diff --git a/.github/allowed-actions.js b/.github/allowed-actions.js index b9d9f05dd8..caf8186623 100644 --- a/.github/allowed-actions.js +++ b/.github/allowed-actions.js @@ -8,15 +8,15 @@ export default [ 'actions/github-script@2b34a689ec86a68d8ab9478298f91d5401337b7d', // v4.0.2 'actions/labeler@5f867a63be70efff62b767459b009290364495eb', // v2.2.0 'actions/setup-node@38d90ce44d5275ad62cc48384b3d8a58c500bb5f', // v2.2.0 - 'actions/stale@9d6f46564a515a9ea11e7762ab3957ee58ca50da', // v3.0.16 + 'actions/stale@cdf15f641adb27a71842045a94023bef6945e3aa', // v4.0.0 'actions/upload-artifact@27121b0bdffd731efa15d66772be8dc71245d074', // v2.2.4 - 'alex-page/github-project-automation-plus@fdb7991b72040d611e1123d2b75ff10eda9372c9', - 'andymckay/labeler@22d5392de2b725cea4b284df5824125054049d84', + 'alex-page/github-project-automation-plus@bb266ff4dde9242060e2d5418e120a133586d488', // v0.8.1 + 'andymckay/labeler@e6c4322d0397f3240f0e7e30a33b5c5df2d39e90', // v1.0.4 'crowdin/github-action@d7f217268068f1244883a993379d62d816f84f25', // v1.4.0 'crykn/copy_folder_to_another_repo_action@0282e8b9fef06de92ddcae9fe6cb44df6226646c', 'cschleiden/actions-linter@caffd707beda4fc6083926a3dff48444bc7c24aa', // uses github-actions-parser v0.23.0 'dawidd6/action-delete-branch@47743101a121ad657031e6704086271ca81b1911', // v3.0.2 - 'dawidd6/action-download-artifact@b9571484721e8187f1fd08147b497129f8972c74', // v2.14.0 + 'dawidd6/action-download-artifact@af92a8455a59214b7b932932f2662fdefbd78126', // v2.15.0 'docker://chinthakagodawita/autoupdate-action:v1', 'dorny/paths-filter@eb75a1edc117d3756a18ef89958ee59f9500ba58', 'github/codeql-action/analyze@v1', @@ -28,12 +28,11 @@ export default [ 'pascalgn/automerge-action@c9bd1823770819dc8fb8a5db2d11a3a95fbe9b07', // v0.12.0 'peter-evans/create-issue-from-file@b4f9ee0a9d4abbfc6986601d9b1a4f8f8e74c77e', 'peter-evans/create-or-update-comment@5221bf4aa615e5c6e95bb142f9673a9c791be2cd', - 'peter-evans/create-pull-request@8c603dbb04b917a9fc2dd991dc54fef54b640b43', + 'peter-evans/create-pull-request@7380612b49221684fefa025244f2ef4008ae50ad', // v3.10.1 'peter-evans/find-comment@0da1f4fc1f20cd898368bd56089d391df418f52f', 'rachmari/actions-add-new-issue-to-column@1a459ef92308ba7c9c9dc2fcdd72f232495574a9', - 'rachmari/labeler@832d42ec5523f3c6d46e8168de71cd54363e3e2e', 'repo-sync/github-sync@3832fe8e2be32372e1b3970bbae8e7079edeec88', - 'repo-sync/pull-request@33777245b1aace1a58c87a29c90321aa7a74bd7d', + 'repo-sync/pull-request@65194d8015be7624d231796ddee1cd52a5023cb3', // v2.6 'someimportantcompany/github-actions-slack-message@0b470c14b39da4260ed9e3f9a4f1298a74ccdefd', 'tjenkinson/gh-action-auto-merge-dependency-updates@4d7756c04d9d999c5968697a621b81c47f533d61', 'Bhacaz/checkout-files@c8f01756bfd894ba746d5bf48205e19000b0742b', // v1.0.0 diff --git a/.github/dependabot.yml b/.github/dependabot.yml new file mode 100644 index 0000000000..8818df1437 --- /dev/null +++ b/.github/dependabot.yml @@ -0,0 +1,12 @@ +version: 2 +updates: + - package-ecosystem: npm + directory: '/' + schedule: + interval: weekly + open-pull-requests-limit: 20 # default is 5 + + - package-ecosystem: 'github-actions' + directory: '/' + schedule: + interval: weekly diff --git a/.github/workflows/60-days-stale-check.yml b/.github/workflows/60-days-stale-check.yml index 24ba31594c..7ab9edcde5 100644 --- a/.github/workflows/60-days-stale-check.yml +++ b/.github/workflows/60-days-stale-check.yml @@ -13,7 +13,7 @@ jobs: if: github.repository == 'github/docs-internal' || github.repository == 'github/docs' runs-on: ubuntu-latest steps: - - uses: actions/stale@9d6f46564a515a9ea11e7762ab3957ee58ca50da + - uses: actions/stale@cdf15f641adb27a71842045a94023bef6945e3aa with: repo-token: ${{ secrets.GITHUB_TOKEN }} stale-issue-message: 'This issue is stale because it has been open 60 days with no activity.' diff --git a/.github/workflows/automerge-dependencies.yml b/.github/workflows/automerge-dependencies.yml index 6e4448a09c..360c1ab9ef 100644 --- a/.github/workflows/automerge-dependencies.yml +++ b/.github/workflows/automerge-dependencies.yml @@ -1,11 +1,15 @@ name: Auto Merge Dependency Updates -# **What it does**: Automatically merge pull requests from dependabot. -# **Why we have it**: To keep our dependencies up-to-date, to avoid security issues. +# **What it does**: +# - automerge-internal: Automatically merge dependabot's pull requests in the internal repository. +# - close-external: Automatically close dependabot's pull requests in the open-source repository. +# **Why we have it**: +# - automerge-internal: To keep our dependencies up-to-date, to avoid security issues. +# - close-external: To avoid duplicating updates against the internal repository. # **Who does it impact**: It helps docs engineering focus on higher value work. on: - pull_request: + pull_request_target: paths: - 'package*.json' - 'Gemfile*' @@ -16,12 +20,67 @@ on: - edited - submitted +permissions: + contents: read + pull-requests: write + jobs: - run: - if: github.repository == 'github/docs-internal' || github.repository == 'github/docs' + automerge-internal: + if: >- + ${{ + github.repository == 'github/docs-internal' && + github.event.pull_request.number && + github.event.pull_request.base.ref == 'main' && + github.event.pull_request.user.login == 'dependabot[bot]' && + github.event.pull_request.state == 'open' + }} runs-on: ubuntu-latest steps: - uses: tjenkinson/gh-action-auto-merge-dependency-updates@4d7756c04d9d999c5968697a621b81c47f533d61 with: repo-token: ${{ secrets.GITHUB_TOKEN }} allowed-actors: dependabot[bot] + + close-external: + if: >- + ${{ + github.repository == 'github/docs' && + github.event.pull_request.number && + github.event.pull_request.base.ref == 'main' && + github.event.pull_request.user.login == 'dependabot[bot]' && + github.event.pull_request.state == 'open' + }} + runs-on: ubuntu-latest + steps: + - name: Close pull request + env: + GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} + PR_URL: ${{ github.event.pull_request.html_url }} + run: | + gh pr close "$PR_URL" + + - name: Comment on the pull request + env: + GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} + PR_URL: ${{ github.event.pull_request.html_url }} + run: | + gh pr comment "$PR_URL" --body "This dependency update will be handled internally by our engineering team." + + # Because we get far too much spam ;_; + - name: Lock conversations + uses: actions/github-script@2b34a689ec86a68d8ab9478298f91d5401337b7d + env: + PR_NUMBER: ${{ github.event.pull_request.number }} + with: + script: | + try { + await github.issues.lock({ + ...context.repo, + issue_number: parseInt(process.env.PR_NUMBER, 10), + lock_reason: 'resolved' + }) + console.log('Locked the pull request to prevent spam!') + } catch (error) { + console.error(`Failed to lock the pull request. Error: ${error}`) + throw error + } diff --git a/.github/workflows/enterprise-dates.yml b/.github/workflows/enterprise-dates.yml index 42fdfb5cf7..72d0a7dc94 100644 --- a/.github/workflows/enterprise-dates.yml +++ b/.github/workflows/enterprise-dates.yml @@ -51,7 +51,7 @@ jobs: - name: Create pull request id: create-pull-request - uses: peter-evans/create-pull-request@8c603dbb04b917a9fc2dd991dc54fef54b640b43 + uses: peter-evans/create-pull-request@7380612b49221684fefa025244f2ef4008ae50ad env: # Disable pre-commit hooks; they don't play nicely here HUSKY: '0' diff --git a/.github/workflows/first-responder-docs-content.yml b/.github/workflows/first-responder-docs-content.yml index 346b534dd1..49ebdeb038 100644 --- a/.github/workflows/first-responder-docs-content.yml +++ b/.github/workflows/first-responder-docs-content.yml @@ -48,7 +48,7 @@ jobs: console.log(`This issue or pull request was authored by an external contributor.`) return 'false' - name: Label external contributor pull requests with docs-content-fr - uses: rachmari/labeler@832d42ec5523f3c6d46e8168de71cd54363e3e2e + uses: andymckay/labeler@e6c4322d0397f3240f0e7e30a33b5c5df2d39e90 if: steps.set-result.outputs.result == 'false' with: repo-token: '${{ secrets.DOCUBOT_READORG_REPO_WORKFLOW_SCOPES }}' @@ -89,7 +89,7 @@ jobs: }) - name: Remove docs-content-fr label if not already removed if: github.event.action == 'closed' - uses: rachmari/labeler@832d42ec5523f3c6d46e8168de71cd54363e3e2e + uses: andymckay/labeler@e6c4322d0397f3240f0e7e30a33b5c5df2d39e90 with: repo-token: '${{ secrets.DOCUBOT_READORG_REPO_WORKFLOW_SCOPES }}' remove-labels: 'docs-content-fr' diff --git a/.github/workflows/move-help-wanted-issues.yml b/.github/workflows/move-help-wanted-issues.yml index 06d23057f1..bd4c630a5b 100644 --- a/.github/workflows/move-help-wanted-issues.yml +++ b/.github/workflows/move-help-wanted-issues.yml @@ -9,13 +9,19 @@ on: types: - labeled +permissions: + issues: none + jobs: move_issues: - if: github.repository == 'github/docs' && (github.event.label.name == 'help wanted' || github.event.label.name == 'good first issue') + if: >- + ${{ + github.repository == 'github/docs' && + (github.event.label.name == 'help wanted' || github.event.label.name == 'good first issue') + }} runs-on: ubuntu-latest - steps: - - uses: alex-page/github-project-automation-plus@fdb7991b72040d611e1123d2b75ff10eda9372c9 + - uses: alex-page/github-project-automation-plus@bb266ff4dde9242060e2d5418e120a133586d488 with: project: Docs team reviews column: Help wanted diff --git a/.github/workflows/move-ready-to-merge-pr.yaml b/.github/workflows/move-ready-to-merge-pr.yaml index 6f7ef03790..f9f5c9871b 100644 --- a/.github/workflows/move-ready-to-merge-pr.yaml +++ b/.github/workflows/move-ready-to-merge-pr.yaml @@ -9,19 +9,27 @@ on: types: - labeled +permissions: + pull-requests: write + jobs: unmark_for_review: - if: github.repository == 'github/docs' && github.event.label.name == 'ready to merge' + if: >- + ${{ + github.repository == 'github/docs' && + github.event.label.name == 'ready to merge' + }} runs-on: ubuntu-latest steps: - name: move PR - uses: alex-page/github-project-automation-plus@fdb7991b72040d611e1123d2b75ff10eda9372c9 + uses: alex-page/github-project-automation-plus@bb266ff4dde9242060e2d5418e120a133586d488 with: project: Docs team reviews column: Triage repo-token: ${{ secrets.DOCUBOT_READORG_REPO_WORKFLOW_SCOPES }} + - name: remove label - uses: andymckay/labeler@22d5392de2b725cea4b284df5824125054049d84 + uses: andymckay/labeler@e6c4322d0397f3240f0e7e30a33b5c5df2d39e90 with: + ignore-if-assigned: 'false' remove-labels: 'waiting for review' - repo-token: ${{ secrets.GITHUB_TOKEN }} diff --git a/.github/workflows/openapi-decorate.yml b/.github/workflows/openapi-decorate.yml index 418f0ee9f1..3ceffe2746 100644 --- a/.github/workflows/openapi-decorate.yml +++ b/.github/workflows/openapi-decorate.yml @@ -5,23 +5,28 @@ name: OpenAPI generate decorated schema files # **Who does it impact**: Anyone making OpenAPI changes in `github/github`, and wanting to get them published on the docs site. on: - workflow_dispatch: pull_request: +permissions: + contents: write + pull-requests: write + jobs: generate-decorated-files: - if: github.event.pull_request.user.login == 'github-openapi-bot' + if: >- + ${{ + github.repository == 'github/docs-internal' && + github.event.pull_request.user.login == 'github-openapi-bot' + }} runs-on: ubuntu-latest steps: - name: Label pull requests with 'github-openapi-bot' - uses: rachmari/labeler@832d42ec5523f3c6d46e8168de71cd54363e3e2e + uses: andymckay/labeler@e6c4322d0397f3240f0e7e30a33b5c5df2d39e90 with: - repo-token: '${{ secrets.GITHUB_TOKEN }}' add-labels: 'github-openapi-bot' + - name: Checkout repository code uses: actions/checkout@5a4ac9002d0be2fb38bd78e4b4dbde5606d7042f - with: - token: ${{ secrets.DOCUBOT_REPO_PAT }} - name: Setup node uses: actions/setup-node@38d90ce44d5275ad62cc48384b3d8a58c500bb5f diff --git a/.github/workflows/remove-unused-assets.yml b/.github/workflows/remove-unused-assets.yml index e6eb420c5f..0e3fbaa739 100644 --- a/.github/workflows/remove-unused-assets.yml +++ b/.github/workflows/remove-unused-assets.yml @@ -42,7 +42,7 @@ jobs: - name: Remove script results file run: rm -rf ./results.md - name: Create pull request - uses: peter-evans/create-pull-request@8c603dbb04b917a9fc2dd991dc54fef54b640b43 + uses: peter-evans/create-pull-request@7380612b49221684fefa025244f2ef4008ae50ad env: # Disable pre-commit hooks; they don't play nicely here HUSKY: '0' diff --git a/.github/workflows/repo-sync.yml b/.github/workflows/repo-sync.yml index 8084a11c06..eb0b936124 100644 --- a/.github/workflows/repo-sync.yml +++ b/.github/workflows/repo-sync.yml @@ -118,7 +118,7 @@ jobs: - name: Create pull request id: create-pull - uses: repo-sync/pull-request@33777245b1aace1a58c87a29c90321aa7a74bd7d + uses: repo-sync/pull-request@65194d8015be7624d231796ddee1cd52a5023cb3 env: GITHUB_TOKEN: ${{ secrets.OCTOMERGER_PAT_WITH_REPO_AND_WORKFLOW_SCOPE }} with: diff --git a/.github/workflows/staging-deploy-pr.yml b/.github/workflows/staging-deploy-pr.yml index 099059c61c..a7e3086157 100644 --- a/.github/workflows/staging-deploy-pr.yml +++ b/.github/workflows/staging-deploy-pr.yml @@ -303,7 +303,7 @@ jobs: # Download the previously built "app.tar" - name: Download build artifact - uses: dawidd6/action-download-artifact@b9571484721e8187f1fd08147b497129f8972c74 + uses: dawidd6/action-download-artifact@af92a8455a59214b7b932932f2662fdefbd78126 with: workflow: ${{ github.event.workflow_run.workflow_id }} run_id: ${{ env.BUILD_ACTIONS_RUN_ID }} diff --git a/.github/workflows/staging-undeploy-pr.yml b/.github/workflows/staging-undeploy-pr.yml index 452a2431d0..404ee3589c 100644 --- a/.github/workflows/staging-undeploy-pr.yml +++ b/.github/workflows/staging-undeploy-pr.yml @@ -50,19 +50,9 @@ jobs: # IMPORTANT: Intentionally OMIT a `concurrency` configuration from this job! steps: - name: Add a label to the PR to block deployment during undeployment - uses: actions/github-script@2b34a689ec86a68d8ab9478298f91d5401337b7d - env: - GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} - PR_NUMBER: ${{ github.event.pull_request.number }} + uses: andymckay/labeler@e6c4322d0397f3240f0e7e30a33b5c5df2d39e90 with: - script: | - const { owner, repo } = context.repo - await github.issues.addLabels({ - owner, - repo, - issue_number: process.env.PR_NUMBER, - labels: ['automated-block-deploy'] - }) + add-labels: 'automated-block-deploy' - name: Check out repo's default branch uses: actions/checkout@5a4ac9002d0be2fb38bd78e4b4dbde5606d7042f @@ -127,19 +117,9 @@ jobs: - if: ${{ always() }} name: Remove the label from the PR to unblock deployment - uses: actions/github-script@2b34a689ec86a68d8ab9478298f91d5401337b7d - env: - GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} - PR_NUMBER: ${{ github.event.pull_request.number }} + uses: andymckay/labeler@e6c4322d0397f3240f0e7e30a33b5c5df2d39e90 with: - script: | - const { owner, repo } = context.repo - await github.issues.removeLabel({ - owner, - repo, - issue_number: process.env.PR_NUMBER, - name: 'automated-block-deploy' - }) + remove-labels: 'automated-block-deploy' - name: Send Slack notification if workflow failed uses: someimportantcompany/github-actions-slack-message@0b470c14b39da4260ed9e3f9a4f1298a74ccdefd diff --git a/.github/workflows/translations.yml b/.github/workflows/translations.yml index 3fe7524c0b..0a609e5f72 100644 --- a/.github/workflows/translations.yml +++ b/.github/workflows/translations.yml @@ -8,6 +8,9 @@ on: schedule: - cron: '20 19 * * *' # once a day at 19:20 UTC / 11:20 PST +permissions: + pull-requests: write + env: FREEZE: ${{ secrets.FREEZE }} @@ -51,13 +54,7 @@ jobs: number: ${{ steps.pr.outputs.number }} - if: ${{ !steps.has-label.outputs.result }} name: Add automerge label - uses: actions/github-script@2b34a689ec86a68d8ab9478298f91d5401337b7d + uses: andymckay/labeler@e6c4322d0397f3240f0e7e30a33b5c5df2d39e90 with: - github-token: ${{ secrets.GITHUB_TOKEN }} - script: | - github.issues.addLabels({ - owner: context.repo.owner, - repo: context.repo.repo, - issue_number: ${{ steps.pr.outputs.number }}, - labels: ['automerge'] - }) + issue-number: ${{ steps.pr.outputs.number }} + add-labels: 'automerge' diff --git a/.github/workflows/triage-issue-comments.yml b/.github/workflows/triage-issue-comments.yml index 2879f7fba8..171ad133dc 100644 --- a/.github/workflows/triage-issue-comments.yml +++ b/.github/workflows/triage-issue-comments.yml @@ -9,9 +9,12 @@ on: types: - created +permissions: + issues: write + jobs: triage-issue-comments: - if: github.repository == 'github/docs' && github.event.issue.pull_request == null + if: ${{ github.repository == 'github/docs' && !github.event.issue.pull_request }} runs-on: ubuntu-latest steps: @@ -19,7 +22,7 @@ jobs: uses: actions/github-script@2b34a689ec86a68d8ab9478298f91d5401337b7d id: is-internal-contributor with: - github-token: ${{secrets.GITHUB_TOKEN}} + github-token: ${{ secrets.GITHUB_TOKEN }} result-encoding: string script: | const repo = context.payload.repository.name @@ -39,10 +42,9 @@ jobs: return 'false' } - name: Label issues with new comments with 'triage' - uses: rachmari/labeler@832d42ec5523f3c6d46e8168de71cd54363e3e2e - if: (steps.is-internal-contributor.outputs.result == 'false') + uses: andymckay/labeler@e6c4322d0397f3240f0e7e30a33b5c5df2d39e90 + if: ${{ steps.is-internal-contributor.outputs.result == 'false' }} with: - repo-token: '${{ secrets.GITHUB_TOKEN }}' add-labels: 'triage' - name: Triage to project board uses: rachmari/actions-add-new-issue-to-column@1a459ef92308ba7c9c9dc2fcdd72f232495574a9 diff --git a/.github/workflows/triage-issues.yml b/.github/workflows/triage-issues.yml index 7a8b15a06d..6260450d5c 100644 --- a/.github/workflows/triage-issues.yml +++ b/.github/workflows/triage-issues.yml @@ -10,16 +10,18 @@ on: - reopened - opened +permissions: + issues: write + jobs: triage_issues: - if: github.repository == 'github/docs' + if: ${{ github.repository == 'github/docs' }} runs-on: ubuntu-latest steps: - name: Label new issues with 'triage' - uses: rachmari/labeler@832d42ec5523f3c6d46e8168de71cd54363e3e2e + uses: andymckay/labeler@e6c4322d0397f3240f0e7e30a33b5c5df2d39e90 with: - repo-token: '${{ secrets.GITHUB_TOKEN }}' add-labels: 'triage' - name: Triage to project board uses: rachmari/actions-add-new-issue-to-column@1a459ef92308ba7c9c9dc2fcdd72f232495574a9 diff --git a/.github/workflows/triage-pull-requests.yml b/.github/workflows/triage-pull-requests.yml index 735b5e6a0d..10887d4efa 100644 --- a/.github/workflows/triage-pull-requests.yml +++ b/.github/workflows/triage-pull-requests.yml @@ -10,16 +10,18 @@ on: - reopened - opened +permissions: + pull-requests: write + jobs: triage_pulls: - if: github.repository != 'github/docs-internal' + if: ${{ github.repository != 'github/docs-internal' }} runs-on: ubuntu-latest steps: - name: Label new pull requests with 'triage' - uses: rachmari/labeler@832d42ec5523f3c6d46e8168de71cd54363e3e2e + uses: andymckay/labeler@e6c4322d0397f3240f0e7e30a33b5c5df2d39e90 with: - repo-token: '${{ secrets.GITHUB_TOKEN }}' add-labels: 'triage' - name: Triage to project board uses: rachmari/actions-add-new-issue-to-column@1a459ef92308ba7c9c9dc2fcdd72f232495574a9 diff --git a/.github/workflows/triage-stale-check.yml b/.github/workflows/triage-stale-check.yml index c8d7f3d29c..b22c11d37f 100644 --- a/.github/workflows/triage-stale-check.yml +++ b/.github/workflows/triage-stale-check.yml @@ -14,7 +14,7 @@ jobs: runs-on: ubuntu-latest steps: - - uses: actions/stale@9d6f46564a515a9ea11e7762ab3957ee58ca50da + - uses: actions/stale@cdf15f641adb27a71842045a94023bef6945e3aa with: repo-token: ${{ secrets.GITHUB_TOKEN }} stale-pr-message: 'A stale label has been added to this pull request because it has been open 7 days with no activity. To keep this PR open, add a comment or push a commit within 3 days.' @@ -26,7 +26,7 @@ jobs: if: github.repository == 'github/docs' runs-on: ubuntu-latest steps: - - uses: actions/stale@9d6f46564a515a9ea11e7762ab3957ee58ca50da + - uses: actions/stale@cdf15f641adb27a71842045a94023bef6945e3aa with: repo-token: ${{ secrets.GITHUB_TOKEN }} stale-pr-message: 'This is a gentle bump for the docs team that this PR is waiting for review.' diff --git a/.github/workflows/triage-unallowed-contributions.yml b/.github/workflows/triage-unallowed-contributions.yml index 6901c27f7a..30e1d18494 100644 --- a/.github/workflows/triage-unallowed-contributions.yml +++ b/.github/workflows/triage-unallowed-contributions.yml @@ -26,7 +26,12 @@ on: jobs: triage: - if: github.repository == 'github/docs' && github.event.pull_request.user.login != 'Octomerger' + if: >- + ${{ + github.repository == 'github/docs' && + github.event.pull_request.user.login != 'Octomerger' && + github.event.pull_request.user.login != 'dependabot[bot]' + }} runs-on: ubuntu-latest steps: - name: Get files changed @@ -70,7 +75,7 @@ jobs: if: ${{ steps.filter.outputs.notAllowed }} uses: actions/github-script@2b34a689ec86a68d8ab9478298f91d5401337b7d with: - github-token: ${{secrets.GITHUB_TOKEN}} + github-token: ${{ secrets.GITHUB_TOKEN }} script: | const badFilesArr = [ '.github/actions-scripts/**', diff --git a/.github/workflows/update-graphql-files.yml b/.github/workflows/update-graphql-files.yml index 2791d8792b..0bd4532808 100644 --- a/.github/workflows/update-graphql-files.yml +++ b/.github/workflows/update-graphql-files.yml @@ -44,7 +44,7 @@ jobs: script/graphql/update-files.js - name: Create pull request id: create-pull-request - uses: peter-evans/create-pull-request@8c603dbb04b917a9fc2dd991dc54fef54b640b43 + uses: peter-evans/create-pull-request@7380612b49221684fefa025244f2ef4008ae50ad env: # Disable pre-commit hooks; they don't play nicely here HUSKY: '0' diff --git a/.github/workflows/workflow-lint.yml b/.github/workflows/workflow-lint.yml index 2153bb944a..bcf082faa8 100644 --- a/.github/workflows/workflow-lint.yml +++ b/.github/workflows/workflow-lint.yml @@ -28,4 +28,4 @@ jobs: - name: Run linter uses: cschleiden/actions-linter@caffd707beda4fc6083926a3dff48444bc7c24aa with: - workflows: '[".github/workflows/*.yml", ".github/workflows/*.yaml", "!.github/workflows/remove-from-fr-board.yaml", "!.github/workflows/staging-deploy-pr.yml", "!.github/workflows/staging-deploy-pr-docker.yml"]' + workflows: '[".github/workflows/*.yml", ".github/workflows/*.yaml", "!.github/workflows/remove-from-fr-board.yaml", "!.github/workflows/staging-deploy-pr.yml", "!.github/workflows/triage-issue-comments.yml"]' diff --git a/assets/images/enterprise/2.22/repository/code-scanning-missing-analysis.png b/assets/images/enterprise/2.22/repository/code-scanning-missing-analysis.png new file mode 100644 index 0000000000..6950cddd66 Binary files /dev/null and b/assets/images/enterprise/2.22/repository/code-scanning-missing-analysis.png differ diff --git a/assets/images/help/settings/actions-review-workflow-rerun.png b/assets/images/help/settings/actions-review-workflow-rerun.png new file mode 100644 index 0000000000..e25da2ffa7 Binary files /dev/null and b/assets/images/help/settings/actions-review-workflow-rerun.png differ diff --git a/components/context/MainContext.tsx b/components/context/MainContext.tsx index e45816b91e..3b5994901b 100644 --- a/components/context/MainContext.tsx +++ b/components/context/MainContext.tsx @@ -62,6 +62,10 @@ export type MainContextT = { article?: BreadcrumbT } activeProducts: Array + communityRedirect: { + name: string + href: string + } currentProduct?: ProductT currentLayoutName: string isHomepageVersion: boolean @@ -110,6 +114,7 @@ export const getMainContext = (req: any, res: any): MainContextT => { return { breadcrumbs: req.context.breadcrumbs || {}, activeProducts: req.context.activeProducts, + communityRedirect: req.context.page?.communityRedirect || {}, currentProduct: req.context.productMap[req.context.currentProduct] || null, currentLayoutName: req.context.currentLayoutName, isHomepageVersion: req.context.page?.documentType === 'homepage', diff --git a/components/lib/display-tool-specific-content.ts b/components/lib/display-tool-specific-content.ts index 6f5ab2ada4..c14de929b0 100644 --- a/components/lib/display-tool-specific-content.ts +++ b/components/lib/display-tool-specific-content.ts @@ -3,7 +3,7 @@ import { preserveAnchorNodePosition } from 'scroll-anchoring' import { sendEvent, EventType } from './events' -const supportedTools = ['cli', 'desktop', 'webui', 'curl', 'codespaces'] +const supportedTools = ['cli', 'desktop', 'webui', 'curl', 'codespaces', 'vscode'] export default function displayToolSpecificContent() { const toolElements = Array.from(document.querySelectorAll('.extended-markdown')).filter((el) => diff --git a/components/page-footer/Support.tsx b/components/page-footer/Support.tsx index 284ca5eda3..9613ad6f4a 100644 --- a/components/page-footer/Support.tsx +++ b/components/page-footer/Support.tsx @@ -7,18 +7,7 @@ import { useMainContext } from 'components/context/MainContext' export const Support = () => { const { isEnterprise } = useVersion() const { t } = useTranslation('support') - const { relativePath } = useMainContext() - - let updatedCommunityLink = '' - - if ( - relativePath?.startsWith('codespaces') || - relativePath?.startsWith('discussions') || - relativePath?.startsWith('sponsors') - ) { - const product = relativePath.substring(0, relativePath.indexOf('/')) - updatedCommunityLink = `https://github.com/github/feedback/discussions/categories/${product}-feedback` - } + const { communityRedirect } = useMainContext() return (
@@ -26,11 +15,11 @@ export const Support = () => {
- {updatedCommunityLink === '' ? t`ask_community` : 'Provide GitHub Feedback'} + {Object.keys(communityRedirect).length === 0 ? t`ask_community` : communityRedirect.name}
diff --git a/components/ui/MarkdownContent/stylesheets/lists.scss b/components/ui/MarkdownContent/stylesheets/lists.scss index da6f495095..ea0051cc78 100644 --- a/components/ui/MarkdownContent/stylesheets/lists.scss +++ b/components/ui/MarkdownContent/stylesheets/lists.scss @@ -1,68 +1,61 @@ .markdownBody { - ol { + ol:not(:global(.no-styling)) { counter-reset: li; list-style: none; position: relative; padding-bottom: 10px; padding-left: 0; - } - ol > li { - padding: 15px 0 15px 55px; - position: relative; - margin-bottom: 5px; - border-top: 3px solid var(--color-auto-gray-2); - } + > li { + padding: 8px 0 8px 40px; + border: 0; + position: relative; + margin-bottom: 5px; - ol > li:before { - content: counter(li); - counter-increment: li; - position: absolute; - top: 10px; - left: 0; - height: 100%; - width: 30px; - padding: 0 10px 0 0; - color: var(--color-auto-gray-4); - font-size: 22px; - font-weight: bold; - line-height: 35px; - text-align: right; - } + &:before { + top: 2px; + font-size: 16px; + width: 24px; + content: counter(li); + counter-increment: li; + position: absolute; + left: 0; + height: 100%; + padding: 0 10px 0 0; + color: var(--color-auto-gray-4); + font-weight: bold; + line-height: 35px; + text-align: right; + } - ol > li > p { - margin: 0; - } + &:after { + content: "."; + display: block; + clear: both; + visibility: hidden; + line-height: 0; + height: 0; + } - ol > li > p:first-child { - margin-top: 0; - } + p { + margin: 0; + } - ol > li:after { - content: "."; - display: block; - clear: both; - visibility: hidden; - line-height: 0; - height: 0; - } + p:first-child { + margin-top: 0; + } - ol > li { - padding: 8px 0 8px 40px; - border: 0; + p:not(:first-child) { + margin-top: 15px; + } - &:before { - top: 2px; - font-size: 16px; - width: 24px; + [class~="extended-markdown"] { + margin-top: 15px; + } } - p:not(:first-child) { - margin-top: 15px; - } - - [class~="extended-markdown"] { - margin-top: 15px; + ol li:before:global(.no-styling) { + display: none; } } diff --git a/content/README.md b/content/README.md index 57bf111abc..8a56ce0ab5 100644 --- a/content/README.md +++ b/content/README.md @@ -28,6 +28,7 @@ See the [contributing docs](/CONTRIBUTING.md) for general information about work - [`type`](#type) - [`topics`](#topics) - [`contributor`](#contributor) + - [`communityRedirect`](#communityRedirect) - [Escaping single quotes](#escaping-single-quotes) - [Autogenerated mini TOCs](#autogenerated-mini-tocs) - [Versioning](#versioning) @@ -220,7 +221,7 @@ defaultPlatform: linux ### `defaultTool` - Purpose: Override the initial tool selection for a page, where tool refers to the application the reader is using to work with GitHub (such as GitHub.com's web UI, the GitHub CLI, or GitHub Desktop) or the GitHub APIs (such as cURL or the GitHub CLI). If this frontmatter is omitted, then the tool-specific content matching the GitHub web UI is shown by default. This behavior can be changed for individual pages, for which a manual selection is more reasonable. -- Type: `String`, one of: `webui`, `cli`, `desktop`, `curl`. +- Type: `String`, one of: `webui`, `cli`, `desktop`, `curl`, `codespaces`, `vscode`. - Optional. ```yaml @@ -264,6 +265,11 @@ includeGuides: - Type: `Object`. Properties are `name` and `URL`. - Optional. +### `communityRedirect` +- Purpose: Set a custom link and link name for `Ask the GitHub community` link in the footer. +- Type: `Object`. Properties are `name` and `href`. +- Optional. + Example: ```yaml diff --git a/content/actions/creating-actions/developing-a-third-party-cli-action.md b/content/actions/creating-actions/developing-a-third-party-cli-action.md new file mode 100644 index 0000000000..273f2d46bf --- /dev/null +++ b/content/actions/creating-actions/developing-a-third-party-cli-action.md @@ -0,0 +1,72 @@ +--- +title: Developing a third party CLI action +shortTitle: CLI setup action +intro: 'Learn how to develop an action to set up a CLI on {% data variables.product.prodname_actions %} runners.' +product: '{% data reusables.gated-features.actions %}' +redirect_from: [] +versions: + fpt: '*' +type: tutorial +topics: + - Actions +--- + +## Introduction + +You can write an action to provide a way for users to access your servers via a configured CLI environment on {% data variables.product.prodname_actions %} runners. + +Your action should: + +- Make it simple for users to specify the version of the CLI to install +- Support multiple operating systems +- Run in an efficient fashion to minimize run-time and associated costs +- Work across {% data variables.product.product_name %}-hosted and self-hosted runners +- Leverage community tooling when possible + +This article will demonstrate how to write an action that retrieves a specific version of your CLI, installs it, adds it to the path, and (optionally) caches it. This type of action (an action that sets up a tool) is often named `setup-$TOOL`. + +## Prerequisites + +You should have an understanding of how to write a custom action. For more information, see "[About custom actions](/actions/creating-actions/about-custom-actions)". For a more detailed guide on how to write a custom action, see "[Creating a JavaScript action](/actions/creating-actions/creating-a-javascript-action)." + +## Example + +The following script demonstrates how you can get a user-specified version as input, download and extract the specific version of your CLI, then add the CLI to the path. + +{% data variables.product.prodname_dotcom %} provides [`actions/toolkit`](https://github.com/actions/toolkit), which is a set of packages that helps you create actions. This example uses the [`actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) and [`actions/tool-cache`](https://github.com/actions/toolkit/tree/main/packages/tool-cache) packages. + +{% raw %} +```javascript{:copy} +const core = require('@actions/core'); +const tc = require('@actions/tool-cache'); + +async function setup() { + // Get version of tool to be installed + const version = core.getInput('version'); + + // Download the specific version of the tool, e.g. as a tarball + const pathToTarball = await tc.downloadTool(getDownloadURL()); + + // Extract the tarball onto the runner + const pathToCLI = await tc.extractTar(pathToTarball); + + // Expose the tool by adding it to the PATH + core.addPath(pathToCLI) +} + +module.exports = setup +``` +{% endraw %} + +To use this script, replace `getDownloadURL` with a function that downloads your CLI. You will also need to create an actions metadata file (`action.yml`) that accepts a `version` input and that runs this script. For full details about how to create an action, see "[Creating a JavaScript action](/actions/creating-actions/creating-a-javascript-action)." + +For a full example of how to set up this action, see [example-setup-gh](https://github.com/github-developer/example-setup-gh). + +## Further reading + +This pattern is employed in several actions. For more examples, see: + +* [`ruby/setup-ruby`](https://github.com/ruby/setup-ruby) +* [`google-github-actions/setup-gcloud`](https://github.com/google-github-actions/setup-gcloud) +* [`hashicorp/setup-terraform`](https://github.com/hashicorp/setup-terraform) + diff --git a/content/actions/creating-actions/index.md b/content/actions/creating-actions/index.md index 39bec938f2..549fc2659b 100644 --- a/content/actions/creating-actions/index.md +++ b/content/actions/creating-actions/index.md @@ -20,6 +20,7 @@ children: - /dockerfile-support-for-github-actions - /setting-exit-codes-for-actions - /publishing-actions-in-github-marketplace + - /developing-a-third-party-cli-action --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} diff --git a/content/actions/deployment/about-continuous-deployment.md b/content/actions/deployment/about-continuous-deployment.md index b80b199a0d..c4bf8c6c1a 100644 --- a/content/actions/deployment/about-continuous-deployment.md +++ b/content/actions/deployment/about-continuous-deployment.md @@ -27,15 +27,19 @@ You can set up a {% data variables.product.prodname_actions %} workflow to deplo You can configure your CD workflow to run when a {% data variables.product.product_name %} event occurs (for example, when new code is pushed to the default branch of your repository), on a set schedule, manually, or when an external event occurs using the repository dispatch webhook. For more information about when your workflow can run, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)." -{% data variables.product.prodname_actions %} provides features that give you more control over deployments. For example, you can use environments to require approval for a job to proceed, restrict which branches can trigger a workflow, or limit access to secrets. You can use concurrency to limit your CD pipeline to a maximum of one in-progress deployment and one pending deployment. For more information about these features, see "[Deploying with GitHub Actions](/actions/deployment/deploying-with-github-actions)" and "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." +{% ifversion fpt or ghae or ghes > 3.0 %} +{% data variables.product.prodname_actions %} provides features that give you more control over deployments. For example, you can use environments to require approval for a job to proceed, restrict which branches can trigger a workflow, or limit access to secrets. {% ifversion fpt or ghae-next or ghes > 3.1 %}You can use concurrency to limit your CD pipeline to a maximum of one in-progress deployment and one pending deployment. {% endif %}For more information about these features, see "[Deploying with GitHub Actions](/actions/deployment/deploying-with-github-actions)" and "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)."{% endif %} ## Workflow templates and third party actions {% data reusables.actions.cd-templates-actions %} +{% ifversion fpt or ghae or ghes > 3.0 %} + ## Further reading - [Deploying with GitHub Actions](/actions/deployment/deploying-with-github-actions) - [Using environments for deployment](/actions/deployment/using-environments-for-deployment){% ifversion fpt %} -- "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)" +- "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)"{% endif %} + {% endif %} diff --git a/content/actions/guides.md b/content/actions/guides.md new file mode 100644 index 0000000000..d02ed0b24c --- /dev/null +++ b/content/actions/guides.md @@ -0,0 +1,66 @@ +--- +title: Guides for GitHub Actions +intro: 'These guides for {% data variables.product.prodname_actions %} include specific use cases and examples to help you configure workflows.' +allowTitleToDifferFromFilename: true +layout: product-sublanding +versions: + fpt: '*' + ghes: '*' + ghae: '*' +learningTracks: + - getting_started + - continuous_integration + - continuous_deployment + - deploy_to_the_cloud + - hosting_your_own_runners + - create_actions +includeGuides: + - /actions/quickstart + - /actions/learn-github-actions/introduction-to-github-actions + - /actions/creating-actions/creating-a-docker-container-action + - /actions/learn-github-actions/using-workflow-templates + - /actions/automating-builds-and-tests/building-and-testing-python + - /actions/automating-builds-and-tests/building-and-testing-nodejs + - /actions/publishing-packages/about-packaging-with-github-actions + - /actions/publishing-packages/publishing-docker-images + - /actions/advanced-guides/caching-dependencies-to-speed-up-workflows + - /actions/automating-builds-and-tests/about-continuous-integration + - /actions/automating-builds-and-tests/building-and-testing-powershell + - /actions/automating-builds-and-tests/building-and-testing-ruby + - /actions/automating-builds-and-tests/building-and-testing-java-with-maven + - /actions/automating-builds-and-tests/building-and-testing-java-with-gradle + - /actions/automating-builds-and-tests/building-and-testing-java-with-ant + - /actions/automating-builds-and-tests/building-and-testing-swift + - /actions/deployment/installing-an-apple-certificate-on-macos-runners-for-xcode-development + - /actions/automating-builds-and-tests/building-and-testing-xamarin-applications + - /actions/publishing-packages/publishing-nodejs-packages + - /actions/publishing-packages/publishing-java-packages-with-maven + - /actions/publishing-packages/publishing-java-packages-with-gradle + - /actions/advanced-guides/storing-workflow-data-as-artifacts + - /actions/using-containerized-services/about-service-containers + - /actions/using-containerized-services/creating-redis-service-containers + - /actions/using-containerized-services/creating-postgresql-service-containers + - /actions/deployment/deploying-to-amazon-elastic-container-service + - /actions/deployment/deploying-to-azure-app-service + - /actions/deployment/deploying-to-google-kubernetes-engine + - /actions/learn-github-actions/essential-features-of-github-actions + - /actions/security-guides/security-hardening-for-github-actions + - /actions/creating-actions/about-custom-actions + - /actions/creating-actions/creating-a-javascript-action + - /actions/creating-actions/creating-a-composite-action + - /actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions + - /actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions + - /actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions + - /actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions + - /actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions + - /actions/managing-issues-and-pull-requests/using-github-actions-for-project-management + - /actions/managing-issues-and-pull-requests/closing-inactive-issues + - /actions/managing-issues-and-pull-requests/scheduling-issue-creation + - /actions/managing-issues-and-pull-requests/adding-labels-to-issues + - /actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added + - /actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards + - /actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column + - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions + - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/keeping-your-actions-up-to-date-with-dependabot +--- + 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 f3a15edd19..6e8c8cedca 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 @@ -54,3 +54,21 @@ Your access token will require the following scope: To authenticate using a {% data variables.product.prodname_dotcom %} App, it must be assigned the following permissions: - For repositories, assign the `administration` permission. - for organizations, assign the `organization_self_hosted_runners` permission. + +## Recommended autoscaling solutions + +{% data variables.product.prodname_dotcom %} recommends and partners closely with two open source projects that you can use for autoscaling your runners. One or both solutions may be suitable, based on your needs. + +The following repositories have detailed instructions for setting up these autoscalers: + +- [actions-runner-controller/actions-runner-controller](https://github.com/actions-runner-controller/actions-runner-controller) - A Kubernetes controller for {% data variables.product.prodname_actions %} self-hosted runnners. +- [philips-labs/terraform-aws-github-runner](https://github.com/philips-labs/terraform-aws-github-runner) - A Terraform module for scalable {% data variables.product.prodname_actions %} runners on Amazon Web Services. + +Each solution has certain specifics that may be important to consider: + +| **Features** | **actions-runner-controller** | **terraform-aws-github-runner** | +| :--- | :--- | :--- | +| Runtime | Kubernetes | Linux and Windows VMs | +| Supported Clouds | Azure, Amazon Web Services, Google Cloud Platform, on-premises | Amazon Web Services | +| Where runners can be scaled | Enterprise, organization, and repository levels. By runner label and runner group. | Organization and repository levels. By runner label and runner group. | +| Pull-based autoscaling support | Yes | No | diff --git a/content/actions/index.md b/content/actions/index.md index aea62f47ed..91e911ace5 100644 --- a/content/actions/index.md +++ b/content/actions/index.md @@ -59,4 +59,5 @@ children: - /using-github-hosted-runners - /hosting-your-own-runners - /migrating-to-github-actions + - /guides --- diff --git a/content/actions/learn-github-actions/reusing-workflows.md b/content/actions/learn-github-actions/reusing-workflows.md index 5b12f1de73..69c5585ff2 100644 --- a/content/actions/learn-github-actions/reusing-workflows.md +++ b/content/actions/learn-github-actions/reusing-workflows.md @@ -45,7 +45,7 @@ A reusable workflow can be used by another workflow if any of the following is t * Reusable workflows can't call other reusable workflows. * Reusable workflows stored within a private repository can only be used by workflows within the same repository. -* Any environment variables set in an `env` context defined at the workflow level in the caller workflow are not be propagated to the called workflow. For more information about the `env` context, see "[Context and expression syntax for GitHub Actions](/actions/reference/context-and-expression-syntax-for-github-actions#env-context)." +* Any environment variables set in an `env` context defined at the workflow level in the caller workflow are not propagated to the called workflow. For more information about the `env` context, see "[Context and expression syntax for GitHub Actions](/actions/reference/context-and-expression-syntax-for-github-actions#env-context)." The following limitations will be removed when workflow reuse moves out of beta: * Reusable workflows can't reference self-hosted runners. diff --git a/content/actions/managing-workflow-runs/index.md b/content/actions/managing-workflow-runs/index.md index 646976f009..73cfdc7857 100644 --- a/content/actions/managing-workflow-runs/index.md +++ b/content/actions/managing-workflow-runs/index.md @@ -14,7 +14,7 @@ versions: ghae: '*' children: - /manually-running-a-workflow - - /re-running-a-workflow + - /re-running-workflows-and-jobs - /canceling-a-workflow - /approving-workflow-runs-from-public-forks - /reviewing-deployments diff --git a/content/actions/managing-workflow-runs/re-running-a-workflow.md b/content/actions/managing-workflow-runs/re-running-a-workflow.md deleted file mode 100644 index d0098bb989..0000000000 --- a/content/actions/managing-workflow-runs/re-running-a-workflow.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -title: Re-running a workflow -intro: You can re-run an instance of a workflow up to 30 days after the initial run. -product: '{% data reusables.gated-features.actions %}' -permissions: People with write permissions to a repository can re-run workflows in the repository. -versions: - fpt: '*' - ghes: '*' - ghae: '*' ---- - -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} - -Re-running a workflow uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (Git ref) of the original event that triggered the workflow run. You can re-run a workflow up to 30 days after the initial run. - -{% include tool-switcher %} - -{% webui %} - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.actions-tab %} -{% data reusables.repositories.navigate-to-workflow %} -{% data reusables.repositories.view-run %} -1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run all jobs**.{% ifversion fpt or ghes > 3.0 or ghae %}![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down-updated.png){% else %}![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png){% endif %} - -{% endwebui %} - -{% cli %} - -{% data reusables.cli.cli-learn-more %} - -To re-run a failed workflow run, use the `run rerun` subcommand. Replace `run-id` with the ID of the failed run that you want to re-run. If you don't specify a `run-id`, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a recent failed run. - -```shell -gh run rerun run-id -``` - -To view the progress of the workflow run, use the `run watch` subcommand and select the run from the interactive list. - -```shell -gh run watch -``` - -{% endcli %} diff --git a/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md b/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md new file mode 100644 index 0000000000..b19a667e10 --- /dev/null +++ b/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md @@ -0,0 +1,72 @@ +--- +title: Re-running workflows and jobs +intro: You can re-run a workflow run up to 30 days after its initial run. +product: '{% data reusables.gated-features.actions %}' +permissions: People with write permissions to a repository can re-run workflows in the repository. +miniTocMaxHeadingLevel: 3 +redirect_from: + - /actions/managing-workflow-runs/re-running-a-workflow +versions: + fpt: '*' + ghes: '*' + ghae: '*' +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +## Re-running all the jobs in a workflow + +Re-running a workflow uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (Git ref) of the original event that triggered the workflow run. You can re-run a workflow for up to 30 days after the initial run. + +{% include tool-switcher %} + +{% webui %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.actions-tab %} +{% data reusables.repositories.navigate-to-workflow %} +{% data reusables.repositories.view-run %} +{% ifversion fpt or ghes > 3.2 or ghae-issue-4721 %} +1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run all jobs** + ![Rerun checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png) +{% endif %} +{% ifversion ghes < 3.3 or ghae %} +1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run all jobs**. + ![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down-updated.png) +{% endif %} + +{% endwebui %} + +{% cli %} + +{% data reusables.cli.cli-learn-more %} + +To re-run a failed workflow run, use the `run rerun` subcommand. Replace `run-id` with the ID of the failed run that you want to re-run. If you don't specify a `run-id`, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a recent failed run. + +```shell +gh run rerun run-id +``` + +To view the progress of the workflow run, use the `run watch` subcommand and select the run from the interactive list. + +```shell +gh run watch +``` + +{% endcli %} + +{% ifversion fpt or ghes > 3.2 or ghae-issue-4721 %} +### Reviewing previous workflow runs + +You can view the results from your previous attempts at running a workflow. You can also view previous workflow runs using the API. For more information, see ["Get a workflow run"](/rest/reference/actions#get-a-workflow-run). + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.actions-tab %} +{% data reusables.repositories.navigate-to-workflow %} +{% data reusables.repositories.view-run %} +1. Any previous run attempts are shown in the left pane. + ![Rerun workflow](/assets/images/help/settings/actions-review-workflow-rerun.png) +1. Click an entry to view its results. + +{% endif %} diff --git a/content/admin/enterprise-support/overview/about-github-enterprise-support.md b/content/admin/enterprise-support/overview/about-github-enterprise-support.md index 73e48c805e..2b8db62f72 100644 --- a/content/admin/enterprise-support/overview/about-github-enterprise-support.md +++ b/content/admin/enterprise-support/overview/about-github-enterprise-support.md @@ -46,6 +46,11 @@ For more information, see "[About {% data variables.contact.premium_support %} f ## Contacting {% data variables.contact.enterprise_support %} +{% ifversion ghes %} +{% data reusables.support.zendesk-deprecation %} +{% endif %} + + You can contact {% data variables.contact.enterprise_support %} through {% ifversion ghes %}{% data variables.contact.contact_enterprise_portal %}{% elsif ghae %} the {% data variables.contact.ae_azure_portal %}{% endif %} to report issues in writing. For more information, see "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)." {% ifversion ghes %} diff --git a/content/admin/enterprise-support/overview/about-support-for-advanced-security.md b/content/admin/enterprise-support/overview/about-support-for-advanced-security.md index dac40da1cc..e2148e5e81 100644 --- a/content/admin/enterprise-support/overview/about-support-for-advanced-security.md +++ b/content/admin/enterprise-support/overview/about-support-for-advanced-security.md @@ -37,6 +37,8 @@ If you're uncertain if the issue is out of scope, open a ticket and we're happy ## Contacting {% data variables.contact.enterprise_support %} +{% data reusables.support.zendesk-deprecation %} + You can contact {% data variables.contact.enterprise_support %} through the {% data variables.contact.contact_enterprise_portal %} for help with: - Installing and using {% data variables.product.prodname_advanced_security %} - Identifying and verifying the causes of supported errors diff --git a/content/admin/enterprise-support/receiving-help-from-github-support/reaching-github-support.md b/content/admin/enterprise-support/receiving-help-from-github-support/reaching-github-support.md index e04a5bb481..6ffc9b3c38 100644 --- a/content/admin/enterprise-support/receiving-help-from-github-support/reaching-github-support.md +++ b/content/admin/enterprise-support/receiving-help-from-github-support/reaching-github-support.md @@ -18,6 +18,8 @@ Though we'll do our best to respond to automated support requests, we typically ## Contacting {% data variables.contact.enterprise_support %} +{% data reusables.support.zendesk-deprecation %} + {% data variables.contact.enterprise_support %} customers can open a support ticket using the {% ifversion ghes %}{% data variables.product.prodname_ghe_server %} {% data variables.enterprise.management_console %} or the {% data variables.contact.contact_enterprise_portal %}{% elsif ghae %} the {% data variables.contact.contact_ae_portal %}{% endif %}. Mark the ticket's priority as {% data variables.product.support_ticket_priority_urgent %}, {% data variables.product.support_ticket_priority_high %}, {% data variables.product.support_ticket_priority_normal %}, or {% data variables.product.support_ticket_priority_low %}. For more information, see "[Assigning a priority to a support ticket](/enterprise/admin/guides/enterprise-support/about-github-enterprise-support#assigning-a-priority-to-a-support-ticket)" and "[Submitting a ticket](/enterprise/admin/guides/enterprise-support/submitting-a-ticket)." ## Contacting {% data variables.contact.enterprise_support %} diff --git a/content/admin/enterprise-support/receiving-help-from-github-support/submitting-a-ticket.md b/content/admin/enterprise-support/receiving-help-from-github-support/submitting-a-ticket.md index 9131c8eab7..76ad6bf019 100644 --- a/content/admin/enterprise-support/receiving-help-from-github-support/submitting-a-ticket.md +++ b/content/admin/enterprise-support/receiving-help-from-github-support/submitting-a-ticket.md @@ -27,6 +27,8 @@ After submitting your support request and optional diagnostic information, {% da ## Submitting a ticket using the {% data variables.contact.enterprise_portal %} +{% data reusables.support.zendesk-deprecation %} + 1. Navigate to the {% data variables.contact.contact_enterprise_portal %}. 5. Click **Submit a Ticket** ![Submit a ticket to Enterprise Support team](/assets/images/enterprise/support/submit-ticket-button.png) diff --git a/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md b/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md index 657c775071..e9a0c4a544 100644 --- a/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md +++ b/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md @@ -31,8 +31,8 @@ After adding a new SSH key to your {% data variables.product.product_name %} acc If your SSH public key file has a different name than the example code, modify the filename to match your current setup. When copying your key, don't add any newlines or whitespace. ```shell - $ pbcopy < ~/.ssh/id_ed25519.pub - # Copies the contents of the id_ed25519.pub file to your clipboard + $ pbcopy < ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}.pub + # Copies the contents of the id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}.pub file to your clipboard ``` {% tip %} @@ -67,8 +67,8 @@ After adding a new SSH key to your {% data variables.product.product_name %} acc If your SSH public key file has a different name than the example code, modify the filename to match your current setup. When copying your key, don't add any newlines or whitespace. ```shell - $ clip < ~/.ssh/id_ed25519.pub - # Copies the contents of the id_ed25519.pub file to your clipboard + $ clip < ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}.pub + # Copies the contents of the id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}.pub file to your clipboard ``` {% tip %} @@ -103,8 +103,8 @@ After adding a new SSH key to your {% data variables.product.product_name %} acc If your SSH public key file has a different name than the example code, modify the filename to match your current setup. When copying your key, don't add any newlines or whitespace. ```shell - $ cat ~/.ssh/id_ed25519.pub - # Then select and copy the contents of the id_ed25519.pub file + $ cat ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}.pub + # Then select and copy the contents of the id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}.pub file # displayed in the terminal to your clipboard ``` diff --git a/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md b/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md index a61e325339..4d0f52284e 100644 --- a/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md +++ b/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md @@ -13,26 +13,30 @@ topics: - SSH shortTitle: Check for existing SSH key --- + {% data reusables.ssh.key-type-support %} {% data reusables.command_line.open_the_multi_os_terminal %} -2. Enter `ls -al ~/.ssh` to see if existing SSH keys are present: +2. Enter `ls -al ~/.ssh` to see if existing SSH keys are present. ```shell $ ls -al ~/.ssh # Lists the files in your .ssh directory, if they exist ``` -3. Check the directory listing to see if you already have a public SSH key. By default, the filenames of the public keys are one of the following: + +3. Check the directory listing to see if you already have a public SSH key. By default, the {% ifversion ghae %}filename of a supported public key for {% data variables.product.product_name %} is *id_rsa.pub*.{% elsif fpt or ghes %}filenames of supported public keys for {% data variables.product.product_name %} are one of the following. - *id_rsa.pub* - *id_ecdsa.pub* - - *id_ed25519.pub* + - *id_ed25519.pub*{% endif %} -If you don't have an existing public and private key pair, or don't wish to use any that are available to connect to {% data variables.product.product_name %}, then [generate a new SSH key](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent). + {% tip %} -If you see an existing public and private key pair listed (for example *id_rsa.pub* and *id_rsa*) that you would like to use to connect to {% data variables.product.product_name %}, you can [add your SSH key to the ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/#adding-your-ssh-key-to-the-ssh-agent). + **Tip**: If you receive an error that *~/.ssh* doesn't exist, you do not have an existing SSH key pair in the default location. You can create a new SSH key pair in the next step. -{% tip %} + {% endtip %} -**Tip:** If you receive an error that *~/.ssh* doesn't exist, don't worry! We'll create it when we [generate a new SSH key](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent). +4. Either generate a new SSH key or upload an existing key. + - If you don't have a supported public and private key pair, or don't wish to use any that are available, generate a new SSH key. + - If you see an existing public and private key pair listed (for example, *id_rsa.pub* and *id_rsa*) that you would like to use to connect to {% data variables.product.product_name %}, you can add the key to the ssh-agent. -{% endtip %} + For more information about generation of a new SSH key or addition of an existing key to the ssh-agent, see "[Generating a new SSH key and adding it to the ssh-agent](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." diff --git a/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md b/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md index 240eaa3c3a..d56e137655 100644 --- a/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md +++ b/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md @@ -22,7 +22,7 @@ With SSH keys, if someone gains access to your computer, they also gain access t You can change the passphrase for an existing private key without regenerating the keypair by typing the following command: ```shell -$ ssh-keygen -p -f ~/.ssh/id_ed25519 +$ ssh-keygen -p -f ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %} > Enter old passphrase: [Type old passphrase] > Key has comment 'your_email@example.com' > Enter new passphrase (empty for no passphrase): [Type new passphrase] diff --git a/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md b/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md index 17daa99047..6023f07ac0 100644 --- a/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md +++ b/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md @@ -165,7 +165,7 @@ codeql database analyze <database> --format=<format> \ | Option | Required | Usage | |--------|:--------:|-----| | `` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the path for the directory that contains the {% data variables.product.prodname_codeql %} database to analyze. | -| `` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the queries to run. To run the standard queries used for {% data variables.product.prodname_code_scanning %}, use: `-code-scanning.qls` where `` is the short code for the language of the database. To see the other query suites included in the {% data variables.product.prodname_codeql_cli %} bundle, look in `//codeql/qlpacks/codeql-/codeql-suites`. For information about creating your own query suite, see [Creating CodeQL query suites](https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/) in the documentation for the {% data variables.product.prodname_codeql_cli %}. +| `` | | Specify {% data variables.product.prodname_codeql %} packs or queries to run. To run the standard queries used for {% data variables.product.prodname_code_scanning %}, omit this parameter. To see the other query suites included in the {% data variables.product.prodname_codeql_cli %} bundle, look in `//codeql/qlpacks/codeql-/codeql-suites`. For information about creating your own query suite, see [Creating CodeQL query suites](https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/) in the documentation for the {% data variables.product.prodname_codeql_cli %}. | `--format` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the format for the results file generated by the command. For upload to {% data variables.product.company_short %} this should be: {% ifversion fpt or ghae %}`sarif-latest`{% else %}`sarifv2.1.0`{% endif %}. For more information, see "[SARIF support for {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/sarif-support-for-code-scanning)." | `--output` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify where to save the SARIF results file.{% ifversion fpt or ghes > 3.1 or ghae %} | `--sarif-category` | {% octicon "question" aria-label="Required with multiple results sets" %} | Optional for single database analysis. Required to define the language when you analyze multiple databases for a single commit in a repository. Specify a category to include in the SARIF results file for this analysis. A category is used to distinguish multiple analyses for the same tool and commit, but performed on different languages or different parts of the code.|{% endif %}{% if codeql-packs %} diff --git a/content/codespaces/index.md b/content/codespaces/index.md index 5c3572bab3..714a40d30d 100644 --- a/content/codespaces/index.md +++ b/content/codespaces/index.md @@ -24,6 +24,9 @@ featuredLinks: - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account popularHeading: Set up your project product_video: 'https://www.youtube-nocookie.com/embed/_W9B7qc9lVc' +communityRedirect: + name: 'Provide GitHub Feedback' + href: 'https://github.com/github/feedback/discussions/categories/codespaces-feedback' redirect_from: - /github/developing-online-with-github-codespaces - /github/developing-online-with-codespaces diff --git a/content/developers/webhooks-and-events/webhooks/about-webhooks.md b/content/developers/webhooks-and-events/webhooks/about-webhooks.md index 7acbcd46c4..05ac954e6e 100644 --- a/content/developers/webhooks-and-events/webhooks/about-webhooks.md +++ b/content/developers/webhooks-and-events/webhooks/about-webhooks.md @@ -32,4 +32,4 @@ For a complete list of available webhook events and their payloads, see "[Webhoo For more information about the `ping` event webhook payload, see the [`ping`](/webhooks/event-payloads/#ping) event. [org-hooks]: /rest/reference/orgs#webhooks/ -[repo-hooks]: /rest/reference/repos#hooks +[repo-hooks]: /rest/reference/repos#webhooks diff --git a/content/discussions/index.md b/content/discussions/index.md index c26f1bcf1a..df6f67a732 100644 --- a/content/discussions/index.md +++ b/content/discussions/index.md @@ -28,6 +28,9 @@ product_video: 'https://www.youtube-nocookie.com/embed/IpBw2SJkFyk' layout: product-landing versions: fpt: '*' +communityRedirect: + name: 'Provide GitHub Feedback' + href: 'https://github.com/github/feedback/discussions/categories/discussions-feedback' children: - /quickstart - /guides diff --git a/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md b/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md index 87ee28d1e1..4bd7c238d1 100644 --- a/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md +++ b/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md @@ -85,7 +85,7 @@ The names of the {% data variables.product.prodname_code_scanning %} analysis ch 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 a "Missing analysis" message when you click **Details** on the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" check. - ![Missing analysis for commit message](/assets/images/help/repository/code-scanning-missing-analysis.png) + ![Missing analysis for commit message](/assets/images/enterprise/2.22/repository/code-scanning-missing-analysis.png) ### Reasons for the "missing analysis" message diff --git a/content/github/site-policy/github-data-protection-agreement-non-enterprise-customers.md b/content/github/site-policy/github-data-protection-agreement-non-enterprise-customers.md deleted file mode 100644 index 2072cf4666..0000000000 --- a/content/github/site-policy/github-data-protection-agreement-non-enterprise-customers.md +++ /dev/null @@ -1,356 +0,0 @@ ---- -title: GitHub Data Protection Agreement (Non-Enterprise Customers) -redirect_from: - - /github/site-policy/github-data-protection-addendum - - /github/site-policy-deprecated/github-data-protection-addendum -versions: - fpt: '*' ---- - -_These terms apply to non-enterprise customers. They also apply to enterprise customers who licensed GitHub offerings prior to January 4, 2021. Enterprise customers who purchase GitHub offerings after that date are directed to https://www.github.com/enterprise-legal for current terms._ - -## INTRODUCTION - -The parties agree that the GitHub Data Protection Agreement (Non-Enterprise Customers) (**“DPA”**) sets forth their obligations with respect to the processing of Customer Personal Data in connection with the GitHub Enterprise Cloud hosted service (the **“Service”**). GitHub makes the commitments in this DPA to all non-enterprise customers using the Service. Separate terms, including different privacy terms, govern Customer’s use of non-GitHub products. - -In the event of any conflict or inconsistency between the DPA and any other terms in Customer’s agreements with GitHub, the DPA shall prevail. The provisions of the DPA supersede any conflicting provisions of the GitHub Privacy Statement that otherwise may apply to processing of Customer Personal Data as defined herein. For clarity, consistent with Clause 10 of the Standard Contractual Clauses in Attachment 1, the Standard Contractual Clauses prevail over any other terms in the DPA. - - -## GITHUB DATA PROTECTION - -### 1. Definitions. - -1.1 The "**Applicable Data Protection Laws**" means certain laws, regulations, regulatory frameworks, or other legislations relating to the processing and use of Customer Personal Data, as applicable to Customer's use of GitHub and the GitHub Service, including: - - a. The EU General Data Protection Regulation 2016/679 (**"GDPR"**), along with any implementing or corresponding equivalent national laws or regulations, once in effect and applicable; and - - b. The California Consumer Privacy Act of 2018, Cal. Civ. Code §§1798.100 et seq. (**"CCPA"**); and - - c. The UK Data Protection Act 2018 and implementation of GDPR contained therein. - -1.2 "**Controller**," "**Data Subject**," "**Member State**," "**Personal Data**," "**Personal Data Breach**," "**Processing**," "**Processor**," and "**Supervisory Authority**" have the meanings given to them in the Applicable Data Protection Laws. In the event of a conflict, the meanings given in the GDPR will supersede. - -1.3 "**Customer Personal Data**" means any Personal Data for which Customer is a Controller, whether supplied by Customer for processing by GitHub or generated by GitHub in the course of performing its obligations under the Agreement. It includes data such as billing information, IP addresses, corporate email addresses, and any other Personal Data for which Customer is a Controller. - -1.4 "**Customer Repository Data**" means any data or information that is uploaded or created by Customer into any of its Private Repositories. - -1.5 A "**Data Breach**" means a Personal Data Breach or any other confirmed or reasonably suspected breach of Customer's Protected Data. - -1.6 "**End User**" means an individual Data Subject who controls a GitHub account and has agreed to the GitHub Terms of Service, and whose Personal Data is being transferred, stored, or processed by GitHub. For example, each Customer employee or contractor who has a GitHub account is also a GitHub End User. - -1.7 "**Permitted Purposes**" for data processing are those limited and specific purposes of providing the Service as set forth in the Agreement, the GitHub Privacy Statement, and this Exhibit A, or the purposes for which a Data Subject has authorized the use of Customer Personal Data. - -1.8 "**Protected Data**" includes any Customer Personal Data and any Customer Repository Data processed by GitHub on behalf of Customer under the Agreement. - -1.9 "**Sensitive Data**" means any Customer Personal Data revealing racial or ethnic origin; political opinions, religious or philosophical beliefs or trade union membership; processing of genetic data or biometric data for the purposes of uniquely identifying a natural person; data concerning health, a natural person's sex life or sexual orientation; and data relating to offences, criminal convictions, or security measures. - -### 2. Status and Compliance. - -#### 2.1 Data Processing. -GitHub acts as a Processor in regard to any Customer Personal Data it receives in connection with the Agreement, and GitHub will process Customer Personal Data only for Permitted Purposes in accordance with Customer's instructions as represented by the Agreement and other written communications. In the event that GitHub is unable to comply with Customer's instructions, such as due to conflicts with the Applicable Data Protection Laws, or where processing is required by the Applicable Data Protection Laws or other legal requirements, GitHub will notify Customer to the extent permissible. GitHub processes all Customer Personal Data in the United States or in the European Union; however, GitHub's subprocessors may process data outside of the United States or the European Union. Additionally, GitHub acts as a Processor for any Customer Repository Data. - -#### 2.2 Data Controllers. -GitHub receives Customer Personal Data both from Customer and directly from Data Subjects who create End User accounts. Customer is a Controller only for the Customer Personal Data it transfers directly to GitHub. - -#### 2.3 GitHub Compliance; Data Transfers. -GitHub will comply with Applicable Data Protection Laws in relation to the processing of Customer Personal Data. - -All transfers of Customer Personal Data out of the European Union, European Economic Area, United Kingdom, and Switzerland to provide the Service shall be governed by the Standard Contractual Clauses in Attachment 1 (Standard Contractual Clauses). -GitHub will abide by the requirements of European Economic Area and Swiss data protection law regarding the collection, use, transfer, retention, and other processing of Customer Personal Data from the European Economic Area, United Kingdom, and Switzerland. All transfers of Customer Personal Data to a third country or an international organization will be subject to appropriate safeguards as described in Article 46 of the GDPR and such transfers and safeguards will be documented according to Article 30(2) of the GDPR. - -In addition, GitHub is certified to the EU-U.S. and Swiss-U.S. Privacy Shield Frameworks and the commitments they entail, although GitHub does not rely on them as a legal basis for transfers of Personal Data. GitHub agrees to notify Customer if it makes a determination that it can no longer meet its obligation to provide the same level of protection as is required by the Privacy Shield principles. - - -### 3. Data Protection. - -#### 3.1 Purpose Limitation. -GitHub will process and communicate the Protected Data only for Permitted Purposes, unless the Parties agree in writing to an expanded purpose. - -#### 3.2 Data Quality and Proportionality. -GitHub will keep the Customer Personal Data accurate and up to date, or enable Customer to do so. GitHub will take commercially reasonable steps to ensure that any Protected Data it collects on Customer's behalf is adequate, relevant, and not excessive in relation to the purposes for which it is transferred and processed. In no event will GitHub intentionally collect Sensitive Data on Customer's behalf. Customer agrees that the GitHub Service is not intended for the storage of Sensitive Data; if Customer chooses to upload Sensitive Data to the Service, Customer must comply with Article 9 of the GDPR, or equivalent provisions in the Applicable Data Protection Laws. - -#### 3.3 Data Retention and Deletion. -Upon Customer's reasonable request, unless prohibited by law, GitHub will return, destroy, or deidentify all Customer Personal Data and related data at all locations where it is stored after it is no longer needed for the Permitted Purposes within thirty days of request. GitHub may retain Customer Personal Data and related data to the extent required by the Applicable Data Protection Laws, and only to the extent and for such period as required by the Applicable Data Protection Laws, provided that GitHub will ensure that Customer Personal Data is processed only as necessary for the purpose specified in the Applicable Data Protection Laws and no other purpose, and Customer Personal Data remains protected by the Applicable Data Protection Laws. - -#### 3.4 Data Processing. -GitHub provides the following information, required by Article 28(3) of the GDPR, regarding its processing of Customer's Protected Data: - -a. *The subject matter and duration of the processing* of Customer Personal Data are set out in the Agreement and this Addendum. - -b. *The nature and purpose of the processing* of Customer Personal Data is described in Section 3.1 of this Addendum. - -c. *The types of Customer Personal Data to be processed* are described in the GitHub Privacy Statement, and include Customer Personal Data such as user names, passwords, email addresses, and IP addresses. GitHub also processes information necessary for billing Customer's account, but does not process or store credit card information. Customer may choose to supply GitHub with additional Customer Personal Data, such as in Customer's profile settings or by uploading Customer Personal Data to its GitHub repositories. - -d. *The categories of Data Subject to whom the Customer Personal Data relates* are the Customer itself and its End Users. - -e. *The obligations and rights of Customer* are set out in the Agreement and this Addendum. - -### 4. Security and Audit Obligations. - -#### 4.1 Technical and Organizational Security Measures. -Taking into account the state of the art, the costs of implementation, and the nature, scope, context and purposes of processing as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons, GitHub will implement appropriate technical and organizational measures to ensure a level of security appropriate to the risks, such as against accidental or unlawful destruction, or loss, alteration, unauthorized disclosure or access, presented by processing the Protected Data. GitHub will regularly monitor compliance with these measures and will continue to take appropriate safeguards throughout the duration of the Agreement. - -#### 4.2 Incident Response and Breach Notification. -GitHub will comply with Applicable Data Protection Laws. - -#### 4.3 GitHub Personnel. -GitHub represents and warrants that it will take reasonable steps to ensure that all GitHub personnel processing Protected Data have agreed to keep the Protected Data confidential and have received adequate training on compliance with this Addendum and the Applicable Data Protection Laws. - -#### 4.4 Records. -GitHub will maintain complete, accurate, and up to date written records of all categories of processing activities carried out on behalf of Customer containing the information required under the Applicable Data Protection Laws. To the extent that assistance does not risk the security of GitHub or the privacy rights of individual Data Subjects, GitHub will make these records available to Customer on request as reasonably required, such as to help Customer demonstrate its compliance under the Applicable Data Protection Laws. - -#### 4.5 Assistance. -GitHub will provide reasonable assistance to Customer with concerns such as data privacy impact assessments, Data Subject rights requests, consultations with Supervisory Authorities, and other similar matters, in each case solely in relation to the processing of Customer Personal Data and taking into account the nature of processing. - -### 5. Use and Disclosure of Protected Data. - -#### 5.1 No Use in Marketing. -GitHub will not use the Protected Data for the purposes of advertising third-party content, and will not sell the Protected Data to any third party except as part of a merger or acquisition. - -#### 5.2 GitHub Privacy Statement. -The GitHub Privacy Statement, publicly available at [https://docs.github.com/articles/github-privacy-statement](/articles/github-privacy-statement), provides detailed notice of GitHub's privacy and data use practices, including its use of cookies, its dispute resolution process, and further details about GitHub's GDPR compliance. - -### 6. Subprocessing and Onward Transfer. - -#### 6.1 Protection of Data. -GitHub is liable for onward transfers of Protected Data to its subprocessors, such as its third-party payment processor. In the event that GitHub does transfer the Protected Data to a third-party subprocessor, or GitHub installs, uses, or enables a third party or third-party services to process the Protected Data on GitHub's behalf, GitHub will ensure that the third-party subprocessor is bound by written agreement that requires them to provide at least the same level of confidentiality, security, and privacy protection as is required of GitHub by this DPA and the Applicable Data Protection Laws. - -#### 6.2 Acceptance of GitHub Subprocessors. -Customer authorizes GitHub to appoint (and permit each subprocessor appointed in accordance with this Section 6 to appoint) subprocessors in accordance with Section 6 and any other restrictions in the Agreement. GitHub may continue to use those subprocessors currently engaged as of the Effective Date of this Addendum. - -#### 6.3 General Consent for Onward Subprocessing. -Customer provides a general consent for GitHub to engage onward subprocessors, conditional on GitHub's compliance with the following requirements: - -a. Any onward subprocessor must agree in writing to only process data in a country that the European Commission has declared to have an "adequate" level of protection; or to only process data on terms equivalent to the Standard Contractual Clauses, or pursuant to a Binding Corporate Rules approval granted by competent European data protection authorities, or pursuant to compliant and valid EU-US Privacy Shield and Swiss-U.S. Privacy Shield certifications; and - -b. GitHub will restrict the onward subprocessor's access to Customer Personal Data only to what is strictly necessary to perform its services, and GitHub will prohibit the subprocessor from processing the Customer Personal Data for any other purpose. - -#### 6.4 Disclosure of Subprocessor Agreements. -GitHub maintains a list of onward subprocessors it has engaged to process Customer Personal Data at [https://docs.github.com/articles/github-subprocessors-and-cookies](/articles/github-subprocessors-and-cookies), including the categories of Customer Personal Data processed, a description of the type of processing the subprocessor performs, and the location of its processing. GitHub will, upon Customer's written request, provide Customer with this list of subprocessors and the terms under which they process the Customer Personal Data. Pursuant to subprocessor confidentiality restrictions, GitHub may remove any confidential or commercially sensitive information before providing the list and the terms to Customer. In the event that GitHub cannot disclose confidential or sensitive information to Customer, the Parties agree that GitHub will provide all information it reasonably can in connection with its subprocessing agreements. - -#### 6.5 Objection to Subprocessors. -GitHub will provide thirty (30) days' prior written notice of the addition or removal of any subprocessor, including the categories listed in Section 6.4, by announcing changes on its site. If Customer has a reasonable objection to GitHub's engagement of a new subprocessor, Customer must notify GitHub promptly in writing. Where possible, GitHub will use commercially reasonable efforts to provide an alternative solution to the affected Service to avoid processing of data by the objectionable subprocessor. In the event that GitHub is unable to provide an alternative solution and the Parties cannot resolve the conflict within ninety days, Customer may terminate the Agreement. - -### 7. Termination. - -#### 7.1 Suspension. -In the event that GitHub is in breach of its obligations to maintain an adequate level of security or privacy protection, Customer may temporarily suspend the transfer of all Customer Personal Data or prohibit collection and processing of Customer Personal Data on Customer's behalf until the breach is repaired or the Agreement is terminated. - -#### 7.2 Termination with Cause. -In addition to any termination rights Customer has under the Agreement, Customer may terminate the Agreement without prejudice to any other claims at law or in equity in the event that: - -a. GitHub notifies Customer that it can no longer meet its privacy obligations; - -b. the transfer, collection, or processing of all Customer Personal Data has been temporarily suspended for longer than one month pursuant to Section 7.1; - -c. GitHub is in substantial or persistent breach of any warranties or representations under this Addendum; - -d. GitHub is no longer carrying on business, is dissolved, enters receivership, or a winding up order is made on behalf of GitHub; or - -e. Customer objects to a subprocessor pursuant to Section 6.5, and GitHub has not been able to provide an alternative solution within ninety days. - -#### 7.3 Breach. -Failure to comply with the material provisions of this Addendum is considered a material breach under the Agreement. - -#### 7.4 Failure to perform. -In the event that changes in law or regulation render performance of this Addendum impossible or commercially unreasonable, the Parties may renegotiate the Addendum in good faith. If renegotiation would not cure the impossibility, or if the Parties cannot reach an agreement, the Parties may terminate the Agreement after thirty days. - -#### 7.5 Notification. -In the event that GitHub determines that it can no longer meet its privacy obligations under this Addendum, GitHub will notify Customer in writing immediately. - -#### 7.6 Modifications. -GitHub may modify this Addendum from time to time as required by the Applicable Data Protection Laws, with thirty days' notice to Customer. - -#### 7.7 Termination Requirements. -Upon Termination, GitHub must: - -a. take reasonable and appropriate steps to stop processing the Customer Personal Data; - -b. within ninety days of termination, delete or deidentify any Customer Personal Data GitHub stores on Customer's behalf pursuant to Section 3.3; and - -c. provide Customer with reasonable assurance that GitHub has complied with its obligations in Section 7.7. - -### 8. Liability for Data Processing. - -#### 8.1 Limitations. -Except as limited by the Applicable Data Protection Laws, any claims brought under this Addendum will be subject to the terms of the Agreement regarding Limitations of Liability. - -## Attachment 1 – The Standard Contractual Clauses (Processors) -Execution of the applicable agreement by Customer includes execution of this Attachment 1 to the GitHub Data Protection Addendum, which is countersigned by GitHub, Inc. - -In countries where regulatory approval is required for use of the Standard Contractual Clauses, the Standard Contractual Clauses cannot be relied upon under European Commission 2010/87/EU (of February 2010) to legitimize export of data from the country, unless Customer has the required regulatory approval. - -For the purposes of Article 46(2) of the General Data Protection Regulation (EU 2016/679) for the transfer of personal data to processors established in third countries which do not ensure an adequate level of data protection, Customer (as data exporter) and GitHub (as data importer, whose signature appears below), each a “party,” together “the parties,” have agreed on the following Contractual Clauses (the “Clauses” or “Standard Contractual Clauses”) in order to adduce adequate safeguards with respect to the protection of privacy and fundamental rights and freedoms of individuals for the transfer by the data exporter to the data importer of the personal data specified in Appendix 1. - -#### Clause 1: Definitions -(a) 'personal data', 'special categories of data', 'process/processing', 'controller', 'processor', 'data subject' and 'supervisory authority' shall have the same meaning as in the General Data Protection Regulation (EU 2016/679) on the protection of individuals with regard to the processing of personal data and on the free movement of such data; - -(b) 'the data exporter' means the controller who transfers the personal data; - -(c) 'the data importer' means the processor who agrees to receive from the data exporter personal data intended for processing on his behalf after the transfer in accordance with his instructions and the terms of the Clauses and who is not subject to a third country's system ensuring adequate protection within the meaning of Article 45(2) of the General Data Protection Regulation (EU 2016/679); - -(d) 'the subprocessor' means any processor engaged by the data importer or by any other subprocessor of the data importer who agrees to receive from the data importer or from any other subprocessor of the data importer personal data exclusively intended for processing activities to be carried out on behalf of the data exporter after the transfer in accordance with his instructions, the terms of the Clauses and the terms of the written subcontract; - -(e) 'the applicable data protection law' means the legislation protecting the fundamental rights and freedoms of individuals and, in particular, their right to privacy with respect to the processing of personal data applicable to a data controller in the Member State in which the data exporter is established; - -(f) 'technical and organizational security measures' means those measures aimed at protecting personal data against accidental or unlawful destruction or accidental loss, alteration, unauthorized disclosure or access, in particular where the processing involves the transmission of data over a network, and against all other unlawful forms of processing. - -#### Clause 2: Details of the transfer -The details of the transfer and in particular the special categories of personal data where applicable are specified in Appendix 1 below which forms an integral part of the Clauses. - -#### Clause 3: Third-party beneficiary clause -1. The data subject can enforce against the data exporter this Clause, Clause 4(b) to (i), Clause 5(a) to (e), and (g) to (j), Clause 6(1) and (2), Clause 7, Clause 8(2), and Clauses 9 to 12 as third-party beneficiary. - -2. The data subject can enforce against the data importer this Clause, Clause 5(a) to (e) and (g), Clause 6, Clause 7, Clause 8(2), and Clauses 9 to 12, in cases where the data exporter has factually disappeared or has ceased to exist in law unless any successor entity has assumed the entire legal obligations of the data exporter by contract or by operation of law, as a result of which it takes on the rights and obligations of the data exporter, in which case the data subject can enforce them against such entity. - -3. The data subject can enforce against the subprocessor this Clause, Clause 5(a) to (e) and (g), Clause 6, Clause 7, Clause 8(2), and Clauses 9 to 12, in cases where both the data exporter and the data importer have factually disappeared or ceased to exist in law or have become insolvent, unless any successor entity has assumed the entire legal obligations of the data exporter by contract or by operation of law as a result of which it takes on the rights and obligations of the data exporter, in which case the data subject can enforce them against such entity. Such third-party liability of the subprocessor shall be limited to its own processing operations under the Clauses. - -4. The parties do not object to a data subject being represented by an association or other body if the data subject so expressly wishes and if permitted by national law. - -#### Clause 4: Obligations of the data exporter -The data exporter agrees and warrants: - -(a) that the processing, including the transfer itself, of the personal data has been and will continue to be carried out in accordance with the relevant provisions of the applicable data protection law (and, where applicable, has been notified to the relevant authorities of the Member State where the data exporter is established) and does not violate the relevant provisions of that State; - -(b) that it has instructed and throughout the duration of the personal data processing services will instruct the data importer to process the personal data transferred only on the data exporter's behalf and in accordance with the applicable data protection law and the Clauses; - -(c) that the data importer will provide sufficient guarantees in respect of the technical and organizational security measures specified in Appendix 2 below; - -(d) that after assessment of the requirements of the applicable data protection law, the security measures are appropriate to protect personal data against accidental or unlawful destruction or accidental loss, alteration, unauthorized disclosure or access, in particular where the processing involves the transmission of data over a network, and against all other unlawful forms of processing, and that these measures ensure a level of security appropriate to the risks presented by the processing and the nature of the data to be protected having regard to the state of the art and the cost of their implementation; - -(e) that it will ensure compliance with the security measures; - -(f) that, if the transfer involves special categories of data, the data subject has been informed or will be informed before, or as soon as possible after, the transfer that its data could be transmitted to a third country not providing adequate protection within the meaning of the General Data Protection Regulation (EU 2016/679); - -(g) to forward any notification received from the data importer or any subprocessor pursuant to Clause 5(b) and Clause 8(3) to the data protection supervisory authority if the data exporter decides to continue the transfer or to lift the suspension; - -(h) to make available to the data subjects upon request a copy of the Clauses, with the exception of Appendix 2, and a summary description of the security measures, as well as a copy of any contract for subprocessing services which has to be made in accordance with the Clauses, unless the Clauses or the contract contain commercial information, in which case it may remove such commercial information; - -(i) that, in the event of subprocessing, the processing activity is carried out in accordance with Clause 11 by a subprocessor providing at least the same level of protection for the personal data and the rights of data subject as the data importer under the Clauses; and - -(j) that it will ensure compliance with Clause 4(a) to (i). - -#### Clause 5: Obligations of the data importer -The data importer agrees and warrants: - -(a) to process the personal data only on behalf of the data exporter and in compliance with its instructions and the Clauses; if it cannot provide such compliance for whatever reasons, it agrees to inform promptly the data exporter of its inability to comply, in which case the data exporter is entitled to suspend the transfer of data and/or terminate the contract; - -(b) that it has no reason to believe that the legislation applicable to it prevents it from fulfilling the instructions received from the data exporter and its obligations under the contract and that in the event of a change in this legislation which is likely to have a substantial adverse effect on the warranties and obligations provided by the Clauses, it will promptly notify the change to the data exporter as soon as it is aware, in which case the data exporter is entitled to suspend the transfer of data and/or terminate the contract; - -(c) that it has implemented the technical and organizational security measures specified in Appendix 2 before processing the personal data transferred; - -(d) that it will promptly notify the data exporter about: - -(i) any legally binding request for disclosure of the personal data by a law enforcement authority unless otherwise prohibited, such as a prohibition under criminal law to preserve the confidentiality of a law enforcement investigation, - -(ii) any accidental or unauthorized access, and - -(iii) any request received directly from the data subjects without responding to that request, unless it has been otherwise authorized to do so; - -(e) to deal promptly and properly with all inquiries from the data exporter relating to its processing of the personal data subject to the transfer and to abide by the advice of the supervisory authority with regard to the processing of the data transferred; - -(f) at the request of the data exporter to submit its data processing facilities for audit of the processing activities covered by the Clauses which shall be carried out by the data exporter or an inspection body composed of independent members and in possession of the required professional qualifications bound by a duty of confidentiality, selected by the data exporter, where applicable, in agreement with the supervisory authority; - -(g) to make available to the data subject upon request a copy of the Clauses, or any existing contract for subprocessing, unless the Clauses or contract contain commercial information, in which case it may remove such commercial information, with the exception of Appendix 2 which shall be replaced by a summary description of the security measures in those cases where the data subject is unable to obtain a copy from the data exporter; - -(h) that, in the event of subprocessing, it has previously informed the data exporter and obtained its prior written consent; - -(i) that the processing services by the subprocessor will be carried out in accordance with Clause 11; and - -(j) to send promptly a copy of any subprocessor agreement it concludes under the Clauses to the data exporter. - -#### Clause 6: Liability -1. The parties agree that any data subject who has suffered damage as a result of any breach of the obligations referred to in Clause 3 or in Clause 11 by any party or subprocessor is entitled to receive compensation from the data exporter for the damage suffered. - -2. If a data subject is not able to bring a claim for compensation in accordance with paragraph 1 against the data exporter, arising out of a breach by the data importer or his subprocessor of any of their obligations referred to in Clause 3 or in Clause 11, because the data exporter has factually disappeared or ceased to exist in law or has become insolvent, the data importer agrees that the data subject may issue a claim against the data importer as if it were the data exporter, unless any successor entity has assumed the entire legal obligations of the data exporter by contract of by operation of law, in which case the data subject can enforce its rights against such entity. -The data importer may not rely on a breach by a subprocessor of its obligations in order to avoid its own liabilities. - -3. If a data subject is not able to bring a claim against the data exporter or the data importer referred to in paragraphs 1 and 2, arising out of a breach by the subprocessor of any of their obligations referred to in Clause 3 or in Clause 11 because both the data exporter and the data importer have factually disappeared or ceased to exist in law or have become insolvent, the subprocessor agrees that the data subject may issue a claim against the data subprocessor with regard to its own processing operations under the Clauses as if it were the data exporter or the data importer, unless any successor entity has assumed the entire legal obligations of the data exporter or data importer by contract or by operation of law, in which case the data subject can enforce its rights against such entity. The liability of the subprocessor shall be limited to its own processing operations under the Clauses. - -#### Clause 7: Mediation and jurisdiction -1. The data importer agrees that if the data subject invokes against it third-party beneficiary rights and/or claims compensation for damages under the Clauses, the data importer will accept the decision of the data subject: - -(a) to refer the dispute to mediation, by an independent person or, where applicable, by the supervisory authority; - -(b) to refer the dispute to the courts in the Member State in which the data exporter is established. - -2. The parties agree that the choice made by the data subject will not prejudice its substantive or procedural rights to seek remedies in accordance with other provisions of national or international law. - -#### Clause 8: Cooperation with supervisory authorities -1. The data exporter agrees to deposit a copy of this contract with the supervisory authority if it so requests or if such deposit is required under the applicable data protection law. - -2. The parties agree that the supervisory authority has the right to conduct an audit of the data importer, and of any subprocessor, which has the same scope and is subject to the same conditions as would apply to an audit of the data exporter under the applicable data protection law. - -3. The data importer shall promptly inform the data exporter about the existence of legislation applicable to it or any subprocessor preventing the conduct of an audit of the data importer, or any subprocessor, pursuant to paragraph 2. In such a case the data exporter shall be entitled to take the measures foreseen in Clause 5(b). - -#### Clause 9: Governing Law. -The Clauses shall be governed by the law of the Member State in which the data exporter is established. - -#### Clause 10: Variation of the contract -The parties undertake not to vary or modify the Clauses. This does not preclude the parties from adding clauses on business related issues where required as long as they do not contradict the Clause. - -#### Clause 11: Subprocessing -1. The data importer shall not subcontract any of its processing operations performed on behalf of the data exporter under the Clauses without the prior written consent of the data exporter. Where the data importer subcontracts its obligations under the Clauses, with the consent of the data exporter, it shall do so only by way of a written agreement with the subprocessor which imposes the same obligations on the subprocessor as are imposed on the data importer under the Clauses. Where the subprocessor fails to fulfil its data protection obligations under such written agreement the data importer shall remain fully liable to the data exporter for the performance of the subprocessor's obligations under such agreement. - -2. The prior written contract between the data importer and the subprocessor shall also provide for a third-party beneficiary clause as laid down in Clause 3 for cases where the data subject is not able to bring the claim for compensation referred to in paragraph 1 of Clause 6 against the data exporter or the data importer because they have factually disappeared or have ceased to exist in law or have become insolvent and no successor entity has assumed the entire legal obligations of the data exporter or data importer by contract or by operation of law. Such third-party liability of the subprocessor shall be limited to its own processing operations under the Clauses. - -3. The provisions relating to data protection aspects for subprocessing of the contract referred to in paragraph 1 shall be governed by the law of the Member State in which the data exporter is established. - -4. The data exporter shall keep a list of subprocessing agreements concluded under the Clauses and notified by the data importer pursuant to Clause 5 (j), which shall be updated at least once a year. The list shall be available to the data exporter's data protection supervisory authority. - -#### Clause 12: Obligation after the termination of personal data processing services -1. The parties agree that on the termination of the provision of data processing services, the data importer and the subprocessor shall, at the choice of the data exporter, return all the personal data transferred and the copies thereof to the data exporter or shall destroy all the personal data and certify to the data exporter that it has done so, unless legislation imposed upon the data importer prevents it from returning or destroying all or part of the personal data transferred. In that case, the data importer warrants that it will guarantee the confidentiality of the personal data transferred and will not actively process the personal data transferred anymore. - -2. The data importer and the subprocessor warrant that upon request of the data exporter and/or of the supervisory authority, it will submit its data processing facilities for an audit of the measures referred to in paragraph 1. - -### Appendix 1 to the Standard Contractual Clauses -Data exporter: Customer is the data exporter. - -**Data importer:** The data importer is GitHub, Inc., a global producer of software and services. - -**Data subjects:** Data subjects include the data exporter’s representatives and end-users including employees, contractors, collaborators, and customers of the data exporter. Data subjects may also include individuals attempting to communicate or transfer personal information to users of the services provided by data importer. GitHub acknowledges that, depending on Customer’s use of the Service, Customer may elect to include personal data from any of the following types of data subjects in the Customer Personal Data: - -- Employees, contractors and temporary workers (current, former, prospective) of data exporter; -- Dependents of the above; -- Data exporter's collaborators/contact persons (natural persons) or employees, contractors or temporary workers of legal entity collaborators/contact persons (current, prospective, former); -- Users (e.g., customers, clients, patients, visitors, etc.) and other data subjects that are users of data exporter's services; -- Partners, stakeholders or individuals who actively collaborate, communicate or otherwise interact with employees of the data exporter and/or use communication tools such as apps and websites provided by the data exporter; -- Stakeholders or individuals who passively interact with data exporter (e.g., because they are the subject of an investigation, research or mentioned in documents or correspondence from or to the data exporter); or -- Professionals with professional privilege (e.g., doctors, lawyers, notaries, religious workers, etc.). - -**Categories of data:** The personal data transferred that is included in e-mail, documents and other data in an electronic form in the context of the Service. GitHub acknowledges that, depending on Customer’s use of the Service, Customer may elect to include personal data from any of the following categories in the Customer Personal Data: -- Authentication data (for example, username, email, password); -- Contact information (for example, email); -- Unique identification numbers and signatures (IP addresses, unique identifier in tracking cookies or similar technology). -- Other unique identifying information. Data subjects may include more data such as real names, avatar images, and other personal information; - -**Special categories of data (if appropriate):** The data importer does not intentionally collect or process any special categories of data in carrying out its services to the data exporter. - -However, because the data importer provides storage services and does not control the categories of data it stores, the data exporter may choose to transfer special categories of data. Consequently, the data exporter is solely responsible for ensuring that it complies with all obligations imposed by applicable laws and regulations relating to the collection and processing of any special categories of data, including obtaining the explicit consent of the data subject prior to processing sensitive personal data. - -**Processing operations:** The personal data transferred will be subject to the following basic processing activities: -GitHub uses personal data for the limited purposes set forth in the GitHub Privacy Statement, available at [https://docs.github.com/articles/github-privacy-statement](/articles/github-privacy-statement), and the “Data Processing” section of the DPA. -Subcontractors: In accordance with the DPA, the data importer may hire other companies to provide limited services on data importer’s behalf, such as providing customer support. Any such subcontractors will be permitted to obtain Customer Personal Data only to deliver the services the data importer has retained them to provide, and they are prohibited from using Customer Personal Data for any other purpose. - -### Appendix 2 to the Standard Contractual Clauses -Description of the technical and organizational security measures implemented by the data importer in accordance with Clauses 4(d) and 5(c): - -**1. Personnel.** Data importer’s personnel will not process Customer Personal Data without authorization. Personnel are obligated to maintain the confidentiality of any Customer Personal Data and this obligation continues even after their engagement ends. - -**2. Data Privacy Contact.** The data privacy officer of the data importer can be reached at the following address: -GitHub, Inc. -Attn: Privacy -88 Colin P. Kelly Jr. Street -San Francisco, CA 94107 USA - -**3. Technical and Organization Measures.** The data importer has implemented and will maintain appropriate technical and organizational measures, internal controls, and information security routines intended to protect Customer Personal Data against accidental loss, destruction, alteration, unauthorized disclosure or access or unlawful destruction. - -Signature of GitHub, Inc. appears below. - -Signing the Standard Contractual Clauses, Appendix 1 and Appendix 2 on behalf of the data importer - -![Screen Shot 2020-07-20 at 2 20 29 PM](/assets/images/help/site-policy/docusign-signature.png) - -Lynn Hashimoto, Head of Product & Regulatory Legal - -GitHub, Inc. diff --git a/content/github/site-policy/github-data-protection-agreement.md b/content/github/site-policy/github-data-protection-agreement.md new file mode 100644 index 0000000000..b43c064b24 --- /dev/null +++ b/content/github/site-policy/github-data-protection-agreement.md @@ -0,0 +1,1006 @@ +--- +title: GitHub Data Protection Agreement +redirect_from: + - /github/site-policy/github-data-protection-addendum + - /github/site-policy-deprecated/github-data-protection-addendum + - /github/site-policy/github-data-protection-agreement-non-enterprise-customers +versions: + fpt: '*' +--- + +## Introduction + +The parties agree that this GitHub Data Protection Agreement (“**DPA**”) sets forth their obligations with respect to the processing and security of Personal Data and, where explicitly stated in the DPA Terms, Customer Data in connection with the Online Services provided by GitHub, Inc. (“**GitHub**”). The DPA (including its Appendix and Attachments) is between GitHub and any customer receiving Online Services from GitHub based on the GitHub Customer Agreement (“**Customer**”), and is incorporated by reference into the GitHub Customer Agreement. + +In the event of any conflict or inconsistency between the DPA Terms and any other terms in the GitHub Customer Agreement, the DPA Terms will prevail. The provisions of the DPA Terms supersede any conflicting provisions of the GitHub Privacy Statement that otherwise may apply to processing of Personal Data. For clarity, the Standard Contractual Clauses prevail over any other term of the DPA Terms. + +### Applicable DPA Terms and Updates + +#### Limits on Updates + +When Customer renews or purchases a new subscription to an Online Service, the then-current DPA Terms will apply and will not change during the term of that new subscription for that Online Service. + +#### New Features, Supplements, or Related Software + +Notwithstanding the foregoing limits on updates, when GitHub introduces features, supplements or related software that are new (i.e., that were not previously included with the subscription), GitHub may provide terms or make updates to the DPA that apply to Customer’s use of those new features, supplements or related software. If those terms include any material adverse changes to the DPA Terms, GitHub will provide Customer a choice to use the new features, supplements, or related software, without loss of existing functionality of a generally available Online Service. If Customer does not use the new features, supplements, or related software, the corresponding new terms will not apply. + +#### Government Regulation and Requirements + +Notwithstanding the foregoing limits on updates, GitHub may modify or terminate an Online Service in any country or jurisdiction where there is any current or future government requirement or obligation that (1) subjects GitHub to any regulation or requirement not generally applicable to businesses operating there, (2) presents a hardship for GitHub to continue operating the Online Service without modification, and/or (3) causes +GitHub to believe the DPA Terms or the Online Service may conflict with any such requirement or obligation. + +### Electronic Notices + +GitHub may provide Customer with information and notices about Online Services electronically, including via email, or through a web site that GitHub identifies. Notice is given as of the date it is made available by GitHub. + +### Prior Versions + +The DPA Terms provide terms for Online Services that are currently available. For earlier versions of the DPA Terms, Customer may contact its reseller or GitHub Account Manager. + +## Definitions + +Capitalized terms used but not defined in this DPA will have the meanings provided in the GitHub Customer Agreement. The following defined terms are used in this DPA: + +“**CCPA**” means the California Consumer Privacy Act as set forth in Cal. Civ. Code §1798.100 et seq. and its implementing regulations. + +“**Customer Data**” means all data, including all text, sound, video, or image files, and software, that are provided to GitHub by, or on behalf of, Customer through use of the Online Service. + +“**Data Protection Requirements**” means the GDPR, Local EU/EEA Data Protection Laws, CCPA, and any applicable laws, regulations, and other legal requirements relating to (a) privacy and data security; and (b) the use, collection, retention, storage, security, disclosure, transfer, disposal, and other processing of any Personal Data. + +“**Diagnostic Data**” means data collected or obtained by GitHub from software that is locally installed by Customer in connection with the Online Service. Diagnostic Data may also be referred to as telemetry. Diagnostic Data does not include Customer Data, Service Generated Data, or Professional Services Data. + +“**DPA Terms**” means both the terms in this DPA and any Online Service-specific terms in the GitHub Customer Agreement that specifically supplement or modify the privacy and security terms in this DPA for a specific Online Service (or feature of an Online Service). In the event of any conflict or inconsistency between the DPA and such Online Service-specific terms, the Online Service-specific terms shall prevail as to the applicable Online Service (or feature of that Online Service). + +“**GDPR**” means Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation). In connection with the United Kingdom, “GDPR” means Regulation (EU) 2016/679 as transposed into national law of the United Kingdom by the UK European Union (Withdrawal) Act 2018 and amended by the UK Data Protection, Privacy and Electronic Communications (Amendments etc.) (EU Exit) Regulations 2019 (as may be amended from time to time). + +“**Local EU/EEA Data Protection Laws**” means any subordinate legislation and regulation implementing the GDPR. + +“**GDPR Related Terms**” means the terms in Attachment 3, under which GitHub makes binding commitments regarding its processing of Personal Data as required by Article 28 of the GDPR. + +“**GitHub Affiliate**” means any entity that directly or indirectly controls, is controlled by or is under common control with GitHub. + +“**GitHub Customer Agreement**” means the service or other agreement(s) entered into by Customer with GitHub for Online Services. + +“**GitHub Privacy Statement**” means the GitHub privacy statement available at https://docs.github.com/en/github/site-policy/github-privacy-statement. + +“**Online Service**” means any service or software provided by GitHub to Customer under the GitHub Customer Agreement agreed upon with Customer, including Previews, updates, patches, bug fixes, and technical support. + +“**Personal Data**” means any information relating to an identified or identifiable natural person. An identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person. + +“**Preview**” means Online Services provided for preview, evaluation, demonstration or trial purposes, or pre-release versions of the Online Services. + +“**Professional Services Data**” means all data, including all text, sound, video, image files or software, that are provided to GitHub, by or on behalf of a Customer (or that Customer authorizes GitHub to obtain from an Online Service) or otherwise obtained or processed by or on behalf of GitHub through an engagement with GitHub to obtain Professional Services. Professional Services Data includes Support Data. + +“**Service Generated Data**” means data generated or derived by GitHub through the operation of an Online Service. Service Generated Data does not include Customer Data, Diagnostic Data, or Professional Services Data. + +“**Standard Contractual Clauses**” means either of the following sets of Standard Contractual Clauses, as applicable in the individual case to the transfer of personal data according to the section of this DPA entitled “Data Transfers and Location” below: +- the Standard Contractual Clauses (MODULE TWO: Transfer controller to processor), dated 4 June 2021, for the transfer of personal data to third countries pursuant to Regulation (EU) 2016/679 of the European Parliament and of the Council, as described in Article 46 of the GDPR and approved by European Commission Implementing Decision (EU) 2021/91 (“Standard Contractual Clauses (EU/EEA)”). The Standard Contractual Clauses (EU/EEA) are set forth in Attachment 1. +- the Standard Contractual Clauses (Processors), dated 5 February 2010, for the transfer of personal data to processors established in third countries which do not ensure an adequate level of data protection, as described in Article 46 of the GDPR, approved by European Commission Decision 2010/87/EU and recognized by the regulatory or supervisory authorities of the United Kingdom for use in connection with data transfers from the United Kingdom (“Standard Contractual Clauses (UK)”). The Standard Contractual Clauses (UK) are set forth in Attachment 2. + +“**Subprocessor**” means other processors used by GitHub to process Personal Data on behalf of Customer in connection with the Online Services, as described in Article 28 of the GDPR. + +“**Support Data**” means all data, including all text, sound, video, image files, or software, that are provided to GitHub by or on behalf of Customer (or that Customer authorizes GitHub to obtain from an Online Service) through an engagement with GitHub to obtain technical support for Online Services covered under this agreement. Support Data is a subset of Professional Services Data. + +Lower case terms used but not defined in this DPA, such as “personal data breach”, “processing”, “controller”, “processor”, “profiling”, “personal data”, and “data subject” will have the same meaning as set forth in Article 4 of the GDPR, irrespective of whether GDPR applies. The terms “data importer” and “data exporter” have the meanings given in the Standard Contractual Clauses. + +For clarity, and as detailed above, data defined as Customer Data, Diagnostic Data, Service Generated Data, and Professional Services Data may contain Personal Data. For illustrative purposes, please see the chart inserted below: + +
personal_data_types
+ +Above is a visual representation of the data types defined in the DPA. All Personal Data is processed as a part of one of the other data types (all of which also include non-personal data). Support Data is a sub-set of Professional Services Data. Except where explicitly stated otherwise, the DPA Terms exclusively apply to Personal Data. + +## General Terms + +### Compliance with Laws + +GitHub will comply with all laws and regulations applicable to its provision of the Online Services, including security breach notification law and Data Protection Requirements. However, GitHub is not responsible for compliance with any laws or regulations applicable to Customer or Customer’s industry that are not generally applicable to information technology service providers. GitHub does not determine whether Customer Data includes information subject to any specific law or regulation. All Security Incidents are subject to the Security Incident Notification terms below. + +Customer must comply with all laws and regulations applicable to its use of Online Services, including laws related to biometric data, confidentiality of communications, and Data Protection Requirements. Customer is responsible for determining whether the Online Services are appropriate for storage and processing of information subject to any specific law or regulation and for using the Online Services in a manner consistent with Customer’s legal and regulatory obligations. Customer is responsible for responding to any request from a third party regarding Customer’s use of an Online Service, such as a request to take down content under the U.S. Digital Millennium Copyright Act or other applicable laws. + +## Data Protection + +Terms This section of the DPA includes the following subsections: +- Scope +- Nature of Data Processing; Ownership +- Disclosure of Processed Data +- Processing of Personal Data; GDPR +- Data Security +- Security Incident Notification +- Data Transfers and Location +- Data Retention and Deletion +- Processor Confidentiality Commitment +- Notice and Controls on Use of Subprocessors +- Educational Institutions +- CJIS Customer Agreement, HIPAA Business Associate, Biometric Data +- California Consumer Privacy Act (CCPA) +- How to Contact GitHub +- Appendix A – Security Measures + +### Scope + +The DPA Terms apply to all Online Services. + +Previews may employ lesser or different privacy and security measures than those typically present in the Online Services. Unless otherwise noted, Customer should not use Previews to process Personal Data or other data that is subject to legal or regulatory compliance requirements. The following terms in this DPA do not apply to Previews: Processing of Personal Data; GDPR, Data Security, and California Consumer Privacy Act. + +### Nature of Data Processing; Ownership + +Except as otherwise stated in the DPA Terms, GitHub will use and otherwise process Customer Data and Personal Data as described and subject to the limitations provided below (a) to provide Customer the Online Service in accordance with Customer’s documented instructions, and/or (b) for GitHub’s legitimate business operations incident to delivery of the Online Services to Customer. As between the parties, Customer retains all right, +title and interest in and to Customer Data. GitHub acquires no rights in Customer Data other than the rights Customer grants to GitHub in this section. This paragraph does not affect GitHub’s rights in software or services GitHub licenses to Customer. + +#### Processing to Provide Customer the Online Services + +For purposes of this DPA, “to provide” an Online Service consists of: +- Delivering functional capabilities as licensed, configured, and used by Customer and its users, including providing personalized user experiences; +- Troubleshooting (e.g., preventing, detecting, and repairing problems); and +- Ongoing improvement (e.g., installing the latest updates and making improvements to user productivity, reliability, efficacy, and security). + +When providing Online Services, GitHub will use or otherwise process Personal Data only on Customer’s behalf and in accordance with Customer’s documented instructions. + +#### Processing for GitHub’s Legitimate Business Operations + +For purposes of this DPA, “GitHub’s legitimate business operations” consist of the following, each as incident to delivery of the Online Services to Customer: (1) billing and account management; (2) compensation (e.g., calculating employee commissions and partner incentives); (3) internal reporting and business modeling (e.g., forecasting, revenue, capacity planning, product strategy); (4) combatting fraud, abuse, cybercrime, or cyber-attacks that may affect GitHub or Online Services; (5) improving the core functionality of accessibility, privacy or energy-efficiency; (6) financial reporting and compliance with legal obligations (subject to the limitations on disclosure of Processed Data outlined below); (7) the creation or management of end user accounts and profiles by GitHub for individual users of Customer (except where Customer creates, manages or otherwise controls such end user accounts or profiles itself); and (8) other purposes pertaining to Personal Data not provided by Customer for storage in GitHub repositories or in connection with Professional Services. + +When processing for GitHub’s legitimate business operations, GitHub will not use or otherwise process Personal Data for: (a) user profiling, (b) advertising or similar commercial purposes, (c) data selling or brokering, or (d) any other purpose, other than for the purposes set out in this section. + +### Disclosure of Processed Data + +GitHub will not disclose or provide access to any Processed Data except: (1) as Customer directs; (2) as described in this DPA; or (3) as required by law. For purposes of this section, “Processed Data” means: (a) Customer Data; (b) Personal Data and (c) any other data processed by GitHub in connection with the Online Service that is Customer’s confidential information under the GitHub Customer Agreement. All processing of Processed Data is subject to GitHub’s obligation of confidentiality under the GitHub Customer Agreement. + +GitHub will not disclose or provide access to any Processed Data to law enforcement unless required by law. If law enforcement contacts GitHub with a demand for Processed Data, GitHub will attempt to redirect the law enforcement agency to request that data directly from Customer. If compelled to disclose or provide access to any Processed Data to law enforcement, GitHub will promptly notify Customer and provide a copy of the demand, unless legally prohibited from doing so. + +Upon receipt of any other third-party request for Processed Data, GitHub will promptly notify Customer unless prohibited by law. GitHub will reject the request unless required by law to comply. If the request is valid, GitHub will attempt to redirect the third party to request the data directly from Customer. + +GitHub will not provide any third party: (a) direct, indirect, blanket, or unfettered access to Processed Data; (b) platform encryption keys used to secure Processed Data or the ability to break such encryption; or (c) access to Processed Data if GitHub is aware that the data is to be used for purposes other than those stated in the third party’s request. + +In support of the above, GitHub may provide Customer’s basic contact information to the third party. + +### Processing of Personal Data; GDPR + +All Personal Data processed by GitHub in connection with the Online Services is obtained as part of either Customer Data, Professional Services Data (including Support Data), Diagnostic Data, or Service Generated Data. Personal Data provided to GitHub by, or on behalf of, Customer through use of the Online Service is also Customer Data. Pseudonymized identifiers may be included in Diagnostic Data or Service Generated Data and are also Personal Data. Any Personal Data pseudonymized, or de-identified but not anonymized, or Personal Data derived from Personal Data is also Personal Data. + +To the extent GitHub is a processor or subprocessor of Personal Data subject to the GDPR, the GDPR Related Terms in Attachment 3 govern that processing and the parties also agree to the following terms in this sub-section (“Processing of Personal Data; GDPR”): + +#### Processor and Controller Roles and Responsibilities + +Customer and GitHub agree that Customer is the controller of Personal Data and GitHub is the processor of such data, except (a) when Customer acts as a processor of Personal Data, in which case GitHub is a subprocessor; or (b) as stated otherwise in the GitHub Customer Agreement or this DPA. When GitHub acts as the processor or subprocessor of Personal Data, it will process Personal Data only on Customer’s behalf and in accordance with documented instructions from Customer. Customer agrees that its GitHub Customer Agreement (including the DPA Terms and any applicable updates), along with the product documentation and Customer’s use and configuration of features in the Online Services, are Customer’s complete documented instructions to GitHub for the processing of Personal Data. Information on use and configuration of the Online Services can be found at https://docs.github.com or a successor location. Any additional or alternate instructions must be agreed to according to the process for amending Customer’s GitHub Customer Agreement. In any instance where the GDPR applies and Customer is a processor, Customer warrants to GitHub that Customer’s instructions, including appointment of GitHub as a processor or subprocessor, have been authorized by the relevant controller. + +To the extent GitHub uses or otherwise processes Personal Data subject to the GDPR for GitHub’s legitimate business operations incident to delivery of the Online Services to Customer, GitHub will comply with the obligations of an independent data controller under GDPR for such use. GitHub is accepting the added responsibilities of a data “controller” under the GDPR for processing in connection with its legitimate business operations to: (a) act consistent with regulatory requirements, to the extent required under the GDPR; and (b) provide increased transparency to Customers and confirm GitHub’s accountability for such processing. GitHub employs safeguards to protect Personal Data in processing, including those identified in this DPA and those contemplated in Article 6(4) of the GDPR. With respect to processing of Personal Data under this paragraph, GitHub makes the commitments set forth in the Standard Contractual Clauses set forth in Attachment 1 or Attachment 2 (as applicable); for those purposes, (i) any GitHub disclosure of Personal Data, as described in Annex III to Attachment 1 or Appendix 3 to Attachment 2 (as applicable), that has been transferred in connection with GitHub’s legitimate business operations is deemed a “Relevant Disclosure” and (ii) the commitments in Annex III to Attachment 1 or Appendix 3 to Attachment 2 (as applicable) apply to such Personal Data. + +#### Processing Details + +The parties acknowledge and agree that: + +- **Subject Matter**. The subject-matter of the processing is limited to Personal Data within the scope of the section of this DPA entitled “Nature of Data Processing; Ownership” above and the GDPR. +- **Duration of the Processing**. The duration of the processing shall be in accordance with Customer instructions and the terms of the DPA. +- **Nature and Purpose of the Processing**. The nature and purpose of the processing shall be to provide the Online Service pursuant to Customer’s GitHub Customer Agreement and for GitHub’s legitimate business operations incident to delivery of the Online Service to Customer (as further described in the section of this DPA entitled “Nature of Data Processing; Ownership” above). +- **Categories of Data**. The types of Personal Data processed by GitHub when providing the Online Service include: (i) Personal Data that Customer elects to include in Customer Data or Professional Services Data (including, without limitation, Support Data); and (ii) those expressly identified in Article 4 of the GDPR that may be contained in Diagnostic Data or Service Generated Data. The types of Personal Data that Customer elects to include in Customer Data or Professional Services Data (including, without limitation, Support Data) may be any categories of Personal Data identified in records maintained by Customer acting as controller pursuant to Article 30 of the GDPR, including the categories of Personal Data set forth in Annex I to Attachment 1 or Appendix 1 to Attachment 2 (as applicable). +- Data Subjects. The categories of data subjects are Customer’s representatives and end users, such as employees, contractors, collaborators, and customers, and may include any other categories of data subjects as identified in records maintained by Customer acting as controller pursuant to Article 30 of the GDPR, including the categories of data subjects set forth in Annex I to Attachment 1 or Appendix 1 to Attachment 2 (as applicable). + +#### Data Subject Rights; Assistance with Requests + +GitHub will make available to Customer, in a manner consistent with the functionality of the Online Service and GitHub’s role as a processor of Personal Data of data subjects, the ability to fulfill data subject requests to exercise their rights under the GDPR. If GitHub receives a request from Customer’s data subject to exercise one or more of its rights under the GDPR in connection with an Online Service for which GitHub is a data processor or subprocessor, GitHub will redirect the data subject to make its request directly to Customer. Customer will be responsible for responding to any such request including, where necessary, by using the functionality of the Online Service. GitHub shall comply with reasonable requests by Customer to assist with Customer’s response to such a data subject request. + +#### Records of Processing Activities + +To the extent the GDPR requires GitHub to collect and maintain records of certain information relating to Customer, Customer will, where requested, supply such information to GitHub and keep it accurate and up-to-date. GitHub may make any such information available to the supervisory authority if required by the GDPR. + +### Data Security + +GitHub will implement and maintain appropriate technical and organizational measures and security safeguards against accidental or unlawful destruction, or loss, alteration, unauthorized disclosure of or access to, Customer Data and Personal Data processed by GitHub on behalf and in accordance with the documented instructions of Customer in connection with the Online Services. GitHub will regularly monitor compliance with these measures and safeguards and will continue to take appropriate steps throughout the term of the GitHub Customer Agreement. Appendix A – Security Safeguards contains a description of the technical and organizational measures and security safeguards implemented by GitHub. + +Customer is solely responsible for making an independent determination as to whether the technical and organizational measures and security safeguards for an Online Service meet Customer’s requirements, including any of its security obligations under applicable Data Protection Requirements. Customer acknowledges and agrees that (taking into account the state of the art, the costs of implementation, and the nature, scope, context and purposes of the processing of its Customer Data and Personal Data as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons) the technical and organizational measures and security safeguards implemented and maintained by GitHub provide a level of security appropriate to the risk with respect to its Customer Data and Personal Data. Customer is responsible for implementing and maintaining privacy protections and security measures for components that Customer provides or controls. + +GitHub will provide security compliance reporting such as external SOC1, type 2 and SOC2, type2 audit reports upon Customer request. Customer agrees that any information and audit rights granted by the applicable Data Protection Requirements (including, where applicable, Article 28(3)(h) of the GDPR) will be satisfied by these compliance reports, and will otherwise only arise to the extent that GitHub's provision of a compliance report does not provide sufficient information, or to the extent that Customer must respond to a regulatory or supervisory authority audit or investigation. + +Should Customer be subject to a regulatory or supervisory authority audit or investigation or carry out an audit or investigation in response to a request by a regulatory or supervisory authority that requires participation from GitHub, and Customers’ obligations cannot reasonably be satisfied (where allowable by Customer’s regulators) through audit reports, documentation, or compliance information that GitHub makes generally available to its customers, then GitHub will promptly respond to Customer’s additional instructions and requests for information, in accordance with the following terms and conditions: + +- GitHub will provide access to relevant knowledgeable personnel, documentation, and application software. +- Customer and GitHub will mutually agree in a prior written agreement (email is acceptable) upon the scope, timing, duration, control and evidence requirements, provided that this requirement to agree will not permit GitHub to unreasonably delay its cooperation. +- Customer must ensure its regulator’s use of an independent, accredited third-party audit firm, during regular business hours, with reasonable advance written notice to GitHub, and subject to reasonable confidentiality procedures. Neither Customer, its regulators, nor its regulators’ delegates shall have access to any data from GitHub’s other customers or to GitHub systems or facilities not involved in the Online Services. +- Customer is responsible for all costs and fees related to GitHub’s cooperation with the regulatory audit of Customer, including all reasonable costs and fees for any and all time GitHub expends, in addition to the rates for services performed by GitHub. +- If the report generated from GitHub’s cooperation with the regulatory audit of Customer includes any findings pertaining to GitHub, +Customer will share such report, findings, and recommended actions with GitHub where allowed by Customer’s regulators. + +### Security Incident Notification + +If GitHub becomes aware of a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Customer Data or Personal Data processed by GitHub on behalf and in accordance with the documented instructions of Customer in connection with the Online Services (each a "Security Incident"), GitHub will promptly and without undue delay (1) notify Customer of the Security Incident; (2) investigate the Security Incident and provide Customer with detailed information about the Security Incident; (3) take reasonable steps to mitigate the effects and to minimize any damage resulting from the Security Incident. + +Notification(s) of Security Incidents will be delivered to one or more of Customer's administrators by any means GitHub selects, including via email. It is Customer's sole responsibility to ensure it maintains accurate contact information with GitHub and that Customer's administrators monitor for and respond to any notifications. Customer is solely responsible for complying with its obligations under incident notification laws applicable to Customer and fulfilling any third-party notification obligations related to any Security Incident. + +GitHub will make reasonable efforts to assist Customer in fulfilling Customer's obligation under GDPR Article 33 or other applicable law or regulations to notify the relevant regulatory or supervisory authority and individual data subjects about a Security Incident. + +GitHub’s notification of or response to a Security Incident under this section is not an acknowledgement by GitHub of any fault or liability with respect to the Security Incident. + +Customer must notify GitHub promptly about any possible misuse of its accounts or authentication credentials or any Security Incident related to an Online Service. + +### Data Transfers and Location + +Personal Data that GitHub processes on behalf and in accordance with the documented instructions of Customer in connection with the Online Services may not be transferred to, or stored and processed in a geographic location except in accordance with the DPA Terms and the safeguards provided below in this section. Taking into account such safeguards, Customer appoints GitHub to transfer Personal Data to the United States or any other country in which GitHub or its Subprocessors operate and to store and process Personal Data to provide the Online Services, except as may be described elsewhere in these DPA Terms. + +All transfers of Personal Data out of the European Union, European Economic Area, or Switzerland to provide the Online Services shall be governed by the Standard Contractual Clauses (EU/EEA) in Attachment 1. All transfers of Personal Data out of the United Kingdom to provide the Online Services shall be governed by the Standard Contractual Clauses (UK) in Attachment 2. For the purposes of the Standard Contractual Clauses (UK) in Attachment 2, references to the “European Union,” “EU,” “European Economic Area,” “EEA” or a “Member State” shall be interpreted to refer to the United Kingdom where reasonably necessary and appropriate to give full force and effect to the Standard Contractual Clauses (UK) with respect to transfers of Personal Data from the United Kingdom. This applies regardless of the fact that, effective January 31, 2020, the United Kingdom is no longer a Member State of the European Union or European Economic Area. + +GitHub will abide by the requirements of applicable European Union, European Economic Area, United Kingdom and Swiss data protection law, and other Data Protection Requirements, in each case regarding the transfer of Personal Data to recipients or jurisdictions outside such jurisdiction. All such transfers of Personal Data will, where applicable, be subject to appropriate safeguards as described in Article 46 of the GDPR and such transfers and safeguards will be documented according to Article 30(2) of the GDPR. + +Subject to the safeguards described above, GitHub may transfer, store and otherwise process Personal Data to or in jurisdictions and geographic locations worldwide as it, subject to its sole discretion, considers reasonably necessary in connection with the Online Services. + +### Data Retention and Deletion + +Upon Customer's reasonable request, unless prohibited by law, GitHub will return or destroy all Customer Data and Personal Data processed by GitHub on behalf and in accordance with the documented instructions of Customer in connection with the Online Services at all locations where it is stored within 30 days of the request, provided that it is no longer needed for providing the Online Services or the purposes for which a data subject had authorized the processing of their Personal Data. GitHub may retain Customer Data or Personal Data to the extent required by the applicable Data Protection Requirements or other applicable law, and only to the extent and for such period as required by the applicable Data Protection Requirements or other applicable law, provided that GitHub will ensure that the Customer Data or Personal Data is processed only as necessary for the purpose specified in the applicable Data Protection Requirements or other applicable law and no other purpose, and the Customer Data or Personal Data remains protected by the Applicable Data Protection Requirements or other applicable law. + +### Processor Confidentiality Commitment + +GitHub will ensure that its personnel engaged in the processing of Customer Data and Personal Data on behalf of Customer in connection with the Online Services (i) will process such data only on instructions from Customer or as described in this DPA, and (ii) will be obligated to maintain the confidentiality and security of such data even after their engagement ends. GitHub shall provide periodic and mandatory data privacy and security training and awareness to its employees with access to Customer Data and Personal Data in accordance with applicable Data Protection Requirements or other applicable law and industry standards. + +### Notice and Controls on Use of Subprocessors + +GitHub may hire Subprocessors to provide certain limited or ancillary services on its behalf. Customer consents to this engagement and to GitHub Affiliates as Subprocessors. The above authorizations will constitute Customer’s prior written consent to the subcontracting by GitHub of the processing of Personal Data if such consent is required under applicable law, the Standard Contractual Clauses or the GDPR Related Terms. + +GitHub is responsible for its Subprocessors’ compliance with GitHub’s obligations in this DPA. GitHub makes available information about Subprocessors on the GitHub website https://github.com/subprocessors (or a successor location). When engaging any Subprocessor, GitHub will ensure via a written contract that the Subprocessor may access and use Customer Data or Personal Data only to deliver the services GitHub has retained them to provide and is prohibited from using Customer Data or Personal Data for any other purpose. GitHub will ensure that Subprocessors are bound by written agreements that require them to provide at least the level of data protection required of GitHub by the DPA, including the limitations on disclosure of Personal Data. GitHub agrees to oversee the Subprocessors to ensure that these contractual obligations are met. + +From time to time, GitHub may engage new Subprocessors. GitHub will give Customer notice (by updating the website at https://github.com/github-subprocessors-list (or a successor location) and providing Customer with a mechanism to obtain notice of that update) of any new Subprocessor in advance of providing that Subprocessor with access to Customer Data. If GitHub engages a new Subprocessor for a new Online Service, GitHub will give Customer notice prior to availability of that Online Service. + +If Customer does not approve of a new Subprocessor, then Customer may terminate any subscription for the affected Online Service without penalty by providing, before the end of the relevant notice period, written notice of termination. Customer may also include an explanation of the grounds for non-approval together with the termination notice, in order to permit GitHub to re-evaluate any such new Subprocessor based on the applicable concerns. If the affected Online Service is part of a suite (or similar single purchase of services), then any termination will apply to the entire suite. After termination, GitHub will remove payment obligations for any subscriptions for the terminated Online Service from subsequent invoices to Customer or its reseller. + +### Educational Institutions +If Customer is an educational agency or institution subject to the regulations under the Family Educational Rights and Privacy Act, 20 U.S.C. § 1232g (FERPA), or similar state student or educational privacy laws (collectively “Educational Privacy Laws”), Customer shall not provide Personal Data covered by such Educational Privacy Laws to GitHub without obtaining GitHub’s prior, written and specific consent and entering into a separate agreement with GitHub governing the parties’ rights and obligations with respect to the processing of such Personal Data by GitHub in connection with the Online Services. + +Subject to the above, if Customer intends to provide to GitHub Personal Data covered by FERPA, the parties agree and acknowledge that, for the purposes of this DPA, GitHub is a “school official” with “legitimate educational interests” in the Personal Data, as those terms have been defined under FERPA and its implementing regulations. Customer understands that GitHub may possess limited or no contact information for Customer’s students and students’ parents. Consequently, Customer will be responsible for obtaining any student or parental consent for any end user’s use of the Online Services that may be required by applicable law and to convey notification on behalf of GitHub to students (or, with respect to a student under 18 years of age and not in attendance at a postsecondary institution, to the student’s parent) of any judicial order or lawfully-issued subpoena requiring the disclosure of Personal Data in GitHub’s possession as may be required under applicable law. + +### CJIS Customer Agreement, HIPAA Business Associate, Biometric Data + +Except with GitHub’s prior, written and specific consent, Customer shall not provide to GitHub any Personal Data + +- relating to criminal convictions and offenses or Personal Data collected or otherwise processed by Customer subject to or in connection with FBI +Criminal Justice Information Services or the related Security Policy. +- constituting protected health information governed by the privacy, security, and breach notification rules issued by the United States Department of Health and Human Services, Parts 160 and 164 of Title 45 of the Code of Federal Regulations, established pursuant to the Health Insurance Portability and Accountability Act of 1996 (Public Law 104-191) or by state health or medical privacy laws. +- collected as part of a clinical trial or other biomedical research study subject to, or conducted in accordance with, the Federal Policy for the Protection of Human Subjects (Common Rule). +- covered by state, federal or foreign biometric privacy laws or otherwise constituting biometric information including information on an individual’s physical, physiological, biological or behavioral characteristics or information derived from such information that is used or intended to be used, singly or in combination with each other or with other information, to establish individual identity. + +### California Consumer Privacy Act (CCPA) / California Privacy Rights Act (CPRA) + +If and to the extent GitHub is processing Personal Data on behalf and in accordance with the documented instructions of Customer within the scope of the CCPA, GitHub makes the following additional commitments to Customer. GitHub will process the Personal Data on behalf of Customer and will not + +- sell the Personal Data as the term “selling” is defined in the CCPA. - share, rent, release, disclose, disseminate, make available, transfer or otherwise communicate orally, in writing or by electronic or other means, the Personal Data to a third party for cross-context behavioral advertising, whether or not for monetary or other valuable consideration, including +transactions for cross-context behavioral advertising in which no money is exchanged. +- retain, use or disclose the Personal Data for any purpose other than for the business purposes specified in the DPA Terms and the GitHub Customer Agreement, including retaining, using or disclosing the Personal Data for a commercial purpose other than the business purposes specified in the DPA Terms or the GitHub Customer Agreement, or as otherwise permitted by the CCPA. +- retain, use or disclose the Personal Data outside of the direct business relationship with Customer. +- combine the Personal Data with personal information that it receives from or on behalf of a third party or collects from California residents, except that GitHub may combine Personal Data to perform any business purpose as permitted by the CCPA or any regulations adopted or issued under the CCPA. + +### How to Contact GitHub + +If Customer believes that GitHub is not adhering to its privacy or security commitments, Customer may contact customer support or use GitHub’s Privacy web form, located at https://support.github.com/contact/privacy. GitHub’s mailing address is: + +**GitHub Privacy**
+GitHub, Inc.
+88 Colin P. Kelly Jr. Street
+San Francisco, California 94107 USA
+ +GitHub B.V. is GitHub’s data protection representative for the European Economic Area. The privacy representative of GitHub B.V. can be reached at the following address: + +**GitHub B.V.**
+Vijzelstraat 68-72
+1017 HL Amsterdam
+The Netherlands
+ +

Appendix A – Security Safeguards

+ +GitHub has implemented and will maintain for Customer Data and Personal Data processed by GitHub on behalf and in accordance with the +documented instructions of Customer in connection with GitHub services the following technical and organizational measures and security +safeguards, which in conjunction with the security commitments in this DPA (including the GDPR Related Terms), are GitHub’s only responsibility +with respect to the security of that data: + +Domain | Practices +-------|---------| +Organization of Information Security | **Security Ownership**. GitHub has appointed one or more security officers responsible for coordinating and monitoring the security policies and procedures.

**Security Roles and Responsibilities**. GitHub personnel with access to Customer Data and Personal Data are subject to confidentiality obligations.

**Risk Management Program**. GitHub performs an annual risk assessment.
GitHub retains its security documents pursuant to its retention requirements after they are no longer in effect.

**Vendor Management**. GitHub has a vendor risk assessment process, vendor contract clauses and additional data protection agreements with vendors. +Asset Management | **Asset Inventory**. GitHub maintains an inventory of all media on which Customer Data and Personal Data is stored. Access to the inventories of such media is restricted to GitHub personnel authorized to have such access.

**Asset Handling**
- GitHub classifies Customer Data and Personal Data to help identify it and to allow for access to it to be appropriately restricted.
- GitHub communicates employee responsibility and accountability for data protection up to and including cause for termination.
GitHub personnel must obtain GitHub authorization prior to remotely accessing Customer Data and Personal Data or processing Customer Data and Personal Data outside GitHub’s facilities. +Human Resources Security | **Security Training**. GitHub requires all new hires to complete security and privacy awareness training as part of initial on-boarding. Participation in annual training is required for all employees to provide a baseline for security and privacy basics. +Physical and Environmental Security | **Physical Access to Facilities**. GitHub limits access to facilities where information systems that process Customer Data and Personal Data are located to identified authorized individuals.

**Physical Access to Components**. GitHub maintains records of the incoming and outgoing media containing Customer Data, including the kind of media, the authorized sender/recipients, date and time, the number of media and the types of Customer Data and Personal Data they contain.

**Protection from Disruptions**. GitHub uses a variety of industry standard systems to protect against loss of data due to power supply failure or line interference.

**Component Disposal**. GitHub uses industry standard processes to delete Customer Data and Personal Data when it is no longer needed. +Communications and Operations Management | **Operational Policy**. GitHub maintains security documents describing its security measures and the relevant procedures and responsibilities of its personnel who have access to Customer Data.

**Data Recovery Procedures**
- On an ongoing basis, but in no case less frequently than once a week (unless no Customer Data and Personal Data has been updated during that period), GitHub maintains multiple copies of Customer Data and Personal Data from which Customer Data and Personal Data can be recovered.
- GitHub stores copies of Customer Data and Personal Data and data recovery procedures in a different place from where the primary computer equipment processing the Customer Data and Personal Data is located.
- GitHub has specific procedures in place governing access to copies of Customer Data.
- GitHub logs data restoration efforts, including the person responsible, the description of the restored data and where applicable, the person responsible and which data (if any) had to be input manually in the data recovery process.

**Malicious Software**. GitHub has threat detection controls to help identify and respond to anomalous or suspicious access to Customer Data, including malicious software originating from public networks.

**Data Beyond Boundaries**
- GitHub encrypts, or enables Customer to encrypt, Customer Data and Personal Data that is transmitted over public networks.
- GitHub restricts access to Customer Data and Personal Data in media leaving its facilities.

**Event Logging**. GitHub logs, or enables Customer to log, access and use of information systems containing Customer Data, registering the access ID, time, authorization granted or denied, and relevant activity. +Access Control | **Access Policy**. GitHub maintains a record of security privileges of individuals having access to Customer Data.

**Access Authorization**
- GitHub maintains and updates a record of personnel authorized to access GitHub systems that contain Customer Data.
- GitHub identifies those personnel who may grant, alter or cancel authorized access to data and resources.
- GitHub ensures that where more than one individual has access to systems containing Customer Data, the individuals have separate identifiers/log-ins where technically and architecturally feasible, and commercially reasonable.

**Least Privilege**
- Technical support personnel are only permitted to have access to Customer Data and Personal Data when needed.
- GitHub restricts access to Customer Data and Personal Data to only those individuals who require such access to perform their job function. GitHub employees are only granted access to production systems based on their role within the organization.

**Integrity and Confidentiality**

- GitHub instructs GitHub personnel to disable administrative sessions when computers are left unattended.
- GitHub stores passwords such that they are encrypted or unintelligible while they are in force.

**Authentication**
- GitHub uses industry standard practices to identify and authenticate users who attempt to access information systems.
- Where authentication mechanisms are based solely on passwords, GitHub requires the password to be at least eight characters long.
- GitHub ensures that de-activated or expired employee identifiers are not granted to other individuals.
- GitHub monitors, or enables Customer to monitor, repeated attempts to gain access to the information system using an invalid password.
- GitHub maintains industry standard procedures to deactivate passwords that have been corrupted or inadvertently disclosed.
- GitHub uses industry standard password protection practices, including practices designed to maintain the confidentiality and integrity of passwords when they are assigned and distributed, and during storage.

**Network Design**. GitHub has controls to ensure no systems storing Customer Data and Personal Data are part of the same logical network used for GitHub business operations. +Information Security Incident Management | **Incident Response Process**
- GitHub maintains a record of security incidents with a description of the incidents, the time period, the consequences of the breach, the name of the reporter, and to whom the incident was reported, and details regarding the handling of the incident.
- In the event that GitHub Security confirms or reasonably suspects that a GitHub.com customer is affected by a data breach, we will notify the customer without undue delay
- GitHub tracks, or enables Customer to track, disclosures of Customer Data, including what data has been disclosed, to whom, and at what time.

**Service Monitoring**. GitHub employs a wide range of continuous monitoring solutions for preventing, detecting, and mitigating attacks to the site. +Business Continuity Management | - GitHub maintains emergency and contingency plans for the facilities in which GitHub information systems that process Customer Data and Personal Data are located.
- GitHub’s redundant storage and its procedures for recovering data are designed to attempt to reconstruct Customer Data and Personal Data in its original or last-replicated state from before the time it was lost or destroyed. + +

Attachment 1 - The Standard Contractual Clauses (EU/EEA)

+ +### Controller to Processor + +#### SECTION I + +##### Clause 1 + +**Purpose and scope** + +
    +
  1. The purpose of these standard contractual clauses is to ensure compliance with the requirements of Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data (General Data Protection Regulation) for the transfer of personal data to a third country.
    2. +
  2. The Parties: +
      +
    1. the natural or legal person(s), public authority/ies, agency/ies or other body/ies (hereinafter ‘entity/ies’) transferring the personal data, as listed in Annex I.A (hereinafter each ‘data exporter’), and
      2. +
    2. the entity/ies in a third country receiving the personal data from the data exporter, directly or indirectly via another entity also Party to these Clauses, as listed in Annex I.A (hereinafter each ‘data importer’)
      3. +
    + have agreed to these standard contractual clauses (hereinafter: ‘Clauses’).
    3. +
  3. These Clauses apply with respect to the transfer of personal data as specified in Annex I.B.
    4. +
  4. The Appendix to these Clauses containing the Annexes referred to therein forms an integral part of these Clauses.
    5. +
+ +##### Clause 2 + +**Effect and invariability of the Clauses** +
    +
  1. These Clauses set out appropriate safeguards, including enforceable data subject rights and effective legal remedies, pursuant to Article 46(1) and Article 46(2)(c) of Regulation (EU) 2016/679 and, with respect to data transfers from controllers to processors and/or processors to processors, standard contractual clauses pursuant to Article 28(7) of Regulation (EU) 2016/679, provided they are not modified, except to select the appropriate Module(s) or to add or update information in the Appendix. This does not prevent the Parties from including the standard contractual clauses laid down in these Clauses in a wider contract and/or to add other clauses or additional safeguards, provided that they do not contradict, directly or indirectly, these Clauses or prejudice the fundamental rights or freedoms of data subjects.
    2. +
  2. These Clauses are without prejudice to obligations to which the data exporter is subject by virtue of Regulation (EU) 2016/679.
    3. +
+ +##### Clause 3 + +**Third-party beneficiaries** + +
    +
  1. Data subjects may invoke and enforce these Clauses, as third-party beneficiaries, against the data exporter and/or data importer, with the following exceptions:
    2. +
      +
    1. Clause 1, Clause 2, Clause 3, Clause 6, Clause 7;
      2. +
    2. Clause 8.1(b), 8.9(a), (c), (d) and (e);
      3. +
    3. Clause 9(a), (c), (d) and (e);
      4. +
    4. Clause 12(a), (d) and (f);
      5. +
    5. Clause 13;
      6. +
    6. Clause 15.1(c), (d) and (e);
      7. +
    7. Clause 16(e);
      8. +
    8. Clause 18(a) and (b).
      9. +
    +
  2. Paragraph (a) is without prejudice to rights of data subjects under Regulation (EU) 2016/679.
    3. +
+ +##### Clause 4 + +**Interpretation** + +
    +
  1. Where these Clauses use terms that are defined in Regulation (EU) 2016/679, those terms shall have the same meaning as in that Regulation.
    2. +
  2. These Clauses shall be read and interpreted in the light of the provisions of Regulation (EU) 2016/679.
    3. +
  3. These Clauses shall not be interpreted in a way that conflicts with rights and obligations provided for in Regulation (EU) 2016/679.
    4. +
+ +##### Clause 5 + +**Hierarchy** + +In the event of a contradiction between these Clauses and the provisions of related agreements between the Parties, existing at the time these Clauses are agreed or entered into thereafter, these Clauses shall prevail. + +##### Clause 6 + +**Description of the transfer(s)** + +The details of the transfer(s), and in particular the categories of personal data that are transferred and the purpose(s) for which they are transferred, are specified in Annex I.B. + +##### Clause 7 + +**Docking clause** + +
    +
  1. An entity that is not a Party to these Clauses may, with the agreement of the Parties, accede to these Clauses at any time, either as a data exporter or as a data importer, by completing the Appendix and signing Annex I.A.
    2. +
  2. Once it has completed the Appendix and signed Annex I.A, the acceding entity shall become a Party to these Clauses and have the rights and obligations of a data exporter or data importer in accordance with its designation in Annex I.A.
    3. +
  3. The acceding entity shall have no rights or obligations arising under these Clauses from the period prior to becoming a Party.
    4. +
+ +#### SECTION II – OBLIGATIONS OF THE PARTIES + +##### Clause 8 + +**Data protection safeguards** + +The data exporter warrants that it has used reasonable efforts to determine that the data importer is able, through the implementation of appropriate technical and organisational measures, to satisfy its obligations under these Clauses. + +**8.1 Instructions** +
    +
  1. The data importer shall process the personal data only on documented instructions from the data exporter. The data exporter may give such instructions throughout the duration of the contract.
    2. +
  2. The data importer shall immediately inform the data exporter if it is unable to follow those instructions.
    3. +
+ + +**8.2 Purpose limitation** + +The data importer shall process the personal data only for the specific purpose(s) of the transfer, as set out in Annex I.B, unless on further instructions from the data exporter. + +**8.3 Transparency** + +On request, the data exporter shall make a copy of these Clauses, including the Appendix as completed by the Parties, available to the data subject free of charge. To the extent necessary to protect business secrets or other confidential information, including the measures described in Annex II and personal data, the data exporter may redact part of the text of the Appendix to these Clauses prior to sharing a copy, but shall provide a meaningful summary where the data subject would otherwise not be able to understand the its content or exercise his/her rights. On request, the Parties shall provide the data subject with the reasons for the redactions, to the extent possible without revealing the redacted information. This Clause is without prejudice to the obligations of the data exporter under Articles 13 and 14 of Regulation (EU) 2016/679. + +**8.4 Accuracy** + +If the data importer becomes aware that the personal data it has received is inaccurate, or has become outdated, it shall inform the data exporter without undue delay. In this case, the data importer shall cooperate with the data exporter to erase or rectify the data. + +**8.5 Duration of processing and erasure or return of data** + +Processing by the data importer shall only take place for the duration specified in Annex I.B. After the end of the provision of the processing services, the data importer shall, at the choice of the data exporter, delete all personal data processed on behalf of the data exporter and certify to the data exporter that it has done so, or return to the data exporter all personal data processed on its behalf and delete existing copies. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit return or deletion of the personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process it to the extent and for as long as required under that local law. This is without prejudice to Clause 14, in particular the requirement for the data importer under Clause 14(e) to notify the data exporter throughout the duration of the contract if it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under Clause 14(a). + +**8.6 Security of processing** + +
    +
  1. The data importer and, during transmission, also the data exporter shall implement appropriate technical and organisational measures to ensure the security of the data, including protection against a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access to that data (hereinafter ‘personal data breach’). In assessing the appropriate level of security, the Parties shall take due account of the state of the art, the costs of implementation, the nature, scope, context and purpose(s) of processing and the risks involved in the processing for the data subjects. The Parties shall in particular consider having recourse to encryption or pseudonymisation, including during transmission, where the purpose of processing can be fulfilled in that manner. In case of pseudonymisation, the additional information for attributing the personal data to a specific data subject shall, where possible, remain under the exclusive control of the data exporter. In complying with its obligations under this paragraph, the data importer shall at least implement the technical and organisational measures specified in Annex II. The data importer shall carry out regular checks to ensure that these measures continue to provide an appropriate level of security.
    2. +
  2. The data importer shall grant access to the personal data to members of its personnel only to the extent strictly necessary for the implementation, management and monitoring of the contract. It shall ensure that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.
    3. +
  3. In the event of a personal data breach concerning personal data processed by the data importer under these Clauses, the data importer shall take appropriate measures to address the breach, including measures to mitigate its adverse effects. The data importer shall also notify the data exporter without undue delay after having become aware of the breach. Such notification shall contain the details of a contact point where more information can be obtained, a description of the nature of the breach (including, where possible, categories and approximate number of data subjects and personal data records concerned), its likely consequences and the measures taken or proposed to address the breach including, where appropriate, measures to mitigate its possible adverse effects. Where, and in so far as, it is not possible to provide all information at the same time, the initial notification shall contain the information then available and further information shall, as it becomes available, subsequently be provided without undue delay.
    4. +
  4. The data importer shall cooperate with and assist the data exporter to enable the data exporter to comply with its obligations under Regulation (EU) 2016/679, in particular to notify the competent supervisory authority and the affected data subjects, taking into account the nature of processing and the information available to the data importer.
    5. +
+ +**8.7 Sensitive data** + +Where the transfer involves personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic data, or biometric data for the purpose of uniquely identifying a natural person, data concerning health or a person’s sex life or sexual orientation, or data relating to criminal convictions and offences (hereinafter ‘sensitive data’), the data importer shall apply the specific restrictions and/or additional safeguards described in Annex I.B. + +**8.8 Onward transfers** + +The data importer shall only disclose the personal data to a third party on documented instructions from the data exporter. In addition, the data may only be disclosed to a third party located outside the European Union (1) (in the same country as the data importer or in another third country, hereinafter ‘onward transfer’) if the third party is or agrees to be bound by these Clauses, under the appropriate Module, or if: + +
    +
  1. the onward transfer is to a country benefitting from an adequacy decision pursuant to Article 45 of Regulation (EU) 2016/679 that covers the onward transfer;
    2. +
  2. the third party otherwise ensures appropriate safeguards pursuant to Articles 46 or 47 Regulation of (EU) 2016/679 with respect to the processing in question;
    3. +
  3. the onward transfer is necessary for the establishment, exercise or defence of legal claims in the context of specific administrative, regulatory or judicial proceedings; or
    4. +
  4. the onward transfer is necessary in order to protect the vital interests of the data subject or of another natural person.

    5. + Any onward transfer is subject to compliance by the data importer with all the other safeguards under these Clauses, in particular purpose limitation. +
+ +**8.9 Documentation and compliance** + +
    +
  1. The data importer shall promptly and adequately deal with enquiries from the data exporter that relate to the processing under these Clauses.
    2. +
  2. The Parties shall be able to demonstrate compliance with these Clauses. In particular, the data importer shall keep appropriate documentation on the processing activities carried out on behalf of the data exporter.
    3. +
  3. The data importer shall make available to the data exporter all information necessary to demonstrate compliance with the obligations set out in these Clauses and at the data exporter’s request, allow for and contribute to audits of the processing activities covered by these Clauses, at reasonable intervals or if there are indications of non-compliance. In deciding on a review or audit, the data exporter may take into account relevant certifications held by the data importer.
    4. +
  4. The data exporter may choose to conduct the audit by itself or mandate an independent auditor. Audits may include inspections at the premises or physical facilities of the data importer and shall, where appropriate, be carried out with reasonable notice.
    5. +
  5. The Parties shall make the information referred to in paragraphs (b) and (c), including the results of any audits, available to the competent supervisory authority on request.
    6. +
+ + +##### Clause 9 + +**Use of sub-processors** + +
    +
  1. GENERAL WRITTEN AUTHORISATION The data importer has the data exporter’s general authorisation for the engagement of sub-processor(s) from an agreed list. The data importer shall specifically inform the data exporter in writing of any intended changes to that list through the addition or replacement of sub-processors at least 90 days in advance, thereby giving the data exporter sufficient time to be able to object to such changes prior to the engagement of the sub-processor(s). The data importer shall provide the data exporter with the information necessary to enable the data exporter to exercise its right to object.
    2. +
  2. Where the data importer engages a sub-processor to carry out specific processing activities (on behalf of the data exporter), it shall do so by way of a written contract that provides for, in substance, the same data protection obligations as those binding the data importer under these Clauses, including in terms of third-party beneficiary rights for data subjects.(2) The Parties agree that, by complying with this Clause, the data importer fulfils its obligations under Clause 8.8. The data importer shall ensure that the sub-processor complies with the obligations to which the data importer is subject pursuant to these Clauses.
    3. +
  3. The data importer shall provide, at the data exporter’s request, a copy of such a sub-processor agreement and any subsequent amendments to the data exporter. To the extent necessary to protect business secrets or other confidential information, including personal data, the data importer may redact the text of the agreement prior to sharing a copy.
    4. +
  4. The data importer shall remain fully responsible to the data exporter for the performance of the sub-processor’s obligations under its contract with the data importer. The data importer shall notify the data exporter of any failure by the sub-processor to fulfil its obligations under that contract.
    5. +
  5. The data importer shall agree a third-party beneficiary clause with the sub-processor whereby – in the event the data importer has factually disappeared, ceased to exist in law or has become insolvent – the data exporter shall have the right to terminate the sub-processor contract and to instruct the sub-processor to erase or return the personal data.
    6. +
+ +##### Clause 10 + +**Data subject rights** + +
    +
  1. The data importer shall promptly notify the data exporter of any request it has received from a data subject. It shall not respond to that request itself unless it has been authorised to do so by the data exporter.
    2. +
  2. The data importer shall assist the data exporter in fulfilling its obligations to respond to data subjects’ requests for the exercise of their rights under Regulation (EU) 2016/679. In this regard, the Parties shall set out in Annex II the appropriate technical and organisational measures, taking into account the nature of the processing, by which the assistance shall be provided, as well as the scope and the extent of the assistance required.
    3. +
  3. In fulfilling its obligations under paragraphs (a) and (b), the data importer shall comply with the instructions from the data exporter.
    4. +
+ +##### Clause 11 + +**Redress** + +
    +
  1. The data importer shall inform data subjects in a transparent and easily accessible format, through individual notice or on its website, of a contact point authorised to handle complaints. It shall deal promptly with any complaints it receives from a data subject.
    2. +
  2. In case of a dispute between a data subject and one of the Parties as regards compliance with these Clauses, that Party shall use its best efforts to resolve the issue amicably in a timely fashion. The Parties shall keep each other informed about such disputes and, where appropriate, cooperate in resolving them.
    3. +
  3. Where the data subject invokes a third-party beneficiary right pursuant to Clause 3, the data importer shall accept the decision of the data subject to:
    4. +
      +
    1. lodge a complaint with the supervisory authority in the Member State of his/her habitual residence or place of work, or the competent supervisory authority pursuant to Clause 13;
      2. +
    2. refer the dispute to the competent courts within the meaning of Clause 18.
      3. +
    +
  4. The Parties accept that the data subject may be represented by a not-for-profit body, organisation or association under the conditions set out in Article 80(1) of Regulation (EU) 2016/679.
    5. +
  5. The data importer shall abide by a decision that is binding under the applicable EU or Member State law.
    6. +
  6. The data importer agrees that the choice made by the data subject will not prejudice his/her substantive and procedural rights to seek remedies in accordance with applicable laws.
    7. +
+ +##### Clause 12 + +**Liability** + +
    +
  1. Each Party shall be liable to the other Party/ies for any damages it causes the other Party/ies by any breach of these Clauses.
    2. +
  2. The data importer shall be liable to the data subject, and the data subject shall be entitled to receive compensation, for any material or non-material damages the data importer or its sub-processor causes the data subject by breaching the third-party beneficiary rights under these Clauses.
    3. +
  3. Notwithstanding paragraph (b), the data exporter shall be liable to the data subject, and the data subject shall be entitled to receive compensation, for any material or non-material damages the data exporter or the data importer (or its sub-processor) causes the data subject by breaching the third-party beneficiary rights under these Clauses. This is without prejudice to the liability of the data exporter and, where the data exporter is a processor acting on behalf of a controller, to the liability of the controller under Regulation (EU) 2016/679 or Regulation (EU) 2018/1725, as applicable.
    4. +
  4. The Parties agree that if the data exporter is held liable under paragraph (c) for damages caused by the data importer (or its sub-processor), it shall be entitled to claim back from the data importer that part of the compensation corresponding to the data importer’s responsibility for the damage.
    5. +
  5. Where more than one Party is responsible for any damage caused to the data subject as a result of a breach of these Clauses, all responsible Parties shall be jointly and severally liable and the data subject is entitled to bring an action in court against any of these Parties.
    6. +
  6. The Parties agree that if one Party is held liable under paragraph (e), it shall be entitled to claim back from the other Party/ies that part of the compensation corresponding to its/their responsibility for the damage.
    7. +
  7. The data importer may not invoke the conduct of a sub-processor to avoid its own liability.
    8. +
+ +##### Clause 13 + +**Supervision** + +
    +
  1. [Where the data exporter is established in an EU Member State:] The supervisory authority with responsibility for ensuring compliance by the data exporter with Regulation (EU) 2016/679 as regards the data transfer, as indicated in Annex I.C, shall act as competent supervisory authority.

    + [Where the data exporter is not established in an EU Member State, but falls within the territorial scope of application of Regulation (EU) 2016/679 in accordance with its Article 3(2) and has appointed a representative pursuant to Article 27(1) of Regulation (EU) 2016/679:] The supervisory authority of the Member State in which the representative within the meaning of Article 27(1) of Regulation (EU) 2016/679 is established, as indicated in Annex I.C, shall act as competent supervisory authority.

    + [Where the data exporter is not established in an EU Member State, but falls within the territorial scope of application of Regulation (EU) 2016/679 in accordance with its Article 3(2) without however having to appoint a representative pursuant to Article 27(2) of Regulation (EU) 2016/679:] The supervisory authority of one of the Member States in which the data subjects whose personal data is transferred under these Clauses in relation to the offering of goods or services to them, or whose behaviour is monitored, are located, as indicated in Annex I.C, shall act as competent supervisory authority.

    2. +
  2. The data importer agrees to submit itself to the jurisdiction of and cooperate with the competent supervisory authority in any procedures aimed at ensuring compliance with these Clauses. In particular, the data importer agrees to respond to enquiries, submit to audits and comply with the measures adopted by the supervisory authority, including remedial and compensatory measures. It shall provide the supervisory authority with written confirmation that the necessary actions have been taken.
    3. +
+ +#### SECTION III – LOCAL LAWS AND OBLIGATIONS IN CASE OF ACCESS BY PUBLIC AUTHORITIES + +##### Clause 14 + +**Local laws and practices affecting compliance with the Clauses** + +
    +
  1. The Parties warrant that they have no reason to believe that the laws and practices in the third country of destination applicable to the processing of the personal data by the data importer, including any requirements to disclose personal data or measures authorising access by public authorities, prevent the data importer from fulfilling its obligations under these Clauses. This is based on the understanding that laws and practices that respect the essence of the fundamental rights and freedoms and do not exceed what is necessary and proportionate in a democratic society to safeguard one of the objectives listed in Article 23(1) of Regulation (EU) 2016/679, are not in contradiction with these Clauses.
    2. +
  2. The Parties declare that in providing the warranty in paragraph (a), they have taken due account in particular of the following elements:
    3. +
      +
    1. the specific circumstances of the transfer, including the length of the processing chain, the number of actors involved and the transmission channels used; intended onward transfers; the type of recipient; the purpose of processing; the categories and format of the transferred personal data; the economic sector in which the transfer occurs; the storage location of the data transferred;
      2. +
    2. the laws and practices of the third country of destination– including those requiring the disclosure of data to public authorities or authorising access by such authorities – relevant in light of the specific circumstances of the transfer, and the applicable limitations and safeguards (3);
      3. +
    3. any relevant contractual, technical or organisational safeguards put in place to supplement the safeguards under these Clauses, including measures applied during transmission and to the processing of the personal data in the country of destination.
      4. +
    +
  3. The data importer warrants that, in carrying out the assessment under paragraph (b), it has made its best efforts to provide the data exporter with relevant information and agrees that it will continue to cooperate with the data exporter in ensuring compliance with these Clauses.
    4. +
  4. The Parties agree to document the assessment under paragraph (b) and make it available to the competent supervisory authority on request.
    5. +
  5. The data importer agrees to notify the data exporter promptly if, after having agreed to these Clauses and for the duration of the contract, it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under paragraph (a), including following a change in the laws of the third country or a measure (such as a disclosure request) indicating an application of such laws in practice that is not in line with the requirements in paragraph (a).
    6. +
  6. Following a notification pursuant to paragraph (e), or if the data exporter otherwise has reason to believe that the data importer can no longer fulfil its obligations under these Clauses, the data exporter shall promptly identify appropriate measures (e.g. technical or organisational measures to ensure security and confidentiality) to be adopted by the data exporter and/or data importer to address the situation. The data exporter shall suspend the data transfer if it considers that no appropriate safeguards for such transfer can be ensured, or if instructed by the competent supervisory authority to do so. In this case, the data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses. If the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise. Where the contract is terminated pursuant to this Clause, Clause 16(d) and (e) shall apply.
    7. +
+ +##### Clause 15 + +**Obligations of the data importer in case of access by public authorities** + +**15.1 Notification** + +
    +
  1. The data importer agrees to notify the data exporter and, where possible, the data subject promptly (if necessary with the help of the data exporter) if it:
    2. +
      +
    1. receives a legally binding request from a public authority, including judicial authorities, under the laws of the country of destination for the disclosure of personal data transferred pursuant to these Clauses; such notification shall include information about the personal data requested, the requesting authority, the legal basis for the request and the response provided; or
      2. +
    2. becomes aware of any direct access by public authorities to personal data transferred pursuant to these Clauses in accordance with the laws of the country of destination; such notification shall include all information available to the importer.
      3. +
    +
  2. If the data importer is prohibited from notifying the data exporter and/or the data subject under the laws of the country of destination, the data importer agrees to use its best efforts to obtain a waiver of the prohibition, with a view to communicating as much information as possible, as soon as possible. The data importer agrees to document its best efforts in order to be able to demonstrate them on request of the data exporter.
    3. +
  3. Where permissible under the laws of the country of destination, the data importer agrees to provide the data exporter, at regular intervals for the duration of the contract, with as much relevant information as possible on the requests received (in particular, number of requests, type of data requested, requesting authority/ies, whether requests have been challenged and the outcome of such challenges, etc.).
    4. +
  4. The data importer agrees to preserve the information pursuant to paragraphs (a) to (c) for the duration of the contract and make it available to the competent supervisory authority on request.
    5. +
  5. Paragraphs (a) to (c) are without prejudice to the obligation of the data importer pursuant to Clause 14(e) and Clause 16 to inform the data exporter promptly where it is unable to comply with these Clauses.
    6. +
+ +**15.2 Review of legality and data minimisation** + +
    +
  1. The data importer agrees to review the legality of the request for disclosure, in particular whether it remains within the powers granted to the requesting public authority, and to challenge the request if, after careful assessment, it concludes that there are reasonable grounds to consider that the request is unlawful under the laws of the country of destination, applicable obligations under international law and principles of international comity. The data importer shall, under the same conditions, pursue possibilities of appeal. When challenging a request, the data importer shall seek interim measures with a view to suspending the effects of the request until the competent judicial authority has decided on its merits. It shall not disclose the personal data requested until required to do so under the applicable procedural rules. These requirements are without prejudice to the obligations of the data importer under Clause 14(e).
    2. +
  2. The data importer agrees to document its legal assessment and any challenge to the request for disclosure and, to the extent permissible under the laws of the country of destination, make the documentation available to the data exporter. It shall also make it available to the competent supervisory authority on request.
    3. +
  3. The data importer agrees to provide the minimum amount of information permissible when responding to a request for disclosure, based on a reasonable interpretation of the request.
    4. +
+ +#### SECTION IV – FINAL PROVISIONS + +##### Clause 16 + +**Non-compliance with the Clauses and termination** + +
    +
  1. The data importer shall promptly inform the data exporter if it is unable to comply with these Clauses, for whatever reason.
    2. +
  2. In the event that the data importer is in breach of these Clauses or unable to comply with these Clauses, the data exporter shall suspend the transfer of personal data to the data importer until compliance is again ensured or the contract is terminated. This is without prejudice to Clause 14(f).
    3. +
  3. The data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses, where:
    4. +
      +
    1. the data exporter has suspended the transfer of personal data to the data importer pursuant to paragraph (b) and compliance with these Clauses is not restored within a reasonable time and in any event within one month of suspension;
      2. +
    2. the data importer is in substantial or persistent breach of these Clauses; or
      3. +
    3. the data importer fails to comply with a binding decision of a competent court or supervisory authority regarding its obligations under these Clauses.
      4. +

    + In these cases, it shall inform the competent supervisory authority of such non-compliance. Where the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise. +
  4. Personal data that has been transferred prior to the termination of the contract pursuant to paragraph (c) shall at the choice of the data exporter immediately be returned to the data exporter or deleted in its entirety. The same shall apply to any copies of the data. The data importer shall certify the deletion of the data to the data exporter. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit the return or deletion of the transferred personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process the data to the extent and for as long as required under that local law.
    5. +
  5. Either Party may revoke its agreement to be bound by these Clauses where (i) the European Commission adopts a decision pursuant to Article 45(3) of Regulation (EU) 2016/679 that covers the transfer of personal data to which these Clauses apply; or (ii) Regulation (EU) 2016/679 becomes part of the legal framework of the country to which the personal data is transferred. This is without prejudice to other obligations applying to the processing in question under Regulation (EU) 2016/679.
    6. +
+ +##### Clause 17 + +**Governing law** + +These Clauses shall be governed by the law of one of the EU Member States, provided such law allows for third-party beneficiary rights. The Parties agree that this shall be the law of the Netherlands. + +##### Clause 18 + +**Choice of forum and jurisdiction** + +
    +
  1. Any dispute arising from these Clauses shall be resolved by the courts of an EU Member State.
    2. +
  2. The Parties agree that those shall be the courts of the Netherlands.
    3. +
  3. A data subject may also bring legal proceedings against the data exporter and/or data importer before the courts of the Member State in which he/she has his/her habitual residence.
    4. +
  4. The Parties agree to submit themselves to the jurisdiction of such courts.
    5. +
+ +## ANNEX I + +**to the Standard Contractual Clauses (EU/EEA)** + +### A. LIST OF PARTIES + +**Data exporter(s)**: Customer is the data exporter
+Name: see GitHub Customer Agreement
+Address: see GitHub Customer Agreement
+Contact person’s name, position and contact details: see GitHub Customer Agreement
+Activities relevant to the data transferred under these Clauses:
+The data exporter is a user of Online Services or Professional Services as defined in the DPA and GitHub Customer Agreement.
+Signature and date: see GitHub Customer Agreement (the DPA and the Standard Contractual Clauses (EU/EEA) are incorporated into the GitHub Customer Agreement
+Role (controller/processor): controller (unless otherwise agreed in the Customer Agreement).
+ +**Data importer(s)**:
+Name: GitHub, Inc.
+Address: 88 Colin P Kelly Jr St, San Francisco, CA 94107, USA
+Contact person’s name, position and contact details: Frances Wiet, Head of Privacy, fwiet@github.com
+Activities relevant to the data transferred under these Clauses:
+GitHub, Inc. is a global producer of software and services
+Signature and date: see GitHub Customer Agreement (the DPA and the Standard Contractual Clauses (EU/EEA) are incorporated into the GitHub Customer Agreement)
+Role (controller/processor): processor or, depending on the agreements set forth in the Customer Agreement, subprocessor. + +### B. DESCRIPTION OF TRANSFER + +_Categories of data subjects whose personal data is transferred:_ + +Data subjects include the data exporter’s representatives and end-users including employees, contractors, collaborators, and customers of the data exporter. Data subjects may also include individuals attempting to communicate or transfer personal data to users of the services provided by data importer. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following types of data subjects in the personal data: +- Employees, contractors and temporary workers (current, former, prospective) of data exporter; +- Data exporter's collaborators/contact persons (natural persons) or employees, contractors or temporary workers of legal entity collaborators/contact persons (current, prospective, former); +- Users and other data subjects that are users of data exporter's services; +- Partners, stakeholders or individuals who actively collaborate, communicate or otherwise interact with employees of the data exporter and/or use communication tools such as apps and websites provided by the data exporter. + +_Categories of personal data transferred:_ + +The personal data transferred that is included in e-mail, documents and other data in an electronic form in the context of the Online Services or Professional Services. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following categories in the personal data: +- Basic personal data (for example place of birth, street name and house number (address), postal code, city of residence, country of residence, mobile phone number, first name, last name, initials, email address, gender, date of birth); +- Authentication data (for example user name, password or PIN code, security question, audit trail); +- Contact information (for example addresses, email, phone numbers, social media identifiers; emergency contact details); +- Unique identification numbers and signatures (for example IP addresses, employee number, student number); +- Pseudonymous identifiers; +- Photos, video and audio; +- Internet activity (for example browsing history, search history, reading and viewing activities); +- Device identification (for example IMEI-number, SIM card number, MAC address); +- Profiling (for example based on observed criminal or anti-social behavior or pseudonymous profiles based on visited URLs, click streams, browsing logs, IP-addresses, domains, apps installed, or profiles based on marketing preferences); +- Special categories of data as voluntarily provided by data subjects (for example racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health, data concerning a natural person’s sex life or sexual orientation, or data relating to criminal convictions or offences); or +- Any other personal data identified in Article 4 of the GDPR. + +_**Sensitive data** transferred (if applicable) and applied restrictions or safeguards that fully take into consideration the nature of the data and the risks involved, such as for instance strict purpose limitation, access restrictions (including access only for staff having followed specialised training), keeping a record of access to the data, restrictions for onward transfers or additional security measures:_
+GitHub does not request or otherwise ask for sensitive data and receives such +data only if and when customers or data subjects decide to provide it. + +_**The frequency of the transfer** (e.g. whether the data is transferred on a one-off or continuous basis):_ + +Continuous as part of the Online Services or Professional Services. + +_**Nature of the processing:**_ + +The personal data transferred will be subject to the following basic processing activities: +
    +
  1. Duration and Object of Data Processing. The duration of data processing shall be for the term designated under the applicable GitHub Customer Agreement between data exporter and the data importer. The objective of the data processing is the performance of Online Services and Professional Services.
    2. +
  2. Personal Data Access. For the term designated under the applicable GitHub Customer Agreement, data importer will, at its election and as necessary under applicable law, either: (1) provide data exporter with the ability to correct, delete, or block personal data, or (2) make such corrections, deletions, or blockages on its behalf.
    3. +
  3. Data Exporter’s Instructions. For Online Services and Professional Services, data importer will only act upon data exporter’s instructions.
    4. +
+ +_Purpose(s) of the data transfer and further processing:_ + +The scope and purpose of processing personal data is described in the “Processing of Personal Data; GDPR” section of the DPA. The data importer operates a global network of data centers and management/support facilities, and processing may take place in any jurisdiction where data importer or its sub-processors operate such facilities in accordance with the “Security Practices and Policies” section of the DPA. + +_The period for which the personal data will be retained, or, if that is not possible, the criteria used to determine that period:_ + +Upon expiration or termination of data exporter’s use of Online Services or Professional Services, it may extract personal data and data importer will delete personal data, each in accordance with the DPA Terms applicable to the agreement. + +_For transfers to (sub-) processors, also specify subject matter, nature and duration of the processing:_ + +In accordance with the DPA, the data importer may hire other companies to provide limited services on data importer’s behalf, such as providing customer support. Any such subcontractors will be permitted to obtain personal data only to deliver the services the data importer has retained them to provide, and they are prohibited from using personal data for any other purpose. Unless a particular subcontractor is replaced ahead of time, the processing will be for the term designated under the applicable GitHub Customer Agreement between data exporter and data importer. + +### C. COMPETENT SUPERVISORY AUTHORITY + +_Identify the competent supervisory authority/ies in accordance with Clause 13:_ + +The supervisory authority with responsibility for ensuring compliance by the data exporter with Regulation (EU) 2016/679. +  +## ANNEX II + +**to the Standard Contractual Clauses (EU/EEA)** + +**TECHNICAL AND ORGANISATIONAL MEASURES INCLUDING TECHNICAL AND ORGANISATIONAL MEASURES TO ENSURE THE SECURITY OF THE DATA** + +_Description of the technical and organisational measures implemented by the data importer(s) (including any relevant certifications) to ensure an appropriate level of security, taking into account the nature, scope, context and purpose of the processing, and the risks for the rights and freedoms of natural persons._ + +
    +
  1. Data Security Certifications. Data importer holds the following data security certifications:
    2. +
      +
    • SOC 1, Type 2;
      • +
    • SOC 2, Type 2;
      • +
    • NIST, to the extent incorporated for FedRAMP Low-Impact / Tailored ATO.
      • +
    +
  2. Personnel. Data importer’s personnel will not process personal data without authorization. Personnel are obligated to maintain the confidentiality of any such personal data and this obligation continues even after their engagement ends.
    3. +
  3. Data Privacy Contact. The data privacy officer of the data importer can be reached at the following address:

    + GitHub, Inc.
    + Attn: Privacy
    + 88 Colin P. Kelly Jr. Street
    + San Francisco, California 94107 USA

    4. +
  4. Technical and Organization Measures. The data importer has implemented and will maintain appropriate technical and organizational measures, internal controls, and information security routines intended to protect personal data, as defined in the Security Practices and Policies section of the DPA, against accidental loss, destruction, or alteration; unauthorized disclosure or access; or unlawful destruction as follows: The technical and organizational measures, internal controls, and information security routines set forth in the Data Security section of the DPA are hereby incorporated into this Annex II to Attachment 1 by this reference and are binding on the data importer as if they were set forth in this Annex 2 to Attachment 1 in their entirety.
    5. +
+ +_For transfers to (sub-) processors, also describe the specific technical and organisational measures to be taken by the (sub-) processor to be able to provide assistance to the controller and, for transfers from a processor to a sub-processor, to the data exporter:_ + +**Vendor management program - third-party risk program** + +The data importer has a vendor risk assessment process, vendor contract clauses and additional data protection agreements with vendors. Vendors undergo reassessment when a new business use case is requested. The data importer’s vendor risk program is structured so all of data importer’s vendors' risk assessments are refreshed two years from the last review date. + +Vendors deemed high risk, such as data center providers or other vendors storing or processing data in scope for the data importer’s regulatory or contractual requirements, undergo reassessment annually. + +## ANNEX III + +**to the Standard Contractual Clauses (EU/EEA)** + +**Additional Safeguards Addendum** + +By this Additional Safeguards Addendum to Standard Contractual Clauses (EU/EEA) (this “Addendum”), GitHub, Inc. (“GitHub”) provides additional safeguards to Customer and additional redress to the data subjects to whom Customer’s personal data relates. + +This Addendum supplements and is made part of, but is not in variation or modification of, the Standard Contractual Clauses (EU/EEA). + +
    +
  1. Challenges to Orders. In addition to Clause 15.1 of the Standard Contractual Clauses (EU/EEA), in the event GitHub receives an order from any third party for compelled disclosure of any personal data that has been transferred under the Standard Contractual Clauses (EU/EEA), GitHub shall:
    2. +
      +
    1. use every reasonable effort to redirect the third party to request data directly from Customer;
      2. +
    2. promptly notify Customer, unless prohibited under the law applicable to the requesting third party, and, if prohibited from notifying Customer, use all lawful efforts to obtain the right to waive the prohibition in order to communicate as much information to Customer as soon as possible; and
      3. +
    3. use all lawful efforts to challenge the order for disclosure on the basis of any legal deficiencies under the laws of the requesting party or any relevant conflicts with the law of the European Union or applicable Member State law.
      4. +

    + For purpose of this section, lawful efforts do not include actions that would result in civil or criminal penalty such as contempt of court under the laws of the relevant jurisdiction. +
  2. Indemnification of Data Subjects. Subject to Sections 3 and 4, GitHub shall indemnify a data subject for any material or non-material damage to the data subject caused by GitHub’s disclosure of personal data of the data subject that has been transferred under the Standard Contractual Clauses (EU/EEA) in response to an order from a non-EU/EEA government body or law enforcement agency (a “Relevant Disclosure”). Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under this Section 2 to the extent the data subject has already received compensation for the same damage, whether from GitHub or otherwise.
    3. +
  3. Conditions of Indemnification. Indemnification under Section 2 is conditional upon the data subject establishing, to GitHub’s reasonable satisfaction, that:
    4. +
      +
    1. GitHub engaged in a Relevant Disclosure;
      2. +
    2. the Relevant Disclosure was the basis of an official proceeding by the non-EU/EEA government body or law enforcement agency against the data subject; and
      3. +
    3. the Relevant Disclosure directly caused the data subject to suffer material or non-material damage.
      4. +

    + The data subject bears the burden of proof with respect to conditions a. though c.
    + Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under Section 2 if GitHub establishes that the Relevant Disclosure did not violate its obligations under Chapter V of the GDPR.
    +
  4. Scope of Damages. Indemnification under Section 2 is limited to material and non-material damages as provided in the GDPR and excludes consequential damages and all other damages not resulting from GitHub’s infringement of the GDPR.
    5. +
  5. Exercise of Rights. Rights granted to data subjects under this Addendum may be enforced by the data subject against GitHub irrespective of any restriction in Clauses 3 or 12 of the Standard Contractual Clauses (EU/EEA). The data subject may only bring a claim under this Addendum on an individual basis, and not part of a class, collective, group or representative action. Rights granted to data subjects under this Addendum are personal to the data subject and may not be assigned.
    6. +
  6. Notice of Change. In addition to Clause 14 of the Standard Contractual Clauses (EU/EEA), GitHub agrees and warrants that it has no reason to believe that the legislation applicable to it or its sub-processors, including in any country to which personal data is transferred either by itself or through a sub-processor, prevents it from fulfilling the instructions received from the data exporter and its obligations under this Addendum or the Standard Contractual Clauses (EU/EEA) and that in the event of a change in this legislation which is likely to have a substantial adverse effect on the warranties and obligations provided by this Addendum or the Standard Contractual Clauses (EU/EEA), it will promptly notify the change to Customer as soon as it is aware, in which case Customer is entitled to suspend the transfer of data and/or terminate the contract.
    7. +
  7. Termination. This Addendum shall automatically terminate if the European Commission, a competent Member State supervisory authority, or an EU or competent Member State court approves a different lawful transfer mechanism that would be applicable to the data transfers covered by the Standard Contractual Clauses (EU/EEA) (and if such mechanism applies only to some of the data transfers, this Addendum will terminate only with respect to those transfers) and that does not require the additional safeguards set forth in this Addendum.
    8. +
+ +

Attachment 2 – The Standard Contractual Clauses (UK)

+ +Execution of the GitHub Customer Agreement by Customer includes execution of this Attachment 2, which is countersigned by GitHub, Inc. + +In countries where regulatory approval is required for use of the Standard Contractual Clauses, the Standard Contractual Clauses cannot be relied upon under European Commission 2010/87/EU (of February 2010) to legitimize export of data from the country, unless Customer has the required regulatory approval. + +Beginning May 25, 2018 and thereafter, references to various Articles from the Directive 95/46/EC in the Standard Contractual Clauses below will be treated as references to the relevant and appropriate Articles in the GDPR. + +For the purposes of Article 26(2) of Directive 95/46/EC for the transfer of personal data to processors established in third countries which do not ensure an adequate level of data protection, Customer (as data exporter) and GitHub, Inc. (as data importer, whose signature appears below), each a “party,” together “the parties,” have agreed on the following Contractual Clauses (the “Clauses” or “Standard Contractual Clauses”) in order to adduce adequate safeguards with respect to the protection of privacy and fundamental rights and freedoms of individuals for the transfer by the data exporter to the data importer of the personal data specified in Appendix 1. + +### Clause 1: Definitions + +
    +
  1. 'personal data', 'special categories of data', 'process/processing', 'controller', 'processor', 'data subject' and 'supervisory authority' shall have the same meaning as in Directive 95/46/EC of the European Parliament and of the Council of 24 October 1995 on the protection of individuals with regard to the processing of personal data and on the free movement of such data;
    2. +
  2. 'the data exporter' means the controller who transfers the personal data;
    3. +
  3. 'the data importer' means the processor who agrees to receive from the data exporter personal data intended for processing on his behalf after the transfer in accordance with his instructions and the terms of the Clauses and who is not subject to a third country's system ensuring adequate protection within the meaning of Article 25(1) of Directive 95/46/EC;
    4. +
  4. 'the subprocessor' means any processor engaged by the data importer or by any other subprocessor of the data importer who agrees to receive from the data importer or from any other subprocessor of the data importer personal data exclusively intended for processing activities to be carried out on behalf of the data exporter after the transfer in accordance with his instructions, the terms of the Clauses and the terms of the written subcontract;
    5. +
  5. 'the applicable data protection law' means the legislation protecting the fundamental rights and freedoms of individuals and, in particular, their right to privacy with respect to the processing of personal data applicable to a data controller in the Member State in which the data exporter is established;
    6. +
  6. 'technical and organisational security measures' means those measures aimed at protecting personal data against accidental or unlawful destruction or accidental loss, alteration, unauthorised disclosure or access, in particular where the processing involves the transmission of data over a network, and against all other unlawful forms of processing.
    7. +
+ +### Clause 2: Details of the transfer + +The details of the transfer and in particular the special categories of personal data where applicable are specified in Appendix 1 below which forms an integral part of the Clauses. + +### Clause 3: Third-party beneficiary clause + +
    +
  1. The data subject can enforce against the data exporter this Clause, Clause 4(b) to (i), Clause 5(a) to (e), and (g) to (j), Clause 6(1) and (2), Clause 7, Clause 8(2), and Clauses 9 to 12 as third-party beneficiary.
    2. +
  2. The data subject can enforce against the data importer this Clause, Clause 5(a) to (e) and (g), Clause 6, Clause 7, Clause 8(2), and Clauses 9 to 12, in cases where the data exporter has factually disappeared or has ceased to exist in law unless any successor entity has assumed the entire legal obligations of the data exporter by contract or by operation of law, as a result of which it takes on the rights and obligations of the data exporter, in which case the data subject can enforce them against such entity.
    3. +
  3. The data subject can enforce against the subprocessor this Clause, Clause 5(a) to (e) and (g), Clause 6, Clause 7, Clause 8(2), and Clauses 9 to 12, in cases where both the data exporter and the data importer have factually disappeared or ceased to exist in law or have become insolvent, unless any successor entity has assumed the entire legal obligations of the data exporter by contract or by operation of law as a result of which it takes on the rights and obligations of the data exporter, in which case the data subject can enforce them against such entity. Such third-party liability of the subprocessor shall be limited to its own processing operations under the Clauses.
    4. +
  4. The parties do not object to a data subject being represented by an association or other body if the data subject so expressly wishes and if permitted by national law.
    5. +
+ +### Clause 4: Obligations of the data exporter + +The data exporter agrees and warrants: + +
    +
  1. that the processing, including the transfer itself, of the personal data has been and will continue to be carried out in accordance with the relevant provisions of the applicable data protection law (and, where applicable, has been notified to the relevant authorities of the Member State where the data exporter is established) and does not violate the relevant provisions of that State;
    2. +
  2. that it has instructed and throughout the duration of the personal data processing services will instruct the data importer to process the personal data transferred only on the data exporter's behalf and in accordance with the applicable data protection law and the Clauses;
    3. +
  3. that the data importer will provide sufficient guarantees in respect of the technical and organisational security measures specified in Appendix 2 below;
    4. +
  4. that after assessment of the requirements of the applicable data protection law, the security measures are appropriate to protect personal data against accidental or unlawful destruction or accidental loss, alteration, unauthorised disclosure or access, in particular where the processing involves the transmission of data over a network, and against all other unlawful forms of processing, and that these measures ensure a level of security appropriate to the risks presented by the processing and the nature of the data to be protected having regard to the state of the art and the cost of their implementation;
    5. +
  5. that it will ensure compliance with the security measures;
    6. +
  6. that, if the transfer involves special categories of data, the data subject has been informed or will be informed before, or as soon as possible after, the transfer that its data could be transmitted to a third country not providing adequate protection within the meaning of Directive 95/46/EC;
    7. +
  7. to forward any notification received from the data importer or any subprocessor pursuant to Clause 5(b) and Clause 8(3) to the data protection supervisory authority if the data exporter decides to continue the transfer or to lift the suspension;
    8. +
  8. to make available to the data subjects upon request a copy of the Clauses, with the exception of Appendix 2, and a summary description of the security measures, as well as a copy of any contract for subprocessing services which has to be made in accordance with the Clauses, unless the Clauses or the contract contain commercial information, in which case it may remove such commercial information;
    9. +
  9. that, in the event of subprocessing, the processing activity is carried out in accordance with Clause 11 by a subprocessor providing at least the same level of protection for the personal data and the rights of data subject as the data importer under the Clauses; and
    10. +
  10. that it will ensure compliance with Clause 4(a) to (i).
    11. +
+ +### Clause 5: Obligations of the data importer + +The data importer agrees and warrants: + +
    +
  1. to process the personal data only on behalf of the data exporter and in compliance with its instructions and the Clauses; if it cannot provide such compliance for whatever reasons, it agrees to inform promptly the data exporter of its inability to comply, in which case the data exporter is entitled to suspend the transfer of data and/or terminate the contract;
    2. +
  2. that it has no reason to believe that the legislation applicable to it prevents it from fulfilling the instructions received from the data exporter and its obligations under the contract and that in the event of a change in this legislation which is likely to have a substantial adverse effect on the warranties and obligations provided by the Clauses, it will promptly notify the change to the data exporter as soon as it is aware, in which case the data exporter is entitled to suspend the transfer of data and/or terminate the contract;
    3. +
  3. that it has implemented the technical and organisational security measures specified in Appendix 2 before processing the personal data transferred;
    4. +
  4. that it will promptly notify the data exporter about:
    5. +
      +
    1. any legally binding request for disclosure of the personal data by a law enforcement authority unless otherwise prohibited, such as a prohibition under criminal law to preserve the confidentiality of a law enforcement investigation,
      2. +
    2. any accidental or unauthorised access, and
      3. +
    3. any request received directly from the data subjects without responding to that request, unless it has been otherwise authorised to do so;
      4. +
    + to deal promptly and properly with all inquiries from the data exporter relating to its processing of the personal data subject to the transfer and to abide by the advice of the supervisory authority with regard to the processing of the data transferred; + at the request of the data exporter to submit its data processing facilities for audit of the processing activities covered by the Clauses which shall be carried out by the data exporter or an inspection body composed of independent members and in possession of the required professional qualifications bound by a duty of confidentiality, selected by the data exporter, where applicable, in agreement with the supervisory authority; +
  5. to make available to the data subject upon request a copy of the Clauses, or any existing contract for subprocessing, unless the Clauses or contract contain commercial information, in which case it may remove such commercial information, with the exception of Appendix 2 which shall be replaced by a summary description of the security measures in those cases where the data subject is unable to obtain a copy from the data exporter;
    6. +
  6. that, in the event of subprocessing, it has previously informed the data exporter and obtained its prior written consent;
    7. +
  7. that the processing services by the subprocessor will be carried out in accordance with Clause 11; and
    8. +
  8. to send promptly a copy of any subprocessor agreement it concludes under the Clauses to the data exporter.
    9. +
+ +### Clause 6: Liability + +
    +
  1. The parties agree that any data subject who has suffered damage as a result of any breach of the obligations referred to in Clause 3 or in Clause 11 by any party or subprocessor is entitled to receive compensation from the data exporter for the damage suffered.
    2. + +
  2. If a data subject is not able to bring a claim for compensation in accordance with paragraph 1 against the data exporter, arising out of a breach by the data importer or his subprocessor of any of their obligations referred to in Clause 3 or in Clause 11, because the data exporter has factually disappeared or ceased to exist in law or has become insolvent, the data importer agrees that the data subject may issue a claim against the data importer as if it were the data exporter, unless any successor entity has assumed the entire legal obligations of the data exporter by contract of by operation of law, in which case the data subject can enforce its rights against such entity.

    + The data importer may not rely on a breach by a subprocessor of its obligations in order to avoid its own liabilities.
    3. + +
  3. If a data subject is not able to bring a claim against the data exporter or the data importer referred to in paragraphs 1 and 2, arising out of a breach by the subprocessor of any of their obligations referred to in Clause 3 or in Clause 11 because both the data exporter and the data importer have factually disappeared or ceased to exist in law or have become insolvent, the subprocessor agrees that the data subject may issue a claim against the data subprocessor with regard to its own processing operations under the Clauses as if it were the data exporter or the data importer, unless any successor entity has assumed the entire legal obligations of the data exporter or data importer by contract or by operation of law, in which case the data subject can enforce its rights against such entity. The liability of the subprocessor shall be limited to its own processing operations under the Clauses.
    4. +
+ +### Clause 7: Mediation and jurisdiction + +
    +
  1. The data importer agrees that if the data subject invokes against it third-party beneficiary rights and/or claims compensation for damages under the Clauses, the data importer will accept the decision of the data subject: +
      +
    1. to refer the dispute to mediation, by an independent person or, where applicable, by the supervisory authority; +
    2. to refer the dispute to the courts in the Member State in which the data exporter is established. +
    +
  2. The parties agree that the choice made by the data subject will not prejudice its substantive or procedural rights to seek remedies in accordance with other provisions of national or international law. +
+ +### Clause 8: Cooperation with supervisory authorities + +
    +
  1. The data exporter agrees to deposit a copy of this contract with the supervisory authority if it so requests or if such deposit is required under the applicable data protection law.
    2. + +
  2. The parties agree that the supervisory authority has the right to conduct an audit of the data importer, and of any subprocessor, which has the same scope and is subject to the same conditions as would apply to an audit of the data exporter under the applicable data protection law.
    3. + +
  3. The data importer shall promptly inform the data exporter about the existence of legislation applicable to it or any subprocessor preventing the conduct of an audit of the data importer, or any subprocessor, pursuant to paragraph 2. In such a case the data exporter shall be entitled to take the measures foreseen in Clause 5 (b).
    4. +
+ +### Clause 9: Governing Law. + +The Clauses shall be governed by the law of the Member State in which the data exporter is established. + +### Clause 10: Variation of the contract + +The parties undertake not to vary or modify the Clauses. This does not preclude the parties from adding clauses on business related issues where required as long as they do not contradict the Clause. + +### Clause 11: Subprocessing + +
    +
  1. The data importer shall not subcontract any of its processing operations performed on behalf of the data exporter under the Clauses without the prior written consent of the data exporter. Where the data importer subcontracts its obligations under the Clauses, with the consent of the data exporter, it shall do so only by way of a written agreement with the subprocessor which imposes the same obligations on the subprocessor as are imposed on the data importer under the Clauses. Where the subprocessor fails to fulfil its data protection obligations under such written agreement the data importer shall remain fully liable to the data exporter for the performance of the subprocessor's obligations under such agreement.
    2. + +
  2. The prior written contract between the data importer and the subprocessor shall also provide for a third-party beneficiary clause as laid down in Clause 3 for cases where the data subject is not able to bring the claim for compensation referred to in paragraph 1 of Clause 6 against the data exporter or the data importer because they have factually disappeared or have ceased to exist in law or have become insolvent and no successor entity has assumed the entire legal obligations of the data exporter or data importer by contract or by operation of law. Such third-party liability of the subprocessor shall be limited to its own processing operations under the Clauses.
    3. + +
  3. The provisions relating to data protection aspects for subprocessing of the contract referred to in paragraph 1 shall be governed by the law of the Member State in which the data exporter is established.
    4. + +
  4. The data exporter shall keep a list of subprocessing agreements concluded under the Clauses and notified by the data importer pursuant to Clause 5 (j), which shall be updated at least once a year. The list shall be available to the data exporter's data protection supervisory authority.
    5. +
+ +### Clause 12: Obligation after the termination of personal data processing services + +
    +
  1. The parties agree that on the termination of the provision of data processing services, the data importer and the subprocessor shall, at the choice of the data exporter, return all the personal data transferred and the copies thereof to the data exporter or shall destroy all the personal data and certify to the data exporter that it has done so, unless legislation imposed upon the data importer prevents it from returning or destroying all or part of the personal data transferred. In that case, the data importer warrants that it will guarantee the confidentiality of the personal data transferred and will not actively process the personal data transferred anymore.
    2. + +
  2. The data importer and the subprocessor warrant that upon request of the data exporter and/or of the supervisory authority, it will submit its data processing facilities for an audit of the measures referred to in paragraph 1.
    3. +
+ +### Appendix 1 to the Standard Contractual Clauses (UK) + +**Data exporter**: Customer is the data exporter. The data exporter is a user of Online Services or Professional Services as defined in the DPA and GitHub Customer Agreement. + +**Data importer**: The data importer is GitHub, Inc., a global producer of software and services. + +**Data subjects**: Data subjects include the data exporter’s representatives and end-users including employees, contractors, collaborators, and customers of the data exporter. Data subjects may also include individuals attempting to communicate or transfer personal data to users of the services provided by data importer. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following types of data subjects in the personal data: +- Employees, contractors and temporary workers (current, former, prospective) of data exporter; +- Data exporter's collaborators/contact persons (natural persons) or employees, contractors or temporary workers of legal entity collaborators/contact persons (current, prospective, former); +- Users and other data subjects that are users of data exporter's services; +- Partners, stakeholders or individuals who actively collaborate, communicate or otherwise interact with employees of the data exporter and/or use communication tools such as apps and websites provided by the data exporter. + +**Categories of data**: The personal data transferred that is included in e-mail, documents and other data in an electronic form in the context of the Online Services or Professional Services. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following categories in the personal data: +- Basic personal data (for example place of birth, street name and house number (address), postal code, city of residence, country of residence, mobile phone number, first name, last name, initials, email address, gender, date of birth); +- Authentication data (for example user name, password or PIN code, security question, audit trail); +- Contact information (for example addresses, email, phone numbers, social media identifiers; emergency contact details); +- Unique identification numbers and signatures (for example IP addresses, employee number, student number); +- Pseudonymous identifiers; +- Photos, video and audio; +- Internet activity (for example browsing history, search history, reading and viewing activities); +- Device identification (for example IMEI-number, SIM card number, MAC address); +- Profiling (for example based on observed criminal or anti-social behavior or pseudonymous profiles based on visited URLs, click streams, browsing logs, IP-addresses, domains, apps installed, or profiles based on marketing preferences); +- Special categories of data as voluntarily provided by data subjects (for example racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health, data concerning a natural person’s sex life or sexual orientation, or data relating to criminal convictions or offences); or +- Any other personal data identified in Article 4 of the GDPR. + +**Processing operations**: The personal data transferred will be subject to the following basic processing activities: + +
    +
  1. Duration and Object of Data Processing. The duration of data processing shall be for the term designated under the applicable GitHub Customer Agreement between data exporter and data importer. The objective of the data processing is the performance of Online Services and Professional Services.
    2. +
  2. Scope and Purpose of Data Processing. The scope and purpose of processing personal data is described in the “Processing of Personal Data; GDPR” section of the DPA. The data importer operates a global network of data centers and management/support facilities, and processing may take place in any jurisdiction where data importer or its sub-processors operate such facilities in accordance with the “Security Practices and Policies” section of the DPA.
    3. +
  3. Personal Data Access. For the term designated under the applicable GitHub Customer Agreement data importer will at its election and as necessary under applicable law, either: (1) provide data exporter with the ability to correct, delete, or block personal data, or (2) make such corrections, deletions, or blockages on its behalf.
    4. +
  4. Data Exporter’s Instructions. For Online Services and Professional Services, data importer will only act upon data exporter’s instructions as conveyed by GitHub.
    5. +
  5. Personal Data Deletion or Return. Upon expiration or termination of data exporter’s use of Online Services or Professional Services, it may extract personal data and data importer will delete personal data, each in accordance with the DPA Terms applicable to the agreement.
    6. +
+ +**Subcontractors**: In accordance with the DPA, the data importer may hire other companies to provide limited services on data importer’s behalf, such as providing customer support. Any such subcontractors will be permitted to obtain personal data only to deliver the services the data importer has retained them to provide, and they are prohibited from using personal data for any other purpose. + +### Appendix 2 to the Standard Contractual Clauses (UK) + +Description of the technical and organizational security measures implemented by the data importer in accordance with Clauses 4(d) and 5(c): + +
    +
  1. Personnel. Data importer’s personnel will not process personal data without authorization. Personnel are obligated to maintain the confidentiality of any such personal data and this obligation continues even after their engagement ends.
    2. + +
  2. Data Privacy Contact. The data privacy officer of the data importer can be reached at the following address:
    +GitHub, Inc.
    +Attn: Privacy
    +88 Colin P. Kelly Jr. Street
    +San Francisco, California 94107 USA
    3. + +
  3. Technical and Organization Measures. The data importer has implemented and will maintain appropriate technical and organizational measures, internal controls, and information security routines intended to protect personal data, as defined in the Security Practices and Policies section of the DPA, against accidental loss, destruction, or alteration; unauthorized disclosure or access; or unlawful destruction as follows: The technical and organizational measures, internal controls, and information security routines set forth in the Security Practices and Policies section of the DPA are hereby incorporated into this Appendix 2 by this reference and are binding on the data importer as if they were set forth in this Appendix 2 in their entirety.
    4. +
+ +### Appendix 3 to the Standard Contractual Clauses (UK) + +**Additional Safeguards Addendum** + +By this Additional Safeguards Addendum to Standard Contractual Clauses (UK) (this “Addendum”), GitHub, Inc. (“GitHub”) provides additional safeguards to Customer and additional redress to the data subjects to whom Customer’s personal data relates. + +This Addendum supplements and is made part of, but is not in variation or modification of, the Standard Contractual Clauses (UK). + +
    +
  1. Challenges to Orders. In addition to Clause 5(d)(i) of the Standard Contractual Clauses (UK), in the event GitHub receives an order from any third party for compelled disclosure of any personal data that has been transferred under the Standard Contractual Clauses (UK), GitHub shall:
    2. +
      +
    1. use every reasonable effort to redirect the third party to request data directly from Customer;
      2. +
    2. promptly notify Customer, unless prohibited under the law applicable to the requesting third party, and, if prohibited from notifying Customer, use all lawful efforts to obtain the right to waive the prohibition in order to communicate as much information to Customer as soon as possible; and
      3. +
    3. use all lawful efforts to challenge the order for disclosure on the basis of any legal deficiencies under the laws of the requesting party or any relevant conflicts with the law of the European Union or applicable Member State law.
      4. +

    + For purpose of this section, lawful efforts do not include actions that would result in civil or criminal penalty such as contempt of court under the laws of the relevant jurisdiction. +
  2. Indemnification of Data Subjects. Subject to Sections 3 and 4, GitHub shall indemnify a data subject for any material or non-material damage to the data subject caused by GitHub’s disclosure of personal data of the data subject that has been transferred under the Standard Contractual Clauses (UK) in response to an order from a non-EU/EEA government body or law enforcement agency (a “Relevant Disclosure”). Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under this Section 2 to the extent the data subject has already received compensation for the same damage, whether from GitHub or otherwise.
    3. +
  3. Conditions of Indemnification. Indemnification under Section 2 is conditional upon the data subject establishing, to GitHub’s reasonable satisfaction, that:
    4. +
      +
    1. GitHub engaged in a Relevant Disclosure;
      2. +
    2. the Relevant Disclosure was the basis of an official proceeding by the non-EU/EEA government body or law enforcement agency against the data subject; and
      3. +
    3. the Relevant Disclosure directly caused the data subject to suffer material or non-material damage.
      4. +

    + The data subject bears the burden of proof with respect to conditions a. though c.
    + Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under Section 2 if GitHub establishes that the Relevant Disclosure did not violate its obligations under Chapter V of the GDPR. +
  4. Scope of Damages. Indemnification under Section 2 is limited to material and non-material damages as provided in the GDPR and excludes consequential damages and all other damages not resulting from GitHub’s infringement of the GDPR.
    5. +
  5. Exercise of Rights. Rights granted to data subjects under this Addendum may be enforced by the data subject against GitHub irrespective of any restriction in Clauses 3 or 6 of the Standard Contractual Clauses (UK). The data subject may only bring a claim under this Addendum on an individual basis, and not part of a class, collective, group or representative action. Rights granted to data subjects under this Addendum are personal to the data subject and may not be assigned.
    6. +
  6. Notice of Change. In addition to Clause 5(b) of the Standard Contractual Clauses (UK), GitHub agrees and warrants that it has no reason to believe that the legislation applicable to it or its sub-processors, including in any country to which personal data is transferred either by itself or through a sub-processor, prevents it from fulfilling the instructions received from the data exporter and its obligations under this Addendum or the Standard Contractual Clauses (UK) and that in the event of a change in this legislation which is likely to have a substantial adverse effect on the warranties and obligations provided by this Addendum or the Standard Contractual Clauses (UK), it will promptly notify the change to Customer as soon as it is aware, in which case Customer is entitled to suspend the transfer of data and/or terminate the contract. +
  7. Termination. This Addendum shall automatically terminate if the European Commission, a competent Member State supervisory authority, or an EU or competent Member State court approves a different lawful transfer mechanism that would be applicable to the data transfers covered by the Standard Contractual Clauses (UK) (and if such mechanism applies only to some of the data transfers, this Addendum will terminate only with respect to those transfers) and that does not require the additional safeguards set forth in this Addendum.

    + Signing the Standard Contractual Clauses (UK), Appendix 1, Appendix 2 and +
+ +

Attachment 3 – European Union General Data Protection Regulation Terms

+ +GitHub makes the commitments in these GDPR Related Terms, to all customers effective May 25, 2018. These commitments are binding upon GitHub with regard to Customer regardless of (1) the version of the GitHub Customer Agreement and DPA that is otherwise applicable to any given Online Services subscription or (2) any other agreement that references this attachment. + +For purposes of these GDPR Related Terms, Customer and GitHub agree that Customer is the controller of Personal Data and GitHub is the processor of such data, except when Customer acts as a processor of Personal Data, in which case GitHub is a subprocessor. These GDPR Related Terms apply to the processing of Personal Data, within the scope of the GDPR, by GitHub on behalf of Customer. These GDPR Related Terms do not limit or reduce any data protection commitments GitHub makes to Customer in the GitHub Customer Agreement or other agreement between GitHub and Customer. These GDPR Related Terms do not apply where GitHub is a controller of Personal Data. + +**Relevant GDPR Obligations: Articles 28, 32, and 33** + +
    +
  1. GitHub shall not engage another processor without prior specific or general written authorisation of Customer. In the case of general written authorisation, GitHub shall inform Customer of any intended changes concerning the addition or replacement of other processors, thereby giving Customer the opportunity to object to such changes. (Article 28(2))
    2. +
  2. Processing by GitHub shall be governed by these GDPR Related Terms under European Union (hereafter “Union”) or Member State law and are binding on GitHub with regard to Customer. The subject-matter and duration of the processing, the nature and purpose of the processing, the type of Personal Data, the categories of data subjects and the obligations and rights of the Customer are set forth in the Customer’s licensing agreement, including these GDPR Related Terms. In particular, GitHub shall:
    3. +
      +
    1. process the Personal Data only on documented instructions from Customer, including with regard to transfers of Personal Data to a third country or an international organisation, unless required to do so by Union or Member State law to which GitHub is subject; in such a case, GitHub shall inform Customer of that legal requirement before processing, unless that law prohibits such information on important grounds of public interest;
      2. +
    2. ensure that persons authorised to process the Personal Data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality;
      3. +
    3. take all measures required pursuant to Article 32 of the GDPR;
      4. +
    4. respect the conditions referred to in paragraphs 1 and 3 for engaging another processor;
      5. +
    5. taking into account the nature of the processing, assist Customer by appropriate technical and organisational measures, insofar as this is possible, for the fulfilment of the Customer’s obligation to respond to requests for exercising the data subject's rights laid down in Chapter III of the GDPR;
      6. +
    6. assist Customer in ensuring compliance with the obligations pursuant to Articles 32 to 36 of the GDPR, taking into account the nature of processing and the information available to GitHub;
      7. +
    7. at the choice of Customer, delete or return all the Personal Data to Customer after the end of the provision of services relating to processing, and delete existing copies unless Union or Member State law requires storage of the Personal Data;
      8. +
    8. make available to Customer all information necessary to demonstrate compliance with the obligations laid down in Article 28 of the GDPR and allow for and contribute to audits, including inspections, conducted by Customer or another auditor mandated by Customer.
      9. +

    + GitHub shall immediately inform Customer if, in its opinion, an instruction infringes the GDPR or other Union or Member State data protection provisions. (Article 28(3))

    +
  3. Where GitHub engages another processor for carrying out specific processing activities on behalf of Customer, the same data protection obligations as set out in these GDPR Related Terms shall be imposed on that other processor by way of a contract or other legal act under Union or Member State law, in particular providing sufficient guarantees to implement appropriate technical and organisational measures in such a manner that the processing will meet the requirements of the GDPR. Where that other processor fails to fulfil its data protection obligations, GitHub shall remain fully liable to the Customer for the performance of that other processor's obligations. (Article 28(4))
    4. +
  4. Taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of processing as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons, Customer and GitHub shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, including inter alia as appropriate:
    5. +
      +
    1. the pseudonymisation and encryption of Personal Data;
      2. +
    2. the ability to ensure the ongoing confidentiality, integrity, availability and resilience of processing systems and services;
      3. +
    3. the ability to restore the availability and access to Personal Data in a timely manner in the event of a physical or technical incident; and
      4. +
    4. a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the processing. (Article 32(1))
      5. +
    +
  5. In assessing the appropriate level of security, account shall be taken of the risks that are presented by processing, in particular from accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to Personal Data transmitted, stored or otherwise processed (Article 32(2)).
    6. +
  6. Customer and GitHub shall take steps to ensure that any natural person acting under the authority of Customer or GitHub who has access to Personal Data does not process them except on instructions from Customer, unless he or she is required to do so by Union or Member State law (Article 32(4)).
    7. +
  7. GitHub shall notify Customer without undue delay after becoming aware of a Personal Data breach (Article 33(2)). Such notification will include that information a processor must provide to a controller under Article 33(3) to the extent such information is reasonably available to GitHub.
    8. +
+ +--------------- + +

(1) The Agreement on the European Economic Area (EEA Agreement) provides for the extension of the European Union’s internal market to the three EEA States Iceland, Liechtenstein and Norway. The Union data protection legislation, including Regulation (EU) 2016/679, is covered by the EEA Agreement and has been incorporated into Annex XI thereto. Therefore, any disclosure by the data importer to a third party located in the EEA does not qualify as an onward transfer for the purpose of these Clauses.

+ +

(2) This requirement may be satisfied by the sub-processor acceding to these Clauses under the appropriate Module, in accordance with Clause 7.

+ +

(3) As regards the impact of such laws and practices on compliance with these Clauses, different elements may be considered as part of an overall assessment. Such elements may include relevant and documented practical experience with prior instances of requests for disclosure from public authorities, or the absence of such requests, covering a sufficiently representative time-frame. This refers in particular to internal records or other documentation, drawn up on a continuous basis in accordance with due diligence and certified at senior management level, provided that this information can be lawfully shared with third parties. Where this practical experience is relied upon to conclude that the data importer will not be prevented from complying with these Clauses, it needs to be supported by other relevant, objective elements, and it is for the Parties to consider carefully whether these elements together carry sufficient weight, in terms of their reliability and representativeness, to support this conclusion. In particular, the Parties have to take into account whether their practical experience is corroborated and not contradicted by publicly available or otherwise accessible, reliable information on the existence or absence of requests within the same sector and/or the application of the law in practice, such as case law and reports by independent oversight bodies.

diff --git a/content/github/site-policy/index.md b/content/github/site-policy/index.md index b4ea2b422b..80677f1a31 100644 --- a/content/github/site-policy/index.md +++ b/content/github/site-policy/index.md @@ -12,7 +12,7 @@ children: - /github-terms-of-service - /github-corporate-terms-of-service - /github-privacy-statement - - /github-data-protection-agreement-non-enterprise-customers + - /github-data-protection-agreement - /global-privacy-practices - /github-sponsors-additional-terms - /github-codespaces-privacy-statement diff --git a/content/github/working-with-github-support/about-github-support.md b/content/github/working-with-github-support/about-github-support.md index e582c958d3..bdda57a3ff 100644 --- a/content/github/working-with-github-support/about-github-support.md +++ b/content/github/working-with-github-support/about-github-support.md @@ -25,6 +25,8 @@ To see if there are currently any incidents affecting services on {% data variab ## Contacting {% data variables.contact.github_support %} +{% data reusables.support.zendesk-deprecation %} + You can use the {% data variables.contact.community_support_forum %} to browse topics, ask questions, share solutions, and interact directly with {% data variables.contact.community_support %}. To report account, security, and abuse issues, or to receive assisted support for a paid account, visit the {% data variables.contact.contact_support_portal %}. If you are an administrator for {% data variables.product.prodname_ghe_server %} without a user account on {% data variables.product.prodname_dotcom_the_website %}, visit the {% data variables.contact.contact_enterprise_portal %}. Email communication from GitHub Support will always be sent from either a `github.com` or `githubsupport.com` address. diff --git a/content/github/working-with-github-support/github-enterprise-cloud-support.md b/content/github/working-with-github-support/github-enterprise-cloud-support.md index cfd4def75b..97283ac6e9 100644 --- a/content/github/working-with-github-support/github-enterprise-cloud-support.md +++ b/content/github/working-with-github-support/github-enterprise-cloud-support.md @@ -18,6 +18,8 @@ shortTitle: GitHub Enterprise Cloud {% endnote %} +{% data reusables.support.zendesk-deprecation %} + You can submit priority questions if you have purchased {% data variables.product.prodname_ghe_cloud %} or if you're a member, outside collaborator, or billing manager of a {% data variables.product.prodname_dotcom %} organization currently subscribed to {% data variables.product.prodname_ghe_cloud %}. Questions that qualify for priority responses: diff --git a/content/github/working-with-github-support/submitting-a-ticket.md b/content/github/working-with-github-support/submitting-a-ticket.md index 5c7f5ed94a..a93a38e1d1 100644 --- a/content/github/working-with-github-support/submitting-a-ticket.md +++ b/content/github/working-with-github-support/submitting-a-ticket.md @@ -35,6 +35,8 @@ If you do not have an enterprise account, please use the {% data variables.conta ## Submitting a ticket using the {% data variables.contact.enterprise_portal %} +{% data reusables.support.zendesk-deprecation %} + 1. Navigate to the {% data variables.contact.contact_enterprise_portal %}. 5. Click **Submit a Ticket** ![Submit a ticket to Enterprise Support team](/assets/images/enterprise/support/submit-ticket-button.png) diff --git a/content/graphql/guides/managing-enterprise-accounts.md b/content/graphql/guides/managing-enterprise-accounts.md index b8aba46a10..f2a8dc33f4 100644 --- a/content/graphql/guides/managing-enterprise-accounts.md +++ b/content/graphql/guides/managing-enterprise-accounts.md @@ -58,9 +58,9 @@ For some example queries, see "[An example query using the Enterprise Accounts A - `admin:enterprise` The enterprise account specific scopes are: - - `admin:enterprise`: Gives full control of enterprises (includes {% ifversion ghes > 3.2 or fpt or ghae %}`manage_runners:enteprise`, {% endif %}`manage_billing:enterprise` and `read:enterprise`) + - `admin:enterprise`: Gives full control of enterprises (includes {% ifversion ghes > 3.2 or fpt or ghae %}`manage_runners:enterprise`, {% endif %}`manage_billing:enterprise` and `read:enterprise`) - `manage_billing:enterprise`: Read and write enterprise billing data.{% ifversion ghes > 3.2 or fpt or ghae %} - - `manage_runners:enteprise`: Access to manage GitHub Actions enterprise runners and runner-groups.{% endif %} + - `manage_runners:enterprise`: Access to manage GitHub Actions enterprise runners and runner-groups.{% endif %} - `read:enterprise`: Read enterprise profile data. 4. Copy your personal access token and keep it in a secure place until you add it to your GraphQL client. diff --git a/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md b/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md index e5c6045f06..a5f19682e5 100644 --- a/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md +++ b/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md @@ -37,7 +37,7 @@ Alternatively, you can enable {% data variables.product.prodname_actions %} for {% endif %} -{% ifversion fpt or ghes > 2.22 or ghae-next %} +{% ifversion fpt or ghes > 2.22 or ghae %} ## Managing {% data variables.product.prodname_actions %} permissions for your organization diff --git a/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md b/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md index 334b5ceae4..0ea081a201 100644 --- a/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md +++ b/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md @@ -7,6 +7,9 @@ versions: topics: - Repositories shortTitle: Automated release notes +communityRedirect: + name: 'Provide GitHub Feedback' + href: 'https://github.com/github/feedback/discussions/categories/releases-feedback' --- {% note %} diff --git a/content/sponsors/index.md b/content/sponsors/index.md index 42452c00d0..ed045ea4db 100644 --- a/content/sponsors/index.md +++ b/content/sponsors/index.md @@ -28,6 +28,9 @@ featuredLinks: layout: product-landing versions: fpt: '*' +communityRedirect: + name: 'Provide GitHub Feedback' + href: 'https://github.com/github/feedback/discussions/categories/sponsors-feedback' children: - /getting-started-with-github-sponsors - /sponsoring-open-source-contributors diff --git a/contributing/content-markup-reference.md b/contributing/content-markup-reference.md index 15b0edeab4..ac1ce965c6 100644 --- a/contributing/content-markup-reference.md +++ b/contributing/content-markup-reference.md @@ -10,6 +10,8 @@ - [Usage](#usage-2) - [Operating system tags](#operating-system-tags) - [Usage](#usage-3) +- [Tool tags](#tool-tags) + - [Usage](#usage-4) - [Reusable and variable strings of text](#reusable-and-variable-strings-of-text) ## Writing in Markdown @@ -102,7 +104,7 @@ You can define a default platform in the frontmatter. For more information, see ## Tool tags -We occasionally need to write documentation for different tools (GitHub UI, GitHub CLI, GitHub Desktop, cURL). Each tool may require a different set of instructions. We use tool tags to demarcate information for each tool. +We occasionally need to write documentation for different tools (GitHub UI, GitHub CLI, GitHub Desktop, cURL, Codespaces, VS Code). Each tool may require a different set of instructions. We use tool tags to demarcate information for each tool. ### Usage @@ -138,6 +140,22 @@ These instructions are pertinent to cURL users. {% endcurl %} ``` +``` +{% codespaces %} + +These instructions are pertinent to Codespaces users. They are mostly used outside the Codespaces docset, when we want to refer to how to do something inside Codespaces. Otherwise `webui` or `vscode` may be used. + +{% endcodespaces %} +``` + +``` +{% vscode %} + +These instructions are pertinent to VS Code users. + +{% endvscode %} +``` + Unlike [operating system tags](#operating-system-tags), which will automatically add tabs to select the operating system at the top of the article, you must add `{% include tool-switcher %}` wherever you want to display tabs to select the tool. This allows you to display the tabs at the top of the article or immediately before a relevant section. You can define a default tool in the frontmatter. For more information, see the [content README](../content/README.md#defaulttool). diff --git a/data/learning-tracks/actions.yml b/data/learning-tracks/actions.yml index 5bcbf7bcdf..bd481b61ff 100644 --- a/data/learning-tracks/actions.yml +++ b/data/learning-tracks/actions.yml @@ -7,38 +7,35 @@ getting_started: - /actions/learn-github-actions/essential-features-of-github-actions - /actions/learn-github-actions/managing-complex-workflows - /actions/learn-github-actions/reusing-workflows - - /actions/learn-github-actions/security-hardening-for-github-actions + - /actions/security-guides/security-hardening-for-github-actions featured_track: true continuous_integration: title: 'Build and test code' description: 'You can create custom continuous integration (CI) workflows right in your repository.' guides: - - /actions/guides/about-continuous-integration - - /actions/guides/setting-up-continuous-integration-using-workflow-templates - - /actions/guides/about-service-containers - - /actions/guides/building-and-testing-nodejs - - /actions/guides/building-and-testing-powershell - - /actions/guides/building-and-testing-python - - /actions/guides/building-and-testing-ruby - - /actions/guides/building-and-testing-java-with-maven - - /actions/guides/building-and-testing-java-with-gradle - - /actions/guides/building-and-testing-java-with-ant + - /actions/automating-builds-and-tests/about-continuous-integration + - /actions/automating-builds-and-tests/building-and-testing-powershell + - /actions/automating-builds-and-tests/building-and-testing-ruby + - /actions/automating-builds-and-tests/building-and-testing-java-with-maven + - /actions/automating-builds-and-tests/building-and-testing-java-with-gradle + - /actions/automating-builds-and-tests/building-and-testing-java-with-ant + - /actions/automating-builds-and-tests/building-and-testing-swift continuous_deployment: title: 'Automate your deployments' description: 'Learn how to automate release publishing for your project with a custom continuous deployment (CD) workflow in {% data variables.product.prodname_actions %}.' guides: - - /actions/guides/about-packaging-with-github-actions - - /actions/guides/publishing-nodejs-packages - - /actions/guides/publishing-java-packages-with-maven - - /actions/guides/publishing-java-packages-with-gradle - - /actions/guides/publishing-docker-images + - /actions/publishing-packages/about-packaging-with-github-actions + - /actions/publishing-packages/publishing-nodejs-packages + - /actions/publishing-packages/publishing-java-packages-with-maven + - /actions/publishing-packages/publishing-java-packages-with-gradle + - /actions/publishing-packages/publishing-docker-images deploy_to_the_cloud: title: 'Deploy to the cloud' description: 'Learn how to use {% data variables.product.prodname_actions %} to build an application and deploy it to various cloud-based platforms.' guides: - - /actions/guides/deploying-to-amazon-elastic-container-service - - /actions/guides/deploying-to-azure-app-service - - /actions/guides/deploying-to-google-kubernetes-engine + - /actions/deployment/deploying-to-amazon-elastic-container-service + - /actions/deployment/deploying-to-azure-app-service + - /actions/deployment/deploying-to-google-kubernetes-engine hosting_your_own_runners: title: 'Host your own runners' description: 'You can create self-hosted runners to run workflows in a highly customizable environment.' @@ -55,7 +52,7 @@ create_actions: title: 'Create an action' description: 'Do you have an idea for a new action? Have you built something custom for your project? Learn how to build shareable actions and publish them to GitHub Marketplace.' guides: - - /actions/creating-actions/about-actions + - /actions/creating-actions/about-custom-actions - /actions/creating-actions/creating-a-docker-container-action - /actions/creating-actions/creating-a-javascript-action - /actions/creating-actions/creating-a-composite-action 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 bcbc025297..6d861afeb4 100644 --- a/data/reusables/secret-scanning/partner-secret-list-private-repo.md +++ b/data/reusables/secret-scanning/partner-secret-list-private-repo.md @@ -3,35 +3,48 @@ Provider | Supported secret | API slug {%- ifversion fpt or ghes > 2.22 or ghae %} Adafruit IO | Adafruit IO Key | adafruit_io_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} -Adobe | Adobe Device Token | adobe_device_token -Adobe | Adobe Service Token | adobe_service_token -Adobe | Adobe Short-Lived Access Token | adobe_short_lived_access_token +Adobe | Adobe Device Token | adobe_device_token{% endif %} +{%- ifversion fpt or ghes > 3.1 or ghae-next %} +Adobe | Adobe Service Token | adobe_service_token{% endif %} +{%- ifversion fpt or ghes > 3.1 or ghae-next %} +Adobe | Adobe Short-Lived Access Token | adobe_short_lived_access_token{% endif %} +{%- ifversion fpt or ghes > 3.1 or ghae-next %} Adobe | Adobe JSON Web Token | adobe_jwt{% endif %} {%- ifversion fpt or ghes > 2.22 or ghae %} -Alibaba Cloud | Alibaba Cloud Access Key ID | alibaba_cloud_access_key_id -Alibaba Cloud | Alibaba Cloud Access Key Secret | alibaba_cloud_access_key_secret -Amazon Web Services (AWS) | Amazon AWS Access Key ID | aws_access_key_id +Alibaba Cloud | Alibaba Cloud Access Key ID | alibaba_cloud_access_key_id{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} +Alibaba Cloud | Alibaba Cloud Access Key Secret | alibaba_cloud_access_key_secret{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} +Amazon Web Services (AWS) | Amazon AWS Access Key ID | aws_access_key_id{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Amazon Web Services (AWS) | Amazon AWS Secret Access Key | aws_secret_access_key{% endif %} {%- ifversion fpt or ghes > 3.2 %} -Amazon Web Services (AWS) | Amazon AWS Session Token | aws_session_token +Amazon Web Services (AWS) | Amazon AWS Session Token | aws_session_token{% endif %} +{%- ifversion fpt or ghes > 3.2 %} Amazon Web Services (AWS) | Amazon AWS Temporary Access Key ID | aws_temporary_access_key_id{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Asana | Asana Personal Access Token | asana_personal_access_token{% endif %} {%- ifversion fpt or ghes > 2.22 or ghae %} -Atlassian | Atlassian API Token | atlassian_api_token +Atlassian | Atlassian API Token | atlassian_api_token{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Atlassian | Atlassian JSON Web Token | atlassian_jwt{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Atlassian | Bitbucket Server Personal Access Token | bitbucket_server_personal_access_token{% endif %} {%- ifversion fpt or ghes > 2.22 or ghae %} -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 -Azure | Azure SQL Connection String | azure_sql_connection_string +Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} +Azure | Azure SAS Token | azure_sas_token{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} +Azure | Azure Service Management Certificate | azure_management_certificate{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} +Azure | Azure SQL Connection String | azure_sql_connection_string{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Azure | Azure Storage Account Key | azure_storage_account_key{% endif %} {%- ifversion fpt or ghes > 3.2 %} Beamer | Beamer API Key | beamer_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} -Checkout.com | Checkout.com Production Secret Key | checkout_production_secret_key +Checkout.com | Checkout.com Production Secret Key | checkout_production_secret_key{% endif %} +{%- ifversion fpt or ghes > 3.1 or ghae-next %} Checkout.com | Checkout.com Test Secret Key | checkout_test_secret_key{% endif %} {%- ifversion fpt or ghes > 2.22 or ghae %} Clojars | Clojars Deploy Token | clojars_deploy_token{% endif %} @@ -40,142 +53,204 @@ CloudBees CodeShip | CloudBees CodeShip Credential | codeship_credential{% endif {%- ifversion fpt or ghes > 3.2 %} Contentful | Contentful Personal Access Token | contentful_personal_access_token{% endif %} {%- ifversion fpt or ghes > 2.22 or ghae %} -Databricks | Databricks Access Token | databricks_access_token +Databricks | Databricks Access Token | databricks_access_token{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Discord | Discord Bot Token | discord_bot_token{% endif %} {%- ifversion fpt or ghes > 3.0 or ghae %} -Doppler | Doppler Personal Token | doppler_personal_token -Doppler | Doppler Service Token | doppler_service_token -Doppler | Doppler CLI Token | doppler_cli_token +Doppler | Doppler Personal Token | doppler_personal_token{% endif %} +{%- ifversion fpt or ghes > 3.0 or ghae %} +Doppler | Doppler Service Token | doppler_service_token{% endif %} +{%- ifversion fpt or ghes > 3.0 or ghae %} +Doppler | Doppler CLI Token | doppler_cli_token{% endif %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Doppler | Doppler SCIM Token | doppler_scim_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Doppler | Doppler Audit Token | doppler_audit_token{% endif %} {%- ifversion fpt or ghes > 2.22 or ghae %} -Dropbox | Dropbox Access Token | dropbox_access_token +Dropbox | Dropbox Access Token | dropbox_access_token{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Dropbox | Dropbox Short Lived Access Token | dropbox_short_lived_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} -Duffel | Duffel Live Access Token | duffel_live_access_token +Duffel | Duffel Live Access Token | duffel_live_access_token{% endif %} +{%- ifversion fpt or ghes > 3.1 or ghae-next %} Duffel | Duffel Test Access Token | duffel_test_access_token{% endif %} {%- ifversion fpt or ghes > 3.0 or ghae %} Dynatrace | Dynatrace Access Token | dynatrace_access_token{% endif %} {%- ifversion fpt or ghes > 2.22 or ghae %} Dynatrace | Dynatrace Internal Token | dynatrace_internal_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} -EasyPost | EasyPost Production API Key | easypost_production_api_key -EasyPost | EasyPost Test API Key | easypost_test_api_key -Facebook | Facebook Access Token | facebook_access_token +EasyPost | EasyPost Production API Key | easypost_production_api_key{% endif %} +{%- ifversion fpt or ghes > 3.1 or ghae-next %} +EasyPost | EasyPost Test API Key | easypost_test_api_key{% endif %} +{%- ifversion fpt or ghes > 3.1 or ghae-next %} +Facebook | Facebook Access Token | facebook_access_token{% endif %} +{%- ifversion fpt or ghes > 3.1 or ghae-next %} Fastly | Fastly API Token | fastly_api_token{% endif %} {%- ifversion fpt or ghes > 2.22 or ghae %} Finicity | Finicity App Key | finicity_app_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} -Flutterwave | Flutterwave Live API Secret Key | flutterwave_live_api_secret_key +Flutterwave | Flutterwave Live API Secret Key | flutterwave_live_api_secret_key{% endif %} +{%- ifversion fpt or ghes > 3.1 or ghae-next %} Flutterwave | Flutterwave Test API Secret Key | flutterwave_test_api_secret_key{% endif %} {%- ifversion fpt or ghes > 2.22 or ghae %} -Frame.io | Frame.io JSON Web Token | frameio_jwt +Frame.io | Frame.io JSON Web Token | frameio_jwt{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Frame.io| Frame.io Developer Token | frameio_developer_token{% endif %} {%- ifversion fpt or ghes > 3.2 %} FullStory | FullStory API Key | fullstory_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} -GitHub | GitHub Personal Access Token | github_personal_access_token -GitHub | GitHub OAuth Access Token | github_oauth_access_token -GitHub | GitHub Refresh Token | github_refresh_token +GitHub | GitHub Personal Access Token | github_personal_access_token{% endif %} +{%- ifversion fpt or ghes > 3.1 or ghae-next %} +GitHub | GitHub OAuth Access Token | github_oauth_access_token{% endif %} +{%- ifversion fpt or ghes > 3.1 or ghae-next %} +GitHub | GitHub Refresh Token | github_refresh_token{% endif %} +{%- ifversion fpt or ghes > 3.1 or ghae-next %} GitHub | GitHub App Installation Access Token | github_app_installation_access_token{% endif %} {%- ifversion fpt or ghes > 2.22 or ghae %} -GitHub | GitHub SSH Private Key | github_ssh_private_key -GoCardless | GoCardless Live Access Token | gocardless_live_access_token +GitHub | GitHub SSH Private Key | github_ssh_private_key{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} +GoCardless | GoCardless Live Access Token | gocardless_live_access_token{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} GoCardless | GoCardless Sandbox Access Token | gocardless_sandbox_access_token{% endif %} {%- ifversion fpt or ghes > 3.2 %} Google | Firebase Cloud Messaging Server Key | firebase_cloud_messaging_server_key{% endif %} {%- ifversion fpt or ghes > 2.22 or ghae %} -Google | Google API Key | google_api_key +Google | Google API Key | google_api_key{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Google | Google Cloud Private Key ID | google_cloud_private_key_id{% endif %} {%- ifversion fpt or ghes > 3.2 %} -Google | Google Cloud Storage Access Key Secret | google_cloud_storage_access_key_secret -Google | Google Cloud Storage Service Account Access Key ID | google_cloud_storage_service_account_access_key_id +Google | Google Cloud Storage Access Key Secret | google_cloud_storage_access_key_secret{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +Google | Google Cloud Storage Service Account Access Key ID | google_cloud_storage_service_account_access_key_id{% endif %} +{%- ifversion fpt or ghes > 3.2 %} Google | Google Cloud Storage User Access Key ID | google_cloud_storage_user_access_key_id{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Grafana | Grafana API Key | grafana_api_key{% endif %} {%- ifversion fpt or ghes > 2.22 or ghae %} -Hashicorp Terraform | Terraform Cloud / Enterprise API Token | terraform_api_token +Hashicorp Terraform | Terraform Cloud / Enterprise API Token | terraform_api_token{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Hubspot | Hubspot API Key | hubspot_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} -Intercom | Intercom Access Token | intercom_access_token -Ionic | Ionic Personal Access Token | ionic_personal_access_token +Intercom | Intercom Access Token | intercom_access_token{% endif %} +{%- ifversion fpt or ghes > 3.1 or ghae-next %} +Ionic | Ionic Personal Access Token | ionic_personal_access_token{% endif %} +{%- ifversion fpt or ghes > 3.1 or ghae-next %} Ionic | Ionic Refresh Token | ionic_refresh_token{% endif %} {%- ifversion fpt or ghes > 3.2 %} -JFrog | JFrog Platform Access Token | jfrog_platform_access_token +JFrog | JFrog Platform Access Token | jfrog_platform_access_token{% endif %} +{%- ifversion fpt or ghes > 3.2 %} JFrog | JFrog Platform API Key | jfrog_platform_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} -Linear | Linear API Key | linear_api_key -Linear | Linear OAuth Access Token | linear_oauth_access_token -Lob | Lob Live API Key | lob_live_api_key +Linear | Linear API Key | linear_api_key{% endif %} +{%- ifversion fpt or ghes > 3.1 or ghae-next %} +Linear | Linear OAuth Access Token | linear_oauth_access_token{% endif %} +{%- ifversion fpt or ghes > 3.1 or ghae-next %} +Lob | Lob Live API Key | lob_live_api_key{% endif %} +{%- ifversion fpt or ghes > 3.1 or ghae-next %} Lob | Lob Test API Key | lob_test_api_key{% endif %} {%- ifversion fpt or ghes > 2.22 or ghae %} -Mailchimp | Mailchimp API Key | mailchimp_api_key +Mailchimp | Mailchimp API Key | mailchimp_api_key{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Mailgun | Mailgun API Key | mailgun_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} MessageBird | MessageBird API Key | messagebird_api_key{% endif %} {%- ifversion fpt or ghes > 3.2 %} -New Relic | New Relic Personal API Key | new_relic_personal_api_key -New Relic | New Relic REST API Key | new_relic_rest_api_key -New Relic | New Relic Insights Query Key | new_relic_insights_query_key +New Relic | New Relic Personal API Key | new_relic_personal_api_key{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +New Relic | New Relic REST API Key | new_relic_rest_api_key{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +New Relic | New Relic Insights Query Key | new_relic_insights_query_key{% endif %} +{%- ifversion fpt or ghes > 3.2 %} New Relic | New Relic License Key | new_relic_license_key{% endif %} {%- ifversion fpt or ghes > 2.22 or ghae %} -npm | npm Access Token | npm_access_token +npm | npm Access Token | npm_access_token{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} NuGet | NuGet API Key | nuget_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} -Onfido | Onfido Live API Token | onfido_live_api_token -Onfido | Onfido Sandbox API Token | onfido_sandbox_api_token +Onfido | Onfido Live API Token | onfido_live_api_token{% endif %} +{%- ifversion fpt or ghes > 3.1 or ghae-next %} +Onfido | Onfido Sandbox API Token | onfido_sandbox_api_token{% endif %} +{%- ifversion fpt or ghes > 3.1 or ghae-next %} OpenAI | OpenAI API Key | openai_api_key{% endif %} {%- ifversion fpt or ghes > 2.22 or ghae %} Palantir | Palantir JSON Web Token | palantir_jwt{% endif %} {%- ifversion fpt or ghes > 3.2 %} -PlanetScale | PlanetScale Database Password | planetscale_database_password -PlanetScale | PlanetScale OAuth Token | planetscale_oauth_token -PlanetScale | PlanetScale Service Token | planetscale_service_token -Plivo | Plivo Auth ID | plivo_auth_id +PlanetScale | PlanetScale Database Password | planetscale_database_password{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +PlanetScale | PlanetScale OAuth Token | planetscale_oauth_token{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +PlanetScale | PlanetScale Service Token | planetscale_service_token{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +Plivo | Plivo Auth ID | plivo_auth_id{% endif %} +{%- ifversion fpt or ghes > 3.2 %} Plivo | Plivo Auth Token | plivo_auth_token{% endif %} {%- ifversion fpt or ghes > 2.22 or ghae %} -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 +Postman | Postman API Key | postman_api_key{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} +Proctorio | Proctorio Consumer Key | proctorio_consumer_key{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} +Proctorio | Proctorio Linkage Key | proctorio_linkage_key{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} +Proctorio | Proctorio Registration Key | proctorio_registration_key{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} +Proctorio | Proctorio Secret Key | proctorio_secret_key{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Pulumi | Pulumi Access Token | pulumi_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} -PyPI | PyPI API Token | pypi_api_token +PyPI | PyPI API Token | pypi_api_token{% endif %} +{%- ifversion fpt or ghes > 3.1 or ghae-next %} RubyGems | RubyGems API Key | rubygems_api_key{% endif %} {%- ifversion fpt or ghes > 2.22 or ghae %} -Samsara | Samsara API Token | samsara_api_token +Samsara | Samsara API Token | samsara_api_token{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Samsara | Samsara OAuth Access Token | samsara_oauth_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} SendGrid | SendGrid API Key | sendgrid_api_key{% endif %} {%- ifversion fpt or ghes > 3.2 %} -Sendinblue | Sendinblue API Key | sendinblue_api_key +Sendinblue | Sendinblue API Key | sendinblue_api_key{% endif %} +{%- ifversion fpt or ghes > 3.2 %} Sendinblue | Sendinblue SMTP Key | sendinblue_smtp_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} -Shippo | Shippo Live API Token | shippo_live_api_token +Shippo | Shippo Live API Token | shippo_live_api_token{% endif %} +{%- ifversion fpt or ghes > 3.1 or ghae-next %} Shippo | Shippo Test API Token | shippo_test_api_token{% endif %} {%- ifversion fpt or ghes > 2.22 or ghae %} -Shopify | Shopify App Shared Secret | shopify_app_shared_secret -Shopify | Shopify Access Token | shopify_access_token -Shopify | Shopify Custom App Access Token | shopify_custom_app_access_token -Shopify | Shopify Private App Password | shopify_private_app_password -Slack | Slack API Token | slack_api_token -Slack | Slack Incoming Webhook URL | slack_incoming_webhook_url -Slack | Slack Workflow Webhook URL | slack_workflow_webhook_url -SSLMate | SSLMate API Key | sslmate_api_key -SSLMate | SSLMate Cluster Secret | sslmate_cluster_secret +Shopify | Shopify App Shared Secret | shopify_app_shared_secret{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} +Shopify | Shopify Access Token | shopify_access_token{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} +Shopify | Shopify Custom App Access Token | shopify_custom_app_access_token{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} +Shopify | Shopify Private App Password | shopify_private_app_password{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} +Slack | Slack API Token | slack_api_token{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} +Slack | Slack Incoming Webhook URL | slack_incoming_webhook_url{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} +Slack | Slack Workflow Webhook URL | slack_workflow_webhook_url{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} +SSLMate | SSLMate API Key | sslmate_api_key{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} +SSLMate | SSLMate Cluster Secret | sslmate_cluster_secret{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Stripe | Stripe API Key | stripe_api_key{% endif %} {%- ifversion fpt or ghes > 3.0 or ghae %} -Stripe | Stripe Live API Secret Key | stripe_live_secret_key -Stripe | Stripe Test API Secret Key | stripe_test_secret_key -Stripe | Stripe Live API Restricted Key | stripe_live_restricted_key +Stripe | Stripe Live API Secret Key | stripe_live_secret_key{% endif %} +{%- ifversion fpt or ghes > 3.0 or ghae %} +Stripe | Stripe Test API Secret Key | stripe_test_secret_key{% endif %} +{%- ifversion fpt or ghes > 3.0 or ghae %} +Stripe | Stripe Live API Restricted Key | stripe_live_restricted_key{% endif %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Stripe | Stripe Test API Restricted Key | stripe_test_restricted_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} -Stripe | Stripe Webhook Signing Secret | stripe_webhook_signing_secret -Tableau | Tableau Personal Access Token | tableau_personal_access_token +Stripe | Stripe Webhook Signing Secret | stripe_webhook_signing_secret{% endif %} +{%- ifversion fpt or ghes > 3.1 or ghae-next %} +Tableau | Tableau Personal Access Token | tableau_personal_access_token{% endif %} +{%- ifversion fpt or ghes > 3.1 or ghae-next %} Telegram | Telegram Bot Token | telegram_bot_token{% endif %} {%- ifversion fpt or ghes > 2.22 or ghae %} -Tencent Cloud | Tencent Cloud Secret ID | tencent_cloud_secret_id -Twilio | Twilio Account String Identifier | twilio_account_sid +Tencent Cloud | Tencent Cloud Secret ID | tencent_cloud_secret_id{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} +Twilio | Twilio Account String Identifier | twilio_account_sid{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Twilio | Twilio API Key | twilio_api_key{% endif %} diff --git a/data/reusables/secret-scanning/partner-secret-list-public-repo.md b/data/reusables/secret-scanning/partner-secret-list-public-repo.md index 465e8b3f3b..3e4de636cd 100644 --- a/data/reusables/secret-scanning/partner-secret-list-public-repo.md +++ b/data/reusables/secret-scanning/partner-secret-list-public-repo.md @@ -35,6 +35,7 @@ Dynatrace | Dynatrace Internal Token Finicity | Finicity App Key Frame.io | Frame.io JSON Web Token Frame.io| Frame.io Developer Token +FullStory| FullStory API Key GitHub | GitHub Personal Access Token GitHub | GitHub OAuth Access Token GitHub | GitHub Refresh Token diff --git a/data/reusables/support/zendesk-deprecation.md b/data/reusables/support/zendesk-deprecation.md new file mode 100644 index 0000000000..8e23cb624f --- /dev/null +++ b/data/reusables/support/zendesk-deprecation.md @@ -0,0 +1,5 @@ +{% warning %} + +**Deprecation notice:** The legacy {% data variables.contact.contact_enterprise_portal %} will be deprecated on November 1, 2021. Any new requests should be submitted through the {% data variables.contact.contact_support_portal %}. For more information, see "[About the Support Portal](https://support.github.com/about-support-portal-enterprise)." + +{% endwarning %} \ No newline at end of file diff --git a/includes/tool-switcher.html b/includes/tool-switcher.html index 16dd691b57..d5b854f5d7 100644 --- a/includes/tool-switcher.html +++ b/includes/tool-switcher.html @@ -6,5 +6,6 @@ cURL Desktop Codespaces + Visual Studio Code
\ No newline at end of file diff --git a/lib/check-node-version.js b/lib/check-node-version.js index 0050ed6284..d473512e7f 100644 --- a/lib/check-node-version.js +++ b/lib/check-node-version.js @@ -7,7 +7,11 @@ const { engines } = packageFile /* istanbul ignore next */ if (!semver.satisfies(process.version, engines.node)) { - console.error(`\n\nYou're using Node.js ${process.version}, but ${engines.node} is required`) - console.error('Visit nodejs.org to download an installer for the latest LTS version.\n\n') + console.error( + `\n\nYou're using Node.js ${process.version.replace(/^v/, '')} but this project requires ${ + engines.node + }` + ) + console.error('Visit nodejs.org to download an installer that meets these requirements.\n\n') process.exit(1) } diff --git a/lib/frontmatter.js b/lib/frontmatter.js index edbdba439f..a364198df2 100644 --- a/lib/frontmatter.js +++ b/lib/frontmatter.js @@ -149,6 +149,13 @@ export const schema = { interactive: { type: 'boolean', }, + communityRedirect: { + type: 'object', + properties: { + name: 'string', + href: 'string', + }, + }, // Platform-specific content preference defaultPlatform: { type: 'string', @@ -157,7 +164,7 @@ export const schema = { // Tool-specific content preference defaultTool: { type: 'string', - enum: ['webui', 'cli', 'desktop', 'curl', 'codespaces'], + enum: ['webui', 'cli', 'desktop', 'curl', 'codespaces', 'vscode'], }, // Documentation contributed by a third party, such as a GitHub Partner contributor: { diff --git a/lib/liquid-tags/extended-markdown.js b/lib/liquid-tags/extended-markdown.js index 5252495b76..bda70d73fe 100644 --- a/lib/liquid-tags/extended-markdown.js +++ b/lib/liquid-tags/extended-markdown.js @@ -7,6 +7,7 @@ export const tags = { webui: '', curl: '', codespaces: '', + vscode: '', all: '', tip: 'border rounded-1 mb-4 p-3 color-border-info color-bg-info f5', note: 'border rounded-1 mb-4 p-3 color-border-info color-bg-info f5', diff --git a/lib/page.js b/lib/page.js index 966f854e6f..e47121741d 100644 --- a/lib/page.js +++ b/lib/page.js @@ -195,6 +195,19 @@ class Page { context.relativePath = this.relativePath const html = await renderContent(this.markdown, context) + // Adding communityRedirect for Discussions, Sponsors, and Codespaces - request from Product + if ( + this.parentProduct && + (this.parentProduct.id === 'discussions' || + this.parentProduct.id === 'sponsors' || + this.parentProduct.id === 'codespaces') + ) { + this.communityRedirect = { + name: 'Provide GitHub Feedback', + href: `https://github.com/github/feedback/discussions/categories/${this.parentProduct.id}-feedback`, + } + } + // product frontmatter may contain liquid if (this.product) { this.product = await renderContent(this.rawProduct, context) diff --git a/lib/rest/static/decorated/api.github.com.json b/lib/rest/static/decorated/api.github.com.json index ce792296b9..9333f5f0ec 100644 --- a/lib/rest/static/decorated/api.github.com.json +++ b/lib/rest/static/decorated/api.github.com.json @@ -34026,6 +34026,17 @@ "format": "date-time" }, "descriptionHTML": "" + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + }, + "descriptionHTML": "

If true pull requests are omitted from the response (empty array).

" } ], "x-codeSamples": [ @@ -34106,6 +34117,17 @@ "type": "integer" }, "descriptionHTML": "

The id of the workflow run.

" + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + }, + "descriptionHTML": "

If true pull requests are omitted from the response (empty array).

" } ], "x-codeSamples": [ @@ -34544,6 +34566,17 @@ "type": "integer" }, "descriptionHTML": "

The attempt number of the workflow run.

" + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + }, + "descriptionHTML": "

If true pull requests are omitted from the response (empty array).

" } ], "x-codeSamples": [ @@ -34592,6 +34625,121 @@ } ] }, + { + "verb": "get", + "requestPath": "/repos/{owner}/{repo}/actions/runs/{run_id}/attempts/{attempt_number}/jobs", + "serverUrl": "https://api.github.com", + "parameters": [ + { + "name": "owner", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "" + }, + { + "name": "repo", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "" + }, + { + "name": "run_id", + "description": "The id of the workflow run.", + "in": "path", + "required": true, + "schema": { + "type": "integer" + }, + "descriptionHTML": "

The id of the workflow run.

" + }, + { + "name": "attempt_number", + "description": "The attempt number of the workflow run.", + "in": "path", + "required": true, + "schema": { + "type": "integer" + }, + "descriptionHTML": "

The attempt number of the workflow run.

" + }, + { + "name": "per_page", + "description": "Results per page (max 100)", + "in": "query", + "schema": { + "type": "integer", + "default": 30 + }, + "descriptionHTML": "

Results per page (max 100)

" + }, + { + "name": "page", + "description": "Page number of the results to fetch.", + "in": "query", + "schema": { + "type": "integer", + "default": 1 + }, + "descriptionHTML": "

Page number of the results to fetch.

" + } + ], + "x-codeSamples": [ + { + "lang": "Shell", + "source": "curl \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n https://api.github.com/repos/octocat/hello-world/actions/runs/42/attempts/42/jobs", + "html": "
curl \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://api.github.com/repos/octocat/hello-world/actions/runs/42/attempts/42/jobs
" + }, + { + "lang": "JavaScript", + "source": "await octokit.request('GET /repos/{owner}/{repo}/actions/runs/{run_id}/attempts/{attempt_number}/jobs', {\n owner: 'octocat',\n repo: 'hello-world',\n run_id: 42,\n attempt_number: 42\n})", + "html": "
await octokit.request('GET /repos/{owner}/{repo}/actions/runs/{run_id}/attempts/{attempt_number}/jobs', {\n  owner: 'octocat',\n  repo: 'hello-world',\n  run_id: 42,\n  attempt_number: 42\n})\n
" + } + ], + "summary": "List jobs for a workflow run attempt", + "description": "Lists jobs for a specific workflow run attempt. Anyone with read access to the repository can use this endpoint. If the repository is private you must use an access token with the `repo` scope. GitHub Apps must have the `actions:read` permission to use this endpoint. You can use parameters to narrow the list of results. For more information about using parameters, see [Parameters](https://docs.github.com/rest/overview/resources-in-the-rest-api#parameters).", + "tags": [ + "actions" + ], + "operationId": "actions/list-jobs-for-workflow-run-attempt", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/rest/reference/actions#list-jobs-for-a-workflow-run-attempt" + }, + "x-github": { + "githubCloudOnly": false, + "enabledForGitHubApps": true, + "previews": [], + "category": "actions", + "subcategory": "workflow-jobs" + }, + "slug": "list-jobs-for-a-workflow-run-attempt", + "category": "actions", + "categoryLabel": "Actions", + "subcategory": "workflow-jobs", + "subcategoryLabel": "Workflow jobs", + "notes": [], + "bodyParameters": [], + "descriptionHTML": "

Lists jobs for a specific workflow run attempt. Anyone with read access to the repository can use this endpoint. If the repository is private you must use an access token with the repo scope. GitHub Apps must have the actions:read permission to use this endpoint. You can use parameters to narrow the list of results. For more information about using parameters, see Parameters.

", + "responses": [ + { + "httpStatusCode": "200", + "httpStatusMessage": "OK", + "description": "Response", + "payload": "
{\n  \"total_count\": 1,\n  \"jobs\": [\n    {\n      \"id\": 399444496,\n      \"run_id\": 29679449,\n      \"run_url\": \"https://api.github.com/repos/octo-org/octo-repo/actions/runs/29679449\",\n      \"node_id\": \"MDEyOldvcmtmbG93IEpvYjM5OTQ0NDQ5Ng==\",\n      \"head_sha\": \"f83a356604ae3c5d03e1b46ef4d1ca77d64a90b0\",\n      \"url\": \"https://api.github.com/repos/octo-org/octo-repo/actions/jobs/399444496\",\n      \"html_url\": \"https://github.com/octo-org/octo-repo/runs/399444496\",\n      \"status\": \"completed\",\n      \"conclusion\": \"success\",\n      \"started_at\": \"2020-01-20T17:42:40Z\",\n      \"completed_at\": \"2020-01-20T17:44:39Z\",\n      \"name\": \"build\",\n      \"steps\": [\n        {\n          \"name\": \"Set up job\",\n          \"status\": \"completed\",\n          \"conclusion\": \"success\",\n          \"number\": 1,\n          \"started_at\": \"2020-01-20T09:42:40.000-08:00\",\n          \"completed_at\": \"2020-01-20T09:42:41.000-08:00\"\n        },\n        {\n          \"name\": \"Run actions/checkout@v2\",\n          \"status\": \"completed\",\n          \"conclusion\": \"success\",\n          \"number\": 2,\n          \"started_at\": \"2020-01-20T09:42:41.000-08:00\",\n          \"completed_at\": \"2020-01-20T09:42:45.000-08:00\"\n        },\n        {\n          \"name\": \"Set up Ruby\",\n          \"status\": \"completed\",\n          \"conclusion\": \"success\",\n          \"number\": 3,\n          \"started_at\": \"2020-01-20T09:42:45.000-08:00\",\n          \"completed_at\": \"2020-01-20T09:42:45.000-08:00\"\n        },\n        {\n          \"name\": \"Run actions/cache@v2\",\n          \"status\": \"completed\",\n          \"conclusion\": \"success\",\n          \"number\": 4,\n          \"started_at\": \"2020-01-20T09:42:45.000-08:00\",\n          \"completed_at\": \"2020-01-20T09:42:48.000-08:00\"\n        },\n        {\n          \"name\": \"Install Bundler\",\n          \"status\": \"completed\",\n          \"conclusion\": \"success\",\n          \"number\": 5,\n          \"started_at\": \"2020-01-20T09:42:48.000-08:00\",\n          \"completed_at\": \"2020-01-20T09:42:52.000-08:00\"\n        },\n        {\n          \"name\": \"Install Gems\",\n          \"status\": \"completed\",\n          \"conclusion\": \"success\",\n          \"number\": 6,\n          \"started_at\": \"2020-01-20T09:42:52.000-08:00\",\n          \"completed_at\": \"2020-01-20T09:42:53.000-08:00\"\n        },\n        {\n          \"name\": \"Run Tests\",\n          \"status\": \"completed\",\n          \"conclusion\": \"success\",\n          \"number\": 7,\n          \"started_at\": \"2020-01-20T09:42:53.000-08:00\",\n          \"completed_at\": \"2020-01-20T09:42:59.000-08:00\"\n        },\n        {\n          \"name\": \"Deploy to Heroku\",\n          \"status\": \"completed\",\n          \"conclusion\": \"success\",\n          \"number\": 8,\n          \"started_at\": \"2020-01-20T09:42:59.000-08:00\",\n          \"completed_at\": \"2020-01-20T09:44:39.000-08:00\"\n        },\n        {\n          \"name\": \"Post actions/cache@v2\",\n          \"status\": \"completed\",\n          \"conclusion\": \"success\",\n          \"number\": 16,\n          \"started_at\": \"2020-01-20T09:44:39.000-08:00\",\n          \"completed_at\": \"2020-01-20T09:44:39.000-08:00\"\n        },\n        {\n          \"name\": \"Complete job\",\n          \"status\": \"completed\",\n          \"conclusion\": \"success\",\n          \"number\": 17,\n          \"started_at\": \"2020-01-20T09:44:39.000-08:00\",\n          \"completed_at\": \"2020-01-20T09:44:39.000-08:00\"\n        }\n      ],\n      \"check_run_url\": \"https://api.github.com/repos/octo-org/octo-repo/check-runs/399444496\",\n      \"labels\": [\n        \"self-hosted\",\n        \"foo\",\n        \"bar\"\n      ],\n      \"runner_id\": 1,\n      \"runner_name\": \"my runner\",\n      \"runner_group_id\": 2,\n      \"runner_group_name\": \"my runner group\"\n    }\n  ]\n}\n
" + }, + { + "httpStatusCode": "404", + "httpStatusMessage": "Not Found", + "description": "Resource not found" + } + ] + }, { "verb": "get", "requestPath": "/repos/{owner}/{repo}/actions/runs/{run_id}/attempts/{attempt_number}/logs", @@ -36541,6 +36689,17 @@ "format": "date-time" }, "descriptionHTML": "" + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + }, + "descriptionHTML": "

If true pull requests are omitted from the response (empty array).

" } ], "x-codeSamples": [ @@ -74892,6 +75051,11 @@ "httpStatusMessage": "Created", "description": "Response for successful upload", "payload": "
{\n  \"url\": \"https://api.github.com/repos/octocat/Hello-World/releases/assets/1\",\n  \"browser_download_url\": \"https://github.com/octocat/Hello-World/releases/download/v1.0.0/example.zip\",\n  \"id\": 1,\n  \"node_id\": \"MDEyOlJlbGVhc2VBc3NldDE=\",\n  \"name\": \"example.zip\",\n  \"label\": \"short description\",\n  \"state\": \"uploaded\",\n  \"content_type\": \"application/zip\",\n  \"size\": 1024,\n  \"download_count\": 42,\n  \"created_at\": \"2013-02-27T19:35:32Z\",\n  \"updated_at\": \"2013-02-27T19:35:32Z\",\n  \"uploader\": {\n    \"login\": \"octocat\",\n    \"id\": 1,\n    \"node_id\": \"MDQ6VXNlcjE=\",\n    \"avatar_url\": \"https://github.com/images/error/octocat_happy.gif\",\n    \"gravatar_id\": \"\",\n    \"url\": \"https://api.github.com/users/octocat\",\n    \"html_url\": \"https://github.com/octocat\",\n    \"followers_url\": \"https://api.github.com/users/octocat/followers\",\n    \"following_url\": \"https://api.github.com/users/octocat/following{/other_user}\",\n    \"gists_url\": \"https://api.github.com/users/octocat/gists{/gist_id}\",\n    \"starred_url\": \"https://api.github.com/users/octocat/starred{/owner}{/repo}\",\n    \"subscriptions_url\": \"https://api.github.com/users/octocat/subscriptions\",\n    \"organizations_url\": \"https://api.github.com/users/octocat/orgs\",\n    \"repos_url\": \"https://api.github.com/users/octocat/repos\",\n    \"events_url\": \"https://api.github.com/users/octocat/events{/privacy}\",\n    \"received_events_url\": \"https://api.github.com/users/octocat/received_events\",\n    \"type\": \"User\",\n    \"site_admin\": false\n  }\n}\n
" + }, + { + "httpStatusCode": "422", + "httpStatusMessage": "Unprocessable Entity", + "description": "Response if you upload an asset with the same filename as another uploaded asset" } ] }, diff --git a/lib/rest/static/decorated/ghes-2.22.json b/lib/rest/static/decorated/ghes-2.22.json index 11b6353504..8faaeba7a1 100644 --- a/lib/rest/static/decorated/ghes-2.22.json +++ b/lib/rest/static/decorated/ghes-2.22.json @@ -29421,6 +29421,17 @@ "format": "date-time" }, "descriptionHTML": "" + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + }, + "descriptionHTML": "

If true pull requests are omitted from the response (empty array).

" } ], "x-codeSamples": [ @@ -29501,6 +29512,17 @@ "type": "integer" }, "descriptionHTML": "

The id of the workflow run.

" + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + }, + "descriptionHTML": "

If true pull requests are omitted from the response (empty array).

" } ], "x-codeSamples": [ @@ -31075,6 +31097,17 @@ "format": "date-time" }, "descriptionHTML": "" + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + }, + "descriptionHTML": "

If true pull requests are omitted from the response (empty array).

" } ], "x-codeSamples": [ @@ -65945,6 +65978,11 @@ "httpStatusMessage": "Created", "description": "Response for successful upload", "payload": "
{\n  \"url\": \"https://api.github.com/repos/octocat/Hello-World/releases/assets/1\",\n  \"browser_download_url\": \"https://github.com/octocat/Hello-World/releases/download/v1.0.0/example.zip\",\n  \"id\": 1,\n  \"node_id\": \"MDEyOlJlbGVhc2VBc3NldDE=\",\n  \"name\": \"example.zip\",\n  \"label\": \"short description\",\n  \"state\": \"uploaded\",\n  \"content_type\": \"application/zip\",\n  \"size\": 1024,\n  \"download_count\": 42,\n  \"created_at\": \"2013-02-27T19:35:32Z\",\n  \"updated_at\": \"2013-02-27T19:35:32Z\",\n  \"uploader\": {\n    \"login\": \"octocat\",\n    \"id\": 1,\n    \"node_id\": \"MDQ6VXNlcjE=\",\n    \"avatar_url\": \"https://github.com/images/error/octocat_happy.gif\",\n    \"gravatar_id\": \"\",\n    \"url\": \"https://api.github.com/users/octocat\",\n    \"html_url\": \"https://github.com/octocat\",\n    \"followers_url\": \"https://api.github.com/users/octocat/followers\",\n    \"following_url\": \"https://api.github.com/users/octocat/following{/other_user}\",\n    \"gists_url\": \"https://api.github.com/users/octocat/gists{/gist_id}\",\n    \"starred_url\": \"https://api.github.com/users/octocat/starred{/owner}{/repo}\",\n    \"subscriptions_url\": \"https://api.github.com/users/octocat/subscriptions\",\n    \"organizations_url\": \"https://api.github.com/users/octocat/orgs\",\n    \"repos_url\": \"https://api.github.com/users/octocat/repos\",\n    \"events_url\": \"https://api.github.com/users/octocat/events{/privacy}\",\n    \"received_events_url\": \"https://api.github.com/users/octocat/received_events\",\n    \"type\": \"User\",\n    \"site_admin\": false\n  }\n}\n
" + }, + { + "httpStatusCode": "422", + "httpStatusMessage": "Unprocessable Entity", + "description": "Response if you upload an asset with the same filename as another uploaded asset" } ] }, diff --git a/lib/rest/static/decorated/ghes-3.0.json b/lib/rest/static/decorated/ghes-3.0.json index 76631033ba..4916798ce3 100644 --- a/lib/rest/static/decorated/ghes-3.0.json +++ b/lib/rest/static/decorated/ghes-3.0.json @@ -33855,6 +33855,17 @@ "format": "date-time" }, "descriptionHTML": "" + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + }, + "descriptionHTML": "

If true pull requests are omitted from the response (empty array).

" } ], "x-codeSamples": [ @@ -33935,6 +33946,17 @@ "type": "integer" }, "descriptionHTML": "

The id of the workflow run.

" + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + }, + "descriptionHTML": "

If true pull requests are omitted from the response (empty array).

" } ], "x-codeSamples": [ @@ -35681,6 +35703,17 @@ "format": "date-time" }, "descriptionHTML": "" + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + }, + "descriptionHTML": "

If true pull requests are omitted from the response (empty array).

" } ], "x-codeSamples": [ @@ -70748,6 +70781,11 @@ "httpStatusMessage": "Created", "description": "Response for successful upload", "payload": "
{\n  \"url\": \"https://api.github.com/repos/octocat/Hello-World/releases/assets/1\",\n  \"browser_download_url\": \"https://github.com/octocat/Hello-World/releases/download/v1.0.0/example.zip\",\n  \"id\": 1,\n  \"node_id\": \"MDEyOlJlbGVhc2VBc3NldDE=\",\n  \"name\": \"example.zip\",\n  \"label\": \"short description\",\n  \"state\": \"uploaded\",\n  \"content_type\": \"application/zip\",\n  \"size\": 1024,\n  \"download_count\": 42,\n  \"created_at\": \"2013-02-27T19:35:32Z\",\n  \"updated_at\": \"2013-02-27T19:35:32Z\",\n  \"uploader\": {\n    \"login\": \"octocat\",\n    \"id\": 1,\n    \"node_id\": \"MDQ6VXNlcjE=\",\n    \"avatar_url\": \"https://github.com/images/error/octocat_happy.gif\",\n    \"gravatar_id\": \"\",\n    \"url\": \"https://api.github.com/users/octocat\",\n    \"html_url\": \"https://github.com/octocat\",\n    \"followers_url\": \"https://api.github.com/users/octocat/followers\",\n    \"following_url\": \"https://api.github.com/users/octocat/following{/other_user}\",\n    \"gists_url\": \"https://api.github.com/users/octocat/gists{/gist_id}\",\n    \"starred_url\": \"https://api.github.com/users/octocat/starred{/owner}{/repo}\",\n    \"subscriptions_url\": \"https://api.github.com/users/octocat/subscriptions\",\n    \"organizations_url\": \"https://api.github.com/users/octocat/orgs\",\n    \"repos_url\": \"https://api.github.com/users/octocat/repos\",\n    \"events_url\": \"https://api.github.com/users/octocat/events{/privacy}\",\n    \"received_events_url\": \"https://api.github.com/users/octocat/received_events\",\n    \"type\": \"User\",\n    \"site_admin\": false\n  }\n}\n
" + }, + { + "httpStatusCode": "422", + "httpStatusMessage": "Unprocessable Entity", + "description": "Response if you upload an asset with the same filename as another uploaded asset" } ] }, diff --git a/lib/rest/static/decorated/ghes-3.1.json b/lib/rest/static/decorated/ghes-3.1.json index 333c8f9473..95e6dc7c68 100644 --- a/lib/rest/static/decorated/ghes-3.1.json +++ b/lib/rest/static/decorated/ghes-3.1.json @@ -33993,6 +33993,17 @@ "format": "date-time" }, "descriptionHTML": "" + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + }, + "descriptionHTML": "

If true pull requests are omitted from the response (empty array).

" } ], "x-codeSamples": [ @@ -34073,6 +34084,17 @@ "type": "integer" }, "descriptionHTML": "

The id of the workflow run.

" + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + }, + "descriptionHTML": "

If true pull requests are omitted from the response (empty array).

" } ], "x-codeSamples": [ @@ -35819,6 +35841,17 @@ "format": "date-time" }, "descriptionHTML": "" + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + }, + "descriptionHTML": "

If true pull requests are omitted from the response (empty array).

" } ], "x-codeSamples": [ @@ -71438,6 +71471,11 @@ "httpStatusMessage": "Created", "description": "Response for successful upload", "payload": "
{\n  \"url\": \"https://api.github.com/repos/octocat/Hello-World/releases/assets/1\",\n  \"browser_download_url\": \"https://github.com/octocat/Hello-World/releases/download/v1.0.0/example.zip\",\n  \"id\": 1,\n  \"node_id\": \"MDEyOlJlbGVhc2VBc3NldDE=\",\n  \"name\": \"example.zip\",\n  \"label\": \"short description\",\n  \"state\": \"uploaded\",\n  \"content_type\": \"application/zip\",\n  \"size\": 1024,\n  \"download_count\": 42,\n  \"created_at\": \"2013-02-27T19:35:32Z\",\n  \"updated_at\": \"2013-02-27T19:35:32Z\",\n  \"uploader\": {\n    \"login\": \"octocat\",\n    \"id\": 1,\n    \"node_id\": \"MDQ6VXNlcjE=\",\n    \"avatar_url\": \"https://github.com/images/error/octocat_happy.gif\",\n    \"gravatar_id\": \"\",\n    \"url\": \"https://api.github.com/users/octocat\",\n    \"html_url\": \"https://github.com/octocat\",\n    \"followers_url\": \"https://api.github.com/users/octocat/followers\",\n    \"following_url\": \"https://api.github.com/users/octocat/following{/other_user}\",\n    \"gists_url\": \"https://api.github.com/users/octocat/gists{/gist_id}\",\n    \"starred_url\": \"https://api.github.com/users/octocat/starred{/owner}{/repo}\",\n    \"subscriptions_url\": \"https://api.github.com/users/octocat/subscriptions\",\n    \"organizations_url\": \"https://api.github.com/users/octocat/orgs\",\n    \"repos_url\": \"https://api.github.com/users/octocat/repos\",\n    \"events_url\": \"https://api.github.com/users/octocat/events{/privacy}\",\n    \"received_events_url\": \"https://api.github.com/users/octocat/received_events\",\n    \"type\": \"User\",\n    \"site_admin\": false\n  }\n}\n
" + }, + { + "httpStatusCode": "422", + "httpStatusMessage": "Unprocessable Entity", + "description": "Response if you upload an asset with the same filename as another uploaded asset" } ] }, diff --git a/lib/rest/static/decorated/ghes-3.2.json b/lib/rest/static/decorated/ghes-3.2.json index 79f86e4cbc..02d4780872 100644 --- a/lib/rest/static/decorated/ghes-3.2.json +++ b/lib/rest/static/decorated/ghes-3.2.json @@ -34907,6 +34907,17 @@ "format": "date-time" }, "descriptionHTML": "" + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + }, + "descriptionHTML": "

If true pull requests are omitted from the response (empty array).

" } ], "x-codeSamples": [ @@ -34987,6 +34998,17 @@ "type": "integer" }, "descriptionHTML": "

The id of the workflow run.

" + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + }, + "descriptionHTML": "

If true pull requests are omitted from the response (empty array).

" } ], "x-codeSamples": [ @@ -37074,6 +37096,17 @@ "format": "date-time" }, "descriptionHTML": "" + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + }, + "descriptionHTML": "

If true pull requests are omitted from the response (empty array).

" } ], "x-codeSamples": [ @@ -73628,6 +73661,11 @@ "httpStatusMessage": "Created", "description": "Response for successful upload", "payload": "
{\n  \"url\": \"https://api.github.com/repos/octocat/Hello-World/releases/assets/1\",\n  \"browser_download_url\": \"https://github.com/octocat/Hello-World/releases/download/v1.0.0/example.zip\",\n  \"id\": 1,\n  \"node_id\": \"MDEyOlJlbGVhc2VBc3NldDE=\",\n  \"name\": \"example.zip\",\n  \"label\": \"short description\",\n  \"state\": \"uploaded\",\n  \"content_type\": \"application/zip\",\n  \"size\": 1024,\n  \"download_count\": 42,\n  \"created_at\": \"2013-02-27T19:35:32Z\",\n  \"updated_at\": \"2013-02-27T19:35:32Z\",\n  \"uploader\": {\n    \"login\": \"octocat\",\n    \"id\": 1,\n    \"node_id\": \"MDQ6VXNlcjE=\",\n    \"avatar_url\": \"https://github.com/images/error/octocat_happy.gif\",\n    \"gravatar_id\": \"\",\n    \"url\": \"https://api.github.com/users/octocat\",\n    \"html_url\": \"https://github.com/octocat\",\n    \"followers_url\": \"https://api.github.com/users/octocat/followers\",\n    \"following_url\": \"https://api.github.com/users/octocat/following{/other_user}\",\n    \"gists_url\": \"https://api.github.com/users/octocat/gists{/gist_id}\",\n    \"starred_url\": \"https://api.github.com/users/octocat/starred{/owner}{/repo}\",\n    \"subscriptions_url\": \"https://api.github.com/users/octocat/subscriptions\",\n    \"organizations_url\": \"https://api.github.com/users/octocat/orgs\",\n    \"repos_url\": \"https://api.github.com/users/octocat/repos\",\n    \"events_url\": \"https://api.github.com/users/octocat/events{/privacy}\",\n    \"received_events_url\": \"https://api.github.com/users/octocat/received_events\",\n    \"type\": \"User\",\n    \"site_admin\": false\n  }\n}\n
" + }, + { + "httpStatusCode": "422", + "httpStatusMessage": "Unprocessable Entity", + "description": "Response if you upload an asset with the same filename as another uploaded asset" } ] }, diff --git a/lib/rest/static/decorated/github.ae.json b/lib/rest/static/decorated/github.ae.json index f930382755..faeaf0d0bc 100644 --- a/lib/rest/static/decorated/github.ae.json +++ b/lib/rest/static/decorated/github.ae.json @@ -26498,6 +26498,17 @@ "format": "date-time" }, "descriptionHTML": "" + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + }, + "descriptionHTML": "

If true pull requests are omitted from the response (empty array).

" } ], "x-codeSamples": [ @@ -26578,6 +26589,17 @@ "type": "integer" }, "descriptionHTML": "

The id of the workflow run.

" + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + }, + "descriptionHTML": "

If true pull requests are omitted from the response (empty array).

" } ], "x-codeSamples": [ @@ -26847,6 +26869,17 @@ "type": "integer" }, "descriptionHTML": "

The attempt number of the workflow run.

" + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + }, + "descriptionHTML": "

If true pull requests are omitted from the response (empty array).

" } ], "x-codeSamples": [ @@ -26895,6 +26928,121 @@ } ] }, + { + "verb": "get", + "requestPath": "/repos/{owner}/{repo}/actions/runs/{run_id}/attempts/{attempt_number}/jobs", + "serverUrl": "https://{hostname}/api/v3", + "parameters": [ + { + "name": "owner", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "" + }, + { + "name": "repo", + "in": "path", + "required": true, + "schema": { + "type": "string" + }, + "descriptionHTML": "" + }, + { + "name": "run_id", + "description": "The id of the workflow run.", + "in": "path", + "required": true, + "schema": { + "type": "integer" + }, + "descriptionHTML": "

The id of the workflow run.

" + }, + { + "name": "attempt_number", + "description": "The attempt number of the workflow run.", + "in": "path", + "required": true, + "schema": { + "type": "integer" + }, + "descriptionHTML": "

The attempt number of the workflow run.

" + }, + { + "name": "per_page", + "description": "Results per page (max 100)", + "in": "query", + "schema": { + "type": "integer", + "default": 30 + }, + "descriptionHTML": "

Results per page (max 100)

" + }, + { + "name": "page", + "description": "Page number of the results to fetch.", + "in": "query", + "schema": { + "type": "integer", + "default": 1 + }, + "descriptionHTML": "

Page number of the results to fetch.

" + } + ], + "x-codeSamples": [ + { + "lang": "Shell", + "source": "curl \\\n -H \"Accept: application/vnd.github.v3+json\" \\\n https://{hostname}/api/v3/repos/octocat/hello-world/actions/runs/42/attempts/42/jobs", + "html": "
curl \\\n  -H \"Accept: application/vnd.github.v3+json\" \\\n  https://{hostname}/api/v3/repos/octocat/hello-world/actions/runs/42/attempts/42/jobs
" + }, + { + "lang": "JavaScript", + "source": "await octokit.request('GET /repos/{owner}/{repo}/actions/runs/{run_id}/attempts/{attempt_number}/jobs', {\n owner: 'octocat',\n repo: 'hello-world',\n run_id: 42,\n attempt_number: 42\n})", + "html": "
await octokit.request('GET /repos/{owner}/{repo}/actions/runs/{run_id}/attempts/{attempt_number}/jobs', {\n  owner: 'octocat',\n  repo: 'hello-world',\n  run_id: 42,\n  attempt_number: 42\n})\n
" + } + ], + "summary": "List jobs for a workflow run attempt", + "description": "Lists jobs for a specific workflow run attempt. Anyone with read access to the repository can use this endpoint. If the repository is private you must use an access token with the `repo` scope. GitHub Apps must have the `actions:read` permission to use this endpoint. You can use parameters to narrow the list of results. For more information about using parameters, see [Parameters](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#parameters).", + "tags": [ + "actions" + ], + "operationId": "actions/list-jobs-for-workflow-run-attempt", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/github-ae@latest/rest/reference/actions#list-jobs-for-a-workflow-run-attempt" + }, + "x-github": { + "githubCloudOnly": false, + "enabledForGitHubApps": true, + "previews": [], + "category": "actions", + "subcategory": "workflow-jobs" + }, + "slug": "list-jobs-for-a-workflow-run-attempt", + "category": "actions", + "categoryLabel": "Actions", + "subcategory": "workflow-jobs", + "subcategoryLabel": "Workflow jobs", + "notes": [], + "bodyParameters": [], + "descriptionHTML": "

Lists jobs for a specific workflow run attempt. Anyone with read access to the repository can use this endpoint. If the repository is private you must use an access token with the repo scope. GitHub Apps must have the actions:read permission to use this endpoint. You can use parameters to narrow the list of results. For more information about using parameters, see Parameters.

", + "responses": [ + { + "httpStatusCode": "200", + "httpStatusMessage": "OK", + "description": "Response", + "payload": "
{\n  \"total_count\": 1,\n  \"jobs\": [\n    {\n      \"id\": 399444496,\n      \"run_id\": 29679449,\n      \"run_url\": \"https://api.github.com/repos/octo-org/octo-repo/actions/runs/29679449\",\n      \"node_id\": \"MDEyOldvcmtmbG93IEpvYjM5OTQ0NDQ5Ng==\",\n      \"head_sha\": \"f83a356604ae3c5d03e1b46ef4d1ca77d64a90b0\",\n      \"url\": \"https://api.github.com/repos/octo-org/octo-repo/actions/jobs/399444496\",\n      \"html_url\": \"https://github.com/octo-org/octo-repo/runs/399444496\",\n      \"status\": \"completed\",\n      \"conclusion\": \"success\",\n      \"started_at\": \"2020-01-20T17:42:40Z\",\n      \"completed_at\": \"2020-01-20T17:44:39Z\",\n      \"name\": \"build\",\n      \"steps\": [\n        {\n          \"name\": \"Set up job\",\n          \"status\": \"completed\",\n          \"conclusion\": \"success\",\n          \"number\": 1,\n          \"started_at\": \"2020-01-20T09:42:40.000-08:00\",\n          \"completed_at\": \"2020-01-20T09:42:41.000-08:00\"\n        },\n        {\n          \"name\": \"Run actions/checkout@v2\",\n          \"status\": \"completed\",\n          \"conclusion\": \"success\",\n          \"number\": 2,\n          \"started_at\": \"2020-01-20T09:42:41.000-08:00\",\n          \"completed_at\": \"2020-01-20T09:42:45.000-08:00\"\n        },\n        {\n          \"name\": \"Set up Ruby\",\n          \"status\": \"completed\",\n          \"conclusion\": \"success\",\n          \"number\": 3,\n          \"started_at\": \"2020-01-20T09:42:45.000-08:00\",\n          \"completed_at\": \"2020-01-20T09:42:45.000-08:00\"\n        },\n        {\n          \"name\": \"Run actions/cache@v2\",\n          \"status\": \"completed\",\n          \"conclusion\": \"success\",\n          \"number\": 4,\n          \"started_at\": \"2020-01-20T09:42:45.000-08:00\",\n          \"completed_at\": \"2020-01-20T09:42:48.000-08:00\"\n        },\n        {\n          \"name\": \"Install Bundler\",\n          \"status\": \"completed\",\n          \"conclusion\": \"success\",\n          \"number\": 5,\n          \"started_at\": \"2020-01-20T09:42:48.000-08:00\",\n          \"completed_at\": \"2020-01-20T09:42:52.000-08:00\"\n        },\n        {\n          \"name\": \"Install Gems\",\n          \"status\": \"completed\",\n          \"conclusion\": \"success\",\n          \"number\": 6,\n          \"started_at\": \"2020-01-20T09:42:52.000-08:00\",\n          \"completed_at\": \"2020-01-20T09:42:53.000-08:00\"\n        },\n        {\n          \"name\": \"Run Tests\",\n          \"status\": \"completed\",\n          \"conclusion\": \"success\",\n          \"number\": 7,\n          \"started_at\": \"2020-01-20T09:42:53.000-08:00\",\n          \"completed_at\": \"2020-01-20T09:42:59.000-08:00\"\n        },\n        {\n          \"name\": \"Deploy to Heroku\",\n          \"status\": \"completed\",\n          \"conclusion\": \"success\",\n          \"number\": 8,\n          \"started_at\": \"2020-01-20T09:42:59.000-08:00\",\n          \"completed_at\": \"2020-01-20T09:44:39.000-08:00\"\n        },\n        {\n          \"name\": \"Post actions/cache@v2\",\n          \"status\": \"completed\",\n          \"conclusion\": \"success\",\n          \"number\": 16,\n          \"started_at\": \"2020-01-20T09:44:39.000-08:00\",\n          \"completed_at\": \"2020-01-20T09:44:39.000-08:00\"\n        },\n        {\n          \"name\": \"Complete job\",\n          \"status\": \"completed\",\n          \"conclusion\": \"success\",\n          \"number\": 17,\n          \"started_at\": \"2020-01-20T09:44:39.000-08:00\",\n          \"completed_at\": \"2020-01-20T09:44:39.000-08:00\"\n        }\n      ],\n      \"check_run_url\": \"https://api.github.com/repos/octo-org/octo-repo/check-runs/399444496\",\n      \"labels\": [\n        \"self-hosted\",\n        \"foo\",\n        \"bar\"\n      ],\n      \"runner_id\": 1,\n      \"runner_name\": \"my runner\",\n      \"runner_group_id\": 2,\n      \"runner_group_name\": \"my runner group\"\n    }\n  ]\n}\n
" + }, + { + "httpStatusCode": "404", + "httpStatusMessage": "Not Found", + "description": "Resource not found" + } + ] + }, { "verb": "get", "requestPath": "/repos/{owner}/{repo}/actions/runs/{run_id}/attempts/{attempt_number}/logs", @@ -28583,6 +28731,17 @@ "format": "date-time" }, "descriptionHTML": "" + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + }, + "descriptionHTML": "

If true pull requests are omitted from the response (empty array).

" } ], "x-codeSamples": [ @@ -64168,6 +64327,11 @@ "httpStatusMessage": "Created", "description": "Response for successful upload", "payload": "
{\n  \"url\": \"https://api.github.com/repos/octocat/Hello-World/releases/assets/1\",\n  \"browser_download_url\": \"https://github.com/octocat/Hello-World/releases/download/v1.0.0/example.zip\",\n  \"id\": 1,\n  \"node_id\": \"MDEyOlJlbGVhc2VBc3NldDE=\",\n  \"name\": \"example.zip\",\n  \"label\": \"short description\",\n  \"state\": \"uploaded\",\n  \"content_type\": \"application/zip\",\n  \"size\": 1024,\n  \"download_count\": 42,\n  \"created_at\": \"2013-02-27T19:35:32Z\",\n  \"updated_at\": \"2013-02-27T19:35:32Z\",\n  \"uploader\": {\n    \"login\": \"octocat\",\n    \"id\": 1,\n    \"node_id\": \"MDQ6VXNlcjE=\",\n    \"avatar_url\": \"https://github.com/images/error/octocat_happy.gif\",\n    \"gravatar_id\": \"\",\n    \"url\": \"https://api.github.com/users/octocat\",\n    \"html_url\": \"https://github.com/octocat\",\n    \"followers_url\": \"https://api.github.com/users/octocat/followers\",\n    \"following_url\": \"https://api.github.com/users/octocat/following{/other_user}\",\n    \"gists_url\": \"https://api.github.com/users/octocat/gists{/gist_id}\",\n    \"starred_url\": \"https://api.github.com/users/octocat/starred{/owner}{/repo}\",\n    \"subscriptions_url\": \"https://api.github.com/users/octocat/subscriptions\",\n    \"organizations_url\": \"https://api.github.com/users/octocat/orgs\",\n    \"repos_url\": \"https://api.github.com/users/octocat/repos\",\n    \"events_url\": \"https://api.github.com/users/octocat/events{/privacy}\",\n    \"received_events_url\": \"https://api.github.com/users/octocat/received_events\",\n    \"type\": \"User\",\n    \"site_admin\": false\n  }\n}\n
" + }, + { + "httpStatusCode": "422", + "httpStatusMessage": "Unprocessable Entity", + "description": "Response if you upload an asset with the same filename as another uploaded asset" } ] }, diff --git a/lib/rest/static/dereferenced/api.github.com.deref.json b/lib/rest/static/dereferenced/api.github.com.deref.json index 0d2bd87e8c..be0d439d5a 100644 --- a/lib/rest/static/dereferenced/api.github.com.deref.json +++ b/lib/rest/static/dereferenced/api.github.com.deref.json @@ -129203,6 +129203,16 @@ "type": "string", "format": "date-time" } + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + } } ], "responses": { @@ -133119,6 +133129,16 @@ "schema": { "type": "integer" } + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + } } ], "responses": { @@ -137679,6 +137699,16 @@ "schema": { "type": "integer" } + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + } } ], "responses": { @@ -141532,6 +141562,448 @@ } } }, + "/repos/{owner}/{repo}/actions/runs/{run_id}/attempts/{attempt_number}/jobs": { + "get": { + "summary": "List jobs for a workflow run attempt", + "description": "Lists jobs for a specific workflow run attempt. Anyone with read access to the repository can use this endpoint. If the repository is private you must use an access token with the `repo` scope. GitHub Apps must have the `actions:read` permission to use this endpoint. You can use parameters to narrow the list of results. For more information about using parameters, see [Parameters](https://docs.github.com/rest/overview/resources-in-the-rest-api#parameters).", + "tags": [ + "actions" + ], + "operationId": "actions/list-jobs-for-workflow-run-attempt", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/rest/reference/actions#list-jobs-for-a-workflow-run-attempt" + }, + "parameters": [ + { + "name": "owner", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "repo", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "run_id", + "description": "The id of the workflow run.", + "in": "path", + "required": true, + "schema": { + "type": "integer" + } + }, + { + "name": "attempt_number", + "description": "The attempt number of the workflow run.", + "in": "path", + "required": true, + "schema": { + "type": "integer" + } + }, + { + "name": "per_page", + "description": "Results per page (max 100)", + "in": "query", + "schema": { + "type": "integer", + "default": 30 + } + }, + { + "name": "page", + "description": "Page number of the results to fetch.", + "in": "query", + "schema": { + "type": "integer", + "default": 1 + } + } + ], + "responses": { + "200": { + "description": "Response", + "content": { + "application/json": { + "schema": { + "type": "object", + "required": [ + "total_count", + "jobs" + ], + "properties": { + "total_count": { + "type": "integer" + }, + "jobs": { + "type": "array", + "items": { + "title": "Job", + "description": "Information of a job execution in a workflow run", + "type": "object", + "properties": { + "id": { + "description": "The id of the job.", + "example": 21, + "type": "integer" + }, + "run_id": { + "description": "The id of the associated workflow run.", + "example": 5, + "type": "integer" + }, + "run_url": { + "type": "string", + "example": "https://api.github.com/repos/github/hello-world/actions/runs/5" + }, + "run_attempt": { + "type": "integer", + "description": "Attempt number of the associated workflow run, 1 for first attempt and higher if the workflow was re-run.", + "example": 1 + }, + "node_id": { + "type": "string", + "example": "MDg6Q2hlY2tSdW40" + }, + "head_sha": { + "description": "The SHA of the commit that is being run.", + "example": "009b8a3a9ccbb128af87f9b1c0f4c62e8a304f6d", + "type": "string" + }, + "url": { + "type": "string", + "example": "https://api.github.com/repos/github/hello-world/actions/jobs/21" + }, + "html_url": { + "type": "string", + "example": "https://github.com/github/hello-world/runs/4", + "nullable": true + }, + "status": { + "description": "The phase of the lifecycle that the job is currently in.", + "example": "queued", + "type": "string", + "enum": [ + "queued", + "in_progress", + "completed" + ] + }, + "conclusion": { + "description": "The outcome of the job.", + "example": "success", + "type": "string", + "nullable": true + }, + "started_at": { + "description": "The time that the job started, in ISO 8601 format.", + "example": "2019-08-08T08:00:00-07:00", + "format": "date-time", + "type": "string" + }, + "completed_at": { + "description": "The time that the job finished, in ISO 8601 format.", + "example": "2019-08-08T08:00:00-07:00", + "format": "date-time", + "type": "string", + "nullable": true + }, + "name": { + "description": "The name of the job.", + "example": "test-coverage", + "type": "string" + }, + "steps": { + "description": "Steps in this job.", + "type": "array", + "items": { + "type": "object", + "required": [ + "name", + "status", + "conclusion", + "number" + ], + "properties": { + "status": { + "description": "The phase of the lifecycle that the job is currently in.", + "example": "queued", + "type": "string", + "enum": [ + "queued", + "in_progress", + "completed" + ] + }, + "conclusion": { + "description": "The outcome of the job.", + "example": "success", + "type": "string", + "nullable": true + }, + "name": { + "description": "The name of the job.", + "example": "test-coverage", + "type": "string" + }, + "number": { + "type": "integer", + "example": 1 + }, + "started_at": { + "description": "The time that the step started, in ISO 8601 format.", + "example": "2019-08-08T08:00:00-07:00", + "format": "date-time", + "type": "string", + "nullable": true + }, + "completed_at": { + "description": "The time that the job finished, in ISO 8601 format.", + "example": "2019-08-08T08:00:00-07:00", + "format": "date-time", + "type": "string", + "nullable": true + } + } + } + }, + "check_run_url": { + "type": "string", + "example": "https://api.github.com/repos/github/hello-world/check-runs/4" + }, + "labels": { + "type": "array", + "items": { + "type": "string" + }, + "description": "Labels for the workflow job. Specified by the \"runs_on\" attribute in the action's workflow file.", + "example": [ + "self-hosted", + "foo", + "bar" + ] + }, + "runner_id": { + "type": "integer", + "nullable": true, + "example": 1, + "description": "The ID of the runner to which this job has been assigned. (If a runner hasn't yet been assigned, this will be null.)" + }, + "runner_name": { + "type": "string", + "nullable": true, + "example": "my runner", + "description": "The name of the runner to which this job has been assigned. (If a runner hasn't yet been assigned, this will be null.)" + }, + "runner_group_id": { + "type": "integer", + "nullable": true, + "example": 2, + "description": "The ID of the runner group to which this job has been assigned. (If a runner hasn't yet been assigned, this will be null.)" + }, + "runner_group_name": { + "type": "string", + "nullable": true, + "example": "my runner group", + "description": "The name of the runner group to which this job has been assigned. (If a runner hasn't yet been assigned, this will be null.)" + } + }, + "required": [ + "id", + "node_id", + "run_id", + "run_url", + "head_sha", + "name", + "url", + "html_url", + "status", + "conclusion", + "started_at", + "completed_at", + "check_run_url", + "labels", + "runner_id", + "runner_name", + "runner_group_id", + "runner_group_name" + ] + } + } + } + }, + "examples": { + "default": { + "value": { + "total_count": 1, + "jobs": [ + { + "id": 399444496, + "run_id": 29679449, + "run_url": "https://api.github.com/repos/octo-org/octo-repo/actions/runs/29679449", + "node_id": "MDEyOldvcmtmbG93IEpvYjM5OTQ0NDQ5Ng==", + "head_sha": "f83a356604ae3c5d03e1b46ef4d1ca77d64a90b0", + "url": "https://api.github.com/repos/octo-org/octo-repo/actions/jobs/399444496", + "html_url": "https://github.com/octo-org/octo-repo/runs/399444496", + "status": "completed", + "conclusion": "success", + "started_at": "2020-01-20T17:42:40Z", + "completed_at": "2020-01-20T17:44:39Z", + "name": "build", + "steps": [ + { + "name": "Set up job", + "status": "completed", + "conclusion": "success", + "number": 1, + "started_at": "2020-01-20T09:42:40.000-08:00", + "completed_at": "2020-01-20T09:42:41.000-08:00" + }, + { + "name": "Run actions/checkout@v2", + "status": "completed", + "conclusion": "success", + "number": 2, + "started_at": "2020-01-20T09:42:41.000-08:00", + "completed_at": "2020-01-20T09:42:45.000-08:00" + }, + { + "name": "Set up Ruby", + "status": "completed", + "conclusion": "success", + "number": 3, + "started_at": "2020-01-20T09:42:45.000-08:00", + "completed_at": "2020-01-20T09:42:45.000-08:00" + }, + { + "name": "Run actions/cache@v2", + "status": "completed", + "conclusion": "success", + "number": 4, + "started_at": "2020-01-20T09:42:45.000-08:00", + "completed_at": "2020-01-20T09:42:48.000-08:00" + }, + { + "name": "Install Bundler", + "status": "completed", + "conclusion": "success", + "number": 5, + "started_at": "2020-01-20T09:42:48.000-08:00", + "completed_at": "2020-01-20T09:42:52.000-08:00" + }, + { + "name": "Install Gems", + "status": "completed", + "conclusion": "success", + "number": 6, + "started_at": "2020-01-20T09:42:52.000-08:00", + "completed_at": "2020-01-20T09:42:53.000-08:00" + }, + { + "name": "Run Tests", + "status": "completed", + "conclusion": "success", + "number": 7, + "started_at": "2020-01-20T09:42:53.000-08:00", + "completed_at": "2020-01-20T09:42:59.000-08:00" + }, + { + "name": "Deploy to Heroku", + "status": "completed", + "conclusion": "success", + "number": 8, + "started_at": "2020-01-20T09:42:59.000-08:00", + "completed_at": "2020-01-20T09:44:39.000-08:00" + }, + { + "name": "Post actions/cache@v2", + "status": "completed", + "conclusion": "success", + "number": 16, + "started_at": "2020-01-20T09:44:39.000-08:00", + "completed_at": "2020-01-20T09:44:39.000-08:00" + }, + { + "name": "Complete job", + "status": "completed", + "conclusion": "success", + "number": 17, + "started_at": "2020-01-20T09:44:39.000-08:00", + "completed_at": "2020-01-20T09:44:39.000-08:00" + } + ], + "check_run_url": "https://api.github.com/repos/octo-org/octo-repo/check-runs/399444496", + "labels": [ + "self-hosted", + "foo", + "bar" + ], + "runner_id": 1, + "runner_name": "my runner", + "runner_group_id": 2, + "runner_group_name": "my runner group" + } + ] + } + } + } + } + }, + "headers": { + "Link": { + "example": "; rel=\"next\", ; rel=\"last\"", + "schema": { + "type": "string" + } + } + } + }, + "404": { + "description": "Resource not found", + "content": { + "application/json": { + "schema": { + "title": "Basic Error", + "description": "Basic Error", + "type": "object", + "properties": { + "message": { + "type": "string" + }, + "documentation_url": { + "type": "string" + }, + "url": { + "type": "string" + }, + "status": { + "type": "string" + } + } + } + } + } + } + }, + "x-github": { + "githubCloudOnly": false, + "enabledForGitHubApps": true, + "previews": [ + + ], + "category": "actions", + "subcategory": "workflow-jobs" + } + } + }, "/repos/{owner}/{repo}/actions/runs/{run_id}/attempts/{attempt_number}/logs": { "get": { "summary": "Download workflow run attempt logs", @@ -144770,6 +145242,16 @@ "type": "string", "format": "date-time" } + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + } } ], "responses": { @@ -331391,6 +331873,9 @@ } } } + }, + "422": { + "description": "Response if you upload an asset with the same filename as another uploaded asset" } }, "x-github": { diff --git a/lib/rest/static/dereferenced/ghes-2.22.deref.json b/lib/rest/static/dereferenced/ghes-2.22.deref.json index e4a2d17b02..680135e364 100644 --- a/lib/rest/static/dereferenced/ghes-2.22.deref.json +++ b/lib/rest/static/dereferenced/ghes-2.22.deref.json @@ -109061,6 +109061,16 @@ "type": "string", "format": "date-time" } + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + } } ], "responses": { @@ -112959,6 +112969,16 @@ "schema": { "type": "integer" } + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + } } ], "responses": { @@ -118700,6 +118720,16 @@ "type": "string", "format": "date-time" } + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + } } ], "responses": { @@ -294738,6 +294768,9 @@ } } } + }, + "422": { + "description": "Response if you upload an asset with the same filename as another uploaded asset" } }, "x-github": { diff --git a/lib/rest/static/dereferenced/ghes-3.0.deref.json b/lib/rest/static/dereferenced/ghes-3.0.deref.json index e9d3ac53f8..c4864e54ac 100644 --- a/lib/rest/static/dereferenced/ghes-3.0.deref.json +++ b/lib/rest/static/dereferenced/ghes-3.0.deref.json @@ -115188,6 +115188,16 @@ "type": "string", "format": "date-time" } + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + } } ], "responses": { @@ -119086,6 +119096,16 @@ "schema": { "type": "integer" } + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + } } ], "responses": { @@ -124951,6 +124971,16 @@ "type": "string", "format": "date-time" } + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + } } ], "responses": { @@ -301579,6 +301609,9 @@ } } } + }, + "422": { + "description": "Response if you upload an asset with the same filename as another uploaded asset" } }, "x-github": { diff --git a/lib/rest/static/dereferenced/ghes-3.1.deref.json b/lib/rest/static/dereferenced/ghes-3.1.deref.json index 928f758aba..c7b6ee435d 100644 --- a/lib/rest/static/dereferenced/ghes-3.1.deref.json +++ b/lib/rest/static/dereferenced/ghes-3.1.deref.json @@ -115508,6 +115508,16 @@ "type": "string", "format": "date-time" } + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + } } ], "responses": { @@ -119406,6 +119416,16 @@ "schema": { "type": "integer" } + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + } } ], "responses": { @@ -125271,6 +125291,16 @@ "type": "string", "format": "date-time" } + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + } } ], "responses": { @@ -305467,6 +305497,9 @@ } } } + }, + "422": { + "description": "Response if you upload an asset with the same filename as another uploaded asset" } }, "x-github": { diff --git a/lib/rest/static/dereferenced/ghes-3.2.deref.json b/lib/rest/static/dereferenced/ghes-3.2.deref.json index b4c49e6e60..5c2d170a1c 100644 --- a/lib/rest/static/dereferenced/ghes-3.2.deref.json +++ b/lib/rest/static/dereferenced/ghes-3.2.deref.json @@ -117704,6 +117704,16 @@ "type": "string", "format": "date-time" } + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + } } ], "responses": { @@ -121620,6 +121630,16 @@ "schema": { "type": "integer" } + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + } } ], "responses": { @@ -128900,6 +128920,16 @@ "type": "string", "format": "date-time" } + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + } } ], "responses": { @@ -312347,6 +312377,9 @@ } } } + }, + "422": { + "description": "Response if you upload an asset with the same filename as another uploaded asset" } }, "x-github": { diff --git a/lib/rest/static/dereferenced/github.ae.deref.json b/lib/rest/static/dereferenced/github.ae.deref.json index 0bff1b87e0..341e70907c 100644 --- a/lib/rest/static/dereferenced/github.ae.deref.json +++ b/lib/rest/static/dereferenced/github.ae.deref.json @@ -84943,6 +84943,16 @@ "type": "string", "format": "date-time" } + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + } } ], "responses": { @@ -88859,6 +88869,16 @@ "schema": { "type": "integer" } + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + } } ], "responses": { @@ -93008,6 +93028,16 @@ "schema": { "type": "integer" } + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + } } ], "responses": { @@ -96861,6 +96891,448 @@ } } }, + "/repos/{owner}/{repo}/actions/runs/{run_id}/attempts/{attempt_number}/jobs": { + "get": { + "summary": "List jobs for a workflow run attempt", + "description": "Lists jobs for a specific workflow run attempt. Anyone with read access to the repository can use this endpoint. If the repository is private you must use an access token with the `repo` scope. GitHub Apps must have the `actions:read` permission to use this endpoint. You can use parameters to narrow the list of results. For more information about using parameters, see [Parameters](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#parameters).", + "tags": [ + "actions" + ], + "operationId": "actions/list-jobs-for-workflow-run-attempt", + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/github-ae@latest/rest/reference/actions#list-jobs-for-a-workflow-run-attempt" + }, + "parameters": [ + { + "name": "owner", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "repo", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "run_id", + "description": "The id of the workflow run.", + "in": "path", + "required": true, + "schema": { + "type": "integer" + } + }, + { + "name": "attempt_number", + "description": "The attempt number of the workflow run.", + "in": "path", + "required": true, + "schema": { + "type": "integer" + } + }, + { + "name": "per_page", + "description": "Results per page (max 100)", + "in": "query", + "schema": { + "type": "integer", + "default": 30 + } + }, + { + "name": "page", + "description": "Page number of the results to fetch.", + "in": "query", + "schema": { + "type": "integer", + "default": 1 + } + } + ], + "responses": { + "200": { + "description": "Response", + "content": { + "application/json": { + "schema": { + "type": "object", + "required": [ + "total_count", + "jobs" + ], + "properties": { + "total_count": { + "type": "integer" + }, + "jobs": { + "type": "array", + "items": { + "title": "Job", + "description": "Information of a job execution in a workflow run", + "type": "object", + "properties": { + "id": { + "description": "The id of the job.", + "example": 21, + "type": "integer" + }, + "run_id": { + "description": "The id of the associated workflow run.", + "example": 5, + "type": "integer" + }, + "run_url": { + "type": "string", + "example": "https://api.github.com/repos/github/hello-world/actions/runs/5" + }, + "run_attempt": { + "type": "integer", + "description": "Attempt number of the associated workflow run, 1 for first attempt and higher if the workflow was re-run.", + "example": 1 + }, + "node_id": { + "type": "string", + "example": "MDg6Q2hlY2tSdW40" + }, + "head_sha": { + "description": "The SHA of the commit that is being run.", + "example": "009b8a3a9ccbb128af87f9b1c0f4c62e8a304f6d", + "type": "string" + }, + "url": { + "type": "string", + "example": "https://api.github.com/repos/github/hello-world/actions/jobs/21" + }, + "html_url": { + "type": "string", + "example": "https://github.com/github/hello-world/runs/4", + "nullable": true + }, + "status": { + "description": "The phase of the lifecycle that the job is currently in.", + "example": "queued", + "type": "string", + "enum": [ + "queued", + "in_progress", + "completed" + ] + }, + "conclusion": { + "description": "The outcome of the job.", + "example": "success", + "type": "string", + "nullable": true + }, + "started_at": { + "description": "The time that the job started, in ISO 8601 format.", + "example": "2019-08-08T08:00:00-07:00", + "format": "date-time", + "type": "string" + }, + "completed_at": { + "description": "The time that the job finished, in ISO 8601 format.", + "example": "2019-08-08T08:00:00-07:00", + "format": "date-time", + "type": "string", + "nullable": true + }, + "name": { + "description": "The name of the job.", + "example": "test-coverage", + "type": "string" + }, + "steps": { + "description": "Steps in this job.", + "type": "array", + "items": { + "type": "object", + "required": [ + "name", + "status", + "conclusion", + "number" + ], + "properties": { + "status": { + "description": "The phase of the lifecycle that the job is currently in.", + "example": "queued", + "type": "string", + "enum": [ + "queued", + "in_progress", + "completed" + ] + }, + "conclusion": { + "description": "The outcome of the job.", + "example": "success", + "type": "string", + "nullable": true + }, + "name": { + "description": "The name of the job.", + "example": "test-coverage", + "type": "string" + }, + "number": { + "type": "integer", + "example": 1 + }, + "started_at": { + "description": "The time that the step started, in ISO 8601 format.", + "example": "2019-08-08T08:00:00-07:00", + "format": "date-time", + "type": "string", + "nullable": true + }, + "completed_at": { + "description": "The time that the job finished, in ISO 8601 format.", + "example": "2019-08-08T08:00:00-07:00", + "format": "date-time", + "type": "string", + "nullable": true + } + } + } + }, + "check_run_url": { + "type": "string", + "example": "https://api.github.com/repos/github/hello-world/check-runs/4" + }, + "labels": { + "type": "array", + "items": { + "type": "string" + }, + "description": "Labels for the workflow job. Specified by the \"runs_on\" attribute in the action's workflow file.", + "example": [ + "self-hosted", + "foo", + "bar" + ] + }, + "runner_id": { + "type": "integer", + "nullable": true, + "example": 1, + "description": "The ID of the runner to which this job has been assigned. (If a runner hasn't yet been assigned, this will be null.)" + }, + "runner_name": { + "type": "string", + "nullable": true, + "example": "my runner", + "description": "The name of the runner to which this job has been assigned. (If a runner hasn't yet been assigned, this will be null.)" + }, + "runner_group_id": { + "type": "integer", + "nullable": true, + "example": 2, + "description": "The ID of the runner group to which this job has been assigned. (If a runner hasn't yet been assigned, this will be null.)" + }, + "runner_group_name": { + "type": "string", + "nullable": true, + "example": "my runner group", + "description": "The name of the runner group to which this job has been assigned. (If a runner hasn't yet been assigned, this will be null.)" + } + }, + "required": [ + "id", + "node_id", + "run_id", + "run_url", + "head_sha", + "name", + "url", + "html_url", + "status", + "conclusion", + "started_at", + "completed_at", + "check_run_url", + "labels", + "runner_id", + "runner_name", + "runner_group_id", + "runner_group_name" + ] + } + } + } + }, + "examples": { + "default": { + "value": { + "total_count": 1, + "jobs": [ + { + "id": 399444496, + "run_id": 29679449, + "run_url": "https://api.github.com/repos/octo-org/octo-repo/actions/runs/29679449", + "node_id": "MDEyOldvcmtmbG93IEpvYjM5OTQ0NDQ5Ng==", + "head_sha": "f83a356604ae3c5d03e1b46ef4d1ca77d64a90b0", + "url": "https://api.github.com/repos/octo-org/octo-repo/actions/jobs/399444496", + "html_url": "https://github.com/octo-org/octo-repo/runs/399444496", + "status": "completed", + "conclusion": "success", + "started_at": "2020-01-20T17:42:40Z", + "completed_at": "2020-01-20T17:44:39Z", + "name": "build", + "steps": [ + { + "name": "Set up job", + "status": "completed", + "conclusion": "success", + "number": 1, + "started_at": "2020-01-20T09:42:40.000-08:00", + "completed_at": "2020-01-20T09:42:41.000-08:00" + }, + { + "name": "Run actions/checkout@v2", + "status": "completed", + "conclusion": "success", + "number": 2, + "started_at": "2020-01-20T09:42:41.000-08:00", + "completed_at": "2020-01-20T09:42:45.000-08:00" + }, + { + "name": "Set up Ruby", + "status": "completed", + "conclusion": "success", + "number": 3, + "started_at": "2020-01-20T09:42:45.000-08:00", + "completed_at": "2020-01-20T09:42:45.000-08:00" + }, + { + "name": "Run actions/cache@v2", + "status": "completed", + "conclusion": "success", + "number": 4, + "started_at": "2020-01-20T09:42:45.000-08:00", + "completed_at": "2020-01-20T09:42:48.000-08:00" + }, + { + "name": "Install Bundler", + "status": "completed", + "conclusion": "success", + "number": 5, + "started_at": "2020-01-20T09:42:48.000-08:00", + "completed_at": "2020-01-20T09:42:52.000-08:00" + }, + { + "name": "Install Gems", + "status": "completed", + "conclusion": "success", + "number": 6, + "started_at": "2020-01-20T09:42:52.000-08:00", + "completed_at": "2020-01-20T09:42:53.000-08:00" + }, + { + "name": "Run Tests", + "status": "completed", + "conclusion": "success", + "number": 7, + "started_at": "2020-01-20T09:42:53.000-08:00", + "completed_at": "2020-01-20T09:42:59.000-08:00" + }, + { + "name": "Deploy to Heroku", + "status": "completed", + "conclusion": "success", + "number": 8, + "started_at": "2020-01-20T09:42:59.000-08:00", + "completed_at": "2020-01-20T09:44:39.000-08:00" + }, + { + "name": "Post actions/cache@v2", + "status": "completed", + "conclusion": "success", + "number": 16, + "started_at": "2020-01-20T09:44:39.000-08:00", + "completed_at": "2020-01-20T09:44:39.000-08:00" + }, + { + "name": "Complete job", + "status": "completed", + "conclusion": "success", + "number": 17, + "started_at": "2020-01-20T09:44:39.000-08:00", + "completed_at": "2020-01-20T09:44:39.000-08:00" + } + ], + "check_run_url": "https://api.github.com/repos/octo-org/octo-repo/check-runs/399444496", + "labels": [ + "self-hosted", + "foo", + "bar" + ], + "runner_id": 1, + "runner_name": "my runner", + "runner_group_id": 2, + "runner_group_name": "my runner group" + } + ] + } + } + } + } + }, + "headers": { + "Link": { + "example": "; rel=\"next\", ; rel=\"last\"", + "schema": { + "type": "string" + } + } + } + }, + "404": { + "description": "Resource not found", + "content": { + "application/json": { + "schema": { + "title": "Basic Error", + "description": "Basic Error", + "type": "object", + "properties": { + "message": { + "type": "string" + }, + "documentation_url": { + "type": "string" + }, + "url": { + "type": "string" + }, + "status": { + "type": "string" + } + } + } + } + } + } + }, + "x-github": { + "githubCloudOnly": false, + "enabledForGitHubApps": true, + "previews": [ + + ], + "category": "actions", + "subcategory": "workflow-jobs" + } + } + }, "/repos/{owner}/{repo}/actions/runs/{run_id}/attempts/{attempt_number}/logs": { "get": { "summary": "Download workflow run attempt logs", @@ -98994,6 +99466,16 @@ "type": "string", "format": "date-time" } + }, + { + "name": "exclude_pull_requests", + "description": "If `true` pull requests are omitted from the response (empty array).", + "in": "query", + "required": false, + "schema": { + "type": "boolean", + "default": false + } } ], "responses": { @@ -278816,6 +279298,9 @@ } } } + }, + "422": { + "description": "Response if you upload an asset with the same filename as another uploaded asset" } }, "x-github": { diff --git a/lib/schema-event.js b/lib/schema-event.js index 9b825bae2a..dad7b692a8 100644 --- a/lib/schema-event.js +++ b/lib/schema-event.js @@ -146,7 +146,7 @@ const context = { }, application_preference: { type: 'string', - enum: ['webui', 'cli', 'desktop', 'curl', 'codespaces'], + enum: ['webui', 'cli', 'desktop', 'curl', 'codespaces', 'vscode'], description: 'The application selected by the user.', }, color_mode_preference: { @@ -404,6 +404,7 @@ const preferenceSchema = { 'desktop', 'curl', 'codespaces', + 'vscode', 'dark', 'light', 'auto', diff --git a/lib/search/indexes/github-docs-2.22-cn-records.json.br b/lib/search/indexes/github-docs-2.22-cn-records.json.br index 94270ac095..e2430efd2e 100644 --- a/lib/search/indexes/github-docs-2.22-cn-records.json.br +++ b/lib/search/indexes/github-docs-2.22-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:b18136a912122e8a840d565c5059d99926de49227b6e81e225ccb5510b677edf -size 525445 +oid sha256:a6198e058c512cb4b179998bc998bc6ceacce2e01767556e33e85fb861eb2b5e +size 527347 diff --git a/lib/search/indexes/github-docs-2.22-cn.json.br b/lib/search/indexes/github-docs-2.22-cn.json.br index 5d741f3af0..2484e33b0d 100644 --- a/lib/search/indexes/github-docs-2.22-cn.json.br +++ b/lib/search/indexes/github-docs-2.22-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:e966edbb48f8df6ff503fa523fdbe042049fb9ed23d14274edbc183863d30a18 -size 868928 +oid sha256:98a1a60203a38925d3869c62b3b89214f364c064f0a7f611bcdb2d5ff39a2e7b +size 883248 diff --git a/lib/search/indexes/github-docs-2.22-de-records.json.br b/lib/search/indexes/github-docs-2.22-de-records.json.br index 1916377d16..ba9be613bb 100644 --- a/lib/search/indexes/github-docs-2.22-de-records.json.br +++ b/lib/search/indexes/github-docs-2.22-de-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:daa952742ae7257b96fb5646101054dc7f54b4225b182d390ccfae2de574f6ac -size 479320 +oid sha256:7d5a285f7c68ff60d7c44594b3ca52cd52f5104c074cb82a5858148179f8b66f +size 481201 diff --git a/lib/search/indexes/github-docs-2.22-de.json.br b/lib/search/indexes/github-docs-2.22-de.json.br index ff24db35af..ad14ae0664 100644 --- a/lib/search/indexes/github-docs-2.22-de.json.br +++ b/lib/search/indexes/github-docs-2.22-de.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:911d0e239e7ad05ffa5f0864c556d197b8303de18711b296acf79f15354ddcee -size 2126624 +oid sha256:2e26959f09eebdd79bf66dd322a97532ee32de510be90aa6ac0c754bf09b8bc6 +size 2140662 diff --git a/lib/search/indexes/github-docs-2.22-en-records.json.br b/lib/search/indexes/github-docs-2.22-en-records.json.br index 2e8bb2be43..f9992ccf61 100644 --- a/lib/search/indexes/github-docs-2.22-en-records.json.br +++ b/lib/search/indexes/github-docs-2.22-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:21f039c13fb41560051af6a3d1e47aee671ee9f8bef1b27c862bbf9ae2b091c5 -size 433663 +oid sha256:f40222db91173cd45774b072c00b8da5514c5b77bc56658642024eab182712fa +size 433881 diff --git a/lib/search/indexes/github-docs-2.22-en.json.br b/lib/search/indexes/github-docs-2.22-en.json.br index dc9930cab3..3621793ac5 100644 --- a/lib/search/indexes/github-docs-2.22-en.json.br +++ b/lib/search/indexes/github-docs-2.22-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:b9968ef6390504b5a5bf60ecb97286877d33c23df4aac55a08c27bc52ae0e2d5 -size 1694288 +oid sha256:74c9583915f4665f486f89ac1afa662d69e31ffd22886a567a23b339e5f9723f +size 1695701 diff --git a/lib/search/indexes/github-docs-2.22-es-records.json.br b/lib/search/indexes/github-docs-2.22-es-records.json.br index 0f8751011b..e568a97e77 100644 --- a/lib/search/indexes/github-docs-2.22-es-records.json.br +++ b/lib/search/indexes/github-docs-2.22-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:20547bea1d8b83886e56c5f79ba334e2268fdb6c3989743307fc50f69d346c37 -size 194940 +oid sha256:dd0393cd0e3ecc7f9f84fcdd4163444ff53c96c5791b9f538e0c6cf42f448eac +size 187117 diff --git a/lib/search/indexes/github-docs-2.22-es.json.br b/lib/search/indexes/github-docs-2.22-es.json.br index 938bb59702..7204bae062 100644 --- a/lib/search/indexes/github-docs-2.22-es.json.br +++ b/lib/search/indexes/github-docs-2.22-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:b9fa4525f09e988bae619e0bcffdce779e8d95850dd4b19e6b4744d75e8e60f5 -size 702623 +oid sha256:c4f936c556fde9f3bd3ad135ff154d5924f8c2b896e58b9da9771212eed271f9 +size 657975 diff --git a/lib/search/indexes/github-docs-2.22-ja-records.json.br b/lib/search/indexes/github-docs-2.22-ja-records.json.br index fcd1b1410c..e710e39c83 100644 --- a/lib/search/indexes/github-docs-2.22-ja-records.json.br +++ b/lib/search/indexes/github-docs-2.22-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:cfdf9028a4e6378b6638ecb23c66d2193e949ecf5df835e1e3c14cffb53a8cee -size 545317 +oid sha256:fb9bfc4cd10b5712fec94bc2a70c55d073aa2ec5f163ef6c45b85096c9b5b781 +size 547951 diff --git a/lib/search/indexes/github-docs-2.22-ja.json.br b/lib/search/indexes/github-docs-2.22-ja.json.br index 1770cc5e93..1d440e006f 100644 --- a/lib/search/indexes/github-docs-2.22-ja.json.br +++ b/lib/search/indexes/github-docs-2.22-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:d395319a57369d19a31b2764ecbdd5e908eb1ac584cc21da6204104a4e5871aa -size 2880022 +oid sha256:55fec62fff71aacad873bd00a083ca6ab7f5bdc6163c92c6c6bc6a2f822ca73f +size 2897665 diff --git a/lib/search/indexes/github-docs-2.22-pt-records.json.br b/lib/search/indexes/github-docs-2.22-pt-records.json.br index f024364ec0..b47e290184 100644 --- a/lib/search/indexes/github-docs-2.22-pt-records.json.br +++ b/lib/search/indexes/github-docs-2.22-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:a68aa2e1e4b176755aeb92b0e877eb4cc16058c240faa3d44c9f1527b371e2b0 -size 456848 +oid sha256:427f3dad37244329aab969a1156badc4a5a955b37ef766802fd8aaf10ad975b1 +size 457004 diff --git a/lib/search/indexes/github-docs-2.22-pt.json.br b/lib/search/indexes/github-docs-2.22-pt.json.br index ff116c5c84..6da724f024 100644 --- a/lib/search/indexes/github-docs-2.22-pt.json.br +++ b/lib/search/indexes/github-docs-2.22-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:db6328d9d0392212c965b39bd8fb9226a4b2a418f25485109ea352a514c76d8e -size 1905314 +oid sha256:e137046615ba1404892ed3aaa476af8b7480d43a96b592b330590c56e32aa129 +size 1887248 diff --git a/lib/search/indexes/github-docs-3.0-cn-records.json.br b/lib/search/indexes/github-docs-3.0-cn-records.json.br index 04e83bfc45..4955a0d345 100644 --- a/lib/search/indexes/github-docs-3.0-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.0-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:fb664fbaa02f8d028754b3dc21da712a52201a4ffdb53fdef47ea30da8d46abd -size 544977 +oid sha256:d5af89fa9cb63eedb5ac1ca75f34912f402db5922845e0cebc4de32aaa702234 +size 546969 diff --git a/lib/search/indexes/github-docs-3.0-cn.json.br b/lib/search/indexes/github-docs-3.0-cn.json.br index b47fffe707..59baf42ee7 100644 --- a/lib/search/indexes/github-docs-3.0-cn.json.br +++ b/lib/search/indexes/github-docs-3.0-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:929606e262c18524332fad570e683c587fcd3c197701502d66a99e67fc6f599e -size 906097 +oid sha256:6617a90032bf6c296ad5c8ac0dc06db5edc7678db9b46c91c9bfbd877f50e4b6 +size 922720 diff --git a/lib/search/indexes/github-docs-3.0-de-records.json.br b/lib/search/indexes/github-docs-3.0-de-records.json.br index 13d464c276..85e6833352 100644 --- a/lib/search/indexes/github-docs-3.0-de-records.json.br +++ b/lib/search/indexes/github-docs-3.0-de-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:d50427dc1993a1342bf3d8f47f5761bc2e9311bbbf9bef926599d497e2825010 -size 499705 +oid sha256:90e7f1cdc0a1e411e67f15187a3f9964cf38143e79d08fae0bd742da3e09c55c +size 501829 diff --git a/lib/search/indexes/github-docs-3.0-de.json.br b/lib/search/indexes/github-docs-3.0-de.json.br index b8c5caa48d..5bc2a7fef5 100644 --- a/lib/search/indexes/github-docs-3.0-de.json.br +++ b/lib/search/indexes/github-docs-3.0-de.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:68861304d0598715a476f5258f3491fc21b3358d16c20f2090cf644f627360d6 -size 2232609 +oid sha256:7ce6143d73f94e7e6afaf2cd00941803ffad3c705ed0aab006a9c23a918eba1f +size 2246374 diff --git a/lib/search/indexes/github-docs-3.0-en-records.json.br b/lib/search/indexes/github-docs-3.0-en-records.json.br index ebea27cd8f..3a740bca41 100644 --- a/lib/search/indexes/github-docs-3.0-en-records.json.br +++ b/lib/search/indexes/github-docs-3.0-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:d74ad7c549363c1ba5e1068ce32f9aab88339d345c43a6350d5659bf1ec52f0c -size 453832 +oid sha256:cf11717422d15388003d9bbac945b638281ea238eb1b6f589c5719c47454e976 +size 454193 diff --git a/lib/search/indexes/github-docs-3.0-en.json.br b/lib/search/indexes/github-docs-3.0-en.json.br index 4a4b6bef29..e921e1487d 100644 --- a/lib/search/indexes/github-docs-3.0-en.json.br +++ b/lib/search/indexes/github-docs-3.0-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:fc4b706325334ac8a440235c7c3cb40ec240dd1f5ab39034636593664ab35680 -size 1769750 +oid sha256:7b161992229d6a6e280d75e8acee764d7f074bc21055f8ad85861aa817697240 +size 1771921 diff --git a/lib/search/indexes/github-docs-3.0-es-records.json.br b/lib/search/indexes/github-docs-3.0-es-records.json.br index d4aaae3c3f..fe4b6e9db9 100644 --- a/lib/search/indexes/github-docs-3.0-es-records.json.br +++ b/lib/search/indexes/github-docs-3.0-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:90886f02b6f26aa3d95de7332ab379319dc7c2edfda81b575c3f99b2b1bf940a -size 193687 +oid sha256:47bcd0615980b1cbdd8cefd24b87c3ffb9b535c7cce525678788486a1dec1c18 +size 185786 diff --git a/lib/search/indexes/github-docs-3.0-es.json.br b/lib/search/indexes/github-docs-3.0-es.json.br index 797376cfe1..bb92b8bd32 100644 --- a/lib/search/indexes/github-docs-3.0-es.json.br +++ b/lib/search/indexes/github-docs-3.0-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:369f478c15a14c4452ffc29d25dae3bb0f158948cc91028401aa260d37c90540 -size 694160 +oid sha256:cc2cc8206b9a875efb2daecf59dd4ddf7407e83c0c7d797603f2389b3711ac4f +size 650315 diff --git a/lib/search/indexes/github-docs-3.0-ja-records.json.br b/lib/search/indexes/github-docs-3.0-ja-records.json.br index 71a2a834b7..b4b86e47cf 100644 --- a/lib/search/indexes/github-docs-3.0-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.0-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:c4fe2ffa9142217d06a5684cb783a05d9db6dc3387defe006c063c307c417d29 -size 567838 +oid sha256:30f78de95f5c9e07fbec5046302564f63279d01d3e7b21c1e778e235b27ce3e0 +size 570043 diff --git a/lib/search/indexes/github-docs-3.0-ja.json.br b/lib/search/indexes/github-docs-3.0-ja.json.br index caf8efdd70..38891bddde 100644 --- a/lib/search/indexes/github-docs-3.0-ja.json.br +++ b/lib/search/indexes/github-docs-3.0-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:a86782d2b6e53e733848b736adc640b29210a809d539ffff96f751fdb102bc32 -size 3006717 +oid sha256:ed7dc54899226814c2021fe57ca81ac0406a8aba48a1d26f449193315fbce818 +size 3023669 diff --git a/lib/search/indexes/github-docs-3.0-pt-records.json.br b/lib/search/indexes/github-docs-3.0-pt-records.json.br index 0d80b5e366..68956b212b 100644 --- a/lib/search/indexes/github-docs-3.0-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.0-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:03811d459de2726ab4a4c94fd62767ca87ea75296464108f14a083a871ff9aea -size 477635 +oid sha256:acedb6612904e71cf9137d7a3dd7b397d99c64fb2ad8ea94f76eadc639e7636f +size 477474 diff --git a/lib/search/indexes/github-docs-3.0-pt.json.br b/lib/search/indexes/github-docs-3.0-pt.json.br index 2a3b47c1a8..efa869bf9c 100644 --- a/lib/search/indexes/github-docs-3.0-pt.json.br +++ b/lib/search/indexes/github-docs-3.0-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:c61d7373405cb2e5b1ba47daff4f6469ea96d4bdf3d4248f8db0a23d0708f9d9 -size 1993680 +oid sha256:1e8afa20051be67bafb39656b802597d2edfc03dbd7895dd0859b04a83c6a214 +size 1971644 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 64e037b0e3..169fcea204 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:70e44da66368b38ce8191d41b062d91d21bc4f162b3b2783866390f490ca5f40 -size 557481 +oid sha256:6ca6dc99e23521380c82fb92962dd6034fe70618b0f581cca1f3fe740f79f3c2 +size 560807 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 76fd62e798..810195fbe2 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:ec3d62c1fb55a05d069457888dd1ab631b86e9b0a8e0764866349b04d4384032 -size 929530 +oid sha256:ad0c47635dc1565c0a4e024f85ef478bb17f69141201e4c231304e7082b27135 +size 951104 diff --git a/lib/search/indexes/github-docs-3.1-de-records.json.br b/lib/search/indexes/github-docs-3.1-de-records.json.br index 37fc664c85..7a1bac739c 100644 --- a/lib/search/indexes/github-docs-3.1-de-records.json.br +++ b/lib/search/indexes/github-docs-3.1-de-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:bbace2944c7400415416c713191c2b9e1946238b05e77a2d5329c39f0bda6ef8 -size 508570 +oid sha256:99ea4455da6a56403195b2ef1aca1513dc48ede90bb1949035323fd4306b446c +size 511524 diff --git a/lib/search/indexes/github-docs-3.1-de.json.br b/lib/search/indexes/github-docs-3.1-de.json.br index 9d5b64b59f..d61083231a 100644 --- a/lib/search/indexes/github-docs-3.1-de.json.br +++ b/lib/search/indexes/github-docs-3.1-de.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:e5e2d149917fbd8f02e5ddeed0cb97414c123cc4473955e3347226fd0265ac43 -size 2285042 +oid sha256:805e291f4c3a2494176c32e615492873bec6637bccc5e5471bbd99e7f4ec7059 +size 2304442 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 d0c2a67f10..27a25da8cc 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:ba4a9c6a86b92aa282df69e2985ffb089b03393bbef79b3d2f88720f67e9148b -size 464186 +oid sha256:6185577acbe05495241f88daa70b3cd684f9e4fc96f5d44a53230bb88e97e1ba +size 463644 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 7d371b8e5f..5678b29184 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:5734fceec1f37a2532755b2f8521cbb7aeabc37d7331f0e7f610adb69167656c -size 1812643 +oid sha256:15a7621f3c1ff9ec82fecd7f6bcba5343d9fd57d395266a5e345818dbccb942f +size 1814472 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 b4af25b254..eccbd375f1 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:acde6a856e539ae15ac5322e852506c34d41788bdd28fc85b9fd3d92495c61fe -size 193544 +oid sha256:0879a25482cd27e2178a16f9924cf460f946fa55a2306d09faab0c0750ddc1e7 +size 185722 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 fbb31ad6b7..756b511fbb 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:12423afe2d1d3738ed8755947641bfa7f5d6972ca293a0acf0c7938007b50ed2 -size 694093 +oid sha256:e0da11d74d76916e2b8d3e6ffade9d711caa4f85cd1213b10d4bec1104457a44 +size 649994 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 697be6f1a8..91c090404a 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:a526e1f4d9329c9a76870cff12f63edf1fd8902633b0511a1e8f25f4a6212260 -size 580090 +oid sha256:43574f2a20f7855eba51ccd69cfac7e236005eba7c777ada6e1af4f2b68851eb +size 583325 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 cc4a1b8628..f045efcaa3 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:0028833d4585018305eaaffde678e5887015618f8245fcdbef2fe11efed27a61 -size 3073042 +oid sha256:0d43b9eb30f9bf7295cd49cad6403e3bd998bbe889c2ae6004e306945b42d2de +size 3101697 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 0471362b1a..f67cfb93c0 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:f8603fdf51ab318332c4958040451fcf68e2030f0d1697b97f43b40c2cd1df6b -size 487230 +oid sha256:5833256650c84267f6e4abda930de4d9aec0bc4db741d7e93d392a2d4142ed46 +size 487663 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 d18db50a6f..4df1b0526d 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:8b82f1954cdaddcc26c4d818799947b7f563d2c9579a328f4ae1c2c7b6080a09 -size 2037154 +oid sha256:4238769f38a37d5448a24b823c417a4244f265adfbc5b2091b5b111ecb7e26db +size 2018540 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 f7c4568acd..fc021bbb0a 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:ee1c3f13484764e96dad734f0a9033c2fe94265b725365066ff5cdbdb9078901 -size 568071 +oid sha256:98da9abbf85d5d0c5628c4e8ee67060b79f949002c12153a3367fbc6906be42c +size 571609 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 d1ee034cb0..415eeb7ab0 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:603a00e8ca9e3ed927e8140050cf71883de21f5faf47e9ad1b679a79f0b59123 -size 949629 +oid sha256:af141b21f9d53d1ce16ae7229a46e6990a302a6c3ded5f6fb791bbb96f245a56 +size 970839 diff --git a/lib/search/indexes/github-docs-3.2-de-records.json.br b/lib/search/indexes/github-docs-3.2-de-records.json.br index d185b2b71a..6bf84cee3c 100644 --- a/lib/search/indexes/github-docs-3.2-de-records.json.br +++ b/lib/search/indexes/github-docs-3.2-de-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:c2e1ce9e78449b2edf7e7b82ded817214ebbd9488eac161abbef7c8be324edcd -size 517603 +oid sha256:b00d55553c334dd3ec26800e62ea8cc2a98b6b81e11e25ce6c088887351305d9 +size 520482 diff --git a/lib/search/indexes/github-docs-3.2-de.json.br b/lib/search/indexes/github-docs-3.2-de.json.br index d94b71dbe5..56cb7fa8ce 100644 --- a/lib/search/indexes/github-docs-3.2-de.json.br +++ b/lib/search/indexes/github-docs-3.2-de.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:0382fef6498d8721e4fb169e52c71dfbfb35727d5cafc5f1f7fe9c22f743b239 -size 2332634 +oid sha256:dc343cf4efdf337eaeb164ff8037aa9501b618793509c0a4545496004c88c101 +size 2351832 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 5d15abcae7..3d5d828161 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:db15240ef2ff8677b564d5b60e5a356ac39ff2f78cdc23162ec9e6a3542f86a2 -size 472748 +oid sha256:1fe736ef16807078d97dc50847e4a96d53a9bf1e715b8b64ffa37ae363d075b8 +size 472996 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 307ed85c5d..ae950f115c 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:4fe5ce2c545f42c147aabce9a4431d4c8266256db6ab85491f833f7ea777998e -size 1845248 +oid sha256:50479d545f9796456f0e01de514e874678b9e19851d117daab8f5dca492e6ccb +size 1847080 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 c19f97f769..6bf4a8fa38 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:b38cbabf68d8ec5e33644ac08e285f0feb6df7539197174573e326f64fcaa660 -size 193645 +oid sha256:4980b3c6fd193977d9fdc17e07ef45566777e715143cec68e54cb27ef36a0d03 +size 185691 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 bc10957994..0684034254 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:f52b8e730159fb626a105508640569691c3f9bbfa67e55cf6554349079ad49b5 -size 694005 +oid sha256:84358327cb1304b890928509cd540ed96d9118a6b8fa4b291af5f36f54950744 +size 650238 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 4ec93fa87e..b42429b737 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:792cca6547994005703b5a5275fb580a1ccfa98fe88b9c33f82ad8be1909c024 -size 590355 +oid sha256:4830329b6849e3137e93c739e262f6a8c1d5b1e06fb816ad8f81ac0b454e845b +size 593865 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 5ebbd7afa6..40aa9e26b7 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:50cfcc6db7a0560c9c5c9da21373427041ad5256d8c937335bab3a9827e1a677 -size 3141528 +oid sha256:f60784e6c86dbd7975f94467cc17c21e4af22ffdae963cf47f05d67c41e1d2a1 +size 3166852 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 e341eeed4a..d7216502b0 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:8dcc420586015c1ffd566e8e71b83264272c09ffc884480b99fe3a2c90882961 -size 496704 +oid sha256:9a21cbd95cf8d5e22a8b6e97dd267cf79d7f639fb54f2b21f2756ec39cf931bc +size 497192 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 c4026051e8..98f1634e80 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:046f12a963bfe4a80851ba6998afa65acced3063161b991c0e3423be98502ac6 -size 2078807 +oid sha256:0e7eac56b51c594ea7f01666d26ff05d6291ac5855156d95a292c9bcdabb7200 +size 2055926 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 00a659ffce..cc66622c09 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:910a945db8b617ab9901b31815b58d54c3a90bd3b23af8c586530b285996e467 -size 771035 +oid sha256:e4598e2c5b74c58fc175349f46be0ac5d5fcf5276e180a2bb6095bc2296233fb +size 782106 diff --git a/lib/search/indexes/github-docs-dotcom-cn.json.br b/lib/search/indexes/github-docs-dotcom-cn.json.br index b47438a55e..5fe15a241e 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:1e0df55a5a1fe7e44cc9636a8c5f0d72620e5564b984983f8cff8d627bbb091b -size 1171159 +oid sha256:a910fd378c1106ab1b13338c8810f9511f4eed47c185f1013ff9952c33bf2f22 +size 1233282 diff --git a/lib/search/indexes/github-docs-dotcom-de-records.json.br b/lib/search/indexes/github-docs-dotcom-de-records.json.br index 6d19f468e3..7515265324 100644 --- a/lib/search/indexes/github-docs-dotcom-de-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-de-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:03c5bbcf8ceecfbe58ff475eeeace38e5a2dd1c7f74278dbc727f38312a677bd -size 690637 +oid sha256:26f94b2c78fd9dae1780d7b3805ce699564157609fcfad2941e3b13f066a954e +size 701690 diff --git a/lib/search/indexes/github-docs-dotcom-de.json.br b/lib/search/indexes/github-docs-dotcom-de.json.br index ae04ef74a1..d6fee95040 100644 --- a/lib/search/indexes/github-docs-dotcom-de.json.br +++ b/lib/search/indexes/github-docs-dotcom-de.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:04b325dd1f3cc1bb1b8c05fbbf25fbdc07847768bd2ed1cca75b929ca91a1a22 -size 3124219 +oid sha256:f82b9f4b137de8acc9497c5d92acd3db147942f2044c0137ac130d8120b5c95d +size 3193115 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 0fab26bfb6..2e9127780c 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:8f9b2997bac874a02b533b4c6942e423a411945e4ab41c1b57cee299df0b8661 -size 638628 +oid sha256:3f726f553a6eb4a88872ea9099f62c27fb1caed0e3156fa306016fb001ecc0c8 +size 640038 diff --git a/lib/search/indexes/github-docs-dotcom-en.json.br b/lib/search/indexes/github-docs-dotcom-en.json.br index c2302b1fe2..9ea408b71b 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:76c705525d2dca5b4a6cc3466592e98eea343f97f6f13e8a6f6504e369e83025 -size 2427077 +oid sha256:8dd5d57c4117aa21d0e2d0cee6d64352b139ebc3cfd6ce1633024bfe4b94e605 +size 2431483 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 b68911d7e5..3c90eb5baa 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:7a1f167e44dbcfacd03437757f8cfead85076161cda6275b13c40a220f572e4b -size 205227 +oid sha256:049fbaebeda97b1409e93beff3729187c674b3787cc5a7b703b98f49c30746bc +size 195168 diff --git a/lib/search/indexes/github-docs-dotcom-es.json.br b/lib/search/indexes/github-docs-dotcom-es.json.br index 6f11f0adcb..b9ed06c4ce 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:318b9e2dbdf07d53b4973500cba9a811a1207398c7055576e24386e2c87e9b51 -size 650952 +oid sha256:477b0c454da7adc85f25227e828d5d39ea9e217ef47f5ef7e7d2fbbefc8781c7 +size 615504 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 39ff09d754..f36f4769a4 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:25d3aba72f92bd0b7dad577e3cb408afe4ce7bacc69b9555f3ee7ee7bdc390c1 -size 795813 +oid sha256:b2b89e6fb94952c6ab0a68bb062944f5a13bedf18385429af5ca813cefae3c6f +size 805880 diff --git a/lib/search/indexes/github-docs-dotcom-ja.json.br b/lib/search/indexes/github-docs-dotcom-ja.json.br index 15554cf670..5e2ece9634 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:2f60abba9349ed6dbb6f9c9fbb00b4ebea002baa6a6b61e0fcbc263e23dc82fd -size 4153257 +oid sha256:54102f090efd8ad84725c914ccf1c3ea9fb9f23fb7c94ca39cc4979fa61a1c67 +size 4233633 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 5f20e93397..b02149a96f 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:12532f45415ce6e3f538c3b6bd9c26bf25fcce3e7f448e51d2292e31cb65cdff -size 669611 +oid sha256:eff32f3370172139a09e154834502b65f01eebf59681a3675d96aa784b2fec58 +size 676652 diff --git a/lib/search/indexes/github-docs-dotcom-pt.json.br b/lib/search/indexes/github-docs-dotcom-pt.json.br index 97538f62f6..d2d4df342c 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:06f0afe5b90acee21a614d7c7fdcbb71e74f810bd8df945f3544c4690f52223c -size 2749613 +oid sha256:460c8b51f0e7a3433a86cba8d50290c896f0a49d7661c6b43589a697c39cd607 +size 2742759 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 ccc07a2e69..8cf68a5aab 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:b1e267176685acf53c111860064d28e4188fe4c8bc8f6f26d8502de1fffe3abf -size 433597 +oid sha256:347f10e6b6c98e0397f3d1c65bf72ef8df3c6dfd17f87c21739d1063f364f5f8 +size 437824 diff --git a/lib/search/indexes/github-docs-ghae-cn.json.br b/lib/search/indexes/github-docs-ghae-cn.json.br index 001dad7be7..7533161f58 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:4eb11f667cdc203fb859cd834656327becc9d3b39ed6fd228ad63d4d861bb810 -size 691448 +oid sha256:df3a25a515c290db92a834ce5589753b058c2e03934d005d9b0a4a02e5ada7ee +size 712102 diff --git a/lib/search/indexes/github-docs-ghae-de-records.json.br b/lib/search/indexes/github-docs-ghae-de-records.json.br index dee5e041aa..559a72eace 100644 --- a/lib/search/indexes/github-docs-ghae-de-records.json.br +++ b/lib/search/indexes/github-docs-ghae-de-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:3d7c82ff9d5a8002a69a3c60bb671a51e64b685229a502fbf41a933afcc51189 -size 400588 +oid sha256:274d70839fb3f6cbe4857629a469e490b6faa21acb4dfbb6190560552347bc9c +size 404010 diff --git a/lib/search/indexes/github-docs-ghae-de.json.br b/lib/search/indexes/github-docs-ghae-de.json.br index 0ff0dbf696..0c0eb3b04c 100644 --- a/lib/search/indexes/github-docs-ghae-de.json.br +++ b/lib/search/indexes/github-docs-ghae-de.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:b230208a25e605a46fe5138382b527a001ecada40d15b49e62272e8aacc54340 -size 1741399 +oid sha256:12976bca82039a78066f46b3e40450bedc3c75440b40a70f08d077973269b0c0 +size 1758980 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 e13ce88267..4677f533cf 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:7c6c4219c39c747687e12ed857576162a9a0a4f63af3e74678765c5938f6667e -size 365598 +oid sha256:5676025479455d95761d549680b6f8b2d8ce5e96eaf1ffa9ad7f7b7f00c2bbc3 +size 365837 diff --git a/lib/search/indexes/github-docs-ghae-en.json.br b/lib/search/indexes/github-docs-ghae-en.json.br index ce8b8b8748..6ef2e0a630 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:aa839332b9f6cb6cba378b70c62a25dca1e126134c6c7d97efd819ecdc066043 -size 1358120 +oid sha256:6981f1516769b9521dce10185482cc427ffdc58be8335d9fbfac20dd01004507 +size 1360243 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 37a0eafb98..83ce95161d 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:092902c72f9599d082a2269749d3686a0353605876306d91bcd96eede2c1a0c7 -size 130841 +oid sha256:a86975cb89ea9986c832500b5c3ff03f7ed35711785e0d7131fe5cbbedb0861b +size 121276 diff --git a/lib/search/indexes/github-docs-ghae-es.json.br b/lib/search/indexes/github-docs-ghae-es.json.br index 844fd6bdba..ec83b5d23c 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:e5a264eb41b8fe6443a46cd0aa9f86d6a8edfd9cea2eae1c0fca3e9c7f4d566a -size 420114 +oid sha256:70b9b2ac95680b262a3cefb693119b8d1530052788e631917a12756107e3156d +size 386413 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 0092431613..93d0aa2a6a 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:4e0f97b0cd2d3fb4ec0a23c74fc1c4f8c49fd25b47f1a86d1d3c953e5e1c5533 -size 452994 +oid sha256:5c8c2d004204f190967f632b2eeb7bbb64c39837e6aba32dc1767cd11ad27799 +size 457278 diff --git a/lib/search/indexes/github-docs-ghae-ja.json.br b/lib/search/indexes/github-docs-ghae-ja.json.br index deeda9751c..f93a89981e 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:e325ed3555379cc5f3a9828cc592a93aeb3fcbf967a7782ad899000d93f69783 -size 2295864 +oid sha256:fd0b7a4bcc3fc993b3f21c1bbdfde2e02abf7c6161e17ee6ddcb941f26929bd9 +size 2322313 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 a1e926371b..22f98e5209 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:8c40404b3acef4325b3686cf516934f924f87c0a2fec725d9031f55347f47139 -size 384949 +oid sha256:401d7882d2c96b741be11161e8f5bc33bffe0c4b408fe3d0c0eb29d196aafc1b +size 385458 diff --git a/lib/search/indexes/github-docs-ghae-pt.json.br b/lib/search/indexes/github-docs-ghae-pt.json.br index 3c9d358c1e..5dbf487970 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:2d2949569e8996e7172a38e62d07ff152d19e885180c64c668dbb0aa32e2d33a -size 1537093 +oid sha256:d96f98797127be6a2cea0d73f2983e0b5d3cc049b28256aba23d0f308e75b862 +size 1524055 diff --git a/package-lock.json b/package-lock.json index fab76066cf..04dcb8bf96 100644 --- a/package-lock.json +++ b/package-lock.json @@ -14,7 +14,7 @@ "@primer/octicons": "^15.1.0", "@primer/octicons-react": "^15.1.0", "accept-language-parser": "^1.5.0", - "ajv": "^8.4.0", + "ajv": "^8.6.3", "ajv-formats": "^2.1.1", "browser-date-formatter": "^3.0.3", "change-case": "^4.1.2", @@ -30,7 +30,7 @@ "dotenv": "^10.0.0", "express": "^4.17.1", "express-basic-auth": "^1.2.0", - "express-rate-limit": "^5.3.0", + "express-rate-limit": "^5.4.1", "express-timeout-handler": "^2.2.2", "flat": "^5.0.2", "github-slugger": "^1.4.0", @@ -44,7 +44,7 @@ "helmet": "^4.6.0", "highlight.js": "^11.2.0", "highlightjs-graphql": "^1.0.2", - "hot-shots": "^8.5.1", + "hot-shots": "^8.5.2", "html-entities": "^2.3.2", "imurmurhash": "^0.1.4", "js-cookie": "^3.0.1", @@ -54,7 +54,7 @@ "lodash-es": "^4.17.21", "lunr": "^2.3.9", "lunr-languages": "^1.9.0", - "mdast-util-from-markdown": "^1.0.0", + "mdast-util-from-markdown": "^1.0.3", "mdast-util-to-string": "^3.1.0", "morgan": "^1.10.0", "next": "^11.1.2", @@ -90,27 +90,27 @@ "throng": "^5.0.0", "ts-dedent": "^2.2.0", "unified": "^10.1.0", - "unist-util-visit": "^4.0.0", + "unist-util-visit": "^4.1.0", "uuid": "^8.3.2", "walk-sync": "^3.0.0" }, "devDependencies": { "@actions/core": "^1.5.0", "@actions/github": "^5.0.0", - "@babel/core": "^7.15.5", + "@babel/core": "^7.15.8", "@babel/eslint-parser": "^7.15.4", "@babel/plugin-syntax-top-level-await": "^7.14.5", "@babel/plugin-transform-runtime": "^7.15.0", - "@babel/preset-env": "^7.15.6", + "@babel/preset-env": "^7.15.8", "@graphql-inspector/core": "^2.9.0", - "@graphql-tools/load": "^7.3.0", + "@graphql-tools/load": "^7.3.2", "@jest/globals": "^27.2.0", - "@octokit/rest": "^18.10.0", + "@octokit/rest": "^18.12.0", "@types/github-slugger": "^1.3.0", "@types/imurmurhash": "^0.1.1", "@types/js-cookie": "^2.2.7", - "@types/lodash": "^4.14.172", - "@types/react": "^17.0.20", + "@types/lodash": "^4.14.175", + "@types/react": "^17.0.27", "@types/react-dom": "^17.0.9", "@types/react-syntax-highlighter": "^13.5.2", "@types/uuid": "^8.3.1", @@ -137,7 +137,7 @@ "eslint-plugin-node": "^11.1.0", "eslint-plugin-promise": "^5.1.0", "event-to-promise": "^0.8.0", - "glob": "^7.1.7", + "glob": "^7.2.0", "graphql": "^15.5.3", "heroku-client": "^3.1.0", "http-status-code": "^2.1.0", @@ -149,8 +149,8 @@ "jest": "^27.2.0", "jest-github-actions-reporter": "^1.0.3", "jest-slow-test-reporter": "^1.0.0", - "linkinator": "^2.14.0", - "lint-staged": "^11.1.2", + "linkinator": "^2.14.4", + "lint-staged": "^11.2.2", "make-promises-safe": "^5.1.0", "minimatch": "^3.0.4", "mkdirp": "^1.0.4", @@ -236,19 +236,19 @@ } }, "node_modules/@babel/core": { - "version": "7.15.5", - "resolved": "https://registry.npmjs.org/@babel/core/-/core-7.15.5.tgz", - "integrity": "sha512-pYgXxiwAgQpgM1bNkZsDEq85f0ggXMA5L7c+o3tskGMh2BunCI9QUwB9Z4jpvXUOuMdyGKiGKQiRe11VS6Jzvg==", + "version": "7.15.8", + "resolved": "https://registry.npmjs.org/@babel/core/-/core-7.15.8.tgz", + "integrity": "sha512-3UG9dsxvYBMYwRv+gS41WKHno4K60/9GPy1CJaH6xy3Elq8CTtvtjT5R5jmNhXfCYLX2mTw+7/aq5ak/gOE0og==", "dependencies": { - "@babel/code-frame": "^7.14.5", - "@babel/generator": "^7.15.4", + "@babel/code-frame": "^7.15.8", + "@babel/generator": "^7.15.8", "@babel/helper-compilation-targets": "^7.15.4", - "@babel/helper-module-transforms": "^7.15.4", + "@babel/helper-module-transforms": "^7.15.8", "@babel/helpers": "^7.15.4", - "@babel/parser": "^7.15.5", + "@babel/parser": "^7.15.8", "@babel/template": "^7.15.4", "@babel/traverse": "^7.15.4", - "@babel/types": "^7.15.4", + "@babel/types": "^7.15.6", "convert-source-map": "^1.7.0", "debug": "^4.1.0", "gensync": "^1.0.0-beta.2", @@ -265,9 +265,9 @@ } }, "node_modules/@babel/core/node_modules/@babel/code-frame": { - "version": "7.14.5", - "resolved": "https://registry.npmjs.org/@babel/code-frame/-/code-frame-7.14.5.tgz", - "integrity": "sha512-9pzDqyc6OLDaqe+zbACgFkb6fKMNG6CObKpnYXChRsvYGyEdc7CA2BaqeOM+vOtCS5ndmJicPJhKAwYRI6UfFw==", + "version": "7.15.8", + "resolved": "https://registry.npmjs.org/@babel/code-frame/-/code-frame-7.15.8.tgz", + "integrity": "sha512-2IAnmn8zbvC/jKYhq5Ki9I+DwjlrtMPUCH/CpHvqI4dNnlwHwsxoIhlc8WcYY5LSYknXQtAlFYuHfqAFCvQ4Wg==", "dependencies": { "@babel/highlight": "^7.14.5" }, @@ -341,11 +341,11 @@ } }, "node_modules/@babel/generator": { - "version": "7.15.4", - "resolved": "https://registry.npmjs.org/@babel/generator/-/generator-7.15.4.tgz", - "integrity": "sha512-d3itta0tu+UayjEORPNz6e1T3FtvWlP5N4V5M+lhp/CxT4oAA7/NcScnpRyspUMLK6tu9MNHmQHxRykuN2R7hw==", + "version": "7.15.8", + "resolved": "https://registry.npmjs.org/@babel/generator/-/generator-7.15.8.tgz", + "integrity": "sha512-ECmAKstXbp1cvpTTZciZCgfOt6iN64lR0d+euv3UZisU5awfRawOvg07Utn/qBGuH4bRIEZKrA/4LzZyXhZr8g==", "dependencies": { - "@babel/types": "^7.15.4", + "@babel/types": "^7.15.6", "jsesc": "^2.5.1", "source-map": "^0.5.0" }, @@ -559,18 +559,18 @@ } }, "node_modules/@babel/helper-module-transforms": { - "version": "7.15.4", - "resolved": "https://registry.npmjs.org/@babel/helper-module-transforms/-/helper-module-transforms-7.15.4.tgz", - "integrity": "sha512-9fHHSGE9zTC++KuXLZcB5FKgvlV83Ox+NLUmQTawovwlJ85+QMhk1CnVk406CQVj97LaWod6KVjl2Sfgw9Aktw==", + "version": "7.15.8", + "resolved": "https://registry.npmjs.org/@babel/helper-module-transforms/-/helper-module-transforms-7.15.8.tgz", + "integrity": "sha512-DfAfA6PfpG8t4S6npwzLvTUpp0sS7JrcuaMiy1Y5645laRJIp/LiLGIBbQKaXSInK8tiGNI7FL7L8UvB8gdUZg==", "dependencies": { "@babel/helper-module-imports": "^7.15.4", "@babel/helper-replace-supers": "^7.15.4", "@babel/helper-simple-access": "^7.15.4", "@babel/helper-split-export-declaration": "^7.15.4", - "@babel/helper-validator-identifier": "^7.14.9", + "@babel/helper-validator-identifier": "^7.15.7", "@babel/template": "^7.15.4", "@babel/traverse": "^7.15.4", - "@babel/types": "^7.15.4" + "@babel/types": "^7.15.6" }, "engines": { "node": ">=6.9.0" @@ -658,9 +658,9 @@ } }, "node_modules/@babel/helper-validator-identifier": { - "version": "7.14.9", - "resolved": "https://registry.npmjs.org/@babel/helper-validator-identifier/-/helper-validator-identifier-7.14.9.tgz", - "integrity": "sha512-pQYxPY0UP6IHISRitNe8bsijHex4TWZXi2HwKVsjPiltzlhse2znVcm9Ace510VT1kxIHjGJCZZQBX2gJDbo0g==", + "version": "7.15.7", + "resolved": "https://registry.npmjs.org/@babel/helper-validator-identifier/-/helper-validator-identifier-7.15.7.tgz", + "integrity": "sha512-K4JvCtQqad9OY2+yTU8w+E82ywk/fe+ELNlt1G8z3bVGlZfn/hOcQQsUhGhW/N+tb3fxK800wLtKOE/aM0m72w==", "engines": { "node": ">=6.9.0" } @@ -750,9 +750,9 @@ } }, "node_modules/@babel/parser": { - "version": "7.15.6", - "resolved": "https://registry.npmjs.org/@babel/parser/-/parser-7.15.6.tgz", - "integrity": "sha512-S/TSCcsRuCkmpUuoWijua0Snt+f3ewU/8spLo+4AXJCZfT0bVCzLD5MuOKdrx0mlAptbKzn5AdgEIIKXxXkz9Q==", + "version": "7.15.8", + "resolved": "https://registry.npmjs.org/@babel/parser/-/parser-7.15.8.tgz", + "integrity": "sha512-BRYa3wcQnjS/nqI8Ac94pYYpJfojHVvVXJ97+IDCImX4Jc8W8Xv1+47enbruk+q1etOpsQNwnfFcNGw+gtPGxA==", "bin": { "parser": "bin/babel-parser.js" }, @@ -778,9 +778,9 @@ } }, "node_modules/@babel/plugin-proposal-async-generator-functions": { - "version": "7.15.4", - "resolved": "https://registry.npmjs.org/@babel/plugin-proposal-async-generator-functions/-/plugin-proposal-async-generator-functions-7.15.4.tgz", - "integrity": "sha512-2zt2g5vTXpMC3OmK6uyjvdXptbhBXfA77XGrd3gh93zwG8lZYBLOBImiGBEG0RANu3JqKEACCz5CGk73OJROBw==", + "version": "7.15.8", + "resolved": "https://registry.npmjs.org/@babel/plugin-proposal-async-generator-functions/-/plugin-proposal-async-generator-functions-7.15.8.tgz", + "integrity": "sha512-2Z5F2R2ibINTc63mY7FLqGfEbmofrHU9FitJW1Q7aPaKFhiPvSq6QEt/BoWN5oME3GVyjcRuNNSRbb9LC0CSWA==", "dev": true, "dependencies": { "@babel/helper-plugin-utils": "^7.14.5", @@ -1697,13 +1697,13 @@ } }, "node_modules/@babel/plugin-transform-spread": { - "version": "7.14.6", - "resolved": "https://registry.npmjs.org/@babel/plugin-transform-spread/-/plugin-transform-spread-7.14.6.tgz", - "integrity": "sha512-Zr0x0YroFJku7n7+/HH3A2eIrGMjbmAIbJSVv0IZ+t3U2WUQUA64S/oeied2e+MaGSjmt4alzBCsK9E8gh+fag==", + "version": "7.15.8", + "resolved": "https://registry.npmjs.org/@babel/plugin-transform-spread/-/plugin-transform-spread-7.15.8.tgz", + "integrity": "sha512-/daZ8s2tNaRekl9YJa9X4bzjpeRZLt122cpgFnQPLGUe61PH8zMEBmYqKkW5xF5JUEh5buEGXJoQpqBmIbpmEQ==", "dev": true, "dependencies": { "@babel/helper-plugin-utils": "^7.14.5", - "@babel/helper-skip-transparent-expression-wrappers": "^7.14.5" + "@babel/helper-skip-transparent-expression-wrappers": "^7.15.4" }, "engines": { "node": ">=6.9.0" @@ -1789,9 +1789,9 @@ } }, "node_modules/@babel/preset-env": { - "version": "7.15.6", - "resolved": "https://registry.npmjs.org/@babel/preset-env/-/preset-env-7.15.6.tgz", - "integrity": "sha512-L+6jcGn7EWu7zqaO2uoTDjjMBW+88FXzV8KvrBl2z6MtRNxlsmUNRlZPaNNPUTgqhyC5DHNFk/2Jmra+ublZWw==", + "version": "7.15.8", + "resolved": "https://registry.npmjs.org/@babel/preset-env/-/preset-env-7.15.8.tgz", + "integrity": "sha512-rCC0wH8husJgY4FPbHsiYyiLxSY8oMDJH7Rl6RQMknbN9oDDHhM9RDFvnGM2MgkbUJzSQB4gtuwygY5mCqGSsA==", "dev": true, "dependencies": { "@babel/compat-data": "^7.15.0", @@ -1799,7 +1799,7 @@ "@babel/helper-plugin-utils": "^7.14.5", "@babel/helper-validator-option": "^7.14.5", "@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining": "^7.15.4", - "@babel/plugin-proposal-async-generator-functions": "^7.15.4", + "@babel/plugin-proposal-async-generator-functions": "^7.15.8", "@babel/plugin-proposal-class-properties": "^7.14.5", "@babel/plugin-proposal-class-static-block": "^7.15.4", "@babel/plugin-proposal-dynamic-import": "^7.14.5", @@ -1854,7 +1854,7 @@ "@babel/plugin-transform-regenerator": "^7.14.5", "@babel/plugin-transform-reserved-words": "^7.14.5", "@babel/plugin-transform-shorthand-properties": "^7.14.5", - "@babel/plugin-transform-spread": "^7.14.6", + "@babel/plugin-transform-spread": "^7.15.8", "@babel/plugin-transform-sticky-regex": "^7.14.5", "@babel/plugin-transform-template-literals": "^7.14.5", "@babel/plugin-transform-typeof-symbol": "^7.14.5", @@ -1863,7 +1863,7 @@ "@babel/preset-modules": "^0.1.4", "@babel/types": "^7.15.6", "babel-plugin-polyfill-corejs2": "^0.2.2", - "babel-plugin-polyfill-corejs3": "^0.2.2", + "babel-plugin-polyfill-corejs3": "^0.2.5", "babel-plugin-polyfill-regenerator": "^0.2.2", "core-js-compat": "^3.16.0", "semver": "^6.3.0" @@ -2171,13 +2171,13 @@ "dev": true }, "node_modules/@graphql-tools/load": { - "version": "7.3.0", - "resolved": "https://registry.npmjs.org/@graphql-tools/load/-/load-7.3.0.tgz", - "integrity": "sha512-ZVipT7yzOpf/DJ2sLI3xGwnULVFp/icu7RFEgDo2ZX0WHiS7EjWZ0cegxEm87+WN4fMwpiysRLzWx67VIHwKGA==", + "version": "7.3.2", + "resolved": "https://registry.npmjs.org/@graphql-tools/load/-/load-7.3.2.tgz", + "integrity": "sha512-tB03MGOlgKkoP6YyzIl/saTYshuLWxQy2JebhYL6gy3XsWmSE7ae1WAL3p+G0pyfw66HaMu905omyulu1VkfXw==", "dev": true, "dependencies": { "@graphql-tools/schema": "8.2.0", - "@graphql-tools/utils": "^8.2.0", + "@graphql-tools/utils": "^8.2.3", "p-limit": "3.1.0", "tslib": "~2.3.0" }, @@ -2247,9 +2247,9 @@ "dev": true }, "node_modules/@graphql-tools/utils": { - "version": "8.2.2", - "resolved": "https://registry.npmjs.org/@graphql-tools/utils/-/utils-8.2.2.tgz", - "integrity": "sha512-29FFY5U4lpXuBiW9dRvuWnBVwGhWbGLa2leZcAMU/Pz47Cr/QLZGVgpLBV9rt+Gbs7wyIJM7t7EuksPs0RDm3g==", + "version": "8.2.5", + "resolved": "https://registry.npmjs.org/@graphql-tools/utils/-/utils-8.2.5.tgz", + "integrity": "sha512-k/Rktklhy22dQfbJLKiLGfQymQCTr6Rd2BilC7g2Yk6wFSzVLYr8jeXNoTD+/p61XBQzBjTVayskvaMvNS3BDg==", "dev": true, "dependencies": { "tslib": "~2.3.0" @@ -3519,18 +3519,18 @@ } }, "node_modules/@octokit/openapi-types": { - "version": "10.1.5", - "resolved": "https://registry.npmjs.org/@octokit/openapi-types/-/openapi-types-10.1.5.tgz", - "integrity": "sha512-OoShNYzhAU8p8JbGHe1rRs1GIErRtmN2230AQCJAjL5lc0AUU5OhppVe6693HIZ2eCBLUhoLPhnnnmQ5ASH7Wg==", + "version": "11.0.0", + "resolved": "https://registry.npmjs.org/@octokit/openapi-types/-/openapi-types-11.0.0.tgz", + "integrity": "sha512-QeMW4h18cEm53ojYufACSRgq3rrQg4BibVcsHytXmbJ+otmXSelr1BCBCEi8q7nqGkYJyGQX30DoULENIgJ8BA==", "dev": true }, "node_modules/@octokit/plugin-paginate-rest": { - "version": "2.16.2", - "resolved": "https://registry.npmjs.org/@octokit/plugin-paginate-rest/-/plugin-paginate-rest-2.16.2.tgz", - "integrity": "sha512-WF5/MTPnFgYH6rMGuxBvbxX2S/3ygNWylakgD7njKES0Qwk5e+d/L6r/BYXSw7B6xJJ3hlwIAmUmOxxYrR+Q8A==", + "version": "2.16.8", + "resolved": "https://registry.npmjs.org/@octokit/plugin-paginate-rest/-/plugin-paginate-rest-2.16.8.tgz", + "integrity": "sha512-VZZYeNNwCkC2XoTUFouTpFdR2esSPuJb4U58iUxeYu4vQ1AUzCs6AI+gf4bL413CQ8DZhkxASflfLWzcp+9shQ==", "dev": true, "dependencies": { - "@octokit/types": "^6.27.2" + "@octokit/types": "^6.32.0" }, "peerDependencies": { "@octokit/core": ">=2" @@ -3546,12 +3546,12 @@ } }, "node_modules/@octokit/plugin-rest-endpoint-methods": { - "version": "5.10.3", - "resolved": "https://registry.npmjs.org/@octokit/plugin-rest-endpoint-methods/-/plugin-rest-endpoint-methods-5.10.3.tgz", - "integrity": "sha512-eAT4gje+VR9xdSlhuHWNXsNLpiODqdqz8jqShMgaxRH82Le2nS6EV6LAo3QPZ05Fso5oGmDfJF6eq9vs1cEhdA==", + "version": "5.12.0", + "resolved": "https://registry.npmjs.org/@octokit/plugin-rest-endpoint-methods/-/plugin-rest-endpoint-methods-5.12.0.tgz", + "integrity": "sha512-OD3Rv660YzXSmhTr8g8kpLvLq3Z5ADvLxtb9a8+1I4S2EqV6YQTHeJwVC5I6vwvV5tMmnj3oeRn7OWc0eODwQw==", "dev": true, "dependencies": { - "@octokit/types": "^6.27.2", + "@octokit/types": "^6.32.0", "deprecation": "^2.3.1" }, "peerDependencies": { @@ -3602,24 +3602,24 @@ } }, "node_modules/@octokit/rest": { - "version": "18.10.0", - "resolved": "https://registry.npmjs.org/@octokit/rest/-/rest-18.10.0.tgz", - "integrity": "sha512-esHR5OKy38bccL/sajHqZudZCvmv4yjovMJzyXlphaUo7xykmtOdILGJ3aAm0mFHmMLmPFmDMJXf39cAjNJsrw==", + "version": "18.12.0", + "resolved": "https://registry.npmjs.org/@octokit/rest/-/rest-18.12.0.tgz", + "integrity": "sha512-gDPiOHlyGavxr72y0guQEhLsemgVjwRePayJ+FcKc2SJqKUbxbkvf5kAZEWA/MKvsfYlQAMVzNJE3ezQcxMJ2Q==", "dev": true, "dependencies": { "@octokit/core": "^3.5.1", - "@octokit/plugin-paginate-rest": "^2.16.0", + "@octokit/plugin-paginate-rest": "^2.16.8", "@octokit/plugin-request-log": "^1.0.4", - "@octokit/plugin-rest-endpoint-methods": "^5.9.0" + "@octokit/plugin-rest-endpoint-methods": "^5.12.0" } }, "node_modules/@octokit/types": { - "version": "6.27.2", - "resolved": "https://registry.npmjs.org/@octokit/types/-/types-6.27.2.tgz", - "integrity": "sha512-AgajmAJh7LhStgaEaNoY1N7znst2q07CKZVdnVB/V4tmitMbk+qijmD0IkkSKulXE5RVLbJjQikJF9+XLqhsVA==", + "version": "6.32.0", + "resolved": "https://registry.npmjs.org/@octokit/types/-/types-6.32.0.tgz", + "integrity": "sha512-7CFlMfpX78PbvGnQZfQ3pD246RGTLITDnLCyYgTOtwNPIdTKMGs/8dJiZA3Fh5vXuZYqu/YHH32GboK7xnZ0ag==", "dev": true, "dependencies": { - "@octokit/openapi-types": "^10.1.5" + "@octokit/openapi-types": "^11.0.0" } }, "node_modules/@primer/components": { @@ -4052,9 +4052,9 @@ } }, "node_modules/@types/lodash": { - "version": "4.14.172", - "resolved": "https://registry.npmjs.org/@types/lodash/-/lodash-4.14.172.tgz", - "integrity": "sha512-/BHF5HAx3em7/KkzVKm3LrsD6HZAXuXO1AJZQ3cRRBZj4oHZDviWPYu0aEplAqDFNHZPW6d3G7KN+ONcCCC7pw==", + "version": "4.14.175", + "resolved": "https://registry.npmjs.org/@types/lodash/-/lodash-4.14.175.tgz", + "integrity": "sha512-XmdEOrKQ8a1Y/yxQFOMbC47G/V2VDO1GvMRnl4O75M4GW/abC5tnfzadQYkqEveqRM1dEJGFFegfPNA2vvx2iw==", "dev": true }, "node_modules/@types/mdast": { @@ -4115,9 +4115,9 @@ "integrity": "sha512-KfRL3PuHmqQLOG+2tGpRO26Ctg+Cq1E01D2DMriKEATHgWLfeNDmq9e29Q9WIky0dQ3NPkd1mzYH8Lm936Z9qw==" }, "node_modules/@types/react": { - "version": "17.0.20", - "resolved": "https://registry.npmjs.org/@types/react/-/react-17.0.20.tgz", - "integrity": "sha512-wWZrPlihslrPpcKyCSlmIlruakxr57/buQN1RjlIeaaTWDLtJkTtRW429MoQJergvVKc4IWBpRhWw7YNh/7GVA==", + "version": "17.0.27", + "resolved": "https://registry.npmjs.org/@types/react/-/react-17.0.27.tgz", + "integrity": "sha512-zgiJwtsggVGtr53MndV7jfiUESTqrbxOcBvwfe6KS/9bzaVPCTDieTWnFNecVNx6EAaapg5xsLLWFfHHR437AA==", "dependencies": { "@types/prop-types": "*", "@types/scheduler": "*", @@ -4794,6 +4794,11 @@ "node": ">=0.4.0" } }, + "node_modules/acorn-es7-plugin": { + "version": "1.1.7", + "resolved": "https://registry.npmjs.org/acorn-es7-plugin/-/acorn-es7-plugin-1.1.7.tgz", + "integrity": "sha1-8u4fMiipDurRJF+asZIusucdM2s=" + }, "node_modules/acorn-globals": { "version": "6.0.0", "resolved": "https://registry.npmjs.org/acorn-globals/-/acorn-globals-6.0.0.tgz", @@ -4898,9 +4903,9 @@ } }, "node_modules/ajv": { - "version": "8.4.0", - "resolved": "https://registry.npmjs.org/ajv/-/ajv-8.4.0.tgz", - "integrity": "sha512-7QD2l6+KBSLwf+7MuYocbWvRPdOu63/trReTLu2KFwkgctnub1auoF+Y1WYcm09CTM7quuscrzqmASaLHC/K4Q==", + "version": "8.6.3", + "resolved": "https://registry.npmjs.org/ajv/-/ajv-8.6.3.tgz", + "integrity": "sha512-SMJOdDP6LqTkD0Uq8qLi+gMwSt0imXLSV080qFVwJCpH9U6Mb+SUGHAXM0KNbcBPguytWyvFxcHgMLe2D2XSpw==", "dependencies": { "fast-deep-equal": "^3.1.1", "json-schema-traverse": "^1.0.0", @@ -5372,12 +5377,12 @@ } }, "node_modules/axios": { - "version": "0.21.1", - "resolved": "https://registry.npmjs.org/axios/-/axios-0.21.1.tgz", - "integrity": "sha512-dKQiRHxGD9PPRIUNIWvZhPTPpl1rf/OxTYKsqKUDjBwYylTvV7SjSHJb9ratfyzM6wCdLCOYLzs73qpg5c4iGA==", + "version": "0.21.4", + "resolved": "https://registry.npmjs.org/axios/-/axios-0.21.4.tgz", + "integrity": "sha512-ut5vewkiu8jjGBdqpM44XxjuCjq9LAKeHVmoVfHVzy8eHgxxq8SbAVQNovDA8mVi05kP0Ea/n/UzcSHcTJQfNg==", "devOptional": true, "dependencies": { - "follow-redirects": "^1.10.0" + "follow-redirects": "^1.14.0" } }, "node_modules/axobject-query": { @@ -5725,13 +5730,13 @@ } }, "node_modules/babel-plugin-polyfill-corejs3": { - "version": "0.2.4", - "resolved": "https://registry.npmjs.org/babel-plugin-polyfill-corejs3/-/babel-plugin-polyfill-corejs3-0.2.4.tgz", - "integrity": "sha512-z3HnJE5TY/j4EFEa/qpQMSbcUJZ5JQi+3UFjXzn6pQCmIKc5Ug5j98SuYyH+m4xQnvKlMDIW4plLfgyVnd0IcQ==", + "version": "0.2.5", + "resolved": "https://registry.npmjs.org/babel-plugin-polyfill-corejs3/-/babel-plugin-polyfill-corejs3-0.2.5.tgz", + "integrity": "sha512-ninF5MQNwAX9Z7c9ED+H2pGt1mXdP4TqzlHKyPIYmJIYz0N+++uwdM7RnJukklhzJ54Q84vA4ZJkgs7lu5vqcw==", "dev": true, "dependencies": { "@babel/helper-define-polyfill-provider": "^0.2.2", - "core-js-compat": "^3.14.0" + "core-js-compat": "^3.16.2" }, "peerDependencies": { "@babel/core": "^7.0.0-0" @@ -6924,6 +6929,14 @@ "url": "https://github.com/sponsors/ljharb" } }, + "node_modules/call-signature": { + "version": "0.0.2", + "resolved": "https://registry.npmjs.org/call-signature/-/call-signature-0.0.2.tgz", + "integrity": "sha1-qEq8glpV70yysCi9dOIFpluaSZY=", + "engines": { + "node": ">=0.10.0" + } + }, "node_modules/callsites": { "version": "3.1.0", "resolved": "https://registry.npmjs.org/callsites/-/callsites-3.1.0.tgz", @@ -7300,9 +7313,9 @@ } }, "node_modules/cheerio-select/node_modules/nth-check": { - "version": "2.0.0", - "resolved": "https://registry.npmjs.org/nth-check/-/nth-check-2.0.0.tgz", - "integrity": "sha512-i4sc/Kj8htBrAiH1viZ0TgU8Y5XqCaV/FziYK6TBczxmeKm3AEFWqqF3195yKudrarqy7Zu80Ra5dobFjn9X/Q==", + "version": "2.0.1", + "resolved": "https://registry.npmjs.org/nth-check/-/nth-check-2.0.1.tgz", + "integrity": "sha512-it1vE95zF6dTT9lBsYbxvqh0Soy4SPowchj0UBGj/V6cTPnXXtQOPUbhZ6CmGzAD/rW22LQK6E96pcdJXk4A4w==", "dependencies": { "boolbase": "^1.0.0" }, @@ -7795,9 +7808,9 @@ "integrity": "sha1-p9BVi9icQveV3UIyj3QIMcpTvCU=" }, "node_modules/colorette": { - "version": "1.3.0", - "resolved": "https://registry.npmjs.org/colorette/-/colorette-1.3.0.tgz", - "integrity": "sha512-ecORCqbSFP7Wm8Y6lyqMJjexBQqXSF7SSeaTyGGphogUjBlFP9m9o08wy86HL2uB7fMTxtOUzLMk7ogKcxMg1w==" + "version": "1.4.0", + "resolved": "https://registry.npmjs.org/colorette/-/colorette-1.4.0.tgz", + "integrity": "sha512-Y2oEozpomLn7Q3HFP7dpww7AtMJplbM9lGZP6RDfHqmbeRjiwRg4n6VM6j4KLmRke85uWEI7JqF17f3pqdRA0g==" }, "node_modules/combined-stream": { "version": "1.0.8", @@ -8073,7 +8086,6 @@ "resolved": "https://registry.npmjs.org/core-js/-/core-js-2.6.12.tgz", "integrity": "sha512-Kb2wC0fvsWfQrgk8HU5lW6U/Lcs8+9aaYcy4ZFc6DDlo4nZ7n70dEgE5rtR0oG6ufKDUnrwfWL1mXR5ljDatrQ==", "deprecated": "core-js@<3.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.", - "dev": true, "hasInstallScript": true }, "node_modules/core-js-compat": { @@ -8151,9 +8163,9 @@ } }, "node_modules/cosmiconfig": { - "version": "7.0.0", - "resolved": "https://registry.npmjs.org/cosmiconfig/-/cosmiconfig-7.0.0.tgz", - "integrity": "sha512-pondGvTuVYDk++upghXJabWzL6Kxu6f26ljFw64Swq9v6sQPUL3EUlVDV56diOjpCayKihL6hVe8exIACU4XcA==", + "version": "7.0.1", + "resolved": "https://registry.npmjs.org/cosmiconfig/-/cosmiconfig-7.0.1.tgz", + "integrity": "sha512-a1YWNUV2HwGimB7dU2s1wUMurNKjpx60HxBB6xUM8Re+2s1g1IIfJvFR0/iCF+XHdE0GMTKTuLR32UQff4TEyQ==", "dev": true, "dependencies": { "@types/parse-json": "^4.0.0", @@ -8776,6 +8788,11 @@ "integrity": "sha512-VvlVYY+VDJe639yHs5PHISzdWTLL3Aw8rO4cvUtwvoxFd6FHbE4OpHHcde52M6096uYYazAmd4l0o5VuFRO2WA==", "optional": true }, + "node_modules/diff-match-patch": { + "version": "1.0.5", + "resolved": "https://registry.npmjs.org/diff-match-patch/-/diff-match-patch-1.0.5.tgz", + "integrity": "sha512-IayShXAgj/QMXgB0IWmKx+rOPuGMhqm5w6jvFxmVenXKIzRqTAAsbBPT3kWQeGANj3jGgvcvv4yK6SxqYmikgw==" + }, "node_modules/diff-sequences": { "version": "27.0.6", "resolved": "https://registry.npmjs.org/diff-sequences/-/diff-sequences-27.0.6.tgz", @@ -9089,6 +9106,11 @@ "stream-shift": "^1.0.0" } }, + "node_modules/eastasianwidth": { + "version": "0.2.0", + "resolved": "https://registry.npmjs.org/eastasianwidth/-/eastasianwidth-0.2.0.tgz", + "integrity": "sha512-I88TYZWc9XiYHRQ4/3c5rjjfgkjhLyW2luGIheGERbNQ6OY7yTybanSpDXZa8y7VUP9YmDcYa+eyq4ca7iLqWA==" + }, "node_modules/ee-first": { "version": "1.1.1", "resolved": "https://registry.npmjs.org/ee-first/-/ee-first-1.1.1.tgz", @@ -9143,6 +9165,24 @@ "node": ">= 0.10" } }, + "node_modules/empower": { + "version": "1.3.1", + "resolved": "https://registry.npmjs.org/empower/-/empower-1.3.1.tgz", + "integrity": "sha512-uB6/ViBaawOO/uujFADTK3SqdYlxYNn+N4usK9MRKZ4Hbn/1QSy8k2PezxCA2/+JGbF8vd/eOfghZ90oOSDZCA==", + "dependencies": { + "core-js": "^2.0.0", + "empower-core": "^1.2.0" + } + }, + "node_modules/empower-core": { + "version": "1.2.0", + "resolved": "https://registry.npmjs.org/empower-core/-/empower-core-1.2.0.tgz", + "integrity": "sha512-g6+K6Geyc1o6FdXs9HwrXleCFan7d66G5xSCfSF7x1mJDCes6t0om9lFQG3zOrzh3Bkb/45N0cZ5Gqsf7YrzGQ==", + "dependencies": { + "call-signature": "0.0.2", + "core-js": "^2.0.0" + } + }, "node_modules/encodeurl": { "version": "1.0.2", "resolved": "https://registry.npmjs.org/encodeurl/-/encodeurl-1.0.2.tgz", @@ -10043,6 +10083,14 @@ "node": ">=4" } }, + "node_modules/espurify": { + "version": "1.8.1", + "resolved": "https://registry.npmjs.org/espurify/-/espurify-1.8.1.tgz", + "integrity": "sha512-ZDko6eY/o+D/gHCWyHTU85mKDgYcS4FJj7S+YD6WIInm7GQ6AnOjmcL4+buFV/JOztVLELi/7MmuGU5NHta0Mg==", + "dependencies": { + "core-js": "^2.0.0" + } + }, "node_modules/esquery": { "version": "1.4.0", "resolved": "https://registry.npmjs.org/esquery/-/esquery-1.4.0.tgz", @@ -10428,9 +10476,9 @@ } }, "node_modules/express-rate-limit": { - "version": "5.3.0", - "resolved": "https://registry.npmjs.org/express-rate-limit/-/express-rate-limit-5.3.0.tgz", - "integrity": "sha512-qJhfEgCnmteSeZAeuOKQ2WEIFTX5ajrzE0xS6gCOBCoRQcU+xEzQmgYQQTpzCcqUAAzTEtu4YEih4pnLfvNtew==" + "version": "5.4.1", + "resolved": "https://registry.npmjs.org/express-rate-limit/-/express-rate-limit-5.4.1.tgz", + "integrity": "sha512-ZQh2h3qiu7wWdvWNYHznBhaOp2ZIXNnT4hl2Ff608STeWtCuJ251NzqQlk7mo5wnO2HmrydBYHuVA9Z3S3ZtXg==" }, "node_modules/express-timeout-handler": { "version": "2.2.2", @@ -11288,9 +11336,9 @@ "integrity": "sha512-w0dzqw/nt51xMVmlaV1+JRzN+oCa1KfcgGEWhxUG16wbdA+Xnt/yoFO8Z8x/V82ZcZ0wy6ln9QDup5avbhiDhQ==" }, "node_modules/glob": { - "version": "7.1.7", - "resolved": "https://registry.npmjs.org/glob/-/glob-7.1.7.tgz", - "integrity": "sha512-OvD9ENzPLbegENnYP5UUfJIirTg4+XwMWGaQfQTY0JenxNvvIKP3U3/tAQSPIu/lHxXYSZmpXlUHeqAIdKzBLQ==", + "version": "7.2.0", + "resolved": "https://registry.npmjs.org/glob/-/glob-7.2.0.tgz", + "integrity": "sha512-lmLf6gtyrPq8tTjSmrO94wBeQbFR3HbLHbuyD69wuyQkImp2hWqMGB47OX65FBkPffO641IP9jWa1z4ivqG26Q==", "dependencies": { "fs.realpath": "^1.0.0", "inflight": "^1.0.4", @@ -11953,9 +12001,9 @@ } }, "node_modules/hast-util-select/node_modules/nth-check": { - "version": "2.0.0", - "resolved": "https://registry.npmjs.org/nth-check/-/nth-check-2.0.0.tgz", - "integrity": "sha512-i4sc/Kj8htBrAiH1viZ0TgU8Y5XqCaV/FziYK6TBczxmeKm3AEFWqqF3195yKudrarqy7Zu80Ra5dobFjn9X/Q==", + "version": "2.0.1", + "resolved": "https://registry.npmjs.org/nth-check/-/nth-check-2.0.1.tgz", + "integrity": "sha512-it1vE95zF6dTT9lBsYbxvqh0Soy4SPowchj0UBGj/V6cTPnXXtQOPUbhZ6CmGzAD/rW22LQK6E96pcdJXk4A4w==", "dependencies": { "boolbase": "^1.0.0" }, @@ -12184,9 +12232,9 @@ } }, "node_modules/hot-shots": { - "version": "8.5.1", - "resolved": "https://registry.npmjs.org/hot-shots/-/hot-shots-8.5.1.tgz", - "integrity": "sha512-LHqIVuoFDdKvtn9nNAC16KgdiinVsPHKSNuGIMoFlAxFzHL782SaWgQ/MTuOkPbwgEEtEmOGaiBeH25UeL/gRA==", + "version": "8.5.2", + "resolved": "https://registry.npmjs.org/hot-shots/-/hot-shots-8.5.2.tgz", + "integrity": "sha512-1CKCtbYU28KtRriRW+mdOZzKce0WPqU0FOYE4bYs3gD1bFpOrYzQDXfQ09Qz9dJPEltasDOGhFKiYaiuW/j9Dg==", "engines": { "node": ">=6.0.0" }, @@ -12567,6 +12615,11 @@ "node": ">=8" } }, + "node_modules/indexof": { + "version": "0.0.1", + "resolved": "https://registry.npmjs.org/indexof/-/indexof-0.0.1.tgz", + "integrity": "sha1-gtwzbSMrkGIXnQWrMpOmYFn9Q10=" + }, "node_modules/infer-owner": { "version": "1.0.4", "resolved": "https://registry.npmjs.org/infer-owner/-/infer-owner-1.0.4.tgz", @@ -13098,18 +13151,6 @@ "integrity": "sha1-5HnICFjfDBsR3dppQPlgEfzaSpo=", "dev": true }, - "node_modules/is-unicode-supported": { - "version": "0.1.0", - "resolved": "https://registry.npmjs.org/is-unicode-supported/-/is-unicode-supported-0.1.0.tgz", - "integrity": "sha512-knxG2q4UC3u8stRGyAVJCOdxFmv5DZiRcdlIaAQXAbSfJya+OhopNotLQrstBhququ4ZpuKbDc/8S6mgXgPFPw==", - "dev": true, - "engines": { - "node": ">=10" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, "node_modules/is-url": { "version": "1.2.4", "resolved": "https://registry.npmjs.org/is-url/-/is-url-1.2.4.tgz", @@ -14617,9 +14658,9 @@ } }, "node_modules/jszip": { - "version": "3.6.0", - "resolved": "https://registry.npmjs.org/jszip/-/jszip-3.6.0.tgz", - "integrity": "sha512-jgnQoG9LKnWO3mnVNBnfhkh0QknICd1FGSrXcgrl67zioyJ4wgx25o9ZqwNtrROSflGBCGYnJfjrIyRIby1OoQ==", + "version": "3.7.1", + "resolved": "https://registry.npmjs.org/jszip/-/jszip-3.7.1.tgz", + "integrity": "sha512-ghL0tz1XG9ZEmRMcEN2vt7xabrDdqHHeykgARpmZ0BiIctWxM47Vt63ZO2dnp4QYt/xJVLLy5Zv1l/xRdh2byg==", "optional": true, "dependencies": { "lie": "~3.3.0", @@ -14735,16 +14776,16 @@ "dev": true }, "node_modules/linkinator": { - "version": "2.14.0", - "resolved": "https://registry.npmjs.org/linkinator/-/linkinator-2.14.0.tgz", - "integrity": "sha512-7OvAgx0Ml7vByog2NsMg3sH+cH8pZyvMt1BhQE6mGnyQONXtKQvzuynLCEFPznVgPpQBQ1onvDP2udyVafvINQ==", + "version": "2.14.4", + "resolved": "https://registry.npmjs.org/linkinator/-/linkinator-2.14.4.tgz", + "integrity": "sha512-ADxb8C9k9LUAHFZCsKZnB+TtxTqVPiL86zQpmMp9x+aarrhY9YBV12msb87C9IR9DBxaohonhIfMVvrJW4E7Wg==", "dev": true, "dependencies": { "chalk": "^4.0.0", - "cheerio": "^1.0.0-rc.10", "escape-html": "^1.0.3", "gaxios": "^4.0.0", "glob": "^7.1.6", + "htmlparser2": "^7.1.2", "jsonexport": "^3.0.0", "marked": "^2.0.0", "meow": "^9.0.0", @@ -14847,6 +14888,82 @@ "integrity": "sha512-dOy+3AuW3a2wNbZHIuMZpTcgjGuLU/uBL/ubcZF9OXbDo8ff4O8yVp5Bf0efS8uEoYo5q4Fx7dY9OgQGXgAsQA==", "dev": true }, + "node_modules/linkinator/node_modules/dom-serializer": { + "version": "1.3.2", + "resolved": "https://registry.npmjs.org/dom-serializer/-/dom-serializer-1.3.2.tgz", + "integrity": "sha512-5c54Bk5Dw4qAxNOI1pFEizPSjVsx5+bpJKmL2kPn8JhBUq2q09tTCa3mjijun2NfK78NMouDYNMBkOrPZiS+ig==", + "dev": true, + "dependencies": { + "domelementtype": "^2.0.1", + "domhandler": "^4.2.0", + "entities": "^2.0.0" + }, + "funding": { + "url": "https://github.com/cheeriojs/dom-serializer?sponsor=1" + } + }, + "node_modules/linkinator/node_modules/dom-serializer/node_modules/entities": { + "version": "2.2.0", + "resolved": "https://registry.npmjs.org/entities/-/entities-2.2.0.tgz", + "integrity": "sha512-p92if5Nz619I0w+akJrLZH0MX0Pb5DX39XOwQTtXSdQQOaYH03S1uIQp4mhOZtAXrxq4ViO67YTiLBo2638o9A==", + "dev": true, + "funding": { + "url": "https://github.com/fb55/entities?sponsor=1" + } + }, + "node_modules/linkinator/node_modules/domelementtype": { + "version": "2.2.0", + "resolved": "https://registry.npmjs.org/domelementtype/-/domelementtype-2.2.0.tgz", + "integrity": "sha512-DtBMo82pv1dFtUmHyr48beiuq792Sxohr+8Hm9zoxklYPfa6n0Z3Byjj2IV7bmr2IyqClnqEQhfgHJJ5QF0R5A==", + "dev": true, + "funding": [ + { + "type": "github", + "url": "https://github.com/sponsors/fb55" + } + ] + }, + "node_modules/linkinator/node_modules/domhandler": { + "version": "4.2.2", + "resolved": "https://registry.npmjs.org/domhandler/-/domhandler-4.2.2.tgz", + "integrity": "sha512-PzE9aBMsdZO8TK4BnuJwH0QT41wgMbRzuZrHUcpYncEjmQazq8QEaBWgLG7ZyC/DAZKEgglpIA6j4Qn/HmxS3w==", + "dev": true, + "dependencies": { + "domelementtype": "^2.2.0" + }, + "engines": { + "node": ">= 4" + }, + "funding": { + "url": "https://github.com/fb55/domhandler?sponsor=1" + } + }, + "node_modules/linkinator/node_modules/domutils": { + "version": "2.8.0", + "resolved": "https://registry.npmjs.org/domutils/-/domutils-2.8.0.tgz", + "integrity": "sha512-w96Cjofp72M5IIhpjgobBimYEfoPjx1Vx0BSX9P30WBdZW2WIKU0T1Bd0kz2eNZ9ikjKgHbEyKx8BB6H1L3h3A==", + "dev": true, + "dependencies": { + "dom-serializer": "^1.0.1", + "domelementtype": "^2.2.0", + "domhandler": "^4.2.0" + }, + "funding": { + "url": "https://github.com/fb55/domutils?sponsor=1" + } + }, + "node_modules/linkinator/node_modules/entities": { + "version": "3.0.1", + "resolved": "https://registry.npmjs.org/entities/-/entities-3.0.1.tgz", + "integrity": "sha512-WiyBqoomrwMdFG1e0kqvASYfnlb0lp8M5o5Fw2OFq1hNZxxcNk8Ik0Xm7LxzBhuidnZB/UtBqVCgUz3kBOP51Q==", + "dev": true, + "engines": { + "node": ">=0.12" + }, + "funding": { + "url": "https://github.com/fb55/entities?sponsor=1" + } + }, "node_modules/linkinator/node_modules/global-dirs": { "version": "3.0.0", "resolved": "https://registry.npmjs.org/global-dirs/-/global-dirs-3.0.0.tgz", @@ -14862,6 +14979,25 @@ "url": "https://github.com/sponsors/sindresorhus" } }, + "node_modules/linkinator/node_modules/htmlparser2": { + "version": "7.1.2", + "resolved": "https://registry.npmjs.org/htmlparser2/-/htmlparser2-7.1.2.tgz", + "integrity": "sha512-d6cqsbJba2nRdg8WW2okyD4ceonFHn9jLFxhwlNcLhQWcFPdxXeJulgOLjLKtAK9T6ahd+GQNZwG9fjmGW7lyg==", + "dev": true, + "funding": [ + "https://github.com/fb55/htmlparser2?sponsor=1", + { + "type": "github", + "url": "https://github.com/sponsors/fb55" + } + ], + "dependencies": { + "domelementtype": "^2.0.1", + "domhandler": "^4.2.2", + "domutils": "^2.8.0", + "entities": "^3.0.1" + } + }, "node_modules/linkinator/node_modules/is-installed-globally": { "version": "0.4.0", "resolved": "https://registry.npmjs.org/is-installed-globally/-/is-installed-globally-0.4.0.tgz", @@ -14972,25 +15108,25 @@ } }, "node_modules/lint-staged": { - "version": "11.1.2", - "resolved": "https://registry.npmjs.org/lint-staged/-/lint-staged-11.1.2.tgz", - "integrity": "sha512-6lYpNoA9wGqkL6Hew/4n1H6lRqF3qCsujVT0Oq5Z4hiSAM7S6NksPJ3gnr7A7R52xCtiZMcEUNNQ6d6X5Bvh9w==", + "version": "11.2.2", + "resolved": "https://registry.npmjs.org/lint-staged/-/lint-staged-11.2.2.tgz", + "integrity": "sha512-rbtLCRTyndPJvtjpLwVjjb6K91jQrJ06oNArA4igPTGYlDCrJMIFbNDUAQGa4GRd8AjUBHkAAmq+K38tcmMaAQ==", "dev": true, "dependencies": { - "chalk": "^4.1.1", - "cli-truncate": "^2.1.0", - "commander": "^7.2.0", - "cosmiconfig": "^7.0.0", - "debug": "^4.3.1", + "cli-truncate": "2.1.0", + "colorette": "^1.4.0", + "commander": "^8.2.0", + "cosmiconfig": "^7.0.1", + "debug": "^4.3.2", "enquirer": "^2.3.6", - "execa": "^5.0.0", - "listr2": "^3.8.2", - "log-symbols": "^4.1.0", + "execa": "^5.1.1", + "listr2": "^3.12.2", "micromatch": "^4.0.4", "normalize-path": "^3.0.0", "please-upgrade-node": "^3.2.0", "string-argv": "0.3.1", - "stringify-object": "^3.3.0" + "stringify-object": "3.3.0", + "supports-color": "8.1.1" }, "bin": { "lint-staged": "bin/lint-staged.js" @@ -14999,15 +15135,6 @@ "url": "https://opencollective.com/lint-staged" } }, - "node_modules/lint-staged/node_modules/commander": { - "version": "7.2.0", - "resolved": "https://registry.npmjs.org/commander/-/commander-7.2.0.tgz", - "integrity": "sha512-QrWXB+ZQSVPmIWIhtEO9H+gwHaMGYiF5ChvoJ+K9ZGHG/sVsa6yiesAD1GC/x46sET00Xlwo1u49RVVVzvcSkw==", - "dev": true, - "engines": { - "node": ">= 10" - } - }, "node_modules/lint-staged/node_modules/debug": { "version": "4.3.2", "resolved": "https://registry.npmjs.org/debug/-/debug-4.3.2.tgz", @@ -15025,12 +15152,36 @@ } } }, + "node_modules/lint-staged/node_modules/has-flag": { + "version": "4.0.0", + "resolved": "https://registry.npmjs.org/has-flag/-/has-flag-4.0.0.tgz", + "integrity": "sha512-EykJT/Q1KjTWctppgIAgfSO0tKVuZUjhgMr17kqTumMl6Afv3EISleU7qZUzoXDFTAHTDC4NOoG/ZxU3EvlMPQ==", + "dev": true, + "engines": { + "node": ">=8" + } + }, "node_modules/lint-staged/node_modules/ms": { "version": "2.1.2", "resolved": "https://registry.npmjs.org/ms/-/ms-2.1.2.tgz", "integrity": "sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w==", "dev": true }, + "node_modules/lint-staged/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/liquidjs": { "version": "9.22.1", "resolved": "https://registry.npmjs.org/liquidjs/-/liquidjs-9.22.1.tgz", @@ -15048,13 +15199,13 @@ } }, "node_modules/listr2": { - "version": "3.10.0", - "resolved": "https://registry.npmjs.org/listr2/-/listr2-3.10.0.tgz", - "integrity": "sha512-eP40ZHihu70sSmqFNbNy2NL1YwImmlMmPh9WO5sLmPDleurMHt3n+SwEWNu2kzKScexZnkyFtc1VI0z/TGlmpw==", + "version": "3.12.2", + "resolved": "https://registry.npmjs.org/listr2/-/listr2-3.12.2.tgz", + "integrity": "sha512-64xC2CJ/As/xgVI3wbhlPWVPx0wfTqbUAkpb7bjDi0thSWMqrf07UFhrfsGoo8YSXmF049Rp9C0cjLC8rZxK9A==", "dev": true, "dependencies": { "cli-truncate": "^2.1.0", - "colorette": "^1.2.2", + "colorette": "^1.4.0", "log-update": "^4.0.0", "p-map": "^4.0.0", "rxjs": "^6.6.7", @@ -15069,9 +15220,9 @@ } }, "node_modules/listr2/node_modules/ansi-regex": { - "version": "5.0.0", - "resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.0.tgz", - "integrity": "sha512-bY6fj56OUQ0hU1KjFNDQuJFezqKdrAyFdIevADiqrWHwSlbmBNMHp5ak2f40Pm8JTFyM2mqxkG6ngkHO11f/lg==", + "version": "5.0.1", + "resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.1.tgz", + "integrity": "sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==", "dev": true, "engines": { "node": ">=8" @@ -15111,12 +15262,12 @@ "dev": true }, "node_modules/listr2/node_modules/strip-ansi": { - "version": "6.0.0", - "resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-6.0.0.tgz", - "integrity": "sha512-AuvKTrTfQNYNIctbR1K/YGTR1756GycPsg7b9bdV9Duqur4gv6aKqHXah67Z8ImS7WEz5QVcOtlfW2rZEugt6w==", + "version": "6.0.1", + "resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-6.0.1.tgz", + "integrity": "sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==", "dev": true, "dependencies": { - "ansi-regex": "^5.0.0" + "ansi-regex": "^5.0.1" }, "engines": { "node": ">=8" @@ -15364,22 +15515,6 @@ "resolved": "https://registry.npmjs.org/lodash.truncate/-/lodash.truncate-4.4.2.tgz", "integrity": "sha1-WjUNoLERO4N+z//VgSy+WNbq4ZM=" }, - "node_modules/log-symbols": { - "version": "4.1.0", - "resolved": "https://registry.npmjs.org/log-symbols/-/log-symbols-4.1.0.tgz", - "integrity": "sha512-8XPvpAA8uyhfteu8pIvQxpJZ7SYYdpUivZpGy6sFsBuKRY/7rQGavedeB8aK+Zkyq6upMFVL/9AW6vOYzfRyLg==", - "dev": true, - "dependencies": { - "chalk": "^4.1.0", - "is-unicode-supported": "^0.1.0" - }, - "engines": { - "node": ">=10" - }, - "funding": { - "url": "https://github.com/sponsors/sindresorhus" - } - }, "node_modules/log-update": { "version": "4.0.0", "resolved": "https://registry.npmjs.org/log-update/-/log-update-4.0.0.tgz", @@ -15651,19 +15786,21 @@ } }, "node_modules/mdast-util-from-markdown": { - "version": "1.0.0", - "resolved": "https://registry.npmjs.org/mdast-util-from-markdown/-/mdast-util-from-markdown-1.0.0.tgz", - "integrity": "sha512-uj2G60sb7z1PNOeElFwCC9b/Se/lFXuLhVKFOAY2EHz/VvgbupTQRNXPoZl7rGpXYL6BNZgcgaybrlSWbo7n/g==", + "version": "1.0.3", + "resolved": "https://registry.npmjs.org/mdast-util-from-markdown/-/mdast-util-from-markdown-1.0.3.tgz", + "integrity": "sha512-8/GPJsE3h73C+PBFJ3cCdvegz07mLS8/5NfuIsP8q/cw/Ph/aximc6OYdfwerwcZqTYVu7WeXm/8+RDztxreZQ==", "dependencies": { "@types/mdast": "^3.0.0", "@types/unist": "^2.0.0", - "mdast-util-to-string": "^3.0.0", + "mdast-util-to-string": "^3.1.0", "micromark": "^3.0.0", "micromark-util-decode-numeric-character-reference": "^1.0.0", + "micromark-util-decode-string": "^1.0.0", "micromark-util-normalize-identifier": "^1.0.0", "micromark-util-symbol": "^1.0.0", "micromark-util-types": "^1.0.0", "parse-entities": "^3.0.0", + "power-assert": "^1.0.0", "unist-util-stringify-position": "^3.0.0" }, "funding": { @@ -16370,6 +16507,27 @@ "micromark-util-symbol": "^1.0.0" } }, + "node_modules/micromark-util-decode-string": { + "version": "1.0.1", + "resolved": "https://registry.npmjs.org/micromark-util-decode-string/-/micromark-util-decode-string-1.0.1.tgz", + "integrity": "sha512-Wf3H6jLaO3iIlHEvblESXaKAr72nK7JtBbLLICPwuZc3eJkMcp4j8rJ5Xv1VbQWMCWWDvKUbVUbE2MfQNznwTA==", + "funding": [ + { + "type": "GitHub Sponsors", + "url": "https://github.com/sponsors/unifiedjs" + }, + { + "type": "OpenCollective", + "url": "https://opencollective.com/unified" + } + ], + "dependencies": { + "micromark-util-character": "^1.0.0", + "micromark-util-decode-numeric-character-reference": "^1.0.0", + "micromark-util-symbol": "^1.0.0", + "parse-entities": "^3.0.0" + } + }, "node_modules/micromark-util-encode": { "version": "1.0.0", "resolved": "https://registry.npmjs.org/micromark-util-encode/-/micromark-util-encode-1.0.0.tgz", @@ -19053,9 +19211,9 @@ } }, "node_modules/path-parse": { - "version": "1.0.6", - "resolved": "https://registry.npmjs.org/path-parse/-/path-parse-1.0.6.tgz", - "integrity": "sha512-GSmOT2EbHrINBf9SR7CDELwlJ8AENk3Qn7OikK4nFYAu3Ote2+JYNVvkpAEQm3/TLNEJFD/xZJjzyxg3KBWOzw==" + "version": "1.0.7", + "resolved": "https://registry.npmjs.org/path-parse/-/path-parse-1.0.7.tgz", + "integrity": "sha512-LDJzPVEEEPR+y48z93A0Ed0yXb8pAByGWo/k5YYdYgpY2/2EsOsksJrq7lOHxryrVOn1ejG6oAp8ahvOIQD8sw==" }, "node_modules/path-to-regexp": { "version": "0.1.7", @@ -19288,6 +19446,115 @@ "resolved": "https://registry.npmjs.org/postcss-value-parser/-/postcss-value-parser-4.1.0.tgz", "integrity": "sha512-97DXOFbQJhk71ne5/Mt6cOu6yxsSfM0QGQyl0L25Gca4yGWEGJaig7l7gbCX623VqTBNGLRLaVUCnNkcedlRSQ==" }, + "node_modules/power-assert": { + "version": "1.6.1", + "resolved": "https://registry.npmjs.org/power-assert/-/power-assert-1.6.1.tgz", + "integrity": "sha512-VWkkZV6Y+W8qLX/PtJu2Ur2jDPIs0a5vbP0TpKeybNcIXmT4vcKoVkyTp5lnQvTpY/DxacAZ4RZisHRHLJcAZQ==", + "dependencies": { + "define-properties": "^1.1.2", + "empower": "^1.3.1", + "power-assert-formatter": "^1.4.1", + "universal-deep-strict-equal": "^1.2.1", + "xtend": "^4.0.0" + } + }, + "node_modules/power-assert-context-formatter": { + "version": "1.2.0", + "resolved": "https://registry.npmjs.org/power-assert-context-formatter/-/power-assert-context-formatter-1.2.0.tgz", + "integrity": "sha512-HLNEW8Bin+BFCpk/zbyKwkEu9W8/zThIStxGo7weYcFkKgMuGCHUJhvJeBGXDZf0Qm2xis4pbnnciGZiX0EpSg==", + "dependencies": { + "core-js": "^2.0.0", + "power-assert-context-traversal": "^1.2.0" + } + }, + "node_modules/power-assert-context-reducer-ast": { + "version": "1.2.0", + "resolved": "https://registry.npmjs.org/power-assert-context-reducer-ast/-/power-assert-context-reducer-ast-1.2.0.tgz", + "integrity": "sha512-EgOxmZ/Lb7tw4EwSKX7ZnfC0P/qRZFEG28dx/690qvhmOJ6hgThYFm5TUWANDLK5NiNKlPBi5WekVGd2+5wPrw==", + "dependencies": { + "acorn": "^5.0.0", + "acorn-es7-plugin": "^1.0.12", + "core-js": "^2.0.0", + "espurify": "^1.6.0", + "estraverse": "^4.2.0" + } + }, + "node_modules/power-assert-context-traversal": { + "version": "1.2.0", + "resolved": "https://registry.npmjs.org/power-assert-context-traversal/-/power-assert-context-traversal-1.2.0.tgz", + "integrity": "sha512-NFoHU6g2umNajiP2l4qb0BRWD773Aw9uWdWYH9EQsVwIZnog5bd2YYLFCVvaxWpwNzWeEfZIon2xtyc63026pQ==", + "dependencies": { + "core-js": "^2.0.0", + "estraverse": "^4.1.0" + } + }, + "node_modules/power-assert-formatter": { + "version": "1.4.1", + "resolved": "https://registry.npmjs.org/power-assert-formatter/-/power-assert-formatter-1.4.1.tgz", + "integrity": "sha1-XcEl7VCj37HdomwZNH879Y7CiEo=", + "dependencies": { + "core-js": "^2.0.0", + "power-assert-context-formatter": "^1.0.7", + "power-assert-context-reducer-ast": "^1.0.7", + "power-assert-renderer-assertion": "^1.0.7", + "power-assert-renderer-comparison": "^1.0.7", + "power-assert-renderer-diagram": "^1.0.7", + "power-assert-renderer-file": "^1.0.7" + } + }, + "node_modules/power-assert-renderer-assertion": { + "version": "1.2.0", + "resolved": "https://registry.npmjs.org/power-assert-renderer-assertion/-/power-assert-renderer-assertion-1.2.0.tgz", + "integrity": "sha512-3F7Q1ZLmV2ZCQv7aV7NJLNK9G7QsostrhOU7U0RhEQS/0vhEqrRg2jEJl1jtUL4ZyL2dXUlaaqrmPv5r9kRvIg==", + "dependencies": { + "power-assert-renderer-base": "^1.1.1", + "power-assert-util-string-width": "^1.2.0" + } + }, + "node_modules/power-assert-renderer-base": { + "version": "1.1.1", + "resolved": "https://registry.npmjs.org/power-assert-renderer-base/-/power-assert-renderer-base-1.1.1.tgz", + "integrity": "sha1-lqZQxv0F7hvB9mtUrWFELIs/Y+s=" + }, + "node_modules/power-assert-renderer-comparison": { + "version": "1.2.0", + "resolved": "https://registry.npmjs.org/power-assert-renderer-comparison/-/power-assert-renderer-comparison-1.2.0.tgz", + "integrity": "sha512-7c3RKPDBKK4E3JqdPtYRE9cM8AyX4LC4yfTvvTYyx8zSqmT5kJnXwzR0yWQLOavACllZfwrAGQzFiXPc5sWa+g==", + "dependencies": { + "core-js": "^2.0.0", + "diff-match-patch": "^1.0.0", + "power-assert-renderer-base": "^1.1.1", + "stringifier": "^1.3.0", + "type-name": "^2.0.1" + } + }, + "node_modules/power-assert-renderer-diagram": { + "version": "1.2.0", + "resolved": "https://registry.npmjs.org/power-assert-renderer-diagram/-/power-assert-renderer-diagram-1.2.0.tgz", + "integrity": "sha512-JZ6PC+DJPQqfU6dwSmpcoD7gNnb/5U77bU5KgNwPPa+i1Pxiz6UuDeM3EUBlhZ1HvH9tMjI60anqVyi5l2oNdg==", + "dependencies": { + "core-js": "^2.0.0", + "power-assert-renderer-base": "^1.1.1", + "power-assert-util-string-width": "^1.2.0", + "stringifier": "^1.3.0" + } + }, + "node_modules/power-assert-renderer-file": { + "version": "1.2.0", + "resolved": "https://registry.npmjs.org/power-assert-renderer-file/-/power-assert-renderer-file-1.2.0.tgz", + "integrity": "sha512-/oaVrRbeOtGoyyd7e4IdLP/jIIUFJdqJtsYzP9/88R39CMnfF/S/rUc8ZQalENfUfQ/wQHu+XZYRMaCEZmEesg==", + "dependencies": { + "power-assert-renderer-base": "^1.1.1" + } + }, + "node_modules/power-assert-util-string-width": { + "version": "1.2.0", + "resolved": "https://registry.npmjs.org/power-assert-util-string-width/-/power-assert-util-string-width-1.2.0.tgz", + "integrity": "sha512-lX90G0igAW0iyORTILZ/QjZWsa1MZ6VVY3L0K86e2eKun3S4LKPH4xZIl8fdeMYLfOjkaszbNSzf1uugLeAm2A==", + "dependencies": { + "eastasianwidth": "^0.2.0" + } + }, "node_modules/prelude-ls": { "version": "1.1.2", "resolved": "https://registry.npmjs.org/prelude-ls/-/prelude-ls-1.1.2.tgz", @@ -19366,9 +19633,9 @@ } }, "node_modules/prismjs": { - "version": "1.24.1", - "resolved": "https://registry.npmjs.org/prismjs/-/prismjs-1.24.1.tgz", - "integrity": "sha512-mNPsedLuk90RVJioIky8ANZEwYm5w9LcvCXrxHlwf4fNVSn8jEipMybMkWUyyF0JhnC+C4VcOVSBuHRKs1L5Ow==" + "version": "1.25.0", + "resolved": "https://registry.npmjs.org/prismjs/-/prismjs-1.25.0.tgz", + "integrity": "sha512-WCjJHl1KEWbnkQom1+SzftbtXMKQoezOCYs5rECqMN+jP+apI7ftoflyqigqzopSO3hMhTEb0mFClA8lkolgEg==" }, "node_modules/private": { "version": "0.1.8", @@ -20059,13 +20326,13 @@ } }, "node_modules/refractor": { - "version": "3.4.0", - "resolved": "https://registry.npmjs.org/refractor/-/refractor-3.4.0.tgz", - "integrity": "sha512-dBeD02lC5eytm9Gld2Mx0cMcnR+zhSnsTfPpWqFaMgUMJfC9A6bcN3Br/NaXrnBJcuxnLFR90k1jrkaSyV8umg==", + "version": "3.5.0", + "resolved": "https://registry.npmjs.org/refractor/-/refractor-3.5.0.tgz", + "integrity": "sha512-QwPJd3ferTZ4cSPPjdP5bsYHMytwWYnAN5EEnLtGvkqp/FCCnGsBgxrm9EuIDnjUC3Uc/kETtvVi7fSIVC74Dg==", "dependencies": { "hastscript": "^6.0.0", "parse-entities": "^2.0.0", - "prismjs": "~1.24.0" + "prismjs": "~1.25.0" }, "funding": { "type": "github", @@ -22376,6 +22643,16 @@ "url": "https://github.com/sponsors/ljharb" } }, + "node_modules/stringifier": { + "version": "1.4.0", + "resolved": "https://registry.npmjs.org/stringifier/-/stringifier-1.4.0.tgz", + "integrity": "sha512-cNsMOqqrcbLcHTXEVmkw9y0fwDwkdgtZwlfyolzpQDoAE1xdNGhQhxBUfiDvvZIKl1hnUEgMv66nHwtMz3OjPw==", + "dependencies": { + "core-js": "^2.0.0", + "traverse": "^0.6.6", + "type-name": "^2.0.1" + } + }, "node_modules/stringify-entities": { "version": "4.0.1", "resolved": "https://registry.npmjs.org/stringify-entities/-/stringify-entities-4.0.1.tgz", @@ -23122,6 +23399,11 @@ "node": ">=8" } }, + "node_modules/traverse": { + "version": "0.6.6", + "resolved": "https://registry.npmjs.org/traverse/-/traverse-0.6.6.tgz", + "integrity": "sha1-y99WD9e5r2MlAv7UD5GMFX6pcTc=" + }, "node_modules/tree-kill": { "version": "1.2.2", "resolved": "https://registry.npmjs.org/tree-kill/-/tree-kill-1.2.2.tgz", @@ -23323,6 +23605,11 @@ "node": ">= 0.6" } }, + "node_modules/type-name": { + "version": "2.0.2", + "resolved": "https://registry.npmjs.org/type-name/-/type-name-2.0.2.tgz", + "integrity": "sha1-7+fUEj2KxSr/9/QMfk3sUmYAj7Q=" + }, "node_modules/typedarray": { "version": "0.0.6", "resolved": "https://registry.npmjs.org/typedarray/-/typedarray-0.0.6.tgz", @@ -23623,9 +23910,9 @@ } }, "node_modules/unist-util-visit": { - "version": "4.0.0", - "resolved": "https://registry.npmjs.org/unist-util-visit/-/unist-util-visit-4.0.0.tgz", - "integrity": "sha512-3HWTvrtU10/E7qgPznBfiOyG0TXj9W8c1GSfaI8L9GkaG1pLePiQPZ7E35a0R3ToQ/zcy4Im6aZ9WBgOTnv1MQ==", + "version": "4.1.0", + "resolved": "https://registry.npmjs.org/unist-util-visit/-/unist-util-visit-4.1.0.tgz", + "integrity": "sha512-n7lyhFKJfVZ9MnKtqbsqkQEk5P1KShj0+//V7mAcoI6bpbUjh3C/OG8HVD+pBihfh6Ovl01m8dkcv9HNqYajmQ==", "dependencies": { "@types/unist": "^2.0.0", "unist-util-is": "^5.0.0", @@ -23680,6 +23967,16 @@ "url": "https://opencollective.com/unified" } }, + "node_modules/universal-deep-strict-equal": { + "version": "1.2.2", + "resolved": "https://registry.npmjs.org/universal-deep-strict-equal/-/universal-deep-strict-equal-1.2.2.tgz", + "integrity": "sha1-DaSsL3PP95JMgfpN4BjKViyisKc=", + "dependencies": { + "array-filter": "^1.0.0", + "indexof": "0.0.1", + "object-keys": "^1.0.0" + } + }, "node_modules/universal-user-agent": { "version": "6.0.0", "resolved": "https://registry.npmjs.org/universal-user-agent/-/universal-user-agent-6.0.0.tgz", @@ -25339,19 +25636,19 @@ "integrity": "sha512-0NqAC1IJE0S0+lL1SWFMxMkz1pKCNCjI4tr2Zx4LJSXxCLAdr6KyArnY+sno5m3yH9g737ygOyPABDsnXkpxiA==" }, "@babel/core": { - "version": "7.15.5", - "resolved": "https://registry.npmjs.org/@babel/core/-/core-7.15.5.tgz", - "integrity": "sha512-pYgXxiwAgQpgM1bNkZsDEq85f0ggXMA5L7c+o3tskGMh2BunCI9QUwB9Z4jpvXUOuMdyGKiGKQiRe11VS6Jzvg==", + "version": "7.15.8", + "resolved": "https://registry.npmjs.org/@babel/core/-/core-7.15.8.tgz", + "integrity": "sha512-3UG9dsxvYBMYwRv+gS41WKHno4K60/9GPy1CJaH6xy3Elq8CTtvtjT5R5jmNhXfCYLX2mTw+7/aq5ak/gOE0og==", "requires": { - "@babel/code-frame": "^7.14.5", - "@babel/generator": "^7.15.4", + "@babel/code-frame": "^7.15.8", + "@babel/generator": "^7.15.8", "@babel/helper-compilation-targets": "^7.15.4", - "@babel/helper-module-transforms": "^7.15.4", + "@babel/helper-module-transforms": "^7.15.8", "@babel/helpers": "^7.15.4", - "@babel/parser": "^7.15.5", + "@babel/parser": "^7.15.8", "@babel/template": "^7.15.4", "@babel/traverse": "^7.15.4", - "@babel/types": "^7.15.4", + "@babel/types": "^7.15.6", "convert-source-map": "^1.7.0", "debug": "^4.1.0", "gensync": "^1.0.0-beta.2", @@ -25361,9 +25658,9 @@ }, "dependencies": { "@babel/code-frame": { - "version": "7.14.5", - "resolved": "https://registry.npmjs.org/@babel/code-frame/-/code-frame-7.14.5.tgz", - "integrity": "sha512-9pzDqyc6OLDaqe+zbACgFkb6fKMNG6CObKpnYXChRsvYGyEdc7CA2BaqeOM+vOtCS5ndmJicPJhKAwYRI6UfFw==", + "version": "7.15.8", + "resolved": "https://registry.npmjs.org/@babel/code-frame/-/code-frame-7.15.8.tgz", + "integrity": "sha512-2IAnmn8zbvC/jKYhq5Ki9I+DwjlrtMPUCH/CpHvqI4dNnlwHwsxoIhlc8WcYY5LSYknXQtAlFYuHfqAFCvQ4Wg==", "requires": { "@babel/highlight": "^7.14.5" } @@ -25414,11 +25711,11 @@ } }, "@babel/generator": { - "version": "7.15.4", - "resolved": "https://registry.npmjs.org/@babel/generator/-/generator-7.15.4.tgz", - "integrity": "sha512-d3itta0tu+UayjEORPNz6e1T3FtvWlP5N4V5M+lhp/CxT4oAA7/NcScnpRyspUMLK6tu9MNHmQHxRykuN2R7hw==", + "version": "7.15.8", + "resolved": "https://registry.npmjs.org/@babel/generator/-/generator-7.15.8.tgz", + "integrity": "sha512-ECmAKstXbp1cvpTTZciZCgfOt6iN64lR0d+euv3UZisU5awfRawOvg07Utn/qBGuH4bRIEZKrA/4LzZyXhZr8g==", "requires": { - "@babel/types": "^7.15.4", + "@babel/types": "^7.15.6", "jsesc": "^2.5.1", "source-map": "^0.5.0" } @@ -25574,18 +25871,18 @@ } }, "@babel/helper-module-transforms": { - "version": "7.15.4", - "resolved": "https://registry.npmjs.org/@babel/helper-module-transforms/-/helper-module-transforms-7.15.4.tgz", - "integrity": "sha512-9fHHSGE9zTC++KuXLZcB5FKgvlV83Ox+NLUmQTawovwlJ85+QMhk1CnVk406CQVj97LaWod6KVjl2Sfgw9Aktw==", + "version": "7.15.8", + "resolved": "https://registry.npmjs.org/@babel/helper-module-transforms/-/helper-module-transforms-7.15.8.tgz", + "integrity": "sha512-DfAfA6PfpG8t4S6npwzLvTUpp0sS7JrcuaMiy1Y5645laRJIp/LiLGIBbQKaXSInK8tiGNI7FL7L8UvB8gdUZg==", "requires": { "@babel/helper-module-imports": "^7.15.4", "@babel/helper-replace-supers": "^7.15.4", "@babel/helper-simple-access": "^7.15.4", "@babel/helper-split-export-declaration": "^7.15.4", - "@babel/helper-validator-identifier": "^7.14.9", + "@babel/helper-validator-identifier": "^7.15.7", "@babel/template": "^7.15.4", "@babel/traverse": "^7.15.4", - "@babel/types": "^7.15.4" + "@babel/types": "^7.15.6" } }, "@babel/helper-optimise-call-expression": { @@ -25649,9 +25946,9 @@ } }, "@babel/helper-validator-identifier": { - "version": "7.14.9", - "resolved": "https://registry.npmjs.org/@babel/helper-validator-identifier/-/helper-validator-identifier-7.14.9.tgz", - "integrity": "sha512-pQYxPY0UP6IHISRitNe8bsijHex4TWZXi2HwKVsjPiltzlhse2znVcm9Ace510VT1kxIHjGJCZZQBX2gJDbo0g==" + "version": "7.15.7", + "resolved": "https://registry.npmjs.org/@babel/helper-validator-identifier/-/helper-validator-identifier-7.15.7.tgz", + "integrity": "sha512-K4JvCtQqad9OY2+yTU8w+E82ywk/fe+ELNlt1G8z3bVGlZfn/hOcQQsUhGhW/N+tb3fxK800wLtKOE/aM0m72w==" }, "@babel/helper-validator-option": { "version": "7.14.5", @@ -25719,9 +26016,9 @@ } }, "@babel/parser": { - "version": "7.15.6", - "resolved": "https://registry.npmjs.org/@babel/parser/-/parser-7.15.6.tgz", - "integrity": "sha512-S/TSCcsRuCkmpUuoWijua0Snt+f3ewU/8spLo+4AXJCZfT0bVCzLD5MuOKdrx0mlAptbKzn5AdgEIIKXxXkz9Q==" + "version": "7.15.8", + "resolved": "https://registry.npmjs.org/@babel/parser/-/parser-7.15.8.tgz", + "integrity": "sha512-BRYa3wcQnjS/nqI8Ac94pYYpJfojHVvVXJ97+IDCImX4Jc8W8Xv1+47enbruk+q1etOpsQNwnfFcNGw+gtPGxA==" }, "@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining": { "version": "7.15.4", @@ -25735,9 +26032,9 @@ } }, "@babel/plugin-proposal-async-generator-functions": { - "version": "7.15.4", - "resolved": "https://registry.npmjs.org/@babel/plugin-proposal-async-generator-functions/-/plugin-proposal-async-generator-functions-7.15.4.tgz", - "integrity": "sha512-2zt2g5vTXpMC3OmK6uyjvdXptbhBXfA77XGrd3gh93zwG8lZYBLOBImiGBEG0RANu3JqKEACCz5CGk73OJROBw==", + "version": "7.15.8", + "resolved": "https://registry.npmjs.org/@babel/plugin-proposal-async-generator-functions/-/plugin-proposal-async-generator-functions-7.15.8.tgz", + "integrity": "sha512-2Z5F2R2ibINTc63mY7FLqGfEbmofrHU9FitJW1Q7aPaKFhiPvSq6QEt/BoWN5oME3GVyjcRuNNSRbb9LC0CSWA==", "dev": true, "requires": { "@babel/helper-plugin-utils": "^7.14.5", @@ -26332,13 +26629,13 @@ } }, "@babel/plugin-transform-spread": { - "version": "7.14.6", - "resolved": "https://registry.npmjs.org/@babel/plugin-transform-spread/-/plugin-transform-spread-7.14.6.tgz", - "integrity": "sha512-Zr0x0YroFJku7n7+/HH3A2eIrGMjbmAIbJSVv0IZ+t3U2WUQUA64S/oeied2e+MaGSjmt4alzBCsK9E8gh+fag==", + "version": "7.15.8", + "resolved": "https://registry.npmjs.org/@babel/plugin-transform-spread/-/plugin-transform-spread-7.15.8.tgz", + "integrity": "sha512-/daZ8s2tNaRekl9YJa9X4bzjpeRZLt122cpgFnQPLGUe61PH8zMEBmYqKkW5xF5JUEh5buEGXJoQpqBmIbpmEQ==", "dev": true, "requires": { "@babel/helper-plugin-utils": "^7.14.5", - "@babel/helper-skip-transparent-expression-wrappers": "^7.14.5" + "@babel/helper-skip-transparent-expression-wrappers": "^7.15.4" } }, "@babel/plugin-transform-sticky-regex": { @@ -26388,9 +26685,9 @@ } }, "@babel/preset-env": { - "version": "7.15.6", - "resolved": "https://registry.npmjs.org/@babel/preset-env/-/preset-env-7.15.6.tgz", - "integrity": "sha512-L+6jcGn7EWu7zqaO2uoTDjjMBW+88FXzV8KvrBl2z6MtRNxlsmUNRlZPaNNPUTgqhyC5DHNFk/2Jmra+ublZWw==", + "version": "7.15.8", + "resolved": "https://registry.npmjs.org/@babel/preset-env/-/preset-env-7.15.8.tgz", + "integrity": "sha512-rCC0wH8husJgY4FPbHsiYyiLxSY8oMDJH7Rl6RQMknbN9oDDHhM9RDFvnGM2MgkbUJzSQB4gtuwygY5mCqGSsA==", "dev": true, "requires": { "@babel/compat-data": "^7.15.0", @@ -26398,7 +26695,7 @@ "@babel/helper-plugin-utils": "^7.14.5", "@babel/helper-validator-option": "^7.14.5", "@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining": "^7.15.4", - "@babel/plugin-proposal-async-generator-functions": "^7.15.4", + "@babel/plugin-proposal-async-generator-functions": "^7.15.8", "@babel/plugin-proposal-class-properties": "^7.14.5", "@babel/plugin-proposal-class-static-block": "^7.15.4", "@babel/plugin-proposal-dynamic-import": "^7.14.5", @@ -26453,7 +26750,7 @@ "@babel/plugin-transform-regenerator": "^7.14.5", "@babel/plugin-transform-reserved-words": "^7.14.5", "@babel/plugin-transform-shorthand-properties": "^7.14.5", - "@babel/plugin-transform-spread": "^7.14.6", + "@babel/plugin-transform-spread": "^7.15.8", "@babel/plugin-transform-sticky-regex": "^7.14.5", "@babel/plugin-transform-template-literals": "^7.14.5", "@babel/plugin-transform-typeof-symbol": "^7.14.5", @@ -26462,7 +26759,7 @@ "@babel/preset-modules": "^0.1.4", "@babel/types": "^7.15.6", "babel-plugin-polyfill-corejs2": "^0.2.2", - "babel-plugin-polyfill-corejs3": "^0.2.2", + "babel-plugin-polyfill-corejs3": "^0.2.5", "babel-plugin-polyfill-regenerator": "^0.2.2", "core-js-compat": "^3.16.0", "semver": "^6.3.0" @@ -26707,13 +27004,13 @@ } }, "@graphql-tools/load": { - "version": "7.3.0", - "resolved": "https://registry.npmjs.org/@graphql-tools/load/-/load-7.3.0.tgz", - "integrity": "sha512-ZVipT7yzOpf/DJ2sLI3xGwnULVFp/icu7RFEgDo2ZX0WHiS7EjWZ0cegxEm87+WN4fMwpiysRLzWx67VIHwKGA==", + "version": "7.3.2", + "resolved": "https://registry.npmjs.org/@graphql-tools/load/-/load-7.3.2.tgz", + "integrity": "sha512-tB03MGOlgKkoP6YyzIl/saTYshuLWxQy2JebhYL6gy3XsWmSE7ae1WAL3p+G0pyfw66HaMu905omyulu1VkfXw==", "dev": true, "requires": { "@graphql-tools/schema": "8.2.0", - "@graphql-tools/utils": "^8.2.0", + "@graphql-tools/utils": "^8.2.3", "p-limit": "3.1.0", "tslib": "~2.3.0" }, @@ -26774,9 +27071,9 @@ } }, "@graphql-tools/utils": { - "version": "8.2.2", - "resolved": "https://registry.npmjs.org/@graphql-tools/utils/-/utils-8.2.2.tgz", - "integrity": "sha512-29FFY5U4lpXuBiW9dRvuWnBVwGhWbGLa2leZcAMU/Pz47Cr/QLZGVgpLBV9rt+Gbs7wyIJM7t7EuksPs0RDm3g==", + "version": "8.2.5", + "resolved": "https://registry.npmjs.org/@graphql-tools/utils/-/utils-8.2.5.tgz", + "integrity": "sha512-k/Rktklhy22dQfbJLKiLGfQymQCTr6Rd2BilC7g2Yk6wFSzVLYr8jeXNoTD+/p61XBQzBjTVayskvaMvNS3BDg==", "dev": true, "requires": { "tslib": "~2.3.0" @@ -27775,18 +28072,18 @@ } }, "@octokit/openapi-types": { - "version": "10.1.5", - "resolved": "https://registry.npmjs.org/@octokit/openapi-types/-/openapi-types-10.1.5.tgz", - "integrity": "sha512-OoShNYzhAU8p8JbGHe1rRs1GIErRtmN2230AQCJAjL5lc0AUU5OhppVe6693HIZ2eCBLUhoLPhnnnmQ5ASH7Wg==", + "version": "11.0.0", + "resolved": "https://registry.npmjs.org/@octokit/openapi-types/-/openapi-types-11.0.0.tgz", + "integrity": "sha512-QeMW4h18cEm53ojYufACSRgq3rrQg4BibVcsHytXmbJ+otmXSelr1BCBCEi8q7nqGkYJyGQX30DoULENIgJ8BA==", "dev": true }, "@octokit/plugin-paginate-rest": { - "version": "2.16.2", - "resolved": "https://registry.npmjs.org/@octokit/plugin-paginate-rest/-/plugin-paginate-rest-2.16.2.tgz", - "integrity": "sha512-WF5/MTPnFgYH6rMGuxBvbxX2S/3ygNWylakgD7njKES0Qwk5e+d/L6r/BYXSw7B6xJJ3hlwIAmUmOxxYrR+Q8A==", + "version": "2.16.8", + "resolved": "https://registry.npmjs.org/@octokit/plugin-paginate-rest/-/plugin-paginate-rest-2.16.8.tgz", + "integrity": "sha512-VZZYeNNwCkC2XoTUFouTpFdR2esSPuJb4U58iUxeYu4vQ1AUzCs6AI+gf4bL413CQ8DZhkxASflfLWzcp+9shQ==", "dev": true, "requires": { - "@octokit/types": "^6.27.2" + "@octokit/types": "^6.32.0" } }, "@octokit/plugin-request-log": { @@ -27797,12 +28094,12 @@ "requires": {} }, "@octokit/plugin-rest-endpoint-methods": { - "version": "5.10.3", - "resolved": "https://registry.npmjs.org/@octokit/plugin-rest-endpoint-methods/-/plugin-rest-endpoint-methods-5.10.3.tgz", - "integrity": "sha512-eAT4gje+VR9xdSlhuHWNXsNLpiODqdqz8jqShMgaxRH82Le2nS6EV6LAo3QPZ05Fso5oGmDfJF6eq9vs1cEhdA==", + "version": "5.12.0", + "resolved": "https://registry.npmjs.org/@octokit/plugin-rest-endpoint-methods/-/plugin-rest-endpoint-methods-5.12.0.tgz", + "integrity": "sha512-OD3Rv660YzXSmhTr8g8kpLvLq3Z5ADvLxtb9a8+1I4S2EqV6YQTHeJwVC5I6vwvV5tMmnj3oeRn7OWc0eODwQw==", "dev": true, "requires": { - "@octokit/types": "^6.27.2", + "@octokit/types": "^6.32.0", "deprecation": "^2.3.1" } }, @@ -27846,24 +28143,24 @@ } }, "@octokit/rest": { - "version": "18.10.0", - "resolved": "https://registry.npmjs.org/@octokit/rest/-/rest-18.10.0.tgz", - "integrity": "sha512-esHR5OKy38bccL/sajHqZudZCvmv4yjovMJzyXlphaUo7xykmtOdILGJ3aAm0mFHmMLmPFmDMJXf39cAjNJsrw==", + "version": "18.12.0", + "resolved": "https://registry.npmjs.org/@octokit/rest/-/rest-18.12.0.tgz", + "integrity": "sha512-gDPiOHlyGavxr72y0guQEhLsemgVjwRePayJ+FcKc2SJqKUbxbkvf5kAZEWA/MKvsfYlQAMVzNJE3ezQcxMJ2Q==", "dev": true, "requires": { "@octokit/core": "^3.5.1", - "@octokit/plugin-paginate-rest": "^2.16.0", + "@octokit/plugin-paginate-rest": "^2.16.8", "@octokit/plugin-request-log": "^1.0.4", - "@octokit/plugin-rest-endpoint-methods": "^5.9.0" + "@octokit/plugin-rest-endpoint-methods": "^5.12.0" } }, "@octokit/types": { - "version": "6.27.2", - "resolved": "https://registry.npmjs.org/@octokit/types/-/types-6.27.2.tgz", - "integrity": "sha512-AgajmAJh7LhStgaEaNoY1N7znst2q07CKZVdnVB/V4tmitMbk+qijmD0IkkSKulXE5RVLbJjQikJF9+XLqhsVA==", + "version": "6.32.0", + "resolved": "https://registry.npmjs.org/@octokit/types/-/types-6.32.0.tgz", + "integrity": "sha512-7CFlMfpX78PbvGnQZfQ3pD246RGTLITDnLCyYgTOtwNPIdTKMGs/8dJiZA3Fh5vXuZYqu/YHH32GboK7xnZ0ag==", "dev": true, "requires": { - "@octokit/openapi-types": "^10.1.5" + "@octokit/openapi-types": "^11.0.0" } }, "@primer/components": { @@ -28267,9 +28564,9 @@ } }, "@types/lodash": { - "version": "4.14.172", - "resolved": "https://registry.npmjs.org/@types/lodash/-/lodash-4.14.172.tgz", - "integrity": "sha512-/BHF5HAx3em7/KkzVKm3LrsD6HZAXuXO1AJZQ3cRRBZj4oHZDviWPYu0aEplAqDFNHZPW6d3G7KN+ONcCCC7pw==", + "version": "4.14.175", + "resolved": "https://registry.npmjs.org/@types/lodash/-/lodash-4.14.175.tgz", + "integrity": "sha512-XmdEOrKQ8a1Y/yxQFOMbC47G/V2VDO1GvMRnl4O75M4GW/abC5tnfzadQYkqEveqRM1dEJGFFegfPNA2vvx2iw==", "dev": true }, "@types/mdast": { @@ -28330,9 +28627,9 @@ "integrity": "sha512-KfRL3PuHmqQLOG+2tGpRO26Ctg+Cq1E01D2DMriKEATHgWLfeNDmq9e29Q9WIky0dQ3NPkd1mzYH8Lm936Z9qw==" }, "@types/react": { - "version": "17.0.20", - "resolved": "https://registry.npmjs.org/@types/react/-/react-17.0.20.tgz", - "integrity": "sha512-wWZrPlihslrPpcKyCSlmIlruakxr57/buQN1RjlIeaaTWDLtJkTtRW429MoQJergvVKc4IWBpRhWw7YNh/7GVA==", + "version": "17.0.27", + "resolved": "https://registry.npmjs.org/@types/react/-/react-17.0.27.tgz", + "integrity": "sha512-zgiJwtsggVGtr53MndV7jfiUESTqrbxOcBvwfe6KS/9bzaVPCTDieTWnFNecVNx6EAaapg5xsLLWFfHHR437AA==", "requires": { "@types/prop-types": "*", "@types/scheduler": "*", @@ -28879,6 +29176,11 @@ "resolved": "https://registry.npmjs.org/acorn/-/acorn-5.7.4.tgz", "integrity": "sha512-1D++VG7BhrtvQpNbBzovKNc1FLGGEE/oGe7b9xJm/RFHMBeUaUGpluV9RLjZa47YFdPcDAenEYuq9pQPcMdLJg==" }, + "acorn-es7-plugin": { + "version": "1.1.7", + "resolved": "https://registry.npmjs.org/acorn-es7-plugin/-/acorn-es7-plugin-1.1.7.tgz", + "integrity": "sha1-8u4fMiipDurRJF+asZIusucdM2s=" + }, "acorn-globals": { "version": "6.0.0", "resolved": "https://registry.npmjs.org/acorn-globals/-/acorn-globals-6.0.0.tgz", @@ -28956,9 +29258,9 @@ } }, "ajv": { - "version": "8.4.0", - "resolved": "https://registry.npmjs.org/ajv/-/ajv-8.4.0.tgz", - "integrity": "sha512-7QD2l6+KBSLwf+7MuYocbWvRPdOu63/trReTLu2KFwkgctnub1auoF+Y1WYcm09CTM7quuscrzqmASaLHC/K4Q==", + "version": "8.6.3", + "resolved": "https://registry.npmjs.org/ajv/-/ajv-8.6.3.tgz", + "integrity": "sha512-SMJOdDP6LqTkD0Uq8qLi+gMwSt0imXLSV080qFVwJCpH9U6Mb+SUGHAXM0KNbcBPguytWyvFxcHgMLe2D2XSpw==", "requires": { "fast-deep-equal": "^3.1.1", "json-schema-traverse": "^1.0.0", @@ -29323,12 +29625,12 @@ "optional": true }, "axios": { - "version": "0.21.1", - "resolved": "https://registry.npmjs.org/axios/-/axios-0.21.1.tgz", - "integrity": "sha512-dKQiRHxGD9PPRIUNIWvZhPTPpl1rf/OxTYKsqKUDjBwYylTvV7SjSHJb9ratfyzM6wCdLCOYLzs73qpg5c4iGA==", + "version": "0.21.4", + "resolved": "https://registry.npmjs.org/axios/-/axios-0.21.4.tgz", + "integrity": "sha512-ut5vewkiu8jjGBdqpM44XxjuCjq9LAKeHVmoVfHVzy8eHgxxq8SbAVQNovDA8mVi05kP0Ea/n/UzcSHcTJQfNg==", "devOptional": true, "requires": { - "follow-redirects": "^1.10.0" + "follow-redirects": "^1.14.0" } }, "axobject-query": { @@ -29641,13 +29943,13 @@ } }, "babel-plugin-polyfill-corejs3": { - "version": "0.2.4", - "resolved": "https://registry.npmjs.org/babel-plugin-polyfill-corejs3/-/babel-plugin-polyfill-corejs3-0.2.4.tgz", - "integrity": "sha512-z3HnJE5TY/j4EFEa/qpQMSbcUJZ5JQi+3UFjXzn6pQCmIKc5Ug5j98SuYyH+m4xQnvKlMDIW4plLfgyVnd0IcQ==", + "version": "0.2.5", + "resolved": "https://registry.npmjs.org/babel-plugin-polyfill-corejs3/-/babel-plugin-polyfill-corejs3-0.2.5.tgz", + "integrity": "sha512-ninF5MQNwAX9Z7c9ED+H2pGt1mXdP4TqzlHKyPIYmJIYz0N+++uwdM7RnJukklhzJ54Q84vA4ZJkgs7lu5vqcw==", "dev": true, "requires": { "@babel/helper-define-polyfill-provider": "^0.2.2", - "core-js-compat": "^3.14.0" + "core-js-compat": "^3.16.2" } }, "babel-plugin-polyfill-regenerator": { @@ -30697,6 +30999,11 @@ "get-intrinsic": "^1.0.2" } }, + "call-signature": { + "version": "0.0.2", + "resolved": "https://registry.npmjs.org/call-signature/-/call-signature-0.0.2.tgz", + "integrity": "sha1-qEq8glpV70yysCi9dOIFpluaSZY=" + }, "callsites": { "version": "3.1.0", "resolved": "https://registry.npmjs.org/callsites/-/callsites-3.1.0.tgz", @@ -31032,9 +31339,9 @@ "integrity": "sha512-p92if5Nz619I0w+akJrLZH0MX0Pb5DX39XOwQTtXSdQQOaYH03S1uIQp4mhOZtAXrxq4ViO67YTiLBo2638o9A==" }, "nth-check": { - "version": "2.0.0", - "resolved": "https://registry.npmjs.org/nth-check/-/nth-check-2.0.0.tgz", - "integrity": "sha512-i4sc/Kj8htBrAiH1viZ0TgU8Y5XqCaV/FziYK6TBczxmeKm3AEFWqqF3195yKudrarqy7Zu80Ra5dobFjn9X/Q==", + "version": "2.0.1", + "resolved": "https://registry.npmjs.org/nth-check/-/nth-check-2.0.1.tgz", + "integrity": "sha512-it1vE95zF6dTT9lBsYbxvqh0Soy4SPowchj0UBGj/V6cTPnXXtQOPUbhZ6CmGzAD/rW22LQK6E96pcdJXk4A4w==", "requires": { "boolbase": "^1.0.0" } @@ -31370,9 +31677,9 @@ "integrity": "sha1-p9BVi9icQveV3UIyj3QIMcpTvCU=" }, "colorette": { - "version": "1.3.0", - "resolved": "https://registry.npmjs.org/colorette/-/colorette-1.3.0.tgz", - "integrity": "sha512-ecORCqbSFP7Wm8Y6lyqMJjexBQqXSF7SSeaTyGGphogUjBlFP9m9o08wy86HL2uB7fMTxtOUzLMk7ogKcxMg1w==" + "version": "1.4.0", + "resolved": "https://registry.npmjs.org/colorette/-/colorette-1.4.0.tgz", + "integrity": "sha512-Y2oEozpomLn7Q3HFP7dpww7AtMJplbM9lGZP6RDfHqmbeRjiwRg4n6VM6j4KLmRke85uWEI7JqF17f3pqdRA0g==" }, "combined-stream": { "version": "1.0.8", @@ -31600,8 +31907,7 @@ "core-js": { "version": "2.6.12", "resolved": "https://registry.npmjs.org/core-js/-/core-js-2.6.12.tgz", - "integrity": "sha512-Kb2wC0fvsWfQrgk8HU5lW6U/Lcs8+9aaYcy4ZFc6DDlo4nZ7n70dEgE5rtR0oG6ufKDUnrwfWL1mXR5ljDatrQ==", - "dev": true + "integrity": "sha512-Kb2wC0fvsWfQrgk8HU5lW6U/Lcs8+9aaYcy4ZFc6DDlo4nZ7n70dEgE5rtR0oG6ufKDUnrwfWL1mXR5ljDatrQ==" }, "core-js-compat": { "version": "3.16.2", @@ -31655,9 +31961,9 @@ } }, "cosmiconfig": { - "version": "7.0.0", - "resolved": "https://registry.npmjs.org/cosmiconfig/-/cosmiconfig-7.0.0.tgz", - "integrity": "sha512-pondGvTuVYDk++upghXJabWzL6Kxu6f26ljFw64Swq9v6sQPUL3EUlVDV56diOjpCayKihL6hVe8exIACU4XcA==", + "version": "7.0.1", + "resolved": "https://registry.npmjs.org/cosmiconfig/-/cosmiconfig-7.0.1.tgz", + "integrity": "sha512-a1YWNUV2HwGimB7dU2s1wUMurNKjpx60HxBB6xUM8Re+2s1g1IIfJvFR0/iCF+XHdE0GMTKTuLR32UQff4TEyQ==", "dev": true, "requires": { "@types/parse-json": "^4.0.0", @@ -32159,6 +32465,11 @@ "integrity": "sha512-VvlVYY+VDJe639yHs5PHISzdWTLL3Aw8rO4cvUtwvoxFd6FHbE4OpHHcde52M6096uYYazAmd4l0o5VuFRO2WA==", "optional": true }, + "diff-match-patch": { + "version": "1.0.5", + "resolved": "https://registry.npmjs.org/diff-match-patch/-/diff-match-patch-1.0.5.tgz", + "integrity": "sha512-IayShXAgj/QMXgB0IWmKx+rOPuGMhqm5w6jvFxmVenXKIzRqTAAsbBPT3kWQeGANj3jGgvcvv4yK6SxqYmikgw==" + }, "diff-sequences": { "version": "27.0.6", "resolved": "https://registry.npmjs.org/diff-sequences/-/diff-sequences-27.0.6.tgz", @@ -32413,6 +32724,11 @@ "stream-shift": "^1.0.0" } }, + "eastasianwidth": { + "version": "0.2.0", + "resolved": "https://registry.npmjs.org/eastasianwidth/-/eastasianwidth-0.2.0.tgz", + "integrity": "sha512-I88TYZWc9XiYHRQ4/3c5rjjfgkjhLyW2luGIheGERbNQ6OY7yTybanSpDXZa8y7VUP9YmDcYa+eyq4ca7iLqWA==" + }, "ee-first": { "version": "1.1.1", "resolved": "https://registry.npmjs.org/ee-first/-/ee-first-1.1.1.tgz", @@ -32460,6 +32776,24 @@ "resolved": "https://registry.npmjs.org/emojis-list/-/emojis-list-2.1.0.tgz", "integrity": "sha1-TapNnbAPmBmIDHn6RXrlsJof04k=" }, + "empower": { + "version": "1.3.1", + "resolved": "https://registry.npmjs.org/empower/-/empower-1.3.1.tgz", + "integrity": "sha512-uB6/ViBaawOO/uujFADTK3SqdYlxYNn+N4usK9MRKZ4Hbn/1QSy8k2PezxCA2/+JGbF8vd/eOfghZ90oOSDZCA==", + "requires": { + "core-js": "^2.0.0", + "empower-core": "^1.2.0" + } + }, + "empower-core": { + "version": "1.2.0", + "resolved": "https://registry.npmjs.org/empower-core/-/empower-core-1.2.0.tgz", + "integrity": "sha512-g6+K6Geyc1o6FdXs9HwrXleCFan7d66G5xSCfSF7x1mJDCes6t0om9lFQG3zOrzh3Bkb/45N0cZ5Gqsf7YrzGQ==", + "requires": { + "call-signature": "0.0.2", + "core-js": "^2.0.0" + } + }, "encodeurl": { "version": "1.0.2", "resolved": "https://registry.npmjs.org/encodeurl/-/encodeurl-1.0.2.tgz", @@ -33127,6 +33461,14 @@ "resolved": "https://registry.npmjs.org/esprima/-/esprima-4.0.1.tgz", "integrity": "sha1-E7BM2z5sXRnfkatph6hpVhmwqnE=" }, + "espurify": { + "version": "1.8.1", + "resolved": "https://registry.npmjs.org/espurify/-/espurify-1.8.1.tgz", + "integrity": "sha512-ZDko6eY/o+D/gHCWyHTU85mKDgYcS4FJj7S+YD6WIInm7GQ6AnOjmcL4+buFV/JOztVLELi/7MmuGU5NHta0Mg==", + "requires": { + "core-js": "^2.0.0" + } + }, "esquery": { "version": "1.4.0", "resolved": "https://registry.npmjs.org/esquery/-/esquery-1.4.0.tgz", @@ -33462,9 +33804,9 @@ } }, "express-rate-limit": { - "version": "5.3.0", - "resolved": "https://registry.npmjs.org/express-rate-limit/-/express-rate-limit-5.3.0.tgz", - "integrity": "sha512-qJhfEgCnmteSeZAeuOKQ2WEIFTX5ajrzE0xS6gCOBCoRQcU+xEzQmgYQQTpzCcqUAAzTEtu4YEih4pnLfvNtew==" + "version": "5.4.1", + "resolved": "https://registry.npmjs.org/express-rate-limit/-/express-rate-limit-5.4.1.tgz", + "integrity": "sha512-ZQh2h3qiu7wWdvWNYHznBhaOp2ZIXNnT4hl2Ff608STeWtCuJ251NzqQlk7mo5wnO2HmrydBYHuVA9Z3S3ZtXg==" }, "express-timeout-handler": { "version": "2.2.2", @@ -34106,9 +34448,9 @@ "integrity": "sha512-w0dzqw/nt51xMVmlaV1+JRzN+oCa1KfcgGEWhxUG16wbdA+Xnt/yoFO8Z8x/V82ZcZ0wy6ln9QDup5avbhiDhQ==" }, "glob": { - "version": "7.1.7", - "resolved": "https://registry.npmjs.org/glob/-/glob-7.1.7.tgz", - "integrity": "sha512-OvD9ENzPLbegENnYP5UUfJIirTg4+XwMWGaQfQTY0JenxNvvIKP3U3/tAQSPIu/lHxXYSZmpXlUHeqAIdKzBLQ==", + "version": "7.2.0", + "resolved": "https://registry.npmjs.org/glob/-/glob-7.2.0.tgz", + "integrity": "sha512-lmLf6gtyrPq8tTjSmrO94wBeQbFR3HbLHbuyD69wuyQkImp2hWqMGB47OX65FBkPffO641IP9jWa1z4ivqG26Q==", "requires": { "fs.realpath": "^1.0.0", "inflight": "^1.0.4", @@ -34609,9 +34951,9 @@ }, "dependencies": { "nth-check": { - "version": "2.0.0", - "resolved": "https://registry.npmjs.org/nth-check/-/nth-check-2.0.0.tgz", - "integrity": "sha512-i4sc/Kj8htBrAiH1viZ0TgU8Y5XqCaV/FziYK6TBczxmeKm3AEFWqqF3195yKudrarqy7Zu80Ra5dobFjn9X/Q==", + "version": "2.0.1", + "resolved": "https://registry.npmjs.org/nth-check/-/nth-check-2.0.1.tgz", + "integrity": "sha512-it1vE95zF6dTT9lBsYbxvqh0Soy4SPowchj0UBGj/V6cTPnXXtQOPUbhZ6CmGzAD/rW22LQK6E96pcdJXk4A4w==", "requires": { "boolbase": "^1.0.0" } @@ -34788,9 +35130,9 @@ } }, "hot-shots": { - "version": "8.5.1", - "resolved": "https://registry.npmjs.org/hot-shots/-/hot-shots-8.5.1.tgz", - "integrity": "sha512-LHqIVuoFDdKvtn9nNAC16KgdiinVsPHKSNuGIMoFlAxFzHL782SaWgQ/MTuOkPbwgEEtEmOGaiBeH25UeL/gRA==", + "version": "8.5.2", + "resolved": "https://registry.npmjs.org/hot-shots/-/hot-shots-8.5.2.tgz", + "integrity": "sha512-1CKCtbYU28KtRriRW+mdOZzKce0WPqU0FOYE4bYs3gD1bFpOrYzQDXfQ09Qz9dJPEltasDOGhFKiYaiuW/j9Dg==", "requires": { "unix-dgram": "2.0.x" } @@ -35077,6 +35419,11 @@ "integrity": "sha512-EdDDZu4A2OyIK7Lr/2zG+w5jmbuk1DVBnEwREQvBzspBJkCEbRa8GxU1lghYcaGJCnRWibjDXlq779X1/y5xwg==", "dev": true }, + "indexof": { + "version": "0.0.1", + "resolved": "https://registry.npmjs.org/indexof/-/indexof-0.0.1.tgz", + "integrity": "sha1-gtwzbSMrkGIXnQWrMpOmYFn9Q10=" + }, "infer-owner": { "version": "1.0.4", "resolved": "https://registry.npmjs.org/infer-owner/-/infer-owner-1.0.4.tgz", @@ -35436,12 +35783,6 @@ "integrity": "sha1-5HnICFjfDBsR3dppQPlgEfzaSpo=", "dev": true }, - "is-unicode-supported": { - "version": "0.1.0", - "resolved": "https://registry.npmjs.org/is-unicode-supported/-/is-unicode-supported-0.1.0.tgz", - "integrity": "sha512-knxG2q4UC3u8stRGyAVJCOdxFmv5DZiRcdlIaAQXAbSfJya+OhopNotLQrstBhququ4ZpuKbDc/8S6mgXgPFPw==", - "dev": true - }, "is-url": { "version": "1.2.4", "resolved": "https://registry.npmjs.org/is-url/-/is-url-1.2.4.tgz", @@ -36635,9 +36976,9 @@ } }, "jszip": { - "version": "3.6.0", - "resolved": "https://registry.npmjs.org/jszip/-/jszip-3.6.0.tgz", - "integrity": "sha512-jgnQoG9LKnWO3mnVNBnfhkh0QknICd1FGSrXcgrl67zioyJ4wgx25o9ZqwNtrROSflGBCGYnJfjrIyRIby1OoQ==", + "version": "3.7.1", + "resolved": "https://registry.npmjs.org/jszip/-/jszip-3.7.1.tgz", + "integrity": "sha512-ghL0tz1XG9ZEmRMcEN2vt7xabrDdqHHeykgARpmZ0BiIctWxM47Vt63ZO2dnp4QYt/xJVLLy5Zv1l/xRdh2byg==", "optional": true, "requires": { "lie": "~3.3.0", @@ -36732,16 +37073,16 @@ "dev": true }, "linkinator": { - "version": "2.14.0", - "resolved": "https://registry.npmjs.org/linkinator/-/linkinator-2.14.0.tgz", - "integrity": "sha512-7OvAgx0Ml7vByog2NsMg3sH+cH8pZyvMt1BhQE6mGnyQONXtKQvzuynLCEFPznVgPpQBQ1onvDP2udyVafvINQ==", + "version": "2.14.4", + "resolved": "https://registry.npmjs.org/linkinator/-/linkinator-2.14.4.tgz", + "integrity": "sha512-ADxb8C9k9LUAHFZCsKZnB+TtxTqVPiL86zQpmMp9x+aarrhY9YBV12msb87C9IR9DBxaohonhIfMVvrJW4E7Wg==", "dev": true, "requires": { "chalk": "^4.0.0", - "cheerio": "^1.0.0-rc.10", "escape-html": "^1.0.3", "gaxios": "^4.0.0", "glob": "^7.1.6", + "htmlparser2": "^7.1.2", "jsonexport": "^3.0.0", "marked": "^2.0.0", "meow": "^9.0.0", @@ -36808,6 +37149,57 @@ "integrity": "sha512-dOy+3AuW3a2wNbZHIuMZpTcgjGuLU/uBL/ubcZF9OXbDo8ff4O8yVp5Bf0efS8uEoYo5q4Fx7dY9OgQGXgAsQA==", "dev": true }, + "dom-serializer": { + "version": "1.3.2", + "resolved": "https://registry.npmjs.org/dom-serializer/-/dom-serializer-1.3.2.tgz", + "integrity": "sha512-5c54Bk5Dw4qAxNOI1pFEizPSjVsx5+bpJKmL2kPn8JhBUq2q09tTCa3mjijun2NfK78NMouDYNMBkOrPZiS+ig==", + "dev": true, + "requires": { + "domelementtype": "^2.0.1", + "domhandler": "^4.2.0", + "entities": "^2.0.0" + }, + "dependencies": { + "entities": { + "version": "2.2.0", + "resolved": "https://registry.npmjs.org/entities/-/entities-2.2.0.tgz", + "integrity": "sha512-p92if5Nz619I0w+akJrLZH0MX0Pb5DX39XOwQTtXSdQQOaYH03S1uIQp4mhOZtAXrxq4ViO67YTiLBo2638o9A==", + "dev": true + } + } + }, + "domelementtype": { + "version": "2.2.0", + "resolved": "https://registry.npmjs.org/domelementtype/-/domelementtype-2.2.0.tgz", + "integrity": "sha512-DtBMo82pv1dFtUmHyr48beiuq792Sxohr+8Hm9zoxklYPfa6n0Z3Byjj2IV7bmr2IyqClnqEQhfgHJJ5QF0R5A==", + "dev": true + }, + "domhandler": { + "version": "4.2.2", + "resolved": "https://registry.npmjs.org/domhandler/-/domhandler-4.2.2.tgz", + "integrity": "sha512-PzE9aBMsdZO8TK4BnuJwH0QT41wgMbRzuZrHUcpYncEjmQazq8QEaBWgLG7ZyC/DAZKEgglpIA6j4Qn/HmxS3w==", + "dev": true, + "requires": { + "domelementtype": "^2.2.0" + } + }, + "domutils": { + "version": "2.8.0", + "resolved": "https://registry.npmjs.org/domutils/-/domutils-2.8.0.tgz", + "integrity": "sha512-w96Cjofp72M5IIhpjgobBimYEfoPjx1Vx0BSX9P30WBdZW2WIKU0T1Bd0kz2eNZ9ikjKgHbEyKx8BB6H1L3h3A==", + "dev": true, + "requires": { + "dom-serializer": "^1.0.1", + "domelementtype": "^2.2.0", + "domhandler": "^4.2.0" + } + }, + "entities": { + "version": "3.0.1", + "resolved": "https://registry.npmjs.org/entities/-/entities-3.0.1.tgz", + "integrity": "sha512-WiyBqoomrwMdFG1e0kqvASYfnlb0lp8M5o5Fw2OFq1hNZxxcNk8Ik0Xm7LxzBhuidnZB/UtBqVCgUz3kBOP51Q==", + "dev": true + }, "global-dirs": { "version": "3.0.0", "resolved": "https://registry.npmjs.org/global-dirs/-/global-dirs-3.0.0.tgz", @@ -36817,6 +37209,18 @@ "ini": "2.0.0" } }, + "htmlparser2": { + "version": "7.1.2", + "resolved": "https://registry.npmjs.org/htmlparser2/-/htmlparser2-7.1.2.tgz", + "integrity": "sha512-d6cqsbJba2nRdg8WW2okyD4ceonFHn9jLFxhwlNcLhQWcFPdxXeJulgOLjLKtAK9T6ahd+GQNZwG9fjmGW7lyg==", + "dev": true, + "requires": { + "domelementtype": "^2.0.1", + "domhandler": "^4.2.2", + "domutils": "^2.8.0", + "entities": "^3.0.1" + } + }, "is-installed-globally": { "version": "0.4.0", "resolved": "https://registry.npmjs.org/is-installed-globally/-/is-installed-globally-0.4.0.tgz", @@ -36893,33 +37297,27 @@ } }, "lint-staged": { - "version": "11.1.2", - "resolved": "https://registry.npmjs.org/lint-staged/-/lint-staged-11.1.2.tgz", - "integrity": "sha512-6lYpNoA9wGqkL6Hew/4n1H6lRqF3qCsujVT0Oq5Z4hiSAM7S6NksPJ3gnr7A7R52xCtiZMcEUNNQ6d6X5Bvh9w==", + "version": "11.2.2", + "resolved": "https://registry.npmjs.org/lint-staged/-/lint-staged-11.2.2.tgz", + "integrity": "sha512-rbtLCRTyndPJvtjpLwVjjb6K91jQrJ06oNArA4igPTGYlDCrJMIFbNDUAQGa4GRd8AjUBHkAAmq+K38tcmMaAQ==", "dev": true, "requires": { - "chalk": "^4.1.1", - "cli-truncate": "^2.1.0", - "commander": "^7.2.0", - "cosmiconfig": "^7.0.0", - "debug": "^4.3.1", + "cli-truncate": "2.1.0", + "colorette": "^1.4.0", + "commander": "^8.2.0", + "cosmiconfig": "^7.0.1", + "debug": "^4.3.2", "enquirer": "^2.3.6", - "execa": "^5.0.0", - "listr2": "^3.8.2", - "log-symbols": "^4.1.0", + "execa": "^5.1.1", + "listr2": "^3.12.2", "micromatch": "^4.0.4", "normalize-path": "^3.0.0", "please-upgrade-node": "^3.2.0", "string-argv": "0.3.1", - "stringify-object": "^3.3.0" + "stringify-object": "3.3.0", + "supports-color": "8.1.1" }, "dependencies": { - "commander": { - "version": "7.2.0", - "resolved": "https://registry.npmjs.org/commander/-/commander-7.2.0.tgz", - "integrity": "sha512-QrWXB+ZQSVPmIWIhtEO9H+gwHaMGYiF5ChvoJ+K9ZGHG/sVsa6yiesAD1GC/x46sET00Xlwo1u49RVVVzvcSkw==", - "dev": true - }, "debug": { "version": "4.3.2", "resolved": "https://registry.npmjs.org/debug/-/debug-4.3.2.tgz", @@ -36929,11 +37327,26 @@ "ms": "2.1.2" } }, + "has-flag": { + "version": "4.0.0", + "resolved": "https://registry.npmjs.org/has-flag/-/has-flag-4.0.0.tgz", + "integrity": "sha512-EykJT/Q1KjTWctppgIAgfSO0tKVuZUjhgMr17kqTumMl6Afv3EISleU7qZUzoXDFTAHTDC4NOoG/ZxU3EvlMPQ==", + "dev": true + }, "ms": { "version": "2.1.2", "resolved": "https://registry.npmjs.org/ms/-/ms-2.1.2.tgz", "integrity": "sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w==", "dev": true + }, + "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" + } } } }, @@ -36943,13 +37356,13 @@ "integrity": "sha512-4gvj9vKqSaLZGQPLcL0kg5CWT+d/gSLMCsoB3aD1W9nQbVViFBm22caGRFQRphpkHoLb+mQ//MHZcNp0lf8qkg==" }, "listr2": { - "version": "3.10.0", - "resolved": "https://registry.npmjs.org/listr2/-/listr2-3.10.0.tgz", - "integrity": "sha512-eP40ZHihu70sSmqFNbNy2NL1YwImmlMmPh9WO5sLmPDleurMHt3n+SwEWNu2kzKScexZnkyFtc1VI0z/TGlmpw==", + "version": "3.12.2", + "resolved": "https://registry.npmjs.org/listr2/-/listr2-3.12.2.tgz", + "integrity": "sha512-64xC2CJ/As/xgVI3wbhlPWVPx0wfTqbUAkpb7bjDi0thSWMqrf07UFhrfsGoo8YSXmF049Rp9C0cjLC8rZxK9A==", "dev": true, "requires": { "cli-truncate": "^2.1.0", - "colorette": "^1.2.2", + "colorette": "^1.4.0", "log-update": "^4.0.0", "p-map": "^4.0.0", "rxjs": "^6.6.7", @@ -36958,9 +37371,9 @@ }, "dependencies": { "ansi-regex": { - "version": "5.0.0", - "resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.0.tgz", - "integrity": "sha512-bY6fj56OUQ0hU1KjFNDQuJFezqKdrAyFdIevADiqrWHwSlbmBNMHp5ak2f40Pm8JTFyM2mqxkG6ngkHO11f/lg==", + "version": "5.0.1", + "resolved": "https://registry.npmjs.org/ansi-regex/-/ansi-regex-5.0.1.tgz", + "integrity": "sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==", "dev": true }, "ansi-styles": { @@ -36988,12 +37401,12 @@ "dev": true }, "strip-ansi": { - "version": "6.0.0", - "resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-6.0.0.tgz", - "integrity": "sha512-AuvKTrTfQNYNIctbR1K/YGTR1756GycPsg7b9bdV9Duqur4gv6aKqHXah67Z8ImS7WEz5QVcOtlfW2rZEugt6w==", + "version": "6.0.1", + "resolved": "https://registry.npmjs.org/strip-ansi/-/strip-ansi-6.0.1.tgz", + "integrity": "sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==", "dev": true, "requires": { - "ansi-regex": "^5.0.0" + "ansi-regex": "^5.0.1" } }, "wrap-ansi": { @@ -37212,16 +37625,6 @@ "resolved": "https://registry.npmjs.org/lodash.truncate/-/lodash.truncate-4.4.2.tgz", "integrity": "sha1-WjUNoLERO4N+z//VgSy+WNbq4ZM=" }, - "log-symbols": { - "version": "4.1.0", - "resolved": "https://registry.npmjs.org/log-symbols/-/log-symbols-4.1.0.tgz", - "integrity": "sha512-8XPvpAA8uyhfteu8pIvQxpJZ7SYYdpUivZpGy6sFsBuKRY/7rQGavedeB8aK+Zkyq6upMFVL/9AW6vOYzfRyLg==", - "dev": true, - "requires": { - "chalk": "^4.1.0", - "is-unicode-supported": "^0.1.0" - } - }, "log-update": { "version": "4.0.0", "resolved": "https://registry.npmjs.org/log-update/-/log-update-4.0.0.tgz", @@ -37426,19 +37829,21 @@ } }, "mdast-util-from-markdown": { - "version": "1.0.0", - "resolved": "https://registry.npmjs.org/mdast-util-from-markdown/-/mdast-util-from-markdown-1.0.0.tgz", - "integrity": "sha512-uj2G60sb7z1PNOeElFwCC9b/Se/lFXuLhVKFOAY2EHz/VvgbupTQRNXPoZl7rGpXYL6BNZgcgaybrlSWbo7n/g==", + "version": "1.0.3", + "resolved": "https://registry.npmjs.org/mdast-util-from-markdown/-/mdast-util-from-markdown-1.0.3.tgz", + "integrity": "sha512-8/GPJsE3h73C+PBFJ3cCdvegz07mLS8/5NfuIsP8q/cw/Ph/aximc6OYdfwerwcZqTYVu7WeXm/8+RDztxreZQ==", "requires": { "@types/mdast": "^3.0.0", "@types/unist": "^2.0.0", - "mdast-util-to-string": "^3.0.0", + "mdast-util-to-string": "^3.1.0", "micromark": "^3.0.0", "micromark-util-decode-numeric-character-reference": "^1.0.0", + "micromark-util-decode-string": "^1.0.0", "micromark-util-normalize-identifier": "^1.0.0", "micromark-util-symbol": "^1.0.0", "micromark-util-types": "^1.0.0", "parse-entities": "^3.0.0", + "power-assert": "^1.0.0", "unist-util-stringify-position": "^3.0.0" } }, @@ -37925,6 +38330,17 @@ "micromark-util-symbol": "^1.0.0" } }, + "micromark-util-decode-string": { + "version": "1.0.1", + "resolved": "https://registry.npmjs.org/micromark-util-decode-string/-/micromark-util-decode-string-1.0.1.tgz", + "integrity": "sha512-Wf3H6jLaO3iIlHEvblESXaKAr72nK7JtBbLLICPwuZc3eJkMcp4j8rJ5Xv1VbQWMCWWDvKUbVUbE2MfQNznwTA==", + "requires": { + "micromark-util-character": "^1.0.0", + "micromark-util-decode-numeric-character-reference": "^1.0.0", + "micromark-util-symbol": "^1.0.0", + "parse-entities": "^3.0.0" + } + }, "micromark-util-encode": { "version": "1.0.0", "resolved": "https://registry.npmjs.org/micromark-util-encode/-/micromark-util-encode-1.0.0.tgz", @@ -40021,9 +40437,9 @@ "integrity": "sha512-ojmeN0qd+y0jszEtoY48r0Peq5dwMEkIlCOu6Q5f41lfkswXuKtYrhgoTpLnyIcHm24Uhqx+5Tqm2InSwLhE6Q==" }, "path-parse": { - "version": "1.0.6", - "resolved": "https://registry.npmjs.org/path-parse/-/path-parse-1.0.6.tgz", - "integrity": "sha512-GSmOT2EbHrINBf9SR7CDELwlJ8AENk3Qn7OikK4nFYAu3Ote2+JYNVvkpAEQm3/TLNEJFD/xZJjzyxg3KBWOzw==" + "version": "1.0.7", + "resolved": "https://registry.npmjs.org/path-parse/-/path-parse-1.0.7.tgz", + "integrity": "sha512-LDJzPVEEEPR+y48z93A0Ed0yXb8pAByGWo/k5YYdYgpY2/2EsOsksJrq7lOHxryrVOn1ejG6oAp8ahvOIQD8sw==" }, "path-to-regexp": { "version": "0.1.7", @@ -40206,6 +40622,115 @@ "resolved": "https://registry.npmjs.org/postcss-value-parser/-/postcss-value-parser-4.1.0.tgz", "integrity": "sha512-97DXOFbQJhk71ne5/Mt6cOu6yxsSfM0QGQyl0L25Gca4yGWEGJaig7l7gbCX623VqTBNGLRLaVUCnNkcedlRSQ==" }, + "power-assert": { + "version": "1.6.1", + "resolved": "https://registry.npmjs.org/power-assert/-/power-assert-1.6.1.tgz", + "integrity": "sha512-VWkkZV6Y+W8qLX/PtJu2Ur2jDPIs0a5vbP0TpKeybNcIXmT4vcKoVkyTp5lnQvTpY/DxacAZ4RZisHRHLJcAZQ==", + "requires": { + "define-properties": "^1.1.2", + "empower": "^1.3.1", + "power-assert-formatter": "^1.4.1", + "universal-deep-strict-equal": "^1.2.1", + "xtend": "^4.0.0" + } + }, + "power-assert-context-formatter": { + "version": "1.2.0", + "resolved": "https://registry.npmjs.org/power-assert-context-formatter/-/power-assert-context-formatter-1.2.0.tgz", + "integrity": "sha512-HLNEW8Bin+BFCpk/zbyKwkEu9W8/zThIStxGo7weYcFkKgMuGCHUJhvJeBGXDZf0Qm2xis4pbnnciGZiX0EpSg==", + "requires": { + "core-js": "^2.0.0", + "power-assert-context-traversal": "^1.2.0" + } + }, + "power-assert-context-reducer-ast": { + "version": "1.2.0", + "resolved": "https://registry.npmjs.org/power-assert-context-reducer-ast/-/power-assert-context-reducer-ast-1.2.0.tgz", + "integrity": "sha512-EgOxmZ/Lb7tw4EwSKX7ZnfC0P/qRZFEG28dx/690qvhmOJ6hgThYFm5TUWANDLK5NiNKlPBi5WekVGd2+5wPrw==", + "requires": { + "acorn": "^5.0.0", + "acorn-es7-plugin": "^1.0.12", + "core-js": "^2.0.0", + "espurify": "^1.6.0", + "estraverse": "^4.2.0" + } + }, + "power-assert-context-traversal": { + "version": "1.2.0", + "resolved": "https://registry.npmjs.org/power-assert-context-traversal/-/power-assert-context-traversal-1.2.0.tgz", + "integrity": "sha512-NFoHU6g2umNajiP2l4qb0BRWD773Aw9uWdWYH9EQsVwIZnog5bd2YYLFCVvaxWpwNzWeEfZIon2xtyc63026pQ==", + "requires": { + "core-js": "^2.0.0", + "estraverse": "^4.1.0" + } + }, + "power-assert-formatter": { + "version": "1.4.1", + "resolved": "https://registry.npmjs.org/power-assert-formatter/-/power-assert-formatter-1.4.1.tgz", + "integrity": "sha1-XcEl7VCj37HdomwZNH879Y7CiEo=", + "requires": { + "core-js": "^2.0.0", + "power-assert-context-formatter": "^1.0.7", + "power-assert-context-reducer-ast": "^1.0.7", + "power-assert-renderer-assertion": "^1.0.7", + "power-assert-renderer-comparison": "^1.0.7", + "power-assert-renderer-diagram": "^1.0.7", + "power-assert-renderer-file": "^1.0.7" + } + }, + "power-assert-renderer-assertion": { + "version": "1.2.0", + "resolved": "https://registry.npmjs.org/power-assert-renderer-assertion/-/power-assert-renderer-assertion-1.2.0.tgz", + "integrity": "sha512-3F7Q1ZLmV2ZCQv7aV7NJLNK9G7QsostrhOU7U0RhEQS/0vhEqrRg2jEJl1jtUL4ZyL2dXUlaaqrmPv5r9kRvIg==", + "requires": { + "power-assert-renderer-base": "^1.1.1", + "power-assert-util-string-width": "^1.2.0" + } + }, + "power-assert-renderer-base": { + "version": "1.1.1", + "resolved": "https://registry.npmjs.org/power-assert-renderer-base/-/power-assert-renderer-base-1.1.1.tgz", + "integrity": "sha1-lqZQxv0F7hvB9mtUrWFELIs/Y+s=" + }, + "power-assert-renderer-comparison": { + "version": "1.2.0", + "resolved": "https://registry.npmjs.org/power-assert-renderer-comparison/-/power-assert-renderer-comparison-1.2.0.tgz", + "integrity": "sha512-7c3RKPDBKK4E3JqdPtYRE9cM8AyX4LC4yfTvvTYyx8zSqmT5kJnXwzR0yWQLOavACllZfwrAGQzFiXPc5sWa+g==", + "requires": { + "core-js": "^2.0.0", + "diff-match-patch": "^1.0.0", + "power-assert-renderer-base": "^1.1.1", + "stringifier": "^1.3.0", + "type-name": "^2.0.1" + } + }, + "power-assert-renderer-diagram": { + "version": "1.2.0", + "resolved": "https://registry.npmjs.org/power-assert-renderer-diagram/-/power-assert-renderer-diagram-1.2.0.tgz", + "integrity": "sha512-JZ6PC+DJPQqfU6dwSmpcoD7gNnb/5U77bU5KgNwPPa+i1Pxiz6UuDeM3EUBlhZ1HvH9tMjI60anqVyi5l2oNdg==", + "requires": { + "core-js": "^2.0.0", + "power-assert-renderer-base": "^1.1.1", + "power-assert-util-string-width": "^1.2.0", + "stringifier": "^1.3.0" + } + }, + "power-assert-renderer-file": { + "version": "1.2.0", + "resolved": "https://registry.npmjs.org/power-assert-renderer-file/-/power-assert-renderer-file-1.2.0.tgz", + "integrity": "sha512-/oaVrRbeOtGoyyd7e4IdLP/jIIUFJdqJtsYzP9/88R39CMnfF/S/rUc8ZQalENfUfQ/wQHu+XZYRMaCEZmEesg==", + "requires": { + "power-assert-renderer-base": "^1.1.1" + } + }, + "power-assert-util-string-width": { + "version": "1.2.0", + "resolved": "https://registry.npmjs.org/power-assert-util-string-width/-/power-assert-util-string-width-1.2.0.tgz", + "integrity": "sha512-lX90G0igAW0iyORTILZ/QjZWsa1MZ6VVY3L0K86e2eKun3S4LKPH4xZIl8fdeMYLfOjkaszbNSzf1uugLeAm2A==", + "requires": { + "eastasianwidth": "^0.2.0" + } + }, "prelude-ls": { "version": "1.1.2", "resolved": "https://registry.npmjs.org/prelude-ls/-/prelude-ls-1.1.2.tgz", @@ -40256,9 +40781,9 @@ "optional": true }, "prismjs": { - "version": "1.24.1", - "resolved": "https://registry.npmjs.org/prismjs/-/prismjs-1.24.1.tgz", - "integrity": "sha512-mNPsedLuk90RVJioIky8ANZEwYm5w9LcvCXrxHlwf4fNVSn8jEipMybMkWUyyF0JhnC+C4VcOVSBuHRKs1L5Ow==" + "version": "1.25.0", + "resolved": "https://registry.npmjs.org/prismjs/-/prismjs-1.25.0.tgz", + "integrity": "sha512-WCjJHl1KEWbnkQom1+SzftbtXMKQoezOCYs5rECqMN+jP+apI7ftoflyqigqzopSO3hMhTEb0mFClA8lkolgEg==" }, "private": { "version": "0.1.8", @@ -40806,13 +41331,13 @@ } }, "refractor": { - "version": "3.4.0", - "resolved": "https://registry.npmjs.org/refractor/-/refractor-3.4.0.tgz", - "integrity": "sha512-dBeD02lC5eytm9Gld2Mx0cMcnR+zhSnsTfPpWqFaMgUMJfC9A6bcN3Br/NaXrnBJcuxnLFR90k1jrkaSyV8umg==", + "version": "3.5.0", + "resolved": "https://registry.npmjs.org/refractor/-/refractor-3.5.0.tgz", + "integrity": "sha512-QwPJd3ferTZ4cSPPjdP5bsYHMytwWYnAN5EEnLtGvkqp/FCCnGsBgxrm9EuIDnjUC3Uc/kETtvVi7fSIVC74Dg==", "requires": { "hastscript": "^6.0.0", "parse-entities": "^2.0.0", - "prismjs": "~1.24.0" + "prismjs": "~1.25.0" }, "dependencies": { "character-entities": { @@ -42655,6 +43180,16 @@ "define-properties": "^1.1.3" } }, + "stringifier": { + "version": "1.4.0", + "resolved": "https://registry.npmjs.org/stringifier/-/stringifier-1.4.0.tgz", + "integrity": "sha512-cNsMOqqrcbLcHTXEVmkw9y0fwDwkdgtZwlfyolzpQDoAE1xdNGhQhxBUfiDvvZIKl1hnUEgMv66nHwtMz3OjPw==", + "requires": { + "core-js": "^2.0.0", + "traverse": "^0.6.6", + "type-name": "^2.0.1" + } + }, "stringify-entities": { "version": "4.0.1", "resolved": "https://registry.npmjs.org/stringify-entities/-/stringify-entities-4.0.1.tgz", @@ -43233,6 +43768,11 @@ "punycode": "^2.1.1" } }, + "traverse": { + "version": "0.6.6", + "resolved": "https://registry.npmjs.org/traverse/-/traverse-0.6.6.tgz", + "integrity": "sha1-y99WD9e5r2MlAv7UD5GMFX6pcTc=" + }, "tree-kill": { "version": "1.2.2", "resolved": "https://registry.npmjs.org/tree-kill/-/tree-kill-1.2.2.tgz", @@ -43378,6 +43918,11 @@ "mime-types": "~2.1.24" } }, + "type-name": { + "version": "2.0.2", + "resolved": "https://registry.npmjs.org/type-name/-/type-name-2.0.2.tgz", + "integrity": "sha1-7+fUEj2KxSr/9/QMfk3sUmYAj7Q=" + }, "typedarray": { "version": "0.0.6", "resolved": "https://registry.npmjs.org/typedarray/-/typedarray-0.0.6.tgz", @@ -43600,9 +44145,9 @@ } }, "unist-util-visit": { - "version": "4.0.0", - "resolved": "https://registry.npmjs.org/unist-util-visit/-/unist-util-visit-4.0.0.tgz", - "integrity": "sha512-3HWTvrtU10/E7qgPznBfiOyG0TXj9W8c1GSfaI8L9GkaG1pLePiQPZ7E35a0R3ToQ/zcy4Im6aZ9WBgOTnv1MQ==", + "version": "4.1.0", + "resolved": "https://registry.npmjs.org/unist-util-visit/-/unist-util-visit-4.1.0.tgz", + "integrity": "sha512-n7lyhFKJfVZ9MnKtqbsqkQEk5P1KShj0+//V7mAcoI6bpbUjh3C/OG8HVD+pBihfh6Ovl01m8dkcv9HNqYajmQ==", "requires": { "@types/unist": "^2.0.0", "unist-util-is": "^5.0.0", @@ -43641,6 +44186,16 @@ } } }, + "universal-deep-strict-equal": { + "version": "1.2.2", + "resolved": "https://registry.npmjs.org/universal-deep-strict-equal/-/universal-deep-strict-equal-1.2.2.tgz", + "integrity": "sha1-DaSsL3PP95JMgfpN4BjKViyisKc=", + "requires": { + "array-filter": "^1.0.0", + "indexof": "0.0.1", + "object-keys": "^1.0.0" + } + }, "universal-user-agent": { "version": "6.0.0", "resolved": "https://registry.npmjs.org/universal-user-agent/-/universal-user-agent-6.0.0.tgz", diff --git a/package.json b/package.json index 287206dd26..da86d13531 100644 --- a/package.json +++ b/package.json @@ -16,7 +16,7 @@ "@primer/octicons": "^15.1.0", "@primer/octicons-react": "^15.1.0", "accept-language-parser": "^1.5.0", - "ajv": "^8.4.0", + "ajv": "^8.6.3", "ajv-formats": "^2.1.1", "browser-date-formatter": "^3.0.3", "change-case": "^4.1.2", @@ -32,7 +32,7 @@ "dotenv": "^10.0.0", "express": "^4.17.1", "express-basic-auth": "^1.2.0", - "express-rate-limit": "^5.3.0", + "express-rate-limit": "^5.4.1", "express-timeout-handler": "^2.2.2", "flat": "^5.0.2", "github-slugger": "^1.4.0", @@ -46,7 +46,7 @@ "helmet": "^4.6.0", "highlight.js": "^11.2.0", "highlightjs-graphql": "^1.0.2", - "hot-shots": "^8.5.1", + "hot-shots": "^8.5.2", "html-entities": "^2.3.2", "imurmurhash": "^0.1.4", "js-cookie": "^3.0.1", @@ -56,7 +56,7 @@ "lodash-es": "^4.17.21", "lunr": "^2.3.9", "lunr-languages": "^1.9.0", - "mdast-util-from-markdown": "^1.0.0", + "mdast-util-from-markdown": "^1.0.3", "mdast-util-to-string": "^3.1.0", "morgan": "^1.10.0", "next": "^11.1.2", @@ -92,27 +92,27 @@ "throng": "^5.0.0", "ts-dedent": "^2.2.0", "unified": "^10.1.0", - "unist-util-visit": "^4.0.0", + "unist-util-visit": "^4.1.0", "uuid": "^8.3.2", "walk-sync": "^3.0.0" }, "devDependencies": { "@actions/core": "^1.5.0", "@actions/github": "^5.0.0", - "@babel/core": "^7.15.5", + "@babel/core": "^7.15.8", "@babel/eslint-parser": "^7.15.4", "@babel/plugin-syntax-top-level-await": "^7.14.5", "@babel/plugin-transform-runtime": "^7.15.0", - "@babel/preset-env": "^7.15.6", + "@babel/preset-env": "^7.15.8", "@graphql-inspector/core": "^2.9.0", - "@graphql-tools/load": "^7.3.0", + "@graphql-tools/load": "^7.3.2", "@jest/globals": "^27.2.0", - "@octokit/rest": "^18.10.0", + "@octokit/rest": "^18.12.0", "@types/github-slugger": "^1.3.0", "@types/imurmurhash": "^0.1.1", "@types/js-cookie": "^2.2.7", - "@types/lodash": "^4.14.172", - "@types/react": "^17.0.20", + "@types/lodash": "^4.14.175", + "@types/react": "^17.0.27", "@types/react-dom": "^17.0.9", "@types/react-syntax-highlighter": "^13.5.2", "@types/uuid": "^8.3.1", @@ -139,7 +139,7 @@ "eslint-plugin-node": "^11.1.0", "eslint-plugin-promise": "^5.1.0", "event-to-promise": "^0.8.0", - "glob": "^7.1.7", + "glob": "^7.2.0", "graphql": "^15.5.3", "heroku-client": "^3.1.0", "http-status-code": "^2.1.0", @@ -151,8 +151,8 @@ "jest": "^27.2.0", "jest-github-actions-reporter": "^1.0.3", "jest-slow-test-reporter": "^1.0.0", - "linkinator": "^2.14.0", - "lint-staged": "^11.1.2", + "linkinator": "^2.14.4", + "lint-staged": "^11.2.2", "make-promises-safe": "^5.1.0", "minimatch": "^3.0.4", "mkdirp": "^1.0.4", diff --git a/script/deployment/deploy-to-staging.js b/script/deployment/deploy-to-staging.js index f2d200beec..9cc7b14bf3 100644 --- a/script/deployment/deploy-to-staging.js +++ b/script/deployment/deploy-to-staging.js @@ -558,7 +558,7 @@ See Heroku logs for more information:\n${logUrl}` timeout: 10000, // Maximum 10 second timeout per request retry: { limit: 7, // About 2 minutes 7 seconds of delay, plus active request time for 8 requests - statusCodes: [404].concat(got.defaults.options.retry.statusCodes), // 404 is extra + statusCodes: [404, 421].concat(got.defaults.options.retry.statusCodes), // prepend extras }, hooks: { beforeRetry: [ diff --git a/tests/browser/browser.js b/tests/browser/browser.js index 7979b8ae99..7329a63b35 100644 --- a/tests/browser/browser.js +++ b/tests/browser/browser.js @@ -48,6 +48,7 @@ describe('browser search', () => { await page.setViewport(initialViewport) }) // 404 page is statically generated with next, so search is not available, but may possibly be brought back + // Docs Engineering issue: 961 it.skip('works on 404 error page', async () => { await page.goto('http://localhost:4001/en/404') await page.click('[data-testid=search] input[type="search"]') @@ -438,6 +439,7 @@ describe('language banner', () => { }) // Skipping because next/links are disabled by default for now +// Docs Engineering issue: 962 describe.skip('next/link client-side navigation', () => { jest.setTimeout(60 * 1000) diff --git a/tests/content/category-pages.js b/tests/content/category-pages.js index bc44603a1a..78f4f1c447 100644 --- a/tests/content/category-pages.js +++ b/tests/content/category-pages.js @@ -153,6 +153,7 @@ describe('category pages', () => { }) // TODO: Unskip this test once the related script has been executed + // Docs Engineering issue: 963 test.skip('slugified title matches parent directory name', () => { // Get the parent directory name const categoryDirPath = path.dirname(indexAbsPath) diff --git a/tests/content/featured-links.js b/tests/content/featured-links.js index b76cf6e49e..200c556424 100644 --- a/tests/content/featured-links.js +++ b/tests/content/featured-links.js @@ -32,7 +32,7 @@ describe('featuredLinks', () => { ) }) - // Skipped. See issues/923 + // Skipped. Docs Engineering issue: 923 test.skip('localized intro links link to localized pages', async () => { const $ = await getDOM('/ja') const $featuredLinks = $('[data-testid=article-list] a') diff --git a/tests/content/site-data.js b/tests/content/site-data.js index 2dee3694a6..41bb57b5db 100644 --- a/tests/content/site-data.js +++ b/tests/content/site-data.js @@ -49,6 +49,7 @@ describe('siteData module (English)', () => { }) // TODO: re-enable once Janky flakyness is resolved + // Docs Engineering issue: 964 test.skip('backfills missing translated site data with English values', async () => { const newFile = path.join(__dirname, '../../data/newfile.yml') await fs.writeFile(newFile, 'newvalue: bar') @@ -84,6 +85,7 @@ describe('siteData module (English)', () => { expect(reusable.includes('1. ')).toBe(true) }) + // Docs Engineering issue: 965 test.skip('encodes bracketed parentheses to prevent them from becoming links', async () => { const reusable = get(data, 'ja.site.data.reusables.organizations.team_name') const expectation = `reusable should contain a bracket followed by a space. Actual value: ${reusable}` diff --git a/tests/rendering/header.js b/tests/rendering/header.js index f2e509093e..77ef563666 100644 --- a/tests/rendering/header.js +++ b/tests/rendering/header.js @@ -67,6 +67,7 @@ describe('header', () => { expect($('[data-testid=header-notification] a[href*="github.com/contact"]').length).toBe(1) }) + // Docs Engineering issue: 966 test.skip('does not display any notices for English', async () => { const $ = await getDOM('/en') expect($('[data-testid=header-notification]').length).toBe(0) @@ -151,7 +152,7 @@ describe('header', () => { expect(ghe.text().trim()).toBe('Enterprise administrators') }) - // Skipped. See issues/923 + // Skipped. Docs Engineering issue: 923 test.skip("point to homepages in the current page's language", async () => { const $ = await getDOM( '/ja/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests' diff --git a/tests/rendering/page-titles.js b/tests/rendering/page-titles.js index ae0082da82..8877130fa3 100644 --- a/tests/rendering/page-titles.js +++ b/tests/rendering/page-titles.js @@ -46,6 +46,7 @@ describe('page titles', () => { // TODO enable this once translated content has synced with the versioning changes // Note the expected translations may need to be updated, since the English title changed // from `GitHub.com Help Documentation` to `GitHub Documentation` + // Docs Engineering issue: 967 test.skip('displays only the site name on localized homepages', async () => { expect((await getDOM('/cn'))('title').text()).toBe('GitHub 帮助文档') expect((await getDOM('/ja'))('title').text()).toBe('GitHub ヘルプドキュメント') diff --git a/tests/rendering/server.js b/tests/rendering/server.js index e5795c4f97..6e39e2a12b 100644 --- a/tests/rendering/server.js +++ b/tests/rendering/server.js @@ -636,6 +636,7 @@ describe('server', () => { // this oneoff redirect is temporarily disabled because it introduces too much complexity // we can reenable it down the road if needed + // Docs Engineering issue: 968 test.skip('redirects versioned category page', async () => { const res = await get('/en/github/receiving-notifications-about-activity-on-github') expect(res.statusCode).toBe(301) @@ -899,6 +900,7 @@ describe('search', () => { }) // SKIPPING: Can we have duplicate IDs? search-input-container and search-results-container are duplicated for mobile and desktop + // Docs Engineering issue: 969 it.skip('articles pages do not render any elements with duplicate IDs', async () => { const $ = await getDOM('/en/articles/accessing-an-organization') const ids = $('body') diff --git a/tests/unit/openapi-schema.js b/tests/unit/openapi-schema.js index 59aaf49414..789b6aef31 100644 --- a/tests/unit/openapi-schema.js +++ b/tests/unit/openapi-schema.js @@ -157,7 +157,7 @@ describe('x-codeSamples for @octokit/core.js', () => { }) // skipped because the definition is current missing the `content-type` parameter - // See GitHub issue #155943 + // GitHub GitHub issue: 155943 test.skip('operation with content-type parameter', () => { const operation = findOperation('POST', '/markdown/raw') expect(isPlainObject(operation)).toBe(true) diff --git a/tests/unit/page.js b/tests/unit/page.js index 094be7df90..1c78e366ff 100644 --- a/tests/unit/page.js +++ b/tests/unit/page.js @@ -403,6 +403,7 @@ describe('Page class', () => { ]) }) + // Docs Engineering issue: 970 it.skip('renders learning tracks that have been defined', async () => { // getLinkData.mockImplementation((guides) => { return guides }) const guides = ['/path/guide1', '/path/guide2'] @@ -486,6 +487,7 @@ describe('Page class', () => { expect(page.includeGuides).toStrictEqual(['/path/guide1', '/path/guide2', '/path/guide3']) }) + // Docs Engineering issue: 971 it.skip('renders guides and topics', async () => { /* getLinkData.mockImplementation(() => { return [{ @@ -553,10 +555,11 @@ describe('Page class', () => { }) describe('page.versions frontmatter', () => { + // Docs Engineering issue: 972 test.skip('pages that apply to older enterprise versions', async () => { // There are none of these in the content at this time! }) - + // Docs Engineering issue: 972 test.skip('pages that apply to newer enterprise versions', async () => { // There are none of these in the content at this time! }) diff --git a/tests/unit/pages.js b/tests/unit/pages.js index 4ac4e50f30..fec86b5872 100644 --- a/tests/unit/pages.js +++ b/tests/unit/pages.js @@ -149,6 +149,7 @@ describe('pages module', () => { expect(liquidErrors.length, failureMessage).toBe(0) }) + // Docs PR: 20035 test.skip('every non-English page has a matching English page', async () => { const englishPaths = chain(pages) .filter((page) => page.languageCode === 'en') diff --git a/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md b/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md index 7bc8e17ee8..b81e9ddc61 100644 --- a/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md +++ b/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md @@ -45,7 +45,7 @@ Wenn Du Benachrichtigungen in Deinem Posteingang abmeldest, werden diese automat {% data reusables.notifications.access_notifications %} 1. Wähle im Posteingang für Benachrichtigungen diejenige Benachrichtigungen aus, die Du abmelden möchtest. -2. Use the **selected** {% octicon "triangle-down" aria-label="The down triangle icon" %} drop-down to click **Unsubscribe.** ![Unsubscribe option from main inbox](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png) +2. Click **Unsubscribe.** ![Unsubscribe option from main inbox](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png) ## Abmeldung von Benachrichtigungen auf der Abonnementseite @@ -61,13 +61,12 @@ Wenn Du ein Repository nicht mehr beobachtest, meldest Du Dich von zukünftigen {% data reusables.notifications.access_notifications %} 1. Verwende in der linken Seitenleiste, unterhalb der Liste der Repositorys, das Dropdownmenü „Manage Notifications" (Benachrichtigungen verwalten) und klicke auf **Watched repositories** (beobachtete Repositorys). ![Dropdownmenü-Optionen „Manage Notifications" (Benachrichtigungen verwalten)](/assets/images/help/notifications-v2/manage-notifications-options.png) 2. Nimm auf der Seite der beobachteten Repositorys eine Bewertung dieser Repositorys vor und wähle dann aus: - {% ifversion ghae or ghes < 3.1 %} - - Ein Repository nicht mehr beobachten - - Only watch releases for a repository - - Ignore all notifications for a repository - {% endif %} {% ifversion fpt or ghes > 3.0 or ghae-next %} - Ein Repository nicht mehr beobachten - Ignore all notifications for a repository - Customize the types of event you receive notifications for ({% data reusables.notifications-v2.custom-notification-types %}, if enabled) + {% else %} + - Ein Repository nicht mehr beobachten + - Only watch releases for a repository + - Ignore all notifications for a repository {% endif %} diff --git a/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md b/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md index 3eaa04d9fd..2ea99bf807 100644 --- a/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md +++ b/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md @@ -70,10 +70,10 @@ Viele Personen vergessen Repositorys, die sie in der Vergangenheit beobachtet ha 1. Verwende in der linken Seitenleiste, unterhalb der Liste der Repositorys, das Dropdownmenü „Manage Notifications" (Benachrichtigungen verwalten) und klicke auf **Watched repositories** (beobachtete Repositorys). ![Dropdownmenü-Optionen „Manage Notifications" (Benachrichtigungen verwalten)](/assets/images/help/notifications-v2/manage-notifications-options.png) 2. Evaluiere die von Dir beobachteten Repositorys und entscheide, ob deren Aktualisierungen für Dich immer noch relevant und hilfreich sind. Wenn Du ein Repository beobachtest, wirst Du über alle Unterhaltungen für dieses Repository benachrichtigt. -{% ifversion ghae or ghes < 3.1 %} - ![Seite der beobachteten Benachrichtigungen](/assets/images/help/notifications-v2/watched-notifications.png) -{% elsif fpt or ghes > 3.0 or ghae-next %} +{% ifversion fpt or ghes > 3.0 or ghae-next %} ![Seite der beobachteten Benachrichtigungen](/assets/images/help/notifications-v2/watched-notifications-custom.png) +{% else %} + ![Seite der beobachteten Benachrichtigungen](/assets/images/help/notifications-v2/watched-notifications.png) {% endif %} {% tip %} diff --git a/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md b/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md index dc2f4d2715..3e43f7d194 100644 --- a/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md +++ b/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md @@ -29,7 +29,7 @@ Du kannst Benachrichtigungen abonnieren für: - Eine Unterhaltung in einem spezifischen Issue, Pull Request oder Gist. - Alle Aktivitäten in einem Repository oder in einer Team-Diskussion. - CI-Aktivität wie beispielsweise der Status von Workflows in Repositorys, die mit {% data variables.product.prodname_actions %} aufgesetzt wurden. {% ifversion fpt or ghes > 3.0 or ghae-next %} -- Repository {% data reusables.notifications-v2.custom-notification-types %} (if enabled). {% elsif ghae or ghes %} +- Repository {% data reusables.notifications-v2.custom-notification-types %} (if enabled).{% else %} - Releases in a repository.{% endif %} Du kannst auch automatisch alle Repositorys überwachen, auf die Du Push-Zugriff hast, mit Ausnahme von Forks. Du kannst jedes andere Repository, auf das Du Zugriff hast, manuell verfolgen durch klicken auf **Watch** (Beobachten). diff --git a/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md b/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md index e8e580338e..2a84d001dd 100644 --- a/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md +++ b/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md @@ -70,12 +70,14 @@ E-Mail-Benachrichtigungen ermöglichen auch Flexibilität bei der Art von Benach Wenn Du ein Repository beobachtest, abonnierst Du Aktualisierungen für Aktivitäten in diesem Repository. Ebenfalls, wenn Du die Diskussionen eines bestimmten Teams verfolgst, abonnierst Du alle Aktualisierungen der Unterhaltung auf der Seite dieses Teams. Weitere Informationen finden Sie unter „[Informationen zu Teamdiskussionen](/organizations/collaborating-with-your-team/about-team-discussions)“. To see repositories that you're watching, go to your [watching page](https://github.com/watching). Weitere Informationen findest Du unter „[Abonnements und Benachrichtigungen auf GitHub verwalten](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)." + {% ifversion ghae or ghes < 3.1 %} ### Benachrichtigungen konfigurieren {% endif %} -You can configure notifications for a repository on the repository page, or on your watching page.{% ifversion ghae or ghes < 3.1 %} You can choose to only receive notifications for releases in a repository, or ignore all notifications for a repository.{% endif %} +You can configure notifications for a repository on the repository page, or on your watching page.{% ifversion ghes < 3.1 %} You can choose to only receive notifications for releases in a repository, or ignore all notifications for a repository.{% endif %} {% ifversion fpt or ghes > 3.0 or ghae-next %} + ### About custom notifications You can customize notifications for a repository. For example, you can choose to only be notified when updates to one or more types of events ({% data reusables.notifications-v2.custom-notification-types %}) happen within a repository, or ignore all notifications for a repository. {% endif %} For more information, see "[Configuring your watch settings for an individual repository](#configuring-your-watch-settings-for-an-individual-repository)" below. @@ -158,25 +160,18 @@ Wenn "Automatisch Repositories beobachten" deaktiviert ist, wirst Du auch nicht ## Konfiguration der Beobachtungseinstellungen für ein einzelnes Repository -Du kannst wählen, ob Du ein einzelnes Repository ansehen möchtest oder nicht mehr. You can also choose to only be notified of {% ifversion fpt or ghes > 3.0 or ghae-next %}certain event types such as {% data reusables.notifications-v2.custom-notification-types %} (if enabled for the repository){% else %}new releases{% endif %}, or completely ignore an individual repository. +Du kannst wählen, ob Du ein einzelnes Repository ansehen möchtest oder nicht mehr. You can also choose to only be notified of {% ifversion fpt or ghes > 3.0 or ghae-next %}certain event types such as {% data reusables.notifications-v2.custom-notification-types %} (if enabled for the repository) {% else %}new releases{% endif %}, or completely ignore an individual repository. {% data reusables.repositories.navigate-to-repo %} 2. Klicke in der oberen rechten Ecke auf das Dropdownmenü „Watch" (Beobachten), um eine der Beobachtungsoptionen zu wählen. -{% ifversion ghae or ghes < 3.1 %} - ![Beobachtungsoptionen in einem Dropdownmenü für ein Repository](/assets/images/help/notifications-v2/watch-repository-options.png) -{% elsif fpt or ghes > 3.0 or ghae-next %} +{% ifversion fpt or ghes > 3.0 or ghae-next %} ![Beobachtungsoptionen in einem Dropdownmenü für ein Repository](/assets/images/help/notifications-v2/watch-repository-options-custom.png) -The **Custom** option allows you to further customize notifications so that you're only notified when specific events happen in the repository, in addition to participating and @mentions. - -{% ifversion fpt or ghes > 3.1 or ghae-issue-4910 %} - ![Custom watch options in a drop-down menu for a repository](/assets/images/help/notifications-v2/watch-repository-options-custom2-dotcom.png) + The **Custom** option allows you to further customize notifications so that you're only notified when specific events happen in the repository, in addition to participating and @mentions. {% else %} - ![Custom watch options in a drop-down menu for a repository](/assets/images/enterprise/3.1/help/notifications-v2/watch-repository-options-custom2.png) -{% endif %} - -If you select "Issues", you will be notified about, and subscribed to, updates on every issue (including those that existed prior to you selecting this option) in the repository. If you're @mentioned in a pull request in this repository, you'll receive notifications for that too, and you'll be subscribed to updates on that specific pull request, in addition to being notified about issues. - + ![Beobachtungsoptionen in einem Dropdownmenü für ein Repository](/assets/images/help/notifications-v2/watch-repository-options.png){% endif %} +{% ifversion fpt or ghes > 3.0 or ghae-next %} + ![Custom watch options in a drop-down menu for a repository](/assets/images/help/notifications-v2/watch-repository-options-custom2-dotcom.png) If you select "Issues", you will be notified about, and subscribed to, updates on every issue (including those that existed prior to you selecting this option) in the repository. If you're @mentioned in a pull request in this repository, you'll receive notifications for that too, and you'll be subscribed to updates on that specific pull request, in addition to being notified about issues. {% endif %} ## Wähle, wohin die E-Mail-Benachrichtigungen Deiner Organisation gesendet werden diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md index 13b2d802f5..bc99c3e2e2 100644 --- a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md +++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md @@ -48,6 +48,14 @@ Wenn Sie ein Konto anlegen, stellt {% data variables.product.product_name %} Ihn Du kannst den Namen, der in Deinem Profil angezeigt wird, ändern. This name may also be displayed next to comments you make on private repositories owned by an organization. Weitere Informationen findest Du unter „[Anzeige der Mitgliedsnamen in Deiner Organisation verwalten](/articles/managing-the-display-of-member-names-in-your-organization)“. +{% ifversion fpt %} +{% note %} + +**Note:** If you're a member of an {% data variables.product.prodname_emu_enterprise %}, any changes to your profile name must be made through your identity provider instead of {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.emu-more-info-account %} + +{% endnote %} +{% endif %} + {% data reusables.user_settings.access_settings %} 2. Gib unter „Name“ den Namen ein, der in Deinem Profil angezeigt werden soll. ![Feld „Name“ (Name) in den Profileinstellungen](/assets/images/help/profile/name-field.png) diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/index.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/index.md index a585053bb2..fcb15e23b1 100644 --- a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/index.md +++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/index.md @@ -14,7 +14,7 @@ children: - /viewing-contributions-on-your-profile - /showing-an-overview-of-your-activity-on-your-profile - /publicizing-or-hiding-your-private-contributions-on-your-profile - - /sending-your-github-enterprise-server-contributions-to-your-githubcom-profile + - /sending-enterprise-contributions-to-your-githubcom-profile - /why-are-my-contributions-not-showing-up-on-my-profile - /troubleshooting-commits-on-your-timeline shortTitle: Manage contribution graph diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md index 4db48ecc9c..9fbb5d0c06 100644 --- a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md +++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md @@ -14,14 +14,18 @@ topics: shortTitle: Private contributions --- -Wenn Du Deine privaten Beiträge veröffentlichst, können Benutzer, die keinen Zugriff auf die Repositorys haben, an denen Du mitarbeitest, die Informationen zu Deinen privaten Beiträgen nicht sehen. Stattdessen sehen sie die Anzahl an privaten Beiträgen, die Du pro Tag geleistet hast. Zu Deinen öffentlichen Beiträgen werden detaillierte Informationen angezeigt. Weitere Informationen findest Du unter „[Beiträge auf Deiner Profilseite anzeigen](/articles/viewing-contributions-on-your-profile-page)“. +Wenn Du Deine privaten Beiträge veröffentlichst, können Benutzer, die keinen Zugriff auf die Repositorys haben, an denen Du mitarbeitest, die Informationen zu Deinen privaten Beiträgen nicht sehen. Stattdessen sehen sie die Anzahl an privaten Beiträgen, die Du pro Tag geleistet hast. Zu Deinen öffentlichen Beiträgen werden detaillierte Informationen angezeigt. For more information, see "[Viewing contributions on your profile page](/articles/viewing-contributions-on-your-profile-page)." + +{% note %} + +**Note:** {% ifversion fpt or ghes %}On {% ifversion fpt %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_name %}{% endif %}, public contributions on your profile are visible {% ifversion fpt %}to anyone in the world who can access {% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}only to other users of {% data variables.product.product_location%}{% endif %}.{% elsif ghae %}On {% data variables.product.prodname_ghe_managed %}, only other members of your enterprise can see the contributions on your profile.{% endif %} + +{% endnote %} ## Die Sichtbarkeit Deiner privaten Beiträge ändern -Standardmäßig sehen Besucher nur die öffentlichen Beiträge in Deinem Profil. - {% data reusables.profile.access_profile %} -2. Veröffentliche Deine privaten Beiträge in Deinem Profil, oder blende sie aus: +1. Veröffentliche Deine privaten Beiträge in Deinem Profil, oder blende sie aus: - Um Deine privaten Beiträge zu veröffentlichen, wähle über Deinem Beteiligungsdiagramm im Dropdownmenü **Contribution settings** (Beitragseinstellungen) die Option **Private contributions** (Private Beiträge) aus. Besucher sehen die Anzahl Deiner privaten Beiträge ohne weitere Details. ![Im Dropdownmenü mit den Beitragseinstellungen festlegen, dass Besucher private Beiträge sehen können](/assets/images/help/profile/private-contributions-on.png) - Um Deine privaten Beiträge auszublenden, hebe über Deinem Beteiligungsdiagramm im Dropdownmenü **Contribution settings** (Beitragseinstellungen) die Auswahl der Option **Private contributions** (Private Beiträge) auf. Besucher sehen dann nur Deine öffentlichen Beiträge. ![Im Dropdownmenü mit den Beitragseinstellungen festlegen, dass Besucher private Beiträge sehen können](/assets/images/help/profile/private-contributions-off.png) diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md b/translations/de-DE/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 new file mode 100644 index 0000000000..c4c1a10f24 --- /dev/null +++ b/translations/de-DE/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 @@ -0,0 +1,65 @@ +--- +title: Sending enterprise contributions to your GitHub.com profile +intro: 'Sie können Ihre Arbeiten auf {% data variables.product.prodname_enterprise %} hervorheben, indem Sie die Anzahl Ihrer Beiträge an Ihr {% data variables.product.prodname_dotcom_the_website %}-Profil senden.' +redirect_from: + - /articles/sending-your-github-enterprise-contributions-to-your-github-com-profile/ + - /articles/sending-your-github-enterprise-server-contributions-to-your-github-com-profile + - /articles/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile + - /github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile + - /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile +versions: + fpt: '*' + ghes: '*' + ghae: next +topics: + - Profiles +shortTitle: Send enterprise contributions +--- + +## About enterprise contributions on your {% data variables.product.prodname_dotcom_the_website %} profile + +Your {% data variables.product.prodname_dotcom_the_website %} profile shows {% ifversion fpt %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae-next %} or {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} contribution counts from the past 90 days. Die {% data reusables.github-connect.sync-frequency %}-Anzahl Ihrer Beiträge aus {% data variables.product.prodname_enterprise %} wird unter Ihren privaten Beiträgen erfasst. The commit details will only show the contribution counts and that these contributions were made in a {% data variables.product.prodname_enterprise %} environment outside of {% data variables.product.prodname_dotcom_the_website %}. + +You can decide whether to show counts for private contributions on your profile. Weitere Informationen findest Du unter „[Private Beiträge in Deinem Profil veröffentlichen oder verbergen](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile/).“ + +Weitere Informationen zur Berechnung der Beitragszahlen findest Du unter „[Beteiligungsdiagramme in Deinem Profil verwalten](/articles/managing-contribution-graphs-on-your-profile/).“ + +{% note %} + +**Hinweise:** +- Für die Verbindung zwischen Deinen Konten gilt die GitHub-Datenschutzerklärung. Benutzer, die diese Verbindung aktivieren, stimmen den Nutzungsbedingungen von GitHub zu. + +- Before you can connect your {% ifversion fpt %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae-next %} or {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} profile to your {% data variables.product.prodname_dotcom_the_website %} profile, your enterprise owner must enable {% data variables.product.prodname_github_connect %} and enable contribution sharing between the environments. For more information, contact your enterprise owner. + +{% endnote %} + +{% ifversion fpt or ghes or ghae %} + +## Sending your enterprise contributions to your {% data variables.product.prodname_dotcom_the_website %} profile + +{% ifversion fpt %} + +- To send enterprise contributions from {% data variables.product.prodname_ghe_server %} to your {% data variables.product.prodname_dotcom_the_website %} profile, see "[Sending enterprise contributions to your {% data variables.product.prodname_dotcom_the_website %} profile](/enterprise-server/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)" in the {% data variables.product.prodname_ghe_server %} documentation.{% ifversion ghae-next %} +- To send enterprise contributions from {% data variables.product.prodname_ghe_managed %} to your {% data variables.product.prodname_dotcom_the_website %} profile, see "[Sending enterprise contributions to your {% data variables.product.prodname_dotcom_the_website %} profile](/github-ae@latest/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)" in the {% data variables.product.prodname_ghe_managed %} documentation.{% endif %} + +{% elsif ghes %} + +1. Sign in to {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_dotcom_the_website %}. +1. On {% data variables.product.prodname_ghe_server %}, in the upper-right corner of any page, click your profile photo, then click **Settings**. ![Symbol „Settings" (Einstellungen) auf der Benutzerleiste](/assets/images/help/settings/userbar-account-settings.png) +{% data reusables.github-connect.github-connect-tab-user-settings %} +{% data reusables.github-connect.connect-dotcom-and-enterprise %} +1. Überprüfe die Ressourcen, auf welche {% data variables.product.prodname_ghe_server %} von Deinem {% data variables.product.prodname_dotcom_the_website %}-Konto zugreifen wird, dann klicke **Authorize** (Autorisieren). ![Autorisiere die Verbindung zwischen dem GitHub Enterprise Server und GitHub.com](/assets/images/help/settings/authorize-ghe-to-connect-to-dotcom.png) +{% data reusables.github-connect.send-contribution-counts-to-githubcom %} + +{% elsif ghae %} + +1. Sign in to {% data variables.product.prodname_ghe_managed %} and {% data variables.product.prodname_dotcom_the_website %}. +1. On {% data variables.product.prodname_ghe_managed %}, in the upper-right corner of any page, click your profile photo, then click **Settings**. ![Symbol „Settings" (Einstellungen) auf der Benutzerleiste](/assets/images/help/settings/userbar-account-settings.png) +{% data reusables.github-connect.github-connect-tab-user-settings %} +{% data reusables.github-connect.connect-dotcom-and-enterprise %} +{% data reusables.github-connect.authorize-connection %} +{% data reusables.github-connect.send-contribution-counts-to-githubcom %} + +{% endif %} + +{% endif %} diff --git a/translations/de-DE/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/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md index a462658f56..949e659fa4 100644 --- a/translations/de-DE/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/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md @@ -83,7 +83,7 @@ Zeitstempel werden für Commits und Pull Requests unterschiedlich berechnet: ![Aktivitätsübersicht im Profil](/assets/images/help/profile/activity-overview-section.png) -Die in der Aktivitätsübersicht angezeigten Organisationen werden dementsprechend priorisiert, wie aktiv Sie in der Organisation sind. Wenn Sie in Ihrer Profil-Bio eine Organisation @erwähnen und Sie ein Organisationsmitglied sind, wird diese Organisation in der Aktivitätsübersicht priorisiert. Weitere Informationen finden Sie unter „[Personen und Teams erwähnen](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)“ oder „[Eine Biografie zu Ihrem Profil hinzufügen](/articles/adding-a-bio-to-your-profile/)“. +Die in der Aktivitätsübersicht angezeigten Organisationen werden dementsprechend priorisiert, wie aktiv Sie in der Organisation sind. Wenn Sie in Ihrer Profil-Bio eine Organisation @erwähnen und Sie ein Organisationsmitglied sind, wird diese Organisation in der Aktivitätsübersicht priorisiert. For more information, see "[Mentioning people and teams](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)” or "[Adding a bio to your profile](/articles/adding-a-bio-to-your-profile/)." ## Beitragsaktivität @@ -91,15 +91,14 @@ Der Abschnitt für die Beitragsaktivität enthält eine detaillierte Zeitleiste ![Zeitfilter für Beitragsaktivität](/assets/images/help/profile/contributions_activity_time_filter.png) -{% ifversion not ghae %} -## Beiträge von {% data variables.product.product_location_enterprise %} auf {% data variables.product.prodname_dotcom_the_website %} anzeigen +{% ifversion fpt or ghes or ghae-next %} + +## Beiträge von {% data variables.product.prodname_enterprise %} auf {% data variables.product.prodname_dotcom_the_website %} anzeigen + +If you use {% ifversion fpt %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae-next %} 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)." -Wenn Ihr Websiteadministrator {% data variables.product.prodname_unified_contributions %} aktiviert hat, können Sie die {% data variables.product.prodname_enterprise %}-Beitragsanzahl an Ihr {% data variables.product.prodname_dotcom_the_website %}-Profil senden. Weitere Informationen findest Du unter „[Deine {% data variables.product.prodname_ghe_server %}-Beiträge an Deine {% data variables.product.prodname_dotcom_the_website %} senden](/articles/sending-your-github-enterprise-server-contributions-to-your-github-com-profile).“ {% endif %} ## Weiterführende Informationen - „[Beiträge auf Ihrer Profilseite anzeigen](/articles/viewing-contributions-on-your-profile-page)“ -- „[Warum werden meine Beiträge nicht in meinem Profil angezeigt?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)“ -- „[Private Beiträge in Deinem Profil veröffentlichen oder verbergen](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)“ -- „[Übersicht über Deine Aktivitäten in Deinem Profil anzeigen](/articles/showing-an-overview-of-your-activity-on-your-profile)“ diff --git a/translations/de-DE/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/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md index 5530f06f26..b4cf27b9fd 100644 --- a/translations/de-DE/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/de-DE/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 @@ -24,6 +24,8 @@ Repositorys, die einer Organisation gehören, können feiner abgestufte Zugriffs {% ifversion fpt %} +If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you can only invite other members of your enterprise to collaborate with you. {% data reusables.enterprise-accounts.emu-more-info-account %} + {% note %} **Hinweis:** {% data variables.product.company_short %} beschränkt die Anzahl an Personen, die innerhalb von 24 Stunden zu einem Repository eingeladen werden können. Wenn Du diese Grenze überschreitest, musst Du entweder 24 Stunden warten oder eine Organisation erstellen, um mit mehr Benutzern zusammenzuarbeiten. diff --git a/translations/de-DE/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/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md index e70e4b9eea..0e890c6b39 100644 --- a/translations/de-DE/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/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md @@ -18,7 +18,9 @@ shortTitle: Add an email address {% note %} -**Hinweis:** {% data reusables.user_settings.no-verification-disposable-emails %} +**Hinweise**: + - {% data reusables.user_settings.no-verification-disposable-emails %} + - If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you cannot make changes to your email address on {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.emu-more-info-account %} {% endnote %} diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md index 320e57b1bd..68130ea138 100644 --- a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md +++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md @@ -31,6 +31,12 @@ Für Folgendes kann {% data variables.product.product_name %} keine Weiterleitun - [@Erwähnungen](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) des alten Benutzernamens - Links zu [Gists](/articles/creating-gists), die Deinen alten Benutzernamen enthalten +{% ifversion fpt %} + +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-Verweise Wenn Du Deinen Benutzernamen geändert hast, leitet {% data variables.product.product_name %} Verweise auf Deine Repositorys automatisch weiter. diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md index b1506091d6..79d3d3cb24 100644 --- a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md +++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md @@ -15,6 +15,7 @@ topics: children: - /about-your-personal-dashboard - /managing-your-theme-settings + - /managing-your-tab-size-rendering-preference - /changing-your-github-username - /merging-multiple-user-accounts - /converting-a-user-into-an-organization diff --git a/translations/de-DE/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/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md new file mode 100644 index 0000000000..469c57ad89 --- /dev/null +++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md @@ -0,0 +1,15 @@ +--- +title: Managing your tab size rendering preference +intro: You can manage the number of spaces a tab is equal to for your user account. +versions: + fpt: '*' +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 user settings sidebar, click **Appearance**. !["Appearance" tab in user settings sidebar](/assets/images/help/settings/appearance-tab.png) +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/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md index 64be820812..bdabf03262 100644 --- a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md +++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md @@ -3,6 +3,7 @@ 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: next ghes: '>=3.2' topics: - Accounts @@ -14,7 +15,15 @@ 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 ghae-issue-4618 %} People with visual impairment may benefit from the dark high contrast theme, with greater contrast between foreground and background elements.{% endif %} +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 ghae-issue-4618 %} 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 %} If you have colorblindness, you may benefit from our light and dark colorblind themes. + +{% note %} + +**Note:** The colorblind themes are currently in public beta. For more information on enabling features in public beta, see "[Exploring early access releases with feature preview](/get-started/using-github/exploring-early-access-releases-with-feature-preview)." + +{% endnote %}{% endif %} {% data reusables.user_settings.access_settings %} 1. In the user settings sidebar, click **Appearance**. !["Appearance" tab in user settings sidebar](/assets/images/help/settings/appearance-tab.png) @@ -24,6 +33,8 @@ You may want to use a dark theme to reduce power consumption on certain devices, {% ifversion fpt or ghae-issue-4618 %}![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 ghae-issue-4618 %}![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 ghae-issue-4619 %} + - 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 %} ## Weiterführende Informationen diff --git a/translations/de-DE/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/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md index 89bda239c1..da6da2ce04 100644 --- a/translations/de-DE/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/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md @@ -35,7 +35,7 @@ Der Repository-Inhaber besitzt die vollständige Kontrolle über das Repository. | {% ifversion fpt %}Invite collaborators{% else %}Add collaborators{% endif %} | | | „[Mitarbeiter in ein persönliches Repository einladen](/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 %} -| Limit interactions with the repository | "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)" |{% endif %}{% ifversion fpt or ghes > 3.0 %} +| Limit interactions with the repository | "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)" |{% endif %}{% ifversion fpt or ghes > 3.0 or ghae-next %} | Rename a branch, including the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" {% endif %} | Einen Pull Request auf einem geschützten Branch zusammenführen, selbst ohne genehmigende Reviews | „[Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches)“ | @@ -73,7 +73,7 @@ Collaborators can also perform the following actions. | Aktion | Weitere Informationen | |:----------------------------------------------------------------------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Fork the repository | "[About forks](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% ifversion fpt or ghes > 3.1 %} +| Fork the repository | "[About forks](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% ifversion fpt or ghes > 3.1 or ghae-next %} | 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](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)"
  • "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"
| diff --git a/translations/de-DE/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md b/translations/de-DE/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md index c3317ef7e4..1ae068e01d 100644 --- a/translations/de-DE/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md +++ b/translations/de-DE/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md @@ -15,8 +15,6 @@ topics: - Workflows --- -{% data reusables.actions.ae-beta %} - ## Informationen zum Zwischenspeichern von Workflow-Abhängigkeiten Workflow-Läufe verwenden häufig dieselben Ausgaben oder heruntergeladenen Abhängigkeiten in aufeinanderfolgenden Durchläufen. Tools zur Verwaltung von Paketen und Abhängigkeiten wie beispielsweise Maven, Gradle, npm und Yarn halten einen lokalen Cache mit heruntergeladenen Abhängigkeiten. diff --git a/translations/de-DE/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md b/translations/de-DE/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md index 5084e0c8e2..533c1b7fb7 100644 --- a/translations/de-DE/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md +++ b/translations/de-DE/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md @@ -20,11 +20,10 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Informationen zu Workflow-Artefakten -Artefakte erlauben es dir, Daten nach dem Job-Abschluss abzuspeichern und diese Daten an einen anderen Job im selben Workflow weiterzugeben. Ein Artefakt ist eine Datei oder eine Dateisammlung, die während einer Workflow-Ausführung erstellt wird. Zum Beispiel kannst Du Artefakte verwenden, um Deine Build- und Testausgabe zu speichern, nachdem ein Workflow-Lauf beendet ist. +Artefakte erlauben es dir, Daten nach dem Job-Abschluss abzuspeichern und diese Daten an einen anderen Job im selben Workflow weiterzugeben. Ein Artefakt ist eine Datei oder eine Dateisammlung, die während einer Workflow-Ausführung erstellt wird. Zum Beispiel kannst Du Artefakte verwenden, um Deine Build- und Testausgabe zu speichern, nachdem ein Workflow-Lauf beendet ist. {% data reusables.actions.reusable-workflow-artifacts %} {% data reusables.github-actions.artifact-log-retention-statement %} The retention period for a pull request restarts each time someone pushes a new commit to the pull request. diff --git a/translations/de-DE/content/actions/automating-builds-and-tests/about-continuous-integration.md b/translations/de-DE/content/actions/automating-builds-and-tests/about-continuous-integration.md index 85590393d5..d9b34b284d 100644 --- a/translations/de-DE/content/actions/automating-builds-and-tests/about-continuous-integration.md +++ b/translations/de-DE/content/actions/automating-builds-and-tests/about-continuous-integration.md @@ -1,6 +1,6 @@ --- title: Informationen zur fortlaufenden Integration -intro: 'Sie können benutzerdefinierte Continuous Integration (CI) und Continuous Deployment (CD)-Workflows direkt in Ihrem {% data variables.product.prodname_dotcom %} Repository mit {% data variables.product.prodname_actions %}erstellen.' +intro: 'You can create custom continuous integration (CI) workflows directly in your {% data variables.product.prodname_dotcom %} repository with {% data variables.product.prodname_actions %}.' product: '{% data reusables.gated-features.actions %}' redirect_from: - /articles/about-continuous-integration @@ -15,13 +15,11 @@ versions: type: overview topics: - CI - - CD shortTitle: Kontinuierliche Integration --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Informationen zur fortlaufenden Integration @@ -49,45 +47,12 @@ Sie können nicht nur ci-Workflows für Ihr Projekt einrichten, sondern auch {% Eine Definition von gebräuchliche Begriffe finden Sie unter "[Kernkonzepte für {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/core-concepts-for-github-actions)". -## Unterstützte Sprachen - +## Workflow templates {% data variables.product.product_name %} bietet CI-Workflowvorlagen für eine Vielzahl von Sprachen und Frameworks. Browse the complete list of CI workflow templates offered by {% data variables.product.product_name %} in the {% ifversion fpt %}[actions/starter-workflows](https://github.com/actions/starter-workflows/tree/main/ci) repository{% else %} `actions/starter-workflows` repository on {% data variables.product.product_location %}{% endif %}. -{% ifversion fpt or ghes > 3.0 or ghae-next %} -## Skipping workflow runs - -If you want to temporarily prevent a workflow from being triggered, you can add a skip instruction to the commit message. Workflows that would otherwise be triggered `on: push` or `on: pull_request`, won't be triggered if you add any of the following strings to the commit message in a push, or the HEAD commit of a pull request: - -* `[skip ci]` -* `[ci skip]` -* `[no ci]` -* `[skip actions]` -* `[actions skip]` - -Alternatively, you can end the commit message with two empty lines followed by either `skip-checks: true` or `skip-checks:true`. - -You won't be able to merge the pull request if your repository is configured to require specific checks to pass first. To allow the pull request to be merged you can push a new commit to the pull request without the skip instruction in the commit message. - -{% note %} - -**Note:** Skip instructions only apply to the `push` and `pull_request` events. For example, adding `[skip ci]` to a commit message won't stop a workflow that's triggered `on: pull_request_target` from running. - -{% endnote %} -{% endif %} - -## Benachrichtigungen für Workflow-Läufe - -{% data reusables.repositories.workflow-notifications %} - -## Status-Badges für Workflow-Läufe - -{% 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)." - ## Weiterführende Informationen {% ifversion fpt %} diff --git a/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md index 51fee62aad..45cb293310 100644 --- a/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md +++ b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md @@ -19,7 +19,6 @@ shortTitle: Build & test Java & Ant {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Einführung diff --git a/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md index 7000c3786c..c20146068c 100644 --- a/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md +++ b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md @@ -19,7 +19,6 @@ shortTitle: Build & test Java & Gradle {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Einführung diff --git a/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md index 0c13b8be55..082dd4c19f 100644 --- a/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md +++ b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md @@ -19,7 +19,6 @@ shortTitle: Build & test Java with Maven {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Einführung diff --git a/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-net.md b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-net.md index 491ab34bcb..0cfec25394 100644 --- a/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-net.md +++ b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-net.md @@ -13,7 +13,6 @@ shortTitle: Build & test .NET {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Einführung diff --git a/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md index c5c956c6ac..43659728f4 100644 --- a/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md +++ b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md @@ -22,7 +22,6 @@ hasExperimentalAlternative: true {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Einführung diff --git a/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-powershell.md b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-powershell.md index 52ad0c77a2..69ea85e882 100644 --- a/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-powershell.md +++ b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-powershell.md @@ -19,7 +19,6 @@ shortTitle: Build & test PowerShell {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Einführung diff --git a/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-python.md b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-python.md index 132cdb0b7d..266075cfdf 100644 --- a/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-python.md +++ b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-python.md @@ -21,7 +21,6 @@ hasExperimentalAlternative: true {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Einführung diff --git a/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-ruby.md b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-ruby.md index 4861ff9f0e..aa9596ce45 100644 --- a/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-ruby.md +++ b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-ruby.md @@ -17,7 +17,6 @@ shortTitle: Build & test Ruby {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Einführung diff --git a/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-swift.md b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-swift.md index 2353a99c7e..23a77fba2e 100644 --- a/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-swift.md +++ b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-swift.md @@ -17,7 +17,6 @@ shortTitle: Build & test Swift {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Einführung diff --git a/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md index 697a631889..58747feecd 100644 --- a/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md +++ b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md @@ -21,7 +21,6 @@ shortTitle: Build & test Xamarin apps {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Einführung diff --git a/translations/de-DE/content/actions/creating-actions/about-custom-actions.md b/translations/de-DE/content/actions/creating-actions/about-custom-actions.md index 84fcb49b71..0295c30390 100644 --- a/translations/de-DE/content/actions/creating-actions/about-custom-actions.md +++ b/translations/de-DE/content/actions/creating-actions/about-custom-actions.md @@ -20,7 +20,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About custom actions diff --git a/translations/de-DE/content/actions/creating-actions/creating-a-composite-action.md b/translations/de-DE/content/actions/creating-actions/creating-a-composite-action.md index 8fd72a79ba..351b274716 100644 --- a/translations/de-DE/content/actions/creating-actions/creating-a-composite-action.md +++ b/translations/de-DE/content/actions/creating-actions/creating-a-composite-action.md @@ -16,7 +16,6 @@ shortTitle: Composite action {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Einführung diff --git a/translations/de-DE/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/de-DE/content/actions/creating-actions/creating-a-docker-container-action.md index dd0ca151d4..402111aadd 100644 --- a/translations/de-DE/content/actions/creating-actions/creating-a-docker-container-action.md +++ b/translations/de-DE/content/actions/creating-actions/creating-a-docker-container-action.md @@ -20,7 +20,6 @@ shortTitle: Docker container action {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Einführung diff --git a/translations/de-DE/content/actions/creating-actions/creating-a-javascript-action.md b/translations/de-DE/content/actions/creating-actions/creating-a-javascript-action.md index 992eda0a8d..37b80b5fb4 100644 --- a/translations/de-DE/content/actions/creating-actions/creating-a-javascript-action.md +++ b/translations/de-DE/content/actions/creating-actions/creating-a-javascript-action.md @@ -20,7 +20,6 @@ shortTitle: JavaScript action {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Einführung diff --git a/translations/de-DE/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/translations/de-DE/content/actions/creating-actions/dockerfile-support-for-github-actions.md index 66fe80cdca..23ba0ffd51 100644 --- a/translations/de-DE/content/actions/creating-actions/dockerfile-support-for-github-actions.md +++ b/translations/de-DE/content/actions/creating-actions/dockerfile-support-for-github-actions.md @@ -14,7 +14,6 @@ type: reference {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Informationen zu Dockerfile-Anweisungen diff --git a/translations/de-DE/content/actions/creating-actions/index.md b/translations/de-DE/content/actions/creating-actions/index.md index 24c778ad01..6b0fb5db64 100644 --- a/translations/de-DE/content/actions/creating-actions/index.md +++ b/translations/de-DE/content/actions/creating-actions/index.md @@ -24,4 +24,3 @@ children: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} diff --git a/translations/de-DE/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/de-DE/content/actions/creating-actions/metadata-syntax-for-github-actions.md index 08891ca69d..60a958c2f7 100644 --- a/translations/de-DE/content/actions/creating-actions/metadata-syntax-for-github-actions.md +++ b/translations/de-DE/content/actions/creating-actions/metadata-syntax-for-github-actions.md @@ -17,13 +17,12 @@ type: reference {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Informationen zur YAML-Syntax für {% data variables.product.prodname_actions %} Für Docker- und JavaScript-Aktionen ist eine Metadatendatei erforderlich. Der Dateiname für die Metadaten muss entweder `action.yml` oder `action.yaml` sein. Die Daten in der Metadaten-Datei definieren die Eingaben, Ausgaben und der Haupteinstiegspunkt für die Aktion. -Aktionsmetadatendateien verwenden die YAML-Syntax. Wenn Sie bislang noch nicht mit YAML gearbeitet haben, lesen Sie den Artikel „[Learn YAML in five minutes](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)“. +Aktionsmetadatendateien verwenden die YAML-Syntax. Wenn YAML für Dich Neuland ist, lies den Artikel „[YAML in fünf Minuten lernen](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)“. ## `name` @@ -31,7 +30,7 @@ Aktionsmetadatendateien verwenden die YAML-Syntax. Wenn Sie bislang noch nicht m ## `Autor` -**Optional**: Der Name des Autors der Aktion. +**Optional** The name of the action's author. ## `Beschreibung` @@ -39,11 +38,11 @@ Aktionsmetadatendateien verwenden die YAML-Syntax. Wenn Sie bislang noch nicht m ## `inputs` -**Optional**: Mit Eingabeparametern können Sie die Daten angeben, welche die Aktion während der Laufzeit erwartet. {% data variables.product.prodname_dotcom %} speichert Eingabeparameter als Umgebungsvariablen. Eingabe-IDs in Großbuchstaben werden während der Laufzeit in Kleinbuchstaben umgewandelt. Sie sollten Eingabe-IDs in Kleinbuchstaben verwenden. +**Optional** Input parameters allow you to specify data that the action expects to use during runtime. {% data variables.product.prodname_dotcom %} speichert Eingabeparameter als Umgebungsvariablen. Eingabe-IDs in Großbuchstaben werden während der Laufzeit in Kleinbuchstaben umgewandelt. Du solltest Eingabe-IDs in Kleinbuchstaben verwenden. ### Beispiel -In diesem Beispiel werden zwei Eingaben konfiguriert: „numOctocats“ und „octocatEyeColor“. Die Eingabe „numOctocats“ ist nicht erforderlich und entspricht standardmäßig dem Wert „1“. Die Eingabe „octocatEyeColor“ ist erforderlich und weist keinen Standardwert auf. Workflow-Dateien, die diese Aktion einsetzen, müssen das Stichwort `with` verwenden, um für „octocatEyeColor“ einen Eingabewert festzulegen. Weitere Informationen zur `with`-Syntax findest Du unter „[Workflow-Syntax für {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepswith)“. +In diesem Beispiel werden zwei Eingaben konfiguriert: „numOctocats“ und „octocatEyeColor“. Die Eingabe „numOctocats“ ist nicht erforderlich und hat standardmäßig den Wert ‚1‘. Die Eingabe „octocatEyeColor“ ist erforderlich und hat keinen Standardwert. Workflow-Dateien, die diese Aktion nutzen, müssen das Schlüsselwort `with` verwenden, um für „octocatEyeColor“ einen Eingabewert festzulegen. Weitere Informationen zu `with`-Syntax finden Sie unter „[Workflow-Syntax für {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepswith)“. ```yaml inputs: @@ -56,7 +55,7 @@ inputs: required: true ``` -When you specify an input in a workflow file or use a default input value, {% data variables.product.prodname_dotcom %} creates an environment variable for the input with the name `INPUT_`. Die erstellte Umgebungsvariable wandelt Eingabenamen in Großbuchstaben um und ersetzt Leerzeichen durch `_`-Zeichen. +When you specify an input in a workflow file or use a default input value, {% data variables.product.prodname_dotcom %} creates an environment variable for the input with the name `INPUT_`. Der Name der aus dem Eingabenamen erstellten Umgebungsvariablen wird in Großbuchstaben umgewandelt und Leerzeichen werden durch das Zeichen `_` ersetzt. If the action is written using a [composite](/actions/creating-actions/creating-a-composite-action), then it will not automatically get `INPUT_`. If the conversion doesn't occur, you can change these inputs manually. @@ -66,7 +65,7 @@ For example, if a workflow defined the `numOctocats` and `octocatEyeColor` input ### `inputs.` -**Erforderlich** Ein Kennzeichner, der die Eingabe identifiziert, als `string`. Der Wert von `` ist eine Übersicht zu den Metadaten der Eingabe. Die `` muss im Objekt `inputs` als ein eindeutiger Kennzeichner vorhanden sein. Die `` muss mit einem Buchstaben oder `_` beginnen und darf nur alphanumerische Zeichen, `-` oder `_` enthalten. +**Erforderlich** Ein Kennzeichner, der die Eingabe identifiziert, als `string`. The value of `` is a map of the input's metadata. Die `` muss im Objekt `inputs` als ein eindeutiger Kennzeichner vorhanden sein. Die `` muss mit einem Buchstaben oder `_` beginnen und darf nur alphanumerische Zeichen, `-` oder `_` enthalten. ### `inputs..description` @@ -78,7 +77,7 @@ For example, if a workflow defined the `numOctocats` and `octocatEyeColor` input ### `inputs..default` -**Optional**: Ein `String`, der den Standardwert darstellt. Der Standardwert wird verwendet, wenn ein Eingabeparameter in einer Workflow-Datei nicht angegeben ist. +**Optional** A `string` representing the default value. Der Standardwert wird verwendet, wenn ein Eingabeparameter in einer Workflow-Datei nicht angegeben ist. ### `inputs..deprecationMessage` @@ -86,7 +85,7 @@ For example, if a workflow defined the `numOctocats` and `octocatEyeColor` input ## `outputs` -**Optional**: Ausgabeparameter erlauben Dir, Daten zu deklarieren, die eine Aktion setzt. Aktionen, die in einem Workflow später ausgeführt werden, können die Ausgabedaten der zuvor ausgeführten Aktionen verwenden. Wenn beispielsweise eine Aktion vorliegt, die zwei Eingaben addiert hat (x + y = z), kann die Aktion die Summe (z) für andere Aktionen ausgeben, damit sie als Eingabe verwendet wird. +**Optional**: Ausgabeparameter erlauben Dir, Daten zu deklarieren, die eine Aktion setzt. Aktionen, die in einem Workflow später ausgeführt werden, können die Ausgabedaten der zuvor ausgeführten Aktionen verwenden. Wenn beispielsweise eine Aktion vorliegt, die zwei Eingaben addiert hat (x + y = z), kann die Aktion die Summe (z) für andere Aktionen ausgeben, damit sie dort als Eingabe verwendet wird. Auch wenn Du in der Metadaten-Datei Deiner Aktion keine Ausgabe deklarierst, kannst Du dennoch Ausgaben festlegen und in einem Workflow verwenden. Weitere Informationen zum Festlegen von Ausgaben in einer Aktion findest Du unter "[Workflow-Befehle für {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions/#setting-an-output-parameter)." @@ -284,7 +283,7 @@ Es wird dringend empfohlen, die verwendete Version der Aktion zu nennen (Git-Ref - Wenn Du Dich auf die Hauptversion der Aktion beziehst, kannst Du kritische Fehlerbehebungen und Sicherheits-Patches erhalten und gleichzeitig die Kompatibilität wahren. Außerdem ist damit sichergestellt, dass der Workflow weiterhin problemlos arbeiteten sollte. - Using the default branch of an action may be convenient, but if someone releases a new major version with a breaking change, your workflow could break. -Für einige Aktionen sind Eingaben erforderlich, die Du mit dem Schlüsselwort [`with`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepswith) festlegen musst. Die erforderlichen Eingaben findest Du in der README-Datei der Aktion. +Some actions require inputs that you must set using the [`with`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepswith) keyword. Die erforderlichen Eingaben findest Du in der README-Datei der Aktion. ```yaml runs: diff --git a/translations/de-DE/content/actions/creating-actions/publishing-actions-in-github-marketplace.md b/translations/de-DE/content/actions/creating-actions/publishing-actions-in-github-marketplace.md index bc05f9c5a4..94fdc1198d 100644 --- a/translations/de-DE/content/actions/creating-actions/publishing-actions-in-github-marketplace.md +++ b/translations/de-DE/content/actions/creating-actions/publishing-actions-in-github-marketplace.md @@ -12,8 +12,6 @@ type: how_to shortTitle: Publish in GitHub Marketplace --- -{% data reusables.actions.ae-beta %} - You must accept the terms of service to publish actions in {% data variables.product.prodname_marketplace %}. ## Informationen zum Veröffentlichen von Aktionen diff --git a/translations/de-DE/content/actions/creating-actions/setting-exit-codes-for-actions.md b/translations/de-DE/content/actions/creating-actions/setting-exit-codes-for-actions.md index d4fe9f665d..9d7b5bbabc 100644 --- a/translations/de-DE/content/actions/creating-actions/setting-exit-codes-for-actions.md +++ b/translations/de-DE/content/actions/creating-actions/setting-exit-codes-for-actions.md @@ -14,7 +14,6 @@ type: how_to {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Informationen zu Exitcodes @@ -37,11 +36,11 @@ try { } ``` -Weitere Informationen finden Sie unter „[Eine JavaScript-Aktion erstellen](/articles/creating-a-javascript-action)“. +Weitere Informationen findest Du unter „[Eine JavaScript-Aktion erstellen](/articles/creating-a-javascript-action)“. ## Fehler-Exit-Code in einer Docker-Container-Aktion festlegen -Wenn Sie eine Docker-Container-Aktion erstellen, können Sie einen Fehler-Exit-Code im `entrypoint.sh`-Skript festlegen. Ein Beispiel: +Wenn Du eine Docker-Container-Aktion erstellst, kannst Du einen Fehler-Exit-Code im Skript `entrypoint.sh` festlegen. Ein Beispiel: ``` if ; then diff --git a/translations/de-DE/content/actions/deployment/about-continuous-deployment.md b/translations/de-DE/content/actions/deployment/about-continuous-deployment.md new file mode 100644 index 0000000000..4ce09833ca --- /dev/null +++ b/translations/de-DE/content/actions/deployment/about-continuous-deployment.md @@ -0,0 +1,41 @@ +--- +title: About continuous deployment +intro: 'You can create custom continuous deployment (CD) workflows directly in your {% data variables.product.prodname_dotcom %} repository with {% data variables.product.prodname_actions %}.' +product: '{% data reusables.gated-features.actions %}' +versions: + fpt: '*' + ghes: '*' + ghae: '*' +type: overview +topics: + - CD +shortTitle: Continuous deployment +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +## About continuous deployment + +_Continuous deployment_ (CD) is the practice of using automation to publish and deploy software updates. As part of the typical CD process, the code is automatically built and tested before deployment. + +Continuous deployment is often coupled with continuous integration. For more information about continuous integration, see "[About continuous integration](/actions/guides/about-continuous-integration)". + +## About continuous deployment using {% data variables.product.prodname_actions %} + +You can set up a {% data variables.product.prodname_actions %} workflow to deploy your software product. To verify that your product works as expected, your workflow can build the code in your repository and run your tests before deploying. + +You can configure your CD workflow to run when a {% data variables.product.product_name %} event occurs (for example, when new code is pushed to the default branch of your repository), on a set schedule, manually, or when an external event occurs using the repository dispatch webhook. For more information about when your workflow can run, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)." + +{% data variables.product.prodname_actions %} provides features that give you more control over deployments. For example, you can use environments to require approval for a job to proceed, restrict which branches can trigger a workflow, or limit access to secrets. You can use concurrency to limit your CD pipeline to a maximum of one in-progress deployment and one pending deployment. For more information about these features, see "[Deploying with GitHub Actions](/actions/deployment/deploying-with-github-actions)" and "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." + +## Workflow templates and third party actions + +{% data reusables.actions.cd-templates-actions %} + +## Weiterführende Informationen + +- [Deploying with GitHub Actions](/actions/deployment/deploying-with-github-actions) +- [Using environments for deployment](/actions/deployment/using-environments-for-deployment){% ifversion fpt %} +- "[ Abrechnung für {% data variables.product.prodname_actions %} verwalten](/billing/managing-billing-for-github-actions)" +{% endif %} diff --git a/translations/de-DE/content/actions/deployment/deploying-to-amazon-elastic-container-service.md b/translations/de-DE/content/actions/deployment/deploying-to-amazon-elastic-container-service.md index 36b871831e..d83427ca3b 100644 --- a/translations/de-DE/content/actions/deployment/deploying-to-amazon-elastic-container-service.md +++ b/translations/de-DE/content/actions/deployment/deploying-to-amazon-elastic-container-service.md @@ -18,11 +18,10 @@ shortTitle: Deploy to Amazon ECS {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Einführung -This guide explains how to use {% data variables.product.prodname_actions %} to build a containerized application, push it to [Amazon Elastic Container Registry (ECR)](https://aws.amazon.com/ecr/), and deploy it to [Amazon Elastic Container Service (ECS)](https://aws.amazon.com/ecs/). +This guide explains how to use {% data variables.product.prodname_actions %} to build a containerized application, push it to [Amazon Elastic Container Registry (ECR)](https://aws.amazon.com/ecr/), and deploy it to [Amazon Elastic Container Service (ECS)](https://aws.amazon.com/ecs/) when a release is created. On every new release in your {% data variables.product.company_short %} repository, the {% data variables.product.prodname_actions %} workflow builds and pushes a new container image to Amazon ECR, and then deploys a new task definition to Amazon ECS. @@ -66,6 +65,8 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you See the documentation for each action used below for the recommended IAM policies for the IAM user, and methods for handling the access key credentials. +5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %} + ## Creating the workflow Once you've completed the prerequisites, you can proceed with creating the workflow. @@ -74,6 +75,8 @@ The following example workflow demonstrates how to build a container image and p Ensure that you provide your own values for all the variables in the `env` key of the workflow. +{% data reusables.actions.delete-env-key %} + ```yaml{:copy} {% data reusables.actions.actions-not-certified-by-github-comment %} @@ -93,17 +96,11 @@ env: CONTAINER_NAME: MY_CONTAINER_NAME # set this to the name of the container in the # containerDefinitions section of your task definition -defaults: - run: - shell: bash - jobs: deploy: name: Deploy - runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae-next %} - permissions: - packages: write - contents: read{% endif %} + runs-on: ubuntu-latest + environment: production {% raw %}steps: - name: Checkout @@ -150,9 +147,10 @@ jobs: wait-for-service-stability: true{% endraw %} ``` - ## Additional resources +For the original starter workflow, see [`aws.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/aws.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository. + For more information on the services used in these examples, see the following documentation: * "[Security best practices in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html)" in the Amazon AWS documentation. diff --git a/translations/de-DE/content/actions/deployment/deploying-to-azure-app-service.md b/translations/de-DE/content/actions/deployment/deploying-to-azure-app-service.md index abd77f40f3..0e59d83ef2 100644 --- a/translations/de-DE/content/actions/deployment/deploying-to-azure-app-service.md +++ b/translations/de-DE/content/actions/deployment/deploying-to-azure-app-service.md @@ -18,7 +18,6 @@ shortTitle: Deploy to Azure App Service {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Einführung @@ -68,13 +67,19 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you In your {% data variables.product.prodname_dotcom %} repository, create a secret named `AZURE_WEBAPP_PUBLISH_PROFILE` that contains the contents of the publish profile. For more information on creating secrets, see "[Encrypted secrets](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)." +4. For Linux apps, add an app setting called `WEBSITE_WEBDEPLOY_USE_SCM` and set it to true in your app. For more information, see "[Configure apps in the portal](https://docs.microsoft.com/en-us/azure/app-service/configure-common#configure-app-settings)" in the Azure documentation. + +5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %} + ## Creating the workflow Once you've completed the prerequisites, you can proceed with creating the workflow. -The following example workflow demonstrates how to build, test, and deploy the Node.js project to Azure App Service. +The following example workflow demonstrates how to build, test, and deploy the Node.js project to Azure App Service when a release is created. -Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created. +Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created. You can also change `AZURE_WEBAPP_PACKAGE_PATH` if the path to your project is not the repository root and `NODE_VERSION` if you want to use a node version other than `10.x`. + +{% data reusables.actions.delete-env-key %} ```yaml{:copy} {% data reusables.actions.actions-not-certified-by-github-comment %} @@ -92,6 +97,8 @@ jobs: build-and-deploy: name: Build and Deploy runs-on: ubuntu-latest + environment: production + steps: - uses: actions/checkout@v2 @@ -122,4 +129,5 @@ The following resources may also be useful: * For the original starter workflow, see [`azure.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository. * 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/en-us/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). diff --git a/translations/de-DE/content/actions/deployment/deploying-to-google-kubernetes-engine.md b/translations/de-DE/content/actions/deployment/deploying-to-google-kubernetes-engine.md index d3d0067362..f4dc8f7a05 100644 --- a/translations/de-DE/content/actions/deployment/deploying-to-google-kubernetes-engine.md +++ b/translations/de-DE/content/actions/deployment/deploying-to-google-kubernetes-engine.md @@ -13,16 +13,15 @@ topics: - CD - Containers - Google Kubernetes Engine -shortTitle: Deploy to Kubernetes (GKE) +shortTitle: Deploy to Google Kubernetes Engine --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Einführung -This guide explains how to use {% data variables.product.prodname_actions %} to build a containerized application, push it to Google Container Registry (GCR), and deploy it to Google Kubernetes Engine (GKE). +This guide explains how to use {% data variables.product.prodname_actions %} to build a containerized application, push it to Google Container Registry (GCR), and deploy it to Google Kubernetes Engine (GKE) when a release is created. GKE is a managed Kubernetes cluster service from Google Cloud that can host your containerized workloads in the cloud or in your own datacenter. For more information, see [Google Kubernetes Engine](https://cloud.google.com/kubernetes-engine). @@ -61,7 +60,7 @@ $ gcloud services enable \ ### Configuring a service account and storing its credentials -This procedure demonstrates how to create the service account for your GKE integration. It explains how to create the account, add roles to it, retrieve its keys, and store them as a base64-encoded [encrypted repository secret](/actions/reference/encrypted-secrets) named `GKE_SA_KEY`. +This procedure demonstrates how to create the service account for your GKE integration. It explains how to create the account, add roles to it, retrieve its keys, and store them as a base64-encoded encrypted repository secret named `GKE_SA_KEY`. 1. Create a new service account: {% raw %} @@ -97,16 +96,29 @@ This procedure demonstrates how to create the service account for your GKE integ $ export GKE_SA_KEY=$(cat key.json | base64) ``` {% endraw %} + For more information about how to store a secret, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)." + +### Storing your project name + +Store the name of your project as a secret named `GKE_PROJECT`. For more information about how to store a secret, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)." ### (Optional) Configuring kustomize Kustomize is an optional tool used for managing YAML specs. After creating a _kustomization_ file, the workflow below can be used to dynamically set fields of the image and pipe in the result to `kubectl`. For more information, see [kustomize usage](https://github.com/kubernetes-sigs/kustomize#usage). +### (Optional) Configure a deployment environment + +{% data reusables.actions.about-environments %} + ## Creating the workflow Once you've completed the prerequisites, you can proceed with creating the workflow. The following example workflow demonstrates how to build a container image and push it to GCR. It then uses the Kubernetes tools (such as `kubectl` and `kustomize`) to pull the image into the cluster deployment. +Under the `env` key, change the value of `GKE_CLUSTER` to the name of your cluster, `GKE_ZONE` to your cluster zone, `DEPLOYMENT_NAME` to the name of your deployment, and `IMAGE` to the name of your image. + +{% data reusables.actions.delete-env-key %} + ```yaml{:copy} {% data reusables.actions.actions-not-certified-by-github-comment %} @@ -127,8 +139,9 @@ jobs: setup-build-publish-deploy: name: Setup, Build, Publish, and Deploy runs-on: ubuntu-latest - steps: + environment: production + steps: - name: Checkout uses: actions/checkout@v2 @@ -138,7 +151,8 @@ jobs: service_account_key: {% raw %}${{ secrets.GKE_SA_KEY }}{% endraw %} project_id: {% raw %}${{ secrets.GKE_PROJECT }}{% endraw %} - # Configure docker to use the gcloud command-line tool as a credential helper + # Configure Docker to use the gcloud command-line tool as a credential + # helper for authentication - run: |- gcloud --quiet auth configure-docker @@ -166,7 +180,7 @@ jobs: # Set up kustomize - name: Set up Kustomize run: |- - curl --location https://github.com/kubernetes-sigs/kustomize/releases/download/kustomize%2Fv4.2.0/kustomize_v4.2.0_linux_amd64.tar.gz | tar xz + curl -sfLo kustomize https://github.com/kubernetes-sigs/kustomize/releases/download/v3.1.0/kustomize_3.1.0_linux_amd64 chmod u+x ./kustomize # Deploy the Docker image to the GKE cluster diff --git a/translations/de-DE/content/actions/deployment/deploying-with-github-actions.md b/translations/de-DE/content/actions/deployment/deploying-with-github-actions.md new file mode 100644 index 0000000000..b182daf18b --- /dev/null +++ b/translations/de-DE/content/actions/deployment/deploying-with-github-actions.md @@ -0,0 +1,173 @@ +--- +title: Deploying with GitHub Actions +intro: Learn how to control deployments with features like environments and concurrency. +product: '{% data reusables.gated-features.actions %}' +versions: + fpt: '*' + ghes: '>=3.1' + ghae: '*' +type: overview +topics: + - CD +shortTitle: Deploy with GitHub Actions +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +## Einführung + +{% data variables.product.prodname_actions %} offers features that let you control deployments. Sie können: + +- 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)." + +## Vorrausetzungen + +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)." + +## Triggering your deployment + +You can use a variety of events to trigger your deployment workflow. Some of the most common are: `pull_request`, `push`, `release`, and `workflow_dispatch`. + +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. +- A release is created. +- Someone manually triggers it. + +```yaml +on: + push: + branches: + - main + pull_request: + branches: + - main + release: + types: + - created + workflow_dispatch: +``` + +Weitere Informationen findest Du unter "[Ereignisse, die Workflows auslösen](/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. + +{% 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. + +```yaml +name: Deployment + +concurrency: production + +on: + push: + branches: + - main + +jobs: + deployment: + runs-on: ubuntu-latest + environment: production + steps: + - name: deploy + # ...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`. + +```yaml +name: Deployment + +on: + push: + branches: + - main + +jobs: + deployment: + runs-on: ubuntu-latest + environment: production + concurrency: production + steps: + - name: deploy + # ...deployment-specific steps +``` + +You can also use `cancel-in-progress` to cancel any currently running job or workflow in the same concurrency group. + +```yaml +name: Deployment + +concurrency: + group: production + cancel-in-progress: true + +on: + push: + branches: + - main + +jobs: + deployment: + runs-on: ubuntu-latest + environment: production + steps: + - name: deploy + # ...deployment-specific steps +``` + +## 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)." + +## 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)." + +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)." + +## Tracking deployments through apps + +{% ifversion fpt %} +If your {% data variables.product.product_name %} personal account or organization 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)." +{% 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)." + +{% ifversion fpt or ghes %} + +## Die Wahl eines Läufers + +You can run your deployment workflow on {% data variables.product.product_name %}-hosted runners or on self-hosted runners. Traffic from {% data variables.product.product_name %}-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.product_name %}-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)." + +{% 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 %} + +For more information, see "[Adding a workflow status badge](/actions/managing-workflow-runs/adding-a-workflow-status-badge)." + +## Nächste Schritte: + +This article demonstrated features of {% data variables.product.prodname_actions %} that you can add to your deployment workflows. + +{% data reusables.actions.cd-templates-actions %} diff --git a/translations/de-DE/content/actions/deployment/index.md b/translations/de-DE/content/actions/deployment/index.md index 2ae385cc62..0fbfa9c440 100644 --- a/translations/de-DE/content/actions/deployment/index.md +++ b/translations/de-DE/content/actions/deployment/index.md @@ -7,10 +7,13 @@ versions: ghes: '*' ghae: '*' children: + - /about-continuous-deployment + - /deploying-with-github-actions + - /using-environments-for-deployment + - /viewing-deployment-history - /deploying-to-amazon-elastic-container-service - /deploying-to-azure-app-service - /deploying-to-google-kubernetes-engine - /installing-an-apple-certificate-on-macos-runners-for-xcode-development - - /environments --- diff --git a/translations/de-DE/content/actions/deployment/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md b/translations/de-DE/content/actions/deployment/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md index a8d828a50f..5d339450a4 100644 --- a/translations/de-DE/content/actions/deployment/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md +++ b/translations/de-DE/content/actions/deployment/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md @@ -17,7 +17,6 @@ shortTitle: Sign Xcode applications {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Einführung diff --git a/translations/de-DE/content/actions/deployment/using-environments-for-deployment.md b/translations/de-DE/content/actions/deployment/using-environments-for-deployment.md new file mode 100644 index 0000000000..ebb8ca57fc --- /dev/null +++ b/translations/de-DE/content/actions/deployment/using-environments-for-deployment.md @@ -0,0 +1,126 @@ +--- +title: Using environments for deployment +shortTitle: Use environments for deployment +intro: You can configure environments with protection rules and secrets. A workflow job that references an environment must follow any protection rules for the environment before running or accessing the environment's secrets. +product: '{% data reusables.gated-features.environments %}' +miniTocMaxHeadingLevel: 3 +redirect_from: + - /actions/reference/environments + - /actions/deployment/environments +versions: + fpt: '*' + ghes: '>=3.1' + ghae: '*' +--- + + +## About environments + +Environments are used to describe a general deployment target like `production`, `staging`, or `development`. 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)." + +You can configure environments with protection rules and secrets. When a workflow job references an environment, the job won't start until all of the environment's protection rules pass. A job also cannot access secrets that are defined in an environment until all the environment protection rules pass. + +{% ifversion fpt %} +{% note %} + +**Note:** If you don't use {% data variables.product.prodname_ghe_cloud %} and convert a repository from public to private, any configured protection rules or environment secrets will be ignored, and you will not be able to configure any environments. If you convert your repository back to public, you will have access to any previously configured protection rules and environment secrets. {% data reusables.enterprise.link-to-ghec-trial %} + +{% endnote %} +{% endif %} + +## Environment protection rules + +Environment protection rules require specific conditions to pass before a job referencing the environment can proceed. {% ifversion fpt or ghae-next or ghes > 3.1 %}You can use environment protection rules to require a manual approval, delay a job, or restrict the environment to certain branches.{% else %}You can use environment protection rules to require a manual approval or delay a job.{% endif %} + +### Required reviewers + +Use required reviewers to require a specific person or team to approve workflow jobs that reference the environment. You can list up to six users or teams as reviewers. The reviewers must have at least read access to the repository. Only one of the required reviewers needs to approve the job for it to proceed. + +For more information on reviewing jobs that reference an environment with required reviewers, see "[Reviewing deployments](/actions/managing-workflow-runs/reviewing-deployments)." + +### Wait timer + +Use a wait timer to delay a job for a specific amount of time after the job is initially triggered. The time (in minutes) must be an integer between 0 and 43,200 (30 days). + +{% ifversion fpt or ghae-next or ghes > 3.1 %} +### Deployment branches + +Use deployment branches to restrict which branches can deploy to the environment. Below are the options for deployment branches for an environment: + +* **All branches**: All branches in the repository can deploy to the environment. +* **Protected branches**: Only branches with branch protection rules enabled can deploy to the environment. If no branch protection rules are defined for any branch in the repository, then all branches can deploy. For more information about branch protection rules, see "[About protected branches](/github/administering-a-repository/about-protected-branches)." +* **Selected branches**: Only branches that match your specified name patterns can deploy to the environment. + + For example, if you specify `releases/*` as a deployment branch rule, only branches whose name begins with `releases/` can deploy to the environment. (Wildcard characters will not match `/`. To match branches that begin with `release/` and contain an additional single slash, use `release/*/*`.) If you add `main` as a deployment branch rule, a branch named `main` can also deploy to the environment. For more information about syntax options for deployment branches, see the [Ruby File.fnmatch documentation](https://ruby-doc.org/core-2.5.1/File.html#method-c-fnmatch). +{% endif %} +## Environment secrets + +Secrets stored in an environment are only available to workflow jobs that reference the environment. If the environment requires approval, a job cannot access environment secrets until one of the required reviewers approves it. For more information about secrets, see "[Encrypted secrets](/actions/reference/encrypted-secrets)." + +{% note %} + +**Note:** Workflows that run on self-hosted runners are not run in an isolated container, even if they use environments. Environment secrets should be treated with the same level of security as repository and organization secrets. For more information, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#hardening-for-self-hosted-runners)." + +{% endnote %} + +## Creating an environment + +{% data reusables.github-actions.permissions-statement-environment %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.github-actions.sidebar-environment %} +{% data reusables.github-actions.new-environment %} +{% data reusables.github-actions.name-environment %} +1. Optionally, specify people or teams that must approve workflow jobs that use this environment. + 1. Select **Required reviewers**. + 1. Enter up to 6 people or teams. Only one of the required reviewers needs to approve the job for it to proceed. + 1. Click **Save protection rules**. +2. Optionally, specify the amount of time to wait before allowing workflow jobs that use this environment to proceed. + 1. Select **Wait timer**. + 1. Enter the number of minutes to wait. + 1. Click **Save protection rules**. +3. Optionally, specify what branches can deploy to this environment. For more information about the possible values, see "[Deployment branches](#deployment-branches)." + 1. Select the desired option in the **Deployment branches** dropdown. + 1. If you chose **Selected branches**, enter the branch name patterns that you want to allow. +4. Optionally, add environment secrets. These secrets are only available to workflow jobs that use the environment. Additionally, workflow jobs that use this environment can only access these secrets after any configured rules (for example, required reviewers) pass. For more information about secrets, see "[Encrypted secrets](/actions/reference/encrypted-secrets)." + 1. Under **Environment secrets**, click **Add Secret**. + 1. Enter the secret name. + 1. Enter the secret value. + 1. Klicken Sie auf **Add secret** (Geheimnis hinzufügen). + +{% ifversion fpt or ghae-next or ghes > 3.1 %}You can also create and configure environments through the REST API. For more information, see "[Environments](/rest/reference/repos#environments)" and "[Secrets](/rest/reference/actions#secrets)."{% endif %} + +Running a workflow that references an environment that does not exist will create an environment with the referenced name. The newly created environment will not have any protection rules or secrets configured. Anyone that can edit workflows in the repository can create environments via a workflow file, but only repository admins can configure the environment. + +## Using an environment + +Each job in a workflow can reference a single environment. Any protection rules configured for the environment must pass before a job referencing the environment is sent to a runner. The job can access the environment's secrets only after the job is sent to a runner. + +When a workflow references an environment, the environment will appear in the repository's deployments. For more information about viewing current and previous deployments, see "[Viewing deployment history](/developers/overview/viewing-deployment-history)." + +{% data reusables.actions.environment-example %} + +## Deleting an environment + +{% data reusables.github-actions.permissions-statement-environment %} + +Deleting an environment will delete all secrets and protection rules associated with the environment. Any jobs currently waiting because of protection rules from the deleted environment will automatically fail. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.github-actions.sidebar-environment %} +1. Next to the environment that you want to delete, click {% octicon "trash" aria-label="The trash icon" %}. +2. Click **I understand, delete this environment**. + +{% ifversion fpt or ghae-next or ghes > 3.1 %}You can also delete environments through the REST API. For more information, see "[Environments](/rest/reference/repos#environments)."{% endif %} + +## How environments relate to deployments + +{% data reusables.actions.environment-deployment-event %} + +You can access these objects through the REST API or GraphQL API. You can also subscribe to these webhook events. For more information, see "[Repositories](/rest/reference/repos#deployments)" (REST API), "[Objects](/graphql/reference/objects#deployment)" (GraphQL API), or "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#deployment)." + +## Nächste Schritte: + +{% data variables.product.prodname_actions %} provides several features for managing your deployments. For more information, see "[Deploying with GitHub Actions](/actions/deployment/deploying-with-github-actions)." diff --git a/translations/de-DE/content/actions/deployment/viewing-deployment-history.md b/translations/de-DE/content/actions/deployment/viewing-deployment-history.md new file mode 100644 index 0000000000..16f184214e --- /dev/null +++ b/translations/de-DE/content/actions/deployment/viewing-deployment-history.md @@ -0,0 +1,27 @@ +--- +title: Viewing deployment history +intro: View current and previous deployments for your repository. +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - API +shortTitle: View deployment history +redirect_from: + - /developers/overview/viewing-deployment-history +--- + + +You can deliver deployments through {% ifversion fpt or ghae or ghes > 3.0 %}{% data variables.product.prodname_actions %} and environments or with {% endif %}the REST API and third party apps. {% ifversion fpt or ghae ghes > 3.0 %}For more information about using environments to deploy with {% data variables.product.prodname_actions %}, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." {% endif %}For more information about deployments with the REST API, see "[Repositories](/rest/reference/repos#deployments)." + +To view current and past deployments, click **Environments** on the home page of your repository. +{% ifversion ghae or ghes < 3.0 %} +![Environments](/assets/images/enterprise/2.22/environments-sidebar.png){% else %} +![Environments](/assets/images/environments-sidebar.png){% endif %} + +The deployments page displays the last active deployment of each environment for your repository. If the deployment includes an environment URL, a **View deployment** button that links to the URL is shown next to the deployment. + +The activity log shows the deployment history for your environments. By default, only the most recent deployment for an environment has an `Active` status; all previously active deployments have an `Inactive` status. For more information on automatic inactivation of deployments, see "[Inactive deployments](/rest/reference/repos#inactive-deployments)." + +You can also use the REST API to get information about deployments. For more information, see "[Repositories](/rest/reference/repos#deployments)." diff --git a/translations/de-DE/content/actions/hosting-your-own-runners/about-self-hosted-runners.md b/translations/de-DE/content/actions/hosting-your-own-runners/about-self-hosted-runners.md index 602acd4f02..c8621efac5 100644 --- a/translations/de-DE/content/actions/hosting-your-own-runners/about-self-hosted-runners.md +++ b/translations/de-DE/content/actions/hosting-your-own-runners/about-self-hosted-runners.md @@ -14,7 +14,6 @@ type: overview {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Informationen zu selbst-gehosteten Runnern @@ -25,7 +24,7 @@ You can add self-hosted runners at various levels in the management hierarchy: - Organization-level runners can process jobs for multiple repositories in an organization. - Enterprise-level runners can be assigned to multiple organizations in an enterprise account. -Your runner machine connects to {% data variables.product.prodname_dotcom %} using the {% data variables.product.prodname_actions %} self-hosted runner application. {% data reusables.github-actions.runner-app-open-source %} When a new version is released, the runner application automatically updates itself when a job is assigned to the runner, or within a week of release if the runner hasn't been assigned any jobs. +Your runner machine connects to {% data variables.product.product_name %} using the {% data variables.product.prodname_actions %} self-hosted runner application. {% data reusables.github-actions.runner-app-open-source %} When a new version is released, the runner application automatically updates itself when a job is assigned to the runner, or within a week of release if the runner hasn't been assigned any jobs. {% data reusables.github-actions.self-hosted-runner-auto-removal %} @@ -172,7 +171,9 @@ You can also use self-hosted runners with a proxy server. For more information, ## Sicherheit von selbst-gehosteten Runner mit öffentlichen Repositories +{% ifversion not ghae %} {% data reusables.github-actions.self-hosted-runner-security %} +{% endif %} This is not an issue with {% data variables.product.prodname_dotcom %}-hosted runners because each {% data variables.product.prodname_dotcom %}-hosted runner is always a clean isolated virtual machine, and it is destroyed at the end of the job execution. diff --git a/translations/de-DE/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md b/translations/de-DE/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md index da3ff52311..2667c633c0 100644 --- a/translations/de-DE/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md +++ b/translations/de-DE/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md @@ -15,7 +15,6 @@ shortTitle: Add self-hosted runners {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} Du kannst einen selbst-gehosteten Runner zu {{ site.data.variables.product.prodname_actions }} hinzufügen. @@ -23,6 +22,7 @@ If you are an organization or enterprise administrator, you might want to add yo For information on supported operating systems for self-hosted runners, or using self-hosted runners with a proxy server, see "[About self-hosted runners](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)." +{% ifversion not ghae %} {% warning %} **Warning:** {% data reusables.github-actions.self-hosted-runner-security %} @@ -30,6 +30,7 @@ For information on supported operating systems for self-hosted runners, or using Weitere Informationen findest Du unter „[Informationen zu selbst-gehosteten Runnern](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)“. {% endwarning %} +{% endif %} ## Einen selbst-gehosteten Runner zu einem Repository hinzufügen @@ -48,7 +49,7 @@ Du kannst selbst-gehostete Runner zu einem einzigen Repository hinzufügen. To a {% data reusables.repositories.sidebar-settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} 1. Under -{% ifversion fpt %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**. +{% ifversion fpt or ghes > 3.1 or ghae %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**. {% data reusables.github-actions.self-hosted-runner-configure %} {% endif %} {% data reusables.github-actions.self-hosted-runner-check-installation-success %} @@ -70,7 +71,7 @@ Du kannst selbst-gehostete Runner auf Organisationsebene hinzufügen, wo sie ver {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} 1. Under -{% ifversion fpt %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**. +{% ifversion fpt or ghes > 3.1 or ghae %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**. {% data reusables.github-actions.self-hosted-runner-configure %} {% endif %} diff --git a/translations/de-DE/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md b/translations/de-DE/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md index e93ccbc18f..aacade1be3 100644 --- a/translations/de-DE/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md +++ b/translations/de-DE/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md @@ -10,7 +10,6 @@ type: overview {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About autoscaling diff --git a/translations/de-DE/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md b/translations/de-DE/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md index ee2eacad05..7181940ccd 100644 --- a/translations/de-DE/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md +++ b/translations/de-DE/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md @@ -15,7 +15,6 @@ shortTitle: Run runner app on startup {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% capture service_first_step %}1. Beende die Anwendung für selbst-gehostete Runner, falls sie gerade läuft.{% endcapture %} {% capture service_non_windows_intro_shell %}Öffne auf der Runner-Maschine eine Shell in dem Verzeichnis, in dem Du die Anwendung für selbst-gehostete Runner installiert hast. Verwende die folgenden Befehle, um den Dienst für selbst-gehosteten Runner zu installieren und zu verwalten.{% endcapture %} diff --git a/translations/de-DE/content/actions/hosting-your-own-runners/index.md b/translations/de-DE/content/actions/hosting-your-own-runners/index.md index 739a98afc8..506887803d 100644 --- a/translations/de-DE/content/actions/hosting-your-own-runners/index.md +++ b/translations/de-DE/content/actions/hosting-your-own-runners/index.md @@ -24,4 +24,3 @@ children: {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} diff --git a/translations/de-DE/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md b/translations/de-DE/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md index 68c2c556be..ebad873ac3 100644 --- a/translations/de-DE/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md +++ b/translations/de-DE/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md @@ -14,7 +14,6 @@ shortTitle: Manage runner groups {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About self-hosted runner groups @@ -173,14 +172,13 @@ Could not find any self-hosted runner group named "rg-runnergroup". ## Moving a self-hosted runner to a group If you don't specify a runner group during the registration process, your new self-hosted runners are automatically assigned to the default group, and can then be moved to another group. -{% ifversion fpt %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} 1. In the "Runners" list, click the runner that you want to configure. 1. Select the Runner group dropdown menu. 1. In "Move runner to group", choose a destination group for the runner. -{% endif %} -{% ifversion ghae or ghes %} -1. In the {% ifversion fpt %}"Runners"{% else %}"Self-hosted runners"{% endif %} section of the settings page, locate the current group of the runner you want to move and expand the list of group members. ![View runner group members](/assets/images/help/settings/actions-org-runner-group-members.png) +{% else %} +1. In the "Self-hosted runners" section of the settings page, locate the current group of the runner you want to move and expand the list of group members. ![View runner group members](/assets/images/help/settings/actions-org-runner-group-members.png) 1. Select the checkbox next to the self-hosted runner, and then click **Move to group** to see the available destinations. ![Runner group member move](/assets/images/help/settings/actions-org-runner-group-member-move.png) 1. To move the runner, click on the destination group. ![Runner group member move](/assets/images/help/settings/actions-org-runner-group-member-move-destination.png) {% endif %} @@ -188,14 +186,13 @@ If you don't specify a runner group during the registration process, your new se Self-hosted runners are automatically returned to the default group when their group is removed. -{% ifversion fpt %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} {% data reusables.github-actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %} 1. In the list of groups, to the right of the group you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. 1. To remove the group, click **Remove group**. 1. Review the confirmation prompts, and click **Remove this runner group**. -{% endif %} -{% ifversion ghae or ghes %} -1. In the {% ifversion fpt %}"Runners"{% else %}"Self-hosted runners"{% endif %} section of the settings page, locate the group you want to delete, and click the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} button. ![View runner group settings](/assets/images/help/settings/actions-org-runner-group-kebab.png) +{% else %} +1. In the "Self-hosted runners" section of the settings page, locate the group you want to delete, and click the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} button. ![View runner group settings](/assets/images/help/settings/actions-org-runner-group-kebab.png) 1. To remove the group, click **Remove group**. ![View runner group settings](/assets/images/help/settings/actions-org-runner-group-remove.png) diff --git a/translations/de-DE/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md b/translations/de-DE/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md index 2b62660153..23d3c867cf 100644 --- a/translations/de-DE/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md +++ b/translations/de-DE/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md @@ -17,7 +17,6 @@ shortTitle: Monitor & troubleshoot {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Den Status eines selbst-gehosteten Runners mittels {% data variables.product.prodname_dotcom %} überprüfen @@ -25,7 +24,7 @@ shortTitle: Monitor & troubleshoot {% data reusables.github-actions.self-hosted-runner-navigate-repo-and-org %} {% data reusables.github-actions.settings-sidebar-actions-runners %} -1. Under {% ifversion fpt %}"Runners"{% else %}"Self-hosted runners"{% endif %}, you can view a list of registered runners, including the runner's name, labels, and status. +1. Under {% ifversion fpt or ghes > 3.1 or ghae-next %}"Runners"{% else %}"Self-hosted runners"{% endif %}, you can view a list of registered runners, including the runner's name, labels, and status. Der Status kann einer der folgenden sein: diff --git a/translations/de-DE/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md b/translations/de-DE/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md index b5c80f1603..18c8d6d07b 100644 --- a/translations/de-DE/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md +++ b/translations/de-DE/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md @@ -15,7 +15,6 @@ shortTitle: Remove self-hosted runners {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Einen Runner aus einem Repository entfernen @@ -57,15 +56,14 @@ To remove a self-hosted runner from a user repository you must be the repository Um einen selbst-gehosteten Runner aus einer Organisation zu entfernen, musst Du ein Organisationsinhaber sein. We recommend that you also have access to the self-hosted runner machine. {% data reusables.github-actions.self-hosted-runner-reusing %} -{% ifversion fpt %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions %} {% data reusables.github-actions.settings-sidebar-actions-runners-updated %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %} -{% endif %} -{% ifversion ghae or ghes %} +{% else %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} @@ -90,10 +88,9 @@ To remove a self-hosted runner from an enterprise account, you must be an enterp {% data reusables.enterprise-accounts.actions-runners-tab %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes %} To remove a self-hosted runner at the enterprise level of -{% data variables.product.product_location %}, you must be a site administrator. We recommend that you also have access to the self-hosted runner machine. +{% data variables.product.product_location %}, you must be an enterprise owner. We recommend that you also have access to the self-hosted runner machine. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} diff --git a/translations/de-DE/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md b/translations/de-DE/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md index 5455192f31..e1a32d1d37 100644 --- a/translations/de-DE/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md +++ b/translations/de-DE/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md @@ -14,7 +14,6 @@ shortTitle: Proxy servers {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Einen Proxyserver mithilfe von Umgebungsvariablen konfigurieren diff --git a/translations/de-DE/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md b/translations/de-DE/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md index e1c9276fbb..32d9c2beb9 100644 --- a/translations/de-DE/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md +++ b/translations/de-DE/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md @@ -12,7 +12,6 @@ shortTitle: Label runners {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} Informationen zum Einsatz von Labels zur Weiterleitung von Jobs an bestimmte Typen von selbst-gehosteten Runnern findest Du unter „[Nutze selbstgehostete Läufer in einem Workflow](/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow)“. diff --git a/translations/de-DE/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md b/translations/de-DE/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md index 6ec7761890..48719f6203 100644 --- a/translations/de-DE/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md +++ b/translations/de-DE/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md @@ -15,7 +15,6 @@ shortTitle: Use runners in a workflow {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} Informationen zum Erstellen benutzerdefinierter und Standard-Labels findest Du unter „[Labels mit selbst-gehosteten Runnern verwenden](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)“. diff --git a/translations/de-DE/content/actions/index.md b/translations/de-DE/content/actions/index.md index 9e59615816..9d9b8ad058 100644 --- a/translations/de-DE/content/actions/index.md +++ b/translations/de-DE/content/actions/index.md @@ -9,6 +9,7 @@ featuredLinks: guides: - /actions/learn-github-actions - /actions/guides/about-continuous-integration + - /actions/deployment/deploying-with-github-actions - /actions/guides/about-packaging-with-github-actions - /actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting guideCards: diff --git a/translations/de-DE/content/actions/learn-github-actions/contexts.md b/translations/de-DE/content/actions/learn-github-actions/contexts.md index b8b6dc3972..5d48b2cb30 100644 --- a/translations/de-DE/content/actions/learn-github-actions/contexts.md +++ b/translations/de-DE/content/actions/learn-github-actions/contexts.md @@ -18,7 +18,6 @@ miniTocMaxHeadingLevel: 3 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About contexts @@ -61,27 +60,29 @@ Der `github`-Kontext enthält Informationen zum Workflow-Lauf und zu dem Ereigni {% data reusables.github-actions.github-context-warning %} {% data reusables.github-actions.context-injection-warning %} -| Name der Eigenschaft | Typ | Beschreibung | -| ------------------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `github` | `Objekt` | Der Top-Level-Kontext, der bei jedem Job oder Schritt im Workflow verfügbar ist. | -| `github.action` | `string` | Der Name der aktuell laufenden Aktion. {% data variables.product.prodname_dotcom %} entfernt Sonderzeichen oder verwendet den Namen `run` wenn der aktuelle Schritt ein Skript ausführt. Wenn Du dieselbe Aktion mehr als einmal im selben Job verwendest, enthält der Name ein Suffix mit der Sequenznummer. Zum Beispiel wird das erste Skript, das Du ausführst, den Namen `run1`haben, und das zweite Skript heißt `run2`. Ebenso wird die zweite Anrufung von `actions/checkout` `actionscheckout2` sein. | -| `github.action_path` | `string` | The path where your action is located. You can use this path to easily access files located in the same repository as your action. This attribute is only supported in composite actions. | -| `github.actor` | `string` | Der Anmeldename des Benutzers, der den Workflow-Lauf initiiert hat | -| `github.base_ref` | `string` | Das `base_ref` oder der Ziel-Branch des Pull Requests in einem Workflow-Lauf. This property is only available when the event that triggers a workflow run is either `pull_request` or `pull_request_target`. | -| `github.event` | `Objekt` | Die vollständige Nutzlast des Ereignis-Webhooks. Weitere Informationen findest Du unter „[Ereignisse, die Workflows auslösen](/articles/events-that-trigger-workflows)“. You can access individual properties of the event using this context. | -| `github.event_name` | `string` | Der Name des Ereignisses, das den Workflow-Lauf ausgelöst hat. | -| `github.event_path` | `string` | Der Pfad zur vollständigen Event-Webhook-Nutzlast auf dem Runner. | -| `github.head_ref` | `string` | Das `head_ref` oder der Quell-Branch des Pull Requests in einem Workflow-Lauf. This property is only available when the event that triggers a workflow run is either `pull_request` or `pull_request_target`. | -| `github.job` | `string` | Die [`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) des aktuellen Jobs. | -| `github.ref` | `string` | Das Branch- oder Tag-Ref, das den Workflow-Lauf ausgelöst hat. For branches this is the format `refs/heads/`, and for tags it is `refs/tags/`. | -| `github.repository` | `string` | Der Inhaber- und Repository-Name, z. B. `Codertocat/Hello-World`. | -| `github.repository_owner` | `string` | Der Name des Repository-Besitzers. Beispielsweise `Codertocat`. | +| Name der Eigenschaft | Typ | Beschreibung | +| ------------------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `github` | `Objekt` | Der Top-Level-Kontext, der bei jedem Job oder Schritt im Workflow verfügbar ist. | +| `github.action` | `string` | Der Name der aktuell laufenden Aktion. {% data variables.product.prodname_dotcom %} removes special characters or uses the name `__run` when the current step runs a script. If you use the same action more than once in the same job, the name will include a suffix with the sequence number with underscore before it. For example, the first script you run will have the name `__run`, and the second script will be named `__run_2`. Ebenso wird die zweite Anrufung von `actions/checkout` `actionscheckout2` sein. | +| `github.action_path` | `string` | The path where your action is located. You can use this path to easily access files located in the same repository as your action. This attribute is only supported in composite actions. | +| `github.actor` | `string` | Der Anmeldename des Benutzers, der den Workflow-Lauf initiiert hat | +| `github.base_ref` | `string` | Das `base_ref` oder der Ziel-Branch des Pull Requests in einem Workflow-Lauf. This property is only available when the event that triggers a workflow run is either `pull_request` or `pull_request_target`. | +| `github.event` | `Objekt` | Die vollständige Nutzlast des Ereignis-Webhooks. Weitere Informationen findest Du unter „[Ereignisse, die Workflows auslösen](/articles/events-that-trigger-workflows)“. You can access individual properties of the event using this context. | +| `github.event_name` | `string` | Der Name des Ereignisses, das den Workflow-Lauf ausgelöst hat. | +| `github.event_path` | `string` | Der Pfad zur vollständigen Event-Webhook-Nutzlast auf dem Runner. | +| `github.head_ref` | `string` | Das `head_ref` oder der Quell-Branch des Pull Requests in einem Workflow-Lauf. This property is only available when the event that triggers a workflow run is either `pull_request` or `pull_request_target`. | +| `github.job` | `string` | Die [`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) des aktuellen Jobs. | +| `github.ref` | `string` | Das Branch- oder Tag-Ref, das den Workflow-Lauf ausgelöst hat. For branches this is the format `refs/heads/`, and for tags it is `refs/tags/`. | +| `github.repository` | `string` | Der Inhaber- und Repository-Name, z. B. `Codertocat/Hello-World`. | +| `github.repository_owner` | `string` | Der Name des Repository-Besitzers. Beispielsweise `Codertocat`. | | `github.run_id` | `string` | {% data reusables.github-actions.run_id_description %} | `github.run_number` | `string` | {% data reusables.github-actions.run_number_description %} -| `github.sha` | `string` | Die Commit-SHA, die den Workflow-Lauf ausgelöst hat. | -| `github.token` | `string` | Ein Token zum Authentifizieren im Namen der in Deinem Repository installierten GitHub-App. Funktionell entspricht dies dem Geheimnis `GITHUB_TOKEN`. Weitere Informationen findest Du unter „[Authentifizierung mit dem GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)". | -| `github.workflow` | `string` | Der Name des Workflows. Wenn in der Workflow-Datei kein `name` (Name) festgelegt ist, entspricht der Wert dieser Eigenschaft dem vollständigen Pfad der Workflow-Datei im Repository. | -| `github.workspace` | `string` | Das Standardarbeitsverzeichnis für Schritte und der Standardspeicherort Deines Repositorys bei Verwendung der Aktion [ `checkout`](https://github.com/actions/checkout). | +| `github.run_attempt` | `string` | A unique number for each attempt of a particular workflow run in a repository. This number begins at 1 for the workflow run's first attempt, and increments with each re-run. | +| `github.server_url` | `string` | Returns the URL of the GitHub server. For example: `https://github.com`. | +| `github.sha` | `string` | Die Commit-SHA, die den Workflow-Lauf ausgelöst hat. | +| `github.token` | `string` | Ein Token zum Authentifizieren im Namen der in Deinem Repository installierten GitHub-App. Funktionell entspricht dies dem Geheimnis `GITHUB_TOKEN`. Weitere Informationen findest Du unter „[Authentifizierung mit dem GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)". | +| `github.workflow` | `string` | Der Name des Workflows. Wenn in der Workflow-Datei kein `name` (Name) festgelegt ist, entspricht der Wert dieser Eigenschaft dem vollständigen Pfad der Workflow-Datei im Repository. | +| `github.workspace` | `string` | Das Standardarbeitsverzeichnis für Schritte und der Standardspeicherort Deines Repositorys bei Verwendung der Aktion [ `checkout`](https://github.com/actions/checkout). | ### `env`-Kontext @@ -130,6 +131,7 @@ Der `runner`-Kontext enthält Informationen über den Runner, der den aktuellen | Name der Eigenschaft | Typ | Beschreibung | | -------------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `runner.name` | `string` | {% data reusables.actions.runner-name-description %} | `runner.os` | `string` | {% data reusables.actions.runner-os-description %} | `runner.temp` | `string` | {% data reusables.actions.runner-temp-directory-description %} | `runner.tool_cache` | `string` | {% ifversion ghae %}For instructions on how to make sure your {% data variables.actions.hosted_runner %} has the required software installed, see "[Creating custom images](/actions/using-github-hosted-runners/creating-custom-images)." {% else %} {% data reusables.actions.runner-tool-cache-description %} {% endif %} diff --git a/translations/de-DE/content/actions/learn-github-actions/creating-workflow-templates.md b/translations/de-DE/content/actions/learn-github-actions/creating-workflow-templates.md new file mode 100644 index 0000000000..026d43ca06 --- /dev/null +++ b/translations/de-DE/content/actions/learn-github-actions/creating-workflow-templates.md @@ -0,0 +1,93 @@ +--- +title: Creating workflow templates +shortTitle: Creating templates +intro: Learn how you can create workflow templates to help people in your team add new workflows more easily. +redirect_from: + - /actions/configuring-and-managing-workflows/sharing-workflow-templates-within-your-organization +versions: + fpt: '*' + ghes: '*' + ghae: '*' +type: tutorial +topics: + - Workflows + - CI +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +## Übersicht + +{% data reusables.actions.workflow-organization-templates %} + +## Erstellen einer Workflowvorlage + +Workflowvorlagen können von Benutzern mit Schreibzugriff auf die `.github` Repository der Organisation erstellt werden. Die Vorlagen können dann von Organisationsmitgliedern verwendet werden, die über die Berechtigung zum Erstellen von Workflows verfügen. You can share workflow templates if your organization's repository is public or if the repository is private and on an Enterprise plan. + +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +{% note %} + +**Note:** To avoid duplication in workflows created from a template you can call reusable workflows from within a workflow template. This can help make your workflows easier to maintain. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." + +{% endnote %} +{% endif %} + +In diesem Verfahren wird veranschaulicht, wie eine Workflowvorlage und eine Metadatendatei erstellt werden. Die Metadatendatei beschreibt, wie die Vorlage benutzern beim Erstellen eines neuen Workflows angezeigt wird. + +1. Wenn es noch nicht vorhanden ist, erstellen Sie ein neues öffentliches Repository mit dem Namen `.github` in Ihrer Organisation. +2. Erstellen Sie ein Verzeichnis mit dem Namen `Workflowvorlagen`. +3. Erstellen Sie Ihre neue Workflowdatei im `Workflow-Vorlagen` Verzeichnis. + + Wenn Sie auf den Standardzweig eines Repositorys verweisen müssen, können Sie den `$default-branch` Platzhalter verwenden. Wenn ein Workflow mit Ihrer Vorlage erstellt wird, wird der Platzhalter automatisch durch den Namen der Standardverzweigung des Repositorys ersetzt. + + Diese Datei mit dem Namen `octo-organization-ci.yml` veranschaulicht beispielsweise einen grundlegenden Workflow. + + ```yaml + name: Octo Organization CI + + on: + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] + + jobs: + build: + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v2 + + - name: Run a one-line script + run: echo Hello from Octo Organization + ``` +4. Erstellen Sie eine Metadatendatei im `Workflow-Vorlagen` Verzeichnis. Die Metadatendatei muss denselben Namen wie die Workflowdatei haben, aber anstelle der Erweiterung `.yml` muss sie mit `.properties.json`angehängt werden. Diese Datei mit dem Namen `octo-organization-ci.properties.json enthält` beispielsweise die Metadaten für eine Workflowdatei mit dem Namen `octo-organization-ci.yml`: + ```yaml + • + "Name": "Octo Organization Workflow", + "beschreibung": "Octo Organization CI workflow template.", + "iconName": "example-icon", + "categories": [ + "Go" + ], + "filePatterns": [ + "package.json + + + + " + ``` + * `Name` - **erforderlich.** Der Name der Workflowvorlage. Dies wird in der Liste der verfügbaren Vorlagen angezeigt. + * `Beschreibung` - **erforderlich.** Die Beschreibung der Workflowvorlage. Dies wird in der Liste der verfügbaren Vorlagen angezeigt. + * `iconName` - **Erforderlich.** Definiert ein Symbol für den Eintrag des Workflows in der Vorlagenliste. Der `iconName` muss ein SVG-Symbol mit demselben Namen sein und in den `Workflow-Vorlagen` Verzeichnis gespeichert werden. Beispielsweise wird eine SVG-Datei mit dem Namen `example-icon.svg` als `Beispielsymbol`referenziert. + * `Kategorien` - **Optional.** Definiert die Sprachkategorie des Workflows. Wenn ein Benutzer die verfügbaren Vorlagen anzeigt, werden die Vorlagen, die derselben Sprache entsprechen, stärker in den Vordergrund gerückt. Informationen zu den verfügbaren Sprachkategorien finden Sie unter https://github.com/github/linguist/blob/master/lib/linguist/languages.yml. + * `filePatterns` - **Optional.** Ermöglicht die Verwendung der Vorlage, wenn das Repository des Benutzers eine Datei im Stammverzeichnis enthält, die einem definierten regulären Ausdruck entspricht. + +Um eine weitere Workflowvorlage hinzuzufügen, fügen Sie Ihre Dateien `Workflow-Vorlagen` -Verzeichnis hinzu. Ein Beispiel: + +![Workflow-Vorlagendateien](/assets/images/help/images/workflow-template-files.png) + +## Nächste Schritte: + +To continue learning about {% data variables.product.prodname_actions %}, see "[Using workflow templates](/actions/learn-github-actions/using-workflow-templates)." diff --git a/translations/de-DE/content/actions/learn-github-actions/environment-variables.md b/translations/de-DE/content/actions/learn-github-actions/environment-variables.md index f0b5291519..fd62edf957 100644 --- a/translations/de-DE/content/actions/learn-github-actions/environment-variables.md +++ b/translations/de-DE/content/actions/learn-github-actions/environment-variables.md @@ -15,7 +15,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Informationen zu Umgebungsvariablen @@ -73,6 +72,7 @@ Es wird dringend empfohlen, dass Aktionen Umgebungsvariablen verwenden, um auf d | `GITHUB_SERVER_URL` | Returns the URL of the {% data variables.product.product_name %} server. For example: `https://{% data variables.product.product_url %}`. | | `GITHUB_API_URL` | Gibt die API-URL zurück. For example: `{% data variables.product.api_url_code %}`. | | `GITHUB_GRAPHQL_URL` | Gibt die GraphQL-API-URL zurück. For example: `{% data variables.product.graphql_url_code %}`. | +| `RUNNER_NAME` | {% data reusables.actions.runner-name-description %} | `RUNNER_OS` | {% data reusables.actions.runner-os-description %} | `RUNNER_TEMP` | {% data reusables.actions.runner-temp-directory-description %} {% ifversion not ghae %}| `RUNNER_TOOL_CACHE` | {% data reusables.actions.runner-tool-cache-description %}{% endif %} diff --git a/translations/de-DE/content/actions/learn-github-actions/essential-features-of-github-actions.md b/translations/de-DE/content/actions/learn-github-actions/essential-features-of-github-actions.md index e12a8022b5..5868b05ca7 100644 --- a/translations/de-DE/content/actions/learn-github-actions/essential-features-of-github-actions.md +++ b/translations/de-DE/content/actions/learn-github-actions/essential-features-of-github-actions.md @@ -13,7 +13,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Übersicht @@ -62,7 +61,7 @@ Weitere Informationen findest Du unter „[Workflow-Syntax für {% data variable ## Sharing data between jobs -If your job generates files that you want to share with another job in the same workflow, or if you want to save the files for later reference, you can store them in {% data variables.product.prodname_dotcom %} as _artifacts_. Artefakte sind die Dateien, die erstellt werden, wenn Sie Ihren Code erstellen und testen. Artefakte können beispielsweise Binär- oder Paketdateien, Testergebnisse, Screenshots oder Protokolldateien sein. Artifacts are associated with the workflow run where they were created and can be used by another job. +If your job generates files that you want to share with another job in the same workflow, or if you want to save the files for later reference, you can store them in {% data variables.product.prodname_dotcom %} as _artifacts_. Artefakte sind die Dateien, die erstellt werden, wenn Sie Ihren Code erstellen und testen. Artefakte können beispielsweise Binär- oder Paketdateien, Testergebnisse, Screenshots oder Protokolldateien sein. Artifacts are associated with the workflow run where they were created and can be used by another job. {% data reusables.actions.reusable-workflow-artifacts %} For example, you can create a file and then upload it as an artifact. diff --git a/translations/de-DE/content/actions/learn-github-actions/events-that-trigger-workflows.md b/translations/de-DE/content/actions/learn-github-actions/events-that-trigger-workflows.md index 1613c8ee07..06d5bf1206 100644 --- a/translations/de-DE/content/actions/learn-github-actions/events-that-trigger-workflows.md +++ b/translations/de-DE/content/actions/learn-github-actions/events-that-trigger-workflows.md @@ -17,7 +17,6 @@ shortTitle: 'Ereignisse, die Workflows auslösen' {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Configuring workflow events @@ -165,6 +164,26 @@ on: types: [opened, deleted] ``` +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## Workflow reuse events + +`workflow_call` is a keyword used as the value of `on` in a workflow, in the same way as an event. It indicates that a workflow can be called from another workflow. For more information see, "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." + +### `workflow_call` + +| Nutzlast des Webhook-Ereignisses | Aktivitätstypen | `GITHUB_SHA` | `GITHUB_REF` | +| -------------------------------- | --------------- | --------------------------- | --------------------------- | +| Same as the caller workflow | – | Same as the caller workflow | Same as the caller workflow | + +#### Beispiel + +To make a workflow reusable it must include `workflow_call` as one of the values of `on`. The example below only runs the workflow when it's called from another workflow: + +```yaml +on: workflow_call +``` +{% endif %} + ## Webhook-Ereignisse You can configure your workflow to run when webhook events are generated on {% data variables.product.product_name %}. Einige Ereignisse werden von mehreren Aktivitätstypen ausgelöst. Wird ein Ereignis von mehreren Aktivitätstypen ausgelöst, können Sie die Aktivitätstypen angeben, die die Ausführung des Workflows auslösen sollen. For more information, see "[Webhooks](/webhooks)." diff --git a/translations/de-DE/content/actions/learn-github-actions/expressions.md b/translations/de-DE/content/actions/learn-github-actions/expressions.md index 83c23de19a..78f6682a80 100644 --- a/translations/de-DE/content/actions/learn-github-actions/expressions.md +++ b/translations/de-DE/content/actions/learn-github-actions/expressions.md @@ -12,7 +12,6 @@ miniTocMaxHeadingLevel: 3 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About expressions diff --git a/translations/de-DE/content/actions/learn-github-actions/finding-and-customizing-actions.md b/translations/de-DE/content/actions/learn-github-actions/finding-and-customizing-actions.md index 9bdd14c177..6e537fb9fd 100644 --- a/translations/de-DE/content/actions/learn-github-actions/finding-and-customizing-actions.md +++ b/translations/de-DE/content/actions/learn-github-actions/finding-and-customizing-actions.md @@ -18,7 +18,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Übersicht @@ -168,7 +167,7 @@ jobs: verwendet: docker://alpine:3.8 ``` -Einige Beispiele für Docker-Aktionen findest Du im [Docker-image.yml-Workflow](https://github.com/actions/starter-workflows/blob/main/ci/docker-image.yml) oder unter „[Eine Docker-Container-Aktion erstellen](/articles/creating-a-docker-container-action)“. +Einige Beispiele für Docker-Aktionen finden Sie im [Docker-image.yml-Workflow](https://github.com/actions/starter-workflows/blob/main/ci/docker-image.yml) oder unter „[Eine Docker-Container-Aktion erstellen](/articles/creating-a-docker-container-action)“. ## Nächste Schritte: diff --git a/translations/de-DE/content/actions/learn-github-actions/index.md b/translations/de-DE/content/actions/learn-github-actions/index.md index 0c382694b3..2a211fefef 100644 --- a/translations/de-DE/content/actions/learn-github-actions/index.md +++ b/translations/de-DE/content/actions/learn-github-actions/index.md @@ -32,8 +32,10 @@ children: - /finding-and-customizing-actions - /essential-features-of-github-actions - /managing-complex-workflows - - /sharing-workflows-with-your-organization + - /sharing-workflows-secrets-and-runners-with-your-organization + - /creating-workflow-templates - /using-workflow-templates + - /reusing-workflows - /events-that-trigger-workflows - /expressions - /contexts diff --git a/translations/de-DE/content/actions/learn-github-actions/managing-complex-workflows.md b/translations/de-DE/content/actions/learn-github-actions/managing-complex-workflows.md index c8882c9d38..89a0248df3 100644 --- a/translations/de-DE/content/actions/learn-github-actions/managing-complex-workflows.md +++ b/translations/de-DE/content/actions/learn-github-actions/managing-complex-workflows.md @@ -13,7 +13,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Übersicht @@ -170,10 +169,13 @@ To learn more about self-hosted runner labels, see ["Using labels with self-host {% data variables.product.prodname_dotcom %}-hosted runner labels, see ["Supported runners and hardware resources"](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources). {% endif %} -{% ifversion fpt or ghes > 3.0 %} +{% data reusables.actions.reusable-workflows %} + +{% ifversion fpt or ghes > 3.0 or ghae-next %} + ## Using environments -You can configure environments with protection rules and secrets. Each job in a workflow can reference a single environment. Any protection rules configured for the environment must pass before a job referencing the environment is sent to a runner. For more information, see "[Environments](/actions/reference/environments)." +You can configure environments with protection rules and secrets. Each job in a workflow can reference a single environment. Any protection rules configured for the environment must pass before a job referencing the environment is sent to a runner. For more information, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." {% endif %} ## Verwenden einer Workflowvorlage @@ -187,4 +189,4 @@ You can configure environments with protection rules and secrets. Each job in a ## Nächste Schritte: -To continue learning about {% data variables.product.prodname_actions %}, see "[Sharing workflows with your organization](/actions/learn-github-actions/sharing-workflows-with-your-organization)." +To continue learning about {% data variables.product.prodname_actions %}, see "[Sharing workflows, secrets, and runners with your organization](/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization)." diff --git a/translations/de-DE/content/actions/learn-github-actions/reusing-workflows.md b/translations/de-DE/content/actions/learn-github-actions/reusing-workflows.md new file mode 100644 index 0000000000..34676e82b5 --- /dev/null +++ b/translations/de-DE/content/actions/learn-github-actions/reusing-workflows.md @@ -0,0 +1,195 @@ +--- +title: Reusing workflows +shortTitle: Reusing workflows +intro: Learn how to avoid duplication when creating a workflow by reusing existing workflows. +miniTocMaxHeadingLevel: 3 +versions: + fpt: '*' + ghes: '>=3.4' + ghae: issue-4757 +type: how_to +topics: + - Workflows +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +{% note %} + +**Note:** Reusable workflows are currently in beta and subject to change. + +{% endnote %} + +## Übersicht + +Rather than copying and pasting from one workflow to another, you can make workflows reusable. You and anyone with access to the reusable workflow can then call the reusable workflow from another workflow. + +Reusing workflows avoids duplication. This makes workflows easier to maintain and allows you to create new workflows more quickly by building on the work of others, just as you do with actions. Workflow reuse also promotes best practice by helping you to use workflows that are well designed, have already been tested, and have been proved to be effective. Your organization can build up a library of reusable workflows that can be centrally maintained. + +A workflow that uses another workflow is referred to as a "caller" workflow. The reusable workflow is a "called" workflow. One caller workflow can use multiple called workflows. Each called workflow is referenced in a single line. The result is that the caller workflow file may contain just a few lines of YAML, but may perform a large number of tasks when it's run. When you reuse a workflow, the entire called workflow is used, just as if it was part of the caller workflow. + +If you reuse a workflow from a different repository, any actions in the called workflow run as if they were part of the caller workflow. For example, if the called workflow uses `actions/checkout`, the action checks out the contents of the repository that hosts the caller workflow, not the called workflow. + +When a reusable workflow is triggered by a caller workflow, the `github` context is always associated with the caller workflow. For more information about the `github` context, see "[Context and expression syntax for GitHub Actions](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)." + +## Access to reusable workflows + +A reusable workflow can be used by another workflow if any of the following is true: + +* Both workflows are in the same repository. +* The called workflow is stored in a public repository. +* The called workflow is stored in an internal repository and the settings for that repository allow it to be accessed. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#allowing-access-to-components-in-an-internal-repository)." + +## Einschränkungen + +* Reusable workflows can't call other reusable workflows. +* Reusable workflows stored within a private repository can only be used by workflows within the same repository. +* Any environment variables set in an `env` context defined at the workflow level in the caller workflow are not be propagated to the called workflow. For more information about the `env` context, see "[Context and expression syntax for GitHub Actions](/actions/reference/context-and-expression-syntax-for-github-actions#env-context)." + +The following limitations will be removed when workflow reuse moves out of beta: +* Reusable workflows can't reference self-hosted runners. +* You can't set the concurrency of a called workflow from the caller workflow. For more information about `jobs..concurrency`, see "[Workflow syntax for GitHub Actions](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idconcurrency)." +* Outputs generated by a called workflow can't be accessed by the caller workflow. + +## Creating a reusable workflow + +Reusable workflows are YAML-formatted files, very similar to any other workflow file. As with other workflow files, you locate reusable workflows in the `.github/workflows` directory of a repository. Subdirectories of the `workflows` directory are not supported. + +For a workflow to be reusable, the values for `on` must include `workflow_call`: + +```yaml +on: + workflow_call: +``` + +You can define inputs and secrets, which can be passed from the caller workflow and then used within the called workflow. The following example, from a reusable workflow, defines two inputs (called "ring" and "environment") and one secret (called "token"): + +```yaml +on: + workflow_call: + inputs: + ring: + description: 'Identifier for the target deployment ring' + default: 'ring-0' + required: false + type: string + environment: + required: false + type: string + secrets: + token: + required: false +``` + +For details of the syntax for defining inputs and secrets, see [on.workflow_call.inputs](/actions/reference/workflow-syntax-for-github-actions#onworkflow_callinputs) and [on.workflow_call.secrets](/actions/reference/workflow-syntax-for-github-actions#onworkflow_callsecrets). + +### Example reusable workflow + +This reusable workflow file named `workflow-B.yml` (we'll refer to this later) takes an input string and a secret from the caller workflow and uses them in an action. + +{% raw %} +```yaml{:copy} +name: Reusable workflow example + +on: + workflow_call: + inputs: + username: + required: true + type: string + secrets: + token: + required: true + +jobs: + example_job: + name: Pass input and secrets to my-action + runs-on: ubuntu-latest + steps: + - uses: ./.github/actions/my-action@v1 + with: + username: ${{ inputs.username }} + token: ${{ secrets.token }} +``` +{% endraw %} + +## Calling a reusable workflow + +You call a reusable workflow by using the `uses` keyword. Unlike when you are using actions within a workflow, you call reusable workflows directly within a job, and not from within job steps. + +[`jobs..uses`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_iduses) + +You reference reusable workflow files using the syntax: + +`{owner}/{repo}/{path}/{filename}@{ref}` + +You can call multiple workflows, referencing each in a separate job. + +{% data reusables.actions.uses-keyword-example %} + +### Passing inputs and secrets to a reusable workflow + +Use the `with` keyword in a job to pass named inputs to the called workflow. Use the `secrets` keyword to pass named secrets. The inputs and secrets you pass must be defined in the called workflow. For inputs, the data type of the input value must match the type specified for that input in the called workflow (boolean, number, or string). + +{% raw %} +```yaml +with: + username: mona +secrets: + token: ${{ secrets.TOKEN }} +``` +{% endraw %} + +### Supported keywords for jobs that call a reusable workflow + +When you call a reusable workflow, you can only use the following keywords in the job containing the call: + +* [`jobs..name`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idname) +* [`jobs..uses`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_iduses) +* [`jobs..with`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idwith) +* [`jobs..with.`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idwithinput_id) +* [`jobs..secrets`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idsecrets) +* [`jobs..secrets.`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idsecretssecret_id) +* [`jobs..needs`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds) +* [`jobs..if`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idif) +* [`jobs..permissions`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idpermissions) + + {% note %} + + **Hinweis:** + + * If `jobs..permissions` is not specified in the calling job, the called workflow will have the default permissions for the `GITHUB_TOKEN`. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)." + * The `GITHUB_TOKEN` permissions passed from the caller workflow can be only downgraded (not elevated) by the called workflow. + + {% endnote %} + +### Example caller workflow + +This workflow file calls two workflow files. The second of these, `workflow-B.yml` (shown above), is passed an input, `username`, and a secret, `token`. + +{% raw %} +```yaml{:copy} +name: Call a reusable workflow + +on: + pull_request: + branches: + - main + +jobs: + call-workflow: + uses: octo-org/example-repo/.github/workflows/workflow-A.yml@v1 + + call-workflow-passing-data: + uses: octo-org/example-repo/.github/workflows/workflow-B.yml@main + with: + username: mona + secrets: + token: ${{ secrets.TOKEN }} +``` +{% endraw %} + +## Nächste Schritte: + +To continue learning about {% data variables.product.prodname_actions %}, see "[Events that trigger workflows](/actions/learn-github-actions/events-that-trigger-workflows)." diff --git a/translations/de-DE/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md b/translations/de-DE/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md new file mode 100644 index 0000000000..94066214fa --- /dev/null +++ b/translations/de-DE/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md @@ -0,0 +1,53 @@ +--- +title: 'Sharing workflows, secrets, and runners with your organization' +shortTitle: Sharing workflows with your organization +intro: 'Learn how you can use organization features to collaborate with your team, by sharing workflow templates, secrets, and self-hosted runners.' +redirect_from: + - /actions/learn-github-actions/sharing-workflows-with-your-organization +versions: + fpt: '*' + ghes: '*' + ghae: '*' +type: how_to +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +## Übersicht + +If you need to share workflows and other {% data variables.product.prodname_actions %} features with your team, then consider collaborating within a {% data variables.product.prodname_dotcom %} organization. An organization allows you to centrally store and manage secrets, artifacts, and self-hosted runners. You can also create workflow templates in the `.github` repository and share them with other users in your organization. + +## Using workflow templates + +{% data reusables.actions.workflow-organization-templates %} For more information, see "[Creating workflow templates](/actions/learn-github-actions/creating-workflow-templates)." + +{% data reusables.actions.reusable-workflows %} + +## Sharing secrets within an organization + +You can centrally manage your secrets within an organization, and then make them available to selected repositories. This also means that you can update a secret in one location, and have the change apply to all repository workflows that use the secret. + +Beim Erstellen eines geheimen Schlüssels in einer Organisation können Sie eine Richtlinie verwenden, um einzuschränken, welche Repositorys auf diesen geheimen Schlüssel zugreifen können. Sie können z. B. Zugriff auf alle Repositorys gewähren oder den Zugriff auf nur private Repositorys oder eine angegebene Liste von Repositorys beschränken. + +{% data reusables.github-actions.permissions-statement-secrets-organization %} + +{% data reusables.organizations.navigate-to-org %} +{% data reusables.organizations.org_settings %} +{% data reusables.github-actions.sidebar-secret %} +1. Klicken Sie auf **Neue geheime**. +1. Geben Sie einen Namen für Ihr Geheimnis in das Eingabefeld **Name** ein. +1. Geben Sie den **Value** für Ihr Geheimnis ein. +1. Wählen Sie im **Repository-Zugriff** Dropdownliste eine Zugriffsrichtlinie aus. +1. Klicken Sie auf **Add secret** (Geheimnis hinzufügen). + +## Share self-hosted runners within an organization + +Organization admins can add their self-hosted runners to groups, and then create policies that control which repositories can access the group. + +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)." + + +## Nächste Schritte: + +To continue learning about {% data variables.product.prodname_actions %}, see "[Creating workflow templates](/actions/learn-github-actions/creating-workflow-templates)." diff --git a/translations/de-DE/content/actions/learn-github-actions/understanding-github-actions.md b/translations/de-DE/content/actions/learn-github-actions/understanding-github-actions.md index aad5cbb1c3..30b98e4b24 100644 --- a/translations/de-DE/content/actions/learn-github-actions/understanding-github-actions.md +++ b/translations/de-DE/content/actions/learn-github-actions/understanding-github-actions.md @@ -18,7 +18,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Übersicht @@ -36,7 +35,7 @@ Below is a list of the multiple {% data variables.product.prodname_actions %} co ### Workflows -The workflow is an automated procedure that you add to your repository. Workflows are made up of one or more jobs and can be scheduled or triggered by an event. The workflow can be used to build, test, package, release, or deploy a project on {% data variables.product.prodname_dotcom %}. +The workflow is an automated procedure that you add to your repository. Workflows are made up of one or more jobs and can be scheduled or triggered by an event. The workflow can be used to build, test, package, release, or deploy a project on {% data variables.product.prodname_dotcom %}. {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %}You can reference a workflow within another workflow, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."{% endif %} ### Ereignisse diff --git a/translations/de-DE/content/actions/learn-github-actions/usage-limits-billing-and-administration.md b/translations/de-DE/content/actions/learn-github-actions/usage-limits-billing-and-administration.md index e64abdd757..09082365be 100644 --- a/translations/de-DE/content/actions/learn-github-actions/usage-limits-billing-and-administration.md +++ b/translations/de-DE/content/actions/learn-github-actions/usage-limits-billing-and-administration.md @@ -16,7 +16,6 @@ shortTitle: Workflow billing & limits {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Informationen zur Abrechnung für {% data variables.product.prodname_actions %} @@ -61,6 +60,12 @@ Usage limits apply to self-hosted runners. Weitere Informationen findest Du unte Neben den Nutzungsbeschränkungen musst Du auch sicherstellen, dass Du {% data variables.product.prodname_actions %} innerhalb der [GitHub-Nutzungsbedingungen](/articles/github-terms-of-service/) verwendest. Weitere Informationen zu {% data variables.product.prodname_actions %}-spezifischen Bedingungen findest Du unter [Zusätzliche Produktbedingungen für GitHub](/github/site-policy/github-additional-product-terms#a-actions-usage). {% endif %} +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## Billing for reusable workflows + +If you reuse a workflow, billing is always associated with the caller workflow. For more information see, "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." +{% endif %} + {% ifversion fpt or ghes > 2.22 or ghae %} ## Artifact and log retention policy diff --git a/translations/de-DE/content/actions/learn-github-actions/using-workflow-templates.md b/translations/de-DE/content/actions/learn-github-actions/using-workflow-templates.md index 246b16b6f6..44ab1b88b9 100644 --- a/translations/de-DE/content/actions/learn-github-actions/using-workflow-templates.md +++ b/translations/de-DE/content/actions/learn-github-actions/using-workflow-templates.md @@ -1,7 +1,7 @@ --- title: Using workflow templates shortTitle: Using templates -intro: You can set up CI using a workflow template that matches the language and tooling you want to use. +intro: '{% data variables.product.product_name %} provides workflow templates for a variety of languages and tooling.' product: '{% data reusables.gated-features.actions %}' redirect_from: - /articles/setting-up-continuous-integration-using-github-actions @@ -17,34 +17,37 @@ type: tutorial topics: - Workflows - CI + - CD --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -Jeder Benutzer mit Schreibberechtigung für ein Repository kann mit {% data variables.product.prodname_actions %} eine fortlaufende Integration (CI) einrichten. +## Informationen zu Workflow-Vorlagen -Nach der Einrichtung der CI können Sie den Workflow an Ihre Bedürfnisse anpassen. +{% data variables.product.product_name %} offers workflow templates for a variety of languages and tooling. When you set up workflows in your repository, {% data variables.product.product_name %} analyzes the code in your repository and recommends workflows based on the language and framework in your repository. Wenn Sie beispielsweise [Node.js](https://nodejs.org/en/)verwenden, schlägt {% data variables.product.product_name %} eine Vorlagendatei vor, die Ihre Node.js-Pakete installiert und Ihre Tests ausführt. + +You can also create your own workflow templates to share with your organization. For more information, see "[Creating workflow templates](/actions/learn-github-actions/creating-workflow-templates)." + +## Using workflow templates + +Anyone with write permission to a repository can set up {% data variables.product.prodname_actions %} workflows for CI/CD or other automation. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} -1. Wähle die Vorlage aus, die der Sprache und den Tools entspricht, die Du verwenden möchtest, und klicke dann auf **Set up this workflow** (Diesen Workflow einrichten). ![Schaltfläche „Setup workflow“ (Workflow einrichten)](/assets/images/help/repository/setup-workflow-button.png) -5. Klicke auf **Start commit** (Commit starten). ![Schaltfläche „Start commit“ (Commit starten)](/assets/images/help/repository/start-commit.png) -{% data reusables.files.write_commit_message %} -{% data reusables.files.choose_commit_branch %} -{% data reusables.files.propose_new_file %} - -Sobald ein Push an Dein Repository erfolgt ist, kannst Du den Status und die detaillierten Protokolle Deines fortlaufenden Integrationsworkflows verfolgen, der auf {% data variables.product.prodname_dotcom %} ausgeführt wird, und angepasste Benachrichtigungen erhalten. Weitere Informationen findest Du unter „[Benachrichtigungen konfigurieren](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)“ und „[Workflowausführung verwalten](/articles/managing-a-workflow-run)“. - -{% 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)." +1. If you already have a workflow in your repository, click **New workflow**. +1. Find the template that you want to use, then click **Set up this workflow**. +1. If the workflow template contains comments detailing additional setup steps, follow these steps. +1. Some workflow templates use secrets. For example, {% raw %}`${{ secrets.npm_token }}`{% endraw %}. If the workflow template uses a secret, store the value described in the secret name as a secret in your repository. For more information, see "[Encrypted secrets](/actions/reference/encrypted-secrets)." +1. Optionally, make additional changes. For example, you might want to change the value of `on` to change when the workflow runs. +1. Klicke auf **Start commit** (Commit starten). +1. Write a commit message and decide whether to commit directly to the default branch or to open a pull request. ## Weiterführende Informationen - „[Informationen zur kontinuierlichen Integration](/articles/about-continuous-integration)“ -- „[Einen Workflow-Lauf verwalten](/articles/managing-a-workflow-run)“ +- "[Managing workflow runs](/actions/managing-workflow-runs)" +- "[About monitoring and troubleshooting](/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting)" - "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" {% ifversion fpt %} - "[ Abrechnung für {% data variables.product.prodname_actions %} verwalten](/billing/managing-billing-for-github-actions)" diff --git a/translations/de-DE/content/actions/learn-github-actions/workflow-commands-for-github-actions.md b/translations/de-DE/content/actions/learn-github-actions/workflow-commands-for-github-actions.md index 3fbc6ccc9a..1022d0e7d7 100644 --- a/translations/de-DE/content/actions/learn-github-actions/workflow-commands-for-github-actions.md +++ b/translations/de-DE/content/actions/learn-github-actions/workflow-commands-for-github-actions.md @@ -18,7 +18,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Informationen zu Workflow-Befehlen @@ -89,7 +88,7 @@ Die folgende Tabelle zeigt, welche Toolkit-Funktionen innerhalb eines Workflows | `core.setOutput` | `set-output` | | `core.setSecret` | `add-mask` | | `core.startGroup` | `Gruppe` | -| `core.warning` | `warning file` | +| `core.warning` | `warnung` | {% ifversion ghes < 3.0 %} ## Setting an environment variable @@ -331,6 +330,12 @@ echo "{name}={value}" >> $GITHUB_ENV Creates or updates an environment variable for any steps running next in a job. The step that creates or updates the environment variable does not have access to the new value, but all subsequent steps in a job will have access. Bei Umgebungsvariablen wird die Groß- und Kleinschreibung berücksichtigt. Sie können auch Satzzeichen enthalten. +{% note %} + +**Note:** Environment variables must be explicitly referenced using the [`env` context](/actions/reference/context-and-expression-syntax-for-github-actions#env-context) in expression syntax or through use of the `$GITHUB_ENV` file directly; environment variables are not implicitly available in shell commands. + +{% endnote %} + ### Beispiel {% raw %} @@ -376,7 +381,7 @@ steps: echo "{path}" >> $GITHUB_PATH ``` -Prepends a directory to the system `PATH` variable and makes it available to all subsequent actions in the current job; the currently running action cannot access the updated path variable. To see the currently defined paths for your job, you can use `echo "$PATH"` in a step or an action. +Prepends a directory to the system `PATH` variable and automatically makes it available to all subsequent actions in the current job; the currently running action cannot access the updated path variable. To see the currently defined paths for your job, you can use `echo "$PATH"` in a step or an action. ### Beispiel diff --git a/translations/de-DE/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md b/translations/de-DE/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md index affab32786..fd48f792a5 100644 --- a/translations/de-DE/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md +++ b/translations/de-DE/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md @@ -16,7 +16,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Informationen zur YAML-Syntaxs für Workflows @@ -184,9 +183,91 @@ Diffs are limited to 300 files. If there are files changed that aren't matched i Weitere Informationen findest Du unter „[Informationen zum Vergleich von Branches in Pull-Requests](/articles/about-comparing-branches-in-pull-requests)“. +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## `on.workflow_call.inputs` + +When using the `workflow_call` keyword, you can optionally specify inputs that are passed to the called workflow from the caller workflow. Inputs for reusable workflows are specified with the same format as action inputs. For more information about inputs, see "[Metadata syntax for GitHub Actions](/actions/creating-actions/metadata-syntax-for-github-actions#inputs)." For more information about the `workflow_call` keyword, see "[Events that trigger workflows](/actions/learn-github-actions/events-that-trigger-workflows#workflow-reuse-events)." + +In addition to the standard input parameters that are available, `on.workflow_call.inputs` requires a `type` parameter. For more information, see [`on.workflow_call..type`](#onworkflow_callinput_idtype). + +If a `default` parameter is not set, the default value of the input is `false` for a boolean, `0` for a number, and `""` for a string. + +Within the called workflow, you can use the `inputs` context to refer to an input. + +If a caller workflow passes an input that is not specified in the called workflow, this results in an error. + +### Beispiel + +{% raw %} +```yaml +on: + workflow_call: + inputs: + username: + description: 'A username passed from the caller workflow' + default: 'john-doe' + required: false + type: string + +jobs: + print-username: + runs-on: ubuntu-latest + + steps: + - name: Print the input name to STDOUT + run: echo The username is ${{ inputs.username }} +``` +{% endraw %} + +For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." + +## `on.workflow_call..type` + +Required if input is defined for the `on.workflow_call` keyword. The value of this parameter is a string specifying the data type of the input. This must be one of: `boolean`, `number`, or `string`. + +## `on.workflow_call.secrets` + +A map of the secrets that can be used in the called workflow. + +Within the called workflow, you can use the `secrets` context to refer to a secret. + +If a caller workflow passes a secret that is not specified in the called workflow, this results in an error. + +### Beispiel + +{% raw %} +```yaml +on: + workflow_call: + secrets: + access-token: + description: 'A token passed from the caller workflow' + required: false + +jobs: + pass-secret-to-action: + runs-on: ubuntu-latest + + steps: + - name: Pass the received secret to an action + uses: ./.github/actions/my-action@v1 + with: + token: ${{ secrets.access-token }} +``` +{% endraw %} + +## `on.workflow_call.secrets.` + +A string identifier to associate with the secret. + +## `on.workflow_call.secrets..required` + +A boolean specifying whether the secret must be supplied. +{% endif %} + ## `on.workflow_dispatch.inputs` -When using `workflow_dispatch` event, you can optionally specify inputs that are passed to the workflow. Workflow dispatch inputs are specified with the same format as action inputs. For more information about the format see "[Metadata syntax for GitHub Actions](/actions/creating-actions/metadata-syntax-for-github-actions#inputs)." +When using the `workflow_dispatch` event, you can optionally specify inputs that are passed to the workflow. Workflow dispatch inputs are specified with the same format as action inputs. For more information about the format see "[Metadata syntax for GitHub Actions](/actions/creating-actions/metadata-syntax-for-github-actions#inputs)." ```yaml on: @@ -272,8 +353,6 @@ defaults: {% ifversion fpt or ghae-next or ghes > 3.1 %} ## `concurrency` -{% data reusables.actions.concurrency-beta %} - Concurrency ensures that only a single job or workflow using the same concurrency group will run at a time. A concurrency group can be any string or expression. The expression can only use the [`github` context](/actions/learn-github-actions/contexts#github-context). For more information about expressions, see "[Expressions](/actions/learn-github-actions/expressions)." You can also specify `concurrency` at the job level. For more information, see [`jobs..concurrency`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idconcurrency). @@ -428,7 +507,7 @@ jobs: {% ifversion fpt or ghes > 3.0 or ghae %} ## `jobs..environment` -The environment that the job references. All environment protection rules must pass before a job referencing the environment is sent to a runner. For more information, see "[Environments](/actions/reference/environments)." +The environment that the job references. All environment protection rules must pass before a job referencing the environment is sent to a runner. For more information, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." You can provide the environment as only the environment `name`, or as an environment object with the `name` and `url`. The URL maps to `environment_url` in the deployments API. For more information about the deployments API, see "[Deployments](/rest/reference/repos#deployments)." @@ -463,8 +542,6 @@ environment: {% ifversion fpt or ghae-next or ghes > 3.1 %} ## `jobs..concurrency` -{% data reusables.actions.concurrency-beta %} - {% note %} **Note:** When concurrency is specified at the job level, order is not guaranteed for jobs or runs that queue within 5 minutes of each other. @@ -1348,6 +1425,70 @@ Zusätzliche Optionen für die Docker-Container-Ressource. Eine Liste der Option {% endwarning %} +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## `jobs..uses` + +The location and version of a reusable workflow file to run as a job. + +`{owner}/{repo}/{path}/{filename}@{ref}` + +`{ref}` can be a SHA, a release tag, or a branch name. Using the commit SHA is the safest for stability and security. For more information, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#reusing-third-party-workflows)." + +### Beispiel + +{% data reusables.actions.uses-keyword-example %} + +For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." + +## `jobs..with` + +When a job is used to call a reusable workflow, you can use `with` to provide a map of inputs that are passed to the called workflow. + +Any inputs that you pass must match the input specifications defined in the called workflow. + +Unlike [`jobs..steps[*].with`](#jobsjob_idstepswith), the inputs you pass with `jobs..with` are not be available as environment variables in the called workflow. Instead, you can reference the inputs by using the `inputs` context. + +### Beispiel + +```yaml +jobs: + call-workflow: + uses: octo-org/example-repo/.github/workflows/called-workflow.yml@main + with: + username: mona +``` + +## `jobs..with.` + +A pair consisting of a string identifier for the input and the value of the input. The identifier must match the name of an input defined by [`on.workflow_call.inputs.`](/actions/creating-actions/metadata-syntax-for-github-actions#inputsinput_id) in the called workflow. The data type of the value must match the type defined by [`on.workflow_call..type`](#onworkflow_callinput_idtype) in the called workflow. + +Allowed expression contexts: `github`, and `needs`. + +## `jobs..secrets` + +When a job is used to call a reusable workflow, you can use `secrets` to provide a map of secrets that are passed to the called workflow. + +Any secrets that you pass must match the names defined in the called workflow. + +### Beispiel + +{% raw %} +```yaml +jobs: + call-workflow: + uses: octo-org/example-repo/.github/workflows/called-workflow.yml@main + secrets: + access-token: ${{ secrets.PERSONAL_ACCESS_TOKEN }} +``` +{% endraw %} + +## `jobs..secrets.` + +A pair consisting of a string identifier for the secret and the value of the secret. The identifier must match the name of a secret defined by [`on.workflow_call.secrets.`](#onworkflow_callsecretssecret_id) in the called workflow. + +Allowed expression contexts: `github`, `needs`, and `secrets`. +{% endif %} + ## Spickzettel zu Filtermustern In Pfad-, Branch- und Tag-Filtern kannst Du Sonderzeichen benutzen. diff --git a/translations/de-DE/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md b/translations/de-DE/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md index b2f9a29615..ae5da83700 100644 --- a/translations/de-DE/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md +++ b/translations/de-DE/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md @@ -16,8 +16,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## Einführung diff --git a/translations/de-DE/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md b/translations/de-DE/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md index 6b5ee4d2bd..72733059c8 100644 --- a/translations/de-DE/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md +++ b/translations/de-DE/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md @@ -16,8 +16,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## Einführung diff --git a/translations/de-DE/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md b/translations/de-DE/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md index 054811266b..29f3d8a903 100644 --- a/translations/de-DE/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md +++ b/translations/de-DE/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md @@ -17,8 +17,6 @@ shortTitle: Add label to comment on issue {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## Einführung diff --git a/translations/de-DE/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md b/translations/de-DE/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md index 2899a85c3b..b10c93b7c1 100644 --- a/translations/de-DE/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md +++ b/translations/de-DE/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md @@ -17,8 +17,6 @@ shortTitle: Move assigned issues {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## Einführung diff --git a/translations/de-DE/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md b/translations/de-DE/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md index e832dd2af5..f8b55ff1ee 100644 --- a/translations/de-DE/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md +++ b/translations/de-DE/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md @@ -17,8 +17,6 @@ shortTitle: Remove label when adding card {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## Einführung diff --git a/translations/de-DE/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md b/translations/de-DE/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md index edd537ce28..dccdb7f5be 100644 --- a/translations/de-DE/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md +++ b/translations/de-DE/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md @@ -16,8 +16,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## Einführung diff --git a/translations/de-DE/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md b/translations/de-DE/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md index fcb7ebb0dc..4a03ed477d 100644 --- a/translations/de-DE/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md +++ b/translations/de-DE/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md @@ -9,7 +9,9 @@ shortTitle: Approve public fork runs ## About workflow runs from public forks -{% data reusables.actions.workflow-run-approve-public-fork %} However, you can configure this behavior for a [repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks), [organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#configuring-required-approval-for-workflows-from-public-forks), or [enterprise](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account#configuring-required-approval-for-workflows-from-public-forks). +{% data reusables.actions.workflow-run-approve-public-fork %} + +You can configure workflow approval requirements for a [repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks), [organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#configuring-required-approval-for-workflows-from-public-forks), or [enterprise](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account#configuring-required-approval-for-workflows-from-public-forks). Workflow runs that have been awaiting approval for more than 30 days are automatically deleted. diff --git a/translations/de-DE/content/actions/managing-workflow-runs/canceling-a-workflow.md b/translations/de-DE/content/actions/managing-workflow-runs/canceling-a-workflow.md index afcb7847cd..94074c0e90 100644 --- a/translations/de-DE/content/actions/managing-workflow-runs/canceling-a-workflow.md +++ b/translations/de-DE/content/actions/managing-workflow-runs/canceling-a-workflow.md @@ -10,7 +10,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.repositories.permissions-statement-write %} diff --git a/translations/de-DE/content/actions/managing-workflow-runs/deleting-a-workflow-run.md b/translations/de-DE/content/actions/managing-workflow-runs/deleting-a-workflow-run.md index 51c957ac88..726f537a16 100644 --- a/translations/de-DE/content/actions/managing-workflow-runs/deleting-a-workflow-run.md +++ b/translations/de-DE/content/actions/managing-workflow-runs/deleting-a-workflow-run.md @@ -10,7 +10,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.repositories.permissions-statement-write %} diff --git a/translations/de-DE/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md b/translations/de-DE/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md index d2c2705361..1761d37153 100644 --- a/translations/de-DE/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md +++ b/translations/de-DE/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md @@ -11,7 +11,6 @@ shortTitle: Disable & enable a workflow {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} Disabling a workflow allows you to stop a workflow from being triggered without having to delete the file from the repo. You can easily re-enable the workflow again on {% data variables.product.prodname_dotcom %}. diff --git a/translations/de-DE/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md b/translations/de-DE/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md index 3056863b11..4e2ab11cb1 100644 --- a/translations/de-DE/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md +++ b/translations/de-DE/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md @@ -11,7 +11,6 @@ shortTitle: Download workflow artifacts {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% ifversion fpt or ghes > 2.22 or ghae %} By default, {% data variables.product.product_name %} stores build logs and artifacts for 90 days, and you can customize this retention period, depending on the type of repository. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)."{% endif %} {% ifversion ghes = 2.22 %} {% data variables.product.product_name %} stores full build logs and artifacts for 90 days.{% endif %} diff --git a/translations/de-DE/content/actions/managing-workflow-runs/index.md b/translations/de-DE/content/actions/managing-workflow-runs/index.md index 140eccb9dd..24c7206c85 100644 --- a/translations/de-DE/content/actions/managing-workflow-runs/index.md +++ b/translations/de-DE/content/actions/managing-workflow-runs/index.md @@ -19,6 +19,7 @@ children: - /approving-workflow-runs-from-public-forks - /reviewing-deployments - /disabling-and-enabling-a-workflow + - /skipping-workflow-runs - /deleting-a-workflow-run - /downloading-workflow-artifacts - /removing-workflow-artifacts @@ -26,5 +27,3 @@ children: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% ifversion fpt or ghes > 3.0 or ghae %}{% endif %} diff --git a/translations/de-DE/content/actions/managing-workflow-runs/manually-running-a-workflow.md b/translations/de-DE/content/actions/managing-workflow-runs/manually-running-a-workflow.md index e2b527098f..3795362f81 100644 --- a/translations/de-DE/content/actions/managing-workflow-runs/manually-running-a-workflow.md +++ b/translations/de-DE/content/actions/managing-workflow-runs/manually-running-a-workflow.md @@ -11,7 +11,6 @@ shortTitle: Manually run a workflow {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Configuring a workflow to run manually diff --git a/translations/de-DE/content/actions/managing-workflow-runs/re-running-a-workflow.md b/translations/de-DE/content/actions/managing-workflow-runs/re-running-a-workflow.md index c0d2b16991..395186ab96 100644 --- a/translations/de-DE/content/actions/managing-workflow-runs/re-running-a-workflow.md +++ b/translations/de-DE/content/actions/managing-workflow-runs/re-running-a-workflow.md @@ -11,7 +11,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} Re-running a workflow uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (Git ref) of the original event that triggered the workflow run. You can re-run a workflow up to 30 days after the initial run. diff --git a/translations/de-DE/content/actions/managing-workflow-runs/removing-workflow-artifacts.md b/translations/de-DE/content/actions/managing-workflow-runs/removing-workflow-artifacts.md index cc449118da..87985cc357 100644 --- a/translations/de-DE/content/actions/managing-workflow-runs/removing-workflow-artifacts.md +++ b/translations/de-DE/content/actions/managing-workflow-runs/removing-workflow-artifacts.md @@ -11,7 +11,6 @@ shortTitle: Remove workflow artifacts {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Deleting an artifact diff --git a/translations/de-DE/content/actions/managing-workflow-runs/reviewing-deployments.md b/translations/de-DE/content/actions/managing-workflow-runs/reviewing-deployments.md index 5649b60107..a4fdb44853 100644 --- a/translations/de-DE/content/actions/managing-workflow-runs/reviewing-deployments.md +++ b/translations/de-DE/content/actions/managing-workflow-runs/reviewing-deployments.md @@ -8,13 +8,12 @@ versions: ghae: '*' --- -{% data reusables.actions.ae-beta %} ## About required reviews in workflows Jobs that reference an environment configured with required reviewers will wait for an approval before starting. While a job is awaiting approval, it has a status of "Waiting". If a job is not approved within 30 days, the workflow run will be automatically canceled. -For more information about environments and required approvals, see "[Environments](/actions/reference/environments)."{% ifversion fpt or ghae-next or ghes > 3.1 %} For information about how to review deployments with the REST API, see "[Workflow Runs](/rest/reference/actions#workflow-runs)."{% endif %} +For more information about environments and required approvals, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)."{% ifversion fpt or ghae-next or ghes > 3.1 %} For information about how to review deployments with the REST API, see "[Workflow Runs](/rest/reference/actions#workflow-runs)."{% endif %} ## Approving or rejecting a job diff --git a/translations/de-DE/content/actions/managing-workflow-runs/skipping-workflow-runs.md b/translations/de-DE/content/actions/managing-workflow-runs/skipping-workflow-runs.md new file mode 100644 index 0000000000..09cd92c4fe --- /dev/null +++ b/translations/de-DE/content/actions/managing-workflow-runs/skipping-workflow-runs.md @@ -0,0 +1,33 @@ +--- +title: Skipping workflow runs +intro: 'You can skip workflow runs triggered by the `push` and `pull_request` events by including a command in your commit message.' +product: '{% data reusables.gated-features.actions %}' +versions: + fpt: '*' + ghes: '>=3.0' + ghae: 'ghae-next' +shortTitle: Skip workflow runs +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +Workflows that would otherwise be triggered using `on: push` or `on: pull_request` won't be triggered if you add any of the following strings to the commit message in a push, or the HEAD commit of a pull request: + +* `[skip ci]` +* `[ci skip]` +* `[no ci]` +* `[skip actions]` +* `[actions skip]` + +Alternatively, you can end the commit message with two empty lines followed by either `skip-checks: true` or `skip-checks:true`. + +You won't be able to merge the pull request if your repository is configured to require specific checks to pass first. To allow the pull request to be merged you can push a new commit to the pull request without the skip instruction in the commit message. + +{% note %} + +**Note:** Skip instructions only apply to the `push` and `pull_request` events. For example, adding `[skip ci]` to a commit message won't stop a workflow that's triggered `on: pull_request_target` from running. + +{% endnote %} + +Skip instructions only apply to the workflow run(s) that would be triggered by the commit that contains the skip instructions. You can also disable a workflow from running. For more information, see "[Disabling and enabling a workflow](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)." \ No newline at end of file diff --git a/translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md b/translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md index 1c4b7d2f86..7f7c9a9226 100644 --- a/translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md +++ b/translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md @@ -19,7 +19,6 @@ shortTitle: Migrate from Azure Pipelines {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Einführung diff --git a/translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md b/translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md index 21cb8590cb..ee24a81c2c 100644 --- a/translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md +++ b/translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md @@ -19,7 +19,6 @@ shortTitle: Migrate from CircleCI {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Einführung diff --git a/translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md b/translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md index 700da5fe26..2aacd54daa 100644 --- a/translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md +++ b/translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md @@ -18,7 +18,6 @@ shortTitle: Migrate from GitLab CI/CD {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Einführung diff --git a/translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md b/translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md index 2228c47fd5..a32330a512 100644 --- a/translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md +++ b/translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md @@ -19,7 +19,6 @@ shortTitle: Migrate from Jenkins {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Einführung diff --git a/translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md index 13a73899b5..8f12b05085 100644 --- a/translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md +++ b/translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md @@ -19,7 +19,6 @@ shortTitle: Migrate from Travis CI {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Einführung diff --git a/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md b/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md index a8b5e57291..5e891e6b84 100644 --- a/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md +++ b/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md @@ -12,7 +12,6 @@ miniTocMaxHeadingLevel: 3 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Monitoring your workflows diff --git a/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md b/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md index cb9dba19f8..1078524f63 100644 --- a/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md +++ b/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md @@ -13,7 +13,6 @@ shortTitle: Add a status badge {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.repositories.actions-workflow-status-badge-intro %} diff --git a/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md b/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md index c3cbd1acda..69d794c173 100644 --- a/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md +++ b/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md @@ -12,7 +12,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} Diese zusätzlichen Protokolle werden aktiviert, indem Geheimnisse im Repository, die den Workflow enthalten, gesetzt werden, sodass die gleichen Berechtigungsanforderungen gelten: diff --git a/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/index.md b/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/index.md index bda6bc8ded..36ad81e817 100644 --- a/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/index.md +++ b/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/index.md @@ -17,9 +17,8 @@ children: - /viewing-job-execution-time - /using-workflow-run-logs - /enabling-debug-logging + - /notifications-for-workflow-runs --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% ifversion fpt or ghes > 3.0 or ghae %}{% endif %} diff --git a/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md b/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md new file mode 100644 index 0000000000..07362157a0 --- /dev/null +++ b/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md @@ -0,0 +1,15 @@ +--- +title: Benachrichtigungen für Workflow-Läufe +intro: You can subscribe to notifications about workflow runs that you trigger. +product: '{% data reusables.gated-features.actions %}' +versions: + fpt: '*' + ghes: '*' + ghae: '*' +shortTitle: Benachrichtigungen +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +{% data reusables.repositories.workflow-notifications %} diff --git a/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md b/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md index 9e777686f6..4561fca6cb 100644 --- a/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md +++ b/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md @@ -13,7 +13,6 @@ shortTitle: Use the visualization graph {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} diff --git a/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md b/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md index 7b765ad8f9..bea7f8073a 100644 --- a/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md +++ b/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md @@ -12,7 +12,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} Auf der Workflow-Lauf-Seite können sie sehen, ob ein Workflow-Lauf ausgeführt wird oder abgeschlossen ist. Sie müssen mit einem {% data variables.product.prodname_dotcom %}-Konto angemeldet sein, um Workflow-Informationen anzuzeigen, auch für öffentliche Repositories. Weitere Informationen finden Sie unter „[Zugriffsberechtigungen auf GitHub](/articles/access-permissions-on-github)“. diff --git a/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md b/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md index 68ff329eea..f2e72ab833 100644 --- a/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md +++ b/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md @@ -11,7 +11,6 @@ shortTitle: View job execution time {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} Billable job execution minutes are only shown for jobs run on private repositories that use {% data variables.product.prodname_dotcom %}-hosted runners. There are no billable minutes when using {% data variables.product.prodname_actions %} in public repositories or for jobs run on self-hosted runners. diff --git a/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md b/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md index 0d05d86294..d4043b2ae4 100644 --- a/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md +++ b/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md @@ -13,7 +13,6 @@ shortTitle: View workflow run history {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.repositories.permissions-statement-read %} diff --git a/translations/de-DE/content/actions/publishing-packages/about-packaging-with-github-actions.md b/translations/de-DE/content/actions/publishing-packages/about-packaging-with-github-actions.md index b98c504c85..5aea5db50e 100644 --- a/translations/de-DE/content/actions/publishing-packages/about-packaging-with-github-actions.md +++ b/translations/de-DE/content/actions/publishing-packages/about-packaging-with-github-actions.md @@ -18,7 +18,6 @@ shortTitle: Packaging with GitHub Actions {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.package_registry.about-packaging-and-actions %} diff --git a/translations/de-DE/content/actions/publishing-packages/publishing-docker-images.md b/translations/de-DE/content/actions/publishing-packages/publishing-docker-images.md index 726238537f..1becdbd478 100644 --- a/translations/de-DE/content/actions/publishing-packages/publishing-docker-images.md +++ b/translations/de-DE/content/actions/publishing-packages/publishing-docker-images.md @@ -18,7 +18,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Einführung diff --git a/translations/de-DE/content/actions/publishing-packages/publishing-java-packages-with-gradle.md b/translations/de-DE/content/actions/publishing-packages/publishing-java-packages-with-gradle.md index affd2aac79..30c3c0a117 100644 --- a/translations/de-DE/content/actions/publishing-packages/publishing-java-packages-with-gradle.md +++ b/translations/de-DE/content/actions/publishing-packages/publishing-java-packages-with-gradle.md @@ -20,7 +20,6 @@ shortTitle: Java packages with Gradle {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Einführung diff --git a/translations/de-DE/content/actions/publishing-packages/publishing-java-packages-with-maven.md b/translations/de-DE/content/actions/publishing-packages/publishing-java-packages-with-maven.md index 6d99fdfa4d..ebc66bc7ea 100644 --- a/translations/de-DE/content/actions/publishing-packages/publishing-java-packages-with-maven.md +++ b/translations/de-DE/content/actions/publishing-packages/publishing-java-packages-with-maven.md @@ -20,7 +20,6 @@ shortTitle: Java packages with Maven {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Einführung diff --git a/translations/de-DE/content/actions/publishing-packages/publishing-nodejs-packages.md b/translations/de-DE/content/actions/publishing-packages/publishing-nodejs-packages.md index 9461f2514c..ad5aa34746 100644 --- a/translations/de-DE/content/actions/publishing-packages/publishing-nodejs-packages.md +++ b/translations/de-DE/content/actions/publishing-packages/publishing-nodejs-packages.md @@ -21,7 +21,6 @@ shortTitle: Node.js packages {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Einführung diff --git a/translations/de-DE/content/actions/quickstart.md b/translations/de-DE/content/actions/quickstart.md index 13a97e6470..23131387a1 100644 --- a/translations/de-DE/content/actions/quickstart.md +++ b/translations/de-DE/content/actions/quickstart.md @@ -16,7 +16,6 @@ shortTitle: Schnellstart {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Einführung diff --git a/translations/de-DE/content/actions/security-guides/automatic-token-authentication.md b/translations/de-DE/content/actions/security-guides/automatic-token-authentication.md index 79ab18ee61..086b622b8b 100644 --- a/translations/de-DE/content/actions/security-guides/automatic-token-authentication.md +++ b/translations/de-DE/content/actions/security-guides/automatic-token-authentication.md @@ -16,7 +16,6 @@ shortTitle: Automatic token authentication {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Informationen zum `GITHUB_TOKEN`-Geheimnis diff --git a/translations/de-DE/content/actions/security-guides/encrypted-secrets.md b/translations/de-DE/content/actions/security-guides/encrypted-secrets.md index db36169328..81bc297f51 100644 --- a/translations/de-DE/content/actions/security-guides/encrypted-secrets.md +++ b/translations/de-DE/content/actions/security-guides/encrypted-secrets.md @@ -16,7 +16,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Informationen zu verschlüsselten Geheimnissen diff --git a/translations/de-DE/content/actions/security-guides/security-hardening-for-github-actions.md b/translations/de-DE/content/actions/security-guides/security-hardening-for-github-actions.md index 0cc873b612..bdbcaab7bc 100644 --- a/translations/de-DE/content/actions/security-guides/security-hardening-for-github-actions.md +++ b/translations/de-DE/content/actions/security-guides/security-hardening-for-github-actions.md @@ -18,7 +18,6 @@ miniTocMaxHeadingLevel: 3 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Übersicht @@ -48,7 +47,7 @@ To help prevent accidental disclosure, {% data variables.product.product_name %} - Rotate secrets periodically to reduce the window of time during which a compromised secret is valid. {% ifversion fpt or ghes > 3.0 or ghae %} - **Consider requiring review for access to secrets** - - You can use required reviewers to protect environment secrets. A workflow job cannot access environment secrets until approval is granted by a reviewer. For more information about storing secrets in environments or requiring reviews for environments, see "[Encrypted secrets](/actions/reference/encrypted-secrets)" and "[Environments](/actions/reference/environments)." + - You can use required reviewers to protect environment secrets. A workflow job cannot access environment secrets until approval is granted by a reviewer. For more information about storing secrets in environments or requiring reviews for environments, see "[Encrypted secrets](/actions/reference/encrypted-secrets)" and "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." {% endif %} ## Using `CODEOWNERS` to monitor changes @@ -183,6 +182,12 @@ You can help mitigate this risk by following these good practices: Although pinning to a commit SHA is the most secure option, specifying a tag is more convenient and is widely used. If you’d like to specify a tag, then be sure that you trust the action's creators. The ‘Verified creator’ badge on {% data variables.product.prodname_marketplace %} is a useful signal, as it indicates that the action was written by a team whose identity has been verified by {% data variables.product.prodname_dotcom %}. Note that there is risk to this approach even if you trust the author, because a tag can be moved or deleted if a bad actor gains access to the repository storing the action. +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## Reusing third-party workflows + +The same principles described above for using third-party actions also apply to using third-party workflows. You can help mitigate the risks associated with reusing workflows by following the same good practices outlined above. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." +{% endif %} + ## Potential impact of a compromised runner These sections consider some of the steps an attacker can take if they're able to run malicious commands on a {% data variables.product.prodname_actions %} runner. diff --git a/translations/de-DE/content/actions/using-containerized-services/about-service-containers.md b/translations/de-DE/content/actions/using-containerized-services/about-service-containers.md index 83e112b368..04d5a5bbc8 100644 --- a/translations/de-DE/content/actions/using-containerized-services/about-service-containers.md +++ b/translations/de-DE/content/actions/using-containerized-services/about-service-containers.md @@ -18,7 +18,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Informationen zu Service-Containern diff --git a/translations/de-DE/content/actions/using-containerized-services/creating-postgresql-service-containers.md b/translations/de-DE/content/actions/using-containerized-services/creating-postgresql-service-containers.md index 9b2189d0f4..3bc5ed94a3 100644 --- a/translations/de-DE/content/actions/using-containerized-services/creating-postgresql-service-containers.md +++ b/translations/de-DE/content/actions/using-containerized-services/creating-postgresql-service-containers.md @@ -19,7 +19,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Einführung diff --git a/translations/de-DE/content/actions/using-containerized-services/creating-redis-service-containers.md b/translations/de-DE/content/actions/using-containerized-services/creating-redis-service-containers.md index ad7db6340d..9e5e7d6773 100644 --- a/translations/de-DE/content/actions/using-containerized-services/creating-redis-service-containers.md +++ b/translations/de-DE/content/actions/using-containerized-services/creating-redis-service-containers.md @@ -19,7 +19,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Einführung diff --git a/translations/de-DE/content/actions/using-github-hosted-runners/about-ae-hosted-runners.md b/translations/de-DE/content/actions/using-github-hosted-runners/about-ae-hosted-runners.md index a1f21c6908..7a88aa2b44 100644 --- a/translations/de-DE/content/actions/using-github-hosted-runners/about-ae-hosted-runners.md +++ b/translations/de-DE/content/actions/using-github-hosted-runners/about-ae-hosted-runners.md @@ -6,23 +6,16 @@ versions: ghae: '*' --- - - - -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} ## About {% data variables.actions.hosted_runner %}s -An {% data variables.actions.hosted_runner %} is a virtual machine hosted by {% data variables.product.prodname_dotcom %} with the {% data variables.product.prodname_actions %} runner service installed. +An {% data variables.actions.hosted_runner %} is a virtual machine managed by {% data variables.product.prodname_dotcom %} with the {% data variables.product.prodname_actions %} runner service installed. {% data variables.actions.hosted_runner %}s are dedicated to your enterprise, and you can choose from a range of hardware and software options. By default, {% data variables.actions.hosted_runner %}s are fully managed and auto-scaled by {% data variables.product.company_short %} to maximize performance while minimizing costs.{% ifversion ghae-next %} You can optionally configure the parameters of this auto-scaling to reduce your cost even more.{% endif %} -{% data variables.product.prodname_ghe_managed %} lets you create and customize {% data variables.actions.hosted_runner %}s using Ubuntu or Windows images; you can select the size of machine you want and configure security hardened networking for them. {% data variables.actions.hosted_runner %}s are fully managed and auto-scaled by {% data variables.product.prodname_dotcom %}. +{% data variables.product.prodname_ghe_managed %} lets you create and customize {% data variables.actions.hosted_runner %}s using Ubuntu or Windows images; you can select the size of machine you want and optionally configure a fixed public IP range for your {% data variables.actions.hosted_runner %}s. Each workflow job is executed in a fresh instance of the {% data variables.actions.hosted_runner %}, and you can run workflows directly on the virtual machine or in a Docker container. All steps in the job execute in the same instance, allowing the actions in that job to share information using the {% data variables.actions.hosted_runner %}'s filesystem. -{% note %} -{% data variables.actions.hosted_runner %}s are the only runners available for {% data variables.product.prodname_ghe_managed %}, and self-hosted runners are not available. -{% endnote %} - To add {% data variables.actions.hosted_runner %}s to your organization or enterprise, see ["Adding {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/adding-ae-hosted-runners)." ## Pool assignments for {% data variables.actions.hosted_runner %}s @@ -35,11 +28,9 @@ During the {% data variables.actions.hosted_runner %} beta, you can manage your ## Billing -{% data variables.product.prodname_actions %} is currently in beta for {% data variables.product.prodname_ghe_managed %}. During this beta period, {% data variables.actions.hosted_runner %}s are not billed, and can be used for free. - Once the beta ends, billed usage will include the full uptime of active instances in your AE hosted runner sets. This includes: - Job time - minutes spent running Actions job. -- Management - minutes spent re-imaging machines and any idle time created as a result of desired auto-scale behavior. +- Management - minutes spent re-imaging machines{% ifversion ghae-next %} and any idle time created as a result of desired auto-scale behavior{% endif %}. Pricing will scale linearly with cores. For example, 4 cores will be twice the price of 2 cores. Windows VMs will be priced higher than Linux VMs. @@ -78,6 +69,14 @@ To get a list of IP address ranges that {% data variables.product.prodname_actio The list of {% data variables.product.prodname_actions %} IP addresses returned by the API is updated once a week. +{% ifversion ghae-next %} + +## Autoscaling + +Each pool of {% data variables.actions.hosted_runner %}s is fully managed by {% data variables.product.company_short %} to maximize performance while minimizing costs. Optionally, you can configure the autoscaling parameters for your enterprise by contacting {% data variables.contact.github_support %}. You can define the minimum number of idle runners and how long a runner should remain idle before being removed from the pool. Each pool can contain up to 600 runners. + +{% endif %} + ## Administrative privileges for {% data variables.actions.hosted_runner %}s The Linux virtual machines run using passwordless `sudo`. Wenn Sie Befehle ausführen oder Tools installieren müssen, die höhere Berechtigungen als der aktuelle Benutzer erfordern, können Sie `sudo` verwenden, ohne ein Passwort angeben zu müssen. Weitere Informationen findest Du im „[Sudo-Handbuch](https://www.sudo.ws/man/1.8.27/sudo.man.html)“. diff --git a/translations/de-DE/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/translations/de-DE/content/actions/using-github-hosted-runners/about-github-hosted-runners.md index eee1d1db5f..906c11fbf3 100644 --- a/translations/de-DE/content/actions/using-github-hosted-runners/about-github-hosted-runners.md +++ b/translations/de-DE/content/actions/using-github-hosted-runners/about-github-hosted-runners.md @@ -16,6 +16,7 @@ versions: shortTitle: GitHub-hosted runners --- +{% data reusables.actions.ae-hosted-runners-beta %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} diff --git a/translations/de-DE/content/actions/using-github-hosted-runners/adding-ae-hosted-runners.md b/translations/de-DE/content/actions/using-github-hosted-runners/adding-ae-hosted-runners.md index 164a4a82f9..c25120b5f8 100644 --- a/translations/de-DE/content/actions/using-github-hosted-runners/adding-ae-hosted-runners.md +++ b/translations/de-DE/content/actions/using-github-hosted-runners/adding-ae-hosted-runners.md @@ -5,7 +5,7 @@ versions: ghae: '*' --- -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} {% note %} @@ -19,7 +19,8 @@ versions: You can add {% data variables.actions.hosted_runner %}s that use the base Azure operating system images. To add {% data variables.actions.hosted_runner %}s to your organization or enterprise, contact {% data variables.product.prodname_dotcom %} support and have the following information ready: - Required operating system: Available options are listed at ["Software specifications](/actions/using-github-hosted-runners/about-ae-hosted-runners#software-specifications)." - - Choose a name for each pool of {% data variables.actions.hosted_runner %}s. These names are created as labels, allowing you to route your workflows to these runners. For more information, see ["Using {% data variables.actions.hosted_runner %}s in a workflow](/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow)." + - Choose a name for each pool of {% data variables.actions.hosted_runner %}s. These names are created as labels, allowing you to route your workflows to these runners. For more information, see ["Using {% data variables.actions.hosted_runner %}s in a workflow](/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow)."{% ifversion ghae-next %} +{% data reusables.actions.autoscaling-parameters %}{% endif %} - Where to add the {% data variables.actions.hosted_runner %}: Identify the names of the organizations and enterprises that will receive the runners. ## Adding an {% data variables.actions.hosted_runner %} with a custom image @@ -33,7 +34,8 @@ Once you've created a custom image using the above steps, contact {% data variab - Image name. - Version. - VM SKU for the new pool. - - Choose a name for each pool of {% data variables.actions.hosted_runner %}s. These names are created as labels, allowing you to route your workflows to these runners. For more information, see ["Using {% data variables.actions.hosted_runner %}s in a workflow](/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow)." + - Choose a name for each pool of {% data variables.actions.hosted_runner %}s. These names are created as labels, allowing you to route your workflows to these runners. For more information, see ["Using {% data variables.actions.hosted_runner %}s in a workflow](/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow)."{% ifversion ghae-next %} +{% data reusables.actions.autoscaling-parameters %}{% endif %} - Where to add the {% data variables.actions.hosted_runner %}: Identify the names of the organizations and enterprises that will receive the runners. ## Reviewing your {% data variables.actions.hosted_runner %}s diff --git a/translations/de-DE/content/actions/using-github-hosted-runners/creating-custom-images.md b/translations/de-DE/content/actions/using-github-hosted-runners/creating-custom-images.md index c8369a8e24..5dfff3138d 100644 --- a/translations/de-DE/content/actions/using-github-hosted-runners/creating-custom-images.md +++ b/translations/de-DE/content/actions/using-github-hosted-runners/creating-custom-images.md @@ -5,7 +5,7 @@ versions: ghae: '*' --- -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} ## Creating an {% data variables.actions.hosted_runner %} with a custom image diff --git a/translations/de-DE/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md b/translations/de-DE/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md index db23278023..3fd637a69f 100644 --- a/translations/de-DE/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md +++ b/translations/de-DE/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md @@ -11,6 +11,7 @@ topics: shortTitle: Customize runners --- +{% data reusables.actions.ae-hosted-runners-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} If you require additional software packages on {% data variables.product.prodname_dotcom %}-hosted runners, you can create a job that installs the packages as part of your workflow. diff --git a/translations/de-DE/content/actions/using-github-hosted-runners/index.md b/translations/de-DE/content/actions/using-github-hosted-runners/index.md index 440c898ae1..16a4af837c 100644 --- a/translations/de-DE/content/actions/using-github-hosted-runners/index.md +++ b/translations/de-DE/content/actions/using-github-hosted-runners/index.md @@ -17,5 +17,6 @@ children: shortTitle: Use GitHub-hosted runners --- +{% data reusables.actions.ae-hosted-runners-beta %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} diff --git a/translations/de-DE/content/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow.md b/translations/de-DE/content/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow.md index cc6c55711e..c011ba7285 100644 --- a/translations/de-DE/content/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow.md +++ b/translations/de-DE/content/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow.md @@ -6,7 +6,7 @@ versions: shortTitle: Use AE hosted runners --- -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} ## Using {% data variables.actions.hosted_runner %}s in a workflow diff --git a/translations/de-DE/content/actions/using-github-hosted-runners/using-groups-to-manage-access-to-ae-hosted-runners.md b/translations/de-DE/content/actions/using-github-hosted-runners/using-groups-to-manage-access-to-ae-hosted-runners.md index 8faf78c5c7..ea277daecd 100644 --- a/translations/de-DE/content/actions/using-github-hosted-runners/using-groups-to-manage-access-to-ae-hosted-runners.md +++ b/translations/de-DE/content/actions/using-github-hosted-runners/using-groups-to-manage-access-to-ae-hosted-runners.md @@ -6,7 +6,7 @@ versions: shortTitle: Manage AE runner groups --- -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} ## About {% data variables.actions.hosted_runner %} groups diff --git a/translations/de-DE/content/actions/using-github-hosted-runners/using-labels-with-ae-hosted-runners.md b/translations/de-DE/content/actions/using-github-hosted-runners/using-labels-with-ae-hosted-runners.md index 9ceb48f896..e474b49da3 100644 --- a/translations/de-DE/content/actions/using-github-hosted-runners/using-labels-with-ae-hosted-runners.md +++ b/translations/de-DE/content/actions/using-github-hosted-runners/using-labels-with-ae-hosted-runners.md @@ -6,7 +6,7 @@ versions: shortTitle: Label AE hosted runners --- -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} For information on how to use labels to route jobs to specific types of {% data variables.actions.hosted_runner %}s, see "[Using {% data variables.actions.hosted_runner %}s in a workflow](/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow)." diff --git a/translations/de-DE/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md b/translations/de-DE/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md index cc4c6369be..7d169e5c87 100644 --- a/translations/de-DE/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md +++ b/translations/de-DE/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md @@ -62,13 +62,13 @@ If you set up the {% data variables.product.prodname_codeql %} action sync tool, {% ifversion ghes = 2.22 %} To run {% data variables.product.prodname_code_scanning %} on {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_actions %}, the appropriate actions must be available locally. You can make the actions available in three ways. -- **Recommended**: You can use [{% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud) to automatically download actions from {% data variables.product.prodname_dotcom_the_website %}. The machine that hosts your instance must be able to access {% data variables.product.prodname_dotcom_the_website %}. This approach ensures that you get the latest software automatically. For more information, see "[Configuring {% data variables.product.prodname_github_connect %} to sync {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)." +- **Recommended**: You can use [{% data variables.product.prodname_github_connect %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud) to automatically download actions from {% data variables.product.prodname_dotcom_the_website %}. The machine that hosts your instance must be able to access {% data variables.product.prodname_dotcom_the_website %}. This approach ensures that you get the latest software automatically. For more information, see "[Configuring {% data variables.product.prodname_github_connect %} to sync {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)." - If you want to use the {% data variables.product.prodname_codeql_workflow %}, you can sync the repository from {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.prodname_ghe_server %}, by using the {% data variables.product.prodname_codeql %} Action sync tool available at [https://github.com/github/codeql-action-sync-tool](https://github.com/github/codeql-action-sync-tool/). You can use this tool regardless of whether {% data variables.product.product_location %} or your {% data variables.product.prodname_actions %} runners have access to the internet, as long as you can access both {% data variables.product.product_location %} and {% data variables.product.prodname_dotcom_the_website %} simultaneously on your computer. - You can create a local copy of an action's repository on your server, by cloning the {% data variables.product.prodname_dotcom_the_website %} repository that contains the action. For example, if you want to use the actions for {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}, you can create a repository in your instance called `github/codeql-action`, then clone the [repository](https://github.com/github/codeql-action) from {% data variables.product.prodname_dotcom_the_website %}, and then push that repository to your instance's `github/codeql-action` repository. You will also need to download any of the releases from the repository on {% data variables.product.prodname_dotcom_the_website %} and upload them to your instance's `github/codeql-action` repository as releases. {% endif %} ### Configuring {% data variables.product.prodname_github_connect %} to sync {% data variables.product.prodname_actions %} -1. If you want to download action workflows on demand from {% data variables.product.prodname_dotcom_the_website %}, you need to enable {% data variables.product.prodname_github_connect %}. For more information, see "[Enabling {% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud#enabling-github-connect)." +1. If you want to download action workflows on demand from {% data variables.product.prodname_dotcom_the_website %}, you need to enable {% data variables.product.prodname_github_connect %}. For more information, see "[Enabling {% data variables.product.prodname_github_connect %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud#enabling-github-connect)." 2. You'll also need to enable {% data variables.product.prodname_actions %} for {% data variables.product.product_location %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)." 3. The next step is to configure access to actions on {% data variables.product.prodname_dotcom_the_website %} using {% data variables.product.prodname_github_connect %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)." 4. Add a self-hosted runner to your repository, organization, or enterprise account. Weitere Informationen findest Du unter "[selbst-gehostete Runner hinzufügen](/actions/hosting-your-own-runners/adding-self-hosted-runners)." diff --git a/translations/de-DE/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md b/translations/de-DE/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md index 0c6eb53f81..42a08d1568 100644 --- a/translations/de-DE/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md +++ b/translations/de-DE/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md @@ -83,10 +83,14 @@ For example, you can enable any {% data variables.product.prodname_GH_advanced_s ```shell ghe-config app.secret-scanning.enabled true ``` - - To enable {% data variables.product.prodname_dependabot %}, enter the following command. - ```shell - {% ifversion ghes > 3.1 %}ghe-config app.dependency-graph.enabled true{% else %}ghe-config app.github.dependency-graph-enabled true{% endif %} + - To enable {% data variables.product.prodname_dependabot %}, enter the following {% ifversion ghes > 3.1 %}command{% else %}commands{% endif %}. + {% ifversion ghes > 3.1 %}```shell + ghe-config app.dependency-graph.enabled true ``` + {% else %}```shell + ghe-config app.github.dependency-graph-enabled true + ghe-config app.github.vulnerability-alerting-and-settings-enabled true + ```{% endif %} 2. Optionally, disable features for {% data variables.product.prodname_GH_advanced_security %}. - To disable {% data variables.product.prodname_code_scanning %}, enter the following commands. @@ -98,11 +102,14 @@ For example, you can enable any {% data variables.product.prodname_GH_advanced_s ```shell ghe-config app.secret-scanning.enabled false ``` - - To disable {% data variables.product.prodname_dependabot %}, enter the following command. - ```shell - {% ifversion ghes > 3.1 %}ghe-config app.dependency-graph.enabled false{% else %}ghe-config app.github.dependency-graph-enabled false{% endif %} + - To disable {% data variables.product.prodname_dependabot %}, enter the following {% ifversion ghes > 3.1 %}command{% else %}commands{% endif %}. + {% ifversion ghes > 3.1 %}```shell + ghe-config app.dependency-graph.enabled false ``` - + {% else %}```shell + ghe-config app.github.dependency-graph-enabled false + ghe-config app.github.vulnerability-alerting-and-settings-enabled false + ```{% endif %} 3. Apply the configuration. ```shell ghe-config-apply diff --git a/translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md b/translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md index c27aae760d..899c81d7f5 100644 --- a/translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md +++ b/translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md @@ -23,7 +23,7 @@ Wenn ein Proxyserver für {% data variables.product.product_location %} aktivier {% note %} -**Hinweis:** Um zwischen {% data variables.product.product_location %} und {% data variables.product.prodname_dotcom_the_website %} eine Verbindung herzustellen, muss Ihre Proxykonfiguration die Konnektivität zwischen `github.com` und `api.github.com` zulassen. Weitere Informationen finden Sie unter „[{% data variables.product.prodname_ghe_server %} mit {% data variables.product.prodname_dotcom_the_website %}](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/connecting-github-enterprise-server-to-github-com) verbinden“. +**Hinweis:** Um zwischen {% data variables.product.product_location %} und {% data variables.product.prodname_dotcom_the_website %} eine Verbindung herzustellen, muss Ihre Proxykonfiguration die Konnektivität zwischen `github.com` und `api.github.com` zulassen. For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_dotcom_the_website %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." {% endnote %} @@ -34,7 +34,7 @@ Wenn ein Proxyserver für {% data variables.product.product_location %} aktivier {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.privacy %} -4. Geben Sie unter **HTTP Proxy Server** (HTTP-Proxyserver) die URL Ihres Proxyservers ein. ![Feld zur Eingabe der HTTP-Proxyserver-URL](/assets/images/enterprise/management-console/http-proxy-field.png) +1. Geben Sie unter **HTTP Proxy Server** (HTTP-Proxyserver) die URL Ihres Proxyservers ein. ![Feld zur Eingabe der HTTP-Proxyserver-URL](/assets/images/enterprise/management-console/http-proxy-field.png) 5. Geben Sie optional unter **HTTP Proxy Exclusion** (HTTP-Proxyausschluss) die Hosts ein, für die kein Proxyzugriff erforderlich ist. Trennen Sie dabei die Hosts durch Kommas voneinander. To exclude all hosts in a domain from requiring proxy access, you can use `.` as a wildcard prefix. For example: `.octo-org.tentacle` ![Feld zur Eingabe von HTTP-Proxyausschlüssen](/assets/images/enterprise/management-console/http-proxy-exclusion-field.png) diff --git a/translations/de-DE/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md index b75e79bb8c..97f1aabe87 100644 --- a/translations/de-DE/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md +++ b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md @@ -351,18 +351,6 @@ stop/waiting - ghe-replica-mode ``` -{% tip %} - -Die von diesem Befehl zurückgegebenen Dienstnamen können mit „[`systemctl`](https://www.freedesktop.org/software/systemd/man/systemctl.html)“-Befehlen verwendet werden, um diese Dienste bei Bedarf zu beenden, zu starten oder erneut zu starten. Ein Beispiel: - -```shell -$ sudo systemctl restart github-resqued -``` - -Das Beenden von Diensten führt zu Ausfallzeiten Ihrer Installation, daher sollten Sie sich an {% data variables.contact.contact_ent_support %} wenden, bevor Sie einen Dienst beenden oder neu starten. - -{% endtip %} - ### ghe-set-password Mit `ghe-set-password` können Sie ein neues Passwort festlegen, um sich bei der [{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-management-console) zu authentifizieren. @@ -808,7 +796,7 @@ $ ssh -p 122 admin@hostname -- 'ghe-update-check' ### ghe-license-usage -Dieses Dienstprogramm exportiert eine Liste von Benutzern der Installation im JSON-Format. Wenn Deine Instanz mit der {% data variables.product.prodname_ghe_cloud %} verbunden ist, verwendet der {% data variables.product.prodname_ghe_server %} diese Informationen, um Lizenzinformationen an die {% data variables.product.prodname_ghe_cloud %} zu melden. Weitere Informationen findest Du unter „[{% data variables.product.prodname_ghe_server %} mit {% data variables.product.prodname_ghe_cloud %} verbinden](/enterprise/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud).“ +Dieses Dienstprogramm exportiert eine Liste von Benutzern der Installation im JSON-Format. Wenn Deine Instanz mit der {% data variables.product.prodname_ghe_cloud %} verbunden ist, verwendet der {% data variables.product.prodname_ghe_server %} diese Informationen, um Lizenzinformationen an die {% data variables.product.prodname_ghe_cloud %} zu melden. For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %} ](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." Standardmäßig wird die Liste der Benutzer in der resultierenden JSON-Datei verschlüsselt. Verwenden Sie das Flag `-h`, um weitere Optionen anzuzeigen. diff --git a/translations/de-DE/content/admin/configuration/index.md b/translations/de-DE/content/admin/configuration/index.md index 5b2cfee3b4..c8181bf7f7 100644 --- a/translations/de-DE/content/admin/configuration/index.md +++ b/translations/de-DE/content/admin/configuration/index.md @@ -12,7 +12,7 @@ topics: children: - /configuring-your-enterprise - /configuring-network-settings - - /managing-connections-between-github-enterprise-server-and-github-enterprise-cloud + - /managing-connections-between-your-enterprise-accounts --- {% ifversion ghes %} diff --git a/translations/de-DE/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md b/translations/de-DE/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md new file mode 100644 index 0000000000..a41ae1b0aa --- /dev/null +++ b/translations/de-DE/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md @@ -0,0 +1,83 @@ +--- +title: Connecting your enterprise account to GitHub Enterprise Cloud +shortTitle: Connect enterprise accounts +intro: 'Nach der Aktivierung von {% data variables.product.prodname_github_connect %} können Sie bestimmte Features und Workflows zwischen {% data variables.product.product_location %} und {% data variables.product.prodname_ghe_cloud %} freigeben.' +redirect_from: + - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-to-github-com/ + - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-server-to-github-com + - /enterprise/admin/developer-workflow/connecting-github-enterprise-server-to-githubcom/ + - /enterprise/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud + - /enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud + - /admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud +permissions: 'Enterprise owners who are also owners of a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable {% data variables.product.prodname_github_connect %}.' +versions: + ghes: '*' + ghae: next +type: how_to +topics: + - Enterprise + - GitHub Connect + - Infrastructure + - Networking +--- + +{% data reusables.github-connect.beta %} + +## Informationen zu {% data variables.product.prodname_github_connect %} + +Zum Aktivieren von {% data variables.product.prodname_github_connect %} musst Du die Verbindung sowohl in {% data variables.product.product_location %} als auch in Deiner Organisation oder Deinem Unternehmenskonto in der {% data variables.product.prodname_ghe_cloud %} konfigurieren. + +{% ifversion ghes %} +Zum Konfigurieren einer Verbindung muss Ihre Proxykonfiguration die Konnektivität mit `github.com` und `api.github.com` zulassen. Weitere Informationen finden Sie unter „[Ausgehenden Webproxyserver konfigurieren](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-an-outbound-web-proxy-server)“. +{% endif %} + +Nach der Aktivierung von {% data variables.product.prodname_github_connect %} können Sie Features, beispielsweise die gemeinsame Suche und einheitliche Beiträge, aktivieren. For more information about all of the features available, see "[Managing connections between your enterprise accounts](/admin/configuration/managing-connections-between-your-enterprise-accounts)." + +Wenn Sie zwischen {% data variables.product.product_location %} und {% data variables.product.prodname_ghe_cloud %} eine Verbindung herstellen, werden in einem Datensatz auf {% data variables.product.prodname_dotcom_the_website %} Informationen zur Verbindung gespeichert. +{% ifversion ghes %} +- Der Teil des öffentlichen Schlüssels Ihrer {% data variables.product.prodname_ghe_server %}-Lizenz +- Ein Hash Ihrer {% data variables.product.prodname_ghe_server %}-Lizenz +- Der Kundenname auf Ihrer {% data variables.product.prodname_ghe_server %}-Lizenz +- The version of {% data variables.product.product_location_enterprise %}{% endif %} +- The hostname of your {% data variables.product.product_name %} instance +- Die Organisation oder das Unternehmenskonto auf {% data variables.product.prodname_dotcom_the_website %}, die bzw. das mit {% data variables.product.product_location %} verbunden ist +- Das Authentifizierungstoken, das von {% data variables.product.product_location %} verwendet wird, um Anforderungen an {% data variables.product.prodname_dotcom_the_website %} zu senden. + +Wenn Du {% data variables.product.prodname_github_connect %} aktivierst, wird zudem eine {% data variables.product.prodname_github_app %} erstellt, die Deiner Organisation oder Deinem Unternehmenskonto in der {% data variables.product.prodname_ghe_cloud %} gehört. {% data variables.product.product_name %} verwendet die Anmeldeinformationen der {% data variables.product.prodname_github_app %}, um Anforderungen an {% data variables.product.prodname_dotcom_the_website %} zu senden. +{% ifversion ghes %} +{% data variables.product.prodname_ghe_server %} speichert die Anmeldeinformationen der {% data variables.product.prodname_github_app %}. Diese Anmeldeinformationen werden mit Hochverfügbarkeits- oder Clustering-Umgebungen repliziert und in von {% data variables.product.prodname_enterprise_backup_utilities %} erstellten Backups, einschließlich Snapshots, gespeichert. +- Ein Authentifizierungstoken, das eine Stunde lang gültig ist +- Ein privater Schlüssel, der zum Generieren eines neuen Authentifizierungstokens verwendet wird +{% endif %} + +Wenn {% data variables.product.prodname_github_connect %} aktiviert wird, können {% data variables.product.prodname_dotcom_the_website %}-Benutzer keine Änderungen an {% data variables.product.product_name %} vornehmen. + +For more information about managing enterprise accounts using the GraphQL API, see "[Enterprise accounts](/graphql/guides/managing-enterprise-accounts)." +## {% data variables.product.prodname_github_connect %} aktivieren + +{% ifversion ghes %} +1. Melden Sie sich bei {% data variables.product.product_location %} und {% data variables.product.prodname_dotcom_the_website %} an. +{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %}{% else %} +1. Melden Sie sich bei {% data variables.product.product_location %} und {% data variables.product.prodname_dotcom_the_website %} an. +{% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %} +1. Under "{% data variables.product.prodname_github_connect %} is not enabled yet", click **Enable {% data variables.product.prodname_github_connect %}**. By clicking **Enable {% data variables.product.prodname_github_connect %}**, you agree to the "{% data variables.product.prodname_dotcom %} Terms for Additional Products and Features." +{% ifversion ghes %} +![Enable GitHub Connect button](/assets/images/enterprise/business-accounts/enable-github-connect-button.png){% else %} +![Enable GitHub Connect button](/assets/images/enterprise/github-ae/enable-github-connect-button.png) +{% endif %} +1. Klicken Sie neben dem Enterprise-Konto oder der Organisation, das bzw. die Sie verbinden möchten, auf **Connect** (Verbinden). ![Schaltfläche „Connect“ (Verbinden) neben einem Enterprise-Konto oder Geschäft](/assets/images/enterprise/business-accounts/choose-enterprise-or-org-connect.png) + +## Disconnecting a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account from your enterprise account + +Wenn Sie die Verbindung zur {% data variables.product.prodname_ghe_cloud %} trennen, wird die {% data variables.product.prodname_github_connect %} {% data variables.product.prodname_github_app %} aus Ihrem Enterprise-Konto oder Ihrer Organisation gelöscht. Zudem werden die auf {% data variables.product.product_location %} gespeicherten Anmeldeinformationen gelöscht. + +{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %} +1. Klicken Sie neben dem Enterprise-Konto oder der Organisation, das bzw. die Sie trennen möchten, auf **Disable {% data variables.product.prodname_github_connect %}** ({% data variables.product.prodname_github_connect %} deaktivieren). +{% ifversion ghes %} + ![Schaltfläche „Disable GitHub Connect“ (GitHub Connect deaktivieren) neben dem Namen eines Enterprise-Kontos oder einer Organisation](/assets/images/enterprise/business-accounts/disable-github-connect-button.png) +1. Lesen Sie Informationen zur Trennung, und klicken Sie auf **Disable {% data variables.product.prodname_github_connect %}** ({% data variables.product.prodname_github_connect %} deaktivieren). ![Modalfenster mit Warnhinweisen zur Trennung und Schaltfläche zur Bestätigung](/assets/images/enterprise/business-accounts/confirm-disable-github-connect.png) +{% else %} + ![Schaltfläche „Disable GitHub Connect“ (GitHub Connect deaktivieren) neben dem Namen eines Enterprise-Kontos oder einer Organisation](/assets/images/enterprise/github-ae/disable-github-connect-button.png) +1. Lesen Sie Informationen zur Trennung, und klicken Sie auf **Disable {% data variables.product.prodname_github_connect %}** ({% data variables.product.prodname_github_connect %} deaktivieren). ![Modalfenster mit Warnhinweisen zur Trennung und Schaltfläche zur Bestätigung](/assets/images/enterprise/github-ae/confirm-disable-github-connect.png) +{% endif %} diff --git a/translations/de-DE/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md b/translations/de-DE/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md new file mode 100644 index 0000000000..b111990a6d --- /dev/null +++ b/translations/de-DE/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md @@ -0,0 +1,97 @@ +--- +title: Enabling alerts for vulnerable dependencies on GitHub Enterprise Server +intro: 'You can connect {% data variables.product.product_location %} to {% data variables.product.prodname_ghe_cloud %} and enable the dependency graph and {% ifversion ghes %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts in repositories in your instance.' +shortTitle: Enable alerts for dependencies +miniTocMaxHeadingLevel: 3 +redirect_from: + - /enterprise/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /enterprise/admin/configuration/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /enterprise/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server +permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable the dependency graph and {% data variables.product.prodname_dependabot %} alerts on {% data variables.product.prodname_ghe_server %}.' +versions: + ghes: '*' +type: how_to +topics: + - Enterprise + - Security + - Dependency graph + - Dependabot +--- + +## About alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %} + +To identify vulnerable dependencies in your repository and receive alerts about vulnerabilities, you need to enable two security features: +- The dependency graph +- {% data variables.product.prodname_dependabot %} alerts + +For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" and "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." + +{% data reusables.repositories.tracks-vulnerabilities %} + +You can connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}, then sync vulnerability data to your instance and generate {% data variables.product.prodname_dependabot_alerts %} in repositories with a vulnerable dependency. + +After connecting {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %} and enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies, vulnerability data is synced from {% data variables.product.prodname_dotcom_the_website %} to your instance once every hour. Sie können die Schwachstellendaten auch jederzeit manuell synchronisieren. Es werden weder Code noch Informationen zu Code von {% data variables.product.product_location %} auf {% data variables.product.prodname_dotcom_the_website %} hochgeladen. + +When {% data variables.product.product_location %} receives information about a vulnerability, it will identify repositories in your instance that use the affected version of the dependency and generate {% data variables.product.prodname_dependabot_alerts %}. You can customize how you receive {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies/#configuring-notifications-for-dependabot-alerts)." + +Before enabling the dependency graph and {% ifversion ghes > 2.21 %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts for vulnerable dependencies on {% data variables.product.product_location %}, you must connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." + +## Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} on GitHub Enterprise Server + +For {% data variables.product.product_location %} to generate {% data variables.product.prodname_dependabot_alerts %} whenever vulnerabilities are detected on your repositories: +- You must connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}. Weitere Informationen finden Sie unter „[{% data variables.product.prodname_ghe_server %} mit {% data variables.product.prodname_ghe_cloud %} verbinden](/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)“. +- You must enable the dependency graph. + +{% ifversion ghes > 3.1 %} +You can enable the dependency graph via the {% data variables.enterprise.management_console %} or the administrative shell. We recommend you follow the {% data variables.enterprise.management_console %} route unless {% data variables.product.product_location %} uses clustering. + +### Enabling the dependency graph via the {% data variables.enterprise.management_console %} +{% endif %}{% ifversion ghes > 3.1 %} +{% data reusables.enterprise_site_admin_settings.sign-in %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.advanced-security-tab %} +1. Under "Security," click **Dependency graph**. ![Checkbox to enable or disable the dependency graph](/assets/images/enterprise/3.2/management-console/enable-dependency-graph-checkbox.png) +{% data reusables.enterprise_management_console.save-settings %} +1. Klicke auf **Visit your instance** (Instanz aufrufen). + +### Enabling the dependency graph via the administrative shell +{% else %} +### Enabling the dependency graph +{% endif %} +{% data reusables.enterprise_site_admin_settings.sign-in %} +1. In the administrative shell, enable the dependency graph on {% data variables.product.product_location %}: + ``` shell + $ {% ifversion ghes > 3.1 %}ghe-config app.dependency-graph.enabled true{% else %}ghe-config app.github.dependency-graph-enabled true{% endif %} + ``` + {% note %} + + **Note**: For more information about enabling access to the administrative shell via SSH, see "[Accessing the administrative shell (SSH)](/enterprise/{{ currentVersion }}/admin/configuration/accessing-the-administrative-shell-ssh)." + + {% endnote %} +1. Apply the configuration. + ```shell + $ ghe-config-apply + ``` +1. Kehren Sie zu {% data variables.product.prodname_ghe_server %} zurück. + +### {% data variables.product.prodname_dependabot_alerts %} aktivieren + +Before enabling {% data variables.product.prodname_dependabot_alerts %} for your instance, you need to enable the dependency graph. For more information, see above. + +{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %} +1. Under "Repositories can be scanned for vulnerabilities", use the drop-down menu and select **Enabled without notifications**. Optionally, to enable alerts with notifications, select **Enabled with notifications**. ![Dropdownmenü zum Aktivieren der Überprüfung von Repositorys auf Schwachstellen](/assets/images/enterprise/site-admin-settings/enable-vulnerability-scanning-in-repositories.png) + {% note %} + + We recommend configuring {% data variables.product.prodname_dependabot_alerts %} without notifications for the first few days to avoid an overload of emails. After a few days, you can enable notifications to receive {% data variables.product.prodname_dependabot_alerts %} as usual. + + {% endnote %} +## Angreifbare Abhängigkeiten auf {% data variables.product.prodname_ghe_server %} anzeigen + +Sie können alle Schwachstellen in {% data variables.product.product_location %} anzeigen und Schwachstellendaten von {% data variables.product.prodname_dotcom_the_website %} manuell synchronisieren, um die Liste zu aktualisieren. + +{% data reusables.enterprise_site_admin_settings.access-settings %} +2. Klicken Sie auf der linken Seitenleiste auf **Vulnerabilities** (Schwachstellen). ![Registerkarte „Vulnerabilities“ (Schwachstellen) auf der Seitenleiste für Websiteadministratoren](/assets/images/enterprise/business-accounts/vulnerabilities-tab.png) +3. Klicken Sie zum Synchronisieren von Schwachstellendaten auf **Sync Vulnerabilities now** (Schwachstellen jetzt synchronisieren). ![Schaltfläche „Sync vulnerabilities now“ (Schwachstellen jetzt synchronisieren)](/assets/images/enterprise/site-admin-settings/sync-vulnerabilities-button.png) diff --git a/translations/de-DE/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md b/translations/de-DE/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md new file mode 100644 index 0000000000..5364525424 --- /dev/null +++ b/translations/de-DE/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md @@ -0,0 +1,31 @@ +--- +title: Automatische Synchronisierung von Benutzerlizenzen zwischen GitHub Enterprise Server und GitHub Enterprise Cloud aktivieren +intro: 'Sie können zwischen {% data variables.product.product_location_enterprise %} und {% data variables.product.prodname_ghe_cloud %} eine Verbindung herstellen und festlegen, dass {% data variables.product.prodname_ghe_server %} Informationen zu Benutzerlizenzen auf Ihr Enterprise-Konto auf {% data variables.product.prodname_dotcom_the_website %} hochladen kann.' +redirect_from: + - /enterprise/admin/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud + - /enterprise/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud + - /admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud +permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable automatic user license synchronization.' +versions: + ghes: '*' +type: how_to +topics: + - Enterprise + - GitHub Connect + - Licensing +shortTitle: Enable user license sync +--- + +## Informationen zur Lizenzsynchronisierung + +After you enable license synchronization, you'll be able to view license usage for your entire enterprise account, across {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}. {% data variables.product.prodname_github_connect %} syncs license between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %} weekly. For more information, see "[Managing your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise)." + +Darüber hinaus können Sie Informationen zu {% data variables.product.prodname_ghe_server %}-Benutzerlizenzen manuell auf {% data variables.product.prodname_ghe_cloud %} hochladen. For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." + +## Lizenzsynchronisierung aktivieren + +Vor der Aktivierung der Lizenzsynchronisierung auf {% data variables.product.product_location_enterprise %} müssen Sie zwischen {% data variables.product.product_location_enterprise %} und {% data variables.product.prodname_dotcom_the_website %} eine Verbindung herstellen. For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." + +{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %} +1. Verwenden Sie unter „Server can sync user license count and usage“ (Server kann Anzahl und Nutzung der Benutzerlizenzen synchronisieren) das Dropdownmenü, und wählen Sie **Enabled** (Aktiviert) aus. ![Dropdownmenü zum Aktivieren der automatischen Synchronisierung von Benutzerlizenzen](/assets/images/enterprise/site-admin-settings/enable-user-license-drop-down.png) diff --git a/translations/de-DE/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md b/translations/de-DE/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md new file mode 100644 index 0000000000..e03817714d --- /dev/null +++ b/translations/de-DE/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md @@ -0,0 +1,46 @@ +--- +title: Enabling unified contributions between your enterprise account and GitHub.com +shortTitle: Enable unified contributions +intro: 'Nach der Aktivierung von {% data variables.product.prodname_github_connect %} können Sie festlegen, dass {% data variables.product.prodname_ghe_cloud %}-Mitglieder ihre Arbeit auf {% data variables.product.product_name %} hervorheben können, indem sie die Beitragsanzahlen an ihre {% data variables.product.prodname_dotcom_the_website %}-Profile senden.' +redirect_from: + - /enterprise/admin/guides/developer-workflow/enabling-unified-contributions-between-github-enterprise-and-github-com/ + - /enterprise/admin/guides/developer-workflow/enabling-unified-contributions-between-github-enterprise-server-and-github-com/ + - /enterprise/admin/developer-workflow/enabling-unified-contributions-between-github-enterprise-server-and-githubcom/ + - /enterprise/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom + - /enterprise/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom + - /admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-unified-contributions-between-github-enterprise-server-and-githubcom +permissions: 'Enterprise owners who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable unified contributions between {% data variables.product.product_location %} and {% data variables.product.prodname_dotcom_the_website %}.' +versions: + ghes: '*' + ghae: next +type: how_to +topics: + - Enterprise + - GitHub Connect +--- + +{% data reusables.github-connect.beta %} + +As an enterprise owner, you can allow end users to send anonymized contribution counts for their work from {% data variables.product.product_location %} to their {% data variables.product.prodname_dotcom_the_website %} contribution graph. + +After you enable {% data variables.product.prodname_github_connect %} and enable {% data variables.product.prodname_unified_contributions %} in both environments, end users on your enterprise account can connect to their {% data variables.product.prodname_dotcom_the_website %} accounts and send contribution counts from {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.github-connect.sync-frequency %} 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)." + +If the enterprise owner disables the functionality or developers opt out of the connection, the {% data variables.product.product_name %} contribution counts will be deleted on {% data variables.product.prodname_dotcom_the_website %}. Wenn der Entwickler seine Profile nach ihrer Deaktivierung erneut verbindet, werden die Beitragsanzahlen für die letzten 90 Tage wiederhergestellt. + +{% data variables.product.product_name %} sendet **nur** nur die Beitragsanzahl und -quelle ({% data variables.product.product_name %}) für verbundene Benutzer. Es werden weder Informationen zum Beitrag noch dazu gesendet, wie er zustande kam. + +Vor der Aktivierung von {% data variables.product.prodname_unified_contributions %} auf {% data variables.product.product_location %} müssen Sie {% data variables.product.product_location %} mit {% data variables.product.prodname_dotcom_the_website %} verbinden. For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_dotcom_the_website %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." + +{% ifversion ghes %} +{% data reusables.github-connect.access-dotcom-and-enterprise %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.business %} +{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %}{% else %} +1. Melden Sie sich bei {% data variables.product.product_location %} und {% data variables.product.prodname_dotcom_the_website %} an. +{% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %} +1. Klicken Sie unter „Users can share contribution counts to {% data variables.product.prodname_dotcom_the_website %}“ (Benutzer können ihre Beitragsanzahlen auf {% data variables.product.prodname_dotcom_the_website %} freigeben) auf **Request access** (Zugriff anfordern). ![Request access to unified contributions option](/assets/images/enterprise/site-admin-settings/dotcom-ghe-connection-request-access.png){% ifversion ghes %} +2. Weitere Anweisungen erhalten Sie, wenn Sie sich bei der {% data variables.product.prodname_ghe_server %}-Website [anmelden](https://enterprise.github.com/login). + +When you request access, we may redirect you to the {% data variables.product.prodname_ghe_server %} site to check your current terms of service. +{% endif %} diff --git a/translations/de-DE/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md b/translations/de-DE/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md new file mode 100644 index 0000000000..3d0a98f6e9 --- /dev/null +++ b/translations/de-DE/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md @@ -0,0 +1,44 @@ +--- +title: Enabling unified search between your enterprise account and GitHub.com +shortTitle: Enable unified search +intro: 'After enabling {% data variables.product.prodname_github_connect %}, you can allow search of {% data variables.product.prodname_dotcom_the_website %} for members of your enterprise on {% data variables.product.product_name %}.' +redirect_from: + - /enterprise/admin/guides/developer-workflow/enabling-unified-search-between-github-enterprise-and-github-com/ + - /enterprise/admin/guides/developer-workflow/enabling-unified-search-between-github-enterprise-server-and-github-com/ + - /enterprise/admin/developer-workflow/enabling-unified-search-between-github-enterprise-server-and-githubcom/ + - /enterprise/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom + - /enterprise/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom + - /admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-unified-search-between-github-enterprise-server-and-githubcom +permissions: 'Enterprise owners who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable unified search between {% data variables.product.product_name %} and {% data variables.product.prodname_dotcom_the_website %}.' +versions: + ghes: '*' + ghae: next +topics: + - Enterprise + - GitHub Connect + - GitHub search +--- + +{% data reusables.github-connect.beta %} + +When you enable unified search, users can view search results from public and private content on {% data variables.product.prodname_dotcom_the_website %} when searching from {% data variables.product.product_location %}{% ifversion ghae %} on {% data variables.product.prodname_ghe_managed %}{% endif %}. + +Benutzer können auf {% data variables.product.prodname_dotcom_the_website %} nicht nach {% data variables.product.product_location %} suchen, selbst wenn sie auf beide Umgebungen zugreifen können. Benutzer können nur auf die privaten Repositorys zugreifen, für die Sie {% data variables.product.prodname_unified_search %} aktiviert haben und auf die sie in den verbundenen {% data variables.product.prodname_ghe_cloud %}-Organisationen zugreifen können. For more information, see "[About searching on {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github/#searching-across-github-enterprise-and-githubcom-simultaneously)" and "[Enabling private {% data variables.product.prodname_dotcom_the_website %} repository search in your enterprise account](/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment)." + +Bei der Suche über die REST und GraphQL-APIs sind die {% data variables.product.prodname_dotcom_the_website %}-Suchergebnisse nicht enthalten. Die erweiterte Suche und die Suche nach Wikis in {% data variables.product.prodname_dotcom_the_website %} werden nicht unterstützt. + +{% ifversion ghes %} +{% data reusables.github-connect.access-dotcom-and-enterprise %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.business %} +{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %}{% else %} +1. Melden Sie sich bei {% data variables.product.product_location %} und {% data variables.product.prodname_dotcom_the_website %} an. +{% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %} +1. Verwenden Sie unter „Users can search {% data variables.product.prodname_dotcom_the_website %}“ (Benutzer können {% data variables.product.prodname_dotcom_the_website %} durchsuchen) das Dropdownmenü, und klicken Sie auf **Enabled** (Aktiviert). ![Option zum Aktivieren der Suche im Dropdownmenü zum Durchsuchen von GitHub.com](/assets/images/enterprise/site-admin-settings/github-dotcom-enable-search.png) +1. Verwenden Sie optional unter „Users can search private repositories on {% data variables.product.prodname_dotcom_the_website %}“ (Benutzer können private Repositorys auf {% data variables.product.prodname_dotcom_the_website %} durchsuchen) das Dropdownmenü, und klicken Sie auf **Enabled** (Aktiviert). ![Option zum Aktivieren der Suche nach privaten Repositorys im Dropdownmenü zum Durchsuchen von GitHub.com](/assets/images/enterprise/site-admin-settings/enable-private-search.png) + +## Weiterführende Informationen + +- "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)" + diff --git a/translations/de-DE/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md b/translations/de-DE/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md new file mode 100644 index 0000000000..77cecba94e --- /dev/null +++ b/translations/de-DE/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md @@ -0,0 +1,25 @@ +--- +title: Managing connections between your enterprise accounts +intro: 'Mit {% data variables.product.prodname_github_connect %} können Sie bestimmte Features und Daten zwischen {% data variables.product.product_location %} und Ihrer {% data variables.product.prodname_ghe_cloud %}-Organisation oder Ihrem -Enterprise-Konto auf {% data variables.product.prodname_dotcom_the_website %} freigeben.' +redirect_from: + - /enterprise/admin/developer-workflow/connecting-github-enterprise-to-github-com + - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-and-github-com/ + - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-server-and-github-com/ + - /enterprise/admin/developer-workflow/connecting-github-enterprise-server-and-githubcom/ + - /enterprise/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud + - /enterprise/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud +versions: + ghes: '*' + ghae: next +topics: + - Enterprise +children: + - /connecting-your-enterprise-account-to-github-enterprise-cloud + - /enabling-unified-search-between-your-enterprise-account-and-githubcom + - /enabling-unified-contributions-between-your-enterprise-account-and-githubcom + - /enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud +shortTitle: Connect enterprise accounts +--- + diff --git a/translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md index 9c2d26ebc0..dd09d59f40 100644 --- a/translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md +++ b/translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md @@ -37,19 +37,46 @@ This article explains how site administrators can configure {% data variables.pr {% endif %} +{%- ifversion ghes < 3.2 %} + The CPU and memory resources available to {% data variables.product.product_location %} determine the maximum job throughput for {% data variables.product.prodname_actions %}. Internal testing at {% data variables.product.company_short %} demonstrated the following maximum throughput for {% data variables.product.prodname_ghe_server %} instances with a range of CPU and memory configurations. You may see different throughput depending on the overall levels of activity on your instance. +{%- endif %} + +{%- ifversion ghes > 3.1 %} + +The CPU and memory resources available to {% data variables.product.product_location %} determine the number of jobs that can be run concurrently without performance loss. + +The peak quantity of concurrent jobs running without performance loss depends on such factors as job duration, artifact usage, number of repositories running Actions, and how much other work your instance is doing not related to Actions. Internal testing at GitHub demonstrated the following performance targets for GitHub Enterprise Server on a range of CPU and memory configurations: + +{% endif %} + +{%- ifversion ghes < 3.2 %} + | vCPUs | Arbeitsspeicher | Maximum job throughput | |:----- |:--------------- |:---------------------- | -| | | | -{%- ifversion ghes > 3.1 %} -| 4 | 32 GB | Demo or light testing | | 8 | 64 GB | 30 jobs | | 16 | 128 GB | 60 jobs | | 32 | 256 GB | 120 jobs | | 64 | 512 GB | 160 jobs | -{%- else ifversion ghes < 3.2 %} -| 4 | 32 GB | Demo or light testing | | 8 | 64 GB | 25 jobs | | 16 | 160 GB | 35 jobs | | 32 | 256 GB | 100 jobs | +| 4 | 32 GB | Demo or light testing | +| 8 | 64 GB | 25 jobs | +| 16 | 160 GB | 35 jobs | +| 32 | 256 GB | 100 jobs | + {%- endif %} +{%- ifversion ghes > 3.1 %} + +| vCPUs | Arbeitsspeicher | Maximum Concurrency* | +|:----- |:--------------- |:-------------------- | +| 32 | 128 GB | 1500 jobs | +| 64 | 256 GB | 1900 jobs | +| 96 | 384 GB | 2200 jobs | + +*Maximum concurrency was measured using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. You may experience different performance depending on the overall levels of activity on your instance. + +{%- endif %} + + If you {% ifversion ghes = 2.22 %}enabled the beta of{% else %}plan to enable{% endif %} {% data variables.product.prodname_actions %} for the users of an existing instance, review the levels of activity for users and automations on the instance and ensure that you have provisioned adequate CPU and memory for your users. For more information about monitoring the capacity and performance of {% data variables.product.prodname_ghe_server %}, see "[Monitoring your appliance](/admin/enterprise-management/monitoring-your-appliance)." For more information about minimum hardware requirements for {% data variables.product.product_location %}, see the hardware considerations for your instance's platform. diff --git a/translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md b/translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md index b527e6f084..812c378557 100644 --- a/translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md +++ b/translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md @@ -10,7 +10,6 @@ children: - /enabling-github-actions-with-azure-blob-storage - /enabling-github-actions-with-amazon-s3-storage - /enabling-github-actions-with-minio-gateway-for-nas-storage - - /enforcing-github-actions-policies-for-your-enterprise shortTitle: Enable GitHub Actions --- diff --git a/translations/de-DE/content/admin/github-actions/index.md b/translations/de-DE/content/admin/github-actions/index.md index fe0779539f..d0fb8bafcd 100644 --- a/translations/de-DE/content/admin/github-actions/index.md +++ b/translations/de-DE/content/admin/github-actions/index.md @@ -16,6 +16,5 @@ children: shortTitle: Manage GitHub Actions --- -{% data reusables.actions.ae-beta %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} diff --git a/translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md b/translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md index 42282a53e2..8b661db885 100644 --- a/translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md +++ b/translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md @@ -18,7 +18,6 @@ shortTitle: Add actions in your enterprise {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data variables.product.prodname_actions %} workflows can use _actions_, which are individual tasks that you can combine to create jobs and customize your workflow. You can create your own actions, or use and customize actions shared by the {% data variables.product.prodname_dotcom %} community. diff --git a/translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md b/translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md index 86ad694f74..a8ef49b657 100644 --- a/translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md +++ b/translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md @@ -19,7 +19,6 @@ shortTitle: Use GitHub Connect for actions {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.actions.enterprise-github-connect-warning %} -{% data reusables.actions.ae-beta %} By default, {% data variables.product.prodname_actions %} workflows on {% data variables.product.product_name %} cannot use actions directly from {% data variables.product.prodname_dotcom_the_website %} or [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions). @@ -27,8 +26,16 @@ To make all actions from {% data variables.product.prodname_dotcom_the_website % ## Enabling automatic access to all {% data variables.product.prodname_dotcom_the_website %} actions -Before enabling access to all actions from {% data variables.product.prodname_dotcom_the_website %} on your enterprise instance, you must connect your enterprise to {% data variables.product.prodname_dotcom_the_website %}. Weitere Informationen finden Sie unter „[{% data variables.product.prodname_ghe_server %} mit {% data variables.product.prodname_ghe_cloud %} verbinden](/enterprise/{{ currentVersion }}/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)“. +Before enabling access to all actions from {% data variables.product.prodname_dotcom_the_website %} on your enterprise instance, you must connect your enterprise to {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Connecting your enterprise to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." -{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %} +{% data reusables.enterprise-accounts.access-enterprise %} +{%- ifversion ghes < 3.1 %} +{% data reusables.enterprise-accounts.settings-tab %} +{%- endif %} +{% data reusables.enterprise-accounts.github-connect-tab %} +{%- ifversion ghes > 3.0 or ghae %} +1. Under "Users can utilize actions from GitHub.com in workflow runs", use the drop-down menu and select **Enabled**. ![Drop-down menu to actions from GitHub.com in workflows runs](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down-ae.png) +{%- else %} 1. Under "Server can use actions from GitHub.com in workflows runs", use the drop-down menu and select **Enabled**. ![Drop-down menu to actions from GitHub.com in workflows runs](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down.png) +{%- endif %} 1. {% data reusables.actions.enterprise-limit-actions-use %} diff --git a/translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md b/translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md index 4b02e8424e..ea86ba7627 100644 --- a/translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md +++ b/translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md @@ -14,13 +14,14 @@ shortTitle: Manually sync actions {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.actions.enterprise-no-internet-actions %} -The recommended approach of enabling access to actions from {% data variables.product.prodname_dotcom_the_website %} is to enable automatic access to all actions. You can do this by using {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.product_name %} with {% data variables.product.prodname_ghe_cloud %} . For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". +{% ifversion ghes or ghae-next %} -However, if you want stricter control over which actions are allowed in your enterprise, you can follow this guide to use {% data variables.product.company_short %}'s open source [`actions-sync`](https://github.com/actions/actions-sync) tool to sync individual action repositories from {% data variables.product.prodname_dotcom_the_website %} to your enterprise. +The recommended approach of enabling access to actions from {% data variables.product.prodname_dotcom_the_website %} is to enable automatic access to all actions. You can do this by using {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.product_name %} with {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)." + +However, if you want stricter control over which actions are allowed in your enterprise, you{% else %}You{% endif %} can follow this guide to use {% data variables.product.company_short %}'s open source [`actions-sync`](https://github.com/actions/actions-sync) tool to sync individual action repositories from {% data variables.product.prodname_dotcom_the_website %} to your enterprise. ## About the `actions-sync` tool @@ -33,7 +34,7 @@ The `actions-sync` tool can only download actions from {% data variables.product ## Vorrausetzungen * Before using the `actions-sync` tool, you must ensure that all destination organizations already exist in your enterprise. The following example demonstrates how to sync actions to an organization named `synced-actions`. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." -* You must create a personal access token (PAT) on your enterprise that can create and write to repositories in the destination organizations. Weitere Informationen finden Sie unter "[Erstellen eines persönlichen Zugriffstokens](/github/authenticating-to-github/creating-a-personal-access-token)." +* You must create a personal access token (PAT) on your enterprise that can create and write to repositories in the destination organizations. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."{% ifversion ghes %} * If you want to sync the bundled actions in the `actions` organization on {% data variables.product.product_location %}, you must be an owner of the `actions` organization. {% note %} @@ -46,7 +47,7 @@ The `actions-sync` tool can only download actions from {% data variables.product ```shell ghe-org-admin-promote -u USERNAME -o actions - ``` + ```{% endif %} ## Example: Using the `actions-sync` tool diff --git a/translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md b/translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md index 1dfb86f606..0f6ecaa869 100644 --- a/translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md +++ b/translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md @@ -14,7 +14,6 @@ shortTitle: Tool cache for offline runners {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About the included setup actions and the runner tool cache diff --git a/translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md b/translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md index b504c8ad0d..233d75c256 100644 --- a/translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md +++ b/translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md @@ -13,7 +13,6 @@ shortTitle: Use the latest bundled actions {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} Your enterprise instance includes a number of built-in actions that you can use in your workflows. For more information about the bundled actions, see "[Official actions bundled with your enterprise instance](/admin/github-actions/about-using-actions-in-your-enterprise#official-actions-bundled-with-your-enterprise-instance)." @@ -29,17 +28,13 @@ You can use {% data variables.product.prodname_github_connect %} to allow {% dat Once {% data variables.product.prodname_github_connect %} is configured, you can use the latest version of an action by deleting its local repository in the `actions` organization on your instance. For example, if your enterprise instance is using the `actions/checkout@v1` action, and you need to use `actions/checkout@v2` which isn't available on your enterprise instance, perform the following steps to be able to use the latest `checkout` action from {% data variables.product.prodname_dotcom_the_website %}: -1. By default, site administrators are not owners of the bundled actions organization. To get the required access to delete the `checkout` repository, use the `ghe-org-admin-promote` command to promote a user to be an owner of the bundled `actions` organization. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" and "[`ghe-org-admin-promote`](/admin/configuration/command-line-utilities#ghe-org-admin-promote)." Ein Beispiel: - - ```shell - $ ghe-org-admin-promote -u octocat -o actions - Do you want to give organization admin privileges for actions to octocat? (y/N) y - Making octocat an admin of actions - --> Adding octocat as an admin of actions - --> octocat is now an admin of the actions organization - --> Done. - ``` -1. On your {% data variables.product.product_name %} instance, delete the `checkout` repository within the `actions` organization. For information on how to delete a repository, see "[Deleting a repository ](/github/administering-a-repository/deleting-a-repository)." -1. It is recommended that you leave the `actions` organization once you no longer require administrative access. For more information, see "[Removing yourself from an organization ](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization)." +1. From an enterprise owner account on {% data variables.product.product_name %}, navigate to the repository you want to delete from the *actions* organization (in this example `checkout`). +1. By default, site administrators are not owners of the bundled *actions* organization. To get the access required to delete the `checkout` repository, you must use the site admin tools. Click {% octicon "rocket" aria-label="The rocket ship" %} in the upper-right corner of any page in that repository. ![Raumschiffsymbol für den Zugriff auf die Einstellungen des Websiteadministrators](/assets/images/enterprise/site-admin-settings/access-new-settings.png) +1. Click {% octicon "shield-lock" %} **Security** to see the security overview for the repository. ![Security header the repository](/assets/images/enterprise/site-admin-settings/access-repo-security-info.png) +1. Under "Privileged access", click **Unlock**. ![Unlock button](/assets/images/enterprise/site-admin-settings/unlock-priviledged-repo-access.png) +1. Under **Reason**, type a reason for unlocking the repository, then click **Unlock**. ![Confirmation dialog](/assets/images/enterprise/site-admin-settings/confirm-unlock-repo-access.png) +1. Now that the repository is unlocked, you can leave the site admin pages and delete the repository within the `actions` organization. At the top of the page, click the repository name, in this example **checkout**, to return to the summary page. ![Repository name link](/assets/images/enterprise/site-admin-settings/display-repository-admin-summary.png) +1. Under "Repository info", click **View code** to leave the site admin pages and display the `checkout` repository. +1. Delete the `checkout` repository within the `actions` organization. For information on how to delete a repository, see "[Deleting a repository](/github/administering-a-repository/deleting-a-repository)." ![View code link](/assets/images/enterprise/site-admin-settings/exit-admin-page-for-repository.png) 1. Configure your workflow's YAML to use `actions/checkout@v2`. 1. Each time your workflow runs, the runner will use the `v2` version of `actions/checkout` from {% data variables.product.prodname_dotcom_the_website %}. diff --git a/translations/de-DE/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md b/translations/de-DE/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md index 4501a3200b..98779f254d 100644 --- a/translations/de-DE/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md +++ b/translations/de-DE/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md @@ -13,7 +13,6 @@ redirect_from: - /admin/github-actions/getting-started-with-github-actions-for-github-ae --- -{% data reusables.actions.ae-beta %} This article explains how site administrators can configure {% data variables.product.prodname_ghe_managed %} to use {% data variables.product.prodname_actions %}. diff --git a/translations/de-DE/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md b/translations/de-DE/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md index 6a995ba974..9049ffa719 100644 --- a/translations/de-DE/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md +++ b/translations/de-DE/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md @@ -8,7 +8,6 @@ redirect_from: shortTitle: Use actions --- -{% data reusables.actions.ae-beta %} {% data variables.product.prodname_actions %} workflows can use _actions_, which are individual tasks that you can combine to create jobs and customize your workflow. You can create your own actions, or use and customize actions shared by the {% data variables.product.prodname_dotcom %} community. diff --git a/translations/de-DE/content/admin/guides.md b/translations/de-DE/content/admin/guides.md index ca08bc3198..bd7eae59d1 100644 --- a/translations/de-DE/content/admin/guides.md +++ b/translations/de-DE/content/admin/guides.md @@ -35,13 +35,13 @@ includeGuides: - /admin/configuration/configuring-rate-limits - /admin/configuration/configuring-secret-scanning-for-your-appliance - /admin/configuration/configuring-tls - - /admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud + - /admin/configuration/connecting-your-enterprise-account-to-github-enterprise-cloud - /admin/configuration/enabling-and-scheduling-maintenance-mode - /admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud - /admin/configuration/enabling-private-mode - /admin/configuration/enabling-subdomain-isolation - - /admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom - - /admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom + - /admin/configuration/enabling-unified-contributions-between-your-enterprise-account-and-githubcom + - /admin/configuration/enabling-unified-search-between-your-enterprise-account-and-githubcom - /admin/configuration/initializing-github-ae - /admin/configuration/managing-github-for-mobile-for-your-enterprise - /admin/configuration/network-ports diff --git a/translations/de-DE/content/admin/overview/about-upgrades-to-new-releases.md b/translations/de-DE/content/admin/overview/about-upgrades-to-new-releases.md index fc021ae421..7ae13c70e9 100644 --- a/translations/de-DE/content/admin/overview/about-upgrades-to-new-releases.md +++ b/translations/de-DE/content/admin/overview/about-upgrades-to-new-releases.md @@ -13,7 +13,7 @@ topics: {% data variables.product.product_name %} is constantly improving, with new functionality and bug fixes introduced through major and minor releases. {% ifversion ghae %}{% data variables.product.prodname_ghe_managed %} is a fully managed service, so {% data variables.product.company_short %} completes the upgrade process for your enterprise.{% endif %} -Major releases include new functionality and feature upgrades and typically occur {% ifversion ghae %}every few weeks or months{% else %} quarterly{% endif %}. {% ifversion ghae %}{% data variables.product.company_short %} will upgrade your enterprise to the latest major release. You will be given advance notice of any planned downtime for your enterprise.{% endif %} +Major releases include new functionality and feature upgrades and typically occur quarterly. {% ifversion ghae %}{% data variables.product.company_short %} will upgrade your enterprise to the latest major release. You will be given advance notice of any planned downtime for your enterprise.{% endif %} {% ifversion ghes %} @@ -43,7 +43,6 @@ To upgrade your enterprise to a new release, see "[Release notes](/enterprise-se ## Weiterführende Informationen -- [ {% data variables.product.prodname_roadmap %} ]({% data variables.product.prodname_roadmap_link %}) in the `github/roadmap` repository -{% ifversion ghae %} +- [ {% data variables.product.prodname_roadmap %} ]({% data variables.product.prodname_roadmap_link %}) in the `github/roadmap` repository{% ifversion ghae %} - [ {% data variables.product.prodname_ghe_managed %} release notes](/admin/release-notes) {% endif %} diff --git a/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise.md b/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise.md new file mode 100644 index 0000000000..6975629cf9 --- /dev/null +++ b/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise.md @@ -0,0 +1,59 @@ +--- +title: Enforcing GitHub Actions policies for your enterprise +intro: 'Enterprise administrators can manage access to {% data variables.product.prodname_actions %} in an enterprise.' +redirect_from: + - /enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise + - /admin/github-actions/enforcing-github-actions-policies-for-your-enterprise + - /admin/github-actions/enabling-github-actions-for-github-enterprise-server/enforcing-github-actions-policies-for-your-enterprise +versions: + ghes: '*' + ghae: '*' +type: how_to +topics: + - Actions + - Enterprise + - Policies +shortTitle: GitHub Actions policies +--- + +{% data reusables.actions.enterprise-beta %} + +## About {% data variables.product.prodname_actions %} permissions for your enterprise + +{% ifversion ghae %}{% else %}When you enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}, it is enabled for all organizations in your enterprise. {% endif %}You can choose to disable {% data variables.product.prodname_actions %} for all organizations in your enterprise, or only allow specific organizations. You can also limit the use of public actions, so that people can only use local actions that exist in your enterprise. + +## Managing {% data variables.product.prodname_actions %} permissions for your enterprise + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.actions-tab %} +{% data reusables.actions.enterprise-actions-permissions %} + +{% ifversion ghes > 2.22 or ghae %} +## Allowing specific actions to run + +{% data reusables.actions.allow-specific-actions-intro %} + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.actions-tab %} +1. Under **Policies**, select **Allow select actions** and add your required actions to the list. + {%- ifversion ghes or ghae-issue-5094 %} + ![Add actions to allow list](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png) + {%- elsif ghae %} + ![Add actions to allow list](/assets/images/enterprise/github-ae/enterprise-actions-policy-allow-list.png) + {%- endif %} +{% endif %} + +{% ifversion ghes > 2.22 or ghae %} +## Enabling workflows for private repository forks + +{% data reusables.github-actions.private-repository-forks-overview %} + +### Configuring the private fork policy for your enterprise + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.actions-tab %} +{% data reusables.github-actions.private-repository-forks-configure %} +{% endif %} diff --git a/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md b/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md index 484a818233..1e62adf19b 100644 --- a/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md +++ b/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md @@ -34,7 +34,7 @@ topics: - Enterprise - Policies - Security -shortTitle: Enforce repository policies +shortTitle: Repository management policies --- ## Configuring the default visibility of new repositories in your enterprise diff --git a/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/index.md b/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/index.md index 73c67d0923..f4cdf81f00 100644 --- a/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/index.md +++ b/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/index.md @@ -11,6 +11,7 @@ topics: children: - /enforcing-repository-management-policies-in-your-enterprise - /restricting-email-notifications-for-your-enterprise + - /enforcing-github-actions-policies-for-your-enterprise - /enforcing-policies-for-advanced-security-in-your-enterprise shortTitle: Enforce policies --- diff --git a/translations/de-DE/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md b/translations/de-DE/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md index 81c732fa5d..04ca8e6da7 100644 --- a/translations/de-DE/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md +++ b/translations/de-DE/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md @@ -30,6 +30,9 @@ If you can't access {% data variables.product.product_name %}, contact your loca {% data reusables.saml.dotcom-saml-explanation %} Organisationsinhaber können Dein Benutzerkonto auf {% data variables.product.prodname_dotcom %} einladen, ihrer SAML SSO benutzenden Organisation beizutreten. Das erlaubt Dir, Beiträge zur Organisation zu leisten und Deine bestehende Identität und Beiträge auf {% data variables.product.prodname_dotcom %} zu behalten. +If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you will use a new account that is provisioned for you. {% data reusables.enterprise-accounts.emu-more-info-account %} + + Wenn Du auf Ressourcen innerhalb einer Organisation zugreifst, die SAML SSO verwendet, leitet {% data variables.product.prodname_dotcom %} Dich zur Authentifizierung zum SAML-Identitätsanbieter (IdP) der Organisation weiter. Nachdem Du Dich erfolgreich mit Deinem Konto auf dem IdP authentifiziert hast, leitet Dich der IdP zurück zu {% data variables.product.prodname_dotcom %}, wo Du dann auf die Ressourcen der Organisation zugreifen kannst. {% data reusables.saml.outside-collaborators-exemption %} diff --git a/translations/de-DE/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md b/translations/de-DE/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md index d825633633..944a396282 100644 --- a/translations/de-DE/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md +++ b/translations/de-DE/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md @@ -20,7 +20,7 @@ shortTitle: Generate new SSH key If you don't already have an SSH key, you must generate a new SSH key to use for authentication. If you're unsure whether you already have an SSH key, you can check for existing keys. For more information, see "[Checking for existing SSH keys](/github/authenticating-to-github/checking-for-existing-ssh-keys)." -{% ifversion fpt %} +{% ifversion fpt or ghae-next or ghes > 3.1 %} If you want to use a hardware security key to authenticate to {% data variables.product.product_name %}, you must generate a new SSH key for your hardware security key. You must connect your hardware security key to your computer when you authenticate with the key pair. For more information, see the [OpenSSH 8.2 release notes](https://www.openssh.com/txt/release-8.2). @@ -31,6 +31,12 @@ If you don't want to reenter your passphrase every time you use your SSH key, yo {% data reusables.command_line.open_the_multi_os_terminal %} 2. Füge den folgenden Text ein, und ersetzte dabei Deine {% data variables.product.product_name %}-E-Mail-Adresse. + {% ifversion ghae %} + + ```shell + $ ssh-keygen -t rsa -b 4096 -C "your_email@example.com" + ``` + {% else %} ```shell $ ssh-keygen -t ed25519 -C "your_email@example.com" ``` @@ -38,20 +44,22 @@ If you don't want to reenter your passphrase every time you use your SSH key, yo **Note:** If you are using a legacy system that doesn't support the Ed25519 algorithm, use: ```shell - $ ssh-keygen -t rsa -b 4096 -C "your_email@example.com" + $ ssh-keygen -t rsa -b 4096 -C "your_email@example.com" ``` {% endnote %} + {% endif %} + This creates a new SSH key, using the provided email as a label. ```shell - > Generating public/private ed25519 key pair. + > Generating public/private algorithm key pair. ``` 3. Wenn die Aufforderung „Enter a file in which to save the key“ (Datei angeben, in der der Schlüssel gespeichert werden soll) angezeigt wird, drücke die Eingabetaste. Dadurch wird der Standard-Speicherort akzeptiert. {% mac %} ```shell - > Enter a file in which to save the key (/Users/you/.ssh/id_ed25519): [Press enter] + > Enter a file in which to save the key (/Users/you/.ssh/id_algorithm): [Press enter] ``` {% endmac %} @@ -59,7 +67,7 @@ If you don't want to reenter your passphrase every time you use your SSH key, yo {% windows %} ```shell - > Enter a file in which to save the key (/c/Users/you/.ssh/id_ed25519):[Press enter] + > Enter a file in which to save the key (/c/Users/you/.ssh/id_algorithm):[Press enter] ``` {% endwindows %} @@ -67,7 +75,7 @@ If you don't want to reenter your passphrase every time you use your SSH key, yo {% linux %} ```shell - > Enter a file in which to save the key (/home/you/.ssh/id_ed25519): [Press enter] + > Enter a file in which to save the key (/home/you/.ssh/algorithm): [Press enter] ``` {% endlinux %} @@ -107,7 +115,7 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav Host * AddKeysToAgent yes UseKeychain yes - IdentityFile ~/.ssh/id_ed25519 + IdentityFile ~/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %} ``` {% note %} @@ -137,7 +145,7 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav 3. Fügen Sie Ihren privaten SSH-Schlüssel zu ssh-agent hinzu, und speichern Sie Ihre Passphrase in der Keychain. {% data reusables.ssh.add-ssh-key-to-ssh-agent %} ```shell - $ ssh-add -K ~/.ssh/id_ed25519 + $ ssh-add -K ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %} ``` {% note %} @@ -189,8 +197,10 @@ If you are using macOS or Linux, you may need to update your SSH client or insta {% data reusables.command_line.open_the_multi_os_terminal %} 3. Paste the text below, substituting in the email address for your account on {% data variables.product.product_name %}. ```shell - $ ssh-keygen -t ed25519-sk -C "your_email@example.com" + $ ssh-keygen -t {% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}-sk -C "your_email@example.com" ``` + + {% ifversion not ghae %} {% note %} **Note:** If the command fails and you receive the error `invalid format` or `feature not supported,` you may be using a hardware security key that does not support the Ed25519 algorithm. Enter the following command instead. @@ -199,13 +209,14 @@ If you are using macOS or Linux, you may need to update your SSH client or insta ``` {% endnote %} + {% endif %} 4. When you are prompted, touch the button on your hardware security key. 5. When you are prompted to "Enter a file in which to save the key," press Enter to accept the default file location. {% mac %} ```shell - > Enter a file in which to save the key (/Users/you/.ssh/id_ed25519_sk): [Press enter] + > Enter a file in which to save the key (/Users/you/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): [Press enter] ``` {% endmac %} @@ -213,7 +224,7 @@ If you are using macOS or Linux, you may need to update your SSH client or insta {% windows %} ```shell - > Enter a file in which to save the key (/c/Users/you/.ssh/id_ed25519_sk):[Press enter] + > Enter a file in which to save the key (/c/Users/you/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk):[Press enter] ``` {% endwindows %} @@ -221,7 +232,7 @@ If you are using macOS or Linux, you may need to update your SSH client or insta {% linux %} ```shell - > Enter a file in which to save the key (/home/you/.ssh/id_ed25519_sk): [Press enter] + > Enter a file in which to save the key (/home/you/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): [Press enter] ``` {% endlinux %} diff --git a/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md index 838f34767b..4c99b4cb0a 100644 --- a/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md +++ b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md @@ -28,6 +28,10 @@ You can access your resources in {% data variables.product.product_name %} in a 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 fpt %} +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](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users#authenticating-as-a-managed-user)". If you're not a member of an {% data variables.product.prodname_emu_enterprise %}, you will authenticate using your browser on {% data variables.product.prodname_dotcom_the_website %}. +{% endif %} + - **Username and password only** - You'll create a password when you create your user 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)." - **Two-factor authentication (2FA)** (recommended) diff --git a/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md index 784abd0970..6c8a04420c 100644 --- a/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md +++ b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md @@ -38,7 +38,7 @@ A token with no assigned scopes can only access public information. Um den Token {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.developer_settings %} {% data reusables.user_settings.personal_access_tokens %} -4. Klicke auf **Generate new token** (Neues Token erzeugen). ![Schaltfläche „Generate new token“ (Neues Token erzeugen)](/assets/images/help/settings/generate_new_token.png) +{% data reusables.user_settings.generate_new_token %} 5. Geben Sie dem Token einen beschreibenden Namen. ![Token description field](/assets/images/help/settings/token_description.png){% ifversion fpt or ghes > 3.2 or ghae-issue-4374 %} 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. Wähle die Scopes oder Berechtigungen aus, die Du diesem Token zuweisen möchtest. Um das Token für den Zugriff auf Repositorys über die Befehlszeile zu verwenden, wähle **repo** aus. diff --git a/translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md b/translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md index 0b5102ffab..2399a04147 100644 --- a/translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md +++ b/translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md @@ -75,33 +75,6 @@ Du kannst eine Fallback-Nummer unabhängig davon verwenden, ob Du die Authentifi Nach der Einrichtung wird eine Bestätigungs-SMS an Dein Backup-Gerät gesendet. -## Eine Fallback-Authentifizierungsmethode mit „Recover Accounts Elsewhere" hinzufügen - -Du kannst zusätzliche Anmeldeinformation für die Authentifizierung bei Deinem Konto erzeugen und bei einem Partner-Wiederherstellungsanbieter speichern. - -### Informationen zu „Recover Accounts Elsewhere" - -Mit „Recover Accounts Elsewhere" kannst Du einen zusätzlichen Sicherheitsfaktor zu Deinem {% data variables.product.product_name %}-Konto hinzufügen, für den Fall, dass Du nicht auf Deine Zwei-Faktor-Authentifizierungsmethode oder Wiederherstellungscodes zugreifen kannst. - -Bei „Recover Accounts Elsewhere" kannst Du Dein {% data variables.product.product_name %}-Konto mit Deinem Facebook-Konto verknüpfen. Du kannst die Anmeldeinformationen für die Authentifizierung in Form eines _Konto-Wiederherstellungstokens_ für Dein {% data variables.product.product_name %}-Konto bei Facebook hinterlegen. - -Wenn Du den Zugriff auf Dein {% data variables.product.product_name %}-Konto verlierst, weil Du nicht mehr auf Deine Zwei-Faktor-Authentifizierungsmethode oder Deine Wiederherstellungscodes zugreifen kannst, kannst Du Dein Kontowiederherstellungstoken vom Wiederherstellungsanbieter abrufen und mit diesem Token nachweisen, dass Dir das {% data variables.product.product_name %}-Konto gehört. - -Nach dem Abrufen Deines Tokens ist {% data variables.contact.contact_support %} möglicherweise in der Lage, die Zwei-Faktor-Authentifizierung für Dein Konto zu deaktivieren. Dann kannst Du Dein Passwort eingeben oder zurücksetzen, um wieder auf Dein Konto zugreifen zu können. - -Wenn Du ein Kontowiederherstellungstoken erzeugst oder abrufst, wird ein Ereignis zum Auditprotokoll Deines Kontos hinzugefügt. Weitere Informationen finden Sie unter „[Sicherheitsprotokoll überprüfen](/articles/reviewing-your-security-log)“. - -### Ein Kontowiederherstellungstoken erzeugen und speichern - -Du kannst ein Kontowiederherstellungstoken erzeugen und bei einem Partner-Wiederherstellungsanbieter speichern. - -1. Melde Dich bei Deinem Facebook-Konto an, und kehre dann zu {% data variables.product.product_name %} zurück. -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.security %} -4. Um ein neues Token zu erzeugen, klicke unter „Recovery tokens“ (Wiederherstellungstoken) auf **Store new token** (Neues Token speichern). ![Schaltfläche zum Speichern eines neuen Wiederherstellungstokens](/assets/images/help/settings/store-new-recovery-token.png) -5. Lies die Informationen zu Kontowiederherstellungstoken und klicke dann auf **Connect with https://www.facebook.com** (Mit https://www.facebook.com verbinden). ![Schaltfläche zum Verbinden eines Wiederherstellungstokens mit Facebook](/assets/images/help/settings/connect-recovery-token-with-facebook.png) -6. Wenn Du zu Facebook weitergeleitet wurdest, lies die Informationen zum Aktivieren der Kontowiederherstellung mit Facebook, bevor Du auf **Save as [_YOUR NAME_]** (Als IHR NAME speichern) klickst. (Wenn Du mehrere Tokens in einem kurzen Zeitraum speicherst, überspringt Facebook diesen Bestätigungsschritt möglicherweise, nachdem Du den ersten Token gespeichert hast.) ![Facebook-Seite mit Schaltfläche zum Aktivieren einer Kontowiederherstellung](/assets/images/help/settings/security-turn-on-rae-facebook.png) - {% endif %} ## Weiterführende Informationen diff --git a/translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md b/translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md index 411b5a8f7a..ffbf0663d3 100644 --- a/translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md +++ b/translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md @@ -28,6 +28,12 @@ Wir empfehlen dringend, eine TOTP-Anwendung (Time-based One-Time Password) zu ve {% endwarning %} +{% ifversion fpt %} + +If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you cannot configure 2FA for your {% data variables.product.prodname_managed_user %} account. 2FA should be configured through your identity provider. + +{% endif %} + ## Zwei-Faktor-Authentifizierung mit einer mobilen TOTP-Anwendung konfigurieren Eine TOTP-Anwendung (Time-based One-Time Password) erzeugt automatisch einen Authentifizierungscode, der sich nach einem bestimmten Zeitraum ändert. Wir empfehlen die Nutzung Cloud-basierter TOTP-Apps wie: diff --git a/translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md b/translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md index acd441acf0..7900df7f01 100644 --- a/translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md +++ b/translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md @@ -71,6 +71,12 @@ Sie kannst die Anmeldeinformationen oder die Wiederherstellungscodes Deiner Zwei ## Authentifizierung mit einem Kontowiederherstellungstoken +{% warning %} + +**Warning:** Account recovery tokens are deprecated and will be disabled on **December 1st, 2021**. Please ensure you have configured other two-factor recovery methods. For more information, see "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)." + +{% endwarning %} + Wenn Du den Zugriff auf die Zwei-Faktor-Authentifizierungsmethoden für Dein {% data variables.product.product_name %}-Konto verlierst, kannst Du Dein Kontowiederherstellungstoken von einem Partner-Wiederherstellungsanbieter abrufen und den {% data variables.product.prodname_dotcom %}-Support darum bitten, es zu prüfen. Wenn Du keinen Zugriff auf Deine Zwei-Faktor-Authentifizierungsmethoden oder Wiederherstellungscodes hast und ein Kontowiederherstellungstoken mit „Recover Accounts Elsewhere" bei Facebook gespeichert hast, kannst Du möglicherweise mit diesem Token wieder Zugriff auf Dein Konto erlangen. diff --git a/translations/de-DE/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md b/translations/de-DE/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md index d2ce7450e4..4373fcb3b8 100644 --- a/translations/de-DE/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md +++ b/translations/de-DE/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md @@ -68,6 +68,8 @@ Die Anzahl der Aufträge, die Du gleichzeitig über alle Repositories in Deinem ## Minuten- und Speicherausgaben berechnen +{% data reusables.dotcom_billing.pricing_cal %} + Am Ende des Monats berechnet {% data variables.product.prodname_dotcom %} die Minuten- und Speicherkosten, die über den in Deinem Konto enthaltenen Kontingent liegen. ### Sample minutes cost calculation diff --git a/translations/de-DE/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md b/translations/de-DE/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md index 8970d05671..33171d696c 100644 --- a/translations/de-DE/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md +++ b/translations/de-DE/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md @@ -28,6 +28,8 @@ Deine {% data variables.product.prodname_codespaces %}-Nutzung teilt das bestehe 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 {% data variables.product.prodname_codespaces %} usage. For more information, see "[Connecting an Azure subscription to your enterprise](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)." +{% data reusables.dotcom_billing.pricing_cal %} + ## Setting a spending limit {% data reusables.codespaces.codespaces-spending-limit-requirement %} diff --git a/translations/de-DE/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md b/translations/de-DE/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md index d7674b20ba..cbd58740dd 100644 --- a/translations/de-DE/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md +++ b/translations/de-DE/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md @@ -49,7 +49,7 @@ Die Speichernutzung wird mit Build-Artefakten geteilt, die von {% data variables {% data variables.product.prodname_dotcom %} belastet die Nutzung auf das Konto, welches das Repository besitzt, in dem das Paket veröffentlicht wird. 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. -Wenn Deine Organisation beispielsweise {% data variables.product.prodname_team %} verwendet, unbegrenzte Ausgaben erlaubt, 150 GB Speicher verwendet und 50 GB Datenübertragung nach Außen während eines Monats verbraucht, würde die Organisation Überzüge von 148 GB für die Speicherung und 40 GB für die Datenübertragung für diesen Monat haben. 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. +Wenn Deine Organisation beispielsweise {% data variables.product.prodname_team %} verwendet, unbegrenzte Ausgaben erlaubt, 150 GB Speicher verwendet und 50 GB Datenübertragung nach Außen während eines Monats verbraucht, würde die Organisation Überzüge von 148 GB für die Speicherung und 40 GB für die Datenübertragung für diesen Monat haben. 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. {% data reusables.dotcom_billing.pricing_cal %} Am Ende jedes Monates wird {% data variables.product.prodname_dotcom %} Deine Datenübertragung auf das nächste GB aufrunden. diff --git a/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md b/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md index a0be859f5a..8344bdcf29 100644 --- a/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md +++ b/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md @@ -68,11 +68,9 @@ If you use the default workflow, {% data variables.product.prodname_code_scannin 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)." -{% note %} - -**Note**: If you want {% data variables.product.prodname_code_scanning %} alerts to appear as pull request checks, you must use the `pull_request` event, described below. - -{% endnote %} +{% ifversion fpt or ghes > 3.2 or ghae-issue-5093 %} +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 %} ### Scanning pull requests @@ -82,6 +80,10 @@ For more information about the `pull_request` event, see "[Workflow syntax for { 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 %} + 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 %} + {% ifversion fpt or ghes > 3.1 or ghae-next %} ### Defining the severities causing pull request check failure @@ -234,7 +236,6 @@ Alternatively, you can install Python dependencies manually on any operating sys ```yaml jobs: CodeQL-Build: - runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae-next %} permissions: security-events: write @@ -266,7 +267,7 @@ jobs: ``` {% endif %} -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ## Configuring a category for the analysis Use `category` to distinguish between multiple analyses for the same tool and commit, but performed on different languages or different parts of the code. The category you specify in your workflow will be included in the SARIF results file. diff --git a/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md b/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md index 0e004b9857..2b0cf03afb 100644 --- a/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md @@ -48,9 +48,9 @@ When {% data variables.product.prodname_code_scanning %} reports data-flow alert Alert severity levels may be `Error`, `Warning`, or `Note`. -By default, any code scanning results with a severity of `error` will cause check failure. {% ifversion fpt or ghes > 3.1 or ghae-next %}You can specify the severity level at which pull requests that trigger code scanning alerts should fail. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %} +By default, any code scanning results with a severity of `error` will cause check failure. {% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %}You can specify the severity level at which pull requests that trigger code scanning alerts should fail. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %} +{% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %} ### About security severity levels {% data variables.product.prodname_code_scanning_capc %} displays security severity levels for alerts that are generated by security queries. Security severity levels can be `Critical`, `High`, `Medium`, or `Low`. @@ -70,10 +70,10 @@ By default, the code scanning alerts page is filtered to show alerts for the def {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-code-scanning-alerts %} -{% ifversion fpt or ghes > 3.1 %} -1. Optionally, use{% ifversion fpt or ghes > 3.1 %} the free text search box or{% endif %} the drop-down menus to filter alerts. For example, you can filter by the tool that was used to identify alerts. ![Filter by tool](/assets/images/help/repository/code-scanning-filter-by-tool.png){% endif %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} +1. Optionally, use the free text search box or the drop-down menus to filter alerts. For example, you can filter by the tool that was used to identify alerts. ![Filter by tool](/assets/images/help/repository/code-scanning-filter-by-tool.png){% endif %} 1. Under "{% data variables.product.prodname_code_scanning_capc %}," click the alert you'd like to explore. -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ![Summary of alerts](/assets/images/help/repository/code-scanning-click-alert.png) {% else %} ![Liste der Warnungen von {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) @@ -81,7 +81,7 @@ By default, the code scanning alerts page is filtered to show alerts for the def 1. Optionally, if the alert highlights a problem with data flow, click **Show paths** to display the path from the data source to the sink where it's used. ![The "Show paths" link on an alert](/assets/images/help/repository/code-scanning-show-paths.png) 1. Alerts from {% data variables.product.prodname_codeql %} analysis include a description of the problem. Click **Show more** for guidance on how to fix your code. ![Details for an alert](/assets/images/help/repository/code-scanning-alert-details.png) -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} {% note %} **Note:** For {% data variables.product.prodname_code_scanning %} analysis with {% data variables.product.prodname_codeql %}, you can see information about the latest run in a header at the top of the list of {% data variables.product.prodname_code_scanning %} alerts for the repository. @@ -91,7 +91,6 @@ For example, you can see when the last scan ran, the number of lines of code ana {% endnote %} {% endif %} - ## Filtering {% data variables.product.prodname_code_scanning %} alerts You can filter the alerts shown in the {% data variables.product.prodname_code_scanning %} alerts view. This is useful if there are many alerts as you can focus on a particular type of alert. There are some predefined filters and a range of keywords that you can use to refine the list of alerts displayed. @@ -105,7 +104,21 @@ You can filter the alerts shown in the {% data variables.product.prodname_code_s The benefit of using keyword filters is that only values with results are shown in the drop-down lists. This makes it easy to avoid setting filters that find no results. +If you enter multiple filters, the view will show alerts matching _all_ these filters. For example, `is:closed severity:high branch:main` will only display closed high-severity alerts that are present on the `main` branch. The exception is filters relating to refs (`ref`, `branch` and `pr`): `is:open branch:main branch:next` will show you open alerts from both the `main` branch and the `next` branch. + +### Restricting results to application code only + +You can use the "Only alerts in application code" filter or `autofilter:true` keyword and value to restrict results to alerts in application code. Application code excludes the following. + +- Code generated by the build process +- Test code +- Library or third-party code +- Dokumentation + +{% data variables.product.prodname_code_scanning_capc %} categorizes files by file path. At this time, you cannot manually categorize source files. + {% ifversion fpt or ghes > 3.1 %} + ## Searching {% data variables.product.prodname_code_scanning %} alerts You can search the list of alerts. This is useful if there is a large number of alerts in your repository, or if you don't know the exact name for an alert for example. {% data variables.product.product_name %} performs the free text search across: @@ -145,11 +158,11 @@ Anyone with write permission for a repository can fix an alert by committing a c If you have write permission for a repository, you can view fixed alerts by viewing the summary of alerts and clicking **Closed**. For more information, see "[Viewing the alerts for a repository](#viewing-the-alerts-for-a-repository)." The "Closed" list shows fixed alerts and alerts that users have dismissed. -You can use{% ifversion fpt or ghes > 3.1 %} the free text search or{% endif %} the filters to display a subset of alerts and then in turn mark all matching alerts as closed. +You can use{% ifversion fpt or ghes > 3.1 or ghae-next %} the free text search or{% endif %} the filters to display a subset of alerts and then in turn mark all matching alerts as closed. Alerts may be fixed in one branch but not in another. You can use the "Branch" drop-down menu, on the summary of alerts, to check whether an alert is fixed in a particular branch. -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ![Filtering alerts by branch](/assets/images/help/repository/code-scanning-branch-filter.png) {% else %} ![Filtering alerts by branch](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png) @@ -185,9 +198,9 @@ To dismiss or delete alerts: ![Deleting alerts](/assets/images/help/repository/code-scanning-delete-alerts.png) - Optionally, you can use{% ifversion fpt or ghes > 3.1 %} the free text search or{% endif %} the filters to display a subset of alerts and then delete all matching alerts at once. For example, if you have removed a query from {% data variables.product.prodname_codeql %} analysis, you can use the "Rule" filter to list just the alerts for that query and then select and delete all of those alerts. + Optionally, you can use{% ifversion fpt or ghes > 3.1 or ghae-next %} the free text search or{% endif %} the filters to display a subset of alerts and then delete all matching alerts at once. For example, if you have removed a query from {% data variables.product.prodname_codeql %} analysis, you can use the "Rule" filter to list just the alerts for that query and then select and delete all of those alerts. -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ![Filter alerts by rule](/assets/images/help/repository/code-scanning-filter-by-rule.png) {% else %} ![Filter alerts by rule](/assets/images/enterprise/3.1/help/repository/code-scanning-filter-by-rule.png) @@ -195,12 +208,11 @@ To dismiss or delete alerts: 1. If you want to dismiss an alert, it's important to explore the alert first, so that you can choose the correct dismissal reason. Click the alert you'd like to explore. -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ![Open an alert from the summary list](/assets/images/help/repository/code-scanning-click-alert.png) {% else %} ![Liste der Warnungen von {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) {% endif %} - 1. Review the alert, then click **Dismiss** and choose a reason for closing the alert. ![Choosing a reason for dismissing an alert](/assets/images/help/repository/code-scanning-alert-close-drop-down.png) {% data reusables.code-scanning.choose-alert-dismissal-reason %} diff --git a/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md b/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md index a907086917..9b08e6ef8d 100644 --- a/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md +++ b/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md @@ -40,8 +40,8 @@ You decide how to generate {% data variables.product.prodname_code_scanning %} a {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} -3. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. {% ifversion fpt or ghes > 3.0 %}If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}. 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)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %} !["Set up {% data variables.product.prodname_code_scanning %}" button to the right of "{% data variables.product.prodname_code_scanning_capc %}" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png) -4. Under "Get started with {% data variables.product.prodname_code_scanning %}", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png){% ifversion fpt or ghes > 2.22 %}Workflows are only displayed if they are relevant for the programming languages detected in the repository. The {% data variables.product.prodname_codeql_workflow %} is always displayed, but the "Set up this workflow" button is only enabled if {% data variables.product.prodname_codeql %} analysis supports the languages present in the repository.{% endif %} +3. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. {% ifversion fpt or ghes > 3.0 or ghae-next %}If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}. 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)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %} !["Set up {% data variables.product.prodname_code_scanning %}" button to the right of "{% data variables.product.prodname_code_scanning_capc %}" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png) +4. Under "Get started with {% data variables.product.prodname_code_scanning %}", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png){% ifversion fpt or ghes > 2.22 or ghae-next %}Workflows are only displayed if they are relevant for the programming languages detected in the repository. The {% data variables.product.prodname_codeql_workflow %} is always displayed, but the "Set up this workflow" button is only enabled if {% data variables.product.prodname_codeql %} analysis supports the languages present in the repository.{% endif %} 5. To customize how {% data variables.product.prodname_code_scanning %} scans your code, edit the workflow. Generally you can commit the {% data variables.product.prodname_codeql_workflow %} without making any changes to it. However, many of the third-party workflows require additional configuration, so read the comments in the workflow before committing. @@ -53,10 +53,43 @@ You decide how to generate {% data variables.product.prodname_code_scanning %} a In the default {% data variables.product.prodname_codeql_workflow %}, {% data variables.product.prodname_code_scanning %} is configured to analyze your code each time you either push a change to the default branch or any protected branches, or raise a pull request against the default branch. As a result, {% data variables.product.prodname_code_scanning %} will now commence. +The `on:pull_request` and `on:push` triggers for code scanning are each useful for different purposes. For more information, see "[Scanning pull requests](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-pull-requests)" and "[Scanning on push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)." ## Bulk set up of {% data variables.product.prodname_code_scanning %} You can set up {% data variables.product.prodname_code_scanning %} in many repositories at once using a script. If you'd like to use a script to raise pull requests that add a {% data variables.product.prodname_actions %} workflow to multiple repositories, see the [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) repository for an example using Powershell, or [`nickliffen/ghas-enablement`](https://github.com/NickLiffen/ghas-enablement) for teams who do not have Powershell and instead would like to use NodeJS. +## Viewing the logging output from {% data variables.product.prodname_code_scanning %} + +After setting up {% data variables.product.prodname_code_scanning %} for your repository, you can watch the output of the actions as they run. + +{% data reusables.repositories.actions-tab %} + + You'll see a list that includes an entry for running the {% data variables.product.prodname_code_scanning %} workflow. The text of the entry is the title you gave your commit message. + + ![Actions list showing {% data variables.product.prodname_code_scanning %} workflow](/assets/images/help/repository/code-scanning-actions-list.png) + +1. Click the entry for the {% data variables.product.prodname_code_scanning %} workflow. + +1. Click the job name on the left. For example, **Analyze (LANGUAGE)**. + + ![Log output from the {% data variables.product.prodname_code_scanning %} workflow](/assets/images/help/repository/code-scanning-logging-analyze-action.png) + +1. Review the logging output from the actions in this workflow as they run. + +1. Once all jobs are complete, you can view the details of any {% data variables.product.prodname_code_scanning %} alerts that were identified. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)." + +{% note %} + +**Note:** If you raised a pull request to add the {% data variables.product.prodname_code_scanning %} workflow to the repository, alerts from that pull request aren't displayed directly on the {% data variables.product.prodname_code_scanning_capc %} page until the pull request is merged. If any alerts were found you can view these, before the pull request is merged, by clicking the **_n_ alerts found** link in the banner on the {% data variables.product.prodname_code_scanning_capc %} page. + +{% ifversion fpt or ghes > 3.1 or ghae-next %} + ![Click the "n alerts found" link](/assets/images/help/repository/code-scanning-alerts-found-link.png) +{% else %} + ![Click the "n alerts found" link](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png) +{% endif %} + +{% endnote %} + ## Understanding the pull request checks Each {% data variables.product.prodname_code_scanning %} workflow you set to run on pull requests always has at least two entries listed in the checks section of a pull request. There is one entry for each of the analysis jobs in the workflow, and a final one for the results of the analysis. @@ -65,13 +98,25 @@ 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 a "Missing analysis" 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-issue-3891 %}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. - ![Missing analysis for commit message](/assets/images/help/repository/code-scanning-missing-analysis.png) +{% ifversion fpt or ghes > 3.2 or ghae-issue-3891 %} + ![Analysis not found for commit message](/assets/images/help/repository/code-scanning-analysis-not-found.png) -### Reasons for the "missing analysis" message +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. -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 "Missing analysis for base commit SHA-HASH" message. +For example, in the screenshot above, {% data variables.product.prodname_code_scanning %} found an analysis for the merge commit of the pull request, but no analysis for the head of the main branch. +{% else %} + ![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 %} +### 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 %}"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: @@ -79,7 +124,7 @@ There are other situations where there may be no analysis for the latest commit To check whether a branch has been scanned, go to the {% data variables.product.prodname_code_scanning_capc %} page, click the **Branch** drop-down and select the relevant branch. -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ![Choose a branch from the Branch drop-down menu](/assets/images/help/repository/code-scanning-branch-dropdown.png) {% else %} ![Choose a branch from the Branch drop-down menu](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-dropdown.png) diff --git a/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md b/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md index 636968e9bc..de46fadb5c 100644 --- a/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md +++ b/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md @@ -28,6 +28,9 @@ 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 %} +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 %} If your pull request targets a protected branch that uses {% data variables.product.prodname_code_scanning %}, and the repository owner has configured required status checks, then the "{% data variables.product.prodname_code_scanning_capc %} results" check must pass before you can merge the pull request. Weitere Informationen findest Du unter „[Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging).“ diff --git a/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md b/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md index 191862e2cc..ae36c9908f 100644 --- a/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md +++ b/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md @@ -22,7 +22,7 @@ shortTitle: View code scanning logs You can use a variety of tools to set up {% data variables.product.prodname_code_scanning %} in your repository. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#options-for-setting-up-code-scanning)." -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} The log and diagnostic information available to you depends on the method you use for {% data variables.product.prodname_code_scanning %} in your repository. You can check the type of {% data variables.product.prodname_code_scanning %} you're using in the **Security** tab of your repository, by using the **Tool** drop-down menu in the alert list. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)." ## About analysis and diagnostic information @@ -35,7 +35,7 @@ You can see analysis and diagnostic information for {% data variables.product.pr If you're using the {% data variables.product.prodname_codeql_cli %} outside {% data variables.product.prodname_dotcom %}, you'll see diagnostic information in the output generated during database analysis. This information is also included in the SARIF results file you upload to {% data variables.product.prodname_dotcom %} with the {% data variables.product.prodname_code_scanning %} results. -For information about the {% data variables.product.prodname_codeql_cli %}, see "[Running {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-cli-in-your-ci-system#viewing-log-and-diagnostic-information)." +For information about the {% data variables.product.prodname_codeql_cli %}, see "[Configuring {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system#viewing-log-and-diagnostic-information)." ### About summary metrics @@ -72,7 +72,7 @@ After setting up {% data variables.product.prodname_code_scanning %} for your re **Note:** If you raised a pull request to add the {% data variables.product.prodname_code_scanning %} workflow to the repository, alerts from that pull request aren't displayed directly on the {% data variables.product.prodname_code_scanning_capc %} page until the pull request is merged. If any alerts were found you can view these, before the pull request is merged, by clicking the **_n_ alerts found** link in the banner on the {% data variables.product.prodname_code_scanning_capc %} page. -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae %} ![Click the "n alerts found" link](/assets/images/help/repository/code-scanning-alerts-found-link.png) {% else %} ![Click the "n alerts found" link](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png) diff --git a/translations/de-DE/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md b/translations/de-DE/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md index 813531f712..025e92bb21 100644 --- a/translations/de-DE/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md +++ b/translations/de-DE/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md @@ -37,7 +37,7 @@ If your SARIF file doesn't include `partialFingerprints`, the `partialFingerprin {% ifversion fpt or ghes > 3.0 or ghae-next %} If you're using the {% data variables.product.prodname_codeql_cli %}, then you can specify the version of SARIF to use. For more information, see "[Configuring {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system#analyzing-a-codeql-database)."{% endif %} -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} You can upload multiple SARIF files for the same tool and commit, and analyze each file using {% data variables.product.prodname_code_scanning %}. You can indicate a "category" for each analysis by specifying a `runAutomationDetails.id` in each file. Only SARIF files with the same category will overwrite each other. For more information about this property, see [`runAutomationDetails` object](#runautomationdetails-object) below. {% endif %} @@ -141,7 +141,7 @@ A location within a programming artifact, such as a file in the repository or a | `region.endLine` | **Required.** The line number of the last character in the region. | | `region.endColumn` | **Required.** The column number of the character following the end of the region. | -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ### `runAutomationDetails` object The `runAutomationDetails` object contains information that specifies the identity of a run. @@ -245,7 +245,7 @@ This SARIF output file has example values to show the minimum required propertie This SARIF output file has example values to show all supported SARIF properties for {% data variables.product.prodname_code_scanning %}. -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ```json { "$schema": "https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json", diff --git a/translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md b/translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md index 7f7deaa569..f7a551c679 100644 --- a/translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md +++ b/translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md @@ -91,8 +91,8 @@ For more information, see "[Running {% data variables.product.prodname_codeql_ru {% endif %} - -{% ifversion ghes = 3.0 or ghae %} + +{% ifversion ghes = 3.0 %} {% data reusables.code-scanning.upload-sarif-ghas %} You add the {% data variables.product.prodname_codeql_runner %} to your third-party system, then call the tool to analyze code and upload the SARIF results to {% data variables.product.product_name %}. The resulting {% data variables.product.prodname_code_scanning %} alerts are shown alongside any alerts generated within {% data variables.product.product_name %}. diff --git a/translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md b/translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md index 1c84895b41..9a1916ff12 100644 --- a/translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md +++ b/translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md @@ -30,7 +30,7 @@ Once you've made the {% data variables.product.prodname_codeql_cli %} available You use three different commands to generate results and upload them to {% data variables.product.product_name %}: -{% ifversion fpt or ghes > 3.1 or ghae-next %} +{% ifversion fpt or ghes > 3.1 or ghae %} 1. `database create` to create a {% data variables.product.prodname_codeql %} database to represent the hierarchical structure of each supported programming language in the repository. 2. `database analyze` to run queries to analyze each {% data variables.product.prodname_codeql %} database and summarize the results in a SARIF file. @@ -50,11 +50,11 @@ You can display the command-line help for any command using the `--help` 3.1 or ghae-next %} + {% ifversion fpt or ghes > 3.1 or ghae %} ```shell # Single supported language - create one CodeQL databsae codeql database create <database> --command<build> --language=<language-identifier> @@ -119,7 +119,7 @@ You can display the command-line help for any command using the `--help` - {% ifversion fpt or ghes > 3.1 or ghae-next %}When used with `--db-cluster`, the option accepts a comma-separated list, or can be specified more than once.{% endif %} + {% ifversion fpt or ghes > 3.1 or ghae %}When used with `--db-cluster`, the option accepts a comma-separated list, or can be specified more than once.{% endif %} @@ -144,7 +144,7 @@ You can display the command-line help for any command using the `--help` - {% ifversion fpt or ghes > 3.1 or ghae-next %} + {% ifversion fpt or ghes > 3.1 or ghae %} @@ -208,7 +208,7 @@ You can display the command-line help for any command using the `--help` 3.1 or ghae-next %}Single language example{% else %}Basic example{% endif %} +### {% ifversion fpt or ghes > 3.1 or ghae %}Single language example{% else %}Basic example{% endif %} This example creates a {% data variables.product.prodname_codeql %} database for the repository checked out at `/checkouts/example-repo`. It uses the JavaScript extractor to create a hierarchical representation of the JavaScript and TypeScript code in the repository. The resulting database is stored in `/codeql-dbs/example-repo`. @@ -226,7 +226,7 @@ $ codeql database create /codeql-dbs/example-repo --language=javascript \ > Successfully created database at /codeql-dbs/example-repo. ``` -{% ifversion fpt or ghes > 3.1 or ghae-next %} +{% ifversion fpt or ghes > 3.1 or ghae %} ### Multiple language example This example creates two {% data variables.product.prodname_codeql %} databases for the repository checked out at `/checkouts/example-repo-multi`. It uses: @@ -273,7 +273,7 @@ $ --output=<output> {% if codeql-packs %}<packs,queries>{% else %} <queries>{% endif %} ``` -{% ifversion fpt or ghes > 3.1 or ghae-next %} +{% ifversion fpt or ghes > 3.1 or ghae %} {% note %} **Note:** If you analyze more than one {% data variables.product.prodname_codeql %} database for a single commit, you must specify a SARIF category for each set of results generated by this command. When you upload the results to {% data variables.product.product_name %}, {% data variables.product.prodname_code_scanning %} uses this category to store the results for each language separately. If you forget to do this, each upload overwrites the previous results. @@ -317,15 +317,14 @@ codeql database analyze <database> --format=<format> \ - <queries> + <packs,queries> - {% octicon "check-circle-fill" aria-label="Required" %} - Specify the queries to run. To run the standard queries used for {% data variables.product.prodname_code_scanning %}, use: <language>-code-scanning.qls where <language> is the short code for the language of the database. To see the other query suites included in the {% data variables.product.prodname_codeql_cli %} bundle, look in /<extraction-root>/codeql/qlpacks/codeql-<language>/codeql-suites. For information about creating your own query suite, see Creating CodeQL query suites in the documentation for the {% data variables.product.prodname_codeql_cli %}. + Specify {% data variables.product.prodname_codeql %} packs or queries to run. To run the standard queries used for {% data variables.product.prodname_code_scanning %}, omit this parameter. To see the other query suites included in the {% data variables.product.prodname_codeql_cli %} bundle, look in /<extraction-root>/codeql/qlpacks/codeql-<language>/codeql-suites. For information about creating your own query suite, see Creating CodeQL query suites in the documentation for the {% data variables.product.prodname_codeql_cli %}. @@ -353,7 +352,7 @@ codeql database analyze <database> --format=<format> \ - Specify where to save the SARIF results file.{% ifversion fpt or ghes > 3.1 or ghae-next %} + Specify where to save the SARIF results file.{% ifversion fpt or ghes > 3.1 or ghae %} @@ -406,7 +405,7 @@ codeql database analyze <database> --format=<format> \ - Optional. Use to get more detailed information about the analysis process{% ifversion fpt or ghes > 3.1 or ghae-next %} and diagnostic data from the database creation process{% endif %}. + Optional. Use to get more detailed information about the analysis process{% ifversion fpt or ghes > 3.1 or ghae %} and diagnostic data from the database creation process{% endif %}. @@ -415,11 +414,11 @@ For more information, see [Analyzing databases with the {% data variables.produc ### Basic example -This example analyzes a {% data variables.product.prodname_codeql %} database stored at `/codeql-dbs/example-repo` and saves the results as a SARIF file: `/temp/example-repo-js.sarif`. {% ifversion fpt or ghes > 3.1 or ghae-next %}It uses `--sarif-category` to include extra information in the SARIF file that identifies the results as JavaScript. This is essential when you have more than one {% data variables.product.prodname_codeql %} database to analyze for a single commit in a repository.{% endif %} +This example analyzes a {% data variables.product.prodname_codeql %} database stored at `/codeql-dbs/example-repo` and saves the results as a SARIF file: `/temp/example-repo-js.sarif`. {% ifversion fpt or ghes > 3.1 or ghae %}It uses `--sarif-category` to include extra information in the SARIF file that identifies the results as JavaScript. This is essential when you have more than one {% data variables.product.prodname_codeql %} database to analyze for a single commit in a repository.{% endif %} ``` $ codeql database analyze /codeql-dbs/example-repo \ - javascript-code-scanning.qls {% ifversion fpt or ghes > 3.1 or ghae-next %}--sarif-category=javascript{% endif %} + javascript-code-scanning.qls {% ifversion fpt or ghes > 3.1 or ghae %}--sarif-category=javascript{% endif %} --format={% ifversion fpt or ghae %}sarif-latest{% else %}sarifv2.1.0{% endif %} --output=/temp/example-repo-js.sarif > Running queries. @@ -444,7 +443,7 @@ When you have decided on the most secure and reliable method for your CI server, ```shell echo "$UPLOAD_TOKEN" | codeql github upload-results --repository=<repository-name> \ --ref=<ref> --commit=<commit> --sarif=<file> \ - {% ifversion ghes > 3.0 or ghae-next %}--github-url=<URL> {% endif %}--github-auth-stdin + {% ifversion ghes > 3.0 or ghae %}--github-url=<URL> {% endif %}--github-auth-stdin ``` @@ -486,7 +485,7 @@ When you have decided on the most secure and reliable method for your CI server, @@ -514,7 +513,7 @@ When you have decided on the most secure and reliable method for your CI server, @@ -555,7 +554,7 @@ This example uploads results from the SARIF file `temp/example-repo-js.sarif` to ``` $ echo $UPLOAD_TOKEN | codeql github upload-results --repository=my-org/example-repo \ --ref=refs/heads/main --commit=deb275d2d5fe9a522a0b7bd8b6b6a1c939552718 \ - --sarif=/temp/example-repo-js.sarif {% ifversion ghes > 3.0 or ghae-next %}--github-url={% data variables.command_line.git_url_example %} \ + --sarif=/temp/example-repo-js.sarif {% ifversion ghes > 3.0 or ghae %}--github-url={% data variables.command_line.git_url_example %} \ {% endif %}--github-auth-stdin ``` @@ -641,6 +640,7 @@ $ codeql database analyze /codeql-dbs/example-repo octo-org/security-queries \ {% endif %} {% ifversion fpt or ghes > 3.1 or ghae-next %} + ## Example CI configuration for {% data variables.product.prodname_codeql %} analysis This is an example of the series of commands that you might use to analyze a codebase with two supported languages and then upload the results to {% data variables.product.product_name %}. diff --git a/translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md b/translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md index 6101be4897..3b1bc2474b 100644 --- a/translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md +++ b/translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md @@ -190,7 +190,7 @@ Analyzes the code in the {% data variables.product.prodname_codeql %} databases | `--no-upload` | | None. Stops the {% data variables.product.prodname_codeql_runner %} from uploading the results to {% data variables.product.product_name %}. | | `--output-dir` | | Directory where the output SARIF files are stored. The default is in the directory of temporary files. | | `--ram` | | Amount of memory to use when running queries. The default is to use all available memory. | -| `--no-add-snippets` | | None. Excludes code snippets from the SARIF output. |{% ifversion fpt or ghes > 3.1 %} +| `--no-add-snippets` | | None. Excludes code snippets from the SARIF output. |{% ifversion fpt or ghes > 3.1 or ghae %} | `--category` | | Category to include in the SARIF results file for this analysis. A category can be used to distinguish multiple analyses for the same tool and commit, but performed on different languages or different parts of the code. This value will appear in the `.automationDetails.id` property in SARIF v2.1.0. {% endif %} | `--threads` | | Number of threads to use when running queries. The default is to use all available cores. | diff --git a/translations/de-DE/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md b/translations/de-DE/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md index 46ec04b016..b9fbfa6ec3 100644 --- a/translations/de-DE/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md +++ b/translations/de-DE/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md @@ -25,7 +25,7 @@ topics: {% data variables.product.company_short %} performs {% data variables.product.prodname_secret_scanning %} on {% ifversion fpt %}public and private{% endif %} repositories for secret patterns provided by {% data variables.product.company_short %} and {% data variables.product.company_short %} partners. For more information on the {% data variables.product.prodname_secret_scanning %} partner program, see "Secret scanning partner program." -However, there can be situations where you want to scan for other secret patterns in your {% ifversion fpt %}private{% endif %} repositories. For example, you might have a secret pattern that is internal to your organization. For these situations, you can define custom {% data variables.product.prodname_secret_scanning %} patterns in your enterprise, organization, or {% ifversion fpt %}private{% endif %} repository on {% data variables.product.product_name %}. You can define up to 20 custom patterns for each {% ifversion fpt %}private{% endif %} repository, organization, or enterprise account. +However, there can be situations where you want to scan for other secret patterns in your {% ifversion fpt %}private{% endif %} repositories. For example, you might have a secret pattern that is internal to your organization. For these situations, you can define custom {% data variables.product.prodname_secret_scanning %} patterns in your enterprise, organization, or {% ifversion fpt %}private{% endif %} repository on {% data variables.product.product_name %}. You can define up to 100 custom patterns for each organization or enterprise account, and up to 20 custom patterns per {% ifversion fpt %}private{% endif %} repository. {% ifversion ghes < 3.3 or ghae %} {% note %} diff --git a/translations/de-DE/content/code-security/security-advisories/publishing-a-security-advisory.md b/translations/de-DE/content/code-security/security-advisories/publishing-a-security-advisory.md index 2e01e84f53..61a5256053 100644 --- a/translations/de-DE/content/code-security/security-advisories/publishing-a-security-advisory.md +++ b/translations/de-DE/content/code-security/security-advisories/publishing-a-security-advisory.md @@ -61,19 +61,6 @@ Die Veröffentlichung eines Sicherheitshinweises verändert die URL für diesen Wenn Du Informationen in einem von Dir veröffentlichten Sicherheitshinweis aktualisieren oder korrigieren musst, kannst Du den Hinweis bearbeiten. Weitere Informationen findest Du unter „[Einen Sicherheitshinweis bearbeiten](/github/managing-security-vulnerabilities/editing-a-security-advisory)." -## CVE-Identifikationsnummer anfordern - -Personen mit Administratorberechtigungen auf einem Sicherheitshinweis können einen CVE-Identifikationsnummer für den Hinweis anfordern. - -{% data reusables.repositories.request-security-advisory-cve-id %} Weitere Informationen findest Du unter „[Über {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories#cve-identification-numbers)." - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-security %} -{% data reusables.repositories.sidebar-advisories %} -4. Klicke in der Liste „Security Advisories" (Sicherheitshinweise) auf den Hinweis für den Du eine CVE-Identifikationsnummer anfordern möchtest. ![Sicherheitshinweis in der Liste](/assets/images/help/security/security-advisory-in-list.png) -5. Benutze das **Publish advisory** (Hinweis veröffentlichen) Dropdownmenü und klicke auf **Request CVE** (CVE-Identifikationsnummer anfordern). ![CVE-Identifikationsnummer im Dropdownmenü anfordern](/assets/images/help/security/security-advisory-drop-down-request-cve.png) -6. Klicke auf **Request CVE** (CVE-Identifikationsnummer anfordern). ![Dropdownmenü „Request CVE" (CVE-Identifikationsnummer anfordern)](/assets/images/help/security/security-advisory-request-cve-button.png) - ## Einen Sicherheitshinweis veröffentlichen Die Veröffentlichung eines Sicherheitshinweises löscht den temporären privaten Fork für den Sicherheitshinweis. @@ -88,6 +75,17 @@ Die Veröffentlichung eines Sicherheitshinweises löscht den temporären private {% data reusables.repositories.github-reviews-security-advisories %} +## Requesting a CVE identification number (Optional) + +{% data reusables.repositories.request-security-advisory-cve-id %} Weitere Informationen findest Du unter „[Über {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories#cve-identification-numbers)." + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-security %} +{% data reusables.repositories.sidebar-advisories %} +4. Klicke in der Liste „Security Advisories" (Sicherheitshinweise) auf den Hinweis für den Du eine CVE-Identifikationsnummer anfordern möchtest. ![Sicherheitshinweis in der Liste](/assets/images/help/security/security-advisory-in-list.png) +5. Benutze das **Publish advisory** (Hinweis veröffentlichen) Dropdownmenü und klicke auf **Request CVE** (CVE-Identifikationsnummer anfordern). ![CVE-Identifikationsnummer im Dropdownmenü anfordern](/assets/images/help/security/security-advisory-drop-down-request-cve.png) +6. Klicke auf **Request CVE** (CVE-Identifikationsnummer anfordern). ![Dropdownmenü „Request CVE" (CVE-Identifikationsnummer anfordern)](/assets/images/help/security/security-advisory-request-cve-button.png) + ## Weiterführende Informationen - „[Einen Sicherheitshinweis zurückziehen](/github/managing-security-vulnerabilities/withdrawing-a-security-advisory)" diff --git a/translations/de-DE/content/code-security/security-overview/about-the-security-overview.md b/translations/de-DE/content/code-security/security-overview/about-the-security-overview.md index c9d9933f42..3d5c882752 100644 --- a/translations/de-DE/content/code-security/security-overview/about-the-security-overview.md +++ b/translations/de-DE/content/code-security/security-overview/about-the-security-overview.md @@ -6,8 +6,8 @@ redirect_from: - /code-security/security-overview/exploring-security-alerts versions: fpt: '*' + ghae: issue-4554 ghes: '>3.1' - ghae: next type: how_to topics: - Security overview diff --git a/translations/de-DE/content/code-security/security-overview/index.md b/translations/de-DE/content/code-security/security-overview/index.md index 3adfe1802b..88ef0c8e5b 100644 --- a/translations/de-DE/content/code-security/security-overview/index.md +++ b/translations/de-DE/content/code-security/security-overview/index.md @@ -5,8 +5,8 @@ intro: 'View, sort, and filter the security alerts from across your organization product: '{% data reusables.gated-features.security-center %}' versions: fpt: '*' + ghae: issue-4554 ghes: '>3.1' - ghae: next topics: - Security overview - Advanced Security diff --git a/translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md b/translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md index 2088b810a5..ba0e0692cc 100644 --- a/translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md +++ b/translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md @@ -1,11 +1,11 @@ --- title: About dependency review intro: 'Dependency review lets you catch vulnerable dependencies before you introduce them to your environment, and provides information on license, dependents, and age of dependencies.' +product: '{% data reusables.gated-features.dependency-review %}' shortTitle: Dependency review versions: fpt: '*' ghes: '>= 3.2' - product: '{% data reusables.gated-features.dependency-review %}' type: overview topics: - Advanced Security diff --git a/translations/de-DE/content/codespaces/developing-in-codespaces/index.md b/translations/de-DE/content/codespaces/developing-in-codespaces/index.md index 01ff135a2e..7453d3aeb6 100644 --- a/translations/de-DE/content/codespaces/developing-in-codespaces/index.md +++ b/translations/de-DE/content/codespaces/developing-in-codespaces/index.md @@ -15,6 +15,5 @@ children: - /forwarding-ports-in-your-codespace - /changing-the-machine-type-for-your-codespace - /using-codespaces-in-visual-studio-code - - /web-based-editor --- diff --git a/translations/de-DE/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md b/translations/de-DE/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md index f208f0e82c..397afa20e6 100644 --- a/translations/de-DE/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md +++ b/translations/de-DE/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md @@ -30,9 +30,7 @@ A typical workflow for updating a file using {% data variables.product.prodname_ ## Creating or switching branches -1. If the current branch is not shown in the status bar, at the bottom of your codespace, right-click the status bar and select **Source control**. -1. Click the branch name in the status bar. ![The branch in the status bar](/assets/images/help/codespaces/branch-in-status-bar.png) -1. In the drop-down, either click the branch you want to switch to, or enter the name for a new branch and click **Create new branch**. ![Choose from the branch menu](/assets/images/help/codespaces/create-new-branch.png) +{% data reusables.codespaces.create-or-switch-branch %} {% tip %} @@ -64,16 +62,11 @@ If the fetch operation detects new changes on the remote repository, you'll see ## Committing your changes -{% data reusables.codespaces.source-control-display-dark %} -1. To stage your changes, click **+** next to the file you've changed, or next to **Changes** if you've changed multiple files and you want to stage them all. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-stage.png) -1. Type a commit message describing the change you've made. ![Source control side bar with a commit message](/assets/images/help/codespaces/codespaces-commit-commit-message.png) -1. To commit your staged changes, click the check mark at the top the source control side bar. ![Click the check mark icon](/assets/images/help/codespaces/codespaces-commit-checkmark-icon.png) +{% data reusables.codespaces.source-control-commit-changes %} ## Raising a pull request -1. After you've committed changes to your local copy of the repository, click the **Create Pull Request** icon. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-pr-button.png) -1. Check that the local branch and repository you're merging from, and the remote branch and repository you're merging into, are correct. Then give the pull request a title and a description. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-pr.png) -1. Klicke auf **Create** (Erstellen). +{% data reusables.codespaces.source-control-pull-request %} ## Pushing changes to your remote repository diff --git a/translations/de-DE/content/codespaces/index.md b/translations/de-DE/content/codespaces/index.md index 06035cb35d..5c3572bab3 100644 --- a/translations/de-DE/content/codespaces/index.md +++ b/translations/de-DE/content/codespaces/index.md @@ -41,6 +41,7 @@ children: - /managing-codespaces-for-your-organization - /codespaces-reference - /troubleshooting + - /the-githubdev-web-based-editor - /guides --- diff --git a/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md index 6f4696b439..d88d07ea5f 100644 --- a/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md +++ b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md @@ -72,3 +72,7 @@ You can check which access policies are applied to a secret in your organization {% data reusables.github-actions.sidebar-secret %} 1. Die Liste der Geheimnisse enthält alle konfigurierten Berechtigungen und Richtlinien. Ein Beispiel: ![Geheimliste](/assets/images/help/settings/actions-org-secrets-list.png) 1. Weitere Informationen zu den konfigurierten Berechtigungen für jeden geheimen Schlüssel finden Sie unter **Aktualisieren**. + +## Weiterführende Informationen + +- "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)" diff --git a/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md index 5674555da1..914132c857 100644 --- a/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md +++ b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md @@ -26,3 +26,7 @@ To manage which users in your organization can use {% data variables.product.pro {% data reusables.organizations.click-codespaces %} 1. Under "Access and security", select the setting you want for your organization. ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-org-access-and-security-radio-buttons.png) 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 owned by your organization. Repeat for all repositories whose codespaces you want to access other repositories. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) + +## Weiterführende Informationen + +- "[Managing repository access for your codespaces](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces)" diff --git a/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md index b8b2d49b16..dc73838b5a 100644 --- a/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md +++ b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md @@ -19,3 +19,7 @@ When any member of your organization performs an action related to {% data varia ![Audit log with Codespaces information](/assets/images/help/settings/codespaces-audit-log-org.png) The audit log includes details such as who performed the action, what the action was, and when the action was performed. For information on {% data variables.product.prodname_codespaces %} actions, see "[{% data variables.product.prodname_codespaces %} category actions](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#codespaces-category-actions)." + +## Weiterführende Informationen + +- "[Reviewing your security logs for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces)" diff --git a/translations/de-DE/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md b/translations/de-DE/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md index 1449384ffc..c8b3805395 100644 --- a/translations/de-DE/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md +++ b/translations/de-DE/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md @@ -73,3 +73,7 @@ You can update the value of an existing secret, and you can change which reposit {% data reusables.user_settings.codespaces-tab %} 1. Under "Codespaces secrets", to the right of the secret you want to delete, click **Delete**. !["Delete" button](/assets/images/help/settings/codespaces-secret-delete-button.png) 1. Lies die Warnung, dann klicke auf **OK**. ![Confirmation to delete secret](/assets/images/help/settings/codespaces-secret-delete-warning.png) + +## Weiterführende Informationen + +- "[Managing encrypted secrets for your repository and organization for {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces)" diff --git a/translations/de-DE/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md b/translations/de-DE/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md index 57753fbdaa..591a58c22d 100644 --- a/translations/de-DE/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md +++ b/translations/de-DE/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md @@ -29,6 +29,6 @@ Once you enable GPG verification, it will immediately take effect for all your c {% note %} -**Note:** Once you have enabled GPG verification for {% data variables.product.prodname_codespaces %}, you also must append `-s` to each commit in order for it to be signed. To do this in {% data variables.product.prodname_vscode %}, ensure the "Git: Enable Commit Signing" option is enabled from the Settings. +**Note:** Once you have enabled GPG verification for {% data variables.product.prodname_codespaces %}, you also must append `-S` to each commit in order for it to be signed. To do this in {% data variables.product.prodname_vscode %}, ensure the "Git: Enable Commit Signing" option is enabled from the Settings. {% endnote %} diff --git a/translations/de-DE/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md b/translations/de-DE/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md index d79c06de7f..d847d035db 100644 --- a/translations/de-DE/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md +++ b/translations/de-DE/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md @@ -20,3 +20,7 @@ When you enable access and security for a repository owned by your user account, {% data reusables.user_settings.codespaces-tab %} 1. Under "Access and security", select the setting you want for your user account. ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png) 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. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) + +## Weiterführende Informationen + +- "[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/de-DE/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md b/translations/de-DE/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md index 956845aa41..17b2211e31 100644 --- a/translations/de-DE/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md +++ b/translations/de-DE/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md @@ -20,3 +20,7 @@ When you perform an action related to {% data variables.product.prodname_codespa ![security log with Codespaces information](/assets/images/help/settings/codespaces-audit-log.png) The security log includes details on what action occurred and when you performed it. For information about {% data variables.product.prodname_codespaces %} actions, see "[{% data variables.product.prodname_codespaces %} category actions](/github/authenticating-to-github/reviewing-your-security-log#codespaces-category-actions)". + +## Weiterführende Informationen + +- "[Reviewing your organization's audit logs for {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces)" diff --git a/translations/de-DE/content/codespaces/the-githubdev-web-based-editor.md b/translations/de-DE/content/codespaces/the-githubdev-web-based-editor.md new file mode 100644 index 0000000000..bdabef18fc --- /dev/null +++ b/translations/de-DE/content/codespaces/the-githubdev-web-based-editor.md @@ -0,0 +1,106 @@ +--- +title: The github.dev web-based editor +intro: 'Use the github.dev {% data variables.product.prodname_serverless %} from your repository or pull request to create and commit changes.' +versions: + fpt: '*' +type: how_to +miniTocMaxHeadingLevel: 3 +topics: + - Codespaces + - Visual Studio Code + - Developer +shortTitle: Web-based editor +redirect_from: + - /codespaces/developing-in-codespaces/web-based-editor +--- + +{% note %} + +**Note:** The github.dev {% data variables.product.prodname_serverless %} is currently in beta preview. You can provide feedback [in our Discussions](https://github.co/browser-editor-feedback). + +{% endnote %} + +## Informationen zu {% data variables.product.prodname_serverless %} + +The {% data variables.product.prodname_serverless %} introduces a lightweight editing experience that runs entirely in your browser. With the {% data variables.product.prodname_serverless %}, you can navigate files and source code repositories from {% data variables.product.prodname_dotcom %}, and make and commit code changes. You can open any repository, fork, or pull request in the editor. + +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 %} 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. + +## Opening the {% data variables.product.prodname_serverless %} + +You can open any {% data variables.product.prodname_dotcom %} repository in the {% data variables.product.prodname_serverless %} in either of the following ways: + +- Press `.` while browsing any repository or pull request on {% data variables.product.prodname_dotcom %}. +- Change the URL from "github.com" to "github.dev". + +## {% data variables.product.prodname_codespaces %} and the {% data variables.product.prodname_serverless %} + +Both the {% data variables.product.prodname_serverless %} and {% data variables.product.prodname_codespaces %} allow you to edit your code straight from your repository. However, both have slightly different benefits, depending on your use case. + +| | {% data variables.product.prodname_serverless %} | {% data variables.product.prodname_codespaces %} +| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| **Cost** | Kostenlos. | Costs for compute and storage. For information on pricing, see "[Codespaces pricing](/en/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)." | +| **Availability** | Available to everyone on GitHub.com. | Available for organizations using GitHub Team or GitHub Enterprise Cloud. | +| **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. | + +### Continue working on {% data variables.product.prodname_codespaces %} + +You can start your workflow in the {% data variables.product.prodname_serverless %} and continue working on a codespace, provided you have [access to {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces). If you try to access the Run and Debug View or the Terminal, you'll be notified that they are not available in the {% data variables.product.prodname_serverless %}. + +To continue your work in a codespace, click **Continue Working on…** and select **Create New Codespace** to create a codespace on your current branch. Before you choose this option, you must commit any changes. + +![A screenshot that shows the "Continue Working on" button in the UI](/assets/images/help/codespaces/codespaces-continue-working.png) + +## 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. + +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. + +### Neuen Branch erstellen + +{% data reusables.codespaces.create-or-switch-branch %} + Any uncommited changes you have made in your old branch will be available on your new branch. + +### Commit your changes + +{% data reusables.codespaces.source-control-commit-changes %} +5. Once you have committed your changes, they will automatically be pushed to your branch on {% data variables.product.prodname_dotcom %}. +### Create a pull request + +{% data reusables.codespaces.source-control-pull-request %} + +### Working with an existing pull request + +You can use the {% data variables.product.prodname_serverless %} to work with an existing pull request. + +1. Browse to the pull request you'd like to open in the {% data variables.product.prodname_serverless %}. +2. Press `.` to open the pull request in the {% data variables.product.prodname_serverless %}. +3. Once you have made any changes, commit them using the steps in [Commit your changes](#commit-your-changes). Your changes will be committed directly to the branch, it's not necessary to push the changes. + +## 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. + +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. + + +## Problemlösungen + +If you have issues opening the {% data variables.product.prodname_serverless %}, try the following: + +- Make sure you are signed in to {% data variables.product.prodname_dotcom %}. +- Disable any ad blockers. +- Use a non-incognito window in your browser to open 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. diff --git a/translations/de-DE/content/communities/documenting-your-project-with-wikis/about-wikis.md b/translations/de-DE/content/communities/documenting-your-project-with-wikis/about-wikis.md index 7c918ef371..10b91b8b86 100644 --- a/translations/de-DE/content/communities/documenting-your-project-with-wikis/about-wikis.md +++ b/translations/de-DE/content/communities/documenting-your-project-with-wikis/about-wikis.md @@ -34,4 +34,4 @@ Sie können Wikis direkt auf {% data variables.product.product_name %} bearbeite - „[Eine Fußzeile oder Seitenleiste für Dein Wiki erstellen](/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki)“ - „[Wiki-Inhalte bearbeiten](/communities/documenting-your-project-with-wikis/editing-wiki-content)“ - „[Änderungsverlauf eines Wikis anzeigen](/articles/viewing-a-wiki-s-history-of-changes)“ -- „[Wikis durchsuchen](/articles/searching-wikis)“ +- „[Wikis durchsuchen](/search-github/searching-on-github/searching-wikis)“ diff --git a/translations/de-DE/content/communities/moderating-comments-and-conversations/locking-conversations.md b/translations/de-DE/content/communities/moderating-comments-and-conversations/locking-conversations.md index 8ac880f1fd..e92bba89ca 100644 --- a/translations/de-DE/content/communities/moderating-comments-and-conversations/locking-conversations.md +++ b/translations/de-DE/content/communities/moderating-comments-and-conversations/locking-conversations.md @@ -20,7 +20,7 @@ Das Sperren einer Unterhaltung erstellt ein Zeitleistenereignis, das für alle B Solange eine Unterhaltung gesperrt ist, können nur [Personen mit Schreibzugriff](/articles/repository-permission-levels-for-an-organization/) und [Repository-Inhaber und -Mitarbeiter](/articles/permission-levels-for-a-user-account-repository/#collaborator-access-for-a-repository-owned-by-a-user-account) Kommentare hinzufügen, ausblenden und löschen. -Um nach gesperrten Unterhaltungen in einem nicht archivierten Repository zu suchen, kannst Du die Qualifizierer `is:locked` und `archived:false` verwenden. In archivierten Repositorys sind Unterhaltungen automatisch gesperrt. Weitere Informationen findest Du unter „[Issues und Pull Requests durchsuchen](/articles/searching-issues-and-pull-requests#search-based-on-whether-a-conversation-is-locked).“ +Um nach gesperrten Unterhaltungen in einem nicht archivierten Repository zu suchen, kannst Du die Qualifizierer `is:locked` und `archived:false` verwenden. In archivierten Repositorys sind Unterhaltungen automatisch gesperrt. Weitere Informationen findest Du unter „[Issues und Pull Requests durchsuchen](/search-github/searching-on-github/searching-issues-and-pull-requests#search-based-on-whether-a-conversation-is-locked).“ 1. Verfasse optional einen Kommentar, in dem Du erklärst, weshalb Du die Unterhaltung sperrst. 2. Klicke am rechten Rand des Issues respektive Pull Requests oder oberhalb des Kommentarfelds auf der Commit-Seite auf **Lock conversation** (Unterhaltung sperren). ![Link „Lock conversation“ (Unterhaltung sperren)](/assets/images/help/repository/lock-conversation.png) diff --git a/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels.md b/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels.md index dbb3f833c1..f60ad86fe0 100644 --- a/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels.md +++ b/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels.md @@ -12,7 +12,7 @@ topics: shortTitle: Encourage contributions --- -Du kannst die Kennzeichnung `good first issue` (guter erster Issue) in Dein öffentliches Repository übernehmen, damit sie von Personen auf der Suche nach Kennzeichnungen gesehen wird. Weitere Informationen zur Suche nach Kennzeichnungen findest Du unter „[Nach Issues und Pull Requests suchen](/articles/searching-issues-and-pull-requests/#search-by-label).“ +Du kannst die Kennzeichnung `good first issue` (guter erster Issue) in Dein öffentliches Repository übernehmen, damit sie von Personen auf der Suche nach Kennzeichnungen gesehen wird. Weitere Informationen zur Suche nach Kennzeichnungen findest Du unter „[Nach Issues und Pull Requests suchen](/search-github/searching-on-github/searching-issues-and-pull-requests/#search-by-label).“ {% data variables.product.prodname_dotcom %} verwendet einen Algorithmus, um die am besten geeigneten Issues in jedem Repository zu ermitteln und sie an verschiedenen Stellen auf {% data variables.product.prodname_dotcom_the_website %} anzuzeigen. Wird die Kennzeichnung `good first issue` (guter erster Issue) hinzugefügt, ist es wahrscheinlicher, dass Deine Issues angezeigt werden. @@ -24,4 +24,4 @@ Du kannst die Kennzeichnung `good first issue` (guter erster Issue) in Dein öff ## Weiterführende Informationen - „[Informationen zu Kennzeichnungen](/articles/about-labels)“ -- „[Nach Repositorys suchen](/articles/searching-for-repositories)“ +- „[Nach Repositorys suchen](/search-github/searching-on-github/searching-for-repositories)“ diff --git a/translations/de-DE/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md b/translations/de-DE/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md index 08f433a390..923a91131d 100644 --- a/translations/de-DE/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md +++ b/translations/de-DE/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md @@ -42,6 +42,7 @@ Using the web application flow, the process to identify users on your site is: If you select **Request user authorization (OAuth) during installation** when creating or modifying your app, step 1 will be completed during app installation. For more information, see "[Authorizing users during installation](/apps/installing-github-apps/#authorizing-users-during-installation)." ### 1. Request a user's GitHub identity +Direct the user to the following URL in their browser: GET {% data variables.product.oauth_host_code %}/login/oauth/authorize @@ -77,6 +78,8 @@ Exchange this `code` for an access token. When expiring tokens are enabled, the Expiring user tokens are currently an optional feature and subject to change. To opt-in to the user-to-server token expiration feature, see "[Activating optional features for apps](/developers/apps/activating-optional-features-for-apps)." +Make a request to the following endpoint to receive an access token: + POST {% data variables.product.oauth_host_code %}/login/oauth/access_token #### Parameters diff --git a/translations/de-DE/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md b/translations/de-DE/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md index 753b85353d..f68d96ceac 100644 --- a/translations/de-DE/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md +++ b/translations/de-DE/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md @@ -32,7 +32,7 @@ Different server-to-server request rate limits apply to {% data variables.produc ### {% data variables.product.prodname_ghe_cloud %} server-to-server rate limits -{% data variables.product.prodname_github_apps %} that are installed on an organization or repository owned by a {% data variables.product.prodname_ghe_cloud %} account and make server-to-server requests have a rate limit of 15,000 requests per hour. +{% data variables.product.prodname_github_apps %} that are installed on an organization or repository owned by a {% data variables.product.prodname_ghe_cloud %} account and make server-to-server requests have a rate limit of 15,000 requests per hour per organization for organization installations or per repository for repository installations. {% endif %} diff --git a/translations/de-DE/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md b/translations/de-DE/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md index 908868856e..280f08b140 100644 --- a/translations/de-DE/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md +++ b/translations/de-DE/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md @@ -78,19 +78,29 @@ Exchange this `code` for an access token: By default, the response takes the following form: - access_token={% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&token_type=bearer +``` +access_token={% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&scope=repo%2Cgist&token_type=bearer +``` -You can also receive the content in different formats depending on the Accept header: +{% data reusables.apps.oauth-auth-vary-response %} - Accept: application/json - {"access_token":"{% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "scope":"repo,gist", "token_type":"bearer"} - - Accept: application/xml - - bearer - repo,gist - {% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %} - +```json +Accept: application/json +{ + "access_token":"{% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", + "scope":"repo,gist", + "token_type":"bearer" +} +``` + +```xml +Accept: application/xml + + bearer + repo,gist + {% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %} + +``` ### 3. Use the access token to access the API @@ -138,27 +148,35 @@ Your app must request a user verification code and verification URL that the app #### Response -{% ifversion fpt %} - ```JSON - { - "device_code": "3584d83530557fdd1f46af8289938c8ef79f9dc5", - "user_code": "WDJB-MJHT", - "verification_uri": "https://github.com/login/device", - "expires_in": 900, - "interval": 5 - } - ``` -{% else %} - ```JSON - { - "device_code": "3584d83530557fdd1f46af8289938c8ef79f9dc5", - "user_code": "WDJB-MJHT", - "verification_uri": "http(s)://[hostname]/login/device", - "expires_in": 900, - "interval": 5 - } - ``` -{% endif %} +By default, the response takes the following form: + +``` +device_code=3584d83530557fdd1f46af8289938c8ef79f9dc5&expires_in=900&interval=5&user_code=WDJB-MJHT&verification_uri=https%3A%2F%{% data variables.product.product_url %}%2Flogin%2Fdevice +``` + +{% data reusables.apps.oauth-auth-vary-response %} + +```json +Accept: application/json +{ + "device_code": "3584d83530557fdd1f46af8289938c8ef79f9dc5", + "user_code": "WDJB-MJHT", + "verification_uri": "{% data variables.product.oauth_host_code %}/login/device", + "expires_in": 900, + "interval": 5 +} +``` + +```xml +Accept: application/xml + + 3584d83530557fdd1f46af8289938c8ef79f9dc5 + WDJB-MJHT + {% data variables.product.oauth_host_code %}/login/device + 900 + 5 + +``` #### Response parameters @@ -196,14 +214,32 @@ Once the user has authorized, the app will receive an access token that can be u #### Response +By default, the response takes the following form: + +``` +access_token={% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&token_type=bearer&scope=repo%2Cgist +``` + +{% data reusables.apps.oauth-auth-vary-response %} + ```json +Accept: application/json { "access_token": "{% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "token_type": "bearer", - "scope": "user" + "scope": "repo,gist" } ``` +```xml +Accept: application/xml + + {% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %} + bearer + gist,repo + +``` + ### Rate limits for the device flow When a user submits the verification code on the browser, there is a rate limit of 50 submissions in an hour per application. diff --git a/translations/de-DE/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md b/translations/de-DE/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md index b266ea4dce..5185473a47 100644 --- a/translations/de-DE/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md +++ b/translations/de-DE/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md @@ -25,7 +25,7 @@ Public installation flows have a landing page to enable other people besides the ## Private installation flow -Private installation flows allow only the owner of a GitHub App to install it. Limited information about the GitHub App will still exist on a public page, but the **Install** button will only be available to organization administrators or the user account if the GitHub App is owned by an individual account. Private{% ifversion ghes < 3.2 or ghae %}, or internal,{% endif %} GitHub Apps can only be installed on the user or organization account of the owner. +Private installation flows allow only the owner of a GitHub App to install it. Limited information about the GitHub App will still exist on a public page, but the **Install** button will only be available to organization administrators or the user account if the GitHub App is owned by an individual account. {% ifversion fpt or ghes > 3.1 or ghae-next %}Private {% else %}Private (also known as internal){% endif %} GitHub Apps can only be installed on the user or organization account of the owner. ## Changing who can install your GitHub App @@ -36,5 +36,5 @@ To change who can install the GitHub App: {% data reusables.user-settings.github_apps %} 3. Select the GitHub App whose installation option you want to change. ![App selection](/assets/images/github-apps/github_apps_select-app.png) {% data reusables.user-settings.github_apps_advanced %} -5. Depending on the installation option of your GitHub App, click either **Make public** or **Make {% ifversion fpt or ghes > 3.1 %}private{% else %}internal{% endif %}**. ![Button to change the installation option of your GitHub App](/assets/images/github-apps/github_apps_make_public.png) -6. Depending on the installation option of your GitHub App, click either **Yes, make this GitHub App public** or **Yes, make this GitHub App {% ifversion fpt or ghes > 3.1 %}private{% else %}internal{% endif %}**. ![Button to confirm the change of your installation option](/assets/images/github-apps/github_apps_confirm_installation_option.png) +5. Depending on the installation option of your GitHub App, click either **Make public** or **Make {% ifversion fpt or ghes > 3.1 or ghae-next %}private{% else %}internal{% endif %}**. ![Button to change the installation option of your GitHub App](/assets/images/github-apps/github_apps_make_public.png) +6. Depending on the installation option of your GitHub App, click either **Yes, make this GitHub App public** or **Yes, make this GitHub App {% ifversion fpt or ghes < 3.2 %}internal{% else %}private{% endif %}**. ![Button to confirm the change of your installation option](/assets/images/github-apps/github_apps_confirm_installation_option.png) diff --git a/translations/de-DE/content/developers/github-marketplace/github-marketplace-overview/about-marketplace-badges.md b/translations/de-DE/content/developers/github-marketplace/github-marketplace-overview/about-marketplace-badges.md index 97a25fd76f..4050a58077 100644 --- a/translations/de-DE/content/developers/github-marketplace/github-marketplace-overview/about-marketplace-badges.md +++ b/translations/de-DE/content/developers/github-marketplace/github-marketplace-overview/about-marketplace-badges.md @@ -30,7 +30,7 @@ Some apps on the {% data variables.product.prodname_marketplace %} have the {% o For more information about the requirements for listing an app on {% data variables.product.prodname_marketplace %}, see "[Requirements for listing an app on {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)." -For information on finding apps to use, see "[Searching {% data variables.product.prodname_marketplace %}](/github/searching-for-information-on-github/searching-github-marketplace)." +For information on finding apps to use, see "[Searching {% data variables.product.prodname_marketplace %}](/search-github/searching-on-github/searching-github-marketplace)." ## For GitHub actions diff --git a/translations/de-DE/content/developers/overview/index.md b/translations/de-DE/content/developers/overview/index.md index a979f7f2a7..05b7aa9731 100644 --- a/translations/de-DE/content/developers/overview/index.md +++ b/translations/de-DE/content/developers/overview/index.md @@ -8,7 +8,6 @@ versions: children: - /about-githubs-apis - /managing-deploy-keys - - /viewing-deployment-history - /using-ssh-agent-forwarding - /secret-scanning-partner-program - /replacing-github-services diff --git a/translations/de-DE/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md b/translations/de-DE/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md index 4b48b39dde..956f2d5b62 100644 --- a/translations/de-DE/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md +++ b/translations/de-DE/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md @@ -190,7 +190,7 @@ Activity related to a branch protection rule. For more information, see "[About {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} -`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 %}`github` {% elsif ghes > 3.0 %}`github-enterprise` {% else %}empty {% endif %}for all other actions. +`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 %}`github`{% elsif ghes > 3.0 or ghae-next %}`github-enterprise`{% else %}empty{% endif %} for all other actions. ### Webhook payload example @@ -1032,24 +1032,29 @@ Deliveries for `review_requested` and `review_request_removed` events will have ### Webhook payload object -| Schlüssel | Typ | Beschreibung | -| -------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `ref` | `string` | The full [`git ref`](/rest/reference/git#refs) that was pushed. Example: `refs/heads/main`. | -| `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. | -| `commits` | `array` | An array of commit objects describing the pushed commits. (The array includes a maximum of 20 commits. If necessary, you can use the [Commits API](/rest/reference/repos#commits) to fetch additional commits. This limit is applied to timeline events only and isn't applied to webhook deliveries.) | -| `commits[][id]` | `string` | The SHA of the commit. | -| `commits[][timestamp]` | `string` | The ISO 8601 timestamp of the commit. | -| `commits[][message]` | `string` | Die Commit-Mitteilung. | -| `commits[][author]` | `Objekt` | 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` | `Objekt` | The user who pushed the commits. | +| Schlüssel | Typ | Beschreibung | +| -------------------------- | --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `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. | +| `erstellt am` | `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` | `Objekt` | 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.) The array includes a maximum of 20 commits. If necessary, you can use the [Commits API](/rest/reference/repos#commits) to fetch additional commits. This limit is applied to timeline events only and isn't applied to webhook deliveries. | +| `commits[][id]` | `string` | The SHA of the commit. | +| `commits[][timestamp]` | `string` | The ISO 8601 timestamp of the commit. | +| `commits[][message]` | `string` | Die Commit-Mitteilung. | +| `commits[][author]` | `Objekt` | 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` | `Objekt` | The user who pushed the commits. | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} diff --git a/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md b/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md index 27a26045f6..51ad66b9c2 100644 --- a/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md +++ b/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md @@ -53,7 +53,7 @@ You can share your feedback about {% data variables.product.prodname_discussions ## Weiterführende Informationen - "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)" -- "[Searching discussions](/github/searching-for-information-on-github/searching-discussions)" +- "[Searching discussions](/search-github/searching-on-github/searching-discussions)" - „[Über Benachrichtigungen](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" - „[Kommentare und Unterhaltungen moderieren](/communities/moderating-comments-and-conversations)“ - „[Deine Sicherheit auf {% data variables.product.prodname_dotcom %} aufrechterhalten](/communities/maintaining-your-safety-on-github)" diff --git a/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md b/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md index 8eeac8cd04..2122c5a6f9 100644 --- a/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md +++ b/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md @@ -2,7 +2,7 @@ title: Collaborating with maintainers using discussions shortTitle: Collaborating with maintainers intro: 'You can contribute to the goals, plans, health, and community for a project on {% data variables.product.product_name %} by communicating with the maintainers of the project in a discussion.' -permissions: People with read permissions to a repository can start and participate in discussions in the repository. +permissions: 'People with read access to a repository can start and participate in discussions in the repository. {% data reusables.enterprise-accounts.emu-permission-interact %}' versions: fpt: '*' --- @@ -32,7 +32,7 @@ To collaborate with maintainers in discussions, a repository administrator or pr ## Filtering the list of discussions -You can search for discussions and filter the list of discussions in a repository. For more information, see "[Searching discussions](/github/searching-for-information-on-github/searching-discussions)." +You can search for discussions and filter the list of discussions in a repository. For more information, see "[Searching discussions](/search-github/searching-on-github/searching-discussions)." {% data reusables.repositories.navigate-to-repo %} {% data reusables.discussions.discussions-tab %} diff --git a/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md b/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md index 1b85582546..41e768e2ad 100644 --- a/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md +++ b/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md @@ -1,7 +1,7 @@ --- title: Participating in a discussion intro: 'You can converse with the community and maintainers in a forum within the repository for a project on {% data variables.product.product_name %}.' -permissions: People with read permissions to a repository can participate in discussions in the repository. +permissions: 'People with read access to a repository can participate in discussions in the repository. {% data reusables.enterprise-accounts.emu-permission-interact %}' versions: fpt: '*' shortTitle: Participate in discussion diff --git a/translations/de-DE/content/discussions/guides/finding-discussions-across-multiple-repositories.md b/translations/de-DE/content/discussions/guides/finding-discussions-across-multiple-repositories.md index fa24cdd98d..644e67fa66 100644 --- a/translations/de-DE/content/discussions/guides/finding-discussions-across-multiple-repositories.md +++ b/translations/de-DE/content/discussions/guides/finding-discussions-across-multiple-repositories.md @@ -15,6 +15,6 @@ shortTitle: Find discussions ## Weiterführende Informationen -- "[Searching discussions](/github/searching-for-information-on-github/searching-discussions)" +- "[Searching discussions](/search-github/searching-on-github/searching-discussions)" - "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)" - "[Managing discussions for your community](/discussions/managing-discussions-for-your-community)" diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md index 7256314c3b..8f80897a52 100644 --- a/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md +++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md @@ -8,12 +8,6 @@ redirect_from: shortTitle: Starter assignment --- -{% note %} - -**Note:** The Git & {% data variables.product.company_short %} starter assignment is in beta and subject to change. - -{% endnote %} - The Git & {% data variables.product.company_short %} starter assignment is a pre-made course that summarizes the basics of Git and {% data variables.product.company_short %} and links students to resources to learn more about specific topics. ## Vorrausetzungen diff --git a/translations/de-DE/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md b/translations/de-DE/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md index 348e408732..44bc71fa3e 100644 --- a/translations/de-DE/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md +++ b/translations/de-DE/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md @@ -1,6 +1,7 @@ --- title: 'Möglichkeiten finden, um zu Open-Source auf GitHub beizutragen' intro: 'Du kannst Möglichkeiten finden, um zu Open-Source-Projekten auf {% data variables.product.product_name %} beizutragen, die für Dich relevant sind.' +permissions: '{% data reusables.enterprise-accounts.emu-permission-interact %}' redirect_from: - /articles/where-can-i-find-open-source-projects-to-work-on/ - /articles/finding-interesting-projects-on-github/ @@ -19,7 +20,7 @@ shortTitle: Contribute to open source ## Relevante Projekte finden -Wenn es ein bestimmtes Thema gibt, das Dich interessiert, besuche `github.com/topics/`. Wenn Du Dich zum Beispiel für Maschinelles Lernen (machine learning) interessierst, kannst Du auf https://github.com/topics/machine-learning relevante Projekte und gute erste Issues finden. Du kannst beliebte Themen durchsuchen, indem Du [Themen](https://github.com/topics) besuchst. Du kannst auch nach Repositories suchen, die zu einem Thema passen, das Dich interessiert. Weitere Informationen finden Sie unter „[Nach Repositorys suchen](/articles/searching-for-repositories/#search-by-topic)“. +Wenn es ein bestimmtes Thema gibt, das Dich interessiert, besuche `github.com/topics/`. Wenn Du Dich zum Beispiel für Maschinelles Lernen (machine learning) interessierst, kannst Du auf https://github.com/topics/machine-learning relevante Projekte und gute erste Issues finden. Du kannst beliebte Themen durchsuchen, indem Du [Themen](https://github.com/topics) besuchst. Du kannst auch nach Repositories suchen, die zu einem Thema passen, das Dich interessiert. Weitere Informationen findest Du unter „[Nach Repositorys suchen](/search-github/searching-on-github/searching-for-repositories#search-by-topic).“ Wenn Du auf {% data variables.product.product_name %} aktiv warst, findest Du personalisierte Empfehlungen für Projekte und gute erste Themen basierend auf Deinen bisherigen Beiträgen, Sternen und andere Aktivitäten unter [Erkunden](https://github.com/explore). Du kannst Dich auch für den 'Erkunden'-Newsletter anmelden, um basierend auf Deinen Interessen E-Mails zu erhalten mit Möglichkeiten für Beiträge zu {% data variables.product.product_name %}. Um Dich anzumelden, siehe ['Erkunden' E-Mail-Newsletter](https://github.com/explore/subscribe). diff --git a/translations/de-DE/content/get-started/exploring-projects-on-github/following-people.md b/translations/de-DE/content/get-started/exploring-projects-on-github/following-people.md index 94a4cdcb46..5ac9708bfc 100644 --- a/translations/de-DE/content/get-started/exploring-projects-on-github/following-people.md +++ b/translations/de-DE/content/get-started/exploring-projects-on-github/following-people.md @@ -1,6 +1,7 @@ --- title: Personen folgen intro: 'Sie können Personen auf {% data variables.product.product_name %} folgen, um Benachrichtigungen über ihre Aktivitäten zu erhalten{% ifversion fpt %} und Projekte in ihren Communitys zu entdecken{% endif %}.' +permissions: '{% data reusables.enterprise-accounts.emu-permission-follow %}' redirect_from: - /articles/following-people - /github/getting-started-with-github/following-people diff --git a/translations/de-DE/content/get-started/getting-started-with-git/associating-text-editors-with-git.md b/translations/de-DE/content/get-started/getting-started-with-git/associating-text-editors-with-git.md index d3c35b544b..a08b55de2b 100644 --- a/translations/de-DE/content/get-started/getting-started-with-git/associating-text-editors-with-git.md +++ b/translations/de-DE/content/get-started/getting-started-with-git/associating-text-editors-with-git.md @@ -61,6 +61,7 @@ shortTitle: Associate text editors ## Atom als Editor verwenden 1. Installiere [Atom](https://atom.io/). Weitere Informationen findest Du unter „[Installieren von Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" in der Atom-Dokumentation. +{% data reusables.command_line.open_the_multi_os_terminal %} 3. Geben Sie den folgenden Befehl ein: ```shell $ git config --global core.editor "atom --wait" diff --git a/translations/de-DE/content/get-started/learning-about-github/access-permissions-on-github.md b/translations/de-DE/content/get-started/learning-about-github/access-permissions-on-github.md index 15d359b92d..cc832e8d7c 100644 --- a/translations/de-DE/content/get-started/learning-about-github/access-permissions-on-github.md +++ b/translations/de-DE/content/get-started/learning-about-github/access-permissions-on-github.md @@ -36,6 +36,8 @@ Organisationsmitglieder können folgende Rollen haben: *Inhaber*{% ifversion fpt *Enterprise-Inhaber* haben die endgültige Kontrolle über das Enterprise-Konto und können sämtliche Aktionen im Enterprise-Konto durchführen. *Abrechnungsmanager* können die Abrechnungseinstellungen Deines Enterprise-Kontos verwalten. Mitglieder und externe Mitarbeiter von Organisationen im Besitz Deines Enterprise-Kontos sind automatisch Mitglieder des Enterprise-Kontos, aber sie haben keinen Zugriff auf das Enterprise-Konto selbst oder dessen Einstellungen. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise)." +If an enterprise uses {% data variables.product.prodname_emus %}, members are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and are fully managed by the identity provider. The {% data variables.product.prodname_managed_users %} have read-only access to repositories that are not a part of their enterprise and cannot interact with users that are not also members of the enterprise. Within the organizations owned by the enterprise, the {% data variables.product.prodname_managed_users %} can be granted the same granular access levels available for regular organizations. For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." + {% data reusables.gated-features.enterprise-accounts %} {% endif %} diff --git a/translations/de-DE/content/get-started/learning-about-github/githubs-products.md b/translations/de-DE/content/get-started/learning-about-github/githubs-products.md index 09638abe35..cb7307d97b 100644 --- a/translations/de-DE/content/get-started/learning-about-github/githubs-products.md +++ b/translations/de-DE/content/get-started/learning-about-github/githubs-products.md @@ -102,6 +102,7 @@ Zusätzlich zu den mit {% data variables.product.prodname_team %} verfügbaren F - 50 GB {% data variables.product.prodname_registry %}-Speicher - Access control for {% data variables.product.prodname_pages %} sites. For more information, see Changing the visibility of your {% data variables.product.prodname_pages %} site" - A service level agreement for 99.9% monthly uptime +- The option to configure your enterprise for {% data variables.product.prodname_emus %}, so you can provision and manage members with your identity provider and restrict your member's contributions to just your enterprise. For more information, see "About {% data variables.product.prodname_emus %}." - Die Option, die Richtlinien und Abrechnungen für mehrere {% data variables.product.prodname_dotcom_the_website %}-Organisationen mit Enterprise-Konto zentral zu verwalten. Weitere Informationen findest Du unter "About enterprise accounts" (Über Enterprise-Konten). Du kannst eine Testversion einrichten, um {% data variables.product.prodname_ghe_cloud %} zu testen. Weitere Informationen findest Du unter „Eine Testversion von {% data variables.product.prodname_ghe_cloud %} einrichten.“ diff --git a/translations/de-DE/content/get-started/learning-about-github/types-of-github-accounts.md b/translations/de-DE/content/get-started/learning-about-github/types-of-github-accounts.md index 0a5e049dff..6db60d1c6c 100644 --- a/translations/de-DE/content/get-started/learning-about-github/types-of-github-accounts.md +++ b/translations/de-DE/content/get-started/learning-about-github/types-of-github-accounts.md @@ -64,6 +64,14 @@ Jede Person, die {% data variables.product.product_location %} benutzt, hat ihr {% endif %} +{% ifversion fpt %} +### {% data variables.product.prodname_emus %} + +With {% data variables.product.prodname_emus %}, instead of using your personal account, members of an {% data variables.product.prodname_emu_enterprise %} are provisioned accounts using the enterprise's identity provider (IdP). {% data variables.product.prodname_managed_users_caps %} authenticate using their IdP instead of a {% data variables.product.prodname_dotcom_the_website %} username and password. + +{% data variables.product.prodname_managed_users_caps %} can only interact with users, repositories, and organizations that are part of their enterprise. {% data variables.product.prodname_managed_users_caps %} have read-only access to the rest of {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." +{% endif %} + ## Organisations-Konten Organisationen sind gemeinsame Konten, in denen Personengruppen projektübergreifend zusammenarbeiten können. Inhaber und Administratoren können den Mitgliederzugriff auf Daten und Projekte der Organisation mit komplexen Sicherheits- und Administrationsfunktionen verwalten. diff --git a/translations/de-DE/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md b/translations/de-DE/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md index 31792b1f98..d1c30393f9 100644 --- a/translations/de-DE/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md +++ b/translations/de-DE/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md @@ -18,16 +18,19 @@ This guide will walk you through setting up, configuring and managing your {% da The main difference between the products is that {% data variables.product.prodname_ghe_cloud %} is hosted by {% data variables.product.prodname_dotcom %}, while {% data variables.product.prodname_ghe_server %} is self-hosted. -Within the {% data variables.product.prodname_ghe_cloud %} product, there are two different types of account that you can use: +With {% data variables.product.prodname_ghe_cloud %}, you have the option of using {% data variables.product.prodname_emus %}. {% data reusables.enterprise-accounts.emu-short-summary %} + +If you choose to let your members create and manage their own user accounts instead, there are two types of accounts you can use with {% data variables.product.prodname_ghe_cloud %}: - A single organization account - An enterprise account that contains multiple organizations -In either scenario, your users will use their own self-created user account and you'll invite them to join. ### 1. Understanding the differences between an organization account and enterprise account Both organization and enterprise accounts are available with {% data variables.product.prodname_ghe_cloud %}. An organization is a shared account where groups of people can collaborate across many projects at once, and owners and administrators can manage access to data and projects. An enterprise account enables collaboration between multiple organizations, and allows owners to centrally manage policy, billing and security for these organizations. For more information on the differences, see "[Organizations and enterprise accounts](/organizations/collaborating-with-groups-in-organizations/about-organizations#organizations-and-enterprise-accounts)." + + If you choose an enterprise account, keep in mind that some policies can be set only at an organization level, while others can be enforced for all organizations in an enterprise. Once you choose the account type you would like, you can proceed to setting up your account. In each of the sections in this guide, proceed to either the single organization or enterprise account section based on your account type. @@ -86,6 +89,11 @@ You can set permissions and member roles, create and manage teams, and give peop ### Managing members of an enterprise account Managing members of an enterprise is separate from managing members or teams in an organization. It is important to note that enterprise owners or administrators cannot access organization-level settings or manage members for organizations in their enterprise unless they are made an organization owner. For more information, see the above section, "[Managing members and teams in your organization](#managing-members-and-teams-in-your-organization)." + +If your enterprise uses {% data variables.product.prodname_emus %}, your members are fully managed through your identity provider. Adding members, making changes to their membership, and assigning roles is all managed using your IdP. For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." + +If your enterprise does not use {% data variables.product.prodname_emus %}, follow the steps below. + #### 1. Assigning roles in an enterprise By default, everyone in an enterprise is a member of the enterprise. There are also administrative roles, including enterprise owner and billing manager, that have different levels of access to enterprise settings and data. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)." #### 2. Inviting people to manage your enterprise @@ -97,6 +105,10 @@ To audit access to enterprise-owned resources or user license usage, you can vie ## Part 4: Managing security with {% data variables.product.prodname_ghe_cloud %} +* [Managing security for a single organization](#managing-security-for-a-single-organization) +* [Managing security for an {% data variables.product.prodname_emu_enterprise %}](#managing-security-for-an-enterprise-with-managed-users) +* [Managing security for an enterprise account without {% data variables.product.prodname_managed_users %}](#managing-security-for-an-enterprise-account-without-managed-users) + ### Managing security for a single organization You can help keep your organization secure by requiring two-factor authentication, configuring security features, reviewing your organization's audit log and integrations, and enabling SAML single sign-on and team synchronization. #### 1. Requiring two-factor authentication @@ -113,8 +125,28 @@ Organization owners can choose to disable, enable but not enforce, or enable and #### 5. Teamsynchronisierung für Deine Organisation verwalten Organization owners can enable team synchronization between your identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organization owners and team maintainers to connect teams in your organization with IdP groups. Weitere Informationen findest Du unter „[Teamsynchronisation für Deine Organisation verwalten](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)." -### Managing security for an enterprise account with multiple organizations +### Managing security for an {% data variables.product.prodname_emu_enterprise %} + +With {% data variables.product.prodname_emus %}, access and identity is managed centrally through your identity provider. Two-factor authentication and other login requirements should be enabled and enforced on your IdP. + +#### 1. Enabling and SAML single sign-on and provisioning in your {% data variables.product.prodname_emu_enterprise %} + +In an {% data variables.product.prodname_emu_enterprise %}, all members are provisioned and managed by your identity provider. You must enable SAML SSO and SCIM provisioning before you can start using your enterprise. For more information on configuring SAML SSO and provisioning for an {% data variables.product.prodname_emu_enterprise %}, see "[Configuring SAML single sign-on for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." + +#### 2. Managing teams in your {% data variables.product.prodname_emu_enterprise %} with your identity provider + +You can connect teams in your organizations to security groups in your identity provider, managing membership of your teams and access to repositories through your IdP. For more information, see "[Managing team memberships with identity provider groups](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)." + +#### 3. Managing allowed IP addresses for organizations in your {% data variables.product.prodname_emu_enterprise %} + +You can configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your {% data variables.product.prodname_emu_enterprise %}. Weiter Informationen findest Du unter „[Sicherheitseinstellungen für Dein Enterprise-Konto erzwingen](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-security-settings-in-your-enterprise-account#managing-allowed-ip-addresses-for-organizations-in-your-enterprise-account)." + +#### 4. Enforcing policies for Advanced Security features in your {% data variables.product.prodname_emu_enterprise %} +{% data reusables.getting-started.enterprise-advanced-security %} + +### Managing security for an enterprise account without {% data variables.product.prodname_managed_users %} To manage security for your enterprise, you can require two-factor authentication, manage allowed IP addresses, enable SAML single sign-on and team synchronization at an enterprise level, and sign up for and enforce GitHub Advanced Security features. + #### 1. Requiring two-factor authentication and managing allowed IP addresses for organizations in your enterprise account Enterprise-Inhaber können vorschreiben, dass Organisationsmitglieder, Abrechnungsmanager und externe Mitarbeiter in allen Organisationen eines Enterprise-Kontos die Zwei-Faktor-Authentifizierung (2FA) für den Schutz ihrer persönlichen Konten verwenden. Before doing so, we recommend notifying all who have access to organizations in your enterprise. You can also configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account. @@ -126,7 +158,7 @@ You can centrally manage access to your enterprise's resources, organization mem You can enable and manage team sychronization between an identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organizations owned by your enterprise account to manage team membership with IdP groups. For more information, see "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/managing-team-synchronization-for-organizations-in-your-enterprise-account)." #### 4. Enforcing policies for Advanced Security features in your enterprise account -If you have a GitHub Advanced Security license for your enterprise account, you can enforce policies to manage {% data variables.product.prodname_dotcom %} Advanced Security features for organizations owned by an enterprise account. For more information, see "[Enforcing policies for Advanced Security in your enterprise account](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-policies-for-advanced-security-in-your-enterprise-account)." +{% data reusables.getting-started.enterprise-advanced-security %} ## Part 5: Managing organization and enterprise level policies and settings diff --git a/translations/de-DE/content/get-started/quickstart/be-social.md b/translations/de-DE/content/get-started/quickstart/be-social.md index 04bcfc9885..97ef03c615 100644 --- a/translations/de-DE/content/get-started/quickstart/be-social.md +++ b/translations/de-DE/content/get-started/quickstart/be-social.md @@ -6,6 +6,7 @@ redirect_from: - /github/getting-started-with-github/be-social - /github/getting-started-with-github/quickstart/be-social intro: 'Sie können mit Personen, Repositorys und Organisationen auf {% data variables.product.prodname_dotcom %} interagieren. Auf Deinem persönlichen Dashboard kannst Du sehen, woran andere gerade arbeiten und mit wem sie sich vernetzen.' +permissions: '{% data reusables.enterprise-accounts.emu-permission-interact %}' versions: fpt: '*' ghes: '*' diff --git a/translations/de-DE/content/get-started/quickstart/fork-a-repo.md b/translations/de-DE/content/get-started/quickstart/fork-a-repo.md index 405b349d10..2bd2ba6cd0 100644 --- a/translations/de-DE/content/get-started/quickstart/fork-a-repo.md +++ b/translations/de-DE/content/get-started/quickstart/fork-a-repo.md @@ -7,6 +7,7 @@ redirect_from: - /github/getting-started-with-github/fork-a-repo - /github/getting-started-with-github/quickstart/fork-a-repo intro: 'Ein Fork ist eine Kopie eines Repositorys. Durch das Forken eines Repositorys kannst Du Änderungen uneingeschränkt testen, ohne Auswirkungen auf das Originalprojekt.' +permissions: '{% data reusables.enterprise-accounts.emu-permission-fork %}' versions: fpt: '*' ghes: '*' diff --git a/translations/de-DE/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md b/translations/de-DE/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md index 2062d640d1..0494b9e592 100644 --- a/translations/de-DE/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md +++ b/translations/de-DE/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md @@ -18,7 +18,7 @@ shortTitle: Enterprise Server trial Sie können eine Testversion anfordern und {% data variables.product.prodname_ghe_server %} 45 Tage lang kostenlos testen. Deine Testversion wird als virtuelle Appliance installiert, wobei Du wählen kannst, ob sie lokal oder in der Cloud bereitgestellt wird. Eine Liste der unterstützten Visualisierungsplattformen findest Du unter „[GitHub Enterprise Server-Instanz einrichten](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance).“ -{% ifversion ghes %}{% data variables.product.prodname_dependabot %}{% else %}Security{% endif %} alerts and {% data variables.product.prodname_github_connect %} are not currently available in trials of {% data variables.product.prodname_ghe_server %}. Kontaktiere {% data variables.contact.contact_enterprise_sales %} für eine Vorstellung dieser Funktionen. For more information about these features, see "About alerts for vulnerable dependencies" and "[Connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)." +{% ifversion ghes %}{% data variables.product.prodname_dependabot %}{% else %}Security{% endif %} alerts and {% data variables.product.prodname_github_connect %} are not currently available in trials of {% data variables.product.prodname_ghe_server %}. Kontaktiere {% data variables.contact.contact_enterprise_sales %} für eine Vorstellung dieser Funktionen. For more information about these features, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" and "[Connecting your enterprise account to {% data variables.product.prodname_dotcom_the_website %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." Testversionen sind auch für {% data variables.product.prodname_ghe_cloud %} verfügbar. Weitere Informationen findest Du unter „[Eine Testversion von {% data variables.product.prodname_ghe_cloud %} einrichten](/articles/setting-up-a-trial-of-github-enterprise-cloud).“ diff --git a/translations/de-DE/content/get-started/using-git/dealing-with-special-characters-in-branch-and-tag-names.md b/translations/de-DE/content/get-started/using-git/dealing-with-special-characters-in-branch-and-tag-names.md new file mode 100644 index 0000000000..e8c3daae8b --- /dev/null +++ b/translations/de-DE/content/get-started/using-git/dealing-with-special-characters-in-branch-and-tag-names.md @@ -0,0 +1,48 @@ +--- +title: Dealing with special characters in branch and tag names +intro: 'Git is very permissive about what characters are allowed in branch and tag names. When using Git from a command-line shell, you may need to escape or quote special characters.' +versions: + fpt: '*' + ghes: '*' + ghae: '*' +shortTitle: Special characters in names +--- + +## About branch and tag names + +Most repositories use simple branch names, such as `main` or `update-icons`. Tag names also usually follow a basic format, such as a version number like `v1.2.3`. Both branch names and tag names may also use the path separator (`/`) for structure, for example `area/item` or `level-1/level-2/level-3`. Other than some exceptions — such as not starting or ending a name with a slash, or having consecutive slashes in the name — Git has very few restrictions on what characters may be used in branch and tag names. For more information, see "[git-check-ref-format](https://git-scm.com/docs/git-check-ref-format)" in the Git documentation. + +## Why you need to escape special characters + +When using a CLI, you might have situations where a branch or tag name contains special characters that have a special meaning for your shell environment. To use these characters safely in a Git command, they must be quoted or escaped, otherwise the command may have unintended effects. + +For example, the `$` character is used by many shells to refer to a variable. Most shells would interpret a valid branch name like `hello-$USER` as equivalent to the word "hello", followed by a hyphen, followed by the current value of the `USER` variable, rather than the literal string `hello-$USER`. If a branch name includes the `$` character, then the shell must be stopped from expanding it as a variable reference. Similarly, if a branch name contains a semi-colon (`;`), most shells interpret it as a command separator, so it needs to be quoted or escaped. + +## How to escape special characters in branch and tag names + +Most branch and tag names with special characters can be handled by including the name in single quotes, for example `'hello-$USER'`. + +* In the [Bash](https://www.gnu.org/software/bash/) shell, enclosing a string of characters in single quotes preserves the literal value of the characters within the single quotes. +* [Zsh](https://www.zsh.org/) behaves similar to Bash, however this behavior is configurable using the `RC_QUOTES` option. +* [PowerShell](https://microsoft.com/powershell) also treats characters literally when inside single quotes. + +For these shells, the main exception is when the branch or tag name itself contains a single quote. In this case, you should consult the official documentation for your shell: + +* [Bash documentation](https://www.gnu.org/software/bash/manual/) +* [Zsh documentation](https://zsh.sourceforge.io/Doc/) +* [Fish documentation](https://fishshell.com/docs/current/) +* [PowerShell documentation](https://docs.microsoft.com/en-gb/powershell/) + +## Naming branches and tags + +If possible, create branch and tag names that don't contain special characters, as these would need to be escaped. A safe default set of characters to use for branch names and tag names is: + +* The English alphabet (`a` to `z` and `A` to `Z`) +* Numbers (`0` to `9`) +* A limited set of punctuation characters: + * period (`.`) + * hyphen (`-`) + * underscore (`_`) + * forward slash (`/`) + +To avoid confusion, you should start branch names with a letter. diff --git a/translations/de-DE/content/get-started/using-git/index.md b/translations/de-DE/content/get-started/using-git/index.md index 5e8f49d068..448cd038be 100644 --- a/translations/de-DE/content/get-started/using-git/index.md +++ b/translations/de-DE/content/get-started/using-git/index.md @@ -23,5 +23,6 @@ children: - /about-git-rebase - /using-git-rebase-on-the-command-line - /resolving-merge-conflicts-after-a-git-rebase + - /dealing-with-special-characters-in-branch-and-tag-names --- diff --git a/translations/de-DE/content/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md b/translations/de-DE/content/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md index b7ebf9c5c3..75aaf13cad 100644 --- a/translations/de-DE/content/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md +++ b/translations/de-DE/content/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md @@ -41,6 +41,12 @@ Wenn _Prüfungen_ in einem Repository eingerichtet sind, weisen Pull Requests di ![Statuschecks innerhalb eines Pull Requests](/assets/images/help/pull_requests/checks.png) +{% note %} + +**Note:** The **Checks** tab only gets populated for pull requests if you set up _checks_, not _statuses_, for the repository. + +{% endnote %} + Wenn eine Prüfung aufgrund einer bestimmten Zeile in einem Commit nicht bestanden wird, findest Du Einzelheiten über den Fehler, die Warnung oder den Hinweis neben dem entsprechenden Code auf der Registerkarte **Files** (Dateien) des Pull Requests. ![Details eines Statuschecks](/assets/images/help/pull_requests/checks-detailed.png) diff --git a/translations/de-DE/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork.md b/translations/de-DE/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork.md index ff550b6f2c..3ca9537e93 100644 --- a/translations/de-DE/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork.md +++ b/translations/de-DE/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork.md @@ -5,7 +5,7 @@ redirect_from: - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork - /articles/creating-a-pull-request-from-a-fork - /github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork -permissions: Anyone with write access to a repository can create a pull request from a user-owned fork. +permissions: 'Anyone with write access to a repository can create a pull request from a user-owned fork. {% data reusables.enterprise-accounts.emu-permission-propose %}' versions: fpt: '*' ghes: '*' diff --git a/translations/de-DE/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md b/translations/de-DE/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md index 7e00ce3c5c..dbaaec4b6c 100644 --- a/translations/de-DE/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md +++ b/translations/de-DE/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md @@ -1,6 +1,7 @@ --- title: Pull Request erstellen intro: 'Erstelle einen Pull Request, um Änderungen an einem Repository vorzuschlagen und um daran mitzuarbeiten. These changes are proposed in a *branch*, which ensures that the default branch only contains finished and approved work.' +permissions: 'Anyone with read access to a repository can create a pull request. {% data reusables.enterprise-accounts.emu-permission-propose %}' redirect_from: - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request - /articles/creating-a-pull-request @@ -13,7 +14,7 @@ topics: - Pull requests --- -Jeder, der Leseberechtigungen für ein Repository besitzt, kann einen Pull Request erstellen. Du benötigst jedoch Schreibberechtigungen, um einen Branch zu erstellen. Wenn Du einen neuen Branch für Deinen Pull Request erstellen möchtest, aber keine Schreibberechtigung hast, kannst Du das Repository zunächst forken. Weitere Informationen findest Du unter „[Einen Pull Request von einem Fork erstellen](/articles/creating-a-pull-request-from-a-fork)“ und „ +If you want to create a new branch for your pull request and do not have write permissions to the repository, you can fork the repository first. Weitere Informationen findest Du unter „[Einen Pull Request von einem Fork erstellen](/articles/creating-a-pull-request-from-a-fork)“ und „ Informationen zu Forks

Du kannst festlegen, in welchen Branch Du Deine Änderungen zusammenführen möchtest, wenn Du Deinen Pull Request erstellst. Pull Requests können nur zwischen zwei unterschiedlichen Branches geöffnet werden. diff --git a/translations/de-DE/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/translations/de-DE/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md index 2a3b4db14d..f294666a47 100644 --- a/translations/de-DE/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md +++ b/translations/de-DE/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md @@ -1,10 +1,10 @@ --- title: Reviewing dependency changes in a pull request intro: 'If a pull request contains changes to dependencies, you can view a summary of what has changed and whether there are known vulnerabilities in any of the dependencies.' +product: '{% data reusables.gated-features.dependency-review %}' versions: fpt: '*' ghes: '>= 3.2' - product: '{% data reusables.gated-features.dependency-review %}' type: how_to topics: - Pull requests @@ -38,19 +38,19 @@ Dependency review allows you to "shift left". You can use the provided predictiv 1. If the pull request contains many files, use the **File filter** drop-down menu to collapse all files that don't record dependencies. This will make it easier to focus your review on the dependency changes. - ![The file filter menu](/assets/images/help/pull_requests/file-filter-menu-json.png) + ![The file filter menu](/assets/images/help/pull_requests/file-filter-menu-json.png) The dependency review provides a clearer view of what has changed in large lock files, where the source diff is not rendered by default. + + {% note %} + + **Note:** Dependency review rich diffs are not available for committed static JavaScript files like `jquery.js`. + + {% endnote %} 1. On the right of the header for a manifest or lock file, display the dependency review by clicking the **{% octicon "file" aria-label="The rich diff icon" %}** rich diff button. ![The rich diff button](/assets/images/help/pull_requests/dependency-review-rich-diff.png) - {% note %} - - **Note:** The dependency review provides a clearer view of what has changed in large lock files, where the source diff is not rendered by default. - - {% endnote %} - -1. Check the dependencies listed in the dependency review. +2. Check the dependencies listed in the dependency review. ![Vulnerability warnings in a dependency review](/assets/images/help/pull_requests/dependency-review-vulnerability.png) diff --git a/translations/de-DE/content/github/collaborating-with-pull-requests/working-with-forks/about-forks.md b/translations/de-DE/content/github/collaborating-with-pull-requests/working-with-forks/about-forks.md index 4be82fbd81..a6a2a7e848 100644 --- a/translations/de-DE/content/github/collaborating-with-pull-requests/working-with-forks/about-forks.md +++ b/translations/de-DE/content/github/collaborating-with-pull-requests/working-with-forks/about-forks.md @@ -20,6 +20,12 @@ Das Forking eines Repositorys ist ähnlich wie das Kopieren eines Repositorys, m {% data reusables.repositories.you-can-fork %} +{% ifversion fpt %} + +If you're a member of a {% data variables.product.prodname_emu_enterprise %}, there are further restrictions on the repositories you can fork. {% data reusables.enterprise-accounts.emu-forks %} For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." + +{% endif %} + {% data reusables.repositories.desktop-fork %} Das Löschen eines Forks wird das ursprüngliche vorgelagerte Repository nicht löschen. Du kannst beliebige Änderungen an Deiner Fork vornehmen – Mitarbeiter hinzufügen, Dateien umbenennen, {% data variables.product.prodname_pages %} generieren –, ohne Auswirkungen auf das Original.{% ifversion fpt %} Du kannst ein geforktes Repository nach dem Löschen nicht wiederherstellen. Weitere Informationen findest Du unter „[Ein gelöschtes Repository wiederherstellen](/articles/restoring-a-deleted-repository)“.{% endif %} diff --git a/translations/de-DE/content/github/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md b/translations/de-DE/content/github/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md index 3e13822da3..e7bab64e9e 100644 --- a/translations/de-DE/content/github/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md +++ b/translations/de-DE/content/github/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md @@ -52,4 +52,4 @@ Falls in Deinen lokalen Git-Konfiguration eine generische E-Mail-Adresse oder ei ## Weiterführende Informationen -* „[Commits suchen](/articles/searching-commits)“ +* „[Commits suchen](/search-github/searching-on-github/searching-commits)“ diff --git a/translations/de-DE/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views.md b/translations/de-DE/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views.md index a903941a94..50d54e2c00 100644 --- a/translations/de-DE/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views.md +++ b/translations/de-DE/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views.md @@ -29,4 +29,4 @@ Weitere Informationen zum Umgang von Git mit Commit-Verläufen findest Du im Abs ## Weiterführende Informationen - „[Commits signieren](/articles/signing-commits)“ -- „[Commits suchen](/articles/searching-commits)“ +- „[Commits suchen](/search-github/searching-on-github/searching-commits)“ diff --git a/translations/de-DE/content/github/copilot/about-github-copilot-telemetry.md b/translations/de-DE/content/github/copilot/about-github-copilot-telemetry.md index 989263e8e0..7139ed503e 100644 --- a/translations/de-DE/content/github/copilot/about-github-copilot-telemetry.md +++ b/translations/de-DE/content/github/copilot/about-github-copilot-telemetry.md @@ -1,6 +1,6 @@ --- title: About GitHub Copilot telemetry -intro: '{% data variables.product.prodname_dotcom %} Copilot collects and relies on additional telemetry data beyond what other {% data variables.product.prodname_dotcom %} products and services collect.' +intro: '{% data variables.product.prodname_copilot %} collects and relies on additional telemetry data beyond what other {% data variables.product.company_short %} products and services collect.' redirect_from: - /early-access/github/copilot/about-github-copilot-telemetry versions: @@ -8,36 +8,21 @@ versions: --- ## What data is collected -The {% data variables.product.prodname_dotcom %} Copilot collects activity from the user’s Visual Studio Code editor, tied to a timestamp, and metadata. This metadata consists of the extension settings and the standard metadata collected by the [Visual Studio Code extension telemetry package](https://www.npmjs.com/package/vscode-extension-telemetry): -* Visual Studio Code machine ID (pseudonymized identifier) -* Visual Studio Code session ID (pseudonymized identifier) -* Visual Studio Code version -* [Geolocation from IP address](https://docs.microsoft.com/en-us/azure/azure-monitor/app/ip-collection?tabs=net) (country, state/province and city, but not the IP address itself) -* Operating system and version -* Extension version -* The VS Code UI (web or desktop) +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. -The activity collected consists of events that are triggered when: +## How the data is used by {% data variables.product.company_short %} -* An error occurs (it records the error kind and relevant background; e.g. if it’s an authentication error the key expiry date is recorded) -* Our models are accessed to ask for code suggestions (it records editor state like position of cursor and snippets of code)—this includes cases when the user takes an action to request code suggestions -* Code suggestions are received or displayed (it records the suggestions, post-processing, and metadata like model certainty and latency) -* Code suggestions are redacted due to filters that ensure AI safety -* The user acts on code suggestions (e.g. to accept or reject them) -* The user has acted on code suggestions and then it records whether or how they persisted in the code +{% data variables.product.company_short %} will use this data for: -## How the data is used -This data will only be used by {% data variables.product.company_short %} for: - -* Directly improving the product, including assessing different strategies in processing and predicting which suggestions users may find helpful -* Directly evaluating the product, e.g. by measuring the positive impact it has on the user -* Improving the underlying code generation models, e.g. by providing positive and negative examples (but always so that your private code is not used as input to suggest code for other users of {% data variables.product.prodname_dotcom %} Copilot) -* Guiding closely related {% data variables.product.prodname_dotcom %} products -* Investigating and detecting potential abuse of the {% data variables.product.prodname_dotcom %} Copilot service -* Other purposes related to improving the {% data variables.product.prodname_dotcom %} Copilot service +- Directly improving the product, including assessing different strategies in processing and predicting which suggestions users may find helpful +- Evaluating the product, e.g. by measuring the positive impact it has on the user +- Improving the underlying code generation models, e.g. by providing positive and negative examples (but always so that your private code is not used as input to suggest code for other users of {% data variables.product.prodname_copilot %}) +- Guiding closely related {% data variables.product.company_short %} products +- Investigating and detecting potential abuse of the {% data variables.product.prodname_copilot %} service +- Other purposes related to improving the {% data variables.product.prodname_copilot %} service, including sharing as described in the next section ## How the data is shared -The telemetry data is stored securely on {% data variables.product.prodname_dotcom %} systems, with appropriate encryption in place. -We know user edit actions and source code snippets are very sensitive data, and access is strictly controlled. The data can only be accessed by (1) named {% data variables.product.company_short %} personnel (employees and contractors) working on the {% data variables.product.company_short %} Copilot team or on the {% data variables.product.company_short %} platform health team, (2) select Microsoft personnel (employees and contractors) working on or with the {% data variables.product.company_short %} Copilot team, and (3) select employees of OpenAI who work on {% data variables.product.company_short %} Copilot. +The telemetry data is stored securely on {% data variables.product.company_short %} systems, with appropriate encryption in place. We know user edit actions, source code snippets, and URLs of repositories and file paths are sensitive data. Consequently, access is strictly controlled. The data can only be accessed by (1) named {% data variables.product.company_short %} personnel (employees and contractors) working on the {% data variables.product.prodname_copilot %} team or on the {% data variables.product.company_short %} platform health team, (2) Microsoft personnel (employees and contractors) working on or with the Azure and/or {% data variables.product.prodname_copilot %} teams, and (3) employees of OpenAI who work on {% data variables.product.prodname_copilot %}. + diff --git a/translations/de-DE/content/github/copilot/github-copilot-telemetry-terms.md b/translations/de-DE/content/github/copilot/github-copilot-telemetry-terms.md new file mode 100644 index 0000000000..6e178850e6 --- /dev/null +++ b/translations/de-DE/content/github/copilot/github-copilot-telemetry-terms.md @@ -0,0 +1,16 @@ +--- +title: GitHub Copilot Telemetry Terms +intro: 'Acceptance of the additional telemetry described below is a condition to joining the wait list for the technical preview of {% data variables.product.prodname_copilot %} and using {% data variables.product.prodname_copilot %} during the technical preview.' +redirect_from: + - /early-access/github/copilot/telemetry-terms + - /github/copilot/telemetry-terms +versions: + fpt: '*' +--- + +## Additional telemetry + +If you use {% data variables.product.prodname_copilot %}, the {% data variables.product.prodname_copilot %} extension/plugin will collect usage information about events generated by interacting with the integrated development environment (IDE). These events include {% data variables.product.prodname_copilot %} performance, features used, and suggestions accepted, modified and accepted, or dismissed. This information may include personal data, including your User Personal Information, as defined in the [GitHub Privacy Statement](/github/site-policy/github-privacy-statement). + +This usage information is used by {% data variables.product.company_short %}, and shared with Microsoft and OpenAI, to develop and improve the extension/plugin and related products. OpenAI also uses this usage information to perform other services related to {% data variables.product.prodname_copilot %}. For example, when you edit files with the {% data variables.product.prodname_copilot %} extension/plugin enabled, file content snippets, suggestions, and any modifications to suggestions will be shared with {% data variables.product.company_short %}, Microsoft, and OpenAI, and used for diagnostic purposes to improve suggestions and related products. {% data variables.product.prodname_copilot %} relies on file content for context, both in the file you are editing and potentially other files open in the same IDE instance. When you are using {% data variables.product.prodname_copilot %}, it may also collect the URLs of repositories or file paths for relevant files. {% data variables.product.prodname_copilot %} does not use these URLs, file paths, or snippets collected in your telemetry as input to suggest code for other users of {% data variables.product.prodname_copilot %}. This information is treated as confidential information and accessed on a need-to-know basis. You are prohibited from collecting telemetry data about other users of {% data variables.product.prodname_copilot %} from the {% data variables.product.prodname_copilot %} extension/plugin. For more details about {% data variables.product.prodname_copilot %} telemetry, please see "[About {% data variables.product.prodname_copilot %} telemetry](/github/copilot/about-github-copilot-telemetry)." You may revoke your consent to the telemetry and personal data processing operations described in this paragraph by contacting GitHub and requesting removal from the technical preview. + diff --git a/translations/de-DE/content/github/copilot/index.md b/translations/de-DE/content/github/copilot/index.md index ef5fc94524..bc5bc35075 100644 --- a/translations/de-DE/content/github/copilot/index.md +++ b/translations/de-DE/content/github/copilot/index.md @@ -5,7 +5,7 @@ versions: fpt: '*' children: - /about-github-copilot-telemetry - - /telemetry-terms + - /github-copilot-telemetry-terms - /research-recitation --- diff --git a/translations/de-DE/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md b/translations/de-DE/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md index 32eb27f458..7ce14861ae 100644 --- a/translations/de-DE/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md +++ b/translations/de-DE/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md @@ -16,7 +16,7 @@ You may also have the option to select a free 14-day trial on some tools. Du kan ## Finding tools on {% data variables.product.prodname_marketplace %} -You can discover, browse, and install apps and actions created by others on {% data variables.product.prodname_marketplace %}, see "[Searching {% data variables.product.prodname_marketplace %}](/github/searching-for-information-on-github/searching-github-marketplace)." +You can discover, browse, and install apps and actions created by others on {% data variables.product.prodname_marketplace %}, see "[Searching {% data variables.product.prodname_marketplace %}](/search-github/searching-on-github/searching-github-marketplace)." {% data reusables.actions.actions-not-verified %} diff --git a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning/sarif-support-for-code-scanning.md b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning/sarif-support-for-code-scanning.md index 150ff6234f..a4051d76e7 100644 --- a/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning/sarif-support-for-code-scanning.md +++ b/translations/de-DE/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning/sarif-support-for-code-scanning.md @@ -31,7 +31,7 @@ If you're new to SARIF and want to learn more, see Microsoft's [`SARIF tutorials Each time a {% data variables.product.prodname_actions %} workflow runs a new code scan, the results for each run are processed and alerts are added to the repository. To prevent duplicate alerts for the same problem, {% data variables.product.prodname_code_scanning %} uses fingerprints to match results across various runs so they only appear once in the latest run for the selected branch. This makes it possible to match alerts to the right line of code when files are edited. -{% data variables.product.prodname_dotcom %} uses the `partialFingerprints` property in the OASIS standard to detect when two results are logically identical. For more information, see the "[partialFingerprints property](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012611)" entry in the OASIS documentation. +{% data variables.product.prodname_dotcom %} uses the `partialFingerprints` property in the OASIS standard as an input in the computation of whether two results are logically identical. Specifically, the `primaryLocationLineHash` is used as a stable intra-file location, which is combined with the repository, file path, and rule data to form the full identity. For more information, see the "[partialFingerprints property](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012611)" entry in the OASIS documentation. SARIF files created by the {% data variables.product.prodname_codeql_workflow %} or using the {% data variables.product.prodname_codeql_runner %} include fingerprint data. If you upload a SARIF file using the `upload-sarif` action and this data is missing, {% data variables.product.prodname_dotcom %} attempts to populate the `partialFingerprints` field from the source files. For more information about uploading results, see "[Uploading a SARIF file to {% data variables.product.prodname_dotcom %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github#uploading-a-code-scanning-analysis-with-github-actions)." @@ -89,17 +89,17 @@ Any valid SARIF 2.1.0 output file can be uploaded, however, {% data variables.pr {% data reusables.code-scanning.upload-sarif-alert-limit %} -| Name | Beschreibung | -| --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `ruleId` | **Optional.** The unique identifier of the rule (`reportingDescriptor.id`). For more information, see the [`reportingDescriptor` object](#reportingdescriptor-object). {% data variables.product.prodname_code_scanning_capc %} uses the rule identifier to filter results by rule on {% data variables.product.prodname_dotcom %}. | -| `ruleIndex` | **Optional.** The index of the associated rule (`reportingDescriptor` object) in the tool component `rules` array. For more information, see the [`run` object](#run-object). | -| `rule` | **Optional.** A reference used to locate the rule (reporting descriptor) for this result. For more information, see the [`reportingDescriptor` object](#reportingdescriptor-object). | -| `level` | **Optional.** The severity of the result. This level overrides the default severity defined by the rule. {% data variables.product.prodname_code_scanning_capc %} uses the level to filter results by severity on {% data variables.product.prodname_dotcom %}. | -| `message.text` | **Required.** A message that describes the result. {% data variables.product.prodname_code_scanning_capc %} displays the message text as the title of the result. Only the first sentence of the message will be displayed when visible space is limited. | -| `locations[]` | **Required.** The set of locations where the result was detected up to a maximum of 10. Only one location should be included unless the problem can only be corrected by making a change at every specified location. **Note:** At least one location is required for {% data variables.product.prodname_code_scanning %} to display a result. {% data variables.product.prodname_code_scanning_capc %} will use this property to decide which file to annotate with the result. Only the first value of this array is used. All other values are ignored. | -| `partialFingerprints` | **Required.** A set of strings used to track the unique identity of the result. {% data variables.product.prodname_code_scanning_capc %} uses `partialFingerprints` to accurately identify which results are the same across commits and branches. {% data variables.product.prodname_code_scanning_capc %} will attempt to use `partialFingerprints` if they exist. If you are uploading third-party SARIF files with the `upload-action`, the action will create `partialFingerprints` for you when they are not included in the SARIF file. For more information, see "[Preventing duplicate alerts using fingerprints](#preventing-duplicate-alerts-using-fingerprints)." **Note:** {% data variables.product.prodname_code_scanning_capc %} only uses the `primaryLocationLineHash`. | -| `codeFlows[].threadFlows[].locations[]` | **Optional.** An array of `location` objects for a `threadFlow` object, which describes the progress of a program through a thread of execution. A `codeFlow` object describes a pattern of code execution used to detect a result. If code flows are provided, {% data variables.product.prodname_code_scanning %} will expand code flows on {% data variables.product.prodname_dotcom %} for the relevant result. For more information, see the [`location` object](#location-object). | -| `relatedLocations[]` | A set of locations relevant to this result. {% data variables.product.prodname_code_scanning_capc %} will link to related locations when they are embedded in the result message. For more information, see the [`location` object](#location-object). | +| Name | Beschreibung | +| --------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `ruleId` | **Optional.** The unique identifier of the rule (`reportingDescriptor.id`). For more information, see the [`reportingDescriptor` object](#reportingdescriptor-object). {% data variables.product.prodname_code_scanning_capc %} uses the rule identifier to filter results by rule on {% data variables.product.prodname_dotcom %}. | +| `ruleIndex` | **Optional.** The index of the associated rule (`reportingDescriptor` object) in the tool component `rules` array. For more information, see the [`run` object](#run-object). | +| `rule` | **Optional.** A reference used to locate the rule (reporting descriptor) for this result. For more information, see the [`reportingDescriptor` object](#reportingdescriptor-object). | +| `level` | **Optional.** The severity of the result. This level overrides the default severity defined by the rule. {% data variables.product.prodname_code_scanning_capc %} uses the level to filter results by severity on {% data variables.product.prodname_dotcom %}. | +| `message.text` | **Required.** A message that describes the result. {% data variables.product.prodname_code_scanning_capc %} displays the message text as the title of the result. Only the first sentence of the message will be displayed when visible space is limited. | +| `locations[]` | **Required.** The set of locations where the result was detected up to a maximum of 10. Only one location should be included unless the problem can only be corrected by making a change at every specified location. **Note:** At least one location is required for {% data variables.product.prodname_code_scanning %} to display a result. {% data variables.product.prodname_code_scanning_capc %} will use this property to decide which file to annotate with the result. Only the first value of this array is used. All other values are ignored. | +| `partialFingerprints` | **Required.** A set of strings used to track the unique identity of the result. {% data variables.product.prodname_code_scanning_capc %} uses `partialFingerprints` as part of the computation to accurately identify which results are the same across commits and branches. {% data variables.product.prodname_code_scanning_capc %} will attempt to use `partialFingerprints` if they exist. If you are uploading third-party SARIF files with the `upload-action`, the action will create `partialFingerprints` for you when they are not included in the SARIF file. For more information, see "[Preventing duplicate alerts using fingerprints](#preventing-duplicate-alerts-using-fingerprints)." **Note:** {% data variables.product.prodname_code_scanning_capc %} only uses the `primaryLocationLineHash`. | +| `codeFlows[].threadFlows[].locations[]` | **Optional.** An array of `location` objects for a `threadFlow` object, which describes the progress of a program through a thread of execution. A `codeFlow` object describes a pattern of code execution used to detect a result. If code flows are provided, {% data variables.product.prodname_code_scanning %} will expand code flows on {% data variables.product.prodname_dotcom %} for the relevant result. For more information, see the [`location` object](#location-object). | +| `relatedLocations[]` | A set of locations relevant to this result. {% data variables.product.prodname_code_scanning_capc %} will link to related locations when they are embedded in the result message. For more information, see the [`location` object](#location-object). | ### `location` object diff --git a/translations/de-DE/content/github/index.md b/translations/de-DE/content/github/index.md index 80b6aa982d..97309d23a8 100644 --- a/translations/de-DE/content/github/index.md +++ b/translations/de-DE/content/github/index.md @@ -15,7 +15,6 @@ children: - /writing-on-github - /committing-changes-to-your-project - /collaborating-with-pull-requests - - /searching-for-information-on-github - /importing-your-projects-to-github - /managing-security-vulnerabilities - /finding-security-vulnerabilities-and-errors-in-your-code diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/about-identity-and-access-management-for-your-enterprise-account.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/about-identity-and-access-management-for-your-enterprise-account.md index 3dfe3805c2..8b7498e5f0 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/about-identity-and-access-management-for-your-enterprise-account.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/about-identity-and-access-management-for-your-enterprise-account.md @@ -21,6 +21,12 @@ If you use Azure AD as your IDP, you can use team synchronization to manage team {% data reusables.saml.switching-from-org-to-enterprise %} For more information, see "[Switching your SAML configuration from an organization to an enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)." +## Informationen zu {% data variables.product.prodname_emus %} + +{% data reusables.enterprise-accounts.emu-short-summary %} + +Configuring {% data variables.product.prodname_emus %} for SAML single-sign on and user provisioning involves following a different process than you would for an enterprise that isn't using {% data variables.product.prodname_managed_users %}. If your enterprise uses {% data variables.product.prodname_emus %}, see "[Configuring SAML single sign-on for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." + ## Supported IdPs We test and officially support the following IdPs. For SAML SSO, we offer limited support for all identity providers that implement the SAML 2.0 standard. For more information, see the [SAML Wiki](https://wiki.oasis-open.org/security) on the OASIS website. @@ -32,4 +38,3 @@ We test and officially support the following IdPs. For SAML SSO, we offer limite | OneLogin | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | PingOne | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | Shibboleth | {% octicon "check-circle-fill" aria-label="The check icon" %} | | - diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/configuring-saml-single-sign-on-for-your-enterprise-account-using-okta.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/configuring-saml-single-sign-on-for-your-enterprise-account-using-okta.md index 8122d4a1b3..91de2150bf 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/configuring-saml-single-sign-on-for-your-enterprise-account-using-okta.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/configuring-saml-single-sign-on-for-your-enterprise-account-using-okta.md @@ -16,6 +16,8 @@ shortTitle: Configure SAML with Okta {% data reusables.enterprise-accounts.user-provisioning-release-stage %} +{% data reusables.enterprise-accounts.emu-saml-note %} + ## About SAML with Okta You can control access to your enterprise account in {% data variables.product.product_name %} and other web applications from one central interface by configuring the enterprise account to use SAML SSO with Okta, an Identity Provider (IdP). diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account.md index 0be35a2dd7..5a1c9f3b0f 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account.md @@ -13,6 +13,8 @@ redirect_from: shortTitle: Enforce SAML --- +{% data reusables.enterprise-accounts.emu-saml-note %} + ## About SAML single sign-on for enterprise accounts {% data reusables.saml.dotcom-saml-explanation %} Weitere Informationen findest Du unter „[Informationen über Identitäts- und Zugriffsmanagement mit SAML Single Sign-On](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)." diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/managing-team-synchronization-for-organizations-in-your-enterprise-account.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/managing-team-synchronization-for-organizations-in-your-enterprise-account.md index dd4c24b8ac..ca7047bc9a 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/managing-team-synchronization-for-organizations-in-your-enterprise-account.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/managing-team-synchronization-for-organizations-in-your-enterprise-account.md @@ -12,6 +12,8 @@ redirect_from: shortTitle: Manage team synchronization --- +{% data reusables.enterprise-accounts.emu-scim-note %} + ## About team synchronization for enterprise accounts If you use Azure AD as your IdP, you can enable team synchronization for your enterprise account to allow organization owners and team maintainers to synchronize teams in the organizations owned by your enterprise accounts with IdP groups. diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md index dc0ea3c5a4..1e02948fe3 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md @@ -10,6 +10,8 @@ topics: shortTitle: Switching from organization --- +{% data reusables.enterprise-accounts.emu-saml-note %} + ## About SAML single sign-on for enterprise accounts {% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %} diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/index.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/index.md index 12012356e5..8d939d4737 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/index.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/index.md @@ -14,6 +14,7 @@ topics: children: - /managing-your-enterprise-account - /managing-users-in-your-enterprise + - /managing-your-enterprise-users-with-your-identity-provider - /managing-organizations-in-your-enterprise-account - /configuring-identity-and-access-management-for-your-enterprise-account - /setting-policies-for-organizations-in-your-enterprise-account diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account.md index 350b10fef7..70b31e4183 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account.md @@ -1,6 +1,6 @@ --- title: Organisationen zu Deinem Enterprise-Konto hinzufügen -intro: 'Du kannst neue Organisationen erstellen, um sie in Deinem Enterprise-Konto zu verwalten.' +intro: You can create new organizations or invite existing organizations to manage within your enterprise account. product: '{% data reusables.gated-features.enterprise-accounts %}' redirect_from: - /articles/adding-organizations-to-your-enterprise-account @@ -13,9 +13,9 @@ topics: shortTitle: Add organizations --- -Enterprise-Inhaber können in den Einstellungen eines Enterprise-Kontos neue Organisationen erstellen. +Enterprise owners can create new organizations within an enterprise account's settings or invite existing organizations to join an enterprise account. -Um Deinem Enterprise-Konto eine Organisation hinzuzufügen, musst Du die Organisation in den Einstellungen des Enterprise-Kontos erstellen. If you want to transfer an existing organization to your enterprise account, contact your {% data variables.product.prodname_dotcom %} sales account representative. +Um Deinem Enterprise-Konto eine Organisation hinzuzufügen, musst Du die Organisation in den Einstellungen des Enterprise-Kontos erstellen. ## Eine Organisation in Deinem Enterprise-Konto erstellen @@ -29,3 +29,15 @@ Enterprise-Inhaber, die eine dem Enterprise-Konto gehörende Organisation erstel 4. Klicke auf **Create organization** (Organisation erstellen). 5. Gib unter „Invite owners“ (Inhaber einladen) den Benutzernamen einer Person ein, die Du dazu einladen möchtest, Organisationsinhaber zu werden. Klicke anschließend auf **Invite** (Einladen). ![Organisationsinhaber-Suchfeld und Schaltfläche „Invite“ (Einladen)](/assets/images/help/business-accounts/invite-org-owner.png) 6. Klicke auf **Finish** (Fertigstellen). + +## Inviting an organization to join your enterprise account + +Enterprise owners can invite existing organizations to join their enterprise account. If the organization you want to invite is already owned by another enterprise, you will not be able to issue an invitation until the previous enterprise gives up ownership of the organization. + +{% data reusables.enterprise-accounts.access-enterprise %} +2. On the **Organizations** tab, above the list of organizations, click **Invite organization**. ![Invite organization](/assets/images/help/business-accounts/enterprise-account-invite-organization.png) +3. Under "Organization name", start typing the name of the organization you want to invite and select it when it appears in the drop-down list. ![Search for organization](/assets/images/help/business-accounts/enterprise-account-search-for-organization.png) +4. Click **Invite organization**. +5. The organization owners will receive an email inviting them to join the organization. At least one owner needs to accept the invitation before the process can continue. You can cancel or resend the invitation at any time before an owner approves it. ![Cancel or resend](/assets/images/help/business-accounts/enterprise-account-invitation-sent.png) +6. Once an organization owner has approved the invitation, you can view its status in the list of pending invitations. ![Pending invitation](/assets/images/help/business-accounts/enterprise-account-pending.png) +7. Click **Approve** to complete the transfer, or **Cancel** to cancel it. ![Approve invitation](/assets/images/help/business-accounts/enterprise-account-transfer-approve.png) diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md index a9288487f7..10f7b62dbd 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md @@ -28,6 +28,12 @@ If you want to manage owners and billing managers for an enterprise account on { {% endif %} +{% ifversion fpt %} + +If your enterprise uses {% data variables.product.prodname_emus %}, enterprise owners can only be added or removed through your identity provider. For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." + +{% endif %} + {% tip %} **Tipp:** Weitere Informationen zum Verwalten von Benutzern in einer Organisation Deines Enterprise-Kontos findest Du unter „[Mitgliedschaft in Deiner Organisation verwalten](/articles/managing-membership-in-your-organization)“ und „[Rollenbasierte Zugriffe von Personen auf Deine Organisation verwalten](/articles/managing-peoples-access-to-your-organization-with-roles).“ diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise.md index ce773debe6..3e9e7a7c7d 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise.md @@ -21,7 +21,14 @@ Everyone in an enterprise is a member of the enterprise. You can also assign adm {% data reusables.enterprise-accounts.enterprise-administrators %} -For more information about adding people to your enterprise, see "{% ifversion fpt %}[Inviting people to manage your enterprise](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise){% else %}[Authentication](/admin/authentication){% endif %}". +{% ifversion fpt %} +If your enterprise does not use {% data variables.product.prodname_emus %}, you can invite someone to an administrative role using a user account on {% data variables.product.product_name %} that they control. For more information, see "[Inviting people to manage your enterprise](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)". + +In an enterprise using {% data variables.product.prodname_emus %}, new owners and members must be provisioned through your identity provider. Enterprise owners and organization owners cannot add new members or owners to the enterprise using {% data variables.product.prodname_dotcom %}. You can select a member's enterprise role using your IdP and it cannot be changed on {% data variables.product.prodname_dotcom %}. You can select a member's role in an organization on {% data variables.product.prodname_dotcom %}. For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." +{% else %} +For more information about adding people to your enterprise, see "[Authentication](/admin/authentication)". + +{% endif %} ## Enterprise-Inhaber diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md index 3de32bf5d7..91c2a51e87 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md @@ -18,18 +18,13 @@ shortTitle: View & manage SAML access Wenn Du SAML Single Sign-On für Dein Enterprise-Konto aktivierst, kann jedes Enterprise-Mitglied seine externe Identität auf Deinem Identitätsanbieter (IdP) mit seinem bestehenden {% data variables.product.product_name %}-Konto verknüpfen. {% data reusables.saml.about-saml-access-enterprise-account %} +If your enterprise is uses {% data variables.product.prodname_emus %}, your members will use accounts provisioned through your IdP. {% data variables.product.prodname_managed_users_caps %} will not use their existing user account on {% data variables.product.product_name %}. For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." + ## Eine verknüpfte Identität anschauen und widerrufen {% data reusables.saml.about-linked-identities %} -{% warning %} - -**Warning:** For organizations using SCIM: -- Revoking a linked user identity on {% data variables.product.product_name %} will also remove the SAML and SCIM metadata. As a result, the identity provider will not be able to synchronize or deprovision the linked user identity. -- An admin must revoke a linked identity through the identity provider. -- To revoke a linked identity and link a different account through the identity provider, an admin can remove and re-assign the user to the {% data variables.product.product_name %} application. For more information, see your identity provider's docs. - -{% endwarning %} +If your enterprise uses {% data variables.product.prodname_emus %}, you will not be able to deprovision or remove user accounts from the enterprise on {% data variables.product.product_name %}. Any changes you need to make to your enterprise's {% data variables.product.prodname_managed_users %} should be made through your IdP. {% data reusables.identity-and-permissions.revoking-identity-team-sync %} diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md new file mode 100644 index 0000000000..5141d36fbd --- /dev/null +++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md @@ -0,0 +1,84 @@ +--- +title: About Enterprise Managed Users +shortTitle: About managed users +intro: 'You can centrally manage identity and access for your enterprise members on {% data variables.product.prodname_dotcom %} from your identity provider.' +product: '{% data reusables.gated-features.emus %}' +redirect_from: + - /early-access/github/articles/get-started-with-managed-users-for-your-enterprise +versions: + fpt: '*' +topics: + - Accounts + - Enterprise +--- + +## Informationen zu {% data variables.product.prodname_emus %} + +With {% data variables.product.prodname_emus %}, you can control the user accounts of your enterprise members through your identity provider (IdP). You can simplify authentication with SAML single sign-on (SSO) and provision, update, and deprovision user accounts for your enterprise members. Users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your IdP are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and added to your enterprise. You control usernames, profile data, team membership, and repository access from your IdP. + +In your IdP, you can give each {% data variables.product.prodname_managed_user %} the role of user, enterprise owner, or billing manager. {% data variables.product.prodname_managed_users_caps %} can own organizations within your enterprise and can add other {% data variables.product.prodname_managed_users %} to the organizations and teams within. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" and "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)." + +You can also manage team membership within an organization in your enterprise directly through your IdP, allowing you to manage repository access using groups in your IdP. Organization membership can be managed manually or updated automatically as {% data variables.product.prodname_managed_users %} are added to teams within the organization. For more information, see "[Managing team memberships with identity provider groups](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)." + +You can grant {% data variables.product.prodname_managed_users %} access and the ability to contribute to repositories within your enterprise, but {% data variables.product.prodname_managed_users %} cannot create public content or collaborate with other users, organizations, and enterprises on the rest of {% data variables.product.prodname_dotcom %}. The {% data variables.product.prodname_managed_users %} provisioned for your enterprise cannot be invited to organizations or repositories outside of the enterprise, nor can the {% data variables.product.prodname_managed_users %} be invited to other enterprises. Outside collaborators are not supported by {% data variables.product.prodname_emus %}. + +The usernames of your enterprise's {% data variables.product.prodname_managed_users %} and their profile information, such as display names and email addresses, are set by through your IdP and cannot be changed by the users themselves. For more information, see "[Usernames and profile information](#usernames-and-profile-information)." + +{% data reusables.enterprise-accounts.emu-forks %} + +Enterprise owners can audit all of the {% data variables.product.prodname_managed_users %}' actions on {% data variables.product.prodname_dotcom %}. + +To use {% data variables.product.prodname_emus %}, you need a separate type of enterprise account with {% data variables.product.prodname_emus %} enabled. For more information about creating this account, see "[About enterprises with managed users](#about-enterprises-with-managed-users)." + + +## Identity provider support + +{% data variables.product.prodname_emus %} supports the following IdPs: + +{% data reusables.enterprise-accounts.emu-supported-idps %} + +## Abilities and restrictions of {% data variables.product.prodname_managed_users %} + +{% data variables.product.prodname_managed_users_caps %} can only contribute to private and internal repositories within their enterprise and private repositories owned by their user account. {% data variables.product.prodname_managed_users_caps %} have read-only access to the wider {% data variables.product.prodname_dotcom %} community. + +* {% data variables.product.prodname_managed_users_caps %} cannot create issues or pull requests in, comment or add reactions to, nor star, watch, or fork repositories outside of the enterprise. +* {% data variables.product.prodname_managed_users_caps %} cannot push code to repositories outside of the enterprise. +* {% data variables.product.prodname_managed_users_caps %} and the content they create is only visible to other members of the enterprise. +* {% data variables.product.prodname_managed_users_caps %} cannot follow users outside of the enterprise. +* {% data variables.product.prodname_managed_users_caps %} cannot create gists or comment on gists. +* {% data variables.product.prodname_managed_users_caps %} cannot install {% data variables.product.prodname_github_apps %} on their user accounts. +* Other {% data variables.product.prodname_dotcom %} users cannot see, mention, or invite a {% data variables.product.prodname_managed_user %} to collaborate. +* {% data variables.product.prodname_managed_users_caps %} can only own private repositories and {% data variables.product.prodname_managed_users %} can only invite other enterprise members to collaborate on their owned repositories. +* Only private and internal repositories can be created in organizations owned by an {% data variables.product.prodname_emu_enterprise %}, depending on organization and enterprise repository visibility settings. + +## About enterprises with managed users + +To use {% data variables.product.prodname_emus %}, you need a separate type of enterprise account with {% data variables.product.prodname_emus %} enabled. To try out {% data variables.product.prodname_emus %} or to discuss options for migrating from your existing enterprise, please contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact). + +Your contact on the GitHub Sales team will work with you to create your new {% data variables.product.prodname_emu_enterprise %}. You'll need to provide the email address for the user who will set up your enterprise and a short code that will be used as the suffix for your enterprise members' usernames. {% data reusables.enterprise-accounts.emu-shortcode %} For more information, see "[Usernames and profile information](#usernames-and-profile-information)." + +After we create your enterprise, you will receive an email from {% data variables.product.prodname_dotcom %} inviting you to choose a password for your enterprise's setup user, which will be the first owner in the enterprise. The setup user is only used to configure SAML single sign-on and SCIM provisioning integration for the enterprise. It will no longer have access to administer the enterprise account once SAML is successfully enabled. + +The setup user's username is your enterprise's shortcode suffixed with `_admin`. After you log in to your setup user, you can get started by configuring SAML SSO for your enterprise. For more information, see "[Configuring SAML single sign-on for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." + +{% note %} + +{% data reusables.enterprise-accounts.emu-password-reset-session %} + +{% endnote %} + +## Authenticating as a {% data variables.product.prodname_managed_user %} + +{% data variables.product.prodname_managed_users_caps %} must authenticate through their identity provider. + +To authenticate, {% data variables.product.prodname_managed_users %} must visit their IdP application portal or **https://github.com/enterprises/ENTERPRISE_NAME**, replacing **ENTERPRISE_NAME** with your enterprise's name. + +## Usernames and profile information + +When your {% data variables.product.prodname_emu_enterprise %} is created, you will choose a short code that will be used as the suffix for your enterprise member's usernames. {% data reusables.enterprise-accounts.emu-shortcode %} The setup user who configures SAML SSO has a username in the format of **@SHORT-CODE_admin**. + +When you provision a new user from your identity provider, the new {% data variables.product.prodname_managed_user %} will have a {% data variables.product.product_name %} username in the format of **@IDP-USERNAME_SHORT-CODE**. When using Azure Active Directory (Azure AD), _IDP-USERNAME_ is formed by normalizing the characters preceding the `@` character in the UPN (User Principal Name) provided by Azure AD. When using Okta, _IDP-USERNAME_ is the normalized username attribute provided by Okta. + +The username of the new account provisioned on {% data variables.product.product_name %}, including underscore and short code, must not exceed 39 characters. + +The profile name and email address of a {% data variables.product.prodname_managed_user %} is also provided by the IdP. {% data variables.product.prodname_managed_users_caps %} cannot change their profile name or email address on {% data variables.product.prodname_dotcom %}. diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/auditing-activity-in-your-enterprise.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/auditing-activity-in-your-enterprise.md new file mode 100644 index 0000000000..55f9102a8f --- /dev/null +++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/auditing-activity-in-your-enterprise.md @@ -0,0 +1,32 @@ +--- +title: Auditing activity in your enterprise +shortTitle: Auditing activity +intro: 'You can audit the activity of the {% data variables.product.prodname_managed_users %} in your enterprise, viewing information about what actions were performed, by which user, and when they took place.' +permissions: Enterprise owners can access the audit log. +product: '{% data reusables.gated-features.emus %}' +versions: + fpt: '*' +topics: + - Accounts + - Enterprise +--- + +## About the audit log + +The audit log allows enterprise owners to quickly review or export the actions performed by both owners and members of your enterprise. Each audit log entry shows information about the event. + +- die Organisation, in der eine Aktion ausgeführt wurde, +- der Benutzer, der die Aktion durchgeführt hat, +- an welchem Repository eine Aktion durchgeführt wurde, +- die Aktion, die durchgeführt wurde, +- in welchem Land die Aktion durchgeführt wurde, +- Datum und Uhrzeit der Aktion. + +## Zugriff auf das Auditprotokoll + +You can also access the audit log for your enterprise from the REST API. For more information, see "[GitHub Enterprise administration](/rest/reference/enterprise-admin#get-the-audit-log-for-an-enterprise)" in the API documentation. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.audit-log-tab %} +1. Optionally, above the list of events, select the **Export Git Events** or **Export** drop-down menu and choose options for exporting events from the audit log. !["Export Git Events" and "Export" drop-down menus for the enterprise audit log](/assets/images/help/enterprises/audit-log-export-drop-down-menus.png) diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users.md new file mode 100644 index 0000000000..0ac32e75d8 --- /dev/null +++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users.md @@ -0,0 +1,109 @@ +--- +title: Configuring SAML single sign-on for Enterprise Managed Users +shortTitle: SAML for managed users +intro: 'You can automatically manage access to your enterprise account on {% data variables.product.prodname_dotcom %} by configuring Security Assertion Markup Language (SAML) single sign-on (SSO).' +product: '{% data reusables.gated-features.emus %}' +versions: + fpt: '*' +topics: + - Accounts + - Enterprise +--- + +## About SAML single sign-on for {% data variables.product.prodname_emus %} + +With {% data variables.product.prodname_emus %}, your enterprise uses SAML SSO to authenticate all members. Instead of signing in to {% data variables.product.prodname_dotcom %} with a {% data variables.product.prodname_dotcom %} username and password, members of your enterprise will sign in through your IdP. + +{% data variables.product.prodname_emus %} supports the following IdPs: + +{% data reusables.enterprise-accounts.emu-supported-idps %} + +After you configure SAML SSO, we recommend storing your recovery codes so you can recover access to your enterprise in the event that your identity provider is unavailable. For more information, see "[Saving your recovery codes](#saving-your-recovery-codes)." + +## Configuring SAML single sign-on for {% data variables.product.prodname_emus %} + +To configure SAML SSO for your {% data variables.product.prodname_emu_enterprise %}, you must configure an application on your IdP and then configure your enterprise on GitHub.com. After you configure SAML SSO, you can configure user provisioning. + +To install and configure the {% data variables.product.prodname_emu_idp_application %} application on your IdP, you must have a tenant and administrative access on a supported IdP. + +{% note %} + +{% data reusables.enterprise-accounts.emu-password-reset-session %} + +{% endnote %} + +1. [Configuring your identity provider](#configuring-your-identity-provider) +2. [Configuring your enterprise](#configuring-your-enterprise) +3. [Enabling provisioning](#enabling-provisioning) + +### Configuring your identity provider + +To configure your IdP, follow the instructions they provide for configuring the {% data variables.product.prodname_emu_idp_application %} application on your IdP. + +1. To install the {% data variables.product.prodname_emu_idp_application %} application, click the link for your IdP below: + + - [{% data variables.product.prodname_emu_idp_application %} application on Azure Active Directory](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/aad.githubenterprisemanageduser?tab=Overview) + - [{% data variables.product.prodname_emu_idp_application %} application on Okta](https://www.okta.com/integrations/github-enterprise-managed-user) + +1. To configure the {% data variables.product.prodname_emu_idp_application %} application and your IdP, click the link below and follow the instructions provided by your IdP: + + - [Azure Active Directory tutorial for {% data variables.product.prodname_emus %}](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-enterprise-managed-user-tutorial) + - [Okta documentation for {% data variables.product.prodname_emus %}](https://saml-doc.okta.com/SAML_Docs/How-to-Configure-SAML-2.0-for-GitHub-Enterprise-Managed-User.html) + +1. So you can test and configure your enterprise, assign yourself or the user that will be configuring SAML SSO on {% data variables.product.prodname_dotcom %} to the {% data variables.product.prodname_emu_idp_application %} application on your IdP. + +1. To enable you to continue configuring your enterprise on {% data variables.product.prodname_dotcom %}, locate and note the following information from the application you installed on your IdP: + + | Wert | Other names | Beschreibung | + |:----------------------------------- |:------------------ |:---------------------------------------------------------------- | + | IdP Sign-On URL | Login URL, IdP URL | Application's URL on your IdP | + | IdP Identifier URL | Issuer | IdP's identifier to service providers for SAML authentication | + | Signing certificate, Base64-encoded | Public certificate | Public certificate that IdP uses to sign authentication requests | + +### Configuring your enterprise + +After you install and configure the {% data variables.product.prodname_emu_idp_application %} application on your identity provider, you can configure your enterprise. + +1. Sign into {% data variables.product.prodname_dotcom_the_website %} as the setup user for your new enterprise with the username **@SHORT-CODE_admin**. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} + +1. Under "SAML single sign-on", select **Require SAML authentication**. ![Kontrollkästchen zum Aktivieren von SAML SSO](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) + +1. Under **Sign on URL**, type the HTTPS endpoint of your IdP for single sign-on requests that you noted while configuring your IdP. ![Feld für die URL, auf die Mitglieder bei der Anmeldung weitergeleitet werden](/assets/images/help/saml/saml_sign_on_url_business.png) + +1. Under **Issuer**, type your SAML issuer URL that you noted while configuring your IdP, to verify the authenticity of sent messages. ![Feld für den Namen des SAML-Ausstellers](/assets/images/help/saml/saml_issuer.png) + +1. Under **Public Certificate**, paste the certificate that you noted while configuring your IdP, to verify SAML responses. ![Feld für das öffentliche Zertifikat des Identity Providers](/assets/images/help/saml/saml_public_certificate.png) + +1. Um die Integrität der Anforderungen von Ihrem SAML-Aussteller zu überprüfen, klicken Sie auf {% octicon "pencil" aria-label="The edit icon" %}. Then, in the "Signature Method" and "Digest Method" drop-downs, choose the hashing algorithm used by your SAML issuer. ![Dropdownmenüs für die Hash-Algorithmen für die Signaturmethode und Digest-Methode, die Dein SAML-Aussteller verwendet](/assets/images/help/saml/saml_hashing_method.png) + +1. Before enabling SAML SSO for your enterprise, to ensure that the information you've entered is correct, click **Test SAML configuration**. ![Schaltfläche zum Testen der SAML-Konfiguration vor dem Erzwingen](/assets/images/help/saml/saml_test.png) + +1. Klicke auf **Save** (Speichern). + + {% note %} + + **Note:** When you require SAML SSO for your enterprise, the setup user will no longer have access to the enterprise but will remain signed in to GitHub. Only {% data variables.product.prodname_managed_users %} provisioned by your IdP will have access to the enterprise. + + {% endnote %} + +1. To ensure you can still access your enterprise in the event that your identity provider is ever unavailable in the future, click **Download**, **Print**, or **Copy** to save your recovery codes. ![Schaltfläche zum Testen der SAML-Konfiguration vor dem Erzwingen](/assets/images/help/saml/saml_recovery_code_options.png) + +### Enabling provisioning + +After you enable SAML SSO, enable provisioning. For more information, see "[Configuring SCIM provisioning for enterprise managed users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users)." + +## Saving your recovery codes + +In the event that your identity provider is unavailable, you can use the setup user and a recovery code to sign in and access your enterprise. If you did not save your recovery codes when you configured SAML SSO, you can still access them from your enterprise's settings. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} + +1. Under "Require SAML authentication", click **Save your recovery codes**. ![Schaltfläche zum Testen der SAML-Konfiguration vor dem Erzwingen](/assets/images/help/enterprises/saml-recovery-codes-link.png) + +2. To save your recovery codes, click **Download**, **Print**, or **Copy**. ![Schaltfläche zum Testen der SAML-Konfiguration vor dem Erzwingen](/assets/images/help/saml/saml_recovery_code_options.png) diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md new file mode 100644 index 0000000000..3ebc5ad6fb --- /dev/null +++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md @@ -0,0 +1,76 @@ +--- +title: Configuring SCIM provisioning for Enterprise Managed Users with Okta +shortTitle: Set up provisioning with Okta +intro: You can provision new users and manage their membership of your enterprise and teams using Okta as your identity provider. +product: '{% data reusables.gated-features.emus %}' +versions: + fpt: '*' +redirect_from: + - /early-access/github/articles/configuring-provisioning-for-managed-users-with-okta +topics: + - Accounts + - Enterprise +--- + +## About provisioning with Okta + +You can use {% data variables.product.prodname_emus %} with Okta as your identity provider to provision new accounts, manage enterprise membership, and manage team memberships for organizations in your enterprise. For more information about provisioning for {% data variables.product.prodname_emus %}, see "[Configuring SCIM provisioning for enterprise managed users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users)." + +Before you can configure provisioning with Okta, you must configure SAML single-sign on. For more information, see "[Configuring SAML single sign-on for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." + +To configure provisioning with Okta, you must set your enterprise's name in the {% data variables.product.prodname_emu_idp_application %} application and enter your setup user's personal access token. You can then start provisioning users in Okta. + +## Supported features + +{% data variables.product.prodname_emus %} supports many provisioning features in Okta. + +| Funktion | Beschreibung | +| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Push neuer Benutzer | Users that are assigned to the {% data variables.product.prodname_emu_idp_application %} application in Okta are automatically created in the enterprise on {% data variables.product.product_name %}. | +| Push Profile Update | Updates made to the user's profile in Okta will be pushed to {% data variables.product.product_name %}. | +| Push Groups | Groups in Okta that are assigned to the {% data variables.product.prodname_emu_idp_application %} application as Push Groups are automatically created in the enterprise on {% data variables.product.product_name %}. | +| Push Benutzer-Deaktivierung | Unassigning the user from the {% data variables.product.prodname_emu_idp_application %} application in Okta will disable the user on {% data variables.product.product_name %}. The user will not be able to sign in, but the user's information is maintained. | +| Benutzer reaktivieren | Users in Okta whose Okta accounts are reactivated and who are assigned back to the {% data variables.product.prodname_emu_idp_application %} application will be enabled. | + +{% note %} + +**Note:** {% data variables.product.prodname_emus %} does not support modifications to usernames. + +{% endnote %} + +## Setting your enterprise name + +After your {% data variables.product.prodname_emu_enterprise %} has been created, you can begin to configure provisioning by setting your enterprise name in Okta. + +1. Navigate to your {% data variables.product.prodname_emu_idp_application %} application on Okta. +1. Click the **Sign On** tab. +1. To make changes, click **Edit**. +1. Under "Advanced Sign-on Settings", in the "Enterprise Name" text box, type your enterprise name. For example, if you access your enterprise at `https://github.com/enterprises/octoinc`, your enterprise name would be "octoinc". ![Screenshot of the Enterprise Name field on Okta](/assets/images/help/enterprises/okta-emu-enterprise-name.png) +1. To save your enterprise name, click **Save**. + +## Configuring provisioning + +After setting your enterprise name, you can proceed to configure provisioning settings. + +To configure provisioning, the setup user with the **@SHORT-CODE_admin** username will need to provide a personal access token with the **admin:enterprise** scope. For more information on creating a new token, see "[Creating a personal access token](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users#creating-a-personal-access-token)." + +1. Navigate to your {% data variables.product.prodname_emu_idp_application %} application on Okta. +1. Click the **Provisioning** tab. +1. In the settings menu, click **Integration**. +1. To make changes, click **Edit**. +1. Wähle **Enable API integration** (API-Integration aktivieren). +1. In the "API Token" field, enter the personal access token with the **admin:enterprise** scope belonging to the setup user. ![Screenshot showing the API Token field on Okta](/assets/images/help/enterprises/okta-emu-token.png) +1. Click **Test API Credentials**. If the test is successful, a verification message will appear at the top of the screen. +1. To save the token, click **Save**. +1. In the settings menu, click **To App**. ![Screenshot showing the To App menu item on Okta](/assets/images/help/enterprises/okta-emu-to-app-menu.png) +1. To the right of "Provisioning to App", to allow changes to be made, click **Edit**. +1. Select **Enable** for **Create Users**, **Update User Attributes**, and **Deactivate Users**. ![Screenshot showing provisioning options on Okta](/assets/images/help/enterprises/okta-emu-provisioning-to-app.png) +1. To finish configuring provisioning, click **Save**. + +## Assigning users + +After you have configured SAML SSO and provisioning, you will be able provision new users on {% data variables.product.prodname_dotcom_the_website %} by assigning users to the {% data variables.product.prodname_emu_idp_application %} application. You can also automatically manage organization membership by assigning groups to the application as push groups and connecting the push groups to teams in your organizations. For more information about managing teams, see "[Managing team memberships with identity provider groups](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)." + +When assigning users, you can use the "Roles" attribute in the {% data variables.product.prodname_emu_idp_application %} application to set a user's role in your enterprise on {% data variables.product.product_name %}. For more information on roles, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)." + +![Screenshot showing the role options for provisioned user on Okta](/assets/images/help/enterprises/okta-emu-user-role.png) diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md new file mode 100644 index 0000000000..5b6d7986e9 --- /dev/null +++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md @@ -0,0 +1,54 @@ +--- +title: Configuring SCIM provisioning for Enterprise Managed Users +shortTitle: Provisioning managed users +intro: You can configure your identity provider to provision new users and manage their membership in your enterprise and teams. +product: '{% data reusables.gated-features.emus %}' +versions: + fpt: '*' +topics: + - Accounts + - Enterprise +--- + +## About provisioning for {% data variables.product.prodname_emus %} + +You can configure provisioning for {% data variables.product.prodname_emus %} to create, manage, and deactivate user accounts for your enterprise members. When you configure provisioning for {% data variables.product.prodname_emus %}, users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your identity provider are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} via SCIM, and the users are added to your enterprise. + +When you update information associated with a user's identity on your IdP, your IdP will update the user's account on GitHub.com. When you unassign the user from the {% data variables.product.prodname_emu_idp_application %} application or deactivate a user's account on your IdP, your IdP will communicate with {% data variables.product.prodname_dotcom %} to invalidate any SAML sessions and disable the member's account. The disabled account's information is maintained and their username is changed to a hash of their original username with the short code appended. If you reassign a user to the {% data variables.product.prodname_emu_idp_application %} application or reactivate their account on your IdP, the {% data variables.product.prodname_managed_user %} account on {% data variables.product.prodname_dotcom %} will be reactivated and username restored. + +Groups in your IdP can be used to manage team membership within your enterprise's organizations, allowing you to configure repository access and permissions through your IdP. For more information, see "[Managing team memberships with identity provider groups](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)." + +## Vorrausetzungen + +Before you can configure provisioning for {% data variables.product.prodname_emus %}, you must configure SAML single-sign on. For more information, see "[Configuring SAML single sign-on for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." + +## Creating a personal access token + +To configure provisioning for your {% data variables.product.prodname_emu_enterprise %}, you need a personal access token with the **admin:enterprise** scope that belongs to the setup user. + +{% warning %} + +**Warning:** If the token expires or a provisioned user creates the token, SCIM provisioning may unexpectedly stop working. Make sure that you create the token while signed in as the setup user and that the token expiration is set to "No expiration". + +{% endwarning %} + +1. Sign into {% data variables.product.prodname_dotcom_the_website %} as the setup user for your new enterprise with the username **@SHORT-CODE_admin**. +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.developer_settings %} +{% data reusables.user_settings.personal_access_tokens %} +{% data reusables.user_settings.generate_new_token %} +1. Under **Note**, give your token a descriptive name. ![Screenshot showing the token's name](/assets/images/help/enterprises/emu-pat-name.png) +1. Select the **Expiration** drop-down menu, then click **No expiration**. ![Screenshot showing token expiration set to no expiration](/assets/images/help/enterprises/emu-pat-no-expiration.png) +1. Select the **admin:enterprise** scope. ![Screenshot showing the admin:enterprise scope](/assets/images/help/enterprises/enterprise-pat-scope.png) +1. Klicke auf **Generate token** (Token erzeugen). ![Schaltfläche „Generate token“ (Token erzeugen)](/assets/images/help/settings/generate_token.png) +1. To copy the token to your clipboard, click the {% octicon "paste" aria-label="The copy icon" %}. ![Newly created token](/assets/images/help/settings/personal_access_tokens.png) +2. To save the token for use later, store the new token securely in a password manager. + +## Configuring provisioning for {% data variables.product.prodname_emus %} + +After creating your personal access token and storing it securely, you can configure provisioning on your identity provider. + +To configure Azure Active Directory to provision users for your {% data variables.product.prodname_emu_enterprise %}, see [Tutorial: Configure GitHub Enterprise Managed User for automatic user provisioning](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-enterprise-managed-user-provisioning-tutorial) in the Azure AD documentation. + +To configure Okta to provision users for your {% data variables.product.prodname_emu_enterprise %}, see "[Configuring SCIM provisioning for Enterprise Managed Users with Okta](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users-with-okta)." + diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/index.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/index.md new file mode 100644 index 0000000000..7104779c1f --- /dev/null +++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/index.md @@ -0,0 +1,19 @@ +--- +title: Managing your enterprise users with your identity provider +shortTitle: Manage users with your IdP +product: '{% data reusables.gated-features.emus %}' +intro: 'You can manage identity and access with your identity provider and provision accounts that can only contribute to your enterprise.' +versions: + fpt: '*' +topics: + - Enterprise + - Accounts +children: + - /about-enterprise-managed-users + - /configuring-saml-single-sign-on-for-enterprise-managed-users + - /configuring-scim-provisioning-for-enterprise-managed-users + - /configuring-scim-provisioning-for-enterprise-managed-users-with-okta + - /managing-team-memberships-with-identity-provider-groups + - /auditing-activity-in-your-enterprise +--- + diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups.md new file mode 100644 index 0000000000..ec04fccc86 --- /dev/null +++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups.md @@ -0,0 +1,67 @@ +--- +title: Managing team memberships with identity provider groups +shortTitle: Manage teams with your IdP +intro: 'You can manage team membership on {% data variables.product.product_name %} through your identity provider (IdP) by connecting IdP groups with your {% data variables.product.prodname_emu_enterprise %}.' +product: '{% data reusables.gated-features.emus %}' +versions: + fpt: '*' +topics: + - Accounts + - Enterprise +--- + +## About team management with {% data variables.product.prodname_emus %} + +With {% data variables.product.prodname_emus %}, you can manage team membership within your enterprise through your IdP. When you connect a team in one of your enterprise's organizations to an IdP group, changes to membership from the IdP group are reflected in your enterprise automatically, reducing the need for manual updates and custom scripts. + +When a change to an IdP group or a new team connection results in a {% data variables.product.prodname_managed_user %} joining a team in an organization they were not already a member of, the {% data variables.product.prodname_managed_user %} will automatically be added to the organization. Organization owners can also manage organization membership manually. When you disconnect a group from a team, users who became members of the organization via team membership are removed from the organization if they are not assigned membership in the organization by any other means. + +You can connect a team in your enterprise to one IdP group. You can assign the same IdP group to multiple teams in your enterprise. + +If you are connecting an existing team to an IdP group, you must first remove any members that were added manually. After you connect a team in your enterprise to an IdP group, your IdP administrator must make team membership changes through the identity provider. You cannot manage team membership on {% data variables.product.prodname_dotcom_the_website %}. + +When group membership changes on your IdP, your IdP sends a SCIM request with the changes to {% data variables.product.prodname_dotcom_the_website %} according to the schedule determined by your IdP, so change may not be immediate. Any requests that change team or organization membership will register in the audit log as changes made by the account used to configure user provisioning. + +Teams connected to IdP groups cannot be parents of other teams nor a child of another team. If the team you want to connect to an IdP group is a parent or child team, we recommend creating a new team or removing the nested relationships that make your team a parent team. + +To manage repository access for any team in your enterprise, including teams connected to an IdP group, you must make changes on {% data variables.product.prodname_dotcom_the_website %}. 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)". + +## Creating a new team connected to an IdP group + +Any member of an organization can create a new team and connect the team to an IdP group. + +{% data reusables.profile.access_org %} +{% data reusables.user_settings.access_org %} +{% data reusables.organizations.new_team %} +{% data reusables.organizations.team_name %} +{% data reusables.organizations.team_description %} +1. To connect a team, select the "Identity Provider Groups" drop-down menu and click the team you want to connect. ![Dropdownmenü zur Auswahl einer Identitätsanbieter-Gruppe](/assets/images/help/teams/choose-an-idp-group.png) +{% data reusables.organizations.team_visibility %} +{% data reusables.organizations.create_team %} + +## Managing the connection between an existing team and an IdP group + +Organization owners and team maintainers can manage the existing connection between an IdP group and a team. + +{% note %} + +**Note**: Before you connect an existing team on {% data variables.product.prodname_dotcom_the_website %} to an IdP group for the first time, all members of the team on {% data variables.product.prodname_dotcom_the_website %} must first be removed. For more information, see "[Removing organization members from a team](/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team)." + +{% endnote %} + +{% data reusables.profile.access_profile %} + +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +1. Optionally, under "Identity Provider Group", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="X symbol" %}. ![Trennen einer verbundenen IdP-Gruppe von einem GitHub-Team](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png) +1. To connect an IdP group, under "Identity Provider Group", select the drop-down menu, and click an identity provider group from the list. ![Drop-down menu to choose identity provider group](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png) +1. Klicke auf **Save changes** (Änderungen speichern). + +## Viewing IdP groups and connected teams + +You can review a list of IdP groups, any teams connected to an IdP group, and see the membership of each IdP group on {% data variables.product.product_name %}. You must edit the membership for a group on your IdP. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.identity-provider-tab %} +1. Under "Identity Provider (IdP) Groups", review the list of IdP groups. diff --git a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account.md b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account.md index 6165fcf225..fbf7fe9d1f 100644 --- a/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account.md +++ b/translations/de-DE/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account.md @@ -42,7 +42,9 @@ You can disable all workflows for an enterprise or set a policy that configures ## Configuring required approval for workflows from public forks -{% data reusables.actions.workflow-run-approve-public-fork %} You can configure this behavior for your enterprise using the procedure below. +{% data reusables.actions.workflow-run-approve-public-fork %} + +You can configure this behavior for your enterprise using the procedure below. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} diff --git a/translations/de-DE/content/github/site-policy/github-data-protection-agreement.md b/translations/de-DE/content/github/site-policy/github-data-protection-agreement.md new file mode 100644 index 0000000000..7554793204 --- /dev/null +++ b/translations/de-DE/content/github/site-policy/github-data-protection-agreement.md @@ -0,0 +1,974 @@ +--- +title: GitHub Data Protection Agreement +redirect_from: + - /github/site-policy/github-data-protection-addendum + - /github/site-policy-deprecated/github-data-protection-addendum + - /github/site-policy/github-data-protection-agreement-non-enterprise-customers +versions: + fpt: '*' +--- + +## Einführung + +The parties agree that this GitHub Data Protection Agreement (“**DPA**”) sets forth their obligations with respect to the processing and security of Personal Data and, where explicitly stated in the DPA Terms, Customer Data in connection with the Online Services provided by GitHub, Inc. (“**GitHub**”). The DPA (including its Appendix and Attachments) is between GitHub and any customer receiving Online Services from GitHub based on the GitHub Customer Agreement (“**Customer**”), and is incorporated by reference into the GitHub Customer Agreement. + +In the event of any conflict or inconsistency between the DPA Terms and any other terms in the GitHub Customer Agreement, the DPA Terms will prevail. The provisions of the DPA Terms supersede any conflicting provisions of the GitHub Privacy Statement that otherwise may apply to processing of Personal Data. For clarity, the Standard Contractual Clauses prevail over any other term of the DPA Terms. + +### Applicable DPA Terms and Updates + +#### Limits on Updates + +When Customer renews or purchases a new subscription to an Online Service, the then-current DPA Terms will apply and will not change during the term of that new subscription for that Online Service. + +#### New Features, Supplements, or Related Software + +Notwithstanding the foregoing limits on updates, when GitHub introduces features, supplements or related software that are new (i.e., that were not previously included with the subscription), GitHub may provide terms or make updates to the DPA that apply to Customer’s use of those new features, supplements or related software. If those terms include any material adverse changes to the DPA Terms, GitHub will provide Customer a choice to use the new features, supplements, or related software, without loss of existing functionality of a generally available Online Service. If Customer does not use the new features, supplements, or related software, the corresponding new terms will not apply. + +#### Government Regulation and Requirements + +Notwithstanding the foregoing limits on updates, GitHub may modify or terminate an Online Service in any country or jurisdiction where there is any current or future government requirement or obligation that (1) subjects GitHub to any regulation or requirement not generally applicable to businesses operating there, (2) presents a hardship for GitHub to continue operating the Online Service without modification, and/or (3) causes GitHub to believe the DPA Terms or the Online Service may conflict with any such requirement or obligation. + +### Electronic Notices + +GitHub may provide Customer with information and notices about Online Services electronically, including via email, or through a web site that GitHub identifies. Notice is given as of the date it is made available by GitHub. + +### Prior Versions + +The DPA Terms provide terms for Online Services that are currently available. For earlier versions of the DPA Terms, Customer may contact its reseller or GitHub Account Manager. + +## Definitionen + +Capitalized terms used but not defined in this DPA will have the meanings provided in the GitHub Customer Agreement. The following defined terms are used in this DPA: + +“**CCPA**” means the California Consumer Privacy Act as set forth in Cal. Civ. Code §1798.100 et seq. and its implementing regulations. + +“**Customer Data**” means all data, including all text, sound, video, or image files, and software, that are provided to GitHub by, or on behalf of, Customer through use of the Online Service. + +“**Data Protection Requirements**” means the GDPR, Local EU/EEA Data Protection Laws, CCPA, and any applicable laws, regulations, and other legal requirements relating to (a) privacy and data security; and (b) the use, collection, retention, storage, security, disclosure, transfer, disposal, and other processing of any Personal Data. + +“**Diagnostic Data**” means data collected or obtained by GitHub from software that is locally installed by Customer in connection with the Online Service. Diagnostic Data may also be referred to as telemetry. Diagnostic Data does not include Customer Data, Service Generated Data, or Professional Services Data. + +“**DPA Terms**” means both the terms in this DPA and any Online Service-specific terms in the GitHub Customer Agreement that specifically supplement or modify the privacy and security terms in this DPA for a specific Online Service (or feature of an Online Service). In the event of any conflict or inconsistency between the DPA and such Online Service-specific terms, the Online Service-specific terms shall prevail as to the applicable Online Service (or feature of that Online Service). + +“**GDPR**” means Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation). In connection with the United Kingdom, “GDPR” means Regulation (EU) 2016/679 as transposed into national law of the United Kingdom by the UK European Union (Withdrawal) Act 2018 and amended by the UK Data Protection, Privacy and Electronic Communications (Amendments etc.) (EU Exit) Regulations 2019 (as may be amended from time to time). + +“**Local EU/EEA Data Protection Laws**” means any subordinate legislation and regulation implementing the GDPR. + +“**GDPR Related Terms**” means the terms in Attachment 3, under which GitHub makes binding commitments regarding its processing of Personal Data as required by Article 28 of the GDPR. + +“**GitHub Affiliate**” means any entity that directly or indirectly controls, is controlled by or is under common control with GitHub. + +“**GitHub Customer Agreement**” means the service or other agreement(s) entered into by Customer with GitHub for Online Services. + +“**GitHub Privacy Statement**” means the GitHub privacy statement available at https://docs.github.com/en/github/site-policy/github-privacy-statement. + +“**Online Service**” means any service or software provided by GitHub to Customer under the GitHub Customer Agreement agreed upon with Customer, including Previews, updates, patches, bug fixes, and technical support. + +“**Personal Data**” means any information relating to an identified or identifiable natural person. An identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person. + +“**Preview**” means Online Services provided for preview, evaluation, demonstration or trial purposes, or pre-release versions of the Online Services. + +“**Professional Services Data**” means all data, including all text, sound, video, image files or software, that are provided to GitHub, by or on behalf of a Customer (or that Customer authorizes GitHub to obtain from an Online Service) or otherwise obtained or processed by or on behalf of GitHub through an engagement with GitHub to obtain Professional Services. Professional Services Data includes Support Data. + +“**Service Generated Data**” means data generated or derived by GitHub through the operation of an Online Service. Service Generated Data does not include Customer Data, Diagnostic Data, or Professional Services Data. + +“**Standard Contractual Clauses**” means either of the following sets of Standard Contractual Clauses, as applicable in the individual case to the transfer of personal data according to the section of this DPA entitled “Data Transfers and Location” below: +- the Standard Contractual Clauses (MODULE TWO: Transfer controller to processor), dated 4 June 2021, for the transfer of personal data to third countries pursuant to Regulation (EU) 2016/679 of the European Parliament and of the Council, as described in Article 46 of the GDPR and approved by European Commission Implementing Decision (EU) 2021/91 (“Standard Contractual Clauses (EU/EEA)”). The Standard Contractual Clauses (EU/EEA) are set forth in Attachment 1. +- the Standard Contractual Clauses (Processors), dated 5 February 2010, for the transfer of personal data to processors established in third countries which do not ensure an adequate level of data protection, as described in Article 46 of the GDPR, approved by European Commission Decision 2010/87/EU and recognized by the regulatory or supervisory authorities of the United Kingdom for use in connection with data transfers from the United Kingdom (“Standard Contractual Clauses (UK)”). The Standard Contractual Clauses (UK) are set forth in Attachment 2. + +“**Subprocessor**” means other processors used by GitHub to process Personal Data on behalf of Customer in connection with the Online Services, as described in Article 28 of the GDPR. + +“**Support Data**” means all data, including all text, sound, video, image files, or software, that are provided to GitHub by or on behalf of Customer (or that Customer authorizes GitHub to obtain from an Online Service) through an engagement with GitHub to obtain technical support for Online Services covered under this agreement. Support Data is a subset of Professional Services Data. + +Lower case terms used but not defined in this DPA, such as “personal data breach”, “processing”, “controller”, “processor”, “profiling”, “personal data”, and “data subject” will have the same meaning as set forth in Article 4 of the GDPR, irrespective of whether GDPR applies. The terms “data importer” and “data exporter” have the meanings given in the Standard Contractual Clauses. + +For clarity, and as detailed above, data defined as Customer Data, Diagnostic Data, Service Generated Data, and Professional Services Data may contain Personal Data. For illustrative purposes, please see the chart inserted below: + +
+ personal_data_types +
+ +Above is a visual representation of the data types defined in the DPA. All Personal Data is processed as a part of one of the other data types (all of which also include non-personal data). Support Data is a sub-set of Professional Services Data. Except where explicitly stated otherwise, the DPA Terms exclusively apply to Personal Data. + +## General Terms + +### Compliance with Laws + +GitHub will comply with all laws and regulations applicable to its provision of the Online Services, including security breach notification law and Data Protection Requirements. However, GitHub is not responsible for compliance with any laws or regulations applicable to Customer or Customer’s industry that are not generally applicable to information technology service providers. GitHub does not determine whether Customer Data includes information subject to any specific law or regulation. All Security Incidents are subject to the Security Incident Notification terms below. + +Customer must comply with all laws and regulations applicable to its use of Online Services, including laws related to biometric data, confidentiality of communications, and Data Protection Requirements. Customer is responsible for determining whether the Online Services are appropriate for storage and processing of information subject to any specific law or regulation and for using the Online Services in a manner consistent with Customer’s legal and regulatory obligations. Customer is responsible for responding to any request from a third party regarding Customer’s use of an Online Service, such as a request to take down content under the U.S. Digital Millennium Copyright Act or other applicable laws. + +## Datenschutz + +Terms This section of the DPA includes the following subsections: +- Scope +- Nature of Data Processing; Ownership +- Disclosure of Processed Data +- Processing of Personal Data; GDPR +- Data Security +- Security Incident Notification +- Data Transfers and Location +- Data Retention and Deletion +- Processor Confidentiality Commitment +- Notice and Controls on Use of Subprocessors +- Educational Institutions +- CJIS Customer Agreement, HIPAA Business Associate, Biometric Data +- California Consumer Privacy Act (CCPA) +- How to Contact GitHub +- Appendix A – Security Measures + +### Scope + +The DPA Terms apply to all Online Services. + +Previews may employ lesser or different privacy and security measures than those typically present in the Online Services. Unless otherwise noted, Customer should not use Previews to process Personal Data or other data that is subject to legal or regulatory compliance requirements. The following terms in this DPA do not apply to Previews: Processing of Personal Data; GDPR, Data Security, and California Consumer Privacy Act. + +### Nature of Data Processing; Ownership + +Except as otherwise stated in the DPA Terms, GitHub will use and otherwise process Customer Data and Personal Data as described and subject to the limitations provided below (a) to provide Customer the Online Service in accordance with Customer’s documented instructions, and/or (b) for GitHub’s legitimate business operations incident to delivery of the Online Services to Customer. As between the parties, Customer retains all right, title and interest in and to Customer Data. GitHub acquires no rights in Customer Data other than the rights Customer grants to GitHub in this section. This paragraph does not affect GitHub’s rights in software or services GitHub licenses to Customer. + +#### Processing to Provide Customer the Online Services + +For purposes of this DPA, “to provide” an Online Service consists of: +- Delivering functional capabilities as licensed, configured, and used by Customer and its users, including providing personalized user experiences; +- Troubleshooting (e.g., preventing, detecting, and repairing problems); and +- Ongoing improvement (e.g., installing the latest updates and making improvements to user productivity, reliability, efficacy, and security). + +When providing Online Services, GitHub will use or otherwise process Personal Data only on Customer’s behalf and in accordance with Customer’s documented instructions. + +#### Processing for GitHub’s Legitimate Business Operations + +For purposes of this DPA, “GitHub’s legitimate business operations” consist of the following, each as incident to delivery of the Online Services to Customer: (1) billing and account management; (2) compensation (e.g., calculating employee commissions and partner incentives); (3) internal reporting and business modeling (e.g., forecasting, revenue, capacity planning, product strategy); (4) combatting fraud, abuse, cybercrime, or cyber-attacks that may affect GitHub or Online Services; (5) improving the core functionality of accessibility, privacy or energy-efficiency; (6) financial reporting and compliance with legal obligations (subject to the limitations on disclosure of Processed Data outlined below); (7) the creation or management of end user accounts and profiles by GitHub for individual users of Customer (except where Customer creates, manages or otherwise controls such end user accounts or profiles itself); and (8) other purposes pertaining to Personal Data not provided by Customer for storage in GitHub repositories or in connection with Professional Services. + +When processing for GitHub’s legitimate business operations, GitHub will not use or otherwise process Personal Data for: (a) user profiling, (b) advertising or similar commercial purposes, (c) data selling or brokering, or (d) any other purpose, other than for the purposes set out in this section. + +### Disclosure of Processed Data + +GitHub will not disclose or provide access to any Processed Data except: (1) as Customer directs; (2) as described in this DPA; or (3) as required by law. For purposes of this section, “Processed Data” means: (a) Customer Data; (b) Personal Data and (c) any other data processed by GitHub in connection with the Online Service that is Customer’s confidential information under the GitHub Customer Agreement. All processing of Processed Data is subject to GitHub’s obligation of confidentiality under the GitHub Customer Agreement. + +GitHub will not disclose or provide access to any Processed Data to law enforcement unless required by law. If law enforcement contacts GitHub with a demand for Processed Data, GitHub will attempt to redirect the law enforcement agency to request that data directly from Customer. If compelled to disclose or provide access to any Processed Data to law enforcement, GitHub will promptly notify Customer and provide a copy of the demand, unless legally prohibited from doing so. + +Upon receipt of any other third-party request for Processed Data, GitHub will promptly notify Customer unless prohibited by law. GitHub will reject the request unless required by law to comply. If the request is valid, GitHub will attempt to redirect the third party to request the data directly from Customer. + +GitHub will not provide any third party: (a) direct, indirect, blanket, or unfettered access to Processed Data; (b) platform encryption keys used to secure Processed Data or the ability to break such encryption; or (c) access to Processed Data if GitHub is aware that the data is to be used for purposes other than those stated in the third party’s request. + +In support of the above, GitHub may provide Customer’s basic contact information to the third party. + +### Processing of Personal Data; GDPR + +All Personal Data processed by GitHub in connection with the Online Services is obtained as part of either Customer Data, Professional Services Data (including Support Data), Diagnostic Data, or Service Generated Data. Personal Data provided to GitHub by, or on behalf of, Customer through use of the Online Service is also Customer Data. Pseudonymized identifiers may be included in Diagnostic Data or Service Generated Data and are also Personal Data. Any Personal Data pseudonymized, or de-identified but not anonymized, or Personal Data derived from Personal Data is also Personal Data. + +To the extent GitHub is a processor or subprocessor of Personal Data subject to the GDPR, the GDPR Related Terms in Attachment 3 govern that processing and the parties also agree to the following terms in this sub-section (“Processing of Personal Data; GDPR”): + +#### Processor and Controller Roles and Responsibilities + +Customer and GitHub agree that Customer is the controller of Personal Data and GitHub is the processor of such data, except (a) when Customer acts as a processor of Personal Data, in which case GitHub is a subprocessor; or (b) as stated otherwise in the GitHub Customer Agreement or this DPA. When GitHub acts as the processor or subprocessor of Personal Data, it will process Personal Data only on Customer’s behalf and in accordance with documented instructions from Customer. Customer agrees that its GitHub Customer Agreement (including the DPA Terms and any applicable updates), along with the product documentation and Customer’s use and configuration of features in the Online Services, are Customer’s complete documented instructions to GitHub for the processing of Personal Data. Information on use and configuration of the Online Services can be found at https://docs.github.com or a successor location. Any additional or alternate instructions must be agreed to according to the process for amending Customer’s GitHub Customer Agreement. In any instance where the GDPR applies and Customer is a processor, Customer warrants to GitHub that Customer’s instructions, including appointment of GitHub as a processor or subprocessor, have been authorized by the relevant controller. + +To the extent GitHub uses or otherwise processes Personal Data subject to the GDPR for GitHub’s legitimate business operations incident to delivery of the Online Services to Customer, GitHub will comply with the obligations of an independent data controller under GDPR for such use. GitHub is accepting the added responsibilities of a data “controller” under the GDPR for processing in connection with its legitimate business operations to: (a) act consistent with regulatory requirements, to the extent required under the GDPR; and (b) provide increased transparency to Customers and confirm GitHub’s accountability for such processing. GitHub employs safeguards to protect Personal Data in processing, including those identified in this DPA and those contemplated in Article 6(4) of the GDPR. With respect to processing of Personal Data under this paragraph, GitHub makes the commitments set forth in the Standard Contractual Clauses set forth in Attachment 1 or Attachment 2 (as applicable); for those purposes, (i) any GitHub disclosure of Personal Data, as described in Annex III to Attachment 1 or Appendix 3 to Attachment 2 (as applicable), that has been transferred in connection with GitHub’s legitimate business operations is deemed a “Relevant Disclosure” and (ii) the commitments in Annex III to Attachment 1 or Appendix 3 to Attachment 2 (as applicable) apply to such Personal Data. + +#### Processing Details + +The parties acknowledge and agree that: + +- **Subject Matter**. The subject-matter of the processing is limited to Personal Data within the scope of the section of this DPA entitled “Nature of Data Processing; Ownership” above and the GDPR. +- **Duration of the Processing**. The duration of the processing shall be in accordance with Customer instructions and the terms of the DPA. +- **Nature and Purpose of the Processing**. The nature and purpose of the processing shall be to provide the Online Service pursuant to Customer’s GitHub Customer Agreement and for GitHub’s legitimate business operations incident to delivery of the Online Service to Customer (as further described in the section of this DPA entitled “Nature of Data Processing; Ownership” above). +- **Categories of Data**. The types of Personal Data processed by GitHub when providing the Online Service include: (i) Personal Data that Customer elects to include in Customer Data or Professional Services Data (including, without limitation, Support Data); and (ii) those expressly identified in Article 4 of the GDPR that may be contained in Diagnostic Data or Service Generated Data. The types of Personal Data that Customer elects to include in Customer Data or Professional Services Data (including, without limitation, Support Data) may be any categories of Personal Data identified in records maintained by Customer acting as controller pursuant to Article 30 of the GDPR, including the categories of Personal Data set forth in Annex I to Attachment 1 or Appendix 1 to Attachment 2 (as applicable). +- Data Subjects. The categories of data subjects are Customer’s representatives and end users, such as employees, contractors, collaborators, and customers, and may include any other categories of data subjects as identified in records maintained by Customer acting as controller pursuant to Article 30 of the GDPR, including the categories of data subjects set forth in Annex I to Attachment 1 or Appendix 1 to Attachment 2 (as applicable). + +#### Data Subject Rights; Assistance with Requests + +GitHub will make available to Customer, in a manner consistent with the functionality of the Online Service and GitHub’s role as a processor of Personal Data of data subjects, the ability to fulfill data subject requests to exercise their rights under the GDPR. If GitHub receives a request from Customer’s data subject to exercise one or more of its rights under the GDPR in connection with an Online Service for which GitHub is a data processor or subprocessor, GitHub will redirect the data subject to make its request directly to Customer. Customer will be responsible for responding to any such request including, where necessary, by using the functionality of the Online Service. GitHub shall comply with reasonable requests by Customer to assist with Customer’s response to such a data subject request. + +#### Records of Processing Activities + +To the extent the GDPR requires GitHub to collect and maintain records of certain information relating to Customer, Customer will, where requested, supply such information to GitHub and keep it accurate and up-to-date. GitHub may make any such information available to the supervisory authority if required by the GDPR. + +### Data Security + +GitHub will implement and maintain appropriate technical and organizational measures and security safeguards against accidental or unlawful destruction, or loss, alteration, unauthorized disclosure of or access to, Customer Data and Personal Data processed by GitHub on behalf and in accordance with the documented instructions of Customer in connection with the Online Services. GitHub will regularly monitor compliance with these measures and safeguards and will continue to take appropriate steps throughout the term of the GitHub Customer Agreement. Appendix A – Security Safeguards contains a description of the technical and organizational measures and security safeguards implemented by GitHub. + +Customer is solely responsible for making an independent determination as to whether the technical and organizational measures and security safeguards for an Online Service meet Customer’s requirements, including any of its security obligations under applicable Data Protection Requirements. Customer acknowledges and agrees that (taking into account the state of the art, the costs of implementation, and the nature, scope, context and purposes of the processing of its Customer Data and Personal Data as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons) the technical and organizational measures and security safeguards implemented and maintained by GitHub provide a level of security appropriate to the risk with respect to its Customer Data and Personal Data. Customer is responsible for implementing and maintaining privacy protections and security measures for components that Customer provides or controls. + +GitHub will provide security compliance reporting such as external SOC1, type 2 and SOC2, type2 audit reports upon Customer request. Customer agrees that any information and audit rights granted by the applicable Data Protection Requirements (including, where applicable, Article 28(3)(h) of the GDPR) will be satisfied by these compliance reports, and will otherwise only arise to the extent that GitHub's provision of a compliance report does not provide sufficient information, or to the extent that Customer must respond to a regulatory or supervisory authority audit or investigation. + +Should Customer be subject to a regulatory or supervisory authority audit or investigation or carry out an audit or investigation in response to a request by a regulatory or supervisory authority that requires participation from GitHub, and Customers’ obligations cannot reasonably be satisfied (where allowable by Customer’s regulators) through audit reports, documentation, or compliance information that GitHub makes generally available to its customers, then GitHub will promptly respond to Customer’s additional instructions and requests for information, in accordance with the following terms and conditions: + +- GitHub will provide access to relevant knowledgeable personnel, documentation, and application software. +- Customer and GitHub will mutually agree in a prior written agreement (email is acceptable) upon the scope, timing, duration, control and evidence requirements, provided that this requirement to agree will not permit GitHub to unreasonably delay its cooperation. +- Customer must ensure its regulator’s use of an independent, accredited third-party audit firm, during regular business hours, with reasonable advance written notice to GitHub, and subject to reasonable confidentiality procedures. Neither Customer, its regulators, nor its regulators’ delegates shall have access to any data from GitHub’s other customers or to GitHub systems or facilities not involved in the Online Services. +- Customer is responsible for all costs and fees related to GitHub’s cooperation with the regulatory audit of Customer, including all reasonable costs and fees for any and all time GitHub expends, in addition to the rates for services performed by GitHub. +- If the report generated from GitHub’s cooperation with the regulatory audit of Customer includes any findings pertaining to GitHub, Customer will share such report, findings, and recommended actions with GitHub where allowed by Customer’s regulators. + +### Security Incident Notification + +If GitHub becomes aware of a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Customer Data or Personal Data processed by GitHub on behalf and in accordance with the documented instructions of Customer in connection with the Online Services (each a "Security Incident"), GitHub will promptly and without undue delay (1) notify Customer of the Security Incident; (2) investigate the Security Incident and provide Customer with detailed information about the Security Incident; (3) take reasonable steps to mitigate the effects and to minimize any damage resulting from the Security Incident. + +Notification(s) of Security Incidents will be delivered to one or more of Customer's administrators by any means GitHub selects, including via email. It is Customer's sole responsibility to ensure it maintains accurate contact information with GitHub and that Customer's administrators monitor for and respond to any notifications. Der Kunde haftet alleinig für die Erfüllung seiner Pflichten nach den für den Kunden geltenden Vorschriften zur Vorfallsmitteilung und die Erfüllung aller Pflichten zur Mitteilung an Dritte im Zusammenhang mit Sicherheitsvorfällen. + +GitHub will make reasonable efforts to assist Customer in fulfilling Customer's obligation under GDPR Article 33 or other applicable law or regulations to notify the relevant regulatory or supervisory authority and individual data subjects about a Security Incident. + +GitHub’s notification of or response to a Security Incident under this section is not an acknowledgement by GitHub of any fault or liability with respect to the Security Incident. + +Customer must notify GitHub promptly about any possible misuse of its accounts or authentication credentials or any Security Incident related to an Online Service. + +### Data Transfers and Location + +Personal Data that GitHub processes on behalf and in accordance with the documented instructions of Customer in connection with the Online Services may not be transferred to, or stored and processed in a geographic location except in accordance with the DPA Terms and the safeguards provided below in this section. Taking into account such safeguards, Customer appoints GitHub to transfer Personal Data to the United States or any other country in which GitHub or its Subprocessors operate and to store and process Personal Data to provide the Online Services, except as may be described elsewhere in these DPA Terms. + +All transfers of Personal Data out of the European Union, European Economic Area, or Switzerland to provide the Online Services shall be governed by the Standard Contractual Clauses (EU/EEA) in Attachment 1. All transfers of Personal Data out of the United Kingdom to provide the Online Services shall be governed by the Standard Contractual Clauses (UK) in Attachment 2. For the purposes of the Standard Contractual Clauses (UK) in Attachment 2, references to the “European Union,” “EU,” “European Economic Area,” “EEA” or a “Member State” shall be interpreted to refer to the United Kingdom where reasonably necessary and appropriate to give full force and effect to the Standard Contractual Clauses (UK) with respect to transfers of Personal Data from the United Kingdom. This applies regardless of the fact that, effective January 31, 2020, the United Kingdom is no longer a Member State of the European Union or European Economic Area. + +GitHub will abide by the requirements of applicable European Union, European Economic Area, United Kingdom and Swiss data protection law, and other Data Protection Requirements, in each case regarding the transfer of Personal Data to recipients or jurisdictions outside such jurisdiction. All such transfers of Personal Data will, where applicable, be subject to appropriate safeguards as described in Article 46 of the GDPR and such transfers and safeguards will be documented according to Article 30(2) of the GDPR. + +Subject to the safeguards described above, GitHub may transfer, store and otherwise process Personal Data to or in jurisdictions and geographic locations worldwide as it, subject to its sole discretion, considers reasonably necessary in connection with the Online Services. + +### Data Retention and Deletion + +Upon Customer's reasonable request, unless prohibited by law, GitHub will return or destroy all Customer Data and Personal Data processed by GitHub on behalf and in accordance with the documented instructions of Customer in connection with the Online Services at all locations where it is stored within 30 days of the request, provided that it is no longer needed for providing the Online Services or the purposes for which a data subject had authorized the processing of their Personal Data. GitHub may retain Customer Data or Personal Data to the extent required by the applicable Data Protection Requirements or other applicable law, and only to the extent and for such period as required by the applicable Data Protection Requirements or other applicable law, provided that GitHub will ensure that the Customer Data or Personal Data is processed only as necessary for the purpose specified in the applicable Data Protection Requirements or other applicable law and no other purpose, and the Customer Data or Personal Data remains protected by the Applicable Data Protection Requirements or other applicable law. + +### Processor Confidentiality Commitment + +GitHub will ensure that its personnel engaged in the processing of Customer Data and Personal Data on behalf of Customer in connection with the Online Services (i) will process such data only on instructions from Customer or as described in this DPA, and (ii) will be obligated to maintain the confidentiality and security of such data even after their engagement ends. GitHub shall provide periodic and mandatory data privacy and security training and awareness to its employees with access to Customer Data and Personal Data in accordance with applicable Data Protection Requirements or other applicable law and industry standards. + +### Notice and Controls on Use of Subprocessors + +GitHub may hire Subprocessors to provide certain limited or ancillary services on its behalf. Customer consents to this engagement and to GitHub Affiliates as Subprocessors. The above authorizations will constitute Customer’s prior written consent to the subcontracting by GitHub of the processing of Personal Data if such consent is required under applicable law, the Standard Contractual Clauses or the GDPR Related Terms. + +GitHub is responsible for its Subprocessors’ compliance with GitHub’s obligations in this DPA. GitHub makes available information about Subprocessors on the GitHub website https://github.com/subprocessors (or a successor location). When engaging any Subprocessor, GitHub will ensure via a written contract that the Subprocessor may access and use Customer Data or Personal Data only to deliver the services GitHub has retained them to provide and is prohibited from using Customer Data or Personal Data for any other purpose. GitHub will ensure that Subprocessors are bound by written agreements that require them to provide at least the level of data protection required of GitHub by the DPA, including the limitations on disclosure of Personal Data. GitHub agrees to oversee the Subprocessors to ensure that these contractual obligations are met. + +From time to time, GitHub may engage new Subprocessors. GitHub will give Customer notice (by updating the website at https://github.com/github-subprocessors-list (or a successor location) and providing Customer with a mechanism to obtain notice of that update) of any new Subprocessor in advance of providing that Subprocessor with access to Customer Data. If GitHub engages a new Subprocessor for a new Online Service, GitHub will give Customer notice prior to availability of that Online Service. + +If Customer does not approve of a new Subprocessor, then Customer may terminate any subscription for the affected Online Service without penalty by providing, before the end of the relevant notice period, written notice of termination. Customer may also include an explanation of the grounds for non-approval together with the termination notice, in order to permit GitHub to re-evaluate any such new Subprocessor based on the applicable concerns. If the affected Online Service is part of a suite (or similar single purchase of services), then any termination will apply to the entire suite. After termination, GitHub will remove payment obligations for any subscriptions for the terminated Online Service from subsequent invoices to Customer or its reseller. + +### Educational Institutions +If Customer is an educational agency or institution subject to the regulations under the Family Educational Rights and Privacy Act, 20 U.S.C. § 1232g (FERPA), or similar state student or educational privacy laws (collectively “Educational Privacy Laws”), Customer shall not provide Personal Data covered by such Educational Privacy Laws to GitHub without obtaining GitHub’s prior, written and specific consent and entering into a separate agreement with GitHub governing the parties’ rights and obligations with respect to the processing of such Personal Data by GitHub in connection with the Online Services. + +Subject to the above, if Customer intends to provide to GitHub Personal Data covered by FERPA, the parties agree and acknowledge that, for the purposes of this DPA, GitHub is a “school official” with “legitimate educational interests” in the Personal Data, as those terms have been defined under FERPA and its implementing regulations. Customer understands that GitHub may possess limited or no contact information for Customer’s students and students’ parents. Consequently, Customer will be responsible for obtaining any student or parental consent for any end user’s use of the Online Services that may be required by applicable law and to convey notification on behalf of GitHub to students (or, with respect to a student under 18 years of age and not in attendance at a postsecondary institution, to the student’s parent) of any judicial order or lawfully-issued subpoena requiring the disclosure of Personal Data in GitHub’s possession as may be required under applicable law. + +### CJIS Customer Agreement, HIPAA Business Associate, Biometric Data + +Except with GitHub’s prior, written and specific consent, Customer shall not provide to GitHub any Personal Data + +- relating to criminal convictions and offenses or Personal Data collected or otherwise processed by Customer subject to or in connection with FBI Criminal Justice Information Services or the related Security Policy. +- constituting protected health information governed by the privacy, security, and breach notification rules issued by the United States Department of Health and Human Services, Parts 160 and 164 of Title 45 of the Code of Federal Regulations, established pursuant to the Health Insurance Portability and Accountability Act of 1996 (Public Law 104-191) or by state health or medical privacy laws. +- collected as part of a clinical trial or other biomedical research study subject to, or conducted in accordance with, the Federal Policy for the Protection of Human Subjects (Common Rule). +- covered by state, federal or foreign biometric privacy laws or otherwise constituting biometric information including information on an individual’s physical, physiological, biological or behavioral characteristics or information derived from such information that is used or intended to be used, singly or in combination with each other or with other information, to establish individual identity. + +### California Consumer Privacy Act (CCPA) / California Privacy Rights Act (CPRA) + +If and to the extent GitHub is processing Personal Data on behalf and in accordance with the documented instructions of Customer within the scope of the CCPA, GitHub makes the following additional commitments to Customer. GitHub will process the Personal Data on behalf of Customer and will not + +- sell the Personal Data as the term “selling” is defined in the CCPA. - share, rent, release, disclose, disseminate, make available, transfer or otherwise communicate orally, in writing or by electronic or other means, the Personal Data to a third party for cross-context behavioral advertising, whether or not for monetary or other valuable consideration, including transactions for cross-context behavioral advertising in which no money is exchanged. +- retain, use or disclose the Personal Data for any purpose other than for the business purposes specified in the DPA Terms and the GitHub Customer Agreement, including retaining, using or disclosing the Personal Data for a commercial purpose other than the business purposes specified in the DPA Terms or the GitHub Customer Agreement, or as otherwise permitted by the CCPA. +- retain, use or disclose the Personal Data outside of the direct business relationship with Customer. +- combine the Personal Data with personal information that it receives from or on behalf of a third party or collects from California residents, except that GitHub may combine Personal Data to perform any business purpose as permitted by the CCPA or any regulations adopted or issued under the CCPA. + +### How to Contact GitHub + +If Customer believes that GitHub is not adhering to its privacy or security commitments, Customer may contact customer support or use GitHub’s Privacy web form, located at https://support.github.com/contact/privacy. GitHub’s mailing address is: + +**GitHub Privacy**
GitHub, Inc.
88 Colin P. Kelly Jr. Street
San Francisco, California 94107 USA
+ +GitHub B.V. is GitHub’s data protection representative for the European Economic Area. The privacy representative of GitHub B.V. can be reached at the following address: + +**GitHub B.V.**
Vijzelstraat 68-72
1017 HL Amsterdam
The Netherlands
+ +

Appendix A – Security Safeguards

+ +GitHub has implemented and will maintain for Customer Data and Personal Data processed by GitHub on behalf and in accordance with the documented instructions of Customer in connection with GitHub services the following technical and organizational measures and security safeguards, which in conjunction with the security commitments in this DPA (including the GDPR Related Terms), are GitHub’s only responsibility with respect to the security of that data: + +| Domain | Practices | +| ---------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Organization of Information Security | **Security Ownership**. GitHub has appointed one or more security officers responsible for coordinating and monitoring the security policies and procedures.

**Security Roles and Responsibilities**. GitHub personnel with access to Customer Data and Personal Data are subject to confidentiality obligations.

**Risk Management Program**. GitHub performs an annual risk assessment.
GitHub retains its security documents pursuant to its retention requirements after they are no longer in effect.

**Vendor Management**. GitHub has a vendor risk assessment process, vendor contract clauses and additional data protection agreements with vendors. | +| Asset Management | **Asset Inventory**. GitHub maintains an inventory of all media on which Customer Data and Personal Data is stored. Access to the inventories of such media is restricted to GitHub personnel authorized to have such access.

**Asset Handling**
- GitHub classifies Customer Data and Personal Data to help identify it and to allow for access to it to be appropriately restricted.
- GitHub communicates employee responsibility and accountability for data protection up to and including cause for termination.
GitHub personnel must obtain GitHub authorization prior to remotely accessing Customer Data and Personal Data or processing Customer Data and Personal Data outside GitHub’s facilities. | +| Human Resources Security | **Security Training**. GitHub requires all new hires to complete security and privacy awareness training as part of initial on-boarding. Participation in annual training is required for all employees to provide a baseline for security and privacy basics. | +| Physical and Environmental Security | **Physical Access to Facilities**. GitHub limits access to facilities where information systems that process Customer Data and Personal Data are located to identified authorized individuals.

**Physical Access to Components**. GitHub maintains records of the incoming and outgoing media containing Customer Data, including the kind of media, the authorized sender/recipients, date and time, the number of media and the types of Customer Data and Personal Data they contain.

**Protection from Disruptions**. GitHub uses a variety of industry standard systems to protect against loss of data due to power supply failure or line interference.

**Component Disposal**. GitHub uses industry standard processes to delete Customer Data and Personal Data when it is no longer needed. | +| Communications and Operations Management | **Operational Policy**. GitHub maintains security documents describing its security measures and the relevant procedures and responsibilities of its personnel who have access to Customer Data.

**Data Recovery Procedures**
- On an ongoing basis, but in no case less frequently than once a week (unless no Customer Data and Personal Data has been updated during that period), GitHub maintains multiple copies of Customer Data and Personal Data from which Customer Data and Personal Data can be recovered.
- GitHub stores copies of Customer Data and Personal Data and data recovery procedures in a different place from where the primary computer equipment processing the Customer Data and Personal Data is located.
- GitHub has specific procedures in place governing access to copies of Customer Data.
- GitHub logs data restoration efforts, including the person responsible, the description of the restored data and where applicable, the person responsible and which data (if any) had to be input manually in the data recovery process.

**Malicious Software**. GitHub has threat detection controls to help identify and respond to anomalous or suspicious access to Customer Data, including malicious software originating from public networks.

**Data Beyond Boundaries**
- GitHub encrypts, or enables Customer to encrypt, Customer Data and Personal Data that is transmitted over public networks.
- GitHub restricts access to Customer Data and Personal Data in media leaving its facilities.

**Event Logging**. GitHub logs, or enables Customer to log, access and use of information systems containing Customer Data, registering the access ID, time, authorization granted or denied, and relevant activity. | +| Access Control | **Access Policy**. GitHub maintains a record of security privileges of individuals having access to Customer Data.

**Access Authorization**
- GitHub maintains and updates a record of personnel authorized to access GitHub systems that contain Customer Data.
- GitHub identifies those personnel who may grant, alter or cancel authorized access to data and resources.
- GitHub ensures that where more than one individual has access to systems containing Customer Data, the individuals have separate identifiers/log-ins where technically and architecturally feasible, and commercially reasonable.

**Least Privilege**
- Technical support personnel are only permitted to have access to Customer Data and Personal Data when needed.
- GitHub restricts access to Customer Data and Personal Data to only those individuals who require such access to perform their job function. GitHub employees are only granted access to production systems based on their role within the organization.

**Integrity and Confidentiality**

- GitHub instructs GitHub personnel to disable administrative sessions when computers are left unattended.
- GitHub stores passwords such that they are encrypted or unintelligible while they are in force.

**Authentication**
- GitHub uses industry standard practices to identify and authenticate users who attempt to access information systems.
- Where authentication mechanisms are based solely on passwords, GitHub requires the password to be at least eight characters long.
- GitHub ensures that de-activated or expired employee identifiers are not granted to other individuals.
- GitHub monitors, or enables Customer to monitor, repeated attempts to gain access to the information system using an invalid password.
- GitHub maintains industry standard procedures to deactivate passwords that have been corrupted or inadvertently disclosed.
- GitHub uses industry standard password protection practices, including practices designed to maintain the confidentiality and integrity of passwords when they are assigned and distributed, and during storage.

**Network Design**. GitHub has controls to ensure no systems storing Customer Data and Personal Data are part of the same logical network used for GitHub business operations. | +| Information Security Incident Management | **Incident Response Process**
- GitHub maintains a record of security incidents with a description of the incidents, the time period, the consequences of the breach, the name of the reporter, and to whom the incident was reported, and details regarding the handling of the incident.
- In the event that GitHub Security confirms or reasonably suspects that a GitHub.com customer is affected by a data breach, we will notify the customer without undue delay
- GitHub tracks, or enables Customer to track, disclosures of Customer Data, including what data has been disclosed, to whom, and at what time.

**Service Monitoring**. GitHub employs a wide range of continuous monitoring solutions for preventing, detecting, and mitigating attacks to the site. | +| Business Continuity Management | - GitHub maintains emergency and contingency plans for the facilities in which GitHub information systems that process Customer Data and Personal Data are located.
- GitHub’s redundant storage and its procedures for recovering data are designed to attempt to reconstruct Customer Data and Personal Data in its original or last-replicated state from before the time it was lost or destroyed. | + +

Attachment 1 - The Standard Contractual Clauses (EU/EEA)

+ +### Controller to Processor + +#### SECTION I + +##### Clause 1 + +**Purpose and scope** + +
    +
  1. The purpose of these standard contractual clauses is to ensure compliance with the requirements of Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data (General Data Protection Regulation) for the transfer of personal data to a third country.
    2. +
  2. The Parties: +
      +
    1. the natural or legal person(s), public authority/ies, agency/ies or other body/ies (hereinafter ‘entity/ies’) transferring the personal data, as listed in Annex I.A (hereinafter each ‘data exporter’), and
      2. +
    2. the entity/ies in a third country receiving the personal data from the data exporter, directly or indirectly via another entity also Party to these Clauses, as listed in Annex I.A (hereinafter each ‘data importer’)
      3. +
    + have agreed to these standard contractual clauses (hereinafter: ‘Clauses’).
    3. +
  3. These Clauses apply with respect to the transfer of personal data as specified in Annex I.B.
    4. +
  4. The Appendix to these Clauses containing the Annexes referred to therein forms an integral part of these Clauses.
    5. +
+ +##### Clause 2 + +**Effect and invariability of the Clauses** +
    +
  1. These Clauses set out appropriate safeguards, including enforceable data subject rights and effective legal remedies, pursuant to Article 46(1) and Article 46(2)(c) of Regulation (EU) 2016/679 and, with respect to data transfers from controllers to processors and/or processors to processors, standard contractual clauses pursuant to Article 28(7) of Regulation (EU) 2016/679, provided they are not modified, except to select the appropriate Module(s) or to add or update information in the Appendix. This does not prevent the Parties from including the standard contractual clauses laid down in these Clauses in a wider contract and/or to add other clauses or additional safeguards, provided that they do not contradict, directly or indirectly, these Clauses or prejudice the fundamental rights or freedoms of data subjects.
    2. +
  2. These Clauses are without prejudice to obligations to which the data exporter is subject by virtue of Regulation (EU) 2016/679.
    3. +
+ +##### Clause 3 + +**Third-party beneficiaries** + +
    +
  1. Data subjects may invoke and enforce these Clauses, as third-party beneficiaries, against the data exporter and/or data importer, with the following exceptions:
    2. +
      +
    1. Clause 1, Clause 2, Clause 3, Clause 6, Clause 7;
      2. +
    2. Clause 8.1(b), 8.9(a), (c), (d) and (e);
      3. +
    3. Clause 9(a), (c), (d) and (e);
      4. +
    4. Clause 12(a), (d) and (f);
      5. +
    5. Clause 13;
      6. +
    6. Clause 15.1(c), (d) and (e);
      7. +
    7. Clause 16(e);
      8. +
    8. Clause 18(a) and (b).
      9. +
    +
  2. Paragraph (a) is without prejudice to rights of data subjects under Regulation (EU) 2016/679.
    3. +
+ +##### Clause 4 + +**Interpretation** + +
    +
  1. Where these Clauses use terms that are defined in Regulation (EU) 2016/679, those terms shall have the same meaning as in that Regulation.
    2. +
  2. These Clauses shall be read and interpreted in the light of the provisions of Regulation (EU) 2016/679.
    3. +
  3. These Clauses shall not be interpreted in a way that conflicts with rights and obligations provided for in Regulation (EU) 2016/679.
    4. +
+ +##### Clause 5 + +**Hierarchy** + +In the event of a contradiction between these Clauses and the provisions of related agreements between the Parties, existing at the time these Clauses are agreed or entered into thereafter, these Clauses shall prevail. + +##### Clause 6 + +**Description of the transfer(s)** + +The details of the transfer(s), and in particular the categories of personal data that are transferred and the purpose(s) for which they are transferred, are specified in Annex I.B. + +##### Clause 7 + +**Docking clause** + +
    +
  1. An entity that is not a Party to these Clauses may, with the agreement of the Parties, accede to these Clauses at any time, either as a data exporter or as a data importer, by completing the Appendix and signing Annex I.A.
    2. +
  2. Once it has completed the Appendix and signed Annex I.A, the acceding entity shall become a Party to these Clauses and have the rights and obligations of a data exporter or data importer in accordance with its designation in Annex I.A.
    3. +
  3. The acceding entity shall have no rights or obligations arising under these Clauses from the period prior to becoming a Party.
    4. +
+ +#### SECTION II – OBLIGATIONS OF THE PARTIES + +##### Clause 8 + +**Data protection safeguards** + +The data exporter warrants that it has used reasonable efforts to determine that the data importer is able, through the implementation of appropriate technical and organisational measures, to satisfy its obligations under these Clauses. + +**8.1 Instructions**
    +
  1. The data importer shall process the personal data only on documented instructions from the data exporter. The data exporter may give such instructions throughout the duration of the contract.
    2. +
  2. The data importer shall immediately inform the data exporter if it is unable to follow those instructions.
    3. +
+ +**8.2 Purpose limitation** + +The data importer shall process the personal data only for the specific purpose(s) of the transfer, as set out in Annex I.B, unless on further instructions from the data exporter. + +**8.3 Transparency** + +On request, the data exporter shall make a copy of these Clauses, including the Appendix as completed by the Parties, available to the data subject free of charge. To the extent necessary to protect business secrets or other confidential information, including the measures described in Annex II and personal data, the data exporter may redact part of the text of the Appendix to these Clauses prior to sharing a copy, but shall provide a meaningful summary where the data subject would otherwise not be able to understand the its content or exercise his/her rights. On request, the Parties shall provide the data subject with the reasons for the redactions, to the extent possible without revealing the redacted information. This Clause is without prejudice to the obligations of the data exporter under Articles 13 and 14 of Regulation (EU) 2016/679. + +**8.4 Accuracy** + +If the data importer becomes aware that the personal data it has received is inaccurate, or has become outdated, it shall inform the data exporter without undue delay. In this case, the data importer shall cooperate with the data exporter to erase or rectify the data. + +**8.5 Duration of processing and erasure or return of data** + +Processing by the data importer shall only take place for the duration specified in Annex I.B. After the end of the provision of the processing services, the data importer shall, at the choice of the data exporter, delete all personal data processed on behalf of the data exporter and certify to the data exporter that it has done so, or return to the data exporter all personal data processed on its behalf and delete existing copies. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit return or deletion of the personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process it to the extent and for as long as required under that local law. This is without prejudice to Clause 14, in particular the requirement for the data importer under Clause 14(e) to notify the data exporter throughout the duration of the contract if it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under Clause 14(a). + +**8.6 Security of processing** + +
    +
  1. The data importer and, during transmission, also the data exporter shall implement appropriate technical and organisational measures to ensure the security of the data, including protection against a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access to that data (hereinafter ‘personal data breach’). In assessing the appropriate level of security, the Parties shall take due account of the state of the art, the costs of implementation, the nature, scope, context and purpose(s) of processing and the risks involved in the processing for the data subjects. The Parties shall in particular consider having recourse to encryption or pseudonymisation, including during transmission, where the purpose of processing can be fulfilled in that manner. In case of pseudonymisation, the additional information for attributing the personal data to a specific data subject shall, where possible, remain under the exclusive control of the data exporter. In complying with its obligations under this paragraph, the data importer shall at least implement the technical and organisational measures specified in Annex II. The data importer shall carry out regular checks to ensure that these measures continue to provide an appropriate level of security.
    2. +
  2. The data importer shall grant access to the personal data to members of its personnel only to the extent strictly necessary for the implementation, management and monitoring of the contract. It shall ensure that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.
    3. +
  3. In the event of a personal data breach concerning personal data processed by the data importer under these Clauses, the data importer shall take appropriate measures to address the breach, including measures to mitigate its adverse effects. The data importer shall also notify the data exporter without undue delay after having become aware of the breach. Such notification shall contain the details of a contact point where more information can be obtained, a description of the nature of the breach (including, where possible, categories and approximate number of data subjects and personal data records concerned), its likely consequences and the measures taken or proposed to address the breach including, where appropriate, measures to mitigate its possible adverse effects. Where, and in so far as, it is not possible to provide all information at the same time, the initial notification shall contain the information then available and further information shall, as it becomes available, subsequently be provided without undue delay.
    4. +
  4. The data importer shall cooperate with and assist the data exporter to enable the data exporter to comply with its obligations under Regulation (EU) 2016/679, in particular to notify the competent supervisory authority and the affected data subjects, taking into account the nature of processing and the information available to the data importer.
    5. +
+ +**8.7 Sensitive data** + +Where the transfer involves personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic data, or biometric data for the purpose of uniquely identifying a natural person, data concerning health or a person’s sex life or sexual orientation, or data relating to criminal convictions and offences (hereinafter ‘sensitive data’), the data importer shall apply the specific restrictions and/or additional safeguards described in Annex I.B. + +**8.8 Onward transfers** + +The data importer shall only disclose the personal data to a third party on documented instructions from the data exporter. In addition, the data may only be disclosed to a third party located outside the European Union (1) (in the same country as the data importer or in another third country, hereinafter ‘onward transfer’) if the third party is or agrees to be bound by these Clauses, under the appropriate Module, or if: + +
    +
  1. the onward transfer is to a country benefitting from an adequacy decision pursuant to Article 45 of Regulation (EU) 2016/679 that covers the onward transfer;
    2. +
  2. the third party otherwise ensures appropriate safeguards pursuant to Articles 46 or 47 Regulation of (EU) 2016/679 with respect to the processing in question;
    3. +
  3. the onward transfer is necessary for the establishment, exercise or defence of legal claims in the context of specific administrative, regulatory or judicial proceedings; or
    4. +
  4. the onward transfer is necessary in order to protect the vital interests of the data subject or of another natural person.

    5. + Any onward transfer is subject to compliance by the data importer with all the other safeguards under these Clauses, in particular purpose limitation. +
+ +**8.9 Documentation and compliance** + +
    +
  1. The data importer shall promptly and adequately deal with enquiries from the data exporter that relate to the processing under these Clauses.
    2. +
  2. The Parties shall be able to demonstrate compliance with these Clauses. In particular, the data importer shall keep appropriate documentation on the processing activities carried out on behalf of the data exporter.
    3. +
  3. The data importer shall make available to the data exporter all information necessary to demonstrate compliance with the obligations set out in these Clauses and at the data exporter’s request, allow for and contribute to audits of the processing activities covered by these Clauses, at reasonable intervals or if there are indications of non-compliance. In deciding on a review or audit, the data exporter may take into account relevant certifications held by the data importer.
    4. +
  4. The data exporter may choose to conduct the audit by itself or mandate an independent auditor. Audits may include inspections at the premises or physical facilities of the data importer and shall, where appropriate, be carried out with reasonable notice.
    5. +
  5. The Parties shall make the information referred to in paragraphs (b) and (c), including the results of any audits, available to the competent supervisory authority on request.
    6. +
+ +##### Clause 9 + +**Use of sub-processors** + +
    +
  1. GENERAL WRITTEN AUTHORISATION The data importer has the data exporter’s general authorisation for the engagement of sub-processor(s) from an agreed list. The data importer shall specifically inform the data exporter in writing of any intended changes to that list through the addition or replacement of sub-processors at least 90 days in advance, thereby giving the data exporter sufficient time to be able to object to such changes prior to the engagement of the sub-processor(s). The data importer shall provide the data exporter with the information necessary to enable the data exporter to exercise its right to object.
    2. +
  2. Where the data importer engages a sub-processor to carry out specific processing activities (on behalf of the data exporter), it shall do so by way of a written contract that provides for, in substance, the same data protection obligations as those binding the data importer under these Clauses, including in terms of third-party beneficiary rights for data subjects.(2) The Parties agree that, by complying with this Clause, the data importer fulfils its obligations under Clause 8.8. The data importer shall ensure that the sub-processor complies with the obligations to which the data importer is subject pursuant to these Clauses.
    3. +
  3. The data importer shall provide, at the data exporter’s request, a copy of such a sub-processor agreement and any subsequent amendments to the data exporter. To the extent necessary to protect business secrets or other confidential information, including personal data, the data importer may redact the text of the agreement prior to sharing a copy.
    4. +
  4. The data importer shall remain fully responsible to the data exporter for the performance of the sub-processor’s obligations under its contract with the data importer. The data importer shall notify the data exporter of any failure by the sub-processor to fulfil its obligations under that contract.
    5. +
  5. The data importer shall agree a third-party beneficiary clause with the sub-processor whereby – in the event the data importer has factually disappeared, ceased to exist in law or has become insolvent – the data exporter shall have the right to terminate the sub-processor contract and to instruct the sub-processor to erase or return the personal data.
    6. +
+ +##### Clause 10 + +**Data subject rights** + +
    +
  1. The data importer shall promptly notify the data exporter of any request it has received from a data subject. It shall not respond to that request itself unless it has been authorised to do so by the data exporter.
    2. +
  2. The data importer shall assist the data exporter in fulfilling its obligations to respond to data subjects’ requests for the exercise of their rights under Regulation (EU) 2016/679. In this regard, the Parties shall set out in Annex II the appropriate technical and organisational measures, taking into account the nature of the processing, by which the assistance shall be provided, as well as the scope and the extent of the assistance required.
    3. +
  3. In fulfilling its obligations under paragraphs (a) and (b), the data importer shall comply with the instructions from the data exporter.
    4. +
+ +##### Clause 11 + +**Redress** + +
    +
  1. The data importer shall inform data subjects in a transparent and easily accessible format, through individual notice or on its website, of a contact point authorised to handle complaints. It shall deal promptly with any complaints it receives from a data subject.
    2. +
  2. In case of a dispute between a data subject and one of the Parties as regards compliance with these Clauses, that Party shall use its best efforts to resolve the issue amicably in a timely fashion. The Parties shall keep each other informed about such disputes and, where appropriate, cooperate in resolving them.
    3. +
  3. Where the data subject invokes a third-party beneficiary right pursuant to Clause 3, the data importer shall accept the decision of the data subject to:
    4. +
      +
    1. lodge a complaint with the supervisory authority in the Member State of his/her habitual residence or place of work, or the competent supervisory authority pursuant to Clause 13;
      2. +
    2. refer the dispute to the competent courts within the meaning of Clause 18.
      3. +
    +
  4. The Parties accept that the data subject may be represented by a not-for-profit body, organisation or association under the conditions set out in Article 80(1) of Regulation (EU) 2016/679.
    5. +
  5. The data importer shall abide by a decision that is binding under the applicable EU or Member State law.
    6. +
  6. The data importer agrees that the choice made by the data subject will not prejudice his/her substantive and procedural rights to seek remedies in accordance with applicable laws.
    7. +
+ +##### Clause 12 + +**Liability** + +
    +
  1. Each Party shall be liable to the other Party/ies for any damages it causes the other Party/ies by any breach of these Clauses.
    2. +
  2. The data importer shall be liable to the data subject, and the data subject shall be entitled to receive compensation, for any material or non-material damages the data importer or its sub-processor causes the data subject by breaching the third-party beneficiary rights under these Clauses.
    3. +
  3. Notwithstanding paragraph (b), the data exporter shall be liable to the data subject, and the data subject shall be entitled to receive compensation, for any material or non-material damages the data exporter or the data importer (or its sub-processor) causes the data subject by breaching the third-party beneficiary rights under these Clauses. This is without prejudice to the liability of the data exporter and, where the data exporter is a processor acting on behalf of a controller, to the liability of the controller under Regulation (EU) 2016/679 or Regulation (EU) 2018/1725, as applicable.
    4. +
  4. The Parties agree that if the data exporter is held liable under paragraph (c) for damages caused by the data importer (or its sub-processor), it shall be entitled to claim back from the data importer that part of the compensation corresponding to the data importer’s responsibility for the damage.
    5. +
  5. Where more than one Party is responsible for any damage caused to the data subject as a result of a breach of these Clauses, all responsible Parties shall be jointly and severally liable and the data subject is entitled to bring an action in court against any of these Parties.
    6. +
  6. The Parties agree that if one Party is held liable under paragraph (e), it shall be entitled to claim back from the other Party/ies that part of the compensation corresponding to its/their responsibility for the damage.
    7. +
  7. The data importer may not invoke the conduct of a sub-processor to avoid its own liability.
    8. +
+ +##### Clause 13 + +**Supervision** + +
    +
  1. [Where the data exporter is established in an EU Member State:] The supervisory authority with responsibility for ensuring compliance by the data exporter with Regulation (EU) 2016/679 as regards the data transfer, as indicated in Annex I.C, shall act as competent supervisory authority.

    + [Where the data exporter is not established in an EU Member State, but falls within the territorial scope of application of Regulation (EU) 2016/679 in accordance with its Article 3(2) and has appointed a representative pursuant to Article 27(1) of Regulation (EU) 2016/679:] The supervisory authority of the Member State in which the representative within the meaning of Article 27(1) of Regulation (EU) 2016/679 is established, as indicated in Annex I.C, shall act as competent supervisory authority.

    + [Where the data exporter is not established in an EU Member State, but falls within the territorial scope of application of Regulation (EU) 2016/679 in accordance with its Article 3(2) without however having to appoint a representative pursuant to Article 27(2) of Regulation (EU) 2016/679:] The supervisory authority of one of the Member States in which the data subjects whose personal data is transferred under these Clauses in relation to the offering of goods or services to them, or whose behaviour is monitored, are located, as indicated in Annex I.C, shall act as competent supervisory authority.

    2. +
  2. The data importer agrees to submit itself to the jurisdiction of and cooperate with the competent supervisory authority in any procedures aimed at ensuring compliance with these Clauses. In particular, the data importer agrees to respond to enquiries, submit to audits and comply with the measures adopted by the supervisory authority, including remedial and compensatory measures. It shall provide the supervisory authority with written confirmation that the necessary actions have been taken.
    3. +
+ +#### SECTION III – LOCAL LAWS AND OBLIGATIONS IN CASE OF ACCESS BY PUBLIC AUTHORITIES + +##### Clause 14 + +**Local laws and practices affecting compliance with the Clauses** + +
    +
  1. The Parties warrant that they have no reason to believe that the laws and practices in the third country of destination applicable to the processing of the personal data by the data importer, including any requirements to disclose personal data or measures authorising access by public authorities, prevent the data importer from fulfilling its obligations under these Clauses. This is based on the understanding that laws and practices that respect the essence of the fundamental rights and freedoms and do not exceed what is necessary and proportionate in a democratic society to safeguard one of the objectives listed in Article 23(1) of Regulation (EU) 2016/679, are not in contradiction with these Clauses.
    2. +
  2. The Parties declare that in providing the warranty in paragraph (a), they have taken due account in particular of the following elements:
    3. +
      +
    1. the specific circumstances of the transfer, including the length of the processing chain, the number of actors involved and the transmission channels used; intended onward transfers; the type of recipient; the purpose of processing; the categories and format of the transferred personal data; the economic sector in which the transfer occurs; the storage location of the data transferred;
      2. +
    2. the laws and practices of the third country of destination– including those requiring the disclosure of data to public authorities or authorising access by such authorities – relevant in light of the specific circumstances of the transfer, and the applicable limitations and safeguards (3);
      3. +
    3. any relevant contractual, technical or organisational safeguards put in place to supplement the safeguards under these Clauses, including measures applied during transmission and to the processing of the personal data in the country of destination.
      4. +
    +
  3. The data importer warrants that, in carrying out the assessment under paragraph (b), it has made its best efforts to provide the data exporter with relevant information and agrees that it will continue to cooperate with the data exporter in ensuring compliance with these Clauses.
    4. +
  4. The Parties agree to document the assessment under paragraph (b) and make it available to the competent supervisory authority on request.
    5. +
  5. The data importer agrees to notify the data exporter promptly if, after having agreed to these Clauses and for the duration of the contract, it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under paragraph (a), including following a change in the laws of the third country or a measure (such as a disclosure request) indicating an application of such laws in practice that is not in line with the requirements in paragraph (a).
    6. +
  6. Following a notification pursuant to paragraph (e), or if the data exporter otherwise has reason to believe that the data importer can no longer fulfil its obligations under these Clauses, the data exporter shall promptly identify appropriate measures (e.g. technical or organisational measures to ensure security and confidentiality) to be adopted by the data exporter and/or data importer to address the situation. The data exporter shall suspend the data transfer if it considers that no appropriate safeguards for such transfer can be ensured, or if instructed by the competent supervisory authority to do so. In this case, the data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses. If the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise. Where the contract is terminated pursuant to this Clause, Clause 16(d) and (e) shall apply.
    7. +
+ +##### Clause 15 + +**Obligations of the data importer in case of access by public authorities** + +**15.1 Notification** + +
    +
  1. The data importer agrees to notify the data exporter and, where possible, the data subject promptly (if necessary with the help of the data exporter) if it:
    2. +
      +
    1. receives a legally binding request from a public authority, including judicial authorities, under the laws of the country of destination for the disclosure of personal data transferred pursuant to these Clauses; such notification shall include information about the personal data requested, the requesting authority, the legal basis for the request and the response provided; or
      2. +
    2. becomes aware of any direct access by public authorities to personal data transferred pursuant to these Clauses in accordance with the laws of the country of destination; such notification shall include all information available to the importer.
      3. +
    +
  2. If the data importer is prohibited from notifying the data exporter and/or the data subject under the laws of the country of destination, the data importer agrees to use its best efforts to obtain a waiver of the prohibition, with a view to communicating as much information as possible, as soon as possible. The data importer agrees to document its best efforts in order to be able to demonstrate them on request of the data exporter.
    3. +
  3. Where permissible under the laws of the country of destination, the data importer agrees to provide the data exporter, at regular intervals for the duration of the contract, with as much relevant information as possible on the requests received (in particular, number of requests, type of data requested, requesting authority/ies, whether requests have been challenged and the outcome of such challenges, etc.).
    4. +
  4. The data importer agrees to preserve the information pursuant to paragraphs (a) to (c) for the duration of the contract and make it available to the competent supervisory authority on request.
    5. +
  5. Paragraphs (a) to (c) are without prejudice to the obligation of the data importer pursuant to Clause 14(e) and Clause 16 to inform the data exporter promptly where it is unable to comply with these Clauses.
    6. +
+ +**15.2 Review of legality and data minimisation** + +
    +
  1. The data importer agrees to review the legality of the request for disclosure, in particular whether it remains within the powers granted to the requesting public authority, and to challenge the request if, after careful assessment, it concludes that there are reasonable grounds to consider that the request is unlawful under the laws of the country of destination, applicable obligations under international law and principles of international comity. The data importer shall, under the same conditions, pursue possibilities of appeal. When challenging a request, the data importer shall seek interim measures with a view to suspending the effects of the request until the competent judicial authority has decided on its merits. It shall not disclose the personal data requested until required to do so under the applicable procedural rules. These requirements are without prejudice to the obligations of the data importer under Clause 14(e).
    2. +
  2. The data importer agrees to document its legal assessment and any challenge to the request for disclosure and, to the extent permissible under the laws of the country of destination, make the documentation available to the data exporter. It shall also make it available to the competent supervisory authority on request.
    3. +
  3. The data importer agrees to provide the minimum amount of information permissible when responding to a request for disclosure, based on a reasonable interpretation of the request.
    4. +
+ +#### SECTION IV – FINAL PROVISIONS + +##### Clause 16 + +**Non-compliance with the Clauses and termination** + +
    +
  1. The data importer shall promptly inform the data exporter if it is unable to comply with these Clauses, for whatever reason.
    2. +
  2. In the event that the data importer is in breach of these Clauses or unable to comply with these Clauses, the data exporter shall suspend the transfer of personal data to the data importer until compliance is again ensured or the contract is terminated. This is without prejudice to Clause 14(f).
    3. +
  3. The data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses, where:
    4. +
      +
    1. the data exporter has suspended the transfer of personal data to the data importer pursuant to paragraph (b) and compliance with these Clauses is not restored within a reasonable time and in any event within one month of suspension;
      2. +
    2. the data importer is in substantial or persistent breach of these Clauses; or
      3. +
    3. the data importer fails to comply with a binding decision of a competent court or supervisory authority regarding its obligations under these Clauses.
      4. +

    + In these cases, it shall inform the competent supervisory authority of such non-compliance. Where the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise. +
  4. Personal data that has been transferred prior to the termination of the contract pursuant to paragraph (c) shall at the choice of the data exporter immediately be returned to the data exporter or deleted in its entirety. The same shall apply to any copies of the data. The data importer shall certify the deletion of the data to the data exporter. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit the return or deletion of the transferred personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process the data to the extent and for as long as required under that local law.
    5. +
  5. Either Party may revoke its agreement to be bound by these Clauses where (i) the European Commission adopts a decision pursuant to Article 45(3) of Regulation (EU) 2016/679 that covers the transfer of personal data to which these Clauses apply; or (ii) Regulation (EU) 2016/679 becomes part of the legal framework of the country to which the personal data is transferred. This is without prejudice to other obligations applying to the processing in question under Regulation (EU) 2016/679.
    6. +
+ +##### Clause 17 + +**Governing law** + +These Clauses shall be governed by the law of one of the EU Member States, provided such law allows for third-party beneficiary rights. The Parties agree that this shall be the law of the Netherlands. + +##### Clause 18 + +**Choice of forum and jurisdiction** + +
    +
  1. Any dispute arising from these Clauses shall be resolved by the courts of an EU Member State.
    2. +
  2. The Parties agree that those shall be the courts of the Netherlands.
    3. +
  3. A data subject may also bring legal proceedings against the data exporter and/or data importer before the courts of the Member State in which he/she has his/her habitual residence.
    4. +
  4. The Parties agree to submit themselves to the jurisdiction of such courts.
    5. +
+ +## ANNEX I + +**to the Standard Contractual Clauses (EU/EEA)** + +### A. LIST OF PARTIES + +**Data exporter(s)**: Customer is the data exporter
Name: see GitHub Customer Agreement
Address: see GitHub Customer Agreement
Contact person’s name, position and contact details: see GitHub Customer Agreement
Activities relevant to the data transferred under these Clauses:
The data exporter is a user of Online Services or Professional Services as defined in the DPA and GitHub Customer Agreement.
Signature and date: see GitHub Customer Agreement (the DPA and the Standard Contractual Clauses (EU/EEA) are incorporated into the GitHub Customer Agreement
Role (controller/processor): controller (unless otherwise agreed in the Customer Agreement).
+ +**Data importer(s)**:
Name: GitHub, Inc.
Address: 88 Colin P Kelly Jr St, San Francisco, CA 94107, USA
Contact person’s name, position and contact details: Frances Wiet, Head of Privacy, fwiet@github.com
Activities relevant to the data transferred under these Clauses:
GitHub, Inc. is a global producer of software and services
Signature and date: see GitHub Customer Agreement (the DPA and the Standard Contractual Clauses (EU/EEA) are incorporated into the GitHub Customer Agreement)
Role (controller/processor): processor or, depending on the agreements set forth in the Customer Agreement, subprocessor. + +### B. DESCRIPTION OF TRANSFER + +_Categories of data subjects whose personal data is transferred:_ + +Data subjects include the data exporter’s representatives and end-users including employees, contractors, collaborators, and customers of the data exporter. Data subjects may also include individuals attempting to communicate or transfer personal data to users of the services provided by data importer. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following types of data subjects in the personal data: +- Employees, contractors and temporary workers (current, former, prospective) of data exporter; +- Data exporter's collaborators/contact persons (natural persons) or employees, contractors or temporary workers of legal entity collaborators/contact persons (current, prospective, former); +- Users and other data subjects that are users of data exporter's services; +- Partners, stakeholders or individuals who actively collaborate, communicate or otherwise interact with employees of the data exporter and/or use communication tools such as apps and websites provided by the data exporter. + +_Categories of personal data transferred:_ + +The personal data transferred that is included in e-mail, documents and other data in an electronic form in the context of the Online Services or Professional Services. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following categories in the personal data: +- Basic personal data (for example place of birth, street name and house number (address), postal code, city of residence, country of residence, mobile phone number, first name, last name, initials, email address, gender, date of birth); +- Authentication data (for example user name, password or PIN code, security question, audit trail); +- Contact information (for example addresses, email, phone numbers, social media identifiers; emergency contact details); +- Unique identification numbers and signatures (for example IP addresses, employee number, student number); +- Pseudonymous identifiers; +- Photos, video and audio; +- Internet activity (for example browsing history, search history, reading and viewing activities); +- Device identification (for example IMEI-number, SIM card number, MAC address); +- Profiling (for example based on observed criminal or anti-social behavior or pseudonymous profiles based on visited URLs, click streams, browsing logs, IP-addresses, domains, apps installed, or profiles based on marketing preferences); +- Special categories of data as voluntarily provided by data subjects (for example racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health, data concerning a natural person’s sex life or sexual orientation, or data relating to criminal convictions or offences); or +- Any other personal data identified in Article 4 of the GDPR. + +_**Sensitive data** transferred (if applicable) and applied restrictions or safeguards that fully take into consideration the nature of the data and the risks involved, such as for instance strict purpose limitation, access restrictions (including access only for staff having followed specialised training), keeping a record of access to the data, restrictions for onward transfers or additional security measures:_
GitHub does not request or otherwise ask for sensitive data and receives such data only if and when customers or data subjects decide to provide it. + +_**The frequency of the transfer** (e.g. whether the data is transferred on a one-off or continuous basis):_ + +Continuous as part of the Online Services or Professional Services. + +_**Nature of the processing:**_ + +The personal data transferred will be subject to the following basic processing activities: +
    +
  1. Duration and Object of Data Processing. The duration of data processing shall be for the term designated under the applicable GitHub Customer Agreement between data exporter and the data importer. The objective of the data processing is the performance of Online Services and Professional Services.
    2. +
  2. Personal Data Access. For the term designated under the applicable GitHub Customer Agreement, data importer will, at its election and as necessary under applicable law, either: (1) provide data exporter with the ability to correct, delete, or block personal data, or (2) make such corrections, deletions, or blockages on its behalf.
    3. +
  3. Data Exporter’s Instructions. For Online Services and Professional Services, data importer will only act upon data exporter’s instructions.
    4. +
+ +_Purpose(s) of the data transfer and further processing:_ + +The scope and purpose of processing personal data is described in the “Processing of Personal Data; GDPR” section of the DPA. The data importer operates a global network of data centers and management/support facilities, and processing may take place in any jurisdiction where data importer or its sub-processors operate such facilities in accordance with the “Security Practices and Policies” section of the DPA. + +_The period for which the personal data will be retained, or, if that is not possible, the criteria used to determine that period:_ + +Upon expiration or termination of data exporter’s use of Online Services or Professional Services, it may extract personal data and data importer will delete personal data, each in accordance with the DPA Terms applicable to the agreement. + +_For transfers to (sub-) processors, also specify subject matter, nature and duration of the processing:_ + +In accordance with the DPA, the data importer may hire other companies to provide limited services on data importer’s behalf, such as providing customer support. Any such subcontractors will be permitted to obtain personal data only to deliver the services the data importer has retained them to provide, and they are prohibited from using personal data for any other purpose. Unless a particular subcontractor is replaced ahead of time, the processing will be for the term designated under the applicable GitHub Customer Agreement between data exporter and data importer. + +### C. COMPETENT SUPERVISORY AUTHORITY + +_Identify the competent supervisory authority/ies in accordance with Clause 13:_ + +The supervisory authority with responsibility for ensuring compliance by the data exporter with Regulation (EU) 2016/679.   +## ANNEX II + +**to the Standard Contractual Clauses (EU/EEA)** + +**TECHNICAL AND ORGANISATIONAL MEASURES INCLUDING TECHNICAL AND ORGANISATIONAL MEASURES TO ENSURE THE SECURITY OF THE DATA** + +_Description of the technical and organisational measures implemented by the data importer(s) (including any relevant certifications) to ensure an appropriate level of security, taking into account the nature, scope, context and purpose of the processing, and the risks for the rights and freedoms of natural persons._ + +
    +
  1. Data Security Certifications. Data importer holds the following data security certifications:
    2. +
      +
    • SOC 1, Type 2;
      • +
    • SOC 2, Type 2;
      • +
    • NIST, to the extent incorporated for FedRAMP Low-Impact / Tailored ATO.
      • +
    +
  2. Personnel. Data importer’s personnel will not process personal data without authorization. Personnel are obligated to maintain the confidentiality of any such personal data and this obligation continues even after their engagement ends.
    3. +
  3. Data Privacy Contact. The data privacy officer of the data importer can be reached at the following address:

    + GitHub, Inc.
    + Attn: Privacy
    + 88 Colin P. Kelly Jr. Street
    + San Francisco, California 94107 USA

    4. +
  4. Technical and Organization Measures. The data importer has implemented and will maintain appropriate technical and organizational measures, internal controls, and information security routines intended to protect personal data, as defined in the Security Practices and Policies section of the DPA, against accidental loss, destruction, or alteration; unauthorized disclosure or access; or unlawful destruction as follows: The technical and organizational measures, internal controls, and information security routines set forth in the Data Security section of the DPA are hereby incorporated into this Annex II to Attachment 1 by this reference and are binding on the data importer as if they were set forth in this Annex 2 to Attachment 1 in their entirety.
    5. +
+ +_For transfers to (sub-) processors, also describe the specific technical and organisational measures to be taken by the (sub-) processor to be able to provide assistance to the controller and, for transfers from a processor to a sub-processor, to the data exporter:_ + +**Vendor management program - third-party risk program** + +The data importer has a vendor risk assessment process, vendor contract clauses and additional data protection agreements with vendors. Vendors undergo reassessment when a new business use case is requested. The data importer’s vendor risk program is structured so all of data importer’s vendors' risk assessments are refreshed two years from the last review date. + +Vendors deemed high risk, such as data center providers or other vendors storing or processing data in scope for the data importer’s regulatory or contractual requirements, undergo reassessment annually. + +## ANNEX III + +**to the Standard Contractual Clauses (EU/EEA)** + +**Additional Safeguards Addendum** + +By this Additional Safeguards Addendum to Standard Contractual Clauses (EU/EEA) (this “Addendum”), GitHub, Inc. (“GitHub”) provides additional safeguards to Customer and additional redress to the data subjects to whom Customer’s personal data relates. + +This Addendum supplements and is made part of, but is not in variation or modification of, the Standard Contractual Clauses (EU/EEA). + +
    +
  1. Challenges to Orders. In addition to Clause 15.1 of the Standard Contractual Clauses (EU/EEA), in the event GitHub receives an order from any third party for compelled disclosure of any personal data that has been transferred under the Standard Contractual Clauses (EU/EEA), GitHub shall:
    2. +
      +
    1. use every reasonable effort to redirect the third party to request data directly from Customer;
      2. +
    2. promptly notify Customer, unless prohibited under the law applicable to the requesting third party, and, if prohibited from notifying Customer, use all lawful efforts to obtain the right to waive the prohibition in order to communicate as much information to Customer as soon as possible; and
      3. +
    3. use all lawful efforts to challenge the order for disclosure on the basis of any legal deficiencies under the laws of the requesting party or any relevant conflicts with the law of the European Union or applicable Member State law.
      4. +

    + For purpose of this section, lawful efforts do not include actions that would result in civil or criminal penalty such as contempt of court under the laws of the relevant jurisdiction. +
  2. Indemnification of Data Subjects. Subject to Sections 3 and 4, GitHub shall indemnify a data subject for any material or non-material damage to the data subject caused by GitHub’s disclosure of personal data of the data subject that has been transferred under the Standard Contractual Clauses (EU/EEA) in response to an order from a non-EU/EEA government body or law enforcement agency (a “Relevant Disclosure”). Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under this Section 2 to the extent the data subject has already received compensation for the same damage, whether from GitHub or otherwise.
    3. +
  3. Conditions of Indemnification. Indemnification under Section 2 is conditional upon the data subject establishing, to GitHub’s reasonable satisfaction, that:
    4. +
      +
    1. GitHub engaged in a Relevant Disclosure;
      2. +
    2. the Relevant Disclosure was the basis of an official proceeding by the non-EU/EEA government body or law enforcement agency against the data subject; and
      3. +
    3. the Relevant Disclosure directly caused the data subject to suffer material or non-material damage.
      4. +

    + The data subject bears the burden of proof with respect to conditions a. though c.
    + Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under Section 2 if GitHub establishes that the Relevant Disclosure did not violate its obligations under Chapter V of the GDPR.
    +
  4. Scope of Damages. Indemnification under Section 2 is limited to material and non-material damages as provided in the GDPR and excludes consequential damages and all other damages not resulting from GitHub’s infringement of the GDPR.
    5. +
  5. Exercise of Rights. Rights granted to data subjects under this Addendum may be enforced by the data subject against GitHub irrespective of any restriction in Clauses 3 or 12 of the Standard Contractual Clauses (EU/EEA). The data subject may only bring a claim under this Addendum on an individual basis, and not part of a class, collective, group or representative action. Rights granted to data subjects under this Addendum are personal to the data subject and may not be assigned.
    6. +
  6. Notice of Change. In addition to Clause 14 of the Standard Contractual Clauses (EU/EEA), GitHub agrees and warrants that it has no reason to believe that the legislation applicable to it or its sub-processors, including in any country to which personal data is transferred either by itself or through a sub-processor, prevents it from fulfilling the instructions received from the data exporter and its obligations under this Addendum or the Standard Contractual Clauses (EU/EEA) and that in the event of a change in this legislation which is likely to have a substantial adverse effect on the warranties and obligations provided by this Addendum or the Standard Contractual Clauses (EU/EEA), it will promptly notify the change to Customer as soon as it is aware, in which case Customer is entitled to suspend the transfer of data and/or terminate the contract.
    7. +
  7. Termination. This Addendum shall automatically terminate if the European Commission, a competent Member State supervisory authority, or an EU or competent Member State court approves a different lawful transfer mechanism that would be applicable to the data transfers covered by the Standard Contractual Clauses (EU/EEA) (and if such mechanism applies only to some of the data transfers, this Addendum will terminate only with respect to those transfers) and that does not require the additional safeguards set forth in this Addendum.
    8. +
+ +

Attachment 2 – The Standard Contractual Clauses (UK)

+ +Execution of the GitHub Customer Agreement by Customer includes execution of this Attachment 2, which is countersigned by GitHub, Inc. + +In countries where regulatory approval is required for use of the Standard Contractual Clauses, the Standard Contractual Clauses cannot be relied upon under European Commission 2010/87/EU (of February 2010) to legitimize export of data from the country, unless Customer has the required regulatory approval. + +Beginning May 25, 2018 and thereafter, references to various Articles from the Directive 95/46/EC in the Standard Contractual Clauses below will be treated as references to the relevant and appropriate Articles in the GDPR. + +For the purposes of Article 26(2) of Directive 95/46/EC for the transfer of personal data to processors established in third countries which do not ensure an adequate level of data protection, Customer (as data exporter) and GitHub, Inc. (as data importer, whose signature appears below), each a “party,” together “the parties,” have agreed on the following Contractual Clauses (the “Clauses” or “Standard Contractual Clauses”) in order to adduce adequate safeguards with respect to the protection of privacy and fundamental rights and freedoms of individuals for the transfer by the data exporter to the data importer of the personal data specified in Appendix 1. + +### Clause 1: Definitions + +
    +
  1. 'personal data', 'special categories of data', 'process/processing', 'controller', 'processor', 'data subject' and 'supervisory authority' shall have the same meaning as in Directive 95/46/EC of the European Parliament and of the Council of 24 October 1995 on the protection of individuals with regard to the processing of personal data and on the free movement of such data;
    2. +
  2. 'the data exporter' means the controller who transfers the personal data;
    3. +
  3. 'the data importer' means the processor who agrees to receive from the data exporter personal data intended for processing on his behalf after the transfer in accordance with his instructions and the terms of the Clauses and who is not subject to a third country's system ensuring adequate protection within the meaning of Article 25(1) of Directive 95/46/EC;
    4. +
  4. 'the subprocessor' means any processor engaged by the data importer or by any other subprocessor of the data importer who agrees to receive from the data importer or from any other subprocessor of the data importer personal data exclusively intended for processing activities to be carried out on behalf of the data exporter after the transfer in accordance with his instructions, the terms of the Clauses and the terms of the written subcontract;
    5. +
  5. 'the applicable data protection law' means the legislation protecting the fundamental rights and freedoms of individuals and, in particular, their right to privacy with respect to the processing of personal data applicable to a data controller in the Member State in which the data exporter is established;
    6. +
  6. 'technical and organisational security measures' means those measures aimed at protecting personal data against accidental or unlawful destruction or accidental loss, alteration, unauthorised disclosure or access, in particular where the processing involves the transmission of data over a network, and against all other unlawful forms of processing.
    7. +
+ +### Clause 2: Details of the transfer + +The details of the transfer and in particular the special categories of personal data where applicable are specified in Appendix 1 below which forms an integral part of the Clauses. + +### Clause 3: Third-party beneficiary clause + +
    +
  1. The data subject can enforce against the data exporter this Clause, Clause 4(b) to (i), Clause 5(a) to (e), and (g) to (j), Clause 6(1) and (2), Clause 7, Clause 8(2), and Clauses 9 to 12 as third-party beneficiary.
    2. +
  2. The data subject can enforce against the data importer this Clause, Clause 5(a) to (e) and (g), Clause 6, Clause 7, Clause 8(2), and Clauses 9 to 12, in cases where the data exporter has factually disappeared or has ceased to exist in law unless any successor entity has assumed the entire legal obligations of the data exporter by contract or by operation of law, as a result of which it takes on the rights and obligations of the data exporter, in which case the data subject can enforce them against such entity.
    3. +
  3. The data subject can enforce against the subprocessor this Clause, Clause 5(a) to (e) and (g), Clause 6, Clause 7, Clause 8(2), and Clauses 9 to 12, in cases where both the data exporter and the data importer have factually disappeared or ceased to exist in law or have become insolvent, unless any successor entity has assumed the entire legal obligations of the data exporter by contract or by operation of law as a result of which it takes on the rights and obligations of the data exporter, in which case the data subject can enforce them against such entity. Such third-party liability of the subprocessor shall be limited to its own processing operations under the Clauses.
    4. +
  4. The parties do not object to a data subject being represented by an association or other body if the data subject so expressly wishes and if permitted by national law.
    5. +
+ +### Clause 4: Obligations of the data exporter + +The data exporter agrees and warrants: + +
    +
  1. that the processing, including the transfer itself, of the personal data has been and will continue to be carried out in accordance with the relevant provisions of the applicable data protection law (and, where applicable, has been notified to the relevant authorities of the Member State where the data exporter is established) and does not violate the relevant provisions of that State;
    2. +
  2. that it has instructed and throughout the duration of the personal data processing services will instruct the data importer to process the personal data transferred only on the data exporter's behalf and in accordance with the applicable data protection law and the Clauses;
    3. +
  3. that the data importer will provide sufficient guarantees in respect of the technical and organisational security measures specified in Appendix 2 below;
    4. +
  4. that after assessment of the requirements of the applicable data protection law, the security measures are appropriate to protect personal data against accidental or unlawful destruction or accidental loss, alteration, unauthorised disclosure or access, in particular where the processing involves the transmission of data over a network, and against all other unlawful forms of processing, and that these measures ensure a level of security appropriate to the risks presented by the processing and the nature of the data to be protected having regard to the state of the art and the cost of their implementation;
    5. +
  5. that it will ensure compliance with the security measures;
    6. +
  6. that, if the transfer involves special categories of data, the data subject has been informed or will be informed before, or as soon as possible after, the transfer that its data could be transmitted to a third country not providing adequate protection within the meaning of Directive 95/46/EC;
    7. +
  7. to forward any notification received from the data importer or any subprocessor pursuant to Clause 5(b) and Clause 8(3) to the data protection supervisory authority if the data exporter decides to continue the transfer or to lift the suspension;
    8. +
  8. to make available to the data subjects upon request a copy of the Clauses, with the exception of Appendix 2, and a summary description of the security measures, as well as a copy of any contract for subprocessing services which has to be made in accordance with the Clauses, unless the Clauses or the contract contain commercial information, in which case it may remove such commercial information;
    9. +
  9. that, in the event of subprocessing, the processing activity is carried out in accordance with Clause 11 by a subprocessor providing at least the same level of protection for the personal data and the rights of data subject as the data importer under the Clauses; and
    10. +
  10. that it will ensure compliance with Clause 4(a) to (i).
    11. +
+ +### Clause 5: Obligations of the data importer + +The data importer agrees and warrants: + +
    +
  1. to process the personal data only on behalf of the data exporter and in compliance with its instructions and the Clauses; if it cannot provide such compliance for whatever reasons, it agrees to inform promptly the data exporter of its inability to comply, in which case the data exporter is entitled to suspend the transfer of data and/or terminate the contract;
    2. +
  2. that it has no reason to believe that the legislation applicable to it prevents it from fulfilling the instructions received from the data exporter and its obligations under the contract and that in the event of a change in this legislation which is likely to have a substantial adverse effect on the warranties and obligations provided by the Clauses, it will promptly notify the change to the data exporter as soon as it is aware, in which case the data exporter is entitled to suspend the transfer of data and/or terminate the contract;
    3. +
  3. that it has implemented the technical and organisational security measures specified in Appendix 2 before processing the personal data transferred;
    4. +
  4. that it will promptly notify the data exporter about:
    5. +
      +
    1. any legally binding request for disclosure of the personal data by a law enforcement authority unless otherwise prohibited, such as a prohibition under criminal law to preserve the confidentiality of a law enforcement investigation,
      2. +
    2. any accidental or unauthorised access, and
      3. +
    3. any request received directly from the data subjects without responding to that request, unless it has been otherwise authorised to do so;
      4. +
    + to deal promptly and properly with all inquiries from the data exporter relating to its processing of the personal data subject to the transfer and to abide by the advice of the supervisory authority with regard to the processing of the data transferred; + at the request of the data exporter to submit its data processing facilities for audit of the processing activities covered by the Clauses which shall be carried out by the data exporter or an inspection body composed of independent members and in possession of the required professional qualifications bound by a duty of confidentiality, selected by the data exporter, where applicable, in agreement with the supervisory authority; +
  5. to make available to the data subject upon request a copy of the Clauses, or any existing contract for subprocessing, unless the Clauses or contract contain commercial information, in which case it may remove such commercial information, with the exception of Appendix 2 which shall be replaced by a summary description of the security measures in those cases where the data subject is unable to obtain a copy from the data exporter;
    6. +
  6. that, in the event of subprocessing, it has previously informed the data exporter and obtained its prior written consent;
    7. +
  7. that the processing services by the subprocessor will be carried out in accordance with Clause 11; and
    8. +
  8. to send promptly a copy of any subprocessor agreement it concludes under the Clauses to the data exporter.
    9. +
+ +### Clause 6: Liability + +
    +
  1. The parties agree that any data subject who has suffered damage as a result of any breach of the obligations referred to in Clause 3 or in Clause 11 by any party or subprocessor is entitled to receive compensation from the data exporter for the damage suffered.
    2. + +
  2. If a data subject is not able to bring a claim for compensation in accordance with paragraph 1 against the data exporter, arising out of a breach by the data importer or his subprocessor of any of their obligations referred to in Clause 3 or in Clause 11, because the data exporter has factually disappeared or ceased to exist in law or has become insolvent, the data importer agrees that the data subject may issue a claim against the data importer as if it were the data exporter, unless any successor entity has assumed the entire legal obligations of the data exporter by contract of by operation of law, in which case the data subject can enforce its rights against such entity.

    + The data importer may not rely on a breach by a subprocessor of its obligations in order to avoid its own liabilities.
    3. + +
  3. If a data subject is not able to bring a claim against the data exporter or the data importer referred to in paragraphs 1 and 2, arising out of a breach by the subprocessor of any of their obligations referred to in Clause 3 or in Clause 11 because both the data exporter and the data importer have factually disappeared or ceased to exist in law or have become insolvent, the subprocessor agrees that the data subject may issue a claim against the data subprocessor with regard to its own processing operations under the Clauses as if it were the data exporter or the data importer, unless any successor entity has assumed the entire legal obligations of the data exporter or data importer by contract or by operation of law, in which case the data subject can enforce its rights against such entity. The liability of the subprocessor shall be limited to its own processing operations under the Clauses.
    4. +
+ +### Clause 7: Mediation and jurisdiction + +
    +
  1. The data importer agrees that if the data subject invokes against it third-party beneficiary rights and/or claims compensation for damages under the Clauses, the data importer will accept the decision of the data subject: +
      +
    1. to refer the dispute to mediation, by an independent person or, where applicable, by the supervisory authority; +
    2. to refer the dispute to the courts in the Member State in which the data exporter is established. +
    +
  2. The parties agree that the choice made by the data subject will not prejudice its substantive or procedural rights to seek remedies in accordance with other provisions of national or international law. +
+ +### Clause 8: Cooperation with supervisory authorities + +
    +
  1. The data exporter agrees to deposit a copy of this contract with the supervisory authority if it so requests or if such deposit is required under the applicable data protection law.
    2. + +
  2. The parties agree that the supervisory authority has the right to conduct an audit of the data importer, and of any subprocessor, which has the same scope and is subject to the same conditions as would apply to an audit of the data exporter under the applicable data protection law.
    3. + +
  3. The data importer shall promptly inform the data exporter about the existence of legislation applicable to it or any subprocessor preventing the conduct of an audit of the data importer, or any subprocessor, pursuant to paragraph 2. In such a case the data exporter shall be entitled to take the measures foreseen in Clause 5 (b).
    4. +
+ +### Clause 9: Governing Law. + +The Clauses shall be governed by the law of the Member State in which the data exporter is established. + +### Clause 10: Variation of the contract + +The parties undertake not to vary or modify the Clauses. This does not preclude the parties from adding clauses on business related issues where required as long as they do not contradict the Clause. + +### Clause 11: Subprocessing + +
    +
  1. The data importer shall not subcontract any of its processing operations performed on behalf of the data exporter under the Clauses without the prior written consent of the data exporter. Where the data importer subcontracts its obligations under the Clauses, with the consent of the data exporter, it shall do so only by way of a written agreement with the subprocessor which imposes the same obligations on the subprocessor as are imposed on the data importer under the Clauses. Where the subprocessor fails to fulfil its data protection obligations under such written agreement the data importer shall remain fully liable to the data exporter for the performance of the subprocessor's obligations under such agreement.
    2. + +
  2. The prior written contract between the data importer and the subprocessor shall also provide for a third-party beneficiary clause as laid down in Clause 3 for cases where the data subject is not able to bring the claim for compensation referred to in paragraph 1 of Clause 6 against the data exporter or the data importer because they have factually disappeared or have ceased to exist in law or have become insolvent and no successor entity has assumed the entire legal obligations of the data exporter or data importer by contract or by operation of law. Such third-party liability of the subprocessor shall be limited to its own processing operations under the Clauses.
    3. + +
  3. The provisions relating to data protection aspects for subprocessing of the contract referred to in paragraph 1 shall be governed by the law of the Member State in which the data exporter is established.
    4. + +
  4. The data exporter shall keep a list of subprocessing agreements concluded under the Clauses and notified by the data importer pursuant to Clause 5 (j), which shall be updated at least once a year. The list shall be available to the data exporter's data protection supervisory authority.
    5. +
+ +### Clause 12: Obligation after the termination of personal data processing services + +
    +
  1. The parties agree that on the termination of the provision of data processing services, the data importer and the subprocessor shall, at the choice of the data exporter, return all the personal data transferred and the copies thereof to the data exporter or shall destroy all the personal data and certify to the data exporter that it has done so, unless legislation imposed upon the data importer prevents it from returning or destroying all or part of the personal data transferred. In that case, the data importer warrants that it will guarantee the confidentiality of the personal data transferred and will not actively process the personal data transferred anymore.
    2. + +
  2. The data importer and the subprocessor warrant that upon request of the data exporter and/or of the supervisory authority, it will submit its data processing facilities for an audit of the measures referred to in paragraph 1.
    3. +
+ +### Appendix 1 to the Standard Contractual Clauses (UK) + +**Data exporter**: Customer is the data exporter. The data exporter is a user of Online Services or Professional Services as defined in the DPA and GitHub Customer Agreement. + +**Data importer**: The data importer is GitHub, Inc., a global producer of software and services. + +**Data subjects**: Data subjects include the data exporter’s representatives and end-users including employees, contractors, collaborators, and customers of the data exporter. Data subjects may also include individuals attempting to communicate or transfer personal data to users of the services provided by data importer. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following types of data subjects in the personal data: +- Employees, contractors and temporary workers (current, former, prospective) of data exporter; +- Data exporter's collaborators/contact persons (natural persons) or employees, contractors or temporary workers of legal entity collaborators/contact persons (current, prospective, former); +- Users and other data subjects that are users of data exporter's services; +- Partners, stakeholders or individuals who actively collaborate, communicate or otherwise interact with employees of the data exporter and/or use communication tools such as apps and websites provided by the data exporter. + +**Categories of data**: The personal data transferred that is included in e-mail, documents and other data in an electronic form in the context of the Online Services or Professional Services. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following categories in the personal data: +- Basic personal data (for example place of birth, street name and house number (address), postal code, city of residence, country of residence, mobile phone number, first name, last name, initials, email address, gender, date of birth); +- Authentication data (for example user name, password or PIN code, security question, audit trail); +- Contact information (for example addresses, email, phone numbers, social media identifiers; emergency contact details); +- Unique identification numbers and signatures (for example IP addresses, employee number, student number); +- Pseudonymous identifiers; +- Photos, video and audio; +- Internet activity (for example browsing history, search history, reading and viewing activities); +- Device identification (for example IMEI-number, SIM card number, MAC address); +- Profiling (for example based on observed criminal or anti-social behavior or pseudonymous profiles based on visited URLs, click streams, browsing logs, IP-addresses, domains, apps installed, or profiles based on marketing preferences); +- Special categories of data as voluntarily provided by data subjects (for example racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health, data concerning a natural person’s sex life or sexual orientation, or data relating to criminal convictions or offences); or +- Any other personal data identified in Article 4 of the GDPR. + +**Processing operations**: The personal data transferred will be subject to the following basic processing activities: + +
    +
  1. Duration and Object of Data Processing. The duration of data processing shall be for the term designated under the applicable GitHub Customer Agreement between data exporter and data importer. The objective of the data processing is the performance of Online Services and Professional Services.
    2. +
  2. Scope and Purpose of Data Processing. The scope and purpose of processing personal data is described in the “Processing of Personal Data; GDPR” section of the DPA. The data importer operates a global network of data centers and management/support facilities, and processing may take place in any jurisdiction where data importer or its sub-processors operate such facilities in accordance with the “Security Practices and Policies” section of the DPA.
    3. +
  3. Personal Data Access. For the term designated under the applicable GitHub Customer Agreement data importer will at its election and as necessary under applicable law, either: (1) provide data exporter with the ability to correct, delete, or block personal data, or (2) make such corrections, deletions, or blockages on its behalf.
    4. +
  4. Data Exporter’s Instructions. For Online Services and Professional Services, data importer will only act upon data exporter’s instructions as conveyed by GitHub.
    5. +
  5. Personal Data Deletion or Return. Upon expiration or termination of data exporter’s use of Online Services or Professional Services, it may extract personal data and data importer will delete personal data, each in accordance with the DPA Terms applicable to the agreement.
    6. +
+ +**Subcontractors**: In accordance with the DPA, the data importer may hire other companies to provide limited services on data importer’s behalf, such as providing customer support. Any such subcontractors will be permitted to obtain personal data only to deliver the services the data importer has retained them to provide, and they are prohibited from using personal data for any other purpose. + +### Appendix 2 to the Standard Contractual Clauses (UK) + +Description of the technical and organizational security measures implemented by the data importer in accordance with Clauses 4(d) and 5(c): + +
    +
  1. Personnel. Data importer’s personnel will not process personal data without authorization. Personnel are obligated to maintain the confidentiality of any such personal data and this obligation continues even after their engagement ends.
    2. + +
  2. Data Privacy Contact. The data privacy officer of the data importer can be reached at the following address:
    +GitHub, Inc.
    +Attn: Privacy
    +88 Colin P. Kelly Jr. Street
    +San Francisco, California 94107 USA
    3. + +
  3. Technical and Organization Measures. The data importer has implemented and will maintain appropriate technical and organizational measures, internal controls, and information security routines intended to protect personal data, as defined in the Security Practices and Policies section of the DPA, against accidental loss, destruction, or alteration; unauthorized disclosure or access; or unlawful destruction as follows: The technical and organizational measures, internal controls, and information security routines set forth in the Security Practices and Policies section of the DPA are hereby incorporated into this Appendix 2 by this reference and are binding on the data importer as if they were set forth in this Appendix 2 in their entirety.
    4. +
+ +### Appendix 3 to the Standard Contractual Clauses (UK) + +**Additional Safeguards Addendum** + +By this Additional Safeguards Addendum to Standard Contractual Clauses (UK) (this “Addendum”), GitHub, Inc. (“GitHub”) provides additional safeguards to Customer and additional redress to the data subjects to whom Customer’s personal data relates. + +This Addendum supplements and is made part of, but is not in variation or modification of, the Standard Contractual Clauses (UK). + +
    +
  1. Challenges to Orders. In addition to Clause 5(d)(i) of the Standard Contractual Clauses (UK), in the event GitHub receives an order from any third party for compelled disclosure of any personal data that has been transferred under the Standard Contractual Clauses (UK), GitHub shall:
    2. +
      +
    1. use every reasonable effort to redirect the third party to request data directly from Customer;
      2. +
    2. promptly notify Customer, unless prohibited under the law applicable to the requesting third party, and, if prohibited from notifying Customer, use all lawful efforts to obtain the right to waive the prohibition in order to communicate as much information to Customer as soon as possible; and
      3. +
    3. use all lawful efforts to challenge the order for disclosure on the basis of any legal deficiencies under the laws of the requesting party or any relevant conflicts with the law of the European Union or applicable Member State law.
      4. +

    + For purpose of this section, lawful efforts do not include actions that would result in civil or criminal penalty such as contempt of court under the laws of the relevant jurisdiction. +
  2. Indemnification of Data Subjects. Subject to Sections 3 and 4, GitHub shall indemnify a data subject for any material or non-material damage to the data subject caused by GitHub’s disclosure of personal data of the data subject that has been transferred under the Standard Contractual Clauses (UK) in response to an order from a non-EU/EEA government body or law enforcement agency (a “Relevant Disclosure”). Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under this Section 2 to the extent the data subject has already received compensation for the same damage, whether from GitHub or otherwise.
    3. +
  3. Conditions of Indemnification. Indemnification under Section 2 is conditional upon the data subject establishing, to GitHub’s reasonable satisfaction, that:
    4. +
      +
    1. GitHub engaged in a Relevant Disclosure;
      2. +
    2. the Relevant Disclosure was the basis of an official proceeding by the non-EU/EEA government body or law enforcement agency against the data subject; and
      3. +
    3. the Relevant Disclosure directly caused the data subject to suffer material or non-material damage.
      4. +

    + The data subject bears the burden of proof with respect to conditions a. though c.
    + Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under Section 2 if GitHub establishes that the Relevant Disclosure did not violate its obligations under Chapter V of the GDPR. +
  4. Scope of Damages. Indemnification under Section 2 is limited to material and non-material damages as provided in the GDPR and excludes consequential damages and all other damages not resulting from GitHub’s infringement of the GDPR.
    5. +
  5. Exercise of Rights. Rights granted to data subjects under this Addendum may be enforced by the data subject against GitHub irrespective of any restriction in Clauses 3 or 6 of the Standard Contractual Clauses (UK). The data subject may only bring a claim under this Addendum on an individual basis, and not part of a class, collective, group or representative action. Rights granted to data subjects under this Addendum are personal to the data subject and may not be assigned.
    6. +
  6. Notice of Change. In addition to Clause 5(b) of the Standard Contractual Clauses (UK), GitHub agrees and warrants that it has no reason to believe that the legislation applicable to it or its sub-processors, including in any country to which personal data is transferred either by itself or through a sub-processor, prevents it from fulfilling the instructions received from the data exporter and its obligations under this Addendum or the Standard Contractual Clauses (UK) and that in the event of a change in this legislation which is likely to have a substantial adverse effect on the warranties and obligations provided by this Addendum or the Standard Contractual Clauses (UK), it will promptly notify the change to Customer as soon as it is aware, in which case Customer is entitled to suspend the transfer of data and/or terminate the contract. +
  7. Termination. This Addendum shall automatically terminate if the European Commission, a competent Member State supervisory authority, or an EU or competent Member State court approves a different lawful transfer mechanism that would be applicable to the data transfers covered by the Standard Contractual Clauses (UK) (and if such mechanism applies only to some of the data transfers, this Addendum will terminate only with respect to those transfers) and that does not require the additional safeguards set forth in this Addendum.

    + Signing the Standard Contractual Clauses (UK), Appendix 1, Appendix 2 and +
+ +

Attachment 3 – European Union General Data Protection Regulation Terms

+ +GitHub makes the commitments in these GDPR Related Terms, to all customers effective May 25, 2018. These commitments are binding upon GitHub with regard to Customer regardless of (1) the version of the GitHub Customer Agreement and DPA that is otherwise applicable to any given Online Services subscription or (2) any other agreement that references this attachment. + +For purposes of these GDPR Related Terms, Customer and GitHub agree that Customer is the controller of Personal Data and GitHub is the processor of such data, except when Customer acts as a processor of Personal Data, in which case GitHub is a subprocessor. These GDPR Related Terms apply to the processing of Personal Data, within the scope of the GDPR, by GitHub on behalf of Customer. These GDPR Related Terms do not limit or reduce any data protection commitments GitHub makes to Customer in the GitHub Customer Agreement or other agreement between GitHub and Customer. These GDPR Related Terms do not apply where GitHub is a controller of Personal Data. + +**Relevant GDPR Obligations: Articles 28, 32, and 33** + +
    +
  1. GitHub shall not engage another processor without prior specific or general written authorisation of Customer. In the case of general written authorisation, GitHub shall inform Customer of any intended changes concerning the addition or replacement of other processors, thereby giving Customer the opportunity to object to such changes. (Article 28(2))
    2. +
  2. Processing by GitHub shall be governed by these GDPR Related Terms under European Union (hereafter “Union”) or Member State law and are binding on GitHub with regard to Customer. The subject-matter and duration of the processing, the nature and purpose of the processing, the type of Personal Data, the categories of data subjects and the obligations and rights of the Customer are set forth in the Customer’s licensing agreement, including these GDPR Related Terms. In particular, GitHub shall:
    3. +
      +
    1. process the Personal Data only on documented instructions from Customer, including with regard to transfers of Personal Data to a third country or an international organisation, unless required to do so by Union or Member State law to which GitHub is subject; in such a case, GitHub shall inform Customer of that legal requirement before processing, unless that law prohibits such information on important grounds of public interest;
      2. +
    2. ensure that persons authorised to process the Personal Data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality;
      3. +
    3. take all measures required pursuant to Article 32 of the GDPR;
      4. +
    4. respect the conditions referred to in paragraphs 1 and 3 for engaging another processor;
      5. +
    5. taking into account the nature of the processing, assist Customer by appropriate technical and organisational measures, insofar as this is possible, for the fulfilment of the Customer’s obligation to respond to requests for exercising the data subject's rights laid down in Chapter III of the GDPR;
      6. +
    6. assist Customer in ensuring compliance with the obligations pursuant to Articles 32 to 36 of the GDPR, taking into account the nature of processing and the information available to GitHub;
      7. +
    7. at the choice of Customer, delete or return all the Personal Data to Customer after the end of the provision of services relating to processing, and delete existing copies unless Union or Member State law requires storage of the Personal Data;
      8. +
    8. make available to Customer all information necessary to demonstrate compliance with the obligations laid down in Article 28 of the GDPR and allow for and contribute to audits, including inspections, conducted by Customer or another auditor mandated by Customer.
      9. +

    + GitHub shall immediately inform Customer if, in its opinion, an instruction infringes the GDPR or other Union or Member State data protection provisions. (Article 28(3))

    +
  3. Where GitHub engages another processor for carrying out specific processing activities on behalf of Customer, the same data protection obligations as set out in these GDPR Related Terms shall be imposed on that other processor by way of a contract or other legal act under Union or Member State law, in particular providing sufficient guarantees to implement appropriate technical and organisational measures in such a manner that the processing will meet the requirements of the GDPR. Where that other processor fails to fulfil its data protection obligations, GitHub shall remain fully liable to the Customer for the performance of that other processor's obligations. (Article 28(4))
    4. +
  4. Taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of processing as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons, Customer and GitHub shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, including inter alia as appropriate:
    5. +
      +
    1. the pseudonymisation and encryption of Personal Data;
      2. +
    2. the ability to ensure the ongoing confidentiality, integrity, availability and resilience of processing systems and services;
      3. +
    3. the ability to restore the availability and access to Personal Data in a timely manner in the event of a physical or technical incident; and
      4. +
    4. a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the processing. (Article 32(1))
      5. +
    +
  5. In assessing the appropriate level of security, account shall be taken of the risks that are presented by processing, in particular from accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to Personal Data transmitted, stored or otherwise processed (Article 32(2)).
    6. +
  6. Customer and GitHub shall take steps to ensure that any natural person acting under the authority of Customer or GitHub who has access to Personal Data does not process them except on instructions from Customer, unless he or she is required to do so by Union or Member State law (Article 32(4)).
    7. +
  7. GitHub shall notify Customer without undue delay after becoming aware of a Personal Data breach (Article 33(2)). Such notification will include that information a processor must provide to a controller under Article 33(3) to the extent such information is reasonably available to GitHub.
    8. +
+ +--------------- + +

(1) The Agreement on the European Economic Area (EEA Agreement) provides for the extension of the European Union’s internal market to the three EEA States Iceland, Liechtenstein and Norway. The Union data protection legislation, including Regulation (EU) 2016/679, is covered by the EEA Agreement and has been incorporated into Annex XI thereto. Therefore, any disclosure by the data importer to a third party located in the EEA does not qualify as an onward transfer for the purpose of these Clauses.

+ +

(2) This requirement may be satisfied by the sub-processor acceding to these Clauses under the appropriate Module, in accordance with Clause 7.

+ +

(3) As regards the impact of such laws and practices on compliance with these Clauses, different elements may be considered as part of an overall assessment. Such elements may include relevant and documented practical experience with prior instances of requests for disclosure from public authorities, or the absence of such requests, covering a sufficiently representative time-frame. This refers in particular to internal records or other documentation, drawn up on a continuous basis in accordance with due diligence and certified at senior management level, provided that this information can be lawfully shared with third parties. Where this practical experience is relied upon to conclude that the data importer will not be prevented from complying with these Clauses, it needs to be supported by other relevant, objective elements, and it is for the Parties to consider carefully whether these elements together carry sufficient weight, in terms of their reliability and representativeness, to support this conclusion. In particular, the Parties have to take into account whether their practical experience is corroborated and not contradicted by publicly available or otherwise accessible, reliable information on the existence or absence of requests within the same sector and/or the application of the law in practice, such as case law and reports by independent oversight bodies.

diff --git a/translations/de-DE/content/github/site-policy/github-terms-for-additional-products-and-features.md b/translations/de-DE/content/github/site-policy/github-terms-for-additional-products-and-features.md index 8f1ea3c25f..1cc109eb55 100644 --- a/translations/de-DE/content/github/site-policy/github-terms-for-additional-products-and-features.md +++ b/translations/de-DE/content/github/site-policy/github-terms-for-additional-products-and-features.md @@ -20,7 +20,7 @@ By using the Additional Products and Features, you also agree to the applicable - **GitHub Enterprise Server** users may have access to the following Additional Products and Features: Actions, Advanced Security, Advisory Database, Connect, Dependabot Preview, Learning Lab, Octoshift, Packages, Pages and SQL Server Images. -- **GitHub AE** users may have access to the following Additional Products and Features: Actions, Advanced Security, Advisory Database, {% ifversion ghae-next %}Connect, {% endif %}Dependabot Preview, Octoshift, Packages and Pages. +- **GitHub AE** users may have access to the following Additional Products and Features: Actions, Advanced Security, Advisory Database,{% ifversion ghae-next %}Connect, {% endif %}Dependabot Preview, Octoshift, Packages and Pages. ## Actions GitHub Actions ermöglicht es Ihnen, benutzerdefinierte Softwareentwicklungs-Lebenszyklus-Workflows direkt in Ihrem GitHub Repository zu erstellen. Actions is billed on a usage basis. The [Actions documentation](/actions) includes details, including compute and storage quantities (depending on your Account plan), and how to monitor your Actions minutes usage and set usage limits. @@ -38,7 +38,7 @@ Um Verstöße gegen diese Einschränkungen und Missbrauch von GitHub Actions zu ## Advanced Security GitHub makes extra security features available to customers under an Advanced Security license. These features include code scanning, secret scanning, and dependency review. The [Advanced Security documentation](/github/getting-started-with-github/about-github-advanced-security) provides more details. -Advanced Security is licensed on a "Unique Committer" basis. A "Unique Committer" is a licensed user of GitHub Enterprise, GitHub Enterprise Cloud, GitHub Enterprise Server, or GitHub AE, who has made a code commit in the last 90 days to any repository with any GitHub Advanced Security functionality activated. You must acquire a GitHub Advanced Security User license for each of your Unique Committers. You may only use GitHub Advanced Security on codebases that are developed by or for you. For GitHub Enterprise Cloud users, some Advanced Security features also require the use of GitHub Actions. +Advanced Security is licensed on a "Unique Committer" basis. A "Unique Committer" is a licensed user of GitHub Enterprise, GitHub Enterprise Cloud, GitHub Enterprise Server, or GitHub AE, who has made a commit in the last 90 days to any repository with any GitHub Advanced Security functionality activated. You must acquire a GitHub Advanced Security User license for each of your Unique Committers. You may only use GitHub Advanced Security on codebases that are developed by or for you. For GitHub Enterprise Cloud users, some Advanced Security features also require the use of GitHub Actions. ## Advisory Database The GitHub Advisory Database allows you to browse or search for vulnerabilities that affect open source projects on GitHub. diff --git a/translations/de-DE/content/github/site-policy/index.md b/translations/de-DE/content/github/site-policy/index.md index a50045ce15..3ad45ec7a5 100644 --- a/translations/de-DE/content/github/site-policy/index.md +++ b/translations/de-DE/content/github/site-policy/index.md @@ -12,7 +12,7 @@ children: - /github-terms-of-service - /github-corporate-terms-of-service - /github-privacy-statement - - /github-data-protection-agreement-non-enterprise-customers + - /github-data-protection-agreement - /global-privacy-practices - /github-sponsors-additional-terms - /github-codespaces-privacy-statement diff --git a/translations/de-DE/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md b/translations/de-DE/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md index 1d6ef9b737..1026fbce8e 100644 --- a/translations/de-DE/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md +++ b/translations/de-DE/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md @@ -1,6 +1,7 @@ --- title: Gists erstellen intro: 'You can create two kinds of gists: {% ifversion ghae %}internal{% else %}public{% endif %} and secret. Create {% ifversion ghae %}an internal{% else %}a public{% endif %} gist if you''re ready to share your ideas with {% ifversion ghae %}enterprise members{% else %}the world{% endif %} or a secret gist if you''re not.' +permissions: '{% data reusables.enterprise-accounts.emu-permission-gist %}' redirect_from: - /articles/about-gists/ - /articles/cannot-delete-an-anonymous-gist/ @@ -42,7 +43,7 @@ Du kannst Gists an Deinem Profil anheften, damit andere Personen sie leichter se {% endif %} -You can discover {% ifversion ghae %}internal{% else %}public{% endif %} gists others have created by going to the {% data variables.gists.gist_homepage %} and clicking **All Gists**. Daraufhin wird eine Seite mit allen Gists angezeigt, die nach dem Zeitpunkt der Erstellung oder Aktualisierung sortiert sind. Mit der {% data variables.gists.gist_search_url %} können Sie Gists auch nach Sprache suchen. Die Gist-Suche nutzt dieselbe Suchsyntax wie [die Codesuche](/articles/searching-code). +You can discover {% ifversion ghae %}internal{% else %}public{% endif %} gists others have created by going to the {% data variables.gists.gist_homepage %} and clicking **All Gists**. Daraufhin wird eine Seite mit allen Gists angezeigt, die nach dem Zeitpunkt der Erstellung oder Aktualisierung sortiert sind. Mit der {% data variables.gists.gist_search_url %} können Sie Gists auch nach Sprache suchen. Die Gist-Suche nutzt dieselbe Suchsyntax wie [die Codesuche](/search-github/searching-on-github/searching-code). Da es sich bei Gists um Git-Repositorys handelt, kannst Du ihren vollständigen Commit-Verlauf anzeigen, einschließlich der Diffs. Du kannst Gists auch forken oder klonen. Weitere Informationen findest Du unter „[Gists forken und klonen](/articles/forking-and-cloning-gists)“. diff --git a/translations/de-DE/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md b/translations/de-DE/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md index 8bae1872ad..c45ba1fbdc 100644 --- a/translations/de-DE/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md +++ b/translations/de-DE/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md @@ -1,6 +1,7 @@ --- title: Gists forken und klonen intro: 'Gists sind tatsächlich Git-Repositorys, was bedeutet, dass Du jeden Gist forken oder klonen kannst, selbst wenn Du nicht der Originalautor bist. Du kannst auch den kompletten Commit-Verlauf eines Gists anzeigen, einschließlich der Diffs.' +permissions: '{% data reusables.enterprise-accounts.emu-permission-gist %}' redirect_from: - /articles/forking-and-cloning-gists - /github/writing-on-github/forking-and-cloning-gists diff --git a/translations/de-DE/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md b/translations/de-DE/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md index a3e92cfdcc..c397374a50 100644 --- a/translations/de-DE/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md +++ b/translations/de-DE/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md @@ -40,9 +40,9 @@ You can indicate emphasis with bold, italic, or strikethrough text in comment fi Du kannst einen Text mit einem `>` zitieren. ```markdown -Mit den Worten von Abraham Lincoln: +Text that is not a quote -> Verzeihen Sie meine Ausdrucksweise. +> Text that is a quote ``` ![Gerenderter zitierter Text](/assets/images/help/writing/quoted-text-rendered.png) @@ -184,7 +184,7 @@ Im folgenden Beispiel kannst Du ein untergeordnetes Listenelement unter dem List ![Liste mit einem untergeordneten Listenelement](/assets/images/help/writing/nested-list-example-3.png) -Du kannst mit derselben Methode mehrere Ebenen an verschachtelten Listen erstellen. Beispiel: Beim ersten untergeordneten Listenelement stehen sieben Zeichen (`␣␣␣␣␣-␣`) vor `Erstes untergeordnetes Listenelement`. Daher musst Du das zweite untergeordnete Listenelement um sieben Leerzeichen einrücken. +Du kannst mit derselben Methode mehrere Ebenen an verschachtelten Listen erstellen. For example, because the first nested list item has seven characters (`␣␣␣␣␣-␣`) before the nested list content `First nested list item`, you would need to indent the second nested list item by seven spaces. ```markdown 100. Erstes Listenelement @@ -262,6 +262,30 @@ For a full list of available emoji and codes, check out [the Emoji-Cheat-Sheet]( Um einen neuen Absatz zu erstellen, lasse eine Zeile zwischen den Textzeilen leer. +{% ifversion fpt or ghae-next or ghes > 3.3 %} +## Footnotes + +You can add footnotes to your content by using this bracket syntax: + +``` +Here is a simple footnote[^1]. + +[^1]: My reference. +``` + +The footnote will render like this: + +![Rendered footnote](/assets/images/site/rendered-footnote.png) +{% endif %} + +## Hiding content with comments + +You can tell {% data variables.product.product_name %} to hide content from the rendered Markdown by placing the content in an HTML comment. + +
+<!-- This content will not appear in the rendered Markdown -->
+
+ ## Markdown-Formatierung ignorieren Sie können {% data variables.product.product_name %} anweisen, die Markdown-Formatierung zu ignorieren, indem Sie das Markdown-Zeichen mit `\` maskieren. @@ -272,13 +296,13 @@ Sie können {% data variables.product.product_name %} anweisen, die Markdown-For Weitere Informationen findest Du unter „[Markdown-Syntax](https://daringfireball.net/projects/markdown/syntax#backslash)“ von Daring Fireball. -## Hiding content with comments +{% ifversion fpt or ghes > 3.2 or ghae-issue-5232 %} -You can tell {% data variables.product.product_name %} to hide content from the rendered Markdown by placing the content in an HTML comment. +## Disabling Markdown rendering -
-<!-- This content will not appear in the rendered Markdown -->
-
+{% data reusables.repositories.disabling-markdown-rendering %} + +{% endif %} ## Weiterführende Informationen diff --git a/translations/de-DE/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md b/translations/de-DE/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md index 2f38c12394..23138ee6db 100644 --- a/translations/de-DE/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md +++ b/translations/de-DE/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md @@ -16,7 +16,7 @@ topics: {% warning %} -**Warning:** If you add an image {% ifversion fpt or ghes > 3.1 or ghae-next %} or video {% endif %} to a pull request or issue comment, anyone can view the anonymized URL without authentication, even if the pull request is in a private repository{% ifversion ghes %}, or if private mode is enabled{% endif %}. To keep sensitive media files private, serve them from a private network or server that requires authentication. {% ifversion fpt %}For more information on anonymized URLs see "[About anonymized URLs](/github/authenticating-to-github/about-anonymized-urls)".{% endif %} +**Warning:** If you add an image{% ifversion fpt or ghes > 3.1 or ghae-next %} or video{% endif %} to a pull request or issue comment, anyone can view the anonymized URL without authentication, even if the pull request is in a private repository{% ifversion ghes %}, or if private mode is enabled{% endif %}. To keep sensitive media files private, serve them from a private network or server that requires authentication. {% ifversion fpt %}For more information on anonymized URLs see "[About anonymized URLs](/github/authenticating-to-github/about-anonymized-urls)".{% endif %} {% endwarning %} @@ -31,9 +31,10 @@ Um eine Datei an eine Issue- oder eine Pull-Request-Unterhaltung anzuhängen, zi {% endtip %} The maximum file size is: -- 10MB for images and gifs{% ifversion fpt or ghes > 3.1 or ghae-next %} +- 10MB for images and gifs{% ifversion fpt %} - 10MB for videos uploaded to a repository owned by a user or organization on a free GitHub plan -- 100MB for videos uploaded to a repository owned by a user or organization on a paid GitHub plan{% endif %} +- 100MB for videos uploaded to a repository owned by a user or organization on a paid GitHub plan{% elsif fpt or ghes > 3.1 or ghae-next %} +- 100MB for videos{% endif %} - 25MB for all other files Wir unterstützen die folgenden Dateiformate: diff --git a/translations/de-DE/content/graphql/guides/managing-enterprise-accounts.md b/translations/de-DE/content/graphql/guides/managing-enterprise-accounts.md index 78ef33e451..99d2844f07 100644 --- a/translations/de-DE/content/graphql/guides/managing-enterprise-accounts.md +++ b/translations/de-DE/content/graphql/guides/managing-enterprise-accounts.md @@ -58,8 +58,9 @@ For some example queries, see "[An example query using the Enterprise Accounts A - `admin:enterprise` The enterprise account specific scopes are: - - `admin:enterprise`: Gives full control of enterprises (includes `manage_billing:enterprise` and `read:enterprise`) - - `manage_billing:enterprise`: Read and write enterprise billing data. + - `admin:enterprise`: Gives full control of enterprises (includes {% ifversion ghes > 3.2 or fpt or ghae %}`manage_runners:enterprise`, {% endif %}`manage_billing:enterprise` and `read:enterprise`) + - `manage_billing:enterprise`: Read and write enterprise billing data.{% ifversion ghes > 3.2 or fpt or ghae %} + - `manage_runners:enterprise`: Access to manage GitHub Actions enterprise runners and runner-groups.{% endif %} - `read:enterprise`: Read enterprise profile data. 4. Copy your personal access token and keep it in a secure place until you add it to your GraphQL client. diff --git a/translations/de-DE/content/graphql/guides/using-the-graphql-api-for-discussions.md b/translations/de-DE/content/graphql/guides/using-the-graphql-api-for-discussions.md index 8578fcf7f1..8668e4e18d 100644 --- a/translations/de-DE/content/graphql/guides/using-the-graphql-api-for-discussions.md +++ b/translations/de-DE/content/graphql/guides/using-the-graphql-api-for-discussions.md @@ -1080,4 +1080,4 @@ Return type fields: ## Suche -Discussion may be returned from the top-level `search` field. To search for discussion, specify `type` as `DISCUSSION`. The `SearchResultItemConnection` type has a `discussionCount` field to report the number of returned discussions, and the `Discussion` type is added to the `SearchResultItem` union. For more information, see "[Queries](/graphql/reference/queries#searchresultitemconnection)" and "[Searching discussions](/github/searching-for-information-on-github/searching-discussions)." +Discussion may be returned from the top-level `search` field. To search for discussion, specify `type` as `DISCUSSION`. The `SearchResultItemConnection` type has a `discussionCount` field to report the number of returned discussions, and the `Discussion` type is added to the `SearchResultItem` union. For more information, see "[Queries](/graphql/reference/queries#searchresultitemconnection)" and "[Searching discussions](/search-github/searching-on-github/searching-discussions)." diff --git a/translations/de-DE/content/index.md b/translations/de-DE/content/index.md index 12ab7e6cd6..3a7fea8970 100644 --- a/translations/de-DE/content/index.md +++ b/translations/de-DE/content/index.md @@ -27,6 +27,7 @@ children: - actions - codespaces - packages + - search-github - developers - rest - graphql diff --git a/translations/de-DE/content/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users.md b/translations/de-DE/content/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users.md index d3070016eb..dc24f9ff79 100644 --- a/translations/de-DE/content/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users.md +++ b/translations/de-DE/content/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users.md @@ -1,6 +1,7 @@ --- title: Issues und Pull Requests anderen GitHub-Benutzern zuweisen intro: 'Zugewiesene Bearbeiter stellen klar, wer bestimmte Issues und Pull Requests bearbeitet.' +permissions: 'Anyone with write access to a repository can assign issues and pull requests. {% data reusables.enterprise-accounts.emu-permission-repo %}' redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/assigning-issues-and-pull-requests-to-other-github-users - /articles/assigning-issues-and-pull-requests-to-other-github-users @@ -15,8 +16,6 @@ topics: shortTitle: Assign issues & PRs --- -Jeder, der über Schreibberechtigungen für ein Repository verfügt, kann Issues und Pull Requests zuweisen. - ## About issue and pull request assignees You can assign up to 10 people to each issue or pull request, including yourself, anyone who has commented on the issue or pull request, anyone with write permissions to the repository, and organization members with read permissions to the repository. Weitere Informationen findest Du unter „[Zugriffsberechtigungen auf {% data variables.product.prodname_dotcom %}](/articles/access-permissions-on-github).“ diff --git a/translations/de-DE/content/issues/tracking-your-work-with-issues/creating-an-issue.md b/translations/de-DE/content/issues/tracking-your-work-with-issues/creating-an-issue.md index 46ca1a8c13..aa681919da 100644 --- a/translations/de-DE/content/issues/tracking-your-work-with-issues/creating-an-issue.md +++ b/translations/de-DE/content/issues/tracking-your-work-with-issues/creating-an-issue.md @@ -1,7 +1,7 @@ --- title: Einen Issue erstellen intro: 'Issues can be created in a variety of ways, so you can choose the most convenient method for your workflow.' -permissions: People with read permissions can create an issue in a repository where issues are enabled. +permissions: 'People with read access can create an issue in a repository where issues are enabled. {% data reusables.enterprise-accounts.emu-permission-repo %}' redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/creating-an-issue - /articles/creating-an-issue diff --git a/translations/de-DE/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md b/translations/de-DE/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md index 3e419bc734..7deb8e2e28 100644 --- a/translations/de-DE/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md +++ b/translations/de-DE/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md @@ -102,7 +102,8 @@ Du kannst die Pull-Request-Liste eines Repositorys filtern, um folgende Pull Req - Pull Requests, für die vor dem Merge [ein Review erforderlich ist](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging) - Pull Requests, die ein Reviewer genehmigt hat - Pull Requests, bei denen ein Reviewer um Änderungen gebeten hat -- Pull Requests, die Du überprüft hast +- Pull requests that you have reviewed{% ifversion fpt or ghae or ghes > 3.2 %} +- Pull requests that someone has asked you directly to review{% endif %} - Pull Requests, um denen [Du oder ein Team, bei dem Du Mitglied bist, um einen Review gebeten wurde](/articles/requesting-a-pull-request-review) {% data reusables.repositories.navigate-to-repo %} @@ -185,7 +186,8 @@ Bei Pull Requests kannst Du die Suche auch verwenden, um: - Von einem Reviewer genehmigte Pull Requests zu filtern: `state:open type:pr review:approved` - Pull Requests zu filtern, in denen ein Reviewer um Änderungen gebeten hat: `state:open type:pr review:changes_requested` - Pull Requests nach [Reviewer](/articles/about-pull-request-reviews/) zu filtern: `state:open type:pr reviewed-by:octocat` -- Pull Requests nach dem bestimmten Benutzer zu filtern, der für den [Review angefordert](/articles/requesting-a-pull-request-review) wurde: `state:open type:pr review-requested:octocat` +- Filter pull requests by the specific user [requested for review](/articles/requesting-a-pull-request-review): `state:open type:pr review-requested:octocat`{% ifversion fpt or ghae or ghes > 3.2 %} +- Filter pull requests that someone has asked you directly to review: `state:open type:pr user-review-requested:@me`{% endif %} - Pull Requests nach einem Team filtern, das für dein Review angefordert wurde: `state:open type:pr team-review-requested:github/atom`{% ifversion fpt or ghes or ghae %} - Nach Pull Requests filtern, die zu einem Issue verknüpft sind, die der Pull Request schließen könnte: `linked:issue`{% endif %} diff --git a/translations/de-DE/content/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository.md b/translations/de-DE/content/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository.md index 9114a5e020..1f406cdedb 100644 --- a/translations/de-DE/content/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository.md +++ b/translations/de-DE/content/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository.md @@ -1,6 +1,7 @@ --- title: Einen Issue an Dein Repository anheften intro: Du kannst bis zu drei wichtige Issues oberhalb der Issueliste in Deinem Repository anheften. +permissions: 'People with write access to a repository can pin issue in the repository. {% data reusables.enterprise-accounts.emu-permission-repo %}' redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/pinning-an-issue-to-your-repository - /articles/pinning-an-issue-to-your-repository @@ -17,8 +18,6 @@ shortTitle: Pin an issue ![Angeheftete Issues](/assets/images/help/issues/pinned-issues.png) -Um einen Issue anzuheften, benötigst Du Schreibberechtigung für das Repository, in dem sich der Issue befindet. - {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issues %} 1. Klicke in der Liste der Issues auf den Issue, den Du anheften möchtest. diff --git a/translations/de-DE/content/issues/tracking-your-work-with-issues/quickstart.md b/translations/de-DE/content/issues/tracking-your-work-with-issues/quickstart.md index cd0e66c876..8395e5afa1 100644 --- a/translations/de-DE/content/issues/tracking-your-work-with-issues/quickstart.md +++ b/translations/de-DE/content/issues/tracking-your-work-with-issues/quickstart.md @@ -19,7 +19,7 @@ This guide demonstrates how to use {% data variables.product.prodname_github_iss ## Vorrausetzungen -To create an issue, you need a repository. You can use an existing repository that you have write access to, or you can create a new repository. The repository must have issues enabled. Weitere Informationen zum Erstellen eines Repositorys findest Du unter „[Ein neues Repository erstellen](/articles/creating-a-new-repository).“ For more information about enabling issues if they are disabled in your repository, see "[Disabling issues](/github/administering-a-repository/managing-repository-settings/disabling-issues)." +To create an issue, you need a repository. You can use an existing repository that you have write access to, or you can create a new repository. {% data reusables.enterprise-accounts.emu-permission-repo %} The repository must have issues enabled. Weitere Informationen zum Erstellen eines Repositorys findest Du unter „[Ein neues Repository erstellen](/articles/creating-a-new-repository).“ For more information about enabling issues if they are disabled in your repository, see "[Disabling issues](/github/administering-a-repository/managing-repository-settings/disabling-issues)." ## Opening a blank issue diff --git a/translations/de-DE/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md b/translations/de-DE/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md index b8adafca5f..524cb50362 100644 --- a/translations/de-DE/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md +++ b/translations/de-DE/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md @@ -1,6 +1,7 @@ --- title: Managing labels intro: 'You can classify {% ifversion fpt %}issues, pull requests, and discussions{% else %}issues and pull requests{% endif %} by creating, editing, applying, and deleting labels.' +permissions: '{% data reusables.enterprise-accounts.emu-permission-repo %}' redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/managing-labels - /articles/managing-Labels @@ -30,8 +31,6 @@ topics: You can manage your work on {% data variables.product.product_name %} by creating labels to categorize {% ifversion fpt %}issues, pull requests, and discussions{% else %}issues and pull requests{% endif %}. You can apply labels in the repository the label was created in. Once a label exists, you can use the label on any {% ifversion fpt %}issue, pull request, or discussion{% else %}issue or pull request{% endif %} within that repository. -Alle Benutzer mit Lesezugriff auf ein Repository können die Kennzeichnungen des Repositorys einsehen und durchsuchen. Anyone with triage access to a repository can apply/dismiss existing labels. Um eine Kennzeichnung zu erstellen, zu bearbeiten, anzuwenden oder zu löschen, benötigst Du Schreibzugriff auf das Repository. - ## About default labels {% data variables.product.product_name %} bietet in jedem neuen Repository Standardkennzeichnungen. Mithilfe dieser Standardkennzeichnungen kannst Du einen Standardworkflow in einem Repository erstellen. @@ -58,6 +57,8 @@ Organisationsinhaber können die Standardkennzeichnungen für Repositories in ih ## Eine Kennzeichnung erstellen +Anyone with write access to a repository can create a label. + {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} {% data reusables.project-management.labels %} @@ -69,11 +70,15 @@ Organisationsinhaber können die Standardkennzeichnungen für Repositories in ih ## Applying a label +Anyone with triage access to a repository can apply and dismiss labels. + 1. Navigate to the {% ifversion fpt %}issue, pull request, or discussion{% else %}issue or pull request{% endif %}. 1. In the right sidebar, to the right of "Labels", click {% octicon "gear" aria-label="The gear icon" %}, then click a label. !["Labels" drop-down menu](/assets/images/help/issues/labels-drop-down.png) ## Eine Kennzeichnung bearbeiten +Anyone with write access to a repository can edit existing labels. + {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} {% data reusables.project-management.labels %} @@ -85,6 +90,8 @@ Organisationsinhaber können die Standardkennzeichnungen für Repositories in ih ## Eine Kennzeichnung löschen +Anyone with write access to a repository can delete existing labels. + Deleting a label will remove the label from issues and pull requests. {% data reusables.repositories.navigate-to-repo %} diff --git a/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md b/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md index e5bbc39950..a77a389343 100644 --- a/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md +++ b/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md @@ -24,6 +24,8 @@ Mit Enterprise-Konten können Inhaber Richtlinien und Abrechnungen für mehrere Bei Organisationen, die einem Enterprise-Konto angehören, wird die Abrechnung auf der Ebene des Enterprise-Kontos verwaltet, und die Abrechnungseinstellungen sind auf der Organisationsebene nicht verfügbar. Enterprise-Inhaber können Richtlinien für alle Organisationen im Enterprise-Konto festlegen oder den Organisationsinhabern erlauben, die Richtlinien auf Organisationsebene festzulegen. Organisationsinhaber können die für Deine Organisation erzwungenen Einstellungen auf der Ebene des Enterprise-Kontos nicht ändern. Wenn Du Fragen zu einer Richtlinie oder einer Einstellung für Deine Organisation hast, wende Dich an den Inhaber Deines Enterprise-Kontos. +{% data reusables.enterprise-accounts.invite-organization %} + {% data reusables.gated-features.enterprise-accounts %} {% data reusables.organizations.org-ownership-recommendation %} Weitere Informationen findest Du unter „[Die Inhaber-Kontinuität für Deine Organisation aufrechterhalten](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)." diff --git a/translations/de-DE/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md b/translations/de-DE/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md index a671ef43de..a6dcf886cb 100644 --- a/translations/de-DE/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md +++ b/translations/de-DE/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md @@ -25,6 +25,18 @@ Du kannst die verknüpfte Identität, die aktiven Sitzungen und die autorisierte {% data reusables.saml.about-linked-identities %} +Wenn verfügbar, wird der Eintrag SCIM-Daten enthalten. Weitere Informationen findest Du unter „[Über SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)." + +{% warning %} + +**Warning:** For organizations using SCIM: +- Revoking a linked user identity on {% data variables.product.product_name %} will also remove the SAML and SCIM metadata. As a result, the identity provider will not be able to synchronize or deprovision the linked user identity. +- An admin must revoke a linked identity through the identity provider. +- To revoke a linked identity and link a different account through the identity provider, an admin can remove and re-assign the user to the {% data variables.product.product_name %} application. For more information, see your identity provider's documentation. + +{% endwarning %} + + {% data reusables.identity-and-permissions.revoking-identity-team-sync %} {% data reusables.profile.access_org %} diff --git a/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md b/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md index fa8f647224..49f6097b09 100644 --- a/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md +++ b/translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md @@ -54,95 +54,96 @@ Some of the features listed below are limited to organizations using {% data var {% endnote %} {% endif %} -| Repository-Aktion | Read (Gelesen) | bewerten | Schreiben | Betreuen | Verwalten | -|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:--------------:|:--------:|:---------:|:--------:|:------------------------------------------------:| -| Pull (Abrufen) aus den zugewiesenen Repositorys der Person oder des Teams | **X** | **X** | **X** | **X** | **X** | -| Erstellen eines Forks des zugewiesenen Repositorys der Person oder des Teams | **X** | **X** | **X** | **X** | **X** | -| Bearbeiten und Löschen eigener Kommentare | **X** | **X** | **X** | **X** | **X** | -| Eröffnen von Issues | **X** | **X** | **X** | **X** | **X** | -| Schließen der selbst eröffneten Issues | **X** | **X** | **X** | **X** | **X** | -| Erneutes Eröffnen von selbst geschlossenen Issues | **X** | **X** | **X** | **X** | **X** | -| Sich-Selbst-Zuweisen von Issues | **X** | **X** | **X** | **X** | **X** | -| Senden von Pull Requests aus Forks der dem Team zugewiesenen Repositorys | **X** | **X** | **X** | **X** | **X** | -| Absenden von Reviews zu Pull Requests | **X** | **X** | **X** | **X** | **X** | -| Anzeigen veröffentlichter Releases | **X** | **X** | **X** | **X** | **X** |{% ifversion fpt %} -| [GitHub Actions-Workflow-Ausführungen](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) ansehen | **X** | **X** | **X** | **X** | **X** +| Repository-Aktion | Read (Gelesen) | bewerten | Schreiben | Betreuen | Verwalten | +|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:--------------:|:--------:|:---------:|:--------:|:-----------------------------------------------------:| +| Pull (Abrufen) aus den zugewiesenen Repositorys der Person oder des Teams | **X** | **X** | **X** | **X** | **X** | +| Erstellen eines Forks des zugewiesenen Repositorys der Person oder des Teams | **X** | **X** | **X** | **X** | **X** | +| Bearbeiten und Löschen eigener Kommentare | **X** | **X** | **X** | **X** | **X** | +| Eröffnen von Issues | **X** | **X** | **X** | **X** | **X** | +| Schließen der selbst eröffneten Issues | **X** | **X** | **X** | **X** | **X** | +| Erneutes Eröffnen von selbst geschlossenen Issues | **X** | **X** | **X** | **X** | **X** | +| Sich-Selbst-Zuweisen von Issues | **X** | **X** | **X** | **X** | **X** | +| Senden von Pull Requests aus Forks der dem Team zugewiesenen Repositorys | **X** | **X** | **X** | **X** | **X** | +| Absenden von Reviews zu Pull Requests | **X** | **X** | **X** | **X** | **X** | +| Anzeigen veröffentlichter Releases | **X** | **X** | **X** | **X** | **X** |{% ifversion fpt %} +| [GitHub Actions-Workflow-Ausführungen](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) ansehen | **X** | **X** | **X** | **X** | **X** {% endif %} -| Bearbeiten von Wikis | **X** | **X** | **X** | **X** | **X** |{% ifversion fpt %} -| [Melden von Missbrauch oder Spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** +| Edit wikis in public repositories | **X** | **X** | **X** | **X** | **X** | +| Edit wikis in private repositories | | | **X** | **X** | **X** |{% ifversion fpt %} +| [Melden von Missbrauch oder Spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** {% endif %} -| Apply/dismiss labels | | **X** | **X** | **X** | **X** | -| Create, edit, delete labels | | | **X** | **X** | **X** | -| Schließen, erneutes Eröffnen und Zuweisen aller Issues und Pull Requests | | **X** | **X** | **X** | **X** |{% ifversion fpt or ghae or ghes > 3.0 %} -| [Enable and disable auto-merge on a pull request](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** +| Apply/dismiss labels | | **X** | **X** | **X** | **X** | +| Create, edit, delete labels | | | **X** | **X** | **X** | +| Schließen, erneutes Eröffnen und Zuweisen aller Issues und Pull Requests | | **X** | **X** | **X** | **X** |{% ifversion fpt or ghae or ghes > 3.0 %} +| [Enable and disable auto-merge on a pull request](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** {% endif %} -| Anwenden von Meilensteinen | | **X** | **X** | **X** | **X** | -| Markieren von [Issues und Pull Requests als Duplikat](/articles/about-duplicate-issues-and-pull-requests) | | **X** | **X** | **X** | **X** | -| Anfordern von [Pull Request-Reviews](/articles/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** | -| Merge a [pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges) | | | **X** | **X** | **X** | -| Push (Schreiben) in die zugewiesenen Repositorys der Person oder des Teams | | | **X** | **X** | **X** | -| Bearbeiten und Löschen der Kommentare beliebiger Benutzer zu Commits, Pull Requests und Issues | | | **X** | **X** | **X** | -| [Ausblenden der Kommentare beliebiger Benutzer](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **X** | **X** | **X** | -| [Blockieren von Unterhaltungen](/communities/moderating-comments-and-conversations/locking-conversations) | | | **X** | **X** | **X** | -| Übertragen von Issues (siehe „[Issue auf ein anderes Repository übertragen](/articles/transferring-an-issue-to-another-repository)“) | | | **X** | **X** | **X** | -| [Agieren als designierter Codeinhaber eines Repositorys](/articles/about-code-owners) | | | **X** | **X** | **X** | -| [Markieren eines Pull-Request-Entwurfs als bereit für den Review](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | -| [Einen Pull Request in einen Entwurf umwandeln](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | -| Absenden von Reviews, die sich auf die Merge-Fähigkeit eines Pull Request auswirken | | | **X** | **X** | **X** | -| [Anwenden vorgeschlagener Änderungen](/articles/incorporating-feedback-in-your-pull-request) auf Pull Requests | | | **X** | **X** | **X** | -| Erstellen von [Statuschecks](/articles/about-status-checks) | | | **X** | **X** | **X** |{% ifversion fpt %} -| Erstellen, Bearbeiten, Ausführen, Neuausführen und Abbrechen von [GitHub-Actions-Workflows](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** +| Anwenden von Meilensteinen | | **X** | **X** | **X** | **X** | +| Markieren von [Issues und Pull Requests als Duplikat](/articles/about-duplicate-issues-and-pull-requests) | | **X** | **X** | **X** | **X** | +| Anfordern von [Pull Request-Reviews](/articles/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** | +| Merge a [pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges) | | | **X** | **X** | **X** | +| Push (Schreiben) in die zugewiesenen Repositorys der Person oder des Teams | | | **X** | **X** | **X** | +| Bearbeiten und Löschen der Kommentare beliebiger Benutzer zu Commits, Pull Requests und Issues | | | **X** | **X** | **X** | +| [Ausblenden der Kommentare beliebiger Benutzer](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **X** | **X** | **X** | +| [Blockieren von Unterhaltungen](/communities/moderating-comments-and-conversations/locking-conversations) | | | **X** | **X** | **X** | +| Übertragen von Issues (siehe „[Issue auf ein anderes Repository übertragen](/articles/transferring-an-issue-to-another-repository)“) | | | **X** | **X** | **X** | +| [Agieren als designierter Codeinhaber eines Repositorys](/articles/about-code-owners) | | | **X** | **X** | **X** | +| [Markieren eines Pull-Request-Entwurfs als bereit für den Review](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | +| [Einen Pull Request in einen Entwurf umwandeln](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | +| Absenden von Reviews, die sich auf die Merge-Fähigkeit eines Pull Request auswirken | | | **X** | **X** | **X** | +| [Anwenden vorgeschlagener Änderungen](/articles/incorporating-feedback-in-your-pull-request) auf Pull Requests | | | **X** | **X** | **X** | +| Erstellen von [Statuschecks](/articles/about-status-checks) | | | **X** | **X** | **X** |{% ifversion fpt %} +| Erstellen, Bearbeiten, Ausführen, Neuausführen und Abbrechen von [GitHub-Actions-Workflows](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** {% endif %} -| Erstellen und Bearbeiten von Releases | | | **X** | **X** | **X** | -| Anzeigen von Release-Entwürfen | | | **X** | **X** | **X** | -| Bearbeiten von Repository-Beschreibungen | | | | **X** | **X** |{% ifversion fpt or ghae %} -| [Pakete anzeigen und installieren](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | -| [Pakete veröffentlichen](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | -| | | | | | | -| {% ifversion fpt or ghes > 3.0 %}[Delete and restore packages](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Delete packages](/packages/learn-github-packages/deleting-a-package){% endif %} | | | | | **X** | {% endif %} -| Verwalten von [Themen](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** | -| Aktivieren von Wikis und Einschränken der Wiki-Editoren | | | | **X** | **X** | -| Aktivieren von Projektboards | | | | **X** | **X** | -| Configure [pull request merges](/articles/configuring-pull-request-merges) | | | | **X** | **X** | -| Configure [a publishing source for {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** | -| [An geschützte Branches pushen](/articles/about-protected-branches) | | | | **X** | **X** | -| [Erstellen und Bearbeiten sozialer Tickets für Repositorys](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% ifversion fpt %} -| [Interaktionen in einem Repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository) limitieren | | | | **X** | **X** +| Erstellen und Bearbeiten von Releases | | | **X** | **X** | **X** | +| Anzeigen von Release-Entwürfen | | | **X** | **X** | **X** | +| Bearbeiten von Repository-Beschreibungen | | | | **X** | **X** |{% ifversion fpt or ghae %} +| [Pakete anzeigen und installieren](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | +| [Pakete veröffentlichen](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | +| | | | | | | +| {% ifversion fpt or ghes > 3.0 %}[Delete and restore packages](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Delete packages](/packages/learn-github-packages/deleting-a-package){% endif %} | | | | | **X** | {% endif %} +| Verwalten von [Themen](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** | +| Aktivieren von Wikis und Einschränken der Wiki-Editoren | | | | **X** | **X** | +| Aktivieren von Projektboards | | | | **X** | **X** | +| Configure [pull request merges](/articles/configuring-pull-request-merges) | | | | **X** | **X** | +| Configure [a publishing source for {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** | +| [An geschützte Branches pushen](/articles/about-protected-branches) | | | | **X** | **X** | +| [Erstellen und Bearbeiten sozialer Tickets für Repositorys](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% ifversion fpt %} +| [Interaktionen in einem Repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository) limitieren | | | | **X** | **X** {% endif %} -| Löschen von Issues (siehe „[Issue löschen](/articles/deleting-an-issue)“) | | | | | **X** | -| Mergen von Pull Requests in geschützten Branches auch ohne Genehmigungsreviews | | | | | **X** | -| [Festlegen der Codeinhaber eines Repositorys](/articles/about-code-owners) | | | | | **X** | -| Ein Repository zu einem Team hinzufügen (für Details siehe „[Teamzugriff auf ein Organisations-Repository verwalten](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)") | | | | | **X** | -| [Verwalten des Zugriffs externer Mitarbeiter auf ein Repository](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | -| [Ändern der Sichtbarkeit eines Repositorys](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | -| Erstellen einer Vorlage aus einem Repository (siehe „[Repository-Vorlage erstellen](/articles/creating-a-template-repository)“) | | | | | **X** | -| Ändern der Einstellungen eines Repositorys | | | | | **X** | -| Verwalten des Team- und Mitarbeiterzugriffs auf ein Repository | | | | | **X** | -| Bearbeiten des Standardbranch eines Repositorys | | | | | **X** |{% ifversion fpt or ghes > 3.0 %} -| Rename the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | | | **X** | -| Rename a branch other than the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | **X** | **X** | **X** +| Löschen von Issues (siehe „[Issue löschen](/articles/deleting-an-issue)“) | | | | | **X** | +| Mergen von Pull Requests in geschützten Branches auch ohne Genehmigungsreviews | | | | | **X** | +| [Festlegen der Codeinhaber eines Repositorys](/articles/about-code-owners) | | | | | **X** | +| Ein Repository zu einem Team hinzufügen (für Details siehe „[Teamzugriff auf ein Organisations-Repository verwalten](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)") | | | | | **X** | +| [Verwalten des Zugriffs externer Mitarbeiter auf ein Repository](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | +| [Ändern der Sichtbarkeit eines Repositorys](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | +| Erstellen einer Vorlage aus einem Repository (siehe „[Repository-Vorlage erstellen](/articles/creating-a-template-repository)“) | | | | | **X** | +| Ändern der Einstellungen eines Repositorys | | | | | **X** | +| Verwalten des Team- und Mitarbeiterzugriffs auf ein Repository | | | | | **X** | +| Bearbeiten des Standardbranch eines Repositorys | | | | | **X** |{% ifversion fpt or ghes > 3.0 or ghae-next %} +| Rename the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | | | **X** | +| Rename a branch other than the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | **X** | **X** | **X** {% endif %} -| Manage webhooks and deploy keys | | | | | **X** |{% ifversion fpt %} -| [Manage data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **X** +| Manage webhooks and deploy keys | | | | | **X** |{% ifversion fpt %} +| [Manage data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **X** {% endif %} -| [Verwalten der Forking-Richtlinie für ein Repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | -| [Übertragen von Repositorys auf die Organisation](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | -| [Löschen von Repositorys oder Übertragen von Repositorys aus der Organisation](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | -| [Archivieren von Repositorys](/articles/about-archiving-repositories) | | | | | **X** |{% ifversion fpt %} -| Anzeigen einer Sponsorenschaltfläche (siehe „[Sponsorenschaltfläche in Ihrem Repository anzeigen](/articles/displaying-a-sponsor-button-in-your-repository)“) | | | | | **X** +| [Verwalten der Forking-Richtlinie für ein Repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | +| [Übertragen von Repositorys auf die Organisation](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | +| [Löschen von Repositorys oder Übertragen von Repositorys aus der Organisation](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | +| [Archivieren von Repositorys](/articles/about-archiving-repositories) | | | | | **X** |{% ifversion fpt %} +| Anzeigen einer Sponsorenschaltfläche (siehe „[Sponsorenschaltfläche in Ihrem Repository anzeigen](/articles/displaying-a-sponsor-button-in-your-repository)“) | | | | | **X** {% endif %} -| Create autolink references to external resources, like JIRA or Zendesk (see "[Configuring autolinks to reference external resources](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **X** |{% ifversion fpt %} -| [Enable {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) in a repository | | | | **X** | **X** | -| [Create and edit categories](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) for {% data variables.product.prodname_discussions %} | | | | **X** | **X** | -| [Move a discussion to a different category](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [Transfer a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) to a new repository | | | **X** | **X** | **X** | -| [Manage pinned discussions](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [Convert issues to discussions in bulk](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [Lock and unlock discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [Individually convert issues to discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [Create new discussions and comment on existing discussions](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** | -| [Delete a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion) | | | | **X** | **X** |{% endif %}{% ifversion fpt %} -| Create [codespaces](/codespaces/about-codespaces) | | | **X** | **X** | **X** +| Create autolink references to external resources, like JIRA or Zendesk (see "[Configuring autolinks to reference external resources](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **X** |{% ifversion fpt %} +| [Enable {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) in a repository | | | | **X** | **X** | +| [Create and edit categories](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) for {% data variables.product.prodname_discussions %} | | | | **X** | **X** | +| [Move a discussion to a different category](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Transfer a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) to a new repository | | | **X** | **X** | **X** | +| [Manage pinned discussions](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Convert issues to discussions in bulk](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Lock and unlock discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [Individually convert issues to discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [Create new discussions and comment on existing discussions](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** | +| [Delete a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion) | | | | **X** | **X** |{% endif %}{% ifversion fpt %} +| Create [codespaces](/codespaces/about-codespaces) | | | **X** | **X** | **X** {% endif %} ### Permission requirements for security features diff --git a/translations/de-DE/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md index 44508c5807..b48720d63c 100644 --- a/translations/de-DE/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md +++ b/translations/de-DE/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md @@ -36,7 +36,7 @@ Alternativ kannst Du {% data variables.product.prodname_actions %} für alle Rep {% endif %} -{% ifversion fpt or ghes > 2.22 %} +{% ifversion fpt or ghes > 2.22 or ghae-next %} ## {% data variables.product.prodname_actions %}-Berechtigungen für Deine Organisation verwalten @@ -63,7 +63,12 @@ You can disable all workflows for an organization or set a policy that configure {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.settings-sidebar-actions %} -1. Under **Policies**, select **Allow select actions** and add your required actions to the list. ![Add actions to allow list](/assets/images/help/organizations/actions-policy-allow-list.png) +1. Under **Policies**, select **Allow select actions** and add your required actions to the list. + {%- ifversion ghes %} + ![Add actions to allow list](/assets/images/help/organizations/actions-policy-allow-list.png) + {%- else %} + ![Add actions to allow list](/assets/images/enterprise/github-ae/organizations/actions-policy-allow-list.png) + {%- endif %} 1. Klicke auf **Save** (Speichern). {% endif %} @@ -71,7 +76,9 @@ You can disable all workflows for an organization or set a policy that configure {% ifversion fpt %} ## Configuring required approval for workflows from public forks -{% data reusables.actions.workflow-run-approve-public-fork %} You can configure this behavior for an organization using the procedure below. Modifying this setting overrides the configuration set at the enterprise level. +{% data reusables.actions.workflow-run-approve-public-fork %} + +You can configure this behavior for an organization using the procedure below. Modifying this setting overrides the configuration set at the enterprise level. {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} diff --git a/translations/de-DE/content/organizations/managing-organization-settings/transferring-organization-ownership.md b/translations/de-DE/content/organizations/managing-organization-settings/transferring-organization-ownership.md index 7c2a1a12b7..1d888fad24 100644 --- a/translations/de-DE/content/organizations/managing-organization-settings/transferring-organization-ownership.md +++ b/translations/de-DE/content/organizations/managing-organization-settings/transferring-organization-ownership.md @@ -15,6 +15,13 @@ topics: shortTitle: Transfer ownership --- +{% ifversion fpt %} +{% note %} + +**Note:** {% data reusables.enterprise-accounts.invite-organization %} + +{% endnote %}{% endif %} + 1. Wenn Du das einige Mitglied mit *Inhaber*-Berechtigungen bist, gib einem anderen Organisationsmitglied ebenfalls die Inhaberrolle. Weitere Informationen findest Du unter „[Ernennung eines Organisationsinhabers](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization#appointing-an-organization-owner)." 2. Kontaktiere den neuen Inhaber, um sicherzustellen, dass dieser [auf die Organisationseinstellungen zugreifen kann](/articles/accessing-your-organization-s-settings). {% ifversion fpt %} diff --git a/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md index 3831a2e7d8..07c394cd52 100644 --- a/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md +++ b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md @@ -13,6 +13,8 @@ topics: shortTitle: IAM with SAML SSO --- +{% data reusables.enterprise-accounts.emu-saml-note %} + ## Informationen zu SAML SSO {% data reusables.saml.dotcom-saml-explanation %} diff --git a/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md index 3729f8c814..b845a14ba6 100644 --- a/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md +++ b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md @@ -12,6 +12,8 @@ topics: - Teams --- +{% data reusables.enterprise-accounts.emu-scim-note %} + Wenn Sie in Ihrer Organisation [SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on) verwenden, können Sie SCIM implementieren, um den Zugriff von Organisationsmitgliedern auf {% data variables.product.product_name %} hinzuzufügen, zu verwalten und zu entfernen. Ein Administrator kann beispielsweise die Bereitstellung des Zugriffs eines Organisationsmitglieds mithilfe von SCIM aufheben und das Mitglied automatisch aus der Organisation entfernen. Wenn Du SAML SSO verwendest, ohne SCIM zu implementieren, ist die Aufhebung der Bereitstellung nicht automatisiert. Wenn die Sitzungen der Organisationsmitglieder ablaufen, nachdem ihr Zugriff vom IdP entfernt wurde, werden sie nicht automatisch aus der Organisation entfernt. Autorisierte Token gewähren auch nach Ablauf ihrer Sitzungen Zugriff auf die Organisation. Um den Zugriff zu entfernen, können Administratoren entweder manuell das autorisierte Token aus der Organisation entfernen oder seine Entfernung mit SCIM automatisieren. diff --git a/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md index c3b458a9d5..423d0f1d59 100644 --- a/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md +++ b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md @@ -17,6 +17,8 @@ topics: shortTitle: Manage team synchronization --- +{% data reusables.enterprise-accounts.emu-scim-note %} + {% data reusables.gated-features.okta-team-sync %} ## Informationen zur Teamsynchronisierung @@ -31,6 +33,8 @@ Du kannst die Teamsynchronisierung zwischen Deinem IdP und {% data variables.pro Du kannst die Teamsynchronisierung auch für Organisationen im Besitz eines Enterprise-Kontos aktivieren. Weiter Informationen findest Du unter „[Sicherheitseinstellungen für Dein Enterprise-Konto erzwingen](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account)." +{% data reusables.enterprise-accounts.team-sync-override %} + {% data reusables.identity-and-permissions.team-sync-usage-limits %} ## Teamsynchronisierung aktivieren diff --git a/translations/de-DE/content/organizations/organizing-members-into-teams/creating-a-team.md b/translations/de-DE/content/organizations/organizing-members-into-teams/creating-a-team.md index d256bd8683..1e80586226 100644 --- a/translations/de-DE/content/organizations/organizing-members-into-teams/creating-a-team.md +++ b/translations/de-DE/content/organizations/organizing-members-into-teams/creating-a-team.md @@ -25,11 +25,13 @@ Nur Organisationsinhaber und Betreuer eines übergeordneten Teams können ein ne {% data reusables.organizations.team_description %} {% data reusables.organizations.create-team-choose-parent %} {% ifversion fpt %} -1. Wenn Deine Organisations oder Dein Enterprise-Konto optional die Teamsynchronisierung verwendet, kannst Du für das Verbinden einer Identitätsanbieter-Gruppe mit Deinem Team das Dropdownmenü „Identity Provider Groups" (Identitätsanbieter-Gruppen) benutzen und bis zu 5 Gruppen auswählen. Weitere Informationen findest Du unter „[Ein Team mit einer Identitätsanbieter-Gruppe synchronisieren](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)." ![Dropdownmenü zur Auswahl einer Identitätsanbieter-Gruppe](/assets/images/help/teams/choose-an-idp-group.png) +1. Optionally, if your organization or enterprise account uses team synchronization or your enterprise uses {% data variables.product.prodname_emus %}, connect an identity provider group to your team. + * If your enterprise uses {% data variables.product.prodname_emus %}, use the "Identity Provider Groups" drop-down menu, and select a single identity provider group to connect to the new team. For more information, "[Managing team memberships with identity provider groups](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)." + * If your organization or enterprise account uses team synchronization, use the "Identity Provider Groups" drop-down menu, and select up to five identity provider groups to connect to the new team. Weitere Informationen findest Du unter „[Ein Team mit einer Identitätsanbieter-Gruppe synchronisieren](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)." ![Dropdownmenü zur Auswahl einer Identitätsanbieter-Gruppe](/assets/images/help/teams/choose-an-idp-group.png) {% endif %} {% data reusables.organizations.team_visibility %} {% data reusables.organizations.create_team %} -9. Optional kannst Du [dem Team Zugriff auf die Repositorys der Organisation gewähren](/articles/managing-team-access-to-an-organization-repository)“. +1. Optional kannst Du [dem Team Zugriff auf die Repositorys der Organisation gewähren](/articles/managing-team-access-to-an-organization-repository)“. ## Weiterführende Informationen diff --git a/translations/de-DE/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md b/translations/de-DE/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md index 58bac05ef7..60ef325171 100644 --- a/translations/de-DE/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md +++ b/translations/de-DE/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md @@ -45,8 +45,11 @@ Any team members that have set their status to "Busy" will not be selected for r 7. Benutze unter „How many team members should be assigned to review?" (Wie viele Teammitglieder sollen dem Review zugewiesen werden?) das Dropdownmenü und wähle die Anzahl der Prüfer, die jedem Pull Request zugewiesen werden sollen. ![Dropdownmenü „Number of reviewers" (Anzahl der Prüfer)](/assets/images/help/teams/review-assignment-number.png) 8. Benutze unter „Routing algorithm" (Routing-Algorithmen) das Dropdownmenü und wähle den Algorithmus, den Du benutzen möchtest. Weitere Informationen findest Du unter „[Routing-Algorithmen](#routing-algorithms)." ![Dropdownmenü „Routing algorithm" (Routing-Algorithmus)](/assets/images/help/teams/review-assignment-algorithm.png) 9. Um optional bestimmte Teammitglieder immer auszulassen, wähle **Never assign certain team members** (Weise bestimmte Teammitglieder nie zu). Dann wähle eines oder mehrere Teammitglieder, die Du immer auslassen willst. ![Kontrollkästchen und Dropdownmenü „Never assign certain team members" (Weise bestimmte Teammitglieder nie zu)](/assets/images/help/teams/review-assignment-skip-members.png) -10. Um optional nur diejenigen Teammitglieder zu informieren, die durch die Code-Review-Zuweisung für einen Pull-Request-Review betroffen sind, wähle unter „Notifications" (Benachrichtigungen) die Option **If assigning team members, don't notify the entire team** (Benachrichtige bei der Zuweisung einzelner Teammitglieder nicht das gesamte Team). ![Benachrichtigungen „Code review assignment" (Code-Review-Zuweisung)](/assets/images/help/teams/review-assignment-notifications.png) -11. Klicke auf **Save changes** (Änderungen speichern). +10. Optionally, to only notify the team members chosen by code review assignment for each pull review request, under "Notifications" select **If assigning team members, don't notify the entire team.** ![Code review assignment notifications](/assets/images/help/teams/review-assignment-notifications.png){% ifversion fpt or ghae or ghes > 3.2 %} +11. Optionally, to include members of child teams as potential reviewers when assigning requests, select **Child team members**. +12. Optionally, to count any members whose review has already been requested against the total number of members to assign, select **Count existing requests**. +13. Optionally, to remove the review request from the team when assigning team members, select **Team review request**.{% endif %} +14. Klicke auf **Save changes** (Änderungen speichern). ## Code-Review-Zuweisungen deaktivieren {% data reusables.profile.access_org %} diff --git a/translations/de-DE/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/de-DE/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md index dc963d100e..0f24072dcd 100644 --- a/translations/de-DE/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md +++ b/translations/de-DE/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md @@ -16,6 +16,8 @@ shortTitle: Synchronize with an IdP {% data reusables.gated-features.okta-team-sync %} +{% data reusables.enterprise-accounts.emu-scim-note %} + ## Informationen zur Teamsynchronisierung {% data reusables.identity-and-permissions.about-team-sync %} @@ -26,6 +28,8 @@ shortTitle: Synchronize with an IdP Sobald ein {% data variables.product.prodname_dotcom %}-Team mit einer IdP-Gruppe verbunden ist, muss Dein IdP-Administrator Änderungen an der Teammitgliedschaft über den Identitätsanbieter durchführen. You cannot manage team membership on {% data variables.product.product_name %}{% ifversion fpt %} or using the API{% endif %}. +{% ifversion fpt %}{% data reusables.enterprise-accounts.team-sync-override %}{% endif %} + {% ifversion fpt %} Alle über den IdP vorgenommenen Änderungen an der Teammitgliedschaft werden im Auditprotokoll von {% data variables.product.product_name %} als Änderungen des Teamsynchronisierungs-Bots angezeigt. Dein IdP wird die Daten der Teammitgliedschaft einmal pro Stunde an {% data variables.product.prodname_dotcom %} senden. Beim Verbinden eines Teams mit einer IdP-Gruppe werden unter Umständen einige Teammitglieder entfernt. Weitere Informationen findest Du unter „[Anforderungen an Mitglieder synchronisierter Teams](#requirements-for-members-of-synchronized-teams).“ {% endif %} @@ -54,8 +58,6 @@ Sobald sich das entfernte Teammitglied jedoch wieder mit SSO bei der Organisatio Um zu verhindern, dass Teammitglieder versehentlich aus einem Team entfernt werden, empfehlen wir innerhalb der Organisations oder dem Enterprise-Konto die Erzwingung des SAML SSO, die Erstellung neuer Teams zur Synchronisierung der Mitgliederdaten und die Überprüfung der IdP-Gruppenmitgliedschaften vor der Synchronisierung bestehender Teams. For more information, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)" and "[Enforcing SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account)." -Wenn Deine Organisation im Besitz eines Enterprise-Kontos ist, wird die Aktivierung der Teamsynchronisierung für das Enterprise-Konto Deine Einstellungen für die Teamsynchronisierung auf Organisationsebene überschreiben. For more information, see "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)." - {% endif %} ## Vorrausetzungen diff --git a/translations/de-DE/content/packages/learn-github-packages/installing-a-package.md b/translations/de-DE/content/packages/learn-github-packages/installing-a-package.md index 0a9d777d8d..e18cc59875 100644 --- a/translations/de-DE/content/packages/learn-github-packages/installing-a-package.md +++ b/translations/de-DE/content/packages/learn-github-packages/installing-a-package.md @@ -18,7 +18,7 @@ versions: ## About package installation -You can search {% data variables.product.prodname_dotcom %} to find packages in {% data variables.product.prodname_registry %} that you can install in your own project. For more information, see "[Searching {% data variables.product.prodname_registry %} for packages](/github/searching-for-information-on-github/searching-for-packages)." +You can search {% data variables.product.prodname_dotcom %} to find packages in {% data variables.product.prodname_registry %} that you can install in your own project. For more information, see "[Searching {% data variables.product.prodname_registry %} for packages](/search-github/searching-on-github/searching-for-packages)." After you find a package, you can read the package's description and installation and usage instructions on the package page. diff --git a/translations/de-DE/content/packages/learn-github-packages/viewing-packages.md b/translations/de-DE/content/packages/learn-github-packages/viewing-packages.md index 8d2eb4c9f6..b725281e34 100644 --- a/translations/de-DE/content/packages/learn-github-packages/viewing-packages.md +++ b/translations/de-DE/content/packages/learn-github-packages/viewing-packages.md @@ -64,4 +64,4 @@ You can find and view any package you've published across all organizations and ## Weiterführende Informationen -- "[Suche nach Paketen](/github/searching-for-information-on-github/searching-for-packages)" +- "[Suche nach Paketen](/search-github/searching-on-github/searching-for-packages)" diff --git a/translations/de-DE/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md b/translations/de-DE/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md index 2801ab45d7..f2c61c10c9 100644 --- a/translations/de-DE/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md +++ b/translations/de-DE/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md @@ -15,8 +15,6 @@ shortTitle: Publish & install with Actions {% data reusables.package_registry.packages-ghes-release-stage %} {% data reusables.package_registry.packages-ghae-release-stage %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## About {% data variables.product.prodname_registry %} with {% data variables.product.prodname_actions %} diff --git a/translations/de-DE/content/packages/quickstart.md b/translations/de-DE/content/packages/quickstart.md index 8c0f3943a6..991ea33702 100644 --- a/translations/de-DE/content/packages/quickstart.md +++ b/translations/de-DE/content/packages/quickstart.md @@ -10,8 +10,6 @@ shortTitle: Schnellstart --- {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## Einführung diff --git a/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md b/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md index 7133e426ef..f061104f6e 100644 --- a/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md +++ b/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md @@ -160,7 +160,11 @@ You can install packages from {% data variables.product.prodname_registry %} by By default, you can add packages from one organization. For more information, see "[Installing packages from other organizations](#installing-packages-from-other-organizations)." -You also need to add the *.npmrc* file to your project so all requests to install packages will go through {% data variables.product.prodname_registry %}. When you route all package requests through {% data variables.product.prodname_registry %}, you can use both scoped and unscoped packages from *npmjs.com*. Weitere Informationen finden Sie unter „[npm-scope](https://docs.npmjs.com/misc/scope) in der npm-Dokumentation. +You also need to add the *.npmrc* file to your project so that all requests to install packages will {% ifversion ghae %}be routed to{% else %}go through{% endif %} {% data variables.product.prodname_registry %}. {% ifversion fpt or ghes > 2.21 %}When you route all package requests through {% data variables.product.prodname_registry %}, you can use both scoped and unscoped packages from *npmjs.org*. For more information, see "[npm-scope](https://docs.npmjs.com/misc/scope)" in the npm documentation.{% endif %} + +{% ifversion ghae %} +By default, you can only use npm packages hosted on your enterprise, and you will not be able to use unscoped packages. For more information on package scoping, see "[npm-scope](https://docs.npmjs.com/misc/scope)" in the npm documentation. If required, {% data variables.product.prodname_dotcom %} support can enable an upstream proxy to npmjs.org. Once an upstream proxy is enabled, if a requested package isn't found on your enterprise, {% data variables.product.prodname_registry %} makes a proxy request to npmjs.org. +{% endif %} {% data reusables.package_registry.authenticate-step %} {% data reusables.package_registry.create-npmrc-owner-step %} diff --git a/translations/de-DE/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md b/translations/de-DE/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md index 732a245980..b24c9d1a98 100644 --- a/translations/de-DE/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md +++ b/translations/de-DE/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md @@ -12,7 +12,11 @@ shortTitle: Change visibility of site ## About access control for {% data variables.product.prodname_pages %} sites -If your project site is published from a private or internal repository that's owned by an organization using {% data variables.product.prodname_ghe_cloud %}, you can manage access control for the site. With access control, you can choose to publish the site publicly to anyone on the internet or privately to people with read access to your repository. A privately published site can be used to share your internal documentation or knowledge base with members of your enterprise. You cannot manage access control for an organization site. For more information about the types of {% data variables.product.prodname_pages %} sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)." +With access control for {% data variables.product.prodname_pages %}, you can restrict access to your {% data variables.product.prodname_pages %} site by publishing the site privately. A privately published site can only be accessed by people with read access to the repository the site is published from. You can use privately published sites to share your internal documentation or knowledge base with members of your enterprise. + +If your enterprise uses {% data variables.product.prodname_emus %}, all {% data variables.product.prodname_pages %} sites are privately published. For more information about {% data variables.product.prodname_emus %}, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." + +If your organization uses {% data variables.product.prodname_ghe_cloud %} without {% data variables.product.prodname_emus %}, you can choose to publish your sites privately or publicly to anyone on the internet. Access control is available for project sites that are published from a private or internal repository that are owned by the organization. You cannot manage access control for an organization site. For more information about the types of {% data variables.product.prodname_pages %} sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)." Privately published sites are available at a different subdomain than publicly published sites. This ensures that your {% data variables.product.prodname_pages %} site is secure from the moment it's published: diff --git a/translations/de-DE/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md b/translations/de-DE/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md index 508ef7ff68..898b27939e 100644 --- a/translations/de-DE/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md +++ b/translations/de-DE/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md @@ -22,6 +22,12 @@ Alle {% data variables.product.prodname_pages %}-Websites, auch Websites, die ko {% data reusables.pages.private_pages_are_public_warning %} +{% note %} + +**Note:** RFC3280 states that the maximum length of the common name should be 64 characters. Therefore, the entire domain name of your {% data variables.product.prodname_pages %} site must be less than 64 characters long for a certificate to be successfully created. + +{% endnote %} + ## HTTPS für Deine {% data variables.product.prodname_pages %}-Website erzwingen {% data reusables.pages.navigate-site-repo %} diff --git a/translations/de-DE/content/repositories/archiving-a-github-repository/archiving-repositories.md b/translations/de-DE/content/repositories/archiving-a-github-repository/archiving-repositories.md index 60349d1cfa..2f37692026 100644 --- a/translations/de-DE/content/repositories/archiving-a-github-repository/archiving-repositories.md +++ b/translations/de-DE/content/repositories/archiving-a-github-repository/archiving-repositories.md @@ -32,7 +32,7 @@ Nach der Archivierung eines Repositorys kannst Du keine Mitarbeiter oder Teams m When a repository is archived, its issues, pull requests, code, labels, milestones, projects, wiki, releases, commits, tags, branches, reactions, code scanning alerts, and comments become read-only. Um Änderungen in einem archivierten Repository vorzunehmen, musst Du das Repository zunächst aus dem Archiv herausnehmen. -Du kannst nach archivierten Repositorys suchen. Weitere Informationen findest Du unter „[Nach Repositorys suchen](/articles/searching-for-repositories/#search-based-on-whether-a-repository-is-archived).“ Weitere Informationen findest Du unter „[Nach Repositorys suchen](/articles/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)“. Weitere Informationen findest Du unter „[Nach Issues und Pull Requests suchen](/articles/searching-issues-and-pull-requests/#search-based-on-whether-a-repository-is-archived).“ +Du kannst nach archivierten Repositorys suchen. Weitere Informationen findest Du unter „[Nach Repositorys suchen](/search-github/searching-on-github/searching-for-repositories/#search-based-on-whether-a-repository-is-archived).“ Weitere Informationen findest Du unter „[Nach Repositorys suchen](/articles/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)“. Weitere Informationen finden Sie unter „[Nach Issues und Pull Requests suchen](/search-github/searching-on-github/searching-issues-and-pull-requests/#search-based-on-whether-a-repository-is-archived)“. ## Repository archivieren diff --git a/translations/de-DE/content/repositories/archiving-a-github-repository/backing-up-a-repository.md b/translations/de-DE/content/repositories/archiving-a-github-repository/backing-up-a-repository.md index 2a8f4e4be8..d487893bbe 100644 --- a/translations/de-DE/content/repositories/archiving-a-github-repository/backing-up-a-repository.md +++ b/translations/de-DE/content/repositories/archiving-a-github-repository/backing-up-a-repository.md @@ -36,7 +36,7 @@ Wenn Du ein Repository oder Wiki klonst, werden nur Git-Daten wie Projektdateien - [Projekte](/rest/reference/projects#list-repository-projects) {% endif %} -Sobald Sie {% ifversion ghes or ghae %}eine lokale Version aller Inhalte haben, die Sie sichern möchten, können Sie ein ZIP-Archiv erstellen und {% else %}Ihr Archiv heruntergeladen haben, können Sie {% endif %}es auf eine externe Festplatte kopieren und/oder auf einen Cloud-basierten Dienst wie [Google Drive](https://www.google.com/drive/) oder [Dropbox](https://www.dropbox.com/) hochladen. +Once you have {% ifversion ghes or ghae %}a local version of all the content you want to back up, you can create a zip archive and {% else %}downloaded your archive, you can {% endif %}copy it to an external hard drive and/or upload it to a cloud-based backup or storage service such as [Azure Blob Storage](https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-overview/), [Google Drive](https://www.google.com/drive/) or [Dropbox](https://www.dropbox.com/). {% ifversion fpt %} ## Backup-Tools (Sicherungswerkzeuge) von Drittanbietern diff --git a/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md index b0e55ebc31..fcea2452ef 100644 --- a/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md +++ b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md @@ -28,13 +28,13 @@ You can choose the default branch for a repository. The default branch is the ba {% endnote %} {% endif %} -{% ifversion fpt or ghes > 3.0 %} +{% ifversion fpt or ghes > 3.0 or ghae-next %} You can also rename the default branch. For more information, see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)." {% endif %} -{% ifversion fpt or ghes > 2.22 %} +{% ifversion fpt or ghes > 2.22 or ghae-next %} {% data reusables.branches.set-default-branch %} diff --git a/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md index 1344afe816..0d325c4e14 100644 --- a/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md +++ b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md @@ -5,6 +5,7 @@ permissions: People with write permissions to a repository can rename a branch i versions: fpt: '*' ghes: '>=3.1' + ghae: next topics: - Repositories redirect_from: diff --git a/translations/de-DE/content/repositories/creating-and-managing-repositories/about-repositories.md b/translations/de-DE/content/repositories/creating-and-managing-repositories/about-repositories.md index 4d7ae873ff..747f2d3574 100644 --- a/translations/de-DE/content/repositories/creating-and-managing-repositories/about-repositories.md +++ b/translations/de-DE/content/repositories/creating-and-managing-repositories/about-repositories.md @@ -74,7 +74,7 @@ All enterprise members have read permissions to the internal repository, but int {% data reusables.repositories.internal-repo-default %} -If a user is removed from all organizations owned by the enterprise, that user's forks of internal repositories are removed automatically. +Any member of the enterprise can fork any internal repository owned by an organization in the enterprise. The forked repository will belong to the member's user account, and the visibility of the fork will be private. If a user is removed from all organizations owned by the enterprise, that user's forks of internal repositories are removed automatically. {% endif %} ## Begrenzungen für die Anzeige von Inhalten und Diffs in einem Repository @@ -107,6 +107,7 @@ Die Vergleichsansicht und die Pull-Request-Seiten zeigen eine Liste mit Commits ## Weiterführende Informationen - „[Ein neues Repository erstellen](/articles/creating-a-new-repository)“ +- „[Über Forks](/github/collaborating-with-pull-requests/working-with-forks/about-forks)" - „[Mithilfe von Issues und Pull Requests zusammenarbeiten](/categories/collaborating-with-issues-and-pull-requests)“ - „[Ihre Arbeit auf {% data variables.product.prodname_dotcom %} verwalten](/categories/managing-your-work-on-github/)“ - „[Ein Repository verwalten](/categories/administering-a-repository)“ diff --git a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md index 33fea40dfb..f693f70377 100644 --- a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md +++ b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md @@ -46,18 +46,19 @@ Lisa, M., & Bot, H. (2017). My Research Software (Version 2.0.4) [Computer softw {% raw %} ``` -@misc{Lisa_My_Research_Software_2017, +@software{Lisa_My_Research_Software_2017, author = {Lisa, Mona and Bot, Hew}, doi = {10.5281/zenodo.1234}, month = {12}, title = {{My Research Software}}, url = {https://github.com/github/linguist}, + version = {2.0.4}, year = {2017} } ``` {% endraw %} -Note the example above produces a _software_ citation (i.e., `@misc` type in BibTeX rather than `@article`). +Note the example above produces a _software_ citation (i.e., `@software` type in BibTeX rather than `@article`). For more information, see the [Citation File Format](https://citation-file-format.github.io/) website. @@ -67,9 +68,15 @@ When you add a `CITATION.cff` file to the default branch of your repository, it ## Citing something other than software -If you would prefer the GitHub citation information to link to another resource such as a research paper then you can use the `preferred-citation` override in CFF. +If you would prefer the {% data variables.product.prodname_dotcom %} citation information to link to another resource such as a research article, then you can use the `preferred-citation` override in CFF with the following types. -Extended CITATION.cff file describing the software, but linking to a research paper as the preferred citation: +| Resource | Typ | +| ---------------- | ------------------ | +| Research article | `article` | +| Conference paper | `conference-paper` | +| Book | `book` | + +Extended CITATION.cff file describing the software, but linking to a research article as the preferred citation: ``` cff-version: 1.2.0 @@ -132,6 +139,10 @@ Lisa, M., & Bot, H. (2021). My awesome research software. Journal Title, 1(1), 1 ``` {% endraw %} +## Citing a dataset + +If your repository contains a dataset, you can set `type: dataset` in your `CITATION.cff` file to produce a data citation string output in the {% data variables.product.prodname_dotcom %} citation prompt. + ## Other citation files The GitHub citation feature will also detect a small number of additional files that are often used by communities and projects to describe how they would like their work to be cited. diff --git a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md index 866d0502e4..d7e3ae9135 100644 --- a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md +++ b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md @@ -29,7 +29,7 @@ Repository-Administratoren können beliebige Themen zu einem Repository hinzufü {% ifversion ghae %}Internal {% else %}Public, internal, {% endif %}and private repositories can have topics, although you will only see private repositories that you have access to in topic search results. -Du kannst nach Repositorys suchen, die mit einem bestimmten Thema verknüpft sind. Weitere Informationen finden Sie unter „[Nach Repositorys suchen](/articles/searching-for-repositories/#search-by-topic)“. Sie können auch nach einer Liste von Themen auf {% data variables.product.product_name %} suchen. Weitere Informationen findest Du unter „[Themen suchen](/articles/searching-topics).“ +Du kannst nach Repositorys suchen, die mit einem bestimmten Thema verknüpft sind. Weitere Informationen findest Du unter „[Nach Repositorys suchen](/search-github/searching-on-github/searching-for-repositories#search-by-topic).“ Sie können auch nach einer Liste von Themen auf {% data variables.product.product_name %} suchen. Weitere Informationen finden Sie unter „[Themen suchen](/search-github/searching-on-github/searching-topics)“. ## Themen zum Repository hinzufügen diff --git a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md index dfd469660e..381d8df0b2 100644 --- a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md +++ b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md @@ -73,7 +73,7 @@ Du kannst Repositorys basierend auf ihrer Lizenz oder Lizenzfamilie filtern. Ver | | Unlicense | `unlicense` | | | zLib License | `zlib` | -Wenn Du nach einer Lizenz einer Familie suchst, enthalten die Suchergebnisse alle Lizenzen dieser Familie. Wenn Du beispielsweise die Abfrage `license:gpl` verwendest, enthalten die Suchergebnisse Repositorys, die unter der GNU General Public License v2.0 und der GNU General Public License v3.0 lizenziert sind. Weitere Informationen findest Du unter „[Nach Repositorys suchen](/articles/searching-for-repositories/#search-by-license).“ +Wenn Du nach einer Lizenz einer Familie suchst, enthalten die Suchergebnisse alle Lizenzen dieser Familie. Wenn Du beispielsweise die Abfrage `license:gpl` verwendest, enthalten die Suchergebnisse Repositorys, die unter der GNU General Public License v2.0 und der GNU General Public License v3.0 lizenziert sind. Weitere Informationen findest Du unter „[Nach Repositorys suchen](/search-github/searching-on-github/searching-for-repositories/#search-by-license).“ ## Eine Lizenz erkennen diff --git a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md index 1b46138643..9861743d87 100644 --- a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md +++ b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md @@ -43,7 +43,7 @@ Alternativ kannst Du {% data variables.product.prodname_actions %} in Deinem Rep {% endif %} -{% ifversion fpt or ghes > 2.22 %} +{% ifversion fpt or ghes > 2.22 or ghae-next %} ## {% data variables.product.prodname_actions %}-Berechtigungen für Dein Repository verwalten @@ -72,14 +72,21 @@ You can disable all workflows for a repository or set a policy that configures w {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.settings-sidebar-actions %} -1. Under **Actions permissions**, select **Allow select actions** and add your required actions to the list. ![Add actions to allow list](/assets/images/help/repository/actions-policy-allow-list.png) +1. Under **Actions permissions**, select **Allow select actions** and add your required actions to the list. + {%- ifversion ghes %} + ![Add actions to allow list](/assets/images/help/repository/actions-policy-allow-list.png) + {%- else %} + ![Add actions to allow list](/assets/images/enterprise/github-ae/repository/actions-policy-allow-list.png) + {%- endif %} 2. Klicke auf **Save** (Speichern). {% endif %} {% ifversion fpt %} ## Configuring required approval for workflows from public forks -{% data reusables.actions.workflow-run-approve-public-fork %} You can configure this behavior for a repository using the procedure below. Modifying this setting overrides the configuration set at the organization or enterprise level. +{% data reusables.actions.workflow-run-approve-public-fork %} + +You can configure this behavior for a repository using the procedure below. Modifying this setting overrides the configuration set at the organization or enterprise level. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} @@ -120,6 +127,29 @@ The default permissions can also be configured in the organization settings. If 1. Click **Save** to apply the settings. {% endif %} +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## Allowing access to components in an internal repository + +{% note %} + +**Note:** {% data reusables.gated-features.internal-repos %} + +{% endnote %} + +Members of your enterprise can use internal repositories to work on projects without sharing information publicly. For information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-internal-repositories)." + +To configure whether workflows in an internal repository can be accessed from outside the repository: + +1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of the internal repository. +1. Under your repository name, click {% octicon "gear" aria-label="The gear icon" %} **Settings**. +{% data reusables.repositories.settings-sidebar-actions %} +1. Under **Access**, choose one of the access settings: ![Set the access to Actions components](/assets/images/help/settings/actions-access-settings.png) + * **Not accessible** - Workflows in other repositories can't use workflows in this repository. + * **Accessible by any repository in the organization** - Workflows in other repositories can use workflows in this repository as long as they are part of the same organization. + * **Accessible by any repository in the enterprise** - Workflows in other repositories can use workflows in this repository as long as they are part of the same enterprise. +1. Click **Save** to apply the settings. +{% endif %} + {% ifversion fpt or ghes > 2.22 or ghae %} ## Configuring the retention period for {% data variables.product.prodname_actions %} artifacts and logs in your repository diff --git a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md index e35b4638f6..88c58574f4 100644 --- a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md +++ b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md @@ -21,6 +21,12 @@ shortTitle: Repository visibility Organisationsinhaber können die Möglichkeit, die Sichtbarkeit des Repositorys zu ändern, auf Organisationsinhaber einschränken. For more information, see "[Restricting repository visibility changes in your organization](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)." +{% ifversion fpt %} + +If you're a member of an {% data variables.product.prodname_emu_enterprise %}, your repositories owned by your user account can only be private, and repositories in your enterprise's organizations can only be private or internal. + +{% endif %} + We recommend reviewing the following caveats before you change the visibility of a repository. {% ifversion ghes or ghae %} diff --git a/translations/de-DE/content/repositories/releasing-projects-on-github/about-releases.md b/translations/de-DE/content/repositories/releasing-projects-on-github/about-releases.md index 7501840e64..65bf1350cc 100644 --- a/translations/de-DE/content/repositories/releasing-projects-on-github/about-releases.md +++ b/translations/de-DE/content/repositories/releasing-projects-on-github/about-releases.md @@ -34,6 +34,9 @@ Du kannst Benachrichtigungen erhalten, wenn neue Releases in einem Repository ve Alle Personen mit Lesezugriff auf ein Repository können Releases anzeigen und vergleichen, aber nur Personen mit Schreibberechtigungen für ein Repository können Releases verwalten. Weitere Informationen findest Du unter „[Verwalten von Releases in einem Repository](/github/administering-a-repository/managing-releases-in-a-repository)." {% ifversion fpt %} + +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)." + 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](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)." {% endif %} diff --git a/translations/de-DE/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md b/translations/de-DE/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md new file mode 100644 index 0000000000..26e47f7be4 --- /dev/null +++ b/translations/de-DE/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md @@ -0,0 +1,93 @@ +--- +title: Automatically generated release notes +intro: You can automatically generate release notes for your GitHub releases +permissions: Repository collaborators and people with write access to a repository can generate and customize automated release notes for a release. +versions: + fpt: '*' +topics: + - Repositories +shortTitle: Automated release notes +--- + +{% note %} + +**Note:** {% data reusables.repositories.auto-gen-release-public-beta %} + +{% endnote %} + +## About automatically generated release notes + +Automatically generated release notes provide an automated alternative to manually writing release notes for your {% data variables.product.prodname_dotcom %} releases. With automatically generated release notes, you can quickly generate an overview of the contents of a release. You can also customize your automated release notes, using labels to create custom categories to organize pull requests you want to include, and exclude certain labels and users from appearing in the output. + +## Creating automatically generated release notes for a new release + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.releases %} +3. Klicke auf **Draft a new release** (Einen neuen Release entwerfen). ![Schaltfläche für Release-Entwurf](/assets/images/help/releases/draft_release_button.png) +4. {% ifversion fpt %}Click **Choose a tag** and type{% else %}Type{% endif %} a version number for your release. Alternatively, select an existing tag. + {% ifversion fpt %} + ![Enter a tag](/assets/images/help/releases/releases-tag-create.png) +5. If you are creating a new tag, click **Create new tag**. ![Confirm you want to create a new tag](/assets/images/help/releases/releases-tag-create-confirm.png) + {% else %} + ![Tag-Version für Release](/assets/images/enterprise/releases/releases-tag-version.png) +{% endif %} +6. If you have created a new tag, use the drop-down menu to select the branch that contains the project you want to release. + {% ifversion fpt %}![Choose a branch](/assets/images/help/releases/releases-choose-branch.png) + {% else %}![Tag-Branch für Releases](/assets/images/enterprise/releases/releases-tag-branch.png) + {% endif %} +7. To the top right of the description text box, click **Auto-generate release notes**. ![Auto-generate release notes](/assets/images/help/releases/auto-generate-release-notes.png) +8. Check the generated notes to ensure they include all (and only) the information you want to include. +9. Um optional binäre Dateien wie kompilierte Programme in Deinen Release einzubinden, ziehe die Dateien mit Drag-and-Drop herüber oder wähle die Dateien manuell im Feld für Binärdateien. ![DMG mit dem Release bereitstellen](/assets/images/help/releases/releases_adding_binary.gif) +10. Um Benutzer darüber zu informieren, dass der Release nicht produktionsbereit und möglicherweise instabil ist, wähle **This is a pre-release** (Dies ist eine Vorabversion). ![Kontrollkästchen für die Markierung eines Release als Vorab-Release](/assets/images/help/releases/prerelease_checkbox.png) +{%- ifversion fpt %} +11. Optionally, select **Create a discussion for this release**, then select the **Category** drop-down menu and click a category for the release discussion. ![Checkbox to create a release discussion and drop-down menu to choose a category](/assets/images/help/releases/create-release-discussion.png) +{%- endif %} +12. Wenn Du Deinen Release publizieren möchtest, klicke auf **Publish release** (Release publizieren). Um den Release später zu bearbeiten, klicke auf **Save draft** (Entwurf speichern). ![Schaltfläche „Publish release“ (Veröffentlichung veröffentlichen) und Schaltfläche zum Speichern als Entwurf](/assets/images/help/releases/release_buttons.png) + + +## Creating a template for automatically generated release notes + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.files.add-file %} +3. In the file name field, type `.github/release.yml` to create the `release.yml` file in the `.github` directory. ![Create new file](/assets/images/help/releases/release-yml.png) +4. In the file, specify the pull request labels and authors you want to exclude from this release. You can also create new categories and list the pull request labels to be included in each of them. For more information, see "[Managing labels](/issues/using-labels-and-milestones-to-track-work/managing-labels)." + +## Example configuration + +{% raw %} +**release.yml** +```yaml{:copy} +# release.yml + +changelog: + exclude: + labels: + - ignore-for-release + authors: + - octocat + categories: + - title: Breaking Changes 🛠 + labels: + - Semver-Major + - breaking-change + - title: Exciting New Features 🎉 + labels: + - Semver-Minor + - enhancement + - title: Other Changes + labels: + - "*" +``` +{% endraw %} + +## Release template syntax + +| Parameter | Beschreibung | Erforderlich | Wert | +|:-------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:---------------------------------------------------------------------------- |:------------------------------------------------------------------------- | +| `changelog` | Defines the contents within it as the custom template for your release notes. | Erforderlich. | No value accepted. | +| `ausschließen` | Creates a category of pull requests to be excluded from the release. Can be set at the top-level of the changelog to apply to all categories or applied on a per-category basis. | Optional | No value accepted. | +| `authors` | Specifies authors to be excluded from the release. | Optional for `exclude` category. | Accepts usernames and bots as values. | +| `kategorien` | Defines the nested contents as custom categories to be included in the template. | Optional | No value accepted. | +| `title` | Creates an individual category. | Required if `categories` parameter exists. | Takes the category name as its value. | +| `labels` | Specifies labels to be used by the enclosing category. | Required if `categories` parameter exists, optional for `exclude` parameter. | Accepts any labels, whether currently existing or planned for the future. | +| `"*"` | Catchall for any pull request not included within a category *above*. If used, it must be added at the end of the file. | Optional | No value accepted. | diff --git a/translations/de-DE/content/repositories/releasing-projects-on-github/index.md b/translations/de-DE/content/repositories/releasing-projects-on-github/index.md index 7cb4c8fecf..0e2e6c36e8 100644 --- a/translations/de-DE/content/repositories/releasing-projects-on-github/index.md +++ b/translations/de-DE/content/repositories/releasing-projects-on-github/index.md @@ -17,6 +17,7 @@ children: - /viewing-your-repositorys-releases-and-tags - /linking-to-releases - /comparing-releases + - /automatically-generated-release-notes - /automation-for-release-forms-with-query-parameters shortTitle: Release projects --- diff --git a/translations/de-DE/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md b/translations/de-DE/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md index b9b154ec74..1500e40017 100644 --- a/translations/de-DE/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md +++ b/translations/de-DE/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md @@ -42,14 +42,14 @@ You can choose whether {% data variables.large_files.product_name_long %} ({% da {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.releases %} 3. Klicke auf **Draft a new release** (Einen neuen Release entwerfen). ![Schaltfläche für Release-Entwurf](/assets/images/help/releases/draft_release_button.png) -4. {% ifversion fpt %}Click **Choose a tag** and type{% else %}Type{% endif %} a version number for your release. +4. {% ifversion fpt %}Click **Choose a tag** and type{% else %}Type{% endif %} a version number for your release. Alternatively, select an existing tag. {% ifversion fpt %} ![Enter a tag](/assets/images/help/releases/releases-tag-create.png) -1. Click **Create new tag**. ![Confirm you want to create a new tag](/assets/images/help/releases/releases-tag-create-confirm.png) +1. If you are creating a new tag, click **Create new tag**. ![Confirm you want to create a new tag](/assets/images/help/releases/releases-tag-create-confirm.png) {% else %} ![Tag-Version für Release](/assets/images/enterprise/releases/releases-tag-version.png) {% endif %} -5. Benutze des Dropdownmenü um den Branch zu wählen, der das Projekt enthält, das Du freigeben willst. +5. If you have created a new tag, use the drop-down menu to select the branch that contains the project you want to release. {% ifversion fpt %}![Choose a branch](/assets/images/help/releases/releases-choose-branch.png) {% else %}![Tag-Branch für Releases](/assets/images/enterprise/releases/releases-tag-branch.png) {% endif %} @@ -57,7 +57,9 @@ You can choose whether {% data variables.large_files.product_name_long %} ({% da {%- ifversion fpt or ghes > 3.2 or ghae-issue-4972 %} If you @mention any {% data variables.product.product_name %} users in the description, the published release will include a **Contributors** section with an avatar list of all the mentioned users. {%- endif %} - ![Beschreibung der Releases](/assets/images/help/releases/releases_description.png) + {% ifversion fpt %} Alternatively, you can automatically generate your release notes by clicking **Auto-generate release notes**. + {% endif %} + ![Beschreibung der Releases](/assets/images/help/releases/releases_description_auto.png) 7. Um optional binäre Dateien wie kompilierte Programme in Deinen Release einzubinden, ziehe die Dateien mit Drag-and-Drop herüber oder wähle die Dateien manuell im Feld für Binärdateien. ![DMG mit dem Release bereitstellen](/assets/images/help/releases/releases_adding_binary.gif) 8. Um Benutzer darüber zu informieren, dass der Release nicht produktionsbereit und möglicherweise instabil ist, wähle **This is a pre-release** (Dies ist eine Vorabversion). ![Kontrollkästchen für die Markierung eines Release als Vorab-Release](/assets/images/help/releases/prerelease_checkbox.png) {%- ifversion fpt %} diff --git a/translations/de-DE/content/repositories/working-with-files/using-files/working-with-non-code-files.md b/translations/de-DE/content/repositories/working-with-files/using-files/working-with-non-code-files.md index 7a692bc9f0..6d2dc1170e 100644 --- a/translations/de-DE/content/repositories/working-with-files/using-files/working-with-non-code-files.md +++ b/translations/de-DE/content/repositories/working-with-files/using-files/working-with-non-code-files.md @@ -188,6 +188,14 @@ Zum Anzeigen der im Zuge eines Commits vorgenommenen Änderungen an einem Dokume ![Änderungen an gerendertem Fließtext](/assets/images/help/repository/rendered_prose_changes.png) +{% ifversion fpt or ghes > 3.2 or ghae-issue-5232 %} + +### Disabling Markdown rendering + +{% data reusables.repositories.disabling-markdown-rendering %} + +{% endif %} + ### Attributänderungen visualisieren Zu Attributänderungen, die im Gegensatz zu Worten im gerenderten Dokument nicht sichtbar werden, geben wir gerne einen Toolhinweis. Beispielsweise erhältst Du bei der Änderung einer Link-URL von einer Website zu einer anderen einen Toolhinweis wie diesen: diff --git a/translations/de-DE/content/rest/guides/getting-started-with-the-rest-api.md b/translations/de-DE/content/rest/guides/getting-started-with-the-rest-api.md index 1387bb0628..321880e145 100644 --- a/translations/de-DE/content/rest/guides/getting-started-with-the-rest-api.md +++ b/translations/de-DE/content/rest/guides/getting-started-with-the-rest-api.md @@ -122,10 +122,10 @@ $ curl -i -u your_username {% data variables.product.api_url_pre %}/use When prompted, you can enter your OAuth token, but we recommend you set up a variable for it: -You can use `-u "username:$token"` and set up a variable for `token` to avoid leaving your token in shell history, which should be avoided. +You can use `-u "your_username:$token"` and set up a variable for `token` to avoid leaving your token in shell history, which should be avoided. ```shell -$ curl -i -u username:$token {% data variables.product.api_url_pre %}/users/octocat +$ curl -i -u your_username:$token {% data variables.product.api_url_pre %}/users/octocat ``` diff --git a/translations/de-DE/content/rest/overview/api-previews.md b/translations/de-DE/content/rest/overview/api-previews.md index c94c5a4402..7e5cc9e731 100644 --- a/translations/de-DE/content/rest/overview/api-previews.md +++ b/translations/de-DE/content/rest/overview/api-previews.md @@ -18,13 +18,7 @@ During the preview period, we may change some features based on developer feedba To access an API preview, you'll need to provide a custom [media type](/rest/overview/media-types) in the `Accept` header for your requests. Feature documentation for each preview specifies which custom media type to provide. -{% ifversion fpt %} -## Migrations - -Allows you to download repositories from your GitHub user or organization account to review, backup, and [migrate](/rest/reference/migrations) data to {% data variables.product.prodname_ghe_server %}. - -**Custom media type:** `wyandotte-preview` **Announced:** [2018-05-24](https://developer.github.com/changes/2018-05-24-user-migration-api/) -{% endif %} +{% ifversion ghes < 3.3 %} ## Enhanced deployments @@ -32,18 +26,28 @@ Exercise greater control over [deployments](/rest/reference/repos#deployments) w **Custom media type:** `ant-man-preview` **Announced:** [2016-04-06](https://developer.github.com/changes/2016-04-06-deployment-and-deployment-status-enhancements/) +{% endif %} + +{% ifversion ghes < 3.3 %} + ## Reactions Manage [reactions](/rest/reference/reactions) for commits, issues, and comments. **Custom media type:** `squirrel-girl-preview` **Announced:** [2016-05-12](https://developer.github.com/changes/2016-05-12-reactions-api-preview/) **Update:** [2016-06-07](https://developer.github.com/changes/2016-06-07-reactions-api-update/) +{% endif %} + +{% ifversion ghes < 3.3 %} + ## Timeline Get a [list of events](/rest/reference/issues#timeline) for an issue or pull request. **Custom media type:** `mockingbird-preview` **Announced:** [2016-05-23](https://developer.github.com/changes/2016-05-23-timeline-preview-api/) +{% endif %} + {% ifversion ghes %} ## Pre-receive environments @@ -52,11 +56,13 @@ Create, list, update, and delete environments for pre-receive hooks. **Custom media type:** `eye-scream-preview` **Announced:** [2015-07-29](/rest/reference/enterprise-admin#pre-receive-environments) {% endif %} +{% ifversion ghes < 3.3 %} ## Projekte Manage [projects](/rest/reference/projects). **Custom media type:** `inertia-preview` **Announced:** [2016-09-14](https://developer.github.com/changes/2016-09-14-projects-api/) **Update:** [2016-10-27](https://developer.github.com/changes/2016-10-27-changes-to-projects-api/) +{% endif %} ## Commit search @@ -70,12 +76,16 @@ View a list of [repository topics](/articles/about-topics/) in [calls](/rest/ref **Custom media type:** `mercy-preview` **Announced:** [2017-01-31](https://github.com/blog/2309-introducing-topics) +{% ifversion ghes < 3.3 %} + ## Codes of conduct View all [codes of conduct](/rest/reference/codes-of-conduct) or get which code of conduct a repository has currently. **Custom media type:** `scarlet-witch-preview` +{% endif %} + {% ifversion ghae or ghes %} ## Global webhooks @@ -93,12 +103,16 @@ You can now use the API to manage the setting for [requiring signed commits on p **Custom media type:** `zzzax-preview` **Announced:** [2018-02-22](https://developer.github.com/changes/2018-02-22-protected-branches-required-signatures) +{% ifversion ghes < 3.3 %} + ## Require multiple approving reviews You can now [require multiple approving reviews](/rest/reference/repos#branches) for a pull request using the API. **Custom media type:** `luke-cage-preview` **Announced:** [2018-03-16](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews) +{% endif %} + {% ifversion ghes < 3.0 %} ## Check runs and check suites API @@ -135,30 +149,42 @@ GitHub App Manifests allow people to create preconfigured GitHub Apps. See "[Cre {% endif %} +{% ifversion ghes < 3.3 %} + ## Deployment statuses You can now update the `environment` of a [deployment status](/rest/reference/repos#create-a-deployment-status) and use the `in_progress` and `queued` states. When you create deployment statuses, you can now use the `auto_inactive` parameter to mark old `production` deployments as `inactive`. **Custom media type:** `flash-preview` **Announced:** [2018-10-16](https://developer.github.com/changes/2018-10-16-deployments-environments-states-and-auto-inactive-updates/) +{% endif %} + +{% ifversion ghes < 3.3 %} + ## Repository creation permissions You can now configure whether organization members can create repositories and which types of repositories they can create. See "[Update an organization](/rest/reference/orgs#update-an-organization)" for more details. **Custom media types:** `surtur-preview` **Announced:** [2019-12-03](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/) +{% endif %} + ## Inhaltsanhänge You can now provide more information in GitHub for URLs that link to registered domains by using the {% data variables.product.prodname_unfurls %} API. See "[Using content attachments](/apps/using-content-attachments/)" for more details. **Custom media types:** `corsair-preview` **Announced:** [2018-12-10](https://developer.github.com/changes/2018-12-10-content-attachments-api/) +{% ifversion ghes < 3.3 %} + ## Enable and disable Pages You can use the new endpoints in the [Pages API](/rest/reference/repos#pages) to enable or disable Pages. To learn more about Pages, see "[GitHub Pages Basics](/categories/github-pages-basics)". **Custom media types:** `switcheroo-preview` **Announced:** [2019-03-14](https://developer.github.com/changes/2019-03-14-enabling-disabling-pages/) +{% endif %} + {% ifversion ghes < 3.3 %} ## List branches or pull requests for a commit @@ -169,11 +195,7 @@ You can use two new endpoints in the [Commits API](/rest/reference/repos#commits {% endif %} -## Enable or disable vulnerability alerts for a repository - -You can use two new endpoints in the [Repos API](/rest/reference/repos) to enable or disable vulnerability alerts. - -**Custom media types:** `dorian-preview` **Announced:** [2019-04-24](https://developer.github.com/changes/2019-04-24-vulnerability-alerts/) +{% ifversion ghes < 3.3 %} ## Update a pull request branch @@ -181,12 +203,6 @@ You can use a new endpoint to [update a pull request branch](/rest/reference/pul **Custom media types:** `lydian-preview` **Announced:** [2019-05-29](https://developer.github.com/changes/2019-05-29-update-branch-api/) -{% ifversion fpt %} -## Enable or disable automated security fixes - -You can use a new set of endpoints to [enable and disable automated security fixes](/rest/reference/repos#enable-automated-security-fixes). - -**Custom media types:** `london-preview` **Announced:** [2019-06-04](https://developer.github.com/changes/2019-06-04-automated-security-fixes/) {% endif %} ## Create and use repository templates @@ -195,7 +211,8 @@ You can use a new endpoint to [Create a repository using a template](/rest/refer **Custom media types:** `baptiste-preview` **Announced:** [2019-07-05](https://developer.github.com/changes/2019-07-16-repository-templates-api/) -{% ifversion fpt or ghes or ghae %} +{% ifversion ghes < 3.3 %} + ## New visibility parameter for the Repositories API You can set and retrieve the visibility of a repository in the [Repositories API](/rest/reference/repos). diff --git a/translations/de-DE/content/rest/overview/troubleshooting.md b/translations/de-DE/content/rest/overview/troubleshooting.md index d53753da35..3b4f59e10b 100644 --- a/translations/de-DE/content/rest/overview/troubleshooting.md +++ b/translations/de-DE/content/rest/overview/troubleshooting.md @@ -62,6 +62,10 @@ curl -u my_username:my_password -X POST "https://api.github.com/authorizations" Then you must switch to the [web application flow](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) to generate access tokens. +## Timeouts + +If {% data variables.product.product_name %} takes more than 10 seconds to process an API request, {% data variables.product.product_name %} will terminate the request and you will receive a timeout response. + {% endif %} [oap-guide]: https://developer.github.com/changes/2015-01-19-an-integrators-guide-to-organization-application-policies/ diff --git a/translations/de-DE/content/rest/reference/actions.md b/translations/de-DE/content/rest/reference/actions.md index abb45568d9..782a78e445 100644 --- a/translations/de-DE/content/rest/reference/actions.md +++ b/translations/de-DE/content/rest/reference/actions.md @@ -12,7 +12,6 @@ topics: miniTocMaxHeadingLevel: 3 --- -{% data reusables.actions.ae-beta %} The {% data variables.product.prodname_actions %} API enables you to manage {% data variables.product.prodname_actions %} using the REST API. {% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} require the permissions mentioned in each endpoint. For more information, see "[{% data variables.product.prodname_actions %} Documentation](/actions)." @@ -22,8 +21,6 @@ The {% data variables.product.prodname_actions %} API enables you to manage {% d ## Artifacts -{% data reusables.actions.ae-beta %} - The Artifacts API allows you to download, delete, and retrieve information about workflow artifacts. {% data reusables.actions.about-artifacts %} For more information, see "[Persisting workflow data using artifacts](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)." {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %} @@ -35,8 +32,6 @@ The Artifacts API allows you to download, delete, and retrieve information about {% ifversion fpt or ghes > 2.22 or ghae %} ## Permissions -{% data reusables.actions.ae-beta %} - The Permissions API allows you to set permissions for what organizations and repositories are allowed to run {% data variables.product.prodname_actions %}, and what actions are allowed to run. For more information, see "[Usage limits, billing, and administration](/actions/reference/usage-limits-billing-and-administration#disabling-or-limiting-github-actions-for-your-repository-or-organization)." You can also set permissions for an enterprise. For more information, see the "[{% data variables.product.prodname_dotcom %} Enterprise administration](/rest/reference/enterprise-admin#github-actions)" REST API. @@ -48,8 +43,6 @@ You can also set permissions for an enterprise. For more information, see the "[ ## Secrets -{% data reusables.actions.ae-beta %} - The Secrets API lets you create, update, delete, and retrieve information about encrypted secrets. {% data reusables.actions.about-secrets %} For more information, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)." {% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `secrets` permission to use this API. Authenticated users must have collaborator access to a repository to create, update, or read secrets. @@ -60,7 +53,6 @@ The Secrets API lets you create, update, delete, and retrieve information about ## Selbst-gehostete Runner -{% data reusables.actions.ae-beta %} {% data reusables.actions.ae-self-hosted-runners-notice %} The Self-hosted Runners API allows you to register, view, and delete self-hosted runners. {% data reusables.actions.about-self-hosted-runners %} Weitere Informationenfindest Du unter „[Deinen eigenen Runner hosten](/actions/hosting-your-own-runners)“. @@ -75,7 +67,6 @@ You can manage self-hosted runners for an enterprise. For more information, see ## Self-hosted runner groups -{% data reusables.actions.ae-beta %} {% data reusables.actions.ae-self-hosted-runners-notice %} The Self-hosted Runners Groups API allows you manage groups of self-hosted runners. 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)." @@ -90,8 +81,6 @@ You can manage self-hosted runner groups for an enterprise. For more information ## Workflows -{% data reusables.actions.ae-beta %} - The Workflows API allows you to view workflows for a repository. {% data reusables.actions.about-workflows %} For more information, see "[Automating your workflow with GitHub Actions](/actions/automating-your-workflow-with-github-actions)." {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %} @@ -102,8 +91,6 @@ The Workflows API allows you to view workflows for a repository. {% data reusabl ## Workflow jobs -{% data reusables.actions.ae-beta %} - The Workflow Jobs API allows you to view logs and workflow jobs. {% data reusables.actions.about-workflow-jobs %} For more information, see "[Workflow syntax for GitHub Actions](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)". {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %} @@ -114,8 +101,6 @@ The Workflow Jobs API allows you to view logs and workflow jobs. {% data reusabl ## Workflow runs -{% data reusables.actions.ae-beta %} - The Workflow Runs API allows you to view, re-run, cancel, and view logs for workflow runs. {% data reusables.actions.about-workflow-runs %} For more information, see "[Managing a workflow run](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)." {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %} diff --git a/translations/de-DE/content/rest/reference/activity.md b/translations/de-DE/content/rest/reference/activity.md index 46360fffb2..29c13256d1 100644 --- a/translations/de-DE/content/rest/reference/activity.md +++ b/translations/de-DE/content/rest/reference/activity.md @@ -145,6 +145,7 @@ Here's a list of potential `reason`s for receiving a notification: | `assign` | You were assigned to the issue. | | `Autor` | You created the thread. | | `kommentieren` | You commented on the thread. | +| `ci_activity` | A {% data variables.product.prodname_actions %} workflow run that you triggered was completed. | | `Einladung` | You accepted an invitation to contribute to the repository. | | `manual` | You subscribed to the thread (via an issue or pull request). | | `erwähnen` | You were specifically **@mentioned** in the content. | diff --git a/translations/de-DE/content/rest/reference/enterprise-admin.md b/translations/de-DE/content/rest/reference/enterprise-admin.md index 57c1aedddc..53d956e265 100644 --- a/translations/de-DE/content/rest/reference/enterprise-admin.md +++ b/translations/de-DE/content/rest/reference/enterprise-admin.md @@ -81,7 +81,6 @@ The current version of your enterprise is returned in the response header of eve ## GitHub Actions -{% data reusables.actions.ae-beta %} {% for operation in currentRestOperations %} {% if operation.subcategory == 'actions' %}{% include rest_operation %}{% endif %} diff --git a/translations/de-DE/content/rest/reference/projects.md b/translations/de-DE/content/rest/reference/projects.md index ec38a94880..cec0c3e049 100644 --- a/translations/de-DE/content/rest/reference/projects.md +++ b/translations/de-DE/content/rest/reference/projects.md @@ -1,6 +1,6 @@ --- title: Projekte -intro: 'The Projects API lets you to create, list, update, delete and customize projects in a repository.' +intro: 'The Projects API lets you create, list, update, delete and customize projects in a repository.' redirect_from: - /v3/projects versions: diff --git a/translations/de-DE/content/rest/reference/repos.md b/translations/de-DE/content/rest/reference/repos.md index e39a6102ab..f63626c662 100644 --- a/translations/de-DE/content/rest/reference/repos.md +++ b/translations/de-DE/content/rest/reference/repos.md @@ -175,7 +175,7 @@ You can communicate that a transient environment no longer exists by setting its {% ifversion fpt or ghes > 3.1 or ghae-next %} ## Environments -The Environments API allows you to create, configure, and delete environments. For more information about environments, see "[Environments](/actions/reference/environments)." To manage environment secrets, see "[Secrets](/rest/reference/actions#secrets)." +The Environments API allows you to create, configure, and delete environments. For more information about environments, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." To manage environment secrets, see "[Secrets](/rest/reference/actions#secrets)." {% for operation in currentRestOperations %} {% if operation.subcategory == 'environments' %}{% include rest_operation %}{% endif %} diff --git a/translations/de-DE/content/rest/reference/scim.md b/translations/de-DE/content/rest/reference/scim.md index ac6b9934aa..ae8c8b3305 100644 --- a/translations/de-DE/content/rest/reference/scim.md +++ b/translations/de-DE/content/rest/reference/scim.md @@ -16,7 +16,9 @@ The SCIM API is used by SCIM-enabled Identity Providers (IdPs) to automate provi {% note %} -**Note:** The SCIM API is available only to organizations on [{% data variables.product.prodname_ghe_cloud %}](/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts) with [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) enabled. {% data reusables.scim.enterprise-account-scim %} For more information about SCIM, see "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)." +**Hinweise:** + - The SCIM API is available only to organizations on [{% data variables.product.prodname_ghe_cloud %}](/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts) with [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) enabled. {% data reusables.scim.enterprise-account-scim %} For more information about SCIM, see "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)." + - The SCIM API cannot be used with {% data variables.product.prodname_emus %}. {% endnote %} diff --git a/translations/de-DE/content/rest/reference/search.md b/translations/de-DE/content/rest/reference/search.md index b6a59ef37f..d8e8bfdecc 100644 --- a/translations/de-DE/content/rest/reference/search.md +++ b/translations/de-DE/content/rest/reference/search.md @@ -50,7 +50,7 @@ GitHub Octocat in:readme user:defunkt const queryString = 'q=' + encodeURIComponent('GitHub Octocat in:readme user:defunkt'); ``` -See "[Searching on GitHub](/articles/searching-on-github/)" for a complete list of available qualifiers, their format, and an example of how to use them. For information about how to use operators to match specific quantities, dates, or to exclude results, see "[Understanding the search syntax](/articles/understanding-the-search-syntax/)." +See "[Searching on GitHub](/articles/searching-on-github/)" for a complete list of available qualifiers, their format, and an example of how to use them. For information about how to use operators to match specific quantities, dates, or to exclude results, see "[Understanding the search syntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax/)." ### Einschränkungen der Abfragelänge diff --git a/translations/de-DE/content/rest/reference/teams.md b/translations/de-DE/content/rest/reference/teams.md index abfc96b233..a8fcdbbae8 100644 --- a/translations/de-DE/content/rest/reference/teams.md +++ b/translations/de-DE/content/rest/reference/teams.md @@ -58,6 +58,12 @@ The Team Synchronization API allows you to manage connections between {% data va You can manage GitHub team members through your IdP with team synchronization. Team synchronization must be enabled to use the Team Synchronization API. For more information, see "Synchronizing teams between your identity provider and GitHub." +{% note %} + +**Note:** The Team Synchronization API cannot be used with {% data variables.product.prodname_emus %}. + +{% endnote %} + {% for operation in currentRestOperations %} {% if operation.subcategory == 'team-sync' %}{% include rest_operation %}{% endif %} {% endfor %} diff --git a/translations/de-DE/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md b/translations/de-DE/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md new file mode 100644 index 0000000000..6fa18c288e --- /dev/null +++ b/translations/de-DE/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md @@ -0,0 +1,90 @@ +--- +title: Informationen zur Suche auf GitHub +intro: 'Our integrated search covers the many repositories, users, and lines of code on {% data variables.product.product_name %}.' +redirect_from: + - /articles/using-the-command-bar/ + - /articles/github-search-basics/ + - /articles/search-basics/ + - /articles/searching-github/ + - /articles/advanced-search/ + - /articles/about-searching-on-github + - /github/searching-for-information-on-github/about-searching-on-github + - /github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +{% data reusables.search.you-can-search-globally %} + +- Um global über {% data variables.product.product_name %} hinweg zu suchen, gib Deine Suchanfrage in das Suchfeld oben auf jeder Seite ein, und wähle im im Dropdownmenü der Suche „All {% data variables.product.prodname_dotcom %}“ (Ganzes Produkt). +- Um in einem bestimmten Repository oder einer bestimmten Organisation zu suchen, navigiere zur Repository- oder Organisationsseite, gib Deine Suchanfrage in das Suchfeld oben auf der Seite ein, und drücke die **Eingabetaste**. + +{% note %} + +**Hinweise:** + +{% ifversion fpt or ghes %} +- {% data reusables.search.required_login %}{% endif %} +- {% data variables.product.prodname_pages %}-Websites können auf {% data variables.product.product_name %} nicht durchsucht werden. Du kannst aber den Quellinhalt mithilfe der Codesuche durchsuchen, wenn er im Standardbranch eines Repositorys vorhanden ist. Weitere Informationen findest Du unter „[Code durchsuchen](/search-github/searching-on-github/searching-code)“. Weitere Informationen über {% data variables.product.prodname_pages %} findest Du unter „[Was ist GitHub Pages?](/articles/what-is-github-pages/)“ +- Currently our search doesn't support exact matching. +- Whenever you are searching in code files, only the first two results in each file will be returned. + +{% endnote %} + +Nach einer Suche auf {% data variables.product.product_name %} können Sie die Ergebnisse sortieren oder durch Anklicken einer der Sprachen in der Seitenleiste weiter eingrenzen. Weitere Informationen finden Sie unter „[Suchergebnisse sortieren](/search-github/getting-started-with-searching-on-github/sorting-search-results)“. + +Bei der {% data variables.product.product_name %}-Suche wird ein ElasticSearch-Cluster verwendet, um Projekte jedes Mal zu indizieren, wenn eine Änderung an {% data variables.product.product_name %} gepusht wird. Issues und Pull Requests werden beim Anlegen oder Ändern indiziert. + +## Arten von Suchen auf {% data variables.product.prodname_dotcom %} + +You can search for the following information across all repositories you can access on {% data variables.product.product_location %}. + +- [Repositorys](/search-github/searching-on-github/searching-for-repositories) +- [Themen](/search-github/searching-on-github/searching-topics) +- [Issues and pull requests](/search-github/searching-on-github/searching-issues-and-pull-requests){% ifversion fpt %} +- [Discussions](/search-github/searching-on-github/searching-discussions){% endif %} +- [Code](/search-github/searching-on-github/searching-code) +- [Commits](/search-github/searching-on-github/searching-commits) +- [Benutzer](/search-github/searching-on-github/searching-users) +- [Packages](/search-github/searching-on-github/searching-for-packages) +- [Wikis](/search-github/searching-on-github/searching-wikis) + +## Über eine visuelle Oberfläche suchen + +Alternativ können Sie {% data variables.product.product_name %} mit der {% data variables.search.search_page_url %} oder {% data variables.search.advanced_url %} durchsuchen. + +Die {% data variables.search.advanced_url %} bietet eine visuelle Oberfläche zum Erstellen von Suchanfragen. Sie können Ihre Suchanfragen nach einer Vielzahl von Faktoren filtern, beispielsweise nach der Anzahl der Sterne oder der Anzahl der Forks eines Repositorys. Wenn Sie die erweiterten Suchfelder ausfüllen, wird Ihre Anfrage automatisch in der oberen Suchleiste erstellt. + +![Erweiterte Suche](/assets/images/help/search/advanced_search_demo.gif) + +{% ifversion fpt or ghes or ghae-next %} + +## Searching repositories on {% data variables.product.prodname_dotcom_the_website %} from your private enterprise environment + +If you use {% ifversion fpt %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae-next %} or {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} and you're a member of a {% data variables.product.prodname_dotcom_the_website %} organization using {% data variables.product.prodname_ghe_cloud %}, an enterprise owner for your {% data variables.product.prodname_enterprise %} environment can enable {% data variables.product.prodname_github_connect %} so that you can search across both environments at the same time{% ifversion ghes or ghae %} from {% data variables.product.product_name %}{% endif %}. For more information, see the following. + +{% ifversion fpt or ghes %} +- "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/{% ifversion ghes %}{{ currentVersion }}{% else %}github-enterprise@latest{% endif %}/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_server %} documentation{% endif %}{% ifversion ghae-next %} +- "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/github-ae@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_managed %} documentation +{% endif %} + +{% ifversion ghes or ghae-next %} + +Um Deine Suche nach Umgebung einzugrenzen, kannst Du eine Filteroption in der {% data variables.search.advanced_url %} oder das Suchpräfix `environment:` verwenden. Um nur nach Inhalten auf {% data variables.product.product_name %} zu suchen, verwenden Sie die Suchsyntax `environment:local`. Um nur nach Inhalten auf {% data variables.product.prodname_dotcom_the_website %} zu suchen, verwende die Suchsyntax `environment:github`. + +Your enterprise owner on {% data variables.product.product_name %} can enable {% data variables.product.prodname_unified_search %} for all public repositories, all private repositories, or only certain private repositories in the connected {% data variables.product.prodname_ghe_cloud %} organization. + +When you search from {% data variables.product.product_name %}, you can only search in the private repositories that you have access to in the connected {% data variables.product.prodname_dotcom_the_website %} organization. Enterprise owners for {% data variables.product.product_name %} and organization owners on {% data variables.product.prodname_dotcom_the_website %} cannot search private repositories owned by your account on {% data variables.product.prodname_dotcom_the_website %}. To search the applicable private repositories, you must enable private repository search for your personal accounts on {% data variables.product.product_name %}. For more information, see "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment)." + +{% endif %} + +{% endif %} + +## Weiterführende Informationen + +- „[Grundlagen der Suchsyntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)“ +- „[Suche auf GitHub](/articles/searching-on-github)“ diff --git a/translations/de-DE/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md b/translations/de-DE/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md new file mode 100644 index 0000000000..e7d2f5d0b7 --- /dev/null +++ b/translations/de-DE/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md @@ -0,0 +1,54 @@ +--- +title: Enabling GitHub.com repository search from your private enterprise environment +shortTitle: Search GitHub.com from enterprise +intro: 'You can connect your personal accounts on {% data variables.product.prodname_dotcom_the_website %} and your private {% data variables.product.prodname_enterprise %} environment to search for content in certain {% data variables.product.prodname_dotcom_the_website %} repositories{% ifversion fpt %} from your private environment{% else %} from {% data variables.product.product_name %}{% endif %}.' +redirect_from: + - /articles/enabling-private-githubcom-repository-search-in-your-github-enterprise-account/ + - /articles/enabling-private-github-com-repository-search-in-your-github-enterprise-server-account/ + - /articles/enabling-private-githubcom-repository-search-in-your-github-enterprise-server-account/ + - /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 +versions: + fpt: '*' + ghes: '*' + ghae: next +topics: + - GitHub search +--- + +## About search for {% data variables.product.prodname_dotcom_the_website %} repositories from {% ifversion fpt %}your private enterprise environment{% else %}{% data variables.product.product_name %}{% endif %} + +You can search for designated private repositories on {% data variables.product.prodname_ghe_cloud %} from {% ifversion fpt %}your private {% data variables.product.prodname_enterprise %} environment{% else %}{% data variables.product.product_location %}{% ifversion ghae %} on {% data variables.product.prodname_ghe_managed %}{% endif %}{% endif %}. {% ifversion fpt %}For example, if you use {% data variables.product.prodname_ghe_server %}, you can search for private repositories from your enterprise from {% data variables.product.prodname_ghe_cloud %} in the web interface for {% data variables.product.prodname_ghe_server %}.{% endif %} + +## Vorrausetzungen + +- An enterprise owner for {% ifversion fpt %}your private {% data variables.product.prodname_enterprise %} environment{% else %}{% data variables.product.product_name %}{% endif %} must enable {% data variables.product.prodname_github_connect %} and {% data variables.product.prodname_unified_search %} for private repositories. For more information, see the following.{% ifversion fpt or ghes %} + - "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/{% ifversion ghes %}{{ currentVersion }}{% else %}github-enterprise@latest{% endif %}/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_server %} documentation{% endif %}{% ifversion ghae-next %} + - "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/github-ae@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_managed %} documentation +{% endif %} + +- You must already have access to the private repositories and connect your account {% ifversion fpt %}in your private {% data variables.product.prodname_enterprise %} environment{% else %}on {% data variables.product.product_name %}{% endif %} with your account on {% data variables.product.prodname_dotcom_the_website %}. For more information about the repositories you can search, see "[About searching on GitHub](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github#searching-repositories-on-githubcom-from-your-private-enterprise-environment)." + +## Enabling GitHub.com repository search from {% ifversion fpt %}your private {% data variables.product.prodname_enterprise %} environment{% else %}{% data variables.product.product_name %}{% endif %} + +{% ifversion fpt %} + +For more information, see the following. + +| Your enterprise environment | Weitere Informationen | +|:--------------------------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| {% data variables.product.prodname_ghe_server %} | "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/enterprise-server@latest/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-enterprise-server)" |{% ifversion ghae-next %} +| +| {% data variables.product.prodname_ghe_managed %} | "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/github-ae@latest//search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-ae)" +{% endif %} + +{% elsif ghes or ghae %} + +1. Sign into {% data variables.product.product_name %} and {% data variables.product.prodname_dotcom_the_website %}. +1. On {% data variables.product.product_name %}, in the upper-right corner of any page, click your profile photo, then click **Settings**. ![Symbol „Settings" (Einstellungen) auf der Benutzerleiste](/assets/images/help/settings/userbar-account-settings.png) +{% data reusables.github-connect.github-connect-tab-user-settings %} +{% data reusables.github-connect.connect-dotcom-and-enterprise %} +{% data reusables.github-connect.connect-dotcom-and-enterprise %} + +{% endif %} diff --git a/translations/de-DE/content/search-github/getting-started-with-searching-on-github/index.md b/translations/de-DE/content/search-github/getting-started-with-searching-on-github/index.md new file mode 100644 index 0000000000..23f487487b --- /dev/null +++ b/translations/de-DE/content/search-github/getting-started-with-searching-on-github/index.md @@ -0,0 +1,21 @@ +--- +title: Erste Schritte bei der Suche auf GitHub +intro: 'You can use a wide range of syntax to search {% data variables.product.product_name %}. You can adjust the scope of your search, build and troubleshoot queries, and sort search results with qualifiers.' +redirect_from: + - /articles/getting-started-with-searching-on-github + - /github/searching-for-information-on-github/getting-started-with-searching-on-github +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +children: + - /about-searching-on-github + - /understanding-the-search-syntax + - /troubleshooting-search-queries + - /sorting-search-results + - /enabling-githubcom-repository-search-from-your-private-enterprise-environment +shortTitle: Start with search on GitHub +--- + diff --git a/translations/de-DE/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md b/translations/de-DE/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md new file mode 100644 index 0000000000..a5590e28ae --- /dev/null +++ b/translations/de-DE/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md @@ -0,0 +1,75 @@ +--- +title: Suchergebnisse sortieren +intro: 'Sie können Ergebnisse der [{% data variables.product.product_name %}-Suche](/articles/searching-on-github) mit den Optionen des Menüs „Sortieren“ oder durch einen „sort“-Kennzeichner in der Abfrage sortieren.' +redirect_from: + - /articles/sorting-search-results + - /github/searching-for-information-on-github/sorting-search-results + - /github/searching-for-information-on-github/getting-started-with-searching-on-github/sorting-search-results +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +Über das Sortiermenü kannst Du die Ergebnisse nach Relevanz, Anzahl der Sterne, Anzahl der Forks und dem letzten Änderungsdatum sortieren. + + ![Menü mit Optionen zum Sortieren der Suchergebnisse](/assets/images/help/search/repo-search-sort.png) + +Mit einem `sort`-Qualifizierer in der Abfrage kannst Du die Suchergebnisse nach Interaktionen, Reaktionen, Erstellungsdatum, Commit-Datum und letztem Änderungsdatum sortieren. + +## Nach Interaktionen sortieren + +Der Qualifizierer `sort:interactions` sortiert in absteigender Reihenfolge nach der Gesamtzahl der Reaktionen und Kommentare. + +| Qualifizierer | Beispiel | +| ------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sort:interactions` oder `sort:interactions-desc` | [**org:github sort:interactions**](https://github.com/search?q=org%3Agithub+sort%3Ainteractions&type=Issues) sucht Issues in {% data variables.product.product_name %}-Repositorys und sortiert sie in absteigender Reihenfolge nach der Gesamtzahl der Reaktionen und Kommentare. | +| `sort:interactions-asc` | [**org:github sort:interactions-asc**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Ainteractions-asc&type=Issues) sucht Issues in {% data variables.product.product_name %}-Repositorys und sortiert sie in aufsteigender Reihenfolge nach der Gesamtzahl der Reaktionen und Kommentare. | + +## Nach Reaktionen sortieren + +Der Qualifizierer `sort:reactions` sortiert nach der Anzahl oder dem Typ der Reaktionen. + +| Qualifizierer | Beispiel | +| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sort:reactions` oder `sort:reactions-desc` | [**org:github sort:reactions**](https://github.com/search?q=org%3Agithub+sort%3Areactions&type=Issues) sucht Issues in {% data variables.product.product_name %}-Repositorys und sortiert sie in absteigender Reihenfolge nach der Anzahl der Reaktionen. | +| `sort:reactions-asc` | [**org:github sort:reactions-asc**](https://github.com/search?q=org%3Agithub+sort%3Areactions-asc&type=Issues) sucht Issues in {% data variables.product.product_name %}-Repositorys und sortiert sie in aufsteigender Reihenfolge nach der Anzahl der Reaktionen. | +| sort:reactions-reaction | [**org:github sort:reactions-+1**](https://github.com/search?q=org%3Agithub+sort%3Areactions-%2B1&type=Issues) sucht Issues in {% data variables.product.product_name %}-Repositorys und sortiert sie in absteigender Reihenfolge nach der Anzahl der :+1:-Reaktionen (Daumen nach oben). | +| | [**org:github sort:reactions--1**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Areactions--1&type=Issues) sucht Issues in {% data variables.product.product_name %}-Repositorys und sortiert sie in absteigender Reihenfolge nach der Anzahl der :-1:-Reaktionen (Daumen nach unten). | +| | [**org:github sort:reactions-smile**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Areactions-smile&type=Issues) sucht Issues in {% data variables.product.product_name %}-Repositorys und sortiert sie in absteigender Reihenfolge nach der Anzahl der :smile:-Reaktionen (Lächeln). | +| | [**org:github sort:reactions-tada**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Areactions-tada&type=Issues) sucht Issues in {% data variables.product.product_name %}-Repositorys und sortiert sie in absteigender Reihenfolge nach der Anzahl der :tada:-Reaktionen (Hurra). | +| | [**org:github sort:reactions-heart**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Areactions-heart&type=Issues) sucht Issues in {% data variables.product.product_name %}-Repositorys und sortiert sie in absteigender Reihenfolge nach der Anzahl der :heart:-Reaktionen (Herz). | + +## Nach Verfassungsdatum sortieren + +Der Qualifizierer `sort:author-date` sortiert in absteigender oder aufsteigender Reihenfolge nach dem Verfassungsdatum. + +| Qualifizierer | Beispiel | +| ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sort:author-date` oder `sort:author-date-desc` | [**feature org:github sort:author-date**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Aauthor-date&type=Commits) sucht Commits mit dem Wort „feature“ in {% data variables.product.product_name %}-Repositorys und sortiert sie in absteigender Reihenfolge nach dem Verfassungsdatum. | +| `sort:author-date-asc` | [**feature org:github sort:author-date-asc**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Aauthor-date-asc&type=Commits) sucht Commits mit dem Wort „feature“ in {% data variables.product.product_name %}-Repositorys und sortiert sie in aufsteigender Reihenfolge nach dem Verfassungsdatum. | + +## Nach Commit-Datum sortieren + +Der Qualifizierer `sort:committer-date` sortiert in absteigender oder aufsteigender Reihenfolge nach dem Commit-Datum. + +| Qualifizierer | Beispiel | +| ----------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sort:committer-date` oder `sort:committer-date-desc` | [**feature org:github sort:committer-date**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Acommitter-date&type=Commits) sucht Commits mit dem Wort „feature“ in {% data variables.product.product_name %}-Repositorys und sortiert sie in absteigender Reihenfolge nach dem Commit-Datum. | +| `sort:committer-date-asc` | [**feature org:github sort:committer-date-asc**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Acommitter-date-asc&type=Commits) sucht Commits mit dem Wort „feature“ in {% data variables.product.product_name %}-Repositorys und sortiert sie in aufsteigender Reihenfolge nach dem Commit-Datum. | + +## Nach Änderungsdatum sortieren + +Der Qualifizierer `sort:updated` sortiert in absteigender oder aufsteigender Reihenfolge nach dem letzten Änderungsdatum. + +| Qualifizierer | Beispiel | +| --------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sort:updated` oder `sort:updated-desc` | [**feature sort:updated**](https://github.com/search?utf8=%E2%9C%93&q=feature+sort%3Aupdated&type=Repositories) sucht Repositorys mit dem Wort „feature“ und sortiert sie in absteigender Reihenfolge nach dem letzten Änderungsdatum. | +| `sort:updated-asc` | [**feature sort:updated-asc**](https://github.com/search?utf8=%E2%9C%93&q=feature+sort%3Aupdated-asc&type=Repositories) sucht Repositorys mit dem Wort „feature“ und sortiert sie in aufsteigender Reihenfolge nach dem letzten Änderungsdatum. | + +## Weiterführende Informationen + +- "[About searching on {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)" +- "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)" diff --git a/translations/de-DE/content/search-github/getting-started-with-searching-on-github/troubleshooting-search-queries.md b/translations/de-DE/content/search-github/getting-started-with-searching-on-github/troubleshooting-search-queries.md new file mode 100644 index 0000000000..75488010c7 --- /dev/null +++ b/translations/de-DE/content/search-github/getting-started-with-searching-on-github/troubleshooting-search-queries.md @@ -0,0 +1,34 @@ +--- +title: Fehlerbehebung bei Suchabfragen +intro: 'Wenn Ihre Suche auf {% data variables.product.product_name %} zu unerwarteten Ergebnissen führt, ziehen Sie zur Behebung dieser Fehler unsere Informationen zu häufigen Problemen und Einschränkungen der Abfragelänge zu Rate.' +redirect_from: + - /articles/troubleshooting-search-queries + - /github/searching-for-information-on-github/troubleshooting-search-queries + - /github/searching-for-information-on-github/getting-started-with-searching-on-github/troubleshooting-search-queries +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +shortTitle: Troubleshoot search queries +--- + +## Mögliche Zeitüberschreitung + +Einige Abfragen stellen für unsere Suchinfrastruktur eine außergewöhnlich hohe Rechenlast dar. Damit die Suche aber für jeden Benutzer schnell erfolgt, sehen wir uns gezwungen, der Dauer einer einzelnen Abfrage Grenzen zu setzen. In den sehr seltenen Fällen, in denen eine Abfrage aufgrund einer Zeitüberschreitung abgebrochen wird, gibt die Suche alle Treffer zurück, die bis zum Abbruch gefunden wurden. Gleichzeitig wirst Du über die Zeitüberschreitung informiert. + +Das Erreichen des Zeitlimits bedeutet jedoch nicht in jedem Fall, dass die Suchergebnisse unvollständig sind. Es bedeutet lediglich, dass die Abfrage vor der vollständigen Durchsuchung aller zur Verfügung stehenden Daten abgebrochen wurde. + +## Einschränkungen der Abfragelänge + +Bei der Suche auf {% data variables.product.product_name %} gelten für Abfragen auch Längeneinschränkungen: + +* Abfragen mit mehr als 256 Zeichen werden nicht unterstützt. +* Mehr als fünf `AND`-, `OR`- oder `NOT`-Operatoren werden in einer Abfrage nicht unterstützt. + +Für bestimmte Arten der Suche, beispielsweise für die Codesuche, gelten unter Umständen weitere Einschränkungen. Nähere Informationen findest Du in der Dokumentation zum jeweiligen Suchtyp. + +## Weiterführende Informationen + +- „[Informationen zur Suche auf GitHub](/search-github/getting-started-with-searching-on-github/about-searching-on-github)“ diff --git a/translations/de-DE/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md b/translations/de-DE/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md new file mode 100644 index 0000000000..f7323ffc96 --- /dev/null +++ b/translations/de-DE/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md @@ -0,0 +1,100 @@ +--- +title: Grundlagen der Suchsyntax +intro: 'Für Suchen auf {% data variables.product.product_name %} können Sie Abfragen erstellen, die nach bestimmten alphanumerischen Zeichenfolgen suchen.' +redirect_from: + - /articles/search-syntax/ + - /articles/understanding-the-search-syntax + - /github/searching-for-information-on-github/understanding-the-search-syntax + - /github/searching-for-information-on-github/getting-started-with-searching-on-github/understanding-the-search-syntax +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +shortTitle: Understand search syntax +--- + +## Abfrage nach Werten mit einem Vergleichsoperator + +Mit `>`, `>=`, `<` und `<=` kannst Du nach Werten suchen, die größer, größer oder gleich, kleiner, oder kleiner oder gleich einem anderen Wert sind. + +| Abfrage | Beispiel | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| >n | **[cats stars:>1000](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%3E1000&type=Repositories)** findet Repositorys mit dem Wort „cats" und mehr als 1.000 Sternen. | +| >=n | **[cats topics:>=5](https://github.com/search?utf8=%E2%9C%93&q=cats+topics%3A%3E%3D5&type=Repositories)** findet Repositorys mit dem Wort „cats", welche 5 oder mehr Themen haben. | +| <n | **[cats size:<10000](https://github.com/search?utf8=%E2%9C%93&q=cats+size%3A%3C10000&type=Code)** findet Code mit dem Wort „cats" in Dateien, die kleiner als 10 KB sind. | +| <=n | **[cats stars:<=50](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%3C%3D50&type=Repositories)** findet Repositorys mit dem Wort „cats" mit 50 oder weniger Sternen. | + +Auch mit [Bereichsabfragen](#query-for-values-between-a-range) kannst Du nach Werten suchen, die größer oder gleich respektive kleiner oder gleich einem anderen Wert sind. + +| Abfrage | Beispiel | +| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| n..* | **[cats stars:10..*](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A10..*&type=Repositories)** ist gleichbedeutend mit `stars:>=10` und sucht Repositorys, die das Wort „cats“ enthalten und mindestens 10 Sterne haben. | +| *..n | **[cats stars:*..10](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%22*..10%22&type=Repositories)** ist gleichbedeutend mit `stars:<=10` und sucht Repositorys, die das Wort „cats“ enthalten und höchstens 10 Sterne haben. | + +## Abfrage nach Werten innerhalb eines Wertebereichs + +Mit der Bereichssyntax n..n kannst Du nach Werten innerhalb eines Wertebereichs suchen. Dabei ist der erste Wert _n_ die untere und der zweite Wert die obere Grenze des gesuchten Bereichs. + +| Abfrage | Beispiel | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| n..n | **[cats stars:10..50](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A10..50&type=Repositories)** sucht Repositorys, die das Wort „cats“ enthalten und zwischen 10 und 50 Sternen haben. | + +## Abfrage nach Datums- und Zeitangaben + +Mit `>`, `>=`, `<`, `<=` und [Bereichsabfragen](#query-for-values-between-a-range) kannst Du nach Datums- und Zeitangaben vor oder nach einem bestimmten Datum/Uhrzeit oder innerhalb eines Datums-/Zeitbereichs suchen. {% data reusables.time_date.date_format %} + +| Abfrage | Beispiel | +| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| >YYYY-MM-DD | **[cats created:>2016-04-29](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3E2016-04-29&type=Issues)** findet Issues mit dem Wort „cats", die nach dem 29. April 0216 erstellt wurden. | +| >=YYYY-MM-DD | **[cats created:>=2017-04-01](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3E%3D2017-04-01&type=Issues)** findet Issues mit dem Wort „cats", welche am oder nach dem 1. April 2017 erstellt wurden. | +| <YYYY-MM-DD | **[cats pushed:<2012-07-05](https://github.com/search?q=cats+pushed%3A%3C2012-07-05&type=Code&utf8=%E2%9C%93)** findet Code mit dem Wort „cats" in Repositorys, die vor dem 5. Juli 2012 übertragen wurden. | +| <=YYYY-MM-DD | **[cats created:<=2012-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3C%3D2012-07-04&type=Issues)** findet Issues mit dem Wort „cats", die am oder vor dem 4. Juli 2012 erstellt wurden. | +| YYYY-MM-DD..YYYY-MM-DD | **[cats pushed:2016-04-30..2016-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+pushed%3A2016-04-30..2016-07-04&type=Repositories)** sucht Repositorys, die das Wort „cats“ enthalten und zu denen zwischen dem 30. April und dem 4. Juli 2016 ein Push erfolgt ist. | +| YYYY-MM-DD..* | **[cats created:2012-04-30..*](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2012-04-30..*&type=Issues)** sucht Issues, die das Wort „cats“ enthalten und nach dem 30. April 2012 erstellt wurden. | +| *..YYYY-MM-DD | **[cats created:*..2012-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A*..2012-07-04&type=Issues)** sucht Issues, die das Wort „cats“ enthalten und vor dem 30. April 2012 erstellt wurden. | + +{% data reusables.time_date.time_format %} + +| Abfrage | Beispiel | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| YYYY-MM-DDTHH:MM:SS+00:00 | **[cats created:2017-01-01T01:00:00+07:00..2017-03-01T15:30:15+07:00](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2017-01-01T01%3A00%3A00%2B07%3A00..2017-03-01T15%3A30%3A15%2B07%3A00&type=Issues)** sucht Issues, die zwischen 1. Januar 2017, 01:00 Uhr (mit einer UTC-Verschiebung von `07:00` Stunden), und 1. März 2017, 15:30 Uhr (mit ebenfalls einer UTC-Verschiebung von `07:00` Stunden), erstellt wurden. with a UTC offset of `07:00` and March 1, 2017 at 3 p.m. with a UTC offset of `07:00`. | +| YYYY-MM-DDTHH:MM:SSZ | **[cats created:2016-03-21T14:11:00Z..2016-04-07T20:45:00Z](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2016-03-21T14%3A11%3A00Z..2016-04-07T20%3A45%3A00Z&type=Issues)** sucht Issues, die zwischen 21. März 2016, 14:11 Uhr, und 7. April 2016, 20:45 Uhr, erstellt wurden. | + +## Ausschluss bestimmter Ergebnisse + +Mit der Syntax `NOT` kannst Du Ergebnisse, die ein bestimmtes Wort enthalten, aus den Abfrageergebnissen ausschließen. Der Operator `NOT` kann nur für Zeichenfolgen verwendet werden. Mit Zahlen oder Datumsangaben funktioniert er nicht. + +| Abfrage | Beispiel | +| ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `NOT` | **[hello NOT world](https://github.com/search?q=hello+NOT+world&type=Repositories)** sucht Repositorys, die das Wort „hello“, aber nicht das Wort „world“ enthalten. | + +Ebenso kannst du Deine Abfrageergebnisse durch Ausschluss bestimmter Teilmengen eingrenzen. Du kannst jedem Qualifizierer ein `-` voranstellen, um Ergebnisse auszuschließen, die mit diesem Qualifizierer übereinstimmen. + +| Abfrage | Beispiel | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| -KENNZEICHNER | **[cats stars:>10 -language:javascript](https://github.com/search?q=cats+stars%3A>10+-language%3Ajavascript&type=Repositories)** findet Repositorys mit dem Wort „cats", die mehr als 10 Sterne haben, aber nicht in JavaScript geschrieben sind. | +| | **[mentions:defunkt -org:github](https://github.com/search?utf8=%E2%9C%93&q=mentions%3Adefunkt+-org%3Agithub&type=Issues)** sucht Issues, die „@defunkt“ erwähnen, aber nicht in Repositorys der Organisation GitHub enthalten sind. | + +## Anführungszeichen für Abfragen nach Zeichenfolgen mit Leerzeichen + +Wenn Deine Suchabfrage Leerzeichen enthält, musst du die gesuchte Zeichenfolge in Anführungszeichen einschließen. Ein Beispiel: + +* [cats NOT "hello world"](https://github.com/search?utf8=✓&q=cats+NOT+"hello+world"&type=Repositories) sucht Repositorys, die das Wort „cats“ enthalten, aber nicht die Wörter „hello world“. +* [build label:"bug fix"](https://github.com/search?utf8=%E2%9C%93&q=build+label%3A%22bug+fix%22&type=Issues) sucht Issues, die das Wort „build“ enthalten und die Kennzeichnung „bug fix“ aufweisen. + +Bei Suchabfragen innerhalb von Code werden einige nicht alphanumerische Zeichen, so auch Leerzeichen, ignoriert, selbst wenn der Suchstring in Anführungszeichen steht. Dies führt oft nicht zum erwünschten Ergebnis. + +{% ifversion fpt or ghes or ghae %} +## Abfragen mit Benutzernamen + +Wenn Deine Abfrage einen Qualifizierer verwendet, der einen Benutzernamen verlangt, beispielsweise `user`, `actor`, oder `assignee`, kannst du jeden {% data variables.product.product_name %}-Benutzernamen verwenden, um eine spezifische Person anzugeben oder `@me` benutzen, um den aktuellen Benutzer anzugeben. + +| Abfrage | Beispiel | +| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `QUALIFIER:USERNAME` | [`author:nat`](https://github.com/search?q=author%3Anat&type=Commits) findet Commits, die von @nat verfasst wurden | +| `QUALIFIER:@me` | [`is:issue assignee:@me`](https://github.com/search?q=is%3Aissue+assignee%3A%40me&type=Issues) findet Issues, die der Person zugewiesen sind, die die Suchresultate anschaut | + +Du kannst `@me` nur mit einem Qualifizierer verwenden und nicht als eigenen Suchbegriff, wie etwa `@me main.workflow`. +{% endif %} diff --git a/translations/de-DE/content/search-github/index.md b/translations/de-DE/content/search-github/index.md new file mode 100644 index 0000000000..e455a597f0 --- /dev/null +++ b/translations/de-DE/content/search-github/index.md @@ -0,0 +1,20 @@ +--- +title: Informationen auf GitHub suchen +intro: Use different types of searches to find the information you want. +redirect_from: + - /categories/78/articles/ + - /categories/search/ + - /categories/searching-for-information-on-github + - /github/searching-for-information-on-github +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +children: + - /getting-started-with-searching-on-github + - /searching-on-github +shortTitle: Search on GitHub +--- + diff --git a/translations/de-DE/content/search-github/searching-on-github/finding-files-on-github.md b/translations/de-DE/content/search-github/searching-on-github/finding-files-on-github.md new file mode 100644 index 0000000000..a207407827 --- /dev/null +++ b/translations/de-DE/content/search-github/searching-on-github/finding-files-on-github.md @@ -0,0 +1,32 @@ +--- +title: Dateien auf GitHub suchen +intro: 'Du kannst mit dem Dateifinder eine Datei in einem Repository suchen. To search for a file in multiple repositories on {% data variables.product.product_name %}, use the [`filename` code search qualifier](/search-github/searching-on-github/searching-code#search-by-filename).' +redirect_from: + - /articles/finding-files-on-github + - /github/searching-for-information-on-github/finding-files-on-github + - /github/searching-for-information-on-github/searching-on-github/finding-files-on-github +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +{% tip %} + +**Tipps:** + +- Bei den Ergebnissen des Dateifinders sind einige Verzeichnisse ausgeschlossen, z. B. `build`, `log`, `tmp` und `vendor`. Um Dateien in diesen Verzeichnissen zu suchen, verwende den [Code-Suchqualifizierer `filename`](/search-github/searching-on-github/searching-code#search-by-filename). +- Du kannst den Dateifinder auch öffnen, indem Du auf der Tastatur auf `t` drückst. Weitere Informationen findest Du unter „[Tastenkürzel](/articles/keyboard-shortcuts).“ + +{% endtip %} + +{% data reusables.repositories.navigate-to-repo %} +2. Above the list of files, click **Go to file**. ![Schaltfläche „Find file“ (Datei finden)](/assets/images/help/search/find-file-button.png) +3. Geben Sie im Suchfeld den Namen der Datei ein, die Sie suchen möchten. ![Suchfeld zur Dateisuche](/assets/images/help/search/find-file-search-field.png) +4. Klicken Sie in der Ergebnisliste auf die gewünschte Datei. + +## Weiterführende Informationen + +- „[Informationen zur Suche auf GitHub](/search-github/getting-started-with-searching-on-github/about-searching-on-github)“ diff --git a/translations/de-DE/content/search-github/searching-on-github/index.md b/translations/de-DE/content/search-github/searching-on-github/index.md new file mode 100644 index 0000000000..1776c828b0 --- /dev/null +++ b/translations/de-DE/content/search-github/searching-on-github/index.md @@ -0,0 +1,27 @@ +--- +title: Auf GitHub suchen +intro: You can use qualifiers to narrow your search and focus on specific categories of information. +redirect_from: + - /articles/searching-on-github + - /github/searching-for-information-on-github/searching-on-github +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +children: + - /finding-files-on-github + - /searching-for-repositories + - /searching-topics + - /searching-code + - /searching-commits + - /searching-issues-and-pull-requests + - /searching-discussions + - /searching-github-marketplace + - /searching-users + - /searching-for-packages + - /searching-wikis + - /searching-in-forks +--- + diff --git a/translations/de-DE/content/search-github/searching-on-github/searching-code.md b/translations/de-DE/content/search-github/searching-on-github/searching-code.md new file mode 100644 index 0000000000..48caad6888 --- /dev/null +++ b/translations/de-DE/content/search-github/searching-on-github/searching-code.md @@ -0,0 +1,112 @@ +--- +title: Code durchsuchen +intro: 'Auf {% data variables.product.product_name %} können Sie Code durchsuchen und die Suchergebnisse mit den folgenden Kennzeichnern der Codesuche in beliebiger Kombination eingrenzen.' +redirect_from: + - /articles/searching-code + - /github/searching-for-information-on-github/searching-files-in-a-repository-for-exact-matches + - /github/searching-for-information-on-github/searching-code-for-exact-matches + - /github/searching-for-information-on-github/searching-code + - /github/searching-for-information-on-github/searching-on-github/searching-code +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +{% data reusables.search.you-can-search-globally %} For more information, see "[About searching on GitHub](/search-github/getting-started-with-searching-on-github/about-searching-on-github)." + +Du kannst Code nur mit den diesen Qualifizierern der Codesuche durchsuchen. Spezifische Qualifizierer für Repositorys, Benutzer oder Commits funktionieren bei der Durchsuchung von Code nicht. + +{% data reusables.search.syntax_tips %} + +## Grundlegendes zur Codesuche + +Aufgrund der Komplexität der Codesuche gelten bei der Durchführung der Suche Einschränkungen: + +{% ifversion fpt or ghes %} +- {% data reusables.search.required_login %}{% endif %} +- Code in [Forks](/articles/about-forks) ist nur durchsuchbar, wenn für den Fork mehr Sterne vergeben wurden als für das übergeordnete Repository. Forks mit weniger Sternen als das übergeordnete Repository sind **nicht** für die Codesuche indiziert. Um Forks mit mehr Sternen als das übergeordnete Repository in die Suchergebnisse einzuschließen, musst Du Deiner Abfrage `fork:true` oder `fork:only` hinzufügen. Weitere Informationen findest Du unter „[Forks durchsuchen](/search-github/searching-on-github/searching-in-forks).“ +- Only the _default branch_ is indexed for code search.{% ifversion fpt %} +- Nur Dateien kleiner 384 KB sind durchsuchbar.{% else %}* Nur Dateien kleiner 5 MB sind durchsuchbar. +- Nur die ersten 500 KB jeder Datei sind durchsuchbar.{% endif %} +- Only repositories with fewer than 500,000 files are searchable.{% ifversion fpt %} +- Only repositories that have had activity or have been returned in search results in the last year are searchable.{% endif %} +- Deine Quellcode-Suche muss mindestens einen Suchbegriff enthalten, ausgenommen bei [`filename`-Suchen](#search-by-filename). Beispielsweise ist eine Suche nach [`language:javascript`](https://github.com/search?utf8=%E2%9C%93&q=language%3Ajavascript&type=Code&ref=searchresults) ungültig, [`amazing language:javascript`](https://github.com/search?utf8=%E2%9C%93&q=amazing+language%3Ajavascript&type=Code&ref=searchresults) ist dagegen gültig. +- Die Suchergebnisse können maximal zwei gefundene Fragmente der gleichen Datei anzeigen, selbst wenn die Datei mehr Treffer enthält. +- Folgende Platzhalterzeichen können in Suchabfragen nicht verwendet werden: . , : ; / \ ` ' " = * ! ? # $ & + ^ | ~ < > ( ) { } [ ] @. Diese Zeichen werden bei der Suche schlicht ignoriert. + +## Suche nach Dateiinhalten oder Dateipfad + +Mit dem Qualifizierer `in` kannst Du Deine Suche auf den Inhalt der Quellcodedatei, auf den Dateipfad oder auf beides eingrenzen. Ohne diesen Qualifizierer werden nur Dateiinhalte durchsucht. + +| Qualifizierer | Beispiel | +| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `in:file` | [**octocat in:file**](https://github.com/search?q=octocat+in%3Afile&type=Code) durchsucht den Dateiinhalt nach dem Code „octocat“. | +| `in:path` | [**octocat in:path**](https://github.com/search?q=octocat+in%3Apath&type=Code) durchsucht den Dateipfad nach dem Code „octocat“. | +| | [**octocat in:file,path**](https://github.com/search?q=octocat+in%3Afile%2Cpath&type=Code) durchsucht Dateiinhalt und den Dateipfad nach dem Code „octocat“. | + +## Suche innerhalb der Repositorys eines Benutzers oder einer Organisation + +Wenn Sie Code in allen Repositorys suchen, die einem bestimmten Benutzer oder einer bestimmten Organisation gehören, verwenden Sie den Kennzeichner `user` bzw. `org`. Für die Suche nach Code in einem bestimmten Repository verwenden Sie den Kennzeichner `repo`. + +| Qualifizierer | Beispiel | +| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**user:defunkt extension:rb**](https://github.com/search?q=user%3Agithub+extension%3Arb&type=Code) sucht nach Code von @defunkt in Dateien mit der Erweiterung .rb. | +| org:ORGNAME | [**org:github extension:js**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+extension%3Ajs&type=Code) sucht nach Code von GitHub in Dateien mit der Erweiterung .js. | +| repo:USERNAME/REPOSITORY | [**repo:mozilla/shumway extension:as**](https://github.com/search?q=repo%3Amozilla%2Fshumway+extension%3Aas&type=Code) sucht nach Code aus dem Projekt „shumway“ von @mozilla in Dateien mit der Erweiterung .as. | + +## Suche nach Standort + +Mit dem Kennzeichner `path` können Sie nach Quellcode unter einem bestimmten Pfad innerhalb eines Repositorys suchen. Mit `path:/` suchen Sie nach Dateien auf der Root-Ebene eines Repositorys. Sie können aber auch einen Verzeichnisnamen oder den Pfad zu einem Verzeichnis angeben, um Dateien innerhalb dieses Verzeichnisses oder seiner Unterverzeichnisse zu durchsuchen. + +| Qualifizierer | Beispiel | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| path:/ | [**octocat filename:readme path:/**](https://github.com/search?utf8=%E2%9C%93&q=octocat+filename%3Areadme+path%3A%2F&type=Code) sucht nach _readme_-Dateien mit dem Wort „octocat“ auf der Root-Ebene eines Repositorys. | +| path:DIRECTORY | [**form path:cgi-bin language:perl**](https://github.com/search?q=form+path%3Acgi-bin+language%3Aperl&type=Code) matches Perl files with the word "form" in the cgi-bin directory, or in any of its subdirectories. | +| path:PATH/TO/DIRECTORY | [**console path:app/public language:javascript**](https://github.com/search?q=console+path%3A%22app%2Fpublic%22+language%3Ajavascript&type=Code) matches JavaScript files with the word "console" in the app/public directory, or in any of its subdirectories (even if they reside in app/public/js/form-validators). | + +## Suche nach Sprache + + +Du kannst Code auch in Abhängigkeit der Programmiersprache suchen. The `language` qualifier can be the language name or alias. For a full list of supported languages with their names and aliases, see the [github/linguist repository](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml). + +| Qualifizierer | Beispiel | +| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| language:LANGUAGE | [**element language:xml size:100**](https://github.com/search?q=element+language%3Axml+size%3A100&type=Code) sucht Code mit dem Wort „element“, der als XML gekennzeichnet ist und genau 100 Byte groß ist. | +| | [**display language:scss**](https://github.com/search?q=display+language%3Ascss&type=Code) sucht Code mit dem Wort „display“, der als SCSS gekennzeichnet ist. | +| | [**org:mozilla language:markdown**](https://github.com/search?utf8=%E2%9C%93&q=org%3Amozilla+language%3Amarkdown&type=Code) sucht Code aus allen Repositorys von @mozilla, der als Markdown gekennzeichnet ist. | + +## Suche nach Dateigröße + +Mit dem Kennzeichner `size` können Sie Quellcode auf Basis der Größe der Datei suchen, in der sich der Code befindet. `size` in Verbindung mit den [„Größer als“-, „Kleiner als“- und „Bereichs“-](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)Operatoren filtert die Ergebnisse der Codesuche nach der Byte-Größe der Datei, die den Code enthält. + +| Qualifizierer | Beispiel | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| size:n | [**function size:>10000 language:python**](https://github.com/search?q=function+size%3A%3E10000+language%3Apython&type=Code) sucht Python-Code mit dem Wort „function“ in Dateien mit einer Größe von mehr als 10 KB. | + +## Suche nach Dateiname + +Der Kennzeichner `filename` sucht Codedateien mit einem bestimmten Dateinamen. Zur Suche nach Dateien in einem Repository können Sie aber auch die Dateisuche verwenden. Weitere Informationen findest Du unter „[Dateien auf GitHub suchen](/search-github/searching-on-github/finding-files-on-github).“ + +| Qualifizierer | Beispiel | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| filename:FILENAME | [**filename:linguist**](https://github.com/search?utf8=%E2%9C%93&q=filename%3Alinguist&type=Code) sucht nach Dateien mit dem Dateinamen „linguist“. | +| | [**filename:.vimrc commands**](https://github.com/search?q=filename%3A.vimrc+commands&type=Code) sucht *.vimrc*-Dateien, deren Namen das Wort „commands“ enthalten. | +| | [**filename:test_helper path:test language:ruby**](https://github.com/search?q=minitest+filename%3Atest_helper+path%3Atest+language%3Aruby&type=Code) sucht Ruby-Dateien mit dem Dateinamen *test_helper* im Verzeichnis *test*. | + +## Suche nach Dateierweiterung + +Der Kennzeichner `extension` sucht Codedateien mit einer bestimmten Dateierweiterung. + +| Qualifizierer | Beispiel | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| extension:EXTENSION | [**form path:cgi-bin extension:pm**](https://github.com/search?q=form+path%3Acgi-bin+extension%3Apm&type=Code) sucht Code mit dem Wort „form“ in Dateien mit der Dateierweiterung .pm unter dem Pfad cgi-bin. | +| | [**icon size:>200000 extension:css**](https://github.com/search?utf8=%E2%9C%93&q=icon+size%3A%3E200000+extension%3Acss&type=Code) sucht Dateien größer als 200 KB mit der Dateierweiterung .css und dem Wort „icon" im Code. | + +## Weiterführende Informationen + +- „[Suchergebnisse sortieren](/search-github/getting-started-with-searching-on-github/sorting-search-results/)“ +- „[Durchsuchen von Forks](/search-github/searching-on-github/searching-in-forks)"{% ifversion fpt %} +- „[Navigieren von Code auf {% data variables.product.prodname_dotcom %}](/github/managing-files-in-a-repository/navigating-code-on-github)"{% endif %} diff --git a/translations/de-DE/content/search-github/searching-on-github/searching-commits.md b/translations/de-DE/content/search-github/searching-on-github/searching-commits.md new file mode 100644 index 0000000000..46dd5bfaac --- /dev/null +++ b/translations/de-DE/content/search-github/searching-on-github/searching-commits.md @@ -0,0 +1,111 @@ +--- +title: Commits durchsuchen +intro: 'Auf {% data variables.product.product_name %} können Sie Commits durchsuchen und die Suchergebnisse mit den folgenden Kennzeichnern der Commit-Suche in beliebiger Kombination eingrenzen.' +redirect_from: + - /articles/searching-commits + - /github/searching-for-information-on-github/searching-commits + - /github/searching-for-information-on-github/searching-on-github/searching-commits +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +Sie können Commits global auf {% data variables.product.product_name %} oder in bestimmten Repositorys oder Organisationen durchsuchen. Weitere Informationen findest Du unter „[Informationen zur Suche auf {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github).“ + +Bei der Suche nach Commits wird nur der [Standardbranch](/articles/about-branches) eines Repositorys durchsucht. + +{% data reusables.search.syntax_tips %} + +## Suche in Commit-Mitteilungen + +Du kannst nach Commits suchen, deren Nachricht bestimmte Wörter enthält. [**fix typo**](https://github.com/search?q=fix+typo&type=Commits) beispielsweise sucht Commits mit den Wörtern „fix“ und „typo“. + +## Suche nach Autor oder Committer + +Mit den Qualifizierern `author` oder `committer` kannst Du Commits von bestimmten Benutzern suchen. + +| Qualifizierer | Beispiel | +| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | +| author:USERNAME | [**author:defunkt**](https://github.com/search?q=author%3Adefunkt&type=Commits) sucht Commits, die von @defunkt verfasst wurden. | +| committer:USERNAME | [**committer:defunkt**](https://github.com/search?q=committer%3Adefunkt&type=Commits) sucht Commits, die von @defunkt freigegeben wurden. | + +Die Qualifizierer `author-name` und `committer-name` gleichen Commits nach dem Namen des Autors oder Freigebenden ab. + +| Qualifizierer | Beispiel | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| author-name:NAME | [**author-name:wanstrath**](https://github.com/search?q=author-name%3Awanstrath&type=Commits) sucht Commits mit „wanstrath“ im Namen des Autors. | +| committer-name:NAME | [**committer-name:wanstrath**](https://github.com/search?q=committer-name%3Awanstrath&type=Commits) sucht Commits mit „wanstrath“ im Namen des Freigebenden. | + +Die Qualifizierer `author-email` und `committer-email` gleichen Commits nach der vollständigen E-Mail-Adresse des Autors oder Freigebenden ab. + +| Qualifizierer | Beispiel | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| author-email:EMAIL | [**author-email:chris@github.com**](https://github.com/search?q=author-email%3Achris%40github.com&type=Commits) sucht Commits, die von chris@github.com verfasst wurden. | +| committer-email:EMAIL | [**committer-email:chris@github.com**](https://github.com/search?q=committer-email%3Achris%40github.com&type=Commits) sucht Commits, die von chris@github.com freigegeben wurden. | + +## Suche nach Verfassungs- oder Commit-Datum + +Mit den Qualifizierern `author-date` und `committer-date` kannst Du Commits suchen, die innerhalb des angegebenen Datumsbereichs verfasst oder freigegeben wurden. + +{% data reusables.search.date_gt_lt %} + +| Qualifizierer | Beispiel | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| author-date:YYYY-MM-DD | [**author-date:<2016-01-01**](https://github.com/search?q=author-date%3A<2016-01-01&type=Commits) sucht Commits, die vor dem 1. Januar 2016 verfasst wurden. | +| committer-date:YYYY-MM-DD | [**committer-date:>2016-01-01**](https://github.com/search?q=committer-date%3A>2016-01-01&type=Commits) matches commits committed after 2016-01-01. | + +## Merge-Commits filtern + +Der Qualifizierer `merge` filtert Merge-Commits. + +| Qualifizierer | Beispiel | +| ------------- | --------------------------------------------------------------------------------------------------- | +| `merge:true` | [**merge:true**](https://github.com/search?q=merge%3Atrue&type=Commits) sucht Merge-Commits. | +| `merge:false` | [**merge:false**](https://github.com/search?q=merge%3Afalse&type=Commits) sucht Commits ohne Merge. | + +## Suche nach Hash + +Der Qualifizierer `hash` sucht Commits mit dem angegebenen SHA-1-Hash. + +| Qualifizierer | Beispiel | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| hash:HASH | [**hash:124a9a0ee1d8f1e15e833aff432fbb3b02632105**](https://github.com/github/gitignore/search?q=hash%3A124a9a0ee1d8f1e15e833aff432fbb3b02632105&type=Commits) sucht Commits mit dem Hash `124a9a0ee1d8f1e15e833aff432fbb3b02632105`. | + +## Suche nach übergeordnetem Commit + +Der Qualifizierer `parent` sucht Commits, deren übergeordneten Commits das angegebene SHA-1-Hash aufweisen. + +| Qualifizierer | Beispiel | +| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| parent:HASH | [**parent:124a9a0ee1d8f1e15e833aff432fbb3b02632105**](https://github.com/github/gitignore/search?q=parent%3A124a9a0ee1d8f1e15e833aff432fbb3b02632105&type=Commits&utf8=%E2%9C%93) sucht untergeordnete Commits von Commits mit dem Hash `124a9a0ee1d8f1e15e833aff432fbb3b02632105`. | + +## Suche nach Struktur + +Der Qualifizierer `tree` sucht Commits mit dem angegebenen SHA-1-Git-Struktur-Hash. + +| Qualifizierer | Beispiel | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | +| tree:HASH | [**tree:99ca967**](https://github.com/github/gitignore/search?q=tree%3A99ca967&type=Commits) sucht Commits, die das Struktur-Hash `99ca967` referenzieren. | + +## Suche innerhalb der Repositorys eines Benutzers oder einer Organisation + +Wenn Du Commits in allen Repositorys suchst, die einem bestimmten Benutzer oder einer bestimmten Organisation gehören, verwende den Qualifizierer `user` respektive `org`. Für die Suche nach Commits in einem bestimmten Repository verwende den Qualifizierer `repo`. + +| Qualifizierer | Beispiel | +| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**gibberish user:defunkt**](https://github.com/search?q=gibberish+user%3Adefunkt&type=Commits&utf8=%E2%9C%93) sucht in Repositorys des Benutzers @defunkt nach Commits, deren Mitteilungen das Wort „gibberish“ enthalten. | +| org:ORGNAME | [**test org:github**](https://github.com/search?utf8=%E2%9C%93&q=test+org%3Agithub&type=Commits) sucht in Repositorys der Organisation @github nach Commits, deren Mitteilungen das Wort „test“ enthalten. | +| repo:USERNAME/REPO | [**language repo:defunkt/gibberish**](https://github.com/search?utf8=%E2%9C%93&q=language+repo%3Adefunkt%2Fgibberish&type=Commits) sucht im Repository „gibberish“ des Benutzers @defunkt nach Commits, deren Mitteilungen das Wort „language“ enthalten. | + +## Filter by repository visibility + +The `is` qualifier matches commits from repositories with the specified visibility. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." + +| Qualifier | Example | ------------- | ------------- |{% ifversion fpt or ghes %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Commits) matches commits to public repositories.{% endif %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Commits) matches commits to internal repositories. | `is:private` | [**is:private**](https://github.com/search?q=is%3Aprivate&type=Commits) matches commits to private repositories. + +## Weiterführende Informationen + +- „[Suchergebnisse sortieren](/search-github/getting-started-with-searching-on-github/sorting-search-results/)“ diff --git a/translations/de-DE/content/search-github/searching-on-github/searching-discussions.md b/translations/de-DE/content/search-github/searching-on-github/searching-discussions.md new file mode 100644 index 0000000000..98b8082c30 --- /dev/null +++ b/translations/de-DE/content/search-github/searching-on-github/searching-discussions.md @@ -0,0 +1,113 @@ +--- +title: Searching discussions +intro: 'You can search for discussions on {% data variables.product.product_name %} and narrow the results using search qualifiers.' +versions: + fpt: '*' +topics: + - GitHub search +redirect_from: + - /github/searching-for-information-on-github/searching-discussions + - /github/searching-for-information-on-github/searching-on-github/searching-discussions +--- + +## About searching for discussions + +You can search for discussions globally across all of {% data variables.product.product_name %}, or search for discussions within a particular organization or repository. Weitere Informationen findest Du unter „[Informationen zur Suche auf {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/about-searching-on-github).“ + +{% data reusables.search.syntax_tips %} + +## Suche nach Titel, Textteil oder Kommentaren + +With the `in` qualifier you can restrict your search for discussions to the title, body, or comments. You can also combine qualifiers to search a combination of title, body, or comments. When you omit the `in` qualifier, {% data variables.product.product_name %} searches the title, body, and comments. + +| Qualifizierer | Beispiel | +|:------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `in:title` | [**welcome in:title**](https://github.com/search?q=welcome+in%3Atitle&type=Discussions) matches discussions with "welcome" in the title. | +| `in:body` | [**onboard in:title,body**](https://github.com/search?q=onboard+in%3Atitle%2Cbody&type=Discussions) matches discussions with "onboard" in the title or body. | +| `in:comments` | [**thanks in:comments**](https://github.com/search?q=thanks+in%3Acomment&type=Discussions) matches discussions with "thanks" in the comments for the discussion. | + +## Suche innerhalb der Repositorys eines Benutzers oder einer Organisation + +To search discussions in all repositories owned by a certain user or organization, you can use the `user` or `org` qualifier. To search discussions in a specific repository, you can use the `repo` qualifier. + +| Qualifizierer | Beispiel | +|:------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**user:octocat feedback**](https://github.com/search?q=user%3Aoctocat+feedback&type=Discussions) matches discussions with the word "feedback" from repositories owned by @octocat. | +| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=Discussions&utf8=%E2%9C%93) matches discussions in repositories owned by the GitHub organization. | +| repo:USERNAME/REPOSITORY | [**repo:nodejs/node created:<2021-01-01**](https://github.com/search?q=repo%3Anodejs%2Fnode+created%3A%3C2020-01-01&type=Discussions) matches discussions from @nodejs' Node.js runtime project that were created before January 2021. | + +## Filter by repository visibility + +You can filter by the visibility of the repository containing the discussions using the `is` qualifier. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." + +| Qualifier | Example | :- | :- |{% ifversion fpt or ghes %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Discussions) matches discussions in public repositories.{% endif %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Discussions) matches discussions in internal repositories. | `is:private` | [**is:private tiramisu**](https://github.com/search?q=is%3Aprivate+tiramisu&type=Discussions) matches discussions that contain the word "tiramisu" in private repositories you can access. + +## Suche nach Autor + +The `author` qualifier finds discussions created by a certain user. + +| Qualifizierer | Beispiel | +|:------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| author:USERNAME | [**cool author:octocat**](https://github.com/search?q=cool+author%3Aoctocat&type=Discussions) matches discussions with the word "cool" that were created by @octocat. | +| | [**bootstrap in:body author:octocat**](https://github.com/search?q=bootstrap+in%3Abody+author%3Aoctocat&type=Discussions) matches discussions created by @octocat that contain the word "bootstrap" in the body. | + +## Suche nach Kommentierer + +The `commenter` qualifier finds discussions that contain a comment from a certain user. + +| Qualifizierer | Beispiel | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| commenter:USERNAME | [**github commenter:becca org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Abecca+org%3Agithub&type=Discussions) matches discussions in repositories owned by GitHub, that contain the word "github," and have a comment by @becca. | + +## Search by a user that's involved in a discussion + +You can use the `involves` qualifier to find discussions that involve a certain user. The qualifier returns discussions that were either created by a certain user, mention the user, or contain comments by the user. The `involves` qualifier is a logical OR between the `author`, `mentions`, and `commenter` qualifiers for a single user. + +| Qualifizierer | Beispiel | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| involves:USERNAME | **[involves:becca involves:octocat](https://github.com/search?q=involves%3Abecca+involves%3Aoctocat&type=Discussions)** matches discussions either @becca or @octocat are involved in. | +| | [**NOT beta in:body involves:becca**](https://github.com/search?q=NOT+beta+in%3Abody+involves%3Abecca&type=Discussions) matches discussions @becca is involved in that do not contain the word "beta" in the body. | + +## Suche nach Anzahl der Kommentare + +You can use the `comments` qualifier along with greater than, less than, and range qualifiers to search by the number of comments. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." + +| Qualifizierer | Beispiel | +|:------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------- | +| comments:n | [**comments:>100**](https://github.com/search?q=comments%3A%3E100&type=Discussions) matches discussions with more than 100 comments. | +| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Discussions) matches discussions with comments ranging from 500 to 1,000. | + +## Suche nach Anzahl der Interaktionen + +You can filter discussions by the number of interactions with the `interactions` qualifier along with greater than, less than, and range qualifiers. The interactions count is the number of reactions and comments on a discussion. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." + +| Qualifizierer | Beispiel | +|:------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------- | +| interactions:n | [** interactions:>2000**](https://github.com/search?q=interactions%3A%3E2000) matches discussions with more than 2,000 interactions. | +| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) matches discussions with interactions ranging from 500 to 1,000. | + +## Suche nach Anzahl der Reaktionen + +You can filter discussions by the number of reactions using the `reactions` qualifier along with greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." + +| Qualifizierer | Beispiel | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------ | +| reactions:n | [** reactions:>1000**](https://github.com/search?q=reactions%3A%3E500) matches discussions with more than 500 reactions. | +| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) matches discussions with reactions ranging from 500 to 1,000. | + +## Search by when a discussion was created or last updated + +You can filter discussions based on times of creation, or when the discussion was last updated. For discussion creation, you can use the `created` qualifier; to find out when an discussion was last updated, use the `updated` qualifier. + +Both qualifiers take a date as a parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifizierer | Beispiel | +|:-------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| created:YYYY-MM-DD | [**created:>2020-11-15**](https://github.com/search?q=created%3A%3E%3D2020-11-15&type=discussions) matches discussions that were created after November 15, 2020. | +| updated:YYYY-MM-DD | [**weird in:body updated:>=2020-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2020-12-01&type=Discussions) matches discussions with the word "weird" in the body that were updated after December 2020. | + +## Weiterführende Informationen + +- „[Suchergebnisse sortieren](/search-github/getting-started-with-searching-on-github/sorting-search-results/)“ diff --git a/translations/de-DE/content/search-github/searching-on-github/searching-for-packages.md b/translations/de-DE/content/search-github/searching-on-github/searching-for-packages.md new file mode 100644 index 0000000000..095e6f82a9 --- /dev/null +++ b/translations/de-DE/content/search-github/searching-on-github/searching-for-packages.md @@ -0,0 +1,45 @@ +--- +title: Suche nach Paketen +intro: 'Du kannst auf {% data variables.product.product_name %} nach Paketen suchen und die Suchresultate mit Qualifizierern einschränken.' +product: '{% data reusables.gated-features.packages %}' +permissions: Anyone can search for packages they have access to. +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +redirect_from: + - /github/searching-for-information-on-github/searching-for-packages + - /github/searching-for-information-on-github/searching-on-github/searching-for-packages +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +## Über die Suche nach Paketen + +Du kannst global über das gesamte {% data variables.product.product_name %} nach Paketen suchen, oder nur innerhalb einer bestimmten Organisation. Weitere Informationen findest Du unter „[Informationen zur Suche auf {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github).“ + +{% ifversion ghes %} +You can only search for packages on {% data variables.product.product_name %}, not {% data variables.product.prodname_dotcom_the_website %}, even if {% data variables.product.prodname_github_connect %} is enabled. +{% endif %} + +{% data reusables.search.syntax_tips %} + +## Suche in den Paketen eines Benutzers oder einer Organisation + +Um Pakete zu finden, die einem bestimmten Benutzer oder einer bestimmten Organisation gehören, benutze die Qualifizierer `user` oder `org`. + +| Qualifizierer | Beispiel | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**user:codertocat**](https://github.com/search?q=user%3Acodertocat&type=RegistryPackages) findet Pakete die @codertocat gehören | +| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=RegistryPackages) findet Pakete, die der {% data variables.product.prodname_dotcom %}-Organisation gehören | + +## Pakete nach Sichtbarkeit filtern + +Um Deine Suche nach öffentlichen oder privaten Paketen zu filtern, benutze den Qualifizierer `is`. + +| Qualifizierer | Beispiel | +| ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `is:public` | [**is:public angular**](https://github.com/search?q=is%3Apublic+angular&type=RegistryPackages) findet öffentliche Pakete, die das Wort „angular" beinhalten | +| `is:private` | [**is:private php**](https://github.com/search?q=is%3Aprivate+php&type=RegistryPackages) findet private Pakete, die das Wort „php" beinhalten | diff --git a/translations/de-DE/content/search-github/searching-on-github/searching-for-repositories.md b/translations/de-DE/content/search-github/searching-on-github/searching-for-repositories.md new file mode 100644 index 0000000000..4a065d53b3 --- /dev/null +++ b/translations/de-DE/content/search-github/searching-on-github/searching-for-repositories.md @@ -0,0 +1,201 @@ +--- +title: Nach Repositorys suchen +intro: 'Auf {% data variables.product.product_name %} können Sie nach Repositorys suchen und die Suchergebnisse mit den folgenden Kennzeichnern der Repository-Suche in beliebiger Kombination eingrenzen.' +redirect_from: + - /articles/searching-repositories/ + - /articles/searching-for-repositories + - /github/searching-for-information-on-github/searching-for-repositories + - /github/searching-for-information-on-github/searching-on-github/searching-for-repositories +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +shortTitle: Search for repositories +--- + +Sie können Repositorys global auf {% data variables.product.product_location %} oder in einer bestimmten Organisation durchsuchen. Weitere Informationen findest Du unter „[Informationen zur Suche auf {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github).“ + +Um Forks in die Suchergebnisse einzuschließen, musst du Deiner Abfrage den Qualifizierer `fork:true` oder `fork:only` hinzufügen. Weitere Informationen findest Du unter „[Forks durchsuchen](/search-github/searching-on-github/searching-in-forks).“ + +{% data reusables.search.syntax_tips %} + +## Suche nach Repository-Name, Beschreibung oder Inhalt der README-Datei + +Mit dem Qualifizierer `in` kannst Du Deine Suche auf den Namen, die Beschreibung oder den Inhalt der README-Dateien der Repositorys oder jede beliebige Kombination derselben eingrenzen. Ohne diesen Qualifizierer werden nur die Namen und Beschreibungen der Repositorys durchsucht. + +| Qualifizierer | Beispiel | +| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `in:name` | [**jquery in:name**](https://github.com/search?q=jquery+in%3Aname&type=Repositories) matches repositories with "jquery" in the repository name. | +| `in:description` | [**jquery in:name,description**](https://github.com/search?q=jquery+in%3Aname%2Cdescription&type=Repositories) matches repositories with "jquery" in the repository name or description. | +| `in:readme` | [**jquery in:readme**](https://github.com/search?q=jquery+in%3Areadme&type=Repositories) matches repositories mentioning "jquery" in the repository's README file. | +| `repo:owner/name` | [**repo:octocat/hello-world**](https://github.com/search?q=repo%3Aoctocat%2Fhello-world) sucht nach einem Repository mit einem bestimmten Namen. | + +## Suche nach Repository-Inhalt + +You can find a repository by searching for content in the repository's README file using the `in:readme` qualifier. Weitere Informationen finden Sie unter „[Informationen zu README-Dateien](/github/creating-cloning-and-archiving-repositories/about-readmes)“. + +`in:readme` ist die einzige Möglichkeit, Repositorys anhand bestimmter Inhalte im Repository zu finden. Wenn Du nach einer bestimmten Datei oder einem bestimmten Inhalt innerhalb eines Repositorys suchst, verwende den Dateifinder oder die code-spezifischen Suchbegriffe. Weitere Informationen findest Du in den Abschnitten „[Dateien auf {% data variables.product.prodname_dotcom %} finden](/search-github/searching-on-github/finding-files-on-github)“ und „[Code durchsuchen](/search-github/searching-on-github/searching-code).“ + +| Qualifizierer | Beispiel | +| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `in:readme` | [**octocat in:readme**](https://github.com/search?q=octocat+in%3Areadme&type=Repositories) matches repositories mentioning "octocat" in the repository's README file. | + +## Suche innerhalb der Repositorys eines Benutzers oder einer Organisation + +Wenn Du alle Repositorys durchsuchen möchtest, die einem bestimmten Benutzer oder einer bestimmten Organisation gehören, verwende den Qualifizierer `user` respektive `org`. + +| Qualifizierer | Beispiel | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**user:defunkt forks:>100**](https://github.com/search?q=user%3Adefunkt+forks%3A%3E%3D100&type=Repositories) sucht Repositorys des Benutzers @defunkt mit mehr als 100 Forks. | +| org:ORGNAME | [**org:github**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub&type=Repositories) sucht GitHub-Repositorys. | + +## Suche nach Repository-Größe + +The `size` qualifier finds repositories that match a certain size (in kilobytes), using greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." + +| Qualifizierer | Beispiel | +| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | +| size:n | [**size:1000**](https://github.com/search?q=size%3A1000&type=Repositories) sucht Repositorys mit einer Größe von 1 MB. | +| | [**size:>=30000**](https://github.com/search?q=size%3A%3E%3D30000&type=Repositories) sucht Repositorys mit einer Größe von mindestens 30 MB. | +| | [**size:<50**](https://github.com/search?q=size%3A%3C50&type=Repositories) sucht Repositorys mit einer Größe von weniger als 50 KB. | +| | [**size:50..120**](https://github.com/search?q=size%3A50..120&type=Repositories) sucht Repositorys mit einer Größe zwischen 50 KB und 120 KB. | + +## Suche nach Anzahl der Follower + +You can filter repositories based on the number of users who follow the repositories, using the `followers` qualifier with greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." + +| Qualifizierer | Beispiel | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| followers:n | [**node followers:>=10000**](https://github.com/search?q=node+followers%3A%3E%3D10000) findet Repositorys mit mehr als 10.000 Followern und die das Wort „node" enthalten. | +| | [**styleguide linter followers:1..10**](https://github.com/search?q=styleguide+linter+followers%3A1..10&type=Repositories) sucht Repositorys mit 1 bis 10 Followern, die „styleguide linter“ enthalten. | + +## Suche nach Anzahl der Forks + +The `forks` qualifier specifies the number of forks a repository should have, using greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." + +| Qualifizierer | Beispiel | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | +| forks:n | [**forks:5**](https://github.com/search?q=forks%3A5&type=Repositories) sucht Repositorys mit genau fünf Forks. | +| | [**forks:>=205**](https://github.com/search?q=forks%3A%3E%3D205&type=Repositories) sucht Repositorys mit mindestens 205 Forks. | +| | [**forks:<90**](https://github.com/search?q=forks%3A%3C90&type=Repositories) sucht Repositorys mit weniger als 90 Forks. | +| | [**forks:10..20**](https://github.com/search?q=forks%3A10..20&type=Repositories) sucht Repositorys mit 10 bis 20 Forks. | + +## Suche nach Anzahl der Sterne + +You can search repositories based on the number of stars the repositories have, using greater than, less than, and range qualifiers. For more information, see "[Saving repositories with stars](/github/getting-started-with-github/saving-repositories-with-stars)" and "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." + +| Qualifizierer | Beispiel | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| stars:n | [**stars:500**](https://github.com/search?utf8=%E2%9C%93&q=stars%3A500&type=Repositories) sucht Repositorys mit genau 500 Sternen. | +| | [**stars:10..20**](https://github.com/search?q=stars%3A10..20+size%3A%3C1000&type=Repositories) sucht Repositorys mit 10 bis 20 Sternen und einer Größe von weniger als 1000 KB. | +| | [**stars:>=500 fork:true language:php**](https://github.com/search?q=stars%3A%3E%3D500+fork%3Atrue+language%3Aphp&type=Repositories) sucht Repositorys, darunter auch Fork-Repositorys, mit mindestens 500 Sternen, die in PHP geschrieben sind. | + +## Suche nach dem Erstellungs- oder letzten Änderungsdatum eines Repositorys + +Du kannst Repositorys nach dem Zeitpunkt der Erstellung oder letzten Änderung filtern. Für die Suche nach dem Erstellungsdatum verwende den Qualifizierer `created`, für die Suche nach dem letzten Änderungsdatum den Qualifizierer `pushed`. Der Qualifizierer `pushed` gibt eine Repository-Liste sortiert nach dem letzten Commit in einem beliebigen Branch der Repositorys zurück. + +Beide Qualifizierer verwenden als Parameter ein Datum. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifizierer | Beispiel | +| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| created:YYYY-MM-DD | [**webos created:<2011-01-01**](https://github.com/search?q=webos+created%3A%3C2011-01-01&type=Repositories) sucht Repositorys, die das Wort „webos“ enthalten und vor 2011 erstellt wurden. | +| pushed:YYYY-MM-DD | [**css pushed:>2013-02-01**](https://github.com/search?utf8=%E2%9C%93&q=css+pushed%3A%3E2013-02-01&type=Repositories) sucht Repositorys, die das Wort „css“ enthalten und deren letzter Push nach Januar 2013 erfolgt ist. | +| | [**case pushed:>=2013-03-06 fork:only**](https://github.com/search?q=case+pushed%3A%3E%3D2013-03-06+fork%3Aonly&type=Repositories) sucht ausschließlich Fork-Repositorys, die das Wort „case“ enthalten und deren letzter Push im März 2013 oder später erfolgt ist. | + +## Suche nach Sprache + +You can search repositories based on the language of the code in the repositories. + +| Qualifizierer | Beispiel | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| language:LANGUAGE | [**rails language:javascript**](https://github.com/search?q=rails+language%3Ajavascript&type=Repositories) sucht Repositorys, die das Wort „rails“ enthalten und in JavaScript geschrieben sind. | + +## Suche nach Thema + +You can find all of the repositories that are classified with a particular topic. Weitere Informationen finden Sie unter „[Repository mit Themen klassifizieren](/github/administering-a-repository/classifying-your-repository-with-topics)“. + +| Qualifizierer | Beispiel | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| topic:TOPIC | [**topic:jekyll**](https://github.com/search?utf8=%E2%9C%93&q=topic%3Ajekyll&type=Repositories&ref=searchresults) sucht Repositorys, die durch das Thema „jekyll“ klassifiziert wurden. | + +## Suche nach Anzahl der Themen + +You can search repositories by the number of topics that have been applied to the repositories, using the `topics` qualifier along with greater than, less than, and range qualifiers. For more information, see "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)" and "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." + +| Qualifizierer | Beispiel | +| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | +| topics:n | [**topics:5**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A5&type=Repositories&ref=searchresults) sucht Repositorys mit fünf Themen. | +| | [**topics:>3**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A%3E3&type=Repositories&ref=searchresults) sucht Repositorys mit mehr als drei Themen. | + +{% ifversion fpt or ghes %} + +## Suche nach Lizenz + +You can search repositories by the type of license in the repositories. You must use a license keyword to filter repositories by a particular license or license family. Weitere Informationen finden Sie unter „[Ein Repository lizenzieren](/github/creating-cloning-and-archiving-repositories/licensing-a-repository)“. + +| Qualifizierer | Beispiel | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| license:LICENSE_KEYWORD | [**license:apache-2.0**](https://github.com/search?utf8=%E2%9C%93&q=license%3Aapache-2.0&type=Repositories&ref=searchresults) sucht Repositorys, die unter Apache License 2.0 lizenziert sind. | + +{% endif %} + +## Search by repository visibility + +You can filter your search based on the visibility of the repositories. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." + +| Qualifier | Example | ------------- | ------------- |{% ifversion fpt or ghes %} | `is:public` | [**is:public org:github**](https://github.com/search?q=is%3Apublic+org%3Agithub&type=Repositories) matches public repositories owned by {% data variables.product.company_short %}.{% endif %} | `is:internal` | [**is:internal test**](https://github.com/search?q=is%3Ainternal+test&type=Repositories) matches internal repositories that you can access and contain the word "test". | `is:private` | [**is:private pages**](https://github.com/search?q=is%3Aprivate+pages&type=Repositories) matches private repositories that you can access and contain the word "pages." + +{% ifversion fpt %} + +## Suche auf Basis der Spiegelung eines Repositorys + +You can search repositories based on whether the repositories are mirrors and hosted elsewhere. Weitere Informationen findest du unter „[Möglichkeiten finden, Beiträge an Open-Source auf {% data variables.product.prodname_dotcom %} zu leisten](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)." + +| Qualifizierer | Beispiel | +| -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `mirror:true` | [**mirror:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Atrue+GNOME&type=) matches repositories that are mirrors and contain the word "GNOME." | +| `mirror:false` | [**mirror:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Afalse+GNOME&type=) matches repositories that are not mirrors and contain the word "GNOME." | + +{% endif %} + +## Suche auf Basis der Archivierung eines Repositorys + +You can search repositories based on whether or not the repositories are archived. For more information, see "[Archiving repositories](/repositories/archiving-a-github-repository/archiving-repositories)." + +| Qualifizierer | Beispiel | +| ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `archived:true` | [**archived:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Atrue+GNOME&type=) matches repositories that are archived and contain the word "GNOME." | +| `archived:false` | [**archived:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Afalse+GNOME&type=) matches repositories that are not archived and contain the word "GNOME." | + +{% ifversion fpt %} + +## Suche nach Anzahl der Issues mit der Kennzeichnung `good first issue` oder `help wanted` + +Mit den Qualifizierern `good-first-issues:>n` und `help-wanted-issues:>n` kannst Du Repositorys mit einer Mindestanzahl an Issues mit der Kennzeichnung `good-first-issue` oder `help-wanted` suchen. Weitere Informationen findest Du auf „[Ermutigen hilfreicher Beiträge zu Deinem Projekt über Kennzeichnungen](/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels)." + +| Qualifizierer | Beispiel | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `good-first-issues:>n` | [**good-first-issues:>2 javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+good-first-issues%3A%3E2&type=) sucht Repositorys mit mehr als zwei Issues mit der Kennzeichnung `good-first-issue`, die das Wort „javascript“ enthalten. | +| `help-wanted-issues:>n` | [**help-wanted-issues:>4 react**](https://github.com/search?utf8=%E2%9C%93&q=react+help-wanted-issues%3A%3E4&type=) sucht Repositorys mit mehr als vier Issues mit der Kennzeichnung `help-wanted`, die das Wort „React“ enthalten. | + +## Search based on ability to sponsor + +You can search for repositories whose owners can be sponsored on {% data variables.product.prodname_sponsors %} with the `is:sponsorable` qualifier. Weitere Informationen findest Du unter „[Informationen zu {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)“. + +You can search for repositories that have a funding file using the `has:funding-file` qualifier. For more information, see "[About FUNDING files](/github/administering-a-repository/managing-repository-settings/displaying-a-sponsor-button-in-your-repository#about-funding-files)." + +| Qualifizierer | Beispiel | +| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `is:sponsorable` | [**is:sponsorable**](https://github.com/search?q=is%3Asponsorable&type=Repositories) matches repositories whose owners have a {% data variables.product.prodname_sponsors %} profile. | +| `has:funding-file` | [**has:funding-file**](https://github.com/search?q=has%3Afunding-file&type=Repositories) matches repositories that have a FUNDING.yml file. | + +{% endif %} + +## Weiterführende Informationen + +- „[Suchergebnisse sortieren](/search-github/getting-started-with-searching-on-github/sorting-search-results/)“ +- „[Forks durchsuchen](/search-github/searching-on-github/searching-in-forks)“ diff --git a/translations/de-DE/content/search-github/searching-on-github/searching-github-marketplace.md b/translations/de-DE/content/search-github/searching-on-github/searching-github-marketplace.md new file mode 100644 index 0000000000..92a4b6161f --- /dev/null +++ b/translations/de-DE/content/search-github/searching-on-github/searching-github-marketplace.md @@ -0,0 +1,38 @@ +--- +title: Durchsuchen des GitHub Marketplace +intro: 'Du kannst nach Apps und Aktionen suchen, die auf {% data variables.product.prodname_marketplace %} verfügbar sind.' +versions: + fpt: '*' +topics: + - GitHub search +redirect_from: + - /github/searching-for-information-on-github/searching-github-marketplace + - /github/searching-for-information-on-github/searching-on-github/searching-github-marketplace +shortTitle: Search GitHub Marketplace +--- + +## Informationen zur Suche auf {% data variables.product.prodname_marketplace %} + +Du kannst Apps und Aktionen auf {% data variables.product.prodname_marketplace %} auf zwei verschiedene Arten finden: + +- Suche in {% data variables.product.prodname_marketplace %}. +- Suche über alles von {% data variables.product.prodname_dotcom_the_website %} und filtere dann die Resultate. + +## Suche in {% data variables.product.prodname_marketplace %} + +1. Klicke im obersten Bereich einer beliebigen Seite auf **Marketplace** (Marktplatz). ![Link zu Marketplace](/assets/images/help/search/marketplace-link.png) +2. Gib ein beliebiges Schlüsselwort ein und drücke **Eingabe**. ![Suche nach Linter auf{% data variables.product.prodname_marketplace %}](/assets/images/help/search/marketplace-apps-and-actions-search-field.png) +3. Optional kannst du Dein Ergebnisse filtern, indem Du auf eine oder mehrere Optionen in der linken Seitenleiste klickst. + +## Suche über {% data variables.product.prodname_dotcom_the_website %} + +Jedes Mal, wenn du über alles von {% data variables.product.prodname_dotcom_the_website %} suchst, kannst Du die Resultate filtern, um passende Apps und Aktionen von {% data variables.product.prodname_marketplace %} zu sehen. + +1. Navigiere zu „https://github.com/search“. +2. Gib ein beliebiges Schlüsselwort ein und drücke **Eingabe**. ![Suchfeld](/assets/images/help/search/search-field.png) +3. Klicke in der linken Seitenleiste auf **Marketplace**. ![Suchergebnisse für Linter mit hervorgehobener Option "Marketplace-Seitenmenü"](/assets/images/help/search/marketplace-left-side-navigation.png) + +## Weiterführende Informationen + +- „[Informationen zu {% data variables.product.prodname_marketplace %}](/github/customizing-your-github-workflow/about-github-marketplace)“ +- „[Aktionen von {% data variables.product.prodname_marketplace %} in Deinem Workflow verwenden](/actions/automating-your-workflow-with-github-actions/using-actions-from-github-marketplace-in-your-workflow)" diff --git a/translations/de-DE/content/search-github/searching-on-github/searching-in-forks.md b/translations/de-DE/content/search-github/searching-on-github/searching-in-forks.md new file mode 100644 index 0000000000..2b25c2334e --- /dev/null +++ b/translations/de-DE/content/search-github/searching-on-github/searching-in-forks.md @@ -0,0 +1,32 @@ +--- +title: Forks durchsuchen +intro: '[Forks](/articles/about-forks) werden in Suchergebnissen standardmäßig nicht berücksichtigt. Du kannst aber wählen, dass Forks in Repository-Suchen und, sofern sie bestimmte Kriterien erfüllen, auch in Codesuchen eingeschlossen werden.' +redirect_from: + - /articles/searching-in-forks + - /github/searching-for-information-on-github/searching-in-forks + - /github/searching-for-information-on-github/searching-on-github/searching-in-forks +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +Um Forks in die Ergebnisse von [Repository-Suchen](/search-github/searching-on-github/searching-for-repositories) einzuschließen, musst Du Deiner Abfrage `fork:true` oder `fork:only` hinzufügen. + +Bei [Codesuchen](/search-github/searching-on-github/searching-code) werden Forks nur indiziert, wenn für sie mehr Sterne vergeben wurden als für das dem Fork übergeordnete Repository. Code in Forks, die weniger Sterne als das übergeordnete Repository aufweisen, können nicht durchsucht werden. Wenn Du Forks mit mehr Sternen als das übergeordnete Repository in den Ergebnissen von Codesuchen aufnehmen möchtest, musst du Deiner Abfrage `fork:true` oder `fork:only` hinzufügen. + +Der Qualifizierer `fork:true` findet alle Ergebnisse, die mit Deiner Suchabfrage übereinstimmen, auch diejenigen aus Forks. Der Qualifizierer `fork:only` findet Ergebnisse, die mit Deiner Suchabfrage übereinstimmen, _nur_ in Forks. + +| Qualifizierer | Beispiel | +| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `fork:true` | [**github fork:true**](https://github.com/search?q=github+fork%3Atrue&type=Repositories) gleicht alle Repositorys mit dem Wort „github“ ab, auch Forks. | +| | [**android language:java fork:true**](https://github.com/search?q=android+language%3Ajava+fork%3Atrue&type=Code) sucht Java-Code mit dem Wort „android“ sowohl in Forks als auch in normalen Repositorys. | +| `fork:only` | [**github fork:only**](https://github.com/search?q=github+fork%3Aonly&type=Repositories) gleicht alle Fork-Repositorys ab, die das Wort „github“ enthalten. | +| | [**forks:>500 fork:only**](https://github.com/search?q=forks%3A%3E500+fork%3Aonly&type=Repositories) sucht Repositorys mit mehr als 500 Forks und gibt nur diejenigen zurück, die Forks sind. | + +## Weiterführende Informationen + +- „[Informationen zu Forks](/articles/about-forks)“ +- „[Informationen zur Suche auf GitHub](/search-github/getting-started-with-searching-on-github/about-searching-on-github)“ diff --git a/translations/de-DE/content/search-github/searching-on-github/searching-issues-and-pull-requests.md b/translations/de-DE/content/search-github/searching-on-github/searching-issues-and-pull-requests.md new file mode 100644 index 0000000000..12d9bb9444 --- /dev/null +++ b/translations/de-DE/content/search-github/searching-on-github/searching-issues-and-pull-requests.md @@ -0,0 +1,343 @@ +--- +title: Issues und Pull Requests durchsuchen +intro: 'Auf {% data variables.product.product_name %} können Sie nach Issues und Pull Requests suchen und die Suchergebnisse mit den folgenden Suchkennzeichnern in beliebiger Kombination eingrenzen.' +redirect_from: + - /articles/searching-issues/ + - /articles/searching-issues-and-pull-requests + - /github/searching-for-information-on-github/searching-issues-and-pull-requests + - /github/searching-for-information-on-github/searching-on-github/searching-issues-and-pull-requests +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +shortTitle: Search issues & PRs +--- + +Sie können Issues und Pull Requests global auf {% data variables.product.product_name %} oder in einer bestimmten Organisation durchsuchen. Weitere Informationen findest Du unter „[Informationen zur Suche auf {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github).“ + +{% tip %} + +**Tips:**{% ifversion ghes or ghae %} + - Dieser Artikel enthält Beispielsuchen für die Website {% data variables.product.prodname_dotcom %}.com. Die gleichen Suchfilter kannst Du jedoch auch auf {% data variables.product.product_location %} verwenden.{% endif %} + - Eine Liste mit Suchsyntax, die Du jedem Qualifizierer hinzufügen kannst, um Deine Ergebnisse zu verbessern, findest Du unter „[Grundlagen der Suchsyntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)“. + - Schließe Suchbegriffe, die aus mehreren Wörtern bestehen, in Anführungszeichen ein. Möchtest Du beispielsweise nach Issues mit der Kennzeichnung „In progress“ suchen, gib `label:"in progress"` ein. Bei der Suche wird die Groß-/Kleinschreibung ignoriert. + - {% data reusables.search.search_issues_and_pull_requests_shortcut %} + + {% endtip %} + +## Suche nur nach Issues oder nur nach Pull Requests + +Die Suche auf {% data variables.product.product_name %} gibt standardmäßig sowohl Issues als auch Pull Requests zurück. Mit dem Qualifizierer `type` oder `is` kannst Du in den Suchergebnissen jedoch auch nur nach Issues oder nur nach Pull Requests filtern. + +| Qualifizierer | Beispiel | +| ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `type:pr` | [**cat type:pr**](https://github.com/search?q=cat+type%3Apr&type=Issues) sucht Pull Requests, die das Wort „cat“ enthalten. | +| `type:issue` | [**github commenter:defunkt type:issue**](https://github.com/search?q=github+commenter%3Adefunkt+type%3Aissue&type=Issues) sucht Issues, die das Wort „github“ enthalten und vom Benutzer @defunkt kommentiert wurden. | +| `is:pr` | [**event is:pr**](https://github.com/search?utf8=%E2%9C%93&q=event+is%3Apr&type=) sucht Pull Requests, die das Wort „event“ enthalten. | +| `is:issue` | [**is:issue label:bug is:closed**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aissue+label%3Abug+is%3Aclosed&type=) sucht geschlossene Issues mit der Kennzeichnung „bug“. | + +## Suche nach Titel, Textteil oder Kommentaren + +Mit dem Qualifizierer `in` kannst Du Deine Suche entweder auf den Titel, auf den Textteil, auf Kommentare oder auf eine beliebige Kombination derselben eingrenzen. Ohne diesen Qualifizierer werden Titel, Textteil und Kommentare durchsucht. + +| Qualifizierer | Beispiel | +| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `in:title` | [**warning in:title**](https://github.com/search?q=warning+in%3Atitle&type=Issues) sucht Issues, deren Titel das Wort „warning“ enthält. | +| `in:body` | [**error in:title,body**](https://github.com/search?q=error+in%3Atitle%2Cbody&type=Issues) sucht Issues, deren Titel oder Textteil das Wort „error“ enthält. | +| `in:comments` | [**shipit in:comments**](https://github.com/search?q=shipit+in%3Acomment&type=Issues) sucht Issues, deren Kommentare das Wort „shipit“ enthalten. | + +## Suche innerhalb der Repositorys eines Benutzers oder einer Organisation + +Wenn Du Issues und Pull Requests in allen Repositorys suchst, die einem bestimmten Benutzer oder einer bestimmten Organisation gehören, verwende den Qualifizierer `user` respektive `org`. Für die Suche nach Issues und Pull Requests in einem bestimmten Repository verwende den Qualifizierer `repo`. + +{% data reusables.pull_requests.large-search-workaround %} + + +| Qualifizierer | Beispiel | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**user:defunkt ubuntu**](https://github.com/search?q=user%3Adefunkt+ubuntu&type=Issues) sucht Issues, die das Wort „ubuntu“ enthalten, aus Repositorys, die dem Benutzer @defunkt gehören. | +| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=Issues&utf8=%E2%9C%93) sucht Issues aus Repositorys, die der Organisation GitHub gehören. | +| 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) sucht Issues aus dem Projekt shumway des Benutzers @mozilla, welche vor März 2012 erstellt wurden. | + + + +## Suche nach Öffnungsstatus + +Mit dem Qualifizierer `state` oder `is` kannst Du Issues und Pull Requests danach filtern, ob sie noch offen oder bereits geschlossen sind. + +| Qualifizierer | Beispiel | +| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `state:open` | [**libraries state:open mentions:vmg**](https://github.com/search?utf8=%E2%9C%93&q=libraries+state%3Aopen+mentions%3Avmg&type=Issues) sucht offene Issues, die @vmg erwähnen und das Wort „libraries“ enthalten. | +| `state:closed` | [**design state:closed in:body**](https://github.com/search?utf8=%E2%9C%93&q=design+state%3Aclosed+in%3Abody&type=Issues) sucht geschlossene Issues, die im Textteil das Wort „design“ enthalten. | +| `is:open` | [**performance is:open is:issue**](https://github.com/search?q=performance+is%3Aopen+is%3Aissue&type=Issues) sucht offene Issues, die das Wort „performance“ enthalten. | +| `is:closed` | [**android is:closed**](https://github.com/search?utf8=%E2%9C%93&q=android+is%3Aclosed&type=) sucht geschlossene Issues und Pull Requests, die das Wort „android“ enthalten. | + +## Filter by repository visibility + +You can filter by the visibility of the repository containing the issues and pull requests using the `is` qualifier. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." + +| Qualifier | Example | ------------- | ------------- |{% ifversion fpt or ghes %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Issues) matches issues and pull requests in public repositories.{% endif %}{% ifversion fpt or ghes or ghae %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Issues) matches issues and pull requests in internal repositories.{% endif %} | `is:private` | [**is:private cupcake**](https://github.com/search?q=is%3Aprivate+cupcake&type=Issues) matches issues and pull requests that contain the word "cupcake" in private repositories you can access. + +## Suche nach Autor + +Der Qualifizierer `author` sucht Issues und Pull Requests, die von einem bestimmten Benutzer oder Integrationskonto erstellt wurden. + +| Qualifizierer | Beispiel | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| author:USERNAME | [**cool author:gjtorikian**](https://github.com/search?q=cool+author%3Agjtorikian&type=Issues) matches issues and pull requests with the word "cool" that were created by @gjtorikian. | +| | [**bootstrap in:body author:mdo**](https://github.com/search?q=bootstrap+in%3Abody+author%3Amdo&type=Issues) matches issues written by @mdo that contain the word "bootstrap" in the body. | +| author:app/USERNAME | [**author:app/robot**](https://github.com/search?q=author%3Aapp%2Frobot&type=Issues) matches issues created by the integration account named "robot." | + +## Suche nach Bearbeiter + +Der Qualifizierer `assignee` sucht Issues und Pull Requests, die einem bestimmten Benutzer zugewiesen sind. Nach Issues und Pull Requests mit _beliebigem_ Bearbeiter kannst Du nicht suchen. Du kannst jedoch nach [Issues und Pull Requests suchen, denen kein Bearbeiter zugewiesen ist](#search-by-missing-metadata). + +| Qualifizierer | Beispiel | +| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| assignee:USERNAME | [**assignee:vmg repo:libgit2/libgit2**](https://github.com/search?utf8=%E2%9C%93&q=assignee%3Avmg+repo%3Alibgit2%2Flibgit2&type=Issues) matches issues and pull requests in libgit2's project libgit2 that are assigned to @vmg. | + +## Suche nach Erwähnung + +Der Qualifizierer `mentions` sucht Issues, in denen ein bestimmter Benutzer erwähnt wird. Weitere Informationen findest Du unter „[Personen und Teams erwähnen](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams).“ + +| Qualifizierer | Beispiel | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| mentions:USERNAME | [**resque mentions:defunkt**](https://github.com/search?q=resque+mentions%3Adefunkt&type=Issues) matches issues with the word "resque" that mention @defunkt. | + +## Suche nach Teamerwähnung + +Mit dem Qualifizierer `team` kannst du innerhalb von Organisationen und Teams, zu denen Du gehörst, Issues oder Pull Requests suchen, die ein bestimmtes Team innerhalb der Organisation @erwähnen. Ersetze in den folgenden Beispielen die Namen durch den Namen Deiner Organisation und Deines Teams, um eine Suche durchzuführen. + +| Qualifizierer | Beispiel | +| ------------------------- | ----------------------------------------------------------------------------------------------------- | +| team:ORGNAME/TEAMNAME | **team:jekyll/owners** matches issues where the `@jekyll/owners` team is mentioned. | +| | **team:myorg/ops is:open is:pr** matches open pull requests where the `@myorg/ops` team is mentioned. | + +## Suche nach Kommentierer + +Der Qualifizierer `commenter` sucht Issues, die einen Kommentar eines bestimmten Benutzers enthalten. + +| Qualifizierer | Beispiel | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| commenter:USERNAME | [**github commenter:defunkt org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Adefunkt+org%3Agithub&type=Issues) matches issues in repositories owned by GitHub, that contain the word "github," and have a comment by @defunkt. | + +## Suche nach beteiligtem Benutzer + +Mit dem Qualifizierer `involves` kannst Du Issues suchen, an denen auf die eine oder andere Weise ein bestimmter Benutzer beteiligt ist. Der Qualifizierer `involves` ist ein logisches ODER zwischen den Qualifizierern `author`, `assignee`, `mentions` und `commenter` für einen einzelnen Benutzer. Dieser Qualifizierer sucht also Issues und Pull Requests, die von einem bestimmten Benutzer erstellt wurden, diesem zugewiesen sind, diesen erwähnen oder in denen dieser Benutzer einen Kommentar hinterlassen hat. + +| Qualifizierer | Beispiel | +| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 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) sucht Issues, an denen @mdo beteiligt ist, die im Textteil jedoch nicht das Wort „bootstrap“ enthalten. | + +{% ifversion fpt or ghes or ghae %} +## Suche nach verknüpften Issues und Pull Request +Du kannst Deine Ergebnisse auf Issues einschränken, die mit einem Pull-Request verknüpft sind, indem Du eine schließende Referenz verwendest, oder auf Pull-Requests, die mit einem Issue verbunden sind, den der Pull-Request schließen kann. + +| Qualifizierer | Beispiel | +| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `linked:pr` | [**repo:desktop/desktop is:open linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+linked%3Apr) findet offene Issues im `desktop/desktop`-Repository, die mit einer schließenden Referenz zu einem Pull Request verknüpft sind. | +| `linked:issue` | [**repo:desktop/desktop is:closed linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aclosed+linked%3Aissue) findet geschlossene Pull Requests im `desktop/desktop`-Repository, die zu einem Issue verknüpft waren, den der Pull Request möglicherweise geschlossen hat. | +| `-linked:pr` | [**repo:desktop/desktop is:open -linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Apr) findet offene Issues im `desktop/desktop`-Repository, die nicht mit einer schließenden Referenz zu einem Pull Request verknüpft sind. | +| `-linked:issue` | [**repo:desktop/desktop is:open -linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Aissue) findet offene Pull Requests im `desktop/desktop`-Repository, die nicht zu einem Issue verknüpft sind, die der Pull Request möglicherweise schließen kann. +{% endif %} + +## Suche nach Kennzeichnung + +Mit dem Kennzeichner `label` können Sie Ihre Suchergebnisse nach Kennzeichnungen eingrenzen. Da Issues verschiedene Kennzeichnungen aufweisen können, können Sie für jeden Issue einen eigenen Kennzeichner auflisten. + +| Qualifizierer | Beispiel | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| label:LABEL | [**label:"help wanted" language:ruby**](https://github.com/search?utf8=%E2%9C%93&q=label%3A%22help+wanted%22+language%3Aruby&type=Issues) sucht Issues in Ruby-Repositorys mit der Kennzeichnung „help wanted“. | +| | [**broken in:body -label:bug label:priority**](https://github.com/search?q=broken+in%3Abody+-label%3Abug+label%3Apriority&type=Issues) sucht Issues, deren Textteil das Wort „broken“ enthält, die nicht die Kennzeichnung „bug“ aufweisen, *jedoch* die Kennzeichnung „priority“ enthalten. | +| | [**label:bug label:resolved**](https://github.com/search?l=&q=label%3Abug+label%3Aresolved&type=Issues) matches issues with the labels "bug" and "resolved."{% ifversion fpt or ghes > 3.2 or ghae-next %} +| | [**label:bug,resolved**](https://github.com/search?q=label%3Abug%2Cresolved&type=Issues) matches issues with the label "bug" or the label "resolved."{% endif %} + +## Suche nach Meilenstein + +Der Kennzeichner `milestone` sucht Issues oder Pull Requests, die innerhalb eines Repositorys Teil eines [Meilensteins](/articles/about-milestones) sind. + +| Qualifizierer | Beispiel | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| milestone:MILESTONE | [**milestone:"overhaul"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22overhaul%22&type=Issues) sucht Issues in einem Meilenstein mit dem Namen „overhaul“. | +| | [**milestone:"bug fix"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22bug+fix%22&type=Issues) sucht Issues in einem Meilenstein mit dem Namen „bug fix“. | + +## Suche nach Projektboard + +Mit dem Kennzeichner `project` können Sie Issues suchen, die innerhalb eines Repositorys oder einer Organisation einem bestimmten [Projektboard](/articles/about-project-boards/) zugeordnet sind. Projektboards werden anhand ihrer Projektboardnummer gesucht. Die Nummer eines Projektboards befindet sich am Ende von dessen URL. + +| Qualifizierer | Beispiel | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------- | +| project:PROJECT_BOARD | **project:github/57** sucht Issues, die GitHub gehören und dem Projektboard 57 der Organisation zugeordnet sind. | +| project:REPOSITORY/PROJECT_BOARD | **project:github/linguist/1** sucht Issues, die Projektboard 1 im Repository „linguist“ von @github zugeordnet sind. | + +## Suche nach Commit-Status + +Sie können Pull Requests nach dem Status ihrer Commits filtern. Dieser Filter ist besonders nützlich, wenn Sie die [Status-API](/rest/reference/repos#statuses) oder einen CI-Dienst verwenden. + +| Qualifizierer | Beispiel | +| ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `status:pending` | [**language:go status:pending**](https://github.com/search?utf8=%E2%9C%93&q=language%3Ago+status%3Apending) sucht offene Pull Requests in Go-Repositorys, deren Status „Pending“ (Ausstehend) ist. | +| `status:success` | [**is:open status:success finally in:body**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aopen+status%3Asuccess+finally+in%3Abody&type=Issues) sucht offene Pull Requests mit dem Status „Successful“ (Erfolgreich), die im Textteil das Wort „finally“ enthalten. | +| `status:failure` | [**created:2015-05-01..2015-05-30 status:failure**](https://github.com/search?utf8=%E2%9C%93&q=created%3A2015-05-01..2015-05-30+status%3Afailure&type=Issues) sucht Pull Requests, die im Mai 2015 geöffnet wurden und den Status „Failed“ (Fehlgeschlagen) aufweisen. | + +## Suche nach Commit-SHA + +Wenn Sie den spezifischen SHA-Hash eines Commits kennen, können Sie ihn für die Suche nach Pull Requests verwenden, die diesen SHA enthalten. Die SHA-Syntax besteht aus mindestens sieben Zeichen. + +| Qualifizierer | Beispiel | +| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| SHA | [**e1109ab**](https://github.com/search?q=e1109ab&type=Issues) sucht Pull Requests, deren Commit-SHAs mit `e1109ab` beginnen. | +| | [**0eff326d6213c is:merged**](https://github.com/search?q=0eff326d+is%3Amerged&type=Issues) sucht zusammengeführte Pull Requests, deren Commit-SHAs mit `0eff326d6213c` beginnen. | + +## Suche nach Branch-Name + +Sie können Pull Requests nach dem Branch filtern, aus dem sie stammen (Head-Branch) oder in den sie gemergt werden (Basis-Branch). + +| Qualifizierer | Beispiel | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| head:HEAD_BRANCH | [**head:change is:closed is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=head%3Achange+is%3Aclosed+is%3Aunmerged) sucht Pull Requests, die aus Branches geöffnet wurden, deren Namen mit „change“ beginnen, die aber inzwischen geschlossen sind. | +| base:BASE_BRANCH | [**base:gh-pages**](https://github.com/search?utf8=%E2%9C%93&q=base%3Agh-pages) sucht Pull Requests, die in den Branch `gh-pages` zusammengeführt werden. | + +## Suche nach Sprache + +Mit dem Kennzeichner `language` können Sie Issues und Pull Requests in Repositorys suchen, die in einer bestimmten Programmiersprache geschrieben sind. + +| Qualifizierer | Beispiel | +| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | +| language:LANGUAGE | [**language:ruby state:open**](https://github.com/search?q=language%3Aruby+state%3Aopen&type=Issues) sucht offene Issues in Ruby-Repositorys. | + +## Suche nach Anzahl der Kommentare + +Mit dem Qualifizierer `comments` in Verbindung mit [„Größer-als“-, „Kleiner-als“- oder Bereichsqualifizierern](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax) kannst Du nach der Anzahl der Kommentare filtern. + +| Qualifizierer | Beispiel | +| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| comments:n | [**state:closed comments:>100**](https://github.com/search?q=state%3Aclosed+comments%3A%3E100&type=Issues) sucht geschlossene Issues mit mehr als 100 Kommentaren. | +| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Issues) sucht Issues mit 500 bis 1.000 Kommentaren. | + +## Suche nach Anzahl der Interaktionen + +Mit dem Qualifizierer `interactions` kannst Du Issues und Pull Requests nach der Anzahl ihrer Interaktionen filtern. Zur Angabe der Anzahl der Interaktionen verwende [„Größer-als“-, „Kleiner-als“- oder Bereichsqualifizierer](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). Interaktionen sind Reaktionen und Kommentare zu einem Issue oder Pull Request. + +| Qualifizierer | Beispiel | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| interactions:n | [** interactions:>2000**](https://github.com/search?q=interactions%3A%3E2000) sucht Issues oder Pull Requests mit mehr als 2.000 Interaktionen. | +| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) sucht Issues oder Pull Requests mit 500 bis 1.000 Interaktionen. | + +## Suche nach Anzahl der Reaktionen + +Mit dem Qualifizierer `reactions` kannst Du Issues und Pull Requests nach der Anzahl ihrer Reaktionen filtern. Zur Angabe der Anzahl der Reaktionen verwende [„Größer-als“-, „Kleiner-als“- oder Bereichsqualifizierer](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). + +| Qualifizierer | Beispiel | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- | +| reactions:n | [** reactions:>1000**](https://github.com/search?q=reactions%3A%3E1000&type=Issues) sucht Issues mit mehr als 1.000 Reaktionen. | +| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) sucht Issues mit 500 bis 1.000 Reaktionen. | + +## Suche nach Pull-Request-Entwürfen +Sie können nach Pull-Request-Entwürfen suchen. Weitere Informationen findest Du unter „[Informationen zu Pull Requests](/articles/about-pull-requests#draft-pull-requests).“ + +| Qualifier | Example | ------------- | -------------{% ifversion fpt or ghes or ghae %} | `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) findet Pull Requests, die bereit sind für den Review.{% else %} | `is:draft` | [**is:draft**](https://github.com/search?q=is%3Adraft) findet Pull-Request-Entwürfe.{% endif %} + +## Suche nach Review-Status und Reviewer eines Pull-Requests + +Du kannst Pull Requests nach ihrem [Review-Status](/articles/about-pull-request-reviews) (_none_ (keiner), _required_ (erforderlich), _approved_ (genehmigt) oder _changes requested_ (Änderungen angefordert)), nach Reviewer und nach angefordertem Reviewer filtern. + +| Qualifizierer | Beispiel | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `review:none` | [**type:pr review:none**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Anone&type=Issues) sucht Pull Requests, die nicht geprüft wurden. | +| `review:required` | [**type:pr review:required**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Arequired&type=Issues) sucht Pull Requests, die vor dem Merge geprüft werden müssen. | +| `review:approved` | [**type:pr review:approved**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Aapproved&type=Issues) sucht Pull Requests, die von einem Reviewer genehmigt wurden. | +| `review:changes_requested` | [**type:pr review:changes_requested**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Achanges_requested&type=Issues) sucht Pull Requests, für die ein Reviewer Änderungen angefordert hat. | +| reviewed-by:USERNAME | [**type:pr reviewed-by:gjtorikian**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+reviewed-by%3Agjtorikian&type=Issues) sucht Pull-Requests, die von einer bestimmten Person geprüft wurden. | +| review-requested:USERNAME | [**type:pr review-requested:benbalter**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review-requested%3Abenbalter&type=Issues) sucht Pull Requests, für deren Review eine bestimmte Person angefordert wurde. Angeforderte Reviewer werden nicht mehr in den Suchergebnissen aufgeführt, sobald sie den Review eines Pull Request abgeschlossen haben. 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 or ghes > 3.2 %} +| 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) sucht Pull Requests, für deren Review das Team `atom/design` angefordert wurde. Angeforderte Reviewer werden nicht mehr in den Suchergebnissen aufgeführt, sobald sie den Review eines Pull Request abgeschlossen haben. | + +## Suche nach dem Datum der Erstellung oder letzten Änderung eines Issues oder Pull Requests + +Sie können Issues nach dem Zeitpunkt der Erstellung oder letzten Änderung filtern. Für die Suche nach dem Erstellungsdatum verwenden Sie den Kennzeichner `created`, für die Suche nach dem letzten Änderungsdatum den Kennzeichner `updated`. + +Beide Qualifizierer verwenden als Parameter ein Datum. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifizierer | Beispiel | +| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| created:YYYY-MM-DD | [**language:c# created:<2011-01-01 state:open**](https://github.com/search?q=language%3Ac%23+created%3A%3C2011-01-01+state%3Aopen&type=Issues) findet offene Issues, die vor 2011 erstellt wurden, in Repositorys die in C# geschrieben sind. | +| updated:YYYY-MM-DD | [**weird in:body updated:>=2013-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2013-02-01&type=Issues) findet Issues, die nach Januar 2013 aktualisiert wurden, mit dem Wort „weird" im Text. | + +## Suche nach dem Datum der Schließung eines Issues oder Pull Requests + +Mit dem Kennzeichner `closed` können Sie Issues und Pull Requests nach ihrem Schließungsdatum filtern. + +Der Kennzeichner verwendet als Parameter ein Datum. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifizierer | Beispiel | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| closed:YYYY-MM-DD | [**language:swift closed:>2014-06-11**](https://github.com/search?q=language%3Aswift+closed%3A%3E2014-06-11&type=Issues) findet Issues und Pull Requests in Swift-Sprache, die nach dem 11. Juni 2014 geschlossen wurden. | +| | [**data in:body closed:<2012-10-01**](https://github.com/search?utf8=%E2%9C%93&q=data+in%3Abody+closed%3A%3C2012-10-01+&type=Issues) findet Issues und Pull Requests mit dem Wort „data" im Text, die vor Oktober 2012 geschlossen wurden. | + +## Suche nach dem Merge-Datum eines Issues oder Pull Requests + +Mit dem Kennzeichner `merged` können Sie Pull Requests nach ihrem Merge-Datum filtern. + +Der Kennzeichner verwendet als Parameter ein Datum. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifizierer | Beispiel | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| merged:YYYY-MM-DD | [**language:javascript merged:<2011-01-01**](https://github.com/search?q=language%3Ajavascript+merged%3A%3C2011-01-01+&type=Issues) findet Pull Requests in JavaScript-Repositorys, die vor 2011 zusammengeführt wurden. | +| | [**fast in:title language:ruby merged:>=2014-05-01**](https://github.com/search?q=fast+in%3Atitle+language%3Aruby+merged%3A%3E%3D2014-05-01+&type=Issues) findet Pull Requests in Ruby-Sprache mit dem Wort „fast" im Titel, die nach April 2014 zusammengeführt wurden. | + +## Suche nach dem Merge-Status eines Pull Requests + +Mit dem Kennzeichner `is` können Sie Pull Requests danach filtern, ob sie gemergt oder ungemergt sind. + +| Qualifizierer | Beispiel | +| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `is:merged` | [**bugfix is:pr is:merged**](https://github.com/search?utf8=%E2%9C%93&q=bugfix+is%3Apr+is%3Amerged&type=) sucht zusammengeführte Pull Requests, die das Wort „bugfix“ enthalten. | +| `is:unmerged` | [**error is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=error+is%3Aunmerged&type=) sucht geschlossene Issues und Pull Requests, die das Wort „error“ enthalten. | + +## Suche auf Basis der Archivierung eines Repositorys + +Der Kennzeichner `archived` filtert Suchergebnisse danach, ob sich ein Issue oder Pull Request in einem archivierten Repository befindet. + +| Qualifizierer | Beispiel | +| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `archived:true` | [**archived:true GNOME**](https://github.com/search?q=archived%3Atrue+GNOME&type=) sucht Issues und Pull Requests mit dem Wort „GNOME“ in archivierten Repositorys, auf die Sie Zugriff haben. | +| `archived:false` | [**archived:false GNOME**](https://github.com/search?q=archived%3Afalse+GNOME&type=) sucht Issues und Pull Requests mit dem Wort „GNOME“ in nicht archivierten Repositorys, auf die Sie Zugriff haben. | + +## Suche nach dem Sperrstatus einer Unterhaltung + +Mit dem Kennzeichner `is` können Sie Issues oder Pull Requests mit gesperrten Unterhaltungen suchen. (siehe „[Unterhaltungen sperren](/communities/moderating-comments-and-conversations/locking-conversations)“) + +| Qualifizierer | Beispiel | +| ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `is:locked` | [**code of conduct is:locked is:issue archived:false**](https://github.com/search?q=code+of+conduct+is%3Alocked+is%3Aissue+archived%3Afalse) sucht in nicht archivierten Repositorys nach Issues oder Pull Requests, die die Wörter „code of conduct“ enthalten und eine gesperrte Unterhaltung aufweisen. | +| `is:unlocked` | [**code of conduct is:unlocked is:issue archived:false**](https://github.com/search?q=code+of+conduct+is%3Aunlocked+archived%3Afalse) sucht in nicht archivierten Repositorys nach Issues oder Pull Requests, die die Wörter „code of conduct“ enthalten und eine ungesperrte Unterhaltung aufweisen. | + +## Suche nach fehlenden Metadaten + +Mit dem Kennzeichner `no` können Sie Ihre Suche auf Issues und Pull Requests eingrenzen, in denen bestimmte Metadaten fehlen. Hierbei können Sie nach folgenden fehlenden Metadaten suchen: + +* Kennzeichnungen +* Meilensteine +* Bearbeiter +* Projekte + +| Qualifizierer | Beispiel | +| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `no:label` | [**priority no:label**](https://github.com/search?q=priority+no%3Alabel&type=Issues) sucht Issues und Pull Requests, die das Wort „priority“ enthalten und keine Kennzeichnungen aufweisen. | +| `no:milestone` | [**sprint no:milestone type:issue**](https://github.com/search?q=sprint+no%3Amilestone+type%3Aissue&type=Issues) sucht Issues, die das Wort „sprint“ enthalten und keinem Meilenstein zugeordnet sind. | +| `no:assignee` | [**important no:assignee language:java type:issue**](https://github.com/search?q=important+no%3Aassignee+language%3Ajava+type%3Aissue&type=Issues) sucht in Java-Repositorys nach Issues, die das Wort „important“ enthalten und keinem Bearbeiter zugeordnet sind. | +| `no:project` | [**build no:project**](https://github.com/search?utf8=%E2%9C%93&q=build+no%3Aproject&type=Issues) sucht Issues, die das Wort „build“ enthalten und keinem Projektboard zugeordnet sind. | + +## Weiterführende Informationen + +- „[Suchergebnisse sortieren](/search-github/getting-started-with-searching-on-github/sorting-search-results/)“ diff --git a/translations/de-DE/content/search-github/searching-on-github/searching-topics.md b/translations/de-DE/content/search-github/searching-on-github/searching-topics.md new file mode 100644 index 0000000000..53dd0aa398 --- /dev/null +++ b/translations/de-DE/content/search-github/searching-on-github/searching-topics.md @@ -0,0 +1,55 @@ +--- +title: Themen durchsuchen +intro: 'Auf {% data variables.product.product_name %} können Sie Themen suchen, die Repositorys zugeordnet sind.' +redirect_from: + - /articles/searching-topics + - /github/searching-for-information-on-github/searching-topics + - /github/searching-for-information-on-github/searching-on-github/searching-topics +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +## {% data variables.product.product_name %} nach Themen durchsuchen + +Sie können auf {% data variables.product.product_name %} Themen suchen, zugehörige Themen untersuchen und ermitteln, wie viele Repositorys einem bestimmten Thema zugeordnet sind. + +1. Navigiere zu „https://github.com/search“. +2. Gib ein Stichwort zum Thema ein. ![Suchfeld](/assets/images/help/search/search-field.png) +3. Klicke in der linken Seitenleiste auf **Topics** (Themen), um die Suche auf Themen einzuschränken. +{% ifversion fpt %} + ![Ergebnisseite der Suche nach Jekyll-Repositorys mit hervorgehobener Option „Topics“ (Themen) in der Seitenleiste](/assets/images/help/search/topic-left-side-navigation-dotcom.png){% else %} +![Jekyll repository search results page on dotcom with topics side-menu option highlighted](/assets/images/help/search/topic-left-side-navigation.png){% endif %} + +## Suche durch Qualifizierer eingrenzen + +Wenn Sie in Repositorys bestimmte Themen suchen, um zu Projekten beizutragen, oder in Erfahrung bringen möchten, welche Themen auf {% data variables.product.product_name %} besonders beliebt sind, können Sie Themen mit den Suchkennzeichnern `is:featured`, `is:curated`, `repositories:n` und `created:YYYY-MM-DD` durchsuchen. + +Der Suchkennzeichner `is:featured` grenzt das Suchergebnis auf die Themen mit den meisten Repositorys auf {% data variables.product.product_name %} ein. Diese Themen werden auch auf „https://github.com/topics/“ vorgestellt. + +Der Qualifizierer `is:curated` grenzt das Suchergebnis auf Themen ein, zu denen Community-Mitglieder zusätzliche Informationen hinzugefügt haben. For more information, see the [explore repository](https://github.com/github/explore). + +Mit dem Datumsparameter und dem Qualifizierer `created:` kannst Du Themen nach ihrem Erstellungsdatum filtern, und mit `repositories:n` kannst Du nach der Anzahl der einem Thema zugeordneten Repositorys filtern. Beide Qualifizierer arbeiten mit [„Größer als“-, „Kleiner als“- und Bereichsqualifizierern](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). + +{% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifizierer | Beispiel | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `is:curated` | [**is:curated javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+is%3Acurated&type=Topics) sucht kuratierte Themen, die das Wort „javascript“ enthalten. | +| `is:featured` | [**is:featured javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+is%3Afeatured&type=Topics) sucht Themen, die auf „https://github.com/topics/“ vorgestellt werden und das Wort „javascript“ enthalten. | +| `is:not-curated` | [**is:not-curated javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+is%3Anot-curated&type=Topics) sucht Themen ohne zusätzliche Informationen wie Beschreibung oder Logo, die das Wort „javascript“ enthalten. | +| `is:not-featured` | [**is:not-featured javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+is%3Anot-featured&type=Topics) sucht Themen, die nicht auf „https://github.com/topics/“ vorgestellt werden, aber das Wort „javascript“ enthalten. | +| `repositories:n` | [**repositories:>5000**](https://github.com/search?q=repositories%3A%3E5000) sucht Themen, denen mehr als 5.000 Repositorys zugeordnet sind. | +| created:YYYY-MM-DD | [**Serverless created:>2019-01-01**](https://github.com/search?q=Serverless+created%3A%3E2019-01-01&type=Topics) sucht Themen, die das Wort „serverless“ enthalten und nach 2018 erstellt wurden. | + +## Repositorys nach Themen durchsuchen + +Mit dem Qualifizierer `topic:` kannst Du nach allen einem bestimmten Thema zugeordneten Repositorys suchen. Weitere Informationen findest Du unter „[Nach Repositorys suchen](/search-github/searching-on-github/searching-for-repositories/#search-by-topic).“ + +## Weiterführende Informationen +- „[Repository mit Themen klassifizieren](/articles/classifying-your-repository-with-topics)“ diff --git a/translations/de-DE/content/search-github/searching-on-github/searching-users.md b/translations/de-DE/content/search-github/searching-on-github/searching-users.md new file mode 100644 index 0000000000..b8751722f6 --- /dev/null +++ b/translations/de-DE/content/search-github/searching-on-github/searching-users.md @@ -0,0 +1,106 @@ +--- +title: Benutzer durchsuchen +intro: 'Auf {% data variables.product.product_name %} können Sie Benutzer durchsuchen und die Suchergebnisse mit den folgenden Kennzeichnern der Benutzersuche in beliebiger Kombination eingrenzen.' +redirect_from: + - /articles/searching-users + - /github/searching-for-information-on-github/searching-users + - /github/searching-for-information-on-github/searching-on-github/searching-users +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +Sie können auf {% data variables.product.product_name %} global nach Benutzern suchen. Weitere Informationen findest Du unter „[Informationen zur Suche auf {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github).“ + +{% data reusables.search.syntax_tips %} + +## Suche nur nach Benutzern oder nur nach Organisationen + +Die Suche nach Benutzern gibt standardmäßig sowohl persönliche Konten als auch Organisationen zurück. Mit dem Qualifizierer `type` kannst Du die Suchergebnisse jedoch ausschließlich auf persönliche Konten oder ausschließlich auf Organisationen eingrenzen. + +| Qualifizierer | Beispiel | +| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `type:user` | [**mike in:name created:<2011-01-01 type:user**](https://github.com/search?q=mike+in:name+created%3A%3C2011-01-01+type%3Auser&type=Users) sucht persönliche Konten mit dem Namen „mike“, die vor 2011 erstellt wurden. | +| `type:org` | [**data in:email type:org**](https://github.com/search?q=data+in%3Aemail+type%3Aorg&type=Users) sucht Organisationen, deren E-Mail-Adresse des Wort „data“ enthält. | + +## Suche nach Kontoname, vollständigem Namen oder öffentlicher E-Mail-Adresse + +Du kannst Deine Suche mit den Qualifizierern `user` respektive `org` auf den Kontonamen eines Benutzers oder einer Organisation eingrenzen. + +Mit dem Qualifizierer `in` kannst Du die Suche auf den Benutzernamen (`login`), den vollständigen Namen oder die öffentliche E-Mail-Adresse eines Benutzers oder einer Organisation oder jede beliebige Kombination derselben eingrenzen. Ohne diesen Qualifizierer werden nur Benutzernamen und E-Mail-Adressen durchsucht. Aus Datenschutzgründen ist die Suche nach E-Mail-Domänen-Namen nicht möglich. + +| Qualifizierer | Beispiel | +| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `user:name` | [**user:octocat**](https://github.com/search?q=user%3Aoctocat&type=Users) sucht einen Benutzer mit dem Benutzernamen „octocat“. | +| `org:name` | [**org:electron type:users**](https://github.com/search?q=org%3Aelectron+type%3Ausers&type=Users) sucht den Kontonamen der Organisation Electron. | +| `in:login` | [**kenya in:login**](https://github.com/search?q=kenya+in%3Alogin&type=Users) sucht Benutzer, deren Benutzername das Wort „kenya“ enthält. | +| `in:name` | [**bolton in:name**](https://github.com/search?q=bolton+in%3Afullname&type=Users) sucht Benutzer, deren wirklicher Name das Wort „bolton“ enthält. | +| `fullname:firstname lastname` | [**fullname:nat friedman**](https://github.com/search?q=fullname%3Anat+friedman&type=Users) sucht einen Benutzer mit dem vollständigen Namen „Nat Friedman“. Hinweis: In diesem Suchkennzeichner werden Leerzeichen beachtet. | +| `in:email` | [**data in:email**](https://github.com/search?q=data+in%3Aemail&type=Users&utf8=%E2%9C%93) sucht Benutzer, deren E-Mail-Adresse das Wort „data“ enthält. | + +## Suche nach der Anzahl der Repositorys eines Benutzers + +Mit dem Qualifizierer `repos` kannst Du Benutzer nach der Anzahl der Repositorys filtern, die ihnen gehören. Zur Angabe der Anzahl der Repositorys verwende [„Größer-als“-, „Kleiner-als“- oder Bereichsqualifizierer](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). + +| Qualifizierer | Beispiel | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| repos:n | [**repos:>9000**](https://github.com/search?q=repos%3A%3E%3D9000&type=Users) findet Benutzer mit mehr als 9.000 Repositorys. | +| | [**bert repos:10..30**](https://github.com/search?q=bert+repos%3A10..30&type=Users) sucht Benutzer mit 10 bis 30 Repositorys, deren Benutzername oder wirklicher Name das Wort „bert“ enthält. | + +## Suche nach dem Dateipfad + +Du kannst Benutzer nach dem Standort suchen, der in ihrem Profil angegeben ist. + +| Qualifizierer | Beispiel | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| location:LOCATION | [**repos:1 location:iceland**](https://github.com/search?q=repos%3A1+location%3Aiceland&type=Users) sucht Benutzer, denen genau ein Repository gehört und die in Island leben. | + +## Suche nach der Repository-Sprache + +Mit dem Qualifizierer `language` kannst Du Benutzer auf Basis der Programmiersprache ihrer Repositorys suchen. + +| Qualifizierer | Beispiel | +| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| language:LANGUAGE | [**language:javascript location:russia**](https://github.com/search?q=language%3Ajavascript+location%3Arussia&type=Users) sucht Benutzer aus Russland, deren Repositorys primär in JavaScript geschrieben sind. | +| | [**jenny language:javascript in:fullname**](https://github.com/search?q=jenny+language%3Ajavascript+in%3Afullname&type=Users) sucht Benutzer, deren Repositorys primär in JavaScript geschrieben sind und deren vollständige Namen das Wort „jenny“ enthalten. | + +## Suche nach dem Erstellungsdatum eines Benutzerkontos + +Mit dem Qualifizierer `created` kannst Du Benutzer nach dem Datum ihres Beitritts zu {% data variables.product.product_name %} filtern. Der Qualifizierer verwendet als Parameter ein Datum. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifizierer | Beispiel | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| created:YYYY-MM-DD | [**created:<2011-01-01**](https://github.com/search?q=created%3A%3C2011-01-01&type=Users) findet Benutzer, die vor 2011 beigetreten sind. | +| | [**created:>=2013-05-11**](https://github.com/search?q=created%3A%3E%3D2013-05-11&type=Users) findet Benutzer, die am oder nach dem 11. Mai 2013 beigetreten sind. | +| | [**created:2013-03-06 location:london**](https://github.com/search?q=created%3A2013-03-06+location%3Alondon&type=Users) sucht Benutzer, die am 6. März 2013 beigetreten sind und als Standort London angeben. | +| | [**created:2010-01-01..2011-01-01 john in:login**](https://github.com/search?q=created%3A2010-01-01..2011-01-01+john+in%3Ausername&type=Users) sucht Benutzer, die in 2010 beigetreten sind und deren Benutzernamen das Wort „john“ enthalten. | + +## Suche nach Anzahl der Follower + +Mit dem Qualifizierer `followers` kannst Du Benutzer nach der Anzahl ihrer Follower filtern. Zur Angabe der Anzahl der Follower verwende die Syntax [„Größer als“-, „Kleiner als“- oder den Bereichsqualifizierer](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). + +| Qualifizierer | Beispiel | +| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| followers:n | [**followers:>=1000**](https://github.com/search?q=followers%3A%3E%3D1000&type=Users) findet Benutzer mit mehr als 1.000 Followern. | +| | [**sparkle followers:1..10**](https://github.com/search?q=sparkle+followers%3A1..10&type=Users) sucht Benutzer mit 1 bis 10 Followern, deren Name das Wort „sparkle“ enthält. | + +{% ifversion fpt %} + +## Search based on ability to sponsor + +You can search for users and organizations who can be sponsored on {% data variables.product.prodname_sponsors %} with the `is:sponsorable` qualifier. Weitere Informationen findest Du unter „[Informationen zu {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)“. + +| Qualifizierer | Beispiel | +| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `is:sponsorable` | [**is:sponsorable**](https://github.com/search?q=is%3Asponsorable&type=Users) matches users and organizations who have a {% data variables.product.prodname_sponsors %} profile. | + +{% endif %} + +## Weiterführende Informationen + +- „[Suchergebnisse sortieren](/search-github/getting-started-with-searching-on-github/sorting-search-results/)“ diff --git a/translations/de-DE/content/search-github/searching-on-github/searching-wikis.md b/translations/de-DE/content/search-github/searching-on-github/searching-wikis.md new file mode 100644 index 0000000000..97eb4a914b --- /dev/null +++ b/translations/de-DE/content/search-github/searching-on-github/searching-wikis.md @@ -0,0 +1,51 @@ +--- +title: Wikis durchsuchen +intro: 'Auf {% data variables.product.product_name %} können Sie Wikis durchsuchen und die Suchergebnisse mit den folgenden Kennzeichnern der Wiki-Suche in beliebiger Kombination eingrenzen.' +redirect_from: + - /articles/searching-wikis + - /github/searching-for-information-on-github/searching-wikis + - /github/searching-for-information-on-github/searching-on-github/searching-wikis +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +Sie können Wikis global auf {% data variables.product.product_name %} oder in bestimmten Repositorys oder Organisationen durchsuchen. Weitere Informationen findest Du unter „[Informationen zur Suche auf {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github).“ + +{% data reusables.search.syntax_tips %} + +## Suche innerhalb der Repositorys eines Benutzers oder einer Organisation + +Wenn Du Wiki-Seiten in allen Repositorys suchst, die einem bestimmten Benutzer oder einer bestimmten Organisation gehören, verwende den Qualifizierer `user` respektive `org`. Für die Suche nach Wiki-Seiten aus einem bestimmten Repository verwende den Qualifizierer `repo`. + +| Qualifizierer | Beispiel | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| user:USERNAME | [**user:defunkt**](https://github.com/search?q=user%3Adefunkt&type=Wikis) sucht Wiki-Seiten aus Repositorys, die dem Benutzer @defunkt gehören. | +| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=Wikis&utf8=%E2%9C%93) sucht Wiki-Seiten aus Repositorys, die der Organisation GitHub gehören. | +| repo:USERNAME/REPOSITORY | [**repo:defunkt/gibberish**](https://github.com/search?q=user%3Adefunkt&type=Wikis) sucht Wiki-Seiten aus dem Repository „gibberish“ des Benutzers @defunkt. | + +## Suche im Titel oder Text einer Wiki-Seite + +Der Qualifizierer `in` beschränkt die Suche auf ausschließlich den Titel oder ausschließlich den Textteil der Wiki-Seite. Ohne diesen Qualifizierer werden sowohl der Titel als auch der Textteil durchsucht. + +| Qualifizierer | Beispiel | +| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `in:title` | [**usage in:title**](https://github.com/search?q=usage+in%3Atitle&type=Wikis) sucht in den Titeln von Wiki-Seiten nach dem Wort „usage“. | +| `in:body` | [**installation in:body**](https://github.com/search?q=installation+in%3Abody&type=Wikis) sucht im Textteil von Wiki-Seiten nach dem Wort „installation“. | + +## Suche nach dem letzten Aktualisierungsdatum + +Der Qualifizierer `updated` beschränkt die Suche auf Wiki-Seiten, deren letztes Änderungsdatum innerhalb des angegebenen Datumbereichs liegt. + +{% data reusables.search.date_gt_lt %} + +| Qualifizierer | Beispiel | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| updated:YYYY-MM-DD | [**usage updated:>2016-01-01**](https://github.com/search?q=usage+updated%3A>2016-01-01&type=Wikis) findet Wiki-Seiten, die das Wort „usage" beinhalten und zuletzt nach dem 1. Januar 2016 angepasst wurden. | + +## Weiterführende Informationen + +- „[Suchergebnisse sortieren](/search-github/getting-started-with-searching-on-github/sorting-search-results/)“ diff --git a/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md index cd2da154c9..c05e4af82f 100644 --- a/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md +++ b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md @@ -30,6 +30,7 @@ shortTitle: Manage payment tiers 1. Optionally, to edit a draft tier, find the draft tier and click **Edit**. ![Edit button next to draft tier](/assets/images/help/sponsors/draft-tier-edit.png) {% data reusables.sponsors.click-add-tier %} {% data reusables.sponsors.tier-price-description %} +{% data reusables.sponsors.add-welcome-message %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} diff --git a/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md index e6aeb626f8..069fcd678a 100644 --- a/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md +++ b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md @@ -51,6 +51,7 @@ Um {% data variables.product.prodname_sponsors %} als ein einzelner Mitwirkender {% data reusables.sponsors.navigate-to-sponsor-tiers-tab %} {% data reusables.sponsors.click-add-tier %} {% data reusables.sponsors.tier-price-description %} +{% data reusables.sponsors.add-welcome-message %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} {% data reusables.sponsors.add-more-tiers %} diff --git a/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md index aad39461b8..144386aed3 100644 --- a/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md +++ b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md @@ -50,6 +50,7 @@ Nachdem {% data variables.product.prodname_dotcom %} Deine Bewerbung überprüft {% data reusables.sponsors.navigate-to-sponsor-tiers-tab %} {% data reusables.sponsors.click-add-tier %} {% data reusables.sponsors.tier-price-description %} +{% data reusables.sponsors.add-welcome-message %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} {% data reusables.sponsors.add-more-tiers %} diff --git a/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md index 0cf275239f..0e9c7a87b6 100644 --- a/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md +++ b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md @@ -37,6 +37,8 @@ The W-8 BEN and W-8 BEN-E tax forms ask for a "U.S. taxpayer identification numb If you are not a U.S. citizen or other U.S. person, including a resident alien individual, then you will usually need to provide the "Foreign tax identifying number". This is a tax identification number that your country of residence has issued you. +If your country of residence or billing country is India, then you can use your Permanent Account Number (PAN) as your tax identification number. + {% note %} **Note:** If your country does not require citizens to have a tax number issued by the government, then you can instead write "not legally required". @@ -56,6 +58,18 @@ If you are a taxpayer in the United States and earn more than 600 US dollars in {% data reusables.sponsors.sponsorships-not-tax-deductible %} +## Sales tax + +GitHub is providing information to assist you in calculating your sales tax obligations. This information is not personalized to your country or tax situation and we recommend you talk to a professional to understand your specific obligations. However, we'd like to provide some high-level information to help you understand the general principles of digital sales tax. + +In most countries around the world, sales tax for digital transactions is based on the location of the recipient, not on the seller. For example, if you are a maintainer in the United States and you provide a taxable benefit to a Sponsor in Germany, German sales tax would apply. + +Sales tax is generally only applicable when a good or service of value is being provided. Goodwill/general support/undying appreciation is not normally taxable. + +In the US, both B2B (business-to-business) and B2C (business-to-consumer) are subject to sales tax. + +In the EU and most other countries and regions, B2C sales are subject to sales tax. B2B sales are not subject to tax. C2C and C2B sales where a consumer is not registered for VAT are not taxable. + ## Weiterführende Informationen - [Sponsoren und Sponsoring anzeigen](/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships) diff --git a/translations/de-DE/data/glossaries/external.yml b/translations/de-DE/data/glossaries/external.yml index 3b288ee05e..801c27999d 100644 --- a/translations/de-DE/data/glossaries/external.yml +++ b/translations/de-DE/data/glossaries/external.yml @@ -9,7 +9,7 @@ - term: Kontowiederherstellungstoken description: >- - Die als Teil einer Kontowiederherstellungseinrichtung gespeicherten Authentifizierungsanmeldeinformationen, die als „Recover Accounts Elsewhere“ bezeichnet werden, mit denen Sie diese Backup-Anmeldeinformationen speichern können. + **Deprecated and will be disabled December 1st, 2021.** The authentication credential stored as part of an account recovery setup called Recover Accounts Elsewhere that allows you to store this backup credential. - term: API-Vorschau description: >- @@ -574,7 +574,7 @@ - term: Recover Accounts Elsewhere description: >- - Ermöglicht Benutzern, einen zusätzlichen Sicherheitsfaktor zu ihrem GitHub-Konto für den Fall hinzuzufügen, dass sie ihren Zugriff auf ihre Zwei-Faktor-Authentifizierungsmethode oder ihre Wiederherstellungscodes verlieren. Benutzer können ihr GitHub-Konto ihrem Facebook-Konto zuordnen, indem sie die Authentifizierungsanmeldeinformationen in der Form eines Kontowiederherstellungstokens für ihr GitHub-Konto mit Facebook speichern. + **Deprecated and will be disabled December 1st, 2021.** Allows users to add an extra security factor to their GitHub account in case they lose access to their two-factor authentication method or recovery codes. Users can associate their GitHub account with their Facebook account by storing an authentication credential in the form of an account recovery token for their GitHub account with Facebook. - term: Wiederherstellungscode description: Ein Code, der Ihnen dabei hilft, den Zugriff auf Ihr GitHub-Konto zurückzuerlangen. diff --git a/translations/de-DE/data/learning-tracks/actions.yml b/translations/de-DE/data/learning-tracks/actions.yml index 86fee141fc..0ab85040f7 100644 --- a/translations/de-DE/data/learning-tracks/actions.yml +++ b/translations/de-DE/data/learning-tracks/actions.yml @@ -7,6 +7,7 @@ getting_started: - /actions/learn-github-actions/finding-and-customizing-actions - /actions/learn-github-actions/essential-features-of-github-actions - /actions/learn-github-actions/managing-complex-workflows + - /actions/learn-github-actions/reusing-workflows - /actions/learn-github-actions/security-hardening-for-github-actions featured_track: true continuous_integration: diff --git a/translations/de-DE/data/release-notes/enterprise-server/2-20/15.yml b/translations/de-DE/data/release-notes/enterprise-server/2-20/15.yml index aa3c664487..eb611e3aa6 100644 --- a/translations/de-DE/data/release-notes/enterprise-server/2-20/15.yml +++ b/translations/de-DE/data/release-notes/enterprise-server/2-20/15.yml @@ -1,9 +1,9 @@ +--- date: '2020-08-26' sections: security_fixes: - >- - **CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2883, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700, - https://github.com/github/pages/pull/2890, https://github.com/github/pages/pull/2898, https://github.com/github/pages/pull/2909, https://github.com/github/pages/pull/2891, https://github.com/github/pages/pull/2884, https://github.com/github/pages/pull/2889 {% endcomment %} + **CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2883, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700, https://github.com/github/pages/pull/2890, https://github.com/github/pages/pull/2898, https://github.com/github/pages/pull/2909, https://github.com/github/pages/pull/2891, https://github.com/github/pages/pull/2884, https://github.com/github/pages/pull/2889 {% endcomment %} - '**MEDIUM:** An improper access control vulnerability was identified that allowed authenticated users of the instance to determine the names of unauthorized private repositories given their numerical IDs. This vulnerability did not allow unauthorized access to any repository content besides the name. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.22 and has been assigned [CVE-2020-10517](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10517). The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/151987, https://github.com/github/github/pull/151713 {% endcomment %}' - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21852, https://github.com/github/enterprise2/pull/21828, https://github.com/github/enterprise2/pull/22153, https://github.com/github/enterprise2/pull/21920, https://github.com/github/enterprise2/pull/22215, https://github.com/github/enterprise2/pull/22190 {% endcomment %}' bugs: @@ -22,3 +22,4 @@ sections: - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - '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.' diff --git a/translations/de-DE/data/release-notes/enterprise-server/2-21/6.yml b/translations/de-DE/data/release-notes/enterprise-server/2-21/6.yml index 03c71afb3a..f51e7b415f 100644 --- a/translations/de-DE/data/release-notes/enterprise-server/2-21/6.yml +++ b/translations/de-DE/data/release-notes/enterprise-server/2-21/6.yml @@ -1,9 +1,9 @@ +--- date: '2020-08-26' sections: security_fixes: - >- - **CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2882, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700, - https://github.com/github/pages/pull/2889, https://github.com/github/pages/pull/2899, https://github.com/github/pages/pull/2903, https://github.com/github/pages/pull/2890, https://github.com/github/pages/pull/2891, https://github.com/github/pages/pull/2884 {% endcomment %} + **CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2882, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700, https://github.com/github/pages/pull/2889, https://github.com/github/pages/pull/2899, https://github.com/github/pages/pull/2903, https://github.com/github/pages/pull/2890, https://github.com/github/pages/pull/2891, https://github.com/github/pages/pull/2884 {% endcomment %} - '**MEDIUM:** An improper access control vulnerability was identified that allowed authenticated users of the instance to determine the names of unauthorized private repositories given their numerical IDs. This vulnerability did not allow unauthorized access to any repository content besides the name. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.22 and has been assigned [CVE-2020-10517](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10517). The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/151986, https://github.com/github/github/pull/151713 {% endcomment %}' - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21853, https://github.com/github/enterprise2/pull/21828, https://github.com/github/enterprise2/pull/22154, https://github.com/github/enterprise2/pull/21920, https://github.com/github/enterprise2/pull/22216, https://github.com/github/enterprise2/pull/22190 {% endcomment %}' bugs: @@ -25,3 +25,4 @@ sections: - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - "Configuring a repository's permission to `Triage` or `Maintain` fails with an error message." + - '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.' diff --git a/translations/de-DE/data/release-notes/enterprise-server/2-22/22.yml b/translations/de-DE/data/release-notes/enterprise-server/2-22/22.yml new file mode 100644 index 0000000000..0bc20acf57 --- /dev/null +++ b/translations/de-DE/data/release-notes/enterprise-server/2-22/22.yml @@ -0,0 +1,15 @@ +--- +date: '2021-09-24' +sections: + security_fixes: + - '**HIGH:** A path traversal vulnerability was identified in {% data variables.product.prodname_ghe_server %} that could be exploited when building a {% data variables.product.prodname_pages %} site. User-controlled configuration options used by {% data variables.product.prodname_pages %} were not sufficiently restricted and made it possible to read files on the {% data variables.product.prodname_ghe_server %} instance. To exploit this vulnerability, an attacker would need 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.1.8 and was fixed in 3.1.8, 3.0.16, and 2.22.22. This is the result of an incomplete fix for CVE-2021-22867. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned CVE-2021-22868. {% comment %} https://github.com/github/pages/pull/3359, https://github.com/github/pages/pull/3357 {% endcomment %}' + bugs: + - 'The {% data variables.product.prodname_github_connect %} configuration of the source instance was always restored to new instances even when the `--config` option for `ghe-restore` was not used. This would lead to a conflict with the {% data variables.product.prodname_github_connect %} connection and license synchronization if both the source and destination instances were online at the same time. {% comment %} https://github.com/github/github/pull/192247, https://github.com/github/github/pull/191951, https://github.com/github/enterprise2/pull/26870, https://github.com/github/backup-utils/pull/770, https://github.com/github/connected-enterprise/issues/208 {% endcomment %}' + - 'Fixes {% data variables.product.prodname_pages %} builds so they take into account the NO_PROXY setting of the appliance. This is relevant to appliances configured with an HTTP proxy only. {% comment %} https://github.com/github/github/pull/192380 {% endcomment %}' + known_issues: + - On a freshly set up {% data variables.product.prodname_ghe_server %} without any users, an attacker could create the first admin user. + - Custom firewall rules are removed during the upgrade process. + - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. + - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters. + - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_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. diff --git a/translations/de-DE/data/release-notes/enterprise-server/3-0/16.yml b/translations/de-DE/data/release-notes/enterprise-server/3-0/16.yml new file mode 100644 index 0000000000..c40eac2c61 --- /dev/null +++ b/translations/de-DE/data/release-notes/enterprise-server/3-0/16.yml @@ -0,0 +1,18 @@ +--- +date: '2021-09-24' +sections: + security_fixes: + - '**HIGH:** A path traversal vulnerability was identified in {% data variables.product.prodname_ghe_server %} that could be exploited when building a {% data variables.product.prodname_pages %} site. User-controlled configuration options used by {% data variables.product.prodname_pages %} were not sufficiently restricted and made it possible to read files on the {% data variables.product.prodname_ghe_server %} instance. To exploit this vulnerability, an attacker would need 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.1.8 and was fixed in 3.1.8, 3.0.16, and 2.22.22. This is the result of an incomplete fix for CVE-2021-22867. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned CVE-2021-22868. {% comment %} https://github.com/github/pages/pull/3360, https://github.com/github/pages/pull/3357 {% endcomment %}' + - '**MEDIUM:** An improper access control vulnerability in {% data variables.product.prodname_ghe_server %} allowed a workflow job to execute in a self-hosted runner group it should not have had access to. This affects customers using self-hosted runner groups for access control. A repository with access to one enterprise runner group could access all of the enterprise runner groups within the organization because of improper authentication checks during the request. This could cause code to be run unintentionally by the incorrect runner group. This vulnerability affected {% data variables.product.prodname_ghe_server %} versions from 3.0.0 to 3.0.15 and 3.1.0 to 3.1.7 and was fixed in 3.0.16 and 3.1.8 releases. It has been assigned CVE-2021-22869. {% comment %} https://github.com/github/enterprise2/pull/27003 {% endcomment %}' + bugs: + - 'Resque worker counts were displayed incorrectly during maintenance mode. {% comment %} https://github.com/github/enterprise2/pull/26898, https://github.com/github/enterprise2/pull/26883 {% endcomment %}' + - 'Allocated memcached memory could be zero in clustering mode. {% comment %} https://github.com/github/enterprise2/pull/26927, https://github.com/github/enterprise2/pull/26832 {% endcomment %}' + - 'Fixes {% data variables.product.prodname_pages %} builds so they take into account the NO_PROXY setting of the appliance. This is relevant to appliances configured with an HTTP proxy only. (update 2021-09-30) {% comment %} https://github.com/github/pages/pull/3360 {% endcomment %}' + known_issues: + - On a freshly set up {% data variables.product.prodname_ghe_server %} without any users, an attacker could create the first admin user. + - Custom firewall rules are removed during the upgrade process. + - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. + - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters. + - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results. + - 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/de-DE/data/release-notes/enterprise-server/3-1/8.yml b/translations/de-DE/data/release-notes/enterprise-server/3-1/8.yml new file mode 100644 index 0000000000..77ecdaab2d --- /dev/null +++ b/translations/de-DE/data/release-notes/enterprise-server/3-1/8.yml @@ -0,0 +1,20 @@ +--- +date: '2021-09-24' +sections: + security_fixes: + - '**HIGH:** A path traversal vulnerability was identified in {% data variables.product.prodname_ghe_server %} that could be exploited when building a {% data variables.product.prodname_pages %} site. User-controlled configuration options used by {% data variables.product.prodname_pages %} were not sufficiently restricted and made it possible to read files on the {% data variables.product.prodname_ghe_server %} instance. To exploit this vulnerability, an attacker would need 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.1.8 and was fixed in 3.1.8, 3.0.16, and 2.22.22. This is the result of an incomplete fix for CVE-2021-22867. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned CVE-2021-22868. {% comment %} https://github.com/github/pages/pull/3361, https://github.com/github/pages/pull/3357 {% endcomment %}' + - '**MEDIUM:** An improper access control vulnerability in {% data variables.product.prodname_ghe_server %} allowed a workflow job to execute in a self-hosted runner group it should not have had access to. This affects customers using self-hosted runner groups for access control. A repository with access to one enterprise runner group could access all of the enterprise runner groups within the organization because of improper authentication checks during the request. This could cause code to be run unintentionally by the incorrect runner group. This vulnerability affected {% data variables.product.prodname_ghe_server %} versions from 3.0.0 to 3.0.15 and 3.1.0 to 3.1.7 and was fixed in 3.0.16 and 3.1.8 releases. It has been assigned CVE-2021-22869. {% comment %} https://github.com/github/enterprise2/pull/27013 {% endcomment %}' + bugs: + - 'Resque worker counts were displayed incorrectly during maintenance mode. {% comment %} https://github.com/github/enterprise2/pull/26899, https://github.com/github/enterprise2/pull/26883 {% endcomment %}' + - 'Allocated memcached memory could be zero in clustering mode. {% comment %} https://github.com/github/enterprise2/pull/26928, https://github.com/github/enterprise2/pull/26832 {% endcomment %}' + - 'Non-empty binary files displayed an incorrect file type and size on the pull request "Files" tab. {% comment %} https://github.com/github/github/pull/192810, https://github.com/github/github/pull/172284, https://github.com/github/coding/issues/694 {% endcomment %}' + - 'Fixes {% data variables.product.prodname_pages %} builds so they take into account the NO_PROXY setting of the appliance. This is relevant to appliances configured with an HTTP proxy only. (update 2021-09-30) {% comment %} https://github.com/github/pages/pull/3360 {% endcomment %}' + known_issues: + - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. + - On a freshly set up {% data variables.product.prodname_ghe_server %} without any users, an attacker could create the first admin user. + - Custom firewall rules are removed during the upgrade process. + - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. + - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters. + - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results. + - If {% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_server %}, teardown of a replica node with `ghe-repl-teardown` will succeed, but may return `ERROR:Running migrations`. + - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. diff --git a/translations/de-DE/data/release-notes/enterprise-server/3-2/0-rc1.yml b/translations/de-DE/data/release-notes/enterprise-server/3-2/0-rc1.yml index 430e555020..e186c81135 100644 --- a/translations/de-DE/data/release-notes/enterprise-server/3-2/0-rc1.yml +++ b/translations/de-DE/data/release-notes/enterprise-server/3-2/0-rc1.yml @@ -1,7 +1,7 @@ --- date: '2021-09-09' release_candidate: true -deprecated: false +deprecated: true intro: 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. sections: features: diff --git a/translations/de-DE/data/release-notes/enterprise-server/3-2/0.yml b/translations/de-DE/data/release-notes/enterprise-server/3-2/0.yml new file mode 100644 index 0000000000..dab08920a6 --- /dev/null +++ b/translations/de-DE/data/release-notes/enterprise-server/3-2/0.yml @@ -0,0 +1,221 @@ +--- +date: '2021-09-28' +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: Custom patterns for secret scanning + notes: + - | + {% data variables.product.prodname_GH_advanced_security %} customers can now specify custom patterns for secret scanning. When a new pattern is specified, secret scanning searches a repository's entire Git history for the pattern, as well as any new commits. + + User defined patterns are in beta for {% data variables.product.prodname_ghe_server %} 3.2. They can be defined at the repository, organization, and enterprise levels. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." + - + heading: Security overview for Advanced Security (beta) + notes: + - | + {% data variables.product.prodname_GH_advanced_security %} customers now have an organization-level view of the application security risks detected by {% data variables.product.prodname_code_scanning %}, {% data variables.product.prodname_dependabot %}, and {% data variables.product.prodname_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 {% data variables.product.prodname_secret_scanning %} alerts at the organization level. Similar views for {% data variables.product.prodname_dependabot %} and {% data variables.product.prodname_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 review (beta) + notes: + - | + {% data variables.product.prodname_GH_advanced_security %} customers can now see a rich diff of the dependencies changed in a pull request. 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 these dependencies. 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)." + - + heading: GitHub Actions environments + notes: + - | + Environments, environment protection rules, and environment secrets are now generally available for {% data variables.product.prodname_actions %} on {% data variables.product.product_name %}. For more information, see "[Environments](/actions/reference/environments)." + + ![Environment protection rules](/assets/images/enterprise/3.2/release-notes/actions-environments.png) + - + heading: SSH authentication with security keys + notes: + - | + SSH authentication using a FIDO2 security key is now supported when you add a `sk-ecdsa-sha2-nistp256@openssh.com` or `sk-ssh-ed25519@openssh.com` SSH key to your account. SSH security keys store secret key material on a separate hardware device that requires verification, such as a tap, to operate. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)." + - + heading: 'Dark and dark dimmed themes' + notes: + - | + Dark and dark dimmed themes are now available for the web UI. {% data variables.product.product_name %} will match your system preferences when you haven't set theme preferences in {% data variables.product.product_name %}. You can also choose which themes are active during the day and night. For more information, see "[Managing your theme settings](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)." + + ![Dark and dark dimmed themes](https://user-images.githubusercontent.com/33528647/114629560-d2231f80-9c86-11eb-9bde-cc301a97040d.gif) + - + heading: 'Approving unverified domains for email notifications' + notes: + - 'Domains that are not able to be verified can now be approved for email notification routing. Enterprise and organization owners will be able to approve domains and immediately augment their email notification restriction policy, allowing notifications to be sent to collaborators, consultants, acquisitions, or other partners. For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#about-approval-of-domains)" and "[Restricting email notifications for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise#restricting-email-notifications-for-your-enterprise-account)."' + - + heading: 'Git Credential Manager (GCM) secure credential storage and multi-factor authentication support' + notes: + - | + Git Credential Manager (GCM) Core versions 2.0.452 and later now provide security-hardened credential storage and multi-factor authentication support for {% data variables.product.product_name %}. + + GCM Core with support for {% data variables.product.product_name %} is included with [Git for Windows](https://gitforwindows.org) versions 2.32 and later. GCM Core is not included with Git for macOS or Linux, but can be installed separately. For more information, see the [latest release](https://github.com/microsoft/Git-Credential-Manager-Core/releases/) and [installation instructions](https://github.com/microsoft/Git-Credential-Manager-Core/releases/) in the `microsoft/Git-Credential-Manager-Core` repository. + changes: + - + heading: Administration Changes + notes: + - A 'User Agent Referrer Policy' setting has been added to the enterprise settings. This allows an admin to set a stricter `Referrer-Policy` to hide the hostname of a {% data variables.product.prodname_ghe_server %} installation from external sites. The setting is disabled by default and is tracked by audit log events for staff and enterprise owners when enabled or disabled. For more information, see "[Configuring Referrer Policy for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)." + - The MySQL health check was changed to use `mysqladmin ping` instead of TCP checks, which removes some unnecessary noise in the MySQL error log. Also, Orchestrator failover checks were improved to prevent unnecessary MySQL failovers when applying cluster config changes. + - 'The Resque service, which supports background job processing, has been replaced with Aqueduct Lite. This change makes the job system easier to manage and should not affect the user experience. For the new administration and debugging commands for Aqueduct, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-aqueduct)."' + - + heading: Token Changes + notes: + - | + The format of authentication tokens for {% data variables.product.product_name %} has changed. The change affects the format of personal access tokens and access tokens for {% data variables.product.prodname_oauth_apps %}, as well as user-to-server, server-to-server, and refresh tokens for {% data variables.product.prodname_github_apps %}. + + The different token types now have unique identifiable prefixes, which allows for secret scanning to detect the tokens so that you can mitigate the impact of someone accidentally committing a token to a repository. {% data variables.product.company_short %} recommends updating existing tokens as soon as possible. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github#githubs-token-formats)" and "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)." + - + heading: 'Repositories changes' + notes: + - Repositories on user profiles and organization profiles now support sorting by star count. + - When viewing the commit history of a single file, you can now click {% octicon "file-code" aria-label="The code icon" %} to view that file at the selected point in history. + - When a submodule is defined with a relative path in {% data variables.product.product_location %}, the submodule is now clickable in the web UI. Clicking the submodule in the web UI will take you to the linked repository. Previously, only submodules with absolute URLs were clickable. This is supported for relative paths for repositories with the same owner that follow the pattern ../REPOSITORY or relative paths for repositories with a different owner that follow the pattern ../OWNER/REPOSITORY. For more information about working with submodules, see [Working with submodules](https://github.blog/2016-02-01-working-with-submodules/) on {% data variables.product.prodname_blog %}. + - 'The web UI can now be used to synchronize an out-of-date branch of a fork with the fork''s upstream branch. If there are no merge conflicts between the branches, the branch is updated either by fast-forwarding or by merging from upstream. If there are conflicts, you will be prompted to create a pull request to resolve the conflicts. For more information, see "[Syncing a fork](/github/collaborating-with-pull-requests/working-with-forks/syncing-a-fork#syncing-a-fork-from-the-web-ui)."' + - + heading: 'Markdown changes' + notes: + - 'The markdown editor used when creating or editing a release in a repository now has a text-editing toolbar. For more information, see "[Managing releases in a repository](/github/administering-a-repository/releasing-projects-on-github/managing-releases-in-a-repository#creating-a-release)."' + - Uploading video files is now supported everywhere you write Markdown on {% data variables.product.product_name %}. Share demos, reproduction steps, and more in your issue and pull request comments, as well as in Markdown files within repositories, such as READMEs. For more information, see "[Attaching files](/github/writing-on-github/working-with-advanced-formatting/attaching-files)." + - Markdown files will now automatically generate a table of contents in the header when there are 2 or more headings. The table of contents is interactive and links to the selected section. All 6 Markdown heading levels are supported. + - 'There is a new keyboard shortcut, `cmd+e` on macOS or `ctrl+e` on Windows, to insert codeblocks in Markdown files, issues, pull requests, and comments.' + - 'Appending `?plain=1` to the URL for any Markdown file will now display the file without rendering and with line numbers. The plain view can be used to link other users to specific lines. For example, appending `?plain=1#L52` will highlight line 52 of a plain text Markdown file. For more information, "[Creating a permanent link to a code snippet](/github/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet#linking-to-markdown)."' + - + heading: 'Issues and pull requests changes' + notes: + - With the [latest version of Octicons](https://github.com/primer/octicons/releases), the states of issues and pull requests are now more visually distinct so you can scan their status more easily. For more information, see [{% data variables.product.prodname_blog %}](https://github.blog/changelog/2021-06-08-new-issue-and-pull-request-state-icons/). + - 'A new "Require conversation resolution before merging" branch protection rule and "Conversations" menu is now available. Easily discover your pull request comments from the "Files changed" tab, and require that all your pull request conversations are resolved before merging. For more information, see "[About pull request reviews](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews#discovering-and-navigating-conversations)" and "[About protected branches](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-conversation-resolution-before-merging)."' + - To prevent the merge of unexpected changes after auto-merge is enabled for a pull request, auto-merge is now disabled automatically when new changes are pushed by a user without write access to the repository. Users without write access can still update the pull request with changes from the base branch when auto-merge is enabled. To prevent a malicious user from using a merge conflict to introduce unexpected changes to the pull request, auto-merge for the pull request is disabled if the update causes a merge conflict. For more information about auto-merge, see "[Automatically merging a pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." + - 'People with maintain permissions 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 permissions 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. + - When a review is requested from a team of more than 100 people, developers are now shown a confirmation dialog box in order to prevent unnecessary notifications for large teams. + - Back-tick `code blocks` are now supported in issue titles, pull request titles, and in any place issue and pull request titles are referenced in {% data variables.product.prodname_ghe_server %}. + - 'Events for pull requests and pull request reviews are now included in the audit log for both [enterprises](/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise) and [organizations](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization). These events help admins better monitor pull request activity and help ensure security and compliance requirements are being met. Events can be viewed from the web UI, exported as CSV or JSON, or accessed via REST API. You can also search the audit log for specific pull request events. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#pull_request-category-actions)."' + - + heading: 'Branches changes' + notes: + - | + The default branch name for new repositories is now `main`. Existing repositories are not impacted by this change. If users, organization owners, or enterprise owners have previously specified a default branch for new repositories, they are also not impacted. + + If you want to set a different default branch name, you can do so in the [user](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories), [organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization), or [enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name) settings. + - | + Branches, including the default branch, can now be renamed using the the {% data variables.product.product_name %} web UI. When a branch is renamed, any open pull requests and draft releases targeting the renamed branch will be retargeted automatically, and branch protection rules that explicitly reference the renamed branch will be updated. + + Admin permissions are required to rename the default branch, but write permissions are sufficient to rename other branches. + + To help make the change as seamless as possible for users: + + * A notice is shown to contributors, maintainers, and admins on the repository homepage with instructions for updating their local repository. + * Web requests to the old branch will be redirected. + * A "moved permanently" HTTP response will be returned to REST API calls. + * An informational message is displayed to Git command line users that push to the old branch. + + For more information, see "[Renaming a branch](/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch)." + - + heading: 'GitHub Actions changes' + notes: + - '{% data variables.product.prodname_actions %} now lets you control the permissions granted to the `GITHUB_TOKEN` secret. The `GITHUB_TOKEN` is an automatically-generated secret that lets you make authenticated calls to the API for {% data variables.product.product_name %} in your workflow runs. {% data variables.product.prodname_actions %} generates a new token for each job and expires the token when a job completes. The token usually has `write` permissions to a number of [API endpoints](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token), except in the case of pull requests from forks, which are always `read`. These new settings allow you to follow a principle of least privilege in your workflows. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token)."' + - '{% data variables.product.prodname_cli %} 1.9 and later allows you to work with {% data variables.product.prodname_actions %} in your terminal. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-04-15-github-cli-1-9-enables-you-to-work-with-github-actions-from-your-terminal/).' + - 'The audit log now includes events associated with {% data variables.product.prodname_actions %} workflow runs. This data provides administrators with a greatly expanded data set for security and compliance audits. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#workflows-category-actions)."' + - '{% data variables.product.prodname_ghe_server %} 3.2 contains performance improvements for job concurrency with {% data variables.product.prodname_actions %}. For more information on the new performance targets on 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)."' + - + heading: 'GitHub Packages changes' + notes: + - Any package or package version for {% data variables.product.prodname_registry %} can now be deleted from {% data variables.product.product_name %}'s web UI. You can also undo the deletion of any package or package version within 30 days. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)". + - + heading: 'Dependabot and Dependency graph changes' + notes: + - 'The dependency graph can now be enabled using the Management Console, rather than needing to run a command in the administrative shell. For more information, see "[Enabling alerts for vulnerable dependencies {% data variables.product.prodname_ghe_server %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server#enabling-the-dependency-graph-and-dependabot-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."' + - Notifications for multiple {% data variables.product.prodname_dependabot_alerts %} are now grouped together if they're discovered at the same time. This significantly reduces the volume of {% data variables.product.prodname_dependabot %} alert notifications that users receive. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-03-18-grouped-dependabot-alert-notifications/). + - 'Dependency graph and {% data variables.product.prodname_dependabot_alerts %} now support Go modules. {% data variables.product.prodname_ghe_server %} analyzes a repository''s `go.mod` files to understand the repository’s dependencies. Along with security advisories, the dependency graph provides the information needed to alert developers to vulnerable dependencies. For more information about enabling the dependency graph on private repositories, see "[Securing your repository](/code-security/getting-started/securing-your-repository#managing-the-dependency-graph)."' + - The default notification settings for security alerts have changed. Previously, if you had permission to view security alerts in a repository, you would receive notifications for that repository as long as your settings allowed for security alert notifications. Now, you must opt in to security alert notifications by watching the repository. You will be notified if you select `All Activity` or configure `Custom` to include `Security alerts`. All existing repositories will be automatically migrated to these new settings and you will continue to receive notifications; however, any new repositories will require opting-in by watching the repository. 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)" and "[Managing alerts from secret scanning](/code-security/secret-security/managing-alerts-from-secret-scanning)." + - + heading: 'Code scanning and secret scanning changes' + notes: + - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} now generates diagnostic information for all supported languages. This helps check the state of the created database to understand the status and quality of performed analysis. The diagnostic information is available starting in [version 2.5.6](https://github.com/github/codeql-cli-binaries/releases) of the [{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/). You can see the detailed diagnostic information in the {% data variables.product.prodname_actions %} logs for {% data variables.product.prodname_codeql %}. For more information, see "[Viewing code scanning logs](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs)."' + - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql_cli %} now supports analyzing several languages during a single build. This makes it easier to run code analysis to use CI/CD systems other than {% data variables.product.prodname_actions %}. The new mode of the `codeql database create` command is available starting [version 2.5.6](https://github.com/github/codeql-cli-binaries/releases) of the [{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/). For more information about setting this up, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-cli-in-your-ci-system)."' + - '{% data variables.product.prodname_code_scanning_capc %} alerts from all enabled tools are now shown in one consolidated list, so that you can easily prioritize across all alerts. You can view alerts from a specific tool by using the "Tool" filter, and the "Rule" and "Tag" filters will dynamically update based on your "Tool" selection.' + - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} now includes beta support for analyzing C++20 code. This is only available when building codebases with GCC on Linux. C++20 modules are not supported yet.' + - 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 for several languages ([C++](https://github.com/github/codeql/tree/main/cpp), [JavaScript](https://github.com/github/codeql/tree/main/javascript), [Python](https://github.com/github/codeql/tree/main/python), and [Java](https://github.com/github/codeql/tree/main/java)). As a result, {% data variables.product.prodname_codeql %} can now detect even more potential sources of untrusted user data, review the steps through which that data flows, and identify potentially dangerous sinks in which this data could end up. This results in an overall improvement of the quality of the {% data variables.product.prodname_code_scanning %} alerts. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-07-01-codeql-code-scanning-now-recognizes-more-sources-and-uses-of-untrusted-user-data/). + - | + {% data variables.product.prodname_code_scanning_capc %} now shows `security-severity` levels for CodeQL security alerts. You can configure which `security-severity` levels will cause a check failure for a pull request. The severity level of security alerts can be `critical`, `high`, `medium`, or `low`. By default, any {% data variables.product.prodname_code_scanning %} alerts with a `security-severity` of `critical` or `high` will cause a pull request check failure. + + Additionally, you can now also configure which severity levels will cause a pull request check to fail for non-security alerts. You can configure this behavior at the repository level, and define whether alerts with the severity `error`, `warning`, or `note` will cause a pull request check to fail. By default, non-security {% data variables.product.prodname_code_scanning %} alerts with a severity of `error` will cause a pull request check failure. + + For more information see "[Defining which alert severity levels cause pull request check failure](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)." + + ![List of code scanning alerts with security levels](/assets/images/enterprise/3.2/release-notes/code-scanning-alerts.png) + - | + Improvements to the branch filter for {% data variables.product.prodname_code_scanning %} alerts make it clearer which {% data variables.product.prodname_code_scanning %} alerts are being displayed on the alerts page. By default, {% data variables.product.prodname_code_scanning %} alerts are filtered to show alerts for the default branch of the repository only. You can use the branch filter to display the alerts on any of the non-default branches. Any branch filter that has been applied is shown in the search bar. + + The search syntax has also been simplified to `branch:`. This syntax can be used multiple times in the search bar to filter on multiple branches. The previous syntax, `ref:refs/heads/`, is still supported, so any saved URLs will continue to work. + - | + Free text search is now available for code scanning alerts. You can search code scanning results to quickly find specific alerts without having to know exact search terms. The search is applied across the alert's name, description, and help text. The syntax is: + + - A single word returns all matches. + - Multiple search words returns matches to either word. + - Words in double quotes returns exact matches. + - The keyword 'AND' returns matches to multiple words. + - '{% data variables.product.prodname_secret_scanning_caps %} added patterns for 23 new service providers. For the updated list of supported secrets, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning)."' + - + heading: API Changes + notes: + - 'Pagination support has been added to the Repositories REST API''s "compare two commits" endpoint, which returns a list of commits reachable from one commit or branch, but unreachable from another. The API can also now return the results for comparisons over 250 commits. For more information, see the "[Repositories](/rest/reference/repos#compare-two-commits)" REST API documentation and "[Traversing with pagination](/rest/guides/traversing-with-pagination)."' + - 'The REST API can now be used to programmatically resend or check the status of webhooks. For more information, see "[Repositories](/rest/reference/repos#webhooks)," "[Organizations](/rest/reference/orgs#webhooks)," and "[Apps](/rest/reference/apps#webhooks)" in the REST API documentation.' + - | + Improvements have been made to the code scanning and {% data variables.product.prodname_GH_advanced_security %} APIs: + + - The code scanning API now returns the CodeQL query version used for an analysis. This can be used to reproduce results or confirm that an analysis used the latest query. For more information, see "[Code scanning](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository)" in the REST API documentation. + - Admin users can now use the REST API to enable or disable {% data variables.product.prodname_GH_advanced_security %} for repositories, using the `security_and_analysis` object on `repos/{org}/{repo}`. In addition, admin users can check whether {% data variables.product.prodname_advanced_security %} is currently enabled for a repository by using a `GET /repos/{owner}/{repo}` request. These changes help you manage {% data variables.product.prodname_advanced_security %} repository access at scale. For more information, see "[Repositories](/rest/reference/repos#update-a-repository)" in the REST API documentation. + #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 %} 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. + deprecations: + - + heading: Deprecation of GitHub Enterprise Server 2.21 + notes: + - '**{% data variables.product.prodname_ghe_server %} 2.21 was discontinued on June 6, 2021**. That 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.2/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' + - + heading: Deprecation of GitHub Enterprise Server 2.22 + notes: + - '**{% data variables.product.prodname_ghe_server %} 2.22 will be discontinued on September 23, 2021**. That 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.2/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' + - + heading: Deprecation of XenServer Hypervisor support + notes: + - Beginning in {% data variables.product.prodname_ghe_server %} 3.1, we will begin discontinuing support for Xen Hypervisor. The complete deprecation is scheduled for {% data variables.product.prodname_ghe_server %} 3.3, following the standard one year deprecation window. Please contact [GitHub Support](https://enterprise.githubsupport.com/hc/en-us/signin) with questions or concerns. + - + heading: Removal of Legacy GitHub Services + notes: + - '{% data variables.product.prodname_ghe_server %} 3.2 removes unused GitHub Service database records. More information is available in the [deprecation announcement post](https://developer.github.com/changes/2018-04-25-github-services-deprecation/).' + - + heading: Deprecation of OAuth Application API endpoints and API authentication via query parameters + notes: + - | + To prevent accidental logging or exposure of `access_tokens`, we discourage the use of OAuth Application API endpoints and the use of API auth via query params. Visit the following posts to see the proposed replacements: + + * [Replacement OAuth Application API endpoints](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#changes-to-make) + * [Replacement auth via headers instead of query param](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make) + + These endpoints and auth route are planned to be removed from {% data variables.product.prodname_ghe_server %} in {% data variables.product.prodname_ghe_server %} 3.4. + - + heading: Removal of legacy GitHub App webhook events and endpoints + notes: + - | + Two legacy GitHub Apps-related webhook events have been removed: `integration_installation` and `integration_installation_repositories`. You should instead be listening to the `installation` and `installation_repositories` events. + - | + The following REST API endpoint has been removed: `POST /installations/{installation_id}/access_tokens`. You should instead be using the namespaced equivalent `POST /app/installations/{installation_id}/access_tokens`. + backups: + - '{% data variables.product.prodname_ghe_server %} 3.2 requires at least [GitHub Enterprise Backup Utilities 3.2.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/enterprise-server@3.2/admin/configuration/configuring-backups-on-your-appliance).' diff --git a/translations/de-DE/data/reusables/actions/about-environments.md b/translations/de-DE/data/reusables/actions/about-environments.md new file mode 100644 index 0000000000..ab9cfa899f --- /dev/null +++ b/translations/de-DE/data/reusables/actions/about-environments.md @@ -0,0 +1 @@ +Environments are used to describe a general deployment target like `production`, `staging`, or `development`. When a {% data variables.product.prodname_actions %} workflow deploys to an environment, the environment is displayed on the main page of the repository. You can use environments to require approval for a job to proceed, restrict which branches can trigger a workflow, or limit access to secrets. For more information about creating environments, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." \ No newline at end of file diff --git a/translations/de-DE/data/reusables/actions/actions-group-concurrency.md b/translations/de-DE/data/reusables/actions/actions-group-concurrency.md index acd4fab5e5..85aece27b2 100644 --- a/translations/de-DE/data/reusables/actions/actions-group-concurrency.md +++ b/translations/de-DE/data/reusables/actions/actions-group-concurrency.md @@ -1,6 +1,6 @@ When a concurrent job or workflow is queued, if another job or workflow using the same concurrency group in the repository is in progress, the queued job or workflow will be `pending`. Any previously pending job or workflow in the concurrency group will be canceled. To also cancel any currently running job or workflow in the same concurrency group, specify `cancel-in-progress: true`. -### Examples: Using concurrency and the default behavior +## Examples: Using concurrency and the default behavior {% raw %} ```yaml @@ -14,7 +14,7 @@ concurrency: ci-${{ github.ref }} ``` {% endraw %} -### Example: Using concurrency to cancel any in-progress job or run +## Example: Using concurrency to cancel any in-progress job or run {% raw %} ```yaml diff --git a/translations/de-DE/data/reusables/actions/ae-hosted-runners-beta.md b/translations/de-DE/data/reusables/actions/ae-hosted-runners-beta.md new file mode 100644 index 0000000000..804f22a849 --- /dev/null +++ b/translations/de-DE/data/reusables/actions/ae-hosted-runners-beta.md @@ -0,0 +1,7 @@ +{% ifversion ghae %} +{% note %} + +**Note:** {% data variables.actions.hosted_runner %}s are currently in beta and subject to change. + +{% endnote %} +{% endif %} diff --git a/translations/de-DE/data/reusables/actions/ae-self-hosted-runners-notice.md b/translations/de-DE/data/reusables/actions/ae-self-hosted-runners-notice.md index cceda715dd..0dec49e4f5 100644 --- a/translations/de-DE/data/reusables/actions/ae-self-hosted-runners-notice.md +++ b/translations/de-DE/data/reusables/actions/ae-self-hosted-runners-notice.md @@ -1,9 +1,19 @@ {% ifversion ghae %} + {% warning %} -** Warning:** Self-hosted runners are currently disabled for {% data variables.product.prodname_ghe_managed %}. This is because {% data variables.product.prodname_ghe_managed %} offers guarantees for security boundaries which are incompatible with how self-hosted runners work. However, if you do need to use self-hosted runners with {% data variables.product.prodname_ghe_managed %} and understand the security implications, you can contact {% data variables.product.prodname_dotcom %} support for a security exception that will enable self-hosted runners. +{% ifversion ghae-next %} + +**Warning:** Self-hosted runners are enabled by default for {% data variables.product.prodname_ghe_managed %}. Self-hosted runners are long-lived, and any compromise to the host machine could leak secrets or credentials or enable other attacks. If you'd like to disable self-hosted runners for your enterprise, you can contact {% data variables.product.prodname_dotcom %} support. For more information about the risks of using self-hosted runners, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/security-hardening-for-github-actions#potential-impact-of-a-compromised-runner)." + +{% elsif ghae %} + +**Warning:** Self-hosted runners are currently disabled for {% data variables.product.prodname_ghe_managed %}. This is because {% data variables.product.prodname_ghe_managed %} offers guarantees for security boundaries which are incompatible with how self-hosted runners work. However, if you do need to use self-hosted runners with {% data variables.product.prodname_ghe_managed %} and understand the security implications, you can contact {% data variables.product.prodname_dotcom %} support for a security exception that will enable self-hosted runners. If you don't need self-hosted runners, then you can use {% data variables.actions.hosted_runner %}s to run your workflows. For more information, see "[About {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/about-ae-hosted-runners)." -{% endwarning %} +{% endif %} + +{% endwarning %} + {% endif %} diff --git a/translations/de-DE/data/reusables/actions/allow-specific-actions-intro.md b/translations/de-DE/data/reusables/actions/allow-specific-actions-intro.md index ea63a6c71c..1d10b77986 100644 --- a/translations/de-DE/data/reusables/actions/allow-specific-actions-intro.md +++ b/translations/de-DE/data/reusables/actions/allow-specific-actions-intro.md @@ -1,7 +1,7 @@ When you choose **Allow select actions**, local actions are allowed, and there are additional options for allowing other specific actions: -- **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` organization. For more information, see the [`actions`](https://github.com/actions) and [`github`](https://github.com/github) organizations.{% ifversion fpt or ghes > 3.0 %} -- **Allow Marketplace actions by verified creators:** {% ifversion ghes > 3.0 %}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 > 3.0 or ghae-issue-5094 %} +- **Allow Marketplace actions by verified creators:** {% ifversion ghes > 3.0 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 specified actions:** You can restrict workflows to use actions in specific organizations and repositories. To restrict access to specific tags or commit SHAs of an action, use the same `/@` syntax used in the workflow to select the action. For example, `actions/javascript-action@v1.0.1` to select a tag or `actions/javascript-action@172239021f7ba04fe7327647b213799853a9eb89` to select a SHA. For more information, see "[Finding and customizing actions](/actions/learn-github-actions/finding-and-customizing-actions#using-release-management-for-your-custom-actions)." diff --git a/translations/de-DE/data/reusables/actions/autoscaling-parameters.md b/translations/de-DE/data/reusables/actions/autoscaling-parameters.md new file mode 100644 index 0000000000..d9c4342b29 --- /dev/null +++ b/translations/de-DE/data/reusables/actions/autoscaling-parameters.md @@ -0,0 +1,3 @@ +- Optionally, autoscaling parameters for each pool. + - Minimum number of idle runners for the pool + - Active timeout: The number of minutes that a runner should remain active in the pool before the pool is reduced to the idle count diff --git a/translations/de-DE/data/reusables/actions/cd-templates-actions.md b/translations/de-DE/data/reusables/actions/cd-templates-actions.md new file mode 100644 index 0000000000..c6eeec90db --- /dev/null +++ b/translations/de-DE/data/reusables/actions/cd-templates-actions.md @@ -0,0 +1,3 @@ +{% data variables.product.product_name %} offers CD workflow templates for several popular services, such as Azure Web App. To learn how to get started using a workflow template, see "[Using workflow templates](/actions/learn-github-actions/using-workflow-templates)" or [browse the full list of deployment workflow templates](https://github.com/actions/starter-workflows/tree/main/deployments). You can also check out our more detailed guides for specific deployment workflows, such as "[Deploying to Azure App Service](/actions/deployment/deploying-to-azure-app-service)." + +Many service providers also offer actions on {% data variables.product.prodname_marketplace %} for deploying to their service. For the full list, see [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?category=deployment&type=actions). \ No newline at end of file diff --git a/translations/de-DE/data/reusables/actions/delete-env-key.md b/translations/de-DE/data/reusables/actions/delete-env-key.md new file mode 100644 index 0000000000..380ebe5653 --- /dev/null +++ b/translations/de-DE/data/reusables/actions/delete-env-key.md @@ -0,0 +1 @@ +If you configured a deployment environment, change the value of `environment` to be the name of your environment. If you did not configure an environment{% ifversion fpt %} or if your workflow is in a private repository and you do not use {% data variables.product.prodname_ghe_cloud %}{% endif %}, delete the `environment` key. \ No newline at end of file diff --git a/translations/de-DE/data/reusables/actions/environment-deployment-event.md b/translations/de-DE/data/reusables/actions/environment-deployment-event.md new file mode 100644 index 0000000000..1a014fbfc6 --- /dev/null +++ b/translations/de-DE/data/reusables/actions/environment-deployment-event.md @@ -0,0 +1 @@ +When a workflow job that references an environment runs, it creates a deployment object with the `environment` property set to the name of your environment. As the workflow progresses, it also creates deployment status objects with the `environment` property set to the name of your environment, the `environment_url` property set to the URL for environment (if specified in the workflow), and the `state` property set to the status of the job. \ No newline at end of file diff --git a/translations/de-DE/data/reusables/actions/environment-example.md b/translations/de-DE/data/reusables/actions/environment-example.md new file mode 100644 index 0000000000..95ed6bc816 --- /dev/null +++ b/translations/de-DE/data/reusables/actions/environment-example.md @@ -0,0 +1,45 @@ +You can specify an environment for each job in your workflow. To do so, add a `jobs..environment` key followed by the name of the environment. + +For example, this workflow will use an environment called `production`. + +```yaml +name: Deployment + +on: + push: + branches: + - main + +jobs: + deployment: + runs-on: ubuntu-latest + environment: production + steps: + - name: deploy + # ...deployment-specific steps +``` + +When the above workflow runs, the `deployment` job will be subject to any rules configured for the `production` environment. For example, if the environment requires reviewers, the job will pause until one of the reviewers approves the job. + +You can also specify a URL for the environment. The specified URL will appear on the deployments page for the repository (accessed by clicking **Environments** on the home page of your repository) and in the visualization graph for the workflow run. If a pull request triggered the workflow, the URL is also displayed as a **View deployment** button in the pull request timeline. + +```yaml +name: Deployment + +on: + push: + branches: + - main + +jobs: + deployment: + runs-on: ubuntu-latest + environment: + name: production + url: https://github.com + steps: + - name: deploy + # ...deployment-specific steps +``` + +![Workflow graph with URL](/assets/images/help/images/deploy-graph.png) \ No newline at end of file diff --git a/translations/de-DE/data/reusables/actions/reusable-workflow-artifacts.md b/translations/de-DE/data/reusables/actions/reusable-workflow-artifacts.md new file mode 100644 index 0000000000..4f5210333f --- /dev/null +++ b/translations/de-DE/data/reusables/actions/reusable-workflow-artifacts.md @@ -0,0 +1,3 @@ +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +All actions and workflows called within a run have write access to that run's artifacts. +{% endif %} \ No newline at end of file diff --git a/translations/de-DE/data/reusables/actions/reusable-workflows.md b/translations/de-DE/data/reusables/actions/reusable-workflows.md new file mode 100644 index 0000000000..377f69ce32 --- /dev/null +++ b/translations/de-DE/data/reusables/actions/reusable-workflows.md @@ -0,0 +1,5 @@ +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## Reusing workflows + +You can call one workflow from within another workflow. This allows you to reuse workflows, avoiding duplication and making your workflows easier to maintain. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." +{% endif %} \ No newline at end of file diff --git a/translations/de-DE/data/reusables/actions/runner-name-description.md b/translations/de-DE/data/reusables/actions/runner-name-description.md new file mode 100644 index 0000000000..c3955e46ec --- /dev/null +++ b/translations/de-DE/data/reusables/actions/runner-name-description.md @@ -0,0 +1 @@ +The name of the runner executing the job. diff --git a/translations/de-DE/data/reusables/actions/uses-keyword-example.md b/translations/de-DE/data/reusables/actions/uses-keyword-example.md new file mode 100644 index 0000000000..fac21c8a9f --- /dev/null +++ b/translations/de-DE/data/reusables/actions/uses-keyword-example.md @@ -0,0 +1,7 @@ +```yaml +jobs: + call-workflow-1: + uses: octo-org/this-repo/.github/workflows/workflow-1.yml@172239021f7ba04fe7327647b213799853a9eb89 + call-workflow-2: + uses: octo-org/another-repo/.github/workflows/workflow-2.yml@v1 +``` \ No newline at end of file diff --git a/translations/de-DE/data/reusables/actions/workflow-organization-templates.md b/translations/de-DE/data/reusables/actions/workflow-organization-templates.md new file mode 100644 index 0000000000..a64c94d584 --- /dev/null +++ b/translations/de-DE/data/reusables/actions/workflow-organization-templates.md @@ -0,0 +1 @@ +Workflow templates allow everyone in your organization who has permission to create workflows to do so more quickly and easily. When you create a new workflow, you can choose a template and some or all of the work of writing the workflow will be done for you. Du kannst Workflow-Vorlagen als Ausgangspunkt verwenden, um Deinen benutzerdefinierten Workflow zu erstellen, oder Du kannst sie unverändert zu verwenden. This not only saves time, it promotes consistency and best practice across your organization. \ No newline at end of file diff --git a/translations/de-DE/data/reusables/actions/workflow-run-approve-public-fork.md b/translations/de-DE/data/reusables/actions/workflow-run-approve-public-fork.md index 1eeb41311a..1873b96f85 100644 --- a/translations/de-DE/data/reusables/actions/workflow-run-approve-public-fork.md +++ b/translations/de-DE/data/reusables/actions/workflow-run-approve-public-fork.md @@ -1,3 +1,9 @@ Anyone can fork a public repository, and then submit a pull request that proposes changes to the repository's {% data variables.product.prodname_actions %} workflows. Although workflows from forks do not have access to sensitive data such as secrets, they can be an annoyance for maintainers if they are modified for abusive purposes. To help prevent this, workflows on pull requests to public repositories from some outside contributors will not run automatically, and might need to be approved first. By default, all first-time contributors require approval to run workflows. + +{% note %} + +**Note:** Workflows triggered by `pull_request_target` events are run in the context of the base branch. Since the base branch is considered trusted, workflows triggered by these events will always run, regardless of approval settings. + +{% endnote %} \ No newline at end of file diff --git a/translations/de-DE/data/reusables/apps/oauth-auth-vary-response.md b/translations/de-DE/data/reusables/apps/oauth-auth-vary-response.md new file mode 100644 index 0000000000..b76fef614b --- /dev/null +++ b/translations/de-DE/data/reusables/apps/oauth-auth-vary-response.md @@ -0,0 +1 @@ +You can also receive the response in different formats if you provide the format in the `Accept` header. For example, `Accept: application/json` or `Accept: application/xml`: diff --git a/translations/de-DE/data/reusables/code-scanning/upload-sarif-alert-limit.md b/translations/de-DE/data/reusables/code-scanning/upload-sarif-alert-limit.md index 23aafdc414..23b5c1d24f 100644 --- a/translations/de-DE/data/reusables/code-scanning/upload-sarif-alert-limit.md +++ b/translations/de-DE/data/reusables/code-scanning/upload-sarif-alert-limit.md @@ -1,5 +1,8 @@ {% note %} -**Note:** SARIF upload supports a maximum of {% ifversion ghae-next or fpt or ghes > 3.0 %}5000{% else %}1000{% endif %} results per upload. Any results over this limit are ignored. If a tool generates too many results, you should update the configuration to focus on results for the most important rules or queries. +**Hinweise:** +- SARIF upload supports a maximum of {% ifversion ghae-next or fpt or ghes > 3.0 %}5000{% else %}1000{% endif %} results per upload. Any results over this limit are ignored. If a tool generates too many results, you should update the configuration to focus on results for the most important rules or queries. + + - For each upload, SARIF upload supports a maximum size of 10 MB for the `gzip`-compressed SARIF file. Any uploads over this limit will be rejected. If your SARIF file is too large because it contains too many results, you should update the configuration to focus on results for the most important rules or queries. {% endnote %} diff --git a/translations/de-DE/data/reusables/codespaces/create-or-switch-branch.md b/translations/de-DE/data/reusables/codespaces/create-or-switch-branch.md new file mode 100644 index 0000000000..caaf86c2d7 --- /dev/null +++ b/translations/de-DE/data/reusables/codespaces/create-or-switch-branch.md @@ -0,0 +1,3 @@ +1. If the current branch is not shown in the status bar, at the bottom of your codespace, right-click the status bar and select **Source control**. +1. Click the branch name in the status bar. ![The branch in the status bar](/assets/images/help/codespaces/branch-in-status-bar.png) +1. In the drop-down, either click the branch you want to switch to, or enter the name for a new branch and click **Create new branch**. ![Choose from the branch menu](/assets/images/help/codespaces/create-new-branch.png) \ No newline at end of file diff --git a/translations/de-DE/data/reusables/codespaces/source-control-commit-changes.md b/translations/de-DE/data/reusables/codespaces/source-control-commit-changes.md new file mode 100644 index 0000000000..19f38cca4a --- /dev/null +++ b/translations/de-DE/data/reusables/codespaces/source-control-commit-changes.md @@ -0,0 +1,4 @@ +{% data reusables.codespaces.source-control-display-dark %} +1. To stage your changes, click **+** next to the file you've changed, or next to **Changes** if you've changed multiple files and you want to stage them all. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-stage.png) +1. Type a commit message describing the change you've made. ![Source control side bar with a commit message](/assets/images/help/codespaces/codespaces-commit-commit-message.png) +1. To commit your staged changes, click the check mark at the top the source control side bar. ![Click the check mark icon](/assets/images/help/codespaces/codespaces-commit-checkmark-icon.png) \ No newline at end of file diff --git a/translations/de-DE/data/reusables/codespaces/source-control-pull-request.md b/translations/de-DE/data/reusables/codespaces/source-control-pull-request.md new file mode 100644 index 0000000000..de2a1d913f --- /dev/null +++ b/translations/de-DE/data/reusables/codespaces/source-control-pull-request.md @@ -0,0 +1,3 @@ +1. After you've committed changes to your local copy of the repository, click the **Create Pull Request** icon. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-pr-button.png) +1. Check that the local branch and repository you're merging from, and the remote branch and repository you're merging into, are correct. Then give the pull request a title and a description. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-pr.png) +1. Klicke auf **Create** (Erstellen). \ No newline at end of file diff --git a/translations/de-DE/data/reusables/dependabot/supported-package-managers.md b/translations/de-DE/data/reusables/dependabot/supported-package-managers.md index 3bf37c4bd7..ab29adaab0 100644 --- a/translations/de-DE/data/reusables/dependabot/supported-package-managers.md +++ b/translations/de-DE/data/reusables/dependabot/supported-package-managers.md @@ -26,7 +26,7 @@ The following table shows, for each package manager: | Terraform | `terraform` | >= 0.13, <= 1.0 | **✓** | **✓** | | | yarn | `npm` | v1 | **✓** | **✓** | | -[1] {% data variables.product.prodname_dependabot %} doesn't run Gradle but supports updates to the following files: `build.gradle` and `build.gradle.kts` (for Kotlin projects). +[1] {% data variables.product.prodname_dependabot %} doesn't run Gradle but supports updates to the following files: `build.gradle`, `build.gradle.kts` (for Kotlin projects), and files included via the `apply` declaration that have `dependencies` in the filename. Note that `apply` does not support `apply to`, recursion, or advanced syntaxes (for example, Kotlin's `apply` with `mapOf`, filenames defined by property). [2] {% data variables.product.prodname_dependabot %} doesn't run Maven but supports updates to `pom.xml` files. diff --git a/translations/de-DE/data/reusables/dependency-review/beta.md b/translations/de-DE/data/reusables/dependency-review/beta.md index d8f7089def..3ca1720c35 100644 --- a/translations/de-DE/data/reusables/dependency-review/beta.md +++ b/translations/de-DE/data/reusables/dependency-review/beta.md @@ -1,7 +1,8 @@ -{% ifversion fpt or ghes > 3.1 %} +{% ifversion ghes > 3.1 %} {% note %} **Note:** Dependency review is currently in beta and subject to change. {% endnote %} + {% endif %} \ No newline at end of file diff --git a/translations/de-DE/data/reusables/developer-site/pull_request_forked_repos_link.md b/translations/de-DE/data/reusables/developer-site/pull_request_forked_repos_link.md index e2e36cddb3..fb1cf54f2f 100644 --- a/translations/de-DE/data/reusables/developer-site/pull_request_forked_repos_link.md +++ b/translations/de-DE/data/reusables/developer-site/pull_request_forked_repos_link.md @@ -1,4 +1,4 @@ -#### Pull-Request-Ereignisse für geforkte Repositorys +### Pull-Request-Ereignisse für geforkte Repositorys {% note %} diff --git a/translations/de-DE/data/reusables/dotcom_billing/pricing_cal.md b/translations/de-DE/data/reusables/dotcom_billing/pricing_cal.md new file mode 100644 index 0000000000..6509379b28 --- /dev/null +++ b/translations/de-DE/data/reusables/dotcom_billing/pricing_cal.md @@ -0,0 +1 @@ +To estimate the costs for consumptive services, you can use the {% data variables.product.prodname_dotcom %} pricing calculator. For more information, go to https://github.com/pricing/calculator. diff --git a/translations/de-DE/data/reusables/enterprise-accounts/about-enterprise-accounts.md b/translations/de-DE/data/reusables/enterprise-accounts/about-enterprise-accounts.md index 6a9443a3bd..dd1d471ad6 100644 --- a/translations/de-DE/data/reusables/enterprise-accounts/about-enterprise-accounts.md +++ b/translations/de-DE/data/reusables/enterprise-accounts/about-enterprise-accounts.md @@ -14,7 +14,7 @@ Organizations are shared accounts where enterprise members can collaborate acros {% ifversion fpt %} -Enterprise owners can create organizations and link the organizations to the enterprise. After you add organizations to your enterprise account, you can manage and enforce policies for the organizations. Die spezifischen Optionen für das Erzwingen variieren je nach Einstellung. Im Allgemeinen können Sie wählen, ob Sie eine einzige Richtlinie für alle Organisationen in Ihrem Enterprise-Konto erzwingen oder es den Inhabern ermöglichen möchten, Richtlinien auf Organisationsebene festzulegen. For more information, see "[Setting policies for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account)." +Enterprise owners can create organizations and link the organizations to the enterprise. Alternatively, you can invite an existing organization to join your enterprise. After you add organizations to your enterprise account, you can manage and enforce policies for the organizations. Die spezifischen Optionen für das Erzwingen variieren je nach Einstellung. Im Allgemeinen können Sie wählen, ob Sie eine einzige Richtlinie für alle Organisationen in Ihrem Enterprise-Konto erzwingen oder es den Inhabern ermöglichen möchten, Richtlinien auf Organisationsebene festzulegen. For more information, see "[Setting policies for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account)." {% elsif ghes or ghae %} @@ -58,6 +58,14 @@ Weitere Informationen über die Unterschiede zwischen {% data variables.product. {% endif %} +{% ifversion fpt %} + +## Informationen zu {% data variables.product.prodname_emus %} + +{% data reusables.enterprise-accounts.emu-short-summary %} + +{% endif %} + ## About billing for your enterprise account The bill for your enterprise account includes the monthly cost for each member of your enterprise. The bill includes {% ifversion fpt %}any paid licenses in organizations outside of your enterprise account, subscriptions to apps in {% data variables.product.prodname_marketplace %}, {% endif %}{% ifversion fpt or ghae %}additional paid services for your enterprise{% ifversion fpt %} like data packs for {% data variables.large_files.product_name_long %},{% endif %} and{% endif %} usage for {% data variables.product.prodname_GH_advanced_security %}. diff --git a/translations/de-DE/data/reusables/enterprise-accounts/access-enterprise.md b/translations/de-DE/data/reusables/enterprise-accounts/access-enterprise.md index a47a055301..19b6004028 100644 --- a/translations/de-DE/data/reusables/enterprise-accounts/access-enterprise.md +++ b/translations/de-DE/data/reusables/enterprise-accounts/access-enterprise.md @@ -5,5 +5,4 @@ {% elsif ghes or ghae %}1. In the top-right corner of {% data variables.product.product_name %}, click your profile photo, then click **Enterprise settings**. !["Enterprise settings" in drop-down menu for profile photo on {% data variables.product.product_name %}](/assets/images/enterprise/settings/enterprise-settings.png) - {% endif %} diff --git a/translations/de-DE/data/reusables/enterprise-accounts/actions-runners-tab.md b/translations/de-DE/data/reusables/enterprise-accounts/actions-runners-tab.md index 19b2de94c1..b6dc023362 100644 --- a/translations/de-DE/data/reusables/enterprise-accounts/actions-runners-tab.md +++ b/translations/de-DE/data/reusables/enterprise-accounts/actions-runners-tab.md @@ -1 +1 @@ -1. Click the {% ifversion fpt %}**Runners**{% else %}**Self-hosted runners**{% endif %} tab. +1. Click the {% ifversion fpt or ghes > 3.1 or ghae-next %}**Runners**{% else %}**Self-hosted runners**{% endif %} tab. diff --git a/translations/de-DE/data/reusables/enterprise-accounts/emu-forks.md b/translations/de-DE/data/reusables/enterprise-accounts/emu-forks.md new file mode 100644 index 0000000000..315ee2736f --- /dev/null +++ b/translations/de-DE/data/reusables/enterprise-accounts/emu-forks.md @@ -0,0 +1 @@ +{% data variables.product.prodname_managed_users_caps %} cannot fork repositories from outside of the enterprise or fork internal repositories. {% data variables.product.prodname_managed_users_caps %} can fork private repositories owned by organizations in the enterprise into other organizations owned by the enterprise, or as a fork owned by the {% data variables.product.prodname_managed_user %}. \ No newline at end of file diff --git a/translations/de-DE/data/reusables/enterprise-accounts/emu-more-info-account.md b/translations/de-DE/data/reusables/enterprise-accounts/emu-more-info-account.md new file mode 100644 index 0000000000..21302799fb --- /dev/null +++ b/translations/de-DE/data/reusables/enterprise-accounts/emu-more-info-account.md @@ -0,0 +1 @@ +For more information, see "[Types of GitHub accounts](/get-started/learning-about-github/types-of-github-accounts#enterprise-managed-users)." \ No newline at end of file diff --git a/translations/de-DE/data/reusables/enterprise-accounts/emu-password-reset-session.md b/translations/de-DE/data/reusables/enterprise-accounts/emu-password-reset-session.md new file mode 100644 index 0000000000..65ed74cc65 --- /dev/null +++ b/translations/de-DE/data/reusables/enterprise-accounts/emu-password-reset-session.md @@ -0,0 +1 @@ +If you need to reset the password for your setup user, use an incognito or private browsing window to request a new password. When the email arrives with the link to reset your password, copy the link into your browser. For more information on resetting your password, see "[Requesting a new password ](/github/authenticating-to-github/keeping-your-account-and-data-secure/updating-your-github-access-credentials#requesting-a-new-password)." \ No newline at end of file diff --git a/translations/de-DE/data/reusables/enterprise-accounts/emu-permission-follow.md b/translations/de-DE/data/reusables/enterprise-accounts/emu-permission-follow.md new file mode 100644 index 0000000000..f166721634 --- /dev/null +++ b/translations/de-DE/data/reusables/enterprise-accounts/emu-permission-follow.md @@ -0,0 +1 @@ +{% ifversion fpt %} Members of an {% data variables.product.prodname_emu_enterprise %} can only follow other members of their enterprise. {% endif %} \ No newline at end of file diff --git a/translations/de-DE/data/reusables/enterprise-accounts/emu-permission-fork.md b/translations/de-DE/data/reusables/enterprise-accounts/emu-permission-fork.md new file mode 100644 index 0000000000..411dfeed7b --- /dev/null +++ b/translations/de-DE/data/reusables/enterprise-accounts/emu-permission-fork.md @@ -0,0 +1 @@ +{% ifversion fpt %}Members of an {% data variables.product.prodname_emu_enterprise %} cannot fork repositories from outside of the enterprise or fork internal repositories.{% endif %} \ No newline at end of file diff --git a/translations/de-DE/data/reusables/enterprise-accounts/emu-permission-gist.md b/translations/de-DE/data/reusables/enterprise-accounts/emu-permission-gist.md new file mode 100644 index 0000000000..3164ea3434 --- /dev/null +++ b/translations/de-DE/data/reusables/enterprise-accounts/emu-permission-gist.md @@ -0,0 +1 @@ +{% ifversion fpt %}Members of an {% data variables.product.prodname_emu_enterprise %} cannot create gists and have read-only access to gists.{% endif %} \ No newline at end of file diff --git a/translations/de-DE/data/reusables/enterprise-accounts/emu-permission-interact.md b/translations/de-DE/data/reusables/enterprise-accounts/emu-permission-interact.md new file mode 100644 index 0000000000..9bdeac19e8 --- /dev/null +++ b/translations/de-DE/data/reusables/enterprise-accounts/emu-permission-interact.md @@ -0,0 +1 @@ +{% ifversion fpt %} Members of an {% data variables.product.prodname_emu_enterprise %} can only interact with repositories within their enterprise. {% endif %} \ No newline at end of file diff --git a/translations/de-DE/data/reusables/enterprise-accounts/emu-permission-propose.md b/translations/de-DE/data/reusables/enterprise-accounts/emu-permission-propose.md new file mode 100644 index 0000000000..85fd4f66e3 --- /dev/null +++ b/translations/de-DE/data/reusables/enterprise-accounts/emu-permission-propose.md @@ -0,0 +1 @@ +{% ifversion fpt %} Members of an {% data variables.product.prodname_emu_enterprise %} can only propose changes in repositories that are part of their enterprise. {% endif %} diff --git a/translations/de-DE/data/reusables/enterprise-accounts/emu-permission-repo.md b/translations/de-DE/data/reusables/enterprise-accounts/emu-permission-repo.md new file mode 100644 index 0000000000..b4278362a5 --- /dev/null +++ b/translations/de-DE/data/reusables/enterprise-accounts/emu-permission-repo.md @@ -0,0 +1 @@ +{% ifversion fpt %} Members of an {% data variables.product.prodname_emu_enterprise %} can only make changes in repositories that are part of their enterprise. {% endif %} diff --git a/translations/de-DE/data/reusables/enterprise-accounts/emu-saml-note.md b/translations/de-DE/data/reusables/enterprise-accounts/emu-saml-note.md new file mode 100644 index 0000000000..2a5bdae038 --- /dev/null +++ b/translations/de-DE/data/reusables/enterprise-accounts/emu-saml-note.md @@ -0,0 +1,7 @@ +{% ifversion fpt%} +{% note %} + +**Note**: If your enterprise uses {% data variables.product.prodname_emus %}, you must follow a different process to configure SAML single sign-on. For more information, see "[Configuring SAML single sign-on for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." + +{% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/de-DE/data/reusables/enterprise-accounts/emu-scim-note.md b/translations/de-DE/data/reusables/enterprise-accounts/emu-scim-note.md new file mode 100644 index 0000000000..309ec9adfb --- /dev/null +++ b/translations/de-DE/data/reusables/enterprise-accounts/emu-scim-note.md @@ -0,0 +1,7 @@ +{% ifversion fpt%} +{% note %} + +**Note**: If your enterprise uses {% data variables.product.prodname_emus %}, you cannot use team synchronization and must instead configure SCIM to manage membership with your identity provider. For more information, see "[Configuring SCIM provisioning for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users)." + +{% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/de-DE/data/reusables/enterprise-accounts/emu-short-summary.md b/translations/de-DE/data/reusables/enterprise-accounts/emu-short-summary.md new file mode 100644 index 0000000000..7e4f69fff9 --- /dev/null +++ b/translations/de-DE/data/reusables/enterprise-accounts/emu-short-summary.md @@ -0,0 +1 @@ +{% data variables.product.prodname_emus %} is a feature of {% data variables.product.prodname_ghe_cloud %} that provides even greater control over enterprise members and resources. With {% data variables.product.prodname_emus %}, all members are provisioned and managed through your identity provider (IdP) instead of users creating their own accounts on {% data variables.product.product_name %}. Team membership can be managed using groups on your IdP. {% data variables.product.prodname_managed_users_caps %} are restricted to their enterprise and are unable to push code, collaborate, or interact with users, repositories, and organizations outside of their enterprise. For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." \ No newline at end of file diff --git a/translations/de-DE/data/reusables/enterprise-accounts/emu-shortcode.md b/translations/de-DE/data/reusables/enterprise-accounts/emu-shortcode.md new file mode 100644 index 0000000000..ec695c807d --- /dev/null +++ b/translations/de-DE/data/reusables/enterprise-accounts/emu-shortcode.md @@ -0,0 +1 @@ +The short code must be unique to your enterprise, a three-to-eight character alphanumeric string, and contain no special characters. \ No newline at end of file diff --git a/translations/de-DE/data/reusables/enterprise-accounts/emu-supported-idps.md b/translations/de-DE/data/reusables/enterprise-accounts/emu-supported-idps.md new file mode 100644 index 0000000000..375040efa3 --- /dev/null +++ b/translations/de-DE/data/reusables/enterprise-accounts/emu-supported-idps.md @@ -0,0 +1,2 @@ +* Azure Active Directory (Azure AD) +* Okta \ No newline at end of file diff --git a/translations/de-DE/data/reusables/enterprise-accounts/github-connect-tab.md b/translations/de-DE/data/reusables/enterprise-accounts/github-connect-tab.md index 043dfba71a..194448cf5a 100644 --- a/translations/de-DE/data/reusables/enterprise-accounts/github-connect-tab.md +++ b/translations/de-DE/data/reusables/enterprise-accounts/github-connect-tab.md @@ -1,3 +1,3 @@ {% ifversion ghes < 3.1 %} 1. Klicken Sie auf der linken Seitenleiste auf **{% data variables.product.prodname_github_connect %}**. ![GitHub Connect tab in the business account settings sidebar](/assets/images/enterprise/business-accounts/settings-github-connect-tab.png){% else %} -1. In the enterprise account sidebar, click {% octicon "plug" aria-label="The GitHub Connect gear" %} **{% data variables.product.prodname_github_connect %}**. ![GitHub Connect tab in the enterprise account sidebar](/assets/images/help//business-accounts/enterprise-account-github-connect-tab.png){% endif %} \ No newline at end of file +1. In the enterprise account sidebar, click {% octicon "plug" aria-label="The GitHub Connect gear" %} **{% data variables.product.prodname_github_connect %}**. ![GitHub Connect tab in the enterprise account sidebar](/assets/images/help//business-accounts/enterprise-account-github-connect-tab.png){% endif %} diff --git a/translations/de-DE/data/reusables/enterprise-accounts/identity-provider-tab.md b/translations/de-DE/data/reusables/enterprise-accounts/identity-provider-tab.md new file mode 100644 index 0000000000..9e94eecb59 --- /dev/null +++ b/translations/de-DE/data/reusables/enterprise-accounts/identity-provider-tab.md @@ -0,0 +1 @@ +1. Under your business account's name, click {% octicon "key" aria-label="The key icon" %} **Identity provider**. !["Identity provider" tab in enterprise sidebar](/assets/images/help/enterprises/enterprise-account-identity-provider-tab.png) \ No newline at end of file diff --git a/translations/de-DE/data/reusables/enterprise-accounts/invite-organization.md b/translations/de-DE/data/reusables/enterprise-accounts/invite-organization.md new file mode 100644 index 0000000000..1d5c99c11e --- /dev/null +++ b/translations/de-DE/data/reusables/enterprise-accounts/invite-organization.md @@ -0,0 +1 @@ +Enterprise account owners and administrators can invite existing organization accounts to join their enterprise. For more information, see "[Inviting an organization to join your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account#inviting-an-organization-to-join-your-enterprise-account)" diff --git a/translations/de-DE/data/reusables/enterprise-accounts/team-sync-override.md b/translations/de-DE/data/reusables/enterprise-accounts/team-sync-override.md new file mode 100644 index 0000000000..a39283eed0 --- /dev/null +++ b/translations/de-DE/data/reusables/enterprise-accounts/team-sync-override.md @@ -0,0 +1 @@ +If your organization is owned by an enterprise account, enabling team synchronization or SCIM provisioning for the enterprise account will override your organization-level team synchronization settings. For more information, see "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)" and "[Configuring SCIM provisioning for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users)." \ No newline at end of file diff --git a/translations/de-DE/data/reusables/enterprise_clustering/proxy_protocol_ports.md b/translations/de-DE/data/reusables/enterprise_clustering/proxy_protocol_ports.md index 2cb45c2066..266fb8664a 100644 --- a/translations/de-DE/data/reusables/enterprise_clustering/proxy_protocol_ports.md +++ b/translations/de-DE/data/reusables/enterprise_clustering/proxy_protocol_ports.md @@ -1,4 +1,4 @@ -#### PROXY-Protokoll – TCP-Portzuordnungen +### PROXY-Protokoll – TCP-Portzuordnungen | Quellport | Zielport | Dienstbeschreibung | |:---------:|:--------:|:---------------------------:| diff --git a/translations/de-DE/data/reusables/enterprise_clustering/without_proxy_protocol_ports.md b/translations/de-DE/data/reusables/enterprise_clustering/without_proxy_protocol_ports.md index 0691d0e25a..1a3ee5b8e1 100644 --- a/translations/de-DE/data/reusables/enterprise_clustering/without_proxy_protocol_ports.md +++ b/translations/de-DE/data/reusables/enterprise_clustering/without_proxy_protocol_ports.md @@ -1,4 +1,4 @@ -#### Protokoll – TCP-Portzuordnungen für die Verwendung ohne PROXY-Unterstützung +### Protokoll – TCP-Portzuordnungen für die Verwendung ohne PROXY-Unterstützung | Quellport | Zielport | Dienstbeschreibung | |:---------:|:--------:|:---------------------------:| diff --git a/translations/de-DE/data/reusables/gated-features/emus.md b/translations/de-DE/data/reusables/gated-features/emus.md new file mode 100644 index 0000000000..f9f25095ea --- /dev/null +++ b/translations/de-DE/data/reusables/gated-features/emus.md @@ -0,0 +1 @@ +To manage users in your enterprise with your identity provider, your enterprise must be enabled for {% data variables.product.prodname_emus %}, which are available with {% data variables.product.prodname_ghe_cloud %}. For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." \ No newline at end of file diff --git a/translations/de-DE/data/reusables/getting-started/enterprise-advanced-security.md b/translations/de-DE/data/reusables/getting-started/enterprise-advanced-security.md new file mode 100644 index 0000000000..faffbe7d63 --- /dev/null +++ b/translations/de-DE/data/reusables/getting-started/enterprise-advanced-security.md @@ -0,0 +1 @@ +If you have a GitHub Advanced Security license for your enterprise account, you can enforce policies to manage {% data variables.product.prodname_dotcom %} Advanced Security features for organizations owned by an enterprise account. For more information, see "[Enforcing policies for Advanced Security in your enterprise account](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-policies-for-advanced-security-in-your-enterprise-account)." \ No newline at end of file diff --git a/translations/de-DE/data/reusables/github-actions/actions-on-examples.md b/translations/de-DE/data/reusables/github-actions/actions-on-examples.md index 42dda5f10d..1b64a1a7f7 100644 --- a/translations/de-DE/data/reusables/github-actions/actions-on-examples.md +++ b/translations/de-DE/data/reusables/github-actions/actions-on-examples.md @@ -1,18 +1,18 @@ -### Example: Using a single event +## Example: Using a single event ```yaml # Triggered when code is pushed to any branch in a repository on: push ``` -### Example: Using a list of events +## Example: Using a list of events ```yaml # Triggers the workflow on push or pull request events on: [push, pull_request] ``` -### Example: Using multiple events with activity types or configuration +## Example: Using multiple events with activity types or configuration Wenn Du Aktivitätstypen oder Konfigurationen für ein Ereignis angeben musst, musst Du jedes Ereignis separat konfigurieren. Du musst einen Doppelpunkt (`:`) an alle Ereignisse anhängen, einschließlich Ereignisse ohne Konfiguration. diff --git a/translations/de-DE/data/reusables/github-actions/disabling-github-actions.md b/translations/de-DE/data/reusables/github-actions/disabling-github-actions.md index ae73419a8d..afe8ee7f1f 100644 --- a/translations/de-DE/data/reusables/github-actions/disabling-github-actions.md +++ b/translations/de-DE/data/reusables/github-actions/disabling-github-actions.md @@ -1 +1 @@ -By default, {% ifversion ghes or ghae %}after {% data variables.product.prodname_actions %} is enabled on {% data variables.product.product_location %}, it{% elsif fpt %}{% data variables.product.prodname_actions %}{% endif %} is enabled on all repositories and organizations. You can choose to disable {% data variables.product.prodname_actions %} or limit them to private actions only, which means that people can only use actions that exist in your repository. +By default, {% ifversion ghes or ghae %}after {% data variables.product.prodname_actions %} is enabled on {% data variables.product.product_location %}, it{% elsif fpt %}{% data variables.product.prodname_actions %}{% endif %} is enabled on all repositories and organizations. You can choose to disable {% data variables.product.prodname_actions %} or limit them to local actions only, which means that people can only use actions that exist in your repository. diff --git a/translations/de-DE/data/reusables/github-actions/name-environment.md b/translations/de-DE/data/reusables/github-actions/name-environment.md new file mode 100644 index 0000000000..f6fd5c69d4 --- /dev/null +++ b/translations/de-DE/data/reusables/github-actions/name-environment.md @@ -0,0 +1 @@ +1. Enter a name for the environment, then click **Configure environment**. Environment names are not case sensitive. An environment name may not exceed 255 characters and must be unique within the repository. diff --git a/translations/de-DE/data/reusables/github-actions/new-environment.md b/translations/de-DE/data/reusables/github-actions/new-environment.md new file mode 100644 index 0000000000..879f2bf20a --- /dev/null +++ b/translations/de-DE/data/reusables/github-actions/new-environment.md @@ -0,0 +1 @@ +1. Click **New environment**. diff --git a/translations/de-DE/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md b/translations/de-DE/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md index c7c2e176b9..db79cb3f59 100644 --- a/translations/de-DE/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md +++ b/translations/de-DE/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md @@ -1,6 +1,7 @@ -1. In the {% ifversion fpt %}"Runners"{% else %}"Self-hosted runners"{% endif %} section of the settings page, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} next to the runner group you'd like to configure, then click **Edit name and [organization|repository] access**. ![Repository-Berechtigungen verwalten](/assets/images/help/settings/actions-runner-manage-permissions.png) +1. In the {% ifversion fpt or ghes > 3.1 or ghae-next %}"Runners"{% else %}"Self-hosted runners"{% endif %} section of the settings page, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} next to the runner group you'd like to configure, then click **Edit name and [organization|repository] access**. ![Repository-Berechtigungen verwalten](/assets/images/help/settings/actions-runner-manage-permissions.png) 1. Modify your policy options, or change the runner group name. + {% ifversion not ghae %} {% warning %} **Warnung** @@ -10,3 +11,4 @@ Weitere Informationen findest Du unter „[Informationen zu selbst-gehosteten Runnern](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)“. {% endwarning %} + {% endif %} diff --git a/translations/de-DE/data/reusables/github-actions/self-hosted-runner-list.md b/translations/de-DE/data/reusables/github-actions/self-hosted-runner-list.md index 6edf2cb3f9..f6cb3732b1 100644 --- a/translations/de-DE/data/reusables/github-actions/self-hosted-runner-list.md +++ b/translations/de-DE/data/reusables/github-actions/self-hosted-runner-list.md @@ -1 +1 @@ - 1. Locate the list of runners under {% ifversion fpt %}"Runners"{% else %}"Self-hosted runners"{% endif %}. + 1. Locate the list of runners under {% ifversion fpt or ghes > 3.1 or ghae-next %}"Runners"{% else %}"Self-hosted runners"{% endif %}. diff --git a/translations/de-DE/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md b/translations/de-DE/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md index 5d5101b06e..7e5e0e142f 100644 --- a/translations/de-DE/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md +++ b/translations/de-DE/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md @@ -6,5 +6,5 @@ 1. In the left sidebar, click **Enterprise overview**. 1. {% endif %} In the enterprise sidebar, {% octicon "law" aria-label="The law icon" %} **Policies**. 1. Navigate to the {% data variables.product.prodname_actions %} settings: - * **In an organization or repository**: Click **Actions** in the left sidebar{% ifversion fpt %}, then click **Runners**{% endif %}. - * {% ifversion fpt %}**If using an enterprise account**:{% elsif ghes or ghae %}**If using an enterprise-level runner**:{% endif %} Click **Actions** under "{% octicon "law" aria-label="The law icon" %} Policies"{% ifversion fpt %}, then click the **Runners** tab{% endif %}. + * **In an organization or repository**: Click **Actions** in the left sidebar{% ifversion fpt or ghes > 3.1 or ghae-next %}, then click **Runners**{% endif %}. + * {% ifversion fpt %}**If using an enterprise account**:{% elsif ghes or ghae %}**If using an enterprise-level runner**:{% endif %} Click **Actions** under "{% octicon "law" aria-label="The law icon" %} Policies"{% ifversion fpt or ghes > 3.1 or ghae-next %}, then click the **Runners** tab{% endif %}. diff --git a/translations/de-DE/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md b/translations/de-DE/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md index ddb2e40a9f..a68071e779 100644 --- a/translations/de-DE/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md +++ b/translations/de-DE/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md @@ -1,4 +1,4 @@ -1. Under {% ifversion fpt %}"Runners"{% else %}"Self-hosted runners"{% endif %}, locate the runner in the list. If your runner is in a group, click {% octicon "chevron-down" aria-label="The downwards chevron" %} to expand the list. +1. Under {% ifversion fpt or ghes > 3.1 or ghae-next %}"Runners"{% else %}"Self-hosted runners"{% endif %}, locate the runner in the list. If your runner is in a group, click {% octicon "chevron-down" aria-label="The downwards chevron" %} to expand the list. 1. Click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} next to the runner you want to remove, then click **Remove**. ![Entfernen einer selbst-gehosteten Läufereinstellung](/assets/images/help/settings/actions-runner-remove.png) diff --git a/translations/de-DE/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md b/translations/de-DE/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md index 39f7f4ff6c..d51fdc01ef 100644 --- a/translations/de-DE/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md +++ b/translations/de-DE/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md @@ -1,2 +1,2 @@ -1. Klicke in der linken Seitenleiste auf **Actions** (Aktionen). -1. In the left sidebar, under "Actions", click **Runner groups**. +1. In the left sidebar, click **Actions**.{% ifversion fpt or ghes > 3.1 or ghae-next %} +1. In the left sidebar, under "Actions", click **Runner groups**.{% endif %} diff --git a/translations/de-DE/data/reusables/github-actions/settings-sidebar-actions-runners.md b/translations/de-DE/data/reusables/github-actions/settings-sidebar-actions-runners.md index cf1a5ba36f..181fbef515 100644 --- a/translations/de-DE/data/reusables/github-actions/settings-sidebar-actions-runners.md +++ b/translations/de-DE/data/reusables/github-actions/settings-sidebar-actions-runners.md @@ -1 +1 @@ -1. In the left sidebar, click **Actions**{% ifversion fpt %}, then click **Runners**{% endif %}. +1. In the left sidebar, click **Actions**{% ifversion fpt or ghes > 3.1 or ghae-next %}, then click **Runners**{% endif %}. diff --git a/translations/de-DE/data/reusables/github-actions/supported-github-runners.md b/translations/de-DE/data/reusables/github-actions/supported-github-runners.md index f73baefe51..c3cd858a84 100644 --- a/translations/de-DE/data/reusables/github-actions/supported-github-runners.md +++ b/translations/de-DE/data/reusables/github-actions/supported-github-runners.md @@ -60,17 +60,6 @@ Ubuntu 18.04 - - - - - @@ -236,7 +235,7 @@ Una vez que tu job comience a ejecutarse, podrás{% ifversion fpt or ghes > 3.0 Para seguir aprendiendo sobre las {% data variables.product.prodname_actions %}, consulta la sección "[Encontrar y personalizar las acciones](/actions/learn-github-actions/finding-and-customizing-actions)". -To understand how billing works for {% data variables.product.prodname_actions %}, see "[About billing for {% data variables.product.prodname_actions %}](/actions/reference/usage-limits-billing-and-administration#about-billing-for-github-actions)". +Para entender cómo funciona la facturación de las {% data variables.product.prodname_actions %}, consulta la sección "[Acerca de la facturación para las {% data variables.product.prodname_actions %}](/actions/reference/usage-limits-billing-and-administration#about-billing-for-github-actions)". ## Contactar con soporte técnico diff --git a/translations/es-ES/content/actions/learn-github-actions/usage-limits-billing-and-administration.md b/translations/es-ES/content/actions/learn-github-actions/usage-limits-billing-and-administration.md index 66b9bd97b2..80f64c20f2 100644 --- a/translations/es-ES/content/actions/learn-github-actions/usage-limits-billing-and-administration.md +++ b/translations/es-ES/content/actions/learn-github-actions/usage-limits-billing-and-administration.md @@ -16,20 +16,19 @@ shortTitle: Límites & facturación de los flujos de trabajo {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Acerca de la facturación para {% data variables.product.prodname_actions %} {% ifversion fpt %} {% data reusables.github-actions.actions-billing %} Para obtener más información, consulta "[Acerca de la facturación de {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)". {% else %} -GitHub Actions usage is free for {% data variables.product.prodname_ghe_server %}s that use self-hosted runners. +El uso de GitHub Actions es gratuito para los {% data variables.product.prodname_ghe_server %} que utilicen ejecutores auto-hospedados. {% endif %} ## Límites de uso {% ifversion fpt %} -There are some limits on {% data variables.product.prodname_actions %} usage when using {% data variables.product.prodname_dotcom %}-hosted runners. Estos límites están sujetos a cambios. +Hay algunos límites de uso de {% data variables.product.prodname_actions %} cuando se utilizan ejecutores hospedados en {% data variables.product.prodname_dotcom %}. Estos límites están sujetos a cambios. {% note %} @@ -61,6 +60,12 @@ Los límites de uso aplican a los ejecutores auto-hospedados. Para obtener más Además de los límites de uso, debes asegurarte de usar las {% data variables.product.prodname_actions %} dentro de los [Términos de servicio de GitHub](/articles/github-terms-of-service/). Para obtener más información sobre los términos específicos de las {% data variables.product.prodname_actions %}, consulta los [Términos adicionales de producto de GitHub](/github/site-policy/github-additional-product-terms#a-actions-usage). {% endif %} +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## Facturación para los flujos de trabajo reutilizables + +Si vuelves a utilizar un flujo de trabajo la facturación siempre se asociará con aquél del que llama. Para obtener más información, consulta la sección "[Reutilizar los flujos de trabajo](/actions/learn-github-actions/reusing-workflows)". +{% endif %} + {% ifversion fpt or ghes > 2.22 or ghae %} ## Polìtica de retenciòn de artefactos y bitàcoras diff --git a/translations/es-ES/content/actions/learn-github-actions/using-workflow-templates.md b/translations/es-ES/content/actions/learn-github-actions/using-workflow-templates.md index 16682571fc..d880f4a446 100644 --- a/translations/es-ES/content/actions/learn-github-actions/using-workflow-templates.md +++ b/translations/es-ES/content/actions/learn-github-actions/using-workflow-templates.md @@ -1,7 +1,7 @@ --- -title: Using workflow templates -shortTitle: Using templates -intro: You can set up CI using a workflow template that matches the language and tooling you want to use. +title: Utilizar plantillas de flujo de trabajo +shortTitle: Utilizar plantillas +intro: '{% data variables.product.product_name %} provides workflow templates for a variety of languages and tooling.' product: '{% data reusables.gated-features.actions %}' redirect_from: - /articles/setting-up-continuous-integration-using-github-actions @@ -17,34 +17,37 @@ type: tutorial topics: - Workflows - CI + - CD --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -Cualquier persona con permiso de escritura en un repositorio puede configurar la integración continua (CI) utilizando {% data variables.product.prodname_actions %}. +## Acerca de plantillas de flujo de trabajo -Una vez que hayas configurado la IC, puedes personalizar el flujo de trabajo para satisfacer tus necesidades. +{% data variables.product.product_name %} offers workflow templates for a variety of languages and tooling. When you set up workflows in your repository, {% data variables.product.product_name %} analyzes the code in your repository and recommends workflows based on the language and framework in your repository. Por ejemplo, si utilizas [Node.js](https://nodejs.org/en/), {% data variables.product.product_name %} te sugerirá un archivo de plantilla que instala tus paquetes de Node.js y ejecuta tus pruebas. + +You can also create your own workflow templates to share with your organization. For more information, see "[Creating workflow templates](/actions/learn-github-actions/creating-workflow-templates)." + +## Utilizar plantillas de flujo de trabajo + +Anyone with write permission to a repository can set up {% data variables.product.prodname_actions %} workflows for CI/CD or other automation. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} -1. Busca la plantilla que coincida con el idioma y las herramientas que deseas utilizar; a continuación, haz clic en **Configurar este flujo de trabajo**. ![Configurar el botón de flujo de trabajo](/assets/images/help/repository/setup-workflow-button.png) -5. Haz clic en **Iniciar confirmación**. ![Botón Start commit (Iniciar confirmación)](/assets/images/help/repository/start-commit.png) -{% data reusables.files.write_commit_message %} -{% data reusables.files.choose_commit_branch %} -{% data reusables.files.propose_new_file %} - -Una vez que se hace una inserción en tu repositorio, puedes seguir el estado y los registros detallados de tu flujo de trabajo de integración continua ejecutado en {% data variables.product.prodname_dotcom %} y recibir notificaciones personalizadas. Para obtener más información, consulta la sección "[Configurar notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)" y "[Administrar una ejecución de flujo de trabajo](/articles/managing-a-workflow-run)". - -{% data reusables.repositories.actions-workflow-status-badge-intro %} - -Para obtener más información, consulta la sección "[Agregar una insignia de estado de flujo de trabajo](/actions/managing-workflow-runs/adding-a-workflow-status-badge)". +1. If you already have a workflow in your repository, click **New workflow**. +1. Find the template that you want to use, then click **Set up this workflow**. +1. If the workflow template contains comments detailing additional setup steps, follow these steps. +1. Some workflow templates use secrets. For example, {% raw %}`${{ secrets.npm_token }}`{% endraw %}. If the workflow template uses a secret, store the value described in the secret name as a secret in your repository. Para obtener más información, consulta "[Secretos cifrados](/actions/reference/encrypted-secrets)". +1. Optionally, make additional changes. For example, you might want to change the value of `on` to change when the workflow runs. +1. Haz clic en **Iniciar confirmación**. +1. Write a commit message and decide whether to commit directly to the default branch or to open a pull request. ## Leer más - "[Acerca de la integración continua](/articles/about-continuous-integration)" -- "[Administrar una ejecución de flujo de trabajo](/articles/managing-a-workflow-run)" +- "[Managing workflow runs](/actions/managing-workflow-runs)" +- "[About monitoring and troubleshooting](/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting)" - "[Aprende sobre las {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" {% ifversion fpt %} - "[Administrar la facturación de {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)" diff --git a/translations/es-ES/content/actions/learn-github-actions/workflow-commands-for-github-actions.md b/translations/es-ES/content/actions/learn-github-actions/workflow-commands-for-github-actions.md index 683270ef15..e1ee728a76 100644 --- a/translations/es-ES/content/actions/learn-github-actions/workflow-commands-for-github-actions.md +++ b/translations/es-ES/content/actions/learn-github-actions/workflow-commands-for-github-actions.md @@ -18,7 +18,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Acerca de los comandos de flujo @@ -89,7 +88,7 @@ La siguiente tabla muestra qué funciones del toolkit se encuentran disponibles | `core.setOutput` | `set-output` | | `core.setSecret` | `add-mask` | | `core.startGroup` | `grupo` | -| `core.warning` | `warning file` | +| `core.warning` | `advertencia` | {% ifversion ghes < 3.0 %} ## Configurar una variable de ambiente @@ -331,6 +330,12 @@ echo "{name}={value}" >> $GITHUB_ENV Crea o actualiza una variable de ambiente para cualquier paso que sea el siguiente en ejecutarse en un job. El paso que crea o actualiza la variable de ambiente no tiene acceso al valor nuevo, pero todos los pasos subsecuentes en un job tendrán acceso. Las variables de entorno distinguen mayúsculas de minúsculas y puedes incluir puntuación. +{% note %} + +**Nota:** Las variables de ambiente deben referenciarse explícitamente utilizando el [contexto`env`](/actions/reference/context-and-expression-syntax-for-github-actions#env-context) en la sintaxis de expresión o mediante el uso del archivo `$GITHUB_ENV` directamente; las variables de ambiente no están disponibles implícitamente en los comandos del shell. + +{% endnote %} + ### Ejemplo {% raw %} @@ -376,7 +381,7 @@ steps: echo "{path}" >> $GITHUB_PATH ``` -Antepone un directorio a la variable `PATH` del sistema y la hace disponible para todas las acciones subsecuentes en el job actual; la acción que se está ejecutando actualmente no puede acceder a la variable de ruta actualizada. Para ver las rutas definidas actualmente para tu job, puedes utilizar `echo "$PATH"` en un paso o en una acción. +Antepone un directorio a la variable de sistema `PATH` y la hace disponible automáticamente para todas las acciones subsecuentes en el job actual; la acción que se está ejecutando actualmente no puede acceder a la variable de ruta actualizada. Para ver las rutas definidas actualmente para tu job, puedes utilizar `echo "$PATH"` en un paso o en una acción. ### Ejemplo diff --git a/translations/es-ES/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md b/translations/es-ES/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md index b015a23d3e..6fed91ab09 100644 --- a/translations/es-ES/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md +++ b/translations/es-ES/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md @@ -16,7 +16,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Acerca de la sintaxis de YAML para flujos de trabajo @@ -52,7 +51,7 @@ on: Cuando uses los eventos `push` y `pull_request` debes configurar un flujo de trabajo para ejecutarlo en ramas o etiquetas específicas. Para un evento `pull_request`, solo se evalúan las ramas y las etiquetas en la base. Si defines solo `etiquetas` o solo `ramas`, el flujo de trabajo no se ejecutará para los eventos que afecten a la ref de Git indefinida. -Las palabras clave `branches`, `branches-ignore`, `tags`, y `tags-ignore` aceptan patrones globales que utilizan caracteres como `*`, `**`, `+`, `?`, `!` y otros para empatar con más de una rama o nombre de etiqueta. If a name contains any of these characters and you want a literal match, you need to *escape* each of these special characters with `\`. Para obtener más información sobre los patrones globales, consulta "[Hoja de información para filtrar patrones](#filter-pattern-cheat-sheet)". +Las palabras clave `branches`, `branches-ignore`, `tags`, y `tags-ignore` aceptan patrones globales que utilizan caracteres como `*`, `**`, `+`, `?`, `!` y otros para empatar con más de una rama o nombre de etiqueta. Si un nombre contiene cualquiera de estos caracteres y quieres tener una coincidencia literal, necesitas *escapar* cada uno de estos caracteres especiales con una `\`. Para obtener más información sobre los patrones globales, consulta "[Hoja de información para filtrar patrones](#filter-pattern-cheat-sheet)". ### Ejemplo: Incluyendo ramas y etiquetas @@ -184,6 +183,88 @@ Los diffs se limitan a 300 archivos. Si hay archivos que cambiaron y no se empat Para obtener más información, consulta "[Acerca de comparar ramas en las solicitudes de extracción](/articles/about-comparing-branches-in-pull-requests)". +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## `on.workflow_call.inputs` + +Cuando se utiliza la palabra clave `workflow_call`, puedes especificar opcionalmente entradas que se pasan al flujo de trabajo al que ese llamó desde aquél del llamante. Las entradas para los flujos de trabajo reutilizables se especifican con el mismo formato que las entradas de las acciones. Para obtener más información sobre las entradas, consulta la sección "[Sintaxis de metadatos para GitHub Actions](/actions/creating-actions/metadata-syntax-for-github-actions#inputs)". Para obtener más información sobre la palabra clave de `workflow_call`, consulta la sección "[Eventos que activan los flujos de trabajo](/actions/learn-github-actions/events-that-trigger-workflows#workflow-reuse-events)". + +Adicionalmente a los parámetros de entrada estándar que están disponibles, `on.workflow_call.inputs` requiere un parámetro de `type`. Para obtener más información, consulta [`on.workflow_call..type`](#onworkflow_callinput_idtype). + +Si un parámetro `default` no se configura, el valor predeterminado de la entrada es `false` en el caso de un booleano, `0` en el caso de un número y `""` para una llamada. + +Dentro del flujo de trabajo llamado, puedes utilizar el contexto `inputs` para referirte a una entrada. + +Si un flujo de trabajo llamante pasa una entrada que no se especifica en el flujo llamado, dará un error como resultado. + +### Ejemplo + +{% raw %} +```yaml +on: + workflow_call: + inputs: + username: + description: 'A username passed from the caller workflow' + default: 'john-doe' + required: false + type: string + +jobs: + print-username: + runs-on: ubuntu-latest + + steps: + - name: Print the input name to STDOUT + run: echo The username is ${{ inputs.username }} +``` +{% endraw %} + +Para obtener más información, consulta la sección "[Reutilizar flujos de trabajo](/actions/learn-github-actions/reusing-workflows)". + +## `on.workflow_call..type` + +Requerido si se define una entrada para la palabra clave `on.workflow_call`. El valor de este parámetro es una secuencia que especifica el tipo de datos de la entrada. Este debe ser alguno de entre: `boolean`, `number` o `string`. + +## `on.workflow_call.secrets` + +Un mapa de los secretos que puede utilizarse en el flujo de trabajo llamado. + +Dentro del flujo de trabajo llamado, puedes utilizar el contexto `secrets` para referirte a un secreto. + +Si un flujo de trabajo llamante pasa un secreto que no se especifica en el flujo de trabajo llamado, esto da un error como resultado. + +### Ejemplo + +{% raw %} +```yaml +on: + workflow_call: + secrets: + access-token: + description: 'A token passed from the caller workflow' + required: false + +jobs: + pass-secret-to-action: + runs-on: ubuntu-latest + + steps: + - name: Pass the received secret to an action + uses: ./.github/actions/my-action@v1 + with: + token: ${{ secrets.access-token }} +``` +{% endraw %} + +## `on.workflow_call.secrets.` + +Un identificador de secuencia para asociar con el secreto. + +## `on.workflow_call.secrets..required` + +Un booleano que especifica si el secreto debe suministrarse. +{% endif %} + ## `on.workflow_dispatch.inputs` Cuando se utiliza el evento `workflow_dispatch`, puedes especificar opcionalmente entradas que se pasan al flujo de trabajo. Las entradas de envío de flujo de trabajo se especifican en el mismo formato que las entradas de acción. Para obtener más información sobre el formato, consulta la sección "[Sintaxis de metadatos para las GitHub Actions](/actions/creating-actions/metadata-syntax-for-github-actions#inputs)". @@ -272,9 +353,7 @@ defaults: {% ifversion fpt or ghae-next or ghes > 3.1 %} ## `concurrency` -{% data reusables.actions.concurrency-beta %} - -La concurrencia se asegura de que solo un job o flujo de trabajo que utilice el mismo grupo de concurrencia se ejecute al mismo tiempo. Un grupo de concurrencia puede ser cualquier secuencia o expresión. The expression can only use the [`github` context](/actions/learn-github-actions/contexts#github-context). For more information about expressions, see "[Expressions](/actions/learn-github-actions/expressions)." +La concurrencia se asegura de que solo un job o flujo de trabajo que utilice el mismo grupo de concurrencia se ejecute al mismo tiempo. Un grupo de concurrencia puede ser cualquier secuencia o expresión. La expresión solo puede utilizar el [contexto`github`](/actions/learn-github-actions/contexts#github-context). Para obtener más información sobre las expresiones, consulta la sección "[Expresiones](/actions/learn-github-actions/expressions)". También puedes especificar la `concurrency` a nivel del job. Para obtener más información, consulta la [`jobsconcurrency`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idconcurrency). @@ -344,7 +423,7 @@ jobs: needs: [job1, job2] ``` -En este ejemplo, `job3` utiliza la expresión condicional `always()` para que siempre se ejecute después de que el `job1` y el `job2` se hayan completado, sin importar si tuvieron éxito o no. For more information, see "[Expressions](/actions/learn-github-actions/expressions#job-status-check-functions)." +En este ejemplo, `job3` utiliza la expresión condicional `always()` para que siempre se ejecute después de que el `job1` y el `job2` se hayan completado, sin importar si tuvieron éxito o no. Para obtener más información, consulta la sección "[Expresiones](/actions/learn-github-actions/expressions#job-status-check-functions)". ## `jobs..runs-on` @@ -428,7 +507,7 @@ jobs: {% ifversion fpt or ghes > 3.0 or ghae %} ## `jobs..environment` -El ambiente que referencia el job. Todas las reglas de protección del ambiente deben pasar antes de que un job que referencie dicho ambiente se envie a un ejecutor. Para obtener más información, consulta la sección "[Ambientes](/actions/reference/environments)". +El ambiente que referencia el job. Todas las reglas de protección del ambiente deben pasar antes de que un job que referencie dicho ambiente se envie a un ejecutor. Para obtener más información, consulta la sección "[Utilizar ambientes para despliegue](/actions/deployment/using-environments-for-deployment)". Puedes proporcionar el ambiente como solo el `name` de éste, o como un objeto de ambiente con el `name` y `url`. La URL mapea hacia `environment_url` en la API de despliegues. Para obtener más información sobre la API de despliegues, consulta la sección "[Despliegues](/rest/reference/repos#deployments)". @@ -447,7 +526,7 @@ environment: url: https://github.com ``` -The URL can be an expression and can use any context except for the [`secrets` context](/actions/learn-github-actions/contexts#contexts). For more information about expressions, see "[Expressions](/actions/learn-github-actions/expressions)." +La URL puede ser una expresión y puede utilizar cualquier contexto, excepto el de [`secrets`](/actions/learn-github-actions/contexts#contexts). Para obtener más información sobre las expresiones, consulta la sección "[Expresiones](/actions/learn-github-actions/expressions)". ### Ejemplo {% raw %} @@ -463,15 +542,13 @@ environment: {% ifversion fpt or ghae-next or ghes > 3.1 %} ## `jobs..concurrency` -{% data reusables.actions.concurrency-beta %} - {% note %} **Nota:** Cuando se especifica la concurrencia a nivel del job, no se garantiza el orden para los jobs o ejecuciones que se ponen en fila a 5 minutos uno del otro. {% endnote %} -La concurrencia se asegura de que solo un job o flujo de trabajo que utilice el mismo grupo de concurrencia se ejecute al mismo tiempo. Un grupo de concurrencia puede ser cualquier secuencia o expresión. La expresión puede utilizar cualquier contexto, con excepción del contexto `secrets`. For more information about expressions, see "[Expressions](/actions/learn-github-actions/expressions)." +La concurrencia se asegura de que solo un job o flujo de trabajo que utilice el mismo grupo de concurrencia se ejecute al mismo tiempo. Un grupo de concurrencia puede ser cualquier secuencia o expresión. La expresión puede utilizar cualquier contexto, con excepción del contexto `secrets`. Para obtener más información sobre las expresiones, consulta la sección "[Expresiones](/actions/learn-github-actions/expressions)". También puedes especificar la `concurrency` a nivel del flujo de trabajo. Para obtener más información, consulta la [`concurrency`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#concurrency). @@ -555,7 +632,7 @@ jobs: Puedes usar el condicional `if` para impedir que se ejecute una tarea si no se cumple una condición. Puedes usar cualquier contexto y expresión admitidos para crear un condicional. -{% data reusables.github-actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)." +{% data reusables.github-actions.expression-syntax-if %} Para obtener más información, consulta la sección "[Expresiones](/actions/learn-github-actions/expressions)". ## `jobs..steps` @@ -595,7 +672,7 @@ Un identificador único para el paso. Puede usar el `id` para hacer referencia a Puedes usar el condiciona `if` para impedir que se ejecute un paso si no se cumple una condición. Puedes usar cualquier contexto y expresión admitidos para crear un condicional. -{% data reusables.github-actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)." +{% data reusables.github-actions.expression-syntax-if %} Para obtener más información, consulta la sección "[Expresiones](/actions/learn-github-actions/expressions)". ### Ejemplo: Utilizando contextos @@ -610,7 +687,7 @@ steps: ### Ejemplo: Utilizando funciones de verificación de estado -El `paso mi copia de seguridad` solo se ejecuta cuando se produce un error en el paso anterior de un trabajo. For more information, see "[Expressions](/actions/learn-github-actions/expressions#job-status-check-functions)." +El `paso mi copia de seguridad` solo se ejecuta cuando se produce un error en el paso anterior de un trabajo. Para obtener más información, consulta la sección "[Expresiones](/actions/learn-github-actions/expressions#job-status-check-functions)". ```yaml steps: @@ -964,7 +1041,7 @@ Establece variables de entorno para los pasos a utilizar en el entorno del ejecu {% data reusables.repositories.actions-env-var-note %} -Es posible que las acciones públicas especifiquen las variables de entorno esperadas en el archivo README. Si estás estableciendo un secreto en una variable de entorno, debes establecer secretos usando el contexto `secretos`. For more information, see "[Using environment variables](/actions/automating-your-workflow-with-github-actions/using-environment-variables)" and "[Contexts](/actions/learn-github-actions/contexts)." +Es posible que las acciones públicas especifiquen las variables de entorno esperadas en el archivo README. Si estás estableciendo un secreto en una variable de entorno, debes establecer secretos usando el contexto `secretos`. Para obtener más información, consulta las secciones "[Utilizar variables de ambiente](/actions/automating-your-workflow-with-github-actions/using-environment-variables)" y "[Contextos](/actions/learn-github-actions/contexts)". ### Ejemplo @@ -1348,6 +1425,70 @@ Opciones adicionales de recursos del contenedor Docker. Para obtener una lista d {% endwarning %} +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## `jobs..uses` + +La ubicación y versión de un archivo de flujo de trabajo reutilizable a ejecutar como un job. + +`{owner}/{repo}/{path}/{filename}@{ref}` + +`{ref}` puede ser un SHA, una etiqueta de lanzamiento o un nombre de rama. Utilizar el SHA de la confirmación es lo más seguro para la estabilidad y seguridad. Para obtener más información, consulta la sección "[Fortalecimiento de la seguridad para las GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#reusing-third-party-workflows)". + +### Ejemplo + +{% data reusables.actions.uses-keyword-example %} + +Para obtener más información, consulta la sección "[Reutilizar flujos de trabajo](/actions/learn-github-actions/reusing-workflows)". + +## `jobs..with` + +Cuando se utiliza un job para llamar a un flujo de trabajo reutilizable, puedes usar `with` para proporcionar un mapa de entradas que se pasen al flujo de trabajo llamado. + +Cualquier entrada que pases debe coincidir con las especificaciones de la entrada que se define en el flujo de trabajo llamado. + +A diferencia de [`jobs..steps[*].with`](#jobsjob_idstepswith), las entradas que pases con `jobs..with` no están disponibles como variables de ambiente en el flujo de trabajo llamado. En vez de esto, puedes referenciar las entradas utilizando el contexto `inputs`. + +### Ejemplo + +```yaml +jobs: + call-workflow: + uses: octo-org/example-repo/.github/workflows/called-workflow.yml@main + with: + username: mona +``` + +## `jobs..with.` + +Un par que consiste de un identificador de secuencias para la entrada y del valor de entrada. El identificador debe coincidir con el nombre de una entrada que defina [`on.workflow_call.inputs.`](/actions/creating-actions/metadata-syntax-for-github-actions#inputsinput_id) en el flujo de trabajo llamado. El tipo de datos del valor debe coincidir con el tipo que definió [`on.workflow_call..type`](#onworkflow_callinput_idtype) en el flujo de trabajo llamado. + +Contextos de expresión permitidos: `github`, y `needs`. + +## `jobs..secrets` + +Cuando se utiliza un job para llamar a un flujo de trabajo reutilizable, puedes utilizar `secrets` para proporcionar un mapa de secretos que se pasa al flujo de trabajo llamado. + +Cualquier secreto que pases debe coincidir con los nombres que se definen en el flujo de trabajo llamado. + +### Ejemplo + +{% raw %} +```yaml +jobs: + call-workflow: + uses: octo-org/example-repo/.github/workflows/called-workflow.yml@main + secrets: + access-token: ${{ secrets.PERSONAL_ACCESS_TOKEN }} +``` +{% endraw %} + +## `jobs..secrets.` + +Un par que consiste de un identificador de secuencias para el secreto y el valor de dicho secreto. El identificador debe coincidir con el nombre de una entrada que defina [`on.workflow_call.secrets.`](#onworkflow_callsecretssecret_id) en el flujo de trabajo llamado. + +Contextos de expresión permitidos: `github`, `needs` y `secrets`. +{% endif %} + ## Hoja de referencia de patrones de filtro Puedes usar caracteres especiales en los filtros de ruta, de rama y de etiqueta. diff --git a/translations/es-ES/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md b/translations/es-ES/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md index f26b40651c..5613254222 100644 --- a/translations/es-ES/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md +++ b/translations/es-ES/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md @@ -16,8 +16,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## Introducción diff --git a/translations/es-ES/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md b/translations/es-ES/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md index c9e6328ef4..9a30060dd0 100644 --- a/translations/es-ES/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md +++ b/translations/es-ES/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md @@ -16,8 +16,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## Introducción @@ -73,7 +71,7 @@ Con base en el parámetro `schedule` (por ejemplo, todos los días a la 1:39 UTC Puedes ver el historial de tus ejecuciones de flujo de trabajo para ver que este flujo de trabajo se ejecute regularmente. Para obtener más información, consulta la sección "[Visualizar el historial de ejecuciones de un flujo de trabajo](/actions/managing-workflow-runs/viewing-workflow-run-history)". -This workflow will only label and/or close 30 issues at a time in order to avoid exceeding a rate limit. Puedes configurar esto con el ajuste de `operations-per-run`. Para obtener más información, consulta la [documentación de la acción `actions/stale`](https://github.com/marketplace/actions/close-stale-issues). +Este flujo de trabajo solo etiquetará o cerrará 30 propuestas a la vez para evitar exceder el límite de tasa. Puedes configurar esto con el ajuste de `operations-per-run`. Para obtener más información, consulta la [documentación de la acción `actions/stale`](https://github.com/marketplace/actions/close-stale-issues). ## Pasos siguientes diff --git a/translations/es-ES/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md b/translations/es-ES/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md index cbfd5c70c9..d5ba962fb6 100644 --- a/translations/es-ES/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md +++ b/translations/es-ES/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md @@ -17,8 +17,6 @@ shortTitle: Agregar una etiqueta para comentar en la propuesta {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## Introducción diff --git a/translations/es-ES/content/actions/managing-issues-and-pull-requests/index.md b/translations/es-ES/content/actions/managing-issues-and-pull-requests/index.md index c8998c1500..c4375b430e 100644 --- a/translations/es-ES/content/actions/managing-issues-and-pull-requests/index.md +++ b/translations/es-ES/content/actions/managing-issues-and-pull-requests/index.md @@ -1,7 +1,7 @@ --- -title: Managing issues and pull requests -shortTitle: Managing issues and pull requests -intro: 'You can automatically manage your issues and pull requests using {% data variables.product.prodname_actions %} workflows.' +title: Administrar propuestas y solicitudes de cambios +shortTitle: Administrar propuestas y solicitudes de cambios +intro: 'Puedes fusionar tus propuestas y solicitudes de cambios automáticamente utilizando los flujos de trabajo de {% data variables.product.prodname_actions %}.' versions: fpt: '*' ghes: '*' diff --git a/translations/es-ES/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md b/translations/es-ES/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md index 7fc1dcaadb..dee10d2c6d 100644 --- a/translations/es-ES/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md +++ b/translations/es-ES/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md @@ -17,8 +17,6 @@ shortTitle: Mover las propuestas asignadas {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## Introducción diff --git a/translations/es-ES/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md b/translations/es-ES/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md index a234ca1e37..fdedfc5904 100644 --- a/translations/es-ES/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md +++ b/translations/es-ES/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md @@ -17,8 +17,6 @@ shortTitle: Elimina la etiqueta al agregar la tarjeta {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## Introducción diff --git a/translations/es-ES/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md b/translations/es-ES/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md index 83335f721a..0bbbd659a2 100644 --- a/translations/es-ES/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md +++ b/translations/es-ES/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md @@ -16,8 +16,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## Introducción diff --git a/translations/es-ES/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md b/translations/es-ES/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md index b2d6751494..ac88c7d6ee 100644 --- a/translations/es-ES/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md +++ b/translations/es-ES/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md @@ -9,7 +9,9 @@ shortTitle: Aprobar las ejecuciones de una bifurcación pública ## Acerca de las ejecuciones de flujo de trabajo de las bifurcaciones públicas -{% data reusables.actions.workflow-run-approve-public-fork %} Sin embargo, puedes configurar este comportamiento para un [repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks), [organización](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#configuring-required-approval-for-workflows-from-public-forks), o [empresa](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account#configuring-required-approval-for-workflows-from-public-forks). +{% data reusables.actions.workflow-run-approve-public-fork %} + +You can configure workflow approval requirements for a [repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks), [organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#configuring-required-approval-for-workflows-from-public-forks), or [enterprise](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account#configuring-required-approval-for-workflows-from-public-forks). Las ejecuciones de flujos de trabajo que hayan estado esperando una aprobación por más de 30 días se borrarán automáticamente. diff --git a/translations/es-ES/content/actions/managing-workflow-runs/canceling-a-workflow.md b/translations/es-ES/content/actions/managing-workflow-runs/canceling-a-workflow.md index e0d4965a8e..867b7aa3e6 100644 --- a/translations/es-ES/content/actions/managing-workflow-runs/canceling-a-workflow.md +++ b/translations/es-ES/content/actions/managing-workflow-runs/canceling-a-workflow.md @@ -10,7 +10,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.repositories.permissions-statement-write %} diff --git a/translations/es-ES/content/actions/managing-workflow-runs/deleting-a-workflow-run.md b/translations/es-ES/content/actions/managing-workflow-runs/deleting-a-workflow-run.md index 7b876017a4..197546d1c3 100644 --- a/translations/es-ES/content/actions/managing-workflow-runs/deleting-a-workflow-run.md +++ b/translations/es-ES/content/actions/managing-workflow-runs/deleting-a-workflow-run.md @@ -10,7 +10,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.repositories.permissions-statement-write %} diff --git a/translations/es-ES/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md b/translations/es-ES/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md index 2839f12ef6..c983ea25c2 100644 --- a/translations/es-ES/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md +++ b/translations/es-ES/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md @@ -11,7 +11,6 @@ shortTitle: Inhabilitar & habilitar un flujo de trabajo {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} Inhabilitar un flujo de trabajo te permite impedir que se active sin tener que borrar el archivo del repositorio. Puedes habilitar el flujo de trabajo de nuevo fácilmente en {% data variables.product.prodname_dotcom %}. diff --git a/translations/es-ES/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md b/translations/es-ES/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md index 1a2dfa84d9..ac42b43f0e 100644 --- a/translations/es-ES/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md +++ b/translations/es-ES/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md @@ -11,9 +11,8 @@ shortTitle: Descargar artefactos de flujo de trabajo {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% ifversion fpt or ghes > 2.22 or ghae %} Predeterminadamente, {% data variables.product.product_name %} almacena las bitácoras de compilación y los artefactos por 90 días, y puedes personalizar este periodo de retención dependiendo del tipo de repositorio. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)."{% endif %} +{% ifversion fpt or ghes > 2.22 or ghae %} Predeterminadamente, {% data variables.product.product_name %} almacena las bitácoras de compilación y los artefactos por 90 días, y puedes personalizar este periodo de retención dependiendo del tipo de repositorio. Para obtener más información, consulta la sección "[Administrar los ajustes de las {% data variables.product.prodname_actions %} en un repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)".{% endif %} {% ifversion ghes = 2.22 %} Las {% data variables.product.product_name %} almacenan las bitácoras y los artefactos por 90 días.{% endif %} {% data reusables.repositories.permissions-statement-read %} diff --git a/translations/es-ES/content/actions/managing-workflow-runs/index.md b/translations/es-ES/content/actions/managing-workflow-runs/index.md index 8ce134e7e8..e526aea6a0 100644 --- a/translations/es-ES/content/actions/managing-workflow-runs/index.md +++ b/translations/es-ES/content/actions/managing-workflow-runs/index.md @@ -1,7 +1,7 @@ --- title: Administrar ejecuciones de flujo de trabajo shortTitle: Administrar ejecuciones de flujo de trabajo -intro: 'You can re-run or cancel a workflow, {% ifversion fpt or ghes > 3.0 or ghae %}review deployments, {% endif %}view billable job execution minutes, and download artifacts.' +intro: 'Puedes volver a ejecutar o cancelar un flujo de trabajo, {% ifversion fpt or ghes > 3.0 or ghae %}revisar despliegues, {% endif %}ver los minutos facturables de ejecución de jobs y descargar artefactos.' redirect_from: - /actions/configuring-and-managing-workflows/managing-a-workflow-run - /articles/managing-a-workflow-run @@ -19,6 +19,7 @@ children: - /approving-workflow-runs-from-public-forks - /reviewing-deployments - /disabling-and-enabling-a-workflow + - /skipping-workflow-runs - /deleting-a-workflow-run - /downloading-workflow-artifacts - /removing-workflow-artifacts @@ -26,5 +27,3 @@ children: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% ifversion fpt or ghes > 3.0 or ghae %}{% endif %} diff --git a/translations/es-ES/content/actions/managing-workflow-runs/manually-running-a-workflow.md b/translations/es-ES/content/actions/managing-workflow-runs/manually-running-a-workflow.md index 07cf681aea..02db400a40 100644 --- a/translations/es-ES/content/actions/managing-workflow-runs/manually-running-a-workflow.md +++ b/translations/es-ES/content/actions/managing-workflow-runs/manually-running-a-workflow.md @@ -6,31 +6,35 @@ versions: fpt: '*' ghes: '*' ghae: '*' +shortTitle: Ejecutar un flujo de trabajo manualmente --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -### Configurar un flujo de trabajo para que se ejecute manualmente +## Configurar un flujo de trabajo para que se ejecute manualmente -Para ejecutar un flujo de trabajo manualmente, éste debe estar configurado para ejecutarse en el evento `workflow_dispatch`. Para obtener más información sobre cómo configurar el evento `workflow_dispatch`, consulta la sección "[Eventos que activan flujos de trabajo](/actions/reference/events-that-trigger-workflows#workflow_dispatch)". - -### Ejecutar un flujo de trabajo en {% data variables.product.prodname_dotcom %} - -Para activar el evento `workflow_dispatch` en {% data variables.product.prodname_dotcom %}, tu flujo de trabajo deberá estar en la rama predeterminada. Sigue estos pasos para activar una ejecución de flujo de trabajo manualmente. +Para ejecutar un flujo de trabajo manualmente, éste debe estar configurado para ejecutarse en el evento `workflow_dispatch`. Para activar el evento `workflow_dispatch`, tu flujo de trabajo debe estar en la rama predeterminada. Para obtener más información sobre cómo configurar el evento `workflow_dispatch`, consulta la sección "[Eventos que activan flujos de trabajo](/actions/reference/events-that-trigger-workflows#workflow_dispatch)". {% data reusables.repositories.permissions-statement-write %} +## Ejecutar un flujo de trabajo + +{% include tool-switcher %} + +{% webui %} + {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} 1. En la barra lateral izquierda, da clic ene l flujo de trabajo que quieras ejecutar. ![flujo de trabajo de la selección en las acciones](/assets/images/actions-select-workflow.png) 1. Sobre la lista de ejecuciones de flujo de trabajo, selecciona **Ejecutar flujo de trabajo**. ![envío del flujo de trabajo de las acciónes](/assets/images/actions-workflow-dispatch.png) -1. Selecciona la rama en donde el flujo de trabajo se ejecutará y teclea los parámetros de entrada que éste utiliza. Da clic en **Ejecutar flujo de trabajo**. ![flujo de trabajo de la ejecución manual de las acciones](/assets/images/actions-manually-run-workflow.png) +1. Utiliza el menú desplegable de **Rama** para seleccionar la rama del flujo de trabajo y para teclear los parámetros de entrada. Da clic en **Ejecutar flujo de trabajo**. ![flujo de trabajo de la ejecución manual de las acciones](/assets/images/actions-manually-run-workflow.png) -### Ejecutar un flujo de trabajo utilizando {% data variables.product.prodname_cli %} +{% endwebui %} -{% data reusables.actions.actions-cli %} +{% cli %} + +{% data reusables.cli.cli-learn-more %} Para ejecutar un flujo de trabajo, utiliza el subcomando `workflow run`. Reemplaza el parámetro `workflow` ya sea con el nombre, ID, o nombre de archivo del flujo de trabajo que quieres ejecutar. Por ejemplo `"Link Checker"`, `1234567`, o `"link-check-test.yml"`. Si no especificas un flujo de trabajo, {% data variables.product.prodname_cli %} devolverá un menú interactivo para que elijas un flujo de trabajo. @@ -62,7 +66,9 @@ Para ver el progreso de la ejecución del flujo de trabajo, utiliza el subcomand gh run watch ``` -### Ejecutar un flujo de trabajo utilizando la API de REST +{% endcli %} + +## Ejecutar un flujo de trabajo utilizando la API de REST Para obtener más información acerca de cómo utilizar la API de REST, consulta la sección [Crear un evento de envío de flujo de trabajo](/rest/reference/actions/#create-a-workflow-dispatch-event)". Si omites las entradas, se utilizarán los valores predeterminados que se hayan definido en el flujo de trabajo. diff --git a/translations/es-ES/content/actions/managing-workflow-runs/re-running-a-workflow.md b/translations/es-ES/content/actions/managing-workflow-runs/re-running-a-workflow.md index 1bd26baaa9..ab974bab19 100644 --- a/translations/es-ES/content/actions/managing-workflow-runs/re-running-a-workflow.md +++ b/translations/es-ES/content/actions/managing-workflow-runs/re-running-a-workflow.md @@ -1,6 +1,6 @@ --- title: Volver a ejecutar un flujo de trabajo -intro: You can re-run an instance of a workflow up to 30 days after the initial run. +intro: Puedes volver a ejecutar una instancia de un flujo de trabajo hasta 30 días después de la ejecución inicial. product: '{% data reusables.gated-features.actions %}' permissions: People with write permissions to a repository can re-run workflows in the repository. versions: @@ -11,9 +11,8 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -Re-running a workflow uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (Git ref) of the original event that triggered the workflow run. You can re-run a workflow up to 30 days after the initial run. +El volver a ejecutar un flujo de trabajo utiliza el mismo `GITHUB_SHA` (SHA de confirmación) y `GITHUB_REF` (ref de Git) del evento original que activó la ejecución de flujo de trabajo. Puedes volver a ejecutar un flujo de trabajo hasta 30 días después de la ejecución inicial. {% include tool-switcher %} diff --git a/translations/es-ES/content/actions/managing-workflow-runs/removing-workflow-artifacts.md b/translations/es-ES/content/actions/managing-workflow-runs/removing-workflow-artifacts.md index 51575c1e56..1e5ea6736e 100644 --- a/translations/es-ES/content/actions/managing-workflow-runs/removing-workflow-artifacts.md +++ b/translations/es-ES/content/actions/managing-workflow-runs/removing-workflow-artifacts.md @@ -11,7 +11,6 @@ shortTitle: Eliminar los artefactos de un flujo de trabajo {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Borrar un artefacto diff --git a/translations/es-ES/content/actions/managing-workflow-runs/reviewing-deployments.md b/translations/es-ES/content/actions/managing-workflow-runs/reviewing-deployments.md index f0f2988537..7731a8ca3c 100644 --- a/translations/es-ES/content/actions/managing-workflow-runs/reviewing-deployments.md +++ b/translations/es-ES/content/actions/managing-workflow-runs/reviewing-deployments.md @@ -8,13 +8,12 @@ versions: ghae: '*' --- -{% data reusables.actions.ae-beta %} ## Acerca de las revisiones requeridas en los flujos de trabajo Los jobs que referencian un ambiente configurado con revisores requeridos esperarán por una aprobación antes de comenzar. Mientras que un job espera su revisión, tendrá un estado de "Waiting". Si un job no se aprueba dentro de 30 días, la ejecución del flujo de trabajo se cancelará automáticamente. -Para obtener más información acerca de los ambientes y las aprobaciones requeridas, consulta la sección "[Ambientes](/actions/reference/environments)".{% ifversion fpt or ghae-next or ghes > 3.1 %} Para obtener información sobre cómo revisar los despliegues con la API de REST, consulta la sección "[Ejecuciones de flujo de trabajo](/rest/reference/actions#workflow-runs)".{% endif %} +Para obtener más información sobre los ambientes y aprobaciones requeridos, consulta la sección"[Utilizar ambientes para despliegue](/actions/deployment/using-environments-for-deployment)".{% ifversion fpt or ghae-next or ghes > 3.1 %} Para obtener información sobre cómo revisar los despliegues con la API de REST, consulta la sección "[Ejecuciones de flujo de trabajo](/rest/reference/actions#workflow-runs)".{% endif %} ## Aprobar o rechazar un job diff --git a/translations/es-ES/content/actions/managing-workflow-runs/skipping-workflow-runs.md b/translations/es-ES/content/actions/managing-workflow-runs/skipping-workflow-runs.md new file mode 100644 index 0000000000..b4c549d69c --- /dev/null +++ b/translations/es-ES/content/actions/managing-workflow-runs/skipping-workflow-runs.md @@ -0,0 +1,33 @@ +--- +title: Saltarse las ejecuciones de código +intro: You can skip workflow runs triggered by the `push` and `pull_request` events by including a command in your commit message. +product: '{% data reusables.gated-features.actions %}' +versions: + fpt: '*' + ghes: '>=3.0' + ghae: ghae-next +shortTitle: Skip workflow runs +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +Workflows that would otherwise be triggered using `on: push` or `on: pull_request` won't be triggered if you add any of the following strings to the commit message in a push, or the HEAD commit of a pull request: + +* `[skip ci]` +* `[ci skip]` +* `[no ci]` +* `[skip actions]` +* `[actions skip]` + +Como alternativa, puedes finalizar el mensaje de confirmación con dos líneas vacías seguidas de ya sea `skip-checks: true` o `skip-checks:true`. + +No podrás fusionar la solicitud de cambios si tu repositorio se cofiguró para requerir que las verificaciones específicas pasen primero. Para permitir que la solicitud de cambios se fusione, puedes subir una confirmación nueva a la solicitud de cambios sin la instrucción de salto en el mensaje de confirmación. + +{% note %} + +**Nota:** Las instrucciones de salto solo aplican para los eventos de `push` y `pull_request`. Por ejemplo, el agregar `[skip ci]` a un mensaje de confirmación no impedirá que se ejecute un flujo de trabajo que se activa con `on: pull_request_target`. + +{% endnote %} + +Skip instructions only apply to the workflow run(s) that would be triggered by the commit that contains the skip instructions. You can also disable a workflow from running. Para obtener más información, consulta la sección "[Inhabilitar y habilitar un flujo de trabajo](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)". diff --git a/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md b/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md index 10ef8a163a..4ae817f8c0 100644 --- a/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md +++ b/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md @@ -19,7 +19,6 @@ shortTitle: Migrarse desde Azure Pipelines {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introducción @@ -204,7 +203,7 @@ jobs:
- Specify the name of the ref you checked out and analyzed so that the results can be matched to the correct code. For a branch use: refs/heads/BRANCH-NAME, for the head commit of a pull request use refs/pulls/NUMBER/head, or for the {% data variables.product.product_name %}-generated merge commit of a pull request use refs/pulls/NUMBER/merge. + Specify the name of the ref you checked out and analyzed so that the results can be matched to the correct code. For a branch use: refs/heads/BRANCH-NAME, for the head commit of a pull request use refs/pulls/NUMBER/head, or for the {% data variables.product.prodname_dotcom %}-generated merge commit of a pull request use refs/pulls/NUMBER/merge.
- Specify the SARIF file to load.{% ifversion ghes > 3.0 or ghae-next %} + Specify the SARIF file to load.{% ifversion ghes > 3.0 or ghae %}
-Ubuntu 16.04[deprecated] - -ubuntu-16.04 - -Deprecated and limited to existing customers only. Migrate to Ubuntu 20.04. For more information, see the blog post. -
macOS Big Sur 11 diff --git a/translations/de-DE/data/reusables/github-connect/access-dotcom-and-enterprise.md b/translations/de-DE/data/reusables/github-connect/access-dotcom-and-enterprise.md index 2d9a75adb7..2f22dbfd74 100644 --- a/translations/de-DE/data/reusables/github-connect/access-dotcom-and-enterprise.md +++ b/translations/de-DE/data/reusables/github-connect/access-dotcom-and-enterprise.md @@ -1 +1 @@ -1. Melden Dich bei {% data variables.product.product_location_enterprise %} und {% data variables.product.prodname_dotcom_the_website %} an. +1. Sign in to {% ifversion ghes %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_ghe_managed %}{% endif %} and {% data variables.product.prodname_dotcom_the_website %}. diff --git a/translations/de-DE/data/reusables/github-connect/access-profile-settings.md b/translations/de-DE/data/reusables/github-connect/access-profile-settings.md index 816b550702..4a4f72c9e2 100644 --- a/translations/de-DE/data/reusables/github-connect/access-profile-settings.md +++ b/translations/de-DE/data/reusables/github-connect/access-profile-settings.md @@ -1 +1 @@ -1. Klicke in {% data variables.product.product_location_enterprise %} in der oberen rechten Ecke einer beliebigen Seite auf Dein Profilfoto und anschließend auf **Settings** (Einstellungen). ![Symbol „Settings" (Einstellungen) auf der Benutzerleiste](/assets/images/help/settings/userbar-account-settings.png) +1. On {% ifversion ghes %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_ghe_managed %}{% endif %}, in the upper-right corner of any page, click your profile photo, then click **Settings**. ![Symbol „Settings" (Einstellungen) auf der Benutzerleiste](/assets/images/help/settings/userbar-account-settings.png) diff --git a/translations/de-DE/data/reusables/github-connect/authorize-connection.md b/translations/de-DE/data/reusables/github-connect/authorize-connection.md index 6316507e96..80546e2c2d 100644 --- a/translations/de-DE/data/reusables/github-connect/authorize-connection.md +++ b/translations/de-DE/data/reusables/github-connect/authorize-connection.md @@ -1 +1,7 @@ -1. Überprüfe die Ressourcen, auf welche {% data variables.product.prodname_ghe_server %} von Deinem {% data variables.product.prodname_dotcom_the_website %}-Konto zugreifen wird, dann klicke **Authorize** (Autorisieren). ![Autorisiere die Verbindung zwischen dem GitHub Enterprise Server und GitHub.com](/assets/images/help/settings/authorize-ghe-to-connect-to-dotcom.png) +1. Review the resources that +{% data variables.product.product_name %} will access from your {% data variables.product.prodname_dotcom_the_website %} account, then click **Authorize**. +{% ifversion ghes %} + ![Verbindung zwischen {% data variables.product.prodname_ghe_server %} und {% data variables.product.prodname_dotcom_the_website %} autorisieren](/assets/images/help/settings/authorize-ghe-to-connect-to-dotcom.png) +{% elsif ghae %} + ![Verbindung zwischen {% data variables.product.prodname_ghe_managed %} und {% data variables.product.prodname_dotcom_the_website %} autorisieren](/assets/images/enterprise/github-ae/settings/authorize-ghae-to-connect-to-dotcom.png) +{% endif %} diff --git a/translations/de-DE/data/reusables/github-connect/beta.md b/translations/de-DE/data/reusables/github-connect/beta.md new file mode 100644 index 0000000000..991a98d3d6 --- /dev/null +++ b/translations/de-DE/data/reusables/github-connect/beta.md @@ -0,0 +1,7 @@ +{% ifversion ghae-next %} +{% note %} + +**Note:** {% data variables.product.prodname_github_connect %} for {% data variables.product.product_name %} is currently in beta and subject to change. + +{% endnote %} +{% endif %} diff --git a/translations/de-DE/data/reusables/github-connect/connect-dotcom-and-enterprise.md b/translations/de-DE/data/reusables/github-connect/connect-dotcom-and-enterprise.md index 4e8eeaf41a..a23a155deb 100644 --- a/translations/de-DE/data/reusables/github-connect/connect-dotcom-and-enterprise.md +++ b/translations/de-DE/data/reusables/github-connect/connect-dotcom-and-enterprise.md @@ -1 +1,6 @@ -1. Klicke auf **Connect to {% data variables.product.prodname_dotcom_the_website %}** (Verbinden mit). ![Verbinde von GitHub Enterprise Server-Einstellungen zu GitHub.com](/assets/images/help/settings/github.com_end_user_connection.png) +1. Klicke auf **Connect to {% data variables.product.prodname_dotcom_the_website %}** (Verbinden mit). +{% ifversion ghes %} + ![Verbinde von GitHub Enterprise Server-Einstellungen zu GitHub.com](/assets/images/help/settings/github.com_end_user_connection.png) +{% else %} + ![Connect to GitHub.com from GitHub AE settings](/assets/images/enterprise/github-ae/settings/github.com-end-user-connection.png) +{% endif %} diff --git a/translations/de-DE/data/reusables/github-connect/send-contribution-counts-to-githubcom.md b/translations/de-DE/data/reusables/github-connect/send-contribution-counts-to-githubcom.md new file mode 100644 index 0000000000..96f6fbc179 --- /dev/null +++ b/translations/de-DE/data/reusables/github-connect/send-contribution-counts-to-githubcom.md @@ -0,0 +1 @@ +1. Aktivieren Sie unter „Contributions“ (Beiträge) das Kontrollkästchen **Send my contribution counts to {% data variables.product.prodname_dotcom_the_website %}** (Anzahl meiner Beiträge an {% data variables.product.prodname_dotcom_the_website %} senden), und klicken Sie auf **Update contributions** (Beiträge aktualisieren). ![Kontrollkästchen „Send my contribution counts...“ (Anzahl meiner Beiträge senden) und Schaltfläche „Update contributions“ (Beiträge aktualisieren)](/assets/images/help/settings/send-and-update-contributions.png) diff --git a/translations/de-DE/data/reusables/github-connect/sync-frequency.md b/translations/de-DE/data/reusables/github-connect/sync-frequency.md index 925b8e8f4e..751b18fad0 100644 --- a/translations/de-DE/data/reusables/github-connect/sync-frequency.md +++ b/translations/de-DE/data/reusables/github-connect/sync-frequency.md @@ -1 +1 @@ -{% data variables.product.prodname_ghe_server %} sendet stündlich Updates. +{% data variables.product.product_name %} sendet stündlich Updates. diff --git a/translations/de-DE/data/reusables/notifications-v2/custom-notification-types.md b/translations/de-DE/data/reusables/notifications-v2/custom-notification-types.md index d29d7447d4..2299c52284 100644 --- a/translations/de-DE/data/reusables/notifications-v2/custom-notification-types.md +++ b/translations/de-DE/data/reusables/notifications-v2/custom-notification-types.md @@ -1,2 +1,2 @@ {%- ifversion fpt or ghes > 3.1 or ghae-issue-4910 %}issues, pulls requests, releases, security alerts, or discussions{% endif %} -{%- ifversion ghes = 3.1 or ghae-next %}issues, pull requests, releases, or discussions{% endif %} +{%- ifversion ghes = 3.1 %}issues, pull requests, releases, or discussions{% endif %} diff --git a/translations/de-DE/data/reusables/pages/about-private-publishing.md b/translations/de-DE/data/reusables/pages/about-private-publishing.md index f1f13531ce..7d6708b21e 100644 --- a/translations/de-DE/data/reusables/pages/about-private-publishing.md +++ b/translations/de-DE/data/reusables/pages/about-private-publishing.md @@ -1 +1 @@ -If your project site is published from a private or internal repository owned by an organization using {% data variables.product.prodname_ghe_cloud %}, you can manage access control for the site. +If your project site is published from a private or internal repository owned by an organization using {% data variables.product.prodname_ghe_cloud %}, you can manage access control for the site. In an {% data variables.product.prodname_emu_enterprise %}, all {% data variables.product.prodname_pages %} sites are privately published. diff --git a/translations/de-DE/data/reusables/repositories/auto-gen-release-public-beta.md b/translations/de-DE/data/reusables/repositories/auto-gen-release-public-beta.md new file mode 100644 index 0000000000..1271ce25e0 --- /dev/null +++ b/translations/de-DE/data/reusables/repositories/auto-gen-release-public-beta.md @@ -0,0 +1 @@ +Automatically generated release notes are currently in public beta and subject to change. diff --git a/translations/de-DE/data/reusables/repositories/disabling-markdown-rendering.md b/translations/de-DE/data/reusables/repositories/disabling-markdown-rendering.md new file mode 100644 index 0000000000..86254f64ec --- /dev/null +++ b/translations/de-DE/data/reusables/repositories/disabling-markdown-rendering.md @@ -0,0 +1,5 @@ +When viewing a Markdown file, you can click {% octicon "code" aria-label="The code icon" %} at the top of the file to disable Markdown rendering and view the file's source instead. + +![Display Markdown as source](/assets/images/help/writing/display-markdown-as-source.png) + +Disabling Markdown rendering enables you to use source view features, such as line linking, which is not possible when viewing rendered Markdown files. diff --git a/translations/de-DE/data/reusables/repositories/request-security-advisory-cve-id.md b/translations/de-DE/data/reusables/repositories/request-security-advisory-cve-id.md index 82da553b0d..64c1f4bb0d 100644 --- a/translations/de-DE/data/reusables/repositories/request-security-advisory-cve-id.md +++ b/translations/de-DE/data/reusables/repositories/request-security-advisory-cve-id.md @@ -1,5 +1,3 @@ -Wenn Du noch keine CVE-Identifikationsnummer für die Sicherheitslücke in Deinem Projekt hast, kannst Du eine CVE-Identifikationsnummer bei {% data variables.product.prodname_dotcom %} anfordern. {% data variables.product.prodname_dotcom %} usually reviews the request within 72 hours. Requesting a CVE identification number doesn't make your security advisory public. If your security advisory is eligible for a CVE, {% data variables.product.prodname_dotcom %} will reserve a CVE identification number for your advisory. We'll then publish the CVE details after you publish the security advisory. +If you want a CVE identification number for the security vulnerability in your project, and don't already have one, you can request a CVE identification number from {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_dotcom %} usually reviews the request within 72 hours. Requesting a CVE identification number doesn't make your security advisory public. If your security advisory is eligible for a CVE, {% data variables.product.prodname_dotcom %} will reserve a CVE identification number for your advisory. We'll then publish the CVE details after you make your security advisory public. Anyone with admin permissions to a security advisory can request a CVE identification number. -If you already have a CVE you want to use, for example, if you use a CNA other than {% data variables.product.prodname_dotcom %}, add it to the security advisory form. This may happen, for example, if you want to get the advisory consistent with other communications you plan to send out at publication time. - -If an advisory form doesn't have a CVE, we will request a CVE for you when you publish the advisory. +If you already have a CVE you want to use, for example, if you use a CVE Numbering Authority (CNA) other than {% data variables.product.prodname_dotcom %}, add the CVE to the security advisory form. This may happen, for example, if you want to get the advisory consistent with other communications you plan to send out at publication time. {% data variables.product.prodname_dotcom %} cannot assign CVEs to your project if it is covered by another CNA. \ No newline at end of file diff --git a/translations/de-DE/data/reusables/repositories/sidebar-issues.md b/translations/de-DE/data/reusables/repositories/sidebar-issues.md index 2edf599142..e58a10bb9e 100644 --- a/translations/de-DE/data/reusables/repositories/sidebar-issues.md +++ b/translations/de-DE/data/reusables/repositories/sidebar-issues.md @@ -1,5 +1,5 @@ 2. Klicken Sie unter dem Namen des Repositorys auf {% octicon "issue-opened" aria-label="The issues icon" %} **Issues**. - {% ifversion fpt or ghes > 3.1 or ghae-issue-4483 %} + {% ifversion fpt or ghes > 3.1 or ghae-next %} ![Registerkarte „Issues"](/assets/images/help/repository/repo-tabs-issues.png){% else %} ![Issues tab](/assets/images/enterprise/3.1/help/repository/repo-tabs-issues.png){% endif %} diff --git a/translations/de-DE/data/reusables/repositories/sidebar-pr.md b/translations/de-DE/data/reusables/repositories/sidebar-pr.md index f3ac0fe0c5..bb3684adde 100644 --- a/translations/de-DE/data/reusables/repositories/sidebar-pr.md +++ b/translations/de-DE/data/reusables/repositories/sidebar-pr.md @@ -1,5 +1,5 @@ 1. Klicken Sie unter dem Namen des Repositorys auf {% octicon "git-pull-request" aria-label="The pull request icon" %} **Pull requests**. - {% ifversion fpt or ghes > 3.1 or ghae-issue-4483 %} + {% ifversion fpt or ghes > 3.1 or ghae-next %} ![Auswahl der Issue- und Pull-Request-Registerkarten](/assets/images/help/repository/repo-tabs-pull-requests.png){% else %} ![Issues tab](/assets/images/enterprise/3.1/help/repository/repo-tabs-pull-requests.png){% endif %} diff --git a/translations/de-DE/data/reusables/repositories/workflow-notifications.md b/translations/de-DE/data/reusables/repositories/workflow-notifications.md index 30c2556fb8..0bf31075a4 100644 --- a/translations/de-DE/data/reusables/repositories/workflow-notifications.md +++ b/translations/de-DE/data/reusables/repositories/workflow-notifications.md @@ -1,4 +1,4 @@ -Wenn Sie E-Mail- oder Webbenachrichtigungen für {% data variables.product.prodname_actions %} aktivieren, erhalten Sie eine Benachrichtigung, wenn ein von Ihnen ausgelöster Workflow abgeschlossen ist. Die Benachrichtigung enthält den Status der Workflow-Ausführung (einschließlich erfolgreicher, fehlgeschlagener, neutraler und abgebrochener Ausführungen). Sie können auch auswählen, ob Sie nur dann eine Benachrichtigung erhalten möchten, wenn eine Workflow-Ausführung fehlgeschlagen ist. +Wenn Sie E-Mail- oder Webbenachrichtigungen für {% data variables.product.prodname_actions %} aktivieren, erhalten Sie eine Benachrichtigung, wenn ein von Ihnen ausgelöster Workflow abgeschlossen ist. Die Benachrichtigung enthält den Status der Workflow-Ausführung (einschließlich erfolgreicher, fehlgeschlagener, neutraler und abgebrochener Ausführungen). Sie können auch auswählen, ob Sie nur dann eine Benachrichtigung erhalten möchten, wenn eine Workflow-Ausführung fehlgeschlagen ist. For more information about enabling or disabling notifications, see "[About notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)." Notifications for scheduled workflows are sent to the user who initially created the workflow. If a different user updates the cron syntax in the workflow file, subsequent notifications will be sent to that user instead.{% ifversion fpt or ghes > 2.22 %} If a scheduled workflow is disabled and then re-enabled, notifications will be sent to the user who re-enabled the workflow rather than the user who last modified the cron syntax.{% endif %} diff --git a/translations/de-DE/data/reusables/saml/about-linked-identities.md b/translations/de-DE/data/reusables/saml/about-linked-identities.md index 1254b5131d..527d283559 100644 --- a/translations/de-DE/data/reusables/saml/about-linked-identities.md +++ b/translations/de-DE/data/reusables/saml/about-linked-identities.md @@ -1,3 +1,3 @@ -Du kannst die Single Sign-On-Identität anzeigen, die ein Mitglied mit seinem {% data variables.product.product_name %}-Konto verknüpft hat. Wenn verfügbar, wird der Eintrag SCIM-Daten enthalten. Weitere Informationen findest Du unter „[Über SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)." +Du kannst die Single Sign-On-Identität anzeigen, die ein Mitglied mit seinem {% data variables.product.product_name %}-Konto verknüpft hat. Wenn ein Mitglied die falsche Identität mit seinem {% data variables.product.product_name %}-Konto verknüpft, kannst Du die verknüpfte Identität widerrufen, damit das Mitglied es erneut versuchen kann. diff --git a/translations/de-DE/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/de-DE/data/reusables/secret-scanning/partner-secret-list-private-repo.md index 7bb265bee2..9e6a06ebd2 100644 --- a/translations/de-DE/data/reusables/secret-scanning/partner-secret-list-private-repo.md +++ b/translations/de-DE/data/reusables/secret-scanning/partner-secret-list-private-repo.md @@ -1,7 +1,7 @@ | Provider | Supported secret | API slug | | -------- | ---------------- | -------- | | | | | -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Adafruit IO | Adafruit IO Key | adafruit_io_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Adobe | Adobe Device Token | adobe_device_token{% endif %} @@ -11,73 +11,73 @@ Adobe | Adobe Service Token | adobe_service_token{% endif %} Adobe | Adobe Short-Lived Access Token | adobe_short_lived_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Adobe | Adobe JSON Web Token | adobe_jwt{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Alibaba Cloud | Alibaba Cloud Access Key ID | alibaba_cloud_access_key_id{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Alibaba Cloud | Alibaba Cloud Access Key Secret | alibaba_cloud_access_key_secret{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Amazon Web Services (AWS) | Amazon AWS Access Key ID | aws_access_key_id{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Amazon Web Services (AWS) | Amazon AWS Secret Access Key | aws_secret_access_key{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Amazon Web Services (AWS) | Amazon AWS Session Token | aws_session_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Amazon Web Services (AWS) | Amazon AWS Temporary Access Key ID | aws_temporary_access_key_id{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Asana | Asana Personal Access Token | asana_personal_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Atlassian | Atlassian API Token | atlassian_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Atlassian | Atlassian JSON Web Token | atlassian_jwt{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Atlassian | Bitbucket Server Personal Access Token | bitbucket_server_personal_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Azure | Azure SAS Token | azure_sas_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Azure | Azure Service Management Certificate | azure_management_certificate{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Azure | Azure SQL Connection String | azure_sql_connection_string{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Azure | Azure Storage Account Key | azure_storage_account_key{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Beamer | Beamer API Key | beamer_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Checkout.com | Checkout.com Production Secret Key | checkout_production_secret_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Checkout.com | Checkout.com Test Secret Key | checkout_test_secret_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Clojars | Clojars Deploy Token | clojars_deploy_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} CloudBees CodeShip | CloudBees CodeShip Credential | codeship_credential{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Contentful | Contentful Personal Access Token | contentful_personal_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Databricks | Databricks Access Token | databricks_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Discord | Discord Bot Token | discord_bot_token{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Doppler | Doppler Personal Token | doppler_personal_token{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Doppler | Doppler Service Token | doppler_service_token{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Doppler | Doppler CLI Token | doppler_cli_token{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Doppler | Doppler SCIM Token | doppler_scim_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Doppler | Doppler Audit Token | doppler_audit_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Dropbox | Dropbox Access Token | dropbox_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Dropbox | Dropbox Short Lived Access Token | dropbox_short_lived_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Duffel | Duffel Live Access Token | duffel_live_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Duffel | Duffel Test Access Token | duffel_test_access_token{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Dynatrace | Dynatrace Access Token | dynatrace_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Dynatrace | Dynatrace Internal Token | dynatrace_internal_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} EasyPost | EasyPost Production API Key | easypost_production_api_key{% endif %} @@ -87,17 +87,17 @@ EasyPost | EasyPost Test API Key | easypost_test_api_key{% endif %} Facebook | Facebook Access Token | facebook_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Fastly | Fastly API Token | fastly_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Finicity | Finicity App Key | finicity_app_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Flutterwave | Flutterwave Live API Secret Key | flutterwave_live_api_secret_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Flutterwave | Flutterwave Test API Secret Key | flutterwave_test_api_secret_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Frame.io | Frame.io JSON Web Token | frameio_jwt{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Frame.io| Frame.io Developer Token | frameio_developer_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} FullStory | FullStory API Key | fullstory_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} GitHub | GitHub Personal Access Token | github_personal_access_token{% endif %} @@ -107,29 +107,29 @@ GitHub | GitHub OAuth Access Token | github_oauth_access_token{% endif %} GitHub | GitHub Refresh Token | github_refresh_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} GitHub | GitHub App Installation Access Token | github_app_installation_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} GitHub | GitHub SSH Private Key | github_ssh_private_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} GoCardless | GoCardless Live Access Token | gocardless_live_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} GoCardless | GoCardless Sandbox Access Token | gocardless_sandbox_access_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Google | Firebase Cloud Messaging Server Key | firebase_cloud_messaging_server_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Google | Google API Key | google_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Google | Google Cloud Private Key ID | google_cloud_private_key_id{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Google | Google Cloud Storage Access Key Secret | google_cloud_storage_access_key_secret{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Google | Google Cloud Storage Service Account Access Key ID | google_cloud_storage_service_account_access_key_id{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Google | Google Cloud Storage User Access Key ID | google_cloud_storage_user_access_key_id{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Grafana | Grafana API Key | grafana_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Hashicorp Terraform | Terraform Cloud / Enterprise API Token | terraform_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Hubspot | Hubspot API Key | hubspot_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Intercom | Intercom Access Token | intercom_access_token{% endif %} @@ -137,9 +137,9 @@ Intercom | Intercom Access Token | intercom_access_token{% endif %} Ionic | Ionic Personal Access Token | ionic_personal_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Ionic | Ionic Refresh Token | ionic_refresh_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} JFrog | JFrog Platform Access Token | jfrog_platform_access_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} JFrog | JFrog Platform API Key | jfrog_platform_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Linear | Linear API Key | linear_api_key{% endif %} @@ -149,15 +149,23 @@ Linear | Linear OAuth Access Token | linear_oauth_access_token{% endif %} Lob | Lob Live API Key | lob_live_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Lob | Lob Test API Key | lob_test_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Mailchimp | Mailchimp API Key | mailchimp_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Mailgun | Mailgun API Key | mailgun_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} MessageBird | MessageBird API Key | messagebird_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} +New Relic | New Relic Personal API Key | new_relic_personal_api_key{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +New Relic | New Relic REST API Key | new_relic_rest_api_key{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +New Relic | New Relic Insights Query Key | new_relic_insights_query_key{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +New Relic | New Relic License Key | new_relic_license_key{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} npm | npm Access Token | npm_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} NuGet | NuGet API Key | nuget_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Onfido | Onfido Live API Token | onfido_live_api_token{% endif %} @@ -165,75 +173,75 @@ Onfido | Onfido Live API Token | onfido_live_api_token{% endif %} Onfido | Onfido Sandbox API Token | onfido_sandbox_api_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} OpenAI | OpenAI API Key | openai_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Palantir | Palantir JSON Web Token | palantir_jwt{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} PlanetScale | PlanetScale Database Password | planetscale_database_password{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} PlanetScale | PlanetScale OAuth Token | planetscale_oauth_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} PlanetScale | PlanetScale Service Token | planetscale_service_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Plivo | Plivo Auth ID | plivo_auth_id{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Plivo | Plivo Auth Token | plivo_auth_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Postman | Postman API Key | postman_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Proctorio | Proctorio Consumer Key | proctorio_consumer_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Proctorio | Proctorio Linkage Key | proctorio_linkage_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Proctorio | Proctorio Registration Key | proctorio_registration_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Proctorio | Proctorio Secret Key | proctorio_secret_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Pulumi | Pulumi Access Token | pulumi_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} PyPI | PyPI API Token | pypi_api_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} RubyGems | RubyGems API Key | rubygems_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Samsara | Samsara API Token | samsara_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Samsara | Samsara OAuth Access Token | samsara_oauth_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} SendGrid | SendGrid API Key | sendgrid_api_key{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Sendinblue | Sendinblue API Key | sendinblue_api_key{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Sendinblue | Sendinblue SMTP Key | sendinblue_smtp_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Shippo | Shippo Live API Token | shippo_live_api_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Shippo | Shippo Test API Token | shippo_test_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Shopify | Shopify App Shared Secret | shopify_app_shared_secret{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Shopify | Shopify Access Token | shopify_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Shopify | Shopify Custom App Access Token | shopify_custom_app_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Shopify | Shopify Private App Password | shopify_private_app_password{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Slack | Slack API Token | slack_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Slack | Slack Incoming Webhook URL | slack_incoming_webhook_url{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Slack | Slack Workflow Webhook URL | slack_workflow_webhook_url{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} SSLMate | SSLMate API Key | sslmate_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} SSLMate | SSLMate Cluster Secret | sslmate_cluster_secret{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Stripe | Stripe API Key | stripe_api_key{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Stripe | Stripe Live API Secret Key | stripe_live_secret_key{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Stripe | Stripe Test API Secret Key | stripe_test_secret_key{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Stripe | Stripe Live API Restricted Key | stripe_live_restricted_key{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Stripe | Stripe Test API Restricted Key | stripe_test_restricted_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Stripe | Stripe Webhook Signing Secret | stripe_webhook_signing_secret{% endif %} @@ -241,9 +249,9 @@ Stripe | Stripe Webhook Signing Secret | stripe_webhook_signing_secret{% endif % Tableau | Tableau Personal Access Token | tableau_personal_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Telegram | Telegram Bot Token | telegram_bot_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Tencent Cloud | Tencent Cloud Secret ID | tencent_cloud_secret_id{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Twilio | Twilio Account String Identifier | twilio_account_sid{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Twilio | Twilio API Key | twilio_api_key{% endif %} diff --git a/translations/de-DE/data/reusables/sponsors/add-welcome-message.md b/translations/de-DE/data/reusables/sponsors/add-welcome-message.md new file mode 100644 index 0000000000..8962236ad1 --- /dev/null +++ b/translations/de-DE/data/reusables/sponsors/add-welcome-message.md @@ -0,0 +1 @@ +1. Optionally, type a welcome message for the tier. ![Add welcome message](/assets/images/help/sponsors/add-a-welcome-message.png) \ No newline at end of file diff --git a/translations/de-DE/data/reusables/sponsors/tier-details.md b/translations/de-DE/data/reusables/sponsors/tier-details.md index 3cd4e49974..466169f788 100644 --- a/translations/de-DE/data/reusables/sponsors/tier-details.md +++ b/translations/de-DE/data/reusables/sponsors/tier-details.md @@ -1,4 +1,4 @@ -You can create up to 10 one-time sponsorship tiers and 10 monthly tiers for sponsors to choose from. Each tier has its own one-time or monthly payment amount in US dollars, and you can choose to enable tiers for custom amounts. In addition, you can choose to enable tiers for custom amounts (monthly and one-time). +You can create up to 10 one-time sponsorship tiers and 10 monthly tiers for sponsors to choose from. Each tier has its own one-time or monthly payment amount in US dollars, and you can choose to enable tiers for custom amounts. In addition, you can choose to enable tiers for custom amounts (monthly and one-time). You can customize the rewards for each tier. For example, rewards for a tier could include: - Early access to new versions @@ -7,4 +7,6 @@ You can customize the rewards for each tier. For example, rewards for a tier cou - Weekly newsletter updates - Other rewards your sponsors would enjoy ✨ +You can include a welcome message with information about accessing or receiving rewards, which will be visible after payment and in the welcome email. + Once you have published a tier, you cannot edit the price of that tier. Stattdessen musst Du die Stufe zurückziehen und einen neue Stufe erstellen. Existing sponsors will remain on the retired tier until they change their sponsorship tier, cancel their sponsorship, or their one-time sponsorship period expires. diff --git a/translations/de-DE/data/reusables/ssh/add-ssh-key-to-ssh-agent-commandline.md b/translations/de-DE/data/reusables/ssh/add-ssh-key-to-ssh-agent-commandline.md index 415f86736d..9bed61119b 100644 --- a/translations/de-DE/data/reusables/ssh/add-ssh-key-to-ssh-agent-commandline.md +++ b/translations/de-DE/data/reusables/ssh/add-ssh-key-to-ssh-agent-commandline.md @@ -1,3 +1,3 @@ ```shell -$ ssh-add ~/.ssh/id_ed25519 +$ ssh-add ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %} ``` diff --git a/translations/de-DE/data/reusables/ssh/add-ssh-key-to-ssh-agent.md b/translations/de-DE/data/reusables/ssh/add-ssh-key-to-ssh-agent.md index fb1ca5ec34..43243b9f14 100644 --- a/translations/de-DE/data/reusables/ssh/add-ssh-key-to-ssh-agent.md +++ b/translations/de-DE/data/reusables/ssh/add-ssh-key-to-ssh-agent.md @@ -1 +1 @@ -If you created your key with a different name, or if you are adding an existing key that has a different name, replace *id_ed25519* in the command with the name of your private key file. +If you created your key with a different name, or if you are adding an existing key that has a different name, replace *id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}* in the command with the name of your private key file. diff --git a/translations/de-DE/data/reusables/user_settings/generate_new_token.md b/translations/de-DE/data/reusables/user_settings/generate_new_token.md new file mode 100644 index 0000000000..86e5deeb02 --- /dev/null +++ b/translations/de-DE/data/reusables/user_settings/generate_new_token.md @@ -0,0 +1 @@ +1. Klicke auf **Generate new token** (Neues Token erzeugen). ![Schaltfläche „Generate new token“ (Neues Token erzeugen)](/assets/images/help/settings/generate_new_token.png) \ No newline at end of file diff --git a/translations/de-DE/data/ui.yml b/translations/de-DE/data/ui.yml index 4e8fd826af..f7e85cc34f 100644 --- a/translations/de-DE/data/ui.yml +++ b/translations/de-DE/data/ui.yml @@ -30,9 +30,10 @@ toc: guides: Leitfäden whats_new: What's new pages: - article_version: 'Artikelversion:' + article_version: 'Artikelversion' miniToc: Inhalt dieses Artikels contributor_callout: This article is contributed and maintained by + all_enterprise_releases: All Enterprise releases errors: oops: Hoppla! something_went_wrong: Leider ist ein Fehler aufgetreten. @@ -155,13 +156,17 @@ product_sublanding: learning_paths_desc: Learning paths are a collection of guides that help you master a particular subject. guides: '{{ productMap[currentProduct].name }} guides' more_guides: more guides - no_result: Sorry, there are no guides that match your filter. load_more: Load more guides all_guides: 'All {{ productMap[currentProduct].name }} guides' + filter_instructions: Filter the guide list using these controls filters: type: Typ topic: Topic all: Alle + guides_found: + multiple: '{n} guides found' + one: 1 guide found + none: No guides found guide_types: overview: Übersicht quick_start: Schnellstart diff --git a/translations/de-DE/data/variables/product.yml b/translations/de-DE/data/variables/product.yml index 4beec2e463..130282d945 100644 --- a/translations/de-DE/data/variables/product.yml +++ b/translations/de-DE/data/variables/product.yml @@ -76,6 +76,14 @@ prodname_actions: 'GitHub Actions' prodname_debug: 'GitHub Debug' #GitHub Discussions prodname_discussions: 'GitHub Discussions' +#GitHub Enterprise Managed Users +prodname_emu_idp_application: 'GitHub Enterprise Managed User' +prodname_emus: 'Enterprise Managed Users' +prodname_managed_user: 'managed user' +prodname_managed_users: 'managed users' +prodname_managed_users_caps: 'Managed users' +prodname_emu_enterprise: 'enterprise with managed users' +prodname_emu_org: 'organization with managed users' #GitHub Issues prodname_github_issues: 'GitHub Issues' #GitHub Packages @@ -94,6 +102,7 @@ prodname_security_center: 'Security Center' #Codespaces prodname_codespaces: 'Codespaces' prodname_github_codespaces: 'GitHub Codespaces' +prodname_serverless: 'web-based editor' #GitHub resources: blog, jobs, Learning Lab prodname_gcf: 'GitHub Community Support' prodname_blog: 'der GitHub-Blog' @@ -135,6 +144,8 @@ prodname_dependabot_version_updates: 'Dependabot version updates' #GitHub Archive Program prodname_archive: 'GitHub Archive-Programm' prodname_arctic_vault: 'Arctic Code Vault' +#GitHub Copilot +prodname_copilot: 'GitHub Copilot' #Links product_url: >- {% ifversion fpt %}github.com{% else %}[hostname]{% endif %} diff --git a/translations/de-DE/data/variables/release_candidate.yml b/translations/de-DE/data/variables/release_candidate.yml index e6ddf079ac..ec65ef6f94 100644 --- a/translations/de-DE/data/variables/release_candidate.yml +++ b/translations/de-DE/data/variables/release_candidate.yml @@ -1,2 +1,2 @@ --- -version: enterprise-server@3.2 +version: '' diff --git a/translations/es-ES/content/account-and-profile/index.md b/translations/es-ES/content/account-and-profile/index.md index 795617d05b..6a2bad3f20 100644 --- a/translations/es-ES/content/account-and-profile/index.md +++ b/translations/es-ES/content/account-and-profile/index.md @@ -1,7 +1,7 @@ --- -title: Your account and profile on GitHub -shortTitle: Account and profile -intro: 'Make {% data variables.product.product_name %} work best for you by adjusting the settings for your user account, personalizing your profile page, and managing the notifications you receive for activity on {% data variables.product.prodname_dotcom %}.' +title: Tu cuenta y perfil en GitHub +shortTitle: Cuenta y perfil +intro: 'Haz que {% data variables.product.product_name %} funcione de la mejor forma para ti configurando los ajustes para tu cuenta de usuario, personalizando tu página de perfil y administrando las notificaciones que recibes de la actividad en {% data variables.product.prodname_dotcom %}.' introLinks: quickstart: /get-started/onboarding/getting-started-with-your-github-account featuredLinks: diff --git a/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md b/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md index 9451aca936..51cb7e2039 100644 --- a/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md +++ b/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md @@ -45,7 +45,7 @@ Cuando te desuscribes de las notificaciones en tu bandeja de entrada, desaparece {% data reusables.notifications.access_notifications %} 1. Desde la bandeja de notificaciones, selecciona aquellas de las cuales deseas darte de baja. -2. Utiliza el menú desplegable de **seleccionado** {% octicon "triangle-down" aria-label="The down triangle icon" %} para dar clic en **Desuscribirse**. ![Opción para darse de baja de una bandeja principal](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png) +2. Click **Unsubscribe.** ![Opción para darse de baja de una bandeja principal](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png) ## Darse de baja de las notificaciones en la página de suscripciones @@ -61,13 +61,12 @@ Cuando dejas de observar un repositorio, de desuscribes de notificaciones futura {% data reusables.notifications.access_notifications %} 1. En la barra lateral izquierda, bajo la lista de repositorios, utiliza el menú desplegable de "Administrar notificaciones" para dar clic en **Repositorios que sigues**. ![Opciones del menú desplegable de administrar notificaciones](/assets/images/help/notifications-v2/manage-notifications-options.png) 2. En la página de repositorios que sigues, después de que hayas evaluado aquellos que estás siguiendo, decide si quieres: - {% ifversion ghae or ghes < 3.1 %} - - Dejar de seguir un repositorio - - Observar únicamente los lanzamientos de un repositorio - - Ignorar todas las notificaciones de un repositorio - {% endif %} {% ifversion fpt or ghes > 3.0 or ghae-next %} - Dejar de seguir un repositorio - Ignorar todas las notificaciones de un repositorio - Personaliza los tipos de evento para los cuales recibes notificaciones ({% data reusables.notifications-v2.custom-notification-types %}, en caso de que se haya habilitado) + {% else %} + - Dejar de seguir un repositorio + - Observar únicamente los lanzamientos de un repositorio + - Ignorar todas las notificaciones de un repositorio {% endif %} diff --git a/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md b/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md index 87eecd00aa..4ab366e0af 100644 --- a/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md +++ b/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md @@ -70,10 +70,10 @@ Muchas personas se olvidan de los repositorios que han marcado para observar. De 1. En la barra lateral izquierda, bajo la lista de repositorios, utiliza el menú desplegable "Administrar notificaciones" y da clic en **Repositorios que sigues**. ![Opciones del menú desplegable de administrar notificaciones](/assets/images/help/notifications-v2/manage-notifications-options.png) 2. Evalúa si los repositorios que estás siguiendo de cerca tienen actualizaciones que aún sean útiles y relevantes. Cuando sigues de cerca un repositorio, se te notificará de todas las conversaciones en el mismo. -{% ifversion ghae or ghes < 3.1 %} - ![Página de notificaciones que sigues](/assets/images/help/notifications-v2/watched-notifications.png) -{% elsif fpt or ghes > 3.0 or ghae-next %} +{% ifversion fpt or ghes > 3.0 or ghae-next %} ![Página de notificaciones que sigues](/assets/images/help/notifications-v2/watched-notifications-custom.png) +{% else %} + ![Página de notificaciones que sigues](/assets/images/help/notifications-v2/watched-notifications.png) {% endif %} {% tip %} diff --git a/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md b/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md index b1f6d5a8e3..06a1276a0f 100644 --- a/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md +++ b/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md @@ -29,7 +29,7 @@ Puedes elegir suscribirte a las notificaciones de: - Una conversación sobre un informe de problemas, solicitud de extracción o gist específico. - Todas las actividades en un repositorio o en un debate de equipo. - Actividades de CI, tales como el estado de los flujos de trabajo en los repositorios configurados con {% data variables.product.prodname_actions %}. {% ifversion fpt or ghes > 3.0 or ghae-next %} -- Repositorio {% data reusables.notifications-v2.custom-notification-types %} (en caso de que estén habilitadas). {% elsif ghae or ghes %} +- Repositorio {% data reusables.notifications-v2.custom-notification-types %} (si se habilitó).{% else %} - Lanzamientos en un repositorio.{% endif %} También puedes elegir seguir automáticamente todos los repositorios en los que tienes acceso de escritura, con excepción de sus bifurcaciones. Puedes seguir de cerca manualmente a cualquier otro repositorio al que tengas acceso si das clic en **Seguir**. 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 f7eea80646..d60a8f47ec 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 @@ -70,12 +70,14 @@ Las notificaciones por correo electrónico también permiten la flexibilidad con Cuando observas un repositorio, te suscribes a las actualizaciones de la actividad en el mismo. De forma similar, cuando observas las discusiones específicas de un equipo, te suscribes a todas las actualizaciones de la conversación en la página de ese equipo. Para obtener más información, consulta [Acerca de los debates del equipo](/organizations/collaborating-with-your-team/about-team-discussions)". Para ver los repositorios que estás observando, dirígete a tu [página de observados](https://github.com/watching). Para obtener más información, consulta la sección "[Administrar suscricpiones y notificaciones en GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)". + {% ifversion ghae or ghes < 3.1 %} ### Configurar notificaciones {% endif %} -Puedes configurar las notificaciones de un repositorio en la página del mismo o en tu página de observados.{% ifversion ghae or ghes < 3.1 %} puedes elegir solo recibir notificaciones para los lanzamientos de un repositorio o ignorar todas las notificaciones de este.{% endif %} +Puedes configurar las notificaciones de un repositorio en la página del mismo o en tu página de observados.{% ifversion ghes < 3.1 %} puedes elegir solo recibir notificaciones para los lanzamientos de un repositorio o ignorar todas las notificaciones de este.{% endif %} {% ifversion fpt or ghes > 3.0 or ghae-next %} + ### Acerca de las notificaciones personalizadas Puedes personalizar las notificaciones de un repositorio. Por ejemplo, puedes elegir que solo se te notifique cuando suceden las actualizaciones a uno o más eventos ({% data reusables.notifications-v2.custom-notification-types %}) dentro de un repositorio o ignorar todas las notificaciones de este. {% endif %} Para obtener más información, consulta la sección "[Configurar tus ajustes de observación para un repositorio individual](#configuring-your-watch-settings-for-an-individual-repository)" a continuación. @@ -158,25 +160,18 @@ Si inhabilitas la opción de "Observar los repositorios automáticamente", no po ## Configurar los ajustes de observación para un repositorio individual -Puedes elegir si quieres observar o dejar de observar un repositorio individual. You can also choose to only be notified of {% ifversion fpt or ghes > 3.0 or ghae-next %}certain event types such as {% data reusables.notifications-v2.custom-notification-types %} (if enabled for the repository){% else %}new releases{% endif %}, or completely ignore an individual repository. +Puedes elegir si quieres observar o dejar de observar un repositorio individual. También puedes elegir que solo se te notifique sobre {% ifversion fpt or ghes > 3.0 or ghae-next %}algunos tipos de evento tales como {% data reusables.notifications-v2.custom-notification-types %} (si es que se habilitó en el repositorio) {% else %}lanzamientos nuevos{% endif %}, o ignorar completamente un repositorio individual. {% data reusables.repositories.navigate-to-repo %} 2. En la esquina superior derecha, da clic en el menú desplegable "Observar" para seleccionar una opción de observación. -{% ifversion ghae or ghes < 3.1 %} - ![Ver opciones en un menú desplegable para un repositorio](/assets/images/help/notifications-v2/watch-repository-options.png) -{% elsif fpt or ghes > 3.0 or ghae-next %} +{% ifversion fpt or ghes > 3.0 or ghae-next %} ![Ver opciones en un menú desplegable para un repositorio](/assets/images/help/notifications-v2/watch-repository-options-custom.png) -La opción **Personalizar** te permite personalizar aún más las notificaciones para que solo se te notifique cuando suceden eventos específicos en el repositorio, adicionalmente a participar y tener @menciones. - -{% ifversion fpt or ghes > 3.1 or ghae-issue-4910 %} - ![Opciones de observación personalizada en un menú desplegable de un repositorio](/assets/images/help/notifications-v2/watch-repository-options-custom2-dotcom.png) + La opción **Personalizar** te permite personalizar aún más las notificaciones para que solo se te notifique cuando suceden eventos específicos en el repositorio, adicionalmente a participar y tener @menciones. {% else %} - ![Opciones de observación personalizada en un menú desplegable de un repositorio](/assets/images/enterprise/3.1/help/notifications-v2/watch-repository-options-custom2.png) -{% endif %} - -Si seleccionas "propuestas", se te notificará sobre y suscribirá a las actualizaciones de cada propuesta (incluyendo aquellas que existieron antes de que seleccionaras esta opción) del repositorio. Si se te @menciona en una solicitud de cambios de este repositorio, también recibirás notificaciones por este evento y se te suscribirá a las actualizaciones de esa solicitud de cambios específica adicionalmente a las notificaciones que tendrás sobre las propuestas. - + ![Ver opciones en un menú desplegable para un repositorio](/assets/images/help/notifications-v2/watch-repository-options.png){% endif %} +{% ifversion fpt or ghes > 3.0 or ghae-next %} + ![Opciones de observación personalizada en un menú desplegable de un repositorio](/assets/images/help/notifications-v2/watch-repository-options-custom2-dotcom.png) Si seleccionas "propuestas", se te notificará sobre y suscribirá a las actualizaciones de cada propuesta (incluyendo aquellas que existieron antes de que seleccionaras esta opción) del repositorio. Si se te @menciona en una solicitud de cambios de este repositorio, también recibirás notificaciones por este evento y se te suscribirá a las actualizaciones de esa solicitud de cambios específica adicionalmente a las notificaciones que tendrás sobre las propuestas. {% endif %} ## Elegir a dónde se envían las notificaciones por correo electrónico de tu organización diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md index 8dae84d95f..bfa45f58ca 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md @@ -15,9 +15,9 @@ topics: shortTitle: Perfil de la organización --- -You can optionally choose to add a description, location, website, and email address for your organization, and pin important repositories. You can customize your organization's profile by adding a README.md file. For more information, see "[Customizing your organization's profile](/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile)." +Opcionalmente, puedes optar por agregar una descripción, una ubicación, un sitio web y una dirección de correo electrónico para tu organización y anclar repositorios importantes. Puedes personalizar el perfil de tu organización agregando un archivo de README.md. Para obtener más información, consulta la sección "[Personalizar el perfil de tu organización ](/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile)". -{% ifversion fpt %}Para confirmar la identidad de tu organización y mostrar el distintivo "Verificada" en la página del perfil de tu organización, debes verificar los dominios de tu organización con {% data variables.product.product_name %}. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."{% endif %} +{% ifversion fpt %}Para confirmar la identidad de tu organización y mostrar el distintivo "Verificada" en la página del perfil de tu organización, debes verificar los dominios de tu organización con {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Verificar o aprobar un dominio para tu organización](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)".{% endif %} {% ifversion fpt or ghes > 3.2 %} ![Muestra de la página de perfil de una organización](/assets/images/help/organizations/org_profile_with_overview.png) diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md index 27050ad4d4..8e70d0e3ea 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md @@ -48,6 +48,14 @@ Cuando te registras en una cuenta, {% data variables.product.product_name %} te Puedes cambiar el nombre que se muestra en tu perfil. Este nombre también podría mostrarse junto a los comentarios que haces en los repositorios privados que pertenezcan a una organización. Para obtener más información, consulta "[Administrar cómo se ven los nombres de los miembros en tu organización](/articles/managing-the-display-of-member-names-in-your-organization)." +{% ifversion fpt %} +{% note %} + +**Nota:** Si eres un miembro de una {% data variables.product.prodname_emu_enterprise %}, cualquier cambio a tu nombre de perfil debe hacerse a través de tu proveedor de identidad en vez de con {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.emu-more-info-account %} + +{% endnote %} +{% endif %} + {% data reusables.user_settings.access_settings %} 2. Dentro de "Nombre", escribe el nombre que deseas que se muestre en tu perfil. ![Campo Nombre en configuraciones de perfil](/assets/images/help/profile/name-field.png) @@ -92,7 +100,7 @@ Cuando configuras tu estado, también puedes permitir que las personas sepan que ![El revisor solicitado muestra una nota de "busy" (ocupado) la lado del nombre de usuario](/assets/images/help/profile/request-a-review-limited-availability-status.png) -Si seleccionas la opción, "Busy" (Ocupado), cuando las personas mencionan tu nombre de usuario, te asignan una propuesta o una solicitud de extracción o te solicitan una revisión de solicitud de extracción, una nota al lado de tu nombre de usuario mostrará que estás ocupado. You will also be excluded from automatic review assignment for pull requests assigned to any teams you belong to. Para obtener más información, consulta la sección "[Administrar una tarea de revisión de código para tu equipo](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)". +Si seleccionas la opción, "Busy" (Ocupado), cuando las personas mencionan tu nombre de usuario, te asignan una propuesta o una solicitud de extracción o te solicitan una revisión de solicitud de extracción, una nota al lado de tu nombre de usuario mostrará que estás ocupado. También se te excluirá de la tarea de revisión automática para las solicitudes de cambio que se asignen a cualquier equipo al que pertenezcas. Para obtener más información, consulta la sección "[Administrar una tarea de revisión de código para tu equipo](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)". 1. En el ángulo superior derecho de {% data variables.product.product_name %}, haz clic en tu foto de perfil, después haz clic en **Set your status (Configurar tu estado)** o, si ya tienes un estado configurado, haz clic en tu estado actual. ![Botón en el perfil para configurar tu estado](/assets/images/help/profile/set-status-on-profile.png) 2. Para agregar un texto personalizado a tu estado, haz clic en el campo texto y escribe un mensaje de estado. ![Campo para escribir un mensaje de estado](/assets/images/help/profile/type-a-status-message.png) diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/index.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/index.md index e73e16257f..a2375e1673 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/index.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/index.md @@ -14,7 +14,7 @@ children: - /viewing-contributions-on-your-profile - /showing-an-overview-of-your-activity-on-your-profile - /publicizing-or-hiding-your-private-contributions-on-your-profile - - /sending-your-github-enterprise-server-contributions-to-your-githubcom-profile + - /sending-enterprise-contributions-to-your-githubcom-profile - /why-are-my-contributions-not-showing-up-on-my-profile - /troubleshooting-commits-on-your-timeline shortTitle: Administrar la gráfica de contribuciones diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-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/publicizing-or-hiding-your-private-contributions-on-your-profile.md index 02beebe8ee..ff9b8ccfd5 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-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/publicizing-or-hiding-your-private-contributions-on-your-profile.md @@ -14,14 +14,18 @@ topics: shortTitle: Contribuciones privadas --- -Si publicas tus contribuciones privadas, las personas sin acceso a los repositorios privados en los que trabajas no podrán ver los detalles de tus contribuciones privadas. En su lugar, verán la cantidad de contribuciones privadas que has realizado durante un determinado día. Tus contribuciones públicas incluirán información detallada. Para obtener más información, consulta "[Ver contribuciones en tu página de perfil](/articles/viewing-contributions-on-your-profile-page)". +Si publicas tus contribuciones privadas, las personas sin acceso a los repositorios privados en los que trabajas no podrán ver los detalles de tus contribuciones privadas. En su lugar, verán la cantidad de contribuciones privadas que has realizado durante un determinado día. Tus contribuciones públicas incluirán información detallada. Para obtener más información, consulta "[Ver contribuciones en tu página de perfil](/articles/viewing-contributions-on-your-profile-page)." + +{% note %} + +**Nota:** {% ifversion fpt or ghes %}En {% ifversion fpt %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_name %}{% endif %}, las contribuciones públicas en tu perfil son visibles {% ifversion fpt %}para cualquiera en el mundo que pueda acceder a {% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}únicamente para otros usuarios de {% data variables.product.product_location%}{% endif %}.{% elsif ghae %}En {% data variables.product.prodname_ghe_managed %}, solo otros miembros de tu empresa pueden ver las contribuciones en tu perfil.{% endif %} + +{% endnote %} ## Cambiar la visibilidad de tus contribuciones privadas -Por defecto, los visitantes únicamente ven las contribuciones públicas en tu perfil. - {% data reusables.profile.access_profile %} -2. Divulga u oculta tus contribuciones privadas en tu perfil: +1. Divulga u oculta tus contribuciones privadas en tu perfil: - Para publicitar tus contribuciones privadas, arriba de tu gráfico de contribuciones, utiliza el menú desplegable **Contribution settings** (Configuraciones de contribuciones) y selecciona **Private contributions** (Contribuciones privadas). Los visitantes verán tus recuentos de contribuciones privadas sin más detalles. ![Habilitar que los visitantes vean las contribuciones privadas desde el menú desplegable de configuraciones de contribuciones](/assets/images/help/profile/private-contributions-on.png) - Para ocultar tus contribuciones privadas, arriba de tu gráfico de contribuciones, utiliza el menú desplegable **Contribution settings** (Configuraciones de contribuciones) y anula la selección de **Private contributions** (Contribuciones privadas). Los visitantes únicamente verán tus contribuciones públicas. ![Habilitar que los visitantes vean las contribuciones privadas desde el menú desplegable de configuraciones de contribuciones](/assets/images/help/profile/private-contributions-off.png) diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md b/translations/es-ES/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 new file mode 100644 index 0000000000..511d08acd4 --- /dev/null +++ b/translations/es-ES/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 @@ -0,0 +1,65 @@ +--- +title: Enviar contribuciones empresariales a tu perfil de GitHub.com +intro: 'Puedes resaltar tu trabajo en {% data variables.product.prodname_enterprise %} al enviar los recuentos de contribuciones a tu perfil {% data variables.product.prodname_dotcom_the_website %}.' +redirect_from: + - /articles/sending-your-github-enterprise-contributions-to-your-github-com-profile/ + - /articles/sending-your-github-enterprise-server-contributions-to-your-github-com-profile + - /articles/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile + - /github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile + - /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile +versions: + fpt: '*' + ghes: '*' + ghae: next +topics: + - Profiles +shortTitle: Enviar contribuciones empresariales +--- + +## Acerca de las contribuciones empresariales en tu perfil de {% data variables.product.prodname_dotcom_the_website %} + +Tu perfil de {% data variables.product.prodname_dotcom_the_website %} muestra {% ifversion fpt %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae-next %}o conteos de contribución de {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} de los 90 días anteriores. Los recuentos de contribuciones de {% data reusables.github-connect.sync-frequency %} de {% data variables.product.prodname_enterprise %} se consideran contribuciones privadas. Los detalles de confirmación solo mostrarán los conteos de contribuciones y que estas se hicieron en un ambiente de {% data variables.product.prodname_enterprise %} fuera de {% data variables.product.prodname_dotcom_the_website %}. + +Puedes decidir si quieres que se muestren los conteos de las contribuciones privadas en tu perfil. Para obtener más información, consulta "[Publicar u ocultar tus contribuciones privadas en tu perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile/)." + +Para obtener más información acerca de cómo se calculan las contribuciones, consulta "[Administrar gráficos de contribuciones en tu perfil](/articles/managing-contribution-graphs-on-your-profile/)." + +{% note %} + +**Notas:** +- La conexión entre tus cuentas está regulada por la Declaración de privacidad de GitHub, y los usuarios que habilitan la conexión aceptan los Términos de servicio de GitHub. + +- Antes de que puedas conectar tu perfil de {% ifversion fpt %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae-next %}o de {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} a tu perfil de {% data variables.product.prodname_dotcom_the_website %}, tu propietario de empresa debe habilitar {% data variables.product.prodname_github_connect %} y también la capacidad de compartir contribuciones entre los ambientes. Para obtener más información, contacta a tu propietario de empresa. + +{% endnote %} + +{% ifversion fpt or ghes or ghae %} + +## Enviar las contribuciones de tu empresa a tu perfil de {% data variables.product.prodname_dotcom_the_website %} + +{% ifversion fpt %} + +- Para enviar contribuciones empresariales desde {% data variables.product.prodname_ghe_server %} a tu perfil de {% data variables.product.prodname_dotcom_the_website %}, consulta la sección "[Enviar contribuciones empresariales a tu perfil de {% data variables.product.prodname_dotcom_the_website %}](/enterprise-server/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)" en la documentación de {% data variables.product.prodname_ghe_server %}.{% ifversion ghae-next %} +- Para enviar contribuciones empresariales desde {% data variables.product.prodname_ghe_managed %} a tu perfil de {% data variables.product.prodname_dotcom_the_website %}, consulta la sección "[Enviar contribuciones empresariales a tu perfil de {% data variables.product.prodname_dotcom_the_website %}](/github-ae@latest/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)" en la documentación de {% data variables.product.prodname_ghe_managed %}.{% endif %} + +{% elsif ghes %} + +1. Iniciar sesión en {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_dotcom_the_website %}. +1. En {% data variables.product.prodname_ghe_server %}, en la esquina superior derecha de cualquier página, haz clic en tu foto de perfil y luego haz clic en **Ajustes**. ![Icono Settings (Parámetros) en la barra de usuario](/assets/images/help/settings/userbar-account-settings.png) +{% data reusables.github-connect.github-connect-tab-user-settings %} +{% data reusables.github-connect.connect-dotcom-and-enterprise %} +1. Revisa los recursos a los que {% data variables.product.prodname_ghe_server %} accederá desde tu cuenta de {% data variables.product.prodname_dotcom_the_website %}, posteriormente, da clic en **Autorizar**. ![Autorizar conexión entre GitHub Enterprise Server y GitHub.com](/assets/images/help/settings/authorize-ghe-to-connect-to-dotcom.png) +{% data reusables.github-connect.send-contribution-counts-to-githubcom %} + +{% elsif ghae %} + +1. Iniciar sesión en {% data variables.product.prodname_ghe_managed %} y {% data variables.product.prodname_dotcom_the_website %}. +1. En {% data variables.product.prodname_ghe_managed %}, en la esquina superior derecha de cualquier página, haz clic en tu foto de perfil y luego haz clic en **Ajustes**. ![Icono Settings (Parámetros) en la barra de usuario](/assets/images/help/settings/userbar-account-settings.png) +{% data reusables.github-connect.github-connect-tab-user-settings %} +{% data reusables.github-connect.connect-dotcom-and-enterprise %} +{% data reusables.github-connect.authorize-connection %} +{% data reusables.github-connect.send-contribution-counts-to-githubcom %} + +{% endif %} + +{% endif %} 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 f294d90697..7851071468 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 @@ -83,7 +83,7 @@ Las marcas horarias se calculan de forma diferente para las confirmaciones y las ![Sección de resumen de actividad en el perfil](/assets/images/help/profile/activity-overview-section.png) -Las organizaciones que se muestran en el resumen de la actividad se priorizan de acuerdo con qué tan activo estés en la organización. Si mencionas una organización en tu biografía de perfil y eres miembro de una organización, entonces esa organización se prioriza en el resumen de la actividad. Para obtener más información, consulta “[Mencionar personas y equipos](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)” o "[Agregar una biografía en tu perfil](/articles/adding-a-bio-to-your-profile/)." +Las organizaciones que se muestran en el resumen de la actividad se priorizan de acuerdo con qué tan activo estés en la organización. Si mencionas una organización en tu biografía de perfil y eres miembro de una organización, entonces esa organización se prioriza en el resumen de la actividad. For more information, see "[Mentioning people and teams](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)” or "[Adding a bio to your profile](/articles/adding-a-bio-to-your-profile/)." ## Actividad de contribución @@ -91,15 +91,14 @@ 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 not ghae %} -## Ver contribuciones de {% data variables.product.product_location_enterprise %} en {% data variables.product.prodname_dotcom_the_website %} +{% ifversion fpt or ghes or ghae-next %} + +## Ver contribuciones de {% data variables.product.prodname_enterprise %} en {% data variables.product.prodname_dotcom_the_website %} + +If you use {% ifversion fpt %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae-next %} 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)." -Si el administrador de tu sitio ha habilitado {% data variables.product.prodname_unified_contributions %}, puedes enviar conteos de contribuciones {% data variables.product.prodname_enterprise %} a tu perfil {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta "[Enviar tus contribuciones {% data variables.product.prodname_ghe_server %} a tu {% data variables.product.prodname_dotcom_the_website %}](/articles/sending-your-github-enterprise-server-contributions-to-your-github-com-profile)." {% endif %} ## Leer más - "[Ver las contribuciones en tu página de perfil](/articles/viewing-contributions-on-your-profile-page)" -- "[¿Por qué mis contribuciones no se ven en mi perfil?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)" -- "[Divulgar u ocultar tus contribuciones privadas en tu perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)" -- "[Mostrar una revisión de tu actividad en tu perfil](/articles/showing-an-overview-of-your-activity-on-your-profile)." diff --git a/translations/es-ES/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 b/translations/es-ES/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 index 62ac834847..15d77b6020 100644 --- a/translations/es-ES/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 +++ b/translations/es-ES/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 @@ -1,6 +1,6 @@ --- title: ¿Por qué mis contribuciones no aparecen en mi perfil? -intro: Learn common reasons that contributions may be missing from your contributions graph. +intro: Aprende sobre las razones habituales por las cuales podrían faltar contribuciones en tu gráfica. redirect_from: - /articles/why-are-my-contributions-not-showing-up-on-my-profile - /github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile @@ -11,10 +11,10 @@ versions: ghae: '*' topics: - Profiles -shortTitle: Missing contributions +shortTitle: Contribuciones faltantes --- -## About your contribution graph +## Acerca de tu gráfica de contribuciones Tu gráfico de contribución de perfil es un registro de las contribuciones que hiciste a los repositorios {% data variables.product.product_name %}. Las contribuciones son registros horarios de acuerdo a la zona horaria universal coordinada (UTC) en lugar de tu zona horaria local. Las contribuciones solo se cuentan si cumplen con determinados criterios. En algunos casos, necesitamos reconstruir tu gráfico para que aparezcan las contribuciones. diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md index eab710e7ff..7a26930628 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md @@ -24,6 +24,8 @@ Los repositorios que son propiedad de una organización pueden conceder acceso m {% ifversion fpt %} +Si eres un miembro de una {% data variables.product.prodname_emu_enterprise %}, solo puedes invitar a otros miembros de esta a que colaboren contigo. {% data reusables.enterprise-accounts.emu-more-info-account %} + {% note %} **Nota:** {% data variables.product.company_short %} limita la cantidad de personas que se pueden invitar a un repositorio dentro de un período de 24 horas. Si excedes este límite, espera 24 horas o crea una organización para colaborar con más personas. @@ -44,7 +46,7 @@ Los repositorios que son propiedad de una organización pueden conceder acceso m 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) 6. En "Colaboradores", comienza a escribir el nombre de usuario del colaborador. 7. Selecciona el nombre de usuario del colaborador del menú desplegable. ![Menú desplegable de la lista de colaboradores](/assets/images/help/repository/repo-settings-collab-autofill.png) -8. Haz clic en **Add collaborator** (Agregar colaborador). !["Add collaborator" button](/assets/images/help/repository/repo-settings-collab-add.png) +8. Haz clic en **Add collaborator** (Agregar colaborador). ![Botón de "Agregar colaborador"](/assets/images/help/repository/repo-settings-collab-add.png) {% endif %} {% ifversion fpt %} 9. El usuario recibirá un correo electrónico invitándolo al repositorio. Una vez que acepte la invitación, tendrá acceso de colaborador a tu repositorio. 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-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md index 62d244d221..2a2d496ca0 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-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md @@ -18,7 +18,9 @@ shortTitle: Agregar una dirección de correo electrónico {% note %} -**Nota**: {% data reusables.user_settings.no-verification-disposable-emails %} +**Notas**: + - {% data reusables.user_settings.no-verification-disposable-emails %} + - Si eres miembro de una {% data variables.product.prodname_emu_enterprise %}, no puedes hacer cambios a tu dirección de correo electrónico en {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.emu-more-info-account %} {% endnote %} 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-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md index 4dd4ddb6dc..90bc3189e9 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-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md @@ -49,7 +49,7 @@ Verás actualizaciones en tus noticias cuando un usuario que sigues: - Abre una propuesta o una solicitud de extracción con la etiqueta "se busca ayuda" o "primera buena propuesta" en un repositorio que estás mirando. - Sube las confirmaciones a un repositorio que estés observando.{% ifversion fpt or ghes %} - Bifurque un repositorio público.{% endif %} -- Publishes a new release. +- Publica un lanzamiento nuevo. Para obtener más información acerca de cómo destacar repositorios y seguir personas, consulta "[Guardar repositorios con estrellas](/articles/saving-repositories-with-stars/)" y "[Seguir a personas](/articles/following-people)". 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/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md index f1860f9f91..c00a55111e 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/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md @@ -19,11 +19,11 @@ shortTitle: Cambiar tu nombre de usuario ## Acerca de los cambios de nombre de usuario -You can change your username to another username that is not currently in use.{% ifversion fpt %} 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. +Puedes cambiar tu nombre de usuario a otro que no esté en uso actualmente.{% ifversion fpt %} 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. -If you hold a trademark for the username, you can find more information about making a trademark complaint on our [Trademark Policy](/articles/github-trademark-policy/) page. +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](/articles/github-trademark-policy/). -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 %} 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 %} +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. @@ -31,6 +31,12 @@ Una vez que cambies tu nombre de usuario, el nombre de usuario anterior estará - [@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 %} + +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. 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-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md index ea94e1fa9c..e075f8c48a 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-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md @@ -24,7 +24,7 @@ shortTitle: Un usuario en una organización - Una organización **no puede** volver a convertirse en un usuario. - Las llaves SSH, tokens de OAuth, perfiles de trabajo, reacciones, y el resto de la información asociada con el usuario, **no** se transferirán a la organización. Esto es solo true para la cuenta de usuario que se convertirá, no para cualquiera de los colaboradores de la cuenta del usuario. - Todas las confirmaciones realizadas a la cuenta del usuario convertida **ya no se asociarán** con esa cuenta. Las confirmaciones **permanecerán** intactas. - - Any forks of private repositories made with the converted user account will be deleted. + - Cualquier bifurcación de un repositorio privado que se haga con la cuenta de usuario convertida, se borrará. {% endwarning %} 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-github-user-account/managing-user-account-settings/index.md index 2e8d27c323..f6aadad2c5 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-github-user-account/managing-user-account-settings/index.md @@ -15,6 +15,7 @@ topics: children: - /about-your-personal-dashboard - /managing-your-theme-settings + - /managing-your-tab-size-rendering-preference - /changing-your-github-username - /merging-multiple-user-accounts - /converting-a-user-into-an-organization 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-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories.md index b828e624f5..4efe0c05f8 100644 --- 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-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories.md @@ -1,6 +1,6 @@ --- title: Administrar el nombre de la rama predeterminada para tus repositorios -intro: 'You can set the default branch name for new repositories that you create on {% data variables.product.product_location %}.' +intro: 'Puedes configurar el nombre de la rama predeterminada para los repositorios nuevos que crees en {% data variables.product.product_location %}.' versions: fpt: '*' ghes: '>=3.0' 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 new file mode 100644 index 0000000000..d485a2cde4 --- /dev/null +++ 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 @@ -0,0 +1,15 @@ +--- +title: Administrar tu preferencia de representación de tamaño de pestaña +intro: Puedes administrar la cantidad de espacios que representa una pestaña en tu cuenta de usuario. +versions: + fpt: '*' +topics: + - Accounts +shortTitle: Administrar el tamaño de tu pestaña +--- + +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 de configuración de usuario, da clic en **Apariencia**. ![Pestaña de "Apariencia" en la barra lateral de configuración de usuario](/assets/images/help/settings/appearance-tab.png) +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-github-user-account/managing-user-account-settings/managing-your-theme-settings.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md index 9fc06b77e8..fabfd0691b 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md @@ -3,6 +3,7 @@ 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: next ghes: '>=3.2' topics: - Accounts @@ -14,7 +15,15 @@ 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. -Posiblemente necesites utilizar el tema oscuro para reducir el consumo de energía en algunos dispositivos, para reducir el cansancio de los ojos cuando haya poca luz o porque prefieres cómo se ve.{% ifversion fpt or ghae-issue-4618 %} Las personas con problemas de la vista pueden beneficiarse de un tema con contraste alto, el cual contrasta los elementos de fondo y superficie aún más.{% endif %} +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 ghae-issue-4618 %} 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-issue-4619 %} Si tienes daltonismo, puedes beneficiarte de nuestros temas claro y oscuro para daltónicos. + +{% note %} + +**Nota:** Los temas para daltónicos se encuentran actualmente en un beta público. Para obtener más información o para habilitar las características del beta público, 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)". + +{% endnote %}{% endif %} {% data reusables.user_settings.access_settings %} 1. En la barra lateral de configuración de usuario, da clic en **Apariencia**. ![Pestaña de "Apariencia" en la barra lateral de configuración de usuario](/assets/images/help/settings/appearance-tab.png) @@ -24,6 +33,8 @@ Posiblemente necesites utilizar el tema oscuro para reducir el consumo de energ {% ifversion fpt or ghae-issue-4618 %}![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 ghae-issue-4618 %}![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 ghae-issue-4619 %} + - 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 %} ## Leer más 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/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 index 1b571a3116..9baa209721 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/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 @@ -35,7 +35,7 @@ El propietario del repositorio tiene control completo del repositorio. Adicional | {% ifversion fpt %}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 %} -| Limitar las interacciones con el repositorio | "[Limitar las interacciones en tu repositorio](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)" |{% endif %}{% ifversion fpt or ghes > 3.0 %} +| Limitar las interacciones con el repositorio | "[Limitar las interacciones en tu repositorio](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)" |{% endif %}{% ifversion fpt or ghes > 3.0 or ghae-next %} | Renombrar una rama, incluyendo la rama predeterminada | "[Renombrar una rama](/github/administering-a-repository/renaming-a-branch)" {% endif %} | 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)" | @@ -54,7 +54,7 @@ El propietario del repositorio tiene control completo del repositorio. Adicional | Administrar el uso de datos para un repositorio privado | "[Administrar la configuración del uso de datos para tu repositorio privado](/github/understanding-how-github-uses-and-protects-your-data/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 | "[Archiving repositories](/repositories/archiving-a-github-repository/archiving-repositories)" |{% ifversion fpt %} +| Archivar el repositorio | "[Archivar repositorios](/repositories/archiving-a-github-repository/archiving-repositories)" |{% ifversion fpt %} | 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 %}{% ifversion fpt or ghae or ghes > 3.0 %} | 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)" | {% endif %} @@ -73,7 +73,7 @@ Los colaboradores también pueden realizar las siguientes acciones. | Acción | Más información | |:-------------------------------------------------------------------------------------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Bifurcar el repositorio | "[Acerca de las bifurcaciones](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% ifversion fpt or ghes > 3.1 %} +| Bifurcar el repositorio | "[Acerca de las bifurcaciones](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% ifversion fpt or ghes > 3.1 or ghae-next %} | 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 solilcitud de cambios](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)"
  • "[Administrar los comentarios perjudiciales](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"
| 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-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do.md index 31349832b0..d6f72159e5 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-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do.md @@ -14,7 +14,7 @@ shortTitle: Casilla de verificción de disponible para contratarse {% warning %} -Nota de obsoletización: GitHub Jobs es ahora obsoleto. La última fecha en la que se publicó un trabajo fue el 19 de mayo de 2021. The GitHub Jobs site has shut down entirely on August 19, 2021, and now redirects to the [GitHub blog post](https://github.blog/changelog/2021-04-19-deprecation-notice-github-jobs-site/) notice, which has more information on the now-completed deprecation of GitHub Jobs. +Nota de obsoletización: GitHub Jobs es ahora obsoleto. La última fecha en la que se publicó un trabajo fue el 19 de mayo de 2021. El sitio de GitHub Jobs se cerró por completo el 19 de agosto de 2021 y ahora se redirecciona a la notificación de [la publicación del blog](https://github.blog/changelog/2021-04-19-deprecation-notice-github-jobs-site/), la cual contiene más información sobre la obsoletización de GitHub Jobs que ahora se completó. {% endwarning %} diff --git a/translations/es-ES/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md b/translations/es-ES/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md index 1053763e6e..9113b07a10 100644 --- a/translations/es-ES/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md +++ b/translations/es-ES/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md @@ -15,8 +15,6 @@ topics: - Workflows --- -{% data reusables.actions.ae-beta %} - ## Acerca de almacenar en caché las dependencias de flujo de trabajo Las ejecuciones de flujo de trabajo a menudo reutilizan las mismas salidas o dependencias descargadas de una ejecución a otra. Por ejemplo, las herramientas de administración de paquetes y dependencias como Maven, Gradle, npm y Yarn mantienen una caché local de las dependencias descargadas. @@ -140,7 +138,7 @@ Para almacenar en caché los archivos en más de un directorio, necesitarás un ### Usar contextos para crear claves de caché -Una clave de caché puede incluir cualquiera de los contextos, funciones, literales y operadores admitidos por {% data variables.product.prodname_actions %}. For more information, see "[Expressions](/actions/learn-github-actions/expressions)." +Una clave de caché puede incluir cualquiera de los contextos, funciones, literales y operadores admitidos por {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Expresiones](/actions/learn-github-actions/expressions)". Usar expresiones para crear una `key` te permite crear automáticamente una nueva caché cuando las dependencias han cambiado. Por ejemplo, puedes crear una `key` utilizando una expresión que calcule el hash de un archivo `package-lock.json` de npm. diff --git a/translations/es-ES/content/actions/advanced-guides/index.md b/translations/es-ES/content/actions/advanced-guides/index.md index 3de81029ce..3372bd29fb 100644 --- a/translations/es-ES/content/actions/advanced-guides/index.md +++ b/translations/es-ES/content/actions/advanced-guides/index.md @@ -1,7 +1,7 @@ --- -title: Advanced guides -shortTitle: Advanced guides -intro: 'How to cache dependencies, store output as artifacts, and use the GitHub CLI in workflows.' +title: Guías avanzadas +shortTitle: Guías avanzadas +intro: 'Cómo guardar dependencias en caché, almacenar resultados como artefactos y utilizar el CLI de GitHub en los flujos de trabajo.' versions: fpt: '*' ghes: '*' diff --git a/translations/es-ES/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md b/translations/es-ES/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md index 5d2a291112..e929d24ab3 100644 --- a/translations/es-ES/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md +++ b/translations/es-ES/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md @@ -20,11 +20,10 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Acerca de los artefactos de flujo de trabajo -Los artefactos te permiten hacer datos persistentes después de que se complete un job y comparten estos datos con otro job en el mismo flujo de trabajo. Un artefacto es un archivo o recopilación de archivos producidos durante una ejecución de flujo de trabajo. Por ejemplo, puedes utilizar artefactos para guardar tu compilación y probar el resultado después de que haya terminado una ejecución de flujo de trabajo. +Los artefactos te permiten hacer datos persistentes después de que se complete un job y comparten estos datos con otro job en el mismo flujo de trabajo. Un artefacto es un archivo o recopilación de archivos producidos durante una ejecución de flujo de trabajo. Por ejemplo, puedes utilizar artefactos para guardar tu compilación y probar el resultado después de que haya terminado una ejecución de flujo de trabajo. {% data reusables.actions.reusable-workflow-artifacts %} {% data reusables.github-actions.artifact-log-retention-statement %} El periodo de retención para una solicitud de cambios se reinicia cada vez que alguien sube una confirmación nueva en dicha solicitud. @@ -133,7 +132,7 @@ El valor `retention-days` no puede exceder el límite de retención que configur ## Descargar o eliminar artefactos -During a workflow run, you can use the [`download-artifact`](https://github.com/actions/download-artifact) action to download artifacts that were previously uploaded in the same workflow run. +Durante una ejecución de flujo de trabajo, puedes utilizar la acción [`download-artifact`](https://github.com/actions/download-artifact) para descargar artefactos que se hayan cargado previamente en la misma ejecución de flujo de trabajo. Después de que se haya completado una ejecución de flujo de trabajo, puedes descargar o borrar los artefactos en {% data variables.product.prodname_dotcom %} o utilizando la API de REST. Para obtener más información, consulta las secciones "[Descargar los artefactos de un flujo de trabajo](/actions/managing-workflow-runs/downloading-workflow-artifacts)", "[eliminar los artefactos de un flujo de trabajo](/actions/managing-workflow-runs/removing-workflow-artifacts)", y la "[API de REST de Artefactos](/rest/reference/actions#artifacts)". diff --git a/translations/es-ES/content/actions/advanced-guides/using-github-cli-in-workflows.md b/translations/es-ES/content/actions/advanced-guides/using-github-cli-in-workflows.md index f39d711c1d..34e197b65b 100644 --- a/translations/es-ES/content/actions/advanced-guides/using-github-cli-in-workflows.md +++ b/translations/es-ES/content/actions/advanced-guides/using-github-cli-in-workflows.md @@ -1,7 +1,7 @@ --- -title: Using GitHub CLI in workflows -shortTitle: GitHub CLI in workflows -intro: 'You can script with {% data variables.product.prodname_cli %} in {% data variables.product.prodname_actions %} workflows.' +title: Utilizar el CLI de GitHub en los flujos de trabajo +shortTitle: El CLI de GitHub en los flujos de trabajo +intro: 'Puedes hacer scripts con el {% data variables.product.prodname_cli %} en los flujos de trabajo de {% data variables.product.prodname_actions %}.' redirect_from: - /actions/guides/using-github-cli-in-workflows versions: @@ -16,9 +16,9 @@ type: how_to {% data reusables.cli.cli-learn-more %} -{% data variables.product.prodname_cli %} is preinstalled on all {% data variables.product.prodname_dotcom %}-hosted runners. For each step that uses {% data variables.product.prodname_cli %}, you must set an environment variable called `GITHUB_TOKEN` to a token with the required scopes. +El {% data variables.product.prodname_cli %} está preinstalado en todos los ejecutores hospedados en {% data variables.product.prodname_dotcom %}. Para cada paso que utilice el {% data variables.product.prodname_cli %}, debes configurar una variable de ambiente llamada `GITHUB_TOKEN` para un token con los alcances requeridos. -You can execute any {% data variables.product.prodname_cli %} command. For example, this workflow uses the `gh issue comment` subcommand to add a comment when an issue is opened. +Puedes ejecutar cualquier comando del {% data variables.product.prodname_cli %}. Por ejemplo, este flujo de trabajo utiliza el subcomando `gh issue comment` para agregar un comentario cuando se abre una propuesta. ```yaml{:copy} name: Comment when opened @@ -36,7 +36,7 @@ jobs: ISSUE: {% raw %}${{ github.event.issue.html_url }}{% endraw %} ``` -You can also execute API calls through {% data variables.product.prodname_cli %}. For example, this workflow first uses the `gh api` subcommand to query the GraphQL API and parse the result. Then it stores the result in an environment variable that it can access in a later step. In the second step, it uses the `gh issue create` subcommand to create an issue containing the information from the first step. +También puedes ejecutar llamadas de la API a través de {% data variables.product.prodname_cli %}. Por ejemplo, este flujo de trabajo utiliza primero el subcomando de `gh api` para consultar la API de GraphQL y analizar el resultado. Entonces, almacenará el resultado en una variable de ambiente a la que pueda acceder en un paso posterior. En el segundo paso, utiliza el subcomando `gh issue create` para crear una propuesta que contenga la información del primer paso. ```yaml{:copy} name: Report remaining open issues diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/about-continuous-integration.md b/translations/es-ES/content/actions/automating-builds-and-tests/about-continuous-integration.md index aa59478757..cea5f10258 100644 --- a/translations/es-ES/content/actions/automating-builds-and-tests/about-continuous-integration.md +++ b/translations/es-ES/content/actions/automating-builds-and-tests/about-continuous-integration.md @@ -1,6 +1,6 @@ --- title: Acerca de la integración continua -intro: 'Puedes crear flujos de trabajo de intgraciones contínuas (IC) personalizadas y despliegues contínuos (DC) directamente en tu repositorio de {% data variables.product.prodname_dotcom %} con las {% data variables.product.prodname_actions %}.' +intro: 'You can create custom continuous integration (CI) workflows directly in your {% data variables.product.prodname_dotcom %} repository with {% data variables.product.prodname_actions %}.' product: '{% data reusables.gated-features.actions %}' redirect_from: - /articles/about-continuous-integration @@ -15,13 +15,11 @@ versions: type: overview topics: - CI - - CD shortTitle: Integración continua --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Acerca de la integración continua @@ -49,45 +47,12 @@ Adicionalmente a ayudarte a configurar los flujos de trabajo de IC para tu proye Para obtener una definición de términos comunes, consulta "[Conceptos básicos para {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/core-concepts-for-github-actions)." -## Lenguajes compatibles - +## Workflow templates {% data variables.product.product_name %} ofrece plantillas de flujo de trabajo de IC para varios lenguajes y marcos de trabajo. Busca en la lista completa de plantillas de flujo de trabajo para IC que ofrece {% data variables.product.product_name %} en el repositorio [actions/starter-workflows](https://github.com/actions/starter-workflows/tree/main/ci) de {% ifversion fpt %}{% else %} repositorio `actions/starter-workflows` en {% data variables.product.product_location %}{% endif %}. -{% ifversion fpt or ghes > 3.0 or ghae-next %} -## Saltarse las ejecuciones de código - -Si quieres prevenir temporalmente que un flujo de trabajo se active, puedes agregar una instrucción de salto en el mensaje de la confirmación. Los flujos de trabajo que comúnmente se activarían, `on: push` o `on: pull_request`, no se activarán si agregas cualquiera de las siguientes secuencias al mensaje de confirmación en una subida o a la confirmación PRINCIPAL (HEAD) de una solicitud de cambios: - -* `[skip ci]` -* `[ci skip]` -* `[no ci]` -* `[skip actions]` -* `[actions skip]` - -Como alternativa, puedes finalizar el mensaje de confirmación con dos líneas vacías seguidas de ya sea `skip-checks: true` o `skip-checks:true`. - -No podrás fusionar la solicitud de cambios si tu repositorio se cofiguró para requerir que las verificaciones específicas pasen primero. Para permitir que la solicitud de cambios se fusione, puedes subir una confirmación nueva a la solicitud de cambios sin la instrucción de salto en el mensaje de confirmación. - -{% note %} - -**Nota:** Las instrucciones de salto solo aplican para los eventos de `push` y `pull_request`. Por ejemplo, el agregar `[skip ci]` a un mensaje de confirmación no impedirá que se ejecute un flujo de trabajo que se activa con `on: pull_request_target`. - -{% endnote %} -{% endif %} - -## Notificaciones para ejecuciones de flujo de trabajo - -{% data reusables.repositories.workflow-notifications %} - -## Distintivos de estado para ejecuciones de flujos de trabajo - -{% data reusables.repositories.actions-workflow-status-badge-intro %} - -Para obtener más información, consulta la sección "[Agregar una insignia de estado de flujo de trabajo](/actions/managing-workflow-runs/adding-a-workflow-status-badge)". - ## Leer más {% ifversion fpt %} diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md index d1559df728..e28bfb3529 100644 --- a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md +++ b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md @@ -19,7 +19,6 @@ shortTitle: Crear & probar con Java & Ant {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introducción diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md index 93bb406ddd..d2fff512bc 100644 --- a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md +++ b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md @@ -19,7 +19,6 @@ shortTitle: Crear & probar con Java & Gradle {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introducción diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md index 7cd192f60c..a571a2d54f 100644 --- a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md +++ b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md @@ -19,7 +19,6 @@ shortTitle: Crear & probar en Java con Maven {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introducción diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-net.md b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-net.md index c099413827..c8885f798b 100644 --- a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-net.md +++ b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-net.md @@ -8,12 +8,11 @@ versions: fpt: '*' ghes: '*' ghae: '*' -shortTitle: Build & test .NET +shortTitle: Crear & probar .NET --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introducción 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 index 27f1d53006..2b810edb94 100644 --- 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 @@ -1,7 +1,7 @@ --- -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. +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. product: '{% data reusables.gated-features.actions %}' redirect_from: - /actions/guides/building-and-testing-nodejs-or-python @@ -14,4 +14,4 @@ topics: - CI --- - \ No newline at end of file + 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 c521f7b5e9..29ef130458 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 @@ -22,7 +22,6 @@ hasExperimentalAlternative: true {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introducción @@ -84,7 +83,7 @@ La acción `setup-node` toma una versión de Node.js como una entrada y configur La plantilla incluye una estrategia de matriz que crea y prueba tu código con cuatro versiones de Node.js: 10.x, 12.x, 14.x, y 15.x. La 'x' es un carácter comodín que coincide con el último lanzamiento menor y de parche disponible para una versión. Cada versión de Node.js especificada en la matriz `node-version` crea un trabajo que ejecuta los mismos pasos. -Cada trabajo puede acceder al valor definido en la matriz `node-version` por medio del contexto `matrix`. La acción `setup-node` utiliza el contexto como la entrada `node-version`. La acción `setup-node` configura cada trabajo con una versión diferente de Node.js antes de construir y probar código. For more information about matrix strategies and contexts, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix)" and "[Contexts](/actions/learn-github-actions/contexts)." +Cada trabajo puede acceder al valor definido en la matriz `node-version` por medio del contexto `matrix`. La acción `setup-node` utiliza el contexto como la entrada `node-version`. La acción `setup-node` configura cada trabajo con una versión diferente de Node.js antes de construir y probar código. Para obtener más información acerca de las estrategias y los contextos de la matriz, consulta las secciones "[Sintaxis de flujo de trabajo para las {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix)" y "[Contextos](/actions/learn-github-actions/contexts)". {% raw %} ```yaml{:copy} diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-powershell.md b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-powershell.md index d01e8d3cb2..eba5196d12 100644 --- a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-powershell.md +++ b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-powershell.md @@ -19,7 +19,6 @@ shortTitle: Compila & prueba PowerShell {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introducción 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 47d817863a..7ec3d0cf60 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 @@ -21,7 +21,6 @@ hasExperimentalAlternative: true {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introducción diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-ruby.md b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-ruby.md index d301a6a474..2116e73f76 100644 --- a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-ruby.md +++ b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-ruby.md @@ -12,12 +12,11 @@ type: tutorial topics: - CI - Ruby -shortTitle: Build & test Ruby +shortTitle: Crear & probar Ruby --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introducción @@ -98,7 +97,7 @@ strategy: ``` {% endraw %} -Cad versión de Ruby que se especifica en el arreglo `ruby-version` crea un job que ejecuta los mismos pasos. El contexto {% raw %}`${{ matrix.ruby-version }}`{% endraw %} se utiliza para acceder a la versión actual del job. For more information about matrix strategies and contexts, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions)" and "[Contexts](/actions/learn-github-actions/contexts)." +Cad versión de Ruby que se especifica en el arreglo `ruby-version` crea un job que ejecuta los mismos pasos. El contexto {% raw %}`${{ matrix.ruby-version }}`{% endraw %} se utiliza para acceder a la versión actual del job. Para obtener más información acerca de las estrategias y los contextos de la matriz, consulta las secciones "[Sintaxis de flujo de trabajo para las {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions)" y "[Contextos](/actions/learn-github-actions/contexts)". El flujo de trabajo ya actualizado en su totalidad con una estrategia de matriz podría verse así: diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-swift.md b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-swift.md index 4525ba354d..55b57daaf6 100644 --- a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-swift.md +++ b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-swift.md @@ -17,13 +17,12 @@ shortTitle: Compilar & probar en Swift {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introducción Esta guía te muestra cómo crear y probar un paquete de Swift. -{% ifversion ghae %} To build and test your Swift project on {% data variables.product.prodname_ghe_managed %}, you will need to create a custom operating system image that includes the necessary Swift dependencies. Para obtener las instrucciones de cómo asegurarte de que tu {% data variables.actions.hosted_runner %} tenga instalado el software necesario, consulta la sección "[Crear imágenes personalizadas](/actions/using-github-hosted-runners/creating-custom-images)". +{% ifversion ghae %} Para compilar y probar tu proyecto de Swift en {% data variables.product.prodname_ghe_managed %}, necesitarás crear una imagen de sistema operativo personalizada que incluya las dependencias necesarias de Swift. Para obtener las instrucciones de cómo asegurarte de que tu {% data variables.actions.hosted_runner %} tenga instalado el software necesario, consulta la sección "[Crear imágenes personalizadas](/actions/using-github-hosted-runners/creating-custom-images)". {% else %}Los ejecutores hospedados en {% data variables.product.prodname_dotcom %} tienen un caché de herramientas con software preinstalado y los ejecutores de Ubuntu y macOS incluyen las dependencias para crear paquetes de Swift. Para encontrar una lista completa de software actualizado y las versiones preinstaladas de Swift y Xcode, consulta la sección "[Acerca de los ejecutores hospedados en GitHub](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-software)".{% endif %} ## Prerrequisitos diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md index 9f0aa737ad..381bbdad5f 100644 --- a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md +++ b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md @@ -21,7 +21,6 @@ shortTitle: Compila & prueba las apps de Xamarin {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introducción 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 c133dce634..493e8a03dd 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 @@ -1,7 +1,7 @@ --- -title: Automating builds and tests -shortTitle: Build and test -intro: 'You can automatically build and test your projects with {% data variables.product.prodname_actions %}.' +title: Compilaciones automáticas y pruebas +shortTitle: Compila y prueba +intro: 'Puedes compilar y hacer pruebas automáticamente en tus proyectos con {% data variables.product.prodname_actions %}.' versions: fpt: '*' ghes: '*' diff --git a/translations/es-ES/content/actions/creating-actions/about-custom-actions.md b/translations/es-ES/content/actions/creating-actions/about-custom-actions.md index 9dfdce0977..93a711e205 100644 --- a/translations/es-ES/content/actions/creating-actions/about-custom-actions.md +++ b/translations/es-ES/content/actions/creating-actions/about-custom-actions.md @@ -1,5 +1,5 @@ --- -title: About custom actions +title: Acercad e las acciones personalizadas intro: 'Las acciones son tareas individuales que puedes combinar para crear trabajos y personalizar tu flujo de trabajo. Puedes crear tus propias acciones, o utilizar y personalizar a quellas que comparte la comunidad de {% data variables.product.prodname_dotcom %}.' product: '{% data reusables.gated-features.actions %}' redirect_from: @@ -20,9 +20,8 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -## About custom actions +## Acercad e las acciones personalizadas Puedes crear acciones por medio de a escritura de un código personalizado que interactúe con tu repositorio de la manera que desees, incluida la integración con las API de {% data variables.product.prodname_dotcom %} y cualquier API de terceros disponible públicamente. Por ejemplo, una acción puede publicar módulos npm, enviar alertas por SMS cuando se crean propuestas urgentes o implementar un código listo para producción. diff --git a/translations/es-ES/content/actions/creating-actions/creating-a-composite-action.md b/translations/es-ES/content/actions/creating-actions/creating-a-composite-action.md index a3dbe9fd06..ff640f8236 100644 --- a/translations/es-ES/content/actions/creating-actions/creating-a-composite-action.md +++ b/translations/es-ES/content/actions/creating-actions/creating-a-composite-action.md @@ -1,6 +1,6 @@ --- -title: Creating a composite action -intro: 'In this guide, you''ll learn how to build a composite action.' +title: Crear una acción compuesta +intro: 'En esta guía, aprenderás cómo crear una acción compuesta.' product: '{% data reusables.gated-features.actions %}' redirect_from: - /actions/creating-actions/creating-a-composite-run-steps-action @@ -11,18 +11,17 @@ versions: type: tutorial topics: - Action development -shortTitle: Composite action +shortTitle: Acción copuesta --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introducción -In this guide, you'll learn about the basic components needed to create and use a packaged composite action. Para centrar esta guía en los componentes necesarios para empaquetar la acción, la funcionalidad del código de la acción es mínima. La acción imprime "Hello World" y después "Goodbye", o si proporcionas un nombre personalizado, imprime "Hello [who-to-greet]" y luego "Goodbye". La acción también mapea un número aleatorio hacia la variable de salida `random-number`, y ejecuta un script denominado `goodbye.sh`. +En esta guía, aprenderás acerca de los componentes básicos necesarios para crear y usar una acción compuesta empaquetada. Para centrar esta guía en los componentes necesarios para empaquetar la acción, la funcionalidad del código de la acción es mínima. La acción imprime "Hello World" y después "Goodbye", o si proporcionas un nombre personalizado, imprime "Hello [who-to-greet]" y luego "Goodbye". La acción también mapea un número aleatorio hacia la variable de salida `random-number`, y ejecuta un script denominado `goodbye.sh`. -Once you complete this project, you should understand how to build your own composite action and test it in a workflow. +Una vez que completes este proyecto, deberías comprender cómo crear tu propia acción compuesta y probarla en un flujo de trabajo. {% data reusables.github-actions.context-injection-warning %} @@ -30,7 +29,7 @@ Once you complete this project, you should understand how to build your own comp Antes de que comiences, crearás un repositorio de {% data variables.product.product_name %}. -1. Crea un repositorio público nuevo en {% data variables.product.product_location %}. You can choose any repository name, or use the following `hello-world-composite-action` example. Puedes agregar estos archivos después de que tu proyecto se haya subido a {% data variables.product.product_name %}. Para obtener más información, consulta "[Crear un repositorio nuevo](/articles/creating-a-new-repository)". +1. Crea un repositorio público nuevo en {% data variables.product.product_location %}. Puedes elegir cualquier nombre de repositorio o utilizar el siguiente ejemplo de `hello-world-composite-action`. Puedes agregar estos archivos después de que tu proyecto se haya subido a {% data variables.product.product_name %}. Para obtener más información, consulta "[Crear un repositorio nuevo](/articles/creating-a-new-repository)". 1. Clona el repositorio en tu computadora. Para obtener más información, consulta "[Clonar un repositorio](/articles/cloning-a-repository)". @@ -40,7 +39,7 @@ Antes de que comiences, crearás un repositorio de {% data variables.product.pro cd hello-world-composite-action ``` -2. In the `hello-world-composite-action` repository, create a new file called `goodbye.sh`, and add the following example code: +2. En el repositorio `hello-world-composite-action`, crea un archivo nuevo que se llame `goodbye.sh` y agrega el siguiente código de ejemplo: ```bash echo "Goodbye" @@ -61,7 +60,7 @@ Antes de que comiences, crearás un repositorio de {% data variables.product.pro ## Crear un archivo de metadatos de una acción -1. In the `hello-world-composite-action` repository, create a new file called `action.yml` and add the following example code. For more information about this syntax, see "[`runs` for a composite actions](/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-composite-actions)". +1. En el repositorio `hello-world-composite-action`, crea un archivo nuevo que se llame `action.yml` y agrega el siguiente código de ejemplo. Para obtener más información acerca de esta sintaxis, consulta la sección de "[`runs` para una acción compuesta](/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-composite-actions)". {% raw %} **action.yml** @@ -89,9 +88,9 @@ Antes de que comiences, crearás un repositorio de {% data variables.product.pro shell: bash ``` {% endraw %} - Este archivo define la entrada `who-to-greet`, mapea el número generado aleatoriamente en la variable de salida `random-number` y ejecuta el script de `goodbye.sh`. It also tells the runner how to execute the composite action. + Este archivo define la entrada `who-to-greet`, mapea el número generado aleatoriamente en la variable de salida `random-number` y ejecuta el script de `goodbye.sh`. También le dice al ejecutor cómo ejecutar la acción compuesta. - For more information about managing outputs, see "[`outputs` for a composite action](/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-composite-actions)". + Para obtener más información acerca de cómo administrar las salidas, consulta la sección "[`outputs` para las acciones compuestas](/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-composite-actions)". Para obtener más información acerca de cómo utilizar `github.action_path`, consulta la sección "[`github context`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)". @@ -114,7 +113,7 @@ Antes de que comiences, crearás un repositorio de {% data variables.product.pro El siguiente código de flujo de trabajo utiliza la acción completada de "hello world" que hiciste previamente en "[Crear un archivo de metadatos para la acción](/actions/creating-actions/creating-a-composite-action#creating-an-action-metadata-file)". -Copy the workflow code into a `.github/workflows/main.yml` file in another repository, but replace `actions/hello-world-composite-action@v1` with the repository and tag you created. También puedes reemplazar la entrada `who-to-greet` con tu nombre. +Copia el código del flujo de trabajo en un archivo de `.github/workflows/main.yml` en otro repositorio, pero reemplaza `actions/hello-world-composite-action@v1` con el repositorio y etiqueta que creaste. También puedes reemplazar la entrada `who-to-greet` con tu nombre. {% raw %} **.github/workflows/main.yml** diff --git a/translations/es-ES/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/es-ES/content/actions/creating-actions/creating-a-docker-container-action.md index 6d11e705da..69d366fdb2 100644 --- a/translations/es-ES/content/actions/creating-actions/creating-a-docker-container-action.md +++ b/translations/es-ES/content/actions/creating-actions/creating-a-docker-container-action.md @@ -20,7 +20,6 @@ shortTitle: Acción del contenedor de Docker {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introducción diff --git a/translations/es-ES/content/actions/creating-actions/creating-a-javascript-action.md b/translations/es-ES/content/actions/creating-actions/creating-a-javascript-action.md index f46e406310..8e882f6122 100644 --- a/translations/es-ES/content/actions/creating-actions/creating-a-javascript-action.md +++ b/translations/es-ES/content/actions/creating-actions/creating-a-javascript-action.md @@ -20,7 +20,6 @@ shortTitle: Acción de JavaScript {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introducción diff --git a/translations/es-ES/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/translations/es-ES/content/actions/creating-actions/dockerfile-support-for-github-actions.md index 2f2f8e3876..01abbf3e7c 100644 --- a/translations/es-ES/content/actions/creating-actions/dockerfile-support-for-github-actions.md +++ b/translations/es-ES/content/actions/creating-actions/dockerfile-support-for-github-actions.md @@ -14,7 +14,6 @@ type: reference {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Acerca de las instrucciones de Dockerfile @@ -100,7 +99,7 @@ Error response from daemon: OCI runtime create failed: container_linux.go:348: s ### CMD -Si defines el `args` en el archivo de metadatos de la acción, éste invalidará la instrucción `CMD` especificada en el `Dockerfile`. Para obtener más información, consulta la sección "[Sintaxis de metadatos para {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#runsargs)". +Si defines el `args` en el archivo de metadatos de la acción, `args` invalidará la instrucción `CMD` especificada en el `Dockerfile`. Para obtener más información, consulta la sección "[Sintaxis de metadatos para {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#runsargs)". Si utilizas `CMD` en tu `Dockerfile`, sigue estos lineamientos: diff --git a/translations/es-ES/content/actions/creating-actions/index.md b/translations/es-ES/content/actions/creating-actions/index.md index 3626bc8817..bcb1ea3d8f 100644 --- a/translations/es-ES/content/actions/creating-actions/index.md +++ b/translations/es-ES/content/actions/creating-actions/index.md @@ -24,4 +24,3 @@ children: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} 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 153f24ffe2..9dc36414ba 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 @@ -17,13 +17,12 @@ type: reference {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Acerca de la nueva sintaxis YAML para {% data variables.product.prodname_actions %} Las acciones Docker y JavaScript requieren un archivo de metadatos. El nombre del archivo de metadatos debe ser `action.yml` o `action.yaml`. Los datos del archivo de metadatos definen las entradas, las salidas y el punto de entrada principal para tu acción. -Los archivos de metadatos de acción usan la sintaxis YAML. Si eres nuevo en YAML, puedes leer "[Aprender YAML en cinco minutos](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)." +Los archivos de metadatos de acción usan la sintaxis YAML. Si eres nuevo en YAML, puedes leer "[Aprender YAML en cinco minutos](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)". ## `name (nombre)` @@ -43,7 +42,7 @@ Los archivos de metadatos de acción usan la sintaxis YAML. Si eres nuevo en YAM ### Ejemplo -Este ejemplo configura dos entradas: numOctocats y octocatEyeColor. La entrada numOctocats no se requiere y se predeterminará a un valor de '1'. Se requiere la entrada octocatEyeColor y no tiene un valor predeterminado. Los archivos de flujo de trabajo que usan esta acción deben usar la palabra clave `with` (con) para establecer un valor de entrada para octocatEyeColor. Para obtener información sobre la sintaxis `with`, consulta "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepswith)". +Este ejemplo configura dos entradas: numOctocats y octocatEyeColor. La entrada numOctocats no se requiere y se predeterminará a un valor de '1'. Se requiere la entrada octocatEyeColor y no tiene un valor predeterminado. Los archivos de flujo de trabajo que usan esta acción deben usar la palabra clave `with` (con) para establecer un valor de entrada para octocatEyeColor. Para obtener información sobre la sintaxis `with` (con), consulta "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepswith)". ```yaml inputs: @@ -86,7 +85,7 @@ Por ejemplo, si un flujo de trabajo definió las entradas de `numOctocats` y `oc ## `outputs (salidas)` -**Opcional** Los parámetros de salida te permiten declarar datos que una acción establece. Las acciones que se ejecutan más tarde en un flujo de trabajo pueden usar el conjunto de datos de salida en acciones de ejecución anterior. Por ejemplo, si se realizó una acción además de las dos entradas (x + y = z), la acción podría dar como resultado la suma (z) para que otras acciones la usen como entrada. +**Opcional** Los parámetros de salida te permiten declarar datos que una acción establece. Las acciones que se ejecutan más tarde en un flujo de trabajo pueden usar el conjunto de datos de salida en acciones de ejecución anterior. Por ejemplo, si tuviste una acción que realizó la adición de dos entradas (x + y = z), la acción podría dar como resultado la suma (z) para que otras acciones la usen como entrada. Si no declaras una salida en tu archivo de metadatos de acción, todavía puedes configurar las salidas y utilizarlas en un flujo de trabajo. Para obtener más información acerca de la configuración de salidas en una acción, consulta "[Comandos de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions/#setting-an-output-parameter)". @@ -284,7 +283,7 @@ Te recomendamos encarecidamente que incluyas la versión de la acción que está - Usar la versión de acción principal específica te permite recibir correcciones críticas y parches de seguridad y al mismo tiempo mantener la compatibilidad. También asegura que tu flujo de trabajo aún debería funcionar. - Puede ser conveniente utilizar la rama predeterminada de una acciòn, pero si alguien lanza una versiòn principal nueva con un cambio importante, tu flujo de trabajo podrìa fallar. -Algunas acciones requieren entradas que se deben establecer usando la palabra clave [`with`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepswith) (con). Revisa el archivo README de la acción para determinar las entradas requeridas. +Algunas acciones requieren entradas que se deben establecer usando la palabra clave [`with`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepswith). Revisa el archivo README de la acción para determinar las entradas requeridas. ```yaml runs: diff --git a/translations/es-ES/content/actions/creating-actions/publishing-actions-in-github-marketplace.md b/translations/es-ES/content/actions/creating-actions/publishing-actions-in-github-marketplace.md index bf378d0e4a..5fe2718518 100644 --- a/translations/es-ES/content/actions/creating-actions/publishing-actions-in-github-marketplace.md +++ b/translations/es-ES/content/actions/creating-actions/publishing-actions-in-github-marketplace.md @@ -12,8 +12,6 @@ type: how_to shortTitle: Publicar en GitHub Marketplace --- -{% data reusables.actions.ae-beta %} - Debes aceptar los términos de servicio para publicar acciones en {% data variables.product.prodname_marketplace %}. ## Acerca de la publicación de acciones diff --git a/translations/es-ES/content/actions/creating-actions/setting-exit-codes-for-actions.md b/translations/es-ES/content/actions/creating-actions/setting-exit-codes-for-actions.md index 49274afa38..118346082d 100644 --- a/translations/es-ES/content/actions/creating-actions/setting-exit-codes-for-actions.md +++ b/translations/es-ES/content/actions/creating-actions/setting-exit-codes-for-actions.md @@ -14,7 +14,6 @@ type: how_to {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Acerca de los códigos de salida diff --git a/translations/es-ES/content/actions/deployment/about-continuous-deployment.md b/translations/es-ES/content/actions/deployment/about-continuous-deployment.md new file mode 100644 index 0000000000..3cbd61eeb7 --- /dev/null +++ b/translations/es-ES/content/actions/deployment/about-continuous-deployment.md @@ -0,0 +1,41 @@ +--- +title: About continuous deployment +intro: 'You can create custom continuous deployment (CD) workflows directly in your {% data variables.product.prodname_dotcom %} repository with {% data variables.product.prodname_actions %}.' +product: '{% data reusables.gated-features.actions %}' +versions: + fpt: '*' + ghes: '*' + ghae: '*' +type: overview +topics: + - CD +shortTitle: Continuous deployment +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +## About continuous deployment + +_Continuous deployment_ (CD) is the practice of using automation to publish and deploy software updates. As part of the typical CD process, the code is automatically built and tested before deployment. + +Continuous deployment is often coupled with continuous integration. For more information about continuous integration, see "[About continuous integration](/actions/guides/about-continuous-integration)". + +## About continuous deployment using {% data variables.product.prodname_actions %} + +You can set up a {% data variables.product.prodname_actions %} workflow to deploy your software product. To verify that your product works as expected, your workflow can build the code in your repository and run your tests before deploying. + +You can configure your CD workflow to run when a {% data variables.product.product_name %} event occurs (for example, when new code is pushed to the default branch of your repository), on a set schedule, manually, or when an external event occurs using the repository dispatch webhook. For more information about when your workflow can run, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)." + +{% data variables.product.prodname_actions %} provides features that give you more control over deployments. For example, you can use environments to require approval for a job to proceed, restrict which branches can trigger a workflow, or limit access to secrets. You can use concurrency to limit your CD pipeline to a maximum of one in-progress deployment and one pending deployment. For more information about these features, see "[Deploying with GitHub Actions](/actions/deployment/deploying-with-github-actions)" and "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." + +## Workflow templates and third party actions + +{% data reusables.actions.cd-templates-actions %} + +## Leer más + +- [Deploying with GitHub Actions](/actions/deployment/deploying-with-github-actions) +- [Using environments for deployment](/actions/deployment/using-environments-for-deployment){% ifversion fpt %} +- "[Administrar la facturación de {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)" +{% endif %} diff --git a/translations/es-ES/content/actions/deployment/deploying-to-amazon-elastic-container-service.md b/translations/es-ES/content/actions/deployment/deploying-to-amazon-elastic-container-service.md index 278c8c0497..73bc5c4d81 100644 --- a/translations/es-ES/content/actions/deployment/deploying-to-amazon-elastic-container-service.md +++ b/translations/es-ES/content/actions/deployment/deploying-to-amazon-elastic-container-service.md @@ -18,11 +18,10 @@ shortTitle: Desplegar hacia Amazon ECS {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introducción -Esta guía te explica cómo utilizar {% data variables.product.prodname_actions %} para crear una aplicación contenerizada, subirla a [Amazon Elastic Container Registry (ECR)](https://aws.amazon.com/ecr/), y desplegarla en [Amazon Elastic Container Service (ECS)](https://aws.amazon.com/ecs/). +This guide explains how to use {% data variables.product.prodname_actions %} to build a containerized application, push it to [Amazon Elastic Container Registry (ECR)](https://aws.amazon.com/ecr/), and deploy it to [Amazon Elastic Container Service (ECS)](https://aws.amazon.com/ecs/) when a release is created. En cada lanzamiento nuevo de tu repositorio de {% data variables.product.company_short %}, el flujo de trabajo de {% data variables.product.prodname_actions %} crea y sube una imagen de contenedor nueva en Amazon ECR, y luego despliega una tarea nueva de definición en Amazon ECS. @@ -66,6 +65,8 @@ Antes de que crees tu flujo de trabajo de {% data variables.product.prodname_act Consulta la documentación para cada acción que se utiliza a continuación para las políticas recomendadas de IAM para el usuario de IAM y los métodos para manejar las credenciales de las llaves de acceso. +5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %} + ## Creating the workflow Once you've completed the prerequisites, you can proceed with creating the workflow. @@ -74,6 +75,8 @@ El siguiente flujo de trabajo de ejemplo demuestra cómo construir una imagen de Asegúrate de que proporcionas tus propios valores para todas las variables en la clave `env` del flujo de trabajo. +{% data reusables.actions.delete-env-key %} + ```yaml{:copy} {% data reusables.actions.actions-not-certified-by-github-comment %} @@ -93,17 +96,11 @@ env: CONTAINER_NAME: MY_CONTAINER_NAME # set this to the name of the container in the # containerDefinitions section of your task definition -defaults: - run: - shell: bash - jobs: deploy: name: Deploy - runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae-next %} - permissions: - packages: write - contents: read{% endif %} + runs-on: ubuntu-latest + environment: production {% raw %}steps: - name: Checkout @@ -150,9 +147,10 @@ jobs: wait-for-service-stability: true{% endraw %} ``` - ## Recursos adicionales +For the original starter workflow, see [`aws.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/aws.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository. + Para obtener más información sobre los servicios que se utilizan en estos ejemplos, consulta la siguiente documentación: * "[Mejores prácticas de seguridad de IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html)" en la documentación de AWS. diff --git a/translations/es-ES/content/actions/deployment/deploying-to-azure-app-service.md b/translations/es-ES/content/actions/deployment/deploying-to-azure-app-service.md index a981862461..e422caffa9 100644 --- a/translations/es-ES/content/actions/deployment/deploying-to-azure-app-service.md +++ b/translations/es-ES/content/actions/deployment/deploying-to-azure-app-service.md @@ -18,7 +18,6 @@ shortTitle: Desplegar hacia el Servicio de Azure App {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introducción @@ -68,13 +67,19 @@ Antes de crear tu flujo de trabajo de {% data variables.product.prodname_actions En tu repositorio de {% data variables.product.prodname_dotcom %}, crea un secreto que se llame `AZURE_WEBAPP_PUBLISH_PROFILE` que tenga el contenido del perfil de publicación. Para obtener más información sobre cómo crear secretos, consulta la sección "[Secretos cifrados](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)". +4. For Linux apps, add an app setting called `WEBSITE_WEBDEPLOY_USE_SCM` and set it to true in your app. For more information, see "[Configure apps in the portal](https://docs.microsoft.com/en-us/azure/app-service/configure-common#configure-app-settings)" in the Azure documentation. + +5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %} + ## Crear un flujo de trabajo Una vez que hayas completado los prerequisitos, puedes proceder con la creación del flujo de trabajo. -El siguiente flujo de trabajo de ejemplo demuestra cómo crear, probar y desplegar el proyecto de Node.js en Azura App Service. +The following example workflow demonstrates how to build, test, and deploy the Node.js project to Azure App Service when a release is created. -Asegúrate de configurar a `AZURE_WEBAPP_NAME` en la clave `env` del flujo de trabajo con el nombre de la app web que creaste. +Asegúrate de configurar a `AZURE_WEBAPP_NAME` en la clave `env` del flujo de trabajo con el nombre de la app web que creaste. You can also change `AZURE_WEBAPP_PACKAGE_PATH` if the path to your project is not the repository root and `NODE_VERSION` if you want to use a node version other than `10.x`. + +{% data reusables.actions.delete-env-key %} ```yaml{:copy} {% data reusables.actions.actions-not-certified-by-github-comment %} @@ -92,6 +97,8 @@ jobs: build-and-deploy: name: Build and Deploy runs-on: ubuntu-latest + environment: production + steps: - uses: actions/checkout@v2 @@ -120,6 +127,7 @@ jobs: Los siguientes recursos también pueden ser útiles: -* For the original starter workflow, see [`azure.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository. +* Para encontrar el flujo de trabajo inicial original, consulta el archivo [`azure.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure.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. +* For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository. * La guía rápida de "[Crear una app web de Node.js en Azure](https://docs.microsoft.com/en-us/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). diff --git a/translations/es-ES/content/actions/deployment/deploying-to-google-kubernetes-engine.md b/translations/es-ES/content/actions/deployment/deploying-to-google-kubernetes-engine.md index bb1594f547..675d8c6d68 100644 --- a/translations/es-ES/content/actions/deployment/deploying-to-google-kubernetes-engine.md +++ b/translations/es-ES/content/actions/deployment/deploying-to-google-kubernetes-engine.md @@ -13,16 +13,15 @@ topics: - CD - Containers - Google Kubernetes Engine -shortTitle: Desplegar hacia Kubernetes (GKE) +shortTitle: Deploy to Google Kubernetes Engine --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introducción -Esta guía te explica cómo utilizar {% data variables.product.prodname_actions %} para crear una aplicación contenerizada, subirla al Registro de Contenedor de Google (GCR), y desplegarla hacia Google Kubernetes Engine (GKE). +This guide explains how to use {% data variables.product.prodname_actions %} to build a containerized application, push it to Google Container Registry (GCR), and deploy it to Google Kubernetes Engine (GKE) when a release is created. GKE es un agrupamiento administrado de Kubernetes de Google Cloud que puede hospedar tus cargas de trabajo contenerizadas en la nube o en tu propio centro de datos. Para obtener más información, consulta la página de [Google Kubernetes Engine](https://cloud.google.com/kubernetes-engine). @@ -61,7 +60,7 @@ $ gcloud services enable \ ### Configurar una cuenta de servicio y almacenar sus crendenciales -Este procedimiento demuestra cómo crear la cuenta de servicio para tu integración con GKE. Aquí se explica cómo crear la cuenta, agregarle los roles, recuperar su claves y almacenarlos como un [secreto de repositorio cifrado](/actions/reference/encrypted-secrets) cifrado en base64 con el nombre de `GKE_SA_KEY`. +Este procedimiento demuestra cómo crear la cuenta de servicio para tu integración con GKE. It explains how to create the account, add roles to it, retrieve its keys, and store them as a base64-encoded encrypted repository secret named `GKE_SA_KEY`. 1. Crea una cuenta de servicio nueva: {% raw %} @@ -91,22 +90,35 @@ Este procedimiento demuestra cómo crear la cuenta de servicio para tu integraci $ gcloud iam service-accounts keys create key.json --iam-account=$SA_EMAIL ``` {% endraw %} -1. Store the service account key as a secret named `GKE_SA_KEY`: +1. Almacena la clave de cuenta de servicio como un secreto llamado `GKE_SA_KEY`: {% raw %} ``` $ export GKE_SA_KEY=$(cat key.json | base64) ``` {% endraw %} + For more information about how to store a secret, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)." + +### Storing your project name + +Store the name of your project as a secret named `GKE_PROJECT`. For more information about how to store a secret, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)." ### (Opcional) Configurar kustomize Kustomize es una herramietna opcional que se utiliza para administrar las especificaciones YAML. Después de crear un archivo de _kustomization_, el flujo de trabajo que se muestra a continuación puede utilizarse para configurar dinámicamente los campos de la imagen y agregar el resultado a `kubectl`. Para obtener más información, consulta la sección [uso de kustomize](https://github.com/kubernetes-sigs/kustomize#usage). +### (Optional) Configure a deployment environment + +{% data reusables.actions.about-environments %} + ## Crear un flujo de trabajo Una vez que hayas completado los prerequisitos, puedes proceder con la creación del flujo de trabajo. El siguiente flujo de trabajo demuestra cómo crear una imagen de contenedor y cómo subirla a GCR. Utiliza entonces las herramientas de Kubernetes (tales como `kubectl` y `kustomize`) para extraer la imagen en el despliegue del agrupamiento. +Under the `env` key, change the value of `GKE_CLUSTER` to the name of your cluster, `GKE_ZONE` to your cluster zone, `DEPLOYMENT_NAME` to the name of your deployment, and `IMAGE` to the name of your image. + +{% data reusables.actions.delete-env-key %} + ```yaml{:copy} {% data reusables.actions.actions-not-certified-by-github-comment %} @@ -127,8 +139,9 @@ jobs: setup-build-publish-deploy: name: Setup, Build, Publish, and Deploy runs-on: ubuntu-latest - steps: + environment: production + steps: - name: Checkout uses: actions/checkout@v2 @@ -138,7 +151,8 @@ jobs: service_account_key: {% raw %}${{ secrets.GKE_SA_KEY }}{% endraw %} project_id: {% raw %}${{ secrets.GKE_PROJECT }}{% endraw %} - # Configure docker to use the gcloud command-line tool as a credential helper + # Configure Docker to use the gcloud command-line tool as a credential + # helper for authentication - run: |- gcloud --quiet auth configure-docker @@ -166,7 +180,7 @@ jobs: # Set up kustomize - name: Set up Kustomize run: |- - curl --location https://github.com/kubernetes-sigs/kustomize/releases/download/kustomize%2Fv4.2.0/kustomize_v4.2.0_linux_amd64.tar.gz | tar xz + curl -sfLo kustomize https://github.com/kubernetes-sigs/kustomize/releases/download/v3.1.0/kustomize_3.1.0_linux_amd64 chmod u+x ./kustomize # Deploy the Docker image to the GKE cluster @@ -182,7 +196,7 @@ jobs: Para obtener más información sobre las herramientas que se utilizan en estos ejemplos, consulta la siguiente documentación: -* For the full starter workflow, see the ["Build and Deploy to GKE" workflow](https://github.com/actions/starter-workflows/blob/main/deployments/google.yml). +* Para encontrar un flujo de trabajo inicial completo, consulta el [flujo de trabajo de "Crear y Desplegar hacia GKE"](https://github.com/actions/starter-workflows/blob/main/deployments/google.yml). * Para ver más flujos de trabajo iniciales y el código que los acompaña, consulta los [Flujos de trabajo de ejemplo de {% data variables.product.prodname_actions %}](https://github.com/google-github-actions/setup-gcloud/tree/master/example-workflows/) de Google. * El motor de personalización de YAML de Kubernetes: [Kustomize](https://kustomize.io/). * "[Desplegar una aplicación web contenerizada](https://cloud.google.com/kubernetes-engine/docs/tutorials/hello-app)" en la documentación de Google Kubernetes Engine. diff --git a/translations/es-ES/content/actions/deployment/deploying-with-github-actions.md b/translations/es-ES/content/actions/deployment/deploying-with-github-actions.md new file mode 100644 index 0000000000..4f3b88b9eb --- /dev/null +++ b/translations/es-ES/content/actions/deployment/deploying-with-github-actions.md @@ -0,0 +1,173 @@ +--- +title: Deploying with GitHub Actions +intro: Learn how to control deployments with features like environments and concurrency. +product: '{% data reusables.gated-features.actions %}' +versions: + fpt: '*' + ghes: '>=3.1' + ghae: '*' +type: overview +topics: + - CD +shortTitle: Deploy with GitHub Actions +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +## Introducción + +{% data variables.product.prodname_actions %} offers features that let you control deployments. Puedes: + +- 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)." + +## Prerrequisitos + +You should be familiar with the syntax for {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Aprende sobre {% 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`, `release`, and `workflow_dispatch`. + +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. +- A release is created. +- Someone manually triggers it. + +```yaml +on: + push: + branches: + - main + pull_request: + branches: + - main + release: + types: + - created + workflow_dispatch: +``` + +Para obtener más información, consulta "[Eventos que activan los flujos de trabajo](/actions/reference/events-that-trigger-workflows)". + +## Utilizar ambientes + +{% data reusables.actions.about-environments %} + +## Using concurrency + +La concurrencia se asegura de que solo un job o flujo de trabajo que utilice el mismo grupo de concurrencia se ejecute al mismo tiempo. Puedes utilizar la concurrencia para que un ambiente tenga un máximo de un despliegue en progreso y un despliegue pendiente a la vez. + +{% 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. + +{% 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. + +```yaml +name: Deployment + +concurrency: production + +on: + push: + branches: + - main + +jobs: + deployment: + runs-on: ubuntu-latest + environment: production + steps: + - name: deploy + # ...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`. + +```yaml +name: Deployment + +on: + push: + branches: + - main + +jobs: + deployment: + runs-on: ubuntu-latest + environment: production + concurrency: production + steps: + - name: deploy + # ...deployment-specific steps +``` + +You can also use `cancel-in-progress` to cancel any currently running job or workflow in the same concurrency group. + +```yaml +name: Deployment + +concurrency: + group: production + cancel-in-progress: true + +on: + push: + branches: + - main + +jobs: + deployment: + runs-on: ubuntu-latest + environment: production + steps: + - name: deploy + # ...deployment-specific steps +``` + +## Visualizar el historial de despliegues + +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)." + +## Monitoring workflow runs + +Cada ejecución de flujo de trabajo genera una gráfica en tiempo real que ilustra el progreso de la misma. 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)." + +You can also view the logs of each workflow run and the history of workflow runs. Para obtener más información, consulta la sección "[Visualizar el historial de ejecuciones de un flujo de trabajo](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)". + +## Tracking deployments through apps + +{% ifversion fpt %} +If your {% data variables.product.product_name %} personal account or organization 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)." +{% 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)." + +{% ifversion fpt or ghes %} + +## Elegir un ejecutor + +You can run your deployment workflow on {% data variables.product.product_name %}-hosted runners or on self-hosted runners. Traffic from {% data variables.product.product_name %}-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.product_name %}-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)." + +{% 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 %} + +Para obtener más información, consulta la sección "[Agregar una insignia de estado de flujo de trabajo](/actions/managing-workflow-runs/adding-a-workflow-status-badge)". + +## Pasos siguientes + +This article demonstrated features of {% data variables.product.prodname_actions %} that you can add to your deployment workflows. + +{% data reusables.actions.cd-templates-actions %} diff --git a/translations/es-ES/content/actions/deployment/index.md b/translations/es-ES/content/actions/deployment/index.md index 1f2cd36718..5233d5a13a 100644 --- a/translations/es-ES/content/actions/deployment/index.md +++ b/translations/es-ES/content/actions/deployment/index.md @@ -1,16 +1,19 @@ --- title: Despliegue shortTitle: Despliegue -intro: 'Automatically deploy projects with {% data variables.product.prodname_actions %}.' +intro: 'Despliega proyectos automáticamente con {% data variables.product.prodname_actions %}.' versions: fpt: '*' ghes: '*' ghae: '*' children: + - /about-continuous-deployment + - /deploying-with-github-actions + - /using-environments-for-deployment + - /viewing-deployment-history - /deploying-to-amazon-elastic-container-service - /deploying-to-azure-app-service - /deploying-to-google-kubernetes-engine - /installing-an-apple-certificate-on-macos-runners-for-xcode-development - - /environments --- diff --git a/translations/es-ES/content/actions/deployment/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md b/translations/es-ES/content/actions/deployment/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md index c3d9d14209..74baa03dc9 100644 --- a/translations/es-ES/content/actions/deployment/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md +++ b/translations/es-ES/content/actions/deployment/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md @@ -17,7 +17,6 @@ shortTitle: Firmar aplicaciones de Xcode {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introducción diff --git a/translations/es-ES/content/actions/deployment/using-environments-for-deployment.md b/translations/es-ES/content/actions/deployment/using-environments-for-deployment.md new file mode 100644 index 0000000000..1742576ecb --- /dev/null +++ b/translations/es-ES/content/actions/deployment/using-environments-for-deployment.md @@ -0,0 +1,126 @@ +--- +title: Using environments for deployment +shortTitle: Use environments for deployment +intro: Puedes configurr ambientes con reglas de protección y secretos. A workflow job that references an environment must follow any protection rules for the environment before running or accessing the environment's secrets. +product: '{% data reusables.gated-features.environments %}' +miniTocMaxHeadingLevel: 3 +redirect_from: + - /actions/reference/environments + - /actions/deployment/environments +versions: + fpt: '*' + ghes: '>=3.1' + ghae: '*' +--- + + +## Acerca de los ambientes + +Environments are used to describe a general deployment target like `production`, `staging`, or `development`. 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)." + +Puedes configurr ambientes con reglas de protección y secretos. Cuando un job de un flujo de trabajo referencia un ambiente, el job no comenzará hasta que todas las reglas de protección del ambiente pasen. Un job tampoco puede acceder a los secretos que se definen en un ambiente sino hasta que todas las reglas de protección de dicho ambiente pasen. + +{% ifversion fpt %} +{% note %} + +**Note:** If you don't use {% data variables.product.prodname_ghe_cloud %} and convert a repository from public to private, any configured protection rules or environment secrets will be ignored, and you will not be able to configure any environments. Si conviertes tu repositorio en público nuevamente, tendrás acceso a cualquier regla de protección y secreto de ambiente que hubieras configurado previamente. {% data reusables.enterprise.link-to-ghec-trial %} + +{% endnote %} +{% endif %} + +## Reglas de protección de ambiente + +Las reglas de protección de ambiente requieren que pasen condiciones específicas antes de que un job que referencia al ambiente pueda proceder. {% ifversion fpt or ghae-next or ghes > 3.1 %}Puedes utilizar las reglas de protección de ambiente para requerir una aprobación manual, retrasar un job, o restringir el ambiente a ramas específicas.{% else %}Puedes utilizar la protección de ambiente para requerir una aprobación manual o retrasar un job.{% endif %} + +### Revisores requeridos + +Utiliza los revisores requeridos para requerir que una persona o equipo específicos aprueben los jobs del flujo de trabajo que referencian el ambiente. Puedes listar hasta seis usuarios o equipos como revisores. Los revisores deben tener acceso de lectura en el repositorio como mínimo. Solo uno de los revisores requeridos necesita aprobar el job para que éste pueda proceder. + +Para obtener más información sobre cómo revisar jobs que referencian un ambiente con revisores requeridos, consulta la sección "[revisar los despliegues](/actions/managing-workflow-runs/reviewing-deployments)". + +### Temporizador de espera + +Utiliza un temporizador de espera para retrasar un job durante una cantidad de tiempo específica después de que el job se active inicialmente. El tiempo (en minutos) debe ser un número entero entre 0 y 43,200 (30 días). + +{% ifversion fpt or ghae-next or ghes > 3.1 %} +### Ramas de despliegue + +Utiliza ramas de despliegue para restringir las ramas que pueden hacer despliegues en el ambiente. A continuación encnotrarás las opciones para las ramas de despliegue de un ambiente: + +* **Todas las ramas**: Todas las ramas del repositorio pueden hacer despliegues en el ambiente. +* **Ramas protegidas**: Solo las ramas que tengan reglas de protección de rama habilitadas podrán hacer despliegues en el ambiente. Si no se han definido reglas de protección de ramas en ninguna de las ramas del repositorio, entonces todas las ramas podrán hacer despliegues. Para obtener más iformación acerca de las reglas de protección de rama, consulta la sección "[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches)". +* **Ramas selectas**: Solo las ramas que coincidan con tus patrones específicos de nombre podrán hacer despliegues en el ambiente. + + Por ejemplo, si especificas `releases/*` como una regla de rama de despliegue, solo aquellas ramas cuyo nombre inicie con `releases/` podrán hacer despliegues en el ambiente. (Los caracteres de comodín no coincidirán con `/`. Para hacer coincidir las ramas que inicien con `release/` y contengan una diagonal sencilla adicional utiliza `release/*/*`.) Si agregas `main` como regla de rama de despliegue, la rama que se llame `main` también podrá hacer despliegues en el ambiente. Para obtener más información sobre las opciones de sintaxis para las ramas de despliegue, consulta la [documentación de File.fnmatch de Ruby](https://ruby-doc.org/core-2.5.1/File.html#method-c-fnmatch). +{% endif %} +## Secretos de ambiente + +Los secretos que se almacenan en un ambiente sólo se encuentran disponibles para los jobs de flujo de trabajo que referencien el ambiente. Si el ambiente requiere aprobación, un job no puede acceder a secretos de ambiente hasta que uno de los revisores requeridos lo apruebe. Para obtener más información sobre los secretos, consulta la sección "[Secretos cifrados](/actions/reference/encrypted-secrets)". + +{% note %} + +**Nota:** Los flujos de trabajo que se ejecutan en ejecutores auto-hospedados no se ejecutan en un contenedor aislado, incluso si utilizan ambientes. Environment secrets should be treated with the same level of security as repository and organization secrets. Para obtener más información, consulta la sección "[Fortalecimiento de la seguridad para las GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#hardening-for-self-hosted-runners)". + +{% endnote %} + +## Crear un ambiente + +{% data reusables.github-actions.permissions-statement-environment %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.github-actions.sidebar-environment %} +{% data reusables.github-actions.new-environment %} +{% data reusables.github-actions.name-environment %} +1. Optionally, specify people or teams that must approve workflow jobs that use this environment. + 1. Select **Required reviewers**. + 1. Enter up to 6 people or teams. Solo uno de los revisores requeridos necesita aprobar el job para que éste pueda proceder. + 1. Click **Save protection rules**. +2. Optionally, specify the amount of time to wait before allowing workflow jobs that use this environment to proceed. + 1. Select **Wait timer**. + 1. Enter the number of minutes to wait. + 1. Click **Save protection rules**. +3. Optionally, specify what branches can deploy to this environment. For more information about the possible values, see "[Deployment branches](#deployment-branches)." + 1. Select the desired option in the **Deployment branches** dropdown. + 1. If you chose **Selected branches**, enter the branch name patterns that you want to allow. +4. Optionally, add environment secrets. These secrets are only available to workflow jobs that use the environment. Additionally, workflow jobs that use this environment can only access these secrets after any configured rules (for example, required reviewers) pass. Para obtener más información sobre los secretos, consulta la sección "[Secretos cifrados](/actions/reference/encrypted-secrets)". + 1. Under **Environment secrets**, click **Add Secret**. + 1. Enter the secret name. + 1. Enter the secret value. + 1. Haz clic en **Agregar secreto** (Agregar secreto). + +{% ifversion fpt or ghae-next or ghes > 3.1 %}También puedes crear y configurar ambientes a través de la API de REST. Para obtener más información, consulta las secciones de "[Ambientes](/rest/reference/repos#environments)" y "[Secretos](/rest/reference/actions#secrets)".{% endif %} + +El ejecutar un flujo de trabajo que referencie un ambiente que no existe creará un ambiente con el nombre referenciado. El ambiente recién creado no tendrá configurada ninguna regla de protección o secreto. Cualquiera que pueda editar flujos de trabajo en el repositorio podrá crear ambientes a través de un archivo de flujo de trabajo, pero solo los administradoresd e repositorio pueden configurar el ambiente. + +## Using an environment + +Cad job en un flujo de trabajo puede referenciar un solo ambiente. Cualquier regla de protección que se configure para el ambiente debe pasar antes de que un job que referencia al ambiente se envíe a un ejecutor. The job can access the environment's secrets only after the job is sent to a runner. + +Cuando un flujo de trabajo referencia un ambiente, éste aparecerá en los despliegues del repositorio. Para obtener más información acerca de visualizar los despliegues actuales y previos, consulta la sección "[Visualizar el historial de despliegues](/developers/overview/viewing-deployment-history)". + +{% data reusables.actions.environment-example %} + +## Borrar un ambiente + +{% data reusables.github-actions.permissions-statement-environment %} + +El borrar un ambiente borrará todos los secretos y reglas de protección asociadas con éste. Cualquier job que esté actualmente en espera porque depende de las reglas de protección del ambiente que se borró, fallará automáticamente. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.github-actions.sidebar-environment %} +1. Junto al ambiente que quieres borrar, haz clic en {% octicon "trash" aria-label="The trash icon" %}. +2. Da clic en **Entiendo, borra este ambiente**. + +{% ifversion fpt or ghae-next or ghes > 3.1 %}También puedes borrar los ambientes a través de la API de REST Para obtener más información, consulta la sección "[Ambientes](/rest/reference/repos#environments)".{% endif %} + +## How environments relate to deployments + +{% data reusables.actions.environment-deployment-event %} + +You can access these objects through the REST API or GraphQL API. You can also subscribe to these webhook events. For more information, see "[Repositories](/rest/reference/repos#deployments)" (REST API), "[Objects](/graphql/reference/objects#deployment)" (GraphQL API), or "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#deployment)." + +## Pasos siguientes + +{% data variables.product.prodname_actions %} provides several features for managing your deployments. For more information, see "[Deploying with GitHub Actions](/actions/deployment/deploying-with-github-actions)." diff --git a/translations/es-ES/content/actions/deployment/viewing-deployment-history.md b/translations/es-ES/content/actions/deployment/viewing-deployment-history.md new file mode 100644 index 0000000000..53fa4817c3 --- /dev/null +++ b/translations/es-ES/content/actions/deployment/viewing-deployment-history.md @@ -0,0 +1,27 @@ +--- +title: Visualizar el historial de despliegues +intro: Ver los despliegues actuales y previos de tu repositorio. +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - API +shortTitle: Ver el historial de despliegue +redirect_from: + - /developers/overview/viewing-deployment-history +--- + + +Puedes entregar despliegues a través de {% ifversion fpt or ghae or ghes > 3.0 %}{% data variables.product.prodname_actions %} y de ambientes o con {% endif %}la API de REST y apps de terceros. {% ifversion fpt or ghae ghes > 3.0 %}For more information about using environments to deploy with {% data variables.product.prodname_actions %}, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." {% endif %}Para obtener más información acerca de los despliegues con la API de REST, consulta la sección "[Repositorios](/rest/reference/repos#deployments)". + +Para ver los despliegues actuales y pasados, da clic en **Ambientes** en la página principal de tu repositorio. +{% ifversion ghae or ghes < 3.0 %} +![Ambientes](/assets/images/enterprise/2.22/environments-sidebar.png){% else %} +![Environments](/assets/images/environments-sidebar.png){% endif %} + +La página de despliegues muestra el último despliegue activo de cada ambiente para tu repositorio. If the deployment includes an environment URL, a **View deployment** button that links to the URL is shown next to the deployment. + +La bitácora de actividad muestra el historial de despliegues para tus ambientes. Predeterminadamente, solo el despliegue más reciente de un ambiente tiene un estado de `Active`; todos los despliegues previos tendrán un estado de `Inactive`. Para obtener más información sobre la inactivación automática de despliegues, consulta la sección "[Despliegues inactivos](/rest/reference/repos#inactive-deployments)". + +También puedes utilizar la API de REST para obtener información sobre los despliegues. Para obtener más información, consulta la sección "[Repositorios](/rest/reference/repos#deployments)". 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 76ec3a071a..791e60d3d5 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 @@ -14,9 +14,8 @@ type: overview {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -### Acerca de los ejecutores autoalojados +## Acerca de los ejecutores autoalojados {% data reusables.github-actions.self-hosted-runner-description %} Los ejecutores auto-hospedados pueden ser físicos, virtuales, estar en un contenedor, en los servidores del usuario, o en la nube. @@ -29,11 +28,11 @@ La máquina de tu ejecutor se conecta a{% data variables.product.product_name %} {% data reusables.github-actions.self-hosted-runner-auto-removal %} -Para obtener más información acerca de la instalación y el uso de los ejecutores auto-alojados, consulta la sección "[Agregar ejecutores auto-alojados](/github/automating-your-workflow-with-github-actions/adding-self-hosted-runners)" y "[Usar ejecutores auto-alojados en un flujo de trabajo](/github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow)". +Para obtener más información acerca de la instalación y el uso de los ejecutores autoalojados, consulta "[Agregar ejecutores autoalojados](/github/automating-your-workflow-with-github-actions/adding-self-hosted-runners)" y "[Usar ejecutores autoalojados en un flujo de trabajo](/github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow)." -### Diferencias entre ejecutores alojados en {% data variables.product.prodname_dotcom %} y autoalojados +## Diferencias entre ejecutores alojados en {% data variables.product.prodname_dotcom %} y autoalojados -Los ejecutores alojados en {% data variables.product.prodname_dotcom %} ofrecen una manera más rápida y sencilla de ejecutar tus flujos de trabajo, mientras que estos son una manera altamente configurable de ejecutar flujos de trabajo en tu propio entorno personalizado. +Los ejecutores alojados en {% data variables.product.prodname_dotcom %} ofrecen una manera más rápida y sencilla de ejecutar tus flujos de trabajo, mientras que los ejecutores autoalojados son una manera altamente configurable de ejecutar flujos de trabajo en tu propio entorno personalizado. **Ejecutores alojados en {% data variables.product.prodname_dotcom %}:** - Reciben actualizaciones automáticas para el sistema operativo, paquetes y herramientas pre-instalados, y la aplicación del ejecutor auto-hospedado. @@ -41,14 +40,14 @@ Los ejecutores alojados en {% data variables.product.prodname_dotcom %} ofrecen - Proporcionan una instancia limpia para cada ejecución de trabajo. - Usan minutos libres en tu plan de {% data variables.product.prodname_dotcom %}, con tarifas por minuto aplicadas después de superar los minutos libres. -**Ejecutores auto-hospedados:** +**Ejecutores autoalojados:** - Reciben actualizaciones automáticas únicamente para la aplicación del ejecutor auto-hospedado. Eres responsable de actualizar el sistema operativo y el resto del software. - Puedes usar los servicios en la nube o las máquinas locales que ya pagas. - Son personalizables para tu hardware, sistema operativo, software y requisitos de seguridad. - No es necesario tener una instancia limpia para cada ejecución de trabajo. - Son de uso gratuito con las {% data variables.product.prodname_actions %}, pero eres responsable del costo de mantener tus máquinas de ejecutores. -### Requisitos para máquinas de ejecutores autoalojados +## Requisitos para máquinas de ejecutores autoalojados Puedes usar cualquier máquina como ejecutor autoalojado, siempre que cumpla con estos requisitos: @@ -57,7 +56,14 @@ Puedes usar cualquier máquina como ejecutor autoalojado, siempre que cumpla con * La máquina tiene suficientes recursos de hardware para el tipo de flujos de trabajo que planeas ejecutar. La propia aplicación del ejecutor autoalojado solo requiere unos recursos mínimos. * Si quieres ejecutar flujos de trabajo que usan acciones del contenedor Docker o contenedores de servicio, debes usar una máquina Linux y Docker debe estar instalado. -### Límites de uso +{% ifversion fpt or ghes > 3.2 %} +## Autoescalar tus ejecutores auto-hospedados + +Puedes aumentar o disminuir la cantidad de ejecutores auto-hospedados automáticamente en tu ambiente como respuesta a los eventos de webhook que recibes. Para obtener más información, consulta la sección "[Autoescalar con ejecutores auto-hospedados](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)". + +{% endif %} + +## Límites de uso Hay algunos límites para el uso de las {% data variables.product.prodname_actions %} cuando se utilizan ejecutores auto-hospedados. Estos límites están sujetos a cambios. @@ -67,15 +73,15 @@ Hay algunos límites para el uso de las {% data variables.product.prodname_actio - **Matiz de jobs** - {% data reusables.github-actions.usage-matrix-limits %} {% data reusables.github-actions.usage-workflow-queue-limits %} -### Continuidad de los flujos de trabajo para los ejecutores auto-hospedados +## Continuidad de los flujos de trabajo para los ejecutores auto-hospedados {% data reusables.github-actions.runner-workflow-continuity %} -### Sistemas operativos y arquitecturas compatibles para los ejecutores auto-hospedados +## Sistemas operativos y arquitecturas compatibles para los ejecutores auto-hospedados -Los siguientes sistemas operativos son compatibles con la aplicación del ejecutor auto-hospedado. +Los siguientes sistemas operativos son compatibles con la aplicación del ejecutor autoalojado. -#### Linux +### Linux - Red Hat Enterprise Linux 7 o superior - CentOS 7 o superior @@ -87,7 +93,7 @@ Los siguientes sistemas operativos son compatibles con la aplicación del ejecut - openSUSE 15 o posterior - SUSE Enterprise Linux (SLES) 12 SP2 o posterior -#### Windows +### Windows - Windows 7 64-bit - Windows 8.1 64-bit @@ -96,11 +102,11 @@ Los siguientes sistemas operativos son compatibles con la aplicación del ejecut - Windows Server 2016 64-bit - Windows Server 2019 64-bit -#### macOS +### macOS - macOS 10.13 (High Sierra) o posterior -#### Arquitecturas +### Arquitecturas Las siguientes arquitecturas de procesamiento son compatibles para la aplicación del ejecutor auto-hospedado. @@ -108,19 +114,19 @@ Las siguientes arquitecturas de procesamiento son compatibles para la aplicació - `ARM64` - Solo Linux. - `ARM32` - Solo Linux. -{% if enterpriseServerVersions contains currentVersion %} +{% ifversion ghes %} -### La comunicación entre ejecutores autoalojados y {{ site.data.variables.product.prodname_dotcom }} +## La comunicación entre ejecutores autoalojados y {{ site.data.variables.product.prodname_dotcom }} -La máquina puede comunicarse con {% data variables.product.prodname_actions %}. Para obtener más información, consulta "[La comunicación entre ejecutores autoalojados y {% data variables.product.prodname_dotcom %}](#communication-between-self-hosted-runners-and-github)." +Podría requerirse algo de configuración adicional para utilizar acciones de {% data variables.product.prodname_dotcom_the_website %} con {% data variables.product.prodname_ghe_server %} o para utilizar las acciones de `actions/setup-LANGUAGE` con ejecutores auto-hospedados que no tengan acceso a internet. Para obtener más información, consulta "[La comunicación entre ejecutores autoalojados y {% data variables.product.prodname_dotcom %}](#communication-between-self-hosted-runners-and-github)." {% endif %} -### La comunicación entre ejecutores autoalojados y {% data variables.product.product_name %} +## La comunicación entre ejecutores autoalojados y {% data variables.product.product_name %} -El ejecutor auto-hospedado sondea a {% data variables.product.product_name %} para solicitar actualizaciones de aplicaciones y para revisar si hay jobs en cola para su procesamiento. El ejecutor auto-hospedado utiliza un _sondeo largo_ de HTTPS que abre una conexión a {% data variables.product.product_name %} por 50 segundos, y si no recibe respuesta alguna, expira y crea un nuevo sondeo largo. La aplicación debe estar ejecutándose en la máquina para aceptar y ejecutar jobs de {% data variables.product.prodname_actions %}. +El ejecutor auto-hospedado sondea a {% data variables.product.product_name %} para solicitar actualizaciones de aplicaciones y para revisar si hay jobs en cola para su procesamiento. El ejecutor auto-hospedado utiliza un _sondeo largo_ de HTTPS que abre una conexión a {% data variables.product.product_name %} por 50 segundos, y si no recibe respuesta alguna, expira y crea un nuevo sondeo largo. La aplicación debe estar ejecutándose en la máquina para aceptar y ejecutar trabajos de {% data variables.product.prodname_actions %}. -{% if currentVersion == "github-ae@latest" %} +{% ifversion ghae %} Debes asegurarte de que el ejecutor auto-hospedado tenga un acceso adecuado a la red para comunicarse con la URL de {% data variables.product.prodname_ghe_managed %}. Por ejemplo, si el nombre de tu instancia es `octoghae`, entonces necesitarás permitir que el ejecutor auto-hospedado acceda a `octoghae.github.com`. @@ -129,10 +135,16 @@ Si utilizas una lista blanca para las direcciones IP para tu cuenta empresarial u organizacional de {% data variables.product.prodname_dotcom %}, debes agregar la dirección IP de tu ejecutor auto-.hospedado a dicha lista. Para obtener más información, consulta "[Administrar las direcciones IP permitidas en tu organización](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)". {% endif %} -{% if currentVersion == "free-pro-team@latest" %} +{% ifversion fpt %} Debes asegurarte de que la máquina tiene el acceso a la red adecuado para comunicarte con las URL de {% data variables.product.prodname_dotcom %} listadas a continuación. +{% note %} + +**Nota:** Algunos de los dominios que se listan a continuación se configuraron utilizando registros de `CNAME`. Algunos cortafuegos podrían requerir que agregues reglas recursivamente apra todos los registros de `CNAME`. Nota que los registros de `CNAME` podrían cambiar en el futuro y que solo los dominios que se listan a continuación seguirán siendo constantes. + +{% endnote %} + ``` github.com api.github.com @@ -144,23 +156,26 @@ codeload.github.com pkg-cache.githubusercontent.com pkg-containers.githubusercontent.com pkg-containers-az.githubusercontent.com +*.blob.core.windows.net ``` Si utilizas un listado de direcciones IP permitidas para tu cuenta organizacional o empresarial de {% data variables.product.prodname_dotcom %}, debes agregar la dirección IP de tu ejecutor auto-hospedado a dicha lista. Para obtener más información, consulta "[Administrar las direcciones IP permitidas para tu organización](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)" o "[Hacer cumplir los parámetros de seguridad en tu cuenta de empresa](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account#using-github-actions-with-an-ip-allow-list)". {% else %} -Debes asegurarte de que la máquina tenga el acceso de red adecuado para comunicarse con {% data variables.product.product_location %}. +Debes asegurarte de que la máquina tenga el acceso a la red adecuado para comunicarse con {% data variables.product.product_location %}. {% endif %} -También puedes usar ejecutores autoalojados con un servidor proxy. Para obtener más información, consulta "[Usar un servidor proxy con ejecutores autoalojados](/actions/automating-your-workflow-with-github-actions/using-a-proxy-server-with-self-hosted-runners)." +También puedes utilizar los ejecutores auto-hospedados con un servidor proxy. Para obtener más información, consulta la sección "[Utilizar un servidor proxy con ejecutores auto-hospedados](/actions/automating-your-workflow-with-github-actions/using-a-proxy-server-with-self-hosted-runners)". -### Seguridad de ejecutores autoalojdados con repositorios públicos +## Seguridad de ejecutores autoalojdados con repositorios públicos +{% ifversion not ghae %} {% data reusables.github-actions.self-hosted-runner-security %} +{% endif %} -Este no es un problema con los ejecutores hospedados en {% data variables.product.prodname_dotcom %}, ya que cada uno de ellos siempre constituye una máquina virtual limpia y aislada, la cual se destruya al final de la ejecución del job. +Esto no es un problema con los ejecutores hospedados en {% data variables.product.prodname_dotcom %}, porque cada ejecutor hospedado en {% data variables.product.prodname_dotcom %} siempre es una máquina virtual aislada y limpia y se destruye al final de la ejecución del trabajo. Los flujos de trabajo que no son de confianza y se ejecutan en tu ejecutor autoalojado plantean riesgos de seguridad considerables para tu máquina y entorno de red, en especial si tu máquina se mantiene en su entorno entre trabajos. Algunos de los riesgos incluyen: diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md b/translations/es-ES/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md index cc0b7ada1d..880ea24245 100644 --- a/translations/es-ES/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md +++ b/translations/es-ES/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md @@ -1,5 +1,5 @@ --- -title: Agregar ejecutores autoalojados +title: Agrega ejecutores auto-hospedados intro: 'Puedes agregar un ejecutor auto-hospedado a {{ site.data.variables.product.prodname_actions }}.' redirect_from: - /github/automating-your-workflow-with-github-actions/adding-self-hosted-runners @@ -9,19 +9,20 @@ versions: ghes: '*' ghae: '*' type: tutorial +shortTitle: Agregar ejecutores auto-hospedados --- {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} Puedes agregar un ejecutor auto-hospedado a {{ site.data.variables.product.prodname_actions }}. So eres un administrador de alguna organización o empresa, podría que quisieras agregar tus ejecutores auto-hospedados a nivel organizacional o empresarial. Este acercamiento hace que el ejecutor esté disponible para múltiples repositorios en tu organización o empresa y también te permite administrar tus ejecutores en un solo lugar. -Para obtener información sobre los sistemas operativos compatibles con los ejecutores auto-hospedados o sobre el uso de ejecutores auto-hospedados con un servidor proxy, consulta "[Acerca de los ejecutores auto-hospedados](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)". +Para obtener información sobre los sistemas operativos compatibles para los ejecutores autoalojados o el uso de ejecutores autoalojados con un servidor proxy, consulta "[Acerca de los ejecutores autoalojados](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)." +{% ifversion not ghae %} {% warning %} **Advertencia:** {% data reusables.github-actions.self-hosted-runner-security %} @@ -29,55 +30,86 @@ Para obtener información sobre los sistemas operativos compatibles con los ejec Para obtener más información, consulta la sección "[Acerca de los ejecutores auto-hospedados](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)". {% endwarning %} +{% endif %} -### Agregar un ejecutor auto-hospedado a un repositorio +## Agregar un ejecutor auto-hospedado a un repositorio -Puedes agregar ejecutores auto-hospedados a un solo repositorio. Para agregar un ejecutor auto-hospedado a un repositorio de usuario, debes ser el dueño del mismo. Para los repositorios organizacionales, debes ser el propietario de la organización o tener acceso de administrador a éste. +Puedes agregar ejecutores auto-hospedados a un solo repositorio. Para agregar un ejecutor autoalojado a un repositorio de usuario, debes ser el propietario del repositorio. Para los repositorios organizacionales, debes ser el propietario de la organización o tener acceso de administrador a éste. +{% ifversion fpt %} +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.github-actions.settings-sidebar-actions %} +{% data reusables.github-actions.settings-sidebar-actions-runners-updated %} +1. Haz clic en **Ejecutor auto-hospedado nuevo**. +{% data reusables.github-actions.self-hosted-runner-configure %} +{% endif %} +{% ifversion ghae or ghes %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} 1. Debajo de -{% if currentVersion == "free-pro-team@latest" %}"Ejecutores"{% else %}"Ejecutores auto-hospedados"{% endif %}, haz clic en **Agregar ejecutor**. +{% ifversion fpt or ghes > 3.1 or ghae %}"Ejecutores"{% else %}"Ejecutores auto-hospedados"{% endif %}, haz clic en **Agregar ejecutor**. {% data reusables.github-actions.self-hosted-runner-configure %} +{% endif %} {% data reusables.github-actions.self-hosted-runner-check-installation-success %} -### Agregar un ejecutor auto-hospedado a una organización +## Agregar un ejecutor auto-hospedado a una organización Puedes agregar ejecutores auto-hospedados a nivel organizacional, en donde se podrán utilizar para procesar jobs para varios repositorios en una organización. Para agregar un ejecutor auto-hospedado a una organización, debes ser el dueño de la misma. +{% ifversion fpt %} +{% data reusables.organizations.navigate-to-org %} +{% data reusables.organizations.org_settings %} +{% data reusables.github-actions.settings-sidebar-actions %} +{% data reusables.github-actions.settings-sidebar-actions-runners-updated %} +1. Haz clic en **Ejecutor nuevo**. +{% data reusables.github-actions.self-hosted-runner-configure %} +{% endif %} +{% ifversion ghae or ghes %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} 1. Debajo de -{% if currentVersion == "free-pro-team@latest" %}"Ejecutores"{% else %}"Ejecutores auto-hospedados"{% endif %}, haz clic en **Agregar ejecutor**. +{% ifversion fpt or ghes > 3.1 or ghae %}"Ejecutores"{% else %}"Ejecutores auto-hospedados"{% endif %}, haz clic en **Agregar ejecutor**. {% data reusables.github-actions.self-hosted-runner-configure %} +{% endif %} + {% data reusables.github-actions.self-hosted-runner-check-installation-success %} {% data reusables.github-actions.self-hosted-runner-public-repo-access %} -### Agregar un ejecutor auto-hospedado a una empresa +## Agregar un ejecutor auto-hospedado a una empresa Puedes agregar ejecutores auto-hospedados a una empresa, en donde pueden asignarse a organizaciones múltiples. Los administradores de la organización podrán controlar entonces qué repositorios pueden utilizarlo. -{% if currentVersion == "free-pro-team@latest" %} +Los ejecutores nuevos se asignan al grupo predeterminado. Puedes modificar el grupo del ejecutor después de que lo hayas registrado. 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#moving-a-self-hosted-runner-to-a-group)". + +{% ifversion fpt %} Para agregar un ejecutor auto-hospedado a una cuenta empresarial, debes ser un propietario de la empresa. -{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} -Para agregar un ejecutor auto-hospedado a nivel empresarial de -{% data variables.product.product_location %}, debes ser un administrador de sitio. -{% endif %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} {% data reusables.enterprise-accounts.actions-runners-tab %} -1. Da clic en **Agregar nuevo** y luego en **Ejecutor nuevo**. Los ejecutores nuevos se asignan al grupo predeterminado. Puedes modificar el grupo del ejecutor después de que lo hayas registrado. 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#moving-a-self-hosted-runner-to-a-group)". +1. Haz clic en **Ejecutor nuevo**. {% data reusables.github-actions.self-hosted-runner-configure %} +{% endif %} +{% ifversion ghae or ghes %} +Para agregar un ejecutor auto-hospedado a nivel empresarial de +{% data variables.product.product_location %}, debes ser un administrador de sitio. +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.actions-tab %} +{% data reusables.enterprise-accounts.actions-runners-tab %} +1. Da clic en **Agregar nuevo** y luego en **Ejecutor nuevo**. +{% data reusables.github-actions.self-hosted-runner-configure %} +{% endif %} {% data reusables.github-actions.self-hosted-runner-check-installation-success %} {% data reusables.github-actions.self-hosted-runner-public-repo-access %} -#### Hacer que los ejecutores empresariales estén disponibles para los repositorios +### Hacer que los ejecutores empresariales estén disponibles para los repositorios Predeterminadamente, los ejecutores en un grupo de ejecutores auto hospedados "Predeterminado" de una empresa se encontrarán disponibles para todas las organizaciones de ésta, pero no así para todos los repositorios en cada una de las organizaciones. 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 2661f7e38f..a47232f06b 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 @@ -1,6 +1,6 @@ --- -title: Autoscaling with self-hosted runners -intro: You can automatically scale your self-hosted runners in response to webhook events. +title: Autoescalar con ejecutores auto-hospedados +intro: Puedes escalar tus ejecutores auto-hospedados automáticamente en respuesta a eventos de webhook. versions: free-pro-team: '*' enterprise-server: '>3.2' @@ -10,13 +10,12 @@ type: overview {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -## About autoscaling +## Acerca del autoescalamiento You can automatically increase or decrease the number of self-hosted runners in your environment in response to the webhook events you receive with a particular label. For example, you can create automation that adds a new self-hosted runner each time you receive a [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook event with the [`queued`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) activity, which notifies you that a new job is ready for processing. The webhook payload includes label data, so you can identify the type of runner the job is requesting. Once the job has finished, you can then create automation that removes the runner in response to the `workflow_job` [`completed`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) activity. -## Using ephemeral runners for autoscaling +## Utilizar ejecutores efímeros para autoescalar {% data variables.product.prodname_dotcom %} recommends implementing autoscaling with ephemeral self-hosted runners; autoscaling with persistent self-hosted runners is not recommended. In certain cases, {% data variables.product.prodname_dotcom %} cannot guarantee that jobs are not assigned to persistent runners while they are shut down. With ephemeral runners, this can be guaranteed because {% data variables.product.prodname_dotcom %} only assigns one job to a runner. @@ -36,22 +35,22 @@ The {% data variables.product.prodname_actions %} service will then automaticall {% endnote %} -## Using webhooks for autoscaling +## Utilizar webhooks para autoescalar You can create your own autoscaling environment by using payloads received from the [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook. This webhook is available at the repository, organization, and enterprise levels, and the payload for this event contains an `action` key that corresponds to the stages of a workflow job's life-cycle; for example when jobs are `queued`, `in_progress`, and `completed`. You must then create your own scaling automation in response to these webhook payloads. -- For more information about the `workflow_job` webhook, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job)." -- To learn how to work with webhooks, see "[Creating webhooks](/developers/webhooks-and-events/webhooks/creating-webhooks)." +- Para obtener más información sobre el webhook de `workflow_job`, consulta la sección de "[Eventos y cargas útiles de los webhooks](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job)". +- Para aprender cómo trabajar con los webhooks, consulta la sección "[Crear webhooks](/developers/webhooks-and-events/webhooks/creating-webhooks)". -## Authentication requirements +## Requisitos de autenticación You can register and delete self-hosted runners using [the API](/rest/reference/actions#self-hosted-runners). To authenticate to the API, your autoscaling implementation can use an access token or a {% data variables.product.prodname_dotcom %} app. Your access token will require the following scope: -- For private repositories, use an access token with the [`repo` scope](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes). -- For public repositories, use an access token with the [`public_repo` scope](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes). +- Para los repositorios privados, utiliza un token de acceso con el [alcance de `repo`](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes). +- Para los repositorios públicos, utiliza un token de acceso con el [alcance de `public_repo`](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes). To authenticate using a {% data variables.product.prodname_dotcom %} App, it must be assigned the following permissions: -- For repositories, assign the `administration` permission. -- for organizations, assign the `organization_self_hosted_runners` permission. +- Para los repositorios, asigna el permiso de `administration`. +- Para las organizaciones, asigna el permiso de `organization_self_hosted_runners`. diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md b/translations/es-ES/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md index d0c19ab0c1..b7a17460f5 100644 --- a/translations/es-ES/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md +++ b/translations/es-ES/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md @@ -15,7 +15,6 @@ shortTitle: Ejecutar la app del ejecutor al inicio {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% capture service_first_step %}1. Detén la aplicación del ejecutor autoalojado si se está ejecutando actualmente.{% endcapture %} {% capture service_non_windows_intro_shell %}En la máquina del ejecutor, abre un shell en el directorio en el que instalaste la aplicación del ejecutor autoalojado. Usa los comandos que se indican a continuación para instalar y administrar el servicio de ejecutor autoalojado.{% endcapture %} diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/index.md b/translations/es-ES/content/actions/hosting-your-own-runners/index.md index 42c17b14b5..d50697a7e2 100644 --- a/translations/es-ES/content/actions/hosting-your-own-runners/index.md +++ b/translations/es-ES/content/actions/hosting-your-own-runners/index.md @@ -24,4 +24,3 @@ children: {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md b/translations/es-ES/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md index 96b0a7efdf..ac95d521b5 100644 --- a/translations/es-ES/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md +++ b/translations/es-ES/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md @@ -14,7 +14,6 @@ shortTitle: Administrar grupos de ejecutores {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Acerca de los grupos de ejecutores auto-hospedados @@ -173,14 +172,13 @@ Could not find any self-hosted runner group named "rg-runnergroup". ## Mover un ejecutor auto-hospedado a un grupo Si no especificas un grupo de ejecutores durante el proceso de registro, tus ejecutores auto-hospedados nuevos se asignarán automáticamente al grupo predeterminado y después se moverán a otro grupo. -{% ifversion fpt %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} 1. En la lista de "Ejecutores", haz clic en aquél que quieras configurar. 1. Selecciona el menú desplegable del grupo de ejecutores. 1. En "Mover el ejecutor al grupo", elige un grupo destino para el ejecutor. -{% endif %} -{% ifversion ghae or ghes %} -1. En la sección de {% ifversion fpt %}"Ejecutores"{% else %}"Ejecutores auto-hospedados"{% endif %} de la página de ajustes, ubica el grupo actual del ejecutor que quieres mover y expande la lista de miembros del grupo. ![Ver los miembros de un grupo de ejecutores](/assets/images/help/settings/actions-org-runner-group-members.png) +{% else %} +1. En la sección de "Ejecutores auto-hospedados" de la página de configuración, ubica el grupo actual del ejecutor que quieres mover y expande la lista de miembros del grupo. ![Ver los miembros de un grupo de ejecutores](/assets/images/help/settings/actions-org-runner-group-members.png) 1. Selecciona la casilla junto al ejecutor auto-hospedado y da clic en **Mover a grupo** para ver los destinos disponibles. ![Mover a un miembro de un grupo de ejecutores](/assets/images/help/settings/actions-org-runner-group-member-move.png) 1. Para mover el ejecutor, da clic en el grupo de destino. ![Mover a un miembro de un grupo de ejecutores](/assets/images/help/settings/actions-org-runner-group-member-move-destination.png) {% endif %} @@ -188,14 +186,13 @@ Si no especificas un grupo de ejecutores durante el proceso de registro, tus eje Los ejecutores auto-hospedados se devuelven automáticamente al grupo predeterminado cuando su grupo se elimina. -{% ifversion fpt %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} {% data reusables.github-actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %} 1. En la lista de grupos, a la derecha del grupo que quieras borrar, haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. 1. Para eliminar el grupo, da clic en **Eliminar grupo**. 1. Revisa el mensaje de confirmación y da clic en **Eliminar este grupo de ejecutores**. -{% endif %} -{% ifversion ghae or ghes %} -1. En la sección de {% ifversion fpt %}"Ejecutores"{% else %}"Ejecutores auto-hospedados"{% endif %} de la página de ajustes, ubica el grupo que quieres borrar y haz clic en el botón de {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![Ver la configuración del grupo de ejecutores](/assets/images/help/settings/actions-org-runner-group-kebab.png) +{% else %} +1. En la sección de "Ejecutores auto-hospedados" de la página de ajustes, ubica el grupo que quieras borrar y haz clic en el botón {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![Ver la configuración del grupo de ejecutores](/assets/images/help/settings/actions-org-runner-group-kebab.png) 1. Para eliminar el grupo, da clic en **Eliminar grupo**. ![Ver la configuración del grupo de ejecutores](/assets/images/help/settings/actions-org-runner-group-remove.png) diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md b/translations/es-ES/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md index 284bd8ead9..7b6972fc5b 100644 --- a/translations/es-ES/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md +++ b/translations/es-ES/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md @@ -11,22 +11,20 @@ versions: ghae: '*' type: tutorial defaultPlatform: linux +shortTitle: Monitorear & solucionar problemas --- {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -### Comprobar el estado de un ejecutor autoalojado utilizando {{ site.data.variables.product.prodname_dotcom }} +## Comprobar el estado de un ejecutor autoalojado utilizando {{ site.data.variables.product.prodname_dotcom }} {% data reusables.github-actions.self-hosted-runner-management-permissions-required %} {% data reusables.github-actions.self-hosted-runner-navigate-repo-and-org %} -{% data reusables.organizations.settings-sidebar-actions %} -1. Debajo de "Ejecutores auto-hospedados", puedes ver una lista de ejecutores registrados, incluyendo su nombre, etiquetas y estado. - - ![Lista de ejecutores](/assets/images/help/settings/actions-runner-list.png) +{% data reusables.github-actions.settings-sidebar-actions-runners %} +1. Debajo de {% ifversion fpt or ghes > 3.1 or ghae-next %}"Ejecutores"{% else %}"Ejecutores auto-hospedados"{% endif %}, puedes ver una lista de ejecutores registrados, incluyendo el nombre, etiquetas y estado del ejecutor. El estado puede ser uno de los siguientes: @@ -35,19 +33,19 @@ defaultPlatform: linux * **Offline (Sin conexión)**: El ejecutor no está conectado a {% data variables.product.product_name %}. Esto puede deberse a que la máquina está fuera de línea, la aplicación del ejecutor autoalojado no se está ejecutando en la máquina o la aplicación del ejecutor autoalojado no se puede comunicar con {% data variables.product.product_name %}. -### Revisar los archivos de bitácora de la aplicación del ejecutor auto-hospedado +## Revisar los archivos de bitácora de la aplicación del ejecutor auto-hospedado Puedes monitorear el estado de la aplicación del ejecutor auto-hospedado y de sus actividades. Los archivos de bitácora se mantienen en el directorio `_diag`, y se genera uno nuevo cada que se inicia la aplicación. El nombre de archivo comienza con *Runner_*, y le sige una marca de tiempo UTC de cuando se inició la aplicación. Para obtener registros detallados sobre las ejecuciones de jobs en el flujo de trabajo, consulta la siguiente sección que describe los archivos *Worker_*. -### Revisar el archivo de bitácora de un job +## Revisar el archivo de bitácora de un job La aplicación del ejecutor auto-hospedado crea un archivo de bitácora detallado para cada job que procesa. Estos archivos se guardan en el directorio `_diag`, y el nombre de archivo comienza con el prefijo *Worker_*. {% linux %} -### Utilizar journalctl para revisar el servicio de la aplicación del ejecutor auto-hospedado +## Utilizar journalctl para revisar el servicio de la aplicación del ejecutor auto-hospedado Para los ejecutores auto-hospedados basados en Linux que se ejecutan en la aplicación utilizando un servicio, puedes utilizar `journalctl` para monitorear su actividad en tiempo real. El servicio predeterminado basado en systemd utiliza la siguiente convención de nomenclatura: `actions.runner.-..service`. Este nombre se trunca si excede los 80 caracteres, así que la manera preferente de encontrar el nombre de un servicio es revisando el archivo _.service_. Por ejemplo: @@ -80,7 +78,7 @@ Para ver la configuración de systemd, puedes ubicar archivo de servicio aquí: {% mac %} -### Utilizar launchd para revisar el servicio de la aplicación del ejecutor auto-hospedado +## Utilizar launchd para revisar el servicio de la aplicación del ejecutor auto-hospedado Para los ejecutores auto-hospedados basados en macOS que se ejecutan en la aplicación como un servicio, puedes utilizar `launchctl` para monitorear su actividad en tiempo real. El servicio predeterminado basado en launchd utiliza la siguiente convención de nomenclatura: `actions.runner.-.`. Este nombre se trunca si excede los 80 caracteres, así que la manera preferente de encontrar el nombre del servicio es revisando el archivo _.service_ en el directorio del ejecutor: @@ -108,7 +106,7 @@ Para ver la configuración de launchd, puedes ubicar el archivo del servicio aqu {% windows %} -### Utilizar PowerShell para revisar el servicio de la aplicación del ejecutor auto-hospedado +## Utilizar PowerShell para revisar el servicio de la aplicación del ejecutor auto-hospedado Para los ejecutores auto-hospedados basados en Windows que se ejecuten en la aplicación como servicio, puedes utilizar PowerShell para monitorear su actividad en tiempo real. El servicio utiliza la convención de nomenclatura `GitHub Actions Runner (-.)`. También puedes encontrar el nombre del servicio si revisas el archivo _.service_ en el directorio del ejecutor: @@ -145,7 +143,7 @@ PS C:\actions-runner> Get-EventLog -LogName Application -Source ActionsRunnerSer {% endwindows %} -### Monitorear el proceso de actualización automática +## Monitorear el proceso de actualización automática Te recomendamos que revises el proceso de actualización automático a menudo, ya que el ejecutor auto-hospedado no podrá procesar jobs si cae debajo de cierto umbral de versiones. La aplicación del ejecutor auto-hospedado se actualiza automáticamente, pero nota que este proceso no incluye ninguna actualización al sistema operativo ni a otro tipo de software; necesitarás administrar estas actualizaciones por separado. @@ -159,9 +157,9 @@ Adicionalmente, puedes encontrar más información en los archivos de bitácora {% linux %} -### Solucionar problemas en los contenedores de los ejecutores auto-hospedados +## Solucionar problemas en los contenedores de los ejecutores auto-hospedados -#### Revisar que se haya instalado Docker +### Revisar que se haya instalado Docker Si tus jobs necesitan contenedores, entonces el ejecutor auto-hospedado debe estar basado en Linux y necesita contar con Docker instalado. Revisa que tu ejecutor auto-hospedado tenga Docker instalado y que el servicio se esté ejecutando. @@ -180,7 +178,7 @@ Si no se ha instalado Docker, entonces las acciones dependientes fallarán con l [2020-02-13 16:56:10Z ERR StepsRunner] Caught exception from step: System.IO.FileNotFoundException: File not found: 'docker' ``` -#### Revisar los permisos de Docker +### Revisar los permisos de Docker Si tu job falla con el siguiente error: diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md b/translations/es-ES/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md index c55870dc5a..dc51ec51d2 100644 --- a/translations/es-ES/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md +++ b/translations/es-ES/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md @@ -15,7 +15,6 @@ shortTitle: Elimina ejecutores auto-hospedados {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Eliminar un ejecutor de un repositorio @@ -27,7 +26,7 @@ shortTitle: Elimina ejecutores auto-hospedados {% endnote %} -Para eliminar un ejecutor autoalojado de un repositorio de usuario, debes ser el propietario del repositorio. Para los repositorios organizacionales, debes ser el propietario de la organización o tener acceso de administrador a éste. Recomendamos que también tengas acceso a la máquina del ejecutor auto-hospedado. +Para eliminar un ejecutor autoalojado de un repositorio de usuario, debes ser el propietario del repositorio. Para los repositorios organizacionales, debes ser el propietario de la organización o tener acceso de administrador a éste. Te recomendamos que también tengas acceso a la máquina del ejecutor auto-hospedado. {% data reusables.github-actions.self-hosted-runner-reusing %} {% ifversion fpt %} @@ -54,18 +53,17 @@ Para eliminar un ejecutor autoalojado de un repositorio de usuario, debes ser el {% endnote %} -Para eliminar el ejecutor auto-hospedado de una organización, debes ser el propietario de la misma. Recomendamos que también tengas acceso a la máquina del ejecutor auto-hospedado. +Para eliminar el ejecutor auto-hospedado de una organización, debes ser el propietario de la misma. Te recomendamos que también tengas acceso a la máquina del ejecutor auto-hospedado. {% data reusables.github-actions.self-hosted-runner-reusing %} -{% ifversion fpt %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions %} {% data reusables.github-actions.settings-sidebar-actions-runners-updated %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %} -{% endif %} -{% ifversion ghae or ghes %} +{% else %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} @@ -83,17 +81,16 @@ Para eliminar el ejecutor auto-hospedado de una organización, debes ser el prop {% data reusables.github-actions.self-hosted-runner-reusing %} {% ifversion fpt %} -Para eliminar a un ejecutor auot-hospedado de una cuenta empresarial, debes ser un propietario de la empresa. Recomendamos que también tengas acceso a la máquina del ejecutor auto-hospedado. +Para eliminar a un ejecutor auot-hospedado de una cuenta empresarial, debes ser un propietario de la empresa. Te recomendamos que también tengas acceso a la máquina del ejecutor auto-hospedado. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} {% data reusables.enterprise-accounts.actions-runners-tab %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes %} Para eliminar un ejecutor auto-hospedado a nivel empresarial de -{% data variables.product.product_location %}, debes ser un administrador de sitio. Recomendamos que también tengas acceso a la máquina del ejecutor auto-hospedado. +{% data variables.product.product_location %}, debes ser un propietario de empresa. Te recomendamos que también tengas acceso a la máquina del ejecutor auto-hospedado. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md b/translations/es-ES/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md index 523e8fe4e7..eb89870a7c 100644 --- a/translations/es-ES/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md +++ b/translations/es-ES/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md @@ -14,7 +14,6 @@ shortTitle: Servidores proxy {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Configurar un servidor proxy mediante variables de entorno diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md b/translations/es-ES/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md index 2b14574dcb..c17011cf50 100644 --- a/translations/es-ES/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md +++ b/translations/es-ES/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md @@ -12,7 +12,6 @@ shortTitle: Etiquetar ejecutores {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} Para obtener información sobre cómo utilizar las etiquetas para rutear jobs a tipos específicos de ejecutores auto-hospedados, consulta la sección "[Utilizar ejecutores auto-hospedados en un flujo de trabajo](/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow)". diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md b/translations/es-ES/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md index 1291342c58..4d363e50ed 100644 --- a/translations/es-ES/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md +++ b/translations/es-ES/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md @@ -15,7 +15,6 @@ shortTitle: Utilizar ejecutores en un flujo de trabajo {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} Para obtener más información sobre cómo crear etiquetas personalizadas y predeterminadas, consulta la sección "[Utilizar etiquetas con ejecutores auto-hospedados](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)". diff --git a/translations/es-ES/content/actions/index.md b/translations/es-ES/content/actions/index.md index bacc9d1c93..351e5317a8 100644 --- a/translations/es-ES/content/actions/index.md +++ b/translations/es-ES/content/actions/index.md @@ -9,6 +9,7 @@ featuredLinks: guides: - /actions/learn-github-actions - /actions/guides/about-continuous-integration + - /actions/deployment/deploying-with-github-actions - /actions/guides/about-packaging-with-github-actions - /actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting guideCards: diff --git a/translations/es-ES/content/actions/learn-github-actions/contexts.md b/translations/es-ES/content/actions/learn-github-actions/contexts.md index 3fa515ea8e..bdfec9b424 100644 --- a/translations/es-ES/content/actions/learn-github-actions/contexts.md +++ b/translations/es-ES/content/actions/learn-github-actions/contexts.md @@ -1,7 +1,7 @@ --- title: Contextos shortTitle: Contextos -intro: You can access context information in workflows and actions. +intro: Puedes acceder a información de contexto en los flujos de trabajo y acciones. product: '{% data reusables.gated-features.actions %}' redirect_from: - /articles/contexts-and-expression-syntax-for-github-actions @@ -18,13 +18,12 @@ miniTocMaxHeadingLevel: 3 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -## About contexts +## Acerca de los contextos {% data reusables.github-actions.context-injection-warning %} -Los contextos son una manera de acceder a información acerca de las ejecuciones de flujo de trabajo, los entornos del ejecutor, los trabajos y los pasos. Los contextos usan la sintaxis de expresión. For more information, see "[Expressions](/actions/learn-github-actions/expressions)." +Los contextos son una manera de acceder a información acerca de las ejecuciones de flujo de trabajo, los entornos del ejecutor, los trabajos y los pasos. Los contextos usan la sintaxis de expresión. Para obtener más información, consulta la sección "[Expresiones](/actions/learn-github-actions/expressions)". {% raw %} `${{ }}` @@ -61,27 +60,29 @@ El contexto de `github` contiene información sobre la ejecución del flujo de t {% data reusables.github-actions.github-context-warning %} {% data reusables.github-actions.context-injection-warning %} -| Nombre de la propiedad | Type | Descripción | -| ------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `github` | `objeto` | El contexto de nivel superior disponible durante cualquier trabajo o paso en un flujo de trabajo. | -| `github.action` | `secuencia` | El nombre de la acción que se está ejecutando actualmente. {% data variables.product.prodname_dotcom %} elimina caracteres especiales o usa el nombre `run` cuando el paso actual ejecuta un script. Si usas la misma acción más de una vez en el mismo trabajo, el nombre incluirá un sufijo con el número de secuencia. Por ejemplo, el primer script que ejecutes tendrá el nombre `run1`, y el segundo script será nombrado `run2`. Del mismo modo, la segunda invocación de `actions/checkout` será `actionscheckout2`. | -| `github.action_path` | `secuencia` | La ruta en donde se ubica tu acción. Puedes utilizar esta ruta para acceder fácilmente a los archivos ubicados en el mismo repositorio que tu acción. Este atributo solo es compatible en las acciones compuestas. | -| `github.actor` | `secuencia` | El inicio de sesión del usuario que inició la ejecución del flujo de trabajo. | -| `github.base_ref` | `secuencia` | La rama `head_ref` o fuente de la solicitud de extracción en una ejecución de flujo de trabajo. Esta propiedad solo está disponible cuando el evento que activa una ejecución de flujo de trabajo es ya sea `pull_request` o `pull_request_target`. | -| `github.event` | `objeto` | La carga de webhook del evento completo. Para obtener más información, consulta "[Eventos que activan los flujos de trabajo](/articles/events-that-trigger-workflows/)". "Puedes acceder a propiedades individuales del evento que utiliza este contexto. | -| `github.event_name` | `secuencia` | El nombre del evento que activó la ejecución del flujo de trabajo. | -| `github.event_path` | `secuencia` | La ruta a la carga del webhook del evento completo en el ejecutor. | -| `github.head_ref` | `secuencia` | La rama `head_ref` o fuente de la solicitud de extracción en una ejecución de flujo de trabajo. Esta propiedad solo está disponible cuando el evento que activa una ejecución de flujo de trabajo es ya sea `pull_request` o `pull_request_target`. | -| `github.job` | `secuencia` | El [`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) del job actual. | -| `github.ref` | `secuencia` | La rama o ref de etiqueta que activó la ejecución del flujo de trabajo. Para las ramas, este es el formato `refs/heads/` y, para las etiquetas, es `refs/tags/`. | -| `github.repository` | `secuencia` | El nombre del repositorio y del propietario. Por ejemplo, `Codertocat/Hello-World`. | -| `github.repository_owner` | `secuencia` | El nombre del propietario del repositorio. Por ejemplo, `Codertocat`. | +| Nombre de la propiedad | Type | Descripción | +| ------------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `github` | `objeto` | El contexto de nivel superior disponible durante cualquier trabajo o paso en un flujo de trabajo. | +| `github.action` | `secuencia` | El nombre de la acción que se está ejecutando actualmente. {% data variables.product.prodname_dotcom %} elimina caracteres especiales o usa el nombre `__run` cuando el paso actual ejecuta un script. Si utilizas la misma acción más de una vez en el mismo job, el nombre incluirá un sufijo con el número de secuencia con un guion bajo antes de este. Por ejemplo, el primer script que ejecutes tendrá el nombre `__run`, y el segundo script será nombrado `__run_2`. Del mismo modo, la segunda invocación de `actions/checkout` será `actionscheckout2`. | +| `github.action_path` | `secuencia` | La ruta en donde se ubica tu acción. Puedes utilizar esta ruta para acceder fácilmente a los archivos ubicados en el mismo repositorio que tu acción. Este atributo solo es compatible en las acciones compuestas. | +| `github.actor` | `secuencia` | El inicio de sesión del usuario que inició la ejecución del flujo de trabajo. | +| `github.base_ref` | `secuencia` | La rama `head_ref` o fuente de la solicitud de extracción en una ejecución de flujo de trabajo. Esta propiedad solo está disponible cuando el evento que activa una ejecución de flujo de trabajo es ya sea `pull_request` o `pull_request_target`. | +| `github.event` | `objeto` | La carga de webhook del evento completo. Para obtener más información, consulta "[Eventos que activan los flujos de trabajo](/articles/events-that-trigger-workflows/)". "Puedes acceder a propiedades individuales del evento que utiliza este contexto. | +| `github.event_name` | `secuencia` | El nombre del evento que activó la ejecución del flujo de trabajo. | +| `github.event_path` | `secuencia` | La ruta a la carga del webhook del evento completo en el ejecutor. | +| `github.head_ref` | `secuencia` | La rama `head_ref` o fuente de la solicitud de extracción en una ejecución de flujo de trabajo. Esta propiedad solo está disponible cuando el evento que activa una ejecución de flujo de trabajo es ya sea `pull_request` o `pull_request_target`. | +| `github.job` | `secuencia` | El [`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) del job actual. | +| `github.ref` | `secuencia` | La rama o ref de etiqueta que activó la ejecución del flujo de trabajo. Para las ramas, este es el formato `refs/heads/` y, para las etiquetas, es `refs/tags/`. | +| `github.repository` | `secuencia` | El nombre del repositorio y del propietario. Por ejemplo, `Codertocat/Hello-World`. | +| `github.repository_owner` | `secuencia` | El nombre del propietario del repositorio. Por ejemplo, `Codertocat`. | | `github. run_id` | `secuencia` | {% data reusables.github-actions.run_id_description %} | `github. run_number` | `secuencia` | {% data reusables.github-actions.run_number_description %} -| `github.sha` | `secuencia` | El SHA de confirmación que activó la ejecución del flujo de trabajo. | -| `github.token` | `secuencia` | Un token para autenticar en nombre de la aplicación de GitHub instalada en tu repositorio. Esto es funcionalmente equivalente al secreto de `GITHUB_TOKEN`. Para más información, consulta "[Autenticando con el GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)." | -| `github.workflow` | `secuencia` | El nombre del flujo de trabajo. Si el archivo de flujo de trabajo no especifica un `nombre`, el valor de esta propiedad es la ruta completa del archivo del flujo de trabajo en el repositorio. | -| `github.workspace` | `secuencia` | El directorio de trabajo predeterminado para los pasos y la ubicación predeterminada de tu repositorio cuando usas la acción [`checkout`](https://github.com/actions/checkout). | +| `github.run_attempt` | `secuencia` | Un número único para cada intento de ejecución de un flujo de trabajo particular en un repositorio. Este número comienza en 1 para el primer intento de ejecución del flujo de trabajo e incrementa con cada re-ejecución. | +| `github.server_url` | `secuencia` | Devuelve la URL al servidor de GitHub. Por ejemplo: `https://github.com`. | +| `github.sha` | `secuencia` | El SHA de confirmación que activó la ejecución del flujo de trabajo. | +| `github.token` | `secuencia` | Un token para autenticar en nombre de la aplicación de GitHub instalada en tu repositorio. Esto es funcionalmente equivalente al secreto de `GITHUB_TOKEN`. Para más información, consulta "[Autenticando con el GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)." | +| `github.workflow` | `secuencia` | El nombre del flujo de trabajo. Si el archivo de flujo de trabajo no especifica un `nombre`, el valor de esta propiedad es la ruta completa del archivo del flujo de trabajo en el repositorio. | +| `github.workspace` | `secuencia` | El directorio de trabajo predeterminado para los pasos y la ubicación predeterminada de tu repositorio cuando usas la acción [`checkout`](https://github.com/actions/checkout). | ### contexto de `env` @@ -130,6 +131,7 @@ El contexto de `runner` contiene información sobre el ejecutor que está ejecut | Nombre de la propiedad | Type | Descripción | | ---------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `runner.name` | `secuencia` | {% data reusables.actions.runner-name-description %} | `runner.os` | `secuencia` | {% data reusables.actions.runner-os-description %} | `runner.temp` | `secuencia` | {% data reusables.actions.runner-temp-directory-description %} | `runner.tool_cache` | `secuencia` | {% ifversion ghae %}Para obtener instrucciones de cómo asegurarte de que tu {% data variables.actions.hosted_runner %} tiene instalado el software necesario, consulta la sección "[Crear imágenes personalizadas](/actions/using-github-hosted-runners/creating-custom-images)". {% else %} {% data reusables.actions.runner-tool-cache-description %} {% endif %} diff --git a/translations/es-ES/content/actions/learn-github-actions/creating-workflow-templates.md b/translations/es-ES/content/actions/learn-github-actions/creating-workflow-templates.md new file mode 100644 index 0000000000..9bd546254f --- /dev/null +++ b/translations/es-ES/content/actions/learn-github-actions/creating-workflow-templates.md @@ -0,0 +1,93 @@ +--- +title: Crear plantillas de flujo de trabajo +shortTitle: Crear plantillas +intro: Aprende cómo puedes crear plantillas de flujo de trabajo para ayudar a los integrantes de tu equipo a agregar flujos de trabajo nuevos más fácilmente. +redirect_from: + - /actions/configuring-and-managing-workflows/sharing-workflow-templates-within-your-organization +versions: + fpt: '*' + ghes: '*' + ghae: '*' +type: tutorial +topics: + - Workflows + - CI +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +## Resumen + +{% data reusables.actions.workflow-organization-templates %} + +## Crear una plantilla de flujo de trabajo + +Los usuarios con acceso de escritura en el repositorio `.github` de la organización pueden crear plantillas de flujo de trabajo. Los miembros de la organización que tengan permisos para crear flujos de trabajo podrán entonces utilizar estas plantillas. You can share workflow templates if your organization's repository is public or if the repository is private and on an Enterprise plan. + +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +{% note %} + +**Nota:** Para evitar la duplicación en los flujos de trabajo que se crean a partir de una plantilla, puedes llamar a los flujos reutilizables desde una plantilla de flujo de trabajo. Esto puede ayudar a que tus flujos de trabajo se mantengan más fácilmente. Para obtener más información, consulta la sección "[Reutilizar flujos de trabajo](/actions/learn-github-actions/reusing-workflows)". + +{% endnote %} +{% endif %} + +Este procedimiento muestra cómo crear una plantilla de flujo de trabajo y un archivo de metadatos. El archivo de metadatos describe cómo se presenta la plantilla a los usuarios cuando están creando un flujo de trabajo nuevo. + +1. En caso de que no exista previamente, crea en tu organización un repositorio público nuevo que se llame `.github`. +2. Crea un directorio que se llame `workflow-templates`. +3. Crea tu nuevo archivo de flujo de trabajo dentro del directorio `workflow-templates`. + + Si necesitas referirte a la rama predeterminada de un repositorio, puedes utilizar el marcador de posición `$default-branch`. Cuando se crea un flujo de trabajo utilizando tu plantilla, el marcador de posición se reemplazará automáticamente con el nombre de la rama predeterminada del repositorio. + + Por ejemplo, este archivo de nombre `octo-organization-ci.yml` ilustra un flujo de trabajo básico. + + ```yaml + name: Octo Organization CI + + on: + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] + + jobs: + build: + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v2 + + - name: Run a one-line script + run: echo Hello from Octo Organization + ``` +4. Crea un archivo de metadatos dentro del directorio `workflow-templates`. El archivo de metadatos debe tener el mismo nombre que el archivo de flujo de trabajo, pero en vez de tener la extensión `.yml`, este deberá encontrarse adjunto en `.properties.json`. Por ejemplo, este archivo que se llama `octo-organization-ci.properties.json` contiene los metadatos para un archivo de flujo de trabajo de nombre `octo-organization-ci.yml`: + ```yaml + { + "name": "Octo Organization Workflow", + "description": "Octo Organization CI workflow template.", + "iconName": "example-icon", + "categories": [ + "Go" + ], + "filePatterns": [ + "package.json$", + "^Dockerfile", + ".*\\.md$" + ] + } + ``` + * `name` - **Requerido.** El nombre de la plantilla de flujo de trabajo. Este se muestra en la lista de plantillas disponibles. + * `description` - **Requerido.** La descripción de la plantilla de flujo de trabajo. Este se muestra en la lista de plantillas disponibles. + * `iconName` - **Requerido.** Define un icono en la lista de plantillas para la entrada del flujo de trabajo. El `iconName` debe ser un icono en SVG del mismo nombre y se debe almacenar en el directorio `workflow-templates`. Por ejemplo, un archivo de tipo SVG que se nombre `example-icon.svg` se referenciará como `example-icon`. + * `categories` - **Opcional.** Define la categoría de lenguaje del flujo de trabajo. Cuando un usuario visualiza las plantillas disponibles, aquellas que empaten con el mismo lenguaje se presentarán con mayor prominencia. Para obtener información sobre las categorías de lenguaje disponibles, consulta https://github.com/github/linguist/blob/master/lib/linguist/languages.yml. + * `filePatterns` - **Opcional.** Permite que se utilice la plantilla si el repositorio del usuario contiene un archivo en su directorio raíz, el cual empate con una expresión regular definida. + +Para agregar otra plantilla de flujo de trabajo, agrega tus archivos al mismo directorio de `workflow-templates`. Por ejemplo: + +![Archivos de plantilla de flujo de trabajo](/assets/images/help/images/workflow-template-files.png) + +## Pasos siguientes + +Para seguir aprendiendo sobre las {% data variables.product.prodname_actions %}, consulta la sección "[Utilizar plantillas de flujo de trabajo](/actions/learn-github-actions/using-workflow-templates)". diff --git a/translations/es-ES/content/actions/learn-github-actions/environment-variables.md b/translations/es-ES/content/actions/learn-github-actions/environment-variables.md index 02cf1fe0ed..88e2d2fa85 100644 --- a/translations/es-ES/content/actions/learn-github-actions/environment-variables.md +++ b/translations/es-ES/content/actions/learn-github-actions/environment-variables.md @@ -15,7 +15,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Acerca de las variables de entorno @@ -73,6 +72,7 @@ Te recomendamos encarecidamente que las acciones usen variables de entorno para | `GITHUB_SERVER_URL` | Devuelve la URL del servidor de {% data variables.product.product_name %}. Por ejemplo: `https://{% data variables.product.product_url %}`. | | `GITHUB_API_URL` | Devuelve la URL de la API. Por ejemplo: `{% data variables.product.api_url_code %}`. | | `GITHUB_GRAPHQL_URL` | Devuelve la URL de la API de GraphQL. Por ejemplo: `{% data variables.product.graphql_url_code %}`. | +| `RUNNER_NAME` | {% data reusables.actions.runner-name-description %} | `RUNNER_OS` | {% data reusables.actions.runner-os-description %} | `RUNNER_TEMP` | {% data reusables.actions.runner-temp-directory-description %} {% ifversion not ghae %}| `RUNNER_TOOL_CACHE` | {% data reusables.actions.runner-tool-cache-description %}{% endif %} diff --git a/translations/es-ES/content/actions/learn-github-actions/essential-features-of-github-actions.md b/translations/es-ES/content/actions/learn-github-actions/essential-features-of-github-actions.md index 9b0e566d35..a310b8470e 100644 --- a/translations/es-ES/content/actions/learn-github-actions/essential-features-of-github-actions.md +++ b/translations/es-ES/content/actions/learn-github-actions/essential-features-of-github-actions.md @@ -13,7 +13,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Resumen @@ -34,7 +33,7 @@ jobs: POSTGRES_PORT: 5432 ``` -Para obtener más información, consulta "[Usar variables de entorno](/actions/configuring-and-managing-workflows/using-environment-variables)". +Para obtener más información, consulta "[Usar variables de entorno](/actions/configuring-and-managing-workflows/using-environment-variables)." ## Agregar scripts a tu flujo de trabajo @@ -62,7 +61,7 @@ Para obtener más información, consulta la sección "[Sintaxis de flujo de trab ## Compartir datos entre jobs -Si tu job genera archivos que quieras compartir con otro job en el mismo flujo de trabajo, o si quieres guardar los archivos para su referencia futura, puedes almacenarlos en {% data variables.product.prodname_dotcom %} como _artefactos_. Los artefactos son los archivos que se crean cuando desarrollas y pruebas tu código. Por ejemplo, los artefactos podrían incluir archivos binarios o de paquete, resultados de pruebas, capturas de pantalla o archivos de registro. Los artefactos se asocian con la ejecución del flujo de trabajo en donde se crearon y otro job puede utilizarlos. +Si tu job genera archivos que quieras compartir con otro job en el mismo flujo de trabajo, o si quieres guardar los archivos para su referencia futura, puedes almacenarlos en {% data variables.product.prodname_dotcom %} como _artefactos_. Los artefactos son los archivos que se crean cuando desarrollas y pruebas tu código. Por ejemplo, los artefactos podrían incluir archivos binarios o de paquete, resultados de pruebas, capturas de pantalla o archivos de registro. Los artefactos se asocian con la ejecución del flujo de trabajo en donde se crearon y otro job puede utilizarlos. {% data reusables.actions.reusable-workflow-artifacts %} Por ejemplo, puedes crear un archivo y luego subirlo como un artefacto. diff --git a/translations/es-ES/content/actions/learn-github-actions/events-that-trigger-workflows.md b/translations/es-ES/content/actions/learn-github-actions/events-that-trigger-workflows.md index 0fb45f8f55..d19ce5b505 100644 --- a/translations/es-ES/content/actions/learn-github-actions/events-that-trigger-workflows.md +++ b/translations/es-ES/content/actions/learn-github-actions/events-that-trigger-workflows.md @@ -17,7 +17,6 @@ shortTitle: Eventos que desencadenan flujos de trabajo {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Configurar los eventos del flujo de trabajo @@ -165,6 +164,26 @@ on: types: [opened, deleted] ``` +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## Eventos de reutilización de flujos de trabajo + +`workflow_call` es una palabra clave que se utiliza como el valor de `on` en un flujo de trabajo de la misma forma que un evento. Esto indica que se puede llamar a un flujo de trabajo desde otro. Para obtener más información, consulta la sección "[Reutilizar los flujos de trabajo](/actions/learn-github-actions/reusing-workflows)". + +### `workflow_call` + +| Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | +| ------------------------------------------ | ------------------ | ------------------------------------------ | ------------------------------------------ | +| El mismo que el flujo de trabajo que llama | n/a | El mismo que el flujo de trabajo que llama | El mismo que el flujo de trabajo que llama | + +#### Ejemplo + +Para que un flujo de trabajo sea reutilizable, debe incluir `workflow_call` como uno de los valores de `on`. El siguiente ejemplo solo ejecuta el flujo de trabajo cuando se le llama desde otro flujo de trabajo: + +```yaml +on: workflow_call +``` +{% endif %} + ## Eventos de webhook Puedes configurar tu flujo de trabajo para que se ejecute cuando se generen los eventos de webhook en {% data variables.product.product_name %}. Algunos eventos tienen más de un tipo de actividad que activa el evento. Si más de un tipo de actividad activa el evento, puedes especificar qué tipos de actividad activarán el flujo de trabajo para que se ejecute. Para obtener más información, consulta la sección "[webhooks](/webhooks)". diff --git a/translations/es-ES/content/actions/learn-github-actions/expressions.md b/translations/es-ES/content/actions/learn-github-actions/expressions.md index c24134b0b1..82cb1e0dd8 100644 --- a/translations/es-ES/content/actions/learn-github-actions/expressions.md +++ b/translations/es-ES/content/actions/learn-github-actions/expressions.md @@ -1,7 +1,7 @@ --- -title: Expressions -shortTitle: Expressions -intro: You can evaluate expressions in workflows and actions. +title: Expresiones +shortTitle: Expresiones +intro: Puedes evaluar las expresiones en los flujos de trabajo y acciones. product: '{% data reusables.gated-features.actions %}' versions: fpt: '*' @@ -12,11 +12,10 @@ miniTocMaxHeadingLevel: 3 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -## About expressions +## Acerca de las expresiones -Puedes usar expresiones para establecer variables programáticamente en archivos de flujo de trabajo y contextos de acceso. Una expresión puede ser cualquier combinación de valores literales, referencias a un contexto o funciones. Puedes combinar valores literales, referencias de contexto y funciones usando operadores. For more information about contexts, see "[Contexts](/actions/learn-github-actions/contexts)." +Puedes usar expresiones para establecer variables programáticamente en archivos de flujo de trabajo y contextos de acceso. Una expresión puede ser cualquier combinación de valores literales, referencias a un contexto o funciones. Puedes combinar valores literales, referencias de contexto y funciones usando operadores. Para obtener más información sobre los contextos, consulta la sección "[Contextos](/actions/learn-github-actions/contexts)". Las expresiones se utilizan comúnmente con la palabra clave condicional `if` en un archivo de flujo de trabajo para determinar si un paso debe ejecutar. Cuando un condicional `if` es `true`, se ejecutará el paso. diff --git a/translations/es-ES/content/actions/learn-github-actions/finding-and-customizing-actions.md b/translations/es-ES/content/actions/learn-github-actions/finding-and-customizing-actions.md index 562ce7bbad..c27f10987d 100644 --- a/translations/es-ES/content/actions/learn-github-actions/finding-and-customizing-actions.md +++ b/translations/es-ES/content/actions/learn-github-actions/finding-and-customizing-actions.md @@ -18,7 +18,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Resumen diff --git a/translations/es-ES/content/actions/learn-github-actions/index.md b/translations/es-ES/content/actions/learn-github-actions/index.md index 4da1495695..93da0061b5 100644 --- a/translations/es-ES/content/actions/learn-github-actions/index.md +++ b/translations/es-ES/content/actions/learn-github-actions/index.md @@ -32,8 +32,10 @@ children: - /finding-and-customizing-actions - /essential-features-of-github-actions - /managing-complex-workflows - - /sharing-workflows-with-your-organization + - /sharing-workflows-secrets-and-runners-with-your-organization + - /creating-workflow-templates - /using-workflow-templates + - /reusing-workflows - /events-that-trigger-workflows - /expressions - /contexts diff --git a/translations/es-ES/content/actions/learn-github-actions/managing-complex-workflows.md b/translations/es-ES/content/actions/learn-github-actions/managing-complex-workflows.md index 3d7df0eb28..06c5ddc770 100644 --- a/translations/es-ES/content/actions/learn-github-actions/managing-complex-workflows.md +++ b/translations/es-ES/content/actions/learn-github-actions/managing-complex-workflows.md @@ -13,11 +13,10 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Resumen -This article describes some of the advanced features of {% data variables.product.prodname_actions %} that help you create more complex workflows. +Este artículo describe algunas de las características avanzadas de las {% data variables.product.prodname_actions %} que te ayudan a crear flujos de trabajo más complejos. ## Almacenar secretos @@ -143,7 +142,7 @@ Para obtener más información, consulta la sección "[Utilizar bases de datos y ## Utilizar etiquetas para enrutar los flujos de trabajo -Esta característica te ayuda a asignar jobs a un ejecutor hospedado específico. Si quieres asegurarte de que un tipo específico de ejecutor procesará tu job, puedes utilizar etiquetas para controlar donde se ejecutan los jobs. You can assign labels to a self-hosted runner in addition to their default label of `self-hosted`. Then, you can refer to these labels in your YAML workflow, ensuring that the job is routed in a predictable way.{% ifversion not ghae %} {% data variables.product.prodname_dotcom %}-hosted runners have predefined labels assigned.{% endif %} +Esta característica te ayuda a asignar jobs a un ejecutor hospedado específico. Si quieres asegurarte de que un tipo específico de ejecutor procesará tu job, puedes utilizar etiquetas para controlar donde se ejecutan los jobs. Puedes asignar etiquetas a un ejecutor auto-hospedado adicionalmente a su etiqueta predeterminada de `self-hosted`. Entonces, puedes referirte a estas etiquetas en tu flujo de trabajo de YAML, garantizando que el job se enrute de forma predecible.{% ifversion not ghae %}Los ejecutores hospedados en {% data variables.product.prodname_dotcom %} tienen asignadas etiquetas predefinidas.{% endif %} {% ifversion ghae %} Este ejemplo muestra como un flujo de trabajo puede utilizar etiquetas para especificar el ejecutor requerido: @@ -164,16 +163,19 @@ jobs: runs-on: [self-hosted, linux, x64, gpu] ``` -A workflow will only run on a runner that has all the labels in the `runs-on` array. The job will preferentially go to an idle self-hosted runner with the specified labels. If none are available and a {% data variables.product.prodname_dotcom %}-hosted runner with the specified labels exists, the job will go to a {% data variables.product.prodname_dotcom %}-hosted runner. +Un flujo de trabajo solo se ejecutará en un ejecutor que tenga todas las etiquetas en el arreglo `runs-on`. El job irá preferencialmente a un ejecutor auto-hospedado inactivo con las etiquetas especificadas. Si no hay alguno disponible y existe un ejecutor hospedado en {% data variables.product.prodname_dotcom %} con las etiquetas especificadas, el job irá a un ejecutor hospedado en {% data variables.product.prodname_dotcom %}. -To learn more about self-hosted runner labels, see ["Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)." To learn more about -{% data variables.product.prodname_dotcom %}-hosted runner labels, see ["Supported runners and hardware resources"](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources). +Para aprender más acerca de las etiquetas auto-hospedadas, consulta la sección ["Utilizar etiquetas con los ejecutores auto-hospedados](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)". Para aprender más sobre +las etiquetas de los ejecutores hospedados en {% data variables.product.prodname_dotcom %}, consulta la sección ["Ejecutores compatibles y recursos de hardware"](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources). {% endif %} -{% ifversion fpt or ghes > 3.0 %} +{% data reusables.actions.reusable-workflows %} + +{% ifversion fpt or ghes > 3.0 or ghae-next %} + ## Utilizar ambientes -Puedes configurr ambientes con reglas de protección y secretos. Cad job en un flujo de trabajo puede referenciar un solo ambiente. Cualquier regla de protección que se configure para el ambiente debe pasar antes de que un job que referencia al ambiente se envíe a un ejecutor. Para obtener más información, consulta la sección "[Ambientes](/actions/reference/environments)". +Puedes configurr ambientes con reglas de protección y secretos. Cad job en un flujo de trabajo puede referenciar un solo ambiente. Cualquier regla de protección que se configure para el ambiente debe pasar antes de que un job que referencia al ambiente se envíe a un ejecutor. Para obtener más información, consulta la sección "[Utilizar ambientes para despliegue](/actions/deployment/using-environments-for-deployment)". {% endif %} ## Utilizar una plantilla de flujo de trabajo @@ -187,4 +189,4 @@ Puedes configurr ambientes con reglas de protección y secretos. Cad job en un f ## Pasos siguientes -Para seguir aprendiendo sobre las {% data variables.product.prodname_actions %}, consulta la sección "[Compartir flujos de trabajo con tu organización](/actions/learn-github-actions/sharing-workflows-with-your-organization)". +Para seguir aprendiendo sobre las {% data variables.product.prodname_actions %}, consulta la sección "[Compartir flujos de trabajo, secretos y ejecutores con tu organización](/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization)". diff --git a/translations/es-ES/content/actions/learn-github-actions/reusing-workflows.md b/translations/es-ES/content/actions/learn-github-actions/reusing-workflows.md new file mode 100644 index 0000000000..61ff54a845 --- /dev/null +++ b/translations/es-ES/content/actions/learn-github-actions/reusing-workflows.md @@ -0,0 +1,195 @@ +--- +title: Reutilizar flujos de trabajo +shortTitle: Reutilizar flujos de trabajo +intro: Aprende cómo evitar la duplicación al crear un flujo de trabajo reusando los flujos existentes. +miniTocMaxHeadingLevel: 3 +versions: + fpt: '*' + ghes: '>=3.4' + ghae: issue-4757 +type: how_to +topics: + - Workflows +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +{% note %} + +**Nota:** Los flujos de trabajo reutilizables se encuentran actualmente en beta y están sujetos a cambios. + +{% endnote %} + +## Resumen + +En vez de copiar y pegar desde un flujo de trabajo hacia otro, puedes hacer flujos de trabajo reutilizables. Tú y cualquiera que tenga acceso a un flujo de trabajo reutilizable pueden entonces llamarlo desde otro flujo. + +El reutilizar flujos de trabajo evita la duplicación. Esto hace que los flujos de trabajo se puedan mantener más fácilmente y te permite crear flujos de trabajo nuevos más fácilmente compilando sobre el trabajo de los demás, tal como lo haces con las acciones. La reutilización de flujos de trabajo también promueve las mejores prácticas al ayudarte a utilizar los flujos de trabajo que están bien diseñados, que ya se han probado y cuya efectividad ya se comprobó. Tu organización puede crear una librería de flujos de trabajo reutilizables que puede mantenerse centralmente. + +A un flujo de trabajo que utiliza otro flujo de trabajo se le llama flujo de trabajo "llamante". El flujo de trabajo reutilizable es un flujo "llamado". Un flujo de trabajo llamante puede utilizar varios flujos de trabajo llamados. Cada flujo de trabajo llamado se referencia en una línea simple. El resultado es que el archivo de flujo de trabajo llamante podrá contener solo unas cuantas líneas de YAML, pero podría realizar una cantidad grande de tareas cuando se ejecute. Cuando reutilizas un flujo de trabajo, se utiliza todo el flujo de trabajo llamado justo como si fuera parte del flujo de trabajo llamante. + +Si utilizas un flujo de trabajo desde un repositorio diferente, cualquier acción en el flujo de trabajo llamado se ejecutará como si fuera parte del llamante. Por ejemplo, si el flujo de trabajo llamado utiliza `actions/checkout`, la acción verifica el contenido del repositorio que hospeda el flujo de trabajo llamante y no el llamado. + +Cuando un flujo de trabajo llamante activa uno reutilizable, el contexto `github` siempre se asocia con el flujo llamante. Para obtener más información sobre el contexto `github`, consulta la sección "[Sintaxis de contexto y expresión para GitHub Actions](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)". + +## Acceso a los flujos de trabajo reutilizables + +Otros flujos de trabajo pueden usar uno reutilizable si cualquiera de los siguientes casos es cierto: + +* Ambos flujos de trabajo están en el mismo repositorio. +* El flujo de trabajo llamado se almacena en un repositorio público. +* El flujo de trabajo llamado se almacena en un repositorio interno y los ajustes de dicho repositorio permiten que se acceda a él. Para obtener más información, consulta la sección "[Administrar la configuración de {% data variables.product.prodname_actions %} en un repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#allowing-access-to-components-in-an-internal-repository)". + +## Limitaciones + +* Los flujos de trabajo reutilizables no pueden llamar a otros que también sean reutilizables. +* Los flujos de trabajo solo podrán usar a los reutilizables que se encuentren almacenados en un repositorio privado en caso de que estos también se encuentren en el mismo repositorio. +* Ninguna variable de ambiente que se configure en un contexto de `env` que se defina a nivel del flujo de trabajo en aquél llamante se propagará al flujo llamado. Para obtener más información sobre el contexto `env`, consulta la sección "[Sintaxis de contexto y expresión para GitHub Actions](/actions/reference/context-and-expression-syntax-for-github-actions#env-context)". + +Se eliminarán las siguientes limitaciones cuando la reutilización del flujo de trabajo salga del beta: +* Los flujos de trabajo reutilizables no pueden referenciar a los ejecutores auto-hospedados. +* No puedes configurar la concurrencia de un flujo de trabajo llamado desde el flujo llamante. Para obtener más información sobre `jobs..concurrency`, consulta la sección "[Sintaxis de flujo de trabajo para las GitHub Actions](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idconcurrency)". +* El flujo de trabajo llamante no puede acceder a las salidas que genera un flujo de trabajo llamado. + +## Crear un flujo de trabajo reutilizable + +Los flujos de trabajo reutilizables son archivos con formato YAML, muy similares a cualquier otro archivo de flujo de trabajo. Tal como con otros flujos de trabajo, puedes ubicar los reutilizables en el directorio `.github/workflows` de un repositorio. Los subdirectorios del directorio `workflows` no son compatibles. + +Para que un flujo de trabajo sea reutilizable, los valores de `on` deben incluir `workflow_call`: + +```yaml +on: + workflow_call: +``` + +Puedes definir entradas y secretos, las cuales pueden pasarse desde el flujo de trabajo llamante y luego utilizarse dentro del flujo llamado. El siguiente ejemplo, desde un flujo de trabajo reutilizable, define dos entradas (llamadas "ring" y "environment") y un secreto (llamado "token"): + +```yaml +on: + workflow_call: + inputs: + ring: + description: 'Identifier for the target deployment ring' + default: 'ring-0' + required: false + type: string + environment: + required: false + type: string + secrets: + token: + required: false +``` + +Para encontrar los detalles de la sintaxis para definir entradas y secretos, consulta [on.workflow_call.inputs](/actions/reference/workflow-syntax-for-github-actions#onworkflow_callinputs) y [on.workflow_call.secrets](/actions/reference/workflow-syntax-for-github-actions#onworkflow_callsecrets). + +### Flujo de trabajo reutilizable de ejemplo + +Este archivo de flujo de trabajo reutilizable llamado `workflow-B.yml` (nos referiremos a él más adelante) toma una secuencia de entrada y un secreto del flujo llamante y lo utiliza en una acción. + +{% raw %} +```yaml{:copy} +name: Reusable workflow example + +on: + workflow_call: + inputs: + username: + required: true + type: string + secrets: + token: + required: true + +jobs: + example_job: + name: Pass input and secrets to my-action + runs-on: ubuntu-latest + steps: + - uses: ./.github/actions/my-action@v1 + with: + username: ${{ inputs.username }} + token: ${{ secrets.token }} +``` +{% endraw %} + +## Llamar a un flujo de trabajo reutilizable + +Se llama a un flujo de trabajo reutilizable utilizando la palabra clave `uses`. A diferencia de cuando utilizas acciones en un flujo de trabajo, los flujos de trabajo reutilizables se llaman directamente desde un job y no dentro de los pasos de un job. + +[`jobs..uses`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_iduses) + +Se referencian los archivos de flujo de trabajo reutilizables utilizando la sintaxis: + +`{owner}/{repo}/{path}/{filename}@{ref}` + +Puedes llamar a flujos de trabajo múltiples, referenciando cada uno en un job separado. + +{% data reusables.actions.uses-keyword-example %} + +### Pasar entradas y secretos a un flujo de trabajo reutilizable + +Utiliza la palabra clave `with` para pasar entradas nombradas al flujo de trabajo llamado. Utiliza la palabra clave `secrets` para pasar los secretos nombrados. Las entradas y secretos que pases deben definirse en el flujo de trabajo llamado. Para las entradas, el tipo de datos del valor de estas debe coincidir con el tipo que se especifica para ellas en el flujo de trabajo llamado (booleano, número o secuencia). + +{% raw %} +```yaml +with: + username: mona +secrets: + token: ${{ secrets.TOKEN }} +``` +{% endraw %} + +### Palabras clave compatibles con los jobs que llaman a un flujo de trabajo reutilizable + +Cuando llamas a un flujo de trabajo reutilizable, solo puedes utilizar las siguientes palabras clave en el job que contiene la llamada: + +* [`jobs..name`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idname) +* [`jobs..uses`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_iduses) +* [`jobs..with`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idwith) +* [`jobs..with.`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idwithinput_id) +* [`jobs..secrets`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idsecrets) +* [`jobs..secrets.`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idsecretssecret_id) +* [`jobs..needs`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds) +* [`jobs..if`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idif) +* [`jobs..permissions`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idpermissions) + + {% note %} + + **Nota:** + + * Si no se especifica `jobs..permissions` en el job de llamada, el flujo de trabajo llamado tendrá los permisos predefinidos para el `GITHUB_TOKEN`. Para obtener más información, consulta la sección "[Autenticación en un flujo de trabajo](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)". + * Los permisos del `GITHUB_TOKEN` que se pasaron del flujo de trabajo llamante solo pueden bajarse de nivel (no elevarse) a través del flujo de trabajo llamado. + + {% endnote %} + +### Flujo de trabajo llamante de ejemplo + +Este archivo de flujo de trabajo llama a otros dos archivos de flujo de trabajo. Al segundo de ellos, `workflow-B.yml` (que se muestra anteriormente), se le pasó una entrada, `username`, y un secreto, `token`. + +{% raw %} +```yaml{:copy} +name: Call a reusable workflow + +on: + pull_request: + branches: + - main + +jobs: + call-workflow: + uses: octo-org/example-repo/.github/workflows/workflow-A.yml@v1 + + call-workflow-passing-data: + uses: octo-org/example-repo/.github/workflows/workflow-B.yml@main + with: + username: mona + secrets: + token: ${{ secrets.TOKEN }} +``` +{% endraw %} + +## Pasos siguientes + +Para seguir aprendiendo sobre las {% data variables.product.prodname_actions %}, consulta la sección "[Eventos que activan flujos de trabajo](/actions/learn-github-actions/events-that-trigger-workflows)". diff --git a/translations/es-ES/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md b/translations/es-ES/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md new file mode 100644 index 0000000000..7c15d3589a --- /dev/null +++ b/translations/es-ES/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md @@ -0,0 +1,53 @@ +--- +title: 'Compartir flujos de trabajo, secretos y ejecutores con tu organización' +shortTitle: Compartir flujos de trabajo con tu organización +intro: 'Aprende cómo puedes utilizar características de la organización para colaborar con tu equipo al compartir plantillas de flujos de trabajo, secretos y ejecutores auto-hospedados.' +redirect_from: + - /actions/learn-github-actions/sharing-workflows-with-your-organization +versions: + fpt: '*' + ghes: '*' + ghae: '*' +type: how_to +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +## Resumen + +Si necesitas compartir flujos de trabajo y otras características de {% data variables.product.prodname_actions %} con tu equipo, entonces considera colaborar dentrod e una organización de {% data variables.product.prodname_dotcom %}. Una organización te permite almacenar centralmente y administrar secretos, artefactos y ejecutores auto-hospedados. También puedes crear plantillas de flujo de trabajo en el repositorio de `.github` y compartirlas con otros usuarios en tu organización. + +## Utilizar plantillas de flujo de trabajo + +{% data reusables.actions.workflow-organization-templates %} Para obtener más información, consulta la sección "[Crear plantillas de flujo de trabajo](/actions/learn-github-actions/creating-workflow-templates)". + +{% data reusables.actions.reusable-workflows %} + +## Compartir secretos dentro de una organización + +Puedes admnistrar tus secretos centralmente dentro de una organización y hacerlos disponibles para repositorios específicos. Esto también significa que púedes actualizar un secreto en una ubicación y hacer que el cambio aplique a todos los flujos de trabajo del repositorio que lo utilicen. + +Cuando creas un secreto en una organización, puedes utilizar una política para limitar el acceso de los repositorios a este. Por ejemplo, puedes otorgar acceso a todos los repositorios, o limitarlo a solo los repositorios privados o a una lista específica de estos. + +{% data reusables.github-actions.permissions-statement-secrets-organization %} + +{% data reusables.organizations.navigate-to-org %} +{% data reusables.organizations.org_settings %} +{% data reusables.github-actions.sidebar-secret %} +1. Da clic en **Secreto nuevo**. +1. Teclea un nombre para tu secreto en el cuadro de entrada **Name**. +1. Ingresa el **Valor** para tu secreto. +1. Desde la lista desplegable **Acceso de los repositorios**, elige una política de acceso. +1. Haz clic en **Agregar secreto** (Agregar secreto). + +## Compartir ejecutores auto-hospedados dentro de una organización + +Los administradores de las organizaciones pueden agregar sus ejecutores auto-hospedados a grupos y luego crear políticas que controlen qué repositorios pueden acceder al grupo. + +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)". + + +## Pasos siguientes + +Para seguir aprendiendo sobre las {% data variables.product.prodname_actions %}, consulta la sección "[Crear plantillas de flujo de trabajo](/actions/learn-github-actions/creating-workflow-templates)". diff --git a/translations/es-ES/content/actions/learn-github-actions/understanding-github-actions.md b/translations/es-ES/content/actions/learn-github-actions/understanding-github-actions.md index 625bc620a3..37b5e6e165 100644 --- a/translations/es-ES/content/actions/learn-github-actions/understanding-github-actions.md +++ b/translations/es-ES/content/actions/learn-github-actions/understanding-github-actions.md @@ -1,7 +1,7 @@ --- -title: Understanding GitHub Actions -shortTitle: Understanding GitHub Actions -intro: 'Learn the basics of {% data variables.product.prodname_actions %}, including core concepts and essential terminology.' +title: Entender las GitHub Actions +shortTitle: Entendiendo las GitHub Actions +intro: 'Aprende lo básico de las {% data variables.product.prodname_actions %}, incluyendo los conceptos nucleares y la terminología esencial.' redirect_from: - /github/automating-your-workflow-with-github-actions/core-concepts-for-github-actions - /actions/automating-your-workflow-with-github-actions/core-concepts-for-github-actions @@ -18,7 +18,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Resumen @@ -36,7 +35,7 @@ A continuación, encontrarás una lista de los diferentes componentes de las {% ### Flujos de trabajo -El flujo de trabajo es un procedimiento automatizado que agregas a tu repositorio. Los flujos de trabajo se componen de uno o más jobs y pueden programarse o activarse a través de un evento. El flujo de trabajo se puede utilizar para crear, probar, empacar, lanzar o desplegar un proyecto en {% data variables.product.prodname_dotcom %}. +El flujo de trabajo es un procedimiento automatizado que agregas a tu repositorio. Los flujos de trabajo se componen de uno o más jobs y pueden programarse o activarse a través de un evento. El flujo de trabajo se puede utilizar para crear, probar, empacar, lanzar o desplegar un proyecto en {% data variables.product.prodname_dotcom %}. {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %}Puedes referenciar un flujo de trabajo dentro de otro flujo de trabajo, consulta la sección "[Reutilizar flujos de trabajo](/actions/learn-github-actions/reusing-workflows)".{% endif %} ### Eventos @@ -179,7 +178,7 @@ Para ayudarte a entender cómo se utiliza la sintaxis de YAML para crear un fluj ``` 		- This step uses the actions/setup-node@v2 action to install the specified version of the node software package on the runner, which gives you access to the npm command. + Este paso utiliza la acción actions/setup-node@v2 para instala la versión especificada del paquete de software del node en el ejecutor, lo cual te otorga acceso al comando npm.
-For more information, see "[Expressions](/actions/learn-github-actions/expressions)." +Para obtener más información, consulta la sección "[Expresiones](/actions/learn-github-actions/expressions)". ## Dependencias entre jobs 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 cf961db7e4..a08e36cc73 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 @@ -19,7 +19,6 @@ shortTitle: Migrarse desde Circle Cl {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introducción diff --git a/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md b/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md index a1dc10ae78..97dc09ba58 100644 --- a/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md +++ b/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md @@ -18,7 +18,6 @@ shortTitle: Migrarse desde GitLab IC/DC {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introducción @@ -133,7 +132,7 @@ Para obtener más información, consulta la sección "[Sintaxis de flujo de trab ## Imágenes de Docker -Tanto la IC/EC de GitLab como las {% data variables.product.prodname_actions %} son compatibles con la ejecución de jobs en una imagen de Docker. In GitLab CI/CD, Docker images are defined with an `image` key, while in {% data variables.product.prodname_actions %} it is done with the `container` key. +Tanto la IC/EC de GitLab como las {% data variables.product.prodname_actions %} son compatibles con la ejecución de jobs en una imagen de Docker. En la IC/EC de GitLab, las imágenes de Docker se definen con una clave de `image`, mientras que en las {% data variables.product.prodname_actions %} se hace con la clave `container`. Puedes encontrar un ejemplo de la sintaxis para cada sistema: @@ -212,7 +211,7 @@ jobs: -For more information, see "[Expressions](/actions/learn-github-actions/expressions)." +Para obtener más información, consulta la sección "[Expresiones](/actions/learn-github-actions/expressions)". ## Dependencias entre los Jobs diff --git a/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md b/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md index 7dcf2ae313..1d6a6d7683 100644 --- a/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md +++ b/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md @@ -19,7 +19,6 @@ shortTitle: Migrarse desde Jenkins {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introducción @@ -43,7 +42,7 @@ Para obtener más información, consulta la sección "[Conceptos esenciales para Jenkis te permite enviar compilaciones a un agente de compilación sencilla, o puedes distribuirlas a través de varios agentes. También puedes clasificar estos agentes de acuerdo con diversos atributos, tales como los tipos de sistema operativo. -De forma similar, las {% data variables.product.prodname_actions %} pueden enviar jobs a los ejecutores auto-hospedados u hospedados en {% data variables.product.prodname_dotcom %}, y puedes utilizar etiquetas para clasificar los ejecutores de acuerdo con diversos atributos. For more information, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions#runners)" and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)." +De forma similar, las {% data variables.product.prodname_actions %} pueden enviar jobs a los ejecutores auto-hospedados u hospedados en {% data variables.product.prodname_dotcom %}, y puedes utilizar etiquetas para clasificar los ejecutores de acuerdo con diversos atributos. Para obtener más información, consulta las secciones "[Entender las {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions#runners)" y "[Acerca de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)". ### Utilizar secciones para organizar mapas 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 2e7ccba1ec..932ea698cf 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 @@ -19,7 +19,6 @@ shortTitle: Migrarse desde Travis CI {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introducción @@ -205,7 +204,7 @@ 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: - - [Building and testing Node.js or Python](/actions/guides/building-and-testing-nodejs-or-python) + - [Crear y probar Node.js o Python](/actions/guides/building-and-testing-nodejs-or-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) @@ -238,7 +237,7 @@ Cuando te migras a {% data variables.product.prodname_actions %}, hay varios ace ## Sintaxis de migración para condicionales y expresiones -Para ejecutar jobs bajo expresiones condicionales, Travis CI y {% data variables.product.prodname_actions %} comparten una sintaxis condicional de tipo `if` similar. {% data variables.product.prodname_actions %} te permite utilizar la condicional `if` para prevenir que un paso o un job se ejecuten a menos de que se cumpla con la condición. For more information, see "[Expressions](/actions/learn-github-actions/expressions)." +Para ejecutar jobs bajo expresiones condicionales, Travis CI y {% data variables.product.prodname_actions %} comparten una sintaxis condicional de tipo `if` similar. {% data variables.product.prodname_actions %} te permite utilizar la condicional `if` para prevenir que un paso o un job se ejecuten a menos de que se cumpla con la condición. Para obtener más información, consulta la sección "[Expresiones](/actions/learn-github-actions/expressions)". Este ejemplo demuestra cómo una condicional de tipo `if` puede controlar si un paso se ejecuta o no: diff --git a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md index b2a3001961..9c7902e266 100644 --- a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md +++ b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md @@ -1,20 +1,19 @@ --- -title: About monitoring and troubleshooting -intro: 'You can use the tools in {% data variables.product.prodname_actions %} to monitor and debug your workflows.' +title: Acerca del monitoreo y solución de problemas +intro: 'Puedes utilizar las herramientas en las {% data variables.product.prodname_actions %} para monitorear y depurar tus flujos de trabajo.' product: '{% data reusables.gated-features.actions %}' versions: fpt: '*' ghes: '*' ghae: '*' -shortTitle: About monitoring and troubleshooting +shortTitle: Acerca de monitorear y solucionar problemas miniTocMaxHeadingLevel: 3 --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -## Monitoring your workflows +## Monitorear tus flujos de trabajo {% ifversion fpt or ghae or ghes > 3.0 %} @@ -24,7 +23,7 @@ Cada ejecución de flujo de trabajo genera una gráfica en tiempo real que ilust ![Gráfica del flujo de trabajo](/assets/images/help/images/workflow-graph.png) -For more information, see "[Using the visualization graph](/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph)." +Para obtener más información, consulta la sección "[Utilizar el gráfico de visualización](/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph)". {% endif %} @@ -37,7 +36,7 @@ Para obtener más información, consulta la sección "[Agregar una insignia de e {% ifversion fpt %} ### Visualizar el tiempo de ejecución de un job -To identify how long a job took to run, you can view its execution time. Por ejemplo: +Para identificar qué tanto tomará un job en ejecutarse, puedes ver su tiempo de ejecución. Por ejemplo: ![Enlace para los detalles de tiempo facturable y de ejecución](/assets/images/help/repository/view-run-billable-time.png) @@ -46,17 +45,17 @@ Para obtener más información, consulta la sección "[Visualizar el tiempo de e ### Visualizar el historial de ejecución del flujo de trabajo -You can view the status of each job and step in a workflow. Por ejemplo: +Puedes ver el estado de cada job y paso en un flujo de trabajo. Por ejemplo: ![Nombre de la ejecución de flujo de trabajo](/assets/images/help/repository/run-name.png) Para obtener más información, consulta la sección "[Visualizar el historial de ejecuciones de un flujo de trabajo](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)". -## Troubleshooting your workflows +## Solucionar los problemas de tus flujos de trabajo ### Utilizar bitácoras de ejecución de flujo de trabajo -Each workflow run generates activity logs that you can view, search, and download. Por ejemplo: +Cada ejecución de flujo de trabajo genera bitácoras de actividad que puedes ver, buscar y descargar. Por ejemplo: ![Resultados del flujo de trabajo de Super linter](/assets/images/help/repository/super-linter-workflow-results-updated-2.png) @@ -68,6 +67,6 @@ Si los registros de flujo de trabajo no proporcionan suficiente detalle para dia ## Monitorear y solucionar problemas para los ejecutores auto-hospedados -If you use self-hosted runners, you can view their activity and diagnose common issues. +Si utilizas ejecutores auto-hospedados, puedes ver su actividad y diagnosticar problemas comunes. Para obtener más información, consulta la sección "[Monitorear y solucionar problemas de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners)". diff --git a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md index 1d6682ec01..1e1c6850c4 100644 --- a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md +++ b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md @@ -13,7 +13,6 @@ shortTitle: Agregar una insignia de estado {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.repositories.actions-workflow-status-badge-intro %} diff --git a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md index 5b8428acf0..7e12fe5c72 100644 --- a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md +++ b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md @@ -12,7 +12,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} Estas bitácoras extra se habilitan configurando los secretos en el repositorio que contiene el flujo de trabajo, así que aplicarán los mismos requisitos de los permisos: diff --git a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/index.md b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/index.md index 3223a21b64..60be99aeb1 100644 --- a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/index.md +++ b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/index.md @@ -1,7 +1,7 @@ --- -title: Monitoring and troubleshooting workflows +title: Monitorear y solucionar los problemas de los flujos de trabajo shortTitle: Monitorear & solucionar problemas -intro: 'You can view the status and results of each step in your workflow, debug a failed workflow, search and download logs, and view billable job execution minutes.' +intro: 'Puedes ver el estado de los resultados de cada paso en tu flujo de trabajo, depurar un flujo de trabajo fallido y descargar las bitácoras y ver los minutos de ejecución facturables de los jobs.' redirect_from: - /articles/viewing-your-repository-s-workflows - /articles/viewing-your-repositorys-workflows @@ -17,9 +17,8 @@ children: - /viewing-job-execution-time - /using-workflow-run-logs - /enabling-debug-logging + - /notifications-for-workflow-runs --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% ifversion fpt or ghes > 3.0 or ghae %}{% endif %} diff --git a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md new file mode 100644 index 0000000000..18527e4ff9 --- /dev/null +++ b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md @@ -0,0 +1,15 @@ +--- +title: Notificaciones para ejecuciones de flujo de trabajo +intro: You can subscribe to notifications about workflow runs that you trigger. +product: '{% data reusables.gated-features.actions %}' +versions: + fpt: '*' + ghes: '*' + ghae: '*' +shortTitle: Notificaciones +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +{% data reusables.repositories.workflow-notifications %} diff --git a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md index c3016f16ef..0b08122813 100644 --- a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md +++ b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md @@ -13,7 +13,6 @@ shortTitle: Utiliza la gráfica de visualización {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} diff --git a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md index 6bcdc88efa..ea00070521 100644 --- a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md +++ b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md @@ -12,7 +12,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} Puedes ver si una ejecución de flujo de trabajo está en curso o completa desde la página de ejecución del flujo de trabajo. Debes haber iniciado sesión en una cuenta de {% data variables.product.prodname_dotcom %} para ver la información de ejecución del flujo de trabajo, incluyendo los casos de repositorios públicos. Para obtener más información, consulta "[Permisos de acceso en GitHub](/articles/access-permissions-on-github)". @@ -69,7 +68,7 @@ Puedes descargar los archivos de bitácora desde tu ejecución de flujo de traba {% data reusables.repositories.view-run-superlinter %} {% data reusables.repositories.navigate-to-job-superlinter %} {% ifversion fpt or ghes > 2.22 or ghae %} -1. In the upper right corner, click {% ifversion fpt or ghes > 3.0 or ghae %}{% octicon "gear" aria-label="The gear icon" %}{% else %}{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}{% endif %} and select **Download log archive**. +1. En la esquina superior derecha, haz clic en {% ifversion fpt or ghes > 3.0 or ghae %}{% octicon "gear" aria-label="The gear icon" %}{% else %}{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}{% endif %} y selecciona **Descargar archivo de bitácora**. {% ifversion fpt or ghes > 3.0 or ghae %} ![Menú desplegable para descargar registros](/assets/images/help/repository/download-logs-drop-down-updated-2.png) {% else %} @@ -88,7 +87,7 @@ Puedes borrar los archivos de bitácora de tu ejecución de flujo de trabajo. {% {% data reusables.repositories.navigate-to-workflow-superlinter %} {% data reusables.repositories.view-run-superlinter %} {% ifversion fpt or ghes > 2.22 or ghae %} -1. In the upper right corner, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. +1. En la esquina superior derecha, haz clic en el {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. {% ifversion fpt or ghes > 3.0 or ghae %} ![Icono de Kebab horizontal](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated-2.png) {% else %} diff --git a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md index c7d234cebc..eac8e4f014 100644 --- a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md +++ b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md @@ -11,7 +11,6 @@ shortTitle: Visualizar el tiempo de ejecución de un job {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} Los minutos de ejecución facturables para un job solo se muestran en aquellos jobs que se ejecutan en repositorios privados que utilizan ejecutores hospedados en {% data variables.product.prodname_dotcom %}. No hay minutos facturables cuando se utiliza {% data variables.product.prodname_actions %} en repositorios públicos o para trabajos que se ejecutan en ejecutores auto-hospedados. diff --git a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md index 4e10584889..3ab7a4813b 100644 --- a/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md +++ b/translations/es-ES/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md @@ -13,7 +13,6 @@ shortTitle: Visualizar el historial de ejecución de un flujo de trabajo {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.repositories.permissions-statement-read %} diff --git a/translations/es-ES/content/actions/publishing-packages/about-packaging-with-github-actions.md b/translations/es-ES/content/actions/publishing-packages/about-packaging-with-github-actions.md index e3b48e3d9d..d85c757e21 100644 --- a/translations/es-ES/content/actions/publishing-packages/about-packaging-with-github-actions.md +++ b/translations/es-ES/content/actions/publishing-packages/about-packaging-with-github-actions.md @@ -18,7 +18,6 @@ shortTitle: Empaquetar con GitHub Actions {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.package_registry.about-packaging-and-actions %} diff --git a/translations/es-ES/content/actions/publishing-packages/index.md b/translations/es-ES/content/actions/publishing-packages/index.md index e80ce51987..43d9628229 100644 --- a/translations/es-ES/content/actions/publishing-packages/index.md +++ b/translations/es-ES/content/actions/publishing-packages/index.md @@ -1,7 +1,7 @@ --- title: Publicar paquetes shortTitle: Publicar paquetes -intro: 'You can automatically publish packages using {% data variables.product.prodname_actions %}.' +intro: 'Puedes publicar paquetes automáticamente utilizando las {% data variables.product.prodname_actions %}.' versions: fpt: '*' ghes: '*' diff --git a/translations/es-ES/content/actions/publishing-packages/publishing-docker-images.md b/translations/es-ES/content/actions/publishing-packages/publishing-docker-images.md index 884acd9d35..50816eecdb 100644 --- a/translations/es-ES/content/actions/publishing-packages/publishing-docker-images.md +++ b/translations/es-ES/content/actions/publishing-packages/publishing-docker-images.md @@ -18,7 +18,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introducción @@ -119,7 +118,7 @@ Las opciones de `login-action` que se requieren para el {% data variables.produc * `password`: Puedes utilizar el secreto generado automáticamente `GITHUB_TOKEN` para la contraseña. Para más información, consulta "[Autenticando con el GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)." {% ifversion fpt %} -The `metadata-action` option required for {% data variables.product.prodname_registry %} is: +La opción de `metadata-action` que se requiere para el {% data variables.product.prodname_registry %} es: * `images`: El designador de nombre de la imagen de Docker que estás compilando. {% endif %} @@ -171,7 +170,7 @@ jobs: {% ifversion ghae %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}{% raw %}/${{ github.repository }}/octo-image:${{ github.event.release.tag_name }}{% endraw %} ``` -The above workflow checks out the {% data variables.product.prodname_dotcom %} repository, uses the `login-action` to log in to the registry, and then uses the `build-push-action` action to: build a Docker image based on your repository's `Dockerfile`; push the image to the Docker registry, and apply the commit SHA and release version as image tags. +El flujo de trabajo anterior verifica el repositorio {% data variables.product.prodname_dotcom %}, utiliza la `login-action` para ingresar en el registro y luego utiliza la acción `build-push-action` para: crear una imagen de Docker con base en el `Dockerfile` de tu repositorio; subir la imagen al registro de Docker y aplicar el SHA de confirmación y versión de lanzamiento como etiquetas de la imagen. {% endif %} ## Publicar imágenes en Docker Hub y en {% data variables.product.prodname_registry %} diff --git a/translations/es-ES/content/actions/publishing-packages/publishing-java-packages-with-gradle.md b/translations/es-ES/content/actions/publishing-packages/publishing-java-packages-with-gradle.md index 72ed5db1b7..e0d320e5dc 100644 --- a/translations/es-ES/content/actions/publishing-packages/publishing-java-packages-with-gradle.md +++ b/translations/es-ES/content/actions/publishing-packages/publishing-java-packages-with-gradle.md @@ -20,7 +20,6 @@ shortTitle: Paquetes de Java con Gradle {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introducción diff --git a/translations/es-ES/content/actions/publishing-packages/publishing-java-packages-with-maven.md b/translations/es-ES/content/actions/publishing-packages/publishing-java-packages-with-maven.md index a18a958be4..6c83c12108 100644 --- a/translations/es-ES/content/actions/publishing-packages/publishing-java-packages-with-maven.md +++ b/translations/es-ES/content/actions/publishing-packages/publishing-java-packages-with-maven.md @@ -20,7 +20,6 @@ shortTitle: Paquetes de Java con Maven {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introducción diff --git a/translations/es-ES/content/actions/publishing-packages/publishing-nodejs-packages.md b/translations/es-ES/content/actions/publishing-packages/publishing-nodejs-packages.md index 136818a60f..f27b12e990 100644 --- a/translations/es-ES/content/actions/publishing-packages/publishing-nodejs-packages.md +++ b/translations/es-ES/content/actions/publishing-packages/publishing-nodejs-packages.md @@ -21,7 +21,6 @@ shortTitle: Paquetes de Node.js {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introducción diff --git a/translations/es-ES/content/actions/quickstart.md b/translations/es-ES/content/actions/quickstart.md index fdf602668f..1614d377b0 100644 --- a/translations/es-ES/content/actions/quickstart.md +++ b/translations/es-ES/content/actions/quickstart.md @@ -11,22 +11,23 @@ versions: type: quick_start topics: - Fundamentals +shortTitle: Inicio Rápido --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -### Introducción +## Introducción Solo necesitas un repositorio de {% data variables.product.prodname_dotcom %} para crear y ejecutar un flujo de trabajo de {% data variables.product.prodname_actions %}. En esta guía, agregarás un flujo de trabajo que demuestre algunas de las características esenciales de las {% data variables.product.prodname_actions %}. El siguiente ejemplo te muestra cómo los jobs de las {% data variables.product.prodname_actions %} pueden activarse automáticamente, dónde se ejecutan y cómo pueden interactuar con el código en tu repositorio. -### Crear tu primer flujo de trabajo +## Crear tu primer flujo de trabajo -1. Desde tu repositorio en {% data variables.product.prodname_dotcom %}, crea un archivo nuevo en el directorio `.github/workflows` que se llame `github-actions-demo.yml`. Para obtener más información, consulta "[Crear nuevos archivos](/github/managing-files-in-a-repository/creating-new-files)." -2. Copia el siguiente contenido de YAML en el arcvhivo `github-actions-demo.yml`: +1. Crea un directorio de `.github/workflows` en tu repositorio en {% data variables.product.prodname_dotcom %} si es que dicho directorio aún no existe. +2. En el directorio `.github/workflows`, crea un archivo llamado `github-actions-demo.yml`. Para obtener más información, consulta "[Crear nuevos archivos](/github/managing-files-in-a-repository/creating-new-files)." +3. Copia el siguiente contenido de YAML en el arcvhivo `github-actions-demo.yml`: {% raw %} ```yaml{:copy} name: GitHub Actions Demo @@ -53,7 +54,7 @@ El siguiente ejemplo te muestra cómo los jobs de las {% data variables.product. El confirmar el flujo de trabajo en una rama de tu repositorio activa el evento `push` y ejecuta tu flujo de trabajo. -### Ver los resultados de tu flujo de trabajo +## Ver los resultados de tu flujo de trabajo {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} @@ -72,11 +73,11 @@ El confirmar el flujo de trabajo en una rama de tu repositorio activa el evento Por ejemplo, puedes ver la lista de archivos en tu repositorio: ![Detalle de la acción de ejemplo](/assets/images/help/repository/actions-quickstart-log-detail.png) -### Más plantillas de flujo de trabajo +## Más plantillas de flujo de trabajo {% data reusables.actions.workflow-template-overview %} -### Pasos siguientes +## Pasos siguientes El flujo de trabajo de ejemplo que acabas de agregar se ejecuta cada vez que se sube el código a la rama y te muestra cómo pueden funcionar las {% data variables.product.prodname_actions %} con el contenido de tu repositorio. Pero esto es solo el inicio de lo que puedes hacer con {% data variables.product.prodname_actions %}: @@ -86,4 +87,3 @@ El flujo de trabajo de ejemplo que acabas de agregar se ejecuta cada vez que se {% data variables.product.prodname_actions %} puede ayudarte a automatizar casi cualquier aspecto de tu s procesos de desarrollo de aplicaciones. ¿Listo para comenzar? Aquí tienes algunos recursos útiles para que tomes tus siguientes pasos con {% data variables.product.prodname_actions %}: - "[Aprende más sobre {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" con este tutorial detallado. -- "[Guías](/actions/guides)" para casos de uso específico y ejemplos. diff --git a/translations/es-ES/content/actions/security-guides/automatic-token-authentication.md b/translations/es-ES/content/actions/security-guides/automatic-token-authentication.md index 7590702908..1772ff6d12 100644 --- a/translations/es-ES/content/actions/security-guides/automatic-token-authentication.md +++ b/translations/es-ES/content/actions/security-guides/automatic-token-authentication.md @@ -1,5 +1,5 @@ --- -title: Automatic token authentication +title: Autenticación automática de token intro: '{% data variables.product.prodname_dotcom %} proporciona un token que puedes usar para autenticar en nombre de {% data variables.product.prodname_actions %}.' product: '{% data reusables.gated-features.actions %}' redirect_from: @@ -11,16 +11,15 @@ versions: fpt: '*' ghes: '*' ghae: '*' -shortTitle: Automatic token authentication +shortTitle: Autenticación de token automática --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Acerca del secreto del `GITHUB_TOKEN` -At the start of each workflow run, {% data variables.product.prodname_dotcom %} automatically creates a unique `GITHUB_TOKEN` secret to use in your workflow. Puedes usar el `GITHUB_TOKEN` para autenticarte en una ejecución de flujo de trabajo. +Al inicio de cada ejecución de flujo de trabajo, {% data variables.product.prodname_dotcom %} crea automáticamente un secreto único de `GITHUB_TOKEN` para utilizar en tu flujo de trabajo. Puedes usar el `GITHUB_TOKEN` para autenticarte en una ejecución de flujo de trabajo. Cuando habilitas {% data variables.product.prodname_actions %}, {% data variables.product.prodname_dotcom %} instala una {% data variables.product.prodname_github_app %} en tu repositorio. El secreto del `GITHUB_TOKEN` es un token de acceso de instalación de {% data variables.product.prodname_github_app %}. Puedes usar el token de acceso de instalación para autenticarte en nombre de la {% data variables.product.prodname_github_app %} instalado en tu repositorio. Los permisos del token están limitados al repositorio que contiene tu flujo de trabajo. Para obtener más información, consulta "[Permisos para el `GITHUB_TOKEN`](#permissions-for-the-github_token)." @@ -98,7 +97,7 @@ jobs: Para obtener mpas información sobre las terminales de la API a los que pueden acceder las {% data variables.product.prodname_github_apps %} con cada permiso, consulta la sección "[ Permisos de las {% data variables.product.prodname_github_app %}](/rest/reference/permissions-required-for-github-apps)". {% ifversion fpt or ghes > 3.1 or ghae-next %} -La siguiente tabla muestra los permisos que se otorgan al `GITHUB_TOKEN` predeterminadamente. People with admin permissions to an {% ifversion not ghes %}enterprise, organization, or repository,{% else %}organization or repository{% endif %} can set the default permissions to be either permissive or restricted. Para obtener más información sobre cómo configurar los permisos predeterminados del `GITHUB_TOKEN` para tu {% ifversion not ghes %}empresa, organización o repositorio,{% else %}organización o repositorio,{% endif %} consulta las secciones {% ifversion not ghes %}"[Requerir políticas de {% data variables.product.prodname_actions %} en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account#setting-the-permissions-of-the-github_token-for-your-enterprise)", {% endif %}"[Inhabilitar o limitar las {% data variables.product.prodname_actions %} para tu organización](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization#setting-the-permissions-of-the-github_token-for-your-organization)" o "[Administrar los ajustes de las {% data variables.product.prodname_actions %} para un repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#setting-the-permissions-of-the-github_token-for-your-repository)". +La siguiente tabla muestra los permisos que se otorgan al `GITHUB_TOKEN` predeterminadamente. Las personas con permisos administrativos en una {% ifversion not ghes %}empresa, organización o repositorio{% else %}organización o repositorio{% endif %} pueden configurar los permisos predeterminados para que sean permisivos o restringidos. Para obtener más información sobre cómo configurar los permisos predeterminados del `GITHUB_TOKEN` para tu {% ifversion not ghes %}empresa, organización o repositorio,{% else %}organización o repositorio,{% endif %} consulta las secciones {% ifversion not ghes %}"[Requerir políticas de {% data variables.product.prodname_actions %} en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account#setting-the-permissions-of-the-github_token-for-your-enterprise)", {% endif %}"[Inhabilitar o limitar las {% data variables.product.prodname_actions %} para tu organización](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization#setting-the-permissions-of-the-github_token-for-your-organization)" o "[Administrar los ajustes de las {% data variables.product.prodname_actions %} para un repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#setting-the-permissions-of-the-github_token-for-your-repository)". | Ámbito | Acceso predeterminado
(permisivo) | Acceso predeterminado
(restringido) | Acceso máximo
de los repos bifurcados | | ------------------------- | ------------------------------------------ | -------------------------------------------- | ---------------------------------------------- | diff --git a/translations/es-ES/content/actions/security-guides/encrypted-secrets.md b/translations/es-ES/content/actions/security-guides/encrypted-secrets.md index 90637355a2..1e93dae516 100644 --- a/translations/es-ES/content/actions/security-guides/encrypted-secrets.md +++ b/translations/es-ES/content/actions/security-guides/encrypted-secrets.md @@ -16,7 +16,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Acerca de los secretos cifrados @@ -222,7 +221,7 @@ Puedes revisar qué políticas de acceso se están aplicando a un secreto en tu {% endnote %} -Para proporcionar una acción con un secreto como variable de entrada o de entorno, puedes usar el contexto de `secrets` para acceder a los secretos que has creado en tu repositorio. For more information, see "[Contexts](/actions/learn-github-actions/contexts)" and "[Workflow syntax for {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)." +Para proporcionar una acción con un secreto como variable de entrada o de entorno, puedes usar el contexto de `secrets` para acceder a los secretos que has creado en tu repositorio. Para obtener más información, consulta las secciones de "[Contextos](/actions/learn-github-actions/contexts)" y "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)". {% raw %} ```yaml diff --git a/translations/es-ES/content/actions/security-guides/index.md b/translations/es-ES/content/actions/security-guides/index.md index 370de92095..0157e89b79 100644 --- a/translations/es-ES/content/actions/security-guides/index.md +++ b/translations/es-ES/content/actions/security-guides/index.md @@ -1,7 +1,7 @@ --- -title: Security guides -shortTitle: Security guides -intro: 'Security hardening and good practices for {% data variables.product.prodname_actions %}.' +title: Guías de seguridad +shortTitle: Guías de seguridad +intro: 'Fortalecimiento de seguridad y buenas prácticas para {% data variables.product.prodname_actions %}.' versions: fpt: '*' ghes: '*' diff --git a/translations/es-ES/content/actions/security-guides/security-hardening-for-github-actions.md b/translations/es-ES/content/actions/security-guides/security-hardening-for-github-actions.md index 432db43284..80dda48ea7 100644 --- a/translations/es-ES/content/actions/security-guides/security-hardening-for-github-actions.md +++ b/translations/es-ES/content/actions/security-guides/security-hardening-for-github-actions.md @@ -18,7 +18,6 @@ miniTocMaxHeadingLevel: 3 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Resumen @@ -48,7 +47,7 @@ Para ayudar a prevenir la divulgación accidental, {% data variables.product.pro - Rota los secretos con frecuencia para reducir la ventana de tiempo en la que un secreto puesto en riesgo es aún válido. {% ifversion fpt or ghes > 3.0 or ghae %} - **Considera requerir revisiones para el acceso a los secretos** - - Puedes utilizar revisiones requeridas para proteger los secretos del ambiente. Un job del flujo de trabajo no podrá acceder a los secretos del ambiente hasta que el revisor otorgue la aprobación. Para obtener más información acerca de almacenar secretos en los ambientes o requerir revisiones para ellos, consulta las secciones "[Secretos cifrados](/actions/reference/encrypted-secrets)" y "[Ambientes](/actions/reference/environments)". + - Puedes utilizar revisiones requeridas para proteger los secretos del ambiente. Un job del flujo de trabajo no podrá acceder a los secretos del ambiente hasta que el revisor otorgue la aprobación. For more information about storing secrets in environments or requiring reviews for environments, see "[Encrypted secrets](/actions/reference/encrypted-secrets)" and "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." {% endif %} ## Utilizar `CODEOWNERS` para monitorear cambios @@ -59,7 +58,7 @@ Para obtener más información, consulta "[Acerca de los propietarios del códig ## Entender el riesgo de las inyecciones de código -When creating workflows, [custom actions](/actions/creating-actions/about-actions), and [composite actions](/actions/creating-actions/creating-a-composite-action) actions, you should always consider whether your code might execute untrusted input from attackers. Esto puede ocurrir cuando un atacante agrega comandos y scripts malintencionados a un contexto. Cuando tu flujo de trabajo se ejecuta, estas secuencias podrían interpretarse como código que luego se ejecutará en el ejecutor. +Cuando creas flujos de trabajo, [acciones personalizadas](/actions/creating-actions/about-actions) y [acciones compuestas](/actions/creating-actions/creating-a-composite-action), siempre debes considerar si tu código podría ejecutar una entrada no confiable de los atacantes. Esto puede ocurrir cuando un atacante agrega comandos y scripts malintencionados a un contexto. Cuando tu flujo de trabajo se ejecuta, estas secuencias podrían interpretarse como código que luego se ejecutará en el ejecutor. Los atacantes pueden agregar su propio código malintencionado al [contexto `github`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context), al cual se le debe tratar como una entrada potencialmente no confiable. Estos contextos pueden terminar habitualmente con `body`, `default_branch`, `email`, `head_ref`, `label`, `message`, `name`, `page_name`,`ref`, y `title`. Por ejemplo: `github.event.issue.title`, o `github.event.pull_request.body`. @@ -183,6 +182,12 @@ Puedes ayudar a mitigar este riesgo si sigues estas buenas prácticas: Aunque fijar el SHA de una confirmación es la opción más segura, especificar una etiqueta es más conveniente y se utiliza ampliamente. Si te gustaría especificar una etiqueta, entonces asegúrate de que confías en los creadores de la acción. La insignia de ‘Verified creator’ en {% data variables.product.prodname_marketplace %} es una señal útil, ya que te indica que la acción viene de un equipo cuya identidad verificó {% data variables.product.prodname_dotcom %}. Nota que este acercamiento sí tiene riesgos aún si confías en el autor, ya que una etiqueta se puede mover o borrar en caso de que un actor malicioso consiga acceso al repositorio que almacena la acción. +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## Reutilizar los flujos de trabajo de terceros + +El mismo principio que se describió anteriormente para utilizar acciones de terceros también aplica para los flujos de trabajo de terceros. Puedes ayudar a mitigar los riesgos asociados con la reutilización de flujos de trabajo si sigues las mismas buenas prácticas que se describen anteriormente. Para obtener más información, consulta la sección "[Reutilizar flujos de trabajo](/actions/learn-github-actions/reusing-workflows)". +{% endif %} + ## Impacto potencial de un ejecutor puesto en riesgo Estas secciones consideran algunos de los pasos que puede llevar a cabo un atacante si pueden ejecutar comandos malintencionados en un ejecutor de {% data variables.product.prodname_actions %}. @@ -296,40 +301,40 @@ Las siguientes tablas describen los eventos de {% data variables.product.prodnam | ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `enterprise.register_self_hosted_runner` | Se crea cuando se registra un ejecutor auto-hospedado nuevo. Para obtener más información, consulta la sección "[Agregar un ejecutor auto-hospedado a una empresa](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-enterprise)". | | `enterprise.remove_self_hosted_runner` | Se activa cuando se elimina un ejecutor auto-hospedado. | -| `enterprise.runner_group_runners_updated` | Triggered when a runner group's member list is updated. Para obtener más información, consulta la sección "[Configurar los ejecutores auto-hospedados en un grupo para una organización](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)". {% ifversion fpt or ghes > 3.1 or ghae-issue-1157 %} -| `enterprise.self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." | -| `enterprise.self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %} +| `enterprise.runner_group_runners_updated` | Se activa cuando la lista de miembros de un grupo de ejecutores se actualiza. Para obtener más información, consulta la sección "[Configurar los ejecutores auto-hospedados en un grupo para una organización](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)". {% ifversion fpt or ghes > 3.1 or ghae-issue-1157 %} +| `enterprise.self_hosted_runner_online` | Se activa cuando la aplicación del ejecutor se inicia. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." | +| `enterprise.self_hosted_runner_offline` | Se activa cuando se detiene la aplicación del ejecutor. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta la sección "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)".{% endif %} | `enterprise.self_hosted_runner_updated` | Se activa cuando se actualiza la aplicación ejecutora. Puede visualizarse utilizando la API de REST y la IU. Este evento no se incluye cuando exportas la bitácora de auditoría como datos de JSON o como un archivo de CSV. Para obtener más información, consulta las secciones "[Acerca de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)" y "[Revisar la bitácora de auditoría en tu organización](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#exporting-the-audit-log)". | | `org.register_self_hosted_runner` | Se crea cuando se registra un ejecutor auto-hospedado nuevo. Para obtener más información, consulta la sección "[Agregar un ejecutor auto-hospedado a una organización](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)". | | `org.remove_self_hosted_runner` | Se activa cuando se elimina un ejecutor auto-hospedado. Para obtener más información, consulta la sección [Eliminar a un ejecutor de una organización](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization). | | `org.runner_group_runners_updated` | Se activa cuando se actualiza la lista de miembros de un grupo de ejecutores. Para obtener más información, consulta la sección "[Configurar ejecutores auto-hospedados en un grupo para una organización](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)". | -| `org.runner_group_updated` | Se activa cuando se cambia la configuración de un grupo de ejecutores auto-hospedados. For more information, see "[Changing the access policy of a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)."{% ifversion fpt or ghes > 3.1 or ghae-issue-1157 %} -| `org.self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." | -| `org.self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %} +| `org.runner_group_updated` | Se activa cuando se cambia la configuración de un grupo de ejecutores auto-hospedados. Para obtener más información, consulta la sección "[cambiar la política de acceso de un grupo de ejecutores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)".{% ifversion fpt or ghes > 3.1 or ghae-issue-1157 %} +| `org.self_hosted_runner_online` | Se activa cuando la aplicación del ejecutor se inicia. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." | +| `org.self_hosted_runner_offline` | Se activa cuando se detiene la aplicación del ejecutor. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta la sección "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)".{% endif %} | `org.self_hosted_runner_updated` | Se activa cuando se actualiza la aplicación ejecutora. Se puede ver utilizando la API de REST y la IU; no se puede ver en la exportación de JSON/CSV. Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)." | | `repo.register_self_hosted_runner` | Se crea cuando se registra un ejecutor auto-hospedado nuevo. Para obtener más información, consulta la sección "[Agregar un ejecutor auto-hospedado a un repositorio](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)". | -| `repo.remove_self_hosted_runner` | Se activa cuando se elimina un ejecutor auto-hospedado. For more information, see "[Removing a runner from a repository](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)."{% ifversion fpt or ghes > 3.1 or ghae-issue-1157 %} -| `repo.self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." | -| `repo.self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %} +| `repo.remove_self_hosted_runner` | Se activa cuando se elimina un ejecutor auto-hospedado. Para obtener más información, consulta la sección "[Eliminar un ejecutor de un repositorio](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)".{% ifversion fpt or ghes > 3.1 or ghae-issue-1157 %} +| `repo.self_hosted_runner_online` | Se activa cuando la aplicación del ejecutor se inicia. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." | +| `repo.self_hosted_runner_offline` | Se activa cuando se detiene la aplicación del ejecutor. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta la sección "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)".{% endif %} | `repo.self_hosted_runner_updated` | Se activa cuando se actualiza la aplicación ejecutora. Se puede ver utilizando la API de REST y la IU; no se puede ver en la exportación de JSON/CSV. Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)." | ### Eventos para grupos de ejecutores auto-hospedados -| Acción | Descripción | -| ------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `enterprise.runner_group_created` | Se activa cuando se crea un grupo de ejecutores auto-hospedados. Para obtener más información, consulta la sección "[Crear un grupo de ejecutores auto-hospedados para una empresa](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-enterprise)". | -| `enterprise.runner_group_removed` | Se activa cuando se elimina un grupo de ejecutores auto-hospedado. Para obtener más información, consulta la sección "[Eliminar un grupo de ejecutores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)". | -| `enterprise.runner_group_runner_removed` | Se activa cuando se utiliza la API de REST para eliminar un ejecutor auto-hospedado de un grupo. | -| `enterprise.runner_group_runners_added` | Se activa cuando se agrega un ejecutor auto-hospedado a un grupo. For more information, see "[Moving a self-hosted runner to a group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)."{% ifversion fpt or ghes > 2.22 or ghae %} -| `enterprise.runner_group_updated` | Se activa cuando se cambia la configuración de un grupo de ejecutores auto-hospedados. For more information, see "[Changing the access policy of a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)."{% endif %}{% ifversion ghes = 2.22 %} -| `enterprise.runner_group_renamed` | Triggered when the self-hosted runner group is renamed. | -| `enterprise.runner_group_visiblity_updated` | Triggered when the visibility settings of the self-hosted runner group are changed.{% endif %} -| `org.runner_group_created` | Se activa cuando se crea un grupo de ejecutores auto-hospedados. Para obtener más información, consulta la sección "[Crear un grupo de ejecutores auto-hospedados para una organización](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization)". | -| `org.runner_group_removed` | Se activa cuando se elimina un grupo de ejecutores auto-hospedado. For more information, see "[Removing a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)."{% ifversion fpt or ghes > 2.22 or ghae %} -| `org.runner_group_updated` | Se activa cuando se cambia la configuración de un grupo de ejecutores auto-hospedados. For more information, see "[Changing the access policy of a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)."{% endif %} -| `org.runner_group_runners_added` | Se activa cuando se agrega un ejecutor auto-hospedado a un grupo. Para obtener más información, consulta la sección "[Mover un ejecutor auto-hospedado a un grupo](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)". | -| `org.runner_group_runner_removed` | Se activa cuando se utiliza la API de REST para eliminar un ejecutor auto-hospedado de un grupo. For more information, see "[Remove a self-hosted runner from a group for an organization](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)."{% ifversion ghes = 2.22 %} -| `org.runner_group_renamed` | Triggered when the self-hosted runner group is renamed. | -| `org.runner_group_visiblity_updated` | Triggered when the visibility settings of the self-hosted runner group are changed.{% endif %} +| Acción | Descripción | +| ------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `enterprise.runner_group_created` | Se activa cuando se crea un grupo de ejecutores auto-hospedados. Para obtener más información, consulta la sección "[Crear un grupo de ejecutores auto-hospedados para una empresa](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-enterprise)". | +| `enterprise.runner_group_removed` | Se activa cuando se elimina un grupo de ejecutores auto-hospedado. Para obtener más información, consulta la sección "[Eliminar un grupo de ejecutores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)". | +| `enterprise.runner_group_runner_removed` | Se activa cuando se utiliza la API de REST para eliminar un ejecutor auto-hospedado de un grupo. | +| `enterprise.runner_group_runners_added` | Se activa cuando se agrega un ejecutor auto-hospedado a un grupo. Para obtener más información, consulta la sección "[Mover un ejecutor auto-hospedado a un grupo](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)".{% ifversion fpt or ghes > 2.22 or ghae %} +| `enterprise.runner_group_updated` | Se activa cuando se cambia la configuración de un grupo de ejecutores auto-hospedados. Para obtener más información, consulta la sección "[Cambiar la política de acceso de un grupo de ejecutores auto-hospedado](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)".{% endif %}{% ifversion ghes = 2.22 %} +| `enterprise.runner_group_renamed` | Se activa cuando el grupo de ejecutores auto-hospedados se renombra. | +| `enterprise.runner_group_visiblity_updated` | Se activa cuando se cambia la configuración de visibilidad del grupo de ejecutores auto-hospedados.{% endif %} +| `org.runner_group_created` | Se activa cuando se crea un grupo de ejecutores auto-hospedados. Para obtener más información, consulta la sección "[Crear un grupo de ejecutores auto-hospedados para una organización](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization)". | +| `org.runner_group_removed` | Se activa cuando se elimina un grupo de ejecutores auto-hospedado. Para obtener más información, consulta la sección "[Eliminar un grupo de ejecutores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)".{% ifversion fpt or ghes > 2.22 or ghae %} +| `org.runner_group_updated` | Se activa cuando se cambia la configuración de un grupo de ejecutores auto-hospedados. Para obtener más información, consulta la sección "[cambiar la política de acceso de un grupo de ejecutores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)".{% endif %} +| `org.runner_group_runners_added` | Se activa cuando se agrega un ejecutor auto-hospedado a un grupo. Para obtener más información, consulta la sección "[Mover un ejecutor auto-hospedado a un grupo](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)". | +| `org.runner_group_runner_removed` | Se activa cuando se utiliza la API de REST para eliminar un ejecutor auto-hospedado de un grupo. Para obtener más información, consulta la sección "[Eliminar un ejecutor auto-hospedados de un grupo para una organización](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)". {% ifversion ghes = 2.22 %} +| `org.runner_group_renamed` | Se activa cuando el grupo de ejecutores auto-hospedados se renombra. | +| `org.runner_group_visiblity_updated` | Se activa cuando se cambia la configuración de visibilidad del grupo de ejecutores auto-hospedados.{% endif %} ### Eventos para las actividades de los flujos de trabajo diff --git a/translations/es-ES/content/actions/using-containerized-services/about-service-containers.md b/translations/es-ES/content/actions/using-containerized-services/about-service-containers.md index c628d193d1..a553a44a1d 100644 --- a/translations/es-ES/content/actions/using-containerized-services/about-service-containers.md +++ b/translations/es-ES/content/actions/using-containerized-services/about-service-containers.md @@ -18,7 +18,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Acerca de los contenedores de servicios diff --git a/translations/es-ES/content/actions/using-containerized-services/creating-postgresql-service-containers.md b/translations/es-ES/content/actions/using-containerized-services/creating-postgresql-service-containers.md index d066822519..74feee1893 100644 --- a/translations/es-ES/content/actions/using-containerized-services/creating-postgresql-service-containers.md +++ b/translations/es-ES/content/actions/using-containerized-services/creating-postgresql-service-containers.md @@ -19,7 +19,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introducción diff --git a/translations/es-ES/content/actions/using-containerized-services/creating-redis-service-containers.md b/translations/es-ES/content/actions/using-containerized-services/creating-redis-service-containers.md index 879ff1eeea..be18cdd6f7 100644 --- a/translations/es-ES/content/actions/using-containerized-services/creating-redis-service-containers.md +++ b/translations/es-ES/content/actions/using-containerized-services/creating-redis-service-containers.md @@ -19,7 +19,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introducción diff --git a/translations/es-ES/content/actions/using-containerized-services/index.md b/translations/es-ES/content/actions/using-containerized-services/index.md index e18f2fb667..22eb359ee6 100644 --- a/translations/es-ES/content/actions/using-containerized-services/index.md +++ b/translations/es-ES/content/actions/using-containerized-services/index.md @@ -1,7 +1,7 @@ --- -title: Using containerized services -shortTitle: Containerized services -intro: 'You can use containerized services in your {% data variables.product.prodname_actions %} workflows.' +title: Utilizar servicios de contenedor +shortTitle: Servicios de contenedor +intro: 'Puedes utilizar servicios de contenedor en tus flujos de trabajo de {% data variables.product.prodname_actions %}.' versions: fpt: '*' ghes: '*' diff --git a/translations/es-ES/content/actions/using-github-hosted-runners/about-ae-hosted-runners.md b/translations/es-ES/content/actions/using-github-hosted-runners/about-ae-hosted-runners.md index b84ceec4fa..fcd624892a 100644 --- a/translations/es-ES/content/actions/using-github-hosted-runners/about-ae-hosted-runners.md +++ b/translations/es-ES/content/actions/using-github-hosted-runners/about-ae-hosted-runners.md @@ -6,23 +6,16 @@ versions: ghae: '*' --- - - - -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} ## Acerca de las {% data variables.actions.hosted_runner %} -Un {% data variables.actions.hosted_runner %} es una máquina virtual hospedada en {% data variables.product.prodname_dotcom %} que tiene instalado el servicio de ejecutor de {% data variables.product.prodname_actions %}. +Un {% data variables.actions.hosted_runner %} es una máquina virtual que administra {% data variables.product.prodname_dotcom %} y que tiene instalado el servicio de ejecutor de {% data variables.product.prodname_actions %}. Los {% data variables.actions.hosted_runner %} de tu empresa son dedicados y puedes elegir de una amplia gama de opciones de hardware y software. Predeterminadamente, {% data variables.product.company_short %} administra y autoescala a los {% data variables.actions.hosted_runner %} integralmente para maximizar el rendimiento mientras que minimiza los costos.{% ifversion ghae-next %} Opcionalmente, puedes configurar los parámetros de este auto-escalamiento para reducir tus costos aún más.{% endif %} -{% data variables.product.prodname_ghe_managed %} te permite crear y personalizar los {% data variables.actions.hosted_runner %} utilizando imágenes de Ubuntu y de Windows; puedes seleccionar el tamaño de máquina que quieras y configurar un trabajo en red con seguridad robustecida para ellos. {% data variables.product.prodname_dotcom %} administra y auto-escala los {% data variables.actions.hosted_runner %} integralmente. +{% data variables.product.prodname_ghe_managed %} te permite crear y personalizar {% data variables.actions.hosted_runner %}s utilizando imágenes de Ubuntu o de Windows; puedes seleccionar el tamaño de máquina que quieras y, opcionalmente, configurar un rango de IP públicas para tus {% data variables.actions.hosted_runner %}s. Cada job del flujo de trabajo se ejecuta en una instancia nueva del {% data variables.actions.hosted_runner %} y puedes ejecutar flujos de trabajo directamente en la máquina virtual o en un contenedor de Docker. Todos los pasos del job se ejecutan en la misma instancia, permitiendo que las acciones en este job compartan información utilizando el sistema de archivos del {% data variables.actions.hosted_runner %}. -{% note %} -Los {% data variables.actions.hosted_runner %} son los únicos disponibles para {% data variables.product.prodname_ghe_managed %} y no se incluye a los ejecutores auto-hospedados. -{% endnote %} - Para agregar {% data variables.actions.hosted_runner %} a tu organización o empresa, consulta la sección ["Agregar {% data variables.actions.hosted_runner %}](/actions/using-github-hosted-runners/adding-ae-hosted-runners)". ## Asignaciones de agrupaciones para los {% data variables.actions.hosted_runner %} @@ -35,11 +28,9 @@ Durante el beta de los {% data variables.actions.hosted_runner %}, puedes admini ## Facturación -{% data variables.product.prodname_actions %} se encuentra acutalmente en beta para {% data variables.product.prodname_ghe_managed %}. Durante este periodo beta, los {% data variables.actions.hosted_runner %} no se facturan, y pueden utilizarse gratuitamente. - Una vez que termine el beta, el uso facturable incluirá el tiempo total de actividad para las instancias activas en tus conjuntos de ejecutores hospedados en AE. Esto incluye: - Hora del job - minutos que se utilizaron ejecutando el job de las acciones. -- Administración - minutos que se utilizaron haciendo re-imagen de las máquinas y tiempo inactivo que se creó como resultado de un comportamiento de auto-escalamiento deseado. +- Administración - minutos gastados volviendo a hacer la imagen de las máquinas{% ifversion ghae-next %} y cualquier tiempo de inactividad que se cree como resultado del comportamiento de autoescalamiento deseado{% endif %}. Los precios aumentarán linearmente con los núcleos. Por ejemplo, 4 núcleos costarán lo doble que 2 núcleos. Las MV de Windows tendrán un precio más alto que las de Linux. @@ -78,6 +69,14 @@ Para obtener una lista de rangos de direcciones IP que utilizan las {% data vari La lista de direcciones IP permitidas de {% data variables.product.prodname_actions %} que devuelve la API se actualiza una vez por semana. +{% ifversion ghae-next %} + +## Autoescalamiento + +{% data variables.product.company_short %} administra cada agrupamiento de {% data variables.actions.hosted_runner %}s integralmente para maximizar el rendimiento mientras que minimiza los costos. Opcionalmente, puedes configurar los parámetros de auto-escalamiento para tu empresa si contactas a {% data variables.contact.github_support %}. Puedes definir la cantidad mínima de ejecutores inactivos y qué tanto deberían estar inactivos antes de eliminarlos de la agrupación. Cada agrupación puede contener hasta 600 ejecutores. + +{% endif %} + ## Privilegios adminsitrativos para los {% data variables.actions.hosted_runner %} Las máquinas virtuales Linux se ejecutan utilizando un `sudo` sin contraseña. Cuando necesitas ejecutar comandos o instalar herramientas que requieren más privilegios que el usuario actual, puedes usar `sudo` sin la necesidad de brindar una contraseña. Para obtener más información, consulta "[Manual de sudo](https://www.sudo.ws/man/1.8.27/sudo.man.html)." diff --git a/translations/es-ES/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/translations/es-ES/content/actions/using-github-hosted-runners/about-github-hosted-runners.md index 0b8fba85f2..c913541d3c 100644 --- a/translations/es-ES/content/actions/using-github-hosted-runners/about-github-hosted-runners.md +++ b/translations/es-ES/content/actions/using-github-hosted-runners/about-github-hosted-runners.md @@ -16,6 +16,7 @@ versions: shortTitle: Ejecutores hospedados en GitHub --- +{% data reusables.actions.ae-hosted-runners-beta %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} diff --git a/translations/es-ES/content/actions/using-github-hosted-runners/adding-ae-hosted-runners.md b/translations/es-ES/content/actions/using-github-hosted-runners/adding-ae-hosted-runners.md index 2fce3337cb..556defc6bd 100644 --- a/translations/es-ES/content/actions/using-github-hosted-runners/adding-ae-hosted-runners.md +++ b/translations/es-ES/content/actions/using-github-hosted-runners/adding-ae-hosted-runners.md @@ -5,7 +5,7 @@ versions: ghae: '*' --- -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} {% note %} @@ -19,7 +19,8 @@ Los {% data variables.actions.hosted_runner %} pueden utilizar la simagenes base Puedes agregar {% data variables.actions.hosted_runner %} que utilicen las imágenes base del sistema operativo de Azure. Para agregar {% data variables.actions.hosted_runner %} a tu organización o empresa, contacta al soporte de {% data variables.product.prodname_dotcom %} y ten a la mano la siguiente información: - Sistema operativo requerido: Se listan las opciones disponibles en ["Especificaciones de software](/actions/using-github-hosted-runners/about-ae-hosted-runners#software-specifications)". - - Elige un nombre para cada agrupación de {% data variables.actions.hosted_runner %}. Estos nombres se crean como etiquetas, lo cual te permite enrutar tus flujos de trabajo a estos ejecutores. Para obtener más información, consulta la sección "[Utilizar {% data variables.actions.hosted_runner %} en un flujo de trabajo](/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow)". + - Elige un nombre para cada agrupación de {% data variables.actions.hosted_runner %}. Estos nombres se crean como etiquetas, lo cual te permite enrutar tus flujos de trabajo a estos ejecutores. Para obtener más información, consulta la sección "[Utilizar {% data variables.actions.hosted_runner %}s en un flujo de trabajo](/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow)".{% ifversion ghae-next %} +{% data reusables.actions.autoscaling-parameters %}{% endif %} - Dónde agregar el {% data variables.actions.hosted_runner %}: Identifica los nombres de las organizaciones y empresas que recibirán los ejecutores. ## Agregar un {% data variables.actions.hosted_runner %} con una imagen personalizada @@ -33,7 +34,8 @@ Una vez que hayas creado una imagen personalizado utilizando los pasos anteriore - Nombre de imagen. - Versión. - SKU de la MV para la agrupación nueva. - - Elige un nombre para cada agrupación de {% data variables.actions.hosted_runner %}. Estos nombres se crean como etiquetas, lo cual te permite enrutar tus flujos de trabajo a estos ejecutores. Para obtener más información, consulta la sección "[Utilizar {% data variables.actions.hosted_runner %} en un flujo de trabajo](/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow)". + - Elige un nombre para cada agrupación de {% data variables.actions.hosted_runner %}. Estos nombres se crean como etiquetas, lo cual te permite enrutar tus flujos de trabajo a estos ejecutores. Para obtener más información, consulta la sección "[Utilizar {% data variables.actions.hosted_runner %}s en un flujo de trabajo](/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow)".{% ifversion ghae-next %} +{% data reusables.actions.autoscaling-parameters %}{% endif %} - Dónde agregar el {% data variables.actions.hosted_runner %}: Identifica los nombres de las organizaciones y empresas que recibirán los ejecutores. ## Revisar tus {% data variables.actions.hosted_runner %} diff --git a/translations/es-ES/content/actions/using-github-hosted-runners/creating-custom-images.md b/translations/es-ES/content/actions/using-github-hosted-runners/creating-custom-images.md index 396507ec3f..29ca598bda 100644 --- a/translations/es-ES/content/actions/using-github-hosted-runners/creating-custom-images.md +++ b/translations/es-ES/content/actions/using-github-hosted-runners/creating-custom-images.md @@ -5,7 +5,7 @@ versions: ghae: '*' --- -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} ## Crear un {% data variables.actions.hosted_runner %} con una imagen personalizada diff --git a/translations/es-ES/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md b/translations/es-ES/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md index be59fa2922..b019777eed 100644 --- a/translations/es-ES/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md +++ b/translations/es-ES/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md @@ -11,6 +11,7 @@ topics: shortTitle: Personalizar los ejecutores --- +{% data reusables.actions.ae-hosted-runners-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} Si requieres paquetes de software adicionales en los ejecutores hospedados en {% data variables.product.prodname_dotcom %}, puedes crear un job que instale los paquetes como parte de tu flujo de trabajo. diff --git a/translations/es-ES/content/actions/using-github-hosted-runners/index.md b/translations/es-ES/content/actions/using-github-hosted-runners/index.md index 62788c69bc..2baf86c8b4 100644 --- a/translations/es-ES/content/actions/using-github-hosted-runners/index.md +++ b/translations/es-ES/content/actions/using-github-hosted-runners/index.md @@ -17,5 +17,6 @@ children: shortTitle: Utilizar los ejecutores hospedados en GitHub --- +{% data reusables.actions.ae-hosted-runners-beta %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} diff --git a/translations/es-ES/content/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow.md b/translations/es-ES/content/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow.md index 43f105b160..06af854c17 100644 --- a/translations/es-ES/content/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow.md +++ b/translations/es-ES/content/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow.md @@ -6,7 +6,7 @@ versions: shortTitle: Utilizar ejecutores hospedados en AE --- -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} ## Utilizar {% data variables.actions.hosted_runner %} en un flujo de trabajo diff --git a/translations/es-ES/content/actions/using-github-hosted-runners/using-groups-to-manage-access-to-ae-hosted-runners.md b/translations/es-ES/content/actions/using-github-hosted-runners/using-groups-to-manage-access-to-ae-hosted-runners.md index 16fc275fb3..335dbe20b9 100644 --- a/translations/es-ES/content/actions/using-github-hosted-runners/using-groups-to-manage-access-to-ae-hosted-runners.md +++ b/translations/es-ES/content/actions/using-github-hosted-runners/using-groups-to-manage-access-to-ae-hosted-runners.md @@ -6,7 +6,7 @@ versions: shortTitle: Administrar los grupos de ejecución de AE --- -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} ## Acerca de los gupos de {% data variables.actions.hosted_runner %} diff --git a/translations/es-ES/content/actions/using-github-hosted-runners/using-labels-with-ae-hosted-runners.md b/translations/es-ES/content/actions/using-github-hosted-runners/using-labels-with-ae-hosted-runners.md index fbb4a24126..0dd42f83c3 100644 --- a/translations/es-ES/content/actions/using-github-hosted-runners/using-labels-with-ae-hosted-runners.md +++ b/translations/es-ES/content/actions/using-github-hosted-runners/using-labels-with-ae-hosted-runners.md @@ -6,7 +6,7 @@ versions: shortTitle: Etiquetar los ejecutores hospedados en AE --- -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} Para obtener más información sobre cómo utilizar las etiquetas para enrutar jobs a tipos específicos de {% data variables.actions.hosted_runner %}, consulta la sección "[Utilizar {% data variables.actions.hosted_runner %} en un flujo de trabajo](/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow)". diff --git a/translations/es-ES/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md b/translations/es-ES/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md index b3db5b2f64..48ef519aaa 100644 --- a/translations/es-ES/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md +++ b/translations/es-ES/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md @@ -29,7 +29,7 @@ Puedes configurar el {% data variables.product.prodname_code_scanning %} para ej ## Prerequisitos para el {% data variables.product.prodname_code_scanning %} -- A license for {% data variables.product.prodname_GH_advanced_security %}{% ifversion ghes > 3.0 %} (see "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)"){% endif %} +- Una licencia para {% data variables.product.prodname_GH_advanced_security %}{% ifversion ghes > 3.0 %} (consulta la sección "[Acerca de la facturación para {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)"){% endif %} - El {% data variables.product.prodname_code_scanning_capc %} habilitado en la consola de administración (consulta la sección "[Habilitar la {% data variables.product.prodname_GH_advanced_security %} para tu empresa](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)") @@ -62,13 +62,13 @@ Si configuras la herramienta de sincronización de la acción de {% data variabl {% ifversion ghes = 2.22 %} Para ejecutar el {% data variables.product.prodname_code_scanning %} en {% data variables.product.prodname_ghe_server %} con las {% data variables.product.prodname_actions %}, las acciones adecuadas deben estar disponibles localmente. Puedes hacer que las acciones estén disponibles en tres formas. -- **Recomendada**: Puedes utilizar [{% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud) para descargar acciones automáticamente desde {% data variables.product.prodname_dotcom_the_website %}. La máquina que hospeda tu instancia debe poder acceder a {% data variables.product.prodname_dotcom_the_website %}. Este enfoque garantiza que obtengas el software más reciente de forma automática. Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_github_connect %} para que se sincronice con {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)". +- **Recomendada**: Puedes utilizar [{% data variables.product.prodname_github_connect %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud) para descargar acciones automáticamente desde {% data variables.product.prodname_dotcom_the_website %}. La máquina que hospeda tu instancia debe poder acceder a {% data variables.product.prodname_dotcom_the_website %}. Este enfoque garantiza que obtengas el software más reciente de forma automática. Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_github_connect %} para que se sincronice con {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)". - Si quieres utilizar el {% data variables.product.prodname_codeql_workflow %}, puedes sincronizar el repositorio de {% data variables.product.prodname_dotcom_the_website %} a {% data variables.product.prodname_ghe_server %}, utilizando la herramienta de sincronización de acciones de {% data variables.product.prodname_codeql %} en [https://github.com/github/codeql-action-sync-tool](https://github.com/github/codeql-action-sync-tool/). Puedes utilizar esta herramienta sin importar si {% data variables.product.product_location %} o tus ejecutores de {% data variables.product.prodname_actions %} tienen acceso a internet, siempre y cuando puedas acceder tanto a {% data variables.product.product_location %} como a {% data variables.product.prodname_dotcom_the_website %} de forma simultánea en tu computadora. - Puedes crear una copia local del repositorio de una accion en tu servidor si clonas el repositorio de {% data variables.product.prodname_dotcom_the_website %} que contiene la acción. Por ejemplo, si quieres utilizar acciones para el {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %}, puedes crear un repositorio en tu instancia, el cual se llame `github/codeql-action`, y luego clonar el [repositorio](https://github.com/github/codeql-action) desde {% data variables.product.prodname_dotcom_the_website %} y posteriormente subir ese repositorio en el de `github/codeql-action` de tu instancia. También necesitarás descargar cualquiera de los lanzamientos del repositorio en {% data variables.product.prodname_dotcom_the_website %} y cargarlos en el repositorio de `github/codeql-action` de tu instancia como lanzamientos. {% endif %} ### Configurar {% data variables.product.prodname_github_connect %} para sincronizarse con {% data variables.product.prodname_actions %} -1. Si quieres descargar flujos de trabajo de acciones por petición desde {% data variables.product.prodname_dotcom_the_website %}, necesitarás habilitar {% data variables.product.prodname_github_connect %}. Para obtener más información, consulta la sección "[Habilitar {% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud#enabling-github-connect)". +1. Si quieres descargar flujos de trabajo de acciones por petición desde {% data variables.product.prodname_dotcom_the_website %}, necesitarás habilitar {% data variables.product.prodname_github_connect %}. Para obtener más información, consulta la sección "[Habilitar {% data variables.product.prodname_github_connect %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud#enabling-github-connect)". 2. También tendrás que habilitar {% data variables.product.prodname_actions %} para {% data variables.product.product_location %}. Para obtener más información, consulta la sección "[Iniciar con las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)". 3. El siguiente paso es configurar el acceso a las acciones en {% data variables.product.prodname_dotcom_the_website %} utilizando {% data variables.product.prodname_github_connect %}. Para obtener más información, consulta la sección "[Habilitar el acceso automático a las acciones de {% data variables.product.prodname_dotcom_the_website %} utilizando{% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". 4. Agrega un ejecutor auto-hospedado a tu repositorio, organización, o cuenta empresarial. Para obtener más información, consulta "[Agregar ejecutores autoalojados](/actions/hosting-your-own-runners/adding-self-hosted-runners)." diff --git a/translations/es-ES/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md b/translations/es-ES/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md index 5a12101d25..b089d9774d 100644 --- a/translations/es-ES/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md +++ b/translations/es-ES/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md @@ -27,7 +27,7 @@ topics: - Necesitas habilitar el marcador de CPU de las [SSSE3](https://www.intel.com/content/dam/www/public/us/en/documents/manuals/64-ia-32-architectures-optimization-manual.pdf#G3.1106470) (Extenciones SIMD de Streaming Suplementario 3, por sus siglas en inglés) en el VM/KVM que ejecuta {% data variables.product.product_location %}. -- A license for {% data variables.product.prodname_GH_advanced_security %}{% ifversion ghes > 3.0 %} (see "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)"){% endif %} +- Una licencia para {% data variables.product.prodname_GH_advanced_security %}{% ifversion ghes > 3.0 %} (consulta la sección "[Acerca de la facturación para {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)"){% endif %} - Eñ {% data variables.product.prodname_secret_scanning_caps %} habilitado en la consola de administración (consulta la sección "[Habilitar la {% data variables.product.prodname_GH_advanced_security %} para tu empresa](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)") @@ -50,11 +50,11 @@ Si no se devuelve un `0`, entonces no se ha habilitado las SSSE3 en tu VM/KVM. N {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} -1. Check if there is {% ifversion ghes < 3.2 %}an **{% data variables.product.prodname_advanced_security %}**{% else %}a **Security**{% endif %} entry in the left sidebar. +1. Verifica si hay una entrada {% ifversion ghes < 3.2 %}de **{% data variables.product.prodname_advanced_security %}**{% else %} de **Seguridad**{% endif %} en la barra lateral izquierda. {% ifversion ghes < 3.2 %} ![Barra lateral de seguridad avanzada](/assets/images/enterprise/management-console/sidebar-advanced-security.png) {% else %} - ![Security sidebar](/assets/images/enterprise/3.2/management-console/sidebar-security.png) + ![Barra lateral de seguridad](/assets/images/enterprise/3.2/management-console/sidebar-security.png) {% endif %} {% data reusables.enterprise_management_console.advanced-security-license %} @@ -66,7 +66,7 @@ Si no se devuelve un `0`, entonces no se ha habilitado las SSSE3 en tu VM/KVM. N {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.advanced-security-tab %} -1. Under "{% ifversion ghes < 3.2 %}{% data variables.product.prodname_advanced_security %}{% else %}Security{% endif %}," click **{% data variables.product.prodname_secret_scanning_caps %}**. ![Casilla para habilitar o inhabilitar el {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/enable-secret-scanning-checkbox.png) +1. Debajo de "{% ifversion ghes < 3.2 %}{% data variables.product.prodname_advanced_security %}{% else %} Seguridad{% endif %}", has clic en **{% data variables.product.prodname_secret_scanning_caps %}**. ![Casilla para habilitar o inhabilitar el {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/enable-secret-scanning-checkbox.png) {% data reusables.enterprise_management_console.save-settings %} ## Inhabilitar las {% data variables.product.prodname_secret_scanning %} @@ -76,5 +76,5 @@ Si no se devuelve un `0`, entonces no se ha habilitado las SSSE3 en tu VM/KVM. N {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.advanced-security-tab %} -1. Under "{% ifversion ghes < 3.2 %}{% data variables.product.prodname_advanced_security %}{% else %}Security{% endif %}," unselect **{% data variables.product.prodname_secret_scanning_caps %}**. ![Casilla para habilitar o inhabilitar el {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/secret-scanning-disable.png) +1. Debajo de "{% ifversion ghes < 3.2 %}{% data variables.product.prodname_advanced_security %}{% else %}Seguridad{% endif %}", deselecciona **{% data variables.product.prodname_secret_scanning_caps %}**. ![Casilla para habilitar o inhabilitar el {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/secret-scanning-disable.png) {% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/es-ES/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md b/translations/es-ES/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md index 7147846935..3735e8794d 100644 --- a/translations/es-ES/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md +++ b/translations/es-ES/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md @@ -26,14 +26,14 @@ Cuando habilitas la {% data variables.product.prodname_GH_advanced_security %} p ## Prerequisitos para habilitar la {% data variables.product.prodname_GH_advanced_security %} -1. Upgrade your license for {% data variables.product.product_name %} to include {% data variables.product.prodname_GH_advanced_security %}.{% ifversion ghes > 3.0 %} For information about licensing, see "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)."{% endif %} -2. Download the new license file. For more information, see "[Downloading your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)." -3. Upload the new license file to {% data variables.product.product_location %}. For more information, see "[Uploading a new license to {% data variables.product.prodname_ghe_server %}](/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)."{% ifversion ghes > 2.22 %} +1. Mejora tu licencia para que {% data variables.product.product_name %} incluya la {% data variables.product.prodname_GH_advanced_security %}.{% ifversion ghes > 3.0 %} Para obtener más información sobre el licenciamiento, consulta la sección "[Acerca de la facturación de {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)".{% endif %} +2. Descarga el archivo de licencia nuevo. Paa obtener más información, consulta la sección "[Descargar tu licencia para {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)". +3. Carga el archivo de licencia nuevo en {% data variables.product.product_location %}. Para obtener más información, consulta la sección "[Cargar una licencia nueva en {% data variables.product.prodname_ghe_server %}](/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)".{% ifversion ghes > 2.22 %} 4. Revisa los prerequisitos para las características que piensas habilitar. - {% data variables.product.prodname_code_scanning_capc %}, consulta la sección "[Configurar el {% data variables.product.prodname_code_scanning %} para tu aplicativo](/admin/advanced-security/configuring-code-scanning-for-your-appliance#prerequisites-for-code-scanning)". - {% data variables.product.prodname_secret_scanning_caps %}, consulta la sección "[Configurar el {% data variables.product.prodname_secret_scanning %} para tu aplicativo](/admin/advanced-security/configuring-secret-scanning-for-your-appliance#prerequisites-for-secret-scanning)".{% endif %} - - {% data variables.product.prodname_dependabot %}, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)." + - {% data variables.product.prodname_dependabot %}, consulta la sección "[Habilitar las alertas para las dependencia svulnerables en {% data variables.product.prodname_ghe_server %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)". ## Verificar si tu licencia incluye a la {% data variables.product.prodname_GH_advanced_security %} @@ -59,50 +59,57 @@ Cuando habilitas la {% data variables.product.prodname_GH_advanced_security %} p {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.advanced-security-tab %}{% ifversion ghes > 2.22 %} -1. Under "{% ifversion ghes < 3.2 %}{% data variables.product.prodname_advanced_security %}{% else %}Security{% endif %}," select the features that you want to enable and deselect any features you want to disable. ![Checkbox to enable or disable {% data variables.product.prodname_advanced_security %} features](/assets/images/enterprise/management-console/enable-advanced-security-checkboxes.png){% else %} +1. Debajo de "{% ifversion ghes < 3.2 %}{% data variables.product.prodname_advanced_security %}{% else %}Seguridad{% endif %}", selecciona las características que quieras habilitar y deselecciona cualquier característica que quieras inhabilitar. ![Checkbox to enable or disable {% data variables.product.prodname_advanced_security %} features](/assets/images/enterprise/management-console/enable-advanced-security-checkboxes.png){% else %} 1. Debajo de "{% data variables.product.prodname_advanced_security %}", da clic en **{% data variables.product.prodname_code_scanning_capc %}**. ![Checkbox to enable or disable {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/management-console/enable-code-scanning-checkbox.png){% endif %} {% data reusables.enterprise_management_console.save-settings %} Cuando {% data variables.product.product_name %} termina de reiniciarse, estás listo para configurar cualquier recurso adicional que se requiera para las características recién habilitadas. Para obtener más información, consulta "[Configurar el {% data variables.product.prodname_code_scanning %} en tu aplicativo](/admin/advanced-security/configuring-code-scanning-for-your-appliance)." -## Enabling or disabling {% data variables.product.prodname_GH_advanced_security %} features via the administrative shell (SSH) +## Habilitar o inhabilitar las características de la {% data variables.product.prodname_GH_advanced_security %} a través del shell administrativo (SSH) Puedes habilitar o inhabilitar las características mediante programación en {% data variables.product.product_location %}. Para obtener más información acerca de las utilidades del shell administrativo y de la línea de comandos para {% data variables.product.prodname_ghe_server %}, consulta las secciones "[Acceder al shell administrativo (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" y "[Utilidades de la línea de comandos](/admin/configuration/command-line-utilities#ghe-config)". -For example, you can enable any {% data variables.product.prodname_GH_advanced_security %} feature with your infrastructure-as-code tooling when you deploy an instance for staging or disaster recovery. +Por ejemplo, puedes habilitar cualquier característica de {% data variables.product.prodname_GH_advanced_security %} con tus herramientas de infraestructura-como-código cuando despliegas una instancia para hacer pruebas o para recuperación de desastres. 1. SSH en {% data variables.product.product_location %}. -1. Enable features for {% data variables.product.prodname_GH_advanced_security %}. +1. Habilita las características de {% data variables.product.prodname_GH_advanced_security %}. - - To enable {% data variables.product.prodname_code_scanning_capc %}, enter the following commands. + - Para habilitar el {% data variables.product.prodname_code_scanning_capc %}, ingresa los siguientes comandos. ```shell ghe-config app.minio.enabled true ghe-config app.code-scanning.enabled true ``` - - To enable {% data variables.product.prodname_secret_scanning_caps %}, enter the following command. + - Para habilitar el {% data variables.product.prodname_secret_scanning_caps %}, ingresa el siguiente comando. ```shell ghe-config app.secret-scanning.enabled true ``` - - To enable {% data variables.product.prodname_dependabot %}, enter the following command. - ```shell - {% ifversion ghes > 3.1 %}ghe-config app.dependency-graph.enabled true{% else %}ghe-config app.github.dependency-graph-enabled true{% endif %} + - Para habilitar el {% data variables.product.prodname_dependabot %}, ingresa el siguiente {% ifversion ghes > 3.1 %}comando{% else %}comandos{% endif %}. + {% ifversion ghes > 3.1 %}```shell + ghe-config app.dependency-graph.enabled true ``` -2. Optionally, disable features for {% data variables.product.prodname_GH_advanced_security %}. + {% else %}```shell + ghe-config app.github.dependency-graph-enabled true + ghe-config app.github.vulnerability-alerting-and-settings-enabled true + ```{% endif %} +2. Opcionalmente, inhabilita las características de {% data variables.product.prodname_GH_advanced_security %}. - - To disable {% data variables.product.prodname_code_scanning %}, enter the following commands. + - Para inhabilitar el {% data variables.product.prodname_code_scanning %}, ingresa los siguientes comandos. ```shell ghe-config app.minio.enabled false ghe-config app.code-scanning.enabled false ``` - - To disable {% data variables.product.prodname_secret_scanning %}, enter the following command. + - Para inhabilitar el {% data variables.product.prodname_secret_scanning %}, ingresa el siguiente comando. ```shell ghe-config app.secret-scanning.enabled false ``` - - To disable {% data variables.product.prodname_dependabot %}, enter the following command. - ```shell - {% ifversion ghes > 3.1 %}ghe-config app.dependency-graph.enabled false{% else %}ghe-config app.github.dependency-graph-enabled false{% endif %} + - Para inhabilitar el {% data variables.product.prodname_dependabot %}, ingresa el siguiente {% ifversion ghes > 3.1 %}comando{% else %}comandos{% endif %}. + {% ifversion ghes > 3.1 %}```shell + ghe-config app.dependency-graph.enabled false ``` - + {% else %}```shell + ghe-config app.github.dependency-graph-enabled false + ghe-config app.github.vulnerability-alerting-and-settings-enabled false + ```{% endif %} 3. Aplica la configuración ```shell ghe-config-apply diff --git a/translations/es-ES/content/admin/advanced-security/viewing-your-github-advanced-security-usage.md b/translations/es-ES/content/admin/advanced-security/viewing-your-github-advanced-security-usage.md index 90215caa6f..407f127904 100644 --- a/translations/es-ES/content/admin/advanced-security/viewing-your-github-advanced-security-usage.md +++ b/translations/es-ES/content/admin/advanced-security/viewing-your-github-advanced-security-usage.md @@ -10,7 +10,7 @@ topics: shortTitle: Visualizar el uso de la Seguridad Avanzada --- -## About licenses for {% data variables.product.prodname_GH_advanced_security %} +## Acerca de las licencias para {% data variables.product.prodname_GH_advanced_security %} {% data reusables.advanced-security.about-ghas-license-seats %} Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)". diff --git a/translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/allowing-built-in-authentication-for-users-outside-your-identity-provider.md b/translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/allowing-built-in-authentication-for-users-outside-your-identity-provider.md index ff1a1a8fc4..6fbd571516 100644 --- a/translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/allowing-built-in-authentication-for-users-outside-your-identity-provider.md +++ b/translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/allowing-built-in-authentication-for-users-outside-your-identity-provider.md @@ -13,7 +13,7 @@ topics: - Authentication - Enterprise - Identity -shortTitle: Authentication outside IdP +shortTitle: Autenticación fuera del IdP --- ## Acerca de la autenticación integrada para usuarios fuera de tu proveedor de identidad diff --git a/translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-built-in-authentication.md b/translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-built-in-authentication.md index 38b73bad9e..8d37568ec3 100644 --- a/translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-built-in-authentication.md +++ b/translations/es-ES/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-built-in-authentication.md @@ -28,14 +28,14 @@ Puedes crear mensajes personalizados que los usuarios verán en las páginas de {% data reusables.enterprise_user_management.two_factor_auth_header %} {% data reusables.enterprise_user_management.2fa_is_available %} -## Creating your account +## Crear tu cuenta -Once your instance has been created, you'll need to create your own admin account. +Una vez que se ha creado tu instancia, necesitarás crear tu propia cuenta de administrador. 1. En la página "Crear cuenta de administrador " en `http(s)://[hostname]/join`, elige tu nombre de usuario, contraseña y dirección de correo electrónico, luego haz clic en **Crear una cuenta**. ![Crear cuenta de administrador](/assets/images/enterprise/site-admin-settings/create-first-admin-acct.png) {% data reusables.enterprise_site_admin_settings.sign-in %} -## Inviting users +## Invitar usuarios {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.invite-user-sidebar-tab %} @@ -43,10 +43,10 @@ Once your instance has been created, you'll need to create your own admin accoun {% tip %} -**Tip:** If email for notifications is configured on the appliance, an invite will also be sent to the provided email address. +**Tip:** Si el correo electrónico para notificaciones se configura en el aplicativo, también se enviará una invitación a la dirección de correo electrónico proporcionada. {% endtip %} ## Leer más -- "[Configuring email for notifications](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications)" +- "[Configurar el correo electrónico para notificaciones](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications)" diff --git a/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md b/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md index 46130515ef..dbebc7a071 100644 --- a/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md +++ b/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md @@ -17,24 +17,24 @@ topics: shortTitle: Configurar un proxy saliente --- -## About proxies with {% data variables.product.product_name %} +## Acerca de los proxies con {% data variables.product.product_name %} Cuando se habilita un servidor proxy para {% data variables.product.product_location %}, primero {% data variables.product.prodname_ghe_server %} envía mensajes fuera de banda a través del servidor proxy, a menos que el host de destino se agregue como una exclusión de servidor proxy HTTP. Los tipos de mensajes fuera de banda incluyen webhooks salientes, carga de paquetes y extracción de avatares heredados. La URL del servidor proxy es el protocolo, dominio o dirección IP más el número de puerto, por ejemplo `http://127.0.0.1:8123`. {% note %} -**Nota:** Para conectarte a {% data variables.product.product_location %} para {% data variables.product.prodname_dotcom_the_website %}, tu configuración proxy debe permitir la conectividad a `github.com` y a `api.github.com`. Para obtener más información, consulta "[Conectarse a {% data variables.product.prodname_ghe_server %} para {% data variables.product.prodname_dotcom_the_website %}](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/connecting-github-enterprise-server-to-github-com)." +**Nota:** Para conectarte a {% data variables.product.product_location %} para {% data variables.product.prodname_dotcom_the_website %}, tu configuración proxy debe permitir la conectividad a `github.com` y a `api.github.com`. Para obtener más información, consulta la sección "[Conectar tu cuenta empresarial a {% data variables.product.prodname_dotcom_the_website %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)". {% endnote %} -{% data reusables.actions.proxy-considerations %} For more information about using {% data variables.product.prodname_actions %} with {% data variables.product.prodname_ghe_server %}, 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)." +{% data reusables.actions.proxy-considerations %} Para obtener más información sobre cómo utilizar las {% data variables.product.prodname_actions %} con {% data variables.product.prodname_ghe_server %}, consulta la sección "[Iniciar con {% data variables.product.prodname_actions %} para {% 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)". ## Configurar un servidor proxy web fuera de banda {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.privacy %} -4. En **Servidor proxy HTTP**, escribe la URL de tu servidor proxy. ![Campo para escribir la URL del servidor proxy HTTP](/assets/images/enterprise/management-console/http-proxy-field.png) +1. En **Servidor proxy HTTP**, escribe la URL de tu servidor proxy. ![Campo para escribir la URL del servidor proxy HTTP](/assets/images/enterprise/management-console/http-proxy-field.png) 5. De manera opcional, en **Exclusión de servidor proxy HTTP**, escribe cualquier host que no exija acceso proxy, separando los hosts con comas. Para excluir a todos los hosts en un dominio de que requieran acceso por proxy, puedes utilizar `.` como un prefijo de comodín. Por ejemplo: `.octo-org.tentacle` ![Campo para escribir cualquier Exclusión de Proxy HTTP](/assets/images/enterprise/management-console/http-proxy-exclusion-field.png) diff --git a/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md b/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md index d15c2b909d..cd9b0dd0ca 100644 --- a/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md +++ b/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md @@ -36,7 +36,7 @@ Los servidores de nombres que especifiques deben resolver el nombre del host de ``` 3. Agrega cualquier entrada de `nameserver` (servidor de nombres) y luego guarda el archivo. 4. Después de verificar tus cambios, guarda el archivo. -5. To add your new nameserver entries to {% data variables.product.product_location %}, run the following: +5. Para agregar tus entradas nuevas de servidores de nombres en {% data variables.product.product_location %}, ejecuta lo siguiente: ```shell $ sudo service resolvconf restart $ sudo service dnsmasq restart diff --git a/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-tls.md b/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-tls.md index 9e87d315f1..8c79773226 100644 --- a/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-tls.md +++ b/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-tls.md @@ -75,5 +75,5 @@ También puedes usar la utilidad de la línea de comando `ghe-ssl-acme` en {% da {% data reusables.enterprise_management_console.save-settings %} {% data reusables.enterprise_management_console.privacy %} 7. Haz clic en **Request TLS certificate** (Solicitar certificado TLS). ![Botón para solicitar certificado TLS](/assets/images/enterprise/management-console/request-tls-button.png) -8. Wait for the "Status" to change from "STARTED" to "DONE". ![Let's Encrypt status](/assets/images/enterprise/management-console/lets-encrypt-status.png) +8. Espera para que el "Estado" cambie de "INICIADO" a "HECHO". ![Estado de "vamos a cifrar"](/assets/images/enterprise/management-console/lets-encrypt-status.png) 9. Haz clic en **Save configuration** (Guardar configuración). diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md index ab443ac8df..1d8247b490 100644 --- a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md +++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md @@ -35,7 +35,7 @@ Para acceder a {% data variables.enterprise.management_console %}, debes utiliza ## Acceder a la {% data variables.enterprise.management_console %} como administrador del sitio -La primera vez que accedas a la {% data variables.enterprise.management_console %} como administrador de sitio, deberás cargar tu archivo de licencia de {% data variables.product.prodname_enterprise %} para autenticarte en la app. For more information, see "[Managing your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise)." +La primera vez que accedas a la {% data variables.enterprise.management_console %} como administrador de sitio, deberás cargar tu archivo de licencia de {% data variables.product.prodname_enterprise %} para autenticarte en la app. Paa obtener más información, consulta la sección "[Administrar tu licencia de {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise)". {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} 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 3421cd0364..25e803fdcc 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 @@ -44,14 +44,14 @@ $ ghe-announce -u Esta utilidad muestra información sobre los trabajos en segundo plano, tanto activos como en cola. Proporciona las mismas cantidades de recuento de trabajos que la barra de estado del administrador que aparece en la parte superior de cada página. -This utility can help identify whether the Aqueduct server is having problems processing background jobs. Any of the following scenarios might be indicative of a problem with Aqueduct: +Esta utilidad puede ayudarte a identificar si el servidor de Aqueduct está teniendo problemas para procesar jobs en segundo plano. Cualquiera de los siguientes casos puede indicar un problema con Aqueduct: * Aumenta la cantidad de trabajos de segundo plano, pero los trabajos activos siguen siendo los mismos. * Las fuentes de eventos no se actualizan. * Los webhooks no se están activando. * La interfaz web no se actualiza después de una subida de Git. -If you suspect Aqueduct is failing, contact {% data variables.contact.contact_ent_support %} for help. +Si sospechas que Aqueduct está fallando, contacta a {% data variables.contact.contact_ent_support %} para obtener ayuda. Con este comando, también puedes detener o reanudar los trabajos en cola. @@ -351,18 +351,6 @@ stop/waiting - ghe-replica-mode ``` -{% tip %} - -Los nombres de servicio que se generen con este comando se pueden utilizar con comandos [`systemctl`](https://www.freedesktop.org/software/systemd/man/systemctl.html) para detener, iniciar o restablecer estos servicios manualmente si así se requiere. Por ejemplo: - -```shell -$ sudo systemctl restart github-resqued -``` - -Detener los servicios generará un tiempo de inactividad en tu instalación, así que recomendamos que te contactes con {% data variables.contact.contact_ent_support %} antes de detener o reiniciar cualquier servicio. - -{% endtip %} - ### ghe-set-password Con `ghe-set-password`, puedes establecer una contraseña nueva para autenticarla en la [{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-management-console). @@ -808,7 +796,7 @@ $ ssh -p 122 admin@hostname -- 'ghe-update-check' ### ghe-license-usage -Esta utilidad exporta una lista de los usuarios de la instalación en formato JSON. Si tu instancia se conecta a {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %} utiliza esta información para reportar la información de licencia a {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta la sección "[Conectar {% data variables.product.prodname_ghe_server %} a{% data variables.product.prodname_ghe_cloud %}](/enterprise/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)". +Esta utilidad exporta una lista de los usuarios de la instalación en formato JSON. Si tu instancia se conecta a {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %} utiliza esta información para reportar la información de licencia a {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta la sección "[Conectar tu cuenta empresarial a {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)". Predeterminadamente, la lista de usuarios en el JSON resultante se encuentra cifrada. Usa la marca `-h` para obtener más opciones. diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md index 8d5e581ec2..718b418818 100644 --- a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md +++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md @@ -68,7 +68,7 @@ Es posible que se requieran más recursos según su uso, como la actividad del u {% note %} - **Note:** If your {% data variables.product.product_location %} is deployed as a cluster or in a high availability configuration using a load balancer, the `GHE_HOSTNAME` can be the load balancer hostname, as long as it allows SSH access (on port 122) to {% data variables.product.product_location %}. + **Nota:** Si tu {% data variables.product.product_location %} se despliega como un clúster o en una configuración de disponibilidad alta utilizando un balanceador de carga, el `GHE_HOSTNAME` puede ser el nombre de host del balanceador de carga siempre y cuando permita acceso por SSH a {% data variables.product.product_location %} (por el puerto 122). {% endnote %} @@ -105,9 +105,9 @@ En el caso de una interrupción de red prolongada o de un evento catastrófico e {% note %} -**Note:** When performing backup restores to {% data variables.product.product_location %}, the same version supportability rules apply. You can only restore data from at most two feature releases behind. +**Nota:** Cuando realizas restauraciones de respaldo hacia {% data variables.product.product_location %} aplicarán las mismas reglas de compatibilidad de versión. Solo puedes restablecer datos de por lo mucho dos lanzamientos de características anteriores. -For example, if you take a backup from GHES 3.0.x, you can restore it into a GHES 3.2.x instance. But, you cannot restore data from a backup of GHES 2.22.x onto 3.2.x, because that would be three jumps between versions (2.22 > 3.0 > 3.1 > 3.2). You would first need to restore onto a 3.1.x instance, and then upgrade to 3.2.x. +Por ejemplo, si tomas un respaldo de GHES 3.0.x, puedes restablecerlo a la instancia GHES 3.2.x. Pero no puedes restablecer datos desde un respaldo de GHES 2.22.x hacia 3.2.x, ya que esto sería tres saltos entre versiones (2.22 > 3.0 > 3.1 > 3.2). Primero necesitarías restablecer a una instancia 3.1.x y luego mejorar a una 3.2.x. {% endnote %} diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md index 3fd343501e..7290826ff2 100644 --- a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md +++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md @@ -30,18 +30,18 @@ Puedes eximir a una lista de usuarios para que no tomen los límites de tasa de {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} -2. Under "Rate Limiting", select **Enable HTTP API Rate Limiting**. ![Casilla para habilitar la limitación de tasa de API](/assets/images/enterprise/management-console/api-rate-limits-checkbox.png) +2. Debajo de "Límite de tasa", selecciona **Habilitar los límites de tasa de la API HTTP**. ![Casilla para habilitar la limitación de tasa de API](/assets/images/enterprise/management-console/api-rate-limits-checkbox.png) 3. Escribe los límites para las solicitudes autenticadas y no autenticadas para cada API o acepta los límites predeterminados que aparecen completados. {% data reusables.enterprise_management_console.save-settings %} -## Enabling secondary rate limits +## Habilitar los límites de tasa secundarios -Setting secondary rate limits protects the overall level of service on {% data variables.product.product_location %}. +El configurar los límites de tasa secundarios protegen el nivel general de servicio en {% data variables.product.product_location %}. {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% ifversion ghes > 3.1 %} -2. Under "Rate Limiting", select **Enable Secondary Rate Limiting**. ![Checkbox for enabling secondary rate limiting](/assets/images/enterprise/management-console/secondary-rate-limits-checkbox.png) +2. Debajo de "Limitación de tasa", selecciona **Habilitar la limitación de tasa secundaria**. ![Casilla para habilitar la limitación de tasa secundaria](/assets/images/enterprise/management-console/secondary-rate-limits-checkbox.png) {% else %} 2. En "Limitación de tasa", selecciona **Enable Abuse Rate Limiting** (Habilitar limitación de tasa de abuso). ![Casilla para habilitar la limitación de tasa de abuso](/assets/images/enterprise/management-console/abuse-rate-limits-checkbox.png) {% endif %} diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md index 382f9686b6..d089713c64 100644 --- a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md +++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md @@ -1,7 +1,7 @@ --- -title: Configuring the referrer policy for your enterprise -shortTitle: Configure referrer policy -intro: 'You can increase the privacy of {% data variables.product.product_location %} by configuring the policy for cross-origin requests.' +title: Configurar la política de referente para tu empresa +shortTitle: Configurar la política de referente +intro: 'Puedes incrementar la privacidad de {% data variables.product.product_location %} si configuras la política para las solicitudes de origen cruzado.' versions: ghes: '>=3.2' type: how_to @@ -12,25 +12,25 @@ topics: - Security --- -## About the referrer policy for your enterprise +## Acerca de la política de referente para tu empresa -The referrer policy controls the information that {% data variables.product.product_name %} transmits in HTTP headers when someone visits a link from {% data variables.product.product_location %} to an external site. +La política de referente controla la información que transmite {% data variables.product.product_name %} en los encabezados HTTP cuando alguien visita un enlace de {% data variables.product.product_location %} a un sitio externo. -By default, when a user on {% data variables.product.product_location %} visits a link to another site from a file or comment on your instance, the request includes the hostname for your instance in plain text within the `Referer` header. If the link leads to an external website, the owner of the website could read the hostname for your instance in requests or log files. +Predeterminadamente, cuando un usuario en {% data variables.product.product_location %} visita un enlace a otro sitio desde el archivo o comentario en tu instancia, la solicitud incluye el nombre de host de tu instancia en texto simple dentro del encabezado `Referer`. Si el enlace lleva a un sitio web externo, el propietario de este podría leer el nombre de host de tu instancia en los archivos de bitácora o en las solicitudes. -You can control the information that {% data variables.product.product_name %} sends when a user visits a link from your instance. +Puedes controlar la información que envía {% data variables.product.product_name %} cuando un usuario visita un enlace de tu instancia. -## Enabling the `same-origin` referrer policy +## Habilita la política de referente de `same-origin` -You can enable the `same-origin` referrer policy to instruct modern browsers to exclude the hostname for {% data variables.product.product_location %} from requests to external websites. The setting applies to all links from the web interface on your instance. By default, {% data variables.product.product_name %} uses the `origin-when-cross-origin` and `strict-origin-when-cross-origin` referrer policies, which means your instance's hostname will appear in HTTP and HTTPS requests to external websites. +Puedes habilitar la política de referente de `same-origin` para instruir a los buscadores modernos para que excluyan el nombre de host de {% data variables.product.product_location %} de las solicitudes a los sitios web externos. El ajuste aplica a todos los enlaces de la interfaz web en tu instancia. Predeterminadamente, {% data variables.product.product_name %} utiliza las políticas de referente `origin-when-cross-origin` y `strict-origin-when-cross-origin`, lo cual significa que el nombre de host de tu instancia aparecerá en solicitudes HTTP y HTTPS hacia sitios web externos. {% note %} -**Note**: Changing the referrer policy to `same-origin` can affect external sites that expect a hostname in the HTTP headers for a request. +**Nota**: El cambiar la política de referente a `same-origin` puede afectar los sitios externos que esperan un nombre de host en los encabezados HTTP para una solicitud. {% endnote %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} -1. Under "User Agent Referrer Policy", select **Enable same origin referrer policy for all organizations**. ![Checkbox for enabling same origin referrer policy](/assets/images/enterprise/settings/referrer-policy-checkbox.png) -1. Haz clic en **Save ** (guardar). ![Save button for enabling same origin referrer policy](/assets/images/enterprise/settings/referrer-policy-save-button.png) +1. Debajo de "Política de Referente del Agente Usuario", selecciona **Habilitar la misma política de referente origen para todas las organizaciones**. ![Casilla de verificación para habilitar la misma política de referente origen](/assets/images/enterprise/settings/referrer-policy-checkbox.png) +1. Haz clic en **Save ** (guardar). ![Botón de guardar para habilitar la política de referente del mismo origen](/assets/images/enterprise/settings/referrer-policy-save-button.png) diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md index ad4c528e51..d11cce6a5d 100644 --- a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md +++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md @@ -14,7 +14,7 @@ redirect_from: Antes de que puedas inicializar tue mpresa, debes comprar {% data variables.product.product_name %}. Para obtener más información, contacta a {% data variables.contact.contact_enterprise_sales %}. -{% data reusables.github-ae.initialize-enterprise %} Make sure the information you provide matches the intended enterprise owner's information in the IdP. Para obtener más información acerca de los propietarios de las empresas, consulta la sección "[Roles en una empresa](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise#enterprise-owner)". +{% data reusables.github-ae.initialize-enterprise %} Asegúrate de que la información que proporcionas empate con la información destinada del propietario de la empresa en el IdP. Para obtener más información acerca de los propietarios de las empresas, consulta la sección "[Roles en una empresa](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise#enterprise-owner)". {% note %} diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md index d2c7296e97..41716009ec 100644 --- a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md +++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md @@ -165,11 +165,11 @@ Esto controla de qué manera se repara el [índice de propuestas][]. Puedes - comenzar una nueva tarea de reparación de índice - restablecer todos los estados de reparación de índices {% endif %} -## Reserved logins +## Inicios de sesión reservados -Certain words are reserved for internal use in {% data variables.product.product_location %}, which means that these words cannot be used as usernames. +Algunas palabras se reservan para uso interno en {% data variables.product.product_location %}, lo cual significa que estas no pueden utilizarse como nombres de usuario. -For example, the following words are reserved, among others: +Por ejemplo, las siguientes palabras, entre otras, son reservadas: - `admin` - `empresa` @@ -177,7 +177,7 @@ For example, the following words are reserved, among others: - `staff` - `asistencia` -For the full list or reserved words, navigate to "Reserved logins" in the site admin dashboard. +Para una lista completa de palabras reservadas, navega a la sección de "Inicios de sesión reservados" en el tablero de administrador de sitio. {% ifversion ghes or ghae %} @@ -197,7 +197,7 @@ Es una lista de los repositorios en {% data variables.product.product_location % ## Todos los usuarios -Here you can see all of the users on {% data variables.product.product_location %}, and [initiate an SSH key audit](/enterprise/{{ currentVersion }}/admin/guides/user-management/auditing-ssh-keys). +Aquí puedes ver a todos los usuarios en {% data variables.product.product_location %} e [iniciar una auditoría de llaves de SSH](/enterprise/{{ currentVersion }}/admin/guides/user-management/auditing-ssh-keys). ## Administrador del sitio @@ -208,7 +208,7 @@ Aquí puedes ver todos los administradores en {% data variables.product.product_ Aquí puedes ver y [suspender](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users) todos los usuarios inactivos en {% data variables.product.product_location %}. Una cuenta de usuario se considera inactiva ("dormant") cuando: {% endif %} {% ifversion ghae %} -Here you can see and suspend all of the inactive users on {% data variables.product.product_location %}. Una cuenta de usuario se considera inactiva ("dormant") cuando: +Aquí puedes ver y suspender a todos los usuarios inactivos en {% data variables.product.product_location %}. Una cuenta de usuario se considera inactiva ("dormant") cuando: {% endif %} - Ha existido durante más tiempo del umbral de inactividad que está establecido para {% data variables.product.product_location %}. diff --git a/translations/es-ES/content/admin/configuration/index.md b/translations/es-ES/content/admin/configuration/index.md index 1a330de9ea..83fc05dca9 100644 --- a/translations/es-ES/content/admin/configuration/index.md +++ b/translations/es-ES/content/admin/configuration/index.md @@ -12,7 +12,7 @@ topics: children: - /configuring-your-enterprise - /configuring-network-settings - - /managing-connections-between-github-enterprise-server-and-github-enterprise-cloud + - /managing-connections-between-your-enterprise-accounts --- {% ifversion ghes %} diff --git a/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md b/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md new file mode 100644 index 0000000000..f9b05d37c1 --- /dev/null +++ b/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md @@ -0,0 +1,83 @@ +--- +title: Connecting your enterprise account to GitHub Enterprise Cloud +shortTitle: Connect enterprise accounts +intro: 'Después de que habilites {% data variables.product.prodname_github_connect %}, puedes compartir características y flujos de trabajo específicos entre {% data variables.product.product_location %} y {% data variables.product.prodname_ghe_cloud %}.' +redirect_from: + - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-to-github-com/ + - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-server-to-github-com + - /enterprise/admin/developer-workflow/connecting-github-enterprise-server-to-githubcom/ + - /enterprise/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud + - /enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud + - /admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud +permissions: 'Enterprise owners who are also owners of a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable {% data variables.product.prodname_github_connect %}.' +versions: + ghes: '*' + ghae: next +type: how_to +topics: + - Enterprise + - GitHub Connect + - Infrastructure + - Networking +--- + +{% data reusables.github-connect.beta %} + +## Acerca de {% data variables.product.prodname_github_connect %} + +Para habilitar {% data variables.product.prodname_github_connect %}, debes configurar la conexión en ambos {% data variables.product.product_location %} y en tu cuenta de empresa u organización de {% data variables.product.prodname_ghe_cloud %}. + +{% ifversion ghes %} +Para configurar una conexión, tu configuración proxy debe permitir la conectividad a `github.com` y `api.github.com`. Para obtener más información, consulta "[Configuring an outbound web proxy server](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-an-outbound-web-proxy-server)." +{% endif %} + +Después de habilitar {% data variables.product.prodname_github_connect %}, podrás habilitar características, como búsqueda unificada y contribuciones unificadas. For more information about all of the features available, see "[Managing connections between your enterprise accounts](/admin/configuration/managing-connections-between-your-enterprise-accounts)." + +Cuando conectas {% data variables.product.product_location %} a {% data variables.product.prodname_ghe_cloud %}, un registro en {% data variables.product.prodname_dotcom_the_website %} almacena información sobre la conexión: +{% ifversion ghes %} +- La parte pública de la clave de tu licencia {% data variables.product.prodname_ghe_server %} +- Un hash de tu licencia {% data variables.product.prodname_ghe_server %} +- El nombre personalizado de tu licencia {% data variables.product.prodname_ghe_server %} +- The version of {% data variables.product.product_location_enterprise %}{% endif %} +- The hostname of your {% data variables.product.product_name %} instance +- La cuenta de empresa u organización en {% data variables.product.prodname_dotcom_the_website %} está conectada a {% data variables.product.product_location %} +- El token de autenticación que usa {% data variables.product.product_location %} para hacerle solicitudes a {% data variables.product.prodname_dotcom_the_website %} + +Habilitar {% data variables.product.prodname_github_connect %} también crea un {% data variables.product.prodname_github_app %} cuyo dueño es la cuenta empresarial u organizacional de {% data variables.product.prodname_ghe_cloud %}. {% data variables.product.product_name %} usa las credenciales de {% data variables.product.prodname_github_app %} para hacerle solicitudes a {% data variables.product.prodname_dotcom_the_website %}. +{% ifversion ghes %} +{% data variables.product.prodname_ghe_server %} almacena credenciales desde la {% data variables.product.prodname_github_app %}. Estas credenciales se replicarán en cualquier entorno de alta disponibilidad o de agrupación y se almacenarán en cualquier copia de seguridad, incluidas las instantáneas creadas por {% data variables.product.prodname_enterprise_backup_utilities %}. +- Un token de autenticación, que es válido durante una hora +- Una clave privada, que se utiliza para generar un nuevo token de autenticación +{% endif %} + +Habilitar {% data variables.product.prodname_github_connect %} no permitirá {% data variables.product.prodname_dotcom_the_website %} que los usuarios hagan cambios en {% data variables.product.product_name %}. + +Para obtener más información acerca de cómo administrar las cuentas empresariales utilizando la API de GraphQL, consulta la sección "[Cuentas empresariales](/graphql/guides/managing-enterprise-accounts)". +## Habilitar {% data variables.product.prodname_github_connect %} + +{% ifversion ghes %} +1. Iniciar sesión en {% data variables.product.product_location %} y {% data variables.product.prodname_dotcom_the_website %}. +{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %}{% else %} +1. Iniciar sesión en {% data variables.product.product_location %} y {% data variables.product.prodname_dotcom_the_website %}. +{% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %} +1. En "{% data variables.product.prodname_github_connect %} aún no está habilitado", haz clic en **Enable {% data variables.product.prodname_github_connect %}** (Habilitar). By clicking **Enable {% data variables.product.prodname_github_connect %}**, you agree to the "{% data variables.product.prodname_dotcom %} Terms for Additional Products and Features." +{% ifversion ghes %} +![Enable GitHub Connect button](/assets/images/enterprise/business-accounts/enable-github-connect-button.png){% else %} +![Enable GitHub Connect button](/assets/images/enterprise/github-ae/enable-github-connect-button.png) +{% endif %} +1. Al lado de la cuenta de usuario u organización a la que quieres conectarte, haz clic en **Connect** (Conectar). ![Conecta el botón junto a una cuenta de empresa o negocio](/assets/images/enterprise/business-accounts/choose-enterprise-or-org-connect.png) + +## Disconnecting a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account from your enterprise account + +Cuando te desconectas de {% data variables.product.prodname_ghe_cloud %}, se elimina la {% data variables.product.prodname_github_connect %} {% data variables.product.prodname_github_app %} de tu cuenta de empresa u organización, y las credenciales almacenadas en {% data variables.product.product_location %} se eliminan. + +{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %} +1. Al lado de la cuenta de empresa u organización de la que te quieres desconectar, haz clic en **Disable {% data variables.product.prodname_github_connect %}** (Inhabilitar {% data variables.product.prodname_github_connect %}). +{% ifversion ghes %} + ![Inhabilitar el botón Conectar de GitHub para una cuenta de empresa o nombre de organización](/assets/images/enterprise/business-accounts/disable-github-connect-button.png) +1. Lee la información acerca de la desconexión y haz clic en **Disable {% data variables.product.prodname_github_connect %}** (Inhabilitar {% data variables.product.prodname_github_connect %}). ![Modal con información de advertencia acerca de la desconexión y el botón de confirmación](/assets/images/enterprise/business-accounts/confirm-disable-github-connect.png) +{% else %} + ![Inhabilitar el botón Conectar de GitHub para una cuenta de empresa o nombre de organización](/assets/images/enterprise/github-ae/disable-github-connect-button.png) +1. Lee la información acerca de la desconexión y haz clic en **Disable {% data variables.product.prodname_github_connect %}** (Inhabilitar {% data variables.product.prodname_github_connect %}). ![Modal con información de advertencia acerca de la desconexión y el botón de confirmación](/assets/images/enterprise/github-ae/confirm-disable-github-connect.png) +{% endif %} diff --git a/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md b/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md new file mode 100644 index 0000000000..4b03182298 --- /dev/null +++ b/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md @@ -0,0 +1,97 @@ +--- +title: Habilitar las alertas para las dependencias vulnerables en GitHub Enterprise Server +intro: 'Puedes conectar a {% data variables.product.product_location %} con {% data variables.product.prodname_ghe_cloud %} y habilitar la gráfica de dependencias y el {% ifversion ghes %}{% data variables.product.prodname_dependabot %}{% else %}alertas de seguridad{% endif %} en los repositorios de tu instancia.' +shortTitle: Habilitar las alertas para las dependencias +miniTocMaxHeadingLevel: 3 +redirect_from: + - /enterprise/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /enterprise/admin/configuration/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /enterprise/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server +permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable the dependency graph and {% data variables.product.prodname_dependabot %} alerts on {% data variables.product.prodname_ghe_server %}.' +versions: + ghes: '*' +type: how_to +topics: + - Enterprise + - Security + - Dependency graph + - Dependabot +--- + +## Acerca de las alertas para las dependencias vulnerables en {% data variables.product.prodname_ghe_server %} + +Para identificar las dependencias vulnerables en tu repositorio y recibir alertas sobre las vulnerabilidades, necesitas habilitar dos características de seguridad: +- La gráfica de dependencias +- Las alertas del {% data variables.product.prodname_dependabot %} + +Para obtener más información, consulta las secciones "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" y "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)". + +{% data reusables.repositories.tracks-vulnerabilities %} + +Puedes conectar a {% data variables.product.product_location %} a {% data variables.product.prodname_dotcom_the_website %} y luego sincronizar los datos de vulnerabilidades a tu instancia y generar {% data variables.product.prodname_dependabot_alerts %} en los repositorios con dependencias vulnerables. + +Después de conectar {% data variables.product.product_location %}a {% data variables.product.prodname_dotcom_the_website %} y habilitar la gráfica de dependencias y las {% data variables.product.prodname_dependabot_alerts %} para las dependencias vulnerables, los datos de vulnerabilidad se sincronizan desde {% data variables.product.prodname_dotcom_the_website %} a tu instancia una vez cada hora. También puedes elegir sincronizar manualmente los datos de vulnerabilidad en cualquier momento. No se han cargado códigos o información sobre el código desde {% data variables.product.product_location %} hasta {% data variables.product.prodname_dotcom_the_website %}. + +Cuando {% data variables.product.product_location %} recibe información sobre una vulnerabilidad, identificará los repositorios en tu instancia que utilicen la versión afectada de la dependencia y generará {% data variables.product.prodname_dependabot_alerts %}. Puedes personalizar la forma en la que recibes las {% data variables.product.prodname_dependabot_alerts %}. Para obtener más información, consulta la sección "[Configurar notificaciones para las dependencias vulnerables](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies/#configuring-notifications-for-dependabot-alerts)". + +Before enabling the dependency graph and {% ifversion ghes > 2.21 %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts for vulnerable dependencies on {% data variables.product.product_location %}, you must connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." + +## Habilitar la gráfica de dependencias y las {% data variables.product.prodname_dependabot_alerts %} en GitHub Enterprise Server + +Para que {% data variables.product.product_location %} genere {% data variables.product.prodname_dependabot_alerts %} cada que las vulnerabilidades se detecten en tus repositorios: +- Debes conectar a {% data variables.product.product_location %} con {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta "[Conectar {% data variables.product.prodname_ghe_server %} a {% data variables.product.prodname_ghe_cloud %}](/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)." +- Debes conectar la gráfica de dependencias. + +{% ifversion ghes > 3.1 %} +Puedes habilitar la gráfica de dependencias a través de la {% data variables.enterprise.management_console %} o del shell administrativo. Te recomendamos que sigas la ruta de la {% data variables.enterprise.management_console %} a menos de que {% data variables.product.product_location %} utilice clústering. + +### Habilitar la gráfica de dependencias a través de la {% data variables.enterprise.management_console %} +{% endif %}{% ifversion ghes > 3.1 %} +{% data reusables.enterprise_site_admin_settings.sign-in %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.advanced-security-tab %} +1. Debajo de "Seguridad", haz clic en **Gráfica de dependencias**. ![Casilla de verificación para habilitar o inhabilitar la gráfica de dependencias](/assets/images/enterprise/3.2/management-console/enable-dependency-graph-checkbox.png) +{% data reusables.enterprise_management_console.save-settings %} +1. Da clic en **Visitar tu instancia**. + +### Habilitar la gráfica de dependencias a través del shell administrativo +{% else %} +### Habilitar la gráfica de dependencias +{% endif %} +{% data reusables.enterprise_site_admin_settings.sign-in %} +1. En el shell administrativo, habilita la gráfica de dependencias en {% data variables.product.product_location %}: + ``` shell + $ {% ifversion ghes > 3.1 %}ghe-config app.dependency-graph.enabled true{% else %}ghe-config app.github.dependency-graph-enabled true{% endif %} + ``` + {% note %} + + **Nota**: Para obtener más información acerca de cómo habilitar el acceso al shell administrativo por SSH, consulta la sección "[Acceder al shell administrativo (SSH)](/enterprise/{{ currentVersion }}/admin/configuration/accessing-the-administrative-shell-ssh)". + + {% endnote %} +1. Aplica la configuración + ```shell + $ ghe-config-apply + ``` +1. Regresa a {% data variables.product.prodname_ghe_server %}. + +### Habilitar {% data variables.product.prodname_dependabot_alerts %} + +Antes de habilitar {% data variables.product.prodname_dependabot_alerts %} para tu instancia, necesitas habilitar la gráfica de dependencias. Para obtener más información, consulta la sección anterior. + +{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %} +1. Debajo de "Los repositorios pueden escanearse par encontrar vulnerabilidades", utiliza el menú desplegable y selecciona **Habilitado sin notificaciones**. Opcionalmente, para habilitar las alertas con notificaciones, selecciona **Habilitado con notificaciones**. ![Menú desplegable para habilitar el escaneo de repositorios para buscar vulnerabilidades](/assets/images/enterprise/site-admin-settings/enable-vulnerability-scanning-in-repositories.png) + {% note %} + + Te recomendamos configurar las {% data variables.product.prodname_dependabot_alerts %} sin notificaciones durante los primeros días para evitar una sobrecarga de correos electrónicos. Después de algunos días, puedes habilitar las notificaciones para recibir las {% data variables.product.prodname_dependabot_alerts %} como de costumbre. + + {% endnote %} +## Ver las dependencias vulnerables en {% data variables.product.prodname_ghe_server %} + +Puedes ver todas las vulnerabilidades en {% data variables.product.product_location %} y sincronizar en forma manual los datos de vulnerabilidad desde {% data variables.product.prodname_dotcom_the_website %} para actualizar la lista. + +{% data reusables.enterprise_site_admin_settings.access-settings %} +2. En la barra lateral izquierda, haz clic en **Vulnerabilities** (Vulnerabilidades). ![Pestaña de vulnerabilidades de la barra lateral del administrador del sitio](/assets/images/enterprise/business-accounts/vulnerabilities-tab.png) +3. Para sincronizar los datos de vulnerabilidades, haz clic en **Sync Vulnerabilities now** (Sincronizar vulnerabilidades ahora). ![Botón de Sincronizar vulnerabilidades ahora](/assets/images/enterprise/site-admin-settings/sync-vulnerabilities-button.png) diff --git a/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md b/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md new file mode 100644 index 0000000000..78a244e8e7 --- /dev/null +++ b/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md @@ -0,0 +1,31 @@ +--- +title: Habilitar la sincronización automática de licencias de usuario entre el servidor de GitHub Enterprise y GitHub Enterprise Cloud +intro: 'Puedes conectar {% data variables.product.product_location_enterprise %} a {% data variables.product.prodname_ghe_cloud %} y permitir que {% data variables.product.prodname_ghe_server %} cargue información de licencias de usuario en tu cuenta de empresa en {% data variables.product.prodname_dotcom_the_website %}.' +redirect_from: + - /enterprise/admin/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud + - /enterprise/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud + - /admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud +permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable automatic user license synchronization.' +versions: + ghes: '*' +type: how_to +topics: + - Enterprise + - GitHub Connect + - Licensing +shortTitle: Habilitar la sincronización de licencias de usuario +--- + +## Acerca de la sincronización de licencias + +Después de que habilitas la sincronización de licencias, podrás ver el uso de licencias para toda tu cuenta empresarial, a través de {% data variables.product.prodname_ghe_server %} y de {% data variables.product.prodname_ghe_cloud %}. {% data variables.product.prodname_github_connect %} sincroniza la licencia entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %} semanalmente. Paa obtener más información, consulta la sección "[Administrar tu licencia de {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise)". + +También puedes cargar en forma manual información de licencias de usuario {% data variables.product.prodname_ghe_server %} en {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta la sección "[Conectar tu cuenta empresarial a {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)". + +## Habilitar la sincronización de licencias + +Antes de habilitar la sincronización de licencias en {% data variables.product.product_location_enterprise %}, debes conectar {% data variables.product.product_location_enterprise %} a {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta la sección "[Conectar tu cuenta empresarial a {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)". + +{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %} +1. En "El servidor puede sincronizar el recuento y uso de licencias de usuario", usa el menú desplegable y selecciona **Enabled** (Habilitado). ![Menú desplegable para habilitar la sincronización automática de licencias de usuario](/assets/images/enterprise/site-admin-settings/enable-user-license-drop-down.png) diff --git a/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md b/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md new file mode 100644 index 0000000000..4c12c3bc05 --- /dev/null +++ b/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md @@ -0,0 +1,46 @@ +--- +title: Enabling unified contributions between your enterprise account and GitHub.com +shortTitle: Habilitar las contribuciones unificadas +intro: 'Después de habilitar {% data variables.product.prodname_github_connect %}, puedes permitir {% data variables.product.prodname_ghe_cloud %} que los miembros destaquen su trabajo en {% data variables.product.product_name %} al enviar los recuentos de contribuciones a sus {% data variables.product.prodname_dotcom_the_website %} perfiles.' +redirect_from: + - /enterprise/admin/guides/developer-workflow/enabling-unified-contributions-between-github-enterprise-and-github-com/ + - /enterprise/admin/guides/developer-workflow/enabling-unified-contributions-between-github-enterprise-server-and-github-com/ + - /enterprise/admin/developer-workflow/enabling-unified-contributions-between-github-enterprise-server-and-githubcom/ + - /enterprise/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom + - /enterprise/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom + - /admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-unified-contributions-between-github-enterprise-server-and-githubcom +permissions: 'Enterprise owners who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable unified contributions between {% data variables.product.product_location %} and {% data variables.product.prodname_dotcom_the_website %}.' +versions: + ghes: '*' + ghae: next +type: how_to +topics: + - Enterprise + - GitHub Connect +--- + +{% data reusables.github-connect.beta %} + +As an enterprise owner, you can allow end users to send anonymized contribution counts for their work from {% data variables.product.product_location %} to their {% data variables.product.prodname_dotcom_the_website %} contribution graph. + +After you enable {% data variables.product.prodname_github_connect %} and enable {% data variables.product.prodname_unified_contributions %} in both environments, end users on your enterprise account can connect to their {% data variables.product.prodname_dotcom_the_website %} accounts and send contribution counts from {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.github-connect.sync-frequency %} 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)." + +If the enterprise owner disables the functionality or developers opt out of the connection, the {% data variables.product.product_name %} contribution counts will be deleted on {% data variables.product.prodname_dotcom_the_website %}. Si el programador vuelve a conectar sus perfiles luego de inhabilitarlos, se restablecerán los recuentos de contribución para los últimos 90 días. + +{% data variables.product.product_name %} **solo** envía el recuento de contribución y la fuente de ({% data variables.product.product_name %}) para los usuarios conectados. No envía ningún tipo de información sobre la contribución o cómo se realizó. + +Antes de habilitar {% data variables.product.prodname_unified_contributions %} en {% data variables.product.product_location %}, debes conectar {% data variables.product.product_location %} a {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_dotcom_the_website %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." + +{% ifversion ghes %} +{% data reusables.github-connect.access-dotcom-and-enterprise %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.business %} +{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %}{% else %} +1. Iniciar sesión en {% data variables.product.product_location %} y {% data variables.product.prodname_dotcom_the_website %}. +{% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %} +1. En "Los usuarios pueden compartir recuentos de contribuciones en {% data variables.product.prodname_dotcom_the_website %}", haz clic en **Request access (Solicita acceso)**. ![Request access to unified contributions option](/assets/images/enterprise/site-admin-settings/dotcom-ghe-connection-request-access.png){% ifversion ghes %} +2. [Inicia sesión](https://enterprise.github.com/login) en el sitio {% data variables.product.prodname_ghe_server %} para recibir más instrucciones. + +When you request access, we may redirect you to the {% data variables.product.prodname_ghe_server %} site to check your current terms of service. +{% endif %} diff --git a/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md b/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md new file mode 100644 index 0000000000..682115065e --- /dev/null +++ b/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md @@ -0,0 +1,44 @@ +--- +title: Enabling unified search between your enterprise account and GitHub.com +shortTitle: Habilitar la búsqueda unificada +intro: 'After enabling {% data variables.product.prodname_github_connect %}, you can allow search of {% data variables.product.prodname_dotcom_the_website %} for members of your enterprise on {% data variables.product.product_name %}.' +redirect_from: + - /enterprise/admin/guides/developer-workflow/enabling-unified-search-between-github-enterprise-and-github-com/ + - /enterprise/admin/guides/developer-workflow/enabling-unified-search-between-github-enterprise-server-and-github-com/ + - /enterprise/admin/developer-workflow/enabling-unified-search-between-github-enterprise-server-and-githubcom/ + - /enterprise/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom + - /enterprise/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom + - /admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-unified-search-between-github-enterprise-server-and-githubcom +permissions: 'Enterprise owners who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable unified search between {% data variables.product.product_name %} and {% data variables.product.prodname_dotcom_the_website %}.' +versions: + ghes: '*' + ghae: next +topics: + - Enterprise + - GitHub Connect + - GitHub search +--- + +{% data reusables.github-connect.beta %} + +When you enable unified search, users can view search results from public and private content on {% data variables.product.prodname_dotcom_the_website %} when searching from {% data variables.product.product_location %}{% ifversion ghae %} on {% data variables.product.prodname_ghe_managed %}{% endif %}. + +Los usuarios no podrán buscar {% data variables.product.product_location %} desde {% data variables.product.prodname_dotcom_the_website %}, incluso si tienen acceso a ambos entornos. Los usuarios solo pueden buscar repositorios privados para los que hayas habilitado {% data variables.product.prodname_unified_search %} y a los que tengan acceso en las organizaciones conectadas {% data variables.product.prodname_ghe_cloud %}. For more information, see "[About searching on {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github/#searching-across-github-enterprise-and-githubcom-simultaneously)" and "[Enabling private {% data variables.product.prodname_dotcom_the_website %} repository search in your enterprise account](/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment)." + +Buscar a través de las API REST y GraphQL no incluye {% data variables.product.prodname_dotcom_the_website %} los resultados de búsqueda. No están admitidas la búsqueda avanzada y buscar wikis en {% data variables.product.prodname_dotcom_the_website %}. + +{% ifversion ghes %} +{% data reusables.github-connect.access-dotcom-and-enterprise %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.business %} +{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %}{% else %} +1. Iniciar sesión en {% data variables.product.product_location %} y {% data variables.product.prodname_dotcom_the_website %}. +{% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %} +1. En "Los usuarios pueden buscar {% data variables.product.prodname_dotcom_the_website %}", utiliza el menú desplegable y haz clic en **Enabled (Habilitado)**. ![Habilitar la opción de búsqueda en el menú desplegable de búsqueda de GitHub.com](/assets/images/enterprise/site-admin-settings/github-dotcom-enable-search.png) +1. De manera opcional, en "Users can search private repositories on (Los usuarios pueden buscar repositorios privados en) {% data variables.product.prodname_dotcom_the_website %}", utiliza el menú desplegable y haz clic en **Enabled (Habilitado)**. ![Habilitar la opción de búsqueda de repositorios privados en el menú desplegable de búsqueda de GitHub.com](/assets/images/enterprise/site-admin-settings/enable-private-search.png) + +## Leer más + +- "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)" + diff --git a/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md b/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md new file mode 100644 index 0000000000..1d03dbfad3 --- /dev/null +++ b/translations/es-ES/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md @@ -0,0 +1,25 @@ +--- +title: Administrar las conexiones entre tus cuentas empresariales +intro: 'Con {% data variables.product.prodname_github_connect %}, puedes compartir determinadas características y datos entre {% data variables.product.product_location %} y la cuenta de tu organización u emprendimiento {% data variables.product.prodname_ghe_cloud %} en {% data variables.product.prodname_dotcom_the_website %}.' +redirect_from: + - /enterprise/admin/developer-workflow/connecting-github-enterprise-to-github-com + - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-and-github-com/ + - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-server-and-github-com/ + - /enterprise/admin/developer-workflow/connecting-github-enterprise-server-and-githubcom/ + - /enterprise/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud + - /enterprise/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud +versions: + ghes: '*' + ghae: next +topics: + - Enterprise +children: + - /connecting-your-enterprise-account-to-github-enterprise-cloud + - /enabling-unified-search-between-your-enterprise-account-and-githubcom + - /enabling-unified-contributions-between-your-enterprise-account-and-githubcom + - /enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud +shortTitle: Conectar cuentas empresariales +--- + diff --git a/translations/es-ES/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md b/translations/es-ES/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md index c3928b683d..0034b69794 100644 --- a/translations/es-ES/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md +++ b/translations/es-ES/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md @@ -353,7 +353,7 @@ Pudes parar la replicación hacia los nodos pasivos para el despliegue de {% dat {% data reusables.enterprise_clustering.open-configuration-file %} -3. In the top-level `[cluster]` section, delete the `redis-master-replica`, and `mysql-master-replica` key-value pairs. +3. En la sección de `[cluster]` de nivel superior, borra los pares de clave-valor de `redis-master-replica` y `mysql-master-replica`. 4. Borra cada sección para un nodo pasivo. Para los nodos pasivos, `replica` se configura como `enabled`. diff --git a/translations/es-ES/content/admin/enterprise-management/configuring-clustering/upgrading-a-cluster.md b/translations/es-ES/content/admin/enterprise-management/configuring-clustering/upgrading-a-cluster.md index 9aff87cb10..7c3bbd382a 100644 --- a/translations/es-ES/content/admin/enterprise-management/configuring-clustering/upgrading-a-cluster.md +++ b/translations/es-ES/content/admin/enterprise-management/configuring-clustering/upgrading-a-cluster.md @@ -79,7 +79,7 @@ Usa un paquete de actualización para actualizar una agrupación de {% data vari > gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u > gpg: Good signature from "GitHub Enterprise (Upgrade Package Key) > " ``` -5. El proceso de actualización reiniciará el nodo MySQL principal una vez que esté completo. Verify that you can `ping` each node after it reboots.{% ifversion ghes > 2.22 %} -6. Connect to the administrative shell of the primary MySQL node and run the `ghe-cluster-config-apply` command. -7. When `ghe-cluster-config-apply` is complete, check that the services are in a healthy state by running `ghe-cluster-status`.{% endif %} +5. El proceso de actualización reiniciará el nodo MySQL principal una vez que esté completo. Verifica que puedes hacer `ping` en cada nodo después de que reinicie.{% ifversion ghes > 2.22 %} +6. Conéctate al shell administrativo del nodo primario de MySQL y ejecuta el comando `ghe-cluster-config-apply`. +7. Cuando se cmpleta el `ghe-cluster-config-apply`, verifica que los servicios estén en un estado saludable ejecutando `ghe-cluster-status`.{% endif %} 8. Cierra el modo de mantenimiento desde el shell administativo de cualquier nodo al ejecutar `ghe-cluster-maintenance -u`. diff --git a/translations/es-ES/content/admin/enterprise-support/overview/about-github-enterprise-support.md b/translations/es-ES/content/admin/enterprise-support/overview/about-github-enterprise-support.md index e020a1d201..7f68a79ce6 100644 --- a/translations/es-ES/content/admin/enterprise-support/overview/about-github-enterprise-support.md +++ b/translations/es-ES/content/admin/enterprise-support/overview/about-github-enterprise-support.md @@ -33,7 +33,7 @@ Adicionalmente a los beneficios de {% data variables.contact.enterprise_support - Soporte técnico por escrito a través del portal de soporte de 24 horas por día, los 7 días de la semana - Soporte técnico telefónico las 24 horas del día, los 7 días de la semana - Un Acuerdo de nivel de servicio (SLA) con tiempos de respuesta iniciales garantizados. - - Customer Reliability Engineers + - Ingenieros de Confianza para el Cliente - Acceso a contenido prémium. - Revisiones de estado programadas. - Horas administrativas administradas diff --git a/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md index 9b3354883f..279cd9f7dd 100644 --- a/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md +++ b/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md @@ -37,19 +37,46 @@ Este artículo explica cómo los administradores de sitio pueden habilitar {% da {% endif %} +{%- ifversion ghes < 3.2 %} + Los recursos de CPU y de memoria que están disponibles para {% data variables.product.product_location %} determinan el rendimiento máximo de jobs para {% data variables.product.prodname_actions %}. Las pruebas internas de {% data variables.product.company_short %} demostraron el siguiente rendimiento máximo para las instancias de {% data variables.product.prodname_ghe_server %} con un rango de CPU y configuraciones de memoria. Puede que vas rendimientos diferentes dependiendo de los niveles generales de actividad en tu instancia. +{%- endif %} + +{%- ifversion ghes > 3.1 %} + +The CPU and memory resources available to {% data variables.product.product_location %} determine the number of jobs that can be run concurrently without performance loss. + +The peak quantity of concurrent jobs running without performance loss depends on such factors as job duration, artifact usage, number of repositories running Actions, and how much other work your instance is doing not related to Actions. Internal testing at GitHub demonstrated the following performance targets for GitHub Enterprise Server on a range of CPU and memory configurations: + +{% endif %} + +{%- ifversion ghes < 3.2 %} + | vCPU | Memoria | Rendimiento máximo del job | |:---- |:------- |:-------------------------- | -| | | | -{%- ifversion ghes > 3.1 %} -| 4 | 32 GB | Demo or light testing | | 8 | 64 GB | 30 jobs | | 16 | 128 GB | 60 jobs | | 32 | 256 GB | 120 jobs | | 64 | 512 GB | 160 jobs | -{%- else ifversion ghes < 3.2 %} -| 4 | 32 GB | Demo or light testing | | 8 | 64 GB | 25 jobs | | 16 | 160 GB | 35 jobs | | 32 | 256 GB | 100 jobs | +| 4 | 32 GB | Demo o pruebas leves | +| 8 | 64 GB | 25 puestos de trabajo | +| 16 | 160 GB | 35 puestos de trabajo | +| 32 | 256 GB | 100 puestos de trabajo | + {%- endif %} +{%- ifversion ghes > 3.1 %} + +| vCPU | Memoria | Maximum Concurrency* | +|:---- |:------- |:----------------------- | +| 32 | 128 GB | 1500 puestos de trabajo | +| 64 | 256 GB | 1900 puestos de trabajo | +| 96 | 384 GB | 2200 puestos de trabajo | + +*Maximum concurrency was measured using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. You may experience different performance depending on the overall levels of activity on your instance. + +{%- endif %} + + Si {% ifversion ghes = 2.22 %}habilitaste el beta de{% else %}planeas habilitar{% endif %} {% data variables.product.prodname_actions %} para los usuarios de una instancia existente, revisa los niveles de actividad para los usuarios y las automatizaciones en la instancia y asegúrate de que hayas aprovisionado la memoria y CPU adecuados para tus usuarios. Para obtener más información acerca de cómo monitorear la capacidad y rendimiento de {% data variables.product.prodname_ghe_server %}, consulta la sección "[Monitorear tu aplicativo](/admin/enterprise-management/monitoring-your-appliance)". Para obtener más información acerca de los requisitos mínimos de {% data variables.product.product_location %}, consulta las consideraciones de hardware para la plataforma de tu instancia. @@ -98,9 +125,9 @@ El soporte para {% data variables.product.prodname_actions %} en {% data variabl {% endif %} -## Networking considerations +## Consideraciones de las conexiones -{% data reusables.actions.proxy-considerations %} For more information about using a proxy with {% data variables.product.prodname_ghe_server %}, see "[Configuring an outbound web proxy server](/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server)." +{% data reusables.actions.proxy-considerations %} Para obtener más información sobre cómo utilizar un proxy con {% data variables.product.prodname_ghe_server %}, consulta la sección "[Configurar un servidor proxy saliente](/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server)". {% ifversion ghes > 2.22 %} @@ -134,6 +161,6 @@ Si quieres aprender más acerca de las prácticas de seguridad para {% data vari {% endif %} -## Reserved Names +## Nombres reservados -When you enable {% data variables.product.prodname_actions %} for your enterprise, two organizations are created: `github` and `actions`. If your enterprise already uses the `github` organization name, `github-org` (or `github-github-org` if `github-org` is also in use) will be used instead. If your enterprise already uses the `actions` organization name, `github-actions` (or `github-actions-org` if `github-actions` is also in use) will be used instead. Once actions is enabled, you won't be able to use these names anymore. +Cuando habilitas las {% data variables.product.prodname_actions %} para tu empresa, se crean dos organizaciones: `github` y `actions`. Si tu empresa utiliza el nombre de organización `github`, `github-org` (o `github-github-org` si `github-org` también se está utilizando) se utilizará en su lugar. Si tu empresa ya utiliza el nombre de organización `actions`, `github-actions` (or `github-actions-org` si `github-actions` también se está utilizando) se utilizará en su lugar. Una vez que se habiliten las acciones, ya no podrás utilizar estos nombres. diff --git a/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md b/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md index 08b7349f81..11742dab75 100644 --- a/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md +++ b/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md @@ -10,7 +10,6 @@ children: - /enabling-github-actions-with-azure-blob-storage - /enabling-github-actions-with-amazon-s3-storage - /enabling-github-actions-with-minio-gateway-for-nas-storage - - /enforcing-github-actions-policies-for-your-enterprise shortTitle: Habiligar GitHub Actions --- diff --git a/translations/es-ES/content/admin/github-actions/index.md b/translations/es-ES/content/admin/github-actions/index.md index 994df21604..e2403eb380 100644 --- a/translations/es-ES/content/admin/github-actions/index.md +++ b/translations/es-ES/content/admin/github-actions/index.md @@ -16,6 +16,5 @@ children: shortTitle: Administrar las GitHub Actions --- -{% data reusables.actions.ae-beta %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} diff --git a/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md b/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md index 17d2bd3229..95808288a8 100644 --- a/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md +++ b/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md @@ -18,7 +18,6 @@ shortTitle: Agregar acciones en tu empresa {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} Los flujos de trabajo de {% data variables.product.prodname_actions %} pueden utilizar _acciones_, las cuales son tareas individuales que puedes combinar para crear jobs y personalizar tu flujo de trabajo. Puedes crear tus propias acciones, o utilizar y personalizar a quellas que comparte la comunidad de {% data variables.product.prodname_dotcom %}. 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 2dcf569b97..ea73f6bdd7 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 @@ -19,7 +19,6 @@ shortTitle: Utilizar GitHub Connect para las acciones {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.actions.enterprise-github-connect-warning %} -{% data reusables.actions.ae-beta %} Predeterminadamente, los flujos de trabajo de {% data variables.product.prodname_actions %} en {% data variables.product.product_name %} no pueden utilizar las acciones directamente desde {% data variables.product.prodname_dotcom_the_website %} o desde [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions). @@ -27,8 +26,16 @@ Para que todas las acciones de {% data variables.product.prodname_dotcom_the_web ## Habilitar el acceso automático a todas las acciones de {% data variables.product.prodname_dotcom_the_website %} -Antes de habilitar el acceso para todas las acciones desde {% data variables.product.prodname_dotcom_the_website %} en tu instancia empresarial, debes conectar a tu empresa con {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta "[Conectar {% data variables.product.prodname_ghe_server %} a {% data variables.product.prodname_ghe_cloud %}](/enterprise/{{ currentVersion }}/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)." +Antes de habilitar el acceso para todas las acciones desde {% data variables.product.prodname_dotcom_the_website %} en tu instancia empresarial, debes conectar a tu empresa con {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta la sección "[Conectar empresa a {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)". -{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %} +{% data reusables.enterprise-accounts.access-enterprise %} +{%- ifversion ghes < 3.1 %} +{% data reusables.enterprise-accounts.settings-tab %} +{%- endif %} +{% data reusables.enterprise-accounts.github-connect-tab %} +{%- ifversion ghes > 3.0 or ghae %} +1. Debajo de "Los usuarios pueden utilizar acciones de GitHub.com en las ejecuciones de flujo de trabajo", utiliza el menú desplegable y selecciona **Habilitado**. ![Menú desplegable a las acciones de GitHub.com en las ejecuciones de flujo de trabajo](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down-ae.png) +{%- else %} 1. Debajo de "El servidor puede utilizar acciones de GitHub.com en las ejecuciones de flujo de trabajo", utiliza el menú desplegable y selecciona **Habilitado**. ![Menú desplegable a las acciones de GitHub.com en las ejecuciones de flujo de trabajo](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down.png) +{%- endif %} 1. {% data reusables.actions.enterprise-limit-actions-use %} 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 1d17d9d61c..d504e3502e 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 @@ -14,13 +14,14 @@ shortTitle: Sincronziar acciones manualmente {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.actions.enterprise-no-internet-actions %} -El acercamiento recomendado para habilitar el acceso a las acciones de {% data variables.product.prodname_dotcom_the_website %} es habilitar el acceso automático para todas las acciones. Puedes hacer esto si utilizas {% data variables.product.prodname_github_connect %} para integrar a {% data variables.product.product_name %} con {% data variables.product.prodname_ghe_cloud %} . Para obtener más información, consulta la sección "[Habilitar el acceso automático a las acciones de {% data variables.product.prodname_dotcom_the_website %} utilizando {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". +{% ifversion ghes or ghae-next %} -Sin embargo, si quieres tener un control más estricto sobre qué acciones se permiten en tu empresa, puedes seguir esta guía para utilizar la herramienta de código abierto [`actions-sync`](https://github.com/actions/actions-sync) de {% data variables.product.company_short %} para sincronizar los repositorios de acción individual desde {% data variables.product.prodname_dotcom_the_website %} hacia tu empresa. +El acercamiento recomendado para habilitar el acceso a las acciones de {% data variables.product.prodname_dotcom_the_website %} es habilitar el acceso automático para todas las acciones. Puedes hacer esto si utilizas {% data variables.product.prodname_github_connect %} para integrar a {% data variables.product.product_name %} con {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta la sección "[Habilitar el acceso automático a las acciones de {% data variables.product.prodname_dotcom_the_website %} utilizando{% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". + +Sin embargo, si quieres tener un control más estricto sobre qué acciones se permiten en tu empresa, puedes{% else %}Puedes{% endif %} seguir esta guía para utilizar la herramienta [`actions-sync`](https://github.com/actions/actions-sync) de código abierto de {% data variables.product.company_short %} para sincronizar los repositorios de acciones individuales desde {% data variables.product.prodname_dotcom_the_website %} hacia tu empresa. ## Acerca de la herramienta `actions-sync` @@ -33,7 +34,7 @@ La herramienta `actions-sync` solo puede descargar acciones de {% data variables ## Prerrequisitos * Antes de utilizar la herramienta `actions-sync`, debes asegurarte de que todas las organizaciones de destino ya existan en tu empresa. El siguiente ejemplo demuestra cómo sincronizar acciones a una organización que se llama `synced-actions`. Para obtener más información, consulta la sección "[Crear una organización nueva desde cero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)". -* Debes crear un token de acceso personal (PAT) en tu empresa que pueda crear y escribir en los repositorios de las organizaciones destino. Para obtener más información, consulta la sección "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)". +* Debes crear un token de acceso personal (PAT) en tu empresa que pueda crear y escribir en los repositorios de las organizaciones destino. Para obtener más información, consulta la sección "[Crear un token de acceso personal](/github/authenticating-to-github/creating-a-personal-access-token)".{% ifversion ghes %} * Si quieresSi quieres sincronizar las acciones incluidas en la organización `actions` en {% data variables.product.product_location %}, debes ser un propietario de la organización `actions`. {% note %} @@ -46,21 +47,21 @@ La herramienta `actions-sync` solo puede descargar acciones de {% data variables ```shell ghe-org-admin-promote -u USERNAME -o actions - ``` + ```{% endif %} -## Ejemplo: Utilizar la herramienta `actions-sync` +## Example: Using the `actions-sync` tool -Este ejemplo demuestra el uso de la herramienta `actions-sync` para sincronizar una acción individual de {% data variables.product.prodname_dotcom_the_website %} con una instancia empresarial. +This example demonstrates using the `actions-sync` tool to sync an individual action from {% data variables.product.prodname_dotcom_the_website %} to an enterprise instance. {% note %} -**Nota:** Este ejemplo utiliza el comando `actions-sync sync`, el cual requiere tener acceso concurrente tanto a la API de {% data variables.product.prodname_dotcom_the_website %} como a la API de tu instancia empresarial desde tu máquina. Si sólo puedes acceder a un sistema a la vez, puedes utilizar los comandos `actions-sync pull` y `push`. Para obtener más información, consulta el [README de `actions-sync`](https://github.com/actions/actions-sync#not-connected-instances). +**Note:** This example uses the `actions-sync sync` command, which requires concurrent access to both the {% data variables.product.prodname_dotcom_the_website %} API and your enterprise instance's API from your machine. If you can only access one system at a time, you can use the `actions-sync pull` and `push` commands. For more information, see the [`actions-sync` README](https://github.com/actions/actions-sync#not-connected-instances). {% endnote %} -1. Descarga y extrae el [lanzamiento más reciente de `actions-sync`](https://github.com/actions/actions-sync/releases) para el sistema operativo de tu máquina. +1. Download and extract the latest [`actions-sync` release](https://github.com/actions/actions-sync/releases) for your machine's operating system. 1. Crea un directorio para almacenar los archivos de caché para la herramienta. -1. Ejecuta el comando `actions-sync sync`: +1. Run the `actions-sync sync` command: ```shell ./actions-sync sync \ diff --git a/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md b/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md index bbbb2a349f..3bc6bd4b82 100644 --- a/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md +++ b/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md @@ -14,7 +14,6 @@ shortTitle: Caché de herramientas para los ejecutores sin conexión {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Acerca de las acciones de configuración incluídas y el caché de la herramienta del ejecutor 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 86cc2ccbd1..384d38a0a4 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 @@ -13,7 +13,6 @@ shortTitle: Utilizar las acciones empaquetadas más recientes {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} Tu instancia empresarial incluye varias acciones integradas que puedes utilizar en tus flujos de trabajo. Para obtener más información sobre las acciones en paquete, consulta la sección "[Acciones oficiales que vienen en paquete con tu instancia empresarial](/admin/github-actions/about-using-actions-in-your-enterprise#official-actions-bundled-with-your-enterprise-instance)". @@ -29,17 +28,13 @@ Puedes utilizar {% data variables.product.prodname_github_connect %} para permit Una vez que se configura {% data variables.product.prodname_github_connect %}, puedes utilizar la versión más reciente de una acción si borras su repositorio local en la organización `actions` en tu instancia. Por ejemplo, si tu instancia empresarial está utilizando la acción `actions/checkout@v1` y necesitas utilizar `actions/checkout@v2`, el cual no está disponible en esta, lleva a cabo los siguietnes pasos para que puedas utilizar la acción más reciente de `checkout` desde {% data variables.product.prodname_dotcom_the_website %}: -1. Predeterminadamente, los administradores de sitio no son los propietarios de la organización de acciones incluidas. Para obtener el acceso requerido para borrar el repositorio `checkout`, utiliza el comando `ghe-org-admin-promote` para promover a un usuario como propietario de la organización empaquetada `actions`. Para obtener más información, consulta la sección "[Acceder al shell administrativo (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" y "[`ghe-org-admin-promote`](/admin/configuration/command-line-utilities#ghe-org-admin-promote)". Por ejemplo: - - ```shell - $ ghe-org-admin-promote -u octocat -o actions - Do you want to give organization admin privileges for actions to octocat? (y/N) y - Making octocat an admin of actions - --> Adding octocat as an admin of actions - --> octocat is now an admin of the actions organization - --> Done. - ``` -1. En tu instancia de {% data variables.product.product_name %}, borra el repositorio `checkout` dentro de la organización `actions`. Para obtener más información sobre cómo borrar un repositorio, consulta la sección "[Borrar un repositorio](/github/administering-a-repository/deleting-a-repository)". -1. Se recomienda que salgas de la organización `actions` una vez que ya no requieras acceso administrativo. Para obtener más información, consulta "[Cómo eliminarte de una organización](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization)". +1. Desde una cuenta de propietario de empresa en {% data variables.product.product_name %}, navega al repositorio que quieras borrar desde la organización *actions* (en este `checkout` de ejemplo). +1. Predeterminadamente, los administradores de sitio no son propietarios de la organización integrada de *actions*. Para obtener el acceso requerido para borrar el repositorio `checkout`, debes utilizar las herramientas de administrador de sitio. Haz clic en {% octicon "rocket" aria-label="The rocket ship" %} en la esquina superior derecha de cualquier página de este repositorio. ![Ícono de cohete para acceder a las configuraciones de administrador del sitio](/assets/images/enterprise/site-admin-settings/access-new-settings.png) +1. Haz clic en {% octicon "shield-lock" %} **Seguridad** para ver el resumen de seguridad del repositorio. ![Asegurar el repositorio del repositorio](/assets/images/enterprise/site-admin-settings/access-repo-security-info.png) +1. Debajo de "Acceso privilegiado", haz clic en **Desbloquear**. ![Botón de desbloquear](/assets/images/enterprise/site-admin-settings/unlock-priviledged-repo-access.png) +1. Debajo de **Razón**, teclea una razón para desbloquear el repositorio y luego haz clic en **Desbloquear**. ![Diálogo de confirmación](/assets/images/enterprise/site-admin-settings/confirm-unlock-repo-access.png) +1. Ahora que el repositorio se desbloqueó, puedes salir de las páginas de administrador de sitio y borrar el repositorio dentro de la organización `actions`. En la parte superior de la página, haz clic en el nombre de repositorio, que en este ejemplo es **checkout**, para regresar a la página de resumen. ![Enlace de nombre de repositorio](/assets/images/enterprise/site-admin-settings/display-repository-admin-summary.png) +1. Debajo de "Información de repositorio", haz clic en **Ver código** para salir de las páginas de administrador del sitio y que se muestre el repositorio `checkout`. +1. Borra el repositorio `checkout` dentro de la organización `actions`. Para obtener más información sobre cómo borrar un repositorio, consulta la sección "[Borrar un repositorio](/github/administering-a-repository/deleting-a-repository)". ![Enlace de ver código](/assets/images/enterprise/site-admin-settings/exit-admin-page-for-repository.png) 1. Configura el YAML de tu flujo de trabajo para que utilice `actions/checkout@v2`. 1. Cada vez que se ejecute tu flujo de trabajo, el ejecutor utilizará la versión `v2` de `actions/checkout` desde {% data variables.product.prodname_dotcom_the_website %}. diff --git a/translations/es-ES/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md b/translations/es-ES/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md index c655d177ec..5ca2f30950 100644 --- a/translations/es-ES/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md +++ b/translations/es-ES/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md @@ -13,7 +13,6 @@ redirect_from: - /admin/github-actions/getting-started-with-github-actions-for-github-ae --- -{% data reusables.actions.ae-beta %} Este artículo explica cómo los administradores de sitio pueden habilitar {% data variables.product.prodname_ghe_managed %} para utilizar {% data variables.product.prodname_actions %}. diff --git a/translations/es-ES/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md b/translations/es-ES/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md index ec1fbd7c0b..441e7fff97 100644 --- a/translations/es-ES/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md +++ b/translations/es-ES/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md @@ -8,7 +8,6 @@ redirect_from: shortTitle: Utiliza acciones --- -{% data reusables.actions.ae-beta %} Los flujos de trabajo de {% data variables.product.prodname_actions %} pueden utilizar _acciones_, las cuales son tareas individuales que puedes combinar para crear jobs y personalizar tu flujo de trabajo. Puedes crear tus propias acciones, o utilizar y personalizar a quellas que comparte la comunidad de {% data variables.product.prodname_dotcom %}. diff --git a/translations/es-ES/content/admin/guides.md b/translations/es-ES/content/admin/guides.md index c83f0e6a67..98e53325fc 100644 --- a/translations/es-ES/content/admin/guides.md +++ b/translations/es-ES/content/admin/guides.md @@ -35,13 +35,13 @@ includeGuides: - /admin/configuration/configuring-rate-limits - /admin/configuration/configuring-secret-scanning-for-your-appliance - /admin/configuration/configuring-tls - - /admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud + - /admin/configuration/connecting-your-enterprise-account-to-github-enterprise-cloud - /admin/configuration/enabling-and-scheduling-maintenance-mode - /admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud - /admin/configuration/enabling-private-mode - /admin/configuration/enabling-subdomain-isolation - - /admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom - - /admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom + - /admin/configuration/enabling-unified-contributions-between-your-enterprise-account-and-githubcom + - /admin/configuration/enabling-unified-search-between-your-enterprise-account-and-githubcom - /admin/configuration/initializing-github-ae - /admin/configuration/managing-github-for-mobile-for-your-enterprise - /admin/configuration/network-ports diff --git a/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md b/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md index 5c46b4a044..8acaebb9ad 100644 --- a/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md +++ b/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md @@ -27,7 +27,7 @@ Esta guía supone que estás familiarizado con los siguientes conceptos de AWS: - [EC2 y Virtual Private Cloud](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-vpc.html) (si planeas iniciar dentro de Virtual Private Cloud) - [Precios de AWS](https://aws.amazon.com/pricing/) (Para calcular y administrar los costos) -For an architectural overview, see the "[AWS Architecture Diagram for Deploying GitHub Enterprise Server](/assets/images/installing-github-enterprise-server-on-aws.png)". +Para ver un resumen arquitectónico, consulta el [Diagrama de Arquitectura de AWS para Desplegar a GitHub Enterprise Server](/assets/images/installing-github-enterprise-server-on-aws.png)". Esta guía te recomienda utilizar el principio del menor privilegio necesario cuando configures {% data variables.product.product_location %} en AWS. Para obtener más información, refiérete a la [Documentación sobre la Administración de Accesos e Identidad (IAM) de AWS](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#grant-least-privilege). diff --git a/translations/es-ES/content/admin/overview/about-enterprise-accounts.md b/translations/es-ES/content/admin/overview/about-enterprise-accounts.md index dbf8be2a69..b9f53296cb 100644 --- a/translations/es-ES/content/admin/overview/about-enterprise-accounts.md +++ b/translations/es-ES/content/admin/overview/about-enterprise-accounts.md @@ -1,6 +1,6 @@ --- title: Acerca de las cuentas de empresa -intro: 'With {% data variables.product.product_name %}, you can use an enterprise account to give administrators a single point of visibility and management.' +intro: 'Con {% data variables.product.product_name %}, puedes utilizar una cuenta empresarial para darle a los administradores un solo punto de visibilidad y administración.' redirect_from: - /enterprise/admin/installation/about-enterprise-accounts - /enterprise/admin/overview/about-enterprise-accounts diff --git a/translations/es-ES/content/admin/overview/about-upgrades-to-new-releases.md b/translations/es-ES/content/admin/overview/about-upgrades-to-new-releases.md index 294c4f72d3..c9561cbaca 100644 --- a/translations/es-ES/content/admin/overview/about-upgrades-to-new-releases.md +++ b/translations/es-ES/content/admin/overview/about-upgrades-to-new-releases.md @@ -13,7 +13,7 @@ topics: {% data variables.product.product_name %} está en mejora contínua, con una funcionalidad nueva y correcciones de errores que se presentan mediante lanzamientos mayores y menores. {% ifversion ghae %}{% data variables.product.prodname_ghe_managed %} es un servicio completamente administrado, así que {% data variables.product.company_short %} completa el proceso de mejora para tu empresa.{% endif %} -Los lanzamientos mayores incluyen nuevas funcionalidades y mejoras de características y, habitualmente, ocurren {% ifversion ghae %}cada pocas semanas o meses{% else %} trimestralmente{% endif %}. {% ifversion ghae %}{% data variables.product.company_short %} actualizará tu empresa al último lanzamiento mayor. Se te notificará previamente sobre cualquier tiempo de inactividad que se planee para tu empresa.{% endif %} +Los lanzamientos principales incluyen funcionalidades nuevas y mejoras de características y habitualmente se presentan cada trimestre. {% ifversion ghae %}{% data variables.product.company_short %} actualizará tu empresa al último lanzamiento mayor. Se te notificará previamente sobre cualquier tiempo de inactividad que se planee para tu empresa.{% endif %} {% ifversion ghes %} @@ -43,7 +43,6 @@ Para mejorar tu empresa a un lanzamiento nuevo, consulta las secciones "[Notas d ## Leer más -- [ {% data variables.product.prodname_roadmap %} ]({% data variables.product.prodname_roadmap_link %}) en el repositorio `github/roadmap` -{% ifversion ghae %} +- [ {% data variables.product.prodname_roadmap %} ]({% data variables.product.prodname_roadmap_link %}) en el repositorio `github/roadmap`{% ifversion ghae %} - [ {% data variables.product.prodname_ghe_managed %} notas de lanzamiento](/admin/release-notes) {% endif %} diff --git a/translations/es-ES/content/admin/overview/system-overview.md b/translations/es-ES/content/admin/overview/system-overview.md index fe40c04615..200f7874ba 100644 --- a/translations/es-ES/content/admin/overview/system-overview.md +++ b/translations/es-ES/content/admin/overview/system-overview.md @@ -74,11 +74,11 @@ El {% data variables.product.prodname_ghe_server %} también incluye caracterís El {% data variables.product.prodname_ghe_server %} ejecuta un sistema operativo Linux personalizado con las aplicaciones y los servicios necesarios únicamente. El {% data variables.product.prodname_dotcom %} gestiona el parche del sistema operativo central del aparato como parte de su ciclo estándar de lanzamiento de productos. Los parches abordan problemas de funcionalidad, de estabilidad y de seguridad no críticos para las aplicaciones de {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_dotcom %} también proporciona parches de seguridad críticos según se necesita fuera del ciclo de lanzamiento regular. -{% data variables.product.prodname_ghe_server %} is provided as an appliance, and many of the operating system packages are modified compared to the usual Debian distribution. We do not support modifying the underlying operating system for this reason (including operating system upgrades), which is aligned with the [{% data variables.product.prodname_ghe_server %} license and support agreement](https://enterprise.github.com/license), under section 11.3 Exclusions. +{% data variables.product.prodname_ghe_server %} se proporciona como un aplicativo y muchos de los paquetes de los sistemas operativos se modifican en comparación con la distribución común de Debian. No ofrecemos compatibilidad con la modificación del sistema operativo subyacente por esta razón (incluyendo las mejoras de los sistemas operativos), lo cual se alinea con la [licencia de {% data variables.product.prodname_ghe_server %} y el acuerdo de soporte](https://enterprise.github.com/license), bajo las exclusiones de la sección 11.3. -Currently, the base of the {% data variables.product.prodname_ghe_server %} appliance is Debian 9 (Stretch) and receives support under the Debian Long Term Support program. There are plans to move to a newer base operating system before the end of the Debian LTS period for Stretch. +Actualmente, la base del aplicativo de {% data variables.product.prodname_ghe_server %} es Debian 9 (Stretch) y recibe soporte bajo el programa de Soporte a Largo Plazo de Debian. Existen planes para migrarse a un sistema operativo base nuevo antes del final del periodo de Debian LTS para Stretch. -Regular patch updates are released on the {% data variables.product.prodname_ghe_server %} [releases](https://enterprise.github.com/releases) page, and the [release notes](/enterprise-server/admin/release-notes) page provides more information. These patches typically contain upstream vendor and project security patches after they've been tested and quality approved by our engineering team. There can be a slight time delay from when the upstream update is released to when it's tested and bundled in an upcoming {% data variables.product.prodname_ghe_server %} patch release. +Las actualizaciones de parche regulares se lanzan en la página de [lanzamientos](https://enterprise.github.com/releases) de {% data variables.product.prodname_ghe_server %} y la página de [notas de lanzamiento](/enterprise-server/admin/release-notes) proporciona más información sobre esto. Estos parches a menudo contienen un proveedor de nivel superior y parches de seguridad de proyecto después de que se prueban y que nuestro equipo de ingeniería aprueba su calidad. Puede haber una pequeña demora en tiempo desde cuando la actualización de nivel superior se lanza hasta cuando se prueba y se empaqueta en un lanzamiento de parche futuro de {% data variables.product.prodname_ghe_server %}. ### Seguridad de la red diff --git a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise.md b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise.md new file mode 100644 index 0000000000..1dfbbc72fe --- /dev/null +++ b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise.md @@ -0,0 +1,59 @@ +--- +title: Requerir las políticas de GitHub Actions para tu empresa +intro: 'Los administradores empresariales pueden gestionar el acceso a {% data variables.product.prodname_actions %} en una empresa.' +redirect_from: + - /enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise + - /admin/github-actions/enforcing-github-actions-policies-for-your-enterprise + - /admin/github-actions/enabling-github-actions-for-github-enterprise-server/enforcing-github-actions-policies-for-your-enterprise +versions: + ghes: '*' + ghae: '*' +type: how_to +topics: + - Actions + - Enterprise + - Policies +shortTitle: GitHub Actions policies +--- + +{% data reusables.actions.enterprise-beta %} + +## Acerca de los permisos de {% data variables.product.prodname_actions %} para tu empresa + +{% ifversion ghae %}{% else %}Cuando habilitas las {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %}, se habilitan para todas las organizaciones en tu empresa. {% endif %}Puedes elegir inhabilitar {% data variables.product.prodname_actions %} para todas las organizaciones en tu empresa o únicamente para algunas específicas. También puedes limitar el uso de acciones públicas para que las personas solo puedan utilizar las acciones locales que existen en tu empresa. + +## Administrar los permisos de {% data variables.product.prodname_actions %} para tu empresa + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.actions-tab %} +{% data reusables.actions.enterprise-actions-permissions %} + +{% ifversion ghes > 2.22 or ghae %} +## Permitir que se ejecuten acciones específicas + +{% data reusables.actions.allow-specific-actions-intro %} + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.actions-tab %} +1. Debajo de **Políticas**, selecciona **Permitir las acciones seleccionadas** y agrega tus acciones requeridas a la lista. + {%- ifversion ghes or ghae-issue-5094 %} + ![Agregar acciones a la lista de permitidos](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png) + {%- elsif ghae %} + ![Agregar acciones a la lista de permitidos](/assets/images/enterprise/github-ae/enterprise-actions-policy-allow-list.png) + {%- endif %} +{% endif %} + +{% ifversion ghes > 2.22 or ghae %} +## Habilitar flujos de trabajo para las bifurcaciones de repositorios privados + +{% data reusables.github-actions.private-repository-forks-overview %} + +### Configurar la política de bifurcación privada para tu empresa + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.actions-tab %} +{% data reusables.github-actions.private-repository-forks-configure %} +{% endif %} diff --git a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md index 5deeede26f..41a9d447ad 100644 --- a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md +++ b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md @@ -34,12 +34,12 @@ topics: - Enterprise - Policies - Security -shortTitle: Requerir políticas de repositorio +shortTitle: Políticas de administración de repositorio --- ## Configurar la visibilidad predeterminada para los repositorios nuevos en tu empresa -Cada vez que alguien crea un repositorio nuevo en tu empresa, esta persona debe elegir una visibilidad para el mismo. Cuando configuras una visibilidad predeterminada para la empresa, eliges qué vsibilidad se seleccina predeterminadamente. For more information on repository visibility, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." +Cada vez que alguien crea un repositorio nuevo en tu empresa, esta persona debe elegir una visibilidad para el mismo. Cuando configuras una visibilidad predeterminada para la empresa, eliges qué vsibilidad se seleccina predeterminadamente. Para obtener más información sobre la visibilidad de los repositorios, consulta la sección "[Acerca de los repositorios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)". Si un propietario de empresa deja de permitir que los miembros de ésta creen ciertos tipos de repositorios, estos no podrán crear este tipo de repositorio aún si la configuración de visibilidad lo tiene como predeterminado. Para obtener más información, consulta la sección "[Configurar una política para la creación de repositorios](#setting-a-policy-for-repository-creation)". diff --git a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/index.md b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/index.md index fadad39a81..0512ba5722 100644 --- a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/index.md +++ b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/index.md @@ -1,6 +1,6 @@ --- title: Requerir políticas para tu empresa -intro: You can configure policies for organizations in your enterprise. +intro: Puedes configurar las políticas para las organizaciones en tu empresa. redirect_from: - /enterprise/admin/policies/enforcing-policies-for-your-enterprise versions: @@ -11,6 +11,7 @@ topics: children: - /enforcing-repository-management-policies-in-your-enterprise - /restricting-email-notifications-for-your-enterprise + - /enforcing-github-actions-policies-for-your-enterprise - /enforcing-policies-for-advanced-security-in-your-enterprise shortTitle: Aplicar políticas --- diff --git a/translations/es-ES/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md b/translations/es-ES/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md index 5d4d020b92..c790608cdb 100644 --- a/translations/es-ES/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md +++ b/translations/es-ES/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md @@ -84,7 +84,7 @@ La variable `$GITHUB_VIA` se encuentra disponible en el ambiente de gancho de pr | Valor | Acción | Más información | |:-------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 
auto-merge deployment api
| Fusión automática de la rama base a través del despliegue que se creó con la API | "[Repositorios](/rest/reference/repos#create-a-deployment)" en la documentación de la API de REST | -| 
blob#save
| Cambio al contenido de un archivo en la interface web | "[Editing files](/repositories/working-with-files/managing-files/editing-files)" | +| 
blob#save
| Cambio al contenido de un archivo en la interface web | "[Editar archivos](/repositories/working-with-files/managing-files/editing-files)" | | 
branch merge api
| Fusión de una rama a través de la API | "[Repositorios](/rest/reference/repos#merge-a-branch)" en la documentación de la API de REST | | 
branches page delete button
| Borrado de una rama en la interface web | "[Crear y borrar ramas dentro de tu repositorio](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#deleting-a-branch)" | | 
git refs create api
| Creación de una referencia a través de la API | "[Base de datos de Git](/rest/reference/git#create-a-reference)" en la documentación de la API de REST | diff --git a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/index.md b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/index.md index b0037ef9de..a32aedf02e 100644 --- a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/index.md +++ b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/index.md @@ -5,7 +5,7 @@ redirect_from: - /enterprise/admin/categories/admin-bootcamp/ - /enterprise/admin/user-management/organizations-and-teams - /enterprise/admin/user-management/managing-organizations-in-your-enterprise -intro: 'Las organizaciones son ideales para crear grupos diferentes de usuarios dentro de tu empresa, como divisiones o grupos trabajando en proyectos similares. {% ifversion ghae %}Internal{% else %}Public and internal{% endif %} repositories that belong to an organization are accessible to members of other organizations in the enterprise, while private repositories are inaccessible to anyone but members of the organization that are granted access.' +intro: 'Las organizaciones son ideales para crear grupos diferentes de usuarios dentro de tu empresa, como divisiones o grupos trabajando en proyectos similares. Los repositorios {% ifversion ghae %}internos{% else %}Los repositorios públicos e internos{% endif %} que pertenecen a una organización son accesibles para los miembros de otras organizaciones en la empresa, mientras que los repositorios privados no son accesibles para nadie mas que los miembros de la organización que cuenta con este acceso.' versions: ghes: '*' ghae: '*' diff --git a/translations/es-ES/content/admin/user-management/managing-repositories-in-your-enterprise/migrating-to-internal-repositories.md b/translations/es-ES/content/admin/user-management/managing-repositories-in-your-enterprise/migrating-to-internal-repositories.md index 095e386939..3fb225829b 100644 --- a/translations/es-ES/content/admin/user-management/managing-repositories-in-your-enterprise/migrating-to-internal-repositories.md +++ b/translations/es-ES/content/admin/user-management/managing-repositories-in-your-enterprise/migrating-to-internal-repositories.md @@ -19,7 +19,7 @@ shortTitle: Migración de repositorio interno ## Acerca de los repositorios internos -Los repositorios internos están disponibles desde {% data variables.product.prodname_ghe_server %} 2.20+. {% data reusables.repositories.about-internal-repos %} For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." +Los repositorios internos están disponibles desde {% data variables.product.prodname_ghe_server %} 2.20+. {% data reusables.repositories.about-internal-repos %} para obtener más información, consulta la sección"[Acerca de los repositorios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)". En lanzamientos futuros de {% data variables.product.prodname_ghe_server %}, ajustaremos la manera en la que funciona la visibilidad de los repositorios para que los conceptos público, interno y privado tengan un significado uniforme para los desarrolladores de {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %}. diff --git a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/best-practices-for-user-security.md b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/best-practices-for-user-security.md index ba3dc24ea2..ced3a2cf34 100644 --- a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/best-practices-for-user-security.md +++ b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/best-practices-for-user-security.md @@ -25,7 +25,7 @@ Para obtener más información sobre cómo configurar la autenticación de dos f ## Solicitar un administrador de contraseñas -We strongly recommend requiring your users to install and use a password manager--such as [LastPass](https://lastpass.com/) or [1Password](https://1password.com/)--on any computer they use to connect to your enterprise. Esto garantiza que las contraseñas sean más seguras y que sea menos probable que se vean comprometidas o sean robadas. +Te recomendamos ampliamente que requieras que tus usuarios instalen y utilicen un administrador de contraseñas--tal como [LastPass](https://lastpass.com/) o [1Password](https://1password.com/)-- en cualquier computadora que utilicen para conectarse a tu empresa. Esto garantiza que las contraseñas sean más seguras y que sea menos probable que se vean comprometidas o sean robadas. ## Restringir el acceso a equipos y repositorios diff --git a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md index 016da645b6..31f4e8ed11 100644 --- a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md +++ b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md @@ -20,7 +20,7 @@ topics: Hay varios tipos de mensajes de usuario. - Los mensajes que aparecen en la {% ifversion ghes %}página de ingreso o de {% endif %}salida{% ifversion ghes > 2.22 or ghae %} -- Mandatory messages, which appear once in a pop-up window that must be dismissed{% endif %}{% ifversion ghes or ghae %} +- Mensajes obligatorios, los cuales aparecen en una ventana emergente que debe cerrarse{% endif %}{% ifversion ghes or ghae %} - Letreros de anuncio, los cuales aparecen en la parte superior de cada página{% endif %} {% ifversion ghes %} @@ -83,8 +83,8 @@ Cada vez que un usuario vea un mensaje obligatorio, se crea un evento de bitáco {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -1. A la derecha de "Mensaje obligatorio", da clic en **Agregar mensaje**. ![Add mandatory message button](/assets/images/enterprise/site-admin-settings/add-mandatory-message-button.png) -1. Debajo de "Mensaje obligatorio", en la casilla de texto, teclea tu mensaje. ![Mandatory message text box](/assets/images/enterprise/site-admin-settings/mandatory-message-text-box.png) +1. A la derecha de "Mensaje obligatorio", da clic en **Agregar mensaje**. ![Botón de agregar mensaje obligatorio](/assets/images/enterprise/site-admin-settings/add-mandatory-message-button.png) +1. Debajo de "Mensaje obligatorio", en la casilla de texto, teclea tu mensaje. ![Caja de texto del mensaje obligatorio](/assets/images/enterprise/site-admin-settings/mandatory-message-text-box.png) {% data reusables.enterprise_site_admin_settings.message-preview-save %} {% endif %} diff --git a/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md b/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md index b7ed85ce5d..f344716cc7 100644 --- a/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md +++ b/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md @@ -54,8 +54,8 @@ topics: | ------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion ghes > 3.0 or ghae-next %} | `business.advanced_security_policy_update` | Un adminsitrador de sitio crea, actualiza o elimina una política para la {% data variables.product.prodname_GH_advanced_security %}. Para obtener más información, consulta la sección "[Requerir políticas para la {% data variables.product.prodname_advanced_security %} en tu empresa](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)".{% endif %} | `business.clear_members_can_create_repos` | Un administrador de sitio elimina una restricción para la creación de repositorios en las organizciones de la empresa. Para obtener más información, consulta la sección "[Requerir políticas de administración de repositorios en tu empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)".{% ifversion ghes > 3.1 %} -| `business.referrer_override_enable` | A site admin enables the referrer policy override. For more information, see "[Configuring the referrer policy for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)." | -| `business.referrer_override_disable` | A site admin disables the referrer policy override. For more information, see "[Configuring the referrer policy for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)."{% endif %} +| `business.referrer_override_enable` | Un administrador de sitio habilita la anulación de la política del referente. Para obtener más información, consulta la sección "[Configurar la política del referente para tu empresa](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)". | +| `business.referrer_override_disable` | Un administrador de sitio inhabilita la anulación de la política del referente. Para obtener más información, consulta la sección "[Configurar la política del referente para tu empresa](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)".{% endif %} | `business.update_member_repository_creation_permission` | Un administrador de sitio restringe la creación de repositorios en las organizaciones de la empresa. Para obtener más información, consulta la sección "[Requerir políticas de administración de repositorios en tu empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)".{% ifversion ghes %} | `enterprise.config.lock_anonymous_git_access` | Un administrador de sitio bloquea el acceso de lectura anónima a Git para prevenir que los administradores de repositorio cambien dicha configuración para los repositorios de la empresa. Para obtener más información consulta la sección "[Requerir políticas de administración de repositorios en tu empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)". | | `enterprise.config.unlock_anonymous_git_access` | Un administrador de sitio desbloquea el acceso de lectura anónima a Git para permitir que los administradores de repositorio cambien dicha configuración en los repositorios de la empresa. Para obtener más información, consulta la sección "[Requerir políticas de administración de repositorios en tu empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)".{% endif %} @@ -95,7 +95,7 @@ topics: ## Solicitudes de cambios -| Action | Description | | :- | :- |{% ifversion ghes > 3.1 or ghae-next %} | `pull_request.create` | A pull request was created. Para obtener más información, consulta la sección"[Crear una solicitud de extracción](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)." | | `pull_request.close` | A pull request was closed without being merged. For more information, see "[Closing a pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)." | | `pull_request.reopen` | A pull request was reopened after previously being closed. | | `pull_request.merge` | A pull request was merged. Para obtener más información, consulta "[Fusionar una solicitud de extracción](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)". | | `pull_request.indirect_merge` | A pull request was considered merged because the pull request's commits were merged into the target branch. | | `pull_request.ready_for_review` | A pull request was marked as ready for review. Para obtener más información, consulta la sección "[Cambiar el estado de una solicitud de extracción](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request#marking-a-pull-request-as-ready-for-review)". | | `pull_request.converted_to_draft` | A pull request was converted to a draft. Para obtener más información, consulta la sección "[Cambiar el estado de una solicitud de extracción](/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_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](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)". | | `pull_request.remove_review_request` | A review request was removed from a pull request. Para obtener más información, consulta la sección "[Acerca de las revisiones de las solicitudes de extracción](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)". | | `pull_request_review.submit` | A review was submitted for a pull request. Para obtener más información, consulta la sección "[Acerca de las revisiones de las solicitudes de extracción](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)". | | `pull_request_review.dismiss` | A review on a pull request was dismissed. Para obtener más información, consulta "[Descartar una revisión de solicitud de extracción](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)". | | `pull_request_review.delete` | A review on a pull request was deleted. | | `pull_request_review_comment.create` | A review comment was added to a pull request. Para obtener más información, consulta la sección "[Acerca de las revisiones de las solicitudes de extracción](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)". | | `pull_request_review_comment.update` | A review comment on a pull request was changed. |{% endif %} | `pull_request_review_comment.delete` | A review comment on a pull request was deleted. | +| Acción | Descripción| | :- | :- |{% ifversion ghes > 3.1 or ghae-next %} | `pull_request.create` | Se creó una solicitud de cambios. Para obtener más información, consulta la sección"[Crear una solicitud de extracción](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)." | | `pull_request.close` | Se cerró una solicitud de cambios sin haberse fusionado. Para obtener más información, consulta la sección "[Cerrar una solicitud de cambios](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)". | | `pull_request.reopen` | Se volvió a abrir una solicitud de cambios después de haberla cerrado previamente. | | `pull_request.merge` | Se fusionó una solicitud de cambios. Para obtener más información, consulta "[Fusionar una solicitud de extracción](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)". | | `pull_request.indirect_merge` | Se consideró a una solicitud de cambios como fusionada porque las confirmaciones de esta se fusionaron en la rama destino. | | `pull_request.ready_for_review` | Se marcó a una solicitud de cambios como lista para revisión. Para obtener más información, consulta la sección "[Cambiar el estado de una solicitud de extracción](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request#marking-a-pull-request-as-ready-for-review)". | | `pull_request.converted_to_draft` | Se convirtió a una solicitud de cambios en borrador. Para obtener más información, consulta la sección "[Cambiar el estado de una solicitud de extracción](/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_review_request` | Se solicitó una revisión en una solicitud de cambios. Para obtener más información, consulta la sección "[Acerca de las revisiones de las solicitudes de extracción](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)". | | `pull_request.remove_review_request` | Se eliminó una solicitud de revisión de una solicitud de cambios. Para obtener más información, consulta la sección "[Acerca de las revisiones de las solicitudes de extracción](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)". | | `pull_request_review.submit` | Se emitió una revisión para una solicitud de cambios. Para obtener más información, consulta la sección "[Acerca de las revisiones de las solicitudes de extracción](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)". | | `pull_request_review.dismiss` | Se descartó una revisión en una solicitud de cambios. Para obtener más información, consulta "[Descartar una revisión de solicitud de extracción](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)". | | `pull_request_review.delete` | Se eliminó una revisión en una solicitud de cambios. | | `pull_request_review_comment.create` | Se agregó un comentario de revisión a una solicitud de cambios. Para obtener más información, consulta la sección "[Acerca de las revisiones de las solicitudes de extracción](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)". | | `pull_request_review_comment.update` | Se cambió un comentario de revisión en una solicitud de cambios. |{% endif %} | `pull_request_review_comment.delete` | Se borró un comentario de revisión en una solicitud de cambios. | ## Ramas protegidas diff --git a/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/index.md b/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/index.md index 258139287e..eed79aaaff 100644 --- a/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/index.md +++ b/translations/es-ES/content/admin/user-management/monitoring-activity-in-your-enterprise/index.md @@ -1,6 +1,6 @@ --- title: Monitorear la actividad en tu empresa -intro: You can view activity by leveraging dashboards and logs in your enterprise. +intro: Puedes ver la actividad si aprovechas los tableros y bitácoras de tu empresa. redirect_from: - /enterprise/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance - /enterprise/admin/user-management/monitoring-activity-in-your-enterprise diff --git a/translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md b/translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md index ebe2ecd66f..e31ca92aa7 100644 --- a/translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md +++ b/translations/es-ES/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md @@ -30,6 +30,9 @@ Si nopuedes acceder a {% data variables.product.product_name %}, contacta al pro {% data reusables.saml.dotcom-saml-explanation %} Los propietarios de la organización pueden invitar a tu cuenta de usuario en {% data variables.product.prodname_dotcom %} para unirse a la organización que utiliza SAML SSO, lo cual te permite contribuir con ella y mantener tu identidad actual y las contribuciones con {% data variables.product.prodname_dotcom %}. +Si eres miembro de una {% data variables.product.prodname_emu_enterprise %}, utilizarás una cuenta nueva que se aprovisionará para ti. {% data reusables.enterprise-accounts.emu-more-info-account %} + + Cuando accedes a recurso dentro de la organización que utiliza SAML SSO, , {% data variables.product.prodname_dotcom %} te redirigirá a el SAML IdP de la organización para autenticarte. Después de que te autentiques exitosamente con tu cuenta en el IdP, este te redirigirá de vuelta a {% data variables.product.prodname_dotcom %}, en donde podrás acceder a los recursos de la organización. {% data reusables.saml.outside-collaborators-exemption %} diff --git a/translations/es-ES/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md b/translations/es-ES/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md index af9bbe5502..506460cf30 100644 --- a/translations/es-ES/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md +++ b/translations/es-ES/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md @@ -104,7 +104,7 @@ Después de agregar una nueva clave SSH a tu cuenta de {% data variables.product {% tip %} - **Tip:** Alternatively, you can locate the hidden `.ssh` folder, open the file in your favorite text editor, and copy it to your clipboard. + **Tip:** Como alternativa, puedes ubicar la carpeta `.ssh` oculta, abrir el archivo en tu editor de texto favorito y copiarlo a tu portapapeles. {% endtip %} @@ -124,7 +124,7 @@ Después de agregar una nueva clave SSH a tu cuenta de {% data variables.product {% data reusables.cli.cli-learn-more %} -To add an SSH key to your GitHub account, use the `ssh-key add` subcommand, specifying your public key. +Para agergar una clave SSH a tu cuenta de GitHub, utiliza el subcomando `ssh-key add`, especificando tu llave pública. ```shell gh ssh-key add key-file diff --git a/translations/es-ES/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md b/translations/es-ES/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md index 44fd822edc..561a4d6749 100644 --- a/translations/es-ES/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md +++ b/translations/es-ES/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md @@ -20,7 +20,7 @@ shortTitle: Generar una llave SSH nueva Si todavía no tienes una llave SSH, debes generar una nueva para utilizarla para autenticación. Si no estás seguro si ya tienes una llave SSH, puedes verificar si hay llaves existentes. Para obtener más información, consulta la sección "[Verificar si hay llaves SSH existentes](/github/authenticating-to-github/checking-for-existing-ssh-keys)". -{% ifversion fpt %} +{% ifversion fpt or ghae-next or ghes > 3.1 %} Si quieres utilizar una llave de seguridad de hardware para autenticarte en {% data variables.product.product_name %}, debes generar una llave SSH nueva para esta. Debes conectar tu llave de seguridad de hardware a tu computadora cuando te autentiques con el par de llaves. Para obtener más información, consulta las[notas de lanzamiento de OpenSSH 8.2](https://www.openssh.com/txt/release-8.2). @@ -31,6 +31,12 @@ Si no deseas volver a ingresar tu contraseña cada vez que usas tu clave SSH, pu {% data reusables.command_line.open_the_multi_os_terminal %} 2. Pega el siguiente texto, que sustituye tu dirección de correo electrónico en {% data variables.product.product_name %}. + {% ifversion ghae %} + + ```shell + $ ssh-keygen -t rsa -b 4096 -C "your_email@example.com" + ``` + {% else %} ```shell $ ssh-keygen -t ed25519 -C "your_email@example.com" ``` @@ -38,20 +44,22 @@ Si no deseas volver a ingresar tu contraseña cada vez que usas tu clave SSH, pu **Nota:** Si estás utilizando un sistema tradicional que no es compatible con el algoritmo Ed25519, utiliza: ```shell - $ ssh-keygen -t rsa -b 4096 -C "your_email@example.com" + $ ssh-keygen -t rsa -b 4096 -C "your_email@example.com" ``` {% endnote %} - This creates a new SSH key, using the provided email as a label. + {% endif %} + + Esto crea una llave SSH utilizando el correo electrónico proporcionado como etiqueta. ```shell - > Generating public/private ed25519 key pair. + > Generating public/private algorithm key pair. ``` 3. Cuando se te indique "Ingresar un archivo donde guardar la clave", presiona Intro. Al hacerlo aceptas la ubicación predeterminada del archivo. {% mac %} ```shell - > Enter a file in which to save the key (/Users/you/.ssh/id_ed25519): [Press enter] + > Enter a file in which to save the key (/Users/you/.ssh/id_algorithm): [Press enter] ``` {% endmac %} @@ -59,7 +67,7 @@ Si no deseas volver a ingresar tu contraseña cada vez que usas tu clave SSH, pu {% windows %} ```shell - > Enter a file in which to save the key (/c/Users/you/.ssh/id_ed25519):[Press enter] + > Enter a file in which to save the key (/c/Users/you/.ssh/id_algorithm):[Press enter] ``` {% endwindows %} @@ -67,7 +75,7 @@ Si no deseas volver a ingresar tu contraseña cada vez que usas tu clave SSH, pu {% linux %} ```shell - > Enter a file in which to save the key (/home/you/.ssh/id_ed25519): [Press enter] + > Enter a file in which to save the key (/home/you/.ssh/algorithm): [Press enter] ``` {% endlinux %} @@ -107,7 +115,7 @@ Antes de agregar una llave SSH nueva al ssh-agent para que administre tus llaves Host * AddKeysToAgent yes UseKeychain yes - IdentityFile ~/.ssh/id_ed25519 + IdentityFile ~/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %} ``` {% note %} @@ -137,11 +145,11 @@ Antes de agregar una llave SSH nueva al ssh-agent para que administre tus llaves 3. Agrega tu llave privada SSH al ssh-agent y almacena tu contraseña en tu keychain. {% data reusables.ssh.add-ssh-key-to-ssh-agent %} ```shell - $ ssh-add -K ~/.ssh/id_ed25519 + $ ssh-add -K ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %} ``` {% note %} - **Note:** The `-K` option is Apple's standard version of `ssh-add`, which stores the passphrase in your keychain for you when you add an SSH key to the ssh-agent. Si eliges no agregar una frase de acceso a tu llave, ejecuta el comando sin la opción `-K`. + **Nota:** La opción `-K` es una versión estándar de Apple de `ssh-add`, que almacena la contraseña en tu keychain cuando agregas una llave SSH al ssh-agent. Si eliges no agregar una frase de acceso a tu llave, ejecuta el comando sin la opción `-K`. Si no tienes instalada la versión estándar de Apple, puedes recibir un mensaje de error. Para obtener más información sobre cómo resolver este error, consulta "[Error: ssh-add: opción ilegal -- K](/articles/error-ssh-add-illegal-option-k)". @@ -189,8 +197,10 @@ Si estás utilizando macOS o Linux, puede que necesites actualizar tu cliente SS {% data reusables.command_line.open_the_multi_os_terminal %} 3. Pega el siguiente texto, sustitutyendo la dirección de correo electrónico por tu cuenta de {% data variables.product.product_name %}. ```shell - $ ssh-keygen -t ed25519-sk -C "your_email@example.com" + $ ssh-keygen -t {% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}-sk -C "your_email@example.com" ``` + + {% ifversion not ghae %} {% note %} **Nota:** Si el comando falla y recibes el error `invalid format` o `feature not supported,` puede que estés utilizando una llave de seguridad de hardware que no sea compatible con el algoritmo Ed25519. En vez de esto, ingresa el siguiente comando. @@ -199,13 +209,14 @@ Si estás utilizando macOS o Linux, puede que necesites actualizar tu cliente SS ``` {% endnote %} + {% endif %} 4. Cuando se te solicite, pulsa el botón en tu llave de seguridad de hardware. 5. Cuando se te pida "Ingresar un archivo en donde se pueda guardar la llave", teclea Enter para aceptar la ubicación predeterminada. {% mac %} ```shell - > Enter a file in which to save the key (/Users/you/.ssh/id_ed25519_sk): [Press enter] + > Enter a file in which to save the key (/Users/you/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): [Press enter] ``` {% endmac %} @@ -213,7 +224,7 @@ Si estás utilizando macOS o Linux, puede que necesites actualizar tu cliente SS {% windows %} ```shell - > Enter a file in which to save the key (/c/Users/you/.ssh/id_ed25519_sk):[Press enter] + > Enter a file in which to save the key (/c/Users/you/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk):[Press enter] ``` {% endwindows %} @@ -221,7 +232,7 @@ Si estás utilizando macOS o Linux, puede que necesites actualizar tu cliente SS {% linux %} ```shell - > Enter a file in which to save the key (/home/you/.ssh/id_ed25519_sk): [Press enter] + > Enter a file in which to save the key (/home/you/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): [Press enter] ``` {% endlinux %} diff --git a/translations/es-ES/content/authentication/connecting-to-github-with-ssh/index.md b/translations/es-ES/content/authentication/connecting-to-github-with-ssh/index.md index 8b48aa8ebf..bb83e2f2a5 100644 --- a/translations/es-ES/content/authentication/connecting-to-github-with-ssh/index.md +++ b/translations/es-ES/content/authentication/connecting-to-github-with-ssh/index.md @@ -1,6 +1,6 @@ --- title: Conectar a GitHub con SSH -intro: 'You can connect to {% data variables.product.product_name %} using the Secure Shell Protocol (SSH), which provides a secure channel over an unsecured network.' +intro: 'Puedes conectarte a {% data variables.product.product_name %} utilizando el Protocolo de Secure Shell (SSH), lo cual proporciona un canal seguro sobre una red insegura.' redirect_from: - /key-setup-redirect/ - /linux-key-setup/ 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 7e7f182071..17aa82d4f2 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 @@ -28,6 +28,10 @@ Puedes acceder a tus recursos en {% data variables.product.product_name %} de mu Puedes autenticarte en {% data variables.product.product_name %} en tu buscador {% ifversion ghae %} utilizando tu IdP. Para obtener más información, consulta la sección "[Acera de la autenticación con el inicio de sesión único de SAML](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)".{% else %} de varias formas. +- {% ifversion fpt %} +Si eres miembro de una {% data variables.product.prodname_emu_enterprise %}, te autenticarás en {% data variables.product.product_name %} en tu buscador utilizando tu IdP. Para obtener más información , consulta la sección "[Autenticarte como un usuario administrado](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users#authenticating-as-a-managed-user)". Si no eres miembro de una {% data variables.product.prodname_emu_enterprise %}, te autenticarás utilizando tu buscador en {% data variables.product.prodname_dotcom_the_website %}. +{% endif %} + - **Nombre de usuario y contraseña únicamente** - Crearás una contraseña cuando crees tu cuenta de usuario en {% data variables.product.product_name %}. Te recomendamos que utilices un administrador de contraseñas para generar una contraseña aleatoria y única. Para obtener más información, consulta la sección "[Crear una contraseña fuerte](/github/authenticating-to-github/creating-a-strong-password)". - **Autenticación de dos factores (2FA)** (recomendada) @@ -58,19 +62,19 @@ Puedes acceder a los repositorios en {% data variables.product.product_name %} d Puedes trabajar con todos los repositorios en {% data variables.product.product_name %} a través de HTTPS, aún si estás detrás de un cortafuegos o de un 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). +Si te autenticas con el {% data variables.product.prodname_cli %}, puedes ya sea autenticarte con un token de acceso personal o a través del buscador web. Para obtener más información sobre cómo autenticarte con el {% data variables.product.prodname_cli %}, consulta la sección [`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). +Si te autenticas sin el {% data variables.product.prodname_cli %}, debes autenticarte con un token de acceso personal. {% data reusables.user_settings.password-authentication-deprecation %} Cada que utilices Git para autenticarte con {% data variables.product.product_name %}, se te pedirá que ingreses tus credenciales para autenticarte con {% data variables.product.product_name %} a menos de que las guardes en caché en un [ayudante para credenciales](/github/getting-started-with-github/caching-your-github-credentials-in-git). ### SSH Puedes trabajar con todos los repositorios en {% data variables.product.product_name %} a través de SSH, aunque los cortafuegos y los proxys podrían rehusarse a permitir las conexiones de SSH. -If you authenticate with {% data variables.product.prodname_cli %}, the CLI will find SSH public keys on your machine and will prompt you to select one for upload. If {% data variables.product.prodname_cli %} does not find a SSH public key for upload, it can generate a new SSH public/private keypair and upload the public key to your {% data variables.product.product_name %} account. Then, 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). +Si te autenticas con el{% data variables.product.prodname_cli %}, este encontrará llaves SSH públicas en tu máquina y te pedirá seleccionar una para cargar. Si el {% data variables.product.prodname_cli %}no encuentra una llave SSH pública para cargar, puede generar un par de llaves SSH pública/privada y cargar la llave pública a tu cuenta de {% data variables.product.product_name %}. Entonces podrás ya sea autenticarte con un token de acceso personal o a través del buscador web. Para obtener más información sobre cómo autenticarte con el {% data variables.product.prodname_cli %}, consulta la sección [`gh auth login`](https://cli.github.com/manual/gh_auth_login). -If you authenticate without {% data variables.product.prodname_cli %}, you will need to generate an SSH public/private keypair on your local machine and add the public key to your {% data variables.product.product_name %} account. Para obtener más información, consulta "[Generar una nueva llave SSH y agregarla a ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." Cada que utilizas Git para autenticarte con {% data variables.product.product_name %}, se te solicitará que ingreses tu frase de ingreso de la llave SSH, a menos de que hayas [almacenado la llave](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent). +Si te autenticas sin el {% data variables.product.prodname_cli %}, necesitarás generar un par de llaves SSH pública/privada en tu máquina local y agregar la llave pública a tu cuenta de {% data variables.product.product_name %}. Para obtener más información, consulta "[Generar una nueva llave SSH y agregarla a ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." Cada que utilizas Git para autenticarte con {% data variables.product.product_name %}, se te solicitará que ingreses tu frase de ingreso de la llave SSH, a menos de que hayas [almacenado la llave](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent). -### Authorizing for SAML single sign-on +### Autorizar para el inicio de sesión única de SAML {% ifversion fpt %}Para utilizar un token de acceso personal o una llave de SSH para acceder a los recursos que le pertenecen a una organización que utiliza el inicio de sesión único de SAML, también deberás autorizar el token personal o la llave SSH. Para obtener más información, consulta la sección "[Autorizar un token de acceso personal para utilizarlo con el inicio de sesión único de SAML](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" o la sección "[Autorizar una llave SSH para su uso con el inicio de sesión único de SAML](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)".{% endif %} diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/authorizing-github-apps.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/authorizing-github-apps.md index 2a5433cd93..7e7928c7b1 100644 --- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/authorizing-github-apps.md +++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/authorizing-github-apps.md @@ -1,6 +1,6 @@ --- -title: Authorizing GitHub Apps -intro: 'You can authorize a {% data variables.product.prodname_github_app %} to allow an application to retrieve information about your {% data variables.product.prodname_dotcom %} account and, in some circumstances, to make changes on {% data variables.product.prodname_dotcom %} on your behalf.' +title: Autorizar las GitHub Apps +intro: 'Puedes autorizar a una {% data variables.product.prodname_github_app %} para que permita que una aplicación recupere información sobre tu cuenta de {% data variables.product.prodname_dotcom %} y, en algunos casos, para hacer cambios en {% data variables.product.prodname_dotcom %} en tu nombre.' versions: fpt: '*' ghes: '*' @@ -12,41 +12,41 @@ redirect_from: - /github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-github-apps --- -Third-party applications that need to verify your {% data variables.product.prodname_dotcom %} identity, or interact with the data on {% data variables.product.prodname_dotcom %} on your behalf, can ask you to authorize the {% data variables.product.prodname_github_app %} to do so. +Las aplicaciones de terceros que necesitan verificar tu identidad de {% data variables.product.prodname_dotcom %} o interactuar con los datos de {% data variables.product.prodname_dotcom %} en tu nombre pueden pedirte que autorices la {% data variables.product.prodname_github_app %} para hacerlo. -When authorizing the {% data variables.product.prodname_github_app %}, you should ensure you trust the application, review who it's developed by, and review the kinds of information the application wants to access. +Al autorizar la {% data variables.product.prodname_github_app %}, deberías asegurarte de que confías en la aplicación, revisar quién la desarrolló y revisar los tipos de información a la que desea acceder la aplicación. -During authorization, you'll be prompted to grant the {% data variables.product.prodname_github_app %} permission to: -* **Verify your {% data variables.product.prodname_dotcom %} identity**
When authorized, the {% data variables.product.prodname_github_app %} will be able to programmatically retrieve your public GitHub profile, as well as some private details (such as your email address), depending on the level of access requested. -* **Know which resources you can access**
When authorized, the {% data variables.product.prodname_github_app %} will be able to programmatically read the _private_ {% data variables.product.prodname_dotcom %} resources that you can access (such as private {% data variables.product.prodname_dotcom %} repositories) _where_ an installation of the {% data variables.product.prodname_github_app %} is also present. The application may use this, for example, so that it can show you an appropriate list of repositories. -* **Act on your behalf**
The application may need to perform tasks on {% data variables.product.prodname_dotcom %}, as you. This might include creating an issue, or commenting on a pull request. This ability to act on your behalf is limited to the {% data variables.product.prodname_dotcom %} resources where _both_ you and the {% data variables.product.prodname_github_app %} have access. In some cases, however, the application may never make any changes on your behalf. +Durante la autorización, se te pedirá que otorgues el permiso de {% data variables.product.prodname_github_app %} para: +* **Verifica tu identidad de {% data variables.product.prodname_dotcom %}**
Cuando se te autorice, la {% data variables.product.prodname_github_app %} podrá recuperar tu perfil público de GitHub mediante programación, así como algunos detalles privados (tal como tu dirección de correo electrónico), dependiendo del nivel de acceso solicitado. +* **Puedes saber a qué recursos puedes acceder**
Cuando se te autorice, la {% data variables.product.prodname_github_app %} podrá leer mediante programación los recursos _privados_ {% data variables.product.prodname_dotcom %} a los que puedes acceder (tales como los repositorios privados de {% data variables.product.prodname_dotcom %}) _en donde_ también está presente una instalación de la {% data variables.product.prodname_github_app %}. La aplicación podría utilizar esto, por ejemplo, para que pueda mostrarte una lista adecuada de repositorios. +* **Actuar en tu nombre**
La aplicación podría necesitar realizar tareas en {% data variables.product.prodname_dotcom %} como si fueras tú. Esto podría incluir el crear una propuesta o comentar en una solicitud de cambios. Esta capacidad de actuar en tu nombre se limita a los recursos de {% data variables.product.prodname_dotcom %} en donde _tanto_ tú como la {% data variables.product.prodname_github_app %} tengan acceso. Sin embargo, en algunos casos, la aplicación podría jamás hacer cambios en tu nombre. -## When does a {% data variables.product.prodname_github_app %} act on your behalf? +## ¿Cuándo actúa una {% data variables.product.prodname_github_app %} en tu nombre? -The situations in which a {% data variables.product.prodname_github_app %} acts on your behalf vary according to the purpose of the {% data variables.product.prodname_github_app %} and the context in which it is being used. +Las situaciones en las cuales una {% data variables.product.prodname_github_app %} actúa en tu nombre varían de acuerdo con el propósito de la {% data variables.product.prodname_github_app %} y el contexto en el cual se utiliza. -For example, an integrated development environment (IDE) may use a {% data variables.product.prodname_github_app %} to interact on your behalf in order to push changes you have authored through the IDE back to repositories on {% data variables.product.prodname_dotcom %}. The {% data variables.product.prodname_github_app %} will achieve this through a [user-to-server request](/get-started/quickstart/github-glossary#user-to-server-request). +Por ejemplo, un ambiente de desarrollo integrado (IDE) podría utilizar una {% data variables.product.prodname_github_app %} para interactuar en tu nombre para subir los cambios que son de tu autoría a través del IDE de vuelta a los repositorios en {% data variables.product.prodname_dotcom %}. La {% data variables.product.prodname_github_app %} logrará esto mediante una [solicitud de usuario a servidor](/get-started/quickstart/github-glossary#user-to-server-request). -When a {% data variables.product.prodname_github_app %} acts on your behalf in this way, this is identified on GitHub via a special icon that shows a small avatar for the {% data variables.product.prodname_github_app %} overlaid onto your own avatar, similar to the one shown below. +Cuando una {% data variables.product.prodname_github_app %} actúa en tu nombre de esta forma, esto lo identifica GitHub a través de un icono especial que muestra un avatar pequeño de la {% data variables.product.prodname_github_app %} sobre tu propio avatar, similar al que se muestra a continuación. -![An issue created by a "user-to-server" request from a {% data variables.product.prodname_github_app %}](/assets/images/help/apps/github-apps-new-issue.png) +![Una propuesta que creó una solicitud de "usuario a servidor" desde una {% data variables.product.prodname_github_app %}](/assets/images/help/apps/github-apps-new-issue.png) -## To what extent can a {% data variables.product.prodname_github_app %} know which resources you can access and act on your behalf? +## ¿Hasta qué punto puede una {% data variables.product.prodname_github_app %} saber a qué recursos puedes acceder y actuar en tu nombre? -The extent to which a {% data variables.product.prodname_github_app %} can know which resources you can access and act on your behalf, after you have authorized it, is limited by: +El grado en el que una {% data variables.product.prodname_github_app %} puede saber a qué recursos puedes acceder y actuar en tu nombre, después de que la has autorizado, se limita por: -* The organizations or repositories on which the app is installed -* The permissions the app has requested -* Your access to {% data variables.product.prodname_dotcom %} resources +* Las organizaciones o repositorios en los cuales se instaló la app +* Los permisos que la app solicitó +* Tu acceso a los recursos de {% data variables.product.prodname_dotcom %} -Let's use an example to explain this. +Utilicemos un ejemplo para explicar esto. -{% data variables.product.prodname_dotcom %} user Alice logs into a third-party web application, ExampleApp, using their {% data variables.product.prodname_dotcom %} identity. During this process, Alice authorizes ExampleApp to perform actions on their behalf. +{% data variables.product.prodname_dotcom %} el usuario Alice inicia sesión en una aplicación web de un tercero, ExampleApp, utilizando su identidad de {% data variables.product.prodname_dotcom %}. Durante este proceso, Alice autoriza a ExampleApp para que realice acciones en su nombre. -However, the activity ExampleApp is able to perform on Alice's behalf in {% data variables.product.prodname_dotcom %} is constrained by: the repositories on which ExampleApp is installed, the permissions ExampleApp has requested, and Alice's access to {% data variables.product.prodname_dotcom %} resources. +Sin embargo, la actividad que ExampleApp puede realizar en nombre de Alice en {% data variables.product.prodname_dotcom %} está limitada por: los repositorios en los cuales se instaló ExampleApp, los permisos que solicitó ExampleApp y el acceso de Alice a los recursos de {% data variables.product.prodname_dotcom %}. -This means that, in order for ExampleApp to create an issue on Alice's behalf, in a repository called Repo A, all of the following must be true: +Esto significa que, para que la ExampleApp cree una propuesta en nombre de Alice, en un repositorio llamado Repo A, todo lo siguiente debe suceder: -* ExampleApp's {% data variables.product.prodname_github_app %} requests write access to issues. -* A user having admin access for Repo A must have installed ExampleApp's {% data variables.product.prodname_github_app %} on Repo A. -* Alice must have read permission for Repo A. For information about which permissions are required to perform various activities, see "[Repository permission levels for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization#repository-access-for-each-permission-level)." +* La {% data variables.product.prodname_github_app %} de ExampleApp solicita acceso de escritura para las propuestas. +* Un usuario que tiene acceso administrativo para el Repo A debe tener instalada la {% data variables.product.prodname_github_app %} de ExampleApp en este. +* Alice debe tener permisos de lectura para el Repo A. Para obtener más información sobre qué permisos se requieren para realizar diversas actividades, consulta la sección "[Niveles de permiso de repositorio para una organización](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization#repository-access-for-each-permission-level)". diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md index d7f5ee65d8..c94c460841 100644 --- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md +++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md @@ -28,7 +28,7 @@ Cuando una {% data variables.product.prodname_oauth_app %} quiere identificarte ## Acceso a {% data variables.product.prodname_oauth_app %} -{% data variables.product.prodname_oauth_apps %} can have *read* or *write* access to your {% data variables.product.product_name %} data. +Las {% data variables.product.prodname_oauth_apps %} pueden tener acceso de *lectura* o *escritura* en tus datos de {% data variables.product.product_name %}. - El **acceso de lectura** solo permite que una app *mire* tus datos. - El **acceso de escritura** permite que una app *cambie* tus datos. @@ -43,7 +43,7 @@ Cuando una {% data variables.product.prodname_oauth_app %} quiere identificarte Los *alcances* son los grupos de permiso denominados que una {% data variables.product.prodname_oauth_app %} puede solicitar para acceder a datos públicos y no públicos. -Cuando quieres usar una {% data variables.product.prodname_oauth_app %} que se integra con {% data variables.product.product_name %}, la app te permite conocer qué tipo de acceso a tus datos serán necesarios. Si otorgas acceso a la app, la app podrá realizar acciones en tu nombre, como leer o modificar datos. Por ejemplo, si quieres usar una app que solicita el alcance `usuario:correo electrónico`, la app solo tendrá acceso de lectura a tus direcciones de correo electrónico privado. For more information, see "[About scopes for {% data variables.product.prodname_oauth_apps %}](/apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps)." +Cuando quieres usar una {% data variables.product.prodname_oauth_app %} que se integra con {% data variables.product.product_name %}, la app te permite conocer qué tipo de acceso a tus datos serán necesarios. Si otorgas acceso a la app, la app podrá realizar acciones en tu nombre, como leer o modificar datos. Por ejemplo, si quieres usar una app que solicita el alcance `usuario:correo electrónico`, la app solo tendrá acceso de lectura a tus direcciones de correo electrónico privado. Para obtener más información, consulta la sección "[Acerca de los alcances para {% data variables.product.prodname_oauth_apps %}](/apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps)". {% tip %} @@ -55,7 +55,7 @@ Cuando quieres usar una {% data variables.product.prodname_oauth_app %} que se i ### Tipos de datos solicitados -{% data variables.product.prodname_oauth_apps %} can request several types of data. +Las {% data variables.product.prodname_oauth_apps %} pueden solicitar diferentes tipos de datos. | Tipos de datos | Descripción | | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -71,30 +71,30 @@ Cuando quieres usar una {% data variables.product.prodname_oauth_app %} que se i ## Solicitar permisos actualizados -When {% data variables.product.prodname_oauth_apps %} request new access permissions, they will notify you of the differences between their current permissions and the new permissions. +Cuando las {% data variables.product.prodname_oauth_apps %} solicitan permisos de acceso nuevos, te notificarán sobre las diferencias entre los permisos actuales y los permisos nuevos. {% ifversion fpt %} -## {% data variables.product.prodname_oauth_apps %} and organizations +## {% data variables.product.prodname_oauth_apps %} y organizaciones Cuando autorizas una {% data variables.product.prodname_oauth_app %} para tu cuenta de usuario personal, verás cómo la autorización afectará a cada organización de la que eres miembro. - **Para organizaciones *con restricciones de acceso a * {% data variables.product.prodname_oauth_app %}, puedes solicitar que los administradores de la organización aprueben la aplicación para usar en esa organización.** Si la organización no aprueba la aplicación, la aplicación solo podrá acceder a los recursos públicos de la organización. Si eres administrador de una organización, puedes [aprobar la aplicación](/articles/approving-oauth-apps-for-your-organization) por tu cuenta. -- **For organizations *without* {% data variables.product.prodname_oauth_app %} access restrictions, the application will automatically be authorized for access to that organization's resources.** For this reason, you should be careful about which {% data variables.product.prodname_oauth_apps %} you approve for access to your personal account resources as well as any organization resources. +- **En el caso de las organizaciones *sin* restricciones de aceso a {% data variables.product.prodname_oauth_app %}, la aplicación se autorizará automáticamente para el acceso alos recursos de dicha organización.** Es por esto que debes tener cuidado con qué {% data variables.product.prodname_oauth_apps %} apruebas para que tengan acceso a los recursos de tu cuenta personal, así como para cualquier recurso de la organización. Si perteneces a cualquier organizacion que imponga el inicio de sesión único de SAML, debes tener una sesión activa de SAML para cada organización cada vez que autorices un {% data variables.product.prodname_oauth_app %}. {% note %} -**Note:** If you are encountering errors authenticating to an organization that enforces SAML single sign-on, you may need to revoke the OAuth App from your [account settings page](https://github.com/settings/applications) and repeat the authentication flow to reauthorize the app. +**Nota:** Si te encuentras errores al autenticarte en una organización que requiera el inicio de sesión único de SAML, podrías necesitar revocar la OAuth App de tu [página de ajustes de cuenta](https://github.com/settings/applications) y repetir el flujo de autenticación para volver a autorizar a la app. {% endnote %} ## Leer más - "[Acerca de las restricciones de acceso a {% data variables.product.prodname_oauth_app %}](/articles/about-oauth-app-access-restrictions)" -- "[Authorizing GitHub Apps](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-github-apps)" +- "[Autorizar las GitHub Apps](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-github-apps)" - "[Soporte técnico de {% data variables.product.prodname_marketplace %}](/articles/github-marketplace-support)" {% endif %} diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md index c391383d5d..503ec0cd3a 100644 --- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md +++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md @@ -38,7 +38,7 @@ Las aplicaciones pueden tener acceso de *lectura* o *escritura* a tus datos de { *Alcances* son grupos de permisos designados que una aplicación puede solicitar para acceder a los datos públicos y no públicos. -Cuando quieres usar una aplicación de terceros que se integra con {% data variables.product.product_name %}, esa aplicación te permite conocer qué tipo de acceso a tus datos serán necesarios. Si otorgas acceso a la aplicación, la aplicación podrá realizar acciones en tu nombre, como leer o modificar datos. Por ejemplo, si quieres usar una app que solicita el alcance `usuario:correo electrónico`, la app solo tendrá acceso de lectura a tus direcciones de correo electrónico privado. For more information, see "[About scopes for {% data variables.product.prodname_oauth_apps %}](/apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps)." +Cuando quieres usar una aplicación de terceros que se integra con {% data variables.product.product_name %}, esa aplicación te permite conocer qué tipo de acceso a tus datos serán necesarios. Si otorgas acceso a la aplicación, la aplicación podrá realizar acciones en tu nombre, como leer o modificar datos. Por ejemplo, si quieres usar una app que solicita el alcance `usuario:correo electrónico`, la app solo tendrá acceso de lectura a tus direcciones de correo electrónico privado. Para obtener más información, consulta la sección "[Acerca de los alcances para {% data variables.product.prodname_oauth_apps %}](/apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps)". {% tip %} 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 9e1875f270..8f6305faf4 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 @@ -20,7 +20,7 @@ shortTitle: Crear un PAT {% note %} -**Note:** If you use {% data variables.product.prodname_cli %} to authenticate to {% data variables.product.product_name %} on the command line, you can skip generating a personal access token and authenticate via the web browser instead. For more information about authenticating with {% data variables.product.prodname_cli %}, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login). +**Nota:** Si utilizas el {% data variables.product.prodname_cli %} para autenticarte en {% data variables.product.product_name %} en la línea de comandos, puedes omitir el generar un token de acceso personal y autenticarte a través del buscador web en su lugar. Para obtener más información sobre cómo autenticarte con el {% data variables.product.prodname_cli %}, consulta la sección [`gh auth login`](https://cli.github.com/manual/gh_auth_login). {% endnote %} @@ -30,7 +30,7 @@ Los tokens de acceso personal (PAT) son una alternativa al uso de contraseñas p {% ifversion fpt %}{% data reusables.user_settings.removes-personal-access-tokens %}{% endif %} -A token with no assigned scopes can only access public information. Para usar tu token para acceder a repositorios desde la línea de comando, selecciona `repo`. For more information, see “[Available scopes](/apps/building-oauth-apps/scopes-for-oauth-apps#available-scopes)”. +Un token sin alcances asignados solo puede acceder a información pública. Para usar tu token para acceder a repositorios desde la línea de comando, selecciona `repo`. Para obtener más información, consulta la sección "[Alcances disponibles](/apps/building-oauth-apps/scopes-for-oauth-apps#available-scopes)". ## Crear un token @@ -38,9 +38,9 @@ A token with no assigned scopes can only access public information. Para usar tu {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.developer_settings %} {% data reusables.user_settings.personal_access_tokens %} -4. Haz clic en **Generar un nuevo token**. ![Generar el botón para el nuevo token](/assets/images/help/settings/generate_new_token.png) +{% 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 %} -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 %} +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 %} ![Seleccionar los alcances del token](/assets/images/help/settings/token_scopes.gif) @@ -75,5 +75,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 %} -- "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %} +- "[Acerca de la autenticación en GitHub](/github/authenticating-to-github/about-authentication-to-github)"{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 %} +- "[Vencimiento y revocación de tokens](/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/githubs-ssh-key-fingerprints.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md index e6677581a6..b2192b5d91 100644 --- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md +++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md @@ -19,11 +19,11 @@ Estas son las huellas dactilares de la llave pública de {% data variables.produ - `SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8` (RSA) -These keys will be supported beginning September 14, 2021: +Estas llaves serán compatibles dese el 14 de septiembre de 2021: - `SHA256:p2QAMXNIC1TJYWeIOttrVc98/R1BUFWu3/LiyKgUfQM` (ECDSA) - `SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU` (Ed25519) -This key will be sunset on November 16, 2021: +Esta llave se extinguirá el 16 de noviembre de 2021: - `SHA256:br9IjFspm1vxR3iA35FWE+4VTyz1hYVLIE2t1/CeyWQ` (DSA) 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 8f25add258..0f29b3c1bb 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 @@ -1,6 +1,6 @@ --- title: Eliminar datos confidenciales de un repositorio -intro: 'Si confirmas datos confidenciales, como una contraseña o clave SSH en un repositorio de Git, puedes eliminarlos del historial. To entirely remove unwanted files from a repository''s history you can use either the `git filter-repo` tool or the BFG Repo-Cleaner open source tool.' +intro: 'Si confirmas datos confidenciales, como una contraseña o clave SSH en un repositorio de Git, puedes eliminarlos del historial. Para eliminar archivos no deseados por completo del historial de un repositorio, puedes utilizar ya sea la herramienta `git filter-repo` o la herramienta de código abierto BFG Repo-Cleaner.' redirect_from: - /remove-sensitive-data/ - /removing-sensitive-data/ @@ -18,21 +18,21 @@ topics: shortTitle: Eliminar los datos sensibles --- -The `git filter-repo` tool and the BFG Repo-Cleaner rewrite your repository's history, which changes the SHAs for existing commits that you alter and any dependent commits. Las SHA de confirmación modificadas pueden afectar las solicitudes de extracción abiertas de tu repositorio. Recomendamos fusionar o cerrar todas las solicitudes de extracción abiertas antes de eliminar archivos de tu repositorio. +La herramienta `git filter-repo` y el BFG Repo-Cleaner reescriben el historial de tu repositorio, el cual cambia los SHA para las confirmaciones existentes que alteras y cualquier confirmación dependiente. Las SHA de confirmación modificadas pueden afectar las solicitudes de extracción abiertas de tu repositorio. Recomendamos fusionar o cerrar todas las solicitudes de extracción abiertas antes de eliminar archivos de tu repositorio. -Puedes eliminar el archivo desde la última confirmación con `git rm`. For information on removing a file that was added with the latest commit, see "[About large files on {% data variables.product.prodname_dotcom %}](/repositories/working-with-files/managing-large-files/about-large-files-on-github#removing-files-from-a-repositorys-history)." +Puedes eliminar el archivo desde la última confirmación con `git rm`. Para obtener más información sobre cómo eliminar un archivo que se agregó con la última confirmación, consulta la sección "[Acerca de los archivos grandes en {% data variables.product.prodname_dotcom %}](/repositories/working-with-files/managing-large-files/about-large-files-on-github#removing-files-from-a-repositorys-history)". {% warning %} -Este artículo te explica cómo hacer confirmaciones con datos confidenciales inaccesibles desde cualquier rama o etiqueta en tu {% data variables.product.product_name %} repositorio. 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. 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 %}. +Este artículo te explica cómo hacer confirmaciones con datos confidenciales inaccesibles desde cualquier rama o etiqueta en tu {% data variables.product.product_name %} repositorio. 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: 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. 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. +**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. {% endwarning %} ## Purgar un archivo del historial de tu repositorio -You can purge a file from your repository's history using either the `git filter-repo` tool or the BFG Repo-Cleaner open source tool. +Puedes purgar un archivo del historial de tu repositorio utilizando ya sea la herramienta `git filter-repo` o la herramienta de código abierto BFG Repo-Cleaner. ### Usar el BFG @@ -58,21 +58,21 @@ $ git push --force Consulta los documentos de [BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/) para obtener todas las indicaciones para el uso y la descarga. -### Using git filter-repo +### Utilizar git filter-repo {% warning %} -**Warning:** If you run `git filter-repo` after stashing changes, you won't be able to retrieve your changes with other stash commands. Before running `git filter-repo`, we recommend unstashing any changes you've made. Para dejar de acumular el último conjunto de cambios que hayas acumulado, ejecuta `git stash show -p | git apply -R`. For more information, see [Git Tools - Stashing and Cleaning](https://git-scm.com/book/en/v2/Git-Tools-Stashing-and-Cleaning). +**Advertencia:** si ejecutas `git filter-repo` después de haber acumulado cambios, no podrás retribuir tus cambios con otros comandos acumulados. Antes de ejecutar `git filter-repo`, te recomendamos anular la acumulación de cualquier cambio que hayas hecho. Para dejar de acumular el último conjunto de cambios que hayas acumulado, ejecuta `git stash show -p | git apply -R`. Para obtener más información, consulta la sección [Herramientas - Almacenar y Limpiar](https://git-scm.com/book/en/v2/Git-Tools-Stashing-and-Cleaning). {% endwarning %} -To illustrate how `git filter-repo` works, we'll show you how to remove your file with sensitive data from the history of your repository and add it to `.gitignore` to ensure that it is not accidentally re-committed. +Para ilustrar cómo funciona `git filter-repo`, te mostraremos cómo eliminar tu archivo con datos confidenciales del historial de tu repositorio y agregarlo a `.gitignore` para asegurar que no se reconfirmó de manera accidental. -1. Install the latest release of the [git filter-repo](https://github.com/newren/git-filter-repo) tool. You can install `git-filter-repo` manually or by using a package manager. For example, to install the tool with HomeBrew, use the `brew install` command. +1. Instala el último lanzamiento de la herramienta [git filter-repo](https://github.com/newren/git-filter-repo). Puedes instalar `git-filter-repo` manualmente o utilizando un administrador de paquete. Por ejemplo, para instalar la herramienta con HomeBrew, utiliza el comando `brew install`. ``` brew install git-filter-repo ``` - For more information, see [*INSTALL.md*](https://github.com/newren/git-filter-repo/blob/main/INSTALL.md) in the `newren/git-filter-repo` repository. + Para obtener más información, consulta el archivo [*INSTALL.md*](https://github.com/newren/git-filter-repo/blob/main/INSTALL.md) en el repositorio `newren/git-filter-repo`. 2. Si aún no tienes una copia local de tu repositorio con datos confidenciales en el historial, [clona el repositorio](/articles/cloning-a-repository/) en tu computadora local. ```shell @@ -91,7 +91,7 @@ To illustrate how `git filter-repo` works, we'll show you how to remove your fil 4. Ejecuta el siguiente comando, reemplazando `PATH-TO-YOUR-FILE-WITH-SENSITIVE-DATA` por la **ruta al archivo que quieres eliminar, no solo con su nombre de archivo**. Estos argumentos harán lo siguiente: - Forzar a Git a que procese, pero no revise, todo el historial de cada rama y etiqueta - Eliminar el archivo especificado y cualquier confirmación vacía generada como resultado - - Remove some configurations, such as the remote URL, stored in the *.git/config* file. You may want to back up this file in advance for restoration later. + - Elimina algunas configuraciones, tales como la URL remota almacenada en el archivo *.git/config*. Podrías necesitar respaldar este archivo con anticipación para restaurarlo posteriormente. - **Sobrescribir tus etiquetas existentes** ```shell $ git filter-repo --invert-paths --path PATH-TO-YOUR-FILE-WITH-SENSITIVE-DATA @@ -147,15 +147,15 @@ To illustrate how `git filter-repo` works, we'll show you how to remove your fil > + 48dc599...051452f main -> main (forced update) ``` -## Fully removing the data from {% data variables.product.prodname_dotcom %} +## Eliminar los datos de {% data variables.product.prodname_dotcom %} por completo -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 %}. +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 %}. Please provide the name of the repository and/or a link to the commit you need removed. +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. 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. -3. After some time has passed and you're confident that the BFG tool / `git filter-repo` had no unintended side effects, you can force all objects in your local repository to be dereferenced and garbage collected with the following commands (using Git 1.8.5 or newer): +3. Después de que haya transcurrido un tiempo y estés seguro de que la herramienta BFG / `git filter-repo` no tuvo efectos secundarios inesperados, puedes forzar a todos los objetos de tu repositorio local a desreferenciarse y recolectar la basura con los siguientes comandos (usando Git 1.8.5 o posterior): ```shell $ git for-each-ref --format="delete %(refname)" refs/original | git update-ref --stdin $ git reflog expire --expire=now --all @@ -183,6 +183,6 @@ Existen algunos trucos sencillos para evitar confirmar cosas que no quieres conf ## Leer más -- [`git filter-repo` man page](https://htmlpreview.github.io/?https://github.com/newren/git-filter-repo/blob/docs/html/git-filter-repo.html) -- [Pro Git: Git Tools - Rewriting History](https://git-scm.com/book/en/Git-Tools-Rewriting-History){% ifversion fpt or ghae or ghes > 2.22 %} -- "[About Secret scanning](/code-security/secret-security/about-secret-scanning)"{% endif %} +- [página man de `git filter-repo`](https://htmlpreview.github.io/?https://github.com/newren/git-filter-repo/blob/docs/html/git-filter-repo.html) +- [Pro Git: Herramientas de Git - Reescribiendo la historia](https://git-scm.com/book/en/Git-Tools-Rewriting-History){% ifversion fpt or ghae or ghes > 2.22 %} +- "[Acerca del escaneo de secretos](/code-security/secret-security/about-secret-scanning)"{% endif %} diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations.md index 9b4e30f0a6..e490535427 100644 --- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations.md +++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations.md @@ -15,19 +15,19 @@ topics: shortTitle: Integraciones autorizadas --- -## Reviewing your authorized {% data variables.product.prodname_oauth_apps %} +## Revisar tus {% data variables.product.prodname_oauth_apps %} autorizadas {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.access_applications %} {% data reusables.user_settings.access_authorized_oauth_apps %} {% data reusables.user_settings.review-oauth-apps %} -## Reviewing your authorized {% data variables.product.prodname_github_apps %} +## Revisar tus {% data variables.product.prodname_github_apps %} autorizadas {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.access_applications %} -3. Click the **Authorized {% data variables.product.prodname_github_apps %}** tab. ![Authorized {% data variables.product.prodname_github_apps %} tab](/assets/images/help/settings/settings-authorized-github-apps-tab.png) -3. Review the {% data variables.product.prodname_github_apps %} that have access to your account. Para las que no reconozcas o las que estén desactualizadas, haz clic en **Revoke** (Revocar). To revoke all {% data variables.product.prodname_github_apps %}, click **Revoke all**. ![Lista de {% data variables.product.prodname_github_app %} autorizadas](/assets/images/help/settings/revoke-github-app.png) +3. Haz clic en la pestaña de **{% data variables.product.prodname_github_apps %} autorizadas**. ![Pestaña de {% data variables.product.prodname_github_apps %} autorizadas](/assets/images/help/settings/settings-authorized-github-apps-tab.png) +3. Revisa las {% data variables.product.prodname_github_apps %}s que tienen acceso a tu cuenta. Para las que no reconozcas o las que estén desactualizadas, haz clic en **Revoke** (Revocar). Para revocar todas las {% data variables.product.prodname_github_apps %}s, haz clic en **Revocar todo**. ![Lista de {% data variables.product.prodname_github_app %} autorizadas](/assets/images/help/settings/revoke-github-app.png) ## Leer más {% ifversion fpt %} 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 126d8ab2bf..6f1e25b904 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 @@ -48,7 +48,7 @@ Tus acciones activan los eventos que se listan en tu bitácora de seguridad. Las | [`codespaces`](#codespaces-category-actions) | Contiene todas las actividades relacionadas con los {% data variables.product.prodname_codespaces %}. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces)". | | [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | Contiene todas las actividades relacionadas con la firma del Acuerdo del programador de {% data variables.product.prodname_marketplace %}. | | [`marketplace_listing`](#marketplace_listing-category-actions) | Contiene todas las actividades relacionadas con el listado de aplicaciones en {% data variables.product.prodname_marketplace %}.{% endif %} -| [`oauth_access`](#oauth_access-category-actions) | Contains all activities related to [{% data variables.product.prodname_oauth_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps) you've connected with.{% ifversion fpt %} +| [`oauth_access`](#oauth_access-category-actions) | Contiene todas las actividades relacionadas con las [{% data variables.product.prodname_oauth_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps) con las que te hayas conectado.{% ifversion fpt %} | [`payment_method`](#payment_method-category-actions) | Contiene todas las actividades relacionadas con el pago de tu suscripción de {% data variables.product.prodname_dotcom %}.{% endif %} | [`profile_picture`](#profile_picture-category-actions) | Contiene todas las actividades relacionadas con tu foto de perfil. | | [`project`](#project-category-actions) | Contiene todas las actividades relacionadas con los tableros de proyecto. | @@ -117,12 +117,12 @@ Un resumen de algunas de las acciones más frecuentes que se registran como even {% endif %} -### `oauth_authorization` category actions +### Acciones de la categoría `oauth_authorization` -| Acción | Descripción | -| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `create (crear)` | 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 (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-issue-4374 or ghes > 3.2 %} and when [authorizations are revoked or expire](/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)` | Se activa cuando [retiras 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 %} y cuando[las autorizaciones se retiran o vencen](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation).{% else %}.{% endif %} {% ifversion fpt %} 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 860db7c773..61f341247d 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 @@ -1,6 +1,6 @@ --- -title: Token expiration and revocation -intro: 'Your tokens can expire and can also be revoked by you, applications you have authorized, and {% data variables.product.product_name %} itself.' +title: Vencimiento y revocación de token +intro: 'Tus tokens pueden vencer y también los puedes revocar tú, las aplicaciones que hayas autorizado y el mismo {% data variables.product.product_name %}.' versions: fpt: '*' ghes: '*' @@ -8,55 +8,55 @@ versions: topics: - Identity - Access management -shortTitle: Token expiration +shortTitle: Vencimiento de token 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 %}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. +Cuando un token {% ifversion fpt or ghae-issue-4374 or ghes > 3.2 %}venció o {% endif %}se revocó, este ya no se puede utilizar para autenticar las solicitudes de la API y de Git. No es posible restablecer un token revocado o vencido, ya seas tú o la aplicación necesitarán crear un token nuevo. -This article explains the possible reasons your {% data variables.product.product_name %} token might be revoked or expire. +Este artículo te explica las posibles razones por las cuales tu token de {% data variables.product.product_name %} podría revocarse o vencer. {% note %} -**Note:** When a personal access token or OAuth token expires or is revoked, you may see an `oauth_authorization.destroy` action in your security log. Para obtener más información, consulta "[Revisar tu registro de seguridad](/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-security-log)". +**Nota:** Cuando un token de acceso personal o token de OAuth vence o se revoca, podrías ver una acción de `oauth_authorization.destroy` en tu bitácora de seguridad. Para obtener más información, consulta "[Revisar tu registro de seguridad](/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-security-log)". {% endnote %} {% ifversion fpt or ghae-issue-4374 or ghes > 3.2 %} -## Token revoked after reaching its expiration date +## El token se revocó después de llegar a su fecha de vencimiento -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. 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)". +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)". {% endif %} {% ifversion fpt %} -## Token revoked when pushed to a public repository or public gist +## El token se revocó cuando se subió a un repositorio o gist público -If a valid OAuth token, {% data variables.product.prodname_github_app %} token, or personal access token is pushed to a public repository or public gist, the token will be automatically revoked. +Si un token OAuth válido, token de {% data variables.product.prodname_github_app %} o de acceso personal se sube a un repositorio o gist público, este se revocará automáticamente. -OAuth tokens and personal access tokens pushed to public repositories and public gists will only be revoked if the token has scopes. +Los tokens de OAuth y los de acceso personal que se suben a los repositorios y gists públicos solo se revocarán si el token tiene alcances. {% endif %} {% ifversion fpt %} -## Token expired due to lack of use +## El token venció debido a la falta de uso -{% data variables.product.product_name %} will automatically revoke an OAuth token or personal access token when the token hasn't been used in one year. +{% data variables.product.product_name %} revocará el token de OAuth o de acceso personal automáticamente cuando no se haya utilizado en un año. {% endif %} -## Token revoked by the user +## El usuario revocó el token -You can revoke your authorization of a {% data variables.product.prodname_github_app %} or {% data variables.product.prodname_oauth_app %} from your account settings which will revoke any tokens associated with the app. For more information, see "[Reviewing your authorized integrations](/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations)" and "[Reviewing your authorized applications (OAuth)](/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-authorized-applications-oauth)." +Puedes revocar tu autorización de una {% data variables.product.prodname_github_app %} o {% data variables.product.prodname_oauth_app %} desde tus ajustes de cuenta, lo cual revocará cualquier token asociado con la app. Para obtener más información, consulta las secciones "[Revisar tus integraciones autorizadas](/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations)" y "[Revisar tus aplicaciones autorizadas (OAuth)](/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-authorized-applications-oauth)". -Once an authorization is revoked, any tokens associated with the authorization will be revoked as well. To re-authorize an application, follow the instructions from the third-party application or website to connect your {% data variables.product.product_name %} account again. +Una vez que se revoca una autorización, cualquier token asociado con la autorización también se revocará. Para volver a autorizar una aplicación, sigue las instrucciones de la aplicación o sitio web tercero para conectarte con tu cuenta de {% data variables.product.product_name %} nuevamente. -## Token revoked by the {% data variables.product.prodname_oauth_app %} +## La {% data variables.product.prodname_oauth_app %} revocó el token -The owner of an {% data variables.product.prodname_oauth_app %} can revoke an account's authorization of their app, this will also revoke any tokens associated with the authorization. For more information about revoking authorizations of your OAuth app, see "[Delete an app authorization](/rest/reference/apps#delete-an-app-authorization)." +El propietario de una {% data variables.product.prodname_oauth_app %} puede revocar una autorización de su app en una cuenta, esto también revocará cualquier token asociado con esa autorización. Para obtener más información sobre cómo revocar las autorizaciones de tu app de OAuth, consulta la sección "[Borrar una autorización de una app](/rest/reference/apps#delete-an-app-authorization)". -## Token revoked due to excess of tokens for an {% data variables.product.prodname_oauth_app %} with the same scope +## El token se revocó debido a un exceso de tokens para una {% data variables.product.prodname_oauth_app %} con el mismo alcance {% data reusables.apps.oauth-token-limit %} -## User token revoked due to {% data variables.product.prodname_github_app %} configuration +## El token de usuario se revocó debido a la configuración de la {% data variables.product.prodname_github_app %} -User-to-server tokens created by a {% data variables.product.prodname_github_app %} will expire after eight hours by default. Owners of {% data variables.product.prodname_github_apps %} can configure their apps so that user-to-server tokens do not expire. For more information about changing how your {% data variables.product.prodname_dotcom %} App's user-to-server tokens behave, see "[Activating optional features for apps](/developers/apps/getting-started-with-apps/activating-optional-features-for-apps)." +Los tokens de usuario a servidor que creó una {% data variables.product.prodname_github_app %} vencerán después de ocho horas, predeterminadamente. Los propietarios de las {% data variables.product.prodname_github_apps %} pueden configurar sus apps para que los tokens de usuario a servidor no venzan. Para obtener más información sobre cómo cambiar la forma en que se compartan los tokens de usuario a servidor de tus Apps de {% data variables.product.prodname_dotcom %}, consulta la sección "[Activar las características opcionales para las apps](/developers/apps/getting-started-with-apps/activating-optional-features-for-apps)". 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 bfb7e7911d..07d1b7ba56 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 @@ -30,7 +30,7 @@ shortTitle: Actualizar las credenciales de acceso {% tip %} -To avoid losing your password in the future, we suggest using a secure password manager, like [LastPass](https://lastpass.com/) or [1Password](https://1password.com/). +Para evitar perder tu contraseña en el futuro, te sugerimos utilizar un administrador de contraseñas seguro, tal como [LastPass](https://lastpass.com/) o [1Password](https://1password.com/). {% endtip %} diff --git a/translations/es-ES/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md b/translations/es-ES/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md index 345cea8af8..a1c27e2a05 100644 --- a/translations/es-ES/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md +++ b/translations/es-ES/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md @@ -86,7 +86,7 @@ No es necesario cargar tu clave pública a {% data variables.product.product_nam {% ifversion fpt %} ## Verificación de firma para bots -Organizations and {% data variables.product.prodname_github_apps %} that require commit signing can use bots to sign commits. Si una confirmación o etiqueta tienen una firma de bot que es criptográficamente comprobable, {% data variables.product.product_name %} marca la confirmación o etiqueta como verificada. +Las organizaciones y {% data variables.product.prodname_github_apps %} que requieren de la firma de confirmación pueden usar bots para firmar las confirmaciones. Si una confirmación o etiqueta tienen una firma de bot que es criptográficamente comprobable, {% data variables.product.product_name %} marca la confirmación o etiqueta como verificada. La verificación de firma para bots solo funcionará si la solicitud se verifica y se autentica como la {% data variables.product.prodname_github_app %} o el bot y no contiene información de autor personalizada, información de persona que confirma el cambio personalizada ni información de firma personalizada, como API de confirmaciones. {% endif %} diff --git a/translations/es-ES/content/authentication/managing-commit-signature-verification/displaying-verification-statuses-for-all-of-your-commits.md b/translations/es-ES/content/authentication/managing-commit-signature-verification/displaying-verification-statuses-for-all-of-your-commits.md index 92e7beaef2..d3a1723abf 100644 --- a/translations/es-ES/content/authentication/managing-commit-signature-verification/displaying-verification-statuses-for-all-of-your-commits.md +++ b/translations/es-ES/content/authentication/managing-commit-signature-verification/displaying-verification-statuses-for-all-of-your-commits.md @@ -18,7 +18,7 @@ redirect_from: Cuando trabajas localmente en tu computadora, Git te permite configurar el autor de tus cambios y la identidad del confirmante. Esto, potencialmente, dificulta que otras personas tengan la confimansa de que realmente hayas creado tus etiquetas y confirmaciones. Para ayudarte a resolver este problema, puedes firmar tus confirmaciones y etiquetas. Para obtener más información, consulta la sección "[Firmar confirmaciones](/github/authenticating-to-github/signing-commits)" y "[Firmar etiquetas](/github/authenticating-to-github/signing-tags)". {% data variables.product.prodname_dotcom %} marca las etiquetas y confirmaciones firmadas con un estado de verificación. -Predeterminadamente, las confirmaciones y etiquetas se marcan como "Verificadas" si se firman con una llave GPG o S/MIME que se verificó con éxito. If a commit or tag has a signature that can't be verified by {% data variables.product.prodname_dotcom %}, we mark the commit or tag "Unverified." En el resto de los casos, no se muestra un estado de verificación. +Predeterminadamente, las confirmaciones y etiquetas se marcan como "Verificadas" si se firman con una llave GPG o S/MIME que se verificó con éxito. Si una confirmación o etiqueta tiene una firma que no puede verificar {% data variables.product.prodname_dotcom %}, la marcaremos como "No verificada". En el resto de los casos, no se muestra un estado de verificación. Sin embargo, puedes proporcionar aún más confianza a otros usuarios sobre la identidad que se atribuye a tus confirmaciones y etiquetas si habilitas el modo vigilanten en tu configuración de {% data variables.product.prodname_dotcom %}. Cuando tienes habilitado el modo vigilante, todas tus confirmaciones y etiquetas se marcan con uno de tres estados de verificación. @@ -26,7 +26,7 @@ Sin embargo, puedes proporcionar aún más confianza a otros usuarios sobre la i {% data reusables.identity-and-permissions.vigilant-mode-verification-statuses %} -You should only enable vigilant mode if you sign all of your commits and tags and use an email address that is verified for your account on {% data variables.product.product_name %} as your committer email address. Después de habilitar este modo, cualquier confirmación o etiqueta sin firmar que generes localmente y subas a {% data variables.product.prodname_dotcom %} se marcará como "Sin verificar". +Deberías habilitar el modo vigilante únicamente si firmas todas tus confirmaciones y etiqueta y utilizas una dirección de correo electrónico que esté verificada para tu cuenta en {% data variables.product.product_name %} como tu dirección de correo electrónico de confirmante. Después de habilitar este modo, cualquier confirmación o etiqueta sin firmar que generes localmente y subas a {% data variables.product.prodname_dotcom %} se marcará como "Sin verificar". {% data reusables.identity-and-permissions.verification-status-check %} diff --git a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md index 63bd273d77..358bf6860f 100644 --- a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md +++ b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md @@ -76,33 +76,6 @@ Selecciona tu código de país y escribe el número de teléfono móvil, incluid Después de la configuración, el dispositivo de copia de seguridad recibirá un SMS de confirmación. -## Agregar un método de autenticación de reserva con Recuperar cuentas en otro lugar - -Puedes generar una credencial de autenticación adicional para tu cuenta y almacenarla con un proveedor de recuperación asociado. - -### Acerca de Recuperar cuentas en otro lugar - -Con Recuperar cuentas en otro lugar, puedes agregar un factor de seguridad adicional a tu cuenta {% data variables.product.product_name %} en caso de que pierdas acceso al método de autenticación de dos factores o los códigos de recuperación. - -Recuperar cuentas en otro lugar te permite asociar tu cuenta {% data variables.product.product_name %} con tu cuenta de Facebook. Puedes almacenar una credencial de autenticación en la forma de un _token de recuperación de cuenta_ para tu cuenta {% data variables.product.product_name %} con Facebook. - -Si pierdes acceso a tu cuenta {% data variables.product.product_name %} porque ya no tienes acceso a tu método de autenticación de dos factores o códigos de recuperación, puedes recuperar tu token de recuperación de cuenta del proveedor de recuperación para demostrar que eres el propietario de tu cuenta {% data variables.product.product_name %}. - -Después de que recuperes tu token, {% data variables.contact.contact_support %} puede inhabilitar la autenticación de dos factores para tu cuenta. Luego, puedes proporcionar o restablecer tu contraseña para recuperar el acceso a tu cuenta. - -Cuando generas o recuperas un token de recuperación de cuenta, se agrega un evento a tu registro de auditoría de la cuenta. Para obtener más información, consulta "[Revisar tu registro de seguridad](/articles/reviewing-your-security-log)". - -### Generar y almacenar un token de recuperación de cuenta - -Puedes generar un token de recuperación de cuenta y almacenarlo con un proveedor de recuperación asociado. - -1. Inicia sesión con tu cuenta de Facebook, luego regresa a tu {% data variables.product.product_name %}. -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.security %} -4. Para generar un token nuevo, en "Recovery tokens" (Tokens de recuperación), haz clic en **Store new token** (Almacenar token nuevo). ![Botón para almacenar un nuevo token de recuperación](/assets/images/help/settings/store-new-recovery-token.png) -5. Obtén más información sobre tokens de recuperación de cuenta, luego haz clic en **Connect with https://www.facebook.com** (Conectar con https://www.facebook.com). ![Botón para conectar un token de recuperación con Facebook](/assets/images/help/settings/connect-recovery-token-with-facebook.png) -6. Una vez que eres redirigido a Facebook, lee la información sobre cómo activar la recuperación de cuenta con Facebook antes de hacer clic en **Save as [_YOUR NAME_]** (Guardar como [_TU NOMBRE_]. (Si guardas múltiples tokens dentro de un período breve, Facebook puede omitir este paso de confirmación después de que guardes tu primer token). ![Página de Facebook con botón para activar la recuperación de la cuenta](/assets/images/help/settings/security-turn-on-rae-facebook.png) - {% endif %} ## Leer más diff --git a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md index 854adb1896..e419786950 100644 --- a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md +++ b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md @@ -28,6 +28,12 @@ Recomendamos encarecidamente el uso de una contraseña única basada en el tiemp {% endwarning %} +{% ifversion fpt %} + +Si eres miembro de una {% data variables.product.prodname_emu_enterprise %}, no podrás configurar la 2FA para tu cuenta de {% data variables.product.prodname_managed_user %}. La 2FA debe configurarse mediante tu proveedor de identidad. + +{% endif %} + ## Configurar la autenticación de dos factores mediante una app móvil TOTP Una aplicación de contraseña única basada en el tiempo (TOTP) genera automáticamente un código de autenticación que cambia después de un cierto período de tiempo. Recomendamos usar apps TOTP basadas en la nube como: diff --git a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/countries-where-sms-authentication-is-supported.md b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/countries-where-sms-authentication-is-supported.md index 1de0811e66..3e5dc35cd0 100644 --- a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/countries-where-sms-authentication-is-supported.md +++ b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/countries-where-sms-authentication-is-supported.md @@ -124,7 +124,7 @@ Si tu país no está en la lista, significa que actualmente no podemos entregar
  • Tanzania
  • Togo
  • Trinidad y Tobago
    • -
  • Turkey
    • +
  • Turquía
  • Turcas y Caicos
  • Uganda
  • Ucrania
    • diff --git a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md index 5b6e933783..6b2837e366 100644 --- a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md +++ b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md @@ -71,6 +71,12 @@ Puedes utilizar tus credenciales de autenticación de dos factores para recobrar ## Autenticar con un token de recuperación de cuenta +{% warning %} + +**Advertencia:** Los tokens de recuperación de cuenta se obsoletizaron y se inhabilitarán el **1 de diciembre de 2021**. Por favor, asegúrate de haber configurado otros métodos de recuperación bifactoriales. Para obtener más información, consulta la sección "[Configurar los métodos de autenticación bifactoriales](/articles/configuring-two-factor-authentication-recovery-methods)". + +{% endwarning %} + Si pierdes el acceso a tus métodos de autenticación de dos factores para tu cuenta {% data variables.product.product_name %}, puedes recuperar tu token de recuperación de cuenta desde un proveedor socio de recuperación y solicitarle a Soporte de {% data variables.product.prodname_dotcom %} que lo revise. Si no tienes acceso a tus métodos de autenticación de dos factores o a tus códigos de recuperación y has almacenado un token de recuperación de cuenta con Facebook utilizando Recuperar cuentas en otro lugar, puedes utilizar tu token para recuperar el acceso a tu cuenta. diff --git a/translations/es-ES/content/authentication/troubleshooting-ssh/error-key-already-in-use.md b/translations/es-ES/content/authentication/troubleshooting-ssh/error-key-already-in-use.md index 9e37f5e2d8..bc482e840b 100644 --- a/translations/es-ES/content/authentication/troubleshooting-ssh/error-key-already-in-use.md +++ b/translations/es-ES/content/authentication/troubleshooting-ssh/error-key-already-in-use.md @@ -27,7 +27,7 @@ $ ssh -T -ai ~/.ssh/id_rsa git@{% data variables.command_line.codeblock El *nombre de usuario* que aparece en la respuesta es la cuenta de {% data variables.product.product_name %} a la que la clave se encuentra actualmente vinculada. Si la respuesta se parece a "username/repo", la llave se ha vinculado a un repositorio como [*llave de implementación*](/guides/managing-deploy-keys#deploy-keys). -To force SSH to use only the key provided on the command line, use `-o` to add the `IdentitiesOnly=yes` option: +Para forzar a SSH a que utilice solo la clave que se proporcionó en la línea de comandos, utiliza `-o` para agregar la opción `IdentitiesOnly=yes`: ```shell $ ssh -v -o "IdentitiesOnly=yes" -i ~/.ssh/id_rsa git@{% data variables.command_line.codeblock %} diff --git a/translations/es-ES/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md b/translations/es-ES/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md index 67f724e682..1c75223540 100644 --- a/translations/es-ES/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md +++ b/translations/es-ES/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md @@ -30,7 +30,7 @@ Si eso funcionó, ¡fantástico! De lo contrario, puede que debas [seguir nuestr ## Habilitar conexiones SSH a través de HTTPS -If you are able to SSH into `git@ssh.{% data variables.command_line.backticks %}` over port 443, you can override your SSH settings to force any connection to {% data variables.product.product_location %} to run through that server and port. +Si puedes ingresar a `git@ssh.{% data variables.command_line.backticks %}` por SSH a través del puerto 443, podrás reemplazar los parámetros SSH para forzar que cualquier conexión a {% data variables.product.product_location %} se ejecute a través de ese servidor y puerto. Para establecer esto en tus parámetros ssh, edita el archivo en `~/.ssh/config` y agrega esta sección: diff --git a/translations/es-ES/content/billing/index.md b/translations/es-ES/content/billing/index.md index fa5a141add..d03d1fec89 100644 --- a/translations/es-ES/content/billing/index.md +++ b/translations/es-ES/content/billing/index.md @@ -1,7 +1,7 @@ --- -title: Billing and payments for GitHub +title: Facturación y pagos para GitHub shortTitle: Facturación y pagos -intro: '{% ifversion fpt %}{% data variables.product.product_name %} offers free and paid products for every account. You can upgrade, downgrade, and view pending changes to your account''s subscription at any time.{% elsif ghes or ghae %}{% data variables.product.company_short %} bills for your enterprise members'' {% ifversion ghae %}usage of {% data variables.product.product_name %}{% elsif ghes %} licence seats for {% data variables.product.product_name %}{% ifversion ghes > 3.0 %} and any additional services that you purchase{% endif %}{% endif %}.{% endif %}' +intro: '{% ifversion fpt %}{% data variables.product.product_name %} ofrece productos gratuitos y de pago para todas las cuentas. Puedes mejorar, bajar de nivel y ver los cambios pendientes de la suscripción de tu cuenta en cualquier momento.{% elsif ghes or ghae %}{% data variables.product.company_short %} cobra por el uso {% ifversion ghae %} de {% data variables.product.product_name %} para los miembros de tu empresa{% elsif ghes %} plazas de licencia de {% data variables.product.product_name %}{% ifversion ghes > 3.0 %} y cualquier servicio adicional que compres{% endif %}{% endif %}.{% endif %}' redirect_from: - /github/setting-up-and-managing-billing-and-payments-on-github - /categories/setting-up-and-managing-billing-and-payments-on-github 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 05f5c19e16..297b644b09 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 @@ -24,7 +24,7 @@ Si compraste {% data variables.product.prodname_enterprise %} mediante un Acuerd Los minutos se restablecen cada mes, pero no es el caso para el uso de almacenamiento. -### Included storage and minutes +### Minutos y almacenamiento incluídos | Producto | Almacenamiento | Minutos (por mes) | | --------------------------------------------------------------------- | -------------- | ----------------- | @@ -36,7 +36,7 @@ Los minutos se restablecen cada mes, pero no es el caso para el uso de almacenam Los jobs que se ejecutan en Windows y macOS y que se hospedan en {% data variables.product.prodname_dotcom %} consumen minutos en una proporción de 2 a 10 veces mayor que aquellos que se ejecutan en Linux. Por ejemplo, utilizar 1,000 minutos en Windows consumirá 2,000 de los minutos incluidos en tu cuenta. Utilizar 1,000 minutos en macOS consumiría 10,000 de los minutos incluidos en tu cuenta. -### Minute multipliers +### Multiplicadores de minutos | Sistema operativo | Multiplicador de minutos | | ----------------- | ------------------------ | @@ -46,7 +46,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)". - 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 %} redondea hacia arriba los minutos que utiliza cada job. + 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. {% note %} @@ -54,9 +54,9 @@ El almacenamiento que utilza un repositorio es el total del almacenamiento utili {% endnote %} -### Per-minute rates +### Tasas por minuto -| Sistema operativo | Per-minute rate (USD) | +| Sistema operativo | Tasa por minuto (USD) | | ----------------- | --------------------- | | Linux | $0.008 | | macOS | $0.08 | @@ -68,19 +68,21 @@ La cantidad de jobs que puedes ejecutar simultáneamente a través de todos los ## Calcular los gastos por minuto y por almacenamiento +{% data reusables.dotcom_billing.pricing_cal %} + Al final de cada mes, {% data variables.product.prodname_dotcom %} calcula el costo de los minutos y almacenamiento utilizados en comparación con lo que se incluye en tu cuenta. -### Sample minutes cost calculation +### Ejemplo de cálculos de costo por minuto -For example, if your organization uses {% data variables.product.prodname_team %} and allows unlimited spending, using 15,000 minutes could have a total storage and minute overage cost of $56 USD, depending on the operating systems used to run jobs. +Por ejemplo, si tu organización utiliza {% data variables.product.prodname_team %} y permite gastos ilimitados, utilizar 15,000 minutos podría tener un costo extra de almacenamiento y minutos de $56 USD dependiendo de los sistemas operativos que se utilizan para ejecutar jobs. -- 5,000 (3,000 Linux and 2,000 Windows) minutes = $56 USD ($24 USD + $32 USD). - - 3,000 Linux minutes at $0.008 USD per minute = $24 USD. - - 2,000 Windows minutes at $0.016 USD per minute = $32 USD. +- 5,000 minutos (3,000 de Linux y 2,000 de Windows) = $56 USD ($24 USD + $32 USD). + - 3,000 minutos de Linux a $0.008 USD por minuto = $24 USD. + - 2,000 minutos de Windows a $0.016 USD por minuto = $32 USD. {% data variables.product.prodname_dotcom %} calcula tu uso de almacenamiento para cada mes basándose en el uso por hora durante el mismo mes. -### Sample storage cost calculation +### Muestra de cálculo de costos de almacenamiento Por ejemplo, si utilizas 3 GB de almacenamiento durante 10 días de Marzo y 12 GB durante 21 días de Marzo, tu uso de almacenamiento sería: diff --git a/translations/es-ES/content/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md b/translations/es-ES/content/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md index 7eea2de9e7..1af696f62b 100644 --- a/translations/es-ES/content/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md +++ b/translations/es-ES/content/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md @@ -62,5 +62,5 @@ Los propietarios de la empresa y gerentes de facturación pueden administrar el {% data reusables.dotcom_billing.update-spending-limit %} -## Managing usage and spending limit email notifications +## Administrar las notificaciones de uso y límite de gastos {% data reusables.billing.email-notifications %} diff --git a/translations/es-ES/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md b/translations/es-ES/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md index d3913981c1..ec74987f3b 100644 --- a/translations/es-ES/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md +++ b/translations/es-ES/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md @@ -1,6 +1,6 @@ --- -title: About billing for GitHub Advanced Security -intro: 'If you want to use {% data variables.product.prodname_GH_advanced_security %} features{% ifversion fpt %} in a private or internal repository{% endif %}, you need a license.{% ifversion fpt %} These features are available free of charge for public repositories on {% data variables.product.prodname_dotcom_the_website %}.{% endif %}' +title: Acerca de la facturación para Github Advanced Security +intro: 'Si quieres utilizar las características de la {% data variables.product.prodname_GH_advanced_security %}{% ifversion fpt %} en un repositorio interno o privado{% endif %}, necesitas una licencia.{% ifversion fpt %} Estas características están disponibles gratuitamente para los repositorios públicos en {% data variables.product.prodname_dotcom_the_website %}.{% endif %}' product: '{% data reusables.gated-features.ghas %}' redirect_from: - /admin/advanced-security/about-licensing-for-github-advanced-security @@ -15,7 +15,7 @@ topics: - Advanced Security - Enterprise - Licensing -shortTitle: Advanced Security billing +shortTitle: Facturación de Advanced Security --- ## Acerca de la facturación para {% data variables.product.prodname_GH_advanced_security %} @@ -36,7 +36,7 @@ Puedes poner a disposición de los usuarios algunas características adicionales {% endif %} -To discuss licensing {% data variables.product.prodname_GH_advanced_security %} for your enterprise, contact {% data variables.contact.contact_enterprise_sales %}. +Para debatir sobre el licenciamiento de {% data variables.product.prodname_GH_advanced_security %} para tu empresa, contacta a {% data variables.contact.contact_enterprise_sales %}. ## Acerca de los números de confirmante para {% data variables.product.prodname_GH_advanced_security %} @@ -48,17 +48,17 @@ To discuss licensing {% data variables.product.prodname_GH_advanced_security %} {% endif %} -Puedes requerir políticas para permitir o dejar de permitir que las organizaciones que pertenecen a tu cuenta empresarial utilicen la {% data variables.product.prodname_advanced_security %}. For more information, see "{% ifversion ghes %}[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise){% elsif fpt or ghae %}[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise-account){% endif %}." +Puedes requerir políticas para permitir o dejar de permitir que las organizaciones que pertenecen a tu cuenta empresarial utilicen la {% data variables.product.prodname_advanced_security %}. Para obtener más información, consulta la sección "{% ifversion ghes %}[Requerir políticas para la {% data variables.product.prodname_advanced_security %} en tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise){% elsif fpt or ghae %}[Requerir políticas para la {% data variables.product.prodname_advanced_security %} en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise-account){% endif %}". {% ifversion fpt or ghes %} -For more information on viewing license usage, see "[Viewing your {% data variables.product.prodname_GH_advanced_security %} usage](/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage)." +Para obtener más información sobre cómo ver el uso de licencias, consulta la sección "[Ver tu uso de {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage)". {% endif %} -## Calculating committer spending +## Calcular los gastos de los confirmantes -The following example timeline demonstrates the events during a month that affect billing for {% data variables.product.prodname_GH_advanced_security %} in an enterprise. For each month, you will find events, the total committer count, and the total number of committers that {% data variables.product.company_short %} would bill for. +La siguiente línea de tiempo de ejemplo demuestra los eventos mensuales que afectan la facturación de {% data variables.product.prodname_GH_advanced_security %} en una empresa. Para cada mes, encontrarás eventos, la cuenta total de confirmantes y la cantidad total de confirmantes por la que cobrará {% data variables.product.company_short %}. @@ -67,25 +67,25 @@ The following example timeline demonstrates the events during a month that affec
    - Events during the month + Eventos del mes - Total committer count + Cuenta total de confirmantes - Committers billed for the month + Confirmantes por los que se cobrará en el mes
    - August 1 + 1 de agosto - A member of your enterprise enables {% data variables.product.prodname_GH_advanced_security %} for repository X. Repository X has 50 committers over the past 90 days. + Un miembro de tu empresa habilita {% data variables.product.prodname_GH_advanced_security %} para el repositorio X. El repositorio X tiene 50 confirmantes en los últimos 90 días. @@ -99,11 +99,11 @@ The following example timeline demonstrates the events during a month that affec
    - September 5 + 5 de septiembre - Developer A leaves the team working on repository X. Developer A's contributions continue to count for 90 days. + El desarrollador A sale del equipo que está trabajando en el repositorio X. Las contribuciones del desarrollador A siguen contando durante 90 días. @@ -117,11 +117,11 @@ The following example timeline demonstrates the events during a month that affec
    - September 8 + 8 de septiembre - Developer B pushes a commit to repository X for the first time. Developer B's usage is pro-rated, because the developer began contributing to repository X partway through the month. + El desarrolador B sube una confirmación al repositorio X por primera vez. El uso del desarrollador B se prorratea, ya que el desarrollador comenzó a contribuir al repositorio X ya empezado el mes. @@ -135,11 +135,11 @@ The following example timeline demonstrates the events during a month that affec
    - October and November + Octubre y noviembre - Developer A's contributions to repository X continue to count because the contributions were within the past 90 days. {% data variables.product.company_short %} now bills for developer B for the entire month because developer B now has contributions within the past 90 days. + Las contribuciones del desarrollador X al repositorio X siguen contando, ya que estas se hicieron dentro de los últimos 90 días. {% data variables.product.company_short %} ahora cobra por el mes completo del desarrollador B, ya que el desarrollador B ahora tiene contribuciones dentro de los 90 días pasados. @@ -153,11 +153,11 @@ The following example timeline demonstrates the events during a month that affec
    - December 4 + 4 de diciembre - 90 days have passed since developer A's last contribution to repository _X. The 90 days lapsed after December started, so {% data variables.product.company_short %} bills for developer A for the entire month. + Han pasado 90 días desde que el desarrollador A hizo su última contribución al repositorio _X. Pasaron 90 días después de que comenzó diciembre, así que {% data variables.product.company_short %} cobra por todo el mes del desarrollador A. @@ -171,11 +171,11 @@ The following example timeline demonstrates the events during a month that affec
    - December 11 + 11 de diciembre - Developer C joins the company and pushes a commit to repository X for the first time. Developer C's usage is pro-rated at 70% for 21 out of 30 days. + El desarrollador C se une a la compañía y sube una confirmación al repositorio X por primera vez. El uso del desarrollador C se prorratea en 70% durante 21 de los 30 días. @@ -189,11 +189,11 @@ The following example timeline demonstrates the events during a month that affec
    - January + Enero - {% data variables.product.company_short %} no longer bills for developer A. {% data variables.product.company_short %} bills for developer C for the entire month. + {% data variables.product.company_short %} ya no cobra por el desarrollador A. {% data variables.product.company_short %} cobra por todo el mes del desarrollador C. @@ -207,11 +207,11 @@ The following example timeline demonstrates the events during a month that affec
    - February 15 + 15 de febrero - A member of your enterprise disables {% data variables.product.prodname_GH_advanced_security %} for repository X. The 51 contributors to repository X do not work in any other repositories with {% data variables.product.prodname_GH_advanced_security %}. {% data variables.product.company_short %} bills for the developers' usage in repository X for February. + Un miembro de tu empresa inhabilita la {% data variables.product.prodname_GH_advanced_security %} para el repositorio X. Los 51 contribuyentes del repositorio X no trabajan en ningún otro repositorio que cuente con la {% data variables.product.prodname_GH_advanced_security %}. {% data variables.product.company_short %} cobra por el uso de los desarrolladores en el repositorio X en febrero. @@ -225,11 +225,11 @@ The following example timeline demonstrates the events during a month that affec
    - March + Marzo - No repository owned by your enterprise has {% data variables.product.prodname_GH_advanced_security %} enabled. + Ningún repositorio que pertenezca a tu empresa tiene habilitada la {% data variables.product.prodname_GH_advanced_security %}. @@ -242,6 +242,6 @@ The following example timeline demonstrates the events during a month that affec
    -## Getting the most out of {% data variables.product.prodname_GH_advanced_security %} +## Sacar el mayor provecho de la {% data variables.product.prodname_GH_advanced_security %} {% data reusables.advanced-security.getting-the-most-from-your-license %} diff --git a/translations/es-ES/content/billing/managing-billing-for-github-advanced-security/index.md b/translations/es-ES/content/billing/managing-billing-for-github-advanced-security/index.md index a5b90f59cd..52722b52ce 100644 --- a/translations/es-ES/content/billing/managing-billing-for-github-advanced-security/index.md +++ b/translations/es-ES/content/billing/managing-billing-for-github-advanced-security/index.md @@ -1,5 +1,5 @@ --- -title: Managing billing for GitHub Advanced Security +title: Administrar la facturación de GitHub Advanced Security shortTitle: GitHub Advanced Security intro: 'Puedes ver y administrar tu uso de plazas en una licencia de {% data variables.product.prodname_advanced_security %}.' product: '{% data reusables.gated-features.ghas %}' diff --git a/translations/es-ES/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md b/translations/es-ES/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md index 93d16dd1a5..2ac03e2912 100644 --- a/translations/es-ES/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md +++ b/translations/es-ES/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md @@ -1,6 +1,6 @@ --- title: Visualizar tu uso de GitHub Advanced Security -intro: 'You can view usage of {% data variables.product.prodname_GH_advanced_security %} for your enterprise.' +intro: 'Puedes ver el uso de {% data variables.product.prodname_GH_advanced_security %} de tu empresa.' permissions: 'Enterprise owners can view usage for {% data variables.product.prodname_GH_advanced_security %}.' product: '{% data reusables.gated-features.ghas %}' redirect_from: @@ -19,7 +19,7 @@ topics: shortTitle: Visualizar el uso de la Seguridad Avanzada --- -## About licenses for {% data variables.product.prodname_GH_advanced_security %} +## Acerca de las licencias para {% data variables.product.prodname_GH_advanced_security %} {% data reusables.advanced-security.about-ghas-license-seats %} Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)". @@ -32,7 +32,7 @@ Puedes verificar cuántas plazas incluye tu licencia y cuántas de ellas se est {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.license-tab %} - La sección de "{% data variables.product.prodname_GH_advanced_security %}" muestra los detalles del uso actual. ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings](/assets/images/help/enterprises/enterprise-licensing-tab-ghas.png) If you run out of seats, the section will be red and show "Limit exceeded". Debes ya sea reducir tu uso de {% data variables.product.prodname_GH_advanced_security %} o comprar más plazas. Para obtener más información, consulta la sección "[Acerca de la facturación para el {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security#getting-the-most-out-of-github-advanced-security)". ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings showing "Limit exceeded"](/assets/images/help/enterprises/enterprise-licensing-tab-ghas-no-seats.png) + La sección de "{% data variables.product.prodname_GH_advanced_security %}" muestra los detalles del uso actual. ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings](/assets/images/help/enterprises/enterprise-licensing-tab-ghas.png) Si te quedas sin plazas, la sección estará en rojo y mostrará "Límite excedido". Debes ya sea reducir tu uso de {% data variables.product.prodname_GH_advanced_security %} o comprar más plazas. Para obtener más información, consulta la sección "[Acerca de la facturación para el {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security#getting-the-most-out-of-github-advanced-security)". ![{% data variables.product.prodname_GH_advanced_security %} en los ajustes de licenciamiento de empresa mostrando "Límite excedido"](/assets/images/help/enterprises/enterprise-licensing-tab-ghas-no-seats.png) 4. Opcionalmente, para ver un resumen detallado del uso por organización, en la barra lateral izquierda, haz clic en **Facturación**. ![Billing tab in the enterprise account settings sidebar](/assets/images/help/business-accounts/settings-billing-tab.png) En la sección de "{% data variables.product.prodname_GH_advanced_security %}" puedes ver la cantidad de confirmantes y confirmantes únicos de cada organización. ![{% data variables.product.prodname_GH_advanced_security %} en la configuración de facturación empresarial](/assets/images/help/billing/ghas-orgs-list-enterprise-dotcom.png) 5. Opcionalmente, haz clic en el nombre de una organización que te pertenezca para mostrar la configuración de seguridad y análisis para la organización. ![Organización que te pertenece en la sección de {% data variables.product.prodname_GH_advanced_security %} de la configuración de facturación empresarial](/assets/images/help/billing/ghas-orgs-list-enterprise-click-org.png) 6. En la página de configuración de "Seguridad & análisis", desplázate hacia la sección de "repositorios de {% data variables.product.prodname_GH_advanced_security %}" para ver un resumen detallado del uso de este repositorio en esta organización. ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/enterprises/settings-security-analysis-ghas-repos-list.png) Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis de tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". diff --git a/translations/es-ES/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md b/translations/es-ES/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md index 488176b67f..c9e218d678 100644 --- a/translations/es-ES/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md +++ b/translations/es-ES/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md @@ -1,7 +1,7 @@ --- title: Acerca de la facturación para Codespaces shortTitle: Acerca de la facturación -intro: 'View pricing and see how to manage {% data variables.product.prodname_codespaces %} billing for your organization.' +intro: 'Ver los precios y cómo administrar la facturación de {% data variables.product.prodname_codespaces %} para tu organización.' permissions: 'To manage billing for Codespaces for an organization, you must be an organization owner or a billing manager.' versions: fpt: '*' @@ -12,13 +12,13 @@ topics: - Billing --- -## {% data variables.product.prodname_codespaces %} pricing +## Precios de {% data variables.product.prodname_codespaces %} -{% data variables.product.prodname_codespaces %} usage is billed for all accounts on the Team and Enterprise plans, and does not include any entitlements. Individual accounts are not currently billed for {% data variables.product.prodname_codespaces %} usage. +El uso de {% data variables.product.prodname_codespaces %} se factura para todas las cuentas en los planes de equipo y empresa y no incluye ningún derecho. El uso de {% data variables.product.prodname_codespaces %} no se cobra actualmente para las cuentas individuales. -{% data variables.product.prodname_codespaces %} usage is billed according to the units of measure in the following table: +El uso de {% data variables.product.prodname_codespaces %} se cobra de acuerdo con las unidades de medida en la siguiente tabla: - Product | SKU | Unit of measure | Price | | ------------------- | -------- | --------------- | ----- | | Codespaces Compute | 2 core | 1 hour | $0.18 | | | 4 core | 1 hour | $0.36 | | | 8 core | 1 hour | $0.72 | | | 16 core | 1 hour | $1.44 | | | 32 core | 1 hour | $2.88 | | Codespaces Storage | Storage | 1 GB-month | $0.07 | + Producto | SKU | Unidad de medida| Precio| | ------------------- | -------- | --------------- | ----- | | Codespaces Compute | 2 núcleos| 1 hora | $0.18 | | | 4 núcleos | 1 hora | $0.36 | | | 8 núcleos | 1 hora | $0.72 | | | 16 núcleos | 1 hora | $1.44 | | | 32 núcleos | 1 hora | $2.88 | | Codespaces Storage | Almacenamiento | 1 GB-mes | $0.07 | ## Acerca de la facturación para {% data variables.product.prodname_codespaces %} @@ -26,9 +26,11 @@ topics: Tu uso de {% data variables.product.prodname_codespaces %} comparte la fecha de facturación, método de pago y recibo existente en tu cuenta. {% data reusables.dotcom_billing.view-all-subscriptions %} -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 {% data variables.product.prodname_codespaces %} usage. Para obtener más información, consulta la sección "[Conectar una suscripción de Azure a tu empresa](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)". +Si compraste {% data variables.product.prodname_enterprise %} mediante un Acuerdo de Microsoft Enterprise, puedes conectar tu ID de Suscripción de Azure a tu cuenta empresarial para habilitar y pagar por el uso de {% data variables.product.prodname_codespaces %}. Para obtener más información, consulta la sección "[Conectar una suscripción de Azure a tu empresa](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)". -## Setting a spending limit +{% data reusables.dotcom_billing.pricing_cal %} + +## Configurar un límite de gastos {% data reusables.codespaces.codespaces-spending-limit-requirement %} @@ -36,16 +38,16 @@ Para obtener más información sobre cómo administrar y cambiar el límite de g {% data reusables.codespaces.exporting-changes %} -## How billing is handled for forked repositories +## Cómo se maneja la facturación para los repositorios bifurcados -{% data variables.product.prodname_codespaces %} can only be used in organizations where a billable owner has been defined. To incur charges to the organization, the user must be a member or collaborator, otherwise they cannot create a codespace. +Los {% data variables.product.prodname_codespaces %} solo pueden utilizarse en las organizaciones donde se haya definido un propietario al que se le pueda facturar. Para incurrir en cargos a la organización, el usuario debe ser un miembro o colaborador, de lo contrario, no podrán crear un codespace. -For example, a user in a private organization can fork a repository within that organization, and can subsequently use a codespace billed to the organization; this is because the organization is the owner of the parent repository, which can remove the user's access, the forked repository, and the codespace. +Por ejemplo, un usuario en una organización privada puede bifurcar un repositorio dentro de dicha organización y puede utilizar subsecuentemente un codespace que se facture a la organización; esto es porque la organización es la propietaria del repositorio padre, la cual puede eliminar el acceso del usuario, el repositorio bifurcado y el codespace. -## How billing is handled when a repository is transferred +## Cómo se maneja la facturación cuando se transfiere un repositorio -Usage is billed and reported on every hour. As such, you pay for any usage when a repository is within your organization. When a repository is transferred out of your organization, any codespaces in that repository are removed as part of the transfer process. +El uso se cobra y reporta por hora. Como tal, pagas por cualquier uso cuando un repositorio se encuentra dentro de tu organización. Cuando un repositorio se transfiere fuera de tu organización, cualquier codespace en este repositorio se elimina como parte del proceso de transferencia. -## What happens when users are removed +## Lo que sucede cuando se eliminan usuarios -If a user is removed from an organization or repository, their codespaces are automatically deleted. +Si un usuario se elimina de una organización o repositorio, su codespace se borra automáticamente. diff --git a/translations/es-ES/content/billing/managing-billing-for-github-codespaces/index.md b/translations/es-ES/content/billing/managing-billing-for-github-codespaces/index.md index f0bbc96162..0d0d3d42ec 100644 --- a/translations/es-ES/content/billing/managing-billing-for-github-codespaces/index.md +++ b/translations/es-ES/content/billing/managing-billing-for-github-codespaces/index.md @@ -1,5 +1,5 @@ --- -title: Managing billing for GitHub Codespaces +title: Administrar la facturación para GitHub Codespaces shortTitle: Codespaces intro: 'Puedes ver el uso y configurar un límite de gastos para {% data variables.product.prodname_codespaces %}.' versions: diff --git a/translations/es-ES/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md b/translations/es-ES/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md index 84a4717806..55df3c6ee7 100644 --- a/translations/es-ES/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md +++ b/translations/es-ES/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md @@ -1,5 +1,5 @@ --- -title: Managing spending limits for Codespaces +title: Administrar los límites de gastos para los Codespaces intro: 'Puedes configurar un límite de gastos para el uso de {% data variables.product.prodname_codespaces %}.' versions: fpt: '*' @@ -19,12 +19,12 @@ shortTitle: Límites de gastos {% data reusables.codespaces.codespaces-spending-limit-requirement %} -Once you've reached your spending limit, your organization or repository will no longer be able to create new codespaces, and won't be able to start existing codespaces. Any existing codespaces that are still running will not be shutdown; if you don't change the spending limit, you will not be charged for the amount that exceeds the limit. +Una vez que hayas llegado a tu límite de gastos, tu organización o repositorio ya no podrán crear codespces nuevos y no podrán iniciar los existentes. Cualquier codespace existente que aún se esté ejecutando no se cerrará. Si no cambias el límite de gastos, no se tecobrará por la cantidad que exceda el límite. Para obtener más información sobre los costos de uso de {% data variables.product.prodname_codespaces %}, consulta la sección "[Acerca de la facturación para {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces)". -## Using your Azure Subscription -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 {% data variables.product.prodname_codespaces %} usage. Para obtener más información, consulta la sección "[Conectar una suscripción de Azure a tu empresa](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)". +## Utilizar tu suscripción de Azure +Si compraste {% data variables.product.prodname_enterprise %} mediante un Acuerdo de Microsoft Enterprise, puedes conectar tu ID de Suscripción de Azure a tu cuenta empresarial para habilitar y pagar por el uso de {% data variables.product.prodname_codespaces %}. Para obtener más información, consulta la sección "[Conectar una suscripción de Azure a tu empresa](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)". ## Administrar el límite de gastos de {% data variables.product.prodname_codespaces %} para tu organización @@ -42,15 +42,15 @@ Los propietarios de la empresa y gerentes de facturación pueden administrar el {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.billing-tab %} -1. Above "{% data variables.product.prodname_codespaces %} monthly usage", click **Spending Limit**. ![Pestaña de límite de gastos](/assets/images/help/settings/spending-limit-tab-enterprise.png) +1. Sobre "Uso mensual de {% data variables.product.prodname_codespaces %}", haz clic en **Límite de gastos**. ![Pestaña de límite de gastos](/assets/images/help/settings/spending-limit-tab-enterprise.png) {% data reusables.dotcom_billing.monthly-spending-limit %} {% data reusables.dotcom_billing.update-spending-limit %} -## Exporting changes when you have reached your spending limit +## Exportar cambios cuando llegaste a tu límite de gastos {% data reusables.codespaces.exporting-changes %} -## Managing usage and spending limit email notifications +## Administrar las notificaciones de uso y límite de gastos -Email notifications are sent to account owners and billing managers when spending reaches 50%, 75%, and 90% of your account's spending limit. +Las notificaciones por correo electrónico se envían a los propietarios de las cuentas y gerentes de facturación cuando el límite de gastos llega a 50%, 75%, y 90% del límite de gastos de tu cuenta. -You can disable these notifications anytime by navigating to the bottom of the **Spending Limit** page. +Puedes inhabilitar estas notificaciones en cualquier momento si navegas al final de la página del **Límite de Gastos**. diff --git a/translations/es-ES/content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md b/translations/es-ES/content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md index 63472d7fd9..34961695bc 100644 --- a/translations/es-ES/content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md +++ b/translations/es-ES/content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md @@ -1,7 +1,7 @@ --- -title: Viewing your Codespaces usage -shortTitle: Viewing your usage -intro: 'You can view the compute minutes and storage used by {% data variables.product.prodname_codespaces %}.' +title: Ver el uso de tus Codespaces +shortTitle: Ver tu uso +intro: 'Puedes ver los minutos de cálculo y almacenamiento que utilizan los {% data variables.product.prodname_codespaces %}.' permissions: 'To manage billing for Codespaces for an organization, you must be an organization owner or a billing manager.' product: '{% data reusables.gated-features.codespaces %}' versions: @@ -14,7 +14,7 @@ topics: ## Visualizar el uso de {% data variables.product.prodname_codespaces %} para tu organización -Los propietarios de la organización y gerentes de facturación pueden ver el uso de {% data variables.product.prodname_codespaces %} para una organización. For organizations managed by an enterprise account, the organization owners can view {% data variables.product.prodname_codespaces %} usage in the organization billing page, and enterprise admins can view the usage for the entire enterprise. +Los propietarios de la organización y gerentes de facturación pueden ver el uso de {% data variables.product.prodname_codespaces %} para una organización. Para las organizaciones que administra una cuenta empresarial, los propietarios de estas pueden ver el uso de los {% data variables.product.prodname_codespaces %} en la página de facturación de la misma y los administradores empresariales pueden ver el uso de toda la empresa. {% data reusables.organizations.billing-settings %} {% data reusables.dotcom_billing.codespaces-minutes %} @@ -26,4 +26,4 @@ Los propietarios de empresa y gerentes de facturación pueden ver el uso de {% d {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.billing-tab %} -1. Under "{% data variables.product.prodname_codespaces %}", view the usage details of each organization in your enterprise account. +1. Debajo de "{% data variables.product.prodname_codespaces %}", ve los detalles de uso de cada organización en tu cuenta empresarial. 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 9f0407aaff..c92f80c5e2 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 @@ -47,9 +47,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. 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 %} 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. -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.25 USD per GB or $37 USD. The overage for data transfer would cost $0.50 USD per GB or $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. 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. {% data reusables.dotcom_billing.pricing_cal %} Al final del mes, {% data variables.product.prodname_dotcom %} redondea tu transferencia de datos al número de GB más cercano. diff --git a/translations/es-ES/content/billing/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages.md b/translations/es-ES/content/billing/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages.md index 2324f0125f..d2904315bd 100644 --- a/translations/es-ES/content/billing/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages.md +++ b/translations/es-ES/content/billing/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages.md @@ -61,5 +61,5 @@ Los propietarios de la empresa y gerentes de facturación pueden administrar el {% data reusables.dotcom_billing.monthly-spending-limit %} {% data reusables.dotcom_billing.update-spending-limit %} -## Managing usage and spending limit email notifications +## Administrar las notificaciones de uso y límite de gastos {% data reusables.billing.email-notifications %} diff --git a/translations/es-ES/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md b/translations/es-ES/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md index 5fe86c0c89..3087778e2c 100644 --- a/translations/es-ES/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md +++ b/translations/es-ES/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md @@ -1,5 +1,5 @@ --- -title: About billing for your enterprise +title: Acerca de la facturación de tu empresa intro: Puedes visualizar la información de facturación para tu empresa. product: '{% data reusables.gated-features.enterprise-accounts %}' redirect_from: @@ -13,10 +13,10 @@ versions: ghae: '*' topics: - Enterprise -shortTitle: Billing for your enterprise +shortTitle: Facturación de tu empresa --- -## About billing for your enterprise +## Acerca de la facturación para tu empresa {% ifversion ghae %} @@ -45,23 +45,23 @@ Puedes ver tu uso actual en tu [Portal de cuenta de Azure](https://portal.azure. {% ifversion fpt %} -{% data variables.product.company_short %} bills monthly for the total number of members in your enterprise account, as well as any additional services you use with {% data variables.product.prodname_ghe_cloud %}. +{% data variables.product.company_short %} cobra mensualmente por la cantidad total de miembros en tu cuenta empresarial, así como por cualquier servicio que utilices con {% data variables.product.prodname_ghe_cloud %}. {% elsif ghes %} -Each user on {% data variables.product.product_location %} consumes a seat on your license. {% data variables.product.company_short %} bills monthly for the total number of seats consumed on your license. +Cada usuario en {% data variables.product.product_location %} consume una plaza en tu licencia. {% data variables.product.company_short %} cobra mensualmente por la cantidad total de plazas que se consumen en tu licencia. {% endif %} {% data reusables.billing.about-invoices-for-enterprises %} Para obtener más información sobre el uso y las facturas, consulta las secciones "[Visualizar la suscripción y uso para tu cuenta empresarial](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)" y {% ifversion ghes %}"Administrar las facturas de tu empresa" en la documentación de {% data variables.product.prodname_dotcom_the_website %}.{% elsif fpt %}"[Administrar las facturas de tu empresa](/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise)".{% endif %} -Administrators for your enterprise account on {% data variables.product.prodname_dotcom_the_website %} can access and manage billing for the enterprise. +Los administradores de tu cuenta empresarial de {% data variables.product.prodname_dotcom_the_website %} pueden acceder y administrar la facturación de la empresa. {% ifversion fpt %} -Each member of your enterprise account with a unique email address consumes a license. Billing managers do not consume a license. Each outside collaborator on a private repository that an organization in your enterprise owns consumes a license, unless the private repository is a fork. Each invitee to your enterprise account, including owners, members of organizations, and outside collaborators, consume a license. For more information about roles in an enterprise account, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" and "[Inviting people to manage your enterprise](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)." +Cada miembro de tu cuenta empresarial con una dirección de correo electrónico única consumirá una plaza. Los gerentes de facturación no consumen plazas. Cada colaborador externo de un repositorio privado que pertenezca a una organización en tu empresa consumirá una licencia, a menos de que dicho repositorio privado sea una bifurcación. Cada invitado a tu cuenta empresarial, incluyendo a los propietarios, miembros de las organizaciones y colaboradores externos, consumirán una licencia. Para obtener más información sobre los roles en una cuenta empresarial, consulta las secciones "[Roles en una empresa](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" y "[Invitar a personas para que administren tu empresa](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)". -{% data reusables.enterprise-accounts.billing-microsoft-ea-overview %} For more information, see "[Connecting an Azure subscription to your enterprise](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)." +{% data reusables.enterprise-accounts.billing-microsoft-ea-overview %} Para obtener más información, consulta la sección "[Conectar una suscripción de Azure a tu empresa](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)". {% endif %} @@ -71,7 +71,7 @@ Each member of your enterprise account with a unique email address consumes a li {% endif %} -## About synchronization of license usage +## Acerca de la sincronización del uso de licencias {% data reusables.enterprise.about-deployment-methods %} @@ -81,5 +81,5 @@ Each member of your enterprise account with a unique email address consumes a li ## Leer más -- "[About enterprise accounts]({% ifversion fpt or ghes %}/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts#about-enterprise-accounts-on-githubcom{% elsif ghae %}/admin/overview/about-enterprise-accounts{% endif %})"{% ifversion fpt or ghes %} -- "[About licenses for GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)"{% endif %} +- "[Acerca de las cuentas empresariales]({% ifversion fpt or ghes %}/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts#about-enterprise-accounts-on-githubcom{% elsif ghae %}/admin/overview/about-enterprise-accounts{% endif %})"{% ifversion fpt or ghes %} +- "[Acerca de las licencias para GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)"{% endif %} diff --git a/translations/es-ES/content/billing/managing-billing-for-your-github-account/index.md b/translations/es-ES/content/billing/managing-billing-for-your-github-account/index.md index addb94ec73..0150066661 100644 --- a/translations/es-ES/content/billing/managing-billing-for-your-github-account/index.md +++ b/translations/es-ES/content/billing/managing-billing-for-your-github-account/index.md @@ -1,7 +1,7 @@ --- title: Administrar la facturación para tu cuenta de GitHub shortTitle: Tu cuenta de GitHub -intro: '{% ifversion fpt %}{% data variables.product.product_name %} offers free and paid products for every account. You can upgrade, downgrade, and view pending changes to your account''s subscription at any time.{% elsif ghes or ghae %}You can manage billing for {% data variables.product.product_name %}{% ifversion ghae %}.{% elsif ghes %} from your enterprise account on {% data variables.product.prodname_dotcom_the_website %}.{% endif %}{% endif %}' +intro: '{% ifversion fpt %}{% data variables.product.product_name %} ofrece productos gratuitos y de pago para todas las cuentas. Puedes mejorar, bajar de nivel y ver los cambios pendientes a la suscripción de tu cuenta en cualquier momento.{% elsif ghes or ghae %}Puedes administrar la configuración de {% data variables.product.product_name %}{% ifversion ghae %}.{% elsif ghes %} desde tu cuenta empresarial en {% data variables.product.prodname_dotcom_the_website %}.{% endif %}{% endif %}' redirect_from: - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account - /categories/97/articles/ diff --git a/translations/es-ES/content/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise.md b/translations/es-ES/content/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise.md index df3bf2c299..e09b968a69 100644 --- a/translations/es-ES/content/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise.md +++ b/translations/es-ES/content/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise.md @@ -1,7 +1,7 @@ --- -title: Managing invoices for your enterprise -shortTitle: Manage invoices -intro: 'You can view, pay, or download a current invoice for your enterprise, and you can view your payment history.' +title: Administrar facturas para tu empresa +shortTitle: Adminsitrar las facturas +intro: 'Puedes ver, pagar o descargar una factura actual de tu empresa y puedes ver tu historial de pagos.' product: '{% data reusables.gated-features.enterprise-accounts %}' versions: fpt: '*' @@ -11,11 +11,11 @@ topics: - Licensing --- -## About invoices for your enterprise +## Acerca de las facturas de tu empresa -{% data reusables.billing.about-invoices-for-enterprises %} For more information, see "[About billing for your enterprise](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)." +{% data reusables.billing.about-invoices-for-enterprises %} Para obtener más información, consulta la sección "[Acerca de la facturación de tu empresa](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)". -For more information about viewing the subscription and usage for your enterprise account, see "[Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)." +Para obtener más información, acerca de la visualización de suscripciones y uso de tu cuenta empresarial, consulta la sección "[visualizar la suscripción y uso de tu cuenta empresarial](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)". {% data reusables.billing.ghes-with-no-enterprise-account %} @@ -24,14 +24,14 @@ For more information about viewing the subscription and usage for your enterpris {% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.billing-tab %} -4. Under "Current Invoice", click **View invoice**. ![Enlace para ver factura](/assets/images/help/business-accounts/view-invoice-link.png) +4. Debajo de "Factura actual", haz clic en **Ver factura**. ![Enlace para ver factura](/assets/images/help/business-accounts/view-invoice-link.png) ## Pagar tu factura actual {% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.billing-tab %} -4. Under "Payment Due", click **Pay invoice**. ![Enlace para pagar factura](/assets/images/help/business-accounts/pay-invoice-link.png) +4. Debajo de "Pago adeudado", haz clic en **Pagar factura**. ![Enlace para pagar factura](/assets/images/help/business-accounts/pay-invoice-link.png) 5. Debajo de "Pagar factura", teclea tu información de tarjeta de crédito en la forma segura, posteriormente, da clic en **Pagar factura**. ![Confirmar y pagar la factura](/assets/images/help/business-accounts/pay-invoice.png) ## Descargar tu factura actual @@ -46,4 +46,4 @@ For more information about viewing the subscription and usage for your enterpris {% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.billing-tab %} -4. To see a summary of your past billing activity, under "Billing", click the **Past Invoices** tab. ![Pestaña de ver historial de pago](/assets/images/help/business-accounts/view-payment-history.png) +4. Para ver un resumen de tu actividad de facturación anterior, debajo de "Facturación", haz clic en la pestaña de **Facturas pasadas**. ![Pestaña de ver historial de pago](/assets/images/help/business-accounts/view-payment-history.png) diff --git a/translations/es-ES/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md b/translations/es-ES/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md index e51c9034a7..9e4fa1abc7 100644 --- a/translations/es-ES/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md +++ b/translations/es-ES/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md @@ -1,6 +1,6 @@ --- title: Ver la suscripción y el uso de tu cuenta de empresa -intro: 'You can view the current {% ifversion fpt %}subscription, {% endif %}license usage{% ifversion fpt %}, invoices, payment history, and other billing information{% endif %} for {% ifversion fpt %}your enterprise account{% elsif ghes %}{% data variables.product.product_location_enterprise %}{% endif %}.' +intro: 'Puedes ver {% ifversion fpt %}la suscripción, {% endif %}el uso de licencia{% ifversion fpt %}, facturas, historial de pagos y otra información de facturación{% endif %} para {% ifversion fpt %}tu cuenta empresarial{% elsif ghes %}{% data variables.product.product_location_enterprise %}{% endif %}.' product: '{% data reusables.gated-features.enterprise-accounts %}' permissions: 'Enterprise owners {% ifversion fpt %}and billing managers {% endif %}can access and manage all billing settings for enterprise accounts.' redirect_from: @@ -18,21 +18,21 @@ shortTitle: Ver la suscripción & uso ## Acerca de la facturación para las cuentas de empresa -You can view an overview of {% ifversion fpt %}your subscription and paid{% elsif ghes %}the license{% endif %} usage for {% ifversion fpt %}your{% elsif ghes %}the{% endif %} enterprise account on {% ifversion fpt %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %}. +Puedes ver un resumen de {% ifversion fpt %}tu suscripción y uso de tu {% elsif ghes %}licencia pagada{% endif %} para {% ifversion fpt %}tu{% elsif ghes %}la{% endif %} cuenta empresarial en {% ifversion fpt %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %}. -For invoiced {% data variables.product.prodname_enterprise %} customers{% ifversion ghes %} who use both {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}{% endif %}, each invoice includes details about billed services for all products. For example, in addition to your usage for {% ifversion fpt %}{% data variables.product.prodname_ghe_cloud %}{% elsif ghes %}{% data variables.product.product_name %}{% endif %}, you may have usage for {% data variables.product.prodname_GH_advanced_security %}{% ifversion fpt %}, {% elsif ghes %}. You may also have usage on {% data variables.product.prodname_dotcom_the_website %}, like {% endif %}paid licenses in organizations outside of your enterprise account, data packs for {% data variables.large_files.product_name_long %}, or subscriptions to apps in {% data variables.product.prodname_marketplace %}. For more information about invoices, see "{% ifversion fpt %}[Managing invoices for your enterprise](/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise)."{% elsif ghes %}Viewing the subscription and usage for your enterprise account" in the {% data variables.product.prodname_dotcom_the_website %} documentation.{% endif %} +Para los clientes de {% data variables.product.prodname_enterprise %} a quienes se factura{% ifversion ghes %} quienes usan tanto {% data variables.product.prodname_ghe_cloud %} como {% data variables.product.prodname_ghe_server %}{% endif %}, cada factura incluye detalles sobre los servicios que se cobran de todos los productos. Por ejemplo, adicionalmente a tu uso de {% ifversion fpt %}{% data variables.product.prodname_ghe_cloud %}{% elsif ghes %}{% data variables.product.product_name %}{% endif %}, puedes tener un uso de {% data variables.product.prodname_GH_advanced_security %}{% ifversion fpt %},{% elsif ghes %}. También puedes tener uso en {% data variables.product.prodname_dotcom_the_website %}, como {% endif %}licencias de pago en organizaciones fuera de tu cuenta empresarial, paquetes de datos para {% data variables.large_files.product_name_long %} o suscripciones en apps dentro de {% data variables.product.prodname_marketplace %}. Para obtener más información sobre las facturas, consulta la sección "{% ifversion fpt %}[Administrar las facturas de tu empresa](/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise)".{% elsif ghes %}Visualizar la suscripción y uso de tu cuenta empresarial" en la documentación de {% data variables.product.prodname_dotcom_the_website %}.{% endif %} {% ifversion fpt %} -In addition to enterprise owners, billing managers can view the subscription and usage for your enterprise account. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise#billing-manager)" and "[Inviting people to manage your enterprise](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)." +Adicionalmente a los propietarios de empresas, los gerentes de facturación pueden ver la suscripción y el uso de tu cuenta empresarial. Para obtener más información, consulta las secciones "[Roles en una empresa](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise#billing-manager)" y "[Invitar a las personas para que administren tu empresa](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)". -{% data reusables.enterprise-accounts.billing-microsoft-ea-overview %} For more information, see "[Connecting an Azure subscription to your enterprise](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)." +{% data reusables.enterprise-accounts.billing-microsoft-ea-overview %} Para obtener más información, consulta la sección "[Conectar una suscripción de Azure a tu empresa](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)". {% endif %} {% ifversion ghes %} -If you want to view an overview of your subscription and usage for {% data variables.product.prodname_enterprise %} and any related services on {% data variables.product.prodname_dotcom_the_website %}, see "[Viewing the subscription and usage for your enterprise account](/free-pro-team@latest/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)" in the {% data variables.product.prodname_dotcom_the_website %} documentation. +Si quieres ver un resumen de tu uso y suscripción de {% data variables.product.prodname_enterprise %} y de cualquier servicio relacionado en {% data variables.product.prodname_dotcom_the_website %}, consulta la sección de "[Ver el uso y suscripción de tu cuenta empresarial](/free-pro-team@latest/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)" en la documentación de {% data variables.product.prodname_dotcom_the_website %}. {% endif %} @@ -41,7 +41,7 @@ If you want to view an overview of your subscription and usage for {% data varia {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.license-tab %} -1. Under "User licenses", view your total licenses, number of consumed licenses, and your subscription expiration date. +1. En "Licencias de Usuario", ve tus licencias totales, la cantidad de licencias consumidas y la fecha de vencimiento de tu suscripción. {% ifversion fpt %}![License and subscription information in enterprise billing settings](/assets/images/help/business-accounts/billing-license-info.png){% else %} ![Información de licencia y suscripción en las configuraciones de facturación de la empresa](/assets/images/enterprise/enterprise-server/enterprise-server-billing-license-info.png){% endif %} 1. Opcionalmente, para ver los detalles del uso de licencia o para descargar un archivo {% ifversion fpt %}CSV{% elsif ghes %}JSON{% endif %} con los detalles de la misma{% ifversion fpt %}, a la derecha de "Licencias de Usuario"{% endif %}, haz clic en **Ver {% ifversion fpt %}detalles{% elsif ghes %}usuarios{% endif %}** o {% ifversion fpt %}{% octicon "download" aria-label="The download icon" %}{% elsif ghes %}**Eportar uso de licencia**{% endif %}.{% ifversion fpt %}!["View details" button and button with download icon to the right of "User Licenses"](/assets/images/help/business-accounts/billing-license-info-click-view-details-or-download.png){% endif %}{% ifversion fpt %} diff --git a/translations/es-ES/content/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method.md b/translations/es-ES/content/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method.md index e10f163373..c4862b3317 100644 --- a/translations/es-ES/content/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method.md +++ b/translations/es-ES/content/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method.md @@ -34,9 +34,9 @@ No entregamos facturas u órdenes de compra de respaldo a cuentas personales. En {% data reusables.user_settings.billing_plans %} {% data reusables.dotcom_billing.update_payment_method %} -1. If your account has existing billing information that you want to update, click **Edit**. ![Botón de facturar con tarjeta nueva](/assets/images/help/billing/billing-information-edit-button.png) +1. Si tu cuenta tiene información de facturación existente que quieras actualizar, haz clic en **Editar**. ![Botón de facturar con tarjeta nueva](/assets/images/help/billing/billing-information-edit-button.png) {% data reusables.dotcom_billing.enter-billing-info %} -1. If your account has an existing payment method that you want to update, click **Edit**. ![Botón de facturar con tarjeta nueva](/assets/images/help/billing/billing-payment-method-edit-button.png) +1. Si tu cuenta tiene un método de pago existente que quieras actualizar, haz clic en **Editar**. ![Botón de facturar con tarjeta nueva](/assets/images/help/billing/billing-payment-method-edit-button.png) {% data reusables.dotcom_billing.enter-payment-info %} ## Actualizar el método de pago de tu organización diff --git a/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md b/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md index 9d2eae4967..61a79a9059 100644 --- a/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md +++ b/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md @@ -1,6 +1,6 @@ --- -title: About licenses for GitHub Enterprise -intro: '{% ifversion fpt %}If you purchase {% data variables.product.prodname_enterprise %} and use {% data variables.product.prodname_ghe_server %}, each{% elsif ghes %}Each{% endif %} {% data variables.product.prodname_ghe_server %} instance requires a license file to validate and unlock the application.' +title: Acerca de las licencias para GitHub Enterprise +intro: '{% ifversion fpt %}Si compras {% data variables.product.prodname_enterprise %} y utilizas {% data variables.product.prodname_ghe_server %}, cada{% elsif ghes %}Cada{% endif %} instancia de {% data variables.product.prodname_ghe_server %} requerirá un archivo de licencia para validar y desbloquear la aplicación.' versions: fpt: '*' ghes: '*' @@ -8,10 +8,10 @@ type: overview topics: - Enterprise - Licensing -shortTitle: About licenses +shortTitle: Acerca de las licencias --- -## About license files for {% data variables.product.prodname_enterprise %} +## Acerca de los archivos de licencia para {% data variables.product.prodname_enterprise %} {% ifversion fpt %} @@ -19,13 +19,13 @@ shortTitle: About licenses {% endif %} -When you purchase or renew {% data variables.product.prodname_enterprise %}, {% data variables.product.company_short %} provides a license file {% ifversion fpt %}for your deployments of {% data variables.product.prodname_ghe_server %}{% elsif ghes %}for {% data variables.product.product_location_enterprise %}{% endif %}. A license file has an expiration date and controls the number of people who can use {% data variables.product.product_location_enterprise %}. After you download and install {% data variables.product.prodname_ghe_server %}, you must upload the license file to unlock the application for you to use. +Cuando compras o renuevas tu suscripción de {% data variables.product.prodname_enterprise %}, {% data variables.product.company_short %} te proporciona un archivo de licencia {% ifversion fpt %}para tus despliegues de {% data variables.product.prodname_ghe_server %}{% elsif ghes %} para {% data variables.product.product_location_enterprise %}{% endif %}. Un archivo de licencia tiene una fecha de vencimiento y controla la cantidad de personas que pueden utilizar {% data variables.product.product_location_enterprise %}. Después de que descargas e instalas {% data variables.product.prodname_ghe_server %}, debes cargar un archivo de licencia para desbloquear la aplicación para tu uso. -For more information about downloading your license file, see "[Downloading your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)." For more information about uploading your license file, see {% ifversion fpt %}"[Uploading a new license to {% data variables.product.prodname_ghe_server %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}"[Uploading a new license to {% data variables.product.prodname_ghe_server %}](/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)."{% endif %} +Para obtener más información sobre cómo descargar tu archivo de licencia, consulta la sección "[Descargar tu licencia para {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)". Para obtener más información acerca de subir tu archivo de licencias, consulta la sección {% ifversion fpt %}"[Cargar una licencia nueva en {% data variables.product.prodname_ghe_server %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)" en la documentación de {% data variables.product.prodname_ghe_server %}.{% elsif ghes %}"[Cargar una licencia nueva en {% data variables.product.prodname_ghe_server %}](/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)".{% endif %} -If your license expires, you won't be able to access {% data variables.product.prodname_ghe_server %} via a web browser or Git. Si es necesario, podrás usar herramientas de línea de comando para hacer un respaldo de seguridad de todos tus datos. Para obtener más información, consulta "[Configurar copias de seguridad en tu aparato](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance)" Si tienes cualquier duda sobre el renovamiento de tu licencia, contacta a {% data variables.contact.contact_enterprise_sales %}. +Si tu licencia vence, no podrás acceder a {% data variables.product.prodname_ghe_server %} a través del buscador web o de Git. Si es necesario, podrás usar herramientas de línea de comando para hacer un respaldo de seguridad de todos tus datos. Para obtener más información, consulta "[Configurar copias de seguridad en tu aparato](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance)" Si tienes cualquier duda sobre el renovamiento de tu licencia, contacta a {% data variables.contact.contact_enterprise_sales %}. -## About synchronization of license usage for {% data variables.product.prodname_enterprise %} +## Acerca de la sincronización de uso de licencias para {% data variables.product.prodname_enterprise %} {% ifversion ghes %} @@ -37,6 +37,6 @@ If your license expires, you won't be able to access {% data variables.product.p ## Leer más -- "[About billing for your enterprise](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)" -- [{% data variables.product.prodname_enterprise %} Releases](https://enterprise.github.com/releases/) website -- "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/admin/installation/setting-up-a-github-enterprise-server-instance)" +- "[Acerca de la facturación para tu empresa](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)" +- Sitio web de [Lanzamientos de {% data variables.product.prodname_enterprise %}](https://enterprise.github.com/releases/) +- "[Configurar una instancia de {% data variables.product.prodname_ghe_server %}](/admin/installation/setting-up-a-github-enterprise-server-instance)" diff --git a/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md b/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md index 334ecb707e..3b7336aa9b 100644 --- a/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md +++ b/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md @@ -1,6 +1,6 @@ --- -title: Downloading your license for GitHub Enterprise -intro: 'You can download a copy of your license file for {% data variables.product.prodname_ghe_server %}.' +title: Descargar tu licencia de GitHub Enterprise +intro: 'Puedes descargar una copia de tu archivo de licencia para {% data variables.product.prodname_ghe_server %}.' permissions: 'Enterprise owners can download license files for {% data variables.product.prodname_ghe_server %}.' versions: fpt: '*' @@ -9,28 +9,28 @@ type: how_to topics: - Enterprise - Licensing -shortTitle: Download your license +shortTitle: Descargar tu licencia --- -## About license files for {% data variables.product.prodname_enterprise %} +## Acerca de los archivos de licencia para {% data variables.product.prodname_enterprise %} -After you purchase or upgrade a license for {% data variables.product.prodname_enterprise %} from {% data variables.contact.contact_enterprise_sales %}, you must download your new license file. For more information about licenses for {% data variables.product.prodname_enterprise %}, see "[About licenses for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)." +Después de comprar o mejorar una licencia de {% data variables.product.prodname_enterprise %} desde {% data variables.contact.contact_enterprise_sales %}, debes descargar tu archivo de licencia nuevo. Para obtener más información sobre las licencias para {% data variables.product.prodname_enterprise %}, consulta la sección "[Acerca de las licencias de {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)". {% data reusables.enterprise-licensing.contact-sales-for-renewals-or-seats %} -## Downloading your license from {% data variables.product.prodname_dotcom_the_website %} +## Descargar tu licencia desde {% data variables.product.prodname_dotcom_the_website %} -You must have an enterprise account on {% data variables.product.prodname_dotcom_the_website %} to download your license from {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información sobre las cuentas empresariales, consulta la sección "[Acerca de las cuentas empresariales](/admin/overview/about-enterprise-accounts)". +Debes tener una cuenta empresarial en {% data variables.product.prodname_dotcom_the_website %} para descargar tu licencia de {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información sobre las cuentas empresariales, consulta la sección "[Acerca de las cuentas empresariales](/admin/overview/about-enterprise-accounts)". {% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} {% data reusables.enterprise-accounts.settings-tab %} 1. En la barra lateral izquierda, da clic en **Licenciamiento empresarial**. ![Pestaña de "Licencias empresariales" en la barra lateral de configuración para la cuenta empresarial](/assets/images/help/enterprises/enterprise-licensing-tab.png) 1. Debajo de "instancias de Enterprise Server", da clic en {% octicon "download" aria-label="The download icon" %} para descargar tu archivo de licencia. ![Descargar la licencia de GitHub Enterprise Server](/assets/images/help/business-accounts/download-ghes-license.png) -After you download your license file, you can upload the file to {% data variables.product.product_location_enterprise %} to validate your application. For more information, see {% ifversion fpt %}"[Uploading a new license to {% data variables.product.prodname_ghe_server %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}"[Uploading a new license to {% data variables.product.prodname_ghe_server %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)."{% endif %} +Después de que descargas tu archivo de licencia, puedes cargar el archivo a {% data variables.product.product_location_enterprise %} para validar tu aplicación. Para obtener más información, consulta la sección {% ifversion fpt %}"[Cargar una licencia nueva a {% data variables.product.prodname_ghe_server %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)" en la documentación de {% data variables.product.prodname_ghe_server %}.{% elsif ghes %}"[Cargar una licencia nueva a {% data variables.product.prodname_ghe_server %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)".{% endif %} -## Downloading your license if you don't have an enterprise account on {% data variables.product.prodname_dotcom_the_website %} +## Descargar tu licencia si no tienes una cuenta empresarial en {% data variables.product.prodname_dotcom_the_website %} -If you do not have an enterprise account on {% data variables.product.prodname_dotcom_the_website %}, or if you're not sure, you may be able to download your {% data variables.product.prodname_ghe_server %} license from the [{% data variables.product.prodname_enterprise %} website](https://enterprise.github.com/download). +Si no tienes una cuenta empresarial en {% data variables.product.prodname_dotcom_the_website %} o si no estás seguro de ello, podrías descarar tu licencia de {% data variables.product.prodname_ghe_server %} desde el [sitio web de {% data variables.product.prodname_enterprise %}](https://enterprise.github.com/download). -If you have any questions about downloading your license, contact {% data variables.contact.contact_enterprise_sales %}. +Si tienes cualquier pregunta sobre cómo descargar tu licencia, contacta a {% data variables.contact.contact_enterprise_sales %}. diff --git a/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/index.md b/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/index.md index 97f03f42b6..8382e4e8f0 100644 --- a/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/index.md +++ b/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/index.md @@ -1,7 +1,7 @@ --- -title: Managing your license for GitHub Enterprise -shortTitle: GitHub Enterprise license -intro: 'You can view, manage, and update your license for {% data variables.product.prodname_enterprise %}, which unlocks the application on {% data variables.product.product_location_enterprise %}.' +title: Administrar tu licencia de GitHub Enterprise +shortTitle: Licenci de GitHub Enterprise +intro: 'Puedes ver, administrar y actualizar tu licencia de {% data variables.product.prodname_enterprise %}, lo cual desbloquea la aplicación en {% data variables.product.product_location_enterprise %}.' redirect_from: - /enterprise/admin/installation/managing-your-github-enterprise-license - /enterprise/admin/categories/licenses/ diff --git a/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md b/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md index f1a3cdcf6d..da49923647 100644 --- a/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md +++ b/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md @@ -1,6 +1,6 @@ --- -title: Syncing license usage between GitHub Enterprise Server and GitHub Enterprise Cloud -intro: 'You can sync license usage from {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %} to view all license usage across your enterprise in one place and ensure that people with accounts in both environments only consume one user license.' +title: Sincornizar el uso de licencias entre GitHub Enterprise Server y GitHub Enterprise Cloud +intro: 'Puedes sincronizar el uso de licencias desde {% data variables.product.prodname_ghe_server %} hacia {% data variables.product.prodname_ghe_cloud %} para ver el uso de licencias a lo largo de tu empresa en un solo lugar y garantizar que las personas con cuentas en ambos ambientes solo consuman una licencia.' permissions: 'Enterprise owners can sync license usage between enterprise accounts on {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}.' versions: ghes: '*' @@ -8,22 +8,22 @@ type: how_to topics: - Enterprise - Licensing -shortTitle: Sync license usage +shortTitle: Sincronizar el uso de licencia --- -## About synchronization of license usage +## Acerca de la sincronización del uso de licencias {% data reusables.enterprise-licensing.about-license-sync %} -If you allow {% data variables.product.product_location %} to connect to {% data variables.product.prodname_dotcom_the_website %}, you can sync license usage between your enterprise accounts automatically. Automatic synchronization ensures that you see up-to-date license details on {% data variables.product.prodname_dotcom_the_website %}. If you don't want to allow {% data variables.product.product_location %} to connect to {% data variables.product.prodname_dotcom_the_website %}, you can manually sync license usage by uploading a file from {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}. +Si permites que {% data variables.product.product_location %} se conecte a {% data variables.product.prodname_dotcom_the_website %}, puedes sincronizar el uso de licencias entre tus cuentas empresariales automáticamente. La sincronización automática garantiza que veas los detalles actualizados de la licencia en {% data variables.product.prodname_dotcom_the_website %}. Si no quieres permitir que {% data variables.product.product_location %} se conecte con {% data variables.product.prodname_dotcom_the_website %}, puedes sincronizar la licencia manualmente cargando un archivo de {% data variables.product.product_location %} a {% data variables.product.prodname_dotcom_the_website %}. -For more information about licenses and usage for {% data variables.product.prodname_ghe_server %}, see "[About licenses for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)." +Para obtener más información sobre las licencias y el uso de {% data variables.product.prodname_ghe_server %}, consulta la sección "[Acerca de las licencias de {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)". -## Automatically syncing license usage +## Sincronizar el uso de licencias automáticamente Puedes utilizar {% data variables.product.prodname_github_connect %} para sincronizar de forma automática el conteo y el uso de la licencia de usuario entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta "[Habilitar la sincronización de licencia de usuario entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %}](/admin/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud)." -## Manually syncing license usage +## Sincronizar el uso de licencias manualmente Puedes descargar un archivo JSON desde {% data variables.product.prodname_ghe_server %} y subir el archivo a {% data variables.product.prodname_ghe_cloud %} para sincronizar de forma manual el uso de la licencia de usuario entre dos implementaciones. diff --git a/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md b/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md index c61a759147..5d138bfa26 100644 --- a/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md +++ b/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md @@ -1,22 +1,22 @@ --- -title: Uploading a new license to GitHub Enterprise Server -intro: 'You can upload your license file for {% data variables.product.prodname_enterprise %} to {% data variables.product.product_location_enterprise %} to validate your application.' +title: Cargar una licencia nueva a GitHub Enterprise Server +intro: 'Puedes cargar tu archivo de licencia para {% data variables.product.prodname_enterprise %} a {% data variables.product.product_location_enterprise %} para validar tu aplicación.' versions: ghes: '*' type: how_to topics: - Enterprise - Licensing -shortTitle: Upload a new license +shortTitle: Cargar una licencia nueva --- -## About license files for {% data variables.product.prodname_enterprise %} +## Acerca de los archivos de licencia para {% data variables.product.prodname_enterprise %} -After you purchase or upgrade a license for {% data variables.product.prodname_enterprise %} from {% data variables.contact.contact_enterprise_sales %}, you must upload the new license file to {% data variables.product.product_location_enterprise %} to unlock your new user licenses. For more information about licenses for {% data variables.product.product_name %}, see "[About licenses for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)" and "[Downloading your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)." +Después de que compras o mejoras una licencia de {% data variables.product.prodname_enterprise %} desde {% data variables.contact.contact_enterprise_sales %}, debes subir el nuevo archivo de licencia a {% data variables.product.product_location_enterprise %} para desbloquear tus licencias de usuario nuevas. Para obtener más información sobre las licencias para {% data variables.product.product_name %}, consulta las secciones "[Acerca de las licencias de {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)" y "[Descargar tu licencia de {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)". {% data reusables.enterprise-licensing.contact-sales-for-renewals-or-seats %} -## Uploading your license to {% data variables.product.product_location_enterprise %} +## Cargar tu licencia en {% data variables.product.product_location_enterprise %} 1. Inicia sesión en {% data variables.product.product_location_enterprise %} como administrador de sitio. {% data reusables.enterprise-accounts.access-enterprise %} @@ -28,7 +28,7 @@ After you purchase or upgrade a license for {% data variables.product.prodname_e {% ifversion ghes < 3.0 %} -If the web UI for {% data variables.product.prodname_ghe_server %} doesn't reflect your updated license immediately, see "[Troubleshooting](#troubleshooting)." +Si la IU web de {% data variables.product.prodname_ghe_server %} no refleja tu licencia actualizada de inmediato, consulta la sección de "[Solución de problemas](#troubleshooting)". ## Solución de problemas diff --git a/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md b/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md index 5b3668966b..021a4bbcc7 100644 --- a/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md +++ b/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md @@ -1,6 +1,6 @@ --- -title: Viewing license usage for GitHub Enterprise -intro: 'You can view license usage for your enterprise on {% ifversion fpt %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %}.' +title: Ver el uso de licencia para GitHub Enterprise +intro: 'Puedes ver el uso de licencia de tu empresa en {% ifversion fpt %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %}.' permissions: 'Enterprise owners can view license usage for {% data variables.product.prodname_enterprise %}.' versions: fpt: '*' @@ -9,26 +9,26 @@ type: how_to topics: - Enterprise - Licensing -shortTitle: View license usage +shortTitle: Ver el uso de licencia --- -## About license usage for {% data variables.product.prodname_enterprise %} +## Acerca del uso de licencia para {% data variables.product.prodname_enterprise %} {% ifversion fpt %} -You can view license usage for your enterprise account on {% data variables.product.prodname_ghe_cloud %} on {% data variables.product.prodname_dotcom_the_website %}. +Puedes ver el uso de licencia de tu cuenta empresarial de {% data variables.product.prodname_ghe_cloud %} en {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-licensing.you-can-sync-for-a-combined-view %} {% elsif ghes %} -You can view license usage for {% data variables.product.prodname_ghe_server %} on {% data variables.product.product_location %}. +Puedes ver el uso de licencia de {% data variables.product.prodname_ghe_server %} en {% data variables.product.product_location %}. -{% data reusables.enterprise-licensing.you-can-sync-for-a-combined-view %} For more information about the display of license usage on {% data variables.product.prodname_dotcom_the_website %}, see "Viewing license usage for {% data variables.product.prodname_enterprise %}" in the {% data variables.product.prodname_dotcom_the_website %} documentation. +{% data reusables.enterprise-licensing.you-can-sync-for-a-combined-view %} Para obtener más información sobre cómo se muestra el uso de licencia en {% data variables.product.prodname_dotcom_the_website %}, consulta la sección "Ver el uso de licencia para {% data variables.product.prodname_enterprise %}" en la documentación de {% data variables.product.prodname_dotcom_the_website %}. {% endif %} -## Viewing license usage on {% ifversion fpt %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %} +## Ver el uso de licencia en {% ifversion fpt %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %} {% ifversion fpt %} @@ -36,14 +36,14 @@ You can view license usage for {% data variables.product.prodname_ghe_server %} {% data reusables.enterprise-accounts.settings-tab %} 1. En la barra lateral izquierda, da clic en **Licenciamiento empresarial**. ![Pestaña de "Licencias empresariales" en la barra lateral de configuración para la cuenta empresarial](/assets/images/help/enterprises/enterprise-licensing-tab.png) 1. Revisa tus licencias actuales de {% data variables.product.prodname_enterprise %}, así como las licencias de usuario disponibles y consumidas. - - If your license includes {% data variables.product.prodname_GH_advanced_security %}, you can review your total seat use. Para obtener más información, consulta la sección "[Visualizar tu uso de {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage)". + - Si tu licencia incluye la {% data variables.product.prodname_GH_advanced_security %}, puedes revisar tu uso total de plazas. Para obtener más información, consulta la sección "[Visualizar tu uso de {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage)". {% elsif ghes %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.license-tab %} -1. Review your current {% data variables.product.prodname_enterprise %} license, as well as consumed and available user licenses.{% ifversion ghes > 3.0 %} - - If your license includes {% data variables.product.prodname_GH_advanced_security %}, you can review your total seat use as well as a per-organization breakdown of committers. Para obtener más información, consulta la sección "[Administrar la {% data variables.product.prodname_GH_advanced_security %} para tu empresa](/admin/advanced-security)".{% endif %} +1. Revisa tus licencias actuales de {% data variables.product.prodname_enterprise %}, así como las licencias de usuario disponibles y consumidas.{% ifversion ghes > 3.0 %} + - Si tu licencia incluye a la {% data variables.product.prodname_GH_advanced_security %}, puedes revisar tu uso total de plazas así como un desglose de confirmantes por organización. Para obtener más información, consulta la sección "[Administrar la {% data variables.product.prodname_GH_advanced_security %} para tu empresa](/admin/advanced-security)".{% endif %} {% endif %} diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md index 25f3b56441..5b5f072380 100644 --- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md +++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md @@ -1,7 +1,7 @@ --- -title: About code scanning with CodeQL -shortTitle: Code scanning with CodeQL -intro: 'You can use {% data variables.product.prodname_codeql %} to identify vulnerabilities and errors in your code. The results are shown as {% data variables.product.prodname_code_scanning %} alerts in {% data variables.product.prodname_dotcom %}.' +title: Acerca del escaneo de código con CodeQL +shortTitle: Escaneo de código con CodeQL +intro: 'Puedes utilizar {% data variables.product.prodname_codeql %} para identificar las vulnerabilidades y errores en tu código. Los resultados se muestran como alertas del {% data variables.product.prodname_code_scanning %} en {% data variables.product.prodname_dotcom %}.' product: '{% data reusables.gated-features.code-scanning %}' redirect_from: - /code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql @@ -23,39 +23,39 @@ topics: {% data reusables.code-scanning.about-codeql-analysis %} -There are two main ways to use {% data variables.product.prodname_codeql %} analysis for {% data variables.product.prodname_code_scanning %}: +Hay dos formas principales para utilizar el análisis de {% data variables.product.prodname_codeql %} para el {% data variables.product.prodname_code_scanning %}: -- Add the {% data variables.product.prodname_codeql %} workflow to your repository. This uses the [github/codeql-action](https://github.com/github/codeql-action/) to run the {% data variables.product.prodname_codeql_cli %}. Para obtener más información, consulta la sección "[Configurar el {% data variables.product.prodname_code_scanning %} en un repositorio](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)". -- Run the {% data variables.product.prodname_codeql %} {% ifversion fpt or ghes > 3.1 or ghae-next %}CLI directly {% elsif ghes = 3.0 %}CLI or runner {% else %}runner {% endif %} in an external CI system and upload the results to {% data variables.product.prodname_dotcom %}. For more information, see "[About {% data variables.product.prodname_codeql %} code scanning in your CI system ](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system)." +- Agregar el flujo de trabajo de {% data variables.product.prodname_codeql %} a tu repositorio. Esto utiliza la [github/codeql-action](https://github.com/github/codeql-action/) para ejecutar el {% data variables.product.prodname_codeql_cli %}. Para obtener más información, consulta la sección "[Configurar el {% data variables.product.prodname_code_scanning %} en un repositorio](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)". +- Ejecuta el {% data variables.product.prodname_codeql %} {% ifversion fpt or ghes > 3.1 or ghae-next %}CLI directamente {% elsif ghes = 3.0 %}CLI o el ejecutor {% else %}ejecutor{% endif %} en un sistema de IC externo y carga los resultados en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Acerca del escaneo de código de {% data variables.product.prodname_codeql %} en tu sistema de IC](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system)". ## Acerca de {% data variables.product.prodname_codeql %} -{% data variables.product.prodname_codeql %} treats code like data, allowing you to find potential vulnerabilities in your code with greater confidence than traditional static analyzers. +El {% data variables.product.prodname_codeql %} trata el código como datos, permitiéndote encontrar vulnerabilidades potenciales en tu código con mayor confianza que los analizadores estáticos tradicionales. -1. You generate a {% data variables.product.prodname_codeql %} database to represent your codebase. -2. Then you run {% data variables.product.prodname_codeql %} queries on that database to identify problems in the codebase. -3. The query results are shown as {% data variables.product.prodname_code_scanning %} alerts in {% data variables.product.product_name %} when you use {% data variables.product.prodname_codeql %} with {% data variables.product.prodname_code_scanning %}. +1. Generas una base de datos de {% data variables.product.prodname_codeql %} para representar tu base de código. +2. Entonces, ejecutarás consultas de {% data variables.product.prodname_codeql %} en esa base de datos para identificar problemas en la base de código. +3. Estos resultados de consulta se muestran como alertas del {% data variables.product.prodname_code_scanning %} en {% data variables.product.product_name %} cuando utilizas al {% data variables.product.prodname_codeql %} con el {% data variables.product.prodname_code_scanning %}. {% data variables.product.prodname_codeql %} es compatible tanto con los lenguajes compilados como con lso interpretados, y puede encontrar vulnerabilidades y errores en el código que se escriba en los lenguajes compatibles. {% data reusables.code-scanning.codeql-languages-bullets %} -## About {% data variables.product.prodname_codeql %} queries +## Acerca de las consultas de {% data variables.product.prodname_codeql %} -{% data variables.product.company_short %} experts, security researchers, and community contributors write and maintain the default {% data variables.product.prodname_codeql %} queries used for {% data variables.product.prodname_code_scanning %}. The queries are regularly updated to improve analysis and reduce any false positive results. The queries are open source, so you can view and contribute to the queries in the [`github/codeql`](https://github.com/github/codeql) repository. Para obtener más información, consulta la sección [{% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql) en el sitio web de GitHub Security Lab. You can also write your own queries. For more information, see "[About {% data variables.product.prodname_codeql %} queries](https://codeql.github.com/docs/writing-codeql-queries/about-codeql-queries/)" in the {% data variables.product.prodname_codeql %} documentation. +Los expertos de {% data variables.product.company_short %}, investigadores de seguridad y contribuyentes comunitarios escriben y mantienen las consultas predeterminadas de {% data variables.product.prodname_codeql %} que se utilizan para el {% data variables.product.prodname_code_scanning %}. Las consultas se actualizan frecuentemente para mejorar el análisis y reducir cualquier resultado falso positivo. Las consultas son de código abierto, así que puedes ver y contribuir con ellas en el repositorio de [`github/codeql`](https://github.com/github/codeql). Para obtener más información, consulta la sección [{% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql) en el sitio web de GitHub Security Lab. También puedes escribir tus propias consultas. Para obtener más información, consulta la sección "[Acerca de las consultas de {% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/writing-codeql-queries/about-codeql-queries/)" en la documentación de {% data variables.product.prodname_codeql %}. -You can run additional queries as part of your code scanning analysis. +Puedes ejecutar consultas adicionales como parte de tu análisis de escaneo de código. {%- if codeql-packs %} -These queries must belong to a published {% data variables.product.prodname_codeql %} query pack (beta) or a QL pack in a repository. {% data variables.product.prodname_codeql %} packs (beta) provide the following benefits over traditional QL packs: +Estas consultas deben pertenecer a un paquete de consultas (beta) de {% data variables.product.prodname_codeql %} publicado o a un paquete de QL en un repositorio. Los paquetes de {% data variables.product.prodname_codeql %} (beta) proporcionan los siguientes beneficios sobre los paquetes tradicionales de QL: -- When a {% data variables.product.prodname_codeql %} query pack (beta) is published to the {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %}, all the transitive dependencies required by the queries and a compilation cache are included in the package. This improves performance and ensures that running the queries in the pack gives identical results every time until you upgrade to a new version of the pack or the CLI. -- QL packs do not include transitive dependencies, so queries in the pack can depend only on the standard libraries (that is, the libraries referenced by an `import LANGUAGE` statement in your query), or libraries in the same QL pack as the query. +- Cuando un paquete de consultas de {% data variables.product.prodname_codeql %} (beta) se publica en el {% data variables.product.prodname_container_registry %} de {% data variables.product.company_short %}, todas las dependencias transitivas que requieren las consultas y un caché de compilación se incluyen en el paquete. Esto mejora el rendimiento y garantiza que el ejecutar las consultas del paquete proporciona resultados idénticos cada vez que actualizas a una versión nueva del paquete o de CLI. +- Los paquetes de QL no incluyen las dependencias transitivas, así que las consultas en el paquete puede depender únicamente de las librerías estándar (esto es, si las librerías se referencian mediante un argumento `import LANGUAGE` en tu consulta) o en las librerías del mismo paquete de QL que la consulta. -For more information, see "[About {% data variables.product.prodname_codeql %} packs](https://codeql.github.com/docs/codeql-cli/about-codeql-packs/)" and "[About {% data variables.product.prodname_ql %} packs](https://codeql.github.com/docs/codeql-cli/about-ql-packs/)" in the {% data variables.product.prodname_codeql %} documentation. +Para obtener más información, consulta las secciones "[Acerca de los paquetes de {% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-cli/about-codeql-packs/)" y "[Acerca de los paquetes de {% data variables.product.prodname_ql %}](https://codeql.github.com/docs/codeql-cli/about-ql-packs/)" en la documentación de {% data variables.product.prodname_codeql %}. {% data reusables.code-scanning.beta-codeql-packs-cli %} {%- else %} -The queries you want to run must belong to a QL pack in a repository. Queries must only depend on the standard libraries (that is, the libraries referenced by an `import LANGUAGE` statement in your query), or libraries in the same QL pack as the query. Para obtener más información, consulta la sección "[Acerca de los paquetes de {% data variables.product.prodname_ql %}](https://codeql.github.com/docs/codeql-cli/about-ql-packs/)". +Estas consultas que quieres ejecutar deben pertenecer al paquete de QL de un repositorio. Las consultas solo deberán depender de las librerías estándar (es decir, aquellas referenciadas por una declaración `import LANGUAGE` en tu consulta), o de aquellas en el mismo paquete de QL que la consulta. Para obtener más información, consulta la sección "[Acerca de los paquetes de {% data variables.product.prodname_ql %}](https://codeql.github.com/docs/codeql-cli/about-ql-packs/)". {% endif %} diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md index 05b40fd2a2..6dba0b4575 100644 --- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md +++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md @@ -42,13 +42,13 @@ Para iniciar con el {% data variables.product.prodname_code_scanning %}, consult {% endif %} -## About tools for {% data variables.product.prodname_code_scanning %} +## Acerca de las herramientas para el {% data variables.product.prodname_code_scanning %} -You can set up {% data variables.product.prodname_code_scanning %} to use the {% data variables.product.prodname_codeql %} product maintained by {% data variables.product.company_short%} or a third-party {% data variables.product.prodname_code_scanning %} tool. +Puedes configurar el {% data variables.product.prodname_code_scanning %} para utilizar el producto de {% data variables.product.prodname_codeql %} que mantiene {% data variables.product.company_short%} o una herramienta de {% data variables.product.prodname_code_scanning %} de un tercero. -### About {% data variables.product.prodname_codeql %} analysis +### Acerca del análisis de {% data variables.product.prodname_codeql %} -{% data reusables.code-scanning.about-codeql-analysis %} For more information about {% data variables.product.prodname_codeql %}, see "[About code scanning with CodeQL](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)." +{% data reusables.code-scanning.about-codeql-analysis %} Para obtener más información sobre {% data variables.product.prodname_codeql %}, consulta la sección "[Acerca del escaneo de código con CodeQL](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)". ### Acerca de las herramientas del {% data variables.product.prodname_code_scanning %} de terceros 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 036a9b722a..53c79cdeb3 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 @@ -68,29 +68,31 @@ Si utilizas el flujo de trabajo predeterminado, el {% data variables.product.pro Si escaneas al subir, entonces los resultados aparecen en la pestaña de **Seguridad** de tu repositorio. Para obtener más información, consulta la sección "[Administrar las alertas del escaneo de código para tu repositorio](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)". -{% note %} - -**Nota**: Si quieres que las alertas del {% data variables.product.prodname_code_scanning %} aparezcan como verificaciones de solicitudes de cambio, debes utilizar el evento `pull_request` que se describe más adelante. - -{% endnote %} +{% ifversion fpt or ghes > 3.2 or ghae-issue-5093 %} +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 %} ### Escanear las solicitudes de extracción -El {% data variables.product.prodname_codeql_workflow %} predeterminado utiliza el evento `pull_request` para activar un escaneo de código sobre las solilcitudes de cambios que se dirigen a la rama predeterminada. {% ifversion ghes %}El evento de `pull_request` no se activará si la solicitud de cambios se abrió desde una bifurcación privada.{% else %}Si una solicitud de cambios es de una bifurcación privada, el evento de `pull_request` solo se activará si seleccionaste la opción de "Ejecutar flujos de trabajo desde solicitudes de cambios de la bifurcación" en la configuración del repositorio. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#enabling-workflows-for-private-repository-forks)."{% endif %} +El {% data variables.product.prodname_codeql_workflow %} predeterminado utiliza el evento `pull_request` para activar un escaneo de código sobre las solilcitudes de cambios que se dirigen a la rama predeterminada. {% ifversion ghes %}El evento de `pull_request` no se activará si la solicitud de cambios se abrió desde una bifurcación privada.{% else %}Si una solicitud de cambios es de una bifurcación privada, el evento de `pull_request` solo se activará si seleccionaste la opción de "Ejecutar flujos de trabajo desde solicitudes de cambios de la bifurcación" en la configuración del repositorio. Para obtener más información, consulta la sección "[Administrar los ajustes de las {% data variables.product.prodname_actions %} en un repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#enabling-workflows-for-private-repository-forks)".{% endif %} Para obtener más información acerca del evento `pull_request`, consulta la sección "[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)". Si escaneas las solicitudes de cambios, entonces los resultados aparecerán como alertas en una verificación de solicitud de cambios. Para obtener màs informaciònPara obtener más información, consulta la sección "[Clasificar las alertas del escaneo de código en las solicitudes de cambios](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)". -{% ifversion fpt or ghes > 3.1 or ghae-next %} -### Defining the severities causing pull request check failure +{% ifversion fpt or ghes > 3.2 or ghae-issue-5093 %} + 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 %} -By default, only alerts with the severity level of `Error`{% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %} or security severity level of `Critical` or `High`{% endif %} will cause a pull request check failure, and a check will still succeed with alerts of lower severities. You can change the levels of alert severities{% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %} and of security severities{% endif %} that will cause a pull request check failure in your repository settings. For more information about severity levels, see "[Managing code scanning alerts for your repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#about-alerts-details)." +{% ifversion fpt or ghes > 3.1 or ghae-next %} +### Definir las gravedades que causan el fallo en la verificación de las solicitudes de cambio + +Predeterminadamente, solo las alertas con un nivel de gravedad de `Error`{% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %} o nivel de gravedad de seguridad de `Crítica` o `Alta`{% endif %} ocasionarán que falle la verificación de una solicitud de cambios y la verificación aún tendrá éxito con aquellas alertas de gravedades menores. Puedes cambiar los niveles de gravedad de las alertas{% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %} y de las gravedades de seguridad{% endif %} que ocasionarán el fallo de una verificación de solicitud de cambios en los ajustes de tu repositorio. Para obtener más información sobre los niveles de gravedad, consulta la sección "[Administrar las alertas del escaneo de código para tu repositorio](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#about-alerts-details)". {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -1. Under "Code scanning", to the right of "Check Failure", use the drop-down menu to select the level of severity you would like to cause a pull request check failure. +1. Debajo de "Escaneo de código", a la derecha de "Fallo de verificación", utiliza el menú desplegable para seleccionar el nivel de gravedad que quisieras que ocasionara un fallo de verificación en la solicitud de cambios. {% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %} ![Configuración de fallo de verificación](/assets/images/help/repository/code-scanning-check-failure-setting.png) {% else %} @@ -155,7 +157,7 @@ Este flujo de trabajo escanea: ## Especificar un sistema operativo -Si tu código requiere un sistema operativo específico para compilar, puedes configurarlo en tu flujo de trabajo. Edita el valor de `jobs.analyze.runs-on` para especificar el sistema operativo para la máquina que ejecuta tus acciones de {% data variables.product.prodname_code_scanning %}. {% ifversion ghes %}Especificas el sistema operativo utilizando una etiqueta adecuada como el segundo elemento en un arreglo de dos elementos, después de `self-hosted`.{% else %} +Si tu código requiere un sistema operativo específico para compilar, puedes configurarlo en tu flujo de trabajo. Edita el valor de `jobs.analyze.runs-on` para especificar el sistema operativo para la máquina que ejecuta tus acciones de {% data variables.product.prodname_code_scanning %}. {% ifversion ghes %}You specify the operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% else %} Si eliges utilizar une ejecutor auto-hospedado para el escaneo de código, puedes especificar un sistema operativo si utilizas una etiqueta adecuada como el segundo elemento en un arreglo de dos elementos, después de `self-hosted`.{% endif %} @@ -168,9 +170,9 @@ jobs: {% ifversion fpt %}Para obtener más información, consulta la sección "[Acerca de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Agregar ejecutores auto-hospedados](/actions/hosting-your-own-runners/adding-self-hosted-runners)."{% endif %} -{% data variables.product.prodname_code_scanning_capc %} es compatible con las últimas versiones de macOs, Ubuntu, y Windows. Los valores habituales para esta configuración son por lo tanto: `ubuntu-latest`, `windows-latest`, y `macos-latest`. Para obtener más información, consulta las secciones {% ifversion ghes %}"[Sintaxis de flujos de trabajo para GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" y "[Utilizar etiquetas con ejecutores auto-hospedados](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}"[Sintaxis de flujo de trabajo para GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}". +{% data variables.product.prodname_code_scanning_capc %} es compatible con las últimas versiones de macOs, Ubuntu, y Windows. Los valores habituales para esta configuración son por lo tanto: `ubuntu-latest`, `windows-latest`, y `macos-latest`. For more information, see {% ifversion ghes %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" and "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}." -{% ifversion ghes %}Debes asegurarte de qeu Git esté en la variable "PATH" en tus ejecutores auto-hospedados.{% else %}Si utilizas el ejecutor auto-hospedado, debes asegurarte de que git esté en la variable "PATH".{% endif %} +{% ifversion ghes %}You must ensure that Git is in the PATH variable on your self-hosted runners.{% else %}If you use a self-hosted runner, you must ensure that Git is in the PATH variable.{% endif %} {% ifversion fpt or ghes > 3.1 or ghae-next %} ## Especificar la ubicación de las bases de datos de {% data variables.product.prodname_codeql %} @@ -234,7 +236,6 @@ Como alternativa, puedes instalar las dependencias de Python manualmente en cual ```yaml jobs: CodeQL-Build: - runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae-next %} permissions: security-events: write @@ -266,7 +267,7 @@ jobs: ``` {% endif %} -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ## Configurar una cateogría para el análisis Utiliza `category` para distinguir entre análisis múltiples de la misma herramienta y confirmación, pero que se lleven a cabo en lenguajes o partes diferentes del código. La categoría que especificas en tu flujo de trabajo se incluirá en el archivo de resultados de SARIF. @@ -285,7 +286,7 @@ Este parámetro es particularmente útil si trabajas en monorepositorios y tiene ``` {% endraw %} -Si no especificas un parámetro de `category` en tu flujo de trabajo, {% data variables.product.product_name %} generará un nombre de categoría para ti con base en el nombre del archivo de flujo de trabajo que activó la acción, el nombre de la acción y cualquier variable de la matriz. Por ejemplo: +If you don't specify a `category` parameter in your workflow, {% data variables.product.product_name %} will generate a category name for you, based on the name of the workflow file triggering the action, the action name, and any matrix variables. Por ejemplo: - El flujo de trabajo `.github/workflows/codeql-analysis.yml` y la acción `analyze` producirán la categoría `.github/workflows/codeql.yml:analyze`. - Las variables Del flujo de trabajo de `.github/workflows/codeql-analysis.yml`, la acción `analyze`, y la matriz de `{language: javascript, os: linux}` producirán la categoría `.github/workflows/codeql-analysis.yml:analyze/language:javascript/os:linux`. @@ -300,19 +301,19 @@ La categoría que especificaste no sobrescribirá los detalles del objeto `runAu {% data reusables.code-scanning.run-additional-queries %} {% if codeql-packs %} -### Using {% data variables.product.prodname_codeql %} query packs +### Utilizar los paquetes de consultas de {% data variables.product.prodname_codeql %} {% data reusables.code-scanning.beta-codeql-packs-cli %} -To add one or more {% data variables.product.prodname_codeql %} query packs (beta), add a `with: packs:` entry within the `uses: github/codeql-action/init@v1` section of the workflow. Within `packs` you specify one or more packages to use and, optionally, which version to download. Where you don't specify a version, the latest version is downloaded. If you want to use packages that are not publicly available, you need to set the `GITHUB_TOKEN` environment variable to a secret that has access to the packages. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)" and "[Encrypted secrets](/actions/reference/encrypted-secrets)." +Para agregar uno o más paquetes de consulta de {% data variables.product.prodname_codeql %} (beta), agrega una entrada de `with: packs:` dentro de la sección de `uses: github/codeql-action/init@v1` del flujo de trabajo. Dentro de `packs` especificas uno o más paquetes a utilizar y, opcionalmente, la versión a descargar. Donde no especifiques una versión, se descargará la más reciente. Si quieres utilizar paquetes que no están disponibles al público, necesitarás configurar la variable de ambiente `GITHUB_TOKEN` como un secreto que tenga acceso a los paquetes. Para obtener más información, consulta las secciones "[Autenticación en un flujo de trabajo](/actions/reference/authentication-in-a-workflow)" y "[Secretos cifrados](/actions/reference/encrypted-secrets)". {% note %} -**Note:** For workflows that generate {% data variables.product.prodname_codeql %} databases for multiple languages, you must instead specify the {% data variables.product.prodname_codeql %} query packs in a configuration file. For more information, see "[Specifying {% data variables.product.prodname_codeql %} query packs](#specifying-codeql-query-packs)" below. +**Nota:** Para el caso de los flujos de trabajo que generan bases de dato de {% data variables.product.prodname_codeql %} para lenguajes múltiples, en su lugar, debes especificar los paquetes de consultas de {% data variables.product.prodname_codeql %} en un archivo de configuración. Para obtener más información, consulta la sección "[Especificar los paquetes de consultas de {% data variables.product.prodname_codeql %}](#specifying-codeql-query-packs)" a continuación. {% endnote %} -In the example below, `scope` is the organization or personal account that published the package. When the workflow runs, the three {% data variables.product.prodname_codeql %} query packs are downloaded from {% data variables.product.product_name %} and the default queries or query suite for each pack run. The latest version of `pack1` is downloaded as no version is specified. Version 1.2.3 of `pack2` is downloaded, as well as the latest version of `pack3` that is compatible with version 1.2.3. +En el siguiente ejemplo, `scope` es la organización o cuenta personal que publicó el paquete. Cuando se ejecuta el flujo de trabajo, los tres paquetes de consulta de {% data variables.product.prodname_codeql %} se descargan de {% data variables.product.product_name %} y se ejecutan las consultas predeterminadas o suite de consultas para cada paquete. La última versión de `pack1` se descarga, ya que no se especificó ninguna versión. Se descarga la versión 1.2.3 del `pack2`, así como la última versión del `pack3` que es compatible con la versión 1.2.3. {% raw %} ``` yaml @@ -323,9 +324,9 @@ In the example below, `scope` is the organization or personal account that publi ``` {% endraw %} -### Using queries in QL packs +### Utilizar las consultas en los paquetes de QL {% endif %} -Para agregar uno o más conjuntos de consultas, agrega una sección de `queries` a tu archivo de configuración. If the queries are in a private repository, use the `external-repository-token` parameter to specify a token that has access to checkout the private repository. +Para agregar uno o más conjuntos de consultas, agrega una sección de `queries` a tu archivo de configuración. Si las consultas están en un repositorio privado, utiliza el parámetro `external-repository-token` para especificar un token que tiene acceso para verificar el repositorio privado. {% raw %} ``` yaml @@ -342,12 +343,12 @@ También puedes ejecutar conjuntos de consultas adicionales si los especificas e {% data reusables.code-scanning.codeql-query-suites %} {% if codeql-packs %} -### Working with custom configuration files +### Trabajar con archivos de configuración personalizados {% endif %} -If you also use a configuration file for custom settings, any additional {% if codeql-packs %}packs or {% endif %}queries specified in your workflow are used instead of those specified in the configuration file. If you want to run the combined set of additional {% if codeql-packs %}packs or {% endif %}queries, prefix the value of {% if codeql-packs %}`packs` or {% endif %}`queries` in the workflow with the `+` symbol. Para encontrar ejemplos de archivos de configuración, consulta la sección "[Ejemplos de archivos de configuración](#example-configuration-files)". +Si también utilizas un archivo de configuración para los ajustes personalizados, cualquier {% if codeql-packs %}paquete o{% endif %} consulta adicional especificados en tu flujo de trabajo se utilizarán en vez de aquellos especificados en el archivo de configuración. Si quieres ejecutar el juego combinado de {% if codeql-packs %}paquetes o {% endif %} consultas adicionales, coloca un prefijo en el valor de {% if codeql-packs %}`packs` o {% endif %}`queries` en el flujo de trabajo con el símbolo `+`. Para encontrar ejemplos de archivos de configuración, consulta la sección "[Ejemplos de archivos de configuración](#example-configuration-files)". -In the following example, the `+` symbol ensures that the specified additional {% if codeql-packs %}packs and {% endif %}queries are used together with any specified in the referenced configuration file. +En el siguiente ejemplo, el símbolo `+` garantiza que los {% if codeql-packs %}paquetes y {% endif %}consultas adicionales especificados se utilicen juntos con cualquiera que se haya especificado en el archivo de configuración referenciado. ``` yaml - uses: github/codeql-action/init@v1 @@ -361,7 +362,7 @@ In the following example, the `+` symbol ensures that the specified additional { ## Utilizar una herramienta de escaneo de código de terceros -A custom configuration file is an alternative way to specify additional {% if codeql-packs %}packs and {% endif %}queries to run. You can also use the file to disable the default queries and to specify which directories to scan during analysis. +Un archivo de configuración personalizado es una forma alterna de especificar {% if codeql-packs %}paquetes y{% endif %} consultas adicionales a ejecutar. También puedes utilizar el archivo para inhabilitar las consultas predeterminadas y para especificar qué directorios escanear durante el análisis. En el archivo de flujo de trabajo, utiliza el parámetro `config-file` de la acción `init` para especificar la ruta al archivo de configuración que quieres utilizar. Este ejemplo carga el archivo de configuración _./.github/codeql/codeql-config.yml_. @@ -386,11 +387,11 @@ El archivo de configuración se ubica en un repositorio privado externo, utiliza Los ajustes en el archivo de configuración se escriben en formato YAML. {% if codeql-packs %} -### Specifying {% data variables.product.prodname_codeql %} query packs +### Especificar paquetes de consultas de {% data variables.product.prodname_codeql %} {% data reusables.code-scanning.beta-codeql-packs-cli %} -You specify {% data variables.product.prodname_codeql %} query packs in an array. Note that the format is different from the format used by the workflow file. +Especificas paquetes de consultas de {% data variables.product.prodname_codeql %} en un arreglo. Nota que el formato es deferente a aquél que utiliza el archivo de flujo de trabajo. {% raw %} ``` yaml @@ -404,7 +405,7 @@ packs: ``` {% endraw %} -If you have a workflow that generates more than one {% data variables.product.prodname_codeql %} database, you can specify any {% data variables.product.prodname_codeql %} query packs to run in a custom configuration file using a nested map of packs. +Si tienes un flujo de trabajo que genere más de una base de datos de {% data variables.product.prodname_codeql %}, puedes especificar cualquier paquete de consultas de {% data variables.product.prodname_codeql %} para que se ejecute en un archivo de configuración personalizado utilizando un mapa de paquetes anidado. {% raw %} ``` yaml diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md index 7dc4fb9215..b5ddbbbb38 100644 --- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md @@ -36,7 +36,7 @@ Predeterminadamente, el {% data variables.product.prodname_code_scanning %} anal ## Acerca de los detalles de las alertas -Cada alerta resalta un problema en el código y el nombre de la herramienta que lo identificó. You can see the line of code that triggered the alert, as well as properties of the alert, such as the severity{% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %}, security severity,{% endif %} and the nature of the problem. Las alertas también te dicen si el problema se introdujo por primera vez. Para las alertas que identificó el análisis de {% data variables.product.prodname_codeql %}, también verás información de cómo arreglar elproblema. +Cada alerta resalta un problema en el código y el nombre de la herramienta que lo identificó. Puedes ver la línea de código que activó la alerta, así como las propiedades de dicha alerta, tales como la gravedad{% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %}, gravedad de seguridad{% endif %} y la naturaleza del problema. Las alertas también te dicen si el problema se introdujo por primera vez. Para las alertas que identificó el análisis de {% data variables.product.prodname_codeql %}, también verás información de cómo arreglar elproblema. ![Ejemplo de alerta de {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-alert.png) @@ -44,20 +44,20 @@ Si configuras el {% data variables.product.prodname_code_scanning %} utilizando Cuando {% data variables.product.prodname_code_scanning %} reporta alertas de flujo de datos, {% data variables.product.prodname_dotcom %} te muestra como se mueven los datos a través del código. El {% data variables.product.prodname_code_scanning_capc %} te permite identificar las áreas de tu código que filtran información sensible y que podrían ser el punto de entrada para los ataques que hagan los usuarios malintencionados. -### About severity levels +### Acerca de los niveles de gravedad -Alert severity levels may be `Error`, `Warning`, or `Note`. +Los niveles de gravedad de las alertas pueden ser `Error`, `Warning`, o `Note`. -By default, any code scanning results with a severity of `error` will cause check failure. {% ifversion fpt or ghes > 3.1 or ghae-next %}You can specify the severity level at which pull requests that trigger code scanning alerts should fail. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %} +Predeterminadamente, cualquier resultado del escaneo de código con una severidad de `error` causará una falla de verificación. {% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %}Puedes especificar el nivel de gravedad en el cual deberían fallar las solicitudes de cambios que activan las alertas del escaneo de código. Para obtener más información, consulta la sección "[Definir las gravedades que ocasionan un fallo en la verificación de las solicitudes de cambios](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)".{% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %} -### About security severity levels +{% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %} +### Acerca de los niveles de gravedad -{% data variables.product.prodname_code_scanning_capc %} displays security severity levels for alerts that are generated by security queries. Security severity levels can be `Critical`, `High`, `Medium`, or `Low`. +El {% data variables.product.prodname_code_scanning_capc %} muestra los niveles de gravedad de seguridad para las alertas que generan las consultas de seguridad. Los niveles de seguridad pueden ser `Critical`, `High`, `Medium` o `Low`. -To calculate the security severity of an alert, we use Common Vulnerability Scoring System (CVSS) data. CVSS is an open framework for communicating the characteristics and severity of software vulnerabilities, and is commonly used by other security products to score alerts. For more information about how severity levels are calculated, see [the blog post](https://github.blog/changelog/2021-07-19-codeql-code-scanning-new-severity-levels-for-security-alerts/). +Para calcular la gravedad de seguridad de una alerta, utilizamos los datos del Sistema de Puntuación para Vulnerabilidades Comunes (CVSS). El CVSS es un marco de trabajo de código abierto para comunicar las características y gravedad de las vulnerabilidades de software y otros productos de seguridad lo utilizan habitualmente para puntuar las alertas. Para obtener más información sobre cómo se calculan los niveles de gravedad, consulta [la publicación del blog](https://github.blog/changelog/2021-07-19-codeql-code-scanning-new-severity-levels-for-security-alerts/). -By default, any code scanning results with a security severity of `Critical` or `High` will cause a check failure. You can specify which security severity level for code scanning results should cause a check failure. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %} +Predeterminadamente, cualquier resultado del escaneo de código con una gravedad de seguridad `Critical` o `High` ocasionarán un fallo de verificación. Puedes especificar qué nivel de gravedad de seguridad para de los resultados del escaneo de código deberían ocasionar una falla de verificación. Para obtener más información, consulta la sección "[Definir las gravedades que ocasionan un fallo en la verificación de las solicitudes de cambios](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)".{% endif %} ## Visualizar las alertas de un repositorio @@ -65,15 +65,15 @@ Cualquiera con permisos de escritura en un repositorio puede ver las anotaciones Necesitas permisos de escritura para ver un resumen de todas las alertas de un repositorio en la pestaña de **Seguridad**. -By default, the code scanning alerts page is filtered to show alerts for the default branch of the repository only. +Predeterminadamente, la página de alertas del escaneo de código se filtra para mostrar las alertas únicamente para la rama predeterminada del repositorio. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-code-scanning-alerts %} -{% ifversion fpt or ghes > 3.1 %} -1. Opcionalmente, utiliza {% ifversion fpt or ghes > 3.1 %} la caja de búsqueda por texto gratuita o{% endif %} los menús desplegables para filtrar las alertas. Por ejemplo, puedes filtrar por la herramienta que se utilizó para identificar las alertas. ![Filter by tool](/assets/images/help/repository/code-scanning-filter-by-tool.png){% endif %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} +1. Opcionalmente, utiliza la caja de búsqueda de texto libre o los menús desplegables para filtrar las alertas. Por ejemplo, puedes filtrar por la herramienta que se utilizó para identificar las alertas. ![Filter by tool](/assets/images/help/repository/code-scanning-filter-by-tool.png){% endif %} 1. Debajo de "{% data variables.product.prodname_code_scanning_capc %}", da clic en la alerta que quisieras explorar. -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ![Resumen de alertas](/assets/images/help/repository/code-scanning-click-alert.png) {% else %} ![Lista de alertas de {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) @@ -81,7 +81,7 @@ By default, the code scanning alerts page is filtered to show alerts for the def 1. Opcionalmente, si la alerta resalta un problema con el flujo de datos, da clic en **Mostrar rutas** para mostrar la ruta desde la fuente de datos hacia el consumidor de datos en donde se utiliza. ![El enlace de "Mostrar rutas" en una alerta](/assets/images/help/repository/code-scanning-show-paths.png) 1. Las alertas del análisis de {% data variables.product.prodname_codeql %} incluyen una descripción del problema. Da clic en **Mostrar más** para obtener orientación sobre cómo arreglar tu código. ![Detalles de una alerta](/assets/images/help/repository/code-scanning-alert-details.png) -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} {% note %} **Nota:** Para realizar el análisis del {% data variables.product.prodname_code_scanning %} con {% data variables.product.prodname_codeql %}, puedes ver la información sobre la última ejecución en un encabezado en la parte superior de la lisa de alertas del {% data variables.product.prodname_code_scanning %} para el repositorio. @@ -91,21 +91,34 @@ Por ejemplo, puedes ver cuándo se ejecutó el último escaneo, la cantidad de l {% endnote %} {% endif %} +## Filtrar las alertas del {% data variables.product.prodname_code_scanning %} -## Filtering {% data variables.product.prodname_code_scanning %} alerts +Puedes filtrar las alertas que se muestran en la vista de alertas del {% data variables.product.prodname_code_scanning %}. Esto es útil si hay muchas alertas, ya que puedes enfocarte en un tipo particular de estas. Hay algunos filtros predefinidos y rangos de palabras clave que puedes utilizar para refinar la lista de alertas que se muestran. -You can filter the alerts shown in the {% data variables.product.prodname_code_scanning %} alerts view. This is useful if there are many alerts as you can focus on a particular type of alert. There are some predefined filters and a range of keywords that you can use to refine the list of alerts displayed. - -- To use a predefined filter, click **Filters**, or a filter shown in the header of the list of alerts, and choose a filter from the drop-down list. - {% ifversion fpt or ghes > 3.0 %}![Predefined filters](/assets/images/help/repository/code-scanning-predefined-filters.png) +- Para utilizar un filtro predefinido, haz clic en **Filtros** o en un filtro que se muestre en el encabezado de la lista de alertas y elige un filtro de la lista desplegable. + {% ifversion fpt or ghes > 3.0 %}![Filtros predefinidos](/assets/images/help/repository/code-scanning-predefined-filters.png) {% else %}![Predefined filters](/assets/images/enterprise/3.0/code-scanning-predefined-filters.png){% endif %} -- To use a keyword, either type directly in the filters text box, or: - 1. Click in the filters text box to show a list of all available filter keywords. - 2. Click the keyword you want to use and then choose a value from the drop-down list. ![Keyword filters list](/assets/images/help/repository/code-scanning-filter-keywords.png) +- Para utilizar una palabra clave, teclea directamente en la caja de texto de filtros o: + 1. Haz clic en la caja de texto de filtros para que se muestre una lista de palabras clave de filtro disponibles. + 2. Haz clic en la palabra clave que quieras utilizar y luego elige un valor de la lista desplegable. ![Lista de filtros de palabra clave](/assets/images/help/repository/code-scanning-filter-keywords.png) -The benefit of using keyword filters is that only values with results are shown in the drop-down lists. This makes it easy to avoid setting filters that find no results. +El beneficio de utilizar filtros de palabra clave es que solo los valores con resultados se muestran en las listas desplegables. Esto hace más fácil el evitar configurar filtros que no encuentran resultados. + +Si ingresas filtros múltiples, la vista te mostrará las alertas que empatan con _todos_ ellos. Por ejemplo, `is:closed severity:high branch:main` solo mostrará las aletas de gravedad alta cerradas que estén presentes en la rama `main`. The exception is filters relating to refs (`ref`, `branch` and `pr`): `is:open branch:main branch:next` will show you open alerts from both the `main` branch and the `next` branch. + +### Restringir los resultados únicamente al código de la aplicación + +Puedes utilizar el filtro de "Solo alertas en el código de la aplicación" o la palabra clave y el valor `autofilter:true` para restringir a las alertas en el código de aplicación. La aplicación de código excluye lo siguiente. + +- El código que genera el proceso de compilación +- El código de prueba +- La librería o código de terceros +- Documentación + +El {% data variables.product.prodname_code_scanning_capc %} categoriza los archivos por sus rutas. En este momento, no puedes categorizar los archivos de código fuente manualmente. {% ifversion fpt or ghes > 3.1 %} + ## Buscar las alertas del {% data variables.product.prodname_code_scanning %} Puedes buscar la lista de alertas. Esto es útil si hay una gran cantidad de alertas en tu repositorio o si no sabes el nombre exacto de una alerta, por ejemplo. {% data variables.product.product_name %} realiza la búsqueda de texto gratuita a través de: @@ -145,11 +158,11 @@ Cualquiera con permisos de escritura en un repositorio puede arreglar una alerta Si tienes permisos de escritura para un repositorio, puedes ver las alertas arregladas si ves el resumen de las alertas y das clic en **Cerrado**. Para obtener más información, consulta la sección "[Visualizar las alertas de un repositorio](#viewing-the-alerts-for-a-repository)". La lista de "Cerrado" muestra las alertas arregladas y las que los usuarios han descartado. -Puedes utilizar{% ifversion fpt or ghes > 3.1 %} la búsqueda gratuita por texto o {% endif %} los filtros para mostrar un subconjunto de alertas y luego, a su vez, marcar todas las alertas coincidentes como cerradas. +Puedes utilizar{% ifversion fpt or ghes > 3.1 or ghae-next %} la búsqueda gratuita por texto o {% endif %} los filtros para mostrar un subconjunto de alertas y luego, a su vez, marcar todas las alertas coincidentes como cerradas. Las alertas pueden arreglarse en una rama pero no en alguna otra. Puedes utilizar el menú desplegable de "Rama", en el resumen de las alertas, para verificar si una alerta se arregló en una rama en particular. -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ![Filtrar alertas por rama](/assets/images/help/repository/code-scanning-branch-filter.png) {% else %} ![Filtrar alertas por rama](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png) @@ -185,9 +198,9 @@ Para descartar o borrar una alerta: ![Borrar alertas](/assets/images/help/repository/code-scanning-delete-alerts.png) - Opcionalmente, puedes utilizar {% ifversion fpt or ghes > 3.1 %} la búsqueda gratuita por texto o{% endif %} los filtros para mostrar un subconjunto de alertas y luego borrar todas las alertas coincidentes a la vez. Por ejemplo, si eliminaste una consulta desde el análisis de {% data variables.product.prodname_codeql %}, puedes utilizar el filtro de "Regla" para listar solo las alertas para esa consulta y luego seleccionar y borrar todas esas alertas. + Opcionalmente, puedes utilizar {% ifversion fpt or ghes > 3.1 or ghae-next %} la búsqueda gratuita por texto o{% endif %} los filtros para mostrar un subconjunto de alertas y luego borrar todas las alertas coincidentes a la vez. Por ejemplo, si eliminaste una consulta desde el análisis de {% data variables.product.prodname_codeql %}, puedes utilizar el filtro de "Regla" para listar solo las alertas para esa consulta y luego seleccionar y borrar todas esas alertas. -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ![Filtrar alertas por regla](/assets/images/help/repository/code-scanning-filter-by-rule.png) {% else %} ![Filtrar alertas por regla](/assets/images/enterprise/3.1/help/repository/code-scanning-filter-by-rule.png) @@ -195,12 +208,11 @@ Para descartar o borrar una alerta: 1. Si quieres descartar una alerta, es importante explorarla primero para que puedas elegir la razón correcta para descartarla. Da clic en la alerta que quisieras explorar. -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ![Abrir una alerta desde la lista de sumario](/assets/images/help/repository/code-scanning-click-alert.png) {% else %} ![Lista de alertas de {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) {% endif %} - 1. Revisa la alerta y da clic en **Descartar** y elije una razón para cerrarla. ![Elegir una razón para descartar una alerta](/assets/images/help/repository/code-scanning-alert-close-drop-down.png) {% data reusables.code-scanning.choose-alert-dismissal-reason %} 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 cc3490ddfb..1a5e14fd07 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 @@ -40,8 +40,8 @@ Tú decides cómo generar las alertas del {% data variables.product.prodname_cod {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} -3. A la derecha de "alertas del {% data variables.product.prodname_code_scanning_capc %}", haz clic en **Configurar el {% data variables.product.prodname_code_scanning %}**. {% ifversion fpt or ghes > 3.0 %}Si falta el {% data variables.product.prodname_code_scanning %}, necesitas pedir al propietario de la organización o adminsitrador del repositorio que habilite la {% data variables.product.prodname_GH_advanced_security %}. Para obtener más información, consulta las secciones "[Administrar la configuración de seguridad y análisis en tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" o "[Administrar la configuración de seguridad y análisis en tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)".{% endif %} ![Botón de "Configurar el {% data variables.product.prodname_code_scanning %}" a la derecha de "{% data variables.product.prodname_code_scanning_capc %}" en el resumen de seguridad](/assets/images/help/security/overview-set-up-code-scanning.png) -4. Debajod e "Iniciar con el {% data variables.product.prodname_code_scanning %}", da clic en **Configurar este flujo de trabajo** en el {% data variables.product.prodname_codeql_workflow %} o en el flujo de trabajo de terceros. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png){% ifversion fpt or ghes > 2.22 %}Los flujos de trabajo solo se muestran si son relevantes para los lenguajes de programación que se detectan en el repositorio. El {% data variables.product.prodname_codeql_workflow %} siempre se muestra, pero el botón de "Configurar este flujo de trabajo" solo se habilita si el análisis de {% data variables.product.prodname_codeql %} es compatible con los lenguajes presentes en el repositorio.{% endif %} +3. A la derecha de "alertas del {% data variables.product.prodname_code_scanning_capc %}", haz clic en **Configurar el {% data variables.product.prodname_code_scanning %}**. {% ifversion fpt or ghes > 3.0 or ghae-next %}Si falta el {% data variables.product.prodname_code_scanning %}, necesitas pedir al propietario de la organización o adminsitrador del repositorio que habilite la {% data variables.product.prodname_GH_advanced_security %}. Para obtener más información, consulta las secciones "[Administrar la configuración de seguridad y análisis en tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" o "[Administrar la configuración de seguridad y análisis en tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)".{% endif %} ![Botón de "Configurar el {% data variables.product.prodname_code_scanning %}" a la derecha de "{% data variables.product.prodname_code_scanning_capc %}" en el resumen de seguridad](/assets/images/help/security/overview-set-up-code-scanning.png) +4. Debajod e "Iniciar con el {% data variables.product.prodname_code_scanning %}", da clic en **Configurar este flujo de trabajo** en el {% data variables.product.prodname_codeql_workflow %} o en el flujo de trabajo de terceros. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png){% ifversion fpt or ghes > 2.22 or ghae-next %}Los flujos de trabajo solo se muestran si son relevantes para los lenguajes de programación que se detectan en el repositorio. El {% data variables.product.prodname_codeql_workflow %} siempre se muestra, pero el botón de "Configurar este flujo de trabajo" solo se habilita si el análisis de {% data variables.product.prodname_codeql %} es compatible con los lenguajes presentes en el repositorio.{% endif %} 5. Para personalizar la forma en que el {% data variables.product.prodname_code_scanning %} escanea tu còdigo, edita el flujo de trabajo. Generalmente, puedes confirmar el {% data variables.product.prodname_codeql_workflow %} sin hacerle ningùn cambio. Sin embargo, muchos de los flujos de trabajo de terceros requieren de configuraciones adicionales, asì que lee los comentarios en el flujo de trabajo antes de confirmar. @@ -53,9 +53,42 @@ Tú decides cómo generar las alertas del {% data variables.product.prodname_cod En el {% data variables.product.prodname_codeql_workflow %} predeterminado, el {% data variables.product.prodname_code_scanning %} se configura para analizar tu código cada vez que ya sea subas un cambio a la rama predeterminada o a cualquier rama protegida, o que levantes una solicitud de cambios contra la rama predeterminada. Como resultado, el {% data variables.product.prodname_code_scanning %} comenzarà ahora. +The `on:pull_request` and `on:push` triggers for code scanning are each useful for different purposes. For more information, see "[Scanning pull requests](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-pull-requests)" and "[Scanning on push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)." ## Configuración del {% data variables.product.prodname_code_scanning %} por lotes -Puedes configurar el {% data variables.product.prodname_code_scanning %} en muchos repositorios al mismo tiempo utilizando un script. If you'd like to use a script to raise pull requests that add a {% data variables.product.prodname_actions %} workflow to multiple repositories, see the [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) repository for an example using Powershell, or [`nickliffen/ghas-enablement`](https://github.com/NickLiffen/ghas-enablement) for teams who do not have Powershell and instead would like to use NodeJS. +Puedes configurar el {% data variables.product.prodname_code_scanning %} en muchos repositorios al mismo tiempo utilizando un script. Si te gustaría utilizar un script para levantar solicitudes de cambios que agreguen un flujo de trabajo de {% data variables.product.prodname_actions %} a varios repositorios, consulta el repositorio de [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) para encontrar un ejemplo utilizando Powershell o el de [`nickliffen/ghas-enablement`](https://github.com/NickLiffen/ghas-enablement) para los equipos que no tengan Powershell y quieran utilizar NodeJS en su lugar. + +## Visualizar la salida de registro del {% data variables.product.prodname_code_scanning %} + +Después de configurar el {% data variables.product.prodname_code_scanning %} para tu repositorio, puedes observar la salida de las acciones mientras se ejecutan. + +{% data reusables.repositories.actions-tab %} + + Veràs una lista que incluye una entrada para ejecutar el flujo de trabajo del {% data variables.product.prodname_code_scanning %}. El texto de la entrada es el título que le diste a tu mensaje de confirmación. + + ![Lista de acciones que muestran el flujo de trabajo del {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-actions-list.png) + +1. Da clic en la entrada para el flujo de trabajo de {% data variables.product.prodname_code_scanning %}. + +1. Da clic en el nombre del job situado a la izquierda. Por ejemplo, **Analizar (IDIOMA)**. + + ![Registro de salida del flujo de trabajo del {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-logging-analyze-action.png) + +1. Revisa la salida de registro de las acciones en este flujo de trabajo conforme se ejecutan. + +1. Una vez que todos los jobs se completen, puedes ver los detalles de cualquier alerta del {% data variables.product.prodname_code_scanning %} que se hayan identificado. Para obtener más información, consulta la sección "[Administrar las alertas de {% data variables.product.prodname_code_scanning %} para tu repositorio](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)". + +{% note %} + +**Nota:** Si levantaste una solicitud de cambios para agregar el flujo de trabajo del {% data variables.product.prodname_code_scanning %} a las alertas del repositorio, las alertas de esa solicitud de cambios no se mostraràn directamente en la pàgina del {% data variables.product.prodname_code_scanning_capc %} hasta que se fusione dicha solicitud. Si se encontrò alguna de las alertas, puedes verlas antes de que se fusione la solicitud de extracciòn dando clic en el enlace de **_n_ alertas encontradas** en el letrero de la pàgina del {% data variables.product.prodname_code_scanning_capc %}. + +{% ifversion fpt or ghes > 3.1 or ghae-next %} + ![Da clic en el enlace de "n alertas encontradas" link](/assets/images/help/repository/code-scanning-alerts-found-link.png) +{% else %} + ![Da clic en el enlace de "n alertas encontradas" link](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png) +{% endif %} + +{% endnote %} ## Entender las verificaciones de la solicitud de cambios @@ -65,13 +98,25 @@ Los nombres de las verificaciones del anàlisis del {% data variables.product.pr ![Verificaciones de solicitudes de cambios del {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-pr-checks.png) -Cuando se completan los jobs del {% data variables.product.prodname_code_scanning %}, {% data variables.product.prodname_dotcom %} averigua si la solicitud de cambios agregò alguna alerta y agrega la entrada "resultados del {% data variables.product.prodname_code_scanning_capc %} / NOMBRE DE LA HERRAMIENTA" a la lista de verificaciones. Despuès de que se lleve a cabo el {% data variables.product.prodname_code_scanning %} por lo menos una vez, puedes dar clic en **Detalles** para ver los resultados del anàlisis. Si utilizaste una solicitud de cambios para agregar el {% data variables.product.prodname_code_scanning %} al repositorio, veràs inicialmente un mensaje de "Missing analysis" cuando des clic en la parte de **Detalles** de la verificaciòn "resultados del {% data variables.product.prodname_code_scanning_capc %} / NOMBRE DE LA HERRAMIENTA". +Cuando se completan los jobs del {% data variables.product.prodname_code_scanning %}, {% data variables.product.prodname_dotcom %} averigua si la solicitud de cambios agregò alguna alerta y agrega la entrada "resultados del {% data variables.product.prodname_code_scanning_capc %} / NOMBRE DE LA HERRAMIENTA" a la lista de verificaciones. Despuès de que se lleve a cabo el {% data variables.product.prodname_code_scanning %} por lo menos una vez, puedes dar clic en **Detalles** para ver los resultados del anàlisis. 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 %}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. - ![Falta el análisis para el mensaje de confirmación](/assets/images/help/repository/code-scanning-missing-analysis.png) +{% ifversion fpt or ghes > 3.2 or ghae-issue-3891 %} + ![Analysis not found for commit message](/assets/images/help/repository/code-scanning-analysis-not-found.png) -### Razones para recibir un mensaje de "missing analysis" +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. -Despuès de que el {% data variables.product.prodname_code_scanning %} analiza el còdigo en una solicitud de cambios, necesita comparar el anàlisis de la rama de tema (la rama que utilizaste para crear la silicolicitud de cambios) con el anàlisis de la rama base (la rama en la cual quieres fusionar la solicitud de cambios). Esto permite al {% data variables.product.prodname_code_scanning %} calcular què alertas introdujo la solicitud de cambios recientemente, cuàles ya estaban presentes en la rama base y si es que cualquiera de las alertas existentes se arreglan con los cambios que lleva la solicitud. Inicialmente, si utilizas una solicitud de cambios para agregar el {% data variables.product.prodname_code_scanning %} a un repositorio, la rama base no se ha analizado, asì que no es posible calcular estos detalles. En este caso, cuando das clic en la verificaciòn de los resultados de la solicitud de cambios, veràs el mensaje "Missing analysis for base commit SHA-HASH". +For example, in the screenshot above, {% data variables.product.prodname_code_scanning %} found an analysis for the merge commit of the pull request, but no analysis for the head of the main branch. +{% else %} + ![Falta el análisis para el mensaje de confirmación](/assets/images/enterprise/3.2/repository/code-scanning-missing-analysis.png) +{% endif %} + +{% ifversion fpt or ghes > 3.2 or ghae-issue-3891 %} +### Reasons for the "Analysis not found" message +{% else %} +### Reasons for the "Missing analysis" message +{% endif %} + +Despuès de que el {% data variables.product.prodname_code_scanning %} analiza el còdigo en una solicitud de cambios, necesita comparar el anàlisis de la rama de tema (la rama que utilizaste para crear la silicolicitud de cambios) con el anàlisis de la rama base (la rama en la cual quieres fusionar la solicitud de cambios). Esto permite al {% data variables.product.prodname_code_scanning %} calcular què alertas introdujo la solicitud de cambios recientemente, cuàles ya estaban presentes en la rama base y si es que cualquiera de las alertas existentes se arreglan con los cambios que lleva la solicitud. Inicialmente, si utilizas una solicitud de cambios para agregar el {% data variables.product.prodname_code_scanning %} a un repositorio, la rama base no se ha analizado, asì que no es posible calcular estos detalles. 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 %}"Analysis not found"{% else %}"Missing analysis for base commit SHA-HASH"{% endif %} message. Existen otras situaciones en donde puede que no haya un anàlisis para la ùltima confirmaciòn hacia la rama base para una solicitud de cambios. Entre estas se incluyen cuando: @@ -79,7 +124,7 @@ Existen otras situaciones en donde puede que no haya un anàlisis para la ùltim Para verificar si se ha escaneado una rama, ve a la pàgina de {% data variables.product.prodname_code_scanning_capc %}, da clic en el menù desplegable de **Rama** y selecciona la rama relevante. -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ![Elige una rama del menú desplegable de Rama](/assets/images/help/repository/code-scanning-branch-dropdown.png) {% else %} ![Elige una rama del menú desplegable de Rama](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-dropdown.png) 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 29cc22547f..4627ededdb 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,42 +28,45 @@ topics: ## Acerca de los resultados del {% data variables.product.prodname_code_scanning %} en las solicitudes de cambios En los repositorios donde se configura el {% data variables.product.prodname_code_scanning %} como una verificación de solicitudes de cambios, éste verificará el código en dicha solicitud. Predeterminadamente, esto se limita a solicitudes de cambios que apuntan a la rama predeterminada, pero puedes cambiar esta configuración dentro de {% data variables.product.prodname_actions %} o en un sistema de IC/EC de terceros. Si el fusionar los cambios puede introducir alertas nuevas de {% data variables.product.prodname_code_scanning %} a la rama destino, éstas se reportarán como resultados de verificación en la solicitud de cambios. Las alertas también se muestran como anotaciones en la pestaña de **Archivos que cambiaron** de la solicitud de cambios. Si tienes permisos de escritura para el repositorio, puedes ver cualquier alerta del {% data variables.product.prodname_code_scanning %} existente en la pestaña de **Seguridad**. Para obtener más información sobre las alertas de los repositorios, consulta la sección "[Administrar las alertas del {% data variables.product.prodname_code_scanning %} para tu repositorio](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)". +{% ifversion fpt or ghes > 3.2 or ghae-issue-5093 %} +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 %} -If your pull request targets a protected branch that uses {% data variables.product.prodname_code_scanning %}, and the repository owner has configured required status checks, then the "{% data variables.product.prodname_code_scanning_capc %} results" check must pass before you can merge the pull request. Para obtener más información, consulta"[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)". +Si tu solicitud de cambios apunta a una rama protegida que utiliza el {% data variables.product.prodname_code_scanning %} y el propietario del repositorio configuró las verificaciones de estado requeridas, entonces la verificación de los "resultados del {% data variables.product.prodname_code_scanning_capc %}" debe pasar antes de que puedas fusionar la solicitud de cambios. Para obtener más información, consulta"[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)". ## Acerca del {% data variables.product.prodname_code_scanning %} como una verificación de solicitudes de cambio Hay muchas opciones para configurar el {% data variables.product.prodname_code_scanning %} como una verificación de solicitudes de cambio, así que la configuración de cada repositorio variará y algunas tendrán más de una verificación. -### {% data variables.product.prodname_code_scanning_capc %} results check +### Verificación de resultados de {% data variables.product.prodname_code_scanning_capc %} -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. +Para todas las configuraciones del {% data variables.product.prodname_code_scanning %}, la verificación que contiene los resultados del {% data variables.product.prodname_code_scanning %} es: **resultados de {% data variables.product.prodname_code_scanning_capc %}**. Los resultados para cada herramienta de análisis se muestran por separado. Cualquier alerta nueva que ocasionen los cambios en la solicitud de cambios se muestran como anotaciones. -{% ifversion fpt or ghes > 3.2 or ghae-issue-4902 %} 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. Para obtener más información, consulta la sección "[Administrar las alertas del escaneo de código para tu repositorio](/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-issue-4902 %} Para ver el conjunto de alertas completo de la rama analizada, haz clic en **Ver todas las alertas de rama**. Esto abre la vista completa de alertas en donde puedes filtrar todas las de la rama por tipo, gravedad, etiqueta, etc. Para obtener más información, consulta la sección "[Administrar las alertas del escaneo de código para tu repositorio](/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) +![verificación de resultados de {% data variables.product.prodname_code_scanning_capc %} en una solicitud de cambios](/assets/images/help/repository/code-scanning-results-check.png) {% endif %} -### {% data variables.product.prodname_code_scanning_capc %} results check failures +### Fallos de verificación de resultados de {% data variables.product.prodname_code_scanning_capc %} -If the {% data variables.product.prodname_code_scanning %} results check finds any problems with a severity of `error`{% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %}, `critical`, or `high`,{% endif %} the check fails and the error is reported in the check results. If all the results found by {% data variables.product.prodname_code_scanning %} have lower severities, the alerts are treated as warnings or notes and the check succeeds. +Si la verificación de los resultados del {% data variables.product.prodname_code_scanning %} encuentra cualquier problema con una gravedad de `error`{% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %}, `critical`, o `high`,{% endif %} la verificación fallará y el error se reportará en los resultados de verificación. Si todos los resultados que encontró el {% data variables.product.prodname_code_scanning %} tienen gravedades menores, las alertas se tratarán como advertencias o notas y la verificación tendrá éxito. ![Verificación fallida del {% data variables.product.prodname_code_scanning %} en una solicitud de cambios](/assets/images/help/repository/code-scanning-check-failure.png) -{% ifversion fpt or ghes > 3.1 or ghae-next %}You can override the default behavior in your repository settings, by specifying the level of severities {% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %}and security severities {% endif %}that will cause a pull request check failure. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)". +{% ifversion fpt or ghes > 3.1 or ghae-next %}Puedes anular el comportamiento predeterminado de los ajustes de tu repositorio si especificas el nivel de gravedad {% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %} y las gravedades de seguridad {% endif %} que ocasionarán el fallo de una verificación de solicitud de cambios. Para obtener más información, consulta la sección "[Definir las gravedades que ocasionan un fallo en la verificación de las solicitudes de cambios](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)". {% endif %} -### Other {% data variables.product.prodname_code_scanning %} checks +### Otras verificaciones del {% data variables.product.prodname_code_scanning %} -Depending on your configuration, you may see additional checks running on pull requests with {% data variables.product.prodname_code_scanning %} configured. These are usually workflows that analyze the code or that upload {% data variables.product.prodname_code_scanning %} results. These checks are useful for troubleshooting when there are problems with the analysis. +Dependiendo de tu configuración, podrías ver verificaciones adicionales ejecutándose en las solicitudes de cambios con el {% data variables.product.prodname_code_scanning %} configurado. A menudo, estos son flujos de trabajo que analizan el código o que cargan resultados del {% data variables.product.prodname_code_scanning %}. Estas verificaciones son útiles para solucionar problemas cuando el análisis los presenta. -For example, if the repository uses the {% data variables.product.prodname_codeql_workflow %} a **{% data variables.product.prodname_codeql %} / Analyze (LANGUAGE)** check is run for each language before the results check runs. La verificación del análisis podría fallar si existieran problemas de configuración o si la solicitud de cambios impide la compilación para un lenguaje que el análisis necesita compilar (por ejemplo, C/C++, C# o Java). +Por ejemplo, si el repositorio utiliza el {% data variables.product.prodname_codeql_workflow %}, se ejecutará una verificación de **{% data variables.product.prodname_codeql %} / Analyze (LANGUAGE)** para cada lenguaje antes de que se ejecute la verificación de resultados. La verificación del análisis podría fallar si existieran problemas de configuración o si la solicitud de cambios impide la compilación para un lenguaje que el análisis necesita compilar (por ejemplo, C/C++, C# o Java). Así como con otras verificaciones de solicitudes de cambios, puedes ver todos los detalles de la falla de la verificación en la pestaña de **Verificaciones**. Para obtener más información acerca de la configuración y la soución de problemas, consulta la sección "[Configurar el {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)" o "[Solucionar problemas del flujo de trabajo de {% data variables.product.prodname_codeql %}](/code-security/secure-coding/troubleshooting-the-codeql-workflow)". -## Viewing an alert on your pull request +## Visualizar una alerta en tu solicitud de cambios -You can see any {% data variables.product.prodname_code_scanning %} alerts introduced in a pull request by displaying the **Files changed** tab. Each alert is shown as an annotation on the lines of code that triggered the alert. The severity of the alert is displayed in the annotation. +Puedes ver cualquier alerta del {% data variables.product.prodname_code_scanning %} que se haya introducido en una solicitud de cambios si muestras la pestaña de **Archivos que cambiaron**. Cada alerta se muestra como una anotación en las líneas de código que la activaron. La gravedad de la alerta se muestra en la anotación. ![Anotación de alerta dentro de un diff de una solicitud de cambios](/assets/images/help/repository/code-scanning-pr-annotation.png) diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md index 124509491c..e3065414b1 100644 --- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md +++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md @@ -106,36 +106,36 @@ Para obtener más información, consulta el extracto de flujo de trabajo en la s Para obtener más información acerca de especificar los pasos de compilación, consulta la sección "[Configurar el flujo de trabajo de {% data variables.product.prodname_codeql %} para los lenguajes compilados](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)". {% ifversion fpt or ghes > 3.1 or ghae-next %} -## Lines of code scanned are lower than expected +## Las líneas de código escaneado son menores de lo esperado -For compiled languages like C/C++, C#, Go, and Java, {% data variables.product.prodname_codeql %} only scans files that are built during the analysis. Therefore the number of lines of code scanned will be lower than expected if some of the source code isn't compiled correctly. This can happen for several reasons: +Para los lenguajes compilados como C/C++, C#, Go y Java, {% data variables.product.prodname_codeql %} solo escanea los archivos que se compilen durante el análisis. Por lo tanto, la cantidad de líneas de código escaneado será menor de lo esperado si parte del código fuente no se compila correctamente. Esto puede suceder por varias razones: -1. The {% data variables.product.prodname_codeql %} `autobuild` feature uses heuristics to build the code in a repository. However, sometimes this approach results in an incomplete analysis of a repository. For example, when multiple `build.sh` commands exist in a single repository, the analysis may not be complete since the `autobuild` step will only execute one of the commands, and therefore some source files may not be compiled. -1. Some compilers do not work with {% data variables.product.prodname_codeql %} and can cause issues while analyzing the code. For example, Project Lombok uses non-public compiler APIs to modify compiler behavior. The assumptions used in these compiler modifications are not valid for {% data variables.product.prodname_codeql %}'s Java extractor, so the code cannot be analyzed. +1. La característica de `autobuild` del {% data variables.product.prodname_codeql %} utiliza la heurística para compilar el código de un repositorio. Sin embargo, algunas veces, este enfoque da como resultado un análisis incompleto del repositorio. Por ejemplo, cuando existen comandos múltiples de `build.sh` en un solo repositorio, el análisis podría no completarse, ya que el paso de `autobuild` solo se ejecutará en uno de los comandos y, por lo tanto, algunos archivos origen no se compilarán. +1. Algunos compiladores no funcionan con {% data variables.product.prodname_codeql %} y pueden causar problemas cuando analizan el código. Por ejemplo, Project Lombok utiliza unas API de compilación no públicas para modificar el comportamiento del compilador. Las asunciones que se utilizan en las modificaciones de este compilador no son válidas para el extractor de Java de {% data variables.product.prodname_codeql %}, así que el código no se puede analizar. -If your {% data variables.product.prodname_codeql %} analysis scans fewer lines of code than expected, there are several approaches you can try to make sure all the necessary source files are compiled. +Si tu análisis de {% data variables.product.prodname_codeql %} escanea menos líneas de código de lo esperado, hay varios enfoques que puedes intentar para asegurarte de que todos los archivos de código fuente necesarios se compilen. -### Replace the `autobuild` step +### Reemplaza el paso `autobuild` -Replace the `autobuild` step with the same build commands you would use in production. This makes sure that {% data variables.product.prodname_codeql %} knows exactly how to compile all of the source files you want to scan. Para obtener más información, consulta la sección "[Configurar el flujo de trabajo de {% data variables.product.prodname_codeql %} para los lenguajes compilados](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)". +Reemplaza el paso `autobuild` con los mismos comandos de compilación que utilizarías en producción. Esto garantiza que {% data variables.product.prodname_codeql %} sepa exactamente cómo compilar todos los archivos de código fuente que quieras escanear. Para obtener más información, consulta la sección "[Configurar el flujo de trabajo de {% data variables.product.prodname_codeql %} para los lenguajes compilados](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)". -### Inspect the copy of the source files in the {% data variables.product.prodname_codeql %} database -You may be able to understand why some source files haven't been analyzed by inspecting the copy of the source code included with the {% data variables.product.prodname_codeql %} database. To obtain the database from your Actions workflow, add an `upload-artifact` action after the analysis step in your code scanning workflow: +### Inspecciona la copia de los archivos de código fuente en la base de datos de {% data variables.product.prodname_codeql %} +Podrías entender por qué algunos archivos de código fuente no se ha analizado si inspeccionas la copia del código fuente que se incluye utilizando la base de datos de {% data variables.product.prodname_codeql %}. Para obtener la base de datos del flujo de trabajo de tus acciones, agrega una acción de `upload-artifact` después del paso de análisis en tu flujo de trabajo de escaneo de código: ``` - uses: actions/upload-artifact@v2 with: name: codeql-database path: ../codeql-database ``` -This uploads the database as an actions artifact that you can download to your local machine. For more information, see "[Storing workflow artifacts](/actions/guides/storing-workflow-data-as-artifacts)." +Esto carga la base de datos como un artefacto de acciones que puedes descargar en tu máquina local. Para obtener más información, consulta la sección "[Almacenar artefactos de los flujos de trabajo ](/actions/guides/storing-workflow-data-as-artifacts)". -The artifact will contain an archived copy of the source files scanned by {% data variables.product.prodname_codeql %} called _src.zip_. If you compare the source code files in the repository and the files in _src.zip_, you can see which types of file are missing. Once you know what types of file are not being analyzed, it is easier to understand how you may need to change the workflow for {% data variables.product.prodname_codeql %} analysis. +El artefacto contendrá una copia archivada de los archivos de código fuente que escaneó el {% data variables.product.prodname_codeql %} llamada _src.zip_. Si comparas los archivos de código fuente en el repositorio con los archivos en _src.zip_, puedes ver qué tipos de archivo faltan. Una vez que sepas qué tipos de archivo son los que no se analizan es más fácil entender cómo podrías cambiar el flujo de trabajo para el análisis de {% data variables.product.prodname_codeql %}. -## Extraction errors in the database +## Extracción de errores en la base de datos -The {% data variables.product.prodname_codeql %} team constantly works on critical extraction errors to make sure that all source files can be scanned. However, the {% data variables.product.prodname_codeql %} extractors do occasionally generate errors during database creation. {% data variables.product.prodname_codeql %} provides information about extraction errors and warnings generated during database creation in a log file. The extraction diagnostics information gives an indication of overall database health. Most extractor errors do not significantly impact the analysis. A small number of extractor errors is healthy and typically indicates a good state of analysis. +El equipo de {% data variables.product.prodname_codeql %} trabaja constantemente en los errores de extracción críticos para asegurarse de que todos los archivos de código fuente pueden escanearse. Sin embargo, los extractores de {% data variables.product.prodname_codeql %} sí generan errores durante la creación de bases de datos ocasionalmente. {% data variables.product.prodname_codeql %} proporciona información acerca de los errores de extracción y las advertencias que se generan durante la creación de bases de datos en un archivo de bitácora. La información de diagnóstico de extracción proporciona una indicación de la salud general de la base de datos. La mayoría de los errores del extractor no impactan el análisis significativamente. Una pequeña parte de los errores del extractor es saludable y, a menudo, indica un buen estado del análisis. -However, if you see extractor errors in the overwhelming majority of files that were compiled during database creation, you should look into the errors in more detail to try to understand why some source files weren't extracted properly. +Sin embargo, si ves errores del extractor en la vasta mayoría de archivos que se compilan durante la creación de la base de datos, deberías revisarlos a detalle para intentar entender por qué algunos archivos de código fuente no se extrajeron adecuadamente. {% else %} ## Algunas porciones de mi repositorio no se analizaron con `autobuild` diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md index 932cb2c655..6b842fb218 100644 --- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md +++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md @@ -22,7 +22,7 @@ shortTitle: Visualizar las bitácoras del escaneo de código Puedes utilizar diversas herramientas para configurar el {% data variables.product.prodname_code_scanning %} en tu repositorio. Para obtener más información, consulta la sección "[Configurar el {% data variables.product.prodname_code_scanning %} en un repositorio](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#options-for-setting-up-code-scanning)". -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} La bitácora y la información diagnóstica que tengas disponible dependerá del método que utilices para el {% data variables.product.prodname_code_scanning %} en tu repositorio. Puedes verificar el tipo de {% data variables.product.prodname_code_scanning %} que estás utilizando en la pestaña de **Seguridad** de tu repositorio si utilizas el menú desplegable de **Herramienta** en la lista de alertas. Para obtener más información, consulta la sección "[Administrar las alertas de {% data variables.product.prodname_code_scanning %} para tu repositorio](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)". ## Acerca del análisis y la información de diagnóstico @@ -35,7 +35,7 @@ Se muestra información de **Diagnóstico** en las bitácoras del flujo de traba Si estás utilizando el {% data variables.product.prodname_codeql_cli %} fuera de {% data variables.product.prodname_dotcom %}, verás la información de diagnóstico en la salida que se generó durante el análisis de la base de datos. Esta información también se incluye en el archivo de resultados SARIF que cargaste en {% data variables.product.prodname_dotcom %} con los resultados del {% data variables.product.prodname_code_scanning %}. -Para obtener más información sobre el {% data variables.product.prodname_codeql_cli %}, consulta la sección "[Ejecutar el {% data variables.product.prodname_codeql_cli %} en tu sistema de IC](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-cli-in-your-ci-system#viewing-log-and-diagnostic-information)". +Para obtener más información sobre el {% data variables.product.prodname_codeql_cli %}, consulta la sección "[Configurar el {% data variables.product.prodname_codeql_cli %} en tu sistema de IC](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system#viewing-log-and-diagnostic-information)". ### Acerca de las métricas de resumen @@ -72,7 +72,7 @@ Después de configurar el {% data variables.product.prodname_code_scanning %} pa **Nota:** Si levantaste una solicitud de cambios para agregar el flujo de trabajo del {% data variables.product.prodname_code_scanning %} a las alertas del repositorio, las alertas de esa solicitud de cambios no se mostraràn directamente en la pàgina del {% data variables.product.prodname_code_scanning_capc %} hasta que se fusione dicha solicitud. Si se encontrò alguna de las alertas, puedes verlas antes de que se fusione la solicitud de extracciòn dando clic en el enlace de **_n_ alertas encontradas** en el letrero de la pàgina del {% data variables.product.prodname_code_scanning_capc %}. -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae %} ![Da clic en el enlace de "n alertas encontradas" link](/assets/images/help/repository/code-scanning-alerts-found-link.png) {% else %} ![Da clic en el enlace de "n alertas encontradas" link](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png) diff --git a/translations/es-ES/content/code-security/code-scanning/index.md b/translations/es-ES/content/code-security/code-scanning/index.md index 41cf031bf2..5ff07ea9dd 100644 --- a/translations/es-ES/content/code-security/code-scanning/index.md +++ b/translations/es-ES/content/code-security/code-scanning/index.md @@ -1,5 +1,5 @@ --- -title: Finding security vulnerabilities and errors in your code with code scanning +title: Encontrar errores y vulnerabilidades de seguridad en tu código con el escaneo de código shortTitle: Escaneo de código intro: 'Mantén tu código seguro utilizando el {% data variables.product.prodname_code_scanning %} para identificar y arreglar vulnerabilidades de seguridad potenciales y otros errores en tu código.' product: '{% data reusables.gated-features.code-scanning %}' diff --git a/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md b/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md index 4c37660bfa..cd40ff050f 100644 --- a/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md +++ b/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md @@ -30,7 +30,7 @@ Si utilizas una herramienta de análisis estático de terceros que pueda produci ## Integraciones con webhooks -You can use {% data variables.product.prodname_code_scanning %} webhooks to build or set up integrations, such as [{% data variables.product.prodname_github_apps %}](/apps/building-github-apps/) or [{% data variables.product.prodname_oauth_apps %}](/apps/building-oauth-apps/), that subscribe to {% data variables.product.prodname_code_scanning %} events in your repository. Por ejemplo, puedes crear una integración que cree una propuesta en {% data variables.product.product_name %} o que te envíe una notificación de Slack cuando se agregue una alerta de {% data variables.product.prodname_code_scanning %} en tu repositorio. Para obtener más información, consulta las secciones "[Crear webhooks](/developers/webhooks-and-events/creating-webhooks)" y "[Eventos de webhook y cargas útiles](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)". +Puedes utilizar los webhooks del {% data variables.product.prodname_code_scanning %} para crear o configurar integraciones, tales como [{% data variables.product.prodname_github_apps %}](/apps/building-github-apps/) o [{% data variables.product.prodname_oauth_apps %}](/apps/building-oauth-apps/) que se suscriban a los eventos del {% data variables.product.prodname_code_scanning %} en tu repositorio. Por ejemplo, puedes crear una integración que cree una propuesta en {% data variables.product.product_name %} o que te envíe una notificación de Slack cuando se agregue una alerta de {% data variables.product.prodname_code_scanning %} en tu repositorio. Para obtener más información, consulta las secciones "[Crear webhooks](/developers/webhooks-and-events/creating-webhooks)" y "[Eventos de webhook y cargas útiles](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)". ## Leer más diff --git a/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md b/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md index 665559e812..f5400b0c44 100644 --- a/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md +++ b/translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md @@ -37,7 +37,7 @@ Si tu archivo SARIF no incluye `partialFingerprints`, este campo se calculará c {% ifversion fpt or ghes > 3.0 or ghae-next %} Si estás utilizando el {% data variables.product.prodname_codeql_cli %}, entonces puedes especificar la versión de SARIF a utilizar. Para obtener más información, consulta la sección "[Configurar el {% data variables.product.prodname_codeql_cli %} en tu sistema de IC](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system#analyzing-a-codeql-database)".{% endif %} -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} Puedes cargar varios archivos SARIF para la misma herramienta y confirmación y analizar cada uno utilizando el {% data variables.product.prodname_code_scanning %}. Puedes indicar una "categoría" para cada análisis si especificas una `runAutomationDetails.id` en cada archivo. Solo los archivos SARIF con la misma categoría podrán sobreescribirse entre ellos. Para obtener más información sobre esta propiedad, consulta el [objeto `runAutomationDetails`](#runautomationdetails-object) a continuación. {% endif %} @@ -91,19 +91,19 @@ Puedes cargar cualquier archivo de salida SARIF 2.1.0 válido, sin embargo, {% d ### Objeto `reportingDescriptor` -| Nombre | Descripción | -| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `id` | **Requerido.** Un identificador único para la regla. El `id` se referencia de otras partes del archivo SARIF y {% data variables.product.prodname_code_scanning %} puede utilizarlo para mostrar las URL en {% data variables.product.prodname_dotcom %}. | -| `name (nombre)` | **Opcional.** El nombre de la regla. {% data variables.product.prodname_code_scanning_capc %} muestra el nombre para permitir que se filtren los resultados por regla en {% data variables.product.prodname_dotcom %}. | -| `shortDescription.text` | **Requerido** Una descripción breve de la acción. {% data variables.product.prodname_code_scanning_capc %} muestra la descripción corta en {% data variables.product.prodname_dotcom %} junto a los resultados asociados. | -| `fullDescription.text` | **Requerido** Una descripción de la regla. {% data variables.product.prodname_code_scanning_capc %} muestra la descripción completa en {% data variables.product.prodname_dotcom %} junto a los resultados asociados. La cantidad máxma de caracteres se limita a 1000. | -| `defaultConfiguration.level` | **Opcional.** Nivel de severidad predeterminado de la regla. {% data variables.product.prodname_code_scanning_capc %} utiliza niveles de severidad para ayudarte a entender qué tan crítico es el resultado de una regla. El atributo `level` en el objeto `result` anular este valor. Para obtener más información, consulta el [objeto `result`](#result-object). Predeterminado: `warning`. | -| `help.text` | **Requerido.** Documentación para la regla utilizando el formato de texto. {% data variables.product.prodname_code_scanning_capc %} Muestra esta documentación de ayuda junto a los resultados asociados. | -| `help.markdown` | **Recomendado.** Documentación para la regla utilizando el formato Markdown. {% data variables.product.prodname_code_scanning_capc %} Muestra esta documentación de ayuda junto a los resultados asociados. Cuando `help.markdown` está disponible, se muestra en vez de `help.text`. | -| `properties.tags[]` | **Opcional.** Un arreglo de secuencias. {% data variables.product.prodname_code_scanning_capc %} utiliza `tags` para permitirte filtrar los resultados en {% data variables.product.prodname_dotcom %}. Por ejemplo, puedes filtrar todos los resultados que tengan la etiqueta `security`. | -| `properties.precision` | **Recomendado.** una secuencia que indica qué tan frecuentemente son verdaderos los resultados que indica esta regla. Por ejemplo, si una regla tiene una tasa alta de falsos positivos, la precisión debería ser `low`. {% data variables.product.prodname_code_scanning_capc %} ordena los resultados de acuerdo con su precisión en {% data variables.product.prodname_dotcom %} para que aquellos con el `level` y la `precision` más altos se muestren primero. Puede ser uno de entre: `very-high`, `high`, `medium`, o `low`. |{% ifversion fpt or ghes > 3.1 or ghae-next %} -| `properties.problem.severity` | **Recommended.** A string that indicates the level of severity of any alerts generated by a non-security query. This, with the `properties.precision` property, determines whether the results are displayed by default on {% data variables.product.prodname_dotcom %} so that the results with the highest `problem.severity`, and highest `precision` are shown first. Can be one of: `error`, `warning`, or `recommendation`. | -| `properties.security-severity` | **Recommended.** A score that indicates the level of severity, between 0.0 and 10.0, for security queries (`@tags` includes `security`). This, with the `properties.precision` property, determines whether the results are displayed by default on {% data variables.product.prodname_dotcom %} so that the results with the highest `security-severity`, and highest `precision` are shown first. {% data variables.product.prodname_code_scanning_capc %} translates numerical scores as follows: over 9.0 is `critical`, 7.0 to 8.9 is `high`, 4.0 to 6.9 is `medium` and 3.9 or less is `low`. {% endif %} +| Nombre | Descripción | +| ---------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `id` | **Requerido.** Un identificador único para la regla. El `id` se referencia de otras partes del archivo SARIF y {% data variables.product.prodname_code_scanning %} puede utilizarlo para mostrar las URL en {% data variables.product.prodname_dotcom %}. | +| `name (nombre)` | **Opcional.** El nombre de la regla. {% data variables.product.prodname_code_scanning_capc %} muestra el nombre para permitir que se filtren los resultados por regla en {% data variables.product.prodname_dotcom %}. | +| `shortDescription.text` | **Requerido** Una descripción breve de la acción. {% data variables.product.prodname_code_scanning_capc %} muestra la descripción corta en {% data variables.product.prodname_dotcom %} junto a los resultados asociados. | +| `fullDescription.text` | **Requerido** Una descripción de la regla. {% data variables.product.prodname_code_scanning_capc %} muestra la descripción completa en {% data variables.product.prodname_dotcom %} junto a los resultados asociados. La cantidad máxma de caracteres se limita a 1000. | +| `defaultConfiguration.level` | **Opcional.** Nivel de severidad predeterminado de la regla. {% data variables.product.prodname_code_scanning_capc %} utiliza niveles de severidad para ayudarte a entender qué tan crítico es el resultado de una regla. El atributo `level` en el objeto `result` anular este valor. Para obtener más información, consulta el [objeto `result`](#result-object). Predeterminado: `warning`. | +| `help.text` | **Requerido.** Documentación para la regla utilizando el formato de texto. {% data variables.product.prodname_code_scanning_capc %} Muestra esta documentación de ayuda junto a los resultados asociados. | +| `help.markdown` | **Recomendado.** Documentación para la regla utilizando el formato Markdown. {% data variables.product.prodname_code_scanning_capc %} Muestra esta documentación de ayuda junto a los resultados asociados. Cuando `help.markdown` está disponible, se muestra en vez de `help.text`. | +| `properties.tags[]` | **Opcional.** Un arreglo de secuencias. {% data variables.product.prodname_code_scanning_capc %} utiliza `tags` para permitirte filtrar los resultados en {% data variables.product.prodname_dotcom %}. Por ejemplo, puedes filtrar todos los resultados que tengan la etiqueta `security`. | +| `properties.precision` | **Recomendado.** una secuencia que indica qué tan frecuentemente son verdaderos los resultados que indica esta regla. Por ejemplo, si una regla tiene una tasa alta de falsos positivos, la precisión debería ser `low`. {% data variables.product.prodname_code_scanning_capc %} ordena los resultados de acuerdo con su precisión en {% data variables.product.prodname_dotcom %} para que aquellos con el `level` y la `precision` más altos se muestren primero. Puede ser uno de entre: `very-high`, `high`, `medium`, o `low`. |{% ifversion fpt or ghes > 3.1 or ghae-next %} +| `properties.problem.severity` | **Recomendado.** Una secuencia que indica el nivel de gravedad de cualquier alerta generada por una consulta que no sea de seguridad. Esto, con la propiedad de `properties.precision`, determina si los resultados se muestran predeterminadamente en {% data variables.product.prodname_dotcom %} para que los resultados con la `problem.severity` y la `precision` más altas se muestren primero. Puede ser uno de entre: `error`, `warning`, o `recommendation`. | +| `properties.security-severity` | **Recomendado.** Una puntuación que indica el nivel de gravedad, entre 0.0 y 10.0, para las consultas de seguridad (`@tags` incluye a `security`). Esto, con la propiedad de `properties.precision`, determina si los resultados se muestran predeterminadamente en {% data variables.product.prodname_dotcom %} para que los resultados con la `security-severity` y la `precision` más altas se muestren primero. {% data variables.product.prodname_code_scanning_capc %} traduce las puntuaciones numéricas de la siguiente forma: más de 9.0 es `critical`, de 7.0 a 8.9 es `high`, de 4.0 a 6.9 es `medium` y 3.9 o menos es `low`. {% endif %} ### `result` object @@ -141,7 +141,7 @@ Una ubicación dentro de un artefacto de programación, tal como un archivo en e | `region.endLine` | **Requerido.** El número de línea de el último caracter en la región. | | `region.endColumn` | **Requerido.** El número de columna del caracter que sigue al final de la región. | -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ### Objeto `runAutomationDetails` El objeto `runAutomationDetails` contiene información que especifica la identidad de una ejecución. @@ -245,7 +245,7 @@ Este archivo de salida SARIF tiene valores de ejemplo para mostrar las propiedad Este archivo de salida SARIF tiene valores ejemplo para mostrar todas las propiedades de SARIF compatibles con {% data variables.product.prodname_code_scanning %}. -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ```json { "$schema": "https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json", diff --git a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md index ad6d7546e9..ec94c10494 100644 --- a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md +++ b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md @@ -28,7 +28,7 @@ redirect_from: ## Acerca del {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %} en tu sistema de IC -{% data reusables.code-scanning.about-code-scanning %} For information, see "[About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)." +{% data reusables.code-scanning.about-code-scanning %} Para obtener más información, consulta la sección "[Acerca del {% data variables.product.prodname_code_scanning %} con {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)". Puedes ejecutar el {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %} dentro de {% data variables.product.product_name %} utilizando {% data variables.product.prodname_actions %}. Como alternativa, si utilizas un sistema de integración o despliegue/entrega contínua (IC/ID) de terceros, puedes ejecutar un análisis de {% data variables.product.prodname_codeql %} en tu sistema existente y cargar los resultados a {% data variables.product.product_location %}. @@ -91,8 +91,8 @@ Para obtener más información, consulta la sección "[Ejecutar el {% data varia {% endif %} - -{% ifversion ghes = 3.0 or ghae %} + +{% ifversion ghes = 3.0 %} {% data reusables.code-scanning.upload-sarif-ghas %} Puedes agregar el {% data variables.product.prodname_codeql_runner %} a tu sistema de terceros y luego llamar a la herramienta para analizar código y cargar los resultados de SARIF a {% data variables.product.product_name %}. Las alertas del {% data variables.product.prodname_code_scanning %} resultantes se muestran junto con cualquier alerta que se genere dentro de {% data variables.product.product_name %}. diff --git a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md index 2cc708a95a..2bc16f53ad 100644 --- a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md +++ b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md @@ -30,7 +30,7 @@ Una vez que hayas puesto el {% data variables.product.prodname_codeql_cli %} dis Utilizarás tres comandos diferentes para generar los resultados y cargarlos a {% data variables.product.product_name %}: -{% ifversion fpt or ghes > 3.1 or ghae-next %} +{% ifversion fpt or ghes > 3.1 or ghae %} 1. `database create` para crear una base de datos de {% data variables.product.prodname_codeql %} para representar la estructura jerárquica de cada lenguage de programación compatible en el repositorio. 2. `database analyze` para ejecutar consultas para analizar cada base de datos de {% data variables.product.prodname_codeql %} y resumir los resultados en un archivo SARIF. @@ -50,11 +50,11 @@ Puedes mostrar la ayuda en la línea de comandos para apoyarte sobre cualquier c 1. Verifica que el código que quieres analizar: - Para una rama, verifica el encabezado de la rama que quieras analizar. - - Para una solicitud de cambios, verifica ya sea la confirmación de encabezado de la solicitud o una confirmación de fusión generada por {% data variables.product.product_name %} de dicha solicitud. + - Para una solicitud de cambios, verifica ya sea la confirmación de encabezado de la solicitud o una confirmación de fusión generada por {% data variables.product.prodname_dotcom %} de dicha solicitud. 2. Configura el ambiente de la base de código, asegurándote de que todas las dependencias estén disponibles. Para obtener más información, consulta las secciones [Crear bases de datos para lenguajes no compilados](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#creating-databases-for-non-compiled-languages) y [Crear bases de datos para lenguajes compilados](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#creating-databases-for-compiled-languages) en la documentación del {% data variables.product.prodname_codeql_cli %}. 3. Encuentra el comando de compilación, en caso de que exista, para la base de código. Habitualmente, esta es una variable en un archivo de configración en el sistema de IC. 4. Ejecuta `codeql database create` desde la raíz de verificación de tu repositorio y recompila la base de código. - {% ifversion fpt or ghes > 3.1 or ghae-next %} + {% ifversion fpt or ghes > 3.1 or ghae %} ```shell # Single supported language - create one CodeQL databsae codeql database create <database> --command<build> --language=<language-identifier> @@ -119,7 +119,7 @@ Puedes mostrar la ayuda en la línea de comandos para apoyarte sobre cualquier c - {% ifversion fpt or ghes > 3.1 or ghae-next %} cuando se utiliza con     `--db-cluster`, la opción acepta una lista separada por comas o puede especificarse más de una vez.{% endif %} + {% ifversion fpt or ghes > 3.1 or ghae %} cuando se utiliza con     `--db-cluster`, la opción acepta una lista separada por comas o puede especificarse más de una vez.{% endif %} @@ -144,7 +144,7 @@ Puedes mostrar la ayuda en la línea de comandos para apoyarte sobre cualquier c - {% ifversion fpt or ghes > 3.1 or ghae-next %} + {% ifversion fpt or ghes > 3.1 or ghae %} @@ -208,7 +208,7 @@ Puedes mostrar la ayuda en la línea de comandos para apoyarte sobre cualquier c Para obtener más información, consulta la sección [Crear bases de datos de {% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/) en la documentación del {% data variables.product.prodname_codeql_cli %}. -### {% ifversion fpt or ghes > 3.1 or ghae-next %}Ejemplo con un solo lenguaje{% else %}Ejemplo básico{% endif %} +### {% ifversion fpt or ghes > 3.1 or ghae %}Ejemplo con un solo lenguaje{% else %}Ejemplo básico{% endif %} Este ejemplo crea una base de datos de {% data variables.product.prodname_codeql %} para el repositorio que se verificón en `/checkouts/example-repo`. Utiliza el extractor de JavaScript para crear una representación jerárquica del código de JavaScript y TypeScript en el repositorio. La base de datos resultante se almacena en `/codeql-dbs/example-repo`. @@ -226,7 +226,7 @@ $ codeql database create /codeql-dbs/example-repo --language=javascript \ > Successfully created database at /codeql-dbs/example-repo. ``` -{% ifversion fpt or ghes > 3.1 or ghae-next %} +{% ifversion fpt or ghes > 3.1 or ghae %} ### Ejemplo de lenguaje múltiple Este ejemplo crea dos bases de datos de {% data variables.product.prodname_codeql %} para el repositorio que se verificó en `/checkouts/example-repo-multi`. Esta utiliza: @@ -261,19 +261,19 @@ $ ## Analizar una base de datos de {% data variables.product.prodname_codeql %} -1. Create a {% data variables.product.prodname_codeql %} database (see above).{% if codeql-packs %} -2. Optional, run `codeql pack download` to download any {% data variables.product.prodname_codeql %} packs (beta) that you want to run during analysis. For more information, see "[Downloading and using {% data variables.product.prodname_codeql %} query packs](#downloading-and-using-codeql-query-packs)" below. +1. Crea una base de datos de {% data variables.product.prodname_codeql %} (mira el ejemplo anterior).{% if codeql-packs %} +2. Opcionalmente, ejecuta `codeql pack download` para descargar cualquier paquete de {% data variables.product.prodname_codeql %} (beta) que quieras ejecutar durante el análisis. Para obtener más información, consulta la sección "[Descargar y usar los paquetes de consultas de {% data variables.product.prodname_codeql %}](#downloading-and-using-codeql-query-packs)" a continuación. ```shell codeql pack download <packs> ``` {% endif %} -3. Run `codeql database analyze` on the database and specify which {% if codeql-packs %}packs and/or {% endif %}queries to use. +3. Ejecuta `codeql database analyze` en la base de datos y especifica qué {% if codeql-packs %}paquetes o {% endif %}consultas utilizar. ```shell codeql database analyze <database> --format=<format> \ --output=<output> {% if codeql-packs %}<packs,queries>{% else %} <queries>{% endif %} ``` -{% ifversion fpt or ghes > 3.1 or ghae-next %} +{% ifversion fpt or ghes > 3.1 or ghae %} {% note %} **Nota:** Si analizaste más de una base de datos de {% data variables.product.prodname_codeql %} para una confirmación simple, debes especificar una categoría SARIF para cada conjunto de resultados que se generaron con este comando. Cuando cargas los resultados en {% data variables.product.product_name %}, el {% data variables.product.prodname_code_scanning %} utiliza esta categoría para almacenar los resultados para cada lenguaje por separado. Si te olvidas de hacerlo, cada carga sobreescribe los resultados anteriores. @@ -317,15 +317,14 @@ codeql database analyze <database> --format=<format> \ - <queries> + <packs,queries> - {% octicon "check-circle-fill" aria-label="Required" %} - Especifica las consultas a ejecutar. Para ejecturar las consultas estándar que se utilizan para el {% data variables.product.prodname_code_scanning %}, utiliza: <language>-code-scanning.qls donde <language> es el código corto para el lenguaje de la base de datos. Para ver el resto de las suites de consultas que se incluyen en el paquete del {% data variables.product.prodname_codeql_cli %}, revisa /<extraction-root>/codeql/qlpacks/codeql-<language>/codeql-suites. Para obtener más información sobre cómo crear tu suite de consultas, dirígete a la sección "Crear suites de consultas de CodeQL en la documentación para el {% data variables.product.prodname_codeql_cli %}. + Specify {% data variables.product.prodname_codeql %} packs or queries to run. To run the standard queries used for {% data variables.product.prodname_code_scanning %}, omit this parameter. Para ver el resto de las suites de consultas que se incluyen en el paquete del {% data variables.product.prodname_codeql_cli %}, revisa /<extraction-root>/codeql/qlpacks/codeql-<language>/codeql-suites. Para obtener más información sobre cómo crear tu suite de consultas, dirígete a la sección "Crear suites de consultas de CodeQL en la documentación para el {% data variables.product.prodname_codeql_cli %}. @@ -353,7 +352,7 @@ codeql database analyze <database> --format=<format> \ - Especifica dónde guardar el archivo de resultados SARIF.{% ifversion fpt or ghes > 3.1 or ghae-next %} + Especifica dónde guardar el archivo de resultados SARIF.{% ifversion fpt or ghes > 3.1 or ghae %} @@ -367,7 +366,7 @@ codeql database analyze <database> --format=<format> \ - Opcional para el análisis de bases de datos simples. Requerido para definir el idioma cuando analizas bases de datos múltiples para una confirmación simple en un repositorio. Especifica una categoría para incluir en el archivo de resultados SARIF para su análisis. A category is used to distinguish multiple analyses for the same tool and commit, but performed on different languages or different parts of the code.|{% endif %}{% if codeql-packs %} + Opcional para el análisis de bases de datos simples. Requerido para definir el idioma cuando analizas bases de datos múltiples para una confirmación simple en un repositorio. Especifica una categoría para incluir en el archivo de resultados SARIF para su análisis. Se utiliza una categoría para distinguir entre análisis múltiples para la misma herramienta y confirmación, pero se realiza en lenguajes diferentes o en partes diferentes del código.{% endif %}{% if codeql-packs %} @@ -380,7 +379,7 @@ codeql database analyze <database> --format=<format> \ - Opcional. Use if you have downloaded CodeQL query packs and want to run the default queries or query suites specified in the packs. For more information, see "Downloading and using {% data variables.product.prodname_codeql %} packs."{% endif %} + Opcional. Utilízalo si descargaste paquetes de consultas de CodeQL y quieres ejecutar las consultas predeterminadas o suites de consultas especificadas en estos. Para obtener más información, consulta la sección "Descargar y utilizar paquetes de {% data variables.product.prodname_codeql %}".{% endif %} @@ -406,7 +405,7 @@ codeql database analyze <database> --format=<format> \ - Opcional. Utilízalo para obtener información más detallada sobre el proceso de análisis{% ifversion fpt or ghes > 3.1 or ghae-next %} y datos de diagnóstico del proceso de creación de bases de datos{% endif %}. + Opcional. Utilízalo para obtener información más detallada sobre el proceso de análisis{% ifversion fpt or ghes > 3.1 or ghae %} y datos de diagnóstico del proceso de creación de bases de datos{% endif %}. @@ -415,11 +414,11 @@ Para obtener más información, consulta la sección [Analizar las bases de dato ### Ejemplo básico -Este ejemplo analiza una base de datos de {% data variables.product.prodname_codeql %} que se almacena en `/codeql-dbs/example-repo` y guarda los resultados como un archivo SARIF: `/temp/example-repo-js.sarif`. {% ifversion fpt or ghes > 3.1 or ghae-next %}Este utiliza `--sarif-category` para incluir información adicional en el archivo SARIF que identifica los resultados como JavaScript. Esto es escencial cuando tienes más de una base de datos de {% data variables.product.prodname_codeql %} que analizar para una sola confirmación en un repositorio.{% endif %} +Este ejemplo analiza una base de datos de {% data variables.product.prodname_codeql %} que se almacena en `/codeql-dbs/example-repo` y guarda los resultados como un archivo SARIF: `/temp/example-repo-js.sarif`. {% ifversion fpt or ghes > 3.1 or ghae %}Este utiliza `--sarif-category` para incluir información adicional en el archivo SARIF que identifica los resultados como JavaScript. Esto es escencial cuando tienes más de una base de datos de {% data variables.product.prodname_codeql %} que analizar para una sola confirmación en un repositorio.{% endif %} ``` $ codeql database analyze /codeql-dbs/example-repo \ - javascript-code-scanning.qls {% ifversion fpt or ghes > 3.1 or ghae-next %}--sarif-category=javascript{% endif %} + javascript-code-scanning.qls {% ifversion fpt or ghes > 3.1 or ghae %}--sarif-category=javascript{% endif %} --format={% ifversion fpt or ghae %}sarif-latest{% else %}sarifv2.1.0{% endif %} --output=/temp/example-repo-js.sarif > Running queries. @@ -444,7 +443,7 @@ Cuando decidas cuál será el método más seguro y confiable para tu servidor d ```shell echo "$UPLOAD_TOKEN" | codeql github upload-results --repository=<repository-name> \ --ref=<ref> --commit=<commit> --sarif=<file> \ - {% ifversion ghes > 3.0 or ghae-next %}--github-url=<URL> {% endif %}--github-auth-stdin + {% ifversion ghes > 3.0 or ghae %}--github-url=<URL> {% endif %}--github-auth-stdin ``` @@ -486,7 +485,7 @@ Cuando decidas cuál será el método más seguro y confiable para tu servidor d @@ -514,7 +513,7 @@ Cuando decidas cuál será el método más seguro y confiable para tu servidor d @@ -555,20 +554,20 @@ Este ejemplo carga los resultados del archivo SARIF `temp/example-repo-js.sarif` ``` $ echo $UPLOAD_TOKEN | codeql github upload-results --repository=my-org/example-repo \ --ref=refs/heads/main --commit=deb275d2d5fe9a522a0b7bd8b6b6a1c939552718 \ - --sarif=/temp/example-repo-js.sarif {% ifversion ghes > 3.0 or ghae-next %}--github-url={% data variables.command_line.git_url_example %} \ + --sarif=/temp/example-repo-js.sarif {% ifversion ghes > 3.0 or ghae %}--github-url={% data variables.command_line.git_url_example %} \ {% endif %}--github-auth-stdin ``` No hay salida para este comando a menos de que la carga no sea exitosa. El símbolo de sistema regresa cuando la carga se completa e inicia el procesamiento de datos. En bases de código más pequeñas, debes poder explorar las alertas del {% data variables.product.prodname_code_scanning %} en {% data variables.product.product_name %} poco tiempo después. Puedes ver las alertas directamente en la solicitud de cambios en la pestaña de **Seguridad** de las ramas, dependiendo del código que verificaste. Para obtener más información, consulta las secciones "[Clasificar las alertas del {% data variables.product.prodname_code_scanning %} en las solicitudes de cambio](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)" y "[Administrar las alertas del {% data variables.product.prodname_code_scanning %} de tu repositorio](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)". {% if codeql-packs %} -## Downloading and using {% data variables.product.prodname_codeql %} query packs +## Descargar y utilizar paquetes de consultas de {% data variables.product.prodname_codeql %} {% data reusables.code-scanning.beta-codeql-packs-cli %} -The {% data variables.product.prodname_codeql_cli %} bundle includes queries that are maintained by {% data variables.product.company_short %} experts, security researchers, and community contributors. If you want to run queries developed by other organizations, {% data variables.product.prodname_codeql %} query packs provide an efficient and reliable way to download and run queries. For more information, see "[About code scanning with CodeQL](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql#about-codeql-queries)." +El paquete de {% data variables.product.prodname_codeql_cli %} incluye consultas que mantienen los expertos de {% data variables.product.company_short %}, los investigadores de seguridad y los contribuyentes de la comunidad. Si quieres ejecutar consultas que desarrollan otras organizaciones, los paquetes de consultas de {% data variables.product.prodname_codeql %} proporcionan una forma confiable y eficiente de descargarlas y ejecutarlas. Para obtener más información, consulta la sección "[Acerca del escaneo de código con 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 %} by running `codeql pack download` and specifying the packages you want to download. If a package is not publicly available, you will need to use a {% data variables.product.prodname_github_app %} or personal access token to authenticate. For more information and an example, see "[Uploading results to {% data variables.product.product_name %}](#uploading-results-to-github)" above. +Antes de que puedas utilizar un paquete de {% data variables.product.prodname_codeql %} para analizar una base de datos, debes descargar cualquier paquete que requieras desde el {% data variables.product.prodname_container_registry %} de {% data variables.product.company_short %} ejecutando `codeql pack download` y especificando los paquetes que quieras descargar. Si un paquete no está disponible públicamente, necesitarás utilizar un token de acceso personal o de {% data variables.product.prodname_github_app %} para autenticarte. Para obtener más información y un ejemplo, consulta la sección anterior de "[Cargar los resultados a {% data variables.product.product_name %}](#uploading-results-to-github)". ```shell codeql pack download <scope/name@version>,... @@ -599,7 +598,7 @@ codeql pack download <scope/name@version>,... @@ -612,14 +611,14 @@ codeql pack download <scope/name@version>,...
    - Especifica el nombre de la ref que verificaste y analizaste para que los resultados puedan empatarse con el código correcto. Para una rama, utiliza: refs/heads/BRANCH-NAME, para la confirmación de encabezado de una solicitud de cambios utiliza refs/pulls/NUMBER/head o, para la confirmación de fusión que genera {% data variables.product.product_name %} para una solicitud de cambios, utiliza refs/pulls/NUMBER/merge. + Especifica el nombre de la ref que verificaste y analizaste para que los resultados puedan empatarse con el código correcto. Para una rama, utiliza: refs/heads/BRANCH-NAME, para la confirmación de encabezado de una solicitud de cambios utiliza refs/pulls/NUMBER/head o, para la confirmación de fusión que genera {% data variables.product.prodname_dotcom %} para una solicitud de cambios, utiliza refs/pulls/NUMBER/merge.
    - Especifica el archivo SARIF a cargar.{% ifversion ghes > 3.0 or ghae-next %} + Especifica el archivo SARIF a cargar.{% ifversion ghes > 3.0 or ghae %}
    - Specify the scope and name of one or more CodeQL query packs to download using a comma-separated list. Optionally, include the version to download and unzip. By default the latest version of this pack is downloaded. + Especifica el alcance y nombre de uno o más paquetes de consultas de CodeQL a descargar utilizando una lista separada por comas. Opcionalmente, incluye la versión para descargar y descomprimir. Se descarga la versión más reciente de este paquete predeterminadamente.
    - Opcional. Pass the {% data variables.product.prodname_github_app %} or personal access token created for authentication with {% data variables.product.company_short %}'s REST API to the CLI via standard input. Esto no se necesita si el comando tiene acceso a una variable de ambiente de GITHUB_TOKEN que se configuró con este token. + Opcional. Pasa la {% data variables.product.prodname_github_app %} o el token de acceso personal que se creó para la autenticación con la API de REST de {% data variables.product.company_short %} al CLI a través de una entrada estándar. Esto no se necesita si el comando tiene acceso a una variable de ambiente de GITHUB_TOKEN que se configuró con este token.
    ### Ejemplo básico -This example runs two commands to download the latest version of the `octo-org/security-queries` pack and then analyze the database `/codeql-dbs/example-repo`. +Este ejemplo ejecuta dos comandos para descargar la última versión del paquete `octo-org/security-queries` y luego analiza la base de datos `/codeql-dbs/example-repo`. ``` $ echo $OCTO-ORG_ACCESS_TOKEN | codeql pack download octo-org/security-queries @@ -641,6 +640,7 @@ $ codeql database analyze /codeql-dbs/example-repo octo-org/security-queries \ {% endif %} {% ifversion fpt or ghes > 3.1 or ghae-next %} + ## Configuración de IC de ejemplo para el análisis de {% data variables.product.prodname_codeql %} Este es un ejemplo de la serie de comandos que puedes utilizar para analizar una base de código con dos lenguajes compatibles y luego cargar los resultados a {% data variables.product.product_name %}. @@ -695,7 +695,7 @@ Si quieres cargar más de un conjunto de resultados a la API del {% data variabl {% ifversion fpt or ghes > 3.2 or ghae-next %} -If your CI system cannot trigger the {% data variables.product.prodname_codeql_cli %} autobuild and you cannot specify a command line for the build, you can use indirect build tracing to create {% data variables.product.prodname_codeql %} databases for compiled languages. For more information, see [Using indirect build tracing](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#using-indirect-build-tracing) in the documentation for the {% data variables.product.prodname_codeql_cli %}. +Si tu sistema de IC no puede activar la autocompilación del {% data variables.product.prodname_codeql_cli %} y no puedes especificar una línea de comandos para dicha compilación, puedes utilizar el rastreo de compilación indirecta para crear bases de datos de {% data variables.product.prodname_codeql %} para los lenguajes compilados. Para obtener más información, consulta la sección [Utilizar el rastreo indirecto de compilaciones](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#using-indirect-build-tracing) en la documentación del {% data variables.product.prodname_codeql_cli %}. {% endif %} diff --git a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md index ea5b413c99..b1668ae185 100644 --- a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md +++ b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md @@ -190,7 +190,7 @@ Analiza el código en las bases de datos de {% data variables.product.prodname_c | `--no-upload` | | Ninguno. Impide que el {% data variables.product.prodname_codeql_runner %} cargue los resultados a {% data variables.product.product_name %}. | | `--output-dir` | | Directorio en donde se almacenan los archivos SARIF de salida. El predeterminado está en el directorio de archivos temporales. | | `--ram` | | Cantidad de memoria a utilizar cuando ejecutes consultas. El valor predeterminado es utilizar toda la memoria disponible. | -| `--no-add-snippets` | | Ninguno. Excluye los fragmentos de código de la salida de SARIF. |{% ifversion fpt or ghes > 3.1 %} +| `--no-add-snippets` | | Ninguno. Excluye los fragmentos de código de la salida de SARIF. |{% ifversion fpt or ghes > 3.1 or ghae %} | `--category` | | Categoría para incluir el archivo de resultados SARIF para este análisis. La categoría puede utilizarse pra distinguir análisis múltiples de la misma herramienta y confirmación, pero que se llevan a cabo en lenguajes diferentes o en partes diferentes del código. Este valor aparecerá en la propiedad `.automationDetails.id` de SARIF v2.1.0. {% endif %} | `--threads` | | Cantidad de hilos a utilizar cuando se ejecutan las consultas. El valor predeterminado es utilizar todos los núcleos disponibles. | diff --git a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md index 5fd86e08e7..0c35cad142 100644 --- a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md +++ b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md @@ -28,7 +28,7 @@ redirect_from: ## Acerca de utilizar el {% data variables.product.prodname_codeql_cli %} para el {% data variables.product.prodname_code_scanning %} -Puedes utilizar el {% data variables.product.prodname_codeql_cli %} para ejecutar el {% data variables.product.prodname_code_scanning %} en el código que estás procesando en un sistema de integración continua (IC) de terceros. {% data reusables.code-scanning.about-code-scanning %} For information, see "[About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)." +Puedes utilizar el {% data variables.product.prodname_codeql_cli %} para ejecutar el {% data variables.product.prodname_code_scanning %} en el código que estás procesando en un sistema de integración continua (IC) de terceros. {% data reusables.code-scanning.about-code-scanning %} Para obtener más información, consulta la sección "[Acerca del {% data variables.product.prodname_code_scanning %} con {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)". {% data reusables.code-scanning.what-is-codeql-cli %} diff --git a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md index c9fe5a4493..86c0438277 100644 --- a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md +++ b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md @@ -1,7 +1,7 @@ --- -title: Migrating from the CodeQL runner to CodeQL CLI -shortTitle: Migrating from the CodeQL runner -intro: 'You can use the {% data variables.product.prodname_codeql_cli %} to complete the same tasks as with the {% data variables.product.prodname_codeql_runner %}.' +title: Migrarse del ejecutor de CodeQL al CLI de CodeQL +shortTitle: Migrarse desde el ejecutor de CodeQL +intro: 'Puedes utilizar el {% data variables.product.prodname_codeql_cli %} para completar las mismas tareas que hacías con el {% data variables.product.prodname_codeql_runner %}.' product: '{% data reusables.gated-features.code-scanning %}' versions: fpt: '*' @@ -13,45 +13,45 @@ topics: - CodeQL --- -# Migrating from the {% data variables.product.prodname_codeql_runner %} to the {% data variables.product.prodname_codeql_cli %} +# Migrarse del {% data variables.product.prodname_codeql_runner %} al {% data variables.product.prodname_codeql_cli %} -The {% data variables.product.prodname_codeql_runner %} is being deprecated. You can use the {% data variables.product.prodname_codeql_cli %} version 2.6.2 and greater instead. This document describes how to migrate common workflows from the {% data variables.product.prodname_codeql_runner %} to the {% data variables.product.prodname_codeql_cli %}. +El {% data variables.product.prodname_codeql_runner %} se va a obsoletizar. Puedes utilizar la versión 2.6.2 del {% data variables.product.prodname_codeql_cli %} y superiores. Este documento describe cómo migrar flujos de trabajo comunes desde el {% data variables.product.prodname_codeql_runner %} hacia el {% data variables.product.prodname_codeql_cli %}. ## Instalación -Download the **{% data variables.product.prodname_codeql %} bundle** from the [`github/codeql-action` repository](https://github.com/github/codeql-action/releases). This bundle contains the {% data variables.product.prodname_codeql_cli %} and the standard {% data variables.product.prodname_codeql %} queries and libraries. +Descarga el **paquete de {% data variables.product.prodname_codeql %}** del [repositorio `github/codeql-action`](https://github.com/github/codeql-action/releases). Este paquete contiene al {% data variables.product.prodname_codeql_cli %} y las consultas estándar y librerías de {% data variables.product.prodname_codeql %}. -For more information on setting up the {% data variables.product.prodname_codeql_cli %}, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)." +Para obtener más información sobre cómo configurar el {% data variables.product.prodname_codeql_cli %}, consulta la sección "[Instalar el {% data variables.product.prodname_codeql_cli %} en tu sistema de IC](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)". -## Overview of workflow changes +## Resumen de los cambios en los flujos de trabajo -A typical workflow that uses the {% data variables.product.prodname_codeql_runner %} to analyze a codebase has the following steps. -- `codeql-runner- init` to start creating {% data variables.product.prodname_codeql %} databases and read the configuration. -- For compiled languages: set environment variables produced by the `init` step. -- For compiled languages: run autobuild or manual build steps. -- `codeql-runner- analyze` to finish creating {% data variables.product.prodname_codeql %} databases, run queries to analyze each {% data variables.product.prodname_codeql %} database, summarize the results in a SARIF file, and upload the results to {% data variables.product.prodname_dotcom %}. +Un flujo de trabajo habitual utiliza el {% data variables.product.prodname_codeql_runner %} para analizar una base de código tiene los siguientes pasos. +- `codeql-runner- init` para comenzar a crear las bases de datos de {% data variables.product.prodname_codeql %} y leer la configuración. +- Para los lenguajes compilados: configura las variables de ambiente que produce el paso `init`. +- Para los lenguajes compilados: ejecuta la autocompilación o los pasos de compilación manual. +- `codeql-runner- analyze` para terminar de crear las bases de datos de {% data variables.product.prodname_codeql %}, ejecutar consultas para analizar cada base de datos de {% data variables.product.prodname_codeql %}, resumir los resultados en un archivo SARIF, y cargar los resultados a {% data variables.product.prodname_dotcom %}. -A typical workflow that uses the {% data variables.product.prodname_codeql_cli %} to analyze a codebase has the following steps. -- `codeql database create` to create {% data variables.product.prodname_codeql %} databases. - - For compiled languages: Optionally provide a build command. -- `codeql database analyze` to run queries to analyze each {% data variables.product.prodname_codeql %} database and summarize the results in a SARIF file. This command must be run once for each language or database. -- `codeql github upload-results` to upload the resulting SARIF files to {% data variables.product.prodname_dotcom %}, to be displayed as code scanning alerts. This command must be run once for each language or SARIF file. +Un flujo de trabajo habitual utiliza el {% data variables.product.prodname_codeql_cli %} para analizar una base de código tiene los siguientes pasos. +- `codeql database create` para crear bases de datos de {% data variables.product.prodname_codeql %}. + - Para los lenguajes compilados: Proporciona un comando de compilación opcionalmente. +- `codeql database analyze` para ejecutar consultas para analizar cada base de datos de {% data variables.product.prodname_codeql %} y resumir los resultados en un archivo SARIF. Este comando debe ejecutarse una vez para cada lenguaje o base de datos. +- `codeql github upload-results` para cargar los archivos SARIF resultantes a {% data variables.product.prodname_dotcom %}, para que se muestre como alertas del escaneo de código. Este comando debe ejecutarse una vez para cada archivo SARIF o lenguaje. Para obtener más información, consulta la sección "[Configurar el {% data variables.product.prodname_codeql_cli %} en tu sistema de IC](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system)". -## Examples of common uses for the {% data variables.product.prodname_codeql_cli %} +## Ejemplos de usos comunes para el {% data variables.product.prodname_codeql_cli %} -### About the examples +### Acerca de los ejemplos -These examples assume that the source code has been checked out to the current working directory. If you use a different directory, change the `--source-root` argument and the build steps accordingly. +Estos ejemplos asumen que el código fuente se verificó en el directorio de trabajo actual. Si utilizas un directorio diferente, cambia el argumento `--source-root` y compila los pasos como sea correcto. -These examples also assume that the {% data variables.product.prodname_codeql_cli %} is placed on the current PATH. +Estos ejemplos también asumen que el {% data variables.product.prodname_codeql_cli %} se coloca en la RUTA correcta. -In these examples, a {% data variables.product.prodname_dotcom %} token with suitable scopes is stored in the `$TOKEN` environment variable and passed to the example commands via stdin, or is stored in the `$GITHUB_TOKEN` environment variable. +En estos ejemplos, un token de{% data variables.product.prodname_dotcom %} con alcance suficiente se almacena en la variable de ambiente `$TOKEN` y se pasa por los comandos de ejemplo a través de stdin o se almacena en la variable de ambiente `$GITHUB_TOKEN`. -The ref name and commit SHA being checked out and analyzed in these examples are known during the workflow. For a branch, use `refs/heads/BRANCH-NAME` as the ref. For the head commit of a pull request, use `refs/pulls/NUMBER/head`. For a {% data variables.product.prodname_dotcom %}-generated merge commit of a pull request, use `refs/pulls/NUMBER/merge`. The examples below all use `refs/heads/main`. If you use a different branch name, you must modify the sample code. +El nombre de ref y el SHA de confirmación que se verifican y analizan en estos ejemplos se conocen durante el flujo de trabajo. En el caso de las ramas, utiliza `refs/heads/BRANCH-NAME` como el ref. En el caso de la confirmación de encabezado de una solicitud de cambios, utiliza `refs/pulls/NUMBER/head`. En el caso de una confirmación de fusión generada por {% data variables.product.prodname_dotcom %} para una solicitud de cambios, utiliza `refs/pulls/NUMBER/merge`. Todos los siguientes ejemplos utilizan `refs/heads/main`. Si utilizas un nombre de rama diferente, debes modificar el código de muestra. -### Single non-compiled language (JavaScript) +### Lenguaje sencillo no compilado (JavaScript) Runner: ```bash @@ -78,9 +78,9 @@ echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \ --sarif=/temp/example-repo-js.sarif --github-auth-stdin ``` -### Single non-compiled language (JavaScript) using a different query suite (security-and-quality) +### Lenguaje sencillo no compilado (JavaScript) utilizando una suite de consultas (security-and-quality) -A similar approach can be taken for compiled languages, or multiple languages. +Se puede tomar un enfoque similar para los lenguajes compilados o los lenguajes múltiples. Runner: ```bash @@ -108,9 +108,9 @@ echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \ --sarif=/temp/example-repo-js.sarif --github-auth-stdin ``` -### Single non-compiled language (JavaScript) using a custom configuration file +### Lenguaje sencillo no compilado (JavaScript) utilizando un archivo de configuración personalizado -A similar approach can be taken for compiled languages, or multiple languages. +Se puede tomar un enfoque similar para los lenguajes compilados o los lenguajes múltiples. Runner: ```bash @@ -139,7 +139,7 @@ echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \ --sarif=/temp/example-repo-js.sarif --github-auth-stdin ``` -### Single compiled language using autobuild (Java) +### Lenguaje sencillo no compilado utilizando compilación automática (Java) Runner: ```bash @@ -173,7 +173,7 @@ echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \ --sarif=/temp/example-repo-java.sarif --github-auth-stdin ``` -### Single compiled language using a custom build command (Java) +### Lenguaje sencillo no copilado utilizando un comando de compilación personalizado (Java) Runner: ```bash @@ -206,9 +206,9 @@ echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \ --sarif=/temp/example-repo-java.sarif --github-auth-stdin ``` -### Single compiled language using indirect build tracing (C# on Windows within Azure DevOps) +### Lenguaje sencillo no compilado utilizando rastreo de compilación indirecto (C# sobre Windows dentro de Azure DevOps) -Indirect build tracing for a compiled language enables {% data variables.product.prodname_codeql %} to detect all build steps between the `init` and `analyze` steps, when the code cannot be built using the autobuilder or an explicit build command line. This is useful when using preconfigured build steps from your CI system, such as the `VSBuild` and `MSBuild` tasks in Azure DevOps. +El rastreo de compilación indirecta para los lenguajes compilados habilita al {% data variables.product.prodname_codeql %} para que detecte los pasos de compilación entre los pasos de `init` y `analyze`, cuando el código no puede compilarse utilizando la compilación automática o una línea de comandos compilada explícita. Esto es útil cuando se utilizan pasos de compilación preconfigurados desde tu sistema de IC, tales como las tareas de `VSBuild` y `MSBuild` en Azure DevOps. Runner: ```yaml @@ -328,9 +328,9 @@ CLI: ``` -### Multiple languages using autobuild (C++, Python) +### Lenguajes múltiples utilizando compilación automática (C++, Python) -This example is not strictly possible with the {% data variables.product.prodname_codeql_runner %}. Only one language (the compiled language with the most files) will be analyzed. +Este ejemplo no es estrictamente posible dentro del {% data variables.product.prodname_codeql_runner %}. Solo se analizará un lenguaje (el lenguaje compilado que tenga la mayoría de los archivos). Runner: ```bash @@ -370,7 +370,7 @@ for language in cpp python; do done ``` -### Multiple languages using a custom build command (C++, Python) +### Lenguajes múltiples utilizando un comando de compilación personalizado (C++, Python) Runner: ```bash diff --git a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md index b6e858cb80..5f40720bb5 100644 --- a/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md +++ b/translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md @@ -34,7 +34,7 @@ topics: ## Acerca de {% data variables.product.prodname_codeql_runner %} -El {% data variables.product.prodname_codeql_runner %} es una herramienta que puedes utilizar para ejecutar el {% data variables.product.prodname_code_scanning %} en el código que estás procesando en un sistema de integración contínua (IC) de terceros. {% data reusables.code-scanning.about-code-scanning %} For information, see "[About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)." +El {% data variables.product.prodname_codeql_runner %} es una herramienta que puedes utilizar para ejecutar el {% data variables.product.prodname_code_scanning %} en el código que estás procesando en un sistema de integración contínua (IC) de terceros. {% data reusables.code-scanning.about-code-scanning %} Para obtener más información, consulta la sección "[Acerca del {% data variables.product.prodname_code_scanning %} con {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)". {% ifversion fpt or ghes > 3.0 or ghae-next %} En muchos casos es más fácil configurar el {% data variables.product.prodname_code_scanning %} de {% data variables.product.prodname_codeql %} utilizando el {% data variables.product.prodname_codeql_cli %} directamente en tu sistema de IC. 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 7c83a2d042..60dcf9bd73 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 @@ -105,7 +105,7 @@ Para obtener más información, consulta la sección "[Administrar la configurac {% endif %} ## Pasos siguientes -{% ifversion fpt or ghes > 3.1 or ghae-next %}You can view, filter, and sort security alerts for repositories owned by your organization in the security overview. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)."{% endif %} +{% ifversion fpt or ghes > 3.1 or ghae-next %}Puedes ver, filtrar y clasificar las alertas de seguridad para los repositorios que pertenecen a tu organización en el resumen de seguridad. Para obtener más información, consulta la sección "[Acerca del resumen de seguridad](/code-security/security-overview/about-the-security-overview)".{% endif %} Puedes ver y administrar las alertas de las características de seguridad para abordar dependencias y vulnerabilidades en tu código. Para obtener más información, consulta las secciones {% ifversion fpt or ghes > 2.22 %} "[Visualizar y actualizar las dependencias vulnerables en tu repositorio](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository),"{% endif %} {% ifversion fpt %}"[Administrar las solicitudes de cambio para las actualizaciones de dependencias](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Administrar el {% data variables.product.prodname_code_scanning %} para tu repositorio](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," y "[Administrar las alertas desde el {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)". 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 5f5d37e62a..87fd7c4908 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 @@ -49,7 +49,7 @@ Para obtener más información, consulta "[Aumentar la seguridad para tu reposit {% ifversion fpt or ghes > 2.22 %} ## Administrar la gráfica de dependencias -Once you have [enabled the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph#enabling-the-dependency-graph), it is automatically generated for {% ifversion fpt or ghes > 2.22 %} all public repositories, and you can choose to enable it for private repositories.{% else %} all repositories.{% endif %} +Una vez que hayas [habilitado la gráfica de dependencias](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph#enabling-the-dependency-graph), esta se generará automáticamente para {% ifversion fpt or ghes > 2.22 %} todos los repositorios públicos y podrás elegir habilitarla para los repositorios privados.{% else %} todos los repositorios.{% endif %} 1. Desde la página principal de tu repositorio, haz clic en **{% octicon "gear" aria-label="The Settings gear" %} Configuración**. 2. Haz clic en **Análisis & seguridad**. diff --git a/translations/es-ES/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md b/translations/es-ES/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md index a74ec9a630..7271af5b03 100644 --- a/translations/es-ES/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md +++ b/translations/es-ES/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md @@ -25,7 +25,7 @@ topics: {% data variables.product.company_short %} lleva a cabo el {% data variables.product.prodname_secret_scanning %} en los repositorios{% ifversion fpt %}públicos y privados{% endif %} para los patrones de secretos que proporcionan los socios de {% data variables.product.company_short %} y {% data variables.product.company_short %}. Para obtener más información sobre el programa asociado del {% data variables.product.prodname_secret_scanning %}, consulta la sección "Programa asociado de escaneo de secretos". -Sin embargo, puede que existan situaciones en las que quieras escanear en búsqueda de otros patrones de secreto en tus repositorios {% ifversion fpt %}privados{% endif %}. Por ejemplo, puede que tengas un patrón secreto que sea interno a tu organización. For these situations, you can define custom {% data variables.product.prodname_secret_scanning %} patterns in your enterprise, organization, or {% ifversion fpt %}private{% endif %} repository on {% data variables.product.product_name %}. You can define up to 20 custom patterns for each {% ifversion fpt %}private{% endif %} repository, organization, or enterprise account. +Sin embargo, puede que existan situaciones en las que quieras escanear en búsqueda de otros patrones de secreto en tus repositorios {% ifversion fpt %}privados{% endif %}. Por ejemplo, puede que tengas un patrón secreto que sea interno a tu organización. Para estos casos, puedes definir patrones personalizados del {% data variables.product.prodname_secret_scanning %} en tu empresa, organización, o epositorio {% ifversion fpt %}privado{% endif %} en{% data variables.product.product_name %}. Puedes definir hasta 100 patrones personalizados para cada cuenta de organización o empresa y hasta 20 de ellos por repositorio {% ifversion fpt %}repositorio privado{% endif %}. {% ifversion ghes < 3.3 or ghae %} {% note %} @@ -62,7 +62,7 @@ Antes de definir un patrón personalizado, debes asegurarte de que hayas habilit {% note %} -**Note:** As there is no dry-run functionality, we recommend that you test your custom patterns in a repository before defining them for your entire organization. That way, you can avoid creating excess false-positive {% data variables.product.prodname_secret_scanning %} alerts. +**Nota:** Como no hay funcionalidad de pruebas en seco, te recomendamos probar tus patrones personalizados en un repositorio antes de definirlos para toda tu organización. De esta forma, puedes evitar crear un exceso de alertas de {% data variables.product.prodname_secret_scanning %} falsas positivas. {% endnote %} @@ -75,13 +75,13 @@ Antes de definir un patrón personalizado, debes asegurarte de que hayas habilit Después de que se cree un patrón, el {% data variables.product.prodname_secret_scanning %} escaneará cualquier secreto en los repositorios {% ifversion fpt %}privados{% endif %} de tu organización, incluyendo el historial completo de Git en todas las ramas. Se alertará a los propietarios de organizaciones y administradores de repositorios de cualquier secreto que se encuentre y estos podrán revisar la alerta en el repositorio en donde se encontró el secreto. Para obtener más información sobre cómo ver las alertas del {% data variables.product.prodname_secret_scanning %}, consulta la sección "[Administrar las alertas del {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)". -## Defining a custom pattern for an enterprise account +## Definir un patrón común para una cuenta empresarial -Before defining a custom pattern, you must ensure that you enable secret scanning for your enterprise account. For more information, see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)." +Antes de definir un patrón personalizado, debes garantizar que habilitaste el escaneo de secretos para tu cuenta empresarial. Para obtener más información, consulta la sección "[Habilitar la {% data variables.product.prodname_GH_advanced_security %} en tu empresa](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)". {% note %} -**Note:** As there is no dry-run functionality, we recommend that you test your custom patterns in a repository before defining them for your entire enterprise. That way, you can avoid creating excess false-positive {% data variables.product.prodname_secret_scanning %} alerts. +**Nota:** Como no hay funcionalidad de pruebas en seco, te recomendamos probar tus patrones personalizados en un repositorio antes de definirlos para toda tu empresa. De esta forma, puedes evitar crear alertas del {% data variables.product.prodname_secret_scanning %} falsas positivas en exceso. {% endnote %} @@ -89,35 +89,35 @@ Before defining a custom pattern, you must ensure that you enable secret scannin {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.advanced-security-policies %} {% data reusables.enterprise-accounts.advanced-security-security-features %} -1. Under "Secret scanning custom patterns", click {% ifversion fpt or ghes > 3.2 or ghae-next %}**New pattern**{% elsif ghes = 3.2 %}**New custom pattern**{% endif %}. +1. Debajo de "Patrones personalizados del escaneo de secretos", haz clic en {% ifversion fpt or ghes > 3.2 or ghae-next %}**Patrón nuevo**{% elsif ghes = 3.2 %}**Patrón personalizado nuevo**{% endif %}. {% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %} -After your pattern is created, {% data variables.product.prodname_secret_scanning %} scans for any secrets in {% ifversion fpt %}private{% endif %} repositories within your enterprise's organizations with {% data variables.product.prodname_GH_advanced_security %} enabled, including their entire Git history on all branches. Se alertará a los propietarios de organizaciones y administradores de repositorios de cualquier secreto que se encuentre y estos podrán revisar la alerta en el repositorio en donde se encontró el secreto. Para obtener más información sobre cómo ver las alertas del {% data variables.product.prodname_secret_scanning %}, consulta la sección "[Administrar las alertas del {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)". +Después de que se cree tu patrón, el {% data variables.product.prodname_secret_scanning %} escaneará en búsqueda de cualquier secreto en los repositorios {% ifversion fpt %}privados{% endif %} dentro de las organizaciones de tu empresa que cuenten con la {% data variables.product.prodname_GH_advanced_security %} habilitada, incluyendo todo su historial de Git en todas las ramas. Se alertará a los propietarios de organizaciones y administradores de repositorios de cualquier secreto que se encuentre y estos podrán revisar la alerta en el repositorio en donde se encontró el secreto. Para obtener más información sobre cómo ver las alertas del {% data variables.product.prodname_secret_scanning %}, consulta la sección "[Administrar las alertas del {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)". {% ifversion fpt or ghes > 3.2 %} -## Editing a custom pattern +## Editar un patrón personalizado -When you save a change to a custom pattern, this closes all the {% data variables.product.prodname_secret_scanning %} alerts that were created using the previous version of the pattern. -1. Navigate to where the custom pattern was created. A custom pattern can be created in a repository, organization, or enterprise account. - * For a repository or organization, display the "Security & analysis" settings for the repository or organization where the custom pattern was created. Para obtener más información, consulta las secciones anteriores "[Definir un patrón personalizado para un repositorio](#defining-a-custom-pattern-for-a-repository)" o "[Definir un patrón personalizado apra una organización](#defining-a-custom-pattern-for-an-organization)". - * For an enterprise, under "Policies" display the "Advanced Security" area, and then click **Security features**. For more information, see "[Defining a custom pattern for an enterprise account](#defining-a-custom-pattern-for-an-enterprise-account)" above. -2. Under "{% data variables.product.prodname_secret_scanning_caps %}", to the right of the custom pattern you want to edit, click {% octicon "pencil" aria-label="The edit icon" %}. -3. When you have reviewed and tested your changes, click **Save changes**. +Cuando guardas un cambio en un patrón personalizado, este cierra todas las alertas del {% data variables.product.prodname_secret_scanning %} que se crearon utilizando la versión anterior del patrón. +1. Navegar a donde se creó el patrón personalizado. Un patrón personalizado puede crearse en un repositorio, organización o cuenta empresarial. + * Para un repositorio u organización, muestra los ajustes de "Seguridad & análisis" para el repositorio u organización en donde se creó el patrón personalizado. Para obtener más información, consulta las secciones anteriores "[Definir un patrón personalizado para un repositorio](#defining-a-custom-pattern-for-a-repository)" o "[Definir un patrón personalizado apra una organización](#defining-a-custom-pattern-for-an-organization)". + * Para una empresa, debajo de "Políticas", muestra el área de "Seguridad Avanzada" y luego haz clic en **Características de seguridad**. Para obtener más información, consulta la sección anterior "[Definir un patrón personalizado para una cuenta empresarial](#defining-a-custom-pattern-for-an-enterprise-account)". +2. Debajo de "{% data variables.product.prodname_secret_scanning_caps %}", a la derecha del patrón personalizado que quieras editar, haz clic en {% octicon "pencil" aria-label="The edit icon" %}. +3. Cuando hayas revisado y probado tus cambios, haz clic en **Guardar cambios**. {% endif %} ## Eliminar un patrón personalizado -1. Navigate to where the custom pattern was created. A custom pattern can be created in a repository, organization, or enterprise account. +1. Navegar a donde se creó el patrón personalizado. Un patrón personalizado se puede crear en un repositorio, organización o cuenta empresarial. - * For a repository or organization, display the "Security & analysis" settings for the repository or organization where the custom pattern was created. Para obtener más información, consulta las secciones anteriores "[Definir un patrón personalizado para un repositorio](#defining-a-custom-pattern-for-a-repository)" o "[Definir un patrón personalizado apra una organización](#defining-a-custom-pattern-for-an-organization)". - * For an enterprise, under "Policies" display the "Advanced Security" area, and then click **Security features**. For more information, see "[Defining a custom pattern for an enterprise account](#defining-a-custom-pattern-for-an-enterprise-account)" above. + * Para un repositorio u organización, muestra los ajustes de "Seguridad & análisis" para el repositorio u organización en donde se creó el patrón personalizado. Para obtener más información, consulta las secciones anteriores "[Definir un patrón personalizado para un repositorio](#defining-a-custom-pattern-for-a-repository)" o "[Definir un patrón personalizado apra una organización](#defining-a-custom-pattern-for-an-organization)". + * Para una empresa, debajo de "Políticas", muestra el área de "Seguridad Avanzada" y luego haz clic en **Características de seguridad**. Para obtener más información, consulta la sección anterior "[Definir un patrón personalizado para una cuenta empresarial](#defining-a-custom-pattern-for-an-enterprise-account)". {%- ifversion fpt or ghes > 3.2 or ghae-next %} -1. To the right of the custom pattern you want to remove, click {% octicon "trash" aria-label="The trash icon" %}. -1. Review the confirmation, and select a method for dealing with any open alerts relating to the custom pattern. -1. Click **Yes, delete this pattern**. +1. A la derecha del patrón personalizado que quieras eliminar, haz clic en {% octicon "trash" aria-label="The trash icon" %}. +1. Revisa la confirmación y seleccionar el método para tratar con cualquier alerta abierta que tenga relación con el patrón personalizado. +1. Haz clic en **Sí, borrar este patrón**. - ![Confirming deletion of a custom {% data variables.product.prodname_secret_scanning %} pattern ](/assets/images/help/repository/secret-scanning-confirm-deletion-custom-pattern.png) + ![Confirmación del borrado de un patrón personalizado del {% data variables.product.prodname_secret_scanning %} ](/assets/images/help/repository/secret-scanning-confirm-deletion-custom-pattern.png) {%- elsif ghes = 3.2 %} -1. To the right of the custom pattern you want to remove, click **Remove**. -1. Review the confirmation, and click **Remove custom pattern**. +1. A la derecha del patrón personalizado que quieras eliminar, haz clic en **Eliminar**. +1. Revisa la confirmación y haz clic en **Eliminar patrón personalizado**. {%- endif %} diff --git a/translations/es-ES/content/code-security/secret-scanning/index.md b/translations/es-ES/content/code-security/secret-scanning/index.md index ae6bcaf69a..e71265cc6a 100644 --- a/translations/es-ES/content/code-security/secret-scanning/index.md +++ b/translations/es-ES/content/code-security/secret-scanning/index.md @@ -1,5 +1,5 @@ --- -title: Keeping secrets secure with secret scanning +title: Mantener los secretos seguros con el escaneo de secretos shortTitle: Escaneo de secretos intro: 'Permite que {% data variables.product.company_short %} haga el trabajo duro de asegurarse que los tokens, llaves privadas y otros secretos de código no estén expuestos en tu repositorio.' product: '{% data reusables.gated-features.secret-scanning %}' diff --git a/translations/es-ES/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md b/translations/es-ES/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md index 142d785187..68b2d902b3 100644 --- a/translations/es-ES/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md +++ b/translations/es-ES/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md @@ -59,7 +59,7 @@ Cuando un secreto se haya confirmado en un repositorio, deberás considerarlo en {% ifversion fpt or ghes > 3.1 or ghae-issue-4910 %} ## Configurar las notificaciones para las alertas del {% data variables.product.prodname_secret_scanning %} -Cuando se detecta un secreto nuevo, {% data variables.product.product_name %} notifica a todos los usuarios con acceso a las alertas de seguridad del repositorio de acuerdo con sus preferencias de notificación. You will receive alerts if you are watching the repository, have enabled notifications for security alerts or for all the activity on the repository, are the author of the commit that contains the secret and are not ignoring the repository. +Cuando se detecta un secreto nuevo, {% data variables.product.product_name %} notifica a todos los usuarios con acceso a las alertas de seguridad del repositorio de acuerdo con sus preferencias de notificación. Recibirás alertas si estás observando el repositorio, si habilitaste las notificaciones para las alertas de seguridad o para toda la actividad del repositorio, si eres el autor de la confirmación que contiene el secreto y si no estás ignorando el repositorio. Para obtener más información, consulta las secciones "[Administrar la seguridad y configuración de análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)" y "[Configurar las notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)". {% endif %} diff --git a/translations/es-ES/content/code-security/security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability.md b/translations/es-ES/content/code-security/security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability.md index be129fca20..83cfa82e81 100644 --- a/translations/es-ES/content/code-security/security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability.md +++ b/translations/es-ES/content/code-security/security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability.md @@ -44,7 +44,7 @@ Cualquier persona con permisos de escritura para un aviso de seguridad puede agr {% data reusables.repositories.sidebar-advisories %} 4. En la lista de "Asesorías de Seguridad", da clic sobre aquella en la que quieras añadir cambios. ![Asesoría de seguridad en el listado](/assets/images/help/security/security-advisory-in-list.png) 5. Agrega tus cambios en {% data variables.product.product_name %} o localmente: - - Para añadir cambios en {% data variables.product.product_name %}, debajo de "Añadir cambios a esta asesoría", da clic en **la bifurcación privada temporal**. Luego, crea una nueva rama y edita los archivos. For more information, see "[Creating and deleting branches within your repository](/articles/creating-and-deleting-branches-within-your-repository)" and "[Editing files](/repositories/working-with-files/managing-files/editing-files)." + - Para añadir cambios en {% data variables.product.product_name %}, debajo de "Añadir cambios a esta asesoría", da clic en **la bifurcación privada temporal**. Luego, crea una nueva rama y edita los archivos. Para obtener más información, consulta las secciones "[Crear y borrar ramas dentro de tu repositorio](/articles/creating-and-deleting-branches-within-your-repository)" y "[Editar los archivos](/repositories/working-with-files/managing-files/editing-files)". - Para añadir cambios localmente, sigue las instrucciones descritas en "Clonar y crear una nueva rama" y "Haz tus cambios, posteriormente, súbelos". ![Agregar cambios en este cuadro de aviso](/assets/images/help/security/add-changes-to-this-advisory-box.png) ## Crear una solicitud de extracción desde una bifurcación privada temporal diff --git a/translations/es-ES/content/code-security/security-advisories/editing-a-security-advisory.md b/translations/es-ES/content/code-security/security-advisories/editing-a-security-advisory.md index 609e3754a5..169f1e6a1a 100644 --- a/translations/es-ES/content/code-security/security-advisories/editing-a-security-advisory.md +++ b/translations/es-ES/content/code-security/security-advisories/editing-a-security-advisory.md @@ -34,7 +34,7 @@ Si crees que se te debería dar crédito por alguna asesoría de seguridad, por {% data reusables.repositories.security-advisory-edit-cwe-cve %} {% data reusables.repositories.security-advisory-edit-description %} 11. Opcionalmente, puedes editar los "Créditos" para la asesoría de seguridad. ![Créditos para una asesoría de seguridad](/assets/images/help/security/security-advisory-credits.png) -12. Da clic en **Actualizar asesoría de seguridad**". !["Update security advisory" button](/assets/images/help/security/update-advisory-button.png) +12. Da clic en **Actualizar asesoría de seguridad**". ![Botón de "Actualizar asesoría de seguridad" button](/assets/images/help/security/update-advisory-button.png) 13. Las personas listadas en la sección de "Créditos" recibirán una notificación web o por correo electrónico que los invita a aceptar el crédito. Si la persona acepta, su nombre de usuario estará visible al público una vez que la asesoría de seguridad se publique. ## Leer más diff --git a/translations/es-ES/content/code-security/security-advisories/publishing-a-security-advisory.md b/translations/es-ES/content/code-security/security-advisories/publishing-a-security-advisory.md index 8963982779..667676aae5 100644 --- a/translations/es-ES/content/code-security/security-advisories/publishing-a-security-advisory.md +++ b/translations/es-ES/content/code-security/security-advisories/publishing-a-security-advisory.md @@ -61,19 +61,6 @@ Después de que publicas una asesoría de seguridad, la URL de la misa permanece Si necesitas actualizar o corregir información en una asesoría de seguridad que hayas publicado, puedes editarla. Para obtener más información, consulta la sección "[Editar una asesoría de seguridad](/github/managing-security-vulnerabilities/editing-a-security-advisory)". -## Pedir el número de identificación de CVE - -Cualquiera con permisos de administrador en una asesoría de seguridad puede solicitar un número de identificación de CVE para la asesoría de seguridad. - -{% data reusables.repositories.request-security-advisory-cve-id %} Para obtener más información, consulta la sección "[Acerca de las {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories#cve-identification-numbers)". - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-security %} -{% data reusables.repositories.sidebar-advisories %} -4. En el listado de "Asesorías de Seguridad", da clic en aquella para la cual quieras solicitar un número de identificación de CVE. ![Asesoría de seguridad en el listado](/assets/images/help/security/security-advisory-in-list.png) -5. Utiliza el menú desplegable de **Publicar asesoría** y da clic en **Solicitar CVE**. ![Solicitar un CVE en el menú desplegable](/assets/images/help/security/security-advisory-drop-down-request-cve.png) -6. Da clic en **Solicitar CVE**. ![Botón "Solicitar CVE"](/assets/images/help/security/security-advisory-request-cve-button.png) - ## Publicar una asesoría de seguridad El publicar una asesoría de seguridad borra la bifurcación temporal privada para la misma. @@ -88,6 +75,17 @@ El publicar una asesoría de seguridad borra la bifurcación temporal privada pa {% data reusables.repositories.github-reviews-security-advisories %} +## Solicitar un número de identificación de CVE (Opcional) + +{% data reusables.repositories.request-security-advisory-cve-id %} Para obtener más información, consulta la sección "[Acerca de las {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories#cve-identification-numbers)". + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-security %} +{% data reusables.repositories.sidebar-advisories %} +4. En el listado de "Asesorías de Seguridad", da clic en aquella para la cual quieras solicitar un número de identificación de CVE. ![Asesoría de seguridad en el listado](/assets/images/help/security/security-advisory-in-list.png) +5. Utiliza el menú desplegable de **Publicar asesoría** y da clic en **Solicitar CVE**. ![Solicitar un CVE en el menú desplegable](/assets/images/help/security/security-advisory-drop-down-request-cve.png) +6. Da clic en **Solicitar CVE**. ![Botón "Solicitar CVE"](/assets/images/help/security/security-advisory-request-cve-button.png) + ## Leer más - "[retirar una asesoría de seguridad](/github/managing-security-vulnerabilities/withdrawing-a-security-advisory)" 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 889a2d5484..dc1613e5f0 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: 'You can view, filter, and sort security alerts for repositories owned by your organization or team in one place: the Security Overview page.' +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.' product: '{% data reusables.gated-features.security-center %}' redirect_from: - /code-security/security-overview/exploring-security-alerts versions: fpt: '*' + ghae: issue-4554 ghes: '>3.1' - ghae: next type: how_to topics: - Security overview @@ -15,7 +15,7 @@ topics: - Alerts - Organizations - Teams -shortTitle: About security overview +shortTitle: Acerca del resumen de seguridad --- {% data reusables.security-center.beta %} @@ -26,13 +26,13 @@ Puedes utilizar el resumen de seguirdad para tener una vista de nivel alto del e El resumen de seguridad indica si las características de {% ifversion fpt or ghes > 3.1 %}seguridad{% endif %}{% ifversion ghae-next %}{% data variables.product.prodname_GH_advanced_security %}{% endif %}están habilitadas para los repositorios que pertenecen a tu organización y consolidan las alertas para cada característica.{% ifversion fpt or ghes > 3.1 %} Las características de seguridad incluyen aquellas de {% data variables.product.prodname_GH_advanced_security %}, tales como el {% data variables.product.prodname_code_scanning %} y el {% data variables.product.prodname_secret_scanning %}, así como las {% data variables.product.prodname_dependabot_alerts %}.{% endif %} Para obtener más información sobre las características de {% data variables.product.prodname_GH_advanced_security %}, consulta la sección "[Acerca de la {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)".{% ifversion fpt or ghes > 3.1 %} para obtener más información sobre las {% data variables.product.prodname_dependabot_alerts %}, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)".{% endif %} -For more information about securing your code at the repository and organization levels, see "[Securing your repository](/code-security/getting-started/securing-your-repository)" and "[Securing your organization](/code-security/getting-started/securing-your-organization)." +Para obtener más información sobre cómo proteger tu código a nivel de repositorio u organización, consulta las secciones "[Proteger tu repositorio](/code-security/getting-started/securing-your-repository)" y "[Proteger tu organización](/code-security/getting-started/securing-your-organization)". En el resumen de seguridad, puedes ver, clasificar y filtrar las alertas para entender los riesgos de seguridad en tu organización y en los repositorios específicos. Puedes aplicar varios filtros para enfocarte en áreas de interés. Por ejemplo, puedes identificar repositorios privados que tengan una gran cantidad de {% data variables.product.prodname_dependabot_alerts %} o repositorios que no tengan alertas del {% data variables.product.prodname_code_scanning %}. ![El resumen de seguridad para una organziación](/assets/images/help/organizations/security-overview.png) -For each repository in the security overview, you will see icons for each type of security feature and how many alerts there are of each type. If a security feature is not enabled for a repository, the icon for that feature will be grayed out. +Para cada repositorio en el resumen de seguridad, verás iconos de cada tipo de característica de seguridad y cuántas alertas hay para cada tipo. Si no se habilita una característica de seguridad para un repositorio, su icono se mostrará en gris. ![Los iconos en el resumen de seguridad](/assets/images/help/organizations/security-overview-icons.png) @@ -41,12 +41,12 @@ For each repository in the security overview, you will see icons for each type o | {% octicon "code-square" aria-label="Code scanning alerts" %} | Alertas de {% data variables.product.prodname_code_scanning_capc %}. Para obtener más información, consulta la sección "[Acerca del {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-code-scanning)". | | {% octicon "key" aria-label="Secret scanning alerts" %} | alertas del {% data variables.product.prodname_secret_scanning_caps %}. Para obtener más información, consulta la sección "[Acerca del {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)". | | {% octicon "hubot" aria-label="Dependabot alerts" %} | {% data variables.product.prodname_dependabot_alerts %}. Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)". | -| {% octicon "check" aria-label="Check" %} | The security feature is enabled, but does not raise alerts in this repository. | -| {% octicon "x" aria-label="x" %} | The security feature is not supported in this repository. | +| {% octicon "check" aria-label="Check" %} | La característica de seguridad se habilitó pero no levanta alertas en este repositorio. | +| {% octicon "x" aria-label="x" %} | La característica de seguridad no es compatible con este repositorio. | Predeterminadamente, los repositorios archivados se excluyen del resumen de seguridad de una organización. Puedes aplicar filtros para ver los repositorios archivados en el resumen de seguridad. Para obtener más información, consulta la sección "[Filtrar la lista de alertas](#filtering-the-list-of-alerts)". -The security overview displays active alerts raised by security features. Si no hay alertas en el resumen de seguridad de un repositorio, las vulnerabilidades de seguridad no detectadas o los errores de código podrían aún existir. +El resumen de seguridad muestra alertas activas que levantan las características de seguridad. Si no hay alertas en el resumen de seguridad de un repositorio, las vulnerabilidades de seguridad no detectadas o los errores de código podrían aún existir. ## Visualizar el resumen de seguridad de una organización @@ -71,7 +71,7 @@ Los miembros de un equipo pueden ver el resumen de seguridad de los repositorios ### Filtrar por nivel de riesgo para los repositorios -The level of risk for a repository is determined by the number and severity of alerts from security features. If one or more security features are not enabled for a repository, the repository will have an unknown level of risk. If a repository has no risks that are detected by security features, the repository will have a clear level of risk. +El nivel de riesgo de un repositorio se determina por la cantidad y severidad de las alertas de las características de seguridad. Si no están habilitadas una o más características de seguridad para un repositorio, este tendrá un nivel de riesgo desconocido. Si un repositorio no tiene riesgos que detecten las características de seguridad, este tendrá un nivel de riesgo claro. | Qualifier | Descripción | | -------------- | -------------------------------------------------------------------- | @@ -89,7 +89,7 @@ The level of risk for a repository is determined by the number and severity of a | secret-scanning-alerts:n | Muestra los repositorios que tienen *n* alertas del {% data variables.product.prodname_secret_scanning %}. Este calificador puede utilizar los operadores de comparación > y <. | | dependabot-alerts:n | Muestra los repositorios que tienen *n* {% data variables.product.prodname_dependabot_alerts %}. Este calificador puede utilizar los operadores de comparación > y <. | -### Filter by whether security features are enabled +### Filtrar por el criterio de tener habilitadas las características de seguridad | Qualifier | Descripción | | ------------------------------- | ----------------------------------------------------------------------------------------------------------------- | @@ -102,7 +102,7 @@ The level of risk for a repository is determined by the number and severity of a ### Filtrar por tipo de repositorio -| Qualifier | Description | | -------- | -------- |{% ifversion fpt or ghes > 3.1 %} | `is:public` | Display public repositories. |{% endif %} | `is:internal` | Display internal repositories. | | `is:private` | Display private repositories. | | `archived:true` | Display archived repositories. | +| Calificador | Descripción | | -------- | -------- |{% ifversion fpt or ghes > 3.1 %} | `is:public` | Muestra repositorios públicos. |{% endif %} | `is:internal` | Muestra repositorios internos. | | `is:private` | Muestra repositorios privados. | | `archived:true` | Muestra repositorios archivados. | ### Filtrar por equipo 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 833459e6d4..c492ff7ffa 100644 --- a/translations/es-ES/content/code-security/security-overview/index.md +++ b/translations/es-ES/content/code-security/security-overview/index.md @@ -5,8 +5,8 @@ intro: 'Visualiza, clasifica y filtra las alertas de seguridad desde cualquier p product: '{% data reusables.gated-features.security-center %}' versions: fpt: '*' + ghae: issue-4554 ghes: '>3.1' - ghae: next topics: - Security overview - Advanced Security diff --git a/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md b/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md index 988ac5c1ac..4464ef469c 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md +++ b/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md @@ -14,7 +14,7 @@ topics: - Repositories - Dependencies - Pull requests -shortTitle: Use Dependabot with actions +shortTitle: Utiliza el Dependabot con las acciones --- ## Acerca del {% data variables.product.prodname_dependabot %} y de las {% data variables.product.prodname_actions %} diff --git a/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md b/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md index c399726c96..1bccfeb7f6 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md +++ b/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md @@ -181,7 +181,7 @@ Utiliza la opción `allow` para personalizar qué dependencias se actualizan. Es | `direct` | Todas | Todas las dependencias definidas explícitamente. | | `indirect` | `bundler`, `pip`, `composer`, `cargo` | Las dependencias de las dependencias directas (también conocidas como sub-dependencias, o dependencias transitorias). | | `all` | Todas | Todas las dependencias definidas explícitamente. Para `bundler`, `pip`, `composer`, `cargo`, también las dependencias de las dependencias directas. | - | `production` | `bundler`, `composer`, `mix`, `maven`, `npm`, `pip` | Only dependencies in the "Production dependency group". | + | `production` | `bundler`, `composer`, `mix`, `maven`, `npm`, `pip` | Solo las dependencias en el "Grupo de dependencias de producción". | | `development` | `bundler`, `composer`, `mix`, `maven`, `npm`, `pip` | Únicamente las dependencias en el "Grupo de dependencias de desarrollo". | ```yaml @@ -539,7 +539,7 @@ updates: ### `schedule.day` -When you set a `weekly` update schedule, by default, {% data variables.product.prodname_dependabot %} checks for new versions on Monday at a random set time for the repository. Utiliza `schedule.day` para especificar un día alterno para revisar si hay actualizaciones. +Cuando configuras una programación de actualizaciones en `weekly`, predeterminadamente, {% data variables.product.prodname_dependabot %} revisa si hay versiones nuevas los lunes en alguna hora aleatoria para el repositorio. Utiliza `schedule.day` para especificar un día alterno para revisar si hay actualizaciones. Valores compatibles @@ -566,7 +566,7 @@ updates: ### `schedule.time` -By default, {% data variables.product.prodname_dependabot %} checks for new versions at a random set time for the repository. Utiliza `schedule.time` para especificar una hora alterna para revisar si hay actualizaciones (formato: `hh:mm`). +Predeterminadamente, el {% data variables.product.prodname_dependabot %} revisa si hay nuevas versiones en una hora aleatoria para el repositorio. Utiliza `schedule.time` para especificar una hora alterna para revisar si hay actualizaciones (formato: `hh:mm`). ```yaml # Set a time for checks @@ -582,7 +582,7 @@ updates: ### `schedule.timezone` -By default, {% data variables.product.prodname_dependabot %} checks for new versions at a random set time for the repository. Utiliza `schedule.timezone` para especificar un huso horario alternativo. El identificador de zona debe ser tomado de la base de datos de Husos Horarios que mantiene [iana](https://www.iana.org/time-zones). Para obtener más información, consulta la [Lista de bases de datos tz para husos horarios](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones). +Predeterminadamente, el {% data variables.product.prodname_dependabot %} revisa si hay nuevas versiones en una hora aleatoria para el repositorio. Utiliza `schedule.timezone` para especificar un huso horario alternativo. El identificador de zona debe ser tomado de la base de datos de Husos Horarios que mantiene [iana](https://www.iana.org/time-zones). Para obtener más información, consulta la [Lista de bases de datos tz para husos horarios](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones). ```yaml # Specify the timezone for checks @@ -827,7 +827,7 @@ registries: ### `maven-repository` -The `maven-repository` type supports username and password. +El tipo `maven-repository` es compatible con usuario y contraseña. {% raw %} ```yaml @@ -844,7 +844,7 @@ registries: El tipo `npm-registry` es compatible con nombre de usuario y contraseña, o token. -When using username and password, your `.npmrc`'s auth token may contain a `base64` encoded `_password`; however, the password referenced in your {% data variables.product.prodname_dependabot %} configuration file must be the original (unencoded) password. +Cuando utilizas un nombre de usuario y contraseña, tu token de autorización de `.npmrc` podría contener un `_password` cifrado en `base64`; sin embargo, la contraseña referenciada en tu archivo de configuración del {% data variables.product.prodname_dependabot %} podría ser la contraseña original (descifrada). {% raw %} ```yaml diff --git a/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/upgrading-from-dependabotcom-to-github-native-dependabot.md b/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/upgrading-from-dependabotcom-to-github-native-dependabot.md index a26eb9e328..5d13b9878c 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/upgrading-from-dependabotcom-to-github-native-dependabot.md +++ b/translations/es-ES/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/upgrading-from-dependabotcom-to-github-native-dependabot.md @@ -16,9 +16,9 @@ shortTitle: Actualizaciones de Dependabot.com {% warning %} -Dependabot Preview has been shut down as of August 3rd, 2021. In order to keep getting Dependabot updates, please migrate to GitHub-native Dependabot. +La Vista Previa del Dependabot también se cerró desde el 3 de agosto de 2021. Para seguir obteniendo actualizaciones del Dependabot, por favor, mígrate al Dependabot nativo de GitHub. -Open pull requests from Dependabot Preview will remain open, including the pull request to upgrade to GitHub-native Dependabot, but the bot itself will no longer work on your {% data variables.product.prodname_dotcom %} accounts and organizations. +Las solicitudes de cambios abiertas de la Vista Previa del Dependabot permanecerán abiertas, incluyendo las solicitudes de cambio para actualizar al Dependabot nativo de GitHub, pero el bot mismo ya no funcionará en tus cuentas y organizaciones de {% data variables.product.prodname_dotcom %}. {% endwarning %} @@ -31,7 +31,7 @@ La vista previa del Dependabot se creó directamente en {% data variables.produc Si bien la mayoría de las características de la vista previa del Dependabot existen en el {% data variables.product.prodname_dependabot %} nativo de {% data variables.product.prodname_dotcom %}, algunas no están disponibles en él: - **Actualizaciones en vivo:** Esperamos tenerlas de vuelta pronto. Por el momento, puedes ejecutar el {% data variables.product.prodname_dependabot %} de {% data variables.product.prodname_dotcom %} diariamente para que atrae paquetes al transcurrir un día de su lanzamiento. - **Registros de variable de ambiente PHP:** Para los proyectos que dependen de la variable de ambiente `ACF_PRO_KEY`, puede que seas capaz de expender tu copia licenciada del plugin de los Campos Personalizados Avanzados. Para encontrar un ejemplo, consulta [dependabot/acf-php-example](https://github.com/dependabot/acf-php-example#readme). Para encontrar otras variables de ambiente, puedes utilizar {% data variables.product.prodname_actions %} para recuperar las dependencias desde estos registros. -- **Fusión automática:** Siempre recomendamos verificar tus dependencias antes de fusionarlas; por lo tanto, la fusión automática no será compatible en el futuro previsible. Para aquellos que vetaron sus dependencias o que solo utilizan las internas, recomendamos agregar aplicaciones de fusión automática de terceros o configurar GitHub Actions para fusionar. We have provided the [`dependabot/fetch-metadata`](https://github.com/marketplace/actions/fetch-metadata-from-dependabot-prs) action to help developers [enable GitHub's automerge](https://github.com/dependabot/fetch-metadata/#enabling-auto-merge). +- **Fusión automática:** Siempre recomendamos verificar tus dependencias antes de fusionarlas; por lo tanto, la fusión automática no será compatible en el futuro previsible. Para aquellos que vetaron sus dependencias o que solo utilizan las internas, recomendamos agregar aplicaciones de fusión automática de terceros o configurar GitHub Actions para fusionar. Hemos proporcionado la acción [`dependabot/fetch-metadata`](https://github.com/marketplace/actions/fetch-metadata-from-dependabot-prs) para ayudar a los desarrolladores a [Habilitar la fusión automática de GitHub](https://github.com/dependabot/fetch-metadata/#enabling-auto-merge). En el {% data variables.product.prodname_dependabot %} nativo de {% data variables.product.prodname_dotcom %}, puedes configurar todas las actualizaciones de versión utilizando el archivo de configuración. Este archivo es similar al archivo de configuración de la vista previa de Dependabot con algunos cambios y mejoras que se incluirán automáticamente en su solicitud de extracción de actualización. Para obtener más información sobre la solicitud de cambios de actualziación, consulta la sección "[Actualizar a un Dependabot nativo de GitHub](/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot#upgrading-to-github-native-dependabot)". diff --git a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates.md b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates.md index 18c29af3f7..63ba8946ea 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates.md +++ b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates.md @@ -51,7 +51,7 @@ Cuando fusionas una solicitud de cambios que contiene una actualización de segu ## Acerca de las puntuaciones de compatibilidad -{% data variables.product.prodname_dependabot_security_updates %} may include compatibility scores to let you know whether updating a dependency could cause breaking changes to your project. Estos se calculan de las pruebas de IC en otros repositorios públicos en donde se ha generado la misma actualización de seguridad. La puntuación de compatibilidad de una actualización es el porcentaje de ejecuciones de IC que pasaron cuando se hicieron actualizaciones en versiones específicas de la dependencia. +Las {% data variables.product.prodname_dependabot_security_updates %} podrían incluir puntuaciones de compatibilidad para hacerte saber si el actualizar una dependencia podría causar cambios sustanciales en tu proyecto. Estos se calculan de las pruebas de IC en otros repositorios públicos en donde se ha generado la misma actualización de seguridad. La puntuación de compatibilidad de una actualización es el porcentaje de ejecuciones de IC que pasaron cuando se hicieron actualizaciones en versiones específicas de la dependencia. ## Acerca de las notificaciones para las actualizaciones de seguridad del {% data variables.product.prodname_dependabot %} diff --git a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md index 2eba1a2288..01902288dd 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md +++ b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md @@ -36,7 +36,7 @@ Predeterminadamente, si tu administrador de sitio configuró el correo electrón ## Configurar las notificaciones para las {% data variables.product.prodname_dependabot_alerts %} {% ifversion fpt or ghes > 3.1 %} -When a new {% data variables.product.prodname_dependabot %} alert is detected, {% data variables.product.product_name %} notifies all users with access to {% data variables.product.prodname_dependabot_alerts %} for the repository according to their notification preferences. You will receive alerts if you are watching the repository, have enabled notifications for security alerts or for all the activity on the repository, and are not ignoring the repository. Para obtener más información, consulta la sección "[Configurar las notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)". +Cuando se detecta una alerta nueva del {% data variables.product.prodname_dependabot %}, {% data variables.product.product_name %} notifica a todos los usuarios del repositorio con acceso a las {% data variables.product.prodname_dependabot_alerts %} de acuerdo con sus preferencias de notificación. Recibirás las alertas si estás observando el repositorio, si habilitas las notificaciones para las alertas de seguridad para toda la actividad del repositorio y si es que no lo estás ignorando. Para obtener más información, consulta la sección "[Configurar las notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)". {% endif %} Puedes configurar los ajustes de notificaciones para ti mismo o para tu organización desde el menú desplegable de administrar notificaciones {% octicon "bell" aria-label="The notifications bell" %} que se muestra en la parte superior de cada página. Para obtener más información, consulta la sección "[Configurar las notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)". diff --git a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md index 614fedbf48..6e591cd80f 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md +++ b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md @@ -72,7 +72,7 @@ Sí, la gráfica de dependencias tiene dos categorías de límites: Los manifiestos mayores a 0.5 MB solo se procesan para las cuentas empresariales. En el caso de otras cuentas, los manifiestos mayores a 0.5 MB se ingoran y no crearán {% data variables.product.prodname_dependabot_alerts %}. - Predeterminadamente, {% data variables.product.prodname_dotcom %} no procesará más de 20 manifiestos por repositorio. {% data variables.product.prodname_dependabot_alerts %} are not created for manifests beyond this limit. Si necesitas incrementar el límite, contacta a {% data variables.contact.contact_support %}. + Predeterminadamente, {% data variables.product.prodname_dotcom %} no procesará más de 20 manifiestos por repositorio. Las {% data variables.product.prodname_dependabot_alerts %} no se crean para los manifiestos más allá de este límite. Si necesitas incrementar el límite, contacta a {% data variables.contact.contact_support %}. 2. **Límites de visualización** 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 7f2bcf6711..3dc73c428f 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 @@ -1,11 +1,11 @@ --- title: Acerca de la revisión de dependencias intro: 'La revisión de dependencias te permite detectar las dependencias vulnerables antes de que las introduzcas a tu ambiente y te proporciona información sobre la licencia, dependientes y edad de las dependencias.' +product: '{% data reusables.gated-features.dependency-review %}' shortTitle: Revisión de dependencias versions: fpt: '*' ghes: '>= 3.2' - product: '{% data reusables.gated-features.dependency-review %}' type: overview topics: - Advanced Security @@ -38,6 +38,6 @@ Las {% data variables.product.prodname_dependabot_alerts %} encontrarán vulnera La revisión de dependencias es compatible con los mismos lenguajes de programación y ecosistemas de administración de paquetes que la gráfica de dependencias. 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#supported-package-ecosystems)". -## Enabling dependency review +## Habilitar la revisión de dependencias -The dependency review feature becomes available when you enable the dependency graph. {% ifversion fpt %}For more information, see "[Enabling the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph#enabling-the-dependency-graph)."{% endif %}{% ifversion ghes > 3.1 %}For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %} +La característica de revisión de dependencias se encuentra disponible cuando habilitas la gráfica de dependencias. {% ifversion fpt %}Para obtener más información, consulta la sección "[Habilitar la gráfica de dependencias](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph#enabling-the-dependency-graph)".{% endif %}{% ifversion ghes > 3.1 %}Para obtener más información, consulta la sección "[Habilitar las alertas para dependencias vulnerables en{% data variables.product.prodname_ghe_server %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)".{% endif %} diff --git a/translations/es-ES/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md b/translations/es-ES/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md index 6ffabdd3e3..45a8b7aa60 100644 --- a/translations/es-ES/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md +++ b/translations/es-ES/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md @@ -9,7 +9,7 @@ product: '{% data reusables.gated-features.codespaces %}' shortTitle: Registro de imagen privado --- -## About private image registries and {% data variables.product.prodname_codespaces %} +## Acerca de los registros de imagen y {% data variables.product.prodname_codespaces %} privados Un registro es un espacio seguro para almacenar y administrar imágenes privadas de contenedores, tales como el Registro de Contenedores de Azure o DockerHub. Puedes crear secretos en GitHub para almacenar los detalles de acceso para un registro privado y utilizarlos para otorgar acceso a tu codespace para las imágenes que se almacenan en el registro. @@ -21,13 +21,13 @@ Cuando ejecutas un codespace, {% data variables.product.prodname_codespaces %} v Puedes almacenar los secretos a nivel de repositorio, organización o usuario, lo cual te permite compartirlos de forma segura entre diferentes codespaces. Cuando creas un conjunto de secretos para un registro de imagen privado, necesitas reemplazar el "<*>” del nombre con un identificador consistente. Para obtener más información, consulta las secciones "[Administrar los secretos cifrados para tus codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)" y "[Administrar los secretos cifrados de tu repositorio y organización para los Codespaces](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces)". -If you are setting the secrets at the user or organization level, make sure to assign those secrets to the repository you'll be creating the codespace in by choosing an access policy from the dropdown list. +Si estás configurando secretos a nivel de organización o de usuario, asegúrate de asignarlos al repositorio en el que crearás el codespace eligiendo una política de acceso desde la lista desplegable. ![Ejemplo de secreto de registro de imagen](/assets/images/help/codespaces/secret-repository-access.png) -## Example secrets +## Secretos de ejemplo -For a private image registry in Azure, you could create the following secrets: +Para los registros de imagen privados en Azure, podrías crear los siguientes secretos: ``` ACR_CONTAINER_REGISTRY_SERVER = mycompany.azurecr.io @@ -35,18 +35,18 @@ ACR_CONTAINER_REGISTRY_USER = acr-user-here ACR_CONTAINER_REGISTRY_PASSWORD = ``` -For information on common image registries, see "[Common image registry servers](#common-image-registry-servers)." +Para obtener más información sobre los registros de imagen comunes, consulta la sección "[Servidores de registro de imagen comunes](#common-image-registry-servers)". ![Ejemplo de secreto de registro de imagen](/assets/images/help/settings/codespaces-image-registry-secret-example.png) -Once you've added the secrets, you may need to stop and then start the codespace you are in for the new environment variables to be passed into the container. For more information, see "[Suspending or stopping a codespace](/codespaces/codespaces-reference/using-the-command-palette-in-codespaces#suspending-or-stopping-a-codespace)." +Una vez que hayas agregado los secretos, podría ser que necesites parar y luego iniciar el codespace en el que estás para que las variables de ambiente nuevas pasen en el contenedor. Para obtener más información, consulta la sección "[Suspender o detener un codespace](/codespaces/codespaces-reference/using-the-command-palette-in-codespaces#suspending-or-stopping-a-codespace)". -## Common image registry servers +## Servidores de registro de imagen comunes -Some of the common image registry servers are listed below: +Algunos de los servidores de registro de imagen comunes se listan a continuación: - [DockerHub](https://docs.docker.com/engine/reference/commandline/info/) - `https://index.docker.io/v1/` -- [GitHub Container Registry](/packages/working-with-a-github-packages-registry/working-with-the-container-registry) - `ghcr.io` -- [Azure Container Registry](https://docs.microsoft.com/azure/container-registry/) - `.azurecr.io` -- [Amazon Elastic Container Registry](https://docs.aws.amazon.com/AmazonECR/latest/userguide/Registries.html) - `.dkr.ecr..amazonaws.com` -- [Google Cloud Container Registry](https://cloud.google.com/container-registry/docs/overview#registries) - `gcr.io` (US), `eu.gcr.io` (EU), `asia.gcr.io` (Asia) +- [Registro de Contenedores de GitHub](/packages/working-with-a-github-packages-registry/working-with-the-container-registry) - `ghcr.io` +- [Registro de Contenedores de Azure](https://docs.microsoft.com/azure/container-registry/) - `.azurecr.io` +- [Registro de Contenedores Elástico de Amazon](https://docs.aws.amazon.com/AmazonECR/latest/userguide/Registries.html) - `.dkr.ecr..amazonaws.com` +- [Registro de Contenedores de Google Cloud](https://cloud.google.com/container-registry/docs/overview#registries) - `gcr.io` (US), `eu.gcr.io` (EU), `asia.gcr.io` (Asia) 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 c19925dd57..4022e9ef03 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 @@ -6,7 +6,7 @@ versions: product: '{% data reusables.gated-features.codespaces %}' topics: - Codespaces -shortTitle: Disaster recovery +shortTitle: Recuperación de desastres --- Nos esforzamos para asegurarnos de que {% data variables.product.prodname_codespaces %} siempre esté disponible. Sin embargo, por causas de fuerza mayor que salen de nuestro control, algunas veces se impacta el servicio en formas qeu pueden causar interrupciones de servicio no planeadas. @@ -21,21 +21,21 @@ La siguiente orientación proporciona opciones sobre cómo manejar la interrupci {% endnote %} -## Option 1: Create a new codespace in another region +## Opción 1: Crea un codespace nuevo en otra región -In the case of a regional outage, we suggest you recreate your codespace in an unaffected region to continue working. Este codespace nuevo tendrá todos los cambios desde tu última subida en {% data variables.product.prodname_dotcom %}. For information on manaully setting another region, see "[Setting your default region for Codespaces](/codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces)." +En caso de que haya una interrupción regional, te sugerimos volver a crear tu codespace en una región no afectada para seguir trabajando. Este codespace nuevo tendrá todos los cambios desde tu última subida en {% data variables.product.prodname_dotcom %}. Para obtener más información sobre cómo configurar otra región manualmente, consulta la sección "[Configurar tu región predeterminada para los Codespaces](/codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces)". -You can optimize recovery time by configuring a `devcontainer.json` in the project's repository, which allows you to define the tools, runtimes, frameworks, editor settings, extensions, and other configuration necessary to restore the development environment automatically. Para obtener más información, consulta la sección "[Configurar Codespaces para tu proyecto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". +Puedes optimizar el tiempo de recuperación si configuras un `devcontainer.json` en el repositorio de un proyecto, el cual te permita definir las herramientas, tiempos de ejecución, configuración del editor, extensiones y otros tipos de configuración necesarios para restablecer el ambiente de desarrollo automáticamente. Para obtener más información, consulta la sección "[Configurar Codespaces para tu proyecto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". ## Opción 2: esperar para la recuperación En este caso, no se requiere que tomes acción alguna. Debes saber que estamos trabajando diligentemente para restaurar la disponibilidad del servicio. -You can check the current service status on the [Status Dashboard](https://www.githubstatus.com/). +Puedes verificar el estado de servicio actual en el [Tablero de estado](https://www.githubstatus.com/). ## Opción 3: Clona el repositorio localmente o edítalo en el buscador -Mientras que los {% data variables.product.prodname_codespaces %} proporcinan el beneficio de un ambiente de desarrollador pre-configurado, siempre debe poderse acceder a tu código mediante el repositorio que se hospeda en {% data variables.product.prodname_dotcom_the_website %}. En caso de que haya una interrupción de un {% data variables.product.prodname_codespaces %}, aún podrás clonar el repositorio localmente o los archivos de edición en el editor del buscador de {% data variables.product.company_short %}. For more information, see "[Editing files](/repositories/working-with-files/managing-files/editing-files)." +Mientras que los {% data variables.product.prodname_codespaces %} proporcinan el beneficio de un ambiente de desarrollador pre-configurado, siempre debe poderse acceder a tu código mediante el repositorio que se hospeda en {% data variables.product.prodname_dotcom_the_website %}. En caso de que haya una interrupción de un {% data variables.product.prodname_codespaces %}, aún podrás clonar el repositorio localmente o los archivos de edición en el editor del buscador de {% data variables.product.company_short %}. Para obtener más información, consulta la sección "[Editar archivos](/repositories/working-with-files/managing-files/editing-files)". Si bien esta opción no te configura un ambiente de desarrollo, te permitirá hacer cambios a tu código fuente conforme los necesites mientras esperas a que se resuelva la interrupción del servicio. 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 d9326ddc39..7a90657bf5 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 @@ -1,6 +1,6 @@ --- -title: Security in Codespaces -intro: 'Overview of the {% data variables.product.prodname_codespaces %} security architecture, with guidelines to help you maintain security and minimize the risk of attack.' +title: La seguridad den los Codespaces +intro: 'Resumen de la arquitectura de seguridad de {% data variables.product.prodname_codespaces %}, con lineamientos para ayudarte a mantener la seguridad y minimizar el riesgo de un ataque.' miniTocMaxHeadingLevel: 3 versions: fpt: '*' @@ -8,98 +8,98 @@ topics: - Codespaces - Security type: reference -shortTitle: Security in Codespaces +shortTitle: Seguridad en los Codespaces --- -## Overview of codespace security +## Resumen de la seguridad de un codespace -{% data variables.product.prodname_codespaces %} is designed to be security hardened by default. Consequently, you will need to ensure that your software development practices do not risk reducing the security posture of your codespace. +{% data variables.product.prodname_codespaces %} se diseñó para que, predeterminadamente, tuviera seguridad reforzada. Como consecuencia, necesitarás garantizar que tus prácticas de desarrollo de software no arriesguen el reducir la postura de seguridad de tu codespace. -This guide describes the way Codespaces keeps your development environment secure and provides some of the good practices that will help maintain your security as you work. As with any development tool, remember that you should only open and work within repositories you know and trust. +Esta guía describe la forma en la que Codespaces mantiene seguro tu ambiente de desarrollo y proporciona algunas de las buenas prácticas que ayudarán a mantener tu seguridad conforme trabajas. Como con cualquier herramienta de desarrollo, recuerda que solo debes intentar abrir y trabajar en repositorios que conoces y confías. -### Environment isolation +### Aislamiento de ambiente -{% data variables.product.prodname_codespaces %} is designed to keep your codespaces separate from each other, with each using its own virtual machine and network. +{% data variables.product.prodname_codespaces %} se diseñó para mantener tus codespaces separados entre sí, con cada uno utilizando su red y máquina virtual propias. -#### Isolated virtual machines +#### Máquinas virtuales aisladas -Each codespace is hosted on its own newly-built virtual machine (VM). Two codespaces are never co-located on the same VM. +Cada codespace se hospeda en su máquina virtual (MV) recién creada. Dos codespaces jamás podrán ubicase en la misma MV. -Every time you restart a codespace, it's deployed to a new VM with the latest available security updates. +Cada vez que reinicias un codespace, este se lanza en una MV nueva con las actualizaciones más recientes de seguridad disponibles. -#### Isolated networking +#### Conexiones aisladas -Each codespace has its own isolated virtual network. We use firewalls to block incoming connections from the internet and to prevent codespaces from communicating with each other on internal networks. By default, codespaces are allowed to make outbound connections to the internet. +Cada codespace tiene su propia red virtual aislada. Utilizamos cortafuegos para bloquear las conexiones entrantes de la internet y para prevenir que los codespaces se comuniquen entre sí en redes internas. Predeterminadamente, se permite que los codespaces hagan conexiones salientes a la internet. ### Autenticación -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 %}. +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 %}. -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. +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. -The token's scope will vary depending on the access you have to the repository where the codespace was created: +El alcance del token variará dependiendo del tipo de acceso que tengas en el repositorio en donde se creó el codespace: -- **If you have write access to the repository**: The token will be scoped for read/write access to the repository. -- **If you only have read access to the repository**: The token will only allow the code to be cloned from the source repository. If you attempt to push to a private repo where you only have read access, {% data variables.product.prodname_codespaces %} will prompt you to create a personal fork of the repository. The token will then be updated to have read/write access to the new personal fork. -- **If you've enabled your codespace to access other repositories**: When a codespace has been granted [access to other repositories](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces), any codespace created from that repository will have read/write tokens scoped to the source repository. In addition, the tokens will also receive read access to other repositories indicated by the user or organization. +- **Si tienes acceso de escritura en el repositorio**: Se dará al token un alcance de acceso de lectura/escritura a este. +- **So solo tienes acceso de lectura al repositorio**: El token solo permitirá que el código se clone desde el repositorio origen. Si intentas subir información a un repositorio privado en donde solo tengas acceso de lectura, {% data variables.product.prodname_codespaces %} te pedirá crear una bifurcación personal de este. El token entonces se actualizará para tener acceso de lectura/escritura a la bifurcación personal nueva. +- **Si habilitaste tu codespace para que acceda a otros repositorios**: Cuando se le otorga [acceso a otros repositorios](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces) a un codespace, cualquiera de ellos que se cree desde ese repositorio tendrá tokens de lectura/escritura con alcance del repositorio origen. Adicionalmente, los tokens también recibirán acceso de lectura para otros repositorios que indique el usuario u organización. -An organization's administrators specify which repositories should be considered trusted. An admin can [choose to trust](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces) none, all, or some of the organization's repositories. A codespace can't have greater permissions to access resources than the person who created it, even if the organization administrator has granted access to all users and all repositories. +Los administradores de una organización especifican qué repositorios deberían considerarse como confiables. Un administrador puede [elegir confiar en](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces) todos, ninguno o algunos de los repositorios de la organización. Un codespace no puede tener permisos de acceso a los recursos si son mayores que los de la persona que lo creó, incluso si el administrador de la organización otorgó acceso a todos los usuarios y a todos los repositorios. -### Codespace connections +### Conexiones de los codespaces -You can connect to your codespace using the TLS encrypted tunnel provided by the {% data variables.product.prodname_codespaces %} service. Only the creator of a codespace can connect to a codespace. Connections are authenticated with {% data variables.product.product_name %}. +Puedes conectar tu codespace utilizando el túnel cifrado de TLS que proporciona el servicio de {% data variables.product.prodname_codespaces %}. Solo el creador de un codespace puede conectarse a este. Las conexiones se autentican con {% data variables.product.product_name %}. -If you need to allow external access to services running on a codespace, you can enable port forwarding for private or public access. +Si necesitas permitir el acceso externo a los servicios que se ejecutan en un codespace, puedes habilitar el reenvío de puertos para acceso público o privado. -### Port forwarding +### Reenvío de puertos -If you need to connect to a service (such as a development web server) running within your codespace, you can configure port forwarding to make the service available on the internet. +Si necesitas conectarte a un servicio (tal como un servidor web de desarrollo) que se ejecute en tu codespace, puedes configurar el reenvío de puertos para hacer que el servicio esté disponible en la internet. -**Privately forwarded ports**: Are accessible on the internet, but only the codespace creator can access them, after authenticating to {% data variables.product.product_name %}. +**Puertos reenviados de forma privada**: Son accesibles mediante el internet, pero solo el creador del codespace puede acceder a ellos después de autenticarse en {% data variables.product.product_name %}. -**Publicly forwarded ports**: Are accessible on the internet, and anyone on the internet can access them. No authentication is needed to access public forwarded ports. +**Puertos reenviados de forma pública**: Se puede acceder a ellos desde internet y todos pueden acceder a ellos. No se necesita autenticación para acceder a los puertos públicos reenviados. -All forwarded ports are private by default, which means that you will need to authenticate before you can access the port. Access to a codespace's private forwarded ports is controlled by authentication cookies with a 3-hour expiry period. When the cookie expires, you will need to reauthenticate. +Todos los puertos reenviados son privados predeterminadamente, lo cual significa que necesitarás autenticarte antes de poder acceder al puerto. El acceso a los puertos privados reenviados de un codespace se controla mediante cookies de autenticación con un periodo de vencimiento de 3 horas. Cuando la cookie venza, necesitarás volver a autenticarte. -A public forwarded port will automatically revert back to private when you remove and re-add the port, or if you restart the codespace. +Un puerto público renviado se revertirá automáticamente a privado cuando elimines y vuelvas a agregar dicho puerto o si reinicias el codespace. -You can use the "Ports" panel to configure a port for public or private access, and can stop port forwarding when it's no longer required. For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)." +Puedes utilizar el panel de "Puertos" para configurar uno de ellos para su acceso público o privado y puedes detener el reenvío de puertos cuando ya no sea necesario. Para obtener más información, consulta la sección "[Reenviar puertos en tu codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)". -## Good security practices for your codespaces +## Buenas prácticas de seguridad para tus codespaces -Codespaces are designed to be security hardened by default. To help maintain this posture, we recommend that you follow good security practices during your development procedures: +Los codespaces se diseñan para estar fortalecidos en seguridad predeterminadamente. Para ayudar a mantener esta postura, te recomendamos que sigas las buenas prácticas de seguridad durante tus procedimientos de desarrollo: -- As with any development tool, remember that you should only open and work within repositories you know and trust. -- Before you add new dependencies to the codespace, check whether they are well-maintained, and if they release updates to fix any security vulnerabilities found in their code. +- Como con cualquier herramienta de desarrollo, recuerda que solo debes intentar abrir y trabajar en repositorios que conoces y confías. +- Antes de agregar cualquier dependencia nueva al codespace, revisa si se mantienen bien y si lanzan actualizaciones para arreglar cualquier vulnerabilidad de seguridad que se encuentre en su código. -### Using secrets to access sensitive information +### Utilizar secretos para acceder a la información sensible -Always use encrypted secrets when you want to use sensitive information (such as access tokens) in a codespace. You can access your secrets as environment variables in the codespace, including from the terminal. For example, you can launch a terminal within your codespace and use `echo $SECRET_NAME` to see the value of a secret. +Utiliza siempre secretos cifrados cuando quieras utilizar información sensible (tal como tokens de acceso) en un codespace. Puedes acceder a tus secretos como variables de ambiente en el codespace, incluso desde la terminal. Por ejemplo, puedes lanzar una terminal dentro de tu codespace y utilizar `echo $SECRET_NAME` para ver el valor del secreto. -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. +Los valores del secreto se copian a las variables de ambiente cada que el codespace se reanuda o se crea, así que, si actualizas un valor secreto mientras el codespace se ejecuta, necesitarás suspender y reanudar para para tomar el valor actualziado. -For more information on secrets, see: -- "[Managing encrypted secrets for your 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)" +Para obtener más información sobre los secretos, consulta: +- "[Administrar los secretos cifrados para tus codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)" +- "[Administrar los secretos cifrados para tu repositorio y organización para los 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 +### Trabajar con las contribuciones y repositorios de otros -When you create a codespace from a PR branch from a fork, the token in the codespace will vary depending on whether the repository is public or private: -- For a private repository, the codespace is granted access to both the fork and parent. -- For a public repository, the codespace will only have access to the fork and opening PRs on the parent. +Cuando creas un codespace desde una rama de solicitud de cambios desde una bifurcación, el token en el codespace variará dependiendo de si el repositorio es público o privado: +- En el caso de un repositorio privado, el codespace obtiene acceso tanto a la bifurcación como al padre. +- En el caso de un repositorio público, el codespace solo tendrá acceso a la bifurcación y a abrir solicitudes de cambios en el padre. -### Additional good practices +### Buenas prácticas adicionales -There are some additional good practices and risks that you should be aware of when using {% data variables.product.prodname_codespaces %}. +Existen algunas buenas prácticas adicionales y riesgos de los cuales debes estar consciente cuando utilices los {% data variables.product.prodname_codespaces %}. -#### Understanding a repository's devcontainer.json file +#### Entender el archivo de devcontainer.json de un repositorio -When creating a codespace, the [devcontainer.json](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) is parsed and applied from the source repo, if one exists. The devcontainer contains powerful features, such as installing third-party extensions and running arbitrary code through a supplied `postCreateCommand`. +Cuando creas un codespace, el [devcontainer.json](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) se interpreta y aplica desde el repositorio fuente, en caso de que exista. El devcontainer contiene características poderosas, tales como instalar extensiones de terceros y ejecutar código arbitrario a través de un `postCreateCommand` suministrado. -#### Granting access through features +#### Otorgar acceso a través de características -Certain development features can potentially add risk to your environment. For example, commit signing, secrets injected into environment variables, authenticated registry access, and packages access can all present potential security issues. We recommend that you only grant access to those who need it and adopt a policy of being as restrictive as possible. +Ciertas características de desarrollo pueden agregar riesgos a tu ambiente potencialmente. Por ejemplo, el firmar confirmaciones, inyectar secretos en las variables de ambiente, tener acceso autenticado al registro y acceder a los paquetes pueden representar problemas potenciales de seguridad. Te recomendamos que solo otorgues acceso a aquellos que lo necesiten y que adoptes una política de ser tan restrictivo como sea posible. -#### Using extensions +#### Utilizar extensiones -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. +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. diff --git a/translations/es-ES/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md b/translations/es-ES/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md index 3b07012fd9..2c7d0299cb 100644 --- a/translations/es-ES/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md +++ b/translations/es-ES/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md @@ -1,6 +1,6 @@ --- -title: Understanding billing for Codespaces -intro: 'Learn how your {% data variables.product.prodname_codespaces %} usage is billed.' +title: Entender la facturación para los Codespaces +intro: 'Aprende cómo se factura tu uso de {% data variables.product.prodname_codespaces %}.' versions: fpt: '*' redirect_from: @@ -12,44 +12,44 @@ topics: - Codespaces - Billing product: '{% data reusables.gated-features.codespaces %}' -shortTitle: Understanding billing +shortTitle: Entender la facturación --- -This article explains how billing works for your codespaces, and explains how your organization's billing manager can help. +Este artículo te explica cómo funciona la facturación para tus codespaces y cómo el gerente de facturación de tu empresa puede ayudar. -## Getting access to {% data variables.product.prodname_codespaces %} +## Obtener acceso a {% data variables.product.prodname_codespaces %} -Your organization's administrator might limit {% data variables.product.prodname_codespaces %} usage to only specific user accounts. To get access, you will need to contact your billing manager. For more information, see "[Managing access and security for your codespaces](/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces)." +Tu administrador de organización podría limitar el uso de los {% data variables.product.prodname_codespaces %} a solo algunas cuentas de usuario específicas. Para obtener acceso, necesitarás contactar a tu gerente de facturación. Para obtener más información, consulta la sección "[Administrar el acceso y la seguridad para tus codespaces](/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces)". -## How much it costs to use {% data variables.product.prodname_codespaces %} +## Cuánto cuesta utilizar {% data variables.product.prodname_codespaces %} -To see the pricing for {% data variables.product.prodname_codespaces %} usage, see "[{% data variables.product.prodname_codespaces %} pricing](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)." +Para ver los precios de uso de {% data variables.product.prodname_codespaces %}, consulta la sección de "[Precios de {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)". -## How your codespace usage is billed +## Cómo se factura tu uso de codespaces -Your codespace is billed for its compute minutes and for the amount of storage it uses on disk. +Tu codespace se cobra de acuerdo con sus minutos de cálculo y con la cantidad de almacenamiento que utiliza en disco. -### Understanding what compute minutes are -Your codespace is billed for the number of minutes that it's active. If your codespaces window is left idle for 30 minutes, it will automatically shutdown, and compute billing for the codespace will end until you start the codespace again. +### Entender qué son los minutos de cálculo +Tu codespace se cobra de acuerdo con la cantidad de minutos durante los cuales está activo. Si tu ventana de codespaces está inactiva durante 30 minutos, se cerrará automáticamente y la facturación por cálculo terminará hasta que lo inicies nuevamente. -### Understanding how codespace storage is billed -For {% data variables.product.prodname_codespaces %}, storage is defined to include any files relating to your codespace, such as the cloned repository, configuration files, and extensions, among others. This storage is billed while your codespace is shutdown. The storage billing for a codespace ends when you manually delete it from https://github.com/codespaces. +### Entender cómo se factura el almacenamiento de un codespace +Para los {% data variables.product.prodname_codespaces %}, el almacenamiento se define para incluir cualquier archivo que se relacione con tu codespace, tal como el repositorio clonado, los archivos de configuración y las extensiones, entre otros. Este almacenamiento se factura mientras tu codespace está cerrado. La facturación de almacenamiento de un codespace termina cuando lo borras manualmente de https://github.com/codespaces. -## How spending limits work +## Cómo funcionan los límites de gastos -Before your organization can use {% data variables.product.prodname_codespaces %}, your billing manager will need to set a spending limit. For more information, see "[Managing spending limits for {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)." +Antes de que tu organización pueda utilizar los {% data variables.product.prodname_codespaces %}, tu gerente de facturación necesitará configurar un límite de gastos. Para obtener más información, consulta la sección "[Administrar los límites de gastos para los {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)". -## Exporting changes when you have reached your spending limit +## Exportar cambios cuando llegaste a tu límite de gastos {% data reusables.codespaces.exporting-changes %} -## Checking your current usage and limits -If you need to check your current usage or spending limit, contact your organization's billing manager. For more information, see "[Viewing your Codespaces usage](/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage)." +## Verificar tu uso y límites actuales +Si necesitas verificar tu uso o límite de gastos actuales, contacta al gerente de facturación de tu organización. Para obtener más información, consulta la sección "[Ver el uso de tus Codespaces](/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage)". -## Codespaces can be automatically deleted +## Los codespaces pueden borrarse automáticamente -Your codespace will be automatically deleted when you are removed from an organization or repository. +Tu codespace se borrará automáticamente cuando lo elimines de un repositorio u organización. -## Deleting your unused codespaces +## Borrar tus codespaces sin utilizar -You can manually delete your codespaces in https://github.com/codespaces and from within {% data variables.product.prodname_vscode %}. To reduce the size of a codespace, you can manually delete files using the terminal or from within {% data variables.product.prodname_vscode %}. +Puedes borrar tus codespaces manualmente en https://github.com/codespaces y desde dentro de {% data variables.product.prodname_vscode %}. Para reducir el tamaño de un codespace, puedes borrar los archivos manualmente utilizando la terminal o desde dentro de {% data variables.product.prodname_vscode %}. diff --git a/translations/es-ES/content/codespaces/codespaces-reference/using-the-command-palette-in-codespaces.md b/translations/es-ES/content/codespaces/codespaces-reference/using-the-command-palette-in-codespaces.md index 77b5390567..b56cb1038b 100644 --- a/translations/es-ES/content/codespaces/codespaces-reference/using-the-command-palette-in-codespaces.md +++ b/translations/es-ES/content/codespaces/codespaces-reference/using-the-command-palette-in-codespaces.md @@ -35,7 +35,7 @@ Para ver a todos los comandos relacionados con los {% data variables.product.pro ### Suspender o detener un codespace -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. +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 paleta de comandos y luego comienza a teclear "stop". Selecciona **Codespaces: Detener el codespace actual**. diff --git a/translations/es-ES/content/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project.md b/translations/es-ES/content/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project.md index 187b9da916..32e5177bc7 100644 --- a/translations/es-ES/content/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project.md +++ b/translations/es-ES/content/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project.md @@ -21,7 +21,7 @@ shortTitle: Configura tu proyecto ## Acerca de los contenedores dev -Un contenedor de desarrollo o contenedor dev es el ambiente que utilizan los {% data variables.product.prodname_codespaces %} para proporcionar las herramientas y tiempos de ejecución que necesita tu proyecto para su desarrollo. When working with a dev container in {% data variables.product.prodname_codespaces %} you can either [use the default configuration](#using-the-default-configuration), [use a predefined configuration](#using-a-predefined-container-configuration), or [create your own configuration](#creating-a-custom-codespace-configuration). La opción que elijas dependerá de las herramientas, tiempos de ejecución, dependencias y flujos de trabajo que el usuario pudiese necesitar para tener éxito en tu proyecto. +Un contenedor de desarrollo o contenedor dev es el ambiente que utilizan los {% data variables.product.prodname_codespaces %} para proporcionar las herramientas y tiempos de ejecución que necesita tu proyecto para su desarrollo. Cuando trabajas con un contenedor de desarrollo en {% data variables.product.prodname_codespaces %} puedes ya sea [utilizar la configuración predeterminada](#using-the-default-configuration), [utilizar una configuración predeterminada](#using-a-predefined-container-configuration) o [crear tu propia configuración](#creating-a-custom-codespace-configuration). La opción que elijas dependerá de las herramientas, tiempos de ejecución, dependencias y flujos de trabajo que el usuario pudiese necesitar para tener éxito en tu proyecto. {% data variables.product.prodname_codespaces %} permite la personalización por proyecto y por rama con un archivo `devcontainer.json`. Este archivo de configuración determina el ambiente de cada codespace nuevo que cualquier persona cree en tu repositorio definiendo un contenedor de desarrollo que puede incluir marcos de trabajo, herramientas, extensiones y reenvío de puertos. También puede utilizarse un Dockerfile junto con el archivo `devcontainer.json` en la carpeta `.devcontainer` para definir todo lo que se necesita para crear una imagen de contenedor. diff --git a/translations/es-ES/content/codespaces/customizing-your-codespace/index.md b/translations/es-ES/content/codespaces/customizing-your-codespace/index.md index 2652644044..7bd2cd9cb6 100644 --- a/translations/es-ES/content/codespaces/customizing-your-codespace/index.md +++ b/translations/es-ES/content/codespaces/customizing-your-codespace/index.md @@ -1,6 +1,6 @@ --- -title: Customizing your codespace -intro: '{% data variables.product.prodname_codespaces %} es un ambiente dedicado para ti. You can configure your repositories with a dev container to define their default Codespaces environment, and personalize your development experience across all of your codespaces with dotfiles and Settings Sync.' +title: Personalizar tu codespace +intro: '{% data variables.product.prodname_codespaces %} es un ambiente dedicado para ti. Puedes configurar tus repositorios con un contenedor de dev para definir su ambiente predeterminado de Codespaces y personalizar tu experiencia de desarrollo a lo largo de tus codespaces con dotfiles y sincronización de ajustes.' product: '{% data reusables.gated-features.codespaces %}' versions: free-pro-team: '*' diff --git a/translations/es-ES/content/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account.md b/translations/es-ES/content/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account.md index dfc695776d..4441592048 100644 --- a/translations/es-ES/content/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account.md +++ b/translations/es-ES/content/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account.md @@ -32,7 +32,7 @@ Los mantenendores de proyecto también pueden definir una configuración predete La configuración de ajustes te permite compartir configuraciones tales como configuraciones, atajos de teclado, fragmentos de código, extensiones y estados de IU entre máquinas e instancias de {% data variables.product.prodname_vscode %}. -To enable Settings Sync, in the bottom-left corner of the Activity Bar, select {% octicon "gear" aria-label="The gear icon" %} and click **Turn on Settings Sync…**. From the dialog, select which settings you'd like to sync. +Para habilitar la Sincronización de Ajustes, en la esquina inferior izquierda de la Barra de Actividad, selecciona {% octicon "gear" aria-label="The gear icon" %} y haz clic en **Encender la Sincronización de Ajustes…**. Desde el diálogo, selecciona qué ajustes te gustaría sincronizar. ![La opción de sincronización de ajustes en el menú de administración](/assets/images/help/codespaces/codespaces-manage-settings-sync.png) @@ -67,31 +67,31 @@ Cualquier cambio a tu repositorio `dotfiles` se aplicará únicamente a cada cod {% endnote %} -### Enabling your dotfiles repository for {% data variables.product.prodname_codespaces %} +### Habilitar tu repositorio de dotfiles para {% data variables.product.prodname_codespaces %} -You can use your public `dotfiles` repository to personalize your {% data variables.product.prodname_codespaces %} environment. Once you set up that repository, you can add your scripts, preferences, and configurations to it. You then need to enable your dotfiles from your personal {% data variables.product.prodname_codespaces %} settings page. +Puedes utilizar tu repositorio público de `dotfiles` para personalizar tu ambiente de {% data variables.product.prodname_codespaces %}. Una vez que configuras el repositorio, puedes agregar tus scripts, preferencias y configuraciones a él. Después, necesitarás habilitar tus dotfiles desde tu página personal de ajustes de {% data variables.product.prodname_codespaces %}. {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.codespaces-tab %} -1. Under "Dotfiles", select "Automatically install dotfiles" so that {% data variables.product.prodname_codespaces %} automatically installs your dotfiles into every new codespace you create. ![Installing dotfiles](/assets/images/help/codespaces/install-dotfiles.png) +1. Debajo de "Dotfiles", selecciona "Instalar dotfiles automáticamente" para que {% data variables.product.prodname_codespaces %} instale tus dotfiles automáticamente en cada codespace nuevo que crees. ![Instalar dotfiles](/assets/images/help/codespaces/install-dotfiles.png) {% note %} - **Note:** This option is only available if you've created a public `dotfiles` repository for your user account. + **Nota:** Esta opción solo se encuentra disponible si creaste un repositorio público de `dotfiles` para tu cuenta de usuario. {% endnote %} -You can add further script, preferences, configuration files to your dotfiles repository or edit existing files whenever you want. Changes to settings will only be picked up by new codespaces. +Puedes agregar más scripts, preferencias o archivos de configuración a tu repositorio de dotfiles o editar los archivos existentes cuando lo desees. Solo los codespaces nuevos tomarán los cambios a los ajustes. -## Other available settings +## Otros ajustes disponibles -You can also personalize {% data variables.product.prodname_codespaces %} using additional [Codespaces settings](https://github.com/settings/codespaces): +También puedes personalizar los {% data variables.product.prodname_codespaces %} utilizando [Ajustes de codespaces](https://github.com/settings/codespaces) adicionales: -- To set your default region, see "[Setting your default region for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces)." -- To set your editor, see "[Setting your default editor for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/setting-your-default-editor-for-codespaces)." -- To add encrypted secrets, see "[Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)." -- To enable GPG verification, see "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)." -- To allow your codespaces to access other repositories, see "[Managing access and security for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)." +- Para configurar tu región predeterminada, consulta la sección "[Configurar tu región predeterminada para los {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces)". +- Para configurar tu editor, consulta la sección "[Configurar tu editor predeterminado para los {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/setting-your-default-editor-for-codespaces)". +- Para agregar secretos cifrados, consulta la sección "[Administrar secretos cifrados para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)". +- Para habilitar la verificación de GPG, consulta la sección "[Administrar la verificación de GPG para los {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)". +- Para permitir que tus codespaces accedan a otros repositorios, consulta la sección "[Administrar el acceso y la seguridad de los {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)". ## Leer más diff --git a/translations/es-ES/content/codespaces/customizing-your-codespace/prebuilding-codespaces-for-your-project.md b/translations/es-ES/content/codespaces/customizing-your-codespace/prebuilding-codespaces-for-your-project.md index d5a23acd64..329936ecea 100644 --- a/translations/es-ES/content/codespaces/customizing-your-codespace/prebuilding-codespaces-for-your-project.md +++ b/translations/es-ES/content/codespaces/customizing-your-codespace/prebuilding-codespaces-for-your-project.md @@ -1,6 +1,6 @@ --- -title: Prebuilding Codespaces for your project -intro: You can configure your project to prebuild a codespace automatically each time you push a change to your repository. +title: Pre-compilar Codespaces para tu proyecto +intro: Puedes configurar tu proyecto para que pre-configure un codespace automáticamente cada que subes un cambio a tu repositorio. versions: fpt: '*' type: how_to @@ -9,17 +9,17 @@ topics: - Set up - Fundamentals product: '{% data reusables.gated-features.codespaces %}' -shortTitle: Prebuilding Codespaces +shortTitle: Pre-compilar los Codespaces --- {% note %} -**Note:** This feature is currently in private preview. +**Nota:** Esta característica actualmente se encuentra en vista previa. {% endnote %} -## About prebuilding a Codespace +## Acerca de pre-compilar un Codespace -Prebuilding your codespaces allows you to be more productive and access your codespace faster. This is because any source code, editor extensions, project dependencies, commands, or configurations have already been downloaded, installed, and applied before you begin your coding session. Once you push changes to your repository, {% data variables.product.prodname_codespaces %} automatically handles configuring the builds. +El Pre-compilar tu codespace te permite ser más productivo y acceder a tu codespace más rápido. Esto es porque cualquier tipo de código fuente, extensiones de editor, dependencias de proyecto, comandos o configuraciones ya se habrán descargado, instalad y aplicado antes de que comiences tu sesión de desarrollo. Una vez que subes los cambios a tu repositorio, {% data variables.product.prodname_codespaces %} maneja automáticamente la configuración de compilaciones. -The ability to prebuild Codespaces is currently in private preview. To get access to this feature, contact codespaces@github.com. +La capacidad de pre-compilar un Codespace actualmente se encuentra en vista previa privada. Para obtener acceso a esta característica, contacta a codespaces@github.com. diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/changing-the-machine-type-for-your-codespace.md b/translations/es-ES/content/codespaces/developing-in-codespaces/changing-the-machine-type-for-your-codespace.md index f36e0c9de9..712449be72 100644 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/changing-the-machine-type-for-your-codespace.md +++ b/translations/es-ES/content/codespaces/developing-in-codespaces/changing-the-machine-type-for-your-codespace.md @@ -1,7 +1,7 @@ --- -title: Changing the machine type for your codespace -shortTitle: Changing the machine type -intro: 'You can change the type of machine that''s running your codespace, so that you''re using resources appropriate for work you''re doing.' +title: Cambiar el tipo de máquina de tu codespace +shortTitle: Cambiar el tipo de máquina +intro: Puedes cambiar el tipo de máquina que está ejecutando tu codespace para que estés utilizando recursos adecuados para el trabajo que estás haciendo. product: '{% data reusables.gated-features.codespaces %}' versions: free-pro-team: '*' @@ -9,51 +9,51 @@ topics: - Codespaces --- -## About machine types +## Acerca de los tipos de máquina {% note %} -**Note:** You can only select or change the machine type if you are a member of an organization using {% data variables.product.prodname_codespaces %} and are creating a codespace on a repository owned by that organization. +**Nota:** Solo puedes seleccionar o cambiar el tipo de máquina si eres miembro de una organización que está utilizando {% data variables.product.prodname_codespaces %} y estás creando un codespace en un repositorio que pertenece a dicha organización. {% endnote %} {% data reusables.codespaces.codespaces-machine-types %} -You can choose a machine type either when you create a codespace or you can change the machine type at any time after you've created a codespace. +Puedes elegir un tipo de máquina, ya sea cuando creas un codespace o puedes cambiar el tipo de máquina en cualquier momento después de que lo hayas creado. -For information on choosing a machine type when you create a codespace, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)." For information on changing the machine type within {% data variables.product.prodname_vscode %}, see "[Using {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code#changing-the-machine-type-in-visual-studio-code)." +Para obtener más información sobre cómo elegir un tio de máquina cuando creas un codespace, consulta la sección "[Crear un codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)". Para obtener más información sobre cómo cambiar el tipo de máquina dentro de {% data variables.product.prodname_vscode %}, consulta la sección "[Utilizar los {% data variables.product.prodname_codespaces %} en {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code#changing-the-machine-type-in-visual-studio-code)". ## Cambiar el tipo de máquina en {% data variables.product.prodname_dotcom %} {% data reusables.codespaces.your-codespaces-procedure-step %} - The current machine type for each of your codespaces is displayed. + Se mostrará el tipo de máquina actual para cada uno de tus codespaces. - !['Your codespaces' list](/assets/images/help/codespaces/your-codespaces-list.png) + ![Lista de 'Tus codespaces'](/assets/images/help/codespaces/your-codespaces-list.png) -1. Click the ellipsis (**...**) to the right of the codespace you want to modify. -1. Click **Change machine type**. +1. Haz clic en los puntos suspensivos (**...**) a la derecha del codespace que quieras modificar. +1. Haz clic en **Cambiar tipo de máquina**. - !['Change machine type' menu option](/assets/images/help/codespaces/change-machine-type-menu-option.png) + ![Opción de menú 'Cambiar tipo de máquina'](/assets/images/help/codespaces/change-machine-type-menu-option.png) -1. Choose the required machine type. +1. Elige el tipo de máquina requerido. -2. Click **Update codespace**. +2. Haz clic en **Actualizar codespace**. - The change will take effect the next time your codespace restarts. + El cambio surtirá efecto la siguiente vez que reinicies tu codespace. -## Force an immediate update of a currently running codespace +## Forzar una actualización inmediata de un codespace que se está ejecutando actualmente -If you change the machine type of a codespace you are currently using, and you want to apply the changes immediately, you can force the codespace to restart. +Si cambias el tipo de máquina de un codespace que estés utilizando actualmente y quieres aplicar los cambios de inmediato, puedes forzar el codespace para que se reinicie. -1. At the bottom left of your codespace window, click **{% data variables.product.prodname_codespaces %}**. +1. En la parte inferior izquierda de tu ventana de codespace, haz clic en **{% data variables.product.prodname_codespaces %}**. - ![Click '{% data variables.product.prodname_codespaces %}'](/assets/images/help/codespaces/codespaces-button.png) + ![Hacer clic en '{% data variables.product.prodname_codespaces %}'](/assets/images/help/codespaces/codespaces-button.png) -1. From the options that are displayed at the top of the page select **Codespaces: Stop Current Codespace**. +1. Desde las opciones que se muestran en la parte superior de la página, selecciona **Codespaces: Detener el Codespace actual**. - !['Suspend Current Codespace' option](/assets/images/help/codespaces/suspend-current-codespace.png) + ![Opción 'Suspender codespace actual'](/assets/images/help/codespaces/suspend-current-codespace.png) -1. After the codespace is stopped, click **Restart codespace**. +1. Después de que se detenga el codespace, haz clic en **Restablecer codespace**. - ![Click 'Resume'](/assets/images/help/codespaces/resume-codespace.png) + ![Hacer clic en 'Reanudar'](/assets/images/help/codespaces/resume-codespace.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 ded53ce9c7..c1543732c4 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 @@ -22,42 +22,42 @@ Puedes crear un codespace ya sea en {% data variables.product.prodname_dotcom_th Los codespaces se asocian con una rama específica de un repositorio y este repositorio no puede estar vacío. {% data reusables.codespaces.concurrent-codespace-limit %} Para obtener más información, consulta la sección "[Borrar un codespace](/github/developing-online-with-codespaces/deleting-a-codespace)". -When you create a codespace, a number of steps happen to create and connect you to your development environment: +Cuando creas un codespace, se suscitan varios pasos para crear y conectarte a tu ambiente de desarrollo: -- Step 1: VM and storage are assigned to your codespace. -- Step 2: Container is created and your repository is cloned. -- Step 3: You can connect to the codespace. -- Step 4: Codespace continues with post-creation setup. +- Paso 1: se le asignan una MV y almacenamiento a tu codespace. +- Paso 2: Se crea el contenedor y se clona tu repositorio. +- Paso 3: Puedes conectarte al codespace. +- Paso 4: El codespace sigue con la configuración post-creación. -For more information on what happens when you create a codespace, see "[Deep Dive](/codespaces/getting-started/deep-dive)." +Para obtener más información sobre lo que sucede cuando creas un codespace, consulta la sección "[A profundidad](/codespaces/getting-started/deep-dive)". {% data reusables.codespaces.use-visual-studio-features %} {% data reusables.codespaces.you-can-see-all-your-codespaces %} -## Access to {% data variables.product.prodname_codespaces %} +## Acceso a los {% data variables.product.prodname_codespaces %} {% data reusables.codespaces.availability %} -When you have access to {% data variables.product.prodname_codespaces %}, you'll see a "Codespaces" tab within the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu when you view a repository. +Cuando tienes acceso a los {% data variables.product.prodname_codespaces %}, verás una pestaña de "Codespaces" dentro del menú desplegable de **{% octicon "code" aria-label="The code icon" %} Código** cuando ves un repositorio. -You'll have access to codespaces under the following conditions: +Tendrás acceso a los codespaces bajo las siguientes condiciones: -* You are a member of an organization that has enabled {% data variables.product.prodname_codespaces %} and set a spending limit. -* An organization owner has granted you access to {% data variables.product.prodname_codespaces %}. -* The repository is owned by the organization that has enabled {% data variables.product.prodname_codespaces %}. +* Eres un miembro de la organización que habilitó los {% data variables.product.prodname_codespaces %} y configuró un límite de gastos. +* Un propietario de la organización te proporcionó acceso a los {% data variables.product.prodname_codespaces %}. +* El repositorio le pertenece a la organización que habilitó los {% data variables.product.prodname_codespaces %}. {% note %} -**Note:** Individuals who have already joined the beta with their personal {% data variables.product.prodname_dotcom %} account will not lose access to {% data variables.product.prodname_codespaces %}, however {% data variables.product.prodname_codespaces %} for individuals will continue to remain in beta. +**Nota:** Los individuos que ya se hayan unido al beta con su cuenta personal de {% data variables.product.prodname_dotcom %} no perderán acceso a los {% data variables.product.prodname_codespaces %}, sin embargo, los {% data variables.product.prodname_codespaces %} para personas individuales seguirán en beta. {% endnote %} -Organization owners can allow all members of the organization to create codespaces, limit codespace creation to selected organization members, or disable codespace creation. For more information about managing access to codespaces within your organization, see "[Enable Codespaces for users in your organization](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization#enable-codespaces-for-users-in-your-organization)." +Los propietarios de las organizaciones pueden permitir que los miembros de la organización creen codespaces, limitar la creación de los codespaces para miembros selectos de la organización o inhabilitar la creación de codespaces. Para obtener información sobre cómo administrar el acceso a los codespaces dentro de tu organización, consulta la sección "[Habilitar los Codespaces para los usuarios de tu organización](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization#enable-codespaces-for-users-in-your-organization)". -Before {% data variables.product.prodname_codespaces %} can be used in an organization, an owner or billing manager must have set a spending limit. For more information, see "[About spending limits for Codespaces](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces#about-spending-limits-for-codespaces)." +Antes de que puedas utilizar {% data variables.product.prodname_codespaces %} en una organización, un propietario o gerente de facturación debe haber configurado un límite de gastos. Para obtener más información, consulta la sección "[Acerca de los límites de gastos para los Codespaces](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces#about-spending-limits-for-codespaces)". -If you would like to create a codespace for a repository owned by your personal account or another user, and you have permission to create repositories in an organization that has enabled {% data variables.product.prodname_codespaces %}, you can fork user-owned repositories to that organization and then create a codespace for the fork. +Si te gustaría crear un codespace para un repositorio que pertenezca a tu cuenta personal o a otro usuario y tienes permiso para crear repositorios en una organización que haya habilitado los {% data variables.product.prodname_codespaces %}, puedes bifurcar repositorios que pertenezcan a los usuarios de esta organización y luego crear un codespace para dicha bifurcación. ## Crear un codespace @@ -66,8 +66,8 @@ If you would like to create a codespace for a repository owned by your personal ![Menú desplegable de rama](/assets/images/help/codespaces/branch-drop-down.png) -3. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu, and in the **Codespaces** tab, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. +3. Debajo del nombre de repositorio, utiliza el menú desplegable de **Código {% octicon "code" aria-label="The code icon" %}** y, en la pestaña de **Codespaces**, haz clic en {% octicon "plus" aria-label="The plus icon" %} **Codespace nuevo**. ![Botón de codespace nuevo](/assets/images/help/codespaces/new-codespace-button.png) - If you are a member of an organization and are creating a codespace on a repository owned by that organization, you can select the option of a different machine type. From the dialog, choose a machine type and then click **Create codespace**. ![Machine type choice](/assets/images/help/codespaces/choose-custom-machine-type.png) + Si eres un miembro de una organización y estás creando un codespace en un repositorio que le pertenece a esta, puedes seleccionar la opción de un tipo de máquina diferente. Desde el diálogo, elige un tipo de máquina y luego haz clic en **Crear codespace**. ![Elección de tipo de máquina](/assets/images/help/codespaces/choose-custom-machine-type.png) diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/deleting-a-codespace.md b/translations/es-ES/content/codespaces/developing-in-codespaces/deleting-a-codespace.md index 64da674ab4..5a177c730a 100644 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/deleting-a-codespace.md +++ b/translations/es-ES/content/codespaces/developing-in-codespaces/deleting-a-codespace.md @@ -24,7 +24,7 @@ topics: {% endnote %} -1. Navigate to the "Your Codespaces" page at [github.com/codespaces](https://github.com/codespaces). +1. Navegar a la página de "Tus Codespaces" en [github.com/codespaces](https://github.com/codespaces). 2. A la derecha del codespace que quieres borrar, haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} y luego en **Borrar {% octicon "trash" aria-label="The trash icon" %}** ![Botón de borrar](/assets/images/help/codespaces/delete-codespace.png) 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 19c2d1317e..651beb3da6 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 @@ Para obtener más información sobre cómo utilizar {% data variables.product.pr {% data reusables.codespaces.connect-to-codespace-from-vscode %} -{% data reusables.codespaces.use-chrome %} For more information, see "[Troubleshooting Codespaces clients](/codespaces/troubleshooting/troubleshooting-codespaces-clients)." +{% data reusables.codespaces.use-chrome %} Para obtener más información, consulta la sección "[Solucionar problemas de los clientes de los Codespaces](/codespaces/troubleshooting/troubleshooting-codespaces-clients)". ### Personalizar tu codespace @@ -57,4 +57,4 @@ La paleta de comandos te permite acceder y administrar muchas características p 1. {% data reusables.codespaces.you-can-see-all-your-codespaces %} 2. Da clic en el nombre del codespace en el cual quieras desarrollar. ![Nombre del codespace](/assets/images/help/codespaces/click-name-codespace.png) -Alternatively, you can see any active codespaces for a repository by navigating to that repository and selecting **{% octicon "code" aria-label="The code icon" %} Code**. The drop-down menu will display all active codespaces for a repository. +Como alternativa, puedes ver cualquier codespace activo en un repositorio si navegas a dicho repositorio y seleccionnas **{% octicon "code" aria-label="The code icon" %} Código**. El menú desplegable mostrará todos los codespaces activos en un repositorio. diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md b/translations/es-ES/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md index 1339169985..4da81e7c50 100644 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md +++ b/translations/es-ES/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md @@ -44,7 +44,7 @@ Puedes etiquetar un puerto para hacerlo más fácil de identificar en una lista. ## Compartir un puerto -If you want to share a forwarded port with others, you need to make the port public. Después de que lo haces público, cualquiera con la URL del puerto puede ver la aplicación que se ejecuta sin necesidad de autenticarse. +Si quieres compartir un puerto reenviado con otros, necesitas hacerlo público. Después de que lo haces público, cualquiera con la URL del puerto puede ver la aplicación que se ejecuta sin necesidad de autenticarse. {% data reusables.codespaces.navigate-to-ports-tab %} 1. Haz clic derecho en el puerto que quieres compartir y luego en **Hacer público**. ![Opción para hacer el puerto público en el menú de clic derecho](/assets/images/help/codespaces/make-public-option.png) diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/index.md b/translations/es-ES/content/codespaces/developing-in-codespaces/index.md index 3c5cba8a15..5fa50231cf 100644 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/index.md +++ b/translations/es-ES/content/codespaces/developing-in-codespaces/index.md @@ -15,6 +15,5 @@ children: - /forwarding-ports-in-your-codespace - /changing-the-machine-type-for-your-codespace - /using-codespaces-in-visual-studio-code - - /web-based-editor --- diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests.md b/translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests.md index 84f606a8b0..c63510e42c 100644 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests.md +++ b/translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests.md @@ -1,7 +1,7 @@ --- -title: Using Codespaces for pull requests +title: Utilizar los Codespaces para solicitudes de cambios shortTitle: Solicitudes de cambios -intro: 'You can use {% data variables.product.prodname_codespaces %} in your development workflow to create pull requests, review pull requests, and address review comments.' +intro: 'Puedes utilizar los {% data variables.product.prodname_codespaces %} en tu flujo de trabajo de desarrollo para crear las solicitudes de cambios, revisar solicitudes de cambios y dirigir comentarios de revisión.' product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' @@ -14,28 +14,28 @@ topics: ## Acerca de las solicitudes de extracción en {% data variables.product.prodname_codespaces %} -{% data variables.product.prodname_codespaces %} provides you with many of the capabilities you might need to work with pull requests: +{% data variables.product.prodname_codespaces %} te proporciona muchas de las capacidades que podrías necesitar para trabajar con las solicitudes de cambios: -- [Create a pull request](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#raising-a-pull-request) - Using either the Terminal and Git commands or the Source Control view, you can create pull requests just as you would on {% data variables.product.prodname_dotcom_the_website %}. If the repository uses a pull request template, you'll be able to use this within the Source Control view. -- [Open a pull request](#opening-a-pull-request-in-codespaces) – You can open an existing pull request in a codespace, provided you have codespace access to the branch that is being merged in. -- [Review a pull request](#reviewing-a-pull-request-in-codespaces) - Once you have opened a pull request in a codespace, you can use the "GitHub Pull Request" view to add review comments and approve pull requests. You can also use {% data variables.product.prodname_codespaces %} to [view review comments](#view-comments-from-a-review-in-codespaces). +- [Crear una solicitud de cambios](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#raising-a-pull-request) - Si utilizas ya sea la Terminal y los comandos de Git o la vista de Control de Código Fuente, puedes crear solicitudes de cambios tal como lo harías en {% data variables.product.prodname_dotcom_the_website %}. Si el repositorio utiliza una plantilla de solicitud de cambios, podrás utilizarla dentro de la vista de Control de Código Fuente. +- [Abre una solicitud de cambios](#opening-a-pull-request-in-codespaces) – Puedes abrir una solicitud de cambios existente en un codespace, tomando en cuenta que tengas acceso al codespace de la rama que se está fusionando. +- [Revisar una solicitud de cambios](#reviewing-a-pull-request-in-codespaces) - Una vez que hayas abierto una solicitud de cambios en un codespace, puedes utilizar la vista de "Solicitud de Cambios de GitHub" para agregar comentarios de revisión y aprobar las solicitudes de cambios. También puedes utilizar los {% data variables.product.prodname_codespaces %} para [ver los comentarios de revisión](#view-comments-from-a-review-in-codespaces). -## Opening a pull request in {% data variables.product.prodname_codespaces %} +## Abrir una solicitud de cambios en {% data variables.product.prodname_codespaces %} {% data reusables.repositories.sidebar-pr %} -2. In the list of pull requests, click the pull request you'd like to open in {% data variables.product.prodname_codespaces %}. -3. On the right-hand side of your screen, click **{% octicon "code" aria-label="The code icon" %} Code**. -4. From the {% data variables.product.prodname_codespaces %} tab, click **New codespace**. ![Option to open PR in a codespace](/assets/images/help/codespaces/open-with-codespaces-pr.png) +2. En la lista de solicitudes de cambios, haz clic en aquella que quieras abrir en {% data variables.product.prodname_codespaces %}. +3. A la derecha de tu pantalla, haz clic en **{% octicon "code" aria-label="The code icon" %} Código**. +4. Desde la pestaña de {% data variables.product.prodname_codespaces %}, haz clic en **Codespace nuevo**. ![Opción para abrir una solicitud de cambios en un codespace](/assets/images/help/codespaces/open-with-codespaces-pr.png) -## Reviewing a pull request in {% data variables.product.prodname_codespaces %} +## Revisar una solicitud de cambios en {% data variables.product.prodname_codespaces %} {% data reusables.codespaces.review-pr %} -For more information on reviewing a pull request, see "[Reviewing proposed changes in a pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)." +Para obtener más información sobre cómo revisar una solicitud de cambios, consulta la sección "[Revisar los cambios propuestos en una solicitud de cambios](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)". -## View comments from a review in {% data variables.product.prodname_codespaces %} +## Ver los comentarios de una revisión en {% data variables.product.prodname_codespaces %} -Once you have received feedback on a pull request, you can [open it in a codespace](#opening-a-pull-request-in-codespaces) to see the [review comments](#reviewing-a-pull-request-in-codespaces). From there you can respond to comments, add reactions, or dismiss the review. +Una vez que hayas recibido retroalimentación en una solicitud de cambios, puedes [Abrirla en un codespace](#opening-a-pull-request-in-codespaces) para ver los [comentarios de revisión](#reviewing-a-pull-request-in-codespaces). Desde ahí, puedes responder a los comentarios, agregar reacciones o descartar la revisión. - ![Option to open PR in a codespace](/assets/images/help/codespaces/incorporating-codespaces.png) + ![Opción para abrir una solicitud de cambios en un codespace](/assets/images/help/codespaces/incorporating-codespaces.png) 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 5e528e2e7a..07a22a37ec 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 @@ -68,7 +68,7 @@ Puedes cambiar el tipo de máquina de tu codespace en cualquier momento. 1. En {% data variables.product.prodname_vscode %}, abre la paleta de comandos (`shift command P` / `shift control P`). 2. Busca y selecciona "Codespaces: Cambiar mi tipo de máquina". ![Buscar una rama para crear un {% data variables.product.prodname_codespaces %} nuevo](/assets/images/help/codespaces/vscode-change-machine-type-option.png) 3. Haz clic en el codespace que quieras cambiar. ![Buscar una rama para crear un {% data variables.product.prodname_codespaces %} nuevo](/assets/images/help/codespaces/vscode-change-machine-choose-repo.png) -4. Choose the machine type you want to use. +4. Elige el tipo de máquina que quieres utilizar. Si el codespace se está ejecutando actualmente, se mostrará un mensaje que pregunta si te gustaría reiniciar y reconectarte con tu codespace ahora. Haz clic en **Sí** en caso de que quieras cambiar el tipo de máquina que se utiliza para este codespace inmediatamente. Si haces clic en **No** o si el codespace no se está ejecutando actualmente, el cambio se reflejará la próxima vez que este se reinicie. 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 10bd8d8d9e..66ee90fc87 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 @@ -30,9 +30,7 @@ Un flujo de trabajo típico para actualizar un archivo utilizando {% data variab ## Crear o cambiar de rama -1. Si la rama actual no se muestra en la barra de estado, en la parte inferior de tu codespace, haz clic derecho en la barra de estado y selecciona **Control de código fuente**. -1. Haz clic en el nombre de rama en la barra de estado. ![La rama en la barra de estado](/assets/images/help/codespaces/branch-in-status-bar.png) -1. En el menú desplegable, haz clic en la rama a la que quieras cambiar o ingresa el nombre de una rama nueva y haz clic en **Crear rama nueva**. ![Elige del menú de la rama](/assets/images/help/codespaces/create-new-branch.png) +{% data reusables.codespaces.create-or-switch-branch %} {% tip %} @@ -48,7 +46,7 @@ Puedes extraer cambios del repositorio remoto hacia tu codespace en cualquier mo 1. En la parte superior de la barra lateral, haz clic en los puntos suspensivos (**...**). ![Botón de puntos suspensivos para las acciones de "más" y "ver"](/assets/images/help/codespaces/source-control-ellipsis-button.png) 1. En el menú desplegable, haz clic en **Extraer**. -If the dev container configuration has been changed since you created the codespace, you can apply the changes by rebuilding the container for the codespace. Para obtener más información, consulta la sección "[Configurar Codespaces para tu proyecto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)". +Si el la configuración del contenedor dev cambió desde que creaste el codespace, puedes aplicar los cambios si recompilas el contenedor para el codespace. Para obtener más información, consulta la sección "[Configurar Codespaces para tu proyecto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)". ## Configurar tu codespace para que recupere los cambios nuevos automáticamente @@ -64,16 +62,11 @@ Si la operación de búsqueda detecta cambios nuevos en el repositorio remoto, v ## Configramr tus cambios -{% data reusables.codespaces.source-control-display-dark %} -1. Para probar tus cambios, haz clic en **+** junto al archivo que cambiaste o junto a **Cambios** si cambiaste archivos múltiples y quieres probarlos todos. ![Barra lateral de control de código fuente con el botón de preparación resaltado](/assets/images/help/codespaces/codespaces-commit-stage.png) -1. Teclea un mensaje de confirmación que describa el cambio que hiciste. ![Barra de control de código fuente con un mensaje de confirmación](/assets/images/help/codespaces/codespaces-commit-commit-message.png) -1. Para confirmar tus cambios planeados, haz clic en la marca de verificación en la parte superior de la barra lateral del control de código fuente. ![Haz clic en el icono de verificación](/assets/images/help/codespaces/codespaces-commit-checkmark-icon.png) +{% data reusables.codespaces.source-control-commit-changes %} ## Levantar una solicitud de cambios -1. Después de haber confirmado los cambios en tu copia local del repositorio, haz clic en el icono de **Crear solicitud de cambios**. ![Barra lateral de control de código fuente con el botón de preparación resaltado](/assets/images/help/codespaces/codespaces-commit-pr-button.png) -1. Verifica que el repositorio y la rama local desde la que estás haciendo la fusión y la rama y repositorio remotos hacia los que estés haciendo la fusión sean correctos. Después, asigna un nombre y descripción a la solicitud de cambios. ![Barra lateral de control de código fuente con el botón de preparación resaltado](/assets/images/help/codespaces/codespaces-commit-pr.png) -1. Da clic en **Crear**. +{% data reusables.codespaces.source-control-pull-request %} ## Subir cambios a tu repositorio remoto 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 046c0ef2d4..f53012f810 100644 --- a/translations/es-ES/content/codespaces/getting-started/deep-dive.md +++ b/translations/es-ES/content/codespaces/getting-started/deep-dive.md @@ -1,5 +1,5 @@ --- -title: Deep dive into Codespaces +title: Conoce los Codespaces a profundidad intro: 'Comprender cómo funciona {% data variables.product.prodname_codespaces %}.' allowTitleToDifferFromFilename: true product: '{% data reusables.gated-features.codespaces %}' @@ -10,95 +10,95 @@ topics: - Codespaces --- -{% data variables.product.prodname_codespaces %} is an instant, cloud-based development environment that uses a container to provide you with common languages, tools, and utilities for development. {% data variables.product.prodname_codespaces %} is also configurable, allowing you to create a customized development environment for your project. By configuring a custom development environment for your project, you can have a repeatable codespace configuration for all users of your project. +{% data variables.product.prodname_codespaces %} es un ambiente de desarrollo basado en la nube e instantáneo que utiliza un contenedor para proporcionarte lenguajes comunes, herramientas y utilidades para el desarrollo. {% data variables.product.prodname_codespaces %} también es configurable, lo cual te permite crear un ambiente de desarrollo personalizado para tu proyecto. Al configurar un ambiente de desarrollo personalizado para tu proyecto, puedes tener una configuración de codespace repetible para todos los usuarios de dicho proyecto. ## Crea tu codespace -There are a number of entry points to create a codespace. +Hay varios puntos de entrada para crear un codespace. -- From your repository for new feature work. -- From an open pull request to explore work-in-progress. -- From a commit in the repository's history to investigate a bug at a specific point in time. -- From {% data variables.product.prodname_vscode %}. +- Desde tu repositorio para trabajo destacado nuevo. +- Desde una solicitud de cambios abierta para explorar el trabajo en curso. +- Desde una confirmación en el historial del repositorio para investigar un error en un punto específico del tiempo. +- Desde {% data variables.product.prodname_vscode %}. -Your codespace can be ephemeral if you need to test something or you can return to the same codespace to work on long-running feature work. Para obtener más información, consulta la sección "[Crear un codespace](/codespaces/developing-in-codespaces/creating-a-codespace)". +Tu codespace puede ser efímero si necesitas probar algo o puedes volver al mismo codespace para trabajar en trabajo destacado a largo plazo. Para obtener más información, consulta la sección "[Crear un codespace](/codespaces/developing-in-codespaces/creating-a-codespace)". -Once you've selected the option to create a new codespace, some steps happen in the background before the codespace is available to you. +Una vez que hayas seleccionado la opción de crear un codespace nuevo, algunos pasos suceden en segundo plano antes de que este esté disponible para ti. ![Botón de abrir con codespaces](/assets/images/help/codespaces/new-codespace-button.png) -### Step 1: VM and storage are assigned to your codespace +### Paso 1: Se asigna una MV y un almacenamiento a tu codespace -When you create a codespace, a [shallow clone](https://github.blog/2020-12-21-get-up-to-speed-with-partial-clone-and-shallow-clone/) of your repository is made on a Linux virtual machine that is both dedicated and private to you. Having a dedicated VM ensures that you have the entire set of compute resources from that machine available to you. If necessary, this also allows you to have full root access to your container. +Cuando creas un codespace, se hace un [clon superficial](https://github.blog/2020-12-21-get-up-to-speed-with-partial-clone-and-shallow-clone/) de tu repositorio en una máquina virtual Linux que es tanto dedicada como privada para ti. El tener una MV dedicada garantiza que tengas un conjunto completo de recursos de cómputo disponibles para ti desde esa máquina. Si es necesario, esto también te permitirá tener acceso de raíz total a tu contenedor. -### Step 2: Container is created +### Paso 2: Se crea el contenedor -{% data variables.product.prodname_codespaces %} uses a container as the development environment. This container is created based on the configurations that you can define in a `devcontainer.json` file and/or Dockerfile in your repository. If you don't [configure a container](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project), {% data variables.product.prodname_codespaces %} uses a [default image](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project#using-the-default-configuration), which has many languages and runtimes available. For information on what the default image contains, see the [`vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers/tree/main/containers/codespaces-linux) repository. +{% data variables.product.prodname_codespaces %} utiliza un contenedor como el ambiente de desarrollo. Este contenedor se crea con base en las configuraciones que puedes definir en un archivo de `devcontainer.json` o Dockerfile en tu repositorio. Si no [configuras un contenedor](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project), {% data variables.product.prodname_codespaces %} utilizará una [imagen predeterminada](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project#using-the-default-configuration), la cual tiene muchos lenguajes y tiempos de ejecución disponibles. Para obtener más información sobre lo que contiene la imagen predeterminada, consulta el repositorio [`vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers/tree/main/containers/codespaces-linux). -### Step 3: Connecting to the codespace +### Paso 3: Conectarse al 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. +Cuando tu contenedor se crea y se ejecuta cualquier otra inicialización, estarás conectado a tu codespace. Puedes conectarte a este a través de la web o a través de [Visual Studio Code](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code) o a través de ambos, en caso de ser necesario. -### Step 4: Post-creation setup +### Paso 4: Ajustes post-creación -Once you're connected to your codespace, automated setup that you specified in your `devcontainer.json` file, such as running the `postCreateCommand` and `postAttachCommand`, may continue. If you have a public dotfiles repository {% 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 look for an install file. Para obtener más información, consulta la sección "[Personalizar {% data variables.product.prodname_codespaces %} para tu cuenta](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account#dotfiles)". +Una vez que estés conectado a tu codespace, la configuración automática que especificaste en tu archivo `devcontainer.json`, tal como ejecutar el `postCreateCommand` y el `postAttachCommand`, podría continuar. Si tienes un {% data variables.product.prodname_codespaces %} de repositorio de dotfiles público, puedes habilitarlo para utilizarlo con el codespace nuevo. Cuando lo habilitas, tus dotfiles se clonarán en el contenedor y buscarán un archivo de instalación. Para obtener más información, consulta la sección "[Personalizar {% data variables.product.prodname_codespaces %} para tu cuenta](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account#dotfiles)". -Finally, the entire history of the repository is copied down with a full clone. +Finalmente, todo el historial del repositorio se copiará con un clon integral. -During post-creation setup you'll still be able to use the integrated terminal and make edits to your files, but take care to avoid any race conditions between your work and the commands that are running. -## {% data variables.product.prodname_codespaces %} lifecycle +Durante la configuración post-creación, aún podrás utilizar la terminal integrada y editar tus archivos, pero ten cuidado de evitar cualquier condiciones de carrera entre tu trabajo y los comandos que se están ejecutando. +## Ciclo de vida de los {% data variables.product.prodname_codespaces %} -### Saving files in your codespace +### Guardar archivos en tu codespace -As you develop in your codespace, it will save any changes to your files every few seconds. Your codespace will keep running for 30 minutes after the last activity. After that time it will stop running but you can restart it from either from the existing browser tab or the list of existing codespaces. File changes from the editor and terminal output are counted as activity and so your codespace will not stop if terminal output is continuing. +Conforme desarrollas en tu codespace, este guardará cualquier cambio en tus archivos cada algunos cuantos segundos. Tu codespace seguirá ejecutándose durante 30 minutos después de la última actividad. Después de este tiempo, este dejará de ejecutarse, pero puedes reiniciarlo ya sea desde la pestaña existente del buscador o desde la lista de codespaces existentes. Los cambios de archivo del editor y de la salida de la terminal se cuentan como actividad y, por lo tanto, tu codespace no se detendrá si la salida de la terminal sigue. {% 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). +**Nota:** Los cambios en un codespace en {% data variables.product.prodname_vscode %} no se guardan automáticamente a menos de que hayas habilitado el [Guardado automático](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save). {% endnote %} -### Closing or stopping your codespace +### Cerrar o detener tu codespace -To stop your codespace you can [use the command palette](/codespaces/codespaces-reference/using-the-command-palette-in-codespaces#suspending-or-stopping-a-codespace) (`Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows)). If you exit your codespace without running the stop command (for example, closing the browser tab), or if you leave the codespace running without interaction, the codespace and its running processes will continue until a window of inactivity occurs, after which the codespace will stop. By default, the window of inactivity is 30 minutes. +Para detener tu codespace, puedes [utilizar la paleta de comandos](/codespaces/codespaces-reference/using-the-command-palette-in-codespaces#suspending-or-stopping-a-codespace) (`Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows)). Si sales de tu codespace sin ejecutar el comando para detenerlo (por ejemplo, cerrar la pestaña del buscador) o si dejas el codespace ejecutándose sin interacción, este y sus procesos en ejecución seguirán hasta que ocurra una ventana de inactividad, después de la cual se detendrá el codespace. Predeterminadamente, la ventana de inactividad es de 30 minutos. -When you close or stop your codespace, all uncommitted changes are preserved until you connect to the codespace again. +Cuando cierras o detienes tu codespace, todos los cambios sin confirmar se preservan hasta que te conectes al codespace nuevamente. -## Running your application +## Ejecutar tu aplicación -La redirección de puertos te otorga acceso a los puertos CRP dentro de tu codespace. For example, if you're running a web application on port 4000 within your codespace, you can automatically forward that port to make the application accessible from your browser. +La redirección de puertos te otorga acceso a los puertos CRP dentro de tu codespace. Por ejemplo, si estás ejecutando una aplicación web por el puerto 4000 dentro de tu codespace, puedes reenviar ese puerto automáticamente para hacer la aplicación accesible desde tu buscador. -Port forwarding determines which ports are made accessible to you from the remote machine. Even if you do not forward a port, that port is still accessible to other processes running inside the codespace itself. +El reenvío de puertos determina cuáles de ellos se hicieron accesibles para ti desde la máquina remota. Incluso si no reenvías un puerto, este será accesible para otros procesos que se ejecuten dentro del mismo codespace. -![Diagram showing how port forwarding works in a codespace](/assets/images/help/codespaces/port-forwarding.png) +![Diagrama que muestra cómo funciona el reenvío de puertos en un codespace](/assets/images/help/codespaces/port-forwarding.png) -When an application running inside {% data variables.product.prodname_codespaces %} outputs a port to the console, {% data variables.product.prodname_codespaces %} detects the localhost URL pattern and automatically forwards the port. You can click on the URL in the terminal or in the toast message to open the port in a browser. For more information on port forwarding, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)." +Cuando una aplicción que se ejecuta dentro del {% data variables.product.prodname_codespaces %} da salida a un puerto hacia la consola, el {% data variables.product.prodname_codespaces %} detecta el patrón de URL del host local y reenvía el puerto automáticamente. Puedes hacer clic en la URL de la terminal o en el mensaje de notificación para abrir el puerto en un buscador. Para obtener más información sobre el reenvío de puertos, consulta la sección "[Reenviar puertos en tu codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)". -While ports can be forwarded automatically, they are not publicly accessible to the internet. By default, all ports are private, but you can [manually make a port public](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace#sharing-a-port) to share access through a URL. +Si bien los puertos pueden reenviarse automáticamente, no son accesibles públicamente en la internet. Predeterminadamente, todos los puertos son privados, pero puedes [hacer un puerto público manualmente](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace#sharing-a-port) para compartir el acceso mediante una URL. -Running your application when you first land in your codespace can make for a fast inner dev loop. As you edit, your changes are automatically saved and available on your forwarded port. To view changes, go back to the running application tab in your browser and refresh it. +El ejecutar tu aplicación cuando llegas por primera vez a tu codespace puede convertirse en un bucle de desarrollador interno rápido. Mientras editas, tus cambios se guardan automáticamente y se ponen disponibles en tu puerto reenviado. Para ver los cambios, regresa a la pestaña de la aplicación en ejecución en tu buscador y actualízala. -## Committing and pushing your changes +## Confirmar y subir tus cambios -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 se encuentra disponible predeterminadamente en tu codespace, entonces puedes confiar en tu flujo de trabajo existente de Git. Puedes trabajar con Git en tu codespace, ya sea a través de la Terminal o utilizando la IU de control de código fuente de [Visual Studio Code](https://code.visualstudio.com/docs/editor/versioncontrol). 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)" -![Running git status in Codespaces Terminal](/assets/images/help/codespaces/git-status.png) +![Ejecutar un estado de git en la Terminal de Codespaces](/assets/images/help/codespaces/git-status.png) -You can create a codespace from any branch, commit, or pull request in your project, or you can switch to a new or existing branch from within your active codespace. Because {% data variables.product.prodname_codespaces %} is designed to be ephemeral, you can use it as an isolated environment to experiment, check a teammate's pull request, or fix merge conflicts. Puedes crear más de un codespace por repositorio o incluso por rama. However, each user account has a limit of 10 codespaces. Si has alcanzado el límite y quieres crear un codespace nuevo, primero debes borrar un codespace. +Puedes crear un codespace desde cualquier rama, confirmación o solicitud de cambios en tu proyecto o puedes cambiar a una rama existente o nueva desde dentro de tu codespace activo. Ya que {% data variables.product.prodname_codespaces %} está diseñado para ser efímero, puedes utilizarlo como un ambiente aislado para experimentar, verificar la solicitud de cambios de un compañero o arreglar conflictos de fusión. Puedes crear más de un codespace por repositorio o incluso por rama. Sin embargo, cada cuenta de usuario tiene un límite de 10 codespaces. Si has alcanzado el límite y quieres crear un codespace nuevo, primero debes borrar un codespace. {% note %} -**Note:** Commits from your codespace will be attributed to the name and public email configured at https://github.com/settings/profile. A token scoped to the repository, included in the environment as `GITHUB_TOKEN`, and your GitHub credentials will be used to authenticate. +**Nota:** Las confirmaciones desde tu codespace se atribuirán al nombre y correo electrónico público que se configuró en https://github.com/settings/profile. Para autenticarte, se utilizará un token con alcance al repositorio, incluido en el ambiente como `GITHUB_TOKEN`, y tus credenciales de GitHub. {% endnote %} -## Personalizing your codespace with extensions +## Personalizar tu codespace con extensiones -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. +El utilizar {% data variables.product.prodname_vscode %} en tu codespace te proporciona acceso a el Mercado de {% data variables.product.prodname_vscode %} para que puedas agregar cualquier extensión que necesites. Para obtener más información sobre cómo se ejecutan las extensiones en {% data variables.product.prodname_codespaces %}, consulta la sección [Apoyar el desarrollo remoto y a los Codespaces de GitHub](https://code.visualstudio.com/api/advanced-topics/remote-extensions) en los documentos de {% data variables.product.prodname_vscode %}. -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. +Si yta utilizas {% data variables.product.prodname_vscode %}, puedes usar la [Sincronización de ajustes](https://code.visualstudio.com/docs/editor/settings-sync) para sincronizar automáticamente extensiones, ajustes, temas y atajos de teclado entre tu instancia local y cualquier {% data variables.product.prodname_codespaces %} que crees. ## Leer más -- [Enabling {% data variables.product.prodname_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization) -- [Managing billing for {% data variables.product.prodname_codespaces %} in your organization](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization) -- [Setting up your project for Codespaces](/codespaces/setting-up-your-project-for-codespaces) +- [Habilitar los {% data variables.product.prodname_codespaces %} para tu organización](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization) +- [Administrar la facturación para los {% data variables.product.prodname_codespaces %} en tu organización](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization) +- [Configurar tu proyecto para los Codespaces](/codespaces/setting-up-your-project-for-codespaces) diff --git a/translations/es-ES/content/codespaces/getting-started/quickstart.md b/translations/es-ES/content/codespaces/getting-started/quickstart.md index 2623e6add3..304f78a3af 100644 --- a/translations/es-ES/content/codespaces/getting-started/quickstart.md +++ b/translations/es-ES/content/codespaces/getting-started/quickstart.md @@ -1,6 +1,6 @@ --- -title: Quickstart for Codespaces -intro: 'Try out {% data variables.product.prodname_codespaces %} in 5 minutes.' +title: Inicio rápido para Codespaces +intro: 'Intenta {% data variables.product.prodname_codespaces %} en 5 minutos.' allowTitleToDifferFromFilename: true product: '{% data reusables.gated-features.codespaces %}' versions: @@ -14,64 +14,64 @@ redirect_from: ## Introducción -In this guide, you'll create a codespace from a [template repository](https://github.com/2percentsilk/haikus-for-codespaces) and explore some of the essential features available to you within the codespace. +En esta guía, crearás un codespace desde un [repositorio de plantilla](https://github.com/2percentsilk/haikus-for-codespaces) y explorarás algunas de las características esenciales disponibles para ti dentro del codespace. -From this quickstart, you will learn how to create a codespace, connect to a forwarded port to view your running application, use version control in a codespace, and personalize your setup with extensions. +Desde esta guía de inicio rápido, aprenderás cómo crear un codespace, cómo conectarte a un puerto reenviado para ver tu aplicación ejecutándose, cómo utilizar el control de versiones en un codespace y cómo personalizar tu configuración con extensiones. -For more information on exactly how {% data variables.product.prodname_codespaces %} works, see the companion guide "[Deep dive into {% data variables.product.prodname_codespaces %}](/codespaces/getting-started/deep-dive)." +Para obtener más información sobre cómo funcionan los {% data variables.product.prodname_codespaces %} exactamente, consulta la guía compañera "[Conoce los {% data variables.product.prodname_codespaces %} a fondo](/codespaces/getting-started/deep-dive)". ## Crea tu codespace -1. Navigate to the [template repository](https://github.com/2percentsilk/haikus-for-codespaces) and select **Use this template**. +1. Navega al [repositorio de plantilla](https://github.com/2percentsilk/haikus-for-codespaces) y selecciona **Utilizar esta plantilla**. -2. Name your repository, select your preferred privacy setting, and click **Create repository from this template**. +2. Nombra a tu repositorio, selecciona tus ajustes de privacidad preferidos y haz clic en **Crear repositorio desde esta plantilla**. -3. Navigate to the main page of the newly created repository. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu, and in the **Codespaces** tab, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. +3. Navega a la página principal del repositorio recientemente creado. Debajo del nombre de repositorio, utiliza el menú desplegable de **Código {% octicon "code" aria-label="The code icon" %}** y, en la pestaña de **Codespaces**, haz clic en {% octicon "plus" aria-label="The plus icon" %} **Codespace nuevo**. ![Botón de codespace nuevo](/assets/images/help/codespaces/new-codespace-button.png) -## Running the application +## Ejecutar la aplicación -Once your codespace is created, your repository will be automatically cloned into it. Now you can run the application and launch it in a browser. +Una vez que se cree tu codespace, tu repositorio se clonará automáticamente en él. Ahora puedes ejecutar la aplicación y lanzarla en un buscador. -1. Since this example uses a Node.js project, start the application by entering `npm run dev` in the terminal. Este comando ejecuta el script `dev` en el archivo package.json e inicia la aplicación web que se define en el repositorio de muestra. +1. Ya que este ejemplo utiliza un proyecto en Node.js, inicia la aplicación ingresando `npm run dev` en la terminal. Este comando ejecuta el script `dev` en el archivo package.json e inicia la aplicación web que se define en el repositorio de muestra. ![npm run dev en la temrinal](/assets/images/help/codespaces/codespaces-npm-run-dev.png) - If you're following along with a different application type, enter the corresponding start command for that project. + Si estás siguiendo la guía con un tipo de aplicación diferente, ingresa el comando de incio correspondiente para este. -2. When your application starts, the codespace recognizes the port the application is running on and displays a prompt to forward that port so you can connect to it. +2. Cuando tu aplicación inicie, el codespace reconocerá el puerto en el cual está ejecutándose y mostrará un mensaje para reenviar este puerto para que te puedas conectar a él. ![Notificación de reenvío de puertos](/assets/images/help/codespaces/quickstart-port-toast.png) 3. Haz clic en **Abrir en el buscador** para ver tu aplicación que se está ejecutando en una pestaña nueva. -## Edit the application and view changes +## Editar la aplicación y ver los cambios -1. Switch back to your codespace and open the `haikus.json` file by double-clicking it in the File Explorer. +1. Regresa a tu codespace y abre el archivo `haikus.json` haciendo doble clic en el Explorador de Archivos. -2. Edit the `text` field of the first haiku to personalize the application with your own haiku. +2. Edita el campo `text` del primer haiku para personalizar la aplicación con tu propio haiku. -3. Go back to the running application tab in your browser and refresh to see your changes. +3. Regresa a la pestaña de la aplicación en ejecución dentro de tu buscador y actualiza para ver los cambios. - {% octicon "light-bulb" aria-label="The lightbulb icon" %} If you've closed the tab, open the Ports panel and click the **Open in browser** icon for the running port. - ![Port Forwarding Panel](/assets/images/help/codespaces/quickstart-forward-port.png) + {% octicon "light-bulb" aria-label="The lightbulb icon" %} Si cerraste la pestaña, abre el panel de Puertos y haz clic en el icono de **Abrir en el buscador** para el puerto en ejecución. + ![Panel de reenvío de puertos](/assets/images/help/codespaces/quickstart-forward-port.png) -## Committing and pushing your changes +## Confirmar y subir tus cambios -Now that you've made a few changes, you can use the integrated terminal or the source view to commit and push the changes back to the remote. +Ahora que hiciste algunos cambios, puedes utilizar la terminal integrada o la vista de código fuente para confirmar y subir los cambios al remoto. {% data reusables.codespaces.source-control-display-dark %} 1. Para probar tus cambios, haz clic en **+** junto al archivo que cambiaste o junto a **Cambios** si cambiaste archivos múltiples y quieres probarlos todos. ![Barra lateral de control de código fuente con el botón de preparación resaltado](/assets/images/help/codespaces/codespaces-commit-stage.png) 1. Teclea un mensaje de confirmación que describa el cambio que hiciste. ![Barra de control de código fuente con un mensaje de confirmación](/assets/images/help/codespaces/codespaces-commit-commit-message.png) 1. Para confirmar tus cambios planeados, haz clic en la marca de verificación en la parte superior de la barra lateral del control de código fuente. ![Click the check mark icon](/assets/images/help/codespaces/codespaces-commit-checkmark-icon.png) - You can push the changes you've made. Esto aplica a aquellos de la rama ascendente en el repositorio remoto. Puede que necesites hacer eso si aún no estás listo para crear una solicitud de cambios o si prefieres crearla en {% data variables.product.prodname_dotcom %}. + Puedes subir los cambios que hiciste. Esto aplica a aquellos de la rama ascendente en el repositorio remoto. Puede que necesites hacer eso si aún no estás listo para crear una solicitud de cambios o si prefieres crearla en {% data variables.product.prodname_dotcom %}. 1. En la parte superior de la barra lateral, haz clic en los puntos suspensivos (**...**). ![Botón de puntos suspensivos para las acciones de "más" y "ver"](/assets/images/help/codespaces/source-control-ellipsis-button-nochanges.png) 1. En el menú desplegable, haz clic en **Subir**. -## Personalizing with an extension +## Personalizar con una extensión -Dentro de un codespace, tienes acceso al 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. +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. 1. En la barra lateral, haz clic en el icono de extensiones. @@ -83,16 +83,16 @@ Dentro de un codespace, tienes acceso al Visual Studio Code Marketplace. For thi ![Seleccionar el tema de 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. 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. ## Siguientes pasos Creaste, personalizaste y ejecutaste exitosamente tu primer aplicación dentro de un codespace, pero ¡hay mucho más que explorar! Aquí tienes algunos recursos útiles para que tomes tus siguientes pasos con {% data variables.product.prodname_codespaces %}. - - [Deep dive](/codespaces/getting-started/deep-dive): This quickstart presented some of the features of {% data variables.product.prodname_codespaces %}. The deep dive looks at these areas from a technical standpoint. - - [Setting up your project for {% data variables.product.prodname_codespaces %}](/codespaces/getting-started-with-codespaces): These guides provide information on setting up your project to use {% data variables.product.prodname_codespaces %} with specific languages - - [Configuring {% data variables.product.prodname_codespaces %} for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project): This guide provides details on creating a custom configuration for {% data variables.product.prodname_codespaces %} for your project. + - [Cónocelo a fondo](/codespaces/getting-started/deep-dive): Esta guía de inicio rápido presenta algunas de las características de los {% data variables.product.prodname_codespaces %}. La guía a fondo ve estas áreas desde un punto de vista técnico. + - [Configurar tu proyecto para los {% data variables.product.prodname_codespaces %}](/codespaces/getting-started-with-codespaces): Estas guías te proporcionan información sobre cómo configurar tu proyecto para utilizar los {% data variables.product.prodname_codespaces %} con lenguajes específicos + - [Configurar los {% data variables.product.prodname_codespaces %} para tu proyecto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project): Esta guía te proporciona detalles para crear una configuración personalizada para los {% data variables.product.prodname_codespaces %} para tu proyecto. ## Leer más -- [Enabling {% data variables.product.prodname_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization) -- [Managing billing for {% data variables.product.prodname_codespaces %} in your organization](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization) +- [Habilitar los {% data variables.product.prodname_codespaces %} para tu organizción](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization) +- [Administrar la facturación para los {% data variables.product.prodname_codespaces %} en tu organización](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization) diff --git a/translations/es-ES/content/codespaces/guides.md b/translations/es-ES/content/codespaces/guides.md index bea56090cf..b0435d3507 100644 --- a/translations/es-ES/content/codespaces/guides.md +++ b/translations/es-ES/content/codespaces/guides.md @@ -2,7 +2,7 @@ title: Guías de codespaces shortTitle: Guías product: '{% data reusables.gated-features.codespaces %}' -intro: Learn how to make the most of GitHub +intro: Aprende cómo sacar el mayor provecho de GitHub allowTitleToDifferFromFilename: true layout: product-sublanding versions: diff --git a/translations/es-ES/content/codespaces/index.md b/translations/es-ES/content/codespaces/index.md index 5fb9f23c3e..eb150ed355 100644 --- a/translations/es-ES/content/codespaces/index.md +++ b/translations/es-ES/content/codespaces/index.md @@ -41,6 +41,7 @@ children: - /managing-codespaces-for-your-organization - /codespaces-reference - /troubleshooting + - /the-githubdev-web-based-editor - /guides --- diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md index ba61180999..6e11c76124 100644 --- a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md +++ b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md @@ -1,6 +1,6 @@ --- -title: Enabling Codespaces for your organization -shortTitle: Enabling Codespaces +title: Habilitar los Codespaces para tu organización +shortTitle: Habilitar los Codespaces intro: 'Puedes controlar qué usuarios de tu organización pueden utilizar {% data variables.product.prodname_codespaces %}.' product: '{% data reusables.gated-features.codespaces %}' permissions: 'To manage user permissions for {% data variables.product.prodname_codespaces %} for an organization, you must be an organization owner.' @@ -16,19 +16,19 @@ topics: --- -## About enabling {% data variables.product.prodname_codespaces %} for your organization +## Acerca de cómo habilitar los {% data variables.product.prodname_codespaces %} para tu organización Los propietarios de organización pueden controlar qué usuarios de tu organización pueden crear y utilizar codespaces. -To use codespaces in your organization, you must do the following: +Para utilizar codespaces en tu organización, debes hacer lo siguiente: -- Ensure that users have [at least write access](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization) to the repositories where they want to use a codespace. -- [Enable {% data variables.product.prodname_codespaces %} for users in your organization](#configuring-which-users-in-your-organization-can-use-codespaces). You can choose allow {% data variables.product.prodname_codespaces %} for selected users or only for specific users. -- [Set a spending limit](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces) +- Asegurarte de que los usuarios tengan [por lo menos acceso de escritura](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization) en los repositorios en donde quieren utilizar un codespace. +- [Habilitar los {% data variables.product.prodname_codespaces %} para los usuarios en tu organización](#configuring-which-users-in-your-organization-can-use-codespaces). Puedes elegir permitir los {% data variables.product.prodname_codespaces %} para los usuarios seleccionados o únicamente para los usuarios específicos. +- [Configurar un límite de gastos](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces) -By default, a codespace can only access the repository from which it was created. Si quieres que los codespaces de tu organización puedan acceder a otros repositorios de organización a los que puede acceder el creador de dichos codespaces, consulta la sección "[Administrar el acceso y la seguridad de los {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)". +Predeterminadamente, un codespace solo puede acceder al repositorio desde el cual se creó. Si quieres que los codespaces de tu organización puedan acceder a otros repositorios de organización a los que puede acceder el creador de dichos codespaces, consulta la sección "[Administrar el acceso y la seguridad de los {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)". -## Enable {% data variables.product.prodname_codespaces %} for users in your organization +## Habilitar los {% data variables.product.prodname_codespaces %} para los usuarios en tu organización {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} @@ -40,14 +40,14 @@ By default, a codespace can only access the repository from which it was created ![Botones radiales de "Permisos de usuario"](/assets/images/help/codespaces/organization-user-permission-settings.png) -## Disabling {% data variables.product.prodname_codespaces %} for your organization +## Inhabilitar los {% data variables.product.prodname_codespaces %} para tu organización {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.click-codespaces %} -1. Under "User permissions", select **Disabled**. +1. Debajo de "Permisos de usuario", selecciona **Inhabilitado**. -## Setting a spending limit +## Configurar un límite de gastos {% data reusables.codespaces.codespaces-spending-limit-requirement %} diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/index.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/index.md index e00b8659e0..7ab7d401e7 100644 --- a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/index.md +++ b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/index.md @@ -12,6 +12,6 @@ children: - /managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces - /managing-repository-access-for-your-organizations-codespaces - /reviewing-your-organizations-audit-logs-for-codespaces -shortTitle: Managing your organization +shortTitle: Admnistrar tu organización --- 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 78eab74a74..34b4f79538 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 @@ -1,7 +1,7 @@ --- -title: Managing billing for Codespaces in your organization -shortTitle: Managing billing for Codespaces -intro: 'You can check your {% data variables.product.prodname_codespaces %} usage and set usage limits.' +title: Administrar la facturación para los Codespaces en tu organización +shortTitle: Administrar la facturación para los Codespaces +intro: 'Puedes verificar tu uso de {% data variables.product.prodname_codespaces %} y configurar los límites de uso.' product: '{% data reusables.gated-features.codespaces %}' permissions: 'To manage billing for Codespaces for an organization, you must be an organization owner or a billing manager.' versions: @@ -14,31 +14,31 @@ topics: ## Resumen -To learn about pricing for {% data variables.product.prodname_codespaces %}, see "[{% data variables.product.prodname_codespaces %} pricing](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)." +Para aprender más sobre los precios de los {% data variables.product.prodname_codespaces %}, consulta la sección "[precios de los {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)". {% data reusables.codespaces.codespaces-billing %} -- As an an organization owner or a billing manager you can manage {% data variables.product.prodname_codespaces %} billing for your organization: ["About billing for Codespaces"](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces) +- Como propietario o gerente de facturación de una organización, puedes administrar la facturación de {% data variables.product.prodname_codespaces %} para tu organización: ["Acerca de la facturación para Codespaces"](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces) -- For users, there is a guide that explains how billing works: ["Understanding billing for Codespaces"](/codespaces/codespaces-reference/understanding-billing-for-codespaces) +- Hay una guía para los usuarios que explica cómo funciona la facturación: ["Entender la facturación para los Codespaces"](/codespaces/codespaces-reference/understanding-billing-for-codespaces) ## Límites de uso -You can set a usage limit for the codespaces in your organization or repository. This limit is applied to the compute and storage usage for {% data variables.product.prodname_codespaces %}: +Puedes configurar el límite de uso de los codespaces en tu organización o repositorio. Este límite se aplica al uso de cálculo y almacenamiento de {% data variables.product.prodname_codespaces %}: -- **Compute minutes:** Compute usage is calculated by the actual number of minutes used by all {% data variables.product.prodname_codespaces %} instances while they are active. These totals are reported to the billing service daily, and is billed monthly. You can set a spending limit for {% data variables.product.prodname_codespaces %} usage in your organization. For more information, see "[Managing spending limits for Codespaces](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)." +- **Minutos de cálculo:** El uso de cálculo se obtiene con la cantidad actual de minutos que utilizan todas las instancias de {% data variables.product.prodname_codespaces %} mientras están activas. Estos totales se reportan al servicio de facturación diariamente y se cobran mensualmente. Puedes configurar un límite de gastos para el uso de {% data variables.product.prodname_codespaces %} en tu organización. Para obtener más información, consulta la sección "[Administrar los límites de gastos para los Codespaces](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)". -- **Storage usage:** For {% data variables.product.prodname_codespaces %} billing purposes, this includes all storage used by all codespaces in your account. This includes all used by the codespaces, such as cloned repositories, configuration files, and extensions, among others. These totals are reported to the billing service daily, and is billed monthly. Al final del mes, {% data variables.product.prodname_dotcom %} redondea tu almacenamiento al número de MB más cercano. To check how many compute minutes and storage GB have been used by {% data variables.product.prodname_codespaces %}, see "[Viewing your Codespaces usage"](/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage)." +- **Uso de almacenamiento:** Para propósitos de facturación de {% data variables.product.prodname_codespaces %}, esto incluye todo el almacenamiento que se utiliza en todos los codespaces de tu cuenta. Esto incluye todos los que utilizan los codespaces, tales como los repositorios clonados, archivos de configuración y extensiones, entre otros. Estos totales se reportan al servicio de facturación diariamente y se cobran mensualmente. Al final del mes, {% data variables.product.prodname_dotcom %} redondea tu almacenamiento al número de MB más cercano. Para verificar cuántos minutos de cálculo y GB de almacenamiento ha utilizado cualquier {% data variables.product.prodname_codespaces %}, consulta la sección "[Ver tu uso de Codespaces](/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage)". -## Disabling or limiting {% data variables.product.prodname_codespaces %} +## Inhabilitar o limitar los {% data variables.product.prodname_codespaces %} -You can disable the use of {% data variables.product.prodname_codespaces %} in your organization or repository. For more information, see "[Managing repository access for your organization's codespaces](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)." +Puedes inhabilitar el uso de los {% data variables.product.prodname_codespaces %} en tu organización o repositorio. Para obtener más información, consulta la sección "[Administrar el acceso de un repositorio a los codespces de tu organización](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)". -You can also limit the individual users who can use {% data variables.product.prodname_codespaces %}. For more information, see "[Managing user permissions for your organization](/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization)." +También puedes limitar a los usuarios individuales que pueden utilizar {% data variables.product.prodname_codespaces %}. Para obtener más información, consulta la sección "[Administrar los permisos de los usuarios para tu organización](/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization)". -## Deleting unused codespaces +## Borrar los codespaces sin utilizar -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. +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. {% note %} diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md index 39e7191d80..b2bdc9b572 100644 --- a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md +++ b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md @@ -72,3 +72,7 @@ Puedes revisar qué políticas de acceso se aplican a un secreto en tu organizac {% data reusables.github-actions.sidebar-secret %} 1. La lista de secretos incluye cualquier política y permiso configurado. Por ejemplo: ![Lista de secretos](/assets/images/help/settings/actions-org-secrets-list.png) 1. Para encontrar más detalles sobre los permisos configurados para cada secreto, da clic en **Actualizar**. + +## Leer más + +- "[Administrar los secretos cifrados para tus codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)" diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md index e8843672f0..b724c2b372 100644 --- a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md +++ b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md @@ -1,6 +1,6 @@ --- -title: Managing repository access for your organization's codespaces -shortTitle: Repository access +title: Administrar el acceso de los codespaces de tu organización a los repositorios +shortTitle: Acceso a los repositorios intro: 'Puedes administrar los repositorios de tu organización a los cuales pueden acceder los {% data variables.product.prodname_codespaces %}.' product: '{% data reusables.gated-features.codespaces %}' permissions: 'To manage access and security for Codespaces for an organization, you must be an organization owner.' @@ -26,3 +26,7 @@ Para administrar qué usuarios de tu organización pueden utilizar {% data varia {% data reusables.organizations.click-codespaces %} 1. Debajo de "Acceso y seguridad", selecciona la configuración que quieras para tu organización.![Botones radiales para adminsitrar los repositorios confiables](/assets/images/help/settings/codespaces-org-access-and-security-radio-buttons.png) 1. Si eliges "Repositorios seleccionados"; entonces selecciona el menú desplegable y da clic en un repositorio para permitir que los codespaces de éste accedan al resto de los repositorios que pertenecen a tu organización. Repite esto para todos los repositorios cuyos codespaces quieras que accedan al resto de los repositorios. ![Menú desplegable de "Repositorios seleccionados"](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) + +## Leer más + +- "[Managing repository access for your codespaces](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces)" diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md index 61a8642650..61d7c42acd 100644 --- a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md +++ b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md @@ -19,3 +19,7 @@ Cuando algún miembro de tu organización lleva a cabo una acción relacionada c ![Bitácora de auditoría con información de los codespaces](/assets/images/help/settings/codespaces-audit-log-org.png) La bitácora de auditoría incluye detalles tales como quién realizó la acción, qué fue esa acción y cuándo se llevó a cabo. Para obtener información sobre las acciones de los {% data variables.product.prodname_codespaces %}, consulta la sección "[acciones de categoría de los {% data variables.product.prodname_codespaces %}](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#codespaces-category-actions)". + +## Leer más + +- "[Reviewing your security logs for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces)" diff --git a/translations/es-ES/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md b/translations/es-ES/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md index 40d5acca68..7df81e572c 100644 --- a/translations/es-ES/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md +++ b/translations/es-ES/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md @@ -73,3 +73,7 @@ Puedes actualizar el valor de un secreto existente y puedes cambiar qué reposit {% data reusables.user_settings.codespaces-tab %} 1. Debajo de "Secretos de los codespaces", a la derecha del secreto que quieras borrar, da clic en **Borrar**. ![Botón de "Borrar"](/assets/images/help/settings/codespaces-secret-delete-button.png) 1. Lee la advertencia y da clic en **OK**. ![Confirmación para borrar un secreto](/assets/images/help/settings/codespaces-secret-delete-warning.png) + +## Leer más + +- "[Managing encrypted secrets for your repository and organization for {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces)" diff --git a/translations/es-ES/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md b/translations/es-ES/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md index 3d27183597..428a1c8a7a 100644 --- a/translations/es-ES/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md +++ b/translations/es-ES/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md @@ -19,7 +19,7 @@ shortTitle: Verificación GPG Después de que habilitas la verificación de GPG, {% data variables.product.company_short %} firmará automáticamente las confirmaciones que hagas en los {% data variables.product.prodname_codespaces %} y éstas tendrán un estado de verificado en {% data variables.product.product_name %}. Predeterminadamente, la verificación GPG se encuentra inhabilitada para los codespaces que creas. Puedes elegir permitir la verificación de GPG para todos los repositorios o para repositorios específicos. Habilita la verificación GPG únicamente para los repositorios en los cuales confías. Para obtener más información acerca de las confirmaciones firmadas por {% data variables.product.product_name %}, consulta la sección "[Acerca de la verificación de firmas de las confirmaciones](/github/authenticating-to-github/about-commit-signature-verification)". -Once you enable GPG verification, it will immediately take effect for all your codespaces. +Una vez que habilitas la verificación de GPG, esta tomará efecto inmediatamente en todos tus codespaces. {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.codespaces-tab %} @@ -29,6 +29,6 @@ Once you enable GPG verification, it will immediately take effect for all your c {% note %} -**Note:** Once you have enabled GPG verification for {% data variables.product.prodname_codespaces %}, you also must append `-s` to each commit in order for it to be signed. To do this in {% data variables.product.prodname_vscode %}, ensure the "Git: Enable Commit Signing" option is enabled from the Settings. +**Note:** Once you have enabled GPG verification for {% data variables.product.prodname_codespaces %}, you also must append `-S` to each commit in order for it to be signed. Para hacerlo en {% data variables.product.prodname_vscode %}, asegúrate de que esté habilitada la opción "Git: Habilitar la Firma de Confirmante" desde los ajustes. {% endnote %} 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 2dcdb2b487..2a1309ec00 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,6 +1,6 @@ --- -title: Managing repository access for your codespaces -shortTitle: Repository access +title: Administrar el acceso de tus codespaces a los repositorios +shortTitle: Acceso a los repositorios intro: 'Puedes administrar los repositorios a los cuales pueden acceder los {% data variables.product.prodname_codespaces %}.' product: '{% data reusables.gated-features.codespaces %}' versions: @@ -20,3 +20,7 @@ Cuando habilitas el acceso y la seguridad de un repositorio que pertenezca a tu {% data reusables.user_settings.codespaces-tab %} 1. Debajo de "Acceso y seguridad"; selecciona la configuración que quieras para tu cuenta de usurio. ![Botones radiales para adminsitrar los repositorios confiables](/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. ![Menú desplegable de "Repositorios seleccionados"](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) + +## Leer más + +- "[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/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md b/translations/es-ES/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md index 32ac3645b2..7f419c9860 100644 --- a/translations/es-ES/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md +++ b/translations/es-ES/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md @@ -1,6 +1,6 @@ --- title: Revisar las bitácoras de seguridad de los Codespaces -shortTitle: Security logs +shortTitle: Bitácoras de seguridad intro: 'Puedes utilizar la bitácora de seguridad para revisar todas las acciones relacionadas con los {% data variables.product.prodname_codespaces %}.' product: '{% data reusables.gated-features.codespaces %}' versions: @@ -20,3 +20,7 @@ Cuando realizas una acción relacionada con {% data variables.product.prodname_c ![bitácora de seguridad con información sobre los codespaces](/assets/images/help/settings/codespaces-audit-log.png) La bitácora de seguridad incluye detalles de qué acción ocurrió y cuándo la realizaste. Para obtener información sobre las acciones de los {% data variables.product.prodname_codespaces %}, consulta la sección "[acciones de categoría de los {% data variables.product.prodname_codespaces %}](/github/authenticating-to-github/reviewing-your-security-log#codespaces-category-actions)". + +## Leer más + +- "[Reviewing your organization's audit logs for {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces)" diff --git a/translations/es-ES/content/codespaces/managing-your-codespaces/setting-your-default-editor-for-codespaces.md b/translations/es-ES/content/codespaces/managing-your-codespaces/setting-your-default-editor-for-codespaces.md index d0c324a463..7d80fcb300 100644 --- a/translations/es-ES/content/codespaces/managing-your-codespaces/setting-your-default-editor-for-codespaces.md +++ b/translations/es-ES/content/codespaces/managing-your-codespaces/setting-your-default-editor-for-codespaces.md @@ -1,20 +1,20 @@ --- -title: Setting your default editor for Codespaces -intro: 'You can set your default editor for {% data variables.product.prodname_codespaces %} in your personal settings page.' +title: Configurar tu editor predeterminado para Codesapces +intro: 'Puedes configurar tu editor predeterminado para {% data variables.product.prodname_codespaces %} en tu página de ajustes personal.' product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' topics: - Codespaces -shortTitle: Set the default editor +shortTitle: Configurar el editor predeterminado --- -On the settings page, you can set your editor preference so that any newly created codespaces are opened automatically in either {% data variables.product.prodname_vscode %} for Web or the {% data variables.product.prodname_vscode %} desktop application. +En la página de ajustes, puedes configurar las preferencias de tu editor para que los codespaces recién creados se abran automáticamente, ya sea en {% data variables.product.prodname_vscode %} para la Web o en {% data variables.product.prodname_vscode %} para escritorio. -If you want to use {% data variables.product.prodname_vscode %} as your default editor for {% data variables.product.prodname_codespaces %}, you need to install {% data variables.product.prodname_vscode %} and the {% data variables.product.prodname_github_codespaces %} extension for {% data variables.product.prodname_vscode %}. For more information, see the [download page for {% data variables.product.prodname_vscode %}](https://code.visualstudio.com/download/) and the [{% data variables.product.prodname_github_codespaces %} extension on the {% data variables.product.prodname_vscode %} marketplace](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces). +Si quieres utilizar {% data variables.product.prodname_vscode %} como tu editor predeterminado para {% data variables.product.prodname_codespaces %}, necesitas instalar {% data variables.product.prodname_vscode %} y la extensión de {% data variables.product.prodname_github_codespaces %} para {% data variables.product.prodname_vscode %}. Para obtener más información, consulta la [página de descarga de {% data variables.product.prodname_vscode %}](https://code.visualstudio.com/download/) y la [ extensión de {% data variables.product.prodname_github_codespaces %} en el mercado de {% data variables.product.prodname_vscode %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces). -## Setting your default editor +## Configurar tu editor predeterminado {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.codespaces-tab %} -1. Under "Editor preference", select the option you want. ![Setting your editor](/assets/images/help/codespaces/select-default-editor.png) If you choose **{% data variables.product.prodname_vscode %}**, {% data variables.product.prodname_codespaces %} will automatically open in the desktop application when you next create a codespace. You may need to allow access to both your browser and {% data variables.product.prodname_vscode %} for it to open successfully. ![Setting your editor](/assets/images/help/codespaces/launch-default-editor.png) +1. Debajo de "Preferencia de editor", selecciona la opción que desees. ![Setting your editor](/assets/images/help/codespaces/select-default-editor.png)Si eliges **{% data variables.product.prodname_vscode %}**, los {% data variables.product.prodname_codespaces %} se abrirán automáticamente en la aplicación de escritorio cuando crees el siguiente codespace. Podrías necesitar permitir acceso tanto a tu buscador como a {% data variables.product.prodname_vscode %} para que abra con éxito. ![Configurar tu editor](/assets/images/help/codespaces/launch-default-editor.png) diff --git a/translations/es-ES/content/codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces.md b/translations/es-ES/content/codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces.md index 9b00a4f227..2ff058b3ae 100644 --- a/translations/es-ES/content/codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces.md +++ b/translations/es-ES/content/codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces.md @@ -1,19 +1,19 @@ --- -title: Setting your default region for Codespaces -intro: 'You can set your default region in the {% data variables.product.prodname_github_codespaces %} profile settings page to personalize where your data is held.' +title: Configurar tu región predeterminada para Codespaces +intro: 'Pues configurar tu región predeterminada en la página de ajustes de perfil de {% data variables.product.prodname_github_codespaces %} para personalizar en donde se guardan tus datos.' product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' topics: - Codespaces -shortTitle: Set the default region +shortTitle: Configurar la región predeterminada --- -You can manually select the region that your codespaces will be created in, allowing you to meet stringent security and compliance requirements. By default, your region is set automatically, based on your location. +Puedes seleccionar manualmente la región en la que se crearán tus codespaces, permitiéndote cumplir con los requisitos de cumplimiento y seguridad estrictos. Predeterminadamente, tu región se configura automáticamente con base en tu ubicación. -## Setting your default region +## Configurar tu región predeterminada {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.codespaces-tab %} -1. Under "Region", select the setting you want. -2. If you chose "Set manually", select your region in the drop-down list. ![Selecting your region](/assets/images/help/codespaces/select-default-region.png) +1. Debajo de "Región", selecciona el ajuste que quieras. +2. Si eliges "Configurar manualmente", selecciona tu región en el menú desplegable. ![Seleccionar tu región](/assets/images/help/codespaces/select-default-region.png) diff --git a/translations/es-ES/content/codespaces/overview.md b/translations/es-ES/content/codespaces/overview.md index e4fe4a2224..5db33698a8 100644 --- a/translations/es-ES/content/codespaces/overview.md +++ b/translations/es-ES/content/codespaces/overview.md @@ -1,8 +1,8 @@ --- -title: GitHub Codespaces overview +title: Resumen de GitHub Codespaces shortTitle: Resumen product: '{% data reusables.gated-features.codespaces %}' -intro: 'This guide introduces {% data variables.product.prodname_codespaces %} and provides details on how it works and how to use it.' +intro: 'Esta guía te presenta a {% data variables.product.prodname_codespaces %} y te proporciona detalles de cómo funciona y cómo utilizarlo.' allowTitleToDifferFromFilename: true redirect_from: - /codespaces/codespaces-reference/about-codespaces @@ -17,26 +17,26 @@ topics: - Codespaces --- -## What is a codespace? +## ¿Qué es un codespace? -A codespace is a development environment that's hosted in the cloud. You can customize your project for {% data variables.product.prodname_codespaces %} by committing [configuration files](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project) to your repository (often known as Configuration-as-Code), which creates a repeatable codespace configuration for all users of your project. +Un codespace es un ambiente de desarrollo que se hospeda en la nube. Puedes personalizar tu proyecto para los {% data variables.product.prodname_codespaces %} si confirmas los [archivos de configuración](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project) a tu repositorio (lo cual se conoce habitualmente como Configuración-como-código), lo cual crea una configuración de codespace repetible para todos los usuarios de tu proyecto. -{% data variables.product.prodname_codespaces %} run on a variety of VM-based compute options hosted by {% data variables.product.product_location %}, which you can configure from 2 core machines up to 32 core machines. You can connect to your codespaces from the browser or locally using {% data variables.product.prodname_vscode %}. +Los {% data variables.product.prodname_codespaces %} se ejecutan en diversas opciones de cómputo basadas en MV hospedadas en {% data variables.product.product_location %}, las cuales puedes configurar desde máquinas de 2 núcleos hasta de 32 núcleos. Puedes conectar tus codespaces desde el buscador o localmente utilizando {% data variables.product.prodname_vscode %}. -![A diagram showing how {% data variables.product.prodname_codespaces %} works](/assets/images/help/codespaces/codespaces-diagram.png) +![Un diagrama que muestra cómo funciona {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/codespaces-diagram.png) -## Using Codespaces +## Utilizar Codespaces -You can create a codespace from any branch or commit in your repository and begin developing using cloud-based compute resources. +Puedes crear un codespace desde cualquier rama o confirmación en tu repositorio y comenzar a desarrollar utilizando recursos de cómputo basados en la nube. -To customize the runtimes and tools in your codespace, you can create a custom configuration to define an environment (or _dev container_) that is specific for your repository. Using a dev container allows you to specify a Docker environment for development with a well-defined tool and runtime stack that can reference an image, Dockerfile, or docker-compose. This means that anyone using the repository will have the same tools available to them when they create a codespace. +Pra personalizar los tiempos de ejecución y herramientas en tu codespace, puedes crear una configuración personalizada para definir un ambiente (o _contenedor dev_) que sea específico para tu repositorio. El utilizar un contenedor dev te permite especificar un ambiente de desarrollo de Docker con una combinación de herramienta y tiempo de ejecución bien definidos que pueden referenciar una imagen, Dockerfile o docker-compose. Esto significa que, cualquiera que utilice el repositorio, tendrá las mismas herramientas disponibles para ellos cuando creen un codespace. -If you don't do any custom 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 "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". +Si no hiciste ninguna configuración personalizada, {% data variables.product.prodname_codespaces %} clonará tu repositorio en un ambiente con la imagen predeterminada del codespace, la cual incluye muchas herramientas, lenguajes y ambientes de tiempo de ejecución. Para obtener más información, consulta la sección "[Configurar Codespaces para tu proyecto](/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)". +También puedes personalizar aspectos de tu ambiente de codespace utilizando un repositorio público de [dotfiles](https://dotfiles.github.io/tutorials/) y la [Sincronización de ajustes](https://code.visualstudio.com/docs/editor/settings-sync). Esta personalización puede incluir preferencias de shell, herramientas adicionales, configuración de editores y extensiones de VS Code. Para obtener más información, consulta la sección "[Personalizar tu codespace](/codespaces/customizing-your-codespace)". ## Acerca de la facturación para {% data variables.product.prodname_codespaces %} -For information on billing for {% data variables.product.prodname_codespaces %}, see "[Managing billing for {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces)." +Para obtener más información sobre la facturación de los {% data variables.product.prodname_codespaces %}, consulta la sección "[Administrar la facturación para los {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces)". -{% data reusables.codespaces.codespaces-spending-limit-requirement %} For information on how organizations owners and billing managers can manage the spending limit for {% data variables.product.prodname_codespaces %} for an organization, see "[Managing your spending limit for {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)." +{% data reusables.codespaces.codespaces-spending-limit-requirement %} Para obtener más información sobre cómo los propietarios de las organizaciones y los gerentes de facturación pueden administrar el límite de gastos de {% data variables.product.prodname_codespaces %} para una organización, consulta la sección "[Administrar tu límite de gastos para {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)". diff --git a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/index.md b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/index.md index a9edf94c66..eed7b1d3fd 100644 --- a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/index.md +++ b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/index.md @@ -1,5 +1,5 @@ --- -title: 'Setting up your project for {% data variables.product.prodname_codespaces %}' +title: 'Configurar tu proyecto para {% data variables.product.prodname_codespaces %}' intro: 'Aprende cómo iniciar con los {% data variables.product.prodname_codespaces %}, incluyendo cómo configurar y hacer ajustes para lenguajes específicos.' product: '{% data reusables.gated-features.codespaces %}' versions: diff --git a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md index d492378b7d..a4811eb079 100644 --- a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md +++ b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md @@ -1,6 +1,6 @@ --- -title: Setting up your C# (.NET) project for Codespaces -shortTitle: Setting up your C# (.NET) project +title: Configurar tu proyecto de C# (.NET) para Codespaces +shortTitle: Configurar tu proyecto de C# (.NET) allowTitleToDifferFromFilename: true product: '{% data reusables.gated-features.codespaces %}' intro: 'Inicia con tu proyecto de C# (.NET) en {% data variables.product.prodname_codespaces %} creando un contenedor dev personalizado.' @@ -25,11 +25,11 @@ Esta guía te muestra cómo configurar tu proyecto de C# (.NET) en {% data varia ## Paso 1: Abre tu proyecto en un codespace -1. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu, and in the **Codespaces** tab, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. +1. Debajo del nombre de repositorio, utiliza el menú desplegable de **Código {% octicon "code" aria-label="The code icon" %}** y, en la pestaña de **Codespaces**, haz clic en {% octicon "plus" aria-label="The plus icon" %} **Codespace nuevo**. ![Botón de codespace nuevo](/assets/images/help/codespaces/new-codespace-button.png) - If you don’t see this option, {% data variables.product.prodname_codespaces %} isn't available for your project. See [Access to {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) for more information. + Si no ves esta opción, entonces los {% data variables.product.prodname_codespaces %} no están disponibles para tu proyecto. Consulta la sección de [Acceso a los {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) para obtener más información. Cuando creas un codespace, tu proyecto se crea en una MV remota dedicada a ti. Predeterminadamente, el contenedor de tu codespace tiene muchos lenguajes de programación y tiempos de ejecución, incluyendo a .NET. También incluye un conjunto de herramientas comunes como git, wget, rsync, openssh y nano. @@ -168,7 +168,7 @@ Ahora que agregaste tu contenedor dev y tienes un entendimiento básico de lo qu 1. En el explorador, expande la carpeta `.devcontainer` y selecciona el archivo `devcontainer.json` del árbol para abrirlo. - ![devcontainer.json file in the Explorer](/assets/images/help/codespaces/devcontainers-options.png) + ![Archivo de devcontainer.json en el explorador](/assets/images/help/codespaces/devcontainers-options.png) 2. Actualiza tu lista de `extensions` en tu archivo `devcontainer.json` para agregar algunas extensiones que son útiles al trabajar con tu proyecto. diff --git a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md index 37de8c0093..e978a2757b 100644 --- a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md +++ b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md @@ -1,6 +1,6 @@ --- -title: Setting up your Java project for Codespaces -shortTitle: Setting up with your Java project +title: Configurar tu proyecto de Java para Codespaces +shortTitle: Configurar tu proyecto de Java intro: 'Inica con tu proyecto de Java en {% data variables.product.prodname_codespaces %} creando un contenedor dev personalizado.' product: '{% data reusables.gated-features.codespaces %}' redirect_from: @@ -24,11 +24,11 @@ Esta guía te muestra cómo configurar tu proyecto de Java en {% data variables. ## Paso 1: Abre tu proyecto en un codespace -1. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu, and in the **Codespaces** tab, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. +1. Debajo del nombre de repositorio, utiliza el menú desplegable de **Código {% octicon "code" aria-label="The code icon" %}** y, en la pestaña de **Codespaces**, haz clic en {% octicon "plus" aria-label="The plus icon" %} **Codespace nuevo**. ![Botón de codespace nuevo](/assets/images/help/codespaces/new-codespace-button.png) - If you don’t see this option, {% data variables.product.prodname_codespaces %} isn't available for your project. See [Access to {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) for more information. + Si no ves esta opción, entonces los {% data variables.product.prodname_codespaces %} no están disponibles para tu proyecto. Consulta la sección de [Acceso a los {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) para obtener más información. Cuando creas un codespace, tu proyecto se crea en una MV remota dedicada a ti. Predeterminadamente, el contenedor para tu codespace tiene muchos lenguajes y tiempos de ejecución, incluyendo Java, nvm, npm, y yarn. También incluye un conjunto de herramientas comunes como git, wget, rsync, openssh y nano. @@ -150,7 +150,7 @@ Ahora que agregaste tu contenedor dev y tienes un entendimiento básico de lo qu 1. En el explorador, selecciona el archivo `devcontainer.json` del árbol para abrirlo. Puede que tengas que expandir la carpeta `.devcontainer` para verlo. - ![devcontainer.json file in the Explorer](/assets/images/help/codespaces/devcontainers-options.png) + ![Archivo de devcontainer.json en el explorador](/assets/images/help/codespaces/devcontainers-options.png) 2. Agrega las siguientes líneas a tu archivo `devcontainer.json` después de `extensions`. diff --git a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md index fdca1050bb..80a332dcdd 100644 --- a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md +++ b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md @@ -1,6 +1,6 @@ --- -title: Setting up your Node.js project for Codespaces -shortTitle: Setting up your Node.js project +title: Configurar tu proyecto de Node.js para Codespaces +shortTitle: Configurar tu proyecto de Node.js intro: 'Inicia con tu proyecto de JavaScript, Node.js o TypeScript en {% data variables.product.prodname_codespaces %} creando un contenedor dev personalizado.' product: '{% data reusables.gated-features.codespaces %}' versions: @@ -28,11 +28,11 @@ Esta guía te muestra cómo configurar tu proyecto de JavaScript, Node.js o Type ## Paso 1: Abre tu proyecto en un codespace -1. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu, and in the **Codespaces** tab, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. +1. Debajo del nombre de repositorio, utiliza el menú desplegable de **Código {% octicon "code" aria-label="The code icon" %}** y, en la pestaña de **Codespaces**, haz clic en {% octicon "plus" aria-label="The plus icon" %} **Codespace nuevo**. ![Botón de codespace nuevo](/assets/images/help/codespaces/new-codespace-button.png) - If you don’t see this option, {% data variables.product.prodname_codespaces %} isn't available for your project. See [Access to {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) for more information. + Si no ves esta opción, entonces los {% data variables.product.prodname_codespaces %} no están disponibles para tu proyecto. Consulta la sección de [Acceso a los {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) para obtener más información. Cuando creas un codespace, tu proyecto se crea en una MV remota dedicada a ti. Predeterminadamente, el contenedor para tu codespace tiene muchos lenguajes y tiempos de ejecución, incluyendo a Node.js, JavaScript, TypeScript, nvm, npm y yarn. También incluye un conjunto de herramientas comunes como git, wget, rsync, openssh y nano. @@ -135,7 +135,7 @@ Ahora que agregaste tu contenedor dev y tienes un entendimiento básico de lo qu 1. En el explorador, selecciona el archivo `devcontainer.json` del árbol para abrirlo. Puede que tengas que expandir la carpeta `.devcontainer` para verlo. - ![devcontainer.json file in the Explorer](/assets/images/help/codespaces/devcontainers-options.png) + ![Archivo de devcontainer.json en el explorador](/assets/images/help/codespaces/devcontainers-options.png) 2. Agrega las siguientes líneas a tu archivo `devcontainer.json` después de `extensions`: diff --git a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md index 23d0b169be..0614b1aee8 100644 --- a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md +++ b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md @@ -1,6 +1,6 @@ --- -title: Setting up your Python project for Codespaces -shortTitle: Setting up your Python project +title: Configurar tu proyecto de Python para Codespaces +shortTitle: Configurar tu proyecto de Python intro: 'Iniciar con tu proyecto de Python en {% data variables.product.prodname_codespaces %} creando un contenedor de dev personalizado.' product: '{% data reusables.gated-features.codespaces %}' versions: @@ -27,11 +27,11 @@ Esta guía te muestra cómo configurar tu proyecto de Python en {% data variable ## Paso 1: Abre tu proyecto en un codespace -1. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu, and in the **Codespaces** tab, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. +1. Debajo del nombre de repositorio, utiliza el menú desplegable de **Código {% octicon "code" aria-label="The code icon" %}** y, en la pestaña de **Codespaces**, haz clic en {% octicon "plus" aria-label="The plus icon" %} **Codespace nuevo**. ![Botón de codespace nuevo](/assets/images/help/codespaces/new-codespace-button.png) - If you don’t see this option, {% data variables.product.prodname_codespaces %} isn't available for your project. See [Access to {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) for more information. + Si no ves esta opción, entonces los {% data variables.product.prodname_codespaces %} no están disponibles para tu proyecto. Consulta la sección de [Acceso a los {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) para obtener más información. @@ -160,7 +160,7 @@ Ahora que agregaste tu contenedor dev y tienes un entendimiento básico de lo qu 1. En el explorador, expande la carpeta `.devcontainer` y selecciona el archivo `devcontainer.json` del árbol para abrirlo. - ![devcontainer.json file in the Explorer](/assets/images/help/codespaces/devcontainers-options.png) + ![Archivo de devcontainer.json en el explorador](/assets/images/help/codespaces/devcontainers-options.png) 2. Actualiza la lista de `extensions` en tu archivo `devcontainer.json` para agregar algunas extensiones que son útiles al trabajar con tu proyecto. 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 new file mode 100644 index 0000000000..3f4e8f4df0 --- /dev/null +++ b/translations/es-ES/content/codespaces/the-githubdev-web-based-editor.md @@ -0,0 +1,106 @@ +--- +title: El editor basado en web de github.dev +intro: 'Utiliza el github.dev {% data variables.product.prodname_serverless %} desde tu repositorio o solicitud de cambios para crear y confirmar cambios.' +versions: + fpt: '*' +type: how_to +miniTocMaxHeadingLevel: 3 +topics: + - Codespaces + - Visual Studio Code + - Developer +shortTitle: Editor basado en la web +redirect_from: + - /codespaces/developing-in-codespaces/web-based-editor +--- + +{% note %} + +**Nota:** el github.dev {% data variables.product.prodname_serverless %} se encuentra acutalmente en vista previa beta. Puedes proporcionar retroalimentación [En nuestros debates](https://github.co/browser-editor-feedback). + +{% endnote %} + +## Acerca de {% data variables.product.prodname_serverless %} + +El {% data variables.product.prodname_serverless %} presenta una experiencia de edición ligera que se ejecuta completamente en tu buscador. Con el {% data variables.product.prodname_serverless %}, puedes navegar por los archivos y repositorios de código abierto desde {% data variables.product.prodname_dotcom %} y hacer y confirmar cambios de código. Puedes abrir cualquier repositorio, bifurcación o solicitud de cambios en el editor. + +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 %} 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. + +## Abrir el {% data variables.product.prodname_serverless %} + +You can open any {% data variables.product.prodname_dotcom %} repository in the {% data variables.product.prodname_serverless %} in either of the following ways: + +- Presiona `.` cuando estés buscando cualquier repositorio o solicitud de cambios en {% data variables.product.prodname_dotcom %}. +- Cambiando la URL de "github.com" a "github.dev". + +## {% data variables.product.prodname_codespaces %} y el {% data variables.product.prodname_serverless %} + +Tanto el {% data variables.product.prodname_serverless %} como los {% data variables.product.prodname_codespaces %} te permiten editar el código directamente desde tu repositorio. Sin embargo, ambos tienen beneficios ligeramente diferentes, dependiendo de tu caso de uso. + +| | {% data variables.product.prodname_serverless %} | {% data variables.product.prodname_codespaces %} +| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| **Costo** | Free. | Costos de cálculo y almacenamiento. Para obtener información sobre los precios, consulta "[Precios de los codespaces](/en/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)". | +| **Disponibilidad** | Disponible para todos en GitHub.com. | Disponible para las organizaciones que utilizan GitHub Team o GitHub Enterprise Cloud. | +| **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. | + +### Seguir trabajando en {% data variables.product.prodname_codespaces %} + +Puedes iniciar tu flujo de trabajo en el {% data variables.product.prodname_serverless %} y seguir trabajando en un codespace, tomando en cuenta que tengas [acceso a {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces). Si intentas acceder a la Vista de Ejecución y Depuración o a la Terminal, se ten notificará que no están disponibles en {% data variables.product.prodname_serverless %}. + +Para seguir trabajando en un codespace, haz clic en **Seguir trabajando en…** y selecciona **Crear codespace nuevo** para crear un codespace en tu rama actual. Antes de que elijas esta opción, debes confirmar cualquier cambio. + +![Una captura de pantalla que muestra el botón "Seguir trabajando en" en la IU](/assets/images/help/codespaces/codespaces-continue-working.png) + +## 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 %}. + +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 %}. + +### Crear una rama nueva + +{% data reusables.codespaces.create-or-switch-branch %} + Cualquier cambio sin confirmar que hayas hecho en tu rama antigua estará disponible en la nueva. + +### Confirmar tus cambios + +{% data reusables.codespaces.source-control-commit-changes %} +5. Una vez que hayas confirmado tus cambios, estos se subirán automáticamente a tu rama de {% data variables.product.prodname_dotcom %}. +### Crear una solicitud de extracción + +{% data reusables.codespaces.source-control-pull-request %} + +### Trabajar con una solicitud de cambios existente + +Puedes utilizar el {% data variables.product.prodname_serverless %} para trabajar con una solicitud de cambios existente. + +1. Navega hasta la solicitud de cambios que te gustaría utilizar en el {% data variables.product.prodname_serverless %}. +2. Presiona `.` para abrir la solicitud de cambios en el {% data variables.product.prodname_serverless %}. +3. Una vez que hayas hecho cualquier cambio, confírmalo utilizando los pasos en [Confirmar tus cambios](#commit-your-changes). Tus cambios se confirmarán directamente en la rama, no es necesario subirlos. + +## 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 %}. + +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 %}. + + +## Solución de problemas + +Si tienes problemas para abrir el {% data variables.product.prodname_serverless %}, intenta lo siguiente: + +- Asegúrate de estar firmado en {% data variables.product.prodname_dotcom %}. +- Inhabilita cualquier bloqueador de anuncios. +- Utiliza una ventana de tu buscador que no esté en modo incógnito 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 %}. diff --git a/translations/es-ES/content/codespaces/troubleshooting/codespaces-logs.md b/translations/es-ES/content/codespaces/troubleshooting/codespaces-logs.md index 414e739d12..bde3d0b04b 100644 --- a/translations/es-ES/content/codespaces/troubleshooting/codespaces-logs.md +++ b/translations/es-ES/content/codespaces/troubleshooting/codespaces-logs.md @@ -1,6 +1,6 @@ --- title: Bitácoras de los codespaces -intro: 'Overview of the logging locations used by {% data variables.product.prodname_codespaces %}.' +intro: 'Resumen de las ubicaciones de inicio de sesión que utiliza {% data variables.product.prodname_codespaces %}.' product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' @@ -12,43 +12,43 @@ shortTitle: Bitácoras de los codespaces --- -Information on {% data variables.product.prodname_codespaces %} is output to three different logs: +La información de {% data variables.product.prodname_codespaces %} se emite en tres bitácoras diferentes: -- Codespace logs -- Creation logs -- Extension logs ({% data variables.product.prodname_vscode %} desktop) or Browser console logs ({% data variables.product.prodname_vscode %} in the web) +- Bitácoras de Codespace +- Bitácoras de creación +- Bitácoras de extensión (en {% data variables.product.prodname_vscode %} para escritorio) o bitácoras de consola de buscador (en {% data variables.product.prodname_vscode %} web) -## Codespace logs +## Bitácoras de Codespace -These logs contain detailed information about the codespace, the container, the session, and the {% data variables.product.prodname_vscode %} environment. They are useful for diagnosing connection issues and other unexpected behavior. For example, the codespace freezes but the "Reload Windows" option unfreezes it for a few minutes, or you are randomly disconnected from the codespace but able to reconnect immediately. +Estas bitácoras contienen información detallada sobre los codespaces, el contenedor, la sesión y el ambiente de {% data variables.product.prodname_vscode %}. Son útiles para diagnosticar los problemas de conexión y otros comportamientos inesperados. Por ejemplo, el codespace se congela pero la opción de "Recargar Windows" lo descongela por algunos minutos, o se te desconecta aleatoriamente del codespace, pero te puedes volver a conectar de inmediato. -1. If you are using {% data variables.product.prodname_codespaces %} in the browser, ensure that you are connected to the codespace you want to debug. -2. Open the Command Palette (`Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows)) and type **Export logs**. Select **Codespaces: Export Logs** from the list to download the logs. -3. Define where to save the zip archive of logs then click **Save** (desktop) or click **OK** (web). -4. If you are using {% data variables.product.prodname_codespaces %} in the browser, right-click on the zip archive of logs from the Explorer view and select **Download…** to download them to your local machine. +1. Si estás utilizando {% data variables.product.prodname_codespaces %} en el buscador, asegúrate de que estés conectado al codespace que quieres depurar. +2. Abre la paleta de comandos (`Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows)) y teclea **Exportar bitácoras**. Selecciona **Codespaces: Exportar Bitácoras** de la lista para descargar las bitácoras. +3. Define dónde guardar el archivo zip de las bitácoras y luego haz clic en **Guardar** (escritorio) o en **OK** (web). +4. Si estás utilizando {% data variables.product.prodname_codespaces %} en el buscador, haz clic derecho en el archivo zip de las bitácoras desde la vista de explorador y selecciona **Download…** para descargarlas en tu máquina local. -## Creation logs +## Bitácoras de creación -These logs contain information about the container, dev container, and their configuration. They are useful for debugging configuration and setup problems. +Estas bitácoras contienen información sobre el contenedor, el contenedor dev y sus configuraciones. Son útiles para depurar la configuración y solucionar problemas. -1. Connect to the codespace you want to debug. -2. Open the Command Palette (`Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows)) and type **Creation logs**. Select **Codespaces: View Creation Log** from the list to open the `creation.log` file. +1. Conéctate al codespace que quieras depurar. +2. Abre la paleta de comandos (`Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows)) y teclea **Creation logs**. Selecciona **Codespaces: View Creation Log** de la lista para abrir el archivo `creation.log`. -If you want to share the log with support, you can copy the text from the creation log into a text editor and save the file locally. +Si quieres compartir la bitácora con soporte, puedes copiar el texto de la bitácora de creación en un editor de texto y guardar el archivo localmente. -## Extension logs +## Bitácoras de extensión -These logs are available for {% data variables.product.prodname_vscode %} desktop users only. They are useful if it seems like the {% data variables.product.prodname_codespaces %} extension or {% data variables.product.prodname_vscode %} editor are having issues that prevent creation or connection. +Estas bitácoras se encuentran disponibles únicamente para los usuarios de escritorio de {% data variables.product.prodname_vscode %}}. Son útiles en caso de que parezca que la extensión de {% data variables.product.prodname_codespaces %} o el editor de {% data variables.product.prodname_vscode %} estén teniendo problemas que prevengan la creación o conexión. -1. In {% data variables.product.prodname_vscode %}, open the Command Palette. -2. Type **Logs** and select **Developer: Open Extension Logs Folder** from the list to open the extension log folder in your system's file explorer. +1. En {% data variables.product.prodname_vscode %}, abre la paleta de comandos. +2. Teclea **Logs** y selecciona **Desarrollador: Abrir la Carpeta de Bitácoras de Extensión** desde la lista para abrir dicha carpeta en el explorador de archivos de tu sistema. -From this view, you can access logs generated by the various extensions that you use in {% data variables.product.prodname_vscode %}. You will see logs for GitHub Codespaces, GitHub Authentication, and Git, in addition to any other extensions you have enabled. +Desde esta vista, puedes acceder a las bitácoras que generan las diversas extensiones que utilizas en {% data variables.product.prodname_vscode %}. Verás las bitácoras de GitHub Codespaces, GitHub Authentication y Git, adicionalmente a cualquier otra extensión que hayas habilitado. -## Browser console logs +## Bitácoras de consola de buscador -These logs are useful only if you want to debug problems with using {% data variables.product.prodname_codespaces %} in the browser. They are useful for debugging problems creating and connecting to {% data variables.product.prodname_codespaces %}. +Estas bitácoras son útiles únicamente si quieres depurar problemas con el uso de {% data variables.product.prodname_codespaces %} en el buscador. Son útiles para depurar problemas creando y conectándose a los {% data variables.product.prodname_codespaces %}. -1. In the browser window for the codespace you want to debug, open the developer tools window. -2. Display the "Console" tab and click **errors** in the left side bar to show only the errors. -3. In the log area on the right, right-click and select **Save as** to save a copy of the errors to your local machine. ![Save errors](/assets/images/help/codespaces/browser-console-log-save.png) +1. En la ventana del buscador del codespace que quieres depurar, abre la ventana de herramientas de desarrollador. +2. Muestra la pestaña de "Consola" y haz clic en **errores** en la barra lateral izquierda para mostrar únicamente los errores. +3. En el área de bitácora a la derecha, da clic derecho y selecciona **Guardar como** para guardar una copia de los errores en tu máquina local. ![Guardar los errores](/assets/images/help/codespaces/browser-console-log-save.png) diff --git a/translations/es-ES/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md b/translations/es-ES/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md index 517663a638..311f28b41b 100644 --- a/translations/es-ES/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md +++ b/translations/es-ES/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md @@ -1,27 +1,27 @@ --- -title: Exporting changes to a branch -intro: This article provides steps for exporting your codespace changes to a branch. +title: Exportar los cambios a una rama +intro: Este artículo proporciona los pasos para exportar los cambios de tu codespace a una rama. product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' type: reference topics: - Codespaces -shortTitle: Exporting changes +shortTitle: Exportar cambios --- -## Exporting changes to a branch +## Exportar los cambios a una rama -While using {% data variables.product.prodname_codespaces %}, you may want to export your changes to a branch without launching a your codespace. +Al utilizar {% data variables.product.prodname_codespaces %} podrías querer exportar tus cambios a una rama sin lanzarlos a tu codespace. -This can be useful when you have hit a [spending limit](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces) or have a general issue accessing your codespace. +Esto puede ser útil cuando hayas llegado a un [límite de gastos](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces) o tengas un problema general para acceder a tu codespace. -To export your changes: +Para exportar tus cambios: -1. Browse to the "Your Codespaces" page at [github.com/codespaces](https://github.com/codespaces) or, for an individual repository, click the **{% octicon "code" aria-label="The code icon" %} Code** menu. -2. Click the ellipsis (**...**) to the right of the codespace you want to export from. -3. Select **{% octicon "git-branch" aria-label="The git branch icon" %} Export changes to branch**. +1. Navega a la página de "Tus Codespaces" en [github.com/codespaces](https://github.com/codespaces) o, en el caso de un repositorio individual, haz clic en el menú **{% octicon "code" aria-label="The code icon" %} Código**. +2. Haz clic en los puntos suspensivos (**...**) a la derecha del codespace desde el cuál quieras exportar. +3. Selecciona **{% octicon "git-branch" aria-label="The git branch icon" %} Exportar cambios a la rama**. - ![Export changes to a branch](/assets/images/help/codespaces/export-changes-to-a-branch.png) + ![Exportar cambios a una rama](/assets/images/help/codespaces/export-changes-to-a-branch.png) -4. From the popover, select **Create branch**. +4. Desde el anuncio emergente, selecciona **Crear rama**. diff --git a/translations/es-ES/content/codespaces/troubleshooting/index.md b/translations/es-ES/content/codespaces/troubleshooting/index.md index 1964f8c1ad..3e967cb7d7 100644 --- a/translations/es-ES/content/codespaces/troubleshooting/index.md +++ b/translations/es-ES/content/codespaces/troubleshooting/index.md @@ -1,8 +1,8 @@ --- -title: Troubleshooting Codespaces +title: Solucionar problemas en los Codespaces shortTitle: Solución de problemas product: '{% data reusables.gated-features.codespaces %}' -intro: 'These guides provide information for troubleshooting {% data variables.product.prodname_codespaces %}' +intro: 'Estas guías te proporcionan información para solucionar los problemas de los {% data variables.product.prodname_codespaces %}' versions: fpt: '*' redirect_from: diff --git a/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md b/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md index 30390bd42e..60cf28e9fc 100644 --- a/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md +++ b/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md @@ -1,25 +1,25 @@ --- -title: Troubleshooting Codespaces clients -intro: 'You can use {% data variables.product.prodname_codespaces %} in your browser or through {% data variables.product.prodname_vscode %}. This article provides troubleshooting steps for common client issues.' +title: Solucionar problemas de los clientes de Codespaces +intro: 'Puedes utilizar {% data variables.product.prodname_codespaces %} en tu buscador o a través de {% data variables.product.prodname_vscode %}. Este artículo proporciona pasos de solución de problemas para los problemas comunes de los clientes.' product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' type: reference topics: - Codespaces -shortTitle: Codespaces clients +shortTitle: Clientes de codespaces --- ## Solución de problemas de {% data variables.product.prodname_vscode %} -When you connect a desktop version of {% data variables.product.prodname_vscode %} to a codespace, you will notice few differences compared with working in a normal workspace but the experience will be fairly similar. +Cuando conectas a una versión de escritorio de {% data variables.product.prodname_vscode %} a un codespace, notarás algunas cuantas diferencias en comparación con trabajar en un espacio de trabajo normal, pero la experiencia será bastante similar. -When you open a codespace in your browser using {% data variables.product.prodname_vscode %} in the web, you will notice more differences. For example, some key bindings will be different or missing, and some extensions may behave differently. For a summary, see: "[Known limitations and adaptions](https://code.visualstudio.com/docs/remote/codespaces#_known-limitations-and-adaptations)" in the {% data variables.product.prodname_vscode %} docs. +Cuando abres un codespace en tu buscador utilizando {% data variables.product.prodname_vscode %} en la web, notarás más diferencias. Por ejemplo, algunas uniones de teclas serán diferentes o no estarán y algunas extensiones podrían comportarse de forma diferente. Para obtener un resumen, consulta la sección "[Adaptaciones y limitaciones conocidas](https://code.visualstudio.com/docs/remote/codespaces#_known-limitations-and-adaptations)" en los documentos de {% data variables.product.prodname_vscode %}. -You can check for known issues and log new issues with the {% data variables.product.prodname_vscode %} experience in the [`microsoft/vscode`](https://github.com/microsoft/vscode/issues?q=is%3Aissue+is%3Aopen+codespaces) repository. +Puedes revisar si hay problemas conocidos y registrar problemas nuevos con la experiencia de {% data variables.product.prodname_vscode %} en el repositorio [`microsoft/vscode`](https://github.com/microsoft/vscode/issues?q=is%3Aissue+is%3Aopen+codespaces). ## Solución de problemas del buscador -If you encounter issues using codespaces in a browser that is not Chromium-based, try switching to a Chromium-based browser, or check for known issues with your browser in the `microsoft/vscode` repository by searching for issues labeled with the name of your browser, such as [`firefox`](https://github.com/microsoft/vscode/issues?q=is%3Aissue+is%3Aopen+label%3Afirefox) or [`safari`](https://github.com/Microsoft/vscode/issues?q=is%3Aopen+is%3Aissue+label%3Asafari). +Si encuentras problemas para utilizar los codespaces en un buscador que no esté basado en Chromium, intenta cambiar a uno que sí lo esté o revisa si hay problemas conocidos con tu buscador en el repositorio de `microsoft/vscode` buscando aquellos etiquetados con el nombre de dicho buscador, tal como [`firefox`](https://github.com/microsoft/vscode/issues?q=is%3Aissue+is%3Aopen+label%3Afirefox) o [`safari`](https://github.com/Microsoft/vscode/issues?q=is%3Aopen+is%3Aissue+label%3Asafari). -If you encounter issues using codespaces in a Chromium-based browser, you can check if you're experiencing another known issue with {% data variables.product.prodname_vscode %} in the [`microsoft/vscode`](https://github.com/microsoft/vscode/issues) repository. +Si encuentras problemas al utilizar codespaces en un buscador basado en Chromium, puedes verificar si estás experimentando algún otro problema conocido de {% data variables.product.prodname_vscode %} en el repositorio [`microsoft/vscode`](https://github.com/microsoft/vscode/issues). diff --git a/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md b/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md index 837290a186..2da7c6005b 100644 --- a/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md +++ b/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md @@ -1,46 +1,46 @@ --- -title: Troubleshooting creation and deletion of Codespaces -intro: 'This article provides troubleshooting steps for common issues you may experience when creating or deleting a codespace, including storage and configuration issues.' +title: Solucionar problemas de creación y borrado de Codespaces +intro: 'Este artículo te muestra los pasos para la solución de problemas comunes que podrías experimentar al crear o borrar un codespace, incluyendo los de almacenamiento y configuración.' product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' type: reference topics: - Codespaces -shortTitle: Creation and deletion +shortTitle: Creación y borrado --- -## Creating codespaces +## Crear codespaces -### No access to create a codespace -{% data variables.product.prodname_codespaces %} are not available for all repositories. If the “Open with Codespaces” button is missing, {% data variables.product.prodname_codespaces %} may not be available for that repository. Para obtener más información, consulta la sección "[Crear un codespace](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces)". +### Sin acceso para crear un codespace +Los {% data variables.product.prodname_codespaces %} no están disponibles para todos los repositorios. Si no se muestra el botón de "Abrir con Codespaces", {% data variables.product.prodname_codespaces %} podría no estar disponible para dicho repositorio. Para obtener más información, consulta la sección "[Crear un codespace](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces)". -If you believe your organization has [enabled {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization#about-enabling-codespaces-for-your-organization), make sure that an organization owner or billing manager has set the spending limit for {% data variables.product.prodname_codespaces %}. Para obtener más información, consulta la sección "[Administrar tu límite de gastos para {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)". +Si crees que tu organización sí [habilitó los {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization#about-enabling-codespaces-for-your-organization), asegúrate de que un propietario de la organización o gerente de facturación haya configurado el límite de gastos para los {% data variables.product.prodname_codespaces %}. Para obtener más información, consulta la sección "[Administrar tu límite de gastos para {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)". -### Codespace does not open when created +### El Codespace no abre cuando se crea -If you create a codespace and it does not open: +Si creas un codespace y este no abre: -1. Try reloading the page in case there was a caching or reporting problem. -2. Go to your {% data variables.product.prodname_codespaces %} page: https://github.com/codespaces and check whether the new codespace is listed there. The process may have successfully created the codespace but failed to report back to your browser. If the new codespace is listed, you can open it directly from that page. -3. Retry creating the codespace for the repository to rule out a transient communication failure. +1. Intenta volver a cargar la página en caso de que hubiera un error de caché o problema reportado. +2. Dirígete a tu página de {% data variables.product.prodname_codespaces %}: https://github.com/codespaces y verifica si el codespace nuevo se listó ahí. El proceso podría haber creado el codespace con éxito pero falló en reportarlo de vuelta a tu buscador. Si el codespace nuevo se ve listado, puedes abrirlo directamente desde esta página. +3. Reintenta crear el codespace para que el repositorio descarte un fallo de comunicación transitorio. -If you still cannot create a codespace for a repository where {% data variables.product.prodname_codespaces %} are available, {% data reusables.codespaces.contact-support %} +Si aún no puedes crear un codespace para un repositorio en donde esté disponible {% data variables.product.prodname_codespaces %}, contacta a {% data reusables.codespaces.contact-support %}. -## Deleting codespaces +## Borrar codespaces -The owner of a codespace has full control over it and only they can delete their codespaces. You cannot delete a codespace created by another user. +El propietario de un codespace tiene control total sobre este y solo él podrá borrarlo. No puedes borrar un codespace que otro usuario haya creado. -## Container storage +## Almacenamiento de contenedores -Cuando creas un codespace, este tiene una cantidad de almacenamiento finita y, con el tiempo, podría que necesites liberar espacio. Try running any of the following commands in the {% data variables.product.prodname_codespaces %} terminal to free up storage space. +Cuando creas un codespace, este tiene una cantidad de almacenamiento finita y, con el tiempo, podría que necesites liberar espacio. Intenta ejecutar cualquiera de los comandos siguientes en la terminal de {% data variables.product.prodname_codespaces %} para liberar espacio de almacenamiento. -- Remove packages that are no longer used by using `sudo apt autoremove`. +- Elimina los paquetes que ya no se utilicen usando `sudo apt autoremove`. - Limpia el caché de apt utilizando `sudo apt clean`. -- See the top 10 largest files in the codespace with`sudo find / -printf '%s %p\n'| sort -nr | head -10`. -- Delete unneeded files, such as build artifacts and logs. +- Consulta los 10 archivos más grandes en el codespace con `sudo find / -printf '%s %p\n'| sort -nr | head -10`. +- Borra los archivos innecesarios, tales como los artefactos y bitácoras de compilación. -Some more destructive options: +Algunas opciones más destructivas: - Elimina las imágenes de Docker, redes y contenedores sin utilizar con `docker system prune` (adjunta una `-a` si quieres eliminar todas las imágenes, y `--volumes` si quieres eliminar todos los volúmenes). - Elimina los archivos no rastreados del árbol de trabajo: `git clean -i`. @@ -53,4 +53,4 @@ Some more destructive options: Este codespace se ejecuta acutalmente en modo de recuperación debido a un error del contenedor. ``` -Revisa las bitácoras de creación, actualiza la configuración como lo requieras y ejecuta **Codespaces: Rebuild Container** en la paleta de comandos para volver a intentarlo. For more information, see " [Codespaces logs](/codespaces/troubleshooting/codespaces-logs)" and "[Configuring {% data variables.product.prodname_codespaces %} for your project](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#apply-changes-to-your-configuration)." +Revisa las bitácoras de creación, actualiza la configuración como lo requieras y ejecuta **Codespaces: Rebuild Container** en la paleta de comandos para volver a intentarlo. Para obtener más información, consulta las secciones "[Bitácoras de codespaces](/codespaces/troubleshooting/codespaces-logs)" y "[Configurar {% data variables.product.prodname_codespaces %} en tu proyecto](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#apply-changes-to-your-configuration)". diff --git a/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-dotfiles-for-codespaces.md b/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-dotfiles-for-codespaces.md index fce27faf12..584e066c18 100644 --- a/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-dotfiles-for-codespaces.md +++ b/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-dotfiles-for-codespaces.md @@ -1,6 +1,6 @@ --- -title: Troubleshooting dotfiles for Codespaces -intro: Troubleshooting steps for common dotfiles issues. +title: Solución de problemas de dotfiles para los Codespaces +intro: Pasos de solución de problemas para los problemas comunes con los dotfiles. product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' @@ -10,12 +10,12 @@ topics: shortTitle: Dotfiles --- -If your codespace fails to pick up configuration settings from dotfiles, you should work through the following debugging steps. +Si tu codespace falla en tomar ajustes de configuración de dotfiles, debes trabajar con los siguientes pasos de depuración. 1. Asegúrate que tu repositorio de dotfiles sea público. Si tienes secretos o datos sensibles que quieras utilizar en tu codespace, utiliza los [Secretos de codespace](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces) en vez de los dotfiles privados. 2. Verifica `/workspaces/.codespaces/.persistedshare/dotfiles` para ver si se clonaron tus dotfiles. - - If your dotfiles were cloned, try manually re-running your install script to verify that it is executable. - - If your dotfiles were not cloned, check `/workspaces/.codespaces/.persistedshare/EnvironmentLog.txt` to see if there was a problem cloning them. -3. Verifica `/workspaces/.codespaces/.persistedshare/creation.log` para encontrar problemas posibles. For more information, see [Creation logs](/codespaces/troubleshooting/codespaces-logs#creation-logs). + - Si se clonaron tus dotfiles, intenta volver a ejecutar tu script de instalación manualmente para verificar que sea ejecutable. + - Si tus dotfiles no se clonaron, revisa `/workspaces/.codespaces/.persistedshare/EnvironmentLog.txt` para ver si hubo un problema al clonarlos. +3. Verifica `/workspaces/.codespaces/.persistedshare/creation.log` para encontrar problemas posibles. Para obtener más información, consulta las [bitácoras de creación](/codespaces/troubleshooting/codespaces-logs#creation-logs). -If the configuration from your dotfiles is correctly picked up, but part of the configuration is incompatible with codespaces, use the `$CODESPACES` environment variable to add conditional logic for codespace-specific configuration settings. +Si la configuración de tus dotfiles se tomó correctamente, pero parte de esta es incompatible con los codespaces, utiliza la variable de ambiente `$CODESPACES` para agregar una lógica condicional para los ajustes de configuración específicos de los codespaces. diff --git a/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-port-forwarding-for-codespaces.md b/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-port-forwarding-for-codespaces.md index 1f0bf8b863..2ac89ea1be 100644 --- a/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-port-forwarding-for-codespaces.md +++ b/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-port-forwarding-for-codespaces.md @@ -1,20 +1,20 @@ --- -title: Troubleshooting port forwarding for Codespaces -intro: Troubleshooting steps for common port forwarding issues. +title: Solución de problemas del reenvío de puertos para Codespaces +intro: Pasos de solución de problemas para los problemas comunes del reenvío de puertos. product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' type: reference topics: - Codespaces -shortTitle: Port forwarding +shortTitle: Reenvío de puertos --- -When an application running inside a codespace outputs a port to the console, {% data variables.product.prodname_codespaces %} detects the localhost URL pattern and automatically forwards the port. For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)." +Cuando una aplicación que se ejecuta en un codespace da salida a la consola a un puerto, el {% data variables.product.prodname_codespaces %} detecta el patrón de URL del host local y reenvía el puerto automáticamente. Para obtener más información, consulta la sección "[Reenviar puertos en tu codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)". -If a port is not automatically forwarded, you can forward it manually. For more information, see "[Forwarding a port](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace#forwarding-a-port)." +Si un puerto no se reenvía automáticamente, puedes reenviarlo manualmente. Para obtener más información, consulta la sección "[Reenviar un puerto](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace#forwarding-a-port)". -If port forwarding is set up, check the following: +Si se configura el reenvío de puertos, verifica lo siguiente: -- Use the notification toast or click the URL in Terminal to open the forwarded port. Typing in `localhost:8000` (as an example) to your local machine will not work if you're connected to the codespace via the browser. -- Make sure to check that your application is still running from within your codespace. If your codespace has stopped after a period of inactivity, you'll need to ensure to restart your application once the codespace has restarted. +- Utiliza la alerta de notificación o haz clic en la URL de la Terminal para abrir el puerto reenviado. No funcionará teclear `localhost:8000` (como ejemplo) en tu máquina local si estás conectado al codespace a través del buscador. +- Asegúrate de verificar que tu aplicación aún se esté ejecutando desde dentro de tu codespace. Si tu codespace paró después de un periodo de inactividad, necesitarás garantizar que tu aplicación reinicie una vez que se reinició el codespace. diff --git a/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-your-connection-to-codespaces.md b/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-your-connection-to-codespaces.md index 8599bc1de1..6b23d3403e 100644 --- a/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-your-connection-to-codespaces.md +++ b/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-your-connection-to-codespaces.md @@ -1,6 +1,6 @@ --- -title: Troubleshooting your connection to Codespaces -intro: 'Troubleshooting help for connecting to {% data variables.product.prodname_codespaces %}.' +title: Resolver problemas de tu conexión a Codespaces +intro: 'Ayuda para resolver problemas para conectarse a {% data variables.product.prodname_codespaces %}.' product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' @@ -12,35 +12,35 @@ shortTitle: Conexión ## 503 codespace service unavailable -Codespaces are set to stop after 30 minutes without any activity. If you try to interact with a codespace after it has stopped, you may see a `503 service unavailable` error. +Los codespaces están configurados para detenerse después de pasar 30 minutos sin actividad. Si intentas interactuar con un codespace después de que se detuvo, podrías ver un error de tipo `503 service unavailable`. -- If a **Start** button is shown in {% data variables.product.prodname_vscode %} or in your browser window, click **Start** to reconnect to the codespace. -- Reset your codespace by reloading the window. From the [command palette](/codespaces/codespaces-reference/using-the-command-palette-in-codespaces#accessing-the-command-palette) in {% data variables.product.prodname_vscode %}, click **Developer: Reload Window**. +- Si se muestra un botón de **Inicio** en {% data variables.product.prodname_vscode %} o en tu ventana de buscador, haz clic en **Inicio** para volverte a conectar al codespace. +- Restablece tu codespace volviendo a cargar la ventana. Desde la [paleta de comandos](/codespaces/codespaces-reference/using-the-command-palette-in-codespaces#accessing-the-command-palette) en {% data variables.product.prodname_vscode %}, haz clic en **Desarrollador: Recargar Ventana**. -## Browser cannot connect +## El buscador no se puede conectar -Sometimes you may not be able to access a codespace from your browser. If this happens, go to https://github.com/codespaces and try connecting to the codespace from that page. +Es posible que en ocasiones no puedas acceder a un codespace desde tu buscador. Si esto sucede, dirígete a https://github.com/codespaces e intenta conectarte al codespace desde esa página. - - If the codespace is not listed on that page, check that you are the owner of the codespace you are trying to connect to. You can only open a codespace that you created. The URLs for your codespaces always include your {% data variables.product.company_short %} handle. - - If the codespace is listed but you cannot connect from that page, check whether you can connect using a different browser. + - Si el codespce no se lista en esa página, verifica que seas el propietario del codespace al cual intentas conectarte. Solo puedes abrir un codespace que tú mismo hayas creado. Las URL de tus codespaces siempre incluyen tu manejo de {% data variables.product.company_short %}. + - Si el codespace se enlista pero no puedes conectarte desde esa página, revisa si puedes conectarte utilizando un buscador diferente. -Your company network may be blocking the connection. If possible, check any logging for rejected connections on your device. +Tu red empresarial puede estar bloqueando la conección. De ser posible, revisa cualquier registro en bitácora para ver si hay conexiones rechazadas en tu dispositivo. -If you still cannot connect, {% data reusables.codespaces.contact-support %} +Si aún no puedes conectarte, {% data reusables.codespaces.contact-support %} -## {% data variables.product.prodname_github_codespaces %} extension for {% data variables.product.prodname_vscode %} cannot connect +## La extensión de {% data variables.product.prodname_github_codespaces %} para {% data variables.product.prodname_vscode %} no puede conectarse -If you cannot connect to a codespace from {% data variables.product.prodname_vscode %} desktop, use the following troubleshooting steps. +Si no puedes conectarte a un codespace desde la versión de escritorio de {% data variables.product.prodname_vscode %}, utiliza los siguientes pasos de solución de problemas. -1. Check that you have the latest version of the {% data variables.product.prodname_github_codespaces %} extension installed. The extension is a preview release and frequent updates are released. - 1. In {% data variables.product.prodname_vscode %}, display the "Extensions" tab. - 2. Select the {% data variables.product.prodname_github_codespaces %} extension to display the extension's overview page. - 3. If an update is available, a button is shown, click **Update to X.X.X** to upgrade to the latest version. -2. Check whether you are using the stable build of {% data variables.product.prodname_vscode %} or the [{% data variables.product.prodname_vscode %} Insiders](https://code.visualstudio.com/insiders/) release (nightly updates). If you are using the insiders release, try installing the [stable build](https://code.visualstudio.com/). -3. Your company network may be blocking the connection. If possible, check any logging for rejected connections on your device. +1. Verifica que tengas instalada la última versión de {% data variables.product.prodname_github_codespaces %}. La extensión es un lanzamiento de vista previa y se lanzan actualizaciones frecuentemente. + 1. En {% data variables.product.prodname_vscode %}, muestra la pestaña de "Extensiones". + 2. Selecciona la extensión de {% data variables.product.prodname_github_codespaces %} para mostrar la página de resumen de extensiones. + 3. Si hay alguna actualización disponible, se mostrará un botón. Haz clic en **Actualizar a X.X.X** para actualizar a la versión más reciente. +2. Verifica si estás utilizando la compilación estable de {% data variables.product.prodname_vscode %} o el lanzamiento de [{% data variables.product.prodname_vscode %} Insiders](https://code.visualstudio.com/insiders/) (con actualizaciones nocturnas). Si estás utilizando el lanzamiento de insiders, intenta instalar la [compilación estable](https://code.visualstudio.com/). +3. Tu red empresarial puede estar bloqueando la conección. De ser posible, revisa cualquier registro en bitácora para ver si hay conexiones rechazadas en tu dispositivo. -If you still cannot connect, {% data reusables.codespaces.contact-support %} +Si aún no puedes conectarte, {% data reusables.codespaces.contact-support %} -### The codespace has latency issues +### El codespace tiene problemas de latencia -If the codespace seems particularly slow or has latency issues, it is possible that it has been created in a region that is far from you. To resolve this, you can [manually set your {% data variables.product.prodname_github_codespaces %} region](/codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces). +Si el codespace se ve particularmente lento o tiene problemas de latencia, es posible que se haya creado en una región lejos de ti. Para resolverlo, puedes [configurar manualmente tu región de {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces). diff --git a/translations/es-ES/content/codespaces/troubleshooting/working-with-support-for-codespaces.md b/translations/es-ES/content/codespaces/troubleshooting/working-with-support-for-codespaces.md index 29b9d1f0ec..f34a62e187 100644 --- a/translations/es-ES/content/codespaces/troubleshooting/working-with-support-for-codespaces.md +++ b/translations/es-ES/content/codespaces/troubleshooting/working-with-support-for-codespaces.md @@ -1,6 +1,6 @@ --- -title: Working with support for Codespaces -intro: 'Tips on getting the best help from support for {% data variables.product.prodname_codespaces %}.' +title: Trabajar con el soporte para Codespaces +intro: 'Tips para obtener la mejor ayuda del soporte para {% data variables.product.prodname_codespaces %}.' product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' @@ -10,24 +10,24 @@ topics: shortTitle: Trabajar con soporte --- -Before support can help you with problems with codespaces, you need to know the name of the codespace and its codespaces ID (identifier). In addition, support may ask you to share some logs with them. For more information, see "[Codespaces logs](/codespaces/troubleshooting/codespaces-logs)" and "[About GitHub Support](/github/working-with-github-support/about-github-support)." +Antes de que soporte pueda ayudarte con los problemas de los codespaces, necesitas saber el nombre del codespace y su ID de codespaces (identificador). Adicionalmente, soporte podría pedirte que le compartas algunas bitácoras. Para obtener más información, consulta las secciones "[Bitácoras de codespaces](/codespaces/troubleshooting/codespaces-logs)" y "[Acerca de GitHub Support](/github/working-with-github-support/about-github-support)". -### Codespace names +### Nombres de los codespaces -Each codespace has a unique name that is a combination of your {% data variables.product.company_short %} handle, the repository name, and some random characters. The additional characters allow you to have codespaces for different branches in the same repository. For example: `octocat-myrepo-gmc7`. +Cada codespace tiene un nombre único que es una combinación de tu manejo de {% data variables.product.company_short %}, el nombre del repositorio, y algunos caracteres aleatorios. Los caracteres adicionales te permiten tener codespaces para ramas diferentes en el mismo repositorio. Por ejemplo: `octocat-myrepo-gmc7`. -To find the name of a codespace: +Para encontrar el nombre de un codespace: -- Open the codespace in the browser. The subdomain of the URL is the name of the codespace. For example: `https://octocat-myrepo-gmc7.github.dev` is the URL for the `octocat-myrepo-gmc7` codespace. -- If you cannot open a codespace, you can access the name in {% data variables.product.product_name %} on https://github.com/codespaces. The name is shown in a pop-up when you hover over the **Open in browser** option on https://github.com/codespaces. ![Codespace name shown on hover over](/assets/images/help/codespaces/find-codespace-name-github.png) +- Abre el codespace en el buscador. El subdominio de la URL es el nombre del codespace. Por ejemplo: `https://octocat-myrepo-gmc7.github.dev` es la URL del codespace `octocat-myrepo-gmc7`. +- Si no puedes abrir un codespace, puedes acceder al nombre en {% data variables.product.product_name %} en https://github.com/codespaces. El nombre se muestra en una ventana emergente cuando pasas el puntero del mouse sobre la opción **Open in browser** en https://github.com/codespaces. ![Nombre del codespace que se muestra al pasar el puntero del mouse](/assets/images/help/codespaces/find-codespace-name-github.png) -The name the codespace is also included in many of the log files. For example, in the codespace logs as the value of `friendlyName`, in the {% data variables.product.prodname_github_codespaces %} extension log after `making GET request for`, and in the browser console log after `clientUrl`. For more information, see "[Codespaces logs](/codespaces/troubleshooting/codespaces-logs)." +El nombre del codespace también se incluye en muchos otros archivos de bitácora. Por ejemplo, en las bitácoras de codespace como el valor de `friendlyName`, en la bitácora de extensiones de {% data variables.product.prodname_github_codespaces %} después de `making GET request for` y en la bitácora de consola del buscador, después de `clientUrl`. Para obtener más información, consulta la sección "[Bitácoras de los codespaces](/codespaces/troubleshooting/codespaces-logs)". -### Codespaces IDs +### ID de los codespaces -Every codespace also has an ID (identifer). This is not shown by default in {% data variables.product.prodname_vscode %} so you may need to update the settings for the {% data variables.product.prodname_github_codespaces %} extension before you can access the ID. +Cada codespace también tiene un ID (identificador). Este no se muestra predeterminadamente en {% data variables.product.prodname_vscode %}, así que podrías tener que actualizar los ajustes para la extensión de {% data variables.product.prodname_github_codespaces %} antes de que puedas acceder a la ID. -1. In {% data variables.product.prodname_vscode %}, browser or desktop, in the Activity Bar on the left, click **Remote Explorer** to show details for the codespace. -2. If the sidebar includes a "Codespace Performance" section, hover over the "Codespace ID" and click the clipboard icon to copy the ID. -3. If the information is not shown, click {% octicon "gear" aria-label="The gear icon" %}, in the bottom-left corner of the Activity Bar, to display the "Settings" tab. -4. Expand **Extensions** and click **{% data variables.product.prodname_github_codespaces %}** to display the settings for the extension. Then enable **Show Performance Explorer** to display the "Codespace Performance" section in the sidebar. ![Codespace ID and settings required to display performance information](/assets/images/help/codespaces/find-codespace-id.png) +1. En {% data variables.product.prodname_vscode %}, ya sea la versión de buscador o de escritorio, en la barra de actividad a la izquierda, haz clic en **Explorador remoto** para que se muestren los detalles del codespace. +2. Si la barra lateral incluye una sección de "Rendimiento del Codespace", pasa el puntero del mouse sobre "ID del Codespace" y haz clic en el icono de portapapeles para copiar la ID. +3. Si no se muestra la información, haz clic en {% octicon "gear" aria-label="The gear icon" %} en la esquina inferior izquierda de la barra de actividad para mostrar la pestaña de "Ajustes". +4. Expande las **Extensiones** y haz clic en **{% data variables.product.prodname_github_codespaces %}** para mostrar los ajustes de la extensión. Entonces, habilita el **Explorador para mostrar el rendmiento** para mostrar la sección de "Rendimiento del Codespace" en la barra lateral. ![ID y ajustes del codespace requeridos para mostrar la información de rendimiento](/assets/images/help/codespaces/find-codespace-id.png) diff --git a/translations/es-ES/content/communities/documenting-your-project-with-wikis/about-wikis.md b/translations/es-ES/content/communities/documenting-your-project-with-wikis/about-wikis.md index 6415e52d1c..27d5968259 100644 --- a/translations/es-ES/content/communities/documenting-your-project-with-wikis/about-wikis.md +++ b/translations/es-ES/content/communities/documenting-your-project-with-wikis/about-wikis.md @@ -34,4 +34,4 @@ Puedes editar las wikis directamente en {% data variables.product.product_name % - "[Crear un pie de página o barra lateral para tu wiki](/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki)" - "[Editar el contenido de una wiki](/communities/documenting-your-project-with-wikis/editing-wiki-content)" - "[Ver el historial de cambios de una wiki](/articles/viewing-a-wiki-s-history-of-changes)" -- "[Buscar wikis](/articles/searching-wikis)" +- "[Buscar wikis](/search-github/searching-on-github/searching-wikis)" diff --git a/translations/es-ES/content/communities/index.md b/translations/es-ES/content/communities/index.md index 126cb40aed..739b58305d 100644 --- a/translations/es-ES/content/communities/index.md +++ b/translations/es-ES/content/communities/index.md @@ -1,7 +1,7 @@ --- title: Crear comunidades shortTitle: Crear comunidades -intro: 'Learn best practices for moderating and setting up collaborative, safe, and effective communities using GitHub’s community-tested tools.' +intro: 'Aprende las mejores prácticas para moderar y configurar comunidades colaborativas, seguras y efectivas utilizando las herramientas que ya probó la comunidad de GitHub.' redirect_from: - /categories/building-a-strong-community - /github/building-a-strong-community diff --git a/translations/es-ES/content/communities/moderating-comments-and-conversations/locking-conversations.md b/translations/es-ES/content/communities/moderating-comments-and-conversations/locking-conversations.md index f81429388a..d757fd20f7 100644 --- a/translations/es-ES/content/communities/moderating-comments-and-conversations/locking-conversations.md +++ b/translations/es-ES/content/communities/moderating-comments-and-conversations/locking-conversations.md @@ -20,7 +20,7 @@ Bloquear una conversación genera un evento de cronología que queda visible par Mientras una conversación está bloqueada, solo [las personas con acceso de escritura](/articles/repository-permission-levels-for-an-organization/) y [los propietarios y colaboradores del repositorio](/articles/permission-levels-for-a-user-account-repository/#collaborator-access-for-a-repository-owned-by-a-user-account) pueden agregar, ocultar y eliminar comentarios. -Para buscar conversaciones bloqueadas en un repositorio que no está archivado, puedes usar los calificadores de búsqueda `is:locked` y `archived:false`. Las conversaciones se bloquean de forma automática en los repositorios archivados. Para obtener más información, consulta "[Buscar propuestas y solicitudes de extracción](/articles/searching-issues-and-pull-requests#search-based-on-whether-a-conversation-is-locked)". +Para buscar conversaciones bloqueadas en un repositorio que no está archivado, puedes usar los calificadores de búsqueda `is:locked` y `archived:false`. Las conversaciones se bloquean de forma automática en los repositorios archivados. Para obtener más información, consulta "[Buscar propuestas y solicitudes de extracción](/search-github/searching-on-github/searching-issues-and-pull-requests#search-based-on-whether-a-conversation-is-locked)". 1. De manera opcional, escribe un comentario que explique el motivo por el cual estás bloqueando la conversación. 2. En el margen derecho de la propuesta o solicitud de extracción, o por encima del cuadro de comentarios de la página de confirmaciones, haz clic en **Lock conversation** (Bloquear conversación). ![Enlace Lock conversation (Bloquear conversación)](/assets/images/help/repository/lock-conversation.png) diff --git a/translations/es-ES/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md b/translations/es-ES/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md index f864925127..549748d836 100644 --- a/translations/es-ES/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md +++ b/translations/es-ES/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md @@ -15,7 +15,7 @@ shortTitle: Archivo de salud de la comunidad ## Acerca de los archivos predeterminados del estado de la comunidad -You can add default community health files to a public repository called `.github`, in the root of the repository or in the `docs` or `.github` folders. +Puedes agregar archivos de salud comunitaria predeterminados a un repositorio público llamado `.github` en la raíz del repositorio o en las carpetas de `docs` o de `.github` . {% data variables.product.product_name %} utilizará y mostrará los archivos predeterminados para cualquier repositorio que pertenezca a la cuenta que no tenga su propio archivo de ese tipo en cualquiera de los siguientes lugares: - la raíz del repositorio @@ -49,4 +49,4 @@ No puedes crear un archivo de licencia predeterminado. Los archivos de licencia 4. Asegúrate de que el estado del repositorio se encuentre configurado en **Público** (los repositorios para los archivos predeterminados no pueden ser privados). ![Botones de selección para seleccionar el estado público o privado](/assets/images/help/repository/create-repository-public-private.png) {% data reusables.repositories.initialize-with-readme %} {% data reusables.repositories.create-repo %} -7. En el repositorio, crea uno de los archivos admitidos de estado de la comunidad. Las plantillas de reporte de problemas{% ifversion fpt or ghae or ghes %} y su archivo de configuración{% endif %} deben estar en una carpeta llamada `.github/ISSUE_TEMPLATE`. All other supported files may be in the root of the repository, the `.github` folder, or the `docs` folder. Para obtener más información, consulta "[Crear nuevos archivos](/articles/creating-new-files/)." +7. En el repositorio, crea uno de los archivos admitidos de estado de la comunidad. Las plantillas de reporte de problemas{% ifversion fpt or ghae or ghes %} y su archivo de configuración{% endif %} deben estar en una carpeta llamada `.github/ISSUE_TEMPLATE`. El resto de los archivos compatibles podrían estar en la raíz del repositorio, en la carpeta de `.github` o en la de `docs`. Para obtener más información, consulta "[Crear nuevos archivos](/articles/creating-new-files/)." diff --git a/translations/es-ES/content/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels.md b/translations/es-ES/content/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels.md index a03e022355..b5c0910e80 100644 --- a/translations/es-ES/content/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels.md +++ b/translations/es-ES/content/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels.md @@ -12,7 +12,7 @@ topics: shortTitle: Motivar a los contribuyentes --- -Puedes aplicar la etiqueta `good first issue` (primera buena propuesta) a las propuestas de tu repositorio público para que las personas puedan encontrarlas cuando busquen por etiquetas. Para obtener más información acerca de buscar por etiquetas, consulta "[Buscar propuestas y solicitudes de extracción](/articles/searching-issues-and-pull-requests/#search-by-label)". +Puedes aplicar la etiqueta `good first issue` (primera buena propuesta) a las propuestas de tu repositorio público para que las personas puedan encontrarlas cuando busquen por etiquetas. Para obtener más información acerca de buscar por etiquetas, consulta "[Buscar propuestas y solicitudes de extracción](/search-github/searching-on-github/searching-issues-and-pull-requests/#search-by-label)". {% data variables.product.prodname_dotcom %} usa un algoritmo para determinar las propuestas más accesibles en cada repositorio y las hace aparecer en varios lugares en {% data variables.product.prodname_dotcom_the_website %}. Agregar la etiqueta `good first issue` (primera buena propuesta) puede aumentar la probabilidad de que tus propuestas salgan a la luz. @@ -24,4 +24,4 @@ Puedes aplicar la etiqueta `good first issue` (primera buena propuesta) a las pr ## Leer más - "[Acerca de las etiquetas](/articles/about-labels)" -- "[Buscar repositorios](/articles/searching-for-repositories)" +- "[Buscar repositorios](/search-github/searching-on-github/searching-for-repositories)" diff --git a/translations/es-ES/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md b/translations/es-ES/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md index 8694b63cf2..a52021459c 100644 --- a/translations/es-ES/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md +++ b/translations/es-ES/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md @@ -41,7 +41,7 @@ Puedes crear lineamientos de contribución predeterminados para tu organización {% data reusables.repositories.navigate-to-repo %} {% data reusables.files.add-file %} -3. Decide si almacenar tus pautas de contribución en la raíz de tu repositorio, el directorio `docs`, o el directorio `.github`. Después, en el campo nombre de archivo, escribe el nombre y la extensión del archivo. Los nombres de archivo de los lineamientos de contribución no distinguen entre mayúsculas y minúsculas. Los archivos se interpretan en formato de texto rico si la extensión de archivo se encuentra en un formato compatible. For more information, see "[Working with non-code files](/repositories/working-with-files/using-files/working-with-non-code-files#rendering-differences-in-prose-documents)." ![Nombre del nuevo archivo](/assets/images/help/repository/new-file-name.png) +3. Decide si almacenar tus pautas de contribución en la raíz de tu repositorio, el directorio `docs`, o el directorio `.github`. Después, en el campo nombre de archivo, escribe el nombre y la extensión del archivo. Los nombres de archivo de los lineamientos de contribución no distinguen entre mayúsculas y minúsculas. Los archivos se interpretan en formato de texto rico si la extensión de archivo se encuentra en un formato compatible. Para obtener más información, consulta la sección "[Trabajar con archivos que no sean de código](/repositories/working-with-files/using-files/working-with-non-code-files#rendering-differences-in-prose-documents)". ![Nombre del nuevo archivo](/assets/images/help/repository/new-file-name.png) - Para hacer visibles tus pautas de contribución en el directorio raíz del repositorio, escribe *CONTRIBUTING*. - Para hacer visibles tus pautas de contribución en el directorio `docs` del repositorio, escribe *docs/* para crear el nuevo directorio, y luego *CONTRIBUTING*. - Si un repositorio contiene más de un archivo de *CONTRIBUCIÓN*, entonces el archivo que se muestra en los enlaces se elige de las ubicaciones en el siguiente orden: el directorio `.github`, luego el directorio raíz del repositorio y finalmente el directorio `docs`. 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 17c8f5a9e5..d64dda1570 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 @@ -70,7 +70,7 @@ Puedes alentar a los colaboradores para que utilicen plantillas de informe de pr {% note %} -**Note:** If you used the legacy workflow to manually create an `issue_template.md` file in the `.github` folder and enable blank issues in your *config.yml* file, the template in `issue_template.md` will be used when people chose to open a blank issue. Si inhabilitas los reportes de problemas en blanco, la plantilla nunca se utilizará. +**Nota:**Si utilizaste el flujo de trabajo tradicional para crear un archivo de `issue_template.md` manualmente en la carpeta de `.github` y habilitar así las propuestas en blanco en tu archivo de *config.yml*, la plantilla en el archivo `issue_template.md` se utilizará cuando las personas decidan abrir una propuesta en blanco. Si inhabilitas los reportes de problemas en blanco, la plantilla nunca se utilizará. {% endnote %} diff --git a/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md b/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md index 923a10a0ff..41c2cd8449 100644 --- a/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md +++ b/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md @@ -58,12 +58,12 @@ Por ejemplo, la siguente definición de formato incluye cuatro elementos de form Para cada elemento de formato, puedes configurar las siguientes claves. -| Clave | Descripción | Requerido | Type | Predeterminado | Valores válidos | -| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------- | --------- | ----------------------------------------------- | ----------------------------------------------- | -| `type` | El tipo de elemento que quieres definir. | Requerido | Secuencia | {% octicon "dash" aria-label="The dash icon" %} |
    • `checkboxes`
    • `dropdown`
    • `input`
    • `markdown`
    • `textarea`
    | -| `id` | The identifier for the element, except when `type` is set to `markdown`. {% data reusables.form-schema.id-must-be-unique %} Si se proporcionó, la `id` es el identificador canónico para el campo en los pre-llenados de parámetro de la consulta de URL. | Opcional | Secuencia | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} -| `attributes` | Un conjunto de pares clave-valor que definen las propiedades del elemento. | Requerido | Hash | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} -| `validations` | Un conjunto de pares de clave-valor que configuran las restricciones en el elemento. | Opcional | Hash | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} +| Clave | Descripción | Requerido | Type | Predeterminado | Valores válidos | +| ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------- | --------- | ----------------------------------------------- | ----------------------------------------------- | +| `type` | El tipo de elemento que quieres definir. | Requerido | Secuencia | {% octicon "dash" aria-label="The dash icon" %} |
    • `checkboxes`
    • `dropdown`
    • `input`
    • `markdown`
    • `textarea`
    | +| `id` | El identificador del elemento, excepto cuando el `type` se configura como `markdown`. {% data reusables.form-schema.id-must-be-unique %} Si se proporcionó, la `id` es el identificador canónico para el campo en los pre-llenados de parámetro de la consulta de URL. | Opcional | Secuencia | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} +| `attributes` | Un conjunto de pares clave-valor que definen las propiedades del elemento. | Requerido | Hash | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} +| `validations` | Un conjunto de pares de clave-valor que configuran las restricciones en el elemento. | Opcional | Hash | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} Puedes elegir desde los siguientes tipos de elementos de formato. Cada tipo tiene atributos y validaciones únicos. diff --git a/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md b/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md index c0cbe66942..d41348c731 100644 --- a/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md +++ b/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md @@ -16,7 +16,7 @@ Puedes crear formatos de propuesta personalizados agregando un archivo de defini Cuando un colaborador llega un formato de propuesta, sus respuestas para cada entrada se convierten en lenguaje de marcado y se agregan al cuerpo de una propuesta. Los contribuyentes pueden editar las propuestas que se crearon con estos formatos de propuesta y otras personas pueden interactuar con las propuestas como con una de ellas que se creó mediante otros métodos. -Issue forms are not supported for pull requests. You can create pull request templates in your repositories for collaborators to use. Para obtener más información, consulta [Crear plantillas de solicitud de extracción para tu repositorio](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository)". +Los formatos de propuesta no son compatibles para las solicitudes de cambios. Puedes crear plantillas de solicitudes de cambios en tus repositorios para que las utilicen los colaboradores. Para obtener más información, consulta [Crear plantillas de solicitud de extracción para tu repositorio](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository)". Este archivo de configuración YAML define un formato de propuesta utilizando varias entradas para reportar un error. diff --git a/translations/es-ES/content/developers/apps/building-github-apps/authenticating-with-github-apps.md b/translations/es-ES/content/developers/apps/building-github-apps/authenticating-with-github-apps.md index 8dfec9eaa3..6832d2ec99 100644 --- a/translations/es-ES/content/developers/apps/building-github-apps/authenticating-with-github-apps.md +++ b/translations/es-ES/content/developers/apps/building-github-apps/authenticating-with-github-apps.md @@ -87,7 +87,7 @@ jwt = JWT.encode(payload, private_key, "RS256") puts jwt ``` -`YOUR_PATH_TO_PEM` y `YOUR_APP_ID` son los valores que debes reemplazar. Make sure to enclose the values in double quotes. +`YOUR_PATH_TO_PEM` y `YOUR_APP_ID` son los valores que debes reemplazar. Asegúrate de poner los valores entre comillas dobles. Utiliza tu identificador de {% data variables.product.prodname_github_app %} (`YOUR_APP_ID`) como el valor para la solicitud del [iss](https://tools.ietf.org/html/rfc7519#section-4.1.1) (emisor) del JWT. Puedes obtener el identificador de {% data variables.product.prodname_github_app %} a través del ping del webhook inicial después de [crear la app](/apps/building-github-apps/creating-a-github-app/), o en cualquier momento desde la página de configuración de la app en la UI de GitHub.com. @@ -116,7 +116,7 @@ Para obtener una lista de las terminales de API de REST que puedes utilizar para ## Autenticarse como una instalación -El autenticarte como una instalación te permite realizar acciones en la API para dicha instalación. Antes de autenticarte como una instalación, debes crear un token de acceso a ésta. Asegúrate de que ya hayas instalado tu GitHub App en por lo menos un repositorio; es imposible crear un token de instalación si una sola instalación. These installation access tokens are used by {% data variables.product.prodname_github_apps %} to authenticate. For more information, see "[Installing GitHub Apps](/developers/apps/managing-github-apps/installing-github-apps)." +El autenticarte como una instalación te permite realizar acciones en la API para dicha instalación. Antes de autenticarte como una instalación, debes crear un token de acceso a ésta. Asegúrate de que ya hayas instalado tu GitHub App en por lo menos un repositorio; es imposible crear un token de instalación si una sola instalación. Las {% data variables.product.prodname_github_apps %} utilizan estos tokens de acceso a la instalación para autenticarse. Para obtener más información, consulta la sección "[Instalar las GitHub Apps](/developers/apps/managing-github-apps/installing-github-apps)". Predeterimenadamente, los tokens de acceso de instalación tienen un alcance de todos los repositorios a los cuales tiene acceso dicha instalación. Puedes limitar el alcance del token de acceso de la instalación a repositorios específicos si utilizas el parámetro `repository_ids`. Consulta la terminal [Crear un token de acceso de instalación para una app](/rest/reference/apps#create-an-installation-access-token-for-an-app) para encontrar más detalles. Los tokens de acceso de instalación cuentan con permisos configurados por la {% data variables.product.prodname_github_app %} y caducan después de una hora. @@ -155,7 +155,7 @@ $ curl -i \ ## Acceder a las terminales de la API como una instalación -For a list of REST API endpoints that are available for use by {% data variables.product.prodname_github_apps %} using an installation access token, see "[Available Endpoints](/rest/overview/endpoints-available-for-github-apps)." +Para encontrar un listado de las terminales de la API de REST disponibles para utilizarse con las {% data variables.product.prodname_github_apps %} utilizando un token de acceso de instalación, consulta la sección "[Terminales Disponibles](/rest/overview/endpoints-available-for-github-apps)". Para encontrar un listad de terminales relacionado con las instalaciones, consulta la sección "[Instalaciones](/rest/reference/apps#installations)". 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 efebe28df6..886f867f61 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 @@ -42,6 +42,7 @@ Al utilizar el flujo de aplicaciones web, el proceso para identificar a los usua Si seleccionas **Solicitar la autorización del usuario (OAuth) durante la instalación** cuando crees o modifiques tu app, el paso 1 se completará durante la instalación de la misma. Para obtener más información, consulta la sección "[Autorizar usuarios durante la instalación](/apps/installing-github-apps/#authorizing-users-during-installation)". ### 1. Solicita la identidad de un usuario de GitHub +Direct the user to the following URL in their browser: GET {% data variables.product.oauth_host_code %}/login/oauth/authorize @@ -73,10 +74,12 @@ Si el usuario acepta tu solicitud, GitHub te redirecciona de regreso a tu sitio {% endnote %} -Intercambia este `code` por un token de acceso. When expiring tokens are enabled, the access token expires in 8 hours and the refresh token expires in 6 months. Cada que actualizas el token, obtienes un nuevo token de actualización. Para obtener más información, consulta la sección "[Actualizar los tokens de acceso de usuario a servidor](/developers/apps/refreshing-user-to-server-access-tokens)". +Intercambia este `code` por un token de acceso. Cuando se habilita el vencimiento de tokens, el token de acceso vence en 8 horas y el token de actualización en 6 meses. Cada que actualizas el token, obtienes un nuevo token de actualización. Para obtener más información, consulta la sección "[Actualizar los tokens de acceso de usuario a servidor](/developers/apps/refreshing-user-to-server-access-tokens)". Los tokens de usuario con vigencia determinada son una característica opcional actualmente y están sujetos a cambios. Para decidir unirse a la característica de vigencia determinada de los tokens de usuario a servidor, consulta la sección "[Activar las características opcionales para las apps](/developers/apps/activating-optional-features-for-apps)". +Make a request to the following endpoint to receive an access token: + POST {% data variables.product.oauth_host_code %}/login/oauth/access_token #### Parámetros diff --git a/translations/es-ES/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md b/translations/es-ES/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md index 5296ea24dc..b27a3ea25f 100644 --- a/translations/es-ES/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md +++ b/translations/es-ES/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md @@ -20,7 +20,7 @@ shortTitle: Límites de tasa {% ifversion fpt %} -Different server-to-server request rate limits apply to {% data variables.product.prodname_github_apps %} if the app is installed on organizations or repositories owned by a {% data variables.product.prodname_ghe_cloud %} account. +Se aplicarán límites de tasa diferentes para las solicitudes de servidor a servidor en las {% data variables.product.prodname_github_apps %} si la app se encuentra instalada en organizaciones o repositorios que pertenezcan a una cuenta de {% data variables.product.prodname_ghe_cloud %}. ### Límites de tasa normales de servidor a servidor @@ -32,17 +32,17 @@ Different server-to-server request rate limits apply to {% data variables.produc ### Límites de tasa de servidor a servidor de {% data variables.product.prodname_ghe_cloud %} -{% data variables.product.prodname_github_apps %} that are installed on an organization or repository owned by a {% data variables.product.prodname_ghe_cloud %} account and make server-to-server requests have a rate limit of 15,000 requests per hour. +Las {% data variables.product.prodname_github_apps %} que se instalen en un repositorio de organización que pertenezca a una cuenta de {% data variables.product.prodname_ghe_cloud %} y haga solicitudes de servidor a servidor tiene un límite de tasa de 15,000 solicitudes por hora por organización por instalaciones de la organización o por repositorio por instalaciones de repositorio. {% endif %} ## Solicitudes de usuario a servidor -{% data variables.product.prodname_github_apps %} can also act [on behalf of a user](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-and-authorizing-users-for-github-apps), making user-to-server requests. +Las {% data variables.product.prodname_github_apps %} también pueden actuar [en nombre de un usuario](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-and-authorizing-users-for-github-apps) al hacer solicitudes de usuario a servidor. {% ifversion fpt %} -Different user-to-server request rate limits apply to {% data variables.product.prodname_github_apps %} if the app is installed on organizations or repositories owned by a {% data variables.product.prodname_ghe_cloud %} account and the authenticated user also belongs to the same {% data variables.product.prodname_ghe_cloud %} account. +Aplicarán límites de tasa para solicitudes de usuario a servidor diferentes a las {% data variables.product.prodname_github_apps %} si la app se instaló en los repositorios u organizaciones que pertenezcan a la cuenta de {% data variables.product.prodname_ghe_cloud %} y el usuario autenticado también pertenecen a la misma cuenta de {% data variables.product.prodname_ghe_cloud %}. ### Límites de tasa normales de usuario a servidor diff --git a/translations/es-ES/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md b/translations/es-ES/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md index 7decc6000c..96878d9b7e 100644 --- a/translations/es-ES/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md +++ b/translations/es-ES/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md @@ -71,9 +71,9 @@ Si quieres que tu app utlice tokens de acceso de usuario a servidor sin caducida ![Opción para unirse a los tokens de usuario con caducidad durante la configuración de las GitHub Apps](/assets/images/github-apps/expire-user-tokens-selection.png) -Existing {% data variables.product.prodname_github_apps %} using user-to-server authorization tokens are only affected by this new flow when the app owner enables expiring user tokens for their app. +Las {% data variables.product.prodname_github_apps %} existentes que utilicen tokens de autorización de usuario a servidor solo se verán afectadas por este flujo nuevo cuando el propietario de la app habilite la caducidad de los tokens para la app en cuestión. -Enabling expiring user tokens for existing {% data variables.product.prodname_github_apps %} requires sending users through the OAuth flow to re-issue new user tokens that will expire in 8 hours and making a request with the refresh token to get a new access token and refresh token. Para obtener más información, consulta la sección "[Identificar y autorizar usuarios para las GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)". +Habilitar los tokens de usuario con caducidad para las {% data variables.product.prodname_github_apps %} existentes requiere que se envíen los usuarios a través del flujo de OAuth para re-emitir tokens de usuario nuevos que caducarán en 8 horas y que harán una solicitud con el token de actualización para obtener un token de acceso y un token de actualización nuevos. Para obtener más información, consulta la sección "[Identificar y autorizar usuarios para las GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)". {% ifversion fpt or ghes > 3.1 or ghae-next %} 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 0583295c8f..a869e8ed76 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 @@ -17,14 +17,14 @@ topics: - OAuth Apps --- -{% data variables.product.product_name %}'s OAuth implementation supports the standard [authorization code grant type](https://tools.ietf.org/html/rfc6749#section-4.1) and the OAuth 2.0 [Device Authorization Grant](https://tools.ietf.org/html/rfc8628) for apps that don't have access to a web browser. +La implementación de OAuth de {% data variables.product.product_name %} es compatible con el [tipo de otorgamientos de código de autorización](https://tools.ietf.org/html/rfc6749#section-4.1) estándar y con el [Otorgamiento de Autorización de Dispositivos](https://tools.ietf.org/html/rfc8628) de OAuth 2.0 para las apps que no tengan acceso a un buscador web. Si quieres saltar el proceso de autorización de tu app en el modo estándar, tal como sucede cuando la estás probando, puedes utilizar el [flujo no web para aplicaciones](#non-web-application-flow). Para autorizar tu app de OAuth, considera qué flujo de autorizaciones queda mejor con ella. -- [flujo web de aplicaciones](#web-application-flow): Se utiliza para autorizar a los usuarios para las aplicaciones de OAuth que se ejecutan en el buscador. (The [implicit grant type](https://tools.ietf.org/html/rfc6749#section-4.2) is not supported.){% ifversion fpt or ghae or ghes > 3.0 %} -- [device flow](#device-flow): Used for headless apps, such as CLI tools.{% endif %} +- [flujo web de aplicaciones](#web-application-flow): Se utiliza para autorizar a los usuarios para las aplicaciones de OAuth que se ejecutan en el buscador. (El [tipo de otorgamiento implícito](https://tools.ietf.org/html/rfc6749#section-4.2) no es compatible.){% ifversion fpt or ghae or ghes > 3.0 %} +- [flujo de dispositivos](#device-flow): Se utiliza para las aplicaciones sin encabezado, tales como las herramientas de CLI.{% endif %} ## Flujo de aplicaciones Web @@ -78,19 +78,29 @@ Intercambia este `code` por un token de acceso: Predeterminadamente, la respuesta toma la siguiente forma: - access_token={% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&token_type=bearer +``` +access_token={% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&scope=repo%2Cgist&token_type=bearer +``` -También puedes recibir el contenido en diferentes formatos, dependiendo del encabezado de aceptación: +{% data reusables.apps.oauth-auth-vary-response %} - Accept: application/json - {"access_token":"{% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "scope":"repo,gist", "token_type":"bearer"} - - Accept: application/xml - - bearer - repo,gist - {% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %} - +```json +Accept: application/json +{ + "access_token":"{% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", + "scope":"repo,gist", + "token_type":"bearer" +} +``` + +```xml +Accept: application/xml + + bearer + repo,gist + {% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %} + +``` ### 3. Utiliza el token de acceso para acceder a la API @@ -138,27 +148,35 @@ Tu app debe solicitar un código de verificación de usuario y una URL de verifi #### Respuesta -{% ifversion fpt %} - ```JSON - { - "device_code": "3584d83530557fdd1f46af8289938c8ef79f9dc5", - "user_code": "WDJB-MJHT", - "verification_uri": "https://github.com/login/device", - "expires_in": 900, - "interval": 5 - } - ``` -{% else %} - ```JSON - { - "device_code": "3584d83530557fdd1f46af8289938c8ef79f9dc5", - "user_code": "WDJB-MJHT", - "verification_uri": "http(s)://[hostname]/login/device", - "expires_in": 900, - "interval": 5 - } - ``` -{% endif %} +Predeterminadamente, la respuesta toma la siguiente forma: + +``` +device_code=3584d83530557fdd1f46af8289938c8ef79f9dc5&expires_in=900&interval=5&user_code=WDJB-MJHT&verification_uri=https%3A%2F%{% data variables.product.product_url %}%2Flogin%2Fdevice +``` + +{% data reusables.apps.oauth-auth-vary-response %} + +```json +Accept: application/json +{ + "device_code": "3584d83530557fdd1f46af8289938c8ef79f9dc5", + "user_code": "WDJB-MJHT", + "verification_uri": "{% data variables.product.oauth_host_code %}/login/device", + "expires_in": 900, + "interval": 5 +} +``` + +```xml +Accept: application/xml + + 3584d83530557fdd1f46af8289938c8ef79f9dc5 + WDJB-MJHT + {% data variables.product.oauth_host_code %}/login/device + 900 + 5 + +``` #### Parámetros de respuesta @@ -196,14 +214,32 @@ Ya que el usuario lo haya autorizado, la app recibirá un token de acceso que se #### Respuesta +Predeterminadamente, la respuesta toma la siguiente forma: + +``` +access_token={% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&token_type=bearer&scope=repo%2Cgist +``` + +{% data reusables.apps.oauth-auth-vary-response %} + ```json +Accept: application/json { "access_token": "{% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "token_type": "bearer", - "scope": "user" + "scope": "repo,gist" } ``` +```xml +Accept: application/xml + + {% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %} + bearer + gist,repo + +``` + ### Límites de tasa para el flujo del dispositivo Cuando un usuario emite el código de verificación en el buscador, hay un límite de tasa de 50 emisiones en una hora por aplicación. @@ -292,8 +328,8 @@ 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)" -{% ifversion fpt or ghae or ghes > 3.0 %}* "[Device flow errors](#error-codes-for-the-device-flow)"{% endif %}{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 %} -* "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %} +{% ifversion fpt or ghae or ghes > 3.0 %}* "[Errores de flujo de dispositivo](#error-codes-for-the-device-flow)"{% endif %}{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 %} +* "[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/building-oauth-apps/scopes-for-oauth-apps.md b/translations/es-ES/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md index 2804572da0..808a425140 100644 --- a/translations/es-ES/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md +++ b/translations/es-ES/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md @@ -47,7 +47,7 @@ X-Accepted-OAuth-Scopes: user |  `repo_deployment` | Otorga acceso a los [estados de despliegue](/rest/reference/repos#deployments) para los repositorios{% ifversion not ghae %}públicos{% else %}internos{% endif %} y privados. Este alcance solo se necesita para otorgar acceso a otros usuarios o servicios para los estados de despliegue, *sin* otorgar acceso al código.{% ifversion not ghae %} |  `public_repo` | Limita el acceso a los repositorios públicos. Esto incluye el acceso de lectura/escritura al código, estados de las confirmaciones, proyectos de repositorio, colaboradores y estados de despliegue para los repositorios públicos y para las organizaciones. También se requieren para marcar los repositorios públicos como favoritos.{% endif %} |  `repo:invite` | Otorga capacidades de aceptar/rechazar las invitaciones para colaborar con un repositorio. Este alcance solo es necesario para otorgar a otros usuarios o servicios acceso a las invitaciones *sin* otorgar acceso al código.{% ifversion fpt or ghes > 3.0 %} -|  `security_events` | Grants:
    read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning)
    read and write access to security events in the [{% data variables.product.prodname_secret_scanning %} API](/rest/reference/secret-scanning)
    This scope is only necessary to grant other users or services access to security events *without* granting access to the code.{% endif %}{% ifversion ghes < 3.1 %} +|  `security_events` | Otorga:
    acceso de lectura y escritura para los eventos de seguridad en la [API del {% data variables.product.prodname_code_scanning %}](/rest/reference/code-scanning)
    acceso de lectura y escritura para los eventos de seguridad en la [API del {% data variables.product.prodname_secret_scanning %}](/rest/reference/secret-scanning)
    Este alcance solo es necesario para otorgar acceso a los eventos de seguridad para otros usuarios o servicios *sin* otorgar acceso al código.{% endif %}{% ifversion ghes < 3.1 %} |  `security_events` | Otorga acceso de lectura y escritura a los eventos de seguridad en la [API de {% data variables.product.prodname_code_scanning %}](/rest/reference/code-scanning). Este alcance solo es necesario para otorgar acceso a los eventos de seguridad a otros usuarios o servicios *sin* otorgarles acceso al código.{% endif %} | **`admin:repo_hook`** | Otorga acceso de lectura, escritura, ping y borrado para los ganchos de repositorio en los repositorios {% ifversion not ghae %}públicos{% else %}internos{% endif %} y privados. El alcance de `repo` {% ifversion not ghae %}y de `public_repo` otorgan{% else %}otorga{% endif %} acceso total a los repositorios, icnluyendo a los ganchos de repositorio. Utiliza el alcance `admin:repo_hook` para limitar el acceso únicamente a los ganchos de los repositorios. | |  `write:repo_hook` | Otorga acceso de lectura, escritura y ping a los ganchos en los repositorios {% ifversion not ghae %}públicos{% else %}internos{% endif %} o privados. | 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 743e99ec9a..1673794498 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 @@ -17,7 +17,7 @@ topics: Las apps en {% data variables.product.prodname_dotcom %} te permiten automatizar y mejorar tu flujo de trabajo. Puedes crear apps para mejorar tu flujo de trabajo. {% ifversion fpt %} También puedes compartir o vender apps en [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace). Para aprender sobre cómo listar una app en {% data variables.product.prodname_marketplace %}, consulta la sección "[Comenzar con GitHub Marketplace](/marketplace/getting-started/)".{% endif %} -{% data reusables.marketplace.github_apps_preferred %}, but GitHub supports both {% data variables.product.prodname_oauth_apps %} and {% data variables.product.prodname_github_apps %}. Para obtener más información sobre cómo elegir un tipo de app, consulta la sección "[Diferencias entre las GitHub Apps y las Apps de OAuth](/developers/apps/differences-between-github-apps-and-oauth-apps)". +{% data reusables.marketplace.github_apps_preferred %}, Pero GitHub es compatible tanto con las {% data variables.product.prodname_oauth_apps %} y con las {% data variables.product.prodname_github_apps %}. Para obtener más información sobre cómo elegir un tipo de app, consulta la sección "[Diferencias entre las GitHub Apps y las Apps de OAuth](/developers/apps/differences-between-github-apps-and-oauth-apps)". {% data reusables.apps.general-apps-restrictions %} @@ -50,7 +50,7 @@ Toma estas ideas en consideración cuando crees {% data variables.product.prodna Para comenzar a desarrollar {% data variables.product.prodname_github_apps %}, comienza con "[Crear una {% data variables.product.prodname_github_app %}](/apps/building-github-apps/creating-a-github-app/)".{% ifversion fpt %} Para aprender cómo utilizar un manifiesto de las {% data variables.product.prodname_github_app %}, el cual permite a la gente crear {% data variables.product.prodname_github_apps %} preconfiguradas, consulta la sección "[Crear {% data variables.product.prodname_github_apps %} desde un manifiesto](/apps/building-github-apps/creating-github-apps-from-a-manifest/)".{% endif %} -## About {% data variables.product.prodname_oauth_apps %} +## Acerca de las {% data variables.product.prodname_oauth_apps %} OAuth2 es un protocolo que permite a las aplicaciones externas el solicitar autorización para usar detalles privados en una cuenta de {% data variables.product.prodname_dotcom %} del usuario sin acceder a su contraseña. Estas son preferentes sobre la Autenticación Básica, ya que los tokens pueden limitarse a ciertos tipos de datos y los usuarios pueden revocarlos en cualquier momento. @@ -58,19 +58,19 @@ OAuth2 es un protocolo que permite a las aplicaciones externas el solicitar auto Una {% data variables.product.prodname_oauth_app %} utiliza a {% data variables.product.prodname_dotcom %} como proveedor de identidad para autenticarse como el usuario que otorga el acceso a la app. Esto significa que, cuando un usuario otorga acceso a una {% data variables.product.prodname_oauth_app %}, también otorga permisos a _todos_ los repositorios a los cuales tienen acceso en su cuenta, y también a cualquier organización a la que pertenezcan que no haya bloqueado el acceso de terceros. -Crear una {% data variables.product.prodname_oauth_app %} es una buena opción si estás creando procesos más complejos de lo que puede manejar un script sencillo. Note that {% data variables.product.prodname_oauth_apps %} are applications that need to be hosted somewhere. +Crear una {% data variables.product.prodname_oauth_app %} es una buena opción si estás creando procesos más complejos de lo que puede manejar un script sencillo. Nota que las {% data variables.product.prodname_oauth_apps %} son aplicaciones que necesitan hospedarse en algún lugar. -Keep these ideas in mind when creating {% data variables.product.prodname_oauth_apps %}: +Toma estas ideas en consideración cuando crees {% data variables.product.prodname_oauth_apps %}: {% ifversion fpt %} * {% data reusables.apps.maximum-oauth-apps-allowed %} {% endif %} * Una {% data variables.product.prodname_oauth_app %} siempre debe actuar como el usuario autenticado de {% data variables.product.prodname_dotcom %} a través de todo {% data variables.product.prodname_dotcom %} (por ejemplo, cuando proporciona notificaciones de usuario). * Una {% data variables.product.prodname_oauth_app %} puede utilizarse como un proveedor de identidad si el usuario autenticado habilita la opción de "Ingresar con {% data variables.product.prodname_dotcom %}". -* No crees una {% data variables.product.prodname_oauth_app %} si quieres que tu aplicación actúe en un solo repositorio. With the `repo` OAuth scope, {% data variables.product.prodname_oauth_apps %} can act on _all_ of the authenticated user's repositories. -* No crees una {% data variables.product.prodname_oauth_app %} para que actúe como una aplicación para tu equipo o compañía. {% data variables.product.prodname_oauth_apps %} authenticate as a single user, so if one person creates an {% data variables.product.prodname_oauth_app %} for a company to use, and then they leave the company, no one else will have access to it.{% ifversion fpt %} +* No crees una {% data variables.product.prodname_oauth_app %} si quieres que tu aplicación actúe en un solo repositorio. Con el alcance de `repo` de OAuth, Las {% data variables.product.prodname_oauth_apps %} podrán actuar en _todos_ los repositorios del usuario autenticado. +* No crees una {% data variables.product.prodname_oauth_app %} para que actúe como una aplicación para tu equipo o compañía. Las {% data variables.product.prodname_oauth_apps %} se autentican como un solo usuario, así que, si una persona crea una {% data variables.product.prodname_oauth_app %} para el uso de una compañía, y luego salen de dicha compañía, nadie más tendrá acceso a ella.{% ifversion fpt %} * {% data reusables.apps.oauth-apps-restrictions %}{% endif %} -For more on {% data variables.product.prodname_oauth_apps %}, see "[Creating an {% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/creating-an-oauth-app/)" and "[Registering your app](/rest/guides/basics-of-authentication#registering-your-app)." +Para obtener más información sobre las {% data variables.product.prodname_oauth_apps %}, consulta las secciones "[Crear una {% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/creating-an-oauth-app/)" y "[Registrar tu app](/rest/guides/basics-of-authentication#registering-your-app)". ## Tokens de acceso personal @@ -84,12 +84,12 @@ 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. -* Don't set up a shared user account to act as a bot user.{% ifversion fpt or ghes > 3.2 or ghae-issue-4374 %} -* Do set an expiration for your personal access tokens, to help keep your information secure.{% endif %} +* No configures una cuenta de usuario compartida para que actúe como un usuario bot.{% ifversion fpt or ghes > 3.2 or ghae-issue-4374 %} +* 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 -Antes de que comiences a crear integraciones, necesitas determinar la mejor forma de acceder, autenticar, e interactuar con las API de {% data variables.product.prodname_dotcom %}. The following image offers some questions to ask yourself when deciding whether to use personal access tokens, {% data variables.product.prodname_github_apps %}, or {% data variables.product.prodname_oauth_apps %} for your integration. +Antes de que comiences a crear integraciones, necesitas determinar la mejor forma de acceder, autenticar, e interactuar con las API de {% data variables.product.prodname_dotcom %}. La siguiente imagen te proporciona algunas preguntas que deberías hacerte a ti mismo cuando decidas si vas a utilizar tokens de acceso personal, {% data variables.product.prodname_github_apps %} o {% data variables.product.prodname_oauth_apps %} para tu integración. ![Introducción al flujo de preguntas de apps](/assets/images/intro-to-apps-flow.png) diff --git a/translations/es-ES/content/developers/apps/getting-started-with-apps/activating-optional-features-for-apps.md b/translations/es-ES/content/developers/apps/getting-started-with-apps/activating-optional-features-for-apps.md index 35a7857b9e..74c753d633 100644 --- a/translations/es-ES/content/developers/apps/getting-started-with-apps/activating-optional-features-for-apps.md +++ b/translations/es-ES/content/developers/apps/getting-started-with-apps/activating-optional-features-for-apps.md @@ -1,6 +1,6 @@ --- title: Activar las características opcionales para las apps -intro: 'You can test new optional features for your {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}.' +intro: 'Puedes probar características nuevas para tus {% data variables.product.prodname_github_apps %} y {% data variables.product.prodname_oauth_apps %}.' redirect_from: - /developers/apps/activating-beta-features-for-apps - /developers/apps/activating-optional-features-for-apps diff --git a/translations/es-ES/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md b/translations/es-ES/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md index 083dee2d7c..e28c5979c0 100644 --- a/translations/es-ES/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md +++ b/translations/es-ES/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md @@ -1,6 +1,6 @@ --- title: Diferencias entre GitHub Apps y Apps de OAuth -intro: 'Understanding the differences between {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %} will help you decide which app you want to create. Una {% data variables.product.prodname_oauth_app %} actúa como un usuario de Github, mientras que una {% data variables.product.prodname_github_app %} utiliza su propia identidad cuando se instala en una organización o en repositorios dentro de una organización.' +intro: 'El entender las diferencias entre las {% data variables.product.prodname_github_apps %} y las {% data variables.product.prodname_oauth_apps %} te ayudará a decidir qué app quieres crear. Una {% data variables.product.prodname_oauth_app %} actúa como un usuario de Github, mientras que una {% data variables.product.prodname_github_app %} utiliza su propia identidad cuando se instala en una organización o en repositorios dentro de una organización.' redirect_from: - /early-access/integrations/integrations-vs-oauth-applications/ - /apps/building-integrations/setting-up-a-new-integration/about-choosing-an-integration-type/ @@ -56,14 +56,14 @@ Una App de OAuth _autorizada_ tiene acceso a todos los recursos que son accesibl {% endnote %} -| GitHub Apps | OAuth Apps | -| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Una GitHub App puede solicitar un token de acceso de la instalación si utiilza una llave privada con un formato de token web de JSON fuera de banda. | Una App de OAuth puede intercambiar un token de solicitud por un token de acceso después de una redirección a través de una solicitud web. | -| Un token de instalación identifica a la app como el bot de las GitHub Apps, tal como el @jenkins-bot. | Un token de acceso identifica a la app como el usuario que otorgó el token para la app, tal como el @octocat. | -| Los tokens de instalación caducan después de un tiempo predefinido (actualmente, 1 hora). | Los tokens de OAuth permanecen activos hasta que el cliente los revoque. | -| {% data reusables.apps.api-rate-limits-non-ghec %}{% ifversion fpt %} Se aplican límites de tasa más altos para {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta la sección "[Límites de tasa para las GitHub Apps](/developers/apps/rate-limits-for-github-apps)".{% endif %} | Los tokens de OAuth utilizan el límite de tasa del usuario de 5,000 solicitudes por hora. | -| Pueden otorgarse incrementos en el límite de tasa tanto a nivel de las GitHub Apps (lo cual afecta a todas las instalaciones) como a nivel de la instalación individual. | Los incrementos en el límite de tasa se otorgan por cada App de OAuth. Cada token que se otorgue a esa App de OAuth obtiene el límite incrementado. | -| {% data variables.product.prodname_github_apps %} can authenticate on behalf of the user, which is called user-to-server requests. El flujo para autorizaciones es el mismo que aquél de las autorizaciones para las apps de OAuth. Los tokens de usuario a servidor pueden caducar y renovarse con un token de actualización. Para obtener más información, consulta las secciones "[Actualizar un token de acceso de usuario a servidor](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)" y "[Identificar y autorizar a los usuarios para las GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)". | The OAuth flow used by {% data variables.product.prodname_oauth_apps %} authorizes an {% data variables.product.prodname_oauth_app %} on behalf of the user. Este es el mismo flujo que se utiliza en las autorizaciones de usuario a servidor de una {% data variables.product.prodname_github_app %}. | +| GitHub Apps | OAuth Apps | +| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Una GitHub App puede solicitar un token de acceso de la instalación si utiilza una llave privada con un formato de token web de JSON fuera de banda. | Una App de OAuth puede intercambiar un token de solicitud por un token de acceso después de una redirección a través de una solicitud web. | +| Un token de instalación identifica a la app como el bot de las GitHub Apps, tal como el @jenkins-bot. | Un token de acceso identifica a la app como el usuario que otorgó el token para la app, tal como el @octocat. | +| Los tokens de instalación caducan después de un tiempo predefinido (actualmente, 1 hora). | Los tokens de OAuth permanecen activos hasta que el cliente los revoque. | +| {% data reusables.apps.api-rate-limits-non-ghec %}{% ifversion fpt %} Se aplican límites de tasa más altos para {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta la sección "[Límites de tasa para las GitHub Apps](/developers/apps/rate-limits-for-github-apps)".{% endif %} | Los tokens de OAuth utilizan el límite de tasa del usuario de 5,000 solicitudes por hora. | +| Pueden otorgarse incrementos en el límite de tasa tanto a nivel de las GitHub Apps (lo cual afecta a todas las instalaciones) como a nivel de la instalación individual. | Los incrementos en el límite de tasa se otorgan por cada App de OAuth. Cada token que se otorgue a esa App de OAuth obtiene el límite incrementado. | +| Las {% data variables.product.prodname_github_apps %} pueden autenticarse a nombre del usuario y a esto se le llama solicitudes de usuario a servidor. El flujo para autorizaciones es el mismo que aquél de las autorizaciones para las apps de OAuth. Los tokens de usuario a servidor pueden caducar y renovarse con un token de actualización. Para obtener más información, consulta las secciones "[Actualizar un token de acceso de usuario a servidor](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)" y "[Identificar y autorizar a los usuarios para las GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)". | El flujo de OAuth que utilizan las {% data variables.product.prodname_oauth_apps %} autoriza a una {% data variables.product.prodname_oauth_app %} en nombre del usuario. Este es el mismo flujo que se utiliza en las autorizaciones de usuario a servidor de una {% data variables.product.prodname_github_app %}. | ## Solicitar niveles de permiso para recursos diff --git a/translations/es-ES/content/developers/apps/getting-started-with-apps/migrating-oauth-apps-to-github-apps.md b/translations/es-ES/content/developers/apps/getting-started-with-apps/migrating-oauth-apps-to-github-apps.md index 0c55ef6707..d7db2cb64c 100644 --- a/translations/es-ES/content/developers/apps/getting-started-with-apps/migrating-oauth-apps-to-github-apps.md +++ b/translations/es-ES/content/developers/apps/getting-started-with-apps/migrating-oauth-apps-to-github-apps.md @@ -10,7 +10,7 @@ versions: ghae: '*' topics: - GitHub Apps -shortTitle: Migrate from OAuth Apps +shortTitle: Migrarse desde las Apps de OAuth --- Este artículo proporciona los lineamientos para los integradores existentes que están considerando migrarse de una App de OAuth a una GitHub App. @@ -41,14 +41,14 @@ Estos lineamientos asumen que has registrado una App de OAuth{% ifversion fpt %} 1. [Entender los diferentes métodos de autenticación](#understand-the-different-methods-of-authentication) 1. [Dirigir a los usuarios a instalar tu GitHub App en los repositorios](#direct-users-to-install-your-github-app-on-repositories) 1. [Eliminar cualquier gancho innecesario en los repositorios](#remove-any-unnecessary-repository-hooks) -1. [Encourage users to revoke access to your OAuth App](#encourage-users-to-revoke-access-to-your-oauth-app) -1. [Delete the OAuth App](#delete-the-oauth-app) +1. [Anima a los usuarios para revocar el acceso a tu App de OAuth](#encourage-users-to-revoke-access-to-your-oauth-app) +1. [Borra la App de OAuth](#delete-the-oauth-app) ### Revisar las terminales de la API disponibles para las Github Apps Mientras que la mayoría de las terminales de la [API de REST](/rest) y de las consultas de [GraphQL](/graphql) están disponibles hoy en día para las GitHub Apps, aún estamos en el proceso de habilitar algunas de ellas. Revisa las [terminales disponibles de REST](/rest/overview/endpoints-available-for-github-apps) para garantizar que las terminales que necesitas sean compatibles con las GitHub Apps. Nota que algunas de las terminales de la API que están habilitadas para las GtiHub Apps permiten que éstas interactúen en nombre del usuario. Consulta la sección "[Solicitudes de usuario a servidor](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-to-server-requests)" para encontrar una lista de terminales disponibles para que una GitHub App se autentique como un usuario. -Te recomendamos revisar la lista de terminales de la API que necesitas tan pronto como te sea posible. Please let Support know if there is an endpoint you require that is not yet enabled for {% data variables.product.prodname_github_apps %}. +Te recomendamos revisar la lista de terminales de la API que necesitas tan pronto como te sea posible. Por favor, comunícale a soporte si hay alguna terminal que requieras y que no esté habilitada aún para las {% data variables.product.prodname_github_apps %}. ### Diseñar con apego a los límites de tasa de la API @@ -102,8 +102,8 @@ Una vez que ti GitHub App se haya instalado en un repositorio, deberías elimina ### Animar a los usuarios a que revoquen el acceso a tu App de OAuth -As your GitHub App installation base grows, consider encouraging your users to revoke access to the legacy OAuth integration. Para obtener más información, consulta la sección "[Autorizar las Apps de OAuth](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps)". +En medida en que vaya creciendo tu base de instalación de la GitHub App, considera exhortar a tus usuarios para revocar el acceso a la integración tradicional de OAuth. Para obtener más información, consulta la sección "[Autorizar las Apps de OAuth](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps)". -### Delete the OAuth App +### Borrar la App de OAuth -To avoid abuse of the OAuth App's credentials, consider deleting the OAuth App. This action will also revoke all of the OAuth App's remaining authorizations. For more information, see "[Deleting an OAuth App](/developers/apps/managing-oauth-apps/deleting-an-oauth-app)." +Para evitar el abuso de las credenciales de las Apps de OAuth, considera borrar la App de OAuth. Esta acción también revocará todas las autorizaciones restantes de la App de OAuth. Para obtener más información, consulta la sección "[Borrar una App de OAuth](/developers/apps/managing-oauth-apps/deleting-an-oauth-app)". diff --git a/translations/es-ES/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md b/translations/es-ES/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md index 09403d86fe..a5eee341a5 100644 --- a/translations/es-ES/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md +++ b/translations/es-ES/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md @@ -25,7 +25,7 @@ Los flujos de las instalaciones públicas tienen una página de llegada para hab ## Flujo de instalación privada -Los flujos de instalación privada permiten que solo el propietario de la GitHub App pueda instalarla. Aún así, existirá información limitada sobre la GitHub App en una página pública, pero el botón de **Instalar** solo estará disponible para los administradores de la organización o para la cuenta de usuario si dicha GitHub App le pertenece a una cuenta individual. Las GitHub Apps privadas{% ifversion ghes < 3.2 or ghae %}, o internas,{% endif %} solo pueden instalarse en la cuenta de organización o de usuario del propietario. +Los flujos de instalación privada permiten que solo el propietario de la GitHub App pueda instalarla. Aún así, existirá información limitada sobre la GitHub App en una página pública, pero el botón de **Instalar** solo estará disponible para los administradores de la organización o para la cuenta de usuario si dicha GitHub App le pertenece a una cuenta individual. Las GitHub Apps {% ifversion fpt or ghes > 3.1 or ghae-next %}privadas {% else %}privadas (también conocidas como internas){% endif %} solo pueden instalarse en la cuenta de usuario u organización del propietario. ## Cambiar el quién puede instalar tu GitHub App @@ -36,5 +36,5 @@ Para cambiar quién puede instalar una GitHub App: {% data reusables.user-settings.github_apps %} 3. Selecciona la GitHub App cuya opción de instalación quieras cambiar. ![Seleccion de apps](/assets/images/github-apps/github_apps_select-app.png) {% data reusables.user-settings.github_apps_advanced %} -5. Dependiendo de la opción de instalación de tu GitHub App, haz clic ya sea en **Hacer pública** o **Hacer{% ifversion fpt or ghes > 3.1 %}privada{% else %}interna{% endif %}**. ![Botón para cambiar la opción de instalación para tu GitHub App](/assets/images/github-apps/github_apps_make_public.png) -6. Dependiendo de la opción de instalación de tu GitHub App, haz clic ya sea en **Sí, hacer esta GitHub App pública** o **Sí, hacer esta GitHub App {% ifversion fpt or ghes > 3.1 %}privada{% else %}interna{% endif %}**. ![Botón para confirmar el cambio de tu opción de instalación](/assets/images/github-apps/github_apps_confirm_installation_option.png) +5. Dependiendo de la opción de instalación de tu GitHub App, haz clic ya sea en **Hacer pública** o **Hacer{% ifversion fpt or ghes > 3.1 or ghae-next %}privada{% else %}interna{% endif %}**. ![Botón para cambiar la opción de instalación para tu GitHub App](/assets/images/github-apps/github_apps_make_public.png) +6. Dependiendo de la opción de instalación de tu GitHub App, haz clic ya sea en **Sí, hacer esta GitHub App pública** o **Sí, hacer esta GitHub App {% ifversion fpt or ghes < 3.2 %}interna{% else %}privada{% endif %}**. ![Botón para confirmar el cambio de tu opción de instalación](/assets/images/github-apps/github_apps_confirm_installation_option.png) diff --git a/translations/es-ES/content/developers/apps/managing-github-apps/suspending-a-github-app-installation.md b/translations/es-ES/content/developers/apps/managing-github-apps/suspending-a-github-app-installation.md index 601d63b1ac..95bfe4d462 100644 --- a/translations/es-ES/content/developers/apps/managing-github-apps/suspending-a-github-app-installation.md +++ b/translations/es-ES/content/developers/apps/managing-github-apps/suspending-a-github-app-installation.md @@ -19,7 +19,7 @@ El integrador que mantiene y al que le pertenece la GitHub app, también llamado Las personas que han instalado una GitHub App, también llamadas propietarias de la instalación, solo podrán suspender o dejar de suspendar una GitHub App a través de la configuración de instalación de la app. Los propietarios de la instalación no pueden usar la API para suspender o dejar de suspender su instalación de la app. -If an installation has been suspended by the {% data variables.product.prodname_github_app %} owner, installation owners cannot unsuspend their installations of the {% data variables.product.prodname_github_app %}. However, installation owners can change other settings, such as repository selection, while the app is suspended. +Si el propietario de la {% data variables.product.prodname_github_app %} suspendió una instalación, los propietarios de dicha instalación no podrán dejar de suspender las instalaciones de la {% data variables.product.prodname_github_app %}. Sin embargo, los propietarios de la instalación pueden cambiar otros ajustes, tales como la selección del repositorio, mientras la app está suspendida. {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.developer_settings %} diff --git a/translations/es-ES/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md b/translations/es-ES/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md index a69041b118..4fac801f1d 100644 --- a/translations/es-ES/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md +++ b/translations/es-ES/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md @@ -58,8 +58,8 @@ Si tu app ya se publicó y eres un publicador verificado, entonces puedes public Para publicar una app de pago (o una app que te ofrece un plan de pago), también debes cumplir con los siguientes requisitos: -- {% data variables.product.prodname_github_apps %} should have a minimum of 100 installations. -- {% data variables.product.prodname_oauth_apps %} should have a minimum of 200 users. +- Las {% data variables.product.prodname_github_apps %} deben tener un mínimo de 100 instalaciones. +- Las {% data variables.product.prodname_oauth_apps %} deben tener un mínimo de 200 usuarios. - Todas las apps de pago deben gestinar los eventos de compra de {% data variables.product.prodname_marketplace %} para las compras nuevas, mejoras, retrocesos, cancelaciones y pruebas gratuitas. Para obtener más información, consulta la sección "[Requisitos de facturación para las apps de pago](#billing-requirements-for-paid-apps)" que se encuentra más adelante. Cuando estés listo para publicar la app en {% data variables.product.prodname_marketplace %}, deberás solicitar la verificación de su listado. diff --git a/translations/es-ES/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-transactions-for-your-listing.md b/translations/es-ES/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-transactions-for-your-listing.md index 43b696d72a..8d2e7edfde 100644 --- a/translations/es-ES/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-transactions-for-your-listing.md +++ b/translations/es-ES/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-transactions-for-your-listing.md @@ -31,8 +31,8 @@ Puedes visualizar o descargar los datos de las transacciones para dar seguimient * **amount_in_cents:** La cantidad de la transacción en centavos. Cuando un valor es menor a la cantidad del plan, el usuario que hizo la mejora y el plan nuevo se prorratean. Un valor de cero indica que el usuario canceló el plan. * **renewal_frequency:** La frecuencia de renovación de la suscripción, ya sea `Monthly` o `Yearly`. * **marketplace_listing_plan_id:** La `id` del plan de suscripción. -* **region:** The name of the region present in billing address. -* **postal_code:** The postal code value present in billing address. +* **region:** El nombre de la región presente en la dirección de facturación. +* **postal_code:** El valor de código postal presente en la dirección de facturación. ![Perspectivas de Marketplace](/assets/images/marketplace/marketplace_transactions.png) diff --git a/translations/es-ES/content/developers/github-marketplace/github-marketplace-overview/about-github-marketplace.md b/translations/es-ES/content/developers/github-marketplace/github-marketplace-overview/about-github-marketplace.md index 1df2f3cee6..796fb72b79 100644 --- a/translations/es-ES/content/developers/github-marketplace/github-marketplace-overview/about-github-marketplace.md +++ b/translations/es-ES/content/developers/github-marketplace/github-marketplace-overview/about-github-marketplace.md @@ -31,11 +31,11 @@ Para publicar las apps con planes gratuitos, solo necesitas cumplir con los requ ### ¿Eres nuevo en las apps? -If you're interested in creating an app for {% data variables.product.prodname_marketplace %}, but you're new to {% data variables.product.prodname_github_apps %} or {% data variables.product.prodname_oauth_apps %}, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" or "[Building {% data variables.product.prodname_oauth_apps %}](/developers/apps/building-oauth-apps)." +Si te interesa crear una app para {% data variables.product.prodname_marketplace %}, pero eres nuevo en las {% data variables.product.prodname_github_apps %} o en las {% data variables.product.prodname_oauth_apps %}, consulta la sección "[Crear {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" o la sección "[Crear {% data variables.product.prodname_oauth_apps %}](/developers/apps/building-oauth-apps)". ### {% data variables.product.prodname_github_apps %} vs. {% data variables.product.prodname_oauth_apps %} -{% data reusables.marketplace.github_apps_preferred %}, although you can list both OAuth and {% data variables.product.prodname_github_apps %} in {% data variables.product.prodname_marketplace %}. For more information, see "[Differences between {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}](/apps/differences-between-apps/)" and "[Migrating {% data variables.product.prodname_oauth_apps %} to {% data variables.product.prodname_github_apps %}](/apps/migrating-oauth-apps-to-github-apps/)." +{% data reusables.marketplace.github_apps_preferred %}, aunque puedes listar tanto las Apps de OAuth como las {% data variables.product.prodname_github_apps %} en {% data variables.product.prodname_marketplace %}. Para obtener más información, consulta las secciones "[Diferencias entre las {% data variables.product.prodname_github_apps %} y las {% data variables.product.prodname_oauth_apps %}](/apps/differences-between-apps/)" y "[Migrar de las {% data variables.product.prodname_oauth_apps %} a las {% data variables.product.prodname_github_apps %}](/apps/migrating-oauth-apps-to-github-apps/)". ## Resumen de cómo publicar una app en {% data variables.product.prodname_marketplace %} diff --git a/translations/es-ES/content/developers/github-marketplace/github-marketplace-overview/about-marketplace-badges.md b/translations/es-ES/content/developers/github-marketplace/github-marketplace-overview/about-marketplace-badges.md index 3810a0bf29..4d74b4b641 100644 --- a/translations/es-ES/content/developers/github-marketplace/github-marketplace-overview/about-marketplace-badges.md +++ b/translations/es-ES/content/developers/github-marketplace/github-marketplace-overview/about-marketplace-badges.md @@ -30,7 +30,7 @@ Algunas apps en {% data variables.product.prodname_marketplace %} tienen la insi Para obtener más información sobre los requisitos para listar una app en {% data variables.product.prodname_marketplace %}, consulta los "[Requisitos para listar una app en {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)". -Para obtener información sobre cómo encontrar apps que puedas utilizar, consulta la sección "[Buscar en {% data variables.product.prodname_marketplace %}](/github/searching-for-information-on-github/searching-github-marketplace)". +Para obtener información sobre cómo encontrar apps que puedas utilizar, consulta la sección "[Buscar en {% data variables.product.prodname_marketplace %}](/search-github/searching-on-github/searching-github-marketplace)". ## Para las GitHub Actions diff --git a/translations/es-ES/content/developers/github-marketplace/selling-your-app-on-github-marketplace/receiving-payment-for-app-purchases.md b/translations/es-ES/content/developers/github-marketplace/selling-your-app-on-github-marketplace/receiving-payment-for-app-purchases.md index ab70724b66..e4e473d137 100644 --- a/translations/es-ES/content/developers/github-marketplace/selling-your-app-on-github-marketplace/receiving-payment-for-app-purchases.md +++ b/translations/es-ES/content/developers/github-marketplace/selling-your-app-on-github-marketplace/receiving-payment-for-app-purchases.md @@ -17,7 +17,7 @@ shortTitle: Recibir pagos Después de que tu listado de {% data variables.product.prodname_marketplace %} para una app con un plan de pago se cree y apruebe, deberás proporcionar los detalles de pago a {% data variables.product.product_name %} como parte del proceso de integración financiera. -Once your revenue reaches a minimum of 500 US dollars for the month, you'll receive an electronic payment from {% data variables.product.company_short %}. Este será el ingreso de las transacciones de marketplace menos la cantidad que cobra {% data variables.product.company_short %} para cubrir los costos de operación. +Una vez que tus ganancias lleguen a un mínimo de 500 dólares estadounidenses por el mes, recibirás un pago electrónico de {% data variables.product.company_short %}. Este será el ingreso de las transacciones de marketplace menos la cantidad que cobra {% data variables.product.company_short %} para cubrir los costos de operación. Para las transacciones que se realicen antes del 1 de enero de 2021, {% data variables.product.company_short %} retendrá el 25% del ingreso de ellas. Para las transacciones que se realicen después de esta fecha, {% data variables.product.company_short %} solo retendrá el 5%. Este cambio se reflejará en los pagos que se reciban desde el final de enero 2021 en adelante. diff --git a/translations/es-ES/content/developers/overview/index.md b/translations/es-ES/content/developers/overview/index.md index ee26df7a9b..7205ff8f4f 100644 --- a/translations/es-ES/content/developers/overview/index.md +++ b/translations/es-ES/content/developers/overview/index.md @@ -8,7 +8,6 @@ versions: children: - /about-githubs-apis - /managing-deploy-keys - - /viewing-deployment-history - /using-ssh-agent-forwarding - /secret-scanning-partner-program - /replacing-github-services diff --git a/translations/es-ES/content/developers/webhooks-and-events/webhooks/about-webhooks.md b/translations/es-ES/content/developers/webhooks-and-events/webhooks/about-webhooks.md index b21bff7560..6fdc24938d 100644 --- a/translations/es-ES/content/developers/webhooks-and-events/webhooks/about-webhooks.md +++ b/translations/es-ES/content/developers/webhooks-and-events/webhooks/about-webhooks.md @@ -12,7 +12,7 @@ topics: - Webhooks --- -Webhooks allow you to build or set up integrations, such as [{% data variables.product.prodname_github_apps %}](/apps/building-github-apps/) or [{% data variables.product.prodname_oauth_apps %}](/apps/building-oauth-apps/), which subscribe to certain events on GitHub.com. Cuando se activa alguno de esos eventos, enviamos una carga útil de POST por HTTP a la URL que el webhook tiene configurada. Los webhooks pueden utilizarse para actualizar un rastreador de problemas externo, activar compilaciones de IC, actualizar un espejo de respaldo, o incluso para desplegar en tu servidor productivo. Solo te limita tu imaginación. +Los Webhooks te permiten crear y configurar integraciones, tales como [{% data variables.product.prodname_github_apps %}](/apps/building-github-apps/) o [{% data variables.product.prodname_oauth_apps %}](/apps/building-oauth-apps/), las cuales se suscriben a ciertos eventos en GitHub.com. Cuando se activa alguno de esos eventos, enviamos una carga útil de POST por HTTP a la URL que el webhook tiene configurada. Los webhooks pueden utilizarse para actualizar un rastreador de problemas externo, activar compilaciones de IC, actualizar un espejo de respaldo, o incluso para desplegar en tu servidor productivo. Solo te limita tu imaginación. Los webhooks pueden instalarse en{% ifversion ghes or ghae %} [{% data variables.product.prodname_enterprise %}](/rest/reference/enterprise-admin#global-webhooks/),{% endif %} una [organización][org-hooks], un [repositorio][repo-hooks] específico, o una {% data variables.product.prodname_github_app %}. Una vez que se instalan, el webhook se enviará cada vez que ocurra uno o más eventos suscritos. 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 1cc4bb0a1b..08cab6c49b 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 @@ -103,21 +103,21 @@ También, el `User-Agent` para las solicitudes tendrá el prefijo `GitHub-Hooksh {% ifversion fpt or ghes > 3.2 or ghae-next %} ## branch_protection_rule -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)." +Actividad relacionada con una regla de protección de rama. Para obtener más información, consulta la sección "[Acerca de las reglas de protección de rama](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#about-branch-protection-rules)". ### Disponibilidad - Webhooks de repositorio - Webhooks de organización -- {% data variables.product.prodname_github_apps %} with at least `read-only` access on repositories administration +- {% data variables.product.prodname_github_apps %} que tengan un acceso mínimo de `read-only` en la administración de repositorios ### Objeto de carga útil del webhook -| Clave | Type | Descripción | -| --------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción realizada. Puede ser `created`, `edited`, o `deleted`. | -| `rule` | `objeto` | 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` | `objeto` | If the action was `edited`, the changes to the rule. | +| Clave | Type | Descripción | +| --------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `Acción` | `secuencia` | La acción realizada. Puede ser `created`, `edited`, o `deleted`. | +| `rule` | `objeto` | La regla de protección de rama. Incluye un `name` y todos los [ajustes de protección de rama](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#about-branch-protection-settings) que se aplicaron a las ramas que empatan con el nombre. Los ajustes binarios son booleanos. Las configuraciones de nivel múltiple son una de entre `off`, `non_admins`, o `everyone`. Las listas de actor y compilación son arreglos de secuencias. | +| `changes` | `objeto` | Si la acción fue `edited`, los cambios a la regla. | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.sender_desc %} @@ -136,7 +136,7 @@ Activity related to a branch protection rule. For more information, see "[About - Los webhooks de repositorio solo reciben cargas útiles para los tipos de evento `created` y `completed` en un repositorio - Los webhooks de organización solo reciben cargas útiles para los tipos de evento `created` y `completed` en los repositorios -- {% 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. La app debe tener el permiso `checks:write` para recibir los tipos de evento `rerequested` y `requested_action`. Las cargas útiles para los tipos de evento `rerequested` y `requested_action` solo se enviarán a la {% data variables.product.prodname_github_app %} que se esté solicitando. {% data variables.product.prodname_github_apps %} with the `checks:write` are automatically subscribed to this webhook event. +- Las {% data variables.product.prodname_github_apps %} con el permiso `checks:read` reciben cargas útiles para los eventos `created` y `completed` que ocurren en un repositorio en donde se haya instalado la app. La app debe tener el permiso `checks:write` para recibir los tipos de evento `rerequested` y `requested_action`. Las cargas útiles para los tipos de evento `rerequested` y `requested_action` solo se enviarán a la {% data variables.product.prodname_github_app %} que se esté solicitando. Las {% data variables.product.prodname_github_apps %} con el `checks:write` se suscriben automáticamente a este evento de webhook. ### Objeto de carga útil del webhook @@ -160,7 +160,7 @@ Activity related to a branch protection rule. For more information, see "[About - Los webhooks de los repositorios únicamente recibirán cargas útiles para los tipos de evento `completed` en un repositorio - Los webhooks de organización recibirán únicamente cargas útiles para los tipos de evento `completed` en los repositorios -- {% 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. La app debe tener el permiso `checks:write` para recibir los tipos de evento `requested` y `rerequested`. Las cargas útiles para los tipos de evento `requested` y `rerequested` se envían únicamente a la {% data variables.product.prodname_github_app %} que se está solicitando. {% data variables.product.prodname_github_apps %} with the `checks:write` are automatically subscribed to this webhook event. +- Las {% data variables.product.prodname_github_apps %} con el permiso `checks:read` reciben cargas útiles para los eventos `created` y `completed` que ocurren en un repositorio en donde se haya instalado la app. La app debe tener el permiso `checks:write` para recibir los tipos de evento `requested` y `rerequested`. Las cargas útiles para los tipos de evento `requested` y `rerequested` se envían únicamente a la {% data variables.product.prodname_github_app %} que se está solicitando. Las {% data variables.product.prodname_github_apps %} con el `checks:write` se suscriben automáticamente a este evento de webhook. ### Objeto de carga útil del webhook @@ -182,7 +182,7 @@ Activity related to a branch protection rule. For more information, see "[About - Webhooks de repositorio - Webhooks de organización -- {% data variables.product.prodname_github_apps %} with the `security_events :read` permission +- {% data variables.product.prodname_github_apps %} con el permiso `security_events :read` ### Objeto de carga útil del webhook @@ -190,7 +190,7 @@ Activity related to a branch protection rule. For more information, see "[About {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} -`sender` | `object` | Si la `action` está como `reopened_by_user` o `closed_by_user`, el objeto que sea el `sender` será el usuario que activó el evento. El objeto `sender` está {% ifversion fpt %}`github` {% elsif ghes > 3.0 %}`github-enterprise` {% else %}vacío{% endif %} para el resto de las acciones. +`sender` | `object` | Si la `action` está como `reopened_by_user` o `closed_by_user`, el objeto que sea el `sender` será el usuario que activó el evento. El objeto `sender` está {% ifversion fpt %}`github` {% elsif ghes > 3.0 or ghae-next %}`github-enterprise` {% else %}vacío{% endif %} para el resto de las acciones. ### Ejemplo de carga útil del webhook @@ -204,7 +204,7 @@ Activity related to a branch protection rule. For more information, see "[About - Webhooks de repositorio - Webhooks de organización -- {% data variables.product.prodname_github_apps %} with the `contents` permission +- {% data variables.product.prodname_github_apps %} con el permiso `contents` ### Objeto de carga útil del webhook @@ -226,7 +226,7 @@ Los eventos de webhook se desencadenan basándose en la especificidad del domini ### Disponibilidad -- {% data variables.product.prodname_github_apps %} with the `content_references:write` permission +- {% data variables.product.prodname_github_apps %} con el permiso `content_references:write` ### Ejemplo de carga útil del webhook @@ -246,7 +246,7 @@ Los eventos de webhook se desencadenan basándose en la especificidad del domini - Webhooks de repositorio - Webhooks de organización -- {% data variables.product.prodname_github_apps %} with the `contents` permission +- {% data variables.product.prodname_github_apps %} con el permiso `contents` ### Objeto de carga útil del webhook @@ -275,7 +275,7 @@ Los eventos de webhook se desencadenan basándose en la especificidad del domini - Webhooks de repositorio - Webhooks de organización -- {% data variables.product.prodname_github_apps %} with the `contents` permission +- {% data variables.product.prodname_github_apps %} con el permiso `contents` ### Objeto de carga útil del webhook @@ -318,7 +318,7 @@ Los eventos de webhook se desencadenan basándose en la especificidad del domini - Webhooks de repositorio - Webhooks de organización -- {% data variables.product.prodname_github_apps %} with the `deployments` permission +- {% data variables.product.prodname_github_apps %} con el permiso `deployments` ### Objeto de carga útil del webhook @@ -343,7 +343,7 @@ Los eventos de webhook se desencadenan basándose en la especificidad del domini - Webhooks de repositorio - Webhooks de organización -- {% data variables.product.prodname_github_apps %} with the `deployments` permission +- {% data variables.product.prodname_github_apps %} con el permiso `deployments` ### Objeto de carga útil del webhook @@ -374,7 +374,7 @@ Actividad relacionada con un debate. Para obtener más información, consulta la - Webhooks de repositorio - Webhooks de organización -- {% data variables.product.prodname_github_apps %} with the `discussions` permission +- Las {% data variables.product.prodname_github_apps %} con el permiso de `discussions` ### Objeto de carga útil del webhook @@ -400,7 +400,7 @@ La actividad relacionada con un comentario en un debate. Para obtener más infor - Webhooks de repositorio - Webhooks de organización -- {% data variables.product.prodname_github_apps %} with the `discussions` permission +- Las {% data variables.product.prodname_github_apps %} con el permiso de `discussions` ### Objeto de carga útil del webhook @@ -448,7 +448,7 @@ La actividad relacionada con un comentario en un debate. Para obtener más infor - Webhooks de repositorio - Webhooks de organización -- {% data variables.product.prodname_github_apps %} with the `contents` permission +- {% data variables.product.prodname_github_apps %} con el permiso `contents` ### Objeto de carga útil del webhook @@ -466,7 +466,7 @@ La actividad relacionada con un comentario en un debate. Para obtener más infor Este evento ocurre cuando alguien revoca su autorización de una {% data variables.product.prodname_github_app %}. Una {% data variables.product.prodname_github_app %} recibe este webhook predeterminadamente y no puede desuscribirse de este evento. -{% 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/)." +{% data reusables.webhooks.authorization_event %} Para obtener detalles sobre las solicitudes de usuario a servidor, las cuales requieren autorización de la {% data variables.product.prodname_github_app %}, consulta la sección "[Identificar y autorizar a los usuarios para las {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)". ### Disponibilidad @@ -491,7 +491,7 @@ Este evento ocurre cuando alguien revoca su autorización de una {% data variabl - Webhooks de repositorio - Webhooks de organización -- {% data variables.product.prodname_github_apps %} with the `contents` permission +- {% data variables.product.prodname_github_apps %} con el permiso `contents` ### Objeto de carga útil del webhook @@ -549,7 +549,7 @@ Este evento ocurre cuando alguien revoca su autorización de una {% data variabl - Webhooks de repositorio - Webhooks de organización -- {% data variables.product.prodname_github_apps %} with the `issues` permission +- {% data variables.product.prodname_github_apps %} con el permiso `issues` ### Objeto de carga útil del webhook @@ -572,7 +572,7 @@ Este evento ocurre cuando alguien revoca su autorización de una {% data variabl - Webhooks de repositorio - Webhooks de organización -- {% data variables.product.prodname_github_apps %} with the `issues` permission +- {% data variables.product.prodname_github_apps %} con el permiso `issues` ### Objeto de carga útil del webhook @@ -595,7 +595,7 @@ Este evento ocurre cuando alguien revoca su autorización de una {% data variabl - Webhooks de repositorio - Webhooks de organización -- {% data variables.product.prodname_github_apps %} with the `metadata` permission +- {% data variables.product.prodname_github_apps %} con el permiso `metadata` ### Objeto de carga útil del webhook @@ -646,7 +646,7 @@ Para obtener una descripción detallada de esta carga útil y de aquella para ca - Webhooks de repositorio - Webhooks de organización -- {% data variables.product.prodname_github_apps %} with the `members` permission +- {% data variables.product.prodname_github_apps %} con el permiso `members` ### Objeto de carga útil del webhook @@ -668,7 +668,7 @@ Para obtener una descripción detallada de esta carga útil y de aquella para ca ### Disponibilidad - Webhooks de organización -- {% data variables.product.prodname_github_apps %} with the `members` permission +- {% data variables.product.prodname_github_apps %} con el permiso `members` ### Objeto de carga útil del webhook @@ -713,7 +713,7 @@ Se eliminó el evento para el cual se configuró este webhook. Este evento únic - Webhooks de repositorio - Webhooks de organización -- {% data variables.product.prodname_github_apps %} with the `pull_requests` permission +- {% data variables.product.prodname_github_apps %} con el permiso `pull_requests` ### Objeto de carga útil del webhook @@ -736,7 +736,7 @@ Se eliminó el evento para el cual se configuró este webhook. Este evento únic {% ifversion ghes or ghae %} - Los webhooks de GitHub Enterprise reciben únicamente eventos de `created` y `deleted`. Para obtener más información, consulta los "[webhooks globales](/rest/reference/enterprise-admin#global-webhooks/).{% endif %} - Los webhooks de organización únicamente reciben los eventos `deleted`, `added`, `removed`, `renamed`, y `invited` events -- {% data variables.product.prodname_github_apps %} with the `members` permission +- {% data variables.product.prodname_github_apps %} con el permiso `members` ### Objeto de carga útil del webhook @@ -762,7 +762,7 @@ Se eliminó el evento para el cual se configuró este webhook. Este evento únic ### Disponibilidad - Webhooks de organización -- {% data variables.product.prodname_github_apps %} with the `organization_administration` permission +- {% data variables.product.prodname_github_apps %} con el permiso `organization_administration` ### Objeto de carga útil del webhook @@ -811,7 +811,7 @@ Actividad relacionada con el {% data variables.product.prodname_registry %}. {% - Webhooks de repositorio - Webhooks de organización -- {% data variables.product.prodname_github_apps %} with the `pages` permission +- {% data variables.product.prodname_github_apps %} con el permiso `pages` ### Objeto de carga útil del webhook @@ -836,7 +836,7 @@ Actividad relacionada con el {% data variables.product.prodname_registry %}. {% - Webhooks de repositorio - Webhooks de organización -- {% data variables.product.prodname_github_apps %} receive a ping event with an `app_id` used to register the app +- Las {% data variables.product.prodname_github_apps %} reciben un evento de ping con un `app_id` que se utiliza para registrar la app ### Objeto de carga útil del webhook @@ -862,7 +862,7 @@ Actividad relacionada con el {% data variables.product.prodname_registry %}. {% - Webhooks de repositorio - Webhooks de organización -- {% data variables.product.prodname_github_apps %} with the `repository_projects` or `organization_projects` permission +- Las {% data variables.product.prodname_github_apps %} con el permiso `repository_projects` or `organization_projects` ### Objeto de carga útil del webhook @@ -884,7 +884,7 @@ Actividad relacionada con el {% data variables.product.prodname_registry %}. {% - Webhooks de repositorio - Webhooks de organización -- {% data variables.product.prodname_github_apps %} with the `repository_projects` or `organization_projects` permission +- Las {% data variables.product.prodname_github_apps %} con el permiso `repository_projects` or `organization_projects` ### Objeto de carga útil del webhook @@ -906,7 +906,7 @@ Actividad relacionada con el {% data variables.product.prodname_registry %}. {% - Webhooks de repositorio - Webhooks de organización -- {% data variables.product.prodname_github_apps %} with the `repository_projects` or `organization_projects` permission +- Las {% data variables.product.prodname_github_apps %} con el permiso `repository_projects` or `organization_projects` ### Objeto de carga útil del webhook @@ -928,7 +928,7 @@ Actividad relacionada con el {% data variables.product.prodname_registry %}. {% - Webhooks de repositorio - Webhooks de organización -- {% data variables.product.prodname_github_apps %} with the `metadata` permission +- {% data variables.product.prodname_github_apps %} con el permiso `metadata` ### Objeto de carga útil del webhook @@ -952,7 +952,7 @@ Actividad relacionada con el {% data variables.product.prodname_registry %}. {% - Webhooks de repositorio - Webhooks de organización -- {% data variables.product.prodname_github_apps %} with the `pull_requests` permission +- {% data variables.product.prodname_github_apps %} con el permiso `pull_requests` ### Objeto de carga útil del webhook @@ -977,7 +977,7 @@ Las entregas para los eventos `review_requested` y `review_request_removed` tend - Webhooks de repositorio - Webhooks de organización -- {% data variables.product.prodname_github_apps %} with the `pull_requests` permission +- {% data variables.product.prodname_github_apps %} con el permiso `pull_requests` ### Objeto de carga útil del webhook @@ -999,7 +999,7 @@ Las entregas para los eventos `review_requested` y `review_request_removed` tend - Webhooks de repositorio - Webhooks de organización -- {% data variables.product.prodname_github_apps %} with the `pull_requests` permission +- {% data variables.product.prodname_github_apps %} con el permiso `pull_requests` ### Objeto de carga útil del webhook @@ -1028,28 +1028,33 @@ Las entregas para los eventos `review_requested` y `review_request_removed` tend - Webhooks de repositorio - Webhooks de organización -- {% data variables.product.prodname_github_apps %} with the `contents` permission +- {% data variables.product.prodname_github_apps %} con el permiso `contents` ### Objeto de carga útil del webhook -| Clave | Type | Descripción | -| -------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `ref` | `secuencia` | Toda la [`git ref`](/rest/reference/git#refs) que se cargó. Ejemplo: `refs/heads/main`. | -| `before` | `secuencia` | El SHA de la confirmación más reciente en `ref` antes de la carga. | -| `after` | `secuencia` | El SHA de la confirmación más reciente en `ref` después de la carga. | -| `commits` | `arreglo` | Un conjunto de objetos de confirmación que describen las confirmaciones subidas. (El conjunto incluye un máximo de 20 confirmaciones. De ser encesario, puedes utilizar la [API de confirmaciones](/rest/reference/repos#commits) para recuperar confirmaciones adicionales. Este límite se aplica a los eventos cronológicos únicamente y no se aplica a las entregas de webhooks). | -| `commits[][id]` | `secuencia` | El SHA de la confirmación. | -| `commits[][timestamp]` | `secuencia` | La marca de tiempo de tipo ISO 8601 de la confirmación. | -| `commits[][message]` | `secuencia` | El mensaje de la confirmación. | -| `commits[][author]` | `objeto` | El autor de git de la confirmación. | -| `commits[][author][name]` | `secuencia` | El nombre del autor de git. | -| `commits[][author][email]` | `secuencia` | La dirección de correo electrónico del autor de git. | -| `commits[][url]` | `url` | URL que apunta al recurso de la API de la confirmación. | -| `commits[][distinct]` | `boolean` | Si la confirmación es distinta de cualquier otra que se haya subido antes. | -| `commits[][added]` | `arreglo` | Un arreglo de archivos que se agregaron en la confirmación. | -| `commits[][modified]` | `arreglo` | Un areglo de archivos que modificó la confirmación. | -| `commits[][removed]` | `arreglo` | Un arreglo de archivos que se eliminaron en la confirmación. | -| `pusher` | `objeto` | El usuario que subió la confirmación. | +| Clave | Tipo | Descripción | +| -------------------------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `ref` | `secuencia` | Toda la [`git ref`](/rest/reference/git#refs) que se cargó. Ejemplo: `refs/heads/main` o `refs/tags/v3.14.1`. | +| `before` | `secuencia` | El SHA de la confirmación más reciente en `ref` antes de la carga. | +| `after` | `secuencia` | El SHA de la confirmación más reciente en `ref` después de la carga. | +| `created` | `boolean` | Si es que esta subida creó la `ref`. | +| `deleted` | `boolean` | Si es que esta subida borró la `ref`. | +| `forced` | `boolean` | Si es que esta subida fue una subida forzada de la `ref`. | +| `head_commit` | `objeto` | Para las subidas en donde `after` es o apunta a un objeto de confirmación, es una representación expandida de dicha confirmación. Para las subidas en donde `after` se refiere a un objeto de etiqueta anotada, es una representación expandida de la confirmación a la que otra etiqueta apuntó. | +| `compare` | `secuencia` | URL que muestra los cambios en esta actualización de `ref`, desde la confirmación `before` hasta la de `after`. Para una `ref` recién creada que se basa directamente en la rama predeterminada, esta es la comparación entre el encabezado de la rama predeterminada y la confirmación de `after`. De lo contrario, esto muestra todas las confirmaciones hasta la confirmación de `after`. | +| `commits` | `arreglo` | Un conjunto de objetos de confirmación que describen las confirmaciones subidas. (Las confirmaciones subidas son todas las que se incluyen en el `compare` entre la confirmación de `before` y la de `after`). El arreglo incluye un máximo de 20 confirmaciones. De ser encesario, puedes utilizar la [API de confirmaciones](/rest/reference/repos#commits) para recuperar confirmaciones adicionales. Este límite se aplica a los eventos cronológicos únicamente y no se aplica a las entregas de webhooks. | +| `commits[][id]` | `secuencia` | El SHA de la confirmación. | +| `commits[][timestamp]` | `secuencia` | La marca de tiempo de tipo ISO 8601 de la confirmación. | +| `commits[][message]` | `secuencia` | El mensaje de la confirmación. | +| `commits[][author]` | `objeto` | El autor de git de la confirmación. | +| `commits[][author][name]` | `secuencia` | El nombre del autor de git. | +| `commits[][author][email]` | `secuencia` | La dirección de correo electrónico del autor de git. | +| `commits[][url]` | `url` | URL que apunta al recurso de la API de la confirmación. | +| `commits[][distinct]` | `boolean` | Si la confirmación es distinta de cualquier otra que se haya subido antes. | +| `commits[][added]` | `arreglo` | Un arreglo de archivos que se agregaron en la confirmación. | +| `commits[][modified]` | `arreglo` | Un areglo de archivos que modificó la confirmación. | +| `commits[][removed]` | `arreglo` | Un arreglo de archivos que se eliminaron en la confirmación. | +| `pusher` | `objeto` | El usuario que subió la confirmación. | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} @@ -1067,7 +1072,7 @@ Las entregas para los eventos `review_requested` y `review_request_removed` tend - Webhooks de repositorio - Webhooks de organización -- {% data variables.product.prodname_github_apps %} with the `contents` permission +- {% data variables.product.prodname_github_apps %} con el permiso `contents` ### Objeto de carga útil del webhook @@ -1089,7 +1094,7 @@ Este evento ocurre cuando una {% data variables.product.prodname_github_app %} e ### Disponibilidad -- {% data variables.product.prodname_github_apps %} must have the `contents` permission to receive this webhook. +- Las {% data variables.product.prodname_github_apps %} deben tener el permiso `contents` para recibir este webhook. ### Ejemplo de carga útil del webhook @@ -1104,7 +1109,7 @@ Este evento ocurre cuando una {% data variables.product.prodname_github_app %} e - Los webhooks de repositorio reciben todos los eventos excepto los de `deleted` - Webhooks de organización -- {% data variables.product.prodname_github_apps %} with the `metadata` permission receive all event types except `deleted` +- Las {% data variables.product.prodname_github_apps %} con el permiso `metadata` reciben todos los tipos de evento menos los de `deleted` ### Objeto de carga útil del webhook @@ -1173,7 +1178,7 @@ Este evento ocurre cuando una {% data variables.product.prodname_github_app %} e - Webhooks de repositorio - Webhooks de organización -- {% data variables.product.prodname_github_apps %} with the `secret_scanning_alerts:read` permission +- Las {% data variables.product.prodname_github_apps %} con el permiso de `secret_scanning_alerts:read` ### Objeto de carga útil del webhook @@ -1196,7 +1201,7 @@ Actividad relacionada con una asesoría de seguridad. Una asesoría de seguridad ### Disponibilidad -- {% data variables.product.prodname_github_apps %} with the `security_events` permission +- {% data variables.product.prodname_github_apps %} con el permiso `security_events` ### Objeto de carga útil del webhook @@ -1264,7 +1269,7 @@ Solo puedes crear un webhook de patrocinio en {% data variables.product.prodname - Webhooks de repositorio - Webhooks de organización -- {% data variables.product.prodname_github_apps %} with the `statuses` permission +- {% data variables.product.prodname_github_apps %} con el permiso `statuses` ### Objeto de carga útil del webhook @@ -1292,7 +1297,7 @@ Solo puedes crear un webhook de patrocinio en {% data variables.product.prodname ### Disponibilidad - Webhooks de organización -- {% data variables.product.prodname_github_apps %} with the `members` permission +- {% data variables.product.prodname_github_apps %} con el permiso `members` ### Objeto de carga útil del webhook @@ -1323,7 +1328,7 @@ Solo puedes crear un webhook de patrocinio en {% data variables.product.prodname - Webhooks de repositorio - Webhooks de organización -- {% data variables.product.prodname_github_apps %} with the `members` permission +- {% data variables.product.prodname_github_apps %} con el permiso `members` ### Objeto de carga útil del webhook @@ -1364,7 +1369,7 @@ El actor del evento es el [usuario](/rest/reference/users) que marcó el reposit - Webhooks de repositorio - Webhooks de organización -- {% data variables.product.prodname_github_apps %} with the `metadata` permission +- {% data variables.product.prodname_github_apps %} con el permiso `metadata` ### Objeto de carga útil del webhook @@ -1385,7 +1390,7 @@ Este evento ocurre cuando alguien activa una ejecución de flujo de trabajo en G ### Disponibilidad -- {% data variables.product.prodname_github_apps %} must have the `contents` permission to receive this webhook. +- Las {% data variables.product.prodname_github_apps %} deben tener el permiso `contents` para recibir este webhook. ### Ejemplo de carga útil del webhook @@ -1402,7 +1407,7 @@ Este evento ocurre cuando alguien activa una ejecución de flujo de trabajo en G - Webhooks de repositorio - Webhooks de organización -- Enterprise webhooks +- Webhooks empresariales ### Objeto de carga útil del webhook @@ -1423,7 +1428,7 @@ Cuando una ejecución de flujo de trabajo de {% data variables.product.prodname_ ### Disponibilidad -- {% data variables.product.prodname_github_apps %} with the `actions` or `contents` permissions. +- En {% data variables.product.prodname_github_apps %} con los permisos de `actions` o de `contents`. ### Objeto de carga útil del webhook diff --git a/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md b/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md index 6c3ed23303..6e0fddcecb 100644 --- a/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md +++ b/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md @@ -18,7 +18,7 @@ Con los {% data variables.product.prodname_discussions %}, la comunidad de tu pr No necesitas cerrar un debate de la misma forma en que cierras una propuesta o una solicitud de cambios. -If a repository administrator or project maintainer enables {% data variables.product.prodname_discussions %} for a repository, anyone who visits the repository can create and participate in discussions for the repository. Los administradores del repositorio y los mantenedores del proyecto pueden administrar los debates y las categorías de los mismos en un repositorio y fijarlos para incrementar la visibilidad de éstos. Los moderadores y colaboradores pueden marcar los comentarios como respuestas, fijar debates, y convertir las propuestas en debates. Para obtener más información, consulta "[Niveles de permiso del repositorio para una organización](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)". +Si un administrador de repositorio o mantenedor de proyecto habilita los {% data variables.product.prodname_discussions %} para un repositorio, cualquiera que visite el repositorio podrá crear y participar en los debates de este. Los administradores del repositorio y los mantenedores del proyecto pueden administrar los debates y las categorías de los mismos en un repositorio y fijarlos para incrementar la visibilidad de éstos. Los moderadores y colaboradores pueden marcar los comentarios como respuestas, fijar debates, y convertir las propuestas en debates. Para obtener más información, consulta "[Niveles de permiso del repositorio para una organización](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)". Para obtener más información sobre la adminsitración de debates para tu repositorio, consulta la sección "[Administrar debates en tu repositorio](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)". @@ -36,7 +36,7 @@ Para obtener más información, consulta la sección "[Administrar las categorí {% data reusables.discussions.you-can-label-discussions %} -## Best practices for {% data variables.product.prodname_discussions %} +## Mejores prácticas para los {% data variables.product.prodname_discussions %} Como mantenedor o miembro de la comunidad, inicia un debate para hacer una pregunta o debatir información que les afecte. Para obtener más información, consulta la sección "[Colaborar con los mantenedores a través de los debates](/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions)". @@ -53,7 +53,7 @@ Puedes compartir tu retroalimentación sobre los {% data variables.product.prodn ## Leer más - "[Acerca de escribir y dar formato en {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)" -- "[Buscar debates](/github/searching-for-information-on-github/searching-discussions)" +- "[Buscar debates](/search-github/searching-on-github/searching-discussions)" - "[Acerca de las notificaciones](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" - "[Moderar comentarios y conversaciones](/communities/moderating-comments-and-conversations)" - "[Mantener tu seguridad en {% data variables.product.prodname_dotcom %}](/communities/maintaining-your-safety-on-github)" diff --git a/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md b/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md index 56d4501630..529c399574 100644 --- a/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md +++ b/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md @@ -2,13 +2,13 @@ title: Colaborar con los mantenedores utilizando debates shortTitle: Colaborar con los mantenedores intro: 'Puedes contribuir a las metas, planes, salud y comunidad de un proyecto en {% data variables.product.product_name %} si te comunicas con los mantenedores del proyecto en un debate.' -permissions: People with read permissions to a repository can start and participate in discussions in the repository. +permissions: 'People with read access to a repository can start and participate in discussions in the repository. {% data reusables.enterprise-accounts.emu-permission-interact %}' versions: fpt: '*' --- -## About collaboration with maintainers using {% data variables.product.prodname_discussions %} +## Acerca de la colaboración con mantenedores utilizando los {% data variables.product.prodname_discussions %} {% data reusables.discussions.about-discussions %} Si utilizas o contribuyes con un proyecto, puedes iniciar un debate para hacer sugerencias e interactuar con los manenedores y miembros de la comunidad con respecto a tus planes, preguntas, ideas y retroalimentación. Para obtener más información, consulta la sección "[‎Acerca de los debates](/discussions/collaborating-with-your-community-using-discussions/about-discussions)". @@ -24,7 +24,7 @@ Para obtener más información acerca de la participación en los debates, consu ## Prerrequisitos -To collaborate with maintainers in discussions, a repository administrator or project maintainer must enable {% data variables.product.prodname_discussions %} for the repository. For more information, see "[Enabling or disabling {% data variables.product.prodname_discussions %} for a repository](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)." +Para colaborar con los mantenedores en los debates, un administrador de repositorio o mantenedor de proyecto debe habilitar los {% data variables.product.prodname_discussions %} para el repositorio. Para obtener más información, consulta la sección "[Habilitar o inhabilitar los {% data variables.product.prodname_discussions %} para un repositorio](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)". ## Iniciar un debate @@ -32,7 +32,7 @@ To collaborate with maintainers in discussions, a repository administrator or pr ## Filtrar la lista de debates -Puedes buscar debates y filtrar la lista de éstos en un repositorio. Para obtener más información, consulta la sección "[Buscar buscar debates](/github/searching-for-information-on-github/searching-discussions)". +Puedes buscar debates y filtrar la lista de éstos en un repositorio. Para obtener más información, consulta la sección "[Buscar buscar debates](/search-github/searching-on-github/searching-discussions)". {% data reusables.repositories.navigate-to-repo %} {% data reusables.discussions.discussions-tab %} diff --git a/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md b/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md index 19d022cd53..cc3eb0bd4e 100644 --- a/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md +++ b/translations/es-ES/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md @@ -1,7 +1,7 @@ --- title: Participar en un debate intro: 'Puedes conversar con la comunidad y con los mantenedores en un foro dentro del repositorio de un proyecto en {% data variables.product.product_name %}.' -permissions: People with read permissions to a repository can participate in discussions in the repository. +permissions: 'People with read access to a repository can participate in discussions in the repository. {% data reusables.enterprise-accounts.emu-permission-interact %}' versions: fpt: '*' shortTitle: Participa en un debate @@ -18,7 +18,7 @@ Puedes bloquear usuarios y reportar el contenido perjudicial para mantener un am ## Prerrequisitos -{% data variables.product.prodname_discussions %} must be enabled for the repository for you to participate in a discussion in the repository. For more information, see "[Enabling or disabling {% data variables.product.prodname_discussions %} for a repository](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)." +Los {% data variables.product.prodname_discussions %} deben estar habilitados en el repositorio para que participes en un debate de este. Para obtener más información, consulta la sección "[Habilitar o inhabilitar los {% data variables.product.prodname_discussions %} para un repositorio](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)". ## Crear un debate diff --git a/translations/es-ES/content/discussions/guides/best-practices-for-community-conversations-on-github.md b/translations/es-ES/content/discussions/guides/best-practices-for-community-conversations-on-github.md index 564b9d4c63..c6046a4d0b 100644 --- a/translations/es-ES/content/discussions/guides/best-practices-for-community-conversations-on-github.md +++ b/translations/es-ES/content/discussions/guides/best-practices-for-community-conversations-on-github.md @@ -1,7 +1,7 @@ --- title: Mejores prácticas para las conversaciones comunitarias en GitHub shortTitle: Mejores prácticas para las conversaciones comunitarias -intro: 'You can use discussions to brainstorm with your team, and eventually move the conversation to an issue when you are ready to scope out the work.' +intro: 'Puedes utilizar los debates para hacer una lluvia de ideas con tu equipo y, en algún momento, migrar la conversación a una propuesta cuando estés listo para delimitar el trabajo.' versions: fpt: '*' --- @@ -21,7 +21,7 @@ Para obtener más información acerca de abrir propuestas y hacer referencias cr Puedes crear y participar en los debates, propuestas y solicitudes de cambio dependiendo del tipo de conversación que desees tener. -Puedes utilizar lps {% data variables.product.prodname_discussions %} para debatir las ideas más amplias, hacer lluvias de ideas y resaltar los detalles específicos de un proyecto antes de hacer cualquier confirmación en una propuesta, la cual puede aumetar su alcance posteriormente. {% data variables.product.prodname_discussions %} is useful for teams if: +Puedes utilizar lps {% data variables.product.prodname_discussions %} para debatir las ideas más amplias, hacer lluvias de ideas y resaltar los detalles específicos de un proyecto antes de hacer cualquier confirmación en una propuesta, la cual puede aumetar su alcance posteriormente. Los {% data variables.product.prodname_discussions %} son útiles para los equipos si: - Estás en la fase de descubrimiento de un proyecto y aún estás aprendiendo en qué dirección quiere ir tu equipo. - Quieres recolectar los comentarios de una comunidad más amplia sobre un proyecto - Quieres mantener la separación entre las correcciones de errores y las conversaciones generales diff --git a/translations/es-ES/content/discussions/guides/finding-discussions-across-multiple-repositories.md b/translations/es-ES/content/discussions/guides/finding-discussions-across-multiple-repositories.md index 4bc66d4b7c..3b7e4040b0 100644 --- a/translations/es-ES/content/discussions/guides/finding-discussions-across-multiple-repositories.md +++ b/translations/es-ES/content/discussions/guides/finding-discussions-across-multiple-repositories.md @@ -15,6 +15,6 @@ shortTitle: Encontrar debates ## Leer más -- "[Buscar debates](/github/searching-for-information-on-github/searching-discussions)" +- "[Buscar debates](/search-github/searching-on-github/searching-discussions)" - "[Acerca de los debates](/discussions/collaborating-with-your-community-using-discussions/about-discussions)" - "[Administrar debates para tu comunidad](/discussions/managing-discussions-for-your-community)" diff --git a/translations/es-ES/content/discussions/guides/granting-higher-permissions-to-top-contributors.md b/translations/es-ES/content/discussions/guides/granting-higher-permissions-to-top-contributors.md index 9e1ecbfcd9..19b736e832 100644 --- a/translations/es-ES/content/discussions/guides/granting-higher-permissions-to-top-contributors.md +++ b/translations/es-ES/content/discussions/guides/granting-higher-permissions-to-top-contributors.md @@ -11,13 +11,13 @@ shortTitle: Otorgar permisos mayores Los colaboradores más útiles en los últimos 30 días se resaltarán en el tablero de {% data variables.product.prodname_discussions %} con base en cuántos comentarios marcaron otros miembros de la comunidad como respuestas. Los colaboradores útiles pueden ayudar a mantener una comunidad saludable y a moderar y guiar el espacio comunitario adicionalmente al trabajo que hacen los mantenedores. -## Step 1: Audit your {% data variables.product.prodname_discussions %} top contributors +## Pase 1: Audita tus contribuyentes principales de los {% data variables.product.prodname_discussions %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.discussions.discussions-tab %} 1. Compara la lista de contribuyentes con sus permisos de acceso para ver quién califica para moderar el debate. -## Step 2: Review permission levels for {% data variables.product.prodname_discussions %} +## Paso 2: Revisa los niveles de permiso de los {% data variables.product.prodname_discussions %} Las personas con permisos de clasificación en un repositorio pueden ayudar a moderar los debates de un proyecto si marcan los comentarios como respuestas, fijar los debates que ya no son útiles o que están haciendo daño a la comunidad, y convertir las propuestas en debates cuando una idea aún se encuentra en una etapa temprana de desarrollo. Para obtener más información, consulta la sección "[Moderar los debates](/discussions/managing-discussions-for-your-community/moderating-discussions)". diff --git a/translations/es-ES/content/discussions/index.md b/translations/es-ES/content/discussions/index.md index 363e8e70bd..ff84f4391a 100644 --- a/translations/es-ES/content/discussions/index.md +++ b/translations/es-ES/content/discussions/index.md @@ -1,6 +1,5 @@ --- title: Documentación sobre los debates de GitHub -beta_product: true shortTitle: GitHub Discussions intro: '{% data variables.product.prodname_discussions %} es un foro de comunicación colaborativa para la comunidad que circunda un proyecto de código abierto. Los miembros de la comunidad pueden hacer preguntas y proporcionar respuestas, compartir actualizaciones, tener conversaciones abiertas y dar seguimiento a las decisiones que afectan la forma de trabajar de la misma.' introLinks: @@ -24,6 +23,7 @@ featuredLinks: - /discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository changelog: label: discussions +examples_source: data/product-examples/discussions/community-examples.yml product_video: 'https://www.youtube-nocookie.com/embed/IpBw2SJkFyk' layout: product-landing versions: diff --git a/translations/es-ES/content/discussions/managing-discussions-for-your-community/index.md b/translations/es-ES/content/discussions/managing-discussions-for-your-community/index.md index 6238f9a2fa..dc3a831494 100644 --- a/translations/es-ES/content/discussions/managing-discussions-for-your-community/index.md +++ b/translations/es-ES/content/discussions/managing-discussions-for-your-community/index.md @@ -1,7 +1,7 @@ --- title: Administrar los debates para tu comunidad shortTitle: Administrar los debates -intro: 'You can enable and configure {% data variables.product.prodname_discussions %} for your repository, and you can use tools on {% data variables.product.product_name %} to moderate conversations among community members.' +intro: 'Puedes habilitar y configurar los {% data variables.product.prodname_discussions %} en tu repositorio y puedes utilizar herramientas en {% data variables.product.product_name %} para moderar conversaciones entre los miembros de la comunidad.' versions: fpt: '*' children: diff --git a/translations/es-ES/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md b/translations/es-ES/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md index bca8224b6d..e815762830 100644 --- a/translations/es-ES/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md +++ b/translations/es-ES/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md @@ -16,7 +16,7 @@ Los propietarios de la organización pueden elegir los permisos que se requieren Como mantenedor de debates, puedes crear recursos comunitarios para impulsar los debates que se alinien con la meta general del proyecto y mantener así un foro abierto y amistoso para los colaboradores. El crear un código de conducta o lineamientos de contribución para que los colaboradores los sigan te ayudará a proporcionar un foro colaborativo y productivo. Para obtener más información sobre cómo crear recursos comunitarios, consulta las secciones "[Agregar un código de conducta a tu proyecto](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)" y "[Configurar los lineamientos para los contribuyentes de un repositorio](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)". -When a discussion yields an idea or bug that is ready to be worked on, you can create a new issue from a discussion. Para obtener más información, consulta la sección "[Crear una propuesta](/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-discussion)". +Cuando un debate produce una idea o error que está listo para solucionarse, puedes crear una propuesta nueva desde un debate. Para obtener más información, consulta la sección "[Crear una propuesta](/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-discussion)". Para obtener más información sobre cómo proporcionar un debate sano, consulta la sección "[Moderar los comentarios y conversaciones](/communities/moderating-comments-and-conversations)". @@ -24,7 +24,7 @@ Para obtener más información sobre cómo proporcionar un debate sano, consulta ## Prerrequisitos -To manage discussions in a repository, {% data variables.product.prodname_discussions %} must be enabled for the repository. For more information, see "[Enabling or disabling {% data variables.product.prodname_discussions %} for a repository](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)." +Para administrar los debates en un repositorio, debes habilitar los {% data variables.product.prodname_discussions %} en este. Para obtener más información, consulta la sección "[Habilitar o inhabilitar los {% data variables.product.prodname_discussions %} para un repositorio](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)". ## Cambiar la categoría de un debate @@ -56,7 +56,7 @@ Editar un debate que se ha fijado no cambiará la categoría del mismo. Para obt {% data reusables.repositories.navigate-to-repo %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %} -1. En la barra lateral derecha, da clic en {% octicon "pencil" aria-label="The pencil icon" %} **Editar debate fijado**. !["Edit pinned discussion" in right sidebar for discussion](/assets/images/help/discussions/click-edit-pinned-discussion.png) +1. En la barra lateral derecha, da clic en {% octicon "pencil" aria-label="The pencil icon" %} **Editar debate fijado**. !["Editar debate fijado" en la barra lateral derecha de un debate](/assets/images/help/discussions/click-edit-pinned-discussion.png) 1. Personaliza la apariencia del debate que fijaste. ![Opciones de personalización para un debate que se fijó](/assets/images/help/discussions/customize-pinned-discussion.png) 1. Da clic en **Fijar debate**. ![Botón de "Fijar debate" debajo de las opciones de personalización para un debate fijado](/assets/images/help/discussions/click-pin-discussion-button.png) diff --git a/translations/es-ES/content/discussions/managing-discussions-for-your-community/moderating-discussions.md b/translations/es-ES/content/discussions/managing-discussions-for-your-community/moderating-discussions.md index 98b055ef0f..caa9081f4b 100644 --- a/translations/es-ES/content/discussions/managing-discussions-for-your-community/moderating-discussions.md +++ b/translations/es-ES/content/discussions/managing-discussions-for-your-community/moderating-discussions.md @@ -1,6 +1,6 @@ --- title: Moderar los debates -intro: 'You can promote healthy collaboration by marking comments as answers, locking or unlocking discussions, converting issues to discussions, and editing or deleting comments, discussions, and categories that don''t align with your community''s code of conduct.' +intro: 'Puedes promover una colaboración sana si marcas los comentarios como respuestas, bloqueando y desbloqueando debates, convirtiendo propuestas en debates y editando o borrando los comentarios, debates y categorías que no se alineen con el código de conducta de tu comunidad.' permissions: People with triage access to a repository can moderate discussions in the repository. versions: fpt: '*' diff --git a/translations/es-ES/content/discussions/quickstart.md b/translations/es-ES/content/discussions/quickstart.md index bf6c8be155..8d9306e508 100644 --- a/translations/es-ES/content/discussions/quickstart.md +++ b/translations/es-ES/content/discussions/quickstart.md @@ -18,17 +18,17 @@ Los debates proporcionan un espacio para que existan conversaciones colaborativa Los propietarios de los repositorios y las personas con acceso de escritura pueden habilitar los {% data variables.product.prodname_discussions %} para una comunidad en sus repositorios privados o públicos. -When you first enable {% data variables.product.prodname_discussions %}, you will be invited to configure a welcome post. +Cuando habilitas los {% data variables.product.prodname_discussions %} por primera vez, se te invitará a configurar una publicación de bienvenida. {% data reusables.repositories.navigate-to-repo %} 1. Debajo de tu nombre de repositorio, da clic en {% octicon "gear" aria-label="The gear icon" %} **Configuración**. ![Botón de configuración pública](/assets/images/help/discussions/public-repo-settings.png) -1. Debajo de "Características", da clic en **Configurar debates**. ![Set up a discussion button under "Features" for enabling or disabling GitHub Discussions for a repository](/assets/images/help/discussions/setup-discussions-button.png) +1. Debajo de "Características", da clic en **Configurar debates**. ![Configurar un botón de debate debajo de las "Características" para habilitar o inhabilitar los debates de GitHub en un repositorio](/assets/images/help/discussions/setup-discussions-button.png) 1. Debajo de "Iniciar un debate nuevo" edita la plantilla para que se apegue con los recursos y el tono que quieras configurar para tu comunidad. 1. Da clic en **Iniciar debate**. ![Botón de "Iniciar debate"](/assets/images/help/discussions/new-discussion-start-discussion-button.png) ## Aceptar contribuyentes en tus debates -You can welcome your community and introduce a new way to communicate in a repository by creating a welcome post and pinning the post to your {% data variables.product.prodname_discussions %} page. El fijar y bloquear los debates ayuda a que las personas sepan si una publicación se hizo a manera de anuncio. Puedes utilizar los anuncios como una forma de vincular a las personas con más recursos y ofrecerles orientación para abrir debates en tu comunidad. Para obtener más información sobre cómo fijar un debate, consulta la sección "[Administrar los debates en tu repositorio](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#pinning-a-discussion)". +Puedes dar la bienvenida a tu comunidad e introducir una forma nueva de comunicarse en un repositorio si creas una publicación de bienvenida y anclas la publicación a tu página de {% data variables.product.prodname_discussions %}. El fijar y bloquear los debates ayuda a que las personas sepan si una publicación se hizo a manera de anuncio. Puedes utilizar los anuncios como una forma de vincular a las personas con más recursos y ofrecerles orientación para abrir debates en tu comunidad. Para obtener más información sobre cómo fijar un debate, consulta la sección "[Administrar los debates en tu repositorio](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#pinning-a-discussion)". ## Configurar los lineamientos comunitarios para los contribuyentes @@ -39,7 +39,7 @@ Para obtener más información sobre proporcionar lineamientos para tu proyecto, ## Crear un debate nuevo -Any authenticated user who can view a repository can create a discussion. +Cualquier usuario autenticado que pueda ver un repositorio puede crear un debate. {% data reusables.discussions.starting-a-discussion %} diff --git a/translations/es-ES/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/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-education-for-students.md index cf54e3140a..be5c542a68 100644 --- a/translations/es-ES/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/es-ES/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 @@ Usar {% data variables.product.prodname_dotcom %} para tus proyectos escolares e {% data reusables.education.about-github-education-link %} -Cualquiera con una cuenta de {% data variables.product.prodname_dotcom %} puede colaborar en repositorios públicos y privados ilimitados con {% data variables.product.prodname_free_user %}. As a student, you can also apply for GitHub Student benefits, which includes access to GitHub Global Campus, a digital campus for our GitHub student community to take advantage of some of the best programs that GitHub Education has to offer. GitHub Global Campus includes the {% data variables.product.prodname_student_pack %}, which offers free access to tools and services used by professional developers, as well as access to [Campus TV](https://www.twitch.tv/githubeducation) content, student events, GitHub Classroom Assignments, and much more, to help students with their technical career goals. Para obtener más información, consulta las secciones "[Postularse para un paquete de desarrollo para alumnos](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)" y [{% data variables.product.prodname_education %}](https://education.github.com/). +Cualquiera con una cuenta de {% data variables.product.prodname_dotcom %} puede colaborar en repositorios públicos y privados ilimitados con {% data variables.product.prodname_free_user %}. Como alumno, también puedes aplicar para obtener los beneficios de Alumnos de Github, los cuales incluyen acceso al Campus Global de GitHub, un campus digital de nuestra comunidad de alumnos de GitHub para que te beneficies de algunos de los mejores programas que GitHub Education ofrece. El Campus Global de GitHub incluye el {% data variables.product.prodname_student_pack %}, el cual ofrece acceso gratuito a las herramientas y servicios que utilizan los desarrolladores profesionales así como el acceso al contenido de la [TV del Campus](https://www.twitch.tv/githubeducation), los eventos estudiantiles, las Tares de GitHub Classroom y mucho más para ayudar a los alumnos con las metas de sus carreras técnicas. Para obtener más información, consulta las secciones "[Postularse para un paquete de desarrollo para alumnos](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)" y [{% data variables.product.prodname_education %}](https://education.github.com/). Si eres un miembro de un club de robótica FIRST, tu mentor puede solicitar un descuento de educador para que tu equipo pueda colaborar usando {% data variables.product.prodname_team %}, lo que permite repositorios privados y usuarios ilimitados, de forma gratuita. Para obtener más información, consulta la sección "[Postularse para un descuento para educador o investigador](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount)". diff --git a/translations/es-ES/content/education/guides.md b/translations/es-ES/content/education/guides.md index 40f96cccb8..1c096ef070 100644 --- a/translations/es-ES/content/education/guides.md +++ b/translations/es-ES/content/education/guides.md @@ -4,18 +4,20 @@ intro: 'Estas guías de {% data variables.product.prodname_education %} te ayuda allowTitleToDifferFromFilename: true versions: fpt: '*' +shortTitle: Guías --- -### Inicia con {% data variables.product.product_name %} +## Inicia con {% data variables.product.product_name %} Los maestros, alumnos e investigadores pueden utilizar herramientas de {% data variables.product.product_name %} para enriquecer un currículum de desarrollo de software y desarrollar habilidades colaborativas para el mundo real. - [Regístrate para una nueva cuenta de {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-a-new-github-account) - [Guía de inicio rápido de Git y {% data variables.product.prodname_dotcom %} ](/github/getting-started-with-github/quickstart) +- [Acerca de Educación GitHub para estudiantes](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-education-for-students) - [Postularse para un descuento de investigador o educador](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount) - [Aplicar un paquete de desarrollo para alumnos](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack) -### Ejecuta un curso de desarrollo de software con {% data variables.product.company_short %} +## Ejecuta un curso de desarrollo de software con {% data variables.product.company_short %} Administra un aula, asigna y revisa el trabajo de tus alumnos y enseña a la nueva generación de desarrolladores de software con {% data variables.product.prodname_classroom %}. @@ -28,7 +30,7 @@ Administra un aula, asigna y revisa el trabajo de tus alumnos y enseña a la nue - [Deja retroalimentación con solicitudes de cambios](/education/manage-coursework-with-github-classroom/leave-feedback-with-pull-requests) - [Utiliza las calificaciones automáticas](/education/manage-coursework-with-github-classroom/use-autograding) -### Aprende a desarrollar software +## Aprende a desarrollar software Incorpora a {% data variables.product.prodname_dotcom %} en tu educación y utiliza las mismas herramientas que los profesionales. @@ -37,7 +39,7 @@ Incorpora a {% data variables.product.prodname_dotcom %} en tu educación y util - [Prueba {% data variables.product.prodname_desktop %}](/desktop) - [Prueba {% data variables.product.prodname_cli %}](/github/getting-started-with-github/github-cli) -### Contribuye con la comunidad +## Contribuye con la comunidad Participa en la comunidad, obtén capacitación de {% data variables.product.company_short %} y aprende o enseña nuevas habilidades. diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md index 579124feea..cb21885da2 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md @@ -11,7 +11,7 @@ redirect_from: ## Acerca de MakeCode Arcade -MakeCode Arcade es un ambiente de desarrollo integrado (IDE, por sus siglas en inglés) para desarrollar juegos retro de arcade utilizando una programación de arrastre de bloques y JavaScript. Con MakeCode Arcade, los alumnos pueden escribir, editar, ejecutar, probar y depurar código desde un buscador. 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)." +MakeCode Arcade es un ambiente de desarrollo integrado (IDE, por sus siglas en inglés) para desarrollar juegos retro de arcade utilizando una programación de arrastre de bloques y JavaScript. Con MakeCode Arcade, los alumnos pueden escribir, editar, ejecutar, probar y depurar código desde un buscador. 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 reusables.classroom.readme-contains-button-for-online-ide %} 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 3e56b15403..f524164282 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,44 +1,44 @@ --- -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 %}.' +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 %}.' versions: fpt: '*' redirect_from: - /education/manage-coursework-with-github-classroom/about-using-vs-code-with-github-classroom --- -## About Visual Studio Code +## Acerca de Visual Studio Code -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)." +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)". -### Your student's editor of choice -The GitHub Classroom integration with Visual Studio Code provides students with an extension pack which contains: +### 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: -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. +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. -### 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)." +### 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)". -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. +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. {% 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). +**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). {% endnote %} -### How to use GitHub Classroom extension pack -The GitHub Classroom extension has two major components: the 'Classrooms' view and the 'Active Assignment' view. +### 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'. -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. +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. -![GitHub Classroom Active Assignment View](/assets/images/help/classroom/vs-code-active-assignment.png) +![Vista de Tarea Activa de GitHub Classroom](/assets/images/help/classroom/vs-code-active-assignment.png) -The student can push their commits to the latest version of remote, by clicking the **sync changes** button, displayed when hovering over the "Active Assignment" line. This abstracts away source control with Git, allowing instructors to teach Git at their own pace. Synching changes also triggers "Tests" to run if a teacher has configured autograding for their assignment. +El alumno puede subir sus confirmaciones a la última versión del remoto si hace clic en el botón de **sincronizar cambios** que se muestra cuando pasas el puntero del mouse sobre la línea de "Tarea Activa". Esto abstrae el control del código fuente con Git, permitiendo que los instructores enseñen Git a su propio ritmo. El sincronizar los cambios también activa las "Pruebas" para que se ejecuten si un profesor configuró la autocalificación para la tarea. -The "Group" node under "Active Assignment" will show members of a group, if the assignment is a group project. It will also show the admin members of the repository who can help when a student is stuck. To collaborate on the project, a student can start a Live Share session with anyone in the group node, and they will immediately share the entire context of the repository with them. You can learn more about Live Share and collaborating with it [here](https://docs.microsoft.com/en-us/visualstudio/liveshare/). +El nodo de "Grupo" bajo la "Tarea Activa" mostrará a los miembros de un grupo si la tarea es un proyecto grupal. También mostrará a los miembros administrativos del repositorio que pueden ayudar cuando un estudiante se atore. Para colaborar en el proyecto, un alumno puede iniciar una sesión de Live Share con cualquiera en el nodo de grupo y compartirán todo el contexto del repositorio con ellos de inmediato. Puedes aprender más sobre Live Share y cómo colaborar con éste [aquí](https://docs.microsoft.com/en-us/visualstudio/liveshare/). -Once a student is done with the assignment, they can also navigate to see other Assignments and Classrooms. These can be found under the GitHub tab. +Una vez que un alumno termina la tarea, también pueden navegar para ver otras tareas y aulas. Estas se pueden encontrar bajo la pestaña de GitHub. 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 cfac2a07f7..412aba4134 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 @@ -1,7 +1,7 @@ --- title: Integrar a GitHub Classroom con un IDE shortTitle: Integrar con un IDE -intro: 'You can preconfigure a supported integrated development environment (IDE) for assignments you create in {% data variables.product.prodname_classroom %}.' +intro: 'Puedes preconfigurar un ambiente de desarrollo integrado (IDE) compatible para las tareas que crees en {% data variables.product.prodname_classroom %}.' versions: fpt: '*' redirect_from: @@ -10,30 +10,30 @@ redirect_from: - /education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-online-ide --- -## About integration with an IDE +## Acerca de la integración con un IDE {% data reusables.classroom.about-online-ides %} -After a student accepts an assignment with an IDE, the README file in the student's assignment repository will contain a button to open the assignment in the IDE. El alumno puede comenzar a trabajar de inmediato y no se requiere alguna configuración adicional. +Después de que un alumno acepta una tarea con un IDE, el archivo README en su repositorio de tareas contendrá un botón para abrir dicha tarea en el IDE. El alumno puede comenzar a trabajar de inmediato y no se requiere alguna configuración adicional. -## Supported IDEs +## IDE compatibles -{% data variables.product.prodname_classroom %} supports the following IDEs. Puedes aprender más sobre la experiencia del alumno para cada IDE. +{% data variables.product.prodname_classroom %} es compatible con los siguientes IDE. Puedes aprender más sobre la experiencia del alumno para cada IDE. | IDE | Más información | |:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | 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 | [{% data variables.product.prodname_classroom %} extension](http://aka.ms/classroom-vscode-ext) in the Visual Studio Marketplace | +| Visual Studio Code | La [extensión de {% data variables.product.prodname_classroom %}](http://aka.ms/classroom-vscode-ext) en el Mercado de Visual Studio | -We know cloud IDE integrations are important to your classroom and are working to bring more options. +Sabemos que las integraciones con IDE en la nube son importantes para tu aula y estamos trabajando para traerte más opciones. -## Configuring an IDE for an assignment +## Configurar un IDE para una tarea -You can choose the IDE you'd like to use for an assignment when you create an assignment. To learn how to create a new assignment that uses an IDE, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" or "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)." +Puedes elegir el IDE que te gustaría utilizar para una tarea cuando la crees. Para aprender cómo crear una tarea nueva que utilice un IDE, consulta la sección "[Crear una tarea individual](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" o "[Crear una tarea de grupo](/education/manage-coursework-with-github-classroom/create-a-group-assignment)". -## Authorizing the OAuth app for an IDE +## Autorizar la App de OAuth para un IDE -The first time you configure an assignment with an IDE, you must authorize the OAuth app for the IDE for your organization. +La primera vez que configuras una tarea con un IDE, deberás autorizar la App de OAuth para este en tu organización. En todos tus repositorios, otorga acceso de **lectura** a la app para metadatos, administración y código, y acceso de **escritura** para administración y código. Para obtener más información, consulta la sección "[Autorizar las Apps de OAuth](/github/authenticating-to-github/authorizing-oauth-apps)". diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/replit-with-github-classroom.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/replit-with-github-classroom.md index 6ca2cb094d..bd10ab5de9 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/replit-with-github-classroom.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/replit-with-github-classroom.md @@ -1,7 +1,7 @@ --- -title: Repl.it with GitHub Classroom -shortTitle: Repl.it with GitHub Classroom -intro: 'As of July 13 2021, Repl.it integration is no longer available in {% data variables.product.prodname_classroom %}.' +title: Repl.it con GitHub Classroom +shortTitle: Repl.it con GitHub Classroom +intro: 'Desde el 13 de julio de 2021, ya no está disponible la integración con Repl.it en {% data variables.product.prodname_classroom %}.' versions: fpt: '*' redirect_from: @@ -10,19 +10,19 @@ redirect_from: - /education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-replit-with-github-classroom --- -## What’s changing with Repl.it integration +## Qué está cambiando con la integración de Repl.it -As of July 13 2021, Repl.it integration is no longer available. Here’s what’s changed: +Desde el 13 de julio de 2021, ya no está disponible la integración con Repl.it. Aquí te mostramos lo que cambió: -- New private and public repls can no longer be created from within GitHub Classroom. -- Replit Hacker benefits, such as Always On and Boosts, are no longer available for new GitHub Classroom users. +- Los repls privados y públicos nuevos ya no se podrán crear desde dentro de GitHub Classroom. +- Los beneficios de Hacker de Replit, tales como los potenciadores de Siempre Encendido, ya no están disponibles para los usuarios nuevos de GitHub Classroom. -## What does this mean for existing assignments? -Your existing GitHub Classroom repls will remain private forever and you can submit work to GitHub Classroom via these repls until September 30 2021. After September 2021, the Replit icon on the assignment README will no longer work. We suggest you remove the instructions from any README using the integration and let students know that the icon will no longer work. +## ¿Qué significa esto para las tareas existentes? +Tus repls existentes de GitHub Classroom se mantendrán privadas por siempre y podrás emitir trabajo a GitHub Classroom a través de ellas hasta el 30 de septiembre de 2021. Después de septiembre de 2021, el icono de Replit en el README de la tarea ya no funcionará. Te sugerimos eliminar las instrucciones de cualquier README utilizando la integración y comunicar a los alumnos que el icono ya no funcionará. -While you can no longer create private repls from within Classroom, you can continue to create private repls in Replit until September 30th. +Si bien ya no puedes crea repls privados desde dentro de las aulas, puedes seguir creando repls privados en Replit hasta el 30 de septiembre. -We know cloud IDE integrations are important to your classroom and are working hard to bring you more options. +Sabemos que las integraciones con IDE en la nube son importantes para tu aula y estamos trabajando arduamente para traerte más opciones. ## Leer más diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/run-student-code-in-an-ide.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/run-student-code-in-an-ide.md index 665d145c06..1627ee3136 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/run-student-code-in-an-ide.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/run-student-code-in-an-ide.md @@ -1,22 +1,22 @@ --- -title: Run student code in an IDE -intro: You can run the code from a student assignment within the integrated development environment (IDE) that you configured for the assignment. +title: Ejecutar código de alumnos en un IDE +intro: Puedes ejecutar el código desde una tarea de un alumno dentro del ambiente de desarrollo integrado (IDE) que configuraste para la tarea. versions: fpt: '*' redirect_from: - /education/manage-coursework-with-github-classroom/running-student-code - /education/manage-coursework-with-github-classroom/run-student-code-in-an-online-ide - /education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/run-student-code-in-an-online-ide -shortTitle: Run code in IDE +shortTitle: Ejecutar código en un IDE --- -## About student code and IDEs +## Acerca de el código de los alumnos y los IDE -If you configure an integrated development environment (IDE) for an assignment, you can run the code within the IDE. No necesitas clonar el repositorio de la tarea en tu computadora. +Si configuras un ambiente de desarrollo integrado (IDE) para una tarea, puedes ejecutar el código dentro de éste. No necesitas clonar el repositorio de la tarea en tu computadora. -For more information about IDEs, 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)." +Para obtener más información sobre los IDE, 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)". -## Running student code in the IDE +## Ejecutar el código de los alumnos en el IDE {% data reusables.classroom.sign-into-github-classroom %} {% data reusables.classroom.click-classroom-in-list %} diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md index 3cf4630084..7d784aa85a 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md @@ -81,7 +81,7 @@ Si ya creaste una tarea grupal para el aula, puedes reutilizar un conjunto de eq {% data reusables.classroom.assignments-guide-intro-for-environment %} - [Elegir un repositorio de plantilla](#choosing-a-template-repository) -- [Choosing an integrated development environment (IDE)](#choosing-an-integrated-development-environment-ide) +- [Elegir un ambiente de desarrollo integrado (IDE)](#choosing-an-integrated-development-environment-ide) ### Elegir un repositorio de plantilla @@ -89,7 +89,7 @@ Predeterminadamente, una tarea nueva creará un repositorio en blanco para cada {% data reusables.classroom.assignments-guide-choose-template-repository %} -### Choosing an integrated development environment (IDE) +### Elegir un ambiente de desarrollo integrado (IDE) {% data reusables.classroom.about-online-ides %} Para obtener más información, consulta la sección "[Integrar el {% data variables.product.prodname_classroom %} con un IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)". @@ -128,7 +128,7 @@ Puedes ver los equipos que están trabajando o que han emitido una tarea en la p ## Pasos siguientes -- Después de que creas una tarea y de que tus alumnos forme equipos, los miembros de dichos equipos pueden comenzar a trabajar en la tarea utilizando las características de Git y de {% data variables.product.product_name %}. Los alumnos pueden clonar el repositorio, subir confirmaciones, administrar ramas, crear y revisar solicitudes de cambio, tratar los confluctos de fusión y debatir los cambios con propuestas. Tanto tú como el equipo pueden revisar el historial de confirmaciones del repositorio. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Repositories](/repositories)," "[Using Git](/github/getting-started-with-github/using-git)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)," and the free course on [managing merge conflicts](https://lab.github.com/githubtraining/managing-merge-conflicts) from {% data variables.product.prodname_learning %}. +- Después de que creas una tarea y de que tus alumnos forme equipos, los miembros de dichos equipos pueden comenzar a trabajar en la tarea utilizando las características de Git y de {% data variables.product.product_name %}. Los alumnos pueden clonar el repositorio, subir confirmaciones, administrar ramas, crear y revisar solicitudes de cambio, tratar los confluctos de fusión y debatir los cambios con propuestas. Tanto tú como el equipo pueden revisar el historial de confirmaciones del repositorio. Para obtener más información, consulta las secciones "[Iniciar con {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)", "[Repositorios](/repositories)", "[Utilizar git](/github/getting-started-with-github/using-git)" y "[Colaborar con las propuestas y solicitudes de cambio](/github/collaborating-with-issues-and-pull-requests)" y el curso gratuito sobre [cómo administrar los conflictos de fusión](https://lab.github.com/githubtraining/managing-merge-conflicts) de {% data variables.product.prodname_learning %}. - Cuando un equipo termina una tarea, puedes revisar los archivos en el repositorio, o puedes revisar el historial y visualizaciones del mismo para entender mejor cómo colaboró el equipo. Para obtener más información, consulta la sección "[Visualizar los datos del repositorio con gráficas](/github/visualizing-repository-data-with-graphs)". diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md index 02514884ad..064207280c 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md @@ -61,7 +61,7 @@ Debajo de "Tarea individual o grupal", selecciona el menú desplegable y da clic {% data reusables.classroom.assignments-guide-intro-for-environment %} - [Elegir un repositorio de plantilla](#choosing-a-template-repository) -- [Choosing an integrated development environment (IDE)](#choosing-an-integrated-development-environment-ide) +- [Elegir un ambiente de desarrollo integrado (IDE)](#choosing-an-integrated-development-environment-ide) ### Elegir un repositorio de plantilla @@ -71,7 +71,7 @@ Predeterminadamente, una tarea nueva creará un repositorio en blanco para cada {% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %} -### Choosing an integrated development environment (IDE) +### Elegir un ambiente de desarrollo integrado (IDE) {% data reusables.classroom.about-online-ides %} Para obtener más información, consulta la sección "[Integrar el {% data variables.product.prodname_classroom %} con un IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)". @@ -108,7 +108,7 @@ Puedes ver si un alumno se unió al aula y aceptó o emitió una tarea en la pes ## Pasos siguientes -- Después de que creas la tarea, los alumnos pueden comenzar a trabajar en ella utilizando las características de Git y {% data variables.product.product_name %}. Los alumnos pueden clonar el repositorio, subir confirmaciones, administrar ramas, crear y revisar solicitudes de cambio, tratar los confluctos de fusión y debatir los cambios con propuestas. Tanto tú como el alumno pueden revisar el historial de confirmaciones del repositorio. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Repositories](/repositories)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)." +- Después de que creas la tarea, los alumnos pueden comenzar a trabajar en ella utilizando las características de Git y {% data variables.product.product_name %}. Los alumnos pueden clonar el repositorio, subir confirmaciones, administrar ramas, crear y revisar solicitudes de cambio, tratar los confluctos de fusión y debatir los cambios con propuestas. Tanto tú como el alumno pueden revisar el historial de confirmaciones del repositorio. Para obtener más información, consulta las secciones "[Iniciar con {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Repositorios](/repositories)," y "[Colaborar con las propuestas y solicitudes de cambio](/github/collaborating-with-issues-and-pull-requests)". - Cuando un alumno termina una tarea, puedes revisar los archivos en el repositorio, o puedes revisar el historial y las visualizaciones del repositorio para entender mejor su trabajo. Para obtener más información, consulta la sección "[Visualizar los datos del repositorio con gráficas](/github/visualizing-repository-data-with-graphs)". diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md index 9639c89173..685fd98c1a 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md @@ -71,15 +71,15 @@ Puedes agregar, editar o borrar las pruebas de calificación automática para un - Para borrar una prueba, a la derecha del nombre de ésta, da clic en {% octicon "trash" aria-label="The trash icon" %}. ![Icono de cesta de basura para borrar una prueba de calificación automática](/assets/images/help/classroom/autograding-click-trash.png) 1. En la parte inferior de la página, da clic en **Actualizar tarea**. ![Botón de "Actualizar tarea" en la parte inferior de la página](/assets/images/help/classroom/assignments-click-update-assignment.png) -## Viewing and downloading results from autograding tests +## Ver y descargar los resultados de las pruebas de autoevaluación -### Download autograding results +### Descargar los resultados de autoevaluación -You can also download a CSV of your students' autograding scores via the "Download" button. This will generate and download a CSV containing a link to the student's repository, their {% data variables.product.prodname_dotcom %} handle, roster identifier, submission timestamp, and autograding score. +También puedes descargar un CSV de las puntuaciones de autoevaluación de tus alumnos a través del botón "Descargar". Esto generará un CSV de descarga que contiene un enlace al repositorio del alumno, a su manejador de {% data variables.product.prodname_dotcom %}, identificador de lista, marca de tiempo de emisión y puntuación de autoevaluación. -!["Download" button selected showing "Download grades highlighted" and an additional option to "Download repositories"](/assets/images/help/classroom/download-grades.png) +![Botón de "Descargar" seleccionado mostrando "Descargar las calificaciones resaltadas" y una opción adicional para "Descargar repositorios"](/assets/images/help/classroom/download-grades.png) -### View individual logs +### Ver bitácoras individuales {% data reusables.classroom.sign-into-github-classroom %} {% data reusables.classroom.click-classroom-in-list %} {% data reusables.classroom.click-assignment-in-list %} diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md index dbd0b7ad74..4ebe5860b3 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md @@ -8,12 +8,6 @@ redirect_from: shortTitle: Tarea de inicio --- -{% note %} - -**Nota:** La tarea inicilal de Git & {% data variables.product.company_short %} está en beta y también está sujeta a cambios. - -{% endnote %} - La tarea inicial de Git & {% data variables.product.company_short %} es un curso prehecho que resume los puntos básicos de Git y de {% data variables.product.company_short %} y enlaza a los alumnos con recursos para aprender más sobre temas específicos. ## Prerrequisitos diff --git a/translations/es-ES/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md b/translations/es-ES/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md index 715e4a1b2e..ae26c6b4ad 100644 --- a/translations/es-ES/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md +++ b/translations/es-ES/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md @@ -1,6 +1,7 @@ --- title: Encontrar maneras para colaborar con el código abierto en GitHub intro: 'Puedes encontrar maneras de contribuir a los proyectos de código abierto en {% data variables.product.product_name %} que te parezcan relevantes.' +permissions: '{% data reusables.enterprise-accounts.emu-permission-interact %}' redirect_from: - /articles/where-can-i-find-open-source-projects-to-work-on/ - /articles/finding-interesting-projects-on-github/ @@ -19,7 +20,7 @@ shortTitle: Contribuir al código abierto ## Descubrir proyectos relevantes -Si hay un tema en particular que te interese, visita `github.com/topics/`. Por ejemplo, si te interesa el aprendizaje automático, puedes encontrar proyectos relevantes e informes de problemas iniciales si visitas https://github.com/topics/machine-learning. Puedes buscar temas populares si visitas [Temas](https://github.com/topics). También puedes buscar repositorios que empaten con algún tema que te interese. Para obtener más información, consulta "[Buscar repositorios](/articles/searching-for-repositories/#search-by-topic)". +Si hay un tema en particular que te interese, visita `github.com/topics/`. Por ejemplo, si te interesa el aprendizaje automático, puedes encontrar proyectos relevantes e informes de problemas iniciales si visitas https://github.com/topics/machine-learning. Puedes buscar temas populares si visitas [Temas](https://github.com/topics). También puedes buscar repositorios que empaten con algún tema que te interese. Para obtener más información, consulta "[Buscar repositorios](/search-github/searching-on-github/searching-for-repositories#search-by-topic)." Si has tenido actividad en {% data variables.product.product_name %} recientemente, puedes encontrar recomendaciones personalizadas para proyectos e informes de problemas iniciales que se basen en tus contribuciones, estrellas y otras actividades previas en [Explore](https://github.com/explore). También puedes registrarte para el boletín Explore para recibir correos electrónicos sobre las oportunidades disponibles para colaborar con {% data variables.product.product_name %} de acuerdo a tus intereses. Para registrarte, consulta [Boletín Explore por correo](https://github.com/explore/subscribe). 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 bf48ee86f2..baa9caaef8 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 @@ -1,6 +1,7 @@ --- title: Seguir a personas intro: 'Puedes seguir a personas en {% data variables.product.product_name %} para recibir notificaciones acerca de su actividad{% ifversion fpt %} y descubrir proyectos en sus comunidades{% endif %}.' +permissions: '{% data reusables.enterprise-accounts.emu-permission-follow %}' redirect_from: - /articles/following-people - /github/getting-started-with-github/following-people @@ -13,51 +14,51 @@ topics: - Profile --- -## About followers on {% data variables.product.product_name %} +## Aceca de los seguidores en {% data variables.product.product_name %} -When you follow people, you'll see their public activity in the activity view of your news feed.{% ifversion fpt %} If someone you follow stars a public repository, {% data variables.product.product_name %} may recommend the repository to you in the discovery view of your news feed.{% endif %} +Cuando sigues a las personas, verás su actividad pública en la vista de actividad de tus noticias.{% ifversion fpt %} Si alguien que sigues marca un repositorio público como favorito, {% data variables.product.product_name %} podría recomendártelo en la vista de descubrimientos de tus noticias.{% endif %} -You can unfollow someone if you do not wish to see their public activity on {% data variables.product.product_name %}. +Puedes dejar de seguir a alguien si no quieres ver su actividad pública en {% data variables.product.product_name %}. -## Following a user on {% data variables.product.product_name %} +## Seguir a un usuario en {% data variables.product.product_name %} -1. Click a user image to display that user's profile. +1. Haz clic en una imagen de usuario para mostrar el perfil de este. - ![User image](/assets/images/help/profile/user-profile-image.png) + ![Imagen de usuario](/assets/images/help/profile/user-profile-image.png) -2. Click **Follow** under their profile image. +2. Haz clic en **Seguir** debajo de su imagen de perfil. ![Botón Follow user (Seguir usuario)](/assets/images/help/profile/follow-user-button.png) -## Unfollowing a user on {% data variables.product.product_name %} +## Dejar de seguir a un usuario en {% data variables.product.product_name %} -1. Click a user image to display that user's profile. +1. Haz clic en una imagen de usuario para mostrar el perfil de éste. - ![User image](/assets/images/help/profile/user-profile-image.png) + ![Imagen de usuario](/assets/images/help/profile/user-profile-image.png) -2. Click **Unfollow** under their profile image. +2. Haz clic en **Dejar de seguir** debajo de su imagen de perfil. - ![User profile button](/assets/images/help/profile/user-profile-unfollow-button.png) + ![Botón de perfil de usuario](/assets/images/help/profile/user-profile-unfollow-button.png) -## Viewing followed users on {% data variables.product.product_name %} +## Visualizar a los usuarios seguidos en {% data variables.product.product_name %} -1. Click a user image to display that user's profile. +1. Haz clic en una imagen de usuario para mostrar el perfil de éste. - ![User image](/assets/images/help/profile/user-profile-image.png) + ![Imagen de usuario](/assets/images/help/profile/user-profile-image.png) -2. Click **following** under their profile image. +2. Haz clic en **siguiendo** debajo de su imagen de perfil. - ![User following](/assets/images/help/profile/user-profile-following.png) + ![Siguiendo a usuario](/assets/images/help/profile/user-profile-following.png) -## Viewing followers on {% data variables.product.product_name %} +## Visualizar los seguidores en {% data variables.product.product_name %} -1. Click a user image to display that user's profile. +1. Haz clic en una imagen de usuario para mostrar el perfil de éste. - ![User image](/assets/images/help/profile/user-profile-image.png) + ![Imagen de usuario](/assets/images/help/profile/user-profile-image.png) -2. Click **followers** under their profile image. +2. Haz clic en **seguidores** debajo de su imagen de perfil. - ![User following](/assets/images/help/profile/user-profile-followers.png) + ![Usuario siguiendo](/assets/images/help/profile/user-profile-followers.png) 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 951877df97..4608f055d2 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 @@ -61,6 +61,7 @@ shortTitle: Editores de texto asociados ## Usar Atom como editor 1. Instala [Atom](https://atom.io/). Para obtener más información, consulta la sección "[Instalar Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" en la documentación de Atom. +{% data reusables.command_line.open_the_multi_os_terminal %} 3. Escribe este comando: ```shell $ git config --global core.editor "atom --wait" diff --git a/translations/es-ES/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md b/translations/es-ES/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md index 330045381e..5b02b07c87 100644 --- a/translations/es-ES/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md +++ b/translations/es-ES/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md @@ -7,7 +7,7 @@ redirect_from: - /github/using-git/caching-your-github-credentials-in-git - /github/getting-started-with-github/caching-your-github-credentials-in-git - /github/getting-started-with-github/getting-started-with-git/caching-your-github-credentials-in-git -intro: 'If you''re [cloning {% data variables.product.product_name %} repositories using HTTPS](/github/getting-started-with-github/about-remote-repositories), we recommend you use {% data variables.product.prodname_cli %} or Git Credential Manager Core (GCM Core) to remember your credentials.' +intro: 'Si estás [clonando repositorios de {% data variables.product.product_name %} utilizando HTTPS](/github/getting-started-with-github/about-remote-repositories), te recomendamos utilizar el {% data variables.product.prodname_cli %} o el Core de Administración de Credenciales de Git (GCM Core) para recordar tus credenciales.' versions: fpt: '*' ghes: '*' @@ -17,66 +17,66 @@ shortTitle: Guardar credenciales en caché {% tip %} -**Tip:** If you clone {% data variables.product.product_name %} repositories using SSH, then you can authenticate using an SSH key instead of using other credentials. Para obtener información acerca de cómo configurar una conexión SSH, consulta la sección "[Generar una llave SSH](/articles/generating-an-ssh-key)". +**Tip:** Si clonas repositorios de {% data variables.product.product_name %} utilizando SSH, entonces puedes autenticarte utilizando una llave SSH en vez de utilizar otras credenciales. Para obtener información acerca de cómo configurar una conexión SSH, consulta la sección "[Generar una llave SSH](/articles/generating-an-ssh-key)". {% endtip %} ## {% data variables.product.prodname_cli %} -{% data variables.product.prodname_cli %} will automatically store your Git credentials for you when you choose `HTTPS` as your preferred protocol for Git operations and answer "yes" to the prompt asking if you would like to authenticate to Git with your {% data variables.product.product_name %} credentials. +El {% data variables.product.prodname_cli %} almacenará tus credenciales de Git automáticamente cuando elijas `HTTPS` como tu protocolo preferido para las operaciones de Git y respondas "yes" cuando te pregunte si quieres autenticarte en Git con tus credenciales de {% data variables.product.product_name %}. -1. [Install](https://github.com/cli/cli#installation) {% data variables.product.prodname_cli %} on macOS, Windows, or Linux. -2. In the command line, enter `gh auth login`, then follow the prompts. - - When prompted for your preferred protocol for Git operations, select `HTTPS`. - - When asked if you would like to authenticate to Git with your {% data variables.product.product_name %} credentials, enter `Y`. +1. [Instala](https://github.com/cli/cli#installation) el {% data variables.product.prodname_cli %} en macoS, Windows o Linux. +2. En la línea de comandos, ingresa `gh auth login` y luego sigue los mensajes. + - Cuando se te pida tu protocolo preferido para operaciones de Git, selecciona `HTTPS`. + - Cuando se te pregunte si quieres autenticarte en Git con tus credenciales de {% data variables.product.product_name %}, ingresa `Y`. -For more information about authenticating with {% data variables.product.prodname_cli %}, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login). +Para obtener más información sobre cómo autenticarte con el {% data variables.product.prodname_cli %}, consulta la sección [`gh auth login`](https://cli.github.com/manual/gh_auth_login). -## Git Credential Manager Core +## Core de Administración de Credenciales de Git -[Git Credential Manager Core](https://github.com/microsoft/Git-Credential-Manager-Core) (GCM Core) is another way to store your credentials securely and connect to GitHub over HTTPS. With GCM Core, you don't have to manually [create and store a PAT](/github/authenticating-to-github/creating-a-personal-access-token), as GCM Core manages authentication on your behalf, including 2FA (two-factor authentication). +El [Core de Administración de Credenciales de Git](https://github.com/microsoft/Git-Credential-Manager-Core) (GCM Core) es otra forma de almacenar tus credenciales de forma segura y conectarte a GitHub por HTTPS. Con el GCM Core, no necesitas [crear y almacenar un PAT](/github/authenticating-to-github/creating-a-personal-access-token) manualmente, ya que el GCM Core administra la autenticación en tu nombre, incluyendo la 2FA (autenticación bifactorial). {% mac %} -1. Install Git using [Homebrew](https://brew.sh/): +1. Instalar Git utilizando [Homebrew](https://brew.sh/): ```shell $ brew install git ``` -2. Install GCM Core using Homebrew: +2. Instalar el GCM Core utilizando Homebrew: ```shell $ brew tap microsoft/git $ brew install --cask git-credential-manager-core ``` - For MacOS, you don't need to run `git config` because GCM Core automatically configures Git for you. + Para MacOS, no necesitas ejecutar `git config`, ya que el GCM Core configura Git automáticamente para ti. {% data reusables.gcm-core.next-time-you-clone %} -Ya que te hayas autenticado exitosamente, tus credenciales se almacenarán en el llavero de macOS y se utilizarán cada que clones una URL con HTTPS. Git will not require you to type your credentials in the command line again unless you change your credentials. +Ya que te hayas autenticado exitosamente, tus credenciales se almacenarán en el llavero de macOS y se utilizarán cada que clones una URL con HTTPS. Git no requerirá que teclees tus credenciales en la línea de comandos nuevamente a menos de que cambies tus credenciales. {% endmac %} {% windows %} -1. Install Git for Windows, which includes GCM Core. For more information, see "[Git for Windows releases](https://github.com/git-for-windows/git/releases/latest)" from its [releases page](https://github.com/git-for-windows/git/releases/latest). +1. Instala Git para Windows, el cual incluye a GCM Core. Para obtener más información, consulta la sección "[Git para lanzamientos de Windows](https://github.com/git-for-windows/git/releases/latest)" desde su [página de lanzamientos](https://github.com/git-for-windows/git/releases/latest). -We recommend always installing the latest version. At a minimum, install version 2.29 or higher, which is the first version offering OAuth support for GitHub. +Te recomendamos instalar siempre la versión más reciente. Por lo mínimo, instala la versión 2.29 o superior, la cual es la primera versión que ofrece compatibilidad con OAuth para GitHub. {% data reusables.gcm-core.next-time-you-clone %} -Once you've authenticated successfully, your credentials are stored in the Windows credential manager and will be used every time you clone an HTTPS URL. Git will not require you to type your credentials in the command line again unless you change your credentials. +Una vez que te hayas autenticado con éxito, tus credenciales se almacenarán en el administrador de credenciales de Windows y se utilizarán cada que clones una URL de HTTPS. Git no requerirá que teclees tus credenciales en la línea de comandos nuevamente a menos de que cambies tus credenciales.
    {% warning %} -**Warning:** Older versions of Git for Windows came with Git Credential Manager for Windows. This older product is no longer supported and cannot connect to GitHub via OAuth. We recommend you upgrade to [the latest version of Git for Windows](https://github.com/git-for-windows/git/releases/latest). +**Advertencia:** Las versiones más antiguas de Git para Windows vienen con el Administrador de Credenciales de Git para Windows. Este producto más antiguo ya no es compatible y no puede conectarse con GitHub a través de OAuth. Te recomendamos mejorar a [la última versión de Git para Windows](https://github.com/git-for-windows/git/releases/latest). {% endwarning %} {% warning %} -**Warning:** If you cached incorrect or outdated credentials in Credential Manager for Windows, Git will fail to access {% data variables.product.product_name %}. To reset your cached credentials so that Git prompts you to enter your credentials, access the Credential Manager in the Windows Control Panel under User Accounts > Credential Manager. Look for the {% data variables.product.product_name %} entry and delete it. +**Advertencia:** Si guardaste credenciales incorrectas o vencidas en caché en el Administrador de Credenciales para Windows, Git no podrá acceder a {% data variables.product.product_name %}. Para restablecer tus credenciales almacenadas en caché y que Git te pida ingresar tus credenciales, accede al Administrador de Credenciales en el Panel de Control de Windows debajo de Cuentas de usuario > Administrador de Credenciales. Busca la entrada de {% data variables.product.product_name %} y bórrala. {% endwarning %} @@ -84,17 +84,17 @@ Once you've authenticated successfully, your credentials are stored in the Windo {% linux %} -For Linux, install Git and GCM Core, then configure Git to use GCM Core. +Para Linux, instala Git y GCM Core y luego configura Git para utilizar GCM Core. -1. Install Git from your distro's packaging system. Instructions will vary depending on the flavor of Linux you run. +1. Instala Git desde el sistema de empaquetado de tu distribución. Las instrucciones variarán dependiendo del tipo de Linux que tengas. -2. Install GCM Core. See the [instructions in the GCM Core repo](https://github.com/microsoft/Git-Credential-Manager-Core#linux-install-instructions), as they'll vary depending on the flavor of Linux you run. +2. Instala GCM Core. Consulta las [instrucciones en el repositorio de GCM Core](https://github.com/microsoft/Git-Credential-Manager-Core#linux-install-instructions), ya que estas variarán dependiendo del tipo de Linux que ejecutas. -3. Configure Git to use GCM Core. There are several backing stores that you may choose from, so see the GCM Core docs to complete your setup. For more information, see "[GCM Core Linux](https://aka.ms/gcmcore-linuxcredstores)." +3. Configura Git para utilizar GCM Core. Hay varias tiendas de respaldo de entre las que puedes elegir, así que revisa los documentos de GCM Core para completar tu configuración. Para obtener más información, consulta la sección "[GCM Core para Linux](https://aka.ms/gcmcore-linuxcredstores)". {% data reusables.gcm-core.next-time-you-clone %} -Once you've authenticated successfully, your credentials are stored on your system and will be used every time you clone an HTTPS URL. Git will not require you to type your credentials in the command line again unless you change your credentials. +Una vez que te hayas autenticado con éxito, tus credenciales se almacenarán en tu sistema y se utilizarán cada que clones una URL de HTTPS. Git no requerirá que teclees tus credenciales en la línea de comandos nuevamente a menos de que cambies tus credenciales. Para obtener más opciones para almacenar tus credenciales en Linux, consulta la sección [Almacenamiento de credenciales](https://git-scm.com/book/en/v2/Git-Tools-Credential-Storage) en Pro Git. @@ -102,4 +102,4 @@ Para obtener más opciones para almacenar tus credenciales en Linux, consulta la
    -For more information or to report issues with GCM Core, see the official GCM Core docs at "[Git Credential Manager Core](https://github.com/microsoft/Git-Credential-Manager-Core)." +Para obtener más información o para reportar propuestas con GCM Core, consulta los documentos oficiales de GCM Core en "[Core de Administración de Credenciales de Git](https://github.com/microsoft/Git-Credential-Manager-Core)". diff --git a/translations/es-ES/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md b/translations/es-ES/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md index c240628557..c48b421d81 100644 --- a/translations/es-ES/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md +++ b/translations/es-ES/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md @@ -16,7 +16,7 @@ versions: shortTitle: Manejar los extremos de línea --- -## About line endings +## Acerca de los finales de línea Cada vez que presionas Enter en tu teclado, insertas un caracter invisible denominado fin de línea. Esto se maneja de forma diferente en los diferentes sistemas operativos. Cuando colaboras en proyectos con Git y {% data variables.product.product_name %}, Git podría producir resultados inesperados si, por ejemplo, estás trabajando en una máquina Windows y tu colaborador hizo cambios en macOS. diff --git a/translations/es-ES/content/get-started/getting-started-with-git/setting-your-username-in-git.md b/translations/es-ES/content/get-started/getting-started-with-git/setting-your-username-in-git.md index 413e344d2a..305f7cd794 100644 --- a/translations/es-ES/content/get-started/getting-started-with-git/setting-your-username-in-git.md +++ b/translations/es-ES/content/get-started/getting-started-with-git/setting-your-username-in-git.md @@ -13,7 +13,7 @@ versions: shortTitle: Configura tu nombre de usuario --- -## About Git usernames +## Acerca de los nombres de usuario de Git Puedes cambiar el nombre que está asociado con tus confirmaciones de Git utilizando el comando `git config`. El nuevo nombre que configures será visible en cualquier confirmación futura que subas a {% data variables.product.product_name %} desde la línea de comando. Si deseas mantener tu nombre real privado, puedes utilizar cualquier texto como nombre de usuario de Git. Cambiar el nombre asociado con tus confirmaciones de Git utilizando `git config` afectará únicamente a las confirmaciones futuras y no cambiará el nombre utilizado para las confirmaciones anteriores. diff --git a/translations/es-ES/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md b/translations/es-ES/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md index ae43a42256..6476416da8 100644 --- a/translations/es-ES/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md +++ b/translations/es-ES/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md @@ -16,9 +16,9 @@ shortTitle: credenciales de Keychain de macOS {% tip %} -**Note:** Updating credentials from the macOS Keychain only applies to users who manually configured a PAT using the `osxkeychain` helper that is built-in to macOS. +**Nota:** El actualizar las credenciales desde la Keychain de macOS solo aplica a los usuarios que configuran el PAT manualmente utilizando el ayudante `osxkeychain` que está integrado en macOS. -We recommend you either [configure SSH](/articles/generating-an-ssh-key) or upgrade to the [Git Credential Manager Core](/get-started/getting-started-with-git/caching-your-github-credentials-in-git) (GCM Core) instead. GCM Core can manage authentication on your behalf (no more manual PATs) including 2FA (two-factor auth). +Te recomendamos que ya sea [configures el SSH](/articles/generating-an-ssh-key) o mejores al [Core de Administración de Credenciales de Git](/get-started/getting-started-with-git/caching-your-github-credentials-in-git) (GCM Core) en su lugar. El GCM Core puede administrar la autenticación en tu nombre (sin utilizar más PAT manuales) incluyendo la 2FA (autenticación bifactorial). {% endtip %} 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 9c143b3450..eb02d2bb90 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 @@ -18,7 +18,7 @@ shortTitle: GitHub Advanced Security {% data variables.product.prodname_dotcom %} tiene muchas características que te ayudan a mejorar y mantener la calidad de tu código. Algunas de estas se incluyen en todos los planes{% ifversion not ghae %}, tales como la gráfica de dependencias y las {% data variables.product.prodname_dependabot_alerts %}{% endif %}. Otras características de seguridad requieren una licencia para que la {% data variables.product.prodname_GH_advanced_security %} se ejecute en los repositorios independientemente de aquellos públicos en {% data variables.product.prodname_dotcom_the_website %}. -{% ifversion fpt or ghes > 3.0 %}For more information about purchasing {% data variables.product.prodname_GH_advanced_security %}, see "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)."{% elsif ghae %}There is no charge for {% data variables.product.prodname_GH_advanced_security %} on {% data variables.product.prodname_ghe_managed %} during the beta release.{% endif %} +{% ifversion fpt or ghes > 3.0 %}Para obtener más información acerca de cómo comprar la {% data variables.product.prodname_GH_advanced_security %}, consulta la sección "[Acerca de la facturación para {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)". {% elsif ghae %}No hay cargo para la {% data variables.product.prodname_GH_advanced_security %} en {% data variables.product.prodname_ghe_managed %} durante el lanzamiento beta.{% endif %} ## Acerca de las características de {% data variables.product.prodname_advanced_security %} diff --git a/translations/es-ES/content/get-started/learning-about-github/access-permissions-on-github.md b/translations/es-ES/content/get-started/learning-about-github/access-permissions-on-github.md index 8795bf91a7..7eb3139fd3 100644 --- a/translations/es-ES/content/get-started/learning-about-github/access-permissions-on-github.md +++ b/translations/es-ES/content/get-started/learning-about-github/access-permissions-on-github.md @@ -36,6 +36,8 @@ Los miembros de la organización pueden tener roles de *propietario*{% ifversion Los *propietarios de empresa* tienen máximo poder sobre la cuenta de la empresa y pueden tomar medidas en la cuenta de la empresa. Los *gerentes de facturación* pueden administrar los parámetros de facturación de la cuenta de la empresa. Los miembros y colaboradores externos de las organizaciones que son propiedad de tu cuenta empresarial automáticamente son miembros de la cuenta empresarial, si bien no tienen acceso a la cuenta empresarial en sí o a sus parámetros. Para obtener más información, consulta la sección "[Roles en una empresa](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise)". +Si una empresa utiliza {% data variables.product.prodname_emus %}, los miembros se aprovisionan como cuentas de usuario nuevas en {% data variables.product.prodname_dotcom %} y el proveedor de identidad los administra en su totalidad. Los {% data variables.product.prodname_managed_users %} tienen acceso de solo lectura a los repositorios que no son parte de su empresa y no pueden interactuar con los usuarios que tampoco sean miembros de la empresa. Dentro de las organizaciones que pertenecen a la empresa, se puede otorgar los mismos niveles de acceso granular de los {% data variables.product.prodname_managed_users %} que estén disponibles para las organizaciones normales. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)". + {% data reusables.gated-features.enterprise-accounts %} {% endif %} diff --git a/translations/es-ES/content/get-started/learning-about-github/githubs-products.md b/translations/es-ES/content/get-started/learning-about-github/githubs-products.md index a18688fad1..7afe4372ce 100644 --- a/translations/es-ES/content/get-started/learning-about-github/githubs-products.md +++ b/translations/es-ES/content/get-started/learning-about-github/githubs-products.md @@ -78,8 +78,8 @@ Adicionalmente a las características disponibles con {% data variables.product. - Revisores de equipo para solicitudes de extracción - Recordatorios programados {% ifversion fpt %} -- The option to enable {% data variables.product.prodname_github_codespaces %} - - Organization owners can enable {% data variables.product.prodname_github_codespaces %} for the organization by setting a spending limit and granting user permissions for members of their organization. For more information, see "[Enabling Codespaces for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization)." +- La opción para habilitar {% data variables.product.prodname_github_codespaces %} + - Los propietarios de organizaciones pueden habilitar los {% data variables.product.prodname_github_codespaces %} para la organización si configuran un límite de gastos y otorgan permisos de usuario para los miembros de su organziación. Para obtener más información, consulta la sección "[Habilitar los Codespaces para tu organización](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization)". {% endif %} {% data reusables.github-actions.actions-billing %} @@ -102,6 +102,7 @@ Adicionalmente a las características disponibles con {% data variables.product. - 50GB de almacenamiento de {% data variables.product.prodname_registry %} - Control de acceso para los sitios de {% data variables.product.prodname_pages %}. Para obtener más información, consulta la sección "Cambiar la visibilidad de tu sitio de {% data variables.product.prodname_pages %}" - Un acuerdo de nivel de servicio del 99.9% de tiempo activo mensual +- La opción de configurar tu empresa para los {% data variables.product.prodname_emus %}, para que puedas aprovisionar y administrar a los miembros con tu proveedor de identidad y restringir sus contribuciones para que solo se hagan en tu empresa. Para obtener más información, consulta la sección "Acerca de {% data variables.product.prodname_emus %}". - La opción de administrar de forma centralizada las políticas y la facturación de múltiples organizaciones {% data variables.product.prodname_dotcom_the_website %} con una cuenta de empresa. Para obtener más información, consulta la sección "Acerca de las cuentas empresariales." Puedes configurar una prueba para evaluar {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta "Configurar una prueba de {% data variables.product.prodname_ghe_cloud %}". diff --git a/translations/es-ES/content/get-started/learning-about-github/types-of-github-accounts.md b/translations/es-ES/content/get-started/learning-about-github/types-of-github-accounts.md index f2d2000a08..645aee5f1d 100644 --- a/translations/es-ES/content/get-started/learning-about-github/types-of-github-accounts.md +++ b/translations/es-ES/content/get-started/learning-about-github/types-of-github-accounts.md @@ -64,6 +64,14 @@ Toda persona que utilice {% data variables.product.product_location %} tiene su {% endif %} +{% ifversion fpt %} +### {% data variables.product.prodname_emus %} + +Con las {% data variables.product.prodname_emus %}, en vez de utilizar tu cuenta personal, los miembros de una {% data variables.product.prodname_emu_enterprise %} son cuentas aprovisionadas utilizando el proveedor de identidad empresarial (IdP). Los {% data variables.product.prodname_managed_users_caps %} se autentican utilizando su IdP en vez de un nombre de usuario y contraseña de {% data variables.product.prodname_dotcom_the_website %}. + +Los {% data variables.product.prodname_managed_users_caps %} solo pueden interactuar con usuarios, repositorios y organizaciones que son parte de la empresa. Los {% data variables.product.prodname_managed_users_caps %} tienen acceso de solo lectura para el resto del {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)". +{% endif %} + ## Cuentas de organización Las organizaciones son cuentas compartidas donde grupos de personas pueden colaborar en muchos proyectos a la vez. Los propietarios y los administradores pueden administrar el acceso de los miembros a los datos y los proyectos de la organización con características administrativas y de seguridad sofisticadas. diff --git a/translations/es-ES/content/get-started/onboarding/getting-started-with-github-ae.md b/translations/es-ES/content/get-started/onboarding/getting-started-with-github-ae.md index 3d63b37033..6f91c522d6 100644 --- a/translations/es-ES/content/get-started/onboarding/getting-started-with-github-ae.md +++ b/translations/es-ES/content/get-started/onboarding/getting-started-with-github-ae.md @@ -1,80 +1,80 @@ --- -title: Getting started with GitHub AE -intro: 'Get started with setting up and configuring {% data variables.product.product_name %} for {% data variables.product.product_location %}.' +title: Iniciar con GitHub AE +intro: 'Inicia con la configuración y ajustes de {% data variables.product.product_name %} para {% data variables.product.product_location %}.' versions: ghae: '*' --- -This guide will walk you through setting up, configuring, and managing settings for {% data variables.product.product_location %} on {% data variables.product.product_name %} as an enterprise owner. +Esta guía te mostrará cómo configurar, ajustar y administrar la configuración de {% data variables.product.product_location %} en {% data variables.product.product_name %} como propietario de la empresa. -## Part 1: Setting up {% data variables.product.product_name %} -To get started with {% data variables.product.product_name %}, you can create your enterprise account, initialize {% data variables.product.product_name %}, configure an IP allow list, configure user authentication and provisioning, and manage billing for {% data variables.product.product_location %}. +## Parte 1: Configurar {% data variables.product.product_name %} +Para comenzar con {% data variables.product.product_name %}, puedes crear tu propia cuenta empresarial, inicializar {% data variables.product.product_name %}, configurar una lista de IP permitidas, configurar la autenticación y aprovisionamiento de usuarios y administrar la facturación de {% data variables.product.product_location %}. -### 1. Creating your {% data variables.product.product_name %} enterprise account -You will first need to purchase {% data variables.product.product_name %}. For more information, contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact). +### 1. Crear tu cuenta empresarial de {% data variables.product.product_name %} +Primero necesitarás comprar {% data variables.product.product_name %}. Para obtener más información, contacta al [Equipo de ventas de {% data variables.product.prodname_dotcom %}](https://enterprise.github.com/contact). {% data reusables.github-ae.initialize-enterprise %} -### 2. Initializing {% data variables.product.product_name %} -After {% data variables.product.company_short %} creates the owner account for {% data variables.product.product_location %} on {% data variables.product.product_name %}, you will receive an email to sign in and complete the initialization. During initialization, you, as the enterprise owner, will name {% data variables.product.product_location %}, configure SAML SSO, create policies for all organizations in {% data variables.product.product_location %}, and configure a support contact for your enterprise members. Para obtener más información, consulta la sección "[Inicializar {% data variables.product.prodname_ghe_managed %}](/admin/configuration/configuring-your-enterprise/initializing-github-ae)". +### 2. Inicializar {% data variables.product.product_name %} +Después de que {% data variables.product.company_short %} crea la cuenta de propietario para {% data variables.product.product_location %} en {% data variables.product.product_name %}, recibirás un correo electrónico para iniciar sesión y completar la inicialización. Durante la inicialización, tú, como propietario de la empresa, nombrarás la {% data variables.product.product_location %}, configurarás el SSO de SAML y crearás políticas para todas las organizaciones en {% data variables.product.product_location %} y configurarás un contacto de soporte para los miembros de tu empresa. Para obtener más información, consulta la sección "[Inicializar {% data variables.product.prodname_ghe_managed %}](/admin/configuration/configuring-your-enterprise/initializing-github-ae)". ### 3. Restringir el tráfico de red -You can configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account. Para obtener más información, consulta la sección "[Restringir el tráfico de red para tu empresa](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise)". +Puedes configurar una lista de direcciones IP permitidas específicas para restringir el acceso a los activos que pertenecen a las organizaciones en tu cuenta empresarial. Para obtener más información, consulta la sección "[Restringir el tráfico de red para tu empresa](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise)". -### 4. Managing identity and access for {% data variables.product.product_location %} -You can centrally manage access to {% data variables.product.product_location %} on {% data variables.product.product_name %} from an identity provider (IdP) using SAML single sign-on (SSO) for user authentication and System for Cross-domain Identity Management (SCIM) for user provisioning. Once you configure provisioning, you can assign or unassign users to the application from the IdP, creating or disabling user accounts in the enterprise. Para obtener más información, consulta la sección "[Acerca de la administración de accesos e identidades para tu empresa](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)". +### 4. Administrar la identidad y el acceso para {% data variables.product.product_location %} +Puedes administrar el acceso centralmente a {% data variables.product.product_location %} en {% data variables.product.product_name %} desde un proveedor de identidad (IdP) utilizando el inicio de sesión único (SSO) de SAML para la autenticación de usuarios y un Sistema de Administración de Identidad de Dominio Cruzado (SCIM) para el aprovisionamiento de usuarios. Una vez que configures el aprovisionamiento, podrás asignar o desasignar usuarios a la aplicación desde el IdP, creando o inhabilitando cuentas de usuario en la empresa. Para obtener más información, consulta la sección "[Acerca de la administración de accesos e identidades para tu empresa](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)". -### 5. Managing billing for {% data variables.product.product_location %} -Owners of the subscription for {% data variables.product.product_location %} on {% data variables.product.product_name %} can view billing details for {% data variables.product.product_name %} in the Azure portal. For more information, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)." +### 5. Administrar la facturación para {% data variables.product.product_location %} +Los propietarios de la suscripción a {% data variables.product.product_location %} en {% data variables.product.product_name %} pueden ver los detalles de facturación para {% data variables.product.product_name %} en el portal de Azure. Para obtener más información, consulta la sección "[Administrar la facturación para tu empresa](/admin/overview/managing-billing-for-your-enterprise)". -## Part 2: Organizing and managing enterprise members -As an enterprise owner for {% data variables.product.product_name %}, you can manage settings on user, repository, team, and organization levels. You can manage members of {% data variables.product.product_location %}, create and manage organizations, set policies for repository management, and create and manage teams. +## Parte 2: Organizar y administrar a los miembros de la empresa +Como propietario de la empresa para {% data variables.product.product_name %}, puedes administrar los ajustes a nivel de los usuarios, repositorios, equipos y de la organización. Puedes administrar a los miembros de {% data variables.product.product_location %}, crear y administrar organizaciones, configurar políticas para la administración de repositorios y crear y administrar equipos. -### 1. Managing members of {% data variables.product.product_location %} +### 1. Adminsitrar a los miembros de {% data variables.product.product_location %} {% data reusables.getting-started.managing-enterprise-members %} ### 2. Crear organizaciones {% data reusables.getting-started.creating-organizations %} -### 3. Adding members to organizations +### 3. Agregar miembros a las organizaciones {% data reusables.getting-started.adding-members-to-organizations %} ### 4. Crear equipos {% data reusables.getting-started.creating-teams %} -### 5. Setting organization and repository permission levels +### 5. Configurar niveles de permiso de organización y repositorio {% data reusables.getting-started.setting-org-and-repo-permissions %} -### 6. Enforcing repository management policies +### 6. Requerir políticas de administración de repositorios {% data reusables.getting-started.enforcing-repo-management-policies %} -## Part 3: Building securely -To increase the security of {% data variables.product.product_location %}, you can monitor {% data variables.product.product_location %} and configure security and analysis features for your organizations. +## Parte 3: Compilar de forma segura +Para incrementar la seguridad de {% data variables.product.product_location %}, puedes monitorear a {% data variables.product.product_location %} y configurar las características de seguridad y análisis para tus organizaciones. -### 1. Monitoring {% data variables.product.product_location %} -You can monitor {% data variables.product.product_location %} with your activity dashboard and audit logging. For more information, see "[Monitoring activity in your enterprise](/admin/user-management/monitoring-activity-in-your-enterprise)." +### 1. Monitorear a {% data variables.product.product_location %} +Puedes monitorear a {% data variables.product.product_location %} con tu tablero de actividad y registro de bitácoras de auditoría. Para obtener más información, consulta la sección "[Monitorear la actividad en tu empresa](/admin/user-management/monitoring-activity-in-your-enterprise)". -### 2. Configuring security features for your organizations +### 2. Configurar las características de seguridad para tus organizaciones {% data reusables.getting-started.configuring-security-features %} -## Part 4: Customizing and automating work on {% data variables.product.product_location %} -You can customize and automate work in organizations in {% data variables.product.product_location %} with the {% data variables.product.prodname_dotcom %} API, {% data variables.product.prodname_actions %}, and {% data variables.product.prodname_pages %}. +## Parte 4: Personalizar y automatizar el trabajo en {% data variables.product.product_location %} +Puedes personalizar y automatizar el trabajo en las organizaciones en {% data variables.product.product_location %} con la API de {% data variables.product.prodname_dotcom %}, las {% data variables.product.prodname_actions %} y las {% data variables.product.prodname_pages %}. -### 1. Using the {% data variables.product.prodname_dotcom %} API +### 1. Utilizar la API de {% data variables.product.prodname_dotcom %} {% data reusables.getting-started.api %} -### 2. Building {% data variables.product.prodname_actions %} +### 2. Crear {% data variables.product.prodname_actions %} {% data reusables.getting-started.actions %} -For more information on enabling and configuring {% data variables.product.prodname_actions %} for {% data variables.product.product_name %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae)." +Para obtener más información sobre cómo habilitar y configurar las {% data variables.product.prodname_actions %} para {% data variables.product.product_name %}, consulta la sección "[Iniciar con las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae)". ### 3. Uso de {% data variables.product.prodname_pages %} {% data reusables.getting-started.github-pages-enterprise %} -## Part 5: Using {% data variables.product.prodname_dotcom %}'s learning and support resources -Your enterprise members can learn more about Git and {% data variables.product.prodname_dotcom %} with our learning resources, and you can get the support you need with {% data variables.product.prodname_dotcom %} Enterprise Support. +## Parte 5: Utilizar los recursos de apoyo y aprendizaje de {% data variables.product.prodname_dotcom %} +Los miembros de tu empresa pueden aprender más sobre Git y sobre {% data variables.product.prodname_dotcom %} con nuestros recursos para aprender y puedes obtener el apoyo que necesitas con {% data variables.product.prodname_dotcom %} Enterprise Support. -### 1. Learning with {% data variables.product.prodname_learning %} +### 1. Aprender con {% data variables.product.prodname_learning %} {% data reusables.getting-started.learning-lab-enterprise %} -### 2. Working with {% data variables.product.prodname_dotcom %} Enterprise Support +### 2. Trabajar con {% data variables.product.prodname_dotcom %} Enterprise Support {% data reusables.getting-started.contact-support-enterprise %} diff --git a/translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md b/translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md index 950a26ee42..e82780c69d 100644 --- a/translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md +++ b/translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md @@ -1,178 +1,210 @@ --- -title: Getting started with GitHub Enterprise Cloud -intro: 'Get started with setting up and managing your {% data variables.product.prodname_ghe_cloud %} organization or enterprise account.' +title: Iniciar con GitHub Enterprise Cloud +intro: 'Inicia con la configuración y administración de tu cuenta organizacional o empresarial de {% data variables.product.prodname_ghe_cloud %}.' versions: fpt: '*' --- -This guide will walk you through setting up, configuring and managing your {% data variables.product.prodname_ghe_cloud %} account as an organization or enterprise owner. +Esta guía te mostrará cómo configurar, ajustar y administrar tu cuenta de {% data variables.product.prodname_ghe_cloud %} como organización o empresa. {% data reusables.enterprise.ghec-cta-button %} -## Part 1: Choosing your account type +## Parte 1: Elegir tu tipo de cuenta -{% data variables.product.prodname_dotcom %} provides two types of Enterprise products: +{% data variables.product.prodname_dotcom %} proporciona dos tipos de productos empresariales: - **{% data variables.product.prodname_ghe_cloud %}** - **{% data variables.product.prodname_ghe_server %}** -The main difference between the products is that {% data variables.product.prodname_ghe_cloud %} is hosted by {% data variables.product.prodname_dotcom %}, while {% data variables.product.prodname_ghe_server %} is self-hosted. +La diferencia principal entre los productos es que {% data variables.product.prodname_dotcom %} hospeda a {% data variables.product.prodname_ghe_cloud %}, mientras que {% data variables.product.prodname_ghe_server %} es auto-hospedado. -Within the {% data variables.product.prodname_ghe_cloud %} product, there are two different types of account that you can use: +Con {% data variables.product.prodname_ghe_cloud %}, tienes la opción de utilizar {% data variables.product.prodname_emus %}. {% data reusables.enterprise-accounts.emu-short-summary %} -- A single organization account -- An enterprise account that contains multiple organizations +Si en vez de esto eliges permitir a que tus miembros creen y administren sus propias cuentas, hay dos tipos de cuentas que puedes utilizar con {% data variables.product.prodname_ghe_cloud %}: -In either scenario, your users will use their own self-created user account and you'll invite them to join. -### 1. Understanding the differences between an organization account and enterprise account +- Una cuenta de organización simple +- Una cuenta empresarial que contiene varias organizaciones -Both organization and enterprise accounts are available with {% data variables.product.prodname_ghe_cloud %}. An organization is a shared account where groups of people can collaborate across many projects at once, and owners and administrators can manage access to data and projects. An enterprise account enables collaboration between multiple organizations, and allows owners to centrally manage policy, billing and security for these organizations. For more information on the differences, see "[Organizations and enterprise accounts](/organizations/collaborating-with-groups-in-organizations/about-organizations#organizations-and-enterprise-accounts)." +### 1. Entender las diferencias entre una cuenta organizacional y una cuenta empresarial -If you choose an enterprise account, keep in mind that some policies can be set only at an organization level, while others can be enforced for all organizations in an enterprise. +Tanto las cuentas de empresa como las de organización se encuentran disponibles con {% data variables.product.prodname_ghe_cloud %}. Una organización es una cuenta compartida en donde los grupos de personas pueden colaborar a través de varios proyectos a la vez y los propietarios y administradores pueden administrar el acceso a los datos y proyectos. Una cuenta empresarial habilita la colaboración entre organizaciones múltiples y permite a los propietarios administrar políticas centralmente, facturar y proporcionar seguridad a estas organizaciones. Para encontrar más información sobre las diferencias, consulta la sección "[Organizaciones y cuentas empresariales](/organizations/collaborating-with-groups-in-organizations/about-organizations#organizations-and-enterprise-accounts)". -Once you choose the account type you would like, you can proceed to setting up your account. In each of the sections in this guide, proceed to either the single organization or enterprise account section based on your account type. -## Part 2: Setting up your account -To get started with {% data variables.product.prodname_ghe_cloud %}, you will want to create your organization or enterprise account and set up and view billing settings, subscriptions and usage. -### Setting up a single organization account with {% data variables.product.prodname_ghe_cloud %} + +Si eliges una cuenta empresarial, ten en mente que algunas políticas se configuran mejor a nivel organizacional, mientras que otras pueden requerirse para todas las organizaciones en una empresa. + +Una vez que elijas el tipo de cuenta que te gustaría utilizar, puedes proceder a configurarla. En cada sección de esta guía, procede a ya sea la sección de organización simple o de cuenta empresarial de acuerdo con tu tipo de cuenta. + +## Parte 2: Configurar tu cuenta +Para iniciar con {% data variables.product.prodname_ghe_cloud %}, necesitarás crear tu cuenta de organización o de empresa y configurar y ver los ajustes de facturación, suscripciones y uso. +### Configurar una cuenta de organización simple con {% data variables.product.prodname_ghe_cloud %} #### 1. Acerca de las organizaciones -Las organizaciones son cuentas compartidas donde grupos de personas pueden colaborar en muchos proyectos a la vez. With {% data variables.product.prodname_ghe_cloud %}, owners and administrators can manage their organization with sophisticated user authentication and management, as well as escalated support and security options. Para obtener más información, consulta "[Acerca de las organizaciones](/organizations/collaborating-with-groups-in-organizations/about-organizations)". -#### 2. Creating or upgrading an organization account +Las organizaciones son cuentas compartidas donde grupos de personas pueden colaborar en muchos proyectos a la vez. Con {% data variables.product.prodname_ghe_cloud %}, los propietarios y administradores pueden manejar su organización con una administración y autenticación de usuarios sofisticada, así como soporte escalado y opciones de seguridad. Para obtener más información, consulta "[Acerca de las organizaciones](/organizations/collaborating-with-groups-in-organizations/about-organizations)". +#### 2. Crear o mejorar una cuenta organizacional -To use an organization account with {% data variables.product.prodname_ghe_cloud %}, you will first need to create an organization. When prompted to choose a plan, select "Enterprise". Para obtener más información, consulta la sección "[Crear una organización nueva desde cero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)". +Para utilizar una cuenta de organización con {% data variables.product.prodname_ghe_cloud %}, primero necesitarás crear una organización. Cuando se te pida elegir un plan, selecciona "Empresa". Para obtener más información, consulta la sección "[Crear una organización nueva desde cero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)". -Alternatively, if you have an existing organization account that you would like to upgrade, follow the steps in "[Upgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription#upgrading-your-organizations-subscription)." -#### 3. Setting up and managing billing +Como alternativa, si tienes una cuenta organizacional existente que quisieras mejorar, sigue los pasos en "[Mejorar tu suscripción de {% data variables.product.prodname_dotcom %}](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription#upgrading-your-organizations-subscription)". +#### 3. Configurar y administrar la facturación -When you choose to use an organization account with {% data variables.product.prodname_ghe_cloud %}, you'll first have access to a [14-day trial](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud). If you don't purchase {% data variables.product.prodname_enterprise %} or {% data variables.product.prodname_team %} before your trial ends, your organization will be downgraded to {% data variables.product.prodname_free_user %} and lose access to any advanced tooling and features that are only included with paid products. For more information, see "[Finishing your trial](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud#finishing-your-trial)." +Cuando eliges utilizar una cuenta de organización con {% data variables.product.prodname_ghe_cloud %}, primero necesitarás tener acceso a la [prueba gratuita de 14 días](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud). Si no compras {% data variables.product.prodname_enterprise %} o {% data variables.product.prodname_team %} antes de que termine tu periodo de prueba, tu organización bajará de nivel a {% data variables.product.prodname_free_user %} y perderá acceso a cualquier herramienta avanzada y características que solo se incluyan con los productos de pago. Para obtener más información, consulta la sección "[Finalizar tu periodo de prueba](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud#finishing-your-trial)". -Your organization's billing settings page allows you to manage settings like your payment method and billing cycle, view information about your subscription, and upgrade your storage and {% data variables.product.prodname_actions %} minutes. For more information on managing your billing settings, see "[Managing your {% data variables.product.prodname_dotcom %} billing settings](/billing/managing-your-github-billing-settings)." +La página de configuración de facturación de tu organización te permite administrar los ajustes como tu método de pago y ciclo de facturación, ver la información sobre tu suscripción y mejorar tu almacenamiento y minutos de {% data variables.product.prodname_actions %}. Para obtener más información sobre cómo administrar tu configuración de facturación, consulta la sección "[Administrar tu configuración de facturación de {% data variables.product.prodname_dotcom %}](/billing/managing-your-github-billing-settings)". -Only organization members with the *owner* or *billing manager* role can access or change billing settings for your organization. A billing manager is a user who manages the billing settings for your organization and does not use a paid license in your organization's subscription. For more information on adding a billing manager to your organization, see "[Adding a billing manager to your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)." +Solo los miembros de la organización con el rol de *propietario* o *gerente de facturación* pueden acceder o cambiar la configuración de facturación para tu organización. Un gerente de facturación es un usuario que administra la configuración de facturación de tu organización y no utiliza una licencia en la suscripción de tu organización. Para obtener más información sobre cómo agregar a un gerente de facturación a tu organización, consulta la sección "[Agregar a un gerente de facturación a tu organización](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)". -### Setting up an enterprise account with {% data variables.product.prodname_ghe_cloud %} +### Configurar una cuenta empresarial con {% data variables.product.prodname_ghe_cloud %} {% note %} -To get an enterprise account created for you, contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact). +Para obtener una cuenta empresarial que se creó para ti, contacta al [Equipo de ventas de {% data variables.product.prodname_dotcom %}](https://enterprise.github.com/contact). {% endnote %} #### 1. Acerca de las cuentas de empresa -An enterprise account allows you to centrally manage policy and settings for multiple {% data variables.product.prodname_dotcom %} organizations, including member access, billing and usage and security. Para obtener más información, consulta "[Acerca de las cuentas de empresa](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts)". +Una cuenta empresarial te permite administrar las políticas y ajustes centralmente para organizaciones múltiples de {% data variables.product.prodname_dotcom %}, incluyendo el acceso de los miembros, la facturación, el uso y la seguridad. Para obtener más información, consulta "[Acerca de las cuentas de empresa](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts)". #### 2. Agregar organizaciones en tu cuenta de empresa -Puedes crear nuevas organizaciones para administrar dentro de tu cuenta de empresa. For more information, see "[Adding organizations to your enterprise](/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account)." +Puedes crear nuevas organizaciones para administrar dentro de tu cuenta de empresa. Para obtener más información, consulta la sección "[Agregar organizaciones a tu empresa](/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account)". -Contact your {% data variables.product.prodname_dotcom %} sales account representative if you want to transfer an existing organization to your enterprise account. +Contacta a tu representante de cuenta de ventas de {% data variables.product.prodname_dotcom %} su quieres transferir una organización existente a tu cuenta empresarial. #### 3. Ver la suscripción y el uso de tu cuenta de empresa -You can view your current subscription, license usage, invoices, payment history, and other billing information for your enterprise account at any time. Both enterprise owners and billing managers can access and manage billing settings for enterprise accounts. Para obtener más información, consulta "[Ver la suscripción y el uso de tu cuenta de empresa](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/viewing-the-subscription-and-usage-for-your-enterprise-account)". +Puedes ver tu suscripción actual, uso de licencia, facturas, historial de pagos y otra información de facturación de tu cuenta empresarial en cualquier momento. Tanto los propietarios de empresas como los gerentes de facturación pueden acceder y administrar la configuración de facturación para las cuentas empresariales. Para obtener más información, consulta "[Ver la suscripción y el uso de tu cuenta de empresa](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/viewing-the-subscription-and-usage-for-your-enterprise-account)". -## Part 3: Managing your organization or enterprise members and teams with {% data variables.product.prodname_ghe_cloud %} +## Parte 3: Administrar los equipos y miembros de tu organización o empresa con {% data variables.product.prodname_ghe_cloud %} -### Managing members and teams in your organization -You can set permissions and member roles, create and manage teams, and give people access to repositories in your organization. -#### 1. Managing members of your organization +### Administrar a los miembros y equipos de tu organización +Puedes configurar los permisos y roles de los miembros, crear y administrar equipos y darles a las personas acceso a los repositorios de tu organización. +#### 1. Administrar a los miembros de tu organización {% data reusables.getting-started.managing-org-members %} -#### 2. Organization permissions and roles +#### 2. Permisos y roles de la organización {% data reusables.getting-started.org-permissions-and-roles %} -#### 3. About and creating teams +#### 3. Acerca de y crear equipos {% data reusables.getting-started.about-and-creating-teams %} -#### 4. Managing team settings +#### 4. Administrar la configuración de los equipos {% data reusables.getting-started.managing-team-settings %} -#### 5. Giving people and teams access to repositories, project boards and apps +#### 5. Otorgar acceso a equipos y personas para los repositorios, tableros de proyecto y apps {% data reusables.getting-started.giving-access-to-repositories-projects-apps %} -### Managing members of an enterprise account -Managing members of an enterprise is separate from managing members or teams in an organization. It is important to note that enterprise owners or administrators cannot access organization-level settings or manage members for organizations in their enterprise unless they are made an organization owner. For more information, see the above section, "[Managing members and teams in your organization](#managing-members-and-teams-in-your-organization)." -#### 1. Assigning roles in an enterprise -By default, everyone in an enterprise is a member of the enterprise. There are also administrative roles, including enterprise owner and billing manager, that have different levels of access to enterprise settings and data. Para obtener más información, consulta la sección "[Roles en una empresa](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)". +### Administrar a los miembros de una cuenta empresarial +Administrar a los miembros de una empresa es algo separado de administrar a los miembros o equipos de una organización. Es importante notar que los propietarios o administradores de una empresa no pueden acceder a los ajustes a nivel organizacional ni administrar a los miembros de las organizaciones en su empresa a menos de que se les haga un propietario de organización. Para obtener más información, consulta la sección anterior: "[Administrar los miembros y equipos de tu organización](#managing-members-and-teams-in-your-organization)". + +Si tu empresa utiliza {% data variables.product.prodname_emus %}, tus miembros se administrarán integralmente mediante tu proveedor de identidad. Tanto la adición de miembros, hacer cambios a sus membrecías y asignar roles se administra utilizando tu IdP. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)". + +Si tu empresa no utiliza {% data variables.product.prodname_emus %}, sigue estos pasos. + +#### 1. Asignar roles en una empresa +Predeterminadamente, cualquiera en una empresa es un miembro de ella. También existen roles administrativos, incluyendo el del propietario y gerente de facturación, que tienen niveles diferentes de acceso a los datos y ajustes de una empresa. Para obtener más información, consulta la sección "[Roles en una empresa](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)". #### 2. Invitar a las personas para que administren tu empresa -You can invite people to manage your enterprise as enterprise owners or billing managers, as well as remove those who no longer need access. For more information, see "[Inviting people to manage your enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)." +Puedes invitar a personas para que administren tu empresa como propietarios o gerentes de facturación, así como eliminar a los que ya no necesiten acceso. Para obtener más información, consulta la sección "[Invitar a las personas para que administren tu empresa](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)". -You can also grant enterprise members the ability to manage support tickets in the support portal. Para obtener más información, consulta la sección "[Administrar la titularidad de soporte para tu empresa](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)". +También puedes otorgar a los miembros de la empresa la capacidad para que administren tickets de soporte en el portal de soporte. Para obtener más información, consulta la sección "[Administrar la titularidad de soporte para tu empresa](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)". #### 3. Visualizar a las personas en tu empresa -To audit access to enterprise-owned resources or user license usage, you can view every enterprise administrator, enterprise member, and outside collaborator in your enterprise. You can see the organizations that a member belongs to and the specific repositories that an outside collaborator has access to. Para obtener más información, consulta la sección "[Visualizar a las personas en tu empresa](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/viewing-people-in-your-enterprise)". +Para auditar el acceso a los recursos que pertenecen a la empresa o al uso de licencias de los usuarios, puedes ver a todos los administradores, miembros y colaboradores externos de tu empresa. Puedes ver las organizaciones a las cuales pertenece un miembro y especificar los repositorios a los cuales tiene acceso un colaborador. Para obtener más información, consulta la sección "[Visualizar a las personas en tu empresa](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/viewing-people-in-your-enterprise)". -## Part 4: Managing security with {% data variables.product.prodname_ghe_cloud %} +## Parte 4: Administrar la seguridad con {% data variables.product.prodname_ghe_cloud %} -### Managing security for a single organization -You can help keep your organization secure by requiring two-factor authentication, configuring security features, reviewing your organization's audit log and integrations, and enabling SAML single sign-on and team synchronization. -#### 1. Requiring two-factor authentication +* [Administrar la seguridad para una sola organización](#managing-security-for-a-single-organization) +* [Administrar la seguridad para una {% data variables.product.prodname_emu_enterprise %}](#managing-security-for-an-enterprise-with-managed-users) +* [Administrar la seguridad para una cuenta empresarial sin {% data variables.product.prodname_managed_users %}](#managing-security-for-an-enterprise-account-without-managed-users) + +### Administrar la seguridad para una sola organización +Puedes ayudar a que tu organización se mantenga protegida requiriendo autenticación bifactorial, configurando las características de seguridad, revisando las bitácoras de auditoría e integraciones de tu organización y habilitando el inicio de sesión único de SAML y la sincronización de equipos. +#### 1. Requerir autenticación bifactorial {% data reusables.getting-started.requiring-2fa %} -#### 2. Configuring security features for your organization +#### 2. Configurar las características de seguridad de tu organización {% data reusables.getting-started.configuring-security-features %} -#### 3. Reviewing your organization's audit log and integrations +#### 3. Revisar las bitácoras de auditoría e integraciones de tu organización {% data reusables.getting-started.reviewing-org-audit-log-and-integrations %} -#### 4. Enabling and enforcing SAML single sign-on for your organization -If you manage your applications and the identities of your organization members with an identity provider (IdP), you can configure SAML single-sign-on (SSO) to control and secure access to organization resources like repositories, issues and pull requests. When members of your organization access organization resources that use SAML SSO, {% data variables.product.prodname_dotcom %} will redirect them to your IdP to authenticate. 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)." +#### 4. Habilitar y requerir el inicio de sesión único de SAML en tu organización +Si administras tus aplicaciones y las identidades de tus miembros de la organización con un proveedor de identidad (IdP), puedes configurar el inicio de sesión único (SSO) de SAML para controlar y proteger el acceso a los recursos organizacionales como los repositorios, propuestas y solicitudes de cambio. Cuando los miembros de tu organización acceden a los recursos de la misma que utilicen el SSO de SAML, {% data variables.product.prodname_dotcom %} los redireccionará a tu IdP para autenticarse. Para obtener más información, consulta la sección "[Acerca de la administración de identidad y accesos con el inicio de sesión único de SAML](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)". -Organization owners can choose to disable, enable but not enforce, or enable and enforce SAML SSO. For more information, see "[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)" and "[Enforcing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)." +Los propietarios de la organización pueden elegir inhabilitar, habilitar pero no requerir o habilitar y requerir el SSO de SAML. Para obtener más información, consulta las secciones "[Habilitar y probar el inicio de sesión único de SAML para tu organización](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)" y "[Requerir el inicio de sesión único de SAML para tu organización](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)". #### 5. Administrar la sincronización de equipos para tu organización -Organization owners can enable team synchronization between your identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organization owners and team maintainers to connect teams in your organization with IdP groups. Para obtener más información, consulta la sección [Administrar la sincronización de equipos para tu organización](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)". +Los propietarios de la organización pueden habilitar la sincronización de equipos entre tu proveedor de identidad (IdP) y {% data variables.product.prodname_dotcom %} para permitir que los propietarios organizacionales y mantenedores de equipo conecten equipos en tu organización con los grupos de IdP. Para obtener más información, consulta la sección [Administrar la sincronización de equipos para tu organización](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)". -### Managing security for an enterprise account with multiple organizations -To manage security for your enterprise, you can require two-factor authentication, manage allowed IP addresses, enable SAML single sign-on and team synchronization at an enterprise level, and sign up for and enforce GitHub Advanced Security features. -#### 1. Requiring two-factor authentication and managing allowed IP addresses for organizations in your enterprise account -Los propietarios de empresa pueden requerir que los miembros de la organización, gerentes de facturación y colaboradores externos en todas las organizaciones que sean propiedad de una cuenta de empresa usen autenticación de dos factores para proteger sus cuentas personales. Before doing so, we recommend notifying all who have access to organizations in your enterprise. You can also configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account. +### Administrar la seguridad para una {% data variables.product.prodname_emu_enterprise %} -For more information on enforcing two-factor authentication and allowed IP address lists, see "[Enforcing security settings in your enterprise account](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-security-settings-in-your-enterprise-account#managing-allowed-ip-addresses-for-organizations-in-your-enterprise-account)." -#### 2. Enabling and enforcing SAML single sign-on for organizations in your enterprise account -You can centrally manage access to your enterprise's resources, organization membership and team membership using your IdP and SAM single sign-on (SSO). Enterprise owners can enable SAML SSO across all organizations owned by an enterprise account. For more information, see "[About identity and access management for your enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/about-identity-and-access-management-for-your-enterprise-account)." +Con {% data variables.product.prodname_emus %}, el acceso y la identidad se administran centralmente mediante tu proveedor de identidad. La autenticación bifactorial y otros requisitos de inicio de sesión deben habilitarse y requerirse en tu IdP. -#### 3. Managing team synchronization -You can enable and manage team sychronization between an identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organizations owned by your enterprise account to manage team membership with IdP groups. Para obtener más información, consulta la sección "[Administrar la sincronización de equipos para las organizaciones en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/managing-team-synchronization-for-organizations-in-your-enterprise-account)". +#### 1. Habilitar el inicio de sesión único de SAML y el aprovisionamiento en tu {% data variables.product.prodname_emu_enterprise %} -#### 4. Enforcing policies for Advanced Security features in your enterprise account -If you have a GitHub Advanced Security license for your enterprise account, you can enforce policies to manage {% data variables.product.prodname_dotcom %} Advanced Security features for organizations owned by an enterprise account. For more information, see "[Enforcing policies for Advanced Security in your enterprise account](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-policies-for-advanced-security-in-your-enterprise-account)." +En una {% data variables.product.prodname_emu_enterprise %}, tu proveedor de identidad administra y aprovisiona a todos los miembros. Debes habilitar el SSO de SAML y el aprovisionamiento de SCIM antes de que puedas comenzar a utilizar tu empresa. Para obtener más información sobre cómo configurar el SSO de SAML y el aprovisionamiento para una {% data variables.product.prodname_emu_enterprise %}, consulta la sección "[Configurar el inicio de sesión único de SAML para los Usuarios Administrados de Enterprise](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)". -## Part 5: Managing organization and enterprise level policies and settings +#### 2. Administrar equipos en tu {% data variables.product.prodname_emu_enterprise %} con tu proveedor de identidad -### Managing settings for a single organization -To manage and moderate your organization, you can set organization policies, manage permissions for repository changes, and use organization-level community health files. -#### 1. Managing organization policies +Puedes conectar equipos en tus organizaciones a grupos de seguridad en tu proveedor de identidad, administrar la membrecía de tus equipos y acceder a repositorios mediante tu IdP. Para obtener más información, consulta la sección "[Administrar las membrecías de equipo con los grupos de proveedor de identidades](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)". + +#### 3. Administrar las direcciones IP permitidas para las organizaciones de tu {% data variables.product.prodname_emu_enterprise %} + +Puedes configurar una lista de direcciones permitidas para IP específicas para restringir el acceso a los activos que pertenecen a las organizaciones de tu {% data variables.product.prodname_emu_enterprise %}. Para obtener más información, consulta la sección "[Requerir los parámetros de seguridad en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-security-settings-in-your-enterprise-account#managing-allowed-ip-addresses-for-organizations-in-your-enterprise-account)". + +#### 4. Reforzar las políticas para las características de Seguridad Avanzada en tu {% data variables.product.prodname_emu_enterprise %} +{% data reusables.getting-started.enterprise-advanced-security %} + +### Administrar la seguridad para una cuenta empresarial sin {% data variables.product.prodname_managed_users %} +Para administrar la seguridad de tu empresa, puedes requerir la autenticación bifactorial, administrar las direcciones IP permitidas, habilitar el inicio de sesión único de SAML y la sincronización de equipos a nivel empresaria y darte de alta para y requerir las características de la Seguridad Avanzada de GitHub. + +#### 1. Requerir la autenticación bifactorial y administrar las direcciones IP permitidas para las organizaciones de tu cuenta empresarial +Los propietarios de empresa pueden requerir que los miembros de la organización, gerentes de facturación y colaboradores externos en todas las organizaciones que sean propiedad de una cuenta de empresa usen autenticación de dos factores para proteger sus cuentas personales. Antes de hacerlo, te recomendamos notificar a todos los que tengan acceso a las organizaciones de tu empresa. También puedes configurar una lista de direcciones IP permitidas específicas para restringir el acceso a los activos que pertenecen a las organizaciones en tu cuenta empresarial. + +Para obtener más información sobre cómo requerir autenticación bifactorial y listas de direcciones IP, consulta la sección "[Requerir una configuración de seguridad en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-security-settings-in-your-enterprise-account#managing-allowed-ip-addresses-for-organizations-in-your-enterprise-account)". +#### 2. Habilitar y requerir el inicio de sesión único de SAML para las organizaciones de tu cuenta empresarial +Puedes administrar centralmente el acceso a los recursos de tu empresa, la membrecía organizacional y la de equipo utilizando tu IdP e inicio de sesión único (SSO) de SAML. Los propietarios de empresas pueden habilitar el SSO de SAML a través de todas las organizaciones que pertenezcan a una cuenta empresarial. Para obtener más información, consulta la sección "[Acerca de la administración de identidad y acceso para tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/about-identity-and-access-management-for-your-enterprise-account)". + +#### 3. Administrar la sincronización de equipos +Puedes habilitar y administrar la sincronización de equipos entre un proveedor de identidad (IdP) y {% data variables.product.prodname_dotcom %} para permitir que las organizaciones que pertenezcan a tu cuenta empresarial administren la membrecía de los equipos con grupos de IdP. Para obtener más información, consulta la sección "[Administrar la sincronización de equipos para las organizaciones en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/managing-team-synchronization-for-organizations-in-your-enterprise-account)". + +#### 4. Requerir políticas para las características de seguridad avanzada en tu cuenta empresarial +{% data reusables.getting-started.enterprise-advanced-security %} + +## Parte 5: Administrar políticas y ajustes a nivel de empresa y organización + +### Administrar los ajustes para una sola organización +Para administrar y moderar tu organización, puedes configurar políticas de organización, administrar permisos para los cambios de repositorio y utilizar archivos de salud comunitaria a nivel de las organizaciones. +#### 1. Administrar las políticas organizacionales {% data reusables.getting-started.managing-org-policies %} -#### 2. Managing repository changes +#### 2. Administrar los cambios de repositorio {% data reusables.getting-started.managing-repo-changes %} -#### 3. Using organization-level community health files and moderation tools +#### 3. Utilizar archivos de salud comunitaria y herramientas de moderación a nivel organizacional {% data reusables.getting-started.using-org-community-files-and-moderation-tools %} -### Managing settings for an enterprise account -To manage and moderate your enterprise, you can set policies for organizations within the enterprise, view audit logs, configure webhooks, and restrict email notifications. -#### 1. Managing policies for organizations in your enterprise account +### Administrar los ajustes de una cuenta empresarial +Para administrar y moderar tu empresa, puedes configurar políticas para las organizaciones dentro de la empresa, ver las bitácoras de auditoría, configurar webhooks y restringir las notificaciones por correo electrónico. +#### 1. Administrar políticas para las organizaciones en tu cuenta empresarial -You can choose to enforce a number of policies for all organizations owned by your enterprise, or choose to allow these policies to be set in each organization. Types of policies you can enforce include repository management, project board, and team policies. For more information, see "[Set organization policies](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account)." -#### 2. Viewing audit logs, configuring webhooks, and restricting email notifications for your enterprise -You can view actions from all of the organizations owned by your enterprise account in the enterprise audit log. You can also configure webhooks to receive events from organizations owned by your enterprise account. For more information, see "[Viewing the audit logs for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account)" and "[Configuring webooks for organization events in your enterprise](/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/configuring-webhooks-for-organization-events-in-your-enterprise-account)." +Puedes elegir el requerir varias políticas para todas las organizaciones que pertenezcan a tu empresa o elegir permitir que estas políticas se configuren en cada organización. Los tipos de políticas que puedes requerir incluyen la administración de repositorios, tablero de proyectos y políticas de equipo. Para obtener más información, consulta la sección "[Configurar las políticas organizacionales](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account)". +#### 2. Ver las bitácoras de auditoría, configurar webhooks y restringir las notificaciones de tu empresa +Puedes ver las acciones de todas las organizaciones que pertenezcan a tu cuenta empresarial en la bitácora de auditoría empresarial. También puedes configurar webhooks para recibir eventos de organizaciones que pertenecen a tu cuenta de empresa. Para obtener más información, consulta las secciones "[Visualizar las bitácoras de auditoría para las organizaciones en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account)" y "[Configurar los webhooks para eventos de organizaciones en tu empresa](/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/configuring-webhooks-for-organization-events-in-your-enterprise-account)". -You can also restrict email notifications for your enterprise account so that enterprise members can only use an email address in a verified or approved domain to receive notifications. For more information, see "[Restricting email notifications for your enterprise account](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/restricting-email-notifications-for-your-enterprise-account)." +También puedes restringir las notificaciones por correo electrónico de tu cuenta empresarial para que los miembros de tu empresa solo puedan utilizar una dirección de correo electrónico en un dominio aprobado o verificado para recibir notificaciones. Para obtener más información, consulta la sección "[Restringir las notificaciones por correo electrónico para tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/restricting-email-notifications-for-your-enterprise-account)". -## Part 6: Customizing and automating your organization or enterprise's work on {% data variables.product.prodname_dotcom %} -Members of your organization or enterprise can use tools from the {% data variables.product.prodname_marketplace %}, the {% data variables.product.product_name %} API, and existing {% data variables.product.product_name %} features to customize and automate your work. +## Parte 6: Personalizar y automatizar el trabajo de tu organización o empresa en {% data variables.product.prodname_dotcom %} +Los miembros de tu organización o empresa pueden utilizar herramientas del {% data variables.product.prodname_marketplace %}, la API de {% data variables.product.product_name %} y características existentes de {% data variables.product.product_name %} para personalizar y automatizar tu trabajo. ### 1. Uso de {% data variables.product.prodname_marketplace %} {% data reusables.getting-started.marketplace %} -### 2. Using the {% data variables.product.prodname_dotcom %} API +### 2. Utilizar la API de {% data variables.product.prodname_dotcom %} {% data reusables.getting-started.api %} -### 3. Building {% data variables.product.prodname_actions %} +### 3. Crear {% data variables.product.prodname_actions %} {% data reusables.getting-started.actions %} -### 4. Publishing and managing {% data variables.product.prodname_registry %} +### 4. Publicar y administrar el {% data variables.product.prodname_registry %} {% data reusables.getting-started.packages %} ### 5. Uso de {% data variables.product.prodname_pages %} -{% data variables.product.prodname_pages %} is a static site hosting service that takes HTML, CSS, and JavaScript files straight from a repository and publishes a website. You can manage the publication of {% data variables.product.prodname_pages %} sites at the organization level. 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)" and "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)." -## Part 7: Participating in {% data variables.product.prodname_dotcom %}'s community +{% data variables.product.prodname_pages %} es un servicio de hospedaje de sitios estáticos que toma archivos de HTML, CSS y JavaScript directamente desde un repositorio y publica un sitio web. Puedes administrar la publicación de los sitios de {% data variables.product.prodname_pages %} a nivel organizacional. Para obtener más información, consulta las secciones "[Administrar la publicación de sitios de {% data variables.product.prodname_pages %} en tu organización](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)" y "[Acerca de {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)". +## Parte 7: Participar en la comunidad de {% data variables.product.prodname_dotcom %} -Members of your organization or enterprise can use GitHub's learning and support resources to get the help they need. You can also support the open source community. -### 1. Learning with {% data variables.product.prodname_learning %} -Members of your organization or enterprise can learn new skills by completing fun, realistic projects in your very own GitHub repository with [{% data variables.product.prodname_learning %}](https://lab.github.com/). Each course is a hands-on lesson created by the GitHub community and taught by the friendly Learning Lab bot. +Los miembros de tu organización o empresa pueden utilizar los recursos de apoyo y aprendizaje de GitHub para obtener la ayuda que necesitan. También puedes apoyar a la comunidad de código abierto. +### 1. Aprender con {% data variables.product.prodname_learning %} +Los miembros de tu organización o empresa pueden aprender habilidades nuevas completando proyectos divertidos y realistas en tu propio repositorio de GitHub con [{% data variables.product.prodname_learning %}](https://lab.github.com/). Cada curso es una lección didáctica que creó la comunidad de GitHub y que la enseña el amigable bot del Laboratorio de Aprendizaje. -For more information, see "[Git and {% data variables.product.prodname_dotcom %} learning resources](/github/getting-started-with-github/quickstart/git-and-github-learning-resources)." -### 2. Supporting the open source community +Para obtener más información, consulta la sección "[Recursos de aprendizaje de Git y de {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/quickstart/git-and-github-learning-resources)". +### 2. Apoyar a la comunidad de código abierto {% data reusables.getting-started.sponsors %} ### 3. Comunicarse con {% data variables.contact.github_support %} {% data reusables.getting-started.contact-support %} -{% data variables.product.prodname_ghe_cloud %} allows you to submit priority support requests with a target eight-hour response time. For more information, see "[{% data variables.product.prodname_ghe_cloud %} support](/github/working-with-github-support/github-enterprise-cloud-support)." +{% data variables.product.prodname_ghe_cloud %} te permite emitir solicitudes de soporte prioritario con un tiempo de respuesta de ocho horas. Para obtener más información, consulta la sección "[Soporte de {% data variables.product.prodname_ghe_cloud %}](/github/working-with-github-support/github-enterprise-cloud-support)". diff --git a/translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-server.md b/translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-server.md index a6f9ef069e..c0cdc1ecd6 100644 --- a/translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-server.md +++ b/translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-server.md @@ -1,120 +1,120 @@ --- title: Guía de inicio para GitHub Enterprise Server -intro: 'Get started with setting up and managing {% data variables.product.product_location %}.' +intro: 'Inicia con la configuración y administración de {% data variables.product.product_location %}.' versions: ghes: '*' --- -This guide will walk you through setting up, configuring and managing {% data variables.product.product_location %} as an enterprise administrator. +Esta guía te mostrará cómo configurar, ajustar y administrar {% data variables.product.product_location %} como un administrador de empresas. -{% data variables.product.company_short %} provides two ways to deploy {% data variables.product.prodname_enterprise %}. +{% data variables.product.company_short %} proporciona dos formas para desplegar {% data variables.product.prodname_enterprise %}. - **{% data variables.product.prodname_ghe_cloud %}** - **{% data variables.product.prodname_ghe_server %}** -{% data variables.product.company_short %} hosts {% data variables.product.prodname_ghe_cloud %}. You can deploy and host {% data variables.product.prodname_ghe_server %} in your own datacenter or a supported cloud provider. +{% data variables.product.company_short %} hospeda a {% data variables.product.prodname_ghe_cloud %}. Puedes desplegar y hospedar a {% data variables.product.prodname_ghe_server %} en tu propio centro de datos o en un proveedor de servicios en la nube que sea compatible. -For an overview of how {% data variables.product.product_name %} works, see "[System overview](/admin/overview/system-overview)." +Para ver un resumen de cómo funciona {% data variables.product.product_name %}, consulta la sección "[Resumen del sistema](/admin/overview/system-overview)". ## Parte 1: Instalar {% data variables.product.product_name %} -To get started with {% data variables.product.product_name %}, you will need to create your enterprise account, install the instance, use the Management Console for initial setup, configure your instance, and manage billing. -### 1. Creating your enterprise account -Before you install {% data variables.product.product_name %}, you can create an enterprise account on {% data variables.product.prodname_dotcom_the_website %} by contacting [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact). An enterprise account on {% data variables.product.prodname_dotcom_the_website %} is useful for billing and for shared features with {% data variables.product.prodname_dotcom_the_website %} via {% data variables.product.prodname_github_connect %}. Para obtener más información, consulta "[Acerca de las cuentas de empresa](/admin/overview/about-enterprise-accounts)". +Para iniciar con {% data variables.product.product_name %}, necesitarás crear tu cuenta empresarial, instalar la instancia, utilizar la Consola de Administración para la configuración inicial, configurar tu instancia y administrar la facturación. +### 1. Crear tu cuenta empresarial +Antes de que instales {% data variables.product.product_name %}, puedes crear una cuenta empresarial en {% data variables.product.prodname_dotcom_the_website %} contactando al [Equio de Ventas de {% data variables.product.prodname_dotcom %}](https://enterprise.github.com/contact). Una cuenta empresarial en {% data variables.product.prodname_dotcom_the_website %} es útil para facturar y compartir características con {% data variables.product.prodname_dotcom_the_website %} a través de {% data variables.product.prodname_github_connect %}. Para obtener más información, consulta "[Acerca de las cuentas de empresa](/admin/overview/about-enterprise-accounts)". ### 2. Instalar {% data variables.product.product_name %} -To get started with {% data variables.product.product_name %}, you will need to install the appliance on a virtualization platform of your choice. Para obtener más información, consulta "[Configurar una instancia del {% data variables.product.prodname_ghe_server %}](/admin/installation/setting-up-a-github-enterprise-server-instance)." +Para iniciar con {% data variables.product.product_name %}, necesitarás instalar el aplicativo en una plataforma de virtualización que tú elijas. Para obtener más información, consulta "[Configurar una instancia del {% data variables.product.prodname_ghe_server %}](/admin/installation/setting-up-a-github-enterprise-server-instance)." -### 3. Using the Management Console -You will use the Management Console to walk through the initial setup process when first launching {% data variables.product.product_location %}. You can also use the Management Console to manage instance settings such as the license, domain, authentication, and TLS. For more information, see "[Accessing the management console](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)." +### 3. Utilizar la consola de administración +Utilizarás la consola de administración para recorrer el proceso de configuración inicial cuando lances {% data variables.product.product_location %} por primera vez. También puedes utilizar la consola de administración para administrar los ajustes de instancia tales como la licencia, dominio, autenticación y TLS. Para obtener más información, consulta la sección "[Acceder a la consola de administración](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)". ### 4. Configurar {% data variables.product.product_location %} -In addition to the Management Console, you can use the site admin dashboard and the administrative shell (SSH) to manage {% data variables.product.product_location %}. For example, you can configure applications and rate limits, view reports, use command-line utilities. For more information, see "[Configuring your enterprise](/admin/configuration/configuring-your-enterprise)." +Adicionalmente a la Consola de Administración, puedes utilizar el tablero de administrador de sitio y el shell administrativo (SSH) para administrar {% data variables.product.product_location %}. Por ejemplo, puedes configurar las aplicaciones y límites de tasa, ver reportes y utilizar utilidades de línea de comandos. Para obtener más información, consulta la sección "[Configurar tu empresa](/admin/configuration/configuring-your-enterprise)". -You can use the default network settings used by {% data variables.product.product_name %} via the dynamic host configuration protocol (DHCP), or you can also configure the network settings using the virtual machine console. También puedes configurar un servidor proxy o reglas de firewall. For more information, see "[Configuring network settings](/admin/configuration/configuring-network-settings)." +Puedes utilizar los ajustes de red predeterminados que utiliza {% data variables.product.product_name %} a través del protocolo de configuración de host dinámico (DHCP), o también puedes configurar los ajustes de red utilizando la consola de la máquina virtual. También puedes configurar un servidor proxy o reglas de firewall. Para obtener más información, consulta la sección "[Configurar los ajustes de red](/admin/configuration/configuring-network-settings)". ### 5. Configurar la disponibilidad alta -You can configure {% data variables.product.product_location %} for high availability to minimize the impact of hardware failures and network outages. For more information, see "[Configuring high availability](/admin/enterprise-management/configuring-high-availability)." +Puedes configurar a {% data variables.product.product_location %} para tener disponibilidad alta para minimizar el impacto de los fallos de hardware e interrupciones de red. Para obtener más información, consulta la sección "[Configurar la disponibilidad alta](/admin/enterprise-management/configuring-high-availability)". ### 6. Configurar una instancia de preparación -You can set up a staging instance to test modifications, plan for disaster recovery, and try out updates before applying them to {% data variables.product.product_location %}. Para obtener más información, consulta "[Configurar una instancia de preparación](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)." +También puedes configurar una instancia de pruebas para las modificaciones, planear la recuperación de desastres y probar las actualizaciones antes de aplicarlas a {% data variables.product.product_location %}. Para obtener más información, consulta "[Configurar una instancia de preparación](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)." -### 7. Designating backups and disaster recovery -To protect your production data, you can configure automated backups of {% data variables.product.product_location %} with {% data variables.product.prodname_enterprise_backup_utilities %}. Para obtener más información, consulta "[Configurar copias de seguridad en tu aparato](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)" +### 7. Designar respaldos y recuperación de desastres +Para proteger tus datos de producción, puedes configurar los respaldos automatizados de {% data variables.product.product_location %} con {% data variables.product.prodname_enterprise_backup_utilities %}. Para obtener más información, consulta "[Configurar copias de seguridad en tu aparato](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)" ### 8. Administrar la facturación para tu empresa -Billing for all the organizations and {% data variables.product.product_name %} instances connected to your enterprise account is aggregated into a single bill charge for all of your paid {% data variables.product.prodname_dotcom %}.com services. Enterprise owners and billing managers can access and manage billing settings for enterprise accounts. For more information, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)." +La facturación para todas las organizaciones e instancias de {% data variables.product.product_name %} conectadas a tu cuenta empresarial se agregará en un cargo de facturación único para todos tus servicios de pago de {% data variables.product.prodname_dotcom %}.com. Los propietarios y gerentes de facturación de las empresas pueden acceder y administrar los ajustes de facturación de las cuentas empresariales. Para obtener más información, consulta "[Administrar la facturación para tu empresa](/admin/overview/managing-billing-for-your-enterprise)". -## Part 2: Organizing and managing your team -As an enterprise owner or administrator, you can manage settings on user, repository, team and organization levels. You can manage members of your enterprise, create and manage organizations, set policies for repository management, and create and manage teams. +## Parte 2: Organizar y administrar tu equipo +Como propietario empresarial o administrador, puedes administrar los ajustes a nivel de usuario, repositorio, equipo y organización. Puedes administrar a los miembros de tu empresa, crear y administrar organizaciones, configurar políticas para la administración de repositorios y crear y administrar equipos. -### 1. Managing members of {% data variables.product.product_location %} +### 1. Adminsitrar a los miembros de {% data variables.product.product_location %} {% data reusables.getting-started.managing-enterprise-members %} ### 2. Crear organizaciones {% data reusables.getting-started.creating-organizations %} -### 3. Adding members to organizations +### 3. Agregar miembros a las organizaciones {% data reusables.getting-started.adding-members-to-organizations %} ### 4. Crear equipos {% data reusables.getting-started.creating-teams %} -### 5. Setting organization and repository permission levels +### 5. Configurar niveles de permiso de organización y repositorio {% data reusables.getting-started.setting-org-and-repo-permissions %} -### 6. Enforcing repository management policies +### 6. Requerir políticas de administración de repositorios {% data reusables.getting-started.enforcing-repo-management-policies %} -## Part 3: Building securely -To increase the security of {% data variables.product.product_location %}, you can configure authentication for enterprise members, use tools and audit logging to stay in compliance, configure security and analysis features for your organizations, and optionally enable {% data variables.product.prodname_GH_advanced_security %}. -### 1. Authenticating enterprise members -You can use {% data variables.product.product_name %}'s built-in authentication method, or you can choose between an established authentication provider, such as CAS, LDAP, or SAML, to integrate your existing accounts and centrally manage user access to {% data variables.product.product_location %}. For more information, see "[Authenticating users for {% data variables.product.product_location %}](/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance)." +## Parte 3: Compilar de forma segura +Para aumentar la seguridad de {% data variables.product.product_location %}, puedes configurar la autenticación para los miembros empresariales, utilizar herramientas y registro en bitácoras de auditoría para permanecer en cumplimiento, configurar las características de seguridad y análisis para tus organizaciones y, opcionalmente, habilitar la {% data variables.product.prodname_GH_advanced_security %}. +### 1. Autenticar a los miembros empresariales +Puedes utilizar el método de autenticación integrado en {% data variables.product.product_name %} o puedes elegir entre un proveedor de autenticación establecido, tal como CAS, LDAP o SAML, para integrar tus cuentas existentes y administrar centralmente el acceso de los usuarios a {% data variables.product.product_location %}. Para obtener más información, consulta la sección "[Autenticar usuarios en {% data variables.product.product_location %}](/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance)". -You can also require two-factor authentication for each of your organizations. For more information, see "[Requiring two factor authentication for an organization](/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization)." +También puedes requerir la autenticación bifactorial para cada una de tus organizaciones. Para obtener más información, consulta la sección "[Requerir la autenticación bifactorial en una organización](/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization)". -### 2. Staying in compliance -You can implement required status checks and commit verifications to enforce your organization's compliance standards and automate compliance workflows. You can also use the audit log for your organization to review actions performed by your team. For more information, see "[Enforcing policy with pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks)" and "[Audit logging](/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging)." +### 2. Mantenerse en cumplimiento +Puedes implementar las verificaciones de estado requeridas y confirmar las verificaciones para hacer cumplir los estándares de cumplimiento de tu organización y automatizar los flujos de trabajo de cumplimiento. También puedes utilizar la bitácora de auditoría de tu organización para revisar las acciones que realiza tu equipo. Para obtener más información, consulta las secciones "[Requerir la política con ganchos de pre-recepción](/admin/policies/enforcing-policy-with-pre-receive-hooks)" y "[Generar bitácoras de auditoría](/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging)". {% ifversion ghes > 2.22 %} -### 3. Configuring security features for your organizations +### 3. Configurar las características de seguridad para tus organizaciones {% data reusables.getting-started.configuring-security-features %} {% endif %} {% ifversion ghes %} -### {% ifversion ghes = 2.22 %}3.{% else %}4.{% endif %} Enabling {% data variables.product.prodname_GH_advanced_security %} features -You can upgrade your {% data variables.product.product_name %} license to include {% data variables.product.prodname_GH_advanced_security %}. This provides extra features that help users find and fix security problems in their code, such as code and secret scanning. For more information, see "[{% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)." +### {% ifversion ghes = 2.22 %}3.{% else %}4.{% endif %} Habilitar las características de la {% data variables.product.prodname_GH_advanced_security %} +Puedes mejorar tu licencia de {% data variables.product.product_name %} para que incluya la {% data variables.product.prodname_GH_advanced_security %}. Esto proporciona características adicionales que ayudan a los usuarios a encontrar y arreglar problemas de seguridad en su código, tales como el escaneo de secretos y de código. Para obtener más información, consulta la sección "[{% data variables.product.prodname_GH_advanced_security %} para tu empresa](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)". {% endif %} -## Part 4: Customizing and automating your enterprise's work on {% data variables.product.prodname_dotcom %} -You can customize and automate work in organizations in your enterprise with {% data variables.product.prodname_dotcom %} and {% data variables.product.prodname_oauth_apps %}, {% data variables.product.prodname_dotcom %} API, {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %} , and {% data variables.product.prodname_pages %}. +## Parte 4: Personalizar y automatizar el trabajo de tu empresa en {% data variables.product.prodname_dotcom %} +Puedes personalizar y automatizar el trabajo de las organizaciones en tu empresa con {% data variables.product.prodname_dotcom %} y las {% data variables.product.prodname_oauth_apps %}, la API de {% data variables.product.prodname_dotcom %}, {% data variables.product.prodname_actions %}, el {% data variables.product.prodname_registry %} y las {% data variables.product.prodname_pages %}. -### 1. Building {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %} -You can build integrations with the {% data variables.product.prodname_dotcom %} API, such as {% data variables.product.prodname_github_apps %} or {% data variables.product.prodname_oauth_apps %}, for use in organizations in your enterprise to complement and extend your workflows. Para obtener más información, consulta "[Acerca de las apps](/developers/apps/getting-started-with-apps/about-apps)." -### 2. Using the {% data variables.product.prodname_dotcom %} API +### 1. Crear {% data variables.product.prodname_github_apps %} y {% data variables.product.prodname_oauth_apps %} +Puedes crear integraciones con la API de {% data variables.product.prodname_dotcom %}, tal como las {% data variables.product.prodname_github_apps %} o {% data variables.product.prodname_oauth_apps %}, para utilizarlas en las organizciones de tu empresa para complementar y extender tus flujos de trabajo. Para obtener más información, consulta "[Acerca de las apps](/developers/apps/getting-started-with-apps/about-apps)." +### 2. Utilizar la API de {% data variables.product.prodname_dotcom %} {% data reusables.getting-started.api %} {% ifversion ghes %} -### 3. Building {% data variables.product.prodname_actions %} +### 3. Crear {% data variables.product.prodname_actions %} {% data reusables.getting-started.actions %} -For more information on enabling and configuring {% data variables.product.prodname_actions %} on {% data variables.product.product_name %}, 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)." +Para obtener más información sobre cómo habilitar y configurar las {% data variables.product.prodname_actions %} en {% data variables.product.product_name %}, consulta la sección "[Iniciar con {% data variables.product.prodname_actions %} para {% 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)". -### 4. Publishing and managing {% data variables.product.prodname_registry %} +### 4. Publicar y administrar el {% data variables.product.prodname_registry %} {% data reusables.getting-started.packages %} -For more information on enabling and configuring {% data variables.product.prodname_registry %} for {% data variables.product.product_location %}, see "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." +Para obtener más información sobre cómo habilitar y configurar el {% data variables.product.prodname_registry %} para {% data variables.product.product_location %}, consulta la sección "[Iniciar con el {% data variables.product.prodname_registry %} para tu empresa](/admin/packages/getting-started-with-github-packages-for-your-enterprise)". {% endif %} ### 5. Uso de {% data variables.product.prodname_pages %} {% data reusables.getting-started.github-pages-enterprise %} -## Part 5: Connecting with other {% data variables.product.prodname_dotcom %} resources -You can use {% data variables.product.prodname_github_connect %} to share resources. +## Parte 5: Conectarse con otros recursos de {% data variables.product.prodname_dotcom %} +Puedes utilizar {% data variables.product.prodname_github_connect %} para compartir recursos. -If you are the owner of both a {% data variables.product.product_name %} instance and a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account, you can enable {% data variables.product.prodname_github_connect %}. {% data variables.product.prodname_github_connect %} allows you to share specific workflows and features between {% data variables.product.product_location %} and {% data variables.product.prodname_ghe_cloud %}, such as unified search and contributions. Para obtener más información, consulta "[Conectar {% data variables.product.prodname_ghe_server %} a {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)." +Si eres el propietario tanto de una instancia de {% data variables.product.product_name %} como de cuenta de organización o de empresa de {% data variables.product.prodname_ghe_cloud %}, puedes habilitar {% data variables.product.prodname_github_connect %}. {% data variables.product.prodname_github_connect %} te permite compartir flujos de trabajo y características específicos entre {% data variables.product.product_location %} y {% data variables.product.prodname_ghe_cloud %}, tales como la búsqueda unificada y las contribuciones. Para obtener más información, consulta "[Conectar {% data variables.product.prodname_ghe_server %} a {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)." -## Part 6: Using {% data variables.product.prodname_dotcom %}'s learning and support resources -Your enterprise members can learn more about Git and {% data variables.product.prodname_dotcom %} with our learning resources, and you can get the support you need when setting up and managing {% data variables.product.product_location %} with {% data variables.product.prodname_dotcom %} Enterprise Support. -### 1. Learning with {% data variables.product.prodname_learning %} +## Parte 6: Utilizar los recursos de apoyo y aprendizaje de {% data variables.product.prodname_dotcom %} +Los miembros de tu empresa pueden aprender más sobre Git y sobre {% data variables.product.prodname_dotcom %} con nuestros recursos para aprender y puedes obtener el apoyo que necesitas cuando configures y administres {% data variables.product.product_location %} con {% data variables.product.prodname_dotcom %} Enterprise Support. +### 1. Aprender con {% data variables.product.prodname_learning %} {% data reusables.getting-started.learning-lab-enterprise %} -### 2. Working with {% data variables.product.prodname_dotcom %} Enterprise Support +### 2. Trabajar con {% data variables.product.prodname_dotcom %} Enterprise Support {% data reusables.getting-started.contact-support-enterprise %} diff --git a/translations/es-ES/content/get-started/onboarding/getting-started-with-github-team.md b/translations/es-ES/content/get-started/onboarding/getting-started-with-github-team.md index 34384800e4..1fb0874fb8 100644 --- a/translations/es-ES/content/get-started/onboarding/getting-started-with-github-team.md +++ b/translations/es-ES/content/get-started/onboarding/getting-started-with-github-team.md @@ -1,96 +1,96 @@ --- -title: Getting started with GitHub Team -intro: 'With {% data variables.product.prodname_team %} groups of people can collaborate across many projects at the same time in an organization account.' +title: Iniciar con GitHub Team +intro: 'Con {% data variables.product.prodname_team %}, los grupos de personas pueden colaborar a través de muchos proyectos al mismo tiempo en una cuenta organizacional.' versions: fpt: '*' --- -This guide will walk you through setting up, configuring and managing your {% data variables.product.prodname_team %} account as an organization owner. +Esta guía te mostrará cómo configurar, ajustar y administrar tu cuenta de {% data variables.product.prodname_team %} como propietario de una organización. -## Part 1: Configuring your {% data variables.product.product_name %} account -As the first steps in starting with {% data variables.product.prodname_team %}, you will need to create a user account or log into your existing account on {% data variables.product.prodname_dotcom %}, create an organization, and set up billing. +## Parte 1: Configurar tu cuenta de {% data variables.product.product_name %} +Como primeros pasos en el inicio con {% data variables.product.prodname_team %}, necesitarás crear una cuenta de usuario o iniciar sesión en tu cuenta existente de {% data variables.product.prodname_dotcom %}, crear una organización y configurar la facturación. ### 1. Acerca de las organizaciones -Las organizaciones son cuentas compartidas donde las empresas y los proyectos de código abierto pueden colaborar en muchos proyectos a la vez. Los propietarios y los administradores pueden administrar el acceso de los miembros a los datos y los proyectos de la organización con características administrativas y de seguridad sofisticadas. For more information on the features of organizations, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations#terms-of-service-and-data-protection-for-organizations)." +Las organizaciones son cuentas compartidas donde las empresas y los proyectos de código abierto pueden colaborar en muchos proyectos a la vez. Los propietarios y los administradores pueden administrar el acceso de los miembros a los datos y los proyectos de la organización con características administrativas y de seguridad sofisticadas. Para obtener más información sobre las características de las organizaciones, consulta la sección "[Acerca de las organizaciones](/organizations/collaborating-with-groups-in-organizations/about-organizations#terms-of-service-and-data-protection-for-organizations)". -### 2. Creating an organization and signing up for {% data variables.product.prodname_team %} -Before creating an organization, you will need to create a user account or log in to your existing {% data variables.product.prodname_dotcom %} account. Para obtener más información, consulta "[Registrarse para una nueva cuenta de {% data variables.product.prodname_dotcom %}](/get-started/signing-up-for-github/signing-up-for-a-new-github-account)". +### 2. Crear una organización y registrarse para {% data variables.product.prodname_team %} +Antes de crear una organización, necesitarás crear una cuenta de usuario o ingresar en tu cuenta existente de {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta "[Registrarse para una nueva cuenta de {% data variables.product.prodname_dotcom %}](/get-started/signing-up-for-github/signing-up-for-a-new-github-account)". -Once your user account is set up, you can create an organization and pick a plan. This is where you can choose a {% data variables.product.prodname_team %} subscription for your organization. Para obtener más información, consulta la sección "[Crear una organización nueva desde cero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)". +Una vez que se configure tu cuenta de usuario, puedes crear una organización y elegir un plan. Aquí es donde puedes elegir una suscripción de {% data variables.product.prodname_team %} para tu organización. Para obtener más información, consulta la sección "[Crear una organización nueva desde cero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)". -### 3. Managing billing for an organization -You must manage billing settings, payment method, and paid features and products for each of your personal accounts and organizations separately. You can switch between settings for your different accounts using the context switcher in your settings. Para obtener más información, consulta la opción "[Cambiar los ajustes de tus cuentas diferentes](/billing/managing-your-github-billing-settings/about-billing-on-github#switching-between-settings-for-your-different-accounts)". +### 3. Administrar la facturación de una organización +Debes administrar la configuración de facturación, método de pago y características y productos de pago para cada una de tus cuentas y organizaciones personales. Puedes cambiar entre la configuración de tus diversas cuentas utilizando el alternador de contexto en tu configuración. Para obtener más información, consulta la opción "[Cambiar los ajustes de tus cuentas diferentes](/billing/managing-your-github-billing-settings/about-billing-on-github#switching-between-settings-for-your-different-accounts)". -Your organization's billing settings page allows you to manage settings like your payment method, billing cycle and billing email, or view information such as your subscription, billing date and payment history. You can also view and upgrade your storage and GitHub Actions minutes. For more information on managing your billing settings, see "[Managing your {% data variables.product.prodname_dotcom %} billing settings](/billing/managing-your-github-billing-settings)." +La página de configuración de facturación de tu organización te permite administrar las configuraciones como tu método de pago, ciclo de facturación y correo electrónico de facturación o ver la información tal como tu suscripción, fecha de facturación e historial de pago. También puedes ver y mejorar tu almacenamiento y tus minutos de GitHub Actions. Para obtener más información sobre cómo administrar tu configuración de facturación, consulta la sección "[Administrar tu configuración de facturación de {% data variables.product.prodname_dotcom %}](/billing/managing-your-github-billing-settings)". -Only organization members with the *owner* or *billing manager* role can access or change billing settings for your organization. A billing manager is someone who manages the billing settings for your organization and does not use a paid license in your organization's subscription. For more information on adding a billing manager to your organization, see "[Adding a billing manager to your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)." +Solo los miembros de la organización con el rol de *propietario* o *gerente de facturación* pueden acceder o cambiar la configuración de facturación para tu organización. Un gerente de facturación es alguien que administra la configuración de facturación de tu organización y no utiliza una licencia de pago en la suscripción de tu organización. Para obtener más información sobre cómo agregar a un gerente de facturación a tu organización, consulta la sección "[Agregar a un gerente de facturación a tu organización](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)". -## Part 2: Adding members and setting up teams -After creating your organization, you can invite members and set permissions and roles. You can also create different levels of teams and set customized levels of permissions for your organization's repositories, project boards, and apps. +## Parte 2: Agregar miembros y configurar equipos +Después de crear tu organización, puedes invitar miembros y configurar permisos y roles. También puedes crear niveles diferentes de equipos y configurar niveles personalizados de permisos para los repositorios, tableros de proyecto y apps de tu organización. -### 1. Managing members of your organization +### 1. Administrar a los miembros de tu organización {% data reusables.getting-started.managing-org-members %} -### 2. Organization permissions and roles +### 2. Permisos y roles de la organización {% data reusables.getting-started.org-permissions-and-roles %} -### 3. About and creating teams +### 3. Acerca de y crear equipos {% data reusables.getting-started.about-and-creating-teams %} -### 4. Managing team settings +### 4. Administrar la configuración de los equipos {% data reusables.getting-started.managing-team-settings %} -### 5. Giving people and teams access to repositories, project boards and apps +### 5. Otorgar acceso a equipos y personas para los repositorios, tableros de proyecto y apps {% data reusables.getting-started.giving-access-to-repositories-projects-apps %} -## Part 3: Managing security for your organization -You can help to make your organization more secure by recommending or requiring two-factor authentication for your organization members, configuring security features, and reviewing your organization's audit log and integrations. +## Parte 3: Administrar la seguridad de tu organización +Puedes ayudar a mejorar la seguridad de tu organización si recomiendas o requieres autenticación bifactorial para los miembros de esta, configurando características de seguridad y revisando las bitácoras de auditoría e integraciones de la misma. -### 1. Requiring two-factor authentication +### 1. Requerir autenticación bifactorial {% data reusables.getting-started.requiring-2fa %} -### 2. Configuring security features for your organization +### 2. Configurar las características de seguridad de tu organización {% data reusables.getting-started.configuring-security-features %} -### 3. Reviewing your organization's audit log and integrations +### 3. Revisar las bitácoras de auditoría e integraciones de tu organización {% data reusables.getting-started.reviewing-org-audit-log-and-integrations %} -## Part 4: Setting organization level policies -### 1. Managing organization policies +## Parte 4: Configurar políticas a nivel organizacional +### 1. Administrar las políticas organizacionales {% data reusables.getting-started.managing-org-policies %} -### 2. Managing repository changes +### 2. Administrar los cambios de repositorio {% data reusables.getting-started.managing-repo-changes %} -### 3. Using organization-level community health files and moderation tools +### 3. Utilizar archivos de salud comunitaria y herramientas de moderación a nivel organizacional {% data reusables.getting-started.using-org-community-files-and-moderation-tools %} -## Part 5: Customizing and automating your work on {% data variables.product.product_name %} +## Parte 5: Personalizar y automatizar tu trabajo en {% data variables.product.product_name %} {% data reusables.getting-started.customizing-and-automating %} ### 1. Uso de {% data variables.product.prodname_marketplace %} {% data reusables.getting-started.marketplace %} -### 2. Using the {% data variables.product.prodname_dotcom %} API +### 2. Utilizar la API de {% data variables.product.prodname_dotcom %} {% data reusables.getting-started.api %} -### 3. Building {% data variables.product.prodname_actions %} +### 3. Crear {% data variables.product.prodname_actions %} {% data reusables.getting-started.actions %} -### 4. Publishing and managing {% data variables.product.prodname_registry %} +### 4. Publicar y administrar el {% data variables.product.prodname_registry %} {% data reusables.getting-started.packages %} -## Part 6: Participating in {% data variables.product.prodname_dotcom %}'s community +## Parte 6: Participar en la comunidad de {% data variables.product.prodname_dotcom %} {% data reusables.getting-started.participating-in-community %} -### 1. Contributing to open source projects +### 1. Contribuir con proyectos de código abierto {% data reusables.getting-started.open-source-projects %} -### 2. Interacting with the {% data variables.product.prodname_gcf %} +### 2. Interactuar con el {% data variables.product.prodname_gcf %} {% data reusables.support.ask-and-answer-forum %} -### 3. Learning with {% data variables.product.prodname_learning %} +### 3. Aprender con {% data variables.product.prodname_learning %} {% data reusables.getting-started.learning-lab %} -### 4. Supporting the open source community +### 4. Apoyar a la comunidad de código abierto {% data reusables.getting-started.sponsors %} ### 5. Comunicarse con {% data variables.contact.github_support %} {% data reusables.getting-started.contact-support %} ## Leer más -- "[Getting started with your GitHub account](/get-started/onboarding/getting-started-with-your-github-account)" +- "[Iniciar con tu cuenta de GitHub](/get-started/onboarding/getting-started-with-your-github-account)" 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 eac62cc0ac..a9c7b15392 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 @@ -1,145 +1,145 @@ --- -title: Getting started with your GitHub account -intro: 'With a user account on {% data variables.product.prodname_dotcom %}, you can import or create repositories, collaborate with others, and connect with the {% data variables.product.prodname_dotcom %} community.' +title: Iniciar con tu cuenta de GitHub +intro: 'Con una cuenta de usuario en {% data variables.product.prodname_dotcom %}, puedes importar o crear repositorios, colaborar con otros y conectarte con la comunidad de {% data variables.product.prodname_dotcom %}.' versions: fpt: '*' ghes: '*' ghae: '*' --- -This guide will walk you through setting up your {% data variables.product.prodname_dotcom %} account and getting started with {% data variables.product.prodname_dotcom %}'s features for collaboration and community. +Esta guía te mostrará cómo configurar tu cuenta de {% data variables.product.prodname_dotcom %} y cómo iniciar con las características de colaboración y comunitarias de {% data variables.product.prodname_dotcom %}. -## Part 1: Configuring your {% data variables.product.prodname_dotcom %} account +## Parte 1: Configurar tu cuenta de {% data variables.product.prodname_dotcom %} {% ifversion fpt %} -The first steps in starting with {% data variables.product.product_name %} are to create an account, choose a product that fits your needs best, verify your email, set up two-factor authentication, and view your profile. +Los primeros pasos para iniciar con {% data variables.product.product_name %} son crear una cuenta, elegir un producto que se acople a tus necesidades, verificar tu correo electrónico, configurar la autenticación bifactorial y ver tu perfil. {% elsif ghes %} -The first steps in starting with {% data variables.product.product_name %} are to access your account, set up two-factor authentication, and view your profile. +Los primeros pasos para comenzar con {% data variables.product.product_name %} son acceder a tu cuenta, configurar la autenticación bifactorial y ver tu perfil. {% elsif ghae %} -The first steps in starting with {% data variables.product.product_name %} are to access your account and view your profile. +Los primeros pasos para comenzar con {% data variables.product.product_name %} son acceder a tu cuenta y ver tu perfil. {% endif %} -{% ifversion fpt %}There are several types of accounts on {% data variables.product.prodname_dotcom %}. {% endif %} Every person who uses {% data variables.product.product_name %} has their own user account, which can be part of multiple organizations and teams. Your user account is your identity on {% data variables.product.product_location %} and represents you as an individual. +{% ifversion fpt %}Hay varios tipos de cuentas en {% data variables.product.prodname_dotcom %}. {% endif %} Todo aquél que utilice {% data variables.product.product_name %} tiene su propia cuenta, la cual puede ser parte de varias organizaciones y equipos. Tu cuenta de usuario es tu identidad en {% data variables.product.product_location %} y te representa como individuo. {% ifversion fpt %} ### 1. Crear una cuenta -To sign up for a {% data variables.product.prodname_dotcom %} account, navigate to https://github.com/ and follow the prompts. +Para registrarte para obtener una cuenta de {% data variables.product.prodname_dotcom %}, navega hasta https://github.com/ y sigue las indicaciones. -To keep your {% data variables.product.prodname_dotcom %} account secure you should use a strong and unique password. Para obtener más información, consulta la sección "[Crear una contraseña fuerte](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-strong-password)". +Para mantener tu cuenta de {% data variables.product.prodname_dotcom %} protegida, debes utilizar una contraseña fuerte y única. Para obtener más información, consulta la sección "[Crear una contraseña fuerte](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-strong-password)". -### 2. Choosing your {% data variables.product.prodname_dotcom %} product -You can choose {% data variables.product.prodname_free_user %} or {% data variables.product.prodname_pro %} to get access to different features for your personal account. You can upgrade at any time if you are unsure at first which product you want. +### 2. Elegir tu producto de {% data variables.product.prodname_dotcom %} +Puedes elegir {% data variables.product.prodname_free_user %} o {% data variables.product.prodname_pro %} para obtener acceso a diversas características de tu cuenta personal. Puedes mejorarlas en cualquier momento si no estás seguro de qué producto quieres inicialmente. -For more information on all of {% data variables.product.prodname_dotcom %}'s plans, see "[{% data variables.product.prodname_dotcom %}'s products](/get-started/learning-about-github/githubs-products)." +Para obtener más información sobre todos los planes de {% data variables.product.prodname_dotcom %}, consulta la sección [ productos de {% data variables.product.prodname_dotcom %}](/get-started/learning-about-github/githubs-products)". ### 3. Verificar tu dirección de correo electrónico -To ensure you can use all the features in your {% data variables.product.product_name %} plan, verify your email address after signing up for a new account. Para obtener más información, consulta "[Verificar tu dirección de correo electrónico](/github/getting-started-with-github/signing-up-for-github/verifying-your-email-address)". +Para garantizar que puedes utilizar todas las características en tu plan de {% data variables.product.product_name %}, verifica tu dirección de correo electrónico después de registrarte para obtener una cuenta nueva. Para obtener más información, consulta "[Verificar tu dirección de correo electrónico](/github/getting-started-with-github/signing-up-for-github/verifying-your-email-address)". {% endif %} {% ifversion ghes %} -### 1. Accessing your account -The administrator of your {% data variables.product.product_name %} instance will notify you about how to authenticate and access your account. The process varies depending on the authentication mode they have configured for the instance. +### 1. Acceder a tu cuenta +El administrador de tu instancia de {% data variables.product.product_name %} te notificará sobre cómo autenticarte y acceder a tu cuenta. El proceso varía dependiendo del modo de autenticación que tienen configurado para la instancia. {% endif %} {% ifversion ghae %} -### 1. Accessing your account -You will receive an email notification once your enterprise owner for {% data variables.product.product_name %} has set up your account, allowing you to authenticate with SAML single sign-on (SSO) and access your account. +### 1. Acceder a tu cuenta +Recibirás una notificación de correo electrónico una vez que tu propietario de empresa en {% data variables.product.product_name %} haya configurado tu cuenta, lo cual te permitirá autenticarte con el inicio de sesión único (SSO) de SAML y acceder a tu cuenta. {% endif %} {% ifversion fpt or ghes %} -### {% ifversion fpt %}4.{% else %}2.{% endif %} Configuring two-factor authentication -La autenticación de dos factores, o 2FA, es una capa extra de seguridad que se usa cuando se inicia sesión en sitios web o aplicaciones. We strongly urge you to configure 2FA for the safety of your account. Para obtener más información, consulta "[Acerca de la autenticación de dos factores](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication)". +### {% ifversion fpt %}4.{% else %}2.{% endif %} Configurar la autenticación bifactorial +La autenticación de dos factores, o 2FA, es una capa extra de seguridad que se usa cuando se inicia sesión en sitios web o aplicaciones. Insistimos en que configures la 2FA por seguridad de tu cuenta. Para obtener más información, consulta "[Acerca de la autenticación de dos factores](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication)". {% endif %} -### {% ifversion fpt %}5.{% elsif ghes %}3.{% else %}2.{% endif %} Viewing your {% data variables.product.product_name %} profile and contribution graph -Your {% data variables.product.product_name %} profile tells people the story of your work through the repositories and gists you've pinned, the organization memberships you've chosen to publicize, the contributions you've made, and the projects you've created. For more information, see "[About your profile](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile)" and "[Viewing contributions on your profile](/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile)." +### {% ifversion fpt %}5.{% elsif ghes %}3.{% else %}2.{% endif %} Ver tu perfil de {% data variables.product.product_name %} y gráfica de contribuciones +Tu perfil de {% data variables.product.product_name %} les dice a las personas la historia de tu trabajo a través de los repositorios y gists que hayas fijado, las membrecías que hayas elegido publicitar, las contribuciones que hayas hecho y los proyectos que hayas creado. Para obtener más información, consulta las secciones "[Acerca de tu perfil](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile)" y "[Ver las contribuciones en tu perfil](/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile)". -## Part 2: Using {% data variables.product.product_name %}'s tools and processes -To best use {% data variables.product.product_name %}, you'll need to set up Git. Git es responsable de todo lo relacionado con {% data variables.product.prodname_dotcom %} que suceda de forma local en tu computadora. To effectively collaborate on {% data variables.product.product_name %}, you'll write in issues and pull requests using {% data variables.product.prodname_dotcom %} Flavored Markdown. +## Parte 2: Utilizar las herramientas y procesos de {% data variables.product.product_name %} +Para utilizar {% data variables.product.product_name %} de la mejor forma, necesitarás configurar Git. Git es responsable de todo lo relacionado con {% data variables.product.prodname_dotcom %} que suceda de forma local en tu computadora. Para colaborar de forma efectiva en {% data variables.product.product_name %}, necesitarás escribir en propuestas y solicitudes de cambio utilizando el Lenguaje de Marcado Enriquecido de {% data variables.product.prodname_dotcom %}. -### 1. Learning Git -{% data variables.product.prodname_dotcom %}'s collaborative approach to development depends on publishing commits from your local repository to {% data variables.product.product_name %} for other people to view, fetch, and update using Git. For more information about Git, see the "[Git Handbook](https://guides.github.com/introduction/git-handbook/)" guide. For more information about how Git is used on {% data variables.product.product_name %}, see "[{% data variables.product.prodname_dotcom %} flow](/get-started/quickstart/github-flow)." +### 1. Aprender a usar Git +El enfoque colaborativo de {% data variables.product.prodname_dotcom %} para el desarrollo depende de las confirmaciones de publicación desde tu repositorio local hacia {% data variables.product.product_name %} para que las vean, recuperen y actualicen otras personas utilizando Git. Para obtener más información sobre Git, consulta la guía del "[Manual de Git](https://guides.github.com/introduction/git-handbook/)". Para obtener más información sobre cómo se utiliza Git en {% data variables.product.product_name %}, consulta la sección "[flujo de {% data variables.product.prodname_dotcom %}](/get-started/quickstart/github-flow)". ### 2. Configurar Git -If you plan to use Git locally on your computer, whether through the command line, an IDE or text editor, you will need to install and set up Git. Para obtener más información, consulta "[Configurar Git](/get-started/quickstart/set-up-git)." +Si planeas utilizar Git localmente en tu computadora, ya sea a través de la línea de comandos, de un IDE o de un editor de texto, necesitarás instalar y configurar Git. Para obtener más información, consulta "[Configurar Git](/get-started/quickstart/set-up-git)." -If you prefer to use a visual interface, you can download and use {% data variables.product.prodname_desktop %}. {% data variables.product.prodname_desktop %} comes packaged with Git, so there is no need to install Git separately. Para obtener más información, consulta "[Comenzar con {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)". +Si prefieres utilizar una interfaz virtual, puedes descargar y utilziar {% data variables.product.prodname_desktop %}. {% data variables.product.prodname_desktop %} viene en un paquete con Git, así que no hay necesidad de instalar Git por separado. Para obtener más información, consulta "[Comenzar con {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)". -Once you install Git, you can connect to {% data variables.product.product_name %} repositories from your local computer, whether your own repository or another user's fork. Cuando te conectas a un repositorio {% data variables.product.product_name %} desde Git, deberás autenticarte con {% data variables.product.product_name %} utilizando HTTPS o SSH. Para obtener más información, consulta la sección "[Acerca de los repositorios remotos](/get-started/getting-started-with-git/about-remote-repositories)". +Una vez que instalaste Git, puedes conectarte a los repositorios de {% data variables.product.product_name %} desde tu computadora local, ya sea que se trate de tu propio repositorio o de la bifurcación del de otro usuario. Cuando te conectas a un repositorio {% data variables.product.product_name %} desde Git, deberás autenticarte con {% data variables.product.product_name %} utilizando HTTPS o SSH. Para obtener más información, consulta la sección "[Acerca de los repositorios remotos](/get-started/getting-started-with-git/about-remote-repositories)". -### 3. Choosing how to interact with {% data variables.product.product_name %} -Everyone has their own unique workflow for interacting with {% data variables.product.prodname_dotcom %}; the interfaces and methods you use depend on your preference and what works best for your needs. +### 3. Elegir cómo interactuar con {% data variables.product.product_name %} +Cada quién tiene su propio flujo de trabajo único para interactuar con {% data variables.product.prodname_dotcom %}; las interfaces y métodos que utilices dependen de tu preferencia y de lo que funcione mejor para cubrir tus necesidades. -For more information about how to authenticate to {% data variables.product.product_name %} with each of these methods, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github)." +Para obtener más información sobre cómo autenticarte en {% data variables.product.product_name %} con cada uno de estos métodos, consulta la sección "[Sobre la autenticación en {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github)". -| **Método** | **Descripción** | **Use cases** | -| ----------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| 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 %} 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. 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. | -| 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. | -| {% data variables.product.prodname_dotcom %} 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 {% data variables.product.prodname_dotcom %} 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 %} -To make your communication clear and organized in issues and pull requests, you can use {% data variables.product.prodname_dotcom %} Flavored Markdown for formatting, which combines an easy-to-read, easy-to-write syntax with some custom functionality. Para obtener más información, consulta "[Acerca de la escritura y el formato en {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)." +| **Método** | **Descripción** | **Casos de Uso** | +| ---------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 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. | +| 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 {% data variables.product.prodname_dotcom %} | {% 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 {% data variables.product.prodname_dotcom %} 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 %} +Para que tus comunicaciones sean más claras y organizadas en propuestas y solicitudes de cambios, puedes utilizar el Lenguaje de Marcado Enriquecido de {% data variables.product.prodname_dotcom %} para formatearlas, el cual combina una sintaxis fácil de escribir y de leer con algunas funcionalidades personalizadas. Para obtener más información, consulta "[Acerca de la escritura y el formato en {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)." -You can learn {% data variables.product.prodname_dotcom %} Flavored Markdown with the "[Communicating using Markdown](https://lab.github.com/githubtraining/communicating-using-markdown)" course on {% data variables.product.prodname_learning %}. +Puedes aprender a utilizar el Lenguaje de Marcado Enriquecido de {% data variables.product.prodname_dotcom %} con el curso de [Comunícarse utilizando el Lenguaje de Marcado](https://lab.github.com/githubtraining/communicating-using-markdown)" que hay en {% data variables.product.prodname_learning %}. -### 5. Searching on {% data variables.product.product_name %} -Our integrated search allows you to find what you are looking for among the many repositories, users and lines of code on {% data variables.product.product_name %}. You can search globally across all of {% data variables.product.product_name %} or limit your search to a particular repository or organization. For more information about the types of searches you can do on {% data variables.product.product_name %}, see "[About searching on {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github)." +### 5. Buscar en {% data variables.product.product_name %} +Nuestra búsqueda integrada te permite encontrar lo que estás buscando de entre los muchos repositorios, usuarios y líneas de código que hay en {% data variables.product.product_name %}. Puedes buscar globalmente a través de todo {% data variables.product.product_name %} o limitar tu búsqueda a un repositorio u organización en particular. Para obtener más información sobre los tipos de búsqueda que puedes hacer en {% data variables.product.product_name %}, consulta la sección "[Acerca de buscar en {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github)". -Our search syntax allows you to construct queries using qualifiers to specify what you want to search for. For more information on the search syntax to use in search, see "[Searching on {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/searching-on-github)." +Nuestra sintaxis de búsqueda te permite construir consultas utilizando calificadores para especificar lo que quieres buscar. Para obtener más información sobre la sintaxis de búsqueda a utilizar, consulta la sección "[Buscar en {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/searching-on-github)". -### 6. Managing files on {% data variables.product.product_name %} -With {% data variables.product.product_name %}, you can create, edit, move and delete files in your repository or any repository you have write access to. You can also track the history of changes in a file line by line. For more information, see "[Managing files on {% data variables.product.prodname_dotcom %}](/github/managing-files-in-a-repository/managing-files-on-github)." +### 6. Administrar los archivos en {% data variables.product.product_name %} +Con {% data variables.product.product_name %}, puedes crear, editar, mover y borrar los archivos en tu repositorio o en cualquier repositorio en el que tengas acceso de escritura. También puedes rastrear el historial de cambios en un archivo, línea por línea. Para obtener más información, consulta la sección "[Administrar archivos en {% data variables.product.prodname_dotcom %}](/github/managing-files-in-a-repository/managing-files-on-github)". -## Part 3: Collaborating on {% data variables.product.product_name %} -Any number of people can work together in repositories across {% data variables.product.product_name %}. You can configure settings, create project boards, and manage your notifications to encourage effective collaboration. +## Parte 3: Colaborar en {% data variables.product.product_name %} +Cualquier cantidad de personas pueden trabajar juntas en los repositorios a lo largo de {% data variables.product.product_name %}. Puedes configurar los ajustes, crear tableros de proyecto y administrar tus notificaciones para motivar una colaboración efectiva. -### 1. Working with repositories +### 1. Trabajar con repositorios #### Crear un repositorio -Un repositorio es como una carpeta para tu proyecto. You can have any number of public and private repositories in your user account. Repositories can contain folders and files, images, videos, spreadsheets, and data sets, as well as the revision history for all files in the repository. Para obtener más información, consulta la sección "[Acerca de los repositorios](/github/creating-cloning-and-archiving-repositories/about-repositories)". +Un repositorio es como una carpeta para tu proyecto. Puedes tener cualquier cantidad de repositorios públicos y privados en tu cuenta de usuario. Los repositorios pueden contener archivos y carpetas, imágenes, videos, hojas de cálculo y juegos de datos, así como el historial de revisión de todos los archivos en el repositorio. Para obtener más información, consulta la sección "[Acerca de los repositorios](/github/creating-cloning-and-archiving-repositories/about-repositories)". -When you create a new repository, you should initialize the repository with a README file to let people know about your project. Para obtener más información, consulta la sección "[Crear un nuevo repositorio](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-new-repository)." +Cuando creas un repositorio nuevo, debes inicializarlo con un archivo README para que las personas sepan sobre tu proyecto. Para obtener más información, consulta la sección "[Crear un nuevo repositorio](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-new-repository)." #### Clonar un repositorio -You can clone an existing repository from {% data variables.product.product_name %} to your local computer, making it easier to add or remove files, fix merge conflicts, or make complex commits. Clonar un repositorio extrae una copia integral de todos los datos del mismo que {% data variables.product.prodname_dotcom %} tiene en ese momento, incluyendo todas las versiones para cada archivo y carpeta para el proyecto. Para obtener más información, consulta "[Clonar un repositorio](/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository)". +Puedes clonar un repositorio existente desde {% data variables.product.product_name %} hacia tu computadora local, haciendo que sea más fácil el agregar o eliminar archivos, corregir conflictos de fusión o hacer confirmaciones complejas. Clonar un repositorio extrae una copia integral de todos los datos del mismo que {% data variables.product.prodname_dotcom %} tiene en ese momento, incluyendo todas las versiones para cada archivo y carpeta para el proyecto. Para obtener más información, consulta "[Clonar un repositorio](/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository)". #### Bifurcar un repositorio -A fork is a copy of a repository that you manage, where any changes you make will not affect the original repository unless you submit a pull request to the project owner. Casi siempre las bifurcaciones se usan para proponer cambios al proyecto de otra persona o para usar el proyecto de otra persona como inicio de tu propia idea. Para obtener más información, consulta la sección "[Trabajar con las bifurcaciones](/github/collaborating-with-pull-requests/working-with-forks)". +Una bifurcación es una copia de un repositorio que administres, en donde cualquier cambio que hagas no afectará el repositorio a menos de que emitas una solicitud de cambios del propietario del proyecto. Casi siempre las bifurcaciones se usan para proponer cambios al proyecto de otra persona o para usar el proyecto de otra persona como inicio de tu propia idea. Para obtener más información, consulta la sección "[Trabajar con las bifurcaciones](/github/collaborating-with-pull-requests/working-with-forks)". ### 2. Importar tus proyectos -If you have existing projects you'd like to move over to {% data variables.product.product_name %} you can import projects using the {% data variables.product.prodname_dotcom %} Importer, the command line, or external migration tools. For more information, see "[Importing source code to {% data variables.product.prodname_dotcom %}](/github/importing-your-projects-to-github/importing-source-code-to-github)." +Si tienes proyectos existentes que quisieras mover a {% data variables.product.product_name %}, puedes importarlos utilizando el importador de {% data variables.product.prodname_dotcom %}, la línea de comandos o herramientas de migración externas. Para obtener más información, consulta la sección, "[Importar el código fuente a {% data variables.product.prodname_dotcom %}](/github/importing-your-projects-to-github/importing-source-code-to-github)"- -### 3. Managing collaborators and permissions -Puedes colaborar en tu proyecto con otros usando los tableros de proyecto, las solicitudes de extracción y las propuestas de tu repositorio. You can invite other people to your repository as collaborators from the **Collaborators** tab in the repository settings. 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/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository)". +### 3. Administrar colaboradores y permisos +Puedes colaborar en tu proyecto con otros usando los tableros de proyecto, las solicitudes de extracción y las propuestas de tu repositorio. Puedes invitar a otras personas para que sean colaboradores en tu repositorio desde la pestaña de **Colaboradores** en los ajustes de repositorio. 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/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository)". -You are the owner of any repository you create in your user account and have full control of the repository. Collaborators have write access to your repository, limiting what they have permission to do. Para obtener más información, consulta "[Niveles de permiso para un repositorio de cuenta de usuario](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository)". +Eres el propietario de cualquier repositorio que crees en tu cuenta de usuario y tienes control total sobre este. Los colaboradores tiene acceso de escritura a tu repositorio, lo cual limita sus permisos. Para obtener más información, consulta "[Niveles de permiso para un repositorio de cuenta de usuario](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository)". ### 4. Administrar configuraciones de repositorios -As the owner of a repository you can configure several settings, including the repository's visibility, topics, and social media preview. Para obtener más información, consulta la sección "[Administrar la configuración de los repositorios](/github/administering-a-repository/managing-repository-settings)". +Como propietario de un repositorio, puedes configurar varios ajustes, incluyendo la visibilidad del repositorio, los temas y la vista previa de redes sociales. Para obtener más información, consulta la sección "[Administrar la configuración de los repositorios](/github/administering-a-repository/managing-repository-settings)". ### 5. Configurar tu proyecto para contribuciones saludables {% ifversion fpt %} -To encourage collaborators in your repository, you need a community that encourages people to use, contribute to, and evangelize your project. For more information, see "[Building Welcoming Communities](https://opensource.guide/building-community/)" in the Open Source Guides. +Para motivar a los colaboradores de tu repositorio, necesitarás una comunidad que motive a las personas para usar, contribuir a y evangelizar tu proyecto. Para obtener más información, consulta la sección "[Crear Comunidades Acogedoras](https://opensource.guide/building-community/)" en las Guías de Código Abierto. -By adding files like contributing guidelines, a code of conduct, and a license to your repository you can create an environment where it's easier for collaborators to make meaningful, useful contributions. Para encontrar más información, visita la sección "[ Configurar tu proyecto para tener contribuciones saludables](/communities/setting-up-your-project-for-healthy-contributions)." +Al agregar archivos como lineamientos de contribución, un código de conducta y una licencia para tu repositorio, puedes crear un ambiente en donde sea más fácil para los colaboradores realizar contribuciones significativas y útiles. Para encontrar más información, visita la sección "[ Configurar tu proyecto para tener contribuciones saludables](/communities/setting-up-your-project-for-healthy-contributions)." {% endif %} {% ifversion ghes or ghae %} -By adding files like contributing guidelines, a code of conduct, and support resources to your repository you can create an environment where it's easier for collaborators to make meaningful, useful contributions. Para encontrar más información, visita la sección "[ Configurar tu proyecto para tener contribuciones saludables](/communities/setting-up-your-project-for-healthy-contributions)." +Al agregar archivos como lineamientos de contribución, un código de conducta y tener compatibilidad con los recursos para tu repositorio, puedes crear un ambiente en donde sea más fácil para los colaboradores realizar contribuciones significativas y útiles. Para encontrar más información, visita la sección "[ Configurar tu proyecto para tener contribuciones saludables](/communities/setting-up-your-project-for-healthy-contributions)." {% endif %} -### 6. Using GitHub Issues and project boards -You can use GitHub Issues to organize your work with issues and pull requests and manage your workflow with project boards. For more information, see "[About issues](/issues/tracking-your-work-with-issues/about-issues)" and "[About project boards](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." +### 6. Utilizar las propuestas y tableros de proyecto de GitHub +Puedes utilizar las propuestas de GiHub para organizar tu trabajo con las propuestas y solicitudes de trabajo y administrar tu flujo de trabajo con tableros de proyecto. Para obtener más información, consulta las secciones "[Acerca de las propuestas](/issues/tracking-your-work-with-issues/about-issues)" y [Acerca de los tableros de proyecto](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)". -### 7. Managing notifications -Notifications provide updates about the activity on {% data variables.product.product_name %} you've subscribed to or participated in. Si ya no te interesa alguna conversación, te puedes dar de baja, dejar de seguir o personalizar los tipos de notificaciones que recibirás en el futuro. Para obtener más información, consulta la sección "[Acerca de las notificaciones](/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)". +### 7. Administrar notificaciones +Las notificaciones proporcionan actualizaciones sobre la actividad en {% data variables.product.product_name %} a la cual estás suscrito o en la cual participas. Si ya no te interesa alguna conversación, te puedes dar de baja, dejar de seguir o personalizar los tipos de notificaciones que recibirás en el futuro. Para obtener más información, consulta la sección "[Acerca de las notificaciones](/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)". ### 8. Trabajar con {% data variables.product.prodname_pages %} -You can use {% data variables.product.prodname_pages %} to create and host a website directly from a {% data variables.product.product_name %} repository. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)". +Puedes utilizar {% data variables.product.prodname_pages %} para crear un host y sitio web directamente desde un repositorio de {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)". {% ifversion fpt %} ### 9. Uso de {% data variables.product.prodname_discussions %} -You can enable {% data variables.product.prodname_discussions %} for your repository to help build a community around your project. Maintainers, contributors and visitors can use discussions to share announcements, ask and answer questions, and participate in conversations around goals. Para obtener más información, consulta la sección "[Acerca de los debates](/discussions/collaborating-with-your-community-using-discussions/about-discussions)". +Puedes habilitar los {% data variables.product.prodname_discussions %} en tu repositorio para ayudar a crear una comunidad al rededor de tu proyecto. Los mantenedores, contribuyentes y visitantes pueden utilizar los debates para compartir anuncios, hacer y responder preguntas y participar en conversaciones sobre las metas. Para obtener más información, consulta la sección "[Acerca de los debates](/discussions/collaborating-with-your-community-using-discussions/about-discussions)". {% endif %} -## Part 4: Customizing and automating your work on {% data variables.product.product_name %} +## Parte 4: Personalizar y automatizar tu trabajo en {% data variables.product.product_name %} {% data reusables.getting-started.customizing-and-automating %} @@ -147,47 +147,47 @@ You can enable {% data variables.product.prodname_discussions %} for your reposi ### 1. Uso de {% data variables.product.prodname_marketplace %} {% data reusables.getting-started.marketplace %} {% endif %} -### {% ifversion fpt %}2.{% else %}1.{% endif %} Using the {% data variables.product.prodname_dotcom %} API +### {% ifversion fpt %}2.{% else %}1.{% endif %} Utilizar la API de {% data variables.product.prodname_dotcom %} {% data reusables.getting-started.api %} -### {% ifversion fpt %}3.{% else %}2.{% endif %} Building {% data variables.product.prodname_actions %} +### {% ifversion fpt %}3.{% else %}2.{% endif %} Crear {% data variables.product.prodname_actions %} {% data reusables.getting-started.actions %} -### {% ifversion fpt %}4.{% else %}3.{% endif %} Publishing and managing {% data variables.product.prodname_registry %} +### {% ifversion fpt %}4.{% else %}3.{% endif %} Publicar y administrar el {% data variables.product.prodname_registry %} {% data reusables.getting-started.packages %} {% ifversion fpt or ghae or ghes > 2.22 %} -## Part 5: Building securely on {% data variables.product.product_name %} -{% data variables.product.product_name %} has a variety of security features that help keep code and secrets secure in repositories. Some features are available for all repositories, while others are only available for public repositories and repositories with a {% data variables.product.prodname_GH_advanced_security %} license. For an overview of {% data variables.product.product_name %} security features, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)." +## Parte 5: Compilar de forma segura en {% data variables.product.product_name %} +{% data variables.product.product_name %} tiene características de seguridad diversas que ayudan a mantener la seguridad del código y de los secretos en los repositorios. Algunas de las características se encuentran disponibles para todos los repositorios, mientras que otras solo están disponibles para los repositorios públicos o para aquellos con una licencia de {% data variables.product.prodname_GH_advanced_security %}. Para ver un resumen de las características de seguridad de {% data variables.product.product_name %}, consulta la sección "[características de seguridad de {% data variables.product.prodname_dotcom %}](/code-security/getting-started/github-security-features)". ### 1. Asegurar tu repositorio -As a repository administrator, you can secure your repositories by configuring repository security settings. These include managing access to your repository, setting a security policy, and managing dependencies. For public repositories, and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled, you can also configure code and secret scanning to automatically identify vulnerabilities and ensure tokens and keys are not exposed. +Como administrador de un repositorio, puedes proteger tus repositorios si configuras los ajustes de seguridad de estos. Estos incluyen el administrar el acceso a tu repositorio, configurar una política de seguridad y administrar las dependencias. Para los repositorios públicos y para los privados que pertenezcan a las organizaciones en donde se haya habilitado la {% data variables.product.prodname_GH_advanced_security %}, también puedes configurar el escaneo de código y de secretos para que identifiquen las vulnerabilidades automáticamente y garanticen que los tokens y las llaves no se expongan. -For more information on steps you can take to secure your repositories, see "[Securing your repository](/code-security/getting-started/securing-your-repository)." +Para obtener más información sobre los pasos que debes tomar para proteger tus repositorios, consulta la sección "[Proteger tu repositorio](/code-security/getting-started/securing-your-repository)". {% endif %} {% ifversion fpt %} -### 2. Managing your dependencies -A large part of building securely is maintaining your project's dependencies to ensure that all packages and applications you depend on are updated and secure. You can manage your repository's dependencies on {% data variables.product.product_name %} by exploring the dependency graph for your repository, using Dependabot to automatically raise pull requests to keep your dependencies up-to-date, and receiving Dependabot alerts and security updates for vulnerable dependencies. +### 2. Administrar tus dependencias +Una parte grande de compilar de forma segura es mantener las dependencias de tu proyecto para asegurarte de que todos los paquetes y aplicaciones de las cuales dependes estén actualizadas y seguras. Puedes administrar las dependencias de tu repositorio en {% data variables.product.product_name %} si exploras la gráfica de dependencias para este utilizando el Dependabot para levantar solicitudes de cambio automáticamente para mantener tus dependencias actualizadas y recibiendo alertas del Dependabot y actualizaciones de seguridad para las dependencias vulnerables. -For more information, see "[Securing your software supply chain](/code-security/supply-chain-security)." +Para obtener más información, consulta la sección "[Proteger tu cadena de suministro de software](/code-security/supply-chain-security)". {% endif %} -## Part {% ifversion ghes < 3.0 %}5:{% else %}6:{% endif %} Participating in {% data variables.product.prodname_dotcom %}'s community +## Parte {% ifversion ghes < 3.0 %}5:{% else %}6:{% endif %} Participar en la comunidad de {% data variables.product.prodname_dotcom %} {% data reusables.getting-started.participating-in-community %} -### 1. Contributing to open source projects +### 1. Contribuir con proyectos de código abierto {% data reusables.getting-started.open-source-projects %} -### 2. Interacting with {% data variables.product.prodname_gcf %} +### 2. Interactuar con {% data variables.product.prodname_gcf %} {% data reusables.support.ask-and-answer-forum %} -### 3. Learning with {% data variables.product.prodname_learning %} +### 3. Aprender con {% data variables.product.prodname_learning %} {% data reusables.getting-started.learning-lab %} {% ifversion fpt %} -### 4. Supporting the open source community +### 4. Apoyar a la comunidad de código abierto {% data reusables.getting-started.sponsors %} ### 5. Comunicarse con {% data variables.contact.github_support %} diff --git a/translations/es-ES/content/get-started/onboarding/index.md b/translations/es-ES/content/get-started/onboarding/index.md index a258e00fdc..63de47e2c6 100644 --- a/translations/es-ES/content/get-started/onboarding/index.md +++ b/translations/es-ES/content/get-started/onboarding/index.md @@ -1,5 +1,5 @@ --- -title: Onboarding +title: Incorporación intro: '' versions: fpt: '*' diff --git a/translations/es-ES/content/get-started/quickstart/be-social.md b/translations/es-ES/content/get-started/quickstart/be-social.md index f1e87d2312..34c0a7416d 100644 --- a/translations/es-ES/content/get-started/quickstart/be-social.md +++ b/translations/es-ES/content/get-started/quickstart/be-social.md @@ -6,6 +6,7 @@ redirect_from: - /github/getting-started-with-github/be-social - /github/getting-started-with-github/quickstart/be-social intro: 'Puedes interactuar con personas, repositorios y organizaciones en {% data variables.product.prodname_dotcom %}. Ve en qué están trabajando los demás y con quién se están conectando desde tu tablero personal.' +permissions: '{% data reusables.enterprise-accounts.emu-permission-interact %}' versions: fpt: '*' ghes: '*' diff --git a/translations/es-ES/content/get-started/quickstart/create-a-repo.md b/translations/es-ES/content/get-started/quickstart/create-a-repo.md index 9a8e314417..088cb564e7 100644 --- a/translations/es-ES/content/get-started/quickstart/create-a-repo.md +++ b/translations/es-ES/content/get-started/quickstart/create-a-repo.md @@ -58,14 +58,14 @@ Puedes almacenar varios proyectos en los repositorios de {% data variables.produ {% data reusables.cli.cli-learn-more %} -1. In the command line, navigate to the directory where you would like to create a local clone of your new project. -2. To create a repository for your project, use the `gh repo create` subcommand. Replace `project-name` with the desired name for your repository. If you want your project to belong to an organization instead of to your user account, specify the organization name and project name with `organization-name/project-name`. +1. En la línea de comandos, navega al directorio en donde te gustaría crear un clon local de tu proyecto nuevo. +2. Para crear un repositorio de tu proyecto, utiliza el subcomando `gh repo create`. Reemplaza a `project-name` con el nombre que deseas dar a tu repositorio. Si quieres que tu proyecto pertenezca a una organización en vez de a tu cuenta de usuario, especifica el nombre de la organización y del proyecto con `organization-name/project-name`. ```shell gh repo create project-name ``` -3. Follow the interactive prompts. To clone the repository locally, confirm yes when asked if you would like to clone the remote project directory. Alternatively, you can specify arguments to skip these prompts. For more information about possible arguments, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_repo_create). +3. Sigue los mensajes interactivos. Para clonar el repositorio localmente, confirma que sí cuando se te pregunte si quisieras clonar el directorio remoto del proyecto. Como alternativa, puedes especificar los argumentos para omitir estos mensajes. Para obtener más información sobre los argumentos posibles, consulta [el manual de {% data variables.product.prodname_cli %}](https://cli.github.com/manual/gh_repo_create). {% endcli %} @@ -94,18 +94,18 @@ Confirmemos un cambio en el archivo *README*. {% cli %} -Now that you have created a project, you can start committing changes. +Ahora que creaste un proyecto, puedes comenzar a confirmar cambios. -Los archivos *README* son un lugar ideal para describir tu proyecto en más detalle o agregar documentación, como la forma en que se debe instalar o usar tu proyecto. El contenido de tu archivo *README* se mostrará automáticamente en la página inicial de tu repositorio. Follow these steps to add a *README* file. +Los archivos *README* son un lugar ideal para describir tu proyecto en más detalle o agregar documentación, como la forma en que se debe instalar o usar tu proyecto. El contenido de tu archivo *README* se mostrará automáticamente en la página inicial de tu repositorio. Sigue estos pasos para agregar un archivo *README*. -1. In the command line, navigate to the root directory of your new project. (This directory was created when you ran the `gh repo create` command.) -1. Create a *README* file with some information about the project. +1. En la línea de comandos, navega al directorio raíz de tu proyecto nuevo. (Este directorio se creó cuando ejecutas el comando `gh repo create`). +1. Crea un archivo *README* con algo de información sobre el proyecto. ```shell echo "info about this project" >> README.md ``` -1. Enter `git status`. You will see that you have an untracked `README.md` file. +1. Ingresa `git status`. Verás que tienes un archivo `README.md` sin rastrear. ```shell $ git status @@ -117,13 +117,13 @@ Los archivos *README* son un lugar ideal para describir tu proyecto en más deta nothing added to commit but untracked files present (use "git add" to track) ``` -1. Stage and commit the file. +1. Prueba y confirma el archivo. ```shell git add README.md && git commit -m "Add README" ``` -1. Push the changes to your branch. +1. Sube los cambios a tu rama. ```shell git push --set-upstream origin HEAD diff --git a/translations/es-ES/content/get-started/quickstart/fork-a-repo.md b/translations/es-ES/content/get-started/quickstart/fork-a-repo.md index 62de0cda0f..7aa504a3ea 100644 --- a/translations/es-ES/content/get-started/quickstart/fork-a-repo.md +++ b/translations/es-ES/content/get-started/quickstart/fork-a-repo.md @@ -7,6 +7,7 @@ redirect_from: - /github/getting-started-with-github/fork-a-repo - /github/getting-started-with-github/quickstart/fork-a-repo intro: Una ramificación es una copia de un repositorio. Bifurcar un repositorio te permite experimentar libremente con cambios sin afectar el proyecto original. +permissions: '{% data reusables.enterprise-accounts.emu-permission-fork %}' versions: fpt: '*' ghes: '*' @@ -83,7 +84,7 @@ gh repo fork repository --org "octo-org" ## Clonar tu repositorio bifurcado -Right now, you have a fork of the Spoon-Knife repository, but you don't have the files in that repository locally on your computer. +Ahora mismo, tienes una bifurcación del repositorio Spoon-Knife, pero no tienes los archivos de ese repositorio localmente en tu computadora. {% include tool-switcher %} {% webui %} diff --git a/translations/es-ES/content/get-started/quickstart/set-up-git.md b/translations/es-ES/content/get-started/quickstart/set-up-git.md index 1b0cfa279c..0ee83db002 100644 --- a/translations/es-ES/content/get-started/quickstart/set-up-git.md +++ b/translations/es-ES/content/get-started/quickstart/set-up-git.md @@ -26,7 +26,7 @@ topics: ## Utilizar GitHub -Para usar Git en la línea de comando, deberás descargar, instalar y configurar Git en tu computadora. You can also install {% data variables.product.prodname_cli %} to use {% data variables.product.product_name %} from the command line. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)". +Para usar Git en la línea de comando, deberás descargar, instalar y configurar Git en tu computadora. También puedes instalar el {% data variables.product.prodname_cli %} para utilizar {% data variables.product.product_name %} desde la línea de comandos. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)". Si deseas trabajar con Git de forma local, pero no deseas utilizar la línea de comando, puedes descargar e instalar en su lugar el cliente [{% data variables.product.prodname_desktop %}]({% data variables.product.desktop_link %}). Para obtener más información, consulta la sección "[Instalar y configurar {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/)". @@ -49,7 +49,7 @@ Cuando te conectas a un repositorio {% data variables.product.product_name %} de {% note %} -**Note:** You can authenticate to {% data variables.product.product_name %} using {% data variables.product.prodname_cli %}, for either HTTP or SSH. For more information, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login). +**Nota:** Puedes autenticarte en {% data variables.product.product_name %} utilizando el {% data variables.product.prodname_cli %} ya sea para HTTP o SSH. Para obtener más información, consulta [`gh auth login`](https://cli.github.com/manual/gh_auth_login). {% endnote %} diff --git a/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md b/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md index 7f3393b75e..35f28d5d7b 100644 --- a/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md +++ b/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md @@ -20,7 +20,7 @@ shortTitle: Prueba de Entreprise Cloud {% data reusables.organizations.about-organizations %} -You can use organizations for free with {% data variables.product.prodname_free_team %}, which includes limited features. For additional features, such as SAML single sign-on (SSO), access control for {% data variables.product.prodname_pages %}, and included {% data variables.product.prodname_actions %} minutes, you can upgrade to {% data variables.product.prodname_ghe_cloud %}. For a detailed list of the features available with {% data variables.product.prodname_ghe_cloud %}, see our [Pricing](https://github.com/pricing) page. +Puedes utilizar organizaciones gratuitamente con {% data variables.product.prodname_free_team %}, las cuales incluyen características limitadas. Para encontrar características adicionales, tales como el inicio de sesión único (SSO) de SAML, el control de accesos para las {% data variables.product.prodname_pages %} y los minutos incluidos de las {% data variables.product.prodname_actions %}, puedes mejorar a {% data variables.product.prodname_ghe_cloud %}. Para encontrar una lista detallada de características disponibles con {% data variables.product.prodname_ghe_cloud %}, consulta nuestra página de [Precios](https://github.com/pricing). {% data reusables.saml.saml-accounts %}Para obtener más información, consulta "Acerca de la administración de identidad y accesos con el inicio de sesión único de SAML". @@ -28,7 +28,7 @@ You can use organizations for free with {% data variables.product.prodname_free_ ## Acerca de las pruebas de {% data variables.product.prodname_ghe_cloud %} -You can set up a 14-day trial to evaluate {% data variables.product.prodname_ghe_cloud %}. No es necesario que proporciones un método de pago durante la prueba a menos que agreges aplicaciones de {% data variables.product.prodname_marketplace %} en tu organización que requieran de un método de pago. Para obtener más información, consulta "Acerca de la facturación para {% data variables.product.prodname_marketplace %}". +Puedes configurar un periodo de 14 días para evaluar {% data variables.product.prodname_ghe_cloud %}. No es necesario que proporciones un método de pago durante la prueba a menos que agreges aplicaciones de {% data variables.product.prodname_marketplace %} en tu organización que requieran de un método de pago. Para obtener más información, consulta "Acerca de la facturación para {% data variables.product.prodname_marketplace %}". Tu prueba incluye 50 asientos. Si necesitas más plazas para evaluar a {% data variables.product.prodname_ghe_cloud %}, contacta a {% data variables.contact.contact_enterprise_sales %}. Al finalizar la prueba, puedes elegir una cantidad diferente de asientos. @@ -36,12 +36,12 @@ También hay pruebas disponibles para {% data variables.product.prodname_ghe_ser ## Configurar tu prueba de {% data variables.product.prodname_ghe_cloud %} -Before you can try {% data variables.product.prodname_ghe_cloud %}, you must be signed into a user account. If you don't already have a user account on {% data variables.product.prodname_dotcom_the_website %}, you must create one. Para obtener más información, consulta "Iniciar sesión para una nueva cuenta de {% data variables.product.prodname_dotcom %}". +Antes de probar {% data variables.product.prodname_ghe_cloud %}, debes firmarte en una cuenta de usuario. Si aún no tienes una cuenta de usuario en {% data variables.product.prodname_dotcom_the_website %}, debes crear una. Para obtener más información, consulta "Iniciar sesión para una nueva cuenta de {% data variables.product.prodname_dotcom %}". -1. Navigate to [{% data variables.product.prodname_dotcom %} for enterprises](https://github.com/enterprise). -1. Click **Start a free trial**. !["Start a free trial" button](/assets/images/help/organizations/start-a-free-trial-button.png) -1. Click **Enterprise Cloud**. !["Enterprise Cloud" button](/assets/images/help/organizations/enterprise-cloud-trial-option.png) -1. Follow the prompts to configure your trial. +1. Navega a [{% data variables.product.prodname_dotcom %} para empresas](https://github.com/enterprise). +1. Haz clic en **Iniciar una prueba gratuita**. ![Botón de "Comenzar una prueba gratuita"](/assets/images/help/organizations/start-a-free-trial-button.png) +1. Haz clic en **Enterprise Cloud**. ![Botón de "Enterprise Cloud"](/assets/images/help/organizations/enterprise-cloud-trial-option.png) +1. Sigue los mensajes para configurar tu prueba. ## Explorar {% data variables.product.prodname_ghe_cloud %} diff --git a/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md b/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md index ddd6e1233a..9877e0b6ee 100644 --- a/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md +++ b/translations/es-ES/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md @@ -18,7 +18,7 @@ shortTitle: Prueba de Enterprise Server Puedes solicitar una prueba de 45 días para evaluar {% data variables.product.prodname_ghe_server %}. La prueba se instalará a modo de aparato virtual, con opciones para la implementación en el entorno local o en la nube. Para acceder a una lista de plataformas de visualización compatibles, consulta "[Configurar un servidor de GitHub Enterprise](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance)". -{% ifversion ghes %}Las alertas de{% else %}Seguridad{% endif %} del {% data variables.product.prodname_dependabot %} y de{% data variables.product.prodname_github_connect %} no están actualmente disponibles durante las pruebas de {% data variables.product.prodname_ghe_server %}. Para obtener una demostración de estas características, contacta a {% data variables.contact.contact_enterprise_sales %}. Para obtener más información acerca de estas características, consulta las secciones "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" y "[Conectar el {% data variables.product.prodname_ghe_server %} a {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)". +{% ifversion ghes %}Las alertas de{% else %}Seguridad{% endif %} del {% data variables.product.prodname_dependabot %} y de{% data variables.product.prodname_github_connect %} no están actualmente disponibles durante las pruebas de {% data variables.product.prodname_ghe_server %}. Para obtener una demostración de estas características, contacta a {% data variables.contact.contact_enterprise_sales %}. Para obtener más información acerca de estas características, consulta las secciones "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" y "[Conectar tu cuenta empresarial a {% data variables.product.prodname_dotcom_the_website %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)". También hay pruebas disponibles para {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta "[Configurar una prueba de {% data variables.product.prodname_ghe_cloud %}](/articles/setting-up-a-trial-of-github-enterprise-cloud)". @@ -28,7 +28,7 @@ También hay pruebas disponibles para {% data variables.product.prodname_ghe_clo {% data variables.product.prodname_ghe_server %} está instalado como aparato virtual. Determina la mejor persona de tu organización para configurar una máquina virtual y pídele que envíe una [solicitud de prueba](https://enterprise.github.com/trial). Puedes comenzar tu prueba de forma inmediata después de enviar una solicitud. -Para configurar una cuenta para el {% data variables.product.prodname_enterprise %} portal web, haz clic en el enlace del correo electrónico que recibiste después de enviar tu solicitud de prueba y sigue las instrucciones. A continuación, descarga tu archivo de licencia. For more information, see "[Managing your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise)." +Para configurar una cuenta para el {% data variables.product.prodname_enterprise %} portal web, haz clic en el enlace del correo electrónico que recibiste después de enviar tu solicitud de prueba y sigue las instrucciones. A continuación, descarga tu archivo de licencia. Paa obtener más información, consulta la sección "[Administrar tu licencia de {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise)". Para instalar {% data variables.product.prodname_ghe_server %}, descarga los elementos necesarios y carga tu archivo de licencia. Para obtener más información, consulta las instrucciones para tu plataforma de visualización elegida en "[Configurar una {% data variables.product.prodname_ghe_server %} instancia](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance)". diff --git a/translations/es-ES/content/get-started/using-git/dealing-with-special-characters-in-branch-and-tag-names.md b/translations/es-ES/content/get-started/using-git/dealing-with-special-characters-in-branch-and-tag-names.md new file mode 100644 index 0000000000..574e5d5685 --- /dev/null +++ b/translations/es-ES/content/get-started/using-git/dealing-with-special-characters-in-branch-and-tag-names.md @@ -0,0 +1,48 @@ +--- +title: Tratar con caracteres especiales en los nombres de rama y etiqueta +intro: 'Git es muy permisivo cuando se trata de qué caracteres se permiten en los nombres de rama y etiqueta. Cuando utilizas Git desde un shell de línea de comandos, podrías necesitar escapar o citar caracteres especiales.' +versions: + fpt: '*' + ghes: '*' + ghae: '*' +shortTitle: Caracteres especiales en los nombres +--- + +## Acerca de los nombres de las ramas y etiquetas + +La mayoría de los repositorios utilizan nombres de rama simples, tales como `main` o `update-icons`. Los nombres de etiqueta también siguen un formato básico, tal como un número de versión como `v1.2.3`. Tanto los nombres de rama como los de etiqueta podrían utilizar el separador de ruta (`/`) para dar estructura, por ejemplo `area/item` o `level-1/level-2/level-3`. Exceptuando un par de casos — tales como el no iniciar o finalizar un nombre con una diagonal o tener diagonales consecutivas en los nombres — Git tiene muy pocas restricciones sobre qué caracteres pueden utilizarse en los nombres de etiqueta y de rama. Para obtener más información, consulta "[git-check-ref-format](https://git-scm.com/docs/git-check-ref-format) en la documentación de Git. + +## Por qué necesitas escapar los caracteres especiales + +Cuando utilizas un CLI, podrías encontrarte con situaciones en donde el nombre de rama o etiqueta contiene caracteres especiales que tienen un significado especial para tu ambiente de shell. Para utilizar estos caracteres de forma segura en un comando de Git, deben citarse o escaparse, de otra manera, los comandos podrían tener efectos sin atender. + +Por ejemplo, muchos shells utilizan el caracter `$` para referirse a una variable. La mayoría de los shells interpretarían un nombre de rama válido como `hello-$USER` como un equivalente de la palabra "hellO", seguida de un guion, seguida del valor actual de la variable `USER`, en vez de la secuencia literal `hello-$USER`. Si un nombre de rama incluye el caracter `$`, entonces el shell no debe expandirlo como una referencia de variable. De forma similar, si un nombre de rama contiene un punto y coma (`;`), la mayoría de los shells lo interpretarán como un separador de comandos, así que necesita citarse o escaparse. + +## Cómo escapar los caracteres especiales en nombres de rama y etiqueta + +La mayoría de los nombres de etiquetas y ramas con caracteres especiales se pueden manejar si incluyen el nombre entre comillas sencillas, por ejemplo `'hello-$USER'`. + +* En el shell de [Bas](https://www.gnu.org/software/bash/), el encerrar una secuencia de caracteres entre comillas simples preserva el valor literal de estos dentro de dichas comillas sencillas. +* [Zsh](https://www.zsh.org/) se comporta de forma similar a Bash, sin embargo, este comportamiento se puede configurar utilizando la opción `RC_QUOTES`. +* [PowerShell](https://microsoft.com/powershell) también trata a los caracteres literalmente cuando están entre comillas sencillas. + +Para estos shells, la excepción principal es cuando el nombre de etiqueta o rama mismo contiene una comilla sencilla. En este caso, debes consultar la documentación oficial de tu shell: + +* [Documentación de Bash](https://www.gnu.org/software/bash/manual/) +* [Documentación de Zsh](https://zsh.sourceforge.io/Doc/) +* [Documentación de Fish](https://fishshell.com/docs/current/) +* [Documentación de PowerShell](https://docs.microsoft.com/en-gb/powershell/) + +## Nombrar las ramas y etiquetas + +De ser posible, crea nombres de rama y de etiqueta que no contengan caracteres especiales, ya que necesitarás escaparlos. Un conjunto predeterminado de caracteres seguros a utilizar para los nombres de rama y etiqueta es: + +* El alfabeto inglés (de la `a` a la `z` y de la `A` a la `Z`) +* Números (`0` to `9`) +* Un conjunto limitado de caracteres de puntuación: + * punto (`.`) + * guion (`-`) + * guion bajo (`_`) + * diagonal (`/`) + +Para evitar la confusión, deberías iniciar los nombres de rama con una letra. diff --git a/translations/es-ES/content/get-started/using-git/index.md b/translations/es-ES/content/get-started/using-git/index.md index 0ba4bed130..c2fd680284 100644 --- a/translations/es-ES/content/get-started/using-git/index.md +++ b/translations/es-ES/content/get-started/using-git/index.md @@ -23,5 +23,6 @@ children: - /about-git-rebase - /using-git-rebase-on-the-command-line - /resolving-merge-conflicts-after-a-git-rebase + - /dealing-with-special-characters-in-branch-and-tag-names --- diff --git a/translations/es-ES/content/get-started/using-git/pushing-commits-to-a-remote-repository.md b/translations/es-ES/content/get-started/using-git/pushing-commits-to-a-remote-repository.md index cbec8a68e4..6e3e8d873b 100644 --- a/translations/es-ES/content/get-started/using-git/pushing-commits-to-a-remote-repository.md +++ b/translations/es-ES/content/get-started/using-git/pushing-commits-to-a-remote-repository.md @@ -14,7 +14,7 @@ versions: shortTitle: Subir confirmaciones a un remoto --- -## About `git push` +## Acerca de `git push` El comando `git push` toma dos argumentos: * Un nombre remoto, por ejemplo, `origin` diff --git a/translations/es-ES/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md b/translations/es-ES/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md index c94e3f5331..f02722778f 100644 --- a/translations/es-ES/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md +++ b/translations/es-ES/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md @@ -26,8 +26,8 @@ Si creas un nuevo clon del repositorio, no perderás ninguno de tus historiales ```shell $ cd REPOSITORY-NAME ``` -5. To filter out the subfolder from the rest of the files in the repository, run [`git filter-repo`](https://github.com/newren/git-filter-repo), supplying this information: - - `FOLDER-NAME`: The folder within your project where you'd like to create a separate repository. +5. Para filtrar la subcarpeta desde el resto de los archivos en el repositorio, ejecuta [`git filter-repo`](https://github.com/newren/git-filter-repo), proporcionando esta información: + - `FOLDER-NAME`: la carpeta dentro de tu proyecto en donde desearías crear un repositorio separado. {% windows %} @@ -45,7 +45,7 @@ Si creas un nuevo clon del repositorio, no perderás ninguno de tus historiales > Rewrite 48dc599c80e20527ed902928085e7861e6b3cbe6 (89/89) > Ref 'refs/heads/BRANCH-NAME' was rewritten ``` - The repository should now only contain the files that were in your subfolder(s). + El repositorio debería ahora únicamente contener archivos que estuvieron en tu(s) subcarpeta(s) 6. [Crea un nuevo repositorio](/articles/creating-a-new-repository/) en {% data variables.product.product_name %}. 7. En la parte superior de la página nueva Quick Setup del repositorio {% data variables.product.product_name %}, haz clic en {% octicon "clippy" aria-label="The copy to clipboard icon" %} para copiar la URL del repositorio remoto. ![Copiar el campo de URL de repositorio remoto](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) diff --git a/translations/es-ES/content/get-started/using-github/github-cli.md b/translations/es-ES/content/get-started/using-github/github-cli.md index 04ea9b7648..ce54c62de2 100644 --- a/translations/es-ES/content/get-started/using-github/github-cli.md +++ b/translations/es-ES/content/get-started/using-github/github-cli.md @@ -13,4 +13,4 @@ topics: {% data reusables.cli.cli-features %} -For more information, see "[{% data variables.product.prodname_cli %}](/github-cli)." +Para obtener más información, consulta la sección "[{% data variables.product.prodname_cli %}](/github-cli)". diff --git a/translations/es-ES/content/get-started/using-github/github-for-mobile.md b/translations/es-ES/content/get-started/using-github/github-for-mobile.md index 6efa261083..6de83ecc5d 100644 --- a/translations/es-ES/content/get-started/using-github/github-for-mobile.md +++ b/translations/es-ES/content/get-started/using-github/github-for-mobile.md @@ -79,7 +79,7 @@ Para volver a habilitar los Enlaces Universales, sostén cualquier enlace de {% Si encuentras un error en {% data variables.product.prodname_mobile %}, puedes mandarnos un mensaje de correo electrónico a mobilefeedback@github.com. -You can submit feature requests or other feedback for {% data variables.product.prodname_mobile %} on [{% data variables.product.prodname_discussions %}](https://github.com/github/feedback/discussions?discussions_q=category%3A%22Mobile+Feedback%22). +Puedes emitir solicitudes de características o cualquier otro tipo de retroalimentación para {% data variables.product.prodname_mobile %} en los [{% data variables.product.prodname_discussions %}](https://github.com/github/feedback/discussions?discussions_q=category%3A%22Mobile+Feedback%22). ## Abandonar los lanzamientos beta para iOS 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 710ac6bb20..0d4a7bf509 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 @@ -24,7 +24,7 @@ A continuación aparece una lista de algunos de los atajos del teclado disponibl | Atajo del teclado | Descripción | | --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| s o / | Se concentra en la barra de búsqueda. Para obtener más información, consulta "[Acerca de buscar en {% data variables.product.company_short %}](/articles/about-searching-on-github)". | +| s o / | Se concentra en la barra de búsqueda. Para obtener más información, consulta "[Acerca de buscar en {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)". | | g n | Dirige a tus notificaciones. Para obtener más información, consulta la sección {% ifversion fpt or ghes or ghae %}"[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 %}". | | esc | Cuando se concentra en la hovercard de un usuario, de una propuesta o de una solicitud de extracción, se cierra la hovercard y se vuelve a centrar en el elemento en el que está la hovercard | @@ -42,23 +42,23 @@ A continuación aparece una lista de algunos de los atajos del teclado disponibl ## Edición del código fuente -| Atajo del teclado | Descripción | -| ----------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion fpt %} -| . | Opens a repository or pull request in the web-based editor. For more information, see "[Web-based editor](/codespaces/developing-in-codespaces/web-based-editor)."{% endif %} -| control b o comando b | Inserta el formato Markdown para el texto en negrita | -| control i o comando i | Inserta el formato Markdown para el texto en cursiva | -| control k o comando k | Inserta el formato Markdown para crear un enlace | -| e | Abre el archivo de código fuente en la pestaña **Editar archivo** | -| control f o comando f | Comienza la búsqueda en el editor de archivos | -| control g o comando g | Busca el siguiente | -| shift control g o shift comando g | Busca el anterior | -| shift control f o opción de comando f | Reemplaza | -| shift control r o shift opción de comando f | Reemplaza todo | -| alt g | Salta la línea | -| control z o comando z | Deshace | -| control y o comando y | Rehace | -| cmd + shift + p | Alterna entre las pestañas **Edit file** (Editar comentario) y **Preview changes** (Vista previa de cambios) | -| control s o command s | Escribir un mensaje de confirmación | +| Atajo del teclado | Descripción | +| ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion fpt %} +| . | Abre un repositorio o solicitud de cambio en el editor basado en la web. Para obtener más información, consulta la sección "[Editor basado en la web](/codespaces/developing-in-codespaces/web-based-editor)".{% endif %} +| control b o comando b | Inserta el formato Markdown para el texto en negrita | +| control i o comando i | Inserta el formato Markdown para el texto en cursiva | +| control k o comando k | Inserta el formato Markdown para crear un enlace | +| e | Abre el archivo de código fuente en la pestaña **Editar archivo** | +| control f o comando f | Comienza la búsqueda en el editor de archivos | +| control g o comando g | Busca el siguiente | +| shift control g o shift comando g | Busca el anterior | +| shift control f o opción de comando f | Reemplaza | +| shift control r o shift opción de comando f | Reemplaza todo | +| alt g | Salta la línea | +| control z o comando z | Deshace | +| control y o comando y | Rehace | +| cmd + shift + p | Alterna entre las pestañas **Edit file** (Editar comentario) y **Preview changes** (Vista previa de cambios) | +| control s o command s | Escribir un mensaje de confirmación | Para obtener más atajos del teclado, consulta la [Documentación de CodeMirror](https://codemirror.net/doc/manual.html#commands). @@ -82,28 +82,28 @@ Para obtener más atajos del teclado, consulta la [Documentación de CodeMirror] | control i o comando i | Inserta formateo de lenguaje de marcado para poner el texto en itálicas{% ifversion fpt or ghae-next or ghes > 3.1 %} | control e o command e | Insterta formato de lenguaje de marcado para código o un comando dentro de una línea{% endif %} | control k o comando k | Inserta el formato Markdown para crear un enlace | -| control shift p o comando shift p | Toggles between the **Write** and **Preview** comment tabs{% ifversion fpt or ghae-next or ghes > 3.2 %} -| control shift 7 or command shift 7 | Inserts Markdown formatting for an ordered list | -| control shift 8 or command shift 8 | Inserts Markdown formatting for an unordered list{% endif %} +| control shift p o comando shift p | Alterna entre las pestañas de comentarios de **Escritura** y **Vista previa **{% ifversion fpt or ghae-next or ghes > 3.2 %} +| control shift 7 o command shift 7 | Inserta formato de lenguaje de marcado para una lista ordenada | +| control shift 8 o command shift 8 | Inserta formato de lenguaje de marcado para una lista no ordenada{% endif %} | control enter | Envía un comentario | | control . y luego control [número de respuesta guardada] | Abre el menú de respuestas guardadas y luego completa automáticamente el campo de comentarios con una respuesta guardada. Para obtener más información, consulta "[Acerca de las respuestas guardadas](/articles/about-saved-replies)".{% ifversion fpt or ghae-next or ghes > 3.2 %} -| control shift . or command shift. | Inserts Markdown formatting for a quote{% endif %}{% ifversion fpt %} +| control shift . o command shift. | Inserta formato de lenguaje de marcado para una cita{% endif %}{% ifversion fpt %} | control g o comando g | Inserta una sugerencia. Para obtener más información, consulta "[Revisar las modificaciones propuestas en una solicitud de extracción](/articles/reviewing-proposed-changes-in-a-pull-request)." {% endif %} | r | Cita el texto seleccionado en tu respuesta. Para obtener más información, consulta "[Escritura básica y sintaxis de formato](/articles/basic-writing-and-formatting-syntax#quoting-text)". | ## Listas de propuestas y solicitudes de extracción -| Atajo del teclado | Descripción | -| ------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| c | Crear un informe de problemas | -| control / o comando / | Hace que el cursor se concentre en la barra de propuestas o solicitudes de respuesta. For more information, see "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)."| | -| u | Filtra por autor | -| l | Filtra por etiquetas o edita etiquetas. Para obtener más información, consulta "[Filtrar propuestas y solicitudes de extracción por etiquetas](/articles/filtering-issues-and-pull-requests-by-labels)". | -| alt y haz clic | Al filtrar por etiquetas, excluye etiquetas. Para obtener más información, consulta "[Filtrar propuestas y solicitudes de extracción por etiquetas](/articles/filtering-issues-and-pull-requests-by-labels)". | -| m | Filtra por hitos o edita hitos. Para obtener más información, consulta "[Filtrar propuestas y solicitudes de extracción por hito](/articles/filtering-issues-and-pull-requests-by-milestone)". | -| a | Filtra por asignatario s o edita asignatarios. Para obtener más información, consulta "[Filtrar propuestas y solicitudes de extracción por asignatarios](/articles/filtering-issues-and-pull-requests-by-assignees)". | -| o o enter | Abre una propuesta | +| Atajo del teclado | Descripción | +| ------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| c | Crear un informe de problemas | +| control / o comando / | Hace que el cursor se concentre en la barra de propuestas o solicitudes de respuesta. Para obtener más información, consulta la sección "[Filtrar y buscar las propuestas y solicitudes de cambio](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)".| | +| u | Filtra por autor | +| l | Filtra por etiquetas o edita etiquetas. Para obtener más información, consulta "[Filtrar propuestas y solicitudes de extracción por etiquetas](/articles/filtering-issues-and-pull-requests-by-labels)". | +| alt y haz clic | Al filtrar por etiquetas, excluye etiquetas. Para obtener más información, consulta "[Filtrar propuestas y solicitudes de extracción por etiquetas](/articles/filtering-issues-and-pull-requests-by-labels)". | +| m | Filtra por hitos o edita hitos. Para obtener más información, consulta "[Filtrar propuestas y solicitudes de extracción por hito](/articles/filtering-issues-and-pull-requests-by-milestone)". | +| a | Filtra por asignatario s o edita asignatarios. Para obtener más información, consulta "[Filtrar propuestas y solicitudes de extracción por asignatarios](/articles/filtering-issues-and-pull-requests-by-assignees)". | +| o o enter | Abre una propuesta | ## Propuestas y solicitudes de extracción | Atajo del teclado | Descripción | diff --git a/translations/es-ES/content/get-started/using-github/troubleshooting-connectivity-problems.md b/translations/es-ES/content/get-started/using-github/troubleshooting-connectivity-problems.md index 761467c541..e85635734a 100644 --- a/translations/es-ES/content/get-started/using-github/troubleshooting-connectivity-problems.md +++ b/translations/es-ES/content/get-started/using-github/troubleshooting-connectivity-problems.md @@ -30,7 +30,7 @@ Si no puedes verificar con el captcha: ## Cambiar métodos de clonación -Cambiar desde la clonación por SSH a la clonación por HTTPS, o viceversa, puede mejorar la conectividad. For more information, see "[Troubleshooting cloning errors](/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors)." +Cambiar desde la clonación por SSH a la clonación por HTTPS, o viceversa, puede mejorar la conectividad. Para obtener más información, consulta la sección "[Solucionar problemas para los errores de clonado](/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors)". Si están ocurriendo interrupciones con SSH, consulta "[Error: Número de archivo erróneo](/articles/error-bad-file-number)". diff --git a/translations/es-ES/content/github-cli/github-cli/about-github-cli.md b/translations/es-ES/content/github-cli/github-cli/about-github-cli.md index f72396b1c6..20a347e262 100644 --- a/translations/es-ES/content/github-cli/github-cli/about-github-cli.md +++ b/translations/es-ES/content/github-cli/github-cli/about-github-cli.md @@ -1,5 +1,5 @@ --- -title: About GitHub CLI +title: Acerca del CLI de GitHub intro: '{% data reusables.cli.cli-intro %}' versions: fpt: '*' diff --git a/translations/es-ES/content/github-cli/github-cli/creating-github-cli-extensions.md b/translations/es-ES/content/github-cli/github-cli/creating-github-cli-extensions.md index 428ee34e06..20e0e15f3f 100644 --- a/translations/es-ES/content/github-cli/github-cli/creating-github-cli-extensions.md +++ b/translations/es-ES/content/github-cli/github-cli/creating-github-cli-extensions.md @@ -1,6 +1,6 @@ --- -title: Creating GitHub CLI extensions -intro: 'Learn how to share new {% data variables.product.prodname_cli %} commands with other users by creating custom extensions for {% data variables.product.prodname_cli %}.' +title: Crear extensiones del CLI de GitHub +intro: 'Aprende cómo compartir comandos nuevos de {% data variables.product.prodname_cli %} con otros usurios creando extensiones personalizadas para {% data variables.product.prodname_cli %}.' versions: fpt: '*' ghes: '*' @@ -9,43 +9,43 @@ topics: - CLI --- -## About {% data variables.product.prodname_cli %} extensions +## Acerca de las extensiones del {% data variables.product.prodname_cli %} -{% data reusables.cli.cli-extensions %} For more information about how to use {% data variables.product.prodname_cli %} extensions, see "[Using {% data variables.product.prodname_cli %} extensions](/github-cli/github-cli/using-github-cli-extensions)." +{% data reusables.cli.cli-extensions %} Para obtener más información sobre cómo utilizar extensiones de {% data variables.product.prodname_cli %}, consulta la sección "[Utilizar extensiones de {% data variables.product.prodname_cli %}](/github-cli/github-cli/using-github-cli-extensions)". -You need a repository for each extension that you create. The repository name must start with `gh-`. The rest of the repository name is the name of the extension. At the root of the repository, there must be an executable file with the same name as the repository. This file will be executed when the extension is invoked. +Necesitas un repositorio para cada extensión que crees. El nombre de repositorio debe iniciar con `gh-`. El resto del nombre del repositorio es el nombre de la extensión. En la raíz del repositorio, debe haber un archivo ejecutable con el mismo nombre del repositorio. Este archivo se ejecutará cuando se invoque la extensión. {% note %} -**Note**: We recommend that the executable file is a bash script because bash is a widely available interpreter. You may use non-bash scripts, but the user must have the necessary interpreter installed in order to use the extension. +**Nota**: Te recomendamos que el archivo ejecutable sea un script bash, ya que bash es un intérprete de disponibilidad amplia. Puedes utilizar scripts diferentes a los de bash, pero el usuario debe tener el interprete necesario instalado para poder utilizar la extensión. {% endnote %} -## Creating an extension with `gh extension create` +## Crear una extensión con `gh extension create` -You can use the `gh extension create` command to create a project for your extension, including a bash script that contains some starter code. +Puedes utilizar el comando `gh extension create` para crear un proyecto para tu extensión, incluyendo un script de bash que contenga algo de código de inicio. -1. Set up a new extension by using the `gh extension create` subcommand. Replace `EXTENSION-NAME` with the name of your extension. +1. Configura una extensión utilizando el subcomando `gh extension create`. Reemplaza `EXTENSION-NAME` con el nombre de tu extensión. ```shell gh extension create EXTENSION-NAME ``` -1. Follow the printed instructions to finalize and optionally publish your extension. +1. Sigue las instrucciones impresas para finalizar y, opcionalmente, publicar tu extensíón. -## Creating an extension manually +## Crear una extensión manualmente -1. Create a local directory called `gh-EXTENSION-NAME` for your extension. Replace `EXTENSION-NAME` with the name of your extension. For example, `gh-whoami`. +1. Crea un directorio local para tu extensión llamado `gh-EXTENSION-NAME`. Reemplaza a `EXTENSION-NAME` con el nombre de tu extensión. Por ejemplo, `gh-whoami`. -1. In the directory that you created, add an executable file with the same name as the directory. +1. En el directorio que creaste, agrega un archivo ejecutable con el mismo nombre que el directorio. {% note %} - **Note:** Make sure that your file is executable. On Unix, you can execute `chmod +x file_name` in the command line to make `file_name` executable. On Windows, you can run `git init -b main`, `git add file_name`, then `git update-index --chmod=+x file_name`. + **Nota:** Asegúrate de que tu archivo sea ejecutable. En Unix, puedes ejecutar `chmod +x file_name` en la línea de comandos para hacer ejecutable a `file_name`. En Windows, puedes ejecutar `git init -b main`, `git add file_name`, luego `git update-index --chmod=+x file_name`. {% endnote %} -1. Write your script in the executable file. Por ejemplo: +1. Escribe tu script en el archivo ejecutable. Por ejemplo: ```bash #!/usr/bin/env bash @@ -53,19 +53,19 @@ You can use the `gh extension create` command to create a project for your exten exec gh api user --jq '"You are @\(.login) (\(.name))."' ``` -1. From your directory, install the extension as a local extension. +1. Desde tu directorio, instala la extensión como extensión local. ```bash gh extension install . ``` -1. Verify that your extension works. Replace `EXTENSION-NAME` with the name of your extension. For example, `whoami`. +1. Verifica que tu extensión funcione. Reemplaza a `EXTENSION-NAME` con el nombre de tu extensión. Por ejemplo, `whoami`. ```shell gh EXTENSION-NAME ``` -1. From your directory, create a repository to publish your extension. Replace `EXTENSION-NAME` with the name of your extension. +1. Desde tu directorio, crea un repositorio para publicar tu extensión. Reemplaza a `EXTENSION-NAME` con el nombre de tu extensión. ```shell git init -b main @@ -73,15 +73,15 @@ You can use the `gh extension create` command to create a project for your exten git add . && git commit -m "initial commit" && git push --set-upstream origin main ``` -1. Optionally, to help other users discover your extension, add the repository topic `gh-extension`. This will make the extension appear on the [`gh-extension` topic page](https://github.com/topics/gh-extension). For more information about how to add a repository topic, see "[Classifying your repository with topics](/github/administering-a-repository/managing-repository-settings/classifying-your-repository-with-topics)." +1. Opcionalmente, para ayudar a que otros usuarios descubran tu extensión, agrega el tema de repositorio `gh-extension`. Esto hará que la extensión aparezca en la [página de tema `gh-extension`](https://github.com/topics/gh-extension). Para obtener más información sobre cómo agregar un tema de repositorio, consulta la sección "[Clasificar tu repositorio con temas](/github/administering-a-repository/managing-repository-settings/classifying-your-repository-with-topics)". -## Tips for writing {% data variables.product.prodname_cli %} extensions +## Tips para escribir extensiones de {% data variables.product.prodname_cli %} -### Handling arguments and flags +### Manejar argumentos y marcadores -All command line arguments following a `gh my-extension-name` command will be passed to the extension script. In a bash script, you can reference arguments with `$1`, `$2`, etc. You can use arguments to take user input or to modify the behavior of the script. +Todos los argumentos de línea de comandos que le sigan a un comando `gh my-extension-name` se pasará al script de la extensión. En un script de bash, puedes referenciar argumentos con `$1`, `$2`, etc. Puedes utilizar argumentos para tomar aportaciones de los usuarios o para modificar el comportamiento del script. -For example, this script handles multiple flags. When the script is called with the `-h` or `--help` flag, the script prints help text instead of continuing execution. When the script is called with the `--name` flag, the script sets the next value after the flag to `name_arg`. When the script is called with the `--verbose` flag, the script prints a different greeting. +Por ejemplo, este script maneja marcadores múltiples. Cuando se llama a este script con el marcador `-h` o `--help`, este imprime el texto de ayuda en vez de continuar con la ejecución. Cuando se llama al script con el marcador `--name`, este configura el siguiente valor después del marcador en `name_arg`. Cuando se llama al script con el marcador `--verbose`, este imprime un saludo diferente. ```bash #!/usr/bin/env bash @@ -117,36 +117,36 @@ else fi ``` -### Calling core commands in non-interactive mode +### Llamar a los comandos de forma no interactiva -Some {% data variables.product.prodname_cli %} core commands will prompt the user for input. When scripting with those commands, a prompt is often undesirable. To avoid prompting, supply the necessary information explicitly via arguments. +Algunos comandos nucleares de {% data variables.product.prodname_cli %} pedirán la entrada del usuario. Cuando se hagan scripts con estos comandos, un mensaje a menudo se considera indeseable. Para evitar los mensajes, proporciona la información necesaria explícitamente a través de argumentos. -For example, to create an issue programmatically, specify the title and body: +Por ejemplo, para crear una propuesta con programación, especifica el título y cuerpo: ```bash gh issue create --title "My Title" --body "Issue description" ``` -### Fetching data programatically +### Recuperar datos con programación -Many core commands support the `--json` flag for fetching data programatically. For example, to return a JSON object listing the number, title, and mergeability status of pull requests: +Muchos comandos nucleares son compatibles con el marcador `--json` para recuperar datos con programación. Por ejemplo, para devolver un objeto JSON listando el número, título y estado de capacidad de fusión de las solicitudes de cambios: ```bash gh pr list --json number,title,mergeStateStatus ``` -If there is not a core command to fetch specific data from GitHub, you can use the [`gh api`](https://cli.github.com/manual/gh_api) command to access the GitHub API. For example, to fetch information about the current user: +Si no hay un comando nuclear para recuperar datos específicos de GitHub, puedes utilizar el comando [`gh api`](https://cli.github.com/manual/gh_api) para acceder a la API de GitHub. Por ejemplo, para recuperar información sobre el usuario actual: ```bash gh api user ``` -All commands that output JSON data also have options to filter that data into something more immediately usable by scripts. For example, to get the current user's name: +Todos los comandos que emiten datos de JSON también tiene opciones para filtrar estos datos hacia algo más inmediatamente útil mediante scripts. Por ejemplo, para obtener el nombre del usuario actual: ```bash gh api user --jq '.name' ``` -For more information, see [`gh help formatting`](https://cli.github.com/manual/gh_help_formatting). +Para obtener más información, consulta [`gh help formatting`](https://cli.github.com/manual/gh_help_formatting). ## Pasos siguientes -To see more examples of {% data variables.product.prodname_cli %} extensions, look at [repositories with the `gh-extension` topic](https://github.com/topics/gh-extension). +Para ver más ejemplos de extensiones de {% data variables.product.prodname_cli %}, revisa el [tema de repositorios con la `gh-extension`](https://github.com/topics/gh-extension). diff --git a/translations/es-ES/content/github-cli/github-cli/github-cli-reference.md b/translations/es-ES/content/github-cli/github-cli/github-cli-reference.md index c6672ce628..54ea811842 100644 --- a/translations/es-ES/content/github-cli/github-cli/github-cli-reference.md +++ b/translations/es-ES/content/github-cli/github-cli/github-cli-reference.md @@ -1,6 +1,6 @@ --- -title: GitHub CLI reference -intro: 'You can view all of the {% data variables.product.prodname_cli %} commands in your terminal or in the {% data variables.product.prodname_cli %} manual.' +title: Referencia del CLI de GitHub +intro: 'Puedes ver todos los comandos de {% data variables.product.prodname_cli %} en tu terminal o en el manual del {% data variables.product.prodname_cli %}.' versions: fpt: '*' ghes: '*' @@ -10,19 +10,19 @@ topics: type: reference --- -To view all {% data variables.product.prodname_cli %} commands, see the [{% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_help_reference) or use the `reference` command. +Para ver todos los comandos del {% data variables.product.prodname_cli %}, consulta el [manual del {% data variables.product.prodname_cli %}](https://cli.github.com/manual/gh_help_reference) o utiliza el comando `reference`. ```shell gh reference ``` -To view the environment variables that can be used with {% data variables.product.prodname_cli %}, see the [{% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_help_environment) or use the `environment` command. +Para ver las variables de ambiente que se pueden utilizar con el {% data variables.product.prodname_cli %}, consulta el [manual del {% data variables.product.prodname_cli %}](https://cli.github.com/manual/gh_help_environment) o utiliza el comando `environment`. ```shell gh environment ``` -To view the configuration settings that can be used with {% data variables.product.prodname_cli %}, see the [{% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_config) or use the `config` command. +Para ver los ajustes de configuración que pueden utilizarse con el {% data variables.product.prodname_cli %}, consulta el [manual del {% data variables.product.prodname_cli %}](https://cli.github.com/manual/gh_config) o utiliza el comando`config`. ```shell gh config diff --git a/translations/es-ES/content/github-cli/github-cli/quickstart.md b/translations/es-ES/content/github-cli/github-cli/quickstart.md index f2ed121071..e92102b775 100644 --- a/translations/es-ES/content/github-cli/github-cli/quickstart.md +++ b/translations/es-ES/content/github-cli/github-cli/quickstart.md @@ -1,6 +1,6 @@ --- -title: GitHub CLI quickstart -intro: 'Start using {% data variables.product.prodname_cli %} to work with {% data variables.product.company_short %} in the command line.' +title: Inicio rápido ára el CLI de GitHub +intro: 'Comienza a utilizar el {% data variables.product.prodname_cli %} para trabajar con {% data variables.product.company_short %} en la línea de comandos.' versions: fpt: '*' ghes: '*' @@ -18,29 +18,29 @@ shortTitle: Inicio Rápido ## Empezar -1. [Install](https://github.com/cli/cli#installation) {% data variables.product.prodname_cli %} on macOS, Windows, or Linux. -1. In the command line, authenticate to {% data variables.product.company_short %}. +1. [Instala](https://github.com/cli/cli#installation) el {% data variables.product.prodname_cli %} en macoS, Windows o Linux. +1. En la línea de comandos, autentícate en {% data variables.product.company_short %}. ```shell gh auth login ``` {% ifversion not fpt %} - To authenticate to {% data variables.product.product_location %}, use the `--hostname` flag. + Para autenticarte en {% data variables.product.product_location %}, utiliza el marcador `--hostname`. ```shell gh auth login --hostname hostname ``` {% endif %} -1. Start working with {% data variables.product.company_short %} in the command line. For example, find an issue to work on with `gh issue status` or `gh issue list --assignee @me`. Create a pull request with `gh pr create`. Review a pull request with `gh pr checkout`, `gh pr diff` and `gh pr review`. +1. Comienza a trabajar con {% data variables.product.company_short %} en la línea de comandos. Por ejemplo, encuentra una propuesta en la cuál trabajar con `gh issue status` o `gh issue list --assignee @me`. Crea una solicitud de cambios con `gh pr create`. Revisa una solcitud de cambios con `gh pr checkout`, `gh pr diff` y `gh pr review`. ## Pasos siguientes -- Tell {% data variables.product.prodname_cli %} which text editor to use for commands that open a text editor. For example, enter `gh config set editor "code -w"` to set your preferred text editor to {% data variables.product.prodname_vscode %}. For more information, see [`gh config set`](https://cli.github.com/manual/gh_config_set). +- Indica al {% data variables.product.prodname_cli %} qué editor de texto utilizar para los comandos que abran un editor de texto. Por ejemplo, ingresa `gh config set editor "code -w"` para configurar a {% data variables.product.prodname_vscode %} como tu editor de texto preferido. Para obtener más información, consulta la sección [`gh config set`](https://cli.github.com/manual/gh_config_set). -- Define aliases for commands that you commonly run. For example, if you run `gh alias set prd "pr create --draft"`, you will then be able to run `gh prd` to quickly open a draft pull request. For more information, see [`gh alias`](https://cli.github.com/manual/gh_alias). +- Define los alias para los comandos que ejecutas comunmente. Por ejemplo, si ejecutas `gh alias set prd "pr create --draft"`, entonces podrás ejecutar `gh prd` para abrir un borrador de solicitud de cambios rápidamente. Para obtener más información, consulta el comando [`gh alias`](https://cli.github.com/manual/gh_alias). -- Create or add custom commands with {% data variables.product.prodname_cli %} extensions. For more information, see "[Using {% data variables.product.prodname_cli %} extensions](/github-cli/github-cli/using-github-cli-extensions)" and "[Creating {% data variables.product.prodname_cli %} extensions](/github-cli/github-cli/creating-github-cli-extensions)." +- Crea o agrega comandos personalizados con las extensiones de {% data variables.product.prodname_cli %}. Para obtener más información, consulta las seciones "[Utilizar las extensiones del {% data variables.product.prodname_cli %}](/github-cli/github-cli/using-github-cli-extensions)" y "[Crear extensiones del {% data variables.product.prodname_cli %}](/github-cli/github-cli/creating-github-cli-extensions)". -- For more information about all of the commands that you can run with {% data variables.product.prodname_cli %}, see "[{% data variables.product.prodname_cli %} reference](/github-cli/github-cli/github-cli-reference)." +- Para obtener más información sobre todos los comandos que puedes ejecutar con el {% data variables.product.prodname_cli %}, consulta la sección "[referencia del {% data variables.product.prodname_cli %}](/github-cli/github-cli/github-cli-reference)". diff --git a/translations/es-ES/content/github-cli/github-cli/using-github-cli-extensions.md b/translations/es-ES/content/github-cli/github-cli/using-github-cli-extensions.md index 27a2bc54fc..dfb769f023 100644 --- a/translations/es-ES/content/github-cli/github-cli/using-github-cli-extensions.md +++ b/translations/es-ES/content/github-cli/github-cli/using-github-cli-extensions.md @@ -1,6 +1,6 @@ --- -title: Using GitHub CLI extensions -intro: 'Learn how to use custom extensions written by other {% data variables.product.prodname_cli %} users.' +title: Utilizar las extensiones del CLI de GitHub +intro: 'Aprende cómo utilizar extensiones personalizadas que escriben otros usuarios de {% data variables.product.prodname_cli %}.' versions: fpt: '*' ghes: '*' @@ -9,61 +9,61 @@ topics: - CLI --- -## About {% data variables.product.prodname_cli %} extensions +## Acerca de las extensiones del {% data variables.product.prodname_cli %} {% note %} -**Note:** Extensions outside of {% data variables.product.product_name %} and {% data variables.product.prodname_cli %} are not certified by {% data variables.product.product_name %} and are governed by separate terms of service, privacy policy, and support documentation. To mitigate risk when using third-party extensions, audit the source code of the extension before installing or updating the extension. +**Nota:** Las extensiones fuera de {% data variables.product.product_name %} y {% data variables.product.prodname_cli %} no están certificadas por {% data variables.product.product_name %} y se rigen por términos de servicio, políticas de privacidad y documentación de soporte distintas. Para mitigar el riesgo al utilizar extensiones de terceros, audita el código fuente de la extensión antes de instalarla o actualizarla. {% endnote %} -{% data reusables.cli.cli-extensions %} For more information about how to create {% data variables.product.prodname_cli %} extensions, see "[Creating {% data variables.product.prodname_cli %} extensions](/github-cli/github-cli/creating-github-cli-extensions)." +{% data reusables.cli.cli-extensions %} Para obtener más información sobre cómo crear extensiones de {% data variables.product.prodname_cli %}, consulta la sección "[Crear extensiones de {% data variables.product.prodname_cli %}](/github-cli/github-cli/creating-github-cli-extensions)". -Extensions are locally installed and are scoped to the user. Therefore, if you access {% data variables.product.prodname_cli %} from a different machine or another user accesses {% data variables.product.prodname_cli %} from the same machine, the extension will not be available. +Las extensiones se instalan localmente y se les da el alcance del usuario. Por lo tanto, si accedes al {% data variables.product.prodname_cli %} desde una máquina diferente o si otro usuario accede al {% data variables.product.prodname_cli %} desde la misma máquina, la extensión no estará disponible. -## Finding extensions +## Encontrar extensiones -You can find extensions by browsing [repositories with the `gh-extension` topic](https://github.com/topics/gh-extension). +Puedes encontrar extensiones si buscas los [repositorios con el tema `gh-extension`](https://github.com/topics/gh-extension). -## Installing extensions +## Instalar extensiones -To install an extension, use the `extensions install` subcommand. Replace the `repo` parameter with the repository of the extension. You can use the full URL, such as `https://github.com/octocat/gh-whoami`, or just the owner and repository, such as `octocat/gh-whoami`. +Para instalar una extensión, utiliza el subcomando `extensions install`. Reemplaza el parámetro `repo` con el repositorio de la extensión. Puedes utilizar la URL completa, tal como `https://github.com/octocat/gh-whoami`, o solo el propietario y repositorio, tal como `octocat/gh-whoami`. -If the owner and repository are used, `gh` will install the extension using the hostname to which `gh` is currently authenticated. The full URL format is useful when installing extensions from a different host. For example, users on {% data variables.product.prodname_ghe_server %} should use the full repository URL to install extensions from {% data variables.product.prodname_dotcom_the_website %} or any other host. +Si se utiliza el propietario y repositorio, `gh` instalará la extensión utilizando el nombre de host en el cual está autenticado `gh`. El formato de URL completa es útil cuando se instalan extensiones desde un host diferente. Por ejemplo, los usuarios de {% data variables.product.prodname_ghe_server %} deben utilizar la URL completa del repositorio para instalar extensiones de {% data variables.product.prodname_dotcom_the_website %} o de cualquier otro host. -To install an extension in development from the current directory, use `.` as the value for the `repo` parameter. +Para instalar una extensión en desarrollo desde el directorio actual, utiliza `.` como el valor para el parámetro `repo`. ```shell gh extension install repo ``` -If you already have an extension by the same name installed, the command will fail. For example, if you have installed `octocat/gh-whoami`, you must uninstall it before installing `hubot/gh-whoami`. +Si ya tienes una extensión con el mismo nombre instalada, el comando fallará. Por ejemplo, si instalaste `octocat/gh-whoami`, debes desinstalarlo antes de instalar `hubot/gh-whoami`. -## Viewing installed extensions +## Ver las extensiones instaladas -To view all installed extensions, use the `extensions list` subcommand. The output will also tell you which extensions have updates available. +Para ver las extensiones instaladas, utiliza el subcomando `extensions list`. La salida también te dirá qué extensiones tienen actualizaciones disponibles. ```shell gh extension list ``` -## Updating extensions +## Actualizar las extensiones -To update an extension, use the `extensions upgrade` subcommand. Replace the `extension` parameter with the name of the extension. +Para actualizar una extensión, utiliza el subcomando `extensions upgrade`. Reemplaza el parámetro `extension` con el nombre de la extensión. ```shell gh extension upgrade extension ``` -To update all installed extensions, use the `--all` flag. +Para actualizar todas las extensiones instaladas, utiliza el marcador `--all`. ```shell gh extension upgrade --all ``` -## Uninstalling extensions +## Desinstalar las extensiones -To uninstall an extension, use the `extensions remove` subcommand. Replace the `extension` parameter with the name of the extension. +Para desinstalar una extensión, utiliza el subcomando `extensions remove`. Reemplaza al parámetro `extension` con el nombre de la extensión. ```shell gh extension remove extension diff --git a/translations/es-ES/content/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md b/translations/es-ES/content/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md index 6c8b3d8fc5..43dd0c1243 100644 --- a/translations/es-ES/content/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md +++ b/translations/es-ES/content/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md @@ -31,7 +31,7 @@ Hay dos tipos de verificaciones de estado en {% data variables.product.product_n - Verificaciones - Estados -_Checks_ are different from _statuses_ in that they provide line annotations, more detailed messaging, and are only available for use with {% data variables.product.prodname_github_apps %}. +Las _verificaciones_ son diferentes de los _estados_, porque brindan anotaciones por línea, mensajes más detallados y solo están disponibles para el uso con {% data variables.product.prodname_github_apps %}. Los propietarios de la organización y los usuarios con acceso de escritura a un repositorio pueden crear verificaciones y estados con la API de {% data variables.product.product_name %}. Para obtener más información, consulta la secciónes "[Verificaciones](/rest/reference/checks)" y "[Estados](/rest/reference/repos#statuses)". @@ -41,6 +41,12 @@ Cuando se configuran las _verificaciones_ en un repositorio, las solicitudes de ![Verificaciones de estado dentro de una solicitud de extracción](/assets/images/help/pull_requests/checks.png) +{% note %} + +**Note:** The **Checks** tab only gets populated for pull requests if you set up _checks_, not _statuses_, for the repository. + +{% endnote %} + Cuando una línea específica en una confirmación hace que una verificación falle, verás los detalles acerca de la falla, adevertencia o aviso al lado del código relevante en la pestaña **Archivos** de la solicitud de extracción. ![Detalles de una verificación de estado](/assets/images/help/pull_requests/checks-detailed.png) diff --git a/translations/es-ES/content/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md b/translations/es-ES/content/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md index 8f36491110..85ef2bae9b 100644 --- a/translations/es-ES/content/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md +++ b/translations/es-ES/content/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md @@ -77,15 +77,15 @@ Si decides que no deseas que los cambios en una rama de tema se fusionen con la {% data reusables.cli.cli-learn-more %} -To merge a pull request, use the `gh pr merge` subcommand. Replace `pull-request` with the number, URL, or head branch of the pull request. +Para fusionar una solicitud de cambios, utiliza el subcomando `gh pr merge`. Reemplaza a `pull-request` con el número, URl o rama de encabezado de la solicitud de cambios. ```shell gh pr merge pull-request ``` -Follow the interactive prompts to complete the merge. For more information about the merge methods that you can choose, see "[About pull request merges](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)." +Sigue los mensajes interactivos para completar la fusión. Para obtener más información sobre los métodos de fusión que puedes elegir, consulta la sección "[Acerca de las fusiones de solicitudes de cambios](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)". -Alternatively, you can use flags to skip the interactive prompts. For example, this command will squash the commits into a single commit with the commit message "my squash commit", merge the squashed commit into the base branch, and then delete the local and remote branch. +Como alternativa, puedes utilizar marcadores para omitir los mensajes interactivos. Por ejemplo, este comando combinará las confirmaciones en una sola con el mensaje de confirmación "my squash commit", fusiona la confirmación combinada en la rama base y luego borra la rama local y remota. ```shell gh pr merge 523 --squash --body "my squash commit" --delete-branch diff --git a/translations/es-ES/content/github/collaborating-with-pull-requests/index.md b/translations/es-ES/content/github/collaborating-with-pull-requests/index.md index ebea642733..28191f919c 100644 --- a/translations/es-ES/content/github/collaborating-with-pull-requests/index.md +++ b/translations/es-ES/content/github/collaborating-with-pull-requests/index.md @@ -22,6 +22,6 @@ children: - /addressing-merge-conflicts - /reviewing-changes-in-pull-requests - /incorporating-changes-from-a-pull-request -shortTitle: Collaborate with pull requests +shortTitle: Colaborar con las solicitudes de cambios --- diff --git a/translations/es-ES/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md b/translations/es-ES/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md index 1885a58058..2753475246 100644 --- a/translations/es-ES/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md +++ b/translations/es-ES/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md @@ -24,7 +24,7 @@ topics: {% endnote %} -You can create pull requests on {% data variables.product.prodname_dotcom_the_website %}, with {% data variables.product.prodname_desktop %}, in {% data variables.product.prodname_codespaces %}, on {% data variables.product.prodname_mobile %}, and when using GitHub CLI. +Puedes crear solicitudes de cambios en {% data variables.product.prodname_dotcom_the_website %}, con {% data variables.product.prodname_desktop %}, en {% data variables.product.prodname_codespaces %}, en {% data variables.product.prodname_mobile %} y cuando utilizas el CLI de GitHub. Después de inicializar una solicitud de extracción, verás una página de revisión que muestra una descripción general de alto nivel de los cambios entre tu rama (la rama de comparación) y la rama base del repositorio. Puedes agregar un resumen de los cambios propuestos, revisar los cambios hechos por las confirmaciones, agregar etiquetas, hitos y asignatarios, y hacer @mención de equipos o colaboradores individuales. Para obtener más información, consulta "[Crear una solicitud de extracción](/articles/creating-a-pull-request)". diff --git a/translations/es-ES/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork.md b/translations/es-ES/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork.md index 024ebadb67..fe5233b8bf 100644 --- a/translations/es-ES/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork.md +++ b/translations/es-ES/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork.md @@ -5,7 +5,7 @@ redirect_from: - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork - /articles/creating-a-pull-request-from-a-fork - /github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork -permissions: Anyone with write access to a repository can create a pull request from a user-owned fork. +permissions: 'Anyone with write access to a repository can create a pull request from a user-owned fork. {% data reusables.enterprise-accounts.emu-permission-propose %}' versions: fpt: '*' ghes: '*' diff --git a/translations/es-ES/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md b/translations/es-ES/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md index 4d7b4f4f7e..122b7f078d 100644 --- a/translations/es-ES/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md +++ b/translations/es-ES/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md @@ -1,6 +1,7 @@ --- title: Crear una solicitud de extracción intro: 'Crea una solicitud de extracción para proponer y colaborar en los cambios en un repositorio. Estos cambios se proponen en una *rama*, lo cual garantiza que la rama predeterminada contenga únicamente trabajo finalizado y aprobado.' +permissions: 'Anyone with read access to a repository can create a pull request. {% data reusables.enterprise-accounts.emu-permission-propose %}' redirect_from: - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request - /articles/creating-a-pull-request @@ -13,7 +14,7 @@ topics: - Pull requests --- -Todo usuario que tenga permisos de lectura para un repositorio puede crear una solicitud de extracción, pero tú debes tener permisos de escritura para poder crear una rama. Si deseas crear una rama nueva para tu solicitud de extracción y no tienes permisos de escritura para el repositorio, puedes bifurcar antes el repositorio. Para obtener más información, consulta "[Crear una solicitud de extracción a partir de una bifurcación](/articles/creating-a-pull-request-from-a-fork)" y " +Si deseas crear una rama nueva para tu solicitud de extracción y no tienes permisos de escritura para el repositorio, puedes bifurcarlo primero. Para obtener más información, consulta "[Crear una solicitud de extracción a partir de una bifurcación](/articles/creating-a-pull-request-from-a-fork)" y " [Acerca de las bifurcaciones](/articles/about-forks)".

    Puedes especificar en qué rama deseas fusionar tus cambios cuando creas tu solicitud de extracción. Las solicitudes de extracción solo se pueden abrir entre dos ramas que sean diferentes. @@ -200,13 +201,13 @@ gh pr create --web {% codespaces %} -1. Once you've committed changes to your local copy of the repository, click the **Create Pull Request** icon. ![Barra lateral de control de código fuente con el botón de preparación resaltado](/assets/images/help/codespaces/codespaces-commit-pr-button.png) +1. Una vez que confirmaste los cambios en tu copia local del repositorio, haz clic en el icono de **Crear Solicitud de Cambios**. ![Barra lateral de control de código fuente con el botón de preparación resaltado](/assets/images/help/codespaces/codespaces-commit-pr-button.png) 1. Verifica que el repositorio y la rama local desde la que estás haciendo la fusión y la rama y repositorio remotos hacia los que estés haciendo la fusión sean correctos. Después, asigna un nombre y descripción a la solicitud de cambios. ![Barra lateral de control de código fuente con el botón de preparación resaltado](/assets/images/help/codespaces/codespaces-commit-pr.png) 1. Da clic en **Crear**. -For more information on creating pull requests in {% data variables.product.prodname_codespaces %}, see "[Using Codespaces for pull requests](/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests)." +Para obtener más información sobre cómo crear solicitudes de cambios en {% data variables.product.prodname_codespaces %}, consulta la sección "[Utilizar los Codespaces para solicitudes de cambios](/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests)". {% endcodespaces %} diff --git a/translations/es-ES/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md b/translations/es-ES/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md index 1a7d65ec2f..c230495f8d 100644 --- a/translations/es-ES/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md +++ b/translations/es-ES/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md @@ -39,7 +39,7 @@ shortTitle: Verificar una solicitud de cambios localmente {% data reusables.cli.cli-learn-more %} -To check out a pull request locally, use the `gh pr checkout` subcommand. Replace `pull-request` with the number, URL, or head branch of the pull request. +Para verificar una solicitud de cambios localmente, utiliza el subcomando `gh pr checkout`. Reemplaza la `pull-request` con el número, URL o rama de encabezado de la solicitud de cambios. ```shell gh pr checkout pull-request diff --git a/translations/es-ES/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/translations/es-ES/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md index ee8aa32e98..44a083ed1b 100644 --- a/translations/es-ES/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md +++ b/translations/es-ES/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md @@ -1,10 +1,10 @@ --- title: Revisar los cambios de las dependencias en una solicitud de cambios intro: 'Si una solicitud de cambios contiene cambios a las dependencias, puedes ver un resumen de lo que ha cambiado y si es que existen vulnerabilidades conocidas en cualquiera de estas dependencias.' +product: '{% data reusables.gated-features.dependency-review %}' versions: fpt: '*' ghes: '>= 3.2' - product: '{% data reusables.gated-features.dependency-review %}' type: how_to topics: - Pull requests @@ -26,7 +26,7 @@ shortTitle: Revisar los cambios de dependencia {% data reusables.dependency-review.feature-overview %} -{% ifversion ghes > 3.1 %} Before you can use dependency review, you must enable the dependency graph and connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta la sección "[Habilitar las alertas para las dependencias vulnerables en {% data variables.product.prodname_ghe_server %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)".{% endif %} +{% ifversion ghes > 3.1 %} Antes de que puedas utilizar la revisión de dependencias, debes habilitar la gráfica de dependencias y conectar {% data variables.product.product_location %} a {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta la sección "[Habilitar las alertas para las dependencias vulnerables en {% data variables.product.prodname_ghe_server %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)".{% endif %} La revisión de dependencias te permite "desplazarte a la izquierda". Puedes utilizar la información predictiva que se te proporciona para detectar dependencias vulnerables antes de que lleguen a tu ambiente productivo. 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)". @@ -38,19 +38,19 @@ La revisión de dependencias te permite "desplazarte a la izquierda". Puedes uti 1. Si la solicitud de cambios contiene muchos archivos, utiliza el menú desplegable de **Filtro de archivos** para que colapse todos los archivos que no registran dependencias. Esto facilitará que te enfoques en tu revisión de cambios a las dependencias. - ![El menú de filtro de archivo](/assets/images/help/pull_requests/file-filter-menu-json.png) + ![El menú de filtro de archivo](/assets/images/help/pull_requests/file-filter-menu-json.png) La revisión de dependencias proporciona una vista más clara de lo que ha cambiado en los archivos de bloqueo grandes, donde la diff origen no se representa predeterminadamente. + + {% note %} + + **Nota:** Los diffs enriquecidos de la revisión de dependencias no están disponibles para los archivos de JavaScript estáticos confirmados como `jquery.js`. + + {% endnote %} 1. A la derecha del encabezado de un archivo de bloqueo o de manifiesto, muestra la revisión de dependencias dando clic en el botón de diff enriquecido **{% octicon "file" aria-label="The rich diff icon" %}**. ![El botón de diff rica](/assets/images/help/pull_requests/dependency-review-rich-diff.png) - {% note %} - - **Nota:** La revisión de dependencias proporciona una vista más clara de lo que ha cambiado en los archivos de bloqueo grandes, donde la diff origen no se representa predeterminadamente. - - {% endnote %} - -1. Verifica las dependencias que se listan en la revisión de dependencias. +2. Verifica las dependencias que se listan en la revisión de dependencias. ![Alertas de vulnerabilidades en una revisión de dependencias](/assets/images/help/pull_requests/dependency-review-vulnerability.png) diff --git a/translations/es-ES/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md b/translations/es-ES/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md index 3625436608..9b6b983b49 100644 --- a/translations/es-ES/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md +++ b/translations/es-ES/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md @@ -43,11 +43,11 @@ Antes de enviar tu revisión, tus comentarios de líneas quedan _pendientes_, y {% codespaces %} -You can use [{% data variables.product.prodname_codespaces %}](/codespaces/overview) to test, run, and review pull requests. +Puedes utilizar los [{% data variables.product.prodname_codespaces %}](/codespaces/overview) para probar, ejecutar y revisar las solicitudes de cambios. {% data reusables.codespaces.review-pr %} -For more information on reviewing pull requests in {% data variables.product.prodname_codespaces %}, see "[Using Codespaces for pull requests](/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests)." +Para obtener más información sobre revisar las solicitudes de cambios en los {% data variables.product.prodname_codespaces %}, consulta la sección "[Utilizar los Codespaces para las solicitudes de cambios](/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests)". {% endcodespaces %} {% endif %} diff --git a/translations/es-ES/content/github/collaborating-with-pull-requests/working-with-forks/about-forks.md b/translations/es-ES/content/github/collaborating-with-pull-requests/working-with-forks/about-forks.md index d211e852cc..2942937ceb 100644 --- a/translations/es-ES/content/github/collaborating-with-pull-requests/working-with-forks/about-forks.md +++ b/translations/es-ES/content/github/collaborating-with-pull-requests/working-with-forks/about-forks.md @@ -20,6 +20,12 @@ Bifurcar un repositorio es similar a copiar un repositorio, con dos diferencias {% data reusables.repositories.you-can-fork %} +{% ifversion fpt %} + +Si eres un miembro de una {% data variables.product.prodname_emu_enterprise %}, hay más restricciones sobre los repositorios que puedes bifurcar. {% data reusables.enterprise-accounts.emu-forks %} Para ver más información, consulta la sección "[Acerca de las {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)". + +{% endif %} + {% data reusables.repositories.desktop-fork %} Eliminar una bifurcación no eliminará el repositorio ascendente original. Puedes hacer tantos cambios como quieras a tu bifurcación—añadir colaboradores, renombrar archivos, generar {% data variables.product.prodname_pages %}—sin que esto afecte el repositorio original.{% ifversion fpt %} no puedes restablecer un repositorio bifurcado previamente eliminado. Para obtener más información, consulta "[Restaurar un repositorio eliminado](/articles/restoring-a-deleted-repository)".{% endif %} diff --git a/translations/es-ES/content/github/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md b/translations/es-ES/content/github/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md index fa5ff12f43..7174ee6d08 100644 --- a/translations/es-ES/content/github/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md +++ b/translations/es-ES/content/github/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md @@ -52,4 +52,4 @@ Si tu configuración de Git local contiene una dirección de correo electrónico ## Leer más -* "[Buscar confirmaciones](/articles/searching-commits)" +* "[Buscar confirmaciones](/search-github/searching-on-github/searching-commits)" diff --git a/translations/es-ES/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views.md b/translations/es-ES/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views.md index d87a42a074..54f7e883be 100644 --- a/translations/es-ES/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views.md +++ b/translations/es-ES/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views.md @@ -29,4 +29,4 @@ Para obtener más información acerca de cómo Git considera el historial de con ## Leer más - "[Firmar confirmaciones](/articles/signing-commits)" -- "[Buscar confirmaciones](/articles/searching-commits)" +- "[Buscar confirmaciones](/search-github/searching-on-github/searching-commits)" 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 f6096927ff..0dd98cbf0e 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 @@ -1,6 +1,6 @@ --- title: Acerca de la telemetría del Copiloto de GitHub -intro: 'El Copiloto de {% data variables.product.prodname_dotcom %} recolecta y confía en datos de telemetría adicionales más allá de lo que recolectan otros productos y servicios de {% data variables.product.prodname_dotcom %}.' +intro: 'El {% data variables.product.prodname_copilot %} recolecta y confía en datos de telemetría adicionales más allá de lo que recolectan otros productos y servicios de {% data variables.product.company_short %}.' redirect_from: - /early-access/github/copilot/about-github-copilot-telemetry versions: @@ -8,36 +8,21 @@ versions: --- ## Qué datos se recolectan -El Copiloto de {% data variables.product.prodname_dotcom %} recolecta la actividad del editor de Visual Studio Code del usuario, lo liga con una marca de tiempo y con metadatos. Estos metadatos consisten en la extensión de ajustes y de los metadatos estándar que recolecta el [Paquete extendido de telemetría de Visual Studio Code](https://www.npmjs.com/package/vscode-extension-telemetry): -* ID de máquina de Visual Studio Code (identificador pseudonimizado) -* ID de sesión de Visual Studio Code (Identificador Pseudonimizado) -* Versión de Visual Studio Code -* [Geoubicación desde la dirección IP](https://docs.microsoft.com/en-us/azure/azure-monitor/app/ip-collection?tabs=net) (país, estado/provincia y ciudad, pero no la dirección IP misma) -* Sistema operativo y versión -* Versión de extensión -* La IU de VS Code (web o escritorio) +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. -La actividad que se recolecta consiste en eventos que se activan cuando: +## Cómo {% data variables.product.company_short %} utiliza los datos -* Ocurre un error (graba el tipo de error y el fondo relevante; por ejemplo, si es un error de autenticación, se graba la fecha de vencimiento de la llave) -* Se accede a nuestros modelos para pedir sugerencias de código (este graba el estado del editor como la posición del cursor y los fragmentos de código); esto incluye los casos en los que el usuario toma una acción para solicitar las sugerencias de código -* Las sugerencias de código se reciben o se muestran (se graban las sugerencias, post-procesamiento y metadatos como la certeza y latencia del modelo) -* Se redactan las sugerencias de código debido a los filtros que garantizan la seguridad de la IA -* El usuario actúa de acuerdo a las sugerencias de código (por ejemplo, para aceptarlas o rechazarlas) -* El usuario actuó de acuerdo con las sugerencias de código y luego registra si o cómo persistieron en este +{% data variables.product.company_short %} utilizará estos datos para: -## Cómo se utilizan lso datos -{% data variables.product.company_short %} solo utilizará estos datos para: - -* Mejorar directamente el producto, incluyendo la valoración de estrategias diversas para procesar y predecir las sugerencias que los usuarios podrían encontrar útiles -* Evaluar el producto directamente, por ejemplo, midiendo el impacto positivo que tiene en el usuario -* Mejorr los modelos de generación de código subyacentes, por ejemplo, proporcionando ejemplos positivos y negativos (pero siempre de tal forma que tu código privado no se utilice como entrada para sugerir código para otros usuarios del Copiloto de {% data variables.product.prodname_dotcom %}) -* Para guiar productos relacionados cercanamente con {% data variables.product.prodname_dotcom %} -* Investigando y detectando el abuso potencial del servicio del Copiloto de {% data variables.product.prodname_dotcom %} -* Otros propósitos relacionados con la mejora del servicio de Copiloto de {% data variables.product.prodname_dotcom %} +- Mejorar directamente el producto, incluyendo la valoración de estrategias diversas para procesar y predecir las sugerencias que los usuarios podrían encontrar útiles +- Evaluar el producto, por ejemplo, midiendo el impacto positivo que tiene en el usuario +- Mejorar los modelos de generación de código subyacentes, por ejemplo, proporcionando ejemplos positivos y negativos (pero siempre de tal forma que tu código privado no se utilice como entrada para sugerir código para otros usuarios del {% data variables.product.prodname_copilot %}) +- Para guiar productos relacionados cercanamente con {% data variables.product.company_short %} +- Investigando y detectando el abuso potencial del servicio del {% data variables.product.prodname_copilot %} +- Otros propósitos relacionados con mejorar el servicio del {% data variables.product.prodname_copilot %}, incluyendo el poder compartir, de acuerdo a como se describe en la siguiente sección ## Cómo se comparten los datos -Los datos de telemetría se almacenan de forma segura en los sistemas de {% data variables.product.prodname_dotcom %} con el cifrado adecuado implementado. -Sabemos que las acciones que editan los usuarios y los fragmentos de código fuente son datos muy sensibles y que el acceso se controla estrictamente. Solo las siguientes entidades pueden acceder a los datos: (1) personal denominado de {% data variables.product.company_short %} (empleados y contratistas) que trabajen en el equipo copiloto de {% data variables.product.company_short %} o en el equipo de salud de la plataforma de {% data variables.product.company_short %}, (2) personal selecto de Microsoft (empleados y contratistas) que trabajen en o con el equipo copiloto de {% data variables.product.company_short %} y (3), empleados selectos de OpenAI que trabajen en el copiloto de {% data variables.product.company_short %}. +Los datos de telemetría se almacenan de forma segura en los sistemas de {% data variables.product.company_short %} con el cifrado adecuado implementado. Sabemos que las acciones que editan los usuarios, los fragmentos de código fuente y las URL de los repositorios, así como las rutas de archivos, son datos sensibles. Consequently, access is strictly controlled. The data can only be accessed by (1) named {% data variables.product.company_short %} personnel (employees and contractors) working on the {% data variables.product.prodname_copilot %} team or on the {% data variables.product.company_short %} platform health team, (2) Microsoft personnel (employees and contractors) working on or with the Azure and/or {% data variables.product.prodname_copilot %} teams, and (3) employees of OpenAI who work on {% data variables.product.prodname_copilot %}. + diff --git a/translations/es-ES/content/github/copilot/github-copilot-telemetry-terms.md b/translations/es-ES/content/github/copilot/github-copilot-telemetry-terms.md new file mode 100644 index 0000000000..5d9fedb1f0 --- /dev/null +++ b/translations/es-ES/content/github/copilot/github-copilot-telemetry-terms.md @@ -0,0 +1,16 @@ +--- +title: GitHub Copilot Telemetry Terms +intro: 'Acceptance of the additional telemetry described below is a condition to joining the wait list for the technical preview of {% data variables.product.prodname_copilot %} and using {% data variables.product.prodname_copilot %} during the technical preview.' +redirect_from: + - /early-access/github/copilot/telemetry-terms + - /github/copilot/telemetry-terms +versions: + fpt: '*' +--- + +## Telemetría adicional + +If you use {% data variables.product.prodname_copilot %}, the {% data variables.product.prodname_copilot %} extension/plugin will collect usage information about events generated by interacting with the integrated development environment (IDE). These events include {% data variables.product.prodname_copilot %} performance, features used, and suggestions accepted, modified and accepted, or dismissed. This information may include personal data, including your User Personal Information, as defined in the [GitHub Privacy Statement](/github/site-policy/github-privacy-statement). + +This usage information is used by {% data variables.product.company_short %}, and shared with Microsoft and OpenAI, to develop and improve the extension/plugin and related products. OpenAI also uses this usage information to perform other services related to {% data variables.product.prodname_copilot %}. For example, when you edit files with the {% data variables.product.prodname_copilot %} extension/plugin enabled, file content snippets, suggestions, and any modifications to suggestions will be shared with {% data variables.product.company_short %}, Microsoft, and OpenAI, and used for diagnostic purposes to improve suggestions and related products. {% data variables.product.prodname_copilot %} relies on file content for context, both in the file you are editing and potentially other files open in the same IDE instance. When you are using {% data variables.product.prodname_copilot %}, it may also collect the URLs of repositories or file paths for relevant files. {% data variables.product.prodname_copilot %} does not use these URLs, file paths, or snippets collected in your telemetry as input to suggest code for other users of {% data variables.product.prodname_copilot %}. This information is treated as confidential information and accessed on a need-to-know basis. You are prohibited from collecting telemetry data about other users of {% data variables.product.prodname_copilot %} from the {% data variables.product.prodname_copilot %} extension/plugin. For more details about {% data variables.product.prodname_copilot %} telemetry, please see "[About {% data variables.product.prodname_copilot %} telemetry](/github/copilot/about-github-copilot-telemetry)." You may revoke your consent to the telemetry and personal data processing operations described in this paragraph by contacting GitHub and requesting removal from the technical preview. + diff --git a/translations/es-ES/content/github/copilot/index.md b/translations/es-ES/content/github/copilot/index.md index 3327512c6c..242e225330 100644 --- a/translations/es-ES/content/github/copilot/index.md +++ b/translations/es-ES/content/github/copilot/index.md @@ -5,7 +5,7 @@ versions: fpt: '*' children: - /about-github-copilot-telemetry - - /telemetry-terms + - /github-copilot-telemetry-terms - /research-recitation --- diff --git a/translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md b/translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md index 3385962580..4bdfd82be1 100644 --- a/translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md +++ b/translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md @@ -8,7 +8,7 @@ versions: fpt: '*' --- -You can discover, browse, and install free and paid tools, including {% data variables.product.prodname_github_apps %}, {% data variables.product.prodname_oauth_apps %}, and {% data variables.product.prodname_actions %}, in [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace). +En [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace), puedes descubrir, buscar e instalar herramientas de pago y gratuitas, incluyendo {% data variables.product.prodname_github_apps %}, {% data variables.product.prodname_oauth_apps %} y {% data variables.product.prodname_actions %}. Si compras una herramienta paga, pagarás por tu suscripción a la herramienta con la misma información de facturación que usas para pagar la suscripción de {% data variables.product.product_name %} y recibirás una factura en tu fecha de facturación regular. Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)". @@ -16,7 +16,7 @@ También puedes tener la opción de seleccionar una prueba gratuita de 14 días ## Encontrar herramientas en {% data variables.product.prodname_marketplace %} -Puedes descubrir, buscar e instalar apps y acciones que otros hayan creado en {% data variables.product.prodname_marketplace %}, consulta la sección "[Buscar en {% data variables.product.prodname_marketplace %}](/github/searching-for-information-on-github/searching-github-marketplace)". +Puedes descubrir, buscar e instalar apps y acciones que otros hayan creado en {% data variables.product.prodname_marketplace %}, consulta la sección "[Buscar en {% data variables.product.prodname_marketplace %}](/search-github/searching-on-github/searching-github-marketplace)". {% data reusables.actions.actions-not-verified %} diff --git a/translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations/about-integrations.md b/translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations/about-integrations.md index c525c5553b..38dbd4ea80 100644 --- a/translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations/about-integrations.md +++ b/translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations/about-integrations.md @@ -8,16 +8,16 @@ versions: fpt: '*' --- -Puedes instalar integraciones en tu cuenta personal o en las organizaciones que posees. You can also install {% data variables.product.prodname_github_apps %} from a third-party in a specific repository where you have admin permissions or which is owned by your organization. +Puedes instalar integraciones en tu cuenta personal o en las organizaciones que posees. También puedes instalar {% data variables.product.prodname_github_apps %} de un tercero en un repositorio específico donde tengas permisos de administrador o que sea propiedad de tu organización. -## Differences between {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %} +## Diferencias entre las {% data variables.product.prodname_github_apps %} y las {% data variables.product.prodname_oauth_apps %} -Integrations can be {% data variables.product.prodname_github_apps %}, {% data variables.product.prodname_oauth_apps %}, or anything that utilizes {% data variables.product.product_name %} APIs or webhooks. +Las integraciones pueden ser {% data variables.product.prodname_github_apps %}, {% data variables.product.prodname_oauth_apps %} o cualquiera que utilice API de {% data variables.product.product_name %} o webhooks. -{% data variables.product.prodname_github_apps %} offer granular permissions and request access to only what the app needs. {% data variables.product.prodname_github_apps %} also offer specific user-level permissions that each user must authorize individually when an app is installed or when the integrator changes the permissions requested by the app. +Las {% data variables.product.prodname_github_apps %} ofrecen permisos granulares y solicitan acceso únicamente a lo que necesita la app. Las {% data variables.product.prodname_github_apps %} también ofrecen un permiso a nivel de usuario que cada uno de estos debe autorizar individualmente cuando se instala la app o cuando el integrador cambia los permisos que solicita la app. Para obtener más información, consulta: -- "[Differences between {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}](/apps/differences-between-apps/)" +- "[Diferencias entre las {% data variables.product.prodname_github_apps %} y las {% data variables.product.prodname_oauth_apps %}](/apps/differences-between-apps/)" - "[Acerca de las apps](/apps/about-apps/)" - "[Permisos a nivel de usario](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-level-permissions)" - "[Autorizar las {% data variables.product.prodname_oauth_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps)" @@ -32,10 +32,10 @@ Puedes crear una {% data variables.product.prodname_github_app %} con configurac Puedes encontrar una integración para instalar o publicar tu propia integración en {% data variables.product.prodname_marketplace %}. -[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) contains {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}. Para obtener más información sobre cómo encontrar una integración o cómo crear tu propia integración, consulta "[Acerca de {% data variables.product.prodname_marketplace %}](/articles/about-github-marketplace)". +[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) contiene a las {% data variables.product.prodname_github_apps %} y las {% data variables.product.prodname_oauth_apps %}. Para obtener más información sobre cómo encontrar una integración o cómo crear tu propia integración, consulta "[Acerca de {% data variables.product.prodname_marketplace %}](/articles/about-github-marketplace)". ## Integraciones compradas directamente a los integradores También puedes comprar algunas integraciones directamente a los integradores. Como miembro de una organización, si encuentras una {% data variables.product.prodname_github_app %} que te gustaría usar, puedes solicitar que una organización apruebe o instale la aplicación para la organización. -If you have admin permissions for all organization-owned repositories the app is installed on, you can install {% data variables.product.prodname_github_apps %} with repository-level permissions without having to ask an organization owner to approve the app. Cuando un integrador cambia los permisos de la aplicación, si los permisos son solo para un repositorio, los propietarios de la organización y las personas con permisos de administrador para un repositorio con esa aplicación instalada pueden revisar y aceptar los nuevos permisos. +Si tienes permisos de administrador para todos los repositorios que son propiedad de una organización en la que la aplicación está instalada, puedes instalar las {% data variables.product.prodname_github_apps %} con los permisos de nivel de repositorio sin tener que solicitar al propietario de la organización que apruebe la aplicación. Cuando un integrador cambia los permisos de la aplicación, si los permisos son solo para un repositorio, los propietarios de la organización y las personas con permisos de administrador para un repositorio con esa aplicación instalada pueden revisar y aceptar los nuevos permisos. diff --git a/translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md b/translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md index bba639a90a..ec0b30c609 100644 --- a/translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md +++ b/translations/es-ES/content/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md @@ -44,8 +44,8 @@ Puedes integrar tu cuenta organizacional o personal de {% data variables.product ### Integración con Slack y con {% data variables.product.product_name %} -You can subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, releases, deployment reviews and deployment statuses. You can also perform activities like close or open issues, and provide rich references to issues and pull requests without leaving Slack. Para obtener más información, visita la [App de integración de Slack](https://github.com/marketplace/slack-github) en Marketplace. +Puedes suscribirte a tus repositorios u organizaciones y obtener actualizaciones en tiempo real sobre propuestas, solicitudes de cambio, confirmaciones, lanzamientos, revisiones y estados de despliegues. También puedes llevar a cabo actividades como cerrar o abrir propuestas y proporcionar referencias enriquecidas para las propuestas y solicitudes de cambios sin salir de Slack. Para obtener más información, visita la [App de integración de Slack](https://github.com/marketplace/slack-github) en Marketplace. ### Microsoft Teams y su integración con {% data variables.product.product_name %} -You can subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, deployment reviews and deployment statuses. You can also perform activities like close or open issues, comment on your issues and pull requests, and provide rich references to issues and pull requests without leaving Microsoft Teams. Para obtener más información, visita la [App de integración de Microsoft Teams](https://appsource.microsoft.com/en-us/product/office/WA200002077) en Microsoft AppsSource. +Puedes suscribirte a tus repositorios u organizaciones y obtener actualizaciones en tiempo real sobre propuestas, solicitudes de cambios, confirmaciones, revisiones y estados de despliegues. También puedes llevar a cabo actividades como cerrar o abrir propuestas, comentar en tus propuestas o solicitudes de cambios y proporcionar referencias enriquecidas para las propuestas y solicitudes de cambios sin salir de Microsoft Teams. Para obtener más información, visita la [App de integración de Microsoft Teams](https://appsource.microsoft.com/en-us/product/office/WA200002077) en Microsoft AppsSource. diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md index 05e17e84b0..f57de592d3 100644 --- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md @@ -42,7 +42,7 @@ En el {% data variables.product.prodname_codeql_workflow %} predeterminado, el { ## Configuración del {% data variables.product.prodname_code_scanning %} por lotes -Puedes configurar el {% data variables.product.prodname_code_scanning %} en muchos repositorios al mismo tiempo utilizando un script. For an example of a script that raises pull requests to add a {% data variables.product.prodname_actions %} workflow to multiple repositories, see the [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) repository for an example using Powershell, or [`nickliffen/ghas-enablement`](https://github.com/NickLiffen/ghas-enablement) for teams who do not have Powershell and instead would like to use NodeJS. +Puedes configurar el {% data variables.product.prodname_code_scanning %} en muchos repositorios al mismo tiempo utilizando un script. Para encontrar un ejemplo de un script que levanta solicitudes de cambio para agregar un flujo de trabajo de {% data variables.product.prodname_actions %} a repositorios múltiples, consulta el repositorio [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) para ver cómo se hace con Powershell o el de [`nickliffen/ghas-enablement`](https://github.com/NickLiffen/ghas-enablement) para los equipos que no tengan Powershell y les gustaría trabajar con NodeJS en su lugar. ## Visualizar la salida de registro del {% data variables.product.prodname_code_scanning %} diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning/about-integration-with-code-scanning.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning/about-integration-with-code-scanning.md index 9b9309ad45..b1dea59ad3 100644 --- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning/about-integration-with-code-scanning.md +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning/about-integration-with-code-scanning.md @@ -22,7 +22,7 @@ Si utilizas una herramienta de análisis estático de terceros que pueda produci ## Integraciones con webhooks -You can use {% data variables.product.prodname_code_scanning %} webhooks to build or set up integrations, such as [{% data variables.product.prodname_github_apps %}](/apps/building-github-apps/) or [{% data variables.product.prodname_oauth_apps %}](/apps/building-oauth-apps/), that subscribe to {% data variables.product.prodname_code_scanning %} events in your repository. Por ejemplo, puedes crear una integración que cree una propuesta en {% data variables.product.product_name %} o que te envíe una notificación de Slack cuando se agregue una alerta de {% data variables.product.prodname_code_scanning %} en tu repositorio. Para obtener más información, consulta las secciones "[Crear webhooks](/developers/webhooks-and-events/creating-webhooks)" y "[Eventos de webhook y cargas útiles](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)". +Puedes utilizar los webhooks del {% data variables.product.prodname_code_scanning %} para crear o configurar integraciones, tales como [{% data variables.product.prodname_github_apps %}](/apps/building-github-apps/) o [{% data variables.product.prodname_oauth_apps %}](/apps/building-oauth-apps/) que se suscriban a los eventos del {% data variables.product.prodname_code_scanning %} en tu repositorio. Por ejemplo, puedes crear una integración que cree una propuesta en {% data variables.product.product_name %} o que te envíe una notificación de Slack cuando se agregue una alerta de {% data variables.product.prodname_code_scanning %} en tu repositorio. Para obtener más información, consulta las secciones "[Crear webhooks](/developers/webhooks-and-events/creating-webhooks)" y "[Eventos de webhook y cargas útiles](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)". ## Leer más diff --git a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning/sarif-support-for-code-scanning.md b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning/sarif-support-for-code-scanning.md index 43040f1941..bf76e51eac 100644 --- a/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning/sarif-support-for-code-scanning.md +++ b/translations/es-ES/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning/sarif-support-for-code-scanning.md @@ -31,7 +31,7 @@ Si SARIF es nuevo para ti y quieres aprender más, consulta el repositorio [`SAR Cada vez que el flujo de trabajo de {{ site.data.variables.product.prodname_actions }} ejecuta un nuevo escaneo de código, los resultados de cada ejecución se procesan y se agregan alertas al repositorio. Para prevenir las alertas duplicadas para el mismo problema, {% data variables.product.prodname_code_scanning %} utiliza huellas dactilares para empatara los resultados a través de diversas ejecuciones para que solo aparezcan una vez en la última ejecución para la rama seleccionada. Esto hace posible empatar las alertas con la línea de código correcta cuando se editan los archivos. -{% data variables.product.prodname_dotcom %} utiliza la propiedad `partialFingerprints` en el estándar OASIS para detectar cuando dos resultados son lógicamente idénticos. Para obtener más información, consulta la sección "[partialFingerprints property](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012611)" en la documentación de OASIS. +{% data variables.product.prodname_dotcom %} uses the `partialFingerprints` property in the OASIS standard as an input in the computation of whether two results are logically identical. Specifically, the `primaryLocationLineHash` is used as a stable intra-file location, which is combined with the repository, file path, and rule data to form the full identity. Para obtener más información, consulta la sección "[partialFingerprints property](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012611)" en la documentación de OASIS. Los archivos SARIF que crea el {% data variables.product.prodname_codeql_workflow %} o los que utilizan el {% data variables.product.prodname_codeql_runner %} incluyen datos de huellas digitales. Si cargas un archivo SARIF utilizando la acción `upload-sarif` y no se encuentran estos datos, {% data variables.product.prodname_dotcom %} intentará poblar el campo `partialFingerprints` desde los archivos de origen. Para obtener más información acerca de cargar los resultados, consulta la sección "[Cargar un archivo SARIF a {% data variables.product.prodname_dotcom %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github#uploading-a-code-scanning-analysis-with-github-actions)". @@ -89,17 +89,17 @@ Puedes cargar cualquier archivo de salida SARIF 2.1.0 válido, sin embargo, {% d {% data reusables.code-scanning.upload-sarif-alert-limit %} -| Nombre | Descripción | -| --------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `ruleId` | **Opcional.** El identificador único de la regla (`reportingDescriptor.id`). Para obtener más información, consulta el [objeto `reportingDescriptor`](#reportingdescriptor-object). {% data variables.product.prodname_code_scanning_capc %} utiliza el identificador de reglas para filtrar los resultados por regla en {% data variables.product.prodname_dotcom %}. | -| `ruleIndex` | **Opcional.** El índice de la regla asociada (`reportingDescriptor` object) en el arreglo de `rules` del componente de la herramienta. Para obtener más información, consulta el [objeto `run`](#run-object). | -| `rule` | **Opcional.** Una referencia que se utiliza para ubicar la regla (descriptor de reporte) para este resultado. Para obtener más información, consulta el [objeto `reportingDescriptor`](#reportingdescriptor-object). | -| `level` | **Opcional.** La severidad del resultado. Este nivel invalida la severidad predeterminada que se define en la regla. {% data variables.product.prodname_code_scanning_capc %} utiliza el nivel para filtrar los resultados en {% data variables.product.prodname_dotcom %} por severidad. | -| `message.text` | **Requerido.** Un mensaje que describe el resultado. {% data variables.product.prodname_code_scanning_capc %} muestra el texto del mensaje como el título del resultado. Se mostrará únicamente la primera oración del mensaje cuando el espacio visible esté limitado. | -| `locations[]` | **Requerido.** El conjunto de ubicaciones donde se detectó el resultado, con un máximo de 10. Sólo se deberá incluir una ubicación a menos de que el problema solo pueda corregirse realizando un cambio en cada ubicación especificada. **Nota:** Se requiere por lo menos una ubicación para que {% data variables.product.prodname_code_scanning %} muestre el resultado. {% data variables.product.prodname_code_scanning_capc %} utilizará esta propiedad para decidir qué archivo anotar con el resultado. Únicamente si se utiliza el primer valor de este arreglo. Se ignorará al resto de los otros valores. | -| `partialFingerprints` | **Requerido.** Un conjunto de secuencias utilizadas para rastrear la identidad única del resultado. {% data variables.product.prodname_code_scanning_capc %} utiliza `partialFingerprints` para identificar con exactitud qué resultados son los mismos a través de las confirmaciones y ramas. {% data variables.product.prodname_code_scanning_capc %} intentará utilizar `partialFingerprints` si es que existe. Si estás cargando un archivo SARIF de terceros con el `upload-action`, la acción creará un `partialFingerprints` para ti cuando no se incluya en el archivo SARIF. Para obtener más información, consulta "[Prevenir alertas duplicadas utilizando huellas dactilares](#preventing-duplicate-alerts-using-fingerprints)". **Nota:** {% data variables.product.prodname_code_scanning_capc %} utilizará únicamente el `primaryLocationLineHash`. | -| `codeFlows[].threadFlows[].locations[]` | **Opcional.** Un arreglo de objetos de `location` para un objeto de `threadFlow`, el cual describe el progreso de un programa a través de un hilo de ejecución. Un objeto de `codeFlow` describe un patrón de ejecución de código que se utiliza para detectar un resultado. Si se proporcionan flujos de código, {% data variables.product.prodname_code_scanning %} los expandirá en {% data variables.product.prodname_dotcom %} para el resultado relevante. Para obtener más información, consulta el [objeto `location`](#location-object). | -| `relatedLocations[]` | Un conjunto de ubicaciones relevantes para el resultado. {% data variables.product.prodname_code_scanning_capc %} vinculará las ubicaciones cuando se incorporen en el mensaje de resultado. Para obtener más información, consulta el [objeto `location`](#location-object). | +| Nombre | Descripción | +| --------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `ruleId` | **Opcional.** El identificador único de la regla (`reportingDescriptor.id`). Para obtener más información, consulta el [objeto `reportingDescriptor`](#reportingdescriptor-object). {% data variables.product.prodname_code_scanning_capc %} utiliza el identificador de reglas para filtrar los resultados por regla en {% data variables.product.prodname_dotcom %}. | +| `ruleIndex` | **Opcional.** El índice de la regla asociada (`reportingDescriptor` object) en el arreglo de `rules` del componente de la herramienta. Para obtener más información, consulta el [objeto `run`](#run-object). | +| `rule` | **Opcional.** Una referencia que se utiliza para ubicar la regla (descriptor de reporte) para este resultado. Para obtener más información, consulta el [objeto `reportingDescriptor`](#reportingdescriptor-object). | +| `level` | **Opcional.** La severidad del resultado. Este nivel invalida la severidad predeterminada que se define en la regla. {% data variables.product.prodname_code_scanning_capc %} utiliza el nivel para filtrar los resultados en {% data variables.product.prodname_dotcom %} por severidad. | +| `message.text` | **Requerido.** Un mensaje que describe el resultado. {% data variables.product.prodname_code_scanning_capc %} muestra el texto del mensaje como el título del resultado. Se mostrará únicamente la primera oración del mensaje cuando el espacio visible esté limitado. | +| `locations[]` | **Requerido.** El conjunto de ubicaciones donde se detectó el resultado, con un máximo de 10. Sólo se deberá incluir una ubicación a menos de que el problema solo pueda corregirse realizando un cambio en cada ubicación especificada. **Nota:** Se requiere por lo menos una ubicación para que {% data variables.product.prodname_code_scanning %} muestre el resultado. {% data variables.product.prodname_code_scanning_capc %} utilizará esta propiedad para decidir qué archivo anotar con el resultado. Únicamente si se utiliza el primer valor de este arreglo. Se ignorará al resto de los otros valores. | +| `partialFingerprints` | **Requerido.** Un conjunto de secuencias utilizadas para rastrear la identidad única del resultado. {% data variables.product.prodname_code_scanning_capc %} uses `partialFingerprints` as part of the computation to accurately identify which results are the same across commits and branches. {% data variables.product.prodname_code_scanning_capc %} intentará utilizar `partialFingerprints` si es que existe. Si estás cargando un archivo SARIF de terceros con el `upload-action`, la acción creará un `partialFingerprints` para ti cuando no se incluya en el archivo SARIF. Para obtener más información, consulta "[Prevenir alertas duplicadas utilizando huellas dactilares](#preventing-duplicate-alerts-using-fingerprints)". **Nota:** {% data variables.product.prodname_code_scanning_capc %} utilizará únicamente el `primaryLocationLineHash`. | +| `codeFlows[].threadFlows[].locations[]` | **Opcional.** Un arreglo de objetos de `location` para un objeto de `threadFlow`, el cual describe el progreso de un programa a través de un hilo de ejecución. Un objeto de `codeFlow` describe un patrón de ejecución de código que se utiliza para detectar un resultado. Si se proporcionan flujos de código, {% data variables.product.prodname_code_scanning %} los expandirá en {% data variables.product.prodname_dotcom %} para el resultado relevante. Para obtener más información, consulta el [objeto `location`](#location-object). | +| `relatedLocations[]` | Un conjunto de ubicaciones relevantes para el resultado. {% data variables.product.prodname_code_scanning_capc %} vinculará las ubicaciones cuando se incorporen en el mensaje de resultado. Para obtener más información, consulta el [objeto `location`](#location-object). | ### Objeto `location` diff --git a/translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line.md b/translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line.md index 17f6a3e0cf..1e0971006c 100644 --- a/translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line.md +++ b/translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line.md @@ -12,7 +12,7 @@ versions: shortTitle: Agregar un proyecto localmente --- -## About adding existing projects to {% data variables.product.product_name %} +## Acerca de agregar proyectos existentes a {% data variables.product.product_name %} {% data reusables.repositories.migrating-from-codeplex %} @@ -24,37 +24,37 @@ shortTitle: Agregar un proyecto localmente {% data reusables.repositories.sensitive-info-warning %} -## Adding a project to {% data variables.product.product_name %} with {% data variables.product.prodname_cli %} +## Agregar un proyecto a {% data variables.product.product_name %} con {% data variables.product.prodname_cli %} -{% data variables.product.prodname_cli %} es una herramienta de código abierto para utilizar {% data variables.product.product_name %} desde la línea de comandos de tu computadora. {% data variables.product.prodname_cli %} can simplify the process of adding an existing project to {% data variables.product.product_name %} using the command line. To learn more about {% data variables.product.prodname_cli %}, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)." +{% data variables.product.prodname_cli %} es una herramienta de código abierto para utilizar {% data variables.product.product_name %} desde la línea de comandos de tu computadora. El {% data variables.product.prodname_cli %} puede simplificar el proceso de agregar un proyecto existente a {% data variables.product.product_name %} utilizando la línea de comandos. Para aprender más sobre el {% data variables.product.prodname_cli %}, consulta la sección "[Acerca del {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)". -1. In the command line, navigate to the root directory of your project. +1. En la línea de comandos, navega al directorio raíz de tu proyecto. 1. Inicializar el directorio local como un repositorio de Git. ```shell git init -b main ``` -1. To create a repository for your project on {% data variables.product.product_name %}, use the `gh repo create` subcommand. Replace `project-name` with the desired name for your repository. If you want your project to belong to an organization instead of to your user account, specify the organization name and project name with `organization-name/project-name`. +1. Para crear un repositorio para tu proyecto en {% data variables.product.product_name %}, utiliza el subcomando `gh repo create`. Reemplaza a `project-name` con el nombre que deseas dar a tu repositorio. Si quieres que tu proyecto pertenezca a una organización en vez de a tu cuenta de usuario, especifica el nombre de la organización y del proyecto con `organization-name/project-name`. ```shell gh repo create project-name ``` -1. Follow the interactive prompts. Alternatively, you can specify arguments to skip these prompts. For more information about possible arguments, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_repo_create). -1. Pull changes from the new repository that you created. (If you created a `.gitignore` or `LICENSE` file in the previous step, this will pull those changes to your local directory.) +1. Sigue los mensajes interactivos. Como alternativa, puedes especificar los argumentos para omitir estos mensajes. Para obtener más información sobre los argumentos posibles, consulta [el manual de {% data variables.product.prodname_cli %}](https://cli.github.com/manual/gh_repo_create). +1. Extrae los cambios del repositorio nuevo que creaste. (Si creaste un archivo `.gitignore` o `LICENSE` en el paso anterior, esto extraerá dichos cambios en tu directorio local.) ```shell git pull --set-upstream origin main ``` -1. Stage, commit, and push all of the files in your project. +1. Prueba, confirma y sube todos los archivos de tu proyecto. ```shell git add . && git commit -m "initial commit" && git push ``` -## Adding a project to {% data variables.product.product_name %} without {% data variables.product.prodname_cli %} +## Agregar un proyecto a {% data variables.product.product_name %} sin el {% data variables.product.prodname_cli %} {% mac %} diff --git a/translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools.md b/translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools.md index dbfc870c92..9de45791b9 100644 --- a/translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools.md +++ b/translations/es-ES/content/github/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools.md @@ -38,7 +38,7 @@ Recomendamos [hg-fast-export](https://github.com/frej/fast-export) para converti Te recomendamos utilizar [git-tfs](https://github.com/git-tfs/git-tfs) para mover los cambios entre TFVC y Git. -For more information about moving from TFVC (a centralized version control system) to Git, see "[Plan your Migration to Git](https://docs.microsoft.com/devops/develop/git/centralized-to-git)" from the Microsoft docs site. +Para obtener más información acerca de migrarse de TFVC (un sistema de control de versiones centralizado) a Git, consulta la sección "[Planea tu migración a Git](https://docs.microsoft.com/devops/develop/git/centralized-to-git)" del sitio de documentos de Microsoft. {% tip %} diff --git a/translations/es-ES/content/github/index.md b/translations/es-ES/content/github/index.md index 9d0bf984a8..1bebdcaca2 100644 --- a/translations/es-ES/content/github/index.md +++ b/translations/es-ES/content/github/index.md @@ -15,7 +15,6 @@ children: - /writing-on-github - /committing-changes-to-your-project - /collaborating-with-pull-requests - - /searching-for-information-on-github - /importing-your-projects-to-github - /managing-security-vulnerabilities - /finding-security-vulnerabilities-and-errors-in-your-code diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/about-identity-and-access-management-for-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/about-identity-and-access-management-for-your-enterprise-account.md index 8e7226a3d8..3bab5dd712 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/about-identity-and-access-management-for-your-enterprise-account.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/about-identity-and-access-management-for-your-enterprise-account.md @@ -13,13 +13,19 @@ shortTitle: IAM para tu empresa ## Acerca de la administración de accesos e identidades para tu cuenta empresarial -{% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %} For more information, see "[Enforcing SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account)." +{% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %} Para obtener más información, consulta la sección "[Requerir el inicio de sesión único de SAML en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account)". Después de que habilites el SSO de SAML, dependiendo del IdP que utilizas, debes poder habilitar las características de administración de acceso y de identidad adicionales. {% data reusables.scim.enterprise-account-scim %} Si utilizas Azure AD como tu IdP, puedes utilizar la sincronización de equipos para administrar la membresía del equipo dentro de cada organización. {% data reusables.identity-and-permissions.about-team-sync %} Para obtener más información, consulta la sección "[Administrar la sincronización de equipos para las organizaciones de tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)". -{% data reusables.saml.switching-from-org-to-enterprise %} For more information, see "[Switching your SAML configuration from an organization to an enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)." +{% data reusables.saml.switching-from-org-to-enterprise %} Para obtener más información, consulta la sección "[Cambiar tu configuración de SAML de una cuenta de organización a una de empresa](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)". + +## Acerca de {% data variables.product.prodname_emus %} + +{% data reusables.enterprise-accounts.emu-short-summary %} + +El configurar las {% data variables.product.prodname_emus %} para el inicio de sesión único de SAML y utilizar el aprovisionamiento involucra seguir un proceso diferente al que se llevaría para una empresa que no está utilizando {% data variables.product.prodname_managed_users %}. Si tu empresa utiliza {% data variables.product.prodname_emus %}, consulta la sección "[Configurar el inicio de sesión único de SAML para los Usuarios Administrados de Enterprise](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)". ## IdP compatibles @@ -32,4 +38,3 @@ Probamos y damos compatibilidad oficial de los siguientes IdP. Para el SSO de SA | OneLogin | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | PingOne | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | Shibboleth | {% octicon "check-circle-fill" aria-label="The check icon" %} | | - diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/configuring-saml-single-sign-on-for-your-enterprise-account-using-okta.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/configuring-saml-single-sign-on-for-your-enterprise-account-using-okta.md index 1cf70cbd2b..395db85133 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/configuring-saml-single-sign-on-for-your-enterprise-account-using-okta.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/configuring-saml-single-sign-on-for-your-enterprise-account-using-okta.md @@ -11,18 +11,20 @@ versions: fpt: '*' topics: - Enterprise -shortTitle: Configure SAML with Okta +shortTitle: Configurar el SAML con Okta --- {% data reusables.enterprise-accounts.user-provisioning-release-stage %} +{% data reusables.enterprise-accounts.emu-saml-note %} + ## Acerca de SAML con Okta Puedes controlar el acceso a tu cuenta empresarial en {% data variables.product.product_name %} y en otras aplicaciones web desde una interface central si configuras dicha cuenta para que utilice el SSO de SAML con Okta, un proveedor de identidad (IdP). -El SSO de SAML controla y protege el acceso a los recursos de la cuenta empresarial como las organizaciones, repositorios, informes de problemas y solicitudes de extracción. For more information, see "[Enforcing SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account)." +El SSO de SAML controla y protege el acceso a los recursos de la cuenta empresarial como las organizaciones, repositorios, informes de problemas y solicitudes de extracción. Para obtener más información, consulta la sección "[Requerir el inicio de sesión único de SAML para las organizaciones de tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account)". -{% data reusables.saml.switching-from-org-to-enterprise %} For more information, see "[Switching your SAML configuration from an organization to an enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)." +{% data reusables.saml.switching-from-org-to-enterprise %} Para obtener más información, consulta la sección "[Cambiar tu configuración de SAML de una cuenta de organización a una de empresa](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)". ## Prerrequisitos @@ -52,7 +54,7 @@ El SSO de SAML controla y protege el acceso a los recursos de la cuenta empresar 1. A la derecha del menú desplegable, teclea `.*.*`. 1. Haz clic en **Save ** (guardar). {% data reusables.saml.okta-view-setup-instructions %} -1. Habilita SAML para tu cuenta empresarial utilizando la información en las instrucciones de configuración. For more information, see "[Enforcing SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account)." +1. Habilita SAML para tu cuenta empresarial utilizando la información en las instrucciones de configuración. Para obtener más información, consulta la sección "[Requerir el inicio de sesión único de SAML para las organizaciones de tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account)". ## Crear grupos en Okta diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account.md index 523f759a78..0958160731 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account.md @@ -1,6 +1,6 @@ --- -title: Enforcing SAML single sign-on for organizations in your enterprise account -intro: 'You can control and secure access to resources like repositories, issues, and pull requests by enforcing SAML single sign-on (SSO) and centralized authentication through an IdP across all organizations owned by an enterprise account.' +title: Requerir el inicio de sesión único de SAML para las organizaciones en tu cuenta empresarial +intro: 'Puedes controlar y asegurar el acceso a los recursos como repositorios, propuestas y solicitudes de cambio al requerir el inicio de sesión único (SSO) de SAML y la autenticación centralizada a través de un IdP a través de todas las organizaciones que pertenecen a una cuenta empresarial.' product: '{% data reusables.gated-features.enterprise-accounts %}' permissions: Enterprise owners can enforce SAML single sign-on for organizations in an enterprise account. versions: @@ -10,9 +10,11 @@ topics: redirect_from: - /github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account - /github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account -shortTitle: Enforce SAML +shortTitle: Requerir SAML --- +{% data reusables.enterprise-accounts.emu-saml-note %} + ## Acerca del inicio de sesión único de SAML para las cuentas empresariales {% data reusables.saml.dotcom-saml-explanation %}Para obtener más información, consulta "[Acerca de la administración de identidad y accesos con el inicio de sesión único de SAML](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)". @@ -25,14 +27,14 @@ shortTitle: Enforce SAML {% data reusables.scim.enterprise-account-scim %} -## Enforcing SAML single-sign on for organizations in your enterprise account +## Requerir el inicio de sesión único de SAML para las organizaciones en tu cuenta empresarial {% note %} **Notas:** -- When you enable SAML SSO for your enterprise, the enterprise configuration will override any existing organization-level SAML configurations. {% data reusables.saml.switching-from-org-to-enterprise %} For more information, see "[Switching your SAML configuration from an organization to an enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)." -- When you enforce SAML SSO for an organization, {% data variables.product.company_short %} removes any members of the organization that have not authenticated successfully with your SAML IdP. When you require SAML SSO for your enterprise, {% data variables.product.company_short %} does not remove members of the enterprise that have not authenticated successfully with your SAML IdP. The next time a member accesses the enterprise's resources, the member must authenticate with your SAML IdP. +- Cuando hablitas el SSO de SAML para tu empresa, la configuración de esta ignorará cualquier configuración de SAML a nivel organizacional. {% data reusables.saml.switching-from-org-to-enterprise %} Para obtener más información, consulta la sección "[Cambiar tu configuración de SAML de una cuenta de organización a una de empresa](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)". +- Cuando requieres el SSO de SAML para una organización, {% data variables.product.company_short %} elimina cualquier miembro de la organización que no se haya autenticado con éxito en tu IdP de SAML. Cuando requieres el SSO de SAML para tu empresa, {% data variables.product.company_short %} no elimina a los miembros de dicha empresa que no se hayan autenticado exitosamente con tu IdP de SAML. La siguiente vez que un miembro acceda a los recursos empresariales, este deberá autenticarse con tu IdP de SAML. {% endnote %} @@ -42,7 +44,7 @@ Para obtener información más detallada sobre cómo habilitar el SAML utilizand {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} 4. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} -5. Under "SAML single sign-on", select **Require SAML authentication**. ![Casilla de verificación para habilitar SAML SSO](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) +5. En "Inicio de sesión único de SAML", selecciona **Requerir autenticación SAML**. ![Casilla de verificación para habilitar SAML SSO](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) 6. En el campo **URL de inicio de sesión**, escribe el extremo HTTPS de tu IdP para las solicitudes de inicio de sesión único. Este valor se encuentra en la configuración de tu IdP. ![Campo para la URL a la que los miembros serán redireccionados cuando inicien sesión](/assets/images/help/saml/saml_sign_on_url_business.png) 7. Opcionalmente, en el campo **Emisor**, teclea tu URL de emisor de SAML para verificar la autenticidad de los mensajes enviados. ![Campo para el nombre del emisor SAML](/assets/images/help/saml/saml_issuer.png) 8. En **Certificado público**, pega un certificado para verificar las respuestas de SAML. ![Campo para el certificado público de tu proveedor de identidad](/assets/images/help/saml/saml_public_certificate.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/managing-team-synchronization-for-organizations-in-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/managing-team-synchronization-for-organizations-in-your-enterprise-account.md index f8f03458e3..43033f9ed3 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/managing-team-synchronization-for-organizations-in-your-enterprise-account.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/managing-team-synchronization-for-organizations-in-your-enterprise-account.md @@ -12,6 +12,8 @@ redirect_from: shortTitle: Administrar la sincronización de equipos --- +{% data reusables.enterprise-accounts.emu-scim-note %} + ## Acerca de la sincronización de equipos para las cuentas empresariales Si utilizas Azure AD como tu IdP, puedes habilitar la sincronización de equipos para tu cuenta empresarial para permitir que los propietarios de la organización y mantenedores de equipo sincronicen equipos en las organizaciones que pertenezcan a tus cuentas empresariales con grupos de IdP. @@ -30,7 +32,7 @@ También puedes configurar y administrar la sincronización de equipos para una Tú o tu administrador de Azure AD debe ser un administrador global o un administrador de Rol Privilegiado en Azure AD. -You must enforce SAML single sign-on for organizations in your enterprise account with your supported IdP. For more information, see "[Enforcing SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account)." +Debes requerir el inicio de sesión único de SAML para las organizaciones en tu cuenta empresarial con tu IdP compatible. Para obtener más información, consulta la sección "[Requerir el inicio de sesión único de SAML para las organizaciones de tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account)". Debes autenticarte en tu cuenta empresarial utilizando el SSO de SAML y el IdP compatible. Para obtener más información, consulta "[Acerca de la autenticación con el inicio de sesión único de SAML](/articles/about-authentication-with-saml-single-sign-on)". diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md index a3f2502f61..bc0175651b 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md @@ -1,39 +1,41 @@ --- -title: Switching your SAML configuration from an organization to an enterprise account -intro: Learn special considerations and best practices for replacing an organization-level SAML configuration with an enterprise-level SAML configuration. +title: Cambiar tu configuración de SAML de una cuenta organizacional a una empresarial +intro: Aprende sobre las consideraciones especiales y mejores prácticas para reemplazar una configuración de SAML a nivel organizacional con una configuración de SAML a nivel empresarial. product: '{% data reusables.gated-features.enterprise-accounts %}' permissions: Enterprise owners can configure SAML single sign-on for an enterprise account. versions: fpt: '*' topics: - Enterprise -shortTitle: Switching from organization +shortTitle: Cambiar desde una organización --- +{% data reusables.enterprise-accounts.emu-saml-note %} + ## Acerca del inicio de sesión único de SAML para las cuentas empresariales {% data reusables.saml.dotcom-saml-explanation %}{% data reusables.saml.about-saml-enterprise-accounts %} {% data reusables.saml.switching-from-org-to-enterprise %} -When you configure SAML SSO at the organization level, each organization must be configured with a unique SSO tenant in your IdP, which means that your members will be associated with a unique SAML identity record for each organization they have succesfully authenticated with. If you configure SAML SSO for your enterprise account instead, each enterprise member will have one SAML identity that is used for all organizations owned by the enterprise account. +Cuando configuras el SSO de SAML a nivel de organización, cada organización debe configurarse con un inquilino de SSO único en tu IdP, lo cual significa que tus miembros se asociarán con un registro de identidad único de SAML para cada organización con la cual se hayan autenticado exitosamente. Si configuras el SSO de SAML para que se utilice en su lugar en tu empresa, cada miembro de ella tendrá una identidad de SAML que se utilizará para todas las organizaciones que pertenezcan a la cuenta empresarial. -After you configure SAML SSO for your enterprise account, the new configuration will override any existing SAML SSO configurations for organizations owned by the enterprise account. +Después de que configures el SSO de SAML para tu cuenta empresarial, la configuración nueva anulará cualquier configuración de SSO de SAML para las organizaciones que pertenezcan a esta cuenta. -Enterprise members will not be notified when an enterprise owner enables SAML for the enterprise account. If SAML SSO was previously enforced at the organization level, members should not see a major difference when navigating directly to organization resources. The members will continue to be prompted to authenticate via SAML. If members navigate to organization resources via their IdP dashboard, they will need to click the new tile for the enterprise-level app, instead of the old tile for the organization-level app. The members will then be able to choose the organization to navigate to. +No se notificará a los miembros de la empresa cuando un propietario habilite SAML para la cuenta empresarial. Si el SSO de SAML se requirió previamente a nivel organizacional, los miembros no deberían ver una diferencia mayor al navegar directamente a los recursos organizacinales. Se les seguirá pidiendo a los miembros autenticarse por SAML. Si los miembros navegan a los recursos organizacionales a través de su tablero de IdP, necesitarán hacer clic en una sección nueva para la app a nivel empresarial en vez de en la anterior para la de nivel organizacional. Entonces los miembros podrán elegir la organización a la cual quieren navegar. -Any personal access tokens (PATs), SSH keys, {% data variables.product.prodname_oauth_apps %}, and {% data variables.product.prodname_github_apps %} that were previously authorized for the organization will continue to be authorized for the organization. However, members will need to authorize any PATs, SSH keys, {% data variables.product.prodname_oauth_apps %}, and {% data variables.product.prodname_github_apps %} that were never authorized for use with SAML SSO for the organization. +Cualquier token de acceso personal (PAT), llave de SSH, {% data variables.product.prodname_oauth_apps %} y {% data variables.product.prodname_github_apps %} que se hayan autorizado previamente para la organización seguirán autorizadas para esta. Sin embargo, los miembros necesitarán autorizar cualquier PAT, llaves SSH, {% data variables.product.prodname_oauth_apps %} y {% data variables.product.prodname_github_apps %} que nunca se hayan autorizado para utilizarse con el SSO de SAML en la organización. -SCIM provisioning is not currently supported when SAML SSO is configured for an enterprise account. If you are currently using SCIM for an organization owned by your enterprise account, you will lose this functionality when switching to an enterprise-level configuration. +El aprovisionamiento de SCIM no es compatible actualmente cuando el SSO de SAML se configura para una cuenta empresarial. Si actualmente estás utilizando SCIM para una organización que pertenece a tu cuenta empresarial, perderás esta funcionalidad cuando cambies a una configuración a nivel empresarial. -You are not required to remove any organization-level SAML configurations before configuring SAML SSO for your enterprise account, but you may want to consider doing so. If SAML is ever disabled for the enterprise account in the future, any remaining organization-level SAML configurations will take effect. Removing the organization-level configurations can prevent unexpected issues in the future. +No se te requiere eliminar ninguna configuración de SAML a nivel organizacional antes de configurar el SSO de SAML para tu cuenta empresarial, pero deberías considerar hacerlo. Si en algún momento se inhabilita SAML para la cuenta empresarial en el futuro, cualquier configuración de SAML a nivel organizacional tomará efecto. El eliminar las configuraciones a nivel organizacional puede prevenir problemas inesperados en el futuro. -## Switching your SAML configuration from an organization to an enterprise account +## Cambiar tu configuración de SAML de una cuenta organizacional a una empresarial -1. Enforce SAML SSO for your enterprise account, making sure all organization members are assigned or given access to the IdP app being used for the enterprise account. For more information, see "[Enforcing SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account)." -1. Optionally, remove any existing SAML configuration for organizations owned by the enterprise account. To help you decide whether to remove the configurations, see "[About SAML single sign-on for enterprise accounts](#about-saml-single-sign-on-for-enterprise-accounts)." -1. If you kept any organization-level SAML configurations in place, to prevent confusion, consider hiding the tile for the organization-level apps in your IdP. -1. Advise your enterprise members about the change. - - Members will no longer be able to access their organizations by clicking the SAML app for the organization in the IdP dashboard. They will need to use the new app configured for the enterprise account. - - Members will need to authorize any PATs or SSH keys that were not previously authorized for use with SAML SSO for their organization. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/github/authenticating-to-github/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" and "[Authorizing an SSH key for use with SAML single sign-on](/github/authenticating-to-github/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)." - - Members may need to reauthorize {% data variables.product.prodname_oauth_apps %} that were previously authorized for the organization. Para obtener más información, consulta la sección "[Acerca de la autenticación con el inicio de sesión único de SAML](/github/authenticating-to-github/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on#about-oauth-apps-and-saml-sso)". +1. Requerir el SSO de SAML para tu cuenta empresarial, asegurándote de que todos los miembros organizacionales se asignen o se les de acceso a la app del IdP que se utiliza para la cuenta empresarial. Para obtener más información, consulta la sección "[Requerir el inicio de sesión único de SAML para las organizaciones de tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account)". +1. Opcionalmente, elimina cualquier configuración existente de SAML para las organizaciones que pertenecen a la cuenta empresarial. Para ayudarte a decidir si quieres eliminar o no las configuraciones, consulta la sección "[Acerca del inicio de sesión único de SAML para las cuentas empresariales](#about-saml-single-sign-on-for-enterprise-accounts)". +1. Si mantuviste activa cualquier configuración de SAML a nivel organizacional, para prevenir la confusión, considera ocultar la sección en las apps a nivel organizacional en tu IdP. +1. Notifica a los miembros de tu empresa sobre este cambio. + - Los miembros ya no podrán acceder a las organizaciones si hacen clic en la app de SAML de la organización en el tablero del IdP. Necesitarán utilizar la app nueva que se configuró para la cuenta empresarial. + - Los miembros necesitarán autorizar cualquier PAT o llave SSH que no se hayan autorizado antes para utilizarlos con el SSO de SAML en su organización. Para obtener más información, consulta las secciones "[Autorizar que un token de acceso personal se utilice con el inicio de sesión único de SAML](/github/authenticating-to-github/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" y "[Autorizar a una llave SSH para que se utilice con el inicio de sesión único de SAML](/github/authenticating-to-github/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)". + - Los miembros podrían necesitar volver a autorizar las {% data variables.product.prodname_oauth_apps %} que se autorizaran anteriormente en la organización. Para obtener más información, consulta la sección "[Acerca de la autenticación con el inicio de sesión único de SAML](/github/authenticating-to-github/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on#about-oauth-apps-and-saml-sso)". diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/index.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/index.md index 4cdec6e141..f08b8a07a0 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/index.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/index.md @@ -14,6 +14,7 @@ topics: children: - /managing-your-enterprise-account - /managing-users-in-your-enterprise + - /managing-your-enterprise-users-with-your-identity-provider - /managing-organizations-in-your-enterprise-account - /configuring-identity-and-access-management-for-your-enterprise-account - /setting-policies-for-organizations-in-your-enterprise-account diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account.md index c7ca80c4f5..1b4594a626 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account.md @@ -1,6 +1,6 @@ --- title: Agregar organizaciones en tu cuenta de empresa -intro: Puedes crear nuevas organizaciones para administrar dentro de tu cuenta de empresa. +intro: Puedes crear organizaciones nuevas o invitar a organizaciones existentes para que se administren con tu cuenta empresarial. product: '{% data reusables.gated-features.enterprise-accounts %}' redirect_from: - /articles/adding-organizations-to-your-enterprise-account @@ -13,9 +13,9 @@ topics: shortTitle: Agregar organizaciones --- -Los propietarios de la empresa pueden crear nuevas organizaciones dentro de los parámetros de la cuenta de empresa. +Los propietarios de las empresas pueden crear organizaciones nuevas dentro de los ajustes de una cuenta empresarial o invitar a organizaciones existentes para que se unan a una empresa. -Para agregar una organización a tu cuenta de empresa, debes crear la organización desde el interior de los parámetros de la cuenta de empresa. Si quieres transferir una organización existente a tu cuenta empresarial, contacta a tu representante de ventas para tu cuenta de {% data variables.product.prodname_dotcom %}. +Para agregar una organización a tu cuenta de empresa, debes crear la organización desde el interior de los parámetros de la cuenta de empresa. ## Crear una organización en tu cuenta de empresa @@ -29,3 +29,15 @@ Los propietarios de empresas que creen una organización que es propiedad de una 4. Haz clic en **Create organization** (Crear organización). 5. En "Invite owners" (Invitar propietarios), escribe el nombre de usuario de una persona a la que te gustaría invitar para convertir en propietario de la organización, luego clic en **Invite** (Invitar). ![Campo de búsqueda del propietario de la organización y botón Invite (Invitar)](/assets/images/help/business-accounts/invite-org-owner.png) 6. Da clic en **Finalizar**. + +## Invitar a una organización para que se una a tu cuenta empresarial + +Los propietarios de las empresas pueden invitar a las organizaciones existentes para que se unan a su cuenta empresarial. Si la organización que quieres invitar ya pertenece a otra empresa, no podrás emitir una invitación hasta que la empresa anterior deje la propiedad de esta. + +{% data reusables.enterprise-accounts.access-enterprise %} +2. En la pestaña **Organizaciones**, sobre la lista de las organizaciones, haz clic en **Invitar organización**. ![Invitar a una organización](/assets/images/help/business-accounts/enterprise-account-invite-organization.png) +3. Debajo de "Nombre de organización", comienza a teclear el nombre de la organización que quieras invitar y selecciónalo cuando se muestre en la lista desplegable. ![Buscar una organización](/assets/images/help/business-accounts/enterprise-account-search-for-organization.png) +4. Haz clic en **Invitar organización**. +5. Los propietarios de la organización recibirán un mensaje de correo electrónico invitándolos a unirse a la organización. Por lo menos el propietario necesita aceptar la invitación antes de que el proceso pueda continuar. Puedes cancelar o reenviar la invitación en cualquier momento antes de que un propietario la apruebe. ![Cancelar o reenviar](/assets/images/help/business-accounts/enterprise-account-invitation-sent.png) +6. Una vez que un propietario de la organización haya aprobado la invitación, puedes ver su estado en la lista de invitaciones pendientes. ![Invitación pendiente](/assets/images/help/business-accounts/enterprise-account-pending.png) +7. Haz clic en **Aprobar** para completar la transferencia o en **Cancelar** para cancelarla. ![Aprobar invitación](/assets/images/help/business-accounts/enterprise-account-transfer-approve.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md index f76d30d318..46be391bbd 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md @@ -1,108 +1,108 @@ --- -title: Streaming the audit logs for organizations in your enterprise account -intro: 'Enterprise owners can stream audit and Git events data from {% data variables.product.prodname_dotcom %} to an external data management system.' +title: Transmitir las bitácoras de auditoría para las organizaciones de tu cuenta empresarial +intro: 'Los propietarios de las empresas pueden transmitir datos de eventos de Git y de auditorías desde {% data variables.product.prodname_dotcom %} a un sistema de administración de datos externo.' product: '{% data reusables.gated-features.enterprise-accounts %}' miniTocMaxHeadingLevel: 3 versions: fpt: '*' topics: - Enterprise -shortTitle: Stream organization audit logs +shortTitle: Transmitir bitácoras de auditoría de la organización --- {% note %} -**Note:** Audit log streaming is currently in beta for {% data variables.product.prodname_ghe_cloud %} and subject to change. +**Nota:** La transmisión de bitácoras de auditoría se encuentra actualmente en beta para {% data variables.product.prodname_ghe_cloud %} y está sujeta a cambios. {% endnote %} -## About exporting audit data +## Acerca de exportar los datos de auditoría -You can extract audit log and Git events data from {% data variables.product.prodname_dotcom %} in multiple ways: +Puedes extraer datos de bitácoras de auditoría y de eventos de git desde {% data variables.product.prodname_dotcom %} en varias formas: -* Go to the Audit log page in {% data variables.product.prodname_dotcom %} and click **Export**.
    For more information, see "[Viewing the audit logs for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account)" and "[Exporting the audit log](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#exporting-the-audit-log)." -* Use the API to poll for new audit log events.
    For more information, see "[Using the audit log API](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#using-the-audit-log-api)." -* Set up {% data variables.product.product_name %} to stream audit data as events are logged. +* Ve a la página de bitácoras de auditoría en {% data variables.product.prodname_dotcom %} y haz clic en **Exportar**.
    Para obtener más información, consulta las secciones "[Ver las bitácoras de auditoría para las organizaciones de tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account)" y "[Exportar la bitácora de auditoría](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#exporting-the-audit-log)". +* Utiliza la API para encuestar por eventos nuevos de bitácoras de auditoría.
    Para obtener más información, consulta la sección "[Utilizar la API de bitácoras de auditoría](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#using-the-audit-log-api)". +* Configurar {% data variables.product.product_name %} para transmitir datos de auditoría mientras se registran los eventos. -## About audit log streaming +## Acerca de la transmisión de bitácoras de auditoría -To help protect your intellectual property and maintain compliance for your organization, you can use streaming to keep copies of your audit log data and monitor: +Para ayudarte a proteger tu propiedad intelectual y mantener el cumplimiento en tu organización, puedes utilizar la transmisión para mantener copias de tus datos de bitácoras de auditoría y monitorear: {% data reusables.audit_log.audited-data-list %} -The benefits of streaming audit data include: +Los beneficios de transmitir datos de auditoría incluyen: -* **Data exploration**. You can examine streamed events using your preferred tool for querying large quantities of data. The stream contains both audit events and Git events across the entire enterprise account. -* **Data continuity**. You can pause the stream for up to seven days without losing any audit data. -* **Data retention**. You can keep your exported audit logs and Git data as long as you need to. +* **Exploración de datos**. Puedes examinar los eventos transmitidos utilizando tu herramienta preferida para consultar cantidades grandes de datos. La transmisión contiene tanto los eventos de auditoría como los de Git a lo largo de toda la cuenta empresarial. +* **Continuidad de datos**. Puedes pausar la transmisión por hasta siete días sin perder datos de auditoría. +* **Retención de datos**. Puedes mantener tus datos de bitácoras de auditoría y de Git exportados conforme los necesites. -Enterprise owners can set up, pause, or delete a stream at any time. The stream exports the audit data for all of the organizations in your enterprise. +Los propietrios de empresas pueden configurar, pausar o borrar una transmisión en cualquier momento. La transmisión exporta los datos de auditoría de todas las organizaciones en tu empresa. -## Setting up audit log streaming +## Configurar la transmisión de bitácoras de auditoría -{% data variables.product.prodname_dotcom %} supports streaming of audit data to either Splunk or Azure Event Hubs. -### Setting up streaming to Splunk +{% data variables.product.prodname_dotcom %} es compatible con la transmisión de datos de auditoría ya sea a los Concentradores de Eventos de Splunk o de Azure. +### Configurar la transmisión a Splunk -To stream audit logs to Splunk's HTTP Event Collector (HEC) endpoint you must make sure that the endpoint is configured to accept HTTPS connections. For more information, see the Splunk documentation article "[Set up and use HTTP Event Collector in Splunk Web](https://docs.splunk.com/Documentation/Splunk/latest/Data/UsetheHTTPEventCollector)." +Para transmitir bitácoras de auditoría a la terminal del Recolector de Eventos HTTP (HEC) de Splunk, debes asegurarte de que la terminal se configure para aceptar conexiones HTTPS. Para obtener más información, consulta el artículo "[Configurar y utilizar el Recolector de Eventos HTTP en la Web de Splunk](https://docs.splunk.com/Documentation/Splunk/latest/Data/UsetheHTTPEventCollector)" en la documentación de Splunk. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.audit-log-tab %} -1. Click the **Log streaming** tab. -1. Click **Configure stream** and select **Splunk**. ![Choose Splunk from the drop-down menu](/assets/images/help/enterprises/audit-stream-choice-splunk.png) -1. On the configuration page, enter: - * The domain on which the application you want to stream to is hosted. +1. Haz clic en la pestaña de **Transmisión de bitácoras**. +1. Haz clic en **Configurar transmisión** y selecciona **Splunk**. ![Elegir Splunk del menú desplegable](/assets/images/help/enterprises/audit-stream-choice-splunk.png) +1. En la página de configuración, ingresa: + * El dominio en el cual se hospeda la aplicación que quieres transmitir. - If you are using Splunk Cloud, `Domain` should be `http-inputs-`, where `host` is the domain you use in Splunk Cloud. Por ejemplo: `http-inputs-mycompany.splunkcloud.com`. + Si estás utilizando Splunk Cloud, `Domain` debe ser `http-inputs-`, en donde `host` es el dominio que utilizas en Splunk Cloud. Por ejemplo: `http-inputs-mycompany.splunkcloud.com`. - * The port on which the application accepts data.
    + * El puerto mediante el cual la aplicación acepta datos.
    - If you are using Splunk Cloud, `Port` should be `443` if you haven't changed the port configuration. If you are using the free trial version of Splunk Cloud, `Port` should be `8088`. + Si estás utilizando Splunk Cloud, `Port` debería ser `443` si no has cambiado la configuración del puerto. Si estás utilizando la versión de prueba gratis de Splunk Cloud, `Port` debe ser `8088`. - * A token that {% data variables.product.prodname_dotcom %} can use to authenticate to the third-party application. ![Enter stream settings](/assets/images/help/enterprises/audit-stream-add-splunk.png) + * Un token que pueda utilizar {% data variables.product.prodname_dotcom %} para autenticarse a la aplicación de terceros. ![Ingresar los ajustes de la transmisión](/assets/images/help/enterprises/audit-stream-add-splunk.png) -2. Leave the **Enable SSL verification** check box selected. +2. Deja seleccionada la casilla de **Habilitar la verificación por SSL**. - Audit logs are always streamed as encrypted data, however, with this option selected, {% data variables.product.prodname_dotcom %} verifies the SSL certificate of your Splunk instance when delivering events. SSL verification helps ensure that events are delivered to your URL endpoint securely. You can clear the selection of this option, but we recommend you leave SSL verification enabled. -3. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect to the Splunk endpoint. ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check-splunk.png) -4. After you have successfully verified the endpoint, click **Save**. + Las bitácoras de auditoría siempre se transmiten como datos cifrados, sin embargo, si seleccionas esta opción, {% data variables.product.prodname_dotcom %} verificará el certificado SSL de tu instancia de Splunk cuando entregue eventos. La verificación por SSL te ayuda a garantizar que los eventos se entreguen a tu terminal URL con seguridad. Puedes limpiar la selección de esta opción, pero te recomendamos que dejes habilitada la verificación por SSL. +3. Haz clic en **Verificar terminal** para verificar que {% data variables.product.prodname_dotcom %} puede conectarse a la terminal de Splunk. ![Verificar la terminal](/assets/images/help/enterprises/audit-stream-check-splunk.png) +4. Después de que hayas verificado la terminal con éxito, haz clic en **Guardar**. -### Setting up streaming to Azure Event Hubs +### Configurar la transmisión hacia Azure Event Hubs -Before setting up a stream in {% data variables.product.prodname_dotcom %}, you must first have an event hub namespace in Microsoft Azure. Next, you must create an event hub instance within the namespace. You'll need the details of this event hub instance when you set up the stream. For details, see the Microsoft documentation, "[Quickstart: Create an event hub using Azure portal](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-create)." +Antes de configurar una transmisión en {% data variables.product.prodname_dotcom %}, primero debes tener un espacio designador de nombre para concentradores de eventos en Microsoft Azure. Posteriormente, debes crear una instancia de concentrador de eventos dentro del designador de nombre. Necesitarás los detalles de esta instancia de concentrador de eventos cuando configures la transmisión. Para encontrar los detalles, consulta la documentación de Microsoft, en la aprte de "[Inicio rápido: Crear un concentrador de eventos utilizando el portal de Azure](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-create)". -You need two pieces of information about your event hub: its instance name and the connection string. +Necesitas dos partes de información sobre tu concentrador de eventos: su nombre de instancia y la secuencia de conexión. -**On Microsoft Azure portal**: -1. In the left menu select **Entities**. Then select **Event Hubs**. The names of your event hubs are listed. ![A list of event hubs](/assets/images/help/enterprises/azure-event-hubs-list.png) -1. Make a note of the name of the event hub you want to stream to. -1. Click the required event hub. Then, in the left menu, select **Shared Access Policies**. -1. Select a shared access policy in the list of policies, or create a new policy. ![A list of shared access policies](/assets/images/help/enterprises/azure-shared-access-policies.png) -1. Click the button to the right of the **Connection string-primary key** field to copy the connection string. ![The event hub connection string](/assets/images/help/enterprises/azure-connection-string.png) +**En el portal de Microsoft Azure**: +1. En el menú de la izquierda, selecciona **Entidades**. Posteriormente, selecciona **Concentradores de Eventos**. Se listarán los nombres de tus concentradores de eventos. ![Una lista de concentradores de eventos](/assets/images/help/enterprises/azure-event-hubs-list.png) +1. Haz una nota del nombre del concentrador de eventos al cual quieras transmitir. +1. Haz clic en el concentrador de eventos requerido. Posteriormente, en el menú de la izquierda, selecciona **Políticas de Acceso Compartido**. +1. Selecciona las políticas de acceso compartido de la lista de políticas o crea una nueva. ![Una lista de políticas de acceso compartidas](/assets/images/help/enterprises/azure-shared-access-policies.png) +1. Haz clic en el botón a la derecha del campo **Secuencia de conexión-llave primaria** para copiar la secuencia de conexión. ![La secuencia de conexión del concentrador de eventos](/assets/images/help/enterprises/azure-connection-string.png) -**On {% data variables.product.prodname_dotcom %}**: +**En {% data variables.product.prodname_dotcom %}**: {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.audit-log-tab %} -1. Click the **Log streaming** tab. -1. Click **Configure stream** and select **Azure Event Hubs**. ![Choose Splunk from the drop-down menu](/assets/images/help/enterprises/audit-stream-choice-azure.png) -1. On the configuration page, enter: - * The name of the Azure Event Hubs instance. - * The connection string. ![Enter stream settings](/assets/images/help/enterprises/audit-stream-add-azure.png) -2. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect to the Azure endpoint. ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check-azure.png) -3. After you have successfully verified the endpoint, click **Save**. +1. Haz clic en la pestaña de **Transmisión de bitácoras**. +1. Haz clic en **Configurar transmisión** y selecciona **Azure Event Hubs**. ![Elige Splunk desde el menú desplegable](/assets/images/help/enterprises/audit-stream-choice-azure.png) +1. En la página de configuración, ingresa: + * El nombre de la instancia de Azure Event Hubs. + * La secuencia de conexión. ![Ingresar la configuración de transmisiones](/assets/images/help/enterprises/audit-stream-add-azure.png) +2. Haz clic en **Verificar terminal** para verificar que {% data variables.product.prodname_dotcom %} puede conectarse a la terminal de Azure. ![Verificar la terminal](/assets/images/help/enterprises/audit-stream-check-azure.png) +3. Después de que hayas verificado la terminal con éxito, haz clic en **Guardar**. -## Pausing audit log streaming +## Pausar la transmisión de bitácoras de auditoría -Pausing the stream allows you to perform maintenance on the receiving application without losing audit data. Audit logs are stored for up to seven days on {% data variables.product.product_location %} and are then exported when you unpause the stream. +El pausar la transmisión te permite realizar el mantenimiento de la aplicación receptora sin perder datos de auditoría. Las bitácoras de auditoría se almacenan por hasta siete días en {% data variables.product.product_location %} y luego se exportan cuando dejas de pausar la transmisión. -1. Display the "Log streaming" tab, as described above. -1. Click **Pause stream**. ![Pause the stream](/assets/images/help/enterprises/audit-stream-pause.png) -1. A confirmation message is displayed. Click **Pause stream** to confirm. +1. Muestra la pestaña "Transmisión de bitácoras" como se describe anteriormente. +1. Haz clic en **Pausar transmisión**. ![Pausar la transmisión](/assets/images/help/enterprises/audit-stream-pause.png) +1. Se mostrará un mensaje de confirmación. Haz clic en **Pausar transmisión** para confirmar. -When the application is ready to receive audit logs again, click **Resume stream** to restart streaming audit logs. +Cuando la aplicación esté lista para recibir bitácoras de auditoría nuevamente, haz clic en **Reanudar transmisión** para reiniciar la transmisión de bitácoras de auditoría. -## Deleting the audit log stream +## Borrar la transmisión de bitácoras de auditoría -1. Display the "Log streaming" tab, as described above. -1. Click **Delete stream**. ![Delete the stream](/assets/images/help/enterprises/audit-stream-delete.png) -2. A confirmation message is displayed. Click **Delete stream** to confirm. +1. Muestra la pestaña de "Transmisión de bitácora", tal como se describe anteriormente. +1. Haz clic en **Borrar transmisión**. ![Borrar la transmisión](/assets/images/help/enterprises/audit-stream-delete.png) +2. Se muestra un mensaje de confirmación. Haz clic en **Borrar transmisión** para confirmar. diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md index 1e634cb6f1..820f2fdb77 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md @@ -1,6 +1,6 @@ --- title: Invitar a las personas para que administren tu empresa -intro: 'You can {% ifversion fpt %}invite people to become enterprise owners or billing managers for{% elsif ghes %}add enterprise owners to{% endif %} your enterprise account. You can also remove enterprise owners {% ifversion fpt %}or billing managers {% endif %}who no longer need access to the enterprise account.' +intro: 'Puedes {% ifversion fpt %}invitar a que las personas se conviertan en propietarios empresariales o gerentes de facturación para {% elsif ghes %}agregar propietarios empresariales a{% endif %} tu cuenta empresarial. También puedes eliminar a los propietarios empresariales {% ifversion fpt %}o gerentes de facturación {% endif %}que ya no necesiten acceso a la cuenta empresarial.' product: '{% data reusables.gated-features.enterprise-accounts %}' permissions: 'Enterprise owners can {% ifversion fpt %}invite other people to become{% elsif ghes %}add{% endif %} additional enterprise administrators.' redirect_from: @@ -18,13 +18,19 @@ topics: shortTitle: Invitar personas para que administren --- -## About users who can manage your enterprise account +## Acerca de los usuarios que pueden administrar tu cuenta empresarial -{% data reusables.enterprise-accounts.enterprise-administrators %} For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise)." +{% data reusables.enterprise-accounts.enterprise-administrators %} Para obtener más información, consulta la sección "[Roles en una empresaempresa](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise)". {% ifversion ghes %} -If you want to manage owners and billing managers for an enterprise account on {% data variables.product.prodname_dotcom_the_website %}, see "[Inviting people to manage your enterprise](/free-pro-team@latest/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)" in the {% data variables.product.prodname_dotcom_the_website %} documentation. +Si quieres administrar los propietarios y gerentes de facturación para una cuenta empresarial en {% data variables.product.prodname_dotcom_the_website %}, consulta la sección "[Invitar a personas para que administren tu empresa](/free-pro-team@latest/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)" en la documentación de {% data variables.product.prodname_dotcom_the_website %}. + +{% endif %} + +{% ifversion fpt %} + +Si tu empresa utiliza {% data variables.product.prodname_emus %}, solo se pueden agregar o eliminar los propietarios de las empresas a través de tu proveedor de identidad. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)". {% endif %} @@ -34,18 +40,18 @@ If you want to manage owners and billing managers for an enterprise account on { {% endtip %} -## {% ifversion fpt %}Inviting{% elsif ghes %}Adding{% endif %} an enterprise administrator to your enterprise account +## {% ifversion fpt %}Invitar{% elsif ghes %}Agregar{% endif %} a un administrador empresarial a tu cuenta empresarial -{% ifversion fpt %}After you invite someone to join the enterprise account, they must accept the emailed invitation before they can access the enterprise account.{% endif %} +{% ifversion fpt %}Después de que invites a alguien para que se una a la cuenta empresarial, esta persona debe aceptar la invitación que le llegó por correo electrónico antes de que pueda acceder a la cuenta empresarial.{% endif %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.people-tab %} 1. En la barra lateral izquierda, haz clic en **Administrators** (Administradores). ![Pestaña Administrators (Administradores) en la barra lateral izquierda](/assets/images/help/business-accounts/administrators-tab.png) -1. Above the list of administrators, click {% ifversion fpt %}**Invite admin**{% elsif ghes %}**Add owner**{% endif %}. +1. Sobre la lista de administradores, haz clic en {% ifversion fpt %}**Invitar administrador**{% elsif ghes %}**Agregar propietario**{% endif %}. {% ifversion fpt %} - !["Invite admin" button above the list of enterprise owners](/assets/images/help/business-accounts/invite-admin-button.png) + ![botón de "invitar administrador" sobre la lista de propietarios empresariales](/assets/images/help/business-accounts/invite-admin-button.png) {% elsif ghes %} - !["Add owner" button above the list of enterprise owners](/assets/images/help/business-accounts/add-owner-button.png) + ![Botón de "Agregar propietario" sobre la lista de propietarios empresariales](/assets/images/help/business-accounts/add-owner-button.png) {% endif %} 1. Escribe el nombre de usuario, el nombre completo o la dirección de correo electrónico de la persona a la que quieres invitar a que se convierta en administrador de empresa, luego selecciona la persona adecuada en los resultados. ![Modal box with field to type a person's username, full name, or email address, and Invite button](/assets/images/help/business-accounts/invite-admins-modal-button.png){% ifversion fpt %} 1. Selecciona **Owner** (Propietario) o **Billing Manager** (Gerente de facturación). ![Casilla modal con opciones de roles](/assets/images/help/business-accounts/invite-admins-roles.png) @@ -58,10 +64,10 @@ Solo los propietarios de empresa pueden eliminar a otros administradores de empr {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.people-tab %} -1. Next to the username of the person you'd like to remove, click {% octicon "gear" aria-label="The Settings gear" %}, then click **Remove owner**{% ifversion fpt %} or **Remove billing manager**{% endif %}. +1. Junto al nombre de usuario de la persona que te gustaría eliminar, haz clic en {% octicon "gear" aria-label="The Settings gear" %}, luego en **Eliminar propietario**{% ifversion fpt %} o **Eliminar gerente de facturación**{% endif %}. {% ifversion fpt %} ![Parámetros con opción del menú para eliminar un administrador de empresa](/assets/images/help/business-accounts/remove-admin.png) {% elsif ghes %} ![Parámetros con opción del menú para eliminar un administrador de empresa](/assets/images/help/business-accounts/ghes-remove-owner.png) {% endif %} -1. Read the confirmation, then click **Remove owner**{% ifversion fpt %} or **Remove billing manager**{% endif %}. +1. Lee la confirmación y luego haz clic en **Eliminar propietario**{% ifversion fpt %} o **Eliminar gerente de facturación**{% endif %}. diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md index dc5ef1c2e2..8993f47600 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md @@ -27,8 +27,8 @@ Los propietarios de las empresas y gerentes de facturación tienen derechos de s {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} 3. Debajo de "Configuración", haz clic en **Soporte**. ![Elemento de menú de soporte](/assets/images/help/enterprises/settings-support.png) -4. Debajo de "Agregar miembro de soporte", comienza a teclear el nombre o nombre de usuario de la persona a la que quieres dar derechos de soporte. Haz clic en su nombre en la lista de coincidencias. ![Add support entitlement search](/assets/images/help/enterprises/settings-support-entitlement-search.png) -5. Haz clic en **Agregar derechos de soporte**. ![Add support entitlement button](/assets/images/help/enterprises/settings-support-add-entitlement.png) +4. Debajo de "Agregar miembro de soporte", comienza a teclear el nombre o nombre de usuario de la persona a la que quieres dar derechos de soporte. Haz clic en su nombre en la lista de coincidencias. ![Agregar una búsqueda de derechos de soporte](/assets/images/help/enterprises/settings-support-entitlement-search.png) +5. Haz clic en **Agregar derechos de soporte**. ![Agregar un botón de derechos de soporte](/assets/images/help/enterprises/settings-support-add-entitlement.png) ## Eliminar los derechos de soporte de un miembro de la empresa diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise.md index 6e109eab13..8c85b9ac49 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise.md @@ -21,7 +21,14 @@ Todas las personas en una empresa son miembros de ella. También puedes asignar {% data reusables.enterprise-accounts.enterprise-administrators %} -Para obtener más información acerca de agregar personas a tu empresa, consulta la sección "{% ifversion fpt %}[Invitar personas para administrar tu empresa](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise){% else %}[Autenticación](/admin/authentication){% endif %}". +{% ifversion fpt %} +Si tu empresa no utiliza {% data variables.product.prodname_emus %}, puedes invitar a alguien a un rol administrativo utilizando una cuetna de usuario en {% data variables.product.product_name %} que ellos controlen. Para obtener más información, consulta la sección "[Invitar a las personas para que administren tu empresa](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)". + +En una empresa que utiliza {% data variables.product.prodname_emus %}, los propietarios y miembros nuevos deben aprovisionarse mediante tu proveedor de identidad. Los propietarios empresariales y propietarios de empresas no pueden agregar miembros o propietarios nuevos a la empresa utilizando {% data variables.product.prodname_dotcom %}. Puedes seleccionar el rol empresarial de un miembro utilizando tu IdP y no puede cambiarse en {% data variables.product.prodname_dotcom %}. Puedes seleccionar el rol de un miembro en una organización de {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)". +{% else %} +Para obtener más información acerca de cómo agregar personas a tu empresa, consulta la sección "[Autenticación](/admin/authentication)". + +{% endif %} ## Propietario de empresa diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md index 375a164054..a31755c45b 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md @@ -18,18 +18,13 @@ shortTitle: Visualizar & administrar el acceso con SAML Cuando habilitas el inicio de sesión único de SAML para tu cuenta empresarial, cada miembro de la empresa puede vincular su identidad externa en tu proveedor de identidad (IdP) para su cuenta existente de {% data variables.product.product_name %}. {% data reusables.saml.about-saml-access-enterprise-account %} +Si tu empresa utiliza {% data variables.product.prodname_emus %}, tus miembros utilizarán cuentas que se aprovisionen a través de tu IdP. {% data variables.product.prodname_managed_users_caps %} no utilizará su cuenta de usuario existente en {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)". + ## Visualizar y revocar una identidad vinculada {% data reusables.saml.about-linked-identities %} -{% warning %} - -**Advertencia:** Para las orgtanizaciones que utilizan SCIM: -- El revocar una identidad de usuario en {% data variables.product.product_name %} también eliminará los metadatos de SAML y de SCIM. Como resultado, el proveedor de identidad no podrá sincronizar o desaprovisionar la identidad de usuario enlazada. -- Un administrador deberá revocar una identidad enlazada a través del proveedor de identidad. -- Para revocar una identidad enlazada y enlazar una cuenta diferente a través del proveedor de identidad, un administrador puede eliminar y volver a asignar el usuario con la aplicación de {% data variables.product.product_name %}. Para obtener más información, consulta los documentos de tu proveedor de identidad. - -{% endwarning %} +If your enterprise uses {% data variables.product.prodname_emus %}, you will not be able to deprovision or remove user accounts from the enterprise on {% data variables.product.product_name %}. Cualquier cambio que necesites hacer a los {% data variables.product.prodname_managed_users %} de tu empresa deberá realizarse mediante tu IdP. {% data reusables.identity-and-permissions.revoking-identity-team-sync %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts.md index 160913fc68..d165ee431f 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts.md @@ -1,6 +1,6 @@ --- title: Acerca de las cuentas de empresa -intro: 'With {% data variables.product.product_name %}, you can use an enterprise account to {% ifversion fpt %}enable collaboration between your organizations, while giving{% elsif ghes or ghae %}give{% endif %} administrators a single point of visibility and management.' +intro: 'Con {% data variables.product.product_name %}, puedes utilizar una cuenta empresarial para {% ifversion fpt %}habilitar la colaboración entre tus organizaciones, mientras que proporcionas{% elsif ghes or ghae %}dar{% endif %} a los administradores un punto único de visibilidad y administración.' product: '{% data reusables.gated-features.enterprise-accounts %}' redirect_from: - /articles/about-github-business-accounts/ diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md new file mode 100644 index 0000000000..8825a829dc --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md @@ -0,0 +1,84 @@ +--- +title: Acerca de los Usuarios Administrados Empresariales +shortTitle: Acerca de los usuarios administrados +intro: 'Puedes administrar centralmente la identidad y el acceso para los miembros de tu empresa en {% data variables.product.prodname_dotcom %} desde tu proveedor de identidad.' +product: '{% data reusables.gated-features.emus %}' +redirect_from: + - /early-access/github/articles/get-started-with-managed-users-for-your-enterprise +versions: + fpt: '*' +topics: + - Accounts + - Enterprise +--- + +## Acerca de {% data variables.product.prodname_emus %} + +Con {% data variables.product.prodname_emus %}, puedes controlar las cuentas de usuario de los miembros de tu empresa a través de tu proveedor de identidad (IdP). Puedes simplificar la autenticación con el inicio de sesión único (SSO) de SAML y aprovisionar, actualizar y desaprovisionar las cuentas de usuario de tus miembros empresariales. Los usuarios que se asignen a la aplicación de {% data variables.product.prodname_emu_idp_application %} en tu IdP se aprovisionarán como cuentas de usuario nuevas en {% data variables.product.prodname_dotcom %} y se agregarán a tu empresa. Tú controlas los nombres de usuario, datos de perfil, membrecía de equipo y acceso al repositorio desde tu IdP. + +En tu IdP, puedes dar a cada {% data variables.product.prodname_managed_user %} el rol de usuario, propietario de la empresa o gerente de facturación. {% data variables.product.prodname_managed_users_caps %} puede ser propietario de organizaciones dentro de tu empresa y puede agregar a otros {% data variables.product.prodname_managed_users %} a las organizaciones y equipos dentro de ella. Para obtener más información, consulta las secciones "[Roles en una empresa](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" y "[Acerca de las organizaciones](/organizations/collaborating-with-groups-in-organizations/about-organizations)". + +También puedes administrar la membrecía de equipo dentro de una organización en tu empresa directamente desde tu IdP, lo cual te permite administrar el acceso al repositorio utilizando grupos en tu IdP. La membrecía de la organización puede administrarse manualmente o actualizarse automáticamente conforme se agreguen {% data variables.product.prodname_managed_users %} a los equipos dentro de dicha organización. Para obtener más información, consulta la sección "[Administrar las membrecías de equipo con los grupos de proveedor de identidades](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)". + +Puedes otorgar acceso a los {% data variables.product.prodname_managed_users %}, así como la habilidad de contribuir con los repositorios dentro de tu empresa, pero los {% data variables.product.prodname_managed_users %} no pueden crear contenido público ni colaborar con otros usuarios, organizaciones y empresas en el resto de {% data variables.product.prodname_dotcom %}. No se puede invitar a los {% data variables.product.prodname_managed_users %} que se aprovisionaron para tu empresa para que se unan a organizaciones o repositorios fuera de esta, ni se puede invitar a los {% data variables.product.prodname_managed_users %} a otras empresas. Los colaboradores externos no son compatibles con los {% data variables.product.prodname_emus %}. + +El nombre de usuario de los {% data variables.product.prodname_managed_users %} de tu empresa y su información de perfil, tal como los nombres y direcciones de correo electrónico que se muestran, se configuran mediante tu IdP y no pueden cambiarlos los mismos usuarios. Para obtener más información, consulta la sección "[Nombres de usuario e información de perfil](#usernames-and-profile-information)". + +{% data reusables.enterprise-accounts.emu-forks %} + +Los propietarios de las empresas pueden auditar todas las acciones de los {% data variables.product.prodname_managed_users %} en {% data variables.product.prodname_dotcom %}. + +Para utilizar los {% data variables.product.prodname_emus %}, necesitas un tipo separado de cuenta empresarial con {% data variables.product.prodname_emus %} habilitados. Para obtener más información sobre cómo crear esta cuenta, consulta la sección "[Acerca de las empresas con usuarios administrados](#about-enterprises-with-managed-users)". + + +## Soporte del proveedor de identidad + +{% data variables.product.prodname_emus %} es compatible con los siguientes IdP: + +{% data reusables.enterprise-accounts.emu-supported-idps %} + +## Habilidades y restricciones de los {% data variables.product.prodname_managed_users %} + +Los {% data variables.product.prodname_managed_users_caps %} solo pueden colaborar en los repositorios privados e internos dentro de su empresa y con los repositorios que pertenecen a su cuenta de usuario. Los {% data variables.product.prodname_managed_users_caps %} tienen acceso de solo lectura al resto de la comunidad de {% data variables.product.prodname_dotcom %}. + +* Los {% data variables.product.prodname_managed_users_caps %} no pueden crear propuestas ni solicitudes de cambios, comentar o agregar reacciones, ni marcar como favoritos u observar o bifurcar repositorios fuera de la empresa. +* Los {% data variables.product.prodname_managed_users_caps %} no pueden subir código a los repositorios fuera de la empresa. +* Solo otros miembros de la empresa pueden ver a los {% data variables.product.prodname_managed_users_caps %} y al contenido que estos crean. +* Los {% data variables.product.prodname_managed_users_caps %} no pueden seguir a usuarios que estén fuera de la empresa. +* Los {% data variables.product.prodname_managed_users_caps %} no pueden crear gists o comentar en ellos. +* Los {% data variables.product.prodname_managed_users_caps %} no pueden instalar {% data variables.product.prodname_github_apps %} en sus cuentas de usuario. +* Otros usuarios de {% data variables.product.prodname_dotcom %} no pueden ver, mencionar o invitar a {% data variables.product.prodname_managed_user %} para colaborar. +* Los {% data variables.product.prodname_managed_users_caps %} solo pueden ser propietarios de repositorios privados y los {% data variables.product.prodname_managed_users %} solo pueden invitar a otros miembros de la empresa para que colaboren con sus propios repositorios. +* Solo se pueden crear repositorios internos y privados en las organizaciones que pertenezcan a una {% data variables.product.prodname_emu_enterprise %}, dependiendo de los ajustes de visibilidad del repositorio o empresa. + +## Acerca de las empresas con usuarios administrados + +Para utilizar los {% data variables.product.prodname_emus %}, necesitas un tipo separado de cuenta empresarial con {% data variables.product.prodname_emus %} habilitados. Para probar {% data variables.product.prodname_emus %} o para debatir sobre las opciones para migrarte desde tu empresa existente, por favor, contacta al [Equipo de ventas de {% data variables.product.prodname_dotcom %}](https://enterprise.github.com/contact). + +Tu contacto en el equipo de ventas de GitHub trabajará contigo para crear tu {% data variables.product.prodname_emu_enterprise %} nueva. Necesitarás proporcionar la dirección de correo electrónico del usuario que configurará tu empresa y un código corto que se utilizará como el sufijo de los nombres de usuario de los miembros. {% data reusables.enterprise-accounts.emu-shortcode %} Para obtener más información, consulta la sección "[Nombres de usuario e información de perfil](#usernames-and-profile-information)". + +Después de crear tu empresa, recibirás un mensaje de correo electrónico de {% data variables.product.prodname_dotcom %}, el cual te invitará a elegir una contraseña para tu usuario de configuración de la empresa, quien será el primer propietario de esta. El usuario de configuración solo se utiliza para configurar el inicio de sesión único de SAML y la integración de aprovisionamiento de SCIM para la empresa. Ya no tendrá acceso para administrar la cuenta empresarial una vez que se habilite SAML con éxito. + +El nombre de usuario del usuario de configuración es el código corto de tu empresa con el sufijo `_admin`. Después de que inicies sesión en tu usuario de configuración, puedes comenzar a configurar el SSO de SAML para tu empresa. Para obtener más información, consulta la sección "[Configurar el inicio de sesión único de SAML para los Usuarios Administrados Empresariales](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)". + +{% note %} + +{% data reusables.enterprise-accounts.emu-password-reset-session %} + +{% endnote %} + +## Autenticarse como una {% data variables.product.prodname_managed_user %} + +Los {% data variables.product.prodname_managed_users_caps %} se deben autenticar mediante su proveedor de identidad. + +Para autenticarse, los {% data variables.product.prodname_managed_users %} deben visitar su portal de la aplicación de IdP o **https://github.com/enterprises/ENTERPRISE_NAME**, reemplazando **ENTERPRISE_NAME** con el nombre de tu empresa. + +## Nombres de usuario e información de perfil + +Cuando se cree tu {% data variables.product.prodname_emu_enterprise %}, elegirás un código corto que se utilizará como el sufijo de los nombres de usuario de los miembros de tu empresa. {% data reusables.enterprise-accounts.emu-shortcode %} El usuario de configuración que configure el SSO de SAML tendrá un nombre de usuario en el formato **@SHORT-CODE_admin**. + +Cuando aprovisionas un usuario nuevo desde tu proveedor de identidad, el {% data variables.product.prodname_managed_user %} nuevo tendrá un nombre de usuario de {% data variables.product.product_name %} en el formato de **@IDP-USERNAME_SHORT-CODE**. Cuando utilizas Azure Active Directory (Azure AD), el _IDP-USERNAME_ se forma normalizando los caracteres que preceden a `@` en el UPN (Nombre Principal de Usuario) que proporciona Azure AD. Cuando utilizas okta, el _IDP-USERNAME_ es el atributo de nombre de usuario normalizado que proporciona Okta. + +El nombre de usuario de la cuenta nueva que se aprovisionó en {% data variables.product.product_name %}, incluyendo el guion bajo y código corto, no debe exceder los 39 caracteres. + +El nombre de perfil y dirección de correo electrónico de un {% data variables.product.prodname_managed_user %} también lo proporciona el IdP. Los {% data variables.product.prodname_managed_users_caps %} no pueden cambiar su nombre de perfil ni dirección de correo electrónico en {% data variables.product.prodname_dotcom %}. diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/auditing-activity-in-your-enterprise.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/auditing-activity-in-your-enterprise.md new file mode 100644 index 0000000000..c7d516a174 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/auditing-activity-in-your-enterprise.md @@ -0,0 +1,32 @@ +--- +title: Actividad de auditoría en tu empresa +shortTitle: Actividad de auditoría +intro: 'Puedes auditar la actividad de los {% data variables.product.prodname_managed_users %} en tu empresa, viendo la información sobre qué acciones se llevaron a cabo, mediante qué usuarios y cuándo.' +permissions: Enterprise owners can access the audit log. +product: '{% data reusables.gated-features.emus %}' +versions: + fpt: '*' +topics: + - Accounts + - Enterprise +--- + +## Acerca de la bitácora de auditoría + +La bitácora de auditoría permite que los propietarios de empresas revisar o exportar rápidamente las acciones que realizaron tanto los propietarios y los miembros de la empresa. Cada entrada de la bitácora de auditoría muestra información del evento. + +- La organización en la que se realizó una acción +- El usuario que realizó la acción +- En qué repositorio se realizó una acción +- La acción que se realizó +- En qué país se realizó la acción +- La fecha y hora en que se produjo la acción + +## Acceder al registro de auditoría + +También puedes acceder a la bitácora de auditoría de tu empresa desde la API de REST. Para obtener más información, consulta la sección "[Administración de GitHub Enterprise](/rest/reference/enterprise-admin#get-the-audit-log-for-an-enterprise)" en la documentación de la API. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.audit-log-tab %} +1. Opcionalmente, sobre la lista de eventos, selecciona el menú desplegable de **Exportar Eventos de Git** o de **Exportar** para elegir las opciones de exportación de eventos de la bitácora de auditoría. ![Menús desplegables de "Exportar Eventos de Git" y "Exportar" para la bitácora de auditoría de la empresa](/assets/images/help/enterprises/audit-log-export-drop-down-menus.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users.md new file mode 100644 index 0000000000..37cc1aeaef --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users.md @@ -0,0 +1,109 @@ +--- +title: Configurar el inicio de sesión único de SAML para los usuarios administrados de Enterprise +shortTitle: SAML para usuarios administrados +intro: 'Puedes administrar el acceso a tu cuenta empresarial automáticamente en {% data variables.product.prodname_dotcom %} si configuras el Inicio de Sesión Único (SSO) de Lenguaje de Marcado para Confirmaciones de Seguridad (SAML).' +product: '{% data reusables.gated-features.emus %}' +versions: + fpt: '*' +topics: + - Accounts + - Enterprise +--- + +## Acerca del inicio de sesión único de SAML para {% data variables.product.prodname_emus %} + +Con {% data variables.product.prodname_emus %}, tu empresa utiliza el SSO de SAML para autenticar a todos los miembros. En vez de iniciar sesión en {% data variables.product.prodname_dotcom %} con un nombre de usuario de {% data variables.product.prodname_dotcom %} y contraseña, los miembros de tu empresa iniciarán sesión con tu IdP. + +{% data variables.product.prodname_emus %} es compatible con los siguientes IdP: + +{% data reusables.enterprise-accounts.emu-supported-idps %} + +Después de que configures el SSO de SAML, te recomendamos que almacenes tus códigos de recuperación para que puedas recuperar el acceso a tu empresa en caso de que no esté disponible tu proveedor de identidad. Para obtener más información, consulta la sección "[Guardar tus códigos de recuperación](#saving-your-recovery-codes)". + +## Configurar el inicio de sesión único de SAML para {% data variables.product.prodname_emus %} + +Para configurar el SSO de SAML para tu {% data variables.product.prodname_emu_enterprise %}, debes configurar una aplicación en tu IdP y luego configurar tu empresa en GitHub.com. Después de que configures el SSO de SAML, puedes configurar el aprovisionamiento de usuarios. + +Para instalar y configurar la aplicación de {% data variables.product.prodname_emu_idp_application %} en tu IdP, debes tener un inquilino y acceso administrativo en un IdP compatible. + +{% note %} + +{% data reusables.enterprise-accounts.emu-password-reset-session %} + +{% endnote %} + +1. [Configurar tu proveedor de identidad](#configuring-your-identity-provider) +2. [Configurar tu empresa](#configuring-your-enterprise) +3. [Habilitar el aprovisionamiento](#enabling-provisioning) + +### Configurar tu proveedor de identidad + +Para configurar tu IdP, sigue las instrucciones que proporciona para configurar la aplicación de {% data variables.product.prodname_emu_idp_application %} en este. + +1. Para instalar la aplicación de {% data variables.product.prodname_emu_idp_application %}, haz clic en el enlace de tu IdP a continuación: + + - [Aplicación de {% data variables.product.prodname_emu_idp_application %} en Azure Active Directory](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/aad.githubenterprisemanageduser?tab=Overview) + - [Aplicación de {% data variables.product.prodname_emu_idp_application %} en Okta](https://www.okta.com/integrations/github-enterprise-managed-user) + +1. Para configurar la aplicación de {% data variables.product.prodname_emu_idp_application %} y tu IdP, haz clic en el siguiente enlace y sigue las instrucciones que proporciona tu IdP: + + - [Tutorial de Azure Active Directory para {% data variables.product.prodname_emus %}](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-enterprise-managed-user-tutorial) + - [Documentación de Okta para {% data variables.product.prodname_emus %}](https://saml-doc.okta.com/SAML_Docs/How-to-Configure-SAML-2.0-for-GitHub-Enterprise-Managed-User.html) + +1. Así que puedes probar y configurar tu empresa, asígnate o asigna al usuario que configurará el SSO de SAML en {% data variables.product.prodname_dotcom %} en la aplicación de {% data variables.product.prodname_emu_idp_application %} en tu IdP. + +1. Para habilitarte para seguir configurando tu empresa en {% data variables.product.prodname_dotcom %}, ubica y anota la siguiente información desde la aplicación que instalaste en tu IdP: + + | Valor | Otros nombres | Descripción | + |:----------------------------------------- |:------------------------------------ |:------------------------------------------------------------------------------------- | + | IdP Sign-On URL | URL de inicio de sesión, URL del IdP | URL de la aplicación en tu IdP | + | IdP Identifier URL | Emisor | El identificador del IdP de los proveedores de servicio para la autenticación de SAML | + | Certificado de firmado, cifrado en Base64 | Certificado público | Certificado público que utiliza el IdP para firmar las solicitudes de autenticación | + +### Configurar tu empresa + +Después de que instalas y configuras la aplicación de {% data variables.product.prodname_emu_idp_application %} en tu proveedor de identidad, puedes configurar tu empresa. + +1. Inicia sesión en {% data variables.product.prodname_dotcom_the_website %} como el usuario configurador para tu empresa nueva con el nombre de usuario **@SHORT-CODE_admin**. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} + +1. En "Inicio de sesión único de SAML", selecciona **Requerir autenticación SAML**. ![Casilla de verificación para habilitar SAML SSO](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) + +1. Debajo de **URL de inicio de sesión**, teclea la terminal HTTPS de tu IdP para solicitudes de inicio de sesión único que anotaste al configurar tu IdP. ![Campo para la URL a la que los miembros serán redireccionados cuando inicien sesión](/assets/images/help/saml/saml_sign_on_url_business.png) + +1. Debajo de **Emisor**, teclea la URL de tu emisor de SAML, el cual anotaste al configurar tu IdP, para verificar la autenticidad de los mensajes enviados. ![Campo para el nombre del emisor SAML](/assets/images/help/saml/saml_issuer.png) + +1. Debajo de **Certificado público**, pega el certificado que anotaste al configurar tu IdP, para verificar las respuestas de SAML. ![Campo para el certificado público de tu proveedor de identidad](/assets/images/help/saml/saml_public_certificate.png) + +1. Para verificar la integridad de las solicitudes de tu emisor de SAML, haz clic en {% octicon "pencil" aria-label="The edit icon" %}. Posteriormente, en los menús desplegables de "Método de firma" y "Método de resumen", elige el algoritmo de hash que utiliza tu emisor de SAML. ![Menús desplegables para los algoritmos de hash del Método de firma y del Método de resumen usados por tu emisor SAML](/assets/images/help/saml/saml_hashing_method.png) + +1. Antes de habilitar el SSO de SAML para tu empresa, para asegurarte de que la información que ingresaste es correcta, haz clic en **Probar la configuración de SAML**. ![Botón para probar la configuración de SAML antes de exigir el inicio de sesión único](/assets/images/help/saml/saml_test.png) + +1. Haz clic en **Save ** (guardar). + + {% note %} + + **Nota:** Cuando requieres el SSO de SAML para tu empresa, el usuario de configuración ya no tendrá acceso a ella, pero permanecerá firmado en GitHub. Únicamente los {% data variables.product.prodname_managed_users %} que haya aprovisionado tu IdP tendrán acceso a la empresa. + + {% endnote %} + +1. Para asegurarte de que aún puedes acceder a tu empresa en caso de que tu proveedor de identidad alguna vez esté indispuesto en el futuro, haz clic en **Descargar**, **Imprimir** o **Copiar** para guardar tus códigos de recuperación. ![Botón para probar la configuración de SAML antes de exigir el inicio de sesión único](/assets/images/help/saml/saml_recovery_code_options.png) + +### Habilitar el aprovisionamiento + +Después de que habilitas el SSO de SAML, habilita el aprovisionamiento. Para obtener más información, consulta la sección "[Configurar el aprovisionamiento de SCIM para los usuarios administrados de las empresas](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users)". + +## Guardar tus códigos de recuperación + +En caso de que tu proveedor de identidad se encuentre indispuesto, puedes utilizar el usuario de configuración y un código de recuperación para iniciar sesión y acceder a tu empresa. Si no guardaste tus códigos de recuperación cuando configuraste el SSO de SAML, aún puedes acceder a ellos desde los ajustes de tu empresa. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} + +1. Debajo de "Requerir la autenticación de SAML", haz clic en **Guardar tus códigos de recuperación**. ![Botón para probar la configuración de SAML antes de exigir el inicio de sesión único](/assets/images/help/enterprises/saml-recovery-codes-link.png) + +2. Para guardar tus códigos de recuperación, haz clic en **Descargar**, **Imprimir** o **Copiar**. ![Botón para probar la configuración de SAML antes de exigir el inicio de sesión único](/assets/images/help/saml/saml_recovery_code_options.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md new file mode 100644 index 0000000000..ae368a224e --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md @@ -0,0 +1,76 @@ +--- +title: Configurar el aprovisionamiento de SCIM para los Usuarios Administrados Empresariales con Okta +shortTitle: Configura el aprovisionamiento con Okta +intro: Puedes aprovisionar usuarios nuevos y administrar la membrecía de tu empresa y equipos utilizando Okta como tu proveedor de identidad. +product: '{% data reusables.gated-features.emus %}' +versions: + fpt: '*' +redirect_from: + - /early-access/github/articles/configuring-provisioning-for-managed-users-with-okta +topics: + - Accounts + - Enterprise +--- + +## Acerca del aprovisionamiento con Okta + +Puedes utilizar los {% data variables.product.prodname_emus %} con Okta como tu proveedor de identidad para aprovisionar cuentas nuevas, administrar la membrecía empresarial y administrar las membrecías de equipo para las organizaciones de tu empresa. Para obtener más información sobre cómo aprovisionar para los {% data variables.product.prodname_emus %}, consulta la sección "[Configurar el aprovisionamiento de SCIM para los usuarios administrados empresariales](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users)". + +Antes de que puedas configurar el aprovisionamiento con Okta, debes configurar el inicio de sesión único de SAML. Para obtener más información, consulta la sección "[Configurar el inicio de sesión único de SAML para los Usuarios Administrados Empresariales](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)". + +Para configurar el aprovisionamiento con Okta, debes configurar el nombre de tu empresa en la aplicación de {% data variables.product.prodname_emu_idp_application %} e ingresar el token de acceso personal del usuario de configuración. Entonces podrás aprovisionar usuarios en Okta. + +## Características compatibles + +{% data variables.product.prodname_emus %} es compatible con muchas características de aprovisionamiento en Okta. + +| Característica | Descripción | +| --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| Subir Usuarios Nuevos | Los usuarios que se asignan a la aplicación de {% data variables.product.prodname_emu_idp_application %} en Okta se crean automáticamente en la empresa en {% data variables.product.product_name %}. | +| Subir la Actualización de Perfil | Las actualizaciones que se hacen al perfil del usuario en Oktan se subirán a {% data variables.product.product_name %}. | +| Grupos de Subida | Los Grupos en Okta que se hayan asignado a la aplicación de {% data variables.product.prodname_emu_idp_application %} como Grupos de Subida se crearán automáticamente en la empresa en {% data variables.product.product_name %}. | +| Subir Desactivaciones de Usuarios | El desasignar al usuario de la aplicación de {% data variables.product.prodname_emu_idp_application %} en Okta lo inhabilitará en {% data variables.product.product_name %}. El usuario no podrá iniciar sesión, pero la información del usuario se mantendrá. | +| Reactivar Usuarios | Se habilitarán los usuarios en Okta cuyas cuentas de Okta se reactiven y quienes se asignen de vuelta a la aplicación de {% data variables.product.prodname_emu_idp_application %}. | + +{% note %} + +**Nota:** {% data variables.product.prodname_emus %} no es compatible con la modificación de nombres de usuario. + +{% endnote %} + +## Configurar el nombre de tu empresa + +Después de que se haya creado tu {% data variables.product.prodname_emu_enterprise %}, puedes comenzar a configurar el aprovisionamiento configurando el nombre de tu empresa en Okta. + +1. Navega a tu aplicación de {% data variables.product.prodname_emu_idp_application %} en Okta. +1. Haz clic en la pestaña **Iniciar sesión**. +1. Para hacer cambios, haz clic en **Editar**. +1. Debajo de "Ajustes avanzados de inicio de sesión", en la caja de texto de "Nombre de empresa", teclea el nombre de tu empresa. Por ejemplo, si accedes a tu empresa en `https://github.com/enterprises/octoinc`, tu nombre de empresa será "octoinc". ![Captura de pantalla del campo de Nombre de Empresa en Okta](/assets/images/help/enterprises/okta-emu-enterprise-name.png) +1. Para guardar el nombre de tu empresa, haz clic en **Guardar**. + +## Configurar el aprovisionamiento + +Después de que configures el nombre de tu empresa, puedes proceder a configurar los ajustes de aprovisionamiento. + +Para configurar el aprovisionamiento, el usuario de configuración con el nombre de usuario **@SHORT-CODE_admin** necesitará aprovisionar un token de acceso personal con el alcance **admin:enterprise**. Para obtener más información sobre cómo crear un token nuevo, consulta la sección [Crear un token de acceso personal](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users#creating-a-personal-access-token)". + +1. Navega a tu aplicación de {% data variables.product.prodname_emu_idp_application %} en Okta. +1. Haz clic en la pestaña de **Aprovisionamiento**. +1. En el menú de configuración, haz clic en ** integración**. +1. Para hacer cambios, haz clic en **Editar**. +1. Selecciona **Habilitar la Integraciòn de la API**. +1. En el campo de "Token de la API", ingresa el token de acceso personal con el alcance **admin:enterprise** que pertenece al usuario de configuración. ![Captura de pantalla que muestra el campo de Token de la API en Okta](/assets/images/help/enterprises/okta-emu-token.png) +1. Haz clic en **Probar las credenciales de la API**. Si la prueba tiene éxito, se mostrará un mensaje de verificación en la parte superior de la pantalla. +1. Para guardar el token, haz clic en **Guardar**. +1. En el menú de configuración, haz clic en **A la App**. ![Captura de pantalla que muestra el elemento de menú "A la App" en Okta](/assets/images/help/enterprises/okta-emu-to-app-menu.png) +1. A la derecha de "Aprovisionamiento a la App", para permitir que se hagan cambios, haz clic en **Editar**. +1. Selecciona **Habilitar** para **Crear usuarios**. **Actualizar atributos de usuarios** y **Desactivar usuarios**. ![Captura de pantalla que muestra las opciones de aprovisionamiento en Okta](/assets/images/help/enterprises/okta-emu-provisioning-to-app.png) +1. Para finalizar la configuración del aprovisionamiento, haz clic en **Guardar**. + +## Asignar usuarios + +Después de haber configurado el SSO de SAML y el aprovisionamiento, podrás aprovisionar usuarios nuevos en {% data variables.product.prodname_dotcom_the_website %} asignando a los usuarios a la aplicación de {% data variables.product.prodname_emu_idp_application %}. También puedes administrar la membrecía organizacional automáticamente asignando grupos a la aplicción como grupos de subida y conectando dichos grupos de subida a los equipos de tus organizaciones. Para obtener más información sobre cómo administrar los equipos, consulta la sección "[Administrar las membrecías de los quipos con grupos de proveedor de identidad](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)". + +Cuando asignas usuarios, puedes utilizar el atributo de "Roles" en la aplicación de {% data variables.product.prodname_emu_idp_application %} para configurar el rol de un usuario en tu empresa en {% data variables.product.product_name %}. Para obtener más información sobre los roles, consulta la sección "[Roles en una empresa](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)". + +![Captura de pantalla que muestra las opciones de roles para el usuario aprovisionado en Okta](/assets/images/help/enterprises/okta-emu-user-role.png) diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md new file mode 100644 index 0000000000..ea324bba5e --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md @@ -0,0 +1,54 @@ +--- +title: Configurar el aprovisionamiento de SCIM para los Usuarios Administrados Empresariales +shortTitle: Aprovisionar a los usuarios administrados +intro: Puedes configurar tu proveedor de identidad para que aprovisione usuarios nuevos y administre sus membrecías en tu empresa y equipos. +product: '{% data reusables.gated-features.emus %}' +versions: + fpt: '*' +topics: + - Accounts + - Enterprise +--- + +## Acerca del aprovisionamiento para los {% data variables.product.prodname_emus %} + +Puedes configurar el aprovisionamiento para que {% data variables.product.prodname_emus %} creen, administren y desactiven cuentas de usuario para tus miembros empresariales. Cuando configuras el aprovisionamiento para {% data variables.product.prodname_emus %}, los usuarios que se asignaron a la aplicación de {% data variables.product.prodname_emu_idp_application %} en tu proveedor de identidad se aprovisionan como cuentas de usuario nuevas en {% data variables.product.prodname_dotcom %} a través de SCIM y los usuarios se agregan a tu empresa. + +Cuando actualzias la información asociada con la identidad de un usuario en tu IdP, este actualizará la cuenta de usuario en GitHub.com. Cuando desasignas al usuario desde la aplicación de {% data variables.product.prodname_emu_idp_application %} o cuando desactivas una cuenta de usuario en tu IdP, dicho IdP se comunicará con {% data variables.product.prodname_dotcom %} para invalidar las sesiones de SAML e inhabilitar la cuenta del miembro. La información de la cuenta inhabilitada se mantiene y su nombre de usuario se cambia por un hash del nombre de usuario original con el código corto anexo. Si reasignas a un usuario a la aplicación de {% data variables.product.prodname_emu_idp_application %} o reactivas su cuenta en tu IdP, la cuenta de {% data variables.product.prodname_managed_user %} en {% data variables.product.prodname_dotcom %} se reactivará y el nombre de usuario se restablecerá. + +Los grupos en tu IdP pueden utilizarse para administrar la membrecía de equipo dentro de las organizaciones de tu empresa, permitiéndote configurar el acceso y los permisos del repositorio mediante tu IdP. Para obtener más información, consulta la sección "[Administrar las membrecías de equipo con los grupos de proveedor de identidades](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)". + +## Prerrequisitos + +Antes de que puedas configurar el aprovisionamiento para {% data variables.product.prodname_emus %}, debes configurar el inicio de sesión único de SAML. Para obtener más información, consulta la sección "[Configurar el inicio de sesión único de SAML para los Usuarios Administrados Empresariales](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)". + +## Crear un token de acceso personal + +Para configurar el aprovisionamiento de tu {% data variables.product.prodname_emu_enterprise %}, necesitas un token de acceso personal con el alcance de **admin:enterprise** que pertenezca el usuario de configuración. + +{% warning %} + +**Advertencia:** Si el token vence o un usuario aprovisionado lo crea, el aprovisionamiento de SCIM podría dejar de funcionar inesperadamente. Asegúrate de crear el token mientras tienes iniciada la sesión como usuario de configuración y que el vencimiento del token esté configurado como "Sin vencimiento". + +{% endwarning %} + +1. Inicia sesión en {% data variables.product.prodname_dotcom_the_website %} como el usuario configurador para tu empresa nueva con el nombre de usuario **@SHORT-CODE_admin**. +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.developer_settings %} +{% data reusables.user_settings.personal_access_tokens %} +{% data reusables.user_settings.generate_new_token %} +1. Debajo de **Nota**, proporciona un nombre descriptivo a tu token. ![Captura de pantalla que muestra el nombre del token](/assets/images/help/enterprises/emu-pat-name.png) +1. Selecciona el menú desplegable de **Vencimiento** y luego haz clic en **Sin vencimiento**. ![Captura de pantalla que muestra el vencimiento de un token configurado como "sin vencimiento"](/assets/images/help/enterprises/emu-pat-no-expiration.png) +1. Selecciona el alcance **admin:enterprise**. ![Captura de pantalla que muestra el alcance admin:enterprise](/assets/images/help/enterprises/enterprise-pat-scope.png) +1. Haz clic en **Generar token**. ![Generar un botón para el token](/assets/images/help/settings/generate_token.png) +1. Para copiar el token a tu portapapeles, haz clic en el {% octicon "paste" aria-label="The copy icon" %}. ![Token recién creado](/assets/images/help/settings/personal_access_tokens.png) +2. Para guardar el token para utilizarlo posteriormente, almacénalo de forma segura en un administrador de contraseñas. + +## Configurar el aprovisionamiento para {% data variables.product.prodname_emus %} + +Después de crear tu token de acceso personal y almacenarlo de forma segura, puedes configurar el aprovisionamiento en tu proveedor de identidad. + +Para configurar a Azure Active Directory para que aprovisione usuarios para tu {% data variables.product.prodname_emu_enterprise %}, consulta el [Tutorial: Configurar a los Usuarios Administrados Empresariales de Github para un aprovisionamiento de usuarios automático](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-enterprise-managed-user-provisioning-tutorial) en la documentación de Azure AD. + +Para configurar Okta para que aprovisione usuarios para tu {% data variables.product.prodname_emu_enterprise %}, consulta la sección "[Configurar el aprovisionamiento de SCIM para los Usuarios Administrados Empresariales con Okta](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users-with-okta)". + diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/index.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/index.md new file mode 100644 index 0000000000..2a1d30cb56 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/index.md @@ -0,0 +1,19 @@ +--- +title: Administrar a tus usuarios empresariales con tu proveedor de identidad +shortTitle: Administrar usuarios con tu IdP +product: '{% data reusables.gated-features.emus %}' +intro: Puedes administrar la identidad y el acceso con tu proveedor de identidad y aprovisionar cuentas que solo puedan contribuir con tu empresa. +versions: + fpt: '*' +topics: + - Enterprise + - Accounts +children: + - /about-enterprise-managed-users + - /configuring-saml-single-sign-on-for-enterprise-managed-users + - /configuring-scim-provisioning-for-enterprise-managed-users + - /configuring-scim-provisioning-for-enterprise-managed-users-with-okta + - /managing-team-memberships-with-identity-provider-groups + - /auditing-activity-in-your-enterprise +--- + diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups.md new file mode 100644 index 0000000000..a0745944a5 --- /dev/null +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups.md @@ -0,0 +1,67 @@ +--- +title: Administrar membrecías de equipo con grupos de proveedor de identidad +shortTitle: Administrar equipos con tu IdP +intro: 'Puedes administrar la membrecía de los equipos en {% data variables.product.product_name %} mediante tu proveedor de identidad (IdP) si conectas grupos de IdP con tu {% data variables.product.prodname_emu_enterprise %}.' +product: '{% data reusables.gated-features.emus %}' +versions: + fpt: '*' +topics: + - Accounts + - Enterprise +--- + +## Acerca de la administración de equipos con {% data variables.product.prodname_emus %} + +Con {% data variables.product.prodname_emus %}, puedes administrar la membrecía de los equipos dentro de tu empresa a través de tu IdP. Cuando conectas un equipo en una de las organizaciones de tu empresa a un grupo de IdP, los cambios a la membrecía desde el grupo de IdP se reflejan automáticamente en tu empresa, lo cual reduce la necesidad de hacer actualizaciones manuales y scripts personalizados. + +Cuando un cambio a un grupo de IdP o una conexión de equipo nueva da como resultado que un {% data variables.product.prodname_managed_user %} se una a un equipo en una organización de la cual no fueran ya miembros, el {% data variables.product.prodname_managed_user %} se agregará automáticamente a dicha organización. Los propietarios de las organizaciones también pueden administrar las membrecías organizacionales manualmente. Cuando desconectas un grupo de un equipo, los usuarios que se convirtieron en miembros de la organización a través de la membrecía de equipo se eliminan de esta si no se les asignó una membrecía en dicha organización por cualquier otro medio. + +Puedes conectar a un equipo de tu empresa a un grupo de IdP. Puedes asignar el mismo grupo de IdP a varios equipos de tu empresa. + +Si estás conectando un equipo a un grupo de IdP, primero debes eliminar a cualquier miembro que se haya agregado manualmente. Después de que conectas a un equipo de tu empresa a un grupo de IdP, tu administrador de IdP debe hacer cambios de membrecía de equipo a través de tu proveedor de identidad. No puedes administrar la membrecía de los equipos en {% data variables.product.prodname_dotcom_the_website %}. + +Cuando cambia la membrecía de grupo en tu IdP, este envía una solicitud de SCIM con los cambios a {% data variables.product.prodname_dotcom_the_website %} de acuerdo con la programación que determinó tu IdP, así que el cambio podría no reflejarse de inmediato. Cualquier solicitud que cambie la membrecía de organización o equipo de se registrará en la bitácora de auditoría como cambios que realizó la cuenta que se utilizó para configurar el aprovisionamiento de usuarios. + +Los equipos que se conectan con los grupos de IdP no pueden ser equipos padres ni hijos de otro equipo. Si el equipo que quieres conectar a un grupo de IdP es un equipo padre o hijo, te recomendamos crear un equipo nuevo o eliminar las relaciones anidadas que hacen de tu equipo un equipo padre. + +Para administrar el acceso a los repositorios de cualquier equipo en tu empresa, incluyendo los equipos conectados a un grupo de IdP, debes hacer cambios en {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta la sección "[Administrar el acceso de un equipo a un repositorio organizacional](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)". + +## Crear un equipo nuevo conectado a un grupo de IdP + +Cualquier miembro de una organización puede crear un equipo nuevo y conectarlo a un grupo de IdP. + +{% data reusables.profile.access_org %} +{% data reusables.user_settings.access_org %} +{% data reusables.organizations.new_team %} +{% data reusables.organizations.team_name %} +{% data reusables.organizations.team_description %} +1. Para conectar a un equipo, selecciona el menú desplegable de "Grupos de Proveedor de Identidad" y haz clic en aquél que quieras conectar. ![Menú desplegable para elegir los grupos de proveedor de identidad](/assets/images/help/teams/choose-an-idp-group.png) +{% data reusables.organizations.team_visibility %} +{% data reusables.organizations.create_team %} + +## Administrar la conexión entre un equipo existente y un grupo de IdP + +Los propietarios organizacionales y mantenedores de equipos pueden administrar la conexión existente entre un grupo de IdP y un equipo. + +{% note %} + +**Nota**: Antes de que conectes un equipo existente de {% data variables.product.prodname_dotcom_the_website %} a un grupo de IdP por primera vez, todos los miembros del equipo en {% data variables.product.prodname_dotcom_the_website %} deben eliminarse primero. Para obtener más información, consulta la sección "[Eliminar miembros organizacionales de un equipo](/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team)". + +{% endnote %} + +{% data reusables.profile.access_profile %} + +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +1. Opcionalmente, debajo de "Grupo de Proveedor de Identidad", a la derecha del grupo de IdP que quieres desconectar, haz clic en {% octicon "x" aria-label="X symbol" %}. ![Deselecciona un grupo IdP conectado desde el equipo de GitHub](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png) +1. Para conectar un grupo de IdP, debajo de "Grupo de Proveedor de Identidad"; selecciona el menú desplegable y haz clic en un grupo de proveedor de identidad de la lista. ![Menú desplegable para elegir un grupo de proveedor de identidad](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png) +1. Haz clic en **Guardar cambios**. + +## Ver los grupos de IdP y equipos conectados + +Puedes revisar una lista de proveedores de IdP, cualquier equipo conectado a un grupo de IdP y ver la membrecía de cada grupo de IdP en {% data variables.product.product_name %}. Debes editar la membrecía de un grupo en tu IdP. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.identity-provider-tab %} +1. Debajo de "Grupos de Proveedor de Identidad (IdP)", revisa la lista de grupos de IdP. diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account.md index cdff350d7e..4e6153dd91 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account.md @@ -42,7 +42,9 @@ Puedes inhabilitar todos los flujos de trabajo de una empresa o configurar una p ## Configurar las aprobaciones requeridas para los flujos de trabajo desde las bifurcaciones pùblicas -{% data reusables.actions.workflow-run-approve-public-fork %} Puedes configurar este comportamiento para tu empresa utilizando el siguiente procedimiento. +{% data reusables.actions.workflow-run-approve-public-fork %} + +You can configure this behavior for your enterprise using the procedure below. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} diff --git a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-repository-management-policies-in-your-enterprise-account.md b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-repository-management-policies-in-your-enterprise-account.md index 4d92d69cc3..2a02b1f71e 100644 --- a/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-repository-management-policies-in-your-enterprise-account.md +++ b/translations/es-ES/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-repository-management-policies-in-your-enterprise-account.md @@ -17,14 +17,14 @@ shortTitle: Políticas para los repositorios Para obtener más información, consulta "[Niveles de permiso del repositorio para una organización](/articles/permission-levels-for-an-organization)". -## Enforcing a policy on base repository permissions +## Requerir una política en los permisos base del repositorio -Across all organizations owned by your enterprise account, you can set a base repository permission level (none, read, write, or admin) for organization members, or allow owners to administer the setting on the organization level. +En todas las organizaciones que pertenecen a tu cuenta de empresa, puedes establecer un nivel de permiso base para los repositorios (ninguno, lectura, escritura o administrador) para los miembros de la organización o permitir que los propietarios administren los parámetros de configuración a nivel de la organización. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} -4. On the **Repository policies** tab, under "Base permissions", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} -5. Under "Base permissions", use the drop-down menu and choose a policy. ![Menú desplegable con opciones de políticas de permisos de repositorios](/assets/images/help/business-accounts/repository-permissions-policy-drop-down.png) +4. En la pestaña **Políticas del repositorio**, en "Permisos base", revisa la información acerca de los cambios en la configuración. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} +5. En "Permisos base", usa el menú desplegable y elige una política. ![Menú desplegable con opciones de políticas de permisos de repositorios](/assets/images/help/business-accounts/repository-permissions-policy-drop-down.png) ## Hacer cumplir una política sobre la creación de repositorios diff --git a/translations/es-ES/content/github/site-policy/github-codespaces-privacy-statement.md b/translations/es-ES/content/github/site-policy/github-codespaces-privacy-statement.md index 580ec9f90b..a21161a27c 100644 --- a/translations/es-ES/content/github/site-policy/github-codespaces-privacy-statement.md +++ b/translations/es-ES/content/github/site-policy/github-codespaces-privacy-statement.md @@ -1,5 +1,5 @@ --- -title: GitHub Codespaces Privacy Statement +title: Declaración de Privacidad de GitHub Codespaces redirect_from: - /github/site-policy/github-codespaces-privacy-policy versions: @@ -9,14 +9,14 @@ topics: - Legal --- -Effective Date: August 10, 2021 +Fecha Efectiva: 10 de agosto de 2021 -Use of GitHub Codespaces is subject to the [GitHub Privacy Statement](/github/site-policy/github-privacy-statement). +El uso de los GitHub Codespaces está sujeto a la [Declaración de Privacidad de GitHub](/github/site-policy/github-privacy-statement). -Activity on github.dev is subject to [GitHub's Beta Previews terms](/github/site-policy/github-terms-of-service#j-beta-previews) +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) -## Using Visual Studio Code +## Utilizar Visual Studio Code -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 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. -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. +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. diff --git a/translations/es-ES/content/github/site-policy/github-data-protection-agreement.md b/translations/es-ES/content/github/site-policy/github-data-protection-agreement.md new file mode 100644 index 0000000000..f587461a0f --- /dev/null +++ b/translations/es-ES/content/github/site-policy/github-data-protection-agreement.md @@ -0,0 +1,974 @@ +--- +title: GitHub Data Protection Agreement +redirect_from: + - /github/site-policy/github-data-protection-addendum + - /github/site-policy-deprecated/github-data-protection-addendum + - /github/site-policy/github-data-protection-agreement-non-enterprise-customers +versions: + fpt: '*' +--- + +## Introducción + +The parties agree that this GitHub Data Protection Agreement (“**DPA**”) sets forth their obligations with respect to the processing and security of Personal Data and, where explicitly stated in the DPA Terms, Customer Data in connection with the Online Services provided by GitHub, Inc. (“**GitHub**”). The DPA (including its Appendix and Attachments) is between GitHub and any customer receiving Online Services from GitHub based on the GitHub Customer Agreement (“**Customer**”), and is incorporated by reference into the GitHub Customer Agreement. + +In the event of any conflict or inconsistency between the DPA Terms and any other terms in the GitHub Customer Agreement, the DPA Terms will prevail. The provisions of the DPA Terms supersede any conflicting provisions of the GitHub Privacy Statement that otherwise may apply to processing of Personal Data. For clarity, the Standard Contractual Clauses prevail over any other term of the DPA Terms. + +### Applicable DPA Terms and Updates + +#### Limits on Updates + +When Customer renews or purchases a new subscription to an Online Service, the then-current DPA Terms will apply and will not change during the term of that new subscription for that Online Service. + +#### New Features, Supplements, or Related Software + +Notwithstanding the foregoing limits on updates, when GitHub introduces features, supplements or related software that are new (i.e., that were not previously included with the subscription), GitHub may provide terms or make updates to the DPA that apply to Customer’s use of those new features, supplements or related software. If those terms include any material adverse changes to the DPA Terms, GitHub will provide Customer a choice to use the new features, supplements, or related software, without loss of existing functionality of a generally available Online Service. If Customer does not use the new features, supplements, or related software, the corresponding new terms will not apply. + +#### Government Regulation and Requirements + +Notwithstanding the foregoing limits on updates, GitHub may modify or terminate an Online Service in any country or jurisdiction where there is any current or future government requirement or obligation that (1) subjects GitHub to any regulation or requirement not generally applicable to businesses operating there, (2) presents a hardship for GitHub to continue operating the Online Service without modification, and/or (3) causes GitHub to believe the DPA Terms or the Online Service may conflict with any such requirement or obligation. + +### Electronic Notices + +GitHub may provide Customer with information and notices about Online Services electronically, including via email, or through a web site that GitHub identifies. Notice is given as of the date it is made available by GitHub. + +### Prior Versions + +The DPA Terms provide terms for Online Services that are currently available. For earlier versions of the DPA Terms, Customer may contact its reseller or GitHub Account Manager. + +## Definiciones + +Capitalized terms used but not defined in this DPA will have the meanings provided in the GitHub Customer Agreement. The following defined terms are used in this DPA: + +“**CCPA**” means the California Consumer Privacy Act as set forth in Cal. Civ. Code §1798.100 et seq. and its implementing regulations. + +“**Customer Data**” means all data, including all text, sound, video, or image files, and software, that are provided to GitHub by, or on behalf of, Customer through use of the Online Service. + +“**Data Protection Requirements**” means the GDPR, Local EU/EEA Data Protection Laws, CCPA, and any applicable laws, regulations, and other legal requirements relating to (a) privacy and data security; and (b) the use, collection, retention, storage, security, disclosure, transfer, disposal, and other processing of any Personal Data. + +“**Diagnostic Data**” means data collected or obtained by GitHub from software that is locally installed by Customer in connection with the Online Service. Diagnostic Data may also be referred to as telemetry. Diagnostic Data does not include Customer Data, Service Generated Data, or Professional Services Data. + +“**DPA Terms**” means both the terms in this DPA and any Online Service-specific terms in the GitHub Customer Agreement that specifically supplement or modify the privacy and security terms in this DPA for a specific Online Service (or feature of an Online Service). In the event of any conflict or inconsistency between the DPA and such Online Service-specific terms, the Online Service-specific terms shall prevail as to the applicable Online Service (or feature of that Online Service). + +“**GDPR**” means Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation). In connection with the United Kingdom, “GDPR” means Regulation (EU) 2016/679 as transposed into national law of the United Kingdom by the UK European Union (Withdrawal) Act 2018 and amended by the UK Data Protection, Privacy and Electronic Communications (Amendments etc.) (EU Exit) Regulations 2019 (as may be amended from time to time). + +“**Local EU/EEA Data Protection Laws**” means any subordinate legislation and regulation implementing the GDPR. + +“**GDPR Related Terms**” means the terms in Attachment 3, under which GitHub makes binding commitments regarding its processing of Personal Data as required by Article 28 of the GDPR. + +“**GitHub Affiliate**” means any entity that directly or indirectly controls, is controlled by or is under common control with GitHub. + +“**GitHub Customer Agreement**” means the service or other agreement(s) entered into by Customer with GitHub for Online Services. + +“**GitHub Privacy Statement**” means the GitHub privacy statement available at https://docs.github.com/en/github/site-policy/github-privacy-statement. + +“**Online Service**” means any service or software provided by GitHub to Customer under the GitHub Customer Agreement agreed upon with Customer, including Previews, updates, patches, bug fixes, and technical support. + +“**Personal Data**” means any information relating to an identified or identifiable natural person. An identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person. + +“**Preview**” means Online Services provided for preview, evaluation, demonstration or trial purposes, or pre-release versions of the Online Services. + +“**Professional Services Data**” means all data, including all text, sound, video, image files or software, that are provided to GitHub, by or on behalf of a Customer (or that Customer authorizes GitHub to obtain from an Online Service) or otherwise obtained or processed by or on behalf of GitHub through an engagement with GitHub to obtain Professional Services. Professional Services Data includes Support Data. + +“**Service Generated Data**” means data generated or derived by GitHub through the operation of an Online Service. Service Generated Data does not include Customer Data, Diagnostic Data, or Professional Services Data. + +“**Standard Contractual Clauses**” means either of the following sets of Standard Contractual Clauses, as applicable in the individual case to the transfer of personal data according to the section of this DPA entitled “Data Transfers and Location” below: +- the Standard Contractual Clauses (MODULE TWO: Transfer controller to processor), dated 4 June 2021, for the transfer of personal data to third countries pursuant to Regulation (EU) 2016/679 of the European Parliament and of the Council, as described in Article 46 of the GDPR and approved by European Commission Implementing Decision (EU) 2021/91 (“Standard Contractual Clauses (EU/EEA)”). The Standard Contractual Clauses (EU/EEA) are set forth in Attachment 1. +- the Standard Contractual Clauses (Processors), dated 5 February 2010, for the transfer of personal data to processors established in third countries which do not ensure an adequate level of data protection, as described in Article 46 of the GDPR, approved by European Commission Decision 2010/87/EU and recognized by the regulatory or supervisory authorities of the United Kingdom for use in connection with data transfers from the United Kingdom (“Standard Contractual Clauses (UK)”). The Standard Contractual Clauses (UK) are set forth in Attachment 2. + +“**Subprocessor**” means other processors used by GitHub to process Personal Data on behalf of Customer in connection with the Online Services, as described in Article 28 of the GDPR. + +“**Support Data**” means all data, including all text, sound, video, image files, or software, that are provided to GitHub by or on behalf of Customer (or that Customer authorizes GitHub to obtain from an Online Service) through an engagement with GitHub to obtain technical support for Online Services covered under this agreement. Support Data is a subset of Professional Services Data. + +Lower case terms used but not defined in this DPA, such as “personal data breach”, “processing”, “controller”, “processor”, “profiling”, “personal data”, and “data subject” will have the same meaning as set forth in Article 4 of the GDPR, irrespective of whether GDPR applies. The terms “data importer” and “data exporter” have the meanings given in the Standard Contractual Clauses. + +For clarity, and as detailed above, data defined as Customer Data, Diagnostic Data, Service Generated Data, and Professional Services Data may contain Personal Data. For illustrative purposes, please see the chart inserted below: + +
    + personal_data_types +
    + +Above is a visual representation of the data types defined in the DPA. All Personal Data is processed as a part of one of the other data types (all of which also include non-personal data). Support Data is a sub-set of Professional Services Data. Except where explicitly stated otherwise, the DPA Terms exclusively apply to Personal Data. + +## General Terms + +### Compliance with Laws + +GitHub will comply with all laws and regulations applicable to its provision of the Online Services, including security breach notification law and Data Protection Requirements. However, GitHub is not responsible for compliance with any laws or regulations applicable to Customer or Customer’s industry that are not generally applicable to information technology service providers. GitHub does not determine whether Customer Data includes information subject to any specific law or regulation. All Security Incidents are subject to the Security Incident Notification terms below. + +Customer must comply with all laws and regulations applicable to its use of Online Services, including laws related to biometric data, confidentiality of communications, and Data Protection Requirements. Customer is responsible for determining whether the Online Services are appropriate for storage and processing of information subject to any specific law or regulation and for using the Online Services in a manner consistent with Customer’s legal and regulatory obligations. Customer is responsible for responding to any request from a third party regarding Customer’s use of an Online Service, such as a request to take down content under the U.S. Digital Millennium Copyright Act or other applicable laws. + +## Protección de datos + +Terms This section of the DPA includes the following subsections: +- Ámbito +- Nature of Data Processing; Ownership +- Disclosure of Processed Data +- Processing of Personal Data; GDPR +- Data Security +- Security Incident Notification +- Data Transfers and Location +- Data Retention and Deletion +- Processor Confidentiality Commitment +- Notice and Controls on Use of Subprocessors +- Educational Institutions +- CJIS Customer Agreement, HIPAA Business Associate, Biometric Data +- California Consumer Privacy Act (CCPA) +- How to Contact GitHub +- Appendix A – Security Measures + +### Ámbito + +The DPA Terms apply to all Online Services. + +Previews may employ lesser or different privacy and security measures than those typically present in the Online Services. Unless otherwise noted, Customer should not use Previews to process Personal Data or other data that is subject to legal or regulatory compliance requirements. The following terms in this DPA do not apply to Previews: Processing of Personal Data; GDPR, Data Security, and California Consumer Privacy Act. + +### Nature of Data Processing; Ownership + +Except as otherwise stated in the DPA Terms, GitHub will use and otherwise process Customer Data and Personal Data as described and subject to the limitations provided below (a) to provide Customer the Online Service in accordance with Customer’s documented instructions, and/or (b) for GitHub’s legitimate business operations incident to delivery of the Online Services to Customer. As between the parties, Customer retains all right, title and interest in and to Customer Data. GitHub acquires no rights in Customer Data other than the rights Customer grants to GitHub in this section. This paragraph does not affect GitHub’s rights in software or services GitHub licenses to Customer. + +#### Processing to Provide Customer the Online Services + +For purposes of this DPA, “to provide” an Online Service consists of: +- Delivering functional capabilities as licensed, configured, and used by Customer and its users, including providing personalized user experiences; +- Troubleshooting (e.g., preventing, detecting, and repairing problems); and +- Ongoing improvement (e.g., installing the latest updates and making improvements to user productivity, reliability, efficacy, and security). + +When providing Online Services, GitHub will use or otherwise process Personal Data only on Customer’s behalf and in accordance with Customer’s documented instructions. + +#### Processing for GitHub’s Legitimate Business Operations + +For purposes of this DPA, “GitHub’s legitimate business operations” consist of the following, each as incident to delivery of the Online Services to Customer: (1) billing and account management; (2) compensation (e.g., calculating employee commissions and partner incentives); (3) internal reporting and business modeling (e.g., forecasting, revenue, capacity planning, product strategy); (4) combatting fraud, abuse, cybercrime, or cyber-attacks that may affect GitHub or Online Services; (5) improving the core functionality of accessibility, privacy or energy-efficiency; (6) financial reporting and compliance with legal obligations (subject to the limitations on disclosure of Processed Data outlined below); (7) the creation or management of end user accounts and profiles by GitHub for individual users of Customer (except where Customer creates, manages or otherwise controls such end user accounts or profiles itself); and (8) other purposes pertaining to Personal Data not provided by Customer for storage in GitHub repositories or in connection with Professional Services. + +When processing for GitHub’s legitimate business operations, GitHub will not use or otherwise process Personal Data for: (a) user profiling, (b) advertising or similar commercial purposes, (c) data selling or brokering, or (d) any other purpose, other than for the purposes set out in this section. + +### Disclosure of Processed Data + +GitHub will not disclose or provide access to any Processed Data except: (1) as Customer directs; (2) as described in this DPA; or (3) as required by law. For purposes of this section, “Processed Data” means: (a) Customer Data; (b) Personal Data and (c) any other data processed by GitHub in connection with the Online Service that is Customer’s confidential information under the GitHub Customer Agreement. All processing of Processed Data is subject to GitHub’s obligation of confidentiality under the GitHub Customer Agreement. + +GitHub will not disclose or provide access to any Processed Data to law enforcement unless required by law. If law enforcement contacts GitHub with a demand for Processed Data, GitHub will attempt to redirect the law enforcement agency to request that data directly from Customer. If compelled to disclose or provide access to any Processed Data to law enforcement, GitHub will promptly notify Customer and provide a copy of the demand, unless legally prohibited from doing so. + +Upon receipt of any other third-party request for Processed Data, GitHub will promptly notify Customer unless prohibited by law. GitHub will reject the request unless required by law to comply. If the request is valid, GitHub will attempt to redirect the third party to request the data directly from Customer. + +GitHub will not provide any third party: (a) direct, indirect, blanket, or unfettered access to Processed Data; (b) platform encryption keys used to secure Processed Data or the ability to break such encryption; or (c) access to Processed Data if GitHub is aware that the data is to be used for purposes other than those stated in the third party’s request. + +In support of the above, GitHub may provide Customer’s basic contact information to the third party. + +### Processing of Personal Data; GDPR + +All Personal Data processed by GitHub in connection with the Online Services is obtained as part of either Customer Data, Professional Services Data (including Support Data), Diagnostic Data, or Service Generated Data. Personal Data provided to GitHub by, or on behalf of, Customer through use of the Online Service is also Customer Data. Pseudonymized identifiers may be included in Diagnostic Data or Service Generated Data and are also Personal Data. Any Personal Data pseudonymized, or de-identified but not anonymized, or Personal Data derived from Personal Data is also Personal Data. + +To the extent GitHub is a processor or subprocessor of Personal Data subject to the GDPR, the GDPR Related Terms in Attachment 3 govern that processing and the parties also agree to the following terms in this sub-section (“Processing of Personal Data; GDPR”): + +#### Processor and Controller Roles and Responsibilities + +Customer and GitHub agree that Customer is the controller of Personal Data and GitHub is the processor of such data, except (a) when Customer acts as a processor of Personal Data, in which case GitHub is a subprocessor; or (b) as stated otherwise in the GitHub Customer Agreement or this DPA. When GitHub acts as the processor or subprocessor of Personal Data, it will process Personal Data only on Customer’s behalf and in accordance with documented instructions from Customer. Customer agrees that its GitHub Customer Agreement (including the DPA Terms and any applicable updates), along with the product documentation and Customer’s use and configuration of features in the Online Services, are Customer’s complete documented instructions to GitHub for the processing of Personal Data. Information on use and configuration of the Online Services can be found at https://docs.github.com or a successor location. Any additional or alternate instructions must be agreed to according to the process for amending Customer’s GitHub Customer Agreement. In any instance where the GDPR applies and Customer is a processor, Customer warrants to GitHub that Customer’s instructions, including appointment of GitHub as a processor or subprocessor, have been authorized by the relevant controller. + +To the extent GitHub uses or otherwise processes Personal Data subject to the GDPR for GitHub’s legitimate business operations incident to delivery of the Online Services to Customer, GitHub will comply with the obligations of an independent data controller under GDPR for such use. GitHub is accepting the added responsibilities of a data “controller” under the GDPR for processing in connection with its legitimate business operations to: (a) act consistent with regulatory requirements, to the extent required under the GDPR; and (b) provide increased transparency to Customers and confirm GitHub’s accountability for such processing. GitHub employs safeguards to protect Personal Data in processing, including those identified in this DPA and those contemplated in Article 6(4) of the GDPR. With respect to processing of Personal Data under this paragraph, GitHub makes the commitments set forth in the Standard Contractual Clauses set forth in Attachment 1 or Attachment 2 (as applicable); for those purposes, (i) any GitHub disclosure of Personal Data, as described in Annex III to Attachment 1 or Appendix 3 to Attachment 2 (as applicable), that has been transferred in connection with GitHub’s legitimate business operations is deemed a “Relevant Disclosure” and (ii) the commitments in Annex III to Attachment 1 or Appendix 3 to Attachment 2 (as applicable) apply to such Personal Data. + +#### Processing Details + +The parties acknowledge and agree that: + +- **Subject Matter**. The subject-matter of the processing is limited to Personal Data within the scope of the section of this DPA entitled “Nature of Data Processing; Ownership” above and the GDPR. +- **Duration of the Processing**. The duration of the processing shall be in accordance with Customer instructions and the terms of the DPA. +- **Nature and Purpose of the Processing**. The nature and purpose of the processing shall be to provide the Online Service pursuant to Customer’s GitHub Customer Agreement and for GitHub’s legitimate business operations incident to delivery of the Online Service to Customer (as further described in the section of this DPA entitled “Nature of Data Processing; Ownership” above). +- **Categories of Data**. The types of Personal Data processed by GitHub when providing the Online Service include: (i) Personal Data that Customer elects to include in Customer Data or Professional Services Data (including, without limitation, Support Data); and (ii) those expressly identified in Article 4 of the GDPR that may be contained in Diagnostic Data or Service Generated Data. The types of Personal Data that Customer elects to include in Customer Data or Professional Services Data (including, without limitation, Support Data) may be any categories of Personal Data identified in records maintained by Customer acting as controller pursuant to Article 30 of the GDPR, including the categories of Personal Data set forth in Annex I to Attachment 1 or Appendix 1 to Attachment 2 (as applicable). +- Data Subjects. The categories of data subjects are Customer’s representatives and end users, such as employees, contractors, collaborators, and customers, and may include any other categories of data subjects as identified in records maintained by Customer acting as controller pursuant to Article 30 of the GDPR, including the categories of data subjects set forth in Annex I to Attachment 1 or Appendix 1 to Attachment 2 (as applicable). + +#### Data Subject Rights; Assistance with Requests + +GitHub will make available to Customer, in a manner consistent with the functionality of the Online Service and GitHub’s role as a processor of Personal Data of data subjects, the ability to fulfill data subject requests to exercise their rights under the GDPR. If GitHub receives a request from Customer’s data subject to exercise one or more of its rights under the GDPR in connection with an Online Service for which GitHub is a data processor or subprocessor, GitHub will redirect the data subject to make its request directly to Customer. Customer will be responsible for responding to any such request including, where necessary, by using the functionality of the Online Service. Github deberá cumplir con las soclitudes razonables que haga el Cliente para asistir la respuesta del mismo a dichas solicitudes de un sujeto de datos. + +#### Records of Processing Activities + +To the extent the GDPR requires GitHub to collect and maintain records of certain information relating to Customer, Customer will, where requested, supply such information to GitHub and keep it accurate and up-to-date. GitHub may make any such information available to the supervisory authority if required by the GDPR. + +### Data Security + +GitHub will implement and maintain appropriate technical and organizational measures and security safeguards against accidental or unlawful destruction, or loss, alteration, unauthorized disclosure of or access to, Customer Data and Personal Data processed by GitHub on behalf and in accordance with the documented instructions of Customer in connection with the Online Services. GitHub will regularly monitor compliance with these measures and safeguards and will continue to take appropriate steps throughout the term of the GitHub Customer Agreement. Appendix A – Security Safeguards contains a description of the technical and organizational measures and security safeguards implemented by GitHub. + +Customer is solely responsible for making an independent determination as to whether the technical and organizational measures and security safeguards for an Online Service meet Customer’s requirements, including any of its security obligations under applicable Data Protection Requirements. Customer acknowledges and agrees that (taking into account the state of the art, the costs of implementation, and the nature, scope, context and purposes of the processing of its Customer Data and Personal Data as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons) the technical and organizational measures and security safeguards implemented and maintained by GitHub provide a level of security appropriate to the risk with respect to its Customer Data and Personal Data. Customer is responsible for implementing and maintaining privacy protections and security measures for components that Customer provides or controls. + +GitHub will provide security compliance reporting such as external SOC1, type 2 and SOC2, type2 audit reports upon Customer request. Customer agrees that any information and audit rights granted by the applicable Data Protection Requirements (including, where applicable, Article 28(3)(h) of the GDPR) will be satisfied by these compliance reports, and will otherwise only arise to the extent that GitHub's provision of a compliance report does not provide sufficient information, or to the extent that Customer must respond to a regulatory or supervisory authority audit or investigation. + +Should Customer be subject to a regulatory or supervisory authority audit or investigation or carry out an audit or investigation in response to a request by a regulatory or supervisory authority that requires participation from GitHub, and Customers’ obligations cannot reasonably be satisfied (where allowable by Customer’s regulators) through audit reports, documentation, or compliance information that GitHub makes generally available to its customers, then GitHub will promptly respond to Customer’s additional instructions and requests for information, in accordance with the following terms and conditions: + +- GitHub will provide access to relevant knowledgeable personnel, documentation, and application software. +- Customer and GitHub will mutually agree in a prior written agreement (email is acceptable) upon the scope, timing, duration, control and evidence requirements, provided that this requirement to agree will not permit GitHub to unreasonably delay its cooperation. +- Customer must ensure its regulator’s use of an independent, accredited third-party audit firm, during regular business hours, with reasonable advance written notice to GitHub, and subject to reasonable confidentiality procedures. Neither Customer, its regulators, nor its regulators’ delegates shall have access to any data from GitHub’s other customers or to GitHub systems or facilities not involved in the Online Services. +- Customer is responsible for all costs and fees related to GitHub’s cooperation with the regulatory audit of Customer, including all reasonable costs and fees for any and all time GitHub expends, in addition to the rates for services performed by GitHub. +- If the report generated from GitHub’s cooperation with the regulatory audit of Customer includes any findings pertaining to GitHub, Customer will share such report, findings, and recommended actions with GitHub where allowed by Customer’s regulators. + +### Security Incident Notification + +If GitHub becomes aware of a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Customer Data or Personal Data processed by GitHub on behalf and in accordance with the documented instructions of Customer in connection with the Online Services (each a "Security Incident"), GitHub will promptly and without undue delay (1) notify Customer of the Security Incident; (2) investigate the Security Incident and provide Customer with detailed information about the Security Incident; (3) take reasonable steps to mitigate the effects and to minimize any damage resulting from the Security Incident. + +Notification(s) of Security Incidents will be delivered to one or more of Customer's administrators by any means GitHub selects, including via email. It is Customer's sole responsibility to ensure it maintains accurate contact information with GitHub and that Customer's administrators monitor for and respond to any notifications. El Cliente es el único responsable de cumplir con sus obligaciones según las leyes de notificación de incidentes aplicables al Cliente y de cumplir con las obligaciones de notificación de terceros relacionadas con cualquier Incidente de seguridad. + +GitHub will make reasonable efforts to assist Customer in fulfilling Customer's obligation under GDPR Article 33 or other applicable law or regulations to notify the relevant regulatory or supervisory authority and individual data subjects about a Security Incident. + +GitHub’s notification of or response to a Security Incident under this section is not an acknowledgement by GitHub of any fault or liability with respect to the Security Incident. + +Customer must notify GitHub promptly about any possible misuse of its accounts or authentication credentials or any Security Incident related to an Online Service. + +### Data Transfers and Location + +Personal Data that GitHub processes on behalf and in accordance with the documented instructions of Customer in connection with the Online Services may not be transferred to, or stored and processed in a geographic location except in accordance with the DPA Terms and the safeguards provided below in this section. Taking into account such safeguards, Customer appoints GitHub to transfer Personal Data to the United States or any other country in which GitHub or its Subprocessors operate and to store and process Personal Data to provide the Online Services, except as may be described elsewhere in these DPA Terms. + +All transfers of Personal Data out of the European Union, European Economic Area, or Switzerland to provide the Online Services shall be governed by the Standard Contractual Clauses (EU/EEA) in Attachment 1. All transfers of Personal Data out of the United Kingdom to provide the Online Services shall be governed by the Standard Contractual Clauses (UK) in Attachment 2. For the purposes of the Standard Contractual Clauses (UK) in Attachment 2, references to the “European Union,” “EU,” “European Economic Area,” “EEA” or a “Member State” shall be interpreted to refer to the United Kingdom where reasonably necessary and appropriate to give full force and effect to the Standard Contractual Clauses (UK) with respect to transfers of Personal Data from the United Kingdom. This applies regardless of the fact that, effective January 31, 2020, the United Kingdom is no longer a Member State of the European Union or European Economic Area. + +GitHub will abide by the requirements of applicable European Union, European Economic Area, United Kingdom and Swiss data protection law, and other Data Protection Requirements, in each case regarding the transfer of Personal Data to recipients or jurisdictions outside such jurisdiction. All such transfers of Personal Data will, where applicable, be subject to appropriate safeguards as described in Article 46 of the GDPR and such transfers and safeguards will be documented according to Article 30(2) of the GDPR. + +Subject to the safeguards described above, GitHub may transfer, store and otherwise process Personal Data to or in jurisdictions and geographic locations worldwide as it, subject to its sole discretion, considers reasonably necessary in connection with the Online Services. + +### Data Retention and Deletion + +Upon Customer's reasonable request, unless prohibited by law, GitHub will return or destroy all Customer Data and Personal Data processed by GitHub on behalf and in accordance with the documented instructions of Customer in connection with the Online Services at all locations where it is stored within 30 days of the request, provided that it is no longer needed for providing the Online Services or the purposes for which a data subject had authorized the processing of their Personal Data. GitHub may retain Customer Data or Personal Data to the extent required by the applicable Data Protection Requirements or other applicable law, and only to the extent and for such period as required by the applicable Data Protection Requirements or other applicable law, provided that GitHub will ensure that the Customer Data or Personal Data is processed only as necessary for the purpose specified in the applicable Data Protection Requirements or other applicable law and no other purpose, and the Customer Data or Personal Data remains protected by the Applicable Data Protection Requirements or other applicable law. + +### Processor Confidentiality Commitment + +GitHub will ensure that its personnel engaged in the processing of Customer Data and Personal Data on behalf of Customer in connection with the Online Services (i) will process such data only on instructions from Customer or as described in this DPA, and (ii) will be obligated to maintain the confidentiality and security of such data even after their engagement ends. GitHub shall provide periodic and mandatory data privacy and security training and awareness to its employees with access to Customer Data and Personal Data in accordance with applicable Data Protection Requirements or other applicable law and industry standards. + +### Notice and Controls on Use of Subprocessors + +GitHub may hire Subprocessors to provide certain limited or ancillary services on its behalf. Customer consents to this engagement and to GitHub Affiliates as Subprocessors. The above authorizations will constitute Customer’s prior written consent to the subcontracting by GitHub of the processing of Personal Data if such consent is required under applicable law, the Standard Contractual Clauses or the GDPR Related Terms. + +GitHub is responsible for its Subprocessors’ compliance with GitHub’s obligations in this DPA. GitHub makes available information about Subprocessors on the GitHub website https://github.com/subprocessors (or a successor location). When engaging any Subprocessor, GitHub will ensure via a written contract that the Subprocessor may access and use Customer Data or Personal Data only to deliver the services GitHub has retained them to provide and is prohibited from using Customer Data or Personal Data for any other purpose. GitHub will ensure that Subprocessors are bound by written agreements that require them to provide at least the level of data protection required of GitHub by the DPA, including the limitations on disclosure of Personal Data. GitHub agrees to oversee the Subprocessors to ensure that these contractual obligations are met. + +From time to time, GitHub may engage new Subprocessors. GitHub will give Customer notice (by updating the website at https://github.com/github-subprocessors-list (or a successor location) and providing Customer with a mechanism to obtain notice of that update) of any new Subprocessor in advance of providing that Subprocessor with access to Customer Data. If GitHub engages a new Subprocessor for a new Online Service, GitHub will give Customer notice prior to availability of that Online Service. + +If Customer does not approve of a new Subprocessor, then Customer may terminate any subscription for the affected Online Service without penalty by providing, before the end of the relevant notice period, written notice of termination. Customer may also include an explanation of the grounds for non-approval together with the termination notice, in order to permit GitHub to re-evaluate any such new Subprocessor based on the applicable concerns. If the affected Online Service is part of a suite (or similar single purchase of services), then any termination will apply to the entire suite. After termination, GitHub will remove payment obligations for any subscriptions for the terminated Online Service from subsequent invoices to Customer or its reseller. + +### Educational Institutions +If Customer is an educational agency or institution subject to the regulations under the Family Educational Rights and Privacy Act, 20 U.S.C. § 1232g (FERPA), or similar state student or educational privacy laws (collectively “Educational Privacy Laws”), Customer shall not provide Personal Data covered by such Educational Privacy Laws to GitHub without obtaining GitHub’s prior, written and specific consent and entering into a separate agreement with GitHub governing the parties’ rights and obligations with respect to the processing of such Personal Data by GitHub in connection with the Online Services. + +Subject to the above, if Customer intends to provide to GitHub Personal Data covered by FERPA, the parties agree and acknowledge that, for the purposes of this DPA, GitHub is a “school official” with “legitimate educational interests” in the Personal Data, as those terms have been defined under FERPA and its implementing regulations. Customer understands that GitHub may possess limited or no contact information for Customer’s students and students’ parents. Consequently, Customer will be responsible for obtaining any student or parental consent for any end user’s use of the Online Services that may be required by applicable law and to convey notification on behalf of GitHub to students (or, with respect to a student under 18 years of age and not in attendance at a postsecondary institution, to the student’s parent) of any judicial order or lawfully-issued subpoena requiring the disclosure of Personal Data in GitHub’s possession as may be required under applicable law. + +### CJIS Customer Agreement, HIPAA Business Associate, Biometric Data + +Except with GitHub’s prior, written and specific consent, Customer shall not provide to GitHub any Personal Data + +- relating to criminal convictions and offenses or Personal Data collected or otherwise processed by Customer subject to or in connection with FBI Criminal Justice Information Services or the related Security Policy. +- constituting protected health information governed by the privacy, security, and breach notification rules issued by the United States Department of Health and Human Services, Parts 160 and 164 of Title 45 of the Code of Federal Regulations, established pursuant to the Health Insurance Portability and Accountability Act of 1996 (Public Law 104-191) or by state health or medical privacy laws. +- collected as part of a clinical trial or other biomedical research study subject to, or conducted in accordance with, the Federal Policy for the Protection of Human Subjects (Common Rule). +- covered by state, federal or foreign biometric privacy laws or otherwise constituting biometric information including information on an individual’s physical, physiological, biological or behavioral characteristics or information derived from such information that is used or intended to be used, singly or in combination with each other or with other information, to establish individual identity. + +### California Consumer Privacy Act (CCPA) / California Privacy Rights Act (CPRA) + +If and to the extent GitHub is processing Personal Data on behalf and in accordance with the documented instructions of Customer within the scope of the CCPA, GitHub makes the following additional commitments to Customer. GitHub will process the Personal Data on behalf of Customer and will not + +- sell the Personal Data as the term “selling” is defined in the CCPA. - share, rent, release, disclose, disseminate, make available, transfer or otherwise communicate orally, in writing or by electronic or other means, the Personal Data to a third party for cross-context behavioral advertising, whether or not for monetary or other valuable consideration, including transactions for cross-context behavioral advertising in which no money is exchanged. +- retain, use or disclose the Personal Data for any purpose other than for the business purposes specified in the DPA Terms and the GitHub Customer Agreement, including retaining, using or disclosing the Personal Data for a commercial purpose other than the business purposes specified in the DPA Terms or the GitHub Customer Agreement, or as otherwise permitted by the CCPA. +- retain, use or disclose the Personal Data outside of the direct business relationship with Customer. +- combine the Personal Data with personal information that it receives from or on behalf of a third party or collects from California residents, except that GitHub may combine Personal Data to perform any business purpose as permitted by the CCPA or any regulations adopted or issued under the CCPA. + +### How to Contact GitHub + +If Customer believes that GitHub is not adhering to its privacy or security commitments, Customer may contact customer support or use GitHub’s Privacy web form, located at https://support.github.com/contact/privacy. GitHub’s mailing address is: + +**GitHub Privacy**
    GitHub, Inc.
    88 Colin P. Kelly Jr. Street
    San Francisco, California 94107 USA
    + +GitHub B.V. is GitHub’s data protection representative for the European Economic Area. The privacy representative of GitHub B.V. can be reached at the following address: + +**GitHub B.V.**
    Vijzelstraat 68-72
    1017 HL Amsterdam
    The Netherlands
    + +

    Appendix A – Security Safeguards

    + +GitHub has implemented and will maintain for Customer Data and Personal Data processed by GitHub on behalf and in accordance with the documented instructions of Customer in connection with GitHub services the following technical and organizational measures and security safeguards, which in conjunction with the security commitments in this DPA (including the GDPR Related Terms), are GitHub’s only responsibility with respect to the security of that data: + +| Domain | Practices | +| ---------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Organization of Information Security | **Security Ownership**. GitHub has appointed one or more security officers responsible for coordinating and monitoring the security policies and procedures.

    **Security Roles and Responsibilities**. GitHub personnel with access to Customer Data and Personal Data are subject to confidentiality obligations.

    **Risk Management Program**. GitHub performs an annual risk assessment.
    GitHub retains its security documents pursuant to its retention requirements after they are no longer in effect.

    **Vendor Management**. GitHub has a vendor risk assessment process, vendor contract clauses and additional data protection agreements with vendors. | +| Asset Management | **Asset Inventory**. GitHub maintains an inventory of all media on which Customer Data and Personal Data is stored. Access to the inventories of such media is restricted to GitHub personnel authorized to have such access.

    **Asset Handling**
    - GitHub classifies Customer Data and Personal Data to help identify it and to allow for access to it to be appropriately restricted.
    - GitHub communicates employee responsibility and accountability for data protection up to and including cause for termination.
    GitHub personnel must obtain GitHub authorization prior to remotely accessing Customer Data and Personal Data or processing Customer Data and Personal Data outside GitHub’s facilities. | +| Human Resources Security | **Security Training**. GitHub requires all new hires to complete security and privacy awareness training as part of initial on-boarding. Participation in annual training is required for all employees to provide a baseline for security and privacy basics. | +| Physical and Environmental Security | **Physical Access to Facilities**. GitHub limits access to facilities where information systems that process Customer Data and Personal Data are located to identified authorized individuals.

    **Physical Access to Components**. GitHub maintains records of the incoming and outgoing media containing Customer Data, including the kind of media, the authorized sender/recipients, date and time, the number of media and the types of Customer Data and Personal Data they contain.

    **Protection from Disruptions**. GitHub uses a variety of industry standard systems to protect against loss of data due to power supply failure or line interference.

    **Component Disposal**. GitHub uses industry standard processes to delete Customer Data and Personal Data when it is no longer needed. | +| Communications and Operations Management | **Operational Policy**. GitHub maintains security documents describing its security measures and the relevant procedures and responsibilities of its personnel who have access to Customer Data.

    **Data Recovery Procedures**
    - On an ongoing basis, but in no case less frequently than once a week (unless no Customer Data and Personal Data has been updated during that period), GitHub maintains multiple copies of Customer Data and Personal Data from which Customer Data and Personal Data can be recovered.
    - GitHub stores copies of Customer Data and Personal Data and data recovery procedures in a different place from where the primary computer equipment processing the Customer Data and Personal Data is located.
    - GitHub has specific procedures in place governing access to copies of Customer Data.
    - GitHub logs data restoration efforts, including the person responsible, the description of the restored data and where applicable, the person responsible and which data (if any) had to be input manually in the data recovery process.

    **Malicious Software**. GitHub has threat detection controls to help identify and respond to anomalous or suspicious access to Customer Data, including malicious software originating from public networks.

    **Data Beyond Boundaries**
    - GitHub encrypts, or enables Customer to encrypt, Customer Data and Personal Data that is transmitted over public networks.
    - GitHub restricts access to Customer Data and Personal Data in media leaving its facilities.

    **Event Logging**. GitHub logs, or enables Customer to log, access and use of information systems containing Customer Data, registering the access ID, time, authorization granted or denied, and relevant activity. | +| Access Control | **Access Policy**. GitHub maintains a record of security privileges of individuals having access to Customer Data.

    **Access Authorization**
    - GitHub maintains and updates a record of personnel authorized to access GitHub systems that contain Customer Data.
    - GitHub identifies those personnel who may grant, alter or cancel authorized access to data and resources.
    - GitHub ensures that where more than one individual has access to systems containing Customer Data, the individuals have separate identifiers/log-ins where technically and architecturally feasible, and commercially reasonable.

    **Least Privilege**
    - Technical support personnel are only permitted to have access to Customer Data and Personal Data when needed.
    - GitHub restricts access to Customer Data and Personal Data to only those individuals who require such access to perform their job function. GitHub employees are only granted access to production systems based on their role within the organization.

    **Integrity and Confidentiality**

    - GitHub instructs GitHub personnel to disable administrative sessions when computers are left unattended.
    - GitHub stores passwords such that they are encrypted or unintelligible while they are in force.

    **Authentication**
    - GitHub uses industry standard practices to identify and authenticate users who attempt to access information systems.
    - Where authentication mechanisms are based solely on passwords, GitHub requires the password to be at least eight characters long.
    - GitHub ensures that de-activated or expired employee identifiers are not granted to other individuals.
    - GitHub monitors, or enables Customer to monitor, repeated attempts to gain access to the information system using an invalid password.
    - GitHub maintains industry standard procedures to deactivate passwords that have been corrupted or inadvertently disclosed.
    - GitHub uses industry standard password protection practices, including practices designed to maintain the confidentiality and integrity of passwords when they are assigned and distributed, and during storage.

    **Network Design**. GitHub has controls to ensure no systems storing Customer Data and Personal Data are part of the same logical network used for GitHub business operations. | +| Information Security Incident Management | **Incident Response Process**
    - GitHub maintains a record of security incidents with a description of the incidents, the time period, the consequences of the breach, the name of the reporter, and to whom the incident was reported, and details regarding the handling of the incident.
    - In the event that GitHub Security confirms or reasonably suspects that a GitHub.com customer is affected by a data breach, we will notify the customer without undue delay
    - GitHub tracks, or enables Customer to track, disclosures of Customer Data, including what data has been disclosed, to whom, and at what time.

    **Service Monitoring**. GitHub employs a wide range of continuous monitoring solutions for preventing, detecting, and mitigating attacks to the site. | +| Business Continuity Management | - GitHub maintains emergency and contingency plans for the facilities in which GitHub information systems that process Customer Data and Personal Data are located.
    - GitHub’s redundant storage and its procedures for recovering data are designed to attempt to reconstruct Customer Data and Personal Data in its original or last-replicated state from before the time it was lost or destroyed. | + +

    Attachment 1 - The Standard Contractual Clauses (EU/EEA)

    + +### Controller to Processor + +#### SECTION I + +##### Clause 1 + +**Purpose and scope** + +
      +
    1. The purpose of these standard contractual clauses is to ensure compliance with the requirements of Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data (General Data Protection Regulation) for the transfer of personal data to a third country.
      2. +
    2. The Parties: +
        +
      1. the natural or legal person(s), public authority/ies, agency/ies or other body/ies (hereinafter ‘entity/ies’) transferring the personal data, as listed in Annex I.A (hereinafter each ‘data exporter’), and
        2. +
      2. the entity/ies in a third country receiving the personal data from the data exporter, directly or indirectly via another entity also Party to these Clauses, as listed in Annex I.A (hereinafter each ‘data importer’)
        3. +
      + have agreed to these standard contractual clauses (hereinafter: ‘Clauses’).
      3. +
    3. These Clauses apply with respect to the transfer of personal data as specified in Annex I.B.
      4. +
    4. The Appendix to these Clauses containing the Annexes referred to therein forms an integral part of these Clauses.
      5. +
    + +##### Clause 2 + +**Effect and invariability of the Clauses** +
      +
    1. These Clauses set out appropriate safeguards, including enforceable data subject rights and effective legal remedies, pursuant to Article 46(1) and Article 46(2)(c) of Regulation (EU) 2016/679 and, with respect to data transfers from controllers to processors and/or processors to processors, standard contractual clauses pursuant to Article 28(7) of Regulation (EU) 2016/679, provided they are not modified, except to select the appropriate Module(s) or to add or update information in the Appendix. This does not prevent the Parties from including the standard contractual clauses laid down in these Clauses in a wider contract and/or to add other clauses or additional safeguards, provided that they do not contradict, directly or indirectly, these Clauses or prejudice the fundamental rights or freedoms of data subjects.
      2. +
    2. These Clauses are without prejudice to obligations to which the data exporter is subject by virtue of Regulation (EU) 2016/679.
      3. +
    + +##### Clause 3 + +**Third-party beneficiaries** + +
      +
    1. Data subjects may invoke and enforce these Clauses, as third-party beneficiaries, against the data exporter and/or data importer, with the following exceptions:
      2. +
        +
      1. Clause 1, Clause 2, Clause 3, Clause 6, Clause 7;
        2. +
      2. Clause 8.1(b), 8.9(a), (c), (d) and (e);
        3. +
      3. Clause 9(a), (c), (d) and (e);
        4. +
      4. Clause 12(a), (d) and (f);
        5. +
      5. Clause 13;
        6. +
      6. Clause 15.1(c), (d) and (e);
        7. +
      7. Clause 16(e);
        8. +
      8. Clause 18(a) and (b).
        9. +
      +
    2. Paragraph (a) is without prejudice to rights of data subjects under Regulation (EU) 2016/679.
      3. +
    + +##### Clause 4 + +**Interpretation** + +
      +
    1. Where these Clauses use terms that are defined in Regulation (EU) 2016/679, those terms shall have the same meaning as in that Regulation.
      2. +
    2. These Clauses shall be read and interpreted in the light of the provisions of Regulation (EU) 2016/679.
      3. +
    3. These Clauses shall not be interpreted in a way that conflicts with rights and obligations provided for in Regulation (EU) 2016/679.
      4. +
    + +##### Clause 5 + +**Hierarchy** + +In the event of a contradiction between these Clauses and the provisions of related agreements between the Parties, existing at the time these Clauses are agreed or entered into thereafter, these Clauses shall prevail. + +##### Clause 6 + +**Description of the transfer(s)** + +The details of the transfer(s), and in particular the categories of personal data that are transferred and the purpose(s) for which they are transferred, are specified in Annex I.B. + +##### Clause 7 + +**Docking clause** + +
      +
    1. An entity that is not a Party to these Clauses may, with the agreement of the Parties, accede to these Clauses at any time, either as a data exporter or as a data importer, by completing the Appendix and signing Annex I.A.
      2. +
    2. Once it has completed the Appendix and signed Annex I.A, the acceding entity shall become a Party to these Clauses and have the rights and obligations of a data exporter or data importer in accordance with its designation in Annex I.A.
      3. +
    3. The acceding entity shall have no rights or obligations arising under these Clauses from the period prior to becoming a Party.
      4. +
    + +#### SECTION II – OBLIGATIONS OF THE PARTIES + +##### Clause 8 + +**Data protection safeguards** + +The data exporter warrants that it has used reasonable efforts to determine that the data importer is able, through the implementation of appropriate technical and organisational measures, to satisfy its obligations under these Clauses. + +**8.1 Instructions**
      +
    1. The data importer shall process the personal data only on documented instructions from the data exporter. The data exporter may give such instructions throughout the duration of the contract.
      2. +
    2. The data importer shall immediately inform the data exporter if it is unable to follow those instructions.
      3. +
    + +**8.2 Purpose limitation** + +The data importer shall process the personal data only for the specific purpose(s) of the transfer, as set out in Annex I.B, unless on further instructions from the data exporter. + +**8.3 Transparency** + +On request, the data exporter shall make a copy of these Clauses, including the Appendix as completed by the Parties, available to the data subject free of charge. To the extent necessary to protect business secrets or other confidential information, including the measures described in Annex II and personal data, the data exporter may redact part of the text of the Appendix to these Clauses prior to sharing a copy, but shall provide a meaningful summary where the data subject would otherwise not be able to understand the its content or exercise his/her rights. On request, the Parties shall provide the data subject with the reasons for the redactions, to the extent possible without revealing the redacted information. This Clause is without prejudice to the obligations of the data exporter under Articles 13 and 14 of Regulation (EU) 2016/679. + +**8.4 Accuracy** + +If the data importer becomes aware that the personal data it has received is inaccurate, or has become outdated, it shall inform the data exporter without undue delay. In this case, the data importer shall cooperate with the data exporter to erase or rectify the data. + +**8.5 Duration of processing and erasure or return of data** + +Processing by the data importer shall only take place for the duration specified in Annex I.B. After the end of the provision of the processing services, the data importer shall, at the choice of the data exporter, delete all personal data processed on behalf of the data exporter and certify to the data exporter that it has done so, or return to the data exporter all personal data processed on its behalf and delete existing copies. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit return or deletion of the personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process it to the extent and for as long as required under that local law. This is without prejudice to Clause 14, in particular the requirement for the data importer under Clause 14(e) to notify the data exporter throughout the duration of the contract if it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under Clause 14(a). + +**8.6 Security of processing** + +
      +
    1. The data importer and, during transmission, also the data exporter shall implement appropriate technical and organisational measures to ensure the security of the data, including protection against a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access to that data (hereinafter ‘personal data breach’). In assessing the appropriate level of security, the Parties shall take due account of the state of the art, the costs of implementation, the nature, scope, context and purpose(s) of processing and the risks involved in the processing for the data subjects. The Parties shall in particular consider having recourse to encryption or pseudonymisation, including during transmission, where the purpose of processing can be fulfilled in that manner. In case of pseudonymisation, the additional information for attributing the personal data to a specific data subject shall, where possible, remain under the exclusive control of the data exporter. In complying with its obligations under this paragraph, the data importer shall at least implement the technical and organisational measures specified in Annex II. The data importer shall carry out regular checks to ensure that these measures continue to provide an appropriate level of security.
      2. +
    2. The data importer shall grant access to the personal data to members of its personnel only to the extent strictly necessary for the implementation, management and monitoring of the contract. It shall ensure that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.
      3. +
    3. In the event of a personal data breach concerning personal data processed by the data importer under these Clauses, the data importer shall take appropriate measures to address the breach, including measures to mitigate its adverse effects. The data importer shall also notify the data exporter without undue delay after having become aware of the breach. Such notification shall contain the details of a contact point where more information can be obtained, a description of the nature of the breach (including, where possible, categories and approximate number of data subjects and personal data records concerned), its likely consequences and the measures taken or proposed to address the breach including, where appropriate, measures to mitigate its possible adverse effects. Where, and in so far as, it is not possible to provide all information at the same time, the initial notification shall contain the information then available and further information shall, as it becomes available, subsequently be provided without undue delay.
      4. +
    4. The data importer shall cooperate with and assist the data exporter to enable the data exporter to comply with its obligations under Regulation (EU) 2016/679, in particular to notify the competent supervisory authority and the affected data subjects, taking into account the nature of processing and the information available to the data importer.
      5. +
    + +**8.7 Sensitive data** + +Where the transfer involves personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic data, or biometric data for the purpose of uniquely identifying a natural person, data concerning health or a person’s sex life or sexual orientation, or data relating to criminal convictions and offences (hereinafter ‘sensitive data’), the data importer shall apply the specific restrictions and/or additional safeguards described in Annex I.B. + +**8.8 Onward transfers** + +The data importer shall only disclose the personal data to a third party on documented instructions from the data exporter. In addition, the data may only be disclosed to a third party located outside the European Union (1) (in the same country as the data importer or in another third country, hereinafter ‘onward transfer’) if the third party is or agrees to be bound by these Clauses, under the appropriate Module, or if: + +
      +
    1. the onward transfer is to a country benefitting from an adequacy decision pursuant to Article 45 of Regulation (EU) 2016/679 that covers the onward transfer;
      2. +
    2. the third party otherwise ensures appropriate safeguards pursuant to Articles 46 or 47 Regulation of (EU) 2016/679 with respect to the processing in question;
      3. +
    3. the onward transfer is necessary for the establishment, exercise or defence of legal claims in the context of specific administrative, regulatory or judicial proceedings; or
      4. +
    4. the onward transfer is necessary in order to protect the vital interests of the data subject or of another natural person.

      5. + Any onward transfer is subject to compliance by the data importer with all the other safeguards under these Clauses, in particular purpose limitation. +
    + +**8.9 Documentation and compliance** + +
      +
    1. The data importer shall promptly and adequately deal with enquiries from the data exporter that relate to the processing under these Clauses.
      2. +
    2. The Parties shall be able to demonstrate compliance with these Clauses. In particular, the data importer shall keep appropriate documentation on the processing activities carried out on behalf of the data exporter.
      3. +
    3. The data importer shall make available to the data exporter all information necessary to demonstrate compliance with the obligations set out in these Clauses and at the data exporter’s request, allow for and contribute to audits of the processing activities covered by these Clauses, at reasonable intervals or if there are indications of non-compliance. In deciding on a review or audit, the data exporter may take into account relevant certifications held by the data importer.
      4. +
    4. The data exporter may choose to conduct the audit by itself or mandate an independent auditor. Audits may include inspections at the premises or physical facilities of the data importer and shall, where appropriate, be carried out with reasonable notice.
      5. +
    5. The Parties shall make the information referred to in paragraphs (b) and (c), including the results of any audits, available to the competent supervisory authority on request.
      6. +
    + +##### Clause 9 + +**Use of sub-processors** + +
      +
    1. GENERAL WRITTEN AUTHORISATION The data importer has the data exporter’s general authorisation for the engagement of sub-processor(s) from an agreed list. The data importer shall specifically inform the data exporter in writing of any intended changes to that list through the addition or replacement of sub-processors at least 90 days in advance, thereby giving the data exporter sufficient time to be able to object to such changes prior to the engagement of the sub-processor(s). The data importer shall provide the data exporter with the information necessary to enable the data exporter to exercise its right to object.
      2. +
    2. Where the data importer engages a sub-processor to carry out specific processing activities (on behalf of the data exporter), it shall do so by way of a written contract that provides for, in substance, the same data protection obligations as those binding the data importer under these Clauses, including in terms of third-party beneficiary rights for data subjects.(2) The Parties agree that, by complying with this Clause, the data importer fulfils its obligations under Clause 8.8. The data importer shall ensure that the sub-processor complies with the obligations to which the data importer is subject pursuant to these Clauses.
      3. +
    3. The data importer shall provide, at the data exporter’s request, a copy of such a sub-processor agreement and any subsequent amendments to the data exporter. To the extent necessary to protect business secrets or other confidential information, including personal data, the data importer may redact the text of the agreement prior to sharing a copy.
      4. +
    4. The data importer shall remain fully responsible to the data exporter for the performance of the sub-processor’s obligations under its contract with the data importer. The data importer shall notify the data exporter of any failure by the sub-processor to fulfil its obligations under that contract.
      5. +
    5. The data importer shall agree a third-party beneficiary clause with the sub-processor whereby – in the event the data importer has factually disappeared, ceased to exist in law or has become insolvent – the data exporter shall have the right to terminate the sub-processor contract and to instruct the sub-processor to erase or return the personal data.
      6. +
    + +##### Clause 10 + +**Data subject rights** + +
      +
    1. The data importer shall promptly notify the data exporter of any request it has received from a data subject. It shall not respond to that request itself unless it has been authorised to do so by the data exporter.
      2. +
    2. The data importer shall assist the data exporter in fulfilling its obligations to respond to data subjects’ requests for the exercise of their rights under Regulation (EU) 2016/679. In this regard, the Parties shall set out in Annex II the appropriate technical and organisational measures, taking into account the nature of the processing, by which the assistance shall be provided, as well as the scope and the extent of the assistance required.
      3. +
    3. In fulfilling its obligations under paragraphs (a) and (b), the data importer shall comply with the instructions from the data exporter.
      4. +
    + +##### Clause 11 + +**Redress** + +
      +
    1. The data importer shall inform data subjects in a transparent and easily accessible format, through individual notice or on its website, of a contact point authorised to handle complaints. It shall deal promptly with any complaints it receives from a data subject.
      2. +
    2. In case of a dispute between a data subject and one of the Parties as regards compliance with these Clauses, that Party shall use its best efforts to resolve the issue amicably in a timely fashion. The Parties shall keep each other informed about such disputes and, where appropriate, cooperate in resolving them.
      3. +
    3. Where the data subject invokes a third-party beneficiary right pursuant to Clause 3, the data importer shall accept the decision of the data subject to:
      4. +
        +
      1. lodge a complaint with the supervisory authority in the Member State of his/her habitual residence or place of work, or the competent supervisory authority pursuant to Clause 13;
        2. +
      2. refer the dispute to the competent courts within the meaning of Clause 18.
        3. +
      +
    4. The Parties accept that the data subject may be represented by a not-for-profit body, organisation or association under the conditions set out in Article 80(1) of Regulation (EU) 2016/679.
      5. +
    5. The data importer shall abide by a decision that is binding under the applicable EU or Member State law.
      6. +
    6. The data importer agrees that the choice made by the data subject will not prejudice his/her substantive and procedural rights to seek remedies in accordance with applicable laws.
      7. +
    + +##### Clause 12 + +**Liability** + +
      +
    1. Each Party shall be liable to the other Party/ies for any damages it causes the other Party/ies by any breach of these Clauses.
      2. +
    2. The data importer shall be liable to the data subject, and the data subject shall be entitled to receive compensation, for any material or non-material damages the data importer or its sub-processor causes the data subject by breaching the third-party beneficiary rights under these Clauses.
      3. +
    3. Notwithstanding paragraph (b), the data exporter shall be liable to the data subject, and the data subject shall be entitled to receive compensation, for any material or non-material damages the data exporter or the data importer (or its sub-processor) causes the data subject by breaching the third-party beneficiary rights under these Clauses. This is without prejudice to the liability of the data exporter and, where the data exporter is a processor acting on behalf of a controller, to the liability of the controller under Regulation (EU) 2016/679 or Regulation (EU) 2018/1725, as applicable.
      4. +
    4. The Parties agree that if the data exporter is held liable under paragraph (c) for damages caused by the data importer (or its sub-processor), it shall be entitled to claim back from the data importer that part of the compensation corresponding to the data importer’s responsibility for the damage.
      5. +
    5. Where more than one Party is responsible for any damage caused to the data subject as a result of a breach of these Clauses, all responsible Parties shall be jointly and severally liable and the data subject is entitled to bring an action in court against any of these Parties.
      6. +
    6. The Parties agree that if one Party is held liable under paragraph (e), it shall be entitled to claim back from the other Party/ies that part of the compensation corresponding to its/their responsibility for the damage.
      7. +
    7. The data importer may not invoke the conduct of a sub-processor to avoid its own liability.
      8. +
    + +##### Clause 13 + +**Supervision** + +
      +
    1. [Where the data exporter is established in an EU Member State:] The supervisory authority with responsibility for ensuring compliance by the data exporter with Regulation (EU) 2016/679 as regards the data transfer, as indicated in Annex I.C, shall act as competent supervisory authority.

      + [Where the data exporter is not established in an EU Member State, but falls within the territorial scope of application of Regulation (EU) 2016/679 in accordance with its Article 3(2) and has appointed a representative pursuant to Article 27(1) of Regulation (EU) 2016/679:] The supervisory authority of the Member State in which the representative within the meaning of Article 27(1) of Regulation (EU) 2016/679 is established, as indicated in Annex I.C, shall act as competent supervisory authority.

      + [Where the data exporter is not established in an EU Member State, but falls within the territorial scope of application of Regulation (EU) 2016/679 in accordance with its Article 3(2) without however having to appoint a representative pursuant to Article 27(2) of Regulation (EU) 2016/679:] The supervisory authority of one of the Member States in which the data subjects whose personal data is transferred under these Clauses in relation to the offering of goods or services to them, or whose behaviour is monitored, are located, as indicated in Annex I.C, shall act as competent supervisory authority.

      2. +
    2. The data importer agrees to submit itself to the jurisdiction of and cooperate with the competent supervisory authority in any procedures aimed at ensuring compliance with these Clauses. In particular, the data importer agrees to respond to enquiries, submit to audits and comply with the measures adopted by the supervisory authority, including remedial and compensatory measures. It shall provide the supervisory authority with written confirmation that the necessary actions have been taken.
      3. +
    + +#### SECTION III – LOCAL LAWS AND OBLIGATIONS IN CASE OF ACCESS BY PUBLIC AUTHORITIES + +##### Clause 14 + +**Local laws and practices affecting compliance with the Clauses** + +
      +
    1. The Parties warrant that they have no reason to believe that the laws and practices in the third country of destination applicable to the processing of the personal data by the data importer, including any requirements to disclose personal data or measures authorising access by public authorities, prevent the data importer from fulfilling its obligations under these Clauses. This is based on the understanding that laws and practices that respect the essence of the fundamental rights and freedoms and do not exceed what is necessary and proportionate in a democratic society to safeguard one of the objectives listed in Article 23(1) of Regulation (EU) 2016/679, are not in contradiction with these Clauses.
      2. +
    2. The Parties declare that in providing the warranty in paragraph (a), they have taken due account in particular of the following elements:
      3. +
        +
      1. the specific circumstances of the transfer, including the length of the processing chain, the number of actors involved and the transmission channels used; intended onward transfers; the type of recipient; the purpose of processing; the categories and format of the transferred personal data; the economic sector in which the transfer occurs; the storage location of the data transferred;
        2. +
      2. the laws and practices of the third country of destination– including those requiring the disclosure of data to public authorities or authorising access by such authorities – relevant in light of the specific circumstances of the transfer, and the applicable limitations and safeguards (3);
        3. +
      3. any relevant contractual, technical or organisational safeguards put in place to supplement the safeguards under these Clauses, including measures applied during transmission and to the processing of the personal data in the country of destination.
        4. +
      +
    3. The data importer warrants that, in carrying out the assessment under paragraph (b), it has made its best efforts to provide the data exporter with relevant information and agrees that it will continue to cooperate with the data exporter in ensuring compliance with these Clauses.
      4. +
    4. The Parties agree to document the assessment under paragraph (b) and make it available to the competent supervisory authority on request.
      5. +
    5. The data importer agrees to notify the data exporter promptly if, after having agreed to these Clauses and for the duration of the contract, it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under paragraph (a), including following a change in the laws of the third country or a measure (such as a disclosure request) indicating an application of such laws in practice that is not in line with the requirements in paragraph (a).
      6. +
    6. Following a notification pursuant to paragraph (e), or if the data exporter otherwise has reason to believe that the data importer can no longer fulfil its obligations under these Clauses, the data exporter shall promptly identify appropriate measures (e.g. technical or organisational measures to ensure security and confidentiality) to be adopted by the data exporter and/or data importer to address the situation. The data exporter shall suspend the data transfer if it considers that no appropriate safeguards for such transfer can be ensured, or if instructed by the competent supervisory authority to do so. In this case, the data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses. If the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise. Where the contract is terminated pursuant to this Clause, Clause 16(d) and (e) shall apply.
      7. +
    + +##### Clause 15 + +**Obligations of the data importer in case of access by public authorities** + +**15.1 Notification** + +
      +
    1. The data importer agrees to notify the data exporter and, where possible, the data subject promptly (if necessary with the help of the data exporter) if it:
      2. +
        +
      1. receives a legally binding request from a public authority, including judicial authorities, under the laws of the country of destination for the disclosure of personal data transferred pursuant to these Clauses; such notification shall include information about the personal data requested, the requesting authority, the legal basis for the request and the response provided; or
        2. +
      2. becomes aware of any direct access by public authorities to personal data transferred pursuant to these Clauses in accordance with the laws of the country of destination; such notification shall include all information available to the importer.
        3. +
      +
    2. If the data importer is prohibited from notifying the data exporter and/or the data subject under the laws of the country of destination, the data importer agrees to use its best efforts to obtain a waiver of the prohibition, with a view to communicating as much information as possible, as soon as possible. The data importer agrees to document its best efforts in order to be able to demonstrate them on request of the data exporter.
      3. +
    3. Where permissible under the laws of the country of destination, the data importer agrees to provide the data exporter, at regular intervals for the duration of the contract, with as much relevant information as possible on the requests received (in particular, number of requests, type of data requested, requesting authority/ies, whether requests have been challenged and the outcome of such challenges, etc.).
      4. +
    4. The data importer agrees to preserve the information pursuant to paragraphs (a) to (c) for the duration of the contract and make it available to the competent supervisory authority on request.
      5. +
    5. Paragraphs (a) to (c) are without prejudice to the obligation of the data importer pursuant to Clause 14(e) and Clause 16 to inform the data exporter promptly where it is unable to comply with these Clauses.
      6. +
    + +**15.2 Review of legality and data minimisation** + +
      +
    1. The data importer agrees to review the legality of the request for disclosure, in particular whether it remains within the powers granted to the requesting public authority, and to challenge the request if, after careful assessment, it concludes that there are reasonable grounds to consider that the request is unlawful under the laws of the country of destination, applicable obligations under international law and principles of international comity. The data importer shall, under the same conditions, pursue possibilities of appeal. When challenging a request, the data importer shall seek interim measures with a view to suspending the effects of the request until the competent judicial authority has decided on its merits. It shall not disclose the personal data requested until required to do so under the applicable procedural rules. These requirements are without prejudice to the obligations of the data importer under Clause 14(e).
      2. +
    2. The data importer agrees to document its legal assessment and any challenge to the request for disclosure and, to the extent permissible under the laws of the country of destination, make the documentation available to the data exporter. It shall also make it available to the competent supervisory authority on request.
      3. +
    3. The data importer agrees to provide the minimum amount of information permissible when responding to a request for disclosure, based on a reasonable interpretation of the request.
      4. +
    + +#### SECTION IV – FINAL PROVISIONS + +##### Clause 16 + +**Non-compliance with the Clauses and termination** + +
      +
    1. The data importer shall promptly inform the data exporter if it is unable to comply with these Clauses, for whatever reason.
      2. +
    2. In the event that the data importer is in breach of these Clauses or unable to comply with these Clauses, the data exporter shall suspend the transfer of personal data to the data importer until compliance is again ensured or the contract is terminated. This is without prejudice to Clause 14(f).
      3. +
    3. The data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses, where:
      4. +
        +
      1. the data exporter has suspended the transfer of personal data to the data importer pursuant to paragraph (b) and compliance with these Clauses is not restored within a reasonable time and in any event within one month of suspension;
        2. +
      2. the data importer is in substantial or persistent breach of these Clauses; or
        3. +
      3. the data importer fails to comply with a binding decision of a competent court or supervisory authority regarding its obligations under these Clauses.
        4. +

      + In these cases, it shall inform the competent supervisory authority of such non-compliance. Where the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise. +
    4. Personal data that has been transferred prior to the termination of the contract pursuant to paragraph (c) shall at the choice of the data exporter immediately be returned to the data exporter or deleted in its entirety. The same shall apply to any copies of the data. The data importer shall certify the deletion of the data to the data exporter. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit the return or deletion of the transferred personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process the data to the extent and for as long as required under that local law.
      5. +
    5. Either Party may revoke its agreement to be bound by these Clauses where (i) the European Commission adopts a decision pursuant to Article 45(3) of Regulation (EU) 2016/679 that covers the transfer of personal data to which these Clauses apply; or (ii) Regulation (EU) 2016/679 becomes part of the legal framework of the country to which the personal data is transferred. This is without prejudice to other obligations applying to the processing in question under Regulation (EU) 2016/679.
      6. +
    + +##### Clause 17 + +**Governing law** + +These Clauses shall be governed by the law of one of the EU Member States, provided such law allows for third-party beneficiary rights. The Parties agree that this shall be the law of the Netherlands. + +##### Clause 18 + +**Choice of forum and jurisdiction** + +
      +
    1. Any dispute arising from these Clauses shall be resolved by the courts of an EU Member State.
      2. +
    2. The Parties agree that those shall be the courts of the Netherlands.
      3. +
    3. A data subject may also bring legal proceedings against the data exporter and/or data importer before the courts of the Member State in which he/she has his/her habitual residence.
      4. +
    4. The Parties agree to submit themselves to the jurisdiction of such courts.
      5. +
    + +## ANNEX I + +**to the Standard Contractual Clauses (EU/EEA)** + +### A. LIST OF PARTIES + +**Data exporter(s)**: Customer is the data exporter
    Name: see GitHub Customer Agreement
    Address: see GitHub Customer Agreement
    Contact person’s name, position and contact details: see GitHub Customer Agreement
    Activities relevant to the data transferred under these Clauses:
    The data exporter is a user of Online Services or Professional Services as defined in the DPA and GitHub Customer Agreement.
    Signature and date: see GitHub Customer Agreement (the DPA and the Standard Contractual Clauses (EU/EEA) are incorporated into the GitHub Customer Agreement
    Role (controller/processor): controller (unless otherwise agreed in the Customer Agreement).
    + +**Data importer(s)**:
    Name: GitHub, Inc.
    Address: 88 Colin P Kelly Jr St, San Francisco, CA 94107, USA
    Contact person’s name, position and contact details: Frances Wiet, Head of Privacy, fwiet@github.com
    Activities relevant to the data transferred under these Clauses:
    GitHub, Inc. is a global producer of software and services
    Signature and date: see GitHub Customer Agreement (the DPA and the Standard Contractual Clauses (EU/EEA) are incorporated into the GitHub Customer Agreement)
    Role (controller/processor): processor or, depending on the agreements set forth in the Customer Agreement, subprocessor. + +### B. DESCRIPTION OF TRANSFER + +_Categories of data subjects whose personal data is transferred:_ + +Data subjects include the data exporter’s representatives and end-users including employees, contractors, collaborators, and customers of the data exporter. Data subjects may also include individuals attempting to communicate or transfer personal data to users of the services provided by data importer. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following types of data subjects in the personal data: +- Empleados, consultores y trabajadores temporales (actuales, previos o futuros) del exportador de los datos; +- Consultores/personas de contacto del exportador de datos (personas naturales) o los empleados, consultores o trabajadores temporales de la entidad legal de las personas de contacto/consultores (actuales, futuros, pasados); +- Users and other data subjects that are users of data exporter's services; +- Partners, stakeholders or individuals who actively collaborate, communicate or otherwise interact with employees of the data exporter and/or use communication tools such as apps and websites provided by the data exporter. + +_Categories of personal data transferred:_ + +The personal data transferred that is included in e-mail, documents and other data in an electronic form in the context of the Online Services or Professional Services. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following categories in the personal data: +- Basic personal data (for example place of birth, street name and house number (address), postal code, city of residence, country of residence, mobile phone number, first name, last name, initials, email address, gender, date of birth); +- Authentication data (for example user name, password or PIN code, security question, audit trail); +- Contact information (for example addresses, email, phone numbers, social media identifiers; emergency contact details); +- Unique identification numbers and signatures (for example IP addresses, employee number, student number); +- Pseudonymous identifiers; +- Photos, video and audio; +- Internet activity (for example browsing history, search history, reading and viewing activities); +- Device identification (for example IMEI-number, SIM card number, MAC address); +- Profiling (for example based on observed criminal or anti-social behavior or pseudonymous profiles based on visited URLs, click streams, browsing logs, IP-addresses, domains, apps installed, or profiles based on marketing preferences); +- Special categories of data as voluntarily provided by data subjects (for example racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health, data concerning a natural person’s sex life or sexual orientation, or data relating to criminal convictions or offences); or +- Any other personal data identified in Article 4 of the GDPR. + +_**Sensitive data** transferred (if applicable) and applied restrictions or safeguards that fully take into consideration the nature of the data and the risks involved, such as for instance strict purpose limitation, access restrictions (including access only for staff having followed specialised training), keeping a record of access to the data, restrictions for onward transfers or additional security measures:_
    GitHub does not request or otherwise ask for sensitive data and receives such data only if and when customers or data subjects decide to provide it. + +_**The frequency of the transfer** (e.g. whether the data is transferred on a one-off or continuous basis):_ + +Continuous as part of the Online Services or Professional Services. + +_**Nature of the processing:**_ + +The personal data transferred will be subject to the following basic processing activities: +
      +
    1. Duration and Object of Data Processing. The duration of data processing shall be for the term designated under the applicable GitHub Customer Agreement between data exporter and the data importer. The objective of the data processing is the performance of Online Services and Professional Services.
      2. +
    2. Personal Data Access. For the term designated under the applicable GitHub Customer Agreement, data importer will, at its election and as necessary under applicable law, either: (1) provide data exporter with the ability to correct, delete, or block personal data, or (2) make such corrections, deletions, or blockages on its behalf.
      3. +
    3. Data Exporter’s Instructions. For Online Services and Professional Services, data importer will only act upon data exporter’s instructions.
      4. +
    + +_Purpose(s) of the data transfer and further processing:_ + +The scope and purpose of processing personal data is described in the “Processing of Personal Data; GDPR” section of the DPA. The data importer operates a global network of data centers and management/support facilities, and processing may take place in any jurisdiction where data importer or its sub-processors operate such facilities in accordance with the “Security Practices and Policies” section of the DPA. + +_The period for which the personal data will be retained, or, if that is not possible, the criteria used to determine that period:_ + +Upon expiration or termination of data exporter’s use of Online Services or Professional Services, it may extract personal data and data importer will delete personal data, each in accordance with the DPA Terms applicable to the agreement. + +_For transfers to (sub-) processors, also specify subject matter, nature and duration of the processing:_ + +In accordance with the DPA, the data importer may hire other companies to provide limited services on data importer’s behalf, such as providing customer support. Any such subcontractors will be permitted to obtain personal data only to deliver the services the data importer has retained them to provide, and they are prohibited from using personal data for any other purpose. Unless a particular subcontractor is replaced ahead of time, the processing will be for the term designated under the applicable GitHub Customer Agreement between data exporter and data importer. + +### C. COMPETENT SUPERVISORY AUTHORITY + +_Identify the competent supervisory authority/ies in accordance with Clause 13:_ + +The supervisory authority with responsibility for ensuring compliance by the data exporter with Regulation (EU) 2016/679.   +## ANNEX II + +**to the Standard Contractual Clauses (EU/EEA)** + +**TECHNICAL AND ORGANISATIONAL MEASURES INCLUDING TECHNICAL AND ORGANISATIONAL MEASURES TO ENSURE THE SECURITY OF THE DATA** + +_Description of the technical and organisational measures implemented by the data importer(s) (including any relevant certifications) to ensure an appropriate level of security, taking into account the nature, scope, context and purpose of the processing, and the risks for the rights and freedoms of natural persons._ + +
      +
    1. Data Security Certifications. Data importer holds the following data security certifications:
      2. +
        +
      • SOC 1, Type 2;
        • +
      • SOC 2, Type 2;
        • +
      • NIST, to the extent incorporated for FedRAMP Low-Impact / Tailored ATO.
        • +
      +
    2. Personnel. Data importer’s personnel will not process personal data without authorization. Personnel are obligated to maintain the confidentiality of any such personal data and this obligation continues even after their engagement ends.
      3. +
    3. Data Privacy Contact. The data privacy officer of the data importer can be reached at the following address:

      + GitHub, Inc.
      + Attn: Privacy
      + 88 Colin P. Kelly Jr. Street
      + San Francisco, California 94107 USA

      4. +
    4. Technical and Organization Measures. The data importer has implemented and will maintain appropriate technical and organizational measures, internal controls, and information security routines intended to protect personal data, as defined in the Security Practices and Policies section of the DPA, against accidental loss, destruction, or alteration; unauthorized disclosure or access; or unlawful destruction as follows: The technical and organizational measures, internal controls, and information security routines set forth in the Data Security section of the DPA are hereby incorporated into this Annex II to Attachment 1 by this reference and are binding on the data importer as if they were set forth in this Annex 2 to Attachment 1 in their entirety.
      5. +
    + +_For transfers to (sub-) processors, also describe the specific technical and organisational measures to be taken by the (sub-) processor to be able to provide assistance to the controller and, for transfers from a processor to a sub-processor, to the data exporter:_ + +**Vendor management program - third-party risk program** + +The data importer has a vendor risk assessment process, vendor contract clauses and additional data protection agreements with vendors. Vendors undergo reassessment when a new business use case is requested. The data importer’s vendor risk program is structured so all of data importer’s vendors' risk assessments are refreshed two years from the last review date. + +Vendors deemed high risk, such as data center providers or other vendors storing or processing data in scope for the data importer’s regulatory or contractual requirements, undergo reassessment annually. + +## ANNEX III + +**to the Standard Contractual Clauses (EU/EEA)** + +**Additional Safeguards Addendum** + +By this Additional Safeguards Addendum to Standard Contractual Clauses (EU/EEA) (this “Addendum”), GitHub, Inc. (“GitHub”) provides additional safeguards to Customer and additional redress to the data subjects to whom Customer’s personal data relates. + +This Addendum supplements and is made part of, but is not in variation or modification of, the Standard Contractual Clauses (EU/EEA). + +
      +
    1. Challenges to Orders. In addition to Clause 15.1 of the Standard Contractual Clauses (EU/EEA), in the event GitHub receives an order from any third party for compelled disclosure of any personal data that has been transferred under the Standard Contractual Clauses (EU/EEA), GitHub shall:
      2. +
        +
      1. use every reasonable effort to redirect the third party to request data directly from Customer;
        2. +
      2. promptly notify Customer, unless prohibited under the law applicable to the requesting third party, and, if prohibited from notifying Customer, use all lawful efforts to obtain the right to waive the prohibition in order to communicate as much information to Customer as soon as possible; and
        3. +
      3. use all lawful efforts to challenge the order for disclosure on the basis of any legal deficiencies under the laws of the requesting party or any relevant conflicts with the law of the European Union or applicable Member State law.
        4. +

      + For purpose of this section, lawful efforts do not include actions that would result in civil or criminal penalty such as contempt of court under the laws of the relevant jurisdiction. +
    2. Indemnification of Data Subjects. Subject to Sections 3 and 4, GitHub shall indemnify a data subject for any material or non-material damage to the data subject caused by GitHub’s disclosure of personal data of the data subject that has been transferred under the Standard Contractual Clauses (EU/EEA) in response to an order from a non-EU/EEA government body or law enforcement agency (a “Relevant Disclosure”). Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under this Section 2 to the extent the data subject has already received compensation for the same damage, whether from GitHub or otherwise.
      3. +
    3. Conditions of Indemnification. Indemnification under Section 2 is conditional upon the data subject establishing, to GitHub’s reasonable satisfaction, that:
      4. +
        +
      1. GitHub engaged in a Relevant Disclosure;
        2. +
      2. the Relevant Disclosure was the basis of an official proceeding by the non-EU/EEA government body or law enforcement agency against the data subject; and
        3. +
      3. the Relevant Disclosure directly caused the data subject to suffer material or non-material damage.
        4. +

      + The data subject bears the burden of proof with respect to conditions a. though c.
      + Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under Section 2 if GitHub establishes that the Relevant Disclosure did not violate its obligations under Chapter V of the GDPR.
      +
    4. Scope of Damages. Indemnification under Section 2 is limited to material and non-material damages as provided in the GDPR and excludes consequential damages and all other damages not resulting from GitHub’s infringement of the GDPR.
      5. +
    5. Exercise of Rights. Rights granted to data subjects under this Addendum may be enforced by the data subject against GitHub irrespective of any restriction in Clauses 3 or 12 of the Standard Contractual Clauses (EU/EEA). The data subject may only bring a claim under this Addendum on an individual basis, and not part of a class, collective, group or representative action. Rights granted to data subjects under this Addendum are personal to the data subject and may not be assigned.
      6. +
    6. Notice of Change. In addition to Clause 14 of the Standard Contractual Clauses (EU/EEA), GitHub agrees and warrants that it has no reason to believe that the legislation applicable to it or its sub-processors, including in any country to which personal data is transferred either by itself or through a sub-processor, prevents it from fulfilling the instructions received from the data exporter and its obligations under this Addendum or the Standard Contractual Clauses (EU/EEA) and that in the event of a change in this legislation which is likely to have a substantial adverse effect on the warranties and obligations provided by this Addendum or the Standard Contractual Clauses (EU/EEA), it will promptly notify the change to Customer as soon as it is aware, in which case Customer is entitled to suspend the transfer of data and/or terminate the contract.
      7. +
    7. Termination. This Addendum shall automatically terminate if the European Commission, a competent Member State supervisory authority, or an EU or competent Member State court approves a different lawful transfer mechanism that would be applicable to the data transfers covered by the Standard Contractual Clauses (EU/EEA) (and if such mechanism applies only to some of the data transfers, this Addendum will terminate only with respect to those transfers) and that does not require the additional safeguards set forth in this Addendum.
      8. +
    + +

    Attachment 2 – The Standard Contractual Clauses (UK)

    + +Execution of the GitHub Customer Agreement by Customer includes execution of this Attachment 2, which is countersigned by GitHub, Inc. + +En los países donde se requiera de aprobación regulatoria para utilizar las Cláusulas Contractuales Estándar, no se podrá depender de éstas bajo la Comisión Europea 2010/87/EU (de febrero de 2010) para legitimar la exportación de datos del país en cuestión, a menos de que el cliente tenga la aprobación regulatoria requerida. + +Beginning May 25, 2018 and thereafter, references to various Articles from the Directive 95/46/EC in the Standard Contractual Clauses below will be treated as references to the relevant and appropriate Articles in the GDPR. + +For the purposes of Article 26(2) of Directive 95/46/EC for the transfer of personal data to processors established in third countries which do not ensure an adequate level of data protection, Customer (as data exporter) and GitHub, Inc. (as data importer, whose signature appears below), each a “party,” together “the parties,” have agreed on the following Contractual Clauses (the “Clauses” or “Standard Contractual Clauses”) in order to adduce adequate safeguards with respect to the protection of privacy and fundamental rights and freedoms of individuals for the transfer by the data exporter to the data importer of the personal data specified in Appendix 1. + +### Cláusula 1: Definiciones + +
      +
    1. 'personal data', 'special categories of data', 'process/processing', 'controller', 'processor', 'data subject' and 'supervisory authority' shall have the same meaning as in Directive 95/46/EC of the European Parliament and of the Council of 24 October 1995 on the protection of individuals with regard to the processing of personal data and on the free movement of such data;
      2. +
    2. 'the data exporter' means the controller who transfers the personal data;
      3. +
    3. 'the data importer' means the processor who agrees to receive from the data exporter personal data intended for processing on his behalf after the transfer in accordance with his instructions and the terms of the Clauses and who is not subject to a third country's system ensuring adequate protection within the meaning of Article 25(1) of Directive 95/46/EC;
      4. +
    4. 'the subprocessor' means any processor engaged by the data importer or by any other subprocessor of the data importer who agrees to receive from the data importer or from any other subprocessor of the data importer personal data exclusively intended for processing activities to be carried out on behalf of the data exporter after the transfer in accordance with his instructions, the terms of the Clauses and the terms of the written subcontract;
      5. +
    5. 'the applicable data protection law' means the legislation protecting the fundamental rights and freedoms of individuals and, in particular, their right to privacy with respect to the processing of personal data applicable to a data controller in the Member State in which the data exporter is established;
      6. +
    6. 'technical and organisational security measures' means those measures aimed at protecting personal data against accidental or unlawful destruction or accidental loss, alteration, unauthorised disclosure or access, in particular where the processing involves the transmission of data over a network, and against all other unlawful forms of processing.
      7. +
    + +### Cláusula 2: Detalles de la transferencia + +Los detalles de la transferencia y, en particular, de las categorías especiales de datos personales en donde sean aplicables se especifican en el Apéndice 1 que se encuentra más adelante, el cual forma una parte integral de las Cláusulas. + +### Cláusula 3: Cláusula de beneficiario tercero + +
      +
    1. El titular de los datos podrá hacer valer la ley contra el exportador de datos en esta Cláusula, la Cláusula 4(b) a (i), la Cláusula 5(a) a (e), y de (g) a (j), la Cláusula 6(1) y (2), la Cláusula 8(2), y las Cláusulas 9 a 12 como beneficiario tercero.
      2. +
    2. El titular de los datos podrá hacer valer la ley contra el importador de datos en esta Cláusula, la Cláusula 5(a) a (e) y (g), la Cláusula 6, Cláusula 7, Clúsula 8(2) y las Cláusulas 9 a 12, en los casos en donde el exportador de los datos haya desaparecido realmente o haya dejado de existir en la ley a menos de que alguna entidad de sucesión haya asumido las obligaciones legales integrales del exportador de datos mediante onctrato o mediante la operación legal, como resultado de que lo que asume en los derechos y obligaciones del exportador de datos, en cuyo caso, el titular de los datos podrá hacer valor esto contra dicha entidad.
      3. +
    3. El sujeto de los datos puede aplicar la ley en contra del subprocesador de esta Cláusula, la Cláusula 5(a) a (e) y (g), Cláusula 6, Cláusula 7, Cláusula 8(2) y Cláusulas 9 a 12, en casos en donde tanto el exportador como el importador de los datos hayan desaparecido realmente o dejado de existir en la ley o se hayan declarado insolventes, a menos de que cualquier entidad sucesora haya asumido todas las obligaciones del exportador de los datos contractualmente o conforme a derecho que resulte en la toma de derchos y obligaciones del exportador de datos, en cuyo caso, el titular de los datos puede aplicar la ley en contra de dicha entidad. Dicha responsabilidad de terceros del subprocesador se limitará a sus propias operaciones de procesamiento bajo las Cláusulas.
      4. +
    4. Las partes no se oponen a que un titular de los datos se represente mediante una asociación o cualquier otro cuerpo si dicho titular así lo desea expresamente y si la ley nacional lo permite.
      5. +
    + +### Cláusula 4: Las obligaciones del exportador de los datos + +El exportador de los datos acuerda y garantiza: + +
      +
    1. that the processing, including the transfer itself, of the personal data has been and will continue to be carried out in accordance with the relevant provisions of the applicable data protection law (and, where applicable, has been notified to the relevant authorities of the Member State where the data exporter is established) and does not violate the relevant provisions of that State;
      2. +
    2. that it has instructed and throughout the duration of the personal data processing services will instruct the data importer to process the personal data transferred only on the data exporter's behalf and in accordance with the applicable data protection law and the Clauses;
      3. +
    3. that the data importer will provide sufficient guarantees in respect of the technical and organisational security measures specified in Appendix 2 below;
      4. +
    4. that after assessment of the requirements of the applicable data protection law, the security measures are appropriate to protect personal data against accidental or unlawful destruction or accidental loss, alteration, unauthorised disclosure or access, in particular where the processing involves the transmission of data over a network, and against all other unlawful forms of processing, and that these measures ensure a level of security appropriate to the risks presented by the processing and the nature of the data to be protected having regard to the state of the art and the cost of their implementation;
      5. +
    5. that it will ensure compliance with the security measures;
      6. +
    6. that, if the transfer involves special categories of data, the data subject has been informed or will be informed before, or as soon as possible after, the transfer that its data could be transmitted to a third country not providing adequate protection within the meaning of Directive 95/46/EC;
      7. +
    7. to forward any notification received from the data importer or any subprocessor pursuant to Clause 5(b) and Clause 8(3) to the data protection supervisory authority if the data exporter decides to continue the transfer or to lift the suspension;
      8. +
    8. to make available to the data subjects upon request a copy of the Clauses, with the exception of Appendix 2, and a summary description of the security measures, as well as a copy of any contract for subprocessing services which has to be made in accordance with the Clauses, unless the Clauses or the contract contain commercial information, in which case it may remove such commercial information;
      9. +
    9. that, in the event of subprocessing, the processing activity is carried out in accordance with Clause 11 by a subprocessor providing at least the same level of protection for the personal data and the rights of data subject as the data importer under the Clauses; and
      10. +
    10. that it will ensure compliance with Clause 4(a) to (i).
      11. +
    + +### Cláusula 5: Obligaciones del importador de los datos + +El importador de los datos acuerda y garantiza: + +
      +
    1. to process the personal data only on behalf of the data exporter and in compliance with its instructions and the Clauses; if it cannot provide such compliance for whatever reasons, it agrees to inform promptly the data exporter of its inability to comply, in which case the data exporter is entitled to suspend the transfer of data and/or terminate the contract;
      2. +
    2. that it has no reason to believe that the legislation applicable to it prevents it from fulfilling the instructions received from the data exporter and its obligations under the contract and that in the event of a change in this legislation which is likely to have a substantial adverse effect on the warranties and obligations provided by the Clauses, it will promptly notify the change to the data exporter as soon as it is aware, in which case the data exporter is entitled to suspend the transfer of data and/or terminate the contract;
      3. +
    3. that it has implemented the technical and organisational security measures specified in Appendix 2 before processing the personal data transferred;
      4. +
    4. that it will promptly notify the data exporter about:
      5. +
        +
      1. any legally binding request for disclosure of the personal data by a law enforcement authority unless otherwise prohibited, such as a prohibition under criminal law to preserve the confidentiality of a law enforcement investigation,
        2. +
      2. any accidental or unauthorised access, and
        3. +
      3. any request received directly from the data subjects without responding to that request, unless it has been otherwise authorised to do so;
        4. +
      + to deal promptly and properly with all inquiries from the data exporter relating to its processing of the personal data subject to the transfer and to abide by the advice of the supervisory authority with regard to the processing of the data transferred; + at the request of the data exporter to submit its data processing facilities for audit of the processing activities covered by the Clauses which shall be carried out by the data exporter or an inspection body composed of independent members and in possession of the required professional qualifications bound by a duty of confidentiality, selected by the data exporter, where applicable, in agreement with the supervisory authority; +
    5. to make available to the data subject upon request a copy of the Clauses, or any existing contract for subprocessing, unless the Clauses or contract contain commercial information, in which case it may remove such commercial information, with the exception of Appendix 2 which shall be replaced by a summary description of the security measures in those cases where the data subject is unable to obtain a copy from the data exporter;
      6. +
    6. that, in the event of subprocessing, it has previously informed the data exporter and obtained its prior written consent;
      7. +
    7. that the processing services by the subprocessor will be carried out in accordance with Clause 11; and
      8. +
    8. to send promptly a copy of any subprocessor agreement it concludes under the Clauses to the data exporter.
      9. +
    + +### Cláusula 6: Responsabilidades + +
      +
    1. Las partes concuerdan que cualquier titular de los datos que haya sufrido daños como resultado de cualquier violación a las obligaciones descritas en la Cláusula 3 o en la Cláusula 11 por parte de cualquier subprocesador tiene derecho a recibir una compensación del exportador de los datos por dicho daño sufrido.
      2. + +
    2. If a data subject is not able to bring a claim for compensation in accordance with paragraph 1 against the data exporter, arising out of a breach by the data importer or his subprocessor of any of their obligations referred to in Clause 3 or in Clause 11, because the data exporter has factually disappeared or ceased to exist in law or has become insolvent, the data importer agrees that the data subject may issue a claim against the data importer as if it were the data exporter, unless any successor entity has assumed the entire legal obligations of the data exporter by contract of by operation of law, in which case the data subject can enforce its rights against such entity.

      + The data importer may not rely on a breach by a subprocessor of its obligations in order to avoid its own liabilities.
      3. + +
    3. Si un titular de los datos no puede presentar un reclamo en contra del exportador o importador de los datos a los cuales se hace referencia en los párrafos 1 y 2, derivado de una violación por parte del subprocesador o por cualquiera de sus obligaciones explicadas en la Cláusula 2 o en la Cláusula 11 ya que ambos, importador y exportador, hayan desaparecido realmente o dejado de existir ante la ley, o se hayan declarado insolventes, el subprocesador acuerda que el titular de los datos podrá emitir un reclamo contra el subprocesador de los datos con respecto a sus propias operaciones de procesamiento bajo las Cláusulas como si fuera el exportador o importador de los mismos, a menos de que cualquier entidad sucesora haya asumido las obligaciones íntegras del exportador o importador de los datos contractualmente o por aplicación de la ley, en cuyo caso, el titular de los datos puede hacer valer sus derechos en contra de dicha entidad. La responsabilidad del subprocesador deberá limitarse a sus propias operaciones de procesamiento bajo las Cláusulas.
      4. +
    + +### Cláusula 7: Mediación y Jurisdicción + +
      +
    1. El iimportador de los datos acuerda que si el titular de los datos apelase en contra de sus derechos de beneficiario tercero y/o reclama una compensación por daños bajo las Cláusulas, el importador de los datos aceptará la decisión del titular de los datos: +
        +
      1. to refer the dispute to mediation, by an independent person or, where applicable, by the supervisory authority; +
      2. to refer the dispute to the courts in the Member State in which the data exporter is established. +
      +
    2. Las partes acuerdan que la elección que haga el titular de los datos no perjudicará sus derechos sustantivos o procesales para buscar remedios de acuerdo con otras disposiciones de la ley internacional o nacional. +
    + +### Cláusula 8: Cooperación con las autoridades supervisantes + +
      +
    1. El exportador de los datos acuerda depositar una copia de este contrato con la autoridad supervisora si así lo requiere o si dicho depósito se requiere bajo la ley de protección de datos aplicable.
      2. + +
    2. Las partes concuerdan que la autoridad supervisora tiene el derecho de conducir una auditoría del importador de los datos, y de cualquier subprocesador, la cual tiene el mismo alcance y está sujeta a las mismas condiciones que aplcarían en una auditoría del exportador de los datos bajo la ley de protección de datos aplicable.
      3. + +
    3. El importador de los datos deberá informar de manera oportuna al exportador de los datos acerca de la existencia de la legislación aplicable a éste o a cualquier subprocesador, previniendo la conducción de una auditoría al importador de los datos o a cualquier subprocesador de acuerdo con el párrafo 2. En tal caso, el exportador de datos tendrá derecho de tomar las medidas previstas en la Cláusula 5 (b).
      4. +
    + +### Cláusula 9: Ley Aplicable. + +Las Cláusulas deberán regirse por medio de la ley del Estado Miembro en el cual se establece el exportador de los datos. + +### Cláusula 10: Variación del contrato + +Las partes se comprometen a no variar o modificar las Cláusulas. Esto no impide que las partes agreguen cláusulas sobre los asuntos relacionados con los negocios conforme se requieran mientras que éstas no contradigan la Cláusula. + +### Cláusula 11: Subprocesamiento + +
      +
    1. El importador de los datos no deberá subcontratar ninguna de sus operaciones de procesamiento que se realicen en nombre del exportador de los datos bajo las Cláusulas sin el consentimiento previo y por escrito del exportador de los datos. En caso de que el importador de los datos subcontrate sus obligaciones debajo de las Cláusulas, con el consentimiento del exportador de los datos, deberá hacerlo únicamente por medio de un contrato por escrito con el subprocesador, el cual imponga las mismas obligaciones en el subprocesador que se impusieron en el importador de los datos bajo las Cláusulas. Donde sea que el subprocesador incumpla con sus obligaciones de protección de datos bajo dicho contrato por escrito, el importador de los datos deberá ser plenamente responsable del exportador de los datos por el cumplimiento de las obligaciones del subprocesador bajo dicho contrato.
      2. + +
    2. El contrato escrito previo entre el importador de los datos y el subprocesador también deberá proporcionar una cláusula de terceros beneficiarios de acuerdo con lo asentado en la Cláusula 3 para los casos en donde el titular de los datos no pueda preentar una reclamación de compensación como se refiere en el párrafo 1 de la Cláusula 6 en contra del exportador o del importador de los datos debido a que han desaparecido realmente o han dejado de existir ante la ley o se hayan declarado insolventes y ninguna entidad sucesora haya asumido las obligaciones legales íntegras del exportador o importador de los datos contractualmente o mediante la ley aplicable. Dicha responsabilidad de terceros del subprocesador se limitará a sus propias operaciones de procesamiento bajo las Cláusulas.
      3. + +
    3. Las disposiciones que se relacionan con los aspectos de protección de datos para el subprocesamiento del cntracto al cual se refiere en el párrafo 1 deberán regirse por la ley del Estado Miembro en el cual se establezca el exportador de los datos.
      4. + +
    4. El exportador de los datos deberá mantener una lista de contratos de subprocesamiento que se celebren bajo las Cláusulas y que el importador de los datos notifique de acuerdo con la Cláusula 5 (j), la cual se debe actualizar por lo menos una vez al año. La lista deberá estar disponible para la autoridad supervisora de protección de datos del exportador de los datos.
      5. +
    + +### Cláusula 12: Obligaciones después de la terminación de los servicios de procesamiento de datos personales + +
      +
    1. Las partes acuerdan que, en la terminación de la prestación de los servicios de procesamiento de datos, el importador y subprocesador de los mismos deberá, a elección del exportador, regresar todos los datos personales transferidos y las copias de los mismos al exportador de los datos o deberá destruir todos los dtos personales y certificar ante el exportador de los datos que así lo ha hecho, a menos de que la legislación impuesta en el importador de los datos impida que regrese o destrulla todos o parte de los datos personales transferidos. En dado caso, el importador de los datos justifica que garantizará la confidencialidad de los datos personales transferidos y que ya no procesará activamente dichos datos personales.
      2. + +
    2. El importador de los datos y el subprocesador garantizan que, bajo solicitud del exportador de los datos y/o de la autoridad supervisora, emitirán sus instalaciones de procesamiento de datos para auditoría de las medidas descritas en el párrafo 1.
      3. +
    + +### Appendix 1 to the Standard Contractual Clauses (UK) + +**Data exporter**: Customer is the data exporter. The data exporter is a user of Online Services or Professional Services as defined in the DPA and GitHub Customer Agreement. + +**Data importer**: The data importer is GitHub, Inc., a global producer of software and services. + +**Data subjects**: Data subjects include the data exporter’s representatives and end-users including employees, contractors, collaborators, and customers of the data exporter. Data subjects may also include individuals attempting to communicate or transfer personal data to users of the services provided by data importer. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following types of data subjects in the personal data: +- Empleados, consultores y trabajadores temporales (actuales, previos o futuros) del exportador de los datos; +- Consultores/personas de contacto del exportador de datos (personas naturales) o los empleados, consultores o trabajadores temporales de la entidad legal de las personas de contacto/consultores (actuales, futuros, pasados); +- Users and other data subjects that are users of data exporter's services; +- Partners, stakeholders or individuals who actively collaborate, communicate or otherwise interact with employees of the data exporter and/or use communication tools such as apps and websites provided by the data exporter. + +**Categories of data**: The personal data transferred that is included in e-mail, documents and other data in an electronic form in the context of the Online Services or Professional Services. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following categories in the personal data: +- Basic personal data (for example place of birth, street name and house number (address), postal code, city of residence, country of residence, mobile phone number, first name, last name, initials, email address, gender, date of birth); +- Authentication data (for example user name, password or PIN code, security question, audit trail); +- Contact information (for example addresses, email, phone numbers, social media identifiers; emergency contact details); +- Unique identification numbers and signatures (for example IP addresses, employee number, student number); +- Pseudonymous identifiers; +- Photos, video and audio; +- Internet activity (for example browsing history, search history, reading and viewing activities); +- Device identification (for example IMEI-number, SIM card number, MAC address); +- Profiling (for example based on observed criminal or anti-social behavior or pseudonymous profiles based on visited URLs, click streams, browsing logs, IP-addresses, domains, apps installed, or profiles based on marketing preferences); +- Special categories of data as voluntarily provided by data subjects (for example racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health, data concerning a natural person’s sex life or sexual orientation, or data relating to criminal convictions or offences); or +- Any other personal data identified in Article 4 of the GDPR. + +**Processing operations**: The personal data transferred will be subject to the following basic processing activities: + +
      +
    1. Duration and Object of Data Processing. The duration of data processing shall be for the term designated under the applicable GitHub Customer Agreement between data exporter and data importer. The objective of the data processing is the performance of Online Services and Professional Services.
      2. +
    2. Scope and Purpose of Data Processing. The scope and purpose of processing personal data is described in the “Processing of Personal Data; GDPR” section of the DPA. The data importer operates a global network of data centers and management/support facilities, and processing may take place in any jurisdiction where data importer or its sub-processors operate such facilities in accordance with the “Security Practices and Policies” section of the DPA.
      3. +
    3. Personal Data Access. For the term designated under the applicable GitHub Customer Agreement data importer will at its election and as necessary under applicable law, either: (1) provide data exporter with the ability to correct, delete, or block personal data, or (2) make such corrections, deletions, or blockages on its behalf.
      4. +
    4. Data Exporter’s Instructions. For Online Services and Professional Services, data importer will only act upon data exporter’s instructions as conveyed by GitHub.
      5. +
    5. Personal Data Deletion or Return. Upon expiration or termination of data exporter’s use of Online Services or Professional Services, it may extract personal data and data importer will delete personal data, each in accordance with the DPA Terms applicable to the agreement.
      6. +
    + +**Subcontractors**: In accordance with the DPA, the data importer may hire other companies to provide limited services on data importer’s behalf, such as providing customer support. Any such subcontractors will be permitted to obtain personal data only to deliver the services the data importer has retained them to provide, and they are prohibited from using personal data for any other purpose. + +### Appendix 2 to the Standard Contractual Clauses (UK) + +Descripción de las medidas de seguridad técnicas y organizacionales implementadas por el importador de los datos de acuerdo con las Cláusulas 4(d) y 5(c): + +
      +
    1. Personnel. Data importer’s personnel will not process personal data without authorization. Personnel are obligated to maintain the confidentiality of any such personal data and this obligation continues even after their engagement ends.
      2. + +
    2. Data Privacy Contact. The data privacy officer of the data importer can be reached at the following address:
      +GitHub, Inc.
      +Attn: Privacy
      +88 Colin P. Kelly Jr. Street
      +San Francisco, California 94107 USA
      3. + +
    3. Technical and Organization Measures. The data importer has implemented and will maintain appropriate technical and organizational measures, internal controls, and information security routines intended to protect personal data, as defined in the Security Practices and Policies section of the DPA, against accidental loss, destruction, or alteration; unauthorized disclosure or access; or unlawful destruction as follows: The technical and organizational measures, internal controls, and information security routines set forth in the Security Practices and Policies section of the DPA are hereby incorporated into this Appendix 2 by this reference and are binding on the data importer as if they were set forth in this Appendix 2 in their entirety.
      4. +
    + +### Appendix 3 to the Standard Contractual Clauses (UK) + +**Additional Safeguards Addendum** + +By this Additional Safeguards Addendum to Standard Contractual Clauses (UK) (this “Addendum”), GitHub, Inc. (“GitHub”) provides additional safeguards to Customer and additional redress to the data subjects to whom Customer’s personal data relates. + +This Addendum supplements and is made part of, but is not in variation or modification of, the Standard Contractual Clauses (UK). + +
      +
    1. Challenges to Orders. In addition to Clause 5(d)(i) of the Standard Contractual Clauses (UK), in the event GitHub receives an order from any third party for compelled disclosure of any personal data that has been transferred under the Standard Contractual Clauses (UK), GitHub shall:
      2. +
        +
      1. use every reasonable effort to redirect the third party to request data directly from Customer;
        2. +
      2. promptly notify Customer, unless prohibited under the law applicable to the requesting third party, and, if prohibited from notifying Customer, use all lawful efforts to obtain the right to waive the prohibition in order to communicate as much information to Customer as soon as possible; and
        3. +
      3. use all lawful efforts to challenge the order for disclosure on the basis of any legal deficiencies under the laws of the requesting party or any relevant conflicts with the law of the European Union or applicable Member State law.
        4. +

      + For purpose of this section, lawful efforts do not include actions that would result in civil or criminal penalty such as contempt of court under the laws of the relevant jurisdiction. +
    2. Indemnification of Data Subjects. Subject to Sections 3 and 4, GitHub shall indemnify a data subject for any material or non-material damage to the data subject caused by GitHub’s disclosure of personal data of the data subject that has been transferred under the Standard Contractual Clauses (UK) in response to an order from a non-EU/EEA government body or law enforcement agency (a “Relevant Disclosure”). Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under this Section 2 to the extent the data subject has already received compensation for the same damage, whether from GitHub or otherwise.
      3. +
    3. Conditions of Indemnification. Indemnification under Section 2 is conditional upon the data subject establishing, to GitHub’s reasonable satisfaction, that:
      4. +
        +
      1. GitHub engaged in a Relevant Disclosure;
        2. +
      2. the Relevant Disclosure was the basis of an official proceeding by the non-EU/EEA government body or law enforcement agency against the data subject; and
        3. +
      3. the Relevant Disclosure directly caused the data subject to suffer material or non-material damage.
        4. +

      + The data subject bears the burden of proof with respect to conditions a. though c.
      + Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under Section 2 if GitHub establishes that the Relevant Disclosure did not violate its obligations under Chapter V of the GDPR. +
    4. Scope of Damages. Indemnification under Section 2 is limited to material and non-material damages as provided in the GDPR and excludes consequential damages and all other damages not resulting from GitHub’s infringement of the GDPR.
      5. +
    5. Exercise of Rights. Rights granted to data subjects under this Addendum may be enforced by the data subject against GitHub irrespective of any restriction in Clauses 3 or 6 of the Standard Contractual Clauses (UK). The data subject may only bring a claim under this Addendum on an individual basis, and not part of a class, collective, group or representative action. Rights granted to data subjects under this Addendum are personal to the data subject and may not be assigned.
      6. +
    6. Notice of Change. In addition to Clause 5(b) of the Standard Contractual Clauses (UK), GitHub agrees and warrants that it has no reason to believe that the legislation applicable to it or its sub-processors, including in any country to which personal data is transferred either by itself or through a sub-processor, prevents it from fulfilling the instructions received from the data exporter and its obligations under this Addendum or the Standard Contractual Clauses (UK) and that in the event of a change in this legislation which is likely to have a substantial adverse effect on the warranties and obligations provided by this Addendum or the Standard Contractual Clauses (UK), it will promptly notify the change to Customer as soon as it is aware, in which case Customer is entitled to suspend the transfer of data and/or terminate the contract. +
    7. Termination. This Addendum shall automatically terminate if the European Commission, a competent Member State supervisory authority, or an EU or competent Member State court approves a different lawful transfer mechanism that would be applicable to the data transfers covered by the Standard Contractual Clauses (UK) (and if such mechanism applies only to some of the data transfers, this Addendum will terminate only with respect to those transfers) and that does not require the additional safeguards set forth in this Addendum.

      + Signing the Standard Contractual Clauses (UK), Appendix 1, Appendix 2 and +
    + +

    Attachment 3 – European Union General Data Protection Regulation Terms

    + +GitHub makes the commitments in these GDPR Related Terms, to all customers effective May 25, 2018. These commitments are binding upon GitHub with regard to Customer regardless of (1) the version of the GitHub Customer Agreement and DPA that is otherwise applicable to any given Online Services subscription or (2) any other agreement that references this attachment. + +For purposes of these GDPR Related Terms, Customer and GitHub agree that Customer is the controller of Personal Data and GitHub is the processor of such data, except when Customer acts as a processor of Personal Data, in which case GitHub is a subprocessor. These GDPR Related Terms apply to the processing of Personal Data, within the scope of the GDPR, by GitHub on behalf of Customer. These GDPR Related Terms do not limit or reduce any data protection commitments GitHub makes to Customer in the GitHub Customer Agreement or other agreement between GitHub and Customer. These GDPR Related Terms do not apply where GitHub is a controller of Personal Data. + +**Relevant GDPR Obligations: Articles 28, 32, and 33** + +
      +
    1. GitHub shall not engage another processor without prior specific or general written authorisation of Customer. In the case of general written authorisation, GitHub shall inform Customer of any intended changes concerning the addition or replacement of other processors, thereby giving Customer the opportunity to object to such changes. (Article 28(2))
      2. +
    2. Processing by GitHub shall be governed by these GDPR Related Terms under European Union (hereafter “Union”) or Member State law and are binding on GitHub with regard to Customer. The subject-matter and duration of the processing, the nature and purpose of the processing, the type of Personal Data, the categories of data subjects and the obligations and rights of the Customer are set forth in the Customer’s licensing agreement, including these GDPR Related Terms. In particular, GitHub shall:
      3. +
        +
      1. process the Personal Data only on documented instructions from Customer, including with regard to transfers of Personal Data to a third country or an international organisation, unless required to do so by Union or Member State law to which GitHub is subject; in such a case, GitHub shall inform Customer of that legal requirement before processing, unless that law prohibits such information on important grounds of public interest;
        2. +
      2. ensure that persons authorised to process the Personal Data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality;
        3. +
      3. take all measures required pursuant to Article 32 of the GDPR;
        4. +
      4. respect the conditions referred to in paragraphs 1 and 3 for engaging another processor;
        5. +
      5. taking into account the nature of the processing, assist Customer by appropriate technical and organisational measures, insofar as this is possible, for the fulfilment of the Customer’s obligation to respond to requests for exercising the data subject's rights laid down in Chapter III of the GDPR;
        6. +
      6. assist Customer in ensuring compliance with the obligations pursuant to Articles 32 to 36 of the GDPR, taking into account the nature of processing and the information available to GitHub;
        7. +
      7. at the choice of Customer, delete or return all the Personal Data to Customer after the end of the provision of services relating to processing, and delete existing copies unless Union or Member State law requires storage of the Personal Data;
        8. +
      8. make available to Customer all information necessary to demonstrate compliance with the obligations laid down in Article 28 of the GDPR and allow for and contribute to audits, including inspections, conducted by Customer or another auditor mandated by Customer.
        9. +

      + GitHub shall immediately inform Customer if, in its opinion, an instruction infringes the GDPR or other Union or Member State data protection provisions. (Article 28(3))

      +
    3. Where GitHub engages another processor for carrying out specific processing activities on behalf of Customer, the same data protection obligations as set out in these GDPR Related Terms shall be imposed on that other processor by way of a contract or other legal act under Union or Member State law, in particular providing sufficient guarantees to implement appropriate technical and organisational measures in such a manner that the processing will meet the requirements of the GDPR. Where that other processor fails to fulfil its data protection obligations, GitHub shall remain fully liable to the Customer for the performance of that other processor's obligations. (Article 28(4))
      4. +
    4. Taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of processing as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons, Customer and GitHub shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, including inter alia as appropriate:
      5. +
        +
      1. the pseudonymisation and encryption of Personal Data;
        2. +
      2. the ability to ensure the ongoing confidentiality, integrity, availability and resilience of processing systems and services;
        3. +
      3. the ability to restore the availability and access to Personal Data in a timely manner in the event of a physical or technical incident; and
        4. +
      4. a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the processing. (Article 32(1))
        5. +
      +
    5. In assessing the appropriate level of security, account shall be taken of the risks that are presented by processing, in particular from accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to Personal Data transmitted, stored or otherwise processed (Article 32(2)).
      6. +
    6. Customer and GitHub shall take steps to ensure that any natural person acting under the authority of Customer or GitHub who has access to Personal Data does not process them except on instructions from Customer, unless he or she is required to do so by Union or Member State law (Article 32(4)).
      7. +
    7. GitHub shall notify Customer without undue delay after becoming aware of a Personal Data breach (Article 33(2)). Such notification will include that information a processor must provide to a controller under Article 33(3) to the extent such information is reasonably available to GitHub.
      8. +
    + +--------------- + +

    (1) The Agreement on the European Economic Area (EEA Agreement) provides for the extension of the European Union’s internal market to the three EEA States Iceland, Liechtenstein and Norway. The Union data protection legislation, including Regulation (EU) 2016/679, is covered by the EEA Agreement and has been incorporated into Annex XI thereto. Therefore, any disclosure by the data importer to a third party located in the EEA does not qualify as an onward transfer for the purpose of these Clauses.

    + +

    (2) This requirement may be satisfied by the sub-processor acceding to these Clauses under the appropriate Module, in accordance with Clause 7.

    + +

    (3) As regards the impact of such laws and practices on compliance with these Clauses, different elements may be considered as part of an overall assessment. Such elements may include relevant and documented practical experience with prior instances of requests for disclosure from public authorities, or the absence of such requests, covering a sufficiently representative time-frame. This refers in particular to internal records or other documentation, drawn up on a continuous basis in accordance with due diligence and certified at senior management level, provided that this information can be lawfully shared with third parties. Where this practical experience is relied upon to conclude that the data importer will not be prevented from complying with these Clauses, it needs to be supported by other relevant, objective elements, and it is for the Parties to consider carefully whether these elements together carry sufficient weight, in terms of their reliability and representativeness, to support this conclusion. In particular, the Parties have to take into account whether their practical experience is corroborated and not contradicted by publicly available or otherwise accessible, reliable information on the existence or absence of requests within the same sector and/or the application of the law in practice, such as case law and reports by independent oversight bodies.

    diff --git a/translations/es-ES/content/github/site-policy/github-terms-for-additional-products-and-features.md b/translations/es-ES/content/github/site-policy/github-terms-for-additional-products-and-features.md index db587fbe05..641fd1fa47 100644 --- a/translations/es-ES/content/github/site-policy/github-terms-for-additional-products-and-features.md +++ b/translations/es-ES/content/github/site-policy/github-terms-for-additional-products-and-features.md @@ -9,7 +9,7 @@ topics: - Legal --- -Version Effective Date: August 10, 2021 +Fecha de entrada en vigor de la versión: 10 de agosto de 2021 Cuando utilices GitHub, podría que se te otorgue acceso a muchos productos y características adicionales ("Características y Productos Adicionales"). Ya que muchas de las Características y Productos Adicionales ofrecen funcionalidades diferentes, las condiciones específicas para dicho producto o característica podrán aplicarse adicionalmente a tu contrato principal con nosotros—las Condiciones de Servicio de GitHub, las Condiciones de Servicio Corporativo de GitHub, las Condiciones Generales de GitHub o el acuerdo de licenciamiento por volumen de Microsoft (cada uno de ellos conocidos como el "Acuerdo"). A continuación, listamos aquellos productos y características jutno con las condiciones adicionales correspondientes que aplican al uso que les des. @@ -25,12 +25,12 @@ Al utilizar las características y productos adicionales, también estás de acu ## Acciones Acciones de GitHub te permiten crear flujos de trabajo de ciclo de vida de desarrollo del software personalizado directamente en tu repositorio de GitHub. Las acciones se facturan conforme se utilizan. La [Documentación de las acciones](/actions) incluye detalles como las cantidades de procesamiento y almacenamiento (dependiendo del plan de tu cuenta), y el cómo monitorear el uso de minutos de tus acciones y configurar los límites de uso. -Actions and any elements of the Actions product or service may not be used in violation of the Agreement, the [GitHub Acceptable Use Polices](/github/site-policy/github-acceptable-use-policies), or the GitHub Actions service limitations set forth in the [Actions documentation](/actions/reference/usage-limits-billing-and-administration). Additionally, regardless of whether an Action is using self-hosted runners, Actions should not be used for: +No podrán utilizarse las acciones ni cualquier elemento del servicio de este producto para violar el acuerdo, las [Políticas de uso aceptable de GitHub](/github/site-policy/github-acceptable-use-policies), ni las limitaciones del servicio de Github, las cuales se establecen en la [Documentación de las acciones](/actions/reference/usage-limits-billing-and-administration). Adicionalmente, sin importar si la acción utiliza ejecutores auto-hospedados, estas no deben utilizarse para: - criptominería; -- disrupting, gaining, or attempting to gain unauthorized access to, any service, device, data, account, or network (other than those authorized by the [GitHub Bug Bounty program](https://bounty.github.com)); -- the provision of a stand-alone or integrated application or service offering the Actions product or service, or any elements of the Actions product or service, for commercial purposes; +- perturbar, ganar o intentar ganar acceso no autorizado a cualquier servicio, dispositivo, datos, cuenta o red (diferentes a aquellos que autoriza el [programa de Recompensas por Errores de GitHub](https://bounty.github.com)); +- la provisión de un servicio o aplicación integrado o independiente que ofrezca el producto o servicio de las acciones o cualquier elemento del servicio o producto de las acciones para propósitos comerciales; - cualquier actividad que coloque un peso en nuestros servidores, ya sea que dicho peso sea excesivo para los beneficios que se proporcionan a los usuarios (por ejemplo, no utilizamos acciones como una red de entrega de contenido o como parte de una aplicación sin servidores, pero una acción de beneficio mínimo podría estar bien si también implica un peso mínimo); o -- if using GitHub-hosted runners, any other activity unrelated to the production, testing, deployment, or publication of the software project associated with the repository where GitHub Actions are used. +- si estás utilizando los ejecutores hospedados en GitHub, cualquier otra actividad sin relación a la producción, pruebas, despliegue o publicación del proyecto de software asociado con el repositorio en donde se utilizan las GitHub Actions. Para evitar violaciones de estas limitaciones y abuso de las Acciones de GitHub, GitHub puede controlar tu uso de Acciones de GitHub. El mal uso de las GitHub Actions podría dar como resultado la terminación de jobs, restricciones en tu capacidad para utilizar las GitHub Actions, o inhabilitar los repositorios que se crearon para ejecutar las acciones de una forma que viole estas condiciones. @@ -38,7 +38,7 @@ Para evitar violaciones de estas limitaciones y abuso de las Acciones de GitHub, ## Advanced Security GitHub hace características de seguridad adicionales para los clientes bajo una licencia de Seguridad Avanzada. Estas características incluyen el escaneo de código, escaneo de secretos y revisión de dependencias. La [Documentación de la seguridad avanzada](/github/getting-started-with-github/about-github-advanced-security) proporciona más detalles. -Se otorgan licencias para la Seguridad Avanzada con base en "Confirmantes únicos". Un "Confirmador único" es un usuario con licencia de GitHub Enterprise, GitHub Enterprise Cloud, GitHub Enterprise Server, o GitHub AE, quien realizó una confirmación de código en los últimos 90 días para cualquier repositorio con cualquier funcionalidad de GitHub Advanced Security activada. Debes adquirir una licencia de usuario de GitHub Advanced Security para cada uno de tus Confirmadores Únicos. Solo puedes utilizar GitHub Advanced Security en las bases de código que desarrollas o que se desarrollan para ti. En el caso de los usuarios de GitHub Enterprise Cloud, algunas características de la Seguridad Avanzada también requieren utilizar las GitHub Actions. +Se otorgan licencias para la Seguridad Avanzada con base en "Confirmantes únicos". Un "Confirmador único" es un usuario con licencia de GitHub Enterprise, GitHub Enterprise Cloud, GitHub Enterprise Server, o GitHub AE, quien realizó una confirmación en los últimos 90 días para cualquier repositorio con cualquier funcionalidad de GitHub Advanced Security activada. Debes adquirir una licencia de usuario de GitHub Advanced Security para cada uno de tus Confirmadores Únicos. Solo puedes utilizar GitHub Advanced Security en las bases de código que desarrollas o que se desarrollan para ti. En el caso de los usuarios de GitHub Enterprise Cloud, algunas características de la Seguridad Avanzada también requieren utilizar las GitHub Actions. ## Base de datos consultiva La base de datos de asesorías de GitHub te permite buscar manualmente o por coincidencia las vulnerabilidades que afectan los proyectos de código abierto en GitHub. @@ -52,20 +52,20 @@ _Licencia para la base de datos consultiva de GitHub_ La base de datos consultiva de GitHub está bajo la licencia [Creative Commons Attribution 4.0](https://creativecommons.org/licenses/by/4.0/). La condición de la atribución se puede cumplir enlazando a la base de datos consultiva de GitHub en [https://github. om/advisories](https://github.com/advisories) o a registros individuales de la base de datos consultiva de GitHub usada, con la calificación de . ## Codespaces -_Note: The github.dev service, available by pressing `.` on a repo or navigating directly to github.dev, is governed by [GitHub's Beta Terms of service](/github/site-policy/github-terms-of-service#j-beta-previews)._ +_Nota: El servicio de github.dev, el cual se encuentra disponible al presionar `.` en un repositorio o navegando directamente a github.dev se rige mediante los [Términos de Servicio de GitHub Beta](/github/site-policy/github-terms-of-service#j-beta-previews)._ -GitHub Codespaces enables you to develop code directly from your browser using the code within your GitHub repository. Codespaces and any elements of the Codespaces service may not be used in violation of the Agreement or the Acceptable Use Policies. Additionally, Codespaces should not be used for: +Los Codespaces de GitHub te permiten desarrollar código directamente desde tu buscador utilizando el código dentro de tu repositorio de GitHub. Los Codespaces y cualquier elemento de este servicio no podrán utilizarse en violación del Acuerdo o de las Políticas de Uso Aceptable. Adicionalmente, los Codespaces no deben utilizarse para: - criptominería; -- using our servers to disrupt, or to gain or to attempt to gain unauthorized access to any service, device, data, account or network (other than those authorized by the GitHub Bug Bounty program); -- the provision of a stand-alone or integrated application or service offering Codespaces or any elements of Codespaces for commercial purposes; -- any activity that places a burden on our servers, where that burden is disproportionate to the benefits provided to users (for example, don't use Codespaces as a content delivery network, as part of a serverless application, or to host any kind of production-facing application); or -- any other activity unrelated to the development or testing of the software project associated with the repository where GitHub Codespaces is initiated. +- utilizar nuestros servidores para perturbar o ganar o intentar ganar acceso no autorizado a cualquier servicio, dispositivo, datos, cuenta o red (diferentes a aquellos que autoriza el Programa de Recompensas por Errores de GitHub); +- la provisión de una aplicación o servicio integrado o independiente que ofrezca Codespaces o cualquier elemento de estos para propósitos comerciales; +- cualquier actividad que coloque una carga en nuestros servidores, ya sea que esta sea desproporcional a los beneficios que se proporcionan a los usuarios (por ejemplo, no utilices los Codespaces como una red de entrega de contenido, como parte de una aplicación sin servidor, ni para hospedar algun tipo de aplicació de cara a producción); o +- cualquier otra actividad sin relación al desarrollo o pruebas del proyecto de software asociado con el repositorio en donde se inicia GitHub Codespaces. -In order to prevent violations of these limitations and abuse of GitHub Codespaces, GitHub may monitor your use of GitHub Codespaces. Misuse of GitHub Codespaces may result in termination of your access to Codespaces, restrictions in your ability to use GitHub Codespaces, or the disabling of repositories created to run Codespaces in a way that violates these Terms. +Para prevenir las violaciones de estas limitaciones y el abuso de GitHub Codespaces, GitHub podría monitorear tu uso de este servicio. El mal uso de GitHub Codespaces podría resultar en la terminación de tu acceso a este servicio, en restricciones en tu capacidad de utilizarlo o en inhabilitar los repositorios que se crean para ejecutar los Cdespaces en la forma en la que se violen estos Términos. -Codespaces allows you to load extensions from the Microsoft Visual Studio Marketplace (“Marketplace Extensions”) for use in your development environment, for example, to process the programming languages that your code is written in. Marketplace Extensions are licensed under their own separate terms of use as noted in the Visual Studio Marketplace, and the terms of use located at https://aka.ms/vsmarketplace-ToU. GitHub makes no warranties of any kind in relation to Marketplace Extensions and is not liable for actions of third-party authors of Marketplace Extensions that are granted access to Your Content. El uso que hagas de cualquier solicitud de terceros corre por tu cuenta y riesgo. +Los Codespaces te permiten cargar extensiones de Microsfot Visual Studio Marketplace ("Extensiones de Marketplace") para utilizar en tu ambiente de desarrollo, por ejemplo, para procesar los lenguajes de programación en los que está escrito tu código. Las extensiones de Marketplace se licencian bajo sus propios términos de uso de acuerdo como se describe en Visual Studio Marketplace y los términos de uso se ubican en https://aka.ms/vsmarketplace-ToU. GitHub no otorga garantías de ningún tipo en relación con las Extensiones de Marketplace y no es responsable por las acciones de autores terceros de estas, a quienes se les otorgue acceso a tu contenido. El uso que hagas de cualquier solicitud de terceros corre por tu cuenta y riesgo. -The generally available version of Codespaces is not currently available for U.S. government customers. Feriado en government customers may continue to use the Codespaces Beta Preview under separate terms. See [Beta Preview terms](/github/site-policy/github-terms-of-service#j-beta-previews). +La versión generalmente disponible de los Codespaces no está disponible actualmente para los clientes del gobierno de los EE.UU. Los clientes del gobierno de los EE.UU. pueden seguir utilizando la Vista Previa Beta de los Codespaces bajo términos independientes. Consulta los [Términos de la Vista Previa Beta](/github/site-policy/github-terms-of-service#j-beta-previews). ## Conexión Con GitHub Connect, puedes compartir algunas características y datos entre tu instancia de GitHub Enterprise Server {% ifversion ghae-next %}o de GitHub AE {% endif %} y tu cuenta empresarial u organizacional de GitHub Enterprise Cloud en GitHub.com. Para habilitar GitHub Connect, debes tener por lo menos una (1) cuenta en GitHub Enterprise Cloud o en GitHub.com y una (1) instancia con licencia de GitHub Enterprise Server{% ifversion ghae-next %} o de GitHub AE{% endif %}. Ti isp de GitHub Enterprise Cloud o de GitHub.com a través de Connect se rige por los términos bajo los cuales obtengas la licencia de GitHub Enterprise Cloud o GitHub.com. El uso de los datos personales se rige de acuerdo con la [Declaración de privacidad de GitHub](/github/site-policy/github-privacy-statement). @@ -111,7 +111,7 @@ Los usos prohiubidos de las Páginas de GitHub incluyen - el contenido sexualmente obsceno - el contenido que falsea de manera fraudulenta tu identidad o el propósito del sitio -If you have questions about whether your use or intended use falls into these categories, please contact [GitHub Support](https://support.github.com/contact?tags=docs-policy). GitHub se reserva el derecho en todo momento de reclamar cualquier subdominio de GitHub sin responsabilidad. +Su tuebes dudas sobre si tu uso o intención de uso cae en las siguientes categorías, por favor, contacta al [Soporte de GitHub](https://support.github.com/contact?tags=docs-policy). GitHub se reserva el derecho en todo momento de reclamar cualquier subdominio de GitHub sin responsabilidad. ## Programa de patrocinadores diff --git a/translations/es-ES/content/github/site-policy/index.md b/translations/es-ES/content/github/site-policy/index.md index 2ae42c7aa6..465afca13a 100644 --- a/translations/es-ES/content/github/site-policy/index.md +++ b/translations/es-ES/content/github/site-policy/index.md @@ -12,7 +12,7 @@ children: - /github-terms-of-service - /github-corporate-terms-of-service - /github-privacy-statement - - /github-data-protection-agreement-non-enterprise-customers + - /github-data-protection-agreement - /global-privacy-practices - /github-sponsors-additional-terms - /github-codespaces-privacy-statement diff --git a/translations/es-ES/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md b/translations/es-ES/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md index a2106aa4ff..8495ba7d07 100644 --- a/translations/es-ES/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md +++ b/translations/es-ES/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md @@ -1,6 +1,7 @@ --- title: Crear gists intro: 'Puedes crear dos tipos de gists: {% ifversion ghae %}internos{% else %}públicos{% endif %} y secretos. Crea un gist {% ifversion ghae %}interno{% else %}público{% endif %} si estás listo para compartir tus ideas con {% ifversion ghae %}los miembros de la emrpesa{% else %}el mundo{% endif %} o, de lo contrario, un gist secreto.' +permissions: '{% data reusables.enterprise-accounts.emu-permission-gist %}' redirect_from: - /articles/about-gists/ - /articles/cannot-delete-an-anonymous-gist/ @@ -19,7 +20,7 @@ Todo gist es un repositorio Git, lo que significa que se puede bifurcar y clonar Los gists pueden ser {% ifversion ghae %}internos{% else %}públicos{% endif %} o secretos. Los gists {% ifversion ghae %}internos{% else %}públicos{% endif %} se muestran en {% data variables.gists.discover_url %}, en donde {% ifversion ghae %}los miembros empresariales{% else %}las personas{% endif %} pueden buscar gists nuevos conforme estos se creen. También se los puede buscar, para que puedas usarlos si deseas que otras personas encuentren tu trabajo y lo vean. -Los gists secretos no se muestran en {% data variables.gists.discover_url %} y no se pueden buscar. Los gists no son privados. If you send the URL of a secret gist to {% ifversion ghae %}another enterprise member{% else %}a friend{% endif %}, they'll be able to see it. Sin embargo, si {% ifversion ghae %}cualquier otro miembro de la empresa{% else %}alguien que no conozcas{% endif %} descubre la URL, también podrán ver tu gist. Si deseas mantener tu código a salvo de las miradas curiosas, puedes optar por [crear un repositorio privado](/articles/creating-a-new-repository) en lugar de un gist. +Los gists secretos no se muestran en {% data variables.gists.discover_url %} y no se pueden buscar. Los gists no son privados. Si envías la URL de un gist secreto a {% ifversion ghae %}otro miembro de la empresa{% else %}un amigo {% endif %}, podrán verlo. Sin embargo, si {% ifversion ghae %}cualquier otro miembro de la empresa{% else %}alguien que no conozcas{% endif %} descubre la URL, también podrán ver tu gist. Si deseas mantener tu código a salvo de las miradas curiosas, puedes optar por [crear un repositorio privado](/articles/creating-a-new-repository) en lugar de un gist. {% data reusables.gist.cannot-convert-public-gists-to-secret %} @@ -42,7 +43,7 @@ Puedes fijar los gists a tu perfil para que otras personas los puedan ver fácil {% endif %} -Puedes descubrir gists {% ifversion ghae %}internos{% else %}públicos{% endif %} que hayan creado otras personas si vas a la {% data variables.gists.gist_homepage %} y das clic en **Todos los gists**. Esto te llevará a una página en la que aparecen todos los gists clasificados y presentados por fecha de creación o actualización. También puedes buscar los gists por idioma con {% data variables.gists.gist_search_url %}. La búsqueda de gists usa la misma sintaxis de búsqueda que la [búsqueda de código](/articles/searching-code). +Puedes descubrir gists {% ifversion ghae %}internos{% else %}públicos{% endif %} que hayan creado otras personas si vas a la {% data variables.gists.gist_homepage %} y das clic en **Todos los gists**. Esto te llevará a una página en la que aparecen todos los gists clasificados y presentados por fecha de creación o actualización. También puedes buscar los gists por idioma con {% data variables.gists.gist_search_url %}. La búsqueda de gists usa la misma sintaxis de búsqueda que la [búsqueda de código](/search-github/searching-on-github/searching-code). Dado que los gists son repositorios Git, puedes ver su historial de confirmaciones completo, que incluye todas las diferencias que existan. También puedes bifurcar o clonar gists. Para obtener más información, consulta "[Bifurcar y clonar gists"](/articles/forking-and-cloning-gists). @@ -50,7 +51,7 @@ Puedes descargar un archivo ZIP de un gist haciendo clic en el botón **Descarga {% ifversion fpt %} -Git admite la asignación de archivos GeoJSON. Estas asignaciones se muestran como gists insertos, para que las asignaciones se puedan compartir e insertar fácilmente. For more information, see "[Working with non-code files](/repositories/working-with-files/using-files/working-with-non-code-files#mapping-geojson-files-on-github)." +Git admite la asignación de archivos GeoJSON. Estas asignaciones se muestran como gists insertos, para que las asignaciones se puedan compartir e insertar fácilmente. Para obtener más información, consulta la sección "[Trabajar con archivos que no sean de código](/repositories/working-with-files/using-files/working-with-non-code-files#mapping-geojson-files-on-github)". {% endif %} diff --git a/translations/es-ES/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md b/translations/es-ES/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md index 60102555c4..a9e15b5af0 100644 --- a/translations/es-ES/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md +++ b/translations/es-ES/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md @@ -1,6 +1,7 @@ --- title: Bifurcar y clonar gists intro: 'Los gists son en realidad repositorios de Git, lo que significa que puedes bifurcar o clonar cualquier gist, aunque no seas el autor original. También puedes ver el historial completo de confirmaciones de un gist, incluidas las diferencias.' +permissions: '{% data reusables.enterprise-accounts.emu-permission-gist %}' redirect_from: - /articles/forking-and-cloning-gists - /github/writing-on-github/forking-and-cloning-gists diff --git a/translations/es-ES/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md b/translations/es-ES/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md index 5a352cf4d1..3bac375c2f 100644 --- a/translations/es-ES/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md +++ b/translations/es-ES/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md @@ -40,9 +40,9 @@ Puedes indicar énfasis con texto en negritas, itálicas o tachadas en los campo Puedes citar texto con un `>`. ```markdown -Tal como dice Abraham Lincoln: +Texto que no es una cita -> Con perdón de la expresión +> Texto que es una cita ``` ![Texto citado representado](/assets/images/help/writing/quoted-text-rendered.png) @@ -100,39 +100,39 @@ Puedes crear un enlace en línea al encerrar el texto del enlace entre corchetes {% data reusables.repositories.relative-links %} -## Images +## Imágenes -You can display an image by adding `!` and wrapping the alt text in`[ ]`. Then wrap the link for the image in parentheses `()`. +Puedes mostrar una imagen si agregas un `!` y pones el texto alternativo entre `[ ]`. Entonces encierra el enlace de la imagen entre paréntesis `()`. -`![This is an image](https://myoctocat.com/assets/images/base-octocat.svg)` +`![Esta es una imagen](https://myoctocat.com/assets/images/base-octocat.svg)` -![Rendered Image](/assets/images/help/writing/image-rendered.png) +![Imagen interpretada](/assets/images/help/writing/image-rendered.png) -{% data variables.product.product_name %} supports embedding images into your issues, pull requests{% ifversion fpt %}, discussions{% endif %}, comments and `.md` files. You can display an image from your repository, add a link to an online image, or upload an image. For more information, see "[Uploading assets](#uploading-assets)." +{% data variables.product.product_name %} es compatible con incrustar imágenes en tus propuestas, solicitudes de cambio{% ifversion fpt %}, debates{% endif %}, comentarios y archivos `.md`. Puedes mostrar una imagen desde tu repositorio, agregar un enlace a una imagen en línea o cargar una imagen. Para obtener más información, consulta la sección "[Cargar activos](#uploading-assets)". {% tip %} -**Tip:** When you want to display an image which is in your repository, you should use relative links instead of absolute links. +**Tip:** Cuando quieras mostrar una imagen que esté en tu repositorio, deberías utilizar enlaces relativos en vez de absolutos. {% endtip %} -Here are some examples for using relative links to display an image. +Aquí tienes algunos ejemplos para utilizar enlaces relativos para mostrar una imagen. -| Contexto | Relative Link | -| ----------------------------------------------------------- | ---------------------------------------------------------------------- | -| In a `.md` file on the same branch | `/assets/images/electrocat.png` | -| In a `.md` file on another branch | `/../main/assets/images/electrocat.png` | -| In issues, pull requests and comments of the repository | `../blob/main/assets/images/electrocat.png` | -| In a `.md` file in another repository | `/../../../../github/docs/blob/main/assets/images/electrocat.png` | -| In issues, pull requests and comments of another repository | `../../../github/docs/blob/main/assets/images/electrocat.png?raw=true` | +| Contexto | Enlace Relativo | +| ----------------------------------------------------------------------- | ---------------------------------------------------------------------- | +| En un archivo `.md` en la misma rama | `/assets/images/electrocat.png` | +| En un archivo `.md` en otra rama | `/../main/assets/images/electrocat.png` | +| En propuestas, solicitudes de cambio y comentarios del repositorio | `../blob/main/assets/images/electrocat.png` | +| En un archivo `.md` en otro repositorio | `/../../../../github/docs/blob/main/assets/images/electrocat.png` | +| En propuestas, solicitudes de cambios y comentarios de otro repositorio | `../../../github/docs/blob/main/assets/images/electrocat.png?raw=true` | {% note %} -**Note**: The last two relative links in the table above will work for images in a private repository only if the viewer has at least read access to the private repository which contains these images. +**Nota**: Los últimos dos enlaces relativos en la tabla anterior funcionarán únicamente para las imágenes en repositorios privados solo si el lector tiene por lo menos acceso de lectura a este. {% endnote %} -For more information, see "[Relative Links](#relative-links)." +Para obtener más información, consulta la sección "[Enlaces relativos](#relative-links)". ## Listas @@ -184,7 +184,7 @@ En este ejemplo, puedes agregar un elemento de la lista anidada debajo del eleme ![Lista con un elemento de lista anidado](/assets/images/help/writing/nested-list-example-3.png) -Puedes crear múltiples niveles de listas anidadas mediante el mismo método. Por ejemplo, dado que el primer elemento de la lista tiene siete espacios (`␣␣␣␣␣-␣`) antes del contenido de la lista anidada `Primer elemento de la lista anidada`, deberías colocar sangría en el primer elemento de la lista anidada por siete espacios. +Puedes crear múltiples niveles de listas anidadas mediante el mismo método. For example, because the first nested list item has seven characters (`␣␣␣␣␣-␣`) before the nested list content `First nested list item`, you would need to indent the second nested list item by seven spaces. ```markdown 100. Primer elemento de la lista @@ -232,7 +232,7 @@ Para obtener más información, consulta "[Referencias y direcciones URL autovin ## Adjuntos de contenido -Some {% data variables.product.prodname_github_apps %} provide information in {% data variables.product.product_name %} for URLs that link to their registered domains. {% data variables.product.product_name %} presenta la información suministrada por la app debajo de la URL en el cuerpo o comentario de una propuesta o solicitud de extracción. +Algunas {% data variables.product.prodname_github_apps %} proporcionan información en {% data variables.product.product_name %} para las URL que enlazan a sus dominios registrados. {% data variables.product.product_name %} presenta la información suministrada por la app debajo de la URL en el cuerpo o comentario de una propuesta o solicitud de extracción. ![Adjunto de contenido](/assets/images/github-apps/content_reference_attachment.png) @@ -262,6 +262,30 @@ 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-next or ghes > 3.3 %} +## Notas al pie + +Puedes agregar notas al pie para tu contenido si utilizas esta sintaxis de corchetes: + +``` +Esta es una nota al pie sencilla[^1]. + +[^1]: Mi referencia. +``` + +La nota al pie se verá así: + +![Nota al pie interpretada](/assets/images/site/rendered-footnote.png) +{% endif %} + +## Ocultar el contenido con comentarios + +Puedes decirle a {% data variables.product.product_name %} que oculte el contenido del lenguaje de marcado interpretado colocando el contenido en un comentario de HTML. + +
    +<!-- This content will not appear in the rendered Markdown -->
+
    + ## Importar formato de Markdown Puedes pedirle a {% data variables.product.product_name %} que ignore (o evada) el formato de Markdown usando `\` antes del carácter de Markdown. @@ -272,13 +296,13 @@ Puedes pedirle a {% data variables.product.product_name %} que ignore (o evada) Para obtener más información, consulta "[Sintaxis de Markdown" de Daring Fireball](https://daringfireball.net/projects/markdown/syntax#backslash), -## Hiding content with comments +{% ifversion fpt or ghes > 3.2 or ghae-issue-5232 %} -You can tell {% data variables.product.product_name %} to hide content from the rendered Markdown by placing the content in an HTML comment. +## Inhabilitar la representación del lenguaje de marcado -
    -<!-- This content will not appear in the rendered Markdown -->
-
    +{% data reusables.repositories.disabling-markdown-rendering %} + +{% endif %} ## Leer más diff --git a/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md b/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md index 58e7b3d448..6759894bd9 100644 --- a/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md +++ b/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md @@ -31,9 +31,10 @@ Para adjuntar un archivo a una propuesta o una conversación de una solicitud de {% endtip %} El tamaño máximo de archivo es: -- 10MB para imágenes y gifs{% ifversion fpt or ghes > 3.1 or ghae-next %} +- 10MB de imágenes y gifs{% ifversion fpt %} - 10MB para videos que se suban a un repositorio que pertenezca a un usuario u organización en un plan gratuito de GitHub -- 100MB para videos que se suban a los repositorios que pertenezcan a un usuario u organización de un plan de pago de GitHub{% endif %} +- 100MB para videos que se suban a los repositorios que pertenezcan a un usuario u organización de un plan de pago de GitHub{% elsif fpt or ghes > 3.1 or ghae-next %} +- 100MB para videos{% endif %} - 25MB para el resto de los archivos Archivos compatibles: diff --git a/translations/es-ES/content/github/writing-on-github/working-with-saved-replies/creating-a-saved-reply.md b/translations/es-ES/content/github/writing-on-github/working-with-saved-replies/creating-a-saved-reply.md index 7e9769fb4f..1db5eddbc0 100644 --- a/translations/es-ES/content/github/writing-on-github/working-with-saved-replies/creating-a-saved-reply.md +++ b/translations/es-ES/content/github/writing-on-github/working-with-saved-replies/creating-a-saved-reply.md @@ -15,7 +15,7 @@ versions: 3. En "Agregar una respuesta guardada", agrega el título de tu respuesta guardada. ![Título de la respuesta guardada](/assets/images/help/settings/saved-replies-title.png) 4. En el campo "Escribir", agrega el contenido que deseas usar para la respuesta guardada. Para obtener más información acerca de la escritura en {% data variables.product.product_name %}, consulta "[Sintaxis de escritura y formato básicos](/articles/basic-writing-and-formatting-syntax)". ![Escribir una respuesta guardada](/assets/images/help/settings/saved-replies-settings-adding.png) 5. Para revisar tu respuesta, haz clic en **Vista previa**. ![Agregar una respuesta guardada](/assets/images/help/settings/saved-replies-preview.png) -6. Haz clic en **Agregar respuesta guardada**. !["Add saved reply" button](/assets/images/help/settings/saved-replies-add-button.png) +6. Haz clic en **Agregar respuesta guardada**. ![Botón de "agregar respuesta guardada"](/assets/images/help/settings/saved-replies-add-button.png) ## Leer más diff --git a/translations/es-ES/content/graphql/guides/managing-enterprise-accounts.md b/translations/es-ES/content/graphql/guides/managing-enterprise-accounts.md index 18445e516a..646feec842 100644 --- a/translations/es-ES/content/graphql/guides/managing-enterprise-accounts.md +++ b/translations/es-ES/content/graphql/guides/managing-enterprise-accounts.md @@ -58,8 +58,9 @@ Para encontrar algunas consultas de ejemplo, visita la sección "[Una consulta d - `admin:enterprise` Los alcances específicos para la cuenta empresarial son: - - `admin:enterprise`: otorga control total de las empresas (incluye`manage_billing:enterprise` y `read:enterprise`) - - `manage_billing:enterprise`: Lee y escribe datos de facturación de la empresa. + - `admin:enterprise`: Proporciona control total de las empresas (incluye a {% ifversion ghes > 3.2 or fpt or ghae %}`manage_runners:enterprise`, {% endif %}`manage_billing:enterprise` y `read:enterprise`) + - `manage_billing:enterprise`: Lee y escribe datos de facturación empresarial.{% ifversion ghes > 3.2 or fpt or ghae %} + - `manage_runners:enterprise`: Acceso para administrar los ejecutores y grupos de ejecutores empresariales de GitHub Actions.{% endif %} - `read:enterprise`: Lee datos del perfil empresarial. 4. Copia tu token de acceso personal y mantenlo en un lugar seguro hasta que lo agregues a tu cliente de GraphQL. diff --git a/translations/es-ES/content/graphql/guides/using-the-graphql-api-for-discussions.md b/translations/es-ES/content/graphql/guides/using-the-graphql-api-for-discussions.md index 1b459533c4..89a12caa82 100644 --- a/translations/es-ES/content/graphql/guides/using-the-graphql-api-for-discussions.md +++ b/translations/es-ES/content/graphql/guides/using-the-graphql-api-for-discussions.md @@ -1,6 +1,6 @@ --- title: Utilizar la API de GraphQL para los debates -intro: 'Learn how to use the {% data variables.product.prodname_discussions %} GraphQL API.' +intro: 'Aprende a utilizar la API de GraphQL de los {% data variables.product.prodname_discussions %}.' versions: fpt: '*' shortTitle: Utilizar GraphQL para los debates @@ -1080,4 +1080,4 @@ Campos de tipo de retorno: ## Buscar -El debate puede devolverse desde el campo `search` de nivel superio. Para buscar un debate, especifica el `type` como `DISCUSSION`. El tipo `SearchResultItemConnection` tiene un campo de `discussionCount` para reportar la cantidad de debates devueltos y el tipo `Discussion` se agrega a la unión `SearchResultItem`. Para obtener más información, consulta las secciones "[Consultas](/graphql/reference/queries#searchresultitemconnection)" y "[Buscar debates](/github/searching-for-information-on-github/searching-discussions)". +El debate puede devolverse desde el campo `search` de nivel superio. Para buscar un debate, especifica el `type` como `DISCUSSION`. El tipo `SearchResultItemConnection` tiene un campo de `discussionCount` para reportar la cantidad de debates devueltos y el tipo `Discussion` se agrega a la unión `SearchResultItem`. Para obtener más información, consulta las secciones "[Consultas](/graphql/reference/queries#searchresultitemconnection)" y "[Buscar debates](/search-github/searching-on-github/searching-discussions)". diff --git a/translations/es-ES/content/index.md b/translations/es-ES/content/index.md index b95036e7e5..8517fc1eef 100644 --- a/translations/es-ES/content/index.md +++ b/translations/es-ES/content/index.md @@ -1,5 +1,5 @@ --- -title: '{% data variables.product.product_name %}{% if currentVersion == "free-pro-team@latest" %}.com{% endif %} Documentación de Ayuda' +title: '{% data variables.product.product_name %}{% ifversion fpt %}.com{% endif %} Documentación de Ayuda' featuredLinks: gettingStarted: - /github/getting-started-with-github/set-up-git @@ -27,6 +27,7 @@ children: - actions - codespaces - packages + - search-github - developers - rest - graphql 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 ed9ab4c67f..bf5406ea41 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 @@ -48,7 +48,7 @@ Puedes @mencionar colaboradores que tengan acceso a tu repositorio en una propue ## Comparar propuestas y debates -Some conversations are more suitable for {% data variables.product.prodname_discussions %}. {% data reusables.discussions.you-can-use-discussions %} Para orientarte sobre cuándo utilizar una propuesta o debate, consulta la sección "[Comuinicarte en GitHub](/github/getting-started-with-github/quickstart/communicating-on-github)". +Algunas conversaciones son más adecuadas para los {% data variables.product.prodname_discussions %}. {% data reusables.discussions.you-can-use-discussions %} Para orientarte sobre cuándo utilizar una propuesta o debate, consulta la sección "[Comuinicarte en GitHub](/github/getting-started-with-github/quickstart/communicating-on-github)". Cuando una conversación en una propuesta se adecua mejor para un debate, puedes intentar convertir la propuesta en debate. {% endif %} 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 de975b59ed..0edf0b0395 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 @@ -1,6 +1,7 @@ --- title: Asignar propuestas y solicitudes de extracción a otros usuarios de GitHub intro: Los asignatarios aclaran quién está trabajando en propuestas y solicitudes de extracción específicas. +permissions: 'Anyone with write access to a repository can assign issues and pull requests. {% data reusables.enterprise-accounts.emu-permission-repo %}' redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/assigning-issues-and-pull-requests-to-other-github-users - /articles/assigning-issues-and-pull-requests-to-other-github-users @@ -15,8 +16,6 @@ topics: shortTitle: Asignar propuestas & solicitudes de cambio --- -Cualquier persona con permisos de escritura en un repositorio puede asignar propuestas y solicitudes de extracción. - ## 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)". diff --git a/translations/es-ES/content/issues/tracking-your-work-with-issues/creating-an-issue.md b/translations/es-ES/content/issues/tracking-your-work-with-issues/creating-an-issue.md index fa76eed355..0a5d040235 100644 --- a/translations/es-ES/content/issues/tracking-your-work-with-issues/creating-an-issue.md +++ b/translations/es-ES/content/issues/tracking-your-work-with-issues/creating-an-issue.md @@ -1,7 +1,7 @@ --- title: Crear una propuesta intro: 'Las propuestas pueden crearse de varias formas, así que puedes elegir el método más conveniente para tu flujo de trabajo.' -permissions: People with read permissions can create an issue in a repository where issues are enabled. +permissions: 'People with read access can create an issue in a repository where issues are enabled. {% data reusables.enterprise-accounts.emu-permission-repo %}' redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/creating-an-issue - /articles/creating-an-issue @@ -43,20 +43,20 @@ Las propuestas se pueden usar para hacer un seguimiento de los errores, mejoras {% data reusables.repositories.assign-an-issue-as-project-maintainer %} {% data reusables.repositories.submit-new-issue %} -## Creating an issue with {% data variables.product.prodname_cli %} +## Crear una propuesta con {% data variables.product.prodname_cli %} -{% data reusables.cli.about-cli %} To learn more about {% data variables.product.prodname_cli %}, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)." +{% data reusables.cli.about-cli %} Para aprender más sobre el {% data variables.product.prodname_cli %}, consulta la sección "[Acerca del {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)". -To create an issue, use the `gh issue create` subcommand. To skip the interactive prompts, include the `--body` and the `--title` flags. +Para crear una propuesta, utiliza el subcomando `gh issue create`. Para omitir los mensajes interactivos, incluye los marcadores `--body` y `--title`. ```shell -gh issue create --title "My new issue" --body "Here are more details." +gh issue create --title "My new issue" --body "Here are more details". ``` -You can also specify assignees, labels, milestones, and projects. +También puedes especificar asignados, etiquetas, hitos y proyectos. ```shell -gh issue create --title "My new issue" --body "Here are more details." --assignee @me,monalisa --label "bug,help wanted" --project onboarding --milestone "learning codebase" +gh issue create --title "My new issue" --body "Here are more details". --assignee @me,monalisa --label "bug,help wanted" --project onboarding --milestone "learning codebase" ``` ## Crear una propuesta desde un comentario @@ -90,15 +90,15 @@ Puedes abrir una nueva propuesta desde una línea específica o líneas de códi {% ifversion fpt %} -## Creating an issue from discussion +## Crear una propuesta a partir de un debate -People with triage permission to a repository can create an issue from a discussion. +Las personas con permiso de clasificación en un repositorio pueden crear una propuesta a partir de un debate. -When you create an issue from a discussion, the contents of the discussion post will be automatically included in the issue body, and any labels will be retained. Creating an issue from a discussion does not convert the discussion to an issue or delete the existing discussion. For more information about {% data variables.product.prodname_discussions %}, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." +Cuando creas una propuesta a partir de un debate, el contenido de la publicación del debate se incluirá automáticamente en el cuerpo de la propuesta y cualquier etiqueta se retendrá. El crear una propuesta a partir de un debate no convertirá el debate en una propuesta ni borrará el debate existente. Para obtener más información sobre los {% data variables.product.prodname_discussions %}, consulta la sección "[Acerca de los debates](/discussions/collaborating-with-your-community-using-discussions/about-discussions)". {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %} -1. In the right sidebar, click {% octicon "issue-opened" aria-label="The issues icon" %} **Create issue from discussion**. ![Button to create issue from discussion](/assets/images/help/discussions/create-issue-from-discussion.jpg) +1. En la barra lateral derecha, haz clic en {% octicon "issue-opened" aria-label="The issues icon" %} **Crear propuesta a partir de un debate**. ![Botón para crear una propuesta a partir de un debate](/assets/images/help/discussions/create-issue-from-discussion.jpg) {% data reusables.repositories.type-issue-title-and-description %} {% data reusables.repositories.assign-an-issue-as-project-maintainer %} {% data reusables.repositories.submit-new-issue %} 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 0b2574ad13..e3dd25b29d 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 @@ -1,6 +1,6 @@ --- -title: Filtering and searching issues and pull requests -intro: 'To find detailed information about a repository on {% data variables.product.product_name %}, you can filter, sort, and search issues and pull requests that are relevant to the repository.' +title: Filtrar y buscar propuestas y solicitudes de cambios +intro: 'Para encontrar información detallada sobre un repositorio en {% data variables.product.product_name %}, puedes filtrar, clasificar y buscar propuestas y solicitudes de cambios que sean relevantes para el repositorio.' redirect_from: - /github/managing-your-work-on-github/finding-information-in-a-repository/filtering-issues-and-pull-requests-by-assignees - /articles/filtering-issues-and-pull-requests-by-assignees @@ -40,7 +40,7 @@ versions: topics: - Issues - Pull requests -shortTitle: Filter and search +shortTitle: Filtrar y buscar --- {% data reusables.cli.filter-issues-and-pull-requests-tip %} @@ -65,7 +65,7 @@ Puedes filtrar propuestas y solicitudes de extracción para buscar: ## Filtrar propuestas y solicitudes de extracción por asignatarios -Once you've [assigned an issue or pull request to someone](/articles/assigning-issues-and-pull-requests-to-other-github-users), you can find items based on who's working on them. +Una vez que hayas [asignado una propuesta o solicitud de cambios a alguien](/articles/assigning-issues-and-pull-requests-to-other-github-users), puedes encontrar los elementos con base en quién está trabajando en ellos. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} @@ -80,7 +80,7 @@ Para borrar tu selección de filtro, haz clic en **Borrar consultas de búsqueda ## Filtrar propuestas y solicitudes de extracción por etiquetas -Once you've [applied labels to an issue or pull request](/articles/applying-labels-to-issues-and-pull-requests), you can find items based on their labels. +Una vez que hayas [aplicado etiquetas a una propuesta o solicitud de cambios](/articles/applying-labels-to-issues-and-pull-requests), puedes encontrar los elementos con base en sus etiquetas. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} @@ -102,7 +102,8 @@ Puedes filtrar la lista de solicitudes de extracción de un repositorio para bus - Solicitudes de extracción que [requieren una revisión](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging) antes de que puedan fusionarse - Solicitudes de extracción que ha aprobado un revisor - Solicitudes de extracción en las que un revisor ha pedido cambios -- Solicitudes de extracción que tú has revisado +- Solicitudes de cambios que revisaste{% ifversion fpt or ghae or ghes > 3.2 %} +- Solicitudes de cambios que alguien te pidió que revisaras directamente{% endif %} - Solicitudes de extracción que [alguien te ha pedido a ti que revises o a un equipo del que eres miembro](/articles/requesting-a-pull-request-review) {% data reusables.repositories.navigate-to-repo %} @@ -112,9 +113,9 @@ Puedes filtrar la lista de solicitudes de extracción de un repositorio para bus ## Utilizar búsqueda para filtrar propuestas y solicitudes de extracción -You can use advanced filters to search for issues and pull requests that meet specific criteria. +Puedes utilizar filtros avanzados para buscar propuestas y solicitudes de cambio que cumplan criterios específicos. -### Searching for issues and pull requests +### Buscar propuestas y solicitudes de cambio {% include tool-switcher %} @@ -136,15 +137,15 @@ La barra de búsqueda de propuestas y solicitudes de extracción te permite defi {% data reusables.cli.cli-learn-more %} -You can use the {% data variables.product.prodname_cli %} to search for issues or pull requests. Use the `gh issue list` or `gh pr list` subcommand along with the `--search` argument and a search query. +Puedes utilizar el {% data variables.product.prodname_cli %} para buscar propuestas o solicitudes de cambio. Utiliza el subcomando `gh issue list` o `gh pr list` junto con el argumento `--search` y consulta de búsqueda. -For example, you can list, in order of date created, all issues that have no assignee and that have the label `help wanted` or `bug`. +Por ejemplo, puedes listar, en orden de fecha en la que se creó, todas las propuestas que no tengan asignado a alguien y que tengan la etiqueta `help wanted` o `bug`. ```shell gh issue list --search 'no:assignee label:"help wanted",bug sort:created-asc' ``` -You can also list all pull requests that mention the `octo-org/octo-team` team. +También puedes listar todas las solicitudes de cambio que mencionen al equipo `octo-org/octo-team`. ```shell gh pr list --search "team:octo-org/octo-team" @@ -152,7 +153,7 @@ gh pr list --search "team:octo-org/octo-team" {% endcli %} -### About search terms +### Acerca de los términos de búsqueda Con los términos de búsqueda de propuestas y solicitudes de extracción, puedes hacer lo siguiente: @@ -165,9 +166,9 @@ Con los términos de búsqueda de propuestas y solicitudes de extracción, puede {% ifversion fpt or ghes > 3.2 or ghae-next %} {% tip %} -**Tip:** You can filter issues and pull requests by label using logical OR or using logical AND. -- To filter issues using logical OR, use the comma syntax: `label:"bug","wip"`. -- To filter issues using logical AND, use separate label filters: `label:"bug" label:"wip"`. +**Tip:** Puedes filtrar propuestas y solicitudes de cambio por etiqueta utilizando el componente lógico OR o el AND. +- Para filtrar propuestas utilizando el componente lógico OR, utiliza la sintaxis con coma: `label:"bug","wip"`. +- Para filtrar propuestas utilizando el componente lógico AND, utiliza filtros de etiqueta separados: `label:"bug" label:"wip"`. {% endtip %} {% endif %} @@ -185,7 +186,8 @@ Para las solicitudes de cambios, también puedes utilizar la búsqueda para: - Filtrar solicitudes de extracción que haya aprobado un revisor: `state:open type:pr review:approved` - Filtrar solicitudes de extracción en las que un revisor haya solicitado cambios: `state:open type:pr review:changes_requested` - Filtrar solicitudes de extracción por [revisor](/articles/about-pull-request-reviews/): `state:open type:pr reviewed-by:octocat` -- Filtrar solicitudes de extracción por el usuario específico [que solicitó la revisión](/articles/requesting-a-pull-request-review): `state:open type:pr review-requested:octocat` +- Filtrar solicitudes de cambios por usuario específico [al que se le solicitó la revisión](/articles/requesting-a-pull-request-review): `state:open type:pr review-requested:octocat`{% ifversion fpt or ghae or ghes > 3.2 %} +- Filtrar solicitudes de cambio que alguien te pidió revisar directamente: `state:open type:pr user-review-requested:@me`{% endif %} - Filtrar solicitudes de extracción por el equipo que se solicita para revisión: `state:open type:pr team-review-requested:github/atom`{% ifversion fpt or ghes or ghae %} - Filtrar por las solicitudes de extracción enlazadas con un informe de problemas que se pudiera cerrar con dicha solicitud: `linked:issue`{% endif %} @@ -224,4 +226,4 @@ Por ejemplo, si filtras propuestas asignadas a Hubot, y clasificas las propuesta ## Leer más -- "[Searching issues and pull requests](/articles/searching-issues)"" +- "[Buscar propuestas y solicitudes de cambio](/articles/searching-issues)"" diff --git a/translations/es-ES/content/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository.md b/translations/es-ES/content/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository.md index a641ff3d95..23c13c0237 100644 --- a/translations/es-ES/content/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository.md +++ b/translations/es-ES/content/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository.md @@ -1,6 +1,7 @@ --- title: Anclar una propuesta a tu repositorio intro: Puedes anclar hasta tres propuestas importantes encima de las propuestas enumeradas en tu repositorio. +permissions: 'People with write access to a repository can pin issue in the repository. {% data reusables.enterprise-accounts.emu-permission-repo %}' redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/pinning-an-issue-to-your-repository - /articles/pinning-an-issue-to-your-repository @@ -17,8 +18,6 @@ shortTitle: Fija una propuesta ![Propuestas ancladas](/assets/images/help/issues/pinned-issues.png) -Para anclar una propuesta, debes tener permisos de escritura para el repositorio dentro del cual se encuentra la propuesta. - {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issues %} 1. En la lista de propuestas, haz clic en la propuesta que deseas anclar. diff --git a/translations/es-ES/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md b/translations/es-ES/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md index 0a2a08206c..8adb0f17cc 100644 --- a/translations/es-ES/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md +++ b/translations/es-ES/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md @@ -80,7 +80,7 @@ Puedes crear etiquetas para que un repositorio categorice las propuestas, solici Para obtener más información, consulta "[Crear una etiqueta](/issues/using-labels-and-milestones-to-track-work/managing-labels#creating-a-label)". -Una vez que hayas creado una etiqueta en un repositorio, puedes aplicarla a cualquier propuesta, solicitud de cambos o debate en este. Puedes entonces filtrar las propuestas y solicitudes de cambio por etiqueta para encontrar todo el trabajo asociado. Por ejemplo, encuentra los errores de cara al usuario en tu proyecto filtrando las propuestas con las etiquetas `front-end` y `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)." +Una vez que hayas creado una etiqueta en un repositorio, puedes aplicarla a cualquier propuesta, solicitud de cambos o debate en este. Puedes entonces filtrar las propuestas y solicitudes de cambio por etiqueta para encontrar todo el trabajo asociado. Por ejemplo, encuentra los errores de cara al usuario en tu proyecto filtrando las propuestas con las etiquetas `front-end` y `bug`. Para obtener más información, consulta la sección "[Filtrar y buscar las propuestas y solicitudes de cambio](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)". ### Ejemplo de etiqueta A continuación se encuentra un ejemplo de una etiqueta de `front-end` que creamos y agregamos a la propuesta. diff --git a/translations/es-ES/content/issues/tracking-your-work-with-issues/quickstart.md b/translations/es-ES/content/issues/tracking-your-work-with-issues/quickstart.md index f886d41084..37f1d1d387 100644 --- a/translations/es-ES/content/issues/tracking-your-work-with-issues/quickstart.md +++ b/translations/es-ES/content/issues/tracking-your-work-with-issues/quickstart.md @@ -19,7 +19,7 @@ Esta guía te muestra cómo utilizar las {% data variables.product.prodname_gith ## Prerrequisitos -Para crear una propuesta, necesitas un repositorio. Puedes utilizar un repositorio existente al cual tengas acceso de escritura o puedes crear un repositorio nuevo. El repositorio debe tener habilitadas las propuestas. Para obtener más información sobre la creación de repositorios, consulta "[Crear un repositorio nuevo](/articles/creating-a-new-repository)." Para obtener más información acerca de habilitar las propuestas si están inhabilitadas en tu repositorio, consulta la sección "[Inhabilitar las propuestas](/github/administering-a-repository/managing-repository-settings/disabling-issues)". +Para crear una propuesta, necesitas un repositorio. Puedes utilizar un repositorio existente al cual tengas acceso de escritura o puedes crear un repositorio nuevo. {% data reusables.enterprise-accounts.emu-permission-repo %} El repositorio debe tener habilitadas las propuestas. Para obtener más información sobre la creación de repositorios, consulta "[Crear un repositorio nuevo](/articles/creating-a-new-repository)." Para obtener más información acerca de habilitar las propuestas si están inhabilitadas en tu repositorio, consulta la sección "[Inhabilitar las propuestas](/github/administering-a-repository/managing-repository-settings/disabling-issues)". ## Abrir una propuesta en blanco diff --git a/translations/es-ES/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md b/translations/es-ES/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md index 5fb24bd2d7..5169733214 100644 --- a/translations/es-ES/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md +++ b/translations/es-ES/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md @@ -42,7 +42,7 @@ Las personas o equipos que se mencionan en la propuesta recibirán una notificac {% data reusables.cli.cli-learn-more %} -To transfer an issue, use the `gh issue transfer` subcommand. Replace the `issue` parameter with the number or URL of the issue. Replace the `{% ifversion ghes %}hostname/{% endif %}owner/repo` parameter with the {% ifversion ghes %}URL{% else %}name{% endif %} of the repository that you want to transfer the issue to, such as `{% ifversion ghes %}https://ghe.io/{% endif %}octocat/octo-repo`. +Para transferir una propuesta, utiliza el subcomando `gh issue transfer`. Reemplaza el parámetro `issue` con el número o URL de la propuesta. Reemplaza el parámetro `{% ifversion ghes %}hostname/{% endif %}owner/repo` con {% ifversion ghes %}la URL{% else %}el nombre{% endif %} del repositorio al que quieras transferir la propuesta, tal como `{% ifversion ghes %}https://ghe.io/{% endif %}octocat/octo-repo`. ```shell gh issue transfer issue {% ifversion ghes %}hostname/{% endif %}owner/repo diff --git a/translations/es-ES/content/issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects.md b/translations/es-ES/content/issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects.md index 653a4662d2..17ebdec841 100644 --- a/translations/es-ES/content/issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects.md +++ b/translations/es-ES/content/issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects.md @@ -33,7 +33,7 @@ Utiliza las vistas de proyecto para mirarlo desde diferentes ángulos. Por ejemplo: - Filtra por estado para ver los elementos que no se marcaron como favoritos -- Group by a custom priority field to monitor the volume of high priority items +- Agrupar por un campo de prioridad personalizado para monitorear el volumen de los elementos de prioridad alta - Ordena por un campo personalizado de fecha para ver los elementos con la fecha de envío destino más cercana Para obtener más información, consulta la sección "[Personalizar las vistas de tu proyecto](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)". diff --git a/translations/es-ES/content/issues/trying-out-the-new-projects-experience/customizing-your-project-views.md b/translations/es-ES/content/issues/trying-out-the-new-projects-experience/customizing-your-project-views.md index 2a512bad3f..8709996240 100644 --- a/translations/es-ES/content/issues/trying-out-the-new-projects-experience/customizing-your-project-views.md +++ b/translations/es-ES/content/issues/trying-out-the-new-projects-experience/customizing-your-project-views.md @@ -75,11 +75,11 @@ Sigue pasos similares para eliminar una clasificación. ## Grupo -In the table layout, you can group items by a custom field value. Cuando los elementos se agrupan, si arrastras un elemento a un grupo nuevo, se aplica el valor de este grupo. Por ejemplo, si agrupas por `Status` y luego arrastras un elemento con un estado a `In progress` hacia el grupo `Done`, el estado del elemento cambiará a `Done`. +En el diseño de tabla, puedes agrupar elementos por un valor de campo personalizado. Cuando los elementos se agrupan, si arrastras un elemento a un grupo nuevo, se aplica el valor de este grupo. Por ejemplo, si agrupas por `Status` y luego arrastras un elemento con un estado a `In progress` hacia el grupo `Done`, el estado del elemento cambiará a `Done`. {% note %} -**Note:** Currently, you cannot group by title, assignees, repository or labels. +**Nota:** Actualmente, no puedes agrupar por título, asignados, repositorio o etiquetas. {% endnote %} @@ -102,17 +102,17 @@ En el diseño de tabla, puedes filtrar por valores de campo. 1. {% data reusables.projects.open-command-palette %} 2. Comienza a teclear "Filter by" o el nombre del campo por el cual quieres filtrar. 3. Selecciona el comando deseado (por ejemplo "filter by Status"). -4. Ingresa el valor por el cual quieras filtrar (por ejemplo: "In progress"). You can also filter for the absence of specific values (for example: "Exclude status") or the absence of all values (for example: "No status"). +4. Ingresa el valor por el cual quieras filtrar (por ejemplo: "In progress"). También puedes filtrar por la ausencia de valores específicos (por ejemplo;: "Exclude status") o por la ausencia de todos los valores (por ejemplo: "No status"). 5. Como alternativa, haz clic en {% octicon "search" aria-label="the search icon" %} en la parte superior de la tabla para mostrar la barra de "Filtrar por palabra clave o campo". Ingresa el nombre de campo y el valor por el cual quieras filtrar. Conforme teclees, se mostrarán los posibles valores. - To filter for multiple values, separate the values with a comma. For example `label:"good first issue",bug` will list all issues with a label `good first issue` or `bug`. + Para filtrar valores múltiples, sepáralos con una coma. Por ejemplo `label:"good first issue",bug` listará las propuestas con una etiqueta de `good first issue` o de `bug`. - To filter for the absence of a specific value, place `-` before your filter. For example, `-label:"bug"` will only show items that do not have the label `bug`. + Para filtrar la ausencia de un valor específico, coloca `-` antes de tu filtro. Por ejemplo, `-label:"bug"` mostrará solo elementos que no tengan la etiqueta `bug`. - To filter for the absence of all values, enter `no:` followed by the field name. For example, `no:assignee` will only show items that do not have an assignee. + Para filtrar de acuerdo a la ausencia de todos los valores, ingresa `no:` seguido del nombre del campo. Por ejemplo, `no:assignee` solo mostrará los elementos que no tengan un asignado. - Separa los filtros múltiples con un espacio. For example, `status:"In progress" -label:"bug" no:assignee` will show only items that have a status of `In progress`, do not have the label `bug`, and do not have an assignee. -6. Alternatively, select the drop-down menu next to the view name and click the menu item that indicates the desired filter. + Separa los filtros múltiples con un espacio. Por ejemplo, `status:"In progress" -label:"bug" no:assignee` solo mostrará los elementos que tengan un estado de `In progress`, que no tengan la etiqueta `bug` y que no tengan un asignado. +6. Como alternativa, selecciona el menú desplegable junto al nombre de la vista y haz clic en el elemento de menú que indique el filtro deseado. ## Guardar vistas diff --git a/translations/es-ES/content/issues/using-labels-and-milestones-to-track-work/filtering-issues-and-pull-requests-by-milestone.md b/translations/es-ES/content/issues/using-labels-and-milestones-to-track-work/filtering-issues-and-pull-requests-by-milestone.md index dd5c34c2f8..08675a4011 100644 --- a/translations/es-ES/content/issues/using-labels-and-milestones-to-track-work/filtering-issues-and-pull-requests-by-milestone.md +++ b/translations/es-ES/content/issues/using-labels-and-milestones-to-track-work/filtering-issues-and-pull-requests-by-milestone.md @@ -31,5 +31,5 @@ shortTitle: Filtrar por hito ## Leer más -- "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)" +- "[Filtrar y buscar propuestas y solicitudes de cambios](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)" - "[Filtrar tarjetas en un tablero de proyecto](/articles/filtering-cards-on-a-project-board)" diff --git a/translations/es-ES/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md b/translations/es-ES/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md index c88f8aa0f8..ac470bca14 100644 --- a/translations/es-ES/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md +++ b/translations/es-ES/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md @@ -1,6 +1,7 @@ --- title: Administrar las etiquetas intro: 'Puedes clasificar {% ifversion fpt %}propuestas, solicitudes de cambio y debates{% else %}propuestas y solicitudes de cambio{% endif %} si creas, editas, aplicas y borras las etiquetas.' +permissions: '{% data reusables.enterprise-accounts.emu-permission-repo %}' redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/managing-labels - /articles/managing-Labels @@ -30,8 +31,6 @@ topics: Puedes administrar tu trabajo en {% data variables.product.product_name %} si creas etiquetas para categorizar {% ifversion fpt %}propuestas, solicitudes de cambio, y debates{% else %}propuestas y solicitudes de cambio{% endif %}. Puedes aplicar etiquetas en el repositorio en el que éstas se hayan creado. Una vez que exista una etiqueta, puedes utilizarla en cualquier {% ifversion fpt %}propuesta, solicitud de cambio o debate{% else %}propuesta o solicitud de cambio{% endif %} dentro del repositorio. -Cualquiera con acceso de lectura a un repositorio puede ver y buscar las etiquetas del repositorio. Cualquiera con acceso de clasificación en un repositorio puede aplicar/descartar las etiquetas existentes. Para crear, editar, aplicar o eliminar una etiqueta, debes tener acceso de escritura al repositorio. - ## Acerca de las etiquetas predeterminadas {% data variables.product.product_name %} ofrece etiquetas predeterminadas en cada repositorio nuevo. Puedes usar estas etiquetas predeterminadas para ayudar a crear un flujo de trabajo estándar en un repositorio. @@ -58,6 +57,8 @@ Los propietarios de la organización pueden personalizar las etiquetas predeterm ## Crear una etiqueta +Cualquiera con acceso de escritura en un repositorio puede crear una etiqueta. + {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} {% data reusables.project-management.labels %} @@ -69,11 +70,15 @@ Los propietarios de la organización pueden personalizar las etiquetas predeterm ## Aplicar una etiqueta +Cualquiera con acceso de clasificación en un repositorio puede aplicar y descartar etiquetas. + 1. Navega a la {% ifversion fpt %}propuesta, solicitud de cambios o debate{% else %}propuesta o solicitud de cambios{% endif %}. 1. En la barra lateral derecha, a la derecha de "Etiquetas", haz clic en {% octicon "gear" aria-label="The gear icon" %} y luego en la etiqueta. ![Menú desplegable de "Labels"](/assets/images/help/issues/labels-drop-down.png) ## Editar una etiqueta +Cualquiera con acceso de escritura en un repositorio puede editar las etiquetas existentes. + {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} {% data reusables.project-management.labels %} @@ -85,6 +90,8 @@ Los propietarios de la organización pueden personalizar las etiquetas predeterm ## Eliminar una etiqueta +Cualquiera con acceso de escritura en un repositorio puede borrar las etiquetas existentes. + El borrar una etiqueta la eliminará de las propuestas y soilcitudes de cambios. {% data reusables.repositories.navigate-to-repo %} @@ -93,6 +100,6 @@ El borrar una etiqueta la eliminará de las propuestas y soilcitudes de cambios. {% data reusables.project-management.delete-label %} ## Leer más -- "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)"{% ifversion fpt or ghes %} +- "[Filtrar y buscar propuestas y solicitudes de cambios](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)"{% ifversion fpt or ghes %} - "[Administrar las etiquetas predeterminadas para los repositorios de tu organización](/articles/managing-default-labels-for-repositories-in-your-organization)"{% endif %}{% ifversion fpt %} - "[Fomentar las contribuciones sanas a tu proyecto con etiquetas](/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels)"{% endif %} diff --git a/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md b/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md index e6093bc71f..e2f05b3e64 100644 --- a/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md +++ b/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md @@ -24,6 +24,8 @@ Las cuentas de empresa le permiten a los propietarios administrar en forma centr Para las organizaciones que pertenecen a una cuenta de empresa, la facturación se administra en el nivel de cuenta de empresa y los parámetros de facturación no están disponibles en el nivel de organización. Los propietarios de la empresa pueden establecer políticas para todas las organizaciones en la cuenta de empresa o permitirle a los propietarios de la organización establecer las políticas en el nivel de organización. Los propietarios de la organización no pueden cambiar los parámetros implementados para tu organización en el nivel de cuenta de empresa. Si tienes consultas sobre una política o la configuración para tu organización, comunícate con el propietario de tu cuenta de empresa. +{% data reusables.enterprise-accounts.invite-organization %} + {% data reusables.gated-features.enterprise-accounts %} {% data reusables.organizations.org-ownership-recommendation %} Para obtener más información, consulta la sección "[Mantener la continuidad de propiedad para tu organización](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)". diff --git a/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md b/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md index cd5aa82a0a..603d62bf26 100644 --- a/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md +++ b/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md @@ -1,28 +1,28 @@ --- -title: Customizing your organization's profile -intro: You can share information about your organization by customizing your organization's profile +title: Personalizar el perfil de tu organización +intro: Puedes compartir la información sobre tu organización si personalizas el perfil de esta versions: fpt: '*' ghes: '*' ghae: '*' topics: - Organizations -shortTitle: Customize organization profile +shortTitle: Personalizar el perfil de una organización --- -## About your organization's profile README +## Acerca del README del perfil de tu organización -You can share information about how to engage with your organization by creating an organization profile README. {% data variables.product.prodname_dotcom %} shows your organization profile README in the "Overview" tab of your organization. +Puedes compartir información sobre como participar con tu organización si creas un README de perfil de esta. {% data variables.product.prodname_dotcom %} te muestra el README del perfil de tu organización en la pestaña de "Resumen" de tu organización. -You can choose what information to include your organization profile README. Here are some examples of information that may be helpful in your organization's profile README. +Puedes elegir el tipo de información que incluirás en el README del perfil de tu organización. Aquí tienes algunos ejemplos de información que podría ser útil para tener en el README del perfil de tu organización. -- An "About" section that describes your organization -- Guidance for getting help in the organization +- Una sección de "Acerca de" que describa a tu organización +- Lineamientos para obtener ayuda en la organización -You can format text and include emoji, images, and GIFs in your organization profile README by using {% data variables.product.company_short %} Flavored Markdown. Para obtener más información, consulta la sección "[Iniciar con la escritura y el formato en {% data variables.product.prodname_dotcom %}](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github)". +Puedes formatear el texto e incluir emojis, imágenes y GIFs en el README del perfil de tu organización si utilizas el Marcado Enriquecido de {% data variables.product.company_short %}. Para obtener más información, consulta la sección "[Iniciar con la escritura y el formato en {% data variables.product.prodname_dotcom %}](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github)". -## Adding an organization profile README +## Agregar un README de perfil de una organización -1. If your organization does not already have a public `.github` repository, create a public `.github` repository. -2. In your organization's `.github` repository, create a `README.md` file in the `profile` folder. -3. Commit the changes to the `README.md` file. The content of the `README.md` will appear on your organization's profile. +1. Si tu organización aun no tiene un repositorio público de `.github`, crea un repositorio público de `.github`. +2. En el repositorio de `.github` de tu organización, crea un archivo de `README.md` en la carpeta `profile`. +3. Confirma los cambios al archivo `README.md`. El contenido del `README.md` aparecerá en el perfil de tu organización. diff --git a/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md b/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md index 3c97962e0d..7c74943cc5 100644 --- a/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md +++ b/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md @@ -37,7 +37,7 @@ Con la información sobre la actividad de la organización puedes ver semanal, m {% note %} -**Note:** Please make sure you have enabled the [Dependency Graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph#enabling-the-dependency-graph). +**Notea:** Por favor, asegúrate de que hayas habilitado la [Gráfica de dependencias](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph#enabling-the-dependency-graph). {% endnote %} diff --git a/translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md b/translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md index 811f349b87..cb39e3d536 100644 --- a/translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md +++ b/translations/es-ES/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md @@ -25,6 +25,18 @@ Puedes ver y revocar la identidad vinculada de cada miembro, sesiones activas y {% data reusables.saml.about-linked-identities %} +Cuando esté disponible, la entrada incluirá datos de SCIM. Para obtener más información, consulta la sección "[Acerca de SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)". + +{% warning %} + +**Advertencia:** Para las orgtanizaciones que utilizan SCIM: +- El revocar una identidad de usuario en {% data variables.product.product_name %} también eliminará los metadatos de SAML y de SCIM. Como resultado, el proveedor de identidad no podrá sincronizar o desaprovisionar la identidad de usuario enlazada. +- Un administrador deberá revocar una identidad enlazada a través del proveedor de identidad. +- Para revocar una identidad enlazada y enlazar una cuenta diferente a través del proveedor de identidad, un administrador puede eliminar y volver a asignar el usuario con la aplicación de {% data variables.product.product_name %}. Para obtener más información, consulta la documentación de tu proveedor de identidad. + +{% endwarning %} + + {% data reusables.identity-and-permissions.revoking-identity-team-sync %} {% data reusables.profile.access_org %} diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md index 37949cf493..77dbe783d1 100644 --- a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md +++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization.md @@ -117,7 +117,7 @@ Para permitir que el {% data variables.product.prodname_dependabot %} acceda a u 1. Ve a la configuración de análisis y seguridad para tu organización. Para obtener más información, consulta la sección "[Mostrar la configuración de análisis y seguridad](#displaying-the-security-and-analysis-settings)". 1. Debajo de "Acceso del {% data variables.product.prodname_dependabot %} a repositorios privados", haz clic en **Agregar repositorios privados** o **Agregar repositorios internos y privados**. ![Botón para agregar repositorios](/assets/images/help/organizations/dependabot-private-repository-access.png) -1. Comienza a teclear el nombre del repositorio que quieras permitir. ![Repository search field with filtered dropdown](/assets/images/help/organizations/dependabot-private-repo-choose.png) +1. Comienza a teclear el nombre del repositorio que quieras permitir. ![El campo de búsqueda del repositorio con el menú desplegable filtrado](/assets/images/help/organizations/dependabot-private-repo-choose.png) 1. Haz clic en el repositorio que quieras permitir. 1. Opcionalmente, para eliminar un repositorio de la lista, a la derecha de este, haz clic en {% octicon "x" aria-label="The X icon" %}. ![Botón "X" para eliminar un repositorio](/assets/images/help/organizations/dependabot-private-repository-list.png) diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization.md index 762403aa12..23fe87072e 100644 --- a/translations/es-ES/content/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization.md +++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization.md @@ -32,7 +32,7 @@ Para obtener más información, consulta la sección "[Verificar o aprobar un do Los colabores externos no están sujetos a las restricciones en las notificaciones por correo electrónico para los dominios verificados o aprobados. Para obtener más información sobre los colaboradores externos, consulta la sección "[Niveles de permiso para una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization#outside-collaborators)". -Si tu organización pertenece a una cuenta empresarial, los miembros de dicha organización podrán recibir notificaciones de cualquier dominio que verifique o apruebe esta cuenta, adicionalmente a cualquier dominio que la misma organización verifique o apruebe. {% ifversion fpt %}For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)."{% endif %}{% ifversion ghes > 3.1 %}For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."{% endif %} +Si tu organización pertenece a una cuenta empresarial, los miembros de dicha organización podrán recibir notificaciones de cualquier dominio que verifique o apruebe esta cuenta, adicionalmente a cualquier dominio que la misma organización verifique o apruebe. {% ifversion fpt %}Para obtener más información, consulta la sección "[Verificar o aprobar un dominio para tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)".{% endif %}{% ifversion ghes > 3.1 %}Para obtener más información, consulta la sección "[Verificar o aprobar un dominio para tu empresa](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)".{% endif %} ## Restringir las notificciones por correo electrónico diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md index 33e4331511..c86d07d6e7 100644 --- a/translations/es-ES/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md +++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md @@ -46,13 +46,15 @@ Para buscar eventos específicos, utiliza el calificador `action` en tu consulta | [`dependency_graph`](#dependency_graph-category-actions) | Contiene las actividades de configuración a nivel de organización para las gráficas de dependencia de los repositorios. Para obtener más información, consulta la sección "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". | | [`dependency_graph_new_repos`](#dependency_graph_new_repos-category-actions) | Contiene las actividades de configuración a nivel de organización para los repositorios nuevos que se crean en ella.{% endif %} | [`discussion_post`](#discussion_post-category-actions) | Contiene todas las actividades relacionadas con los debates publicados en una página de equipo. | -| [`discussion_post_reply`](#discussion_post_reply-category-actions) | Contains all activities related to replies to discussions posted to a team page.{% ifversion fpt or ghes %} +| [`discussion_post_reply`](#discussion_post_reply-category-actions) | Contiene todas las actividades relacionadas con las respuestas a los debates que se publican en una página de equipo.{% ifversion fpt or ghes %} | [`empresa`](#enterprise-category-actions) | Contiene las actividades relacionadas con la configuración de la empresa. |{% endif %} | [`gancho`](#hook-category-actions) | Contiene todas las actividades relacionadas con los webhooks. | | [`integration_installation_request`](#integration_installation_request-category-actions) | Contiene todas las actividades relacionadas con las solicitudes de los miembros de la organización para que los propietarios aprueben las integraciones para el uso en la organización. | +| [`ip_allow_list`](#ip_allow_list) | Contiene las actividades relacionadas con habilitar o inhabilitar la lista de direcciones IP permitidas para una organización. | +| [`ip_allow_list_entry`](#ip_allow_list_entry) | Contiene las actividades relacionadas con la creación, borrado y edición de una entrada en una lista de direcciones IP permitidas para una organización. | | [`propuesta`](#issue-category-actions) | Contiene las actividades relacionadas con borrar una propuesta. |{% ifversion fpt %} | [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | Contiene todas las actividades relacionadas con la firma del Acuerdo del programador de {% data variables.product.prodname_marketplace %}. | -| [`marketplace_listing`](#marketplace_listing-category-actions) | Contiene todas las actividades relacionadas con listar aplicaciones en {% data variables.product.prodname_marketplace %}.{% endif %}{% ifversion fpt or ghes > 3.0 %} +| [`marketplace_listing`](#marketplace_listing-category-actions) | Contiene todas las actividades relacionadas con el listado de apps en {% data variables.product.prodname_marketplace %}.{% endif %}{% ifversion fpt or ghes > 3.0 %} | [`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 fpt %} | [`org_credential_authorization`](#org_credential_authorization-category-actions) | Contiene todas las actividades relacionadas con la autorización de credenciales para su uso con el inicio de sesión único de SAML. {% endif %}{% ifversion fpt or ghes or ghae %} @@ -122,7 +124,7 @@ Al utilizar el calificador `country`, puedes filtrar los eventos en la bitácora Puedes interactuar con la bitácora de audotaría si utilizas la API de GraphQL{% ifversion fpt %} o la API de REST{% endif %}. {% ifversion fpt %} -The audit log API requires {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %} +La API de bitácoras de auditoría requiere {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %} ### Utilizar la API de GraphQL @@ -134,7 +136,7 @@ The audit log API requires {% data variables.product.prodname_ghe_cloud %}. {% d {% endnote %} -To ensure your intellectual property is secure, and you maintain compliance for your organization, you can use the audit log GraphQL API to keep copies of your audit log data and monitor: +Para garantizar que tu propiedad intelectual está segura y que mantienes el cumplimiento para tu organización, puedes utilizar la API de GraphQL para bitácoras de auditoría para mantener copias de tus datos de bitácoras de auditoría y monitorear: {% data reusables.audit_log.audit-log-api-info %} {% ifversion fpt %} @@ -155,7 +157,7 @@ Por ejemplo, puedes hacer una solicitud de GraphQL para ver todos los miembros n {% endnote %} -To ensure your intellectual property is secure, and you maintain compliance for your organization, you can use the audit log REST API to keep copies of your audit log data and monitor: +Para garantizar que tu propiedad intelectual está segura y que mantienes el cumplimiento para tu organización, puedes utilizar la API de REST de bitácoras de auditoría para mantener copias de tus bitácoras de auditoría y monitorear: {% data reusables.audit_log.audited-data-list %} {% data reusables.audit_log.audit-log-git-events-retention %} @@ -337,6 +339,23 @@ Un resumen de algunas de las acciones más comunes que se registran como eventos | `create (crear)` | Se activa cuando un miembro de la organización solicita que un propietario de la organización instale una integración para utilizar en la organización. | | `close` | Se activa cuando un propietario de la organización aprueba o rechaza una solicitud para instalar una integración para que se utilice en una organización, o cuando la cancela el miembro de la organización que abrió la solicitud. | +### `ip_allow_list` category actions + +| Acción | Descripción | +| ---------------------------- | --------------------------------------------------------------------------------------------------------------- | +| `habilitar` | Se activa cuando se habilita una lista de direcciones IP permitidas para una organización. | +| `inhabilitar` | Se activa cuando se inhabilita una lista de direcciones IP permitidas para una organización. | +| `enable_for_installed_apps` | Triggered when an IP allow list was enabled for installed {% data variables.product.prodname_github_apps %}. | +| `disable_for_installed_apps` | Triggered when an IP allow list was disabled for installed {% data variables.product.prodname_github_apps %}. | + +### `ip_allow_list_entry` category actions + +| Acción | Descripción | +| -------------------- | --------------------------------------------------------------- | +| `create (crear)` | Triggered when an IP address was added to an IP allow list. | +| `actualización` | Triggered when an IP address or its description was changed. | +| `destroy (destruir)` | Triggered when an IP address was deleted from an IP allow list. | + ### acciones de la categoría `issue` | Acción | Descripción | @@ -380,7 +399,7 @@ Para obtener más información, consulta la sección "[Administrar la publicaci | Acción | Descripción | | --------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `add_member (agregar miembro)` | Triggered when a user joins an organization.{% ifversion fpt or ghes > 3.0 or ghae-next %} +| `add_member (agregar miembro)` | Se activa cuando un usuario se une a una organización.{% ifversion fpt or ghes > 3.0 or ghae-next %} | `advanced_security_policy_selected_member_disabled` | Se activa cuando un propietario de empresa previene que las carcaterísticas de la {% data variables.product.prodname_GH_advanced_security %} se habiliten para los repositorios que pertenecen a la organización. {% data reusables.advanced-security.more-information-about-enforcement-policy %} | `advanced_security_policy_selected_member_enabled` | Se activa cuando un propietario de empresa permite que se habiliten las características de la {% data variables.product.prodname_GH_advanced_security %} en los repositorios que pertenecen a la organización. {% data reusables.advanced-security.more-information-about-enforcement-policy %}{% endif %}{% ifversion fpt %} | `audit_log_export` | Se activa cuando un administrador de la organización [crea una exportación del registro de auditoría de la organización](#exporting-the-audit-log). Si la exportación incluía una consulta, el registro detallará la consulta utilizada y la cantidad de entradas en el registro de auditoría que coinciden con esa consulta. | @@ -394,13 +413,13 @@ Para obtener más información, consulta la sección "[Administrar la publicaci | `enable_oauth_app_restrictions` | Se activa cuando un propietario [habilita restricciones de acceso de {% data variables.product.prodname_oauth_app %} ](/articles/enabling-oauth-app-access-restrictions-for-your-organization) para tu organización. | | `enable_saml` | Se activa cuando un administrador de la organización [habilita el inicio de sesión único de SAML](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) para una organización.{% endif %} | `enable_member_team_creation_permission` | Se activa cuando un propietario de la organización permite que los miembros creen equipos. Para obtener más información, consulta "[Configurar los permisos de creación de equipo en tu organización](/articles/setting-team-creation-permissions-in-your-organization)." |{% ifversion not ghae %} -| `enable_two_factor_requirement` | Triggered when an owner requires two-factor authentication for all members{% ifversion fpt %}, billing managers,{% endif %} and outside collaborators in an organization.{% endif %}{% ifversion fpt %} -| `invite_member` | Triggered when [a new user was invited to join your organization](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization). | +| `enable_two_factor_requirement` | Se activa cuando un propietario requiere la autenticación bifactorial para todos los miembros{% ifversion fpt %}, gerentes de facturación{% endif %} y colaboradores externos en una organización.{% endif %}{% ifversion fpt %} +| `invite_member` | Se activa cuando [se invitó a un usuario nuevo a unirse a tu organización](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization). | | `oauth_app_access_approved` | Se activa cuando un propietario [le otorga acceso a la organización a una {% data variables.product.prodname_oauth_app %}](/articles/approving-oauth-apps-for-your-organization/). | | `oauth_app_access_denied` | Se activa cuando un propietario [inhabilita un acceso de {% data variables.product.prodname_oauth_app %} anteriormente aprobado](/articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization) para tu organización. | -| `oauth_app_access_requested` | Triggered when an organization member requests that an owner grant an {% data variables.product.prodname_oauth_app %} access to your organization.{% endif %} +| `oauth_app_access_requested` | Se activa cuando un miembro de la organización solicita que un propietario otorgue un acceso de {% data variables.product.prodname_oauth_app %} para tu organización.{% endif %} | `register_self_hosted_runner` | Se crea cuando se registra un ejecutor auto-hospedado nuevo. Para obtener más información, consulta la sección "[Agregar un ejecutor auto-hospedado a una organización](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)". | -| `remove_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is removed.{% ifversion fpt %} +| `remove_actions_secret` | Se activa cuando se elimina un secreto de {% data variables.product.prodname_actions %}.{% ifversion fpt %} | `remove_billing_manager` | Se activa cuando un [propietario elimina un gerente de facturación de una organización](/articles/removing-a-billing-manager-from-your-organization/) o cuando [se requiere autenticación de dos factores en una organización](/articles/requiring-two-factor-authentication-in-your-organization) y un gerente de facturación no usa la 2FA o inhabilita la 2FA. {% endif %} | `remove_member (eliminar miembro)` | Se activa cuando un [propietario elimina a un miembro de una organización](/articles/removing-a-member-from-your-organization/){% ifversion not ghae %} o cuando [se requiere la autenticación bifactorial en una organización](/articles/requiring-two-factor-authentication-in-your-organization) y un miembro de la organización no utiliza 2FA o la inhabilita{% endif %}. También se activa cuando un [miembro de la organización se elimina a sí mismo](/articles/removing-yourself-from-an-organization/) de una organización. | @@ -409,20 +428,20 @@ Para obtener más información, consulta la sección "[Administrar la publicaci | `revoke_external_identity` | Se actuva cuando un dueño de una organización retira la identidad vinculada de un mimebro. Para obtener más información, consulta la sección "[Visualizar y administrar el acceso de SAML de un miembro a tu organización](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)". | | `revoke_sso_session` | Se activa cuando el dueño de una organización retira la sesión de SAML de un miembro. Para obtener más información, consulta la sección "[Visualizar y administrar el acceso de SAML de un miembro a tu organización](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)". |{% endif %} | `runner_group_created` | Se activa cuando se crea un grupo de ejecutores auto-hospedados. Para obtener más información, consulta la sección "[Crear un grupo de ejecutores auto-hospedados para una organización](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization)". | -| `runner_group_removed` | Se activa cuando se elimina un grupo de ejecutores auto-hospedado. For more information, see "[Removing a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)."{% ifversion fpt or ghes > 2.22 or ghae %} -| `runner_group_updated` | Se activa cuando se cambia la configuración de un grupo de ejecutores auto-hospedados. For more information, see "[Changing the access policy of a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)."{% endif %} +| `runner_group_removed` | Se activa cuando se elimina un grupo de ejecutores auto-hospedado. Para obtener más información, consulta la sección "[Eliminar un grupo de ejecutores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)".{% ifversion fpt or ghes > 2.22 or ghae %} +| `runner_group_updated` | Se activa cuando se cambia la configuración de un grupo de ejecutores auto-hospedados. Para obtener más información, consulta la sección "[cambiar la política de acceso de un grupo de ejecutores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)".{% endif %} | `runner_group_runners_added` | Se activa cuando se agrega un ejecutor auto-hospedado a un grupo. Para obtener más información, consulta la sección [Mover un ejecutor auto-hospedado a un grupo](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group). | | `runner_group_runner_removed` | Se activa cuando se utiliza la API de REST para eliminar un ejecutor auto-hospedado de un grupo. Para obtener más información, consulta la sección "[Eliminar un ejecutor auto-hospedado de un grupo en una organización](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)". | -| `runner_group_runners_updated` | Se activa cuando se actualiza la lista de miembros de un grupo de ejecutores. For more information, see "[Set self-hosted runners in a group for an organization](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)."{% ifversion ghes = 2.22 %} -| `runner_group_renamed` | Triggered when the self-hosted runner group is renamed. | -| `runner_group_visiblity_updated` | Triggered when the visibility settings of the self-hosted runner group are changed.{% endif %}{% ifversion fpt or ghes > 3.1 or ghae-issue-1157 %} -| `self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." | -| `self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %}{% ifversion fpt or ghes %} +| `runner_group_runners_updated` | Se activa cuando se actualiza la lista de miembros de un grupo de ejecutores. Para obtener más información, consulta la sección "[Configurar los ejecutores auto-hospedados en un grupo para una organización](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)". {% ifversion ghes = 2.22 %} +| `runner_group_renamed` | Se activa cuando el grupo de ejecutores auto-hospedados se renombra. | +| `runner_group_visiblity_updated` | Se activa cuando se cambia la configuración de visibilidad del grupo de ejecutores auto-hospedados.{% endif %}{% ifversion fpt or ghes > 3.1 or ghae-issue-1157 %} +| `self_hosted_runner_online` | Se activa cuando la aplicación del ejecutor se inicia. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." | +| `self_hosted_runner_offline` | Se activa cuando se detiene la aplicación del ejecutor. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta la sección "[Verificar el estado de un ejecutor auto-hospedado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)".{% endif %}{% ifversion fpt or ghes %} | `self_hosted_runner_updated` | Se activa cuando se actualiza la aplicación ejecutora. Se puede ver utilizando la API de REST y la IU; no se puede ver en la exportación de JSON/CSV. Para obtener más información, consulta la sección "[Acerca de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)".{% endif %}{% ifversion fpt %} | `set_actions_fork_pr_approvals_policy` | Se activa cuando se cambia el ajuste para requerir aprobaciones para los flujos de trabajo desde las bifurcaciones públicas en una organización. Para obtener más información, consulte la sección "[Requerir la aprobación para los flujos de trabajo desde las bifurcaciones públicas](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#requiring-approval-for-workflows-from-public-forks)".{% endif %}{% ifversion fpt or ghes > 2.22 or ghae %} | `set_actions_retention_limit` | Se activa cuando se cambia el periodo de retención para los artefactos y bitácoras de las {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Configurar el periodo de retención de los artefactos de las {% data variables.product.prodname_actions %} y las bitácoras en tu organización](/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization)".{% endif %}{% ifversion fpt or ghes > 2.22 %} | `set_fork_pr_workflows_policy` | Se activa cuando se cambia la política de flujos de trabajo sobre las bifurcaciones de repositorios privados. Para obtener más información, consulta la sección "[Habilitar los flujos de trabajo para las bifurcaciones de repositorios privados](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#enabling-workflows-for-private-repository-forks)".{% endif %}{% ifversion fpt %} -| `unblock_user` | Triggered when an organization owner [unblocks a user from an organization](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization).{% endif %}{% ifversion fpt or ghes %} +| `unblock_user` | Se acvita cuando el propietario de una organización [desbloquea a un usuario de la misma](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization).{% endif %}{% ifversion fpt or ghes %} | `update_actions_secret` | Se activa cuando se actualiza un secreto de {% data variables.product.prodname_actions %}.{% endif %}{% ifversion fpt or ghes > 2.22 or ghae %} | `update_new_repository_default_branch_setting` | Se activa cuando el propietario cambia el nombre de la rama predeterminada para los repositorios nuevos de la organización. Para obtener más información, consulta la sección "[Administrar el nombre de la rama predeterminada para los repositorios en tu organización](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)".{% endif %} | `update_default_repository_permission` | Se activa cuando un propietario cambia el nivel de permiso al repositorio predeterminado para los miembros de la organización. | @@ -563,39 +582,39 @@ Para obtener más información, consulta la sección "[Administrar la publicaci ### acciones de la categoría `repo` -| Acción | Descripción | -| --------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `access (acceder)` | Se activa cuando un usuario [cambia la visibilidad](/github/administering-a-repository/setting-repository-visibility) de un repositorio en la organización. | -| `actions_enabled` | Se activa cuando {% data variables.product.prodname_actions %} se habilita en un repositorio. Puede visualizarse utilizando la IU. Este evento no se incluye cuando accedes a la bitácora de auditoría utilizando la API de REST. Para obtener más información, consulta la sección "[Utilizar la API de REST](#using-the-rest-api)". | -| `add_member (agregar miembro)` | Se activa cuando un usuario acepta una [invitación para tener acceso de colaboración a un repositorio](/articles/inviting-collaborators-to-a-personal-repository). | +| Acción | Descripción | +| --------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `access (acceder)` | Se activa cuando un usuario [cambia la visibilidad](/github/administering-a-repository/setting-repository-visibility) de un repositorio en la organización. | +| `actions_enabled` | Se activa cuando {% data variables.product.prodname_actions %} se habilita en un repositorio. Puede visualizarse utilizando la IU. Este evento no se incluye cuando accedes a la bitácora de auditoría utilizando la API de REST. Para obtener más información, consulta la sección "[Utilizar la API de REST](#using-the-rest-api)". | +| `add_member (agregar miembro)` | Se activa cuando un usuario acepta una [invitación para tener acceso de colaboración a un repositorio](/articles/inviting-collaborators-to-a-personal-repository). | | `add_topic (agregar tema)` | Se activa cuando un administrador de repositorio [agrega un tema](/articles/classifying-your-repository-with-topics) a un repositorio.{% ifversion fpt or ghes > 3.0 or ghae-next %} -| `advanced_security_disabled` | Se activa cuando un adminsitrador de repositorio inhabilita las características de {% data variables.product.prodname_GH_advanced_security %} en este. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)". | +| `advanced_security_disabled` | Se activa cuando un adminsitrador de repositorio inhabilita las características de {% data variables.product.prodname_GH_advanced_security %} en este. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)". | | `advanced_security_enabled` | Se activa cuando un administrador de repositorio habilita las características de la {% data variables.product.prodname_GH_advanced_security %} para este. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)".{% endif %} | `archived (archivado)` | Se activa cuando un administrador del repositorio [archiva un repositorio](/articles/about-archiving-repositories).{% ifversion ghes %} -| `config.disable_anonymous_git_access (configurar inhabilitar el acceso de git anónimo)` | Se activa cuando [se inhabilita el acceso de lectura de Git anónimo](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) en un repositorio público. | -| `config.enable_anonymous_git_access (configurar habilitar acceso de git anónimo)` | Se activa cuando [se habilita el acceso de lectura de Git anónimo](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) en un repositorio público. | -| `config.lock_anonymous_git_access (configurar bloquear acceso de git anónimo)` | Se activa cuando se bloquea el parámetro de acceso de lectura de Git anónimo [de un repositorio](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access). | +| `config.disable_anonymous_git_access (configurar inhabilitar el acceso de git anónimo)` | Se activa cuando [se inhabilita el acceso de lectura de Git anónimo](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) en un repositorio público. | +| `config.enable_anonymous_git_access (configurar habilitar acceso de git anónimo)` | Se activa cuando [se habilita el acceso de lectura de Git anónimo](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) en un repositorio público. | +| `config.lock_anonymous_git_access (configurar bloquear acceso de git anónimo)` | Se activa cuando se bloquea el parámetro de acceso de lectura de Git anónimo [de un repositorio](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access). | | `config.unlock_anonymous_git_access (configurar desbloquear acceso de git anónimo)` | Se activa cuando se desbloquea el parámetro de acceso de lectura de Git anónimo [de un repositorio](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access).{% endif %} -| `create (crear)` | Triggered when [a new repository is created](/articles/creating-a-new-repository).{% ifversion fpt or ghes %} +| `create (crear)` | Se activa cuando [se crea un repositorio nuevo](/articles/creating-a-new-repository).{% ifversion fpt or ghes %} | `create_actions_secret` | Se crea cuando un secreto de {% data variables.product.prodname_actions %} se crea para un repositorio. Para obtener más información, consulta la sección "[Crear secretos cifrados para un repositorio](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)".{% endif %} | `destroy (destruir)` | Se activa cuando [se elimina un repositorio](/articles/deleting-a-repository).{% ifversion fpt %} | `inhabilitar` | Se activa cuando se inhabilita un repositorio (p. ej., por [fondos insuficientes](/articles/unlocking-a-locked-account)).{% endif %} -| `habilitar` | Triggered when a repository is re-enabled.{% ifversion fpt or ghes %} +| `habilitar` | Se activa cuando se vuelve a habilitar un repositorio.{% ifversion fpt or ghes %} | `remove_actions_secret` | Se activa cuando se elimina un secreto de {% data variables.product.prodname_actions %}.{% endif %} -| `remove_member (eliminar miembro)` | Se activa cuando un usuario se [elimina de un repositorio como colaborador](/articles/removing-a-collaborator-from-a-personal-repository). | -| `register_self_hosted_runner` | Se crea cuando se registra un ejecutor auto-hospedado nuevo. Para obtener más información, consulta la sección "[Agregar un ejecutor auto-hospedado a un repositorio](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)". | -| `remove_self_hosted_runner` | Se activa cuando se elimina un ejecutor auto-hospedado. Para obtener más información, consulta la sección "[Eliminar a un ejecutor de un repositorio](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)". | -| `remove_topic (eliminar tema)` | Se activa cuando un administrador del repositorio elimina un tema de un repositorio. | -| `rename (renombrar)` | Triggered when [a repository is renamed](/articles/renaming-a-repository).{% ifversion fpt or ghes > 3.1 or ghae-issue-1157 %} -| `self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." | -| `self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %}{% ifversion fpt or ghes %} +| `remove_member (eliminar miembro)` | Se activa cuando un usuario se [elimina de un repositorio como colaborador](/articles/removing-a-collaborator-from-a-personal-repository). | +| `register_self_hosted_runner` | Se crea cuando se registra un ejecutor auto-hospedado nuevo. Para obtener más información, consulta la sección "[Agregar un ejecutor auto-hospedado a un repositorio](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)". | +| `remove_self_hosted_runner` | Se activa cuando se elimina un ejecutor auto-hospedado. Para obtener más información, consulta la sección "[Eliminar a un ejecutor de un repositorio](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)". | +| `remove_topic (eliminar tema)` | Se activa cuando un administrador del repositorio elimina un tema de un repositorio. | +| `rename (renombrar)` | Se activa cuando [se vuelve a nombrar a un repositorio](/articles/renaming-a-repository).{% ifversion fpt or ghes > 3.1 or ghae-issue-1157 %} +| `self_hosted_runner_online` | Se activa cuando la aplicación del ejecutor se inicia. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." | +| `self_hosted_runner_offline` | Se activa cuando se detiene la aplicación del ejecutor. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta la sección "[Verificar el estado de un ejecutor auto-hospedado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)".{% endif %}{% ifversion fpt or ghes %} | `self_hosted_runner_updated` | Se activa cuando se actualiza la aplicación ejecutora. Se puede ver utilizando la API de REST y la IU; no se puede ver en la exportación de JSON/CSV. Para obtener más información, consulta la sección "[Acerca de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)".{% endif %}{% ifversion fpt %} -| `set_actions_fork_pr_approvals_policy` | Se activa cuando se cambia la configuración para requerir aprobaciones para los flujos de trabajo de las bifurcaciones públicas. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks)."{% endif %}{% ifversion fpt or ghes > 2.22 or ghae %} -| `set_actions_retention_limit` | Se activa cuando se cambia el periodo de retención para los artefactos y bitácoras de las {% data variables.product.prodname_actions %}. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)."{% endif %}{% ifversion fpt or ghes > 2.22 %} -| `set_fork_pr_workflows_policy` | Se activa cuando se cambia la política para flujos de trabajo en las bifurcaciones de los repositorios privados. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#enabling-workflows-for-private-repository-forks)."{% endif %} -| `transferencia` | Se activa cuando [se transfiere un repositorio](/articles/how-to-transfer-a-repository). | -| `transfer_start (comienzo de transferencia)` | Se activa cuando está por ocurrir una transferencia de repositorio. | -| `unarchived (desarchivado)` | Triggered when a repository admin unarchives a repository.{% ifversion fpt or ghes %} +| `set_actions_fork_pr_approvals_policy` | Se activa cuando se cambia la configuración para requerir aprobaciones para los flujos de trabajo de las bifurcaciones públicas. Para obtener más información, consulta la sección "[Administrar los ajustes de las {% data variables.product.prodname_actions %} en un repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks)".{% endif %}{% ifversion fpt or ghes > 2.22 or ghae %} +| `set_actions_retention_limit` | Se activa cuando se cambia el periodo de retención para los artefactos y bitácoras de las {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Administrar la configuración de {% data variables.product.prodname_actions %} en un repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)".{% endif %}{% ifversion fpt or ghes > 2.22 %} +| `set_fork_pr_workflows_policy` | Se activa cuando se cambia la política para flujos de trabajo en las bifurcaciones de los repositorios privados. Para obtener más información, consulta la sección "[Administrar los ajustes de las {% data variables.product.prodname_actions %} en un repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#enabling-workflows-for-private-repository-forks)".{% endif %} +| `transferencia` | Se activa cuando [se transfiere un repositorio](/articles/how-to-transfer-a-repository). | +| `transfer_start (comienzo de transferencia)` | Se activa cuando está por ocurrir una transferencia de repositorio. | +| `unarchived (desarchivado)` | Se activa cuando un administrador de repositorio deja de archivar un repositorio.{% ifversion fpt or ghes %} | `update_actions_secret` | Se activa cuando se actualiza un secreto de {% data variables.product.prodname_actions %}.{% endif %} {% ifversion fpt %} @@ -640,11 +659,11 @@ Para obtener más información, consulta la sección "[Administrar la publicaci {% endif %}{% ifversion not ghae %} ### acciones de la categoría `repository_vulnerability_alert` -| Acción | Descripción | -| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `create (crear)` | Triggered when {% data variables.product.product_name %} creates a {% ifversion fpt or ghes %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alert for a repository that uses a vulnerable dependency. Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)". | -| `descartar` | Triggered when an organization owner or person with admin access to the repository dismisses a {% ifversion fpt or ghes %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alert about a vulnerable dependency. | -| `resolver` | Se activa cuando alguien con acceso de escritura en un repositorio sube cambios para actualizar y resolver una vulnerabilidad en una dependencia de proyecto. | +| Acción | Descripción | +| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `create (crear)` | Se activa cuando {% data variables.product.product_name %} crea una alerta de {% ifversion fpt or ghes %}{% else %}seguridad del {% data variables.product.prodname_dependabot %}{% endif %} para un repositorio que utiliza una dependencia vulnerable. Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)". | +| `descartar` | Se activa cuando un propietario de organización o persona con acceso administrativo al repositorio descarta una alerta de {% ifversion fpt or ghes %}seguridad del {% else %}{% data variables.product.prodname_dependabot %}{% endif %} sobre una dependencia vulnerable. | +| `resolver` | Se activa cuando alguien con acceso de escritura en un repositorio sube cambios para actualizar y resolver una vulnerabilidad en una dependencia de proyecto. | {% endif %}{% ifversion fpt %} ### acciones de la categoría `repository_vulnerability_alerts` diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md index d1dc1a84fc..3efa00a556 100644 --- a/translations/es-ES/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md +++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations.md @@ -17,7 +17,7 @@ shortTitle: Revisar las integraciones instaladas {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -4. In the left sidebar, click **Installed {% data variables.product.prodname_github_apps %}**. ![Installed {% data variables.product.prodname_github_apps %} tab in the organization settings sidebar](/assets/images/help/organizations/org-settings-installed-github-apps.png) +4. En la barra lateral izquierda, haz clic en **{% data variables.product.prodname_github_apps %} Instaladas**. ![Pestaña de {% data variables.product.prodname_github_apps %} instaladas en la barra lateral de parámetros de la organización](/assets/images/help/organizations/org-settings-installed-github-apps.png) 5. Al lado de la {% data variables.product.prodname_github_app %} que quieras revisar, haz clic en **Configure** (Configurar). ![Botón Configure (Configurar)](/assets/images/help/organizations/configure-installed-integration-button.png) 6. Revisa el acceso al repositorio y los permisos de {% data variables.product.prodname_github_app %}. ![Opción para darle acceso a {% data variables.product.prodname_github_app %} a todos los repositorios o a repositorios específicos](/assets/images/help/organizations/toggle-integration-repo-access.png) - Para darle acceso a la {% data variables.product.prodname_github_app %} a todos los repositorios de tu organización, selecciona **All repositories** (Todos los repositorios). diff --git a/translations/es-ES/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md index 6f6b687acc..75389e14ec 100644 --- a/translations/es-ES/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md +++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md @@ -1,6 +1,6 @@ --- title: Agregar administradores de App GitHub a tu organización -intro: 'Organization owners can grant users the ability to manage some or all {% data variables.product.prodname_github_apps %} owned by the organization.' +intro: 'Los propietarios de la organización pueden conceder a los usuarios la capacidad para administrar alguna o todas las {% data variables.product.prodname_github_apps %} que le pertenecen a la organización.' redirect_from: - /articles/adding-github-app-managers-in-your-organization - /github/setting-up-and-managing-organizations-and-teams/adding-github-app-managers-in-your-organization @@ -16,7 +16,7 @@ shortTitle: Agregar administradores de GitHub Apps Para más información sobre los permisos del administrador de {% data variables.product.prodname_github_app %}, consulta "[Niveles de permiso para una organización](/articles/permission-levels-for-an-organization#github-app-managers)". -## Giving someone the ability to manage all {% data variables.product.prodname_github_apps %} owned by the organization +## Brindar a alguien la posibilidad de administrar todas las {% data variables.product.prodname_github_apps %} que son propiedad de la organización {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} @@ -28,7 +28,7 @@ Para más información sobre los permisos del administrador de {% data variables {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.github-apps-settings-sidebar %} -1. Under "{% data variables.product.prodname_github_apps %}", click on the avatar of the app you'd like to add a {% data variables.product.prodname_github_app %} manager for. ![Seleccionar {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/select-github-app.png) +1. Debajo de "{% data variables.product.prodname_github_apps %}s", haz clic en el avatar de la app a la que quieres agregar un administrador de {% data variables.product.prodname_github_app %}. ![Seleccionar {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/select-github-app.png) {% data reusables.organizations.app-managers-settings-sidebar %} 1. En "App managers" (Administradores de la app), escribe el nombre de usuario de la persona a quien deseas designar como administrador de la App GitHub para la app, y haz clic en **Grant** (Conceder). ![Agregar un administrador de {% data variables.product.prodname_github_app %} para una app específica](/assets/images/help/organizations/add-github-app-manager-for-app.png) diff --git a/translations/es-ES/content/organizations/managing-access-to-your-organizations-apps/index.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-apps/index.md index cbcded93ed..d016686bbe 100644 --- a/translations/es-ES/content/organizations/managing-access-to-your-organizations-apps/index.md +++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-apps/index.md @@ -1,6 +1,6 @@ --- title: Administrar el acceso a las aplicaciones de tu organización -intro: 'As an organization owner, you can allow individual organization members to manage {% data variables.product.prodname_github_apps %} in your organization.' +intro: 'Como propietario de una organización, puedes permitir a los miembros individuales de la misma que administren las {% data variables.product.prodname_github_apps %} en tu organización.' redirect_from: - /articles/managing-access-to-your-organization-s-apps - /articles/managing-access-to-your-organizations-apps diff --git a/translations/es-ES/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md index 22871ae5df..3abce6d5b2 100644 --- a/translations/es-ES/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md +++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md @@ -28,7 +28,7 @@ Para más información sobre los permisos del administrador de {% data variables {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.github-apps-settings-sidebar %} -1. Under "{% data variables.product.prodname_github_apps %}", click on the avatar of the app you'd like to remove a {% data variables.product.prodname_github_app %} manager from. ![Seleccionar {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/select-github-app.png) +1. Debajo de "{% data variables.product.prodname_github_apps %}s", haz clic en el avatar de la app de la que quieres eliminar un administrador de {% data variables.product.prodname_github_app %}. ![Seleccionar {% data variables.product.prodname_github_app %}](/assets/images/help/organizations/select-github-app.png) {% data reusables.organizations.app-managers-settings-sidebar %} 1. En "App managers" (Administradores de app), encuentra el nombre de usuario de la persona para la que quieres eliminar {% data variables.product.prodname_github_app %} los permisos de administrador, luego haz clic en **Revoke** (Revocar). ![Revocar {% data variables.product.prodname_github_app %} permisos de administrador](/assets/images/help/organizations/github-app-manager-revoke-permissions-individual-app.png) diff --git a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md index 2fcf1fde7f..70abe55a34 100644 --- a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md +++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md @@ -14,7 +14,7 @@ topics: shortTitle: Agregar un colaborador externo --- -## About outside collaborators +## Acerca de los colaboradores externos {% data reusables.organizations.owners-and-admins-can %} agregar colaboradores externos a un repositorio, a menos que un propietario de la organización haya restringido la capacidad para invitar colaboradores. Para obtener más información, consulta "[Establecer permisos para agregar colaboradores externos](/articles/setting-permissions-for-adding-outside-collaborators)". @@ -27,10 +27,10 @@ Si tu organización [requiere miembros y colaboradores externos para usar la aut {% data reusables.organizations.outside_collaborator_forks %} {% ifversion fpt %} -To further support your team's collaboration abilities, you can upgrade to {% data variables.product.prodname_ghe_cloud %}, which includes features like protected branches and code owners on private repositories. {% data reusables.enterprise.link-to-ghec-trial %} +Para apoyar aún más las capacidades de colaboración de tu equipo, puedes mejorar a {% data variables.product.prodname_ghe_cloud %}, el cual incluye características como las ramas protegidas y los propietarios de código en los repositorios privados. {% data reusables.enterprise.link-to-ghec-trial %} {% endif %} -## Adding outside collaborators to a repository +## Agregar colaboradores externos a un repositorio {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} diff --git a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md index 544dba8f96..2fa859a60b 100644 --- a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md +++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md @@ -43,7 +43,7 @@ Además de administrar los parámetros al nivel de la organización, los propiet ## Acceso al repositorio para cada nivel de permiso {% ifversion fpt %} -Some of the features listed below are limited to organizations using {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %} +Algunas de las características que se listan a continuación se limitan a las organizaciones que utilizan {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %} {% endif %} {% ifversion fpt or ghes %} @@ -54,95 +54,96 @@ Some of the features listed below are limited to organizations using {% data var {% endnote %} {% endif %} -| Acción del repositorio | Read | Clasificación | Escritura | Mantenimiento | Admin | -|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-------------:|:---------:|:-------------:|:------------------------------------------------:| -| Extraer desde los repositorios asignados de la persona o el equipo | **X** | **X** | **X** | **X** | **X** | -| Bifurcar los repositorios asignados de la persona o el equipo | **X** | **X** | **X** | **X** | **X** | -| Editar y eliminar sus propios comentarios | **X** | **X** | **X** | **X** | **X** | -| Abrir propuestas | **X** | **X** | **X** | **X** | **X** | -| Cerrar propuestas que ellos mismos abrieron | **X** | **X** | **X** | **X** | **X** | -| Reabrir propuestas que ellos mismos cerraron | **X** | **X** | **X** | **X** | **X** | -| Recibir la asignación de una propuesta | **X** | **X** | **X** | **X** | **X** | -| Enviar solicitudes de extracción desde las bifurcaciones de los repositorios asignados del equipo | **X** | **X** | **X** | **X** | **X** | -| Enviar revisiones sobre solicitudes de extracción | **X** | **X** | **X** | **X** | **X** | -| Ver los lanzamientos publicados | **X** | **X** | **X** | **X** | **X** |{% ifversion fpt %} -| Ver las [Ejecuciones de flujo de trabajo de GitHub Actions](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **X** | **X** | **X** | **X** | **X** +| Acción del repositorio | Read | Clasificación | Escritura | Mantenimiento | Admin | +|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-------------:|:---------:|:-------------:|:-----------------------------------------------------:| +| Extraer desde los repositorios asignados de la persona o el equipo | **X** | **X** | **X** | **X** | **X** | +| Bifurcar los repositorios asignados de la persona o el equipo | **X** | **X** | **X** | **X** | **X** | +| Editar y eliminar sus propios comentarios | **X** | **X** | **X** | **X** | **X** | +| Abrir propuestas | **X** | **X** | **X** | **X** | **X** | +| Cerrar propuestas que ellos mismos abrieron | **X** | **X** | **X** | **X** | **X** | +| Reabrir propuestas que ellos mismos cerraron | **X** | **X** | **X** | **X** | **X** | +| Recibir la asignación de una propuesta | **X** | **X** | **X** | **X** | **X** | +| Enviar solicitudes de extracción desde las bifurcaciones de los repositorios asignados del equipo | **X** | **X** | **X** | **X** | **X** | +| Enviar revisiones sobre solicitudes de extracción | **X** | **X** | **X** | **X** | **X** | +| Ver los lanzamientos publicados | **X** | **X** | **X** | **X** | **X** |{% ifversion fpt %} +| Ver las [Ejecuciones de flujo de trabajo de GitHub Actions](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **X** | **X** | **X** | **X** | **X** {% endif %} -| Editar wikis | **X** | **X** | **X** | **X** | **X** |{% ifversion fpt %} -| [Informar contenido abusivo o de spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** +| Edit wikis in public repositories | **X** | **X** | **X** | **X** | **X** | +| Edit wikis in private repositories | | | **X** | **X** | **X** |{% ifversion fpt %} +| [Informar contenido abusivo o de spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** {% endif %} -| Aplicar/descartar etiquetas | | **X** | **X** | **X** | **X** | -| Crear, editar, borrar etiquetas | | | **X** | **X** | **X** | -| Elegir, reabrir y asignar todas las propuestas y solicitudes de extracción | | **X** | **X** | **X** | **X** |{% ifversion fpt or ghae or ghes > 3.0 %} -| [Habilitar e inhabilitar la fusión automática en una solicitud de cambios](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** +| Aplicar/descartar etiquetas | | **X** | **X** | **X** | **X** | +| Crear, editar, borrar etiquetas | | | **X** | **X** | **X** | +| Elegir, reabrir y asignar todas las propuestas y solicitudes de extracción | | **X** | **X** | **X** | **X** |{% ifversion fpt or ghae or ghes > 3.0 %} +| [Habilitar e inhabilitar la fusión automática en una solicitud de cambios](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** {% endif %} -| Aplicar hitos | | **X** | **X** | **X** | **X** | -| Marcar [duplicar propuestas y solicitudes de extracción](/articles/about-duplicate-issues-and-pull-requests) | | **X** | **X** | **X** | **X** | -| Solicitar [revisiones de solicitudes de extracción](/articles/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** | -| Merge a [pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges) | | | **X** | **X** | **X** | -| Subir a (escribir en) los repositorios asignados de la persona o el equipo | | | **X** | **X** | **X** | -| Editar y eliminar comentarios o confirmaciones, solicitudes de extracción y propuestas de cualquier persona | | | **X** | **X** | **X** | -| [Ocultar los comentarios de cualquier persona](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **X** | **X** | **X** | -| [Bloquear conversaciones](/communities/moderating-comments-and-conversations/locking-conversations) | | | **X** | **X** | **X** | -| Transferir propuestas (consulta "[Transferir una propuesta a otro repositorio](/articles/transferring-an-issue-to-another-repository)" para obtener detalles) | | | **X** | **X** | **X** | -| [Actuar como propietario del código designado para un repositorio](/articles/about-code-owners) | | | **X** | **X** | **X** | -| [Marcar un borrador de solicitud de extracción como listo para revisión](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | -| [Convertir una solicitud de extracción en borrador](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | -| Enviar revisiones que afecten la capacidad de fusión de una solicitud de extracción | | | **X** | **X** | **X** | -| [Aplicar cambios sugeridos](/articles/incorporating-feedback-in-your-pull-request) a las solicitudes de extracción | | | **X** | **X** | **X** | -| Crear [comprobaciones de estado](/articles/about-status-checks) | | | **X** | **X** | **X** |{% ifversion fpt %} -| Crear, editar, ejecutar, volver a ejecutar y cancelar [Flujos de trabajo de Acciones de GitHub](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** +| Aplicar hitos | | **X** | **X** | **X** | **X** | +| Marcar [duplicar propuestas y solicitudes de extracción](/articles/about-duplicate-issues-and-pull-requests) | | **X** | **X** | **X** | **X** | +| Solicitar [revisiones de solicitudes de extracción](/articles/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** | +| Fusionar una [solicitud de cambios](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges) | | | **X** | **X** | **X** | +| Subir a (escribir en) los repositorios asignados de la persona o el equipo | | | **X** | **X** | **X** | +| Editar y eliminar comentarios o confirmaciones, solicitudes de extracción y propuestas de cualquier persona | | | **X** | **X** | **X** | +| [Ocultar los comentarios de cualquier persona](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **X** | **X** | **X** | +| [Bloquear conversaciones](/communities/moderating-comments-and-conversations/locking-conversations) | | | **X** | **X** | **X** | +| Transferir propuestas (consulta "[Transferir una propuesta a otro repositorio](/articles/transferring-an-issue-to-another-repository)" para obtener detalles) | | | **X** | **X** | **X** | +| [Actuar como propietario del código designado para un repositorio](/articles/about-code-owners) | | | **X** | **X** | **X** | +| [Marcar un borrador de solicitud de extracción como listo para revisión](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | +| [Convertir una solicitud de extracción en borrador](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | +| Enviar revisiones que afecten la capacidad de fusión de una solicitud de extracción | | | **X** | **X** | **X** | +| [Aplicar cambios sugeridos](/articles/incorporating-feedback-in-your-pull-request) a las solicitudes de extracción | | | **X** | **X** | **X** | +| Crear [comprobaciones de estado](/articles/about-status-checks) | | | **X** | **X** | **X** |{% ifversion fpt %} +| Crear, editar, ejecutar, volver a ejecutar y cancelar [Flujos de trabajo de Acciones de GitHub](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** {% endif %} -| Crear y editar lanzamientos | | | **X** | **X** | **X** | -| Ver lanzamientos en borrador | | | **X** | **X** | **X** | -| Editar la descripción de un repositorio | | | | **X** | **X** |{% ifversion fpt or ghae %} -| [Ver e instalar paquetes](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | -| [Publicar paquetes](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | -| | | | | | | -| {% ifversion fpt or ghes > 3.0 %}[Borrar y restablecer paquetes](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Borrar paquetes](/packages/learn-github-packages/deleting-a-package){% endif %} | | | | | **X** | {% endif %} -| Administrar [temas](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** | -| Habilitar wikis y restringir editores de wikis | | | | **X** | **X** | -| Habilitar tableros de proyecto | | | | **X** | **X** | -| Configurar las [fusiones de la solicitud de extracción](/articles/configuring-pull-request-merges) | | | | **X** | **X** | -| Configurar [una fuente de publicaciones para {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** | -| [Subir a ramas protegidas](/articles/about-protected-branches) | | | | **X** | **X** | -| [Crear y editar las tarjetas sociales del repositorio](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% ifversion fpt %} -| Limitar las [interacciones en un repositorio](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository) | | | | **X** | **X** +| Crear y editar lanzamientos | | | **X** | **X** | **X** | +| Ver lanzamientos en borrador | | | **X** | **X** | **X** | +| Editar la descripción de un repositorio | | | | **X** | **X** |{% ifversion fpt or ghae %} +| [Ver e instalar paquetes](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | +| [Publicar paquetes](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | +| | | | | | | +| {% ifversion fpt or ghes > 3.0 %}[Borrar y restablecer paquetes](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Borrar paquetes](/packages/learn-github-packages/deleting-a-package){% endif %} | | | | | **X** | {% endif %} +| Administrar [temas](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** | +| Habilitar wikis y restringir editores de wikis | | | | **X** | **X** | +| Habilitar tableros de proyecto | | | | **X** | **X** | +| Configurar las [fusiones de la solicitud de extracción](/articles/configuring-pull-request-merges) | | | | **X** | **X** | +| Configurar [una fuente de publicaciones para {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** | +| [Subir a ramas protegidas](/articles/about-protected-branches) | | | | **X** | **X** | +| [Crear y editar las tarjetas sociales del repositorio](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% ifversion fpt %} +| Limitar las [interacciones en un repositorio](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository) | | | | **X** | **X** {% endif %} -| Eliminar una propuesta (consulta "[Eliminar una propuesta](/articles/deleting-an-issue)") | | | | | **X** | -| Fusionar solicitudes de extracción en ramas protegidas, incluso si no existen revisiones en aprobación | | | | | **X** | -| [Definir propietarios del código para un repositorio](/articles/about-code-owners) | | | | | **X** | -| Añadir un repositorio a un equipo (consulta la sección "[Administrar el acceso de un equipo a un repositorio de la organización](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)" para obtener más detalles) | | | | | **X** | -| [Gestionar el acceso de un colaborador externo a un repositorio](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | -| [Cambiar la visibilidad de un repositorio](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | -| Volver plantilla un repositorio (consulta "[Crear un repositorio de plantilla](/articles/creating-a-template-repository)") | | | | | **X** | -| Cambiar los parámetros de un repositorio | | | | | **X** | -| Administrar el acceso de un equipo o colaborador al repositorio | | | | | **X** | -| Editar la rama predeterminada del repositorio | | | | | **X** |{% ifversion fpt or ghes > 3.0 %} -| Renombrar la rama predeterminada del repositorio (consulta la sección "[Renombrar una rama](/github/administering-a-repository/renaming-a-branch)") | | | | | **X** | -| Renombrar una rama diferente a la rama predeterminada del repositorio (consulta la sección "[Renombrar una rama](/github/administering-a-repository/renaming-a-branch)") | | | **X** | **X** | **X** +| Eliminar una propuesta (consulta "[Eliminar una propuesta](/articles/deleting-an-issue)") | | | | | **X** | +| Fusionar solicitudes de extracción en ramas protegidas, incluso si no existen revisiones en aprobación | | | | | **X** | +| [Definir propietarios del código para un repositorio](/articles/about-code-owners) | | | | | **X** | +| Añadir un repositorio a un equipo (consulta la sección "[Administrar el acceso de un equipo a un repositorio de la organización](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)" para obtener más detalles) | | | | | **X** | +| [Gestionar el acceso de un colaborador externo a un repositorio](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | +| [Cambiar la visibilidad de un repositorio](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | +| Volver plantilla un repositorio (consulta "[Crear un repositorio de plantilla](/articles/creating-a-template-repository)") | | | | | **X** | +| Cambiar los parámetros de un repositorio | | | | | **X** | +| Administrar el acceso de un equipo o colaborador al repositorio | | | | | **X** | +| Editar la rama predeterminada del repositorio | | | | | **X** |{% ifversion fpt or ghes > 3.0 or ghae-next %} +| Renombrar la rama predeterminada del repositorio (consulta la sección "[Renombrar una rama](/github/administering-a-repository/renaming-a-branch)") | | | | | **X** | +| Renombrar una rama diferente a la rama predeterminada del repositorio (consulta la sección "[Renombrar una rama](/github/administering-a-repository/renaming-a-branch)") | | | **X** | **X** | **X** {% endif %} -| Administrar webhooks y desplegar llaves | | | | | **X** |{% ifversion fpt %} -| [Administrar la configuración de uso de datos para tu repositorio privado](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **X** +| Administrar webhooks y desplegar llaves | | | | | **X** |{% ifversion fpt %} +| [Administrar la configuración de uso de datos para tu repositorio privado](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **X** {% endif %} -| [Administrar la política de bifurcación de un repositorio](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | -| [Transferir repositorios a la organización](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | -| [Eliminar o transferir repositorios fuera de la organización](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | -| [Archivar repositorios](/articles/about-archiving-repositories) | | | | | **X** |{% ifversion fpt %} -| Mostrar el botón de un patrocinador (consulta "[Mostrar el botón de un patrocinador en tu repositorio](/articles/displaying-a-sponsor-button-in-your-repository)") | | | | | **X** +| [Administrar la política de bifurcación de un repositorio](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | +| [Transferir repositorios a la organización](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | +| [Eliminar o transferir repositorios fuera de la organización](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | +| [Archivar repositorios](/articles/about-archiving-repositories) | | | | | **X** |{% ifversion fpt %} +| Mostrar el botón de un patrocinador (consulta "[Mostrar el botón de un patrocinador en tu repositorio](/articles/displaying-a-sponsor-button-in-your-repository)") | | | | | **X** {% endif %} -| Crear referencias de enlace automático a recursos externos, como JIRA o Zendesk (consulta "[Configurar enlaces automáticos para referenciar recursos externos](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **X** |{% ifversion fpt %} -| [Habilitar {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) en un repositorio | | | | **X** | **X** | -| [Crear y editar categorías](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) para {% data variables.product.prodname_discussions %} | | | | **X** | **X** | -| [Mover un debate a una categoría diferente](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [Transferir un debate](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) a un repositorio nuevo | | | **X** | **X** | **X** | -| [Administrar debates fijados](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [Converitr propuestas en debates por lote](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [Bloquear y desbloquear los debates](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [Convertir las propuestas en debates individualmente](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [Crear debates nuevos y comentar sobre los debates existentes](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** | -| [Borrar un debate](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion) | | | | **X** | **X** |{% endif %}{% ifversion fpt %} -| Crear [codespaces](/codespaces/about-codespaces) | | | **X** | **X** | **X** +| Crear referencias de enlace automático a recursos externos, como JIRA o Zendesk (consulta "[Configurar enlaces automáticos para referenciar recursos externos](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **X** |{% ifversion fpt %} +| [Habilitar {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) en un repositorio | | | | **X** | **X** | +| [Crear y editar categorías](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) para {% data variables.product.prodname_discussions %} | | | | **X** | **X** | +| [Mover un debate a una categoría diferente](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Transferir un debate](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) a un repositorio nuevo | | | **X** | **X** | **X** | +| [Administrar debates fijados](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Converitr propuestas en debates por lote](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Bloquear y desbloquear los debates](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [Convertir las propuestas en debates individualmente](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [Crear debates nuevos y comentar sobre los debates existentes](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** | +| [Borrar un debate](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion) | | | | **X** | **X** |{% endif %}{% ifversion fpt %} +| Crear [codespaces](/codespaces/about-codespaces) | | | **X** | **X** | **X** {% endif %} ### Requisitos de permisos para características de seguridad diff --git a/translations/es-ES/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md b/translations/es-ES/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md index 05c4903b91..6cb7767e26 100644 --- a/translations/es-ES/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md +++ b/translations/es-ES/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md @@ -21,7 +21,7 @@ Una vez que agregas una CA de SSH a tu cuenta de empresa u organización, puedes Por ejemplo, puedes crear un sistema interno que emita un nuevo certificado para tus programadores cada mañana. Cada programador puede usar su certificado diario para trabajar en los repositorios de tu organización en {% data variables.product.product_name %}. Al finalizar el día, el certificado puede expirar automáticamente, protegiendo tus repositorios si el certificado más tarde se ve comprometido. -Cuando emites cada certificado, debes incluir una extensión que especifique para qué usuario de {% data variables.product.product_name %} es el certificado. Por ejemplo, puedes usar el comando `ssh-keygen` de OpenSSH, reemplazando _KEY-IDENTITY_ por tu identidad de clave y _USERNAME_ por un nombre de usuario de {% data variables.product.product_name %}. The certificate you generate will be authorized to act on behalf of that user for any of your organization's resources. Make sure you validate the user's identity before you issue the certificate. +Cuando emites cada certificado, debes incluir una extensión que especifique para qué usuario de {% data variables.product.product_name %} es el certificado. Por ejemplo, puedes usar el comando `ssh-keygen` de OpenSSH, reemplazando _KEY-IDENTITY_ por tu identidad de clave y _USERNAME_ por un nombre de usuario de {% data variables.product.product_name %}. El certificado que generes se autorizará para actuar en nombre de ese usuario para cualquiera de los recursos de tu organización. Asegúrate de validar la identidad de los usuarios antes de que emitas el certificado. ```shell $ ssh-keygen -s ./ca-key -I KEY-IDENTITY -O extension:login@{% data variables.product.product_url %}=USERNAME ./user-key.pub diff --git a/translations/es-ES/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md b/translations/es-ES/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md index 09822e9d0e..b6fb416314 100644 --- a/translations/es-ES/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md +++ b/translations/es-ES/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md @@ -23,7 +23,7 @@ Solo los propietarios de la organización pueden eliminar usuarios de una organi **Advertencia:** Cuando eliminas a algún miembro de una organización: - La cuenta de licencias pagadas no baja de categoría automáticamente. Para pagar por menos licencias después de eliminar usuarios de tu organización, sigue los pasos de la sección "[Bajar el cupo límite de plazas pagadas en tu organización](/articles/downgrading-your-organization-s-paid-seats)". - Los miembros eliminados perderán el acceso a las bifurcaciones privadas de los repositorios privados de tu organización, pero aún podrían tener copias locales de estas. Sin embargo, no pueden sincronizar las copias locales con tus repositorios de la organización. Se pueden restaurar las bifurcaciones privadas del usuario si se lo reinstala [como miembro de la organización](/articles/reinstating-a-former-member-of-your-organization) dentro de los tres meses posteriores a haber sido eliminado de la organización. En última instancia, tú eres el responsable de asegurar que las personas que perdieron acceso a un repositorio borren cualquier información confidencial o propiedad intelectual. -- If your organization is owned by an enterprise account, removed members will also lose access to private forks of your organization's internal repositories, if the removed member is not a member of any other organization owned by the same enterprise account. Para obtener más información, consulta "[Acerca de las cuentas de empresa](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts)". +- Si tu organización le pertenece a una cuenta empresarial, los miembros eliminados también perderán acceso a las bifurcaciones privadas de los repositorios internos de tu organización en caso de que el miembro que se elimine no sea miembro de otra organización que le pertenezca a la misma cuenta empresarial. Para obtener más información, consulta "[Acerca de las cuentas de empresa](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts)". - Cualquier invitación a una organización que envíe un miembro eliminado, y que no se haya aceptado, se cancelará y no se podrá acceder a ella. {% endwarning %} @@ -34,7 +34,7 @@ Solo los propietarios de la organización pueden eliminar usuarios de una organi **Advertencia:** Cuando eliminas a algún miembro de una organización: - Los miembros eliminados perderán el acceso a las bifurcaciones privadas de los repositorios privados de tu organización, pero aún podrían tener copias locales de estas. Sin embargo, no pueden sincronizar las copias locales con tus repositorios de la organización. Se pueden restaurar las bifurcaciones privadas del usuario si se lo reinstala [como miembro de la organización](/articles/reinstating-a-former-member-of-your-organization) dentro de los tres meses posteriores a haber sido eliminado de la organización. En última instancia, tú eres el responsable de asegurar que las personas que perdieron acceso a un repositorio borren cualquier información confidencial o propiedad intelectual. -- Removed members will also lose access to private forks of your organization's internal repositories, if the removed member is not a member of any other organization in your enterprise. +- Los miembros eliminados también perderán acceso a las bifurcaciones privadas de los repositorios internos de tu organización si el miembro que s eliminó no es miembro de otra organización de tu empresa. - Cualquier invitación a una organización que envíe el usuario eliminado y que no se haya aceptado se cancelará y no se podrá acceder a ella. {% endwarning %} 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 1ed5805c9d..c10ed348c0 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 @@ -36,7 +36,7 @@ De manera alterna, puedes habilitar {% data variables.product.prodname_actions % {% endif %} -{% ifversion fpt or ghes > 2.22 %} +{% ifversion fpt or ghes > 2.22 or ghae-next %} ## Administrar los permisos de {% data variables.product.prodname_actions %} para tu organización @@ -63,7 +63,12 @@ Puedes inhabilitar todos los flujos de trabajo para una organización o configur {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.settings-sidebar-actions %} -1. Debajo de **Políticas**, selecciona **Permitir las acciones seleccionadas** y agrega tus acciones requeridas a la lista. ![Agregar acciones a la lista de permitidos](/assets/images/help/organizations/actions-policy-allow-list.png) +1. Debajo de **Políticas**, selecciona **Permitir las acciones seleccionadas** y agrega tus acciones requeridas a la lista. + {%- ifversion ghes %} + ![Agregar acciones a la lista de permitidos](/assets/images/help/organizations/actions-policy-allow-list.png) + {%- else %} + ![Agregar acciones a la lista de permitidos](/assets/images/enterprise/github-ae/organizations/actions-policy-allow-list.png) + {%- endif %} 1. Haz clic en **Save ** (guardar). {% endif %} @@ -71,7 +76,9 @@ Puedes inhabilitar todos los flujos de trabajo para una organización o configur {% ifversion fpt %} ## Configurar las aprobaciones requeridas para los flujos de trabajo desde las bifurcaciones pùblicas -{% data reusables.actions.workflow-run-approve-public-fork %} Puedes configurar este comportamiento para una organizaciòn utilizando el siguiente procedimiento. El modificar este ajuste anula el ajuste de configuraciòn a nivel empresarial. +{% data reusables.actions.workflow-run-approve-public-fork %} + +You can configure this behavior for an organization using the procedure below. El modificar este ajuste anula el ajuste de configuraciòn a nivel empresarial. {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} diff --git a/translations/es-ES/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md index 77256efc62..05d3df195a 100644 --- a/translations/es-ES/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md +++ b/translations/es-ES/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md @@ -14,7 +14,7 @@ topics: shortTitle: Restringir la creación de repositorios --- -Puedes elegir si los miembros pueden crear repositorios en tu organización o no. If you allow members to create repositories, you can choose which types of repositories members can create.{% ifversion fpt %} To allow members to create private repositories only, your organization must use {% data variables.product.prodname_ghe_cloud %}.{% endif %} For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." +Puedes elegir si los miembros pueden crear repositorios en tu organización o no. Si permites que los miembros creen repositorios, puedes elegir qué tipos de repositorios pueden crear.{% ifversion fpt %} Para permitir que los miembros creen únicamente repositorios privados, tu organización debe utilizar {% data variables.product.prodname_ghe_cloud %}.{% endif %} Para obtener más información, consulta la sección "[Acerca de los repositorios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)". Los propietarios de la organización siempre pueden crear cualquier tipo de repositorio. 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 8ac5508da3..5735e03f85 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 @@ -31,4 +31,4 @@ Puedes restringir la habilidad de cambiar la visibilidad de un repositorio para ## Leer más -- "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)" +- "[Acerca de los repositorios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)" diff --git a/translations/es-ES/content/organizations/managing-organization-settings/transferring-organization-ownership.md b/translations/es-ES/content/organizations/managing-organization-settings/transferring-organization-ownership.md index 237857839e..c7a37fc435 100644 --- a/translations/es-ES/content/organizations/managing-organization-settings/transferring-organization-ownership.md +++ b/translations/es-ES/content/organizations/managing-organization-settings/transferring-organization-ownership.md @@ -15,6 +15,13 @@ topics: shortTitle: Transferir la propiedad --- +{% ifversion fpt %} +{% note %} + +**Nota:**{% data reusables.enterprise-accounts.invite-organization %} + +{% endnote %}{% endif %} + 1. Si eres el único miembro con privilegios de *propietario*, otorga el rol de propietario a otro miembro de la organización. Para obtener más información, consulta "[Designar a un propietario de la organización](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization#appointing-an-organization-owner)". 2. Contáctacte con el propietario nuevo y asegúrate de que pueda [acceder a los parámetros de la organización](/articles/accessing-your-organization-s-settings). {% ifversion fpt %} diff --git a/translations/es-ES/content/organizations/managing-organization-settings/upgrading-to-the-corporate-terms-of-service.md b/translations/es-ES/content/organizations/managing-organization-settings/upgrading-to-the-corporate-terms-of-service.md index a9195eb917..196113ca70 100644 --- a/translations/es-ES/content/organizations/managing-organization-settings/upgrading-to-the-corporate-terms-of-service.md +++ b/translations/es-ES/content/organizations/managing-organization-settings/upgrading-to-the-corporate-terms-of-service.md @@ -14,11 +14,11 @@ shortTitle: Actualizar a los ToS corporativos Los Términos de servicio estándar son un acuerdo entre {% data variables.product.prodname_dotcom %} y tú como individualidad. Para suscribir un acuerdo con {% data variables.product.prodname_dotcom %} en nombre de una entidad, como una empresa, una organización sin fines de lucro o un grupo, los propietarios de la organización pueden subir de categoría a los Términos de servicio corporativos. -1. Navigate to your organization's settings and scroll to the **Terms of Service** box. ![scroll to the Terms of Service](/assets/images/help/organizations/account-settings-tos.png) +1. Navega a la configuración de tu organización y desplázate a la caja de **Términos de servicio**. ![desplazarse a los Términos de Servicio](/assets/images/help/organizations/account-settings-tos.png) -2. After you've read the Corporate Terms of Service, click **Sign corporate terms**. ![select 'Sign corporate terms'](/assets/images/help/organizations/button-sign-corporate-tos.png) +2. Después de que hayas leído los Términos de Servicio Corporativo, haz clic en **Firmar los términos corporativos**. ![seleccionar 'Firmar los términos corporativos'](/assets/images/help/organizations/button-sign-corporate-tos.png) -3. Select **Yes, I want to sign these terms on behalf of my business.** ![Casilla para firmar en nombre de tu empresa](/assets/images/help/organizations/sign-on-behalf-business.png) +3. Selecciona **Sí, quiero firmar estos términos en nombre de mi negocio.** ![Casilla para firmar en nombre de tu empresa](/assets/images/help/organizations/sign-on-behalf-business.png) 4. Escribe el nombre de la empresa, organización sin fines de lucro o grupo al que le pertenece la cuenta de la organización. Esta es la entidad que celebrará el acuerdo con {% data variables.product.prodname_dotcom %}. ![Campo del nombre de la empresa](/assets/images/help/organizations/business-name-field.png) 5. Para aceptar los Términos de servicio corporativos en nombre de tu entidad, haz clic en **Accept terms** (Aceptar términos). ![Botón Accept terms (Aceptar términos)](/assets/images/help/organizations/accept-terms-button.png) diff --git a/translations/es-ES/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md index 58d04ff8af..0504c44919 100644 --- a/translations/es-ES/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md +++ b/translations/es-ES/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md @@ -22,13 +22,13 @@ shortTitle: Verificar o aprobar un dominio ## Acerca de la verificación de dominios -Después de verificar la propiedad de los dominios de tu organización, se mostrará un distintivo "Verified" (Verificado) en el perfil de la organización. {% ifversion fpt %}If your organization is on {% data variables.product.prodname_ghe_cloud %} and has agreed to the Corporate Terms of Service, organization owners will be able to verify the identity of organization members by viewing each member's email address within the verified domain. For more information, see "[About your organization's profile page](/articles/about-your-organization-s-profile/)" and "Upgrading to the Corporate Terms of Service."{% endif %} +Después de verificar la propiedad de los dominios de tu organización, se mostrará un distintivo "Verified" (Verificado) en el perfil de la organización. {% ifversion fpt %}Si tu organización está en {% data variables.product.prodname_ghe_cloud %} y firmó el acuerdo de los Términos de Servicio Corporativo, los propietarios de la organización podrán verificar la identidad de los miembros organizacionales viendo sus direcciones de correo electrónico dentro del dominio verificado. Para obtener más información, consulta las secciones "[Acerca de la página de perfil de tu organización](/articles/about-your-organization-s-profile/)" y "Actualizar a los Términos de servicio corporativos".{% endif %} -{% ifversion fpt %}If your organization is owned by an enterprise account, a{% elsif ghes %}A{% endif %} "Verified" badge will display on your organization's profile for any domains verified for the enterprise account, in addition to any domains verified for the organization. Organization owners can view any domains that an enterprise owner has verified or approved, and edit the domains if the organization owner is also an enterprise owner. {% ifversion fpt %}For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)."{% endif %}{% ifversion ghes > 3.1 %}For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."{% endif %} +{% ifversion fpt %}Si tu organización le pertenece a una cuenta empresarial, se mostrará una{% elsif ghes %}Se mostrará una{% endif %} insignia de "Verificada" en el perfil de esta en todos los dominios verificados de la cuenta empresarial, adicionalmente a cualquier dominio verificado de la organización. Los propietarios de las organizaciones pueden ver cualquier dominio que haya verificado o aprobado el propietario de la empresa y pueden editar los dominios si el propietario de la organización es también un propietario de la empresa. {% ifversion fpt %}Para obtener más información, consulta la sección "[Verificar o aprobar un dominio para tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)".{% endif %}{% ifversion ghes > 3.1 %}Para obtener más información, consulta la sección "[Verificar o aprobar un dominio para tu empresa](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)".{% endif %} {% data reusables.organizations.verified-domains-details %} -{% ifversion fpt %}On {% data variables.product.prodname_ghe_cloud %}, after verifying ownership of your organization's domain, you can restrict email notifications for the organization to that domain. Para obtener más información, consulta la sección "[Restringir las notificaciones por correo electrónico para tu organización](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)". {% data reusables.enterprise.link-to-ghec-trial %}{% endif %} +{% ifversion fpt %}En {% data variables.product.prodname_ghe_cloud %}, después de verificar la propiedad del dominio de tu organización, puedes restringir las notificaciones por correo electrónico para la organización de dicho dominio. Para obtener más información, consulta la sección "[Restringir las notificaciones por correo electrónico para tu organización](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)". {% data reusables.enterprise.link-to-ghec-trial %}{% endif %} ## Acerca de la probación de dominios @@ -40,7 +40,7 @@ Después de que apruebas dominios para tu organización, puedes restringir las n Los propietarios de empresas no pueden ver qué miembros de las organizaciones o direcciones de correo electrónico reciben notificaciones dentro de los dominios aprobados. -Los propietarios de las empresas también pueden aprobar dominios adicionales para las organizaciones que pertenezcan a la empresa. {% ifversion fpt %}For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)."{% endif %}{% ifversion ghes > 3.1 %}For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."{% endif %} +Los propietarios de las empresas también pueden aprobar dominios adicionales para las organizaciones que pertenezcan a la empresa. {% ifversion fpt %}Para obtener más información, consulta la sección "[Verificar o aprobar un dominio para tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)".{% endif %}{% ifversion ghes > 3.1 %}Para obtener más información, consulta la sección "[Verificar o aprobar un dominio para tu empresa](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)".{% endif %} ## Verificar un dominio para tu organización diff --git a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md index 0d8dd6427a..7ac242972b 100644 --- a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md +++ b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md @@ -51,7 +51,7 @@ Los gerentes de facturación**no** pueden: {% note %} -**Note:** If your organization is managed using [Enterprise Accounts](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts) you will not be able to invite Billing Managers at the organization level. +**Nota:** Si tu organización se administra utilizando [Cuentas empresariales](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts) no podrás invitar a los gerentes de facturación a nivel organizacional. {% endnote %} diff --git a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md index 344bdfbb99..ae6656ffb1 100644 --- a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md +++ b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization.md @@ -26,7 +26,7 @@ Los miembros de la organización pueden tener roles de *propietario*{% ifversion - El acceso como **Miembros** es el rol por defecto para todo el resto. {% ifversion fpt %} -Some of the features listed below are limited to organizations using {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %} +Algunas de las características que se listan a continuación se limitan a las organizaciones que utilizan {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %} {% endif %} {% ifversion fpt %} @@ -135,9 +135,9 @@ Some of the features listed below are limited to organizations using {% data var ## {% data variables.product.prodname_github_app %} administadores -By default, only organization owners can manage the settings of {% data variables.product.prodname_github_apps %} owned by an organization. To allow additional users to manage {% data variables.product.prodname_github_apps %} owned by an organization, an owner can grant them {% data variables.product.prodname_github_app %} manager permissions. +Predeterminadamente, solo los propietarios de la organización pueden administrar la configuración de las {% data variables.product.prodname_github_apps %} que pertenezcan a una organización. Para permitir que más usuarios administren las {% data variables.product.prodname_github_apps %} que le pertenecen a una organización, un propietario puede otorgarles permisos de administrador de {% data variables.product.prodname_github_app %}. -When you designate a user as a {% data variables.product.prodname_github_app %} manager in your organization, you can grant them access to manage the settings of some or all {% data variables.product.prodname_github_apps %} owned by the organization. Para obtener más información, consulta: +Cuando designas un usuario como administrador de {% data variables.product.prodname_github_app %} en tu organización, puedes otorgarle acceso para administrar las configuraciones de algunas o todas las {% data variables.product.prodname_github_apps %} que le pertenecen a la organización. Para obtener más información, consulta: - "[Agregar administradores de GitHub App en tu organización](/articles/adding-github-app-managers-in-your-organization)" - "[Eliminar administradores de GitHub App de tu organización](/articles/removing-github-app-managers-from-your-organization)" diff --git a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md index 943a5a43a8..a3e4edbf40 100644 --- a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md +++ b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md @@ -13,13 +13,15 @@ topics: shortTitle: IAM con el SSO de SAML --- +{% data reusables.enterprise-accounts.emu-saml-note %} + ## Acerca de SAML SSO {% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.saml-accounts %} -Los propietarios de las organizaciones pueden requerir el SSO de SAML para una organización individual o para todas las organizaciones en una cuenta empresarial. For more information, see "[Enforcing SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account)." +Los propietarios de las organizaciones pueden requerir el SSO de SAML para una organización individual o para todas las organizaciones en una cuenta empresarial. Para obtener más información, consulta la sección "[Requerir el inicio de sesión único de SAML para las organizaciones de tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account)". {% data reusables.saml.saml-requires-ghec %} {% data reusables.enterprise.link-to-ghec-trial %} @@ -35,7 +37,7 @@ Para acceder a los recursos protegidos de tu organización tulizando la API y Gi La primera vez que un miembro utilice el SSO de SAML para acceder a tu organización, {% data variables.product.prodname_dotcom %} creará automáticamente un registro que vinculará a tu organización, la cuenta de {% data variables.product.prodname_dotcom %} del miembro y la cuenta del miembro en tu IdP. Puedes ver y retirar la identidad de SAML que se ha vinculado, activar sesiones, y autorizar las credenciales para los miembros de tu organización o cuenta empresarial. Para obtener más información, consulta la sección "[Visualizar y administrar un 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)" y [Visualizar y administrar un acceso de SAML de un usuario a tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise-account)". -Si los miembros ingresan con una sesión de SSO de SAML cuando crean un nuevo repositorio, la visibilidad predeterminada de dicho repositorio será privada. De lo contrario, la visibilidad predeterminada es pública. For more information on repository visibility, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." +Si los miembros ingresan con una sesión de SSO de SAML cuando crean un nuevo repositorio, la visibilidad predeterminada de dicho repositorio será privada. De lo contrario, la visibilidad predeterminada es pública. Para obtener más información sobre la visibilidad de los repositorios, consulta la sección "[Acerca de los repositorios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)". Los miembros de una organización también deben contar con una sesión activa de SAML para autorizar un {% data variables.product.prodname_oauth_app %}. Puedes decidir no llevar este requisito si contactas a {% data variables.contact.contact_support %}. {% data variables.product.product_name %} no recomienda que renuncies a este requisito, ya que expondrá a tu organización a un riesgo mayor de que se roben las cuentas y de que exista pérdida de datos. diff --git a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md index fd8359072b..7df90663e1 100644 --- a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md +++ b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md @@ -12,6 +12,8 @@ topics: - Teams --- +{% data reusables.enterprise-accounts.emu-scim-note %} + Si usas [SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on) en tu organización, puedes implementar SCIM para agregar, administrar y eliminar el acceso de los miembros de la organización a {% data variables.product.product_name %}. Por ejemplo, un administrador puede desaprovisionar a un miembro de la organización usando el SCIM y eliminar automáticamente el miembro de la organización. Si usas SAML SSO sin implementar SCIM, no tendrás un desaprovisionamiento automático. Cuando las sesiones de los miembros de la organización expiran una vez que su acceso ha sido eliminado del IdP, no se eliminan automáticamente de la organización. Los tokens autorizados otorgan acceso a la organización incluso una vez que las sesiones han expirado. Para eliminar el acceso, los administradores de la organización pueden eliminar de forma manual el token autorizado de la organización o automatizar su eliminación con SCIM. diff --git a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md index b224eb76bb..746bae2bf2 100644 --- a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md +++ b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md @@ -13,7 +13,7 @@ topics: shortTitle: Proveedor de identidad no disponible --- -Los administradores de la organización pueden usar [uno de los códigos de reuperación descargados o guardados](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes)para saltear un inicio de sesión único. You may have saved these to a password manager, such as [LastPass](https://lastpass.com/) or [1Password](https://1password.com/). +Los administradores de la organización pueden usar [uno de los códigos de reuperación descargados o guardados](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes)para saltear un inicio de sesión único. Puedes haber guardado esto en un administrador de contraseñas tal como [LastPass](https://lastpass.com/) o [1Password](https://1password.com/). {% note %} diff --git a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md index b63c8e2e17..0601a13ca4 100644 --- a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md +++ b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md @@ -13,9 +13,9 @@ topics: shortTitle: Conectar un IdP --- -When you enable SAML SSO for your {% data variables.product.product_name %} organization, you connect your identity provider (IdP) to your organization. Para obtener más información, consulta "[Habilitar y probar el inicio de sesión único para tu organización](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)". +Cuando habilitas el SSO de SAML para tu organización de {% data variables.product.product_name %}, conectas tu proveedor de identidad (IdP) a ella. Para obtener más información, consulta "[Habilitar y probar el inicio de sesión único para tu organización](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)". -You can find the SAML and SCIM implementation details for your IdP in the IdP's documentation. +Puedes encontrar los detalles de implementación de SAML y de SCIM para tu IdP en la documentación de este. - Active Directory Federation Services (AD FS) [SAML](https://docs.microsoft.com/windows-server/identity/active-directory-federation-services) - Azure Active Directory (Azure AD) [SAML](https://docs.microsoft.com/azure/active-directory/active-directory-saas-github-tutorial) y [SCIM](https://docs.microsoft.com/azure/active-directory/active-directory-saas-github-provisioning-tutorial) - Okta [SAML](http://saml-doc.okta.com/SAML_Docs/How-to-Configure-SAML-2.0-for-Github-com.html) y [SCIM](http://developer.okta.com/standards/SCIM/) diff --git a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md index a323776cb9..7142939c6a 100644 --- a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md +++ b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md @@ -14,7 +14,7 @@ topics: shortTitle: Descargar los códigos de recuperación de SAML --- -Los códigos de recuperación no se deben compartir ni distribuir. We recommend saving them with a password manager such as [LastPass](https://lastpass.com/) or [1Password](https://1password.com/). +Los códigos de recuperación no se deben compartir ni distribuir. Te recomendamos guardarlos con un administrador de contraseñas como [LastPass](https://lastpass.com/) o [1Password](https://1password.com/). {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} diff --git a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md index 9578ac5e3e..683f8de263 100644 --- a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md +++ b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md @@ -13,7 +13,7 @@ topics: shortTitle: Habilitar & probar el SSO de SAML --- -## About SAML single sign-on +## Acerca del inicio de sesión único de SAML Puedes habilitar SAML SSO (inicio de sesión único) en tu organización sin requerir que todos los miembros lo usen. Habilitar pero no exigir SAML SSO en tu organización puede facilitar la adopción de SAML SSO por parte de la organización. Una vez que la mayoría de los miembros usen SAML SSO, podrás exigirlo en toda la organización. @@ -25,9 +25,9 @@ Si habilitas pero no exiges SAML SSO, los miembros de la organización que elija {% data reusables.saml.saml-requires-ghec %} {% data reusables.enterprise.link-to-ghec-trial %} -Before your enforce SAML SSO in your organization, ensure that you've prepared the organization. Para obtener más información, consulta "[Preparación para exigir inicio de sesión único SAML en tu organización](/articles/preparing-to-enforce-saml-single-sign-on-in-your-organization)". +Antes de requerir el SSO de SAML en tu organización, asegúrate de que la hayas preparado. Para obtener más información, consulta "[Preparación para exigir inicio de sesión único SAML en tu organización](/articles/preparing-to-enforce-saml-single-sign-on-in-your-organization)". -For more information about the identity providers (IdPs) that {% data variables.product.company_short %} supports for SAML SSO, see "[Connecting your identity provider to your organization](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)." +Para obtener más información sobre los proveedores de identidad (IdP) que son compatibles con {% data variables.product.company_short %} para el SSO de SAML, consulta la sección "[Conectar tu proveedor de identidad a tu organización](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)". {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} diff --git a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md index f5dc4a160a..b8fd7f41a8 100644 --- a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md +++ b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md @@ -1,6 +1,6 @@ --- title: Hacer cumplir el inicio de sesión único de SAML para tu organización -intro: Organization owners and admins can enforce SAML SSO so that all organization members must authenticate via an identity provider (IdP). +intro: Los propietarios y los administradores de la organización pueden requerir el inicio de sesión único de SAML para que todos los miembros de la organización se tengan que autenticar a través de un proveedor de identidad (IdP). product: '{% data reusables.gated-features.saml-sso %}' redirect_from: - /articles/enforcing-saml-single-sign-on-for-your-organization @@ -13,19 +13,19 @@ topics: shortTitle: Hacer cumplir el inicio de sesión único de SAML --- -## About enforcement of SAML SSO for your organization +## Acerca de requerir el SSO de SAML en tu organización -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 user account to an identity on the IdP. Members can still access the organization's resources before authentication with your IdP. +Cuando habilitas el SSO de SAML, {% data variables.product.prodname_dotcom %} mostrará a los miembros que visitan los recursos de la organización en {% data variables.product.prodname_dotcom_the_website %} para autenticarse en tu IdP, lo cual vincula la cuenta de usuario del miembro a una identidad en el IdP. Los mimebros aún pueden acceder a los recursos organizacionales antes de autenticarse con tu IdP. -![Banner with prompt to authenticate via SAML SSO to access organization](/assets/images/help/saml/sso-has-been-enabled.png) +![Anuncio con mensaje para autenticarse mediante el SSO de SAML para acceder a una organización](/assets/images/help/saml/sso-has-been-enabled.png) -You can also enforce SAML SSO for your organization. {% data reusables.saml.when-you-enforce %} Enforcement removes any members and administrators who have not authenticated via your IdP from the organization. {% data variables.product.company_short %} sends an email notification to each removed user. +También puedes requerir el SSO de SAML para tu organización. {% data reusables.saml.when-you-enforce %} Cuando esto se requiere, se elimina de la organizacióna cualquier miembro y administrador que no se hayan autenticado mediante el IdP. {% data variables.product.company_short %} envía una notificación de correo electrónico a cada usuario eliminado. -Puedes restaurar los miembros de la organización una vez que realizas el inicio de sesión único sin problemas. Removed users' access privileges and settings are saved for three months and can be restored during this time frame. Para obtener más información, consulta "[Reinstalar un miembro antiguo de tu organización](/enterprise/{{ page.version }}/user/articles/reinstating-a-former-member-of-your-organization)". +Puedes restaurar los miembros de la organización una vez que realizas el inicio de sesión único sin problemas. Los ajustes y privilegios de acceso de los usuarios eliminados se guardan por tres meses y se pueden almacenar durante este periodo de tiempo. Para obtener más información, consulta "[Reinstalar un miembro antiguo de tu organización](/enterprise/{{ page.version }}/user/articles/reinstating-a-former-member-of-your-organization)". -Bots and service accounts that do not have external identities set up in your organization's IdP will also be removed when you enforce SAML SSO. For more information about bots and service accounts, see "[Managing bots and service accounts with SAML single sign-on](/articles/managing-bots-and-service-accounts-with-saml-single-sign-on)." +Los bots y cuentas de servicio que no tengan identidades externas configuradas en el IdP de tu organización también se eliminarán cuando requieras el SSO de SAML. Para obtener más información acerca de los bots y las cuentas de servicio, consulta la sección "[Administrar los bots y las cuentas de servicio con el inicio de sesión único de SAML](/articles/managing-bots-and-service-accounts-with-saml-single-sign-on)". -If your organization is owned by an enterprise account, requiring SAML for the enterprise account will override your organization-level SAML configuration and enforce SAML SSO for every organization in the enterprise. For more information, see "[Enforcing SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account)." +Si tu organización le pertenece a una cuenta empresarial, el requerir SAML para dicha cuenta anulará la configuración de SAML a nivel de organización y requerirá el SSO de SAML para todas las organizaciones que pertenezcan a la empresa. Para obtener más información, consulta la sección "[Requerir el inicio de sesión único de SAML para las organizaciones de tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account)". {% tip %} @@ -33,16 +33,16 @@ If your organization is owned by an enterprise account, requiring SAML for the e {% endtip %} -## Enforcing SAML SSO for your organization +## Requerir el SSO de SAML para tu organización -1. Enable and test SAML SSO for your organization, then authenticate with your IdP at least once. Para obtener más información, consulta "[Habilitar y probar el inicio de sesión único para tu organización](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)". -1. Prepare to enforce SAML SSO for your organization. Para obtener más información, consulta "[Preparación para exigir inicio de sesión único SAML en tu organización](/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization)". +1. Habilita y prueba el SSO de SAML para tu organización y luego autentícate con tu IdP por lo menos una vez. Para obtener más información, consulta "[Habilitar y probar el inicio de sesión único para tu organización](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)". +1. Prepárate para requerir el SSO de SAML para tu organización. Para obtener más información, consulta "[Preparación para exigir inicio de sesión único SAML en tu organización](/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization)". {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.security %} -1. Under "SAML single sign-on", select **Require SAML SSO authentication for all members of the _ORGANIZATION_ organization**. !["Require SAML SSO authentication" checkbox](/assets/images/help/saml/require-saml-sso-authentication.png) -1. If any organization members have not authenticated via your IdP, {% data variables.product.company_short %} displays the members. If you enforce SAML SSO, {% data variables.product.company_short %} will remove the members from the organization. Review the warning and click **Remove members and require SAML single sign-on**. !["Confirm SAML SSO enforcement" dialog with list of members to remove from organization](/assets/images/help/saml/confirm-saml-sso-enforcement.png) -1. Under "Single sign-on recovery codes", review your recovery codes. Store the recovery codes in a safe location like a password manager. +1. Debajo de "Inicio de sesión único de SAML", selecciona **Requerir la autenticación con el SSO de SAML para todos los miembros de la organización _ORGANIZATION_**. ![Casilla de verificación de "Requerir autenticación con el SSO de SAML"](/assets/images/help/saml/require-saml-sso-authentication.png) +1. Si cualquiera de los miembros de la organización no se autentica a través de tu IdP, {% data variables.product.company_short %} lo mostrará. Si requieres el SSO de SAML, {% data variables.product.company_short %} eliminará a los miembros de la organización. Revisa la advertencia y haz clic en **Eliminar a los miembros y requerir el inicio de sesión único de SAML**. ![Diálogo de "Confirmar que se requiere el SSO de SAML" con lista de miembros a eliminar de la organización](/assets/images/help/saml/confirm-saml-sso-enforcement.png) +1. Debajo de "Códigos de recuperación del inicio de sesión único", revisa tus códigos de recuperación. Almacena los códigos de recuperación en una ubicación segura, como un administrador de contraseñas. ## Leer más diff --git a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md index dcb5e0bd5e..eaa0644dfd 100644 --- a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md +++ b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md @@ -17,6 +17,8 @@ topics: shortTitle: Administrar la sincronización de equipos --- +{% data reusables.enterprise-accounts.emu-scim-note %} + {% data reusables.gated-features.okta-team-sync %} ## Acerca de la sincronización de equipo @@ -31,6 +33,8 @@ Puedes habilitar la sincronización de equipos entre tu IdP y {% data variables. También puedes habilitar la sincronización de equipos para las organizaciones que pertenezcan a tu cuenta empresarial. Para obtener más información, consulta la sección "[Requerir los parámetros de seguridad en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account)". +{% data reusables.enterprise-accounts.team-sync-override %} + {% data reusables.identity-and-permissions.team-sync-usage-limits %} ## Habilitar la sincronización de equipo diff --git a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md index 6430cbd3eb..e26b90cb41 100644 --- a/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md +++ b/translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md @@ -13,14 +13,14 @@ topics: shortTitle: Prepararse para requerir el SSO de SAML --- -{% data reusables.saml.when-you-enforce %} Before enforcing SAML SSO in your organization, you should review organization membership, enable SAML SSO, and review organization members' SAML access. For more information, see the following. +{% data reusables.saml.when-you-enforce %} Antes de requerir el SSO de SAML en tu organización, debes revisar la membrecía de la misma, habilitar el SSO de SAML y revisar el acceso de SAML de los miembros de esta. Para obtener más información, consulta lo siguiente. -| Task | Más información | +| Tarea | Más información | |:--------------------------------------------------------------------------------------------------------- |:------------------------- | -| Add or remove members from your organization |
    • "[Inviting users to join your organization](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)"
    • "[Removing a member from your organization](/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization)"
    | -| Connect your IdP to your organization by enabling SAML SSO |
    • "[Connecting your identity provider to your organization](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)"
    • "[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)"
    | -| Asegurar que los miembros de tu organización se hayan registrado y hayan vinculado sus cuentas con tu IdP |
    • "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)"
    | +| Agregar o eliminar miembros de tu organización |
    • "[Invitar a los usuarios para que se unan a tu organización](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)"
    • "[Eliminar a un miembro de tu organización](/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization)"
    | +| Conecta tu IdP a tu organización habilitando el SSO de SAML |
    • "[Conectar tu proveedor de identidad a tu organización](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)"
    • "[Habilitar y probar el inicio de sesión único de SAML para tu organización](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)"
    | +| Asegurar que los miembros de tu organización se hayan registrado y hayan vinculado sus cuentas con tu IdP |
    • "[Visualizar y administrar el acceso de SAML de un miembro en tu organización](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)"
    | -After you finish these tasks, you can enforce SAML SSO for your organization. Para obtener más información, consulta la sección "[Requerir el inicio de sesión único de SAML en tu organización](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)". +Después de que termines con estas tareas, puedes requerir el SSO de SAML en tu organización. Para obtener más información, consulta la sección "[Requerir el inicio de sesión único de SAML en tu organización](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)". {% data reusables.saml.outside-collaborators-exemption %} diff --git a/translations/es-ES/content/organizations/organizing-members-into-teams/creating-a-team.md b/translations/es-ES/content/organizations/organizing-members-into-teams/creating-a-team.md index 3efe7e00fb..8e5011f104 100644 --- a/translations/es-ES/content/organizations/organizing-members-into-teams/creating-a-team.md +++ b/translations/es-ES/content/organizations/organizing-members-into-teams/creating-a-team.md @@ -25,11 +25,13 @@ Solo los propietarios y mantenedores de la organización en un equipo padre pued {% data reusables.organizations.team_description %} {% data reusables.organizations.create-team-choose-parent %} {% ifversion fpt %} -1. Como opción, si tu cuenta organizacional o empresarial utiliza la sincronización de equipos, para conectar un grupo de proveedor de identidad a tu equipo, utiliza el menú desplegable "Grupos de Proveedor de Identidad", y selecciona hasta 5 grupos. Para obtener más información, consulta la sección "[Sincronizar a un equipo con un grupo de proveedor de identidad](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)". ![Menú desplegable para elegir los grupos de proveedor de identidad](/assets/images/help/teams/choose-an-idp-group.png) +1. Opcionalmente, si tu cuenta organizacional o empresarial utiliza la sincronización de equipos o si tu empresa utiliza {% data variables.product.prodname_emus %}, conecta un grupo de proveedor de identidad a tu equipo. + * Si tu empresa utiliza {% data variables.product.prodname_emus %}, utiliza el menú desplegable de "Grupos de Proveedor de Identidad" y selecciona un solo grupo de proveedor de identidad para conectarlo al equipo nuevo. Para obtener más información, consulta la sección "[Administrar las membrecías de equipo con grupos de proveedor de identidad](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)". + * Si tu cuenta organizacional o empresarial utiliza la sincronización de equipos, utiliza el menú desplegable de "Grupo de Proveedor de Identidad" y selecciona hasta cinco grupos de proveedor de identidad para conectar al equipo nuevo. Para obtener más información, consulta la sección "[Sincronizar a un equipo con un grupo de proveedor de identidad](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)". ![Menú desplegable para elegir los grupos de proveedor de identidad](/assets/images/help/teams/choose-an-idp-group.png) {% endif %} {% data reusables.organizations.team_visibility %} {% data reusables.organizations.create_team %} -9. También puede [darle acceso al equipo a los repositorios de la organización](/articles/managing-team-access-to-an-organization-repository). +1. También puede [darle acceso al equipo a los repositorios de la organización](/articles/managing-team-access-to-an-organization-repository). ## Leer más diff --git a/translations/es-ES/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md b/translations/es-ES/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md index a5501cb4b5..878fa5fb76 100644 --- a/translations/es-ES/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md +++ b/translations/es-ES/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md @@ -22,7 +22,7 @@ Al utilizar tareas de revisión de código, cada que se pida a tu equipo revisar Cuando se les solicita automáticamente una revisión a los propietarios del código, el equipo se eliminará y reemplazará con los individuos de todos modos. Las aprobaciones individuales no satisfacen el requisito de aprobación del propietario del código en una rama protegida. Para obtener más información, consulta "[Acerca de los propietarios del código](/github/creating-cloning-and-archiving-repositories/about-code-owners)." {% ifversion fpt %} -To further enhance your team's collaboration abilities, you can upgrade to {% data variables.product.prodname_ghe_cloud %}, which includes features like protected branches and code owners on private repositories. {% data reusables.enterprise.link-to-ghec-trial %} +Para ampliar aún más las capacidades de colaboración de tu equipo, puedes mejorar a {% data variables.product.prodname_ghe_cloud %}, el cual incluye características como ramas protegidas y propietarios de código en repositorios privados. {% data reusables.enterprise.link-to-ghec-trial %} {% endif %} ## Rutear algoritmos @@ -33,7 +33,7 @@ El algoritmo de round robin (turno rotativo) escoge revisores basándose en qui El algoritmo de balanceo de carga escoge a los revisores basándose en la cantidad total de solicitudes de revisión recientes para cada miembro, y considera el número de revisiones pendientes para cada uno de ellos. El algoritmo de balanceo de carga intenta asegurarse de que cada miembro del equipo revise una cantidad igual de solicitudes de extracción en cualquier periodo de 30 días. -Any team members that have set their status to "Busy" will not be selected for review. If all team members are busy, the pull request will remain assigned to the team itself. For more information about user statuses, see "[Setting a status](/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile#setting-a-status)." +Cualquier miembro del equipo que haya configurado su estado como "Ocupado" no podrá seleccionarse para revisión. Si todos los miembros del equipo están ocupados, la solicitud de cambios seguirá estando asignada al equipo mismo. Para obtener más información acerca de los estados de usuario, consulta la sección "[Configurar un estado](/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile#setting-a-status)". ## Configurar una tarea de revisión de código {% data reusables.profile.access_org %} @@ -45,8 +45,11 @@ Any team members that have set their status to "Busy" will not be selected for r 7. Debajo de "¿Cuántos miembros del equipo deberán asignarse para revisión?", utiliza el menú desplegable y elije el número de revisores que se asignarán a cada solicitud de extracción. ![Menú desplegable de cantidad de revisores](/assets/images/help/teams/review-assignment-number.png) 8. Debajo de "Algoritmo de ruteo", utiliza el menú desplegable y elige qué algoritmo quieres utilizar. Para obtener más información, consulta la sección "[Algoritmos de ruteo](#routing-algorithms)". ![Menú desplegable de algoritmo de ruteo](/assets/images/help/teams/review-assignment-algorithm.png) 9. De manera opcional, para siempre omitir miembros específicos del equipo, selecciona **Nunca asignar ciertos miembros del equipo**. Después, selecciona uno o más miembros del equipo que quieras omitir siempre. ![Menú desplegable y casilla de "nunca asignar ciertos miembros del equipo"](/assets/images/help/teams/review-assignment-skip-members.png) -10. De manera opcional, para notificar únicamente a los miembros del equipo que se escogieron por tarea de revisión en cada solicitud revisión de código, selecciona **No notificar a todo el equipo si se asignan miembros específicos** debajo de "Notificaciones". ![Notificaciones de tarea de revisión de código](/assets/images/help/teams/review-assignment-notifications.png) -11. Haz clic en **Guardar cambios**. +10. Opcionalmente, para notificar solo a los miembros del equipo que eligió la tarea de revisión de código para cada solicitud de revisión de cambios, debajo de "Notificaciones", selecciona **no notificar a todo el equipo si se asignaron miembros específicos.**![Code review assignment notifications](/assets/images/help/teams/review-assignment-notifications.png){% ifversion fpt or ghae or ghes > 3.2 %} +11. Opcionalmente, para incluir a los miembros de los equipos hijos como revisores potenciales al asignar solicitudes, selecciona **Miembros del equipo hijo**. +12. Opcionalmente, para contar a cualquier miembro cuya revisión se haya solicitado contra la cantidad total de miembros a asignar, selecciona **Contar las solicitudes existentes**. +13. Opcionalmente, para eliminar la solicitud de revisión del equipo cuando se asignan miembros de este, selecciona **Solicitud de revisión de equipo**.{% endif %} +14. Haz clic en **Guardar cambios**. ## Inhabilitar una tarea de revisión de código {% data reusables.profile.access_org %} diff --git a/translations/es-ES/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/es-ES/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md index 0ed9e0ba49..4a6f0913ad 100644 --- a/translations/es-ES/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md +++ b/translations/es-ES/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md @@ -16,6 +16,8 @@ shortTitle: Sincronizar con un IdP {% data reusables.gated-features.okta-team-sync %} +{% data reusables.enterprise-accounts.emu-scim-note %} + ## Acerca de la sincronización de equipo {% data reusables.identity-and-permissions.about-team-sync %} @@ -26,6 +28,8 @@ shortTitle: Sincronizar con un IdP Una vez que un equipo de {% data variables.product.prodname_dotcom %} se conecta a un grupo de IdP, tu administrador de IdP debe hacer cambios en la membrecía del equipo a través del proveedor de identidad. No puedes administrar las membrecías de equipo en {% data variables.product.product_name %}{% ifversion fpt %} ni utilizando la API{% endif %}. +{% ifversion fpt %}{% data reusables.enterprise-accounts.team-sync-override %}{% endif %} + {% ifversion fpt %} Todos los cambios a la membrecía de equipo que se hagan con tu IdP aparecerán en la bitácora de auditoría en {% data variables.product.product_name %} como cambios que realiza el bot de sincronización de equipos. Tu IdP enviará datos de la membresía de equipo a {% data variables.product.prodname_dotcom %} una vez por hora. Conectar un equipo a un grupo IdP puede eliminar a algunos miembros del equipo. Para obtener más información, consulta "[Requisitos para los miembros de los equipos sincronizados](#requirements-for-members-of-synchronized-teams)." {% endif %} @@ -52,9 +56,7 @@ Los equipos o miembros del grupo existentes que no cumplan con estos criterios s Puedes volver a agregar automáticamente a aquellos miembros del equipo que hayas eliminado una vez que se autentiquen en la cuenta empresarial u organizacional utilizando el SSO y así se migren al grupo de IdP conectado. -Para evitar eliminar miembros del equipo accidentalmente, te recomendamos requerir el SSO de SAML en tu cuenta organizacional o empresarial mediante la creación de nuevos equipos para sincronizar datos de membrecías y revisar la membrecía del grupo de IdP antes de que sincronices a los equipos existentes. For more information, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)" and "[Enforcing SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account)." - -Si tu organización pertenece a una cuenta empresarial, habilitar la sincronización de equipos para la cuenta empresarial anulará la configuración de sincronización de equipos a nivel organizacional. Para obtener más información, consulta la sección "[Administrar la sincronización de equipos para las organizaciones en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)". +Para evitar eliminar miembros del equipo accidentalmente, te recomendamos requerir el SSO de SAML en tu cuenta organizacional o empresarial mediante la creación de nuevos equipos para sincronizar datos de membrecías y revisar la membrecía del grupo de IdP antes de que sincronices a los equipos existentes. Para obtener más información, consulta las secciones "[Requerir el inicio de sesión único de SAML para tu organización](/articles/enforcing-saml-single-sign-on-for-your-organization)" y "[Requerir el inicio de sesión único de SAML para las organizaciones en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account)". {% endif %} diff --git a/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md b/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md index c7467fd4fe..e8d0ceae23 100644 --- a/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md +++ b/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md @@ -1,6 +1,6 @@ --- title: Acerca de las restricciones de acceso a App OAuth -intro: 'Organizations can choose which {% data variables.product.prodname_oauth_apps %} have access to their repositories and other resources by enabling {% data variables.product.prodname_oauth_app %} access restrictions.' +intro: 'Las organizaciones pueden elegir qué {% data variables.product.prodname_oauth_apps %} tienen acceso a sus repositorios y otros recursos al activar las restricciones de acceso a {% data variables.product.prodname_oauth_app %}.' redirect_from: - /articles/about-third-party-application-restrictions/ - /articles/about-oauth-app-access-restrictions @@ -15,7 +15,7 @@ shortTitle: Acceso a las Apps de OAuth ## Acerca de las restricciones de acceso a App OAuth -Cuando las restricciones de acceso a {% data variables.product.prodname_oauth_app %} están activadas, los miembros de la organización no pueden autorizar el acceso de {% data variables.product.prodname_oauth_app %} a los recursos de la organización. Organization members can request owner approval for {% data variables.product.prodname_oauth_apps %} they'd like to use, and organization owners receive a notification of pending requests. +Cuando las restricciones de acceso a {% data variables.product.prodname_oauth_app %} están activadas, los miembros de la organización no pueden autorizar el acceso de {% data variables.product.prodname_oauth_app %} a los recursos de la organización. Los miembros de la organización pueden solicitar la aprobación de los propietarios para las {% data variables.product.prodname_oauth_apps %} que quieran usar y los propietarios de la organización reciben una notificación de solicitudes pendientes. {% data reusables.organizations.oauth_app_restrictions_default %} @@ -25,18 +25,18 @@ Cuando las restricciones de acceso a {% data variables.product.prodname_oauth_ap {% endtip %} -To further protect your organization's resources, you can upgrade to {% data variables.product.prodname_ghe_cloud %}, which includes security features like SAML single sign-on. {% data reusables.enterprise.link-to-ghec-trial %} +Para proteger los recursos de tu organización aún más, puedes mejorar a {% data variables.product.prodname_ghe_cloud %}, lo cual incluye características de seguridad como el inicio de sesión único de SAML. {% data reusables.enterprise.link-to-ghec-trial %} ## Configurar las restricciones de acceso a {% data variables.product.prodname_oauth_app %} Cuando el propietario de una organización configura las restricciones de acceso a {% data variables.product.prodname_oauth_app %} por primera vez: - Las **Aplicaciones que son propiedad de la organización** automáticamente ganan acceso a los recursos de la organización. -- **{% data variables.product.prodname_oauth_apps %}** immediately lose access to the organization's resources. +- Las **{% data variables.product.prodname_oauth_apps %}s** inmediatamente pierden acceso a los recursos de la organización. - Las **claves SSH creadas antes de febrero de 2014** inmediatamente pierden acceso a los recursos de la organización (esto incluye claves de implementación y usuarios). -- **SSH keys created by {% data variables.product.prodname_oauth_apps %} during or after February 2014** immediately lose access to the organization's resources. -- **Hook deliveries from private organization repositories** will no longer be sent to unapproved {% data variables.product.prodname_oauth_apps %}. -- **API access** to private organization resources is not available for unapproved {% data variables.product.prodname_oauth_apps %}. Además, no hay acciones de creación, actualización ni eliminación privilegiadas en los recursos públicos de la organización. +- Las **Llaves SSH que creen las {% data variables.product.prodname_oauth_apps %} durante o después de febrero de 2014** perdieron acceso a los recursos de la organización inmediatamente. +- Las **entregas de gancho de los repositorios privados de una organización** ya no se enviarán a {% data variables.product.prodname_oauth_apps %} no aprobadas. +- El **acceso de la API** a los recursos privados de la organización no está disponible para las {% data variables.product.prodname_oauth_apps %} no aprobadas. Además, no hay acciones de creación, actualización ni eliminación privilegiadas en los recursos públicos de la organización. - Los **enlaces creados por los usuarios y los enlaces creados antes de mayo de 2014** no se verán afectados. - Las **bifurcaciones privadas de los repositorios que son propiedad de una organización** están sujetas a las restricciones de acceso de la organización. @@ -57,9 +57,9 @@ Si una organización desactiva las restricciones de aplicación de acceso de {% ## Leer más - "[Activar las restricciones de acceso de {% data variables.product.prodname_oauth_app %} para tu organización](/articles/enabling-oauth-app-access-restrictions-for-your-organization)" -- "[Approving {% data variables.product.prodname_oauth_apps %} for your organization](/articles/approving-oauth-apps-for-your-organization)" +- "[Aprobar las {% data variables.product.prodname_oauth_apps %} para tu organización ](/articles/approving-oauth-apps-for-your-organization)" - "[Revisar las integraciones instaladas de tu organización](/articles/reviewing-your-organization-s-installed-integrations)" - "[Denegar el acceso a una {% data variables.product.prodname_oauth_app %} anteriormente aprobada para tu organización](/articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization)" - "[Desactivar las restricciones de acceso de {% data variables.product.prodname_oauth_app %} para tu organización](/articles/disabling-oauth-app-access-restrictions-for-your-organization)" -- "[Requesting organization approval for {% data variables.product.prodname_oauth_apps %}](/articles/requesting-organization-approval-for-oauth-apps)" +- "[Solicitar la aprobación de una organización para las {% data variables.product.prodname_oauth_apps %}](/articles/requesting-organization-approval-for-oauth-apps)" - "[Autorizar las {% data variables.product.prodname_oauth_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps)" diff --git a/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md b/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md index 905010ab8a..5c8b6fba3a 100644 --- a/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md +++ b/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md @@ -1,6 +1,6 @@ --- title: Inhabilitar las restricciones de acceso de las App OAuth para tu organización -intro: 'Organization owners can disable restrictions on the {% data variables.product.prodname_oauth_apps %} that have access to the organization''s resources.' +intro: 'Los propietarios de la organización pueden inhabilitar las restricciones de las {% data variables.product.prodname_oauth_apps %} que tienen acceso a los recursos de la organización.' redirect_from: - /articles/disabling-third-party-application-restrictions-for-your-organization/ - /articles/disabling-oauth-app-access-restrictions-for-your-organization diff --git a/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md b/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md index 5d5b52795d..f304a1d8e2 100644 --- a/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md +++ b/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md @@ -1,6 +1,6 @@ --- title: Habilitar las restricciones de acceso de las App OAuth para tu organización -intro: 'Organization owners can enable {% data variables.product.prodname_oauth_app %} access restrictions to prevent untrusted apps from accessing the organization''s resources while allowing organization members to use {% data variables.product.prodname_oauth_apps %} for their personal accounts.' +intro: 'Los propietarios de la organización pueden habilitar las restricciones de acceso a {% data variables.product.prodname_oauth_app %} para prevenir que las aplicaciones no confiables accedan a los recursos organizacionales mientras permiten que los miembros de dicha organización utilicen las {% data variables.product.prodname_oauth_apps %} para sus cuentas personales.' redirect_from: - /articles/enabling-third-party-application-restrictions-for-your-organization/ - /articles/enabling-oauth-app-access-restrictions-for-your-organization @@ -18,7 +18,7 @@ shortTitle: Habilitar las Apps de OAuth {% warning %} **Advertencias**: -- Enabling {% data variables.product.prodname_oauth_app %} access restrictions will revoke organization access for all previously authorized {% data variables.product.prodname_oauth_apps %} and SSH keys. Para obtener más información, consulta "[Acerca de las restricciones de acceso a {% data variables.product.prodname_oauth_app %}](/articles/about-oauth-app-access-restrictions)". +- Habilitar las restricciones de acceso de las {% data variables.product.prodname_oauth_app %} revocará los accesos de la organización a todas las {% data variables.product.prodname_oauth_apps %} y claves SSH que hayan sido previamente autorizadas. Para obtener más información, consulta "[Acerca de las restricciones de acceso a {% data variables.product.prodname_oauth_app %}](/articles/about-oauth-app-access-restrictions)". - Una vez que hayas configurado las restricciones de acceso de {% data variables.product.prodname_oauth_app %}, asegúrate de autorizar nuevamente toda {% data variables.product.prodname_oauth_app %} que requiera acceso a los datos privados de la organización de manera continua. Todos los miembros de la organización deberán crear nuevas claves SSH y la organización deberá crear nuevas llaves de implementación, según sea necesario. - Cuando se habilitan las restricciones de acceso de {% data variables.product.prodname_oauth_app %}, las aplicaciones pueden usar un token de OAuth para acceder a información acerca de transacciones en {% data variables.product.prodname_marketplace %}. diff --git a/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/index.md b/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/index.md index 2f040cacc5..15700b27be 100644 --- a/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/index.md +++ b/translations/es-ES/content/organizations/restricting-access-to-your-organizations-data/index.md @@ -1,6 +1,6 @@ --- title: Restringir el acceso a los datos de tu organización -intro: '{% data variables.product.prodname_oauth_app %} las restricciones de acceso le permiten a los propietarios de la organización que restrinjan el acceso de una app no confiable a los datos de la organización. Organization members can then use {% data variables.product.prodname_oauth_apps %} for their personal user accounts while keeping organization data safe.' +intro: '{% data variables.product.prodname_oauth_app %} las restricciones de acceso le permiten a los propietarios de la organización que restrinjan el acceso de una app no confiable a los datos de la organización. Los miembros de la organización pueden utilizar las {% data variables.product.prodname_oauth_apps %} para sus cuentas de usuario personales mientras mantienen los datos organizacionales seguros.' redirect_from: - /articles/restricting-access-to-your-organization-s-data - /articles/restricting-access-to-your-organizations-data diff --git a/translations/es-ES/content/packages/learn-github-packages/deleting-and-restoring-a-package.md b/translations/es-ES/content/packages/learn-github-packages/deleting-and-restoring-a-package.md index fd2d0a27f6..484f0f3d9d 100644 --- a/translations/es-ES/content/packages/learn-github-packages/deleting-and-restoring-a-package.md +++ b/translations/es-ES/content/packages/learn-github-packages/deleting-and-restoring-a-package.md @@ -172,9 +172,9 @@ Puedes restablecer un paquete o versión que hayas borrado si: Por ejemplo, si borraste un paquete de rubygem con el nombre `octo-package` que tuviera un alcance para el repositorio `octo-repo-owner/octo-repo`, entonces solo podrías restablecer el paquete si su designador de nombre `rubygem.pkg.github.com/octo-repo-owner/octo-repo/octo-package` estuviera disponible todavía, suponiendo que no hayan pasado 30 días. También debes de cumplir con estos requisitos de permisos: - - For repository-scoped packages: You have admin permissions to the repository that owns the deleted package.{% ifversion fpt %} + - Para los paquetes con alcance de repositorio: Tienes permisos de administrador en el repositorio al que pertenece el paquete que se borró.{% ifversion fpt %} - Para los paquetes con alcance de cuenta de usuario: El paquete borrado pertenece a tu cuenta de usuario. - - For organization-scoped packages: You have admin permissions to the deleted package in the organization that owns the package.{% endif %} + - Para los paquetes con alcance de organización: Tienes permisos de administrador en el paquete que se borró en la organización a la cual este pertenece.{% endif %} Para obtener más información, consulta la sección "[Permisos necesarios](#required-permissions-to-delete-or-restore-a-package)". @@ -182,7 +182,7 @@ Una vez que se restablezca el paquete, este utilizará el designador de nombre q ### Restablecer un paquete en una organización -You can restore a deleted package through your organization account settings, as long as the package was in one of your repositories{% ifversion fpt %} or had granular permissions and was scoped to your organization account{% endif %}. +Puedes restablecer un paquete borrado a través de la configuración de cuenta de tu organización siempre y cuando dicho paquete estuviera en uno de tus repositorios{% ifversion fpt %} o tuviera permisos granulares y tuviera el alcance de tu cuenta de organización{% endif %}. Para revisar quién puede restablecer un paquete en una organización, consulta la sección "[Permisos necesarios](#required-permissions-to-delete-or-restore-a-package)". diff --git a/translations/es-ES/content/packages/learn-github-packages/installing-a-package.md b/translations/es-ES/content/packages/learn-github-packages/installing-a-package.md index 07c3b50013..b0c8a51940 100644 --- a/translations/es-ES/content/packages/learn-github-packages/installing-a-package.md +++ b/translations/es-ES/content/packages/learn-github-packages/installing-a-package.md @@ -18,7 +18,7 @@ versions: ## Acerca de la instalación del paquete -Puedes buscar {% data variables.product.product_name %} para encontrar los paquetes en {% data variables.product.prodname_registry %} que puedes instalar en tu propio proyecto. Para obtener más información, consulta "[Buscar {% data variables.product.prodname_registry %} para paquetes](/github/searching-for-information-on-github/searching-for-packages)". +Puedes buscar {% data variables.product.product_name %} para encontrar los paquetes en {% data variables.product.prodname_registry %} que puedes instalar en tu propio proyecto. Para obtener más información, consulta "[Buscar {% data variables.product.prodname_registry %} para paquetes](/search-github/searching-on-github/searching-for-packages)". Una vez que encuentres un paquete, puedes leer las instrucciones de la descripción y la instalación y el uso del paquete en la página del paquete. diff --git a/translations/es-ES/content/packages/learn-github-packages/viewing-packages.md b/translations/es-ES/content/packages/learn-github-packages/viewing-packages.md index 8608cbc3ac..eb8285d3ae 100644 --- a/translations/es-ES/content/packages/learn-github-packages/viewing-packages.md +++ b/translations/es-ES/content/packages/learn-github-packages/viewing-packages.md @@ -64,4 +64,4 @@ Puedes encontrar y ver cualquier paquete que hayas publicado en cualquier organi ## Leer más -- "[Buscar paquetes](/github/searching-for-information-on-github/searching-for-packages)" +- "[Buscar paquetes](/search-github/searching-on-github/searching-for-packages)" diff --git a/translations/es-ES/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md b/translations/es-ES/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md index a5ad7e2b36..7c93bed553 100644 --- a/translations/es-ES/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md +++ b/translations/es-ES/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md @@ -15,8 +15,6 @@ shortTitle: Publicar & instalar con acciones {% data reusables.package_registry.packages-ghes-release-stage %} {% data reusables.package_registry.packages-ghae-release-stage %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## Acerca de {% data variables.product.prodname_registry %} con {% data variables.product.prodname_actions %} diff --git a/translations/es-ES/content/packages/quickstart.md b/translations/es-ES/content/packages/quickstart.md index 26083c29f9..23642f0853 100644 --- a/translations/es-ES/content/packages/quickstart.md +++ b/translations/es-ES/content/packages/quickstart.md @@ -10,8 +10,6 @@ shortTitle: Inicio Rápido --- {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## Introducción diff --git a/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md b/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md index 56befd8e64..fceed63352 100644 --- a/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md +++ b/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md @@ -165,9 +165,9 @@ subprojects { $ gradle publish ``` -## Using a published package +## Utilizar un paquete publicado -To use a published package from {% data variables.product.prodname_registry %}, add the package as a dependency and add the repository to your project. Para obtener más información, consulta "[Declarar dependencias](https://docs.gradle.org/current/userguide/declaring_dependencies.html)" en la documentación de Gradle. +Para utiliza run paquete publicado del {% data variables.product.prodname_registry %}, agrégalo como una dependencia y luego agrega el repositorio a tu proyecto. Para obtener más información, consulta "[Declarar dependencias](https://docs.gradle.org/current/userguide/declaring_dependencies.html)" en la documentación de Gradle. {% data reusables.package_registry.authenticate-step %} 2. Agrega las dependencias del paquete a tu archivo *build.gradle* (Gradle Groovy) o archivo *build.gradle.kts* (Kotlin DSL). @@ -185,7 +185,7 @@ To use a published package from {% data variables.product.prodname_registry %}, } ``` -3. Add the repository to your *build.gradle* file (Gradle Groovy) or *build.gradle.kts* file (Kotlin DSL) file. +3. Agrega el repositorio a tu archivo de *build.gradle* (Gradel Groovy) o a tu archivo de *build.gradle.kts* (Kotlin DSL). Ejemplo utilizando Gradle Groovy: ```shell diff --git a/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md b/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md index ccb43edbc1..fa81a6d19b 100644 --- a/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md +++ b/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md @@ -160,7 +160,11 @@ Puedes instalar paquetes desde {% data variables.product.prodname_registry %} al Por defecto, puedes agregar paquetes de una organización. Para obtener más información, consulta la sección "[Instalar paquetes de otras organizaciones](#installing-packages-from-other-organizations)". -También debes agregar el archivo *.npmrc* a tu proyecto por lo que todas las solicitudes de instalación de paquetes pasarán por {% data variables.product.prodname_registry %}. Cuando enrutas todas las solicitudes de paquete a través de {% data variables.product.prodname_registry %}, puedes usar paquetes con alcance definido y sin alcance definido de *npmjs.com*. Para obtener más información, consulta "[npm-scope](https://docs.npmjs.com/misc/scope)" en la documentación de npm. +También necesitas agregar el archivo *.npmrc* a tu proyecto para que todas las solicitudes para instalar paquetes se {% ifversion ghae %}enruten a{% else %}pasen por{% endif %} el {% data variables.product.prodname_registry %}. {% ifversion fpt or ghes > 2.21 %}Cuando enrutas todas las solicitudes de paquetes a través del {% data variables.product.prodname_registry %}, puedes utilizar tanto los paquetes dentro como fuera del alcance de *npmjs.org*. Para obtener más información, consulta la sección de "[npm-scope](https://docs.npmjs.com/misc/scope)" en la documentación de npm.{% endif %} + +{% ifversion ghae %} +Predeterminadamente, solo puedes utilizar paquetes de npm hospedados en tu empresa y no podrás utilizar paquetes fuera del alcance. Para obtener más información sobre el alcance de los paquetes, consulta la sección de "[npm-scope](https://docs.npmjs.com/misc/scope)" en la documentación de npm. En caso de que se requiera, se puede habilitar el {% data variables.product.prodname_dotcom %} en un proxy de nivel superior como npmjs.org. Una vez que se habilite un proxy de nivel superior, si un paquete que se haya solicitado no se encuentra en tu empresa, el {% data variables.product.prodname_registry %} hará una solicitud de proxy a npmjs.org. +{% endif %} {% data reusables.package_registry.authenticate-step %} {% data reusables.package_registry.create-npmrc-owner-step %} diff --git a/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md b/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md index 882758bf9e..cd802368e5 100644 --- a/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md +++ b/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md @@ -70,7 +70,7 @@ Para coonfigurar un dominio apex, tal como `example.com`, debes configurar un ar {% data reusables.repositories.sidebar-settings %} {% data reusables.pages.sidebar-pages %} 4. Debajo de "Dominio personalizado", teclea tu dominio personalizado y luego da clic en **Guardar**. Esto creará una confirmación que agregará un archivo _CNAME_ en la raíz de tu fuente de publicación. ![Botón de guardar dominio personalizado](/assets/images/help/pages/save-custom-apex-domain.png) -5. Desplázate hasta tu proveedor DNS y crea un registro `ALIAS`, `ANAME` o `A`. You can also create `AAAA` records for IPv6 support. {% data reusables.pages.contact-dns-provider %} +5. Desplázate hasta tu proveedor DNS y crea un registro `ALIAS`, `ANAME` o `A`. También puedes crear registros de `AAAA` para compatibilidad con IPv6. {% data reusables.pages.contact-dns-provider %} - Para crear un registro `ALIAS` o `ANAME`, apunta tu dominio apex al dominio predeterminado de tu sitio. {% data reusables.pages.default-domain-information %} - Para crear registros `A`, apunta tu dominio apex a las direccioens IP de {% data variables.product.prodname_pages %}. ```shell @@ -79,7 +79,7 @@ Para coonfigurar un dominio apex, tal como `example.com`, debes configurar un ar 185.199.110.153 185.199.111.153 ``` - - To create `AAAA` records, point your apex domain to the IP addresses for {% data variables.product.prodname_pages %}. + - Para crear registros de `AAAA`, apunta tu dominio de apex a la dirección IP para {% data variables.product.prodname_pages %}. ```shell 2606:50c0:8000::153 2606:50c0:8001::153 @@ -90,7 +90,7 @@ Para coonfigurar un dominio apex, tal como `example.com`, debes configurar un ar {% indented_data_reference reusables.pages.wildcard-dns-warning spaces=3 %} {% data reusables.command_line.open_the_multi_os_terminal %} 6. Para confirmar que tu registro DNS esté configurado correctamente, usa el comando `dig` reemplazando _EXAMPLE.COM_ por tu dominio apex. Confirma que los resultados coincidan con las direcciones IP de las {% data variables.product.prodname_pages %} que aparecen arriba. - - For `A` records. + - Para los registros de `A`. ```shell $ dig EXAMPLE.COM +noall +answer -t A > EXAMPLE.COM 3600 IN A 185.199.108.153 @@ -98,7 +98,7 @@ Para coonfigurar un dominio apex, tal como `example.com`, debes configurar un ar > EXAMPLE.COM 3600 IN A 185.199.110.153 > EXAMPLE.COM 3600 IN A 185.199.111.153 ``` - - For `AAAA` records. + - Para los registros de `AAAA`. ```shell $ dig EXAMPLE.COM +noall +answer -t AAAA > EXAMPLE.COM 3600 IN AAAA 2606:50c0:8000::153 diff --git a/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md b/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md index c2c29739f9..e3288fc309 100644 --- a/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md +++ b/translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md @@ -32,10 +32,10 @@ Luego, asegúrate de que el archivo _CNAME_ tenga el formato correcto. Si tienes problemas para apuntar el dominio predeterminado para tu sitio a tu dominio personalizado, contáctate con tu proveedor DNS. -You can also use one of the following methods to test whether your custom domain's DNS records are configured correctly: +También puedes utilizar uno de los siguientes métodos para probar si los registros de DNS de tus dominios personalizados están configurados correctamente: -- A CLI tool such as `dig`. For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)". -- An online DNS lookup tool. +- Una herramienta de CLI tal como `dig`. Para obtener más información, consulta "[Administrar un dominio personalizado para tu sitio de {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)". +- Una herramienta de búsqueda de DNS en línea. ## Nombres de dominios personalizados que no son compatibles diff --git a/translations/es-ES/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md b/translations/es-ES/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md index 2a6ecee7c9..8e6b8bc1cb 100644 --- a/translations/es-ES/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md +++ b/translations/es-ES/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md @@ -38,7 +38,7 @@ Si antes agregaste manualmente un tema de Jekyll a tu repositorio, puede que eso 4. Para elegir un tema, haz clic en el tema que quieras y luego haz clic en **Select theme** (Seleccionar tema). ![Opciones de temas y botón Select theme (Seleccionar tema)](/assets/images/help/pages/select-theme.png) 5. Puede que se te solicite que edites el archivo *README.md* de tu sitio. - Para editar el archivo más tarde, haz clic en **Cancel** (Cancelar). ![Enlace de cancelación al editar un archivo](/assets/images/help/pages/cancel-edit.png) - - To edit the file now, see "[Editing files](/repositories/working-with-files/managing-files/editing-files)." + - Para editar el archivo ahora, consulta la sección "[Editar archivos](/repositories/working-with-files/managing-files/editing-files)". El tema elegido se aplicará automáticamente a los archivos markdown de tu repositorio. Para aplicar el tema a los archivos HTML de tu repositorio, debes agregar el texto preliminar de YAML que especifica un diseño para cada archivo. Para obtener más información, consulta "[Texto preliminar](https://jekyllrb.com/docs/front-matter/)" en el sitio de Jekyll. 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 5ba5ba8149..34e5155124 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 @@ -12,7 +12,11 @@ shortTitle: Cambiar la visibilidad del sitio ## Acerca del control de acceso para los sitios de {% data variables.product.prodname_pages %} -Si tu sitio de proyecto se publica desde un repositorio privado o interno que pertenezca a una organización que utiliza {% data variables.product.prodname_ghe_cloud %}, puedes administrar el control de accesos para el sitio. Con el control de acceso puedes elegir publicar el sitio de forma pública para cualquiera en internet o de forma privada para las personas con acceso de lectura en tu repositorio. Un sitio que se publica de forma privada puede utilizarse para compartir tu documentación o base de conocimientos internos con los miembros de tu empresa. 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)". +Con control de acceso para {% data variables.product.prodname_pages %}, puedes restringir el acceso a tu sitio de {% data variables.product.prodname_pages %} si lo publicas en privado. Solo las personas con acceso de lectura al repositorio desde el cual se publica el sitio pueden acceder al sitio que se publicó en privado. Puedes utilizar sitios publicados en privado para compartir tu documentación o base de conocimiento interna con los miembros de tu empresa. + +Si tu empresa utiliza {% data variables.product.prodname_emus %}, todos los sitios de {% data variables.product.prodname_pages %} se publicarán en privado. Para obtener más información sobre las {% data variables.product.prodname_emus %}, consulta la sección "[Acerca de las {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-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)". Los sitios que se publican de forma privada se encuentran disponibles en un subdominio diferente que el de aquellos sitios que se publican de forma pública. Esto garantiza que tu sitio de {% data variables.product.prodname_pages %} es seguro desde el momento en el que se publica: diff --git a/translations/es-ES/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md b/translations/es-ES/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md index 4a50233766..303ca47849 100644 --- a/translations/es-ES/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md +++ b/translations/es-ES/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md @@ -22,6 +22,12 @@ Todos los sitios {% data variables.product.prodname_pages %}, incluidos los siti {% data reusables.pages.private_pages_are_public_warning %} +{% note %} + +**Nota:** El RFC3280 indica que la longitud máxima del nombre común debe ser de 64 caracteres. Por lo tanto, todo el nombre de dominio de tu sitio de {% data variables.product.prodname_pages %} debe ser menor a 64 caracteres de longitud para que se cree un certificado exitosamente. + +{% endnote %} + ## Aplicar HTTPS en tu sitio {% data variables.product.prodname_pages %} {% data reusables.pages.navigate-site-repo %} diff --git a/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md index 18a22d2771..41c5b47046 100644 --- a/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md +++ b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md @@ -61,7 +61,7 @@ De manera predeterminada, Jekyll no compila archivos o carpetas que: - termina con `~` - están excluidos por el parámetro `exclude` en tu archivo de configuración -If you want Jekyll to process any of these files, you can use the `include` setting in your configuration file. +Si quieres que Jekyll procese cualquiera de estos archivos, puedes utilizar el ajuste `include` en tu archivo de configuración. ## Texto preliminar diff --git a/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md index 6247e4fdc4..3744ec896e 100644 --- a/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md +++ b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md @@ -86,7 +86,7 @@ Antes de que puedas usar Jekyll para crear un sitio de {% data variables.product La versión correcta de Jekyll se instalará como una dependencia de la gema `github-pages`. 1. Guarda y cierra el Gemfile. -1. From the command line, run `bundle install`. +1. Desde la línea de comandos, ejecuta `bundle install`. 1. Opcionalmente, haz cualquier edición necesaria en el archivo `_config.yml`. Esto se requiere para las rutas relativas cuando el repositorio se hospeda en un subdirectorio. Para obtener más información, consulta la sección "[Dividir una subcarpeta en un repositorio nuevo](/github/getting-started-with-github/using-git/splitting-a-subfolder-out-into-a-new-repository)". ```yml domain: my-site.github.io # if you want to force HTTPS, specify the domain without the http at the start, e.g. example.com diff --git a/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md index 6ac70f6c1c..f4597e1bb6 100644 --- a/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md +++ b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md @@ -18,9 +18,9 @@ shortTitle: Configurar un procesador de lenguaje de marcado Las personas con permisos de escritura para un repositorio pueden configurar el procesador Markdown para un sitio de {% data variables.product.prodname_pages %}. -{% data variables.product.prodname_pages %} supports two Markdown processors: [kramdown](http://kramdown.gettalong.org/) and {% data variables.product.prodname_dotcom %}'s own Markdown processor, which is used to render [{% data variables.product.prodname_dotcom %} Flavored Markdown (GFM)](https://github.github.com/gfm/) throughout {% data variables.product.product_name %}. Para obtener más información, consulta "[Acerca de la escritura y el formato en {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github)." +{% data variables.product.prodname_pages %} es compatible con dos procesadores de lenguaje de marcado: [kramdown](http://kramdown.gettalong.org/) y el procesador de lenguaje de marcado propio de {% data variables.product.prodname_dotcom %}, el cual se utiliza para procesar el [{% data variables.product.prodname_dotcom %} Lenguaje de marcado enriquecido (GFM)](https://github.github.com/gfm/) a través de {% data variables.product.product_name %}. Para obtener más información, consulta "[Acerca de la escritura y el formato en {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github)." -You can use {% data variables.product.prodname_dotcom %} Flavored Markdown with either processor, but only our GFM processor will always match the results you see on {% data variables.product.product_name %}. +Puedes utilizar el Lenguaje de Marcado Enriquecido de {% data variables.product.prodname_dotcom %} con cualquier procesador, pero solo tu procesador de GFM empatará siempre con los resultados que ves en {% data variables.product.product_name %}. {% data reusables.pages.navigate-site-repo %} 2. En tu repositorio, navega hasta el archivo *_config.yml*. diff --git a/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md index c7e38473ef..b8b151d04d 100644 --- a/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md +++ b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md @@ -157,7 +157,7 @@ Este error significa que tienes enlaces permanentes relativos que no son compati Los enlaces permanentes son URL permanentes que hacen referencia a una página particular en tu sitio. Los enlaces permanentes absolutos comienzan con la raíz del sitio, mientras que los enlaces permanentes relativos comienzan con la carpeta que contiene la página referenciada. {% data variables.product.prodname_pages %} y Jekyll ya no admiten enlaces permanentes relativos. Para obtener más información acerca de los enlaces permanentes, consulta "[Enlaces permanentes](https://jekyllrb.com/docs/permalinks/)" en la documentación de Jekyll. -Para solucionar el problema, elimina la línea `relativa_permalinks` de tu archivo *_config.yml* y vuelve a formatear cualquier enlace permanente relativo de tu sitio con enlaces permanentes absolutos. For more information, see "[Editing files](/repositories/working-with-files/managing-files/editing-files)." +Para solucionar el problema, elimina la línea `relativa_permalinks` de tu archivo *_config.yml* y vuelve a formatear cualquier enlace permanente relativo de tu sitio con enlaces permanentes absolutos. Para obtener más información, consulta la sección "[Editar archivos](/repositories/working-with-files/managing-files/editing-files)". ## El enlace simbólico no existe dentro del repositorio de tu sitio diff --git a/translations/es-ES/content/repositories/archiving-a-github-repository/archiving-repositories.md b/translations/es-ES/content/repositories/archiving-a-github-repository/archiving-repositories.md index 23224c97d6..5829a5dcad 100644 --- a/translations/es-ES/content/repositories/archiving-a-github-repository/archiving-repositories.md +++ b/translations/es-ES/content/repositories/archiving-a-github-repository/archiving-repositories.md @@ -16,7 +16,7 @@ topics: - Repositories --- -## About repository archival +## Acerca del archivamiento de repositorios {% ifversion fpt %} {% note %} @@ -32,7 +32,7 @@ Una vez que se archiva un repositorio, no puedes agregar ni eliminar colaborador Cuando se archiva un repositorio, sus propuestas, solicitudes de cambios, còdigo, etiquetas, hitos, proyectos, wiki, lanzamientos, confirmaciones, etiquetas, ramas, reacciones, alertas de escaneo de còdigo y comentarios se hacen de solo lectura. Para realizar cambios en un repositorio archivado, primero debes desarchivar el repositorio. -Puedes buscar repositorios archivados. Para obtener más información, consulta "[Buscar repositorios](/articles/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)." Para obtener más información, consulta "[Buscar repositorios](/articles/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)". Para obtener más información, consulta "[Buscar propuestas y solicitudes de extracción](/articles/searching-issues-and-pull-requests/#search-based-on-whether-a-repository-is-archived)". +Puedes buscar repositorios archivados. Para obtener más información, consulta "[Buscar repositorios](/search-github/searching-on-github/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)." Para obtener más información, consulta "[Buscar repositorios](/articles/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)". Para obtener más información, consulta "[Buscar propuestas y solicitudes de extracción](/search-github/searching-on-github/searching-issues-and-pull-requests/#search-based-on-whether-a-repository-is-archived)". ## Archivar un repositorio diff --git a/translations/es-ES/content/repositories/archiving-a-github-repository/backing-up-a-repository.md b/translations/es-ES/content/repositories/archiving-a-github-repository/backing-up-a-repository.md index a14cd6bf33..b49195a602 100644 --- a/translations/es-ES/content/repositories/archiving-a-github-repository/backing-up-a-repository.md +++ b/translations/es-ES/content/repositories/archiving-a-github-repository/backing-up-a-repository.md @@ -36,7 +36,7 @@ Cuando clonas un repositorio o wiki, solo se descargan los datos Git, como archi - [Proyectos](/rest/reference/projects#list-repository-projects) {% endif %} -Una vez que tienes una versión local{% ifversion ghes or ghae %} de todo el contenido del que deseas realizar una copia de seguridad, puedes crear un archivo zip y {% else %}una vez descargado tu archivo, puedes{% endif %}copiarlo en un disco duro externo o cargarlo en un servicio de copia de seguridad basado en la nube, como [Google Drive](https://www.google.com/drive/) o [Dropbox](https://www.dropbox.com/). +Once you have {% ifversion ghes or ghae %}a local version of all the content you want to back up, you can create a zip archive and {% else %}downloaded your archive, you can {% endif %}copy it to an external hard drive and/or upload it to a cloud-based backup or storage service such as [Azure Blob Storage](https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-overview/), [Google Drive](https://www.google.com/drive/) or [Dropbox](https://www.dropbox.com/). {% ifversion fpt %} ## Herramientas de copias de seguridad de terceros 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 1fc3a122c3..f0544ab39e 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 @@ -11,7 +11,7 @@ versions: ghae: '*' topics: - Repositories -shortTitle: About merge methods +shortTitle: Acerca de los métodos de fusión --- {% data reusables.pull_requests.configure_pull_request_merges_intro %} Puedes implementar un tipo de método de fusión, como el cambio de base o la combinación de confirmaciones, con solo activar el método deseado para tu repositorio. diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/index.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/index.md index dc41e62225..884c5680c9 100644 --- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/index.md +++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/index.md @@ -1,6 +1,6 @@ --- -title: Configuring branches and merges in your repository -intro: 'You can manage branches in your repository, configure the way branches are merged in your repository, and protect important branches by definining the mergeability of pull requests.' +title: Configurar ramas y fusiones en tu repositorio +intro: 'Puedes administrar las ramas en tu repositorio, configurar la forma en la que estas se fusionan en él y proteger las ramas importantes definiendo la capacidad de fusión de las solicitudes de cambios.' versions: fpt: '*' ghes: '*' @@ -11,6 +11,6 @@ children: - /managing-branches-in-your-repository - /configuring-pull-request-merges - /defining-the-mergeability-of-pull-requests -shortTitle: Branches and merges +shortTitle: Ramas y fusiones --- diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md index 821c0a9f24..12c1b40fd7 100644 --- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md +++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md @@ -28,13 +28,13 @@ Puedes elegir la rama predeterminada para un repositorio. Èsta es la rama base {% endnote %} {% endif %} -{% ifversion fpt or ghes > 3.0 %} +{% ifversion fpt or ghes > 3.0 or ghae-next %} También puedes renombrar la rama predeterminada. Para obtener más información, consulta la sección "[Renombrar una rama](/github/administering-a-repository/renaming-a-branch)". {% endif %} -{% ifversion fpt or ghes > 2.22 %} +{% ifversion fpt or ghes > 2.22 or ghae-next %} {% data reusables.branches.set-default-branch %} @@ -54,7 +54,7 @@ Para cambiar la rama predeterminada, tu repositorio debe tener màs de una rama. 1. Debajo de "Rama predeterminada", a la derecha del nombre de rama predeterminado, da clic en el {% octicon "arrow-switch" aria-label="The switch icon with two arrows" %}. ![Cambiar el icono con dos flechas hacia la derecha del nombre de la rama predeterminada actual](/assets/images/help/repository/repository-options-defaultbranch-change.png) 1. Utiliza el menù desplegable y luego da clic en el nombre de una rama. ![Menù desplegable para elegir una rama predeterminada nueva](/assets/images/help/repository/repository-options-defaultbranch-drop-down.png) 1. Da clic en **Actualizar**. ![Botòn de "Update" despuès de elegir una rama predeterminada nueva](/assets/images/help/repository/repository-options-defaultbranch-update.png) -1. Lee la advertencia y luego da clic en **Entiendo, actualizar la rama predeterminada.** !["I understand, update the default branch." button to perform the update](/assets/images/help/repository/repository-options-defaultbranch-i-understand.png) +1. Lee la advertencia y luego da clic en **Entiendo, actualizar la rama predeterminada.** ![Botón de "Entiendo, actualizar la rama predeterminada." para realizar la actualización](/assets/images/help/repository/repository-options-defaultbranch-i-understand.png) {% else %} diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md index 382b4ae900..a7601ba54d 100644 --- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md +++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md @@ -14,7 +14,7 @@ versions: ghae: '*' topics: - Repositories -shortTitle: Delete & restore branches +shortTitle: Borrar & restablecer las ramas --- ## Borrar la rama utilizada para una solicitud de extracción diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md index 5a0232e8df..46526c2d77 100644 --- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md +++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md @@ -5,6 +5,7 @@ permissions: People with write permissions to a repository can rename a branch i versions: fpt: '*' ghes: '>=3.1' + ghae: next topics: - Repositories redirect_from: diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/viewing-branches-in-your-repository.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/viewing-branches-in-your-repository.md index c01013b6bd..30eceabe21 100644 --- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/viewing-branches-in-your-repository.md +++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/viewing-branches-in-your-repository.md @@ -17,7 +17,7 @@ shortTitle: Ver ramas {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.navigate-to-branches %} 3. Utiliza la navegación en la parte superior de la página para ver las listas de ramas específicas: - - **Your branches**: In repositories that you have push access to, the **Yours** view shows all branches that you’ve pushed to, excluding the default branch, with the most recent branches first. + - **Tus ramas**: En los repositorios a los cuales hayas subido código, la vista de **Tuyos** muestra todas las ramas que has subido, excluyendo la predeterminada, con las ramas más recientes primero. - **Ramas activas**: la vista **Active** (Activas) muestra todas las ramas a las que alguien ha confirmado dentro de los últimos tres meses, ordenadas de forma descendente desde las ramas con las confirmaciones más recientes. - **Ramas en espera**: la vista **Stale** (En espera) muestra todas las ramas en las que nadie ha confirmado durante los últimos tres meses, ordenadas de forma descendente desde las confirmaciones más antiguas. Utiliza esta lista para determinar [qué ramas eliminar](/articles/creating-and-deleting-branches-within-your-repository). - **Todas las ramas**: la vista **All** (Todas) muestra la rama por defecto, seguida por todas las otras ramas ordenadas de forma descendente desde las ramas con las confirmaciones más recientes. diff --git a/translations/es-ES/content/repositories/creating-and-managing-repositories/about-repositories.md b/translations/es-ES/content/repositories/creating-and-managing-repositories/about-repositories.md index 9bc6bc6e07..e71aba68d6 100644 --- a/translations/es-ES/content/repositories/creating-and-managing-repositories/about-repositories.md +++ b/translations/es-ES/content/repositories/creating-and-managing-repositories/about-repositories.md @@ -74,7 +74,7 @@ Todos los miembros de las empresas tienen permiso de lectura para los repositori {% data reusables.repositories.internal-repo-default %} -Si se elimina a un usuario de todas las organizaciones que pertenezcan a la empresa, las bifurcaciones de dicho usuario para los repositorios internos se eliminarán automáticamente. +Cualquier miembro de la empresa puede bifurcar cualquier repositorio interno que pertenezca a una organización de esta. El repositorio bifurcado pertenecerá a la cuenta de usuario del miembro y la visibilidad de este será privada. Si se elimina a un usuario de todas las organizaciones que pertenezcan a la empresa, las bifurcaciones de dicho usuario para los repositorios internos se eliminarán automáticamente. {% endif %} ## Límites para ver contenido y diferencias en un repositorio @@ -85,7 +85,7 @@ La mayoría de los límites que aparecen a continuación afectan tanto {% data v ### Límites de texto -Text files over **512 KB** are always displayed as plain text. El código no es de sintaxis resaltada, y los archivos de prosa no se convierten a HTML (como Markdown, AsciiDoc, *etc.*). +Los archivos de texto de más de **512 KB** siempre se mostrarán como texto simple. El código no es de sintaxis resaltada, y los archivos de prosa no se convierten a HTML (como Markdown, AsciiDoc, *etc.*). Los archivos de texto de más de **5 MB** están disponibles solo a través de sus URL originales, que se ofrecen a través de `{% data variables.product.raw_github_com %}`; por ejemplo, `https://{% data variables.product.raw_github_com %}/octocat/Spoon-Knife/master/index.html`. Haz clic en el botón **Raw** (Original) para obtener la URL original de un archivo. @@ -93,9 +93,9 @@ Los archivos de texto de más de **5 MB** están disponibles solo a través de s Como las diferencias se pueden volver muy grandes, imponemos los siguientes límites en las diferencias para las confirmaciones, las solicitudes de extracción y las vistas comparadas: -- In a pull request, no total diff may exceed *20,000 lines that you can load* or *1 MB* of raw diff data. -- No single file's diff may exceed *20,000 lines that you can load* or *500 KB* of raw diff data. *Cuatrocientas líneas* y *20 KB* se cargan de forma automática para un archivo único. -- The maximum number of files in a single diff is limited to *300*. +- En una solicitud de cambios, ningún diff total podrá exceder las *20,000 líneas que puedes cargar* o *1 MB* de datos de diff sin procesar. +- El diff de un archivo único no puede superar las *20.000 líneas que puedes cargar* o *500 KB* de datos de la diferencia original. *Cuatrocientas líneas* y *20 KB* se cargan de forma automática para un archivo único. +- La cantidad máxima de archivos en diff único se limita a *300*. - La cantidad máxima de archivos de representación (como PDF y archivos GeoJSON) en una diferencia única está limitada a *25*. Se pueden mostrar algunas partes de una diferencia limitada, pero no se muestra nada que supere el límite. @@ -107,6 +107,7 @@ Las páginas de vista comparada y de solicitudes de extracción muestran una lis ## Leer más - "[Crear un repositorio nuevo](/articles/creating-a-new-repository)" +- "[Acerca de las bifurcaciones](/github/collaborating-with-pull-requests/working-with-forks/about-forks)" - "[Colaborar con propuestas y solicitudes de extracción](/categories/collaborating-with-issues-and-pull-requests)" - "[Administrar tu trabajo en {% data variables.product.prodname_dotcom %}](/categories/managing-your-work-on-github/)" - "[Administrar un repositorio](/categories/administering-a-repository)" 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 c2f027495e..220770115e 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 @@ -39,7 +39,7 @@ topics: 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 %} -6. Si no estás utilizando una plantilla, hay varios elementos opcionales que puedes pre-cargar en tu repositorio. Si estás importando un repositorio existente a {% data variables.product.product_name %}, no elijas ninguna de estas opciones, ya que producirás un conflicto de fusión. Puedes agregar o crear nuevos archivos usando la interfaz de usuario o elegir agregar nuevos archivos usando luego la línea de comando. For more information, see "[Importing a Git repository using the command line](/articles/importing-a-git-repository-using-the-command-line/)," "[Adding a file to a repository](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository#adding-a-file-to-a-repository-using-the-command-line)," and "[Addressing merge conflicts](/articles/addressing-merge-conflicts/)." +6. Si no estás utilizando una plantilla, hay varios elementos opcionales que puedes pre-cargar en tu repositorio. Si estás importando un repositorio existente a {% data variables.product.product_name %}, no elijas ninguna de estas opciones, ya que producirás un conflicto de fusión. Puedes agregar o crear nuevos archivos usando la interfaz de usuario o elegir agregar nuevos archivos usando luego la línea de comando. Para obtener más información, consulta las secciones "[Importar un repositorio de Git utilizando la línea de comandos](/articles/importing-a-git-repository-using-the-command-line/)", "[Agregar un archivo a un repositorio](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository#adding-a-file-to-a-repository-using-the-command-line)" y "[Abordar los conflictos de fusión](/articles/addressing-merge-conflicts/)". - Puedes crear un README, que es un documento que describe tu proyecto. Para obtener más información, consulta "[Acerca de los README](/articles/about-readmes/)". - Puedes crear un archivo *.gitignore*, que es un conjunto de reglas de ignorar. Para obtener más información, consulta "[Ignorar archivos](/github/getting-started-with-github/ignoring-files)".{% ifversion fpt %} - Puedes elegir agregar una licencia de software a tu proyecto. Para más información, consulta "[Licenciando un repositorio](/articles/licensing-a-repository)."{% endif %} diff --git a/translations/es-ES/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md b/translations/es-ES/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md index 14d6b3e7ff..3d7c1a9a0b 100644 --- a/translations/es-ES/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md +++ b/translations/es-ES/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md @@ -1,6 +1,6 @@ --- title: Duplicar un repositorio -intro: 'To maintain a mirror of a repository without forking it, you can run a special clone command, then mirror-push to the new repository.' +intro: 'Para mantener una réplica de un repositorio sin bifurcarlo, puedes ejecutar un comando de clonado especial y luego subir la réplica al repositorio nuevo.' redirect_from: - /articles/duplicating-a-repo/ - /articles/duplicating-a-repository @@ -18,13 +18,13 @@ topics: {% note %} -**Note:** If you have a project hosted on another version control system, you can automatically import your project to {% data variables.product.prodname_dotcom %} using the {% data variables.product.prodname_dotcom %} Importer tool. For more information, see "[About {% data variables.product.prodname_dotcom %} Importer](/github/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer)." +**Nota:** Si tienes un proyecto hospedado en otro sistema de control de versiones, puedes importar tu proyecto automáticamente a {% data variables.product.prodname_dotcom %} utilizando la herramienta importadora de {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Acerca del importador de {% data variables.product.prodname_dotcom %}](/github/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer)". {% endnote %} {% endif %} -Before you can push the original repository to your new copy, or _mirror_, of the repository, you must [create the new repository](/articles/creating-a-new-repository) on {% data variables.product.product_location %}. En estos ejemplos, `exampleuser/new-repository` o `exampleuser/mirrored` son los espejos. +Antes de que puedas subir el repositorio original a tu copia nueva o _réplica_ de este, debes [crear un repositorio nuevo](/articles/creating-a-new-repository) en {% data variables.product.product_location %}. En estos ejemplos, `exampleuser/new-repository` o `exampleuser/mirrored` son los espejos. ## Generar un espejo de un repositorio @@ -97,8 +97,8 @@ $ git push --mirror {% ifversion fpt %} ## Leer más -* "[Pushing changes to GitHub](/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/pushing-changes-to-github#pushing-changes-to-github)" -* "[About Git Large File Storage and GitHub Desktop](/desktop/getting-started-with-github-desktop/about-git-large-file-storage-and-github-desktop)" +* "[Subir cambios a GitHub](/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/pushing-changes-to-github#pushing-changes-to-github)" +* "[Acerca del Almacenamiento de Archivos Grandes de Git y de GitHub Desktop](/desktop/getting-started-with-github-desktop/about-git-large-file-storage-and-github-desktop)" * "[Acerca del Importador GitHub](/github/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer)" {% endif %} diff --git a/translations/es-ES/content/repositories/creating-and-managing-repositories/index.md b/translations/es-ES/content/repositories/creating-and-managing-repositories/index.md index c86ec3b98f..5d1109a618 100644 --- a/translations/es-ES/content/repositories/creating-and-managing-repositories/index.md +++ b/translations/es-ES/content/repositories/creating-and-managing-repositories/index.md @@ -1,6 +1,6 @@ --- -title: Creating and managing repositories -intro: 'You can create a repository on {% data variables.product.product_name %} to store and collaborate on your project''s files, then manage the repository''s name and location.' +title: Crear y administrar repositorios +intro: 'Puedes crear un repositorio en {% data variables.product.product_name %} para almacenar y colaborar con los archivos de tu proyecto y luego administrar el nombre y ubicación del repositorio.' redirect_from: - /articles/creating-a-repository-on-github - /github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github @@ -23,6 +23,6 @@ children: - /transferring-a-repository - /deleting-a-repository - /restoring-a-deleted-repository -shortTitle: Create & manage repositories +shortTitle: Crear & administrar repositorios --- diff --git a/translations/es-ES/content/repositories/creating-and-managing-repositories/transferring-a-repository.md b/translations/es-ES/content/repositories/creating-and-managing-repositories/transferring-a-repository.md index a61e621fb8..c8f7f344b6 100644 --- a/translations/es-ES/content/repositories/creating-and-managing-repositories/transferring-a-repository.md +++ b/translations/es-ES/content/repositories/creating-and-managing-repositories/transferring-a-repository.md @@ -50,7 +50,7 @@ Cuando transfieres un repositorio, también se transfieren sus propuestas, solic $ git remote set-url origin new_url ``` -- When you transfer a repository from an organization to a user account, the repository's read-only collaborators will not be transferred. This is because collaborators can't have read-only access to repositories owned by a user account. Para obtener más información acerca de los niveles de permiso en los repositorios, consulta "[Niveles de permiso para un repositorio de la cuenta de un usuario](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" y"[Niveles de permiso para una organización](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)." +- Cuando transfieres un repositorio desde una organización a una cuenta de usuario, los colaboradores de solo lectura de este no se transferirán. Esto es porque los colaboradores no pueden tener acceso de solo lectura a los repositorios que pertenecen a una cuenta de usuario. Para obtener más información acerca de los niveles de permiso en los repositorios, consulta "[Niveles de permiso para un repositorio de la cuenta de un usuario](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" y"[Niveles de permiso para una organización](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)." Para obtener más información, consulta "[Administrar repositorios remotos](/github/getting-started-with-github/managing-remote-repositories)." diff --git a/translations/es-ES/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md b/translations/es-ES/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md index 3d8dc5c770..14db9a5d9b 100644 --- a/translations/es-ES/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md +++ b/translations/es-ES/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md @@ -1,6 +1,6 @@ --- title: Solucionar los errores de clonado -intro: 'If you''re having trouble cloning a repository, check these common errors.' +intro: 'Si estás teniendo problemas para clonar un repositorio, verifica estos errores comunes.' redirect_from: - /articles/error-the-requested-url-returned-error-403 - /articles/error-the-requested-url-returned-error-401 diff --git a/translations/es-ES/content/repositories/index.md b/translations/es-ES/content/repositories/index.md index 1ca5d865c4..59110613ff 100644 --- a/translations/es-ES/content/repositories/index.md +++ b/translations/es-ES/content/repositories/index.md @@ -1,6 +1,6 @@ --- title: Repositorios -intro: Learn to use and manage the repositories that allow you to store and collaborate on your project's code. +intro: Aprende a utilizar y administrar los repositorios que te permiten almacenar y colaborar con el código de tu proyecto. redirect_from: - /github/creating-cloning-and-archiving-repositories versions: diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md index 33fea40dfb..fbe88144fc 100644 --- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md +++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md @@ -1,6 +1,6 @@ --- -title: About CITATION files -intro: You can add a CITATION file to your repository to help users correctly cite your software. +title: Acerca de los archivos de CITATION +intro: Puedes agregar un archivo de CITATION a tu repositorio para ayudar a que los usuarios citen tu software correctamente. redirect_from: - /github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-citation-files versions: @@ -11,11 +11,11 @@ topics: - Repositories --- -## About CITATION files +## Acerca de los archivos de CITATION -You can add a `CITATION.cff` file to the root of a repository to let others know how you would like them to cite your work. The citation file format is plain text with human- and machine-readable citation information. +Puedes agregar un archivo de `CITATION.cff` a la raíz de un repositorio para que otros sepan cómo te gustaría que citaran tu trabajo. El formato de archivo de cita es texto simple con información de cita legible para humanos y máquinas. -Example `CITATION.cff` file: +Ejemplo de archivo de `CITATION.cff`: ``` cff-version: 1.2.0 @@ -34,7 +34,7 @@ date-released: 2017-12-18 url: "https://github.com/github/linguist" ``` -The GitHub citation prompt on your repository will show the example `CITATION.cff` content in these formats: +El mensaje de cita de GitHub en tu repositorio te mostrará el contenido de ejemplo de un `CITATION.cff` en estos formatos: **APA** @@ -46,30 +46,37 @@ Lisa, M., & Bot, H. (2017). My Research Software (Version 2.0.4) [Computer softw {% raw %} ``` -@misc{Lisa_My_Research_Software_2017, +@software{Lisa_My_Research_Software_2017, author = {Lisa, Mona and Bot, Hew}, doi = {10.5281/zenodo.1234}, month = {12}, title = {{My Research Software}}, url = {https://github.com/github/linguist}, + version = {2.0.4}, year = {2017} } ``` {% endraw %} -Note the example above produces a _software_ citation (i.e., `@misc` type in BibTeX rather than `@article`). +Note the example above produces a _software_ citation (i.e., `@software` type in BibTeX rather than `@article`). -For more information, see the [Citation File Format](https://citation-file-format.github.io/) website. +Para obtener más información, consulta el sitio web de [Formatos de Archivos de Citas](https://citation-file-format.github.io/). -When you add a `CITATION.cff` file to the default branch of your repository, it is automatically linked from the repository landing page. This makes it easy for other users to cite your software project, using the information you've provided. +Cuando agregas un archivo de `CITATION.cff` a la rama predeterminada de tu repositorio, este se enlaza automáticamente desde la página de llegada del repositorio. Esto hace fácil que otros usuarios citen tu proyecto de software, utilizando la información que proporcionaste. -![Citation link on repository landing page](/assets/images/help/repository/citation-link.png) +![Enlaze de cita en la página de inicio de un repositorio](/assets/images/help/repository/citation-link.png) -## Citing something other than software +## Citar algo que no sea software -If you would prefer the GitHub citation information to link to another resource such as a research paper then you can use the `preferred-citation` override in CFF. +If you would prefer the {% data variables.product.prodname_dotcom %} citation information to link to another resource such as a research article, then you can use the `preferred-citation` override in CFF with the following types. -Extended CITATION.cff file describing the software, but linking to a research paper as the preferred citation: +| Resource | Type | +| ---------------- | ------------------ | +| Research article | `article` | +| Conference paper | `conference-paper` | +| Book | `book` | + +Extended CITATION.cff file describing the software, but linking to a research article as the preferred citation: ``` cff-version: 1.2.0 @@ -106,7 +113,7 @@ preferred-citation: year: 2021 ``` -The example `CITATION.cff` file above will produce the following outputs in the GitHub citation prompt: +El archivo `CITATION.cff` anterior producirá los siguientes resultados en el mensaje de cita de GitHub: **APA** @@ -132,11 +139,15 @@ Lisa, M., & Bot, H. (2021). My awesome research software. Journal Title, 1(1), 1 ``` {% endraw %} -## Other citation files +## Citing a dataset -The GitHub citation feature will also detect a small number of additional files that are often used by communities and projects to describe how they would like their work to be cited. +If your repository contains a dataset, you can set `type: dataset` in your `CITATION.cff` file to produce a data citation string output in the {% data variables.product.prodname_dotcom %} citation prompt. -GitHub will link to these files in the _Cite this repository_ prompt, but will not attempt to parse them into other citation formats. +## Otros archivos de cita + +La característica de cita de GitHub también detectará una cantidad pequeña de archivos adicionales que a menudo se utilizan en las comunidades y proyectos para describir cómo quieren que se cite su trabajo. + +GitHub enlazará estos archivos en el mensaje de _Citar este repositorio_, pero no intentará analizarlos en otros formatos de cita. ``` # Note these are case-insensitive and must be in the root of the repository @@ -151,8 +162,8 @@ CITATIONS.md inst/CITATION ``` -## Citation formats +## Formatos de cita -We currently support APA and BibTex file formats. +Actualmente tenemos compatibilidad con formatos de archivo en APA y BibTex. -Are you looking for additional citation formats? GitHub uses a Ruby library, to parse the `CITATION.cff` files. You can request additional formats in the [ruby-cff](https://github.com/citation-file-format/ruby-cff) repository, or contribute them yourself. +¡Estás buscando formatos de cita adicionales? GitHub utiliza una librería de Ruby para analizar los archivos de `CITATION.cff`. Puedes solicitar formatos adicionales en el repositorio [ruby-cff](https://github.com/citation-file-format/ruby-cff) o proporcionarlos tú mismo como contribución. diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md index 795dc28c99..89ee625c7d 100644 --- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md +++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md @@ -17,7 +17,7 @@ topics: Las personas con permisos administrativos o de propietario pueden configurar un archivo CODEOWNERS en un repositorio. -Las personas que elijas como propietarios del código deben tener permisos de escritura para el repositorio. When the code owner is a team, that team must be visible and it must have write permissions, even if all the individual members of the team already have write permissions directly, through organization membership, or through another team membership. +Las personas que elijas como propietarios del código deben tener permisos de escritura para el repositorio. Cuando el propietario del código es un equipo, ese equipo debe ser visible y tener permisos de escritura, incluso si todos los miembros individuales del equipo ya tienen permisos de escritura, a través de la membresía de la organización o a través de la membresía de otro equipo. ## Acerca de los propietarios del código @@ -42,16 +42,16 @@ Cada archivo CODEOWNERS asigna los propietarios del código para una única rama Para que los propietarios del código reciban las solicitudes de revisión, el archivo CODEOWNERS debe estar en la rama base de la solicitud de extracción. Por ejemplo, si asignas `@octocat` como el propietario del código para los archivos *.js* en la rama `gh-pages` de tu repositorio, `@octocat` recibirá las solicitudes de revisión cuando una solicitud de extracción con cambios en los archivos *.js* se abra entre la rama de encabezado y `gh-pages`. {% ifversion fpt or ghae or ghes > 3.2 %} -## CODEOWNERS file size +## Tamaño de archivo de CODEOWNERS -CODEOWNERS files must be under 3 MB in size. A CODEOWNERS file over this limit will not be loaded, which means that code owner information not to be shown and the appropriate code owners will not be requested to review changes in a pull request. +Los archivos de CODEOWNERS deben ser de menos de 3 MB. Un archivo de CODEOWNERS que sobrepase este límite no se cargará, lo cual significa que la información de los propietarios de código no se mostrará y que no se solicitará que los propietarios de código adecuados revisen los cambios en una solicitud de cambios. -To reduce the size of your CODEOWNERS file, consider using wildcard patterns to consolidate multiple entries into a single entry. +Para reducir el tamaño de tu archivo de CODEOWNERS, considera utilizar patrones de comodín para consolidar varias entradas en una. {% endif %} ## Sintáxis de CODEOWNERS -Un archivo de CODEOWNERS utiliza un patrón que sigue la mayoría de las mismas reglas que utilizan los archivos [gitignore](https://git-scm.com/docs/gitignore#_pattern_format), con [algunas excepciones](#syntax-exceptions). El patrón es seguido por uno o más nombres de usuarios o nombres de equipos de {% data variables.product.prodname_dotcom %} usando el formato estándar `@username` o `@org/team-name`. Users must have `read` access to the repository and teams must have explicit `write` access, even if the team's members already have access. También puedes hacer referencia a un usuario mediante una dirección de correo electrónico que haya sido agregada a su cuenta de {% data variables.product.product_name %}, por ejemplo `user@example.com`. +Un archivo de CODEOWNERS utiliza un patrón que sigue la mayoría de las mismas reglas que utilizan los archivos [gitignore](https://git-scm.com/docs/gitignore#_pattern_format), con [algunas excepciones](#syntax-exceptions). El patrón es seguido por uno o más nombres de usuarios o nombres de equipos de {% data variables.product.prodname_dotcom %} usando el formato estándar `@username` o `@org/team-name`. Los usuarios deben tener acceso de `read` en el repositorio y los equipos deben tener acceso explícito de `write`, incluso si los miembros de dichos equipos ya tienen acceso. También puedes hacer referencia a un usuario mediante una dirección de correo electrónico que haya sido agregada a su cuenta de {% data variables.product.product_name %}, por ejemplo `user@example.com`. Si cualquier línea de tu archivo de CODEOWNERS contiene una sintaxi inválida, el archivo no se detectará y no se utilizará para solicitar revisiones. ### Ejemplo de un archivo CODEOWNERS @@ -109,8 +109,8 @@ Hay algunas reglas de sintaxis para los archivos de gitignore que no funcionan c - Utilizar `!` para negar un patrón - Utilizar `[ ]` para definir un rango de carácter -## CODEOWNERS and branch protection -Repository owners can add branch protection rules to ensure that changed code is reviewed by the owners of the changed files. Para obtener más información, consulta la sección "[Acerca de las ramas protegidas](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)". +## Protección de rama y de CODEOWNERS +Los propietarios de los repositorios pueden agregar reglas de protección de rama para asegurarse de que los propietarios de los archivos que se modificaron revisen el código que cambió. Para obtener más información, consulta la sección "[Acerca de las ramas protegidas](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)". ### Ejemplo de un archivo CODEOWNERS diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md index dc0cf1b7ce..ec0ace0cdf 100644 --- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md +++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md @@ -17,7 +17,7 @@ topics: ## Acerca de los archivos README -Puedes agregar un archivo README a un repositorio para comunicar información importante sobre tu proyecto. A README, along with a repository license{% ifversion fpt or ghes > 3.2 or ghae-issue-4651 %}, citation file{% endif %}{% ifversion fpt %}, contribution guidelines, and a code of conduct{% elsif ghes %} and contribution guidelines{% endif %}, communicates expectations for your project and helps you manage contributions. +Puedes agregar un archivo README a un repositorio para comunicar información importante sobre tu proyecto. El contar con un README, en conjunto con una licencia de repositorio{% ifversion fpt or ghes > 3.2 or ghae-issue-4651 %}, archivo de citas{% endif %}{% ifversion fpt %}, lineamientos de contribución y código de conducta{% elsif ghes %} y lineamientos de contribución{% endif %}, comunica las expectativas de tu proyecto y te ayuda a administrar las contribuciones. Para obtener más información acerca de cómo proporcionar lineamientos para tu proyecto, consulta la sección {% ifversion fpt %}"[Agregar un código de conducta para tu proyecto](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)" y {% endif %}"[Configurar tu proyecto para que tenga contribuciones sanas](/communities/setting-up-your-project-for-healthy-contributions)". diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md index a4bf2c389b..52cffdd564 100644 --- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md +++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md @@ -29,7 +29,7 @@ Los administradores del repositorio pueden agregar los temas que deseen a un rep {% ifversion ghae %}Los repositorios internos {% else %}Públicos, internos, {% endif %}y privados pueden tener temas, aunque solo verás los repositorios privados a los cuales tengas acceso en los resultados de búsqueda por tema. -Puedes buscar los repositorios que están asociados con un tema en particular. Para obtener más información, consulta "[Buscar repositorios](/articles/searching-for-repositories/#search-by-topic)". También puedes buscar un listado de temas en {% data variables.product.product_name %}. Para obtener más información, consulta "[Buscar temas](/articles/searching-topics)". +Puedes buscar los repositorios que están asociados con un tema en particular. Para obtener más información, consulta "[Buscar repositorios](/search-github/searching-on-github/searching-for-repositories#search-by-topic)." También puedes buscar un listado de temas en {% data variables.product.product_name %}. Para obtener más información, consulta "[Buscar temas](/search-github/searching-on-github/searching-topics)". ## Agregar temas a tu repositorio diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/index.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/index.md index 8ee1a06a5e..5c9d469b9c 100644 --- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/index.md +++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/index.md @@ -1,6 +1,6 @@ --- -title: Customizing your repository -intro: You can choose the way your repository appears by customizing your repository. +title: Personalizar tu repositorio +intro: Puedes elegir la forma en la que se muestra tu repositorio si lo personalizas. versions: fpt: '*' ghes: '*' @@ -16,6 +16,6 @@ children: - /about-code-owners - /about-repository-languages - /about-citation-files -shortTitle: Customize your repository +shortTitle: Personalizar tu repositorio --- diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md index 3192965844..627b22d416 100644 --- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md +++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md @@ -73,7 +73,7 @@ Puedes filtrar repositorios en función de su licencia o familia de licencia usa | | The Unlicense | `unlicense` | | | zLib License | `zlib` | -Cuando busques por una licencia de familia, los resultados incluirán todas las licencias de esa familia. Por ejemplo, cuando utilices la consulta `license:gpl`, los resultados incluirán los repositorios con licencia de GNU General Public License v2.0 y GNU General Public License v3.0. Para obtener más información, consulta "[Buscar repositorios](/articles/searching-for-repositories/#search-by-license)." +Cuando busques por una licencia de familia, los resultados incluirán todas las licencias de esa familia. Por ejemplo, cuando utilices la consulta `license:gpl`, los resultados incluirán los repositorios con licencia de GNU General Public License v2.0 y GNU General Public License v3.0. Para obtener más información, consulta "[Buscar repositorios](/search-github/searching-on-github/searching-for-repositories/#search-by-license)." ## Detectar una licencia diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md index 52bed81fd0..068b8cfb56 100644 --- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md +++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md @@ -1,6 +1,6 @@ --- title: Habilita o inhabilita los debates de GitHub para un repositorio -intro: 'You can use {% data variables.product.prodname_discussions %} in a repository as a place for your community to have conversations, ask questions, and post answers without scoping work in an issue.' +intro: 'Puedes utilizar los {% data variables.product.prodname_discussions %} en un repositorio como un lugar para que tu comunidad tenga conversaciones, haga preguntas y publique respuestas sin dimensionar el trabajo en una propuesta.' product: '{% data reusables.gated-features.discussions %}' permissions: 'People with admin permissions to a repository can enable {% data variables.product.prodname_discussions %} for the repository.' versions: @@ -13,7 +13,7 @@ redirect_from: shortTitle: Debates --- -## Enabling or disabling {% data variables.product.prodname_discussions %} for your repository +## Habilitar o inhabilitar los {% data variables.product.prodname_discussions %} en tu repositorio {% data reusables.discussions.enabling-or-disabling-github-discussions-for-your-repository %} 1. Para inhabilitar los debates, debajo de "Características", deselecciona **Debates**. diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/index.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/index.md index 9ad3dc1f15..f71ace92e2 100644 --- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/index.md +++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/index.md @@ -1,6 +1,6 @@ --- -title: Enabling features for your repository -intro: 'You can enable, configure, and disable optional features for your repository.' +title: Habilitarlas características para tu repositorio +intro: 'Puedes habilitar, configurar e inhabilitar las características opcionales de tu repositorio.' versions: fpt: '*' ghes: '*' @@ -13,6 +13,6 @@ children: - /managing-github-actions-settings-for-a-repository - /enabling-or-disabling-github-discussions-for-a-repository - /managing-security-and-analysis-settings-for-your-repository -shortTitle: Enable features +shortTitle: Habilitar características --- diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md index 3f16fd2259..5d4b44cb29 100644 --- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md +++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md @@ -1,6 +1,6 @@ --- -title: Managing GitHub Actions settings for a repository -intro: 'You can disable or configure {% data variables.product.prodname_actions %} for a specific repository.' +title: Administrar los ajustes de las GitHub Actions de un repositorio +intro: 'Puedes inhabilitar o configurar las {% data variables.product.prodname_actions %} en un repositorio específico.' redirect_from: - /github/administering-a-repository/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository - /github/administering-a-repository/managing-repository-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository @@ -12,7 +12,7 @@ versions: ghae: '*' topics: - Pull requests -shortTitle: Manage GitHub Actions settings +shortTitle: Administrar los ajustes de las GitHub Actions --- {% data reusables.actions.enterprise-beta %} @@ -32,7 +32,7 @@ De manera alterna, puedes habilitar {% data variables.product.prodname_actions % {% note %} -**Nota:** Tal vez no pueds administrar estas configuraciones si tu organización tiene una política de anulación o si la administra una cuenta empresarial que tiene dicha configuración. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)" or {% ifversion fpt %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif ghes %}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."{% endif %} +**Nota:** Tal vez no pueds administrar estas configuraciones si tu organización tiene una política de anulación o si la administra una cuenta empresarial que tiene dicha configuración. Para obtener más información, consulta las secciones "[Inhabilitar o limitar las {% data variables.product.prodname_actions %} en tu organización](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)" o {% ifversion fpt %}"[Requerir políticas de las {% data variables.product.prodname_actions %} en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)".{% elsif ghes %}"[Requerir políticas de {% data variables.product.prodname_actions %} para tu empresa](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)".{% endif %} {% endnote %} @@ -43,7 +43,7 @@ De manera alterna, puedes habilitar {% data variables.product.prodname_actions % {% endif %} -{% ifversion fpt or ghes > 2.22 %} +{% ifversion fpt or ghes > 2.22 or ghae-next %} ## Administrar los permisos de {% data variables.product.prodname_actions %} para tu repositorio @@ -53,7 +53,7 @@ Puedes inhabilitar todos los flujos de trabajo para un repositorio o configurar {% note %} -**Nota:** Tal vez no pueds administrar estas configuraciones si tu organización tiene una política de anulación o si la administra una cuenta empresarial que tiene dicha configuración. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)" or {% ifversion fpt %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif ghes %}"[Enforcing {% data variables.product.prodname_actions %} policies for your enterprise](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)." +**Nota:** Tal vez no pueds administrar estas configuraciones si tu organización tiene una política de anulación o si la administra una cuenta empresarial que tiene dicha configuración. Para obtener más información, consulta las secciones "[Inhabilitar o limitar las {% data variables.product.prodname_actions %} en tu organización](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)" o {% ifversion fpt %}"[Hacer cumplir las políticas de las {% data variables.product.prodname_actions %} en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)."{% elsif ghes %}"[Hacer cumplir las políticas de las {% data variables.product.prodname_actions %} para tu empresa](/enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)". {% endif %} @@ -72,14 +72,21 @@ Puedes inhabilitar todos los flujos de trabajo para un repositorio o configurar {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.settings-sidebar-actions %} -1. Debajo de **Permisos de las acciones**, selecciona **Permitir acciones seleccionadas** y agrega tus acciones requeridas a la lista. ![Agregar acciones a la lista de permitidos](/assets/images/help/repository/actions-policy-allow-list.png) +1. Debajo de **Permisos de las acciones**, selecciona **Permitir acciones seleccionadas** y agrega tus acciones requeridas a la lista. + {%- ifversion ghes %} + ![Agregar acciones a la lista de permitidos](/assets/images/help/repository/actions-policy-allow-list.png) + {%- else %} + ![Agregar acciones a la lista de permitidos](/assets/images/enterprise/github-ae/repository/actions-policy-allow-list.png) + {%- endif %} 2. Haz clic en **Save ** (guardar). {% endif %} {% ifversion fpt %} ## Configurar las aprobaciones requeridas para los flujos de trabajo desde las bifurcaciones pùblicas -{% data reusables.actions.workflow-run-approve-public-fork %} Puedes configurar este comportamiento para un repositorio utilizando el siguiente procedimiento. El modificar este ajuste anula la configuración que se haya hecho a nviel organizacional o empresarial. +{% data reusables.actions.workflow-run-approve-public-fork %} + +You can configure this behavior for a repository using the procedure below. El modificar este ajuste anula la configuración que se haya hecho a nviel organizacional o empresarial. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} @@ -120,8 +127,31 @@ También pueden configurarse los permisos predeterminados en los ajustes de la o 1. Da clic en **Guardar** para aplicar la configuración. {% endif %} +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## Permitir el acceso a los componentes en un repositorio interno + +{% note %} + +**Nota:** {% data reusables.gated-features.internal-repos %} + +{% endnote %} + +Los miembros de tu empresa pueden utilizar repositorios internos para trabajar en proyectos sin compartir información públicamente. Para obtener más información, consulta la sección "[Acerca de los repositorios](/repositories/creating-and-managing-repositories/about-repositories#about-internal-repositories)". + +Para configurar si se puede acceder desde un repositorio externo a los flujos de trabajo de un repositorio interno: + +1. En {% data variables.product.prodname_dotcom %}, navega hasta la página principal del repositorio interno. +1. Debajo de tu nombre de repositorio, haz clic en {% octicon "gear" aria-label="The gear icon" %}**Configuración**. +{% data reusables.repositories.settings-sidebar-actions %} +1. Debajo de **Acceso**, elige uno de los ajustes de acceso: ![Configurar el acceso a los componentes de las acciones](/assets/images/help/settings/actions-access-settings.png) + * **No accesible** - Los flujos de trabajo en otros repositorios no pueden utilizar flujos de trabajo en este repositorio. + * **Accesible mediante cualquier repositorio en la organización** - Los flujos de trabajo en otros repositorios pueden utilizar flujos de trabajo en este repositorio siempre y cuando sean parte de la misma organización. + * **Accesible mediante cualquier repositorio de la empresa** - Los flujos de trabajo de otros repositorios pueden utilizar a los de este, siempre y cuando sean parte de la misma empresa. +1. Da clic en **Guardar** para aplicar la configuración. +{% endif %} + {% ifversion fpt or ghes > 2.22 or ghae %} -## Configuring the retention period for {% data variables.product.prodname_actions %} artifacts and logs in your repository +## Configurar el periodo de retención de los artefactos y bitácoras de las {% data variables.product.prodname_actions %} en tu repositorio Puedes configurar el periodo de retenciòn para los artefactos de las {% data variables.product.prodname_actions %} y las bitàcoras en tu repositorio. diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/index.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/index.md index 1cf155f785..6e620a39af 100644 --- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/index.md +++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/index.md @@ -1,6 +1,6 @@ --- -title: Managing your repository’s settings and features -intro: 'You can customize your repository, enable or disable optional features for your repository, and manage your repository’s settings.' +title: Administrar la configuración y características de tu repositorio +intro: 'Puedes personalizar tu repositorio, habilitar o inhabilitar sus características opcionales y administrar la configuración de este.' redirect_from: - /categories/administering-a-repository - /articles/managing-repository-settings diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md index 20c2735f21..0edc2ab15f 100644 --- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md +++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md @@ -15,7 +15,7 @@ topics: shortTitle: Configurar los enlaces automáticos --- -Anyone with admin permissions to a repository can configure autolink references to link issues, pull requests, commit messages, and release descriptions to external third-party services. +Cualquier usuario con permisos de administración en un repositorio puede configurar referencias de enlace automático para vincular propuestas, solicitudes de cambios, mensajes de confirmación y descripciones de lanzamientos con los servicios externos de terceros. Si usas Zendesk para hacer el seguimiento de los tickets informados por el usuario, por ejemplo, puedes referenciar un número de ticket en la solicitud de extracción que abres para corregir el problema. diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/index.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/index.md index c8107186db..413ba28816 100644 --- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/index.md +++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/index.md @@ -1,6 +1,6 @@ --- title: Administrar configuraciones de repositorios -intro: You can choose the way your repository functions by managing repository settings. +intro: Puedes elegir la forma en la que funciona tu repositorio si administras la configuración de repositorios. versions: fpt: '*' ghes: '*' diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository.md index c060cc1755..cae00705c2 100644 --- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository.md +++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository.md @@ -18,7 +18,7 @@ redirect_from: Si eliges incluir los objetos de {% data variables.large_files.product_name_short %} en los archivos de tu repositorio, cada descarga de dichos archivos contará en el uso de ancho de banda para tu cuenta. Cada cuenta recibirá una {% data variables.large_files.initial_bandwidth_quota %} mensual de ancho de banda gratuito, y podrás pagar por cualquier uso adicional. Para obtener más información, consulta las secciones "[Acerca del uso del ancho de banda y del almacenamiento](/github/managing-large-files/about-storage-and-bandwidth-usage)" y "[Administrar la facturación para {% data variables.large_files.product_name_long %}](/billing/managing-billing-for-git-large-file-storage)". -If you use an external LFS server (configured in your `.lfsconfig`), those LFS files will not be included in archives of the repository. The archive will only contain files that have been committed to {% data variables.product.product_name %}. +Si utilizas un servidor LFS externo (configurado en tu `.lfsconfig`), estos archivos de LFS no se incluirán en los archivos del repositorio. El archivo solo contendrá archivos que se hayan confirmado en {% data variables.product.product_name %}. ## Administrar los objetos de {% data variables.large_files.product_name_short %} en los archivos diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md index 75847c0947..55a29f5cdc 100644 --- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md +++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md @@ -21,6 +21,12 @@ shortTitle: Visibilidad del repositorio Los propietarios de las organizaciones pueden restringir la capacidad de cambiar la visibilidad de un repositorio únicamente para otros propietarios de organizaciones. Para obtener más información, consulta la sección "[Restringir los cambios a la visibilidad del repositorio en tu organización](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)". +{% ifversion fpt %} + +Si eres un miembro de una {% data variables.product.prodname_emu_enterprise %}, los repositorios que pertenezcan a tu cuenta de usuario solo podrán ser privados, y aquellos en las organizaciones de tu empresa solo podrán ser privados o internos. + +{% endif %} + Te recomendamos revisar las siguientes consideraciones antes de que cambies la visibilidad de un repositorio. {% ifversion ghes or ghae %} @@ -90,4 +96,4 @@ Para obtener más información sobre cómo mejorar la seguridad del repositorio, ## Leer más -- "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)" +- "[Acerca de los repositorios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)" 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 3a484ad970..d5e78d8c0e 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 @@ -34,6 +34,9 @@ Puedes recibir notificaciones cuando se publican nuevos lanzamientos en un repos Cualquiera que tenga acceso de lectura a un repositorio podrá ver y comparar los lanzamientos, pero únicamente aquellos con permisos de escritura en éste podrán administrarlos. Para obtener más información, consulta "[Administrar lanzamientos en un repositorio](/github/administering-a-repository/managing-releases-in-a-repository)." {% ifversion fpt %} + +Puedes crear notas de lanzamiento manualmente mientras administras un lanzamiento. Como alternativa, puedes generar notas de lanzamiento automáticamente desde una plantilla predeterminada o personalizar tu propia plantilla de notas de lanzamiento. Para obtener más información, consulta la sección "[Notas de lanzamiento generadas automáticamente](/repositories/releasing-projects-on-github/automatically-generated-release-notes)". + Las personas con permisos administrativos sobre un repositorio pueden elegir si los objetos de {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) se incluirán en los archivos ZIP y en los archivos .tar que {% data variables.product.product_name %} crea para cada lanzamiento. Para obtener más información, consulta la sección "[Administrar los objetos de {% data variables.large_files.product_name_short %} en los archivos de tu repositorio](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)". {% endif %} diff --git a/translations/es-ES/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md b/translations/es-ES/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md new file mode 100644 index 0000000000..9cfda349aa --- /dev/null +++ b/translations/es-ES/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md @@ -0,0 +1,93 @@ +--- +title: Notas de lanzamiento generadas automáticamente +intro: Puedes generar notas de lanzamiento automáticamente para tus lanzamientos de GitHub +permissions: Repository collaborators and people with write access to a repository can generate and customize automated release notes for a release. +versions: + fpt: '*' +topics: + - Repositories +shortTitle: Notas de lanzamiento automatizadas +--- + +{% note %} + +**Nota:**{% data reusables.repositories.auto-gen-release-public-beta %} + +{% endnote %} + +## Acerca de las notas de lanzamiento generadas automáticamente + +Las notas de lanzamiento generadas automáticamente proporcionan una alternativa de automatización para escribir notas de lanzamiento manualmente para tus lanzamientos de {% data variables.product.prodname_dotcom %}. Con las notas de lanzamiento generadas automáticamente, puedes generar rápidamente un resumen del contenido de un lanzamiento. También puedes personalizar tus notas de lanzamiento automatizadas, utilizando etiquetas para crear categorías personalizadas para organizar las solicitudes de cambio que quieras incluir y excluyendo ciertas etiquetas y usuarios para que no aparezcan en la salida. + +## Crear notas de lanzamiento generadas automáticamente para un lanzamiento nuevo + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.releases %} +3. Haz clic en **Borrador de un nuevo lanzamiento**. ![Botón Borrador de lanzamientos](/assets/images/help/releases/draft_release_button.png) +4. {% ifversion fpt %}Haz clic en **Elige una etiqueta** y teclea {% else %}Teclea{% endif %} un número de versión para tu lanzamiento. Como alternativa, selecciona una etiqueta existente. + {% ifversion fpt %} + ![Ingresa una etiqueta](/assets/images/help/releases/releases-tag-create.png) +5. Si estás creando una etiqueta nueva, haz clic en **Crear etiqueta nueva**. ![Confirma si quieres crear una etiqueta nueva](/assets/images/help/releases/releases-tag-create-confirm.png) + {% else %} + ![Versión de lanzamientos con etiquetas](/assets/images/enterprise/releases/releases-tag-version.png) +{% endif %} +6. Si creaste una etiqueta nueva, utiliza el menú desplegable para seleccionar la rama que contiene el proyecto que quieres lanzar. + {% ifversion fpt %}![Elige una rama](/assets/images/help/releases/releases-choose-branch.png) + {% else %}![Rama de lanzamientos con etiquetas](/assets/images/enterprise/releases/releases-tag-branch.png) + {% endif %} +7. En la caja de texto de descripción que se encuentra en la esquina superior derecha, haz clic en **Autogenerar notas de lanzamiento**. ![Autogenerar notas de lanzamiento](/assets/images/help/releases/auto-generate-release-notes.png) +8. Verifica las notas generadas para garantizar que incluyan toda (y únicamente) la información que quieras incluir. +9. Opcionalmente, para incluir los archivos binarios tales como programas compilados en tu lanzamiento, arrastra y suelta o selecciona manualmente los archivos en la caja de binarios. ![Proporcionar un DMG con el lanzamiento](/assets/images/help/releases/releases_adding_binary.gif) +10. Para notificar a los usuarios que el lanzamiento no está listo para producción y puede ser inestable, selecciona **Esto es un pre-lanzamiento**. ![Casilla de verificación para marcar un lanzamiento como prelanzamiento](/assets/images/help/releases/prerelease_checkbox.png) +{%- ifversion fpt %} +11. Opcionalmente, selecciona **Crear un debate para este lanzamiento** y luego, selecciona el menú desplegable de **Categoría** y haz clic en aquella que describa el debate de dicho lanzamiento. ![Casilla de verificación para crear un debate de lanzamiento y menú desplegable para elegir una categoría](/assets/images/help/releases/create-release-discussion.png) +{%- endif %} +12. Si estás listo para publicitar tu lanzamiento, haz clic en **Publicar lanzamiento**. Para seguir trabajando luego en el lanzamiento, haz clic en **Guardar borrador**. ![Botones Publicar lanzamiento y Borrador de lanzamiento](/assets/images/help/releases/release_buttons.png) + + +## Crear una plantilla para las notas de lanzamiento generadas automáticamente + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.files.add-file %} +3. En el campo de nombre de archivo, teclea `.github/release.yml` para crear el archivo `release.yml` en el directorio `.github`. ![Crear archivo nuevo](/assets/images/help/releases/release-yml.png) +4. En el archivo, especifica las etiquetas y los autores de la solicitud de cambios a los cuales quieras excluir de este lanzamiento. También puedes crear categorías nuevas y listar las etiquetas de la solicitud de cambios que se deben incluir en cada una de ellas. Para obtener más información, consulta la sección "[Administrar etiquetas](/issues/using-labels-and-milestones-to-track-work/managing-labels)". + +## Ejemplo de configuración + +{% raw %} +**release.yml** +```yaml{:copy} +# release.yml + +changelog: + exclude: + labels: + - ignore-for-release + authors: + - octocat + categories: + - title: Breaking Changes 🛠 + labels: + - Semver-Major + - breaking-change + - title: Exciting New Features 🎉 + labels: + - Semver-Minor + - enhancement + - title: Other Changes + labels: + - "*" +``` +{% endraw %} + +## Sintaxis de las plantillas de lanzamiento + +| Parámetro | Descripción | Requerido | Valor | +|:------------ |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------------------------------------------------------------------------------------------------- |:----------------------------------------------------------------------------------------------- | +| `changelog` | Define el contenido dentro de esta como la plantilla personalizada para tus notas de lanzamiento. | Requerido. | No se aceptó ningún valor. | +| `exclude` | Crea una categoría de solicitudes de cambio a excluirse del lanzamiento. Puede configurarse en el nivel superior de la bitácora de cambios a aplicar a todas las categorías o a la que se aplicó por categoría. | Opcional | No se aceptó ningún valor. | +| `authors` | Especifica los autores que se deben excluir del lanzamiento. | Opcional para la categoría `exclude`. | Acepta los nombres de usuario y bots como valores. | +| `categories` | Define el contenido anidado como categorías personalizadas para que se incluya en la plantilla. | Opcional | No se aceptó ningún valor. | +| `title` | Crea una categoría ndividual. | Se requiere si existe el parámetro `categories`. | Toma el nombre de la categoría como su valor. | +| `labels` | Especifica las etiquetas que utilizará la categoría envolvente. | Se requiere si existe el parámetro `categories`, el cual es opcional para el parámetro `exclude`. | Acepta cualquier etiqueta, ya sea que existan actualmente o que estén planeadas para el futuro. | +| `"*"` | Catchall para cualquier solicitud de cambios que no se incluya dentro de alguna de las categorías *anteriores*. Si se utiliza, se debe agregar al final del archivo. | Opcional | No se aceptó ningún valor. | diff --git a/translations/es-ES/content/repositories/releasing-projects-on-github/index.md b/translations/es-ES/content/repositories/releasing-projects-on-github/index.md index 2ed251c415..f5efe2e5f1 100644 --- a/translations/es-ES/content/repositories/releasing-projects-on-github/index.md +++ b/translations/es-ES/content/repositories/releasing-projects-on-github/index.md @@ -17,6 +17,7 @@ children: - /viewing-your-repositorys-releases-and-tags - /linking-to-releases - /comparing-releases + - /automatically-generated-release-notes - /automation-for-release-forms-with-query-parameters shortTitle: Liberar proyectos --- diff --git a/translations/es-ES/content/repositories/releasing-projects-on-github/linking-to-releases.md b/translations/es-ES/content/repositories/releasing-projects-on-github/linking-to-releases.md index 12d96a0a3d..10ee4a2ba8 100644 --- a/translations/es-ES/content/repositories/releasing-projects-on-github/linking-to-releases.md +++ b/translations/es-ES/content/repositories/releasing-projects-on-github/linking-to-releases.md @@ -18,4 +18,4 @@ topics: 3. Encuentra el lanzamiento al que quieres enlazar y da clic en el número de versión. ![Información de la etiqueta de lanzamientos](/assets/images/help/releases/release_tag_name.png) 3. Como alternativa, da clic derecho en **Lanzamiento más Reciente** y copia la URL para compartirlo. El sufijo de esta URL siempre es `/releases/latest`. ![Etiqueta del último lanzamiento](/assets/images/help/releases/release_latest_release_tag.png) -To link directly to a download of your latest release asset that was manually uploaded, link to `/owner/name/releases/latest/download/asset-name.zip`. +Para enlazarlo directamente con una descarga de tu último activo de lanzamiento que se cargó manualmente, enlaza a `/owner/name/releases/latest/download/nombre-de-activo.zip`. diff --git a/translations/es-ES/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md b/translations/es-ES/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md index c391ef3dab..aedadc00f4 100644 --- a/translations/es-ES/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md +++ b/translations/es-ES/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md @@ -24,7 +24,7 @@ shortTitle: Administrar los lanzamientos ## Acerca de la administración de lanzamientos -You can create new releases with release notes, @mentions of contributors, and links to binary files, as well as edit or delete existing releases. +Puedes crear lanzamientos nuevos con notas de lanzamiento, @menciones de contribuyentes y enlaces a archivos binarios, así como editar o borrar los lanzamientos existentes. {% ifversion fpt %} También puedes publicar una acción desde un lanzamiento específico en {% data variables.product.prodname_marketplace %}. Para obtener más información, consulta la sección "Publicar una acción en {% data variables.product.prodname_marketplace %}". @@ -42,22 +42,24 @@ Puedes elegir si los objetos de {% data variables.large_files.product_name_long {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.releases %} 3. Haz clic en **Borrador de un nuevo lanzamiento**. ![Botón Borrador de lanzamientos](/assets/images/help/releases/draft_release_button.png) -4. {% ifversion fpt %}Click **Choose a tag** and type{% else %}Type{% endif %} a version number for your release. +4. {% ifversion fpt %}Haz clic en **Elige una etiqueta** y teclea {% else %}Teclea{% endif %} un número de versión para tu lanzamiento. Como alternativa, selecciona una etiqueta existente. {% ifversion fpt %} - ![Enter a tag](/assets/images/help/releases/releases-tag-create.png) -1. Click **Create new tag**. ![Confirm you want to create a new tag](/assets/images/help/releases/releases-tag-create-confirm.png) + ![Ingresa una etiqueta](/assets/images/help/releases/releases-tag-create.png) +1. Si estás creando una etiqueta nueva, haz clic en **Crear etiqueta nueva**. ![Confirma si quieres crear una etiqueta nueva](/assets/images/help/releases/releases-tag-create-confirm.png) {% else %} ![Versión de lanzamientos con etiquetas](/assets/images/enterprise/releases/releases-tag-version.png) {% endif %} -5. Utiliza el menú desplegable para seleccionar la rama que contiene el proyecto que quieres lanzar. - {% ifversion fpt %}![Choose a branch](/assets/images/help/releases/releases-choose-branch.png) +5. Si creaste una etiqueta nueva, utiliza el menú desplegable para seleccionar la rama que contiene el proyecto que quieres lanzar. + {% ifversion fpt %}![Elige una rama](/assets/images/help/releases/releases-choose-branch.png) {% else %}![Rama de lanzamientos con etiquetas](/assets/images/enterprise/releases/releases-tag-branch.png) {% endif %} 6. Escribe un título y una descripción para tu lanzamiento. {%- ifversion fpt or ghes > 3.2 or ghae-issue-4972 %} - If you @mention any {% data variables.product.product_name %} users in the description, the published release will include a **Contributors** section with an avatar list of all the mentioned users. + Si @mencionas a cualquier usuario de {% data variables.product.product_name %} en la descripción, el lanzamiento publicado incluirá una sección de **Contribuyentes** con una lista de avatares de los usuarios mencionados. {%- endif %} - ![Descripción de lanzamientos](/assets/images/help/releases/releases_description.png) + {% ifversion fpt %} Como alternativa, puedes generar tus notas de lanzamiento automáticamente dando clic en **Generar notas de lanzamiento automáticamente**. + {% endif %} + ![Descripción de lanzamientos](/assets/images/help/releases/releases_description_auto.png) 7. Opcionalmente, para incluir los archivos binarios tales como programas compilados en tu lanzamiento, arrastra y suelta o selecciona manualmente los archivos en la caja de binarios. ![Proporcionar un DMG con el lanzamiento](/assets/images/help/releases/releases_adding_binary.gif) 8. Para notificar a los usuarios que el lanzamiento no está listo para producción y puede ser inestable, selecciona **Esto es un pre-lanzamiento**. ![Casilla de verificación para marcar un lanzamiento como prelanzamiento](/assets/images/help/releases/prerelease_checkbox.png) {%- ifversion fpt %} @@ -66,9 +68,9 @@ Puedes elegir si los objetos de {% data variables.large_files.product_name_long 9. Si estás listo para publicitar tu lanzamiento, haz clic en **Publicar lanzamiento**. Para seguir trabajando luego en el lanzamiento, haz clic en **Guardar borrador**. ![Botones Publicar lanzamiento y Borrador de lanzamiento](/assets/images/help/releases/release_buttons.png) {%- ifversion fpt or ghes > 3.2 or ghae-issue-4972 %} - You can then view your published or draft releases in the releases feed for your repository. For more information, see "[Viewing your repository's releases and tags](/github/administering-a-repository/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags)." + Entonces podrás ver tus lanzamientos publicados o en borrador dentro de las noticias de lanzamientos de tu repositorio. Para obtener más información, consulta la sección "[Ver las etiquetas y lanzamientos de tu repositorio](/github/administering-a-repository/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags)". - ![Published release with @mentioned contributors](/assets/images/help/releases/releases-overview-with-contributors.png) + ![Lanzamiento publicado con contribuyentes @mencionados](/assets/images/help/releases/releases-overview-with-contributors.png) {%- endif %} {% endwebui %} @@ -77,19 +79,19 @@ Puedes elegir si los objetos de {% data variables.large_files.product_name_long {% data reusables.cli.cli-learn-more %} -1. To create a release, use the `gh release create` subcommand. Replace `tag` with the desired tag for the release. +1. Para crear un lanzamiento, utiliza el subcomando `gh release create`. Reemplaza `tag` con la etiqueta deseada para el lanzamiento. ```shell gh release create tag ``` -2. Follow the interactive prompts. Alternatively, you can specify arguments to skip these prompts. For more information about possible arguments, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_release_create). For example, this command creates a prerelease with the specified title and notes. +2. Sigue los mensajes interactivos. Como alternativa, puedes especificar los argumentos para omitir estos mensajes. Para obtener más información sobre los argumentos posibles, consulta [el manual de {% data variables.product.prodname_cli %}](https://cli.github.com/manual/gh_release_create). Por ejemplo, este comando crea un pre-lanzamiento con el título y notas especificados. ```shell gh release create v1.3.2 --title "v1.3.2 (beta)" --notes "this is a beta release" --prerelease ``` {% ifversion fpt or ghes > 3.2 or ghae-issue-4972 %} -If you @mention any {% data variables.product.product_name %} users in the notes, the published release on {% data variables.product.prodname_dotcom_the_website %} will include a **Contributors** section with an avatar list of all the mentioned users. +Si @mencionas a cualquier usuario de {% data variables.product.product_name %} en las notas, el lanzamiento publicado en el {% data variables.product.prodname_dotcom_the_website %} incluirá una sección de **Contribuyentes** con una lista de avatares de todos los usuarios mencionados. {% endif %} {% endcli %} @@ -103,13 +105,13 @@ If you @mention any {% data variables.product.product_name %} users in the notes {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.releases %} 3. En la parte derecha de la página, junto al lanzamiento que quieres editar, da clic en **Editar lanzamiento**. ![Editar un lanzamiento](/assets/images/help/releases/edit-release.png) -4. Edit the details for the release in the form, then click **Update release**.{% ifversion fpt or ghes > 3.2 or ghae-issue-4972 %} If you add or remove any @mentions of GitHub users in the description, those users will be added or removed from the avatar list in the **Contributors** section of the release.{% endif %} ![Actualizar un lanzamiento](/assets/images/help/releases/update-release.png) +4. Edita los detalles del lanzamiento en el formato, luego haz clic en **Actualizar lanzamiento**.{% ifversion fpt or ghes > 3.2 or ghae-issue-4972 %} Si agregas o eliminas cualquier @mención de los usuarios de GitHub en la descripción, estos se agregarán o eliminarán de la lista de avatares en la sección de **Contribuyentes** del lanzamiento.{% endif %} ![Actualizar un lanzamiento](/assets/images/help/releases/update-release.png) {% endwebui %} {% cli %} -Releases cannot currently be edited with {% data variables.product.prodname_cli %}. +Los lanzamientos no pueden editarse con {% data variables.product.prodname_cli %} actualmente. {% endcli %} @@ -129,7 +131,7 @@ Releases cannot currently be edited with {% data variables.product.prodname_cli {% cli %} -1. To delete a release, use the `gh release delete` subcommand. Replace `tag` with the tag of the release to delete. Use the `-y` flag to skip confirmation. +1. Para borrar un lanzamiento, utiliza el subcomando `gh release delete`. Reemplaza `tag` con la etiqueta del lanzamiento que se debe borrar. Utiliza el marcador `-y` para omitir la confirmación. ```shell gh release delete tag -y diff --git a/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/analyzing-changes-to-a-repositorys-content.md b/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/analyzing-changes-to-a-repositorys-content.md index e9baf7c4d7..7236f0e453 100644 --- a/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/analyzing-changes-to-a-repositorys-content.md +++ b/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/analyzing-changes-to-a-repositorys-content.md @@ -19,7 +19,7 @@ versions: ghae: '*' topics: - Repositories -shortTitle: Analyze changes +shortTitle: Analizar cambios --- ## Ver confirmaciones en un repositorio @@ -40,7 +40,7 @@ El gráfico inferior muestra la cantidad promedio de confirmaciones por día de {% data reusables.repositories.accessing-repository-graphs %} 3. En la barra lateral izquierda, haz clic en **Commits (Confirmaciones)**. ![Pestaña de confirmaciones](/assets/images/help/graphs/commits_tab.png) -## Visualizing additions and deletion to content in a repository +## Ver incorporaciones y eliminaciones del contenido de un repositorio El gráfico de frecuencia de código muestra las incorporaciones y eliminaciones de contenido de cada semana en el historial de un repositorio. diff --git a/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/index.md b/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/index.md index b3496b376a..5223052ccf 100644 --- a/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/index.md +++ b/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/index.md @@ -1,6 +1,6 @@ --- -title: Viewing activity and data for your repository -intro: Gain insight into your repository by viewing activity and data. +title: Ver la actividad y los datos de tu repositorio +intro: Obtén perspectivas en tu repositorio viendo su actividad y datos. redirect_from: - /categories/44/articles - /categories/graphs-and-contributions @@ -23,6 +23,6 @@ children: - /understanding-connections-between-repositories - /about-the-dependency-graph - /exploring-the-dependencies-of-a-repository -shortTitle: View activity and data +shortTitle: Ver la actividad y datos --- 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 07def8d65a..03d197a375 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 @@ -1,6 +1,6 @@ --- title: Entender las conexiones entre repositorios -intro: You can better understand the connections that exist between repositories by viewing a repository's network and forks and the projects that depend on the repository. +intro: Puedes entender mejor las conexiones que existen entre los repositorios si ves la red y las bifurcaciones de este y los proyectos que dependen de él. redirect_from: - /articles/viewing-a-repository-s-network - /articles/viewing-a-repositorys-network @@ -19,12 +19,12 @@ versions: ghae: '*' topics: - Repositories -shortTitle: Connections between repositories +shortTitle: Conexiones entre repositorios --- ## Ver la red de un repositorio -'The network graph displays the branch history of the entire repository network, including branches of the root repository and branches of forks that contain commits unique to the network.' product: '{% data reusables.gated-features.repository-insights %}' +'La gráfica de red muestra el historial de ramas de toda la red del repositorio, incluyendo las ramas en el repositorio raíz y las ramas de las bifurcaciones que contienen confirmaciones únicas para la red'. producto: '{% data reusables.gated-features.repository-insights %}' ![Gráfico de red del repositorio](/assets/images/help/graphs/repo_network_graph.png) diff --git a/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-summary-of-repository-activity.md b/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-summary-of-repository-activity.md index 1a5ed5e31e..b936ed3275 100644 --- a/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-summary-of-repository-activity.md +++ b/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-summary-of-repository-activity.md @@ -1,6 +1,6 @@ --- title: Ver un resumen de la actividad de un repositorio -intro: 'You can view an overview of a repository''s pull request, issue, and commit activity.' +intro: 'Puedes ver un resumen de la solicitud de cambios, propuesta y actividad de confirmación de un repositorio.' product: '{% data reusables.gated-features.repository-insights %}' redirect_from: - /articles/viewing-a-summary-of-repository-activity @@ -15,13 +15,13 @@ topics: shortTitle: Visualizar la actividad de los repositorios --- -## About Pulse +## Acerca de Pulse -Puedes ver un resumen de la actividad de un repositorio a través de Pulse. Pulse includes a list of open and merged pull requests, open and closed issues, and a graph showing the commit activity for the top 15 users who committed to the default branch of the project in the selected [time period](/articles/viewing-a-summary-of-repository-activity#filtering-by-time). +Puedes ver un resumen de la actividad de un repositorio a través de Pulse. Pulse incluye una lista de solicitudes de cambios abiertas y fusionadas, propuestas abiertas y cerradas y una gráfica que muestra la actividad de la confirmación para los principales 15 usuarios que hicieron confirmaciones en la rama predeterminada del proyecto en el [periodo de tiempo](/articles/viewing-a-summary-of-repository-activity#filtering-by-time) seleccionado. Los coautores de confirmación están incluidos en el resumen de actividad de confirmación si sus confirmaciones fueron fusionadas dentro de la rama por defecto del repositorio y están en los 15 usuarios principales que contribuyeron en la mayoría de las confirmaciones. -## Accessing Pulse +## Acceder a Pulse {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.accessing-repository-graphs %} diff --git a/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository.md b/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository.md index e7086bf8f3..4d83618945 100644 --- a/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository.md +++ b/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository.md @@ -27,7 +27,7 @@ También puedes ver información de implementación en la pestaña "Conversation ## Ver el tablero de implementaciones {% data reusables.repositories.navigate-to-repo %} -2. To the right of the list of files, click **Environments**. ![Environments on the right of the repository page](/assets/images/help/repository/environments.png) +2. A la derecha de la lista de archivos, haz clic en **Ambientes**. ![Ambientes a la derecha de la página del repositorio](/assets/images/help/repository/environments.png) ## Leer más - "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)" diff --git a/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/viewing-traffic-to-a-repository.md b/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/viewing-traffic-to-a-repository.md index ce43903d49..3c8b4f2c1b 100644 --- a/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/viewing-traffic-to-a-repository.md +++ b/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/viewing-traffic-to-a-repository.md @@ -10,7 +10,7 @@ versions: fpt: '*' topics: - Repositories -shortTitle: View repository traffic +shortTitle: Ver el tráfico del repositorio --- Puedes desplazarte a los sitios de referencia, excluidos los motores de búsqueda y {% data variables.product.product_name %} propiamente dicho, desde los vínculos donde se hizo la referencia a las rutas específicas. El contenido popular vincula al contenido específico que generó tráfico. diff --git a/translations/es-ES/content/repositories/working-with-files/index.md b/translations/es-ES/content/repositories/working-with-files/index.md index 679311a1a0..c8fa23f840 100644 --- a/translations/es-ES/content/repositories/working-with-files/index.md +++ b/translations/es-ES/content/repositories/working-with-files/index.md @@ -1,6 +1,6 @@ --- -title: Working with files -intro: Learn how to manage and use files in repositories. +title: Trabajar con los archivos +intro: Aprende cómo adminstrar y utilizar los archivos en los repositorios. redirect_from: - /categories/81/articles/ - /categories/manipulating-files/ @@ -16,6 +16,6 @@ children: - /managing-files - /using-files - /managing-large-files -shortTitle: Work with files +shortTitle: Trabajar con los archivos --- diff --git a/translations/es-ES/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md b/translations/es-ES/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md index e8c2555a86..f0fbd3b913 100644 --- a/translations/es-ES/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md +++ b/translations/es-ES/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md @@ -1,6 +1,6 @@ --- title: Agregar un archivo a un repositorio -intro: 'You can upload and commit an existing file to a repository on {% data variables.product.product_name %} or by using the command line.' +intro: 'Puedes cargar y confirmar un archivo existente a un repositorio de {% data variables.product.product_name %} o utilizando la línea de comandos.' redirect_from: - /articles/adding-a-file-to-a-repository - /github/managing-files-in-a-repository/adding-a-file-to-a-repository @@ -18,7 +18,7 @@ topics: shortTitle: Agregar un archivo --- -## Adding a file to a repository on {% data variables.product.product_name %} +## Agregar un archivo a un repositorio en {% data variables.product.product_name %} Los archivos que agregues a un repositorio mediante un navegador están limitados a {% data variables.large_files.max_github_browser_size %} por archivo. Puedes agregar archivos más grandes, de hasta {% data variables.large_files.max_github_size %} cada uno, mediante la línea de comando. Para obtener más información, consulta "[Agregar un archivo a un repositorio mediante la línea de comando](#adding-a-file-to-a-repository-using-the-command-line)". diff --git a/translations/es-ES/content/repositories/working-with-files/managing-files/editing-files.md b/translations/es-ES/content/repositories/working-with-files/managing-files/editing-files.md index f6db99a2cd..cb14ab526b 100644 --- a/translations/es-ES/content/repositories/working-with-files/managing-files/editing-files.md +++ b/translations/es-ES/content/repositories/working-with-files/managing-files/editing-files.md @@ -1,5 +1,5 @@ --- -title: Editing files +title: Editar archivos intro: 'Puedes editar archivos directamente en {% data variables.product.product_name %} en cualquiera de tus repositorios usando el editor de archivos.' redirect_from: - /articles/editing-files/ @@ -15,7 +15,7 @@ versions: ghae: '*' topics: - Repositories -shortTitle: Edit files +shortTitle: Editar archivos --- ## Editar archivos en tu repositorio @@ -43,7 +43,7 @@ shortTitle: Edit files ## Editar archivos en el repositorio de otro usuario -When you edit a file in another user's repository, we'll automatically [fork the repository](/articles/fork-a-repo) and [open a pull request](/articles/creating-a-pull-request) for you. +Cuando editas un archivo en el repositorio de otro usuario, automáticamente [bifurcaremos el repositorio](/articles/fork-a-repo) y [abriremos una solicitud de cambios](/articles/creating-a-pull-request) para ti. 1. En el repositorio de otro usuario, dirígete a la carpeta que contiene el archivo que deseas editar. Haz clic en el nombre del archivo que deseas editar. 2. Sobre el contenido del archivo, haz clic en {% octicon "pencil" aria-label="The edit icon" %}. En este punto del proceso, GitHub bifurca el repositorio por ti. diff --git a/translations/es-ES/content/repositories/working-with-files/managing-files/index.md b/translations/es-ES/content/repositories/working-with-files/managing-files/index.md index 19779580a9..7951d9e444 100644 --- a/translations/es-ES/content/repositories/working-with-files/managing-files/index.md +++ b/translations/es-ES/content/repositories/working-with-files/managing-files/index.md @@ -1,6 +1,6 @@ --- title: Administrar archivos -intro: 'You can create, edit, move, and delete files in a repository, directly on {% data variables.product.product_name %} or on the command line.' +intro: 'Puedes crear, editar, mover y borrar archivos en un repositorio, directamente en {% data variables.product.product_name %} o en la línea de comandos.' redirect_from: - /articles/managing-files-on-github - /github/managing-files-in-a-repository/managing-files-on-github diff --git a/translations/es-ES/content/repositories/working-with-files/managing-files/moving-a-file-to-a-new-location.md b/translations/es-ES/content/repositories/working-with-files/managing-files/moving-a-file-to-a-new-location.md index b8c535948a..bc14c4b566 100644 --- a/translations/es-ES/content/repositories/working-with-files/managing-files/moving-a-file-to-a-new-location.md +++ b/translations/es-ES/content/repositories/working-with-files/managing-files/moving-a-file-to-a-new-location.md @@ -1,6 +1,6 @@ --- title: Mover un archivo a una nueva ubicación -intro: 'You can move a file to a different directory on {% data variables.product.product_name %} or by using the command line.' +intro: 'Puedes mover un archivo a un directorio diferente desde {% data variables.product.product_name %} o utilizando la línea de comandos.' redirect_from: - /articles/moving-a-file-to-a-new-location - /github/managing-files-in-a-repository/moving-a-file-to-a-new-location @@ -19,7 +19,7 @@ shortTitle: Mover un archivo Además de cambiar la ubicación del archivo, también puedes [actualizar los contenidos de tu archivo](/articles/editing-files-in-your-repository), o [darle un nuevo nombre](/articles/renaming-a-file) en la misma confirmación. -## Moving a file to a new location on {% data variables.product.product_name %} +## Migrar un archivo a una ubicación nueva en {% data variables.product.product_name %} {% tip %} diff --git a/translations/es-ES/content/repositories/working-with-files/managing-files/renaming-a-file.md b/translations/es-ES/content/repositories/working-with-files/managing-files/renaming-a-file.md index 292b9388ae..276c1e150b 100644 --- a/translations/es-ES/content/repositories/working-with-files/managing-files/renaming-a-file.md +++ b/translations/es-ES/content/repositories/working-with-files/managing-files/renaming-a-file.md @@ -1,6 +1,6 @@ --- title: Renombrar un archivo -intro: 'You can rename any file in your repository directly in {% data variables.product.product_name %} or by using the command line.' +intro: 'Puedes renombrar cualquier archivo en tu repositorio directamente en {% data variables.product.product_name %} o utilizando la línea de comandos.' redirect_from: - /articles/renaming-a-file - /github/managing-files-in-a-repository/renaming-a-file @@ -16,9 +16,9 @@ topics: - Repositories --- -## Renaming a file on {% data variables.product.product_name %} +## Renombrar un archivo en {% data variables.product.product_name %} -Renaming a file also gives you the opportunity to [move the file to a new location](/articles/moving-a-file-to-a-new-location) +El renombrar un archivo también te da la oportunidad de [mover el archivo a una ubicación nueva](/articles/moving-a-file-to-a-new-location) {% tip %} diff --git a/translations/es-ES/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md b/translations/es-ES/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md index f6bb3328be..1a4bfe72a3 100644 --- a/translations/es-ES/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md +++ b/translations/es-ES/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md @@ -1,6 +1,6 @@ --- title: Acerca de Large File Storage de Git -intro: '{% data variables.product.product_name %} limits the size of files allowed in repositories. To track files beyond this limit, you can use {% data variables.large_files.product_name_long %}.' +intro: '{% data variables.product.product_name %} limita el tamaño de los archivos permitidos en los repositorios. Para rastrear los archivos más allá de este límite, puedes utilizar {% data variables.large_files.product_name_long %}.' redirect_from: - /articles/about-large-file-storage/ - /articles/about-git-large-file-storage diff --git a/translations/es-ES/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md b/translations/es-ES/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md index 0a1b6d6aac..2796fa2f8c 100644 --- a/translations/es-ES/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md +++ b/translations/es-ES/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md @@ -1,6 +1,6 @@ --- -title: About large files on GitHub -intro: '{% data variables.product.product_name %} limits the size of files you can track in regular Git repositories. Learn how to track or remove files that are beyond the limit.' +title: Acerca de los archivos grandes en GitHub +intro: '{% data variables.product.product_name %} limita el tamaño de los archivos que puedes rastrear en los repositorios regulares de Git. Aprende cómo rastrear o eliminar archivos que sobrepasan el límite.' redirect_from: - /articles/distributing-large-binaries - /github/managing-large-files/distributing-large-binaries @@ -20,18 +20,18 @@ versions: fpt: '*' ghes: '*' ghae: '*' -shortTitle: Large files +shortTitle: Archivos grandes --- -## About size limits on {% data variables.product.product_name %} +## Acerca de los límites de tamaño en {% data variables.product.product_name %} {% ifversion fpt %} {% data variables.product.product_name %} intenta proporcionar almacenamiento abundante para todos los repositorios de Git, aunque existen límites físicos para los tamaños de los archivos y repositorios. Para garantizar el rendimiento y la legibilidad para nuestros usuarios, monitoreamos activamente las señales de la salud general de los repositorios. La salud de los repositorios es una función de varios factores de interacción, incluyendo el tamaño, frecuencia de confirmaciones y estructura. -### File size limits +### Límites de tamaño de archivos {% endif %} -{% data variables.product.product_name %} limits the size of files allowed in repositories. Recibirás una advertencia de Git si intentas añadir o actualizar un archivo mayor a {% data variables.large_files.warning_size %}. Los cambios aún se subirán a tu repositorio, pero puedes considerar eliminar la confirmación para minimizar el impacto en el rendimiento. Para obtener información, consulta [Eliminar archivos del historial de un repositorio](#removing-files-from-a-repositorys-history)" +{% data variables.product.product_name %} limita el tamaño de los archivos permitidos en los repositorios. Recibirás una advertencia de Git si intentas añadir o actualizar un archivo mayor a {% data variables.large_files.warning_size %}. Los cambios aún se subirán a tu repositorio, pero puedes considerar eliminar la confirmación para minimizar el impacto en el rendimiento. Para obtener información, consulta [Eliminar archivos del historial de un repositorio](#removing-files-from-a-repositorys-history)" {% note %} @@ -39,16 +39,16 @@ shortTitle: Large files {% endnote %} -{% ifversion ghes %}Predeterminadamente, {% endif %}{% data variables.product.product_name %} bloquea las subidas que excedan {% data variables.large_files.max_github_size %}. {% ifversion ghes %}Sin embargo, un administrador de sitio puede configurar un límite diferente para {% data variables.product.product_location %}. For more information, see "[Setting Git push limits](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-git-push-limits)."{% endif %} +{% ifversion ghes %}Predeterminadamente, {% endif %}{% data variables.product.product_name %} bloquea las subidas que excedan {% data variables.large_files.max_github_size %}. {% ifversion ghes %}Sin embargo, un administrador de sitio puede configurar un límite diferente para {% data variables.product.product_location %}. Para obtener más información, consulta la sección "[Configurar los límites de subida de Git](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-git-push-limits)".{% endif %} -To track files beyond this limit, you must use {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}). Para obtener más información, consulta la sección "[Acerca de {% data variables.large_files.product_name_long %}](/repositories/working-with-files/managing-large-files/about-git-large-file-storage)". +Para rastrear archivos que sobrepasen este límite, debes utilizar {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}). Para obtener más información, consulta la sección "[Acerca de {% data variables.large_files.product_name_long %}](/repositories/working-with-files/managing-large-files/about-git-large-file-storage)". -If you need to distribute large files within your repository, you can create releases on {% data variables.product.product_location %} instead of tracking the files. Para obtener más información, consulta la sección "[Distribuir archivos binarios grandes](#distributing-large-binaries)". +Si necesitas distribuir archivos grandes dentro de tu repositorio, puedes crear lanzamientos en {% data variables.product.product_location %} en vez de rastrear los archivos. Para obtener más información, consulta la sección "[Distribuir archivos binarios grandes](#distributing-large-binaries)". -Git is not designed to handle large SQL files. Para compartir bases de datos grandes con otros desarrolladores, te recomendamos utilizar [Dropbox](https://www.dropbox.com/). +Git no se diseñó para manejar archivos grandes de SQL. Para compartir bases de datos grandes con otros desarrolladores, te recomendamos utilizar [Dropbox](https://www.dropbox.com/). {% ifversion fpt %} -### Repository size limits +### Límites de tamaño de repositorio Te recomendamos que los repositorios sean siempre pequeños, idealmente, de menos de 1 GB, y se recomienda ampliamente que sean de menos de 5GB. Los repositorios más pequeños se clonan más rápido y se puede mantenerlos mejor y trabajar en ellos más fácilmente. Si tu repositorio impacta excesivamente nuestra infraestructura, puede que recibas un mensaje de correo electrónico de {% data variables.contact.github_support %}, el cual te solicitará que tomes acciones correctivas. Intentamos ser flexibles, especialmente con proyectos grandes que tienen muchos colaboradores, y trabajaremos junto contigo para encontrar una resolución cada que sea posible. Puedes prevenir que tu repositorio impacte nuestra infraestructura si administras el tamaño de tu repositorio y su salud general con eficacia. Puedes encontrar consejos y una herramienta para análisis de repositorios en el repositorio [`github/git-sizer`](https://github.com/github/git-sizer). diff --git a/translations/es-ES/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md b/translations/es-ES/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md index 9ca00b1a81..77013dfc5b 100644 --- a/translations/es-ES/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md +++ b/translations/es-ES/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md @@ -21,7 +21,7 @@ Cuando confirmas y subes un cambio a un archivo seguido con {% data variables.la Por ejemplo: - Si subes un archivo de 500 MB a {% data variables.large_files.product_name_short %}, usarás 500 MB de tu almacenamiento asignado y nada de tu ancho de banda. Si realizas un cambio de 1 byte y subes el archivo de nuevo, usarás otros 500 MB de almacenamiento y no de ancho de banda, llevando tu uso total por esas dos subidas a 1 GB de almacenamiento y cero ancho de banda. - Si descargas un archivo de 500 MB que es seguido con LFS, usarás 500 MB del ancho de banda asignado del propietario del repositorio. Si un colaborador sube un cambio al archivo y extraes la versión nueva a tu repositorio local, usarás otros 500 MB de ancho de banda, llevando el uso total por esas dos descargas a 1 GB de ancho de banda. -- If {% data variables.product.prodname_actions %} downloads a 500 MB file that is tracked with LFS, it will use 500 MB of the repository owner's allotted bandwidth. +- Si {% data variables.product.prodname_actions %} descarga un archivo de 500 MB que se rastree con LFS, este utilizará 500 MB del ancho de banda asignado al repositorio del propietario. {% ifversion fpt %} Si los objetos de {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) se incluyen en los archivos de código fuente para tu repositorio, las descargas de estos archivos contarán en el uso de ancho de banda para el repositorio. Para obtener más información, consulta la sección "[Administrar los objetos de {% data variables.large_files.product_name_short %} en los archivos de tu repositorio](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)". diff --git a/translations/es-ES/content/repositories/working-with-files/using-files/index.md b/translations/es-ES/content/repositories/working-with-files/using-files/index.md index 896fefe26c..6b4bbf4ceb 100644 --- a/translations/es-ES/content/repositories/working-with-files/using-files/index.md +++ b/translations/es-ES/content/repositories/working-with-files/using-files/index.md @@ -1,6 +1,6 @@ --- -title: Using files -intro: 'You can navigate and track changes in the code in your files.' +title: Utilizar los archivos +intro: Puedes navegar y rastrear los cambios en el código de tus archivos. versions: fpt: '*' ghes: '*' diff --git a/translations/es-ES/content/repositories/working-with-files/using-files/working-with-non-code-files.md b/translations/es-ES/content/repositories/working-with-files/using-files/working-with-non-code-files.md index a678a73c17..bbb3acdcc4 100644 --- a/translations/es-ES/content/repositories/working-with-files/using-files/working-with-non-code-files.md +++ b/translations/es-ES/content/repositories/working-with-files/using-files/working-with-non-code-files.md @@ -1,6 +1,6 @@ --- title: Trabajar con archivos sin código -intro: '{% data variables.product.product_name %} supports rendering and diffing in a number of non-code file formats.' +intro: '{% data variables.product.product_name %} es compatible con interpretar y diferenciar varios formatos de archivo que no son de código.' redirect_from: - /articles/rendering-and-diffing-images - /github/managing-files-in-a-repository/rendering-and-diffing-images @@ -188,6 +188,14 @@ Puedes hacer clic en {% octicon "file" aria-label="The paper icon" %} para ver l ![Cambios en prosa representados](/assets/images/help/repository/rendered_prose_changes.png) +{% ifversion fpt or ghes > 3.2 or ghae-issue-5232 %} + +### Inhabilitar la representación del lenguaje de marcado + +{% data reusables.repositories.disabling-markdown-rendering %} + +{% endif %} + ### Ver los cambios del atributo Proporcionamos una información de herramienta que describe los cambios en los atributos que, a diferencia de las palabras, no serían visibles en el documento representado. Por ejemplo, si la URL de un enlace cambia de un sitio web a otro, mostraríamos una información de herramienta como la siguiente: @@ -216,7 +224,7 @@ No admitimos directamente vistas representadas de confirmaciones en documentos H En general, las vistas representadas de los cambios en un documento que contiene HTML insertados mostrarán los cambios en los elementos que se admiten en la vista del documento de {% data variables.product.product_name %}. Los cambios en los documentos que contienen HTML insertados siempre se deben verificar en las vistas de origen y representada para corroborar que estén todos. -## Mapping geoJSON files on {% data variables.product.prodname_dotcom %} +## Mapear archivos de geoJSON en {% data variables.product.prodname_dotcom %} {% data variables.product.product_name %} admite representar archivos de mapa geoJSON y topoJSON dentro de repositorios {% data variables.product.product_name %}. Simplemente confirma el archivo como lo harías normalmente utilizando una extensión `.geojson` o `.topojson`. También se admiten archivos con una extensión `.json`, pero únicamente si `type` están configurados para `FeatureCollection`, `GeometryCollection`, o `topology`. Después, navega hasta la ruta del archivo geoJSON en GitHub.com. @@ -289,9 +297,9 @@ Todavía se podrían representar los datos al convertir el archivo `.geojson` a * [Documentación de estilización de marcador MapBox](http://www.mapbox.com/developers/simplestyle/) * [TopoJSON Wiki](https://github.com/mbostock/topojson/wiki) -## Working with Jupyter Notebook files on {% data variables.product.prodname_dotcom %} +## Trabajar con arhivos de Jupyter Notebook en {% data variables.product.prodname_dotcom %} -When you add Jupyter Notebook or IPython Notebook files with a *.ipynb* extension on {% data variables.product.product_location %}, they will render as static HTML files in your repository. +Cuando agregas archivos de Jupyter Notebook o IPython Notebook con una extensión *.ipynb* en {% data variables.product.product_location %}, estas se interpretarán como archivos HTML estáticos en tu repositorio. Las funciones interactivas de notebook, como los gráficos JavaScript personalizados, no funcionarán en tu repositorio en {% data variables.product.product_location %}. Para obtener un ejemplo, consulta [*Enlaces e interacciones.ipynb*](https://github.com/bokeh/bokeh-notebooks/blob/main/tutorial/06%20-%20Linking%20and%20Interactions.ipynb). diff --git a/translations/es-ES/content/rest/README.md b/translations/es-ES/content/rest/README.md index 7505685603..efed3e03b1 100644 --- a/translations/es-ES/content/rest/README.md +++ b/translations/es-ES/content/rest/README.md @@ -7,4 +7,4 @@ El contenido que se procesa con las etiquetas de `include` se toma del directorio `/lib/rest/static`, el cual se genera automáticamente desde el código abierto de la API en GitHub y no debe editarlo ninguna persona. Para obtener más información, consulta el archivo [`/lib/rest/README.md`](/lib/rest/README.md). - **We cannot accept changes to content that is rendered by `include` tags. However, you can open an issue describing the changes you would like to see.** + **No podemos aceptar cambios al contenido que interpretan las etiquetas de `include`. Sin embargo, puedes abrir una propuesta que describa los cambios que te gustaría ver.** 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 e5cb87863b..10209f69c3 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 @@ -122,10 +122,10 @@ $ curl -i -u your_username {% data variables.product.api_url_pre %}/use Cuando se te solicite, puedes ingresar tu token de OAuth, pero te recomendamos que configures una variable para éste: -Puedes utilizar `-u "username:$token"` y configurar una variable para `token` y así evitar el dejar tu token en el historial del shell, lo cual debe evitarse. +Puedes utilizar `-u "your_username:$token"` y configurar una variable para `token` y así evitar que tu token se quede en el historial del shell, lo cual debes evitar. ```shell -$ curl -i -u username:$token {% data variables.product.api_url_pre %}/users/octocat +$ curl -i -u your_username:$token {% data variables.product.api_url_pre %}/users/octocat ``` diff --git a/translations/es-ES/content/rest/overview/api-previews.md b/translations/es-ES/content/rest/overview/api-previews.md index 9cf258f067..329f254990 100644 --- a/translations/es-ES/content/rest/overview/api-previews.md +++ b/translations/es-ES/content/rest/overview/api-previews.md @@ -18,13 +18,7 @@ Durante el periodo de vista previa, podríamos cambiar algunas características Para acceder a la vista previa de las API, necesitarás proporcionar un [tipo de medios](/rest/overview/media-types) personalizado en el encabezado `Accept` para tus solicitudes. La documentación de características para cada vista previa especifica qué tipo de medios personalizados proporcionar. -{% ifversion fpt %} -## Migraciones - -Te permite descargar repositorios desde tu usuario de GitHub o cuenta organizacional para revisar, respaldar y [migrar](/rest/reference/migrations) los datos al {% data variables.product.prodname_ghe_server %}. - -**Tipo de medios personalizados:** `wyandotte-preview` **Anunciado en:**[2018-05-24](https://developer.github.com/changes/2018-05-24-user-migration-api/) -{% endif %} +{% ifversion ghes < 3.3 %} ## Despliegues ampliados @@ -32,18 +26,28 @@ Ejerce mayo control sobre los [despliegues](/rest/reference/repos#deployments) c **Tipo de medios personalizados:** `ant-man-preview` **Anunciado en:**[2016-04-06](https://developer.github.com/changes/2016-04-06-deployment-and-deployment-status-enhancements/) +{% endif %} + +{% ifversion ghes < 3.3 %} + ## Reacciones Administra las [reacciones](/rest/reference/reactions) para las confirmaciones, informes de problemas y comentarios. **Tipo de medios personalizado:** `squirrel-girl-preview` **Anunciado en:** [2016-05-12](https://developer.github.com/changes/2016-05-12-reactions-api-preview/) **Actualizado en:** [2016-06-07](https://developer.github.com/changes/2016-06-07-reactions-api-update/) +{% endif %} + +{% ifversion ghes < 3.3 %} + ## Línea de tiempo Obtén una [lista de eventos](/rest/reference/issues#timeline) para un informe de problemas o solictud de extracción. **Tipo de medios personalizados:** `mockingbird-preview` **Anunciado en:**[2016-05-23](https://developer.github.com/changes/2016-05-23-timeline-preview-api/) +{% endif %} + {% ifversion ghes %} ## Ambientes de pre-recepción @@ -52,11 +56,13 @@ Crea, lista, actualiza y borra ambientes para los ganchos de pre-recepción. **Tipo de medios personalizados:** `eye-scream-preview` **Anunciado en:**[2015-07-29](/rest/reference/enterprise-admin#pre-receive-environments) {% endif %} +{% ifversion ghes < 3.3 %} ## Proyectos Administra [proyectos](/rest/reference/projects). **Tipo de medios personalizado:** `inertia-preview` **Anunciado en:** [2016-09-14](https://developer.github.com/changes/2016-09-14-projects-api/) **Actualizado en:** [2016-10-27](https://developer.github.com/changes/2016-10-27-changes-to-projects-api/) +{% endif %} ## Búsqueda de confirmación @@ -70,12 +76,16 @@ Ver una lista de los [temas del repositorio](/articles/about-topics/) en [llamad **Tipo de medios personalizados:** `mercy-preview` **Anunciado en:**[2017-01-31](https://github.com/blog/2309-introducing-topics) +{% ifversion ghes < 3.3 %} + ## Códigos de conducta Ver todos los [códigos de conducta](/rest/reference/codes-of-conduct) u obtener qué código de conducta tiene actualmente un repositorio. **Tipo de medios personalizado:** `scarlet-witch-preview` +{% endif %} + {% ifversion ghae or ghes %} ## Webhooks globales @@ -93,12 +103,16 @@ Ahora puedes utilizar la API para administrar la configuración para [requerir c **Tipo de medios personalizados:** `zzzax-preview` **Anunciado en:**[2018-02-22](https://developer.github.com/changes/2018-02-22-protected-branches-required-signatures) +{% ifversion ghes < 3.3 %} + ## Requerir múltiples revisiones de aprobación Ahora puedes [requerir múltiples revisiones de aprobación](/rest/reference/repos#branches) para una solicitud de extracción que utilice la API. **Tipo de medios personalizados:** `luke-cage-preview` **Anunciado en:**[2018-03-16](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews) +{% endif %} + {% ifversion ghes < 3.0 %} ## API de suites de verificación y ejecuciones de verificación @@ -135,30 +149,42 @@ Los Manifiestos de las GitHub Apps permiten a las personas crear GitHub Apps pre {% endif %} +{% ifversion ghes < 3.3 %} + ## Estados de despliegue Ahora puedes actualizar el `environment` de un [estado de despliegue](/rest/reference/repos#create-a-deployment-status) y utilizar los estados de `in_progress` y `queued`. Cuando creas estados de despliegue, ahora puedes utilizar el parámetro `auto_inactive` para marcar los despliegues de `production` antiguos como `inactive`. **Tipo de medios personalizados:** `flash-preview` **Anunciado en:**[2018-10-16](https://developer.github.com/changes/2018-10-16-deployments-environments-states-and-auto-inactive-updates/) +{% endif %} + +{% ifversion ghes < 3.3 %} + ## Permisos de creación de repositorios Ahora puedes configurar si los miembros de la organización pueden crear repositorios y decidir qué tipos de éstos pueden crear. Consulta la sección "[Actualizar una organización](/rest/reference/orgs#update-an-organization)" para obtener más detalles. **Tipo de medios personalizados:** `surtur-preview` **Anunciado en:**[2019-12-03](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/) +{% endif %} + ## Adjuntos de contenido Ahora puedes proporcionar más información en GitHub para las URL que enlazan a los dominios registrados si utilizas la API {% data variables.product.prodname_unfurls %}. Consulta la sección "[Utilizar adjuntos de contenido](/apps/using-content-attachments/)" para obtener más detalles. **Tipo de medios personalizados:** `corsair-preview` **Anunciado en:**[2018-12-10](https://developer.github.com/changes/2018-12-10-content-attachments-api/) +{% ifversion ghes < 3.3 %} + ## Habilitar e inhabilitar las páginas Puedes utilizar las terminales nuevas en la [API de páginas](/rest/reference/repos#pages) para habilitar o inhabilitar las Páginas. Para aprender más sobre las páginas, consulta la sección "[Fundamentos de GitHub Pages](/categories/github-pages-basics)". **Tipo de medios personalizados:** `switcheroo-preview` **Anunciado en:**[2019-03-14](https://developer.github.com/changes/2019-03-14-enabling-disabling-pages/) +{% endif %} + {% ifversion ghes < 3.3 %} ## Listar ramas o solicitudes de extracción para una confirmación @@ -169,11 +195,7 @@ Puedes utilizar dos terminales nuevas en la [API de Confirmaciones](/rest/refere {% endif %} -## Habilitar o inhabilitar las alertas vulnerables para un repositorio - -Puedes utilizar dos terminales nueva en la [API de Repos](/rest/reference/repos) para habilitar o inhabilitar las alertas de vulnerabilidades. - -**Tipo de medios personalizados:** `dorian-preview` **Anunciado en:**[2019-04-24](https://developer.github.com/changes/2019-04-24-vulnerability-alerts/) +{% ifversion ghes < 3.3 %} ## Actualizar la rama de una solicitud de extracción @@ -181,12 +203,6 @@ Puedes utilizar una terminal nueva para [actualizar una rama de una solicitud de **Tipo de medios personalizados:** `lydian-preview` **Anunciado en:**[2019-05-29](https://developer.github.com/changes/2019-05-29-update-branch-api/) -{% ifversion fpt %} -## Habilitar o inhabilitar las correcciónes de seguridad automatizadas - -Puedes utilizar un conjunto de terminales nuevo para [habilitar e inhabilitar las correcciones de seguridad automatizados](/rest/reference/repos#enable-automated-security-fixes). - -**Tipo de medios personalizados:** `london-preview` **Anunciado en:**[2019-06-04](https://developer.github.com/changes/2019-06-04-automated-security-fixes/) {% endif %} ## Crear y utilizar plantillas de repositorio @@ -195,7 +211,8 @@ Puedes Puedes utilizar una terminal nueva para [crear un repositorio utilizando **Tipos de medios personalizados:** `baptiste-preview` **Anunciado en:**[2019-07-05](https://developer.github.com/changes/2019-07-16-repository-templates-api/) -{% ifversion fpt or ghes or ghae %} +{% ifversion ghes < 3.3 %} + ## Parámetro de visibilidad nuevo para la API de Repositorios Puedes configurar y recuperar la visibilidad de un repositorio en la [API de Repositorios](/rest/reference/repos). diff --git a/translations/es-ES/content/rest/overview/troubleshooting.md b/translations/es-ES/content/rest/overview/troubleshooting.md index 117e7337dc..1267c15a18 100644 --- a/translations/es-ES/content/rest/overview/troubleshooting.md +++ b/translations/es-ES/content/rest/overview/troubleshooting.md @@ -62,6 +62,10 @@ curl -u my_username:my_password -X POST "https://api.github.com/authorizations" Entonces debes cambiar al [flujo de aplicaciones web](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) para generar tokens de acceso. +## Exceder el tiempo de espera + +Si a {% data variables.product.product_name %} le toma más de 10 segundos procesar una solicitud de la API, {% data variables.product.product_name %} terminará la solicitud y recibirás una respuesta de tiempo de espera excedido. + {% endif %} [oap-guide]: https://developer.github.com/changes/2015-01-19-an-integrators-guide-to-organization-application-policies/ diff --git a/translations/es-ES/content/rest/reference/actions.md b/translations/es-ES/content/rest/reference/actions.md index 0a980c692c..9fd3e74c9f 100644 --- a/translations/es-ES/content/rest/reference/actions.md +++ b/translations/es-ES/content/rest/reference/actions.md @@ -12,7 +12,6 @@ topics: miniTocMaxHeadingLevel: 3 --- -{% data reusables.actions.ae-beta %} La API de {% data variables.product.prodname_actions %} te permite administrar las {% data variables.product.prodname_actions %} utilizando la API de REST. La {% data reusables.actions.actions-authentication %} de las {% data variables.product.prodname_github_apps %} requieren los permisos que se mencionan en cada terminal. Para obtener más información, consulta la sección "[Documentación de {% data variables.product.prodname_actions %}](/actions)". @@ -22,8 +21,6 @@ La API de {% data variables.product.prodname_actions %} te permite administrar l ## Artefactos -{% data reusables.actions.ae-beta %} - La API de Artefactos te permite descargar, borrar y recuperar información acerca de los artefactos de los flujos de trabajo. {% data reusables.actions.about-artifacts %} Para obtener más información, consulta la sección "[Conservar datos de flujo de trabajo mediante artefactos](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)". {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %} @@ -35,8 +32,6 @@ La API de Artefactos te permite descargar, borrar y recuperar información acerc {% ifversion fpt or ghes > 2.22 or ghae %} ## Permisos -{% data reusables.actions.ae-beta %} - La API de permisos te permite configurar permisos para indicar qué organizaciones y repositorios pueden ejecutar las {% data variables.product.prodname_actions %}, y qué acciones se pueden ejecutar. Para obtener más información, consulta la sección "[Límites de uso, facturación y administración](/actions/reference/usage-limits-billing-and-administration#disabling-or-limiting-github-actions-for-your-repository-or-organization)". También puedes configurar permisos para una empresa. Para obtener más información, consulta la API de REST para la "[ Administración de {% data variables.product.prodname_dotcom %} Enterprise](/rest/reference/enterprise-admin#github-actions)". @@ -48,8 +43,6 @@ También puedes configurar permisos para una empresa. Para obtener más informac ## Secretos -{% data reusables.actions.ae-beta %} - La API de Secretos te permite crear, actualizar, borrar y recuperar información acerca de los secretos cifrados. {% data reusables.actions.about-secrets %} Para obtener más información, consulta la sección "[Crear y utilizar secretos cifrados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)". La {% data reusables.actions.actions-authentication %} en las {% data variables.product.prodname_github_apps %} debe contar con el permiso de `secrets` para utilizar esta API. Los usuarios autenticados deben tener acceso de colaborador en el repositorio para crear, actualizar o leer los secretos. @@ -60,7 +53,6 @@ La {% data reusables.actions.actions-authentication %} en las {% data variables. ## Ejecutores autoalojados -{% data reusables.actions.ae-beta %} {% data reusables.actions.ae-self-hosted-runners-notice %} La API de Ejecutores auto-hospedados te permite registrar, ver, y borrar estos ejecutores. {% data reusables.actions.about-self-hosted-runners %} Para obtener más información, consulta "[Alojar tus propios ejecutores](/actions/hosting-your-own-runners)". @@ -75,7 +67,6 @@ Puedes administrar los ejecutores auto-programados para una empresa. Para obtene ## Grupos de ejecutores auto-hospedados -{% data reusables.actions.ae-beta %} {% data reusables.actions.ae-self-hosted-runners-notice %} La API de Grupos de Ejecutores Auto-Hospedados te permite administrar grupos para los ejecutores auto-hospedados. 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)". @@ -90,8 +81,6 @@ Puedes administrar los grupos de ejecutores auto-hospedados para una empresa. Pa ## Flujos de trabajo -{% data reusables.actions.ae-beta %} - La API de flujos de trabajo te permite ver los flujos de trabajo de un repositorio. {% data reusables.actions.about-workflows %} Para obtener más información, consulta la sección "[Automatizar tu flujo de trabajo con GitHub Actions](/actions/automating-your-workflow-with-github-actions)". {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %} @@ -102,8 +91,6 @@ La API de flujos de trabajo te permite ver los flujos de trabajo de un repositor ## Jobs de los flujos de trabajo -{% data reusables.actions.ae-beta %} - La API de Jobs de Flujos de Trabajo te permite ver las bitácoras y los jobs de un flujo de trabajo. {% data reusables.actions.about-workflow-jobs %} Para obtener más información, consulta la sección "[Sintaxis de flujode trabajo para GitHub Actions](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)". {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %} @@ -114,8 +101,6 @@ La API de Jobs de Flujos de Trabajo te permite ver las bitácoras y los jobs de ## Ejecuciones de flujo de trabajo -{% data reusables.actions.ae-beta %} - La API de Ejecuciones de Flujo de Trabajo te permite ver, re-ejecutar, cancelar y ver las bitácoras de las ejecuciones de los flujos de trabajo. {% data reusables.actions.about-workflow-runs %} Para obtener más información, consulta la sección "[Administrar una ejecución de flujo de trabajo](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)". {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %} diff --git a/translations/es-ES/content/rest/reference/activity.md b/translations/es-ES/content/rest/reference/activity.md index 7d9131674d..49295491ce 100644 --- a/translations/es-ES/content/rest/reference/activity.md +++ b/translations/es-ES/content/rest/reference/activity.md @@ -145,6 +145,7 @@ Hay una lista potencial de `reason` para recibir una notificación: | `assign` | Se te asignó al informe de problemas. | | `autor` | Creaste el hilo. | | `comentario` | Comentaste en el hilo. | +| `ci_activity` | A {% data variables.product.prodname_actions %} workflow run that you triggered was completed. | | `invitación` | Aceptaste una invitación para colaborar en el repositorio. | | `manual` | Te suscribiste al hilo (a través de un informe de problemas o solicitud de extracción). | | `mención` | Se te **@mencionó** específicamente en el contenido. | diff --git a/translations/es-ES/content/rest/reference/code-scanning.md b/translations/es-ES/content/rest/reference/code-scanning.md index a1747399dc..e891fa2be8 100644 --- a/translations/es-ES/content/rest/reference/code-scanning.md +++ b/translations/es-ES/content/rest/reference/code-scanning.md @@ -1,6 +1,6 @@ --- title: Escaneo de código -intro: The Code Scanning API enables you to retrieve and update the code scanning alerts and analyses from a repository. +intro: La API de Escaneo de Código te permite recuperar y actualizar las alertas y análisis de escaneo de código desde un repositorio. redirect_from: - /v3/code-scanning product: '{% data reusables.gated-features.code-scanning %}' diff --git a/translations/es-ES/content/rest/reference/enterprise-admin.md b/translations/es-ES/content/rest/reference/enterprise-admin.md index a2f6c2beb4..413a841437 100644 --- a/translations/es-ES/content/rest/reference/enterprise-admin.md +++ b/translations/es-ES/content/rest/reference/enterprise-admin.md @@ -1,5 +1,6 @@ --- title: Administración de GitHub Enterprise +intro: 'You can use these {{ site.data.variables.product.prodname_ghe_cloud }} endpoints to administer your enterprise account. Entre las tareas que puedes realizar con esta API hay muchas que se relacionan con las GitHub Actions.' allowTitleToDifferFromFilename: true redirect_from: - /v3/enterprise-admin @@ -10,11 +11,11 @@ versions: ghae: '*' topics: - API +miniTocMaxHeadingLevel: 3 +shortTitle: Administración empresarial --- -You can use these {{ site.data.variables.product.prodname_ghe_cloud }} endpoints to administer your enterprise account. - -{% if currentVersion == "free-pro-team@latest" %} +{% ifversion fpt %} {% note %} @@ -26,29 +27,29 @@ You can use these {{ site.data.variables.product.prodname_ghe_cloud }} endpoints ### URL de las Terminales -Las terminales de la API de REST{% if enterpriseServerVersions contains currentVersion %}—excepto las terminales de la API de [Consola de Administración](#management-console)—{% endif %} se prefijan con la siguiente URL: +Las terminales de la API de REST{% ifversion ghes %}—excepto las terminales de la API de [Consola de Administración](#management-console)—{% endif %} se prefijan con la siguiente URL: ```shell {% data variables.product.api_url_pre %} ``` -{% if enterpriseServerVersions contains currentVersion %} +{% ifversion ghes %} Las terminales de la API de [Consola de Administración](#management-console) solo llevan un prefijo con un nombre de host: ```shell http(s)://hostname/ ``` {% endif %} -{% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %} +{% ifversion ghae or ghes %} ### Autenticación -Las terminales de la API para tu instalación de {% data variables.product.product_name %} acceptan [los mismos métodos de autenticación](/rest/overview/resources-in-the-rest-api#authentication) que los de la API de GitHub.com. Puedes autenticarte con **[Tokens de OAuth](/apps/building-integrations/setting-up-and-registering-oauth-apps/)** {% if enterpriseServerVersions contains currentVersion %}(los cuales se pueden crear utilizando la [API de autorizciones](/rest/reference/oauth-authorizations#create-a-new-authorization)) {% endif %}o la **[autenticación básica](/rest/overview/resources-in-the-rest-api#basic-authentication)**. {% if enterpriseServerVersions contains currentVersion %} Los tokens de OAuth deben tener el [alcance de OAuth](/developers/apps/scopes-for-oauth-apps#available-scopes) de `site_admin` cuando se utilicen con las terminales específicas de la empresa. {% endif %} +Las terminales de la API para tu instalación de {% data variables.product.product_name %} acceptan [los mismos métodos de autenticación](/rest/overview/resources-in-the-rest-api#authentication) que los de la API de GitHub.com. Puedes autenticarte con **[Tokens de OAuth](/apps/building-integrations/setting-up-and-registering-oauth-apps/)** {% ifversion ghes %}(los cuales se pueden crear utilizando la [API de autorizciones](/rest/reference/oauth-authorizations#create-a-new-authorization)) {% endif %}o con la **[autenticación básica](/rest/overview/resources-in-the-rest-api#basic-authentication)**. {% ifversion ghes %} Los tokens de OAuth deben tener el [alcance de OAuth](/developers/apps/scopes-for-oauth-apps#available-scopes) de `site_admin` cuando se utilicen con las terminales específicas de la empresa. {% endif %} -Solo los administradores de sitio autenticados en {% data variables.product.product_name %} pueden acceder a las terminales de la API de administración empresarial{% if enterpriseServerVersions contains currentVersion %}, con exepción de la API de [Consola de Administración](#management-console), la cual requiere la [contraseña de la Consola de Administración](/enterprise/admin/articles/accessing-the-management-console/){% endif %}. +Solo los administradores de sitio autenticados en {% data variables.product.product_name %} pueden acceder a las terminales de la API de administración empresarial{% ifversion ghes %}, con exepción de la API de [Consola de Administración](#management-console), la cual requiere la [contraseña de la Consola de Administración](/enterprise/admin/articles/accessing-the-management-console/){% endif %}. {% endif %} -{% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %} +{% ifversion ghae or ghes %} ### Información de la versión La versión actual de tu empresa se devuelve en el encabezado de respuesta de cada API: `X-GitHub-Enterprise-Version: {{currentVersion}}.0` También puedes leer la versión actual si llamas a la [terminal de meta](/rest/reference/meta/). @@ -59,7 +60,7 @@ La versión actual de tu empresa se devuelve en el encabezado de respuesta de ca {% endif %} -{% if currentVersion == "free-pro-team@latest" %} +{% ifversion fpt %} ## Registro de auditoría @@ -69,7 +70,7 @@ La versión actual de tu empresa se devuelve en el encabezado de respuesta de ca {% endif %} -{% if currentVersion == "free-pro-team@latest" %} +{% ifversion fpt %} ## Facturación {% for operation in currentRestOperations %} @@ -78,80 +79,15 @@ La versión actual de tu empresa se devuelve en el encabezado de respuesta de ca {% endif %} -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} ## GitHub Actions -{% data reusables.actions.ae-beta %} {% for operation in currentRestOperations %} {% if operation.subcategory == 'actions' %}{% include rest_operation %}{% endif %} {% endfor %} -{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -## SCIM - -### Aprovisionamiento de SCIM para Empresas - -Los Proveedores de Identidad (IdPs) con SCIM habilitado pueden utilizar la API de SCIM para automatizar el aprovisionamiento de la membresía empresarial. La API de {% data variables.product.product_name %} se basa en la versión 2.0 del [estándar de SCIM](http://www.simplecloud.info/). - -El IdP debe utilizar `{% data variables.product.api_url_code %}/scim/v2/enterprises/{enterprise}/` como la terminal de SCIM. - -{% note %} - -**Nota:** La API empresarial de SCIM solo se encuentra disponible para las empresas en [{% data variables.product.prodname_ghe_cloud %}](/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts) que cuenten con el [SSO de SAML](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) habilitado. Para obtener más información acerca de SCIM, consulta "[Acerca de SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)". - -{% endnote %} - -### Autenticar las llamadas a la API de SCIM - -Debes autenticarte como un propietario de una empresa de {% data variables.product.product_name %} para utilizar su API de SCIM. La API espera que se incluya un token [Portador de OAuth 2.0](/developers/apps/authenticating-with-github-apps) en el encabezado `Authorization`. También podrías utilizar un token de acceso personal, pero primero debes [autorizarlo para su uso con tu SSO empresarial de SAML](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on). - -### Mapeo de los datos de SAML y de SCIM - -El IdP de SAML y el cliente de SCIM deben utilizar valores coincidentes de `NameID` y `userName` para cada usuario. Esto le permite al usuario que se autentica mediante SAML el poder enlazarse con su identidad aprovisionada de SCIM. - -Los grupos de SCIM se empatan con las organizaciones de {% data variables.product.product_name %} que tienen exactamente el mismo nombre, y que son propiedad de la cuenta empresarial. - -El IdP de SAML y el cliente de SCIM deben configurarse para empatar exactamente el `displayName` del grupo de SCIM con el nombre correspondiente de la organización de {% data variables.product.product_name %}. Esto le permite a {% data variables.product.product_name %} enlazar el grupo de SCIM con la membrecía organizacional de {% data variables.product.product_name %}. - -### Atributos de Usuario de SCIM compatibles - -| Nombre | Type | Descripción | -| ---------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `userName` | `secuencia` | El nombre de usuario para el usuario. | -| `name.givenName` | `secuencia` | El primer nombre del usuario. | -| `name.lastName` | `secuencia` | El apellido del usuario. | -| `emails` | `arreglo` | Lista de correos electrónicos del usuario. | -| `externalId` | `secuencia` | El proveedor de SAML genera este identificador, el cual utiliza como una ID única para empatarla contra un usuario de GitHub. Puedes encontrar la `externalID` para un usuario ya sea con el proveedor de SAML, o utilizar la terminal de [Listar las identidades aprovisionadas de SCIM para una empresa](#list-scim-provisioned-identities-for-an-enterprise) y filtrar otros atributos conocidos, tales como el nombre de usuario o la dirección de correo electrónico de un usuario de GitHub. | -| `id` | `secuencia` | Identificador que genera la terminal de SCIM de GitHub. | -| `active` | `boolean` | Se utiliza para indicar si la identidad está activa (true) o si debe desaprovisionarse (false). | -| `groups` | `arreglo` | Lista opcional de las ID del grupo de SCIM del cual el usuario es miembro. | - -{% note %} - -**Nota:** Las URL de terminal para la API de SCIM distinguen entre mayúsculas y minúsculas. Por ejemplo, la primera letra en la terminal `Users` debe ponerse en mayúscula: - -```shell -GET /scim/v2/enterprises/{enterprise}/Users/{scim_user_id} -``` - -{% endnote %} - -### Atributos del Grupo de SCIM compatibles - -| Nombre | Type | Descripción | -| ------------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `displayName` | `secuencia` | El nombre del grupo de SCIM, el cual debe empatar exactamente con el nombre de la organización de {% data variables.product.product_name %} correspondiente. Por ejemplo, si la URL de la organización es `https://github.com/octo-org`, el nombre del grupo debe ser `octo-org`. | -| `members` | `arreglo` | Lista de IDs de usuario de SCIM que son miembros del grupo. | - -{% for operation in currentRestOperations %} - {% if operation.subcategory == 'scim' %}{% include rest_operation %}{% endif %} -{% endfor %} - -{% endif %} -{% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %} +{% ifversion ghae or ghes %} ## Estadísticas de los Administradores La API de estadísticas de los administradores proporciona diversas métricas sobre tu instalación. *Solo se encuentra disponible para los administradores de sitio [autenticados.](/rest/overview/resources-in-the-rest-api#authentication)* Los usuarios normales recibirán una respuesta `404` si intentan acceder a ella. @@ -162,7 +98,7 @@ La API de estadísticas de los administradores proporciona diversas métricas so {% endif %} -{% if currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.22" %} +{% ifversion ghae or ghes > 2.22 %} ## Anuncios @@ -174,7 +110,7 @@ La API de anuncios te permite administrar el letrero de anuncios globales en tu {% endif %} -{% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %} +{% ifversion ghae or ghes %} ## Webhooks globales @@ -188,7 +124,7 @@ Los webhooks globales se instalan en tu empresa. Puedes utilizar los webhooks gl {% endif %} -{% if enterpriseServerVersions contains currentVersion %} +{% ifversion ghes %} ## LDAP @@ -202,8 +138,7 @@ Con las terminales de mapeo de LDAP, puedes actualizar el Nombre Distintivo (DN, {% endif %} - -{% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %} +{% ifversion ghae or ghes %} ## Licencia La API de licencias proporciona información sobre tu licencia empresarial. *Solo se encuentra disponible para los administradores de sitio [autenticados.](/rest/overview/resources-in-the-rest-api#authentication)* Los usuarios normales recibirán una respuesta `404` si intentan acceder a ella. @@ -214,7 +149,7 @@ La API de licencias proporciona información sobre tu licencia empresarial. *Sol {% endif %} -{% if enterpriseServerVersions contains currentVersion %} +{% ifversion ghes %} ## Consola de administración @@ -252,7 +187,7 @@ $ curl -L 'https://api_key:your-amazing-password@hostname: {% endif %} -{% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %} +{% ifversion ghae or ghes %} ## Organizaciones La API de Administración Organizacional te permite crear organizaciones en tu empresa. *Solo se encuentra disponible para los administradores de sitio [autenticados.](/rest/overview/resources-in-the-rest-api#authentication)* Los usuarios normales recibirán una respuesta `404` si intentan acceder a ella. @@ -263,8 +198,7 @@ La API de Administración Organizacional te permite crear organizaciones en tu e {% endif %} - -{% if enterpriseServerVersions contains currentVersion %} +{% ifversion ghes %} ## Ganchos de Pre-recepción de la Organización La API de Ganchos de Pre-recepción de la Organización te permite ver y modificar la aplicación de dichos ganchos que están disponibles para una organización. @@ -288,7 +222,7 @@ Los valores posibles para *enforcement* son `enabled`, `disabled` y `testing`. E {% endif %} -{% if enterpriseServerVersions contains currentVersion %} +{% ifversion ghes %} ## Ambientes de pre-recepción @@ -322,7 +256,7 @@ Los valores posibles para `state` son `not_started`, `in_progress`, `success`, ` {% endif %} -{% if enterpriseServerVersions contains currentVersion %} +{% ifversion ghes %} ## Ganchos de pre-recepción La API de Ganchos Pre-recepción te permite crear, listar, actualizar y borrar los ganchos de pre-recepción. *Solo se encuentra disponible para los administradores de sitio [autenticados.](/rest/overview/resources-in-the-rest-api#authentication)* Los usuarios normales recibirán una respuesta `404` si intentan acceder a ella. @@ -348,7 +282,7 @@ Los valores posibles para *enforcement* son `enabled`, `disabled` y `testing`. E {% endif %} -{% if enterpriseServerVersions contains currentVersion %} +{% ifversion ghes %} ## Ganchos de pre-recepción del repositorio @@ -372,10 +306,10 @@ Los valores posibles para *enforcement* son `enabled`, `disabled` y `testing`. E {% endif %} -{% if currentVersion == "github-ae@latest" or enterpriseServerVersions contains currentVersion %} +{% ifversion ghae or ghes %} ## Usuarios -La API de Administración de Usuarios te permite suspender{% if enterpriseServerVersions contains currentVersion %}, dejar de suspender, promover, y degradar{% endif %}{% if currentVersion == "github-ae@latest" %} y dejar de suspender{% endif %} a los usuarios en tu empresa. *Solo se encuentra disponible para los administradores de sitio [autenticados.](/rest/overview/resources-in-the-rest-api#authentication)* Los usuarios normales recibirán una respuesta `403` si intentan acceder a ella. +La API de Administración de Usuarios te permite suspender{% ifversion ghes %}, dejar de suspender, promover, y degradar{% endif %}{% ifversion ghae %} y dejar de suspender{% endif %} a los usuarios en tu empresa. *Solo se encuentra disponible para los administradores de sitio [autenticados.](/rest/overview/resources-in-the-rest-api#authentication)* Los usuarios normales recibirán una respuesta `403` si intentan acceder a ella. {% for operation in currentRestOperations %} {% if operation.subcategory == 'users' %}{% include rest_operation %}{% endif %} diff --git a/translations/es-ES/content/rest/reference/packages.md b/translations/es-ES/content/rest/reference/packages.md index 1a6e6b1a1b..1c527f40c0 100644 --- a/translations/es-ES/content/rest/reference/packages.md +++ b/translations/es-ES/content/rest/reference/packages.md @@ -1,6 +1,6 @@ --- title: Paquetes -intro: 'With the {% data variables.product.prodname_registry %} API, you can manage packages for your {% data variables.product.prodname_dotcom %} repositories and organizations.' +intro: 'Con la API del {% data variables.product.prodname_registry %}, puedes administrar paquetes para tus repositorios y organizaciones de {% data variables.product.prodname_dotcom %}.' product: '{% data reusables.gated-features.packages %}' versions: fpt: '*' diff --git a/translations/es-ES/content/rest/reference/repos.md b/translations/es-ES/content/rest/reference/repos.md index aa8772a148..2363709e7b 100644 --- a/translations/es-ES/content/rest/reference/repos.md +++ b/translations/es-ES/content/rest/reference/repos.md @@ -175,7 +175,7 @@ Puedes comunicar que un ambiente transitorio ya no existe si configuras el `stat {% ifversion fpt or ghes > 3.1 or ghae-next %} ## Ambientes -La API de Ambientes te permite crear, configurar y borrar ambientes. Para obtener información sobre los ambientes, consulta la sección "[Ambientes](/actions/reference/environments)". Para administrar los secretos de ambiente, consulta la sección "[Secretos](/rest/reference/actions#secrets)". +La API de Ambientes te permite crear, configurar y borrar ambientes. Para obtener más información sobre los ambientes, consulta la sección "[Utilizar ambientes para despliegue](/actions/deployment/using-environments-for-deployment)". Para administrar los secretos de ambiente, consulta la sección "[Secretos](/rest/reference/actions#secrets)". {% for operation in currentRestOperations %} {% if operation.subcategory == 'environments' %}{% include rest_operation %}{% endif %} diff --git a/translations/es-ES/content/rest/reference/scim.md b/translations/es-ES/content/rest/reference/scim.md index 982fcc801c..881bdd9ad4 100644 --- a/translations/es-ES/content/rest/reference/scim.md +++ b/translations/es-ES/content/rest/reference/scim.md @@ -16,7 +16,9 @@ Los proveedores de identidad (IdP) habilitados para SCIM utilizan la API de SCIM {% note %} -**Nota:** La API de SCIM está disponible solo para las organizaciones en [{% data variables.product.prodname_ghe_cloud %}](/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts) que tienen habilitado el [SSO de SAML](/rest/overview/other-authentication-methods#authenticating-for-saml-sso). {% data reusables.scim.enterprise-account-scim %} Para obtener más información sobre SCIM, consulta la sección "[Acerca de SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)". +**Notas:** + - La API de SCIM se encuentra disponible únicamente para las organizaciones de [{% data variables.product.prodname_ghe_cloud %}](/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts) que cuentan con el [SSO de SAML](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) habilitado. {% data reusables.scim.enterprise-account-scim %} Para obtener más información sobre SCIM, consulta la sección "[Acerca de SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)". + - La API de SCIM no puede utilizarse con {% data variables.product.prodname_emus %}. {% endnote %} diff --git a/translations/es-ES/content/rest/reference/search.md b/translations/es-ES/content/rest/reference/search.md index c262aa069f..9244b97395 100644 --- a/translations/es-ES/content/rest/reference/search.md +++ b/translations/es-ES/content/rest/reference/search.md @@ -50,7 +50,7 @@ GitHub Octocat in:readme user:defunkt const queryString = 'q=' + encodeURIComponent('GitHub Octocat in:readme user:defunkt'); ``` -Consulta la sección "[Buscar en GitHub](/articles/searching-on-github/)" para encontrar una lista completa de calificadores disponibles, su formato, y ejemplos de cómo utilizarlos. Para obtener más información acerca de cómo utilizar los operadores para que coincidan con cantidades y fechas específicas, o para que excluyan resultados, consulta "[Entender la sintaxis de búsqueda](/articles/understanding-the-search-syntax/)". +Consulta la sección "[Buscar en GitHub](/articles/searching-on-github/)" para encontrar una lista completa de calificadores disponibles, su formato, y ejemplos de cómo utilizarlos. Para obtener más información acerca de cómo utilizar los operadores para que coincidan con cantidades y fechas específicas o para que excluyan resultados, consulta la sección "[Entender la sintaxis de búsqueda](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax/)". ### Limitaciones sobre la longitud de la consulta diff --git a/translations/es-ES/content/rest/reference/teams.md b/translations/es-ES/content/rest/reference/teams.md index c1ec4f2691..e4ae4d1f24 100644 --- a/translations/es-ES/content/rest/reference/teams.md +++ b/translations/es-ES/content/rest/reference/teams.md @@ -58,6 +58,12 @@ La API de sincronización de equipos te permite administrar las conexiones entre Puedes administrar a los miembros del equipo de GitHub a través de tu IdP con la sincronización de equipos. Ésta se debe habilitar para usar la API de Sincronización de Equipos. Para obtener más información, consulta la sección "Sincronizar equipos entre tu proveedor de identidad y GitHub". +{% note %} + +**Nota:** La API de sincronización de equipos no puede utilizarse con {% data variables.product.prodname_emus %}. + +{% endnote %} + {% for operation in currentRestOperations %} {% if operation.subcategory == 'team-sync' %}{% include rest_operation %}{% endif %} {% endfor %} diff --git a/translations/es-ES/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md b/translations/es-ES/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md new file mode 100644 index 0000000000..6dd4a4abc1 --- /dev/null +++ b/translations/es-ES/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md @@ -0,0 +1,90 @@ +--- +title: Acerca de la búsqueda en GitHub +intro: 'Nuestra búsqueda integrada cubre los diversos repositorios, usuarios y líneas de código en {% data variables.product.product_name %}.' +redirect_from: + - /articles/using-the-command-bar/ + - /articles/github-search-basics/ + - /articles/search-basics/ + - /articles/searching-github/ + - /articles/advanced-search/ + - /articles/about-searching-on-github + - /github/searching-for-information-on-github/about-searching-on-github + - /github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +{% data reusables.search.you-can-search-globally %} + +- Para hacer una búsqueda global en todo {% data variables.product.product_name %}, escribe lo que estás buscando en el campo de búsqueda en la parte superior de cualquier página y elige "Todo {% data variables.product.prodname_dotcom %}" en el menú de búsqueda desplegable. +- Para buscar dentro de un repositorio o una organización en particular, navega a la página del repositorio o de la organización, escribe lo que estás buscando en el campo de búsqueda en la parte superior de la página y presiona **Aceptar**. + +{% note %} + +**Notas:** + +{% ifversion fpt or ghes %} +- {% data reusables.search.required_login %}{% endif %} +- Los sitios {% data variables.product.prodname_pages %} no se pueden buscar en {% data variables.product.product_name %}. Sin embargo, puedes buscar el contenido fuente si existe en la rama por defecto de un repositorio, usando la búsqueda de código. Para obtener más información, consulta "[Código de búsqueda](/search-github/searching-on-github/searching-code)". Para obtener más información acerca de {% data variables.product.prodname_pages %}, consulta "[¿Qué son las Páginas de GitHub?](/articles/what-is-github-pages/)" +- Actualmente, nuestra búsqueda no es compatible con las coincidencias exactas. +- Cuando estés buscando dentro de archivos de código, únicamente se devolverán los primeros dos resultados de cada archivo. + +{% endnote %} + +Después de ejecutar una búsqueda en {% data variables.product.product_name %}, puedes clasificar los resultados o refinarlos más haciendo clic en uno de los idiomas de la barra lateral. Para obtener más información, consulta "[Clasificar los resultados de búsqueda](/search-github/getting-started-with-searching-on-github/sorting-search-results)". + +La búsqueda de {% data variables.product.product_name %} usa una agrupación ElasticSearch para indexar los proyectos cada vez que se sube un cambio a {% data variables.product.product_name %}. Las propuestas y las solicitudes de extracción son indexadas cuando son creadas o modificadas. + +## Tipos de búsquedas en {% data variables.product.prodname_dotcom %} + +Puedes buscar la siguiente información a través de todos los repositorios a los que puedes acceder en {% data variables.product.product_location %}. + +- [Repositorios](/search-github/searching-on-github/searching-for-repositories) +- [Temas](/search-github/searching-on-github/searching-topics) +- [propuestas y solicitudes de cambios](/search-github/searching-on-github/searching-issues-and-pull-requests){% ifversion fpt %} +- [Debates](/search-github/searching-on-github/searching-discussions){% endif %} +- [Código](/search-github/searching-on-github/searching-code) +- [Confirmaciones](/search-github/searching-on-github/searching-commits) +- [Usuarios](/search-github/searching-on-github/searching-users) +- [Paquetes](/search-github/searching-on-github/searching-for-packages) +- [Wikis](/search-github/searching-on-github/searching-wikis) + +## Buscar usando una interfaz visual + +Alternativamente, puedes buscar {% data variables.product.product_name %} usando {% data variables.search.search_page_url %} o {% data variables.search.advanced_url %}. + +{% data variables.search.advanced_url %} ofrece una interfaz visual para construir consultas de búsqueda. Puedes filtrar tus búsquedas por diferentes factores, como la cantidad de estrellas o la cantidad de bifurcaciones que tiene un repositorio. A medida que completas los campos de búsqueda de avanzada, tu consulta se construirá automáticamente en la barra de búsqueda superior. + +![Búsqueda avanzada](/assets/images/help/search/advanced_search_demo.gif) + +{% ifversion fpt or ghes or ghae-next %} + +## Buscar repositorios en {% data variables.product.prodname_dotcom_the_website %} desde tu ambiente de empresa privada + +If you use {% ifversion fpt %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae-next %} or {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} and you're a member of a {% data variables.product.prodname_dotcom_the_website %} organization using {% data variables.product.prodname_ghe_cloud %}, an enterprise owner for your {% data variables.product.prodname_enterprise %} environment can enable {% data variables.product.prodname_github_connect %} so that you can search across both environments at the same time{% ifversion ghes or ghae %} from {% data variables.product.product_name %}{% endif %}. Para obtener más información, consulta lo siguiente. + +{% ifversion fpt or ghes %} +- "[Habilitar la {% data variables.product.prodname_unified_search %} entre tu cuenta empresarial y {% data variables.product.prodname_dotcom_the_website %}](/{% ifversion ghes %}{{ currentVersion }}{% else %}github-enterprise@latest{% endif %}/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" en la documentación de {% data variables.product.prodname_ghe_server %}{% endif %}{% ifversion ghae-next %} +- "[Habilitar la {% data variables.product.prodname_unified_search %} entre tu cuenta empresarial y {% data variables.product.prodname_dotcom_the_website %}](/github-ae@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" en la documentación de {% data variables.product.prodname_ghe_managed %} +{% endif %} + +{% ifversion ghes or ghae-next %} + +Para limitar tu búsqueda por entorno, puedes usar una opción de filtro en {% data variables.search.advanced_url %} o puedes usar el prefijo de búsqueda `environment:`. Para solo buscar contenido en {% data variables.product.product_name %}, usa la sintaxis de búsqueda `environment:local`. Para solo buscar contenido en {% data variables.product.prodname_dotcom_the_website %}, usa la sintaxis de búsqueda `environment:github`. + +Tu propietario de empresa en {% data variables.product.product_name %} puede habilitar la {% data variables.product.prodname_unified_search %} para todos los repositorios públicos y privados o únicamente los privados en la organización conectada de {% data variables.product.prodname_ghe_cloud %}. + +Cuando buscas en {% data variables.product.product_name %}, solo puedes buscar en los repositorios privados de la organización conectada de {% data variables.product.prodname_dotcom_the_website %} a los cuales tengas acceso. Los propietarios de empresa de {% data variables.product.product_name %} y los propietarios de organizaciones en {% data variables.product.prodname_dotcom_the_website %} no pueden buscar en los repositorios privados que pertenezcan a tu cuenta de {% data variables.product.prodname_dotcom_the_website %}. Para buscar los repositorios privados aplicables, debes habilitar la búsqueda en repositorios privados para tus cuentas personales de {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Habilitar la búsqueda de repositorios en {% data variables.product.prodname_dotcom_the_website %} desde tu ambiente empresarial privado](/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment)". + +{% endif %} + +{% endif %} + +## Leer más + +- "[Entender la sintaxis de búsqueda](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)" +- "[Búsqueda en GitHub](/articles/searching-on-github)" diff --git a/translations/es-ES/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md b/translations/es-ES/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md new file mode 100644 index 0000000000..9303c4afd1 --- /dev/null +++ b/translations/es-ES/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md @@ -0,0 +1,54 @@ +--- +title: Habilitar la búsqueda en repositorios de GitHub.com desde tu ambiente empresarial privado +shortTitle: Buscar en GitHub.com desde una empresa +intro: 'Puedes conectar tus cuentas personales de {% data variables.product.prodname_dotcom_the_website %} y tu ambiente privado de {% data variables.product.prodname_enterprise %} para buscar contenido en repositorios específicos de {% data variables.product.prodname_dotcom_the_website %}{% ifversion fpt %} desde tu ambiente privado{% else %} desde {% data variables.product.product_name %}{% endif %}.' +redirect_from: + - /articles/enabling-private-githubcom-repository-search-in-your-github-enterprise-account/ + - /articles/enabling-private-github-com-repository-search-in-your-github-enterprise-server-account/ + - /articles/enabling-private-githubcom-repository-search-in-your-github-enterprise-server-account/ + - /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 +versions: + fpt: '*' + ghes: '*' + ghae: next +topics: + - GitHub search +--- + +## Acerca de cómo buscar repositorios de {% data variables.product.prodname_dotcom_the_website %} desde {% ifversion fpt %}tu ambiente empresarial privado{% else %}{% data variables.product.product_name %}{% endif %} + +Puedes buscar repositorios privados designados en {% data variables.product.prodname_ghe_cloud %} desde {% ifversion fpt %}tu ambiente privado de {% data variables.product.prodname_enterprise %}{% else %}{% data variables.product.product_location %}{% ifversion ghae %} en {% data variables.product.prodname_ghe_managed %}{% endif %}{% endif %}. {% ifversion fpt %}Por ejemplo, si utilizas {% data variables.product.prodname_ghe_server %}, puedes buscar repositorios privados desde tu empresa en {% data variables.product.prodname_ghe_cloud %} en la interfaz web de {% data variables.product.prodname_ghe_server %}.{% endif %} + +## Prerrequisitos + +- Un propietario de empresa de {% ifversion fpt %}tu ambiente privado de {% data variables.product.prodname_enterprise %}{% else %}{% data variables.product.product_name %}{% endif %} debe habilitar {% data variables.product.prodname_github_connect %} y {% data variables.product.prodname_unified_search %}. Para obtener más información, consulta lo siguiente.{% ifversion fpt or ghes %} + - "[Habilitar la {% data variables.product.prodname_unified_search %} entre tu cuenta empresarial y {% data variables.product.prodname_dotcom_the_website %}](/{% ifversion ghes %}{{ currentVersion }}{% else %}github-enterprise@latest{% endif %}/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" en la documentación de {% data variables.product.prodname_ghe_server %}{% endif %}{% ifversion ghae-next %} + - "[Habilitar {% data variables.product.prodname_unified_search %} entre tu cuenta empresarial y {% data variables.product.prodname_dotcom_the_website %}](/github-ae@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" en la documentación de {% data variables.product.prodname_ghe_managed %} documentation +{% endif %} + +- Ya debes tener acceso a los repositorios privados y conectar tu cuenta {% ifversion fpt %}en tu ambiente privado de {% data variables.product.prodname_enterprise %}{% else %} en {% data variables.product.product_name %}{% endif %} con tu cuenta en {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información sobre los repositorios en los que puedes buscar, consulta la sección "[Acerca de cómo buscar en GitHub](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github#searching-repositories-on-githubcom-from-your-private-enterprise-environment)". + +## Habilitar la búsqueda de repositorios de GitHub.com desde {% ifversion fpt %}tu ambiente privado de {% data variables.product.prodname_enterprise %}{% else %}{% data variables.product.product_name %}{% endif %} + +{% ifversion fpt %} + +Para obtener más información, consulta lo siguiente. + +| Tue ambiente empresarial | Más información | +|:--------------------------------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| {% data variables.product.prodname_ghe_server %} | "[Habilitar la búsqueda de repositorios de {% data variables.product.prodname_dotcom_the_website %} desde tu ambiente empresarial privado](/enterprise-server@latest/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-enterprise-server)" |{% ifversion ghae-next %} +| +| {% data variables.product.prodname_ghe_managed %} | "[Habilitar la búsqueda de repositorios de {% data variables.product.prodname_dotcom_the_website %} desde tu ambiente empresarial privado](/github-ae@latest//search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-ae)" +{% endif %} + +{% elsif ghes or ghae %} + +1. Inicia sesión en {% data variables.product.product_name %} y en {% data variables.product.prodname_dotcom_the_website %}. +1. En {% data variables.product.product_name %}, en la esquina superior derecha de cualquier página, haz clic en tu foto de perfil y luego haz clic en **Ajustes**. ![Icono Settings (Parámetros) en la barra de usuario](/assets/images/help/settings/userbar-account-settings.png) +{% data reusables.github-connect.github-connect-tab-user-settings %} +{% data reusables.github-connect.connect-dotcom-and-enterprise %} +{% data reusables.github-connect.connect-dotcom-and-enterprise %} + +{% endif %} diff --git a/translations/es-ES/content/search-github/getting-started-with-searching-on-github/index.md b/translations/es-ES/content/search-github/getting-started-with-searching-on-github/index.md new file mode 100644 index 0000000000..2dfb94abdc --- /dev/null +++ b/translations/es-ES/content/search-github/getting-started-with-searching-on-github/index.md @@ -0,0 +1,21 @@ +--- +title: Comenzar con la búsqueda en GitHub +intro: 'Puedes usar una sintaxis amplia para buscar en {% data variables.product.product_name %}. Puedes ajustar el alcance de tus consultas de búsqueda, compilación y solución de problemas y clasificar los resultados con calificadores.' +redirect_from: + - /articles/getting-started-with-searching-on-github + - /github/searching-for-information-on-github/getting-started-with-searching-on-github +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +children: + - /about-searching-on-github + - /understanding-the-search-syntax + - /troubleshooting-search-queries + - /sorting-search-results + - /enabling-githubcom-repository-search-from-your-private-enterprise-environment +shortTitle: Iniciar con la búsqueda en GitHub +--- + diff --git a/translations/es-ES/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md b/translations/es-ES/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md new file mode 100644 index 0000000000..ada343c852 --- /dev/null +++ b/translations/es-ES/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md @@ -0,0 +1,75 @@ +--- +title: Clasificar resultados de búsqueda +intro: 'Puedes clasificar los resultados de búsqueda [{% data variables.product.product_name %} search](/articles/searching-on-github) utilizando el menú de Clasificación, o al agregar un calificador `sort` a tu consulta.' +redirect_from: + - /articles/sorting-search-results + - /github/searching-for-information-on-github/sorting-search-results + - /github/searching-for-information-on-github/getting-started-with-searching-on-github/sorting-search-results +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +Utiliza el menú Sort (Clasificar) para clasificar resultados por relevancia, cantidad de estrellas, cantidad de bifurcaciones y qué tan recientemente se actualizaron los elementos. + + ![Menú con opciones para clasificar resultados de búsqueda](/assets/images/help/search/repo-search-sort.png) + +Para clasificar por interacciones, reacciones, fecha de autor, fecha de persona que confirma el cambio, o qué tan recientemente se actualizaron los elementos, puedes agregar un calificador `sort` a tu consulta de búsqueda. + +## Clasificar por interacciones + +El calificador `sort:interactions` clasifica según el mayor número combinado de reacciones y comentarios. + +| Qualifier | Ejemplo | +| ----------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sort:interactions` or `sort:interactions-desc` | [**org:github sort:interactions**](https://github.com/search?q=org%3Agithub+sort%3Ainteractions&type=Issues) encuentra propuestas en repositorios propiedad de {% data variables.product.product_name %}, clasificadas por el mayor número combinado de reacciones y comentarios. | +| `sort:interactions-asc` | [**org:github sort:interactions-asc**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Ainteractions-asc&type=Issues) encuentra propuestas en repositorios propiedad de {% data variables.product.product_name %}, clasificadas por el menor número combinado de reacciones y comentarios. | + +## Clasificar por reacciones + +El calificador `sort:reactions` clasifica por la cantidad o el tipo de reacciones. + +| Qualifier | Ejemplo | +| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sort:reactions` or `sort:reactions-desc` | [**org:github sort:reactions**](https://github.com/search?q=org%3Agithub+sort%3Areactions&type=Issues) encuentra propuestas en repositorios propiedad de {% data variables.product.product_name %}, clasificadas por la mayor cantidad de reacciones. | +| `sort:reactions-asc` | [**org:github sort:reactions-asc**](https://github.com/search?q=org%3Agithub+sort%3Areactions-asc&type=Issues) encuentra propuestas en repositorios propiedad de {% data variables.product.product_name %}, clasificadas por la cantidad ascendente de reacciones (desde la menor a la mayor). | +| sort:reactions-reaction | [**org:github sort:reactions-+1**](https://github.com/search?q=org%3Agithub+sort%3Areactions-%2B1&type=Issues) encuentra propuestas en repositorios propiedad de {% data variables.product.product_name %}, clasificadas por la mayor cantidad de reacciones positivas (:+1:). | +| | [**org:github sort:reactions--1**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Areactions--1&type=Issues) encuentra propuestas en repositorios propiedad de {% data variables.product.product_name %}, clasificadas por la mayor cantidad de reacciones negativas (:-1:). | +| | [**org:github sort:reactions-smile**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Areactions-smile&type=Issues) encuentra propuestas en repositorios propiedad de {% data variables.product.product_name %}, clasificadas por las mayores reacciones de risa (:smile:). | +| | [**org:github sort:reactions-tada**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Areactions-tada&type=Issues) encuentra propuestas en repositorios propiedad de {% data variables.product.product_name %}, clasificadas por la mayor cantidad de reacciones buenas (:tada:). | +| | [**org:github sort:reactions-heart**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Areactions-heart&type=Issues) encuentra propuestas en repositorios propiedad de {% data variables.product.product_name %}, clasificadas por la mayor cantidad de reacciones corazón(:heart:). | + +## Clasificar por fecha de autor + +El calificador `sort:author-date` clasifica por fecha de autor descendente o ascendente. + +| Qualifier | Ejemplo | +| --------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sort:author-date` or `sort:author-date-desc` | [**feature org:github sort:author-date**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Aauthor-date&type=Commits) encuentra confirmaciones que contienen la palabra "feature" en repositorios propiedad de {% data variables.product.product_name %}, clasificadas por fecha de autor descendente. | +| `sort:author-date-asc` | [**feature org:github sort:author-date-asc**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Aauthor-date-asc&type=Commits) encuentra confirmaciones que contienen la palabra "feature" en repositorios propiedad de {% data variables.product.product_name %}, clasificadas por fecha de autor ascendente. | + +## Clasificar por fecha de persona que confirma el cambio + +El calificador `sort:committer-date` clasifica por fecha de persona que confirma el cambio descendente o ascendente. + +| Qualifier | Ejemplo | +| --------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sort:committer-date` or `sort:committer-date-desc` | [**feature org:github sort:committer-date**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Acommitter-date&type=Commits) encuentra confirmaciones que contienen la palabra "feature" en repositorios propiedad de {% data variables.product.product_name %}, clasificadas por fecha de la persona que confirma el cambio descendente. | +| `sort:committer-date-asc` | [**feature org:github sort:committer-date-asc**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Acommitter-date-asc&type=Commits) encuentra confirmaciones que contienen la palabra "feature" en repositorios propiedad de {% data variables.product.product_name %}, clasificadas por fecha ascendente de la persona que confirma el cambio. | + +## Clasificar por fecha de actualización + +El calificador `sort:updated` clasifica según qué tan recientemente se actualizaron los elementos. + +| Qualifier | Ejemplo | +| ------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sort:updated` or `sort:updated-desc` | [**feature sort:updated**](https://github.com/search?utf8=%E2%9C%93&q=feature+sort%3Aupdated&type=Repositories) encuentra repositorios que contienen la palabra "feature," clasificados por la fecha de actualización más reciente. | +| `sort:updated-asc` | [**feature sort:updated-asc**](https://github.com/search?utf8=%E2%9C%93&q=feature+sort%3Aupdated-asc&type=Repositories) encuentra repositorios que contienen la palabra "feature," clasificados por la fecha de actualización menos reciente. | + +## Leer más + +- "[Acerca de buscar en {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)" +- "[Filtrar y buscar propuestas y solicitudes de cambios](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)" diff --git a/translations/es-ES/content/search-github/getting-started-with-searching-on-github/troubleshooting-search-queries.md b/translations/es-ES/content/search-github/getting-started-with-searching-on-github/troubleshooting-search-queries.md new file mode 100644 index 0000000000..9e00953a05 --- /dev/null +++ b/translations/es-ES/content/search-github/getting-started-with-searching-on-github/troubleshooting-search-queries.md @@ -0,0 +1,34 @@ +--- +title: Solucionar problemas de consultas de búsqueda +intro: 'Si encuentras resultados inesperados cuando buscas en {% data variables.product.product_name %}, puedes solucionar los problemas revisando los problemas comunes y las limitaciones.' +redirect_from: + - /articles/troubleshooting-search-queries + - /github/searching-for-information-on-github/troubleshooting-search-queries + - /github/searching-for-information-on-github/getting-started-with-searching-on-github/troubleshooting-search-queries +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +shortTitle: Solucionar problemas de las consultas de búsqueda +--- + +## Interrupciones potenciales + +Algunas consultas son costosas desde el punto de vista informático para que las ejecute nuestra infraestructura de búsqueda. Para que la búsqueda siga siendo rápida para todos, limitamos la cantidad de tiempo que se puede ejecutar una consulta individual. En pocas situaciones, cuando una consulta supera el límite de tiempo, la búsqueda devuelve todas las coincidencias que se encontraron antes de que se acabara el tiempo y te informa que se acabó el tiempo. + +Llegar a una interrupción no necesariamente significa que los resultados de búsqueda estén incompletos. Solo significa que la consulta se interrumpió antes de que se buscara en todos los datos posibles. + +## Limitaciones sobre la longitud de la consulta + +Existen algunos límites en la longitud de las consultas cuando se busca en {% data variables.product.product_name %}: + +* No se admiten consultas que superen los 256 caracteres +* No puede elaborar una consulta que utilice más de cinco operadores `AND`, `OR` o `NOT` + +Los tipos de búsqueda específicos, como la búsqueda de código, pueden tener más limitaciones. Revisa la documentación de estos tipos de búsqueda para obtener más información. + +## Leer más + +- "[Acerca de buscar en GitHub](/search-github/getting-started-with-searching-on-github/about-searching-on-github)" 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 new file mode 100644 index 0000000000..b8b8333fa5 --- /dev/null +++ b/translations/es-ES/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md @@ -0,0 +1,100 @@ +--- +title: Entender la sintaxis de búsqueda +intro: 'Cuando buscas {% data variables.product.product_name %}, puedes construir consultas que coincidan con números y palabras específicas.' +redirect_from: + - /articles/search-syntax/ + - /articles/understanding-the-search-syntax + - /github/searching-for-information-on-github/understanding-the-search-syntax + - /github/searching-for-information-on-github/getting-started-with-searching-on-github/understanding-the-search-syntax +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +shortTitle: Entender la sintaxis de búsqueda +--- + +## Consulta para valores mayores o menores que otro valor + +Puedes utilizar `>`, `>=`, `<` y `<=` para buscar valores que sean mayores, mayores o iguales, menores y menores o iguales a otro valor. + +| Consulta | Ejemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| >n | **[cats stars:>1000](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%3E1000&type=Repositories)** coincidirá con los repositorios que tengan la palabra "cats" y tengan más de 1000 estrellas. | +| >=n | **[cats topics:>=5](https://github.com/search?utf8=%E2%9C%93&q=cats+topics%3A%3E%3D5&type=Repositories)** coincidirá con los repositorios que tengan la palabra "cats" y tengan 5 o más temas. | +| <n | **[cats size:<10000](https://github.com/search?utf8=%E2%9C%93&q=cats+size%3A%3C10000&type=Code)** coincidirá con el código que tenga la palabra "cats" en los archivos que sean menores a 10 KB. | +| <=n | **[cats stars:<=50](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%3C%3D50&type=Repositories)** coincidirá con los repositorios que tengan la palabra "cats" y 50 estrellas o menos. | + +También puedes utilizar [consultas por rango](#query-for-values-between-a-range) para buscar valores que sean mayores o iguales, o menores o iguales a otro valor. + +| Consulta | Ejemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| n..* | **[gatos estrellas:10..*](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A10..*&type=Repositories)** equivale a `estrellas:>=10` y busca repositorios con la palabra "gatos" que tengan 10 o más estrellas. | +| *..n | **[gatos estrellas:*..10](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%22*..10%22&type=Repositories)** equivale a `estrellas:<=10` y busca repositorios con la palabra "gatos" que tengan 10 o menos estrellas. | + +## Consulta para valores entre un rango + +Puedes utilizar la sintaxis de rango n..n para buscar valores dentro de un rango, en los que el primer número _n_ sea el valor más bajo y el segundo sea el valor más alto. + +| Consulta | Ejemplo | +| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| n..n | **[gatos estrellas:10..50](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A10..50&type=Repositories)** busca repositorios con la palabra "gatos" que tengan entre 10 y 50 estrellas. | + +## Consulta por fechas + +Puedes buscar fechas que sean anteriores o posteriores a otra fecha o que entren en un rango de fechas, utilizando `>`, `>=`, `<`, `<=` y [consultas por rango](#query-for-values-between-a-range). {% data reusables.time_date.date_format %} + +| Consulta | Ejemplo | +| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| >AAAA-MM-DD | **[cats created:>2016-04-29](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3E2016-04-29&type=Issues)** coincidirá con informes de problemas que tengan la palabra "cats" y se hayan creado después del 29 de abril de 2016. | +| >=AAAA-MM-DD | **[cats created:>=2017-04-01](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3E%3D2017-04-01&type=Issues)** coincidirá con informes de problemas que contengan la palabra "cats" y se hayan creado en o después del 1 de abril de 2017. | +| <AAAA-MM-DD | **[cats pushed:<2012-07-05](https://github.com/search?q=cats+pushed%3A%3C2012-07-05&type=Code&utf8=%E2%9C%93)** coincidirá con el código que contenga la palabra "cats" en los repositorios en los que se subió información antes del 5 de julio de 2012. | +| <=AAAA-MM-DD | **[cats created:<=2012-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3C%3D2012-07-04&type=Issues)** coincidirá con los informes de problemas que contengan la palabra "cats" y se hayan creado en o antes del 4 de julio de 2012. | +| AAAA-MM-DD..AAAA-MM-DD | **[gatos subidos:2016-04-30..2016-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+pushed%3A2016-04-30..2016-07-04&type=Repositories)** busca repositorios con la palabra "gatos" que se hayan subido entre fines de abril y julio de 2016. | +| AAAA-MM-DD..* | **[gatos creados:2012-04-30..*](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2012-04-30..*&type=Issues)** busca propuestas que se hayan creado después del 30 de abril de 2012 y contengan la palabra "gatos". | +| *..AAAA-MM-DD | **[gatos creados:*..2012-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A*..2012-07-04&type=Issues)** busca propuestas creadas antes del 4 de julio de 2012 que contengan la palabra "gatos". | + +{% data reusables.time_date.time_format %} + +| Consulta | Ejemplo | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| AAAA-MM-DDTHH:MM:SS+00:00 | **[gatos creados:2017-01-01T01:00:00+07:00..2017-03-01T15:30:15+07:00](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2017-01-01T01%3A00%3A00%2B07%3A00..2017-03-01T15%3A30%3A15%2B07%3A00&type=Issues)** busca propuestas creadas entre el 1 de enero de 2017 a la 1 a. m. con una compensación de UTC de `07:00` y el 1 de marzo de 2017 a las 3 p. Con un desplazamiento UTC de `07:00` y 1 de marzo de 2017 a las 3 p.m. m. con una compensación de UTC de `07:00`. | +| AAAA-MM-DDTHH:MM:SSZ | **[gatos creados:2016-03-21T14:11:00Z..2016-04-07T20:45:00Z](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2016-03-21T14%3A11%3A00Z..2016-04-07T20%3A45%3A00Z&type=Issues)** busca propuestas creadas entre el 21 de marzo de 2016 a las 2:11 p. m. y el 7 de abril de 2106 a las 8:45 p. m. | + +## Excluye determinados resultados + +Puedes excluir resultados que contengan una determinada palabra utilizando la sintaxis `NOT` (NO). El operador `NOT` solo se puede utilizar para las palabras clave en cadena. No funciona para números o fechas. + +| Consulta | Ejemplo | +| -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `NOT` | **[hola NOT mundo](https://github.com/search?q=hello+NOT+world&type=Repositories)** busca repositorios que tengan la palabra "hola", pero no la palabra "mundo" | + +Otra manera de reducir los resultados de búsqueda es excluir determinados subconjuntos. Puedes usar como prefijo de cualquier calificador de búsqueda un `-` para excluir todos los resultados que coincidan con ese calificador. + +| Consulta | Ejemplo | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| -CALIFICADOR | **[cats stars:>10 -language:javascript](https://github.com/search?q=cats+stars%3A>10+-language%3Ajavascript&type=Repositories)** coincidirá con los repositorios que tengan la palabra "cats" y tengan más de 10 estrellas, pero no se hayan escrito en JavaScript. | +| | **[menciones:defunkt -org:github](https://github.com/search?utf8=%E2%9C%93&q=mentions%3Adefunkt+-org%3Agithub&type=Issues)** busca propuestas que mencionan a @defunkt y no estén en repositorios de la organización de GitHub | + +## Utiliza comillas para las consultas con espacios en blanco + +Si tu consulta de búsqueda contiene espacios en blanco, tendrás que encerrarla entre comillas. Por ejemplo: + +* [gatos NOT "hola mundo"](https://github.com/search?utf8=✓&q=cats+NOT+"hello+world"&type=Repositories) busca repositorios con la palabra "gatos", pero sin las palabras "hola mundo". +* [construir etiqueta:"corrección de error"](https://github.com/search?utf8=%E2%9C%93&q=build+label%3A%22bug+fix%22&type=Issues) busca propuestas con la palabra "construir" que tengan la etiqueta "corrección de error". + +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 %} +## 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. + +| Consulta | Ejemplo | +| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `QUALIFIER:USERNAME` | [`author:nat`](https://github.com/search?q=author%3Anat&type=Commits) coincidirá con las confirmaciones del autor @nat | +| `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/index.md b/translations/es-ES/content/search-github/index.md new file mode 100644 index 0000000000..1d3a11a050 --- /dev/null +++ b/translations/es-ES/content/search-github/index.md @@ -0,0 +1,20 @@ +--- +title: Buscar información en GitHub +intro: Utiliza los diferentes tipos de búsqueda para encontrar la información que quieres. +redirect_from: + - /categories/78/articles/ + - /categories/search/ + - /categories/searching-for-information-on-github + - /github/searching-for-information-on-github +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +children: + - /getting-started-with-searching-on-github + - /searching-on-github +shortTitle: Busca en GitHub +--- + diff --git a/translations/es-ES/content/search-github/searching-on-github/finding-files-on-github.md b/translations/es-ES/content/search-github/searching-on-github/finding-files-on-github.md new file mode 100644 index 0000000000..9c3dc4c052 --- /dev/null +++ b/translations/es-ES/content/search-github/searching-on-github/finding-files-on-github.md @@ -0,0 +1,32 @@ +--- +title: Buscar archivos en GitHub +intro: 'Puedes buscar un archivo en un repositorio utilizando el buscador de archivos. Para buscar un archivo en varios repositorios de {% data variables.product.product_name %}, utiliza el [calificador de búsqueda de código `filename`](/search-github/searching-on-github/searching-code#search-by-filename).' +redirect_from: + - /articles/finding-files-on-github + - /github/searching-for-information-on-github/finding-files-on-github + - /github/searching-for-information-on-github/searching-on-github/finding-files-on-github +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +{% tip %} + +**Tips:** + +- Los resultados del buscador de archivos excluyen algunos directorios como `build`, `log`, `tmp` y `vendor`. Para buscar archivos dentro de estos directorios, usa el [calificador de búsqueda de código `filename`](/search-github/searching-on-github/searching-code#search-by-filename). +- También puedes abrir el buscador de archivos presionando `t` en tu teclado. Para obtener más información, consulta "[Atajos del teclado](/articles/keyboard-shortcuts/#comments)". + +{% endtip %} + +{% data reusables.repositories.navigate-to-repo %} +2. Sobre la lista de archivos, da clic en **Ir al archivo**. ![Botón Buscar archivo](/assets/images/help/search/find-file-button.png) +3. En el campo de búsqueda, escribe el nombre del archivo que deseas buscar. ![Campo de búsqueda Buscar archivo](/assets/images/help/search/find-file-search-field.png) +4. En la lista de resultados, haz clic en el archivo que deseas buscar. + +## Leer más + +- "[Acerca de buscar en GitHub](/search-github/getting-started-with-searching-on-github/about-searching-on-github)" diff --git a/translations/es-ES/content/search-github/searching-on-github/index.md b/translations/es-ES/content/search-github/searching-on-github/index.md new file mode 100644 index 0000000000..197f6a74a3 --- /dev/null +++ b/translations/es-ES/content/search-github/searching-on-github/index.md @@ -0,0 +1,27 @@ +--- +title: Buscar en GitHub +intro: Puedes utilizar calificadores para acotar tu búsqueda y enfocarte en categorías de información específicas. +redirect_from: + - /articles/searching-on-github + - /github/searching-for-information-on-github/searching-on-github +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +children: + - /finding-files-on-github + - /searching-for-repositories + - /searching-topics + - /searching-code + - /searching-commits + - /searching-issues-and-pull-requests + - /searching-discussions + - /searching-github-marketplace + - /searching-users + - /searching-for-packages + - /searching-wikis + - /searching-in-forks +--- + diff --git a/translations/es-ES/content/search-github/searching-on-github/searching-code.md b/translations/es-ES/content/search-github/searching-on-github/searching-code.md new file mode 100644 index 0000000000..1cc38574e9 --- /dev/null +++ b/translations/es-ES/content/search-github/searching-on-github/searching-code.md @@ -0,0 +1,112 @@ +--- +title: Buscar código +intro: 'Puedes buscar código en {% data variables.product.product_name %} y acotar los resultados utilizando estos calificadores de búsqueda de código en cualquier combinación.' +redirect_from: + - /articles/searching-code + - /github/searching-for-information-on-github/searching-files-in-a-repository-for-exact-matches + - /github/searching-for-information-on-github/searching-code-for-exact-matches + - /github/searching-for-information-on-github/searching-code + - /github/searching-for-information-on-github/searching-on-github/searching-code +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +{% data reusables.search.you-can-search-globally %} Para obtener más información, consulta la sección "[Acerca de buscar en GitHub](/search-github/getting-started-with-searching-on-github/about-searching-on-github)". + +Únicamente puedes buscar código utilizando estos calificadores de búsqueda de código. Los calificadores de búsqueda especialmente para repositorios, usuarios o confirmaciones de cambios, no funcionarán cuando busques código. + +{% data reusables.search.syntax_tips %} + +## Consideraciones sobre la búsqueda de código + +Debido a la complejidad de la búsqueda de código, hay algunas restricciones sobre cómo se realizan las búsquedas: + +{% ifversion fpt or ghes %} +- {% data reusables.search.required_login %}{% endif %} +- El código en [bifurcaciones](/articles/about-forks) es únicamente indexado si la bifurcación tiene más estrellas que el repositorio padre. Las bifurcaciones con menos estrellas que el repositorio padre **no** son indexadas para la búsqueda de código. Para incluir bifurcaciones con más estrellas que sus padres en los resultados de las búsquedas, deberás agregar `fork:true` o `fork:only` en tu consulta. Para obtener más información, consulta "[Buscar en bifurcaciones](/search-github/searching-on-github/searching-in-forks)". +- Solo la _rama predeterminada_ se indiza para la búsqueda de código.{% ifversion fpt %} +- Solo los archivos menores de 384 KB son indexados.{% else %}* Solo los archivos menores de 5 MB son indexados. +- Solo los primeros 500 KB de cada archivo son indexados.{% endif %} +- Solo se pueden hacer búsquedas en los repositorios con menos de 500,000 archivos.{% ifversion fpt %} +- Solo se pueden hacer búsquedas en los repositorios que han tenido actividad o que se han devuelto en los resultados de búsqueda dentro del último año.{% endif %} +- Excepto con las búsquedas por [`nombre de archivo`](#search-by-filename), siempre debes incluir por lo menos un término de búsqueda cuando buscas el código fuente. Por ejemplo, no es válido buscar por [`language:javascript`](https://github.com/search?utf8=%E2%9C%93&q=language%3Ajavascript&type=Code&ref=searchresults), mientras que sí los es por [`amazing language:javascript`](https://github.com/search?utf8=%E2%9C%93&q=amazing+language%3Ajavascript&type=Code&ref=searchresults). +- A lo sumo, los resultados de búsqueda pueden mostrar dos fragmentos del mismo archivo, pero puede haber más resultados dentro del archivo. +- No puedes utilizar los siguientes caracteres comodines como parte de la consulta de búsqueda: . , : ; / \ ` ' " = * ! ? # $ & + ^ | ~ < > ( ) { } [ ] @. La búsqueda simplemente ignorará estos símbolos. + +## Buscar según los contenidos del archivo o la ruta de archivo + +Con el calificador `in` puedes restringir tu búsqueda a los contenidos del archivo del código fuente, de la ruta del archivo, o de ambos. Cuando omites este calificador, únicamente se busca el contenido del archivo. + +| Qualifier | Ejemplo | +| --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `in:file` | [**octocat in:file**](https://github.com/search?q=octocat+in%3Afile&type=Code) encuentra el código donde aparece "octocat" en el contenido del archivo. | +| `in:path` | [**octocat in:path**](https://github.com/search?q=octocat+in%3Apath&type=Code) encuentra el código donde aparece "octocat" en la ruta del archivo. | +| | [**octocat in:file,path**](https://github.com/search?q=octocat+in%3Afile%2Cpath&type=Code) encuentra el código donde aparece "octocat" en el contenido del archivo o la ruta del archivo. | + +## Buscar dentro de los repositorios de un usuario u organización + +Para buscar el código en todos los repositorios que son propiedad de una determinada organización o usuario, puedes utilizar el calificador `user` u `org`. Para buscar el código en un repositorio específico, puedes utilizar el calificador `repo`. + +| Qualifier | Ejemplo | +| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**user:defunkt extension:rb**](https://github.com/search?q=user%3Agithub+extension%3Arb&type=Code) encuentra el código de @defunkt que termina en .rb. | +| org:ORGNAME | [**org:github extension:js**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+extension%3Ajs&type=Code) encuentra el código de GitHub que termina en .js. | +| repo:USERNAME/REPOSITORY | [**repo:mozilla/shumway extension:as**](https://github.com/search?q=repo%3Amozilla%2Fshumway+extension%3Aas&type=Code) encuentra el código del proyecto shumway de @mozilla que termina en .as. | + +## Buscar por ubicación del archivo + +Puedes utilizar el calificador `path` (ruta) para buscar el código fuente que aparece en una ubicación específica en un repositorio. Utiliza `path:/` para buscar archivos que estén ubicados a nivel de la raíz de un repositorio. O especifica un nombre de directorio o ruta a un directorio para buscar archivos que estén ubicados dentro de ese directorio o alguno de sus subdirectorios. + +| Qualifier | Ejemplo | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| path:/ | [**octocat filename:readme path:/**](https://github.com/search?utf8=%E2%9C%93&q=octocat+filename%3Areadme+path%3A%2F&type=Code) encuentra los archivos _readme_ con la palabra "octocat" que se encuentran al nivel de raíz de un repositorio. | +| path:DIRECTORY | [**form path:cgi-bin language:perl**](https://github.com/search?q=form+path%3Acgi-bin+language%3Aperl&type=Code) matches Perl files with the word "form" in the cgi-bin directory, or in any of its subdirectories. | +| path:PATH/TO/DIRECTORY | [**console path:app/public language:javascript**](https://github.com/search?q=console+path%3A%22app%2Fpublic%22+language%3Ajavascript&type=Code) matches JavaScript files with the word "console" in the app/public directory, or in any of its subdirectories (even if they reside in app/public/js/form-validators). | + +## Buscar por lenguaje + + +Puedes buscar el código basado en el lenguaje en que está escrito. El calificador `language` puede ser el nombre o el alias del idioma. Para obtener una lista completa de lenguajes compatibles con sus nombres y alias, consulta el [repositorio github/linguist](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml). + +| Qualifier | Ejemplo | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| language:LANGUAGE | [**element language:xml size:100**](https://github.com/search?q=element+language%3Axml+size%3A100&type=Code) encuentra código con la palabra "element" que está marcada como XML y tiene exactamente 100 bytes. | +| | [**display language:scss**](https://github.com/search?q=display+language%3Ascss&type=Code) encuentra código con la palabra "display," que está marcada como SCSS. | +| | [**org:mozilla language:markdown**](https://github.com/search?utf8=%E2%9C%93&q=org%3Amozilla+language%3Amarkdown&type=Code) encuentra código de todos los repositorios de @mozilla que están marcados como Markdown. | + +## Buscar por tamaño de archivo + +Puedes utilizar el calificador `size` (tamaño) para buscar código fuente en base al tamaño del archivo donde existe el código. El calificador `size` utiliza [calificadores mayor que, menor que y rango](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax) para filtrar resultados en base al tamaño de bytes del archivo en donde se encuentra el código. + +| Qualifier | Ejemplo | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| size:n | [**function size:>10000 language:python**](https://github.com/search?q=function+size%3A%3E10000+language%3Apython&type=Code) encuentra código con la palabra "function," escrita en Python, en archivos que son mayores a 10 KB. | + +## Buscar por nombre de archivo + +El calificador `filename` (nombre de archivo) encuentra archivos de código con un determinado nombre de archivo. También puedes encontrar un archivo en un repositorio utilizando el buscador de archivo. Para obtener más información, consulta "[Encontrar archivos en GitHub](/search-github/searching-on-github/finding-files-on-github)." + +| Qualifier | Ejemplo | +| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| filename:FILENAME | [**filename:linguist**](https://github.com/search?utf8=%E2%9C%93&q=filename%3Alinguist&type=Code) encuentra archivos con el nombre de "linguist." | +| | [**filename:.vimrc commands**](https://github.com/search?q=filename%3A.vimrc+commands&type=Code) encuentra los archivos *.vimrc* con la palabra "commands". | +| | [**filename:test_helper path:test language:ruby**](https://github.com/search?q=minitest+filename%3Atest_helper+path%3Atest+language%3Aruby&type=Code) encuentra archivos Ruby con el nombre *test_helper* dentro del directorio *test*. | + +## Buscar por extensión de archivo + +El calificador `extension` (extensión) encuentra archivos de código con una determinada extensión de archivo. + +| Qualifier | Ejemplo | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| extension:EXTENSION | [**form path:cgi-bin extension:pm**](https://github.com/search?q=form+path%3Acgi-bin+extension%3Apm&type=Code) encuentra el código con la palabra "form", debajo de cgi-bin, con la extensión de archivo .pm. | +| | [**icon size:>200000 extension:css**](https://github.com/search?utf8=%E2%9C%93&q=icon+size%3A%3E200000+extension%3Acss&type=Code) busca archivos más grandes de 200 KB que terminan en .css y tienen la palabra "icon". | + +## Leer más + +- "[Clasificar los resultados de la búsqueda](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" +- "[Buscar en ramificaciones](/search-github/searching-on-github/searching-in-forks)"{% ifversion fpt %} +- "[Navegar en el código de {% data variables.product.prodname_dotcom %}](/github/managing-files-in-a-repository/navigating-code-on-github)"{% endif %} diff --git a/translations/es-ES/content/search-github/searching-on-github/searching-commits.md b/translations/es-ES/content/search-github/searching-on-github/searching-commits.md new file mode 100644 index 0000000000..4524ed3d72 --- /dev/null +++ b/translations/es-ES/content/search-github/searching-on-github/searching-commits.md @@ -0,0 +1,111 @@ +--- +title: Buscar confirmaciones de cambios +intro: 'Puedes buscar confirmaciones de cambios en {% data variables.product.product_name %} y acotar los resultados utilizando estos calificadores de búsqueda de confirmaciones con cualquier combinación.' +redirect_from: + - /articles/searching-commits + - /github/searching-for-information-on-github/searching-commits + - /github/searching-for-information-on-github/searching-on-github/searching-commits +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +Puedes buscar confirmaciones de cambios globalmente a través de todos los {% data variables.product.product_name %}, o buscar confirmaciones de cambios dentro de un repositorio particular u organización. Para obtener más información, consulta "[Acerca de buscar en {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)". + +Cuando buscas confirmaciones de cambios, se busca únicamente la [rama predeterminada](/articles/about-branches) de un repositorio. + +{% data reusables.search.syntax_tips %} + +## Buscar dentro de los mensajes de confirmación + +Puedes encontrar confirmaciones que contengan determinadas palabras en el mensaje. Por ejemplo, [**fix typo**](https://github.com/search?q=fix+typo&type=Commits) encuentra las confirmaciones que contienen las palabras "fix" y "typo." + +## Buscar por el autor o la persona que confirma el cambio + +Puedes encontrar confirmaciones de cambios por un usuario particular con los calificadores `author` (autor) o `committer` (persona que confirma el cambio). + +| Qualifier | Ejemplo | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | +| author:USERNAME | [**author:defunkt**](https://github.com/search?q=author%3Adefunkt&type=Commits) encuentra confirmaciones cuya autoría corresponde a @defunkt. | +| committer:USERNAME | [**committer:defunkt**](https://github.com/search?q=committer%3Adefunkt&type=Commits) encuentra confirmaciones de @defunkt. | + +Los calificadores `author-name` y `committer-name` encuentran confirmaciones por el nombre de su autor o de la persona que confirma el cambio. + +| Qualifier | Ejemplo | +| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| author-name:NAME | [**author-name:wanstrath**](https://github.com/search?q=author-name%3Awanstrath&type=Commits) encuentra confirmaciones con "wanstrath" en el nombre de autor. | +| committer-name:NAME | [**committer-name:wanstrath**](https://github.com/search?q=committer-name%3Awanstrath&type=Commits) encuentra confirmaciones con "wanstrath" en el nombre de la persona que confirma el cambio. | + +Los calificadores `author-email` y `committer-email` encuentran confirmaciones por la dirección completa de correo electrónico del autor o de la persona que confirma el cambio. + +| Qualifier | Ejemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| author-email:EMAIL | [**author-email:chris@github.com**](https://github.com/search?q=author-email%3Achris%40github.com&type=Commits) encuentra confirmaciones cuyo autor es chris@github.com. | +| committer-email:EMAIL | [**committer-email:chris@github.com**](https://github.com/search?q=committer-email%3Achris%40github.com&type=Commits) encuentra confirmaciones de chris@github.com. | + +## Buscar por fecha de autoría o de confirmación + +Utiliza los calificadores `author-date` y `committer-date` para encontrar confirmaciones que fueron creadas o confirmadas dentro de un rango de fechas especificado. + +{% data reusables.search.date_gt_lt %} + +| Qualifier | Ejemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| author-date:YYYY-MM-DD | [**author-date:<2016-01-01**](https://github.com/search?q=author-date%3A<2016-01-01&type=Commits) encuentra confirmaciones creadas antes del 2016-01-01. | +| committer-date:YYYY-MM-DD | [**committer-date:>2016-01-01**](https://github.com/search?q=committer-date%3A>2016-01-01&type=Commits) encuentra las confirmaciones que se crearon después del 2016-01-01. | + +## Filtrar confirmaciones de fusión + +Los filtros del calificador `merge` de confirmación de fusión. + +| Qualifier | Ejemplo | +| ------------- | ---------------------------------------------------------------------------------------------------------------- | +| `merge:true` | [**merge:true**](https://github.com/search?q=merge%3Atrue&type=Commits) encuentra confirmaciones de fusión. | +| `merge:false` | [**merge:false**](https://github.com/search?q=merge%3Afalse&type=Commits) encuentra confirmaciones de no fusión. | + +## Filtrar por hash + +El calificador `hash` encuentra confirmaciones con el hash SHA-1 especificado. + +| Qualifier | Ejemplo | +| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| hash:HASH | [**hash:124a9a0ee1d8f1e15e833aff432fbb3b02632105**](https://github.com/github/gitignore/search?q=hash%3A124a9a0ee1d8f1e15e833aff432fbb3b02632105&type=Commits) encuentra confirmaciones con el hash `124a9a0ee1d8f1e15e833aff432fbb3b02632105`. | + +## Filtrar por padre + +El calificador `parent` (padre) encuentra confirmaciones cuyo padre tiene el hash SHA-1 especificado. + +| Qualifier | Ejemplo | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| parent:HASH | [**parent:124a9a0ee1d8f1e15e833aff432fbb3b02632105**](https://github.com/github/gitignore/search?q=parent%3A124a9a0ee1d8f1e15e833aff432fbb3b02632105&type=Commits&utf8=%E2%9C%93) encuentra el hijo de las confirmaciones con el hash `124a9a0ee1d8f1e15e833aff432fbb3b02632105`. | + +## Filtrar por árbol + +El calificador `tree` (árbol) encuentra confirmaciones con el hash de árbol de git SHA-1 especificado. + +| Qualifier | Ejemplo | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| tree:HASH | [**tree:99ca967**](https://github.com/github/gitignore/search?q=tree%3A99ca967&type=Commits) encuentra confirmaciones que se refieren al hash del árbol `99ca967`. | + +## Buscar dentro de los repositorios de un usuario u organización + +Para buscar confirmaciones en todos los repositorios que son propiedad de una determinada organización o usuario, utiliza el calificador `user` (usuario) u `org` (organización). Para buscar confirmaciones en un repositorio específico, utiliza el calificador `repo`. + +| Qualifier | Ejemplo | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| user:USERNAME | [**gibberish user:defunkt**](https://github.com/search?q=gibberish+user%3Adefunkt&type=Commits&utf8=%E2%9C%93) encuentra mensajes de confirmación con la palabra "gibberish" en repositorios propiedad de @defunkt. | +| org:ORGNAME | [**test org:github**](https://github.com/search?utf8=%E2%9C%93&q=test+org%3Agithub&type=Commits) encuentra mensajes de confirmación con la palabra "test" en repositorios propiedad de @github. | +| repo:USERNAME/REPO | [**language repo:defunkt/gibberish**](https://github.com/search?utf8=%E2%9C%93&q=language+repo%3Adefunkt%2Fgibberish&type=Commits) encuentra mensajes de confirmación con la palabra "language" en un repositorio "gibberish" de @defunkt. | + +## Filtrar por visibilidad de repositorio + +El calificador `is` coincide con las confirmaciones de los repositorios con la visibilidad especificada. Para obtener más información, consulta la sección "[Acerca de los repositorios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)". + +| Calificador| Ejemplo | ------------- | ------------- |{% ifversion fpt or ghes %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Commits) coincide con las confirmaciones de los repositorios públicos.{% endif %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Commits) coincide con las confirmaciones de los repositorios internos. | `is:private` | [**is:private**](https://github.com/search?q=is%3Aprivate&type=Commits) coincide con las confirmaciones de los repositorios privados. + +## Leer más + +- "[Clasificar los resultados de la búsqueda](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" diff --git a/translations/es-ES/content/search-github/searching-on-github/searching-discussions.md b/translations/es-ES/content/search-github/searching-on-github/searching-discussions.md new file mode 100644 index 0000000000..63aa339234 --- /dev/null +++ b/translations/es-ES/content/search-github/searching-on-github/searching-discussions.md @@ -0,0 +1,113 @@ +--- +title: Buscar debates +intro: 'Puedes buscar debates en {% data variables.product.product_name %} y reducir los resultados utilizando calificadores.' +versions: + fpt: '*' +topics: + - GitHub search +redirect_from: + - /github/searching-for-information-on-github/searching-discussions + - /github/searching-for-information-on-github/searching-on-github/searching-discussions +--- + +## Acerca de buscar debates + +Puedes buscar debates globalmente a través de todo {% data variables.product.product_name %}, o buscar debates dentro de una organización o repositorio específicos. Para obtener más información, consulta [Acerca de buscar en {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/about-searching-on-github)". + +{% data reusables.search.syntax_tips %} + +## Buscar por título, cuerpo o comentarios + +Puedes restringir la búsqueda de debates al título, cuerpo o comentarios si utilizas el calificador `in`. También puedes combinar los calificadores para buscar una combinación de título, cuerpo o comentarios. Cuando omites el calificador `in`, {% data variables.product.product_name %} busca el título, cuerpo y comentarios. + +| Qualifier | Ejemplo | +|:------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `in:title` | [**welcome in:title**](https://github.com/search?q=welcome+in%3Atitle&type=Discussions) coincide con los debates que tengan "welcome" en el título. | +| `in:body` | [**onboard in:title,body**](https://github.com/search?q=onboard+in%3Atitle%2Cbody&type=Discussions) coincide con los debates que tengan "onboard" en el título o en el cuerpo. | +| `in:comments` | [**thanks in:comments**](https://github.com/search?q=thanks+in%3Acomment&type=Discussions) coincide con los debates que tengan "thanks" en sus comentarios. | + +## Buscar dentro de los repositorios de un usuario u organización + +Para buscar los debates en todos los repositorios que pertenezcan a algún usuario u organización, puedes utilizar el calificador `user` o `org`. Para buscar los debates en un repositorio específico, puedes utilizar el calificador `repo`. + +| Qualifier | Ejemplo | +|:------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**user:octocat feedback**](https://github.com/search?q=user%3Aoctocat+feedback&type=Discussions) coincide con debates con la palabra "retroalimentación" de los repositorios que pertenezcan a @octocat. | +| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=Discussions&utf8=%E2%9C%93) coincide con los debates en los repositorios que pertenezcan a la organización GitHub. | +| repo:USERNAME/REPOSITORY | [**repo:nodejs/node created:<2021-01-01**](https://github.com/search?q=repo%3Anodejs%2Fnode+created%3A%3C2020-01-01&type=Discussions) coincide con los debates del proyecto de tiempo de ejecución de Node.js de @nodejs que se crearon antes de enero de 2021. | + +## Filtrar por visibilidad de repositorio + +Puedes filtrar los resultados por la visibilidad del repositorio que contenga los debates que utilicen el calificador `is`. Para obtener más información, consulta la sección "[Acerca de los repositorios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)". + +| Calificador| Ejemplo | :- | :- |{% ifversion fpt or ghes %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Discussions) coincide con los debates en los repositorios públicos.{% endif %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Discussions) coincide con los debates en los repositorios internos. | `is:private` | [**is:private tiramisu**](https://github.com/search?q=is%3Aprivate+tiramisu&type=Discussions) coincide con los debates que contiene la palabra "tiramisu" en los repositorios privados a los que puedes acceder. + +## Buscar por autor + +El calificador `author` encuentra debates crean usuarios específicos. + +| Qualifier | Ejemplo | +|:------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| author:USERNAME | [**cool author:octocat**](https://github.com/search?q=cool+author%3Aoctocat&type=Discussions) coincide con debates que tienen la palabra "cool" y que creó @octocat. | +| | [**bootstrap in:body author:octocat**](https://github.com/search?q=bootstrap+in%3Abody+author%3Aoctocat&type=Discussions) coincide con debates que creó @octocat y que contienen la palabra "bootstrap" enel cuerpo. | + +## Buscar por comentarista + +El calificador `commenter` encuentra debates que contienen un comentario de un usuario específico. + +| Qualifier | Ejemplo | +|:------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| commenter:USERNAME | [**github commenter:becca org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Abecca+org%3Agithub&type=Discussions) coincide con debates en los repositorios que pertenecen a GitHub, los cuales contengan la palabra "github" y un comentario de @becca. | + +## Buscar por un usuario que está involucrado en un debate + +Puedes utilizar el calificador `involves` para encontrar debates que involucren a algún usuario. El calificador devuelve los debates que un usuario haya creado, que mencionen al usuario, o que contengan sus comentarios. El calificador `involves` es un operador lógico OR (o) entre los calificadores `author`, `mentions`, y `commenter` para un usuario único. + +| Qualifier | Ejemplo | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| involves:USERNAME | **[involves:becca involves:octocat](https://github.com/search?q=involves%3Abecca+involves%3Aoctocat&type=Discussions)** coincide con debates en los que se involucre ya sea a @becca o a @octocat. | +| | [**NOT beta in:body involves:becca**](https://github.com/search?q=NOT+beta+in%3Abody+involves%3Abecca&type=Discussions) coincide con debates en los que se involucre a @becca, en los cuales no se contenga la palabra "beta" dentro del cuerpo. | + +## Buscar por cantidad de comentarios + +Puedes utilizar el calificador `comments` junto con los calificadores de mayor que, menor que y de rango para buscar por cantidad de comentarios. Para obtener más información, consulta la sección "[Entender la sintaxis de búsqueda](/github/searching-for-information-on-github/understanding-the-search-syntax)". + +| Qualifier | Ejemplo | +|:------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------- | +| comments:n | [**comments:>100**](https://github.com/search?q=comments%3A%3E100&type=Discussions) coincide con debates de más de 100 comentarios. | +| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Discussions) coincide con debates que tengan entre 500 y 1,000 comentarios. | + +## Buscar por cantidad de interacciones + +Puedes filtrar debates por el número de interacciones con el calificador `interactions` junto con los calificadores de mayor qué, menor qué y de rango. El conteo de interacciones es la cantidad de reacciones y comentarios en un debate. Para obtener más información, consulta la sección "[Entender la sintaxis de búsqueda](/github/searching-for-information-on-github/understanding-the-search-syntax)". + +| Qualifier | Ejemplo | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------- | +| interactions:n | [** interactions:>2000**](https://github.com/search?q=interactions%3A%3E2000) coincide con los debates de más de 2,000 interacciones. | +| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) coincide con los debates que tengan entre 500 y 1,000 interacciones. | + +## Buscar por cantidad de reacciones + +Puedes filtrar los debates de acuerdo con la cantidad de reacciones si utilizas el calificador `reactions` junto con los calificadores de mayor qué, menor qué y rango. Para obtener más información, consulta la sección "[Entender la sintaxis de búsqueda](/github/searching-for-information-on-github/understanding-the-search-syntax)". + +| Qualifier | Ejemplo | +|:------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------- | +| reactions:n | [** reactions:>1000**](https://github.com/search?q=reactions%3A%3E500) coincide con debates con más de 500 reacciones. | +| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) coincide con los debtes que tengan entre 500 y 1,000 reacciones. | + +## Buscar por cuándo se creó o actualizó por última vez un debate + +Puedes filtrar los debates con base en las fechas de creación o por cuándo se actualizaron por última vez. Para la creación de debates, puedes utilizar el calificador `created`; para saber cuándo se actualizó por última vez el debate, utiliza el calificador `updated`. + +Ambos calificadores toman la fecha como parámetro. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifier | Ejemplo | +|:-------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| created:YYYY-MM-DD | [**created:>2020-11-15**](https://github.com/search?q=created%3A%3E%3D2020-11-15&type=discussions) coincide con debates que se crearon después del 15 de noviembre de 2020. | +| updated:YYYY-MM-DD | [**weird in:body updated:>=2020-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2020-12-01&type=Discussions) coincide con debates que tengan la palabra "weird" en el cuerpo y que se hayan actualizado después de diciembre de 2020. | + +## Leer más + +- "[Clasificar los resultados de la búsqueda](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" diff --git a/translations/es-ES/content/search-github/searching-on-github/searching-for-packages.md b/translations/es-ES/content/search-github/searching-on-github/searching-for-packages.md new file mode 100644 index 0000000000..8dcde61069 --- /dev/null +++ b/translations/es-ES/content/search-github/searching-on-github/searching-for-packages.md @@ -0,0 +1,45 @@ +--- +title: Buscar paquetes +intro: 'Puedes buscar paquetes en {% data variables.product.product_name %} y acotar los resultados utilizando los calificadores de búsqueda.' +product: '{% data reusables.gated-features.packages %}' +permissions: Anyone can search for packages they have access to. +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +redirect_from: + - /github/searching-for-information-on-github/searching-for-packages + - /github/searching-for-information-on-github/searching-on-github/searching-for-packages +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +## Acerca de la búsqueda de paquetes + +Puedes buscar paquetes globalmente a través de todo {% data variables.product.product_name %}, o buscarlos dentro de una organización en particular. Para obtener más información, consulta [Acerca de buscar en {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)". + +{% ifversion ghes %} +Solo puedes buscar paquetes en {% data variables.product.product_name %}, no en {% data variables.product.prodname_dotcom_the_website %}, incluso si estpa habilitado {% data variables.product.prodname_github_connect %}. +{% endif %} + +{% data reusables.search.syntax_tips %} + +## Buscar dentro de los paquetes de una organización o usuario + +Para encontrar paquetes que sean propiedad de cierto usuario u organización, utiliza el calificador `user` u `org`. + +| Qualifier | Ejemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**user:codertocat**](https://github.com/search?q=user%3Acodertocat&type=RegistryPackages) coincidirá con paquetes que sean propiedad de @codertocat | +| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=RegistryPackages) coincidirá con paquetes que sean propiedad de la organización {% data variables.product.prodname_dotcom %} + +## Filtrar por visibilidad del paquete + +Para filtrar tu búsqueda por el criterio de si el paquete es público o privado, utiliza el calificador `is`. + +| Qualifier | Ejemplo | +| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `is:public` | [**is:public angular**](https://github.com/search?q=is%3Apublic+angular&type=RegistryPackages) coincidirá con los paquetes públicos que contengan la palabra "angular" | +| `is:private` | [**is:private php**](https://github.com/search?q=is%3Aprivate+php&type=RegistryPackages) coincidirá con los paquetes privados que contengan la palabra "php" | diff --git a/translations/es-ES/content/search-github/searching-on-github/searching-for-repositories.md b/translations/es-ES/content/search-github/searching-on-github/searching-for-repositories.md new file mode 100644 index 0000000000..1d368e3518 --- /dev/null +++ b/translations/es-ES/content/search-github/searching-on-github/searching-for-repositories.md @@ -0,0 +1,201 @@ +--- +title: Buscar repositorios +intro: 'Puedes buscar repositorios en {% data variables.product.product_name %} y acotar los resultados utilizando estos calificadores de búsqueda de repositorio en cualquier combinación.' +redirect_from: + - /articles/searching-repositories/ + - /articles/searching-for-repositories + - /github/searching-for-information-on-github/searching-for-repositories + - /github/searching-for-information-on-github/searching-on-github/searching-for-repositories +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +shortTitle: Buscar repositorios +--- + +Puedes buscar repositorios globalmente a través de todos los {% data variables.product.product_location %}, o buscar repositorios dentro de una organización particular. Para obtener más información, consulta [Acerca de buscar en {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)". + +Para incluir bifurcaciones en los resultados de las búsquedas, deberás agregar `fork:true` o `fork:only` en tu consulta. Para obtener más información, consulta "[Buscar en bifurcaciones](/search-github/searching-on-github/searching-in-forks)". + +{% data reusables.search.syntax_tips %} + +## Buscar por nombre de repositorio, descripción o contenidos del archivo README + +Con el calificador `in` puedes restringir tu búsqueda al nombre del repositorio, su descripción, los contenidos del archivo README, o cualquier combinación de estos. Cuando omites este calificador, únicamente se buscan el nombre del repositorio y la descripción. + +| Qualifier | Ejemplo | +| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `in:name` | [**jquery in:name**](https://github.com/search?q=jquery+in%3Aname&type=Repositories) coincide con repositorios que tengan "jquery" en su nombre. | +| `in:description` | [**jquery in:name,description**](https://github.com/search?q=jquery+in%3Aname%2Cdescription&type=Repositories) coincide con repositorios que tengan "jquary" en su nombre o descripción. | +| `in:readme` | [**jquery in:readme**](https://github.com/search?q=jquery+in%3Areadme&type=Repositories) coincide con repositorios que mencionen "jquery" en su archivo README. | +| `repo:owner/name` | [**repo:octocat/hello-world**](https://github.com/search?q=repo%3Aoctocat%2Fhello-world) encuentra un nombre de repositorio específico. | + +## Buscar en base a los contenidos de un repositorio + +Puedes encontrar un repositorio si buscas el contenido de su archivo README utilizando el calificador `in:readme`. Para obtener más información, consulta "[Acerca de los README](/github/creating-cloning-and-archiving-repositories/about-readmes)". + +Además de utilizar `in:readme`, no es posible encontrar repositorios al buscar por el contenido específico dentro del repositorio. Para buscar un archivo o contenido específico dentro de un repositorio, puedes utilizar el buscador de archivo o los calificadores de búsqueda específica. Para obtener más información, consulta "[Encontrar archivos en {% data variables.product.prodname_dotcom %}](/search-github/searching-on-github/finding-files-on-github)" y "[Buscar código](/search-github/searching-on-github/searching-code)." + +| Qualifier | Ejemplo | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `in:readme` | [**octocat in:readme**](https://github.com/search?q=octocat+in%3Areadme&type=Repositories) coincide con repositorios que mencionen "octocat" en su archivo README. | + +## Buscar dentro de los repositorios de un usuario u organización + +Para buscar en todos los repositorios que son propiedad de una determinada organización o usuario, puedes utilizar el calificador `user` u `org`. + +| Qualifier | Ejemplo | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**user:defunkt forks:>100**](https://github.com/search?q=user%3Adefunkt+forks%3A%3E%3D100&type=Repositories) encuentra repositorios de @defunkt que tienen más de 100 bifurcaciones. | +| org:ORGNAME | [**org:github**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub&type=Repositories) encuentra repositorios de GitHub. | + +## Buscar por tamaño del repositorio + +El calificador `size` encuentra repositorios que coinciden con un tamaño determinado (en kilobytes), utilizando los calificadores de mayor que, menor que y rango. Para obtener más información, consulta la sección "[Entender la sintaxis de búsqueda](/github/searching-for-information-on-github/understanding-the-search-syntax)". + +| Qualifier | Ejemplo | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | +| size:n | [**size:1000**](https://github.com/search?q=size%3A1000&type=Repositories) encuentra repositorios que tienen más de 1 MB con exactitud. | +| | [**size:>=30000**](https://github.com/search?q=size%3A%3E%3D30000&type=Repositories) encuentra repositorios que tienen por lo menos 30 MB. | +| | [**size:<50**](https://github.com/search?q=size%3A%3C50&type=Repositories) encuentra repositorios que son menores de 50 KB. | +| | [**size:50..120**](https://github.com/search?q=size%3A50..120&type=Repositories) encuentra repositorios que están entre 50 KB y 120 KB. | + +## Buscar por cantidad de seguidores + +Puedes filtrar los repositorios con base en la cantidad de usuarios que los siguen, utilizando el calificador `followers` con aquellos de mayor qué, menor qué y rango. Para obtener más información, consulta la sección "[Entender la sintaxis de búsqueda](/github/searching-for-information-on-github/understanding-the-search-syntax)". + +| Qualifier | Ejemplo | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| followers:n | [**node followers:>=10000**](https://github.com/search?q=node+followers%3A%3E%3D10000) coincidirá con repositorios que tengan 10,000 o más seguidores y en donde se mencione la palabra "node". | +| | [**styleguide linter followers:1..10**](https://github.com/search?q=styleguide+linter+followers%3A1..10&type=Repositories) encuentra repositorios con 1 a 10 seguidores, que mencionan la palabra "styleguide linter." | + +## Buscar por cantidad de bifurcaciones + +El calificador `forks` especifica la cantidad de bifurcaciones que un repositorio debería tener, utilizando los calificadores de mayor qué, menor qué y rango. Para obtener más información, consulta la sección "[Entender la sintaxis de búsqueda](/github/searching-for-information-on-github/understanding-the-search-syntax)". + +| Qualifier | Ejemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | +| forks:n | [**forks:5**](https://github.com/search?q=forks%3A5&type=Repositories) encuentra repositorios con solo cinco bifurcaciones. | +| | [**forks:>=205**](https://github.com/search?q=forks%3A%3E%3D205&type=Repositories) encuentra repositorios con por lo menos 205 bifurcaciones. | +| | [**forks:<90**](https://github.com/search?q=forks%3A%3C90&type=Repositories) encuentra repositorios con menos de 90 bifurcaciones. | +| | [**forks:10..20**](https://github.com/search?q=forks%3A10..20&type=Repositories) encuentra repositorios con 10 a 20 bifurcaciones. | + +## Buscar por cantidad de estrellas + +Puedes buscar repositorios con base en la cantidad de estrellas que tienen, utilizando los calificadores de mayor qué, menor qué y rango. Para obtener más información, consulta las secciones "[Guardar los repositorios con estrellas](/github/getting-started-with-github/saving-repositories-with-stars)" y "[Entender la sintaxis de búsqueda](/github/searching-for-information-on-github/understanding-the-search-syntax)". + +| Qualifier | Ejemplo | +| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| stars:n | [**stars:500**](https://github.com/search?utf8=%E2%9C%93&q=stars%3A500&type=Repositories) encuentra repositorios con exactamente 500 estrellas. | +| | [**stars:10..20**](https://github.com/search?q=stars%3A10..20+size%3A%3C1000&type=Repositories) encuentra repositorios con 10 a 20 estrellas, que son menores que 1000 KB. | +| | [**stars:>=500 fork:true language:php**](https://github.com/search?q=stars%3A%3E%3D500+fork%3Atrue+language%3Aphp&type=Repositories) encuentra repositorios con al menos 500 estrellas, incluidas los bifurcados, que están escritos en PHP. | + +## Buscar por cuándo fue creado o actualizado por última vez un repositorio + +Puedes filtrar repositorios en base al momento de creación o al momento de la última actualización. Para la creación de un repositorio, puedes usar el calificador `created` (creado); para encontrar cuándo se actualizó por última vez un repositorio, querrás utilizar el calificador `pushed` (subido). El calificador `pushed` devolverá una lista de repositorios, clasificados por la confirmación más reciente realizada en alguna rama en el repositorio. + +Ambos toman una fecha como su parámetro. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifier | Ejemplo | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| created:YYYY-MM-DD | [**webos created:<2011-01-01**](https://github.com/search?q=webos+created%3A%3C2011-01-01&type=Repositories) encuentra repositorios con la palabra "webos" que fueron creados antes del 2011. | +| pushed:YYYY-MM-DD | [**css pushed:>2013-02-01**](https://github.com/search?utf8=%E2%9C%93&q=css+pushed%3A%3E2013-02-01&type=Repositories) encuentra repositorios con la palabra "css" que fueron subidos después de enero de 2013. | +| | [**case pushed:>=2013-03-06 fork:only**](https://github.com/search?q=case+pushed%3A%3E%3D2013-03-06+fork%3Aonly&type=Repositories) encuentra repositorios con la palabra "case" que fueron subidos el 6 de marzo de 2013 o después, y que son bifurcaciones. | + +## Buscar por lenguaje + +Puedes buscar repositorios con base en el lenguaje de programación del código que contienen. + +| Qualifier | Ejemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| language:LANGUAGE | [**rails language:javascript**](https://github.com/search?q=rails+language%3Ajavascript&type=Repositories) encuentra repositorios con la palabra "rails" que están escritos en JavaScript. | + +## Buscar por tema + +Puedes encontrar todos los repositorios que se clasifiquen con un tema particular. Para obtener más información, consulta "[Clasificar tu repositorio con temas](/github/administering-a-repository/classifying-your-repository-with-topics)". + +| Qualifier | Ejemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| topic:TOPIC | [**topic:jekyll**](https://github.com/search?utf8=%E2%9C%93&q=topic%3Ajekyll&type=Repositories&ref=searchresults) encuentra repositorios que se han clasificado con el tema "jekyll." | + +## Buscar por cantidad de temas + +Puedes buscar repositorios por la cantidad de temas que se les hayan aplicado utilizando el calificador `topics` en conjunto con aquellos de mayor qué, menor qué y rango. Para obtener más información, consulta las secciones "[Clasificar tu repositorio con temas](/github/administering-a-repository/classifying-your-repository-with-topics)" y "[Entender la sintaxis de búsqueda](/github/searching-for-information-on-github/understanding-the-search-syntax)". + +| Qualifier | Ejemplo | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| topics:n | [**topics:5**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A5&type=Repositories&ref=searchresults) encuentra repositorios que tienen cinco temas. | +| | [**topics:>3**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A%3E3&type=Repositories&ref=searchresults) coincidirá con repositorios que tengan más de tres temas. | + +{% ifversion fpt or ghes %} + +## Buscar por licencia + +Puedes buscar repositorios con por su tipo de licencia. Debes utilizar una palabra clave de licencia para filtrar los repositorios por algún tipo particular o familia de licencias. Para obtener más información, consulta "[Licenciar un repositorio](/github/creating-cloning-and-archiving-repositories/licensing-a-repository)". + +| Qualifier | Ejemplo | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| license:LICENSE_KEYWORD | [**license:apache-2.0**](https://github.com/search?utf8=%E2%9C%93&q=license%3Aapache-2.0&type=Repositories&ref=searchresults) encuentra repositorios que tienen licencia de Apache License 2.0. | + +{% endif %} + +## Buscar por visibilidad del repositorio + +Puedes filtrar tu búsqueda con base en la visibilidad de los repositorios. Para obtener más información, consulta la sección "[Acerca de los repositorios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)". + +| Calificador | Ejemplo | ------------- | ------------- |{% ifversion fpt or ghes %} | `is:public` | [**is:public org:github**](https://github.com/search?q=is%3Apublic+org%3Agithub&type=Repositories) empata con los repositorios públicos que pertenezcan a {% data variables.product.company_short %}.{% endif %} | `is:internal` | [**is:internal test**](https://github.com/search?q=is%3Ainternal+test&type=Repositories) empata con los repositorios internos a los que puedes acceder y que contengan la palabra "test". | `is:private` | [**is:private pages**](https://github.com/search?q=is%3Aprivate+pages&type=Repositories) coincide con los repositorios privados a los cuales puedes acceder y que contengan la palabra "pages". + +{% ifversion fpt %} + +## Buscar en base a si un repositorio es un espejo + +Puedes buscar repositorios con base en si éstos son espejos y se hospedan en otro lugar. Para obtener más información, consulta "[Encontrar formas de contribuir al código abierto en {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)." + +| Qualifier | Ejemplo | +| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `mirror:true` | [**mirror:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Atrue+GNOME&type=) coincide con los repositorios que son espejos y que contienen la palabra "GNOME". | +| `mirror:false` | [**mirror:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Afalse+GNOME&type=) coincide con los repositorios que no son espejos y que contienen la palabra "GNOME". | + +{% endif %} + +## Buscar en base a si un repositorio está archivado + +Puedes buscar los repositorios con base en si se archivaron o no. Para obtener más información, consulta la sección "[Archivar los repositorios](/repositories/archiving-a-github-repository/archiving-repositories)". + +| Qualifier | Ejemplo | +| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `archived:true` | [**archived:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Atrue+GNOME&type=) coincide con los repositorios que se archivan y que contienen la palabra "GNOME". | +| `archived:false` | [**archived:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Afalse+GNOME&type=) coincide con los repositorios que no están archivados y que contienen la palabra "GNOME". | + +{% ifversion fpt %} + +## Buscar en base a la cantidad de propuestas con las etiquetas `good first issue` o `help wanted` + +Puedes buscar repositorios que tienen una cantidad mínima de propuestas etiquetadas como `help-wanted` (se necesita ayuda) o `good-first-issue` (buena propuesta inicial) con los calificadores `help-wanted-issues:>n` y `good-first-issues:>n`. Para encontrar más información, consulta "[Fomentar las contribuciones útiles a tu proyecto con etiquetas](/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels)." + +| Qualifier | Ejemplo | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `good-first-issues:>n` | [**good-first-issues:>2 javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+good-first-issues%3A%3E2&type=) encuentra repositorios con más de dos propuestas etiquetadas como `good-first-issue` y que contienen la palabra "javascript." | +| `help-wanted-issues:>n` | [**help-wanted-issues:>4 react**](https://github.com/search?utf8=%E2%9C%93&q=react+help-wanted-issues%3A%3E4&type=) encuentra repositorios con más de cuatro propuestas etiquetadas como `help-wanted` y que contienen la palabra "React." | + +## Búsqueda basada en la capacidad de patrocinar + +Puedes buscar repositorios cuyos propietarios puedan patrocinarse en {% data variables.product.prodname_sponsors %} con el calificador `is:sponsorable`. Para obtener más información, consulta "[Acerca de {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)". + +Puedes buscar repositorios que tengan un archivo de fondos utilizando el calificador `has:funding-file`. Para obtener más información, consulta la sección "[Acerca de los archivos de FONDOS](/github/administering-a-repository/managing-repository-settings/displaying-a-sponsor-button-in-your-repository#about-funding-files)". + +| Qualifier | Ejemplo | +| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `is:sponsorable` | [**is:sponsorable**](https://github.com/search?q=is%3Asponsorable&type=Repositories) encuentra repositorios cuyos propietarios tengan un perfil de {% data variables.product.prodname_sponsors %}. | +| `has:funding-file` | [**has:funding-file**](https://github.com/search?q=has%3Afunding-file&type=Repositories) encuentra repositorios que tengan un archivo de FUNDING.yml. | + +{% endif %} + +## Leer más + +- "[Clasificar los resultados de la búsqueda](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" +- "[Búsqueda en bifurcaciones](/search-github/searching-on-github/searching-in-forks)" diff --git a/translations/es-ES/content/search-github/searching-on-github/searching-github-marketplace.md b/translations/es-ES/content/search-github/searching-on-github/searching-github-marketplace.md new file mode 100644 index 0000000000..1dd79dd9f3 --- /dev/null +++ b/translations/es-ES/content/search-github/searching-on-github/searching-github-marketplace.md @@ -0,0 +1,38 @@ +--- +title: Buscar en el Mercado de GitHub +intro: 'Puedes buscar aplicaciones y acciones disponibles en{% data variables.product.prodname_marketplace %}.' +versions: + fpt: '*' +topics: + - GitHub search +redirect_from: + - /github/searching-for-information-on-github/searching-github-marketplace + - /github/searching-for-information-on-github/searching-on-github/searching-github-marketplace +shortTitle: Buscar en GitHub Marketplace +--- + +## Acerca de buscar en {% data variables.product.prodname_marketplace %} + +Puedes encontrar aplicaciones y acciones en{% data variables.product.prodname_marketplace %} de dos formas: + +- Buscar en{% data variables.product.prodname_marketplace %}. +- Buscar a través de todo {% data variables.product.prodname_dotcom_the_website %} y filtrar los resultados posteriormente. + +## Buscar en {% data variables.product.prodname_marketplace %} + +1. En la parte superior de cualquier página, da clic en **Mercado**. ![Enlace a Mercado](/assets/images/help/search/marketplace-link.png) +2. Teclea cualquier palabra clave y presiona **Enter**. ![Buscar linter en {% data variables.product.prodname_marketplace %}](/assets/images/help/search/marketplace-apps-and-actions-search-field.png) +3. Opcionalmente, filtra tus resultados dando clic en una o más opciones en la barra lateral. + +## Buscar a través de {% data variables.product.prodname_dotcom_the_website %} + +Cada vez que buscas en todo {% data variables.product.prodname_dotcom_the_website %}, puedes filtrar los resultados para ver las coincidencias de aplicaciones y acciones de {% data variables.product.prodname_marketplace %}. + +1. Navega hasta https://github.com/search. +2. Teclea cualquier palabra clave y presiona **Enter**. ![campo buscar](/assets/images/help/search/search-field.png) +3. En la barra lateral, da clic en **Mercado**. ![Buscar resultados para linter con la opción del menú lateral del Mercado resaltada](/assets/images/help/search/marketplace-left-side-navigation.png) + +## Leer más + +- "[Acerca de {% data variables.product.prodname_marketplace %}](/github/customizing-your-github-workflow/about-github-marketplace)" +- "[Utilizar acciones de {% data variables.product.prodname_marketplace %} en tu flujo de trabajo](/actions/automating-your-workflow-with-github-actions/using-actions-from-github-marketplace-in-your-workflow)" diff --git a/translations/es-ES/content/search-github/searching-on-github/searching-in-forks.md b/translations/es-ES/content/search-github/searching-on-github/searching-in-forks.md new file mode 100644 index 0000000000..71e1a2c79a --- /dev/null +++ b/translations/es-ES/content/search-github/searching-on-github/searching-in-forks.md @@ -0,0 +1,32 @@ +--- +title: Buscar en bifurcaciones +intro: 'Por defecto, las bifurcaciones [forks](/articles/about-forks) no se muestran en los resultados de la búsqueda. Puedes elegir incluirlas en las búsquedas de repositorios y en las búsquedas de código si cumplen con determinados criterios.' +redirect_from: + - /articles/searching-in-forks + - /github/searching-for-information-on-github/searching-in-forks + - /github/searching-for-information-on-github/searching-on-github/searching-in-forks +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +Para mostrar bifurcaciones en los resultados de la [búsqueda de repositorios](/search-github/searching-on-github/searching-for-repositories), agrega `fork:true` o `fork:only` en tu consulta. + +Las fiburcaciones solo se indexan por [búsqueda de código](/search-github/searching-on-github/searching-code) cuando tienen más estrellas que el repositorio padre. No podrás buscar el código en una bifurcación que tenga menos estrellas que su padre. Para mostrar bifurcaciones con más estrellas que el repositorio padre en los resultados de una búsqueda de código, agrega `fork:true` o `fork:only` en tu consulta. + +El calificador `fork:true` encuentra todos los resultados que coinciden con tu consulta de búsqueda, incluidas las bifurcaciones. El calificador `fork:only` encuentra _únicamente_ bifurcaciones que coinciden con tu consulta de búsqueda. + +| Qualifier | Ejemplo | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `fork:true` | [**github fork:true**](https://github.com/search?q=github+fork%3Atrue&type=Repositories) encuentra todos los repositorios que contienen la palabra "github," incluidas las bifurcaciones. | +| | [**android language:java fork:true**](https://github.com/search?q=android+language%3Ajava+fork%3Atrue&type=Code) encuentra código con la palabra "android" que está escrito en Java, tanto en bifurcaciones como en repositorios normales. | +| `fork:only` | [**github fork:only**](https://github.com/search?q=github+fork%3Aonly&type=Repositories) encuentra todos los repositorios de bifurcaciones que contienen la palabra "github." | +| | [**forks:>500 fork:only**](https://github.com/search?q=forks%3A%3E500+fork%3Aonly&type=Repositories) coincidirá con repositorios de más de 500 ramificaciones, y regresará únicamente aquellos que son ramificaciones. | + +## Leer más + +- "[Acerca de las bifurcaciones](/articles/about-forks)" +- "[Acerca de buscar en GitHub](/search-github/getting-started-with-searching-on-github/about-searching-on-github)" 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 new file mode 100644 index 0000000000..57f2b38e73 --- /dev/null +++ b/translations/es-ES/content/search-github/searching-on-github/searching-issues-and-pull-requests.md @@ -0,0 +1,343 @@ +--- +title: Buscar propuestas y solicitudes de extracción +intro: 'Puedes buscar propuestas y solicitudes de extracción en {% data variables.product.product_name %} y acotar los resultados utilizando estos calificadores de búsqueda en cualquier combinación.' +redirect_from: + - /articles/searching-issues/ + - /articles/searching-issues-and-pull-requests + - /github/searching-for-information-on-github/searching-issues-and-pull-requests + - /github/searching-for-information-on-github/searching-on-github/searching-issues-and-pull-requests +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +shortTitle: Buscar propuestas & solicitudes de cambio +--- + +Puedes buscar propuestas y solicitudes de extracción globalmente a través de todos los {% data variables.product.product_name %}, o buscar propuestas y solicitudes de extracción dentro de una organización particular. Para obtener más información, consulta "[Acerca de buscar en {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)". + +{% tip %} + +**Tips:**{% ifversion ghes or ghae %} + - Este artículo contiene búsquedas de ejemplo en el sitio web {% data variables.product.prodname_dotcom %}.com, pero puedes utilizar los mismos filtros de búsqueda en {% data variables.product.product_location %}.{% endif %} + - Para obtener una lista de sintaxis de búsqueda que puedas agregar a cualquier calificador para mejorar aún más tus resultados, consulta "[Comprender la sintaxis de búsqueda](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)". + - Utiliza comillas alrededor de los términos de búsqueda que contengan varias palabras. Por ejemplo, si deseas buscar propuestas con la etiqueta "In progress" (En curso), buscarías por la etiqueta `label:"in progress"`. Buscar no distingue entre mayúsculas y minúsculas. + - {% data reusables.search.search_issues_and_pull_requests_shortcut %} + + {% endtip %} + +## Buscar únicamente propuestas o solicitudes de extracción + +Por defecto, la búsqueda de {% data variables.product.product_name %} devolverá tanto propuestas como solicitudes de extracción. Sin embargo, puedes restringir los resultados de la búsqueda a solo propuestas y solicitudes de extracción utilizando el calificador `type` o `is`. + +| Qualifier | Ejemplo | +| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `type:pr` | [**cat type:pr**](https://github.com/search?q=cat+type%3Apr&type=Issues) encuentra solicitudes de extracción con la palabra "cat." | +| `type:issue` | [**github commenter:defunkt type:issue**](https://github.com/search?q=github+commenter%3Adefunkt+type%3Aissue&type=Issues) encuentra propuestas que contienen la palabra "github," y tienen un comentario de @defunkt. | +| `is:pr` | [**event is:pr**](https://github.com/search?utf8=%E2%9C%93&q=event+is%3Apr&type=) encuentra solicitudes de extracción con la palabra "event." | +| `is:issue` | [**is:issue label:bug is:closed**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aissue+label%3Abug+is%3Aclosed&type=) encuentra propuestas cerradas con la etiqueta "bug." | + +## Buscar por título, cuerpo o comentarios + +Con el calificador `in` puedes restringir tu búsqueda por título, cuerpo, comentarios o cualquier combinación de estos. Cuando omites este calificador, se buscan el título, el cuerpo y los comentarios, todos ellos. + +| Qualifier | Ejemplo | +| ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | +| `in:title` | [**warning in:title**](https://github.com/search?q=warning+in%3Atitle&type=Issues) encuentra propuestas con "warning" en su título. | +| `in:body` | [**error in:title,body**](https://github.com/search?q=error+in%3Atitle%2Cbody&type=Issues) encuentra propuestas con "error" en su título o cuerpo. | +| `in:comments` | [**shipit in:comments**](https://github.com/search?q=shipit+in%3Acomment&type=Issues) encuentra propuestas que mencionan "shipit" en sus comentarios. | + +## Buscar dentro de los repositorios de un usuario u organización + +Para buscar propuestas y solicitudes de extracción en todos los repositorios que son propiedad de un determinado usuario u organización, puedes utilizar el calificador `user` o `org`. Para buscar propuestas y solicitudes de extracción en un repositorio específico, puedes utilizar el calificador `repo`. + +{% data reusables.pull_requests.large-search-workaround %} + + +| Qualifier | Ejemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| user:USERNAME | [**user:defunkt ubuntu**](https://github.com/search?q=user%3Adefunkt+ubuntu&type=Issues) encuentra propuestas con la palabra "ubuntu" de repositorios que son propiedad de @defunkt. | +| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=Issues&utf8=%E2%9C%93) encuentra propuestas en repositorios que son propiedad de la organización de 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) coincidirá con informes de problemas del proyecto de shumway de @mozilla que fueron creados antes de marzo de 2012. | + + + +## Buscar por estado abierto o cerrado + +Puedes filtrar propuestas y solicitudes de extracción en base a si están abiertas o cerradas utilizando el calificador `state` o `is`. + +| Qualifier | Ejemplo | +| -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `state:open` | [**libraries state:open mentions:vmg**](https://github.com/search?utf8=%E2%9C%93&q=libraries+state%3Aopen+mentions%3Avmg&type=Issues) encuentra propuestas abiertas que mencionan a @vmg con la palabra "libraries." | +| `state:closed` | [**design state:closed in:body**](https://github.com/search?utf8=%E2%9C%93&q=design+state%3Aclosed+in%3Abody&type=Issues) encuentra propuestas cerradas con la palabra "design" en el cuerpo. | +| `is:open` | [**performance is:open is:issue**](https://github.com/search?q=performance+is%3Aopen+is%3Aissue&type=Issues) encuentra propuestas abiertas con la palabra "performance." | +| `is:closed` | [**android is:closed**](https://github.com/search?utf8=%E2%9C%93&q=android+is%3Aclosed&type=) encuentra propuestas y solicitudes de extracción cerradas con la palabra "android." | + +## Filtrar por visibilidad de repositorio + +Puedes filtrar por la visibilidad del repositorio que contenga las propuestas y solicitudes de cambios utilizando el calificador `is`. Para obtener más información, consulta la sección "[Acerca de los repositorios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)". + +| Calificador| Ejemplo | ------------- | ------------- |{% ifversion fpt or ghes %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Issues) empata con propuestas y solicitudes de cambio en los repositorios públicos.{% endif %}{% ifversion fpt or ghes or ghae %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Issues) empata con propuestas y solicitudes de cambio en los repositorios internos.{% endif %} | `is:private` | [**is:private cupcake**](https://github.com/search?q=is%3Aprivate+cupcake&type=Issues) empata con propuestas y solicitudes de cambio que contienen la palabra "cupacke" en los repositorios privados a los que puedes acceder. + +## Buscar por autor + +El calificador `author` (autor) encuentra propuestas y solicitudes de extracción creadas por un determinado usuario o cuenta de integración. + +| Qualifier | Ejemplo | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| author:USERNAME | [**cool author:gjtorikian**](https://github.com/search?q=cool+author%3Agjtorikian&type=Issues) coincide con las propeustas y solicitudes de cambios que contienen la palabra "cool" y que creó @gjtorikian. | +| | [**bootstrap in:body author:mdo**](https://github.com/search?q=bootstrap+in%3Abody+author%3Amdo&type=Issues) coincide con las propuestas que escribió @mdo y que contienen la palabra "bootstrap" en el cuerpo. | +| author:app/USERNAME | [**author:app/robot**](https://github.com/search?q=author%3Aapp%2Frobot&type=Issues) coincide con las propuestas que creó la cuenta de integración llamada "robot". | + +## Buscar por asignatario + +El calificador `assignee` (asignatario) encuentra propuestas y solicitudes de extracción que están asignadas a un determinado usuario. No puedes buscar propuestas y solicitudes que tengan _algún_ asignado cualquiera, sin embargo, puedes buscar por [propuestas y solicitudes de cambios que no tengan asignados](#search-by-missing-metadata). + +| Qualifier | Ejemplo | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| assignee:USERNAME | [**assignee:vmg repo:libgit2/libgit2**](https://github.com/search?utf8=%E2%9C%93&q=assignee%3Avmg+repo%3Alibgit2%2Flibgit2&type=Issues) coincide con las propuestas y solicitudes de cambio en el proyecto de libgit2 que se hayan asignado a @vmg. | + +## Buscar por mención + +El calificador `mentions` (menciones) encuentra propuestas que mencionan a un determinado usuario. Para obtener más información, consulta [Mencionar personas y equipos](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)." + +| Qualifier | Ejemplo | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| mentions:USERNAME | [**resque mentions:defunkt**](https://github.com/search?q=resque+mentions%3Adefunkt&type=Issues) coincide con las propuestas que tengan la palabra "resque" y que mencionen a @defunkt. | + +## Buscar por mención de equipo + +Para las organizaciones y los equipos a los que perteneces, puedes utilizar el calificador `team` (equipo) para encontrar propuestas y solicitudes de extracción que mencionan a un determinado equipo dentro de esa organización. Reemplaza estos nombres de ejemplo con el nombre de tu organización y equipo para realizar una búsqueda. + +| Qualifier | Ejemplo | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------- | +| team:ORGNAME/TEAMNAME | **team:jekyll/owners** coincide con las propeustas en donde se menciona al equipo `@jekyll/owners`. | +| | **team:myorg/ops is:open is:pr** coincide con las solicitudes de cambios en donde se menciona al equipo `@myorg/ops`. | + +## Buscar por comentarista + +El calificador `commenter` (comentarista) encuentra propuestas que contienen un comentario de un determinado usuario. + +| Qualifier | Ejemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| commenter:USERNAME | [**github commenter:defunkt org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Adefunkt+org%3Agithub&type=Issues) coincide con las propuestas en los repositorios que le pertenecen a GitHub y que contienen la palabra "github" y un comentario de @defunkt. | + +## Buscar por usuario que participa en una propuesta o solicitud de extracción + +Puedes utilizar el calificador `involves` para encontrar propuestas que de algún modo involucran a un determinado usuario. El calificador `involves` es un operador lógico OR (o) entre los calificadores `author`, `assignee`, `mentions` y `commenter` para un usuario único. En otras palabras, este calificador encuentra propuestas y solicitudes de extracción que fueron creadas por un determinado usuario, asignadas a ese usuario, que lo mencionan o que fueron comentadas por ese usuario. + +| Qualifier | Ejemplo | +| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| involves:USERNAME | **[involves:defunkt involves:jlord](https://github.com/search?q=involves%3Adefunkt+involves%3Ajlord&type=Issues)** coincide con las propeustas en donde estén involucrados ya sea @defunkt o @jlord. | +| | [**NOT bootstrap in:body involves:mdo**](https://github.com/search?q=NOT+bootstrap+in%3Abody+involves%3Amdo&type=Issues) coincide con las propuestas en donde se involucra a @mdo y que no contienen la palabra "bootstrap" en el cuerpo. | + +{% ifversion fpt or ghes or ghae %} +## Buscar reportes de problemas y solicitudes de extracción enlazados +Puedes acotar tus resultados para que solo incluyan informes de problemas que se enlazaron con solicitudes de extracción con una referencia cerrada, o solicitudes de extracción que se enlazaron a un informe de problemas que se pueden cerrar con otra solicitud de extracción. + +| Qualifier | Ejemplo | +| --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `linked:pr` | [**repo:desktop/desktop is:open linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+linked%3Apr) coincidirá con informes de problemas abiertos en el repositorio `desktop/desktop` que se enlazan a una solicitud de extracción con una referencia cerrada. | +| `linked:issue` | [**repo:desktop/desktop is:closed linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aclosed+linked%3Aissue) coincidirá con las solicitudes de extracción cerradas en el repositorio `desktop/desktop` que se enlazaron a un informe de problemas que se pudo haber cerrado con una solicitud de extracción. | +| `-linked:pr` | [**repo:desktop/desktop is:open -linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Apr) coincidirá con informes de problemas abiertos en el repositorio `desktop/desktop` que no estén enlazados a una solicitud de extracción por una referencia cerrada. | +| `-linked:issue` | [**repo:desktop/desktop is:open -linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Aissue) Coincidirá con las solicitudes de extracción abiertas en el repositorio `desktop/desktop` que no se hayan enlazado con un informe de problemas que la solicitud de extracción haya creado. +{% endif %} + +## Buscar por etiqueta + +Puedes acotar tus resultados por etiquetas, utilizando el calificador `label` (etiqueta). Ya que las propuestas pueden tener múltiples etiquetas, puedes enumerar un calificador separado para cada propuesta. + +| Qualifier | Ejemplo | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| label:LABEL | [**label:"help wanted" language:ruby**](https://github.com/search?utf8=%E2%9C%93&q=label%3A%22help+wanted%22+language%3Aruby&type=Issues) encuentra propuestas con la etiqueta "help wanted" (se necesita ayuda) que están en los repositorios Ruby. | +| | [**broken in:body -label:bug label:priority**](https://github.com/search?q=broken+in%3Abody+-label%3Abug+label%3Apriority&type=Issues) encuentra propuestas con la palabra "broken" en el cuerpo, que no tienen la etiqueta "bug" (error), pero *que tienen* la etiqueta "priority" (prioridad). | +| | [**label:bug label:resolved**](https://github.com/search?l=&q=label%3Abug+label%3Aresolved&type=Issues) encuentra propuestas con las etiquetas "bug" "resolved".{% ifversion fpt or ghes > 3.2 or ghae-next %} +| | [**label:bug,resolved**](https://github.com/search?q=label%3Abug%2Cresolved&type=Issues) encuentra propuestas con la etiqueta "bug" o "resolved".{% endif %} + +## Buscar por hito + +El calificador `milestone` (hito) encuentra propuestas o solicitudes de extracción que son parte de un [hito](/articles/about-milestones) dentro de un repositorio. + +| Qualifier | Ejemplo | +| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| milestone:MILESTONE | [**milestone:"overhaul"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22overhaul%22&type=Issues) encuentra propuestas que son un hito con el nombre de "overhaul." | +| | [**milestone:"bug fix"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22bug+fix%22&type=Issues) encuentra propuestas que están en un hito con el nombre de "bug fix." | + +## Buscar por tablero de proyecto + +Puedes utilizar el calificador `project` (proyecto) para encontrar propuestas que están asociadas con un [tablero de proyecto](/articles/about-project-boards/) específico en un repositorio u organización. Debes buscar tableros de proyecto por el número del tablero de proyecto. Puedes encontrar el número del tablero de proyecto al final de la URL de cada tablero de proyecto. + +| Qualifier | Ejemplo | +| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | +| project:PROJECT_BOARD | **project:github/57** encuentra propuestas propiedad de GitHub que están asociadas con el tablero de proyecto de la organización número 57. | +| project:REPOSITORY/PROJECT_BOARD | **project:github/linguist/1** encuentra propuestas que están asociadas con el tablero de proyecto 1 en el repositorio lingüístico de @github. | + +## Buscar por estado de confirmación + +Puedes filtrar solicitudes de extracción en base al estado de las confirmaciones. Esto es particularmente útil si estás utilizando [el estado API](/rest/reference/repos#statuses) o un servicio CI. + +| Qualifier | Ejemplo | +| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `status:pending` | [**language:go status:pending**](https://github.com/search?utf8=%E2%9C%93&q=language%3Ago+status%3Apending) encuentra solicitudes de extracción abiertas en repositorios Go donde el estado es pendiente. | +| `status:success` | [**is:open status:success finally in:body**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aopen+status%3Asuccess+finally+in%3Abody&type=Issues) encuentra solicitudes de extracción abiertas con la palabra "finally" en el cuerpo con un estado exitoso. | +| `status:failure` | [**created:2015-05-01..2015-05-30 status:failure**](https://github.com/search?utf8=%E2%9C%93&q=created%3A2015-05-01..2015-05-30+status%3Afailure&type=Issues) encuentra solicitudes de extracción abiertas en mayo de 2015 con un estado falló. | + +## Buscar por SHA de confirmación + +Si sabes el hash SHA específico de una confirmación, puedes utilizarlo para buscar solicitudes de extracción que contienen ese SHA. La sintaxis SHA debe ser por lo menos de siete caracteres. + +| Qualifier | Ejemplo | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| SHA | [**e1109ab**](https://github.com/search?q=e1109ab&type=Issues) encuentra solicitudes de extracción con una confirmación SHA que comience con `e1109ab`. | +| | [**0eff326d6213c is:merged**](https://github.com/search?q=0eff326d+is%3Amerged&type=Issues) encuentra solicitudes de extracción fusionadas con una confirmación SHA que comience con `0eff326d6213c`. | + +## Buscar por nombre de la rama + +Puedes filtrar solicitudes de extracción en base a la rama de la que provienen (la rama "head" [de encabezado]) o la rama en la que están fusionadas (en la rama "base" [base]). + +| Qualifier | Ejemplo | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| head:HEAD_BRANCH | [**head:change is:closed is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=head%3Achange+is%3Aclosed+is%3Aunmerged) encuentra solicitudes de extracción abiertas desde los nombres de las ramas que comienzan con la palabra "change" que están cerradas. | +| base:BASE_BRANCH | [**base:gh-pages**](https://github.com/search?utf8=%E2%9C%93&q=base%3Agh-pages) encuentra solicitudes de extracción que se están fusionando dentro de la rama `gh-pages`. | + +## Buscar por lenguaje + +Con el calificador `language` (lenguaje) puedes buscar propuestas y solicitudes de extracción dentro de repositorios que están escritos en un determinado lenguaje. + +| Qualifier | Ejemplo | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| language:LANGUAGE | [**language:ruby state:open**](https://github.com/search?q=language%3Aruby+state%3Aopen&type=Issues) encuentra propuestas abiertas que están en los repositorios Ruby. | + +## Buscar por cantidad de comentarios + +Puedes utilizar el calificador `comments` (comentarios) junto con los calificadores [mayor que, menor que y rango ](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax) para buscar por cantidad de comentarios. + +| Qualifier | Ejemplo | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| comments:n | [**state:closed comments:>100**](https://github.com/search?q=state%3Aclosed+comments%3A%3E100&type=Issues) encuentra propuestas cerradas con más de 100 comentarios. | +| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Issues) encuentra propuestas con comentarios que van desde 500 a 1000. | + +## Buscar por cantidad de interacciones + +Puedes filtrar propuestas y solicitudes de extracción en base a la cantidad de interacciones, utilizando el calificador `interactions` (interacciones) y junto con [los calificadores mayor que, menor que y rango](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). El conteo de interacciones es la cantidad de reacciones y comentarios sobre una propuesta o solicitud de extracción. + +| Qualifier | Ejemplo | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| interactions:n | [** interactions:>2000**](https://github.com/search?q=interactions%3A%3E2000) encuentra solicitudes de extracción o propuestas con más de 2000 interacciones. | +| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) encuentra solicitudes de extracción o propuestas con un rango de interacciones entre 500 a 1000. | + +## Buscar por cantidad de reacciones + +Puedes filtrar propuestas y solicitudes de extracción en base a la cantidad de reacciones, utilizando el calificador `reactions` (reacciones) y junto con [los calificadores mayor que, menor que y rango](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). + +| Qualifier | Ejemplo | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | +| reactions:n | [** reactions:>1000**](https://github.com/search?q=reactions%3A%3E1000&type=Issues) encuentra propuestas con más de 1000 reacciones. | +| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) encuentra propuestas con reacciones con un rango de entre 500 a 1000. | + +## Buscar solicitudes de extracción en borrador +Puedes filtrar por solicitudes de extracción en borrador. Para obtener más información, consulta "[Acerca de las solicitudes de extracción](/articles/about-pull-requests#draft-pull-requests)." + +| Calificador| Ejemplo | ------------- | -------------{% ifversion fpt or ghes or ghae %} | `draft:true` | [**draft:true**](https://github.com/search?q=draft%3Atrue) empata con los borradores de solicitudes de cambio. | `draft:false` | [**draft:false**](https://github.com/search?q=draft%3Afalse) coincidirá con las solicitudes de extracción listas para revisión.{% else %} | `is:draft` | [**is:draft**](https://github.com/search?q=is%3Adraft) coincidirá con las solicitudes de extracción en estado de borrador.{% endif %} + +## Buscar por estado de revisión de solicitud de extracción y revisor + +Puedes filtrar las solicitudes de extracción en función de su [estado de revisión](/articles/about-pull-request-reviews) (_ninguno_, _requerido_, _aprobado_ o _cambios solicitados_), por revisor y por revisor solicitado. + +| Qualifier | Ejemplo | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `review:none` | [**type:pr review:none**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Anone&type=Issues) encuentra solicitudes de extracción que no han sido revisadas. | +| `review:required` | [**type:pr review:required**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Arequired&type=Issues) encuentra solicitudes de extracción que requieren una revisión antes de poder ser fusionadas. | +| `review:approved` | [**type:pr review:approved**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Aapproved&type=Issues) encuentra solicitudes de extracción que un revisor ha aprobado. | +| `review:changes_requested` | [**type:pr review:changes_requested**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Achanges_requested&type=Issues) encuentra solicitudes de extracción en las cuales un revisor ha solicitado cambios. | +| reviewed-by:USERNAME | [**type:pr reviewed-by:gjtorikian**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+reviewed-by%3Agjtorikian&type=Issues) encuentra revisión de solicitudes de extracción por una persona particular. | +| review-requested:USERNAME | [**type:pr review-requested:benbalter**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review-requested%3Abenbalter&type=Issues) encuentra solicitudes de extracción donde una persona específica solicitó una revisión. Los revisores solicitados ya no se enumeran en los resultados de búsqueda después de que han revisado una solicitud de extracción. Si la persona que se solicitó está en un equipo al cual se le solicitó una revisión, entonces revisa que las solicitudes para dicho equipo también aparezcan en los resultados de búsqueda.{% ifversion fpt or ghae or ghes > 3.2 %} +| user-review-requested:@me | [**type:pr user-review-requested:@me**](https://github.com/search?q=is%3Apr+user-review-requested%3A%40me+) coincide con las solicitudes de cambio que se te solicitaron revisar directamente.{% 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) encuentra solicitudes de extracción que tienen solicitudes de revisión de un equipo `atom/design`. Los revisores solicitados ya no se enumeran en los resultados de búsqueda después de que han revisado una solicitud de extracción. | + +## Buscar por cuándo una propuesta o solicitud de extracción fue creada o actualizada por última vez + +Puedes filtrar propuestas en base al momento de creación o al momento de su última actualización. Para la creación de una propuesta, puedes usar el calificador `created` (creado); para encontrar cuándo se actualizó por última vez un repositorio, querrás utilizar el calificador `pushed` (subido). + +Ambos toman una fecha como su parámetro. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifier | Ejemplo | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| created:YYYY-MM-DD | [**language:c# created:<2011-01-01 state:open**](https://github.com/search?q=language%3Ac%23+created%3A%3C2011-01-01+state%3Aopen&type=Issues) encuentra las propuestas que se crearon antes de 2011 en los repositorios que están escritos en C#. | +| updated:YYYY-MM-DD | [**weird in:body updated:>=2013-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2013-02-01&type=Issues) encuentra las propuestas con la palabra "weird" en el cuerpo, las cuales se actualizaron después de febrero del 2013. | + +## Buscar por cuándo una propuesta o solicitud de extracción fue cerrada + +Puedes filtrar propuestas y solicitudes de extracción en base a su momento de cierre, utilizando el calificador `closed` (cerrada). + +Este calificador toma una fecha como su parámetro. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifier | Ejemplo | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| closed:YYYY-MM-DD | [**language:swift closed:>2014-06-11**](https://github.com/search?q=language%3Aswift+closed%3A%3E2014-06-11&type=Issues) encuentra las propuestas y solicitudes de cambios en Swift que se cerraron después del 11 de junio de 2014. | +| | [**data in:body closed:<2012-10-01**](https://github.com/search?utf8=%E2%9C%93&q=data+in%3Abody+closed%3A%3C2012-10-01+&type=Issues) encuentra las propuestas y solicitudes de cambio con la palabra "data" en el cuerpo, las cuales se cerrron antes de octubre de 2012. | + +## Buscar por cuándo una solicitud de extracción fue fusionada + +Puedes filtrar solicitudes de extracción en base a cuándo fueron fusionadas, utilizando el calificador `merged` (fusionada). + +Este calificador toma una fecha como su parámetro. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifier | Ejemplo | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| merged:YYYY-MM-DD | [**language:javascript merged:<2011-01-01**](https://github.com/search?q=language%3Ajavascript+merged%3A%3C2011-01-01+&type=Issues) encuntra las solicitudes de cambio en los repositorios de JavaScript que se fusionaron antes de 2011. | +| | [**fast in:title language:ruby merged:>=2014-05-01**](https://github.com/search?q=fast+in%3Atitle+language%3Aruby+merged%3A%3E%3D2014-05-01+&type=Issues) encuentra las solicitudes de cambiosen Ruby con la palabra "fast" en el título, los cuales se hayan fusionado después de mayo de 2014. | + +## Buscar en base a si una solicitud de extracción se fusionó o se desagrupó + +Puedes filtrar solicitudes de extracción en base a cuándo fueron fusionadas o desagrupadas, utilizando el calificador `is`. + +| Qualifier | Ejemplo | +| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `is:merged` | [**bugfix is:pr is:merged**](https://github.com/search?utf8=%E2%9C%93&q=bugfix+is%3Apr+is%3Amerged&type=) encuentra solicitudes de extracción fusionadas con la palabra "bugfix." | +| `is:unmerged` | [**error is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=error+is%3Aunmerged&type=) encuentra propuestas y solicitudes de extracción cerradas con la palabra "error." | + +## Buscar en base a si un repositorio está archivado + +El calificador `archived` (archivado) filtra tus resultados en base a si una propuesta o una solicitud de extracción está en un repositorio archivado. + +| Qualifier | Ejemplo | +| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `archived:true` | [**archived:true GNOME**](https://github.com/search?q=archived%3Atrue+GNOME&type=) encuentra propuestas y solicitudes de extracción que contienen la palabra "GNOME" en repositorios archivados a los que tienes acceso. | +| `archived:false` | [**archived:false GNOME**](https://github.com/search?q=archived%3Afalse+GNOME&type=) encuentra propuestas y solicitudes de extracción que contienen la palabra "GNOME" en repositorios no archivados a los que tienes acceso. | + +## Buscar en base a si una conversación está bloqueada + +Puedes buscar por una propuesta o solicitud de extracción que tiene una conversación utilizando el calificador `is`. Para obtener más información, consulta "[Bloquear conversaciones](/communities/moderating-comments-and-conversations/locking-conversations)." + +| Qualifier | Ejemplo | +| ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `is:locked` | [**code of conduct is:locked is:issue archived:false**](https://github.com/search?q=code+of+conduct+is%3Alocked+is%3Aissue+archived%3Afalse) encuentra propuestas o solicitudes de extracción con las palabras "code of conduct" que tienen una conversación bloqueada en un repositorio que no se ha archivado. | +| `is:unlocked` | [**code of conduct is:unlocked is:issue archived:false**](https://github.com/search?q=code+of+conduct+is%3Aunlocked+archived%3Afalse) encuentra propuestas o solicitudes de extracción con las palabras "code of conduct" que tienen una conversación desbloqueada en un repositorio que no se ha archivado. | + +## Buscar por metadatos faltantes + +Puedes acotar tu búsqueda a propuestas y solicitudes de extracción que tienen determinados metadatos faltantes, utilizando el calificador `no`. Esos metadatos incluyen: + +* Etiquetas +* Hitos +* Asignatarios +* Proyectos + +| Qualifier | Ejemplo | +| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `no:label` | [**priority no:label**](https://github.com/search?q=priority+no%3Alabel&type=Issues) encuentra propuestas y solicitudes de extracción con la palabra "priority" que tampoco tienen ninguna etiqueta. | +| `no:milestone` | [**sprint no:milestone type:issue**](https://github.com/search?q=sprint+no%3Amilestone+type%3Aissue&type=Issues) encuentra propuestas no asociadas con un hito que contienen la palabra "sprint." | +| `no:assignee` | [**important no:assignee language:java type:issue**](https://github.com/search?q=important+no%3Aassignee+language%3Ajava+type%3Aissue&type=Issues) encuentra propuestas no asociadas con un asignatario, que contienen la palabra "important," y en repositorios Java. | +| `no:project` | [**build no:project**](https://github.com/search?utf8=%E2%9C%93&q=build+no%3Aproject&type=Issues) encuentra propuestas no asociadas con un tablero de proyecto, que contienen la palabra "build." | + +## Leer más + +- "[Clasificar los resultados de la búsqueda](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" diff --git a/translations/es-ES/content/search-github/searching-on-github/searching-topics.md b/translations/es-ES/content/search-github/searching-on-github/searching-topics.md new file mode 100644 index 0000000000..99733ed56e --- /dev/null +++ b/translations/es-ES/content/search-github/searching-on-github/searching-topics.md @@ -0,0 +1,55 @@ +--- +title: Buscar temas +intro: 'Puedes buscar temas asociados con los repositorios en {% data variables.product.product_name %}.' +redirect_from: + - /articles/searching-topics + - /github/searching-for-information-on-github/searching-topics + - /github/searching-for-information-on-github/searching-on-github/searching-topics +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +## Buscar temas en {% data variables.product.product_name %} + +Puedes buscar temas en {% data variables.product.product_name %}, explorar temas relacionados y ver cuántos repositorios están asociados con un tema determinado. + +1. Navega hasta https://github.com/search. +2. Escribe una palabra clave del tema. ![campo buscar](/assets/images/help/search/search-field.png) +3. En la barra lateral de la izquierda, para acotar tu búsqueda por temas, haz clic en **Topics (Temas)**. +{% ifversion fpt %} + ![La página de resultados de búsqueda de repositorios de Jekyll con la opción de menú lateral de temas resaltada](/assets/images/help/search/topic-left-side-navigation-dotcom.png){% else %} +![Jekyll repository search results page on dotcom with topics side-menu option highlighted](/assets/images/help/search/topic-left-side-navigation.png){% endif %} + +## Acotar tu búsqueda con calificadores de búsqueda + +Si deseas explorar repositorios sobre un determinado tema, encontrar proyectos en los que contribuir, o conocer qué temas son más populares en {% data variables.product.product_name %}, puedes buscar temas con los calificadores de búsqueda `is:featured`, `is:curated`, `repositories:n` y `created:YYYY-MM-DD`. + +El calificador de búsqueda `is:featured` acotará los resultados de búsqueda a los temas con la mayor cantidad de repositorios en {% data variables.product.product_name %}. Estos temas también se muestran en https://github.com/topics/. + +El calificador de búsqueda de `is:curated` acotará los resultados de búsqueda en los temas a los que los miembros de la comunidad han agregado información adicional. Para obtener más información, consulta la sección de [explorar repositorios](https://github.com/github/explore). + +Puedes filtrar temas en base a cuándo se crearon utilizando el parámetro de fecha y `created:` o en base a cuántos repositorios están asociados con este tema utilizando `repositories:n`. Estos dos calificadores pueden utilizar los calificadores de rango mayor que y menor que [](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). + +{% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifier | Ejemplo | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `is:curated` | [**is:curated javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+is%3Acurated&type=Topics) encuentra temas que están conservados y contienen la palabra "javascript." | +| `is:featured` | [**is:featured javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+is%3Afeatured&type=Topics) encuentra temas que se muestran en https://github.com/topics/ y contienen la palabra "javascript." | +| `is:not-curated` | [**is:not-curated javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+is%3Anot-curated&type=Topics) encuentra temas que no tienen información extra, como una descripción o un logo, y que contienen la palabra "javascript." | +| `is:not-featured` | [**is:not-featured javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+is%3Anot-featured&type=Topics) encuentra temas que no se muestran en https://github.com/topics/ y contienen la palabra "javascript." | +| `repositories:n` | [**repositories:>5000**](https://github.com/search?q=repositories%3A%3E5000) encuentra temas que tienen más de 5000 repositorios. | +| created:YYYY-MM-DD | [**Serverless created:>2019-01-01**](https://github.com/search?q=Serverless+created%3A%3E2019-01-01&type=Topics) encuentra temas con la palabra "serverless" que fueron creados después de 2018. | + +## Buscar repositorios por tema + +Puedes utilizar el calificador `topic:` (tema) para encontrar cada repositorio conectado a un tema particular. Para obtener más información, consulta "[Buscar repositorios](/search-github/searching-on-github/searching-for-repositories/#search-by-topic)." + +## Leer más +- "[Clasificar tu repositorio con temas](/articles/classifying-your-repository-with-topics)" diff --git a/translations/es-ES/content/search-github/searching-on-github/searching-users.md b/translations/es-ES/content/search-github/searching-on-github/searching-users.md new file mode 100644 index 0000000000..062ce4958c --- /dev/null +++ b/translations/es-ES/content/search-github/searching-on-github/searching-users.md @@ -0,0 +1,106 @@ +--- +title: Buscar usuarios +intro: 'Puedes buscar usuarios en {% data variables.product.product_name %} y acotar los resultados utilizando estos calificadores de búsqueda de usuarios en cualquier combinación.' +redirect_from: + - /articles/searching-users + - /github/searching-for-information-on-github/searching-users + - /github/searching-for-information-on-github/searching-on-github/searching-users +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +Puedes buscar usuarios globalmente a través de todos los {% data variables.product.product_name %}. Para obtener más información, consulta "[Acerca de buscar en {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)". + +{% data reusables.search.syntax_tips %} + +## Buscar únicamente por usuarios u organizaciones + +Por defecto, buscar usuarios mostrará personas y organizaciones. Sin embargo, puedes utilizar el calificador `type` (tipo) para restringir los resultados de la búsqueda a cuentas personales o de organizaciones únicamente. + +| Qualifier | Ejemplo | +| ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `type:user` | [**mike in:name created:<2011-01-01 type:user**](https://github.com/search?q=mike+in:name+created%3A%3C2011-01-01+type%3Auser&type=Users) encuentra cuentas personales con el nombre "mike" que fueron creadas antes de 2011. | +| `type:org` | [**data in:email type:org**](https://github.com/search?q=data+in%3Aemail+type%3Aorg&type=Users) encuentra organizaciones con la palabra "data" en su correo electrónico. | + +## Buscar por nombre de cuenta, nombre completo o correo electrónico público + +Puedes filtrar tu búsqueda al nombre de la cuenta de usuario personal o de una organización con los calificadores `user` u `org`. + +Con el calificador `in` puedes restringir tu búsqueda al nombre de usuario (`login`), el nombre completo, el correo electrónico público, o cualquier combinación de ellos. Cuando omites este calificador, únicamente se buscan el nombre de usuario y la dirección de correo electrónico. Por razones de privacidad, no puedes buscar por nombre de dominio de correo electrónico. + +| Qualifier | Ejemplo | +| ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `user:name` | [**user:octocat**](https://github.com/search?q=user%3Aoctocat&type=Users) encuentra el usuario con el nombre de usuario "octocat". | +| `org:name` | [**org:electron type:users**](https://github.com/search?q=org%3Aelectron+type%3Ausers&type=Users) encuentra el nombre de la cuenta de la organización Electron. | +| `in:login` | [**kenya in:login**](https://github.com/search?q=kenya+in%3Alogin&type=Users) encuentra los usuarios con la palabra "kenya" en su nombre de usuario. | +| `in:name` | [**bolton in:name**](https://github.com/search?q=bolton+in%3Afullname&type=Users) encuentra a los usuarios cuyo nombre real contiene la palabra "bolton." | +| `fullname:firstname lastname` | [**fullname:nat friedman**](https://github.com/search?q=fullname%3Anat+friedman&type=Users) encuentra un usuario con el nombre completo "Nat Friedman." Nota: este calificador de búsqueda es sensible a los espacios. | +| `in:email` | [**data in:email**](https://github.com/search?q=data+in%3Aemail&type=Users&utf8=%E2%9C%93) encuentra a los usuarios con la palabra "data" en su correo electrónico. | + +## Buscar por cantidad de repositorios que posee el usuario + +Puedes filtrar usuarios en base a la cantidad de repositorios que poseen, utilizando el calificador `repos` y [los calificadores mayor que, menor que y rango](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). + +| Qualifier | Ejemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| repos:n | [**repos:>9000**](https://github.com/search?q=repos%3A%3E%3D9000&type=Users) coincidirá con los usuarios cuyo número de repositorios sea mayor a 9.000. | +| | [**bert repos:10..30**](https://github.com/search?q=bert+repos%3A10..30&type=Users) encuentra usuarios con la palabra "bert" en su nombre de usuario o nombre real que poseen de 10 a 30 repositorios. | + +## Buscar por ubicación + +Puedes buscar usuarios por la ubicación indicada en su perfil. + +| Qualifier | Ejemplo | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| location:LOCATION | [**repos:1 location:iceland**](https://github.com/search?q=repos%3A1+location%3Aiceland&type=Users) encuentra usuarios con exactamente un repositorio que viven en Islandia. | + +## Buscar por lenguaje del repositorio + +Utilizando el calificador `language` (lenguaje) puedes buscar usuarios en base al lenguaje de los repositorios que poseen. + +| Qualifier | Ejemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| language:LANGUAGE | [**language:javascript location:russia**](https://github.com/search?q=language%3Ajavascript+location%3Arussia&type=Users) encuentra usuarios en Rusia con una mayoría de sus repositorios escritos en JavaScript. | +| | [**jenny language:javascript in:fullname**](https://github.com/search?q=jenny+language%3Ajavascript+in%3Afullname&type=Users) encuentra usuarios con repositorios en JavaScript cuyos nombres completos contienen la palabra "jenny." | + +## Buscar por cuándo fue creada la cuenta del usuario + +Puedes filtrar usuarios en base a cuándo se unieron a {% data variables.product.product_name %} con el calificador `created` (creada). Este calificador toma una fecha como su parámetro. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifier | Ejemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| created:YYYY-MM-DD | [**created:<2011-01-01**](https://github.com/search?q=created%3A%3C2011-01-01&type=Users) coincidirá con los usuarios que se hayan unido antes de 2011. | +| | [**created:>=2013-05-11**](https://github.com/search?q=created%3A%3E%3D2013-05-11&type=Users) coincidirá con los usuarios que se hayan unido en o después del 11 de mayo. | +| | [**created:2013-03-06 location:london**](https://github.com/search?q=created%3A2013-03-06+location%3Alondon&type=Users) encuentra usuarios que se unieron el 6 de marzo de 2013, y que muestran su ubicación como Londres. | +| | [**created:2010-01-01..2011-01-01 john in:login**](https://github.com/search?q=created%3A2010-01-01..2011-01-01+john+in%3Ausername&type=Users) encuentra usuarios que se unieron entre 2010 y 2011 con la palabra "john" en su nombre de usuario. | + +## Buscar por cantidad de seguidores + +Puedes filtrar usuarios en base a la cantidad de seguidores que tienen, utilizando el calificador `followers` (seguidores) con los calificadores [mayor que, menor que y rango](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). + +| Qualifier | Ejemplo | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| followers:n | [**followers:>=1000**](https://github.com/search?q=followers%3A%3E%3D1000&type=Users) coincidirá con los usuarios con 1,000 o más seguidores. | +| | [**sparkle followers:1..10**](https://github.com/search?q=sparkle+followers%3A1..10&type=Users) encuentra usuarios entre 1 y 10 seguidores, con la palabra "sparkle" en su nombre. | + +{% ifversion fpt %} + +## Búsqueda basada en la capacidad de patrocinar + +Puedes buscar usuarios y organizaciones que puedan patrocinarse en {% data variables.product.prodname_sponsors %} con el calificativo `is:sponsorable`. Para obtener más información, consulta "[Acerca de {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)". + +| Qualifier | Ejemplo | +| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `is:sponsorable` | [**is:sponsorable**](https://github.com/search?q=is%3Asponsorable&type=Users) coincide con los usuarios y organizaciones que tienen un perfil de {% data variables.product.prodname_sponsors %}. | + +{% endif %} + +## Leer más + +- "[Clasificar los resultados de la búsqueda](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" diff --git a/translations/es-ES/content/search-github/searching-on-github/searching-wikis.md b/translations/es-ES/content/search-github/searching-on-github/searching-wikis.md new file mode 100644 index 0000000000..4781f1c295 --- /dev/null +++ b/translations/es-ES/content/search-github/searching-on-github/searching-wikis.md @@ -0,0 +1,51 @@ +--- +title: Buscar wikis +intro: 'Puedes buscar wikis en {% data variables.product.product_name %} y acotar los resultados utilizando estos calificadores de búsqueda de wiki en cualquier combinación.' +redirect_from: + - /articles/searching-wikis + - /github/searching-for-information-on-github/searching-wikis + - /github/searching-for-information-on-github/searching-on-github/searching-wikis +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +Puedes buscar wikis globalmente a través de todos los {% data variables.product.product_name %}, o buscar wikis dentro de un repositorio u organización particular. Para obtener más información, consulta "[Acerca de buscar en {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)". + +{% data reusables.search.syntax_tips %} + +## Buscar dentro de los repositorios de un usuario u organización + +Para encontrar páginas wiki de todos los repositorios propiedad de un determinado usuario u organización, utiliza el calificador `user` u `org`. Para buscar páginas wiki en un repositorio específico, utiliza el calificador `repo`. + +| Qualifier | Ejemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| user:USERNAME | [**user:defunkt**](https://github.com/search?q=user%3Adefunkt&type=Wikis) encuentra páginas wiki de los repositorios propiedad de @defunkt. | +| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=Wikis&utf8=%E2%9C%93) encuentra wikis en repositorios propiedad de la organización de GitHub. | +| repo:USERNAME/REPOSITORY | [**repo:defunkt/gibberish**](https://github.com/search?q=user%3Adefunkt&type=Wikis) encuentra páginas wiki del repositorio "gibberish" de @defunkt. | + +## Buscar dentro del título o el texto del cuerpo de una página wiki + +El calificador `in` acota la búsqueda al título o al texto del cuerpo de la página wiki. Sin el calificador, se busca tanto en el título como en el texto del cuerpo. + +| Qualifier | Ejemplo | +| ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `in:title` | [**usage in:title**](https://github.com/search?q=usage+in%3Atitle&type=Wikis) encuentra títulos de página wiki con la palabra "usage." | +| `in:body` | [**installation in:body**](https://github.com/search?q=installation+in%3Abody&type=Wikis) encuentra páginas wiki con la palabra "installation" en el texto de su cuerpo principal. | + +## Buscar por la última fecha de actualización + +El calificador `updated` (actualizada) empareja páginas wiki que fueron actualizadas por última vez dentro de un rango específico de fechas. + +{% data reusables.search.date_gt_lt %} + +| Qualifier | Ejemplo | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| updated:YYYY-MM-DD | [**usage updated:>2016-01-01**](https://github.com/search?q=usage+updated%3A>2016-01-01&type=Wikis) coincidirá con las páginas de wiki con la palabra "uso" que se actualizaron por última vez después del 2016-01-01. | + +## Leer más + +- "[Clasificar los resultados de la búsqueda](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" 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 7fd567d0f6..c69badebd3 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 @@ -47,6 +47,6 @@ Las donaciones entre los desarrolladores patrocinados no se empatarán. ## Leer más - "[Patrocinar a contribuyentes de código abierto](/sponsors/sponsoring-open-source-contributors)" - "[Recibir patrocinios a través de {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors)". -- "[Searching users and organizations based on ability to sponsor](/github/searching-for-information-on-github/searching-on-github/searching-users#search-based-on-ability-to-sponsor)" -- "[Searching repositories based on ability to sponsor](/github/searching-for-information-on-github/searching-on-github/searching-for-repositories#search-based-on-ability-to-sponsor)" +- "[buscar usuarios y organizaciones con base en su capacidad de patrocinar](/github/searching-for-information-on-github/searching-on-github/searching-users#search-based-on-ability-to-sponsor)" +- "[Buscar repositorios con base en la capacidad de patrocinar](/github/searching-for-information-on-github/searching-on-github/searching-for-repositories#search-based-on-ability-to-sponsor)" - "[Preguntas frecuentes con el equipo {% data variables.product.prodname_sponsors %} ](https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/)" en {% data variables.product.prodname_blog %} diff --git a/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md index 39e6e3e9fe..f77be7ce43 100644 --- a/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md +++ b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md @@ -30,6 +30,7 @@ shortTitle: Administrar los niveles de pago 1. Opcionalmente, para editar un nivel de borrador, encuentra dicho nivel y haz clic en **Editar**. ![Botón de editar junto al nivel en borrador](/assets/images/help/sponsors/draft-tier-edit.png) {% data reusables.sponsors.click-add-tier %} {% data reusables.sponsors.tier-price-description %} +{% data reusables.sponsors.add-welcome-message %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} 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 c0f2a74ec4..1c7feed24d 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 @@ -51,6 +51,7 @@ Para unirte a {% data variables.product.prodname_sponsors %} como un colaborador {% data reusables.sponsors.navigate-to-sponsor-tiers-tab %} {% data reusables.sponsors.click-add-tier %} {% data reusables.sponsors.tier-price-description %} +{% data reusables.sponsors.add-welcome-message %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} {% data reusables.sponsors.add-more-tiers %} 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-user-account.md index 3549426182..90a0947e58 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-user-account.md @@ -50,6 +50,7 @@ Una vez que {% data variables.product.prodname_dotcom %} revise tu aplicación, {% data reusables.sponsors.navigate-to-sponsor-tiers-tab %} {% data reusables.sponsors.click-add-tier %} {% data reusables.sponsors.tier-price-description %} +{% data reusables.sponsors.add-welcome-message %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} {% data reusables.sponsors.add-more-tiers %} diff --git a/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/sponsors-for-companies.md b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/sponsors-for-companies.md index c6ddf99a7e..c8741d9216 100644 --- a/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/sponsors-for-companies.md +++ b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/sponsors-for-companies.md @@ -1,7 +1,7 @@ --- -title: Receiving payments from Sponsors for Companies -shortTitle: Sponsors for Companies -intro: 'To accept payments from the Sponsors for Companies service, you must accept some additional terms.' +title: Recibir pagos de Patrocinadores para Compañías +shortTitle: Patrocinadores para Compañías +intro: 'Para aceptar pagos del servicio de Patrocinadores para Compañías, debes aceptar algunos términos adicionales.' allowTitleToDifferFromFilename: true versions: fpt: '*' @@ -13,28 +13,28 @@ topics: {% data reusables.sponsors.beta-note-sponsors-for-companies %} -## About the Sponsors for Companies service +## Acerca del servicio de Patrocinadores para las Compañías -When you create a sponsors profile, you become eligible for sponsorship payments from individual users and organizations who are billed by credit card. In addition, {% data variables.product.company_short %} now offers a Sponsors for Companies service to enterprise customers who pay by invoice, including companies who use {% data variables.product.prodname_ghe_server %} or {% data variables.product.prodname_ghe_managed %}. +Cuando creas un perfil de patrocinadores, te haces elegible para recibir pagos de patrocinio de usuarios individuales y organizaciones a los que se les cobra por tarjeta de crédito. Adicionalmente, {% data variables.product.company_short %} ahora ofrece un servicio de Patrocinadores para Compañías para los clientes empresariales que pagan por factura, incluyendo las compañías que utilizan {% data variables.product.prodname_ghe_server %} o {% data variables.product.prodname_ghe_managed %}. - The funds you receive under the Sponsors for Companies service come directly from {% data variables.product.company_short %}, and your participation in this service is subject to separate terms: the "GitHub Maintainer Additional Terms for Optional Data Provision". If you wish to receive funds from {% data variables.product.company_short %} under the Sponsors for Companies service, you'll need to complete the agreement before receiving any of those funds. + Los fondos que recibes bajo el servicio de Patrocinadores para Compañías vienen directamente de {% data variables.product.company_short %} y tu participación en dicho servicio está sujeta a términos separados: los "Términos Adicionales de Mantenedor de GitHub para la Provisión de Datos Opcional". Si quieres recibir fondos de {% data variables.product.company_short %} bajo el servicio de Patrocinadores para Compañías, necesitas completar el acuerdo antes de poderlos recibir. -## About the additional terms +## Acerca de los términos adicionales -The "GitHub Maintainer Additional Terms for Optional Data Provision" agreement is available from your [{% data variables.product.prodname_sponsors %} dashboard](https://github.com/sponsors/accounts) (see steps below). Key points of the agreement include: +El acuerdo de "Términos Adicionales de Mantenedor de GitHub para Provisión de Datos Opcional" se encuentra disponible desde tu [ Tablero de {% data variables.product.prodname_sponsors %}](https://github.com/sponsors/accounts) (consulta los pasos a continuación). Los puntos clave del acuerdo incluyen: -* Due to the way the service is set up, you'll receive payment from {% data variables.product.company_short %}, not from another company. -* If taxes are required to be withheld on payment made through this program, {% data variables.product.company_short %} will deduct taxes from the amount owed and pay them to the appropriate taxing authority. -* We'll share some aggregated data on your project(s) or projects you contribute to with the companies that pay for access to this data on a {% data variables.product.company_short %} dashboard. These data fields are outlined in Section 5 of the agreement. -* Data will be aggregated and will not include any User Personal Information (as defined in {% data variables.product.company_short %}’s [Privacy Statement](/github/site-policy/github-privacy-statement)), or any information from private repositories. -* You, as a Maintainer, can terminate the agreement with 14 days notice by contacting us. +* Debido a la forma en la que se configura el servicio, recibirás el pago de {% data variables.product.company_short %}, no de otra compañía. +* Si se requiere retener impuestos sobre el pago que se haga mediante este programa, {% data variables.product.company_short %} los deducirá de la cantidad que se deba y los pagará a la autoridad fiscal adecuada. +* Compartiremos en un tablero de {% data variables.product.company_short %} los datos agregados sobre tus proyectos o sobre aquellos en los cuales contribuyas con las compañías que pagan por el acceso a estos datos. Estos campos de datos se detallan en la sección 5 del acuerdo. +* Los datos se agregarán y no incluirán Información Personal de Usuario (de acuerdo a como se define en la [Declaración de privacidad](/github/site-policy/github-privacy-statement) de {% data variables.product.company_short %}) ni cualquier información de los repositorios privados. +* Tú, como mantenedor, puedes finalizar el acuerdo si nos contactas con 14 días de antelación para notificarnos. -If you agree to the terms outlined in the "GitHub Maintainer Additional Terms for Optional Data Provision" agreement, you will receive a payment from {% data variables.product.company_short %} each time a company purchases access to the service. The company purchases access to the dashboard from {% data variables.product.company_short %} for a limited amount of time (for example, one month or one year), and {% data variables.product.company_short %} purchases a license to your data to populate the dashboard. Your financial relationship is with {% data variables.product.company_short %}, not the company taking part in the service. +Si estás de acuerdo con los términos que se detallan en el acuerdo de "Términos Adicionales de Mantenedor de GitHub para la Provisión de Datos Opcionales", recibirás un pago de {% data variables.product.company_short %} cada que una compañía compre el acceso a este servicio. La compañía compra el acceso al tablero desde {% data variables.product.company_short %} por una cantidad limitada de tiempo (por ejemplo, por un mes o un año) y {% data variables.product.company_short %} compra la licencia para tus datos o llena el tablero. Tu relación financiera es con{% data variables.product.company_short %} y no con la compañía que participa en el servicio. -## Accepting the additional terms +## Aceptar los térmnos adicionales -You can view and accept the "GitHub Maintainer Additional Terms for Optional Data Provision" agreement from your [{% data variables.product.prodname_sponsors %} dashboard](https://github.com/sponsors/accounts). For information about joining the Sponsors for Companies service, see "[Paying for GitHub Sponsors by invoice](/sponsors/sponsoring-open-source-contributors/paying-for-github-sponsors-by-invoice)." +Puedes ver y aceptar el acuerdo de "Términos Adicionales de Mantenedor de GitHub para la Provisión de Datos Opcionales" desde tu [Tablero de {% data variables.product.prodname_sponsors %}](https://github.com/sponsors/accounts). Para obtener información sobre cómo unirte al servicio de Patrocinadores para Compañías, consulta la sección "[Pagar por GitHub Sponsors por factura](/sponsors/sponsoring-open-source-contributors/paying-for-github-sponsors-by-invoice)". {% data reusables.sponsors.navigate-to-sponsors-dashboard %} -3. On the "Overview" tab, under "Optional steps", click **GitHub Maintainer Additional Terms for Optional Data Provision** to display the agreement. -4. When you have read the agreement, click **Accept** to accept the terms and join the Sponsors for Companies service. Alternatively, click the {% octicon "x" aria-label="The x octicon" %} in the top right corner of the dialog to close the agreement without accepting. +3. En la pestaña de "Resumen", debajo de "Pasos opcionales", haz clic en **Términos Adicionales de Mantenedor de GitHub para la Provisión de Datos Opcionales** para mostrar el acuerdo. +4. Cuando hayas leído el acuerdo, haz clic en **Aceptar** para aceptar los términos y unirte al servicio de Patrocinadores para Compañías. Como alternativa, haz clic en el {% octicon "x" aria-label="The x octicon" %} en la esquina superior derecha del diálogo para cerrar el acuerdo sin aceptarlo. 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 404b3e12f3..b6f7e0e00c 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 @@ -13,49 +13,63 @@ topics: shortTitle: Información fiscal --- -## W-9/W-8 tax forms +## Formatos de impuestos W-9/W-8 -By law, {% data variables.product.prodname_dotcom %} is required by the U.S. Internal Revenue Service (IRS) to collect tax information from all U.S. and non-U.S. maintainers. These forms are held by {% data variables.product.prodname_dotcom %} and are not required to be submitted to the IRS. +Por ley, el Servicio de Impuestos Internos de los EE.UU. requiere que {% data variables.product.prodname_dotcom %} recopile información sobre los impuestos de todos los mantenedores tanto dentro como fuera de los EE.UU. {% data variables.product.prodname_dotcom %} retiene estos formatos y no se necesitan enviar al IRS. ### W-9 (U.S.) -The information from W-9 tax forms helps {% data variables.product.prodname_dotcom %} use the correct Taxpayer Identification Number (TIN) to report income paid to you to the IRS in a 1099 form. +La información del formato W-9 ayuda a que {% data variables.product.prodname_dotcom %} utilice el Número de Identificación de Contribuyente (TIN, por sus siglas en inglés) correcto para reportar al IRS los ingresos que se te pagan en un formato 1099. -If you are a taxpayer in the United States, you must submit a [W-9](https://www.irs.gov/forms-pubs/about-form-w-9) before you can publish your {% data variables.product.prodname_sponsors %} profile. +Si eres un contribuyente en los Estados Unidos, debes emitir un formato ["W-9](https://www.irs.gov/forms-pubs/about-form-w-9) antes de poder publicar tu perfil de {% data variables.product.prodname_sponsors %}. -### W-8 BEN/W-8 BEN-E (non-U.S.) +### W-8 BEN/W-8 BEN-E (Fuera de los EE.UU.) -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. +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. -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. Para obtener más información, consulta las secciones "[Configurar {% data variables.product.prodname_sponsors %} para tu cuenta de usuario](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-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 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 de usuario](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-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. -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. +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. -### Tax identification numbers +### Números de identificación de impuestos -The W-8 BEN and W-8 BEN-E tax forms ask for a "U.S. taxpayer identification number (SSN or ITIN)" or "Foreign tax identifying number". +Los formatos de impuestos W-8 BEN y W-8 BEN-E requieren un "número de identificación de contribuyente (SSN o ITIN) de los EE.UU." o de un "Número de identificación de contribuyente extranjero". -If you are not a U.S. citizen or other U.S. person, including a resident alien individual, then you will usually need to provide the "Foreign tax identifying number". This is a tax identification number that your country of residence has issued you. +Si no eres ciudadano de los EE.UU. o cualquier otro tipo de persona que resida en los EE.UU., incluyendo a los extranjeros residentes individuales, entonces lo común es que necesites proporcionar el "Número de identificación de contribuyente extranjero". Este es un número de identificación de contribuyente que tu país de residencia te debe emitir. + +Si tu país de residencia o tu país de facturación es India, entonces puedes utilizar tu Número de Cuenta Permanente (PAN) como tu número de identificación de contribuyente. {% note %} -**Note:** If your country does not require citizens to have a tax number issued by the government, then you can instead write "not legally required". +**Nota:** Si tu país no requiere que su gobierno emita un número de contribuyente a sus ciudadanos, entonces puedes escribir "no se requiere legalmente". -Guidance from the IRS states that you should not write "not applicable." For more information, see "[Instructions for Form W-8BEN, Line 6](https://www.irs.gov/instructions/iw8ben#idm139867098922656)" on the IRS website. +Los lineamientos del IRS indican que no debes escribir "no aplicable". Para obtener más información, consulta la sección "[Instrucciones para el Formato W-.8BEN, Línea 6](https://www.irs.gov/instructions/iw8ben#idm139867098922656)" en el sitio web del IRS. {% endnote %} -The IRS allows non-resident and resident aliens to request an [Individual Taxpayer Identification Number](https://www.irs.gov/individuals/international-taxpayers/taxpayer-identification-numbers-tin#itin) or ITIN. It is unlikely that this is necessary for maintainers receiving income through {% data variables.product.prodname_sponsors %}, but read the full [instructions](https://www.irs.gov/pub/irs-pdf/iw8ben.pdf) to determine your individual circumstances. +El IRS permite que los residentes extranjeros y los no residentes soliciten un [Número Individual de Identificación de Contribuyente](https://www.irs.gov/individuals/international-taxpayers/taxpayer-identification-numbers-tin#itin) o ITIN. Es poco común que esto sea necesario para los mantenedores que reciben ingresos a través de {% data variables.product.prodname_sponsors %}, pero puedes leer todas las [instrucciones](https://www.irs.gov/pub/irs-pdf/iw8ben.pdf) para determinar tus circunstancias individuales. -## 1099 forms +## Formatos 1099 -If you are a taxpayer in the United States and earn more than 600 US dollars in a tax year, {% data variables.product.prodname_dotcom %} will send you a [1099-NEC](https://www.irs.gov/forms-pubs/about-form-1099-nec) before January 31 of the next calendar year. No proporcionamos formularios fiscales para los contribuyentes internacionales. +Si eres un contribuyente en los Estados Unidos y ganas más de 600 dólares estadounidenses en un año fiscal, {% data variables.product.prodname_dotcom %} te enviará un formato [1099 NEC](https://www.irs.gov/forms-pubs/about-form-1099-nec) antes del 31 de enero del siguiente año calendario. No proporcionamos formularios fiscales para los contribuyentes internacionales. -## General tax information +## Información fiscal general {% data variables.product.prodname_dotcom %} no retiene impuestos de {% data variables.product.prodname_sponsors %} pagos. Los programadores patrocinados son responsables de estimar y pagar sus propios impuestos. {% data reusables.sponsors.sponsorships-not-tax-deductible %} +## Sales tax + +GitHub is providing information to assist you in calculating your sales tax obligations. This information is not personalized to your country or tax situation and we recommend you talk to a professional to understand your specific obligations. However, we'd like to provide some high-level information to help you understand the general principles of digital sales tax. + +In most countries around the world, sales tax for digital transactions is based on the location of the recipient, not on the seller. For example, if you are a maintainer in the United States and you provide a taxable benefit to a Sponsor in Germany, German sales tax would apply. + +Sales tax is generally only applicable when a good or service of value is being provided. Goodwill/general support/undying appreciation is not normally taxable. + +In the US, both B2B (business-to-business) and B2C (business-to-consumer) are subject to sales tax. + +In the EU and most other countries and regions, B2C sales are subject to sales tax. B2B sales are not subject to tax. C2C and C2B sales where a consumer is not registered for VAT are not taxable. + ## Leer más - [Ver tus patrocinadores y patrocinios](/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships) diff --git a/translations/es-ES/content/sponsors/sponsoring-open-source-contributors/paying-for-github-sponsors-by-invoice.md b/translations/es-ES/content/sponsors/sponsoring-open-source-contributors/paying-for-github-sponsors-by-invoice.md index bacb83e639..998cf08a2b 100644 --- a/translations/es-ES/content/sponsors/sponsoring-open-source-contributors/paying-for-github-sponsors-by-invoice.md +++ b/translations/es-ES/content/sponsors/sponsoring-open-source-contributors/paying-for-github-sponsors-by-invoice.md @@ -1,7 +1,7 @@ --- -title: Paying for GitHub Sponsors by invoice -shortTitle: Paying by invoice -intro: 'If your company pays {% data variables.product.company_short %} by invoice, you can join the Sponsors for Companies service.' +title: Pagar por GitHub Sponsors por factura +shortTitle: Pagar por factura +intro: 'Si tu compañía paga por {% data variables.product.company_short %} por factura, puedes unirte al servicio de Patrocinadores para Compañías.' versions: fpt: '*' type: how_to @@ -14,8 +14,8 @@ redirect_from: {% data reusables.sponsors.beta-note-sponsors-for-companies %} -Companies can use an invoice method to participate in the {% data variables.product.prodname_sponsors %} program. This can be particularly convenient if your company has an existing invoiced billing relationship with {% data variables.product.company_short %}. Companies paying by invoice get access to a {% data variables.product.product_name %} dashboard that measures open source contributions and activity across the public projects on {% data variables.product.prodname_dotcom_the_website %} they're interested in. +Las compañías utilizan un método de facturación para participar en el programa de {% data variables.product.prodname_sponsors %}. Esto puede ser particularmente conveniente si tu compañía tiene una relación de cobro por factura con {% data variables.product.company_short %}. Las compañías que pagan por factura obtiene acceso a un tablero de {% data variables.product.product_name %} que mide las contribuciones de código abierto y la actividad a través de los proyectos públicos de {% data variables.product.prodname_dotcom_the_website %} en las que están interesadas. -You can join this beta program by talking to your sales representative, or by [contacting us](https://support.github.com/contact/org-sponsors-waitlist). +Puedes unirte a este programa beta si hablas con tu representante de ventas o si [nos contactas](https://support.github.com/contact/org-sponsors-waitlist). -For information about receiving payments from the Sponsors for Companies service, see "[Receiving payments from Sponsors for Companies](/sponsors/receiving-sponsorships-through-github-sponsors/sponsors-for-companies)." +Para obtener más información sobre cómo recibir pagos del servicio de Patrocinadores para Compañías, consulta la sección "[Recibir pagos de los Patrocinadores para Compañías](/sponsors/receiving-sponsorships-through-github-sponsors/sponsors-for-companies)". 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 c59bfcb91d..409de3e7e4 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 @@ -28,7 +28,7 @@ Puedes patrocinar una cuenta en nombre de tu cuenta de usuario para invertir en - Desarrollar una conciencia de marca como una organización que valora el código abierto - Agradecer a los desarrolladores de código abierto por crear bibliotecas que complementan el producto que ofrece tu organización -Puedes utilizar una tarjeta de crédito para patrocinar una cuenta en {% data variables.product.product_name %}. If your organization wants to pay by invoice, you can read more at [Paying for {% data variables.product.prodname_sponsors %} via invoice](/sponsors/sponsoring-open-source-contributors/paying-for-github-sponsors-via-invoice). +Puedes utilizar una tarjeta de crédito para patrocinar una cuenta en {% data variables.product.product_name %}. Si tu organización quiere pagar por factura, puedes leer más en la sección de [Pagar {% data variables.product.prodname_sponsors %} por factura](/sponsors/sponsoring-open-source-contributors/paying-for-github-sponsors-via-invoice). {% 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)". diff --git a/translations/es-ES/data/glossaries/external.yml b/translations/es-ES/data/glossaries/external.yml index d423ed1f2f..0f829905bc 100644 --- a/translations/es-ES/data/glossaries/external.yml +++ b/translations/es-ES/data/glossaries/external.yml @@ -9,7 +9,7 @@ - term: token de recuperación de cuenta description: >- - La credencial de autenticación almacenada como parte de la configuración de recuperación de una cuenta denominada Recuperar cuentas en otro lugar que te permite almacenar esta credencial de respaldo. + **Se obsoletizó y se inhabilitará el 1 de diciembre de 2021.** La credencial de autenticación que se almacena como parte de una configuración de recuperación de cuenta llamada Recover Accounts Elswhere que te permite almacenar esta credencial de respaldo. - term: Vista previa de API description: >- @@ -574,7 +574,7 @@ - term: Recuperar cuentas en otro lugar description: >- - Le permite a los usuarios agregar un factor de seguridad extra a su cuenta de GitHub en caso de que pierdan acceso a su método de autenticación de dos factores o a sus códigos de recuperación. Los usuarios pueden asociar su cuenta de GitHub con su cuenta de Facebook almacenando una credencial de autenticación en forma de token de recuperación de cuenta para su cuenta de GitHub con Facebook. + **Se obsoletizó y se inhabilitará el 1 de diciembre de 2021.** Permite a los usuarios agregar un factor de seguridad adicional a su cuenta de GitHub en caso de que pierdan acceso a su método de autenticación bifactorial o códigos de recuperación. Los usuarios pueden asociar su cuenta de GitHub con su cuenta de Facebook si almacenan la credencial de autenticación como un token de recuperación de cuenta con Facebook. - term: código de recuperación description: Un código que te ayuda a volver a tener acceso a tu cuenta de GitHub. @@ -654,7 +654,7 @@ description: >- Un registro que enumera las últimas 50 acciones o las realizadas dentro de los últimos 90 días. - - term: server-to-server request + term: solicitud de servidor a servidor description: >- Una solicitud de API que utilice una aplicación que actúe como un bot, independientemente de cualquier usuario particular. Por ejemplo, una aplicación que se ejecuta de forma programada y cierra propuestas donde no ha habido actividad por mucho tiempo. Las aplicaciones que utilizan este tipo de autenticación no utilizan una cuenta de GitHub con licencia, así que, en una empresa con un plan de facturación que permite que se utilicen solo cierto número de licencias, un bot de servidor a servidor no consumirá una de tus licencias de GitHub. El token que se utiliza en una solicitud de servidor a servidor se adquiere programáticamente a través de la [API de GitHub](/rest/reference/apps#create-an-installation-access-token-for-an-app). Consulta también la sección de "[solicitud de usuario a servidor](#user-to-server-request)". - @@ -684,7 +684,7 @@ description: >- Una representación visual dentro de una solicitud de extracción de que tus confirmaciones cumplen las condiciones establecidas para el repositorio con el que estás contribuyendo. - - term: status checks + term: verificaciones de estado description: >- Las verificaciones de estado son procesos externos, como compilaciones de integración continua, que se ejecutan para cada confirmación que realices en un repositorio. Para obtener más información, consulta "[acerca de las verificaciones de Estado] (/articles/about-status-checks)." - @@ -718,7 +718,7 @@ description: >- Un modo de explorar repositorios en una área temática en particular, encontrar proyectos a los cuales contribuir y descubrir nuevas soluciones para un problema específico en GitHub. - - term: traffic graph + term: gráfica de tráfico description: >- Un gráfico del repositorio que muestra el tráfico de un repositorio, incluso clones completos (no recuperaciones), los visitantes de los últimos 14 días, sitios de referencia y contenido popular. - @@ -741,7 +741,7 @@ term: nombre de usuario description: El identificador de un usuario en GitHub. - - term: user-to-server request + term: solicitud de usuario a servidor description: >- Una solicitud de API que utiliza una aplicación que realice la tarea en nombre de un usuario particular. Cuando la tarea se lleva a cabo con una autenticación de usuario a servidor, esta se muestra en GitHub como si la hubiera hecho un usuario a través de una aplicación. Por ejemplo, puedes elegir crear una propuesta desde dentro de una aplicación de terceros y la aplicación lo haría en tu nombre en GitHub. El alcance de las tareas que puede realizar una aplicación utilizando una solicitud de usuario a servidor se restringe tanto por los permisos como por el acceso de la app y del usuario. El token que se utiliza en una solicitud de usuario a servidor se adquiere a través de OAuth. para obtener más información, consulta la sección "[Identificar y autorizar a los usuarios para las GitHub Apps]](/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps)". Consulta también la sección de "[Solicitud de servidor a servidor](#server-to-server-request)". - diff --git a/translations/es-ES/data/glossaries/internal.yml b/translations/es-ES/data/glossaries/internal.yml index 30a37b3a5d..b5a31ef13d 100644 --- a/translations/es-ES/data/glossaries/internal.yml +++ b/translations/es-ES/data/glossaries/internal.yml @@ -229,7 +229,7 @@ - term: GPG description: >- - GNU Privacy Guard. Encryption software that you can use to encrypt (and decrypt) files that contain sensitive data + Guardia de Privacidad de GNU. Software de cifrado que puedes utilizar para cifrar (y descirar) archivos que contienen datos sensibles - term: llave GPG description: Una clave de cifrado usada con GPG. diff --git a/translations/es-ES/data/learning-tracks/README.md b/translations/es-ES/data/learning-tracks/README.md index e05b85d843..f75dab88cb 100644 --- a/translations/es-ES/data/learning-tracks/README.md +++ b/translations/es-ES/data/learning-tracks/README.md @@ -29,7 +29,7 @@ El aprender a rastrear datos de un producto se define en dos lugares: ## Control de versiones -El versionamiento para aprender pistas se procesa en l ahora interpretada de la página. El código vive en [`lib/learning-tracks.js`](lib/learning-tracks.js), al cual llama `page.render()`. The processed learning tracks are then rendered by `components/sublanding`. +El versionamiento para aprender pistas se procesa en l ahora interpretada de la página. El código vive en [`lib/learning-tracks.js`](lib/learning-tracks.js), al cual llama `page.render()`. `components/sublanding` interpreta las pistas de aprendizaje procesadas. Las condicionales líquidas **no** deben utilizarse para versionar en el archivo YAML para las guías. Solo las guías de pistas de aprendizaje que aplican a la versión actual se interpretarán automáticamente. Si no hay pistas con guías que pertenezcan a la versión actual, la sección de pistas de aprendizaje no se interpretará en lo absoluto. diff --git a/translations/es-ES/data/learning-tracks/actions.yml b/translations/es-ES/data/learning-tracks/actions.yml index e547e6cb94..b326c44b11 100644 --- a/translations/es-ES/data/learning-tracks/actions.yml +++ b/translations/es-ES/data/learning-tracks/actions.yml @@ -7,6 +7,7 @@ getting_started: - /actions/learn-github-actions/finding-and-customizing-actions - /actions/learn-github-actions/essential-features-of-github-actions - /actions/learn-github-actions/managing-complex-workflows + - /actions/learn-github-actions/reusing-workflows - /actions/learn-github-actions/security-hardening-for-github-actions featured_track: true continuous_integration: diff --git a/translations/es-ES/data/product-examples/README.md b/translations/es-ES/data/product-examples/README.md index 288332078e..7764a2e7bb 100644 --- a/translations/es-ES/data/product-examples/README.md +++ b/translations/es-ES/data/product-examples/README.md @@ -35,7 +35,7 @@ en donde la sintaxis para `versions` es la misma que la [propiedad de texto prel Los datos de ejemplo del producto se agregan al objeto `context` en `middleware/contextualizers/product-examples.js`. -The data is then rendered by `components/landing`. +Entonces, `components/landing` interpretará los datos. ## Imposición del modelado diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-20/15.yml b/translations/es-ES/data/release-notes/enterprise-server/2-20/15.yml index 5c45606855..9497fe99b1 100644 Binary files a/translations/es-ES/data/release-notes/enterprise-server/2-20/15.yml and b/translations/es-ES/data/release-notes/enterprise-server/2-20/15.yml differ diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-21/6.yml b/translations/es-ES/data/release-notes/enterprise-server/2-21/6.yml index b05ff2c584..0bda5eabf4 100644 Binary files a/translations/es-ES/data/release-notes/enterprise-server/2-21/6.yml and b/translations/es-ES/data/release-notes/enterprise-server/2-21/6.yml differ diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-22/17.yml b/translations/es-ES/data/release-notes/enterprise-server/2-22/17.yml index 0c35c14592..e39a47c61d 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/2-22/17.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/2-22/17.yml @@ -1,16 +1,16 @@ date: '2021-07-14' sections: security_fixes: - - '**HIGH:** A path traversal vulnerability was identified in GitHub Enterprise Server that could be exploited when building a GitHub Pages site. User-controlled configuration options used by GitHub Pages were not sufficiently restricted and made it possible to read files on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.1.3 and has been assigned CVE-2021-22867. This vulnerability was reported via the GitHub Bug Bounty program.' + - '**ALTA:** Una vulnerabilidad que atravesaba rutas se identificó en GitHub Enterprise Server, la cual podría aprovecharse al crear un sitio de GitHub Pages. Las opciones de configuración que controla el usuario y que utiliza GitHub Pages no se restringieron suficientemente, lo cual hizo posible que se leyeran archivos en la instancia de GitHub Enterprise Server. Para aprovechar esta vulnerabilidad, el atacante necesitaría permiso para crear y compilar un sitio de GitHub Pages en la instancia de GitHub Enterprise Server. Esta vulnerabilidad afectó a todas las versiones de GitHub Enterprise Server anteriores a la 3.1.3 y se le asignó el CVE-2021-22867. Esta vulnerabilidad se reportó a través del programa de Recompensas por Errores de GitHub.' - 'Los paquetes se actualizaron a las últimas versiones de seguridad.' bugs: - - '`ghe-cluster-config-node-init` would fail during cluster setup if HTTP proxy is enabled.' - - 'Collectd would not resolve the forwarding destination hostname after the initial startup.' - - 'The job that purged stale deleted repositories could fail to make progress if some of those repositories were protected from deletion by legal holds.' - - 'Git pushes could result in a 500 Internal Server Error during the user reconciliation process on instances using LDAP authentication mode.' - - 'A significant number of 503 errors were logged every time a user visited a repository''s `/settings` page if the dependency graph was not enabled.' + - 'El `ghe-cluster-config-node-init` falló durante la configuración de clúster si se había habilitado el proxy de HTTP.' + - 'Collectd no resolvió el nombre de host destino que se estaba reenviando después del inicio principal.' + - 'El job que purgó los repositorios inactivos borrados pudo haber fallado en hacer progreso si alguno de estos repositorios estaba protegido contra borrado debido a las retenciones legales.' + - 'Las subidas de Git dieron como resultado un Error de Servidor Interno 500 durante el proceso de reconciliación del usuario en las instancias que utilizaban el modo de autenticación de LDAP.' + - 'Una cantidad significativa de 503 errores se registró cada que un usuario vistió la página de `/settings` de un repositorio si la gráfica de dependencias no estaba habilitada.' changes: - - 'Improved the efficiency of config apply by skipping IP allow firewall rules that had not changed, which saved significant time on large clusters.' + - 'Se mejoró la eficiencia de la aplicación de configuraciones al omitir las reglas de cortafuegos para permitir IP, las cuales no hubieran cambiado, lo cual ahorró tiempo significativo en los clústeres grandes.' known_issues: - 'En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador.' - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-22/18.yml b/translations/es-ES/data/release-notes/enterprise-server/2-22/18.yml index 6af68307e3..619bed1448 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/2-22/18.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/2-22/18.yml @@ -3,10 +3,10 @@ sections: security_fixes: - 'Los paquetes se actualizaron a las últimas versiones de seguridad.' bugs: - - 'A significant number of 503 errors were being created if the scheduled job to sync vulnerabilities with GitHub.com attempted to run when dependency graph was not enabled and content analysis was enabled.' - - 'Unauthenticated HTTP proxy for the pages containers build was not supported for any users that use HTTP proxies.' + - 'Una cantidad significativa de 503 errores se habrían estado creando si el job programado para sincronizar vulnerabilidades con GitHub.com intentó ejecutarse cuando la gráfica de dependencias no estuvo habilitada y el análisis de contenido sí estaba habilitado.' + - 'El proxy HTTP no autenticado para la compilación de contenedores de las páginas no era compatible para ningún usuario que utilizara proxys HTTP.' changes: - - 'The logs for `babeld` now include a `cmd` field for HTTP ref advertisement requests instead of only including it during the negotiation requests.' + - 'Las bitácoras de `babeld` ahora incluyen un campo de `cmd` para las solicitudes de publicidad de ref de HTTP en vez de solo incluirlas durante las solicitudes de negociación.' known_issues: - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-22/19.yml b/translations/es-ES/data/release-notes/enterprise-server/2-22/19.yml index f9226debd2..6d30bc1a83 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/2-22/19.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/2-22/19.yml @@ -1,9 +1,9 @@ date: '2021-08-10' sections: bugs: - - 'Audit log entries for changes made to "Repository creation" organization settings were inaccurate.' + - 'Las entradas de bitácoras de auditoría para los cambios realizados a los ajustes de organización de "Creación de repositorios" fueron inexactas.' changes: - - 'Abuse rate limits are now called Secondary rate limits, since the behavior they limit is not always abusive.' + - 'El abuso de límites de tasa ahora se llama Límites de tasa secundarios, ya que el comportamiento que limitan no siempre es abusivo.' known_issues: - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-22/20.yml b/translations/es-ES/data/release-notes/enterprise-server/2-22/20.yml index c18c191a7a..a76faf2037 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/2-22/20.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/2-22/20.yml @@ -3,8 +3,8 @@ sections: security_fixes: - 'Los paquetes se actualizaron a las últimas versiones de seguridad.' bugs: - - 'Journald messages related to automatic updates (`Adding h/m/s random time.`) were logged to syslog.' - - 'Git hooks to the internal API that result in failing requests returned the exception `undefined method body for "success":String (NoMethodError)` instead of returning an explicit `nil`.' + - 'Los mensajes de Journald con relación a las actualizaciones automáticas (`Agregar una hora aleatoria en h/m/s.`) se registraron en syslog.' + - 'Los ganchos de Git hacia la API interna que dio como resultado solicitudes fallidas devolvieron la excepción `undefined method body for "success":String (NoMethodError)` en vez de devolver un `nil` explícito.' known_issues: - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/2-22/22.yml b/translations/es-ES/data/release-notes/enterprise-server/2-22/22.yml new file mode 100644 index 0000000000..d205514db5 --- /dev/null +++ b/translations/es-ES/data/release-notes/enterprise-server/2-22/22.yml @@ -0,0 +1,14 @@ +date: '2021-09-24' +sections: + security_fixes: + - '**HIGH:** Se identificó una vulnerabilidad de navegación de ruta en {% data variables.product.prodname_ghe_server %} que pudo haberse aprovechado al crear un sitio de {% data variables.product.prodname_pages %}. Las opciones de configuración que controla el usuario y que utiliza {% data variables.product.prodname_pages %} no se restringieron lo suficiente e hicieron posible que se leyeran archivos en la instancia de {% data variables.product.prodname_ghe_server %}. Para aprovechar esta vulnerabilidad, los atacantes tendrían que obtener permisos para crear y compilar un sitio de {% data variables.product.prodname_pages %} en la instancia de {% data variables.product.prodname_ghe_server %}. Esta vulnerabilidad afectó a todas las versiones de {% data variables.product.prodname_ghe_server %} anteriores a la 3.1.8 y se arregló en las versiones 3.1.8, 3.0.16 y 2.22.22. Este es el resultado de un arreglo incompleto para el caso CVE-2021-22867. Esta vulnerabilidad se reportó a través del Programa de Recompensas por Errores de GitHub y se le asignó el caso CVE-2021-22868. {% comment %} https://github.com/github/pages/pull/3359, https://github.com/github/pages/pull/3357 {% endcomment %}' + bugs: + - 'La configuración de {% data variables.product.prodname_github_connect %} de la instancia siempre se restableció a instancias nuevas, incluso cuando no se utilizó la opción `--config` option para `ghe-restore`. Esto podría ocasionar un conflicto con la conexión de {% data variables.product.prodname_github_connect %} y con la sincronización de licencias si tanto las instancias de origen como las de destino estuvieran en línea al mismo tiempo. {% comment %} https://github.com/github/github/pull/192247, https://github.com/github/github/pull/191951, https://github.com/github/enterprise2/pull/26870, https://github.com/github/backup-utils/pull/770, https://github.com/github/connected-enterprise/issues/208 {% endcomment %}' + - 'Arregla compilaciones de {% data variables.product.prodname_pages %} para que tomen en cuenta la configuración de NO_PROXY del aplicativo. Esto es relevante para los aplicativos configurados únicamente con un proxy HTTP. {% comment %} https://github.com/github/github/pull/192380 {% endcomment %}' + known_issues: + - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' + - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.' + - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con {% data variables.product.prodname_github_connect %}, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.' + - 'Cuando un nodo de réplica está fuera de línea en una configuración de disponibilidad alta, {% data variables.product.product_name %} aún podría enrutar las solicitudes a {% data variables.product.prodname_pages %} para el nodo fuera de línea, reduciendo la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/0-rc1.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/0-rc1.yml index 0a82ca02b0..29af190caa 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/0-rc1.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-0/0-rc1.yml @@ -19,7 +19,7 @@ sections: - Las utilidades de seguridad pueden activar correos electrónicos innecesarios para los administradores - La configuración incorrecta de los paquetes se muestra en la página de vista de miembros de la organización - Después de eliminarte a ti mismo como propietario de la empresa, se te redireccionará a una página 404. La operación será exitosa. - - '`ghe-config-apply` occasionally fails with `ERROR: Failure waiting for nomad jobs to apply` until the Nomad job queue is cleared. This currently requires as admin to delete `/etc/nomad-jobs/queue`.' + - '`ghe-config-apply` ocasionalmente falla con `ERROR: Failure waiting for nomad jobs to apply` hasta que la cola de job Nómada se vacíe. Esto requiere actualmente que un administrador borre la parte de `/etc/nomad-jobs/queue`.' - Cuando configuras un nodo de rélica múltiple, el estado de la réplica puede sincronizarse incorrectamente. - Los clientes que intentan restablecer un respaldo de 3.0 en una instancia nueva no deberán preconfigurarla, ya que esto podría conllevar a un estado malo para los inicios de sesión de usuario. Te recomendamos restablecerte a una instancia inconfigurada y nueva. - Los candidatos de lanzamiento para el lanzamiento de GitHub Enterprise Server 3.0 aún no están disponibles en el mercado de Azure. Para probar los candidatos de lanzamiento en ambientes de montaje, inicia una instancia 2.21 o 2.22 y luego actualízala con el paquete de mejoras de Azure en la página de descargas. diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/0.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/0.yml index e04d2ee334..8ac540fdbb 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/0.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-0/0.yml @@ -25,7 +25,7 @@ sections: - 'El sistema de entrega de eventos de webhook se ha renovado en su arquitectura para tener un rendimiento mayor y menos retraso en los mensajes. También utiliza menos memoria y CPU en {% data variables.product.prodname_ghe_server %} 3.0+.' - 'Los propietarios de empresas y organizaciones ahora pueden ver a qué miembros del equipo se ha promovido o degradado hacia o desde su puesto como mantenedor de equipo en la bitácora de auditoría a través de los nuevos eventos de bitácora de auditoría `team.promote_maintainer` y `team.demote_maintainer`. Para obtener más información, consulta la sección "[Acciones auditadas](/enterprise-server@3.0/admin/user-management/audited-actions)".' - 'Los mantenedores de repositorio con sitios de {% data variables.product.prodname_pages %} existentes pueden [actualizar fácilmente el nombre de rama predeterminado anterior](/enterprise-server@3.0/github/working-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites).' - - 'Additional hardware resources are required to run {% data variables.product.prodname_ghe_server %} with any of Actions, Packages or Advanced Security enabled. For more information on the minimum required resources for each supported platform, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise-server@3.0/admin/installation/setting-up-a-github-enterprise-server-instance)."' + - 'Se requieren recursos adicionales de hardware para ejecutar {% data variables.product.prodname_ghe_server %} que cuente con cualquier tipo de Acción, Paquete o Seguridad Avanzada habilitados. Para obtener más información sobre los recursos mínimos requeridos para cada plataforma compatible, consulta la sección "[Configurar una instancia de {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.0/admin/installation/setting-up-a-github-enterprise-server-instance)".' - 'Los administradores ahora pueden [publicar un mensaje](/enterprise-server@3.0/admin/user-management/customizing-user-messages-for-your-enterprise), que todos los usuarios deben aceptar. Esto te puede ayudar a incorporar usuarios nuevos y hacer notar otras políticas e información específica de la organización.' - heading: 'Cambios de seguridad' notes: @@ -80,7 +80,7 @@ sections: - 'Las compilaciones antiguas de las páginas no se limpiaron, lo cual pudo haber llenado el disco del usuario (`/data/user/`).' - 'Cuando borras una rama después de fusionar una solicitud de cambios, se mostrará un mensaje de error aunque el borrado de la rama sea exitoso.' - 'Cuando un nodo de réplica está fuera de línea en una configuración de disponibilidad alta, {% data variables.product.product_name %} aún podría enrutar las solicitudes a {% data variables.product.prodname_pages %} para el nodo fuera de línea, reduciendo la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' - - 'Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.' + - '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.' deprecations: - heading: 'Obsoletización de GitHub Enterprise Server 2.19' notes: diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/1.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/1.yml index 5eb9037e79..2386c55ded 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/1.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-0/1.yml @@ -35,7 +35,7 @@ sections: - '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 era más grande a 255 caracteres.' - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.' - - '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://enterprise.githubsupport.com/hc/en-us).' + - 'Cuando se habilita el modo de mantenimiento, algunos servicios siguen estando listados como "procesos activos". Se espera que los servicios identificados se ejecuten durante el modo de mantenimiento. Si experimentas este problema y no estás seguro de cómo solucionarlo, contacta al [Soporte Empresarial de GitHub](https://enterprise.githubsupport.com/hc/en-us).' - 'El registro duplicado hacia `/var/log/messages`, `/var/log/syslog`, y `/var/log/user.log` da como resultado una utilización incrementada del volúmen raíz.' - 'Los usuarios pueden descartar un mensaje obligatorio sin verificar todas las casillas.' - '[Los scripts de gancho de pre-recepción](/admin/policies/enforcing-policy-with-pre-receive-hooks) no pueden escribir archivos temporales, los cuales pueden causar que falle la ejecución del script. Los usuarios que utilizan ganchos de pre-recepción deberían hacer pruebas en un ambiente de pruebas para ver si dichos scripts requieren de acceso de escritura.' @@ -69,4 +69,4 @@ sections: 2. Si muestra que uno o más nodos están afectados, reinícialos. - 'Cuando un nodo de réplica está fuera de línea en una configuración de disponibilidad alta, {% data variables.product.product_name %} aún podría enrutar las solicitudes a {% data variables.product.prodname_pages %} para el nodo fuera de línea, reduciendo la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. + - 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-0/10.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/10.yml index f3ecf98dd8..7a9db20be1 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/10.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-0/10.yml @@ -17,4 +17,4 @@ sections: - Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres. - Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com. - Cuando un nodo de réplica está fuera de línea en una configuración de disponibilidad alta, {% data variables.product.product_name %} aún podría enrutar las solicitudes a {% data variables.product.prodname_pages %} para el nodo fuera de línea, reduciendo la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. + - 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-0/11.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/11.yml index 684d142e1c..0cd557d14f 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/11.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-0/11.yml @@ -1,21 +1,21 @@ date: '2021-07-14' sections: security_fixes: - - '**HIGH:** A path traversal vulnerability was identified in GitHub Enterprise Server that could be exploited when building a GitHub Pages site. User-controlled configuration options used by GitHub Pages were not sufficiently restricted and made it possible to read files on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.1.3 and has been assigned CVE-2021-22867. This vulnerability was reported via the GitHub Bug Bounty program.' + - '**ALTA:** Una vulnerabilidad que atravesaba rutas se identificó en GitHub Enterprise Server, la cual podría aprovecharse al crear un sitio de GitHub Pages. Las opciones de configuración que controla el usuario y que utiliza GitHub Pages no se restringieron suficientemente, lo cual hizo posible que se leyeran archivos en la instancia de GitHub Enterprise Server. Para aprovechar esta vulnerabilidad, el atacante necesitaría permiso para crear y compilar un sitio de GitHub Pages en la instancia de GitHub Enterprise Server. Esta vulnerabilidad afectó a todas las versiones de GitHub Enterprise Server anteriores a la 3.1.3 y se le asignó el CVE-2021-22867. Esta vulnerabilidad se reportó a través del programa de Recompensas por Errores de GitHub.' - 'Los paquetes se actualizaron a las últimas versiones de seguridad.' bugs: - - 'SAML expiration date variable was not configurable.' - - 'Application services would fail their health checks during config apply before they could enter a healthy state.' - - '`ghe-cluster-config-node-init` would fail during cluster setup if HTTP proxy is enabled.' - - 'Pre-receive hooks could encounter an error `Failed to resolve full path of the current executable` due to `/proc` not being mounted on the container.' - - 'Collectd would not resolve the forwarding destination hostname after the initial startup.' - - 'The job that purged stale deleted repositories could fail to make progress if some of those repositories were protected from deletion by legal holds.' - - 'Running `git nw-gc --pristine` would result in an error.' - - 'Background jobs were being queued to the `spam` queue which were not being processed.' - - 'The preferred merge method would be reset when retrying after a failed PR merge.' - - 'Git pushes could result in a 500 Internal Server Error during the user reconciliation process on instances using LDAP authentication mode.' + - 'La variable de vencimiento de fecha de SAML no se pudo configurar.' + - 'Los servicios de aplicación fallaron en sus verificaciones de salud durante una aplicación de configuración antes de que pudieran ingresar a un estado saludable.' + - 'El `ghe-cluster-config-node-init` falló durante la configuración de clúster si se había habilitado el proxy de HTTP.' + - 'Los ganchos de pre-recepción pudieron haber encontrado un error de tipo `Failed to resolve full path of the current executable` debido a que un `/proc` no se pudo montar en el contenedor.' + - 'Collectd no resolvió el nombre de host destino que se estaba reenviando después del inicio principal.' + - 'El job que purgó los repositorios inactivos borrados pudo haber fallado en hacer progreso si alguno de estos repositorios estaba protegido contra borrado debido a las retenciones legales.' + - 'El ejecutar `git nw-gc --pristine` dio como resultado un error.' + - 'Los jobs en segundo plano se pusieron en la fila de `spam`, los cuales no se estaban procesando.' + - 'El método de fusión preferido se restablecerá cuando se reintente después de una fusión fallida de solicitud de cambio.' + - 'Las subidas de Git dieron como resultado un Error de Servidor Interno 500 durante el proceso de reconciliación del usuario en las instancias que utilizaban el modo de autenticación de LDAP.' changes: - - 'Improved the efficiency of config apply by skipping IP allow firewall rules that had not changed, which saved significant time on large clusters.' + - 'Se mejoró la eficiencia de la aplicación de configuraciones al omitir las reglas de cortafuegos para permitir IP, las cuales no hubieran cambiado, lo cual ahorró tiempo significativo en los clústeres grandes.' known_issues: - 'En un GitHub Enterprise Server recién configurado sin usuarios, un atacante pudo crear el primer usuario administrador.' - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' @@ -23,4 +23,4 @@ sections: - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.' - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.' - 'Cuando un nodo de réplica está fuera de línea en una configuración de disponibilidad alta, {% data variables.product.product_name %} aún podría enrutar las solicitudes a {% data variables.product.prodname_pages %} para el nodo fuera de línea, reduciendo la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' - - 'Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.' + - '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-0/12.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/12.yml index 9d4684dbe0..03f64e9758 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/12.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-0/12.yml @@ -3,14 +3,14 @@ sections: security_fixes: - 'Los paquetes se actualizaron a las últimas versiones de seguridad.' bugs: - - 'Custom pre-receive hooks could lead to an error like `error: object directory /data/user/repositories/0/nw/12/34/56/7890/network.git/objects does not exist; check .git/objects/info/alternates`.' - - 'Unauthenticated HTTP proxy for the pages containers build was not supported for any users that use HTTP proxies.' - - 'A significant number of 503 errors were logged every time a user visited a repository''''s `/settings` page if the dependency graph was not enabled.' - - 'Internal repositories were only returned when a user had affiliations with the repository through a team or through collaborator status, or queried with the `?type=internal` parameter.' - - 'Failed background jobs had unlimited retries which could cause large queue depths.' - - 'A significant number of 503 errors were being created if the scheduled job to sync vulnerabilities with GitHub.com attempted to run when dependency graph was not enabled and content analysis was enabled.' + - 'Los ganchos de pre-recepción personalizados podrían llevar a un error como `error: object directory /data/user/repositories/0/nw/12/34/56/7890/network.git/objects does not exist; check .git/objects/info/alternates`.' + - 'El proxy HTTP no autenticado para la compilación de contenedores de las páginas no era compatible para ningún usuario que utilizara proxys HTTP.' + - 'Una cantidad significativa de 503 errores se registró cada que un usuario vistió la página de `/settings` de un repositorio si la gráfica de dependencias no estaba habilitada.' + - 'Los repositorios internos solo se devolvieron cuando un usuario había tenido afiliaciones con el repositorio mediante un equipo o estado de colaborador o cuando se consultaron con el parámetro `?type=internal`.' + - 'Los jobs en segundo plano fallidos tienen reintentos ilimitados, los cuales podrían causar filas muy largas.' + - 'Una cantidad significativa de 503 errores se habrían estado creando si el job programado para sincronizar vulnerabilidades con GitHub.com intentó ejecutarse cuando la gráfica de dependencias no estuvo habilitada y el análisis de contenido sí estaba habilitado.' changes: - - 'The logs for `babeld` now include a `cmd` field for HTTP ref advertisement requests instead of only including it during the negotiation requests.' + - 'Las bitácoras de `babeld` ahora incluyen un campo de `cmd` para las solicitudes de publicidad de ref de HTTP en vez de solo incluirlas durante las solicitudes de negociación.' known_issues: - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' @@ -18,4 +18,4 @@ sections: - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.' - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.' - 'Cuando un nodo de réplica está fuera de línea en una configuración de disponibilidad alta, {% data variables.product.product_name %} aún podría enrutar las solicitudes a {% data variables.product.prodname_pages %} para el nodo fuera de línea, reduciendo la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' - - 'Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.' + - '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-0/13.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/13.yml index cd887eaea5..c3186cfd25 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/13.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-0/13.yml @@ -1,12 +1,12 @@ date: '2021-08-10' sections: bugs: - - 'When GitHub Actions is enabled without running regular scheduled backups the MSSQL Transaction Log could grow unbounded and can consume all available space on the appliance''s Data Disk causing a possible outage.' - - 'Audit log entries for changes made to "Repository creation" organization settings were inaccurate.' - - 'Excessive logging of `ActionController::UnknownFormat` exceptions caused unnecessary disk usage.' - - 'LDAP `group_dn` values longer than 255 characters would result in errors being logged: `Data truncated for column ''group_dn'' at row 1`.' + - 'Cuando se habilitaron las GitHub Actions sin ejecutar los respaldos con programación frecuente, la bitácora de transacción de MSSQL pudo haber crecido más allá de los límites y consumido todo el espacio disponible en el disco de datos del aplicativo, causando una posible interrupción del servicio.' + - 'Las entradas de bitácoras de auditoría para los cambios realizados a los ajustes de organización de "Creación de repositorios" fueron inexactas.' + - 'El registro excesivo de las exepciones de `ActionController::UnknownFormat` causa un uso innecesario de disco.' + - 'Los valores de `group_dn` de LDAP de más de 255 caracteres dieron como resultado que los errores se registraran: `Datos truncados para la columna ''group_dn'' en la fila 1`.' changes: - - 'Abuse rate limits are now called Secondary rate limits, since the behavior they limit is not always abusive.' + - 'El abuso de límites de tasa ahora se llama Límites de tasa secundarios, ya que el comportamiento que limitan no siempre es abusivo.' known_issues: - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' @@ -14,4 +14,4 @@ sections: - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.' - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.' - 'Cuando un nodo de réplica está fuera de línea en una configuración de disponibilidad alta, {% data variables.product.product_name %} aún podría enrutar las solicitudes a {% data variables.product.prodname_pages %} para el nodo fuera de línea, reduciendo la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' - - 'Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.' + - '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-0/14.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/14.yml index a230f76544..f70ec4b348 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/14.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-0/14.yml @@ -3,14 +3,14 @@ sections: security_fixes: - 'Los paquetes se actualizaron a las últimas versiones de seguridad.' bugs: - - 'Attaching very large images or animated GIFs to images or pull requests would fail.' - - 'Journald messages related to automatic updates (`Adding h/m/s random time.`) were logged to syslog.' - - 'Custom pre-receive hooks that used a bash subshell would return an error: `No such file or directory`.' - - 'Custom pre-receive hooks that created named pipes (FIFOs) would crash or hang, resulting in a timeout error.' - - 'Adding filters to the audit log advanced search page did not populate the query text box in real-time with the correct facet prefix and value.' - - 'Git hooks to the internal API that result in failing requests returned the exception `undefined method body for "success":String (NoMethodError)` instead of returning an explicit `nil`.' - - 'When an integration was removed, it was possible for an unrelated OAuth application or integration to also be removed.' - - 'When a mandatory message containing an emoji character was added, attempting to view or change the message would return a 500 Internal Server Error.' + - 'El agregar imágenes muy grandes o GIF animados a las imágenes o solicitudes de cambio, fallará.' + - 'Los mensajes de Journald con relación a las actualizaciones automáticas (`Agregar una hora aleatoria en h/m/s.`) se registraron en syslog.' + - 'Los ganchos de pre-recepción que utilizaron un subshell de bash devolvieron un error de tipo: `No such file or directory`.' + - 'Los ganchos de pre-recepción que crearon canalizaciones nombradas (FIFO) fallaron o demoraron, lo cual resultó en un error de tiempo de espera.' + - 'Agregar filtros para que la página de búsqueda avanzada de bitácoras de auditoría no llenó la caja de texto de consultas en tiempo real con el valor y prefijo de faceta correcto.' + - 'Los ganchos de Git hacia la API interna que dio como resultado solicitudes fallidas devolvieron la excepción `undefined method body for "success":String (NoMethodError)` en vez de devolver un `nil` explícito.' + - 'Cuando se eliminó una integración, fue posible que una aplicación OAuth o integración no relacionada s también se eliminaran.' + - 'Cuando se agregó un mensaje obligatorio que contenía un caracter de emoji que intentaba ver o cambiar el mensaje, se devolvió un error tipo "500 Internal Server Error".' known_issues: - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' @@ -18,4 +18,4 @@ sections: - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.' - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.' - 'Cuando un nodo de réplica está fuera de línea en una configuración de disponibilidad alta, {% data variables.product.product_name %} aún podría enrutar las solicitudes a {% data variables.product.prodname_pages %} para el nodo fuera de línea, reduciendo la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' - - 'Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.' + - '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-0/15.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/15.yml index a6c47b39d3..79fa3934f6 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/15.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-0/15.yml @@ -3,10 +3,10 @@ sections: security_fixes: - 'Los paquetes se actualizaron a las últimas versiones de seguridad.' bugs: - - 'Attempting to tear down a newly-added replica node by specifying its UUID with `ghe-repl-teardown` would fail without reporting an error if replication was not started.' - - 'GitHub Pages builds were being passed through an external proxy if there was one configured.' - - 'Custom pre-receive hooks that created sub-processes would lack a `PATH` variable in their environment, resulting in "No such file or directory" errors.' - - 'MySQL could failover during an upgrade if `mysql-auto-failover` was enabled.' + - 'Intentar tirar un nodo de réplica recién agregado especificando su UUID con `ghe-repl-teardown` falló sin reportar un error en caos de que la replicación no hubiera iniciado.' + - 'Las compilaciones de GitHub Pages se estaban pasando por un proxy externo si es que había alguno configurada.' + - 'Los ganchos de pre-recepción que crearon subprocesos no tenían una variable de `PATH` en su ambiente, lo cual dio como resultado un error de tipo "No such file or directory".' + - 'MySQL pudo haberse recuperado de un desastre durante una mejora si se había habilitado `mysql-auto-failover`.' known_issues: - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' @@ -14,4 +14,4 @@ sections: - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.' - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.' - 'Cuando un nodo de réplica está fuera de línea en una configuración de disponibilidad alta, {% data variables.product.product_name %} aún podría enrutar las solicitudes a {% data variables.product.prodname_pages %} para el nodo fuera de línea, reduciendo la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' - - 'Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.' + - '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-0/16.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/16.yml new file mode 100644 index 0000000000..928e64a275 --- /dev/null +++ b/translations/es-ES/data/release-notes/enterprise-server/3-0/16.yml @@ -0,0 +1,17 @@ +date: '2021-09-24' +sections: + security_fixes: + - '**ALTA:** Se identificó una vulnerabilidad de navegación de ruta en {% data variables.product.prodname_ghe_server %} que podría aprovecharse cuando se compile un sitio de {% data variables.product.prodname_pages %}. Las opciones de configuración que controla el usuario y que utilizan las {% data variables.product.prodname_pages %} no se restringieron lo suficiente e hicieron posible que se leyeran archivos en la instancia de {% data variables.product.prodname_ghe_server %}. para explotar esta vulnerabilidad, un atacante necesitaría permiso para crear y compilar un sitio de {% data variables.product.prodname_pages %} en la instancia de {% data variables.product.prodname_ghe_server %}. Esta vulnerabilidad afectó a todas las versiones de {% data variables.product.prodname_ghe_server %} anteriores a la 3.1.8 y se corriegió en la 3.1.8, 3.0.16 y 2.22.22. Este es el resultado de un arreglo incompleto para el caso CVE-2021-22867. Esta vulnerabilidad se reportó mediante el Programa de Recompensas por Errores de GitHub y se le asignó el caso CVE-2021-22868. {% comment %} https://github.com/github/pages/pull/3360, https://github.com/github/pages/pull/3357 {% endcomment %}' + - '**MEDIA:** Una vulnerabilidad de control de accesos inadecuada en {% data variables.product.prodname_ghe_server %} permitió que un job de flujo de trabajo se ejecutara en un grupo de ejecutores auto-hospedados al cual no debía haber tenido acceso. Esto afecta a los clientes que utilizan grupos de ejecutores auto-hospedados para el control de accesos. Un repositorio con acceso a un grupo de ejecutores empresariales podría acceder a todos los grupos de ejecutores empresariales dentro de la organización debido a las verificaciones de autenticación inadecuadas durante la solicitud. Esto podría ocasionar que se ejecutara código sin querer por parte del grupo de ejecutores incorrecto. Esta vulnerabilidad afectó a las versiones de la 3.0.0 a la 3.0.15 y de la 3.1.0 a la 3.1.7 de {% data variables.product.prodname_ghe_server %} y se corrigió en los lanzamientos 3.0.16 y 3.1.8. Se le asignó el caso CVE-2021-22869. {% comment %} https://github.com/github/enterprise2/pull/27003 {% endcomment %}' + bugs: + - 'Los conteos del trabajador de Resque se mostraron incorrectamente durante el modo de mantenimiento. {% comment %} https://github.com/github/enterprise2/pull/26898, https://github.com/github/enterprise2/pull/26883 {% endcomment %}' + - 'La memoria memcached asignada pudo haber sido cero en el modo de clústering. {% comment %} https://github.com/github/enterprise2/pull/26927, https://github.com/github/enterprise2/pull/26832 {% endcomment %}' + - "Arregla compilaciones de las {% data variables.product.prodname_pages %} para que tomen en cuenta la configuración de NO_PROXY del aplicativo. Esto es relevante para los aplicativos configurados únicamente con un proxy HTTP. (actualización 2021-09-30) {% comment %} https://github.com/github/pages/pull/3360 {% endcomment %}\n \nsections -> bugs -> 2\nFile: 16.yml" + known_issues: + - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' + - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.' + - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.' + - 'Cuando un nodo de réplica está fuera de línea en una configuración de disponibilidad alta, {% data variables.product.product_name %} aún podría enrutar las solicitudes a {% data variables.product.prodname_pages %} para el nodo fuera de línea, reduciendo la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' + - 'Los límites de recursos que son específicos para procesar ganchos de pre-recepción podrían ocasionar que fallen algunos ganchos de pre-recepción.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/2.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/2.yml index 060178e7d4..9a8f778843 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/2.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-0/2.yml @@ -27,7 +27,7 @@ sections: - 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 era más grande a 255 caracteres. - Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com. - - 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://enterprise.githubsupport.com/hc/en-us). + - Cuando se habilita el modo de mantenimiento, algunos servicios siguen estando listados como "procesos activos". Se espera que los servicios identificados se ejecuten durante el modo de mantenimiento. Si experimentas este problema y no estás seguro de cómo solucionarlo, contacta al [Soporte Empresarial de GitHub](https://enterprise.githubsupport.com/hc/en-us). - La interpretación de Jupyter Notebook en la IU web podría fallar si el bloc de notas incluye caracteres diferentes a los de ASCII UTF-8. - El reStructuredText (RST) que se representa en la IU web podría fallar y mostrar un texto de marcado RST sin procesar. - Las compilaciones antiguas de las páginas no se limpiaron, lo cual pudo haber llenado el disco del usuario (`/data/user/`). @@ -55,4 +55,4 @@ sections: 2. Si muestra que uno o más nodos están afectados, reinícialos. - Cuando un nodo de réplica está fuera de línea en una configuración de disponibilidad alta, {% data variables.product.product_name %} aún podría enrutar las solicitudes a {% data variables.product.prodname_pages %} para el nodo fuera de línea, reduciendo la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. + - 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-0/3.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/3.yml index fbbf31a759..7e9351afde 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/3.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-0/3.yml @@ -26,7 +26,7 @@ sections: - 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 era más grande a 255 caracteres. - Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com. - - 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://enterprise.githubsupport.com/hc/en-us). + - Cuando se habilita el modo de mantenimiento, algunos servicios siguen estando listados como "procesos activos". Se espera que los servicios identificados se ejecuten durante el modo de mantenimiento. Si experimentas este problema y no estás seguro de cómo solucionarlo, contacta al [Soporte Empresarial de GitHub](https://enterprise.githubsupport.com/hc/en-us). - La interpretación de Jupyter Notebook en la IU web podría fallar si el bloc de notas incluye caracteres diferentes a los de ASCII UTF-8. - El reStructuredText (RST) que se representa en la IU web podría fallar y mostrar un texto de marcado RST sin procesar. - Las compilaciones antiguas de las páginas no se limpiaron, lo cual pudo haber llenado el disco del usuario (`/data/user/`). @@ -40,4 +40,4 @@ sections: sudo /usr/sbin/logrotate -f /etc/logrotate.conf ``` - Cuando un nodo de réplica está fuera de línea en una configuración de disponibilidad alta, {% data variables.product.product_name %} aún podría enrutar las solicitudes a {% data variables.product.prodname_pages %} para el nodo fuera de línea, reduciendo la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios. - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. + - 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-0/4.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/4.yml index 7af68b949e..bd851de946 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/4.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-0/4.yml @@ -24,4 +24,4 @@ sections: - 'El reStructuredText (RST) que se representa en la IU web podría fallar y mostrar un texto de marcado RST sin procesar.' - 'Cuando borras una rama después de fusionar una solicitud de cambios, se mostrará un mensaje de error aunque el borrado de la rama sea exitoso.' - 'Cuando un nodo de réplica está fuera de línea en una configuración de disponibilidad alta, {% data variables.product.product_name %} aún podría enrutar las solicitudes a {% data variables.product.prodname_pages %} para el nodo fuera de línea, reduciendo la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' - - 'Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.' + - '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-0/5.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/5.yml index e3d5d4a16f..88bf8ed26f 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/5.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-0/5.yml @@ -25,4 +25,4 @@ sections: - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.' - 'Cuando borras una rama después de fusionar una solicitud de cambios, se mostrará un mensaje de error aunque el borrado de la rama sea exitoso.' - 'Cuando un nodo de réplica está fuera de línea en una configuración de disponibilidad alta, {% data variables.product.product_name %} aún podría enrutar las solicitudes a {% data variables.product.prodname_pages %} para el nodo fuera de línea, reduciendo la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' - - 'Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.' + - '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-0/6.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/6.yml index 463dc1d6ec..f6069f6eb4 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/6.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-0/6.yml @@ -28,4 +28,4 @@ sections: - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio era más grande a 255 caracteres.' - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.' - 'Cuando un nodo de réplica está fuera de línea en una configuración de disponibilidad alta, {% data variables.product.product_name %} aún podría enrutar las solicitudes a {% data variables.product.prodname_pages %} para el nodo fuera de línea, reduciendo la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' - - 'Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.' + - '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-0/7.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/7.yml index a41d0586ed..96ee9c3beb 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/7.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-0/7.yml @@ -21,4 +21,4 @@ sections: - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio era más grande a 255 caracteres.' - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.' - 'Cuando un nodo de réplica está fuera de línea en una configuración de disponibilidad alta, {% data variables.product.product_name %} aún podría enrutar las solicitudes a {% data variables.product.prodname_pages %} para el nodo fuera de línea, reduciendo la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' - - 'Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.' + - '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-0/8.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/8.yml index 95d1a7e6e1..744f9b2345 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/8.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-0/8.yml @@ -24,4 +24,4 @@ sections: - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio era más grande a 255 caracteres.' - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.' - 'Cuando un nodo de réplica está fuera de línea en una configuración de disponibilidad alta, {% data variables.product.product_name %} aún podría enrutar las solicitudes a {% data variables.product.prodname_pages %} para el nodo fuera de línea, reduciendo la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' - - 'Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.' + - '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-0/9.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/9.yml index d97f9224e1..fbeb6dca37 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-0/9.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-0/9.yml @@ -21,4 +21,4 @@ sections: - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.' - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.' - 'Cuando un nodo de réplica está fuera de línea en una configuración de disponibilidad alta, {% data variables.product.product_name %} aún podría enrutar las solicitudes a {% data variables.product.prodname_pages %} para el nodo fuera de línea, reduciendo la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' - - 'Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.' + - 'Los límites de recursos que son específicos para procesar ganchos de pre-recepción podrían ocasionar que fallen algunos ganchos de pre-recepción.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/0.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/0.yml index 5b2bcdeff0..6f3bbb15f3 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-1/0.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-1/0.yml @@ -85,7 +85,7 @@ sections: - 'El actualizar una instancia que ejecuta un lanzamiento 2.13 previamente, pero no uno de tipo 2.14, da como resultado un error de migración de base de datos que se relacionaba con la transición de datos `AddRepositoryIdToCheckRuns`.' - "Después de actualizar de la versión 3.0.x a la 3.1.x, en algunos casos, puede que GitHub actions falle con un error de tipo: `An unexpected error occurred when executing this workflow.` Para solucionar este problema, conéctate al shell administrativo (ssh) y ejecuta:\n```\nghe-actions-console -s actions -c \"Queue-ServiceJob -JobId 4DB1F4CF-19FD-40E0-A253-91288813DE8B\"\n```\n" - 'Cuando un nodo de réplica está fuera de línea en una configuración de disponibilidad alta, {% data variables.product.product_name %} aún podría enrutar las solicitudes a {% data variables.product.prodname_pages %} para el nodo fuera de línea, reduciendo la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' - - 'Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.' + - '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.' deprecations: - heading: 'Obsoletización de GitHub Enterprise Server 2.20' notes: diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/1.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/1.yml index 2d8e446802..8775ae154a 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-1/1.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-1/1.yml @@ -22,5 +22,5 @@ sections: - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.' - "Después de actualizar de la versión 3.0.x a la 3.1.x, en algunos casos, puede que GitHub actions falle con un error de tipo: `An unexpected error occurred when executing this workflow.` Para solucionar este problema, conéctate al shell administrativo (ssh) y ejecuta:\n```\nghe-actions-console -s actions -c \"Queue-ServiceJob -JobId 4DB1F4CF-19FD-40E0-A253-91288813DE8B\"\n```\n" - 'Cuando un nodo de réplica está fuera de línea en una configuración de disponibilidad alta, {% data variables.product.product_name %} aún podría enrutar las solicitudes a {% data variables.product.prodname_pages %} para el nodo fuera de línea, reduciendo la disponibilidad de {% data variables.product.prodname_pages %} para los usuarios.' - - '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.' + - '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-1/2.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/2.yml index 72ced088cc..b9e9fdc936 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-1/2.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-1/2.yml @@ -23,5 +23,5 @@ sections: ``` ghe-actions-console -s actions -c "Queue-ServiceJob -JobId 4DB1F4CF-19FD-40E0-A253-91288813DE8B" ``` - - 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. + - 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-1/3.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/3.yml index d503b21d80..fc56f5a520 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-1/3.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-1/3.yml @@ -1,21 +1,21 @@ date: '2021-07-14' sections: security_fixes: - - '**HIGH:** A path traversal vulnerability was identified in GitHub Enterprise Server that could be exploited when building a GitHub Pages site. User-controlled configuration options used by GitHub Pages were not sufficiently restricted and made it possible to read files on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.1.3 and has been assigned CVE-2021-22867. This vulnerability was reported via the GitHub Bug Bounty program.' + - '**ALTA:** Una vulnerabilidad que atravesaba rutas se identificó en GitHub Enterprise Server, la cual podría aprovecharse al crear un sitio de GitHub Pages. Las opciones de configuración que controla el usuario y que utiliza GitHub Pages no se restringieron suficientemente, lo cual hizo posible que se leyeran archivos en la instancia de GitHub Enterprise Server. Para aprovechar esta vulnerabilidad, el atacante necesitaría permiso para crear y compilar un sitio de GitHub Pages en la instancia de GitHub Enterprise Server. Esta vulnerabilidad afectó a todas las versiones de GitHub Enterprise Server anteriores a la 3.1.3 y se le asignó el CVE-2021-22867. Esta vulnerabilidad se reportó a través del programa de Recompensas por Errores de GitHub.' - 'Los paquetes se actualizaron a las últimas versiones de seguridad.' bugs: - - 'SAML expiration date variable was not configurable.' - - 'Application services would fail their health checks during config apply before they could enter a healthy state.' - - '`ghe-cluster-config-node-init` would fail during cluster setup if HTTP proxy is enabled.' - - 'Pre-receive hooks could encounter an error `Failed to resolve full path of the current executable` due to `/proc` not being mounted on the container.' - - 'Collectd would not resolve the forwarding destination hostname after the initial startup.' - - 'The job that purged stale deleted repositories could fail to make progress if some of those repositories were protected from deletion by legal holds.' - - 'Background jobs were being queued to the `spam` queue which were not being processed.' - - 'The preferred merge method would be reset when retrying after a failed PR merge.' - - 'Git pushes could result in a 500 Internal Server Error during the user reconciliation process on instances using LDAP authentication mode.' - - 'After upgrading from 3.0.x to 3.1.x, in some cases GitHub Actions would fail with an error: `An unexpected error occurred when executing this workflow.`' + - 'La variable de vencimiento de fecha de SAML no se pudo configurar.' + - 'Los servicios de aplicación fallaron en sus verificaciones de salud durante una aplicación de configuración antes de que pudieran ingresar a un estado saludable.' + - 'El `ghe-cluster-config-node-init` falló durante la configuración de clúster si se había habilitado el proxy de HTTP.' + - 'Los ganchos de pre-recepción pudieron haber encontrado un error de tipo `Failed to resolve full path of the current executable` debido a que un `/proc` no se pudo montar en el contenedor.' + - 'Collectd no resolvió el nombre de host destino que se estaba reenviando después del inicio principal.' + - 'El job que purgó los repositorios inactivos borrados pudo haber fallado en hacer progreso si alguno de estos repositorios estaba protegido contra borrado debido a las retenciones legales.' + - 'Los jobs en segundo plano se pusieron en la fila de `spam`, los cuales no se estaban procesando.' + - 'El método de fusión preferido se restablecerá cuando se reintente después de una fusión fallida de solicitud de cambio.' + - 'Las subidas de Git dieron como resultado un Error de Servidor Interno 500 durante el proceso de reconciliación del usuario en las instancias que utilizaban el modo de autenticación de LDAP.' + - 'Después de mejorar de la versión 3.0.x a la 3.1.x, en algunos casos, las GitHub Actions fallarían con un error de tipo `An unexpected error occurred when executing this workflow`.' changes: - - 'Improved the efficiency of config apply by skipping IP allow firewall rules that had not changed, which saved significant time on large clusters.' + - 'Se mejoró la eficiencia de la aplicación de configuraciones al omitir las reglas de cortafuegos para permitir IP, las cuales no hubieran cambiado, lo cual ahorró tiempo significativo en los clústeres grandes.' known_issues: - 'El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.' - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' @@ -23,5 +23,5 @@ sections: - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.' - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.' - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.' - - '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.' + - '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-1/4.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/4.yml index cf1717a5ba..de8f9915de 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-1/4.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-1/4.yml @@ -3,19 +3,19 @@ sections: security_fixes: - 'Los paquetes se actualizaron a las últimas versiones de seguridad.' bugs: - - 'The counts on packages pages were not being incremented when a package was downloaded.' - - '`ghe-config-apply` would timeout, ask for a prompt or fail for a customer that had {% data variables.product.prodname_secret_scanning %} enabled, and had either disabled or never enabled {% data variables.product.prodname_actions %} on their instance.' - - 'Log files were not reopened after rotation in some cases leading to high disk space usage on instances with high uptime.' - - 'Upgrade could fail from older version of {% data variables.product.prodname_ghe_server %} due to a missing job in {% data variables.product.prodname_actions %}.' - - 'Custom pre-receive hooks could lead to an error like `error: object directory /data/user/repositories/0/nw/12/34/56/7890/network.git/objects does not exist; check .git/objects/info/alternates`.' - - 'Unauthenticated HTTP proxy for the pages containers build was not supported for any users that use HTTP proxies.' - - 'A significant number of 503 errors were logged every time a user visited a repository''s `/settings` page if the dependency graph was not enabled.' - - 'Internal repositories were only returned when a user had affiliations with the repository through a team or through collaborator status, or queried with the `?type=internal` parameter.' - - 'Failed background jobs had unlimited retries which could cause large queue depths.' - - 'A significant number of 503 errors were being created if the scheduled job to sync vulnerabilities with GitHub.com attempted to run when dependency graph was not enabled and content analysis was enabled.' - - "When {% data variables.product.prodname_actions %} is enabled without running regular scheduled backups, the MSSQL transaction log could grow unbounded and can consume all available space on the appliance's data disk, causing a possible outage.\n\nIf you have configured regularly scheduled MSSQL backups, no further actions is required. Otherwise, if you have {% data variables.product.prodname_actions %} previously enabled, run the following commands after installing this patch.\n\n```\nghe-actions-console -s Mps -c 'Update-Service -Force'\nghe-actions-console -s Token -c 'Update-Service -Force'\nghe-actions-console -s Actions -c 'Update-Service -Force'\n```\n" + - 'Los conteos en las páginas de los paquetes no se estaban incrementando cuando se descargaba un paquete.' + - 'El tiempo de `ghe-config-apply` venció, pidió un mensaje o falló para un cliente que tenía habilitado el {% data variables.product.prodname_secret_scanning %} e inhabilitó o jamás habilitó las {% data variables.product.prodname_actions %} en su instancia.' + - 'Los archivos de bitácora no se volvieron a abrir después de su rotación en algunos casos, lo cual ocasionó un uso alto de espacio en disco en las instancias con tiempo de actividad alto.' + - 'Las actualizaciones desde una versión antigua de {% data variables.product.prodname_ghe_server %} podrían fallar debido a que falta un job en {% data variables.product.prodname_actions %}.' + - 'Los ganchos de pre-recepción personalizados podrían llevar a un error como `error: object directory /data/user/repositories/0/nw/12/34/56/7890/network.git/objects does not exist; check .git/objects/info/alternates`.' + - 'El proxy HTTP no autenticado para la compilación de contenedores de las páginas no era compatible para ningún usuario que utilizara proxys HTTP.' + - 'Una cantidad significativa de 503 errores se registró cada que un usuario vistió la página de `/settings` de un repositorio si la gráfica de dependencias no estaba habilitada.' + - 'Los repositorios internos solo se devolvieron cuando un usuario había tenido afiliaciones con el repositorio mediante un equipo o estado de colaborador o cuando se consultaron con el parámetro `?type=internal`.' + - 'Los jobs en segundo plano fallidos tienen reintentos ilimitados, los cuales podrían causar filas muy largas.' + - 'Una cantidad significativa de 503 errores se habrían estado creando si el job programado para sincronizar vulnerabilidades con GitHub.com intentó ejecutarse cuando la gráfica de dependencias no estuvo habilitada y el análisis de contenido sí estaba habilitado.' + - "Cuando se habilitan las {% data variables.product.prodname_actions %} sin ejecutar respaldos programados frecuentes, la bitácora de transacción de MSSQL podría crecer sin límites y consumir todo el espacio disponible en el disco de datos del aplicativo, ocasionando una posible interrupción.\n\nSi configuraste los respaldos programados frecuentes de MSSQL, no necesitas tomar ninguna acción adicional. De lo contrario, si tienes habilitadas las {% data variables.product.prodname_actions %} previamente, ejecuta los siguientes comandos después de instalar este parche.\n\n```\nghe-actions-console -s Mps -c 'Update-Service -Force'\nghe-actions-console -s Token -c 'Update-Service -Force'\nghe-actions-console -s Actions -c 'Update-Service -Force'\n```\n" changes: - - 'The logs for `babeld` now include a `cmd` field for HTTP ref advertisement requests instead of only including it during the negotiation requests.' + - 'Las bitácoras de `babeld` ahora incluyen un campo de `cmd` para las solicitudes de publicidad de ref de HTTP en vez de solo incluirlas durante las solicitudes de negociación.' known_issues: - 'El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.' - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' @@ -23,5 +23,5 @@ sections: - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.' - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.' - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.' - - '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.' + - '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-1/5.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/5.yml index f2332d0bdb..0f9489c330 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-1/5.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-1/5.yml @@ -1,14 +1,14 @@ date: '2021-08-10' sections: bugs: - - 'Custom pre-receive hooks that used a bash subshell would return an error: `No such file or directory`.' - - 'When GitHub Actions is enabled without running regular scheduled backups the MSSQL Transaction Log could grow unbounded and can consume all available space on the appliance''s Data Disk causing a possible outage.' - - 'Unnecessary database logging consumed a large amount of disk space on instances with heavy LFS usage.' - - 'Audit log entries for changes made to "Repository creation" organization settings were inaccurate.' - - 'Excessive logging of `ActionController::UnknownFormat` exceptions caused unnecessary disk usage.' - - 'LDAP `group_dn` values longer than 255 characters would result in errors being logged: `Data truncated for column ''group_dn'' at row 1`.' + - 'Los ganchos de pre-recepción que utilizaron un subshell de bash devolvieron un error de tipo: `No such file or directory`.' + - 'Cuando se habilitaron las GitHub Actions sin ejecutar los respaldos con programación frecuente, la bitácora de transacción de MSSQL pudo haber crecido más allá de los límites y consumido todo el espacio disponible en el disco de datos del aplicativo, causando una posible interrupción del servicio.' + - 'El registro innecesario en las bases de datos consumió una cantidad grande de espacio en disco en las instancias con un uso fuerte de LFS.' + - 'Las entradas de bitácoras de auditoría para los cambios realizados a los ajustes de organización de "Creación de repositorios" fueron inexactas.' + - 'El registro excesivo de las exepciones de `ActionController::UnknownFormat` causa un uso innecesario de disco.' + - 'Los valores de `group_dn` de LDAP de más de 255 caracteres dieron como resultado que los errores se registraran: `Datos truncados para la columna ''group_dn'' en la fila 1`.' changes: - - 'Abuse rate limits are now called Secondary rate limits, since the behavior they limit is not always abusive.' + - 'El abuso de límites de tasa ahora se llama Límites de tasa secundarios, ya que el comportamiento que limitan no siempre es abusivo.' known_issues: - 'El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.' - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' @@ -16,5 +16,5 @@ sections: - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.' - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.' - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.' - - '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.' + - '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-1/6.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/6.yml index fdfa76b2e5..f4972baae5 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-1/6.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-1/6.yml @@ -3,15 +3,15 @@ sections: security_fixes: - 'Los paquetes se actualizaron a las últimas versiones de seguridad.' bugs: - - 'Attaching very large images or animated GIFs to images or pull requests would fail.' - - 'Journald messages related to automatic updates (`Adding h/m/s random time.`) were logged to syslog.' - - 'Custom pre-receive hooks that created named pipes (FIFOs) would crash or hang, resulting in a timeout error.' - - 'Adding filters to the audit log advanced search page did not populate the query text box in real-time with the correct facet prefix and value.' - - 'Git hooks to the internal API that result in failing requests returned the exception `undefined method body for "success":String (NoMethodError)` instead of returning an explicit `nil`.' - - 'When an integration was removed, it was possible for an unrelated OAuth application or integration to also be removed.' - - 'When a mandatory message containing an emoji character was added, attempting to view or change the message would return a 500 Internal Server Error.' + - 'El agregar imágenes muy grandes o GIF animados a las imágenes o solicitudes de cambio, fallará.' + - 'Los mensajes de Journald con relación a las actualizaciones automáticas (`Agregar una hora aleatoria en h/m/s.`) se registraron en syslog.' + - 'Los ganchos de pre-recepción que crearon canalizaciones nombradas (FIFO) fallaron o demoraron, lo cual resultó en un error de tiempo de espera.' + - 'Agregar filtros para que la página de búsqueda avanzada de bitácoras de auditoría no llene la caja de texto de consultas en tiempo real con el valor y prefijo de faceta correcto.' + - 'Los ganchos de Git hacia la API interna que dio como resultado solicitudes fallidas devolvieron la excepción `undefined method body for "success":String (NoMethodError)` en vez de devolver un `nil` explícito.' + - 'Cuando se eliminó una integración, fue posible que una aplicación OAuth o integración no relacionada s también se eliminaran.' + - 'Cuando se agregó un mensaje obligatorio que contenía un caracter de emoji que intentaba ver o cambiar el mensaje, se devolvió un error tipo "500 Internal Server Error".' changes: - - 'Adds `triage` and `maintain` to the list of permissions returned by the REST API.' + - 'Agrega `triage` y `maintain` a la lista de permisos que devuelve la API de REST.' known_issues: - 'El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.' - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' @@ -19,5 +19,5 @@ sections: - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.' - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.' - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.' - - '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.' + - '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-1/7.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/7.yml index bdd16983d7..b595cb338f 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-1/7.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-1/7.yml @@ -3,10 +3,10 @@ sections: security_fixes: - 'Los paquetes se actualizaron a las últimas versiones de seguridad.' bugs: - - 'Attempting to tear down a newly-added replica node by specifying its UUID with `ghe-repl-teardown` would fail without reporting an error if replication was not started.' - - 'GitHub Pages builds were being passed through an external proxy if there was one configured.' - - 'Custom pre-receive hooks that created sub-processes would lack a `PATH` variable in their environment, resulting in "No such file or directory" errors.' - - 'MySQL could failover during an upgrade if `mysql-auto-failover` was enabled.' + - 'Intentar tirar un nodo de réplica recién agregado especificando su UUID con `ghe-repl-teardown` falló sin reportar un error en caos de que la replicación no hubiera iniciado.' + - 'Las compilaciones de GitHub Pages se estaban pasando por un proxy externo si es que había alguno configurada.' + - 'Los ganchos de pre-recepción que crearon subprocesos no tenían una variable de `PATH` en su ambiente, lo cual dio como resultado un error de tipo "No such file or directory".' + - 'MySQL pudo haberse recuperado de un desastre durante una mejora si se había habilitado `mysql-auto-failover`.' known_issues: - 'El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.' - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' @@ -14,5 +14,5 @@ sections: - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.' - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.' - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.' - - '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.' + - '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-1/8.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/8.yml new file mode 100644 index 0000000000..444f7895d2 --- /dev/null +++ b/translations/es-ES/data/release-notes/enterprise-server/3-1/8.yml @@ -0,0 +1,19 @@ +date: '2021-09-24' +sections: + security_fixes: + - '**ALTA:** Se identificó una vulnerabilidad de navegación de ruta en {% data variables.product.prodname_ghe_server %} que podría aprovecharse al crear un sitio de {% data variables.product.prodname_pages %}. Las opciones de configuración que controla el usuario y que utiliza {% data variables.product.prodname_pages %} no se restringieron lo suficiente e hicieron posible que se leyeran archivos en la instancia de {% data variables.product.prodname_ghe_server %}. Para aprovechar esta vulnerabilidad, los atacantes necesitarían permisos para crear y compilar un sitio de {% data variables.product.prodname_pages %} en la isntancia de {% data variables.product.prodname_ghe_server %}. Esta vulnerabilidad afectó a todas las versiones de {% data variables.product.prodname_ghe_server %} anteriores a la 3.1.8 y se corrigió en las versiones 3.1.8, 3.0.16 y 2.22.22. Este es el resultado de un arreglo incompleto para el CVE-2021-22867. Esta vulnerabilidad se reportó a través del Programa de Recompensas por Errores de GitHub y se le asignó el caso CVE-2021-22868. {% comment %} https://github.com/github/pages/pull/3361, https://github.com/github/pages/pull/3357 {% endcomment %}' + - '**MEDIA:** Una vulnerabilidad de control de accesos inadecuado en {% data variables.product.prodname_ghe_server %} permitió que un job de flujo de trabajo se ejecutara en un grupo de ejecutores auto-hospedados al cual no debería haber accedido. Esto afecta a los clientes que utilizan grupos de ejecutores auto-hospedados para el control de accesos. Un repositorio con acceso a un grupo de ejecutores empresariales podría acceder a todos los grupos de ejecutores empresariales dentro de la organización debido a las verificaciones de autenticación inadecuadas durante la solicitud. Esto podría ocasionar que se ejecutara código sin querer por parte del grupo de ejecutores incorrecto. Esta vulnerabilidad afectó a las versiones desde la 3.0.0 hasta la 3.0.15 y desde la 3.1.0 hasta la 3.1.7 de {% data variables.product.prodname_ghe_server %} y se corrigió en los lanzamientos 3.0.16 y 3.1.8. Se le asignó el caso CVE-2021-22869. {% comment %} https://github.com/github/enterprise2/pull/27013 {% endcomment %}' + bugs: + - 'Los conteos del trabajador de Resque se mostraron incorrectamente durante el modo de mantenimiento. {% comment %} https://github.com/github/enterprise2/pull/26899, https://github.com/github/enterprise2/pull/26883 {% endcomment %}' + - 'La memoria memcached asignada pudo haber sido cero en el modo de clústering. {% comment %} https://github.com/github/enterprise2/pull/26928, https://github.com/github/enterprise2/pull/26832 {% endcomment %}' + - 'Los archivos binarios no vacíos mostraron un tipo y tamaño de archivo incorrectos en la pestaña "Archivos" de una solicitud de cambios. {% comment %} https://github.com/github/github/pull/192810, https://github.com/github/github/pull/172284, https://github.com/github/coding/issues/694 {% endcomment %}' + - "Arregla compilaciones de las {% data variables.product.prodname_pages %} para que tomen en cuenta la configuración de NO_PROXY del aplicativo. Esto es relevante para los aplicativos configurados únicamente con un proxy HTTP. (actualización 2021-09-30) {% comment %} https://github.com/github/pages/pull/3360 {% endcomment %}\n \nsections -> bugs -> 2\nFile: 16.yml" + known_issues: + - 'El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.' + - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' + - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.' + - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.' + - 'Si se habilitan las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}, el desmontar un nodo de réplica con `ghe-repl-teardown` tendrá éxito, pero podría devolver un `ERROR:Running migrations`.' + - 'Los límites de recursos que son específicos para procesar ganchos de pre-recepción podrían ocasionar que fallen algunos ganchos de pre-recepción.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/0-rc1.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/0-rc1.yml index cc02d8607e..b9ec151a93 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-2/0-rc1.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-2/0-rc1.yml @@ -1,99 +1,99 @@ date: '2021-09-09' release_candidate: true -deprecated: false +deprecated: true intro: 'Si {% data variables.product.product_location %} está ejecutando una compilación candidata a lanzamiento, no puedes mejorarla con un hotpatch. Te recomendamos que solo ejecutes candidatos a lanzamiento en ambientes de prueba.' sections: features: - - heading: 'Custom patterns for secret scanning' + - heading: 'Patrones personalizados para el escaneo de secretos' notes: - - "{% data variables.product.prodname_GH_advanced_security %} customers can now specify custom patterns for secret scanning. When a new pattern is specified, secret scanning searches a repository's entire Git history for the pattern, as well as any new commits.\n\nUser defined patterns are in beta for {% data variables.product.prodname_ghe_server %} 3.2. They can be defined at the repository, organization, and enterprise levels. For more information, see \"[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning).\"\n" - - heading: 'Security overview for Advanced Security (beta)' + - "Los clientes de {% data variables.product.prodname_GH_advanced_security %} ahora pueden especificar los patrones para el escaneo de secretos. Cuando se especifica un patrón nuevo, el escaneo de secretos busca dicho patrón en todo el historial de Git del repositorio, así como cualquier confirmación nueva.\n\nLos patrones definidos por los usuarios se encuentran en beta para {% data variables.product.prodname_ghe_server %} 3.2. Se pueden definir a nivel de repositorio, organización y empresa. Para obtener más información, consulta la sección \"[Definir patrones personalizados para el escaneo de secretos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)\".\n" + - heading: 'Resumen de seguridad para la Seguridad Avanzada (beta)' notes: - "Los clientes de la {% data variables.product.prodname_GH_advanced_security %} ahora tienen una vista de nivel de organización apra los riegos de seguridad de las aplicaciones que detecte el {% data variables.product.prodname_code_scanning %}, el {% data variables.product.prodname_dependabot %} y el {% data variables.product.prodname_secret_scanning %}. El resumen de seguridad muestra la habilitación de estado de las características de seguridad en cada repositorio, así como la cantidad de alertas que se detectan.\n\nAdicionalmente, el resumen de seguridad lista todas las alertas del {% data variables.product.prodname_secret_scanning %} a nivel organizacional. Tendremos vistas similares para el {% data variables.product.prodname_dependabot %} y el {% data variables.product.prodname_code_scanning %} en los lanzamientos futuros cercanos. Para obtener más información, consulta la sección \"[Acerca del resumen de seguridad](/code-security/security-overview/about-the-security-overview)\".\n\n![Captura de pantalla del resumen de seguridad](/assets/images/enterprise/3.2/release-notes/security-overview-UI.png)\n" - - heading: 'Dependency review (beta)' + - heading: 'Revisión de dependencias (beta)' notes: - - "{% data variables.product.prodname_GH_advanced_security %} customers can now see a rich diff of the dependencies changed in a pull request. 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 these dependencies. 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).\"\n" - - heading: 'GitHub Actions environments' + - "Los clientes de {% data variables.product.prodname_GH_advanced_security %} ahora pueden ver un diff enriquecido de las dependencias que cambiaron en una solicitud de cambios. La revisión de dependencias proporciona una vista fácil de entender de los cambios a las dependencias y de su impacto de seguridad en la pestaña de \"Archivos que cambiaron\" de las solicitudes de cambios. Esta te informa de las dependencias que se agregaron, eliminaron o actualizaron junto con la información de vulnerabilidades de estas dependencias. Para obtener más información, consulta la sección \"[Revisar los cambios de dependencias en una solicitud de cambios](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)\".\n" + - heading: 'Ambientes de GitHub Actions' notes: - - "Environments, environment protection rules, and environment secrets are now generally available for {% data variables.product.prodname_actions %} on {% data variables.product.product_name %}. For more information, see \"[Environments](/actions/reference/environments).\"\n\n![Environment protection rules](/assets/images/enterprise/3.2/release-notes/actions-environments.png)\n" - - heading: 'SSH authentication with security keys' + - "Los ambientes, las reglas de protección de ambiente y los secretos de ambiente ahora están disponibles en general para las {% data variables.product.prodname_actions %} en {% data variables.product.product_name %}. Para obtener más información, consulta la sección \"[Environments](/actions/reference/environments)\".\n" + - heading: 'Autenticación por SSH con llaves seguras' notes: - - "SSH authentication using a FIDO2 security key is now supported when you add a `sk-ecdsa-sha2-nistp256@openssh.com` or `sk-ssh-ed25519@openssh.com` SSH key to your account. SSH security keys store secret key material on a separate hardware device that requires verification, such as a tap, to operate. For more information, see \"[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key).\"\n" - - heading: 'Dark and dark dimmed themes' + - "Ahora es compatible la autenticación por SSH utilizando una llave de seguridad FIDO2 cuando agregas una llave SSH de tipo `sk-ecdsa-sha2-nistp256@openssh.com` o `sk-ssh-ed25519@openssh.com` a tu cuenta. Las llaves de seguridad SSH almacenan material de llaves secretas en un dispositivo de hardware por separado, el cual requiere de verificación, tal como un tap, para operar. Para obtener más información, consulta la sección \"[Generar una clave SSH nueva y agregarla al ssh-agent](/github/authenticating-to-github/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)\".\n" + - heading: 'Temas oscuro y oscuro atenuado' notes: - - "Dark and dark dimmed themes are now available for the web UI. {% data variables.product.product_name %} will match your system preferences when you haven't set theme preferences in {% data variables.product.product_name %}. You can also choose which themes are active during the day and night. For more information, see \"[Managing your theme settings](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings).\"\n\n![Dark and dark dimmed themes](https://user-images.githubusercontent.com/33528647/114629560-d2231f80-9c86-11eb-9bde-cc301a97040d.gif)\n" - - heading: 'Approving unverified domains for email notifications' + - "Ahora hay temas oscuro y opaco oscuro disponibles para la IU web. {% data variables.product.product_name %} empatará las preferencias de tu sistema si no has configurado las preferencias de tema en {% data variables.product.product_name %}. También puedes elegir qué temas estarán activos durante el día y la noche. Para obtener más información, consulta la sección \"[Administrar la configuración de tu tema](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)\".\n\n![Temas oscuro y opaco oscuro](https://user-images.githubusercontent.com/33528647/114629560-d2231f80-9c86-11eb-9bde-cc301a97040d.gif)\n" + - heading: 'Aprobar dominios no verificados para las notificaciones de correo electrónico' notes: - 'Los dominios que no se pueden verificar ahora pueden aprobarse para el enrutamiento de notificaciones por correo electrónico. Los propietarios de empresas y organizaciones podrán aprobar dominios y aumentar su política de restricción de notificaciones por correo electrónico automáticamente, lo cual permitirá que las notificaciones se envíen a los colaboradores, consultores, adquisiciones o a otros socios. para obtener más información, consulta las secciones "[Verificar o aprobar un dominio para tu empresa](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#about-approval-of-domains)" y "[Restringir las notificaciones por correo electrónico para tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise#restricting-email-notifications-for-your-enterprise-account)."' - - heading: 'Git Credential Manager (GCM) secure credential storage and multi-factor authentication support' + - heading: 'Soporte para el almacenamiento de credenciales seguro del Administrador de Credenciales de Git (GCM) y autenticación multifactorial' notes: - "Las versiones 2.0.452 y posteriores del Administrador de Credenciales de Git (GCM) Core ahora proporcionan compatibilidad de almacenamiento de credenciales con seguridad fortalecida y autenticación multifactorial para {% data variables.product.product_name %}.\n\nEl GCM Core con compatibilidad para {% data variables.product.product_name %} se incluye con [Git para Windows](https://gitforwindows.org) en sus versiones 2.32 y posterior. GCM Core no se incluye con Git para macOS o para Linux, pero puede instalarse por separado. Para obtener más información, consulta el [lanzamiento más reciente](https://github.com/microsoft/Git-Credential-Manager-Core/releases/) y las [instrucciones de instalación](https://github.com/microsoft/Git-Credential-Manager-Core/releases/) en el repositorio `microsoft/Git-Credential-Manager-Core`.\n" changes: - heading: 'Cambios en la administración' notes: - - 'A ''User Agent Referrer Policy'' setting has been added to the enterprise settings. This allows an admin to set a stricter `Referrer-Policy` to hide the hostname of a {% data variables.product.prodname_ghe_server %} installation from external sites. The setting is disabled by default and is tracked by audit log events for staff and enterprise owners when enabled or disabled. For more information, see "[Configuring Referrer Policy for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)."' - - 'The MySQL health check was changed to use `mysqladmin ping` instead of TCP checks, which removes some unnecessary noise in the MySQL error log. Also, Orchestrator failover checks were improved to prevent unnecessary MySQL failovers when applying cluster config changes.' - - 'The Resque service, which supports background job processing, has been replaced with Aqueduct Lite. This change makes the job system easier to manage and should not affect the user experience. For the new administration and debugging commands for Aqueduct, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-aqueduct)."' - - heading: 'Token Changes' + - 'Se agregó un ajuste de "Política de Referente de Agente Usuario" a la configuración empresarial. Esto permite que un administrador configure una "Política de referente" más estricta para ocultar el nombre de host de una instalación de {% data variables.product.prodname_ghe_server %} de sitios externos. Este ajuste se encuentra inhabilitado predeterminadamente y los eventos de bitácoras de auditoría lo rastrean para los propietarios empresariales y el personal de las empresas cuando se habilita o inhabilita. Para obtener más información, consulta la sección "[Configurar la Política de Referente en tu empresa](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)".' + - 'La revisión de salud de MySQL se cambió al uso de `mysqladmin ping` en vez de las verificaciones de TCP, lo cual elimina algo del ruido innecesario en la bitácora de errores de MySQL, las verificaciones de recuperación de fallos del orquestador se mejoraron para prevenir las recuperaciones de fallos de MySQL innecesarias al aplicar cambios de configuración del clúster.' + - 'El servicio Resque, el cual da la compatibilidad con procesamiento de jobs en segundo plano, se reemplazó con Aqueduct Lite. este cambio hace que el sistema de jobs se pueda administrar más fácilmente y no debería afectar la experiencia del usuario. Para la administración y comandos de depuración nuevas de Aqueduct, consulta la sección "[Utilidades de la línea de comandos](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-aqueduct)".' + - heading: 'Cambios de Token' notes: - "El formato de tokens de autenticación para {% data variables.product.product_name %} ha cambiado,. Dicho cambio afecta el formato de los tokens de acceso personal y de los tokens de acceso para las {% data variables.product.prodname_oauth_apps %}, así como de los tokens de usuario a servidor, de servidor a servidor y de actualización para {% data variables.product.prodname_github_apps %}.\n\nLos diferentes tipos de token ahora tienen prefijos identificables únicos, los cuales permiten que el escaneo de secretos detecten los tokens para que puedas mitigar el impacto de que alguien confirme un token accidentalmente en un repositorio. {% data variables.product.company_short %} recomienda actualizar los tokens existentes tan pronto como te sea posible. Para obtener más información, consulta las secciones \"[Acerca de la autenticación en {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github#githubs-token-formats)\" y \"[Acerca del {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)\".\n" - - heading: 'Repositories changes' + - heading: 'Cambios de repositorios' notes: - - 'Repositories on user profiles and organization profiles now support sorting by star count.' - - 'When viewing the commit history of a single file, you can now click {% octicon "file-code" aria-label="The code icon" %} to view that file at the selected point in history.' + - 'Los repositorios en los perfiles de usuario y en los perfiles de organización ahora son compatibles con la clasificación por conteo de estrellas.' + - 'Cuando veas el historial de confirmación de un archivo único, ahora puedes hacer clic en {% octicon "file-code" aria-label="The code icon" %} para ver dicho archivo en algún punto selecto del historial.' - 'Cuando un submódulo se define con una ruta relativa en {% data variables.product.product_location %}, el submódulo ahora se puede hacer clic en la interfaz web. Al hacer clic en el submódulo de la interfaz web le llevará al repositorio enlazado. Anteriormente, sólo los submódulos con URLs absolutas podían hacer clic. Esto es soportado para rutas relativas para los repositorios con el mismo propietario que siguen el patrón ..REPOSITORY o rutas relativas de repositorios con un propietario diferente que siga el patrón ../OWNER/REPOSITORY. Para obtener más información sobre cómo trabajar con submódulos, consulta la sección [Trabajar con submódulos](https://github.blog/2016-02-01-working-with-submodules/) en {% data variables.product.prodname_blog %}.' - - 'The web UI can now be used to synchronize an out-of-date branch of a fork with the fork''s upstream branch. If there are no merge conflicts between the branches, the branch is updated either by fast-forwarding or by merging from upstream. If there are conflicts, you will be prompted to create a pull request to resolve the conflicts. For more information, see "[Syncing a fork](/github/collaborating-with-pull-requests/working-with-forks/syncing-a-fork#syncing-a-fork-from-the-web-ui)."' - - heading: 'Markdown changes' + - 'La IU web ahora puede utilizarse para sincronizar una rama desactualizada de una bifurcación con la rama ascendente de dicha bifurcación. Si no hay conflictos de fusión entre las ramas, la rama se actualizará ya sea mediante un envío rápido o mediante la fusión desde la parte ascendente. Si hay conflictos, se te pedirá crear una solicitud de cambios para resolverlos. Para obtener más información, consulta la sección "[Sincronizar una bifurcación](/github/collaborating-with-pull-requests/working-with-forks/syncing-a-fork#syncing-a-fork-from-the-web-ui)".' + - heading: 'Cambios en el Lenguaje de Marcado' notes: - - 'The markdown editor used when creating or editing a release in a repository now has a text-editing toolbar. For more information, see "[Managing releases in a repository](/github/administering-a-repository/releasing-projects-on-github/managing-releases-in-a-repository#creating-a-release)."' - - 'Uploading video files is now supported everywhere you write Markdown on {% data variables.product.product_name %}. Share demos, reproduction steps, and more in your issue and pull request comments, as well as in Markdown files within repositories, such as READMEs. For more information, see "[Attaching files](/github/writing-on-github/working-with-advanced-formatting/attaching-files)."' - - 'Markdown files will now automatically generate a table of contents in the header when there are 2 or more headings. The table of contents is interactive and links to the selected section. All 6 Markdown heading levels are supported.' - - 'There is a new keyboard shortcut, `cmd+e` on macOS or `ctrl+e` on Windows, to insert codeblocks in Markdown files, issues, pull requests, and comments.' - - 'Appending `?plain=1` to the URL for any Markdown file will now display the file without rendering and with line numbers. The plain view can be used to link other users to specific lines. For example, appending `?plain=1#L52` will highlight line 52 of a plain text Markdown file. For more information, "[Creating a permanent link to a code snippet](/github/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet#linking-to-markdown)."' - - heading: 'Issues and pull requests changes' + - 'El editor de lenguaje de marcado que se utiliza al crear o editar un lanzamiento en un repositorio ahora tiene una barra de herramientas para edición de texto. Para obtener más información, consulta la sección "[Adminsitrar los lanzamientos en un repositorio](/github/administering-a-repository/releasing-projects-on-github/managing-releases-in-a-repository#creating-a-release)".' + - '{% data variables.product.product_name %} ahora tiene compatibilidad para cargar archivos de video en donde sea que utilices lenguaje de marcado. Comparte demostraciones, pasos de reproducción y más en los comentarios de tus propuestas y solicitudes de cambio, así como en los archivos de lenguaje de marcado dentro de los repositorios, tales como los README. Para obtener más información, consulta la sección "[Adjuntar archivos](/github/writing-on-github/working-with-advanced-formatting/attaching-files)".' + - 'Los archivos de lenguaje de marcado ahora generarán una tabla de contenido automáticamente en el encabezado cuando haya 2 o más encabezados. La tabla de contenido es interactiva y enlaza a la sección seleccionada. Los 6 niveles de encabezado del lenguaje de marcado son compatibles.' + - 'Hay un atajo de teclado nuevo, `cmd+e` en macOS o `ctrl+e` en Windows, para insertar bloques de código en los archivos, propuestas, solicitudes de cambio y comentarios de Lenguaje de Marcado.' + - 'El agregar `?plain=1` a la URL en cualquier archivo de lenguaje de marcado ahora mostrará al archivo sin procesar y con números de línea. La vista simple puede utilizarse para enlazar a otros usuarios a líneas específicas. Por ejemplo, el agregar `?plain=1#L52` resaltará la línea 52 del archivo de marcado en texto simple. Para obtener más información, consulta la sección "[Crear un enlace permanente a un fragmento de código](/github/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet#linking-to-markdown)".' + - heading: 'Cambios en propuestas y sollicitudes de cambio' notes: - - 'With the [latest version of Octicons](https://github.com/primer/octicons/releases), the states of issues and pull requests are now more visually distinct so you can scan their status more easily. For more information, see [{% data variables.product.prodname_blog %}](https://github.blog/changelog/2021-06-08-new-issue-and-pull-request-state-icons/).' - - 'A new "Require conversation resolution before merging" branch protection rule and "Conversations" menu is now available. Easily discover your pull request comments from the "Files changed" tab, and require that all your pull request conversations are resolved before merging. For more information, see "[About pull request reviews](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews#discovering-and-navigating-conversations)" and "[About protected branches](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-conversation-resolution-before-merging)."' + - 'Con la [versión más reciente de Octicons](https://github.com/primer/octicons/releases), los estados de las propuestas y solicitudes de cambios ahora son más fáciles de distinguir visualmente para que puedas escanear los estados de forma más sencilla. Para obtener más información consulta la sección [{% data variables.product.prodname_blog %}](https://github.blog/changelog/2021-06-08-new-issue-and-pull-request-state-icons/).' + - 'Ahora tenemos disponible una regla de protección de rama de "Requerir la resolución de la conversación antes de fusionar" y un menú de "Conversaciones". Descubre fácilmente tus comentarios de solicitudes de cambios desde la pestaña de "Archivos que cambiaron" y requiere qeu todas tus conversaciones en solicitudes de cambio se resuelvan antes de fusionarse. Para obtener más información, consulta las secciones "[Acerca de las revisiones de solicitudes de cambio](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews#discovering-and-navigating-conversations)" y "[Acerca de las ramas protegidas](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-conversation-resolution-before-merging)".' - 'Para prevenir la fusión de cambios inesperados después de habilitar la fusión automática para una solicitud de cambios, ahora se inhabilitó esta opción automáticamente cuando un usuario sin acceso de escritura al repositorio sube estos cambios. Los usuarios que no tengan permisos de escritura aún pueden actualizar la solicitud de cambios con aquellos de la rama base cuando se habilita la fusión automática. Para prevenir que un usuario malintencionado utilice un conflicto de fusión para introducir cambios inesperados a la solicitud de cambios, la fusión automática para la solicitud de cambios se encuentra inhabilitada si dicha actualización causa un conflicto de fusión. Para obtener más información sobre la fusión automática, consulta la sección "[Fusionar una solicitud de cambios automáticamente](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)".' - 'Las personas con permisos de mantenimiento ahora pueden administrar el ajuste de "Permitir la fusión automática" a nivel de repositorio. Este ajuste, el cual a menudo se encuentra inhabilitado, controla si la fusión automática está disponible para las solicitudes de cambios en el repositorio., Anteriormente, solo las personas con permisos administrativos podían administrar este ajuste. Adicionalmente, este ajuste ahora puede controlarse utilizando las API de REST para "[Crear repositorio](/rest/reference/repos#create-an-organization-repository)" y "[Actualizar repositorio](/rest/reference/repos#update-a-repository)". Para obtener más información, consulta la sección "[Administrar la fusión automática para las solicitudes de cambios en tu repositorio]](/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.' - - 'When a review is requested from a team of more than 100 people, developers are now shown a confirmation dialog box in order to prevent unnecessary notifications for large teams.' - - 'Back-tick `code blocks` are now supported in issue titles, pull request titles, and in any place issue and pull request titles are referenced in {% data variables.product.prodname_ghe_server %}.' + - 'La selección de propuestas y solicitudes de cambio de los asignados ahora es compatible con la búsqueda de escritura anticipada, así que puedes encontrar usuarios en tu organización más rápidamente. Adicionalmente, las clasificaciones de resultados de búsqueda se actualizaron para preferir las coincidencias al inicio del nombre de usuario de una persona o nombre de perfil.' + - 'Cuando se solicita una revisión de un equipo de más de 100 personas, los desarrolladores ahora muestran una caja de diálogo de confirmación para poder prevenir las notificaciones innecesarias para los equipos grandes.' + - 'Ahora hay compatibilidad con tener `code blocks` con comilla inversa en los títulos de las propuestas y en cualquier lugar en el que se referencien propuestas y solicitudes de cambios en {% data variables.product.prodname_ghe_server %}.' - 'Los eventos para las solicitudes de cambios y revisiones de solicitudes de cambios ahora se incluyen en la bitácora de auditoría tanto para [enterprises](/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise) como para [organizations](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization). estos eventos ayudan a que los administradores monitoreen mejor la actividad de las solicitudes de cambios y ayuden a garantizar que se cumplan los requisitos de seguridad y cumplimiento. Los eventos pueden verse desde la IU web, exportarse como CSV o JSON o acceder a ellos a través de la API de REST. También puedes buscar la bitácora de auditoría para los eventos de solicitudes de cambio específicos. Para obtener más información, consulta la sección "[Revisar la bitácora de auditoría para tu organización](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#pull_request-category-actions)".' - - heading: 'Branches changes' + - heading: 'Cambios a las ramas' notes: - "El nombre de rama predeterminado para los repositorios nuevos ahora es `main`. Los repositorios existentes no se verán impactados por este cambio. Si los usuarios, propietarios de organizaciones o propietarios de empresas ya especificaron una rama predeterminada para repositorios nuevos anteriormente, tampoco se les impactará.\n\nSi quieres configurar un nombre de rama predeterminada diferente, puedes hacerlo en los ajustes de [user](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories), [organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization), o [enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name).\n" - "Las ramas, incluyendo a la predeterminada, ahora pueden volver a nombrarse utilizando la IU web de {% data variables.product.product_name %}. Cuando una rama se vuelve a nombrar, cualquier solicitud de cambios abierta y lanzamiento de borrador que apunten a la rama que se volvió a nombrar se redirigirá automáticamente y las reglas de protección de rama que referencien explícitamente a la rama que se volvió a nombrar se actualizarán.\n\nSe requieren permisos administrativos para volver a nombrar la rama predeterminada, pero es suficiente contar con permisos de escritura para volver a nombrar otras ramas.\n\nPara ayudar a hacer el cambio con tanta continuidad como sea posible para los usuarios:\n\n* Se muestra un aviso a los contribuyentes, mantenedores y administradores de la página de inicio del repositorio, el cual contiene instrucciones para actualizar su repositorio local.\n*Las solicitudes web para la rama antigua se redireccionarán.\n* Se devolverá una respuesta HTTP de \"se movió permanentemente\" a todo llamado de la API de REST.\n* Se mostrará un mensaje informativo para los usuarios de la línea de comandos de Git que suban información a la rama antigua.\n\nPara obtener más información, consulta la sección \"[Volver a nombrar una rama](/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch)\".\n" - - heading: 'GitHub Actions changes' + - heading: 'Cambioas a las GitHub Actions' notes: - 'Las {% data variables.product.prodname_actions %} ahora te permiten controlar los permisos que se otorgan al secreto del `GITHUB_TOKEN`. El `GITHUB_TOKEN` es un secreto que se genera automáticamente y te permite hacer llamados autenticados a la API de {% data variables.product.product_name %} en tus ejecuciones de flujo de trabajo. Las {% data variables.product.prodname_actions %} generan un token nuevo para cada job y hacen que el token venza cuando se completa el job. El token a menudo tiene permisos de `escritura` para varias [Terminales de la API](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token), con excepción de los casos de las solicitudes de cambios de las bifurcaciones, los cuales siempre se marcan como de `lectura`. Estos ajustes nuevos te permiten seguir el principio de los menores privilegios necesarios en tus flujos de trabajo,. Para obtener más información, consulta la sección "[Autenticación en un flujo de trabajo](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token)".' - - '{% data variables.product.prodname_cli %} 1.9 and later allows you to work with {% data variables.product.prodname_actions %} in your terminal. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-04-15-github-cli-1-9-enables-you-to-work-with-github-actions-from-your-terminal/).' - - 'The audit log now includes events associated with {% data variables.product.prodname_actions %} workflow runs. This data provides administrators with a greatly expanded data set for security and compliance audits. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#workflows-category-actions)."' - - 'Performance improvements have been made to {% data variables.product.prodname_actions %}, which may result in higher maximum job throughput. For more information on job throughput with internally-tested 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)."' - - heading: 'GitHub Packages changes' + - 'El {% data variables.product.prodname_cli %} 1.9 y posterior te permiten trabajar con las {% data variables.product.prodname_actions %} en tu terminal. Para obtener más información, consulta la sección [Registro de cambios de {% data variables.product.prodname_dotcom %}](https://github.blog/changelog/2021-04-15-github-cli-1-9-enables-you-to-work-with-github-actions-from-your-terminal/).' + - 'La bitácora de auditoría ahora incluye eventos asociados con las ejecuciones de flujo de trabajo de {% data variables.product.prodname_actions %}. Estos datos proporcionan un conjunto de datos ampliamente expandidos para los administradores, así como auditorías de cumplimiento. Para obtener más información, consulta la sección "[Revisar la bitácora de auditoría de tu organización](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#workflows-category-actions)".' + - 'Se hicieron mejoras de rendimiento a {% data variables.product.prodname_actions %}, lo cual podría dar como resultado una capacidad de procesamiento de jobs máxima más alta. Para obtener más información sobre la capacidad de procesamiento de los jobs con configuraciones de CPU y memoria probadas internamente, consulta la sección "[Iniciar con {% data variables.product.prodname_actions %} para {% 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)".' + - heading: 'Cambios a los GitHub packages' notes: - - 'Any package or package version for {% data variables.product.prodname_registry %} can now be deleted from {% data variables.product.product_name %}''s web UI. You can also undo the deletion of any package or package version within 30 days. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)".' - - heading: 'Dependabot and Dependency graph changes' + - 'Cualquier paquete o versión de paquete del {% data variables.product.prodname_registry %} ahora se puede borrar de la IU web de {% data variables.product.product_name %}. También puedes deshacer el borrado de cualquier paquete o versión de paquete dentro de los primeros 30 días. Para obtener más información, consulta la sección "[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)".' + - heading: 'Cambios al Dependabot y a la gráfica de Dependencias' notes: - - 'The dependency graph can now be enabled using the Management Console, rather than needing to run a command in the administrative shell. For more information, see "[Enabling alerts for vulnerable dependencies {% data variables.product.prodname_ghe_server %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server#enabling-the-dependency-graph-and-dependabot-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."' - - 'Notifications for multiple {% data variables.product.prodname_dependabot_alerts %} are now grouped together if they''re discovered at the same time. This significantly reduces the volume of {% data variables.product.prodname_dependabot %} alert notifications that users receive. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-03-18-grouped-dependabot-alert-notifications/).' - - 'Dependency graph and {% data variables.product.prodname_dependabot_alerts %} now support Go modules. {% data variables.product.prodname_ghe_server %} analyzes a repository''s `go.mod` files to understand the repository’s dependencies. Along with security advisories, the dependency graph provides the information needed to alert developers to vulnerable dependencies. For more information about enabling the dependency graph on private repositories, see "[Securing your repository](/code-security/getting-started/securing-your-repository#managing-the-dependency-graph)."' + - 'La gráfica de dependencias ahora puede habilitarse utilizando la Consola de Administración en vez de necesitar la ejecución de un comando en el shell administrativo. Para obtener más información, consulta la sección "[Habilitar las alertas para las dependencias vulnerables de {% data variables.product.prodname_ghe_server %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server#enabling-the-dependency-graph-and-dependabot-alerts-for-vulnerable-dependencies-on-github-enterprise-server)".' + - 'Ahora, las notificaciones para {% data variables.product.prodname_dependabot_alerts %} múltiples se agrupan si se descubren al mismo tiempo. Esto reduce significativamente el volumen de notificaciones de alertas del {% data variables.product.prodname_dependabot %} que reciben los usuarios. Para obtener más información, consulta la sección [Registro de cambios de {% data variables.product.prodname_dotcom %}](https://github.blog/changelog/2021-03-18-grouped-dependabot-alert-notifications/).' + - 'Las gráficas de dependencias y {% data variables.product.prodname_dependabot_alerts %} ahora son compatibles con los módulos de Go. {% data variables.product.prodname_ghe_server %} analiza los archivos de `go.mod` de un repositorio para entender las dependencias del mismo. En conjunto con las asesorías de seguridad, la gráfica de dependencias proporciona la información necesaria para alertar a los desarrolladores sobre las dependencias vulnerables. Para obtener más información sobre cómo habilitar la gráfica de dependencias en los repositorios privados, consulta la sección "[Asegurar tu repositorio](/code-security/getting-started/securing-your-repository#managing-the-dependency-graph)".' - 'Los ajustes de notificación predeterminados para las alertas de seguridad han cambiado. Anteriormente, si tenías permiso para ver las alertas de seguridad en un repositorio, hubieras recibido las notificaciones de dicho repositorio mientras tu configuración permitiera las notificaciones de alertas de seguridad. Ahora debes decidir unirte a las notificaciones de alertas de seguridad observando el repositorio. Se te notificará si seleccionas `Toda la actividad` o si configuras `Personalizado` para incluir las `Alertas de seguridad`. Todos los repositorios existentes se migrarán automáticamente a estos ajustes nuevos y seguirás recibiendo notificaciones; sin embargo, cualquier repositorio nuevo requerirá que decidas unirte observando el repositorio. Para obtener más información, consulta las secciones "[Configurar notificaciones para las dependencias vulnerables](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies)" y "[Administrar las alertas del escaneo de secretos](/code-security/secret-security/managing-alerts-from-secret-scanning)".' - - heading: 'Code scanning and secret scanning changes' + - heading: 'Cambios al escaneo de código y de secretos' notes: - 'El {% data variables.product.prodname_code_scanning_capc %} con {% data variables.product.prodname_codeql %} ahora genera información diagnóstica para todos los lenguajes compatibles. Esto ayuda a mantener el estado de la base de datos creada para entender el estado y calidad del análisis que se realizó. La información diagnóstica se encuentra disponible desde la [versión 2.5.6](https://github.com/github/codeql-cli-binaries/releases) del {% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/). Puedes ver esta información diagnóstica detallada en las bitácoras para {% data variables.product.prodname_codeql %} de las {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Visualizar las bitácoras de escaneo de código](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs)".' - 'El {% data variables.product.prodname_code_scanning_capc %} con {% data variables.product.prodname_codeql_cli %} ahora es compatible con el análisis de diversos lenguajes durante una compilación sencilla. Esto facilita el ejecutar análisis de código para utilizar sistemas de IC/DC diferentes a los de las {% data variables.product.prodname_actions %}. El modo nuevo del comando `codeql database create` se encuentra disponible desde la [versión 2.5.6] (https://github.com/github/codeql-cli-binaries/releases) del [{% data variables.product.prodname_codeql_cli %}] (https://codeql.github.com/docs/codeql-cli/). Para obtener más información sobre cómo configurar esto, consulta la sección "[Instalar el {% data variables.product.prodname_codeql_cli %} en tu sistema de IC](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-cli-in-your-ci-system)".' - - '{% data variables.product.prodname_code_scanning_capc %} alerts from all enabled tools are now shown in one consolidated list, so that you can easily prioritize across all alerts. You can view alerts from a specific tool by using the "Tool" filter, and the "Rule" and "Tag" filters will dynamically update based on your "Tool" selection.' - - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} now includes beta support for analyzing C++20 code. This is only available when building codebases with GCC on Linux. C++20 modules are not supported yet.' + - 'Las alertas de {% data variables.product.prodname_code_scanning_capc %} de todas las herramientas habilitadas ahora se muestran en una lista consolidada para que puedas priorizar fácilmente entre todas ellas. Puedes ver las alertas desde una herramienta específica utilizando le filtro de "Herramienta" y los de "Regla" y "Etiqueta" se actualizarán dinámicamente con base en tu selección de "Herramientas".' + - 'El {% data variables.product.prodname_code_scanning_capc %} cib {% data variables.product.prodname_codeql %} ahora incluye soporte beta para analizar código de C++20. Esto solo está disponible cuando creas bases de código con GCC en Linux. Los módulos de C++20 aún no son compatibles.' - 'La profundidad del análisis de {% data variables.product.prodname_codeql %} se mejoró al agregar compatibilidad para más [librerías y marcos de trabajo](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) y al incrementar la cobertura de nuestros modelos de marcos de trabajo y librerías para varios lenguajes ({C++](https://github.com/github/codeql/tree/main/cpp), [JavaScript](https://github.com/github/codeql/tree/main/javascript), [Python](https://github.com/github/codeql/tree/main/python), y [Java](https://github.com/github/codeql/tree/main/java)). Como resultado, el {% data variables.product.prodname_codeql %} ahora puede detectar aún más fuentes potenciales de datos de usuarios no confiables, revisar los pasos a través de los cuales fluyen los datos e identificar hundimientos potencialmente peligrosos en los cuales podrían terminar estos datos,. Esto da como resultado una mejora general de la calidad de las alertas del {% data variables.product.prodname_code_scanning %}. Para obtener más información, consulta la sección de [registro de cambios de {% data variables.product.prodname_dotcom %}](https://github.blog/changelog/2021-07-01-codeql-code-scanning-now-recognizes-more-sources-and-uses-of-untrusted-user-data/).' - "El {% data variables.product.prodname_code_scanning_capc %} ahora muestra niveles de `gravedad de seguridad` para las alertas del Code QL. Puedes configurar qué niveles de `gravedad de seguridad` ocasionarán un fallo de verificación para una solicitud de cambios. El nivel de gravedad de las alertas de seguridad puede ser `crítico`, `alto, `medio` o `bajo`. Predeterminadamente, cualquier alerta del {% data variables.product.prodname_code_scanning %} con un `nivel de gravedad` que sea `crítico` o `alto` ocasionará que una solicitud de cambios falle.\n\nAdicionalmetnte, ahora también puedes configurar qué niveles de gravedad ocasionarán que la verificación de solicitudes de cambio falle para las alertas que no sean de seguridad. Puedes configurar este comportamiento a nivel de repositorio y definir si las alertas con gravedad de `error`, `advertencia` o `nota` ocasionarán que una verificación de solicitud de cambio falle. Predeterminadamente, las alertas del {% data variables.product.prodname_code_scanning %} que no sean de seguridad y tengan un nivel de gravedad de `error` ocasionarán que la verificación de una solicitud de cambios falle.\n\nPara obtener más información, consulta la sección \"[Definir qué alertas de niveles de gravedad ocasionan que falle la verificación de las solicitudes de cambio]](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)\".\n\n![Lista de alertas de escaneo de código con niveles de seguridad](/assets/images/enterprise/3.2/release-notes/code-scanning-alerts.png)\n" - "Las mejoras al filtro de rama para las alertas del {% data variables.product.prodname_code_scanning %} dejan más claro qué alertas del {% data variables.product.prodname_code_scanning %} se están mostrando en la página de alertas. Predeterminadamente, las alertas del {% data variables.product.prodname_code_scanning %} se filtran para mostrar únicamente las alertas de la rama predeterminada del repositorio. Puedes utilizar el filtro de rama para mostrar las alertas en cualquiera de las ramas no predeterminadas. Cualquier filtro de rama que se haya aplicado se mostrará en la barra de búsqueda.\n\nLa sintaxis de búsqueda también se simplificó como `branch:`. Esta sintaxis se puede utilizar varias veces en la barra de búsqueda para filtrar en ramas múltiples. La sintaxis previa `ref:refs/heads/`, aún es compatible, así que cualquier URL que se haya guardado seguirá funcionando.\n" - - "Free text search is now available for code scanning alerts. You can search code scanning results to quickly find specific alerts without having to know exact search terms. The search is applied across the alert's name, description, and help text. The syntax is:\n\n- A single word returns all matches.\n- Multiple search words returns matches to either word.\n- Words in double quotes returns exact matches.\n- The keyword 'AND' returns matches to multiple words.\n" - - '{% data variables.product.prodname_secret_scanning_caps %} added patterns for 23 new service providers. For the updated list of supported secrets, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning)."' + - "Ahora está disponible la búsqueda de texto libre para las alertas de escaneo de código. Puedes buscar resultados del escaneo de código para encontrar alertas específicas rápidamente sin tener que conocer los términos de búsqueda exactos. La búsqueda se aplica a lo large del nombre, descripción y texto de ayuda de la alerta. La sintaxis es:\n\n- Una palabra única devuelve todas las coincidencias.\n- Las palabras de búsqueda múltiples devuelven coincidencias para cualquiera de las palabras.\n- Las palabras entre comillas dobles devuelven coincidencias exactas.\n- La palabra clave 'AND' devuelve coincidencias de palabras múltiples.\n" + - '{% data variables.product.prodname_secret_scanning_caps %} agregó patrones para 23 proveedores de servicio nuevos. Para encontrar la lista actualizada de secretos compatibles, consulta la sección "[Acerca del escaneo de secretos](/code-security/secret-scanning/about-secret-scanning)".' - heading: 'Cambios a la API' notes: - - 'Pagination support has been added to the Repositories REST API''s "compare two commits" endpoint, which returns a list of commits reachable from one commit or branch, but unreachable from another. The API can also now return the results for comparisons over 250 commits. For more information, see the "[Repositories](/rest/reference/repos#compare-two-commits)" REST API documentation and "[Traversing with pagination](/rest/guides/traversing-with-pagination)."' - - 'The REST API can now be used to programmatically resend or check the status of webhooks. For more information, see "[Repositories](/rest/reference/repos#webhooks)," "[Organizations](/rest/reference/orgs#webhooks)," and "[Apps](/rest/reference/apps#webhooks)" in the REST API documentation.' + - 'La compatibilidad con paginación se agregó a la terminar de "comparar dos confirmaciones" de la API de REST, la cual devuelve una lista de confirmaciones que se pueden alcanzar desde una confirmación o rama, pero no desde alguna otra. La API ahora también puede devolver los resultados para comparaciones de más de 250 confirmaciones. Para obtener más información, consulta la sección de "[Repositories](/rest/reference/repos#compare-two-commits)" de la API de REST y la sección de "[Navegar con paginación](/rest/guides/traversing-with-pagination)".' + - 'La API de REST ahora puede utilizarse para reenviar mediante programación o verificar el estado de los webhooks. Para obtener más información, consulta las secciones "[Repositories](/rest/reference/repos#webhooks)," "[Organizations](/rest/reference/orgs#webhooks)," y "[Apps](/rest/reference/apps#webhooks)" in the REST API documentation.' - "Se han realizado mejoras al escaneo de código y a las API de la {% data variables.product.prodname_GH_advanced_security %}:\n\n- La API de escaneo de código ahora devuelve la versión de consulta de COdeQL que se utiliza para un análisis. Esto puede utilizarse para reproducir los resultados o confirmar un análisis que se utiliza como la consulta más reciente. Para obtener información, consulta la sección \"[Escaneo de código](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository)\" en la documentación de la API de REST.\n-Los usuarios administrativos ahora pueden utilizar la API de REST para habilitar o inhabilitar la {% data variables.product.prodname_GH_advanced_security %} para repositorios utilizando el objeto `security_and_analysis` en `repos/{org}/{repo}`. Adicionalmente, los usuarios administrativos pueden verificar si la {% data variables.product.prodname_advanced_security %} se encuentra habilitada actualmente para un repositorio utilizando una solicitud de tipo `GET /repos/{owner}/{repo}`. Estos cambios de ayudan a administrar el acceso a los repositorios de {% data variables.product.prodname_advanced_security %} en escala. Para obtener más información, consulta la sección de \"[Repositories](/rest/reference/repos#update-a-repository)\" en la documentación de la API de REST.\n" known_issues: - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' @@ -102,26 +102,26 @@ sections: - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.' - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.' - 'El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.' - - 'Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.' + - '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.' deprecations: - heading: 'Obsoletización de GitHub Enterprise Server 2.21' notes: - - '**{% data variables.product.prodname_ghe_server %} 2.21 was discontinued on June 6, 2021**. That 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.2/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' - - heading: 'Deprecation of GitHub Enterprise Server 2.22' + - '**{% data variables.product.prodname_ghe_server %} 2.21 se descontinuó el 6 de junio de 2021**. Esto significa que no se harán lanzamientos de parche, aún para los problemas de seguridad crítucos, después de esta fecha. Para obtener un rendimiento mejor, una seguridad mejorada y características nuevas, [actualiza a la última versión de {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.2/admin/enterprise-management/upgrading-github-enterprise-server) tan pronto te sea posible.' + - heading: 'Obsoletización de GitHub Enterprise Server 2.22' notes: - - '**{% data variables.product.prodname_ghe_server %} 2.22 will be discontinued on September 23, 2021**. That 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.2/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' + - '**{% data variables.product.prodname_ghe_server %} 2.22 se descontinuará el 23 de septiembre de 2021**. Esto significa que no se harán lanzamientos de parches, incluso para los problemas de seguridad, después de dicha fecha. Para tener un rendimiento mejor, una seguridad mejorada y cualquier característica nueva, [actualiza a la versión más nueva de {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.2/admin/enterprise-management/upgrading-github-enterprise-server) tan pronto te sea posible.' - heading: 'Obsoletización del soporte para XenServer Hypervisor' notes: - - 'Beginning in {% data variables.product.prodname_ghe_server %} 3.1, we will begin discontinuing support for Xen Hypervisor. The complete deprecation is scheduled for {% data variables.product.prodname_ghe_server %} 3.3, following the standard one year deprecation window. Please contact [GitHub Support](https://enterprise.githubsupport.com/hc/en-us/signin) with questions or concerns.' - - heading: 'Removal of Legacy GitHub Services' + - 'Desde la versión 3.1 de {% data variables.product.prodname_ghe_server %}, comenzaremos a descontinuar la compatibilidad con Xen Hypervisor. La obsoletización completa está programada para la versión 3.3 de {% data variables.product.prodname_ghe_server %}, siguiendo la ventana de obsoletización estándar de un año. Por favor, contacta al [Soporte de Github](https://enterprise.githubsupport.com/hc/en-us/signin) so tienes dudas o preguntas.' + - heading: 'Eliminación de los servicios tradicionales de GitHub' notes: - - '{% data variables.product.prodname_ghe_server %} 3.2 removes unused GitHub Service database records. More information is available in the [deprecation announcement post](https://developer.github.com/changes/2018-04-25-github-services-deprecation/).' - - heading: 'Deprecation of OAuth Application API endpoints and API authentication via query parameters' + - '{% data variables.product.prodname_ghe_server %} 3.2 elimina los registros de base de datos de GitHub Service sin utilizar. Hay más información disponible en la [publicación del anuncio de obsoletización](https://developer.github.com/changes/2018-04-25-github-services-deprecation/).' + - heading: 'Obsoletización de las terminales de la API de Aplicaciones OAuth y autenticación de la API a través de parámetros de consulta' notes: - "Para prevenir el inicio de sesión o exposición accidental de los `access_tokens`, desalentamos el uso de las terminales de la API de las Aplicaciones OAuth y el uso de auth de API a través de parámetros de consultas. Visita las siguientes publicaciones para ver los reemplazos propuestos:\n\n*[Reemplazo para las terminales de la API de Aplicaciones OAuth](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#changes-to-make)\n* [Reemplazo de auth a través de encabezados en vez de parámetros de consulta](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make)\n\nSe pretende que estas terminales y rutas de auth se eliminen del {% data variables.product.prodname_ghe_server %} en la versión 3.4 de {% data variables.product.prodname_ghe_server %}.\n" - - heading: 'Removal of legacy GitHub App webhook events and endpoints' + - heading: 'Eliminación de los eventos de webhook y terminales tradicionales de las GitHub Apps' notes: - - "Two legacy GitHub Apps-related webhook events have been removed: `integration_installation` and `integration_installation_repositories`. You should instead be listening to the `installation` and `installation_repositories` events.\n" - - "The following REST API endpoint has been removed: `POST /installations/{installation_id}/access_tokens`. You should instead be using the namespaced equivalent `POST /app/installations/{installation_id}/access_tokens`.\n" + - "Se eliminaron dos eventos de webhook relacionados con las GitHub Apps tradicionales: `integration_installation` y `integration_installation_repositories`. En su lugar, deberías estar escuchando a los eventos de `installation` y `installation_repositories`.\n" + - "La siguiente terminal de la API de REST se eliminó: `POST /installations/{installation_id}/access_tokens`. En su lugar, deberías etar utilizando aquella con designador de nombre: `POST /app/installations/{installation_id}/access_tokens`.\n" backups: - - '{% data variables.product.prodname_ghe_server %} 3.2 requires at least [GitHub Enterprise Backup Utilities 3.2.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/enterprise-server@3.2/admin/configuration/configuring-backups-on-your-appliance).' + - '{% data variables.product.prodname_ghe_server %} 3.2 requiere de por lo menos contar con [Las Utilidades de Respaldo 3.2.0 de GitHub Enterprise](https://github.com/github/backup-utils) para [Los Respaldos y Recuperación de Desastres](/enterprise-server@3.2/admin/configuration/configuring-backups-on-your-appliance).' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/0.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/0.yml new file mode 100644 index 0000000000..da6faf2421 --- /dev/null +++ b/translations/es-ES/data/release-notes/enterprise-server/3-2/0.yml @@ -0,0 +1,125 @@ +date: '2021-09-28' +intro: 'Para encontrar las instrucciones de mejora, consulta la sección "[Mejorar a {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)".' +sections: + features: + - heading: 'Patrones personalizados para el escaneo de secretos' + notes: + - "Los clientes de {% data variables.product.prodname_GH_advanced_security %} ahora pueden especificar los patrones para el escaneo de secretos. Cuando se especifica un patrón nuevo, el escaneo de secretos busca dicho patrón en todo el historial de Git del repositorio, así como cualquier confirmación nueva.\n\nLos patrones definidos por los usuarios se encuentran en beta para {% data variables.product.prodname_ghe_server %} 3.2. Se pueden definir a nivel de repositorio, organización y empresa. Para obtener más información, consulta la sección \"[Definir patrones personalizados para el escaneo de secretos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)\".\n" + - heading: 'Resumen de seguridad para la Seguridad Avanzada (beta)' + notes: + - "Los clientes de la {% data variables.product.prodname_GH_advanced_security %} ahora tienen una vista de nivel de organización apra los riegos de seguridad de las aplicaciones que detecte el {% data variables.product.prodname_code_scanning %}, el {% data variables.product.prodname_dependabot %} y el {% data variables.product.prodname_secret_scanning %}. El resumen de seguridad muestra la habilitación de estado de las características de seguridad en cada repositorio, así como la cantidad de alertas que se detectan.\n\nAdicionalmente, el resumen de seguridad lista todas las alertas del {% data variables.product.prodname_secret_scanning %} a nivel organizacional. Tendremos vistas similares para el {% data variables.product.prodname_dependabot %} y el {% data variables.product.prodname_code_scanning %} en los lanzamientos futuros cercanos. Para obtener más información, consulta la sección \"[Acerca del resumen de seguridad](/code-security/security-overview/about-the-security-overview)\".\n\n![Captura de pantalla del resumen de seguridad](/assets/images/enterprise/3.2/release-notes/security-overview-UI.png)\n" + - heading: 'Revisión de dependencias (beta)' + notes: + - "Los clientes de {% data variables.product.prodname_GH_advanced_security %} ahora pueden ver un diff enriquecido de las dependencias que cambiaron en una solicitud de cambios. La revisión de dependencias proporciona una vista fácil de entender de los cambios a las dependencias y de su impacto de seguridad en la pestaña de \"Archivos que cambiaron\" de las solicitudes de cambios. Esta te informa de las dependencias que se agregaron, eliminaron o actualizaron junto con la información de vulnerabilidades de estas dependencias. Para obtener más información, consulta la sección \"[Revisar los cambios de dependencias en una solicitud de cambios](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)\".\n" + - heading: 'Ambientes de GitHub Actions' + notes: + - "Los ambientes, las reglas de protección de ambiente y los secretos de ambiente ahora están disponibles en general para las {% data variables.product.prodname_actions %} en {% data variables.product.product_name %}. Para obtener más información, consulta la sección \"[Environments](/actions/reference/environments)\".\n" + - heading: 'Autenticación por SSH con llaves seguras' + notes: + - "Ahora es compatible la autenticación por SSH utilizando una llave de seguridad FIDO2 cuando agregas una llave SSH de tipo `sk-ecdsa-sha2-nistp256@openssh.com` o `sk-ssh-ed25519@openssh.com` a tu cuenta. Las llaves de seguridad SSH almacenan material de llaves secretas en un dispositivo de hardware por separado, el cual requiere de verificación, tal como un tap, para operar. Para obtener más información, consulta la sección \"[Generar una clave SSH nueva y agregarla al ssh-agent](/github/authenticating-to-github/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)\".\n" + - heading: 'Temas oscuro y oscuro atenuado' + notes: + - "Ahora hay temas oscuro y opaco oscuro disponibles para la IU web. {% data variables.product.product_name %} empatará las preferencias de tu sistema si no has configurado las preferencias de tema en {% data variables.product.product_name %}. También puedes elegir qué temas estarán activos durante el día y la noche. Para obtener más información, consulta la sección \"[Administrar la configuración de tu tema](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)\".\n\n![Temas oscuro y opaco oscuro](https://user-images.githubusercontent.com/33528647/114629560-d2231f80-9c86-11eb-9bde-cc301a97040d.gif)\n" + - heading: 'Aprobar dominios no verificados para las notificaciones de correo electrónico' + notes: + - 'Los dominios que no se pueden verificar ahora pueden aprobarse para el enrutamiento de notificaciones por correo electrónico. Los propietarios de empresas y organizaciones podrán aprobar dominios y aumentar su política de restricción de notificaciones por correo electrónico automáticamente, lo cual permitirá que las notificaciones se envíen a los colaboradores, consultores, adquisiciones o a otros socios. para obtener más información, consulta las secciones "[Verificar o aprobar un dominio para tu empresa](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#about-approval-of-domains)" y "[Restringir las notificaciones por correo electrónico para tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise#restricting-email-notifications-for-your-enterprise-account)."' + - heading: 'Soporte para el almacenamiento de credenciales seguro del Administrador de Credenciales de Git (GCM) y autenticación multifactorial' + notes: + - "Las versiones 2.0.452 y posteriores del Administrador de Credenciales de Git (GCM) Core ahora proporcionan compatibilidad de almacenamiento de credenciales con seguridad fortalecida y autenticación multifactorial para {% data variables.product.product_name %}.\n\nEl GCM Core con compatibilidad para {% data variables.product.product_name %} se incluye con [Git para Windows](https://gitforwindows.org) en sus versiones 2.32 y posterior. GCM Core no se incluye con Git para macOS o para Linux, pero puede instalarse por separado. Para obtener más información, consulta el [lanzamiento más reciente](https://github.com/microsoft/Git-Credential-Manager-Core/releases/) y las [instrucciones de instalación](https://github.com/microsoft/Git-Credential-Manager-Core/releases/) en el repositorio `microsoft/Git-Credential-Manager-Core`.\n" + changes: + - heading: 'Cambios en la administración' + notes: + - 'Se agregó un ajuste de "Política de Referente de Agente Usuario" a la configuración empresarial. Esto permite que un administrador configure una "Política de referente" más estricta para ocultar el nombre de host de una instalación de {% data variables.product.prodname_ghe_server %} de sitios externos. Este ajuste se encuentra inhabilitado predeterminadamente y los eventos de bitácoras de auditoría lo rastrean para los propietarios empresariales y el personal de las empresas cuando se habilita o inhabilita. Para obtener más información, consulta la sección "[Configurar la Política de Referente en tu empresa](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)".' + - 'La revisión de salud de MySQL se cambió al uso de `mysqladmin ping` en vez de las verificaciones de TCP, lo cual elimina algo del ruido innecesario en la bitácora de errores de MySQL, las verificaciones de recuperación de fallos del orquestador se mejoraron para prevenir las recuperaciones de fallos de MySQL innecesarias al aplicar cambios de configuración del clúster.' + - 'El servicio Resque, el cual da la compatibilidad con procesamiento de jobs en segundo plano, se reemplazó con Aqueduct Lite. este cambio hace que el sistema de jobs se pueda administrar más fácilmente y no debería afectar la experiencia del usuario. Para la administración y comandos de depuración nuevas de Aqueduct, consulta la sección "[Utilidades de la línea de comandos](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-aqueduct)".' + - heading: 'Cambios de Token' + notes: + - "El formato de tokens de autenticación para {% data variables.product.product_name %} ha cambiado,. Dicho cambio afecta el formato de los tokens de acceso personal y de los tokens de acceso para las {% data variables.product.prodname_oauth_apps %}, así como de los tokens de usuario a servidor, de servidor a servidor y de actualización para {% data variables.product.prodname_github_apps %}.\n\nLos diferentes tipos de token ahora tienen prefijos identificables únicos, los cuales permiten que el escaneo de secretos detecten los tokens para que puedas mitigar el impacto de que alguien confirme un token accidentalmente en un repositorio. {% data variables.product.company_short %} recomienda actualizar los tokens existentes tan pronto como te sea posible. Para obtener más información, consulta las secciones \"[Acerca de la autenticación en {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github#githubs-token-formats)\" y \"[Acerca del {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)\".\n" + - heading: 'Cambios de repositorios' + notes: + - 'Los repositorios en los perfiles de usuario y en los perfiles de organización ahora son compatibles con la clasificación por conteo de estrellas.' + - 'Cuando veas el historial de confirmación de un archivo único, ahora puedes hacer clic en {% octicon "file-code" aria-label="The code icon" %} para ver dicho archivo en algún punto selecto del historial.' + - 'Cuando un submódulo se define con una ruta relativa en {% data variables.product.product_location %}, el submódulo ahora se puede hacer clic en la interfaz web. Al hacer clic en el submódulo de la interfaz web le llevará al repositorio enlazado. Anteriormente, sólo los submódulos con URLs absolutas podían hacer clic. Esto es soportado para rutas relativas para los repositorios con el mismo propietario que siguen el patrón ..REPOSITORY o rutas relativas de repositorios con un propietario diferente que siga el patrón ../OWNER/REPOSITORY. Para obtener más información sobre cómo trabajar con submódulos, consulta la sección [Trabajar con submódulos](https://github.blog/2016-02-01-working-with-submodules/) en {% data variables.product.prodname_blog %}.' + - 'La IU web ahora puede utilizarse para sincronizar una rama desactualizada de una bifurcación con la rama ascendente de dicha bifurcación. Si no hay conflictos de fusión entre las ramas, la rama se actualizará ya sea mediante un envío rápido o mediante la fusión desde la parte ascendente. Si hay conflictos, se te pedirá crear una solicitud de cambios para resolverlos. Para obtener más información, consulta la sección "[Sincronizar una bifurcación](/github/collaborating-with-pull-requests/working-with-forks/syncing-a-fork#syncing-a-fork-from-the-web-ui)".' + - heading: 'Cambios en el Lenguaje de Marcado' + notes: + - 'El editor de lenguaje de marcado que se utiliza al crear o editar un lanzamiento en un repositorio ahora tiene una barra de herramientas para edición de texto. Para obtener más información, consulta la sección "[Adminsitrar los lanzamientos en un repositorio](/github/administering-a-repository/releasing-projects-on-github/managing-releases-in-a-repository#creating-a-release)".' + - '{% data variables.product.product_name %} ahora tiene compatibilidad para cargar archivos de video en donde sea que utilices lenguaje de marcado. Comparte demostraciones, pasos de reproducción y más en los comentarios de tus propuestas y solicitudes de cambio, así como en los archivos de lenguaje de marcado dentro de los repositorios, tales como los README. Para obtener más información, consulta la sección "[Adjuntar archivos](/github/writing-on-github/working-with-advanced-formatting/attaching-files)".' + - 'Los archivos de lenguaje de marcado ahora generarán una tabla de contenido automáticamente en el encabezado cuando haya 2 o más encabezados. La tabla de contenido es interactiva y enlaza a la sección seleccionada. Los 6 niveles de encabezado del lenguaje de marcado son compatibles.' + - 'Hay un atajo de teclado nuevo, `cmd+e` en macOS o `ctrl+e` en Windows, para insertar bloques de código en los archivos, propuestas, solicitudes de cambio y comentarios de Lenguaje de Marcado.' + - 'El agregar `?plain=1` a la URL en cualquier archivo de lenguaje de marcado ahora mostrará al archivo sin procesar y con números de línea. La vista simple puede utilizarse para enlazar a otros usuarios a líneas específicas. Por ejemplo, el agregar `?plain=1#L52` resaltará la línea 52 del archivo de marcado en texto simple. Para obtener más información, consulta la sección "[Crear un enlace permanente a un fragmento de código](/github/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet#linking-to-markdown)".' + - heading: 'Cambios en propuestas y sollicitudes de cambio' + notes: + - 'Con la [versión más reciente de Octicons](https://github.com/primer/octicons/releases), los estados de las propuestas y solicitudes de cambios ahora son más fáciles de distinguir visualmente para que puedas escanear los estados de forma más sencilla. Para obtener más información consulta la sección [{% data variables.product.prodname_blog %}](https://github.blog/changelog/2021-06-08-new-issue-and-pull-request-state-icons/).' + - 'Ahora tenemos disponible una regla de protección de rama de "Requerir la resolución de la conversación antes de fusionar" y un menú de "Conversaciones". Descubre fácilmente tus comentarios de solicitudes de cambios desde la pestaña de "Archivos que cambiaron" y requiere qeu todas tus conversaciones en solicitudes de cambio se resuelvan antes de fusionarse. Para obtener más información, consulta las secciones "[Acerca de las revisiones de solicitudes de cambio](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews#discovering-and-navigating-conversations)" y "[Acerca de las ramas protegidas](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-conversation-resolution-before-merging)".' + - 'Para prevenir la fusión de cambios inesperados después de habilitar la fusión automática para una solicitud de cambios, ahora se inhabilitó esta opción automáticamente cuando un usuario sin acceso de escritura al repositorio sube estos cambios. Los usuarios que no tengan permisos de escritura aún pueden actualizar la solicitud de cambios con aquellos de la rama base cuando se habilita la fusión automática. Para prevenir que un usuario malintencionado utilice un conflicto de fusión para introducir cambios inesperados a la solicitud de cambios, la fusión automática para la solicitud de cambios se encuentra inhabilitada si dicha actualización causa un conflicto de fusión. Para obtener más información sobre la fusión automática, consulta la sección "[Fusionar una solicitud de cambios automáticamente](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)".' + - 'Las personas con permisos de mantenimiento ahora pueden administrar el ajuste de "Permitir la fusión automática" a nivel de repositorio. Este ajuste, el cual a menudo se encuentra inhabilitado, controla si la fusión automática está disponible para las solicitudes de cambios en el repositorio., Anteriormente, solo las personas con permisos administrativos podían administrar este ajuste. Adicionalmente, este ajuste ahora puede controlarse utilizando las API de REST para "[Crear repositorio](/rest/reference/repos#create-an-organization-repository)" y "[Actualizar repositorio](/rest/reference/repos#update-a-repository)". Para obtener más información, consulta la sección "[Administrar la fusión automática para las solicitudes de cambios en tu repositorio]](/github/administering-a-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository)".' + - 'La selección de propuestas y solicitudes de cambio de los asignados ahora es compatible con la búsqueda de escritura anticipada, así que puedes encontrar usuarios en tu organización más rápidamente. Adicionalmente, las clasificaciones de resultados de búsqueda se actualizaron para preferir las coincidencias al inicio del nombre de usuario de una persona o nombre de perfil.' + - 'Cuando se solicita una revisión de un equipo de más de 100 personas, los desarrolladores ahora muestran una caja de diálogo de confirmación para poder prevenir las notificaciones innecesarias para los equipos grandes.' + - 'Ahora hay compatibilidad con tener `code blocks` con comilla inversa en los títulos de las propuestas y en cualquier lugar en el que se referencien propuestas y solicitudes de cambios en {% data variables.product.prodname_ghe_server %}.' + - 'Los eventos para las solicitudes de cambios y revisiones de solicitudes de cambios ahora se incluyen en la bitácora de auditoría tanto para [enterprises](/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise) como para [organizations](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization). estos eventos ayudan a que los administradores monitoreen mejor la actividad de las solicitudes de cambios y ayuden a garantizar que se cumplan los requisitos de seguridad y cumplimiento. Los eventos pueden verse desde la IU web, exportarse como CSV o JSON o acceder a ellos a través de la API de REST. También puedes buscar la bitácora de auditoría para los eventos de solicitudes de cambio específicos. Para obtener más información, consulta la sección "[Revisar la bitácora de auditoría para tu organización](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#pull_request-category-actions)".' + - heading: 'Cambios a las ramas' + notes: + - "El nombre de rama predeterminado para los repositorios nuevos ahora es `main`. Los repositorios existentes no se verán impactados por este cambio. Si los usuarios, propietarios de organizaciones o propietarios de empresas ya especificaron una rama predeterminada para repositorios nuevos anteriormente, tampoco se les impactará.\n\nSi quieres configurar un nombre de rama predeterminada diferente, puedes hacerlo en los ajustes de [user](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories), [organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization), o [enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name).\n" + - "Las ramas, incluyendo a la predeterminada, ahora pueden volver a nombrarse utilizando la IU web de {% data variables.product.product_name %}. Cuando una rama se vuelve a nombrar, cualquier solicitud de cambios abierta y lanzamiento de borrador que apunten a la rama que se volvió a nombrar se redirigirá automáticamente y las reglas de protección de rama que referencien explícitamente a la rama que se volvió a nombrar se actualizarán.\n\nSe requieren permisos administrativos para volver a nombrar la rama predeterminada, pero es suficiente contar con permisos de escritura para volver a nombrar otras ramas.\n\nPara ayudar a hacer el cambio con tanta continuidad como sea posible para los usuarios:\n\n* Se muestra un aviso a los contribuyentes, mantenedores y administradores de la página de inicio del repositorio, el cual contiene instrucciones para actualizar su repositorio local.\n*Las solicitudes web para la rama antigua se redireccionarán.\n* Se devolverá una respuesta HTTP de \"se movió permanentemente\" a todo llamado de la API de REST.\n* Se mostrará un mensaje informativo para los usuarios de la línea de comandos de Git que suban información a la rama antigua.\n\nPara obtener más información, consulta la sección \"[Volver a nombrar una rama](/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch)\".\n" + - heading: 'Cambioas a las GitHub Actions' + notes: + - 'Las {% data variables.product.prodname_actions %} ahora te permiten controlar los permisos que se otorgan al secreto del `GITHUB_TOKEN`. El `GITHUB_TOKEN` es un secreto que se genera automáticamente y te permite hacer llamados autenticados a la API de {% data variables.product.product_name %} en tus ejecuciones de flujo de trabajo. Las {% data variables.product.prodname_actions %} generan un token nuevo para cada job y hacen que el token venza cuando se completa el job. El token a menudo tiene permisos de `escritura` para varias [Terminales de la API](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token), con excepción de los casos de las solicitudes de cambios de las bifurcaciones, los cuales siempre se marcan como de `lectura`. Estos ajustes nuevos te permiten seguir el principio de los menores privilegios necesarios en tus flujos de trabajo,. Para obtener más información, consulta la sección "[Autenticación en un flujo de trabajo](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token)".' + - 'El {% data variables.product.prodname_cli %} 1.9 y posterior te permiten trabajar con las {% data variables.product.prodname_actions %} en tu terminal. Para obtener más información, consulta la sección [Registro de cambios de {% data variables.product.prodname_dotcom %}](https://github.blog/changelog/2021-04-15-github-cli-1-9-enables-you-to-work-with-github-actions-from-your-terminal/).' + - 'La bitácora de auditoría ahora incluye eventos asociados con las ejecuciones de flujo de trabajo de {% data variables.product.prodname_actions %}. Estos datos proporcionan un conjunto de datos ampliamente expandidos para los administradores, así como auditorías de cumplimiento. Para obtener más información, consulta la sección "[Revisar la bitácora de auditoría de tu organización](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#workflows-category-actions)".' + - '{% data variables.product.prodname_ghe_server %} 3.2 contains performance improvements for job concurrency with {% data variables.product.prodname_actions %}. For more information on the new performance targets on 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)."' + - heading: 'Cambios a los GitHub packages' + notes: + - 'Cualquier paquete o versión de paquete del {% data variables.product.prodname_registry %} ahora se puede borrar de la IU web de {% data variables.product.product_name %}. También puedes deshacer el borrado de cualquier paquete o versión de paquete dentro de los primeros 30 días. Para obtener más información, consulta la sección "[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)".' + - heading: 'Cambios al Dependabot y a la gráfica de Dependencias' + notes: + - 'La gráfica de dependencias ahora puede habilitarse utilizando la Consola de Administración en vez de necesitar la ejecución de un comando en el shell administrativo. Para obtener más información, consulta la sección "[Habilitar las alertas para las dependencias vulnerables de {% data variables.product.prodname_ghe_server %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server#enabling-the-dependency-graph-and-dependabot-alerts-for-vulnerable-dependencies-on-github-enterprise-server)".' + - 'Ahora, las notificaciones para {% data variables.product.prodname_dependabot_alerts %} múltiples se agrupan si se descubren al mismo tiempo. Esto reduce significativamente el volumen de notificaciones de alertas del {% data variables.product.prodname_dependabot %} que reciben los usuarios. Para obtener más información, consulta la sección [Registro de cambios de {% data variables.product.prodname_dotcom %}](https://github.blog/changelog/2021-03-18-grouped-dependabot-alert-notifications/).' + - 'Las gráficas de dependencias y {% data variables.product.prodname_dependabot_alerts %} ahora son compatibles con los módulos de Go. {% data variables.product.prodname_ghe_server %} analiza los archivos de `go.mod` de un repositorio para entender las dependencias del mismo. En conjunto con las asesorías de seguridad, la gráfica de dependencias proporciona la información necesaria para alertar a los desarrolladores sobre las dependencias vulnerables. Para obtener más información sobre cómo habilitar la gráfica de dependencias en los repositorios privados, consulta la sección "[Asegurar tu repositorio](/code-security/getting-started/securing-your-repository#managing-the-dependency-graph)".' + - 'Los ajustes de notificación predeterminados para las alertas de seguridad han cambiado. Anteriormente, si tenías permiso para ver las alertas de seguridad en un repositorio, hubieras recibido las notificaciones de dicho repositorio mientras tu configuración permitiera las notificaciones de alertas de seguridad. Ahora debes decidir unirte a las notificaciones de alertas de seguridad observando el repositorio. Se te notificará si seleccionas `Toda la actividad` o si configuras `Personalizado` para incluir las `Alertas de seguridad`. Todos los repositorios existentes se migrarán automáticamente a estos ajustes nuevos y seguirás recibiendo notificaciones; sin embargo, cualquier repositorio nuevo requerirá que decidas unirte observando el repositorio. Para obtener más información, consulta las secciones "[Configurar notificaciones para las dependencias vulnerables](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies)" y "[Administrar las alertas del escaneo de secretos](/code-security/secret-security/managing-alerts-from-secret-scanning)".' + - heading: 'Cambios al escaneo de código y de secretos' + notes: + - 'El {% data variables.product.prodname_code_scanning_capc %} con {% data variables.product.prodname_codeql %} ahora genera información diagnóstica para todos los lenguajes compatibles. Esto ayuda a mantener el estado de la base de datos creada para entender el estado y calidad del análisis que se realizó. La información diagnóstica se encuentra disponible desde la [versión 2.5.6](https://github.com/github/codeql-cli-binaries/releases) del {% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/). Puedes ver esta información diagnóstica detallada en las bitácoras para {% data variables.product.prodname_codeql %} de las {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Visualizar las bitácoras de escaneo de código](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs)".' + - 'El {% data variables.product.prodname_code_scanning_capc %} con {% data variables.product.prodname_codeql_cli %} ahora es compatible con el análisis de diversos lenguajes durante una compilación sencilla. Esto facilita el ejecutar análisis de código para utilizar sistemas de IC/DC diferentes a los de las {% data variables.product.prodname_actions %}. El modo nuevo del comando `codeql database create` se encuentra disponible desde la [versión 2.5.6] (https://github.com/github/codeql-cli-binaries/releases) del [{% data variables.product.prodname_codeql_cli %}] (https://codeql.github.com/docs/codeql-cli/). Para obtener más información sobre cómo configurar esto, consulta la sección "[Instalar el {% data variables.product.prodname_codeql_cli %} en tu sistema de IC](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-cli-in-your-ci-system)".' + - 'Las alertas de {% data variables.product.prodname_code_scanning_capc %} de todas las herramientas habilitadas ahora se muestran en una lista consolidada para que puedas priorizar fácilmente entre todas ellas. Puedes ver las alertas desde una herramienta específica utilizando le filtro de "Herramienta" y los de "Regla" y "Etiqueta" se actualizarán dinámicamente con base en tu selección de "Herramientas".' + - 'El {% data variables.product.prodname_code_scanning_capc %} cib {% data variables.product.prodname_codeql %} ahora incluye soporte beta para analizar código de C++20. Esto solo está disponible cuando creas bases de código con GCC en Linux. Los módulos de C++20 aún no son compatibles.' + - 'La profundidad del análisis de {% data variables.product.prodname_codeql %} se mejoró al agregar compatibilidad para más [librerías y marcos de trabajo](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) y al incrementar la cobertura de nuestros modelos de marcos de trabajo y librerías para varios lenguajes ({C++](https://github.com/github/codeql/tree/main/cpp), [JavaScript](https://github.com/github/codeql/tree/main/javascript), [Python](https://github.com/github/codeql/tree/main/python), y [Java](https://github.com/github/codeql/tree/main/java)). Como resultado, el {% data variables.product.prodname_codeql %} ahora puede detectar aún más fuentes potenciales de datos de usuarios no confiables, revisar los pasos a través de los cuales fluyen los datos e identificar hundimientos potencialmente peligrosos en los cuales podrían terminar estos datos,. Esto da como resultado una mejora general de la calidad de las alertas del {% data variables.product.prodname_code_scanning %}. Para obtener más información, consulta la sección de [registro de cambios de {% data variables.product.prodname_dotcom %}](https://github.blog/changelog/2021-07-01-codeql-code-scanning-now-recognizes-more-sources-and-uses-of-untrusted-user-data/).' + - "El {% data variables.product.prodname_code_scanning_capc %} ahora muestra niveles de `gravedad de seguridad` para las alertas del Code QL. Puedes configurar qué niveles de `gravedad de seguridad` ocasionarán un fallo de verificación para una solicitud de cambios. El nivel de gravedad de las alertas de seguridad puede ser `crítico`, `alto, `medio` o `bajo`. Predeterminadamente, cualquier alerta del {% data variables.product.prodname_code_scanning %} con un `nivel de gravedad` que sea `crítico` o `alto` ocasionará que una solicitud de cambios falle.\n\nAdicionalmetnte, ahora también puedes configurar qué niveles de gravedad ocasionarán que la verificación de solicitudes de cambio falle para las alertas que no sean de seguridad. Puedes configurar este comportamiento a nivel de repositorio y definir si las alertas con gravedad de `error`, `advertencia` o `nota` ocasionarán que una verificación de solicitud de cambio falle. Predeterminadamente, las alertas del {% data variables.product.prodname_code_scanning %} que no sean de seguridad y tengan un nivel de gravedad de `error` ocasionarán que la verificación de una solicitud de cambios falle.\n\nPara obtener más información, consulta la sección \"[Definir qué alertas de niveles de gravedad ocasionan que falle la verificación de las solicitudes de cambio]](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)\".\n\n![Lista de alertas de escaneo de código con niveles de seguridad](/assets/images/enterprise/3.2/release-notes/code-scanning-alerts.png)\n" + - "Las mejoras al filtro de rama para las alertas del {% data variables.product.prodname_code_scanning %} dejan más claro qué alertas del {% data variables.product.prodname_code_scanning %} se están mostrando en la página de alertas. Predeterminadamente, las alertas del {% data variables.product.prodname_code_scanning %} se filtran para mostrar únicamente las alertas de la rama predeterminada del repositorio. Puedes utilizar el filtro de rama para mostrar las alertas en cualquiera de las ramas no predeterminadas. Cualquier filtro de rama que se haya aplicado se mostrará en la barra de búsqueda.\n\nLa sintaxis de búsqueda también se simplificó como `branch:`. Esta sintaxis se puede utilizar varias veces en la barra de búsqueda para filtrar en ramas múltiples. La sintaxis previa `ref:refs/heads/`, aún es compatible, así que cualquier URL que se haya guardado seguirá funcionando.\n" + - "Ahora está disponible la búsqueda de texto libre para las alertas de escaneo de código. Puedes buscar resultados del escaneo de código para encontrar alertas específicas rápidamente sin tener que conocer los términos de búsqueda exactos. La búsqueda se aplica a lo large del nombre, descripción y texto de ayuda de la alerta. La sintaxis es:\n\n- Una palabra única devuelve todas las coincidencias.\n- Las palabras de búsqueda múltiples devuelven coincidencias para cualquiera de las palabras.\n- Las palabras entre comillas dobles devuelven coincidencias exactas.\n- La palabra clave 'AND' devuelve coincidencias de palabras múltiples.\n" + - '{% data variables.product.prodname_secret_scanning_caps %} agregó patrones para 23 proveedores de servicio nuevos. Para encontrar la lista actualizada de secretos compatibles, consulta la sección "[Acerca del escaneo de secretos](/code-security/secret-scanning/about-secret-scanning)".' + - heading: 'Cambios a la API' + notes: + - 'La compatibilidad con paginación se agregó a la terminar de "comparar dos confirmaciones" de la API de REST, la cual devuelve una lista de confirmaciones que se pueden alcanzar desde una confirmación o rama, pero no desde alguna otra. La API ahora también puede devolver los resultados para comparaciones de más de 250 confirmaciones. Para obtener más información, consulta la sección de "[Repositories](/rest/reference/repos#compare-two-commits)" de la API de REST y la sección de "[Navegar con paginación](/rest/guides/traversing-with-pagination)".' + - 'La API de REST ahora puede utilizarse para reenviar mediante programación o verificar el estado de los webhooks. Para obtener más información, consulta las secciones "[Repositories](/rest/reference/repos#webhooks)," "[Organizations](/rest/reference/orgs#webhooks)," y "[Apps](/rest/reference/apps#webhooks)" in the REST API documentation.' + - "Se han realizado mejoras al escaneo de código y a las API de la {% data variables.product.prodname_GH_advanced_security %}:\n\n- La API de escaneo de código ahora devuelve la versión de consulta de COdeQL que se utiliza para un análisis. Esto puede utilizarse para reproducir los resultados o confirmar un análisis que se utiliza como la consulta más reciente. Para obtener información, consulta la sección \"[Escaneo de código](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository)\" en la documentación de la API de REST.\n-Los usuarios administrativos ahora pueden utilizar la API de REST para habilitar o inhabilitar la {% data variables.product.prodname_GH_advanced_security %} para repositorios utilizando el objeto `security_and_analysis` en `repos/{org}/{repo}`. Adicionalmente, los usuarios administrativos pueden verificar si la {% data variables.product.prodname_advanced_security %} se encuentra habilitada actualmente para un repositorio utilizando una solicitud de tipo `GET /repos/{owner}/{repo}`. Estos cambios de ayudan a administrar el acceso a los repositorios de {% data variables.product.prodname_advanced_security %} en escala. Para obtener más información, consulta la sección de \"[Repositories](/rest/reference/repos#update-a-repository)\" en la documentación de la API de REST.\n" + known_issues: + - 'En una instalación nueva de {% data variables.product.prodname_ghe_server %} que no tenga ningún usuario, cualquier atacante podría crear el primer usuario administrativo.' + - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.' + - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.' + - 'Cuando se habilita "Los usuarios pueden buscar en GitHub.com" con GitHub Connect, las propuestas en los repositorios privados e internos no se incluirán en los resultados de búsqueda de GitHub.com.' + - 'El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.' + - 'Los límites de recursos que son específicos para procesar ganchos de pre-recepción podrían ocasionar que fallen algunos ganchos de pre-recepción.' + deprecations: + - heading: 'Obsoletización de GitHub Enterprise Server 2.21' + notes: + - '**{% data variables.product.prodname_ghe_server %} 2.21 se descontinuó el 6 de junio de 2021**. Esto significa que no se harán lanzamientos de parche, aún para los problemas de seguridad crítucos, después de esta fecha. Para obtener un rendimiento mejor, una seguridad mejorada y características nuevas, [actualiza a la última versión de {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.2/admin/enterprise-management/upgrading-github-enterprise-server) tan pronto te sea posible.' + - heading: 'Obsoletización de GitHub Enterprise Server 2.22' + notes: + - '**{% data variables.product.prodname_ghe_server %} 2.22 se descontinuará el 23 de septiembre de 2021**. Esto significa que no se harán lanzamientos de parches, incluso para los problemas de seguridad, después de dicha fecha. Para tener un rendimiento mejor, una seguridad mejorada y cualquier característica nueva, [actualiza a la versión más nueva de {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.2/admin/enterprise-management/upgrading-github-enterprise-server) tan pronto te sea posible.' + - heading: 'Obsoletización del soporte para XenServer Hypervisor' + notes: + - 'Desde la versión 3.1 de {% data variables.product.prodname_ghe_server %}, comenzaremos a descontinuar la compatibilidad con Xen Hypervisor. La obsoletización completa está programada para la versión 3.3 de {% data variables.product.prodname_ghe_server %}, siguiendo la ventana de obsoletización estándar de un año. Por favor, contacta al [Soporte de Github](https://enterprise.githubsupport.com/hc/en-us/signin) so tienes dudas o preguntas.' + - heading: 'Eliminación de los servicios tradicionales de GitHub' + notes: + - '{% data variables.product.prodname_ghe_server %} 3.2 elimina los registros de base de datos de GitHub Service sin utilizar. Hay más información disponible en la [publicación del anuncio de obsoletización](https://developer.github.com/changes/2018-04-25-github-services-deprecation/).' + - heading: 'Obsoletización de las terminales de la API de Aplicaciones OAuth y autenticación de la API a través de parámetros de consulta' + notes: + - "Para prevenir el inicio de sesión o exposición accidental de los `access_tokens`, desalentamos el uso de las terminales de la API de las Aplicaciones OAuth y el uso de auth de API a través de parámetros de consultas. Visita las siguientes publicaciones para ver los reemplazos propuestos:\n\n*[Reemplazo para las terminales de la API de Aplicaciones OAuth](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#changes-to-make)\n* [Reemplazo de auth a través de encabezados en vez de parámetros de consulta](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make)\n\nSe pretende que estas terminales y rutas de auth se eliminen del {% data variables.product.prodname_ghe_server %} en la versión 3.4 de {% data variables.product.prodname_ghe_server %}.\n" + - heading: 'Eliminación de los eventos de webhook y terminales tradicionales de las GitHub Apps' + notes: + - "Se eliminaron dos eventos de webhook relacionados con las GitHub Apps tradicionales: `integration_installation` y `integration_installation_repositories`. En su lugar, deberías estar escuchando a los eventos de `installation` y `installation_repositories`.\n" + - "La siguiente terminal de la API de REST se eliminó: `POST /installations/{installation_id}/access_tokens`. En su lugar, deberías etar utilizando aquella con designador de nombre: `POST /app/installations/{installation_id}/access_tokens`.\n" + backups: + - '{% data variables.product.prodname_ghe_server %} 3.2 requiere de por lo menos contar con [Las Utilidades de Respaldo 3.2.0 de GitHub Enterprise](https://github.com/github/backup-utils) para [Los Respaldos y Recuperación de Desastres](/enterprise-server@3.2/admin/configuration/configuring-backups-on-your-appliance).' diff --git a/translations/es-ES/data/release-notes/enterprise-server/README.md b/translations/es-ES/data/release-notes/enterprise-server/README.md index 302e98d8f4..455cefbe49 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/README.md +++ b/translations/es-ES/data/release-notes/enterprise-server/README.md @@ -26,9 +26,9 @@ Los datos de YAML se procesan y clasifican por `middleware/contextualizers/relea ### Diseños -The `context` object data is rendered by `components/release-notes`. +`components/release-notes` interpreta el objeto de datos de `context`. -The release notes page has a custom design with CSS in `stylesheets/release-notes.scss`. +La página de notas de lanzamiento tiene un diseño personalizado con CSS en `stylesheets/release-notes.scss`. ### Modelo diff --git a/translations/es-ES/data/release-notes/github-ae/README.md b/translations/es-ES/data/release-notes/github-ae/README.md index c33a807ca6..70901239ec 100644 --- a/translations/es-ES/data/release-notes/github-ae/README.md +++ b/translations/es-ES/data/release-notes/github-ae/README.md @@ -24,9 +24,9 @@ Los datos de YAML se procesan y clasifican por `middleware/contextualizers/relea ### Diseños -The `context` object data is rendered by `components/release-notes`. +`components/release-notes` interpreta el objeto de datos de `context`. -The release notes page has a custom design with CSS in `stylesheets/release-notes.scss`. +La página de notas de lanzamiento tiene un diseño personalizado con CSS en `stylesheets/release-notes.scss`. ### Modelo diff --git a/translations/es-ES/data/reusables/actions/about-environments.md b/translations/es-ES/data/reusables/actions/about-environments.md new file mode 100644 index 0000000000..ab9cfa899f --- /dev/null +++ b/translations/es-ES/data/reusables/actions/about-environments.md @@ -0,0 +1 @@ +Environments are used to describe a general deployment target like `production`, `staging`, or `development`. When a {% data variables.product.prodname_actions %} workflow deploys to an environment, the environment is displayed on the main page of the repository. You can use environments to require approval for a job to proceed, restrict which branches can trigger a workflow, or limit access to secrets. For more information about creating environments, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." \ No newline at end of file diff --git a/translations/es-ES/data/reusables/actions/actions-app-actions-permissions-api.md b/translations/es-ES/data/reusables/actions/actions-app-actions-permissions-api.md index dcef6c2152..63b3bff01b 100644 --- a/translations/es-ES/data/reusables/actions/actions-app-actions-permissions-api.md +++ b/translations/es-ES/data/reusables/actions/actions-app-actions-permissions-api.md @@ -1 +1 @@ -{% data variables.product.prodname_github_apps %} must have the `actions` permission to use this API. +Las {% data variables.product.prodname_github_apps %} deben tener el permiso de `actions` para utilizar esta API. diff --git a/translations/es-ES/data/reusables/actions/actions-audit-events-for-enterprise.md b/translations/es-ES/data/reusables/actions/actions-audit-events-for-enterprise.md index d691d13b5d..713ce069c1 100644 --- a/translations/es-ES/data/reusables/actions/actions-audit-events-for-enterprise.md +++ b/translations/es-ES/data/reusables/actions/actions-audit-events-for-enterprise.md @@ -1,16 +1,16 @@ -| Acción | Descripción | -| -------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `remove_self_hosted_runner` | Se activa cuando se elimina un ejecutor auto-hospedado. | -| `register_self_hosted_runner` | Se crea cuando se registra un ejecutor auto-hospedado nuevo. Para obtener más información, consulta "[Agregar ejecutores autoalojados](/actions/hosting-your-own-runners/adding-self-hosted-runners)." | -| `runner_group_created` | Se activa cuando se crea un grupo de ejecutores auto-hospedados. Para obtener más información, consulta la sección "[Acerca de los grupos de ejecutores autoalojados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#about-self-hosted-runner-groups). | -| `runner_group_removed` | Se activa cuando se elimina un grupo de ejecutores auto-hospedado. For more information, see "[Removing a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)."{% ifversion ghes = 2.22 %} -| `runner_group_renamed` | Triggered when the self-hosted runner group is renamed. | -| `runner_group_visiblity_updated` | Triggered when the visibility settings of the self-hosted runner group are changed.{% endif %} -| `runner_group_runner_removed` | Se activa cuando se utiliza la API de REST para eliminar un ejecutor auto-hospedado de un grupo. | -| `runner_group_runners_added` | Se activa cuando se agrega un ejecutor auto-hospedado a un grupo. Para obtener más información, consulta la sección "[Mover un ejecutor auto-hospedado a un grupo](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)". | +| Acción | Descripción | +| -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `remove_self_hosted_runner` | Se activa cuando se elimina un ejecutor auto-hospedado. | +| `register_self_hosted_runner` | Se crea cuando se registra un ejecutor auto-hospedado nuevo. Para obtener más información, consulta "[Agregar ejecutores autoalojados](/actions/hosting-your-own-runners/adding-self-hosted-runners)." | +| `runner_group_created` | Se activa cuando se crea un grupo de ejecutores auto-hospedados. Para obtener más información, consulta la sección "[Acerca de los grupos de ejecutores autoalojados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#about-self-hosted-runner-groups). | +| `runner_group_removed` | Se activa cuando se elimina un grupo de ejecutores auto-hospedado. Para obtener más información, consulta la sección "[Eliminar un grupo de ejecutores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)".{% ifversion ghes = 2.22 %} +| `runner_group_renamed` | Se activa cuando el grupo de ejecutores auto-hospedados se renombra. | +| `runner_group_visiblity_updated` | Se activa cuando se cambia la configuración de visibilidad del grupo de ejecutores auto-hospedados.{% endif %} +| `runner_group_runner_removed` | Se activa cuando se utiliza la API de REST para eliminar un ejecutor auto-hospedado de un grupo. | +| `runner_group_runners_added` | Se activa cuando se agrega un ejecutor auto-hospedado a un grupo. Para obtener más información, consulta la sección "[Mover un ejecutor auto-hospedado a un grupo](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)". | | `runner_group_runners_updated` | Se activa cuando se actualiza la lista de miembros de un grupo de ejecutores. Para obtener más información, consulta la sección "[Configurar los ejecutores auto-hospedados en un grupo para una organización](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)". {% ifversion fpt or ghes > 2.22 or ghae %} -| `runner_group_updated` | Se activa cuando se cambia la configuración de un grupo de ejecutores auto-hospedados. For more information, see "[Changing the access policy of a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)."{% endif %} +| `runner_group_updated` | Se activa cuando se cambia la configuración de un grupo de ejecutores auto-hospedados. Para obtener más información, consulta la sección "[cambiar la política de acceso de un grupo de ejecutores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)".{% endif %} | `self_hosted_runner_updated` | Se activa cuando se actualiza la aplicación ejecutora. Se puede ver utilizando la API de REST y la IU; no se puede ver en la exportación de JSON/CSV. Para obtener más información, consulta la sección "[Acerca de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)".{% ifversion fpt %} -| `self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." | -| `self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %} +| `self_hosted_runner_online` | Se activa cuando la aplicación del ejecutor se inicia. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." | +| `self_hosted_runner_offline` | Se activa cuando se detiene la aplicación del ejecutor. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta la sección "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)".{% endif %} diff --git a/translations/es-ES/data/reusables/actions/actions-audit-events-workflow.md b/translations/es-ES/data/reusables/actions/actions-audit-events-workflow.md index f36ca44ca0..c76a64aa3d 100644 --- a/translations/es-ES/data/reusables/actions/actions-audit-events-workflow.md +++ b/translations/es-ES/data/reusables/actions/actions-audit-events-workflow.md @@ -1,12 +1,12 @@ -| Acción | Descripción | -| ---------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion fpt or ghes > 3.1 or ghae-issue-1157 %} -| `cancel_workflow_run` | Se activa cuando se cancela una ejecución de flujo de trabajo. For more information, see "[Canceling a workflow](/actions/managing-workflow-runs/canceling-a-workflow)."{% endif %}{% ifversion fpt %} -| `completed_workflow_run` | Se activa cuando el estado de un flujo de trabajo cambia a `completed`. Solo se puede visualizar utilizando la API de REST; no se puede visualizar en la IU ni en la exportación de JSON/CSV. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."{% endif %}{% ifversion fpt %} -| `created_workflow_run` | Se activa cuando se crea una ejecución de flujo de trabajo. Solo se puede visualizar utilizando la API de REST; no se puede visualizar en la IU ni en la exportación de JSON/CSV. For more information, see "[Create an example workflow](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)."{% endif %}{% ifversion fpt or ghes > 3.1 or ghae-issue-1157 %} -| `delete_workflow_run` | Se activa cuando se borra una ejecución de flujo de trabajo. Para obtener más información, consulta la sección "[Borrar una ejecución de flujo de trabajo](/actions/managing-workflow-runs/deleting-a-workflow-run)". | -| `disable_workflow` | Se activa cuando se inhabilita un flujo de trabajo. | -| `enable_workflow` | Se activa cuando se habilita un flujo de trabajo después de que `disable_workflow` lo inhabilitó previamente. | -| `rerun_workflow_run` | Se activa cuando se vuelve a ejecutar una ejecución de flujo de trabajo. For more information, see "[Re-running a workflow](/actions/managing-workflow-runs/re-running-a-workflow)."{% endif %}{% ifversion fpt %} -| `prepared_workflow_job` | Se activa cuando se inicia un job de flujo de trabajo. Incluye la lista de secretos que se proporcionaron al job. Solo se puede visualizar utilizando la API de REST; no se puede visualizar en la IU ni en la exportación de JSON/CSV. For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."{% endif %}{% ifversion fpt or ghes > 3.1 or ghae-issue-1157 %} -| `approve_workflow_job` | Triggered when a workflow job has been approved. For more information, see "[Reviewing deployments](/actions/managing-workflow-runs/reviewing-deployments)." | -| `reject_workflow_job` | Triggered when a workflow job has been rejected. For more information, see "[Reviewing deployments](/actions/managing-workflow-runs/reviewing-deployments)."{% endif %} +| Acción | Descripción | +| ---------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion fpt or ghes > 3.1 or ghae-issue-1157 %} +| `cancel_workflow_run` | Se activa cuando se cancela una ejecución de flujo de trabajo. Para obtener más información, consulta la sección "[Cancelar un flujo de trabajo](/actions/managing-workflow-runs/canceling-a-workflow)".{% endif %}{% ifversion fpt %} +| `completed_workflow_run` | Se activa cuando el estado de un flujo de trabajo cambia a `completed`. Solo se puede visualizar utilizando la API de REST; no se puede visualizar en la IU ni en la exportación de JSON/CSV. Para obtener más información, consulta la sección "[Visualizar el historial de ejecuciones de un flujo de trabajo](/actions/managing-workflow-runs/viewing-workflow-run-history)".{% endif %}{% ifversion fpt %} +| `created_workflow_run` | Se activa cuando se crea una ejecución de flujo de trabajo. Solo se puede visualizar utilizando la API de REST; no se puede visualizar en la IU ni en la exportación de JSON/CSV. Para obtener más información, consulta la sección "[Crear un flujo de trabajo de ejemplo](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)".{% endif %}{% ifversion fpt or ghes > 3.1 or ghae-issue-1157 %} +| `delete_workflow_run` | Se activa cuando se borra una ejecución de flujo de trabajo. Para obtener más información, consulta la sección "[Borrar una ejecución de flujo de trabajo](/actions/managing-workflow-runs/deleting-a-workflow-run)". | +| `disable_workflow` | Se activa cuando se inhabilita un flujo de trabajo. | +| `enable_workflow` | Se activa cuando se habilita un flujo de trabajo después de que `disable_workflow` lo inhabilitó previamente. | +| `rerun_workflow_run` | Se activa cuando se vuelve a ejecutar una ejecución de flujo de trabajo. Para obtener más información, consulta la sección "[Volver a ejecutar un flujo de trabajo](/actions/managing-workflow-runs/re-running-a-workflow)".{% endif %}{% ifversion fpt %} +| `prepared_workflow_job` | Se activa cuando se inicia un job de flujo de trabajo. Incluye la lista de secretos que se proporcionaron al job. Solo se puede visualizar utilizando la API de REST; no se puede visualizar en la IU ni en la exportación de JSON/CSV. Para obtener más información, consulta la sección "[Eventos que activan flujos de trabajo](/actions/reference/events-that-trigger-workflows)".{% endif %}{% ifversion fpt or ghes > 3.1 or ghae-issue-1157 %} +| `approve_workflow_job` | Se activa cuando se aprueba el job de un flujo de trabajo. Para obtener más información, consulta la sección "[Revisar los despliegues](/actions/managing-workflow-runs/reviewing-deployments)". | +| `reject_workflow_job` | Se activa cuando se rechaza el job de un flujo de trabajo. Para obtener más información, consulta la sección "[Revisar los despliegues](/actions/managing-workflow-runs/reviewing-deployments)".{% endif %} diff --git a/translations/es-ES/data/reusables/actions/actions-authentication.md b/translations/es-ES/data/reusables/actions/actions-authentication.md index 47b4401aa4..ea3abddabf 100644 --- a/translations/es-ES/data/reusables/actions/actions-authentication.md +++ b/translations/es-ES/data/reusables/actions/actions-authentication.md @@ -1 +1 @@ -This API is available for authenticated users, {% data variables.product.prodname_oauth_apps %}, and {% data variables.product.prodname_github_apps %}. Los tokens de acceso requieren el [alcance `repo`](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes) para los repositorios privados y el [alcance `public_repo`](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes) para {% ifversion ghae %} para los repositorios que están disponibles para todos en la empresa.{% else %}repositorios públicos.{% endif %} +Esta API se encuentra disponible para los usuarios autenticados, las {% data variables.product.prodname_oauth_apps %} y las {% data variables.product.prodname_github_apps %}. Los tokens de acceso requieren el [alcance `repo`](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes) para los repositorios privados y el [alcance `public_repo`](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes) para {% ifversion ghae %} para los repositorios que están disponibles para todos en la empresa.{% else %}repositorios públicos.{% endif %} diff --git a/translations/es-ES/data/reusables/actions/actions-group-concurrency.md b/translations/es-ES/data/reusables/actions/actions-group-concurrency.md index 5115bb8c26..63edac3ae9 100644 --- a/translations/es-ES/data/reusables/actions/actions-group-concurrency.md +++ b/translations/es-ES/data/reusables/actions/actions-group-concurrency.md @@ -1,6 +1,6 @@ Cuando un job o flujo de trabajo concurrente se pone en cola, si otro job o workflow que utilicen el mismo grupo de concurrencia en el repositorio se encuentra en progreso, el job o flujo de trabajo en cola se mostrará como `pending`. Cualquier job o flujo de trabajo pendientes anteriores en el grupo de concurrencia se cancelarán. Para también cancelar cualquier job ejecutándose concurrentemente en el mismo grupo de concurrencia, especifica `cancel-in-progress: true`. -### Ejemplos: Utilizando la concurrencia y el comportamiento predeterminado +## Ejemplos: Utilizando la concurrencia y el comportamiento predeterminado {% raw %} ```yaml @@ -14,7 +14,7 @@ concurrency: ci-${{ github.ref }} ``` {% endraw %} -### Ejemplo: Utilizar la concurrencia para cancelar cualquier job o ejecución en curso +## Ejemplo: Utilizar la concurrencia para cancelar cualquier job o ejecución en curso {% raw %} ```yaml diff --git a/translations/es-ES/data/reusables/actions/ae-hosted-runners-beta.md b/translations/es-ES/data/reusables/actions/ae-hosted-runners-beta.md new file mode 100644 index 0000000000..3abe4cf00b --- /dev/null +++ b/translations/es-ES/data/reusables/actions/ae-hosted-runners-beta.md @@ -0,0 +1,7 @@ +{% ifversion ghae %} +{% note %} + +**Nota:** Los {% data variables.actions.hosted_runner %} se encuentran actualmente en beta y están sujetos a cambios. + +{% endnote %} +{% endif %} diff --git a/translations/es-ES/data/reusables/actions/ae-self-hosted-runners-notice.md b/translations/es-ES/data/reusables/actions/ae-self-hosted-runners-notice.md index 2450ad57ef..ee2da8757a 100644 --- a/translations/es-ES/data/reusables/actions/ae-self-hosted-runners-notice.md +++ b/translations/es-ES/data/reusables/actions/ae-self-hosted-runners-notice.md @@ -1,9 +1,19 @@ {% ifversion ghae %} + {% warning %} -** Advertencia:** Los ejecutores auto-hospedados se encuentran actualmente inhabilitados para {% data variables.product.prodname_ghe_managed %}. Esto es porque {% data variables.product.prodname_ghe_managed %} ofrece garantías para los límites de seguridad, las cuales son incompatibles con la forma en que trabajan los ejecutores auto-hospedados. Sin embargo, en caso de que sí necesites utilizar ejecutores auto-hospedados con {% data variables.product.prodname_ghe_managed %} y entender las implicaciones de seguridad, puedes contactar al soporte de {% data variables.product.prodname_dotcom %} para que hagan una exepción de seguridad que los habilitará. +{% ifversion ghae-next %} + +**Advertencia:** Los ejecutores auto-hospedados se hablitan predeterminadamente para {% data variables.product.prodname_ghe_managed %}. Los ejecutores auto-hospedados son de larga duración y cualquier riesgo que sufra la máquina hospedadora podría filtrar secretos o credenciales, o habilitar otros ataques. Si te gustaría inhabilitar los ejecutores auto-hospedados en tu empresa, puedes contactar al soporte de {% data variables.product.prodname_dotcom %}. Para obtener más información sobre los riesgos de utilizar ejecutores auto-hospedados, consulta la sección "[Fortalecimiento de seguridad para las {% data variables.product.prodname_actions %}](/actions/learn-github-actions/security-hardening-for-github-actions#potential-impact-of-a-compromised-runner)". + +{% elsif ghae %} + +**Advertencia:** Los ejecutores auto-hospedados actualmente están inhabilitados para {% data variables.product.prodname_ghe_managed %}. Esto es porque {% data variables.product.prodname_ghe_managed %} ofrece garantías para los límites de seguridad, las cuales son incompatibles con la forma en que trabajan los ejecutores auto-hospedados. Sin embargo, en caso de que sí necesites utilizar ejecutores auto-hospedados con {% data variables.product.prodname_ghe_managed %} y entender las implicaciones de seguridad, puedes contactar al soporte de {% data variables.product.prodname_dotcom %} para que hagan una exepción de seguridad que los habilitará. Si no necesitas ejecutores auto-hospedados, entonces puedes utilizar {% data variables.actions.hosted_runner %} para que ejecuten tus flujos de trabajo. Para obtener más información, consulta la sección "[Acerca de los {% data variables.actions.hosted_runner %}](/actions/using-github-hosted-runners/about-ae-hosted-runners)". -{% endwarning %} +{% endif %} + +{% endwarning %} + {% endif %} 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 aa7e41dfb0..f9ac1613eb 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 @@ -1,7 +1,7 @@ Cuando eliges el **Permitir las acciones seleccionadas**, las acciones locales se permitirán y habrá opciones adicionales para permitir otras acciones específicas: -- **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 de `actions` y de `github`. For more information, see the [`actions`](https://github.com/actions) and [`github`](https://github.com/github) organizations.{% ifversion fpt or ghes > 3.0 %} -- **Allow Marketplace actions by verified creators:** {% ifversion ghes > 3.0 %}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 %} +- **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 > 3.0 or ghae-issue-5094 %} +- **Permite las acciones de Marketplace de creadores verificados:** {% ifversion ghes > 3.0 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 especificadas:** Puedes restringir los flujos de trabajo para que utilicen las acciones que se encuentren en organizciones y repositorios específicos. Para restringir el acceso a las etiquetas específicas o a los SHA de confirmación de una acción, puedes utilizar la misma sintaxis de `/@` en el flujo de trabajo para seleccionar la acción. Por ejemplo, `actions/javascript-action@v1.0.1` para seleccionar una etiqueta o `actions/javascript-action@172239021f7ba04fe7327647b213799853a9eb89` para seleccionar un SHA. Para obtener más información, consulta la sección "[Encontrar y personalizar las acciones](/actions/learn-github-actions/finding-and-customizing-actions#using-release-management-for-your-custom-actions)". diff --git a/translations/es-ES/data/reusables/actions/autoscaling-parameters.md b/translations/es-ES/data/reusables/actions/autoscaling-parameters.md new file mode 100644 index 0000000000..3af1e5335f --- /dev/null +++ b/translations/es-ES/data/reusables/actions/autoscaling-parameters.md @@ -0,0 +1,3 @@ +- Opcionalmente, autoescalar parámetros para cada agrupación. + - Cantidad mínima de ejecutores inactivos para la agrupación + - Límite de tiempo activo: La cantidad de minutos que un ejecutor debería permanecer activo en la agrupación antes de que esta se reduzca al conteo de los inactivos diff --git a/translations/es-ES/data/reusables/actions/cd-templates-actions.md b/translations/es-ES/data/reusables/actions/cd-templates-actions.md new file mode 100644 index 0000000000..c6eeec90db --- /dev/null +++ b/translations/es-ES/data/reusables/actions/cd-templates-actions.md @@ -0,0 +1,3 @@ +{% data variables.product.product_name %} offers CD workflow templates for several popular services, such as Azure Web App. To learn how to get started using a workflow template, see "[Using workflow templates](/actions/learn-github-actions/using-workflow-templates)" or [browse the full list of deployment workflow templates](https://github.com/actions/starter-workflows/tree/main/deployments). You can also check out our more detailed guides for specific deployment workflows, such as "[Deploying to Azure App Service](/actions/deployment/deploying-to-azure-app-service)." + +Many service providers also offer actions on {% data variables.product.prodname_marketplace %} for deploying to their service. For the full list, see [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?category=deployment&type=actions). \ No newline at end of file diff --git a/translations/es-ES/data/reusables/actions/delete-env-key.md b/translations/es-ES/data/reusables/actions/delete-env-key.md new file mode 100644 index 0000000000..380ebe5653 --- /dev/null +++ b/translations/es-ES/data/reusables/actions/delete-env-key.md @@ -0,0 +1 @@ +If you configured a deployment environment, change the value of `environment` to be the name of your environment. If you did not configure an environment{% ifversion fpt %} or if your workflow is in a private repository and you do not use {% data variables.product.prodname_ghe_cloud %}{% endif %}, delete the `environment` key. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/actions/environment-deployment-event.md b/translations/es-ES/data/reusables/actions/environment-deployment-event.md new file mode 100644 index 0000000000..1a014fbfc6 --- /dev/null +++ b/translations/es-ES/data/reusables/actions/environment-deployment-event.md @@ -0,0 +1 @@ +When a workflow job that references an environment runs, it creates a deployment object with the `environment` property set to the name of your environment. As the workflow progresses, it also creates deployment status objects with the `environment` property set to the name of your environment, the `environment_url` property set to the URL for environment (if specified in the workflow), and the `state` property set to the status of the job. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/actions/environment-example.md b/translations/es-ES/data/reusables/actions/environment-example.md new file mode 100644 index 0000000000..95ed6bc816 --- /dev/null +++ b/translations/es-ES/data/reusables/actions/environment-example.md @@ -0,0 +1,45 @@ +You can specify an environment for each job in your workflow. To do so, add a `jobs..environment` key followed by the name of the environment. + +For example, this workflow will use an environment called `production`. + +```yaml +name: Deployment + +on: + push: + branches: + - main + +jobs: + deployment: + runs-on: ubuntu-latest + environment: production + steps: + - name: deploy + # ...deployment-specific steps +``` + +When the above workflow runs, the `deployment` job will be subject to any rules configured for the `production` environment. For example, if the environment requires reviewers, the job will pause until one of the reviewers approves the job. + +You can also specify a URL for the environment. The specified URL will appear on the deployments page for the repository (accessed by clicking **Environments** on the home page of your repository) and in the visualization graph for the workflow run. If a pull request triggered the workflow, the URL is also displayed as a **View deployment** button in the pull request timeline. + +```yaml +name: Deployment + +on: + push: + branches: + - main + +jobs: + deployment: + runs-on: ubuntu-latest + environment: + name: production + url: https://github.com + steps: + - name: deploy + # ...deployment-specific steps +``` + +![Workflow graph with URL](/assets/images/help/images/deploy-graph.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/actions/message-annotation-explanation.md b/translations/es-ES/data/reusables/actions/message-annotation-explanation.md index fab91b5275..d03e71faec 100644 --- a/translations/es-ES/data/reusables/actions/message-annotation-explanation.md +++ b/translations/es-ES/data/reusables/actions/message-annotation-explanation.md @@ -1 +1 @@ -This message will create an annotation, which can associate the message with a particular file in your repository. Optionally, your message can specify a position within the file. +Este mensaje creará una anotación, la cual puede asociar el mensaje con un archivo particular de tu repositorio. Opcionalmente, tu mensaje puede especificar una posición dentro del archivo. diff --git a/translations/es-ES/data/reusables/actions/proxy-considerations.md b/translations/es-ES/data/reusables/actions/proxy-considerations.md index f5a628f9c0..614e775622 100644 --- a/translations/es-ES/data/reusables/actions/proxy-considerations.md +++ b/translations/es-ES/data/reusables/actions/proxy-considerations.md @@ -1 +1 @@ -If {% data variables.product.prodname_actions %} is enabled for your enterprise, only HTTP proxies are supported. SOCK5 and HTTPS proxies and Polipo are not supported. \ No newline at end of file +Si se habilitan las {% data variables.product.prodname_actions %} para tu empresa, solo los proxies HTTP serán compatibles. No son compatibles los proxies SOCK5, HTTPS y Polipo. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/actions/reusable-workflow-artifacts.md b/translations/es-ES/data/reusables/actions/reusable-workflow-artifacts.md new file mode 100644 index 0000000000..7a74baffa9 --- /dev/null +++ b/translations/es-ES/data/reusables/actions/reusable-workflow-artifacts.md @@ -0,0 +1,3 @@ +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +Todas las acciones y flujos de trabajo a las que se les llama desde dentro de una ejecución tienen acceso de escritura a los artefactos de dicha ejecución. +{% endif %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/actions/reusable-workflows.md b/translations/es-ES/data/reusables/actions/reusable-workflows.md new file mode 100644 index 0000000000..07b541dcf3 --- /dev/null +++ b/translations/es-ES/data/reusables/actions/reusable-workflows.md @@ -0,0 +1,5 @@ +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## Reutilizar flujos de trabajo + +Puedes llamar a un flujo de trabajo desde dentro de otro. Esto te permite reutilizar flujos de trabajo, evitando la duplicación y haciendo que tus flujos se puedan mantener mejor. Para obtener más información, consulta la sección "[Reutilizar flujos de trabajo](/actions/learn-github-actions/reusing-workflows)". +{% endif %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/actions/runner-name-description.md b/translations/es-ES/data/reusables/actions/runner-name-description.md new file mode 100644 index 0000000000..960601a74d --- /dev/null +++ b/translations/es-ES/data/reusables/actions/runner-name-description.md @@ -0,0 +1 @@ +El nombre del ejecutor que ejecuta el job. diff --git a/translations/es-ES/data/reusables/actions/uses-keyword-example.md b/translations/es-ES/data/reusables/actions/uses-keyword-example.md new file mode 100644 index 0000000000..fac21c8a9f --- /dev/null +++ b/translations/es-ES/data/reusables/actions/uses-keyword-example.md @@ -0,0 +1,7 @@ +```yaml +jobs: + call-workflow-1: + uses: octo-org/this-repo/.github/workflows/workflow-1.yml@172239021f7ba04fe7327647b213799853a9eb89 + call-workflow-2: + uses: octo-org/another-repo/.github/workflows/workflow-2.yml@v1 +``` \ No newline at end of file diff --git a/translations/es-ES/data/reusables/actions/workflow-organization-templates.md b/translations/es-ES/data/reusables/actions/workflow-organization-templates.md new file mode 100644 index 0000000000..5625321c8a --- /dev/null +++ b/translations/es-ES/data/reusables/actions/workflow-organization-templates.md @@ -0,0 +1 @@ +Las plantillas de flujo de trabajo permiten a toda persona de tu organización que tenga permiso de crear flujos de trabajo hacerlo más rápida y fácilmente. Cuando creas un flujo de trabajo nuevo, puedes elegir una plantilla para que haga por ti algo o todo el trabajo de escribir el flujo. Puedes usar plantillas de flujo de trabajo como lugar de inicio para crear tu flujo de trabajo personalizado o usarlos tal como están. Esto no solo ahorra tiempo, sino que promueve la consistencia y las mejores prácticas a lo largo de tu organización. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/actions/workflow-run-approve-public-fork.md b/translations/es-ES/data/reusables/actions/workflow-run-approve-public-fork.md index a8c663cb8a..33b58d3d2d 100644 --- a/translations/es-ES/data/reusables/actions/workflow-run-approve-public-fork.md +++ b/translations/es-ES/data/reusables/actions/workflow-run-approve-public-fork.md @@ -1,3 +1,9 @@ Cualquiera puede bifurcar un repositorio público y luego emitir una solicitud de cambios que proponga cambios en los flujos de trabajo de {% data variables.product.prodname_actions %} del mismo. Aunque los flujos de trabajo de las bifurcaciones no tienen acceso a datos sensibles tales como los secretos, pueden ser molestos para los mantenedores si se modifican para fines de abuso. Para ayudar a prevenir esto, los flujos de trabajo sobre las solicitudes de cambio en los repositorios públicos de algunos contribuyentes no se ejecutarán automáticamente y podrían necesitar aprobarse primero. Predeterminadamente, todos los contribuyentes de primera vez necesitan aprobación para ejecutar flujos de trabajo. + +{% note %} + +**Note:** Workflows triggered by `pull_request_target` events are run in the context of the base branch. Since the base branch is considered trusted, workflows triggered by these events will always run, regardless of approval settings. + +{% endnote %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/advanced-security/getting-the-most-from-your-license.md b/translations/es-ES/data/reusables/advanced-security/getting-the-most-from-your-license.md index 26402ee670..38ed49b0fc 100644 --- a/translations/es-ES/data/reusables/advanced-security/getting-the-most-from-your-license.md +++ b/translations/es-ES/data/reusables/advanced-security/getting-the-most-from-your-license.md @@ -3,4 +3,4 @@ Cuando decides qué repositorios y organizaciones priorizar para la {% data vari - Las bases de código que son más críticas para el éxito de tu empresa. Estos son los proyectos para los cuales la introducción de código vulnerable, los secretos de código rígido, o las dependencias vulnerables tendrían el mayor impacto en tu empresa. - Las bases de código con la frecuencia de confirmación más alta. Estos son los proyectos que se desarrollan de forma más activa y, por consecuencia, hay un riesgo mayor para que se introduzcan problemas de seguridad. -When you have enabled {% data variables.product.prodname_GH_advanced_security %} for these organizations or repositories, assess which other codebases you could add without incurring billing for unique committers. Finally, review the remaining important and busy codebases. {% ifversion fpt or ghes %}If you want to increase the number of seats in your license, contact {% data variables.contact.contact_enterprise_sales %}.{% endif %} +Si habilitaste {% data variables.product.prodname_GH_advanced_security %} para estas organizaciones o repositorios, valor qué otras bases de código podrías agregar sin incurrir en un cargo para los confirmantes únicos. Finalmente, revisa las bases de código restantes que sean importantes y estén ocupadas. {% ifversion fpt or ghes %}Si quieres incrementar la cantidad de plazas en tu licencia, contacta a {% data variables.contact.contact_enterprise_sales %}.{% endif %} diff --git a/translations/es-ES/data/reusables/advanced-security/note-org-enable-uses-seats.md b/translations/es-ES/data/reusables/advanced-security/note-org-enable-uses-seats.md index a75038058f..bfd9ec8483 100644 --- a/translations/es-ES/data/reusables/advanced-security/note-org-enable-uses-seats.md +++ b/translations/es-ES/data/reusables/advanced-security/note-org-enable-uses-seats.md @@ -2,6 +2,6 @@ {% note %} **Nota:** Si habilitas -{% data variables.product.prodname_GH_advanced_security %}, los confirmantes de estos repositorios utilizarán las plazas en tu licencia de {% data variables.product.prodname_GH_advanced_security %}. Esta opción se inhabilita si excediste la capacidad de tu licencia. {% ifversion fpt %}For more information, see "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)."{% endif %} +{% data variables.product.prodname_GH_advanced_security %}, los confirmantes de estos repositorios utilizarán las plazas en tu licencia de {% data variables.product.prodname_GH_advanced_security %}. Esta opción se inhabilita si excediste la capacidad de tu licencia. {% ifversion fpt %}Para obtener más información, consulta la sección "[Acerca de la facturación para la {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)".{% endif %} {% endnote %} {% endif %} diff --git a/translations/es-ES/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md b/translations/es-ES/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md index 2ed4d8e08a..c964453a72 100644 --- a/translations/es-ES/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md +++ b/translations/es-ES/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md @@ -1,7 +1,7 @@ 1. Ingresa los detalles de tu patrón personalizado nuevo: 1. Debes proporcionar por lo menos el nombre de tu patrón y una expresión regular para el formato de tu patrón secreto. 1. Puedes hacer clic en **{% octicon "chevron-down" aria-label="down" %} Más opciones** para proporcionar otro tipo de contenido circundante o requisitos de coincidencia adicionales para el formato de secreto. - 1. Provide a sample test string to make sure your configuration is matching the patterns you expect. + 1. Proporciona una secuencia de pruebas de muestra para asegurarte de que tu configuración empate con los patrones que esperas. ![Crear un formato de patrón personalizado del {% data variables.product.prodname_secret_scanning %}](/assets/images/help/repository/secret-scanning-create-custom-pattern.png) -1. When you are satisfied with your new custom pattern, click {% ifversion fpt or ghes > 3.2 or ghae-next %}**Create pattern**{% elsif ghes = 3.2 %}**Create custom pattern**{% endif %}. +1. Cuando estés satisfecho con tu patrón personalizado nuevo, haz clic en {% ifversion fpt or ghes > 3.2 or ghae-next %}**Crear patrón**{% elsif ghes = 3.2 %}**Crear patrón personalizado**{% endif %}. diff --git a/translations/es-ES/data/reusables/advanced-security/secret-scanning-new-custom-pattern.md b/translations/es-ES/data/reusables/advanced-security/secret-scanning-new-custom-pattern.md index 9239b55773..19223f910e 100644 --- a/translations/es-ES/data/reusables/advanced-security/secret-scanning-new-custom-pattern.md +++ b/translations/es-ES/data/reusables/advanced-security/secret-scanning-new-custom-pattern.md @@ -1 +1 @@ -1. Under "{% data variables.product.prodname_secret_scanning_caps %}", under "Custom patterns", click {% ifversion fpt or ghes > 3.2 or ghae-next %}**New pattern**{% elsif ghes = 3.2 %}**New custom pattern**{% endif %}. \ No newline at end of file +1. Debajo de "{% data variables.product.prodname_secret_scanning_caps %}", debajo de "Patrones personalizados", haz clic en {% ifversion fpt or ghes > 3.2 or ghae-next %}**Patrón nuevo**{% elsif ghes = 3.2 %}**Patrón personalizado nuevo**{% endif %}. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/apps/api-rate-limits-non-ghec.md b/translations/es-ES/data/reusables/apps/api-rate-limits-non-ghec.md index 166c6fc1fd..eecdf162b3 100644 --- a/translations/es-ES/data/reusables/apps/api-rate-limits-non-ghec.md +++ b/translations/es-ES/data/reusables/apps/api-rate-limits-non-ghec.md @@ -1 +1 @@ -{% data variables.product.prodname_github_apps %} making server-to-server requests use the installation's minimum rate limit of 5,000 requests per hour. Las instalaciones de organización con más de 20 usuarios reciben 50 solicitudes adicionales por hora para cada usuario. Las instalaciones que tienen más de 20 repositorios reciben otras 50 solicitudes adicionales por hora para cada repositorio. El límite de tasa máximo para una instalación es de 12,500 solicitudes por hora. +Las {% data variables.product.prodname_github_apps %} que hagan solicitudes de servidor a servidor utilizan el límite de tasa mínimo de la instalación, el cual es de 5,000 solicitudes por hora. Las instalaciones de organización con más de 20 usuarios reciben 50 solicitudes adicionales por hora para cada usuario. Las instalaciones que tienen más de 20 repositorios reciben otras 50 solicitudes adicionales por hora para cada repositorio. El límite de tasa máximo para una instalación es de 12,500 solicitudes por hora. diff --git a/translations/es-ES/data/reusables/apps/oauth-auth-vary-response.md b/translations/es-ES/data/reusables/apps/oauth-auth-vary-response.md new file mode 100644 index 0000000000..b76fef614b --- /dev/null +++ b/translations/es-ES/data/reusables/apps/oauth-auth-vary-response.md @@ -0,0 +1 @@ +You can also receive the response in different formats if you provide the format in the `Accept` header. For example, `Accept: application/json` or `Accept: application/xml`: diff --git a/translations/es-ES/data/reusables/apps/oauth-token-limit.md b/translations/es-ES/data/reusables/apps/oauth-token-limit.md index ee00b69f78..f1ed36e30f 100644 --- a/translations/es-ES/data/reusables/apps/oauth-token-limit.md +++ b/translations/es-ES/data/reusables/apps/oauth-token-limit.md @@ -1 +1 @@ -Hay un límite de diez tokens que se emite por combinación de usuario/aplicación/alcance. If an application creates more than 10 tokens for the same user and the same scopes, the oldest tokens with the same user/application/scope combination will be revoked. \ No newline at end of file +Hay un límite de diez tokens que se emite por combinación de usuario/aplicación/alcance. Si una aplicación crea más de 10 tokens para el mismo usuario y los mismos alcances, se revocarán los tokens más antiguos con la misma combinación de usuario/aplicación/alcance. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/billing/about-invoices-for-enterprises.md b/translations/es-ES/data/reusables/billing/about-invoices-for-enterprises.md index 87b56d3b14..81f79ba4b4 100644 --- a/translations/es-ES/data/reusables/billing/about-invoices-for-enterprises.md +++ b/translations/es-ES/data/reusables/billing/about-invoices-for-enterprises.md @@ -1 +1 @@ -For invoiced {% data variables.product.prodname_enterprise %} customers, {% data variables.product.company_short %} bills through an enterprise account on {% data variables.product.prodname_dotcom_the_website %}. Each invoice includes a single bill charge for all of your paid {% data variables.product.prodname_dotcom_the_website %} services and any {% data variables.product.prodname_ghe_server %} instances. +Para los clientes a los que se les factura por {% data variables.product.prodname_enterprise %}, {% data variables.product.company_short %} envía las facturas mediante una cuenta empresarial en {% data variables.product.prodname_dotcom_the_website %}. Cada factura incluye un cargo único para todos tus servicios de pago de {% data variables.product.prodname_dotcom_the_website %} y por cualquier instancia de {% data variables.product.prodname_ghe_server %}. diff --git a/translations/es-ES/data/reusables/billing/email-notifications.md b/translations/es-ES/data/reusables/billing/email-notifications.md index 3dd296397f..2b9d224cc8 100644 --- a/translations/es-ES/data/reusables/billing/email-notifications.md +++ b/translations/es-ES/data/reusables/billing/email-notifications.md @@ -1,3 +1,3 @@ -Email notifications are sent to account owners and billing managers when spending reaches 50%, 75%, and 90% of your account's included usage and when spending reaches 50%, 75%, and 90% of your account's spending limit. +Las notificaciones por correo electrónico se envían a los propietarios de cuenta y gerentes de facturación cuando los gastos llegan a 50%, 75%, y 90% del uso incluido en tu cuenta y cuando llegan a 50%, 75%, y 90% del límite de gastos de la misma. -You can disable these notifications anytime by navigating to the bottom of the **Spending Limit** page. \ No newline at end of file +Puedes inhabilitar estas notificaciones en cualquier momento si navegas al final de la página del **Límite de Gastos**. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/billing/ghes-with-no-enterprise-account.md b/translations/es-ES/data/reusables/billing/ghes-with-no-enterprise-account.md index ea5183e6af..1e6164addf 100644 --- a/translations/es-ES/data/reusables/billing/ghes-with-no-enterprise-account.md +++ b/translations/es-ES/data/reusables/billing/ghes-with-no-enterprise-account.md @@ -1 +1 @@ -{% data variables.product.prodname_enterprise %} customers with no enterprise account on {% data variables.product.prodname_dotcom_the_website %} can view invoices and payment history on the [{% data variables.product.prodname_enterprise %} website](https://enterprise.github.com/login). {% data reusables.enterprise-accounts.to-upgrade-or-get-started %} +Los clientes de {% data variables.product.prodname_enterprise %} sin una cuenta empresarial en {% data variables.product.prodname_dotcom_the_website %} pueden ver las facturas e historial de pagos en el [sitio web de {% data variables.product.prodname_enterprise %}](https://enterprise.github.com/login). {% data reusables.enterprise-accounts.to-upgrade-or-get-started %} diff --git a/translations/es-ES/data/reusables/classroom/about-online-ides.md b/translations/es-ES/data/reusables/classroom/about-online-ides.md index f0f8c18688..088798fb86 100644 --- a/translations/es-ES/data/reusables/classroom/about-online-ides.md +++ b/translations/es-ES/data/reusables/classroom/about-online-ides.md @@ -1 +1 @@ -You can optionally configure an assignment to use an integrated development environment (IDE). IDEs allow your students to write code, run programs, and collaborate without installing Git and a full development toolchain on the student's computer. If you choose an IDE for an assignment, students can still check out and run code locally on a computer with the necessary software. +Opcionalmente, puedes configurar una tarea para utilizar un ambiente de desarrollo integrado (IDE). Los IDE permiten a los alumnos escribir código, ejecutar programas y colaborar sin instalar Git y contar con una cadena de herramientas de desarrollo integral en la computadora del alumno. Si eliges un IDE para una tarea, los alumnos aún pueden verificar y ejecutar el código localmente en una computadora con el software necesario. diff --git a/translations/es-ES/data/reusables/classroom/assignments-guide-choose-an-online-ide.md b/translations/es-ES/data/reusables/classroom/assignments-guide-choose-an-online-ide.md index 894af05249..90fc9b9aea 100644 --- a/translations/es-ES/data/reusables/classroom/assignments-guide-choose-an-online-ide.md +++ b/translations/es-ES/data/reusables/classroom/assignments-guide-choose-an-online-ide.md @@ -1,4 +1,4 @@ -To choose an IDE for the assignment, select the Add an editor drop-down menu and click the IDE you'd like your students to use. +Para elegir un IDE para la tarea, selecciona el menú desplegable de "Agregar un editor" y haz clic en el IDE que te gustaría que utilizaran tus alumnos.
    Utilizar el menú desplegable de 'Seleccionar un IDE en línea' para dar clic en un IDE en línea para la tarea diff --git a/translations/es-ES/data/reusables/classroom/assignments-guide-choose-visibility.md b/translations/es-ES/data/reusables/classroom/assignments-guide-choose-visibility.md index dcbced27ac..cf0e4b5aa0 100644 --- a/translations/es-ES/data/reusables/classroom/assignments-guide-choose-visibility.md +++ b/translations/es-ES/data/reusables/classroom/assignments-guide-choose-visibility.md @@ -1,6 +1,6 @@ Los repositorios de una tarea pueden ser públicos o privados. Si utilizas repositorios privados, solo el alumno o equipo puede ver la retroalimentación que proporciones. -También puedes decidir si quieres otorgar a los alumnos permisos administrativos en el repositorio para una tarea. Otorga permisos administrativos si es que el alumno debe realizar tareas administrativas en el repositorio de tareas. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)" and "[Repository permission levels for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)." +También puedes decidir si quieres otorgar a los alumnos permisos administrativos en el repositorio para una tarea. Otorga permisos administrativos si es que el alumno debe realizar tareas administrativas en el repositorio de tareas. Para obtener más información, consulta las secciones "[Acerca de los repositorios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)" y "[Niveles de permiso de los repositorios para una organización](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)". Selecciona una visibilidad debajo de "Visibilidad del repositorio". Opcionalmente, selecciona **Otorgar a los alumnos acceso administrativo para el repositorio**. diff --git a/translations/es-ES/data/reusables/classroom/assignments-guide-create-the-assignment.md b/translations/es-ES/data/reusables/classroom/assignments-guide-create-the-assignment.md index b6fccb2bee..c633bc3e31 100644 --- a/translations/es-ES/data/reusables/classroom/assignments-guide-create-the-assignment.md +++ b/translations/es-ES/data/reusables/classroom/assignments-guide-create-the-assignment.md @@ -1,5 +1,5 @@ 1. Inicia sesión en {% data variables.product.prodname_classroom_with_url %}. 1. Navegar a un aula. -1. In the {% octicon "repo" aria-label="The repo icon" %} **Assignments** tab, create the assignment. - - If this your first assignment, click **Create an assignment**. ![Crear tu primera tarea](/assets/images/help/classroom/assignments-create-first-assignment.png) - - Otherwise, click **New assignment**. ![En el botón de 'Tarea nueva'](/assets/images/help/classroom/assignments-click-new-assignment-button.png) +1. Crea la tarea en la pestaña de **Tareas**{% octicon "repo" aria-label="The repo icon" %}. + - Si esta es tu primer tarea, haz clic en **Crear una tarea**. ![Crear tu primera tarea](/assets/images/help/classroom/assignments-create-first-assignment.png) + - De lo contrario, haz clic en **Tarea nueva**. ![En el botón de 'Tarea nueva'](/assets/images/help/classroom/assignments-click-new-assignment-button.png) diff --git a/translations/es-ES/data/reusables/classroom/readme-contains-button-for-online-ide.md b/translations/es-ES/data/reusables/classroom/readme-contains-button-for-online-ide.md index ba12fbf246..a321e8c6f5 100644 --- a/translations/es-ES/data/reusables/classroom/readme-contains-button-for-online-ide.md +++ b/translations/es-ES/data/reusables/classroom/readme-contains-button-for-online-ide.md @@ -1 +1 @@ -When a student accepts an assignment with an IDE, the assignment repository will include a _README.md_ file with a special button at the top of the file. The button links the student directly to the workspace in the IDE. +Cuando un alumno acepta una tarea con un IDE, dicho repositorio incluirá un archivo _README.md_ con un botón especial en la parte superior del archivo. El botón vincula al alumno directamente con el espacio de trabajo en el IDE. diff --git a/translations/es-ES/data/reusables/cli/cli-extensions.md b/translations/es-ES/data/reusables/cli/cli-extensions.md index 4e7f890088..88c0d96d5e 100644 --- a/translations/es-ES/data/reusables/cli/cli-extensions.md +++ b/translations/es-ES/data/reusables/cli/cli-extensions.md @@ -1 +1 @@ -{% data variables.product.prodname_cli %} extensions are custom {% data variables.product.prodname_cli %} commands that anyone can create and use. \ No newline at end of file +Las extensiones del {% data variables.product.prodname_cli %} son comandos personalizados del {% data variables.product.prodname_cli %} que cualquiera puede crear y utilizar. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/cli/cli-features.md b/translations/es-ES/data/reusables/cli/cli-features.md index 32c8116c6d..faca03f31c 100644 --- a/translations/es-ES/data/reusables/cli/cli-features.md +++ b/translations/es-ES/data/reusables/cli/cli-features.md @@ -1,7 +1,7 @@ El {% data variables.product.prodname_cli %} incluye características de {% data variables.product.prodname_dotcom %} tales como: - Ver, crear, clonar, y bifurcar repositorios -- Create, close, edit, and view issues and pull requests +- Crear, cerrar, editar y ver las propuestas y solicitudes de cambio - Revisar, fusionar y hacer diffs con las solicitudes de cambios - Ejecutar, visualizar y listar flujos de trabajo - Crear, listar, visualizar y borrar lanzamientos diff --git a/translations/es-ES/data/reusables/cli/cli-learn-more.md b/translations/es-ES/data/reusables/cli/cli-learn-more.md index 9a7d8272ea..1c30ffab64 100644 --- a/translations/es-ES/data/reusables/cli/cli-learn-more.md +++ b/translations/es-ES/data/reusables/cli/cli-learn-more.md @@ -1,5 +1,5 @@ {% note %} -To learn more about {% data variables.product.prodname_cli %}, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)." +Para aprender más sobre el {% data variables.product.prodname_cli %}, consulta la sección "[Acerca del {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)". {% endnote %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/code-scanning/about-codeql-analysis.md b/translations/es-ES/data/reusables/code-scanning/about-codeql-analysis.md index 543933d4fb..1bd2bb364a 100644 --- a/translations/es-ES/data/reusables/code-scanning/about-codeql-analysis.md +++ b/translations/es-ES/data/reusables/code-scanning/about-codeql-analysis.md @@ -1 +1 @@ -{% data variables.product.prodname_codeql %} is the code analysis engine developed by {% data variables.product.company_short %} to automate security checks. You can analyze your code using {% data variables.product.prodname_codeql %} and display the results as {% data variables.product.prodname_code_scanning %} alerts. +{% data variables.product.prodname_codeql %} es el motor de análisis de código que desarrolló {% data variables.product.company_short %} para automatizar las verificaciones de seguridad. Puedes analizar tu código utilizando {% data variables.product.prodname_codeql %} y mostrando los resultados como alertas del {% data variables.product.prodname_code_scanning %}. diff --git a/translations/es-ES/data/reusables/code-scanning/beta-codeql-packs-cli.md b/translations/es-ES/data/reusables/code-scanning/beta-codeql-packs-cli.md index a3f012cc4d..98636c818a 100644 --- a/translations/es-ES/data/reusables/code-scanning/beta-codeql-packs-cli.md +++ b/translations/es-ES/data/reusables/code-scanning/beta-codeql-packs-cli.md @@ -2,7 +2,7 @@ {% note %} -**Note:** The {% data variables.product.prodname_codeql %} package management functionality, including {% data variables.product.prodname_codeql %} packs, is currently in beta and subject to change. +**Nota:** La funcionalidad de administración de paquetes de {% data variables.product.prodname_codeql %}, incluyendo los paquetes de {% data variables.product.prodname_codeql %}, se encuentra actualmente en beta y está sujeta a cambios. {% endnote %} diff --git a/translations/es-ES/data/reusables/code-scanning/deprecation-codeql-runner.md b/translations/es-ES/data/reusables/code-scanning/deprecation-codeql-runner.md index 2583a9304c..99226e5912 100644 --- a/translations/es-ES/data/reusables/code-scanning/deprecation-codeql-runner.md +++ b/translations/es-ES/data/reusables/code-scanning/deprecation-codeql-runner.md @@ -1,7 +1,7 @@ {% note %} -**Note:** The {% data variables.product.prodname_codeql_runner %} is being deprecated. Please use the [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-cli-binaries/releases) version 2.6.2 or greater instead. -{% data variables.product.prodname_ghe_server %} 3.3 will be the final release series that supports the {% data variables.product.prodname_codeql_runner %}. On {% data variables.product.prodname_ghe_cloud %}, the {% data variables.product.prodname_codeql_runner %} will be supported until March 2022. -For more information, see [the CodeQL runner deprecation](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/). +**Nota:** El {% data variables.product.prodname_codeql_runner %} se va a obsoletizar. Por favor, utiliza la versión 2.6.2 de [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-cli-binaries/releases) o superior en su lugar. +{% data variables.product.prodname_ghe_server %} 3.3 será la última serie de lanzamiento que será compatible con el {% data variables.product.prodname_codeql_runner %}. En {% data variables.product.prodname_ghe_cloud %}, el {% data variables.product.prodname_codeql_runner %} será compatible hasta marzo del 2022. +Para obtener más información, consulta la [obsoletización del ejecutor de CodeQL](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/). {% endnote %} diff --git a/translations/es-ES/data/reusables/code-scanning/run-additional-queries.md b/translations/es-ES/data/reusables/code-scanning/run-additional-queries.md index 07f91fdf44..b7c45be268 100644 --- a/translations/es-ES/data/reusables/code-scanning/run-additional-queries.md +++ b/translations/es-ES/data/reusables/code-scanning/run-additional-queries.md @@ -1,20 +1,20 @@ Cuando utilizas {% data variables.product.prodname_codeql %} para escanear código, el motor de análisis de {% data variables.product.prodname_codeql %} genera una base de datos desde el código y ejecuta consultas en éste. El {% data variables.product.prodname_codeql %} utiliza un conjunto predeterminado de consultas, pero puedes especificar más consultas para que se ejecuten, adicionalmente a las predeterminadas. {% if codeql-packs %} -You can run extra queries if they are part of a -{% data variables.product.prodname_codeql %} pack (beta) published to the {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %} or a {% data variables.product.prodname_ql %} pack stored in a repository. For more information, see "[About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql#about-codeql-queries)." +Puedes ejecutar consultas adicionales si son parte de un +paquete de {% data variables.product.prodname_codeql %} (beta) publicado en el {% data variables.product.prodname_container_registry %} de {% data variables.product.company_short %} o de un paquete de {% data variables.product.prodname_ql %} en un repositorio. Para obtener más información, consulta la sección "[Acerca del {% data variables.product.prodname_code_scanning %} con {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql#about-codeql-queries)". -The options available to specify the additional queries you want to run are: +Las opciones disponibles para especificar las consultas adicionales que quieres ejecutar son: -- `packs` to install one or more {% data variables.product.prodname_codeql %} query packs (beta) and run the default query suite or queries for those packs. -- `queries` to specify a single _.ql_ file, a directory containing multiple _.ql_ files, a _.qls_ query suite definition file, or any combination. Para obtener más información acerca de las definiciones de la suite de consultas, diríjete a la sección "[Crear suites de consultas de {% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/)". +- `packs` para instalar uno o más paquetes de consulta de {% data variables.product.prodname_codeql %} (beta) y ejecutar la suite de consultas predeterminada para estos paquetes. +- `queries` para especificar un archivo sencilo de _.ql_, un directorio que contenga varios archivos de _.ql_, un archivo de definición de suite de consultas _.qls_ o cualquier combinación de estos. Para obtener más información acerca de las definiciones de la suite de consultas, diríjete a la sección "[Crear suites de consultas de {% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/)". -You can use both `packs` and `queries` in the same workflow. +Puedes utilizar tanto `packs` como `queries` en el mismo flujo de trabajo. {% else %} -Any additional queries you want to run must belong to a -{% data variables.product.prodname_ql %} pack in a repository. For more information, see {% ifversion ghes < 3.0 %}"[About {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning#about-codeql)."{% else %}"[About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql#about-codeql-queries)."{% endif %} +Cualquier consulta adicional que quieras ejecutar debe pertenecer a un +paquete de {% data variables.product.prodname_ql %} en un repositorio. Para obtener más información, consulta la sección {% ifversion ghes < 3.0 %}"[Acerca del {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning#about-codeql)".{% else %}"[Acerca del {% data variables.product.prodname_code_scanning %} con {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql#about-codeql-queries)".{% endif %} Puedes especificar un solo archivo _.ql_, un directorio que contenga varios archivos _.ql_, un archivo de definición de suite de consulta _.qls_, o cualquier combinación de éstos. Para obtener más información acerca de las definiciones de la suite de consultas, diríjete a la sección "[Crear suites de consultas de {% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/)". {% endif %} -{% ifversion fpt %}We don't recommend referencing query suites directly from the `github/codeql` repository, like `github/codeql/cpp/ql/src@main`. Puede que dichas consultas no se compilen con la misma versión de {% data variables.product.prodname_codeql %} que se utiliza para tus otras consultas, lo cual puede llevar a que se cometan errores durante el análisis.{% endif %} +{% ifversion fpt %}No te recomendamos referenciar las suites de consultas directamente desde el repositorio de `github/codeql`, como por ejemplo `github/codeql/cpp/ql/src@main`. Puede que dichas consultas no se compilen con la misma versión de {% data variables.product.prodname_codeql %} que se utiliza para tus otras consultas, lo cual puede llevar a que se cometan errores durante el análisis.{% endif %} diff --git a/translations/es-ES/data/reusables/code-scanning/upload-sarif-alert-limit.md b/translations/es-ES/data/reusables/code-scanning/upload-sarif-alert-limit.md index 3df69eedf5..f8b57d126a 100644 --- a/translations/es-ES/data/reusables/code-scanning/upload-sarif-alert-limit.md +++ b/translations/es-ES/data/reusables/code-scanning/upload-sarif-alert-limit.md @@ -1,5 +1,8 @@ {% note %} -**Nota:** La carga de SARIF es compatible con un máximo de {% ifversion ghae-next or fpt or ghes > 3.0 %}5000{% else %}1000{% endif %} resultados por carga. Cualquier resultado que sobrepase este límite se ignorará. Si una herramienta genera demasiados resultados, debes actualizar la configuración para enfocarte en los resultados de las reglas o consultas más importantes. +**Notas:** +- SARIF upload supports a maximum of {% ifversion ghae-next or fpt or ghes > 3.0 %}5000{% else %}1000{% endif %} results per upload. Cualquier resultado que sobrepase este límite se ignorará. Si una herramienta genera demasiados resultados, debes actualizar la configuración para enfocarte en los resultados de las reglas o consultas más importantes. + + - For each upload, SARIF upload supports a maximum size of 10 MB for the `gzip`-compressed SARIF file. Any uploads over this limit will be rejected. If your SARIF file is too large because it contains too many results, you should update the configuration to focus on results for the most important rules or queries. {% endnote %} diff --git a/translations/es-ES/data/reusables/codespaces/availability.md b/translations/es-ES/data/reusables/codespaces/availability.md index df1d8f27be..7125be9c54 100644 --- a/translations/es-ES/data/reusables/codespaces/availability.md +++ b/translations/es-ES/data/reusables/codespaces/availability.md @@ -1 +1 @@ -Codespaces are available for repositories owned by organizations using {% data variables.product.prodname_team %} and {% data variables.product.prodname_ghe_cloud %}. +Los Codespaces están disponibles para los repositorios que pertenecen a las organizaciones que utilizan {% data variables.product.prodname_team %} y {% data variables.product.prodname_ghe_cloud %}. diff --git a/translations/es-ES/data/reusables/codespaces/codespaces-billing.md b/translations/es-ES/data/reusables/codespaces/codespaces-billing.md index f712aef7f1..60393bb900 100644 --- a/translations/es-ES/data/reusables/codespaces/codespaces-billing.md +++ b/translations/es-ES/data/reusables/codespaces/codespaces-billing.md @@ -1,9 +1,9 @@ -{% data variables.product.prodname_codespaces %} are billed in US dollars (USD) according to their compute and storage usage. +Los {% data variables.product.prodname_codespaces %} se cobran en dólares estadounidenses (USD) de acuerdo con su uso de almacenamiento y cálculo. -### Calculating compute usage -The total number of uptime minutes for which the {% data variables.product.prodname_codespaces %} instances are active. Compute usage is calculated by the actual number of minutes used by all codespaces. These totals are reported to the billing service daily, and are billed monthly. +### Calcular el uso de cómputo +La cantidad total de tiempo de actividad en minutos durante la cual están activas las instancias de {% data variables.product.prodname_codespaces %}. El uso de cómputo se calcula mediante la cantidad real de minutos que utilizan todos los codespaces. Estos totales se reportan al servicio de facturación diariamente y se cobran mensualmente. -Uptime is controlled by stopping your codespace which can be done manually or based on period of inactivity. For more information, see "[Closing or stopping your codespace](/codespaces/getting-started/deep-dive#closing-or-stopping-your-codespace)". +El tiempo de actividad se controla deteniendo tu codespace, lo cual puede hacerse manualmente o con base en un periodo de inactividad. Para obtener más información, consulta la sección "[Cerrar o detener tu codespace](/codespaces/getting-started/deep-dive#closing-or-stopping-your-codespace)". -### Calculating storage usage -For {% data variables.product.prodname_codespaces %} billing purposes, this includes all storage used by all codespaces in your account. This includes any files used by the codespaces, such as cloned repositories, configuration files, and extensions, among others. These totals are reported to the billing service daily, and are billed monthly. Al final del mes, {% data variables.product.prodname_dotcom %} redondea tu almacenamiento al número de MB más cercano. +### Calcular el uso de almacenamiento +Para propósitos de facturación de {% data variables.product.prodname_codespaces %}, esto incluye todo el almacenamiento que utilizan todos los codespaces en tu cuenta. Esto incluye cualquier archivo que utilicen los codespaces, tales como los repositorios clonados, archivos de configuración y extensiones, entre otros. Estos totales se reportan al servicio de facturación diariamente y se cobran mensualmente. Al final del mes, {% data variables.product.prodname_dotcom %} redondea tu almacenamiento al número de MB más cercano. diff --git a/translations/es-ES/data/reusables/codespaces/codespaces-machine-types.md b/translations/es-ES/data/reusables/codespaces/codespaces-machine-types.md index 0d04ac4e3c..2336efbd81 100644 --- a/translations/es-ES/data/reusables/codespaces/codespaces-machine-types.md +++ b/translations/es-ES/data/reusables/codespaces/codespaces-machine-types.md @@ -1 +1 @@ -You can run your codespace on a choice of remote machine, from 2 cores to 32 cores. Cada una de estas tiene un nivel de recursos y de facturación diferentes. For information, see "[About billing for Codespaces](/github/developing-online-with-codespaces/about-billing-for-codespaces)." +Puedes ejecutar tu codespace en la máquina remota de tu elección, desde 2 hasta 32 núcleos. Cada una de estas tiene un nivel de recursos y de facturación diferentes. Para obtener más información, consulta la sección "[Acerca de la facturación para los Codespaces](/github/developing-online-with-codespaces/about-billing-for-codespaces)". diff --git a/translations/es-ES/data/reusables/codespaces/codespaces-spending-limit-requirement.md b/translations/es-ES/data/reusables/codespaces/codespaces-spending-limit-requirement.md index a91b3595d3..d52e73be01 100644 --- a/translations/es-ES/data/reusables/codespaces/codespaces-spending-limit-requirement.md +++ b/translations/es-ES/data/reusables/codespaces/codespaces-spending-limit-requirement.md @@ -1,7 +1,7 @@ {% note %} -**Note:** You must set a spending limit before you can use {% data variables.product.prodname_codespaces %}. +**Nota:** Debes configurar un límite de gastos antes de pode utilizar {% data variables.product.prodname_codespaces %}. {% endnote %} -By default, your organization or enterprise will have a {% data variables.product.prodname_codespaces %} spending limit of $0, which prevents new codespaces from being created or existing codespaces from being opened. To allow your users to create codespaces in your organization, set the limit to a value higher than $0. +Predeterminadamente, tu organización o empresa tendrá un límite de gastos de {% data variables.product.prodname_codespaces %} de $0, lo cual previene que se creen codespaces nuevos o que se abran los existentes. Para permitir que tus usuarios creen codespaces en tu organización, configura el límite a un valor mayor a $0. diff --git a/translations/es-ES/data/reusables/codespaces/concurrent-codespace-limit.md b/translations/es-ES/data/reusables/codespaces/concurrent-codespace-limit.md index 4c41f7fa98..c77cbc1af1 100644 --- a/translations/es-ES/data/reusables/codespaces/concurrent-codespace-limit.md +++ b/translations/es-ES/data/reusables/codespaces/concurrent-codespace-limit.md @@ -1 +1 @@ -Puedes crear más de un codespace por repositorio o incluso por rama. However, each user account has a limit of 10 codespaces. Si has alcanzado el límite y quieres crear un codespace nuevo, primero debes borrar un codespace. +Puedes crear más de un codespace por repositorio o incluso por rama. Sin embargo, cada cuenta de usuario tiene un límite de 10 codespaces. Si has alcanzado el límite y quieres crear un codespace nuevo, primero debes borrar un codespace. diff --git a/translations/es-ES/data/reusables/codespaces/contact-support.md b/translations/es-ES/data/reusables/codespaces/contact-support.md index b3ea0615e1..8a37c76058 100644 --- a/translations/es-ES/data/reusables/codespaces/contact-support.md +++ b/translations/es-ES/data/reusables/codespaces/contact-support.md @@ -1 +1 @@ -you may need to contact support. For more information, see "[Working with support](/codespaces/troubleshooting/working-with-support-for-codespaces)." +podrías necesitar contactar a soporte. Para obtener más información, consulta la sección "[Trabajar con soporte](/codespaces/troubleshooting/working-with-support-for-codespaces)". diff --git a/translations/es-ES/data/reusables/codespaces/create-or-switch-branch.md b/translations/es-ES/data/reusables/codespaces/create-or-switch-branch.md new file mode 100644 index 0000000000..b74ce8de58 --- /dev/null +++ b/translations/es-ES/data/reusables/codespaces/create-or-switch-branch.md @@ -0,0 +1,3 @@ +1. Si la rama actual no se muestra en la barra de estado, en la parte inferior de tu codespace, haz clic derecho en la barra de estado y selecciona **Control de código fuente**. +1. Haz clic en el nombre de rama en la barra de estado. ![La rama en la barra de estado](/assets/images/help/codespaces/branch-in-status-bar.png) +1. En el menú desplegable, haz clic en la rama a la que quieras cambiar o ingresa el nombre de una rama nueva y haz clic en **Crear rama nueva**. ![Elige del menú de la rama](/assets/images/help/codespaces/create-new-branch.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/codespaces/exporting-changes.md b/translations/es-ES/data/reusables/codespaces/exporting-changes.md index c4c642faee..a883132563 100644 --- a/translations/es-ES/data/reusables/codespaces/exporting-changes.md +++ b/translations/es-ES/data/reusables/codespaces/exporting-changes.md @@ -1 +1 @@ -If you hit a spending limit, you will no longer be able to create or resume your codespaces. You can still [export any work in progress changes to a new branch](/codespaces/troubleshooting/exporting-changes-to-a-branch). \ No newline at end of file +Si llegas a un límite de gastos, ya no podrás crear o reanudar tus codespaces. Aún puedes [exportar cualquier cambio de tu trabajo en curso a una nueva rama](/codespaces/troubleshooting/exporting-changes-to-a-branch). \ No newline at end of file diff --git a/translations/es-ES/data/reusables/codespaces/review-pr.md b/translations/es-ES/data/reusables/codespaces/review-pr.md index cf263511e8..9e6b9f7fc8 100644 --- a/translations/es-ES/data/reusables/codespaces/review-pr.md +++ b/translations/es-ES/data/reusables/codespaces/review-pr.md @@ -1,5 +1,5 @@ -1. Open the pull request in a codespace, as described in "[Opening a pull request](/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests#opening-a-pull-request-in-codespaces)." -2. In the Activity Bar, click the **GitHub Pull Request** view. This view only appears when you open a pull request in a codespace. ![Option to open PR in a codespace](/assets/images/help/codespaces/github-pr-view.png) -3. To review a specific file, click the **Open File** icon in the Side Bar. ![Option to open PR in a codespace](/assets/images/help/codespaces/changes-in-files.png) -4. To add review comments, click the **+** icon next to the line number. Type your review comment and then click **Start Review**. ![Option to open PR in a codespace](/assets/images/help/codespaces/start-review.png) -5. When you are finished adding review comments, from the Side Bar you can choose to either submit the comments, approve the changes, or request changes. ![Option to open PR in a codespace](/assets/images/help/codespaces/submit-review.png) +1. Abre la solicitud de cambios en un codespace, de acuerdo con lo descrito en "[Abrir una solicitud de cambios](/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests#opening-a-pull-request-in-codespaces)". +2. En la barra de actividad, haz clic en la vista de **Solicitud de cambios de GitHub**. Esta vista solo se muestra cuando abres una solicitud de cambios en un codespace. ![Opción para abrir una solicitud de cambios en un codespace](/assets/images/help/codespaces/github-pr-view.png) +3. Para revisar un archivo específico, haz clic en el icono de **Abrir archivo** en la barra lateral. ![Opción para abrir una solicitud de cambios en un codespace](/assets/images/help/codespaces/changes-in-files.png) +4. Para agregar comentarios, haz clic en el icono de **+** junto al número de línea. Teclea tu comentario de revisión y luego haz clic en **Comenzar revisión**. ![Opción para abrir una solicitud de cambios en un codespace](/assets/images/help/codespaces/start-review.png) +5. Cuando termines de revisar los comentarios, desde la barra lateral, puedes elegir ya sea emitirlos, aprobar los cambios, o solicitar cambios. ![Opción para abrir una solicitud de cambios en un codespace](/assets/images/help/codespaces/submit-review.png) diff --git a/translations/es-ES/data/reusables/codespaces/source-control-commit-changes.md b/translations/es-ES/data/reusables/codespaces/source-control-commit-changes.md new file mode 100644 index 0000000000..76317ee834 --- /dev/null +++ b/translations/es-ES/data/reusables/codespaces/source-control-commit-changes.md @@ -0,0 +1,4 @@ +{% data reusables.codespaces.source-control-display-dark %} +1. Para probar tus cambios, haz clic en **+** junto al archivo que cambiaste o junto a **Cambios** si cambiaste archivos múltiples y quieres probarlos todos. ![Barra lateral de control de código fuente con el botón de preparación resaltado](/assets/images/help/codespaces/codespaces-commit-stage.png) +1. Teclea un mensaje de confirmación que describa el cambio que hiciste. ![Barra de control de código fuente con un mensaje de confirmación](/assets/images/help/codespaces/codespaces-commit-commit-message.png) +1. Para confirmar tus cambios planeados, haz clic en la marca de verificación en la parte superior de la barra lateral del control de código fuente. ![Haz clic en el icono de verificación](/assets/images/help/codespaces/codespaces-commit-checkmark-icon.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/codespaces/source-control-pull-request.md b/translations/es-ES/data/reusables/codespaces/source-control-pull-request.md new file mode 100644 index 0000000000..2cb222039f --- /dev/null +++ b/translations/es-ES/data/reusables/codespaces/source-control-pull-request.md @@ -0,0 +1,3 @@ +1. Después de haber confirmado los cambios en tu copia local del repositorio, haz clic en el icono de **Crear solicitud de cambios**. ![Barra lateral de control de código fuente con el botón de preparación resaltado](/assets/images/help/codespaces/codespaces-commit-pr-button.png) +1. Verifica que el repositorio y la rama local desde la que estás haciendo la fusión y la rama y repositorio remotos hacia los que estés haciendo la fusión sean correctos. Después, asigna un nombre y descripción a la solicitud de cambios. ![Barra lateral de control de código fuente con el botón de preparación resaltado](/assets/images/help/codespaces/codespaces-commit-pr.png) +1. Da clic en **Crear**. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/dependabot/supported-package-managers.md b/translations/es-ES/data/reusables/dependabot/supported-package-managers.md index 16a05c9ef3..59dcc3722e 100644 --- a/translations/es-ES/data/reusables/dependabot/supported-package-managers.md +++ b/translations/es-ES/data/reusables/dependabot/supported-package-managers.md @@ -26,7 +26,7 @@ La siguiente tabla muestra, para cada administrador de paquetes: | Terraform | `terraform` | >= 0.13, <= 1.0 | **✓** | **✓** | | | yarn | `npm` | v1 | **✓** | **✓** | | -[1] El {% data variables.product.prodname_dependabot %} no ejecuta Gradle pero es compatible con las actualizaciones a los siguietnes archivos: `build.gradle` y `build.gradle.kts` (para los proyectos de Kotlin). +[1] El {% data variables.product.prodname_dependabot %} no ejecuta Gradle pero es compatible con las actualizaciones de los siguientes archivos: `build.gradle`, `build.gradle.kts` (para los proyectos de Kotlin), y los archivos que se incluye a través de la declaración `apply` que tengan `dependencies` en el nombre de archivo. Toma en cuenta que `apply` no es compatible con `apply to`, con la recursión o con las sintaxis avanzadas (por ejemplo, el `apply` de Kotlin con `mapOf`, que son nombres de archivo que se definen por propiedad). [2] El {% data variables.product.prodname_dependabot %} no ejecuta Maven pero es compatible con las actualizaciones a los archivos `pom.xml`. diff --git a/translations/es-ES/data/reusables/dependency-review/beta.md b/translations/es-ES/data/reusables/dependency-review/beta.md index 4a35074263..4583a9cebe 100644 --- a/translations/es-ES/data/reusables/dependency-review/beta.md +++ b/translations/es-ES/data/reusables/dependency-review/beta.md @@ -1,7 +1,8 @@ -{% ifversion fpt or ghes > 3.1 %} +{% ifversion ghes > 3.1 %} {% note %} **Nota:** Las revisiones de dependencias se encuentran actualmente en beta y están sujetas a cambios. {% endnote %} + {% endif %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/developer-site/pull_request_forked_repos_link.md b/translations/es-ES/data/reusables/developer-site/pull_request_forked_repos_link.md index 8ec2a97325..64da9c3926 100644 --- a/translations/es-ES/data/reusables/developer-site/pull_request_forked_repos_link.md +++ b/translations/es-ES/data/reusables/developer-site/pull_request_forked_repos_link.md @@ -1,4 +1,4 @@ -#### Eventos de solicitud de extracción para repositorios bifurcados +### Eventos de solicitud de extracción para repositorios bifurcados {% note %} diff --git a/translations/es-ES/data/reusables/discussions/about-discussions.md b/translations/es-ES/data/reusables/discussions/about-discussions.md index 846f180578..0566782cfc 100644 --- a/translations/es-ES/data/reusables/discussions/about-discussions.md +++ b/translations/es-ES/data/reusables/discussions/about-discussions.md @@ -1 +1 @@ -{% data variables.product.prodname_discussions %} is an open forum for conversation among maintainers and the community for a project on {% data variables.product.product_name %}. +Los {% data variables.product.prodname_discussions %} son un foro abierto para tener conversaciones entre los mantenedores y la comunidad para algún proyecto en {% data variables.product.product_name %}. diff --git a/translations/es-ES/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-repository.md b/translations/es-ES/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-repository.md index c5860e1566..6b2602240b 100644 --- a/translations/es-ES/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-repository.md +++ b/translations/es-ES/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-repository.md @@ -1,5 +1,5 @@ -You can enable or disable {% data variables.product.prodname_discussions %} for a repository. +Puedes habilitar o inhabilitar los {% data variables.product.prodname_discussions %} para un repositorio. {% data reusables.repositories.navigate-to-repo %} 1. Debajo de tu nombre de repositorio, da clic en {% octicon "gear" aria-label="The gear icon" %} **Configuración**. ![Botón de configuración del repositorio](/assets/images/help/discussions/public-repo-settings.png) -1. Debajo de "Características", selecciona **Debates**. ![Checkbox under "Features" for enabling or disabling {% data variables.product.prodname_discussions %} for a repository](/assets/images/help/discussions/select-discussions-checkbox.png) +1. Debajo de "Características", selecciona **Debates**. ![Casilla de verificación debajo de "Características" para habilitar o inhabilitar los {% data variables.product.prodname_discussions %} para un repositorio](/assets/images/help/discussions/select-discussions-checkbox.png) diff --git a/translations/es-ES/data/reusables/discussions/you-can-use-discussions.md b/translations/es-ES/data/reusables/discussions/you-can-use-discussions.md index 48dc3d6181..14063bcc95 100644 --- a/translations/es-ES/data/reusables/discussions/you-can-use-discussions.md +++ b/translations/es-ES/data/reusables/discussions/you-can-use-discussions.md @@ -1 +1 @@ -You can use {% data variables.product.prodname_discussions %} to ask and answer questions, share information, make announcements, and conduct or participate in conversations about a project. Para obtener más información, consulta la sección "[Acerca de los debates](/discussions/collaborating-with-your-community-using-discussions/about-discussions)". +Puedes utilizar los {% data variables.product.prodname_discussions %} para hacer y responder preguntas, compartir información, hacer anuncios y conducir o participar en las conversaciones sobre un proyecto. Para obtener más información, consulta la sección "[Acerca de los debates](/discussions/collaborating-with-your-community-using-discussions/about-discussions)". diff --git a/translations/es-ES/data/reusables/dotcom_billing/codespaces-minutes.md b/translations/es-ES/data/reusables/dotcom_billing/codespaces-minutes.md index 6fe0f0d9f5..649572cdb0 100644 --- a/translations/es-ES/data/reusables/dotcom_billing/codespaces-minutes.md +++ b/translations/es-ES/data/reusables/dotcom_billing/codespaces-minutes.md @@ -1 +1 @@ -1. Under "{% data variables.product.prodname_codespaces %}", view usage details of your compute hours and storage. ![Detalles de uso de minutos](/assets/images/help/billing/codespaces-compute-storage.png) +1. Debajo de "{% data variables.product.prodname_codespaces %}", visualiza los detalles de uso de tus horas de cálculo y almacenamiento. ![Detalles de uso de minutos](/assets/images/help/billing/codespaces-compute-storage.png) diff --git a/translations/es-ES/data/reusables/dotcom_billing/enter-billing-info.md b/translations/es-ES/data/reusables/dotcom_billing/enter-billing-info.md index b17b064cd4..a71ebf0af4 100644 --- a/translations/es-ES/data/reusables/dotcom_billing/enter-billing-info.md +++ b/translations/es-ES/data/reusables/dotcom_billing/enter-billing-info.md @@ -1 +1 @@ -1. Under "Billing information", complete the form, then click **Save**. +1. Debajo de "Información de facturación", completa el formato y luego haz clic en **Guardar**. diff --git a/translations/es-ES/data/reusables/dotcom_billing/lfs-data.md b/translations/es-ES/data/reusables/dotcom_billing/lfs-data.md index 2ca34a1cc3..52fd53fb75 100644 --- a/translations/es-ES/data/reusables/dotcom_billing/lfs-data.md +++ b/translations/es-ES/data/reusables/dotcom_billing/lfs-data.md @@ -1,3 +1,3 @@ -1. View details of your bandwidth and storage usage under "{% data variables.large_files.product_name_short %} Data." To view your organization's LFS data usage by repository, click the arrows next to "Storage" and "Bandwidth." +1. Ve los detalles de tu uso de almacenamiento y ancho de banda en "Datos de {% data variables.large_files.product_name_short %}". Para ver el uso de datos LFS de tu organización por repositorio, haz clic en las flechas junto a "Almacenamiento" y "Ancho de Banda". ![Detalles del uso de datos de Git LFS](/assets/images/help/billing/lfs-data.png) diff --git a/translations/es-ES/data/reusables/dotcom_billing/monthly-spending-limit-actions-packages.md b/translations/es-ES/data/reusables/dotcom_billing/monthly-spending-limit-actions-packages.md index b9b69365fa..fad406cff1 100644 --- a/translations/es-ES/data/reusables/dotcom_billing/monthly-spending-limit-actions-packages.md +++ b/translations/es-ES/data/reusables/dotcom_billing/monthly-spending-limit-actions-packages.md @@ -1 +1 @@ -1. Under "Monthly spending limit", scroll down to "Actions & Packages" and choose to limit spending or allow unlimited spending. ![Botones radiales para limitar los gastos o permitir gastos ilimitados](/assets/images/help/billing/limit-or-unlimited.png) +1. Debajo de "Límite de gastos mensual", desplázate hacia abajo hasta "Acciones & Paquetes" y elige limitar el gasto o permitir el gasto ilimitado. ![Botones radiales para limitar los gastos o permitir gastos ilimitados](/assets/images/help/billing/limit-or-unlimited.png) diff --git a/translations/es-ES/data/reusables/dotcom_billing/monthly-spending-limit-codespaces.md b/translations/es-ES/data/reusables/dotcom_billing/monthly-spending-limit-codespaces.md index 36ba975703..87160d26f8 100644 --- a/translations/es-ES/data/reusables/dotcom_billing/monthly-spending-limit-codespaces.md +++ b/translations/es-ES/data/reusables/dotcom_billing/monthly-spending-limit-codespaces.md @@ -1 +1 @@ -1. Under "Monthly spending limit", scroll down to "Codespaces" and choose to limit spending or allow unlimited spending. ![Botones radiales para limitar los gastos o permitir gastos ilimitados](/assets/images/help/billing/limit-or-unlimited-codespaces.png) +1. Debajo de "Límite de gastos mensual", desplázate hacia abajo para encontrar "Codespaces" y elige limitar el gasto o permitir el gasto ilimitado. ![Botones radiales para limitar los gastos o permitir gastos ilimitados](/assets/images/help/billing/limit-or-unlimited-codespaces.png) diff --git a/translations/es-ES/data/reusables/dotcom_billing/pricing_cal.md b/translations/es-ES/data/reusables/dotcom_billing/pricing_cal.md new file mode 100644 index 0000000000..655f15601b --- /dev/null +++ b/translations/es-ES/data/reusables/dotcom_billing/pricing_cal.md @@ -0,0 +1 @@ +Para estimar los costos por servicios de consumo, puedes utilizar el calculador de precios de {% data variables.product.prodname_dotcom %}. Para obtener más información, dirígete a https://github.com/pricing/calculator. diff --git a/translations/es-ES/data/reusables/enterprise-accounts/about-enterprise-accounts.md b/translations/es-ES/data/reusables/enterprise-accounts/about-enterprise-accounts.md index 996f9aa441..a75faf5757 100644 --- a/translations/es-ES/data/reusables/enterprise-accounts/about-enterprise-accounts.md +++ b/translations/es-ES/data/reusables/enterprise-accounts/about-enterprise-accounts.md @@ -1,76 +1,84 @@ -## About enterprise accounts on {% ifversion fpt %}{% data variables.product.prodname_ghe_cloud %}{% else %}{% data variables.product.product_name %}{% endif %} +## Acerca de las cuentas empresariales en {% ifversion fpt %}{% data variables.product.prodname_ghe_cloud %}{% else %}{% data variables.product.product_name %}{% endif %} {% ifversion fpt %} -Your enterprise account on {% data variables.product.prodname_dotcom_the_website %} allows you to manage multiple organizations. Tu cuenta de empresa debe tener un controlador, como una organización o cuenta personal en {% data variables.product.prodname_dotcom %}. +Tu cuenta empresarial en {% data variables.product.prodname_dotcom_the_website %} te permite administrar organizaciones múltiples. Tu cuenta de empresa debe tener un controlador, como una organización o cuenta personal en {% data variables.product.prodname_dotcom %}. {% elsif ghes or ghae %} -The enterprise account on {% ifversion ghes %}{% data variables.product.product_location_enterprise %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} allows you to manage the organizations{% ifversion ghes %} on{% elsif ghae %} owned by{% endif %} your {% ifversion ghes %}{% data variables.product.prodname_ghe_server %} instance{% elsif ghae %}enterprise{% endif %}. +La cuenta empresarial en {% ifversion ghes %}{% data variables.product.product_location_enterprise %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} te permite administrar las organizaciones{% ifversion ghes %} en{% elsif ghae %} que pertenecen a{% endif %} tu {% ifversion ghes %}instancia de {% data variables.product.prodname_ghe_server %}{% elsif ghae %}empresa{% endif %}. {% endif %} -Organizations are shared accounts where enterprise members can collaborate across many projects at once. Organization owners can manage access to the organization's data and projects with sophisticated security and administrative features. For more information, see {% ifversion fpt %}"[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)."{% elsif ghes or ghae %}"[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)" and "[Managing users, organizations, and repositories](/admin/user-management)."{% endif %} +Las organizaciones son cuentas compartidas en donde los miembros de las empresas pueden colaborar a través de muchos proyectos al mismo tiempo. Los propietarios de la organización pueden administrar el acceso a los datos y proyectos de esta con seguridad y características administrativas sofisticadas. Para obtener más información, consulta la sección {% ifversion fpt %}"[Acerca de las organizaciones](/organizations/collaborating-with-groups-in-organizations/about-organizations)".{% elsif ghes or ghae %}"[Acerca de las organizaciones](/organizations/collaborating-with-groups-in-organizations/about-organizations)" y "[Administrar usuarios, organizaciones y repositorios](/admin/user-management)".{% endif %} {% ifversion fpt %} -Enterprise owners can create organizations and link the organizations to the enterprise. After you add organizations to your enterprise account, you can manage and enforce policies for the organizations. Las opciones de cumplimiento específicas varían según el parámetro, generalmente, puedes elegir implementar una política única para cada organización en tu cuenta de empresa o puedes permitirle a los propietarios configurar la política en el nivel de organización. For more information, see "[Setting policies for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account)." +Los propietarios de las empresas pueden crear organizaciones y enlazarlas a la empresa. Como alternativa, puedes invitar a una organización existente para que se una a tu empresa. Después de que agregues organizaciones a tu cuenta empresarial, puedes administrar y requerir políticas para dichas organizaciones. Las opciones de cumplimiento específicas varían según el parámetro, generalmente, puedes elegir implementar una política única para cada organización en tu cuenta de empresa o puedes permitirle a los propietarios configurar la política en el nivel de organización. Para obtener más información, consulta la sección "[Configurar las políticas para las organizaciones de tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account)". {% elsif ghes or ghae %} -For more information about the management of policies for your enterprise account, see "[Setting policies for your enterprise](/admin/policies)." +Para obtener más información sobre la administración de políticas para tu cuenta empresarial, consulta la sección "[Configurar las políticas de tu empresa](/admin/policies)". {% endif %} -## About administration of your enterprise account +## Acerca de la administración de tu cuenta empresarial {% ifversion ghes or ghae %} -From your enterprise account on {% ifversion ghae %}{% data variables.product.product_name %}{% elsif ghes %}a {% data variables.product.prodname_ghe_server %} instance{% endif %}, administrators can view enterprise membership and manage the following for the {% ifversion ghes %}{% data variables.product.prodname_ghe_server %} instance{% elsif ghae %}enterprise on {% data variables.product.prodname_ghe_managed %}{% endif %}. +Desde tu cuenta empresarial en {% ifversion ghae %}{% data variables.product.product_name %}{% elsif ghes %}una instancia de {% data variables.product.prodname_ghe_server %}{% endif %}, los administradores pueden ver la membrecía empresrial y administrar lo siguiente para la instancia de {% ifversion ghes %}{% data variables.product.prodname_ghe_server %}{% elsif ghae %}empresa en {% data variables.product.prodname_ghe_managed %}{% endif %}. {% ifversion ghes %} -- License usage{% endif %} -- Security ({% ifversion ghae %}single sign-on, IP allow lists, {% endif %}SSH certificate authorities, two-factor authentication) -- Enterprise policies for organizations owned by the enterprise account +- Uso de licencia{% endif %} +- Seguridad ({% ifversion ghae %}inicio de sesión único, listas de IP permitidas, {% endif %}autoridades de certificados SSH, autenticación bifactorial) +- Políticas empresariales para las organizaciones que pertenezcan a la cuenta empresarial {% endif %} {% ifversion ghes %} -### About administration of your enterprise account on {% data variables.product.prodname_ghe_cloud %} +### Acerca de la administración de tu cuenta empresarial en {% data variables.product.prodname_ghe_cloud %} {% endif %} -{% ifversion fpt or ghes %}When you try or purchase {% data variables.product.prodname_enterprise %}, you can{% ifversion ghes %} also{% endif %} create an enterprise account for {% data variables.product.prodname_ghe_cloud %} on {% data variables.product.prodname_dotcom_the_website %}. Administrators for the enterprise account on {% data variables.product.prodname_dotcom_the_website %} can view membership and manage the following for the enterprise account{% ifversion ghes %} on {% data variables.product.prodname_dotcom_the_website %}{% endif %}. +{% ifversion fpt or ghes %}Cuando pruebas o compras {% data variables.product.prodname_enterprise %}, también {% ifversion ghes %} puedes{% endif %} crear una cuenta empresarial para {% data variables.product.prodname_ghe_cloud %} en {% data variables.product.prodname_dotcom_the_website %}. Los administradores de la cuenta empresarial en {% data variables.product.prodname_dotcom_the_website %} pueden ver la membrecía y administrar lo siguiente para la cuenta empresarial{% ifversion ghes %} en {% data variables.product.prodname_dotcom_the_website %}{% endif %}. -- Billing and usage (services on {% data variables.product.prodname_dotcom_the_website %}, {% data variables.product.prodname_GH_advanced_security %}, user licenses) -- Security (single sign-on, IP allow lists, SSH certificate authorities, two-factor authentication) -- Enterprise policies for organizations owned by the enterprise account +- Facturación y uso (Servicios en {% data variables.product.prodname_dotcom_the_website %}, {% data variables.product.prodname_GH_advanced_security %}, licencias de usuario) +- Seguridad (Inicio de sesión único, listas de IP permitidas, autoridades de certificados SSH, autenticación bifactorial) +- Políticas empresariales para las organizaciones que pertenecen a la cuenta empresarial -If you use both {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}, you can also manage the following for {% data variables.product.prodname_ghe_server %} from your enterprise account on {% data variables.product.prodname_dotcom_the_website %}. +Si utilizas tanto {% data variables.product.prodname_ghe_cloud %} como {% data variables.product.prodname_ghe_server %}, también puedes administrar lo siguiente para {% data variables.product.prodname_ghe_server %} desde tu cuenta empresarial en {% data variables.product.prodname_dotcom_the_website %}. -- Billing and usage for {% data variables.product.prodname_ghe_server %} instances +- Facturación y uso de las instancias de {% data variables.product.prodname_ghe_server %} - Solicitudes y paquetes de soporte compartidos con {% data variables.contact.enterprise_support %} -You can also connect the enterprise account on {% data variables.product.product_location_enterprise %} to your enterprise account on {% data variables.product.prodname_dotcom_the_website %} to see license usage details for your {% data variables.product.prodname_enterprise %} subscription from {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta la sección {% ifversion fpt %}"[Sincronizar el uso de licencia entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)" en la documentación de {% data variables.product.prodname_ghe_server %}.{% elsif ghes %}"[Sincronizar el uso de licencias entre {% data variables.product.prodname_ghe_server %} y {% 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 %} +También puedes conectar la cuenta empresarial en {% data variables.product.product_location_enterprise %} a tu cuenta empresarial en {% data variables.product.prodname_dotcom_the_website %} para ver los detalles de uso de licencia para tu suscripción de {% data variables.product.prodname_enterprise %} desde {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta la sección {% ifversion fpt %}"[Sincronizar el uso de licencia entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)" en la documentación de {% data variables.product.prodname_ghe_server %}.{% elsif ghes %}"[Sincronizar el uso de licencias entre {% data variables.product.prodname_ghe_server %} y {% 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 %} Para obtener más información acerca de las diferencias entre {% data variables.product.prodname_ghe_cloud %} y {% data variables.product.prodname_ghe_server %}, consulta la sección "[ productos de {% data variables.product.prodname_dotcom %}](/get-started/learning-about-github/githubs-products)". {% data reusables.enterprise-accounts.to-upgrade-or-get-started %} {% endif %} -## About billing for your enterprise account +{% ifversion fpt %} -The bill for your enterprise account includes the monthly cost for each member of your enterprise. The bill includes {% ifversion fpt %}any paid licenses in organizations outside of your enterprise account, subscriptions to apps in {% data variables.product.prodname_marketplace %}, {% endif %}{% ifversion fpt or ghae %}additional paid services for your enterprise{% ifversion fpt %} like data packs for {% data variables.large_files.product_name_long %},{% endif %} and{% endif %} usage for {% data variables.product.prodname_GH_advanced_security %}. +## Acerca de {% data variables.product.prodname_emus %} + +{% data reusables.enterprise-accounts.emu-short-summary %} + +{% endif %} + +## Acerca de la facturación para tu cuenta empresarial + +La factura de tu cuenta empresarial incluye el costo mensual de cada miembro de ella. La factura incluye {% ifversion fpt %}cualquier tipo de licencia de pago en organizaciones fuera de tu cuenta empresarial, suscripciones a las apps en {% data variables.product.prodname_marketplace %}, {% endif %}{% ifversion fpt or ghae %}los servicios de pago adicionales para tu empresa{% ifversion fpt %} como paquetes de datos para {% data variables.large_files.product_name_long %},{% endif %} y{% endif %} el uso de {% data variables.product.prodname_GH_advanced_security %}. {% ifversion fpt %} -For more information about billing for your {% data variables.product.prodname_ghe_cloud %} subscription, see "[Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)" and "[About billing for your enterprise](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)." +Para obtener más información sobre la facturación de tu suscripción de {% data variables.product.prodname_ghe_cloud %}, consulta las secciones "[Ver la suscripción y el uso de tu cuenta empresarial](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)" y "[Acerca de la facturación de tu empresa](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)". {% elsif ghes %} {% data reusables.enterprise-accounts.enterprise-accounts-billing %} -For more information about billing for {% ifversion fpt %}{% data variables.product.prodname_ghe_cloud %}{% else %}{% data variables.product.product_name %}{% endif %}, see "[About billing for your enterprise](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)." +Para obtener más información sobre la facturación para {% ifversion fpt %}{% data variables.product.prodname_ghe_cloud %}{% else %}{% data variables.product.product_name %}{% endif %}, consulta la sección "[Acerca de la facturación para tu empresa](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)". {% endif %} @@ -78,10 +86,10 @@ For more information about billing for {% ifversion fpt %}{% data variables.prod {% ifversion fpt %} -{% data variables.product.prodname_enterprise %} offers two deployment options. In addition to {% data variables.product.prodname_ghe_cloud %}, you can use {% data variables.product.prodname_ghe_server %} to host development work for your enterprise in your data center or supported cloud provider. {% endif %}Enterprise owners on {% data variables.product.prodname_dotcom_the_website %} can use an enterprise account to manage payment and licensing for {% data variables.product.prodname_ghe_server %} instances. For more information, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products#github-enterprise)" and "[Managing your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise)." +{% data variables.product.prodname_enterprise %} ofrece opciones de despliegue. Adicionalmente a las {% data variables.product.prodname_ghe_cloud %}, puedes utilizar {% data variables.product.prodname_ghe_server %} para hospedar trabajo de desarrollo para tu empresa en tu centro de datos o proveedor compatible en la nube. {% endif %}Los propietarios empresariales en {% data variables.product.prodname_dotcom_the_website %} pueden utilizar una cuenta empresarial para administrar el pago y el licenciamiento de las instancias de {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta las secciones "[ productos de {% data variables.product.company_short %}](/get-started/learning-about-github/githubs-products#github-enterprise)" y "[Administrar tu licencia para {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise)". {% endif %} ## Leer más -- "[Enterprise accounts](/graphql/guides/managing-enterprise-accounts)" in the GraphQL API documentation +- "[Cuentas empresariales](/graphql/guides/managing-enterprise-accounts)" en la documentación de la API de GraphQL diff --git a/translations/es-ES/data/reusables/enterprise-accounts/access-enterprise.md b/translations/es-ES/data/reusables/enterprise-accounts/access-enterprise.md index 69465b0edb..560b1f09f7 100644 --- a/translations/es-ES/data/reusables/enterprise-accounts/access-enterprise.md +++ b/translations/es-ES/data/reusables/enterprise-accounts/access-enterprise.md @@ -5,5 +5,4 @@ {% elsif ghes or ghae %}1. En la esquina superior derecha de {% data variables.product.product_name %}, da clic en tu foto de perfil y luego en **Configuración de empresa**. !["Configuración de empresa" en el menú desplegable de la foto de perfil en {% data variables.product.product_name %}](/assets/images/enterprise/settings/enterprise-settings.png) - {% endif %} diff --git a/translations/es-ES/data/reusables/enterprise-accounts/actions-runner-groups-tab.md b/translations/es-ES/data/reusables/enterprise-accounts/actions-runner-groups-tab.md index 25b349604d..021cfc86d4 100644 --- a/translations/es-ES/data/reusables/enterprise-accounts/actions-runner-groups-tab.md +++ b/translations/es-ES/data/reusables/enterprise-accounts/actions-runner-groups-tab.md @@ -1 +1 @@ -1. Click the **Runner groups** tab. \ No newline at end of file +1. Haz clic en la pestaña **Grupos de ejecutores**. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/enterprise-accounts/actions-runners-tab.md b/translations/es-ES/data/reusables/enterprise-accounts/actions-runners-tab.md index 02df9aad12..9bf929c69d 100644 --- a/translations/es-ES/data/reusables/enterprise-accounts/actions-runners-tab.md +++ b/translations/es-ES/data/reusables/enterprise-accounts/actions-runners-tab.md @@ -1 +1 @@ -1. Haz clic en la pestaña de {% ifversion fpt %}**Ejecutores**{% else %}**Ejecutores auto-hospedados**{% endif %}. +1. Haz clic en la pestaña de {% ifversion fpt or ghes > 3.1 or ghae-next %}**Ejecutores**{% else %}**Ejecutores auto-hospedados**{% endif %}. diff --git a/translations/es-ES/data/reusables/enterprise-accounts/advanced-security-security-features.md b/translations/es-ES/data/reusables/enterprise-accounts/advanced-security-security-features.md index fd65ca0801..58389bd284 100644 --- a/translations/es-ES/data/reusables/enterprise-accounts/advanced-security-security-features.md +++ b/translations/es-ES/data/reusables/enterprise-accounts/advanced-security-security-features.md @@ -1 +1 @@ -1. Under "GitHub Advanced Security", click the **Security features** tab. +1. Debajo de "GitHub Advanced Security", haz clic en la pestaña de **Características de Seguridad**. 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 57ca31b009..d220575548 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 {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %} usage beyond the amounts included with your account. +Si compras {% 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 el uso de {% data variables.product.prodname_actions %} y del {% data variables.product.prodname_registry %} más allá de las cantidades que se incluyen en tu cuenta. diff --git a/translations/es-ES/data/reusables/enterprise-accounts/domains-about-approval.md b/translations/es-ES/data/reusables/enterprise-accounts/domains-about-approval.md index 83f41d7ded..65a819b1d3 100644 --- a/translations/es-ES/data/reusables/enterprise-accounts/domains-about-approval.md +++ b/translations/es-ES/data/reusables/enterprise-accounts/domains-about-approval.md @@ -2,9 +2,9 @@ {% data reusables.enterprise-accounts.approved-domains-about %} -Después de que apruebas los dominios en tu cuenta empresarial, puedes restringir las notificaciones por correo electrónico para la actividad dentro de esta a los usuarios con direcciones de correo electrónico verificadas dentro de los dominios aprobados o verificados. {% ifversion fpt%}For more information, see "[Restricting email notifications for your enterprise account](/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account)."{% endif %}{% ifversion ghes > 3.1 %}For more information, see "[Restricting email notifications for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise)."{% endif %} +Después de que apruebas los dominios en tu cuenta empresarial, puedes restringir las notificaciones por correo electrónico para la actividad dentro de esta a los usuarios con direcciones de correo electrónico verificadas dentro de los dominios aprobados o verificados. {% ifversion fpt%}Para obtener más información, consulta la sección "[Restringir las notificaciones por correo electrónico para tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account)".{% endif %}{% ifversion ghes > 3.1 %}Para obtener más información, consulta la sección "[Restringir las notificaciones por correo electrónico para tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise)".{% endif %} -{% ifversion fpt%}To receive email notifications, the owner of the user account must verify the email address in on {% data variables.product.product_name %}. Para obtener más información, consulta "[Verificar tu dirección de correo electrónico](/github/getting-started-with-github/verifying-your-email-address)".{% endif %} +{% ifversion fpt%}Para recibir notificaciones por correo electrónico, el propietario de la cuenta de usuario debe verificar la dirección de correo electrónico en {% data variables.product.product_name %}. Para obtener más información, consulta "[Verificar tu dirección de correo electrónico](/github/getting-started-with-github/verifying-your-email-address)".{% endif %} Los propietarios de la organización no pueden ver la dirección de correo electrónico ni qué cuenta de usuario está asociada con alguna de ellas desde un dominio aprobado. diff --git a/translations/es-ES/data/reusables/enterprise-accounts/domains-about-verification.md b/translations/es-ES/data/reusables/enterprise-accounts/domains-about-verification.md index b1de71587b..bbbf449596 100644 --- a/translations/es-ES/data/reusables/enterprise-accounts/domains-about-verification.md +++ b/translations/es-ES/data/reusables/enterprise-accounts/domains-about-verification.md @@ -4,7 +4,7 @@ Después de que verificas la propiedad de los dominios de tus cuentas empresaria Los propietarios de las organizaciones podrán verificar la identidad de los miembros de éstas si visualizan la dirección de correo electrónico de cada miembro dentro del dominio verificado. -Después de que verificas los dominios para tu cuenta empresarial, puedes restringir las notificaciones de correo electrónico a los dominios verificados para todas las organizaciones que le pertenezcan a tu cuenta empresarial. {% ifversion fpt%}For more information, see "[Restricting email notifications for your enterprise account](/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account)."{% endif %}{% ifversion ghes > 3.1 %}For more information, see "[Restricting email notifications for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise)."{% endif %} +Después de que verificas los dominios para tu cuenta empresarial, puedes restringir las notificaciones de correo electrónico a los dominios verificados para todas las organizaciones que le pertenezcan a tu cuenta empresarial. {% ifversion fpt%}Para obtener más información, consulta la sección "[Restringir las notificaciones por correo electrónico para tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account)".{% endif %}{% ifversion ghes > 3.1 %}Para obtener más información, consulta la sección "[Restringir las notificaciones por correo electrónico para tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise)".{% endif %} Incluso si no restringieras las notificaciones por correo electrónico para la cuenta empresarial, en caso de que un propietario de organización lo haya hecho, los miembros de dicha organización podrán recibir notificaciones en cualquier dominio que la empresa haya verificado o aprobado para la cuenta empresarial adicionalmente a cualquier dominio que se haya verificado o aprobado previamente para la organización. Para obtener más información sobre cómo restringir las notificaciones de una organización, consulta la sección "[Restringir las notificaciones por correo electrónico para tu organización](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)". diff --git a/translations/es-ES/data/reusables/enterprise-accounts/email-restrictions-about.md b/translations/es-ES/data/reusables/enterprise-accounts/email-restrictions-about.md index e5a7359efc..5c594f8618 100644 --- a/translations/es-ES/data/reusables/enterprise-accounts/email-restrictions-about.md +++ b/translations/es-ES/data/reusables/enterprise-accounts/email-restrictions-about.md @@ -7,7 +7,7 @@ Los dominios se pueden heredar desde la cuenta empresarial, o los puedes configu {% endif %} {% ifversion ghes > 3.1 %} -Los dominios se pueden heredar desde la cuenta empresarial, o los puedes configurar una organización específica. For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)" and "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)." +Los dominios se pueden heredar desde la cuenta empresarial, o los puedes configurar una organización específica. Para obtener más información, consulta la sección "[Verificar o aprobar un dominio para tu empresa](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)" y "[Restringir las notificaciones por correo electrónico para tu organización](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)". {% endif %} {% data reusables.notifications.email-restrictions-verification %} diff --git a/translations/es-ES/data/reusables/enterprise-accounts/email-restrictions-restricting.md b/translations/es-ES/data/reusables/enterprise-accounts/email-restrictions-restricting.md index c6800b8163..7acbe2530c 100644 --- a/translations/es-ES/data/reusables/enterprise-accounts/email-restrictions-restricting.md +++ b/translations/es-ES/data/reusables/enterprise-accounts/email-restrictions-restricting.md @@ -1,4 +1,4 @@ -Antes de que puedas restringir las notificaciones por correo electrónico para tu cuenta empresarial, debes verificar o aprobar por lo menos un dominio para esta. {% ifversion fpt %} For more information, see "[Verifying or approving a domain for your enterprise account](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)."{% endif %}{% ifversion ghes > 3.1 %} For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."{% endif %} +Antes de que puedas restringir las notificaciones por correo electrónico para tu cuenta empresarial, debes verificar o aprobar por lo menos un dominio para esta. {% ifversion fpt %} Para obtener más información, consulta la sección "[Verificar o aprobar un dominio para tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account)".{% endif %}{% ifversion ghes > 3.1 %} Para obtener más información, consulta la sección "[Verificar o aprobar un dominio para tu empresa](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)".{% endif %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} diff --git a/translations/es-ES/data/reusables/enterprise-accounts/emu-forks.md b/translations/es-ES/data/reusables/enterprise-accounts/emu-forks.md new file mode 100644 index 0000000000..c1bf1f7502 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/emu-forks.md @@ -0,0 +1 @@ +Los {% data variables.product.prodname_managed_users_caps %} no pueden bifurcar repositorios desde fuera de la empresa ni bifurcar repositorios internos. Los {% data variables.product.prodname_managed_users_caps %} pueden bifurcar repositorios privados que pertenezcan a organizaciones en la empresa hacia otras organizaciones que también pertenezcan a ella o como una bifurcación que pertenezca al {% data variables.product.prodname_managed_user %}. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/enterprise-accounts/emu-more-info-account.md b/translations/es-ES/data/reusables/enterprise-accounts/emu-more-info-account.md new file mode 100644 index 0000000000..3e77615e91 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/emu-more-info-account.md @@ -0,0 +1 @@ +Para obtener más información, consulta la sección "[Tipos de cuenta de GitHub](/get-started/learning-about-github/types-of-github-accounts#enterprise-managed-users)". \ No newline at end of file diff --git a/translations/es-ES/data/reusables/enterprise-accounts/emu-password-reset-session.md b/translations/es-ES/data/reusables/enterprise-accounts/emu-password-reset-session.md new file mode 100644 index 0000000000..6732d802dd --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/emu-password-reset-session.md @@ -0,0 +1 @@ +Si necesitas restablecer la contraseña de tu usuario de configuración, utiliza una ventana privada o de modo incógnito para solicitar una contraseña nueva. Cuando recibas el correo electrónico con el enlace para restablecer tu contraseña, cópialo en tu buscador. Para obtener más información sobre cómo restablecer tu contraseña, consulta la sección "[Solicitar una contraseña nueva](/github/authenticating-to-github/keeping-your-account-and-data-secure/updating-your-github-access-credentials#requesting-a-new-password)". \ No newline at end of file diff --git a/translations/es-ES/data/reusables/enterprise-accounts/emu-permission-follow.md b/translations/es-ES/data/reusables/enterprise-accounts/emu-permission-follow.md new file mode 100644 index 0000000000..7193630d98 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/emu-permission-follow.md @@ -0,0 +1 @@ +{% ifversion fpt %} Los miembros de una {% data variables.product.prodname_emu_enterprise %} solo pueden seguir a otros miembros de su empresa. {% endif %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/enterprise-accounts/emu-permission-fork.md b/translations/es-ES/data/reusables/enterprise-accounts/emu-permission-fork.md new file mode 100644 index 0000000000..f4e649625c --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/emu-permission-fork.md @@ -0,0 +1 @@ +{% ifversion fpt %}Los miembros de una {% data variables.product.prodname_emu_enterprise %} no pueden bifurcar repositorios desde fuera de la empresa ni bifurcar repositorios internos.{% endif %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/enterprise-accounts/emu-permission-gist.md b/translations/es-ES/data/reusables/enterprise-accounts/emu-permission-gist.md new file mode 100644 index 0000000000..ddc31be56d --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/emu-permission-gist.md @@ -0,0 +1 @@ +{% ifversion fpt %}Los miembros de una {% data variables.product.prodname_emu_enterprise %} no pueden crear gists y tener acceso de solo lectura a estos.{% endif %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/enterprise-accounts/emu-permission-interact.md b/translations/es-ES/data/reusables/enterprise-accounts/emu-permission-interact.md new file mode 100644 index 0000000000..597118fd48 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/emu-permission-interact.md @@ -0,0 +1 @@ +{% ifversion fpt %}Los miembros de una {% data variables.product.prodname_emu_enterprise %} solo pueden interactuar con los repositorios dentro de su empresa. {% endif %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/enterprise-accounts/emu-permission-propose.md b/translations/es-ES/data/reusables/enterprise-accounts/emu-permission-propose.md new file mode 100644 index 0000000000..3332edfb70 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/emu-permission-propose.md @@ -0,0 +1 @@ +{% ifversion fpt %} Los miembros de una {% data variables.product.prodname_emu_enterprise %} solo pueden proponer cambios en los repositorios que sean parte de ella. {% endif %} diff --git a/translations/es-ES/data/reusables/enterprise-accounts/emu-permission-repo.md b/translations/es-ES/data/reusables/enterprise-accounts/emu-permission-repo.md new file mode 100644 index 0000000000..86370d0cd3 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/emu-permission-repo.md @@ -0,0 +1 @@ +{% ifversion fpt %} Los miembros de una {% data variables.product.prodname_emu_enterprise %} solo pueden hacer cambios en los repositorios que sean parte de ella. {% endif %} diff --git a/translations/es-ES/data/reusables/enterprise-accounts/emu-saml-note.md b/translations/es-ES/data/reusables/enterprise-accounts/emu-saml-note.md new file mode 100644 index 0000000000..c5a3a3a128 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/emu-saml-note.md @@ -0,0 +1,7 @@ +{% ifversion fpt%} +{% note %} + +**Nota**: Si tu empresa utiliza {% data variables.product.prodname_emus %}, debes seguir un proceso diferente para configurar el inicio de sesión único de SAML. Para obtener más información, consulta la sección "[Configurar el inicio de sesión único de SAML para los Usuarios Administrados Empresariales](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)". + +{% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/enterprise-accounts/emu-scim-note.md b/translations/es-ES/data/reusables/enterprise-accounts/emu-scim-note.md new file mode 100644 index 0000000000..7c54fa9390 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/emu-scim-note.md @@ -0,0 +1,7 @@ +{% ifversion fpt%} +{% note %} + +**Nota**: Si tu empresa utiliza {% data variables.product.prodname_emus %}, no puedes utilizar la sincronización de equipos y, en su lugar, debes configurar SCIM para administrar la membrecía con tu proveedor de identidad. Para obtener más información, consulta la sección "[Configurar el aprovisionamiento de SCIM para los Usuarios Administrados Empresariales](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users)". + +{% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/enterprise-accounts/emu-short-summary.md b/translations/es-ES/data/reusables/enterprise-accounts/emu-short-summary.md new file mode 100644 index 0000000000..3a8a2cf486 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/emu-short-summary.md @@ -0,0 +1 @@ +{% data variables.product.prodname_emus %} es una característica de {% data variables.product.prodname_ghe_cloud %} que proporciona un control aún mayor sobre los miembros y recursos empresariales. Con {% data variables.product.prodname_emus %}, todos los miembros se aprovisionan y administran a través de tu proveedor de identidad (IdP) en vez de que creen sus cuentas propias en {% data variables.product.product_name %}. La membrecía de equipo puede administrarse utilizando grupos en tu IdP. Los {% data variables.product.prodname_managed_users_caps %} se restringen a su empresa y no pueden subir código, colaborar o interactuar con usuarios, repositorios y organizaciones fuera de ella. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)". \ No newline at end of file diff --git a/translations/es-ES/data/reusables/enterprise-accounts/emu-shortcode.md b/translations/es-ES/data/reusables/enterprise-accounts/emu-shortcode.md new file mode 100644 index 0000000000..daf856a8fe --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/emu-shortcode.md @@ -0,0 +1 @@ +El código corto debe ser único para tu empresa, debe ser una secuencia de tres a ocho caracteres alfanuméricos que no contenga caracteres especiales. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/enterprise-accounts/emu-supported-idps.md b/translations/es-ES/data/reusables/enterprise-accounts/emu-supported-idps.md new file mode 100644 index 0000000000..375040efa3 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/emu-supported-idps.md @@ -0,0 +1,2 @@ +* Azure Active Directory (Azure AD) +* Okta \ No newline at end of file diff --git a/translations/es-ES/data/reusables/enterprise-accounts/github-connect-tab.md b/translations/es-ES/data/reusables/enterprise-accounts/github-connect-tab.md index f86957fcfc..b19827c082 100644 --- a/translations/es-ES/data/reusables/enterprise-accounts/github-connect-tab.md +++ b/translations/es-ES/data/reusables/enterprise-accounts/github-connect-tab.md @@ -1,3 +1,3 @@ {% ifversion ghes < 3.1 %} 1. En la barra lateral izquierda, haz clic en **{% data variables.product.prodname_github_connect %}**. ![GitHub Connect tab in the business account settings sidebar](/assets/images/enterprise/business-accounts/settings-github-connect-tab.png){% else %} -1. In the enterprise account sidebar, click {% octicon "plug" aria-label="The GitHub Connect gear" %} **{% data variables.product.prodname_github_connect %}**. ![GitHub Connect tab in the enterprise account sidebar](/assets/images/help//business-accounts/enterprise-account-github-connect-tab.png){% endif %} \ No newline at end of file +1. En la barra lateral de la cuenta empresarial, haz clic en {% octicon "plug" aria-label="The GitHub Connect gear" %} **{% data variables.product.prodname_github_connect %}**. ![GitHub Connect tab in the enterprise account sidebar](/assets/images/help//business-accounts/enterprise-account-github-connect-tab.png){% endif %} diff --git a/translations/es-ES/data/reusables/enterprise-accounts/identity-provider-tab.md b/translations/es-ES/data/reusables/enterprise-accounts/identity-provider-tab.md new file mode 100644 index 0000000000..866f0e40f2 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/identity-provider-tab.md @@ -0,0 +1 @@ +1. Dentro del nombre de tu cuenta de empresa, haz clic en {% octicon "key" aria-label="The key icon" %} **Proveedor de identidad**. ![Pestaña de "proveedor de identidad" en la barra lateral de la empresa](/assets/images/help/enterprises/enterprise-account-identity-provider-tab.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/enterprise-accounts/invite-organization.md b/translations/es-ES/data/reusables/enterprise-accounts/invite-organization.md new file mode 100644 index 0000000000..b530693e67 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/invite-organization.md @@ -0,0 +1 @@ +Los propietarios y administradores de las cuentas empresariales pueden invitar a cuentas organizacionales existentes para que se unan a su empresa. Para obtener más información, consulta la sección "[Invitar a una organización para que se una a su cuenta empresarial](/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account#inviting-an-organization-to-join-your-enterprise-account)". diff --git a/translations/es-ES/data/reusables/enterprise-accounts/restrict-email-notifications-enterprise.md b/translations/es-ES/data/reusables/enterprise-accounts/restrict-email-notifications-enterprise.md index d2034a95f7..88751881d2 100644 --- a/translations/es-ES/data/reusables/enterprise-accounts/restrict-email-notifications-enterprise.md +++ b/translations/es-ES/data/reusables/enterprise-accounts/restrict-email-notifications-enterprise.md @@ -1 +1 @@ -1. Under "Notification preferences", select **Restrict email notifications to only approved or verified domains**. ![Casilla para restringir las notificaciones por correo electrónico para los correos electrónicos de dominio verificado](/assets/images/help/enterprises/restrict-email-notifications-to-domain-enterprise.png) +1. Debajo de "Preferencias de notificación", selecciona **Restringir las notificaciones por correo electrónico únicamente a los dominios verificados o aprobados**. ![Casilla para restringir las notificaciones por correo electrónico para los correos electrónicos de dominio verificado](/assets/images/help/enterprises/restrict-email-notifications-to-domain-enterprise.png) diff --git a/translations/es-ES/data/reusables/enterprise-accounts/team-sync-override.md b/translations/es-ES/data/reusables/enterprise-accounts/team-sync-override.md new file mode 100644 index 0000000000..b2e4438348 --- /dev/null +++ b/translations/es-ES/data/reusables/enterprise-accounts/team-sync-override.md @@ -0,0 +1 @@ +Si tu organización pertenece a una cuenta empresarial, el habilitar la sincronización de equipo o el aprovisionamiento de SCIM para la cuenta empresarial anulará tus ajustes de sincronización de equipos a nivel organizacional. Para obtener más información, consulta las secciones "[Administrar la sincronización de equipos para las organizaciones de tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)" y "[Configurar el aprovisionamiento de SCIM para los Usuarios Administrados Empresariales](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users)". \ No newline at end of file diff --git a/translations/es-ES/data/reusables/enterprise-accounts/view-current-policy-config-orgs.md b/translations/es-ES/data/reusables/enterprise-accounts/view-current-policy-config-orgs.md index 5f0d33bb1e..e9775f0960 100644 --- a/translations/es-ES/data/reusables/enterprise-accounts/view-current-policy-config-orgs.md +++ b/translations/es-ES/data/reusables/enterprise-accounts/view-current-policy-config-orgs.md @@ -1 +1 @@ -Optionally, to view the current configuration for all organizations in the enterprise account before you change the setting, click {% octicon "eye" aria-label="The eye octicon" %} **View your organizations' current configurations**. ![Enlace para visualizar la configuración política actual para todas las organizaciones en el negocio](/assets/images/help/business-accounts/view-current-policy-implementation-link.png) +Opcionalmente, para ver la configuración actual en todas las organizaciones de la cuenta empresarial antes de requerir alguna configuración adicional, da clic en {% octicon "eye" aria-label="The eye octicon" %} **Ver las configuraciones actuales de tus organizaciones**. ![Enlace para visualizar la configuración política actual para todas las organizaciones en el negocio](/assets/images/help/business-accounts/view-current-policy-implementation-link.png) diff --git a/translations/es-ES/data/reusables/enterprise-licensing/about-license-sync.md b/translations/es-ES/data/reusables/enterprise-licensing/about-license-sync.md index ce91a8c64c..462e8a0ed7 100644 --- a/translations/es-ES/data/reusables/enterprise-licensing/about-license-sync.md +++ b/translations/es-ES/data/reusables/enterprise-licensing/about-license-sync.md @@ -1 +1 @@ -You can allocate the user count for your {% data variables.product.prodname_enterprise %} license to members of both {% data variables.product.product_location_enterprise %} and an enterprise account on {% data variables.product.prodname_ghe_cloud %}. When you add a user to either environment, the user will consume one license. If a user has accounts in both environments, to consume only one license, the user's primary email address on {% data variables.product.product_location_enterprise %} must be the same as the user's verified email address on {% data variables.product.prodname_dotcom_the_website %}. Puedes sincronizar la cantidad de licencias y el uso entre los ambientes. +Puedes asignar la cuenta de usuarios para tu licencia de {% data variables.product.prodname_enterprise %} tanto a los miembros de {% data variables.product.product_location_enterprise %} como a una cuenta empresarial en {% data variables.product.prodname_ghe_cloud %}. Cuando agregas un usuario a cualquier ambiente, este consumirá una licencia. Si un usuario tiene cuentas en ambos ambientes, para que se consuma solo una licencia, la dirección de correo electrónico primaria del usuario en {% data variables.product.product_location_enterprise %} debe ser la misma que la dirección verificada del usuario en {% data variables.product.prodname_dotcom_the_website %}. Puedes sincronizar la cantidad de licencias y el uso entre los ambientes. diff --git a/translations/es-ES/data/reusables/enterprise-licensing/contact-sales-for-renewals-or-seats.md b/translations/es-ES/data/reusables/enterprise-licensing/contact-sales-for-renewals-or-seats.md index 8805af07e2..c6f1bca965 100644 --- a/translations/es-ES/data/reusables/enterprise-licensing/contact-sales-for-renewals-or-seats.md +++ b/translations/es-ES/data/reusables/enterprise-licensing/contact-sales-for-renewals-or-seats.md @@ -1 +1 @@ -If you'd like to renew or add user licenses to {% data variables.product.prodname_enterprise %}, or if you have questions about your license, contact {% data variables.contact.contact_enterprise_sales %}. El archivo de tu licencia nueva estará disponible para la descarga de forma inmediata después de que hayas completado tu orden. +Si quisieras renovar o agregar licencias de usuario a {% data variables.product.prodname_enterprise %} o si tienes preguntas sobre tu licencia, contacta a {% data variables.contact.contact_enterprise_sales %}. El archivo de tu licencia nueva estará disponible para la descarga de forma inmediata después de que hayas completado tu orden. diff --git a/translations/es-ES/data/reusables/enterprise-licensing/you-can-sync-for-a-combined-view.md b/translations/es-ES/data/reusables/enterprise-licensing/you-can-sync-for-a-combined-view.md index e388719b95..a1ab18002e 100644 --- a/translations/es-ES/data/reusables/enterprise-licensing/you-can-sync-for-a-combined-view.md +++ b/translations/es-ES/data/reusables/enterprise-licensing/you-can-sync-for-a-combined-view.md @@ -1 +1 @@ -If you use both {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %} and sync license usage between the products, you can view license usage for both on {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta la sección {% ifversion fpt %}"[Sincronizar el uso de licencia entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)" en la documentación de {% data variables.product.prodname_ghe_server %}.{% elsif ghes %}"[Sincronizar el uso de licencias entre {% data variables.product.prodname_ghe_server %} y {% 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 %} +Si utilizas tanto {% data variables.product.prodname_ghe_cloud %} como {% data variables.product.prodname_ghe_server %} y sincronizas el uso de licencias entre los productos, puedes ver el uso de licencias de ambos en {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta la sección {% ifversion fpt %}"[Sincronizar el uso de licencia entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)" en la documentación de {% data variables.product.prodname_ghe_server %}.{% elsif ghes %}"[Sincronizar el uso de licencias entre {% data variables.product.prodname_ghe_server %} y {% 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 %} diff --git a/translations/es-ES/data/reusables/enterprise/about-deployment-methods.md b/translations/es-ES/data/reusables/enterprise/about-deployment-methods.md index 7b172e17c9..0307281051 100644 --- a/translations/es-ES/data/reusables/enterprise/about-deployment-methods.md +++ b/translations/es-ES/data/reusables/enterprise/about-deployment-methods.md @@ -1 +1 @@ -{% data variables.product.prodname_enterprise %} offers two deployment options. {% ifversion fpt %}In addition to {% data variables.product.prodname_ghe_cloud %}, you can use {% data variables.product.prodname_ghe_server %} to host development work for your enterprise in your data center or a supported cloud.{% elsif ghes %}In addition to {% data variables.product.product_name %}, you can use {% data variables.product.prodname_ghe_cloud %} to host development work for your enterprise on {% data variables.product.prodname_dotcom_the_website %}.{% endif %} For more information, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products#github-enterprise)." +{% data variables.product.prodname_enterprise %} ofrece opciones de despliegue. {% ifversion fpt %}Adicionalmente a {% data variables.product.prodname_ghe_cloud %}, puedes utilizar {% data variables.product.prodname_ghe_server %} para hospedar el trabajo de desarrollo de tu empresa en tu centro de datos o en una nube compatible.{% elsif ghes %}Adicionalmente a {% data variables.product.product_name %}, puedes utilizar {% data variables.product.prodname_ghe_cloud %} para hospedar el trabajo de desarrollo para tu empresa en {% data variables.product.prodname_dotcom_the_website %}.{% endif %} Para obtener más información, consulta la sección de "[productos de {% data variables.product.company_short %}](/get-started/learning-about-github/githubs-products#github-enterprise)". diff --git a/translations/es-ES/data/reusables/enterprise/ghec-cta-button.md b/translations/es-ES/data/reusables/enterprise/ghec-cta-button.md index 4fe93719f2..68b5bdcbd8 100644 --- a/translations/es-ES/data/reusables/enterprise/ghec-cta-button.md +++ b/translations/es-ES/data/reusables/enterprise/ghec-cta-button.md @@ -1 +1 @@ -Try risk-free for 14 days +Pruébalo sin riesgos por 14 días diff --git a/translations/es-ES/data/reusables/enterprise/link-to-ghec-trial.md b/translations/es-ES/data/reusables/enterprise/link-to-ghec-trial.md index 31c4e5a5a8..4e7568f8b9 100644 --- a/translations/es-ES/data/reusables/enterprise/link-to-ghec-trial.md +++ b/translations/es-ES/data/reusables/enterprise/link-to-ghec-trial.md @@ -1 +1 @@ -For more information about how you can try {% data variables.product.prodname_ghe_cloud %} for free, see "[Setting up a trial of {% data variables.product.prodname_ghe_cloud %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud)." +Para obtener más información sobre cómo puedes probar {% data variables.product.prodname_ghe_cloud %} gratis, consulta la sección "[Configurar una prueba de {% data variables.product.prodname_ghe_cloud %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud)". diff --git a/translations/es-ES/data/reusables/enterprise_clustering/proxy_protocol_ports.md b/translations/es-ES/data/reusables/enterprise_clustering/proxy_protocol_ports.md index 6574ce927e..d44d1870fe 100644 --- a/translations/es-ES/data/reusables/enterprise_clustering/proxy_protocol_ports.md +++ b/translations/es-ES/data/reusables/enterprise_clustering/proxy_protocol_ports.md @@ -1,4 +1,4 @@ -#### Mapeos de puertos de protocolo TCP de PROXY +### Mapeos de puertos de protocolo TCP de PROXY | Puerto fuente | Puerto de destino | Descripción del servicio | |:-------------:|:-----------------:|:---------------------------:| diff --git a/translations/es-ES/data/reusables/enterprise_clustering/without_proxy_protocol_ports.md b/translations/es-ES/data/reusables/enterprise_clustering/without_proxy_protocol_ports.md index 518c54f7c0..cd535f78c5 100644 --- a/translations/es-ES/data/reusables/enterprise_clustering/without_proxy_protocol_ports.md +++ b/translations/es-ES/data/reusables/enterprise_clustering/without_proxy_protocol_ports.md @@ -1,4 +1,4 @@ -#### Mapeos de puertos de protocolo TCP para usar sin soporte de PROXY +### Mapeos de puertos de protocolo TCP para usar sin soporte de PROXY | Puerto fuente | Puerto de destino | Descripción del servicio | |:-------------:|:-----------------:|:---------------------------:| diff --git a/translations/es-ES/data/reusables/enterprise_installation/replication-command.md b/translations/es-ES/data/reusables/enterprise_installation/replication-command.md index 2e560f96a3..c71b9c98f5 100644 --- a/translations/es-ES/data/reusables/enterprise_installation/replication-command.md +++ b/translations/es-ES/data/reusables/enterprise_installation/replication-command.md @@ -4,6 +4,6 @@ ``` {% warning %} - **Advertencia:** `ghe-repl-start` causa una breve interrupción en el servidor principal, durante la cual los usuarios pueden ver errores internos del servidor. Para proporcionar un mensaje más amigable, ejecuta `ghe-maintenance -s` en el nodo principal antes de ejecutar `ghe-repl-start` en el nodo réplica para poner la aplicación en modo de mantenimiento. Una vez que se inicie la replicación, deshabilita el modo de mantenimiento con `ghe-maintenance -u`. Git replication will not progress while the primary node is in maintenance mode. + **Advertencia:** `ghe-repl-start` causa una breve interrupción en el servidor principal, durante la cual los usuarios pueden ver errores internos del servidor. Para proporcionar un mensaje más amigable, ejecuta `ghe-maintenance -s` en el nodo principal antes de ejecutar `ghe-repl-start` en el nodo réplica para poner la aplicación en modo de mantenimiento. Una vez que se inicie la replicación, deshabilita el modo de mantenimiento con `ghe-maintenance -u`. La replicación de Git no progresará mientras el nodo primario esté en modo de mantenimiento. {% endwarning %} diff --git a/translations/es-ES/data/reusables/enterprise_installation/software-license.md b/translations/es-ES/data/reusables/enterprise_installation/software-license.md index 6ad32e82c5..a451186a38 100644 --- a/translations/es-ES/data/reusables/enterprise_installation/software-license.md +++ b/translations/es-ES/data/reusables/enterprise_installation/software-license.md @@ -1 +1 @@ -Debes tener un archivo de licencia de {% data variables.product.prodname_enterprise %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_server %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server#setting-up-your-trial-of-github-enterprise-server)" and "[About licenses for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)." +Debes tener un archivo de licencia de {% data variables.product.prodname_enterprise %}. Para obtener más información, consulta las secciones "[Configurar una prueba de {% data variables.product.prodname_ghe_server %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server#setting-up-your-trial-of-github-enterprise-server)" y "[Acerca de las licencias de {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)". diff --git a/translations/es-ES/data/reusables/enterprise_installation/upload-a-license-file.md b/translations/es-ES/data/reusables/enterprise_installation/upload-a-license-file.md index c3e4201458..ce89dcaf56 100644 --- a/translations/es-ES/data/reusables/enterprise_installation/upload-a-license-file.md +++ b/translations/es-ES/data/reusables/enterprise_installation/upload-a-license-file.md @@ -1 +1 @@ -2. En el prompt, carga tu archivo de licencia y configura una contraseña de consola de administración. For more information, see "[Managing your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise)." +2. En el prompt, carga tu archivo de licencia y configura una contraseña de consola de administración. Paa obtener más información, consulta la sección "[Administrar tu licencia de {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise)". diff --git a/translations/es-ES/data/reusables/enterprise_management_console/advanced-security-license.md b/translations/es-ES/data/reusables/enterprise_management_console/advanced-security-license.md index 1ba9937af1..181a0d6b9b 100644 --- a/translations/es-ES/data/reusables/enterprise_management_console/advanced-security-license.md +++ b/translations/es-ES/data/reusables/enterprise_management_console/advanced-security-license.md @@ -1 +1 @@ -If you can't see {% ifversion ghes < 3.2 %}**{% data variables.product.prodname_advanced_security %}**{% else %}**Security**{% endif %} in the sidebar, it means that your license doesn't include support for {% data variables.product.prodname_advanced_security %} features, including {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_secret_scanning %}. La licencia de {% data variables.product.prodname_advanced_security %} te permite acceder, a ti y a tus usuarios, a las características que te permiten añadir seguridad a tus repositorios ya tu código. {% ifversion ghes > 2.22 %}Para obtener más información, consulta la sección "[Acerca de GitHub Advanced Security](/github/getting-started-with-github/about-github-advanced-security)" o contacta a {% data variables.contact.contact_enterprise_sales %}.{% endif %} +Si no puedes ver la parte de {% ifversion ghes < 3.2 %}**{% data variables.product.prodname_advanced_security %}**{% else %}**Seguridad**{% endif %} en la barra lateral, significa que tu licencia no incluye soporte para las características de la {% data variables.product.prodname_advanced_security %}, incluyendo el {% data variables.product.prodname_code_scanning %} y {% data variables.product.prodname_secret_scanning %}. La licencia de {% data variables.product.prodname_advanced_security %} te permite acceder, a ti y a tus usuarios, a las características que te permiten añadir seguridad a tus repositorios ya tu código. {% ifversion ghes > 2.22 %}Para obtener más información, consulta la sección "[Acerca de GitHub Advanced Security](/github/getting-started-with-github/about-github-advanced-security)" o contacta a {% data variables.contact.contact_enterprise_sales %}.{% endif %} diff --git a/translations/es-ES/data/reusables/enterprise_management_console/advanced-security-tab.md b/translations/es-ES/data/reusables/enterprise_management_console/advanced-security-tab.md index 486f1ba382..48d9f54ff9 100644 --- a/translations/es-ES/data/reusables/enterprise_management_console/advanced-security-tab.md +++ b/translations/es-ES/data/reusables/enterprise_management_console/advanced-security-tab.md @@ -1,2 +1,2 @@ -1. In the left sidebar, click {% ifversion ghes < 3.2 %}**{% data variables.product.prodname_advanced_security %}**{% else %}**Security**{% endif %}.{% ifversion ghes < 3.2 %} ![Advanced Security sidebar](/assets/images/enterprise/management-console/sidebar-advanced-security.png){% else %} +1. En la barra lateral izquierda, haz clic en {% ifversion ghes < 3.2 %}**{% data variables.product.prodname_advanced_security %}**{% else %}**Seguridad**{% endif %}.{% ifversion ghes < 3.2 %} ![Advanced Security sidebar](/assets/images/enterprise/management-console/sidebar-advanced-security.png){% else %} ![Security sidebar](/assets/images/enterprise/3.2/management-console/sidebar-security.png){% endif %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/gated-features/codespaces.md b/translations/es-ES/data/reusables/gated-features/codespaces.md index 4b85591f8f..22aa3868a2 100644 --- a/translations/es-ES/data/reusables/gated-features/codespaces.md +++ b/translations/es-ES/data/reusables/gated-features/codespaces.md @@ -1 +1 @@ -Codespaces is available for organizations using {% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info-org-products %} +Codespaces está disponible para las organizaciones que utilicen {% data variables.product.prodname_team %} o {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info-org-products %} 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 8848c7a4e7..72f3046497 100644 --- a/translations/es-ES/data/reusables/gated-features/dependency-review.md +++ b/translations/es-ES/data/reusables/gated-features/dependency-review.md @@ -1,3 +1,3 @@ -{% ifversion fpt %}Dependency review is available for all public repositories and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled.{% endif %} -{% ifversion ghes > 3.1 %}Dependency review is available for organization-owned repositories where {% data variables.product.prodname_GH_advanced_security %} is enabled. +{% ifversion fpt %}La reviesión de dependencias se encuentra disponible para todos los repositorios públicos y para aquellos privados que pertenezcan a organizaciones en donde se haya habilitado la {% data variables.product.prodname_GH_advanced_security %}.{% endif %} +{% ifversion ghes > 3.1 %}La revisión de dependencias se encuentra disponible para los repositorios que pertenecen a las organizaciones en donde se encuentra habilitada la {% data variables.product.prodname_GH_advanced_security %}. {% endif %} {% data reusables.advanced-security.more-info-ghas %} diff --git a/translations/es-ES/data/reusables/gated-features/discussions.md b/translations/es-ES/data/reusables/gated-features/discussions.md index 65d9afd325..618609343f 100644 --- a/translations/es-ES/data/reusables/gated-features/discussions.md +++ b/translations/es-ES/data/reusables/gated-features/discussions.md @@ -1 +1 @@ -{% data variables.product.prodname_discussions %} is available for public and private repositories on {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.gated-features.more-info-org-products %} +Los {% data variables.product.prodname_discussions %} están disponibles para los repositorios públicos y privados en {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.gated-features.more-info-org-products %} diff --git a/translations/es-ES/data/reusables/gated-features/emus.md b/translations/es-ES/data/reusables/gated-features/emus.md new file mode 100644 index 0000000000..3e433f798a --- /dev/null +++ b/translations/es-ES/data/reusables/gated-features/emus.md @@ -0,0 +1 @@ +Para administrar a los usuarios de tu empresa con tu proveedor de identidad, esta debe habilitarse para {% data variables.product.prodname_emus %}, los cuales están disponibles con {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)". \ No newline at end of file diff --git a/translations/es-ES/data/reusables/gated-features/environments.md b/translations/es-ES/data/reusables/gated-features/environments.md index 3a83d0f0b2..b6ac8d0db2 100644 --- a/translations/es-ES/data/reusables/gated-features/environments.md +++ b/translations/es-ES/data/reusables/gated-features/environments.md @@ -1 +1 @@ -Environments, environment protection rules, and environment secrets are available in **public** repositories for all products. For access to environments in **private** repositories, you must use {% data variables.product.prodname_enterprise %}.{% ifversion fpt %} {% data reusables.gated-features.more-info %}{% endif %} +Los ambientes, las reglas de protección de ambiente y los secretos de ambiente se encuentran disponibles en los repositorios **públicos** para todos los productos. Para tener acceso a los ambientes en los repositorios **privados**, debes utilizar {% data variables.product.prodname_enterprise %}.{% data reusables.gated-features.more-info %}{% ifversion fpt %}{% endif %} diff --git a/translations/es-ES/data/reusables/gated-features/ghas.md b/translations/es-ES/data/reusables/gated-features/ghas.md index a8814b11e1..c398f84621 100644 --- a/translations/es-ES/data/reusables/gated-features/ghas.md +++ b/translations/es-ES/data/reusables/gated-features/ghas.md @@ -1 +1 @@ -{% data variables.product.prodname_GH_advanced_security %} is available for enterprise accounts on {% data variables.product.prodname_ghe_cloud %}{% ifversion ghae %}, {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_server %}.{% ifversion fpt %} {% data variables.product.prodname_GH_advanced_security %} is also included in all public repositories on {% data variables.product.prodname_dotcom_the_website %}.{% endif %} For more information, see "[About GitHub's products](/github/getting-started-with-github/githubs-products)." +{% data variables.product.prodname_GH_advanced_security %} se encuentra disponible para las cuentas empresariales en {% data variables.product.prodname_ghe_cloud %}{% ifversion ghae %}, {% data variables.product.prodname_ghe_managed %},{% endif %} y {% data variables.product.prodname_ghe_server %}.{% ifversion fpt %}{% data variables.product.prodname_GH_advanced_security %} también se incluye en todos los repositorios públicos en {% data variables.product.prodname_dotcom_the_website %}.{% endif %} Para obtener más información, consulta la sección "[Acerca de los productos de GitHub](/github/getting-started-with-github/githubs-products)". diff --git a/translations/es-ES/data/reusables/gated-features/restrict-email-domain.md b/translations/es-ES/data/reusables/gated-features/restrict-email-domain.md index ba3bebe8c6..e8a80879b2 100644 --- a/translations/es-ES/data/reusables/gated-features/restrict-email-domain.md +++ b/translations/es-ES/data/reusables/gated-features/restrict-email-domain.md @@ -1 +1 @@ -Restriction of email notifications to approved or verified domains is available with {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta la sección "[Productos de GitHub](/articles/githubs-products)". +La restricción de notificaciones de correo electrónico para los dominios aprobados o verificados se encuentra disponible con {% data variables.product.prodname_ghe_cloud %} y {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta la sección "[Productos de GitHub](/articles/githubs-products)". diff --git a/translations/es-ES/data/reusables/gated-features/verify-and-approve-domain.md b/translations/es-ES/data/reusables/gated-features/verify-and-approve-domain.md index 20ff542c7b..a8bc61e65b 100644 --- a/translations/es-ES/data/reusables/gated-features/verify-and-approve-domain.md +++ b/translations/es-ES/data/reusables/gated-features/verify-and-approve-domain.md @@ -1 +1 @@ -Verification and approval of domains is available with {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta la sección "[Productos de GitHub](/articles/githubs-products)". +La verificación y aprobación de dominios se encuentra disponible con {% data variables.product.prodname_ghe_cloud %} y {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta la sección "[Productos de GitHub](/articles/githubs-products)". diff --git a/translations/es-ES/data/reusables/gcm-core/next-time-you-clone.md b/translations/es-ES/data/reusables/gcm-core/next-time-you-clone.md index 06e9d9479b..b15c47da37 100644 --- a/translations/es-ES/data/reusables/gcm-core/next-time-you-clone.md +++ b/translations/es-ES/data/reusables/gcm-core/next-time-you-clone.md @@ -1 +1 @@ -The next time you clone an HTTPS URL that requires authentication, Git will prompt you to log in using a browser window. You may first be asked to authorize an OAuth app.{% ifversion not ghae %} If your account or organization requires [two-factor auth](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa), you'll also need to complete the 2FA challenge.{% endif %} +La próxima vez que clones una URL de HTTPS que requiera autenticación, Git te pedirá iniciar sesión utilizando una ventana de buscador. Podría ser que primero se te pida autorizar una app de OAuth.{% ifversion not ghae %} Si tu cuenta u organización requiere [autenticación bifactorial](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa), también necesitas completar el reto de 2FA.{% endif %} diff --git a/translations/es-ES/data/reusables/getting-started/about-and-creating-teams.md b/translations/es-ES/data/reusables/getting-started/about-and-creating-teams.md index e670dc630a..c35ee2f446 100644 --- a/translations/es-ES/data/reusables/getting-started/about-and-creating-teams.md +++ b/translations/es-ES/data/reusables/getting-started/about-and-creating-teams.md @@ -1,3 +1,3 @@ -Teams are groups of organization members that you can create to reflect your company or group's structure with cascading access permissions and mentions. Organization members can send notifications to a team or request reviews, and teams can be visible or secret. Para obtener más información, consulta la sección "[Acerca de los equipos](/organizations/organizing-members-into-teams/about-teams)". +Los equipos son grupos de miembros de una organización que puedes crear para reflejar la estructura de tu empresa o grupo con menciones y permisos de acceso en cascada. Los miembros de una organización pueden enviar notificaciones a un equipo o solicitar revisiones y los equipos pueden ser visibles o secretos. Para obtener más información, consulta la sección "[Acerca de los equipos](/organizations/organizing-members-into-teams/about-teams)". -You can create independent teams or have multiple levels of nested teams to reflect your group or company's hierarchy. For more information, see "[Creating a team](/organizations/organizing-members-into-teams/creating-a-team)." +Puedes crear equipos independientes o tener niveles múltiples de equipos anidados para reflejar la jerarquía de tu grupo o compañía. Para obtener más información, consulta la sección "[Crear un equipo](/organizations/organizing-members-into-teams/creating-a-team)". diff --git a/translations/es-ES/data/reusables/getting-started/actions.md b/translations/es-ES/data/reusables/getting-started/actions.md index 422b556614..164f0a69d9 100644 --- a/translations/es-ES/data/reusables/getting-started/actions.md +++ b/translations/es-ES/data/reusables/getting-started/actions.md @@ -1 +1 @@ -With {% data variables.product.prodname_actions %}, you can automate and customize {% data variables.product.product_location %}'s development workflow on {% data variables.product.product_name %}. Puedes crear tus propias acciones y usar y personalizar acciones compartidas por la comunidad {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Aprende sobre {% data variables.product.prodname_actions %}](/actions/learn-github-actions)". +Con las {% data variables.product.prodname_actions %}, puedes automatizar y personalizar el flujo de desarrollo de {% data variables.product.product_location %} en {% data variables.product.product_name %}. Puedes crear tus propias acciones y usar y personalizar acciones compartidas por la comunidad {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Aprende sobre {% data variables.product.prodname_actions %}](/actions/learn-github-actions)". diff --git a/translations/es-ES/data/reusables/getting-started/adding-members-to-organizations.md b/translations/es-ES/data/reusables/getting-started/adding-members-to-organizations.md index 7b4b952a80..7755485b1d 100644 --- a/translations/es-ES/data/reusables/getting-started/adding-members-to-organizations.md +++ b/translations/es-ES/data/reusables/getting-started/adding-members-to-organizations.md @@ -1 +1 @@ -You can add members to organizations in {% data variables.product.product_location %} as long as you are an organization owner in the organizations you want to manage. You can also configure visibility of organization membership. For more information, see "[Adding people to your organization](/organizations/managing-membership-in-your-organization/adding-people-to-your-organization)" and "[Configuring visibility for organization membership](/admin/user-management/managing-organizations-in-your-enterprise/configuring-visibility-for-organization-membership)." +Puedes agregar miembros a las organizaciones en {% data variables.product.product_location %} mientras seas propietario de una de las organizaciones que quieres administrar. También puedes configurar la visibilidad de la membrecía de la organización. Para obtener más información, consulta las secciones "[Agregar personas a tu organización](/organizations/managing-membership-in-your-organization/adding-people-to-your-organization)" y "[Configurar la visibilidad para la membresía de la organización](/admin/user-management/managing-organizations-in-your-enterprise/configuring-visibility-for-organization-membership)". diff --git a/translations/es-ES/data/reusables/getting-started/api.md b/translations/es-ES/data/reusables/getting-started/api.md index 50c60b9738..a4e188608a 100644 --- a/translations/es-ES/data/reusables/getting-started/api.md +++ b/translations/es-ES/data/reusables/getting-started/api.md @@ -1 +1 @@ -There are two versions of the {% data variables.product.prodname_dotcom %} API: the REST API and the GraphQL API. You can use the {% data variables.product.prodname_dotcom %} APIs to automate common tasks, [back up your data](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository/backing-up-a-repository), or {% ifversion fpt %}[create integrations](/github/customizing-your-github-workflow/exploring-integrations/about-integrations){% else %}create integrations{% endif %} that extend {% data variables.product.product_name %}. For more information, see "[About {% data variables.product.prodname_dotcom %}'s APIs](/developers/overview/about-githubs-apis)." +Hay dos versiones de la API de {% data variables.product.prodname_dotcom %}: la API de REST y la API de GraphQL. Puedes utilizar las API de {% data variables.product.prodname_dotcom %} para automatizar tareas comunes, [respaldar tus datos](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository/backing-up-a-repository) o {% ifversion fpt %}[crear integraciones](/github/customizing-your-github-workflow/exploring-integrations/about-integrations){% else %}crear integraciones{% endif %} que proporcione {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Acerca de las API de {% data variables.product.prodname_dotcom %}](/developers/overview/about-githubs-apis)". diff --git a/translations/es-ES/data/reusables/getting-started/configuring-security-features.md b/translations/es-ES/data/reusables/getting-started/configuring-security-features.md index 872e7b4ef6..a53fed017a 100644 --- a/translations/es-ES/data/reusables/getting-started/configuring-security-features.md +++ b/translations/es-ES/data/reusables/getting-started/configuring-security-features.md @@ -1 +1 @@ -To keep {% ifversion ghes or ghae %}the organizations in {% data variables.product.product_location %}{% else %}your organization{% endif %} secure, you can use a variety of {% data variables.product.prodname_dotcom %} security features, including security policies, dependency graphs, secret scanning and Dependabot security and version updates. For more information, see "[Securing your organization](/code-security/getting-started/securing-your-organization)" and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." +Para mantener la seguridad en {% ifversion ghes or ghae %}las organizaciones en {% data variables.product.product_location %}{% else %}tu organización{% endif %}, puedes utilizar diversas características de seguridad de {% data variables.product.prodname_dotcom %}, incluyendo las políticas de seguridad, gráficas de dependencias, escaneo de secretos y actualizaciones de versión y de seguridad del Dependabot. Para obtener más información, consulta las secciones "[Asegurar tu organización](/code-security/getting-started/securing-your-organization)" y "[Administrar la configuración de seguridad y análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". diff --git a/translations/es-ES/data/reusables/getting-started/contact-support-enterprise.md b/translations/es-ES/data/reusables/getting-started/contact-support-enterprise.md index ee9871562d..b0bdfec68d 100644 --- a/translations/es-ES/data/reusables/getting-started/contact-support-enterprise.md +++ b/translations/es-ES/data/reusables/getting-started/contact-support-enterprise.md @@ -1 +1 @@ -{% data variables.product.product_name %} includes access to {% data variables.contact.enterprise_support %}. {% data variables.contact.enterprise_support %} can help you troubleshoot issues that come up on {% data variables.product.product_name %}. {% ifversion ghes %}You can also choose to sign up for {% data variables.product.prodname_dotcom %} Premium Support for additional features. {% endif %}For more information, see "[About {% data variables.contact.enterprise_support %}](/admin/enterprise-support/overview/about-github-enterprise-support)." +{% data variables.product.product_name %} incluye el acceso a {% data variables.contact.enterprise_support %}. {% data variables.contact.enterprise_support %} puede ayudarte a solucionar los problemas que se presenten en {% data variables.product.product_name %}. {% ifversion ghes %}También puedes elegir registrarte para las características adicionales del Soporte Premium de {% data variables.product.prodname_dotcom %}. {% endif %}Para obtener más información, consulta la sección "[Acerca {% data variables.contact.enterprise_support %}](/admin/enterprise-support/overview/about-github-enterprise-support)". diff --git a/translations/es-ES/data/reusables/getting-started/contact-support.md b/translations/es-ES/data/reusables/getting-started/contact-support.md index 3ac5f5176f..f87c99ee0e 100644 --- a/translations/es-ES/data/reusables/getting-started/contact-support.md +++ b/translations/es-ES/data/reusables/getting-started/contact-support.md @@ -1 +1 @@ -{% data variables.contact.github_support %} puede ayudarte a solucionar los problemas con los que te encuentres cuando utilices {% data variables.product.prodname_dotcom %}. For more information, see “[About {% data variables.contact.github_support %}](/github/working-with-github-support/about-github-support)." +{% data variables.contact.github_support %} puede ayudarte a solucionar los problemas con los que te encuentres cuando utilices {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Acerca de {% data variables.contact.github_support %}](/github/working-with-github-support/about-github-support)". diff --git a/translations/es-ES/data/reusables/getting-started/creating-organizations.md b/translations/es-ES/data/reusables/getting-started/creating-organizations.md index 6553d119e4..2b65643331 100644 --- a/translations/es-ES/data/reusables/getting-started/creating-organizations.md +++ b/translations/es-ES/data/reusables/getting-started/creating-organizations.md @@ -1 +1 @@ -You can create new organizations in {% data variables.product.product_location %} to reflect your company or group's structure. Para obtener más información, consulta la sección "[Crear una organización nueva desde cero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)". +Puedes crear organizaciones nuevas en {% data variables.product.product_location %} para que reflejen la estructura de tu grupo o compañía. Para obtener más información, consulta la sección "[Crear una organización nueva desde cero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)". diff --git a/translations/es-ES/data/reusables/getting-started/creating-teams.md b/translations/es-ES/data/reusables/getting-started/creating-teams.md index a86eba853a..1ff3e18181 100644 --- a/translations/es-ES/data/reusables/getting-started/creating-teams.md +++ b/translations/es-ES/data/reusables/getting-started/creating-teams.md @@ -1 +1 @@ -Teams are groups of organization members that can be granted permissions to specific repositories as a group. You can create individual teams or multiple levels of nested teams in each of your organizations. For more information, see "[Creating teams](/organizations/organizing-members-into-teams/creating-a-team)" and "[Adding people to teams](/organizations/organizing-members-into-teams/adding-organization-members-to-a-team)." +Los equipos son grupos de miembros de organizaciones a los que se pueden otorgar permisos a repositorios específicos como un grupo. Puedes crear equipos individuales o niveles múltiples de equipos anidados en cada una de tus organizaciones. Para obtener más información, consulta las secciones "[Crear equipos](/organizations/organizing-members-into-teams/creating-a-team)" y "[Agregar personas a los equipos](/organizations/organizing-members-into-teams/adding-organization-members-to-a-team)". diff --git a/translations/es-ES/data/reusables/getting-started/customizing-and-automating.md b/translations/es-ES/data/reusables/getting-started/customizing-and-automating.md index c384e99f9c..5b27253d1e 100644 --- a/translations/es-ES/data/reusables/getting-started/customizing-and-automating.md +++ b/translations/es-ES/data/reusables/getting-started/customizing-and-automating.md @@ -1 +1 @@ -You can use tools from the {% data variables.product.prodname_marketplace %}, the {% data variables.product.product_name %} API, and existing {% data variables.product.product_name %} features to customize and automate your work. +Puedes utilizar las herramientas del {% data variables.product.prodname_marketplace %}, la API de {% data variables.product.product_name %} y características existentes de {% data variables.product.product_name %} para personalizar y automatizar tu trabajo. diff --git a/translations/es-ES/data/reusables/getting-started/enforcing-repo-management-policies.md b/translations/es-ES/data/reusables/getting-started/enforcing-repo-management-policies.md index bf68181320..c7ceb73aec 100644 --- a/translations/es-ES/data/reusables/getting-started/enforcing-repo-management-policies.md +++ b/translations/es-ES/data/reusables/getting-started/enforcing-repo-management-policies.md @@ -1 +1 @@ -As an enterprise owner, you can set repository management policies for all organizations in {% data variables.product.product_location %}, or allow policies to be set separately in each organization. Para obtener más información consulta la sección "[Requerir políticas de administración de repositorios en tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise)". +Como propietario de empresa, puedes configurar políticas de administración de repositorios para todas las organizaciones de {% data variables.product.product_location %} o permitir que las políticas se configuren por separado en cada organización. Para obtener más información consulta la sección "[Requerir políticas de administración de repositorios en tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise)". diff --git a/translations/es-ES/data/reusables/getting-started/enterprise-advanced-security.md b/translations/es-ES/data/reusables/getting-started/enterprise-advanced-security.md new file mode 100644 index 0000000000..85eb91af38 --- /dev/null +++ b/translations/es-ES/data/reusables/getting-started/enterprise-advanced-security.md @@ -0,0 +1 @@ +Si tienes una licencia de GitHub Advanced Security para tu cuenta empresarial, puedes requerir políticas para admnistrar las características de la Seguridad Avanzada de {% data variables.product.prodname_dotcom %} para las organizaciones que pertenecen a una cuenta empresarial. Para obtener más información, consulta la sección "[Requerir políticas de Seguridad Avanzada en tu cuenta empresarial](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-policies-for-advanced-security-in-your-enterprise-account)". \ No newline at end of file diff --git a/translations/es-ES/data/reusables/getting-started/github-pages-enterprise.md b/translations/es-ES/data/reusables/getting-started/github-pages-enterprise.md index eb381f7aaf..f491aae8f6 100644 --- a/translations/es-ES/data/reusables/getting-started/github-pages-enterprise.md +++ b/translations/es-ES/data/reusables/getting-started/github-pages-enterprise.md @@ -1 +1 @@ -{% data variables.product.prodname_pages %} is a static site hosting service that takes HTML, CSS, and JavaScript files straight from a repository and publishes a website. You can enable or disable {% data variables.product.prodname_pages %} for your enterprise members at the organization level. For more information, see "[Configuring {% data variables.product.prodname_pages %} for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise)" and "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)." +{% data variables.product.prodname_pages %} es un servicio de hospedaje de sitios estáticos que toma archivos de HTML, CSS y JavaScript directamente desde un repositorio y publica un sitio web. Puedes habilitar o inhabilitar las {% data variables.product.prodname_pages %} para tus miembros empresariales a nivel de organización. Para obtener más información, consulta las secciones "[Configurar las {% data variables.product.prodname_pages %} para tu empresa](/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise)" y "[Acerca de las {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)". diff --git a/translations/es-ES/data/reusables/getting-started/giving-access-to-repositories-projects-apps.md b/translations/es-ES/data/reusables/getting-started/giving-access-to-repositories-projects-apps.md index 1b73d10015..3a76ea0f16 100644 --- a/translations/es-ES/data/reusables/getting-started/giving-access-to-repositories-projects-apps.md +++ b/translations/es-ES/data/reusables/getting-started/giving-access-to-repositories-projects-apps.md @@ -1,3 +1,3 @@ -You can give organization members, teams, and outside collaborators different levels of access to repositories owned by your organization with granular permission levels. Para obtener más información, consulta "[Niveles de permiso del repositorio para una organización](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)". +Puedes otorgar diferentes niveles de acceso a los repositorios que pertenezcan a tu organización para los miembros, equipos y colaboradores de la misma con niveles de permiso granular. Para obtener más información, consulta "[Niveles de permiso del repositorio para una organización](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)". -You can also customize access to your organization's project boards and allow individual organization members to manage your organization's {% data variables.product.prodname_github_apps %}. For more information, see "[Managing access to your organization's project boards](/organizations/managing-access-to-your-organizations-project-boards)" and "[Managing access to your organization's apps](/organizations/managing-access-to-your-organizations-apps)." +También puedes personalizar el acceso a los tableros de proyecto de tu organización y permitir que miembros individuales de esta administren las {% data variables.product.prodname_github_apps %} de ella. Para obtener más información, consulta las secciones "[Administrar el acceso a los tableros de proyecto de tu organización](/organizations/managing-access-to-your-organizations-project-boards)" y "[Administrar el acceso a las apps de tu organización](/organizations/managing-access-to-your-organizations-apps)". diff --git a/translations/es-ES/data/reusables/getting-started/learning-lab-enterprise.md b/translations/es-ES/data/reusables/getting-started/learning-lab-enterprise.md index f4810ab1b9..896e71b323 100644 --- a/translations/es-ES/data/reusables/getting-started/learning-lab-enterprise.md +++ b/translations/es-ES/data/reusables/getting-started/learning-lab-enterprise.md @@ -1,3 +1,3 @@ -Your enterprise members can learn new skills by completing fun, realistic projects in their very own GitHub repository with [{% data variables.product.prodname_learning %}](https://lab.github.com/). Each course is a hands-on lesson created by the GitHub community and taught by the friendly Learning Lab bot. +Los miembros de tu empresa pueden aprender habilidades nuevas completando proyectos divertidos y realistas en su propio repositorio de GitHub con [{% data variables.product.prodname_learning %}](https://lab.github.com/). Cada curso es una lección didáctica que creó la comunidad de GitHub y que la enseña el amigable bot del Laboratorio de Aprendizaje. -For more information, see “[Git and {% data variables.product.prodname_dotcom %} learning resources](/github/getting-started-with-github/quickstart/git-and-github-learning-resources)." +Para obtener más información, consulta la sección "[Recursos de aprendizaje de Git y de {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/quickstart/git-and-github-learning-resources)". diff --git a/translations/es-ES/data/reusables/getting-started/learning-lab.md b/translations/es-ES/data/reusables/getting-started/learning-lab.md index 2a87845e26..b559e487cd 100644 --- a/translations/es-ES/data/reusables/getting-started/learning-lab.md +++ b/translations/es-ES/data/reusables/getting-started/learning-lab.md @@ -1,3 +1,3 @@ -You can learn new skills by completing fun, realistic projects in your very own GitHub repository with [{% data variables.product.prodname_learning %}](https://lab.github.com/). Each course is a hands-on lesson created by the GitHub community and taught by the friendly Learning Lab bot. +Puedes aprender habilidades nuevas completando proyectos divertidos y realistas en tu propio repositorio de GitHub con [{% data variables.product.prodname_learning %}](https://lab.github.com/). Cada curso es una lección didáctica que creó la comunidad de GitHub y que la enseña el amigable bot del Laboratorio de Aprendizaje. -For more information, see “[Git and {% data variables.product.prodname_dotcom %} learning resources](/github/getting-started-with-github/quickstart/git-and-github-learning-resources)." +Para obtener más información, consulta la sección "[Recursos de aprendizaje de Git y de {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/quickstart/git-and-github-learning-resources)". diff --git a/translations/es-ES/data/reusables/getting-started/managing-enterprise-members.md b/translations/es-ES/data/reusables/getting-started/managing-enterprise-members.md index e178feaeb3..b3e4763d03 100644 --- a/translations/es-ES/data/reusables/getting-started/managing-enterprise-members.md +++ b/translations/es-ES/data/reusables/getting-started/managing-enterprise-members.md @@ -1 +1 @@ -You can manage settings and audit activity for the members of {% data variables.product.product_location %}. You can {% ifversion ghes %}promote an enterprise member to be a site administrator, {% endif %}manage dormant users, view the audit log for user activity, and customize messages that enterprise members will see. For more information, see "[Managing users in your enterprise](/admin/user-management/managing-users-in-your-enterprise)." +Puedes administrar los ajustes y la actividad de auditoría para los miembros de {% data variables.product.product_location %}. Puedes {% ifversion ghes %}promover a un miembro de la empresa para que sea un adminsitrador de sitio, {% endif %}administrar usuarios inactivos, ver la bitácora de auditoría para la actividad de usuario y personalizar los mensajes que verán los miembros empresariales. Para obtener más información, consulta la sección "[Administrar usuarios en tu empresa](/admin/user-management/managing-users-in-your-enterprise)". diff --git a/translations/es-ES/data/reusables/getting-started/managing-org-members.md b/translations/es-ES/data/reusables/getting-started/managing-org-members.md index e57ffb217b..1876d0fe23 100644 --- a/translations/es-ES/data/reusables/getting-started/managing-org-members.md +++ b/translations/es-ES/data/reusables/getting-started/managing-org-members.md @@ -1 +1 @@ -You can invite anyone to be a member of your organization, as long as they have a personal account on {% data variables.product.prodname_dotcom %}. You can also remove members and reinstate former members. For more information, see "[Managing membership in your organization](/organizations/managing-membership-in-your-organization)." +Puedes invitar a cualquiera para que sea un miembro de tu organización, siempre y cuando tengan una cuenta personal en {% data variables.product.prodname_dotcom %}. También puedes eliminar a los miembros y reinstaurar a los miembros anteriores. Para obtener más información, consulta la sección "[Administrar la membrecía de tu organización](/organizations/managing-membership-in-your-organization)". diff --git a/translations/es-ES/data/reusables/getting-started/managing-org-policies.md b/translations/es-ES/data/reusables/getting-started/managing-org-policies.md index 717d24f2ed..8d136524ce 100644 --- a/translations/es-ES/data/reusables/getting-started/managing-org-policies.md +++ b/translations/es-ES/data/reusables/getting-started/managing-org-policies.md @@ -1,5 +1,5 @@ -You can manage permissions and policies for a number of different actions and features in your organization. +Puedes administrar permisos y políticas para varias acciones y características diferentes de tu organización. -For example, to protect your organization's data and number of paid licenses, you can choose to allow only organization owners to invite outside collaborators to organization repositories. You can also choose to allow or prevent the forking of private repositories owned by your organization. For more information, see "[Setting permissions for adding outside collaborators](/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators)" and "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)." +Por ejemplo, para proteger los datos y la cantidad de licencias de pago de tu organización, puedes elegir solo permitir a los propietarios de las organizaciones invitar colaboradores a los repositorios organizacionales. También puedes elegir permitir o prevenir la bifurcación de los repositorios privados que pertenecen a tu organización. Para obtener más información, consulta las secciones "[Configurar permisos para agregar colaboradores externos](/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators)" y "[Administrar la política de bifurcación de tu organización](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)". -For the full list of settings you can configure for your organization, see "[Managing organization settings](/organizations/managing-organization-settings)." +Para obtener la lista completa de ajustes que puedes configurar para tu organización, consulta la sección "[Administrar los ajustes de una organización](/organizations/managing-organization-settings)". diff --git a/translations/es-ES/data/reusables/getting-started/managing-repo-changes.md b/translations/es-ES/data/reusables/getting-started/managing-repo-changes.md index bc3b0ebbce..e3071a7aa1 100644 --- a/translations/es-ES/data/reusables/getting-started/managing-repo-changes.md +++ b/translations/es-ES/data/reusables/getting-started/managing-repo-changes.md @@ -1,3 +1,3 @@ -You can configure permissions for creating, transferring and deleting repositories in your organization, including which types members can create. For more information, see "[Restricting repository creation in your organization](/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization)" and "[Setting permissions for deleting or transferring repositories](/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories)." +Puedes configurar los permisos para crear, transferir y borrar los repositorios de tu organización, incluyendo qué tipos pueden crear los miembros. Para obtener más información, consulta las secciones "[Restringir la creación de repositorios en tu organización](/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization)" y "[Configurar los permisos para borrar o transferir los repositorios](/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories)". -You can also restrict or grant the ability to change repository visibility. Para obtener más información, consulta la sección "[Restringir los cambios a la visibilidad del repositorio en tu organización](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)". +También puedes restringir u otorgar la capacidad de cambiar la visibilidad de los repositorios. Para obtener más información, consulta la sección "[Restringir los cambios a la visibilidad del repositorio en tu organización](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)". diff --git a/translations/es-ES/data/reusables/getting-started/managing-team-settings.md b/translations/es-ES/data/reusables/getting-started/managing-team-settings.md index ddfaf48c4e..7ad3183a44 100644 --- a/translations/es-ES/data/reusables/getting-started/managing-team-settings.md +++ b/translations/es-ES/data/reusables/getting-started/managing-team-settings.md @@ -1,3 +1,3 @@ -You can designate a "team maintainer" to manage team settings and discussions, among other privileges. For more information, see "[Giving "team maintainer" permissions to an organization member](/organizations/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member)." +Puedes designar un "mantenedor de equipo" para administrar los ajustes y debates del equipo, entre otros privilegios. Para obtener más información, consulta la sección "[Otorgar permisos de "mantenedor de equipo" a un miembro de la organización](/organizations/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member)". -You can manage code review assignments for your team, change team visibility, manage scheduled reminders for your team, and more in your team's settings. For more information, see "[Organizing members into teams](/organizations/organizing-members-into-teams)." +Puedes administrar las tareas de revisión de código para tu equipo, cambiar la visibilidad de los equipos, administrar los recordatorios programados para tus equipos y más en los ajustes de equipo. Para obtener más información, consulta la sección "[Organizar miembros en equipos](/organizations/organizing-members-into-teams)". diff --git a/translations/es-ES/data/reusables/getting-started/marketplace.md b/translations/es-ES/data/reusables/getting-started/marketplace.md index 72261fef0d..5283cdf6a7 100644 --- a/translations/es-ES/data/reusables/getting-started/marketplace.md +++ b/translations/es-ES/data/reusables/getting-started/marketplace.md @@ -1 +1 @@ -{% data variables.product.prodname_marketplace %} contains integrations that add functionality and improve your workflow. En [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace), puedes descubrir, buscar e instalar herramientas gratuitas y de pago, incluyendo {% data variables.product.prodname_github_app %}s, {% data variables.product.prodname_oauth_app %}s, y {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_marketplace %}](/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace)". +{% data variables.product.prodname_marketplace %} contiene integraciones que agregan funcionalidad y mejoran tu flujo de trabajo. En [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace), puedes descubrir, buscar e instalar herramientas gratuitas y de pago, incluyendo {% data variables.product.prodname_github_app %}s, {% data variables.product.prodname_oauth_app %}s, y {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_marketplace %}](/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace)". diff --git a/translations/es-ES/data/reusables/getting-started/open-source-projects.md b/translations/es-ES/data/reusables/getting-started/open-source-projects.md index dd72b489de..775dab2bcf 100644 --- a/translations/es-ES/data/reusables/getting-started/open-source-projects.md +++ b/translations/es-ES/data/reusables/getting-started/open-source-projects.md @@ -1,4 +1,4 @@ -Contributing to open source projects on {% data variables.product.prodname_dotcom %} can be a rewarding way to learn, teach, and build experience in just about any skill you can imagine. For more information, see “[How to Contribute to Open Source](https://opensource.guide/how-to-contribute/)" in the Open Source Guides. +El contribuir con proyectos de código abierto en {% data variables.product.prodname_dotcom %} puede ser una forma gratificante de aprender, enseñar y crear una experiencia sobre cualquier habilidad que te puedas imaginar. Para obtener más información, consulta la sección "[Cómo contribuir con el código abierto](https://opensource.guide/how-to-contribute/)" en las Guías de código abierto. -You can find personalized recommendations for projects and good first issues based on your past contributions, stars, and other activities in [Explore](https://github.com/explore).{% ifversion fpt %} For more information, see “[Finding ways to contribute to open source on GitHub](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)." +Puedes encontrar recomendaciones personalizadas para los proyectos y buenas primeras propuestas con base en tus contribuciones anteriores, marcas de favoritos y otras actividades en [Explorar](https://github.com/explore).{% ifversion fpt %} Para obtener más información, consulta la sección "[Encontrar formas para contribuir con los proyectos de código abierto en GitHub](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)". {% endif %} diff --git a/translations/es-ES/data/reusables/getting-started/org-permissions-and-roles.md b/translations/es-ES/data/reusables/getting-started/org-permissions-and-roles.md index be1ae3d08d..6d8bc018c9 100644 --- a/translations/es-ES/data/reusables/getting-started/org-permissions-and-roles.md +++ b/translations/es-ES/data/reusables/getting-started/org-permissions-and-roles.md @@ -1 +1 @@ -Each person in your organization has a role that defines their level of access to the organization. The member role is the default, and you can assign owner and billing manager roles as well as "team maintainer" permissions. Para obtener más información, consulta ´la sección "[Niveles de permisos para una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization)". +Cada persona en tu organización tiene un rol que define su nivel de acceso a esta. El rol de miembro es el predeterminado y puedes asignar roles de propietario y gerente de facturación así como permisos de "mantenedor de equipo". Para obtener más información, consulta ´la sección "[Niveles de permisos para una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization)". diff --git a/translations/es-ES/data/reusables/getting-started/packages.md b/translations/es-ES/data/reusables/getting-started/packages.md index 528d229fca..0b92395547 100644 --- a/translations/es-ES/data/reusables/getting-started/packages.md +++ b/translations/es-ES/data/reusables/getting-started/packages.md @@ -1 +1 @@ -{% data variables.product.prodname_registry %} es un servicio de alojamiento de paquete de software que te permite alojar tus paquetes de software de forma privada o pública y usar paquetes como dependencias en tus proyectos. For more information, see “[Introduction to {% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages)." +{% data variables.product.prodname_registry %} es un servicio de alojamiento de paquete de software que te permite alojar tus paquetes de software de forma privada o pública y usar paquetes como dependencias en tus proyectos. Para obtener más información, consulta la sección "[Introducción al {% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages)". diff --git a/translations/es-ES/data/reusables/getting-started/participating-in-community.md b/translations/es-ES/data/reusables/getting-started/participating-in-community.md index d5575e40e6..22ade06010 100644 --- a/translations/es-ES/data/reusables/getting-started/participating-in-community.md +++ b/translations/es-ES/data/reusables/getting-started/participating-in-community.md @@ -1 +1 @@ -There are many ways to participate in the {% data variables.product.prodname_dotcom %} community. You can contribute to open source projects, interact with people in the {% data variables.product.prodname_gcf %}, or learn with {% data variables.product.prodname_learning %}. +Hay muchas formas de participar en la comunidad de {% data variables.product.prodname_dotcom %}. Puedes contribuir con los proyectos de código abierto, interactuar con las personas en {% data variables.product.prodname_gcf %} o aprender con {% data variables.product.prodname_learning %}. diff --git a/translations/es-ES/data/reusables/getting-started/requiring-2fa.md b/translations/es-ES/data/reusables/getting-started/requiring-2fa.md index f2b1d1c208..93798e764b 100644 --- a/translations/es-ES/data/reusables/getting-started/requiring-2fa.md +++ b/translations/es-ES/data/reusables/getting-started/requiring-2fa.md @@ -1 +1 @@ -You can view whether your organization members have two-factor authentication enabled and choose to require two-factor authentication in your organization. Para obtener más información, consulta "[Solicitar la autenticación de dos factores en tu organización](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)". +Puedes ver si los miembros de tu organización tienen habilitada la autenticación bifactorial y elegir requerir la autenticación bifactorial en tu organización. Para obtener más información, consulta "[Solicitar la autenticación de dos factores en tu organización](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)". diff --git a/translations/es-ES/data/reusables/getting-started/reviewing-org-audit-log-and-integrations.md b/translations/es-ES/data/reusables/getting-started/reviewing-org-audit-log-and-integrations.md index 69712f3636..6a23a0afa7 100644 --- a/translations/es-ES/data/reusables/getting-started/reviewing-org-audit-log-and-integrations.md +++ b/translations/es-ES/data/reusables/getting-started/reviewing-org-audit-log-and-integrations.md @@ -1,3 +1,3 @@ -The audit log for your organization allows you, as an organization owner, to review the actions performed by members of the organization within the last 90 days. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization)." +La bitácora de auditoría de tu organización te permite, como propietario de la organización, revisar las acciones que llevan a cabo los miembros de la organización dentro de los últimos 90 días. Para obtener más información, consulta la sección "[Revisar la bitácora de auditoría de tu organización](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization)". -You can also review and configure the permission levels for your organization's installed integrations. For more information, see "[Reviewing your organization's installed integrations](/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations)." +También puedes revisar y configurar los niveles de permiso de las integraciones instaladas en tu organización. Para obtener más información, consulta la sección "[Revisar las integraciones autorizadas de tu organización](/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations)". diff --git a/translations/es-ES/data/reusables/getting-started/setting-org-and-repo-permissions.md b/translations/es-ES/data/reusables/getting-started/setting-org-and-repo-permissions.md index 9dc3f590ae..336306c3e6 100644 --- a/translations/es-ES/data/reusables/getting-started/setting-org-and-repo-permissions.md +++ b/translations/es-ES/data/reusables/getting-started/setting-org-and-repo-permissions.md @@ -1,3 +1,3 @@ -We recommend giving a limited number of members in each organization an organization owner role, which provides complete administrative access for that organization. Para obtener más información, consulta ´la sección "[Niveles de permisos para una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization)". +Te recomendamos proporcionar una cantidad limitada de miembros en cada organización y rol de propietario de organización, lo cual proporciona acceso administrativo completo para ellas. Para obtener más información, consulta ´la sección "[Niveles de permisos para una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization)". -For organizations where you have admin permissions, you can also customize access to each repository with granular permission levels. For more information, see "[Repository permissions levels for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)." +En el caso de las organizaciones en donde tienes permisos administrativos, también puedes personalizar el acceso a cada repositorio con niveles de permiso granulares. Para obtener más información, consulta la sección "[Niveles de permisos del repositorio para una organización](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)". diff --git a/translations/es-ES/data/reusables/getting-started/sponsors.md b/translations/es-ES/data/reusables/getting-started/sponsors.md index af9e9f8639..b0d6e95b26 100644 --- a/translations/es-ES/data/reusables/getting-started/sponsors.md +++ b/translations/es-ES/data/reusables/getting-started/sponsors.md @@ -1 +1 @@ -{% data variables.product.prodname_sponsors %} allows you to make a monthly recurring payment to a developer or organization who designs, creates, or maintains open source projects you depend on. For more information, see “[About {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." +{% data variables.product.prodname_sponsors %} te permite hacer un pago mensual recurrente a un desarrollador u organización que diseñe, cree o mantenga proyectos de código abierto de los cuales dependas. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)". diff --git a/translations/es-ES/data/reusables/getting-started/using-org-community-files-and-moderation-tools.md b/translations/es-ES/data/reusables/getting-started/using-org-community-files-and-moderation-tools.md index 3d9acc3f03..0664b86dc6 100644 --- a/translations/es-ES/data/reusables/getting-started/using-org-community-files-and-moderation-tools.md +++ b/translations/es-ES/data/reusables/getting-started/using-org-community-files-and-moderation-tools.md @@ -1,3 +1,3 @@ -You can create default community health files, such as a CONTRIBUTING.md file, a CODE_OF_CONDUCT.md file, or even issue and pull request templates, for your organization. These default files will be used for any repository owned by your organization that does not contain its own file of that type. 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 archivos de salud comunitaria, tales como el archivo CONTRIBUTING.md, un archivo CODE_OF_CONDUCT.md o incluso plantillas de propuestas y de solicitudes de cambios para tu organziación. Estos archivos predeterminados pueden utilizarse para cualquier repositorio que le pertenezca a tu organización y no contenga su propio archivo de este tipo. 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)." -{% data variables.product.prodname_dotcom %} offers multiple tools for moderating and managing your community. For more information, see "[Tools for moderating your community](/communities/setting-up-your-project-for-healthy-contributions/about-community-management-and-moderation#tools-for-moderating-your-community)." +{% data variables.product.prodname_dotcom %} ofrece varias herramientas para moderar y mantener tu comunidad. Para obtener más información, consulta la sección "[Herramientas para moderar a tu comunidad](/communities/setting-up-your-project-for-healthy-contributions/about-community-management-and-moderation#tools-for-moderating-your-community)". diff --git a/translations/es-ES/data/reusables/github-actions/actions-on-examples.md b/translations/es-ES/data/reusables/github-actions/actions-on-examples.md index 4eadd48407..07311c8e88 100644 --- a/translations/es-ES/data/reusables/github-actions/actions-on-examples.md +++ b/translations/es-ES/data/reusables/github-actions/actions-on-examples.md @@ -1,18 +1,18 @@ -### Ejemplo: utilizando un solo evento +## Ejemplo: utilizando un solo evento ```yaml # Triggered when code is pushed to any branch in a repository on: push ``` -### Ejemplo: Utilizando una lista de eventos +## Ejemplo: Utilizando una lista de eventos ```yaml # Triggers the workflow on push or pull request events on: [push, pull_request] ``` -### Ejemplo: Utilizando eventos múltiples con tipos de actividad o configuración +## Ejemplo: Utilizando eventos múltiples con tipos de actividad o configuración Si necesitas especificar tipos de actividad o configuración para un evento, debes configurar cada evento por separado. Debes agregar dos puntos (`:`) a todos los eventos, incluyendo aquellos sin configuración. diff --git a/translations/es-ES/data/reusables/github-actions/actions-spending-limit-brief.md b/translations/es-ES/data/reusables/github-actions/actions-spending-limit-brief.md index d483827302..6fa38db593 100644 --- a/translations/es-ES/data/reusables/github-actions/actions-spending-limit-brief.md +++ b/translations/es-ES/data/reusables/github-actions/actions-spending-limit-brief.md @@ -1 +1 @@ -If you are a monthly-billed customer, your account will have a default spending limit of 0 US dollars (USD), which prevents additional usage of minutes or storage for private repositories beyond the amounts included with your account. Si pagas tu cuenta por factura, ésta tendrá un límite de gastos ilimitado predeterminadamente. +Si eres un cliente que factura mensualmente, tu cuenta tendrá un límite de gastos predeterminado de 0 dólares Estadounidenses (USD), lo cual previene el uso adicional de minutos o almacenamiento para los repositorios privados más allá de las cantidades que se incluyen en tu cuenta. Si pagas tu cuenta por factura, ésta tendrá un límite de gastos ilimitado predeterminadamente. diff --git a/translations/es-ES/data/reusables/github-actions/actions-spending-limit-detailed.md b/translations/es-ES/data/reusables/github-actions/actions-spending-limit-detailed.md index 1497c63078..81d05a2b04 100644 --- a/translations/es-ES/data/reusables/github-actions/actions-spending-limit-detailed.md +++ b/translations/es-ES/data/reusables/github-actions/actions-spending-limit-detailed.md @@ -1,3 +1,3 @@ {% data reusables.github-actions.actions-spending-limit-brief %} -If you have an unlimited spending limit or a spending limit set higher than $0 USD, you will be billed for any additional minutes or storage beyond the included amounts in your account, also called overages. {% data variables.product.prodname_dotcom %} cobra el uso a la cuenta a la que pertenezca el repositorio en donde se ejecuta un flujo de trabajo. No podrán aplicarse los cupones que tenga tu cuenta para los excedentes de {% data variables.product.prodname_actions %}. +Si tu límite de gastos es ilimitado o lo configuraste en más de $0 USD, se te facturará por cualquier minuto o almacenamiento adicional que esté más allá de las cantidades que se incluyen en tu cuenta, lo cual también se conoce como excedentes. {% data variables.product.prodname_dotcom %} cobra el uso a la cuenta a la que pertenezca el repositorio en donde se ejecuta un flujo de trabajo. No podrán aplicarse los cupones que tenga tu cuenta para los excedentes de {% data variables.product.prodname_actions %}. diff --git a/translations/es-ES/data/reusables/github-actions/disabling-github-actions.md b/translations/es-ES/data/reusables/github-actions/disabling-github-actions.md index 35fd3440d7..c8253e7deb 100644 --- a/translations/es-ES/data/reusables/github-actions/disabling-github-actions.md +++ b/translations/es-ES/data/reusables/github-actions/disabling-github-actions.md @@ -1 +1 @@ -Predeterminadamente, {% ifversion ghes or ghae %}después de que se habilita {% data variables.product.prodname_actions %} en {% data variables.product.product_location %}, este {% elsif fpt %} las {% data variables.product.prodname_actions %}{% endif %} se habilita en todos los repositorios y organizaciones. Puedes elegir inhabilitar las {% data variables.product.prodname_actions %} o limitarlas para las acciones privadas únicamente, lo cual significa que las personas solo podrá utilizar las acciones que existan en tu repositorio. +Predeterminadamente, {% ifversion ghes or ghae %}después de que se habilita {% data variables.product.prodname_actions %} en {% data variables.product.product_location %}, este {% elsif fpt %} las {% data variables.product.prodname_actions %}{% endif %} se habilita en todos los repositorios y organizaciones. Puedes elegir inhabilitar las {% data variables.product.prodname_actions %} o limitarlas para las acciones locales únicamente, lo cual significa que las personas solo podrá utilizar las acciones que existan en tu repositorio. diff --git a/translations/es-ES/data/reusables/github-actions/forked-write-permission.md b/translations/es-ES/data/reusables/github-actions/forked-write-permission.md index 4cff430e00..5a3c51952e 100644 --- a/translations/es-ES/data/reusables/github-actions/forked-write-permission.md +++ b/translations/es-ES/data/reusables/github-actions/forked-write-permission.md @@ -1 +1 @@ -Puedes utilizar la clave `permissions` para agregar y eliminar los permisos de lectura para los repositorios bifurcados pero, habitualmente, no puedes otorgar acceso de escritura. La excepción a este comportamiento es donde un usuario administrador seleccionó la opción de **Enviar tokens a los flujos de trabajo desde las solicitudes de cambios** en la configuración de {% data variables.product.prodname_actions %}. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#enabling-workflows-for-private-repository-forks)." +Puedes utilizar la clave `permissions` para agregar y eliminar los permisos de lectura para los repositorios bifurcados pero, habitualmente, no puedes otorgar acceso de escritura. La excepción a este comportamiento es donde un usuario administrador seleccionó la opción de **Enviar tokens a los flujos de trabajo desde las solicitudes de cambios** en la configuración de {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Administrar la configuración de {% data variables.product.prodname_actions %} en un repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#enabling-workflows-for-private-repository-forks)". diff --git a/translations/es-ES/data/reusables/github-actions/macos-runner-preview.md b/translations/es-ES/data/reusables/github-actions/macos-runner-preview.md index 5302cf8c7c..8ca052061f 100644 --- a/translations/es-ES/data/reusables/github-actions/macos-runner-preview.md +++ b/translations/es-ES/data/reusables/github-actions/macos-runner-preview.md @@ -1 +1 @@ -The macos-latest YAML workflow label currently uses the macOS 10.15 virtual environment. +La etiqueta de flujo de trabajo de YAML macos-latest utiliza actualmente el ambiente virtual de macOS 10.15. diff --git a/translations/es-ES/data/reusables/github-actions/name-environment.md b/translations/es-ES/data/reusables/github-actions/name-environment.md new file mode 100644 index 0000000000..3c6ad4b0ea --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/name-environment.md @@ -0,0 +1 @@ +1. Ingresa un nombre para el ambiente y luego da clic en **Configurar ambiente**. Los nombres de ambiente no distinguen entre mayúsculas y minúsculas. Un nombre de ambiente no deberá exceder los 255 caracteres y deberá ser único dentro del repositorio. diff --git a/translations/es-ES/data/reusables/github-actions/new-environment.md b/translations/es-ES/data/reusables/github-actions/new-environment.md new file mode 100644 index 0000000000..ff54e1d516 --- /dev/null +++ b/translations/es-ES/data/reusables/github-actions/new-environment.md @@ -0,0 +1 @@ +1. Da clic en **Ambiente nuevo**. diff --git a/translations/es-ES/data/reusables/github-actions/private-repository-forks-overview.md b/translations/es-ES/data/reusables/github-actions/private-repository-forks-overview.md index cb84267867..4b65523e30 100644 --- a/translations/es-ES/data/reusables/github-actions/private-repository-forks-overview.md +++ b/translations/es-ES/data/reusables/github-actions/private-repository-forks-overview.md @@ -1,4 +1,4 @@ -Si dependes en el uso de bifurcaciones de tus repositorios privados, puedes configurar las políticas que controlan cómo los usuarios pueden ejecutar flujos de trabajo en los eventos de `pull_request`. Available to private and internal repositories only, you can configure these policy settings for enterprises, organizations, or repositories. For enterprise accounts, the policies are applied to all repositories in all organizations. +Si dependes en el uso de bifurcaciones de tus repositorios privados, puedes configurar las políticas que controlan cómo los usuarios pueden ejecutar flujos de trabajo en los eventos de `pull_request`. Disponible solo para repositorios privados e internos, puedes configurar los ajustes de esta política para empresas, organizaciones y repositorios. For enterprise accounts, the policies are applied to all repositories in all organizations. - **Ejecutar flujos de trabajo desde las solicitudes de extracción de las bifurcaciones** - permite a los usuarios ejecutar flujos de trabajo desde las solicitudes de extracción de las bifurcaciones utilizando un `GITHUB_TOKEN` con permisos de solo lectura y sin acceso a los secretos. - **Enviar tokens de escritura a los flujos de trabajo desde las solicitudes de extracción** - Permite a las solicitudes de extracción de las bifuraciones utilizar un `GITHUB_TOKEN` con permiso de escritura. diff --git a/translations/es-ES/data/reusables/github-actions/runner-group-assign-policy-org.md b/translations/es-ES/data/reusables/github-actions/runner-group-assign-policy-org.md index 46e73ea4e7..c768df76d4 100644 --- a/translations/es-ES/data/reusables/github-actions/runner-group-assign-policy-org.md +++ b/translations/es-ES/data/reusables/github-actions/runner-group-assign-policy-org.md @@ -1,3 +1,3 @@ 1. Ingresa un nombre para tu grupo de ejecutores y asigna una política para el acceso organizacional. - Puedes configurar un grupo de ejecutores para que una lista específica de organizaciones o todas las organizaciones de la empresa puedan acceder a él. Predeterminadamente, solo los repositorios privados pueden acceder a los ejecutores en un grupo de ejecutores, pero puedes anular esto. This setting can't be overridden if configuring an organization's runner group that was shared by an enterprise. \ No newline at end of file + Puedes configurar un grupo de ejecutores para que una lista específica de organizaciones o todas las organizaciones de la empresa puedan acceder a él. Predeterminadamente, solo los repositorios privados pueden acceder a los ejecutores en un grupo de ejecutores, pero puedes anular esto. Esta configuración no puede anularse si se configura el grupo de ejecutores de una organización que compartió una empresa. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/github-actions/runner-group-assign-policy-repo.md b/translations/es-ES/data/reusables/github-actions/runner-group-assign-policy-repo.md index ff8083fd22..1f01d06d84 100644 --- a/translations/es-ES/data/reusables/github-actions/runner-group-assign-policy-repo.md +++ b/translations/es-ES/data/reusables/github-actions/runner-group-assign-policy-repo.md @@ -1,3 +1,3 @@ 1. Ingresa un nombre para tu grupo de ejecutores y asigna una política para el acceso al repositorio. - Puedes configurar un grupo de ejecutores para que una lista específica de repositorios puedan acceder a este o para que todos los repositorios de la organización puedan hacerlo. Predeterminadamente, solo los repositorios privados pueden acceder a los ejecutores en un grupo de ejecutores, pero puedes anular esto. This setting can't be overridden if configuring an organization's runner group that was shared by an enterprise. \ No newline at end of file + Puedes configurar un grupo de ejecutores para que una lista específica de repositorios puedan acceder a este o para que todos los repositorios de la organización puedan hacerlo. Predeterminadamente, solo los repositorios privados pueden acceder a los ejecutores en un grupo de ejecutores, pero puedes anular esto. Esta configuración no puede anularse si se configura el grupo de ejecutores de una organización que compartió una empresa. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-check-installation-success.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-check-installation-success.md index b802fa9967..ace5ff396a 100644 --- a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-check-installation-success.md +++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-check-installation-success.md @@ -1,7 +1,7 @@ ### Revisar que tu ejecutor auto-hospedado se haya agregado exitosamente -After completing the steps to add a self-hosted runner, the runner and its status are now listed under {% ifversion fpt %}"Runners"{% elsif ghae or ghes %}"Self-hosted runners"{% endif %}. +Después de completar estos pasos para agregar un ejecutor auto-hospedado, dicho ejecutor y su estado ahora se listan bajo {% ifversion fpt %}"Ejecutores"{% elsif ghae or ghes %}"Ejecutores auto-hospedados"{% endif %}. La aplicación del ejecutor autoalojado debe estar activa para que el ejecutor acepte trabajos. Cuando la aplicación del ejecutor está conectada a {% data variables.product.product_name %} y lista para recibir trabajos, verás el siguiente mensaje en la terminal de la máquina. diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md index 2b6f89b5b1..f20c06745b 100644 --- a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md +++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md @@ -1,6 +1,7 @@ -1. En la sección de {% ifversion fpt %}"ejecutores"{% else %}"ejecutores auto-hospedados"{% endif %} de la página de ajustes, haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} junto al grupo de ejecutores que te gustaría configurar y luego en **Editar el nombre y acceso a la [organización|repositorio]**. ![Administrar permisos del repositorio](/assets/images/help/settings/actions-runner-manage-permissions.png) +1. En la sección de {% ifversion fpt or ghes > 3.1 or ghae-next %}"ejecutores"{% else %}"ejecutores auto-hospedados"{% endif %} de la página de ajustes, haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} junto al grupo de ejecutores que te gustaría configurar y luego en **Editar el nombre y acceso a la [organización|repositorio]**. ![Administrar permisos del repositorio](/assets/images/help/settings/actions-runner-manage-permissions.png) 1. Modifica tus opciones de política o cambia el nombre del grupo ejecutor. + {% ifversion not ghae %} {% warning %} **Advertencia** @@ -10,3 +11,4 @@ Para obtener más información, consulta "[Acerca de los ejecutores autoalojados](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)." {% endwarning %} + {% endif %} diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-configure.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-configure.md index 72fb7a3154..d28a33586e 100644 --- a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-configure.md +++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-configure.md @@ -1,4 +1,4 @@ -1. Select the operating system image and architecture of your self-hosted runner machine. +1. La imagen y arquitectura de tu sistema operativo para tu máquina del ejecutor auto-hospedado. 1. Verás instrucciones que te mostrarán cómo descargar la aplicación del ejecutor e instalarla en tu máquina de ejecutor autoalojado. Abre un shell en tu máquina de ejecutor autoalojado y ejecuta cada comando del shell en el orden que se muestra. diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-create-group.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-create-group.md index 1b1cc6d034..f67e70e5d7 100644 --- a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-create-group.md +++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-create-group.md @@ -1 +1 @@ -1. Click **Create group** to create the group and apply the policy. \ No newline at end of file +1. Haz clic en **Crear grupo** para crear el grupo y aplicar la política. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md index 3cff2724fc..51d2af3e4f 100644 --- a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md +++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md @@ -1,10 +1,10 @@ -1. Navigate to where your self-hosted runner groups are located: +1. Navega a donde se ubiquen tus grupos de ejecutores auto-hospedados: * **En un repositorio organizacional**: navega a la página principal y da clic en {% octicon "gear" aria-label="The Settings gear" %} **Configuración**. * {% ifversion fpt %}**Si se utiliza una cuenta empresarial**: navega a tu cuenta visitando `https://github.com/enterprises/ENTERPRISE-NAME`, remplazando la parte de `ENTERPRISE-NAME` con tu nombre de cuenta empresarial.{% elsif ghes or ghae %}**Si utilizas un ejecutor a nivel empresarial**: 1. En la esquina superior derecha de cualquier página, da clic en {% octicon "rocket" aria-label="The rocket ship" %}. 1. En la barra lateral izquierda, da clic en **Resumen empresarial**. 1. {% endif %} En la barra lateral de empresa, {% octicon "law" aria-label="The law icon" %} **Políticas**. -1. Navigate to the "Runner groups" settings: - * **In an organization or repository**: Click **Actions** in the left sidebar{% ifversion fpt %}, then click **Runner groups** below it{% endif %}. - * {% ifversion fpt %}**If using an enterprise account**:{% elsif ghes or ghae %}**If using an enterprise-level runner**:{% endif %} Click **Actions** under "{% octicon "law" aria-label="The law icon" %} Policies"{% ifversion fpt %}, then click the **Runners groups** tab{% endif %}. +1. Navega a los ajustes de los "Grupos de ejecutores": + * **En un repositorio de organización**: Haz clic en **Acciones** en la barra lateral izquierda{% ifversion fpt %} y luego en **Grupos de ejecutores** debajo{% endif %}. + * {% ifversion fpt %}**Si estás utilizand una cuenta empresarial**:{% elsif ghes or ghae %}**Si estás utilizando un ejecutor a nivel empresarial**:{% endif %} Haz clic en **Acciones** debajo de "{% octicon "law" aria-label="The law icon" %} Políticas"{% ifversion fpt %}, y luego en la pestaña de **Grupos de Ejecutores** {% endif %}. diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-labels-runs-on.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-labels-runs-on.md index b7a65f0d5e..70f1ad4354 100644 --- a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-labels-runs-on.md +++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-labels-runs-on.md @@ -1,3 +1,3 @@ Para especificar un ejecutor auto-hospedado para tu trabajo, configura `runs-on` en tu archivo de flujo de trabajo con las etiquetas de dicho ejecutor. -All self-hosted runners have the `self-hosted` label. Using only this label will select any self-hosted runner. To select runners that meet certain criteria, such as operating system or architecture, provide an array of labels that begins with `self-hosted` (this must be listed first) and then includes additional labels as needed. +Todos los ejecutores auto-hospedados tienen la etiqueta `self-hosted`. El utilizar únicamente esta etiqueta seleccionará cualquier ejecutor auto-hospedado. Para seleccionar los ejecutores que cumplen con ciertos criterios, tales como el sistema operativo o arquitectura, proporciona un arreglo de etiquetas que comience con `self-hosted` (este se debe listar primero) y que luego incluya etiquetas adicionales conforme lo requieras. diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-list.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-list.md index 45dd2ebde6..d4357e3258 100644 --- a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-list.md +++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-list.md @@ -1 +1 @@ - 1. Ubica la lista de ejecutores debajo de {% ifversion fpt %}"Ejecutores"{% else %}"Ejecutores auto-hospedados"{% endif %}. + 1. Ubica la lista de ejecutores debajo de {% ifversion fpt or ghes > 3.1 or ghae-next %}"Ejecutores"{% else %}"Ejecutores auto-hospedados"{% endif %}. diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md index 50a0850aa1..507513d81f 100644 --- a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md +++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md @@ -6,5 +6,5 @@ 1. En la barra lateral izquierda, da clic en **Resumen empresarial**. 1. {% endif %} En la barra lateral de empresa, {% octicon "law" aria-label="The law icon" %} **Políticas**. 1. Navega a los ajustes de {% data variables.product.prodname_actions %}: - * **En una organización o repositorio**: Haz clic en **Acciones** en la barra lateral izquierda{% ifversion fpt %} y luego en **Ejecutores**{% endif %}. - * {% ifversion fpt %}**Si estás utilizand una cuenta empresarial**:{% elsif ghes or ghae %}**Si estás utilizando un ejecutor a nivel empresarial**:{% endif %} Haz clic en **Acciones** debajo de "{% octicon "law" aria-label="The law icon" %} Políticas"{% ifversion fpt %}, y luego en la pestaña de **Ejecutores** {% endif %}. + * **En una organización o repositorio**: Haz clic en **Acciones** en la barra lateral izquierda{% ifversion fpt or ghes > 3.1 or ghae-next %} y luego en **Ejecutores**{% endif %}. + * {% ifversion fpt %}**Si estás utilizand una cuenta empresarial**:{% elsif ghes or ghae %}**Si estás utilizando un ejecutor a nivel empresarial**:{% endif %} Haz clic en **Acciones** debajo de "{% octicon "law" aria-label="The law icon" %} Políticas"{% ifversion fpt or ghes > 3.1 or ghae-next %}, y luego en la pestaña de **Ejecutores** {% endif %}. diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-removing-a-runner-updated.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-removing-a-runner-updated.md index d49e3df8e7..996a416a39 100644 --- a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-removing-a-runner-updated.md +++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-removing-a-runner-updated.md @@ -1,4 +1,4 @@ -1. Click **Remove**. +1. Haz clic en **Eliminar**. 1. Verás las instrucciones para eliminar el ejecutor auto-hospedado. Completa cualquiera de los siguientes pasos para eliminar el ejecutor, dependiendo de si aún se puede acceder a él: * **Si tienes acceso a la máquina del ejecutor:** Sigue las instrucciones en la pantalla para que el sistema operativo de tu máquina ejecute el comando de eliminación. Las instrucciones incluyen la URL solicitada y un token de tiempo limitado generado automáticamente. @@ -9,4 +9,4 @@ * Elimina cualquier archivo de configuración de la aplicación del ejecutor autoalojado en la máquina. * Elimina todos los servicios configurados si no se ejecuta en modo interactivo. - * **If you don't have access to the machine:** Click **Force remove this runner** to force {% data variables.product.product_name %} to remove the runner. + * **Si no tienes acceso a la máquina:** Da clic en **Forzar la eliminación de este ejecutor** para forzar a {% data variables.product.product_name %} a que remueva el ejecutor. diff --git a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md index dc710ad82c..38b03f7625 100644 --- a/translations/es-ES/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md +++ b/translations/es-ES/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md @@ -1,4 +1,4 @@ -1. Debajo de {% ifversion fpt %}"Ejecutores"{% else %}"Ejecutores auto-hospedados"{% endif %}, ubica el ejecutor en la lista. Si tu ejecutor está en un grupo, da clic en {% octicon "chevron-down" aria-label="The downwards chevron" %} para expandir la lista. +1. Debajo de {% ifversion fpt or ghes > 3.1 or ghae-next %}"Ejecutores"{% else %}"Ejecutores auto-hospedados"{% endif %}, ubica el ejecutor en la lista. Si tu ejecutor está en un grupo, da clic en {% octicon "chevron-down" aria-label="The downwards chevron" %} para expandir la lista. 1. Da clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} junto al ejecutor que quieres eliminar, y luego da clic en **Eliminar**. ![Eliminar una configuración de ejecutor autoalojado](/assets/images/help/settings/actions-runner-remove.png) diff --git a/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runner-groups-selection.md b/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runner-groups-selection.md index b60a52acbe..07dfd3cbef 100644 --- a/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runner-groups-selection.md +++ b/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runner-groups-selection.md @@ -1 +1 @@ -1. In the list of groups, click the runner group you'd like to configure. +1. En la lista de grupos, haz clic en el grupo de ejecutores que te gustaría configurar. diff --git a/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md b/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md index 7d85a71f85..1865940c35 100644 --- a/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md +++ b/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md @@ -1,2 +1,2 @@ -1. En la barra lateral izquierda, da clic en **Acciones**. -1. In the left sidebar, under "Actions", click **Runner groups**. +1. En la barra lateral izquierda, haz clic en **Acciones**.{% ifversion fpt or ghes > 3.1 or ghae-next %} +1. En la barra lateral izquierda, debajo de "Acciones"; haz clic en **Grupos ejecutores**.{% endif %} diff --git a/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runner-selection.md b/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runner-selection.md index c4985fa1c5..476c6177e6 100644 --- a/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runner-selection.md +++ b/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runner-selection.md @@ -1 +1 @@ -1. In the list of runners, click the runner you'd like to configure. +1. En la lista de ejecutores, haz clic en el que te gustaría configurar. diff --git a/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runners-updated.md b/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runners-updated.md index b3818637db..84fdafe30e 100644 --- a/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runners-updated.md +++ b/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runners-updated.md @@ -1 +1 @@ -1. In the left sidebar, under "Actions", click **Runners**. \ No newline at end of file +1. En la barra lateral izquierda, debajo de "Acciones", haz clic en **Ejecutores**. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runners.md b/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runners.md index 51e68722cf..c5c78afaff 100644 --- a/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runners.md +++ b/translations/es-ES/data/reusables/github-actions/settings-sidebar-actions-runners.md @@ -1 +1 @@ -1. En la barra lateral izquierda, haz clic en **Acciones**{% ifversion fpt %} y luego haz clic en **Ejecutores**{% endif %}. +1. En la barra lateral izquierda, haz clic en **Acciones**{% ifversion fpt or ghes > 3.1 or ghae-next %} y luego haz clic en **Ejecutores**{% endif %}. diff --git a/translations/es-ES/data/reusables/github-actions/supported-github-runners.md b/translations/es-ES/data/reusables/github-actions/supported-github-runners.md index 79771388b1..283cabe215 100644 --- a/translations/es-ES/data/reusables/github-actions/supported-github-runners.md +++ b/translations/es-ES/data/reusables/github-actions/supported-github-runners.md @@ -15,7 +15,7 @@ Windows Server 2022[beta] windows-2022 -The windows-latest label currently uses the Windows Server 2019 runner image. +La etiqueta de windows-latest actualmente utiliza la imagen de ejecutor de Windows Server 2019. @@ -60,24 +60,13 @@ Ubuntu 18.04 -Ubuntu 16.04[deprecated] - - -ubuntu-16.04 - - -Deprecated and limited to existing customers only. Migrate to Ubuntu 20.04. For more information, see the blog post. - - - - macOS Big Sur 11 macos-11 -The macos-latest label currently uses the macOS 10.15 runner image. +La etiqueta de macos-latest actualmente utiliza la imagen de ejecutor de macOS 10.15. @@ -95,6 +84,6 @@ macOS Catalina 10.15 {% warning %} -Note: Beta Images are provided "as-is", "with all faults" and "as available" and are excluded from the service level agreement and warranty. Beta Images may not be covered by customer support. +Nota: Las imágenes beta se proporcionan "tal cual", "con todas las fallas" y "tal como están disponibles" y se excluyen del acuerdo de nivel de servicio y de la garantía. El soporte al cliente podría no cubrir las imágenes beta. {% endwarning %} diff --git a/translations/es-ES/data/reusables/github-connect/access-dotcom-and-enterprise.md b/translations/es-ES/data/reusables/github-connect/access-dotcom-and-enterprise.md index 75c6726d7c..86f4b1fa32 100644 --- a/translations/es-ES/data/reusables/github-connect/access-dotcom-and-enterprise.md +++ b/translations/es-ES/data/reusables/github-connect/access-dotcom-and-enterprise.md @@ -1 +1 @@ -1. Iniciar sesión en {% data variables.product.product_location_enterprise %} y {% data variables.product.prodname_dotcom_the_website %}. +1. Inicia sesión en {% ifversion ghes %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_ghe_managed %}{% endif %} y {% data variables.product.prodname_dotcom_the_website %}. diff --git a/translations/es-ES/data/reusables/github-connect/access-profile-settings.md b/translations/es-ES/data/reusables/github-connect/access-profile-settings.md index c601a6309d..42b6e9fc8e 100644 --- a/translations/es-ES/data/reusables/github-connect/access-profile-settings.md +++ b/translations/es-ES/data/reusables/github-connect/access-profile-settings.md @@ -1 +1 @@ -1. En {% data variables.product.product_location_enterprise %}, en el ángulo superior derecho de cualquier página, haz clic en tu foto de perfil y luego haz clic en **Settings** (Parámetros). ![Icono Settings (Parámetros) en la barra de usuario](/assets/images/help/settings/userbar-account-settings.png) +1. En {% ifversion ghes %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_ghe_managed %}{% endif %}, en la esquina superior derecha de cualquier página, haz clic en tu foto de perfil y luego en **Ajustes**. ![Icono Settings (Parámetros) en la barra de usuario](/assets/images/help/settings/userbar-account-settings.png) diff --git a/translations/es-ES/data/reusables/github-connect/authorize-connection.md b/translations/es-ES/data/reusables/github-connect/authorize-connection.md index 220d5c6ec7..1dad67fb83 100644 --- a/translations/es-ES/data/reusables/github-connect/authorize-connection.md +++ b/translations/es-ES/data/reusables/github-connect/authorize-connection.md @@ -1 +1,7 @@ -1. Revisa los recursos a los que {% data variables.product.prodname_ghe_server %} accederá desde tu cuenta de {% data variables.product.prodname_dotcom_the_website %}, posteriormente, da clic en **Autorizar**. ![Autorizar conexión entre GitHub Enterprise Server y GitHub.com](/assets/images/help/settings/authorize-ghe-to-connect-to-dotcom.png) +1. Revisa los recursos a los que +accederá {% data variables.product.product_name %} desde tu cuenta de {% data variables.product.prodname_dotcom_the_website %} y luego haz clic en **Autorizar**. +{% ifversion ghes %} + ![Autoriza la conexión entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_dotcom_the_website %}](/assets/images/help/settings/authorize-ghe-to-connect-to-dotcom.png) +{% elsif ghae %} + ![Autoriza la conexión entre {% data variables.product.prodname_ghe_managed %} y {% data variables.product.prodname_dotcom_the_website %}](/assets/images/enterprise/github-ae/settings/authorize-ghae-to-connect-to-dotcom.png) +{% endif %} diff --git a/translations/es-ES/data/reusables/github-connect/beta.md b/translations/es-ES/data/reusables/github-connect/beta.md new file mode 100644 index 0000000000..38de9506c0 --- /dev/null +++ b/translations/es-ES/data/reusables/github-connect/beta.md @@ -0,0 +1,7 @@ +{% ifversion ghae-next %} +{% note %} + +**Nota:** {% data variables.product.prodname_github_connect %} para {% data variables.product.product_name %} se encuentra actualmente en beta y está sujeto a cambios. + +{% endnote %} +{% endif %} diff --git a/translations/es-ES/data/reusables/github-connect/connect-dotcom-and-enterprise.md b/translations/es-ES/data/reusables/github-connect/connect-dotcom-and-enterprise.md index c375744a01..caf20d730b 100644 --- a/translations/es-ES/data/reusables/github-connect/connect-dotcom-and-enterprise.md +++ b/translations/es-ES/data/reusables/github-connect/connect-dotcom-and-enterprise.md @@ -1 +1,6 @@ -1. Da clic en **Conectar con {% data variables.product.prodname_dotcom_the_website %}**. ![Conectarse con GitHub.com desde la configuración de GitHub Enterprise Server](/assets/images/help/settings/github.com_end_user_connection.png) +1. Da clic en **Conectar con {% data variables.product.prodname_dotcom_the_website %}**. +{% ifversion ghes %} + ![Conectarse con GitHub.com desde la configuración de GitHub Enterprise Server](/assets/images/help/settings/github.com_end_user_connection.png) +{% else %} + ![Conéctate a GitHub.com desde los ajustes de GitHub AE](/assets/images/enterprise/github-ae/settings/github.com-end-user-connection.png) +{% endif %} diff --git a/translations/es-ES/data/reusables/github-connect/send-contribution-counts-to-githubcom.md b/translations/es-ES/data/reusables/github-connect/send-contribution-counts-to-githubcom.md new file mode 100644 index 0000000000..18a044ccbb --- /dev/null +++ b/translations/es-ES/data/reusables/github-connect/send-contribution-counts-to-githubcom.md @@ -0,0 +1 @@ +1. Debajo de "Contributions" (Contribuciones), selecciona **Send my contribution counts to {% data variables.product.prodname_dotcom_the_website %}** (Enviar mi recuento de contribuciones a {% data variables.product.prodname_dotcom_the_website %}), luego haz clic en **Update contributions** (Actualizar contribuciones). ![Casilla para enviar contribuciones y botón para actualizar contribuciones](/assets/images/help/settings/send-and-update-contributions.png) diff --git a/translations/es-ES/data/reusables/github-connect/sync-frequency.md b/translations/es-ES/data/reusables/github-connect/sync-frequency.md index 93299f0265..0057d0fdb2 100644 --- a/translations/es-ES/data/reusables/github-connect/sync-frequency.md +++ b/translations/es-ES/data/reusables/github-connect/sync-frequency.md @@ -1 +1 @@ -{% data variables.product.prodname_ghe_server %} envía actualizaciones cada hora. +{% data variables.product.product_name %} envía actualizaciones cada hora. diff --git a/translations/es-ES/data/reusables/identity-and-permissions/team-sync-usage-limits.md b/translations/es-ES/data/reusables/identity-and-permissions/team-sync-usage-limits.md index 94ba17c8e4..9117c2f608 100644 --- a/translations/es-ES/data/reusables/identity-and-permissions/team-sync-usage-limits.md +++ b/translations/es-ES/data/reusables/identity-and-permissions/team-sync-usage-limits.md @@ -1,8 +1,8 @@ ### Límites de uso -There are usage limits for the team synchonization feature. Exceeding these limits will lead to a degredation in performance and may cause synchronization failures. +Hay límites de uso para la característica de sincronización de equipos. El exceder estos límites ocasionará una degradación del rendimiento y podrá causar fallas de sincronización. -- Maximum number of members in a GitHub team: 5,000 -- Maximum number of members in a GitHub organization: 10,000 -- Maximum number of teams in a GitHub organization: 1,500 +- Cantidad máxima de miembros en un equipo de GitHub: 5,000 +- Cantidad máxima de miembros en una organización de GitHub: 10,000 +- Cantidad máxima de equipos en una organización de GitHub: 1,500 diff --git a/translations/es-ES/data/reusables/notifications-v2/custom-notification-types.md b/translations/es-ES/data/reusables/notifications-v2/custom-notification-types.md index 080ae42ef4..f03a29842c 100644 --- a/translations/es-ES/data/reusables/notifications-v2/custom-notification-types.md +++ b/translations/es-ES/data/reusables/notifications-v2/custom-notification-types.md @@ -1,2 +1,2 @@ {%- ifversion fpt or ghes > 3.1 or ghae-issue-4910 %}propuestas, solicitudes de cambios, lanzamientos, alertas de seguridad o debates{% endif %} -{%- ifversion ghes = 3.1 or ghae-next %}propuestas, solicitudes de cambio, lanzamientos, o debates{% endif %} +{%- ifversion ghes = 3.1 %}propuestas, solicitudes de cambio, lanzamientos, o debates{% endif %} diff --git a/translations/es-ES/data/reusables/notifications/email-restrictions-verification.md b/translations/es-ES/data/reusables/notifications/email-restrictions-verification.md index b0cfa2e33e..1a54571c5a 100644 --- a/translations/es-ES/data/reusables/notifications/email-restrictions-verification.md +++ b/translations/es-ES/data/reusables/notifications/email-restrictions-verification.md @@ -1 +1 @@ -Después de que habilitas las restricciones por correo electrónico, los miembros pueden recibir notificacions por correo electrónico en direcciones de correo electrónico verificadas con dominios que hayas verificado o aprobado. {% ifversion fpt %}For more information, see "[Verifying your email address](/github/getting-started-with-github/verifying-your-email-address)."{% endif %} +Después de que habilitas las restricciones por correo electrónico, los miembros pueden recibir notificacions por correo electrónico en direcciones de correo electrónico verificadas con dominios que hayas verificado o aprobado. {% ifversion fpt %}Para obtener más información, consulta la sección "[Verificar tu dirección de correo electrónico](/github/getting-started-with-github/verifying-your-email-address)".{% endif %} diff --git a/translations/es-ES/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization2.md b/translations/es-ES/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization2.md index 6327152310..432e559cfd 100644 --- a/translations/es-ES/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization2.md +++ b/translations/es-ES/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization2.md @@ -1 +1 @@ -You can choose the delivery method for notifications, as well as the frequency at which the notifications are sent to you. \ No newline at end of file +Puedes elegir el método de entrega de las notificaciones, así como la frecuencia en las que se te envían. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/notifications/vulnerable-dependency-notification-enable.md b/translations/es-ES/data/reusables/notifications/vulnerable-dependency-notification-enable.md index 295c5d9a23..68e724b7bf 100644 --- a/translations/es-ES/data/reusables/notifications/vulnerable-dependency-notification-enable.md +++ b/translations/es-ES/data/reusables/notifications/vulnerable-dependency-notification-enable.md @@ -1,3 +1,3 @@ {% ifversion fpt or ghes > 3.1 %} -To receive notifications about {% data variables.product.prodname_dependabot_alerts %} on repositories, you need to watch these repositories, and subscribe to receive "All Activity" notifications or configure custom settings to include "Security alerts." For more information, see "[Configuring your watch settings for an individual repository](/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)." +Para recibir notificaciones sobre las {% data variables.product.prodname_dependabot_alerts %} en los repositorios, necesitas observar dichos repositorios y suscribirte para recibir notificaciones de "Toda la Actividad" o configurar los ajustes personalizados para que incluyan las "Alertas de seguridad". Para obtener más información, consulta la sección "[Configurar tus ajustes de observación para repositorios individuales](/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)". {% endif %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/organizations/about-organizations.md b/translations/es-ES/data/reusables/organizations/about-organizations.md index eb7509598f..f1c10ac8b4 100644 --- a/translations/es-ES/data/reusables/organizations/about-organizations.md +++ b/translations/es-ES/data/reusables/organizations/about-organizations.md @@ -1 +1 @@ -Your team can collaborate on {% data variables.product.product_name %} by using an organization account. Each person that uses {% data variables.product.prodname_dotcom %} signs into a user account. Multiple user accounts can collaborate on shared projects by joining the same organization account, which owns the repositories. A subset of these user accounts can be given the role of organization owner, which allows those people to granularly manage access to the organization's resources using sophisticated security and administrative features. +Tu equipo puede colaborar en {% data variables.product.product_name %} utilizando una cuenta de organización. Cada persona que utiliza {% data variables.product.prodname_dotcom %} se debe firmar con una cuenta de usuario. Las cuentas de usuario múltiples pueden colaborar en proyectos compartidos si se unen a la misma cuenta de organización que es propietaria de los repositorios. Un subconjunto de estas cuentas de usuario puede obtener el rol de propietario de la organización, el cual permite a estas personas administrar el acceso a los recursos de la organización de forma granular, utilizando características administrativas y de seguridad sofisticadas. diff --git a/translations/es-ES/data/reusables/organizations/github-apps-settings-sidebar.md b/translations/es-ES/data/reusables/organizations/github-apps-settings-sidebar.md index 677d0b37c5..2d7941f4d9 100644 --- a/translations/es-ES/data/reusables/organizations/github-apps-settings-sidebar.md +++ b/translations/es-ES/data/reusables/organizations/github-apps-settings-sidebar.md @@ -1 +1 @@ -1. En la barra lateral izquierda, haz clic en **{% data variables.product.prodname_github_apps %}**. ![{% data variables.product.prodname_github_apps %} settings](/assets/images/help/organizations/github-apps-settings-sidebar.png) +1. En la barra lateral izquierda, haz clic en **{% data variables.product.prodname_github_apps %}**. ![Ajustes de las {% data variables.product.prodname_github_apps %}](/assets/images/help/organizations/github-apps-settings-sidebar.png) diff --git a/translations/es-ES/data/reusables/organizations/new_team.md b/translations/es-ES/data/reusables/organizations/new_team.md index 7ab2dd8c47..ee80cc87a8 100644 --- a/translations/es-ES/data/reusables/organizations/new_team.md +++ b/translations/es-ES/data/reusables/organizations/new_team.md @@ -1,5 +1,5 @@ 1. Debajo del nombre de tu organización, da clic en -{% octicon "people" aria-label="The people icon" %} **Teams**. +{% octicon "people" aria-label="The people icon" %} **Equipos**. {% ifversion fpt or ghes > 3.2 %} ![Pestaña de equipos](/assets/images/help/organizations/organization-teams-tab-with-overview.png) {% else %} diff --git a/translations/es-ES/data/reusables/organizations/org-invite-scim.md b/translations/es-ES/data/reusables/organizations/org-invite-scim.md index d2290e8e2b..dfb78b6aaa 100644 --- a/translations/es-ES/data/reusables/organizations/org-invite-scim.md +++ b/translations/es-ES/data/reusables/organizations/org-invite-scim.md @@ -1 +1 @@ -Las invitaciones pendientes caducarán después de 7 días. Esto restablecerá cualquier licencia sin reclamar. If an invitation is generated by System for Cross-domain Identity Management (SCIM), the invitation will not expire. +Las invitaciones pendientes caducarán después de 7 días. Esto restablecerá cualquier licencia sin reclamar. Si el Sistema para la Administración de Identidades de Dominio Cruzado (SCIM) genera una invitación, esta no vencerá. diff --git a/translations/es-ES/data/reusables/organizations/owners-team.md b/translations/es-ES/data/reusables/organizations/owners-team.md index 8fc412dc57..cca42c27c9 100644 --- a/translations/es-ES/data/reusables/organizations/owners-team.md +++ b/translations/es-ES/data/reusables/organizations/owners-team.md @@ -1,5 +1,5 @@ 1. Debajo del nombre de tu organización, da clic en -{% octicon "people" aria-label="The people icon" %} **Teams**. +{% octicon "people" aria-label="The people icon" %} **Equipos**. {% ifversion fpt or ghes > 3.2 %} ![Pestaña de equipos](/assets/images/help/organizations/organization-teams-tab-with-overview.png) {% else %} diff --git a/translations/es-ES/data/reusables/organizations/restrict-email-notifications.md b/translations/es-ES/data/reusables/organizations/restrict-email-notifications.md index 9be6b1c3bc..e6d0c8a3fb 100644 --- a/translations/es-ES/data/reusables/organizations/restrict-email-notifications.md +++ b/translations/es-ES/data/reusables/organizations/restrict-email-notifications.md @@ -1 +1 @@ -1. Under "Notification preferences", select **Restrict email notifications to only approved or verified domains**. ![Casilla para restringir las notificaciones por correo electrónico para los correos electrónicos de dominio verificado](/assets/images/help/organizations/restrict-email-notifications-to-domain.png) +1. Debajo de "Preferencias de notificación", selecciona **Restringir las notificaciones por correo electrónico únicamente a los dominios verificados o aprobados**. ![Casilla para restringir las notificaciones por correo electrónico para los correos electrónicos de dominio verificado](/assets/images/help/organizations/restrict-email-notifications-to-domain.png) diff --git a/translations/es-ES/data/reusables/organizations/specific_team.md b/translations/es-ES/data/reusables/organizations/specific_team.md index a9692b6f63..91eb29b56f 100644 --- a/translations/es-ES/data/reusables/organizations/specific_team.md +++ b/translations/es-ES/data/reusables/organizations/specific_team.md @@ -1,5 +1,5 @@ 1. Debajo del nombre de tu organización, da clic en -{% octicon "people" aria-label="The people icon" %} **Teams**. +{% octicon "people" aria-label="The people icon" %} **Equipos**. {% ifversion fpt or ghes > 3.2 %} ![Pestaña de equipos](/assets/images/help/organizations/organization-teams-tab-with-overview.png) {% else %} diff --git a/translations/es-ES/data/reusables/organizations/teams.md b/translations/es-ES/data/reusables/organizations/teams.md index 5275f9cb6d..438a2c04f8 100644 --- a/translations/es-ES/data/reusables/organizations/teams.md +++ b/translations/es-ES/data/reusables/organizations/teams.md @@ -1,5 +1,5 @@ 1. Debajo del nombre de tu organización, da clic en -{% octicon "people" aria-label="The people icon" %} **Teams**. +{% octicon "people" aria-label="The people icon" %} **Equipos**. {% ifversion fpt or ghes > 3.2 %} ![Pestaña de equipos en la página de la organización](/assets/images/help/organizations/organization-teams-tab-with-overview.png) {% else %} diff --git a/translations/es-ES/data/reusables/package_registry/authenticate-packages.md b/translations/es-ES/data/reusables/package_registry/authenticate-packages.md index 64b208d748..68a4dbbc1c 100644 --- a/translations/es-ES/data/reusables/package_registry/authenticate-packages.md +++ b/translations/es-ES/data/reusables/package_registry/authenticate-packages.md @@ -1,9 +1,7 @@ -You need an access token to publish, install, and delete packages. You can use a personal access token to authenticate with your username directly to {% data variables.product.prodname_registry %} or the {% data variables.product.prodname_dotcom %} API. When you create a personal access token, you can assign the token different scopes depending on your needs. +Necesitas de un token de acceso para publicar, instalar, y borrar paquetes en {{ site.data.variables.product.prodname_registry }}. -{% if currentVersion == "free-pro-team@latest" %} -To authenticate using a {% data variables.product.prodname_actions %} workflow: -- For package registries (`PACKAGE-REGISTRY.pkg.github.com`), you can use a `GITHUB_TOKEN`. -- For the container registry (`ghcr.io/OWNER/IMAGE-NAME`), you must use a personal access token. -{% else %} -To authenticate to {% data variables.product.prodname_registry %} using a {% data variables.product.prodname_actions %} workflow, you must use `GITHUB_TOKEN`. -{% endif %} +Puees utilizar un token de acceso personal (PAT) para autenticarte en el {% data variables.product.prodname_registry %} o en la API de {% data variables.product.prodname_dotcom %}. Cuando creas un token de acceso personal, puedes asignar al token diferentes ámbitos en función de tus necesidades. Para obtener más información sobre los alcances relacionados con los paquetes para un PAT, consulta la sección "[Acerca de los permisos para los Paquetes de GitHub](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)". + +Para autenticarte en un registro del {% data variables.product.prodname_registry %} dentro de un flujo de trabajo de {% data variables.product.prodname_actions %}, puedes utilizar: +- `GITHUB_TOKEN` para publicar los paquetes asociados con el repositorio del flujo de trabajo. +- un PAT para instalar los paquetes asociados con otros repositorios privados (a los cuales no puede acceder el `GITHUB_TOKEN`). diff --git a/translations/es-ES/data/reusables/package_registry/packages-spending-limit-brief.md b/translations/es-ES/data/reusables/package_registry/packages-spending-limit-brief.md index 7d222c521c..1a8f0411f4 100644 --- a/translations/es-ES/data/reusables/package_registry/packages-spending-limit-brief.md +++ b/translations/es-ES/data/reusables/package_registry/packages-spending-limit-brief.md @@ -1 +1 @@ -If you are a monthly-billed customer, your account will have a default spending limit of 0 US dollars (USD), which prevents additional usage of storage or data transfer after you reach the included amounts. Si pagas tu cuenta por factura, ésta tendrá un límite de gastos ilimitado predeterminadamente. +Si eres un cliente que factura mensualmente, tu cuenta tendrá un límite de gastos predeterminado de 0 dólares Estadounidenses (USD), lo cual previene el uso adicional de almacenamiento o transferencia de datos después de que alcanzas las cantidades que se incluyen. Si pagas tu cuenta por factura, ésta tendrá un límite de gastos ilimitado predeterminadamente. diff --git a/translations/es-ES/data/reusables/package_registry/packages-spending-limit-detailed.md b/translations/es-ES/data/reusables/package_registry/packages-spending-limit-detailed.md index 28dc99ea9a..d47c531967 100644 --- a/translations/es-ES/data/reusables/package_registry/packages-spending-limit-detailed.md +++ b/translations/es-ES/data/reusables/package_registry/packages-spending-limit-detailed.md @@ -1,3 +1,3 @@ {% data reusables.package_registry.packages-spending-limit-brief %} -If you have an unlimited spending limit or a spending limit set higher than $0 USD, you will be billed for any additional storage or data transfer, also called overages, up to your spending limit. No podrán aplicarse los cupones que tenga tu cuenta para los excedentes de {% data variables.product.prodname_registry %}. +Si tu limite de gastos es ilimitado o si lo configuraste en más de $0 USD, se te facturará por cualquier almacenamiento o transferencia de datos adicional, lo cual también se conoce como excedente, hasta que se llegue a tu límite de gastos. No podrán aplicarse los cupones que tenga tu cuenta para los excedentes de {% data variables.product.prodname_registry %}. diff --git a/translations/es-ES/data/reusables/pages/about-private-publishing.md b/translations/es-ES/data/reusables/pages/about-private-publishing.md index e83f86ecda..9f9d6511de 100644 --- a/translations/es-ES/data/reusables/pages/about-private-publishing.md +++ b/translations/es-ES/data/reusables/pages/about-private-publishing.md @@ -1 +1 @@ -Si tu sitio de proyecto se publica desde un repositorio privado o interno que pertenezca a una organización que utiliza {% data variables.product.prodname_ghe_cloud %}, puedes administrar el control de accesos para el sitio. +Si tu sitio de proyecto se publica desde un repositorio privado o interno que pertenezca a una organización que utiliza {% data variables.product.prodname_ghe_cloud %}, puedes administrar el control de accesos para el sitio. En una {% data variables.product.prodname_emu_enterprise %}, todos los sitios de {% data variables.product.prodname_pages %} se publican en privado. diff --git a/translations/es-ES/data/reusables/pull_requests/large-search-workaround.md b/translations/es-ES/data/reusables/pull_requests/large-search-workaround.md index c0e68b6b9b..7ff4701d1f 100644 --- a/translations/es-ES/data/reusables/pull_requests/large-search-workaround.md +++ b/translations/es-ES/data/reusables/pull_requests/large-search-workaround.md @@ -1 +1 @@ -If you have access to pull requests in more than 10,000 repositories, you will need to limit your search to a specific organization, user account, or repository to see results. \ No newline at end of file +Si tienes acceso a las solicitudes de cambio en más de 10,000 repositorios, necesitarás limitar tu búsqueda a una organización, cuenta de usuario o repositorio específicos para poder ver los resultados. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/repositories/auto-gen-release-public-beta.md b/translations/es-ES/data/reusables/repositories/auto-gen-release-public-beta.md new file mode 100644 index 0000000000..fc9b843d21 --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/auto-gen-release-public-beta.md @@ -0,0 +1 @@ +Las notas de lanzamiento generadas automáticamente se encuentran actualmente en beta público y están sujetas a cambios. diff --git a/translations/es-ES/data/reusables/repositories/disabling-markdown-rendering.md b/translations/es-ES/data/reusables/repositories/disabling-markdown-rendering.md new file mode 100644 index 0000000000..f7219ace5f --- /dev/null +++ b/translations/es-ES/data/reusables/repositories/disabling-markdown-rendering.md @@ -0,0 +1,5 @@ +Cuando ves un archivo de lenguaje de marcado, puedes hacer clic en el {% octicon "code" aria-label="The code icon" %} en la parte superior de este para inhabilitar la representación de lenguaje de marcado y ver en su lugar el código fuente del archivo. + +![Mostrar el lenguaje de marcado como código fuente](/assets/images/help/writing/display-markdown-as-source.png) + +El inhabilitar la interpretación de lenguaje de marcado te permite utilizar las características de vista de código fuente, tales como el enlazado de líneas, el cual no es posible cuando se está viendo un archivo interpretado en lenguaje de marcado. diff --git a/translations/es-ES/data/reusables/repositories/request-security-advisory-cve-id.md b/translations/es-ES/data/reusables/repositories/request-security-advisory-cve-id.md index 8774bf8921..9cbe0a4ca5 100644 --- a/translations/es-ES/data/reusables/repositories/request-security-advisory-cve-id.md +++ b/translations/es-ES/data/reusables/repositories/request-security-advisory-cve-id.md @@ -1,5 +1,3 @@ -Si aún no tienes un número de identificación CVE para la vulnerabilidad de seguridad en tu proyecto, puedes solicitar un número de identificación de CVE de {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_dotcom %} habitualmente revisa la solicitud dentro de las primeras 72 horas de su recepción. El solicitar un número de identificación de CVE no convierte tu asesoría de seguridad en pública. Si tu asesoría de seguridad es elegible para un CVE, {% data variables.product.prodname_dotcom %} rservará un número de identificación de CVE para ésta. Después publicaremos los detalles del CVE después de que publiques la asesoría de seguridad. +Si quieres un número de identificación CVE para la vulnerabilidad de seguridad en tu proyecto y aún no tienes uno, puedes solicitarlo de {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_dotcom %} habitualmente revisa la solicitud dentro de las primeras 72 horas de su recepción. El solicitar un número de identificación de CVE no convierte tu asesoría de seguridad en pública. Si tu asesoría de seguridad es elegible para un CVE, {% data variables.product.prodname_dotcom %} reservará un número de identificación de CVE para ésta. Entonces publicaremos los detalles de CVE después de que hayas hecho pública tu asesoría de seguridad. Cualquiera con permisos de administrador en una asesoría de seguridad puede solicitar un número de identificación de CVE. -Si ya tienes un CVE que quieres utilizar, por ejemplo, si utilizas un CNA diferente al de {% data variables.product.prodname_dotcom %}, agrégalo al formato de asesoría de seguridad. Esto podría pasar, por ejemplo, si quiers que la asesoría sea consistente con otras comnicaciones que planees enviar al momento de la publicación. - -Si un formato de asesoría no tiene un CVE, solicitaremos un CVE para ti cuando publiques la asesoría. +Si ya tienes un CVE que quieres utilizar, por ejemplo, si utilizas una Autoridad de Numeración de CVE (CNA) diferente a la de {% data variables.product.prodname_dotcom %}, agrega el CVE al formato de asesoría de seguridad. Esto podría pasar, por ejemplo, si quiers que la asesoría sea consistente con otras comnicaciones que planees enviar al momento de la publicación. {% data variables.product.prodname_dotcom %} no pude asignar un CVE a tu proyecto si se cubre con otro CNA. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/repositories/sidebar-issues.md b/translations/es-ES/data/reusables/repositories/sidebar-issues.md index 48ba4fb5ef..7ea2e0e045 100644 --- a/translations/es-ES/data/reusables/repositories/sidebar-issues.md +++ b/translations/es-ES/data/reusables/repositories/sidebar-issues.md @@ -1,5 +1,5 @@ 2. Debajo del nombre de tu repositorio, da clic en {% octicon "issue-opened" aria-label="The issues icon" %} **Propuestas**. - {% ifversion fpt or ghes > 3.1 or ghae-issue-4483 %} + {% ifversion fpt or ghes > 3.1 or ghae-next %} ![Pestaña de informe de problemas](/assets/images/help/repository/repo-tabs-issues.png){% else %} ![Issues tab](/assets/images/enterprise/3.1/help/repository/repo-tabs-issues.png){% endif %} diff --git a/translations/es-ES/data/reusables/repositories/sidebar-pr.md b/translations/es-ES/data/reusables/repositories/sidebar-pr.md index 274d5619fe..b400f5fd46 100644 --- a/translations/es-ES/data/reusables/repositories/sidebar-pr.md +++ b/translations/es-ES/data/reusables/repositories/sidebar-pr.md @@ -1,5 +1,5 @@ 1. Debajo del nombre de tu repositorio, da clic en {% octicon "git-pull-request" aria-label="The pull request icon" %} **Solicitudes de cambios**. - {% ifversion fpt or ghes > 3.1 or ghae-issue-4483 %} + {% ifversion fpt or ghes > 3.1 or ghae-next %} ![Selección de la pestaña de propuestas y solicitudes de extracción](/assets/images/help/repository/repo-tabs-pull-requests.png){% else %} ![Issues tab](/assets/images/enterprise/3.1/help/repository/repo-tabs-pull-requests.png){% endif %} diff --git a/translations/es-ES/data/reusables/repositories/workflow-notifications.md b/translations/es-ES/data/reusables/repositories/workflow-notifications.md index 86614cc3cd..90a0ca8a82 100644 --- a/translations/es-ES/data/reusables/repositories/workflow-notifications.md +++ b/translations/es-ES/data/reusables/repositories/workflow-notifications.md @@ -1,4 +1,4 @@ -Si habilitas las notificaciones web o por correo electrónico para {% data variables.product.prodname_actions %}, recibirás una notificación cuando alguna ejecución de flujo de trabajo que hayas activado se complete. La notificación incluirá el estado de la ejecución de flujo de trabajo (que incluye ejecuciones exitosas, fallidas, neutrales y canceladas). También puedes elegir recibir una notificación solo cuando falle una ejecución de flujo de trabajo. +Si habilitas las notificaciones web o por correo electrónico para {% data variables.product.prodname_actions %}, recibirás una notificación cuando alguna ejecución de flujo de trabajo que hayas activado se complete. La notificación incluirá el estado de la ejecución de flujo de trabajo (que incluye ejecuciones exitosas, fallidas, neutrales y canceladas). También puedes elegir recibir una notificación solo cuando falle una ejecución de flujo de trabajo. Para obtener más información sobre cómo habilitar o inhabilitar las notificaciones, consulta la sección "[Acerca de las notificaciones](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)". Las notificaciones par alos flujos de trabajo programados se envían al usuario que creó el flujo de trabajo inicialmente. Si un usuario diferente actualiza la sintaxis de cron en el archivo de flujo de trabajo, las notificaciones subsecuentes se enviarán a este usuario en vez de al otro.{% ifversion fpt or ghes > 2.22 %} Si se inhabilita un flujo de trabajo y luego se rehabilita, las notificaciones se enviarán a aquél usuario que haya rehabilitado el flujo de trabajo en vez de al que modificó la sintaxis de cron por última vez.{% endif %} diff --git a/translations/es-ES/data/reusables/saml/about-linked-identities.md b/translations/es-ES/data/reusables/saml/about-linked-identities.md index 9e249437cc..4250358864 100644 --- a/translations/es-ES/data/reusables/saml/about-linked-identities.md +++ b/translations/es-ES/data/reusables/saml/about-linked-identities.md @@ -1,3 +1,3 @@ -Puedes ver la identidad de inicio de sesión único que cualquier miembro tenga vinculada con su cuenta de {% data variables.product.product_name %}. Cuando esté disponible, la entrada incluirá datos de SCIM. Para obtener más información, consulta la sección "[Acerca de SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)". +Puedes ver la identidad de inicio de sesión único que cualquier miembro tenga vinculada con su cuenta de {% data variables.product.product_name %}. Si un miembro vincula la identidad incorrecta a la cuenta de {% data variables.product.product_name %}, podrás revocar dicha identidad para permitir que el miembro lo intente de nuevo. diff --git a/translations/es-ES/data/reusables/saml/about-saml-enterprise-accounts.md b/translations/es-ES/data/reusables/saml/about-saml-enterprise-accounts.md index aebf4268b6..9fc2fdbe6f 100644 --- a/translations/es-ES/data/reusables/saml/about-saml-enterprise-accounts.md +++ b/translations/es-ES/data/reusables/saml/about-saml-enterprise-accounts.md @@ -1 +1 @@ -Los propietarios de empresa pueden habilitar el SSO de SAML y la autenticación centralizada a través de el IdP de SAML para todas las organizaciones que pertenezcan a su cuenta empresarial. After you enable SAML SSO for your enterprise account, SAML SSO is enforced for all organizations owned by your enterprise account. Se les exigirá a todos los miembros que se autentiquen usando SAML SSO para obtener acceso a las organizaciones de las que son miembros, y se les exigirá a los propietarios de empresas que se autentiquen usando SAML SSO cuando accesan a la cuenta de empresa. +Los propietarios de empresa pueden habilitar el SSO de SAML y la autenticación centralizada a través de el IdP de SAML para todas las organizaciones que pertenezcan a su cuenta empresarial. Después de habilitar el SSO de SAML para tu cuenta empresarial, este se requerirá en todas las organizaciones que le pertenezcan a ella. Se les exigirá a todos los miembros que se autentiquen usando SAML SSO para obtener acceso a las organizaciones de las que son miembros, y se les exigirá a los propietarios de empresas que se autentiquen usando SAML SSO cuando accesan a la cuenta de empresa. diff --git a/translations/es-ES/data/reusables/saml/saml-accounts.md b/translations/es-ES/data/reusables/saml/saml-accounts.md index 71ad4fe932..b42e11e893 100644 --- a/translations/es-ES/data/reusables/saml/saml-accounts.md +++ b/translations/es-ES/data/reusables/saml/saml-accounts.md @@ -1 +1 @@ -If you configure SAML SSO, members of your {% data variables.product.prodname_dotcom %} organization will continue to log into their user accounts on {% data variables.product.prodname_dotcom %}. Cuando un miembro accede a recursos dentro de tu organización que utiliza el SSO de SAML, {% data variables.product.prodname_dotcom %} lo redirecciona a tu IdP para autenticarse. Después de autenticarse exitosamente, tu IdP redirecciona a este miembro a {% data variables.product.prodname_dotcom %}, en donde puede acceder a los recursos de tu organización. +Si configuras el SSO de SAML, los miembros de tu organización de {% data variables.product.prodname_dotcom %} continuarán ingresando en sus cuentas de usuario en {% data variables.product.prodname_dotcom %}. Cuando un miembro accede a recursos dentro de tu organización que utiliza el SSO de SAML, {% data variables.product.prodname_dotcom %} lo redirecciona a tu IdP para autenticarse. Después de autenticarse exitosamente, tu IdP redirecciona a este miembro a {% data variables.product.prodname_dotcom %}, en donde puede acceder a los recursos de tu organización. diff --git a/translations/es-ES/data/reusables/saml/saml-requires-ghec.md b/translations/es-ES/data/reusables/saml/saml-requires-ghec.md index 0cf73bddd5..7b1a7a7e24 100644 --- a/translations/es-ES/data/reusables/saml/saml-requires-ghec.md +++ b/translations/es-ES/data/reusables/saml/saml-requires-ghec.md @@ -1 +1 @@ -SAML SSO requires {% data variables.product.prodname_ghe_cloud %}. +El SSO de SAML requiere {% data variables.product.prodname_ghe_cloud %}. diff --git a/translations/es-ES/data/reusables/saml/switching-from-org-to-enterprise.md b/translations/es-ES/data/reusables/saml/switching-from-org-to-enterprise.md index 4cb267fa13..b531250a05 100644 --- a/translations/es-ES/data/reusables/saml/switching-from-org-to-enterprise.md +++ b/translations/es-ES/data/reusables/saml/switching-from-org-to-enterprise.md @@ -1 +1 @@ -There are special considerations when enabling SAML SSO for your enterprise account if any of the organizations owned by the enterprise account are already configured to use SAML SSO. \ No newline at end of file +Existen consideraciones especiales al habilitar el SSO de SAML en tu cuenta empresarial si cualquiera de las organizaciones que pertenecen a la cuenta empresarial ya se configuraron para utilizar el SSO de SAML. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/saml/when-you-enforce.md b/translations/es-ES/data/reusables/saml/when-you-enforce.md index 83c4949182..bbb0b1eb08 100644 --- a/translations/es-ES/data/reusables/saml/when-you-enforce.md +++ b/translations/es-ES/data/reusables/saml/when-you-enforce.md @@ -1 +1 @@ -When you enforce SAML SSO, all members of the organization must authenticate through your IdP to access the organization's resources. +Cuando requieres el SSO de SAML, todos los miembros de la organización deben autenticarse a través de tu IdP para acceder a los recursos organizacionales. 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 e5a47bc839..723975ec3e 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 @@ -1,7 +1,7 @@ -| Provider | Secreto compatible | Slug de la API | -| -------- | ------------------ | -------------- | -| | | | -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +| Proveedor | Secreto compatible | Slug de la API | +| --------- | ------------------ | -------------- | +| | | | +{%- ifversion fpt or ghes > 2.22 or ghae %} Adafruit IO | Adafruit IO Key | adafruit_io_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Adobe | Token de Dispositivo de Adobe | adobe_device_token{% endif %} @@ -11,73 +11,73 @@ Adobe | Token de Servicio de Adobe | adobe_service_token{% endif %} Adobe | Token de Acceso de Duración Corta de Adobe | adobe_short_lived_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Adobe | Token Web JSON de Adobe | adobe_jwt{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Alibaba Cloud | ID de Llave de Acceso de Alibaba Cloud | alibaba_cloud_access_key_id{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Alibaba Cloud | Secreto de Llave de Acceso de Alibaba Cloud | alibaba_cloud_access_key_secret{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Amazon Web Services (AWS) | ID de Llave de Acceso de Amazon AWS | aws_access_key_id{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Amazon Web Services (AWS) | Llave de Acceso de Secreto de Amazon AWS | aws_secret_access_key{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} -Amazon Web Services (AWS) | Amazon AWS Session Token | aws_session_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} -Amazon Web Services (AWS) | Amazon AWS Temporary Access Key ID | aws_temporary_access_key_id{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +Amazon Web Services (AWS) | Token de Sesión de Amazon AWS | aws_session_token{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +Amazon Web Services (AWS) | ID de Llave de Acceso Temporal de Amazon AWS | aws_temporary_access_key_id{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Asana | Token de Acceso Personal de Asana Personal | asana_personal_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Atlassian | Token de la API de Atlassian | atlassian_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Atlassian | Token Web JSON de Atlassian | atlassian_jwt{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Atlassian | Token de Acceso Personal de Bitbucket Server | bitbucket_server_personal_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Azure | Token de Acceso Personal de Azure DevOps | azure_devops_personal_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Azure | Token de Azure SAS | azure_sas_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Azure | Certificado de Administración de Servicio de Azure | azure_management_certificate{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Azure | Secuencia de Conexión SQL de Azure | azure_sql_connection_string{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Azure | Llave de Cuenta de Almacenamiento de Azure | azure_storage_account_key{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} -Beamer | Beamer API Key | beamer_api_key{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +Beamer | Llave de la API de Beamer | beamer_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} -Checkout.com | Checkout.com Production Secret Key | checkout_production_secret_key{% endif %} +Checkout.com | Llave de Secreto de Producción de Checkout.com | checkout_production_secret_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} -Checkout.com | Checkout.com Test Secret Key | checkout_test_secret_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +Checkout.com | Llave de Secreto de Pruebas de Checkout.com | checkout_test_secret_key{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Clojars | Token de Despliegue de Clojars | clojars_deploy_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} CloudBees CodeShip | Credencial de CodeShip de CloudBees | codeship_credential{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} -Contentful | Contentful Personal Access Token | contentful_personal_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} +Contentful | Token de Acceso personal de Contentful | contentful_personal_access_token{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Databricks | Token de Acceso de Databricks | databricks_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Discord | Token del Bot de Discord | discord_bot_token{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Doppler | Token Personal de Doppler | doppler_personal_token{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Doppler | Token de Servicio de Doppler | doppler_service_token{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Doppler | Token del CLI de Doppler | doppler_cli_token{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Doppler | Token de SCIM de Doppler | doppler_scim_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} -Doppler | Doppler Audit Token | doppler_audit_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +Doppler | Token de Auditoría de Doppler | doppler_audit_token{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Dropbox | Token de Acceso de Dropbox | dropbox_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Dropbox | Token de Acceso de Duración Corta de Dropbox | dropbox_short_lived_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} -Duffel | Duffel Live Access Token | duffel_live_access_token{% endif %} +Duffel | Token de Acceso en Vivo de Duffel | duffel_live_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} -Duffel | Duffel Test Access Token | duffel_test_access_token{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +Duffel | Token de Acceso de Prueba de Duffel | duffel_test_access_token{% endif %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Dynatrace | Token de Acceso de Dynatrace | dynatrace_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Dynatrace | Token Interno de Dynatrace | dynatrace_internal_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} EasyPost | Llave de la API de Producción de EasyPost | easypost_production_api_key{% endif %} @@ -87,18 +87,18 @@ EasyPost | Llave de la API de Pruebas de EasyPost | easypost_test_api_key{% endi Facebook | Token de Acceso de Facebook | facebook_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Fastly | Token de la API de Fastly | fastly_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Finicity | Llave de la App de Finicity | finicity_app_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} -Flutterwave | Flutterwave Live API Secret Key | flutterwave_live_api_secret_key{% endif %} +Flutterwave | Llave de Secreto de la API en Vivo de Flutterwave | flutterwave_live_api_secret_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} -Flutterwave | Flutterwave Test API Secret Key | flutterwave_test_api_secret_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +Flutterwave | Llave de Secreto de la API de Pruebas de Flutterwave | flutterwave_test_api_secret_key{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Frame.io | Token Web de JSON de Frame.io | frameio_jwt{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Frame.io| Token de Desarrollador de Frame.io | frameio_developer_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} -FullStory | FullStory API Key | fullstory_api_key{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +FullStory | Llave de la API de FullStory | fullstory_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} GitHub | Token de Acceso Personal de GitHub | github_personal_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} @@ -107,29 +107,29 @@ GitHub | Token de Acceso de OAuth de GitHub | github_oauth_access_token{% endif GitHub | Token de Actualización de GitHub | github_refresh_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} GitHub | Token de Acceso a la Instalacción de una GitHub App | github_app_installation_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} GitHub | Llave Privada SSH de GitHub | github_ssh_private_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} GoCardless | Token de Acceso Directo de GoCardless | gocardless_live_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} GoCardless | Token de Acceso a GoCardless Sandbox | gocardless_sandbox_access_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} -Google | Firebase Cloud Messaging Server Key | firebase_cloud_messaging_server_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} -Google | Google API Key | google_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} -Google | Google Cloud Private Key ID | google_cloud_private_key_id{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} -Google | Google Cloud Storage Access Key Secret | google_cloud_storage_access_key_secret{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} -Google | Google Cloud Storage Service Account Access Key ID | google_cloud_storage_service_account_access_key_id{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} -Google | Google Cloud Storage User Access Key ID | google_cloud_storage_user_access_key_id{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +Google | Llave del Servidor de Mensajería de Firebase Cloud | firebase_cloud_messaging_server_key{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} +Google | Llave de la API de Google | google_api_key{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} +Google | ID de la Llave Privada de Google Cloud | google_cloud_private_key_id{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +Google | Secreto de la Llave de Acceso de Almacenamiento de Google Cloud | google_cloud_storage_access_key_secret{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +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 ghes > 3.2 %} +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 ghes > 3.1 or ghae-next %} Grafana | Llave de la API de Grafana | grafana_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Hashicorp Terraform | Token de Terraform Cloud / API de Enterprise API | terraform_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Hubspot | Llave de la API de Hubspot API | hubspot_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Intercom | Token de Acceso a Intercom | intercom_access_token{% endif %} @@ -137,10 +137,10 @@ Intercom | Token de Acceso a Intercom | intercom_access_token{% endif %} Ionic | Token de Acceso Personal de Ionic | ionic_personal_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Ionic | Token de Actualización de Ionic | ionic_refresh_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} -JFrog | JFrog Platform Access Token | jfrog_platform_access_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} -JFrog | JFrog Platform API Key | jfrog_platform_api_key{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +JFrog | Token de Acceso a la Plataforma de JFrog | jfrog_platform_access_token{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +JFrog | Llave de la API de la Plataforma de JFrog | jfrog_platform_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Linear | Llave de la API de Linear | linear_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} @@ -149,15 +149,23 @@ Linear | Token de Acceso Oauth de Linear | linear_oauth_access_token{% endif %} Lob | Llave de la API en Vivo de Lob | lob_live_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Lob | Llave de la API de Prueba de Lob | lob_test_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Mailchimp | Llave de la API de Mailchimp | mailchimp_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Mailgun | Llave de la API de Mailgun | mailgun_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} MessageBird | Llave de la API de MessageBird | messagebird_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} +New Relic | Llave Personal de la API de New Relic | new_relic_personal_api_key{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +New Relic | Llave de la API de REST de New Relic | new_relic_rest_api_key{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +New Relic | Llave de Consulta de Perspectivas de New Relic | new_relic_insights_query_key{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +New Relic | Llave de Licencia de New Relic | new_relic_license_key{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} npm | Token de Acceso a npm | npm_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} NuGet | Llave de la API de NuGet | nuget_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Onfido | Token de la API de Onfido Live | onfido_live_api_token{% endif %} @@ -165,75 +173,75 @@ 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 ghes > 3.1 or ghae-next %} OpenAI | Llave de la API de OpenAI | openai_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Palantir | Token Web de JSON de Palantir | palantir_jwt{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} -PlanetScale | PlanetScale Database Password | planetscale_database_password{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} -PlanetScale | PlanetScale OAuth Token | planetscale_oauth_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} -PlanetScale | PlanetScale Service Token | planetscale_service_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} -Plivo | Plivo Auth ID | plivo_auth_id{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} -Plivo | Plivo Auth Token | plivo_auth_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} +PlanetScale | Contraseña de la Base de Datos de PlanetScale | planetscale_database_password{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +PlanetScale | Token de OAuth de PlanetScale | planetscale_oauth_token{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +PlanetScale | Token de Servicio de PlanetScale | planetscale_service_token{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +Plivo | ID de Auth de Plivo | plivo_auth_id{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +Plivo | Token de Auth de Plivo Auth | plivo_auth_token{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Postman | Llave de la API de Postman | postman_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Proctorio | Llave de Consumidor de Proctorio | proctorio_consumer_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Proctorio | Llave de Enlace de Proctorio | proctorio_linkage_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Proctorio | Llave de Registro de Proctorio | proctorio_registration_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Proctorio | Llave Secreta de Proctorio | proctorio_secret_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Pulumi | Token de Acceso a Pulumi | pulumi_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} PyPI | Token de la API de PyPI | pypi_api_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} RubyGems | Llave de la API de RubyGems | rubygems_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Samsara | Token de la API de Samsara | samsara_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Samsara | Token de Acceso OAuth de Samsara | samsara_oauth_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} SendGrid | Llave de la API de SendGrid | sendgrid_api_key{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} -Sendinblue | Sendinblue API Key | sendinblue_api_key{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} -Sendinblue | Sendinblue SMTP Key | sendinblue_smtp_key{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +Sendinblue | Llave de la API de Sendinblue | sendinblue_api_key{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +Sendinblue | Llave de SMTP de Sendinblue | sendinblue_smtp_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Shippo | Token de la API de Shippo Live | shippo_live_api_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Shippo | Token de la APi de Prueba de Shippo | shippo_test_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Shopify | Secreto Compartido de la App de Shopify | shopify_app_shared_secret{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Shopify | Token de Acceso de Shopify | shopify_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Shopify | Toekn de Acceso a la App Personalizada de Shopify | shopify_custom_app_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Shopify | Contraseña de la App Privada de Shopify | shopify_private_app_password{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Slack | Token de la API de Slack | slack_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Slack | URL de Webhook Entrante de Slack | slack_incoming_webhook_url{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Slack | URL de Webhook de Flujo de Trabajo de Slack | slack_workflow_webhook_url{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} SSLMate | Llave de la API de SSLMate | sslmate_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} SSLMate | Secreto de Clúster de SSLMate | sslmate_cluster_secret{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Stripe | Llave de la API de Stripe | stripe_api_key{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Stripe | Llave Secreta en Vivo de la API de Stripe | stripe_live_secret_key{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Stripe | Llave Secreta de la API de Prueba de Stripe | stripe_test_secret_key{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Stripe | Llave Restringida de la API en Vivo de Stripe | stripe_live_restricted_key{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Stripe | Llave Restringida de la API de Prueba de Stripe | stripe_test_restricted_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Stripe | Secreto de Firmado de Webhook de Stripe | stripe_webhook_signing_secret{% endif %} @@ -241,9 +249,9 @@ Stripe | Secreto de Firmado de Webhook de Stripe | stripe_webhook_signing_secret Tableau | Token de Acceso Personal a Tableau | tableau_personal_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Telegram | Token del Bot de Telegram | telegram_bot_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Tencent Cloud | ID Secreta de Tencent Cloud | tencent_cloud_secret_id{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Twilio | Identificador de Secuencia de Cuenta de Twilio | twilio_account_sid{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Twilio | Llave de la API de Twilio | twilio_api_key{% endif %} diff --git a/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-public-repo.md b/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-public-repo.md index e02a928ecb..2f908830b5 100644 --- a/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-public-repo.md +++ b/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-public-repo.md @@ -15,11 +15,11 @@ | Azure | Certificado de Administración de Servicios de Azure | | Azure | Secuencia de Conexión de Azure SQL | | Azure | Clave de Cuenta de Almacenamiento de Azure | -| Checkout.com | Checkout.com Production Secret Key | -| Checkout.com | Checkout.com Test Secret Key | +| Checkout.com | Clave secreta de productión de Checkout.com | +| Checkout.com | Clave secreta de pruebas de Checkout.com | | Clojars | Token de Despliegue de Clojars | | CloudBees CodeShip | Credencial de Codeship de CloudBees | -| Contributed Systems | Contributed Systems Credentials | +| Sistemas Contribuidos | Credenciales de los sistemas contribuidos | | Databricks | Token de Acceso de Databricks | | Datadog | Clave de API de Datadog | | Discord | Token de Bot de Discord | @@ -27,7 +27,7 @@ | Doppler | Token de Servicio de Doppler | | Doppler | Token de CLI de Doppler | | Doppler | Token de SCIM de Doppler | -| Doppler | Doppler Audit Token | +| Doppler | Token de auditoría de Doppler | | Dropbox | Token de Acceso de Dropbox | | Dropbox | Token de Acceso de Vida Corta de Dropbox | | Dynatrace | Token de Acceso de Dynatrace | @@ -58,10 +58,10 @@ | NuGet | Clave de API de NuGet | | OpenAI | Clave de la API de OpenAI | | Palantir | Token Web de JSON de Palantir | -| PlanetScale | PlanetScale Database Password | -| PlanetScale | PlanetScale OAuth Token | -| PlanetScale | PlanetScale Service Token | -| Plivo | Plivo Auth ID and Token | +| PlanetScale | Contraseña de base de datos de PlanetScale | +| PlanetScale | Token de OAuth de PlanetScale | +| PlanetScale | Token de Servicio de PlanetScale | +| Plivo | Token e ID de Auth de Plivo | | Postman | Clave de API de Postman | | Proctorio | Clave de Consumidor de Proctorio | | Proctorio | Clave de Enlace de Proctorio | diff --git a/translations/es-ES/data/reusables/security/displayed-information.md b/translations/es-ES/data/reusables/security/displayed-information.md index 6187bab908..3868c361f1 100644 --- a/translations/es-ES/data/reusables/security/displayed-information.md +++ b/translations/es-ES/data/reusables/security/displayed-information.md @@ -3,6 +3,6 @@ Cuando habilitas una o más características de seguridad y análisis para los r - Todos los repositorios existentes tendrán la configuración seleccionada. - Los repositorios nuevos seguirán la configuración seleccionada si habilitaste la casilla de verificación para estos.{% ifversion fpt %} - Utilizamos los permisos para escanear en busca de archivos de manifiesto para aplicar los servicios relevantes. -- If enabled, you'll see dependency information in the dependency graph. -- If enabled, {% data variables.product.prodname_dotcom %} will generate {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies. -- If enabled, {% data variables.product.prodname_dependabot %} Security Updates will create pull requests to upgrade those dependencies.{% endif %} +- Si se habilita, verás la información de dependencias en la gráfica de dependencias. +- Si se habilita, {% data variables.product.prodname_dotcom %} generará {% data variables.product.prodname_dependabot_alerts %} para las dependencias vulnerables. +- Si se habilita, las actualizaciones de seguridad del {% data variables.product.prodname_dependabot %} crearán solicitudes de cambios para mejorar aquellas dependencias.{% endif %} diff --git a/translations/es-ES/data/reusables/sponsors/add-welcome-message.md b/translations/es-ES/data/reusables/sponsors/add-welcome-message.md new file mode 100644 index 0000000000..13c94dba67 --- /dev/null +++ b/translations/es-ES/data/reusables/sponsors/add-welcome-message.md @@ -0,0 +1 @@ +1. Opcionalmente, teclea un mensaje de bienvenida para el nivel. ![Agregar un mensaje de bienvenida](/assets/images/help/sponsors/add-a-welcome-message.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/sponsors/beta-note-sponsors-for-companies.md b/translations/es-ES/data/reusables/sponsors/beta-note-sponsors-for-companies.md index 695c2e0056..cdc84e60f7 100644 --- a/translations/es-ES/data/reusables/sponsors/beta-note-sponsors-for-companies.md +++ b/translations/es-ES/data/reusables/sponsors/beta-note-sponsors-for-companies.md @@ -1,5 +1,5 @@ {% note %} -**Note:** The Sponsors for Companies service is currently in beta and subject to change. +**Nota:** El servicio de Patrocinadores para Compañías se encuentra actualmente en beta y está sujeto a cambios. {% endnote %} diff --git a/translations/es-ES/data/reusables/sponsors/tier-details.md b/translations/es-ES/data/reusables/sponsors/tier-details.md index 06ae6c8ea4..1b4d56cf8e 100644 --- a/translations/es-ES/data/reusables/sponsors/tier-details.md +++ b/translations/es-ES/data/reusables/sponsors/tier-details.md @@ -1,4 +1,4 @@ -Puedes crear hasta 10 niveles de patrocinio de una sola ocación y 10 niveles mensuales para que los patrocinadores escojan entre ellos. Cada nivel tiene su propia cantidad de pago mensual o de única ocasión en dólares estadounidenses y puedes elegir habilitar los niveles para cantidades personalizadas. Adicionalmente, puedes elegir habilitar los niveles para las cantidades personalizadas (mensuales y de única ocasión). +Puedes crear hasta 10 niveles de patrocinio de una sola ocasión y 10 niveles mensuales para que los patrocinadores escojan entre ellos. Cada nivel tiene su propia cantidad de pago mensual o de única ocasión en dólares estadounidenses y puedes elegir habilitar los niveles para cantidades personalizadas. Adicionalmente, puedes elegir habilitar los niveles para las cantidades personalizadas (mensuales y de única ocasión). Puedes personalizar las recompensas de cada nivel. Por ejemplo, las recompensas de un nivel podrían incluir: - Acceso temprano a versiones nuevas @@ -7,4 +7,6 @@ Puedes personalizar las recompensas de cada nivel. Por ejemplo, las recompensas - Actualizaciones del boletín semanal - Otras recompensas de las cuales disfrutarían tus patrocinadores ✨ +Puedes incluir un mensaje de bienvenida con información sobre cómo acceder o recibir recompensas, el cual se podrá ver después de hacer el pago y en el correo electrónico de bienvenida. + Una vez que hayas publicado un nivel, no podrás editar el precio del mismo. En vez de eso, deberás retirar el nivel y crear uno nuevo. Los patrocinadores existentes seguirán en el nivel que se retiró hasta que cambian su nivel de patrocinio, cancelen su patrocinio, o venza su periodo de patrocinio de una sola ocasión. diff --git a/translations/es-ES/data/reusables/ssh/add-ssh-key-to-ssh-agent-commandline.md b/translations/es-ES/data/reusables/ssh/add-ssh-key-to-ssh-agent-commandline.md index 415f86736d..9bed61119b 100644 --- a/translations/es-ES/data/reusables/ssh/add-ssh-key-to-ssh-agent-commandline.md +++ b/translations/es-ES/data/reusables/ssh/add-ssh-key-to-ssh-agent-commandline.md @@ -1,3 +1,3 @@ ```shell -$ ssh-add ~/.ssh/id_ed25519 +$ ssh-add ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %} ``` diff --git a/translations/es-ES/data/reusables/ssh/add-ssh-key-to-ssh-agent.md b/translations/es-ES/data/reusables/ssh/add-ssh-key-to-ssh-agent.md index c07831e466..4174a9a319 100644 --- a/translations/es-ES/data/reusables/ssh/add-ssh-key-to-ssh-agent.md +++ b/translations/es-ES/data/reusables/ssh/add-ssh-key-to-ssh-agent.md @@ -1 +1 @@ -Si creaste tu llave con un nombre diferente, o si estás agregando una llave existente que tiene un nombre diferente, reemplaza *id_ed25519* en el comando con el nombre de tu archivo de llave privada. +Si creaste tu llave con un nombre diferente o si estás agregando una llave existente que tenga un nombre diferente, reemplaza a *id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}* en el comando con el nombre de tu archivo de llave privada. 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 c844af9547..b414d3d5d4 100644 --- a/translations/es-ES/data/reusables/ssh/key-type-support.md +++ b/translations/es-ES/data/reusables/ssh/key-type-support.md @@ -1,9 +1,9 @@ {% note %} -**Note:** {% data variables.product.company_short %} is improving security by dropping older, insecure key types. +**Nota:** {% data variables.product.company_short %} está mejrando la seguridad al dejar los tipos de llaves inseguras y más antiguas. -DSA keys (`ssh-dss`) are no longer supported. Existing keys will continue to function through March 15, 2022. You cannot add new DSA keys to your user account on {% data variables.product.product_name %}. +Ya no hay compatibilidad con llaves DSA (`ssh-dss`). Las llaves existentes seguirán funcionando hasta el 15 de mazo de 2022. No puedes agregar llaves DSA nuevas a tu cuenta de usuario en {% data variables.product.product_name %}. -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. +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 %} diff --git a/translations/es-ES/data/reusables/user_settings/access_org.md b/translations/es-ES/data/reusables/user_settings/access_org.md index b8f1dc2dec..4057c97921 100644 --- a/translations/es-ES/data/reusables/user_settings/access_org.md +++ b/translations/es-ES/data/reusables/user_settings/access_org.md @@ -1 +1 @@ -2. Click the name of your organization. ![Nombre de la organización en la lista de organizaciones](/assets/images/help/organizations/org-settings-link.png) +2. Haz clic en el nombre de tu organización. ![Nombre de la organización en la lista de organizaciones](/assets/images/help/organizations/org-settings-link.png) diff --git a/translations/es-ES/data/reusables/user_settings/generate_new_token.md b/translations/es-ES/data/reusables/user_settings/generate_new_token.md new file mode 100644 index 0000000000..f7834b08e3 --- /dev/null +++ b/translations/es-ES/data/reusables/user_settings/generate_new_token.md @@ -0,0 +1 @@ +1. Haz clic en **Generar un nuevo token**. ![Generar el botón para el nuevo token](/assets/images/help/settings/generate_new_token.png) \ No newline at end of file diff --git a/translations/es-ES/data/reusables/webhooks/webhooks-rest-api-links.md b/translations/es-ES/data/reusables/webhooks/webhooks-rest-api-links.md index 671f26ac86..8e9793edf5 100644 --- a/translations/es-ES/data/reusables/webhooks/webhooks-rest-api-links.md +++ b/translations/es-ES/data/reusables/webhooks/webhooks-rest-api-links.md @@ -1,5 +1,5 @@ -The webhook REST APIs enable you to manage repository{% ifversion ghes < 3.0 %} and organization{% else %}, organization, and app{% endif %} webhooks.{% ifversion fpt or ghes > 3.2 or ghae %} You can use this API to list webhook deliveries for a webhook, or get and redeliver an individual delivery for a webhook, which can be integrated into an external app or service.{% endif %}{% ifversion fpt or ghes > 2.22 or ghae %} You can also use the REST API to change the configuration of the webhook. For example, you can modify the payload URL, content type, SSL verification, and secret.{% endif %} For more information, see: +Las API de REST de los webhooks te permiten administrar los webhooks de repositorios {% ifversion ghes < 3.0 %} y organizaciones{% else %}, organizaciones y aplicaciones{% endif %}.{% ifversion fpt or ghes > 3.2 or ghae %} Puedes utilizar esta API para listar las entregas de listas de webhooks para un webhook u obtener y volver a hacer entregas individuales para un webhook, el cual se pueda integrar en un servicio o app externa.{% endif %}{% ifversion fpt or ghes > 2.22 or ghae %} También puedes utilizar la API de REST para cambiar la configuración del webhook. Por ejemplo, puedes modificar la URL de la carga útil, el tipo de contenido, la verificación SSL y el secreto.{% endif %} Para obtener más información, consulta las secciones: - [API de REST para los webhooks de los repositorios](/rest/reference/repos#webhooks) - [API de REST para los Webhooks de las Organizaciones](/rest/reference/orgs#webhooks){% ifversion fpt or ghes > 2.22 or ghae %} -- [{% data variables.product.prodname_github_app %} Webhooks REST API](/rest/reference/apps#webhooks){% endif %} +- [{% data variables.product.prodname_github_app %} API de REST de Webhooks](/rest/reference/apps#webhooks){% endif %} diff --git a/translations/es-ES/data/reusables/webhooks/workflow_job_properties.md b/translations/es-ES/data/reusables/webhooks/workflow_job_properties.md index dbd64fc8dd..bca545d41e 100644 --- a/translations/es-ES/data/reusables/webhooks/workflow_job_properties.md +++ b/translations/es-ES/data/reusables/webhooks/workflow_job_properties.md @@ -1,4 +1,4 @@ -| Clave | Type | Descripción | -| -------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción realizada. Puede ser una de las siguientes:
    • `queued` - A new job was created.
    • `in_progress` - The job has started processing on the runner.
    • `completed` - The `status` of the job is `completed`.
    | -| `workflow_job` | `objeto` | The workflow job. Many `workflow_job` keys, such as `head_sha`, `conclusion`, and `started_at` are the same as those in a [`check_run`](#check_run) object. | \ No newline at end of file +| Clave | Type | Descripción | +| -------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `Acción` | `secuencia` | La acción realizada. Puede ser una de las siguientes:
    • `queued` - Se creó un job nuevo.
    • `in_progress` - El job se comenzó a procesar en el ejecutor.
    • `completed` - el `status` del job es `completed`.
    | +| `workflow_job` | `objeto` | El job de flujo de trabajo. Muchas claves de `workflow_job`, tales como `head_sha`, `conclusion`, y `started_at` son las mismas que aquellas en un objeto [`check_run`](#check_run). | \ No newline at end of file diff --git a/translations/es-ES/data/reusables/webhooks/workflow_job_short_desc.md b/translations/es-ES/data/reusables/webhooks/workflow_job_short_desc.md index 08dc892ea3..a3824c2ac3 100644 --- a/translations/es-ES/data/reusables/webhooks/workflow_job_short_desc.md +++ b/translations/es-ES/data/reusables/webhooks/workflow_job_short_desc.md @@ -1 +1 @@ -A {% data variables.product.prodname_actions %} workflow job has been queued, is in progress, or has been completed on a repository. {% data reusables.webhooks.action_type_desc %} +Un job de flujo de trabajo de {% data variables.product.prodname_actions %} se puso en cola, está en progreso o se completó en un repositorio. {% data reusables.webhooks.action_type_desc %} diff --git a/translations/es-ES/data/ui.yml b/translations/es-ES/data/ui.yml index 0c8ec8247f..46e2d4534e 100644 --- a/translations/es-ES/data/ui.yml +++ b/translations/es-ES/data/ui.yml @@ -30,9 +30,10 @@ toc: guides: Guías whats_new: Qué hay de nuevo pages: - article_version: 'Versión del artículo:' + article_version: 'Versión del artículo' miniToc: En este artículo contributor_callout: En este artículo contribuye y lo mantiene + all_enterprise_releases: Todos los lanzamientos de Enterprise errors: oops: '¡Ups!' something_went_wrong: Parece que algo salió mal. @@ -155,13 +156,17 @@ product_sublanding: learning_paths_desc: Las rutas de aprendizaje son una recopilación de guías que te ayudan a dominar un tema en particular. guides: 'Guías de {{ productMap[currentProduct].name }}' more_guides: más guías - no_result: Lo sentimos, no hay guías que coincidan con tu filtro. load_more: Carga más guías all_guides: 'Todas las guías de {{ productMap[currentProduct].name }}' + filter_instructions: Filtra la lista de guías utilizando estos controles filters: type: Type topic: Tema all: Todas + guides_found: + multiple: 'Se encontraron {n} guías' + one: Se encontró 1 guía + none: No se encontraron guías guide_types: overview: Resumen quick_start: Inicio Rápido diff --git a/translations/es-ES/data/variables/contact.yml b/translations/es-ES/data/variables/contact.yml index c81b26a543..e5e6c681c7 100644 --- a/translations/es-ES/data/variables/contact.yml +++ b/translations/es-ES/data/variables/contact.yml @@ -2,7 +2,7 @@ #TODO: Replace with support.github.com once portal is deprecated. contact_ent_support: 'GitHub Enterprise Support](https://enterprise.githubsupport.com/hc/en-us) o [GitHub Premium Support](https://premium.githubsupport.com)' contact_support: >- - {% ifversion fpt %}[GitHub Support](https://support.github.com/contact?tags=docs-generic){% else %}your site administrator{% endif %} + {% ifversion fpt %}[Soporte de GitHub](https://support.github.com/contact?tags=docs-generic){% else %}el administrador de tu sitio{% endif %} report_abuse: >- {% ifversion fpt %}[Report abuse](https://github.com/contact/report-abuse){% endif %} report_content: >- diff --git a/translations/es-ES/data/variables/migrations.yml b/translations/es-ES/data/variables/migrations.yml index 3f4894bfa1..b2074b9e10 100644 --- a/translations/es-ES/data/variables/migrations.yml +++ b/translations/es-ES/data/variables/migrations.yml @@ -2,6 +2,6 @@ user_migrations_intro: >- Puedes utilizar esta API para revisar, respaldar, o migrar tus datos de usuario que se almacenan en {% data variables.product.product_name %},com. organization_migrations_intro: >- - The organization migrations API lets you move a repository from {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.prodname_ghe_server %}. For more information, see "[Exporting migration data from GitHub.com](/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-githubcom)." + La API de migraciones de la organización te permite mover un repositorio desde {% data variables.product.prodname_dotcom_the_website %} a {% data variables.product.prodname_ghe_server %}. Para obtener más información, consulta la sección "[Exportar los datos de migración de GitHub.com](/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-githubcom)". source_imports_intro: >- La API de Importaciones de Código Fuente te permite iniciar una importación desde un repositorio origen en Git, Subversion, Mercurial o Team Foundation Version Control. Esta es la misma funcionalidad que tiene el importador de {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Importar un repositorio con el importador de {% data variables.product.prodname_dotcom %}](/github/importing-your-projects-to-github/importing-a-repository-with-github-importer)". diff --git a/translations/es-ES/data/variables/product.yml b/translations/es-ES/data/variables/product.yml index 6c3763688c..7604bfdc92 100644 --- a/translations/es-ES/data/variables/product.yml +++ b/translations/es-ES/data/variables/product.yml @@ -76,6 +76,14 @@ prodname_actions: 'GitHub Actions' prodname_debug: 'Depuración de GitHub' #GitHub Discussions prodname_discussions: 'GitHub Discussions' +#GitHub Enterprise Managed Users +prodname_emu_idp_application: 'Usuario Administrado de GitHub Enterprise' +prodname_emus: 'Usuarios Administrados de Enterprise' +prodname_managed_user: 'usuario administrado' +prodname_managed_users: 'usuarios administrados' +prodname_managed_users_caps: 'Usuarios administrados' +prodname_emu_enterprise: 'empresa con usuarios administrados' +prodname_emu_org: 'organización con usuarios administrados' #GitHub Issues prodname_github_issues: 'Propuestas de GitHub' #GitHub Packages @@ -94,6 +102,7 @@ prodname_security_center: 'Centro de seguridad' #Codespaces prodname_codespaces: 'Codespaces' prodname_github_codespaces: 'Acerca de GitHub Codespaces' +prodname_serverless: 'editor basado en la web' #GitHub resources: blog, jobs, Learning Lab prodname_gcf: 'Soporte de la Comunidad de GitHub' prodname_blog: 'el blog de GitHub' @@ -135,6 +144,8 @@ prodname_dependabot_version_updates: 'Actualizaciones de versión del dependabot #GitHub Archive Program prodname_archive: 'Programa de Archivo de GitHub' prodname_arctic_vault: 'Bóveda de Código del Ártico' +#GitHub Copilot +prodname_copilot: 'Copiloto de GitHub' #Links product_url: >- {% ifversion fpt %}github.com{% else %}[hostname]{% endif %} diff --git a/translations/es-ES/data/variables/release_candidate.yml b/translations/es-ES/data/variables/release_candidate.yml index e6ddf079ac..ec65ef6f94 100644 --- a/translations/es-ES/data/variables/release_candidate.yml +++ b/translations/es-ES/data/variables/release_candidate.yml @@ -1,2 +1,2 @@ --- -version: enterprise-server@3.2 +version: '' diff --git a/translations/es-XL/content/actions/index.md b/translations/es-XL/content/actions/index.md index a57214431a..99a854f8fd 100644 --- a/translations/es-XL/content/actions/index.md +++ b/translations/es-XL/content/actions/index.md @@ -6,6 +6,7 @@ featuredLinks: guides: - /actions/learn-github-actions - /actions/guides/about-continuous-integration + - /actions/deployment/deploying-with-github-actions - /actions/guides/about-packaging-with-github-actions - /actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting guideCards: diff --git a/translations/es-XL/content/admin/configuration/index.md b/translations/es-XL/content/admin/configuration/index.md index 00c70ddbd2..e0d693a1f2 100644 --- a/translations/es-XL/content/admin/configuration/index.md +++ b/translations/es-XL/content/admin/configuration/index.md @@ -12,7 +12,7 @@ topics: children: - /configuring-your-enterprise - /configuring-network-settings - - /managing-connections-between-github-enterprise-server-and-github-enterprise-cloud + - /managing-connections-between-your-enterprise-accounts --- ### Índice diff --git a/translations/es-XL/content/admin/policies/enforcing-policies-for-your-enterprise/index.md b/translations/es-XL/content/admin/policies/enforcing-policies-for-your-enterprise/index.md index 74f0f89501..ad7d16b6d8 100644 --- a/translations/es-XL/content/admin/policies/enforcing-policies-for-your-enterprise/index.md +++ b/translations/es-XL/content/admin/policies/enforcing-policies-for-your-enterprise/index.md @@ -10,6 +10,7 @@ topics: children: - /enforcing-repository-management-policies-in-your-enterprise - /restricting-email-notifications-for-your-enterprise + - /enforcing-github-actions-policies-for-your-enterprise - /enforcing-policies-for-advanced-security-in-your-enterprise --- diff --git a/translations/es-XL/content/developers/overview/index.md b/translations/es-XL/content/developers/overview/index.md index df13b10ce3..bb9cd35b21 100644 --- a/translations/es-XL/content/developers/overview/index.md +++ b/translations/es-XL/content/developers/overview/index.md @@ -8,7 +8,6 @@ versions: children: - /about-githubs-apis - /managing-deploy-keys - - /viewing-deployment-history - /using-ssh-agent-forwarding - /secret-scanning-partner-program - /replacing-github-services diff --git a/translations/es-XL/content/github/index.md b/translations/es-XL/content/github/index.md index 04d183038b..8485ffc99d 100644 --- a/translations/es-XL/content/github/index.md +++ b/translations/es-XL/content/github/index.md @@ -15,7 +15,6 @@ children: - /writing-on-github - /committing-changes-to-your-project - /collaborating-with-pull-requests - - /searching-for-information-on-github - /importing-your-projects-to-github - /managing-security-vulnerabilities - /finding-security-vulnerabilities-and-errors-in-your-code diff --git a/translations/es-XL/content/github/site-policy/index.md b/translations/es-XL/content/github/site-policy/index.md index 51458c278a..a101a06afb 100644 --- a/translations/es-XL/content/github/site-policy/index.md +++ b/translations/es-XL/content/github/site-policy/index.md @@ -12,7 +12,7 @@ children: - /github-terms-of-service - /github-corporate-terms-of-service - /github-privacy-statement - - /github-data-protection-agreement-non-enterprise-customers + - /github-data-protection-agreement - /global-privacy-practices - /github-sponsors-additional-terms - /github-codespaces-privacy-statement diff --git a/translations/es-XL/content/index.md b/translations/es-XL/content/index.md index 379286c915..00e8054831 100644 --- a/translations/es-XL/content/index.md +++ b/translations/es-XL/content/index.md @@ -4,7 +4,7 @@ featuredLinks: gettingStarted: - /github/getting-started-with-github/set-up-git - /github/authenticating-to-github/connecting-to-github-with-ssh - - /github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github + - /repositories/creating-and-managing-repositories - /github/writing-on-github/basic-writing-and-formatting-syntax popular: - /github/collaborating-with-issues-and-pull-requests/about-pull-requests @@ -14,20 +14,25 @@ featuredLinks: - /github/working-with-github-pages versions: '*' children: + - get-started + - account-and-profile + - authentication + - repositories - github - admin - billing - organizations - code-security + - issues - actions + - codespaces - packages + - search-github - developers - rest - graphql - - insights - - issues + - github-cli - discussions - - codespaces - sponsors - communities - pages @@ -35,11 +40,6 @@ children: - desktop - early-access externalProducts: - cli: - id: cli - name: GitHub CLI - href: 'https://cli.github.com/manual' - external: true atom: id: atom name: Atom diff --git a/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md b/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md index e4d229fc43..f884fdd47f 100644 --- a/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md +++ b/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md @@ -45,7 +45,7 @@ shortTitle: Manage your subscriptions {% data reusables.notifications.access_notifications %} 1. 通知インボックスから、サブスクライブ解除する通知を選択します。 -2. **選択した** {% octicon "triangle-down" aria-label="The down triangle icon" %} ドロップダウンを使用して、[**Unsubscribe**] をクリックします。 ![メインインボックスの [Unsubcribe] オプション](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png) +2. Click **Unsubscribe.** ![メインインボックスの [Unsubcribe] オプション](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png) ## サブスクリプションページで通知をサブスクライブ解除する @@ -61,13 +61,12 @@ shortTitle: Manage your subscriptions {% data reusables.notifications.access_notifications %} 1. 左側のサイドバーの、リポジトリリストの下にある [Manage notifications] ドロップダウンを使用して、[**Watched repositories**] をクリックします。 ![[Manage notifications] ドロップダウンメニューオプション](/assets/images/help/notifications-v2/manage-notifications-options.png) 2. Watch しているリポジトリのページで、Watchしているリポジトリを評価した後、次のいずれかを選択します。 - {% ifversion ghae or ghes < 3.1 %} - - リポジトリの Watch 解除 - - Only watch releases for a repository - - Ignore all notifications for a repository - {% endif %} {% ifversion fpt or ghes > 3.0 or ghae-next %} - リポジトリの Watch 解除 - Ignore all notifications for a repository - Customize the types of event you receive notifications for ({% data reusables.notifications-v2.custom-notification-types %}, if enabled) + {% else %} + - リポジトリの Watch 解除 + - Only watch releases for a repository + - Ignore all notifications for a repository {% endif %} diff --git a/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md b/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md index d6ace71654..2eb8ee3b99 100644 --- a/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md +++ b/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md @@ -70,10 +70,10 @@ shortTitle: View subscriptions 1. 左側のサイドバーの、リポジトリリストの下にある [Manage notifications] ドロップダウンメニューを使用して、[**Watched repositories**] をクリックします。 ![[Manage notifications] ドロップダウンメニューオプション](/assets/images/help/notifications-v2/manage-notifications-options.png) 2. Watch しているリポジトリを評価し、それらの更新がまだ関連していて有用であるかどうかを判断します。 リポジトリを Watch すると、そのリポジトリのすべての会話が通知されます。 -{% ifversion ghae or ghes < 3.1 %} - ![Watch対象の通知ページ](/assets/images/help/notifications-v2/watched-notifications.png) -{% elsif fpt or ghes > 3.0 or ghae-next %} +{% ifversion fpt or ghes > 3.0 or ghae-next %} ![Watch対象の通知ページ](/assets/images/help/notifications-v2/watched-notifications-custom.png) +{% else %} + ![Watch対象の通知ページ](/assets/images/help/notifications-v2/watched-notifications.png) {% endif %} {% tip %} diff --git a/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md b/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md index 658bebd348..d367e37da5 100644 --- a/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md +++ b/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md @@ -29,7 +29,7 @@ topics: - 特定の Issue、プルリクエスト、または Gist の会話。 - リポジトリまたは Team ディスカッション内のすべてのアクティビティ。 - {% data variables.product.prodname_actions %} で設定されたリポジトリ内のワークフローのステータスなどの CI アクティビティ。 {% ifversion fpt or ghes > 3.0 or ghae-next %} -- Repository {% data reusables.notifications-v2.custom-notification-types %} (if enabled). {% elsif ghae or ghes %} +- Repository {% data reusables.notifications-v2.custom-notification-types %} (if enabled).{% else %} - Releases in a repository.{% endif %} フォークを除き、あなたがプッシュアクセスを持つすべてのリポジトリを自動的にWatchすることもできます。 [**Watch**] をクリックすると、手動でアクセスできる他のリポジトリを Watch できます。 diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md index f2ab357cae..2330e2297f 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md @@ -48,6 +48,14 @@ shortTitle: Personalize プロフィールに表示される名前は変更可能です。 この名前は、Organization が所有するプライベートリポジトリへのコメントの横に表示されることもあります。 詳細は「[Organization のメンバー名表示を管理する](/articles/managing-the-display-of-member-names-in-your-organization)」を参照してください。 +{% ifversion fpt %} +{% note %} + +**Note:** If you're a member of an {% data variables.product.prodname_emu_enterprise %}, any changes to your profile name must be made through your identity provider instead of {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.emu-more-info-account %} + +{% endnote %} +{% endif %} + {% data reusables.user_settings.access_settings %} 2. [Name] の下に、プロフィールに表示する名前を入力します。 ![プロフィール設定の [Name] フィールド](/assets/images/help/profile/name-field.png) diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/index.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/index.md index 8843a43799..b3ea7f683c 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/index.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/index.md @@ -14,7 +14,7 @@ children: - /viewing-contributions-on-your-profile - /showing-an-overview-of-your-activity-on-your-profile - /publicizing-or-hiding-your-private-contributions-on-your-profile - - /sending-your-github-enterprise-server-contributions-to-your-githubcom-profile + - /sending-enterprise-contributions-to-your-githubcom-profile - /why-are-my-contributions-not-showing-up-on-my-profile - /troubleshooting-commits-on-your-timeline shortTitle: Manage contribution graph diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-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/publicizing-or-hiding-your-private-contributions-on-your-profile.md index 9971937504..a911bbd02b 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-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/publicizing-or-hiding-your-private-contributions-on-your-profile.md @@ -14,14 +14,18 @@ topics: shortTitle: Private contributions --- -プライベートコントリビューションを公開しても、あなたが作業しているプライベートリポジトリへのアクセス権がないユーザーがあなたのプライベートコントリビューションを見ることはできません。 かわりに、特定の日におけるプライベートコントリビューションの数だけを見ることができます。 パブリックコントリビューションには、詳細な情報が含まれます。 詳細は、「[プロフィールページ上にコントリビューションを表示する](/articles/viewing-contributions-on-your-profile-page)」を参照してください。 +プライベートコントリビューションを公開しても、あなたが作業しているプライベートリポジトリへのアクセス権がないユーザーがあなたのプライベートコントリビューションを見ることはできません。 かわりに、特定の日におけるプライベートコントリビューションの数だけを見ることができます。 パブリックコントリビューションには、詳細な情報が含まれます。 For more information, see "[Viewing contributions on your profile page](/articles/viewing-contributions-on-your-profile-page)." + +{% note %} + +**Note:** {% ifversion fpt or ghes %}On {% ifversion fpt %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_name %}{% endif %}, public contributions on your profile are visible {% ifversion fpt %}to anyone in the world who can access {% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}only to other users of {% data variables.product.product_location%}{% endif %}.{% elsif ghae %}On {% data variables.product.prodname_ghe_managed %}, only other members of your enterprise can see the contributions on your profile.{% endif %} + +{% endnote %} ## プライベートコントリビューションの可視性を変更する -デフォルトでは、訪問者にはあなたのプロフィールのパブリックコントリビューションしか表示されません。 - {% data reusables.profile.access_profile %} -2. プライベートコントリビューションをプロフィールで公開または非公開にする +1. プライベートコントリビューションをプロフィールで公開または非公開にする - プライベートコントリビューションを公開するには、コントリビューショングラフの上で、[**Contribution settings**] ドロップダウンメニューから [**Private contributions**] を選択します。 訪問者には、プライベートコントリビューションの数だけが表示され、それ以上の詳細は表示されません。 ![[Contribution settings] メニューで、訪問者がプライベートコントリビューションを見られるようにする](/assets/images/help/profile/private-contributions-on.png) - プライベートコントリビューションを非公開にするには、コントリビューショングラフの上で、[**Contribution settings**] ドロップダウンメニューを使用し、[**Private contributions**] の選択を解除します。訪問者には、パブリックコントリビューションのみが表示されるようになります。 ![[Contribution settings] メニューで、訪問者がプライベートコントリビューションを見られるようにする](/assets/images/help/profile/private-contributions-off.png) diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md new file mode 100644 index 0000000000..cac941f84e --- /dev/null +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md @@ -0,0 +1,65 @@ +--- +title: Sending enterprise contributions to your GitHub.com profile +intro: '{% data variables.product.prodname_dotcom_the_website %} プロフィールにコントリビューションカウントを送ることで、{% data variables.product.prodname_enterprise %} のあなたの作業をハイライトできます。' +redirect_from: + - /articles/sending-your-github-enterprise-contributions-to-your-github-com-profile/ + - /articles/sending-your-github-enterprise-server-contributions-to-your-github-com-profile + - /articles/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile + - /github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile + - /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile +versions: + fpt: '*' + ghes: '*' + ghae: next +topics: + - Profiles +shortTitle: Send enterprise contributions +--- + +## About enterprise contributions on your {% data variables.product.prodname_dotcom_the_website %} profile + +Your {% data variables.product.prodname_dotcom_the_website %} profile shows {% ifversion fpt %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae-next %} or {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} contribution counts from the past 90 days. {% data variables.product.prodname_enterprise %} からの {% data reusables.github-connect.sync-frequency %} コントリビューションのカウントは、プライベートコントリビューションとみなされます。 The commit details will only show the contribution counts and that these contributions were made in a {% data variables.product.prodname_enterprise %} environment outside of {% data variables.product.prodname_dotcom_the_website %}. + +You can decide whether to show counts for private contributions on your profile. 詳細は「[プライベートコントリビューションをプロフィールで公開または非公開にする](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile/)」を参照してください。 + +コントリビューションの計算方法の詳しい情報については、「[プロフィールでコントリビューショングラフを管理する](/articles/managing-contribution-graphs-on-your-profile/)」を参照してください。 + +{% note %} + +**ノート:** +- お客様のアカウント間のコネクションは、GitHub's Privacy Statement が適用されます。また、接続を有効にしているユーザは、GitHub's Terms of Service を承諾するものとします。 + +- Before you can connect your {% ifversion fpt %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae-next %} or {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} profile to your {% data variables.product.prodname_dotcom_the_website %} profile, your enterprise owner must enable {% data variables.product.prodname_github_connect %} and enable contribution sharing between the environments. For more information, contact your enterprise owner. + +{% endnote %} + +{% ifversion fpt or ghes or ghae %} + +## Sending your enterprise contributions to your {% data variables.product.prodname_dotcom_the_website %} profile + +{% ifversion fpt %} + +- To send enterprise contributions from {% data variables.product.prodname_ghe_server %} to your {% data variables.product.prodname_dotcom_the_website %} profile, see "[Sending enterprise contributions to your {% data variables.product.prodname_dotcom_the_website %} profile](/enterprise-server/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)" in the {% data variables.product.prodname_ghe_server %} documentation.{% ifversion ghae-next %} +- To send enterprise contributions from {% data variables.product.prodname_ghe_managed %} to your {% data variables.product.prodname_dotcom_the_website %} profile, see "[Sending enterprise contributions to your {% data variables.product.prodname_dotcom_the_website %} profile](/github-ae@latest/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)" in the {% data variables.product.prodname_ghe_managed %} documentation.{% endif %} + +{% elsif ghes %} + +1. Sign in to {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_dotcom_the_website %}. +1. On {% data variables.product.prodname_ghe_server %}, in the upper-right corner of any page, click your profile photo, then click **Settings**. ![ユーザバーの [Settings（設定）] アイコン](/assets/images/help/settings/userbar-account-settings.png) +{% data reusables.github-connect.github-connect-tab-user-settings %} +{% data reusables.github-connect.connect-dotcom-and-enterprise %} +1. {% data variables.product.prodname_dotcom_the_website %}アカウントから{% data variables.product.prodname_ghe_server %}がアクセスするリソースをレビューし、** Authorize（承認）**をクリックしてください。 ![GitHub Enterprise ServerとGitHub.com間の接続の承認](/assets/images/help/settings/authorize-ghe-to-connect-to-dotcom.png) +{% data reusables.github-connect.send-contribution-counts-to-githubcom %} + +{% elsif ghae %} + +1. Sign in to {% data variables.product.prodname_ghe_managed %} and {% data variables.product.prodname_dotcom_the_website %}. +1. On {% data variables.product.prodname_ghe_managed %}, in the upper-right corner of any page, click your profile photo, then click **Settings**. ![ユーザバーの [Settings（設定）] アイコン](/assets/images/help/settings/userbar-account-settings.png) +{% data reusables.github-connect.github-connect-tab-user-settings %} +{% data reusables.github-connect.connect-dotcom-and-enterprise %} +{% data reusables.github-connect.authorize-connection %} +{% data reusables.github-connect.send-contribution-counts-to-githubcom %} + +{% endif %} + +{% endif %} 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 aee92b16b6..bae1c7b50e 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 @@ -83,7 +83,7 @@ shortTitle: View contributions ![プロフィール上のアクティビティオーバービューセクション](/assets/images/help/profile/activity-overview-section.png) -アクティビティの概要に記載されている Organization は、Organization 内でのアクティビティの程度に応じて優先順位が付けられています。 プロフィール略歴で Organization に @メンションしており、あなたが Organization のメンバーである場合、その Organization がアクティビティの概要で最優先されます。 詳細は「[人や Team のメンション](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)」または「[プロフィールに略歴を追加する](/articles/adding-a-bio-to-your-profile/)」を参照してください。 +アクティビティの概要に記載されている Organization は、Organization 内でのアクティビティの程度に応じて優先順位が付けられています。 プロフィール略歴で Organization に @メンションしており、あなたが Organization のメンバーである場合、その Organization がアクティビティの概要で最優先されます。 For more information, see "[Mentioning people and teams](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)” or "[Adding a bio to your profile](/articles/adding-a-bio-to-your-profile/)." ## コントリビューションアクティビティ @@ -91,15 +91,14 @@ shortTitle: View contributions ![コントリビューションアクティビティ時間フィルター](/assets/images/help/profile/contributions_activity_time_filter.png) -{% ifversion not ghae %} -## {% data variables.product.prodname_dotcom_the_website %} 上の {% data variables.product.product_location_enterprise %} からコントリビューションを表示する +{% ifversion fpt or ghes or ghae-next %} + +## {% data variables.product.prodname_dotcom_the_website %} 上の {% data variables.product.prodname_enterprise %} からコントリビューションを表示する + +If you use {% ifversion fpt %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae-next %} 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)." -サイト管理者が、{% data variables.product.prodname_unified_contributions %} を有効にしている場合、{% data variables.product.prodname_enterprise %} コントリビューションカウントを {% data variables.product.prodname_dotcom_the_website %} プロフィールに送信できます。 詳細は「[{% data variables.product.prodname_ghe_server %} コントリビューションを {% data variables.product.prodname_dotcom_the_website %} に送信する](/articles/sending-your-github-enterprise-server-contributions-to-your-github-com-profile)」を参照してください。 {% endif %} ## 参考リンク - [プロフィールページ上にコントリビューションを表示する](/articles/viewing-contributions-on-your-profile-page) -- [プロフィール上でコントリビューションが表示されない理由](/articles/why-are-my-contributions-not-showing-up-on-my-profile) -- [プロフィールでプライベートコントリビューションを公開または非表示にする](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile) -- [プロフィール上にアクティビティの概要を表示する](/articles/showing-an-overview-of-your-activity-on-your-profile) diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md index d00febfccd..215f5e4ce2 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md @@ -24,6 +24,8 @@ Organization が所有するリポジトリは、細やかなアクセスを許 {% ifversion fpt %} +If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you can only invite other members of your enterprise to collaborate with you. {% data reusables.enterprise-accounts.emu-more-info-account %} + {% note %} **メモ:** {% data variables.product.company_short %} では、24 時間以内にリポジトリに招待できる人数に上限があります。 この上限を超える場合は、24 時間待つか、コラボレーションする人数の多い Organization を作成してください。 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-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md index 98bd53094d..72c857bfcc 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-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md @@ -18,7 +18,9 @@ shortTitle: Add an email address {% note %} -**参考**:{% data reusables.user_settings.no-verification-disposable-emails %} +設定ファイルでクエリスイートを指定すると、{% data variables.product.prodname_codeql %} 分析エンジンは、デフォルトのクエリセットに加えて、スイートに含まれるクエリを実行します。 + - {% data reusables.user_settings.no-verification-disposable-emails %} + - If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you cannot make changes to your email address on {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.emu-more-info-account %} {% endnote %} 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-github-user-account/managing-user-account-settings/changing-your-github-username.md index a5149bfc62..d8d93f8289 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-github-user-account/managing-user-account-settings/changing-your-github-username.md @@ -31,6 +31,12 @@ If you do not hold a trademark for the name, you can choose another username or - 古いユーザ名を使用する [@メンション](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) - 古いユーザ名を含む [Gist](/articles/creating-gists) にリンクする +{% ifversion fpt %} + +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 %} + ## リポジトリ参照 ユーザ名を変更した後、{% data variables.product.product_name %} は自動的にあなたのリポジトリへの参照をリダイレクトします。 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-github-user-account/managing-user-account-settings/index.md index 149c065246..f6715c17cb 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-github-user-account/managing-user-account-settings/index.md @@ -15,6 +15,7 @@ topics: children: - /about-your-personal-dashboard - /managing-your-theme-settings + - /managing-your-tab-size-rendering-preference - /changing-your-github-username - /merging-multiple-user-accounts - /converting-a-user-into-an-organization diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md new file mode 100644 index 0000000000..11a0636ca9 --- /dev/null +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md @@ -0,0 +1,15 @@ +--- +title: Managing your tab size rendering preference +intro: You can manage the number of spaces a tab is equal to for your user account. +versions: + fpt: '*' +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. [User settings] サイドバーで、[**Appearance**] をクリックします。 ![[User settings] サイドバーの [Appearance] タブ](/assets/images/help/settings/appearance-tab.png) +2. Under "Tab size preference", select the drop-down menu and choose your preference. ![Tab size preference button](/assets/images/help/settings/tab-size-preference.png) diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md index 09b5b4527d..10fd6d3d60 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md @@ -3,6 +3,7 @@ title: テーマ設定を管理する 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: next ghes: '>=3.2' topics: - Accounts @@ -14,7 +15,15 @@ shortTitle: Manage theme settings {% data variables.product.product_name %} を使用時期と使用方法を選択して柔軟性を高めるために、テーマ設定をして {% data variables.product.product_name %} の外観を変更できます。 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 ghae-issue-4618 %} People with visual impairment may benefit from the dark high contrast theme, with greater contrast between foreground and background elements.{% endif %} +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 ghae-issue-4618 %} 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 %} If you have colorblindness, you may benefit from our light and dark colorblind themes. + +{% note %} + +**Note:** The colorblind themes are currently in public beta. For more information on enabling features in public beta, see "[Exploring early access releases with feature preview](/get-started/using-github/exploring-early-access-releases-with-feature-preview)." + +{% endnote %}{% endif %} {% data reusables.user_settings.access_settings %} 1. [User settings] サイドバーで、[**Appearance**] をクリックします。 ![[User settings] サイドバーの [Appearance] タブ](/assets/images/help/settings/appearance-tab.png) @@ -24,6 +33,8 @@ You may want to use a dark theme to reduce power consumption on certain devices, {% ifversion fpt or ghae-issue-4618 %}![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 ghae-issue-4618 %}![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 ghae-issue-4619 %} + - 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/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 index 15b55e765d..a0ada3dd01 100644 --- 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 @@ -35,7 +35,7 @@ shortTitle: Permission user repositories | {% ifversion fpt %}コラボレータを招待{% else %}コラボレータを追加{% endif %} | | | [個人リポジトリへのコラボレータの招待](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository) | | | リポジトリの表示変更 | 「[リポジトリの可視性を設定する](/github/administering-a-repository/setting-repository-visibility)」 |{% ifversion fpt %} -| リポジトリとのインタラクションの制限 | 「[リポジトリでのインタラクションを制限する](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)」 |{% endif %}{% ifversion fpt or ghes > 3.0 %} +| リポジトリとのインタラクションの制限 | 「[リポジトリでのインタラクションを制限する](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)」 |{% endif %}{% ifversion fpt or ghes > 3.0 or ghae-next %} | デフォルトブランチを含むブランチ名の変更 | 「[ブランチ名を変更する](/github/administering-a-repository/renaming-a-branch)」 {% endif %} | 保護されたブランチで、レビューの承認がなくてもプルリクエストをマージする | [保護されたブランチについて](/github/administering-a-repository/about-protected-branches) | @@ -73,7 +73,7 @@ shortTitle: Permission user repositories | アクション | 詳細情報 | |:------------------------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| リポジトリのフォーク | 「[フォークについて](/github/collaborating-with-issues-and-pull-requests/about-forks)」 |{% ifversion fpt or ghes > 3.1 %} +| リポジトリのフォーク | 「[フォークについて](/github/collaborating-with-issues-and-pull-requests/about-forks)」 |{% ifversion fpt or ghes > 3.1 or ghae-next %} | デフォルトブランチ以外のブランチ名の変更 | 「[ブランチ名を変更する](/github/administering-a-repository/renaming-a-branch)」 {% endif %} | リポジトリ内のコミット、プルリクエスト、Issue に関するコメントの作成、編集、削除 |
    • 「[About issues](/github/managing-your-work-on-github/about-issues)」
    • 「[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)」
    • "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"
    | diff --git a/translations/ja-JP/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md b/translations/ja-JP/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md index b4c567da88..42179832bc 100644 --- a/translations/ja-JP/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md +++ b/translations/ja-JP/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md @@ -15,8 +15,6 @@ topics: - Workflows --- -{% data reusables.actions.ae-beta %} - ## ワークフローの依存関係のキャッシングについて ワークフローの実行は、しばしば他の実行と同じ出力あるいはダウンロードされた依存関係を再利用します。 たとえばMaven、Gradle、npm、Yarnといったパッケージ及び依存関係管理ツールは、ダウンロードされた依存関係のローカルキャッシュを保持します。 diff --git a/translations/ja-JP/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md b/translations/ja-JP/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md index be6e898cc5..f937f4b02c 100644 --- a/translations/ja-JP/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md +++ b/translations/ja-JP/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md @@ -20,11 +20,10 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## ワークフローの成果物について -成果物を使えば、ジョブの完了後にデータを永続化でき、そのデータを同じワークフロー中の他のジョブと共有できます。 成果物とは、ワークフロー実行中に生成されるファイル、またはファイルのコレクションです。 たとえば、ワークフローの実行が終了した後、成果物を使ってビルドとテストの出力を保存しておけます。 +成果物を使えば、ジョブの完了後にデータを永続化でき、そのデータを同じワークフロー中の他のジョブと共有できます。 成果物とは、ワークフロー実行中に生成されるファイル、またはファイルのコレクションです。 たとえば、ワークフローの実行が終了した後、成果物を使ってビルドとテストの出力を保存しておけます。 {% data reusables.actions.reusable-workflow-artifacts %} {% data reusables.github-actions.artifact-log-retention-statement %} プルリクエストの保持期間は、ユーザが新しいコミットをプルリクエストにプッシュするたびに再開されます。 diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/about-continuous-integration.md b/translations/ja-JP/content/actions/automating-builds-and-tests/about-continuous-integration.md index cddb0790c0..bda1e99ee6 100644 --- a/translations/ja-JP/content/actions/automating-builds-and-tests/about-continuous-integration.md +++ b/translations/ja-JP/content/actions/automating-builds-and-tests/about-continuous-integration.md @@ -1,6 +1,6 @@ --- title: 継続的インテグレーションについて -intro: '{% data variables.product.prodname_actions %} で {% data variables.product.prodname_dotcom %} リポジトリにカスタム継続的インテグレーション（CI）ワークフローと継続的デプロイメント（CD）ワークフローを直接作成できます。' +intro: 'You can create custom continuous integration (CI) workflows directly in your {% data variables.product.prodname_dotcom %} repository with {% data variables.product.prodname_actions %}.' product: '{% data reusables.gated-features.actions %}' redirect_from: - /articles/about-continuous-integration @@ -15,13 +15,11 @@ versions: type: overview topics: - CI - - CD shortTitle: 継続的インテグレーション --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 継続的インテグレーションについて @@ -49,45 +47,12 @@ CI ワークフローは、{% data variables.product.product_name %} イベン 一般的な用語の定義については「[{% data variables.product.prodname_actions %} の中核的概念](/github/automating-your-workflow-with-github-actions/core-concepts-for-github-actions)」を参照してください。 -## サポートされている言語 - +## Workflow templates {% data variables.product.product_name %} では、各種言語およびフレームワークに応じて CI ワークフローテンプレートが提供されます。 {% data variables.product.product_location %} 上の {% ifversion fpt %}[actions/starter-workflows](https://github.com/actions/starter-workflows/tree/main/ci) リポジトリ{% else %} `actions/starter-workflows` リポジトリで {% data variables.product.product_name %} が提供する CI ワークフローテンプレートの完全なリストを参照します。{% endif %} -{% ifversion fpt or ghes > 3.0 or ghae-next %} -## ワークフロー実行をスキップする - -ワークフローがトリガーされないようにする場合は、コミットメッセージにスキップ命令を追加できます。 `on: push` または `on: pull_request` でトリガーされるワークフローは、プッシュまたはプルリクエストの HEAD コミットで、次の文字列型のいずれかをコミットメッセージに追加した場合トリガーされません。 - -* `[skip ci]` -* `[ci skip]` -* `[no ci]` -* `[skip actions]` -* `[actions skip]` - -または、コミットメッセージを 2 行の空行で終了し、その後に `skip-checks: true` または `skip-checks:true` のいずれかを続けることもできます。 - -最初にリポジトリがパスするための特定のチェックを受けるように設定されている場合、プルリクエストをマージすることはできません。 プルリクエストをマージできるようにするには、コミットメッセージのスキップ命令なしでプルリクエストに新しいコミットをプッシュできます。 - -{% note %} - -**注釈:** スキップ命令は、`push` および `pull_request` イベントにのみ適用されます。 たとえば、コミットメッセージに `[skip ci]` を追加しても、`on: pull_request_target` でトリガーされたワークフロー実行は停止されません。 - -{% endnote %} -{% endif %} - -## ワークフロー実行の通知 - -{% data reusables.repositories.workflow-notifications %} - -## ワークフロー実行のためのステータスバッジ - -{% 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)." - ## 参考リンク {% ifversion fpt %} diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md index b53096b176..ad410011f6 100644 --- a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md +++ b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md @@ -19,7 +19,6 @@ shortTitle: Build & test Java & Ant {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## はじめに diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md index 5586e879e8..549fb53e57 100644 --- a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md +++ b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md @@ -19,7 +19,6 @@ shortTitle: Build & test Java & Gradle {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## はじめに diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md index 7356bbd95c..4d06e68cf4 100644 --- a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md +++ b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md @@ -19,7 +19,6 @@ shortTitle: Build & test Java with Maven {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## はじめに diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-net.md b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-net.md index 73565b62b2..31b0082de2 100644 --- a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-net.md +++ b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-net.md @@ -13,7 +13,6 @@ shortTitle: Build & test .NET {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## はじめに 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 ffdd587474..8b195bdfba 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 @@ -22,7 +22,6 @@ hasExperimentalAlternative: true {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## はじめに diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-powershell.md b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-powershell.md index bd3cb6da5c..8c2288fca2 100644 --- a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-powershell.md +++ b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-powershell.md @@ -19,7 +19,6 @@ shortTitle: Build & test PowerShell {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-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 cc3e3bb574..8d7b5e8dd7 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 @@ -21,7 +21,6 @@ hasExperimentalAlternative: true {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## はじめに diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-ruby.md b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-ruby.md index 4108a5c7bf..74cfd66a45 100644 --- a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-ruby.md +++ b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-ruby.md @@ -17,7 +17,6 @@ shortTitle: Build & test Ruby {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## はじめに diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-swift.md b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-swift.md index 5cedfef8c9..c2164a3aae 100644 --- a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-swift.md +++ b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-swift.md @@ -17,7 +17,6 @@ shortTitle: Build & test Swift {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## はじめに diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md index 45cc380f48..83cd66b16d 100644 --- a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md +++ b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md @@ -21,7 +21,6 @@ shortTitle: Build & test Xamarin apps {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## はじめに diff --git a/translations/ja-JP/content/actions/creating-actions/about-custom-actions.md b/translations/ja-JP/content/actions/creating-actions/about-custom-actions.md index 23c52584e9..ddedeab209 100644 --- a/translations/ja-JP/content/actions/creating-actions/about-custom-actions.md +++ b/translations/ja-JP/content/actions/creating-actions/about-custom-actions.md @@ -20,7 +20,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About custom actions diff --git a/translations/ja-JP/content/actions/creating-actions/creating-a-composite-action.md b/translations/ja-JP/content/actions/creating-actions/creating-a-composite-action.md index 2601c53d3c..16eca6961a 100644 --- a/translations/ja-JP/content/actions/creating-actions/creating-a-composite-action.md +++ b/translations/ja-JP/content/actions/creating-actions/creating-a-composite-action.md @@ -16,7 +16,6 @@ shortTitle: Composite action {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## はじめに diff --git a/translations/ja-JP/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/ja-JP/content/actions/creating-actions/creating-a-docker-container-action.md index c79115ae04..7e444671e1 100644 --- a/translations/ja-JP/content/actions/creating-actions/creating-a-docker-container-action.md +++ b/translations/ja-JP/content/actions/creating-actions/creating-a-docker-container-action.md @@ -20,7 +20,6 @@ shortTitle: Docker container action {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## はじめに diff --git a/translations/ja-JP/content/actions/creating-actions/creating-a-javascript-action.md b/translations/ja-JP/content/actions/creating-actions/creating-a-javascript-action.md index 9904ca57fa..b868a8f9e8 100644 --- a/translations/ja-JP/content/actions/creating-actions/creating-a-javascript-action.md +++ b/translations/ja-JP/content/actions/creating-actions/creating-a-javascript-action.md @@ -20,7 +20,6 @@ shortTitle: JavaScript action {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## はじめに diff --git a/translations/ja-JP/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/translations/ja-JP/content/actions/creating-actions/dockerfile-support-for-github-actions.md index 22f1fee920..c6c10f646e 100644 --- a/translations/ja-JP/content/actions/creating-actions/dockerfile-support-for-github-actions.md +++ b/translations/ja-JP/content/actions/creating-actions/dockerfile-support-for-github-actions.md @@ -14,7 +14,6 @@ type: reference {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Dockerfileの命令について @@ -22,7 +21,7 @@ type: reference ## Dockerfileの命令とオーバーライド -Dockerの命令の中にはGitHub Actionと関わるものがあり、アクションのメタデータファイルはDockerの命令のいくつかをオーバーライドできます。 予期しない動作を避けるために、Dockerfileが{% data variables.product.prodname_actions %}とどのように関わるかについて馴染んでおいてください。 +Dockerの命令の中にはGitHub Actionsと関わるものがあり、アクションのメタデータファイルはDockerの命令のいくつかをオーバーライドできます。 予期しない動作を避けるために、Dockerfileが{% data variables.product.prodname_actions %}とどのように関わるかについて馴染んでおいてください。 ### USER @@ -77,7 +76,7 @@ ENTRYPOINT ["/entrypoint.sh"] #### *entrypoint.sh*ファイルの例 -上のDockerfileを使って、{% data variables.product.product_name %}はアクションのメタデータファイルに設定された`args`を、`entrypoint.sh`の引数として送ります。 `#!/bin/sh`[シバン](https://ja.wikipedia.org/wiki/シバン_(Unix))を`entrypoint.sh`ファイルの先頭に追加し、システムの[POSIX](https://ja.wikipedia.org/wiki/POSIX)準拠のシェルを明示的に使ってください。 +上のDockerfileを使って、{% data variables.product.product_name %}はアクションのメタデータファイルに設定された`args`を、`entrypoint.sh`の引数として送ります。 Add the `#!/bin/sh` [shebang](https://en.wikipedia.org/wiki/Shebang_(Unix)) at the top of the `entrypoint.sh` file to explicitly use the system's [POSIX](https://en.wikipedia.org/wiki/POSIX)-compliant shell. ``` sh #!/bin/sh diff --git a/translations/ja-JP/content/actions/creating-actions/index.md b/translations/ja-JP/content/actions/creating-actions/index.md index d64783a358..097d80d248 100644 --- a/translations/ja-JP/content/actions/creating-actions/index.md +++ b/translations/ja-JP/content/actions/creating-actions/index.md @@ -24,4 +24,3 @@ children: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} 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 5fe047dc00..29a5271583 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 @@ -17,7 +17,6 @@ type: reference {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## {% data variables.product.prodname_actions %}のYAML構文について @@ -27,19 +26,19 @@ Docker及びJavaScriptアクションにはメタデータファイルが必要 ## `name` -**必須**アクションの名前。 {% data variables.product.prodname_dotcom %}は`name`を**Actions**タブに表示して、それぞれのジョブのアクションを見て区別しやすくします。 +**Required** The name of your action. {% data variables.product.prodname_dotcom %} displays the `name` in the **Actions** tab to help visually identify actions in each job. ## `作者` -**オプション** アクションの作者の名前。 +**Optional** The name of the action's author. ## `説明` -**必須** アクションの短い説明。 +**Required** A short description of the action. ## `inputs` -**オプション** inputsパラメーターを使うと、アクションが実行時に使うデータを指定できます。 {% data variables.product.prodname_dotcom %}は、inputsパラメータを環境変数として保存します。 大文字が使われているInputsのidは、実行時に小文字に変換されます。 inputsのidには小文字を使うことをおすすめします。 +**Optional** Input parameters allow you to specify data that the action expects to use during runtime. {% data variables.product.prodname_dotcom %}は、inputsパラメータを環境変数として保存します。 大文字が使われているInputsのidは、実行時に小文字に変換されます。 inputsのidには小文字を使うことをおすすめします。 ### サンプル @@ -66,19 +65,19 @@ To access the environment variable in a Docker container action, you must pass t ### `inputs.` -**必須** `文字列型`の識別子で、入力と結びつけられます。 ``の値は、入力のメタデータのマップです。 ``は、`inputs`オブジェクト内でユニークな識別子でなければなりません。 ``は、文字あるいは`_`で始める必要があり、英数字、`-`、`_`しか使用できません。 +**Required** A `string` identifier to associate with the input. ``の値は、入力のメタデータのマップです。 ``は、`inputs`オブジェクト内でユニークな識別子でなければなりません。 ``は、文字あるいは`_`で始める必要があり、英数字、`-`、`_`しか使用できません。 ### `inputs..description` -**必須** 入力パラメーターの`文字列`での説明。 +**Required** A `string` description of the input parameter. ### `inputs..required` -**必須** この入力パラメーターがアクションに必須かどうかを示す`論理値`。 パラメーターが必須の場合は`true`に設定してください。 +**Required** A `boolean` to indicate whether the action requires the input parameter. パラメーターが必須の場合は`true`に設定してください。 ### `inputs..default` -**オプション** デフォルト値を示す`文字列`。 デフォルト値は、入力パラメーターがワークフローファイルで指定されなかった場合に使われます。 +**Optional** A `string` representing the default value. デフォルト値は、入力パラメーターがワークフローファイルで指定されなかった場合に使われます。 ### `inputs..deprecationMessage` @@ -100,11 +99,11 @@ outputs: ### `outputs.` -**必須** `文字列型`の識別子で、出力と結びつけられます。 ``の値は、出力のメタデータのマップです。 ``は、`outputs`オブジェクト内でユニークな識別子でなければなりません。 ``は、文字あるいは`_`で始める必要があり、英数字、`-`、`_`しか使用できません。 +**Required** A `string` identifier to associate with the output. ``の値は、出力のメタデータのマップです。 ``は、`outputs`オブジェクト内でユニークな識別子でなければなりません。 ``は、文字あるいは`_`で始める必要があり、英数字、`-`、`_`しか使用できません。 ### `outputs..description` -**必須** 出力パラメーターの`文字列`での説明。 +**Required** A `string` description of the output parameter. ## `outputs` for composite actions @@ -155,7 +154,7 @@ runs: ### `pre` -**オプション** `main:`アクションが開始される前の、ジョブの開始時点でスクリプトを実行できるようにします。 たとえば、`pre:`を使って必要なセットアップスクリプトを実行できます。 [`using`](#runsusing)構文を使って指定されたアプリケーションがこのファイルを実行します。 `pre:`アクションはデフォルトで常に実行されますが、[`pre-if`](#pre-if)を使ってこれをオーバーライドすることができます。 +**オプション** `main:`アクションが開始される前の、ジョブの開始時点でスクリプトを実行できるようにします。 たとえば、`pre:`を使って必要なセットアップスクリプトを実行できます。 The application specified with the [`using`](#runsusing) syntax will execute this file. `pre:`アクションはデフォルトで常に実行されますが、[`pre-if`](#pre-if)を使ってこれをオーバーライドすることができます。 この例では、`pre:`アクションは`setup.js`というスクリプトを実行します。 @@ -180,7 +179,7 @@ runs: ### `post` -**オプション** `main:`アクションの終了後、ジョブの終わりにスクリプトを実行できるようにします。 たとえば、`post:`を使って特定のプロセスを終了させたり、不要なファイルを削除したりできます。 [`using`](#runsusing)構文を使って指定されたアプリケーションがこのファイルを実行します。 +**オプション** `main:`アクションの終了後、ジョブの終わりにスクリプトを実行できるようにします。 たとえば、`post:`を使って特定のプロセスを終了させたり、不要なファイルを削除したりできます。 The application specified with the [`using`](#runsusing) syntax will execute this file. この例では、`post:`アクションは`cleanup.js`というスクリプトを実行します。 @@ -284,7 +283,7 @@ Git ref、SHA、またはDockerタグ番号を指定して、使用している - 特定のメジャーアクションバージョンを使用すると、互換性を維持したまま重要な修正とセキュリティパッチを受け取ることができます。 ワークフローが引き続き動作することも保証できます。 - アクションのデフォルトブランチを使用すると便利なこともありますが、別のユーザが破壊的変更を加えた新しいメジャーバージョンをリリースすると、ワークフローが動作しなくなる場合があります。 -入力が必要なアクションもあり、入力を[`with`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepswith)キーワードを使って設定する必要があります。 必要な入力を判断するには、アクションのREADMEファイルをお読みください。 +Some actions require inputs that you must set using the [`with`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepswith) keyword. 必要な入力を判断するには、アクションのREADMEファイルをお読みください。 ```yaml runs: @@ -353,7 +352,7 @@ runs: **オプション** `entrypoint`アクションが始まる前にスクリプトを実行できるようにしてくれます。 たとえば、`pre-entrypoint:`を使って必要なセットアップスクリプトを実行できます。 {% data variables.product.prodname_actions %}は`docker run`を使ってこのアクションを起動し、同じベースイメージを使う新しいコンテナ内でスクリプトを実行します。 これはすなわち、ランタイムの状態はメインの`entrypoint`コンテナとは異なるということで、必要な状態はワークスペースや`HOME`内、あるいは`STATE_`変数としてアクセスしなければなりません。 `pre-entrypoint:`アクションはデフォルトで常に実行されますが、[`pre-if`](#pre-if)を使ってこれをオーバーライドすることができます。 -[`using`](#runsusing)構文を使って指定されたアプリケーションがこのファイルを実行します。 +The application specified with the [`using`](#runsusing) syntax will execute this file. この例では、`pre-entrypoint:`アクションは`setup.sh`というスクリプトを実行します。 diff --git a/translations/ja-JP/content/actions/creating-actions/publishing-actions-in-github-marketplace.md b/translations/ja-JP/content/actions/creating-actions/publishing-actions-in-github-marketplace.md index 71555ac0e4..70aa1a76ad 100644 --- a/translations/ja-JP/content/actions/creating-actions/publishing-actions-in-github-marketplace.md +++ b/translations/ja-JP/content/actions/creating-actions/publishing-actions-in-github-marketplace.md @@ -12,8 +12,6 @@ type: how_to shortTitle: Publish in GitHub Marketplace --- -{% data reusables.actions.ae-beta %} - {% data variables.product.prodname_marketplace %}でアクションを公開するには、利用規約に同意していなければなりません。 ## アクションの公開について diff --git a/translations/ja-JP/content/actions/creating-actions/setting-exit-codes-for-actions.md b/translations/ja-JP/content/actions/creating-actions/setting-exit-codes-for-actions.md index aec8862bb9..8ed68b4a52 100644 --- a/translations/ja-JP/content/actions/creating-actions/setting-exit-codes-for-actions.md +++ b/translations/ja-JP/content/actions/creating-actions/setting-exit-codes-for-actions.md @@ -14,7 +14,6 @@ type: how_to {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 終了コードについて @@ -41,7 +40,7 @@ try { ## Docker コンテナアクションで失敗終了コードを設定する -Docker コンテナアクションを作成している場合、失敗終了コードを `entrypoint.sh` スクリプトに設定できます。 例: +Docker コンテナアクションを作成している場合、失敗終了コードを `entrypoint.sh` スクリプトで設定できます。 例: ``` if ; then diff --git a/translations/ja-JP/content/actions/deployment/about-continuous-deployment.md b/translations/ja-JP/content/actions/deployment/about-continuous-deployment.md new file mode 100644 index 0000000000..e2dd694634 --- /dev/null +++ b/translations/ja-JP/content/actions/deployment/about-continuous-deployment.md @@ -0,0 +1,41 @@ +--- +title: About continuous deployment +intro: 'You can create custom continuous deployment (CD) workflows directly in your {% data variables.product.prodname_dotcom %} repository with {% data variables.product.prodname_actions %}.' +product: '{% data reusables.gated-features.actions %}' +versions: + fpt: '*' + ghes: '*' + ghae: '*' +type: overview +topics: + - CD +shortTitle: Continuous deployment +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +## About continuous deployment + +_Continuous deployment_ (CD) is the practice of using automation to publish and deploy software updates. As part of the typical CD process, the code is automatically built and tested before deployment. + +Continuous deployment is often coupled with continuous integration. For more information about continuous integration, see "[About continuous integration](/actions/guides/about-continuous-integration)". + +## About continuous deployment using {% data variables.product.prodname_actions %} + +You can set up a {% data variables.product.prodname_actions %} workflow to deploy your software product. To verify that your product works as expected, your workflow can build the code in your repository and run your tests before deploying. + +You can configure your CD workflow to run when a {% data variables.product.product_name %} event occurs (for example, when new code is pushed to the default branch of your repository), on a set schedule, manually, or when an external event occurs using the repository dispatch webhook. For more information about when your workflow can run, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)." + +{% data variables.product.prodname_actions %} provides features that give you more control over deployments. For example, you can use environments to require approval for a job to proceed, restrict which branches can trigger a workflow, or limit access to secrets. You can use concurrency to limit your CD pipeline to a maximum of one in-progress deployment and one pending deployment. For more information about these features, see "[Deploying with GitHub Actions](/actions/deployment/deploying-with-github-actions)" and "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." + +## Workflow templates and third party actions + +{% data reusables.actions.cd-templates-actions %} + +## 参考リンク + +- [Deploying with GitHub Actions](/actions/deployment/deploying-with-github-actions) +- [Using environments for deployment](/actions/deployment/using-environments-for-deployment){% ifversion fpt %} +- 「[{% data variables.product.prodname_actions %} の支払いを管理する](/billing/managing-billing-for-github-actions)」 +{% endif %} diff --git a/translations/ja-JP/content/actions/deployment/deploying-to-amazon-elastic-container-service.md b/translations/ja-JP/content/actions/deployment/deploying-to-amazon-elastic-container-service.md index 470f99493e..df3847f304 100644 --- a/translations/ja-JP/content/actions/deployment/deploying-to-amazon-elastic-container-service.md +++ b/translations/ja-JP/content/actions/deployment/deploying-to-amazon-elastic-container-service.md @@ -18,11 +18,10 @@ shortTitle: Deploy to Amazon ECS {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## はじめに -このガイドは、{% data variables.product.prodname_actions %}を使ってコンテナ化されたアプリケーションをビルドし、それを[Amazon Elastic Container Registry (ECR)](https://aws.amazon.com/ecr/)にプッシュし、[Amazon Elastic Container Service (ECS)](https://aws.amazon.com/ecs/)にデプロイする方法を説明します。 +This guide explains how to use {% data variables.product.prodname_actions %} to build a containerized application, push it to [Amazon Elastic Container Registry (ECR)](https://aws.amazon.com/ecr/), and deploy it to [Amazon Elastic Container Service (ECS)](https://aws.amazon.com/ecs/) when a release is created. {% data variables.product.company_short %}リポジトリへの新しいリリースごとに、{% data variables.product.prodname_actions %}ワークフローは新しいコンテナイメージをビルドし、Amazon ECRにプッシュし、そして新しいタスクの定義をAmazon ECSにデプロイします。 @@ -66,6 +65,8 @@ shortTitle: Deploy to Amazon ECS IAMユーザに推奨されるIAMポリシー及びアクセスキーの認証情報を処理するメソッドについては、以下で使われている各アクションのドキュメンテーションを参照してください。 +5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %} + ## Creating the workflow Once you've completed the prerequisites, you can proceed with creating the workflow. @@ -74,6 +75,8 @@ Once you've completed the prerequisites, you can proceed with creating the workf ワークフローの`env`キー内のすべての変数について、自分の値を渡すようにしてください。 +{% data reusables.actions.delete-env-key %} + ```yaml{:copy} {% data reusables.actions.actions-not-certified-by-github-comment %} @@ -93,17 +96,11 @@ env: CONTAINER_NAME: MY_CONTAINER_NAME # set this to the name of the container in the # containerDefinitions section of your task definition -defaults: - run: - shell: bash - jobs: deploy: name: Deploy - runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae-next %} - permissions: - packages: write - contents: read{% endif %} + runs-on: ubuntu-latest + environment: production {% raw %}steps: - name: Checkout @@ -150,9 +147,10 @@ jobs: wait-for-service-stability: true{% endraw %} ``` - ## 追加リソース +For the original starter workflow, see [`aws.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/aws.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository. + この例で使われているサービスに関する詳しい情報については、以下のドキュメンテーションを参照してください。 * Amazon AWSドキュメンテーションの「[IAM でのセキュリティのベストプラクティス](https://docs.aws.amazon.com/ja_jp/IAM/latest/UserGuide/best-practices.html)」 diff --git a/translations/ja-JP/content/actions/deployment/deploying-to-azure-app-service.md b/translations/ja-JP/content/actions/deployment/deploying-to-azure-app-service.md index 9a73682e73..0bda490f8f 100644 --- a/translations/ja-JP/content/actions/deployment/deploying-to-azure-app-service.md +++ b/translations/ja-JP/content/actions/deployment/deploying-to-azure-app-service.md @@ -18,7 +18,6 @@ shortTitle: Deploy to Azure App Service {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## はじめに @@ -68,13 +67,19 @@ Azure App Serviceではいくつかの言語でWebアプリケーションを動 {% data variables.product.prodname_dotcom %}リポジトリで、公開されたプロフィールの内容を含む`AZURE_WEBAPP_PUBLISH_PROFILE`という名前のシークレットを生成してください。 シークレットの作成に関する詳しい情報については「[暗号化されたシークレット](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)」を参照してください。 +4. For Linux apps, add an app setting called `WEBSITE_WEBDEPLOY_USE_SCM` and set it to true in your app. For more information, see "[Configure apps in the portal](https://docs.microsoft.com/en-us/azure/app-service/configure-common#configure-app-settings)" in the Azure documentation. + +5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %} + ## ワークフローの作成 必要な環境を整えたら、ワークフローの作成に進むことができます。 -以下の例のワークフローは、Node.jsのプロジェクトをビルド、テストし、Azure App Serviceへデプロイする方法を示します。 +The following example workflow demonstrates how to build, test, and deploy the Node.js project to Azure App Service when a release is created. -ワークフローの`env`キー中の`AZURE_WEBAPP_NAME`を、作成したWebアプリケーションの名前に設定してください。 +ワークフローの`env`キー中の`AZURE_WEBAPP_NAME`を、作成したWebアプリケーションの名前に設定してください。 You can also change `AZURE_WEBAPP_PACKAGE_PATH` if the path to your project is not the repository root and `NODE_VERSION` if you want to use a node version other than `10.x`. + +{% data reusables.actions.delete-env-key %} ```yaml{:copy} {% data reusables.actions.actions-not-certified-by-github-comment %} @@ -92,6 +97,8 @@ jobs: build-and-deploy: name: Build and Deploy runs-on: ubuntu-latest + environment: production + steps: - uses: actions/checkout@v2 @@ -122,4 +129,5 @@ jobs: * For the original starter workflow, see [`azure.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository. * 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. * Azure web appドキュメンテーション中の「[Azure で Node.js Web アプリを作成する](https://docs.microsoft.com/ja-jp/azure/app-service/quickstart-nodejs)」クイックスタートは、[Azure App Serviceエクステンション](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azureappservice)とともにVS Codeを利用する方法を示しています。 diff --git a/translations/ja-JP/content/actions/deployment/deploying-to-google-kubernetes-engine.md b/translations/ja-JP/content/actions/deployment/deploying-to-google-kubernetes-engine.md index 43cdfb02f3..932a3169ae 100644 --- a/translations/ja-JP/content/actions/deployment/deploying-to-google-kubernetes-engine.md +++ b/translations/ja-JP/content/actions/deployment/deploying-to-google-kubernetes-engine.md @@ -13,16 +13,15 @@ topics: - CD - Containers - Google Kubernetes Engine -shortTitle: Deploy to Kubernetes (GKE) +shortTitle: Deploy to Google Kubernetes Engine --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## はじめに -このガイドは、{% data variables.product.prodname_actions %}を使ってコンテナ化されたアプリケーションをビルドし、それをGoogle Container Registryにプッシュし、Google Kubernetes Engine (GKE)にデプロイする方法を説明します。 +This guide explains how to use {% data variables.product.prodname_actions %} to build a containerized application, push it to Google Container Registry (GCR), and deploy it to Google Kubernetes Engine (GKE) when a release is created. GKEはGoogle CloudによるマネージドなKubernetesクラスタサービスで、コンテナ化されたワークロードをクラウドもしくはユーザ自身のデータセンターでホストできます。 詳しい情報については[Google Kubernetes Engine](https://cloud.google.com/kubernetes-engine)を参照してください。 @@ -61,7 +60,7 @@ $ gcloud services enable \ ### サービスアカウントの設定と資格情報の保存 -この手順は、GKEインテグレーション用のサービスアカウントの作成方法を示します。 アカウントの作成、アカウントへのロールの追加、アカウントのキーの取得、それらの`GKE_SA_KEY`という名前のbase64エンコードされた[暗号化されたリポジトリシークレット](/actions/reference/encrypted-secrets)としての保存の方法を説明します。 +この手順は、GKEインテグレーション用のサービスアカウントの作成方法を示します。 It explains how to create the account, add roles to it, retrieve its keys, and store them as a base64-encoded encrypted repository secret named `GKE_SA_KEY`. 1. 新しいサービスアカウントを作成してください。 {% raw %} @@ -97,16 +96,29 @@ $ gcloud services enable \ $ export GKE_SA_KEY=$(cat key.json | base64) ``` {% endraw %} + For more information about how to store a secret, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)." + +### Storing your project name + +Store the name of your project as a secret named `GKE_PROJECT`. For more information about how to store a secret, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)." ### （オプション）kustomizeの設定 Kustomizeは、YAML仕様を管理するために使われるオプションのツールです。 _kustomization_ ファイルの作成後、以下のワークフローを使用して、イメージのフィールドを動的に設定し、結果を `kubectl` にパイプすることができます。 詳しい情報については、「[kustomize の使い方](https://github.com/kubernetes-sigs/kustomize#usage)」を参照してください。 +### (Optional) Configure a deployment environment + +{% data reusables.actions.about-environments %} + ## ワークフローの作成 必要な環境を整えたら、ワークフローの作成に進むことができます。 以下のワークフロー例は、コンテナイメージを作成して GCR にプッシュする方法を示しています。 次に、Kubernetes ツール（`kubectl` や `kustomize` など）を使用して、イメージをクラスタデプロイメントにプルします。 +Under the `env` key, change the value of `GKE_CLUSTER` to the name of your cluster, `GKE_ZONE` to your cluster zone, `DEPLOYMENT_NAME` to the name of your deployment, and `IMAGE` to the name of your image. + +{% data reusables.actions.delete-env-key %} + ```yaml{:copy} {% data reusables.actions.actions-not-certified-by-github-comment %} @@ -127,8 +139,9 @@ jobs: setup-build-publish-deploy: name: Setup, Build, Publish, and Deploy runs-on: ubuntu-latest - steps: + environment: production + steps: - name: Checkout uses: actions/checkout@v2 @@ -138,7 +151,8 @@ jobs: service_account_key: {% raw %}${{ secrets.GKE_SA_KEY }}{% endraw %} project_id: {% raw %}${{ secrets.GKE_PROJECT }}{% endraw %} - # Configure docker to use the gcloud command-line tool as a credential helper + # Configure Docker to use the gcloud command-line tool as a credential + # helper for authentication - run: |- gcloud --quiet auth configure-docker @@ -158,18 +172,18 @@ jobs: --build-arg GITHUB_REF="$GITHUB_REF" \ . - # Push the Docker image to Google Container Registry + # Docker イメージを Google Container Registry にプッシュする - name: Publish run: |- docker push "gcr.io/$PROJECT_ID/$IMAGE:$GITHUB_SHA" - # Set up kustomize + # kustomize を設定する - name: Set up Kustomize run: |- - curl --location https://github.com/kubernetes-sigs/kustomize/releases/download/kustomize%2Fv4.2.0/kustomize_v4.2.0_linux_amd64.tar.gz | tar xz + curl -sfLo kustomize https://github.com/kubernetes-sigs/kustomize/releases/download/v3.1.0/kustomize_3.1.0_linux_amd64 chmod u+x ./kustomize - # Deploy the Docker image to the GKE cluster + # Docker イメージを GKE クラスタにデプロイする - name: Deploy run: |- ./kustomize edit set image gcr.io/PROJECT_ID/IMAGE:TAG=gcr.io/$PROJECT_ID/$IMAGE:$GITHUB_SHA diff --git a/translations/ja-JP/content/actions/deployment/deploying-with-github-actions.md b/translations/ja-JP/content/actions/deployment/deploying-with-github-actions.md new file mode 100644 index 0000000000..0bfea57fab --- /dev/null +++ b/translations/ja-JP/content/actions/deployment/deploying-with-github-actions.md @@ -0,0 +1,173 @@ +--- +title: Deploying with GitHub Actions +intro: Learn how to control deployments with features like environments and concurrency. +product: '{% data reusables.gated-features.actions %}' +versions: + fpt: '*' + ghes: '>=3.1' + ghae: '*' +type: overview +topics: + - CD +shortTitle: Deploy with GitHub Actions +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +## はじめに + +{% data variables.product.prodname_actions %} offers features that let you control deployments. You can: + +- 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)." + +## 必要な環境 + +You should be familiar with the syntax for {% data variables.product.prodname_actions %}. 詳しい情報については、「[{% 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`, `release`, and `workflow_dispatch`. + +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. +- A release is created. +- Someone manually triggers it. + +```yaml +on: + push: + branches: + - main + pull_request: + branches: + - main + release: + types: + - created + workflow_dispatch: +``` + +詳しい情報については、「[ワークフローをトリガーするイベント](/actions/reference/events-that-trigger-workflows)」を参照してください。 + +## 環境の使用 + +{% data reusables.actions.about-environments %} + +## Using concurrency + +並行処理により、同じ並行処理グループを使用する単一のジョブまたはワークフローのみが一度に実行されます。 並行処理では、環境で一度に最大 1 つのデプロイメントが進行中で、1 つのデプロイメントが保留になるようにすることができます。 + +{% 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. + +{% 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. + +```yaml +name: Deployment + +concurrency: production + +on: + push: + branches: + - main + +jobs: + deployment: + runs-on: ubuntu-latest + environment: production + steps: + - name: deploy + # ...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`. + +```yaml +name: Deployment + +on: + push: + branches: + - main + +jobs: + deployment: + runs-on: ubuntu-latest + environment: production + concurrency: production + steps: + - name: deploy + # ...deployment-specific steps +``` + +You can also use `cancel-in-progress` to cancel any currently running job or workflow in the same concurrency group. + +```yaml +name: Deployment + +concurrency: + group: production + cancel-in-progress: true + +on: + push: + branches: + - main + +jobs: + deployment: + runs-on: ubuntu-latest + environment: production + steps: + - name: deploy + # ...deployment-specific steps +``` + +## デプロイメント履歴の表示 + +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)." + +## Monitoring workflow runs + +すべてのワークフローの実行は、実行の進行を示すリアルタイムのグラフを生成します。 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)." + +You can also view the logs of each workflow run and the history of workflow runs. 詳しい情報については、「[ワークフロー実行の履歴を表示する](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)」を参照してください。 + +## Tracking deployments through apps + +{% ifversion fpt %} +If your {% data variables.product.product_name %} personal account or organization 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)." +{% 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)." + +{% ifversion fpt or ghes %} + +## ランナーの選択 + +You can run your deployment workflow on {% data variables.product.product_name %}-hosted runners or on self-hosted runners. Traffic from {% data variables.product.product_name %}-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.product_name %}-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)." + +{% 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 %} + +For more information, see "[Adding a workflow status badge](/actions/managing-workflow-runs/adding-a-workflow-status-badge)." + +## 次のステップ + +This article demonstrated features of {% data variables.product.prodname_actions %} that you can add to your deployment workflows. + +{% data reusables.actions.cd-templates-actions %} diff --git a/translations/ja-JP/content/actions/deployment/index.md b/translations/ja-JP/content/actions/deployment/index.md index a200de45a1..ffb81d8922 100644 --- a/translations/ja-JP/content/actions/deployment/index.md +++ b/translations/ja-JP/content/actions/deployment/index.md @@ -7,10 +7,13 @@ versions: ghes: '*' ghae: '*' children: + - /about-continuous-deployment + - /deploying-with-github-actions + - /using-environments-for-deployment + - /viewing-deployment-history - /deploying-to-amazon-elastic-container-service - /deploying-to-azure-app-service - /deploying-to-google-kubernetes-engine - /installing-an-apple-certificate-on-macos-runners-for-xcode-development - - /environments --- diff --git a/translations/ja-JP/content/actions/deployment/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md b/translations/ja-JP/content/actions/deployment/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md index 939b99e309..6c0828af0a 100644 --- a/translations/ja-JP/content/actions/deployment/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md +++ b/translations/ja-JP/content/actions/deployment/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md @@ -17,7 +17,6 @@ shortTitle: Sign Xcode applications {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## はじめに diff --git a/translations/ja-JP/content/actions/deployment/using-environments-for-deployment.md b/translations/ja-JP/content/actions/deployment/using-environments-for-deployment.md new file mode 100644 index 0000000000..74c9f5cedf --- /dev/null +++ b/translations/ja-JP/content/actions/deployment/using-environments-for-deployment.md @@ -0,0 +1,126 @@ +--- +title: Using environments for deployment +shortTitle: Use environments for deployment +intro: 保護ルールとシークレットを持つ環境を設定できます。 A workflow job that references an environment must follow any protection rules for the environment before running or accessing the environment's secrets. +product: '{% data reusables.gated-features.environments %}' +miniTocMaxHeadingLevel: 3 +redirect_from: + - /actions/reference/environments + - /actions/deployment/environments +versions: + fpt: '*' + ghes: '>=3.1' + ghae: '*' +--- + + +## 環境について + +Environments are used to describe a general deployment target like `production`, `staging`, or `development`. 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)." + +保護ルールとシークレットを持つ環境を設定できます。 ワークフローのジョブが環境を参照すると、その環境の保護ルールをすべてパスするまではジョブは開始されません。 すべての環境の保護ルールをパスするまで、ジョブは環境で定義されているシークレットにアクセスできません。 + +{% ifversion fpt %} +{% note %} + +**Note:** If you don't use {% data variables.product.prodname_ghe_cloud %} and convert a repository from public to private, any configured protection rules or environment secrets will be ignored, and you will not be able to configure any environments. リポジトリをパブリックに変換して戻せば、以前に設定されていた保護ルールや環境のシークレットにアクセスできるようになります。 {% data reusables.enterprise.link-to-ghec-trial %} + +{% endnote %} +{% endif %} + +## 環境の保護ルール + +環境の保護ルールは、その環境を参照しているジョブが進行する前に特定の条件をパスすることを要求します。 {% ifversion fpt or ghae-next or ghes > 3.1 %}環境保護ルールを使用して、手動による承認を要求したり、ジョブを遅延させたり、環境を特定のブランチに制限したりすることができます。{% else %}環境保護ルールを使用して、手動による承認を要求したり、ジョブを遅延させたりすることができます。{% endif %} + +### 必須のレビュー担当者 + +必須のレビュー担当者を使って、特定の人もしくはTeamがその環境を参照するワークフローのジョブを承認しなければならないようにすることができます。 最大で6人のユーザもしくはTeamをレビュー担当者とすることができます。 レビュー担当者は、少なくともそのリポジトリの読み取りアクセス権を持っていなければなりません。 ジョブが進行するため承認が必要なレビュー担当者は1人だけです。 + +必須のレビュー担当者を持つ環境を参照しているジョブのレビューに関する詳しい情報については「[デプロイメントのレビュー](/actions/managing-workflow-runs/reviewing-deployments)」を参照してください。 + +### 待機タイマー + +ジョブが最初にトリガーされた後、特定の時間ジョブを遅延させるために、待機タイマーを使ってください。 時間（分）は、0から43,200（30日）の間の整数でなければなりません。 + +{% ifversion fpt or ghae-next or ghes > 3.1 %} +### デプロイメントブランチ + +デプロイメントブランチを使用して、環境にデプロイできるブランチを制限します。 環境のデプロイメントブランチのオプションは以下のとおりです。 + +* **すべてのブランチ**: リポジトリ内のすべてのブランチを環境にデプロイできます。 +* **保護されたブランチ**: 環境にデプロイできるのはブランチ保護ルールが有効になっているブランチのみです。 リポジトリ内のどのブランチにもブランチ保護ルールが定義されていない場合は、すべてのブランチをデプロイできます。 ブランチ保護ルールの詳細については、「[保護されたブランチについて](/github/administering-a-repository/about-protected-branches)」を参照してください。 +* **選択したブランチ**: 環境にデプロイできるのは指定した名前パターンに一致するブランチのみです。 + + たとえば、デプロイメントブランチルールとして `releases/*` を指定した場合、名前が `releases/` で始まるブランチのみが環境にデプロイできます。 （ワイルドカード文字は `/` と一致しません。 `release/` で始まり、追加の単一スラッシュを含むブランチを一致させるには、`release/*/*` を使用します。） `main` をデプロイメントブランチルールとして追加すると、`main` という名前のブランチも環境にデプロイできます。 デプロイメントブランチの構文オプションの詳細については、[Ruby File.fnmatch documentation](https://ruby-doc.org/core-2.5.1/File.html#method-c-fnmatch) のドキュメントを参照してください。 +{% endif %} +## 環境のシークレット + +環境に保存されたシークレットは、その環境を参照するワークフロージョブからのみ利用できます。 環境が承認を必要とするなら、ジョブは必須のレビュー担当者の一人が承認するまで環境のシークレットにアクセスできません。 シークレットに関する詳しい情報については「[暗号化されたシークレット](/actions/reference/encrypted-secrets)」を参照してください。 + +{% note %} + +**注釈:** セルフホストランナーで実行されるワークフローは、環境を使用している場合でも、分離されたコンテナでは実行されません。 Environment secrets should be treated with the same level of security as repository and organization secrets. 詳しい情報については「[GitHub Actionsのためのセキュリティ強化](/actions/learn-github-actions/security-hardening-for-github-actions#hardening-for-self-hosted-runners)」を参照してください。 + +{% endnote %} + +## 環境の作成 + +{% data reusables.github-actions.permissions-statement-environment %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.github-actions.sidebar-environment %} +{% data reusables.github-actions.new-environment %} +{% data reusables.github-actions.name-environment %} +1. Optionally, specify people or teams that must approve workflow jobs that use this environment. + 1. Select **Required reviewers**. + 1. Enter up to 6 people or teams. ジョブが進行するため承認が必要なレビュー担当者は1人だけです。 + 1. Click **Save protection rules**. +2. Optionally, specify the amount of time to wait before allowing workflow jobs that use this environment to proceed. + 1. Select **Wait timer**. + 1. Enter the number of minutes to wait. + 1. Click **Save protection rules**. +3. Optionally, specify what branches can deploy to this environment. For more information about the possible values, see "[Deployment branches](#deployment-branches)." + 1. Select the desired option in the **Deployment branches** dropdown. + 1. If you chose **Selected branches**, enter the branch name patterns that you want to allow. +4. Optionally, add environment secrets. These secrets are only available to workflow jobs that use the environment. Additionally, workflow jobs that use this environment can only access these secrets after any configured rules (for example, required reviewers) pass. シークレットに関する詳しい情報については「[暗号化されたシークレット](/actions/reference/encrypted-secrets)」を参照してください。 + 1. Under **Environment secrets**, click **Add Secret**. + 1. Enter the secret name. + 1. Enter the secret value. + 1. [**Add secret（シークレットの追加）**] をクリックします。 + +{% ifversion fpt or ghae-next or ghes > 3.1 %}REST API を介して環境を作成および設定することもできます。 詳しい情報については、「[環境](/rest/reference/repos#environments)」および「[シークレット](/rest/reference/actions#secrets)」を参照してください。{% endif %} + +存在しない環境を参照するワークフローを実行すると、参照された名前を持つ環境が作成されます。 新しく作成される環境には、保護ルールやシークレットは設定されていません。 リポジトリのワークフローを編集できる人は、ワークフローファイルを通じて環境を作成できますが、その環境を設定できるのはリポジトリ管理者だけです。 + +## Using an environment + +ワークフロー内の各ジョブは、1つの環境を参照できます。 この環境を参照するとジョブがランナーに送信される前に、環境に設定された保護ルールをパスしなければなりません。 The job can access the environment's secrets only after the job is sent to a runner. + +ワークフローが環境を参照する場合、その環境はリポジトリのデプロイメントに現れます。 現在及び以前のデプロイメントの表示に関する詳細については「[デプロイメント履歴の表示](/developers/overview/viewing-deployment-history)」を参照してください。 + +{% data reusables.actions.environment-example %} + +## 環境の削除 + +{% data reusables.github-actions.permissions-statement-environment %} + +環境を削除すると、その環境に関連づけられたすべてのシークレットと保護ルールが削除されます。 削除された環境の保護ルールのために待機していたジョブは、自動的に失敗します。 + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.github-actions.sidebar-environment %} +1. 削除する環境の横にある {% octicon "trash" aria-label="The trash icon" %} をクリックします。 +2. **I understand, delete this environment（分かりました、この環境を削除してください）**をクリックしてください。 + +{% ifversion fpt or ghae-next or ghes > 3.1 %}REST API を介して環境を削除することもできます。 詳しい情報については、「[環境](/rest/reference/repos#environments)」を参照してください。{% endif %} + +## How environments relate to deployments + +{% data reusables.actions.environment-deployment-event %} + +You can access these objects through the REST API or GraphQL API. You can also subscribe to these webhook events. For more information, see "[Repositories](/rest/reference/repos#deployments)" (REST API), "[Objects](/graphql/reference/objects#deployment)" (GraphQL API), or "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#deployment)." + +## 次のステップ + +{% data variables.product.prodname_actions %} provides several features for managing your deployments. For more information, see "[Deploying with GitHub Actions](/actions/deployment/deploying-with-github-actions)." diff --git a/translations/ja-JP/content/actions/deployment/viewing-deployment-history.md b/translations/ja-JP/content/actions/deployment/viewing-deployment-history.md new file mode 100644 index 0000000000..7b2fd5f823 --- /dev/null +++ b/translations/ja-JP/content/actions/deployment/viewing-deployment-history.md @@ -0,0 +1,27 @@ +--- +title: デプロイメント履歴の表示 +intro: リポジトリの現在と過去のデプロイメントの表示。 +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - API +shortTitle: View deployment history +redirect_from: + - /developers/overview/viewing-deployment-history +--- + + +{% ifversion fpt or ghae or ghes > 3.0 %}{% data variables.product.prodname_actions %}及び環境、もしくは{% endif %}REST APIとサードパーティのアプリケーションを通じて、デプロイメントを配信できます。 {% ifversion fpt or ghae ghes > 3.0 %}For more information about using environments to deploy with {% data variables.product.prodname_actions %}, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." {% endif %} REST APIでのデプロイメントに関する詳しい情報については、「[リポジトリ](/rest/reference/repos#deployments)」を参照してください。 + +現在及び過去のデプロイメントを表示するには、リポジトリのホームページの** Environments（環境）**をクリックしてください。 +{% ifversion ghae or ghes < 3.0 %} +![環境](/assets/images/enterprise/2.22/environments-sidebar.png){% else %} +![Environments](/assets/images/environments-sidebar.png){% endif %} + +デプロイメントページは、リポジトリの各環境の最新のアクティブなデプロイメントを表示します。 If the deployment includes an environment URL, a **View deployment** button that links to the URL is shown next to the deployment. + +アクティビティログは、環境のデプロイメントの履歴を表示します。 デフォルトでは、環境の最新のデプロイメントだけが`Active`ステータスを持ち、すべての過去にアクティブだったデプロイメントは`Inactive`ステータスを持ちます。 デプロイメントの自動的な非アクティブ化に関する詳しい情報については「[デプロイメントの非アクティブ化](/rest/reference/repos#inactive-deployments)」を参照してください。 + +また、REST APIを使ってデプロイメントに関する情報を取得することもできます。 詳しい情報については「[リポジトリ](/rest/reference/repos#deployments)」を参照してください。 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 629a255224..77d781452d 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 @@ -14,7 +14,6 @@ type: overview {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## セルフホストランナーについて @@ -172,7 +171,9 @@ pkg-containers-az.githubusercontent.com ## パブリックリポジトリでのセルフホストランナーのセキュリティ +{% ifversion not ghae %} {% data reusables.github-actions.self-hosted-runner-security %} +{% endif %} それぞれの{% data variables.product.prodname_dotcom %}ホストランナーは常にクリーンな隔離された仮想マシンになり、ジョブの実行が終わると破棄されるので、{% data variables.product.prodname_dotcom %}ホストランナーではこれは問題にはなりません。 diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md index 19d793288d..dc306cdaf9 100644 --- a/translations/ja-JP/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md +++ b/translations/ja-JP/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md @@ -15,7 +15,6 @@ shortTitle: Add self-hosted runners {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} リポジトリ、Organization、Enterpriseにセルフホストランナーを追加できます。 @@ -23,6 +22,7 @@ Organization または Enterprise 管理者の場合は、Organization または セルフホストランナーでサポートされているオペレーティングシステム、あるいはプロキシサーバーとセルフホストランナーを使う方法に関する情報については、「[セルフホストランナーについて](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)」を参照してください。 +{% ifversion not ghae %} {% warning %} **警告：** {% data reusables.github-actions.self-hosted-runner-security %} @@ -30,6 +30,7 @@ Organization または Enterprise 管理者の場合は、Organization または 詳しい情報については「[セルフホストランナーについて](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)」を参照してください。 {% endwarning %} +{% endif %} ## リポジトリへのセルフホストランナーの追加 @@ -48,7 +49,7 @@ Organization または Enterprise 管理者の場合は、Organization または {% data reusables.repositories.sidebar-settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} 1. GitHub Insightsの -{% ifversion fpt %}"ランナー"{% else %}"セルフホストランナー"{% endif %} で、[**Add runner**] をクリックします。 +{% ifversion fpt or ghes > 3.1 or ghae %}"ランナー"{% else %}"セルフホストランナー"{% endif %} で、[**Add runner**] をクリックします。 {% data reusables.github-actions.self-hosted-runner-configure %} {% endif %} {% data reusables.github-actions.self-hosted-runner-check-installation-success %} @@ -70,7 +71,7 @@ Organization または Enterprise 管理者の場合は、Organization または {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} 1. GitHub Insightsの -{% ifversion fpt %}"ランナー"{% else %}"セルフホストランナー"{% endif %} で、[**Add runner**] をクリックします。 +{% ifversion fpt or ghes > 3.1 or ghae %}"ランナー"{% else %}"セルフホストランナー"{% endif %} で、[**Add runner**] をクリックします。 {% data reusables.github-actions.self-hosted-runner-configure %} {% endif %} 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 e1ea5f8ce4..ecb901a241 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 @@ -10,7 +10,6 @@ type: overview {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About autoscaling diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md b/translations/ja-JP/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md index 6212d80a38..f0448ef45d 100644 --- a/translations/ja-JP/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md +++ b/translations/ja-JP/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md @@ -15,7 +15,6 @@ shortTitle: Run runner app on startup {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% capture service_first_step %}1. セルフホストランナー アプリケーションが現在実行中の場合は、そのアプリケーションを停止します。{% endcapture %} {% capture service_non_windows_intro_shell %}ランナー マシンで、セルフホストランナー アプリケーションをインストールしたディレクトリでシェルを開きます。 以下のコマンドを使って、セルフホストランナーサービスをインストール及び管理します。{% endcapture %} diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/index.md b/translations/ja-JP/content/actions/hosting-your-own-runners/index.md index 91af6d7656..c8bd173a30 100644 --- a/translations/ja-JP/content/actions/hosting-your-own-runners/index.md +++ b/translations/ja-JP/content/actions/hosting-your-own-runners/index.md @@ -24,4 +24,3 @@ children: {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md b/translations/ja-JP/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md index 6419910479..d35f9f8b14 100644 --- a/translations/ja-JP/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md +++ b/translations/ja-JP/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md @@ -14,7 +14,6 @@ shortTitle: Manage runner groups {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## セルフホストランナーのグループについて @@ -173,14 +172,13 @@ Could not find any self-hosted runner group named "rg-runnergroup". ## セルフホストランナーをグループに移動する If you don't specify a runner group during the registration process, your new self-hosted runners are automatically assigned to the default group, and can then be moved to another group. -{% ifversion fpt %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} 1. In the "Runners" list, click the runner that you want to configure. 1. Select the Runner group dropdown menu. 1. In "Move runner to group", choose a destination group for the runner. -{% endif %} -{% ifversion ghae or ghes %} -1. {% ifversion fpt %}[Runners]{% else %}[Self-hosted runners]{% endif %} セクションで、移動するランナーの現在のグループを見つけて、グループメンバーのリストを展開します。 ![ランナーグループのメンバーを表示](/assets/images/help/settings/actions-org-runner-group-members.png) +{% else %} +1. In the "Self-hosted runners" section of the settings page, locate the current group of the runner you want to move and expand the list of group members. ![ランナーグループのメンバーを表示](/assets/images/help/settings/actions-org-runner-group-members.png) 1. セルフホストランナーの横にあるチェックボックスを選択し、[**Move to group**] をクリックして、利用可能な移動先を確認します。 ![ランナーグループのメンバーを移動](/assets/images/help/settings/actions-org-runner-group-member-move.png) 1. 移動先のグループをクリックして、ランナーを移動します。 ![ランナーグループのメンバーを移動](/assets/images/help/settings/actions-org-runner-group-member-move-destination.png) {% endif %} @@ -188,14 +186,13 @@ If you don't specify a runner group during the registration process, your new se セルフホストランナーは、グループが削除されると自動的にデフォルトグループに戻ります。 -{% ifversion fpt %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} {% data reusables.github-actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %} 1. In the list of groups, to the right of the group you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. 1. グループを削除するには、[**Remove group**] をクリックします。 1. 確認プロンプトを確認し、[**Remove this runner group**] をクリックします。 -{% endif %} -{% ifversion ghae or ghes %} -1. 設定ページの {% ifversion fpt %}[Runners]{% else %}[Self-hosted runners]{% endif %} セクションで、削除するグループを見つけて、{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} ボタンをクリックします。 ![ランナーグループの設定を表示](/assets/images/help/settings/actions-org-runner-group-kebab.png) +{% else %} +1. In the "Self-hosted runners" section of the settings page, locate the group you want to delete, and click the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} button. ![ランナーグループの設定を表示](/assets/images/help/settings/actions-org-runner-group-kebab.png) 1. グループを削除するには、[**Remove group**] をクリックします。 ![ランナーグループの設定を表示](/assets/images/help/settings/actions-org-runner-group-remove.png) diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md index 542cfae022..9541e9dfa9 100644 --- a/translations/ja-JP/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md +++ b/translations/ja-JP/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md @@ -11,22 +11,20 @@ versions: ghae: '*' type: tutorial defaultPlatform: linux +shortTitle: Monitor & troubleshoot --- {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -### {{ site.data.variables.product.prodname_dotcom }}を使ったセルフホストランナーのステータスのチェック +## {% data variables.product.prodname_dotcom %}を使ったセルフホストランナーのステータスのチェック {% data reusables.github-actions.self-hosted-runner-management-permissions-required %} {% data reusables.github-actions.self-hosted-runner-navigate-repo-and-org %} {% data reusables.github-actions.settings-sidebar-actions-runners %} -1. {% if currentVersion == "free-pro-team@latest" %}[Runners]{% else %}[Self-hosted runners]{% endif %} で、ランナーの名前、ラベル、ステータスなど、登録済みのランナーのリストを表示できます。 - - ![ランナーのリスト](/assets/images/help/settings/actions-runner-list.png) +1. Under {% ifversion fpt or ghes > 3.1 or ghae-next %}"Runners"{% else %}"Self-hosted runners"{% endif %}, you can view a list of registered runners, including the runner's name, labels, and status. ステータスは以下のいずれかです。 @@ -35,19 +33,19 @@ defaultPlatform: linux * **Offline**: ランナーは{% data variables.product.product_name %}に接続されていません。 これは、マシンがオフラインになっているか、マシン上でセルフホストランナーアプリケーションが動作していないか、セルフホストランナーアプリケーションが{% data variables.product.product_name %}と通信できていないかです。 -### セルフホストランナーアプリケーションのログファイルのレビュー +## セルフホストランナーアプリケーションのログファイルのレビュー セルフホストランナーアプリケーションのステータスと、そのアクティビティをモニタリングできます。 ログファイルは`_diag`ディレクトリに保存されており、アプリケーションが起動されるたびに新しいログが生成されます。 ファイル名は*Runner_*で始まり、その後にアプリケーションが起動された時刻のUTCタイムスタンプが続きます。 ワークフロージョブの実行に関する詳細なログについては、*Worker_*ファイルについて述べた次のセクションを参照してください。 -### ジョブのログファイルのレビュー +## ジョブのログファイルのレビュー セルフホストランナーアプリケーションは、処理するジョブごとに詳細なログファイルを生成します。 これらのファイルは`_diag`ディレクトリに保存され、ファイル名は*Worker_*で始まります。 {% linux %} -### journalctlを使ってのセルフホストランナーアプリケーションのチェック +## journalctlを使ってのセルフホストランナーアプリケーションのチェック サービスを利用してアプリケーションを実行しているLinuxベースのセルフホストランナーでは、リアルタイムのアクティビティをモニターするのに`journalctl`が使えます。 デフォルトのsystemdベースのサービスは、以下の命名規則を使います。 `actions.runner.-..service` この名前は80文字を超える場合には切り捨てられるので、サービス名を見つける方法としては_.service_ファイルをチェックするのが良いでしょう。 例: @@ -80,7 +78,7 @@ systemdの設定を見るには、サービスファイルを以下で見つけ {% mac %} -### launchdを使ってのセルフホストランナーアプリケーションのチェック +## launchdを使ってのセルフホストランナーアプリケーションのチェック サービスとしてアプリケーションを実行しているmacOSベースのセルフホストランナーでは、リアルタイムのアクティビティをモニターするのに`launchctl`が使えます。 デフォルトのlaunchdベースのサービスは、以下の命名規則を使います。 `actions.runner.-.` この名前は80文字を超える場合には切り捨てられるので、サービス名を見つける方法としてはランナーのディレクトリ内にある_.service_ファイルをチェックするのが良いでしょう。 @@ -108,7 +106,7 @@ launchdの設定を見るには、サービスファイルを以下で見つけ {% windows %} -### PowerShellを使ってのセルフホストランナーアプリケーションのチェック +## PowerShellを使ってのセルフホストランナーアプリケーションのチェック サービスとしてアプリケーションを実行しているWindowsベースのセルフホストランナーでは、リアルタイムのアクティビティをモニターするのにPowerShellが使えます。 サービスは`GitHub Actions Runner (-.)`という命名規則を使います。 ランナーのディレクトリ内にある_.service_ファイルを調べても、サービスの名前を見つけることができます。 @@ -145,7 +143,7 @@ PS C:\actions-runner> Get-EventLog -LogName Application -Source ActionsRunnerSer {% endwindows %} -### 自動アップデートプロセスのモニタリング +## 自動アップデートプロセスのモニタリング セルフホストランナーは、特定のバージョンのしきい値を下回るとジョブを処理できなくなるため、定期的に自動更新プロセスを確認することをお勧めします。 セルフホストランナーアプリケーションは自動的に更新されますが、このプロセスにはオペレーティングシステムやその他のソフトウェアの更新は含まれません。これらの更新を個別に管理する必要があります。 @@ -159,9 +157,9 @@ PS C:\actions-runner> Get-EventLog -LogName Application -Source ActionsRunnerSer {% linux %} -### セルフホストランナー内のコンテナのトラブルシューティング +## セルフホストランナー内のコンテナのトラブルシューティング -#### Dockerがインストールされていることを確認 +### Dockerがインストールされていることを確認 ジョブがコンテナを必要とするなら、セルフホストランナーはLinuxベースで、Dockerがインストールされていなければなりません。 セルフホストランナーにDockerがインストールされており、サービスが動作中であることを確認してください。 @@ -180,7 +178,7 @@ Dockerがインストールされていないなら、Dockerに依存するア [2020-02-13 16:56:10Z ERR StepsRunner] Caught exception from step: System.IO.FileNotFoundException: File not found: 'docker' ``` -#### Dockerの権限の確認 +### Dockerの権限の確認 ジョブが次のエラーで失敗するなら、 diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md index 8f13411d54..c404a98c9c 100644 --- a/translations/ja-JP/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md +++ b/translations/ja-JP/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md @@ -15,7 +15,6 @@ shortTitle: Remove self-hosted runners {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## リポジトリからのランナーの削除 @@ -57,15 +56,14 @@ shortTitle: Remove self-hosted runners Organizationからセルフホストランナーを削除するには、Organizationのオーナーでなければなりません。 セルフホストランナーのマシンへもアクセスできるようにしておくことをおすすめします。 {% data reusables.github-actions.self-hosted-runner-reusing %} -{% ifversion fpt %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions %} {% data reusables.github-actions.settings-sidebar-actions-runners-updated %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %} -{% endif %} -{% ifversion ghae or ghes %} +{% else %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} @@ -90,10 +88,9 @@ Organizationからセルフホストランナーを削除するには、Organiza {% data reusables.enterprise-accounts.actions-runners-tab %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes %} セルフホストランナーを -{% data variables.product.product_location %} の Enterprise レベルで削除するには、サイト管理者である必要があります。 セルフホストランナーのマシンへもアクセスできるようにしておくことをおすすめします。 +{% data variables.product.product_location %}, you must be an enterprise owner. セルフホストランナーのマシンへもアクセスできるようにしておくことをおすすめします。 {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md index 6885e5181d..de1ab8171e 100644 --- a/translations/ja-JP/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md +++ b/translations/ja-JP/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md @@ -14,7 +14,6 @@ shortTitle: Proxy servers {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 環境変数を利用したプロキシサーバーの設定 diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md index cd567613c0..b6fb344070 100644 --- a/translations/ja-JP/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md +++ b/translations/ja-JP/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md @@ -12,7 +12,6 @@ shortTitle: Label runners {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} 特定の種類のセルフホストランナーにジョブをまわすためのラベルの利用方法に関する情報については、「[ワークフロー内でのセルフホストランナーの利用](/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow)」を参照してください。 diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md b/translations/ja-JP/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md index 531f41f483..f23c15b513 100644 --- a/translations/ja-JP/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md +++ b/translations/ja-JP/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md @@ -9,14 +9,16 @@ versions: ghes: '*' ghae: '*' type: tutorial +shortTitle: Use runners in a workflow --- +{% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} カスタム及びデフォルトラベルの作成に関する情報については「[セルフホストランナーでのラベルの利用](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)」を参照してください。 -### ワークフローでのセルフホストランナーの利用 +## ワークフローでのセルフホストランナーの利用 ラベルを使うと、セルフホストランナーの共有される特徴に基づき、ワークフローのジョブを特定の種類のセルフホストランナーに送れます。 たとえば、ジョブが特定のハードウェアコンポーネントやソフトウェアパッケージを必要とするなら、カスタムラベルをランナーに割り当て、そのラベルを持つランナー上でのみ実行されるようジョブを設定できます。 @@ -24,13 +26,13 @@ type: tutorial 詳細については、「[{% data variables.product.prodname_actions %}のワークフロー構文](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idruns-on)」を参照してください。 -### デフォルトラベルを使ったジョブの転送 +## デフォルトラベルを使ったジョブの転送 セルフホストランナーは、{% data variables.product.prodname_actions %}に追加されたときに特定のラベルを自動的に受信します。 それらは、ランナーのオペレーティングシステムとハードウェアプラットフォームを示すために使われます。 * `self-hosted`: セルフホストランナーに適用されるデフォルトのラベル。 * `linux`、`windows`、`macOS`: オペレーティングシステムに基づいて適用されます。 -* `x64`, `ARM`, or `ARM64`: Applied depending on hardware architecture. +* `x64`、`ARM`、または `ARM64`: ハードウェアアーキテクチャに基づいて適用されます。 ワークフローのYAMLを使って、これらのラベルの組み合わせに対してジョブを送信できます。 この例では、3つのラベルすべてにマッチするセルフホストランナーが、ジョブを実行する資格を持つことになります。 @@ -44,7 +46,7 @@ runs-on: [self-hosted, linux, ARM64] デフォルトラベルは固定されており、変更や削除はできません。 ジョブの転送をもっと制御する必要がある場合は、カスタムラベルの利用を検討してください。 -### カスタムラベルを使ったジョブの転送 +## カスタムラベルを使ったジョブの転送 カスタムラベルを作成し、セルフホストランナーに割り当てることがいつでもできます。 カスタムラベルを使えば、付けられたラベルに基づいて特定の種類のセルフホストランナーにジョブを送信できるようになります。 @@ -63,13 +65,21 @@ runs-on: [self-hosted, linux, x64, gpu] これらのラベルは累積的に働くので、このジョブを処理できるセルフホストランナーは、4つすべてのラベルがマッチしていなければなりません。 -### セルフホストランナーのルーティングの優先順位 +## セルフホストランナーのルーティングの優先順位 ジョブをセルフホストランナーにルーティングする際に、{% data variables.product.prodname_dotcom %}はジョブの`runs-on`ラベルにマッチするランナーを探します。 -1. {% data variables.product.prodname_dotcom %}ま、まずリポジトリレベルで、続いてOrganizationのレベルで{% if currentVersion ver_gt "enterprise-server@2.21" %}、そしてEnterpriseのレベルで{% endif %}ランナーを探します。 +{% ifversion fpt or ghes > 3.2 or ghae-next %} +- {% data variables.product.prodname_dotcom %} first searches for an online and idle runner at the repository level, then at the organization level, {% ifversion fpt %} and if the organization is part of an enterprise,{% endif %} then at the enterprise level. +- If {% data variables.product.prodname_dotcom %} finds an online and idle runner at a certain level that matches the job's `runs-on` labels, the job is then assigned and sent to the runner. + - If the runner doesn't pick up the assigned job within 60 seconds, the job is queued at all levels and waits for a matching runner from any level to come online and pick up the job. +- If {% data variables.product.prodname_dotcom %} doesn't find an online and idle runner at any level, the job is queued to all levels and waits for a matching runner from any level to come online and pick up the job. +- 24時間以上にわたってキューに残っていたジョブは失敗します。 +{% else %} +1. {% data variables.product.prodname_dotcom %} first searches for a runner at the repository level, then at the organization level, then at the enterprise level. 2. ジョブは最初にマッチした、オンラインでアイドル状態のランナーに送信されます。 - マッチしたすべてのランナーがビジーだった場合、ジョブはマッチしたオンラインのランナーが最も多いレベルでキューイングされます。 - マッチしたランナーがすべてオフラインだった場合、ジョブはマッチしたオフラインのランナーが最も多いレベルでキューイングされます。 - マッチするランナーがどのレベルにもなかった場合、そのジョブは失敗します。 - 24時間以上にわたってキューに残っていたジョブは失敗します。 +{% endif %} diff --git a/translations/ja-JP/content/actions/index.md b/translations/ja-JP/content/actions/index.md index 30421a9bc8..68840a6e8d 100644 --- a/translations/ja-JP/content/actions/index.md +++ b/translations/ja-JP/content/actions/index.md @@ -9,6 +9,7 @@ featuredLinks: guides: - /actions/learn-github-actions - /actions/guides/about-continuous-integration + - /actions/deployment/deploying-with-github-actions - /actions/guides/about-packaging-with-github-actions - /actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting guideCards: diff --git a/translations/ja-JP/content/actions/learn-github-actions/contexts.md b/translations/ja-JP/content/actions/learn-github-actions/contexts.md index ffea700173..c52229f3f3 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/contexts.md +++ b/translations/ja-JP/content/actions/learn-github-actions/contexts.md @@ -18,7 +18,6 @@ miniTocMaxHeadingLevel: 3 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About contexts @@ -61,27 +60,29 @@ miniTocMaxHeadingLevel: 3 {% data reusables.github-actions.github-context-warning %} {% data reusables.github-actions.context-injection-warning %} -| プロパティ名 | 種類 | 説明 | -| ------------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `github` | `オブジェクト` | ワークフローのあらゆるジョブやステップにおいて使用できる最上位のコンテキスト。 | -| `github.action` | `string` | 現在実行中のアクションの名前。 {% data variables.product.prodname_dotcom %}は、現在のステップがスクリプトを実行する際に、特殊なキャラクターを削除するか、`run`という名前を使います。 同じジョブの中で同じアクションを複数回使う場合、名前には順番に番号が加えられます。 たとえば、実行する最初のスクリプトの名前は`run1`で、2番目のスクリプトの名前は`run2`というようになります。 同様に、`actions/checkout`の2回目の呼び出しは`actionscheckout2`となります。 | -| `github.action_path` | `string` | アクションが置かれているパス。 このパスを使用して、アクションと同じリポジトリにあるファイルに簡単にアクセスできます。 This attribute is only supported in composite actions. | -| `github.actor` | `string` | ワークフローの実行を開始したユーザのログイン。 | -| `github.base_ref` | `string` | ワークフローの実行における `base_ref` またはPull Requestのターゲットブランチ。 このプロパティは、ワークフローの実行をトリガーするイベントが `pull_request` または `pull_request_target` のいずれかである場合にのみ使用できます。 | -| `github.event` | `オブジェクト` | webhook ペイロードの完全なイベント。 詳しい情報については、「[ワークフローをトリガーするイベント](/articles/events-that-trigger-workflows/)」を参照してください。 このコンテキストを使用して、イベントの個々のプロパティにアクセスできます。 | -| `github.event_name` | `string` | ワークフローの実行をトリガーしたイベントの名前。 | -| `github.event_path` | `string` | ランナー上の完全なイベントwebhookペイロードへのパス。 | -| `github.head_ref` | `string` | ワークフローの実行における `head_ref` またはPull Requestのソースブランチ。 このプロパティは、ワークフローの実行をトリガーするイベントが `pull_request` または `pull_request_target` のいずれかである場合にのみ使用できます。 | -| `github.job` | `string` | 現在のジョブの[`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id)。 | -| `github.ref` | `string` | ワークフローの実行をトリガーしたブランチまたはタグ ref。 For branches this is the format `refs/heads/`, and for tags it is `refs/tags/`. | -| `github.repository` | `string` | 所有者およびリポジトリの名前。 `Codertocat/Hello-World`などです。 | -| `github.repository_owner` | `string` | リポジトリのオーナーの名前。 たとえば`Codertocat`。 | +| プロパティ名 | 種類 | 説明 | +| ------------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `github` | `オブジェクト` | ワークフローのあらゆるジョブやステップにおいて使用できる最上位のコンテキスト。 | +| `github.action` | `string` | 現在実行中のアクションの名前。 {% data variables.product.prodname_dotcom %} removes special characters or uses the name `__run` when the current step runs a script. If you use the same action more than once in the same job, the name will include a suffix with the sequence number with underscore before it. For example, the first script you run will have the name `__run`, and the second script will be named `__run_2`. 同様に、`actions/checkout`の2回目の呼び出しは`actionscheckout2`となります。 | +| `github.action_path` | `string` | アクションが置かれているパス。 このパスを使用して、アクションと同じリポジトリにあるファイルに簡単にアクセスできます。 This attribute is only supported in composite actions. | +| `github.actor` | `string` | ワークフローの実行を開始したユーザのログイン。 | +| `github.base_ref` | `string` | ワークフローの実行における `base_ref` またはPull Requestのターゲットブランチ。 このプロパティは、ワークフローの実行をトリガーするイベントが `pull_request` または `pull_request_target` のいずれかである場合にのみ使用できます。 | +| `github.event` | `オブジェクト` | webhook ペイロードの完全なイベント。 詳しい情報については、「[ワークフローをトリガーするイベント](/articles/events-that-trigger-workflows/)」を参照してください。 このコンテキストを使用して、イベントの個々のプロパティにアクセスできます。 | +| `github.event_name` | `string` | ワークフローの実行をトリガーしたイベントの名前。 | +| `github.event_path` | `string` | ランナー上の完全なイベントwebhookペイロードへのパス。 | +| `github.head_ref` | `string` | ワークフローの実行における `head_ref` またはPull Requestのソースブランチ。 このプロパティは、ワークフローの実行をトリガーするイベントが `pull_request` または `pull_request_target` のいずれかである場合にのみ使用できます。 | +| `github.job` | `string` | 現在のジョブの[`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id)。 | +| `github.ref` | `string` | ワークフローの実行をトリガーしたブランチまたはタグ ref。 For branches this is the format `refs/heads/`, and for tags it is `refs/tags/`. | +| `github.repository` | `string` | 所有者およびリポジトリの名前。 `Codertocat/Hello-World`などです。 | +| `github.repository_owner` | `string` | リポジトリのオーナーの名前。 たとえば`Codertocat`。 | | `github.run_id` | `string` | {% data reusables.github-actions.run_id_description %} | `github.run_number` | `string` | {% data reusables.github-actions.run_number_description %} -| `github.sha` | `string` | ワークフローの実行をトリガーしたコミット SHA。 | -| `github.token` | `string` | リポジトリにインストールされたGitHub Appの代わりに認証するためのトークン。 これは機能的に`GITHUB_TOKEN`シークレットに等価です。 詳しい情報については「[GITHUB_TOKENでの認証](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)」を参照してください。 | -| `github.workflow` | `string` | ワークフローの名前。 ワークフローファイルで `name` を指定していない場合、このプロパティの値は、リポジトリ内にあるワークフローファイルのフルパスになります。 | -| `github.workspace` | `string` | [`checkout`](https://github.com/actions/checkout)アクションを使う際の、ステップにとってのデフォルトのワーキングディレクトリであり、リポジトリのデフォルトの場所です。 | +| `github.run_attempt` | `string` | A unique number for each attempt of a particular workflow run in a repository. This number begins at 1 for the workflow run's first attempt, and increments with each re-run. | +| `github.server_url` | `string` | Returns the URL of the GitHub server. たとえば、`https://github.com` などです。 | +| `github.sha` | `string` | ワークフローの実行をトリガーしたコミット SHA。 | +| `github.token` | `string` | リポジトリにインストールされたGitHub Appの代わりに認証するためのトークン。 これは機能的に`GITHUB_TOKEN`シークレットに等価です。 詳しい情報については「[GITHUB_TOKENでの認証](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)」を参照してください。 | +| `github.workflow` | `string` | ワークフローの名前。 ワークフローファイルで `name` を指定していない場合、このプロパティの値は、リポジトリ内にあるワークフローファイルのフルパスになります。 | +| `github.workspace` | `string` | [`checkout`](https://github.com/actions/checkout)アクションを使う際の、ステップにとってのデフォルトのワーキングディレクトリであり、リポジトリのデフォルトの場所です。 | ### `env`コンテキスト @@ -130,6 +131,7 @@ miniTocMaxHeadingLevel: 3 | プロパティ名 | 種類 | 説明 | | ------------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `runner.name` | `string` | {% data reusables.actions.runner-name-description %} | `runner.os` | `string` | {% data reusables.actions.runner-os-description %} | `runner.temp` | `string` | {% data reusables.actions.runner-temp-directory-description %} | `runner.tool_cache` | `string` | {% ifversion ghae %}{% data variables.actions.hosted_runner %} に必要なソフトウェアがインストールされていることを確認する方法については、「[カスタムイメージの作成](/actions/using-github-hosted-runners/creating-custom-images)」を参照してください。 {% else %} {% data reusables.actions.runner-tool-cache-description %} {% endif %} diff --git a/translations/ja-JP/content/actions/learn-github-actions/creating-workflow-templates.md b/translations/ja-JP/content/actions/learn-github-actions/creating-workflow-templates.md new file mode 100644 index 0000000000..11965282e1 --- /dev/null +++ b/translations/ja-JP/content/actions/learn-github-actions/creating-workflow-templates.md @@ -0,0 +1,93 @@ +--- +title: Creating workflow templates +shortTitle: Creating templates +intro: Learn how you can create workflow templates to help people in your team add new workflows more easily. +redirect_from: + - /actions/configuring-and-managing-workflows/sharing-workflow-templates-within-your-organization +versions: + fpt: '*' + ghes: '*' + ghae: '*' +type: tutorial +topics: + - Workflows + - CI +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +## 概要 + +{% data reusables.actions.workflow-organization-templates %} + +## ワークフロー テンプレートの作成 + +ワークフローテンプレートは、Organizationの `.github` リポジトリへの書き込みアクセス権を持つユーザが作成できます。 その後、ワークフローを作成する権限を持つOrganizationのメンバーがテンプレートを使用できます。 You can share workflow templates if your organization's repository is public or if the repository is private and on an Enterprise plan. + +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +{% note %} + +**Note:** To avoid duplication in workflows created from a template you can call reusable workflows from within a workflow template. This can help make your workflows easier to maintain. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." + +{% endnote %} +{% endif %} + +この手順では、ワークフロー テンプレートとメタデータ ファイルを作成する方法を示します。 メタデータ ファイルには、ユーザが新しいワークフローを作成するときにテンプレートがどのように表示されるかについて説明します。 + +1. 存在しない場合は、Organization内で`.github`という名前の新しいパブリック リポジトリを作成します。 +2. `workflow-templates`という名前のディレクトリを作成します。 +3. `workflow-templates` ディレクトリ内に新しいワークフローファイルを作成します。 + + リポジトリのデフォルトブランチを参照する必要がある場合は、 `$default-branch` プレースホルダを使用できます。 テンプレートを使用してワークフローを作成すると、プレースホルダはリポジトリのデフォルトブランチの名前に自動的に置き換えられます。 + + たとえば、`octo-organization-ci.yml`という名前のこのファイルは、基本的なワークフローを示しています。 + + ```yaml + name: Octo Organization CI + + on: + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] + + jobs: + build: + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v2 + + - name: Run a one-line script + run: echo Hello from Octo Organization + ``` +4. `workflow-templates` ディレクトリ内にメタデータファイルを作成します。 メタデータ ファイルは、ワークフロー ファイルと同じ名前である必要がありますが、 `.yml` 拡張子の代わりに、 `.properties.json`を付ける必要があります。 たとえば`octo-organization-ci.properties.json`という名前のこのファイルには 、`octo-organization-ci.yml`という名前のワークフローファイルのメタデータが含まれています。 + ```yaml + { + "name": "Octo Organization Workflow", + "description": "Octo Organization CI workflow template.", + "iconName": "example-icon", + "categories": [ + "Go" + ], + "filePatterns": [ + "package.json$", + "^Dockerfile", + ".*\\.md$" + ] + } + ``` + * `name` - **必須。** ワークフロー テンプレートの名前。 これは、使用可能なテンプレートの一覧に表示されます。 + * `description` - **必須。** ワークフロー テンプレートの説明。 これは、使用可能なテンプレートの一覧に表示されます。 + * `iconName` - **必須。** テンプレート リスト内のワークフローのエントリのアイコンを定義します。 `iconName` は、同じ名前の SVG アイコンである必要があり、 `workflow-templates` ディレクトリに格納する必要があります。 たとえば、`example-icon.svg`という名前の SVG ファイルは、 `example-icon`として参照されます。 + * `categories` - **オプション。** ワークフローの言語カテゴリを定義します。 ユーザーが使用可能なテンプレートを表示する際に、同じ言語に一致するテンプレートが目立つようにになります。 使用可能な言語カテゴリについては、「https://github.com/github/linguist/blob/master/lib/linguist/languages.yml」を参照してください。 + * `filePatterns` - **オプション 。** 定義された正規表現に一致するファイルがユーザーのリポジトリのルート ディレクトリにある場合に、テンプレートを使用できるようにします。 + +別のワークフロー テンプレートを追加するには、同じ `workflow-templates` ディレクトリにファイルを追加します。 例: + +![ワークフロー テンプレート ファイル](/assets/images/help/images/workflow-template-files.png) + +## 次のステップ + +To continue learning about {% data variables.product.prodname_actions %}, see "[Using workflow templates](/actions/learn-github-actions/using-workflow-templates)." diff --git a/translations/ja-JP/content/actions/learn-github-actions/environment-variables.md b/translations/ja-JP/content/actions/learn-github-actions/environment-variables.md index 60d2823165..1afb564b9b 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/environment-variables.md +++ b/translations/ja-JP/content/actions/learn-github-actions/environment-variables.md @@ -15,7 +15,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 環境変数について @@ -73,6 +72,7 @@ You can also use the {% ifversion fpt or ghes > 2.22 or ghae %}`GITHUB_ENV` envi | `GITHUB_SERVER_URL` | {% data variables.product.product_name %} サーバーの URL を返します。 For example: `https://{% data variables.product.product_url %}`. | | `GITHUB_API_URL` | API URL を返します。 For example: `{% data variables.product.api_url_code %}`. | | `GITHUB_GRAPHQL_URL` | グラフ QL API の URL を返します。 For example: `{% data variables.product.graphql_url_code %}`. | +| `RUNNER_NAME` | {% data reusables.actions.runner-name-description %} | `RUNNER_OS` | {% data reusables.actions.runner-os-description %} | `RUNNER_TEMP` | {% data reusables.actions.runner-temp-directory-description %} {% ifversion not ghae %}| `RUNNER_TOOL_CACHE` | {% data reusables.actions.runner-tool-cache-description %}{% endif %} diff --git a/translations/ja-JP/content/actions/learn-github-actions/essential-features-of-github-actions.md b/translations/ja-JP/content/actions/learn-github-actions/essential-features-of-github-actions.md index 980fa78b62..7f7633e320 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/essential-features-of-github-actions.md +++ b/translations/ja-JP/content/actions/learn-github-actions/essential-features-of-github-actions.md @@ -13,7 +13,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 概要 @@ -62,7 +61,7 @@ jobs: ## ジョブ間でデータを共有する -ジョブが同じワークフロー内の別のジョブと共有するファイルを生成する場合、または後で参照できるようにファイルを保存する場合は、それらを_成果物_として {% data variables.product.prodname_dotcom %} に保存できます。 成果物とは、コードをビルドしてテストするときに作成されるファイルのことです。 たとえば、成果物には、バイナリまたパッケージファイル、テスト結果、スクリーンショット、ログファイルなどがあります。 成果物は、それが作成されたワークフロー実行に関連付けられており、別のジョブで使用できます。 +ジョブが同じワークフロー内の別のジョブと共有するファイルを生成する場合、または後で参照できるようにファイルを保存する場合は、それらを_成果物_として {% data variables.product.prodname_dotcom %} に保存できます。 成果物とは、コードをビルドしてテストするときに作成されるファイルのことです。 たとえば、成果物には、バイナリまたパッケージファイル、テスト結果、スクリーンショット、ログファイルなどがあります。 成果物は、それが作成されたワークフロー実行に関連付けられており、別のジョブで使用できます。 {% data reusables.actions.reusable-workflow-artifacts %} たとえば、ファイルを作成し、それを成果物としてアップロードできます。 diff --git a/translations/ja-JP/content/actions/learn-github-actions/events-that-trigger-workflows.md b/translations/ja-JP/content/actions/learn-github-actions/events-that-trigger-workflows.md index 90ee8c2e48..7d7c34fb55 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/events-that-trigger-workflows.md +++ b/translations/ja-JP/content/actions/learn-github-actions/events-that-trigger-workflows.md @@ -17,7 +17,6 @@ shortTitle: ワークフローをトリガーするイベント {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## ワークフローイベントを設定する @@ -165,6 +164,26 @@ on: types: [opened, deleted] ``` +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## Workflow reuse events + +`workflow_call` is a keyword used as the value of `on` in a workflow, in the same way as an event. It indicates that a workflow can be called from another workflow. For more information see, "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." + +### `workflow_call` + +| webhook イベントのペイロード | アクティビティタイプ | `GITHUB_SHA` | `GITHUB_REF` | +| --------------------------- | ---------- | --------------------------- | --------------------------- | +| Same as the caller workflow | n/a | Same as the caller workflow | Same as the caller workflow | + +#### サンプル + +To make a workflow reusable it must include `workflow_call` as one of the values of `on`. The example below only runs the workflow when it's called from another workflow: + +```yaml +on: workflow_call +``` +{% endif %} + ## webhook イベント webhook イベントが {% data variables.product.product_name %} で生成されたときに実行されるようにワークフローを設定できます イベントによっては、そのイベントをトリガーするアクティビティタイプが 複数あります。 イベントをトリガーするアクティビティタイプが複数ある場合は、ワークフローの実行をトリガーするアクティビティタイプを指定できます。 詳しい情報については、「[webhook](/webhooks)」を参照してください。 diff --git a/translations/ja-JP/content/actions/learn-github-actions/expressions.md b/translations/ja-JP/content/actions/learn-github-actions/expressions.md index 81430134b8..912c902260 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/expressions.md +++ b/translations/ja-JP/content/actions/learn-github-actions/expressions.md @@ -12,7 +12,6 @@ miniTocMaxHeadingLevel: 3 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About expressions diff --git a/translations/ja-JP/content/actions/learn-github-actions/finding-and-customizing-actions.md b/translations/ja-JP/content/actions/learn-github-actions/finding-and-customizing-actions.md index f9ad29bf00..a56a521ee8 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/finding-and-customizing-actions.md +++ b/translations/ja-JP/content/actions/learn-github-actions/finding-and-customizing-actions.md @@ -18,7 +18,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 概要 diff --git a/translations/ja-JP/content/actions/learn-github-actions/index.md b/translations/ja-JP/content/actions/learn-github-actions/index.md index bd59039019..f9c8768c82 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/index.md +++ b/translations/ja-JP/content/actions/learn-github-actions/index.md @@ -32,8 +32,10 @@ children: - /finding-and-customizing-actions - /essential-features-of-github-actions - /managing-complex-workflows - - /sharing-workflows-with-your-organization + - /sharing-workflows-secrets-and-runners-with-your-organization + - /creating-workflow-templates - /using-workflow-templates + - /reusing-workflows - /events-that-trigger-workflows - /expressions - /contexts diff --git a/translations/ja-JP/content/actions/learn-github-actions/managing-complex-workflows.md b/translations/ja-JP/content/actions/learn-github-actions/managing-complex-workflows.md index c5170c5e4f..e52a6d7bc0 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/managing-complex-workflows.md +++ b/translations/ja-JP/content/actions/learn-github-actions/managing-complex-workflows.md @@ -13,7 +13,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 概要 @@ -170,10 +169,13 @@ To learn more about self-hosted runner labels, see ["Using labels with self-host {% data variables.product.prodname_dotcom %}-hosted runner labels, see ["Supported runners and hardware resources"](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources). {% endif %} -{% ifversion fpt or ghes > 3.0 %} +{% data reusables.actions.reusable-workflows %} + +{% ifversion fpt or ghes > 3.0 or ghae-next %} + ## 環境の使用 -保護ルールとシークレットを持つ環境を設定できます。 ワークフロー内の各ジョブは、1つの環境を参照できます。 この環境を参照するとジョブがランナーに送信される前に、環境に設定された保護ルールをパスしなければなりません。 詳しい情報については「[環境](/actions/reference/environments)」を参照してください。 +保護ルールとシークレットを持つ環境を設定できます。 ワークフロー内の各ジョブは、1つの環境を参照できます。 この環境を参照するとジョブがランナーに送信される前に、環境に設定された保護ルールをパスしなければなりません。 For more information, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." {% endif %} ## ワークフロー テンプレートの使用 @@ -187,4 +189,4 @@ To learn more about self-hosted runner labels, see ["Using labels with self-host ## 次のステップ -{% data variables.product.prodname_actions %} について詳しくは、「[Organization とワークフローを共有する](/actions/learn-github-actions/sharing-workflows-with-your-organization)」を参照してください。 +To continue learning about {% data variables.product.prodname_actions %}, see "[Sharing workflows, secrets, and runners with your organization](/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization)." diff --git a/translations/ja-JP/content/actions/learn-github-actions/reusing-workflows.md b/translations/ja-JP/content/actions/learn-github-actions/reusing-workflows.md new file mode 100644 index 0000000000..1d41463fc3 --- /dev/null +++ b/translations/ja-JP/content/actions/learn-github-actions/reusing-workflows.md @@ -0,0 +1,195 @@ +--- +title: Reusing workflows +shortTitle: Reusing workflows +intro: Learn how to avoid duplication when creating a workflow by reusing existing workflows. +miniTocMaxHeadingLevel: 3 +versions: + fpt: '*' + ghes: '>=3.4' + ghae: issue-4757 +type: how_to +topics: + - Workflows +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +{% note %} + +**Note:** Reusable workflows are currently in beta and subject to change. + +{% endnote %} + +## 概要 + +Rather than copying and pasting from one workflow to another, you can make workflows reusable. You and anyone with access to the reusable workflow can then call the reusable workflow from another workflow. + +Reusing workflows avoids duplication. This makes workflows easier to maintain and allows you to create new workflows more quickly by building on the work of others, just as you do with actions. Workflow reuse also promotes best practice by helping you to use workflows that are well designed, have already been tested, and have been proved to be effective. Your organization can build up a library of reusable workflows that can be centrally maintained. + +A workflow that uses another workflow is referred to as a "caller" workflow. The reusable workflow is a "called" workflow. One caller workflow can use multiple called workflows. Each called workflow is referenced in a single line. The result is that the caller workflow file may contain just a few lines of YAML, but may perform a large number of tasks when it's run. When you reuse a workflow, the entire called workflow is used, just as if it was part of the caller workflow. + +If you reuse a workflow from a different repository, any actions in the called workflow run as if they were part of the caller workflow. For example, if the called workflow uses `actions/checkout`, the action checks out the contents of the repository that hosts the caller workflow, not the called workflow. + +When a reusable workflow is triggered by a caller workflow, the `github` context is always associated with the caller workflow. For more information about the `github` context, see "[Context and expression syntax for GitHub Actions](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)." + +## Access to reusable workflows + +A reusable workflow can be used by another workflow if any of the following is true: + +* Both workflows are in the same repository. +* The called workflow is stored in a public repository. +* The called workflow is stored in an internal repository and the settings for that repository allow it to be accessed. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#allowing-access-to-components-in-an-internal-repository)." + +## 制限事項 + +* Reusable workflows can't call other reusable workflows. +* Reusable workflows stored within a private repository can only be used by workflows within the same repository. +* Any environment variables set in an `env` context defined at the workflow level in the caller workflow are not be propagated to the called workflow. For more information about the `env` context, see "[Context and expression syntax for GitHub Actions](/actions/reference/context-and-expression-syntax-for-github-actions#env-context)." + +The following limitations will be removed when workflow reuse moves out of beta: +* Reusable workflows can't reference self-hosted runners. +* You can't set the concurrency of a called workflow from the caller workflow. For more information about `jobs..concurrency`, see "[Workflow syntax for GitHub Actions](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idconcurrency)." +* Outputs generated by a called workflow can't be accessed by the caller workflow. + +## Creating a reusable workflow + +Reusable workflows are YAML-formatted files, very similar to any other workflow file. As with other workflow files, you locate reusable workflows in the `.github/workflows` directory of a repository. Subdirectories of the `workflows` directory are not supported. + +For a workflow to be reusable, the values for `on` must include `workflow_call`: + +```yaml +on: + workflow_call: +``` + +You can define inputs and secrets, which can be passed from the caller workflow and then used within the called workflow. The following example, from a reusable workflow, defines two inputs (called "ring" and "environment") and one secret (called "token"): + +```yaml +on: + workflow_call: + inputs: + ring: + description: 'Identifier for the target deployment ring' + default: 'ring-0' + required: false + type: string + environment: + required: false + type: string + secrets: + token: + required: false +``` + +For details of the syntax for defining inputs and secrets, see [on.workflow_call.inputs](/actions/reference/workflow-syntax-for-github-actions#onworkflow_callinputs) and [on.workflow_call.secrets](/actions/reference/workflow-syntax-for-github-actions#onworkflow_callsecrets). + +### Example reusable workflow + +This reusable workflow file named `workflow-B.yml` (we'll refer to this later) takes an input string and a secret from the caller workflow and uses them in an action. + +{% raw %} +```yaml{:copy} +name: Reusable workflow example + +on: + workflow_call: + inputs: + username: + required: true + type: string + secrets: + token: + required: true + +jobs: + example_job: + name: Pass input and secrets to my-action + runs-on: ubuntu-latest + steps: + - uses: ./.github/actions/my-action@v1 + with: + username: ${{ inputs.username }} + token: ${{ secrets.token }} +``` +{% endraw %} + +## Calling a reusable workflow + +You call a reusable workflow by using the `uses` keyword. Unlike when you are using actions within a workflow, you call reusable workflows directly within a job, and not from within job steps. + +[`jobs..uses`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_iduses) + +You reference reusable workflow files using the syntax: + +`{owner}/{repo}/{path}/{filename}@{ref}` + +You can call multiple workflows, referencing each in a separate job. + +{% data reusables.actions.uses-keyword-example %} + +### Passing inputs and secrets to a reusable workflow + +Use the `with` keyword in a job to pass named inputs to the called workflow. Use the `secrets` keyword to pass named secrets. The inputs and secrets you pass must be defined in the called workflow. For inputs, the data type of the input value must match the type specified for that input in the called workflow (boolean, number, or string). + +{% raw %} +```yaml +with: + username: mona +secrets: + token: ${{ secrets.TOKEN }} +``` +{% endraw %} + +### Supported keywords for jobs that call a reusable workflow + +When you call a reusable workflow, you can only use the following keywords in the job containing the call: + +* [`jobs..name`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idname) +* [`jobs..uses`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_iduses) +* [`jobs..with`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idwith) +* [`jobs..with.`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idwithinput_id) +* [`jobs..secrets`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idsecrets) +* [`jobs..secrets.`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idsecretssecret_id) +* [`jobs..needs`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds) +* [`jobs..if`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idif) +* [`jobs..permissions`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idpermissions) + + {% note %} + + **注釈:** + + * If `jobs..permissions` is not specified in the calling job, the called workflow will have the default permissions for the `GITHUB_TOKEN`. 詳しい情報については、「[ワークフローでの認証](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)」を参照してください。 + * The `GITHUB_TOKEN` permissions passed from the caller workflow can be only downgraded (not elevated) by the called workflow. + + {% endnote %} + +### Example caller workflow + +This workflow file calls two workflow files. The second of these, `workflow-B.yml` (shown above), is passed an input, `username`, and a secret, `token`. + +{% raw %} +```yaml{:copy} +name: Call a reusable workflow + +on: + pull_request: + branches: + - main + +jobs: + call-workflow: + uses: octo-org/example-repo/.github/workflows/workflow-A.yml@v1 + + call-workflow-passing-data: + uses: octo-org/example-repo/.github/workflows/workflow-B.yml@main + with: + username: mona + secrets: + token: ${{ secrets.TOKEN }} +``` +{% endraw %} + +## 次のステップ + +To continue learning about {% data variables.product.prodname_actions %}, see "[Events that trigger workflows](/actions/learn-github-actions/events-that-trigger-workflows)." diff --git a/translations/ja-JP/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md b/translations/ja-JP/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md new file mode 100644 index 0000000000..264e4bad3a --- /dev/null +++ b/translations/ja-JP/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md @@ -0,0 +1,53 @@ +--- +title: 'Sharing workflows, secrets, and runners with your organization' +shortTitle: ワークフローを Organization と共有する +intro: ワークフローテンプレート、シークレット、およびセルフホストランナーを共有することで、Organization 機能を使用して Team とコラボレーションする方法を学びます。 +redirect_from: + - /actions/learn-github-actions/sharing-workflows-with-your-organization +versions: + fpt: '*' + ghes: '*' + ghae: '*' +type: how_to +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +## 概要 + +ワークフローやその他の {% data variables.product.prodname_actions %} 機能を Team と共有する必要がある場合は、{% data variables.product.prodname_dotcom %} Organization 内でのコラボレーションを検討します。 Organization を使用すると、シークレット、成果物、およびセルフホストランナーを一元的に保存および管理できます。 `.github` リポジトリにワークフローテンプレートを作成して、Organization 内の他のユーザと共有することもできます。 + +## Using workflow templates + +{% data reusables.actions.workflow-organization-templates %} For more information, see "[Creating workflow templates](/actions/learn-github-actions/creating-workflow-templates)." + +{% data reusables.actions.reusable-workflows %} + +## Organization 内でシークレットを共有する + +Organization 内でシークレットを一元管理し、選択したリポジトリで使用できるようにすることができます。 これは、1 つの場所でシークレットを更新し、その変更をシークレットを使用するすべてのリポジトリワークフローに適用できるということを示します。 + +Organizationでシークレットを作成する場合、ポリシーを使用して、そのシークレットにアクセスできるリポジトリを制限できます。 たとえば、すべてのリポジトリにアクセスを許可したり、プライベート リポジトリまたは指定したリポジトリ のリストのみにアクセスを制限したりできます。 + +{% data reusables.github-actions.permissions-statement-secrets-organization %} + +{% data reusables.organizations.navigate-to-org %} +{% data reusables.organizations.org_settings %} +{% data reusables.github-actions.sidebar-secret %} +1. [**New secret（新しいシークレット）**] をクリックします。 +1. **[Name（名前）]** 入力ボックスにシークレットの名前を入力します。 +1. シークレットの **Value（値）** を入力します。 +1. [ **Repository access（リポジトリアクセス）** ドロップダウン リストから、アクセス ポリシーを選択します。 +1. [**Add secret（シークレットの追加）**] をクリックします。 + +## Organization 内でセルフホストランナーを共有する + +Organization の管理者は、セルフホストランナーをグループに追加してから、グループにアクセスできるリポジトリを制御するポリシーを作成できます。 + +詳しい情報については、「[グループを使用したセルフホストランナーへのアクセスを管理する](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)」を参照してください。 + + +## 次のステップ + +To continue learning about {% data variables.product.prodname_actions %}, see "[Creating workflow templates](/actions/learn-github-actions/creating-workflow-templates)." diff --git a/translations/ja-JP/content/actions/learn-github-actions/understanding-github-actions.md b/translations/ja-JP/content/actions/learn-github-actions/understanding-github-actions.md index 7691527d15..a2370b0bdc 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/understanding-github-actions.md +++ b/translations/ja-JP/content/actions/learn-github-actions/understanding-github-actions.md @@ -18,7 +18,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 概要 @@ -36,7 +35,7 @@ topics: ### ワークフロー -ワークフローは、リポジトリに追加する自動化された手順です。 ワークフローは 1 つ以上のジョブで構成されており、スケジュールまたはイベントによってトリガーできます。 ワークフローを使用して、{% data variables.product.prodname_dotcom %} でプロジェクトをビルド、テスト、パッケージ、リリース、またはデプロイできます。 +ワークフローは、リポジトリに追加する自動化された手順です。 ワークフローは 1 つ以上のジョブで構成されており、スケジュールまたはイベントによってトリガーできます。 ワークフローを使用して、{% data variables.product.prodname_dotcom %} でプロジェクトをビルド、テスト、パッケージ、リリース、またはデプロイできます。 {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %}You can reference a workflow within another workflow, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."{% endif %} ### イベント diff --git a/translations/ja-JP/content/actions/learn-github-actions/usage-limits-billing-and-administration.md b/translations/ja-JP/content/actions/learn-github-actions/usage-limits-billing-and-administration.md index d361c69ae6..34f8d64003 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/usage-limits-billing-and-administration.md +++ b/translations/ja-JP/content/actions/learn-github-actions/usage-limits-billing-and-administration.md @@ -16,7 +16,6 @@ shortTitle: Workflow billing & limits {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## {% data variables.product.prodname_actions %}の支払いについて @@ -61,6 +60,12 @@ There are some limits on {% data variables.product.prodname_actions %} usage whe 使用制限に加えて、{% data variables.product.prodname_actions %}を[GitHubの利用規約](/articles/github-terms-of-service/)内で使っていることを確認しなければなりません。 {% data variables.product.prodname_actions %}の固有の規約に関する詳しい情報については、[GitHubの追加製品規約](/github/site-policy/github-additional-product-terms#a-actions-usage)を参照してください。 {% endif %} +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## Billing for reusable workflows + +If you reuse a workflow, billing is always associated with the caller workflow. For more information see, "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." +{% endif %} + {% ifversion fpt or ghes > 2.22 or ghae %} ## 成果物とログの保持ポリシー diff --git a/translations/ja-JP/content/actions/learn-github-actions/using-workflow-templates.md b/translations/ja-JP/content/actions/learn-github-actions/using-workflow-templates.md index 938877c9e2..a5563ea442 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/using-workflow-templates.md +++ b/translations/ja-JP/content/actions/learn-github-actions/using-workflow-templates.md @@ -1,7 +1,7 @@ --- title: Using workflow templates shortTitle: Using templates -intro: You can set up CI using a workflow template that matches the language and tooling you want to use. +intro: '{% data variables.product.product_name %} provides workflow templates for a variety of languages and tooling.' product: '{% data reusables.gated-features.actions %}' redirect_from: - /articles/setting-up-continuous-integration-using-github-actions @@ -17,34 +17,37 @@ type: tutorial topics: - Workflows - CI + - CD --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -リポジトリへの書き込み権限があるユーザなら誰でも {% data variables.product.prodname_actions %} を使用して継続的インテグレーション (CI) を設定することができます。 +## ワークフローテンプレートについて -CIを設定すると、必要に応じてワークフローをカスタマイズすることができます。 +{% data variables.product.product_name %} offers workflow templates for a variety of languages and tooling. When you set up workflows in your repository, {% data variables.product.product_name %} analyzes the code in your repository and recommends workflows based on the language and framework in your repository. たとえば、[Node.js](https://nodejs.org/en/) を使用する場合、{% data variables.product.product_name %} は、Node.js パッケージをインストールしてテストを実行するテンプレートファイルを提案します。 + +You can also create your own workflow templates to share with your organization. For more information, see "[Creating workflow templates](/actions/learn-github-actions/creating-workflow-templates)." + +## Using workflow templates + +Anyone with write permission to a repository can set up {% data variables.product.prodname_actions %} workflows for CI/CD or other automation. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} -1. 使用したい言語とツールにマッチするテンプレートを探し、[**Set up this workflow**] をクリックします。 ![[Setup workflow] ボタン](/assets/images/help/repository/setup-workflow-button.png) -5. [**Start commit**] をクリックします。 ![[Start commit]ボタン](/assets/images/help/repository/start-commit.png) -{% data reusables.files.write_commit_message %} -{% data reusables.files.choose_commit_branch %} -{% data reusables.files.propose_new_file %} - -リポジトリへのプッシュを実行すると、{% data variables.product.prodname_dotcom %}で実行された継続的インテグレーションワークフローのステータスと詳細ログを追跡し、カスタマイズした通知を受け取ることができます。 詳しい情報については、「[通知を設定する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)」及び「[ワークフローの実行の管理](/articles/managing-a-workflow-run)」を参照してください。 - -{% 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)." +1. If you already have a workflow in your repository, click **New workflow**. +1. Find the template that you want to use, then click **Set up this workflow**. +1. If the workflow template contains comments detailing additional setup steps, follow these steps. +1. Some workflow templates use secrets. For example, {% raw %}`${{ secrets.npm_token }}`{% endraw %}. If the workflow template uses a secret, store the value described in the secret name as a secret in your repository. For more information, see "[Encrypted secrets](/actions/reference/encrypted-secrets)." +1. Optionally, make additional changes. For example, you might want to change the value of `on` to change when the workflow runs. +1. [**Start commit**] をクリックします。 +1. Write a commit message and decide whether to commit directly to the default branch or to open a pull request. ## 参考リンク - [継続的インテグレーションについて](/articles/about-continuous-integration) -- "[ワークフロー実行の管理](/articles/managing-a-workflow-run)" +- "[Managing workflow runs](/actions/managing-workflow-runs)" +- "[About monitoring and troubleshooting](/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting)" - 「[{% data variables.product.prodname_actions %} を学ぶ](/actions/learn-github-actions)」 {% ifversion fpt %} - 「[{% data variables.product.prodname_actions %} の支払いを管理する](/billing/managing-billing-for-github-actions)」 diff --git a/translations/ja-JP/content/actions/learn-github-actions/workflow-commands-for-github-actions.md b/translations/ja-JP/content/actions/learn-github-actions/workflow-commands-for-github-actions.md index a6f050937a..31833df7a0 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/workflow-commands-for-github-actions.md +++ b/translations/ja-JP/content/actions/learn-github-actions/workflow-commands-for-github-actions.md @@ -18,7 +18,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## ワークフローコマンドについて @@ -89,7 +88,7 @@ core.setOutput('SELECTED_COLOR', 'green'); | `core.setOutput` | `set-output` | | `core.setSecret` | `add-mask` | | `core.startGroup` | `group` | -| `core.warning` | `warning file` | +| `core.warning` | `警告` | {% ifversion ghes < 3.0 %} ## 環境変数の設定 @@ -331,6 +330,12 @@ echo "{name}={value}" >> $GITHUB_ENV Creates or updates an environment variable for any steps running next in a job. The step that creates or updates the environment variable does not have access to the new value, but all subsequent steps in a job will have access. 環境変数では、大文字と小文字が区別され、句読点を含めることができます。 +{% note %} + +**Note:** Environment variables must be explicitly referenced using the [`env` context](/actions/reference/context-and-expression-syntax-for-github-actions#env-context) in expression syntax or through use of the `$GITHUB_ENV` file directly; environment variables are not implicitly available in shell commands. + +{% endnote %} + ### サンプル {% raw %} @@ -376,7 +381,7 @@ steps: echo "{path}" >> $GITHUB_PATH ``` -システムの`PATH`変数の先頭にディレクトリを追加し、現在のジョブ中の以降のすべてのアクションで利用できるようにします。現在実行中のアクションは、更新されたPATH変数にアクセスできません。 ジョブに現在定義されているパスを見るには、ステップもしくはアクション中で`echo "$PATH"`を使うことができます。 +Prepends a directory to the system `PATH` variable and automatically makes it available to all subsequent actions in the current job; the currently running action cannot access the updated path variable. ジョブに現在定義されているパスを見るには、ステップもしくはアクション中で`echo "$PATH"`を使うことができます。 ### サンプル diff --git a/translations/ja-JP/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md b/translations/ja-JP/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md index afb20b8287..758303dbfa 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md +++ b/translations/ja-JP/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md @@ -16,7 +16,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## ワークフロー用のYAML構文について @@ -184,9 +183,91 @@ Diffs are limited to 300 files. If there are files changed that aren't matched i 詳しい情報については「[Pull Request中のブランチの比較について](/articles/about-comparing-branches-in-pull-requests)」を参照してください。 +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## `on.workflow_call.inputs` + +When using the `workflow_call` keyword, you can optionally specify inputs that are passed to the called workflow from the caller workflow. Inputs for reusable workflows are specified with the same format as action inputs. For more information about inputs, see "[Metadata syntax for GitHub Actions](/actions/creating-actions/metadata-syntax-for-github-actions#inputs)." For more information about the `workflow_call` keyword, see "[Events that trigger workflows](/actions/learn-github-actions/events-that-trigger-workflows#workflow-reuse-events)." + +In addition to the standard input parameters that are available, `on.workflow_call.inputs` requires a `type` parameter. For more information, see [`on.workflow_call..type`](#onworkflow_callinput_idtype). + +If a `default` parameter is not set, the default value of the input is `false` for a boolean, `0` for a number, and `""` for a string. + +Within the called workflow, you can use the `inputs` context to refer to an input. + +If a caller workflow passes an input that is not specified in the called workflow, this results in an error. + +### サンプル + +{% raw %} +```yaml +on: + workflow_call: + inputs: + username: + description: 'A username passed from the caller workflow' + default: 'john-doe' + required: false + type: string + +jobs: + print-username: + runs-on: ubuntu-latest + + steps: + - name: Print the input name to STDOUT + run: echo The username is ${{ inputs.username }} +``` +{% endraw %} + +For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." + +## `on.workflow_call..type` + +Required if input is defined for the `on.workflow_call` keyword. The value of this parameter is a string specifying the data type of the input. This must be one of: `boolean`, `number`, or `string`. + +## `on.workflow_call.secrets` + +A map of the secrets that can be used in the called workflow. + +Within the called workflow, you can use the `secrets` context to refer to a secret. + +If a caller workflow passes a secret that is not specified in the called workflow, this results in an error. + +### サンプル + +{% raw %} +```yaml +on: + workflow_call: + secrets: + access-token: + description: 'A token passed from the caller workflow' + required: false + +jobs: + pass-secret-to-action: + runs-on: ubuntu-latest + + steps: + - name: Pass the received secret to an action + uses: ./.github/actions/my-action@v1 + with: + token: ${{ secrets.access-token }} +``` +{% endraw %} + +## `on.workflow_call.secrets.` + +A string identifier to associate with the secret. + +## `on.workflow_call.secrets..required` + +A boolean specifying whether the secret must be supplied. +{% endif %} + ## `on.workflow_dispatch.inputs` -When using `workflow_dispatch` event, you can optionally specify inputs that are passed to the workflow. Workflow dispatch inputs are specified with the same format as action inputs. For more information about the format see "[Metadata syntax for GitHub Actions](/actions/creating-actions/metadata-syntax-for-github-actions#inputs)." +When using the `workflow_dispatch` event, you can optionally specify inputs that are passed to the workflow. Workflow dispatch inputs are specified with the same format as action inputs. For more information about the format see "[Metadata syntax for GitHub Actions](/actions/creating-actions/metadata-syntax-for-github-actions#inputs)." ```yaml on: @@ -272,8 +353,6 @@ defaults: {% ifversion fpt or ghae-next or ghes > 3.1 %} ## `concurrency` -{% data reusables.actions.concurrency-beta %} - 並行処理により、同じ並行処理グループを使用する単一のジョブまたはワークフローのみが一度に実行されます。 並行処理グループには、任意の文字列または式を使用できます。 The expression can only use the [`github` context](/actions/learn-github-actions/contexts#github-context). For more information about expressions, see "[Expressions](/actions/learn-github-actions/expressions)." ジョブレベルで `concurrency` を指定することもできます。 詳しい情報については、[`jobs..concurrency`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idconcurrency) を参照してください。 @@ -428,7 +507,7 @@ jobs: {% ifversion fpt or ghes > 3.0 or ghae %} ## `jobs..environment` -ジョブが参照する環境。 環境を参照するジョブがランナーに送られる前に、その環境のすべて保護ルールはパスしなければなりません。 詳しい情報については「[環境](/actions/reference/environments)」を参照してください。 +ジョブが参照する環境。 環境を参照するジョブがランナーに送られる前に、その環境のすべて保護ルールはパスしなければなりません。 For more information, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." 環境は、環境の`name`だけで、あるいは`name` and `url`を持つenvironmentオブジェクトとして渡すことができます。 デプロイメントAPIでは、このURLは`environment_url`にマップされます。 デプロイメントAPIに関する詳しい情報については「[デプロイメント](/rest/reference/repos#deployments)」を参照してください。 @@ -463,8 +542,6 @@ environment: {% ifversion fpt or ghae-next or ghes > 3.1 %} ## `jobs..concurrency` -{% data reusables.actions.concurrency-beta %} - {% note %} **注釈:** ジョブレベルで並行処理が指定されている場合、ジョブの順序は保証されないか、互いに 5 分以内にそのキューを実行します。 @@ -1348,6 +1425,70 @@ volumes: {% endwarning %} +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## `jobs..uses` + +The location and version of a reusable workflow file to run as a job. + +`{owner}/{repo}/{path}/{filename}@{ref}` + +`{ref}` can be a SHA, a release tag, or a branch name. Using the commit SHA is the safest for stability and security. 詳しい情報については「[GitHub Actionsのためのセキュリティ強化](/actions/learn-github-actions/security-hardening-for-github-actions#reusing-third-party-workflows)」を参照してください。 + +### サンプル + +{% data reusables.actions.uses-keyword-example %} + +For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." + +## `jobs..with` + +When a job is used to call a reusable workflow, you can use `with` to provide a map of inputs that are passed to the called workflow. + +Any inputs that you pass must match the input specifications defined in the called workflow. + +Unlike [`jobs..steps[*].with`](#jobsjob_idstepswith), the inputs you pass with `jobs..with` are not be available as environment variables in the called workflow. Instead, you can reference the inputs by using the `inputs` context. + +### サンプル + +```yaml +jobs: + call-workflow: + uses: octo-org/example-repo/.github/workflows/called-workflow.yml@main + with: + username: mona +``` + +## `jobs..with.` + +A pair consisting of a string identifier for the input and the value of the input. The identifier must match the name of an input defined by [`on.workflow_call.inputs.`](/actions/creating-actions/metadata-syntax-for-github-actions#inputsinput_id) in the called workflow. The data type of the value must match the type defined by [`on.workflow_call..type`](#onworkflow_callinput_idtype) in the called workflow. + +Allowed expression contexts: `github`, and `needs`. + +## `jobs..secrets` + +When a job is used to call a reusable workflow, you can use `secrets` to provide a map of secrets that are passed to the called workflow. + +Any secrets that you pass must match the names defined in the called workflow. + +### サンプル + +{% raw %} +```yaml +jobs: + call-workflow: + uses: octo-org/example-repo/.github/workflows/called-workflow.yml@main + secrets: + access-token: ${{ secrets.PERSONAL_ACCESS_TOKEN }} +``` +{% endraw %} + +## `jobs..secrets.` + +A pair consisting of a string identifier for the secret and the value of the secret. The identifier must match the name of a secret defined by [`on.workflow_call.secrets.`](#onworkflow_callsecretssecret_id) in the called workflow. + +Allowed expression contexts: `github`, `needs`, and `secrets`. +{% endif %} + ## フィルタパターンのチートシート 特別なキャラクタをパス、ブランチ、タグフィルタで利用できます。 diff --git a/translations/ja-JP/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md b/translations/ja-JP/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md index 146944fa5e..766481ea16 100644 --- a/translations/ja-JP/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md +++ b/translations/ja-JP/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md @@ -16,8 +16,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## はじめに diff --git a/translations/ja-JP/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md b/translations/ja-JP/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md index 1cda1f1233..9154785508 100644 --- a/translations/ja-JP/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md +++ b/translations/ja-JP/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md @@ -16,8 +16,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## はじめに diff --git a/translations/ja-JP/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md b/translations/ja-JP/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md index 3f7db0b01c..64bfd27236 100644 --- a/translations/ja-JP/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md +++ b/translations/ja-JP/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md @@ -17,8 +17,6 @@ shortTitle: Add label to comment on issue {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## はじめに diff --git a/translations/ja-JP/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md b/translations/ja-JP/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md index aa0918e638..2aa8b96e59 100644 --- a/translations/ja-JP/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md +++ b/translations/ja-JP/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md @@ -17,8 +17,6 @@ shortTitle: Move assigned issues {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## はじめに diff --git a/translations/ja-JP/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md b/translations/ja-JP/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md index 5946a93324..4d0ce9bd03 100644 --- a/translations/ja-JP/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md +++ b/translations/ja-JP/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md @@ -17,8 +17,6 @@ shortTitle: Remove label when adding card {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## はじめに diff --git a/translations/ja-JP/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md b/translations/ja-JP/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md index a162952cb9..ad48869e68 100644 --- a/translations/ja-JP/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md +++ b/translations/ja-JP/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md @@ -16,8 +16,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## はじめに diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md b/translations/ja-JP/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md index 53dd996076..55d34722e5 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md @@ -9,7 +9,9 @@ shortTitle: Approve public fork runs ## About workflow runs from public forks -{% data reusables.actions.workflow-run-approve-public-fork %} However, you can configure this behavior for a [repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks), [organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#configuring-required-approval-for-workflows-from-public-forks), or [enterprise](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account#configuring-required-approval-for-workflows-from-public-forks). +{% data reusables.actions.workflow-run-approve-public-fork %} + +You can configure workflow approval requirements for a [repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks), [organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#configuring-required-approval-for-workflows-from-public-forks), or [enterprise](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account#configuring-required-approval-for-workflows-from-public-forks). Workflow runs that have been awaiting approval for more than 30 days are automatically deleted. diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/canceling-a-workflow.md b/translations/ja-JP/content/actions/managing-workflow-runs/canceling-a-workflow.md index 27a141a2f5..945943517f 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/canceling-a-workflow.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/canceling-a-workflow.md @@ -10,7 +10,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.repositories.permissions-statement-write %} diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/deleting-a-workflow-run.md b/translations/ja-JP/content/actions/managing-workflow-runs/deleting-a-workflow-run.md index aa4c8a4327..0a5fe7268d 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/deleting-a-workflow-run.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/deleting-a-workflow-run.md @@ -10,7 +10,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.repositories.permissions-statement-write %} diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md b/translations/ja-JP/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md index 49fcacc9f1..0c2f3d15b4 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md @@ -11,7 +11,6 @@ shortTitle: Disable & enable a workflow {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ワークフローを無効にすると、リポジトリからファイルを削除することなく、ワークフローがトリガーされないようにすることができます。 {% data variables.product.prodname_dotcom %} でワークフローを簡単に再度有効にすることができます。 diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md b/translations/ja-JP/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md index 5bf977b24f..11eb407453 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md @@ -11,7 +11,6 @@ shortTitle: Download workflow artifacts {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% ifversion fpt or ghes > 2.22 or ghae %}デフォルトでは、{% data variables.product.product_name %} はビルドログと成果物を 90 日間保存します。リポジトリのタイプに応じて、この保持期間をカスタマイズできます。 For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)."{% endif %} {% ifversion ghes = 2.22 %} {% data variables.product.product_name %} には、完全なビルドログと成果物が 90 日間保存されます。{% endif %} diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/index.md b/translations/ja-JP/content/actions/managing-workflow-runs/index.md index d61e784321..990dd13f97 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/index.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/index.md @@ -19,6 +19,7 @@ children: - /approving-workflow-runs-from-public-forks - /reviewing-deployments - /disabling-and-enabling-a-workflow + - /skipping-workflow-runs - /deleting-a-workflow-run - /downloading-workflow-artifacts - /removing-workflow-artifacts @@ -26,5 +27,3 @@ children: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% ifversion fpt or ghes > 3.0 or ghae %}{% endif %} diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/manually-running-a-workflow.md b/translations/ja-JP/content/actions/managing-workflow-runs/manually-running-a-workflow.md index 43ebc5ecf6..5f9e387490 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/manually-running-a-workflow.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/manually-running-a-workflow.md @@ -11,7 +11,6 @@ shortTitle: Manually run a workflow {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## ワークフローを手動実行する設定 diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/re-running-a-workflow.md b/translations/ja-JP/content/actions/managing-workflow-runs/re-running-a-workflow.md index c7299c7e52..0953064509 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/re-running-a-workflow.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/re-running-a-workflow.md @@ -11,7 +11,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} Re-running a workflow uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (Git ref) of the original event that triggered the workflow run. You can re-run a workflow up to 30 days after the initial run. diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/removing-workflow-artifacts.md b/translations/ja-JP/content/actions/managing-workflow-runs/removing-workflow-artifacts.md index fc5681ba77..24753fa7d1 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/removing-workflow-artifacts.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/removing-workflow-artifacts.md @@ -11,7 +11,6 @@ shortTitle: Remove workflow artifacts {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 成果物を削除する diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/reviewing-deployments.md b/translations/ja-JP/content/actions/managing-workflow-runs/reviewing-deployments.md index 923141780e..37b7c2ddba 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/reviewing-deployments.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/reviewing-deployments.md @@ -8,13 +8,12 @@ versions: ghae: '*' --- -{% data reusables.actions.ae-beta %} ## ワークフローで必須のレビューについて 必須のレビュー担当者が設定された環境を参照するジョブは、開始前に承認を待ちます。 承認を待っている間のジョブは、ステータスが"Waiting"になります。 ジョブが30日以内に承認されなければ、そのワークフローは自動的にキャンセルされます。 -環境と必要な承認の詳細については、「[環境](/actions/reference/environments)」を参照してください。{% ifversion fpt or ghae-next or ghes > 3.1 %}REST API を使用してデプロイメントをレビューする方法については、「[ワークフローの実行](/rest/reference/actions#workflow-runs)」を参照してください。{% endif %} +For more information about environments and required approvals, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)."{% ifversion fpt or ghae-next or ghes > 3.1 %} For information about how to review deployments with the REST API, see "[Workflow Runs](/rest/reference/actions#workflow-runs)."{% endif %} ## ジョブの承認もしくは拒否 diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/skipping-workflow-runs.md b/translations/ja-JP/content/actions/managing-workflow-runs/skipping-workflow-runs.md new file mode 100644 index 0000000000..6442c38c92 --- /dev/null +++ b/translations/ja-JP/content/actions/managing-workflow-runs/skipping-workflow-runs.md @@ -0,0 +1,33 @@ +--- +title: ワークフロー実行をスキップする +intro: You can skip workflow runs triggered by the `push` and `pull_request` events by including a command in your commit message. +product: '{% data reusables.gated-features.actions %}' +versions: + fpt: '*' + ghes: '>=3.0' + ghae: ghae-next +shortTitle: Skip workflow runs +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +Workflows that would otherwise be triggered using `on: push` or `on: pull_request` won't be triggered if you add any of the following strings to the commit message in a push, or the HEAD commit of a pull request: + +* `[skip ci]` +* `[ci skip]` +* `[no ci]` +* `[skip actions]` +* `[actions skip]` + +または、コミットメッセージを 2 行の空行で終了し、その後に `skip-checks: true` または `skip-checks:true` のいずれかを続けることもできます。 + +最初にリポジトリがパスするための特定のチェックを受けるように設定されている場合、プルリクエストをマージすることはできません。 プルリクエストをマージできるようにするには、コミットメッセージのスキップ命令なしでプルリクエストに新しいコミットをプッシュできます。 + +{% note %} + +**注釈:** スキップ命令は、`push` および `pull_request` イベントにのみ適用されます。 たとえば、コミットメッセージに `[skip ci]` を追加しても、`on: pull_request_target` でトリガーされたワークフロー実行は停止されません。 + +{% endnote %} + +Skip instructions only apply to the workflow run(s) that would be triggered by the commit that contains the skip instructions. You can also disable a workflow from running. 詳しい情報については、「[ワークフローの無効化と有効化](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)」を参照してください。 diff --git a/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md b/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md index c19b3350bd..bd90744d7e 100644 --- a/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md +++ b/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md @@ -19,7 +19,6 @@ shortTitle: Migrate from Azure Pipelines {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## はじめに diff --git a/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md b/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md index 035f67bec4..ae91b3eac5 100644 --- a/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md +++ b/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md @@ -19,7 +19,6 @@ shortTitle: Migrate from CircleCI {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## はじめに diff --git a/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md b/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md index bbff12b464..940afc981b 100644 --- a/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md +++ b/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md @@ -18,7 +18,6 @@ shortTitle: Migrate from GitLab CI/CD {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## はじめに diff --git a/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md b/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md index 586bfba566..5fdd766f6f 100644 --- a/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md +++ b/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md @@ -19,7 +19,6 @@ shortTitle: Migrate from Jenkins {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## はじめに 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 0cd1e178b5..4705d5d1fd 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 @@ -19,7 +19,6 @@ shortTitle: Migrate from Travis CI {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## はじめに diff --git a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md index 6dae8e1881..edba6dc659 100644 --- a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md +++ b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md @@ -12,7 +12,6 @@ miniTocMaxHeadingLevel: 3 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Monitoring your workflows diff --git a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md index 99c81b9cda..25a295578e 100644 --- a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md +++ b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md @@ -13,7 +13,6 @@ shortTitle: Add a status badge {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.repositories.actions-workflow-status-badge-intro %} diff --git a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md index dd2aef28e7..8901edbc45 100644 --- a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md +++ b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md @@ -12,7 +12,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} これらの追加ログは、ワークフローを含むリポジトリにシークレットを設定することで有効になるため、同じ権限要件が適用されます。 diff --git a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/index.md b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/index.md index bda6bc8ded..36ad81e817 100644 --- a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/index.md +++ b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/index.md @@ -17,9 +17,8 @@ children: - /viewing-job-execution-time - /using-workflow-run-logs - /enabling-debug-logging + - /notifications-for-workflow-runs --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% ifversion fpt or ghes > 3.0 or ghae %}{% endif %} diff --git a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md new file mode 100644 index 0000000000..bc06639561 --- /dev/null +++ b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md @@ -0,0 +1,15 @@ +--- +title: ワークフロー実行の通知 +intro: You can subscribe to notifications about workflow runs that you trigger. +product: '{% data reusables.gated-features.actions %}' +versions: + fpt: '*' + ghes: '*' + ghae: '*' +shortTitle: 通知 +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +{% data reusables.repositories.workflow-notifications %} diff --git a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md index 016c8a2156..d545da56df 100644 --- a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md +++ b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md @@ -13,7 +13,6 @@ shortTitle: Use the visualization graph {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} diff --git a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md index 8ca5dac1ed..73ca1413ee 100644 --- a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md +++ b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md @@ -12,7 +12,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ワークフローの実行ページから、ワークフローの実行が進行中か完了しているかを確認できます。 パブリックなリポジトリの分も含むワークフローの実行情報を見るには、{% data variables.product.prodname_dotcom %}のアカウントにログインしなければなりません。 詳細は「[GitHub 上のアクセス権限](/articles/access-permissions-on-github)」を参照してください。 diff --git a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md index 17a76179e4..b930588a3a 100644 --- a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md +++ b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md @@ -11,7 +11,6 @@ shortTitle: View job execution time {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} 請求可能なジョブ実行時間（分）は、{% data variables.product.prodname_dotcom %} ホストランナーを使用するプライベートリポジトリで実行されるジョブに対してのみ表示されます。 パブリックリポジトリで {% data variables.product.prodname_actions %} を使用する場合、またはセルフホストランナーで実行されるジョブの場合、請求対象となる実行時間はありません。 diff --git a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md index c2d94c4cd1..597a99eca9 100644 --- a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md +++ b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md @@ -13,7 +13,6 @@ shortTitle: View workflow run history {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.repositories.permissions-statement-read %} diff --git a/translations/ja-JP/content/actions/publishing-packages/about-packaging-with-github-actions.md b/translations/ja-JP/content/actions/publishing-packages/about-packaging-with-github-actions.md index 3d8ecdef93..bc7fe2a8cd 100644 --- a/translations/ja-JP/content/actions/publishing-packages/about-packaging-with-github-actions.md +++ b/translations/ja-JP/content/actions/publishing-packages/about-packaging-with-github-actions.md @@ -18,7 +18,6 @@ shortTitle: Packaging with GitHub Actions {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.package_registry.about-packaging-and-actions %} diff --git a/translations/ja-JP/content/actions/publishing-packages/publishing-docker-images.md b/translations/ja-JP/content/actions/publishing-packages/publishing-docker-images.md index 32bac23545..6efa2da955 100644 --- a/translations/ja-JP/content/actions/publishing-packages/publishing-docker-images.md +++ b/translations/ja-JP/content/actions/publishing-packages/publishing-docker-images.md @@ -18,7 +18,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## はじめに diff --git a/translations/ja-JP/content/actions/publishing-packages/publishing-java-packages-with-gradle.md b/translations/ja-JP/content/actions/publishing-packages/publishing-java-packages-with-gradle.md index 5a10d6288b..690ecd235a 100644 --- a/translations/ja-JP/content/actions/publishing-packages/publishing-java-packages-with-gradle.md +++ b/translations/ja-JP/content/actions/publishing-packages/publishing-java-packages-with-gradle.md @@ -20,7 +20,6 @@ shortTitle: Java packages with Gradle {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## はじめに diff --git a/translations/ja-JP/content/actions/publishing-packages/publishing-java-packages-with-maven.md b/translations/ja-JP/content/actions/publishing-packages/publishing-java-packages-with-maven.md index f4f5504c5a..55463f956a 100644 --- a/translations/ja-JP/content/actions/publishing-packages/publishing-java-packages-with-maven.md +++ b/translations/ja-JP/content/actions/publishing-packages/publishing-java-packages-with-maven.md @@ -20,7 +20,6 @@ shortTitle: Java packages with Maven {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## はじめに diff --git a/translations/ja-JP/content/actions/publishing-packages/publishing-nodejs-packages.md b/translations/ja-JP/content/actions/publishing-packages/publishing-nodejs-packages.md index 006d1e9d61..0fad7c5a8a 100644 --- a/translations/ja-JP/content/actions/publishing-packages/publishing-nodejs-packages.md +++ b/translations/ja-JP/content/actions/publishing-packages/publishing-nodejs-packages.md @@ -21,7 +21,6 @@ shortTitle: Node.js packages {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## はじめに diff --git a/translations/ja-JP/content/actions/quickstart.md b/translations/ja-JP/content/actions/quickstart.md index ce520a7889..c1191890e2 100644 --- a/translations/ja-JP/content/actions/quickstart.md +++ b/translations/ja-JP/content/actions/quickstart.md @@ -16,7 +16,6 @@ shortTitle: クイックスタート {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## はじめに diff --git a/translations/ja-JP/content/actions/security-guides/automatic-token-authentication.md b/translations/ja-JP/content/actions/security-guides/automatic-token-authentication.md index 8728c5e359..1763457dec 100644 --- a/translations/ja-JP/content/actions/security-guides/automatic-token-authentication.md +++ b/translations/ja-JP/content/actions/security-guides/automatic-token-authentication.md @@ -16,7 +16,6 @@ shortTitle: Automatic token authentication {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## `GITHUB_TOKEN`シークレットについて diff --git a/translations/ja-JP/content/actions/security-guides/encrypted-secrets.md b/translations/ja-JP/content/actions/security-guides/encrypted-secrets.md index 11825ef5b7..46ef192893 100644 --- a/translations/ja-JP/content/actions/security-guides/encrypted-secrets.md +++ b/translations/ja-JP/content/actions/security-guides/encrypted-secrets.md @@ -16,7 +16,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 暗号化されたシークレットについて diff --git a/translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md b/translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md index 1001ff6b6d..db816f74f8 100644 --- a/translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md +++ b/translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md @@ -18,7 +18,6 @@ miniTocMaxHeadingLevel: 3 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 概要 @@ -48,7 +47,7 @@ miniTocMaxHeadingLevel: 3 - シークレットを定期的にローテーションして、不正使用されたシークレットが有効である期間を短縮します。 {% ifversion fpt or ghes > 3.0 or ghae %} - **シークレットへのアクセスのレビューを必須とすることを検討する** - - 必須のレビュー担当者を使って環境のシークレットを保護できます。 レビュー担当者によって許可されるまで、ワークフローのジョブは環境のシークレットにアクセスできません。 緩急尾へのシークレットの保存、あるいは環境にレビュー担当者を必須とすることの詳細については、「[暗号化されたシークレット](/actions/reference/encrypted-secrets)」及び「[環境](/actions/reference/environments)」を参照してください。 + - 必須のレビュー担当者を使って環境のシークレットを保護できます。 レビュー担当者によって許可されるまで、ワークフローのジョブは環境のシークレットにアクセスできません。 For more information about storing secrets in environments or requiring reviews for environments, see "[Encrypted secrets](/actions/reference/encrypted-secrets)" and "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." {% endif %} ## Using `CODEOWNERS` to monitor changes @@ -183,6 +182,12 @@ To help mitigate the risk of an exposed token, consider restricting the assigned コミット SHA に対するピン止めが最も安全なオプションですが、タグを指定する方が便利で広く使用されています。 タグを指定する場合は、アクションの作成者が信頼できることを確認してください。 {% data variables.product.prodname_marketplace %} の「Verified creator」バッジは便利な判断材料で、 {% data variables.product.prodname_dotcom %} で身元が確認されたチームによって作成されたアクションであることを示しています。 作者が信頼できる場合でも、このアプローチにはリスクがあることに注意してください。悪意のある人がアクションを保存しているリポジトリにアクセスすると、タグが移動または削除される可能性があります。 +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## Reusing third-party workflows + +The same principles described above for using third-party actions also apply to using third-party workflows. You can help mitigate the risks associated with reusing workflows by following the same good practices outlined above. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." +{% endif %} + ## Potential impact of a compromised runner These sections consider some of the steps an attacker can take if they're able to run malicious commands on a {% data variables.product.prodname_actions %} runner. diff --git a/translations/ja-JP/content/actions/using-containerized-services/about-service-containers.md b/translations/ja-JP/content/actions/using-containerized-services/about-service-containers.md index 872260c2f7..c50d91ec9a 100644 --- a/translations/ja-JP/content/actions/using-containerized-services/about-service-containers.md +++ b/translations/ja-JP/content/actions/using-containerized-services/about-service-containers.md @@ -18,7 +18,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## サービスコンテナについて diff --git a/translations/ja-JP/content/actions/using-containerized-services/creating-postgresql-service-containers.md b/translations/ja-JP/content/actions/using-containerized-services/creating-postgresql-service-containers.md index 3ef3c0b4f5..db5842d75b 100644 --- a/translations/ja-JP/content/actions/using-containerized-services/creating-postgresql-service-containers.md +++ b/translations/ja-JP/content/actions/using-containerized-services/creating-postgresql-service-containers.md @@ -19,7 +19,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## はじめに diff --git a/translations/ja-JP/content/actions/using-containerized-services/creating-redis-service-containers.md b/translations/ja-JP/content/actions/using-containerized-services/creating-redis-service-containers.md index 5988aebb16..4c1edb8f90 100644 --- a/translations/ja-JP/content/actions/using-containerized-services/creating-redis-service-containers.md +++ b/translations/ja-JP/content/actions/using-containerized-services/creating-redis-service-containers.md @@ -19,7 +19,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## はじめに diff --git a/translations/ja-JP/content/actions/using-github-hosted-runners/about-ae-hosted-runners.md b/translations/ja-JP/content/actions/using-github-hosted-runners/about-ae-hosted-runners.md index 73b2f9e299..5eca1a99b4 100644 --- a/translations/ja-JP/content/actions/using-github-hosted-runners/about-ae-hosted-runners.md +++ b/translations/ja-JP/content/actions/using-github-hosted-runners/about-ae-hosted-runners.md @@ -6,23 +6,16 @@ versions: ghae: '*' --- - - - -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} ## {% data variables.actions.hosted_runner %} について -An {% data variables.actions.hosted_runner %} is a virtual machine hosted by {% data variables.product.prodname_dotcom %} with the {% data variables.product.prodname_actions %} runner service installed. +An {% data variables.actions.hosted_runner %} is a virtual machine managed by {% data variables.product.prodname_dotcom %} with the {% data variables.product.prodname_actions %} runner service installed. {% data variables.actions.hosted_runner %}s are dedicated to your enterprise, and you can choose from a range of hardware and software options. By default, {% data variables.actions.hosted_runner %}s are fully managed and auto-scaled by {% data variables.product.company_short %} to maximize performance while minimizing costs.{% ifversion ghae-next %} You can optionally configure the parameters of this auto-scaling to reduce your cost even more.{% endif %} -{% data variables.product.prodname_ghe_managed %} lets you create and customize {% data variables.actions.hosted_runner %}s using Ubuntu or Windows images; you can select the size of machine you want and configure security hardened networking for them. {% data variables.actions.hosted_runner %}s are fully managed and auto-scaled by {% data variables.product.prodname_dotcom %}. +{% data variables.product.prodname_ghe_managed %} lets you create and customize {% data variables.actions.hosted_runner %}s using Ubuntu or Windows images; you can select the size of machine you want and optionally configure a fixed public IP range for your {% data variables.actions.hosted_runner %}s. Each workflow job is executed in a fresh instance of the {% data variables.actions.hosted_runner %}, and you can run workflows directly on the virtual machine or in a Docker container. All steps in the job execute in the same instance, allowing the actions in that job to share information using the {% data variables.actions.hosted_runner %}'s filesystem. -{% note %} -{% data variables.actions.hosted_runner %}s are the only runners available for {% data variables.product.prodname_ghe_managed %}, and self-hosted runners are not available. -{% endnote %} - To add {% data variables.actions.hosted_runner %}s to your organization or enterprise, see ["Adding {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/adding-ae-hosted-runners)." ## Pool assignments for {% data variables.actions.hosted_runner %}s @@ -35,11 +28,9 @@ During the {% data variables.actions.hosted_runner %} beta, you can manage your ## 支払い -{% data variables.product.prodname_actions %} is currently in beta for {% data variables.product.prodname_ghe_managed %}. During this beta period, {% data variables.actions.hosted_runner %}s are not billed, and can be used for free. - Once the beta ends, billed usage will include the full uptime of active instances in your AE hosted runner sets. これは以下のものが含まれます。 - Job time - minutes spent running Actions job. -- Management - minutes spent re-imaging machines and any idle time created as a result of desired auto-scale behavior. +- Management - minutes spent re-imaging machines{% ifversion ghae-next %} and any idle time created as a result of desired auto-scale behavior{% endif %}. Pricing will scale linearly with cores. For example, 4 cores will be twice the price of 2 cores. Windows VMs will be priced higher than Linux VMs. @@ -78,6 +69,14 @@ To get a list of IP address ranges that {% data variables.product.prodname_actio このAPIが返す{% data variables.product.prodname_actions %}のIPアドレスのリストは、週に1回更新されます。 +{% ifversion ghae-next %} + +## Autoscaling + +Each pool of {% data variables.actions.hosted_runner %}s is fully managed by {% data variables.product.company_short %} to maximize performance while minimizing costs. Optionally, you can configure the autoscaling parameters for your enterprise by contacting {% data variables.contact.github_support %}. You can define the minimum number of idle runners and how long a runner should remain idle before being removed from the pool. Each pool can contain up to 600 runners. + +{% endif %} + ## Administrative privileges for {% data variables.actions.hosted_runner %}s The Linux virtual machines run using passwordless `sudo`. 現在のユーザが持っているよりも高い権限が求められるコマンドやインストールツールを実行する必要がある場合は、パスワードを入力する必要なく、`sudo`を使うことができます。 詳しい情報については、「[Sudo Manual](https://www.sudo.ws/man/1.8.27/sudo.man.html)」を参照してください。 diff --git a/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md index f6304a4b47..b2f219be6d 100644 --- a/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md +++ b/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md @@ -16,6 +16,7 @@ versions: shortTitle: GitHub-hosted runners --- +{% data reusables.actions.ae-hosted-runners-beta %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} diff --git a/translations/ja-JP/content/actions/using-github-hosted-runners/adding-ae-hosted-runners.md b/translations/ja-JP/content/actions/using-github-hosted-runners/adding-ae-hosted-runners.md index fea7ce43a0..f68a137f2e 100644 --- a/translations/ja-JP/content/actions/using-github-hosted-runners/adding-ae-hosted-runners.md +++ b/translations/ja-JP/content/actions/using-github-hosted-runners/adding-ae-hosted-runners.md @@ -5,7 +5,7 @@ versions: ghae: '*' --- -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} {% note %} @@ -19,7 +19,8 @@ versions: You can add {% data variables.actions.hosted_runner %}s that use the base Azure operating system images. To add {% data variables.actions.hosted_runner %}s to your organization or enterprise, contact {% data variables.product.prodname_dotcom %} support and have the following information ready: - Required operating system: Available options are listed at ["Software specifications](/actions/using-github-hosted-runners/about-ae-hosted-runners#software-specifications)." - - Choose a name for each pool of {% data variables.actions.hosted_runner %}s. These names are created as labels, allowing you to route your workflows to these runners. For more information, see ["Using {% data variables.actions.hosted_runner %}s in a workflow](/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow)." + - Choose a name for each pool of {% data variables.actions.hosted_runner %}s. These names are created as labels, allowing you to route your workflows to these runners. For more information, see ["Using {% data variables.actions.hosted_runner %}s in a workflow](/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow)."{% ifversion ghae-next %} +{% data reusables.actions.autoscaling-parameters %}{% endif %} - Where to add the {% data variables.actions.hosted_runner %}: Identify the names of the organizations and enterprises that will receive the runners. ## Adding an {% data variables.actions.hosted_runner %} with a custom image @@ -33,7 +34,8 @@ Once you've created a custom image using the above steps, contact {% data variab - Image name. - バージョン. - VM SKU for the new pool. - - Choose a name for each pool of {% data variables.actions.hosted_runner %}s. These names are created as labels, allowing you to route your workflows to these runners. For more information, see ["Using {% data variables.actions.hosted_runner %}s in a workflow](/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow)." + - Choose a name for each pool of {% data variables.actions.hosted_runner %}s. These names are created as labels, allowing you to route your workflows to these runners. For more information, see ["Using {% data variables.actions.hosted_runner %}s in a workflow](/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow)."{% ifversion ghae-next %} +{% data reusables.actions.autoscaling-parameters %}{% endif %} - Where to add the {% data variables.actions.hosted_runner %}: Identify the names of the organizations and enterprises that will receive the runners. ## Reviewing your {% data variables.actions.hosted_runner %}s diff --git a/translations/ja-JP/content/actions/using-github-hosted-runners/creating-custom-images.md b/translations/ja-JP/content/actions/using-github-hosted-runners/creating-custom-images.md index c8369a8e24..5dfff3138d 100644 --- a/translations/ja-JP/content/actions/using-github-hosted-runners/creating-custom-images.md +++ b/translations/ja-JP/content/actions/using-github-hosted-runners/creating-custom-images.md @@ -5,7 +5,7 @@ versions: ghae: '*' --- -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} ## Creating an {% data variables.actions.hosted_runner %} with a custom image diff --git a/translations/ja-JP/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md b/translations/ja-JP/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md index db23278023..3fd637a69f 100644 --- a/translations/ja-JP/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md +++ b/translations/ja-JP/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md @@ -11,6 +11,7 @@ topics: shortTitle: Customize runners --- +{% data reusables.actions.ae-hosted-runners-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} If you require additional software packages on {% data variables.product.prodname_dotcom %}-hosted runners, you can create a job that installs the packages as part of your workflow. diff --git a/translations/ja-JP/content/actions/using-github-hosted-runners/index.md b/translations/ja-JP/content/actions/using-github-hosted-runners/index.md index 440c898ae1..16a4af837c 100644 --- a/translations/ja-JP/content/actions/using-github-hosted-runners/index.md +++ b/translations/ja-JP/content/actions/using-github-hosted-runners/index.md @@ -17,5 +17,6 @@ children: shortTitle: Use GitHub-hosted runners --- +{% data reusables.actions.ae-hosted-runners-beta %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} diff --git a/translations/ja-JP/content/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow.md b/translations/ja-JP/content/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow.md index 7ee6a6025f..239e49e8f1 100644 --- a/translations/ja-JP/content/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow.md +++ b/translations/ja-JP/content/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow.md @@ -6,7 +6,7 @@ versions: shortTitle: Use AE hosted runners --- -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} ## Using {% data variables.actions.hosted_runner %}s in a workflow diff --git a/translations/ja-JP/content/actions/using-github-hosted-runners/using-groups-to-manage-access-to-ae-hosted-runners.md b/translations/ja-JP/content/actions/using-github-hosted-runners/using-groups-to-manage-access-to-ae-hosted-runners.md index 8d3bc17cc0..1da8d8fc44 100644 --- a/translations/ja-JP/content/actions/using-github-hosted-runners/using-groups-to-manage-access-to-ae-hosted-runners.md +++ b/translations/ja-JP/content/actions/using-github-hosted-runners/using-groups-to-manage-access-to-ae-hosted-runners.md @@ -6,7 +6,7 @@ versions: shortTitle: Manage AE runner groups --- -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} ## About {% data variables.actions.hosted_runner %} groups diff --git a/translations/ja-JP/content/actions/using-github-hosted-runners/using-labels-with-ae-hosted-runners.md b/translations/ja-JP/content/actions/using-github-hosted-runners/using-labels-with-ae-hosted-runners.md index 6e8a972e0c..9063a7496f 100644 --- a/translations/ja-JP/content/actions/using-github-hosted-runners/using-labels-with-ae-hosted-runners.md +++ b/translations/ja-JP/content/actions/using-github-hosted-runners/using-labels-with-ae-hosted-runners.md @@ -6,7 +6,7 @@ versions: shortTitle: Label AE hosted runners --- -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} For information on how to use labels to route jobs to specific types of {% data variables.actions.hosted_runner %}s, see "[Using {% data variables.actions.hosted_runner %}s in a workflow](/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow)." diff --git a/translations/ja-JP/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md b/translations/ja-JP/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md index 2ad0098515..e18cf592ee 100644 --- a/translations/ja-JP/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md +++ b/translations/ja-JP/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md @@ -62,13 +62,13 @@ If you want to use actions to run {% data variables.product.prodname_code_scanni {% ifversion ghes = 2.22 %} {% data variables.product.prodname_actions %} を使用して {% data variables.product.prodname_ghe_server %} で {% data variables.product.prodname_code_scanning %} を実行するには、適切なアクションがローカルで使用可能である必要があります。 アクションは 3 つの方法で利用可能にすることができます。 -- **推奨**: [{% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud) を使用して、{% data variables.product.prodname_dotcom_the_website %} からアクションを自動的にダウンロードできます。 インスタンスをホストするマシンは、{% data variables.product.prodname_dotcom_the_website %} にアクセス可能である必要があります。 この方法で、最新のソフトウェアを自動的に入手できます。 詳しい情報については、「[{% data variables.product.prodname_actions %} を同期するために {% data variables.product.prodname_github_connect %} を設定する](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)」を参照してください。 +- **推奨**: [{% data variables.product.prodname_github_connect %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud) を使用して、{% data variables.product.prodname_dotcom_the_website %} からアクションを自動的にダウンロードできます。 インスタンスをホストするマシンは、{% data variables.product.prodname_dotcom_the_website %} にアクセス可能である必要があります。 この方法で、最新のソフトウェアを自動的に入手できます。 詳しい情報については、「[{% data variables.product.prodname_actions %} を同期するために {% data variables.product.prodname_github_connect %} を設定する](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)」を参照してください。 - {% data variables.product.prodname_codeql_workflow %} を使用する場合は、[https://github.com/github/codeql-action-sync-tool](https://github.com/github/codeql-action-sync-tool/) にある {% data variables.product.prodname_codeql %} Action 同期ツールを使用して、リポジトリを {% data variables.product.prodname_dotcom_the_website %} から {% data variables.product.prodname_ghe_server %} に同期できます。 コンピューターで {% data variables.product.product_location %} と {% data variables.product.prodname_dotcom_the_website %} の両方に同時にアクセスできる限り、{% data variables.product.product_location %} または {% data variables.product.prodname_actions %} ランナーがインターネットにアクセスできるかどうかに関係なく、このツールを使用できます。 - アクションを含む {% data variables.product.prodname_dotcom_the_website %} リポジトリのクローンを作成することにより、サーバー上にアクションのリポジトリのローカルコピーを作成できます。 たとえば、{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} のアクションを使用する場合は、インスタンスに `github/codeql-action` というリポジトリを作成し、{% data variables.product.prodname_dotcom_the_website %} から[リポジトリ](https://github.com/github/codeql-action)のクローンを作成して、そのリポジトリをインスタンスの `github/codeql-action` リポジトリにプッシュできます。 また、{% data variables.product.prodname_dotcom_the_website %} のリポジトリからリリースをダウンロードし、リリースとしてインスタンスの `github/codeql-action` リポジトリにアップロードする必要があります。 {% endif %} ### {% data variables.product.prodname_actions %} を同期するために {% data variables.product.prodname_github_connect %} を設定する -1. {% data variables.product.prodname_dotcom_the_website %} からオンデマンドでアクションワークフローをダウンロードする場合は、{% data variables.product.prodname_github_connect %} を有効にする必要があります。 詳しい情報については、「[{% data variables.product.prodname_github_connect %} を有効化する](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud#enabling-github-connect)」を参照してください。 +1. {% data variables.product.prodname_dotcom_the_website %} からオンデマンドでアクションワークフローをダウンロードする場合は、{% data variables.product.prodname_github_connect %} を有効にする必要があります。 詳しい情報については、「[{% data variables.product.prodname_github_connect %} を有効化する](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud#enabling-github-connect)」を参照してください。 2. また、{% data variables.product.product_location %} に対して {% data variables.product.prodname_actions %} を有効化する必要があります。 詳しい情報については、「[{% data variables.product.prodname_ghe_server %} の {% data variables.product.prodname_actions %} を使ってみる](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)」を参照してください。 3. 次のステップは、{% data variables.product.prodname_github_connect %} を使用して、{% data variables.product.prodname_dotcom_the_website %} に対するアクションへのアクセスを設定することです。 詳しい情報については、「[{% data variables.product.prodname_github_connect %} を使用した {% data variables.product.prodname_dotcom_the_website %} アクションへの自動アクセスを有効化する](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)」を参照してください。 4. セルフホストランナーをリポジトリ、Organization、または Enterprise アカウントに追加します。 詳しい情報については「[セルフホストランナーの追加](/actions/hosting-your-own-runners/adding-self-hosted-runners)」を参照してください。 diff --git a/translations/ja-JP/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md b/translations/ja-JP/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md index 9af453f382..fd094fcc81 100644 --- a/translations/ja-JP/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md @@ -83,10 +83,14 @@ For example, you can enable any {% data variables.product.prodname_GH_advanced_s ```shell ghe-config app.secret-scanning.enabled true ``` - - To enable {% data variables.product.prodname_dependabot %}, enter the following command. - ```shell - {% ifversion ghes > 3.1 %}ghe-config app.dependency-graph.enabled true{% else %}ghe-config app.github.dependency-graph-enabled true{% endif %} + - To enable {% data variables.product.prodname_dependabot %}, enter the following {% ifversion ghes > 3.1 %}command{% else %}commands{% endif %}. + {% ifversion ghes > 3.1 %}```shell + ghe-config app.dependency-graph.enabled true ``` + {% else %}```shell + ghe-config app.github.dependency-graph-enabled true + ghe-config app.github.vulnerability-alerting-and-settings-enabled true + ```{% endif %} 2. Optionally, disable features for {% data variables.product.prodname_GH_advanced_security %}. - To disable {% data variables.product.prodname_code_scanning %}, enter the following commands. @@ -98,11 +102,14 @@ For example, you can enable any {% data variables.product.prodname_GH_advanced_s ```shell ghe-config app.secret-scanning.enabled false ``` - - To disable {% data variables.product.prodname_dependabot %}, enter the following command. - ```shell - {% ifversion ghes > 3.1 %}ghe-config app.dependency-graph.enabled false{% else %}ghe-config app.github.dependency-graph-enabled false{% endif %} + - To disable {% data variables.product.prodname_dependabot %}, enter the following {% ifversion ghes > 3.1 %}command{% else %}commands{% endif %}. + {% ifversion ghes > 3.1 %}```shell + ghe-config app.dependency-graph.enabled false ``` - + {% else %}```shell + ghe-config app.github.dependency-graph-enabled false + ghe-config app.github.vulnerability-alerting-and-settings-enabled false + ```{% endif %} 3. 設定を適用します。 ```shell ghe-config-apply diff --git a/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md b/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md index 24e24ee169..de124e0d39 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md +++ b/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md @@ -23,7 +23,7 @@ shortTitle: Configure an outbound proxy {% note %} -**メモ:** {% data variables.product.product_location %}　を　{% data variables.product.prodname_dotcom_the_website %} に接続するには、`github.com` と `api.github.com` への接続がプロキシ設定で許可されている必要があります。 詳細は「[{% data variables.product.prodname_ghe_server %} を {% data variables.product.prodname_dotcom_the_website %} に接続する](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/connecting-github-enterprise-server-to-github-com)」を参照してください。 +**メモ:** {% data variables.product.product_location %}　を　{% data variables.product.prodname_dotcom_the_website %} に接続するには、`github.com` と `api.github.com` への接続がプロキシ設定で許可されている必要があります。 For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_dotcom_the_website %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." {% endnote %} @@ -34,7 +34,7 @@ shortTitle: Configure an outbound proxy {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.privacy %} -4. **HTTP Proxy Server（HTTPプロキシサーバ）**の下に、プロキシサーバのURLを入力してください。 ![HTTP プロキシサーバーのURLを入力するためのフィールド](/assets/images/enterprise/management-console/http-proxy-field.png) +1. **HTTP Proxy Server（HTTPプロキシサーバ）**の下に、プロキシサーバのURLを入力してください。 ![HTTP プロキシサーバーのURLを入力するためのフィールド](/assets/images/enterprise/management-console/http-proxy-field.png) 5. オプションで、プロキシのアクセスを要しないホストがあれば**HTTP Proxy Exclusion（HTTPプロキシの除外）**の下にカンマ区切りで入力してください。 ドメイン内のすべてのホストをプロキシアクセスの要求から除外するには `.` をワイルドカードプレフィックスとして使用できます。 たとえば、`.octo-org.tentacle` などです。 ![HTTP プロキシの除外を入力するためのフィールド](/assets/images/enterprise/management-console/http-proxy-exclusion-field.png) 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 9062ce4f56..3446f6e97e 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 @@ -351,18 +351,6 @@ stop/waiting - ghe-replica-mode ``` -{% tip %} - -このコマンドが返すサービス名は、[`systemctl`](https://www.freedesktop.org/software/systemd/man/systemctl.html)コマンドで利用して、それらのサービスを必要に応じて手動で停止、起動、再起動できます。 例: - -```shell -$ sudo systemctl restart github-resqued -``` - -サービスを停止することによって、インスタレーションが稼働停止しますので、サービスを停止または再起動する前に {% data variables.contact.contact_ent_support %} に連絡することをおすすめします。 - -{% endtip %} - ### ghe-set-password `ghe-set-password` では、[{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-management-console) に認証するための新しいパスワードを設定することができます。 @@ -807,7 +795,7 @@ $ ssh -p 122 admin@hostname -- 'ghe-update-check' ### ghe-license-usage -このユーティリティは、インストールのユーザーのリストを JSON 形式でエクスポートします。 インスタンスが {% data variables.product.prodname_ghe_cloud %} に接続されている場合、{% data variables.product.prodname_ghe_server %} はこの情報を使用してライセンス情報を {% data variables.product.prodname_ghe_cloud %} に報告します。 詳しい情報については、「[{% data variables.product.prodname_ghe_server %} を {% data variables.product.prodname_ghe_cloud %} に接続する](/enterprise/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)」を参照してください。 +このユーティリティは、インストールのユーザーのリストを JSON 形式でエクスポートします。 インスタンスが {% data variables.product.prodname_ghe_cloud %} に接続されている場合、{% data variables.product.prodname_ghe_server %} はこの情報を使用してライセンス情報を {% data variables.product.prodname_ghe_cloud %} に報告します。 For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %} ](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." デフォルトでは、結果の JSON ファイル内のユーザのリストは暗号化されます。 その他のオプションを利用するには、`-h` のフラグを使ってください。 diff --git a/translations/ja-JP/content/admin/configuration/index.md b/translations/ja-JP/content/admin/configuration/index.md index 86aae5476c..17a12ad2df 100644 --- a/translations/ja-JP/content/admin/configuration/index.md +++ b/translations/ja-JP/content/admin/configuration/index.md @@ -12,7 +12,7 @@ topics: children: - /configuring-your-enterprise - /configuring-network-settings - - /managing-connections-between-github-enterprise-server-and-github-enterprise-cloud + - /managing-connections-between-your-enterprise-accounts --- {% ifversion ghes %} diff --git a/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md b/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md new file mode 100644 index 0000000000..3eaa01cd20 --- /dev/null +++ b/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md @@ -0,0 +1,83 @@ +--- +title: Connecting your enterprise account to GitHub Enterprise Cloud +shortTitle: Connect enterprise accounts +intro: '{% data variables.product.prodname_github_connect %}を有効化すると、特定の機能やワークフローを{% data variables.product.product_location %}と{% data variables.product.prodname_ghe_cloud %}のOrganizationの間で共有できます。' +redirect_from: + - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-to-github-com/ + - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-server-to-github-com + - /enterprise/admin/developer-workflow/connecting-github-enterprise-server-to-githubcom/ + - /enterprise/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud + - /enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud + - /admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud +permissions: 'Enterprise owners who are also owners of a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable {% data variables.product.prodname_github_connect %}.' +versions: + ghes: '*' + ghae: next +type: how_to +topics: + - Enterprise + - GitHub Connect + - Infrastructure + - Networking +--- + +{% data reusables.github-connect.beta %} + +## {% data variables.product.prodname_github_connect %} について + +{% data variables.product.prodname_github_connect %}を有効化するには、{% data variables.product.product_location %}と{% data variables.product.prodname_ghe_cloud %} のOrganizationまたはEnterpriseアカウントの両方で接続を設定しなければなりません。 + +{% ifversion ghes %} +接続を設定するには、プロキシの設定で`github.com` および `api.github.com` への接続が許可されていなければなりません。 詳細は「[アウトバウンド Web プロキシサーバーを設定する](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-an-outbound-web-proxy-server)」を参照してください。 +{% endif %} + +{% data variables.product.prodname_github_connect %}を有効化すると、Unified Searchや統合コントリビューションといった機能を使用できるようになります。 For more information about all of the features available, see "[Managing connections between your enterprise accounts](/admin/configuration/managing-connections-between-your-enterprise-accounts)." + +{% data variables.product.product_location %}を{% data variables.product.prodname_ghe_cloud %}に接続すると、{% data variables.product.prodname_dotcom_the_website %}上のレコードに、接続に関する情報が保存されます: +{% ifversion ghes %} +- {% data variables.product.prodname_ghe_server %} ライセンスの公開鍵の部分 +- {% data variables.product.prodname_ghe_server %} ライセンスのハッシュ +- {% data variables.product.prodname_ghe_server %} ライセンスの顧客名 +- The version of {% data variables.product.product_location_enterprise %}{% endif %} +- The hostname of your {% data variables.product.product_name %} instance +- {% data variables.product.product_location %}に接続している{% data variables.product.prodname_dotcom_the_website %}上のOrganizationまたはEnterpriseアカウント +- {% data variables.product.prodname_dotcom_the_website %} へのリクエストの発行に {% data variables.product.product_location %} が使用する認証トークン + +{% data variables.product.prodname_github_connect %}を有効化すると、{% data variables.product.prodname_ghe_cloud %}のOrganizationまたはEnterpriseアカウントが所有している{% data variables.product.prodname_github_app %}も作成されます。 {% data variables.product.product_name %} は {% data variables.product.prodname_github_app %} のクレデンシャルを使って {% data variables.product.prodname_dotcom_the_website %} へのリクエストを発行します。 +{% ifversion ghes %} +{% data variables.product.prodname_ghe_server %} は {% data variables.product.prodname_github_app %} からのクレデンシャルを保存します。 以下のクレデンシャルは、High Availability あるいはクラスタリング環境ではレプリケーションされ、{% data variables.product.prodname_enterprise_backup_utilities %} が作成するスナップショットを含むあらゆるバックアップに保存されます。 +- 1 時間にわたって有効な認証トークン +- 新しい認証トークンを生成するのに使われる秘密鍵 +{% endif %} + +{% data variables.product.prodname_github_connect %} を有効化しても、{% data variables.product.prodname_dotcom_the_website %} のユーザは {% data variables.product.product_name %} を変更できるようになりません。 + +GraphQL APIを利用したEnterpriseアカウントの管理に関する詳しい情報については、「[Enterprise アカウント](/graphql/guides/managing-enterprise-accounts)」を参照してください。 +## {% data variables.product.prodname_github_connect %} の有効化 + +{% ifversion ghes %} +1. {% data variables.product.product_location %}と{% data variables.product.prodname_dotcom_the_website %}にサインインしてください。 +{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %}{% else %} +1. {% data variables.product.product_location %}と{% data variables.product.prodname_dotcom_the_website %}にサインインしてください。 +{% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %} +1. 「{% data variables.product.prodname_github_connect %} is not enabled yet」の下で、「**Enable{% data variables.product.prodname_github_connect %}**」をクリックします。 By clicking **Enable {% data variables.product.prodname_github_connect %}**, you agree to the "{% data variables.product.prodname_dotcom %} Terms for Additional Products and Features." +{% ifversion ghes %} +![Enable GitHub Connect button](/assets/images/enterprise/business-accounts/enable-github-connect-button.png){% else %} +![Enable GitHub Connect button](/assets/images/enterprise/github-ae/enable-github-connect-button.png) +{% endif %} +1. 接続したいEnterpriseアカウントまたはOrganizationの横にある「**Connect**」をクリックします。 ![Enterprise アカウントまたはビジネスアカウントの横にある [Connect] ボタン](/assets/images/enterprise/business-accounts/choose-enterprise-or-org-connect.png) + +## Disconnecting a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account from your enterprise account + +{% data variables.product.prodname_ghe_cloud %}から切断すると、EnterpriseアカウントまたはOrganizationから{% data variables.product.prodname_github_connect %}{% data variables.product.prodname_github_app %}が削除され、{% data variables.product.product_location %}に保存されているクレデンシャルが削除されます。 + +{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %} +1. 切断しようとするEnterpriseアカウントまたはOrganizationの横にある「**Disable {% data variables.product.prodname_github_connect %}**」をクリックします。 +{% ifversion ghes %} + ![EnterpriseアカウントまたはOrganization名の横にある「Disable GitHub Connect」ボタン](/assets/images/enterprise/business-accounts/disable-github-connect-button.png) +1. 切断に関する情報を読み、「 **Disable {% data variables.product.prodname_github_connect %}**」をクリックします。 ![切断に関する警告情報が表示され確定ボタンがあるモーダル](/assets/images/enterprise/business-accounts/confirm-disable-github-connect.png) +{% else %} + ![EnterpriseアカウントまたはOrganization名の横にある「Disable GitHub Connect」ボタン](/assets/images/enterprise/github-ae/disable-github-connect-button.png) +1. 切断に関する情報を読み、「 **Disable {% data variables.product.prodname_github_connect %}**」をクリックします。 ![切断に関する警告情報が表示され確定ボタンがあるモーダル](/assets/images/enterprise/github-ae/confirm-disable-github-connect.png) +{% endif %} diff --git a/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md b/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md new file mode 100644 index 0000000000..3a8c8df3fa --- /dev/null +++ b/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md @@ -0,0 +1,97 @@ +--- +title: GitHub Enterprise Serverで脆弱性のある依存関係に対するアラートを有効化する +intro: 'You can connect {% data variables.product.product_location %} to {% data variables.product.prodname_ghe_cloud %} and enable the dependency graph and {% ifversion ghes %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts in repositories in your instance.' +shortTitle: Enable alerts for dependencies +miniTocMaxHeadingLevel: 3 +redirect_from: + - /enterprise/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /enterprise/admin/configuration/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /enterprise/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server +permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable the dependency graph and {% data variables.product.prodname_dependabot %} alerts on {% data variables.product.prodname_ghe_server %}.' +versions: + ghes: '*' +type: how_to +topics: + - Enterprise + - Security + - Dependency graph + - Dependabot +--- + +## {% data variables.product.prodname_ghe_server %} 上の脆弱性のある依存関係に対するアラートについて + +To identify vulnerable dependencies in your repository and receive alerts about vulnerabilities, you need to enable two security features: +- The dependency graph +- {% data variables.product.prodname_dependabot %} アラート + +For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" and "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." + +{% data reusables.repositories.tracks-vulnerabilities %} + +You can connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}, then sync vulnerability data to your instance and generate {% data variables.product.prodname_dependabot_alerts %} in repositories with a vulnerable dependency. + +After connecting {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %} and enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies, vulnerability data is synced from {% data variables.product.prodname_dotcom_the_website %} to your instance once every hour. また、脆弱性データはいつでも手動で同期することができます。 {% data variables.product.product_location %} からのコードまたはコードに関する情報は、{% data variables.product.prodname_dotcom_the_website %} にアップロードされません。 + +When {% data variables.product.product_location %} receives information about a vulnerability, it will identify repositories in your instance that use the affected version of the dependency and generate {% data variables.product.prodname_dependabot_alerts %}. {% data variables.product.prodname_dependabot_alerts %} を受け取る方法をカスタマイズできます。 詳しい情報については、「[脆弱性のある依存関係に対する通知を設定する](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies/#configuring-notifications-for-dependabot-alerts)」を参照してください。 + +Before enabling the dependency graph and {% ifversion ghes > 2.21 %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts for vulnerable dependencies on {% data variables.product.product_location %}, you must connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." + +## Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} on GitHub Enterprise Server + +For {% data variables.product.product_location %} to generate {% data variables.product.prodname_dependabot_alerts %} whenever vulnerabilities are detected on your repositories: +- You must connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}. 詳細は、「[{% data variables.product.prodname_ghe_server %}を{% data variables.product.prodname_ghe_cloud %}に接続する](/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)」を参照してください。 +- You must enable the dependency graph. + +{% ifversion ghes > 3.1 %} +You can enable the dependency graph via the {% data variables.enterprise.management_console %} or the administrative shell. We recommend you follow the {% data variables.enterprise.management_console %} route unless {% data variables.product.product_location %} uses clustering. + +### Enabling the dependency graph via the {% data variables.enterprise.management_console %} +{% endif %}{% ifversion ghes > 3.1 %} +{% data reusables.enterprise_site_admin_settings.sign-in %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.advanced-security-tab %} +1. Under "Security," click **Dependency graph**. ![Checkbox to enable or disable the dependency graph](/assets/images/enterprise/3.2/management-console/enable-dependency-graph-checkbox.png) +{% data reusables.enterprise_management_console.save-settings %} +1. **Visit your instance（インスタンスへのアクセス）**をクリックしてください。 + +### Enabling the dependency graph via the administrative shell +{% else %} +### 依存関係グラフの有効化 +{% endif %} +{% data reusables.enterprise_site_admin_settings.sign-in %} +1. In the administrative shell, enable the dependency graph on {% data variables.product.product_location %}: + ``` shell + $ {% ifversion ghes > 3.1 %}ghe-config app.dependency-graph.enabled true{% else %}ghe-config app.github.dependency-graph-enabled true{% endif %} + ``` + {% note %} + + **注釈**: SSH 経由で管理シェルへのアクセスを有効化する方法について詳しくは、「[管理シェル (SSH) にアクセスする](/enterprise/{{ currentVersion }}/admin/configuration/accessing-the-administrative-shell-ssh)」を参照してください。 + + {% endnote %} +1. 設定を適用します。 + ```shell + $ ghe-config-apply + ``` +1. {% data variables.product.prodname_ghe_server %}に戻ります。 + +### {% data variables.product.prodname_dependabot_alerts %} の有効化 + +Before enabling {% data variables.product.prodname_dependabot_alerts %} for your instance, you need to enable the dependency graph. For more information, see above. + +{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %} +1. [Repositories can be scanned for vulnerabilities] で、ドロップダウンメニューを使用して、[**Enabled without notifications**] を選択します。 必要に応じて、通知を含むアラートを有効化にするには、[**Enabled with notifications**] を選択します。 ![脆弱性に対するリポジトリのスキャンを有効化するドロップダウンメニュー](/assets/images/enterprise/site-admin-settings/enable-vulnerability-scanning-in-repositories.png) + {% note %} + + We recommend configuring {% data variables.product.prodname_dependabot_alerts %} without notifications for the first few days to avoid an overload of emails. 数日後、通知を有効化すれば、通常どおり {% data variables.product.prodname_dependabot_alerts %} を受信できます。 + + {% endnote %} +## {% data variables.product.prodname_ghe_server %}で脆弱性のある依存関係を表示する + +{% data variables.product.product_location %}ですべての脆弱性を表示し、{% data variables.product.prodname_dotcom_the_website %}から脆弱性データを手動で同期して、リストを更新することができます。 + +{% data reusables.enterprise_site_admin_settings.access-settings %} +2. 左サイドバーで [**Vulnerabilities**] をクリックします。 ![サイト管理サイドバーの [Vulnerabilities] タブ](/assets/images/enterprise/business-accounts/vulnerabilities-tab.png) +3. 脆弱性データを同期するには、[**Sync Vulnerabilities now**] をクリックします。 ![[Sync vulnerabilities now] ボタン](/assets/images/enterprise/site-admin-settings/sync-vulnerabilities-button.png) diff --git a/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md b/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md new file mode 100644 index 0000000000..893bf6f014 --- /dev/null +++ b/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md @@ -0,0 +1,31 @@ +--- +title: GitHub Enterprise ServerとGitHub Enterprise Cloudの間で自動ユーザライセンス同期を有効化する +intro: '{% data variables.product.product_location_enterprise %}を{% data variables.product.prodname_ghe_cloud %}に接続すると、{% data variables.product.prodname_ghe_server %}でユーザライセンス情報を{% data variables.product.prodname_dotcom_the_website %}上のEnterpriseアカウントにアップロードすることができます。' +redirect_from: + - /enterprise/admin/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud + - /enterprise/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud + - /admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud +permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable automatic user license synchronization.' +versions: + ghes: '*' +type: how_to +topics: + - Enterprise + - GitHub Connect + - Licensing +shortTitle: Enable user license sync +--- + +## ライセンスの同期について + +ライセンスの同期を有効にすると、{% data variables.product.prodname_ghe_server %} および {% data variables.product.prodname_ghe_cloud %} 全体で、Enterprise アカウント全体のライセンス使用状況を表示できるようになります。 {% data variables.product.prodname_github_connect %} は、{% data variables.product.prodname_ghe_server %} と {% data variables.product.prodname_ghe_cloud %} 間で毎週ライセンスを同期します。 For more information, see "[Managing your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise)." + +{% data variables.product.prodname_ghe_server %}ユーザライセンス情報を手動で{% data variables.product.prodname_ghe_cloud %}にアップロードすることもできます。 For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." + +## ライセンス同期の有効化 + +{% data variables.product.product_location_enterprise %}でライセンス同期を有効化する前に、{% data variables.product.product_location_enterprise %}を{% data variables.product.prodname_dotcom_the_website %}に接続する必要があります。 For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." + +{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %} +1. [Server can sync user license count and usage] で、ドロップダウンメニューを使って [**Enabled**] を選択します。 ![自動ユーザライセンス同期を有効化するドロップダウンメニュー](/assets/images/enterprise/site-admin-settings/enable-user-license-drop-down.png) diff --git a/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md b/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md new file mode 100644 index 0000000000..bf403cdee5 --- /dev/null +++ b/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md @@ -0,0 +1,46 @@ +--- +title: Enabling unified contributions between your enterprise account and GitHub.com +shortTitle: Enable unified contributions +intro: '{% data variables.product.prodname_github_connect %}を有効化すると、{% data variables.product.prodname_ghe_cloud %}のメンバーがコントリビューション数を{% data variables.product.prodname_dotcom_the_website %}のプロフィールに送信して、{% data variables.product.product_name %}上の作業をハイライトできるようにできます。' +redirect_from: + - /enterprise/admin/guides/developer-workflow/enabling-unified-contributions-between-github-enterprise-and-github-com/ + - /enterprise/admin/guides/developer-workflow/enabling-unified-contributions-between-github-enterprise-server-and-github-com/ + - /enterprise/admin/developer-workflow/enabling-unified-contributions-between-github-enterprise-server-and-githubcom/ + - /enterprise/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom + - /enterprise/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom + - /admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-unified-contributions-between-github-enterprise-server-and-githubcom +permissions: 'Enterprise owners who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable unified contributions between {% data variables.product.product_location %} and {% data variables.product.prodname_dotcom_the_website %}.' +versions: + ghes: '*' + ghae: next +type: how_to +topics: + - Enterprise + - GitHub Connect +--- + +{% data reusables.github-connect.beta %} + +As an enterprise owner, you can allow end users to send anonymized contribution counts for their work from {% data variables.product.product_location %} to their {% data variables.product.prodname_dotcom_the_website %} contribution graph. + +After you enable {% data variables.product.prodname_github_connect %} and enable {% data variables.product.prodname_unified_contributions %} in both environments, end users on your enterprise account can connect to their {% data variables.product.prodname_dotcom_the_website %} accounts and send contribution counts from {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.github-connect.sync-frequency %} 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)." + +If the enterprise owner disables the functionality or developers opt out of the connection, the {% data variables.product.product_name %} contribution counts will be deleted on {% data variables.product.prodname_dotcom_the_website %}. 開発者がプロフィールを無効にした後に再接続すると、過去 90 日間のコントリビューションカウントが復元されます。 + +{% data variables.product.product_name %} は、接続されているユーザーのコントリビューションカウントおよびソース ({% data variables.product.product_name %}) **のみ**を送信します。 コントリビューションまたはその作成方法に関する情報は送信されません。 + +{% data variables.product.product_location %}で {% data variables.product.prodname_unified_contributions %}を有効化する前に、{% data variables.product.product_location %}を {% data variables.product.prodname_dotcom_the_website %}に接続する必要があります。 For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_dotcom_the_website %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." + +{% ifversion ghes %} +{% data reusables.github-connect.access-dotcom-and-enterprise %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.business %} +{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %}{% else %} +1. {% data variables.product.product_location %}と{% data variables.product.prodname_dotcom_the_website %}にサインインしてください。 +{% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %} +1. \[Users can share contribution counts to {% data variables.product.prodname_dotcom_the_website %}\] (ユーザは {% data variables.product.prodname_dotcom_the_website %} にコントリビューション数を共有できる) の下で、[**Request access**] (アクセスをリクエスト) をクリックします。 ![Request access to unified contributions option](/assets/images/enterprise/site-admin-settings/dotcom-ghe-connection-request-access.png){% ifversion ghes %} +2. {% data variables.product.prodname_ghe_server %} サイトに[サインイン](https://enterprise.github.com/login)して、以降の指示を受けてください。 + +When you request access, we may redirect you to the {% data variables.product.prodname_ghe_server %} site to check your current terms of service. +{% endif %} diff --git a/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md b/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md new file mode 100644 index 0000000000..ee1a89f9b6 --- /dev/null +++ b/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md @@ -0,0 +1,44 @@ +--- +title: Enabling unified search between your enterprise account and GitHub.com +shortTitle: Enable unified search +intro: 'After enabling {% data variables.product.prodname_github_connect %}, you can allow search of {% data variables.product.prodname_dotcom_the_website %} for members of your enterprise on {% data variables.product.product_name %}.' +redirect_from: + - /enterprise/admin/guides/developer-workflow/enabling-unified-search-between-github-enterprise-and-github-com/ + - /enterprise/admin/guides/developer-workflow/enabling-unified-search-between-github-enterprise-server-and-github-com/ + - /enterprise/admin/developer-workflow/enabling-unified-search-between-github-enterprise-server-and-githubcom/ + - /enterprise/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom + - /enterprise/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom + - /admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-unified-search-between-github-enterprise-server-and-githubcom +permissions: 'Enterprise owners who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable unified search between {% data variables.product.product_name %} and {% data variables.product.prodname_dotcom_the_website %}.' +versions: + ghes: '*' + ghae: next +topics: + - Enterprise + - GitHub Connect + - GitHub search +--- + +{% data reusables.github-connect.beta %} + +When you enable unified search, users can view search results from public and private content on {% data variables.product.prodname_dotcom_the_website %} when searching from {% data variables.product.product_location %}{% ifversion ghae %} on {% data variables.product.prodname_ghe_managed %}{% endif %}. + +両方の環境にアクセスできる場合でも、ユーザは{% data variables.product.prodname_dotcom_the_website %}から{% data variables.product.product_location %}を検索することはできません。 ユーザが検索できるのは、あなたが{% data variables.product.prodname_unified_search %}を有効化したプライベートリポジトリと、接続された{% data variables.product.prodname_ghe_cloud %} Organizationでユーザがアクセスできるプライベートリポジトリだけです。 For more information, see "[About searching on {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github/#searching-across-github-enterprise-and-githubcom-simultaneously)" and "[Enabling private {% data variables.product.prodname_dotcom_the_website %} repository search in your enterprise account](/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment)." + +REST及びGraphQL APIでの検索には、{% data variables.product.prodname_dotcom_the_website %}の検索結果は含まれません。 {% data variables.product.prodname_dotcom_the_website %}の高度な検索及びwikiの検索はサポートされていません。 + +{% ifversion ghes %} +{% data reusables.github-connect.access-dotcom-and-enterprise %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.business %} +{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %}{% else %} +1. {% data variables.product.product_location %}と{% data variables.product.prodname_dotcom_the_website %}にサインインしてください。 +{% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %} +1. \[Users can search {% data variables.product.prodname_dotcom_the_website %}\] (ユーザは {% data variables.product.prodname_dotcom_the_website %} を検索可能) の下で、ドロップダウンメニューを使って [**Enabled**] をクリックします。 ![Enable search option in the [search GitHub.com] ドロップダウンメニューの [Enable search] オプション](/assets/images/enterprise/site-admin-settings/github-dotcom-enable-search.png) +1. \[Users can search private repositories on {% data variables.product.prodname_dotcom_the_website %}\] (ユーザは {% data variables.product.prodname_dotcom_the_website %} のプライベートリポジトリを検索可能) の下でドロップダウンメニューを使い、[**Enabled**] (有効) をクリックすることもできます。 ![[search GitHub.com] ドロップダウンメニューの [Enable private repositories search] オプション](/assets/images/enterprise/site-admin-settings/enable-private-search.png) + +## 参考リンク + +- "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)" + diff --git a/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md b/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md new file mode 100644 index 0000000000..9f36c9e4d4 --- /dev/null +++ b/translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md @@ -0,0 +1,25 @@ +--- +title: Managing connections between your enterprise accounts +intro: '{% data variables.product.prodname_github_connect %}を使えば、{% data variables.product.prodname_dotcom_the_website %}で、{% data variables.product.product_location %}と{% data variables.product.prodname_ghe_cloud %}のOrganizationまたはEnterpriseアカウントの特定の機能やデータを共有できます。' +redirect_from: + - /enterprise/admin/developer-workflow/connecting-github-enterprise-to-github-com + - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-and-github-com/ + - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-server-and-github-com/ + - /enterprise/admin/developer-workflow/connecting-github-enterprise-server-and-githubcom/ + - /enterprise/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud + - /enterprise/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud +versions: + ghes: '*' + ghae: next +topics: + - Enterprise +children: + - /connecting-your-enterprise-account-to-github-enterprise-cloud + - /enabling-unified-search-between-your-enterprise-account-and-githubcom + - /enabling-unified-contributions-between-your-enterprise-account-and-githubcom + - /enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud +shortTitle: Connect enterprise accounts +--- + diff --git a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md index a29ab4eed4..d2d455a633 100644 --- a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md +++ b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md @@ -37,19 +37,46 @@ topics: {% endif %} +{%- ifversion ghes < 3.2 %} + {% data variables.product.product_location %} で使用可能な CPU およびメモリリソースによって、{% data variables.product.prodname_actions %} の最大ジョブスループットが決まります。 {% data variables.product.company_short %} での内部テストでは、さまざまな CPU およびメモリ設定の {% data variables.product.prodname_ghe_server %} インスタンスで次の最大スループットが実証されました。 インスタンスのアクティビティの全体的なレベルに応じて、スループットが異なる場合があります。 -| vCPUs | メモリ | 最大ジョブスループット数 | -|:----- |:--- |:------------ | -| | | | -{%- ifversion ghes > 3.1 %} -| 4 | 32 GB | Demo or light testing | | 8 | 64 GB | 30 jobs | | 16 | 128 GB | 60 jobs | | 32 | 256 GB | 120 jobs | | 64 | 512 GB | 160 jobs | -{%- else ifversion ghes < 3.2 %} -| 4 | 32 GB | Demo or light testing | | 8 | 64 GB | 25 jobs | | 16 | 160 GB | 35 jobs | | 32 | 256 GB | 100 jobs | {%- endif %} +{%- ifversion ghes > 3.1 %} + +The CPU and memory resources available to {% data variables.product.product_location %} determine the number of jobs that can be run concurrently without performance loss. + +The peak quantity of concurrent jobs running without performance loss depends on such factors as job duration, artifact usage, number of repositories running Actions, and how much other work your instance is doing not related to Actions. Internal testing at GitHub demonstrated the following performance targets for GitHub Enterprise Server on a range of CPU and memory configurations: + +{% endif %} + +{%- ifversion ghes < 3.2 %} + +| vCPUs | メモリ | 最大ジョブスループット数 | +|:----- |:------ |:------------ | +| 4 | 32 GB | デモまたは軽いテスト | +| 8 | 64 GB | 25ジョブ | +| 16 | 160 GB | 35ジョブ | +| 32 | 256 GB | 100ジョブ | + +{%- endif %} + +{%- ifversion ghes > 3.1 %} + +| vCPUs | メモリ | Maximum Concurrency* | +|:----- |:------ |:-------------------- | +| 32 | 128 GB | 1500ジョブ | +| 64 | 256 GB | 1900ジョブ | +| 96 | 384 GB | 2200ジョブ | + +*Maximum concurrency was measured using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. You may experience different performance depending on the overall levels of activity on your instance. + +{%- endif %} + + 既存のインスタンスのユーザに対して {% data variables.product.prodname_actions %} の{% ifversion ghes = 2.22 %}ベータを有効化した{% else %}有効化する{% endif %}場合は、ユーザのアクティビティのレベルとインスタンスの自動化を確認し、ユーザーに適切な CPU とメモリをプロビジョニングしたことを確認してください。 {% data variables.product.prodname_ghe_server %}のキャパシティとパフォーマンスのモニタリングに関する詳しい情報については「[アプラインアンスのモニタリング](/admin/enterprise-management/monitoring-your-appliance)」を参照してください。 {% data variables.product.product_location %} の最小ハードウェア要件の詳細については、インスタンスのプラットフォームのハードウェアに関する考慮事項を参照してください。 diff --git a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md index 29e1b8d8fe..4a69cffa96 100644 --- a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md +++ b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md @@ -10,7 +10,6 @@ children: - /enabling-github-actions-with-azure-blob-storage - /enabling-github-actions-with-amazon-s3-storage - /enabling-github-actions-with-minio-gateway-for-nas-storage - - /enforcing-github-actions-policies-for-your-enterprise shortTitle: Enable GitHub Actions --- diff --git a/translations/ja-JP/content/admin/github-actions/index.md b/translations/ja-JP/content/admin/github-actions/index.md index 31d9324591..0aa0819836 100644 --- a/translations/ja-JP/content/admin/github-actions/index.md +++ b/translations/ja-JP/content/admin/github-actions/index.md @@ -16,6 +16,5 @@ children: shortTitle: Manage GitHub Actions --- -{% data reusables.actions.ae-beta %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} diff --git a/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md b/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md index 234845fbc9..a1f95203ce 100644 --- a/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md +++ b/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md @@ -18,7 +18,6 @@ shortTitle: Add actions in your enterprise {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data variables.product.prodname_actions %} ワークフローは_アクション_を使用できます。アクションは、ジョブを作成してワークフローをカスタマイズするために組み合わせることができる個々のタスクです。 独自のアクションの作成、または {% data variables.product.prodname_dotcom %} コミュニティによって共有されるアクションの使用やカスタマイズができます。 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 e9d24b2865..0a9959efed 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 @@ -19,7 +19,6 @@ shortTitle: Use GitHub Connect for actions {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.actions.enterprise-github-connect-warning %} -{% data reusables.actions.ae-beta %} デフォルトでは、{% data variables.product.product_name %} の {% data variables.product.prodname_actions %} ワークフローは {% data variables.product.prodname_dotcom_the_website %} または [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions) から直接アクションを使用できません。 @@ -27,8 +26,16 @@ shortTitle: Use GitHub Connect for actions ## すべての {% data variables.product.prodname_dotcom_the_website %} アクションへの自動アクセスを有効化する -Enterprise インスタンスで {% data variables.product.prodname_dotcom_the_website %} からのすべてのアクションへのアクセスを有効にする前に、Enterprise を {% data variables.product.prodname_dotcom_the_website %} に接続する必要があります。 詳細は、「[{% data variables.product.prodname_ghe_server %}を{% data variables.product.prodname_ghe_cloud %}に接続する](/enterprise/{{ currentVersion }}/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)」を参照してください。 +Enterprise インスタンスで {% data variables.product.prodname_dotcom_the_website %} からのすべてのアクションへのアクセスを有効にする前に、Enterprise を {% data variables.product.prodname_dotcom_the_website %} に接続する必要があります。 For more information, see "[Connecting your enterprise to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." -{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %} +{% data reusables.enterprise-accounts.access-enterprise %} +{%- ifversion ghes < 3.1 %} +{% data reusables.enterprise-accounts.settings-tab %} +{%- endif %} +{% data reusables.enterprise-accounts.github-connect-tab %} +{%- ifversion ghes > 3.0 or ghae %} +1. Under "Users can utilize actions from GitHub.com in workflow runs", use the drop-down menu and select **Enabled**. ![ワークフロー実行内の GitHub.com からアクションへのドロップダウンメニュー](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down-ae.png) +{%- else %} 1. [Server can use actions from GitHub.com in workflows runs] で、ドロップダウンメニューを使用して [**Enabled**] を選択します。 ![ワークフロー実行内の GitHub.com からアクションへのドロップダウンメニュー](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down.png) +{%- endif %} 1. {% data reusables.actions.enterprise-limit-actions-use %} 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 ca61dfb159..a454f1dfff 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 @@ -14,13 +14,14 @@ shortTitle: Manually sync actions {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.actions.enterprise-no-internet-actions %} +{% ifversion ghes or ghae-next %} + {% data variables.product.prodname_dotcom_the_website %} からのアクションへのアクセスを有効化する際に推奨されるアプローチは、すべてのアクションへの自動アクセスを有効化することです。 これを行うには、{% data variables.product.prodname_github_connect %} を使用して {% data variables.product.product_name %} を {% data variables.product.prodname_ghe_cloud %} と統合します。 詳しい情報については、「[{% data variables.product.prodname_github_connect %} を使用した {% data variables.product.prodname_dotcom_the_website %} アクションへの自動アクセスを有効化する](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)」を参照してください。 -ただし、Enterprise で許可されるアクションをより厳密に制御する場合は、このガイドに従って、{% data variables.product.company_short %} のオープンソース [`actions-sync`](https://github.com/actions/actions-sync) ツールを使用して、個々のアクションリポジトリを {% data variables.product.prodname_dotcom_the_website %} から Enterprise に同期できます。 +However, if you want stricter control over which actions are allowed in your enterprise, you{% else %}You{% endif %} can follow this guide to use {% data variables.product.company_short %}'s open source [`actions-sync`](https://github.com/actions/actions-sync) tool to sync individual action repositories from {% data variables.product.prodname_dotcom_the_website %} to your enterprise. ## `actions-sync` ツールについて @@ -33,7 +34,7 @@ shortTitle: Manually sync actions ## 必要な環境 * `actions-sync` ツールを使用する前に、すべての宛先 Organization が Enterprise にすでに存在していることを確認する必要があります。 次の例は、`synced-actions` という名前の Organization にアクションを同期する方法を示しています。 詳しい情報については、「[新しい Organization をゼロから作成する](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)」を参照してください。 -* Enterprise に、宛先 Organization のリポジトリを作成して書き込むことができる個人アクセストークン (PAT) を作成する必要があります。 詳しい情報については、「[個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token)」を参照してください。 +* Enterprise に、宛先 Organization のリポジトリを作成して書き込むことができる個人アクセストークン (PAT) を作成する必要があります。 For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."{% ifversion ghes %} * {% data variables.product.product_location %} の `actions` の Organization でバンドルされたアクションを同期する場合は、`actions` の Organization の所有者である必要があります。 {% note %} @@ -46,21 +47,21 @@ shortTitle: Manually sync actions ```shell ghe-org-admin-promote -u USERNAME -o actions - ``` + ```{% endif %} -## 例: `actions-sync` ツールを使用する +## Example: Using the `actions-sync` tool -この例は、`actions-sync` ツールを使用して、個々のアクションを {% data variables.product.prodname_dotcom_the_website %} から Enterprise インスタンスに同期する方法を示しています。 +This example demonstrates using the `actions-sync` tool to sync an individual action from {% data variables.product.prodname_dotcom_the_website %} to an enterprise instance. {% note %} -**注釈:** この例では、`actions-sync sync` コマンドを使用します。これには、マシンから {% data variables.product.prodname_dotcom_the_website %} API と Enterprise インスタンスの API の両方への同時アクセスが必要です。 一度に 1 つのシステムにのみアクセスできる場合は、`actions-sync pull` および `push` コマンドを使用できます。 詳しい情報については、「[`actions/cache` README](https://github.com/actions/actions-sync#not-connected-instances)」を参照してください。 +**Note:** This example uses the `actions-sync sync` command, which requires concurrent access to both the {% data variables.product.prodname_dotcom_the_website %} API and your enterprise instance's API from your machine. If you can only access one system at a time, you can use the `actions-sync pull` and `push` commands. For more information, see the [`actions-sync` README](https://github.com/actions/actions-sync#not-connected-instances). {% endnote %} -1. マシンのオペレーティングシステムの最新の [`actions-sync` リリース](https://github.com/actions/actions-sync/releases)をダウンロードして抽出します。 +1. Download and extract the latest [`actions-sync` release](https://github.com/actions/actions-sync/releases) for your machine's operating system. 1. ツールのキャッシュファイルを保存するディレクトリを作成します。 -1. `actions-sync sync` コマンドを実行します。 +1. Run the `actions-sync sync` command: ```shell ./actions-sync sync \ diff --git a/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md b/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md index 30ab3d2f37..2697e338e0 100644 --- a/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md +++ b/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md @@ -14,7 +14,6 @@ shortTitle: Tool cache for offline runners {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 含まれているセットアップアクションとランナーツールキャッシュについて 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 d7ba87712d..463b74d1fd 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 @@ -13,7 +13,6 @@ shortTitle: Use the latest bundled actions {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} Your enterprise instance includes a number of built-in actions that you can use in your workflows. For more information about the bundled actions, see "[Official actions bundled with your enterprise instance](/admin/github-actions/about-using-actions-in-your-enterprise#official-actions-bundled-with-your-enterprise-instance)." @@ -29,17 +28,13 @@ You can use {% data variables.product.prodname_github_connect %} to allow {% dat Once {% data variables.product.prodname_github_connect %} is configured, you can use the latest version of an action by deleting its local repository in the `actions` organization on your instance. For example, if your enterprise instance is using the `actions/checkout@v1` action, and you need to use `actions/checkout@v2` which isn't available on your enterprise instance, perform the following steps to be able to use the latest `checkout` action from {% data variables.product.prodname_dotcom_the_website %}: -1. By default, site administrators are not owners of the bundled actions organization. To get the required access to delete the `checkout` repository, use the `ghe-org-admin-promote` command to promote a user to be an owner of the bundled `actions` organization. 詳しい情報については、「[管理シェル (SSH) へのアクセス](/admin/configuration/accessing-the-administrative-shell-ssh)」および「[`ghe-org-admin-promote`](/admin/configuration/command-line-utilities#ghe-org-admin-promote)」を参照してください。 例: - - ```shell - $ ghe-org-admin-promote -u octocat -o actions - Do you want to give organization admin privileges for actions to octocat? (y/N) y - Making octocat an admin of actions - --> Adding octocat as an admin of actions - --> octocat is now an admin of the actions organization - --> Done. - ``` -1. On your {% data variables.product.product_name %} instance, delete the `checkout` repository within the `actions` organization. For information on how to delete a repository, see "[Deleting a repository ](/github/administering-a-repository/deleting-a-repository)." -1. It is recommended that you leave the `actions` organization once you no longer require administrative access. For more information, see "[Removing yourself from an organization ](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization)." +1. From an enterprise owner account on {% data variables.product.product_name %}, navigate to the repository you want to delete from the *actions* organization (in this example `checkout`). +1. By default, site administrators are not owners of the bundled *actions* organization. To get the access required to delete the `checkout` repository, you must use the site admin tools. Click {% octicon "rocket" aria-label="The rocket ship" %} in the upper-right corner of any page in that repository. ![サイトアドミン設定にアクセスするための宇宙船のアイコン](/assets/images/enterprise/site-admin-settings/access-new-settings.png) +1. Click {% octicon "shield-lock" %} **Security** to see the security overview for the repository. ![Security header the repository](/assets/images/enterprise/site-admin-settings/access-repo-security-info.png) +1. Under "Privileged access", click **Unlock**. ![Unlock button](/assets/images/enterprise/site-admin-settings/unlock-priviledged-repo-access.png) +1. Under **Reason**, type a reason for unlocking the repository, then click **Unlock**. ![Confirmation dialog](/assets/images/enterprise/site-admin-settings/confirm-unlock-repo-access.png) +1. Now that the repository is unlocked, you can leave the site admin pages and delete the repository within the `actions` organization. At the top of the page, click the repository name, in this example **checkout**, to return to the summary page. ![Repository name link](/assets/images/enterprise/site-admin-settings/display-repository-admin-summary.png) +1. Under "Repository info", click **View code** to leave the site admin pages and display the `checkout` repository. +1. Delete the `checkout` repository within the `actions` organization. For information on how to delete a repository, see "[Deleting a repository](/github/administering-a-repository/deleting-a-repository)." ![View code link](/assets/images/enterprise/site-admin-settings/exit-admin-page-for-repository.png) 1. Configure your workflow's YAML to use `actions/checkout@v2`. 1. Each time your workflow runs, the runner will use the `v2` version of `actions/checkout` from {% data variables.product.prodname_dotcom_the_website %}. diff --git a/translations/ja-JP/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md b/translations/ja-JP/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md index b2f7efd25e..bdd2938044 100644 --- a/translations/ja-JP/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md +++ b/translations/ja-JP/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md @@ -13,7 +13,6 @@ redirect_from: - /admin/github-actions/getting-started-with-github-actions-for-github-ae --- -{% data reusables.actions.ae-beta %} この記事では、サイト管理者が {% data variables.product.prodname_actions %} を使用するように {% data variables.product.prodname_ghe_managed %} を設定する方法について説明しています。 diff --git a/translations/ja-JP/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md b/translations/ja-JP/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md index e06726891a..f52c7a2ddc 100644 --- a/translations/ja-JP/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md +++ b/translations/ja-JP/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md @@ -8,7 +8,6 @@ redirect_from: shortTitle: Use actions --- -{% data reusables.actions.ae-beta %} {% data variables.product.prodname_actions %} ワークフローは_アクション_を使用できます。アクションは、ジョブを作成してワークフローをカスタマイズするために組み合わせることができる個々のタスクです。 独自のアクションの作成、または {% data variables.product.prodname_dotcom %} コミュニティによって共有されるアクションの使用やカスタマイズができます。 diff --git a/translations/ja-JP/content/admin/guides.md b/translations/ja-JP/content/admin/guides.md index fe485efda7..198bcf27f2 100644 --- a/translations/ja-JP/content/admin/guides.md +++ b/translations/ja-JP/content/admin/guides.md @@ -35,13 +35,13 @@ includeGuides: - /admin/configuration/configuring-rate-limits - /admin/configuration/configuring-secret-scanning-for-your-appliance - /admin/configuration/configuring-tls - - /admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud + - /admin/configuration/connecting-your-enterprise-account-to-github-enterprise-cloud - /admin/configuration/enabling-and-scheduling-maintenance-mode - /admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud - /admin/configuration/enabling-private-mode - /admin/configuration/enabling-subdomain-isolation - - /admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom - - /admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom + - /admin/configuration/enabling-unified-contributions-between-your-enterprise-account-and-githubcom + - /admin/configuration/enabling-unified-search-between-your-enterprise-account-and-githubcom - /admin/configuration/initializing-github-ae - /admin/configuration/managing-github-for-mobile-for-your-enterprise - /admin/configuration/network-ports diff --git a/translations/ja-JP/content/admin/overview/about-upgrades-to-new-releases.md b/translations/ja-JP/content/admin/overview/about-upgrades-to-new-releases.md index e614fcef6f..c5021f0928 100644 --- a/translations/ja-JP/content/admin/overview/about-upgrades-to-new-releases.md +++ b/translations/ja-JP/content/admin/overview/about-upgrades-to-new-releases.md @@ -13,7 +13,7 @@ topics: {% data variables.product.product_name %} は常に改善されており、メジャーリリースとマイナーリリースで新機能とバグ修正が導入されています。 {% ifversion ghae %}{% data variables.product.prodname_ghe_managed %} はフルマネージドサービスであるため、{% data variables.product.company_short %} が Enterprise のアップグレードプロセスを完了します。{% endif %} -メジャーリリースには、新機能と機能のアップグレードが含まれ、通常、{% ifversion ghae %}数週間または数か月{% else %}四半期ごとに発生します。{% endif %} {% ifversion ghae %}{% data variables.product.company_short %} は、Enterprise を最新のメジャーリリースにアップグレードします。 Enterprise で予定されているダウンタイムについては、事前に通知されます。{% endif %} +通常、メジャーリリースは四半期ごとに行われ、新機能と機能のアップグレードが含まれます。 {% ifversion ghae %}{% data variables.product.company_short %} は、Enterprise を最新のメジャーリリースにアップグレードします。 Enterprise で予定されているダウンタイムについては、事前に通知されます。{% endif %} {% ifversion ghes %} @@ -43,7 +43,6 @@ Enterprise を新しいリリースにアップグレードするには、「[ ## 参考リンク -- `github/roadmap` リポジトリの [ {% data variables.product.prodname_roadmap %} ]({% data variables.product.prodname_roadmap_link %}) -{% ifversion ghae %} +- [ {% data variables.product.prodname_roadmap %} ]({% data variables.product.prodname_roadmap_link %}) in the `github/roadmap` repository{% ifversion ghae %} - [ {% data variables.product.prodname_ghe_managed %} のリリースノート](/admin/release-notes) {% endif %} diff --git a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise.md b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise.md new file mode 100644 index 0000000000..0f9431c5d5 --- /dev/null +++ b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise.md @@ -0,0 +1,59 @@ +--- +title: Enterprise に GitHub Actions のポリシーを適用する +intro: 'Enterprise 管理者は、Enterprise 内の {% data variables.product.prodname_actions %} へのアクセスを管理できます。' +redirect_from: + - /enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise + - /admin/github-actions/enforcing-github-actions-policies-for-your-enterprise + - /admin/github-actions/enabling-github-actions-for-github-enterprise-server/enforcing-github-actions-policies-for-your-enterprise +versions: + ghes: '*' + ghae: '*' +type: how_to +topics: + - Actions + - Enterprise + - Policies +shortTitle: GitHub Actions policies +--- + +{% data reusables.actions.enterprise-beta %} + +## Enterprise の {% data variables.product.prodname_actions %} 権限について + +{% ifversion ghae %}{% else %}{% data variables.product.prodname_ghe_server %} で {% data variables.product.prodname_actions %} を有効にすると、Enterprise 内のすべての Organization で有効化されます。 {% endif %} Enterprise 内のすべての Organization に対して {% data variables.product.prodname_actions %} を無効にするか、特定の Organization のみを許可するかを選択できます。 Enterprise にあるローカルのアクションだけ利用できるように、パブリックなアクションの利用を制限することもできます。 + +## Enterprise の {% data variables.product.prodname_actions %} 権限の管理 + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.actions-tab %} +{% data reusables.actions.enterprise-actions-permissions %} + +{% ifversion ghes > 2.22 or ghae %} +## 特定のアクションの実行を許可する + +{% data reusables.actions.allow-specific-actions-intro %} + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.actions-tab %} +1. [**Policies**] で [**Allow select actions**] を選択し、必要なアクションをリストに追加します。 + {%- ifversion ghes or ghae-issue-5094 %} + ![許可リストにアクションを追加する](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png) + {%- elsif ghae %} + ![許可リストにアクションを追加する](/assets/images/enterprise/github-ae/enterprise-actions-policy-allow-list.png) + {%- endif %} +{% endif %} + +{% ifversion ghes > 2.22 or ghae %} +## プライベートリポジトリのフォークのワークフローを有効にする + +{% data reusables.github-actions.private-repository-forks-overview %} + +### Enterprise のプライベートフォークポリシーを設定する + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.actions-tab %} +{% data reusables.github-actions.private-repository-forks-configure %} +{% endif %} diff --git a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md index 1066796c6b..d1162fec7b 100644 --- a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md +++ b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md @@ -34,7 +34,7 @@ topics: - Enterprise - Policies - Security -shortTitle: Enforce repository policies +shortTitle: Repository management policies --- ## Enterprise 内の新しいリポジトリのデフォルトの可視性を設定する diff --git a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/index.md b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/index.md index 02e257d087..f7fb0838c0 100644 --- a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/index.md +++ b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/index.md @@ -11,6 +11,7 @@ topics: children: - /enforcing-repository-management-policies-in-your-enterprise - /restricting-email-notifications-for-your-enterprise + - /enforcing-github-actions-policies-for-your-enterprise - /enforcing-policies-for-advanced-security-in-your-enterprise shortTitle: Enforce policies --- diff --git a/translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md b/translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md index 222f5c98fb..f14684d5d7 100644 --- a/translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md +++ b/translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md @@ -30,6 +30,9 @@ SAML SSO を使用すると、Enterprise のオーナーは、SAML IdP から {% {% data reusables.saml.dotcom-saml-explanation %}Organization のオーナーは、{% data variables.product.prodname_dotcom %}でユーザアカウントを SAML SSO を使用する Organization に招待できます。これにより、Organization に貢献することができ、{% data variables.product.prodname_dotcom %}の既存の ID とコントリビューションを保持できます。 +If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you will use a new account that is provisioned for you. {% data reusables.enterprise-accounts.emu-more-info-account %} + + SAML SSO を使用する Organization のリソースにアクセスすると、{% data variables.product.prodname_dotcom %}は認証のために Organization の SAML IdP にリダイレクトします。 IdP でアカウントが正常に認証されると、IdP は{% data variables.product.prodname_dotcom %}に戻り、Organization のリソースにアクセスできます。 {% data reusables.saml.outside-collaborators-exemption %} diff --git a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md index 286b28842b..e7b9952392 100644 --- a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md +++ b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md @@ -20,7 +20,7 @@ shortTitle: Generate new SSH key If you don't already have an SSH key, you must generate a new SSH key to use for authentication. If you're unsure whether you already have an SSH key, you can check for existing keys. For more information, see "[Checking for existing SSH keys](/github/authenticating-to-github/checking-for-existing-ssh-keys)." -{% ifversion fpt %} +{% ifversion fpt or ghae-next or ghes > 3.1 %} If you want to use a hardware security key to authenticate to {% data variables.product.product_name %}, you must generate a new SSH key for your hardware security key. You must connect your hardware security key to your computer when you authenticate with the key pair. For more information, see the [OpenSSH 8.2 release notes](https://www.openssh.com/txt/release-8.2). @@ -31,6 +31,12 @@ If you don't want to reenter your passphrase every time you use your SSH key, yo {% data reusables.command_line.open_the_multi_os_terminal %} 2. 以下のテキストを貼り付けます。メールアドレスは自分の {% data variables.product.product_name %} メールアドレスに置き換えてください。 + {% ifversion ghae %} + + ```shell + $ ssh-keygen -t rsa -b 4096 -C "your_email@example.com" + ``` + {% else %} ```shell $ ssh-keygen -t ed25519 -C "your_email@example.com" ``` @@ -38,20 +44,22 @@ If you don't want to reenter your passphrase every time you use your SSH key, yo **注釈:** Ed25519 アルゴリズムをサポートしないレガシーシステムを使用している場合は、以下を使用します。 ```shell - $ ssh-keygen -t rsa -b 4096 -C "your_email@example.com" + $ ssh-keygen -t rsa -b 4096 -C "your_email@example.com" ``` {% endnote %} + {% endif %} + This creates a new SSH key, using the provided email as a label. ```shell - > Generating public/private ed25519 key pair. + > Generating public/private algorithm key pair. ``` 3. 「Enter a file in which to save the key」というメッセージが表示されたら、Enter キーを押します。 これにより、デフォルトのファイル場所が受け入れられます。 {% mac %} ```shell - > Enter a file in which to save the key (/Users/you/.ssh/id_ed25519): [Press enter] + > Enter a file in which to save the key (/Users/you/.ssh/id_algorithm): [Press enter] ``` {% endmac %} @@ -59,7 +67,7 @@ If you don't want to reenter your passphrase every time you use your SSH key, yo {% windows %} ```shell - > Enter a file in which to save the key (/c/Users/you/.ssh/id_ed25519):[Press enter] + > Enter a file in which to save the key (/c/Users/you/.ssh/id_algorithm):[Press enter] ``` {% endwindows %} @@ -67,7 +75,7 @@ If you don't want to reenter your passphrase every time you use your SSH key, yo {% linux %} ```shell - > Enter a file in which to save the key (/home/you/.ssh/id_ed25519): [Press enter] + > Enter a file in which to save the key (/home/you/.ssh/algorithm): [Press enter] ``` {% endlinux %} @@ -107,7 +115,7 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav Host * AddKeysToAgent yes UseKeychain yes - IdentityFile ~/.ssh/id_ed25519 + IdentityFile ~/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %} ``` {% note %} @@ -137,7 +145,7 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav 3. SSH 秘密鍵を ssh-agent に追加して、パスフレーズをキーチェーンに保存します。 {% data reusables.ssh.add-ssh-key-to-ssh-agent %} ```shell - $ ssh-add -K ~/.ssh/id_ed25519 + $ ssh-add -K ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %} ``` {% note %} @@ -189,8 +197,10 @@ If you are using macOS or Linux, you may need to update your SSH client or insta {% data reusables.command_line.open_the_multi_os_terminal %} 3. Paste the text below, substituting in the email address for your account on {% data variables.product.product_name %}. ```shell - $ ssh-keygen -t ed25519-sk -C "your_email@example.com" + $ ssh-keygen -t {% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}-sk -C "your_email@example.com" ``` + + {% ifversion not ghae %} {% note %} **Note:** If the command fails and you receive the error `invalid format` or `feature not supported,` you may be using a hardware security key that does not support the Ed25519 algorithm. Enter the following command instead. @@ -199,13 +209,14 @@ If you are using macOS or Linux, you may need to update your SSH client or insta ``` {% endnote %} + {% endif %} 4. When you are prompted, touch the button on your hardware security key. 5. When you are prompted to "Enter a file in which to save the key," press Enter to accept the default file location. {% mac %} ```shell - > Enter a file in which to save the key (/Users/you/.ssh/id_ed25519_sk): [Press enter] + > Enter a file in which to save the key (/Users/you/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): [Press enter] ``` {% endmac %} @@ -213,7 +224,7 @@ If you are using macOS or Linux, you may need to update your SSH client or insta {% windows %} ```shell - > Enter a file in which to save the key (/c/Users/you/.ssh/id_ed25519_sk):[Press enter] + > Enter a file in which to save the key (/c/Users/you/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk):[Press enter] ``` {% endwindows %} @@ -221,7 +232,7 @@ If you are using macOS or Linux, you may need to update your SSH client or insta {% linux %} ```shell - > Enter a file in which to save the key (/home/you/.ssh/id_ed25519_sk): [Press enter] + > Enter a file in which to save the key (/home/you/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): [Press enter] ``` {% endlinux %} 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 e24aae53bd..bca44d423c 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 @@ -28,6 +28,10 @@ shortTitle: Authentication to GitHub IdP を使用して、ブラウザ {% ifversion ghae %} で {% data variables.product.product_name %} に認証できます。 詳しい情報については、いくつかの方法で{% else %}「[SAML シングルサインオンでの認証について](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)」を参照してください。 +- {% ifversion fpt %} +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](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users#authenticating-as-a-managed-user)". If you're not a member of an {% data variables.product.prodname_emu_enterprise %}, you will authenticate using your browser on {% data variables.product.prodname_dotcom_the_website %}. +{% endif %} + - **ユーザ名とパスワードのみ** - {% data variables.product.product_name %} でユーザアカウントを作成するときにパスワードを作成します。 パスワードマネージャを使用して、ランダムで一意のパスワードを生成することをお勧めします。 詳しい情報については、「[強力なパスワードを作成する](/github/authenticating-to-github/creating-a-strong-password)」を参照してください。 - **2 要素認証 (2FA)**（推奨） 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 268804226b..ad5d6e4e0f 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 @@ -38,7 +38,7 @@ A token with no assigned scopes can only access public information. トークン {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.developer_settings %} {% data reusables.user_settings.personal_access_tokens %} -4. [**Generate new token**] をクリックします。 ![[Generate new token] ボタン](/assets/images/help/settings/generate_new_token.png) +{% 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 %} 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**] を選択します。 diff --git a/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md b/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md index c6e04c2d48..652fceb236 100644 --- a/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md +++ b/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md @@ -75,33 +75,6 @@ shortTitle: Configure 2FA recovery 設定後、バックアップデバイスが確認の SMS を受信します。 -## Recovery Accounts Elsewhere でフォールバック認証方式を追加する - -アカウントに対して追加の認証クレデンシャルを生成し、パートナーリカバリプロバイダを利用して保存できます。 - -### Recovery Accounts Elsewhere について - -Recover Accounts Elsewhere を使うと、2 要素認証やリカバリコードへのアクセスを失った場合に備えて、あなたの {% data variables.product.product_name %} アカウントにセキュリティ要素を追加できます。 - -Recovery Accounts Elsewhere を使用して、あなたの {% data variables.product.product_name %}アカウントをあなたの Facebook アカウントに関連付けることができます。 Facebook により、_アカウントリカバリトークン_として、あなたの {% data variables.product.product_name %} アカウントの認証クレデンシャルを保存できます。 - -2 要素認証方法やリカバリコードにアクセスができなくなったために、{% data variables.product.product_name %} へのアクセスをなくした場合でも、リカバリプロバイダーからアカウントリカバリトークンを取得できます。これはあなたが {% data variables.product.product_name %} アカウントのオーナーであることを証明するのに役立ちます。 - -トークンを再取得後、{% data variables.contact.contact_support %} はあなたのアカウントで 2 要素認証を無効にできるかもしれません。 その後、アカウントに再びアクセスするため、パスワードを入力またはリセットできます。 - -アカウントリカバリトークンを生成または取得すると、アカウントの Audit log にイベントが追加されます。 詳細は「[セキュリティログをレビューする](/articles/reviewing-your-security-log)」を参照してください。 - -### アカウントリカバリトークンを生成、保存する - -アカウントリカバリトークンを生成し、パートナーリカバリプロバイダを利用して保存できます。 - -1. あなたの Facebook アカウントにサインインしてから、{% data variables.product.product_name %} に戻ります。 -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.security %} -4. 新しいトークンを生成するため、[Recovery tokens] の下にある [**Store new token**] をクリックします。 ![新しいリカバリトークンを保存するボタン](/assets/images/help/settings/store-new-recovery-token.png) -5. アカウントリカバリトークンに関する情報を読み、[**Connect with https://www.facebook.com**] をクリックします。 ![リカバリトークンを Facebook と関連付けるボタン](/assets/images/help/settings/connect-recovery-token-with-facebook.png) -6. Facebook にリダイレクト後、Facebook でアカウントリカバリをオンにすることに関する情報を読んでから、[**Save as [_あなたの名前_]**] をクリックします。 (短時間で複数のトークンを保存する場合、最初のトークンを保存した後は、Facebook がこの確認を省略することがあります。) ![アカウントリカバリを有効にするボタンがある Facebook ページ](/assets/images/help/settings/security-turn-on-rae-facebook.png) - {% endif %} ## 参考リンク diff --git a/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md b/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md index 3a9e9d2f52..c59daff659 100644 --- a/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md +++ b/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md @@ -28,6 +28,12 @@ shortTitle: Configure 2FA {% endwarning %} +{% ifversion fpt %} + +If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you cannot configure 2FA for your {% data variables.product.prodname_managed_user %} account. 2FA should be configured through your identity provider. + +{% endif %} + ## TOTP モバイルアプリを使って 2要素認証を設定する 時間ベースのワンタイムパスワード (TOTP) アプリケーションは、認証コードを自動的に生成します。このコードは、一定の時間が過ぎた後は変化します。 以下のような、クラウドベースの TOTP アプリの利用をおすすめします: diff --git a/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md b/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md index bd38d520a6..ff0b0f7e0b 100644 --- a/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md +++ b/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md @@ -71,6 +71,12 @@ If you know your {% data variables.product.product_name %} password but don't ha ## アカウントリカバリトークンによる認証 +{% warning %} + +**Warning:** Account recovery tokens are deprecated and will be disabled on **December 1st, 2021**. Please ensure you have configured other two-factor recovery methods. For more information, see "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)." + +{% endwarning %} + {% data variables.product.product_name %} アカウントの 2 要素認証方式へのアクセスをなくした場合でも、アカウントリカバリトークンをパートナーリカバリプロバイダから再取得して、{% data variables.product.prodname_dotcom %} Support にレビューを依頼することができます。 2 要素認証方式やリカバリコードへのアクセスがない場合でも、Recovery Accounts Elsewhere を使用して Facebook にアカウントリカバリトークンを格納してあれば、トークンを使用してアカウントへのアクセスを再取得できる可能性があります。 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 47ca45c5c3..dcc5b1144d 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 @@ -68,6 +68,8 @@ Microsoft Enterprise Agreement を通じて {% data variables.product.prodname_e ## 利用時間 (分) とストレージ消費量の計算 +{% data reusables.dotcom_billing.pricing_cal %} + 月末に、{% data variables.product.prodname_dotcom %}はアカウントに含まれている量に対して使用された分とストレージのコストを計算します。 ### Sample minutes cost calculation diff --git a/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md b/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md index 6df73b8952..98ab6506a3 100644 --- a/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md +++ b/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md @@ -28,6 +28,8 @@ topics: 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 {% data variables.product.prodname_codespaces %} usage. 詳しい情報については、「[Azure サブスクリプションを Enterprise に接続する](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)」を参照してください。 +{% data reusables.dotcom_billing.pricing_cal %} + ## Setting a spending limit {% data reusables.codespaces.codespaces-spending-limit-requirement %} 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 8db31e409b..94acc57a11 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,7 +49,7 @@ Microsoft Enterprise Agreement を通じて {% data variables.product.prodname_e {% 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.25 USD per GB of storage and $0.50 USD per GB of data transfer. -たとえば、Organizationが{% data variables.product.prodname_team %}を使用し、無制限の利用を許可しており、1か月あたりのストレージ使用量が150 GB、データ転送が50GBだった場合、そのOrganizationの当月の超過分はストレージが148GB、データ転送が40GBということです。 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. +たとえば、Organizationが{% data variables.product.prodname_team %}を使用し、無制限の利用を許可しており、1か月あたりのストレージ使用量が150 GB、データ転送が50GBだった場合、そのOrganizationの当月の超過分はストレージが148GB、データ転送が40GBということです。 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. {% data reusables.dotcom_billing.pricing_cal %} 月末に、{% data variables.product.prodname_dotcom %}はデータ転送を最も近いGBに丸めます。 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 c920cdae3a..9193c8eff9 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 @@ -68,11 +68,9 @@ shortTitle: Code scanningの設定 プッシュ時にスキャンするなら、結果はリポジトリの** Security（セキュリティ）**タブに表示されます。 詳しい情報については、「[リポジトリの コードスキャンアラートを管理する](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)」を参照してください。 -{% note %} - -**ノート**: {% data variables.product.prodname_code_scanning %}アラートをPull Requestのチェックとして表示させたいなら、以下に述べる`pull_request`イベントを使わなければなりません。 - -{% endnote %} +{% ifversion fpt or ghes > 3.2 or ghae-issue-5093 %} +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 %} ### プルリクエストをスキャンする @@ -82,6 +80,10 @@ shortTitle: Code scanningの設定 Pull Requestをスキャンすると、その結果はPull Requestチェック内のアラートとして表示されます。 詳しい情報については、「[プルリクエストでコードスキャンアラートをトリアージする](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)」を参照してください。 +{% ifversion fpt or ghes > 3.2 or ghae-issue-5093 %} + 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 %} + {% ifversion fpt or ghes > 3.1 or ghae-next %} ### Defining the severities causing pull request check failure @@ -155,7 +157,7 @@ on: ## オペレーティングシステムを指定する -コードのコンパイルに特定のオペレーティングシステムが必要な場合は、そのオペレーティングシステムを {% data variables.product.prodname_codeql_workflow %} で設定できます。 `jobs.analyze.runs-on` の値を編集して、{% data variables.product.prodname_code_scanning %} のアクションを実行するマシンのオペレーティングシステムを指定します。 {% ifversion ghes %}オペレーティングシステムの指定には、`self-hosted` の後に、2 つの要素がある配列の 2 番目の要素として、適切なラベルを使用します。{% else %} +コードのコンパイルに特定のオペレーティングシステムが必要な場合は、そのオペレーティングシステムを {% data variables.product.prodname_codeql_workflow %} で設定できます。 `jobs.analyze.runs-on` の値を編集して、{% data variables.product.prodname_code_scanning %} のアクションを実行するマシンのオペレーティングシステムを指定します。 {% ifversion ghes %}You specify the operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% else %} Code Scanningにセルフホストランナーを使うことにしたなら、`self-hosted` の後に、2 つの要素がある配列の 2 番目の要素として適切なラベルを使用し、オペレーティングシステムを指定できます。{% endif %} @@ -168,9 +170,9 @@ jobs: {% ifversion fpt %}詳しい情報については、「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners)」および「[セルフホストランナーを追加する](/actions/hosting-your-own-runners/adding-self-hosted-runners)」を参照してください。{% endif %} -{% data variables.product.prodname_code_scanning_capc %} は、macOS、Ubuntu、Windows の最新バージョンをサポートしています。 Typical values for this setting are therefore: `ubuntu-latest`, `windows-latest`, and `macos-latest`. 詳しい情報については、{% ifversion ghes %}「[GitHub Actions のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)」および「[セルフホストランナーでラベルを使用する](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)」{% else %}「[GitHub Actionsのワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on)」{% endif %}を参照してください。 +{% data variables.product.prodname_code_scanning_capc %} は、macOS、Ubuntu、Windows の最新バージョンをサポートしています。 Typical values for this setting are therefore: `ubuntu-latest`, `windows-latest`, and `macos-latest`. For more information, see {% ifversion ghes %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" and "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}." -{% ifversion ghes %}GitがセルフホストランナーのPATH変数内にあるようにしなければなりません。{% else %}セルフホストランナーを使っているなら、GitがPATH変数内にあるようにしなければなりません。{% endif %} +{% ifversion ghes %}You must ensure that Git is in the PATH variable on your self-hosted runners.{% else %}If you use a self-hosted runner, you must ensure that Git is in the PATH variable.{% endif %} {% ifversion fpt or ghes > 3.1 or ghae-next %} ## {% data variables.product.prodname_codeql %}データベースの場所の指定 @@ -234,7 +236,6 @@ Alternatively, you can install Python dependencies manually on any operating sys ```yaml jobs: CodeQL-Build: - runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae-next %} permissions: security-events: write @@ -253,20 +254,20 @@ jobs: if [ -f requirements.txt ]; then pip install -r requirements.txt; fi - # 環境変数`CODEQL-PYTHON`を - # 依存関係を含むPythonの実行可能ファイルに設定 + # Set the `CODEQL-PYTHON` environment variable to the Python executable + # that includes the dependencies echo "CODEQL_PYTHON=$(which python)" >> $GITHUB_ENV - name: Initialize CodeQL uses: github/codeql-action/init@v1 with: languages: python - # デフォルトの動作をオーバーライドして、アクションが - # Pythonの依存関係を自動インストールしないようにする + # Override the default behavior so that the action doesn't attempt + # to auto-install Python dependencies setup-python-dependencies: false ``` {% endif %} -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ## 分析のカテゴリの設定 `category`を使って、同じツールやコミットに対して行われる、ただし様々な言語やコードの様々な部分に対して行われる複数の分析を区別してください。 ワークフロー中で指定したカテゴリは、SARIF結果ファイルに含まれます。 @@ -285,7 +286,7 @@ jobs: ``` {% endraw %} -ワークフローで`category`を指定しない場合、{% data variables.product.product_name %}はアクションをトリガーしたワークフロー名、アクション名、任意のマトリクス変数に基づいてカテゴリ名を生成します。 例: +If you don't specify a `category` parameter in your workflow, {% data variables.product.product_name %} will generate a category name for you, based on the name of the workflow file triggering the action, the action name, and any matrix variables. 例: - `.github/workflows/codeql-analysis.yml`ワークフローと`analyze`アクションは、`.github/workflows/codeql.yml:analyze`というカテゴリを生成します。 - `.github/workflows/codeql-analysis.yml`ワークフロー、`analyze`アクション、マトリクス変数`{language: javascript, os: linux}`は、`.github/workflows/codeql-analysis.yml:analyze/language:javascript/os:linux`というカテゴリを生成します。 diff --git a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md index d0657c491a..16b54f4a88 100644 --- a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md @@ -48,9 +48,9 @@ topics: Alert severity levels may be `Error`, `Warning`, or `Note`. -By default, any code scanning results with a severity of `error` will cause check failure. {% ifversion fpt or ghes > 3.1 or ghae-next %}You can specify the severity level at which pull requests that trigger code scanning alerts should fail. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %} +By default, any code scanning results with a severity of `error` will cause check failure. {% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %}You can specify the severity level at which pull requests that trigger code scanning alerts should fail. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %} +{% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %} ### About security severity levels {% data variables.product.prodname_code_scanning_capc %} displays security severity levels for alerts that are generated by security queries. Security severity levels can be `Critical`, `High`, `Medium`, or `Low`. @@ -70,10 +70,10 @@ By default, the code scanning alerts page is filtered to show alerts for the def {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-code-scanning-alerts %} -{% ifversion fpt or ghes > 3.1 %} -1. あるいは{% ifversion fpt or ghes > 3.1 %}自由テキスト検索ボックスもしくは{% endif %}ドロップダウンメニューを使ってアラートをフィルタしてください。 たとえば、アラートを識別するために使われたツールによってフィルタリングできます。 ![Filter by tool](/assets/images/help/repository/code-scanning-filter-by-tool.png){% endif %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} +1. Optionally, use the free text search box or the drop-down menus to filter alerts. たとえば、アラートを識別するために使われたツールによってフィルタリングできます。 ![Filter by tool](/assets/images/help/repository/code-scanning-filter-by-tool.png){% endif %} 1. [{% data variables.product.prodname_code_scanning_capc %}] で、調査するアラートをクリックします。 -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ![アラートの概要](/assets/images/help/repository/code-scanning-click-alert.png) {% else %} ![{% data variables.product.prodname_code_scanning %}からのアラートのリスト](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) @@ -81,7 +81,7 @@ By default, the code scanning alerts page is filtered to show alerts for the def 1. アラートでデータフローの問題が強調表示された場合は、必要に応じて [**Show paths**] をクリックし、データソースから、それが使用されているシンクまでのパスを表示します。 ![アラートの [Show paths] リンク](/assets/images/help/repository/code-scanning-show-paths.png) 1. {% data variables.product.prodname_codeql %} 解析によるアラートには、問題の説明も含まれています。 コードを修正する方法についてのガイダンスを表示するには、[**Show more**] をクリックします。 ![アラートの詳細情報](/assets/images/help/repository/code-scanning-alert-details.png) -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} {% note %} **ノート:** {% data variables.product.prodname_codeql %}での{% data variables.product.prodname_code_scanning %}分析に対して、リポジトリの{% data variables.product.prodname_code_scanning %}アラートのリストの上部にあるヘッダ中で、最新の実行に関する情報を見ることができます。 @@ -91,7 +91,6 @@ By default, the code scanning alerts page is filtered to show alerts for the def {% endnote %} {% endif %} - ## Filtering {% data variables.product.prodname_code_scanning %} alerts You can filter the alerts shown in the {% data variables.product.prodname_code_scanning %} alerts view. This is useful if there are many alerts as you can focus on a particular type of alert. There are some predefined filters and a range of keywords that you can use to refine the list of alerts displayed. @@ -105,7 +104,21 @@ You can filter the alerts shown in the {% data variables.product.prodname_code_s The benefit of using keyword filters is that only values with results are shown in the drop-down lists. This makes it easy to avoid setting filters that find no results. +If you enter multiple filters, the view will show alerts matching _all_ these filters. For example, `is:closed severity:high branch:main` will only display closed high-severity alerts that are present on the `main` branch. The exception is filters relating to refs (`ref`, `branch` and `pr`): `is:open branch:main branch:next` will show you open alerts from both the `main` branch and the `next` branch. + +### Restricting results to application code only + +You can use the "Only alerts in application code" filter or `autofilter:true` keyword and value to restrict results to alerts in application code. Application code excludes the following. + +- Code generated by the build process +- Test code +- Library or third-party code +- ドキュメント + +{% data variables.product.prodname_code_scanning_capc %} categorizes files by file path. At this time, you cannot manually categorize source files. + {% ifversion fpt or ghes > 3.1 %} + ## {% data variables.product.prodname_code_scanning %}アラートの検索 アラートのリストを検索できます。 これは、リポジトリ中に大量のアラートがある場合や、たとえばアラートの正確な名前を知らないような場合に役立ちます。 {% data variables.product.product_name %}は以下に渡って自由テキスト検索を行います。 @@ -145,11 +158,11 @@ The benefit of using keyword filters is that only values with results are shown リポジトリへの書き込み権限がある場合は、アラートの概要を表示して、[**Closed**] をクリックすることで、解決したアラートを表示できます。 詳しい情報については、「[リポジトリのアラートを表示する](#viewing-the-alerts-for-a-repository)」を参照してください。 "Closed"リストは、修正されたアラートと、ユーザが却下したアラートを示します。 -{% ifversion fpt or ghes > 3.1 %}自由テキスト検索もしくは{% endif %}フィルタを使って、アラートの一部を表示してから、マッチするすべてのアラートをクローズされたものとしてマークできます。 +{% ifversion fpt or ghes > 3.1 or ghae-next %}自由テキスト検索もしくは{% endif %}フィルタを使って、アラートの一部を表示してから、マッチするすべてのアラートをクローズされたものとしてマークできます。 あるブランチでは解決されたアラートが、別のブランチでは解決されていないことがあります。 アラートの概要で [Branch] ドロップダウンメニューを使用し、特定のブランチでアラートが解決されたかどうか確認できます。 -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ![ブランチによるアラートのフィルタリング](/assets/images/help/repository/code-scanning-branch-filter.png) {% else %} ![ブランチによるアラートのフィルタリング](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png) @@ -185,9 +198,9 @@ The benefit of using keyword filters is that only values with results are shown ![アラートの削除](/assets/images/help/repository/code-scanning-delete-alerts.png) - あるいは{% ifversion fpt or ghes > 3.1 %}自由テキスト検索もしくは{% endif %}フィルタを使ってアラートの一部を表示させ、マッチするすべてのアラートを一度に削除することができます。 たとえば、クエリを{% data variables.product.prodname_codeql %}分析から削除したら、"Rule"フィルタを使ってそのクエリに対するアラートだけをリストして、それらのアラートをすべて選択して削除できます。 + あるいは{% ifversion fpt or ghes > 3.1 or ghae-next %}自由テキスト検索もしくは{% endif %}フィルタを使ってアラートの一部を表示させ、マッチするすべてのアラートを一度に削除することができます。 たとえば、クエリを{% data variables.product.prodname_codeql %}分析から削除したら、"Rule"フィルタを使ってそのクエリに対するアラートだけをリストして、それらのアラートをすべて選択して削除できます。 -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ![ルールによるアラートのフィルタリング](/assets/images/help/repository/code-scanning-filter-by-rule.png) {% else %} ![ルールによるアラートのフィルタリング](/assets/images/enterprise/3.1/help/repository/code-scanning-filter-by-rule.png) @@ -195,12 +208,11 @@ The benefit of using keyword filters is that only values with results are shown 1. アラートを却下したい場合、そのアラートをまず調べて、却下する正しい理由を選択できるようにすることが重要です。 調べたいアラートをクリックしてください。 -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ![サマリリストからのアラートのオープン](/assets/images/help/repository/code-scanning-click-alert.png) {% else %} ![{% data variables.product.prodname_code_scanning %}からのアラートのリスト](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) {% endif %} - 1. アラートをレビューして、**Dismiss（却下）**をクリックし、アラートをクローズする理由を選択してください。 ![アラートを却下する理由の選択](/assets/images/help/repository/code-scanning-alert-close-drop-down.png) {% data reusables.code-scanning.choose-alert-dismissal-reason %} 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 eed714ffa2..e7d82746ab 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 @@ -40,8 +40,8 @@ topics: {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} -3. ”{% data variables.product.prodname_code_scanning_capc %} alerts"の右で、**Set up {% data variables.product.prodname_code_scanning %}**をクリックしてください。 {% ifversion fpt or ghes > 3.0 %}{% data variables.product.prodname_code_scanning %}がない場合は、Organizationのオーナーもしくはリポジトリの管理者に{% data variables.product.prodname_GH_advanced_security %}を有効化してもらうよう頼まなければなりません。 詳しい情報については、「[Organization のセキュリティおよび分析設定を管理する](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」または「[リポジトリのセキュリティと分析設定を管理する](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)」を参照してください。{% endif %} ![セキュリティの概要にある、[{% data variables.product.prodname_code_scanning_capc %}] の右側の [{% data variables.product.prodname_code_scanning %}] ボタン](/assets/images/help/security/overview-set-up-code-scanning.png) -4. [Get started with {% data variables.product.prodname_code_scanning %}] で、{% data variables.product.prodname_codeql_workflow %} またはサードパーティーのワークフローの [**Set up this workflow**] をクリックします。 !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png){% ifversion fpt or ghes > 2.22 %}ワークフローは、リポジトリで検索されたプログラミング言語に関連がある場合にのみ表示されます。 {% data variables.product.prodname_codeql_workflow %}は常に表示されますが、"Set up this workflow（このワークフローをセットアップ）"ボタンは{% data variables.product.prodname_codeql %}分析がリポジトリ内にある言語をサポートしている場合にのみ有効になります。{% endif %} +3. ”{% data variables.product.prodname_code_scanning_capc %} alerts"の右で、**Set up {% data variables.product.prodname_code_scanning %}**をクリックしてください。 {% ifversion fpt or ghes > 3.0 or ghae-next %}{% data variables.product.prodname_code_scanning %}がない場合は、Organizationのオーナーもしくはリポジトリの管理者に{% data variables.product.prodname_GH_advanced_security %}を有効化してもらうよう頼まなければなりません。 詳しい情報については、「[Organization のセキュリティおよび分析設定を管理する](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」または「[リポジトリのセキュリティと分析設定を管理する](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)」を参照してください。{% endif %} ![セキュリティの概要にある、[{% data variables.product.prodname_code_scanning_capc %}] の右側の [{% data variables.product.prodname_code_scanning %}] ボタン](/assets/images/help/security/overview-set-up-code-scanning.png) +4. [Get started with {% data variables.product.prodname_code_scanning %}] で、{% data variables.product.prodname_codeql_workflow %} またはサードパーティーのワークフローの [**Set up this workflow**] をクリックします。 !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png){% ifversion fpt or ghes > 2.22 or ghae-next %}ワークフローは、リポジトリで検索されたプログラミング言語に関連がある場合にのみ表示されます。 {% data variables.product.prodname_codeql_workflow %}は常に表示されますが、"Set up this workflow（このワークフローをセットアップ）"ボタンは{% data variables.product.prodname_codeql %}分析がリポジトリ内にある言語をサポートしている場合にのみ有効になります。{% endif %} 5. {% data variables.product.prodname_code_scanning %} がコードをスキャンする方法をカスタマイズするため、ワークフローを編集します。 通常は、何も変更せずに {% data variables.product.prodname_codeql_workflow %} をコミットできます。 ただし、サードパーティのワークフローは、その多くで追加設定が必要なため、コミットする前にワークフローのコメントをお読みください。 @@ -53,10 +53,43 @@ topics: デフォルトの {% data variables.product.prodname_codeql_workflow %} では、{% data variables.product.prodname_code_scanning %} は、デフォルトブランチまたは保護されたブランチに変更をプッシュするたび、あるいはデフォルトブランチにプルリクエストを生成するたびに、コードを解析するよう設定されています。 その結果として、{% data variables.product.prodname_code_scanning %} が開始されます。 +The `on:pull_request` and `on:push` triggers for code scanning are each useful for different purposes. For more information, see "[Scanning pull requests](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-pull-requests)" and "[Scanning on push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)." ## {% data variables.product.prodname_code_scanning %} の一括セットアップ スクリプトを使用して、{% data variables.product.prodname_code_scanning %} を多くのリポジトリで一括でセットアップできます。 If you'd like to use a script to raise pull requests that add a {% data variables.product.prodname_actions %} workflow to multiple repositories, see the [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) repository for an example using Powershell, or [`nickliffen/ghas-enablement`](https://github.com/NickLiffen/ghas-enablement) for teams who do not have Powershell and instead would like to use NodeJS. +## {% data variables.product.prodname_code_scanning %} からログ出力を表示する + +リポジトリで{% data variables.product.prodname_code_scanning %}をセットアップしたら、アクションが実行されるとその出力を見ることができます。 + +{% data reusables.repositories.actions-tab %} + + {% data variables.product.prodname_code_scanning %} ワークフローを実行するためのエントリを含むリストが表示されます。 エントリのテキストは、コミットメッセージに付けるタイトルです。 + + ![{% data variables.product.prodname_code_scanning %} ワークフローを表示しているアクションのリスト](/assets/images/help/repository/code-scanning-actions-list.png) + +1. {% data variables.product.prodname_code_scanning %} ワークフローのエントリをクリックします。 + +1. 左側のジョブ名をクリックします。 ここでは例として、[**Analyze (言語)**] をクリックします。 + + ![{% data variables.product.prodname_code_scanning %} ワークフローからのログ出力](/assets/images/help/repository/code-scanning-logging-analyze-action.png) + +1. このワークフローの実行時にアクションから出力されるログを確認します。 + +1. すべてのジョブが完了すると、確認されたすべての {% data variables.product.prodname_code_scanning %} アラートの詳細を表示できます。 詳しい情報については、「[リポジトリの {% data variables.product.prodname_code_scanning %} アラートを管理する](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)」を参照してください。 + +{% note %} + +**注釈:** {% data variables.product.prodname_code_scanning %} ワークフローを追加するためのプルリクエストをリポジトリに発行すると、そのプルリクエストからのアラートは、そのプルリクエストがマージされるまで {% data variables.product.prodname_code_scanning_capc %} ページに直接表示されません。 アラートが見つかった場合は、プルリクエストがマージされる前に、{% data variables.product.prodname_code_scanning_capc %} ページのバナーにある [**_(数字)_ alerts found**] をクリックしてそのアラートを表示できます。 + +{% ifversion fpt or ghes > 3.1 or ghae-next %} + ![[n alerts found] のリンクをクリック](/assets/images/help/repository/code-scanning-alerts-found-link.png) +{% else %} + ![[n alerts found] のリンクをクリック](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png) +{% endif %} + +{% endnote %} + ## プルリクエストのチェックを理解する Pull Requestで実行するよう設定した各 {% data variables.product.prodname_code_scanning %} ワークフローでは、Pull Requestのチェックセクションに常に最低 2 つのエントリが表示されています。 ワークフローの解析ジョブごとに 1 つのエントリがあり、最後のエントリは解析結果です。 @@ -66,13 +99,25 @@ Pull Requestで実行するよう設定した各 {% data variables.product.prodn ![{% data variables.product.prodname_code_scanning %} プルリクエストのチェック](/assets/images/help/repository/code-scanning-pr-checks.png) {% data variables.product.prodname_code_scanning %} ジョブが完了すると、 -{% data variables.product.prodname_dotcom %} はプルリクエストにより追加されたアラートがないか確認し、チェックのリストに「{% data variables.product.prodname_code_scanning_capc %} の結果 / ツール名」のエントリを追加します。 {% data variables.product.prodname_code_scanning %} が 1 回でも実行された後は、[**Details**] をクリックして解析結果を表示できます。 プルリクエストを使用してリポジトリに {% data variables.product.prodname_code_scanning %} を追加した場合、「{% data variables.product.prodname_code_scanning_capc %} 結果 / ツール名」チェックの [**Details**] をクリックすると最初は「Missing analysis」のメッセージが表示されます。 +{% data variables.product.prodname_dotcom %} はプルリクエストにより追加されたアラートがないか確認し、チェックのリストに「{% data variables.product.prodname_code_scanning_capc %} の結果 / ツール名」のエントリを追加します。 {% data variables.product.prodname_code_scanning %} が 1 回でも実行された後は、[**Details**] をクリックして解析結果を表示できます。 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 %}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. - ![コミットメッセージの解析がありません](/assets/images/help/repository/code-scanning-missing-analysis.png) +{% ifversion fpt or ghes > 3.2 or ghae-issue-3891 %} + ![Analysis not found for commit message](/assets/images/help/repository/code-scanning-analysis-not-found.png) -### 「missing analysis」のメッセージが出る理由 +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. -プルリクエストのコードを解析した後、{% data variables.product.prodname_code_scanning %} はトピックブランチ (プルリクエストを作成するために使用したブランチ) の解析と、ベースブランチ (プルリクエストをマージするブランチ) の解析を比較する必要があります。 これにより、{% data variables.product.prodname_code_scanning %} はプルリクエストにより新しく発生したアラートはどれか、ベースブランチに既に存在していたアラートはどれか、また既存のアラートがプルリクエストの変更により修正されたかを測定できます。 始めにプルリクエストを使用してリポジトリに {% data variables.product.prodname_code_scanning %} を追加した段階では、ベースブランチはまだ解析されていないので、こうした情報を測定できません。 この場合、プルリクエストの結果チェックをくりっくすると、「Missing analysis for base commit SHA-HASH (ベースコミット SHA-HASH の解析がありません)」というメッセージが表示されます。 +For example, in the screenshot above, {% data variables.product.prodname_code_scanning %} found an analysis for the merge commit of the pull request, but no analysis for the head of the main branch. +{% else %} + ![コミットメッセージの解析がありません](/assets/images/enterprise/3.2/repository/code-scanning-missing-analysis.png) +{% endif %} + +{% ifversion fpt or ghes > 3.2 or ghae-issue-3891 %} +### Reasons for the "Analysis not found" message +{% else %} +### Reasons for the "Missing analysis" message +{% endif %} + +プルリクエストのコードを解析した後、{% data variables.product.prodname_code_scanning %} はトピックブランチ (プルリクエストを作成するために使用したブランチ) の解析と、ベースブランチ (プルリクエストをマージするブランチ) の解析を比較する必要があります。 これにより、{% data variables.product.prodname_code_scanning %} はプルリクエストにより新しく発生したアラートはどれか、ベースブランチに既に存在していたアラートはどれか、また既存のアラートがプルリクエストの変更により修正されたかを測定できます。 始めにプルリクエストを使用してリポジトリに {% data variables.product.prodname_code_scanning %} を追加した段階では、ベースブランチはまだ解析されていないので、こうした情報を測定できません。 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 %}"Analysis not found"{% else %}"Missing analysis for base commit SHA-HASH"{% endif %} message. この他にも、プルリクエストのベースブランチに対する直近のコミットで解析結果がないことがあります。 たとえば、次のような場合です。 @@ -80,7 +125,7 @@ Pull Requestで実行するよう設定した各 {% data variables.product.prodn ブランチがスキャン済みかを確認するには、{% data variables.product.prodname_code_scanning_capc %} ページに移動し、[**Branch**] ドロップダウンをクリックして該当するブランチを選択します。 -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ![[Branch] ドロップダウンメニューからブランチを選択](/assets/images/help/repository/code-scanning-branch-dropdown.png) {% else %} ![[Branch] ドロップダウンメニューからブランチを選択](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-dropdown.png) 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 12575af1f0..8d4c0b465b 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,6 +28,9 @@ 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**] タブでアノテーションとしても表示されます。 リポジトリへの書き込み権限がある場合、既存のすべての {% data variables.product.prodname_code_scanning %} アラートを [**Security**] タブで表示できます。 リポジトリのアラートに関する詳しい情報については、「[リポジトリの {% 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 %} +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 %} If your pull request targets a protected branch that uses {% data variables.product.prodname_code_scanning %}, and the repository owner has configured required status checks, then the "{% data variables.product.prodname_code_scanning_capc %} results" check must pass before you can merge the pull request. 詳しい情報については[保護されたブランチについて](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)を参照してください。 diff --git a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md index b59f981c2d..93b251240d 100644 --- a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md +++ b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md @@ -22,7 +22,7 @@ shortTitle: Code scanningログの表示 リポジトリでの{% data variables.product.prodname_code_scanning %}のセットアップには、様々なツールを使うことができます。 詳しい情報については「[リポジトリに対する{% data variables.product.prodname_code_scanning %}のセットアップ](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#options-for-setting-up-code-scanning)」を参照してください。 -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} 利用できるログと診断情報は、リポジトリ中での{% data variables.product.prodname_code_scanning %}の利用方法によります。 使用している{% data variables.product.prodname_code_scanning %}の種類は、リポジトリの**Security（セキュリティ）**タブで、アラートリスト中の**Tool（ツール）**ドロップダウンメニューを使ってチェックできます。 詳しい情報については、「[リポジトリの {% data variables.product.prodname_code_scanning %} アラートを管理する](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)」を参照してください。 ## 分析と診断情報について @@ -35,7 +35,7 @@ shortTitle: Code scanningログの表示 {% data variables.product.prodname_dotcom %}の外部で{% data variables.product.prodname_codeql_cli %}を使っているなら、診断情報はデータベース分析の間に生成された出力中に示されます。 この情報は、{% data variables.product.prodname_code_scanning %}の結果とともに{% data variables.product.prodname_dotcom %}にアップロードするSARIF結果ファイル中にも含まれています。 -{% data variables.product.prodname_codeql_cli %}に関する情報については「[CIシステムでの{% data variables.product.prodname_codeql_cli %}の実行](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-cli-in-your-ci-system#viewing-log-and-diagnostic-information)」を参照してください。 +For information about the {% data variables.product.prodname_codeql_cli %}, see "[Configuring {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system#viewing-log-and-diagnostic-information)." ### サマリメトリクスについて @@ -72,7 +72,7 @@ shortTitle: Code scanningログの表示 **注釈:** {% data variables.product.prodname_code_scanning %} ワークフローを追加するためのプルリクエストをリポジトリに発行すると、そのプルリクエストからのアラートは、そのプルリクエストがマージされるまで {% data variables.product.prodname_code_scanning_capc %} ページに直接表示されません。 アラートが見つかった場合は、プルリクエストがマージされる前に、{% data variables.product.prodname_code_scanning_capc %} ページのバナーにある [**_(数字)_ alerts found**] をクリックしてそのアラートを表示できます。 -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae %} ![[n alerts found] のリンクをクリック](/assets/images/help/repository/code-scanning-alerts-found-link.png) {% else %} ![[n alerts found] のリンクをクリック](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png) diff --git a/translations/ja-JP/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md b/translations/ja-JP/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md index 0227968b9f..275889549d 100644 --- a/translations/ja-JP/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md +++ b/translations/ja-JP/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md @@ -37,7 +37,7 @@ SARIF ファイルに `partialFingerprints` が含まれていない場合、{% {% ifversion fpt or ghes > 3.0 or ghae-next %} {% data variables.product.prodname_codeql_cli %}を使っているなら、使用するSARIFのバージョンを指定できます。 詳しい情報については「[CIシステムでの{% data variables.product.prodname_codeql_cli %}の設定](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system#analyzing-a-codeql-database)」を参照してください。{% endif %} -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} 同じツールとコミットに対して複数のSARIFファイルをアップロードして、それぞれのファイルを{% data variables.product.prodname_code_scanning %}を使って分析できます。 それぞれのファイル中で`runAutomationDetails.id`を指定することによって、それぞれの分析に対して「カテゴリ」を示すことができます。 同じカテゴリのSARIFファイル同士だけがお互いを上書きします。 このプロパティに関する詳しい情報については、以下の[`runAutomationDetails` object](#runautomationdetails-object)を参照してください。 {% endif %} @@ -141,7 +141,7 @@ SARIF ファイルが {% data variables.product.prodname_code_scanning %} と互 | `region.endLine` | **必須。**リージョンの最後の文字の行番号。 | | `region.endColumn` | **必須。**リージョンの末尾に続く文字の列番号。 | -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ### `runAutomationDetails`オブジェクト `runAutomationDetails`オブジェクトには、実行のアイデンティティを指定する情報が含まれています。 @@ -245,7 +245,7 @@ SARIF ファイルが {% data variables.product.prodname_code_scanning %} と互 次の SARIF 出力ファイルには、{% data variables.product.prodname_code_scanning %} でサポートされているすべての SARIF プロパティを示す値の例が示されています。 -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ```json { "$schema": "https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json", diff --git a/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md index 1df50ad089..33838cd174 100644 --- a/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md +++ b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md @@ -91,8 +91,8 @@ redirect_from: {% endif %} - -{% ifversion ghes = 3.0 or ghae %} + +{% ifversion ghes = 3.0 %} {% data reusables.code-scanning.upload-sarif-ghas %} {% data variables.product.prodname_codeql_runner %}をサードパーティのシステムに追加して、コードを分析するツールを呼び、SARIFの結果を{% data variables.product.product_name %}にアップロードしてください。 結果の{% data variables.product.prodname_code_scanning %}アラートは、{% data variables.product.product_name %}内で生成されたアラートとともに表示されます。 diff --git a/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md index 036df4ba4d..f82abf518b 100644 --- a/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md +++ b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md @@ -30,7 +30,7 @@ CIシステム内のサーバーで{% data variables.product.prodname_codeql_cli 結果を生成して{% data variables.product.product_name %}にアップロードするには、3つの異なるコマンドを使います。 -{% ifversion fpt or ghes > 3.1 or ghae-next %} +{% ifversion fpt or ghes > 3.1 or ghae %} 1. `database create`で、リポジトリ中のサポートされている各プログラミング言語の階層構造を表す{% data variables.product.prodname_codeql %}データベースを作成してください。 2. `database analyze`でクエリを実行し、各{% data variables.product.prodname_codeql %}データベースを分析し、結果をSARIFファイルにまとめてください。 @@ -50,11 +50,11 @@ CIシステム内のサーバーで{% data variables.product.prodname_codeql_cli 1. 分析したいコードをチェックアウトしてください: - ブランチの場合は、分析したいブランチのheadをチェックアウトしてください。 - - Pull Requestの場合は、Pull Requestのheadコミットをチェックアウトするか、{% data variables.product.product_name %}が生成したPull Requestのマージコミットをチェックアウトしてください。 + - Pull Requestの場合は、Pull Requestのheadコミットをチェックアウトするか、{% data variables.product.prodname_dotcom %}が生成したPull Requestのマージコミットをチェックアウトしてください。 2. コードベースの環境をセットアップし、すべての依存関係が利用できるようにしてください。 詳しい情報については、{% data variables.product.prodname_codeql_cli %}のドキュメンテーション中の[非コンパイル言語のデータベースの作成](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#creating-databases-for-non-compiled-languages)及び[コンパイル言語のデータベースの作成](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#creating-databases-for-compiled-languages)を参照してください。 3. コードベースのビルドコマンドがあれば、それを見つけてください。 通常これはCIシステムの設定ファイルにあります。 4. リポジトリのチェックアウトのルートから`codeql database create`を実行し、コードベースをビルドしてください。 - {% ifversion fpt or ghes > 3.1 or ghae-next %} + {% ifversion fpt or ghes > 3.1 or ghae %} ```shell # 単一のサポートされている言語 - 1つのCodeQLデータベースを作成 codeql database create <database> --command<build> --language=<language-identifier> @@ -119,7 +119,7 @@ CIシステム内のサーバーで{% data variables.product.prodname_codeql_cli - {% ifversion fpt or ghes > 3.1 or ghae-next %}     `--db-cluster`とともに使われると、このオプションはカンマ区切りのリストを取るか、複数回指定できます。{% endif %} + {% ifversion fpt or ghes > 3.1 or ghae %} `--db-cluster`とともに使われると、このオプションはカンマ区切りのリストを取るか、複数回指定できます。{% endif %} @@ -144,7 +144,7 @@ CIシステム内のサーバーで{% data variables.product.prodname_codeql_cli - {% ifversion fpt or ghes > 3.1 or ghae-next %} + {% ifversion fpt or ghes > 3.1 or ghae %} @@ -208,7 +208,7 @@ CIシステム内のサーバーで{% data variables.product.prodname_codeql_cli 詳しい情報については{% data variables.product.prodname_codeql_cli %}のドキュメンテーション中の[{% data variables.product.prodname_codeql %}データベースの作成](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/)を参照してください。 -### {% ifversion fpt or ghes > 3.1 or ghae-next %}単一言語の例{% else %}基本の例{% endif %} +### {% ifversion fpt or ghes > 3.1 or ghae %}単一言語の例{% else %}基本の例{% endif %} この例は、`/checkouts/example-repo`にチェックアウトされたリポジトリの{% data variables.product.prodname_codeql %}データベースを作成します。 これはJavaScript extractorを使い、リポジトリ中のJavaScriptとTypeScriptコードの階層表現を作成します。 結果のデータベースは`/codeql-dbs/example-repo`に保存されます。 @@ -226,7 +226,7 @@ $ codeql database create /codeql-dbs/example-repo --language=javascript \ > Successfully created database at /codeql-dbs/example-repo. ``` -{% ifversion fpt or ghes > 3.1 or ghae-next %} +{% ifversion fpt or ghes > 3.1 or ghae %} ### 複数言語の例 この例は、`/checkouts/example-repo-multi`にチェックアウトされたリポジトリの2つの{% data variables.product.prodname_codeql %}データベースを作成します。 これは以下を使用します。 @@ -273,7 +273,7 @@ $ --output=<output> {% if codeql-packs %}<packs,queries>{% else %} <queries>{% endif %} ``` -{% ifversion fpt or ghes > 3.1 or ghae-next %} +{% ifversion fpt or ghes > 3.1 or ghae %} {% note %} **ノート:** 1つのコミットに対して複数の{% data variables.product.prodname_codeql %}データベースを分析する場合、このコマンドが生成するそれぞれの結果セットに対してSARIFカテゴリを指定しなければなりません。 結果を{% data variables.product.product_name %}にアップロードする際には、{% data variables.product.prodname_code_scanning %}はこのカテゴリを使ってそれぞれの言語に対する結果を別々に保存します。 これを忘れると、それぞれのアップロードが以前の結果を上書きしてしまいます。 @@ -317,15 +317,14 @@ codeql database analyze <database> --format=<format> \ - <queries> + <packs,queries> - {% octicon "check-circle-fill" aria-label="Required" %} - 実行するクエリを指定します。 {% data variables.product.prodname_code_scanning %}で使われる標準のクエリを実行するには、<language>-code-scanning.qlsを使ってください。ここで<language>はデータベースの言語の短いコードです。 {% data variables.product.prodname_codeql_cli %}バンドル内に含まれている他のクエリスイートを見るには、/<extraction-root>/codeql/qlpacks/codeql-<language>/codeql-suitesを見てください。 独自のクエリスイートの作成に関する情報については、{% data variables.product.prodname_codeql_cli %}のドキュメンテーション中のCodeQLクエリスイートの作成を参照してください。 + Specify {% data variables.product.prodname_codeql %} packs or queries to run. To run the standard queries used for {% data variables.product.prodname_code_scanning %}, omit this parameter. {% data variables.product.prodname_codeql_cli %}バンドル内に含まれている他のクエリスイートを見るには、/<extraction-root>/codeql/qlpacks/codeql-<language>/codeql-suitesを見てください。 独自のクエリスイートの作成に関する情報については、{% data variables.product.prodname_codeql_cli %}のドキュメンテーション中のCodeQLクエリスイートの作成を参照してください。 @@ -353,7 +352,7 @@ codeql database analyze <database> --format=<format> \ - SARIF結果ファイルを保存する場所を指定します。{% ifversion fpt or ghes > 3.1 or ghae-next %} + SARIF結果ファイルを保存する場所を指定します。{% ifversion fpt or ghes > 3.1 or ghae %} @@ -406,7 +405,7 @@ codeql database analyze <database> --format=<format> \ - オプション。 分析のプロセス{% ifversion fpt or ghes > 3.1 or ghae-next %}とデータベース作成プロセスからの診断データ{% endif %}に関する詳細な情報を得るために使用します。 + オプション。 分析のプロセス{% ifversion fpt or ghes > 3.1 or ghae %}とデータベース作成プロセスからの診断データ{% endif %}に関する詳細な情報を得るために使用します。 @@ -415,11 +414,11 @@ codeql database analyze <database> --format=<format> \ ### 基本的な例 -この例は`/codeql-dbs/example-repo`に保存された{% data variables.product.prodname_codeql %}データベースを分析し、結果を`/temp/example-repo-js.sarif`というSARIFファイルに保存します。 {% ifversion fpt or ghes > 3.1 or ghae-next %}ここでは`--sarif-category`を使って結果をJavaScriptとして識別する追加情報をSARIFファイルに含めます。 これは、リポジトリ中の単一のコミットに対して分析する{% data variables.product.prodname_codeql %}データベースが複数ある場合に不可欠です。{% endif %} +この例は`/codeql-dbs/example-repo`に保存された{% data variables.product.prodname_codeql %}データベースを分析し、結果を`/temp/example-repo-js.sarif`というSARIFファイルに保存します。 {% ifversion fpt or ghes > 3.1 or ghae %}ここでは`--sarif-category`を使って結果をJavaScriptとして識別する追加情報をSARIFファイルに含めます。 これは、リポジトリ中の単一のコミットに対して分析する{% data variables.product.prodname_codeql %}データベースが複数ある場合に不可欠です。{% endif %} ``` $ codeql database analyze /codeql-dbs/example-repo \ - javascript-code-scanning.qls {% ifversion fpt or ghes > 3.1 or ghae-next %}--sarif-category=javascript{% endif %} + javascript-code-scanning.qls {% ifversion fpt or ghes > 3.1 or ghae %}--sarif-category=javascript{% endif %} --format={% ifversion fpt or ghae %}sarif-latest{% else %}sarifv2.1.0{% endif %} --output=/temp/example-repo-js.sarif > Running queries. @@ -444,7 +443,7 @@ $ codeql database analyze /codeql-dbs/example-repo \ ```shell echo "$UPLOAD_TOKEN" | codeql github upload-results --repository=<repository-name> \ --ref=<ref> --commit=<commit> --sarif=<file> \ - {% ifversion ghes > 3.0 or ghae-next %}--github-url=<URL> {% endif %}--github-auth-stdin + {% ifversion ghes > 3.0 or ghae %}--github-url=<URL> {% endif %}--github-auth-stdin ``` @@ -486,7 +485,7 @@ $ codeql database analyze /codeql-dbs/example-repo \ @@ -514,7 +513,7 @@ $ codeql database analyze /codeql-dbs/example-repo \ @@ -555,7 +554,7 @@ $ codeql database analyze /codeql-dbs/example-repo \ ``` $ echo $UPLOAD_TOKEN | codeql github upload-results --repository=my-org/example-repo \ --ref=refs/heads/main --commit=deb275d2d5fe9a522a0b7bd8b6b6a1c939552718 \ - --sarif=/temp/example-repo-js.sarif {% ifversion ghes > 3.0 or ghae-next %}--github-url={% data variables.command_line.git_url_example %} \ + --sarif=/temp/example-repo-js.sarif {% ifversion ghes > 3.0 or ghae %}--github-url={% data variables.command_line.git_url_example %} \ {% endif %}--github-auth-stdin ``` @@ -641,6 +640,7 @@ $ codeql database analyze /codeql-dbs/example-repo octo-org/security-queries \ {% endif %} {% ifversion fpt or ghes > 3.1 or ghae-next %} + ## {% data variables.product.prodname_codeql %}分析のためのCIの設定例 これは、2つのサポートされている言語を持つコードベースを分析し、結果を{% data variables.product.product_name %}にアップロードするために使うことができる一連のコマンドの例です。 diff --git a/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md index 7681717fe9..e0cf512a22 100644 --- a/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md +++ b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md @@ -191,7 +191,7 @@ $ /path/to-runner/codeql-runner-linux autobuild --language csharp | `--no-upload` | | なし. {% data variables.product.prodname_codeql_runner %} が結果を {% data variables.product.product_name %} にアップロードすることを停止します。 | | `--output-dir` | | 出力される SARIF ファイルが保存されるディレクトリ。 デフォルトは一時ファイルのディレクトリです。 | | `--ram` | | クエリの実行時に使用するメモリの量。 デフォルトでは、使用できるすべてのメモリを使用します。 | -| `--no-add-snippets` | | なし. SARIF 出力からコードスニペットを除外します。 |{% ifversion fpt or ghes > 3.1 %} +| `--no-add-snippets` | | なし. SARIF 出力からコードスニペットを除外します。 |{% ifversion fpt or ghes > 3.1 or ghae %} | `--category` | | この分析でSARIF結果ファイルに含めるカテゴリ。 カテゴリは、同じツールとコミットについて、ただし様々な言語やコードの様々な部分に対して行われる複数の分析を区別するために使うことができます。 この値は、SARIF v2.1.0では`.automationDetails.id`プロパティに現れます。 {% endif %} | `--threads` | | クエリの実行時に使用するスレッドの数。 デフォルトでは、使用できるすべてのコアを使用します。 | 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 4570a1fbda..71630210fa 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 @@ -25,7 +25,7 @@ topics: {% data variables.product.company_short %}は、{% ifversion fpt %}パブリック及びプライベート{% endif %}リポジトリ上で{% data variables.product.company_short %}及び{% data variables.product.company_short %}パートナーが提供するシークレットのパターンの{% data variables.product.prodname_secret_scanning %}を行います。 {% data variables.product.prodname_secret_scanning %}パートナープログラムに関する詳しい情報については「Secret scanningパートナープログラム」を参照してください。 -ただし、{% ifversion fpt %}プライベート{% endif %}リポジトリ中で他のシークレットのパターンをスキャンしたいこともあるでしょう。 たとえば、Organizationの内部的なシークレットのパターンを持っていることもあるかもしれません。 For these situations, you can define custom {% data variables.product.prodname_secret_scanning %} patterns in your enterprise, organization, or {% ifversion fpt %}private{% endif %} repository on {% data variables.product.product_name %}. You can define up to 20 custom patterns for each {% ifversion fpt %}private{% endif %} repository, organization, or enterprise account. +ただし、{% ifversion fpt %}プライベート{% endif %}リポジトリ中で他のシークレットのパターンをスキャンしたいこともあるでしょう。 たとえば、Organizationの内部的なシークレットのパターンを持っていることもあるかもしれません。 For these situations, you can define custom {% data variables.product.prodname_secret_scanning %} patterns in your enterprise, organization, or {% ifversion fpt %}private{% endif %} repository on {% data variables.product.product_name %}. You can define up to 100 custom patterns for each organization or enterprise account, and up to 20 custom patterns per {% ifversion fpt %}private{% endif %} repository. {% ifversion ghes < 3.3 or ghae %} {% note %} diff --git a/translations/ja-JP/content/code-security/security-advisories/publishing-a-security-advisory.md b/translations/ja-JP/content/code-security/security-advisories/publishing-a-security-advisory.md index af0fa825b0..7a1bb821c7 100644 --- a/translations/ja-JP/content/code-security/security-advisories/publishing-a-security-advisory.md +++ b/translations/ja-JP/content/code-security/security-advisories/publishing-a-security-advisory.md @@ -61,19 +61,6 @@ shortTitle: アドバイザリの公開 公開したセキュリティアドバイザリの情報をアップデートまたは修正する必要がある場合は、セキュリティアドバイザリを編集できます。 詳しい情報については、「[セキュリティアドバイザリを編集する](/github/managing-security-vulnerabilities/editing-a-security-advisory)」を参照してください。 -## CVE 識別番号をリクエストする - -セキュリティアドバイザリの管理者権限を持っているすべてのユーザは、セキュリティアドバイザリの CVE 識別番号をリクエストできます。 - -{% data reusables.repositories.request-security-advisory-cve-id %} 詳しい情報については、「[{% data variables.product.prodname_security_advisories %} について](/github/managing-security-vulnerabilities/about-github-security-advisories#cve-identification-numbers)」を参照してください。 - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-security %} -{% data reusables.repositories.sidebar-advisories %} -4. [Security Advisories] のリストから、CVE 識別番号をリクエストするセキュリティアドバイザリをクリックします。 ![リスト内のセキュリティアドバイザリ](/assets/images/help/security/security-advisory-in-list.png) -5. [**Edit**] ドロップダウンメニューを使用して、[**Request CVE**] をクリックします。 ![ドロップダウンの [Request CVE]](/assets/images/help/security/security-advisory-drop-down-request-cve.png) -6. [**Request CVE**] をクリックします。 ![[Request CVE] ボタン](/assets/images/help/security/security-advisory-request-cve-button.png) - ## セキュリティアドバイザリを公開する セキュリティアドバイザリを公開すると、セキュリティアドバイザリの一時的なプライベートフォークが削除されます。 @@ -88,6 +75,17 @@ shortTitle: アドバイザリの公開 {% data reusables.repositories.github-reviews-security-advisories %} +## Requesting a CVE identification number (Optional) + +{% data reusables.repositories.request-security-advisory-cve-id %} 詳しい情報については、「[{% data variables.product.prodname_security_advisories %} について](/github/managing-security-vulnerabilities/about-github-security-advisories#cve-identification-numbers)」を参照してください。 + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-security %} +{% data reusables.repositories.sidebar-advisories %} +4. [Security Advisories] のリストから、CVE 識別番号をリクエストするセキュリティアドバイザリをクリックします。 ![リスト内のセキュリティアドバイザリ](/assets/images/help/security/security-advisory-in-list.png) +5. [**Edit**] ドロップダウンメニューを使用して、[**Request CVE**] をクリックします。 ![ドロップダウンの [Request CVE]](/assets/images/help/security/security-advisory-drop-down-request-cve.png) +6. [**Request CVE**] をクリックします。 ![[Request CVE] ボタン](/assets/images/help/security/security-advisory-request-cve-button.png) + ## 参考リンク - 「[セキュリティアドバイザリを撤回する](/github/managing-security-vulnerabilities/withdrawing-a-security-advisory)」 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 5e900254d9..f088f86e44 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 @@ -6,8 +6,8 @@ redirect_from: - /code-security/security-overview/exploring-security-alerts versions: fpt: '*' + ghae: issue-4554 ghes: '>3.1' - ghae: next type: how_to topics: - Security overview 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 11fe39cf6a..b34061e771 100644 --- a/translations/ja-JP/content/code-security/security-overview/index.md +++ b/translations/ja-JP/content/code-security/security-overview/index.md @@ -5,8 +5,8 @@ intro: 一カ所でOrganization内のセキュリティアラートを表示、 product: '{% data reusables.gated-features.security-center %}' versions: fpt: '*' + ghae: issue-4554 ghes: '>3.1' - ghae: next topics: - Security overview - Advanced Security 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 22f5491e78..390c63f7a0 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 @@ -1,11 +1,11 @@ --- title: 依存関係のレビューについて intro: 依存関係のレビューは、脆弱性のある依存関係を自分の環境に持ち込んでしまう前に捉え、ライセンス、依存物、依存関係の期間に関する情報を提供します。 +product: '{% data reusables.gated-features.dependency-review %}' shortTitle: 依存関係のレビュー versions: fpt: '*' ghes: '>= 3.2' - product: '{% data reusables.gated-features.dependency-review %}' type: overview topics: - Advanced Security diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/index.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/index.md index 8cbbd32ce1..6e330e1f22 100644 --- a/translations/ja-JP/content/codespaces/developing-in-codespaces/index.md +++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/index.md @@ -15,6 +15,5 @@ children: - /forwarding-ports-in-your-codespace - /changing-the-machine-type-for-your-codespace - /using-codespaces-in-visual-studio-code - - /web-based-editor --- 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 15b77cc04f..897de641f5 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 @@ -30,9 +30,7 @@ shortTitle: ソースコントロール ## ブランチの作成または切り替え -1. 現在のブランチがステータスバーに表示されていない場合は、codespace の下部でステータスバーを右クリックし、[**Source control**] を選択します。 -1. ステータスバーでブランチ名をクリックします。 ![ステータスバーにあるブランチ](/assets/images/help/codespaces/branch-in-status-bar.png) -1. ドロップダウンで、切り替えるブランチをクリックするか、新しいブランチ名を入力して [**Create new branch**] をクリックします。 ![ブランチメニューから選択](/assets/images/help/codespaces/create-new-branch.png) +{% data reusables.codespaces.create-or-switch-branch %} {% tip %} @@ -64,16 +62,11 @@ If the dev container configuration has been changed since you created the codesp ## 変更をコミットする -{% data reusables.codespaces.source-control-display-dark %} -1. 変更をステージングするには、変更したファイルの隣にある [**+**] をクリックするか、複数のファイルを変更してすべてをステージングする場合は [**Changes**] の隣をクリックします。 ![ステージングボタンが強調表示されたソースコントロールサイドバー](/assets/images/help/codespaces/codespaces-commit-stage.png) -1. 行った変更について説明するコミットメッセージを入力します。 ![コミットメッセージがあるソースコントロールサイドバー](/assets/images/help/codespaces/codespaces-commit-commit-message.png) -1. ステージングされた変更をコミットするには、ソースコントロールサイドバーの上部にあるチェックマークをクリックします。 ![チェックマークアイコンをクリックする](/assets/images/help/codespaces/codespaces-commit-checkmark-icon.png) +{% data reusables.codespaces.source-control-commit-changes %} ## プルリクエストを発行する -1. リポジトリのローカルコピーに変更をコミットしてから、[**Create Pull Request**] アイコンをクリックします。 ![ステージングボタンが強調表示されたソースコントロールサイドバー](/assets/images/help/codespaces/codespaces-commit-pr-button.png) -1. マージ元のローカルブランチとリポジトリ、およびマージ先のリモートブランチとリポジトリが正しいことを確認します。 そして、プルリクエストにタイトルと説明を付けます。 ![ステージングボタンが強調表示されたソースコントロールサイドバー](/assets/images/help/codespaces/codespaces-commit-pr.png) -1. ** Create（作成）**をクリックしてください。 +{% data reusables.codespaces.source-control-pull-request %} ## リモートリポジトリに変更をプッシュする diff --git a/translations/ja-JP/content/codespaces/index.md b/translations/ja-JP/content/codespaces/index.md index 25be1f2cbe..3db10aef65 100644 --- a/translations/ja-JP/content/codespaces/index.md +++ b/translations/ja-JP/content/codespaces/index.md @@ -41,6 +41,7 @@ children: - /managing-codespaces-for-your-organization - /codespaces-reference - /troubleshooting + - /the-githubdev-web-based-editor - /guides --- 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 7e34f802e8..d00cc95232 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 @@ -72,3 +72,7 @@ Organization 内のシークレットに適用されているアクセスポリ {% data reusables.github-actions.sidebar-secret %} 1. シークレットのリストには、設定済みのアクセス許可とポリシーが含まれます。 例: ![シークレットリスト](/assets/images/help/settings/actions-org-secrets-list.png) 1. 各シークレットに設定されているアクセス許可の詳細については、[**Update（更新）**] をクリックしてください。 + +## 参考リンク + +- "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)" diff --git a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md index b6a031e072..f854eb6ce6 100644 --- a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md +++ b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md @@ -26,3 +26,7 @@ Organization 内のどのユーザが {% data variables.product.prodname_codespa {% data reusables.organizations.click-codespaces %} 1. [Access and security] で、あなたの Organization の設定を選択します。 ![信頼するリポジトリを管理するラジオボタン](/assets/images/help/settings/codespaces-org-access-and-security-radio-buttons.png) 1. [Selected repositories] を選択した場合、ドロップダウンメニューを選択してから、あなたの Organization が所有するその他のリポジトリにアクセスを許可する、リポジトリのコードスペースをクリックします。 その他のリポジトリにコードスペースによるアクセスを許可したい、すべてのリポジトリについて同じ手順を繰り返します。 ![[Selected repositories]ドロップダウンメニュー](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) + +## 参考リンク + +- "[Managing repository access for your codespaces](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces)" diff --git a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md index e8dda34c5b..23d9c6155e 100644 --- a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md +++ b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md @@ -19,3 +19,7 @@ Organization のメンバーが {% data variables.product.prodname_codespaces %} ![Codespaces 情報を含む Audit log](/assets/images/help/settings/codespaces-audit-log-org.png) The audit log includes details such as who performed the action, what the action was, and when the action was performed. For information on {% data variables.product.prodname_codespaces %} actions, see "[{% data variables.product.prodname_codespaces %} category actions](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#codespaces-category-actions)." + +## 参考リンク + +- "[Reviewing your security logs for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces)" diff --git a/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md b/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md index 67d754ac44..0b4cfc0520 100644 --- a/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md +++ b/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md @@ -73,3 +73,7 @@ shortTitle: 暗号化されたシークレット {% data reusables.user_settings.codespaces-tab %} 1. [Codespaces secrets] で、削除するシークレットの右にある [**Delete**] をクリックします。 ![[Delete] ボタン](/assets/images/help/settings/codespaces-secret-delete-button.png) 1. 警告を読んで、**OK**をクリックしてください。 ![シークレットの削除の確認](/assets/images/help/settings/codespaces-secret-delete-warning.png) + +## 参考リンク + +- "[Managing encrypted secrets for your repository and organization for {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces)" diff --git a/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md b/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md index 41a65213a9..fea3024797 100644 --- a/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md +++ b/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md @@ -29,6 +29,6 @@ Once you enable GPG verification, it will immediately take effect for all your c {% note %} -**Note:** Once you have enabled GPG verification for {% data variables.product.prodname_codespaces %}, you also must append `-s` to each commit in order for it to be signed. To do this in {% data variables.product.prodname_vscode %}, ensure the "Git: Enable Commit Signing" option is enabled from the Settings. +**Note:** Once you have enabled GPG verification for {% data variables.product.prodname_codespaces %}, you also must append `-S` to each commit in order for it to be signed. To do this in {% data variables.product.prodname_vscode %}, ensure the "Git: Enable Commit Signing" option is enabled from the Settings. {% endnote %} 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 bf121b9919..b3f3830bd1 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 @@ -20,3 +20,7 @@ redirect_from: {% data reusables.user_settings.codespaces-tab %} 1. [Access and security] で、あなたのユーザアカウントの設定を選択します。 ![信頼するリポジトリを管理するラジオボタン](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png) 1. [Selected repositories] を選択した場合、ドロップダウンメニューを選択してから、あなたの所有するその他のリポジトリにアクセスを許可する、リポジトリのコードスペースをクリックします。 所有するその他のリポジトリにコードスペースによるアクセスを許可したい、すべてのリポジトリについて同じ手順を繰り返します。 ![[Selected repositories]ドロップダウンメニュー](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) + +## 参考リンク + +- "[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/ja-JP/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md b/translations/ja-JP/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md index 2638d59da5..3f67910afc 100644 --- a/translations/ja-JP/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md +++ b/translations/ja-JP/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md @@ -20,3 +20,7 @@ topics: ![Codespaces 情報を含むセキュリティログ](/assets/images/help/settings/codespaces-audit-log.png) セキュリティログには、発生したアクションの詳細と実行タイミングについての詳細が含まれます。 For information about {% data variables.product.prodname_codespaces %} actions, see "[{% data variables.product.prodname_codespaces %} category actions](/github/authenticating-to-github/reviewing-your-security-log#codespaces-category-actions)". + +## 参考リンク + +- "[Reviewing your organization's audit logs for {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces)" 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 new file mode 100644 index 0000000000..28e9e36b1c --- /dev/null +++ b/translations/ja-JP/content/codespaces/the-githubdev-web-based-editor.md @@ -0,0 +1,106 @@ +--- +title: The github.dev web-based editor +intro: 'Use the github.dev {% data variables.product.prodname_serverless %} from your repository or pull request to create and commit changes.' +versions: + fpt: '*' +type: how_to +miniTocMaxHeadingLevel: 3 +topics: + - Codespaces + - Visual Studio Code + - Developer +shortTitle: Web-based editor +redirect_from: + - /codespaces/developing-in-codespaces/web-based-editor +--- + +{% note %} + +**Note:** The github.dev {% data variables.product.prodname_serverless %} is currently in beta preview. You can provide feedback [in our Discussions](https://github.co/browser-editor-feedback). + +{% endnote %} + +## {% data variables.product.prodname_serverless %} について + +The {% data variables.product.prodname_serverless %} introduces a lightweight editing experience that runs entirely in your browser. With the {% data variables.product.prodname_serverless %}, you can navigate files and source code repositories from {% data variables.product.prodname_dotcom %}, and make and commit code changes. You can open any repository, fork, or pull request in the editor. + +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 %} 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. + +## Opening the {% data variables.product.prodname_serverless %} + +You can open any {% data variables.product.prodname_dotcom %} repository in the {% data variables.product.prodname_serverless %} in either of the following ways: + +- Press `.` while browsing any repository or pull request on {% data variables.product.prodname_dotcom %}. +- Change the URL from "github.com" to "github.dev". + +## {% data variables.product.prodname_codespaces %} and the {% data variables.product.prodname_serverless %} + +Both the {% data variables.product.prodname_serverless %} and {% data variables.product.prodname_codespaces %} allow you to edit your code straight from your repository. However, both have slightly different benefits, depending on your use case. + +| | {% data variables.product.prodname_serverless %} | {% data variables.product.prodname_codespaces %} +| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| **料金** | 無料. | Costs for compute and storage. For information on pricing, see "[Codespaces pricing](/en/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)." | +| **利用の可否** | Available to everyone on GitHub.com. | Available for organizations using GitHub Team or GitHub Enterprise Cloud. | +| **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. | + +### Continue working on {% data variables.product.prodname_codespaces %} + +You can start your workflow in the {% data variables.product.prodname_serverless %} and continue working on a codespace, provided you have [access to {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces). If you try to access the Run and Debug View or the Terminal, you'll be notified that they are not available in the {% data variables.product.prodname_serverless %}. + +To continue your work in a codespace, click **Continue Working on…** and select **Create New Codespace** to create a codespace on your current branch. Before you choose this option, you must commit any changes. + +![A screenshot that shows the "Continue Working on" button in the UI](/assets/images/help/codespaces/codespaces-continue-working.png) + +## 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. + +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. + +### 新規ブランチの作成 + +{% data reusables.codespaces.create-or-switch-branch %} + Any uncommited changes you have made in your old branch will be available on your new branch. + +### Commit your changes + +{% data reusables.codespaces.source-control-commit-changes %} +5. Once you have committed your changes, they will automatically be pushed to your branch on {% data variables.product.prodname_dotcom %}. +### Pull Requestの作成 + +{% data reusables.codespaces.source-control-pull-request %} + +### Working with an existing pull request + +You can use the {% data variables.product.prodname_serverless %} to work with an existing pull request. + +1. Browse to the pull request you'd like to open in the {% data variables.product.prodname_serverless %}. +2. Press `.` to open the pull request in the {% data variables.product.prodname_serverless %}. +3. Once you have made any changes, commit them using the steps in [Commit your changes](#commit-your-changes). Your changes will be committed directly to the branch, it's not necessary to push the changes. + +## 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. + +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. + + +## トラブルシューティング + +If you have issues opening the {% data variables.product.prodname_serverless %}, try the following: + +- Make sure you are signed in to {% data variables.product.prodname_dotcom %}. +- Disable any ad blockers. +- Use a non-incognito window in your browser to open 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. diff --git a/translations/ja-JP/content/communities/documenting-your-project-with-wikis/about-wikis.md b/translations/ja-JP/content/communities/documenting-your-project-with-wikis/about-wikis.md index 5c1fdf4fcd..faf2a2e203 100644 --- a/translations/ja-JP/content/communities/documenting-your-project-with-wikis/about-wikis.md +++ b/translations/ja-JP/content/communities/documenting-your-project-with-wikis/about-wikis.md @@ -34,4 +34,4 @@ topics: - 「[ウィキにフッタやサイドバーを作成する](/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki)」 - 「[ウィキのコンテンツを編集する](/communities/documenting-your-project-with-wikis/editing-wiki-content)」 - [Wkiの変更履歴の表示](/articles/viewing-a-wiki-s-history-of-changes) -- [Wikiの検索](/articles/searching-wikis) +- [Wikiの検索](/search-github/searching-on-github/searching-wikis) diff --git a/translations/ja-JP/content/communities/moderating-comments-and-conversations/locking-conversations.md b/translations/ja-JP/content/communities/moderating-comments-and-conversations/locking-conversations.md index 1970baa25a..b4c1fd91c0 100644 --- a/translations/ja-JP/content/communities/moderating-comments-and-conversations/locking-conversations.md +++ b/translations/ja-JP/content/communities/moderating-comments-and-conversations/locking-conversations.md @@ -20,7 +20,7 @@ topics: 会話がロックされている間も、[書き込みアクセスを持つユーザ](/articles/repository-permission-levels-for-an-organization/)と[リポジトリのオーナーおよびコラボレーター](/articles/permission-levels-for-a-user-account-repository/#collaborator-access-for-a-repository-owned-by-a-user-account)はコメントを追加または削除したり、非表示にしたりできます。 -アーカイブされていないリポジトリでロックされた会話を検索するには、検索修飾子 `is:locked` および `archived:false` を使用できます。 会話はアーカイブされたリポジトリで自動的にロックされます。 詳細は「[Issue およびプルリクエストを検索する](/articles/searching-issues-and-pull-requests#search-based-on-whether-a-conversation-is-locked)」を参照してください。 +アーカイブされていないリポジトリでロックされた会話を検索するには、検索修飾子 `is:locked` および `archived:false` を使用できます。 会話はアーカイブされたリポジトリで自動的にロックされます。 詳細は「[Issue およびプルリクエストを検索する](/search-github/searching-on-github/searching-issues-and-pull-requests#search-based-on-whether-a-conversation-is-locked)」を参照してください。 1. オプションで、会話をロックする理由を説明するコメントを書いてください。 2. Issue またはプルリクエストの右マージン、またはコメント ページのコメント ボックスの上で、[**Lock conversation**] をクリックします。 ![[Lock conversation] リンク](/assets/images/help/repository/lock-conversation.png) diff --git a/translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md b/translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md index 06e618732f..9241e6152b 100644 --- a/translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md +++ b/translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md @@ -1,6 +1,6 @@ --- -title: Creating a default community health file -intro: 'You can create default community health files, such as CONTRIBUTING and CODE_OF_CONDUCT. Default files will be used for any public repository owned by the account that does not contain its own file of that type.' +title: デフォルトのコミュニティ健全性ファイルを作成する +intro: CONTRIBUTING や CODE_OF_CONDUCT など、デフォルトのコミュニティ健全性ファイルを作成できます。 デフォルトのファイルは、そのような種類の独自ファイルを持たないアカウントが所有するすべてのリポジトリに使用されます。 redirect_from: - /articles/creating-a-default-community-health-file-for-your-organization - /github/building-a-strong-community/creating-a-default-community-health-file-for-your-organization @@ -10,45 +10,44 @@ versions: ghes: '*' topics: - Community +shortTitle: コミュニティ健全性ファイル --- -### About default community health files +## デフォルトのコミュニティ健全性ファイルについて -You can add default community health files to the root of a public repository called `.github` that is owned by an organization{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} or user account{% endif %}. +You can add default community health files to a public repository called `.github`, in the root of the repository or in the `docs` or `.github` folders. -{% data variables.product.product_name %} will use and display default files for any public repository owned by the account that does not have its own file of that type in any of the following places: -- the root of the repository -- the `.github` folder -- the `docs` folder +{% data variables.product.product_name %} は、次のいずれかの場所にその種類の独自ファイルを持たないアカウントが所有するリポジトリのデフォルトファイルを使用および表示します。 +- リポジトリのルート +- `.github` フォルダ +- `docs` フォルダ -For example, anyone who creates an issue or pull request in a public repository that does not have its own CONTRIBUTING file will see a link to the default CONTRIBUTING file. If a repository has any files in its own `.github/ISSUE_TEMPLATE` folder{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}, including issue templates or a *config.yml* file,{% endif %} none of the contents of the default `.github/ISSUE_TEMPLATE` folder will be used. +たとえば、独自の CONTRIBUTING ファイルを持たないリポジトリで Issue またはプルリクエストを作成すると、デフォルトの CONTRIBUTING ファイルへのリンクが表示されます。 リポジトリの独自の `.github/ISSUE_TEMPLATE` フォルダ内に +{% ifversion fpt or ghae or ghes %}、Issue テンプレートや *config.yml* ファイルなどの{% endif %}ファイルがある場合、デフォルトの`.github/ISSUE_TEMPLATE`フォルダにあるコンテンツは使用されません。 -Default files are not included in clones, packages, or downloads of individual repositories because they are stored only in the `.github` repository. +デフォルトのファイルは `.github` リポジトリにのみ格納されるものであって、クローン、パッケージ、リポジトリ個別のダウンロードには含まれません。 -### Supported file types +## サポートされているファイルの種類 -You can create defaults in your organization{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} or user account{% endif %} for the following community health files: +Organization {% ifversion fpt or ghae or ghes %}またはユーザアカウント{% endif %}に対して、次のコミュニティ健全性ファイルにデフォルトを作成できます。 -Community health file | Description ---- | ---{% if currentVersion == "free-pro-team@latest" %} -*CODE_OF_CONDUCT.md* | A CODE_OF_CONDUCT file defines standards for how to engage in a community. For more information, see "[Adding a code of conduct to your project](/articles/adding-a-code-of-conduct-to-your-project/)."{% endif %} -*CONTRIBUTING.md* | A CONTRIBUTING file communicates how people should contribute to your project. For more information, see "[Setting guidelines for repository contributors](/articles/setting-guidelines-for-repository-contributors/)."{% if currentVersion == "free-pro-team@latest" %} -*FUNDING.yml* | A FUNDING file displays a sponsor button in your repository to increase the visibility of funding options for your open source project. For more information, see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)."{% endif %} -Issue and pull request templates{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} and *config.yml*{% endif %} | Issue and pull request templates customize and standardize the information you'd like contributors to include when they open issues and pull requests in your repository. For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates/)."{% if currentVersion == "free-pro-team@latest" %} -*SECURITY.md* | A SECURITY file gives instructions for how to responsibly report a security vulnerability in your project. For more information, see "[Adding a security policy to your repository](/articles/adding-a-security-policy-to-your-repository)."{% endif %} -*SUPPORT.md* | A SUPPORT file lets people know about ways to get help with your project. For more information, see "[Adding support resources to your project](/articles/adding-support-resources-to-your-project/)." +| コミュニティ健全性ファイル | 説明 | +| ----------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion fpt %} +| *CODE_OF_CONDUCT.md* | CODE_OF_CONDUCT ファイルは、コミュニティへの関わり方についての基準を定義します。 詳しい情報については、「[プロジェクトへの行動規範の追加](/articles/adding-a-code-of-conduct-to-your-project/)」を参照してください。{% endif %} +| *CONTRIBUTING.md* | CONTRIBUTING ファイルは、人々がプロジェクトにどのように貢献すべきかを伝えます。 詳しい情報については、「[リポジトリコントリビューターのためのガイドラインを定める](/articles/setting-guidelines-for-repository-contributors/)」を参照してください。{% ifversion fpt %} +| *FUNDING.yml* | FUNDING ファイルは、あなたのオープンソースプロジェクトに対する資金提供のオプションについての認知度を高める目的で、リポジトリにスポンサーボタンを表示するためのものです。 詳細は「[リポジトリにスポンサーボタンを表示する](/articles/displaying-a-sponsor-button-in-your-repository)」を参照してください。{% endif %} +| Issue およびプルリクエストテンプレート{% ifversion fpt or ghae or ghes %}および*config.yml*{% endif %} | Issue およびプルリクエストのテンプレートは、リポジトリで Issue およびプルリクエストを開くときに含める情報をカスタマイズして標準化します。 詳しい情報については、「[Issue およびプルリクエストのテンプレートについて](/articles/about-issue-and-pull-request-templates/)」を参照してください。{% ifversion fpt or ghes > 3.0 %} +| *SECURITY.md* | SECURITY ファイルには、プロジェクトのセキュリティの脆弱性について報告する方法が記載されています。 詳しい情報については「[リポジトリにセキュリティポリシーを追加する](/code-security/getting-started/adding-a-security-policy-to-your-repository)」を参照してください。{% endif %} +| *SUPPORT.md* | SUPPORT ファイルは、プロジェクトについて支援を受ける方法を伝えるためのものです。 詳しい情報については"[プロジェクトへのサポートリソースの追加](/articles/adding-support-resources-to-your-project/)"を参照してください。 | -You cannot create a default license file. License files must be added to individual repositories so the file will be included when a project is cloned, packaged, or downloaded. +デフォルトのライセンスファイルを作成することはできません。 ライセンスファイルは、プロジェクトのクローン時、パッケージ時、またはダウンロード時に含められるよう、個々のリポジトリに追加する必要があります。 -### Creating a repository for default files +## デフォルトのファイル用にリポジトリを作成 {% data reusables.repositories.create_new %} -2. Use the **Owner** drop-down menu, and select the organization{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} or user account{% endif %} you want to create default files for. - ![Owner drop-down menu](/assets/images/help/repository/create-repository-owner.png) -3. Type **.github** as the name for your repository, and an optional description. - ![Create repository field](/assets/images/help/repository/default-file-repository-name.png) -4. Make sure the repository status is set to **Public** (a repository for default files cannot be private). - ![Radio buttons to select private or public status](/assets/images/help/repository/create-repository-public-private.png) +2. [**Owner**] ドロップダウンメニューを使用して、デフォルトファイルを作成する Organization {% ifversion fpt or ghae or ghes %}またはユーザアカウント{% endif %}を選択します。 ![[Owner] ドロップダウンメニュー](/assets/images/help/repository/create-repository-owner.png) +3. リポジトリの名前として **.github** と入力し、任意で説明を入力します。 ![リポジトリ作成フィールド](/assets/images/help/repository/default-file-repository-name.png) +4. リポジトリのステータスが **Public** に設定されていることを確認してください (デフォルトファイルのリポジトリをプライベートにすることはできません)。 ![プライベートまたはパブリックのステータスを選択するラジオボタン](/assets/images/help/repository/create-repository-public-private.png) {% data reusables.repositories.initialize-with-readme %} {% data reusables.repositories.create-repo %} -7. In the repository, create one of the supported community health files. Issue templates{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} and their configuration file{% endif %} must be in a folder called `.github/ISSUE_TEMPLATE`. All other supported files must be in the root of the repository. For more information, see "[Creating new files](/articles/creating-new-files/)." +7. リポジトリの中に、サポートされているコミュニティ健全性ファイルの 1 つを作成します。 Issue テンプレート{% ifversion fpt or ghae or ghes %}とその設定ファイル{% endif %}は、`.github/ISSUE_TEMPLATE` というフォルダ内になければなりません。 All other supported files may be in the root of the repository, the `.github` folder, or the `docs` folder. 詳細は「[新しいファイルを作成する](/articles/creating-new-files/)」を参照してください。 diff --git a/translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels.md b/translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels.md index 9335ca4733..f126936255 100644 --- a/translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels.md +++ b/translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels.md @@ -12,7 +12,7 @@ topics: shortTitle: コントリビューションの奨励 --- -ラベルで検索した際に見つけられるよう、パブリックリポジトリの Issue に `good first issue` ラベルを適用できます。 ラベル別検索についての詳細は、「[Issue およびプルリクエストを検索する](/articles/searching-issues-and-pull-requests/#search-by-label)」を参照してください。 +ラベルで検索した際に見つけられるよう、パブリックリポジトリの Issue に `good first issue` ラベルを適用できます。 ラベル別検索についての詳細は、「[Issue およびプルリクエストを検索する](/search-github/searching-on-github/searching-issues-and-pull-requests/#search-by-label)」を参照してください。 {% data variables.product.prodname_dotcom %} は、各リポジトリにおいて最も取り組みやすい Issue を判断するためのアルゴリズムを用いて、それらを {% data variables.product.prodname_dotcom_the_website %} のさまざまな場所に表示します。 `good first issue` ラベルを付ければ、Issue が表示される可能性が高まります。 @@ -24,4 +24,4 @@ shortTitle: コントリビューションの奨励 ## 参考リンク - [ラベルについて](/articles/about-labels) -- 「[リポジトリの検索](/articles/searching-for-repositories)」 +- 「[リポジトリの検索](/search-github/searching-on-github/searching-for-repositories)」 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 30cc1ab431..60da50d96d 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 @@ -42,6 +42,7 @@ Web アプリケーションフローを利用して、サイト上のユーザ アプリケーションを作成または変更する際に [**Request user authorization (OAuth) during installation**] を選択した場合、アプリケーションのインストール中にステップ 1 が完了します。 詳しい情報については、「[インストール中のユーザの認可](/apps/installing-github-apps/#authorizing-users-during-installation)」を参照してください。 ### 1. ユーザのGitHubアイデンティティのリクエスト +Direct the user to the following URL in their browser: GET {% data variables.product.oauth_host_code %}/login/oauth/authorize @@ -77,6 +78,8 @@ GitHub Appが`login`パラメータを指定すると、ユーザに対して利 ユーザトークンの期限設定は、現在のところオプション機能であり、変更される可能性があります。 ユーザからサーバーに対するトークンの期限設定にオプトインするには、「[アプリケーションのオプション機能を有効化する](/developers/apps/activating-optional-features-for-apps)」を参照してください。 +Make a request to the following endpoint to receive an access token: + POST {% data variables.product.oauth_host_code %}/login/oauth/access_token #### パラメータ diff --git a/translations/ja-JP/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md b/translations/ja-JP/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md index 9991bb0a6f..97222d47a5 100644 --- a/translations/ja-JP/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md +++ b/translations/ja-JP/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md @@ -32,7 +32,7 @@ Different server-to-server request rate limits apply to {% data variables.produc ### {% data variables.product.prodname_ghe_cloud %}のサーバーからサーバーへのレート制限 -{% data variables.product.prodname_github_apps %} that are installed on an organization or repository owned by a {% data variables.product.prodname_ghe_cloud %} account and make server-to-server requests have a rate limit of 15,000 requests per hour. +{% data variables.product.prodname_github_apps %} that are installed on an organization or repository owned by a {% data variables.product.prodname_ghe_cloud %} account and make server-to-server requests have a rate limit of 15,000 requests per hour per organization for organization installations or per repository for repository installations. {% 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 d9c7f979f9..e7db9b8338 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 @@ -78,19 +78,29 @@ GitHub Appが`login`パラメータを指定すると、ユーザに対して利 デフォルトでは、レスポンスは以下の形式になります。 - access_token={% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&token_type=bearer +``` +access_token={% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&scope=repo%2Cgist&token_type=bearer +``` -Acceptヘッダに応じて、異なる形式でコンテンツを受け取ることもできます。 +{% data reusables.apps.oauth-auth-vary-response %} - Accept: application/json - {"access_token":"{% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "scope":"repo,gist", "token_type":"bearer"} - - Accept: application/xml - - bearer - repo,gist - {% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %} - +```json +Accept: application/json +{ + "access_token":"{% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", + "scope":"repo,gist", + "token_type":"bearer" +} +``` + +```xml +Accept: application/xml + + bearer + repo,gist + {% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %} + +``` ### 3. アクセストークンを使ったAPIへのアクセス @@ -138,27 +148,35 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre #### レスポンス -{% ifversion fpt %} - ```JSON - { - "device_code": "3584d83530557fdd1f46af8289938c8ef79f9dc5", - "user_code": "WDJB-MJHT", - "verification_uri": "https://github.com/login/device", - "expires_in": 900, - "interval": 5 - } - ``` -{% else %} - ```JSON - { - "device_code": "3584d83530557fdd1f46af8289938c8ef79f9dc5", - "user_code": "WDJB-MJHT", - "verification_uri": "http(s)://[hostname]/login/device", - "expires_in": 900, - "interval": 5 - } - ``` -{% endif %} +デフォルトでは、レスポンスは以下の形式になります。 + +``` +device_code=3584d83530557fdd1f46af8289938c8ef79f9dc5&expires_in=900&interval=5&user_code=WDJB-MJHT&verification_uri=https%3A%2F%{% data variables.product.product_url %}%2Flogin%2Fdevice +``` + +{% data reusables.apps.oauth-auth-vary-response %} + +```json +Accept: application/json +{ + "device_code": "3584d83530557fdd1f46af8289938c8ef79f9dc5", + "user_code": "WDJB-MJHT", + "verification_uri": "{% data variables.product.oauth_host_code %}/login/device", + "expires_in": 900, + "interval": 5 +} +``` + +```xml +Accept: application/xml + + 3584d83530557fdd1f46af8289938c8ef79f9dc5 + WDJB-MJHT + {% data variables.product.oauth_host_code %}/login/device + 900 + 5 + +``` #### レスポンスのパラメータ @@ -196,14 +214,32 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre #### レスポンス +デフォルトでは、レスポンスは以下の形式になります。 + +``` +access_token={% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&token_type=bearer&scope=repo%2Cgist +``` + +{% data reusables.apps.oauth-auth-vary-response %} + ```json +Accept: application/json { "access_token": "{% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "token_type": "bearer", - "scope": "user" + "scope": "repo,gist" } ``` +```xml +Accept: application/xml + + {% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %} + bearer + gist,repo + +``` + ### デバイスフローのレート制限 ユーザがブラウザ上で検証コードをサブミットする場合、アプリケーションごとに1時間に50回のサブミットというレート制限があります。 diff --git a/translations/ja-JP/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md b/translations/ja-JP/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md index 9c5b39f45d..97ef64d167 100644 --- a/translations/ja-JP/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md +++ b/translations/ja-JP/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md @@ -25,7 +25,7 @@ shortTitle: アプリケーションの可視性を管理 ## プライベートのインストールフロー -プライベートインストールフローを利用すれば、GitHub Appのオーナーだけがそのアプリケーションをインストールできます。 そのGitHub Appに関する限定的な情報はパブリックなページに存在しますが、**インストール**ボタンはOrganizationの管理者もしくはGitHub Appが個人のアカウントによって所有されている場合はそのユーザアカウントからのみ利用できます。 プライベート{% ifversion ghes < 3.2 or ghae %}、または内部{% endif %}のGitHub Appは、ユーザ、もしくはオーナーのOrganizationアカウントにのみインストールできます。 +プライベートインストールフローを利用すれば、GitHub Appのオーナーだけがそのアプリケーションをインストールできます。 そのGitHub Appに関する限定的な情報はパブリックなページに存在しますが、**インストール**ボタンはOrganizationの管理者もしくはGitHub Appが個人のアカウントによって所有されている場合はそのユーザアカウントからのみ利用できます。 {% ifversion fpt or ghes > 3.1 or ghae-next %}Private {% else %}Private (also known as internal){% endif %} GitHub Apps can only be installed on the user or organization account of the owner. ## GitHub Appをインストールできるユーザの変更 @@ -36,5 +36,5 @@ GitHub Appをインストールできるユーザを変更するには以下の {% data reusables.user-settings.github_apps %} 3. インストールオプションを変更したいGitHub Appを選択してください。 ![アプリケーションの選択](/assets/images/github-apps/github_apps_select-app.png) {% data reusables.user-settings.github_apps_advanced %} -5. GitHub Appのインストールオプションに応じて、**Make public**もしくは**Make {% ifversion fpt or ghes > 3.1 %}private{% else %}internal{% endif %}**をクリックしてください。 ![GitHub Appのインストールオプションを変更するボタン](/assets/images/github-apps/github_apps_make_public.png) -6. GitHub Appのインストールオプションに応じて、**Yes, make this GitHub App public**または**Yes, make this GitHub App {% ifversion fpt or ghes > 3.1 %}private{% else %}internal{% endif %}**をクリックしてください。 ![インストールオプションの変更の確認ボタン](/assets/images/github-apps/github_apps_confirm_installation_option.png) +5. GitHub Appのインストールオプションに応じて、**Make public**もしくは**Make {% ifversion fpt or ghes > 3.1 or ghae-next %}private{% else %}internal{% endif %}**をクリックしてください。 ![GitHub Appのインストールオプションを変更するボタン](/assets/images/github-apps/github_apps_make_public.png) +6. Depending on the installation option of your GitHub App, click either **Yes, make this GitHub App public** or **Yes, make this GitHub App {% ifversion fpt or ghes < 3.2 %}internal{% else %}private{% endif %}**. ![インストールオプションの変更の確認ボタン](/assets/images/github-apps/github_apps_confirm_installation_option.png) diff --git a/translations/ja-JP/content/developers/github-marketplace/github-marketplace-overview/about-marketplace-badges.md b/translations/ja-JP/content/developers/github-marketplace/github-marketplace-overview/about-marketplace-badges.md index 0ba0b2f1b5..9202e69139 100644 --- a/translations/ja-JP/content/developers/github-marketplace/github-marketplace-overview/about-marketplace-badges.md +++ b/translations/ja-JP/content/developers/github-marketplace/github-marketplace-overview/about-marketplace-badges.md @@ -30,7 +30,7 @@ versions: {% data variables.product.prodname_marketplace %}でアプリケーションをリストするための要件に関する情報については、「[{% data variables.product.prodname_marketplace %}上にアプリケーションをリストするための要件](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)」を参照してください。 -使用するアプリケーションの探し方に関する情報については、「[{% data variables.product.prodname_marketplace %}の検索](/github/searching-for-information-on-github/searching-github-marketplace)」を参照してください。 +使用するアプリケーションの探し方に関する情報については、「[{% data variables.product.prodname_marketplace %}の検索](/search-github/searching-on-github/searching-github-marketplace)」を参照してください。 ## GitHub Actions diff --git a/translations/ja-JP/content/developers/overview/index.md b/translations/ja-JP/content/developers/overview/index.md index 16cf15e15a..fa897121a6 100644 --- a/translations/ja-JP/content/developers/overview/index.md +++ b/translations/ja-JP/content/developers/overview/index.md @@ -8,7 +8,6 @@ versions: children: - /about-githubs-apis - /managing-deploy-keys - - /viewing-deployment-history - /using-ssh-agent-forwarding - /secret-scanning-partner-program - /replacing-github-services 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 bb86b7c9da..a97891ff8d 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 @@ -190,7 +190,7 @@ Activity related to a branch protection rule. For more information, see "[About {% 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` オブジェクトは、イベントをトリガーしたユーザになります。 The `sender` object is {% ifversion fpt %}`github` {% elsif ghes > 3.0 %}`github-enterprise` {% else %}empty {% endif %}for all other actions. +`sender` | `object` | `action` が `reopened_by_user` または `closed_by_user` の場合、`sender` オブジェクトは、イベントをトリガーしたユーザになります。 The `sender` object is {% ifversion fpt %}`github`{% elsif ghes > 3.0 or ghae-next %}`github-enterprise`{% else %}empty{% endif %} for all other actions. ### webhook ペイロードの例 @@ -1032,24 +1032,29 @@ GitHub Marketplace の購入に関連するアクティビティ。 {% data reus ### webhook ペイロードオブジェクト -| キー | 種類 | 説明 | -| -------------------------- | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `ref` | `string` | プッシュされた完全な[`git ref`](/rest/reference/git#refs)。 例:`refs/heads/main`。 | -| `before` | `string` | プッシュ前の`ref` 上の最新のコミットのSHA。 | -| `after` | `string` | プッシュ後の`ref`上の最新のコミットのSHA。 | -| `commits` | `array` | プッシュされたコミットを示すコミットオブジェクトの配列。 （配列には最大で20のコミットが含まれる。 必要な場合は、追加のコミットを[Commits API](/rest/reference/repos#commits)を使ってフェッチできる。 この制限はタイムラインイベントにのみ適用され、webhookの配信には適用されない） | -| `commits[][id]` | `string` | コミットのSHA。 | -| `commits[][timestamp]` | `string` | コミットの ISO 8601 タイムスタンプ。 | -| `commits[][message]` | `string` | コミットメッセージ。 | -| `commits[][author]` | `オブジェクト` | コミットのGit作者。 | -| `commits[][author][name]` | `string` | Git作者の名前。 | -| `commits[][author][email]` | `string` | Git作者のメールアドレス。 | -| `commits[][url]` | `url` | コミットAPIのリソースを指すURL。 | -| `commits[][distinct]` | `boolean` | このコミットが以前にプッシュされたいずれとも異なっているか。 | -| `commits[][added]` | `array` | コミットに追加されたファイルの配列。 | -| `commits[][modified]` | `array` | コミットによって変更されたファイルの配列。 | -| `commits[][removed]` | `array` | コミットから削除されたファイルの配列。 | -| `pusher` | `オブジェクト` | コミットをプッシュしたユーザ。 | +| キー | 種類 | 説明 | +| -------------------------- | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `ref` | `string` | プッシュされた完全な[`git ref`](/rest/reference/git#refs)。 Example: `refs/heads/main` or `refs/tags/v3.14.1`. | +| `before` | `string` | プッシュ前の`ref` 上の最新のコミットのSHA。 | +| `after` | `string` | プッシュ後の`ref`上の最新のコミットのSHA。 | +| `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` | `オブジェクト` | 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` | プッシュされたコミットを示すコミットオブジェクトの配列。 (Pushed commits are all commits that are included in the `compare` between the `before` commit and the `after` commit.) The array includes a maximum of 20 commits. 必要な場合は、追加のコミットを[Commits API](/rest/reference/repos#commits)を使ってフェッチできる。 This limit is applied to timeline events only and isn't applied to webhook deliveries. | +| `commits[][id]` | `string` | コミットのSHA。 | +| `commits[][timestamp]` | `string` | コミットの ISO 8601 タイムスタンプ。 | +| `commits[][message]` | `string` | コミットメッセージ。 | +| `commits[][author]` | `オブジェクト` | コミットのGit作者。 | +| `commits[][author][name]` | `string` | Git作者の名前。 | +| `commits[][author][email]` | `string` | Git作者のメールアドレス。 | +| `commits[][url]` | `url` | コミットAPIのリソースを指すURL。 | +| `commits[][distinct]` | `boolean` | このコミットが以前にプッシュされたいずれとも異なっているか。 | +| `commits[][added]` | `array` | コミットに追加されたファイルの配列。 | +| `commits[][modified]` | `array` | コミットによって変更されたファイルの配列。 | +| `commits[][removed]` | `array` | コミットから削除されたファイルの配列。 | +| `pusher` | `オブジェクト` | コミットをプッシュしたユーザ。 | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} diff --git a/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md b/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md index bd99be4511..de77d9d686 100644 --- a/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md +++ b/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md @@ -53,7 +53,7 @@ You can organize discussions with categories and labels. ## 参考リンク - 「[{% data variables.product.prodname_dotcom %} での書き方と書式設定について](/github/writing-on-github/about-writing-and-formatting-on-github)」 -- 「[ディスカッションを検索する](/github/searching-for-information-on-github/searching-discussions)」 +- 「[ディスカッションを検索する](/search-github/searching-on-github/searching-discussions)」 - 「[通知について](/github/managing-subscriptions-and-notifications-on-github/about-notifications)」 - [コメントと会話の管理](/communities/moderating-comments-and-conversations) - 「[{% data variables.product.prodname_dotcom %} での安全性を維持する](/communities/maintaining-your-safety-on-github)」 diff --git a/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md b/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md index e00e0a0a76..43401ba3e2 100644 --- a/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md +++ b/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md @@ -2,7 +2,7 @@ title: ディスカッションを使用してメンテナとコラボレーションする shortTitle: メンテナとコラボレーションする intro: 'ディスカッションでプロジェクトのメンテナと連絡を取り合うことにより、{% data variables.product.product_name %} でプロジェクトの目標、計画、健全性、およびコミュニティに貢献できます。' -permissions: People with read permissions to a repository can start and participate in discussions in the repository. +permissions: 'People with read access to a repository can start and participate in discussions in the repository. {% data reusables.enterprise-accounts.emu-permission-interact %}' versions: fpt: '*' --- @@ -32,7 +32,7 @@ To collaborate with maintainers in discussions, a repository administrator or pr ## ディスカッションのリストをフィルタする -ディスカッションを検索し、リポジトリ内のディスカッションのリストをフィルタできます。 詳しい情報については、「[ ディスカッションを検索する](/github/searching-for-information-on-github/searching-discussions)」を参照してください。 +ディスカッションを検索し、リポジトリ内のディスカッションのリストをフィルタできます。 詳しい情報については、「[ ディスカッションを検索する](/search-github/searching-on-github/searching-discussions)」を参照してください。 {% data reusables.repositories.navigate-to-repo %} {% data reusables.discussions.discussions-tab %} diff --git a/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md b/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md index 68064aeb80..a3622b1baf 100644 --- a/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md +++ b/translations/ja-JP/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md @@ -1,7 +1,7 @@ --- title: ディスカッションに参加する intro: '{% data variables.product.product_name %} のプロジェクトのリポジトリ内のフォーラムで、コミュニティやメンテナと会話することができます。' -permissions: People with read permissions to a repository can participate in discussions in the repository. +permissions: 'People with read access to a repository can participate in discussions in the repository. {% data reusables.enterprise-accounts.emu-permission-interact %}' versions: fpt: '*' shortTitle: Participate in discussion diff --git a/translations/ja-JP/content/discussions/guides/finding-discussions-across-multiple-repositories.md b/translations/ja-JP/content/discussions/guides/finding-discussions-across-multiple-repositories.md index 5501dd7efc..33f912f3c0 100644 --- a/translations/ja-JP/content/discussions/guides/finding-discussions-across-multiple-repositories.md +++ b/translations/ja-JP/content/discussions/guides/finding-discussions-across-multiple-repositories.md @@ -15,6 +15,6 @@ shortTitle: Find discussions ## 参考リンク -- 「[ディスカッションを検索する](/github/searching-for-information-on-github/searching-discussions)」 +- 「[ディスカッションを検索する](/search-github/searching-on-github/searching-discussions)」 - 「[Discussions について](/discussions/collaborating-with-your-community-using-discussions/about-discussions)」 - 「[コミュニティの Discussions を管理する](/discussions/managing-discussions-for-your-community)」 diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md index dad8ffd23c..363cd322ac 100644 --- a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md @@ -8,12 +8,6 @@ redirect_from: shortTitle: Starter assignment --- -{% note %} - -**Note:** The Git & {% data variables.product.company_short %} starter assignment is in beta and subject to change. - -{% endnote %} - The Git & {% data variables.product.company_short %} starter assignment is a pre-made course that summarizes the basics of Git and {% data variables.product.company_short %} and links students to resources to learn more about specific topics. ## 必要な環境 diff --git a/translations/ja-JP/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md b/translations/ja-JP/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md index f41723972f..d19e165954 100644 --- a/translations/ja-JP/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md +++ b/translations/ja-JP/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md @@ -1,6 +1,7 @@ --- title: GitHub でオープンソースにコントリビュートする方法を見つける intro: '自分に関連する {% data variables.product.product_name %} のオープンソースプロジェクトにコントリビュートする方法を見つけることができます。' +permissions: '{% data reusables.enterprise-accounts.emu-permission-interact %}' redirect_from: - /articles/where-can-i-find-open-source-projects-to-work-on/ - /articles/finding-interesting-projects-on-github/ @@ -19,7 +20,7 @@ shortTitle: Contribute to open source ## 関連プロジェクトを発見する -興味のある特定の Topics がある場合は、`github.com/topics/` にアクセスしてください。 たとえば、機械学習に興味がある場合は、https://github.com/topics/machine-learning にアクセスして、関連するプロジェクトと good first issue を見つけることができます。 [[Topics](https://github.com/topics)] にアクセスすると、人気のある Topics を閲覧できます。 興味のある Topics に一致するリポジトリを検索することもできます。 詳しい情報については[リポジトリの検索](/articles/searching-for-repositories#search-by-topic)を参照してください。 +興味のある特定の Topics がある場合は、`github.com/topics/` にアクセスしてください。 たとえば、機械学習に興味がある場合は、https://github.com/topics/machine-learning にアクセスして、関連するプロジェクトと good first issue を見つけることができます。 [[Topics](https://github.com/topics)] にアクセスすると、人気のある Topics を閲覧できます。 興味のある Topics に一致するリポジトリを検索することもできます。 詳しい情報については[リポジトリの検索](/search-github/searching-on-github/searching-for-repositories#search-by-topic)を参照してください。 {% data variables.product.product_name %} で積極的に活動している場合は、[Explore](https://github.com/explore) での過去のコントリビューション、Star、およびその他のアクティビティに基づいて、プロジェクトについての個別の推奨事項と good first issue を見つけることができます。 Explore ニュースレターにサインアップして、あなたの興味に基づいて {% data variables.product.product_name %} にコントリビュートする機会について記載されたメールを受け取ることもできます。 サインアップするには、「[Explore メールニュースレター](https://github.com/explore/subscribe)」を参照してください。 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 f4aa1e191f..427c277fa4 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 @@ -1,6 +1,7 @@ --- title: 人をフォローする intro: '{% data variables.product.product_name %} のユーザをフォローして、アクティビティに関する通知を受け取ることができます。{% ifversion fpt %}また、それらのユーザのコミュニティ内でプロジェクトを見つけることもできます。{% endif %}' +permissions: '{% data reusables.enterprise-accounts.emu-permission-follow %}' redirect_from: - /articles/following-people - /github/getting-started-with-github/following-people 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 bdd0e357cd..4503dec22d 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 @@ -61,6 +61,7 @@ shortTitle: Associate text editors ## エディタとして Atom を使う 1. [Atom](https://atom.io/)をインストールします。 詳しい情報については、Atomのドキュメンテーションの「[Atomのインストール](https://flight-manual.atom.io/getting-started/sections/installing-atom/)」を参照してください。 +{% data reusables.command_line.open_the_multi_os_terminal %} 3. 以下のコマンドを入力してください: ```shell $ git config --global core.editor "atom --wait" diff --git a/translations/ja-JP/content/get-started/learning-about-github/access-permissions-on-github.md b/translations/ja-JP/content/get-started/learning-about-github/access-permissions-on-github.md index aec830fa29..f237a7d43a 100644 --- a/translations/ja-JP/content/get-started/learning-about-github/access-permissions-on-github.md +++ b/translations/ja-JP/content/get-started/learning-about-github/access-permissions-on-github.md @@ -36,6 +36,8 @@ Organization のメンバーは、*owner (オーナー)*{% ifversion fpt %}、*b *Enterprise のオーナー*は、Enterprise アカウントに対して最大の力を持ち、Enterprise アカウントであらゆるアクションを取ることができます。 *支払いマネージャー*は、Enterprise アカウントの支払い設定を管理できます。 Enterprise アカウントが所有する Organization のメンバーと外部コラボレーターは、自動的に Enterprise アカウントのメンバーになりますが、Enterprise アカウントそのものやその設定にはアクセスできません。 詳しい情報については、「[Enterprise アカウントのロール](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise)」を参照してください。 +If an enterprise uses {% data variables.product.prodname_emus %}, members are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and are fully managed by the identity provider. The {% data variables.product.prodname_managed_users %} have read-only access to repositories that are not a part of their enterprise and cannot interact with users that are not also members of the enterprise. Within the organizations owned by the enterprise, the {% data variables.product.prodname_managed_users %} can be granted the same granular access levels available for regular organizations. For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." + {% data reusables.gated-features.enterprise-accounts %} {% endif %} diff --git a/translations/ja-JP/content/get-started/learning-about-github/githubs-products.md b/translations/ja-JP/content/get-started/learning-about-github/githubs-products.md index 151f3526bf..71ad1e45c3 100644 --- a/translations/ja-JP/content/get-started/learning-about-github/githubs-products.md +++ b/translations/ja-JP/content/get-started/learning-about-github/githubs-products.md @@ -102,6 +102,7 @@ Organizationの{% data variables.product.prodname_free_team %}で利用できる - 50GBの{% data variables.product.prodname_registry %}ストレージ - {% data variables.product.prodname_pages %} サイトのアクセス制御。 詳しい情報については、「{% data variables.product.prodname_pages %} サイトの可視性を変更する」を参照してください。 - 99.9% の月次稼働時間を保証するサービスレベルアグリーメント +- The option to configure your enterprise for {% data variables.product.prodname_emus %}, so you can provision and manage members with your identity provider and restrict your member's contributions to just your enterprise. For more information, see "About {% data variables.product.prodname_emus %}." - エンタープライズアカウントで複数の {% data variables.product.prodname_dotcom_the_website %} Organization に対してポリシーと請求を一元管理するためのオプション。 詳細は「Enterprise アカウントについて」を参照してください。 {% data variables.product.prodname_ghe_cloud %} を評価するためのトライアルを設定できます。 詳しい情報については、「{% data variables.product.prodname_ghe_cloud %} のトライアルを設定する」を参照してください。 diff --git a/translations/ja-JP/content/get-started/learning-about-github/types-of-github-accounts.md b/translations/ja-JP/content/get-started/learning-about-github/types-of-github-accounts.md index 2e4d2f7871..5d161bc3a7 100644 --- a/translations/ja-JP/content/get-started/learning-about-github/types-of-github-accounts.md +++ b/translations/ja-JP/content/get-started/learning-about-github/types-of-github-accounts.md @@ -64,6 +64,14 @@ topics: {% endif %} +{% ifversion fpt %} +### {% data variables.product.prodname_emus %} + +With {% data variables.product.prodname_emus %}, instead of using your personal account, members of an {% data variables.product.prodname_emu_enterprise %} are provisioned accounts using the enterprise's identity provider (IdP). {% data variables.product.prodname_managed_users_caps %} authenticate using their IdP instead of a {% data variables.product.prodname_dotcom_the_website %} username and password. + +{% data variables.product.prodname_managed_users_caps %} can only interact with users, repositories, and organizations that are part of their enterprise. {% data variables.product.prodname_managed_users_caps %} have read-only access to the rest of {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." +{% endif %} + ## Organization アカウント Organization は、多くの人がいくつものプロジェクトにわたって同時にコラボレーションできる共有アカウントです。 オーナーと管理者は、Organizationのデータとプロジェクトへのメンバーのアクセスを、洗練されたセキュリティ及び管理機能で管理できます。 diff --git a/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md b/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md index 4aa9998bf5..5ba8b18625 100644 --- a/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md +++ b/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md @@ -18,16 +18,19 @@ This guide will walk you through setting up, configuring and managing your {% da The main difference between the products is that {% data variables.product.prodname_ghe_cloud %} is hosted by {% data variables.product.prodname_dotcom %}, while {% data variables.product.prodname_ghe_server %} is self-hosted. -Within the {% data variables.product.prodname_ghe_cloud %} product, there are two different types of account that you can use: +With {% data variables.product.prodname_ghe_cloud %}, you have the option of using {% data variables.product.prodname_emus %}. {% data reusables.enterprise-accounts.emu-short-summary %} + +If you choose to let your members create and manage their own user accounts instead, there are two types of accounts you can use with {% data variables.product.prodname_ghe_cloud %}: - A single organization account - An enterprise account that contains multiple organizations -In either scenario, your users will use their own self-created user account and you'll invite them to join. ### 1. Understanding the differences between an organization account and enterprise account Both organization and enterprise accounts are available with {% data variables.product.prodname_ghe_cloud %}. An organization is a shared account where groups of people can collaborate across many projects at once, and owners and administrators can manage access to data and projects. An enterprise account enables collaboration between multiple organizations, and allows owners to centrally manage policy, billing and security for these organizations. For more information on the differences, see "[Organizations and enterprise accounts](/organizations/collaborating-with-groups-in-organizations/about-organizations#organizations-and-enterprise-accounts)." + + If you choose an enterprise account, keep in mind that some policies can be set only at an organization level, while others can be enforced for all organizations in an enterprise. Once you choose the account type you would like, you can proceed to setting up your account. In each of the sections in this guide, proceed to either the single organization or enterprise account section based on your account type. @@ -86,6 +89,11 @@ You can set permissions and member roles, create and manage teams, and give peop ### Managing members of an enterprise account Managing members of an enterprise is separate from managing members or teams in an organization. It is important to note that enterprise owners or administrators cannot access organization-level settings or manage members for organizations in their enterprise unless they are made an organization owner. For more information, see the above section, "[Managing members and teams in your organization](#managing-members-and-teams-in-your-organization)." + +If your enterprise uses {% data variables.product.prodname_emus %}, your members are fully managed through your identity provider. Adding members, making changes to their membership, and assigning roles is all managed using your IdP. For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." + +If your enterprise does not use {% data variables.product.prodname_emus %}, follow the steps below. + #### 1. Assigning roles in an enterprise By default, everyone in an enterprise is a member of the enterprise. There are also administrative roles, including enterprise owner and billing manager, that have different levels of access to enterprise settings and data. 詳しい情報については、「[Enterprise アカウントのロール](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)」を参照してください。 #### 2. Enterprise を管理するようユーザを招待する @@ -97,6 +105,10 @@ To audit access to enterprise-owned resources or user license usage, you can vie ## Part 4: Managing security with {% data variables.product.prodname_ghe_cloud %} +* [Managing security for a single organization](#managing-security-for-a-single-organization) +* [Managing security for an {% data variables.product.prodname_emu_enterprise %}](#managing-security-for-an-enterprise-with-managed-users) +* [Managing security for an enterprise account without {% data variables.product.prodname_managed_users %}](#managing-security-for-an-enterprise-account-without-managed-users) + ### Managing security for a single organization You can help keep your organization secure by requiring two-factor authentication, configuring security features, reviewing your organization's audit log and integrations, and enabling SAML single sign-on and team synchronization. #### 1. Requiring two-factor authentication @@ -113,8 +125,28 @@ Organization owners can choose to disable, enable but not enforce, or enable and #### 5. Organization の Team 同期を管理する Organization owners can enable team synchronization between your identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organization owners and team maintainers to connect teams in your organization with IdP groups. 詳細は「[Organization の Team 同期を管理する](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)」を参照してください。 -### Managing security for an enterprise account with multiple organizations +### Managing security for an {% data variables.product.prodname_emu_enterprise %} + +With {% data variables.product.prodname_emus %}, access and identity is managed centrally through your identity provider. Two-factor authentication and other login requirements should be enabled and enforced on your IdP. + +#### 1. Enabling and SAML single sign-on and provisioning in your {% data variables.product.prodname_emu_enterprise %} + +In an {% data variables.product.prodname_emu_enterprise %}, all members are provisioned and managed by your identity provider. You must enable SAML SSO and SCIM provisioning before you can start using your enterprise. For more information on configuring SAML SSO and provisioning for an {% data variables.product.prodname_emu_enterprise %}, see "[Configuring SAML single sign-on for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." + +#### 2. Managing teams in your {% data variables.product.prodname_emu_enterprise %} with your identity provider + +You can connect teams in your organizations to security groups in your identity provider, managing membership of your teams and access to repositories through your IdP. For more information, see "[Managing team memberships with identity provider groups](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)." + +#### 3. Managing allowed IP addresses for organizations in your {% data variables.product.prodname_emu_enterprise %} + +You can configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your {% data variables.product.prodname_emu_enterprise %}. 詳細は、「[Enterprise アカウントでセキュリティ設定を強制する](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-security-settings-in-your-enterprise-account#managing-allowed-ip-addresses-for-organizations-in-your-enterprise-account)」を参照してください。 + +#### 4. Enforcing policies for Advanced Security features in your {% data variables.product.prodname_emu_enterprise %} +{% data reusables.getting-started.enterprise-advanced-security %} + +### Managing security for an enterprise account without {% data variables.product.prodname_managed_users %} To manage security for your enterprise, you can require two-factor authentication, manage allowed IP addresses, enable SAML single sign-on and team synchronization at an enterprise level, and sign up for and enforce GitHub Advanced Security features. + #### 1. Requiring two-factor authentication and managing allowed IP addresses for organizations in your enterprise account Enterprise のオーナーは、Enterprise アカウントが所有するすべての Organization で、Organization のメンバー、支払いマネージャー、外部コラボレーターに対して個人アカウントをセキュアに保つために 2 要素認証の使用を義務化できます。 Before doing so, we recommend notifying all who have access to organizations in your enterprise. You can also configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account. @@ -126,7 +158,7 @@ You can centrally manage access to your enterprise's resources, organization mem You can enable and manage team sychronization between an identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organizations owned by your enterprise account to manage team membership with IdP groups. 詳しい情報については、「[Enterprise アカウントで Organization の Team 同期を管理する](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/managing-team-synchronization-for-organizations-in-your-enterprise-account)」参照してください。 #### 4. Enforcing policies for Advanced Security features in your enterprise account -If you have a GitHub Advanced Security license for your enterprise account, you can enforce policies to manage {% data variables.product.prodname_dotcom %} Advanced Security features for organizations owned by an enterprise account. For more information, see "[Enforcing policies for Advanced Security in your enterprise account](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-policies-for-advanced-security-in-your-enterprise-account)." +{% data reusables.getting-started.enterprise-advanced-security %} ## Part 5: Managing organization and enterprise level policies and settings diff --git a/translations/ja-JP/content/get-started/quickstart/be-social.md b/translations/ja-JP/content/get-started/quickstart/be-social.md index 6f650cd33c..0d42dce4c0 100644 --- a/translations/ja-JP/content/get-started/quickstart/be-social.md +++ b/translations/ja-JP/content/get-started/quickstart/be-social.md @@ -6,6 +6,7 @@ redirect_from: - /github/getting-started-with-github/be-social - /github/getting-started-with-github/quickstart/be-social intro: '{% data variables.product.prodname_dotcom %} 上で、人々、リポジトリ、Organization と関わることができます。 個人ダッシュボードから、他の人々がどんな作業をしていて、何とつながっているのかを見てください。' +permissions: '{% data reusables.enterprise-accounts.emu-permission-interact %}' versions: fpt: '*' ghes: '*' diff --git a/translations/ja-JP/content/get-started/quickstart/fork-a-repo.md b/translations/ja-JP/content/get-started/quickstart/fork-a-repo.md index 8e30a10227..7823a66307 100644 --- a/translations/ja-JP/content/get-started/quickstart/fork-a-repo.md +++ b/translations/ja-JP/content/get-started/quickstart/fork-a-repo.md @@ -7,6 +7,7 @@ redirect_from: - /github/getting-started-with-github/fork-a-repo - /github/getting-started-with-github/quickstart/fork-a-repo intro: フォークとはリポジトリのコピーのことです。 リポジトリをフォークすることにより、オリジナルのプロジェクトに影響を与えることなく変更を自由にテストできます。 +permissions: '{% data reusables.enterprise-accounts.emu-permission-fork %}' versions: fpt: '*' ghes: '*' diff --git a/translations/ja-JP/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md b/translations/ja-JP/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md index e07ff80d01..34ec8d7e71 100644 --- a/translations/ja-JP/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md +++ b/translations/ja-JP/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md @@ -18,7 +18,7 @@ shortTitle: Enterprise Server trial {% data variables.product.prodname_ghe_server %} を評価するための 45 日間トライアルをリクエストできます。 トライアルは仮想アプライアンスとしてインストールされ、オンプレミスまたはクラウドでのデプロイメントのオプションがあります。 サポートされている仮想化プラットフォームの一覧については「[GitHub Enterprise Server インスタンスをセットアップする](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance)」を参照してください。 -{% ifversion ghes %}{% data variables.product.prodname_dependabot %}{% else %}現在、セキュリティ{% endif %}アラートと {% data variables.product.prodname_github_connect %} は {% data variables.product.prodname_ghe_server %} のトライアルでは利用できません。 これらの機能のデモについては、{% data variables.contact.contact_enterprise_sales %} にお問い合わせください。 これらの機能の詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)」 および「[{% data variables.product.prodname_ghe_server %} を {% data variables.product.prodname_dotcom_the_website %} に接続する](/enterprise/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)」を参照してください。 +{% ifversion ghes %}{% data variables.product.prodname_dependabot %}{% else %}現在、セキュリティ{% endif %}アラートと {% data variables.product.prodname_github_connect %} は {% data variables.product.prodname_ghe_server %} のトライアルでは利用できません。 これらの機能のデモについては、{% data variables.contact.contact_enterprise_sales %} にお問い合わせください。 For more information about these features, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" and "[Connecting your enterprise account to {% data variables.product.prodname_dotcom_the_website %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." {% data variables.product.prodname_ghe_cloud %} のトライアルも利用できます。 詳しい情報については、「[{% data variables.product.prodname_ghe_cloud %} のトライアルを設定する](/articles/setting-up-a-trial-of-github-enterprise-cloud)」を参照してください。 diff --git a/translations/ja-JP/content/get-started/using-git/dealing-with-special-characters-in-branch-and-tag-names.md b/translations/ja-JP/content/get-started/using-git/dealing-with-special-characters-in-branch-and-tag-names.md new file mode 100644 index 0000000000..e8c3daae8b --- /dev/null +++ b/translations/ja-JP/content/get-started/using-git/dealing-with-special-characters-in-branch-and-tag-names.md @@ -0,0 +1,48 @@ +--- +title: Dealing with special characters in branch and tag names +intro: 'Git is very permissive about what characters are allowed in branch and tag names. When using Git from a command-line shell, you may need to escape or quote special characters.' +versions: + fpt: '*' + ghes: '*' + ghae: '*' +shortTitle: Special characters in names +--- + +## About branch and tag names + +Most repositories use simple branch names, such as `main` or `update-icons`. Tag names also usually follow a basic format, such as a version number like `v1.2.3`. Both branch names and tag names may also use the path separator (`/`) for structure, for example `area/item` or `level-1/level-2/level-3`. Other than some exceptions — such as not starting or ending a name with a slash, or having consecutive slashes in the name — Git has very few restrictions on what characters may be used in branch and tag names. For more information, see "[git-check-ref-format](https://git-scm.com/docs/git-check-ref-format)" in the Git documentation. + +## Why you need to escape special characters + +When using a CLI, you might have situations where a branch or tag name contains special characters that have a special meaning for your shell environment. To use these characters safely in a Git command, they must be quoted or escaped, otherwise the command may have unintended effects. + +For example, the `$` character is used by many shells to refer to a variable. Most shells would interpret a valid branch name like `hello-$USER` as equivalent to the word "hello", followed by a hyphen, followed by the current value of the `USER` variable, rather than the literal string `hello-$USER`. If a branch name includes the `$` character, then the shell must be stopped from expanding it as a variable reference. Similarly, if a branch name contains a semi-colon (`;`), most shells interpret it as a command separator, so it needs to be quoted or escaped. + +## How to escape special characters in branch and tag names + +Most branch and tag names with special characters can be handled by including the name in single quotes, for example `'hello-$USER'`. + +* In the [Bash](https://www.gnu.org/software/bash/) shell, enclosing a string of characters in single quotes preserves the literal value of the characters within the single quotes. +* [Zsh](https://www.zsh.org/) behaves similar to Bash, however this behavior is configurable using the `RC_QUOTES` option. +* [PowerShell](https://microsoft.com/powershell) also treats characters literally when inside single quotes. + +For these shells, the main exception is when the branch or tag name itself contains a single quote. In this case, you should consult the official documentation for your shell: + +* [Bash documentation](https://www.gnu.org/software/bash/manual/) +* [Zsh documentation](https://zsh.sourceforge.io/Doc/) +* [Fish documentation](https://fishshell.com/docs/current/) +* [PowerShell documentation](https://docs.microsoft.com/en-gb/powershell/) + +## Naming branches and tags + +If possible, create branch and tag names that don't contain special characters, as these would need to be escaped. A safe default set of characters to use for branch names and tag names is: + +* The English alphabet (`a` to `z` and `A` to `Z`) +* Numbers (`0` to `9`) +* A limited set of punctuation characters: + * period (`.`) + * hyphen (`-`) + * underscore (`_`) + * forward slash (`/`) + +To avoid confusion, you should start branch names with a letter. diff --git a/translations/ja-JP/content/get-started/using-git/index.md b/translations/ja-JP/content/get-started/using-git/index.md index 1f57217dd8..cf5dfbf67f 100644 --- a/translations/ja-JP/content/get-started/using-git/index.md +++ b/translations/ja-JP/content/get-started/using-git/index.md @@ -23,5 +23,6 @@ children: - /about-git-rebase - /using-git-rebase-on-the-command-line - /resolving-merge-conflicts-after-a-git-rebase + - /dealing-with-special-characters-in-branch-and-tag-names --- 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 24f25e7d25..2915689cb8 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 @@ -24,7 +24,7 @@ versions: | キーボードショートカット | 説明 | | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| s または / | 検索バーにフォーカスします。 詳細は「[{% data variables.product.company_short %} での検索について](/articles/about-searching-on-github)」を参照してください。 | +| 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 %}「[通知について](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}「[通知について](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}」を参照してください。 | | esc | ユーザ、Issue、またはプルリクエストのホバーカードにフォーカスすると、ホバーカードが閉じ、ホバーカードが含まれている要素に再フォーカスします | diff --git a/translations/ja-JP/content/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md b/translations/ja-JP/content/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md index 79dd909e6f..3634192251 100644 --- a/translations/ja-JP/content/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md +++ b/translations/ja-JP/content/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md @@ -41,6 +41,12 @@ Organization オーナー、およびリポジトリにプッシュアクセス ![プルリクエスト中のステータスチェック](/assets/images/help/pull_requests/checks.png) +{% note %} + +**Note:** The **Checks** tab only gets populated for pull requests if you set up _checks_, not _statuses_, for the repository. + +{% endnote %} + コミットの特定の行でチェックが失敗している場合、その失敗、警告、注意に関する詳細がプルリクエストの [**Files**] タブの関連するコードの横に表示されます。 ![失敗したステータスチェックの詳細](/assets/images/help/pull_requests/checks-detailed.png) diff --git a/translations/ja-JP/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork.md b/translations/ja-JP/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork.md index ff11f909ac..d7890a3896 100644 --- a/translations/ja-JP/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork.md +++ b/translations/ja-JP/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork.md @@ -5,7 +5,7 @@ redirect_from: - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork - /articles/creating-a-pull-request-from-a-fork - /github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork -permissions: Anyone with write access to a repository can create a pull request from a user-owned fork. +permissions: 'Anyone with write access to a repository can create a pull request from a user-owned fork. {% data reusables.enterprise-accounts.emu-permission-propose %}' versions: fpt: '*' ghes: '*' diff --git a/translations/ja-JP/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md b/translations/ja-JP/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md index d47dc784cd..74828c4991 100644 --- a/translations/ja-JP/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md +++ b/translations/ja-JP/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md @@ -1,6 +1,7 @@ --- title: プルリクエストの作成方法 intro: リポジトリへの、変更の提案、または変更における共同作業をするには、プルリクエストを作成できます。 これらの変更は「ブランチ」を介して提案され、デフォルトブランチには完成していて、かつ承認された作業のみが含まれるようにします。 +permissions: 'Anyone with read access to a repository can create a pull request. {% data reusables.enterprise-accounts.emu-permission-propose %}' redirect_from: - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request - /articles/creating-a-pull-request @@ -13,7 +14,7 @@ topics: - Pull requests --- -リポジトリに対する読み取り権限があるユーザなら誰でもプルリクエストを作成できますが、ブランチの作成には書き込み権限が必要です。 プルリクエストのための新しいブランチを作成したいけれども、リポジトリへの書き込み権限がない場合は、まずリポジトリをフォークできます。 詳細は「[フォークからプルリクエストを作成する](/articles/creating-a-pull-request-from-a-fork)」および「[フォークについて](/articles/about-forks)」を参照してください。 +If you want to create a new branch for your pull request and do not have write permissions to the repository, you can fork the repository first. 詳細は「[フォークからプルリクエストを作成する](/articles/creating-a-pull-request-from-a-fork)」および「[フォークについて](/articles/about-forks)」を参照してください。 プルリクエストを作成するとき、変更をどのブランチにマージするかを指定できます。 2 つのブランチ間で違いがある場合にのみ、プルリクエストをオープンできます。 diff --git a/translations/ja-JP/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/translations/ja-JP/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md index 2c4bc7f90a..b22486e11c 100644 --- a/translations/ja-JP/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md +++ b/translations/ja-JP/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md @@ -1,10 +1,10 @@ --- title: プルリクエスト内の依存関係の変更をレビューする intro: プルリクエストに依存関係への変更が含まれている場合は、変更内容の概要と、依存関係に既知の脆弱性があるかどうかを確認できます。 +product: '{% data reusables.gated-features.dependency-review %}' versions: fpt: '*' ghes: '>= 3.2' - product: '{% data reusables.gated-features.dependency-review %}' type: how_to topics: - Pull requests @@ -38,19 +38,19 @@ shortTitle: Review dependency changes 1. プルリクエストに多数のファイルが含まれている場合は、[**File filter**] ドロップダウンメニューを使用して、依存関係を記録しないすべてのファイルを折りたたみます。 これにより、レビューを依存関係の変更に焦点を絞りやすくなります。 - ![ファイルフィルタメニュー](/assets/images/help/pull_requests/file-filter-menu-json.png) + ![ファイルフィルタメニュー](/assets/images/help/pull_requests/file-filter-menu-json.png) The dependency review provides a clearer view of what has changed in large lock files, where the source diff is not rendered by default. + + {% note %} + + **Note:** Dependency review rich diffs are not available for committed static JavaScript files like `jquery.js`. + + {% endnote %} 1. マニフェストまたはロックファイルのヘッダの右側で、**リッチ{% octicon "file" aria-label="The rich diff icon" %}** diff ボタンをクリックして依存関係のレビューを表示します。 ![リッチ diff ボタン](/assets/images/help/pull_requests/dependency-review-rich-diff.png) - {% note %} - - **注釈:** 依存関係のレビューでは、ソース diff がデフォルトでレンダリングされない大きなロックファイルで何が変更されたかをより明確に確認できます。 - - {% endnote %} - -1. 依存関係のレビューにリストされている依存関係を確認します。 +2. 依存関係のレビューにリストされている依存関係を確認します。 ![依存関係のレビューにおける脆弱性の警告](/assets/images/help/pull_requests/dependency-review-vulnerability.png) diff --git a/translations/ja-JP/content/github/collaborating-with-pull-requests/working-with-forks/about-forks.md b/translations/ja-JP/content/github/collaborating-with-pull-requests/working-with-forks/about-forks.md index a8699da9e5..74d3e199d8 100644 --- a/translations/ja-JP/content/github/collaborating-with-pull-requests/working-with-forks/about-forks.md +++ b/translations/ja-JP/content/github/collaborating-with-pull-requests/working-with-forks/about-forks.md @@ -20,6 +20,12 @@ topics: {% data reusables.repositories.you-can-fork %} +{% ifversion fpt %} + +If you're a member of a {% data variables.product.prodname_emu_enterprise %}, there are further restrictions on the repositories you can fork. {% data reusables.enterprise-accounts.emu-forks %} For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." + +{% endif %} + {% data reusables.repositories.desktop-fork %} フォークを削除しても、オリジナルの上流のリポジトリは削除されません。 オリジナルに影響を与えることなく、コラボレータの追加、ファイル名の変更、{% data variables.product.prodname_pages %} の生成など、自分のフォークに必要な変更を加えることができます。{% ifversion fpt %}削除されたフォークリポジトリを復元することはできません。 詳しい情報については、「[削除されたリポジトリを復元する](/articles/restoring-a-deleted-repository)」を参照してください。{% endif %} diff --git a/translations/ja-JP/content/github/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md b/translations/ja-JP/content/github/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md index 4db4f3bad7..16a630ed21 100644 --- a/translations/ja-JP/content/github/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md +++ b/translations/ja-JP/content/github/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md @@ -52,4 +52,4 @@ shortTitle: Linked to wrong user ## 参考リンク -* "[コミットの検索](/articles/searching-commits)" +* "[コミットの検索](/search-github/searching-on-github/searching-commits)" diff --git a/translations/ja-JP/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views.md b/translations/ja-JP/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views.md index e5afe7d238..c8ca74fec8 100644 --- a/translations/ja-JP/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views.md +++ b/translations/ja-JP/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views.md @@ -29,4 +29,4 @@ Gitのコミット履歴に対する考え方に関する詳しい情報につ ## 参考リンク - 「[コミットに署名する](/articles/signing-commits)」 -- "[コミットの検索](/articles/searching-commits)" +- "[コミットの検索](/search-github/searching-on-github/searching-commits)" 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 989263e8e0..7139ed503e 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 @@ -1,6 +1,6 @@ --- title: About GitHub Copilot telemetry -intro: '{% data variables.product.prodname_dotcom %} Copilot collects and relies on additional telemetry data beyond what other {% data variables.product.prodname_dotcom %} products and services collect.' +intro: '{% data variables.product.prodname_copilot %} collects and relies on additional telemetry data beyond what other {% data variables.product.company_short %} products and services collect.' redirect_from: - /early-access/github/copilot/about-github-copilot-telemetry versions: @@ -8,36 +8,21 @@ versions: --- ## What data is collected -The {% data variables.product.prodname_dotcom %} Copilot collects activity from the user’s Visual Studio Code editor, tied to a timestamp, and metadata. This metadata consists of the extension settings and the standard metadata collected by the [Visual Studio Code extension telemetry package](https://www.npmjs.com/package/vscode-extension-telemetry): -* Visual Studio Code machine ID (pseudonymized identifier) -* Visual Studio Code session ID (pseudonymized identifier) -* Visual Studio Code version -* [Geolocation from IP address](https://docs.microsoft.com/en-us/azure/azure-monitor/app/ip-collection?tabs=net) (country, state/province and city, but not the IP address itself) -* Operating system and version -* Extension version -* The VS Code UI (web or desktop) +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. -The activity collected consists of events that are triggered when: +## How the data is used by {% data variables.product.company_short %} -* An error occurs (it records the error kind and relevant background; e.g. if it’s an authentication error the key expiry date is recorded) -* Our models are accessed to ask for code suggestions (it records editor state like position of cursor and snippets of code)—this includes cases when the user takes an action to request code suggestions -* Code suggestions are received or displayed (it records the suggestions, post-processing, and metadata like model certainty and latency) -* Code suggestions are redacted due to filters that ensure AI safety -* The user acts on code suggestions (e.g. to accept or reject them) -* The user has acted on code suggestions and then it records whether or how they persisted in the code +{% data variables.product.company_short %} will use this data for: -## How the data is used -This data will only be used by {% data variables.product.company_short %} for: - -* Directly improving the product, including assessing different strategies in processing and predicting which suggestions users may find helpful -* Directly evaluating the product, e.g. by measuring the positive impact it has on the user -* Improving the underlying code generation models, e.g. by providing positive and negative examples (but always so that your private code is not used as input to suggest code for other users of {% data variables.product.prodname_dotcom %} Copilot) -* Guiding closely related {% data variables.product.prodname_dotcom %} products -* Investigating and detecting potential abuse of the {% data variables.product.prodname_dotcom %} Copilot service -* Other purposes related to improving the {% data variables.product.prodname_dotcom %} Copilot service +- Directly improving the product, including assessing different strategies in processing and predicting which suggestions users may find helpful +- Evaluating the product, e.g. by measuring the positive impact it has on the user +- Improving the underlying code generation models, e.g. by providing positive and negative examples (but always so that your private code is not used as input to suggest code for other users of {% data variables.product.prodname_copilot %}) +- Guiding closely related {% data variables.product.company_short %} products +- Investigating and detecting potential abuse of the {% data variables.product.prodname_copilot %} service +- Other purposes related to improving the {% data variables.product.prodname_copilot %} service, including sharing as described in the next section ## How the data is shared -The telemetry data is stored securely on {% data variables.product.prodname_dotcom %} systems, with appropriate encryption in place. -We know user edit actions and source code snippets are very sensitive data, and access is strictly controlled. The data can only be accessed by (1) named {% data variables.product.company_short %} personnel (employees and contractors) working on the {% data variables.product.company_short %} Copilot team or on the {% data variables.product.company_short %} platform health team, (2) select Microsoft personnel (employees and contractors) working on or with the {% data variables.product.company_short %} Copilot team, and (3) select employees of OpenAI who work on {% data variables.product.company_short %} Copilot. +The telemetry data is stored securely on {% data variables.product.company_short %} systems, with appropriate encryption in place. We know user edit actions, source code snippets, and URLs of repositories and file paths are sensitive data. Consequently, access is strictly controlled. The data can only be accessed by (1) named {% data variables.product.company_short %} personnel (employees and contractors) working on the {% data variables.product.prodname_copilot %} team or on the {% data variables.product.company_short %} platform health team, (2) Microsoft personnel (employees and contractors) working on or with the Azure and/or {% data variables.product.prodname_copilot %} teams, and (3) employees of OpenAI who work on {% data variables.product.prodname_copilot %}. + diff --git a/translations/ja-JP/content/github/copilot/github-copilot-telemetry-terms.md b/translations/ja-JP/content/github/copilot/github-copilot-telemetry-terms.md new file mode 100644 index 0000000000..6e178850e6 --- /dev/null +++ b/translations/ja-JP/content/github/copilot/github-copilot-telemetry-terms.md @@ -0,0 +1,16 @@ +--- +title: GitHub Copilot Telemetry Terms +intro: 'Acceptance of the additional telemetry described below is a condition to joining the wait list for the technical preview of {% data variables.product.prodname_copilot %} and using {% data variables.product.prodname_copilot %} during the technical preview.' +redirect_from: + - /early-access/github/copilot/telemetry-terms + - /github/copilot/telemetry-terms +versions: + fpt: '*' +--- + +## Additional telemetry + +If you use {% data variables.product.prodname_copilot %}, the {% data variables.product.prodname_copilot %} extension/plugin will collect usage information about events generated by interacting with the integrated development environment (IDE). These events include {% data variables.product.prodname_copilot %} performance, features used, and suggestions accepted, modified and accepted, or dismissed. This information may include personal data, including your User Personal Information, as defined in the [GitHub Privacy Statement](/github/site-policy/github-privacy-statement). + +This usage information is used by {% data variables.product.company_short %}, and shared with Microsoft and OpenAI, to develop and improve the extension/plugin and related products. OpenAI also uses this usage information to perform other services related to {% data variables.product.prodname_copilot %}. For example, when you edit files with the {% data variables.product.prodname_copilot %} extension/plugin enabled, file content snippets, suggestions, and any modifications to suggestions will be shared with {% data variables.product.company_short %}, Microsoft, and OpenAI, and used for diagnostic purposes to improve suggestions and related products. {% data variables.product.prodname_copilot %} relies on file content for context, both in the file you are editing and potentially other files open in the same IDE instance. When you are using {% data variables.product.prodname_copilot %}, it may also collect the URLs of repositories or file paths for relevant files. {% data variables.product.prodname_copilot %} does not use these URLs, file paths, or snippets collected in your telemetry as input to suggest code for other users of {% data variables.product.prodname_copilot %}. This information is treated as confidential information and accessed on a need-to-know basis. You are prohibited from collecting telemetry data about other users of {% data variables.product.prodname_copilot %} from the {% data variables.product.prodname_copilot %} extension/plugin. For more details about {% data variables.product.prodname_copilot %} telemetry, please see "[About {% data variables.product.prodname_copilot %} telemetry](/github/copilot/about-github-copilot-telemetry)." You may revoke your consent to the telemetry and personal data processing operations described in this paragraph by contacting GitHub and requesting removal from the technical preview. + diff --git a/translations/ja-JP/content/github/copilot/index.md b/translations/ja-JP/content/github/copilot/index.md index ef5fc94524..bc5bc35075 100644 --- a/translations/ja-JP/content/github/copilot/index.md +++ b/translations/ja-JP/content/github/copilot/index.md @@ -5,7 +5,7 @@ versions: fpt: '*' children: - /about-github-copilot-telemetry - - /telemetry-terms + - /github-copilot-telemetry-terms - /research-recitation --- diff --git a/translations/ja-JP/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md b/translations/ja-JP/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md index aad6813404..651e962f0a 100644 --- a/translations/ja-JP/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md +++ b/translations/ja-JP/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md @@ -16,7 +16,7 @@ You can discover, browse, and install free and paid tools, including {% data var ## {% data variables.product.prodname_marketplace %} でツールを見つける -他のユーザが作成したアプリやアクションを {% data variables.product.prodname_marketplace %} で検出、参照、インストールできます。「[{% data variables.product.prodname_marketplace %} を検索する](/github/searching-for-information-on-github/searching-github-marketplace)」を参照してください。 +他のユーザが作成したアプリやアクションを {% data variables.product.prodname_marketplace %} で検出、参照、インストールできます。「[{% data variables.product.prodname_marketplace %} を検索する](/search-github/searching-on-github/searching-github-marketplace)」を参照してください。 {% data reusables.actions.actions-not-verified %} diff --git a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning/sarif-support-for-code-scanning.md b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning/sarif-support-for-code-scanning.md index bdb33256a8..0b3016375b 100644 --- a/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning/sarif-support-for-code-scanning.md +++ b/translations/ja-JP/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning/sarif-support-for-code-scanning.md @@ -31,7 +31,7 @@ SARIF の使用が初めてで、詳細を確認する必要がある場合は {% data variables.product.prodname_actions %} ワークフローが新しいコードスキャンを実行するたびに、それぞれの実行結果が処理され、アラートがリポジトリに追加されます。 同じ問題に対するアラートの重複を防ぐために、{% data variables.product.prodname_code_scanning %} はフィンガープリントを使用してさまざまな実行結果を照合し、選択したブランチの最新の実行で 1 回だけ表示されるようにします。 これにより、ファイルが編集されたときに、アラートを適切なコードの行にマッチさせることができます。 -{% data variables.product.prodname_dotcom %} は、OASIS 標準の `partialFingerprints` プロパティを使用して、2 つの結果が論理的に同一の場合に検出します。 詳しい情報については、OASIS ドキュメントの「"[partialFingerprints プロパティ](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012611)」エントリを参照してください。 +{% data variables.product.prodname_dotcom %} uses the `partialFingerprints` property in the OASIS standard as an input in the computation of whether two results are logically identical. Specifically, the `primaryLocationLineHash` is used as a stable intra-file location, which is combined with the repository, file path, and rule data to form the full identity. 詳しい情報については、OASIS ドキュメントの「"[partialFingerprints プロパティ](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012611)」エントリを参照してください。 `id` は SARIF ファイルの他の部分から参照され、{% data variables.product.prodname_code_scanning %} が {% data variables.product.prodname_dotcom %} に URL を表示するために使用できます。 `upload-sarif` アクションを使用して SARIF ファイルをアップロードし、このデータが欠落している場合、{% data variables.product.prodname_dotcom %} はソースファイルから `partialFingerprints` フィールドの入力を試みます。 結果のアップロードに関する詳しい情報については、「[SARIF ファイルを {% data variables.product.prodname_dotcom %} にアップロードする](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github#uploading-a-code-scanning-analysis-with-github-actions)」を参照してください。 @@ -89,17 +89,17 @@ SARIF ファイルが {% data variables.product.prodname_code_scanning %} と互 {% data reusables.code-scanning.upload-sarif-alert-limit %} -| 名前 | 説明 | -| --------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `ruleId` | **任意。**ルールの一意の識別子（`reportingDescriptor.id`）。 詳しい情報については、「[`reportingDescriptor` オブジェクト](#reportingdescriptor-object)」を参照してください。 {% data variables.product.prodname_code_scanning_capc %} は、ルール識別子を使用して、{% data variables.product.prodname_dotcom %} のルールで結果をフィルタします。 | -| `ruleIndex` | **任意。**ツールコンポーネントの `rules` 配列内の関連するルール（`reportingDescriptor` オブジェクト）のインデックス。 詳しい情報については、「[`run` オブジェクト](#run-object)」を参照してください。 | -| `rule` | **任意。**この結果のルール（レポート記述子）を見つけるために使用される参照。 詳しい情報については、「[`reportingDescriptor` オブジェクト](#reportingdescriptor-object)」を参照してください。 | -| `level` | **任意。**結果の重要度。 このレベルは、ルールで定義されているデフォルトの重要度をオーバーライドします。 {% data variables.product.prodname_code_scanning_capc %} は、レベルを使用して、{% data variables.product.prodname_dotcom %} の重要度で結果をフィルタします。 | -| `message.text` | **必須。**結果を説明するメッセージ。 {% data variables.product.prodname_code_scanning_capc %} は、結果のタイトルとしてメッセージテキストを表示します。 表示スペースが限られている場合、メッセージの最初の文のみが表示されます。 | -| `locations[]` | **必須。**結果が検出された場所。最大値は 10 です。 指定された場所ごとに変更を加えることでのみ問題を修正できる場合を除き、1 つの場所のみを含める必要があります。 **注釈:** {% data variables.product.prodname_code_scanning %} が結果を表示するには、少なくとも 1 つの場所が必要です。 {% data variables.product.prodname_code_scanning_capc %} は、このプロパティを使用して、結果を注釈するファイルを決定します。 この配列の最初の値のみが使用されます。 他のすべての値は無視されます。 | -| `partialFingerprints` | **必須。**結果の一意の ID を追跡するために使用される文字列。 {% data variables.product.prodname_code_scanning_capc %} は、`partialFingerprints` を使用して、コミットとブランチで同じ結果であるものを正確に識別します。 {% data variables.product.prodname_code_scanning_capc %} は、`partialFingerprints` がある場合、それを使用しようとします。 `upload-action` を使用してサードパーティの SARIF ファイルをアップロードする場合、SARIF ファイルに含まれていないときに、アクションによって `partialFingerprints` が作成されます。 詳しい情報については、「[フィンガープリントを使用してアラートの重複を防止する](#preventing-duplicate-alerts-using-fingerprints)」を参照してください。 **注釈:** {% data variables.product.prodname_code_scanning_capc %} は、`primaryLocationLineHash` のみを使用します。 | -| `codeFlows[].threadFlows[].locations[]` | **任意。**`threadFlow` オブジェクトに対する `location` オブジェクトの配列。実行スレッドを通してプログラムの進行状況を記述します。 `codeFlow` オブジェクトは、結果の検出に使用されるコード実行パターンを記述します。 コードフローが入力されている場合、{% data variables.product.prodname_code_scanning %} は、関連する結果の {% data variables.product.prodname_dotcom %} のコードフローを拡張します。 詳しい情報については、「[`location` オブジェクト](#location-object)」を参照してください。 | -| `relatedLocations[]` | この結果に関連する場所。 結果メッセージに埋め込まれている場合、{% data variables.product.prodname_code_scanning_capc %} は、関連する場所にリンクします。 詳しい情報については、「[`location` オブジェクト](#location-object)」を参照してください。 | +| 名前 | 説明 | +| --------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `ruleId` | **任意。**ルールの一意の識別子（`reportingDescriptor.id`）。 詳しい情報については、「[`reportingDescriptor` オブジェクト](#reportingdescriptor-object)」を参照してください。 {% data variables.product.prodname_code_scanning_capc %} は、ルール識別子を使用して、{% data variables.product.prodname_dotcom %} のルールで結果をフィルタします。 | +| `ruleIndex` | **任意。**ツールコンポーネントの `rules` 配列内の関連するルール（`reportingDescriptor` オブジェクト）のインデックス。 詳しい情報については、「[`run` オブジェクト](#run-object)」を参照してください。 | +| `rule` | **任意。**この結果のルール（レポート記述子）を見つけるために使用される参照。 詳しい情報については、「[`reportingDescriptor` オブジェクト](#reportingdescriptor-object)」を参照してください。 | +| `level` | **任意。**結果の重要度。 このレベルは、ルールで定義されているデフォルトの重要度をオーバーライドします。 {% data variables.product.prodname_code_scanning_capc %} は、レベルを使用して、{% data variables.product.prodname_dotcom %} の重要度で結果をフィルタします。 | +| `message.text` | **必須。**結果を説明するメッセージ。 {% data variables.product.prodname_code_scanning_capc %} は、結果のタイトルとしてメッセージテキストを表示します。 表示スペースが限られている場合、メッセージの最初の文のみが表示されます。 | +| `locations[]` | **必須。**結果が検出された場所。最大値は 10 です。 指定された場所ごとに変更を加えることでのみ問題を修正できる場合を除き、1 つの場所のみを含める必要があります。 **注釈:** {% data variables.product.prodname_code_scanning %} が結果を表示するには、少なくとも 1 つの場所が必要です。 {% data variables.product.prodname_code_scanning_capc %} は、このプロパティを使用して、結果を注釈するファイルを決定します。 この配列の最初の値のみが使用されます。 他のすべての値は無視されます。 | +| `partialFingerprints` | **必須。**結果の一意の ID を追跡するために使用される文字列。 {% data variables.product.prodname_code_scanning_capc %} uses `partialFingerprints` as part of the computation to accurately identify which results are the same across commits and branches. {% data variables.product.prodname_code_scanning_capc %} は、`partialFingerprints` がある場合、それを使用しようとします。 `upload-action` を使用してサードパーティの SARIF ファイルをアップロードする場合、SARIF ファイルに含まれていないときに、アクションによって `partialFingerprints` が作成されます。 詳しい情報については、「[フィンガープリントを使用してアラートの重複を防止する](#preventing-duplicate-alerts-using-fingerprints)」を参照してください。 **注釈:** {% data variables.product.prodname_code_scanning_capc %} は、`primaryLocationLineHash` のみを使用します。 | +| `codeFlows[].threadFlows[].locations[]` | **任意。**`threadFlow` オブジェクトに対する `location` オブジェクトの配列。実行スレッドを通してプログラムの進行状況を記述します。 `codeFlow` オブジェクトは、結果の検出に使用されるコード実行パターンを記述します。 コードフローが入力されている場合、{% data variables.product.prodname_code_scanning %} は、関連する結果の {% data variables.product.prodname_dotcom %} のコードフローを拡張します。 詳しい情報については、「[`location` オブジェクト](#location-object)」を参照してください。 | +| `relatedLocations[]` | この結果に関連する場所。 結果メッセージに埋め込まれている場合、{% data variables.product.prodname_code_scanning_capc %} は、関連する場所にリンクします。 詳しい情報については、「[`location` オブジェクト](#location-object)」を参照してください。 | ### `location` オブジェクト diff --git a/translations/ja-JP/content/github/index.md b/translations/ja-JP/content/github/index.md index 7dc2b951bb..2b0e00ef72 100644 --- a/translations/ja-JP/content/github/index.md +++ b/translations/ja-JP/content/github/index.md @@ -15,7 +15,6 @@ children: - /writing-on-github - /committing-changes-to-your-project - /collaborating-with-pull-requests - - /searching-for-information-on-github - /importing-your-projects-to-github - /managing-security-vulnerabilities - /finding-security-vulnerabilities-and-errors-in-your-code diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/about-identity-and-access-management-for-your-enterprise-account.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/about-identity-and-access-management-for-your-enterprise-account.md index 3140312765..cfb9d2537b 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/about-identity-and-access-management-for-your-enterprise-account.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/about-identity-and-access-management-for-your-enterprise-account.md @@ -21,6 +21,12 @@ IdP として Azure AD を使用している場合は、Team 同期を使用し {% data reusables.saml.switching-from-org-to-enterprise %} For more information, see "[Switching your SAML configuration from an organization to an enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)." +## {% data variables.product.prodname_emus %}について + +{% data reusables.enterprise-accounts.emu-short-summary %} + +Configuring {% data variables.product.prodname_emus %} for SAML single-sign on and user provisioning involves following a different process than you would for an enterprise that isn't using {% data variables.product.prodname_managed_users %}. If your enterprise uses {% data variables.product.prodname_emus %}, see "[Configuring SAML single sign-on for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." + ## サポートされている IdP 以下の IdP はテスト済みで公式にサポートされています。 SAML SSO の場合、SAML 2.0 標準を実装するすべてのアイデンティティプロバイダに対して限定的なサポートが提供されています。 詳しい情報については、OASIS Web サイトの [SAML Wiki](https://wiki.oasis-open.org/security) を参照してください。 @@ -32,4 +38,3 @@ IdP として Azure AD を使用している場合は、Team 同期を使用し | OneLogin | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | PingOne | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | Shibboleth | {% octicon "check-circle-fill" aria-label="The check icon" %} | | - diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/configuring-saml-single-sign-on-for-your-enterprise-account-using-okta.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/configuring-saml-single-sign-on-for-your-enterprise-account-using-okta.md index d143b17111..4e3b40144b 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/configuring-saml-single-sign-on-for-your-enterprise-account-using-okta.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/configuring-saml-single-sign-on-for-your-enterprise-account-using-okta.md @@ -16,6 +16,8 @@ shortTitle: Configure SAML with Okta {% data reusables.enterprise-accounts.user-provisioning-release-stage %} +{% data reusables.enterprise-accounts.emu-saml-note %} + ## About SAML with Okta You can control access to your enterprise account in {% data variables.product.product_name %} and other web applications from one central interface by configuring the enterprise account to use SAML SSO with Okta, an Identity Provider (IdP). diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account.md index fb3051306d..9b7ddc14c3 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account.md @@ -13,6 +13,8 @@ redirect_from: shortTitle: Enforce SAML --- +{% data reusables.enterprise-accounts.emu-saml-note %} + ## Enterprise アカウントの SAML シングルサインオンについて {% data reusables.saml.dotcom-saml-explanation %} 詳細は「[SAML シングルサインオンを使うアイデンティティおよびアクセス管理について](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)」を参照してください。 diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/managing-team-synchronization-for-organizations-in-your-enterprise-account.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/managing-team-synchronization-for-organizations-in-your-enterprise-account.md index a396e6b6d2..eee1f32e98 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/managing-team-synchronization-for-organizations-in-your-enterprise-account.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/managing-team-synchronization-for-organizations-in-your-enterprise-account.md @@ -12,6 +12,8 @@ redirect_from: shortTitle: Teamの同期の管理 --- +{% data reusables.enterprise-accounts.emu-scim-note %} + ## Enterprise アカウントのチーム同期について Azure AD を IdP として使用する場合は、Enterprise アカウントのチーム同期を有効にして、Organization のオーナーとチームメンテナが、Enterprise アカウントが所有する Organization のチームを IdP グループと同期できるようにすることができます。 diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md index dda8e1ded2..7cb28a7ffd 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md @@ -10,6 +10,8 @@ topics: shortTitle: Switching from organization --- +{% data reusables.enterprise-accounts.emu-saml-note %} + ## Enterprise アカウントの SAML シングルサインオンについて {% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %} diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/index.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/index.md index eb0b1d7c4d..1ed00decf6 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/index.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/index.md @@ -14,6 +14,7 @@ topics: children: - /managing-your-enterprise-account - /managing-users-in-your-enterprise + - /managing-your-enterprise-users-with-your-identity-provider - /managing-organizations-in-your-enterprise-account - /configuring-identity-and-access-management-for-your-enterprise-account - /setting-policies-for-organizations-in-your-enterprise-account diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account.md index dc3f8288fe..299f5627b8 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account.md @@ -1,6 +1,6 @@ --- title: Enterprise アカウントに Organization を追加する -intro: Enterprise アカウント内に、新しい Organization を作成して管理できます。 +intro: You can create new organizations or invite existing organizations to manage within your enterprise account. product: '{% data reusables.gated-features.enterprise-accounts %}' redirect_from: - /articles/adding-organizations-to-your-enterprise-account @@ -13,9 +13,9 @@ topics: shortTitle: Add organizations --- -Enterprise のオーナーは、Enterprise アカウント内に新しい Organization を作成できます。 +Enterprise owners can create new organizations within an enterprise account's settings or invite existing organizations to join an enterprise account. -Organization を Enterprise アカウントに追加するには、 Enterprise アカウント設定から Organization を作成する必要があります。 既存の Organization を Enterprise アカウントに移行する場合は、{% data variables.product.prodname_dotcom %} セールス顧客担当にお問い合わせください。 +Organization を Enterprise アカウントに追加するには、 Enterprise アカウント設定から Organization を作成する必要があります。 ## Enterprise アカウント内で Organization を作成する @@ -29,3 +29,15 @@ Enterprise アカウントにより所有される Organization を作成した 4. **Create organization（Organizationの作成）**をクリックしてください。 5. [Invite owners] の下で、Organization のオーナーになるよう招待したい人のユーザ名を入力し、[**Invite**] をクリックします。 ![Organization オーナーの検索フィールドと招待ボタン](/assets/images/help/business-accounts/invite-org-owner.png) 6. [**Finish**] をクリックします。 + +## Inviting an organization to join your enterprise account + +Enterprise owners can invite existing organizations to join their enterprise account. If the organization you want to invite is already owned by another enterprise, you will not be able to issue an invitation until the previous enterprise gives up ownership of the organization. + +{% data reusables.enterprise-accounts.access-enterprise %} +2. On the **Organizations** tab, above the list of organizations, click **Invite organization**. ![Invite organization](/assets/images/help/business-accounts/enterprise-account-invite-organization.png) +3. Under "Organization name", start typing the name of the organization you want to invite and select it when it appears in the drop-down list. ![Search for organization](/assets/images/help/business-accounts/enterprise-account-search-for-organization.png) +4. Click **Invite organization**. +5. The organization owners will receive an email inviting them to join the organization. At least one owner needs to accept the invitation before the process can continue. You can cancel or resend the invitation at any time before an owner approves it. ![Cancel or resend](/assets/images/help/business-accounts/enterprise-account-invitation-sent.png) +6. Once an organization owner has approved the invitation, you can view its status in the list of pending invitations. ![Pending invitation](/assets/images/help/business-accounts/enterprise-account-pending.png) +7. Click **Approve** to complete the transfer, or **Cancel** to cancel it. ![Approve invitation](/assets/images/help/business-accounts/enterprise-account-transfer-approve.png) diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md index 0f1ac1aae2..66b532d086 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md @@ -28,6 +28,12 @@ If you want to manage owners and billing managers for an enterprise account on { {% endif %} +{% ifversion fpt %} + +If your enterprise uses {% data variables.product.prodname_emus %}, enterprise owners can only be added or removed through your identity provider. For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." + +{% endif %} + {% tip %} **ヒント:** Enterprise アカウントが所有する Organization 内のユーザを管理する方法に関する詳しい情報については、「[Organization でメンバーシップを管理する](/articles/managing-membership-in-your-organization)」および「[Organization への人々のアクセスをロールで管理する](/articles/managing-peoples-access-to-your-organization-with-roles)」を参照してください。 diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise.md index 14e121d371..4c5387a23c 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise.md @@ -21,7 +21,14 @@ Enterprise 内の全員が Enterprise のメンバーです。 Enterprise のメ {% data reusables.enterprise-accounts.enterprise-administrators %} -Enterprise にユーザを追加する方法について詳しくは、「{% ifversion fpt %}[Enterprise を管理するために人を招待する](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise){% else %}[認証](/admin/authentication){% endif %}」を参照してください。 +{% ifversion fpt %} +If your enterprise does not use {% data variables.product.prodname_emus %}, you can invite someone to an administrative role using a user account on {% data variables.product.product_name %} that they control. For more information, see "[Inviting people to manage your enterprise](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)". + +In an enterprise using {% data variables.product.prodname_emus %}, new owners and members must be provisioned through your identity provider. Enterprise owners and organization owners cannot add new members or owners to the enterprise using {% data variables.product.prodname_dotcom %}. You can select a member's enterprise role using your IdP and it cannot be changed on {% data variables.product.prodname_dotcom %}. You can select a member's role in an organization on {% data variables.product.prodname_dotcom %}. For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." +{% else %} +For more information about adding people to your enterprise, see "[Authentication](/admin/authentication)". + +{% endif %} ## Enterprise オーナー diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md index 59cd7f545f..7b1db51e48 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md @@ -18,18 +18,13 @@ shortTitle: View & manage SAML access Enterprise アカウントに対する SAML シングルサインオンを有効にすると、各 Enterprise メンバーは ID プロバイダ (IdP) での外部アイデンティティを、既存の {% data variables.product.product_name %} アカウントにリンクできます。 {% data reusables.saml.about-saml-access-enterprise-account %} +If your enterprise is uses {% data variables.product.prodname_emus %}, your members will use accounts provisioned through your IdP. {% data variables.product.prodname_managed_users_caps %} will not use their existing user account on {% data variables.product.product_name %}. For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." + ## リンクされているアイデンティティの表示と取り消し {% data reusables.saml.about-linked-identities %} -{% warning %} - -**Warning:** For organizations using SCIM: -- Revoking a linked user identity on {% data variables.product.product_name %} will also remove the SAML and SCIM metadata. As a result, the identity provider will not be able to synchronize or deprovision the linked user identity. -- An admin must revoke a linked identity through the identity provider. -- To revoke a linked identity and link a different account through the identity provider, an admin can remove and re-assign the user to the {% data variables.product.product_name %} application. For more information, see your identity provider's docs. - -{% endwarning %} +If your enterprise uses {% data variables.product.prodname_emus %}, you will not be able to deprovision or remove user accounts from the enterprise on {% data variables.product.product_name %}. Any changes you need to make to your enterprise's {% data variables.product.prodname_managed_users %} should be made through your IdP. {% data reusables.identity-and-permissions.revoking-identity-team-sync %} diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md new file mode 100644 index 0000000000..0724c75642 --- /dev/null +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md @@ -0,0 +1,84 @@ +--- +title: About Enterprise Managed Users +shortTitle: About managed users +intro: 'You can centrally manage identity and access for your enterprise members on {% data variables.product.prodname_dotcom %} from your identity provider.' +product: '{% data reusables.gated-features.emus %}' +redirect_from: + - /early-access/github/articles/get-started-with-managed-users-for-your-enterprise +versions: + fpt: '*' +topics: + - Accounts + - Enterprise +--- + +## {% data variables.product.prodname_emus %}について + +With {% data variables.product.prodname_emus %}, you can control the user accounts of your enterprise members through your identity provider (IdP). You can simplify authentication with SAML single sign-on (SSO) and provision, update, and deprovision user accounts for your enterprise members. Users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your IdP are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and added to your enterprise. You control usernames, profile data, team membership, and repository access from your IdP. + +In your IdP, you can give each {% data variables.product.prodname_managed_user %} the role of user, enterprise owner, or billing manager. {% data variables.product.prodname_managed_users_caps %} can own organizations within your enterprise and can add other {% data variables.product.prodname_managed_users %} to the organizations and teams within. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" and "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)." + +You can also manage team membership within an organization in your enterprise directly through your IdP, allowing you to manage repository access using groups in your IdP. Organization membership can be managed manually or updated automatically as {% data variables.product.prodname_managed_users %} are added to teams within the organization. For more information, see "[Managing team memberships with identity provider groups](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)." + +You can grant {% data variables.product.prodname_managed_users %} access and the ability to contribute to repositories within your enterprise, but {% data variables.product.prodname_managed_users %} cannot create public content or collaborate with other users, organizations, and enterprises on the rest of {% data variables.product.prodname_dotcom %}. The {% data variables.product.prodname_managed_users %} provisioned for your enterprise cannot be invited to organizations or repositories outside of the enterprise, nor can the {% data variables.product.prodname_managed_users %} be invited to other enterprises. Outside collaborators are not supported by {% data variables.product.prodname_emus %}. + +The usernames of your enterprise's {% data variables.product.prodname_managed_users %} and their profile information, such as display names and email addresses, are set by through your IdP and cannot be changed by the users themselves. For more information, see "[Usernames and profile information](#usernames-and-profile-information)." + +{% data reusables.enterprise-accounts.emu-forks %} + +Enterprise owners can audit all of the {% data variables.product.prodname_managed_users %}' actions on {% data variables.product.prodname_dotcom %}. + +To use {% data variables.product.prodname_emus %}, you need a separate type of enterprise account with {% data variables.product.prodname_emus %} enabled. For more information about creating this account, see "[About enterprises with managed users](#about-enterprises-with-managed-users)." + + +## Identity provider support + +{% data variables.product.prodname_emus %} supports the following IdPs: + +{% data reusables.enterprise-accounts.emu-supported-idps %} + +## Abilities and restrictions of {% data variables.product.prodname_managed_users %} + +{% data variables.product.prodname_managed_users_caps %} can only contribute to private and internal repositories within their enterprise and private repositories owned by their user account. {% data variables.product.prodname_managed_users_caps %} have read-only access to the wider {% data variables.product.prodname_dotcom %} community. + +* {% data variables.product.prodname_managed_users_caps %} cannot create issues or pull requests in, comment or add reactions to, nor star, watch, or fork repositories outside of the enterprise. +* {% data variables.product.prodname_managed_users_caps %} cannot push code to repositories outside of the enterprise. +* {% data variables.product.prodname_managed_users_caps %} and the content they create is only visible to other members of the enterprise. +* {% data variables.product.prodname_managed_users_caps %} cannot follow users outside of the enterprise. +* {% data variables.product.prodname_managed_users_caps %} cannot create gists or comment on gists. +* {% data variables.product.prodname_managed_users_caps %} cannot install {% data variables.product.prodname_github_apps %} on their user accounts. +* Other {% data variables.product.prodname_dotcom %} users cannot see, mention, or invite a {% data variables.product.prodname_managed_user %} to collaborate. +* {% data variables.product.prodname_managed_users_caps %} can only own private repositories and {% data variables.product.prodname_managed_users %} can only invite other enterprise members to collaborate on their owned repositories. +* Only private and internal repositories can be created in organizations owned by an {% data variables.product.prodname_emu_enterprise %}, depending on organization and enterprise repository visibility settings. + +## About enterprises with managed users + +To use {% data variables.product.prodname_emus %}, you need a separate type of enterprise account with {% data variables.product.prodname_emus %} enabled. To try out {% data variables.product.prodname_emus %} or to discuss options for migrating from your existing enterprise, please contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact). + +Your contact on the GitHub Sales team will work with you to create your new {% data variables.product.prodname_emu_enterprise %}. You'll need to provide the email address for the user who will set up your enterprise and a short code that will be used as the suffix for your enterprise members' usernames. {% data reusables.enterprise-accounts.emu-shortcode %} For more information, see "[Usernames and profile information](#usernames-and-profile-information)." + +After we create your enterprise, you will receive an email from {% data variables.product.prodname_dotcom %} inviting you to choose a password for your enterprise's setup user, which will be the first owner in the enterprise. The setup user is only used to configure SAML single sign-on and SCIM provisioning integration for the enterprise. It will no longer have access to administer the enterprise account once SAML is successfully enabled. + +The setup user's username is your enterprise's shortcode suffixed with `_admin`. After you log in to your setup user, you can get started by configuring SAML SSO for your enterprise. For more information, see "[Configuring SAML single sign-on for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." + +{% note %} + +{% data reusables.enterprise-accounts.emu-password-reset-session %} + +{% endnote %} + +## {% data variables.product.prodname_managed_user %} として認証を行う + +{% data variables.product.prodname_managed_users_caps %} must authenticate through their identity provider. + +To authenticate, {% data variables.product.prodname_managed_users %} must visit their IdP application portal or **https://github.com/enterprises/ENTERPRISE_NAME**, replacing **ENTERPRISE_NAME** with your enterprise's name. + +## Usernames and profile information + +When your {% data variables.product.prodname_emu_enterprise %} is created, you will choose a short code that will be used as the suffix for your enterprise member's usernames. {% data reusables.enterprise-accounts.emu-shortcode %} The setup user who configures SAML SSO has a username in the format of **@SHORT-CODE_admin**. + +When you provision a new user from your identity provider, the new {% data variables.product.prodname_managed_user %} will have a {% data variables.product.product_name %} username in the format of **@IDP-USERNAME_SHORT-CODE**. When using Azure Active Directory (Azure AD), _IDP-USERNAME_ is formed by normalizing the characters preceding the `@` character in the UPN (User Principal Name) provided by Azure AD. When using Okta, _IDP-USERNAME_ is the normalized username attribute provided by Okta. + +The username of the new account provisioned on {% data variables.product.product_name %}, including underscore and short code, must not exceed 39 characters. + +The profile name and email address of a {% data variables.product.prodname_managed_user %} is also provided by the IdP. {% data variables.product.prodname_managed_users_caps %} cannot change their profile name or email address on {% data variables.product.prodname_dotcom %}. diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/auditing-activity-in-your-enterprise.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/auditing-activity-in-your-enterprise.md new file mode 100644 index 0000000000..022dece95f --- /dev/null +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/auditing-activity-in-your-enterprise.md @@ -0,0 +1,32 @@ +--- +title: Auditing activity in your enterprise +shortTitle: Auditing activity +intro: 'You can audit the activity of the {% data variables.product.prodname_managed_users %} in your enterprise, viewing information about what actions were performed, by which user, and when they took place.' +permissions: Enterprise owners can access the audit log. +product: '{% data reusables.gated-features.emus %}' +versions: + fpt: '*' +topics: + - Accounts + - Enterprise +--- + +## About the audit log + +The audit log allows enterprise owners to quickly review or export the actions performed by both owners and members of your enterprise. Each audit log entry shows information about the event. + +- アクションが実行された Organization +- アクションを実行したユーザ +- アクションの対象となったリポジトリ +- 実行されたアクション +- アクションが実行された国 +- アクションが発生した日時 + +## Audit log にアクセスする + +You can also access the audit log for your enterprise from the REST API. For more information, see "[GitHub Enterprise administration](/rest/reference/enterprise-admin#get-the-audit-log-for-an-enterprise)" in the API documentation. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.audit-log-tab %} +1. Optionally, above the list of events, select the **Export Git Events** or **Export** drop-down menu and choose options for exporting events from the audit log. !["Export Git Events" and "Export" drop-down menus for the enterprise audit log](/assets/images/help/enterprises/audit-log-export-drop-down-menus.png) diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users.md new file mode 100644 index 0000000000..56892e874b --- /dev/null +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users.md @@ -0,0 +1,109 @@ +--- +title: Configuring SAML single sign-on for Enterprise Managed Users +shortTitle: SAML for managed users +intro: 'You can automatically manage access to your enterprise account on {% data variables.product.prodname_dotcom %} by configuring Security Assertion Markup Language (SAML) single sign-on (SSO).' +product: '{% data reusables.gated-features.emus %}' +versions: + fpt: '*' +topics: + - Accounts + - Enterprise +--- + +## About SAML single sign-on for {% data variables.product.prodname_emus %} + +With {% data variables.product.prodname_emus %}, your enterprise uses SAML SSO to authenticate all members. Instead of signing in to {% data variables.product.prodname_dotcom %} with a {% data variables.product.prodname_dotcom %} username and password, members of your enterprise will sign in through your IdP. + +{% data variables.product.prodname_emus %} supports the following IdPs: + +{% data reusables.enterprise-accounts.emu-supported-idps %} + +After you configure SAML SSO, we recommend storing your recovery codes so you can recover access to your enterprise in the event that your identity provider is unavailable. For more information, see "[Saving your recovery codes](#saving-your-recovery-codes)." + +## Configuring SAML single sign-on for {% data variables.product.prodname_emus %} + +To configure SAML SSO for your {% data variables.product.prodname_emu_enterprise %}, you must configure an application on your IdP and then configure your enterprise on GitHub.com. After you configure SAML SSO, you can configure user provisioning. + +To install and configure the {% data variables.product.prodname_emu_idp_application %} application on your IdP, you must have a tenant and administrative access on a supported IdP. + +{% note %} + +{% data reusables.enterprise-accounts.emu-password-reset-session %} + +{% endnote %} + +1. [Configuring your identity provider](#configuring-your-identity-provider) +2. [Enterprise を設定する](#configuring-your-enterprise) +3. [Enabling provisioning](#enabling-provisioning) + +### Configuring your identity provider + +To configure your IdP, follow the instructions they provide for configuring the {% data variables.product.prodname_emu_idp_application %} application on your IdP. + +1. To install the {% data variables.product.prodname_emu_idp_application %} application, click the link for your IdP below: + + - [{% data variables.product.prodname_emu_idp_application %} application on Azure Active Directory](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/aad.githubenterprisemanageduser?tab=Overview) + - [{% data variables.product.prodname_emu_idp_application %} application on Okta](https://www.okta.com/integrations/github-enterprise-managed-user) + +1. To configure the {% data variables.product.prodname_emu_idp_application %} application and your IdP, click the link below and follow the instructions provided by your IdP: + + - [Azure Active Directory tutorial for {% data variables.product.prodname_emus %}](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-enterprise-managed-user-tutorial) + - [Okta documentation for {% data variables.product.prodname_emus %}](https://saml-doc.okta.com/SAML_Docs/How-to-Configure-SAML-2.0-for-GitHub-Enterprise-Managed-User.html) + +1. So you can test and configure your enterprise, assign yourself or the user that will be configuring SAML SSO on {% data variables.product.prodname_dotcom %} to the {% data variables.product.prodname_emu_idp_application %} application on your IdP. + +1. To enable you to continue configuring your enterprise on {% data variables.product.prodname_dotcom %}, locate and note the following information from the application you installed on your IdP: + + | 値 | 別名 | 説明 | + |:----------------------------------- |:------------------ |:---------------------------------------------------------------- | + | IdP Sign-On URL | Login URL, IdP URL | Application's URL on your IdP | + | IdP Identifier URL | Issuer | IdP's identifier to service providers for SAML authentication | + | Signing certificate, Base64-encoded | Public certificate | Public certificate that IdP uses to sign authentication requests | + +### Enterprise を設定する + +After you install and configure the {% data variables.product.prodname_emu_idp_application %} application on your identity provider, you can configure your enterprise. + +1. Sign into {% data variables.product.prodname_dotcom_the_website %} as the setup user for your new enterprise with the username **@SHORT-CODE_admin**. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} + +1. Under "SAML single sign-on", select **Require SAML authentication**. ![SAML SSO を有効化するためのチェックボックス](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) + +1. Under **Sign on URL**, type the HTTPS endpoint of your IdP for single sign-on requests that you noted while configuring your IdP. ![メンバーがサインインする際にリダイレクトされる URL のフィールド](/assets/images/help/saml/saml_sign_on_url_business.png) + +1. Under **Issuer**, type your SAML issuer URL that you noted while configuring your IdP, to verify the authenticity of sent messages. ![SAMl 発行者の名前のフィールド](/assets/images/help/saml/saml_issuer.png) + +1. Under **Public Certificate**, paste the certificate that you noted while configuring your IdP, to verify SAML responses. ![アイデンティティプロバイダからの公開の証明書のフィールド](/assets/images/help/saml/saml_public_certificate.png) + +1. SAML 発行者からのリクエストの完全性を確認するには、{% octicon "pencil" aria-label="The edit icon" %} をクリックします。 Then, in the "Signature Method" and "Digest Method" drop-downs, choose the hashing algorithm used by your SAML issuer. ![SAML 発行者が使用する署名方式とダイジェスト方式のハッシュアルゴリズム用のドロップダウン](/assets/images/help/saml/saml_hashing_method.png) + +1. Before enabling SAML SSO for your enterprise, to ensure that the information you've entered is correct, click **Test SAML configuration**. ![強制化の前に SAML の構成をテストするためのボタン](/assets/images/help/saml/saml_test.png) + +1. [**Save**] をクリックします。 + + {% note %} + + **Note:** When you require SAML SSO for your enterprise, the setup user will no longer have access to the enterprise but will remain signed in to GitHub. Only {% data variables.product.prodname_managed_users %} provisioned by your IdP will have access to the enterprise. + + {% endnote %} + +1. To ensure you can still access your enterprise in the event that your identity provider is ever unavailable in the future, click **Download**, **Print**, or **Copy** to save your recovery codes. ![強制化の前に SAML の構成をテストするためのボタン](/assets/images/help/saml/saml_recovery_code_options.png) + +### Enabling provisioning + +After you enable SAML SSO, enable provisioning. For more information, see "[Configuring SCIM provisioning for enterprise managed users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users)." + +## Saving your recovery codes + +In the event that your identity provider is unavailable, you can use the setup user and a recovery code to sign in and access your enterprise. If you did not save your recovery codes when you configured SAML SSO, you can still access them from your enterprise's settings. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} + +1. Under "Require SAML authentication", click **Save your recovery codes**. ![強制化の前に SAML の構成をテストするためのボタン](/assets/images/help/enterprises/saml-recovery-codes-link.png) + +2. To save your recovery codes, click **Download**, **Print**, or **Copy**. ![強制化の前に SAML の構成をテストするためのボタン](/assets/images/help/saml/saml_recovery_code_options.png) diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md new file mode 100644 index 0000000000..c2aacc89f8 --- /dev/null +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md @@ -0,0 +1,76 @@ +--- +title: Configuring SCIM provisioning for Enterprise Managed Users with Okta +shortTitle: Set up provisioning with Okta +intro: You can provision new users and manage their membership of your enterprise and teams using Okta as your identity provider. +product: '{% data reusables.gated-features.emus %}' +versions: + fpt: '*' +redirect_from: + - /early-access/github/articles/configuring-provisioning-for-managed-users-with-okta +topics: + - Accounts + - Enterprise +--- + +## About provisioning with Okta + +You can use {% data variables.product.prodname_emus %} with Okta as your identity provider to provision new accounts, manage enterprise membership, and manage team memberships for organizations in your enterprise. For more information about provisioning for {% data variables.product.prodname_emus %}, see "[Configuring SCIM provisioning for enterprise managed users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users)." + +Before you can configure provisioning with Okta, you must configure SAML single-sign on. For more information, see "[Configuring SAML single sign-on for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." + +To configure provisioning with Okta, you must set your enterprise's name in the {% data variables.product.prodname_emu_idp_application %} application and enter your setup user's personal access token. You can then start provisioning users in Okta. + +## Supported features + +{% data variables.product.prodname_emus %} supports many provisioning features in Okta. + +| 機能 | 説明 | +| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 新しいユーザのプッシュ | Users that are assigned to the {% data variables.product.prodname_emu_idp_application %} application in Okta are automatically created in the enterprise on {% data variables.product.product_name %}. | +| Push Profile Update | Updates made to the user's profile in Okta will be pushed to {% data variables.product.product_name %}. | +| Push Groups | Groups in Okta that are assigned to the {% data variables.product.prodname_emu_idp_application %} application as Push Groups are automatically created in the enterprise on {% data variables.product.product_name %}. | +| ユーザ無効化のプッシュ | Unassigning the user from the {% data variables.product.prodname_emu_idp_application %} application in Okta will disable the user on {% data variables.product.product_name %}. The user will not be able to sign in, but the user's information is maintained. | +| ユーザの再アクティブ化 | Users in Okta whose Okta accounts are reactivated and who are assigned back to the {% data variables.product.prodname_emu_idp_application %} application will be enabled. | + +{% note %} + +**Note:** {% data variables.product.prodname_emus %} does not support modifications to usernames. + +{% endnote %} + +## Setting your enterprise name + +After your {% data variables.product.prodname_emu_enterprise %} has been created, you can begin to configure provisioning by setting your enterprise name in Okta. + +1. Navigate to your {% data variables.product.prodname_emu_idp_application %} application on Okta. +1. Click the **Sign On** tab. +1. To make changes, click **Edit**. +1. Under "Advanced Sign-on Settings", in the "Enterprise Name" text box, type your enterprise name. For example, if you access your enterprise at `https://github.com/enterprises/octoinc`, your enterprise name would be "octoinc". ![Screenshot of the Enterprise Name field on Okta](/assets/images/help/enterprises/okta-emu-enterprise-name.png) +1. To save your enterprise name, click **Save**. + +## Configuring provisioning + +After setting your enterprise name, you can proceed to configure provisioning settings. + +To configure provisioning, the setup user with the **@SHORT-CODE_admin** username will need to provide a personal access token with the **admin:enterprise** scope. For more information on creating a new token, see "[Creating a personal access token](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users#creating-a-personal-access-token)." + +1. Navigate to your {% data variables.product.prodname_emu_idp_application %} application on Okta. +1. Click the **Provisioning** tab. +1. In the settings menu, click **Integration**. +1. To make changes, click **Edit**. +1. [**Enable API integration**] を選択します。 +1. In the "API Token" field, enter the personal access token with the **admin:enterprise** scope belonging to the setup user. ![Screenshot showing the API Token field on Okta](/assets/images/help/enterprises/okta-emu-token.png) +1. Click **Test API Credentials**. If the test is successful, a verification message will appear at the top of the screen. +1. To save the token, click **Save**. +1. In the settings menu, click **To App**. ![Screenshot showing the To App menu item on Okta](/assets/images/help/enterprises/okta-emu-to-app-menu.png) +1. To the right of "Provisioning to App", to allow changes to be made, click **Edit**. +1. Select **Enable** for **Create Users**, **Update User Attributes**, and **Deactivate Users**. ![Screenshot showing provisioning options on Okta](/assets/images/help/enterprises/okta-emu-provisioning-to-app.png) +1. To finish configuring provisioning, click **Save**. + +## Assigning users + +After you have configured SAML SSO and provisioning, you will be able provision new users on {% data variables.product.prodname_dotcom_the_website %} by assigning users to the {% data variables.product.prodname_emu_idp_application %} application. You can also automatically manage organization membership by assigning groups to the application as push groups and connecting the push groups to teams in your organizations. For more information about managing teams, see "[Managing team memberships with identity provider groups](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)." + +When assigning users, you can use the "Roles" attribute in the {% data variables.product.prodname_emu_idp_application %} application to set a user's role in your enterprise on {% data variables.product.product_name %}. For more information on roles, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)." + +![Screenshot showing the role options for provisioned user on Okta](/assets/images/help/enterprises/okta-emu-user-role.png) diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md new file mode 100644 index 0000000000..8a5087d60b --- /dev/null +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md @@ -0,0 +1,54 @@ +--- +title: Configuring SCIM provisioning for Enterprise Managed Users +shortTitle: Provisioning managed users +intro: You can configure your identity provider to provision new users and manage their membership in your enterprise and teams. +product: '{% data reusables.gated-features.emus %}' +versions: + fpt: '*' +topics: + - Accounts + - Enterprise +--- + +## About provisioning for {% data variables.product.prodname_emus %} + +You can configure provisioning for {% data variables.product.prodname_emus %} to create, manage, and deactivate user accounts for your enterprise members. When you configure provisioning for {% data variables.product.prodname_emus %}, users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your identity provider are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} via SCIM, and the users are added to your enterprise. + +When you update information associated with a user's identity on your IdP, your IdP will update the user's account on GitHub.com. When you unassign the user from the {% data variables.product.prodname_emu_idp_application %} application or deactivate a user's account on your IdP, your IdP will communicate with {% data variables.product.prodname_dotcom %} to invalidate any SAML sessions and disable the member's account. The disabled account's information is maintained and their username is changed to a hash of their original username with the short code appended. If you reassign a user to the {% data variables.product.prodname_emu_idp_application %} application or reactivate their account on your IdP, the {% data variables.product.prodname_managed_user %} account on {% data variables.product.prodname_dotcom %} will be reactivated and username restored. + +Groups in your IdP can be used to manage team membership within your enterprise's organizations, allowing you to configure repository access and permissions through your IdP. For more information, see "[Managing team memberships with identity provider groups](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)." + +## 必要な環境 + +Before you can configure provisioning for {% data variables.product.prodname_emus %}, you must configure SAML single-sign on. For more information, see "[Configuring SAML single sign-on for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." + +## 個人アクセストークンを使用する + +To configure provisioning for your {% data variables.product.prodname_emu_enterprise %}, you need a personal access token with the **admin:enterprise** scope that belongs to the setup user. + +{% warning %} + +**Warning:** If the token expires or a provisioned user creates the token, SCIM provisioning may unexpectedly stop working. Make sure that you create the token while signed in as the setup user and that the token expiration is set to "No expiration". + +{% endwarning %} + +1. Sign into {% data variables.product.prodname_dotcom_the_website %} as the setup user for your new enterprise with the username **@SHORT-CODE_admin**. +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.developer_settings %} +{% data reusables.user_settings.personal_access_tokens %} +{% data reusables.user_settings.generate_new_token %} +1. Under **Note**, give your token a descriptive name. ![Screenshot showing the token's name](/assets/images/help/enterprises/emu-pat-name.png) +1. Select the **Expiration** drop-down menu, then click **No expiration**. ![Screenshot showing token expiration set to no expiration](/assets/images/help/enterprises/emu-pat-no-expiration.png) +1. Select the **admin:enterprise** scope. ![Screenshot showing the admin:enterprise scope](/assets/images/help/enterprises/enterprise-pat-scope.png) +1. [**Generate token**] をクリックします。 ![[Generate token] ボタン](/assets/images/help/settings/generate_token.png) +1. To copy the token to your clipboard, click the {% octicon "paste" aria-label="The copy icon" %}. ![新しく作成されたトークン](/assets/images/help/settings/personal_access_tokens.png) +2. To save the token for use later, store the new token securely in a password manager. + +## Configuring provisioning for {% data variables.product.prodname_emus %} + +After creating your personal access token and storing it securely, you can configure provisioning on your identity provider. + +To configure Azure Active Directory to provision users for your {% data variables.product.prodname_emu_enterprise %}, see [Tutorial: Configure GitHub Enterprise Managed User for automatic user provisioning](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-enterprise-managed-user-provisioning-tutorial) in the Azure AD documentation. + +To configure Okta to provision users for your {% data variables.product.prodname_emu_enterprise %}, see "[Configuring SCIM provisioning for Enterprise Managed Users with Okta](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users-with-okta)." + diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/index.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/index.md new file mode 100644 index 0000000000..8005a503ab --- /dev/null +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/index.md @@ -0,0 +1,19 @@ +--- +title: Managing your enterprise users with your identity provider +shortTitle: Manage users with your IdP +product: '{% data reusables.gated-features.emus %}' +intro: You can manage identity and access with your identity provider and provision accounts that can only contribute to your enterprise. +versions: + fpt: '*' +topics: + - Enterprise + - Accounts +children: + - /about-enterprise-managed-users + - /configuring-saml-single-sign-on-for-enterprise-managed-users + - /configuring-scim-provisioning-for-enterprise-managed-users + - /configuring-scim-provisioning-for-enterprise-managed-users-with-okta + - /managing-team-memberships-with-identity-provider-groups + - /auditing-activity-in-your-enterprise +--- + diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups.md new file mode 100644 index 0000000000..188a452ea5 --- /dev/null +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups.md @@ -0,0 +1,67 @@ +--- +title: Managing team memberships with identity provider groups +shortTitle: Manage teams with your IdP +intro: 'You can manage team membership on {% data variables.product.product_name %} through your identity provider (IdP) by connecting IdP groups with your {% data variables.product.prodname_emu_enterprise %}.' +product: '{% data reusables.gated-features.emus %}' +versions: + fpt: '*' +topics: + - Accounts + - Enterprise +--- + +## About team management with {% data variables.product.prodname_emus %} + +With {% data variables.product.prodname_emus %}, you can manage team membership within your enterprise through your IdP. When you connect a team in one of your enterprise's organizations to an IdP group, changes to membership from the IdP group are reflected in your enterprise automatically, reducing the need for manual updates and custom scripts. + +When a change to an IdP group or a new team connection results in a {% data variables.product.prodname_managed_user %} joining a team in an organization they were not already a member of, the {% data variables.product.prodname_managed_user %} will automatically be added to the organization. Organization owners can also manage organization membership manually. When you disconnect a group from a team, users who became members of the organization via team membership are removed from the organization if they are not assigned membership in the organization by any other means. + +You can connect a team in your enterprise to one IdP group. You can assign the same IdP group to multiple teams in your enterprise. + +If you are connecting an existing team to an IdP group, you must first remove any members that were added manually. After you connect a team in your enterprise to an IdP group, your IdP administrator must make team membership changes through the identity provider. You cannot manage team membership on {% data variables.product.prodname_dotcom_the_website %}. + +When group membership changes on your IdP, your IdP sends a SCIM request with the changes to {% data variables.product.prodname_dotcom_the_website %} according to the schedule determined by your IdP, so change may not be immediate. Any requests that change team or organization membership will register in the audit log as changes made by the account used to configure user provisioning. + +Teams connected to IdP groups cannot be parents of other teams nor a child of another team. If the team you want to connect to an IdP group is a parent or child team, we recommend creating a new team or removing the nested relationships that make your team a parent team. + +To manage repository access for any team in your enterprise, including teams connected to an IdP group, you must make changes on {% data variables.product.prodname_dotcom_the_website %}. 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)". + +## Creating a new team connected to an IdP group + +Any member of an organization can create a new team and connect the team to an IdP group. + +{% data reusables.profile.access_org %} +{% data reusables.user_settings.access_org %} +{% data reusables.organizations.new_team %} +{% data reusables.organizations.team_name %} +{% data reusables.organizations.team_description %} +1. To connect a team, select the "Identity Provider Groups" drop-down menu and click the team you want to connect. ![アイデンティティプロバイダグループを選択するドロップダウンメニュー](/assets/images/help/teams/choose-an-idp-group.png) +{% data reusables.organizations.team_visibility %} +{% data reusables.organizations.create_team %} + +## Managing the connection between an existing team and an IdP group + +Organization owners and team maintainers can manage the existing connection between an IdP group and a team. + +{% note %} + +**Note**: Before you connect an existing team on {% data variables.product.prodname_dotcom_the_website %} to an IdP group for the first time, all members of the team on {% data variables.product.prodname_dotcom_the_website %} must first be removed. For more information, see "[Removing organization members from a team](/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team)." + +{% endnote %} + +{% data reusables.profile.access_profile %} + +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +1. Optionally, under "Identity Provider Group", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="X symbol" %}. ![接続した IdP グループを GitHub team から選択解除する](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png) +1. To connect an IdP group, under "Identity Provider Group", select the drop-down menu, and click an identity provider group from the list. ![Drop-down menu to choose identity provider group](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png) +1. [**Save changes**] をクリックします。 + +## Viewing IdP groups and connected teams + +You can review a list of IdP groups, any teams connected to an IdP group, and see the membership of each IdP group on {% data variables.product.product_name %}. You must edit the membership for a group on your IdP. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.identity-provider-tab %} +1. Under "Identity Provider (IdP) Groups", review the list of IdP groups. diff --git a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account.md b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account.md index 035435a3ca..59560e6647 100644 --- a/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account.md +++ b/translations/ja-JP/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account.md @@ -42,7 +42,9 @@ Enterprise のワークフローをすべて無効にすることも、Organizat ## パブリックフォークからのワークフローに対する必須の承認の設定 -{% data reusables.actions.workflow-run-approve-public-fork %} You can configure this behavior for your enterprise using the procedure below. +{% data reusables.actions.workflow-run-approve-public-fork %} + +You can configure this behavior for your enterprise using the procedure below. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} diff --git a/translations/ja-JP/content/github/site-policy/github-data-protection-agreement.md b/translations/ja-JP/content/github/site-policy/github-data-protection-agreement.md new file mode 100644 index 0000000000..25693ba8b1 --- /dev/null +++ b/translations/ja-JP/content/github/site-policy/github-data-protection-agreement.md @@ -0,0 +1,974 @@ +--- +title: GitHub Data Protection Agreement +redirect_from: + - /github/site-policy/github-data-protection-addendum + - /github/site-policy-deprecated/github-data-protection-addendum + - /github/site-policy/github-data-protection-agreement-non-enterprise-customers +versions: + fpt: '*' +--- + +## はじめに + +The parties agree that this GitHub Data Protection Agreement (“**DPA**”) sets forth their obligations with respect to the processing and security of Personal Data and, where explicitly stated in the DPA Terms, Customer Data in connection with the Online Services provided by GitHub, Inc. (“**GitHub**”). The DPA (including its Appendix and Attachments) is between GitHub and any customer receiving Online Services from GitHub based on the GitHub Customer Agreement (“**Customer**”), and is incorporated by reference into the GitHub Customer Agreement. + +In the event of any conflict or inconsistency between the DPA Terms and any other terms in the GitHub Customer Agreement, the DPA Terms will prevail. The provisions of the DPA Terms supersede any conflicting provisions of the GitHub Privacy Statement that otherwise may apply to processing of Personal Data. For clarity, the Standard Contractual Clauses prevail over any other term of the DPA Terms. + +### Applicable DPA Terms and Updates + +#### Limits on Updates + +When Customer renews or purchases a new subscription to an Online Service, the then-current DPA Terms will apply and will not change during the term of that new subscription for that Online Service. + +#### New Features, Supplements, or Related Software + +Notwithstanding the foregoing limits on updates, when GitHub introduces features, supplements or related software that are new (i.e., that were not previously included with the subscription), GitHub may provide terms or make updates to the DPA that apply to Customer’s use of those new features, supplements or related software. If those terms include any material adverse changes to the DPA Terms, GitHub will provide Customer a choice to use the new features, supplements, or related software, without loss of existing functionality of a generally available Online Service. If Customer does not use the new features, supplements, or related software, the corresponding new terms will not apply. + +#### Government Regulation and Requirements + +Notwithstanding the foregoing limits on updates, GitHub may modify or terminate an Online Service in any country or jurisdiction where there is any current or future government requirement or obligation that (1) subjects GitHub to any regulation or requirement not generally applicable to businesses operating there, (2) presents a hardship for GitHub to continue operating the Online Service without modification, and/or (3) causes GitHub to believe the DPA Terms or the Online Service may conflict with any such requirement or obligation. + +### Electronic Notices + +GitHub may provide Customer with information and notices about Online Services electronically, including via email, or through a web site that GitHub identifies. Notice is given as of the date it is made available by GitHub. + +### Prior Versions + +The DPA Terms provide terms for Online Services that are currently available. For earlier versions of the DPA Terms, Customer may contact its reseller or GitHub Account Manager. + +## 定義 + +Capitalized terms used but not defined in this DPA will have the meanings provided in the GitHub Customer Agreement. The following defined terms are used in this DPA: + +“**CCPA**” means the California Consumer Privacy Act as set forth in Cal. Civ. Code §1798.100 et seq. and its implementing regulations. + +“**Customer Data**” means all data, including all text, sound, video, or image files, and software, that are provided to GitHub by, or on behalf of, Customer through use of the Online Service. + +“**Data Protection Requirements**” means the GDPR, Local EU/EEA Data Protection Laws, CCPA, and any applicable laws, regulations, and other legal requirements relating to (a) privacy and data security; and (b) the use, collection, retention, storage, security, disclosure, transfer, disposal, and other processing of any Personal Data. + +“**Diagnostic Data**” means data collected or obtained by GitHub from software that is locally installed by Customer in connection with the Online Service. Diagnostic Data may also be referred to as telemetry. Diagnostic Data does not include Customer Data, Service Generated Data, or Professional Services Data. + +“**DPA Terms**” means both the terms in this DPA and any Online Service-specific terms in the GitHub Customer Agreement that specifically supplement or modify the privacy and security terms in this DPA for a specific Online Service (or feature of an Online Service). In the event of any conflict or inconsistency between the DPA and such Online Service-specific terms, the Online Service-specific terms shall prevail as to the applicable Online Service (or feature of that Online Service). + +“**GDPR**” means Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation). In connection with the United Kingdom, “GDPR” means Regulation (EU) 2016/679 as transposed into national law of the United Kingdom by the UK European Union (Withdrawal) Act 2018 and amended by the UK Data Protection, Privacy and Electronic Communications (Amendments etc.) (EU Exit) Regulations 2019 (as may be amended from time to time). + +“**Local EU/EEA Data Protection Laws**” means any subordinate legislation and regulation implementing the GDPR. + +“**GDPR Related Terms**” means the terms in Attachment 3, under which GitHub makes binding commitments regarding its processing of Personal Data as required by Article 28 of the GDPR. + +“**GitHub Affiliate**” means any entity that directly or indirectly controls, is controlled by or is under common control with GitHub. + +“**GitHub Customer Agreement**” means the service or other agreement(s) entered into by Customer with GitHub for Online Services. + +“**GitHub Privacy Statement**” means the GitHub privacy statement available at https://docs.github.com/en/github/site-policy/github-privacy-statement. + +“**Online Service**” means any service or software provided by GitHub to Customer under the GitHub Customer Agreement agreed upon with Customer, including Previews, updates, patches, bug fixes, and technical support. + +“**Personal Data**” means any information relating to an identified or identifiable natural person. An identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person. + +“**Preview**” means Online Services provided for preview, evaluation, demonstration or trial purposes, or pre-release versions of the Online Services. + +“**Professional Services Data**” means all data, including all text, sound, video, image files or software, that are provided to GitHub, by or on behalf of a Customer (or that Customer authorizes GitHub to obtain from an Online Service) or otherwise obtained or processed by or on behalf of GitHub through an engagement with GitHub to obtain Professional Services. Professional Services Data includes Support Data. + +“**Service Generated Data**” means data generated or derived by GitHub through the operation of an Online Service. Service Generated Data does not include Customer Data, Diagnostic Data, or Professional Services Data. + +“**Standard Contractual Clauses**” means either of the following sets of Standard Contractual Clauses, as applicable in the individual case to the transfer of personal data according to the section of this DPA entitled “Data Transfers and Location” below: +- the Standard Contractual Clauses (MODULE TWO: Transfer controller to processor), dated 4 June 2021, for the transfer of personal data to third countries pursuant to Regulation (EU) 2016/679 of the European Parliament and of the Council, as described in Article 46 of the GDPR and approved by European Commission Implementing Decision (EU) 2021/91 (“Standard Contractual Clauses (EU/EEA)”). The Standard Contractual Clauses (EU/EEA) are set forth in Attachment 1. +- the Standard Contractual Clauses (Processors), dated 5 February 2010, for the transfer of personal data to processors established in third countries which do not ensure an adequate level of data protection, as described in Article 46 of the GDPR, approved by European Commission Decision 2010/87/EU and recognized by the regulatory or supervisory authorities of the United Kingdom for use in connection with data transfers from the United Kingdom (“Standard Contractual Clauses (UK)”). The Standard Contractual Clauses (UK) are set forth in Attachment 2. + +“**Subprocessor**” means other processors used by GitHub to process Personal Data on behalf of Customer in connection with the Online Services, as described in Article 28 of the GDPR. + +“**Support Data**” means all data, including all text, sound, video, image files, or software, that are provided to GitHub by or on behalf of Customer (or that Customer authorizes GitHub to obtain from an Online Service) through an engagement with GitHub to obtain technical support for Online Services covered under this agreement. Support Data is a subset of Professional Services Data. + +Lower case terms used but not defined in this DPA, such as “personal data breach”, “processing”, “controller”, “processor”, “profiling”, “personal data”, and “data subject” will have the same meaning as set forth in Article 4 of the GDPR, irrespective of whether GDPR applies. The terms “data importer” and “data exporter” have the meanings given in the Standard Contractual Clauses. + +For clarity, and as detailed above, data defined as Customer Data, Diagnostic Data, Service Generated Data, and Professional Services Data may contain Personal Data. For illustrative purposes, please see the chart inserted below: + +
    + personal_data_types +
    + +Above is a visual representation of the data types defined in the DPA. All Personal Data is processed as a part of one of the other data types (all of which also include non-personal data). Support Data is a sub-set of Professional Services Data. Except where explicitly stated otherwise, the DPA Terms exclusively apply to Personal Data. + +## General Terms + +### Compliance with Laws + +GitHub will comply with all laws and regulations applicable to its provision of the Online Services, including security breach notification law and Data Protection Requirements. However, GitHub is not responsible for compliance with any laws or regulations applicable to Customer or Customer’s industry that are not generally applicable to information technology service providers. GitHub does not determine whether Customer Data includes information subject to any specific law or regulation. All Security Incidents are subject to the Security Incident Notification terms below. + +Customer must comply with all laws and regulations applicable to its use of Online Services, including laws related to biometric data, confidentiality of communications, and Data Protection Requirements. Customer is responsible for determining whether the Online Services are appropriate for storage and processing of information subject to any specific law or regulation and for using the Online Services in a manner consistent with Customer’s legal and regulatory obligations. Customer is responsible for responding to any request from a third party regarding Customer’s use of an Online Service, such as a request to take down content under the U.S. Digital Millennium Copyright Act or other applicable laws. + +## データ保護 + +Terms This section of the DPA includes the following subsections: +- スコープ +- Nature of Data Processing; Ownership +- Disclosure of Processed Data +- Processing of Personal Data; GDPR +- Data Security +- Security Incident Notification +- Data Transfers and Location +- Data Retention and Deletion +- Processor Confidentiality Commitment +- Notice and Controls on Use of Subprocessors +- Educational Institutions +- CJIS Customer Agreement, HIPAA Business Associate, Biometric Data +- California Consumer Privacy Act (CCPA) +- How to Contact GitHub +- Appendix A – Security Measures + +### スコープ + +The DPA Terms apply to all Online Services. + +Previews may employ lesser or different privacy and security measures than those typically present in the Online Services. Unless otherwise noted, Customer should not use Previews to process Personal Data or other data that is subject to legal or regulatory compliance requirements. The following terms in this DPA do not apply to Previews: Processing of Personal Data; GDPR, Data Security, and California Consumer Privacy Act. + +### Nature of Data Processing; Ownership + +Except as otherwise stated in the DPA Terms, GitHub will use and otherwise process Customer Data and Personal Data as described and subject to the limitations provided below (a) to provide Customer the Online Service in accordance with Customer’s documented instructions, and/or (b) for GitHub’s legitimate business operations incident to delivery of the Online Services to Customer. As between the parties, Customer retains all right, title and interest in and to Customer Data. GitHub acquires no rights in Customer Data other than the rights Customer grants to GitHub in this section. This paragraph does not affect GitHub’s rights in software or services GitHub licenses to Customer. + +#### Processing to Provide Customer the Online Services + +For purposes of this DPA, “to provide” an Online Service consists of: +- Delivering functional capabilities as licensed, configured, and used by Customer and its users, including providing personalized user experiences; +- Troubleshooting (e.g., preventing, detecting, and repairing problems); and +- Ongoing improvement (e.g., installing the latest updates and making improvements to user productivity, reliability, efficacy, and security). + +When providing Online Services, GitHub will use or otherwise process Personal Data only on Customer’s behalf and in accordance with Customer’s documented instructions. + +#### Processing for GitHub’s Legitimate Business Operations + +For purposes of this DPA, “GitHub’s legitimate business operations” consist of the following, each as incident to delivery of the Online Services to Customer: (1) billing and account management; (2) compensation (e.g., calculating employee commissions and partner incentives); (3) internal reporting and business modeling (e.g., forecasting, revenue, capacity planning, product strategy); (4) combatting fraud, abuse, cybercrime, or cyber-attacks that may affect GitHub or Online Services; (5) improving the core functionality of accessibility, privacy or energy-efficiency; (6) financial reporting and compliance with legal obligations (subject to the limitations on disclosure of Processed Data outlined below); (7) the creation or management of end user accounts and profiles by GitHub for individual users of Customer (except where Customer creates, manages or otherwise controls such end user accounts or profiles itself); and (8) other purposes pertaining to Personal Data not provided by Customer for storage in GitHub repositories or in connection with Professional Services. + +When processing for GitHub’s legitimate business operations, GitHub will not use or otherwise process Personal Data for: (a) user profiling, (b) advertising or similar commercial purposes, (c) data selling or brokering, or (d) any other purpose, other than for the purposes set out in this section. + +### Disclosure of Processed Data + +GitHub will not disclose or provide access to any Processed Data except: (1) as Customer directs; (2) as described in this DPA; or (3) as required by law. For purposes of this section, “Processed Data” means: (a) Customer Data; (b) Personal Data and (c) any other data processed by GitHub in connection with the Online Service that is Customer’s confidential information under the GitHub Customer Agreement. All processing of Processed Data is subject to GitHub’s obligation of confidentiality under the GitHub Customer Agreement. + +GitHub will not disclose or provide access to any Processed Data to law enforcement unless required by law. If law enforcement contacts GitHub with a demand for Processed Data, GitHub will attempt to redirect the law enforcement agency to request that data directly from Customer. If compelled to disclose or provide access to any Processed Data to law enforcement, GitHub will promptly notify Customer and provide a copy of the demand, unless legally prohibited from doing so. + +Upon receipt of any other third-party request for Processed Data, GitHub will promptly notify Customer unless prohibited by law. GitHub will reject the request unless required by law to comply. If the request is valid, GitHub will attempt to redirect the third party to request the data directly from Customer. + +GitHub will not provide any third party: (a) direct, indirect, blanket, or unfettered access to Processed Data; (b) platform encryption keys used to secure Processed Data or the ability to break such encryption; or (c) access to Processed Data if GitHub is aware that the data is to be used for purposes other than those stated in the third party’s request. + +In support of the above, GitHub may provide Customer’s basic contact information to the third party. + +### Processing of Personal Data; GDPR + +All Personal Data processed by GitHub in connection with the Online Services is obtained as part of either Customer Data, Professional Services Data (including Support Data), Diagnostic Data, or Service Generated Data. Personal Data provided to GitHub by, or on behalf of, Customer through use of the Online Service is also Customer Data. Pseudonymized identifiers may be included in Diagnostic Data or Service Generated Data and are also Personal Data. Any Personal Data pseudonymized, or de-identified but not anonymized, or Personal Data derived from Personal Data is also Personal Data. + +To the extent GitHub is a processor or subprocessor of Personal Data subject to the GDPR, the GDPR Related Terms in Attachment 3 govern that processing and the parties also agree to the following terms in this sub-section (“Processing of Personal Data; GDPR”): + +#### Processor and Controller Roles and Responsibilities + +Customer and GitHub agree that Customer is the controller of Personal Data and GitHub is the processor of such data, except (a) when Customer acts as a processor of Personal Data, in which case GitHub is a subprocessor; or (b) as stated otherwise in the GitHub Customer Agreement or this DPA. When GitHub acts as the processor or subprocessor of Personal Data, it will process Personal Data only on Customer’s behalf and in accordance with documented instructions from Customer. Customer agrees that its GitHub Customer Agreement (including the DPA Terms and any applicable updates), along with the product documentation and Customer’s use and configuration of features in the Online Services, are Customer’s complete documented instructions to GitHub for the processing of Personal Data. Information on use and configuration of the Online Services can be found at https://docs.github.com or a successor location. Any additional or alternate instructions must be agreed to according to the process for amending Customer’s GitHub Customer Agreement. In any instance where the GDPR applies and Customer is a processor, Customer warrants to GitHub that Customer’s instructions, including appointment of GitHub as a processor or subprocessor, have been authorized by the relevant controller. + +To the extent GitHub uses or otherwise processes Personal Data subject to the GDPR for GitHub’s legitimate business operations incident to delivery of the Online Services to Customer, GitHub will comply with the obligations of an independent data controller under GDPR for such use. GitHub is accepting the added responsibilities of a data “controller” under the GDPR for processing in connection with its legitimate business operations to: (a) act consistent with regulatory requirements, to the extent required under the GDPR; and (b) provide increased transparency to Customers and confirm GitHub’s accountability for such processing. GitHub employs safeguards to protect Personal Data in processing, including those identified in this DPA and those contemplated in Article 6(4) of the GDPR. With respect to processing of Personal Data under this paragraph, GitHub makes the commitments set forth in the Standard Contractual Clauses set forth in Attachment 1 or Attachment 2 (as applicable); for those purposes, (i) any GitHub disclosure of Personal Data, as described in Annex III to Attachment 1 or Appendix 3 to Attachment 2 (as applicable), that has been transferred in connection with GitHub’s legitimate business operations is deemed a “Relevant Disclosure” and (ii) the commitments in Annex III to Attachment 1 or Appendix 3 to Attachment 2 (as applicable) apply to such Personal Data. + +#### Processing Details + +The parties acknowledge and agree that: + +- **Subject Matter**. The subject-matter of the processing is limited to Personal Data within the scope of the section of this DPA entitled “Nature of Data Processing; Ownership” above and the GDPR. +- **Duration of the Processing**. The duration of the processing shall be in accordance with Customer instructions and the terms of the DPA. +- **Nature and Purpose of the Processing**. The nature and purpose of the processing shall be to provide the Online Service pursuant to Customer’s GitHub Customer Agreement and for GitHub’s legitimate business operations incident to delivery of the Online Service to Customer (as further described in the section of this DPA entitled “Nature of Data Processing; Ownership” above). +- **Categories of Data**. The types of Personal Data processed by GitHub when providing the Online Service include: (i) Personal Data that Customer elects to include in Customer Data or Professional Services Data (including, without limitation, Support Data); and (ii) those expressly identified in Article 4 of the GDPR that may be contained in Diagnostic Data or Service Generated Data. The types of Personal Data that Customer elects to include in Customer Data or Professional Services Data (including, without limitation, Support Data) may be any categories of Personal Data identified in records maintained by Customer acting as controller pursuant to Article 30 of the GDPR, including the categories of Personal Data set forth in Annex I to Attachment 1 or Appendix 1 to Attachment 2 (as applicable). +- Data Subjects. The categories of data subjects are Customer’s representatives and end users, such as employees, contractors, collaborators, and customers, and may include any other categories of data subjects as identified in records maintained by Customer acting as controller pursuant to Article 30 of the GDPR, including the categories of data subjects set forth in Annex I to Attachment 1 or Appendix 1 to Attachment 2 (as applicable). + +#### Data Subject Rights; Assistance with Requests + +GitHub will make available to Customer, in a manner consistent with the functionality of the Online Service and GitHub’s role as a processor of Personal Data of data subjects, the ability to fulfill data subject requests to exercise their rights under the GDPR. If GitHub receives a request from Customer’s data subject to exercise one or more of its rights under the GDPR in connection with an Online Service for which GitHub is a data processor or subprocessor, GitHub will redirect the data subject to make its request directly to Customer. Customer will be responsible for responding to any such request including, where necessary, by using the functionality of the Online Service. GitHubは、かかるデータ主体の要求に応答するお客様を支援するため、お客様による合理的な要求に応じるものとします。 + +#### Records of Processing Activities + +To the extent the GDPR requires GitHub to collect and maintain records of certain information relating to Customer, Customer will, where requested, supply such information to GitHub and keep it accurate and up-to-date. GitHub may make any such information available to the supervisory authority if required by the GDPR. + +### Data Security + +GitHub will implement and maintain appropriate technical and organizational measures and security safeguards against accidental or unlawful destruction, or loss, alteration, unauthorized disclosure of or access to, Customer Data and Personal Data processed by GitHub on behalf and in accordance with the documented instructions of Customer in connection with the Online Services. GitHub will regularly monitor compliance with these measures and safeguards and will continue to take appropriate steps throughout the term of the GitHub Customer Agreement. Appendix A – Security Safeguards contains a description of the technical and organizational measures and security safeguards implemented by GitHub. + +Customer is solely responsible for making an independent determination as to whether the technical and organizational measures and security safeguards for an Online Service meet Customer’s requirements, including any of its security obligations under applicable Data Protection Requirements. Customer acknowledges and agrees that (taking into account the state of the art, the costs of implementation, and the nature, scope, context and purposes of the processing of its Customer Data and Personal Data as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons) the technical and organizational measures and security safeguards implemented and maintained by GitHub provide a level of security appropriate to the risk with respect to its Customer Data and Personal Data. Customer is responsible for implementing and maintaining privacy protections and security measures for components that Customer provides or controls. + +GitHub will provide security compliance reporting such as external SOC1, type 2 and SOC2, type2 audit reports upon Customer request. Customer agrees that any information and audit rights granted by the applicable Data Protection Requirements (including, where applicable, Article 28(3)(h) of the GDPR) will be satisfied by these compliance reports, and will otherwise only arise to the extent that GitHub's provision of a compliance report does not provide sufficient information, or to the extent that Customer must respond to a regulatory or supervisory authority audit or investigation. + +Should Customer be subject to a regulatory or supervisory authority audit or investigation or carry out an audit or investigation in response to a request by a regulatory or supervisory authority that requires participation from GitHub, and Customers’ obligations cannot reasonably be satisfied (where allowable by Customer’s regulators) through audit reports, documentation, or compliance information that GitHub makes generally available to its customers, then GitHub will promptly respond to Customer’s additional instructions and requests for information, in accordance with the following terms and conditions: + +- GitHub will provide access to relevant knowledgeable personnel, documentation, and application software. +- Customer and GitHub will mutually agree in a prior written agreement (email is acceptable) upon the scope, timing, duration, control and evidence requirements, provided that this requirement to agree will not permit GitHub to unreasonably delay its cooperation. +- Customer must ensure its regulator’s use of an independent, accredited third-party audit firm, during regular business hours, with reasonable advance written notice to GitHub, and subject to reasonable confidentiality procedures. Neither Customer, its regulators, nor its regulators’ delegates shall have access to any data from GitHub’s other customers or to GitHub systems or facilities not involved in the Online Services. +- Customer is responsible for all costs and fees related to GitHub’s cooperation with the regulatory audit of Customer, including all reasonable costs and fees for any and all time GitHub expends, in addition to the rates for services performed by GitHub. +- If the report generated from GitHub’s cooperation with the regulatory audit of Customer includes any findings pertaining to GitHub, Customer will share such report, findings, and recommended actions with GitHub where allowed by Customer’s regulators. + +### Security Incident Notification + +If GitHub becomes aware of a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Customer Data or Personal Data processed by GitHub on behalf and in accordance with the documented instructions of Customer in connection with the Online Services (each a "Security Incident"), GitHub will promptly and without undue delay (1) notify Customer of the Security Incident; (2) investigate the Security Incident and provide Customer with detailed information about the Security Incident; (3) take reasonable steps to mitigate the effects and to minimize any damage resulting from the Security Incident. + +Notification(s) of Security Incidents will be delivered to one or more of Customer's administrators by any means GitHub selects, including via email. It is Customer's sole responsibility to ensure it maintains accurate contact information with GitHub and that Customer's administrators monitor for and respond to any notifications. お客様は、お客様に該当するインシデント通知関連法のもとでの義務に従い、セキュリティインシデントに関係する第三者の通知義務を満たす責任を全面的に負います。 + +GitHub will make reasonable efforts to assist Customer in fulfilling Customer's obligation under GDPR Article 33 or other applicable law or regulations to notify the relevant regulatory or supervisory authority and individual data subjects about a Security Incident. + +GitHub’s notification of or response to a Security Incident under this section is not an acknowledgement by GitHub of any fault or liability with respect to the Security Incident. + +Customer must notify GitHub promptly about any possible misuse of its accounts or authentication credentials or any Security Incident related to an Online Service. + +### Data Transfers and Location + +Personal Data that GitHub processes on behalf and in accordance with the documented instructions of Customer in connection with the Online Services may not be transferred to, or stored and processed in a geographic location except in accordance with the DPA Terms and the safeguards provided below in this section. Taking into account such safeguards, Customer appoints GitHub to transfer Personal Data to the United States or any other country in which GitHub or its Subprocessors operate and to store and process Personal Data to provide the Online Services, except as may be described elsewhere in these DPA Terms. + +All transfers of Personal Data out of the European Union, European Economic Area, or Switzerland to provide the Online Services shall be governed by the Standard Contractual Clauses (EU/EEA) in Attachment 1. All transfers of Personal Data out of the United Kingdom to provide the Online Services shall be governed by the Standard Contractual Clauses (UK) in Attachment 2. For the purposes of the Standard Contractual Clauses (UK) in Attachment 2, references to the “European Union,” “EU,” “European Economic Area,” “EEA” or a “Member State” shall be interpreted to refer to the United Kingdom where reasonably necessary and appropriate to give full force and effect to the Standard Contractual Clauses (UK) with respect to transfers of Personal Data from the United Kingdom. This applies regardless of the fact that, effective January 31, 2020, the United Kingdom is no longer a Member State of the European Union or European Economic Area. + +GitHub will abide by the requirements of applicable European Union, European Economic Area, United Kingdom and Swiss data protection law, and other Data Protection Requirements, in each case regarding the transfer of Personal Data to recipients or jurisdictions outside such jurisdiction. All such transfers of Personal Data will, where applicable, be subject to appropriate safeguards as described in Article 46 of the GDPR and such transfers and safeguards will be documented according to Article 30(2) of the GDPR. + +Subject to the safeguards described above, GitHub may transfer, store and otherwise process Personal Data to or in jurisdictions and geographic locations worldwide as it, subject to its sole discretion, considers reasonably necessary in connection with the Online Services. + +### Data Retention and Deletion + +Upon Customer's reasonable request, unless prohibited by law, GitHub will return or destroy all Customer Data and Personal Data processed by GitHub on behalf and in accordance with the documented instructions of Customer in connection with the Online Services at all locations where it is stored within 30 days of the request, provided that it is no longer needed for providing the Online Services or the purposes for which a data subject had authorized the processing of their Personal Data. GitHub may retain Customer Data or Personal Data to the extent required by the applicable Data Protection Requirements or other applicable law, and only to the extent and for such period as required by the applicable Data Protection Requirements or other applicable law, provided that GitHub will ensure that the Customer Data or Personal Data is processed only as necessary for the purpose specified in the applicable Data Protection Requirements or other applicable law and no other purpose, and the Customer Data or Personal Data remains protected by the Applicable Data Protection Requirements or other applicable law. + +### Processor Confidentiality Commitment + +GitHub will ensure that its personnel engaged in the processing of Customer Data and Personal Data on behalf of Customer in connection with the Online Services (i) will process such data only on instructions from Customer or as described in this DPA, and (ii) will be obligated to maintain the confidentiality and security of such data even after their engagement ends. GitHub shall provide periodic and mandatory data privacy and security training and awareness to its employees with access to Customer Data and Personal Data in accordance with applicable Data Protection Requirements or other applicable law and industry standards. + +### Notice and Controls on Use of Subprocessors + +GitHub may hire Subprocessors to provide certain limited or ancillary services on its behalf. Customer consents to this engagement and to GitHub Affiliates as Subprocessors. The above authorizations will constitute Customer’s prior written consent to the subcontracting by GitHub of the processing of Personal Data if such consent is required under applicable law, the Standard Contractual Clauses or the GDPR Related Terms. + +GitHub is responsible for its Subprocessors’ compliance with GitHub’s obligations in this DPA. GitHub makes available information about Subprocessors on the GitHub website https://github.com/subprocessors (or a successor location). When engaging any Subprocessor, GitHub will ensure via a written contract that the Subprocessor may access and use Customer Data or Personal Data only to deliver the services GitHub has retained them to provide and is prohibited from using Customer Data or Personal Data for any other purpose. GitHub will ensure that Subprocessors are bound by written agreements that require them to provide at least the level of data protection required of GitHub by the DPA, including the limitations on disclosure of Personal Data. GitHub agrees to oversee the Subprocessors to ensure that these contractual obligations are met. + +From time to time, GitHub may engage new Subprocessors. GitHub will give Customer notice (by updating the website at https://github.com/github-subprocessors-list (or a successor location) and providing Customer with a mechanism to obtain notice of that update) of any new Subprocessor in advance of providing that Subprocessor with access to Customer Data. If GitHub engages a new Subprocessor for a new Online Service, GitHub will give Customer notice prior to availability of that Online Service. + +If Customer does not approve of a new Subprocessor, then Customer may terminate any subscription for the affected Online Service without penalty by providing, before the end of the relevant notice period, written notice of termination. Customer may also include an explanation of the grounds for non-approval together with the termination notice, in order to permit GitHub to re-evaluate any such new Subprocessor based on the applicable concerns. If the affected Online Service is part of a suite (or similar single purchase of services), then any termination will apply to the entire suite. After termination, GitHub will remove payment obligations for any subscriptions for the terminated Online Service from subsequent invoices to Customer or its reseller. + +### Educational Institutions +If Customer is an educational agency or institution subject to the regulations under the Family Educational Rights and Privacy Act, 20 U.S.C. § 1232g (FERPA), or similar state student or educational privacy laws (collectively “Educational Privacy Laws”), Customer shall not provide Personal Data covered by such Educational Privacy Laws to GitHub without obtaining GitHub’s prior, written and specific consent and entering into a separate agreement with GitHub governing the parties’ rights and obligations with respect to the processing of such Personal Data by GitHub in connection with the Online Services. + +Subject to the above, if Customer intends to provide to GitHub Personal Data covered by FERPA, the parties agree and acknowledge that, for the purposes of this DPA, GitHub is a “school official” with “legitimate educational interests” in the Personal Data, as those terms have been defined under FERPA and its implementing regulations. Customer understands that GitHub may possess limited or no contact information for Customer’s students and students’ parents. Consequently, Customer will be responsible for obtaining any student or parental consent for any end user’s use of the Online Services that may be required by applicable law and to convey notification on behalf of GitHub to students (or, with respect to a student under 18 years of age and not in attendance at a postsecondary institution, to the student’s parent) of any judicial order or lawfully-issued subpoena requiring the disclosure of Personal Data in GitHub’s possession as may be required under applicable law. + +### CJIS Customer Agreement, HIPAA Business Associate, Biometric Data + +Except with GitHub’s prior, written and specific consent, Customer shall not provide to GitHub any Personal Data + +- relating to criminal convictions and offenses or Personal Data collected or otherwise processed by Customer subject to or in connection with FBI Criminal Justice Information Services or the related Security Policy. +- constituting protected health information governed by the privacy, security, and breach notification rules issued by the United States Department of Health and Human Services, Parts 160 and 164 of Title 45 of the Code of Federal Regulations, established pursuant to the Health Insurance Portability and Accountability Act of 1996 (Public Law 104-191) or by state health or medical privacy laws. +- collected as part of a clinical trial or other biomedical research study subject to, or conducted in accordance with, the Federal Policy for the Protection of Human Subjects (Common Rule). +- covered by state, federal or foreign biometric privacy laws or otherwise constituting biometric information including information on an individual’s physical, physiological, biological or behavioral characteristics or information derived from such information that is used or intended to be used, singly or in combination with each other or with other information, to establish individual identity. + +### California Consumer Privacy Act (CCPA) / California Privacy Rights Act (CPRA) + +If and to the extent GitHub is processing Personal Data on behalf and in accordance with the documented instructions of Customer within the scope of the CCPA, GitHub makes the following additional commitments to Customer. GitHub will process the Personal Data on behalf of Customer and will not + +- sell the Personal Data as the term “selling” is defined in the CCPA. - share, rent, release, disclose, disseminate, make available, transfer or otherwise communicate orally, in writing or by electronic or other means, the Personal Data to a third party for cross-context behavioral advertising, whether or not for monetary or other valuable consideration, including transactions for cross-context behavioral advertising in which no money is exchanged. +- retain, use or disclose the Personal Data for any purpose other than for the business purposes specified in the DPA Terms and the GitHub Customer Agreement, including retaining, using or disclosing the Personal Data for a commercial purpose other than the business purposes specified in the DPA Terms or the GitHub Customer Agreement, or as otherwise permitted by the CCPA. +- retain, use or disclose the Personal Data outside of the direct business relationship with Customer. +- combine the Personal Data with personal information that it receives from or on behalf of a third party or collects from California residents, except that GitHub may combine Personal Data to perform any business purpose as permitted by the CCPA or any regulations adopted or issued under the CCPA. + +### How to Contact GitHub + +If Customer believes that GitHub is not adhering to its privacy or security commitments, Customer may contact customer support or use GitHub’s Privacy web form, located at https://support.github.com/contact/privacy. GitHub’s mailing address is: + +**GitHub Privacy**
    GitHub, Inc.
    88 Colin P. Kelly Jr. Street
    San Francisco, California 94107 USA
    + +GitHub B.V. is GitHub’s data protection representative for the European Economic Area. The privacy representative of GitHub B.V. can be reached at the following address: + +**GitHub B.V.**
    Vijzelstraat 68-72
    1017 HL Amsterdam
    The Netherlands
    + +

    Appendix A – Security Safeguards

    + +GitHub has implemented and will maintain for Customer Data and Personal Data processed by GitHub on behalf and in accordance with the documented instructions of Customer in connection with GitHub services the following technical and organizational measures and security safeguards, which in conjunction with the security commitments in this DPA (including the GDPR Related Terms), are GitHub’s only responsibility with respect to the security of that data: + +| Domain | Practices | +| ---------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Organization of Information Security | **Security Ownership**. GitHub has appointed one or more security officers responsible for coordinating and monitoring the security policies and procedures.

    **Security Roles and Responsibilities**. GitHub personnel with access to Customer Data and Personal Data are subject to confidentiality obligations.

    **Risk Management Program**. GitHub performs an annual risk assessment.
    GitHub retains its security documents pursuant to its retention requirements after they are no longer in effect.

    **Vendor Management**. GitHub has a vendor risk assessment process, vendor contract clauses and additional data protection agreements with vendors. | +| Asset Management | **Asset Inventory**. GitHub maintains an inventory of all media on which Customer Data and Personal Data is stored. Access to the inventories of such media is restricted to GitHub personnel authorized to have such access.

    **Asset Handling**
    - GitHub classifies Customer Data and Personal Data to help identify it and to allow for access to it to be appropriately restricted.
    - GitHub communicates employee responsibility and accountability for data protection up to and including cause for termination.
    GitHub personnel must obtain GitHub authorization prior to remotely accessing Customer Data and Personal Data or processing Customer Data and Personal Data outside GitHub’s facilities. | +| Human Resources Security | **Security Training**. GitHub requires all new hires to complete security and privacy awareness training as part of initial on-boarding. Participation in annual training is required for all employees to provide a baseline for security and privacy basics. | +| Physical and Environmental Security | **Physical Access to Facilities**. GitHub limits access to facilities where information systems that process Customer Data and Personal Data are located to identified authorized individuals.

    **Physical Access to Components**. GitHub maintains records of the incoming and outgoing media containing Customer Data, including the kind of media, the authorized sender/recipients, date and time, the number of media and the types of Customer Data and Personal Data they contain.

    **Protection from Disruptions**. GitHub uses a variety of industry standard systems to protect against loss of data due to power supply failure or line interference.

    **Component Disposal**. GitHub uses industry standard processes to delete Customer Data and Personal Data when it is no longer needed. | +| Communications and Operations Management | **Operational Policy**. GitHub maintains security documents describing its security measures and the relevant procedures and responsibilities of its personnel who have access to Customer Data.

    **Data Recovery Procedures**
    - On an ongoing basis, but in no case less frequently than once a week (unless no Customer Data and Personal Data has been updated during that period), GitHub maintains multiple copies of Customer Data and Personal Data from which Customer Data and Personal Data can be recovered.
    - GitHub stores copies of Customer Data and Personal Data and data recovery procedures in a different place from where the primary computer equipment processing the Customer Data and Personal Data is located.
    - GitHub has specific procedures in place governing access to copies of Customer Data.
    - GitHub logs data restoration efforts, including the person responsible, the description of the restored data and where applicable, the person responsible and which data (if any) had to be input manually in the data recovery process.

    **Malicious Software**. GitHub has threat detection controls to help identify and respond to anomalous or suspicious access to Customer Data, including malicious software originating from public networks.

    **Data Beyond Boundaries**
    - GitHub encrypts, or enables Customer to encrypt, Customer Data and Personal Data that is transmitted over public networks.
    - GitHub restricts access to Customer Data and Personal Data in media leaving its facilities.

    **Event Logging**. GitHub logs, or enables Customer to log, access and use of information systems containing Customer Data, registering the access ID, time, authorization granted or denied, and relevant activity. | +| Access Control | **Access Policy**. GitHub maintains a record of security privileges of individuals having access to Customer Data.

    **Access Authorization**
    - GitHub maintains and updates a record of personnel authorized to access GitHub systems that contain Customer Data.
    - GitHub identifies those personnel who may grant, alter or cancel authorized access to data and resources.
    - GitHub ensures that where more than one individual has access to systems containing Customer Data, the individuals have separate identifiers/log-ins where technically and architecturally feasible, and commercially reasonable.

    **Least Privilege**
    - Technical support personnel are only permitted to have access to Customer Data and Personal Data when needed.
    - GitHub restricts access to Customer Data and Personal Data to only those individuals who require such access to perform their job function. GitHub employees are only granted access to production systems based on their role within the organization.

    **Integrity and Confidentiality**

    - GitHub instructs GitHub personnel to disable administrative sessions when computers are left unattended.
    - GitHub stores passwords such that they are encrypted or unintelligible while they are in force.

    **Authentication**
    - GitHub uses industry standard practices to identify and authenticate users who attempt to access information systems.
    - Where authentication mechanisms are based solely on passwords, GitHub requires the password to be at least eight characters long.
    - GitHub ensures that de-activated or expired employee identifiers are not granted to other individuals.
    - GitHub monitors, or enables Customer to monitor, repeated attempts to gain access to the information system using an invalid password.
    - GitHub maintains industry standard procedures to deactivate passwords that have been corrupted or inadvertently disclosed.
    - GitHub uses industry standard password protection practices, including practices designed to maintain the confidentiality and integrity of passwords when they are assigned and distributed, and during storage.

    **Network Design**. GitHub has controls to ensure no systems storing Customer Data and Personal Data are part of the same logical network used for GitHub business operations. | +| Information Security Incident Management | **Incident Response Process**
    - GitHub maintains a record of security incidents with a description of the incidents, the time period, the consequences of the breach, the name of the reporter, and to whom the incident was reported, and details regarding the handling of the incident.
    - In the event that GitHub Security confirms or reasonably suspects that a GitHub.com customer is affected by a data breach, we will notify the customer without undue delay
    - GitHub tracks, or enables Customer to track, disclosures of Customer Data, including what data has been disclosed, to whom, and at what time.

    **Service Monitoring**. GitHub employs a wide range of continuous monitoring solutions for preventing, detecting, and mitigating attacks to the site. | +| Business Continuity Management | - GitHub maintains emergency and contingency plans for the facilities in which GitHub information systems that process Customer Data and Personal Data are located.
    - GitHub’s redundant storage and its procedures for recovering data are designed to attempt to reconstruct Customer Data and Personal Data in its original or last-replicated state from before the time it was lost or destroyed. | + +

    Attachment 1 - The Standard Contractual Clauses (EU/EEA)

    + +### Controller to Processor + +#### SECTION I + +##### Clause 1 + +**Purpose and scope** + +
      +
    1. The purpose of these standard contractual clauses is to ensure compliance with the requirements of Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data (General Data Protection Regulation) for the transfer of personal data to a third country.
      2. +
    2. The Parties: +
        +
      1. the natural or legal person(s), public authority/ies, agency/ies or other body/ies (hereinafter ‘entity/ies’) transferring the personal data, as listed in Annex I.A (hereinafter each ‘data exporter’), and
        2. +
      2. the entity/ies in a third country receiving the personal data from the data exporter, directly or indirectly via another entity also Party to these Clauses, as listed in Annex I.A (hereinafter each ‘data importer’)
        3. +
      + have agreed to these standard contractual clauses (hereinafter: ‘Clauses’).
      3. +
    3. These Clauses apply with respect to the transfer of personal data as specified in Annex I.B.
      4. +
    4. The Appendix to these Clauses containing the Annexes referred to therein forms an integral part of these Clauses.
      5. +
    + +##### Clause 2 + +**Effect and invariability of the Clauses** +
      +
    1. These Clauses set out appropriate safeguards, including enforceable data subject rights and effective legal remedies, pursuant to Article 46(1) and Article 46(2)(c) of Regulation (EU) 2016/679 and, with respect to data transfers from controllers to processors and/or processors to processors, standard contractual clauses pursuant to Article 28(7) of Regulation (EU) 2016/679, provided they are not modified, except to select the appropriate Module(s) or to add or update information in the Appendix. This does not prevent the Parties from including the standard contractual clauses laid down in these Clauses in a wider contract and/or to add other clauses or additional safeguards, provided that they do not contradict, directly or indirectly, these Clauses or prejudice the fundamental rights or freedoms of data subjects.
      2. +
    2. These Clauses are without prejudice to obligations to which the data exporter is subject by virtue of Regulation (EU) 2016/679.
      3. +
    + +##### Clause 3 + +**Third-party beneficiaries** + +
      +
    1. Data subjects may invoke and enforce these Clauses, as third-party beneficiaries, against the data exporter and/or data importer, with the following exceptions:
      2. +
        +
      1. Clause 1, Clause 2, Clause 3, Clause 6, Clause 7;
        2. +
      2. Clause 8.1(b), 8.9(a), (c), (d) and (e);
        3. +
      3. Clause 9(a), (c), (d) and (e);
        4. +
      4. Clause 12(a), (d) and (f);
        5. +
      5. Clause 13;
        6. +
      6. Clause 15.1(c), (d) and (e);
        7. +
      7. Clause 16(e);
        8. +
      8. Clause 18(a) and (b).
        9. +
      +
    2. Paragraph (a) is without prejudice to rights of data subjects under Regulation (EU) 2016/679.
      3. +
    + +##### Clause 4 + +**Interpretation** + +
      +
    1. Where these Clauses use terms that are defined in Regulation (EU) 2016/679, those terms shall have the same meaning as in that Regulation.
      2. +
    2. These Clauses shall be read and interpreted in the light of the provisions of Regulation (EU) 2016/679.
      3. +
    3. These Clauses shall not be interpreted in a way that conflicts with rights and obligations provided for in Regulation (EU) 2016/679.
      4. +
    + +##### Clause 5 + +**Hierarchy** + +In the event of a contradiction between these Clauses and the provisions of related agreements between the Parties, existing at the time these Clauses are agreed or entered into thereafter, these Clauses shall prevail. + +##### Clause 6 + +**Description of the transfer(s)** + +The details of the transfer(s), and in particular the categories of personal data that are transferred and the purpose(s) for which they are transferred, are specified in Annex I.B. + +##### Clause 7 + +**Docking clause** + +
      +
    1. An entity that is not a Party to these Clauses may, with the agreement of the Parties, accede to these Clauses at any time, either as a data exporter or as a data importer, by completing the Appendix and signing Annex I.A.
      2. +
    2. Once it has completed the Appendix and signed Annex I.A, the acceding entity shall become a Party to these Clauses and have the rights and obligations of a data exporter or data importer in accordance with its designation in Annex I.A.
      3. +
    3. The acceding entity shall have no rights or obligations arising under these Clauses from the period prior to becoming a Party.
      4. +
    + +#### SECTION II – OBLIGATIONS OF THE PARTIES + +##### Clause 8 + +**Data protection safeguards** + +The data exporter warrants that it has used reasonable efforts to determine that the data importer is able, through the implementation of appropriate technical and organisational measures, to satisfy its obligations under these Clauses. + +**8.1 Instructions**
      +
    1. The data importer shall process the personal data only on documented instructions from the data exporter. The data exporter may give such instructions throughout the duration of the contract.
      2. +
    2. The data importer shall immediately inform the data exporter if it is unable to follow those instructions.
      3. +
    + +**8.2 Purpose limitation** + +The data importer shall process the personal data only for the specific purpose(s) of the transfer, as set out in Annex I.B, unless on further instructions from the data exporter. + +**8.3 Transparency** + +On request, the data exporter shall make a copy of these Clauses, including the Appendix as completed by the Parties, available to the data subject free of charge. To the extent necessary to protect business secrets or other confidential information, including the measures described in Annex II and personal data, the data exporter may redact part of the text of the Appendix to these Clauses prior to sharing a copy, but shall provide a meaningful summary where the data subject would otherwise not be able to understand the its content or exercise his/her rights. On request, the Parties shall provide the data subject with the reasons for the redactions, to the extent possible without revealing the redacted information. This Clause is without prejudice to the obligations of the data exporter under Articles 13 and 14 of Regulation (EU) 2016/679. + +**8.4 Accuracy** + +If the data importer becomes aware that the personal data it has received is inaccurate, or has become outdated, it shall inform the data exporter without undue delay. In this case, the data importer shall cooperate with the data exporter to erase or rectify the data. + +**8.5 Duration of processing and erasure or return of data** + +Processing by the data importer shall only take place for the duration specified in Annex I.B. After the end of the provision of the processing services, the data importer shall, at the choice of the data exporter, delete all personal data processed on behalf of the data exporter and certify to the data exporter that it has done so, or return to the data exporter all personal data processed on its behalf and delete existing copies. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit return or deletion of the personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process it to the extent and for as long as required under that local law. This is without prejudice to Clause 14, in particular the requirement for the data importer under Clause 14(e) to notify the data exporter throughout the duration of the contract if it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under Clause 14(a). + +**8.6 Security of processing** + +
      +
    1. The data importer and, during transmission, also the data exporter shall implement appropriate technical and organisational measures to ensure the security of the data, including protection against a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access to that data (hereinafter ‘personal data breach’). In assessing the appropriate level of security, the Parties shall take due account of the state of the art, the costs of implementation, the nature, scope, context and purpose(s) of processing and the risks involved in the processing for the data subjects. The Parties shall in particular consider having recourse to encryption or pseudonymisation, including during transmission, where the purpose of processing can be fulfilled in that manner. In case of pseudonymisation, the additional information for attributing the personal data to a specific data subject shall, where possible, remain under the exclusive control of the data exporter. In complying with its obligations under this paragraph, the data importer shall at least implement the technical and organisational measures specified in Annex II. The data importer shall carry out regular checks to ensure that these measures continue to provide an appropriate level of security.
      2. +
    2. The data importer shall grant access to the personal data to members of its personnel only to the extent strictly necessary for the implementation, management and monitoring of the contract. It shall ensure that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.
      3. +
    3. In the event of a personal data breach concerning personal data processed by the data importer under these Clauses, the data importer shall take appropriate measures to address the breach, including measures to mitigate its adverse effects. The data importer shall also notify the data exporter without undue delay after having become aware of the breach. Such notification shall contain the details of a contact point where more information can be obtained, a description of the nature of the breach (including, where possible, categories and approximate number of data subjects and personal data records concerned), its likely consequences and the measures taken or proposed to address the breach including, where appropriate, measures to mitigate its possible adverse effects. Where, and in so far as, it is not possible to provide all information at the same time, the initial notification shall contain the information then available and further information shall, as it becomes available, subsequently be provided without undue delay.
      4. +
    4. The data importer shall cooperate with and assist the data exporter to enable the data exporter to comply with its obligations under Regulation (EU) 2016/679, in particular to notify the competent supervisory authority and the affected data subjects, taking into account the nature of processing and the information available to the data importer.
      5. +
    + +**8.7 Sensitive data** + +Where the transfer involves personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic data, or biometric data for the purpose of uniquely identifying a natural person, data concerning health or a person’s sex life or sexual orientation, or data relating to criminal convictions and offences (hereinafter ‘sensitive data’), the data importer shall apply the specific restrictions and/or additional safeguards described in Annex I.B. + +**8.8 Onward transfers** + +The data importer shall only disclose the personal data to a third party on documented instructions from the data exporter. In addition, the data may only be disclosed to a third party located outside the European Union (1) (in the same country as the data importer or in another third country, hereinafter ‘onward transfer’) if the third party is or agrees to be bound by these Clauses, under the appropriate Module, or if: + +
      +
    1. the onward transfer is to a country benefitting from an adequacy decision pursuant to Article 45 of Regulation (EU) 2016/679 that covers the onward transfer;
      2. +
    2. the third party otherwise ensures appropriate safeguards pursuant to Articles 46 or 47 Regulation of (EU) 2016/679 with respect to the processing in question;
      3. +
    3. the onward transfer is necessary for the establishment, exercise or defence of legal claims in the context of specific administrative, regulatory or judicial proceedings; or
      4. +
    4. the onward transfer is necessary in order to protect the vital interests of the data subject or of another natural person.

      5. + Any onward transfer is subject to compliance by the data importer with all the other safeguards under these Clauses, in particular purpose limitation. +
    + +**8.9 Documentation and compliance** + +
      +
    1. The data importer shall promptly and adequately deal with enquiries from the data exporter that relate to the processing under these Clauses.
      2. +
    2. The Parties shall be able to demonstrate compliance with these Clauses. In particular, the data importer shall keep appropriate documentation on the processing activities carried out on behalf of the data exporter.
      3. +
    3. The data importer shall make available to the data exporter all information necessary to demonstrate compliance with the obligations set out in these Clauses and at the data exporter’s request, allow for and contribute to audits of the processing activities covered by these Clauses, at reasonable intervals or if there are indications of non-compliance. In deciding on a review or audit, the data exporter may take into account relevant certifications held by the data importer.
      4. +
    4. The data exporter may choose to conduct the audit by itself or mandate an independent auditor. Audits may include inspections at the premises or physical facilities of the data importer and shall, where appropriate, be carried out with reasonable notice.
      5. +
    5. The Parties shall make the information referred to in paragraphs (b) and (c), including the results of any audits, available to the competent supervisory authority on request.
      6. +
    + +##### Clause 9 + +**Use of sub-processors** + +
      +
    1. GENERAL WRITTEN AUTHORISATION The data importer has the data exporter’s general authorisation for the engagement of sub-processor(s) from an agreed list. The data importer shall specifically inform the data exporter in writing of any intended changes to that list through the addition or replacement of sub-processors at least 90 days in advance, thereby giving the data exporter sufficient time to be able to object to such changes prior to the engagement of the sub-processor(s). The data importer shall provide the data exporter with the information necessary to enable the data exporter to exercise its right to object.
      2. +
    2. Where the data importer engages a sub-processor to carry out specific processing activities (on behalf of the data exporter), it shall do so by way of a written contract that provides for, in substance, the same data protection obligations as those binding the data importer under these Clauses, including in terms of third-party beneficiary rights for data subjects.(2) The Parties agree that, by complying with this Clause, the data importer fulfils its obligations under Clause 8.8. The data importer shall ensure that the sub-processor complies with the obligations to which the data importer is subject pursuant to these Clauses.
      3. +
    3. The data importer shall provide, at the data exporter’s request, a copy of such a sub-processor agreement and any subsequent amendments to the data exporter. To the extent necessary to protect business secrets or other confidential information, including personal data, the data importer may redact the text of the agreement prior to sharing a copy.
      4. +
    4. The data importer shall remain fully responsible to the data exporter for the performance of the sub-processor’s obligations under its contract with the data importer. The data importer shall notify the data exporter of any failure by the sub-processor to fulfil its obligations under that contract.
      5. +
    5. The data importer shall agree a third-party beneficiary clause with the sub-processor whereby – in the event the data importer has factually disappeared, ceased to exist in law or has become insolvent – the data exporter shall have the right to terminate the sub-processor contract and to instruct the sub-processor to erase or return the personal data.
      6. +
    + +##### Clause 10 + +**Data subject rights** + +
      +
    1. The data importer shall promptly notify the data exporter of any request it has received from a data subject. It shall not respond to that request itself unless it has been authorised to do so by the data exporter.
      2. +
    2. The data importer shall assist the data exporter in fulfilling its obligations to respond to data subjects’ requests for the exercise of their rights under Regulation (EU) 2016/679. In this regard, the Parties shall set out in Annex II the appropriate technical and organisational measures, taking into account the nature of the processing, by which the assistance shall be provided, as well as the scope and the extent of the assistance required.
      3. +
    3. In fulfilling its obligations under paragraphs (a) and (b), the data importer shall comply with the instructions from the data exporter.
      4. +
    + +##### Clause 11 + +**Redress** + +
      +
    1. The data importer shall inform data subjects in a transparent and easily accessible format, through individual notice or on its website, of a contact point authorised to handle complaints. It shall deal promptly with any complaints it receives from a data subject.
      2. +
    2. In case of a dispute between a data subject and one of the Parties as regards compliance with these Clauses, that Party shall use its best efforts to resolve the issue amicably in a timely fashion. The Parties shall keep each other informed about such disputes and, where appropriate, cooperate in resolving them.
      3. +
    3. Where the data subject invokes a third-party beneficiary right pursuant to Clause 3, the data importer shall accept the decision of the data subject to:
      4. +
        +
      1. lodge a complaint with the supervisory authority in the Member State of his/her habitual residence or place of work, or the competent supervisory authority pursuant to Clause 13;
        2. +
      2. refer the dispute to the competent courts within the meaning of Clause 18.
        3. +
      +
    4. The Parties accept that the data subject may be represented by a not-for-profit body, organisation or association under the conditions set out in Article 80(1) of Regulation (EU) 2016/679.
      5. +
    5. The data importer shall abide by a decision that is binding under the applicable EU or Member State law.
      6. +
    6. The data importer agrees that the choice made by the data subject will not prejudice his/her substantive and procedural rights to seek remedies in accordance with applicable laws.
      7. +
    + +##### Clause 12 + +**Liability** + +
      +
    1. Each Party shall be liable to the other Party/ies for any damages it causes the other Party/ies by any breach of these Clauses.
      2. +
    2. The data importer shall be liable to the data subject, and the data subject shall be entitled to receive compensation, for any material or non-material damages the data importer or its sub-processor causes the data subject by breaching the third-party beneficiary rights under these Clauses.
      3. +
    3. Notwithstanding paragraph (b), the data exporter shall be liable to the data subject, and the data subject shall be entitled to receive compensation, for any material or non-material damages the data exporter or the data importer (or its sub-processor) causes the data subject by breaching the third-party beneficiary rights under these Clauses. This is without prejudice to the liability of the data exporter and, where the data exporter is a processor acting on behalf of a controller, to the liability of the controller under Regulation (EU) 2016/679 or Regulation (EU) 2018/1725, as applicable.
      4. +
    4. The Parties agree that if the data exporter is held liable under paragraph (c) for damages caused by the data importer (or its sub-processor), it shall be entitled to claim back from the data importer that part of the compensation corresponding to the data importer’s responsibility for the damage.
      5. +
    5. Where more than one Party is responsible for any damage caused to the data subject as a result of a breach of these Clauses, all responsible Parties shall be jointly and severally liable and the data subject is entitled to bring an action in court against any of these Parties.
      6. +
    6. The Parties agree that if one Party is held liable under paragraph (e), it shall be entitled to claim back from the other Party/ies that part of the compensation corresponding to its/their responsibility for the damage.
      7. +
    7. The data importer may not invoke the conduct of a sub-processor to avoid its own liability.
      8. +
    + +##### Clause 13 + +**Supervision** + +
      +
    1. [Where the data exporter is established in an EU Member State:] The supervisory authority with responsibility for ensuring compliance by the data exporter with Regulation (EU) 2016/679 as regards the data transfer, as indicated in Annex I.C, shall act as competent supervisory authority.

      + [Where the data exporter is not established in an EU Member State, but falls within the territorial scope of application of Regulation (EU) 2016/679 in accordance with its Article 3(2) and has appointed a representative pursuant to Article 27(1) of Regulation (EU) 2016/679:] The supervisory authority of the Member State in which the representative within the meaning of Article 27(1) of Regulation (EU) 2016/679 is established, as indicated in Annex I.C, shall act as competent supervisory authority.

      + [Where the data exporter is not established in an EU Member State, but falls within the territorial scope of application of Regulation (EU) 2016/679 in accordance with its Article 3(2) without however having to appoint a representative pursuant to Article 27(2) of Regulation (EU) 2016/679:] The supervisory authority of one of the Member States in which the data subjects whose personal data is transferred under these Clauses in relation to the offering of goods or services to them, or whose behaviour is monitored, are located, as indicated in Annex I.C, shall act as competent supervisory authority.

      2. +
    2. The data importer agrees to submit itself to the jurisdiction of and cooperate with the competent supervisory authority in any procedures aimed at ensuring compliance with these Clauses. In particular, the data importer agrees to respond to enquiries, submit to audits and comply with the measures adopted by the supervisory authority, including remedial and compensatory measures. It shall provide the supervisory authority with written confirmation that the necessary actions have been taken.
      3. +
    + +#### SECTION III – LOCAL LAWS AND OBLIGATIONS IN CASE OF ACCESS BY PUBLIC AUTHORITIES + +##### Clause 14 + +**Local laws and practices affecting compliance with the Clauses** + +
      +
    1. The Parties warrant that they have no reason to believe that the laws and practices in the third country of destination applicable to the processing of the personal data by the data importer, including any requirements to disclose personal data or measures authorising access by public authorities, prevent the data importer from fulfilling its obligations under these Clauses. This is based on the understanding that laws and practices that respect the essence of the fundamental rights and freedoms and do not exceed what is necessary and proportionate in a democratic society to safeguard one of the objectives listed in Article 23(1) of Regulation (EU) 2016/679, are not in contradiction with these Clauses.
      2. +
    2. The Parties declare that in providing the warranty in paragraph (a), they have taken due account in particular of the following elements:
      3. +
        +
      1. the specific circumstances of the transfer, including the length of the processing chain, the number of actors involved and the transmission channels used; intended onward transfers; the type of recipient; the purpose of processing; the categories and format of the transferred personal data; the economic sector in which the transfer occurs; the storage location of the data transferred;
        2. +
      2. the laws and practices of the third country of destination– including those requiring the disclosure of data to public authorities or authorising access by such authorities – relevant in light of the specific circumstances of the transfer, and the applicable limitations and safeguards (3);
        3. +
      3. any relevant contractual, technical or organisational safeguards put in place to supplement the safeguards under these Clauses, including measures applied during transmission and to the processing of the personal data in the country of destination.
        4. +
      +
    3. The data importer warrants that, in carrying out the assessment under paragraph (b), it has made its best efforts to provide the data exporter with relevant information and agrees that it will continue to cooperate with the data exporter in ensuring compliance with these Clauses.
      4. +
    4. The Parties agree to document the assessment under paragraph (b) and make it available to the competent supervisory authority on request.
      5. +
    5. The data importer agrees to notify the data exporter promptly if, after having agreed to these Clauses and for the duration of the contract, it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under paragraph (a), including following a change in the laws of the third country or a measure (such as a disclosure request) indicating an application of such laws in practice that is not in line with the requirements in paragraph (a).
      6. +
    6. Following a notification pursuant to paragraph (e), or if the data exporter otherwise has reason to believe that the data importer can no longer fulfil its obligations under these Clauses, the data exporter shall promptly identify appropriate measures (e.g. technical or organisational measures to ensure security and confidentiality) to be adopted by the data exporter and/or data importer to address the situation. The data exporter shall suspend the data transfer if it considers that no appropriate safeguards for such transfer can be ensured, or if instructed by the competent supervisory authority to do so. In this case, the data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses. If the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise. Where the contract is terminated pursuant to this Clause, Clause 16(d) and (e) shall apply.
      7. +
    + +##### Clause 15 + +**Obligations of the data importer in case of access by public authorities** + +**15.1 Notification** + +
      +
    1. The data importer agrees to notify the data exporter and, where possible, the data subject promptly (if necessary with the help of the data exporter) if it:
      2. +
        +
      1. receives a legally binding request from a public authority, including judicial authorities, under the laws of the country of destination for the disclosure of personal data transferred pursuant to these Clauses; such notification shall include information about the personal data requested, the requesting authority, the legal basis for the request and the response provided; or
        2. +
      2. becomes aware of any direct access by public authorities to personal data transferred pursuant to these Clauses in accordance with the laws of the country of destination; such notification shall include all information available to the importer.
        3. +
      +
    2. If the data importer is prohibited from notifying the data exporter and/or the data subject under the laws of the country of destination, the data importer agrees to use its best efforts to obtain a waiver of the prohibition, with a view to communicating as much information as possible, as soon as possible. The data importer agrees to document its best efforts in order to be able to demonstrate them on request of the data exporter.
      3. +
    3. Where permissible under the laws of the country of destination, the data importer agrees to provide the data exporter, at regular intervals for the duration of the contract, with as much relevant information as possible on the requests received (in particular, number of requests, type of data requested, requesting authority/ies, whether requests have been challenged and the outcome of such challenges, etc.).
      4. +
    4. The data importer agrees to preserve the information pursuant to paragraphs (a) to (c) for the duration of the contract and make it available to the competent supervisory authority on request.
      5. +
    5. Paragraphs (a) to (c) are without prejudice to the obligation of the data importer pursuant to Clause 14(e) and Clause 16 to inform the data exporter promptly where it is unable to comply with these Clauses.
      6. +
    + +**15.2 Review of legality and data minimisation** + +
      +
    1. The data importer agrees to review the legality of the request for disclosure, in particular whether it remains within the powers granted to the requesting public authority, and to challenge the request if, after careful assessment, it concludes that there are reasonable grounds to consider that the request is unlawful under the laws of the country of destination, applicable obligations under international law and principles of international comity. The data importer shall, under the same conditions, pursue possibilities of appeal. When challenging a request, the data importer shall seek interim measures with a view to suspending the effects of the request until the competent judicial authority has decided on its merits. It shall not disclose the personal data requested until required to do so under the applicable procedural rules. These requirements are without prejudice to the obligations of the data importer under Clause 14(e).
      2. +
    2. The data importer agrees to document its legal assessment and any challenge to the request for disclosure and, to the extent permissible under the laws of the country of destination, make the documentation available to the data exporter. It shall also make it available to the competent supervisory authority on request.
      3. +
    3. The data importer agrees to provide the minimum amount of information permissible when responding to a request for disclosure, based on a reasonable interpretation of the request.
      4. +
    + +#### SECTION IV – FINAL PROVISIONS + +##### Clause 16 + +**Non-compliance with the Clauses and termination** + +
      +
    1. The data importer shall promptly inform the data exporter if it is unable to comply with these Clauses, for whatever reason.
      2. +
    2. In the event that the data importer is in breach of these Clauses or unable to comply with these Clauses, the data exporter shall suspend the transfer of personal data to the data importer until compliance is again ensured or the contract is terminated. This is without prejudice to Clause 14(f).
      3. +
    3. The data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses, where:
      4. +
        +
      1. the data exporter has suspended the transfer of personal data to the data importer pursuant to paragraph (b) and compliance with these Clauses is not restored within a reasonable time and in any event within one month of suspension;
        2. +
      2. the data importer is in substantial or persistent breach of these Clauses; or
        3. +
      3. the data importer fails to comply with a binding decision of a competent court or supervisory authority regarding its obligations under these Clauses.
        4. +

      + In these cases, it shall inform the competent supervisory authority of such non-compliance. Where the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise. +
    4. Personal data that has been transferred prior to the termination of the contract pursuant to paragraph (c) shall at the choice of the data exporter immediately be returned to the data exporter or deleted in its entirety. The same shall apply to any copies of the data. The data importer shall certify the deletion of the data to the data exporter. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit the return or deletion of the transferred personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process the data to the extent and for as long as required under that local law.
      5. +
    5. Either Party may revoke its agreement to be bound by these Clauses where (i) the European Commission adopts a decision pursuant to Article 45(3) of Regulation (EU) 2016/679 that covers the transfer of personal data to which these Clauses apply; or (ii) Regulation (EU) 2016/679 becomes part of the legal framework of the country to which the personal data is transferred. This is without prejudice to other obligations applying to the processing in question under Regulation (EU) 2016/679.
      6. +
    + +##### Clause 17 + +**Governing law** + +These Clauses shall be governed by the law of one of the EU Member States, provided such law allows for third-party beneficiary rights. The Parties agree that this shall be the law of the Netherlands. + +##### Clause 18 + +**Choice of forum and jurisdiction** + +
      +
    1. Any dispute arising from these Clauses shall be resolved by the courts of an EU Member State.
      2. +
    2. The Parties agree that those shall be the courts of the Netherlands.
      3. +
    3. A data subject may also bring legal proceedings against the data exporter and/or data importer before the courts of the Member State in which he/she has his/her habitual residence.
      4. +
    4. The Parties agree to submit themselves to the jurisdiction of such courts.
      5. +
    + +## ANNEX I + +**to the Standard Contractual Clauses (EU/EEA)** + +### A. LIST OF PARTIES + +**Data exporter(s)**: Customer is the data exporter
    Name: see GitHub Customer Agreement
    Address: see GitHub Customer Agreement
    Contact person’s name, position and contact details: see GitHub Customer Agreement
    Activities relevant to the data transferred under these Clauses:
    The data exporter is a user of Online Services or Professional Services as defined in the DPA and GitHub Customer Agreement.
    Signature and date: see GitHub Customer Agreement (the DPA and the Standard Contractual Clauses (EU/EEA) are incorporated into the GitHub Customer Agreement
    Role (controller/processor): controller (unless otherwise agreed in the Customer Agreement).
    + +**Data importer(s)**:
    Name: GitHub, Inc.
    Address: 88 Colin P Kelly Jr St, San Francisco, CA 94107, USA
    Contact person’s name, position and contact details: Frances Wiet, Head of Privacy, fwiet@github.com
    Activities relevant to the data transferred under these Clauses:
    GitHub, Inc. is a global producer of software and services
    Signature and date: see GitHub Customer Agreement (the DPA and the Standard Contractual Clauses (EU/EEA) are incorporated into the GitHub Customer Agreement)
    Role (controller/processor): processor or, depending on the agreements set forth in the Customer Agreement, subprocessor. + +### B. DESCRIPTION OF TRANSFER + +_Categories of data subjects whose personal data is transferred:_ + +Data subjects include the data exporter’s representatives and end-users including employees, contractors, collaborators, and customers of the data exporter. Data subjects may also include individuals attempting to communicate or transfer personal data to users of the services provided by data importer. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following types of data subjects in the personal data: +- データ輸出者の従業員、請負業者、派遣労働者 (現在、過去、見込みを含む)。 +- データ輸出者のコラボレータ/担当者 (自然人) または従業員、請負業者または法人コラボレータ/担当者の派遣労働者 (現在、見込み、過去を含む)。 +- Users and other data subjects that are users of data exporter's services; +- Partners, stakeholders or individuals who actively collaborate, communicate or otherwise interact with employees of the data exporter and/or use communication tools such as apps and websites provided by the data exporter. + +_Categories of personal data transferred:_ + +The personal data transferred that is included in e-mail, documents and other data in an electronic form in the context of the Online Services or Professional Services. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following categories in the personal data: +- Basic personal data (for example place of birth, street name and house number (address), postal code, city of residence, country of residence, mobile phone number, first name, last name, initials, email address, gender, date of birth); +- Authentication data (for example user name, password or PIN code, security question, audit trail); +- Contact information (for example addresses, email, phone numbers, social media identifiers; emergency contact details); +- Unique identification numbers and signatures (for example IP addresses, employee number, student number); +- Pseudonymous identifiers; +- Photos, video and audio; +- Internet activity (for example browsing history, search history, reading and viewing activities); +- Device identification (for example IMEI-number, SIM card number, MAC address); +- Profiling (for example based on observed criminal or anti-social behavior or pseudonymous profiles based on visited URLs, click streams, browsing logs, IP-addresses, domains, apps installed, or profiles based on marketing preferences); +- Special categories of data as voluntarily provided by data subjects (for example racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health, data concerning a natural person’s sex life or sexual orientation, or data relating to criminal convictions or offences); or +- Any other personal data identified in Article 4 of the GDPR. + +_**Sensitive data** transferred (if applicable) and applied restrictions or safeguards that fully take into consideration the nature of the data and the risks involved, such as for instance strict purpose limitation, access restrictions (including access only for staff having followed specialised training), keeping a record of access to the data, restrictions for onward transfers or additional security measures:_
    GitHub does not request or otherwise ask for sensitive data and receives such data only if and when customers or data subjects decide to provide it. + +_**The frequency of the transfer** (e.g. whether the data is transferred on a one-off or continuous basis):_ + +Continuous as part of the Online Services or Professional Services. + +_**Nature of the processing:**_ + +The personal data transferred will be subject to the following basic processing activities: +
      +
    1. Duration and Object of Data Processing. The duration of data processing shall be for the term designated under the applicable GitHub Customer Agreement between data exporter and the data importer. The objective of the data processing is the performance of Online Services and Professional Services.
      2. +
    2. Personal Data Access. For the term designated under the applicable GitHub Customer Agreement, data importer will, at its election and as necessary under applicable law, either: (1) provide data exporter with the ability to correct, delete, or block personal data, or (2) make such corrections, deletions, or blockages on its behalf.
      3. +
    3. Data Exporter’s Instructions. For Online Services and Professional Services, data importer will only act upon data exporter’s instructions.
      4. +
    + +_Purpose(s) of the data transfer and further processing:_ + +The scope and purpose of processing personal data is described in the “Processing of Personal Data; GDPR” section of the DPA. The data importer operates a global network of data centers and management/support facilities, and processing may take place in any jurisdiction where data importer or its sub-processors operate such facilities in accordance with the “Security Practices and Policies” section of the DPA. + +_The period for which the personal data will be retained, or, if that is not possible, the criteria used to determine that period:_ + +Upon expiration or termination of data exporter’s use of Online Services or Professional Services, it may extract personal data and data importer will delete personal data, each in accordance with the DPA Terms applicable to the agreement. + +_For transfers to (sub-) processors, also specify subject matter, nature and duration of the processing:_ + +In accordance with the DPA, the data importer may hire other companies to provide limited services on data importer’s behalf, such as providing customer support. Any such subcontractors will be permitted to obtain personal data only to deliver the services the data importer has retained them to provide, and they are prohibited from using personal data for any other purpose. Unless a particular subcontractor is replaced ahead of time, the processing will be for the term designated under the applicable GitHub Customer Agreement between data exporter and data importer. + +### C. COMPETENT SUPERVISORY AUTHORITY + +_Identify the competent supervisory authority/ies in accordance with Clause 13:_ + +The supervisory authority with responsibility for ensuring compliance by the data exporter with Regulation (EU) 2016/679.   +## ANNEX II + +**to the Standard Contractual Clauses (EU/EEA)** + +**TECHNICAL AND ORGANISATIONAL MEASURES INCLUDING TECHNICAL AND ORGANISATIONAL MEASURES TO ENSURE THE SECURITY OF THE DATA** + +_Description of the technical and organisational measures implemented by the data importer(s) (including any relevant certifications) to ensure an appropriate level of security, taking into account the nature, scope, context and purpose of the processing, and the risks for the rights and freedoms of natural persons._ + +
      +
    1. Data Security Certifications. Data importer holds the following data security certifications:
      2. +
        +
      • SOC 1, Type 2;
        • +
      • SOC 2, Type 2;
        • +
      • NIST, to the extent incorporated for FedRAMP Low-Impact / Tailored ATO.
        • +
      +
    2. Personnel. Data importer’s personnel will not process personal data without authorization. Personnel are obligated to maintain the confidentiality of any such personal data and this obligation continues even after their engagement ends.
      3. +
    3. Data Privacy Contact. The data privacy officer of the data importer can be reached at the following address:

      + GitHub, Inc.
      + Attn: Privacy
      + 88 Colin P. Kelly Jr. Street
      + San Francisco, California 94107 USA

      4. +
    4. Technical and Organization Measures. The data importer has implemented and will maintain appropriate technical and organizational measures, internal controls, and information security routines intended to protect personal data, as defined in the Security Practices and Policies section of the DPA, against accidental loss, destruction, or alteration; unauthorized disclosure or access; or unlawful destruction as follows: The technical and organizational measures, internal controls, and information security routines set forth in the Data Security section of the DPA are hereby incorporated into this Annex II to Attachment 1 by this reference and are binding on the data importer as if they were set forth in this Annex 2 to Attachment 1 in their entirety.
      5. +
    + +_For transfers to (sub-) processors, also describe the specific technical and organisational measures to be taken by the (sub-) processor to be able to provide assistance to the controller and, for transfers from a processor to a sub-processor, to the data exporter:_ + +**Vendor management program - third-party risk program** + +The data importer has a vendor risk assessment process, vendor contract clauses and additional data protection agreements with vendors. Vendors undergo reassessment when a new business use case is requested. The data importer’s vendor risk program is structured so all of data importer’s vendors' risk assessments are refreshed two years from the last review date. + +Vendors deemed high risk, such as data center providers or other vendors storing or processing data in scope for the data importer’s regulatory or contractual requirements, undergo reassessment annually. + +## ANNEX III + +**to the Standard Contractual Clauses (EU/EEA)** + +**Additional Safeguards Addendum** + +By this Additional Safeguards Addendum to Standard Contractual Clauses (EU/EEA) (this “Addendum”), GitHub, Inc. (“GitHub”) provides additional safeguards to Customer and additional redress to the data subjects to whom Customer’s personal data relates. + +This Addendum supplements and is made part of, but is not in variation or modification of, the Standard Contractual Clauses (EU/EEA). + +
      +
    1. Challenges to Orders. In addition to Clause 15.1 of the Standard Contractual Clauses (EU/EEA), in the event GitHub receives an order from any third party for compelled disclosure of any personal data that has been transferred under the Standard Contractual Clauses (EU/EEA), GitHub shall:
      2. +
        +
      1. use every reasonable effort to redirect the third party to request data directly from Customer;
        2. +
      2. promptly notify Customer, unless prohibited under the law applicable to the requesting third party, and, if prohibited from notifying Customer, use all lawful efforts to obtain the right to waive the prohibition in order to communicate as much information to Customer as soon as possible; and
        3. +
      3. use all lawful efforts to challenge the order for disclosure on the basis of any legal deficiencies under the laws of the requesting party or any relevant conflicts with the law of the European Union or applicable Member State law.
        4. +

      + For purpose of this section, lawful efforts do not include actions that would result in civil or criminal penalty such as contempt of court under the laws of the relevant jurisdiction. +
    2. Indemnification of Data Subjects. Subject to Sections 3 and 4, GitHub shall indemnify a data subject for any material or non-material damage to the data subject caused by GitHub’s disclosure of personal data of the data subject that has been transferred under the Standard Contractual Clauses (EU/EEA) in response to an order from a non-EU/EEA government body or law enforcement agency (a “Relevant Disclosure”). Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under this Section 2 to the extent the data subject has already received compensation for the same damage, whether from GitHub or otherwise.
      3. +
    3. Conditions of Indemnification. Indemnification under Section 2 is conditional upon the data subject establishing, to GitHub’s reasonable satisfaction, that:
      4. +
        +
      1. GitHub engaged in a Relevant Disclosure;
        2. +
      2. the Relevant Disclosure was the basis of an official proceeding by the non-EU/EEA government body or law enforcement agency against the data subject; and
        3. +
      3. the Relevant Disclosure directly caused the data subject to suffer material or non-material damage.
        4. +

      + The data subject bears the burden of proof with respect to conditions a. though c.
      + Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under Section 2 if GitHub establishes that the Relevant Disclosure did not violate its obligations under Chapter V of the GDPR.
      +
    4. Scope of Damages. Indemnification under Section 2 is limited to material and non-material damages as provided in the GDPR and excludes consequential damages and all other damages not resulting from GitHub’s infringement of the GDPR.
      5. +
    5. Exercise of Rights. Rights granted to data subjects under this Addendum may be enforced by the data subject against GitHub irrespective of any restriction in Clauses 3 or 12 of the Standard Contractual Clauses (EU/EEA). The data subject may only bring a claim under this Addendum on an individual basis, and not part of a class, collective, group or representative action. Rights granted to data subjects under this Addendum are personal to the data subject and may not be assigned.
      6. +
    6. Notice of Change. In addition to Clause 14 of the Standard Contractual Clauses (EU/EEA), GitHub agrees and warrants that it has no reason to believe that the legislation applicable to it or its sub-processors, including in any country to which personal data is transferred either by itself or through a sub-processor, prevents it from fulfilling the instructions received from the data exporter and its obligations under this Addendum or the Standard Contractual Clauses (EU/EEA) and that in the event of a change in this legislation which is likely to have a substantial adverse effect on the warranties and obligations provided by this Addendum or the Standard Contractual Clauses (EU/EEA), it will promptly notify the change to Customer as soon as it is aware, in which case Customer is entitled to suspend the transfer of data and/or terminate the contract.
      7. +
    7. Termination. This Addendum shall automatically terminate if the European Commission, a competent Member State supervisory authority, or an EU or competent Member State court approves a different lawful transfer mechanism that would be applicable to the data transfers covered by the Standard Contractual Clauses (EU/EEA) (and if such mechanism applies only to some of the data transfers, this Addendum will terminate only with respect to those transfers) and that does not require the additional safeguards set forth in this Addendum.
      8. +
    + +

    Attachment 2 – The Standard Contractual Clauses (UK)

    + +Execution of the GitHub Customer Agreement by Customer includes execution of this Attachment 2, which is countersigned by GitHub, Inc. + +本標準契約条項の使用に規制当局の承認が必要な国においては、お客様が規制当局から必要な証人を得ていない限り、欧州委員会2010/87/EU (2010年2月) に基づき、当該国からのデータ輸出を合法とするにあたり、本標準契約条項に依拠することはできません。 + +Beginning May 25, 2018 and thereafter, references to various Articles from the Directive 95/46/EC in the Standard Contractual Clauses below will be treated as references to the relevant and appropriate Articles in the GDPR. + +For the purposes of Article 26(2) of Directive 95/46/EC for the transfer of personal data to processors established in third countries which do not ensure an adequate level of data protection, Customer (as data exporter) and GitHub, Inc. (as data importer, whose signature appears below), each a “party,” together “the parties,” have agreed on the following Contractual Clauses (the “Clauses” or “Standard Contractual Clauses”) in order to adduce adequate safeguards with respect to the protection of privacy and fundamental rights and freedoms of individuals for the transfer by the data exporter to the data importer of the personal data specified in Appendix 1. + +### 第1条: 定義 + +
      +
    1. 'personal data', 'special categories of data', 'process/processing', 'controller', 'processor', 'data subject' and 'supervisory authority' shall have the same meaning as in Directive 95/46/EC of the European Parliament and of the Council of 24 October 1995 on the protection of individuals with regard to the processing of personal data and on the free movement of such data;
      2. +
    2. 'the data exporter' means the controller who transfers the personal data;
      3. +
    3. 'the data importer' means the processor who agrees to receive from the data exporter personal data intended for processing on his behalf after the transfer in accordance with his instructions and the terms of the Clauses and who is not subject to a third country's system ensuring adequate protection within the meaning of Article 25(1) of Directive 95/46/EC;
      4. +
    4. 'the subprocessor' means any processor engaged by the data importer or by any other subprocessor of the data importer who agrees to receive from the data importer or from any other subprocessor of the data importer personal data exclusively intended for processing activities to be carried out on behalf of the data exporter after the transfer in accordance with his instructions, the terms of the Clauses and the terms of the written subcontract;
      5. +
    5. 'the applicable data protection law' means the legislation protecting the fundamental rights and freedoms of individuals and, in particular, their right to privacy with respect to the processing of personal data applicable to a data controller in the Member State in which the data exporter is established;
      6. +
    6. 'technical and organisational security measures' means those measures aimed at protecting personal data against accidental or unlawful destruction or accidental loss, alteration, unauthorised disclosure or access, in particular where the processing involves the transmission of data over a network, and against all other unlawful forms of processing.
      7. +
    + +### 第2条: 転送の詳細 + +転送の詳細、特に適用される特別なカテゴリの個人データについては、本条項と不可分である、下記の添付文書1に明記されています。 + +### 第3条: 第三者受益者条項 + +
      +
    1. データ主体は、データ輸出者に対して、本条項、第4条4 (b) から (i)、第5条 (a) から (e) および (g) から (j)、第6条 (1) および (2)、第7条、第8条 (2)、ならびに第9条から第12条を、第三者受益者として執行することができます。
      2. +
    2. データ主体は、データ輸出者が事実上存在しなくなった場合、または法律上存在しなくなった場合、 データ輸入者に対して本条項、第5条 (a) から (e) および (g)、第6条、第7条、第条8 (2)、ならびに第9条から第12条を執行することができます。ただし、後継法人が契約または法律の定めによりデータ輸出者の法的義務をすべて引き受けた場合を除きます。この場合、後継法人がデータ輸出者の権利および義務を引き受けることとなり、データ主体はかかる法人に対して上記条項を執行できます。
      3. +
    3. データ主体は、サブプロセッサーとデータ輸入者の双方が事実上存在しなくなった場合、法律上存在しなくなった場合、または、債務超過に陥った場合、サブプロセッサーに対して本条項、第5条 (a) から (e) および (g)、第6条、第7条、第条8 (2)、ならびに第9条から第12条を執行することができます。ただし、後継法人が契約または法律の定めによりデータ輸出者の法的義務をすべて引き受けた場合を除きます。この場合、後継法人がデータ輸出者の権利および義務を引き受けることとなり、データ主体はかかる法人に対して上記条項を執行できます。 サブプロセッサーの第三者に対するかかる責任は、かかる条項に基づく自らの処理操作に限定されるものとします。
      4. +
    4. 両当事者は、データ主体が特に希望しており、かつ国家の法令により許可されている場合、組合またははその他組織体がデータ主体を代表することに反対しないものとします。
      5. +
    + +### 第4条: データ輸出者の義務 + +データ輸出者は、以下のことに同意し、保証します。 + +
      +
    1. that the processing, including the transfer itself, of the personal data has been and will continue to be carried out in accordance with the relevant provisions of the applicable data protection law (and, where applicable, has been notified to the relevant authorities of the Member State where the data exporter is established) and does not violate the relevant provisions of that State;
      2. +
    2. that it has instructed and throughout the duration of the personal data processing services will instruct the data importer to process the personal data transferred only on the data exporter's behalf and in accordance with the applicable data protection law and the Clauses;
      3. +
    3. that the data importer will provide sufficient guarantees in respect of the technical and organisational security measures specified in Appendix 2 below;
      4. +
    4. that after assessment of the requirements of the applicable data protection law, the security measures are appropriate to protect personal data against accidental or unlawful destruction or accidental loss, alteration, unauthorised disclosure or access, in particular where the processing involves the transmission of data over a network, and against all other unlawful forms of processing, and that these measures ensure a level of security appropriate to the risks presented by the processing and the nature of the data to be protected having regard to the state of the art and the cost of their implementation;
      5. +
    5. that it will ensure compliance with the security measures;
      6. +
    6. that, if the transfer involves special categories of data, the data subject has been informed or will be informed before, or as soon as possible after, the transfer that its data could be transmitted to a third country not providing adequate protection within the meaning of Directive 95/46/EC;
      7. +
    7. to forward any notification received from the data importer or any subprocessor pursuant to Clause 5(b) and Clause 8(3) to the data protection supervisory authority if the data exporter decides to continue the transfer or to lift the suspension;
      8. +
    8. to make available to the data subjects upon request a copy of the Clauses, with the exception of Appendix 2, and a summary description of the security measures, as well as a copy of any contract for subprocessing services which has to be made in accordance with the Clauses, unless the Clauses or the contract contain commercial information, in which case it may remove such commercial information;
      9. +
    9. that, in the event of subprocessing, the processing activity is carried out in accordance with Clause 11 by a subprocessor providing at least the same level of protection for the personal data and the rights of data subject as the data importer under the Clauses; and
      10. +
    10. that it will ensure compliance with Clause 4(a) to (i).
      11. +
    + +### 第5条: データ輸入者の義務 + +データ輸入者は、以下のことに同意し、保証します。 + +
      +
    1. to process the personal data only on behalf of the data exporter and in compliance with its instructions and the Clauses; if it cannot provide such compliance for whatever reasons, it agrees to inform promptly the data exporter of its inability to comply, in which case the data exporter is entitled to suspend the transfer of data and/or terminate the contract;
      2. +
    2. that it has no reason to believe that the legislation applicable to it prevents it from fulfilling the instructions received from the data exporter and its obligations under the contract and that in the event of a change in this legislation which is likely to have a substantial adverse effect on the warranties and obligations provided by the Clauses, it will promptly notify the change to the data exporter as soon as it is aware, in which case the data exporter is entitled to suspend the transfer of data and/or terminate the contract;
      3. +
    3. that it has implemented the technical and organisational security measures specified in Appendix 2 before processing the personal data transferred;
      4. +
    4. that it will promptly notify the data exporter about:
      5. +
        +
      1. any legally binding request for disclosure of the personal data by a law enforcement authority unless otherwise prohibited, such as a prohibition under criminal law to preserve the confidentiality of a law enforcement investigation,
        2. +
      2. any accidental or unauthorised access, and
        3. +
      3. any request received directly from the data subjects without responding to that request, unless it has been otherwise authorised to do so;
        4. +
      + to deal promptly and properly with all inquiries from the data exporter relating to its processing of the personal data subject to the transfer and to abide by the advice of the supervisory authority with regard to the processing of the data transferred; + at the request of the data exporter to submit its data processing facilities for audit of the processing activities covered by the Clauses which shall be carried out by the data exporter or an inspection body composed of independent members and in possession of the required professional qualifications bound by a duty of confidentiality, selected by the data exporter, where applicable, in agreement with the supervisory authority; +
    5. to make available to the data subject upon request a copy of the Clauses, or any existing contract for subprocessing, unless the Clauses or contract contain commercial information, in which case it may remove such commercial information, with the exception of Appendix 2 which shall be replaced by a summary description of the security measures in those cases where the data subject is unable to obtain a copy from the data exporter;
      6. +
    6. that, in the event of subprocessing, it has previously informed the data exporter and obtained its prior written consent;
      7. +
    7. that the processing services by the subprocessor will be carried out in accordance with Clause 11; and
      8. +
    8. to send promptly a copy of any subprocessor agreement it concludes under the Clauses to the data exporter.
      9. +
    + +### 第6条: 責任 + +
      +
    1. 両当事者は、当事者のいずれかまたは副処理者が本契約条項の第3条または第11条に違反したことにより損害を被ったデータ主体が、当該損害について、データ輸出者から賠償を受ける権利を有することに同意します。
      2. + +
    2. If a data subject is not able to bring a claim for compensation in accordance with paragraph 1 against the data exporter, arising out of a breach by the data importer or his subprocessor of any of their obligations referred to in Clause 3 or in Clause 11, because the data exporter has factually disappeared or ceased to exist in law or has become insolvent, the data importer agrees that the data subject may issue a claim against the data importer as if it were the data exporter, unless any successor entity has assumed the entire legal obligations of the data exporter by contract of by operation of law, in which case the data subject can enforce its rights against such entity.

      + The data importer may not rely on a breach by a subprocessor of its obligations in order to avoid its own liabilities.
      3. + +
    3. データ輸出者およびデータ輸入者の双方が事実上消滅し、もしくは法律上存在しなくなった場合、またはこれらの双方が支払不能に陥ったために、データ主体が、副処理者が第3条または第11条に規定された義務に違反したことによるする請求について、第1項および第2項に規定されたデータ輸出者またはデータ輸入者に対する請求を行うことができない場合、副処理者は、データ主体が、本契約条項に基づく副処理者の副処理に関して、あたかも副処理者がデータ輸出者またはデータ輸入者であるかのように、副処理者に対して請求を行うことができることに同意します。ただし、データ輸出者またはデータ輸入者の承継人が、契約または法律により、データ輸出者またはデータ輸入者の法的義務を全て引き受けた場合を除きます。この場合、データ主体は、当該承継人に対して自身の権利を行使することができます。 副処理者の法的責任は、本契約条項に基づく自身の処理業務に限定されるものとします。
      4. +
    + +### 第7条: 調停と管轄 + +
      +
    1. データ輸入者は、データ主体が本契約条項に基づきデータ輸入者に対して第三受益者としての権利を行使し、または損害賠償請求を行った場合、データ主体による以下の決定に従うことに同意します。 +
        +
      1. to refer the dispute to mediation, by an independent person or, where applicable, by the supervisory authority; +
      2. to refer the dispute to the courts in the Member State in which the data exporter is established. +
      +
    2. 両当事者は、データ主体が上記選択を行っても、データ主体が国内法または国際法の他の条項に従い救済を求める実体的権利または手続的権利に影響を与えないことに同意します。 +
    + +### 第8条: 監督当局との協力 + +
      +
    1. データ輸出者は、監督当局が要請した場合、または適用されるデータ保護法令に基づき必要とされる場合、本契約書のコピーを監督当局に預けることに同意します。
      2. + +
    2. 両当事者は、監督当局がデータ輸入者および副処理者の監査を行う権利を有することに同意します。この監査の範囲は、適用されるデータ保護法令に基づくデータ輸出者に対する監査と同じものであり、また同じ条件が適用されます。
      3. + +
    3. データ輸入者は、第2項に基づくデータ輸入者または副処理者の監査の実施を妨げる、データ輸入者または副処理者に適用される法律が存在する場合、データ輸出者にすみやかに通知するものとします。 このような場合、データ輸出者は、第5条 (b) に記載された措置をとる権利を有するものとします。
      4. +
    + +### 第9条: 準拠法 + +本契約条項は、データ輸出者が設立されている加盟国の法律に準拠するものとします。 + +### 第10条: 契約の変更 + +両当事者は、本契約の変更または修正を行わないことを約束します。 これは、両当事者が、本契約と矛盾しない限度で、必要に応じて商取引上の条項を追加することを妨げるものではありません。 + +### 第11条: 副処理 + +
      +
    1. データ輸入者は、データ輸出者の書面による事前の同意なしに、データ輸出者に代わって実施するいかなる処理操作も再委託してはなりません。 データ輸入者が、データ輸出者の同意を得て本契約条項に基づく自身の義務を委託する場合、データ輸入者は、本契約に基づきデータ輸入者に課されるものと同一の義務を副処理者に課す契約を書面で締結することによってのみ、かかる副処理の委託を行うものとします。 副処理者が、かかる書面による契約に基づくデータ保護義務の履行を怠った場合、データ輸入者は、当該契約に基づく副処理者の義務の履行について、データ輸出者に対し完全に責任を負うものとします。
      2. + +
    2. データ輸出者またはデータ輸入者が事実上消滅し、もしくは法律上存在しなくなった場合、またはこれらの双方が支払不能に陥った場合で、かつ契約または法律によりデータ輸出者またはデータ輸入者の法的義務を全て引き受ける承継人が存在しないため、データ主体が第6条1項に規定された損害賠償の請求をデータ輸出者またはデータ輸入者に対して行うことができない場合に備え、データ輸入者と副処理者との間の事前の書面による契約には、第3条に定められている第三者受益者条項を規定するものとします。 サブプロセッサーの第三者に対するかかる責任は、かかる条項に基づく自らの処理操作に限定されるものとします。
      3. + +
    3. 第1項で言及されている、契約に基づく副処理におけるデータ保護の観点に関する規定は、データ輸出者が設立された加盟国の法律に準拠するものとします。
      4. + +
    4. データ輸出者は、本契約に基づき締結され、第5条 (j) に基づきデータ輸入者から通知された副処理契約のリストを保管し、このリストを少なくとも1年に1回更新するものとします。 このリストは、データ輸出者のデータ保護監督当局も入手できるものとします。
      5. +
    + +### 第12条: 個人データ処理サービス終了後の義務 + +
      +
    1. 両当事者は、データ処理サービスの提供が終了した際、データ輸入者および副処理者が、データ輸出者の選択に従い、移転された全ての個人データおよびそのコピーをデータ輸出者に返却するか、または全ての個人データを破棄し、データ輸出者に対して破棄を行った旨を証明することに同意します。ただし、データ輸入者に適用される法律により、データ輸入者が移転されたデータの全部または一部を返還または破棄することが禁じられている場合を除きます。 この場合、データ輸入者は、移転された当該個人データの秘密を保証することおよび当該個人データの処理を積極的に行わないことを保証します。
      2. + +
    2. データ輸入者および副処理者は、データ輸出者または監督当局の要請に応じ、第1項に規定された措置の監査のため、データ処理設備を提供することに同意します。
      3. +
    + +### Appendix 1 to the Standard Contractual Clauses (UK) + +**Data exporter**: Customer is the data exporter. The data exporter is a user of Online Services or Professional Services as defined in the DPA and GitHub Customer Agreement. + +**Data importer**: The data importer is GitHub, Inc., a global producer of software and services. + +**Data subjects**: Data subjects include the data exporter’s representatives and end-users including employees, contractors, collaborators, and customers of the data exporter. Data subjects may also include individuals attempting to communicate or transfer personal data to users of the services provided by data importer. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following types of data subjects in the personal data: +- データ輸出者の従業員、請負業者、派遣労働者 (現在、過去、見込みを含む)。 +- データ輸出者のコラボレータ/担当者 (自然人) または従業員、請負業者または法人コラボレータ/担当者の派遣労働者 (現在、見込み、過去を含む)。 +- Users and other data subjects that are users of data exporter's services; +- Partners, stakeholders or individuals who actively collaborate, communicate or otherwise interact with employees of the data exporter and/or use communication tools such as apps and websites provided by the data exporter. + +**Categories of data**: The personal data transferred that is included in e-mail, documents and other data in an electronic form in the context of the Online Services or Professional Services. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following categories in the personal data: +- Basic personal data (for example place of birth, street name and house number (address), postal code, city of residence, country of residence, mobile phone number, first name, last name, initials, email address, gender, date of birth); +- Authentication data (for example user name, password or PIN code, security question, audit trail); +- Contact information (for example addresses, email, phone numbers, social media identifiers; emergency contact details); +- Unique identification numbers and signatures (for example IP addresses, employee number, student number); +- Pseudonymous identifiers; +- Photos, video and audio; +- Internet activity (for example browsing history, search history, reading and viewing activities); +- Device identification (for example IMEI-number, SIM card number, MAC address); +- Profiling (for example based on observed criminal or anti-social behavior or pseudonymous profiles based on visited URLs, click streams, browsing logs, IP-addresses, domains, apps installed, or profiles based on marketing preferences); +- Special categories of data as voluntarily provided by data subjects (for example racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health, data concerning a natural person’s sex life or sexual orientation, or data relating to criminal convictions or offences); or +- Any other personal data identified in Article 4 of the GDPR. + +**Processing operations**: The personal data transferred will be subject to the following basic processing activities: + +
      +
    1. Duration and Object of Data Processing. The duration of data processing shall be for the term designated under the applicable GitHub Customer Agreement between data exporter and data importer. The objective of the data processing is the performance of Online Services and Professional Services.
      2. +
    2. Scope and Purpose of Data Processing. The scope and purpose of processing personal data is described in the “Processing of Personal Data; GDPR” section of the DPA. The data importer operates a global network of data centers and management/support facilities, and processing may take place in any jurisdiction where data importer or its sub-processors operate such facilities in accordance with the “Security Practices and Policies” section of the DPA.
      3. +
    3. Personal Data Access. For the term designated under the applicable GitHub Customer Agreement data importer will at its election and as necessary under applicable law, either: (1) provide data exporter with the ability to correct, delete, or block personal data, or (2) make such corrections, deletions, or blockages on its behalf.
      4. +
    4. Data Exporter’s Instructions. For Online Services and Professional Services, data importer will only act upon data exporter’s instructions as conveyed by GitHub.
      5. +
    5. Personal Data Deletion or Return. Upon expiration or termination of data exporter’s use of Online Services or Professional Services, it may extract personal data and data importer will delete personal data, each in accordance with the DPA Terms applicable to the agreement.
      6. +
    + +**Subcontractors**: In accordance with the DPA, the data importer may hire other companies to provide limited services on data importer’s behalf, such as providing customer support. Any such subcontractors will be permitted to obtain personal data only to deliver the services the data importer has retained them to provide, and they are prohibited from using personal data for any other purpose. + +### Appendix 2 to the Standard Contractual Clauses (UK) + +第4条 (d) および第5条 (c) に従ってデータ輸入者が実施する、技術的および組織的セキュリティ対策を以下に説明します。 + +
      +
    1. Personnel. Data importer’s personnel will not process personal data without authorization. Personnel are obligated to maintain the confidentiality of any such personal data and this obligation continues even after their engagement ends.
      2. + +
    2. Data Privacy Contact. The data privacy officer of the data importer can be reached at the following address:
      +GitHub, Inc.
      +Attn: Privacy
      +88 Colin P. Kelly Jr. Street
      +San Francisco, California 94107 USA
      3. + +
    3. Technical and Organization Measures. The data importer has implemented and will maintain appropriate technical and organizational measures, internal controls, and information security routines intended to protect personal data, as defined in the Security Practices and Policies section of the DPA, against accidental loss, destruction, or alteration; unauthorized disclosure or access; or unlawful destruction as follows: The technical and organizational measures, internal controls, and information security routines set forth in the Security Practices and Policies section of the DPA are hereby incorporated into this Appendix 2 by this reference and are binding on the data importer as if they were set forth in this Appendix 2 in their entirety.
      4. +
    + +### Appendix 3 to the Standard Contractual Clauses (UK) + +**Additional Safeguards Addendum** + +By this Additional Safeguards Addendum to Standard Contractual Clauses (UK) (this “Addendum”), GitHub, Inc. (“GitHub”) provides additional safeguards to Customer and additional redress to the data subjects to whom Customer’s personal data relates. + +This Addendum supplements and is made part of, but is not in variation or modification of, the Standard Contractual Clauses (UK). + +
      +
    1. Challenges to Orders. In addition to Clause 5(d)(i) of the Standard Contractual Clauses (UK), in the event GitHub receives an order from any third party for compelled disclosure of any personal data that has been transferred under the Standard Contractual Clauses (UK), GitHub shall:
      2. +
        +
      1. use every reasonable effort to redirect the third party to request data directly from Customer;
        2. +
      2. promptly notify Customer, unless prohibited under the law applicable to the requesting third party, and, if prohibited from notifying Customer, use all lawful efforts to obtain the right to waive the prohibition in order to communicate as much information to Customer as soon as possible; and
        3. +
      3. use all lawful efforts to challenge the order for disclosure on the basis of any legal deficiencies under the laws of the requesting party or any relevant conflicts with the law of the European Union or applicable Member State law.
        4. +

      + For purpose of this section, lawful efforts do not include actions that would result in civil or criminal penalty such as contempt of court under the laws of the relevant jurisdiction. +
    2. Indemnification of Data Subjects. Subject to Sections 3 and 4, GitHub shall indemnify a data subject for any material or non-material damage to the data subject caused by GitHub’s disclosure of personal data of the data subject that has been transferred under the Standard Contractual Clauses (UK) in response to an order from a non-EU/EEA government body or law enforcement agency (a “Relevant Disclosure”). Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under this Section 2 to the extent the data subject has already received compensation for the same damage, whether from GitHub or otherwise.
      3. +
    3. Conditions of Indemnification. Indemnification under Section 2 is conditional upon the data subject establishing, to GitHub’s reasonable satisfaction, that:
      4. +
        +
      1. GitHub engaged in a Relevant Disclosure;
        2. +
      2. the Relevant Disclosure was the basis of an official proceeding by the non-EU/EEA government body or law enforcement agency against the data subject; and
        3. +
      3. the Relevant Disclosure directly caused the data subject to suffer material or non-material damage.
        4. +

      + The data subject bears the burden of proof with respect to conditions a. though c.
      + Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under Section 2 if GitHub establishes that the Relevant Disclosure did not violate its obligations under Chapter V of the GDPR. +
    4. Scope of Damages. Indemnification under Section 2 is limited to material and non-material damages as provided in the GDPR and excludes consequential damages and all other damages not resulting from GitHub’s infringement of the GDPR.
      5. +
    5. Exercise of Rights. Rights granted to data subjects under this Addendum may be enforced by the data subject against GitHub irrespective of any restriction in Clauses 3 or 6 of the Standard Contractual Clauses (UK). The data subject may only bring a claim under this Addendum on an individual basis, and not part of a class, collective, group or representative action. Rights granted to data subjects under this Addendum are personal to the data subject and may not be assigned.
      6. +
    6. Notice of Change. In addition to Clause 5(b) of the Standard Contractual Clauses (UK), GitHub agrees and warrants that it has no reason to believe that the legislation applicable to it or its sub-processors, including in any country to which personal data is transferred either by itself or through a sub-processor, prevents it from fulfilling the instructions received from the data exporter and its obligations under this Addendum or the Standard Contractual Clauses (UK) and that in the event of a change in this legislation which is likely to have a substantial adverse effect on the warranties and obligations provided by this Addendum or the Standard Contractual Clauses (UK), it will promptly notify the change to Customer as soon as it is aware, in which case Customer is entitled to suspend the transfer of data and/or terminate the contract. +
    7. Termination. This Addendum shall automatically terminate if the European Commission, a competent Member State supervisory authority, or an EU or competent Member State court approves a different lawful transfer mechanism that would be applicable to the data transfers covered by the Standard Contractual Clauses (UK) (and if such mechanism applies only to some of the data transfers, this Addendum will terminate only with respect to those transfers) and that does not require the additional safeguards set forth in this Addendum.

      + Signing the Standard Contractual Clauses (UK), Appendix 1, Appendix 2 and +
    + +

    Attachment 3 – European Union General Data Protection Regulation Terms

    + +GitHub makes the commitments in these GDPR Related Terms, to all customers effective May 25, 2018. These commitments are binding upon GitHub with regard to Customer regardless of (1) the version of the GitHub Customer Agreement and DPA that is otherwise applicable to any given Online Services subscription or (2) any other agreement that references this attachment. + +For purposes of these GDPR Related Terms, Customer and GitHub agree that Customer is the controller of Personal Data and GitHub is the processor of such data, except when Customer acts as a processor of Personal Data, in which case GitHub is a subprocessor. These GDPR Related Terms apply to the processing of Personal Data, within the scope of the GDPR, by GitHub on behalf of Customer. These GDPR Related Terms do not limit or reduce any data protection commitments GitHub makes to Customer in the GitHub Customer Agreement or other agreement between GitHub and Customer. These GDPR Related Terms do not apply where GitHub is a controller of Personal Data. + +**Relevant GDPR Obligations: Articles 28, 32, and 33** + +
      +
    1. GitHub shall not engage another processor without prior specific or general written authorisation of Customer. In the case of general written authorisation, GitHub shall inform Customer of any intended changes concerning the addition or replacement of other processors, thereby giving Customer the opportunity to object to such changes. (Article 28(2))
      2. +
    2. Processing by GitHub shall be governed by these GDPR Related Terms under European Union (hereafter “Union”) or Member State law and are binding on GitHub with regard to Customer. The subject-matter and duration of the processing, the nature and purpose of the processing, the type of Personal Data, the categories of data subjects and the obligations and rights of the Customer are set forth in the Customer’s licensing agreement, including these GDPR Related Terms. In particular, GitHub shall:
      3. +
        +
      1. process the Personal Data only on documented instructions from Customer, including with regard to transfers of Personal Data to a third country or an international organisation, unless required to do so by Union or Member State law to which GitHub is subject; in such a case, GitHub shall inform Customer of that legal requirement before processing, unless that law prohibits such information on important grounds of public interest;
        2. +
      2. ensure that persons authorised to process the Personal Data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality;
        3. +
      3. take all measures required pursuant to Article 32 of the GDPR;
        4. +
      4. respect the conditions referred to in paragraphs 1 and 3 for engaging another processor;
        5. +
      5. taking into account the nature of the processing, assist Customer by appropriate technical and organisational measures, insofar as this is possible, for the fulfilment of the Customer’s obligation to respond to requests for exercising the data subject's rights laid down in Chapter III of the GDPR;
        6. +
      6. assist Customer in ensuring compliance with the obligations pursuant to Articles 32 to 36 of the GDPR, taking into account the nature of processing and the information available to GitHub;
        7. +
      7. at the choice of Customer, delete or return all the Personal Data to Customer after the end of the provision of services relating to processing, and delete existing copies unless Union or Member State law requires storage of the Personal Data;
        8. +
      8. make available to Customer all information necessary to demonstrate compliance with the obligations laid down in Article 28 of the GDPR and allow for and contribute to audits, including inspections, conducted by Customer or another auditor mandated by Customer.
        9. +

      + GitHub shall immediately inform Customer if, in its opinion, an instruction infringes the GDPR or other Union or Member State data protection provisions. (Article 28(3))

      +
    3. Where GitHub engages another processor for carrying out specific processing activities on behalf of Customer, the same data protection obligations as set out in these GDPR Related Terms shall be imposed on that other processor by way of a contract or other legal act under Union or Member State law, in particular providing sufficient guarantees to implement appropriate technical and organisational measures in such a manner that the processing will meet the requirements of the GDPR. Where that other processor fails to fulfil its data protection obligations, GitHub shall remain fully liable to the Customer for the performance of that other processor's obligations. (Article 28(4))
      4. +
    4. Taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of processing as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons, Customer and GitHub shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, including inter alia as appropriate:
      5. +
        +
      1. the pseudonymisation and encryption of Personal Data;
        2. +
      2. the ability to ensure the ongoing confidentiality, integrity, availability and resilience of processing systems and services;
        3. +
      3. the ability to restore the availability and access to Personal Data in a timely manner in the event of a physical or technical incident; and
        4. +
      4. a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the processing. (Article 32(1))
        5. +
      +
    5. In assessing the appropriate level of security, account shall be taken of the risks that are presented by processing, in particular from accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to Personal Data transmitted, stored or otherwise processed (Article 32(2)).
      6. +
    6. Customer and GitHub shall take steps to ensure that any natural person acting under the authority of Customer or GitHub who has access to Personal Data does not process them except on instructions from Customer, unless he or she is required to do so by Union or Member State law (Article 32(4)).
      7. +
    7. GitHub shall notify Customer without undue delay after becoming aware of a Personal Data breach (Article 33(2)). Such notification will include that information a processor must provide to a controller under Article 33(3) to the extent such information is reasonably available to GitHub.
      8. +
    + +--------------- + +

    (1) The Agreement on the European Economic Area (EEA Agreement) provides for the extension of the European Union’s internal market to the three EEA States Iceland, Liechtenstein and Norway. The Union data protection legislation, including Regulation (EU) 2016/679, is covered by the EEA Agreement and has been incorporated into Annex XI thereto. Therefore, any disclosure by the data importer to a third party located in the EEA does not qualify as an onward transfer for the purpose of these Clauses.

    + +

    (2) This requirement may be satisfied by the sub-processor acceding to these Clauses under the appropriate Module, in accordance with Clause 7.

    + +

    (3) As regards the impact of such laws and practices on compliance with these Clauses, different elements may be considered as part of an overall assessment. Such elements may include relevant and documented practical experience with prior instances of requests for disclosure from public authorities, or the absence of such requests, covering a sufficiently representative time-frame. This refers in particular to internal records or other documentation, drawn up on a continuous basis in accordance with due diligence and certified at senior management level, provided that this information can be lawfully shared with third parties. Where this practical experience is relied upon to conclude that the data importer will not be prevented from complying with these Clauses, it needs to be supported by other relevant, objective elements, and it is for the Parties to consider carefully whether these elements together carry sufficient weight, in terms of their reliability and representativeness, to support this conclusion. In particular, the Parties have to take into account whether their practical experience is corroborated and not contradicted by publicly available or otherwise accessible, reliable information on the existence or absence of requests within the same sector and/or the application of the law in practice, such as case law and reports by independent oversight bodies.

    diff --git a/translations/ja-JP/content/github/site-policy/github-terms-for-additional-products-and-features.md b/translations/ja-JP/content/github/site-policy/github-terms-for-additional-products-and-features.md index 15991cd87a..27b37b17a2 100644 --- a/translations/ja-JP/content/github/site-policy/github-terms-for-additional-products-and-features.md +++ b/translations/ja-JP/content/github/site-policy/github-terms-for-additional-products-and-features.md @@ -20,7 +20,7 @@ GitHub を利用する際、数多くの追加製品や機能 (「追加製品 - **GitHub Enterprise Server** のユーザは、以下の「追加製品および機能」にアクセスできます。Actions、Advanced Security、Advisory Database、Connect、Dependabot Preview、Learning Lab、Octoshift、Packages、Pages and SQL Server Images。 -- **GitHub AE** のユーザは、以下の「追加製品および機能」にアクセスできます。Actions、Advanced Security、Advisory Database、{% ifversion ghae-next %}Connect、{% endif %}Dependabot Preview、Octoshift、Packages and Pages。 +- **GitHub AE** users may have access to the following Additional Products and Features: Actions, Advanced Security, Advisory Database,{% ifversion ghae-next %}Connect, {% endif %}Dependabot Preview, Octoshift, Packages and Pages. ## アクション GitHubアクションでは、カスタムソフトウェア開発のライフサイクルにわたるワークフローをGitHubリポジトリに直接作成することができます。 Actionsは、使用量に基づいて課金されます。 [Actionsのドキュメント](/actions)には、計算量やストレージ容量 (アカウントのプランによって異なる)、およびActionsの使用分数の監視方法や利用限度の設定方法などの詳細情報が記載されています。 @@ -38,7 +38,7 @@ Actions and any elements of the Actions product or service may not be used in vi ## Advanced Security Advanced Security ライセンスを取得しているお客様に対して、GitHub は追加セキュリティ機能を提供しています。 追加機能にはコードスキャン、シークレットスキャン、依存関係レビューが含まれます。 詳細は [Advanced Security のドキュメント](/github/getting-started-with-github/about-github-advanced-security)をご覧ください。 -Advanced Security のライセンスは、「ユニークコミッター」ごとに付与されます。 「ユニークコミッター」とは、GitHub Enterprise、GitHub Enterprise Cloud、GitHub Enterprise Server、またはGitHub AEのライセンスを付与されており、直近90日間にGitHub Advanced Securityの何らかの機能を有効化してコードのコミットを行ったユーザのことです。 お客様の各「ユニークコミッター」ごとに、GitHub Advanced Securityの「ユーザライセンス」を取得する必要があります。 GitHub Advanced Securityは、お客様によりまたはお客様のために開発されたコードベースにおいてのみ使用できます。 GitHub Enterprise Cloud ユーザの場合、一部のAdvanced Securityセキュリティ機能にはGitHub Actionsを使用する必要もあります。 +Advanced Security のライセンスは、「ユニークコミッター」ごとに付与されます。 A "Unique Committer" is a licensed user of GitHub Enterprise, GitHub Enterprise Cloud, GitHub Enterprise Server, or GitHub AE, who has made a commit in the last 90 days to any repository with any GitHub Advanced Security functionality activated. お客様の各「ユニークコミッター」ごとに、GitHub Advanced Securityの「ユーザライセンス」を取得する必要があります。 GitHub Advanced Securityは、お客様によりまたはお客様のために開発されたコードベースにおいてのみ使用できます。 GitHub Enterprise Cloud ユーザの場合、一部のAdvanced Securityセキュリティ機能にはGitHub Actionsを使用する必要もあります。 ## Advisory Database GitHub Advisory Databaseを使用すると、GitHubのオープンソースプロジェクトに影響を与える脆弱性を閲覧および検索できます。 diff --git a/translations/ja-JP/content/github/site-policy/index.md b/translations/ja-JP/content/github/site-policy/index.md index bae9644e82..2a282e5647 100644 --- a/translations/ja-JP/content/github/site-policy/index.md +++ b/translations/ja-JP/content/github/site-policy/index.md @@ -12,7 +12,7 @@ children: - /github-terms-of-service - /github-corporate-terms-of-service - /github-privacy-statement - - /github-data-protection-agreement-non-enterprise-customers + - /github-data-protection-agreement - /global-privacy-practices - /github-sponsors-additional-terms - /github-codespaces-privacy-statement diff --git a/translations/ja-JP/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md b/translations/ja-JP/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md index 3a26216b95..6dc09ac299 100644 --- a/translations/ja-JP/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md +++ b/translations/ja-JP/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md @@ -1,6 +1,7 @@ --- title: Gist の作成 intro: '{% ifversion ghae %}内部{% else %}パブリック{% endif %}とシークレットの 2 種類の Gist を作成できます。 アイデアを {% ifversion ghae %}Enterprise のメンバー{% else %}世界{% endif %}と共有する準備ができている場合は、{% ifversion ghae %}内部{% else %}パブリック{% endif %}の Gist を作成します。そうでない場合は、シークレットの Gist を作成します。' +permissions: '{% data reusables.enterprise-accounts.emu-permission-gist %}' redirect_from: - /articles/about-gists/ - /articles/cannot-delete-an-anonymous-gist/ @@ -42,7 +43,7 @@ Gist をプロフィールにピン止めして、他のユーザが簡単に見 {% endif %} -{% data variables.gists.gist_homepage %} に移動し、[**All Gists**] をクリックすると、他の人が作成した{% ifversion ghae %}内部{% else %}パブリック{% endif %} Gist を見つけることができます。 こうすると、すべての Gist が作成時刻または更新時刻でソートされて表示されるページに行きます。 また、Gist は {% data variables.gists.gist_search_url %} で言語ごとに検索できます。 Gist 検索は[コード検索](/articles/searching-code)と同じ検索構文を使います。 +{% data variables.gists.gist_homepage %} に移動し、[**All Gists**] をクリックすると、他の人が作成した{% ifversion ghae %}内部{% else %}パブリック{% endif %} Gist を見つけることができます。 こうすると、すべての Gist が作成時刻または更新時刻でソートされて表示されるページに行きます。 また、Gist は {% data variables.gists.gist_search_url %} で言語ごとに検索できます。 Gist 検索は[コード検索](/search-github/searching-on-github/searching-code)と同じ検索構文を使います。 Gist は Git リポジトリであるため、完全なコミット履歴を diff とともに表示させることができます。 Gist はフォークしたりクローンしたりすることもできます。 詳細は「[Gist のフォークおよびクローン](/articles/forking-and-cloning-gists)」を参照してください。 diff --git a/translations/ja-JP/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md b/translations/ja-JP/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md index e37d7dbfff..f4400added 100644 --- a/translations/ja-JP/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md +++ b/translations/ja-JP/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md @@ -1,6 +1,7 @@ --- title: Gistのフォークとクローン intro: Gists は Git リポジトリです。つまり、オリジナルの作者でなくても Gist をフォークしたりクローンしたりできます。 diff など、Gist の完全なコミット履歴を見ることもできます。 +permissions: '{% data reusables.enterprise-accounts.emu-permission-gist %}' redirect_from: - /articles/forking-and-cloning-gists - /github/writing-on-github/forking-and-cloning-gists diff --git a/translations/ja-JP/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md b/translations/ja-JP/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md index b03a3629cb..4892714fec 100644 --- a/translations/ja-JP/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md +++ b/translations/ja-JP/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md @@ -40,9 +40,9 @@ shortTitle: Basic formatting syntax テキストは`>`で引用できます。 ```markdown -アブラハムリンカーンの言葉：: +Text that is not a quote -> フランス語で失礼します +> Text that is a quote ``` ![表示された引用テキスト](/assets/images/help/writing/quoted-text-rendered.png) @@ -184,7 +184,7 @@ For more information, see "[Relative Links](#relative-links)." ![入れ子になったリストアイテムを持つリスト](/assets/images/help/writing/nested-list-example-3.png) -同じ方法で、複数レベルの入れ子になったリストを作成できます。 たとえば、最初の入れ子になったリストアイテムは内容である`最初の入れ子になったリストアイテム`の前に 7 つの空白 (`␣␣␣␣␣-␣`) があるため、2 番目の入れ子になったリストアイテムは 7 つの空白でインデントしなければならないでしょう。 +同じ方法で、複数レベルの入れ子になったリストを作成できます。 For example, because the first nested list item has seven characters (`␣␣␣␣␣-␣`) before the nested list content `First nested list item`, you would need to indent the second nested list item by seven spaces. ```markdown 100. 最初のリストアイテム @@ -262,6 +262,30 @@ Some {% data variables.product.prodname_github_apps %} provide information in {% テキスト行の間に空白行を残すことで、新しいパラグラフを作成できます。 +{% ifversion fpt or ghae-next or ghes > 3.3 %} +## Footnotes + +You can add footnotes to your content by using this bracket syntax: + +``` +Here is a simple footnote[^1]. + +[^1]: My reference. +``` + +The footnote will render like this: + +![Rendered footnote](/assets/images/site/rendered-footnote.png) +{% endif %} + +## Hiding content with comments + +You can tell {% data variables.product.product_name %} to hide content from the rendered Markdown by placing the content in an HTML comment. + +
    +<!-- This content will not appear in the rendered Markdown -->
+
    + ## Markdown のフォーマットの無視 {% data variables.product.product_name %}に対し、Markdown のキャラクタの前に `\` を使うことで、Markdown のフォーマットを無視 (エスケープ) させることができます。 @@ -272,13 +296,13 @@ Some {% data variables.product.prodname_github_apps %} provide information in {% 詳しい情報については Daring Fireball の [Markdown Syntax](https://daringfireball.net/projects/markdown/syntax#backslash) を参照してください。 -## Hiding content with comments +{% ifversion fpt or ghes > 3.2 or ghae-issue-5232 %} -You can tell {% data variables.product.product_name %} to hide content from the rendered Markdown by placing the content in an HTML comment. +## Disabling Markdown rendering -
    -<!-- This content will not appear in the rendered Markdown -->
-
    +{% data reusables.repositories.disabling-markdown-rendering %} + +{% endif %} ## 参考リンク diff --git a/translations/ja-JP/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md b/translations/ja-JP/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md index 89648d94c7..8c0dc764af 100644 --- a/translations/ja-JP/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md +++ b/translations/ja-JP/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md @@ -16,7 +16,7 @@ topics: {% warning %} -**Warning:** If you add an image {% ifversion fpt or ghes > 3.1 or ghae-next %} or video {% endif %} to a pull request or issue comment, anyone can view the anonymized URL without authentication, even if the pull request is in a private repository{% ifversion ghes %}, or if private mode is enabled{% endif %}. To keep sensitive media files private, serve them from a private network or server that requires authentication. {% ifversion fpt %}For more information on anonymized URLs see "[About anonymized URLs](/github/authenticating-to-github/about-anonymized-urls)".{% endif %} +**Warning:** If you add an image{% ifversion fpt or ghes > 3.1 or ghae-next %} or video{% endif %} to a pull request or issue comment, anyone can view the anonymized URL without authentication, even if the pull request is in a private repository{% ifversion ghes %}, or if private mode is enabled{% endif %}. To keep sensitive media files private, serve them from a private network or server that requires authentication. {% ifversion fpt %}For more information on anonymized URLs see "[About anonymized URLs](/github/authenticating-to-github/about-anonymized-urls)".{% endif %} {% endwarning %} @@ -31,9 +31,10 @@ Issue やプルリクエストの会話にファイルを添付するには、 {% endtip %} The maximum file size is: -- 10MB for images and gifs{% ifversion fpt or ghes > 3.1 or ghae-next %} +- 10MB for images and gifs{% ifversion fpt %} - 10MB for videos uploaded to a repository owned by a user or organization on a free GitHub plan -- 100MB for videos uploaded to a repository owned by a user or organization on a paid GitHub plan{% endif %} +- 100MB for videos uploaded to a repository owned by a user or organization on a paid GitHub plan{% elsif fpt or ghes > 3.1 or ghae-next %} +- 100MB for videos{% endif %} - 25MB for all other files 以下のファイルがサポートされています: diff --git a/translations/ja-JP/content/graphql/guides/managing-enterprise-accounts.md b/translations/ja-JP/content/graphql/guides/managing-enterprise-accounts.md index 353977c35e..9164289206 100644 --- a/translations/ja-JP/content/graphql/guides/managing-enterprise-accounts.md +++ b/translations/ja-JP/content/graphql/guides/managing-enterprise-accounts.md @@ -58,8 +58,9 @@ GraphQLを使ってEnterpriseアカウントの管理を始めるには、以下 - `admin:enterprise` Enterpriseアカウントに固有にスコープは以下のとおりです。 - - `admin:enterprise`: Enterpriseの完全な制御を与えます（`manage_billing:enterprise`及び`read:enterprise`を含む） - - `manage_billing:enterprise`: Enterpriseの支払いデータの読み書き。 + - `admin:enterprise`: Gives full control of enterprises (includes {% ifversion ghes > 3.2 or fpt or ghae %}`manage_runners:enterprise`, {% endif %}`manage_billing:enterprise` and `read:enterprise`) + - `manage_billing:enterprise`: Read and write enterprise billing data.{% ifversion ghes > 3.2 or fpt or ghae %} + - `manage_runners:enterprise`: Access to manage GitHub Actions enterprise runners and runner-groups.{% endif %} - `read:enterprise`: Enterpriseのプロフィールデータの読み取り。 4. 個人アクセストークンをコピーし、GraphQLクライアントに追加するまでは安全な場所に保管しておいてください。 diff --git a/translations/ja-JP/content/graphql/guides/using-the-graphql-api-for-discussions.md b/translations/ja-JP/content/graphql/guides/using-the-graphql-api-for-discussions.md index adf68be8f0..117e0ac3b0 100644 --- a/translations/ja-JP/content/graphql/guides/using-the-graphql-api-for-discussions.md +++ b/translations/ja-JP/content/graphql/guides/using-the-graphql-api-for-discussions.md @@ -1080,4 +1080,4 @@ mutation { ## 検索 -ディスカッションは、トップレベルの`search`フィールドから返されることがあります。 ディスカッションを検索するには、`type`を`DISCUSSION`に指定してください。 `SearchResultItemConnection`型は、返されるディスカッション数を知らせる`discussionCount`フィールドを持ち、`SearchResultItem`共用体には`Discussion`型が追加されます。 詳しい情報については「[クエリ](/graphql/reference/queries#searchresultitemconnection)」及び「[ディスカッションの検索](/github/searching-for-information-on-github/searching-discussions)」を参照してください。 +ディスカッションは、トップレベルの`search`フィールドから返されることがあります。 ディスカッションを検索するには、`type`を`DISCUSSION`に指定してください。 `SearchResultItemConnection`型は、返されるディスカッション数を知らせる`discussionCount`フィールドを持ち、`SearchResultItem`共用体には`Discussion`型が追加されます。 詳しい情報については「[クエリ](/graphql/reference/queries#searchresultitemconnection)」及び「[ディスカッションの検索](/search-github/searching-on-github/searching-discussions)」を参照してください。 diff --git a/translations/ja-JP/content/index.md b/translations/ja-JP/content/index.md index 0d5870a050..ca006e35ff 100644 --- a/translations/ja-JP/content/index.md +++ b/translations/ja-JP/content/index.md @@ -27,6 +27,7 @@ children: - actions - codespaces - packages + - search-github - developers - rest - graphql 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 17d033d87f..ff281dedc5 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 @@ -1,6 +1,7 @@ --- title: GitHub の他のユーザに Issue およびPull Requestをアサインする intro: アサインされた人によって、誰が特定の Issue やPull Requestで作業しているかが明確になります。 +permissions: 'Anyone with write access to a repository can assign issues and pull requests. {% data reusables.enterprise-accounts.emu-permission-repo %}' redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/assigning-issues-and-pull-requests-to-other-github-users - /articles/assigning-issues-and-pull-requests-to-other-github-users @@ -15,11 +16,9 @@ topics: shortTitle: Issue及びPRのアサイン --- -リポジトリへの書き込み権限があるユーザなら誰でもIssue およびPull Requestをアサインできます。 - ## Issue およびPull Requestをアサインされた人について -自身、該当する Issue またはPull Requestにコメントした任意の人、リポジトリへの書き込み権限がある任意の人、およびリポジトリの読み取り権限がある Organization メンバーを含めて、最大 10 人まで各 Issue またはPull Requestにアサインできます。 詳細は「[{% data variables.product.prodname_dotcom %} 上のアクセス権限](/articles/access-permissions-on-github)」を参照してください。 +自身、該当する Issue またはプルリクエストにコメントした任意の人、リポジトリへの書き込み権限がある任意の人、およびリポジトリの読み取り権限がある Organization メンバーを含めて、最大 10 人まで各 Issue またはプルリクエストにアサインできます。 詳細は「[{% data variables.product.prodname_dotcom %} 上のアクセス権限](/articles/access-permissions-on-github)」を参照してください。 ## 個別の Issue またはPull Requestを割り当てる diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/creating-an-issue.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/creating-an-issue.md index 1127ba31e0..c61bd4bf46 100644 --- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/creating-an-issue.md +++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/creating-an-issue.md @@ -1,7 +1,7 @@ --- title: Issue の作成 intro: Issueは様々な方法で作成できるので、ワークフローで最も便利な方法を選択できます。 -permissions: People with read permissions can create an issue in a repository where issues are enabled. +permissions: 'People with read access can create an issue in a repository where issues are enabled. {% data reusables.enterprise-accounts.emu-permission-repo %}' redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/creating-an-issue - /articles/creating-an-issue diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md index aed8223205..39502d339e 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 @@ -102,7 +102,8 @@ Once you've [applied labels to an issue or pull request](/articles/applying-labe - マージの前に[レビューが必要](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)なプルリクエスト - レビュー担当者が承認したプルリクエスト - レビュー担当者が変更を求めているプルリクエスト -- 自分がレビューしたプルリクエスト +- Pull requests that you have reviewed{% ifversion fpt or ghae or ghes > 3.2 %} +- Pull requests that someone has asked you directly to review{% endif %} - [自分、または自分のチームに誰かがレビューを依頼](/articles/requesting-a-pull-request-review)したプルリクエスト {% data reusables.repositories.navigate-to-repo %} @@ -185,7 +186,8 @@ Issueについては、以下も検索に利用できます。 - レビュー担当者が承認したプルリクエストのフィルタリング: `state:open type:pr review:approved` - レビュー担当者が変更を要求したプルリクエストのフィルタリング: `state:open type:pr review:changes_requested` - [レビュー担当者](/articles/about-pull-request-reviews/)によるプルリクエストのフィルタリング: `state:open type:pr reviewed-by:octocat` -- [レビューを要求された](/articles/requesting-a-pull-request-review)特定のユーザーによるプルリクエストのフィルタリング: `state:open type:pr review-requested:octocat` +- Filter pull requests by the specific user [requested for review](/articles/requesting-a-pull-request-review): `state:open type:pr review-requested:octocat`{% ifversion fpt or ghae or ghes > 3.2 %} +- Filter pull requests that someone has asked you directly to review: `state:open type:pr user-review-requested:@me`{% endif %} - レビューを要求されたチームによるプルリクエストのフィルタリング: `state:open type:pr team-review-requested:github/atom`{% ifversion fpt or ghes or ghae %} - プルリクエストでクローズできるIssueにリンクされているプルリクエストのフィルタリング: `linked:issue`{% endif %} diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository.md index 1fcae73cd5..b708b11a5b 100644 --- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository.md +++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository.md @@ -1,6 +1,7 @@ --- title: Issue をリポジトリにピン止めする intro: リポジトリの Issue リストの上に、最大 3 つまで重要な Issue をピン止めできます。 +permissions: 'People with write access to a repository can pin issue in the repository. {% data reusables.enterprise-accounts.emu-permission-repo %}' redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/pinning-an-issue-to-your-repository - /articles/pinning-an-issue-to-your-repository @@ -17,8 +18,6 @@ shortTitle: Issueをピン止めする ![ピン止めした Issue](/assets/images/help/issues/pinned-issues.png) -Issue をピン止めするには、その Issue があるリポジトリへの書き込み権限が必要です。 - {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issues %} 1. Issue のリストで、ピン止めする Issue をクリックします。 diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/quickstart.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/quickstart.md index a83b5fad7d..560111f153 100644 --- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/quickstart.md +++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/quickstart.md @@ -19,7 +19,7 @@ topics: ## 必要な環境 -Issueを作成するにはリポジトリが必要です。 書き込みアクセス権を持つ既存のリポジトリを利用することも、新しいリポジトリを作成することもできます。 このリポジトリではIssueが有効になっていなければなりません。 リポジトリの作成に関する詳細は「[新しいリポジトリの作成](/articles/creating-a-new-repository)」を参照してください。 リポジトリでIssueが無効化されている場合、Issueを有効化する方法に関する情報については「[Issueの無効化](/github/administering-a-repository/managing-repository-settings/disabling-issues)」を参照してください。 +Issueを作成するにはリポジトリが必要です。 書き込みアクセス権を持つ既存のリポジトリを利用することも、新しいリポジトリを作成することもできます。 {% data reusables.enterprise-accounts.emu-permission-repo %} The repository must have issues enabled. リポジトリの作成に関する詳細は「[新しいリポジトリの作成](/articles/creating-a-new-repository)」を参照してください。 リポジトリでIssueが無効化されている場合、Issueを有効化する方法に関する情報については「[Issueの無効化](/github/administering-a-repository/managing-repository-settings/disabling-issues)」を参照してください。 ## 空のIssueのオープン diff --git a/translations/ja-JP/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md b/translations/ja-JP/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md index 5ac2b1c4cc..bc635e24da 100644 --- a/translations/ja-JP/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md +++ b/translations/ja-JP/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md @@ -1,6 +1,7 @@ --- title: ラベルを管理する intro: 'ラベルの作成、編集、適用、削除によって、{% ifversion fpt %}Issue、Pull Request、ディスカッション{% else %}IssueとPull Request{% endif %}を分類できます。' +permissions: '{% data reusables.enterprise-accounts.emu-permission-repo %}' redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/managing-labels - /articles/managing-Labels @@ -30,8 +31,6 @@ topics: {% data variables.product.product_name %}上の作業を、{% ifversion fpt %}Issue、Pull Request、ディスカッション{% else %}IssueとPull Request{% endif %}を分類するためのラベルを作成することによって管理できます。 ラベルが作成されたリポジトリ内にラベルを適用できます。 ラベルがあれば、そのリポジトリ内の任意の{% ifversion fpt %}Issue、Pull Request、ディスカッション{% else %}IssueやPull Request{% endif %}にそのラベルを使用できます。 -リポジトリへの読み取りアクセスを持つ人は、誰でもリポジトリのラベルを表示・検索できます。 リポジトリへのトリアージアクセスを持つすべてのユーザは、既存のラベルを適用/却下できます。 ラベルの作成、編集、適用、削除をするためには、リポジトリに書き込みアクセスができなければなりません。 - ## デフォルトラベルについて {% data variables.product.product_name %} は、すべての新しいリポジトリにデフォルトのラベルを提供します。 これらのデフォルトラベルを使用して、リポジトリに標準のワークフローを作成しやすくすることができます。 @@ -50,7 +49,7 @@ topics: リポジトリの作成時に、すべての新しいリポジトリにデフォルトのラベルが含められますが、後でそのラベルを編集または削除できます。 -`good first issue`ラベル付きのIssueは、リポジトリの`contribute`ページを展開するために使われます。 `contribute`ページの例については[github/docs/contribute](https://github.com/github/docs/contribute)を参照してください。 +Issues with the `good first issue` label are used to populate the repository's `contribute` page. `contribute`ページの例については[github/docs/contribute](https://github.com/github/docs/contribute)を参照してください。 {% ifversion fpt or ghes %} Organization のオーナーは、Organization 内のリポジトリのためのデフォルトラベルをカスタマイズできます。 詳しい情報については、「[Organization 内のリポジトリのためのデフォルトラベルを管理する](/articles/managing-default-labels-for-repositories-in-your-organization)」を参照してください。 @@ -58,6 +57,8 @@ Organization のオーナーは、Organization 内のリポジトリのための ## ラベルの作成 +Anyone with write access to a repository can create a label. + {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} {% data reusables.project-management.labels %} @@ -69,11 +70,15 @@ Organization のオーナーは、Organization 内のリポジトリのための ## Applying a label +Anyone with triage access to a repository can apply and dismiss labels. + 1. {% ifversion fpt %}Issue、Pull Request、ディスカッション{% else %}IssueあるいはPull Request{% endif %}にアクセスしてください。 1. 右のサイドバーで、"Labels（ラベル）"の右の{% octicon "gear" aria-label="The gear icon" %}をクリックし、続いてラベルをクリックしてください !["ラベル" ドロップダウンメニュー](/assets/images/help/issues/labels-drop-down.png) ## ラベルの編集 +Anyone with write access to a repository can edit existing labels. + {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} {% data reusables.project-management.labels %} @@ -85,6 +90,8 @@ Organization のオーナーは、Organization 内のリポジトリのための ## ラベルの削除 +Anyone with write access to a repository can delete existing labels. + ラベルを削除すると、Issue とプルリクエストからラベルが削除されます。 {% data reusables.repositories.navigate-to-repo %} diff --git a/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md index f34e28ddbe..9f44e56415 100644 --- a/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md +++ b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md @@ -24,6 +24,8 @@ Enterprise アカウントは、複数の {% data variables.product.prodname_dot enterprise アカウントに属する Organization では、支払いは enterprise アカウントのレベルで管理され、Organization のレベルでは支払い設定は利用できません。 Enterprise のオーナーは、Enterprise アカウントですべての Organization に対するポリシーを設定することも、Organization のオーナーに Organization のレベルでポリシーを設定することを許可することもできます。 Organization のオーナーは、Enterprise アカウントのレベルで Organization に強制された設定を変更することはできません。 Organization のポリシーや設定について質問がある場合は Enterprise アカウントのオーナーに問い合わせてください。 +{% data reusables.enterprise-accounts.invite-organization %} + {% data reusables.gated-features.enterprise-accounts %} {% data reusables.organizations.org-ownership-recommendation %}詳細は、「[Organization の所有権の継続性を管理する](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)」を参照してください。 diff --git a/translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md b/translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md index 81a412e630..f39c529de8 100644 --- a/translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md +++ b/translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md @@ -25,6 +25,18 @@ Organization に対する SAML シングルサインオンを有効にすると {% data reusables.saml.about-linked-identities %} +利用できる場合には、このエントリにはSCIMデータが含まれます。 詳しい情報については「[SCIMについて](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)」を参照してください。 + +{% warning %} + +**Warning:** For organizations using SCIM: +- Revoking a linked user identity on {% data variables.product.product_name %} will also remove the SAML and SCIM metadata. As a result, the identity provider will not be able to synchronize or deprovision the linked user identity. +- An admin must revoke a linked identity through the identity provider. +- To revoke a linked identity and link a different account through the identity provider, an admin can remove and re-assign the user to the {% data variables.product.product_name %} application. For more information, see your identity provider's documentation. + +{% endwarning %} + + {% data reusables.identity-and-permissions.revoking-identity-team-sync %} {% data reusables.profile.access_org %} diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md index 230a2a17de..0d14ae9504 100644 --- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md @@ -54,95 +54,96 @@ Some of the features listed below are limited to organizations using {% data var {% endnote %} {% endif %} -| リポジトリアクション | Read | Triage | Write | Maintain | Admin | -|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:------:|:-----:|:--------:|:------------------------------------------------:| -| 個人または Team の割り当てリポジトリからのプル | **X** | **X** | **X** | **X** | **X** | -| 個人または Team の割り当てリポジトリのフォーク | **X** | **X** | **X** | **X** | **X** | -| 自分のコメントの編集および削除 | **X** | **X** | **X** | **X** | **X** | -| Issue のオープン | **X** | **X** | **X** | **X** | **X** | -| 自分でオープンした Issue のクローズ | **X** | **X** | **X** | **X** | **X** | -| 自分でクローズした Issue を再オープン | **X** | **X** | **X** | **X** | **X** | -| 自分に割り当てられた Issue の取得 | **X** | **X** | **X** | **X** | **X** | -| Team の割り当てリポジトリのフォークからのプルリクエストの送信 | **X** | **X** | **X** | **X** | **X** | -| プルリクエストについてのレビューのサブミット | **X** | **X** | **X** | **X** | **X** | -| 公開済みリリースの表示 | **X** | **X** | **X** | **X** | **X** |{% ifversion fpt %} -| [[GitHub Actions workflow runs](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)] の表示 | **X** | **X** | **X** | **X** | **X** +| リポジトリアクション | Read | Triage | Write | Maintain | Admin | +|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:------:|:-----:|:--------:|:-----------------------------------------------------:| +| 個人または Team の割り当てリポジトリからのプル | **X** | **X** | **X** | **X** | **X** | +| 個人または Team の割り当てリポジトリのフォーク | **X** | **X** | **X** | **X** | **X** | +| 自分のコメントの編集および削除 | **X** | **X** | **X** | **X** | **X** | +| Issue のオープン | **X** | **X** | **X** | **X** | **X** | +| 自分でオープンした Issue のクローズ | **X** | **X** | **X** | **X** | **X** | +| 自分でクローズした Issue を再オープン | **X** | **X** | **X** | **X** | **X** | +| 自分に割り当てられた Issue の取得 | **X** | **X** | **X** | **X** | **X** | +| Team の割り当てリポジトリのフォークからのプルリクエストの送信 | **X** | **X** | **X** | **X** | **X** | +| プルリクエストについてのレビューのサブミット | **X** | **X** | **X** | **X** | **X** | +| 公開済みリリースの表示 | **X** | **X** | **X** | **X** | **X** |{% ifversion fpt %} +| [[GitHub Actions workflow runs](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)] の表示 | **X** | **X** | **X** | **X** | **X** {% endif %} -| wiki の編集 | **X** | **X** | **X** | **X** | **X** |{% ifversion fpt %} -| [悪用あるいはスパムの可能性があるコンテンツのレポート](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** +| Edit wikis in public repositories | **X** | **X** | **X** | **X** | **X** | +| Edit wikis in private repositories | | | **X** | **X** | **X** |{% ifversion fpt %} +| [悪用あるいはスパムの可能性があるコンテンツのレポート](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** {% endif %} -| ラベルの適用/却下 | | **X** | **X** | **X** | **X** | -| ラベルの作成、編集、削除 | | | **X** | **X** | **X** | -| すべての Issue およびプルリクエストのクローズ、再オープン、割り当て | | **X** | **X** | **X** | **X** |{% ifversion fpt or ghae or ghes > 3.0 %} -| [プルリクエストの自動マージの有効化または無効化](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** +| ラベルの適用/却下 | | **X** | **X** | **X** | **X** | +| ラベルの作成、編集、削除 | | | **X** | **X** | **X** | +| すべての Issue およびプルリクエストのクローズ、再オープン、割り当て | | **X** | **X** | **X** | **X** |{% ifversion fpt or ghae or ghes > 3.0 %} +| [プルリクエストの自動マージの有効化または無効化](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** {% endif %} -| マイルストーンの適用 | | **X** | **X** | **X** | **X** | -| [重複した Issue とプルリクエスト](/articles/about-duplicate-issues-and-pull-requests)のマーク付け | | **X** | **X** | **X** | **X** | -| [プルリクエストのレビュー](/articles/requesting-a-pull-request-review)の要求 | | **X** | **X** | **X** | **X** | -| Merge a [pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges) | | | **X** | **X** | **X** | -| 個人または Team の割り当てリポジトリへのプッシュ (書き込み) | | | **X** | **X** | **X** | -| コミット、プルリクエスト、Issue についての他者によるコメントの編集と削除 | | | **X** | **X** | **X** | -| [他者によるコメントの非表示](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **X** | **X** | **X** | -| [会話のロック](/communities/moderating-comments-and-conversations/locking-conversations) | | | **X** | **X** | **X** | -| Issue の移譲 (詳細は「[他のリポジトリへ Issue を移譲する](/articles/transferring-an-issue-to-another-repository)」を参照) | | | **X** | **X** | **X** | -| [リポジトリに指定されたコードオーナーとしてのアクション](/articles/about-code-owners) | | | **X** | **X** | **X** | -| [プルリクエストのドラフトに、レビューの準備ができたことを示すマークを付ける](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | -| [プルリクエストをドラフトに変換する](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | -| プルリクエストのマージ可能性に影響するレビューのサブミット | | | **X** | **X** | **X** | -| プルリクエストに[提案された変更を適用する](/articles/incorporating-feedback-in-your-pull-request) | | | **X** | **X** | **X** | -| [ステータスチェック](/articles/about-status-checks)の作成 | | | **X** | **X** | **X** |{% ifversion fpt %} -| [GitHub Actions ワークフロー](/actions/automating-your-workflow-with-github-actions/) の作成、編集、実行、再実行、キャンセル | | | **X** | **X** | **X** +| マイルストーンの適用 | | **X** | **X** | **X** | **X** | +| [重複した Issue とプルリクエスト](/articles/about-duplicate-issues-and-pull-requests)のマーク付け | | **X** | **X** | **X** | **X** | +| [プルリクエストのレビュー](/articles/requesting-a-pull-request-review)の要求 | | **X** | **X** | **X** | **X** | +| Merge a [pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges) | | | **X** | **X** | **X** | +| 個人または Team の割り当てリポジトリへのプッシュ (書き込み) | | | **X** | **X** | **X** | +| コミット、プルリクエスト、Issue についての他者によるコメントの編集と削除 | | | **X** | **X** | **X** | +| [他者によるコメントの非表示](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **X** | **X** | **X** | +| [会話のロック](/communities/moderating-comments-and-conversations/locking-conversations) | | | **X** | **X** | **X** | +| Issue の移譲 (詳細は「[他のリポジトリへ Issue を移譲する](/articles/transferring-an-issue-to-another-repository)」を参照) | | | **X** | **X** | **X** | +| [リポジトリに指定されたコードオーナーとしてのアクション](/articles/about-code-owners) | | | **X** | **X** | **X** | +| [プルリクエストのドラフトに、レビューの準備ができたことを示すマークを付ける](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | +| [プルリクエストをドラフトに変換する](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | +| プルリクエストのマージ可能性に影響するレビューのサブミット | | | **X** | **X** | **X** | +| プルリクエストに[提案された変更を適用する](/articles/incorporating-feedback-in-your-pull-request) | | | **X** | **X** | **X** | +| [ステータスチェック](/articles/about-status-checks)の作成 | | | **X** | **X** | **X** |{% ifversion fpt %} +| [GitHub Actions ワークフロー](/actions/automating-your-workflow-with-github-actions/) の作成、編集、実行、再実行、キャンセル | | | **X** | **X** | **X** {% endif %} -| リリースの作成と編集 | | | **X** | **X** | **X** | -| ドラフトリリースの表示 | | | **X** | **X** | **X** | -| リポジトリの説明の編集 | | | | **X** | **X** |{% ifversion fpt or ghae %} -| [パッケージの表示とインストール](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | -| [パッケージの公開](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | -| | | | | | | -| {% ifversion fpt or ghes > 3.0 %}[パッケージを削除および復元する](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[パッケージを削除する](/packages/learn-github-packages/deleting-a-package){% endif %} | | | | | **X** | {% endif %} -| [Topics](/articles/classifying-your-repository-with-topics) の管理 | | | | **X** | **X** | -| Wiki の有効化および Wiki 編集者の制限 | | | | **X** | **X** | -| プロジェクトボードの有効化 | | | | **X** | **X** | -| [プルリクエストのマージ](/articles/configuring-pull-request-merges)の設定 | | | | **X** | **X** | -| [{% data variables.product.prodname_pages %} の公開ソース](/articles/configuring-a-publishing-source-for-github-pages)の設定 | | | | **X** | **X** | -| [保護されたブランチへのプッシュ](/articles/about-protected-branches) | | | | **X** | **X** | -| [リポジトリソーシャルカードの作成と編集](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% ifversion fpt %} -| [リポジトリでのインタラクション](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)を制限する | | | | **X** | **X** +| リリースの作成と編集 | | | **X** | **X** | **X** | +| ドラフトリリースの表示 | | | **X** | **X** | **X** | +| リポジトリの説明の編集 | | | | **X** | **X** |{% ifversion fpt or ghae %} +| [パッケージの表示とインストール](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | +| [パッケージの公開](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | +| | | | | | | +| {% ifversion fpt or ghes > 3.0 %}[パッケージを削除および復元する](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[パッケージを削除する](/packages/learn-github-packages/deleting-a-package){% endif %} | | | | | **X** | {% endif %} +| [Topics](/articles/classifying-your-repository-with-topics) の管理 | | | | **X** | **X** | +| Wiki の有効化および Wiki 編集者の制限 | | | | **X** | **X** | +| プロジェクトボードの有効化 | | | | **X** | **X** | +| [プルリクエストのマージ](/articles/configuring-pull-request-merges)の設定 | | | | **X** | **X** | +| [{% data variables.product.prodname_pages %} の公開ソース](/articles/configuring-a-publishing-source-for-github-pages)の設定 | | | | **X** | **X** | +| [保護されたブランチへのプッシュ](/articles/about-protected-branches) | | | | **X** | **X** | +| [リポジトリソーシャルカードの作成と編集](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% ifversion fpt %} +| [リポジトリでのインタラクション](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)を制限する | | | | **X** | **X** {% endif %} -| Issue の削除 (「[Issue を削除する](/articles/deleting-an-issue)」を参照) | | | | | **X** | -| 保護されたブランチでのプルリクエストのマージ（レビューの承認がなくても） | | | | | **X** | -| [リポジトリのコードオーナーの定義](/articles/about-code-owners) | | | | | **X** | -| リポジトリを Team に追加する (詳細は「[Organization リポジトリへの Team のアクセスを管理する](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)」を参照) | | | | | **X** | -| [外部のコラボレータのリポジトリへのアクセスの管理](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | -| [リポジトリの可視性の変更](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | -| リポジトリのテンプレート化 (「[テンプレートリポジトリを作成する](/articles/creating-a-template-repository)」を参照) | | | | | **X** | -| リポジトリ設定の変更 | | | | | **X** | -| Team およびコラボレータのリポジトリへのアクセス管理 | | | | | **X** | -| リポジトリのデフォルトブランチ編集 | | | | | **X** |{% ifversion fpt or ghes > 3.0 %} -| リポジトリのデフォルトブランチの名前を変更する（「[ブランチの名前を変更する](/github/administering-a-repository/renaming-a-branch)」を参照） | | | | | **X** | -| リポジトリのデフォルトブランチを変更する（「[ブランチの名前を変更する](/github/administering-a-repository/renaming-a-branch)」を参照） | | | **X** | **X** | **X** +| Issue の削除 (「[Issue を削除する](/articles/deleting-an-issue)」を参照) | | | | | **X** | +| 保護されたブランチでのプルリクエストのマージ（レビューの承認がなくても） | | | | | **X** | +| [リポジトリのコードオーナーの定義](/articles/about-code-owners) | | | | | **X** | +| リポジトリを Team に追加する (詳細は「[Organization リポジトリへの Team のアクセスを管理する](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)」を参照) | | | | | **X** | +| [外部のコラボレータのリポジトリへのアクセスの管理](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | +| [リポジトリの可視性の変更](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | +| リポジトリのテンプレート化 (「[テンプレートリポジトリを作成する](/articles/creating-a-template-repository)」を参照) | | | | | **X** | +| リポジトリ設定の変更 | | | | | **X** | +| Team およびコラボレータのリポジトリへのアクセス管理 | | | | | **X** | +| リポジトリのデフォルトブランチ編集 | | | | | **X** |{% ifversion fpt or ghes > 3.0 or ghae-next %} +| リポジトリのデフォルトブランチの名前を変更する（「[ブランチの名前を変更する](/github/administering-a-repository/renaming-a-branch)」を参照） | | | | | **X** | +| リポジトリのデフォルトブランチを変更する（「[ブランチの名前を変更する](/github/administering-a-repository/renaming-a-branch)」を参照） | | | **X** | **X** | **X** {% endif %} -| Webhookおよびデプロイキーの管理 | | | | | **X** |{% ifversion fpt %} -| [プライベートリポジトリ用のデータ利用設定を管理する](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **X** +| Webhookおよびデプロイキーの管理 | | | | | **X** |{% ifversion fpt %} +| [プライベートリポジトリ用のデータ利用設定を管理する](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **X** {% endif %} -| [リポジトリのフォークポリシーを管理する](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | -| [リポジトリの Organization への移譲](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | -| [リポジトリの削除または Organization 外への移譲](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | -| [リポジトリのアーカイブ](/articles/about-archiving-repositories) | | | | | **X** |{% ifversion fpt %} -| スポンサーボタンの表示 (「[リポジトリにスポンサーボタンを表示する](/articles/displaying-a-sponsor-button-in-your-repository)」を参照) | | | | | **X** +| [リポジトリのフォークポリシーを管理する](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | +| [リポジトリの Organization への移譲](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | +| [リポジトリの削除または Organization 外への移譲](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | +| [リポジトリのアーカイブ](/articles/about-archiving-repositories) | | | | | **X** |{% ifversion fpt %} +| スポンサーボタンの表示 (「[リポジトリにスポンサーボタンを表示する](/articles/displaying-a-sponsor-button-in-your-repository)」を参照) | | | | | **X** {% endif %} -| JIRA や Zendesk などの外部リソースに対する自動リンク参照を作成します (「[外部リソースを参照する自動リンクの設定](/articles/configuring-autolinks-to-reference-external-resources)」を参照)。 | | | | | **X** |{% ifversion fpt %} -| リポジトリの [{% data variables.product.prodname_discussions %} の有効化](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) | | | | **X** | **X** | -| {% data variables.product.prodname_discussions %} の[カテゴリの作成および編集](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) | | | | **X** | **X** | -| [ディスカッションを別のカテゴリに移動する](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| 新しいリポジトリに[ディスカッションを転送する](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [ピン止めされたディスカッションを管理する](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [Issue をまとめてディスカッションに変換する](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [ディスカッションのロックとロック解除](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [Issue を個別にディスカッションに変換する](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [新しいディスカッションを作成し、既存のディスカッションにコメントする](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** | -| [ディスカッションの削除](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion) | | | | **X** | **X** |{% endif %}{% ifversion fpt %} -| [codespaces](/codespaces/about-codespaces)の作成 | | | **X** | **X** | **X** +| JIRA や Zendesk などの外部リソースに対する自動リンク参照を作成します (「[外部リソースを参照する自動リンクの設定](/articles/configuring-autolinks-to-reference-external-resources)」を参照)。 | | | | | **X** |{% ifversion fpt %} +| リポジトリの [{% data variables.product.prodname_discussions %} の有効化](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) | | | | **X** | **X** | +| {% data variables.product.prodname_discussions %} の[カテゴリの作成および編集](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) | | | | **X** | **X** | +| [ディスカッションを別のカテゴリに移動する](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| 新しいリポジトリに[ディスカッションを転送する](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [ピン止めされたディスカッションを管理する](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Issue をまとめてディスカッションに変換する](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [ディスカッションのロックとロック解除](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [Issue を個別にディスカッションに変換する](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [新しいディスカッションを作成し、既存のディスカッションにコメントする](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** | +| [ディスカッションの削除](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion) | | | | **X** | **X** |{% endif %}{% ifversion fpt %} +| [codespaces](/codespaces/about-codespaces)の作成 | | | **X** | **X** | **X** {% endif %} ### セキュリティ機能のアクセス許可要件 diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md index c56656df18..1652a61b15 100644 --- a/translations/ja-JP/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md +++ b/translations/ja-JP/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md @@ -36,7 +36,7 @@ Organization のすべてのリポジトリについて {% data variables.produc {% endif %} -{% ifversion fpt or ghes > 2.22 %} +{% ifversion fpt or ghes > 2.22 or ghae-next %} ## Organization の {% data variables.product.prodname_actions %} 権限の管理 @@ -63,7 +63,12 @@ Organization のワークフローをすべて無効にすることも、Organiz {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.settings-sidebar-actions %} -1. [**Policies**] で [**Allow select actions**] を選択し、必要なアクションをリストに追加します。 ![許可リストにアクションを追加する](/assets/images/help/organizations/actions-policy-allow-list.png) +1. [**Policies**] で [**Allow select actions**] を選択し、必要なアクションをリストに追加します。 + {%- ifversion ghes %} + ![許可リストにアクションを追加する](/assets/images/help/organizations/actions-policy-allow-list.png) + {%- else %} + ![許可リストにアクションを追加する](/assets/images/enterprise/github-ae/organizations/actions-policy-allow-list.png) + {%- endif %} 1. [**Save**] をクリックします。 {% endif %} @@ -71,7 +76,9 @@ Organization のワークフローをすべて無効にすることも、Organiz {% ifversion fpt %} ## パブリックフォークからのワークフローに対する必須の承認の設定 -{% data reusables.actions.workflow-run-approve-public-fork %} 以下の手順で、Organizationに対してこの動作を設定できます。 この設定を変更すると、Enterpriseレベルでの設定が上書きされます。 +{% data reusables.actions.workflow-run-approve-public-fork %} + +You can configure this behavior for an organization using the procedure below. この設定を変更すると、Enterpriseレベルでの設定が上書きされます。 {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/transferring-organization-ownership.md b/translations/ja-JP/content/organizations/managing-organization-settings/transferring-organization-ownership.md index e596e5d8bf..b88f980375 100644 --- a/translations/ja-JP/content/organizations/managing-organization-settings/transferring-organization-ownership.md +++ b/translations/ja-JP/content/organizations/managing-organization-settings/transferring-organization-ownership.md @@ -15,6 +15,13 @@ topics: shortTitle: 所有権の移譲 --- +{% ifversion fpt %} +{% note %} + +**注釈:** {% data reusables.enterprise-accounts.invite-organization %} + +{% endnote %}{% endif %} + 1. もしあなたが *owner* の権限を持つ唯一のメンバーである場合、他の Organization メンバーにオーナーロールを付与します。 詳細は「[Organizationのオーナーの指名](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization#appointing-an-organization-owner)」を参照してください。 2. 新しいオーナーに連絡し、そのオーナーが [Organization の設定にアクセス](/articles/accessing-your-organization-s-settings)できることを確認します。 {% ifversion fpt %} diff --git a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md index 21b5aac81c..a34caf2b35 100644 --- a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md +++ b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md @@ -13,6 +13,8 @@ topics: shortTitle: SAML SSOを使うIAM --- +{% data reusables.enterprise-accounts.emu-saml-note %} + ## SAML SSO について {% data reusables.saml.dotcom-saml-explanation %} diff --git a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md index fe45c451d6..b7b63afe64 100644 --- a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md +++ b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md @@ -12,6 +12,8 @@ topics: - Teams --- +{% data reusables.enterprise-accounts.emu-scim-note %} + [SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on) を Organization 内で使うと、Organization のメンバーの {% data variables.product.product_name %}へのアクセスの追加、管理、削除のための SCIM を実装できます。 たとえば、管理者は Organization のメンバーのデプロビジョニングに SCIM を使い、自動的にメンバーを Organization から削除できます。 SCIM を実装せずに SAML SSO を使った場合、自動のプロビジョニング解除は行われません。 Organization のメンバーのアクセスが ldP から削除された後、セッションの有効期限が切れても、そのメンバーは Organization から自動的には削除されません。 認証済みのトークンにより、セッションが期限切れになった後も Organization へのアクセスが許可されます。 アクセスを削除するには、Organization の管理者は手動で認証済みのトークンを Organization から削除するか、その削除を SCIM で自動化します。 diff --git a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md index 7763e47502..0e3390f9aa 100644 --- a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md +++ b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md @@ -17,6 +17,8 @@ topics: shortTitle: Teamの同期の管理 --- +{% data reusables.enterprise-accounts.emu-scim-note %} + {% data reusables.gated-features.okta-team-sync %} ## Team の同期について @@ -31,6 +33,8 @@ IdP と {% data variables.product.product_name %} の間で Team の同期を有 Enterprise アカウントが所有する Organization に対して Team の同期を有効化することもできます。 詳細は、「[Enterprise アカウントでセキュリティ設定を強制する](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account)」を参照してください。 +{% data reusables.enterprise-accounts.team-sync-override %} + {% data reusables.identity-and-permissions.team-sync-usage-limits %} ## Team の同期を有効化する diff --git a/translations/ja-JP/content/organizations/organizing-members-into-teams/creating-a-team.md b/translations/ja-JP/content/organizations/organizing-members-into-teams/creating-a-team.md index da1fe0a2de..b9b28157d8 100644 --- a/translations/ja-JP/content/organizations/organizing-members-into-teams/creating-a-team.md +++ b/translations/ja-JP/content/organizations/organizing-members-into-teams/creating-a-team.md @@ -25,11 +25,13 @@ Organization のオーナーと親チームのメンテナだけが親の下に {% data reusables.organizations.team_description %} {% data reusables.organizations.create-team-choose-parent %} {% ifversion fpt %} -1. オプションとして、Organization またはEnterprise アカウントが Team 同期を使用している場合は、Team にアイデンティティプロバイダグループを接続するために、[Identity Provider Groups] ドロップダウンメニューから アイデンティティプロバイダグループを 5 つまで選択します。 詳しい情報については「[アイデンティティプロバイダグループとTeamの同期](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)」を参照してください。 ![アイデンティティプロバイダグループを選択するドロップダウンメニュー](/assets/images/help/teams/choose-an-idp-group.png) +1. Optionally, if your organization or enterprise account uses team synchronization or your enterprise uses {% data variables.product.prodname_emus %}, connect an identity provider group to your team. + * If your enterprise uses {% data variables.product.prodname_emus %}, use the "Identity Provider Groups" drop-down menu, and select a single identity provider group to connect to the new team. For more information, "[Managing team memberships with identity provider groups](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)." + * If your organization or enterprise account uses team synchronization, use the "Identity Provider Groups" drop-down menu, and select up to five identity provider groups to connect to the new team. 詳しい情報については「[アイデンティティプロバイダグループとTeamの同期](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)」を参照してください。 ![アイデンティティプロバイダグループを選択するドロップダウンメニュー](/assets/images/help/teams/choose-an-idp-group.png) {% endif %} {% data reusables.organizations.team_visibility %} {% data reusables.organizations.create_team %} -9. 任意で、[Team のアクセスを Organization リポジトリに与えます](/articles/managing-team-access-to-an-organization-repository)。 +1. 任意で、[Team のアクセスを Organization リポジトリに与えます](/articles/managing-team-access-to-an-organization-repository)。 ## 参考リンク diff --git a/translations/ja-JP/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md b/translations/ja-JP/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md index 0d0528a2d0..f6babbdad6 100644 --- a/translations/ja-JP/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md +++ b/translations/ja-JP/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md @@ -45,8 +45,11 @@ Any team members that have set their status to "Busy" will not be selected for r 7. [How many team members should be assigned to review?] でドロップダウンメニューを使用し、各プルリクエストに割り当てるレビュー担当者の数を選択します。 ![[Number of reviewers] ドロップダウン](/assets/images/help/teams/review-assignment-number.png) 8. [Routing algorithm] のドロップダウンメニューで、使用するアルゴリズムを選択します。 詳細は、「[ルーティングアルゴリズム](#routing-algorithms)」を参照してください。 ![[Routing algorithm] ドロップダウン](/assets/images/help/teams/review-assignment-algorithm.png) 9. オプションで、Team の特定メンバーを常にスキップする場合は、[**Never assign certain team members**] を選択します。 次に、スキップする 1 つ以上の Team メンバーを選択します。 ![[Never assign certain team members] チェックボックスとラジオボタン](/assets/images/help/teams/review-assignment-skip-members.png) -10. オプションで、プルレビューリクエストごとのコードレビュー割り当てによって選択された Teamメンバーのみに通知する場合は、[Notifications] で[**If assigning team members, don't notify the entire team.**] を選択します。 ![コードレビューの割当ての通知](/assets/images/help/teams/review-assignment-notifications.png) -11. [**Save changes**] をクリックします。 +10. Optionally, to only notify the team members chosen by code review assignment for each pull review request, under "Notifications" select **If assigning team members, don't notify the entire team.** ![Code review assignment notifications](/assets/images/help/teams/review-assignment-notifications.png){% ifversion fpt or ghae or ghes > 3.2 %} +11. Optionally, to include members of child teams as potential reviewers when assigning requests, select **Child team members**. +12. Optionally, to count any members whose review has already been requested against the total number of members to assign, select **Count existing requests**. +13. Optionally, to remove the review request from the team when assigning team members, select **Team review request**.{% endif %} +14. [**Save changes**] をクリックします。 ## コードレビューの割り当てを無効化する {% data reusables.profile.access_org %} diff --git a/translations/ja-JP/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/ja-JP/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md index 19ffaca493..6df45704a7 100644 --- a/translations/ja-JP/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md +++ b/translations/ja-JP/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md @@ -16,6 +16,8 @@ shortTitle: IdPとの同期 {% data reusables.gated-features.okta-team-sync %} +{% data reusables.enterprise-accounts.emu-scim-note %} + ## Team の同期について {% data reusables.identity-and-permissions.about-team-sync %} @@ -26,6 +28,8 @@ shortTitle: IdPとの同期 いったん {% data variables.product.prodname_dotcom %} Team が IdP グループに接続されたら、IdP 管理者はアイデンティティプロバイダを通して Team メンバーシップを変更する必要があります。 {% data variables.product.product_name %}で、{% ifversion fpt %} または API を使用して{% endif %}Team のメンバーシップを管理することはできません。 +{% ifversion fpt %}{% data reusables.enterprise-accounts.team-sync-override %}{% endif %} + {% ifversion fpt %} IdP を通じた Team メンバーシップ変更はすべて、Team 同期ボットによる変更として {% data variables.product.product_name %} の Audit log に記載されます。 IdP は、Team メンバーシップのデータを 1 時間に 1 回 {% data variables.product.prodname_dotcom %} に送信します。 Team を IdP グループに接続すると、Team メンバーが削除される場合があります。 詳細は「[同期される Team のメンバーに関する要件](#requirements-for-members-of-synchronized-teams)」を参照してください。 {% endif %} @@ -54,8 +58,6 @@ IdP グループに接続された Team を含めて {% data variables.product.p 意図しない Team メンバーの削除を避けるために、Organization または Enterprise アカウントで SAML SSO を施行し、メンバーシップデータを同期するため新しい Team を作成し、IdP グループのメンバーシップを確認してから既存の Team を同期することをおすすめします。 For more information, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)" and "[Enforcing SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account)." -Organization が Enterprise アカウントによって所有されている場合、その Enterprise アカウントに Team の同期を有効化すると、Organization レベルの Team の同期はオーバーライドされます。 詳しい情報については、「[Enterprise アカウントで Organization の Team 同期を管理する](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)」参照してください。 - {% endif %} ## 必要な環境 diff --git a/translations/ja-JP/content/packages/learn-github-packages/installing-a-package.md b/translations/ja-JP/content/packages/learn-github-packages/installing-a-package.md index e0d328a812..25e91cc97c 100644 --- a/translations/ja-JP/content/packages/learn-github-packages/installing-a-package.md +++ b/translations/ja-JP/content/packages/learn-github-packages/installing-a-package.md @@ -18,7 +18,7 @@ versions: ## パッケージのインストールについて -{% data variables.product.product_name %}を検索して、自分のプロジェクトにインストールできるパッケージを{% data variables.product.prodname_registry %}で見つけることができます。 詳しい情報については「[パッケージを{% data variables.product.prodname_registry %}で検索する](/github/searching-for-information-on-github/searching-for-packages)」を参照してください。 +{% data variables.product.product_name %}を検索して、自分のプロジェクトにインストールできるパッケージを{% data variables.product.prodname_registry %}で見つけることができます。 詳しい情報については「[パッケージを{% data variables.product.prodname_registry %}で検索する](/search-github/searching-on-github/searching-for-packages)」を参照してください。 パッケージを見つけたなら、そのパッケージの説明と、パッケージのページにあるインストールと利用方法の指示を読むことができます。 diff --git a/translations/ja-JP/content/packages/learn-github-packages/viewing-packages.md b/translations/ja-JP/content/packages/learn-github-packages/viewing-packages.md index 4db129c1e7..d1b6999929 100644 --- a/translations/ja-JP/content/packages/learn-github-packages/viewing-packages.md +++ b/translations/ja-JP/content/packages/learn-github-packages/viewing-packages.md @@ -64,4 +64,4 @@ versions: ## 参考リンク -- [パッケージの検索](/github/searching-for-information-on-github/searching-for-packages) +- [パッケージの検索](/search-github/searching-on-github/searching-for-packages) diff --git a/translations/ja-JP/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md b/translations/ja-JP/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md index 65fe520d9a..36aef73260 100644 --- a/translations/ja-JP/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md +++ b/translations/ja-JP/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md @@ -15,8 +15,6 @@ shortTitle: Actionsでの公開とインストール {% data reusables.package_registry.packages-ghes-release-stage %} {% data reusables.package_registry.packages-ghae-release-stage %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## {% data variables.product.prodname_actions %}との{% data variables.product.prodname_registry %}について diff --git a/translations/ja-JP/content/packages/quickstart.md b/translations/ja-JP/content/packages/quickstart.md index 027628340b..b1b7ec6e83 100644 --- a/translations/ja-JP/content/packages/quickstart.md +++ b/translations/ja-JP/content/packages/quickstart.md @@ -10,8 +10,6 @@ shortTitle: クイックスタート --- {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## はじめに diff --git a/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md index d285780010..862bd94d4d 100644 --- a/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md +++ b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md @@ -160,7 +160,11 @@ $ npm login --scope=@OWNER --registry=https://HOSTNAME/_regist デフォルトでは、パッケージは1つのOrganizationから追加できます。 詳しい情報については「[他のOrganizationからのパッケージのインストール](#installing-packages-from-other-organizations)」を参照してください。 -また、*.npmrc*ファイルをプロジェクトに追加して、パッケージのインストールのすべてのリクエストが{% data variables.product.prodname_registry %}を経由するようにしなければなりません。 すべてのパッケージリクエストを{% data variables.product.prodname_registry %}を経由させると、*npmjs.com*からスコープ付き及びスコープ付きではないパッケージの両方を利用できます。 詳しい情報については npm ドキュメンテーションの「[npm-scope](https://docs.npmjs.com/misc/scope)」を参照してください。 +You also need to add the *.npmrc* file to your project so that all requests to install packages will {% ifversion ghae %}be routed to{% else %}go through{% endif %} {% data variables.product.prodname_registry %}. {% ifversion fpt or ghes > 2.21 %}When you route all package requests through {% data variables.product.prodname_registry %}, you can use both scoped and unscoped packages from *npmjs.org*. For more information, see "[npm-scope](https://docs.npmjs.com/misc/scope)" in the npm documentation.{% endif %} + +{% ifversion ghae %} +By default, you can only use npm packages hosted on your enterprise, and you will not be able to use unscoped packages. For more information on package scoping, see "[npm-scope](https://docs.npmjs.com/misc/scope)" in the npm documentation. If required, {% data variables.product.prodname_dotcom %} support can enable an upstream proxy to npmjs.org. Once an upstream proxy is enabled, if a requested package isn't found on your enterprise, {% data variables.product.prodname_registry %} makes a proxy request to npmjs.org. +{% endif %} {% data reusables.package_registry.authenticate-step %} {% data reusables.package_registry.create-npmrc-owner-step %} diff --git a/translations/ja-JP/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md b/translations/ja-JP/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md index 1902b2c5ac..a2f10325f1 100644 --- a/translations/ja-JP/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md +++ b/translations/ja-JP/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md @@ -12,7 +12,11 @@ shortTitle: サイトの可視性の変更 ## {% data variables.product.prodname_pages %} サイトのアクセス制御について -プロジェクトサイトが {% data variables.product.prodname_ghe_cloud %} を使用する Organization が所有するプライベートもしくは内部リポジトリから公開される場合、そのサイトのアクセス制御を管理できます。 アクセス制御を使用すると、インターネット上のすべての人にサイトを公開する（パブリック）か、リポジトリへの読み取りアクセス権を持つ人限定で公開する（プライベート）かを選択できます。 プライベートで公開されたサイトでは、社内のドキュメントやナレッジベースを Enterprise のメンバーと共有できます。 Organization サイトのアクセス制御を管理することはできません。 {% data variables.product.prodname_pages %}サイトの種類に関する詳しい情報については「[{% data variables.product.prodname_pages %}について](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)」を参照してください。 +With access control for {% data variables.product.prodname_pages %}, you can restrict access to your {% data variables.product.prodname_pages %} site by publishing the site privately. A privately published site can only be accessed by people with read access to the repository the site is published from. You can use privately published sites to share your internal documentation or knowledge base with members of your enterprise. + +If your enterprise uses {% data variables.product.prodname_emus %}, all {% data variables.product.prodname_pages %} sites are privately published. For more information about {% data variables.product.prodname_emus %}, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." + +If your organization uses {% data variables.product.prodname_ghe_cloud %} without {% data variables.product.prodname_emus %}, you can choose to publish your sites privately or publicly to anyone on the internet. Access control is available for project sites that are published from a private or internal repository that are owned by the organization. Organization サイトのアクセス制御を管理することはできません。 {% data variables.product.prodname_pages %}サイトの種類に関する詳しい情報については「[{% data variables.product.prodname_pages %}について](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)」を参照してください。 プライベートのサイトは、パブリックのサイトとは異なるサブドメインで利用できます。 これにより、{% data variables.product.prodname_pages %} サイトが公開された瞬間から安全になります。 diff --git a/translations/ja-JP/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md b/translations/ja-JP/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md index 118f79b4a2..c82498c682 100644 --- a/translations/ja-JP/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md +++ b/translations/ja-JP/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md @@ -22,6 +22,12 @@ shortTitle: HTTPSでのサイトの保護 {% data reusables.pages.private_pages_are_public_warning %} +{% note %} + +**Note:** RFC3280 states that the maximum length of the common name should be 64 characters. Therefore, the entire domain name of your {% data variables.product.prodname_pages %} site must be less than 64 characters long for a certificate to be successfully created. + +{% endnote %} + ## あなたの {% data variables.product.prodname_pages %} サイトに HTTPS を強制する {% data reusables.pages.navigate-site-repo %} diff --git a/translations/ja-JP/content/repositories/archiving-a-github-repository/archiving-repositories.md b/translations/ja-JP/content/repositories/archiving-a-github-repository/archiving-repositories.md index 2d8fdfb98a..4b3997981b 100644 --- a/translations/ja-JP/content/repositories/archiving-a-github-repository/archiving-repositories.md +++ b/translations/ja-JP/content/repositories/archiving-a-github-repository/archiving-repositories.md @@ -32,7 +32,7 @@ topics: リポジトリがアーカイブされると、その Issue、プルリクエスト、コード、ラベル、マイルストーン、プロジェクト、wiki、リリース、コミット、タグ、ブランチ、リアクション、コードスキャンアラート、およびコメントが読み取り専用になります。 アーカイブされたリポジトリに変更を加えるには、まずそのリポジトリのアーカイブ解除をしなければなりません。 -アーカイブされたリポジトリに対して検索ができます。 詳しい情報については[リポジトリの検索](/articles/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)を参照してください。 詳しい情報については[リポジトリの検索](/articles/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)を参照してください。 詳しい情報については[Issueやプルリクエストの検索](/articles/searching-issues-and-pull-requests/#search-based-on-whether-a-repository-is-archived)を参照してください。 +アーカイブされたリポジトリに対して検索ができます。 詳しい情報については[リポジトリの検索](/search-github/searching-on-github/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)を参照してください。 詳しい情報については[リポジトリの検索](/articles/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)を参照してください。 詳しい情報については[Issueやプルリクエストの検索](/search-github/searching-on-github/searching-issues-and-pull-requests/#search-based-on-whether-a-repository-is-archived)を参照してください。 ## リポジトリをアーカイブへ保管 diff --git a/translations/ja-JP/content/repositories/archiving-a-github-repository/backing-up-a-repository.md b/translations/ja-JP/content/repositories/archiving-a-github-repository/backing-up-a-repository.md index b8c4f555c7..545aec05dd 100644 --- a/translations/ja-JP/content/repositories/archiving-a-github-repository/backing-up-a-repository.md +++ b/translations/ja-JP/content/repositories/archiving-a-github-repository/backing-up-a-repository.md @@ -36,7 +36,7 @@ topics: - [プロジェクト](/rest/reference/projects#list-repository-projects) {% endif %} -{% ifversion ghes or ghae %}バックアップしたいすべての内容のローカルバージョンができたなら、zipアーカイブを作成して{% else %}アーカイブがダウンロードできたなら{% endif %}外部ハードディスクにコピーするか、[Google Drive](https://www.google.com/drive/)あるいは[ Dropbox](https://www.dropbox.com/)などのクラウドベースのバックアップサービスにアップロードしてください。 +Once you have {% ifversion ghes or ghae %}a local version of all the content you want to back up, you can create a zip archive and {% else %}downloaded your archive, you can {% endif %}copy it to an external hard drive and/or upload it to a cloud-based backup or storage service such as [Azure Blob Storage](https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-overview/), [Google Drive](https://www.google.com/drive/) or [Dropbox](https://www.dropbox.com/). {% ifversion fpt %} ## サードパーティのバックアップツール diff --git a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md index d71922e91c..ea3621b925 100644 --- a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md +++ b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md @@ -28,13 +28,13 @@ shortTitle: Change the default branch {% endnote %} {% endif %} -{% ifversion fpt or ghes > 3.0 %} +{% ifversion fpt or ghes > 3.0 or ghae-next %} デフォルトブランチの名前は変更することもできます。 詳しい情報については、「[ブランチの名前を変更する](/github/administering-a-repository/renaming-a-branch)」を参照してください。 {% endif %} -{% ifversion fpt or ghes > 2.22 %} +{% ifversion fpt or ghes > 2.22 or ghae-next %} {% data reusables.branches.set-default-branch %} diff --git a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md index 54d7877cf8..d7596f2418 100644 --- a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md +++ b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md @@ -5,6 +5,7 @@ permissions: People with write permissions to a repository can rename a branch i versions: fpt: '*' ghes: '>=3.1' + ghae: next topics: - Repositories redirect_from: diff --git a/translations/ja-JP/content/repositories/creating-and-managing-repositories/about-repositories.md b/translations/ja-JP/content/repositories/creating-and-managing-repositories/about-repositories.md index 7a937f2603..88ab63844f 100644 --- a/translations/ja-JP/content/repositories/creating-and-managing-repositories/about-repositories.md +++ b/translations/ja-JP/content/repositories/creating-and-managing-repositories/about-repositories.md @@ -74,7 +74,7 @@ Organization のオーナーは、Organization 内で作成されたすべての {% data reusables.repositories.internal-repo-default %} -Enterprise が所有するすべての Organization からユーザが削除されると、そのユーザの内部リポジトリのフォークは自動的に削除されます。 +Any member of the enterprise can fork any internal repository owned by an organization in the enterprise. The forked repository will belong to the member's user account, and the visibility of the fork will be private. Enterprise が所有するすべての Organization からユーザが削除されると、そのユーザの内部リポジトリのフォークは自動的に削除されます。 {% endif %} ## リポジトリでコンテンツと diff の表示を制限する @@ -107,6 +107,7 @@ diff はきわめて大きくなることがあるため、コミット、プル ## 参考リンク - 「[新しいリポジトリを作成する](/articles/creating-a-new-repository)」 +- 「[フォークについて](/github/collaborating-with-pull-requests/working-with-forks/about-forks)」 - [Issue とプルリクエストでのコラボレーション](/categories/collaborating-with-issues-and-pull-requests) - 「[{% data variables.product.prodname_dotcom %}での作業を管理する](/categories/managing-your-work-on-github/)」 - [リポジトリの管理](/categories/administering-a-repository) diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md index 33fea40dfb..9bb92e5099 100644 --- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md +++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md @@ -46,18 +46,19 @@ Lisa, M., & Bot, H. (2017). My Research Software (Version 2.0.4) [Computer softw {% raw %} ``` -@misc{Lisa_My_Research_Software_2017, +@software{Lisa_My_Research_Software_2017, author = {Lisa, Mona and Bot, Hew}, doi = {10.5281/zenodo.1234}, month = {12}, title = {{My Research Software}}, url = {https://github.com/github/linguist}, + version = {2.0.4}, year = {2017} } ``` {% endraw %} -Note the example above produces a _software_ citation (i.e., `@misc` type in BibTeX rather than `@article`). +Note the example above produces a _software_ citation (i.e., `@software` type in BibTeX rather than `@article`). For more information, see the [Citation File Format](https://citation-file-format.github.io/) website. @@ -67,9 +68,15 @@ When you add a `CITATION.cff` file to the default branch of your repository, it ## Citing something other than software -If you would prefer the GitHub citation information to link to another resource such as a research paper then you can use the `preferred-citation` override in CFF. +If you would prefer the {% data variables.product.prodname_dotcom %} citation information to link to another resource such as a research article, then you can use the `preferred-citation` override in CFF with the following types. -Extended CITATION.cff file describing the software, but linking to a research paper as the preferred citation: +| Resource | 種類 | +| ---------------- | ------------------ | +| Research article | `article` | +| Conference paper | `conference-paper` | +| Book | `book` | + +Extended CITATION.cff file describing the software, but linking to a research article as the preferred citation: ``` cff-version: 1.2.0 @@ -132,6 +139,10 @@ Lisa, M., & Bot, H. (2021). My awesome research software. Journal Title, 1(1), 1 ``` {% endraw %} +## Citing a dataset + +If your repository contains a dataset, you can set `type: dataset` in your `CITATION.cff` file to produce a data citation string output in the {% data variables.product.prodname_dotcom %} citation prompt. + ## Other citation files The GitHub citation feature will also detect a small number of additional files that are often used by communities and projects to describe how they would like their work to be cited. diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md index 6dd810b545..3b0af1fc1b 100644 --- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md +++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md @@ -29,7 +29,7 @@ Topics を利用すれば、特定の領域に関するリポジトリを調べ {% ifversion ghae %}内部{% else %}パブリック、内部、{% endif %}およびプライベートリポジトリも Topics を持つことができますが、Topics の検索結果で見えるプライベートリポジトリはアクセス権を持っているものだけです。 -特定のトピックに関連付けられているリポジトリを検索できます。 詳しい情報については[リポジトリの検索](/articles/searching-for-repositories#search-by-topic)を参照してください。 また、{% data variables.product.product_name %} 上でトピックのリストを検索することもできます。 詳細は「[トピックを検索する](/articles/searching-topics)」を参照してください。 +特定のトピックに関連付けられているリポジトリを検索できます。 詳しい情報については[リポジトリの検索](/search-github/searching-on-github/searching-for-repositories#search-by-topic)を参照してください。 また、{% data variables.product.product_name %} 上でトピックのリストを検索することもできます。 詳細は「[トピックを検索する](/search-github/searching-on-github/searching-topics)」を参照してください。 ## Topics をリポジトリに追加する diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md index 2d3634b9e5..0c2294630a 100644 --- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md +++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md @@ -73,7 +73,7 @@ topics: | | The Unlicense | `unlicense` | | | zLib License | `zlib` | -ファミリー ライセンス別で検索すると、結果にはそのファミリーのライセンスがすべて含まれます。 たとえば、`license:gpl` というクエリを実行した結果には、GNU General Public License v2.0 と GNU General Public License v3.0 でライセンスされているリポジトリが含まれます。 詳しい情報については[リポジトリの検索](/articles/searching-for-repositories/#search-by-license)を参照してください。 +ファミリー ライセンス別で検索すると、結果にはそのファミリーのライセンスがすべて含まれます。 たとえば、`license:gpl` というクエリを実行した結果には、GNU General Public License v2.0 と GNU General Public License v3.0 でライセンスされているリポジトリが含まれます。 詳しい情報については[リポジトリの検索](/search-github/searching-on-github/searching-for-repositories/#search-by-license)を参照してください。 ## ライセンスを見つけてもらう 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 2ef588bdf3..a0961da173 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 @@ -43,7 +43,7 @@ shortTitle: Manage GitHub Actions settings {% endif %} -{% ifversion fpt or ghes > 2.22 %} +{% ifversion fpt or ghes > 2.22 or ghae-next %} ## リポジトリの {% data variables.product.prodname_actions %} 権限を管理する @@ -72,14 +72,21 @@ shortTitle: Manage GitHub Actions settings {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.settings-sidebar-actions %} -1. [**Actions permissions**] で [**Allow select actions**] を選択し、必要なアクションをリストに追加します。 ![許可リストにアクションを追加する](/assets/images/help/repository/actions-policy-allow-list.png) +1. [**Actions permissions**] で [**Allow select actions**] を選択し、必要なアクションをリストに追加します。 + {%- ifversion ghes %} + ![許可リストにアクションを追加する](/assets/images/help/repository/actions-policy-allow-list.png) + {%- else %} + ![許可リストにアクションを追加する](/assets/images/enterprise/github-ae/repository/actions-policy-allow-list.png) + {%- endif %} 2. [**Save**] をクリックします。 {% endif %} {% ifversion fpt %} ## パブリックフォークからのワークフローに対する必須の承認の設定 -{% data reusables.actions.workflow-run-approve-public-fork %} You can configure this behavior for a repository using the procedure below. Modifying this setting overrides the configuration set at the organization or enterprise level. +{% data reusables.actions.workflow-run-approve-public-fork %} + +You can configure this behavior for a repository using the procedure below. Modifying this setting overrides the configuration set at the organization or enterprise level. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} @@ -120,6 +127,29 @@ The default permissions can also be configured in the organization settings. If 1. **Save（保存）**をクリックして、設定を適用してください。 {% endif %} +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## Allowing access to components in an internal repository + +{% note %} + +**注釈:** {% data reusables.gated-features.internal-repos %} + +{% endnote %} + +Members of your enterprise can use internal repositories to work on projects without sharing information publicly. For information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-internal-repositories)." + +To configure whether workflows in an internal repository can be accessed from outside the repository: + +1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of the internal repository. +1. Under your repository name, click {% octicon "gear" aria-label="The gear icon" %} **Settings**. +{% data reusables.repositories.settings-sidebar-actions %} +1. Under **Access**, choose one of the access settings: ![Set the access to Actions components](/assets/images/help/settings/actions-access-settings.png) + * **Not accessible** - Workflows in other repositories can't use workflows in this repository. + * **Accessible by any repository in the organization** - Workflows in other repositories can use workflows in this repository as long as they are part of the same organization. + * **Accessible by any repository in the enterprise** - Workflows in other repositories can use workflows in this repository as long as they are part of the same enterprise. +1. **Save（保存）**をクリックして、設定を適用してください。 +{% endif %} + {% ifversion fpt or ghes > 2.22 or ghae %} ## Configuring the retention period for {% data variables.product.prodname_actions %} artifacts and logs in your repository diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md index 8585344b62..50162e9c00 100644 --- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md +++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md @@ -21,6 +21,12 @@ shortTitle: Repository visibility Organization のオーナーは、リポジトリの可視性を変更する機能を Organization のオーナーのみに制限できます。 詳しい情報については「[Organization 内でリポジトリの可視性の変更を制限する](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)」を参照してください。 +{% ifversion fpt %} + +If you're a member of an {% data variables.product.prodname_emu_enterprise %}, your repositories owned by your user account can only be private, and repositories in your enterprise's organizations can only be private or internal. + +{% endif %} + リポジトリの可視性を変更する前に、次の注意点を確認することをお勧めします。 {% ifversion ghes or ghae %} 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 46979f47d2..52be7a8259 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 @@ -34,6 +34,9 @@ topics: リポジトリへの読み取りアクセス権を持つ人はリリースを表示および比較できますが、リリースの管理はリポジトリへの書き込み権限を持つ人のみができます。 詳細は「[リポジトリのリリースを管理する](/github/administering-a-repository/managing-releases-in-a-repository)」を参照してください。 {% ifversion fpt %} + +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)." + リポジトリへの管理者権限を持つユーザは、{% 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 %} オブジェクトを管理する](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)」を参照してください。 {% endif %} diff --git a/translations/ja-JP/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md b/translations/ja-JP/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md new file mode 100644 index 0000000000..249d518517 --- /dev/null +++ b/translations/ja-JP/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md @@ -0,0 +1,93 @@ +--- +title: Automatically generated release notes +intro: You can automatically generate release notes for your GitHub releases +permissions: Repository collaborators and people with write access to a repository can generate and customize automated release notes for a release. +versions: + fpt: '*' +topics: + - Repositories +shortTitle: Automated release notes +--- + +{% note %} + +**注釈:** {% data reusables.repositories.auto-gen-release-public-beta %} + +{% endnote %} + +## About automatically generated release notes + +Automatically generated release notes provide an automated alternative to manually writing release notes for your {% data variables.product.prodname_dotcom %} releases. With automatically generated release notes, you can quickly generate an overview of the contents of a release. You can also customize your automated release notes, using labels to create custom categories to organize pull requests you want to include, and exclude certain labels and users from appearing in the output. + +## Creating automatically generated release notes for a new release + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.releases %} +3. [**Draft a new release**] をクリックします。 ![新しいリリースのドラフトを作成するボタン](/assets/images/help/releases/draft_release_button.png) +4. {% ifversion fpt %}Click **Choose a tag** and type{% else %}Type{% endif %} a version number for your release. Alternatively, select an existing tag. + {% ifversion fpt %} + ![Enter a tag](/assets/images/help/releases/releases-tag-create.png) +5. If you are creating a new tag, click **Create new tag**. ![Confirm you want to create a new tag](/assets/images/help/releases/releases-tag-create-confirm.png) + {% else %} + ![タグ付きバージョンのリリース](/assets/images/enterprise/releases/releases-tag-version.png) +{% endif %} +6. If you have created a new tag, use the drop-down menu to select the branch that contains the project you want to release. + {% ifversion fpt %}![Choose a branch](/assets/images/help/releases/releases-choose-branch.png) + {% else %}![タグ付きブランチのリリース](/assets/images/enterprise/releases/releases-tag-branch.png) + {% endif %} +7. To the top right of the description text box, click **Auto-generate release notes**. ![Auto-generate release notes](/assets/images/help/releases/auto-generate-release-notes.png) +8. Check the generated notes to ensure they include all (and only) the information you want to include. +9. オプションで、コンパイルされたプログラムなどのバイナリファイルをリリースに含めるには、ドラッグアンドドロップするかバイナリボックスで手動で選択します。 ![リリースに DMG ファイルを含める](/assets/images/help/releases/releases_adding_binary.gif) +10. リリースが不安定であり、運用準備ができていないことをユーザに通知するには、[**This is a pre-release**] を選択します。 ![リリースをプレリリースとしてマークするチェックボックス](/assets/images/help/releases/prerelease_checkbox.png) +{%- ifversion fpt %} +11. 必要に応じて、[**Create a discussion for this release**] を選択し、[**Category**] ドロップダウンメニューを選択してリリースディスカッションのカテゴリをクリックします。 ![リリースディスカッションを作成するためのチェックボックスと、カテゴリを選択するドロップダウンメニュー](/assets/images/help/releases/create-release-discussion.png) +{%- endif %} +12. リリースを公開する準備ができている場合は、[**Publish release**] をクリックします。 リリースの作業を後でする場合は、[**Save draft**] をクリックします。 ![[Publish release] と [Save draft] ボタン](/assets/images/help/releases/release_buttons.png) + + +## Creating a template for automatically generated release notes + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.files.add-file %} +3. In the file name field, type `.github/release.yml` to create the `release.yml` file in the `.github` directory. ![Create new file](/assets/images/help/releases/release-yml.png) +4. In the file, specify the pull request labels and authors you want to exclude from this release. You can also create new categories and list the pull request labels to be included in each of them. 詳しい情報については、「[ラベルを管理する](/issues/using-labels-and-milestones-to-track-work/managing-labels)」を参照してください。 + +## 設定例 + +{% raw %} +**release.yml** +```yaml{:copy} +# release.yml + +changelog: + exclude: + labels: + - ignore-for-release + authors: + - octocat + categories: + - title: Breaking Changes 🛠 + labels: + - Semver-Major + - breaking-change + - title: Exciting New Features 🎉 + labels: + - Semver-Minor + - enhancement + - title: Other Changes + labels: + - "*" +``` +{% endraw %} + +## Release template syntax + +| Parameter | 説明 | 必須 | 値 | +|:--------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:---------------------------------------------------------------------------- |:------------------------------------------------------------------------- | +| `変更履歴` | Defines the contents within it as the custom template for your release notes. | 必須. | No value accepted. | +| `除外` | Creates a category of pull requests to be excluded from the release. Can be set at the top-level of the changelog to apply to all categories or applied on a per-category basis. | 任意 | No value accepted. | +| `authors` | Specifies authors to be excluded from the release. | Optional for `exclude` category. | Accepts usernames and bots as values. | +| `カテゴリ` | Defines the nested contents as custom categories to be included in the template. | 任意 | No value accepted. | +| `title` | Creates an individual category. | Required if `categories` parameter exists. | Takes the category name as its value. | +| `labels` | Specifies labels to be used by the enclosing category. | Required if `categories` parameter exists, optional for `exclude` parameter. | Accepts any labels, whether currently existing or planned for the future. | +| `"*"` | Catchall for any pull request not included within a category *above*. If used, it must be added at the end of the file. | 任意 | No value accepted. | diff --git a/translations/ja-JP/content/repositories/releasing-projects-on-github/index.md b/translations/ja-JP/content/repositories/releasing-projects-on-github/index.md index c2c08c4269..77c7e29b78 100644 --- a/translations/ja-JP/content/repositories/releasing-projects-on-github/index.md +++ b/translations/ja-JP/content/repositories/releasing-projects-on-github/index.md @@ -17,6 +17,7 @@ children: - /viewing-your-repositorys-releases-and-tags - /linking-to-releases - /comparing-releases + - /automatically-generated-release-notes - /automation-for-release-forms-with-query-parameters shortTitle: Release projects --- diff --git a/translations/ja-JP/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md b/translations/ja-JP/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md index b12f63d138..ed42b06b08 100644 --- a/translations/ja-JP/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md +++ b/translations/ja-JP/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md @@ -42,14 +42,14 @@ You can create new releases with release notes, @mentions of contributors, and l {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.releases %} 3. [**Draft a new release**] をクリックします。 ![新しいリリースのドラフトを作成するボタン](/assets/images/help/releases/draft_release_button.png) -4. {% ifversion fpt %}Click **Choose a tag** and type{% else %}Type{% endif %} a version number for your release. +4. {% ifversion fpt %}Click **Choose a tag** and type{% else %}Type{% endif %} a version number for your release. Alternatively, select an existing tag. {% ifversion fpt %} ![Enter a tag](/assets/images/help/releases/releases-tag-create.png) -1. Click **Create new tag**. ![Confirm you want to create a new tag](/assets/images/help/releases/releases-tag-create-confirm.png) +1. If you are creating a new tag, click **Create new tag**. ![Confirm you want to create a new tag](/assets/images/help/releases/releases-tag-create-confirm.png) {% else %} ![タグ付きバージョンのリリース](/assets/images/enterprise/releases/releases-tag-version.png) {% endif %} -5. ドロップダウンメニューを使ってリリース対象のプロジェクトを含むブランチを選択します。 +5. If you have created a new tag, use the drop-down menu to select the branch that contains the project you want to release. {% ifversion fpt %}![Choose a branch](/assets/images/help/releases/releases-choose-branch.png) {% else %}![タグ付きブランチのリリース](/assets/images/enterprise/releases/releases-tag-branch.png) {% endif %} @@ -57,7 +57,9 @@ You can create new releases with release notes, @mentions of contributors, and l {%- ifversion fpt or ghes > 3.2 or ghae-issue-4972 %} If you @mention any {% data variables.product.product_name %} users in the description, the published release will include a **Contributors** section with an avatar list of all the mentioned users. {%- endif %} - ![リリースの説明](/assets/images/help/releases/releases_description.png) + {% ifversion fpt %} Alternatively, you can automatically generate your release notes by clicking **Auto-generate release notes**. + {% endif %} + ![リリースの説明](/assets/images/help/releases/releases_description_auto.png) 7. オプションで、コンパイルされたプログラムなどのバイナリファイルをリリースに含めるには、ドラッグアンドドロップするかバイナリボックスで手動で選択します。 ![リリースに DMG ファイルを含める](/assets/images/help/releases/releases_adding_binary.gif) 8. リリースが不安定であり、運用準備ができていないことをユーザに通知するには、[**This is a pre-release**] を選択します。 ![リリースをプレリリースとしてマークするチェックボックス](/assets/images/help/releases/prerelease_checkbox.png) {%- ifversion fpt %} diff --git a/translations/ja-JP/content/repositories/working-with-files/using-files/working-with-non-code-files.md b/translations/ja-JP/content/repositories/working-with-files/using-files/working-with-non-code-files.md index 8d9a31f8ab..2061eeed0d 100644 --- a/translations/ja-JP/content/repositories/working-with-files/using-files/working-with-non-code-files.md +++ b/translations/ja-JP/content/repositories/working-with-files/using-files/working-with-non-code-files.md @@ -188,6 +188,14 @@ GitHub では PDF ドキュメントのレンダリングをサポートして ![レンダリング済み文章変更](/assets/images/help/repository/rendered_prose_changes.png) +{% ifversion fpt or ghes > 3.2 or ghae-issue-5232 %} + +### Disabling Markdown rendering + +{% data reusables.repositories.disabling-markdown-rendering %} + +{% endif %} + ### 属性変更を可視化する 読者に見せる文字部分とは異なり、属性への変更は、レンダリングされたドキュメントでは見えなくなります。Github ではそれをツールチップで示します。 たとえば、リンク URL が、あるウェブサイトから別のものに変更された場合、ツールチップで次のように示されます: 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 42905015ff..b435359419 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 @@ -122,10 +122,10 @@ $ curl -i -u your_username {% data variables.product.api_url_pre %}/use プロンプトが表示されたらOAuthトークンを入力できますが、そのための変数を設定することをお勧めします。 -トークンをシェル履歴に残すことは避けるべきです。`-u "username:$token"`を使用して、`token`の変数を設定すると、トークンはシェル履歴に残りません。 +You can use `-u "your_username:$token"` and set up a variable for `token` to avoid leaving your token in shell history, which should be avoided. ```shell -$ curl -i -u username:$token {% data variables.product.api_url_pre %}/users/octocat +$ curl -i -u your_username:$token {% data variables.product.api_url_pre %}/users/octocat ``` diff --git a/translations/ja-JP/content/rest/overview/api-previews.md b/translations/ja-JP/content/rest/overview/api-previews.md index 9290c7a062..fd0096f1ea 100644 --- a/translations/ja-JP/content/rest/overview/api-previews.md +++ b/translations/ja-JP/content/rest/overview/api-previews.md @@ -18,13 +18,7 @@ API プレビューを使用すると、正式に GitHub API の一部になる API プレビューにアクセスするには、リクエストの ` Accept` ヘッダー内でカスタムの[メディアタイプ](/rest/overview/media-types)を提供しなければなりません。 各プレビューの機能ドキュメントに、どのカスタムメディアタイプを提供するのかが示されています。 -{% ifversion fpt %} -## 移行 - -GitHub ユーザまたは Organization アカウントからリポジトリをダウンロードして、データの確認、バックアップ、{% data variables.product.prodname_ghe_server %} への[移行](/rest/reference/migrations)ができます。 - -**カスタムメディアタイプ:** `wyandotte-preview` **発表日:** [2018-05-24](https://developer.github.com/changes/2018-05-24-user-migration-api/) -{% endif %} +{% ifversion ghes < 3.3 %} ## 強化されたデプロイメント @@ -32,18 +26,28 @@ GitHub ユーザまたは Organization アカウントからリポジトリを **カスタムメディアタイプ:** `ant-man-preview` **発表日:** [2016-04-06](https://developer.github.com/changes/2016-04-06-deployment-and-deployment-status-enhancements/) +{% endif %} + +{% ifversion ghes < 3.3 %} + ## リアクション コミット、Issue、コメントに対する[リアクション](/rest/reference/reactions)を管理します。 **カスタムメディアタイプ:** `squirrel-girl-preview` **発表日:** [2016-05-12](https://developer.github.com/changes/2016-05-12-reactions-api-preview/) **更新日:** [2016-06-07](https://developer.github.com/changes/2016-06-07-reactions-api-update/) +{% endif %} + +{% ifversion ghes < 3.3 %} + ## タイムライン Issue またはプルリクエストの[イベントのリスト](/rest/reference/issues#timeline)を取得します。 **カスタムメディアタイプ:** `mockingbird-preview` **発表日:** [2016-05-23](https://developer.github.com/changes/2016-05-23-timeline-preview-api/) +{% endif %} + {% ifversion ghes %} ## pre-receive 環境 @@ -52,11 +56,13 @@ pre-receive フックの環境を作成、一覧表示、更新、削除しま **カスタムメディアタイプ:** `eye-scream-preview` **発表日:** [2015-07-29](/rest/reference/enterprise-admin#pre-receive-environments) {% endif %} +{% ifversion ghes < 3.3 %} ## プロジェクト [プロジェクト](/rest/reference/projects)を管理します。 **カスタムメディアタイプ:** `inertia-preview` **発表日:** [2016-09-14](https://developer.github.com/changes/2016-09-14-projects-api/) **更新日:** [2016-10-27](https://developer.github.com/changes/2016-10-27-changes-to-projects-api/) +{% endif %} ## コミット検索 @@ -70,12 +76,16 @@ pre-receive フックの環境を作成、一覧表示、更新、削除しま **カスタムメディアタイプ:** `mercy-preview` **発表日:** [2017-01-31](https://github.com/blog/2309-introducing-topics) +{% ifversion ghes < 3.3 %} + ## 行動規範 すべての[行動規範](/rest/reference/codes-of-conduct)を表示するか、リポジトリに現在ある行動規範を取得します。 **カスタムメディアタイプ:** `scarlet-witch-preview` +{% endif %} + {% ifversion ghae or ghes %} ## グローバル webhook @@ -93,12 +103,16 @@ pre-receive フックの環境を作成、一覧表示、更新、削除しま **カスタムメディアタイプ:** `zzzax-preview` **発表日:** [2018-02-22](https://developer.github.com/changes/2018-02-22-protected-branches-required-signatures) +{% ifversion ghes < 3.3 %} + ## 複数の承認レビューの必須化 API を使用して、プルリクエストに対して[複数の承認レビューを必須にする](/rest/reference/repos#branches)ことができるようになりました。 **カスタムメディアタイプ:** `luke-cage-preview` **発表日:** [2018-03-16](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews) +{% endif %} + {% ifversion ghes < 3.0 %} ## チェック実行とチェックスイート API @@ -135,30 +149,42 @@ GitHub App マニフェストを使用すると、事前設された GitHub App {% endif %} +{% ifversion ghes < 3.3 %} + ## デプロイメントステータス [デプロイメントステータス](/rest/reference/repos#create-a-deployment-status)の`環境`を更新し、`in_progress` および `queued` ステータスを使用できるようになりました。 デプロイメントステータスを作成するときに、`auto_inactive` パラメータを使用して、古い`本番`デプロイメントを `inactive` としてマークできるようになりました。 **カスタムメディアタイプ:** `flash-preview` **発表日:** [2018-10-16](https://developer.github.com/changes/2018-10-16-deployments-environments-states-and-auto-inactive-updates/) +{% endif %} + +{% ifversion ghes < 3.3 %} + ## リポジトリの作成権限 Organization メンバーによるリポジトリの作成可否、および作成可能なリポジトリのタイプを設定できるようになりました。 詳細については、「[Organization を更新する](/rest/reference/orgs#update-an-organization)」を参照してください。 **カスタムメディアタイプ:** `surtur-preview` **発表日:** [2019-12-03](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/) +{% endif %} + ## コンテンツの添付 {% data variables.product.prodname_unfurls %} API を使用して、登録されたドメインにリンクする URL の詳細情報を GitHub で提供できるようになりました。 詳細については、「[添付コンテンツを使用する](/apps/using-content-attachments/)」を参照してください。 **カスタムメディアタイプ:** `corsair-preview` **発表日:** [2018-12-10](https://developer.github.com/changes/2018-12-10-content-attachments-api/) +{% ifversion ghes < 3.3 %} + ## Pages の有効化と無効化 [Pages API](/rest/reference/repos#pages) の新しいエンドポイントを使用して、Pages を有効または無効にできます。 Pages の詳細については、「[GitHub Pages の基本](/categories/github-pages-basics) 」を参照してください。 **カスタムメディアタイプ:** `switcheroo-preview` **発表日:** [2019-03-14](https://developer.github.com/changes/2019-03-14-enabling-disabling-pages/) +{% endif %} + {% ifversion ghes < 3.3 %} ## コミットのブランチまたはプルリクエストの一覧表示 @@ -169,11 +195,7 @@ Organization メンバーによるリポジトリの作成可否、および作 {% endif %} -## リポジトリの脆弱性アラートの有効化または無効化 - -[Repos API](/rest/reference/repos) で 2 つの新しいエンドポイントを使用して、脆弱性アラートを有効化または無効化できます。 - -**カスタムメディアタイプ:** `dorian-preview` **発表日:** [2019-04-24](https://developer.github.com/changes/2019-04-24-vulnerability-alerts/) +{% ifversion ghes < 3.3 %} ## プルリクエストブランチの更新 @@ -181,12 +203,6 @@ Organization メンバーによるリポジトリの作成可否、および作 **カスタムメディアタイプ:** `lydian-preview` **発表日:** [2019-05-29](https://developer.github.com/changes/2019-05-29-update-branch-api/) -{% ifversion fpt %} -## 自動セキュリティ修正の有効化または無効化 - -新しいエンドポイントを使用して、[自動セキュリティ修正を有効化または無効化](/rest/reference/repos#enable-automated-security-fixes)することができます。 - -**カスタムメディアタイプ:** `london-preview` **発表日:** [2019-06-04](https://developer.github.com/changes/2019-06-04-automated-security-fixes/) {% endif %} ## リポジトリテンプレートの作成および使用 @@ -195,7 +211,8 @@ Organization メンバーによるリポジトリの作成可否、および作 **カスタムメディアタイプ:** `baptiste-preview` **発表日:** [2019-07-05](https://developer.github.com/changes/2019-07-16-repository-templates-api/) -{% ifversion fpt or ghes or ghae %} +{% ifversion ghes < 3.3 %} + ## Repositories API の新しい可視性パラメータ [Repositories API](/rest/reference/repos) でリポジトリの可視性を設定および取得できます。 diff --git a/translations/ja-JP/content/rest/overview/troubleshooting.md b/translations/ja-JP/content/rest/overview/troubleshooting.md index 669b18a7f2..62c1802006 100644 --- a/translations/ja-JP/content/rest/overview/troubleshooting.md +++ b/translations/ja-JP/content/rest/overview/troubleshooting.md @@ -62,6 +62,10 @@ curl -u my_username:my_password -X POST "https://api.github.com/authorizations" 次に、[Web アプリケーションフロー](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow)に切り替えて、アクセストークンを生成します。 +## Timeouts + +If {% data variables.product.product_name %} takes more than 10 seconds to process an API request, {% data variables.product.product_name %} will terminate the request and you will receive a timeout response. + {% endif %} [oap-guide]: https://developer.github.com/changes/2015-01-19-an-integrators-guide-to-organization-application-policies/ diff --git a/translations/ja-JP/content/rest/reference/actions.md b/translations/ja-JP/content/rest/reference/actions.md index 2f7759c728..e7ed020ae6 100644 --- a/translations/ja-JP/content/rest/reference/actions.md +++ b/translations/ja-JP/content/rest/reference/actions.md @@ -12,7 +12,6 @@ topics: miniTocMaxHeadingLevel: 3 --- -{% data reusables.actions.ae-beta %} {% data variables.product.prodname_actions %} API では、REST API を使用して {% data variables.product.prodname_actions %} を管理できます。 {% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} require the permissions mentioned in each endpoint. 詳しい情報については、「[{% data variables.product.prodname_actions %} のドキュメント](/actions)」を参照してください。 @@ -22,8 +21,6 @@ miniTocMaxHeadingLevel: 3 ## 成果物 -{% data reusables.actions.ae-beta %} - 成果物 API では、ワークフローの成果物に関する情報をダウンロード、削除、および取得できます。 {% data reusables.actions.about-artifacts %} 詳しい情報については、「[成果物を利用してワークフローのデータを永続化する](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)」を参照してください。 {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %} @@ -35,8 +32,6 @@ miniTocMaxHeadingLevel: 3 {% ifversion fpt or ghes > 2.22 or ghae %} ## 権限 -{% data reusables.actions.ae-beta %} - 権限 API では、どの組織とリポジトリが {% data variables.product.prodname_actions %} を実行できるか、どのアクションを実行できるかについて権限を設定できます。 詳しい情報については、「[使用制限、支払い、および管理](/actions/reference/usage-limits-billing-and-administration#disabling-or-limiting-github-actions-for-your-repository-or-organization)」を参照してください。 Enterprise の権限を設定することもできます。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} Enterprise 管理](/rest/reference/enterprise-admin#github-actions)」REST API を参照してください。 @@ -48,8 +43,6 @@ Enterprise の権限を設定することもできます。 詳しい情報に ## シークレット -{% data reusables.actions.ae-beta %} - シークレット API では、暗号化されたシークレットに関する情報を作成、更新、削除、および取得できます。 {% data reusables.actions.about-secrets %} 詳しい情報については、「[暗号化されたシークレットの作成と利用](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。 {% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `secrets` permission to use this API. 認証されたユーザは、シークレットを作成、更新、または読み取るために、リポジトリへのコラボレータアクセス権を持っている必要があります。 @@ -60,7 +53,6 @@ Enterprise の権限を設定することもできます。 詳しい情報に ## セルフホストランナー -{% data reusables.actions.ae-beta %} {% data reusables.actions.ae-self-hosted-runners-notice %} セルフホストランナー API では、自分のホストランナーの登録、表示、削除ができます。 {% data reusables.actions.about-self-hosted-runners %} 詳しい情報については「[自分のランナーのホスト](/actions/hosting-your-own-runners)」を参照してください。 @@ -75,7 +67,6 @@ Enterprise のセルフホストランナーを管理できます。 詳しい ## セルフホストランナーグループ -{% data reusables.actions.ae-beta %} {% data reusables.actions.ae-self-hosted-runners-notice %} セルフホストランナーグループ API を使用すると、セルフホストランナーのグループを管理できます。 詳しい情報については、「[グループを使用したセルフホストランナーへのアクセスを管理する](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)」を参照してください。 @@ -90,8 +81,6 @@ Enterprise のセルフホストランナーグループを管理できます。 ## ワークフロー -{% data reusables.actions.ae-beta %} - ワークフロー API を使用すると、リポジトリのワークフローを表示できます。 {% data reusables.actions.about-workflows %}詳しい情報については、「[GitHub Actions でワークフローを自動化する](/actions/automating-your-workflow-with-github-actions)」を参照してください。 {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %} @@ -102,8 +91,6 @@ Enterprise のセルフホストランナーグループを管理できます。 ## ワークフロージョブ -{% data reusables.actions.ae-beta %} - ワークフロージョブ API では、ログとワークフロージョブを表示できます。 {% data reusables.actions.about-workflow-jobs %}詳しい情報については、「[GitHub Actions のワークフロー構文](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)」を参照してください。 {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %} @@ -114,8 +101,6 @@ Enterprise のセルフホストランナーグループを管理できます。 ## ワークフロー実行 -{% data reusables.actions.ae-beta %} - ワークフロー実行 API では、ワークフロー実行のログを表示、再実行、キャンセル、表示できます。 {% data reusables.actions.about-workflow-runs %}詳しい情報については、「[ワークフロー実行を管理する](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)」を参照してください。 {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %} diff --git a/translations/ja-JP/content/rest/reference/activity.md b/translations/ja-JP/content/rest/reference/activity.md index 59623b9547..d0d8328bea 100644 --- a/translations/ja-JP/content/rest/reference/activity.md +++ b/translations/ja-JP/content/rest/reference/activity.md @@ -145,6 +145,7 @@ $ -H "If-Modified-Since: Thu, 25 Oct 2012 15:16:27 GMT" | `assign` | Issue に割り当てられた。 | | `作者` | スレッドを作成した。 | | `コメント` | スレッドにコメントした。 | +| `ci_activity` | A {% data variables.product.prodname_actions %} workflow run that you triggered was completed. | | `招待` | リポジトリへのコントリビューションへの招待を承諾した。 | | `manual` | スレッドをサブスクライブした（Issue またはプルリクエストを介して）。 | | `メンション` | コンテンツで具体的に**@メンション**された。 | diff --git a/translations/ja-JP/content/rest/reference/enterprise-admin.md b/translations/ja-JP/content/rest/reference/enterprise-admin.md index 5eb09f8e89..d0d5ac2c55 100644 --- a/translations/ja-JP/content/rest/reference/enterprise-admin.md +++ b/translations/ja-JP/content/rest/reference/enterprise-admin.md @@ -81,7 +81,6 @@ Enterprise の現在のバージョンは、すべての API のレスポンス ## GitHub Actions -{% data reusables.actions.ae-beta %} {% for operation in currentRestOperations %} {% if operation.subcategory == 'actions' %}{% include rest_operation %}{% endif %} diff --git a/translations/ja-JP/content/rest/reference/projects.md b/translations/ja-JP/content/rest/reference/projects.md index d8df40d43f..329b5eec30 100644 --- a/translations/ja-JP/content/rest/reference/projects.md +++ b/translations/ja-JP/content/rest/reference/projects.md @@ -1,6 +1,6 @@ --- title: プロジェクト -intro: Projects APIを使うと、リポジトリ内でプロジェクトの作成、リスト、更新、削除、カスタマイズが行えます。 +intro: 'The Projects API lets you create, list, update, delete and customize projects in a repository.' redirect_from: - /v3/projects versions: diff --git a/translations/ja-JP/content/rest/reference/repos.md b/translations/ja-JP/content/rest/reference/repos.md index e32826e3d1..13a2cb937b 100644 --- a/translations/ja-JP/content/rest/reference/repos.md +++ b/translations/ja-JP/content/rest/reference/repos.md @@ -175,7 +175,7 @@ When you set the state of a deployment to `success`, then all prior non-transien {% ifversion fpt or ghes > 3.1 or ghae-next %} ## 環境 -Environments APIを使うと、環境を作成、設定、削除できます。 環境に関する詳しい情報については「[環境](/actions/reference/environments)」を参照してください。 環境のシークレットの管理については「[シークレット](/rest/reference/actions#secrets)」を参照してください。 +Environments APIを使うと、環境を作成、設定、削除できます。 For more information about environments, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." 環境のシークレットの管理については「[シークレット](/rest/reference/actions#secrets)」を参照してください。 {% for operation in currentRestOperations %} {% if operation.subcategory == 'environments' %}{% include rest_operation %}{% endif %} diff --git a/translations/ja-JP/content/rest/reference/scim.md b/translations/ja-JP/content/rest/reference/scim.md index cfbf72b6f3..ef0512d6a0 100644 --- a/translations/ja-JP/content/rest/reference/scim.md +++ b/translations/ja-JP/content/rest/reference/scim.md @@ -16,7 +16,9 @@ SCIM API は SCIM を有効にしたアイデンティティプロバイダ (IdP {% note %} -**注釈:** SCIM API は、[SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) が有効になっている [{% data variables.product.prodname_ghe_cloud %}](/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts) 上の Organization でのみ使用できます。 {% data reusables.scim.enterprise-account-scim %} SCIMに関する詳しい情報については、「[SCIM について](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim) 」を参照してください。 +**ノート:** + - The SCIM API is available only to organizations on [{% data variables.product.prodname_ghe_cloud %}](/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts) with [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) enabled. {% data reusables.scim.enterprise-account-scim %} SCIMに関する詳しい情報については、「[SCIM について](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim) 」を参照してください。 + - The SCIM API cannot be used with {% data variables.product.prodname_emus %}. {% endnote %} diff --git a/translations/ja-JP/content/rest/reference/search.md b/translations/ja-JP/content/rest/reference/search.md index 789aa2b265..86098f2b94 100644 --- a/translations/ja-JP/content/rest/reference/search.md +++ b/translations/ja-JP/content/rest/reference/search.md @@ -50,7 +50,7 @@ GitHub Octocat in:readme user:defunkt const queryString = 'q=' + encodeURIComponent('GitHub Octocat in:readme user:defunkt'); ``` -使用可能な修飾子の完全な一覧、フォーマット、使用例については、「[GitHub での検索](/articles/searching-on-github/)」を参照してください。 特定の数量、日付に一致させたり、検索結果から除外したりするために演算子を使う方法の詳細については、「[検索構文を理解する](/articles/understanding-the-search-syntax/)」を参照してください。 +使用可能な修飾子の完全な一覧、フォーマット、使用例については、「[GitHub での検索](/articles/searching-on-github/)」を参照してください。 For information about how to use operators to match specific quantities, dates, or to exclude results, see "[Understanding the search syntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax/)." ### クエリの長さの制限 diff --git a/translations/ja-JP/content/rest/reference/teams.md b/translations/ja-JP/content/rest/reference/teams.md index ef27918c3e..61484098c6 100644 --- a/translations/ja-JP/content/rest/reference/teams.md +++ b/translations/ja-JP/content/rest/reference/teams.md @@ -58,6 +58,12 @@ Team Synchronization API では、{% data variables.product.product_name %} Team Team 同期を使用して、IdPを通じて GitHubTeamメンバーを管理できます。 Team Synchronization API を使用するには、チーム同期が有効である必要があります。 詳しい情報については「アイデンティティプロバイダとGitHub間でのTeamの同期」を参照してください。 +{% note %} + +**Note:** The Team Synchronization API cannot be used with {% data variables.product.prodname_emus %}. + +{% endnote %} + {% for operation in currentRestOperations %} {% if operation.subcategory == 'team-sync' %}{% include rest_operation %}{% endif %} {% endfor %} diff --git a/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md b/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md new file mode 100644 index 0000000000..fb7a11d029 --- /dev/null +++ b/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md @@ -0,0 +1,90 @@ +--- +title: GitHub での検索について +intro: 'GitHub の統合検索機能は、{% data variables.product.product_name %}上の多くのリポジトリ、ユーザ、コードの行が対象です。' +redirect_from: + - /articles/using-the-command-bar/ + - /articles/github-search-basics/ + - /articles/search-basics/ + - /articles/searching-github/ + - /articles/advanced-search/ + - /articles/about-searching-on-github + - /github/searching-for-information-on-github/about-searching-on-github + - /github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +{% data reusables.search.you-can-search-globally %} + +- {% data variables.product.product_name %} 全体にわたってグローバルに検索するには、探している内容を任意のページの上部にある検索フィールドに入力し、[All {% data variables.product.prodname_dotcom %}] を検索ドロップダウンメニューで選択します。 +- 特定のリポジトリあるいは Organization 内で検索するには、そのリポジトリあるいは Organization のページにアクセスし、検索する内容をページの上部にある検索フィールドに入力し、**Enter** を押してください。 + +{% note %} + +**ノート:** + +{% ifversion fpt or ghes %} +- {% data reusables.search.required_login %}{% endif %} +- {% data variables.product.prodname_pages %}サイトは、{% data variables.product.product_name %}上では検索できません。 ただし、コンテンツのソースがリポジトリのデフォルトブランチにある場合は、コード検索を使って検索できます。 詳しい情報については[コードの検索](/search-github/searching-on-github/searching-code)を参照してください。 {% data variables.product.prodname_pages %}に関する詳しい情報については、[GitHub Pages とは何ですか？ ](/articles/what-is-github-pages/)を参照してください。 +- 現在、GitHub の検索は完全一致をサポートしていません。 +- コードファイルのどこを検索しても、返されるのは各ファイルで最初の 2 つの結果のみです。 + +{% endnote %} + +{% data variables.product.product_name %}上で検索を行った後、結果をソートしたり、サイドバー内の言語の 1 つをクリックしてさらに絞り込んだりすることができます。 詳しい情報については[検索結果のソート](/search-github/getting-started-with-searching-on-github/sorting-search-results)を参照してください。 + +{% data variables.product.product_name %}の検索は、変更が {% data variables.product.product_name %}にプッシュされるたびにプロジェクトを Elasticsearch クラスタを使ってインデックス付けしています。 Issue やプルリクエストは、作成あるいは変更されると同時にインデックス付けされます。 + +## {% data variables.product.prodname_dotcom %}での検索の種類 + +以下の情報は、{% data variables.product.product_location %} でアクセスできるすべてのリポジトリから検索できます。 + +- [リポジトリ](/search-github/searching-on-github/searching-for-repositories) +- [Topics](/search-github/searching-on-github/searching-topics) +- [Issue およびプルリクエスト](/search-github/searching-on-github/searching-issues-and-pull-requests){% ifversion fpt %} +- [ディスカッション](/search-github/searching-on-github/searching-discussions){% endif %} +- [コード](/search-github/searching-on-github/searching-code) +- [コミット](/search-github/searching-on-github/searching-commits) +- [ユーザ](/search-github/searching-on-github/searching-users) +- [パッケージ](/search-github/searching-on-github/searching-for-packages) +- [Wiki](/search-github/searching-on-github/searching-wikis) + +## ビジュアルインターフェースを使った検索 + +別の方法として、{% data variables.search.search_page_url %}または {% data variables.search.advanced_url %}を使って {% data variables.product.product_name %}を検索できます。 + +{% data variables.search.advanced_url %}は、検索クエリを構築するビジュアルなインターフェースを提供します。 検索は、Star 数やリポジトリの持つフォーク数など、様々な要素でフィルタリングできます。 高度な検索フィールドに記入していくに従って、上部の検索バーでは自動的にクエリが構築されていきます。 + +![高度な検索](/assets/images/help/search/advanced_search_demo.gif) + +{% ifversion fpt or ghes or ghae-next %} + +## Searching repositories on {% data variables.product.prodname_dotcom_the_website %} from your private enterprise environment + +If you use {% ifversion fpt %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae-next %} or {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} and you're a member of a {% data variables.product.prodname_dotcom_the_website %} organization using {% data variables.product.prodname_ghe_cloud %}, an enterprise owner for your {% data variables.product.prodname_enterprise %} environment can enable {% data variables.product.prodname_github_connect %} so that you can search across both environments at the same time{% ifversion ghes or ghae %} from {% data variables.product.product_name %}{% endif %}. For more information, see the following. + +{% ifversion fpt or ghes %} +- "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/{% ifversion ghes %}{{ currentVersion }}{% else %}github-enterprise@latest{% endif %}/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_server %} documentation{% endif %}{% ifversion ghae-next %} +- "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/github-ae@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_managed %} documentation +{% endif %} + +{% ifversion ghes or ghae-next %} + +検索の範囲を環境で狭めるには、{% data variables.search.advanced_url %} 上のフィルタオプションを使うか、検索プレフィックス `environment:` を利用できます。 {% data variables.product.product_name %} 上のコンテンツだけを検索するには、`environment:local` という検索構文を使います。 {% data variables.product.prodname_dotcom_the_website %} 上のコンテンツだけを検索するには`environment:github` を使います。 + +Your enterprise owner on {% data variables.product.product_name %} can enable {% data variables.product.prodname_unified_search %} for all public repositories, all private repositories, or only certain private repositories in the connected {% data variables.product.prodname_ghe_cloud %} organization. + +When you search from {% data variables.product.product_name %}, you can only search in the private repositories that you have access to in the connected {% data variables.product.prodname_dotcom_the_website %} organization. Enterprise owners for {% data variables.product.product_name %} and organization owners on {% data variables.product.prodname_dotcom_the_website %} cannot search private repositories owned by your account on {% data variables.product.prodname_dotcom_the_website %}. To search the applicable private repositories, you must enable private repository search for your personal accounts on {% data variables.product.product_name %}. For more information, see "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment)." + +{% endif %} + +{% endif %} + +## 参考リンク + +- [検索構文を理解する](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax) +- [GitHub での検索](/articles/searching-on-github) diff --git a/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md b/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md new file mode 100644 index 0000000000..e76da94d23 --- /dev/null +++ b/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md @@ -0,0 +1,54 @@ +--- +title: Enabling GitHub.com repository search from your private enterprise environment +shortTitle: Search GitHub.com from enterprise +intro: 'You can connect your personal accounts on {% data variables.product.prodname_dotcom_the_website %} and your private {% data variables.product.prodname_enterprise %} environment to search for content in certain {% data variables.product.prodname_dotcom_the_website %} repositories{% ifversion fpt %} from your private environment{% else %} from {% data variables.product.product_name %}{% endif %}.' +redirect_from: + - /articles/enabling-private-githubcom-repository-search-in-your-github-enterprise-account/ + - /articles/enabling-private-github-com-repository-search-in-your-github-enterprise-server-account/ + - /articles/enabling-private-githubcom-repository-search-in-your-github-enterprise-server-account/ + - /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 +versions: + fpt: '*' + ghes: '*' + ghae: next +topics: + - GitHub search +--- + +## About search for {% data variables.product.prodname_dotcom_the_website %} repositories from {% ifversion fpt %}your private enterprise environment{% else %}{% data variables.product.product_name %}{% endif %} + +You can search for designated private repositories on {% data variables.product.prodname_ghe_cloud %} from {% ifversion fpt %}your private {% data variables.product.prodname_enterprise %} environment{% else %}{% data variables.product.product_location %}{% ifversion ghae %} on {% data variables.product.prodname_ghe_managed %}{% endif %}{% endif %}. {% ifversion fpt %}For example, if you use {% data variables.product.prodname_ghe_server %}, you can search for private repositories from your enterprise from {% data variables.product.prodname_ghe_cloud %} in the web interface for {% data variables.product.prodname_ghe_server %}.{% endif %} + +## 必要な環境 + +- An enterprise owner for {% ifversion fpt %}your private {% data variables.product.prodname_enterprise %} environment{% else %}{% data variables.product.product_name %}{% endif %} must enable {% data variables.product.prodname_github_connect %} and {% data variables.product.prodname_unified_search %} for private repositories. For more information, see the following.{% ifversion fpt or ghes %} + - "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/{% ifversion ghes %}{{ currentVersion }}{% else %}github-enterprise@latest{% endif %}/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_server %} documentation{% endif %}{% ifversion ghae-next %} + - "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/github-ae@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_managed %} documentation +{% endif %} + +- You must already have access to the private repositories and connect your account {% ifversion fpt %}in your private {% data variables.product.prodname_enterprise %} environment{% else %}on {% data variables.product.product_name %}{% endif %} with your account on {% data variables.product.prodname_dotcom_the_website %}. For more information about the repositories you can search, see "[About searching on GitHub](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github#searching-repositories-on-githubcom-from-your-private-enterprise-environment)." + +## Enabling GitHub.com repository search from {% ifversion fpt %}your private {% data variables.product.prodname_enterprise %} environment{% else %}{% data variables.product.product_name %}{% endif %} + +{% ifversion fpt %} + +For more information, see the following. + +| Your enterprise environment | 詳細情報 | +|:--------------------------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| {% data variables.product.prodname_ghe_server %} | "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/enterprise-server@latest/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-enterprise-server)" |{% ifversion ghae-next %} +| +| {% data variables.product.prodname_ghe_managed %} | "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/github-ae@latest//search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-ae)" +{% endif %} + +{% elsif ghes or ghae %} + +1. Sign into {% data variables.product.product_name %} and {% data variables.product.prodname_dotcom_the_website %}. +1. On {% data variables.product.product_name %}, in the upper-right corner of any page, click your profile photo, then click **Settings**. ![ユーザバーの [Settings（設定）] アイコン](/assets/images/help/settings/userbar-account-settings.png) +{% data reusables.github-connect.github-connect-tab-user-settings %} +{% data reusables.github-connect.connect-dotcom-and-enterprise %} +{% data reusables.github-connect.connect-dotcom-and-enterprise %} + +{% endif %} diff --git a/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/index.md b/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/index.md new file mode 100644 index 0000000000..e61cd0ff2b --- /dev/null +++ b/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/index.md @@ -0,0 +1,21 @@ +--- +title: GitHub の検索を使ってみる +intro: 'You can use a wide range of syntax to search {% data variables.product.product_name %}. You can adjust the scope of your search, build and troubleshoot queries, and sort search results with qualifiers.' +redirect_from: + - /articles/getting-started-with-searching-on-github + - /github/searching-for-information-on-github/getting-started-with-searching-on-github +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +children: + - /about-searching-on-github + - /understanding-the-search-syntax + - /troubleshooting-search-queries + - /sorting-search-results + - /enabling-githubcom-repository-search-from-your-private-enterprise-environment +shortTitle: Start with search on GitHub +--- + diff --git a/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md b/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md new file mode 100644 index 0000000000..80e33fef47 --- /dev/null +++ b/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md @@ -0,0 +1,75 @@ +--- +title: 検索結果をソートする +intro: '[Sort] メニューを使って、またはクエリに sort 修飾子を加えることで、[{% data variables.product.product_name %} 検索](/articles/searching-on-github)結果をソートできます。' +redirect_from: + - /articles/sorting-search-results + - /github/searching-for-information-on-github/sorting-search-results + - /github/searching-for-information-on-github/getting-started-with-searching-on-github/sorting-search-results +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +[Sort] メニューを使用して、関連性、Star の数、フォークの数、およびアイテムの更新の頻度で検索結果をソートできます。 + + ![検索結果ソートのオプション付きメニュー](/assets/images/help/search/repo-search-sort.png) + +インタラクション、リアクション、作者日付、コミッター日付、またはアイテム更新頻度でソートするには、検索クエリに `sort` 修飾子を追加します。 + +## インタラクションでソート + +`sort:interactions` 修飾子は、インタラクションおよびコメントの合計数の多い順にソートします。 + +| 修飾子 | サンプル | +| ------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sort:interactions` または `sort:interactions-desc` | [**org:github sort:interactions**](https://github.com/search?q=org%3Agithub+sort%3Ainteractions&type=Issues) は、{% data variables.product.product_name %} が所有するリポジトリの Issue にマッチし、インタラクションおよびコメントの合計数の多い順にソートされます。 | +| `sort:interactions-asc` | [**org:github sort:interactions-asc**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Ainteractions-asc&type=Issues) は、{% data variables.product.product_name %} が所有するリポジトリの Issue にマッチし、インタラクションおよびコメントの合計数の少ない順にソートされます。 | + +## リアクションでソート + +`sort:reactions` 修飾子は、リアクションおよびコメントの合計数の多い順にソートします。 + +| 修飾子 | サンプル | +| ------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sort:reactions` または `sort:reactions-desc` | [**org:github sort:reactions**](https://github.com/search?q=org%3Agithub+sort%3Areactions&type=Issues) は、{% data variables.product.product_name %} が所有するリポジトリの Issue にマッチし、リアクションの数の多い順にソートされます。 | +| `sort:reactions-asc` | [**org:github sort:reactions-asc**](https://github.com/search?q=org%3Agithub+sort%3Areactions-asc&type=Issues) は、{% data variables.product.product_name %} が所有するリポジトリの Issue にマッチし、リアクションの数の少ない順にソートされます。 | +| sort:reactions-reaction | [**org:github sort:reactions-+1**](https://github.com/search?q=org%3Agithub+sort%3Areactions-%2B1&type=Issues) は、{% data variables.product.product_name %} が所有するリポジトリの Issue にマッチし、サムズアップ (:+1:) のリアクションが多い順にソートされます。 | +| | [**org:github sort:reactions--1**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Areactions--1&type=Issues)は、{% data variables.product.product_name %} が所有するリポジトリの Issue にマッチし、サムズダウン (:-1:) のリアクションが多い順にソートされます。 | +| | [**org:github sort:reactions-smile**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Areactions-smile&type=Issues) は、{% data variables.product.product_name %} が所有するリポジトリの Issue にマッチし、スマイル (:smile:) のリアクションが多い順にソートされます。 | +| | [**org:github sort:reactions-tada**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Areactions-tada&type=Issues) は、{% data variables.product.product_name %} が所有するリポジトリの Issue にマッチし、「やったー！」(:tada:) の多い順にソートされます。 | +| | [**org:github sort:reactions-heart**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Areactions-heart&type=Issues) は、{% data variables.product.product_name %} が所有するリポジトリの Issue にマッチし、ハート (:heart:) が多い順にソートされます。 | + +## オーサー日付でソート + +`sort:author-date` 修飾子は、オーサー日付を降順または昇順でソートします。 + +| 修飾子 | サンプル | +| ---------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sort:author-date` または `sort:author-date-desc` | [**feature org:github sort:author-date**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Aauthor-date&type=Commits) は、オーサー日付で降順にソートされた、{% data variables.product.product_name %} が所有するリポジトリの「feature」という単語を含むコミットにマッチします。 | +| `sort:author-date-asc` | [**feature org:github sort:author-date-asc**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Aauthor-date-asc&type=Commits) は、{% data variables.product.product_name %} が所有するリポジトリの「feature」という単語を含むコミットにマッチし、作者日付の昇順でソートされます。 | + +## コミッター日付でソート + +`sort:committer-date` 修飾子は、コミッター日付を降順または昇順でソートします。 + +| 修飾子 | サンプル | +| ---------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sort:committer-date` または `sort:committer-date-desc` | [**feature org:github sort:committer-date**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Acommitter-date&type=Commits) は、{% data variables.product.product_name %} が所有するリポジトリの「feature」という単語を含むコミットにマッチし、コミッター日付の降順にソートされます。 | +| `sort:committer-date-asc` | [**feature org:github sort:committer-date-asc**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Acommitter-date-asc&type=Commits) は、{% data variables.product.product_name %} が所有するリポジトリの「feature」という単語を含むコミットにマッチし、コミッター日付の昇順でソートされます。 | + +## 更新日付でソート + +`sort:updated` 修飾子は、アイテムがどれだけ最近に更新されたかでソートします。 + +| 修飾子 | サンプル | +| -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `sort:updated` または `sort:updated-desc` | [**feature sort:updated**](https://github.com/search?utf8=%E2%9C%93&q=feature+sort%3Aupdated&type=Repositories) は、「feature」という単語を含むリポジトリにマッチし、更新日付の新しい順でソートされます。 | +| `sort:updated-asc` | [**feature sort:updated-asc**](https://github.com/search?utf8=%E2%9C%93&q=feature+sort%3Aupdated-asc&type=Repositories) は、更新日付の古い順でソートされた、「feature」という単語を含むリポジトリにマッチします。 | + +## 参考リンク + +- "[About searching on {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)" +- "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)" diff --git a/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/troubleshooting-search-queries.md b/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/troubleshooting-search-queries.md new file mode 100644 index 0000000000..3a54a8a427 --- /dev/null +++ b/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/troubleshooting-search-queries.md @@ -0,0 +1,34 @@ +--- +title: クエリ検索のトラブルシューティング +intro: '{% data variables.product.product_name %} での検索中に予期しない結果が起きた場合、よくある問題および制限を確認することでトラブルシューティングできます。' +redirect_from: + - /articles/troubleshooting-search-queries + - /github/searching-for-information-on-github/troubleshooting-search-queries + - /github/searching-for-information-on-github/getting-started-with-searching-on-github/troubleshooting-search-queries +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +shortTitle: Troubleshoot search queries +--- + +## タイムアウトの可能性 + +いくつかのクエリは、弊社の検索インフラで実行するには計算するうえでコストが高くなります。 皆さんが検索を迅速に行えるように、個別のクエリを実行する時間について制限を設けています。 まれなことですがクエリが制限時間を超えた場合、検索結果はタイムアウトになる前に見つかった全てのマッチを表示し、タイムアウトが起きたことを知らせます。 + +タイムアウトになったことは、必ずしも検索結果が未完了であるということではありません。 ただ、すべての検索可能なデータを検索する前にクエリが中断したことを意味しています。 + +## クエリの長さの制限 + +{% data variables.product.product_name %} での検索では、クエリの長さに一定の制限があります。 + +* 256 文字を超えるクエリはサポートされません。 +* 6 つ以上の `AND`、`OR` や `NOT` 演算子を使ったクエリを作成することはできません。 + +コードの検索など特定の検索形式は、さらなる制限がある可能性があります。 詳しい情報については、これらの検索形式のドキュメントを確認してください。 + +## 参考リンク + +- "[GitHub での検索について](/search-github/getting-started-with-searching-on-github/about-searching-on-github)" 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 new file mode 100644 index 0000000000..5f5e855eea --- /dev/null +++ b/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md @@ -0,0 +1,100 @@ +--- +title: 検索構文を理解する +intro: '{% data variables.product.product_name %} の検索では、特定の数字や単語にマッチするクエリを作成できます。' +redirect_from: + - /articles/search-syntax/ + - /articles/understanding-the-search-syntax + - /github/searching-for-information-on-github/understanding-the-search-syntax + - /github/searching-for-information-on-github/getting-started-with-searching-on-github/understanding-the-search-syntax +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +shortTitle: Understand search syntax +--- + +## ある値より大きいまたは小さい値のクエリ + +`>`、`>=`、`<`、`<=` などを使って、他の値に対する値の大なり、大なりイコール、小なり、または、小なりイコールでの検索を行えます。 + +| クエリ | サンプル | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | +| >n | **[cats stars:>1000](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%3E1000&type=Repositories)** は、1000 を超える Star のある、「cats」という単語があるリポジトリにマッチします。 | +| >=n | **[cats topics:>=5](https://github.com/search?utf8=%E2%9C%93&q=cats+topics%3A%3E%3D5&type=Repositories)** は、トピックが 5 つ以上ある、「cats」という単語のあるリポジトリにマッチします。 | +| <n | **[cats size:<10000](https://github.com/search?utf8=%E2%9C%93&q=cats+size%3A%3C10000&type=Code)** は、10 KB より小さいファイルで、「cats」という単語があるコードにマッチします。 | +| <=n | **[cats stars:<=50](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%3C%3D50&type=Repositories)** は、50 以下の Star があり、「cats」という単語のあるリポジトリにマッチします。 | + +他の値に対する値の大なり、大なりイコール、小なり、または、小なりイコールでの検索は、[range queries](#query-for-values-between-a-range) を使って実行することもできます。 + +| クエリ | サンプル | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| n..* | **[cats stars:10..*](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A10..*&type=Repositories)** は、`stars:>=10` と同様に、10 以上の Star のある、「cats」という単語のあるリポジトリにマッチします。 | +| *..n | **[cats stars:*..10](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%22*..10%22&type=Repositories) は、**`stars:<=10` と同様に、Star が 10 以下で、「cats」という単語のあるリポジトリにマッチします。 | + +## 一定範囲にある値のクエリ + +n..n という範囲構文を使って、範囲内の値を検索できます。最初の番号 _n_ が最小値で、二番目が最大値です。 + +| クエリ | サンプル | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| n..n | **[cats stars:10..50](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A10..50&type=Repositories)** は、Star が 10 から 50 までの間の数の、「cats」という単語のあるリポジトリにマッチします。 | + +## 日付のクエリ + +`>` 、`>=` 、`<` 、`<=` や [range queries](#query-for-values-between-a-range) を使って、他の日より前または後の日付や、一定の範囲内の日付を検索できます。 {% data reusables.time_date.date_format %} + +| クエリ | サンプル | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| >YYYY-MM-DD | **[cats created:>2016-04-29](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3E2016-04-29&type=Issues)** は、2016 年 4 月 29 日より後に作成された、「cats」という単語のある Issue にマッチします。 | +| >=YYYY-MM-DD | **[cats created:>=2017-04-01](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3E%3D2017-04-01&type=Issues)** は、2017 年 4 月 1 日以降に作成された、「cats」という単語を含む Issue にマッチします。 | +| <YYYY-MM-DD | **[cats pushed:<2012-07-05](https://github.com/search?q=cats+pushed%3A%3C2012-07-05&type=Code&utf8=%E2%9C%93)** は、2012 年 7 月 5 日より前にプッシュされた、リポジトリに「cats」という単語のあるコードにマッチします。 | +| <=YYYY-MM-DD | **[cats created:<=2012-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3C%3D2012-07-04&type=Issues)** は、2012 年 7 月 4 日以前に作成された、「cats」という単語のある Issue にマッチします。 | +| YYYY-MM-DD..YYYY-MM-DD | **[cats pushed:2016-04-30..2016-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+pushed%3A2016-04-30..2016-07-04&type=Repositories)** は、2016 年 4 月末から 2017 年 7 月 4 日の間にプッシュされた、「cats」という単語のあるリポジトリにマッチします。 | +| YYYY-MM-DD..* | **[cats created:2012-04-30..*](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2012-04-30..*&type=Issues)** は、「cats」という単語を含む、2012 年 4 月 30 日より後に作成された Issue にマッチします。 | +| *..YYYY-MM-DD | **[cats created:*..2012-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A*..2012-07-04&type=Issues)** は、「cats」という単語のある、2012 年 7 月 4 日より前に作成された Issue にマッチします。 | + +{% data reusables.time_date.time_format %} + +| クエリ | サンプル | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| YYYY-MM-DDTHH:MM:SS+00:00 | **[cats created:2017-01-01T01:00:00+07:00..2017-03-01T15:30:15+07:00](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2017-01-01T01%3A00%3A00%2B07%3A00..2017-03-01T15%3A30%3A15%2B07%3A00&type=Issues)** 2017 年 1 月 1 日午前 1 時（世界協定時`+7時間`）と 2017 年 3 月 1 日午後 3 時（世界協定時 `+7時間`）の間に作成された Issue にマッチします。 （世界協定時`+7時間`）と 2017 年 3 月 1 日午後 3 時 （世界協定時 `+7時間`）の間に作成された Issue にマッチします。 | +| YYYY-MM-DDTHH:MM:SSZ | **[cats created:2016-03-21T14:11:00Z..2016-04-07T20:45:00Z](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2016-03-21T14%3A11%3A00Z..2016-04-07T20%3A45%3A00Z&type=Issues)** は、2016 年 3 月 21 日午後 2 時 11 分と 2016 年 4 月 7 日 8 時 45 分の間に作成された Issue にマッチします。 | + +## 一定の検索結果の除外 + +`NOT` 構文を使うことで、一定の単語を含む検索結果を除外できます。 `NOT` 演算子は、文字列型キーワードに限って使うことができます。 数や日付では機能しません。 + +| クエリ | サンプル | +| ----- | ----------------------------------------------------------------------------------------------------------------------------------- | +| `NOT` | **[hello NOT world](https://github.com/search?q=hello+NOT+world&type=Repositories)** は、「world」という単語がなく、「hello」という単語のあるリポジトリにマッチします。 | + +検索結果を絞り込む他の方法としては、一定のサブセットを除外することです。 `-` のプリフィックスを修飾子に付けることで、その修飾子にマッチする全ての結果を除外できます。 + +| クエリ | サンプル | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| -QUALIFIER | **[cats stars:>10 -language:javascript](https://github.com/search?q=cats+stars%3A>10+-language%3Ajavascript&type=Repositories)** は、JavaScriptで書かれていない、Star が 10 を上回る、「cats」という単語のあるリポジトリにマッチします。 | +| | **[mentions:defunkt -org:github](https://github.com/search?utf8=%E2%9C%93&q=mentions%3Adefunkt+-org%3Agithub&type=Issues)** は、GitHub の Organization のリポジトリにはない、@defunkt をメンションする Issue にマッチします。 | + +## 空白のあるクエリに引用符を使う + +検索クエリに空白がある場合は引用府で囲む必要があります。 例: + +* [cats NOT "hello world"](https://github.com/search?utf8=✓&q=cats+NOT+"hello+world"&type=Repositories) は、「hello world」という単語がなく、「cats」という単語のあるリポジトリにマッチします。 +* [build label:"bug fix"](https://github.com/search?utf8=%E2%9C%93&q=build+label%3A%22bug+fix%22&type=Issues) は、「bug fix」というラベルがある、「build」という単語のある Issue にマッチします。 + +スペースなど、いくつかの英数字以外の記号は、引用符で囲ったコード検索クエリから省かれるので、結果が予想外のものになる場合があります。 + +{% ifversion fpt or ghes or ghae %} +## ユーザ名によるクエリ + +検索クエリに、`user`、`actor`、`assignee`などユーザ名を必要とする修飾子が含まれる場合は、任意の {% data variables.product.product_name %} ユーザ名を使用して特定の個人を指定するか、`@me`を使用して現在のユーザを指定することができます。 + +| クエリ | サンプル | +| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | +| `QUALIFIER:USERNAME` | [`author:nat`](https://github.com/search?q=author%3Anat&type=Commits) は、@nat が書いたコミットにマッチします。 | +| `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/index.md b/translations/ja-JP/content/search-github/index.md new file mode 100644 index 0000000000..57554b36f5 --- /dev/null +++ b/translations/ja-JP/content/search-github/index.md @@ -0,0 +1,20 @@ +--- +title: GitHub で情報を検索する +intro: Use different types of searches to find the information you want. +redirect_from: + - /categories/78/articles/ + - /categories/search/ + - /categories/searching-for-information-on-github + - /github/searching-for-information-on-github +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +children: + - /getting-started-with-searching-on-github + - /searching-on-github +shortTitle: Search on GitHub +--- + diff --git a/translations/ja-JP/content/search-github/searching-on-github/finding-files-on-github.md b/translations/ja-JP/content/search-github/searching-on-github/finding-files-on-github.md new file mode 100644 index 0000000000..b36d7093e0 --- /dev/null +++ b/translations/ja-JP/content/search-github/searching-on-github/finding-files-on-github.md @@ -0,0 +1,32 @@ +--- +title: GitHub でファイルを検索する +intro: 'ファイルファインダーを使ってリポジトリにあるファイルを検索できます。 To search for a file in multiple repositories on {% data variables.product.product_name %}, use the [`filename` code search qualifier](/search-github/searching-on-github/searching-code#search-by-filename).' +redirect_from: + - /articles/finding-files-on-github + - /github/searching-for-information-on-github/finding-files-on-github + - /github/searching-for-information-on-github/searching-on-github/finding-files-on-github +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +{% tip %} + +**参考:** + +- ファイルファインダーの結果では、`build`、`log`、`tmp`、および `vendor` のような一部のディレクトリは除外されます。 これらのディレクトリ内のファイルを検索するには、[`filename` コード検索修飾子](/search-github/searching-on-github/searching-code#search-by-filename)を使用します。 +- キーボードの `t` キーを押してファイルファインダーを開くこともできます。 詳細は「[キーボードのショートカット](/articles/keyboard-shortcuts)」を参照してください。 + +{% endtip %} + +{% data reusables.repositories.navigate-to-repo %} +2. ファイルの一覧の上にある [**Go to file**] をクリックします。 ![[Find file] ボタン](/assets/images/help/search/find-file-button.png) +3. 検索フィールドで、検索したいファイル名を入力します。 ![ファイル検索の検索フィールド](/assets/images/help/search/find-file-search-field.png) +4. 結果のリストで、目的のファイルをクリックします。 + +## 参考リンク + +- "[GitHub での検索について](/search-github/getting-started-with-searching-on-github/about-searching-on-github)" diff --git a/translations/ja-JP/content/search-github/searching-on-github/index.md b/translations/ja-JP/content/search-github/searching-on-github/index.md new file mode 100644 index 0000000000..f31dae28aa --- /dev/null +++ b/translations/ja-JP/content/search-github/searching-on-github/index.md @@ -0,0 +1,27 @@ +--- +title: GitHub 上で検索する +intro: You can use qualifiers to narrow your search and focus on specific categories of information. +redirect_from: + - /articles/searching-on-github + - /github/searching-for-information-on-github/searching-on-github +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +children: + - /finding-files-on-github + - /searching-for-repositories + - /searching-topics + - /searching-code + - /searching-commits + - /searching-issues-and-pull-requests + - /searching-discussions + - /searching-github-marketplace + - /searching-users + - /searching-for-packages + - /searching-wikis + - /searching-in-forks +--- + diff --git a/translations/ja-JP/content/search-github/searching-on-github/searching-code.md b/translations/ja-JP/content/search-github/searching-on-github/searching-code.md new file mode 100644 index 0000000000..db0ef9d4f7 --- /dev/null +++ b/translations/ja-JP/content/search-github/searching-on-github/searching-code.md @@ -0,0 +1,112 @@ +--- +title: コードの検索 +intro: '{% data variables.product.product_name %} 上のコードを検索することができます。そして、これらのコードを検索する修飾子を組み合わせることで、検索結果を絞ることができます。' +redirect_from: + - /articles/searching-code + - /github/searching-for-information-on-github/searching-files-in-a-repository-for-exact-matches + - /github/searching-for-information-on-github/searching-code-for-exact-matches + - /github/searching-for-information-on-github/searching-code + - /github/searching-for-information-on-github/searching-on-github/searching-code +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +{% data reusables.search.you-can-search-globally %} 詳細については、「[GitHub での検索](/search-github/getting-started-with-searching-on-github/about-searching-on-github)」を参照してください。 + +これらのコード検索の修飾子を使わなければ、コードを検索できません。 リポジトリ、ユーザまたはコミットの特定の修飾子での検索は、コードを検索する場合、うまくいきません。 + +{% data reusables.search.syntax_tips %} + +## コード検索での留意点 + +コードの検索は複雑なため、検索の実行には一定の制限があります。 + +{% ifversion fpt or ghes %} +- {% data reusables.search.required_login %}{% endif %} +- [フォーク](/articles/about-forks)のコードは、親リポジトリより Star が多い場合に限って検索可能です。 親リポジトリより Star が少ないフォークは、コード検索ではインデックス**されません。** 親リポジトリより Star が多いフォークを検索結果に含めるためには、クエリに `fork:true` または `fork:only` を追加する必要があります。 詳細は「[フォーク内で検索する](/search-github/searching-on-github/searching-in-forks)」を参照してください。 +- コード検索では、_デフォルトブランチ_のみインデックスされます。{% ifversion fpt %} +- 384 KB より小さいファイルのみ検索可能です。{% else %}* 5 MB より小さいファイルのみ検索可能です。 +- 各ファイルの最初の 500 KB のみ検索可能です。{% endif %} +- 500,000 ファイル未満のリポジトリのみが検索可能です。{% ifversion fpt %} +- 昨年アクティビティがあった、または検索結果に返されたリポジトリのみが検索可能です。{% endif %} +- [`filename`](#search-by-filename) の検索を除き、ソースコードを検索する場合、常に少なくとも検索単語を 1 つ含める必要があります。 たとえば[`language:javascript`](https://github.com/search?utf8=%E2%9C%93&q=language%3Ajavascript&type=Code&ref=searchresults) は有効な検索ではありませんが、[`amazing language:javascript`](https://github.com/search?utf8=%E2%9C%93&q=amazing+language%3Ajavascript&type=Code&ref=searchresults) は有効な検索です。 +- 検索結果では、同一ファイルから取り出される部分は 2 つまでです。そのファイルはさらに多くの部分でヒットしている可能性があります。 +- クエリの一部として次のワイルドカード文字を用いることはできません: . , : ; / \ ` ' " = * ! ? # $ & + ^ | ~ < > ( ) { } [ ] @. 検索では、これらのシンボルは単に無視されます。 + +## ファイルの内容またはファイルパスで検索 + +`in` 修飾子によって、ソースコードファイル、ファイルパスまたはその両方の内容に検索を限定することができます。 この修飾子を省略した場合、ファイルの内容だけが検索されます。 + +| 修飾子 | サンプル | +| --------- | ----------------------------------------------------------------------------------------------------------------------------------------- | +| `in:file` | [**octocat in:file**](https://github.com/search?q=octocat+in%3Afile&type=Code) は、ファイルの内容に「octocat」が出現するコードにマッチします。 | +| `in:path` | [**octocat in:path**](https://github.com/search?q=octocat+in%3Apath&type=Code) は、ファイルパスに「octocat」が含まれているコードにマッチします。 | +| | [**octocat in:file,path**](https://github.com/search?q=octocat+in%3Afile%2Cpath&type=Code) は、ファイルの内容またはファイルパスに「octocat」が含まれているコードにマッチします。 | + +## ユーザまたは Organization のリポジトリ内の検索 + +特定のユーザまたは Organization のすべてのリポジトリのコードを検索するには、`user` 修飾子または `org` 修飾子を使います。 特定のリポジトリのコードを検索するには、`repo` 修飾子を使います。 + +| 修飾子 | サンプル | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| user:USERNAME | [**user:defunkt extension:rb**](https://github.com/search?q=user%3Agithub+extension%3Arb&type=Code) は、末尾が .rb の @defunkt からのコードにマッチします。 | +| org:ORGNAME | [**org:github extension:js**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+extension%3Ajs&type=Code) は、末尾が .js の GitHub からのコードにマッチします。 | +| repo:USERNAME/REPOSITORY | [**repo:mozilla/shumway extension:as**](https://github.com/search?q=repo%3Amozilla%2Fshumway+extension%3Aas&type=Code) は、末尾が .as の @mozilla の shumway project からのコードにマッチします。 | + +## ファイルの場所での検索 + +リポジトリの特定の場所に表示されているソースコードを探すには、`path` 修飾子を使います。 リポジトリの root レベルにあるファイルを検索するには、`path:/` を使います。 または、ディレクトリやそのサブディレクトリ内に存在しているファイルを検索するには、ディレクトリ名もしくはディレクトリへのパスを明示してください。 + +| 修飾子 | サンプル | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| path:/ | [**octocat filename:readme path:/**](https://github.com/search?utf8=%E2%9C%93&q=octocat+filename%3Areadme+path%3A%2F&type=Code) は、リポジトリの root レベルに存在する 「octocat」という単語がある _readme_ ファイルにマッチします。 | +| path:DIRECTORY | [**form path:cgi-bin language:perl**](https://github.com/search?q=form+path%3Acgi-bin+language%3Aperl&type=Code) matches Perl files with the word "form" in the cgi-bin directory, or in any of its subdirectories. | +| path:PATH/TO/DIRECTORY | [**console path:app/public language:javascript**](https://github.com/search?q=console+path%3A%22app%2Fpublic%22+language%3Ajavascript&type=Code) matches JavaScript files with the word "console" in the app/public directory, or in any of its subdirectories (even if they reside in app/public/js/form-validators). | + +## 言語で検索 + + +コードが書かれた言語で検索することができます。 The `language` qualifier can be the language name or alias. For a full list of supported languages with their names and aliases, see the [github/linguist repository](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml). + +| 修飾子 | サンプル | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| language:LANGUAGE | [**element language:xml size:100**](https://github.com/search?q=element+language%3Axml+size%3A100&type=Code) は、XML 形式でちょうど 100 バイトであり「element」という単語があるコードにマッチします。 | +| | [**display language:scss**](https://github.com/search?q=display+language%3Ascss&type=Code) は、SCSS 形式の「display」という単語があるコードにマッチします。 | +| | [**org:mozilla language:markdown**](https://github.com/search?utf8=%E2%9C%93&q=org%3Amozilla+language%3Amarkdown&type=Code) は、Markdown 形式の @mozilla のすべてのリポジトリからのコードにマッチします。 | + +## ファイルサイズで検索 + +コードが存在するファイルのサイズによってソースコードを検索するには、`size` 修飾子を使います。 `size` 修飾子は、ファイルのバイトサイズによって検索結果を仕分けするために、[不等号や範囲の修飾子](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)を使います。 + +| 修飾子 | サンプル | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| size:n | [**function size:>10000 language:python**](https://github.com/search?q=function+size%3A%3E10000+language%3Apython&type=Code) は、10 KB より大きいファイルにある Python で記述された「function」という単語があるコードにマッチします。 | + +## ファイル名で検索 + +`filename` 修飾子は、特定のファイル名を持つコードファイルにマッチします。 ファイルファインダーを使ってリポジトリにあるファイルを表示できます。 詳細は「[GitHub でファイルを検索する](/search-github/searching-on-github/finding-files-on-github)」を参照してください。 + +| 修飾子 | サンプル | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| filename:FILENAME | [**filename:linguist**](https://github.com/search?utf8=%E2%9C%93&q=filename%3Alinguist&type=Code) は、「linguist」と名付けられたファイルにマッチします。 | +| | [**filename:.vimrc commands**](https://github.com/search?q=filename%3A.vimrc+commands&type=Code) は、「commands」という単語がある *.vimrc* ファイルにマッチします。 | +| | [**filename:test_helper path:test language:ruby**](https://github.com/search?q=minitest+filename%3Atest_helper+path%3Atest+language%3Aruby&type=Code) は、*test* ディレクトリ内の *test_helper* と名付けられた Ruby のファイルにマッチします。 | + +## ファイルの拡張子で検索 + +`extension` 修飾子は、特定のファイル拡張子のあるファイルにマッチします。 + +| 修飾子 | サンプル | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| extension:EXTENSION | [**form path:cgi-bin extension:pm**](https://github.com/search?q=form+path%3Acgi-bin+extension%3Apm&type=Code) は、cgi-bin にあって .pm というファイル拡張子を持ち 「form」という単語があるコードにマッチします。 | +| | [**icon size:>200000 extension:css**](https://github.com/search?utf8=%E2%9C%93&q=icon+size%3A%3E200000+extension%3Acss&type=Code) は、200 KB より大きく「icon」という単語を含み、末尾が .css のファイルにマッチします。 | + +## 参考リンク + +- 「[検索結果をソートする](/search-github/getting-started-with-searching-on-github/sorting-search-results/)」 +- "[フォーク内を検索する](/search-github/searching-on-github/searching-in-forks)"{% ifversion fpt %} +- "[ {% data variables.product.prodname_dotcom %} 上のコード間を移動する](/github/managing-files-in-a-repository/navigating-code-on-github)"{% endif %} diff --git a/translations/ja-JP/content/search-github/searching-on-github/searching-commits.md b/translations/ja-JP/content/search-github/searching-on-github/searching-commits.md new file mode 100644 index 0000000000..57dc058b96 --- /dev/null +++ b/translations/ja-JP/content/search-github/searching-on-github/searching-commits.md @@ -0,0 +1,111 @@ +--- +title: コミットを検索する +intro: '{% data variables.product.product_name %} 上のコミットを検索することができます。そして、これらのコミットを検索する修飾子を組み合わせることで、検索結果を絞ることができます。' +redirect_from: + - /articles/searching-commits + - /github/searching-for-information-on-github/searching-commits + - /github/searching-for-information-on-github/searching-on-github/searching-commits +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +{% data variables.product.product_name %} 全体にわたってグローバルにコミットを検索できます。あるいは、特定のリポジトリや Organization のコミットに限った検索もできます。 詳細は「[{% data variables.product.company_short %} での検索について](/search-github/getting-started-with-searching-on-github/about-searching-on-github)」を参照してください。 + +コミットを検索する場合、リポジトリの[デフォルトブランチ](/articles/about-branches)だけが検索されます。 + +{% data reusables.search.syntax_tips %} + +## コミットメッセージ内を検索 + +メッセージに特定の単語を含むコミットを検索できます。 たとえば、[**fix typo**](https://github.com/search?q=fix+typo&type=Commits) は、「fix」および「typo」という単語を含むコミットにマッチします。 + +## オーサーやコミッターで検索 + +特定のユーザによるコミットを、`author` 修飾子や `committer` 修飾子を使って検索できます。 + +| 修飾子 | サンプル | +| ------------------------- | -------------------------------------------------------------------------------------------------------------------- | +| author:USERNAME | [**author:defunkt**](https://github.com/search?q=author%3Adefunkt&type=Commits) は、@defunkt が書いたコミットにマッチします。 | +| committer:USERNAME | [**committer:defunkt**](https://github.com/search?q=committer%3Adefunkt&type=Commits) は、@defunkt がコミットしたコミットにマッチします。 | + +`author-name` 修飾子や `committer-name` 修飾子は、オーサー名やコミッター名のコミットにマッチします。 + +| 修飾子 | サンプル | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | +| author-name:NAME | [**author-name:wanstrath**](https://github.com/search?q=author-name%3Awanstrath&type=Commits) は、作者名が「wanstrath」であるコミットにマッチします。 | +| committer-name:NAME | [**committer-name:wanstrath**](https://github.com/search?q=committer-name%3Awanstrath&type=Commits) は、コミッター名が「wanstrath」であるコミットにマッチします。 | + +`author-email` 修飾子や `committer-email` 修飾子は、作者やコミッターのフルメールアドレスで、コミットにマッチします。 + +| 修飾子 | サンプル | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| author-email:EMAIL | [**author-email:chris@github.com**](https://github.com/search?q=author-email%3Achris%40github.com&type=Commits) は、chris@github.com が作者であるコミットにマッチします。 | +| committer-email:EMAIL | [**committer-email:chris@github.com**](https://github.com/search?q=committer-email%3Achris%40github.com&type=Commits) は、chris@github.com がコミットしたコミットにマッチします。 | + +## オーサー日付やコミット日付で検索 + +`author-date` 修飾子や `committer-date` 修飾子を使うと、特定の期間内に書かれたまたはコミットされたコミットにマッチします。 + +{% data reusables.search.date_gt_lt %} + +| 修飾子 | サンプル | +| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | +| author-date:YYYY-MM-DD | [**author-date:<2016-01-01**](https://github.com/search?q=author-date%3A<2016-01-01&type=Commits) は、2016 年 1 月 1 日より前に作成されたコミットにマッチします。 | +| committer-date:YYYY-MM-DD | [**committer-date:>2016-01-01**](https://github.com/search?q=committer-date%3A>2016-01-01&type=Commits) は、2016 年 1 月 1 日以降に作成されたコミットにマッチします。 | + +## マージコミットのフィルタリング + +`merge` 修飾子はマージコミットをフィルタリングします。 + +| 修飾子 | サンプル | +| ------------- | -------------------------------------------------------------------------------------------- | +| `merge:true` | [**merge:true**](https://github.com/search?q=merge%3Atrue&type=Commits) は、マージコミットにマッチします。 | +| `merge:false` | [**merge:false**](https://github.com/search?q=merge%3Afalse&type=Commits) は、非マージコミットにマッチします。 | + +## ハッシュで検索 + +`hash` 修飾子は、特定の SHA-1 ハッシュのコミットにマッチします。 + +| 修飾子 | サンプル | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| hash:HASH | [**hash:124a9a0ee1d8f1e15e833aff432fbb3b02632105**](https://github.com/github/gitignore/search?q=hash%3A124a9a0ee1d8f1e15e833aff432fbb3b02632105&type=Commits) は、ハッシュ `124a9a0ee1d8f1e15e833aff432fbb3b02632105` のコミットにマッチします。 | + +## 親で検索 + +`parent` 修飾子は、親コミットが特定の SHA-1 ハッシュのコミットにマッチします。 + +| 修飾子 | サンプル | +| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| parent:HASH | [**parent:124a9a0ee1d8f1e15e833aff432fbb3b02632105**](https://github.com/github/gitignore/search?q=parent%3A124a9a0ee1d8f1e15e833aff432fbb3b02632105&type=Commits&utf8=%E2%9C%93) は、ハッシュ `124a9a0ee1d8f1e15e833aff432fbb3b02632105` の子コミットにマッチします。 | + +## ツリーで検索 + +`tree` 修飾子は、特定の SHA-1 Git ツリーハッシュのコミットにマッチします。 + +| 修飾子 | サンプル | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | +| tree:HASH | [**tree:99ca967**](https://github.com/github/gitignore/search?q=tree%3A99ca967&type=Commits) は、ツリーハッシュ `99ca967` を参照するコミットにマッチします。 | + +## ユーザまたは Organization のリポジトリ内の検索 + +特定のユーザまたは Organization のすべてのリポジトリのコミットを検索するには、`user` 修飾子または `org` 修飾子を使います。 特定のリポジトリのコミットを検索するには、`repo` 修飾子を使用します。 + +| 修飾子 | サンプル | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**gibberish user:defunkt**](https://github.com/search?q=gibberish+user%3Adefunkt&type=Commits&utf8=%E2%9C%93) は、@defunkt が保有するリポジトリの「gibberish」という単語があるコミットメッセージにマッチします。 | +| org:ORGNAME | [**test org:github**](https://github.com/search?utf8=%E2%9C%93&q=test+org%3Agithub&type=Commits) は、@github が保有するリポジトリの「test」という単語があるコミットメッセージにマッチします。 | +| repo:USERNAME/REPO | [**language repo:defunkt/gibberish**](https://github.com/search?utf8=%E2%9C%93&q=language+repo%3Adefunkt%2Fgibberish&type=Commits) は、@defunkt の「gibberish」リポジトリにある「language」という単語があるコミットメッセージにマッチします。 | + +## リポジトリの可視性によるフィルタ + +`is` 修飾子は、指定した可視性を持つリポジトリからのコミットにマッチします。 For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." + +| 修飾子 | 例 | ------------- | ------------- |{% ifversion fpt or ghes %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Commits) はパブリックリポジトリへのコミットにマッチします。{% endif %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Commits) は内部リポジトリへのコミットにマッチします。 | `is:private` | [**is:private**](https://github.com/search?q=is%3Aprivate&type=Commits) はプライベートリポジトリへのコミットに一致します。 + +## 参考リンク + +- 「[検索結果をソートする](/search-github/getting-started-with-searching-on-github/sorting-search-results/)」 diff --git a/translations/ja-JP/content/search-github/searching-on-github/searching-discussions.md b/translations/ja-JP/content/search-github/searching-on-github/searching-discussions.md new file mode 100644 index 0000000000..f99ba40334 --- /dev/null +++ b/translations/ja-JP/content/search-github/searching-on-github/searching-discussions.md @@ -0,0 +1,113 @@ +--- +title: ディスカッションを検索する +intro: '{% data variables.product.product_name %} 上のディスカッションを検索し、検索修飾子を使用して検索結果を絞り込むことができます。' +versions: + fpt: '*' +topics: + - GitHub search +redirect_from: + - /github/searching-for-information-on-github/searching-discussions + - /github/searching-for-information-on-github/searching-on-github/searching-discussions +--- + +## ディスカッションの検索について + +{% data variables.product.product_name %} 全体にわたってグローバルにディスカッションを検索できます。あるいは、特定の Organization のみのディスカッションの検索もできます。 詳細は「[{% data variables.product.prodname_dotcom %} での検索について](/github/searching-for-information-on-github/about-searching-on-github)」を参照してください。 + +{% data reusables.search.syntax_tips %} + +## タイトル、本文、またはコメントで検索 + +`in` 修飾子を使用すると、ディスカッションの検索をタイトル、本文、またはコメントに制限できます。 修飾子を組み合わせて、タイトル、本文、またはコメントの組み合わせを検索することもできます。 `in` 修飾子を省略すると、{% data variables.product.product_name %} はタイトル、本文、およびコメントを検索します。 + +| 修飾子 | サンプル | +|:------------- |:---------------------------------------------------------------------------------------------------------------------------------------- | +| `in:title` | [**welcome in:title**](https://github.com/search?q=welcome+in%3Atitle&type=Discussions) は、タイトルに「welcome」を含むディスカッションにマッチします。 | +| `in:body` | [**error in:title,body**](https://github.com/search?q=onboard+in%3Atitle%2Cbody&type=Discussions) は、タイトルか本文に「onboard」を含むディスカッションにマッチします。 | +| `in:comments` | [**welcome in:title**](https://github.com/search?q=thanks+in%3Acomment&type=Discussions) は、ディスカッションのコメントに「thanks」を含むディスカッションにマッチします。 | + +## ユーザまたは Organization のリポジトリ内の検索 + +特定のユーザまたは Organization のすべてのリポジトリのディスカッションを検索するには、`user` 修飾子または `org` 修飾子を使います。 特定のリポジトリのディスカッションを検索するには、`repo` 修飾子を使います。 + +| 修飾子 | サンプル | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**user:octocat feedback**](https://github.com/search?q=user%3Aoctocat+feedback&type=Discussions) @octocat が所有するリポジトリからの「feedback」という単語を含むディスカッションにマッチします。 | +| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=Discussions&utf8=%E2%9C%93) は、GitHub Organization が保有するリポジトリのディスカッションにマッチします。 | +| repo:USERNAME/REPOSITORY | [**repo:nodejs/node created:<2021-01-01**](https://github.com/search?q=repo%3Anodejs%2Fnode+created%3A%3C2020-01-01&type=Discussions) は、2021年1月以前に作成された@nodejs の Node.js ランタイムプロジェクトからのディスカッションにマッチします。 | + +## リポジトリの可視性によるフィルタ + +`is` 修飾子を使用して、ディスカッションを含むリポジトリの可視性でフィルタできます。 For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." + +| 修飾子 | 例 | :- | :- |{% ifversion fpt or ghes %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Discussions) はパブリックリポジトリへのディスカッションにマッチします。{% endif %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Discussions) は内部リポジトリへのディスカッションにマッチします。 | `is:private` | [**is:private tiramisu**](https://github.com/search?q=is%3Aprivate+tiramisu&type=Discussions) は、アクセス可能なプライベートリポジトリに「tiramisu」という単語を含むディスカッションにマッチします。 + +## 作者で検索 + +`author` 修飾子は、特定のユーザが作成したディスカッションを表示します。 + +| 修飾子 | サンプル | +|:------------------------- |:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| author:USERNAME | [**cool author:gjtorikian**](https://github.com/search?q=cool+author%3Aoctocat&type=Discussions) は、@octocat が作成した「cool」という単語を含むディスカッションにマッチします。 | +| | [**bootstrap in:body author:octocat**](https://github.com/search?q=bootstrap+in%3Abody+author%3Aoctocat&type=Discussions) は、@octocat が作成した「bootstrap」という単語を含むディスカッションにマッチします。 | + +## コメントした人で検索 + +`commenter` 修飾子は、特定のユーザからのコメントを含むディスカッションを検索します。 + +| 修飾子 | サンプル | +|:------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| commenter:USERNAME | [**github commenter:becca org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Abecca+org%3Agithub&type=Discussions) は、@beccaのコメントがあり、「github」という単語がある、GitHub が所有するリポジトリのディスカッションにマッチします。 | + +## ディスカッションに関与しているユーザで検索 + +`involves` 修飾子では、特定のユーザが関与するディスカッションを表示します。 修飾子は、特定のユーザが作成したディスカッション、特定のユーザをメンションしたディスカッション、特定のユーザによるコメントを含むディスカッションを返します。 `involves` 修飾子は、単一ユーザについて、`author`、`mentions`、および `commenter` を論理 OR でつなげます。 + +| 修飾子 | サンプル | +|:------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| involves:USERNAME | **[involves:becca involves:octocat](https://github.com/search?q=involves%3Abecca+involves%3Aoctocat&type=Discussions)** は、@becca または @octocat が関与しているディスカッションにマッチします。 | +| | [**NOT beta in:body involves:becca**](https://github.com/search?q=NOT+beta+in%3Abody+involves%3Abecca&type=Discussions) は、本文に「beta」という単語を含まず、@becca が関与しているディスカッションにマッチします。 | + +## コメントの数で検索 + +コメント数で検索するには、不等号や範囲の修飾子とともに `comments` 修飾子を使います。 詳しい情報については、「[検索構文を理解する](/github/searching-for-information-on-github/understanding-the-search-syntax)」を参照してください。 + +| 修飾子 | サンプル | +|:------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------- | +| comments:n | [**comments:>100**](https://github.com/search?q=comments%3A%3E100&type=Discussions) は、コメント数が 100 を超えるクローズしたディスカッションにマッチします。 | +| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Discussions)は、500 から 1,000 までの範囲のコメント数のディスカッションにマッチします。 | + +## インタラクションの数で検索 + +`interactions` 修飾子を使用したインタラクションの数と、不等号や範囲の修飾子によってディスカッションをフィルタできます。 インタラクションの数は、ディスカッションに対するリアクションとコメントの数のことです。 詳しい情報については、「[検索構文を理解する](/github/searching-for-information-on-github/understanding-the-search-syntax)」を参照してください。 + +| 修飾子 | サンプル | +|:------------------------- |:----------------------------------------------------------------------------------------------------------------------------------- | +| interactions:n | [** interactions:>2000**](https://github.com/search?q=interactions%3A%3E2000) は、インタラクションの数が 2,000 以上あるディスカッションにマッチします。 | +| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) は、500～1,000 の範囲のインタラクションとのディスカッションにマッチします。 | + +## リアクションの数で検索 + +不等号や範囲の修飾子と一緒に `reactions` 修飾子を使用して、リアクションの数でディスカッションをフィルタすることができます。 詳しい情報については、「[検索構文を理解する](/github/searching-for-information-on-github/understanding-the-search-syntax)」を参照してください。 + +| 修飾子 | サンプル | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------ | +| reactions:n | [** reactions:>1000**](https://github.com/search?q=reactions%3A%3E500) は、リアクションの数が 500 以上あるディスカッションにマッチします。 | +| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) は、リアクションの数が 500～1,000 の範囲のディスカッションにマッチします。 | + +## ディスカッションの作成時期または最終更新時期で検索 + +作成時期または最終更新時期でディスカッションをフィルタできます。 ディスカッションの作成時期については、`created` の修飾子を使います。ディスカッションの最終更新時期で表示するには、`updated` の修飾子を使います。 + +両方の修飾子は、パラメータとして日付を使います。 {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| 修飾子 | サンプル | +|:-------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| created:YYYY-MM-DD | [**created:>2020-11-15**](https://github.com/search?q=created%3A%3E%3D2020-11-15&type=discussions) は、2020 年 11 月 15 日以降に作成されたディスカッションにマッチします。 | +| updated:YYYY-MM-DD | [**weird in:body updated:>=2020-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2020-12-01&type=Discussions) は、2020 年 12 月以降に更新された、本文に「weird」という単語を含むディスカッションにマッチします。 | + +## 参考リンク + +- 「[検索結果をソートする](/search-github/getting-started-with-searching-on-github/sorting-search-results/)」 diff --git a/translations/ja-JP/content/search-github/searching-on-github/searching-for-packages.md b/translations/ja-JP/content/search-github/searching-on-github/searching-for-packages.md new file mode 100644 index 0000000000..63e14f47fc --- /dev/null +++ b/translations/ja-JP/content/search-github/searching-on-github/searching-for-packages.md @@ -0,0 +1,45 @@ +--- +title: パッケージを検索する +intro: '{% data variables.product.product_name %} 上のパッケージを検索し、検索修飾子を使用して検索結果を絞ることができます。' +product: '{% data reusables.gated-features.packages %}' +permissions: Anyone can search for packages they have access to. +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +redirect_from: + - /github/searching-for-information-on-github/searching-for-packages + - /github/searching-for-information-on-github/searching-on-github/searching-for-packages +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +## パッケージの検索について + +{% data variables.product.product_name %} 全体にわたってグローバルにパッケージを検索できます。あるいは、特定の Organization のみのパッケージの検索もできます。 詳細は「[{% data variables.product.prodname_dotcom %} での検索について](/search-github/getting-started-with-searching-on-github/about-searching-on-github)」を参照してください。 + +{% ifversion ghes %} +You can only search for packages on {% data variables.product.product_name %}, not {% data variables.product.prodname_dotcom_the_website %}, even if {% data variables.product.prodname_github_connect %} is enabled. +{% endif %} + +{% data reusables.search.syntax_tips %} + +## ユーザまたは Organization のパッケージ内の検索 + +特定のユーザまたは Organization が所有するパッケージを検索するには、`user` 修飾子または `org` 修飾子を使います。 + +| 修飾子 | サンプル | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**user:codertocat**](https://github.com/search?q=user%3Acodertocat&type=RegistryPackages) は、@codertocat が所有するパッケージにマッチします。 | +| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=RegistryPackages) は、{% data variables.product.prodname_dotcom %} Organization が所有するパッケージにマッチします。 | + +## パッケージの可視性によるフィルタリング + +パッケージがパブリックかプライベートかを基準に検索をフィルタリングするには、`is` 修飾子を使用します。 + +| 修飾子 | サンプル | +| ------------ | ------------------------------------------------------------------------------------------------------------------------------------ | +| `is:public` | [**is:public angular**](https://github.com/search?q=is%3Apublic+angular&type=RegistryPackages) は、「angular」という単語を含むパブリックパッケージにマッチします。 | +| `is:private` | [**is:private php**](https://github.com/search?q=is%3Aprivate+php&type=RegistryPackages) は、「php」という単語を含むプライベートパッケージにマッチします。 | diff --git a/translations/ja-JP/content/search-github/searching-on-github/searching-for-repositories.md b/translations/ja-JP/content/search-github/searching-on-github/searching-for-repositories.md new file mode 100644 index 0000000000..6e97ac196e --- /dev/null +++ b/translations/ja-JP/content/search-github/searching-on-github/searching-for-repositories.md @@ -0,0 +1,201 @@ +--- +title: リポジトリを検索する +intro: '{% data variables.product.product_name %} 上のリポジトリを検索することができます。そして、これらのリポジトリを検索する修飾子を組み合わせることで、検索結果を絞ることができます。' +redirect_from: + - /articles/searching-repositories/ + - /articles/searching-for-repositories + - /github/searching-for-information-on-github/searching-for-repositories + - /github/searching-for-information-on-github/searching-on-github/searching-for-repositories +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +shortTitle: Search for repositories +--- + +{% data variables.product.product_location %} 全体にわたってグローバルにリポジトリを検索できます。あるいは、特定の Organization のみのリポジトリの検索もできます。 詳細は「[{% data variables.product.prodname_dotcom %} での検索について](/search-github/getting-started-with-searching-on-github/about-searching-on-github)」を参照してください。 + +フォークを検索結果に含めるためには、クエリに `fork:true` または `fork:only` を追加する必要があります。 詳細は「[フォーク内で検索する](/search-github/searching-on-github/searching-in-forks)」を参照してください。 + +{% data reusables.search.syntax_tips %} + +## リポジトリ名、説明、または README ファイルの内容で検索 + +`in` 修飾子によって、リポジトリ名、リポジトリの説明、README ファイルの内容や、これらの組み合わせに限定した検索ができます。 この修飾子を省略した場合、リポジトリ名および説明だけが検索されます。 + +| 修飾子 | サンプル | +| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `in:name` | [**jquery in:name**](https://github.com/search?q=jquery+in%3Aname&type=Repositories) は、リポジトリ名に「jquery」が含まれるリポジトリにマッチします。 | +| `in:description` | [**jquery in:name,description**](https://github.com/search?q=jquery+in%3Aname%2Cdescription&type=Repositories) は、リポジトリ名または説明に「jquery」が含まれるリポジトリにマッチします。 | +| `in:readme` | [**jquery in:readme**](https://github.com/search?q=jquery+in%3Areadme&type=Repositories) は、リポジトリの README ファイルで「jquery」をメンションしているリポジトリにマッチします。 | +| `repo:owner/name` | [**repo:octocat/hello-world**](https://github.com/search?q=repo%3Aoctocat%2Fhello-world) は、特定のリポジトリ名にマッチします。 | + +## リポジトリの内容で検索 + +`in:readme` 修飾子を使用すると、リポジトリの README ファイルの内容に基づいてリポジトリを検索できます。 詳細は「[README について](/github/creating-cloning-and-archiving-repositories/about-readmes)」を参照してください。 + +`in:readme` は、特定の内容に基づいてリポジトリを検索する唯一の方法です。 リポジトリ内の特定のファイルや内容を検索するには、ファイルファインダー、またはコード固有の検索修飾子を使います。 詳細は「[ {% data variables.product.prodname_dotcom %}でファイルを検索する](/search-github/searching-on-github/finding-files-on-github)」および「[コードの検索](/search-github/searching-on-github/searching-code)」を参照してください。 + +| 修飾子 | サンプル | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | +| `in:readme` | [**octocat in:readme**](https://github.com/search?q=octocat+in%3Areadme&type=Repositories) は、リポジトリの README ファイルで「octocat」をメンションしているリポジトリにマッチします。 | + +## ユーザまたは Organization のリポジトリ内の検索 + +特定のユーザまたは Organization のすべてのリポジトリで検索するには、`user` 修飾子または `org` 修飾子を使います。 + +| 修飾子 | サンプル | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| user:USERNAME | [**user:defunkt forks:>100**](https://github.com/search?q=user%3Adefunkt+forks%3A%3E%3D100&type=Repositories) は、フォーク数が 100 より多い @defunkt からのリポジトリにマッチします。 | +| org:ORGNAME | [**org:github**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub&type=Repositories) は、GitHub からのリポジトリにマッチします。 | + +## リポジトリのサイズで検索 + +`size` 修飾子は、不等号や範囲の修飾子を使うことで、特定のサイズ (キロバイト) に合致するリポジトリを表示します。 詳しい情報については、「[検索構文を理解する](/github/searching-for-information-on-github/understanding-the-search-syntax)」を参照してください。 + +| 修飾子 | サンプル | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------- | +| size:n | [**size:1000**](https://github.com/search?q=size%3A1000&type=Repositories) は、ちょうど 1 MB のリポジトリにマッチします。 | +| | [**size:>=30000**](https://github.com/search?q=size%3A%3E%3D30000&type=Repositories) は、30 MB 以上のリポジトリにマッチします。 | +| | [**size:<50**](https://github.com/search?q=size%3A%3C50&type=Repositories) は、50 KB 未満のリポジトリにマッチします。 | +| | [**size:50..120**](https://github.com/search?q=size%3A50..120&type=Repositories) は、50 KB から 120 KB までのリポジトリにマッチします。 | + +## フォロワーの数の検索 + +`followers` 修飾子と、不等号や範囲の修飾子を使用すると、リポジトリをフォローしているユーザーの数に基づいてリポジトリをフィルタリングできます。 詳しい情報については、「[検索構文を理解する](/github/searching-for-information-on-github/understanding-the-search-syntax)」を参照してください。 + +| 修飾子 | サンプル | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| followers:n | [**node followers:>=10000**](https://github.com/search?q=node+followers%3A%3E%3D10000) は、「node」という単語にメンションしている、10,000 人以上のフォロワーがいるリポジトリにマッチします。 | +| | [**styleguide linter followers:1..10**](https://github.com/search?q=styleguide+linter+followers%3A1..10&type=Repositories) は、「styleguide linter」という単語にメンションしている、フォロアーが 1 人から 10 人までのリポジトリにマッチします。 | + +## フォークの数で検索 + +`forks` 修飾子は、不等号や範囲の修飾子を使って、リポジトリが持つべきフォークの数を指定します。 詳しい情報については、「[検索構文を理解する](/github/searching-for-information-on-github/understanding-the-search-syntax)」を参照してください。 + +| 修飾子 | サンプル | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------- | +| forks:n | [**forks:5**](https://github.com/search?q=forks%3A5&type=Repositories) は、フォーク数が 5 のリポジトリだけにマッチします。 | +| | [**forks:>=205**](https://github.com/search?q=forks%3A%3E%3D205&type=Repositories) は、フォーク数が 205 以上のリポジトリにマッチします。 | +| | [**forks:<90**](https://github.com/search?q=forks%3A%3C90&type=Repositories) は、フォーク数が 90 未満のリポジトリにマッチします。 | +| | [**forks:10..20**](https://github.com/search?q=forks%3A10..20&type=Repositories) は、フォーク数が 10 から 20 までのリポジトリにマッチします。 | + +## Star の数で検索 + +不等号や範囲の修飾子を使って、リポジトリの Star の数でリポジトリを検索できます。 詳しい情報については「[Star を付けてリポジトリを保存する](/github/getting-started-with-github/saving-repositories-with-stars)」および「[検索構文を理解する](/github/searching-for-information-on-github/understanding-the-search-syntax)」を参照してください。 + +| 修飾子 | サンプル | +| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| stars:n | [**stars:500**](https://github.com/search?utf8=%E2%9C%93&q=stars%3A500&type=Repositories) は、Star がちょうど 500 のリポジトリにマッチします。 | +| | [**stars:10..20**](https://github.com/search?q=stars%3A10..20+size%3A%3C1000&type=Repositories) は、1000 KB 未満で、Star が 10 から 20 のリポジトリにマッチします。 | +| | [**stars:>=500 fork:true language:php**](https://github.com/search?q=stars%3A%3E%3D500+fork%3Atrue+language%3Aphp&type=Repositories) は、PHP 形式のフォークされたリポジトリを含め Star が 500 以上のリポジトリにマッチします。 | + +## リポジトリの作成時期や最終更新時期で検索 + +作成時期や最終更新時期でリポジトリをフィルタリングできます。 リポジトリの作成時期については、`created` 修飾子を使います。リポジトリの最終更新時期で見つけるには、`pushed` 修飾子を使います。 `pushed` 修飾子は、リポジトリのいずれかのブランチに対する一番最近のコミットでソートされた、リポジトリのリストを表示します。 + +どちらの修飾子も、パラメータとして日付を使います。 {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| 修飾子 | サンプル | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| created:YYYY-MM-DD | [**webos created:<2011-01-01**](https://github.com/search?q=webos+created%3A%3C2011-01-01&type=Repositories) は、2011 年より前に作成された「webos」という単語があるリポジトリにマッチします。 | +| pushed:YYYY-MM-DD | [**css pushed:>2013-02-01**](https://github.com/search?utf8=%E2%9C%93&q=css+pushed%3A%3E2013-02-01&type=Repositories) は、2013 年 1 月より後にプッシュされた「css」という単語があるリポジトリにマッチします。 | +| | [**case pushed:>=2013-03-06 fork:only**](https://github.com/search?q=case+pushed%3A%3E%3D2013-03-06+fork%3Aonly&type=Repositories) は、2013 年 3 月 6 日以降にプッシュされ、フォークであり、「case」という単語があるリポジトリにマッチします。 | + +## 言語で検索 + +リポジトリのコードの言語に基づいてリポジトリを検索できます。 + +| 修飾子 | サンプル | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| language:LANGUAGE | [**rails language:javascript**](https://github.com/search?q=rails+language%3Ajavascript&type=Repositories) は、JavaScript 形式で記述された「rails」という単語があるリポジトリにマッチします。 | + +## Topics で検索 + +特定の Topics で分類されたすべてのリポジトリを見つけることができます。 詳細は「[トピックでリポジトリを分類する](/github/administering-a-repository/classifying-your-repository-with-topics)」を参照してください。 + +| 修飾子 | サンプル | +| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | +| topic:TOPIC | [**topic:jekyll**](https://github.com/search?utf8=%E2%9C%93&q=topic%3Ajekyll&type=Repositories&ref=searchresults) は、Topics「jekyll」で分類されたリポジトリにマッチします。 | + +## Topics の数で検索 + +`topics` 修飾子と、不等号や範囲の修飾子を使うと、リポジトリに適用された Topics の数でリポジトリを検索できます。 詳しい情報については「[Topics によるリポジトリの分類](/github/administering-a-repository/classifying-your-repository-with-topics)」および「[検索構文を理解する](/github/searching-for-information-on-github/understanding-the-search-syntax)」を参照してください。 + +| 修飾子 | サンプル | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | +| topics:n | [**topics:5**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A5&type=Repositories&ref=searchresults) は、5 つのトピックがあるリポジトリにマッチします。 | +| | [**topics:>3**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A%3E3&type=Repositories&ref=searchresults) は、4 つ以上のトピックがあるリポジトリにマッチします。 | + +{% ifversion fpt or ghes %} + +## ライセンスで検索 + +リポジトリのライセンスの種類に基づいてリポジトリを検索できます。 特定のライセンスまたはライセンスファミリーによってリポジトリをフィルタリングするには、ライセンスキーワードを使う必要があります。 詳細は「[リポジトリのライセンス](/github/creating-cloning-and-archiving-repositories/licensing-a-repository)」を参照してください。 + +| 修飾子 | サンプル | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| license:LICENSE_KEYWORD | [**license:apache-2.0**](https://github.com/search?utf8=%E2%9C%93&q=license%3Aapache-2.0&type=Repositories&ref=searchresults) は、Apache ライセンス 2.0 によりライセンスされたリポジトリにマッチします。 | + +{% endif %} + +## リポジトリの可視性で検索 + +リポジトリの可視性に基づいて検索を絞り込むことができます。 For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." + +| Qualifier | Example | ------------- | ------------- |{% ifversion fpt or ghes %} | `is:public` | [**is:public org:github**](https://github.com/search?q=is%3Apublic+org%3Agithub&type=Repositories) matches public repositories owned by {% data variables.product.company_short %}.{% endif %} | `is:internal` | [**is:internal test**](https://github.com/search?q=is%3Ainternal+test&type=Repositories) matches internal repositories that you can access and contain the word "test". | `is:private` | [**is:private pages**](https://github.com/search?q=is%3Aprivate+pages&type=Repositories) は、自分がアクセスできて「pages」という単語を含むプライベートリポジトリにマッチします。 + +{% ifversion fpt %} + +## リポジトリがミラーかどうかで検索 + +リポジトリがミラーか、それ以外にホストされているかに基づいてリポジトリを検索できます。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} でオープンソースにコントリビュートする方法を見つける](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)」を参照してください。 + +| 修飾子 | サンプル | +| -------------- | --------------------------------------------------------------------------------------------------------------------------------------- | +| `mirror:true` | [**mirror:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Atrue+GNOME&type=) は、ミラーで「GNOME」という単語を含むリポジトリにマッチします。 | +| `mirror:false` | [**mirror:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Afalse+GNOME&type=)は、ミラーではなく、かつ「GNOME」という単語を含むリポジトリにマッチします。 | + +{% endif %} + +## リポジトリがアーカイブされているかどうかで検索 + +アーカイブされているかどうかでリポジトリを検索できます。 For more information, see "[Archiving repositories](/repositories/archiving-a-github-repository/archiving-repositories)." + +| 修飾子 | サンプル | +| ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | +| `archived:true` | [**archived:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Atrue+GNOME&type=) は、「GNOME」という単語を含むアーカイブされたリポジトリにマッチします。 | +| `archived:false` | [**archived:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Afalse+GNOME&type=) は、「GNOME」という単語を含む、アーカイブされていないリポジトリにマッチします。 | + +{% ifversion fpt %} + +## `good first issue` ラベルや `help wanted` ラベルの付いた Issue の数で検索 + +`help-wanted` ラベルや `good-first-issue` ラベルの付いた Issue の最低数があるリポジトリを、`help-wanted-issues:>n` 修飾子や `good-first-issues:>n` 修飾子によって検索できます。 詳細は、「[ラベルを使用してプロジェクトに役立つコントリビューションを促す](/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels)」を参照してください。 + +| 修飾子 | サンプル | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `good-first-issues:>n` | [**good-first-issues:>2 javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+good-first-issues%3A%3E2&type=) は、「javascript」という単語を含む、`good-first-issue` ラベルが付いた３つ以上の Issue のあるリポジトリにマッチします。 | +| `help-wanted-issues:>n` | [**help-wanted-issues:>4 react**](https://github.com/search?utf8=%E2%9C%93&q=react+help-wanted-issues%3A%3E4&type=) は、「React」という単語を含む、`help-wanted` ラベルが付いた 5 つ以上の Issue のあるリポジトリにマッチします。 | + +## Search based on ability to sponsor + +You can search for repositories whose owners can be sponsored on {% data variables.product.prodname_sponsors %} with the `is:sponsorable` qualifier. 詳しい情報については「[{% data variables.product.prodname_sponsors %}について](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)」を参照してください。 + +You can search for repositories that have a funding file using the `has:funding-file` qualifier. For more information, see "[About FUNDING files](/github/administering-a-repository/managing-repository-settings/displaying-a-sponsor-button-in-your-repository#about-funding-files)." + +| 修飾子 | サンプル | +| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `is:sponsorable` | [**is:sponsorable**](https://github.com/search?q=is%3Asponsorable&type=Repositories) matches repositories whose owners have a {% data variables.product.prodname_sponsors %} profile. | +| `has:funding-file` | [**has:funding-file**](https://github.com/search?q=has%3Afunding-file&type=Repositories) matches repositories that have a FUNDING.yml file. | + +{% endif %} + +## 参考リンク + +- 「[検索結果をソートする](/search-github/getting-started-with-searching-on-github/sorting-search-results/)」 +- [フォーク内を検索する](/search-github/searching-on-github/searching-in-forks) diff --git a/translations/ja-JP/content/search-github/searching-on-github/searching-github-marketplace.md b/translations/ja-JP/content/search-github/searching-on-github/searching-github-marketplace.md new file mode 100644 index 0000000000..0448fa425b --- /dev/null +++ b/translations/ja-JP/content/search-github/searching-on-github/searching-github-marketplace.md @@ -0,0 +1,38 @@ +--- +title: GitHub Marketplace の検索 +intro: '{% data variables.product.prodname_marketplace %} で使用できるアプリケーションとアクションを検索できます。' +versions: + fpt: '*' +topics: + - GitHub search +redirect_from: + - /github/searching-for-information-on-github/searching-github-marketplace + - /github/searching-for-information-on-github/searching-on-github/searching-github-marketplace +shortTitle: Search GitHub Marketplace +--- + +## {% data variables.product.prodname_marketplace %} の検索について + +{% data variables.product.prodname_marketplace %} のアプリケーションとアクションは、次の2つの方法で検索できます。 + +- {% data variables.product.prodname_marketplace %} 内から検索する。 +- {% data variables.product.prodname_dotcom_the_website %} のすべてで検索してから、検索結果を絞り込む。 + +## {% data variables.product.prodname_marketplace %} 内から検索する + +1. 任意のページの上部で**Marketplace**をクリックしてください。 ![Marketplace リンク](/assets/images/help/search/marketplace-link.png) +2. キーワードを入力して **Enter**キーを押します。 ![{% data variables.product.prodname_marketplace %} で文法チェッカーを検索する](/assets/images/help/search/marketplace-apps-and-actions-search-field.png) +3. オプションで、左サイドバーの1つまたは複数のオプションをクリックして、検索結果を絞り込みます。 + +## {% data variables.product.prodname_dotcom_the_website %} を検索する + +{% data variables.product.prodname_dotcom_the_website %} の全体を検索するときは常に、検査結果を絞り込んでマッチするアプリケーションとアクションを {% data variables.product.prodname_marketplace %} から見つけることができます。 + +1. Https://github.com/search に移動します。 +2. キーワードを入力して **Enter**キーを押します。 ![検索フィールド](/assets/images/help/search/search-field.png) +3. 左のサイドバーで [**Marketplace**] をクリックします。 ![文法チェッカーの検索結果で、Marketplaceのサイドメニューオプションがハイライトされている](/assets/images/help/search/marketplace-left-side-navigation.png) + +## 参考リンク + +- [{% data variables.product.prodname_marketplace %}について](/github/customizing-your-github-workflow/about-github-marketplace) +- [ワークフローで{% data variables.product.prodname_marketplace %}からのアクションを利用する](/actions/automating-your-workflow-with-github-actions/using-actions-from-github-marketplace-in-your-workflow) diff --git a/translations/ja-JP/content/search-github/searching-on-github/searching-in-forks.md b/translations/ja-JP/content/search-github/searching-on-github/searching-in-forks.md new file mode 100644 index 0000000000..29f31f5344 --- /dev/null +++ b/translations/ja-JP/content/search-github/searching-on-github/searching-in-forks.md @@ -0,0 +1,32 @@ +--- +title: フォーク内を検索する +intro: 'デフォルトでは[フォーク](/articles/about-forks)は検索結果に表示されません。 リポジトリの検索にフォークを含めることができます。一定の要件を満たす場合は、コードの検索でもできます。' +redirect_from: + - /articles/searching-in-forks + - /github/searching-for-information-on-github/searching-in-forks + - /github/searching-for-information-on-github/searching-on-github/searching-in-forks +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +[リポジトリの検索](/search-github/searching-on-github/searching-for-repositories)結果でフォークを表示するには、クエリに `fork:true` または `fork:only` を追加します。 + +フォークは、親リポジトリより Star が多い場合に限り、[コード検索](/search-github/searching-on-github/searching-code)用にインデックスされます。 親より Star が少ないフォークのコードは検索できません。 コード検索結果で親リポジトリより Star の多いフォークを表示するには、クエリに `fork:true` または `fork:only` を追加します。 + +`fork:true` 修飾子は、フォークを含む、検索クエリにマッチする全ての結果を表示できます。 `fork:only` 修飾子は、検索クエリにマッチするフォークだけを表示できます。__ + +| 修飾子 | サンプル | +| ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `fork:true` | [**github fork:true**](https://github.com/search?q=github+fork%3Atrue&type=Repositories) は、フォークを含め、「github」という単語を含む全てのリポジトリにマッチします。 | +| | [**android language:java fork:true**](https://github.com/search?q=android+language%3Ajava+fork%3Atrue&type=Code) は、フォークおよびリポジトリの両方にある Java で記述された「android」という単語があるコードにマッチします。 | +| `fork:only` | [**github fork:only**](https://github.com/search?q=github+fork%3Aonly&type=Repositories) は、「github」という単語を含むすべてのフォークリポジトリにマッチします。 | +| | [**forks:>500 fork:only**](https://github.com/search?q=forks%3A%3E500+fork%3Aonly&type=Repositories) は、フォークが 500 超の、フォークであるリポジトリのみを表示します。 | + +## 参考リンク + +- [フォークについて](/articles/about-forks) +- "[GitHub での検索について](/search-github/getting-started-with-searching-on-github/about-searching-on-github)" 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 new file mode 100644 index 0000000000..879389180e --- /dev/null +++ b/translations/ja-JP/content/search-github/searching-on-github/searching-issues-and-pull-requests.md @@ -0,0 +1,343 @@ +--- +title: Issue およびプルリクエストを検索する +intro: '{% data variables.product.product_name %} 上の Issue およびプルリクエストを検索することができます。そして、これらの検索用修飾子を組み合わせることで、検索結果を絞ることができます。' +redirect_from: + - /articles/searching-issues/ + - /articles/searching-issues-and-pull-requests + - /github/searching-for-information-on-github/searching-issues-and-pull-requests + - /github/searching-for-information-on-github/searching-on-github/searching-issues-and-pull-requests +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +shortTitle: Search issues & PRs +--- + +{% data variables.product.product_name %} 全体にわたってグローバルに Issue およびプルリクエストを検索できます。あるいは、特定の Organization の Issue およびプルリクエストに限った検索もできます。 詳細は「[{% data variables.product.company_short %} での検索について](/search-github/getting-started-with-searching-on-github/about-searching-on-github)」を参照してください。 + +{% tip %} + +**ヒント:**{% ifversion ghes or ghae %} + - この記事には、{% data variables.product.prodname_dotcom %}.com のウェブサイトでの検索例が含まれています。ですが、同じ検索フィルターを {% data variables.product.product_location %} で使えます。{% endif %} + - 検索結果を改良する検索修飾子を追加できる検索構文のリストについては、「[検索構文を理解する](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)」を参照してください。 + - 複数単語の検索用語は引用符で囲みます。 たとえば "In progress" というラベルを持つ Issue を検索したい場合は、`label:"in progress"` とします。 検索では、大文字と小文字は区別されません。 + - {% data reusables.search.search_issues_and_pull_requests_shortcut %} + + {% endtip %} + +## Issue またはプルリクエストに限定した検索 + +デフォルトでは、{% data variables.product.product_name %} の検索は、Issueとプルリクエストの両方を結果表示します。 ですが、`type` 修飾子または `is` 修飾子を使うことで、Issue またはプルリクエストに限った検索ができます。 + +| 修飾子 | サンプル | +| ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `type:pr` | [**cat type:pr**](https://github.com/search?q=cat+type%3Apr&type=Issues) は、「cat」という単語があるプルリクエストにマッチします。 | +| `type:issue` | [**github commenter:defunkt type:issue**](https://github.com/search?q=github+commenter%3Adefunkt+type%3Aissue&type=Issues) は、「github」という単語を含み、かつ、@defunkt によるコメントがある Issue にマッチします。 | +| `is:pr` | [**event is:pr**](https://github.com/search?utf8=%E2%9C%93&q=event+is%3Apr&type=) は、「event」という単語があるプルリクエストにマッチします。 | +| `is:issue` | [**is:issue label:bug is:closed**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aissue+label%3Abug+is%3Aclosed&type=) は、「bug」のラベルが付いたクローズされた Issue にマッチします。 | + +## タイトル、本文、またはコメントで検索 + +`in` 修飾子によって、タイトル、本文、コメントやその組み合わせに限定した検索ができます。 この修飾子を省略した場合、タイトル、本文、そしてコメントがすべて検索されます。 + +| 修飾子 | サンプル | +| ------------- | ------------------------------------------------------------------------------------------------------------------------------ | +| `in:title` | [**warning in:title**](https://github.com/search?q=warning+in%3Atitle&type=Issues) は、タイトルに「warning」を含む Issue にマッチします。 | +| `in:body` | [**error in:title,body**](https://github.com/search?q=error+in%3Atitle%2Cbody&type=Issues) は、タイトルか本文に「error」を含む Issue にマッチします。 | +| `in:comments` | [**shipit in:comments**](https://github.com/search?q=shipit+in%3Acomment&type=Issues) は、コメントで「shipit」にメンションしている Issue にマッチします。 | + +## ユーザまたは Organization のリポジトリ内の検索 + +特定のユーザーや Organization が保有するすべてのリポジトリの Issue とプルリクエストを検索するには、 `user` 修飾子または `org` 修飾子を使います。 特定のリポジトリの Issue やプルリクエストを検索するには、`repo` 修飾子を使います。 + +{% 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 およびプルリクエストをフィルタリングできます。 + +| 修飾子 | サンプル | +| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `state:open` | [**libraries state:open mentions:vmg**](https://github.com/search?utf8=%E2%9C%93&q=libraries+state%3Aopen+mentions%3Avmg&type=Issues) は、「libraries」という単語がある @vmg にメンションしているオープン Issue にマッチします。 | +| `state:closed` | [**design state:closed in:body**](https://github.com/search?utf8=%E2%9C%93&q=design+state%3Aclosed+in%3Abody&type=Issues) は、本文に「design」という単語がある、クローズされた Issue にマッチします。 | +| `is:open` | [**performance is:open is:issue**](https://github.com/search?q=performance+is%3Aopen+is%3Aissue&type=Issues) は、「performance」という単語があるオープン Issue にマッチします。 | +| `is:closed` | [**android is:closed**](https://github.com/search?utf8=%E2%9C%93&q=android+is%3Aclosed&type=) は、「android」という単語があるクローズされた Issue とプルリクエストにマッチします。 | + +## リポジトリの可視性によるフィルタ + +`is` 修飾子を使用して、Issue とプルリクエストを含むリポジトリの可視性でフィルタできます。 For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." + +| Qualifier | Example | ------------- | ------------- |{% ifversion fpt or ghes %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Issues) matches issues and pull requests in public repositories.{% endif %}{% ifversion fpt or ghes or ghae %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Issues) matches issues and pull requests in internal repositories.{% endif %} | `is:private` | [**is:private cupcake**](https://github.com/search?q=is%3Aprivate+cupcake&type=Issues) matches issues and pull requests that contain the word "cupcake" in private repositories you can access. + +## 作者で検索 + +`author` 修飾子によって、特定のユーザまたはインテグレーションアカウントが作成した Issue およびプルリクエストを検索できます。 + +| 修飾子 | サンプル | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| author:USERNAME | [**cool author:gjtorikian**](https://github.com/search?q=cool+author%3Agjtorikian&type=Issues) は、@gjtorikian が作成した「cool」という単語がある Issue とプルリクエストにマッチします。 | +| | [**bootstrap in:body author:mdo**](https://github.com/search?q=bootstrap+in%3Abody+author%3Amdo&type=Issues) は、本文に「bootstrap」という単語を含む @mdo が作成した Issue にマッチします。 | +| author:app/USERNAME | [**author:app/robot**](https://github.com/search?q=author%3Aapp%2Frobot&type=Issues) は、「robot」というインテグレーションアカウントが作成した Issue にマッチします。 | + +## アサインされた人で検索 + +`assignee` 修飾子は、特定のユーザにアサインされた Issue およびプルリクエストを表示します。 アサインされた人がいる Issue およびプルリクエストは、_一切_検索できません。 [アサインされた人がいない Issue およびプルリクエスト](#search-by-missing-metadata)は検索できます。 + +| 修飾子 | サンプル | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| assignee:USERNAME | [**assignee:vmg repo:libgit2/libgit2**](https://github.com/search?utf8=%E2%9C%93&q=assignee%3Avmg+repo%3Alibgit2%2Flibgit2&type=Issues) は、@vmg にアサインされた libgit2 のプロジェクト libgit2 の Issue およびプルリクエストにマッチします。 | + +## メンションで検索 + +`mentions` 修飾子は、特定のユーザーにメンションしている Issue を表示します。 詳細は「[人およびチームにメンションする](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)」を参照してください。 + +| 修飾子 | サンプル | +| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | +| mentions:USERNAME | [**resque mentions:defunkt**](https://github.com/search?q=resque+mentions%3Adefunkt&type=Issues) は、@defunkt にメンションしている「resque」という単語がある Issue にマッチします。 | + +## Team メンションで検索 + +あなたが属する Organization および Team について、 `team` 修飾子により、Organization 内の一定の Team に @メンションしている Issue またはプルリクエストを表示します。 検索を行うには、これらのサンプルの名前をあなたの Organization および Team の名前に置き換えてください。 + +| 修飾子 | サンプル | +| ------------------------- | ------------------------------------------------------------------------------------ | +| team:ORGNAME/TEAMNAME | **team:jekyll/owners** は、`@jekyll/owners` Team がメンションされている Issue にマッチします。 | +| | **team:myorg/ops is:open is:pr** は、`@myorg/ops` Team がメンションされているオープンなプルリクエストにマッチします。 | + +## コメントした人で検索 + +`commenter` 修飾子は、特定のユーザからのコメントを含む Issue を検索します。 + +| 修飾子 | サンプル | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| commenter:USERNAME | [**github commenter:defunkt org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Adefunkt+org%3Agithub&type=Issues) は、@defunkt のコメントがあり、「github」という単語がある、GitHub が所有するリポジトリの Issue にマッチします。 | + +## Issue やプルリクエストに関係したユーザで検索 + +`involves` 修飾子は、特定のユーザが何らかの方法で関与する Issue を表示します。 `involves` 修飾子は、単一ユーザについて、`author`、`assignee`、`mentions`、および `commenter` を論理 OR でつなげます。 言い換えれば、この修飾子は、特定のユーザが作成した、当該ユーザにアサインされた、当該ユーザをメンションした、または、当該ユーザがコメントした、Issue およびプルリクエストを表示します。 + +| 修飾子 | サンプル | +| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 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 %} +## リンクされた 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 %} + +## ラベルで検索 + +`label` 修飾子を使って、ラベルで検索結果を絞り込むことができます。 Issue は複数のラベルがある可能性があることから、各 Issue について異なる修飾子を記載できます。 + +| 修飾子 | サンプル | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| label:LABEL | [**label:"help wanted" language:ruby**](https://github.com/search?utf8=%E2%9C%93&q=label%3A%22help+wanted%22+language%3Aruby&type=Issues) は、Ruby のリポジトリにある「help wanted」のラベルがある Issue にマッチします。 | +| | [**broken in:body -label:bug label:priority**](https://github.com/search?q=broken+in%3Abody+-label%3Abug+label%3Apriority&type=Issues)は、「bug」ラベルはないが「priority」ラベルがある、本文に「broken」という単語がある Issue にマッチします。** | +| | [**label:bug label:resolved**](https://github.com/search?l=&q=label%3Abug+label%3Aresolved&type=Issues) matches issues with the labels "bug" and "resolved."{% ifversion fpt or ghes > 3.2 or ghae-next %} +| | [**label:bug,resolved**](https://github.com/search?q=label%3Abug%2Cresolved&type=Issues) matches issues with the label "bug" or the label "resolved."{% endif %} + +## マイルストーンで検索 + +`milestone` 修飾子は、リポジトリ内の[マイルストーン](/articles/about-milestones)の一部である Issue またはプルリクエストを表示します。 + +| 修飾子 | サンプル | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | +| milestone:MILESTONE | [**milestone:"overhaul"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22overhaul%22&type=Issues)は、「overhaul」という名前のマイルストーンにある Issue にマッチします。 | +| | [**milestone:"bug fix"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22bug+fix%22&type=Issues)は、「bug fix」という名前のマイルストーンにある Issue にマッチします。 | + +## プロジェクトボードで検索 + +リポジトリまたは Organization にある特定の[プロジェクトボード](/articles/about-project-boards/)と関連する Issue を表示するには、`project` 修飾子を使います。 プロジェクトボードはプロジェクトボード番号で検索する必要があります。 プロジェクトボードの URL の末尾に、プロジェクトボード番号が表示されています。 + +| 修飾子 | サンプル | +| -------------------------- | ---------------------------------------------------------------------------------------------- | +| project:PROJECT_BOARD | **project:github/57** は、Organization のプロジェクトボード 57 に関連付けられている、GitHub が所有する Issue にマッチします。 | +| project:REPOSITORY/PROJECT_BOARD | **project:github/linguist/1** は、@github の Linguist リポジトリのプロジェクトボード 1 に関連付けられている Issue にマッチします。 | + +## コミットステータスで検索 + +コミットのステータスでプルリクエストをフィルタリングできます。 [ステータス API](/rest/reference/repos#statuses) または CI サービスを使っている場合、特に役立ちます。 + +| 修飾子 | サンプル | +| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `status:pending` | [**language:go status:pending**](https://github.com/search?utf8=%E2%9C%93&q=language%3Ago+status%3Apending) は、ステータスが pending になっている Go リポジトリにオープンしたプルリクエストにマッチします。 | +| `status:success` | [**is:open status:success finally in:body**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aopen+status%3Asuccess+finally+in%3Abody&type=Issues) は、ステータスが successful になっている body に「finally」という単語があるオープンなプルリクエストにマッチします。 | +| `status:failure` | [**created:2015-05-01..2015-05-30 status:failure**](https://github.com/search?utf8=%E2%9C%93&q=created%3A2015-05-01..2015-05-30+status%3Afailure&type=Issues) は、ステータスが failed になっている 2015 年 5 月にオープンしたプルリクエストにマッチします。 | + +## コミット SHA で検索 + +コミットの特定の SHA ハッシュを知っている場合、その SHA を含むプルリクエストを検索するために使えます。 SHA の構文は、7 字以上であることが必要です。 + +| 修飾子 | サンプル | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | +| SHA | [**e1109ab**](https://github.com/search?q=e1109ab&type=Issues) は、`e1109ab` で始まるコミット SHA のプルリクエストにマッチします。 | +| | [**0eff326d6213c is:merged**](https://github.com/search?q=0eff326d+is%3Amerged&type=Issues) は、`0eff326d6213c`で始まるコミット SHA のマージされたプルリクエストにマッチします。 | + +## ブランチ名で検索 + +元のブランチ (「head」ブランチ) またはマージされるブランチ (「base」ブランチ) でプルリクエストをフィルタリングできます。 + +| 修飾子 | サンプル | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| head:HEAD_BRANCH | [**head:change is:closed is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=head%3Achange+is%3Aclosed+is%3Aunmerged) は、クローズされた「change」という単語から始まる名前のブランチから開かれたプルリクエストに一致します。 | +| base:BASE_BRANCH | [**base:gh-pages**](https://github.com/search?utf8=%E2%9C%93&q=base%3Agh-pages) は、`gh-pages` ブランチにマージされるプルリクエストにマッチします。 | + +## 言語で検索 + +`language` 修飾子により、特定の言語で記述されたリポジトリ内の Issue およびプルリクエストを検索できます。 + +| 修飾子 | サンプル | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | +| language:LANGUAGE | [**language:ruby state:open**](https://github.com/search?q=language%3Aruby+state%3Aopen&type=Issues) は、Ruby のリポジトリにあるオープン Issue にマッチします。 | + +## コメントの数で検索 + +コメントの数で検索するには、[不等号や範囲の修飾子](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)とともに `comments` 修飾子を使います。 + +| 修飾子 | サンプル | +| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | +| comments:n | [**state:closed comments:>100**](https://github.com/search?q=state%3Aclosed+comments%3A%3E100&type=Issues)は、コメント数が 100 を超えるクローズした Issue にマッチします。 | +| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Issues)は、500 から 1,000 までの範囲のコメント数の Issue にマッチします。 | + +## インタラクションの数で検索 + +`interactions` 修飾子と[不等号や範囲の修飾子](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)を使って、Issue や プルリクエストをインタラクションの数でフィルタリングできます。 インタラクションの数とは、1 つの Issue またはプルリクエストにあるリアクションおよびコメントの数のことです。 + +| 修飾子 | サンプル | +| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | +| interactions:n | [** interactions:>2000**](https://github.com/search?q=interactions%3A%3E2000) は、インタラクションの数が 2,000 を超えるプルリクエストまたは Issue にマッチします。 | +| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) は、インタラクションの数が 500 から 1,000 までの範囲のプルリクエストまたは Issue にマッチします。 | + +## リアクションの数で検索 + +`reactions` 修飾子と[不等号や範囲の修飾子](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)を使って、Issue や プルリクエストをリアクションの数でフィルタリングできます。 + +| 修飾子 | サンプル | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | +| reactions:n | [** reactions:>1000**](https://github.com/search?q=reactions%3A%3E1000&type=Issues) は、リアクションの数が 1,000 を超える Issue にマッチします。 | +| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) は、リアクションの数が 500 から 1,000 までの範囲の Issue にマッチします。 | + +## ドラフトプルリクエストを検索 +ドラフトプルリクエストをフィルタリングすることができます。 詳しい情報については[プルリクエストについて](/articles/about-pull-requests#draft-pull-requests)を参照してください。 + +| Qualifier | Example | ------------- | -------------{% ifversion fpt or ghes or ghae %} | `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) は、レビューの準備ができたプルリクエストに一致します。{% else %} | `is:draft` | [**is:draft**](https://github.com/search?q=is%3Adraft) はドラフトプルリクエストに一致します。{% endif %} + +## プルリクエストレビューのステータスおよびレビュー担当者で検索 + +レビュー担当者およびレビューリクエストを受けた人で、[レビューステータス](/articles/about-pull-request-reviews) (_none_、_required_、_approved_、または _changes requested_) でプルリクエストをフィルタリングできます。 + +| 修飾子 | サンプル | +| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `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 or ghes > 3.2 %} +| 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`からのレビューリクエストがあるプルリクエストにマッチします。 リクエストを受けたレビュー担当者は、プルリクエストのレビュー後は検索結果に表示されなくなります。 | + +## Issue やプルリクエストの作成時期や最終更新時期で検索 + +作成時期または最終更新時期で Issue をフィルタリングできます。 Issue の作成時期については、`created` の修飾子を使います。Issue の最終更新時期で表示するには、`updated` の修飾子を使います。 + +どちらの修飾子も、パラメータとして日付を使います。 {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| 修飾子 | サンプル | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| created:YYYY-MM-DD | [**language:c# created:<2011-01-01 state:open**](https://github.com/search?q=language%3Ac%23+created%3A%3C2011-01-01+state%3Aopen&type=Issues) は、C# で記述されたリポジトリの 2011 年より前に作成されたオープンな Issue にマッチします。 | +| updated:YYYY-MM-DD | [**weird in:body updated:>=2013-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2013-02-01&type=Issues) は、2013 年 2 月以降に更新された、本文に「weird」という単語を含む Issue にマッチします。 | + +## Issue やプルリクエストがクローズされた時期で検索 + +`closed` 修飾子を使って、Issue およびプルリクエストを、クローズされているかどうかでフィルタリングできます。 + +この修飾子は、パラメータとして日付を使います。 {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| 修飾子 | サンプル | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| closed:YYYY-MM-DD | [**language:swift closed:>2014-06-11**](https://github.com/search?q=language%3Aswift+closed%3A%3E2014-06-11&type=Issues) は、2014 年 6 月 11 日より後にクローズした Swift の Issue およびプルリクエストにマッチします。 | +| | [**data in:body closed:<2012-10-01**](https://github.com/search?utf8=%E2%9C%93&q=data+in%3Abody+closed%3A%3C2012-10-01+&type=Issues) は、2012 年 10 月より前にクローズされた、body に「data」という単語がある Issue およびプルリクエストにマッチします。 | + +## プルリクエストがマージされた時期で検索 + +`merged` 修飾子を使って、マージされているかどうかでプルリクエストをフィルタリングできます。 + +この修飾子は、パラメータとして日付を使います。 {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| 修飾子 | サンプル | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| merged:YYYY-MM-DD | [**language:javascript merged:<2011-01-01**](https://github.com/search?q=language%3Ajavascript+merged%3A%3C2011-01-01+&type=Issues) は、2011 年より前にマージされた JavaScript のリポジトリにあるプルリクエストにマッチします。 | +| | [**fast in:title language:ruby merged:>=2014-05-01**](https://github.com/search?q=fast+in%3Atitle+language%3Aruby+merged%3A%3E%3D2014-05-01+&type=Issues)は、2014 年 5 月以降にマージされた、タイトルに「fast」という単語がある Ruby のプルリクエストにマッチします。 | + +## プルリクエストがマージされているかどうかで検索 + +`is` 修飾子を使って、マージされたかどうかでプルリクエストをフィルタリングできます。 + +| 修飾子 | サンプル | +| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | +| `is:merged` | [**bugfix is:pr is:merged**](https://github.com/search?utf8=%E2%9C%93&q=bugfix+is%3Apr+is%3Amerged&type=) は、「bugfix」という単語がある、マージされたプルリクエストにマッチします。 | +| `is:unmerged` | [**error is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=error+is%3Aunmerged&type=) は、「error」という単語がある、クローズされた Issue およびプルリクエストにマッチします。 | + +## リポジトリがアーカイブされているかどうかで検索 + +`archived` 修飾子は、Issue またはプルリクエストがアーカイブされたリポジトリにあるかどうかでフィルタリングできます。 + +| 修飾子 | サンプル | +| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `archived:true` | [**archived:true GNOME**](https://github.com/search?q=archived%3Atrue+GNOME&type=) は、アクセスできるアーカイブされたリポジトリの、「GNOME」という単語を含む Issue およびプルリクエストにマッチします。 | +| `archived:false` | [**archived:false GNOME**](https://github.com/search?q=archived%3Afalse+GNOME&type=) は、アクセスできるアーカイブされていないリポジトリの、「GNOME」という単語を含む Issue およびプルリクエストにマッチします。 | + +## 会話がロックされているかどうかで検索 + +`is` 修飾子を使用して、ロックされている会話がある Issue またはプルリクエストを検索することができます。 詳細は「[会話をロックする](/communities/moderating-comments-and-conversations/locking-conversations)」を参照してください。 + +| 修飾子 | サンプル | +| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `is:locked` | [**code of conduct is:locked is:issue archived:false**](https://github.com/search?q=code+of+conduct+is%3Alocked+is%3Aissue+archived%3Afalse) は、アーカイブされていないリポジトリにロックされている会話がある、「code of conduct」という言葉を含む Issue またはプルリクエストにマッチします。 | +| `is:unlocked` | [**code of conduct is:unlocked is:issue archived:false**](https://github.com/search?q=code+of+conduct+is%3Aunlocked+archived%3Afalse) は、アーカイブされていないリポジトリにアンロックされている会話がある、「code of conduct」という言葉を含む Issue またはプルリクエストにマッチします。 | + +## 欠損しているメタデータで検索 + +`no` 修飾子を使って、一定のメタデータがない Issue およびプルリクエストに検索を絞り込むことができます。 こうしたメタデータには、以下のようなものがあります: + +* ラベル +* マイルストーン +* アサインされた人 +* プロジェクト + +| 修飾子 | サンプル | +| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `no:label` | [**priority no:label**](https://github.com/search?q=priority+no%3Alabel&type=Issues) は、ラベルのない、「priority」という単語がある Issue およびプルリクエストにマッチします。 | +| `no:milestone` | [**sprint no:milestone type:issue**](https://github.com/search?q=sprint+no%3Amilestone+type%3Aissue&type=Issues) は、「sprint」という単語を含む、マイルストーンと関連のない Issue にマッチします。 | +| `no:assignee` | [**important no:assignee language:java type:issue**](https://github.com/search?q=important+no%3Aassignee+language%3Ajava+type%3Aissue&type=Issues) は、Java のリポジトリにある、「important」という単語を含む、アサインされた人とは関連付けられていない Issue にマッチします。 | +| `no:project` | [**build no:project**](https://github.com/search?utf8=%E2%9C%93&q=build+no%3Aproject&type=Issues) は、「build」という単語を含む、プロジェクトボードとは関連付けられていない Issue にマッチします。 | + +## 参考リンク + +- 「[検索結果をソートする](/search-github/getting-started-with-searching-on-github/sorting-search-results/)」 diff --git a/translations/ja-JP/content/search-github/searching-on-github/searching-topics.md b/translations/ja-JP/content/search-github/searching-on-github/searching-topics.md new file mode 100644 index 0000000000..1e09a28760 --- /dev/null +++ b/translations/ja-JP/content/search-github/searching-on-github/searching-topics.md @@ -0,0 +1,56 @@ +--- +title: トピックを検索する +intro: '{% data variables.product.product_name %} 上のリポジトリと関連するトピックを検索できます。' +redirect_from: + - /articles/searching-topics + - /github/searching-for-information-on-github/searching-topics + - /github/searching-for-information-on-github/searching-on-github/searching-topics +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +## トピックを {% data variables.product.product_name %} で検索 + +{% data variables.product.product_name %} 上でトピックを検索したり、関連するトピックを調べたり、特定のトピックに関連するリポジトリがどのくらいあるのかを確認したりできます。 + +1. Https://github.com/search に移動します。 +2. トピックのキーワードを入力します。 ![検索フィールド](/assets/images/help/search/search-field.png) +3. 検索をトピックに絞るため、左サイドバーで [**Topics**] をクリックします。 +{% ifversion fpt %} + ![サイドメニューのオプションが強調されたトピックを含む Jekyll リポジトリ検索結果ページ](/assets/images/help/search/topic-left-side-navigation-dotcom.png){% else %} +![Jekyll repository search results page on dotcom with topics side-menu option highlighted](/assets/images/help/search/topic-left-side-navigation.png) +{% endif %} + +## 検索修飾子で検索を絞り込む + +特定のトピックについてのリポジトリを調べたり、コントリビュートするプロジェクトを表示したり、{% data variables.product.product_name %} 上で最も人気のあるトピックを調べたりする場合、検索修飾子である `is:featured`、`is:curated`、`repositories:n`、および `created:YYYY-MM-DD` を使ってトピックを検索します。 + +`is:featured` 検索修飾子は、{% data variables.product.product_name %} 上のほとんどのリポジトリのトピックの検索結果を絞り込みます。 また、これらのトピックは、https://github.com/topics/ に特集されています。 + +`is:curated` 検索修飾子は、検索結果を、コミュニティのメンバーが特別な情報を追加したトピックに限定します。 詳しい情報については、「[リポジトリを調べる](https://github.com/github/explore)」を参照してください。 + +トピックは、日付パラメータと `created:` を使って、作成した日付に基づいてフィルタリングできます。また、`repositories:n` を使って、トピックに関連付けられているリポジトリの数でフィルタリングすることも可能です。 これら両方の修飾子では、[不等号や範囲の修飾子](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)を使うことができます。 + +{% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| 修飾子 | サンプル | +| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `is:curated` | [**is:curated javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+is%3Acurated&type=Topics) は、「javascript」という単語を含む、curatedのTopicsにマッチします。 | +| `is:featured` | [**is:featured javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+is%3Afeatured&type=Topics) は、「javascript」という単語を含む、https://github.com/topics/ で特集されているトピックにマッチします。 | +| `is:not-curated` | [**is:not-curated javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+is%3Anot-curated&type=Topics) は、「javascript」という単語を含む、説明やロゴなどの特別な情報がないトピックにマッチします。 | +| `is:not-featured` | [**is:not-featured javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+is%3Anot-featured&type=Topics)は、「javascript」という単語を含む、https://github.com/topics/ で特集されていないトピックにマッチします。 | +| `repositories:n` | [**repositories:>5000**](https://github.com/search?q=repositories%3A%3E5000) は、5000 を超えるリポジトリに関連付けられているトピックにマッチします。 | +| created:YYYY-MM-DD | [**Serverless created:>2019-01-01**](https://github.com/search?q=Serverless+created%3A%3E2019-01-01&type=Topics) は、2019 年以降に作成された、「serverless」という単語を含むトピックにマッチします。 | + +## トピックでリポジトリを検索 + +`topic:` 修飾子を使って、特定のトピックに関連するすべてのリポジトリを検索できます。 詳しい情報については[リポジトリの検索](/search-github/searching-on-github/searching-for-repositories/#search-by-topic)を参照してください。 + +## 参考リンク +- [Topics によるリポジトリの分類](/articles/classifying-your-repository-with-topics) diff --git a/translations/ja-JP/content/search-github/searching-on-github/searching-users.md b/translations/ja-JP/content/search-github/searching-on-github/searching-users.md new file mode 100644 index 0000000000..3089f25abc --- /dev/null +++ b/translations/ja-JP/content/search-github/searching-on-github/searching-users.md @@ -0,0 +1,106 @@ +--- +title: ユーザを検索する +intro: '{% data variables.product.product_name %} 上のユーザを検索できます。また、これらのユーザの検索修飾子の組み合わせを使って、結果を絞り込むことができます。' +redirect_from: + - /articles/searching-users + - /github/searching-for-information-on-github/searching-users + - /github/searching-for-information-on-github/searching-on-github/searching-users +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +{% data variables.product.product_name %} のユーザを幅広くグローバルに検索できます。 詳細は「[{% data variables.product.company_short %} での検索について](/search-github/getting-started-with-searching-on-github/about-searching-on-github)」を参照してください。 + +{% data reusables.search.syntax_tips %} + +## ユーザまたは Organization に限られた検索 + +初期設定では、ユーザ検索は、個人および Organization の両方を表示します。 ですが、`type` 修飾子を使って、個人アカウントまたは Organization に限定して検索できます。 + +| 修飾子 | サンプル | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `type:user` | [**mike in:name created:<2011-01-01 type:user**](https://github.com/search?q=mike+in:name+created%3A%3C2011-01-01+type%3Auser&type=Users) は、2011 年より前に作成された、「mike」という名前の個人アカウントにマッチします。 | +| `type:org` | [**data in:email type:org**](https://github.com/search?q=data+in%3Aemail+type%3Aorg&type=Users) は、e-mail に「data」という単語がある Organization にマッチします。 | + +## アカウント名、フルネームやパブリックメールで検索 + +`user` や `org` 修飾子を使って、個人ユーザや Organization のアカウント名で検索をフィルタリングできます。 + +`in` 修飾子によって、ユーザ名 (`login`)、フルネーム、パブリックメールやこれらの組み合わせに限定した検索ができます。 この修飾子を削除した場合、ユーザ名およびメールアドレスのみが検索されます。 プライバシー保護のため、メールアドレスのドメイン名では検索できないようになっています。 + +| 修飾子 | サンプル | +| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `user:name` | [**user:octocat**](https://github.com/search?q=user%3Aoctocat&type=Users) は、ユーザ名「octocat」にマッチします。 | +| `org:name` | [**org:electron type:users**](https://github.com/search?q=org%3Aelectron+type%3Ausers&type=Users) は、Electron Organization のアカウント名にマッチします。 | +| `in:login` | [**kenya in:login**](https://github.com/search?q=kenya+in%3Alogin&type=Users) は、ユーザ名に「kenya」という単語があるユーザにマッチします。 | +| `in:name` | [**bolton in:name**](https://github.com/search?q=bolton+in%3Afullname&type=Users) は、本名に「bolton」という単語を含むユーザにマッチします。 | +| `fullname:firstname lastname` | [**fullname:nat friedman**](https://github.com/search?q=fullname%3Anat+friedman&type=Users) は、フルネームが「Nat Friedman」であるユーザにマッチします。 メモ: この修飾子は、スペース文字の有無を区別します。 | +| `in:email` | [**data in:email**](https://github.com/search?q=data+in%3Aemail&type=Users&utf8=%E2%9C%93) は、メールに「data」という単語があるユーザにマッチします。 | + +## ユーザが保有するリポジトリの数で検索 + +`repos` 修飾子および[不等号や範囲の修飾子](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)を使って、ユーザが保有するリポジトリの数でユーザをフィルタリングできます。 + +| 修飾子 | サンプル | +| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | +| repos:n | [**repos:>9000**](https://github.com/search?q=repos%3A%3E%3D9000&type=Users) は、9,000 を超えるレポジトリ数のユーザにマッチします。 | +| | [**bert repos:10..30**](https://github.com/search?q=bert+repos%3A10..30&type=Users) は、10 以上 30 以下のリポジトリを保有しており、ユーザ名または本名に「bert」という単語があるユーザにマッチします。 | + +## 場所で検索 + +プロフィールに表示されている場所でユーザを検索できます。 + +| 修飾子 | サンプル | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | +| location:LOCATION | [**repos:1 location:iceland**](https://github.com/search?q=repos%3A1+location%3Aiceland&type=Users) は、アイスランドに住んでいる、リポジトリをちょうど 1 つ保有するユーザにマッチします。 | + +## リポジトリの言語で検索 + +`language` 修飾子を使って、ユーザが保有するリポジトリの言語でユーザを検索できます。 + +| 修飾子 | サンプル | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| language:LANGUAGE | [**language:javascript location:russia**](https://github.com/search?q=language%3Ajavascript+location%3Arussia&type=Users) は、リポジトリを主に JavaScript で記述している、ロシアに住んでいるユーザにマッチします。 | +| | [**jenny language:javascript in:fullname**](https://github.com/search?q=jenny+language%3Ajavascript+in%3Afullname&type=Users) は、「jenny」という単語がフルネームに含まれる、JavaScript のリポジトリのあるユーザにマッチします。 | + +## ユーザアカウントの作成時期で検索 + +`created` 修飾子を使って、{% data variables.product.product_name %} に参加した時期でユーザをフィルタリングできます。 パラメータとして日付を採用しています。 {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| 修飾子 | サンプル | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| created:YYYY-MM-DD | [**created:<2011-01-01**](https://github.com/search?q=created%3A%3C2011-01-01&type=Users) は、2011 年より前に参加したユーザにマッチします。 | +| | [**created:>=2013-05-11**](https://github.com/search?q=created%3A%3E%3D2013-05-11&type=Users) は、2013 年 5 月 11 日以降に参加したユーザにマッチします。 | +| | [**created:2013-03-06 location:london**](https://github.com/search?q=created%3A2013-03-06+location%3Alondon&type=Users) は、場所をロンドンとして登録している、2013 年 3 月 6 日に参加したユーザにマッチします。 | +| | [**created:2010-01-01..2011-01-01 john in:login**](https://github.com/search?q=created%3A2010-01-01..2011-01-01+john+in%3Ausername&type=Users) は、ユーザ名に「john」という単語がある、2010 年から 2011 年の間に参加したユーザにマッチします。 | + +## フォロワーの数の検索 + +`followers` 修飾子を [不等号や範囲の修飾子](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)とともに使うことで、ユーザのフォロワーの数でユーザをフィルタリングできます。 + +| 修飾子 | サンプル | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | +| followers:n | [**followers:>=1000**](https://github.com/search?q=followers%3A%3E%3D1000&type=Users) は、1,000 以上のフォロワーがいるユーザにマッチします。 | +| | [**sparkle followers:1..10**](https://github.com/search?q=sparkle+followers%3A1..10&type=Users) は、「sparkle」という単語がある名前のフォロワーが 1 名から 10 名までいるユーザにマッチします。 | + +{% ifversion fpt %} + +## Search based on ability to sponsor + +You can search for users and organizations who can be sponsored on {% data variables.product.prodname_sponsors %} with the `is:sponsorable` qualifier. 詳しい情報については「[{% data variables.product.prodname_sponsors %}について](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)」を参照してください。 + +| 修飾子 | サンプル | +| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `is:sponsorable` | [**is:sponsorable**](https://github.com/search?q=is%3Asponsorable&type=Users) matches users and organizations who have a {% data variables.product.prodname_sponsors %} profile. | + +{% endif %} + +## 参考リンク + +- 「[検索結果をソートする](/search-github/getting-started-with-searching-on-github/sorting-search-results/)」 diff --git a/translations/ja-JP/content/search-github/searching-on-github/searching-wikis.md b/translations/ja-JP/content/search-github/searching-on-github/searching-wikis.md new file mode 100644 index 0000000000..dc04992ee6 --- /dev/null +++ b/translations/ja-JP/content/search-github/searching-on-github/searching-wikis.md @@ -0,0 +1,51 @@ +--- +title: ウィキを検索する +intro: '{% data variables.product.product_name %} 上のウィキを検索できます。また、これらのウィキの検索修飾子の組み合わせを使って、結果を絞り込むことができます。' +redirect_from: + - /articles/searching-wikis + - /github/searching-for-information-on-github/searching-wikis + - /github/searching-for-information-on-github/searching-on-github/searching-wikis +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +{% data variables.product.product_name %} 全体にわたってグローバルにウィキを検索できます。あるいは、特定のリポジトリや Organization のみのウィキの検索もできます。 詳細は「[{% data variables.product.company_short %} での検索について](/search-github/getting-started-with-searching-on-github/about-searching-on-github)」を参照してください。 + +{% data reusables.search.syntax_tips %} + +## ユーザまたは Organization のリポジトリ内の検索 + +特定のユーザまたは Organization が所有するすべてのリポジトリのウィキページを表示するには、`user` 修飾子 `org` 修飾子を使います。 特定のリポジトリのウィキページを表示するには、`repo` 修飾子を使います。 + +| 修飾子 | サンプル | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**user:defunkt**](https://github.com/search?q=user%3Adefunkt&type=Wikis) は、@defunkt が所有するリポジトリのウィキページにマッチします。 | +| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=Wikis&utf8=%E2%9C%93) は、GitHub Organization が所有するリポジトリのウィキにマッチします。 | +| repo:USERNAME/REPOSITORY | [**repo:defunkt/gibberish**](https://github.com/search?q=user%3Adefunkt&type=Wikis) は、「gibberish」リポジトリのウィキページにマッチします。 | + +## ウィキページのタイトルまたは本文内の検索 + +`in` は、ウィキページのタイトルまたは本文のテキストに検索を限定します。 この修飾子がない場合、タイトルおよび本文のテキストの両方が検索されます。 + +| 修飾子 | サンプル | +| ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | +| `in:title` | [**usage in:title**](https://github.com/search?q=usage+in%3Atitle&type=Wikis) は、「usage」という単語があるウィキページのタイトルにマッチします。 | +| `in:body` | [**installation in:body**](https://github.com/search?q=installation+in%3Abody&type=Wikis)は、main body テキストに「installation」という単語があるウィキページにマッチします。 | + +## 最終更新日で検索 + +`updated` 修飾子は、特定の日付範囲内に最終更新されたウィキページにマッチします。 + +{% data reusables.search.date_gt_lt %} + +| 修飾子 | サンプル | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| updated:YYYY-MM-DD | [**usage updated:>2016-01-01**](https://github.com/search?q=usage+updated%3A>2016-01-01&type=Wikis) は、2016 年 1 月 1 日より後に最終更新された、「usage」という単語があるウィキページにマッチします。 | + +## 参考リンク + +- 「[検索結果をソートする](/search-github/getting-started-with-searching-on-github/sorting-search-results/)」 diff --git a/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md index d0723bf792..fcfdb5acea 100644 --- a/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md +++ b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md @@ -30,6 +30,7 @@ shortTitle: Manage payment tiers 1. 必要に応じて、ドラフト層を編集するには、ドラフト層を見つけて [**Edit**] をクリックします。 ![ドラフト層の横にある編集ボタン](/assets/images/help/sponsors/draft-tier-edit.png) {% data reusables.sponsors.click-add-tier %} {% data reusables.sponsors.tier-price-description %} +{% data reusables.sponsors.add-welcome-message %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} 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 0f422e1321..42ce83159b 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 @@ -51,6 +51,7 @@ Organization 外の個人コントリビューターとして {% data variables. {% data reusables.sponsors.navigate-to-sponsor-tiers-tab %} {% data reusables.sponsors.click-add-tier %} {% data reusables.sponsors.tier-price-description %} +{% data reusables.sponsors.add-welcome-message %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} {% data reusables.sponsors.add-more-tiers %} 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-user-account.md index da24837adb..7b75043dca 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-user-account.md @@ -50,6 +50,7 @@ Organization として {% data variables.product.prodname_sponsors %} に参加 {% data reusables.sponsors.navigate-to-sponsor-tiers-tab %} {% data reusables.sponsors.click-add-tier %} {% data reusables.sponsors.tier-price-description %} +{% data reusables.sponsors.add-welcome-message %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} {% data reusables.sponsors.add-more-tiers %} 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 2f78dee85f..f91216082b 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 @@ -37,6 +37,8 @@ The W-8 BEN and W-8 BEN-E tax forms ask for a "U.S. taxpayer identification numb If you are not a U.S. citizen or other U.S. person, including a resident alien individual, then you will usually need to provide the "Foreign tax identifying number". This is a tax identification number that your country of residence has issued you. +If your country of residence or billing country is India, then you can use your Permanent Account Number (PAN) as your tax identification number. + {% note %} **Note:** If your country does not require citizens to have a tax number issued by the government, then you can instead write "not legally required". @@ -56,6 +58,18 @@ If you are a taxpayer in the United States and earn more than 600 US dollars in {% data reusables.sponsors.sponsorships-not-tax-deductible %} +## Sales tax + +GitHub is providing information to assist you in calculating your sales tax obligations. This information is not personalized to your country or tax situation and we recommend you talk to a professional to understand your specific obligations. However, we'd like to provide some high-level information to help you understand the general principles of digital sales tax. + +In most countries around the world, sales tax for digital transactions is based on the location of the recipient, not on the seller. For example, if you are a maintainer in the United States and you provide a taxable benefit to a Sponsor in Germany, German sales tax would apply. + +Sales tax is generally only applicable when a good or service of value is being provided. Goodwill/general support/undying appreciation is not normally taxable. + +In the US, both B2B (business-to-business) and B2C (business-to-consumer) are subject to sales tax. + +In the EU and most other countries and regions, B2C sales are subject to sales tax. B2B sales are not subject to tax. C2C and C2B sales where a consumer is not registered for VAT are not taxable. + ## 参考リンク - [スポンサーとスポンサーシップを表示する](/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships) diff --git a/translations/ja-JP/data/glossaries/external.yml b/translations/ja-JP/data/glossaries/external.yml index a0b8ec952e..2dce1ec324 100644 --- a/translations/ja-JP/data/glossaries/external.yml +++ b/translations/ja-JP/data/glossaries/external.yml @@ -9,7 +9,7 @@ - term: アカウントリカバリトークン description: >- - Recover Accounts Elsewhere というアカウントリカバリセットアップの一部として格納される認証資格情報。このバックアップ資格情報を格納できるようにします。 + **Deprecated and will be disabled December 1st, 2021.** The authentication credential stored as part of an account recovery setup called Recover Accounts Elsewhere that allows you to store this backup credential. - term: APIプレビュー description: >- @@ -574,7 +574,7 @@ - term: Recovery Accounts Elsewhere description: >- - ユーザに対し、2 要素認証方法やリカバリコードへのアクセスを失った場合に備えて、自分の GitHub アカウントにセキュリティ要素をさらに追加することを許可するもの。ユーザは自分の GitHub アカウントの認証の資格情報をアカウントリカバリトークンの形で Facebook に格納すれば、GitHub アカウントを Facebook アカウントに関連付けることができます。 + **Deprecated and will be disabled December 1st, 2021.** Allows users to add an extra security factor to their GitHub account in case they lose access to their two-factor authentication method or recovery codes. Users can associate their GitHub account with their Facebook account by storing an authentication credential in the form of an account recovery token for their GitHub account with Facebook. - term: リカバリコード description: GitHub アカウントへのアクセスを再取得できるようにするコード。 @@ -654,9 +654,9 @@ description: >- 直近の 50 個のアクションまたは過去 90 日間に実行されたアクションを一覧表示するログ。 - - term: server-to-server request + term: server-to-serverリクエスト description: >- - An API request used by an application that acts as a bot, independently of any particular user. For example, an application that runs on a scheduled basis and closes issues where there has been no activity for a long time. Applications that use this type of authentication don't use a licensed GitHub account so, in an enterprise with a billing plan that allows a certain number of licenses to be used, a server-to-server bot is not consuming one of your GitHub licenses. The token used in a server-to-server request is acquired programmatically, via [the GitHub API](/rest/reference/apps#create-an-installation-access-token-for-an-app). See also, "[user-to-server request](#user-to-server-request)." + 特定のユーザとは関係なく、botとして振る舞うアプリケーションが使用するAPIリクエスト。たとえば、スケジュールに基づいて動作し、長期間にわたってアクティビティがないIssueをクローズするアプリケーション。この種の認証を利用するアプリケーションは、ライセンスされたGitHubのアカウントを使用しないので、特定数のライセンスの利用を許可する支払いプランを使っている企業では、サーバー対サーバーのボットはGitHubライセンスを消費しません。サーバーからサーバーへのリクエストで使われるトークンは、[GitHub API](/rest/reference/apps#create-an-installation-access-token-for-an-app)を使ってプログラムから取得できます。「[ユーザーからサーバーへのリクエスト](#user-to-server-request)」も参照してください。 - term: サービスフック description: >- @@ -684,7 +684,7 @@ description: >- コミットがコントリビューション先リポジトリに設定されている条件を満たしていることを、プルリクエスト内で視覚的に表現したもの。 - - term: status checks + term: ステータスチェック description: >- ステータスチェックは、継続的インテグレーションのビルドのような外部プロセスで、リポジトリにコミットを行うたびに実行されます。詳しい情報については「[ステータスチェックについて](/articles/about-status-checks)」を参照してください。 - @@ -718,7 +718,7 @@ description: >- GitHub で、特定の領域に関するリポジトリを調べたり、コントリビュートするプロジェクトを探したり、特定の問題に対する新たなソリューションを見つけ出したりするための方法。 - - term: traffic graph + term: トラフィックグラフ description: >- フルクローン（フェッチではない）、過去 14 日間の訪問者、参照サイト、人気コンテンツなど、リポジトリのトラフィックを表示するリポジトリグラフ。 - @@ -741,9 +741,9 @@ term: ユーザ名 description: GitHub 上でのユーザのハンドル。 - - term: user-to-server request + term: user-to-serverリクエスト description: >- - An API request used by an application that performs a task on behalf of a particular user. Where a task is carried out with user-to-server authentication it's shown on GitHub as having been done by a user via an application. For example, you might choose to create an issue from within a third-party application, and the application would do this on your behalf on GitHub. The scope of tasks an application can perform using a user-to-server request is restricted by both the app's and the user's permissions and access. The token used in a user-to-server request is acquired via OAuth. For more information, see "[Identifying and authorizing users for GitHub Apps](/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps)." See also, "[server-to-server request](#server-to-server-request)." + 特定のユーザの代わりにタスクを実行するアプリケーションが使用するAPIリクエスト。user-to-server認証で実行されたタスクは、GitHub上ではアプリケーションを使用してユーザが実行したとして表示されます。たとえば、サードパーティのアプリケーション内からIssueを作成することができ、そのアプリケーションはあなたの代わりにGitHub上でその処理を行ってくれるでしょう。user-to-serverリクエストを使ってアプリケーションが実行できるタスクのスコープは、アプリケーション及びユーザの権限及びアクセスの両方によって制限されます。user-to-serverリクエストによって使われるトークンは、OAuthによって取得されます。詳しい情報については「[GitHub Appsのユーザの特定と認可](/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps)」を参照してください。「[server-to-serverリクエスト](#server-to-server-request)」も参照してください。 - term: 参照可能なチーム description: Organization の各メンバーが表示および @メンションできる Team。 diff --git a/translations/ja-JP/data/glossaries/internal.yml b/translations/ja-JP/data/glossaries/internal.yml index 06a25e1da4..f3d1b6cc70 100644 --- a/translations/ja-JP/data/glossaries/internal.yml +++ b/translations/ja-JP/data/glossaries/internal.yml @@ -229,7 +229,7 @@ - term: GPG description: >- - GNU Privacy Guard. Encryption software that you can use to encrypt (and decrypt) files that contain sensitive data + GNU Privacy Guard。機密データを含むファイルを暗号化（および復号化）するのに使用できる暗号化ソフトウェア - term: GPGキー description: GPG で使用する暗号化キー。 diff --git a/translations/ja-JP/data/graphql/ghes-3.2/graphql_previews.enterprise.yml b/translations/ja-JP/data/graphql/ghes-3.2/graphql_previews.enterprise.yml index eaad85dca9..070b2b8ff9 100644 --- a/translations/ja-JP/data/graphql/ghes-3.2/graphql_previews.enterprise.yml +++ b/translations/ja-JP/data/graphql/ghes-3.2/graphql_previews.enterprise.yml @@ -29,7 +29,7 @@ - '@github/c2c-actions-service' - title: >- - >- MergeInfoPreview - More detailed information about a pull request's merge state. + >- MergeInfoPreview - Pull Requestのマージ状態に関する詳細な情報。 description: >- このプレビューは、プルリクエストのマージ状態に関する詳細な情報を提供するフィールドへのアクセスのサポートを追加します。 toggled_by: ':merge-info-preview' diff --git a/translations/ja-JP/data/learning-tracks/README.md b/translations/ja-JP/data/learning-tracks/README.md index ed19d9bde6..62f1fa93f7 100644 --- a/translations/ja-JP/data/learning-tracks/README.md +++ b/translations/ja-JP/data/learning-tracks/README.md @@ -29,7 +29,7 @@ ## バージョン管理 -学習トラックのバージョン付けは、ページのレンダリングの時点で処理されます。 コードは[`lib/learning-tracks.js`](lib/learning-tracks.js)にあり、これは`page.render()`によって呼ばれます。 The processed learning tracks are then rendered by `components/sublanding`. +学習トラックのバージョン付けは、ページのレンダリングの時点で処理されます。 コードは[`lib/learning-tracks.js`](lib/learning-tracks.js)にあり、これは`page.render()`によって呼ばれます。 そして処理された学習トラックは、`components/sublanding`によってレンダリングされます。 ガイドのためのYAMLファイルのバージョン付けでLiquid条件文を使う必要は**ありません**。 現在のバージョンに適用される学習トラックのガイドだけが自動的にレンダリングされます。 現在のバージョンに属するガイドを持つトラックがない場合、その学習トラックのセクションはまったくレンダリングされません。 diff --git a/translations/ja-JP/data/learning-tracks/actions.yml b/translations/ja-JP/data/learning-tracks/actions.yml index d287f9944f..bb1070ac47 100644 --- a/translations/ja-JP/data/learning-tracks/actions.yml +++ b/translations/ja-JP/data/learning-tracks/actions.yml @@ -7,6 +7,7 @@ getting_started: - /actions/learn-github-actions/finding-and-customizing-actions - /actions/learn-github-actions/essential-features-of-github-actions - /actions/learn-github-actions/managing-complex-workflows + - /actions/learn-github-actions/reusing-workflows - /actions/learn-github-actions/security-hardening-for-github-actions featured_track: true continuous_integration: diff --git a/translations/ja-JP/data/product-examples/README.md b/translations/ja-JP/data/product-examples/README.md index 7c5deb3672..376df32544 100644 --- a/translations/ja-JP/data/product-examples/README.md +++ b/translations/ja-JP/data/product-examples/README.md @@ -35,7 +35,7 @@ 製品のサンプルデータは、`middleware/contextualizers/product-examples.js`中の`context`オブジェクトに追加されます。 -The data is then rendered by `components/landing`. +そしてこのデータは、`components/landing`によってレンダリングされます。 ## スキーマの適用 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/2-20/15.yml b/translations/ja-JP/data/release-notes/enterprise-server/2-20/15.yml index aa3c664487..34bb0ff9b7 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/2-20/15.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/2-20/15.yml @@ -1,24 +1,25 @@ +--- date: '2020-08-26' sections: security_fixes: - >- - **CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2883, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700, - https://github.com/github/pages/pull/2890, https://github.com/github/pages/pull/2898, https://github.com/github/pages/pull/2909, https://github.com/github/pages/pull/2891, https://github.com/github/pages/pull/2884, https://github.com/github/pages/pull/2889 {% endcomment %} - - '**MEDIUM:** An improper access control vulnerability was identified that allowed authenticated users of the instance to determine the names of unauthorized private repositories given their numerical IDs. This vulnerability did not allow unauthorized access to any repository content besides the name. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.22 and has been assigned [CVE-2020-10517](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10517). The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/151987, https://github.com/github/github/pull/151713 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21852, https://github.com/github/enterprise2/pull/21828, https://github.com/github/enterprise2/pull/22153, https://github.com/github/enterprise2/pull/21920, https://github.com/github/enterprise2/pull/22215, https://github.com/github/enterprise2/pull/22190 {% endcomment %}' + **CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2883, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700, https://github.com/github/pages/pull/2890, https://github.com/github/pages/pull/2898, https://github.com/github/pages/pull/2909, https://github.com/github/pages/pull/2891, https://github.com/github/pages/pull/2884, https://github.com/github/pages/pull/2889 {% endcomment %} + - '**中:** インスタンスの認証されたユーザが、数値IDの分かっている認可されていないプライベートリポジトリの名前を決めることができてしまう、不適切なアクセス制御の脆弱性が特定されました。この脆弱性では、名前以外のリポジトリの内容への未認可のアクセスはできません。この脆弱性は2.22以前のGitHub Enterprise Serverのすべてのバージョンに影響するもので、[CVE-2020-10517](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10517)が割り当てられました。この脆弱性は[GitHub Bug Bountyプログラム](https://bounty.github.com)で報告されました。{% comment %} https://github.com/github/github/pull/151987, https://github.com/github/github/pull/151713 {% endcomment %}' + - 'パッケージが最新のセキュリティバージョンに更新されました。{% comment %} https://github.com/github/enterprise2/pull/21852, https://github.com/github/enterprise2/pull/21828, https://github.com/github/enterprise2/pull/22153, https://github.com/github/enterprise2/pull/21920, https://github.com/github/enterprise2/pull/22215, https://github.com/github/enterprise2/pull/22190 {% endcomment %}' bugs: - - 'A message was not logged when the ghe-config-apply process had finished running ghe-es-auto-expand. {% comment %} https://github.com/github/enterprise2/pull/22177, https://github.com/github/enterprise2/pull/22171 {% endcomment %}' - - 'Excessive logging to the `syslog` file could occur on high-availability replicas if the primary appliance is unavailable. {% comment %} https://github.com/github/enterprise2/pull/22267, https://github.com/github/enterprise2/pull/22124 {% endcomment %}' - - "Database re-seeding on a replica could fail with an error: `Got packet bigger than 'max_allowed_packet'` {% comment %} https://github.com/github/enterprise2/pull/22321, https://github.com/github/enterprise2/pull/20063 {% endcomment %}" - - 'In some cases duplicate user data could cause a 500 error while running the ghe-license-usage script. {% comment %} https://github.com/github/github/pull/152638 {% endcomment %}' + - 'ghe-config-applyプロセスがghe-es-auto-expandの実行を終了させた際に、メッセージが記録されませんでした。{% comment %} https://github.com/github/enterprise2/pull/22177, https://github.com/github/enterprise2/pull/22171 {% endcomment %}' + - 'High Availabilityレプリカで、プライマリアプライアンスが利用できない場合に、過剰なログが`syslog`ファイルに記録されました。{% comment %} https://github.com/github/enterprise2/pull/22267, https://github.com/github/enterprise2/pull/22124 {% endcomment %}' + - "レプリカ上でのデータベースの再シードが`Got packet bigger than 'max_allowed_packet'のエラーで失敗することがありました。{% comment %} https://github.com/github/enterprise2/pull/22321, https://github.com/github/enterprise2/pull/20063 {% endcomment %}" + - 'ghe-license-usageスクリプトを実行した際に、複製されたユーザデータが500エラーを引き起こすことがありました。{% comment %} https://github.com/github/github/pull/152638 {% endcomment %}' changes: - - 'In a high availability or geo-replication configuration, replica instances would exit maintenance mode when ghe-config-apply ran. {% comment %} https://github.com/github/enterprise2/pull/21776, https://github.com/github/enterprise2/pull/21440 {% endcomment %}' - - "We've added support for the R5a and R5n AWS instance types. {% comment %} https://github.com/github/enterprise2/pull/21902, https://github.com/github/enterprise2/pull/21173 {% endcomment %}" - - 'Removed the license seat count information on the administrative SSH MOTD due to a performance issue impacting GitHub Enterprise Server clusters. {% comment %} https://github.com/github/enterprise2/pull/21993, https://github.com/github/enterprise2/pull/21870 {% endcomment %}' + - 'High-availabilityもしくはGeo-replication構成で、ghe-config-applyが実行されるとレプリカインスタンスがメンテナンスモードから抜けてしまいます。{% comment %} https://github.com/github/enterprise2/pull/21776, https://github.com/github/enterprise2/pull/21440 {% endcomment %}' + - "AWSのインスタンスタイプとしてR5a及びR5nのサポートを追加しました。{% comment %} https://github.com/github/enterprise2/pull/21902, https://github.com/github/enterprise2/pull/21173 {% endcomment %}" + - 'GitHub Enterprise Serverクラスタに影響するパフォーマンスの問題により、管理のSSH MOTD上のライセンスシートカウント情報を削除しました。{% comment %} https://github.com/github/enterprise2/pull/21993, https://github.com/github/enterprise2/pull/21870 {% endcomment %}' known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - '新たにセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理者ユーザを作成できました。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'カスタムのファイアウォールルールがアップデートの際に維持されません。 {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'ファイルパスが255文字以上の場合、同じリポジトリ内のblobへのパーマリンクが含まれていると、Issueをクローズできません。 {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'GitHub Connectで"Users can search GitHub.com"が有効化されていると、プライベート及びインターナルリポジトリのIssueがGitHub.comの検索結果に含まれません。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'High Availability構成でレプリカノードがオフラインの場合でも、{% data variables.product.product_name %}が{% data variables.product.prodname_pages %}リクエストをオフラインのノードにルーティングし続ける場合があり、それによってユーザにとっての{% data variables.product.prodname_pages %}の可用性が下がってしまいます。' 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 f4d20d4066..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://enterprise.githubsupport.com/hc/en-us) 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/6.yml b/translations/ja-JP/data/release-notes/enterprise-server/2-21/6.yml index 03c71afb3a..7012852a75 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/2-21/6.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/2-21/6.yml @@ -1,27 +1,28 @@ +--- date: '2020-08-26' sections: security_fixes: - >- - **CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2882, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700, - https://github.com/github/pages/pull/2889, https://github.com/github/pages/pull/2899, https://github.com/github/pages/pull/2903, https://github.com/github/pages/pull/2890, https://github.com/github/pages/pull/2891, https://github.com/github/pages/pull/2884 {% endcomment %} - - '**MEDIUM:** An improper access control vulnerability was identified that allowed authenticated users of the instance to determine the names of unauthorized private repositories given their numerical IDs. This vulnerability did not allow unauthorized access to any repository content besides the name. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.22 and has been assigned [CVE-2020-10517](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10517). The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/151986, https://github.com/github/github/pull/151713 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21853, https://github.com/github/enterprise2/pull/21828, https://github.com/github/enterprise2/pull/22154, https://github.com/github/enterprise2/pull/21920, https://github.com/github/enterprise2/pull/22216, https://github.com/github/enterprise2/pull/22190 {% endcomment %}' + **CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2882, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700, https://github.com/github/pages/pull/2889, https://github.com/github/pages/pull/2899, https://github.com/github/pages/pull/2903, https://github.com/github/pages/pull/2890, https://github.com/github/pages/pull/2891, https://github.com/github/pages/pull/2884 {% endcomment %} + - '**中:** インスタンスの認証されたユーザが、数値IDの分かっている認可されていないプライベートリポジトリの名前を決めることができてしまう、不適切なアクセス制御の脆弱性が特定されました。この脆弱性では、名前以外のリポジトリの内容への未認可のアクセスはできません。この脆弱性は2.22以前のGitHub Enterprise Serverのすべてのバージョンに影響するもので、[CVE-2020-10517](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10517)が割り当てられました。この脆弱性は[GitHub Bug Bountyプログラム](https://bounty.github.com)で報告されました。{% comment %} https://github.com/github/github/pull/151986, https://github.com/github/github/pull/151713 {% endcomment %}' + - 'パッケージが最新のセキュリティバージョンに更新されました。{% comment %} https://github.com/github/enterprise2/pull/21853, https://github.com/github/enterprise2/pull/21828, https://github.com/github/enterprise2/pull/22154, https://github.com/github/enterprise2/pull/21920, https://github.com/github/enterprise2/pull/22216, https://github.com/github/enterprise2/pull/22190 {% endcomment %}' bugs: - - 'A message was not logged when the ghe-config-apply process had finished running ghe-es-auto-expand. {% comment %} https://github.com/github/enterprise2/pull/22178, https://github.com/github/enterprise2/pull/22171 {% endcomment %}' - - 'Excessive logging to the `syslog` file could occur on high-availability replicas if the primary appliance is unavailable. {% comment %} https://github.com/github/enterprise2/pull/22268, https://github.com/github/enterprise2/pull/22124 {% endcomment %}' - - "Database re-seeding on a replica could fail with an error: `Got packet bigger than 'max_allowed_packet'` {% comment %} https://github.com/github/enterprise2/pull/22322, https://github.com/github/enterprise2/pull/20063 {% endcomment %}" - - 'In some cases duplicate user data could cause a 500 error while running the ghe-license-usage script. {% comment %} https://github.com/github/github/pull/152637 {% endcomment %}' - - 'Using `ghe-migrator`, the `add` command would fail to lock a repository when using the `--lock` flag. {% comment %} https://github.com/github/github/pull/152780, https://github.com/github/github/pull/152588 {% endcomment %}' + - 'ghe-config-applyプロセスがghe-es-auto-expandの実行を終了させた際に、メッセージが記録されませんでした。{% comment %} https://github.com/github/enterprise2/pull/22178, https://github.com/github/enterprise2/pull/22171 {% endcomment %}' + - 'High Availabilityレプリカで、プライマリアプライアンスが利用できない場合に、過剰なログが`syslog`ファイルに記録されました。{% comment %} https://github.com/github/enterprise2/pull/22268, https://github.com/github/enterprise2/pull/22124 {% endcomment %}' + - "レプリカ上でのデータベースの再シードが`Got packet bigger than 'max_allowed_packet'のエラーで失敗することがありました。{% comment %} https://github.com/github/enterprise2/pull/22322, https://github.com/github/enterprise2/pull/20063 {% endcomment %}" + - 'ghe-license-usageスクリプトを実行した際に、複製されたユーザデータが500エラーを引き起こすことがありました。{% comment %} https://github.com/github/github/pull/152637 {% endcomment %}' + - '`ghe-migrator`を使い、`add`コマンド`で--lock`フラグを利用してリポジトリをロックするのに失敗します。{% comment %} https://github.com/github/github/pull/152780, https://github.com/github/github/pull/152588 {% endcomment %}' changes: - - 'In a high availability or geo-replication configuration, replica instances would exit maintenance mode when ghe-config-apply ran. {% comment %} https://github.com/github/enterprise2/pull/21777, https://github.com/github/enterprise2/pull/21440 {% endcomment %}' - - "We've added support for the R5a and R5n AWS instance types. {% comment %} https://github.com/github/enterprise2/pull/21903, https://github.com/github/enterprise2/pull/21173 {% endcomment %}" - - 'Removed the license seat count information on the administrative SSH MOTD due to a performance issue impacting GitHub Enterprise Server clusters. {% comment %} https://github.com/github/enterprise2/pull/21994, https://github.com/github/enterprise2/pull/21870 {% endcomment %}' + - 'High-availabilityもしくはGeo-replication構成で、ghe-config-applyが実行されるとレプリカインスタンスがメンテナンスモードから抜けてしまいます。{% comment %} https://github.com/github/enterprise2/pull/21777, https://github.com/github/enterprise2/pull/21440 {% endcomment %}' + - "AWSのインスタンスタイプとしてR5a及びR5nのサポートを追加しました。{% comment %} https://github.com/github/enterprise2/pull/21903, https://github.com/github/enterprise2/pull/21173 {% endcomment %}" + - 'GitHub Enterprise Serverクラスタに影響するパフォーマンスの問題により、管理のSSH MOTD上のライセンスシートカウント情報を削除しました。{% comment %} https://github.com/github/enterprise2/pull/21994, https://github.com/github/enterprise2/pull/21870 {% endcomment %}' known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - "Configuring a repository's permission to `Triage` or `Maintain` fails with an error message." + - '新たにセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理者ユーザを作成できました。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'カスタムのファイアウォールルールがアップデートの際に維持されません。 {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'ファイルパスが255文字以上の場合、同じリポジトリ内のblobへのパーマリンクが含まれていると、Issueをクローズできません。 {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'GitHub Connectで"Users can search GitHub.com"が有効化されていると、プライベート及びインターナルリポジトリのIssueがGitHub.comの検索結果に含まれません。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'コマンドラインでリポジトリにプッシュした際に、セキュリティアラートが報告されません。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - '監査ログが実際のソースIDアドレスではなく、127.0.0.1に起因するものとされることがあります。（2020-11-02更新）{% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' + - "リポジトリの権限を`Triage`もしくは`Maintain`に設定しようとすると、失敗してエラーメッセージが表示されます。" + - 'High Availability構成でレプリカノードがオフラインの場合でも、{% data variables.product.product_name %}が{% data variables.product.prodname_pages %}リクエストをオフラインのノードにルーティングし続ける場合があり、それによってユーザにとっての{% data variables.product.prodname_pages %}の可用性が下がってしまいます。' diff --git a/translations/ja-JP/data/release-notes/enterprise-server/2-22/17.yml b/translations/ja-JP/data/release-notes/enterprise-server/2-22/17.yml index bada0fbe5d..2478c3df49 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/2-22/17.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/2-22/17.yml @@ -2,16 +2,16 @@ date: '2021-07-14' sections: security_fixes: - - '**HIGH:** A path traversal vulnerability was identified in GitHub Enterprise Server that could be exploited when building a GitHub Pages site. User-controlled configuration options used by GitHub Pages were not sufficiently restricted and made it possible to read files on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.1.3 and has been assigned CVE-2021-22867. This vulnerability was reported via the GitHub Bug Bounty program.' + - '**高:** GitHubPagesのサイトをビルドする際に利用される可能性があるパストラバーサルの脆弱性が、GitHub Enterprise Serverで特定されました。GitHub Pagesが使用するユーザが制御する設定オプションが十分に厳密ではなく、GitHub Enterprise Serverインスタンス上のファイルを読めてしまいます。この脆弱性を利用するには、攻撃者はGitHub Enterprise Serverインスタンス上でGitHub Pagesのサイトを作成してビルドする権限を持っていなければなりません。この脆弱性は3.1.3以前のすべてのバージョンのGitHub Enterprise Serverに影響し、CVE-2021-22867が割り当てられました。この脆弱性はGitHub Bug Bountyプログラムを通じて報告されました。' - パッケージは最新のセキュリティバージョンにアップデートされました。 bugs: - - '`ghe-cluster-config-node-init` would fail during cluster setup if HTTP proxy is enabled.' - - Collectd would not resolve the forwarding destination hostname after the initial startup. - - The job that purged stale deleted repositories could fail to make progress if some of those repositories were protected from deletion by legal holds. - - Git pushes could result in a 500 Internal Server Error during the user reconciliation process on instances using LDAP authentication mode. - - A significant number of 503 errors were logged every time a user visited a repository's `/settings` page if the dependency graph was not enabled. + - '`ghe-cluster-config-node-init`は、HTTPプロキシが有効化されているとクラスタのセットアップの間に失敗します。' + - collectdは、初期のセットアップ後にフォワード先のホスト名を解決しません。 + - 古い柵得除されたリポジトリをパージするジョブは、それらのリポジトリの中に訴訟ホールドによって削除から保護されているものがある場合、処理を進められないことがあります。 + - LDAP認証モードを使うインスタンスにおいて、Git pushがユーザ照合プロセス中に500 Internal Server Errorになることがあります。 + - 依存関係グラフが有効化されていない場合、ユーザがリポジトリの`/settings`ページにアクセスするたびに大量の503エラーが記録されました。 changes: - - Improved the efficiency of config apply by skipping IP allow firewall rules that had not changed, which saved significant time on large clusters. + - 変更されなかったIP許可ファイアウォールルールをスキップすることによって、設定適用の効率性が改善されました。これは大規模なクラスタでは大きな時間の節約になります。 known_issues: - 新しくセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理ユーザを作成できました。 - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/2-22/18.yml b/translations/ja-JP/data/release-notes/enterprise-server/2-22/18.yml index 7c5937e8f5..cb9efa6b61 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/2-22/18.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/2-22/18.yml @@ -4,10 +4,10 @@ sections: security_fixes: - パッケージは最新のセキュリティバージョンにアップデートされました。 bugs: - - A significant number of 503 errors were being created if the scheduled job to sync vulnerabilities with GitHub.com attempted to run when dependency graph was not enabled and content analysis was enabled. - - Unauthenticated HTTP proxy for the pages containers build was not supported for any users that use HTTP proxies. + - 依存関係グラフが有効化されておらず、コンテンツ分析が有効化されている状態で、スケジュールジョブがGitHub.comと脆弱性を同期しようとすると、大量の503エラーが発生しました。 + - HTTPプロキシを使用するユーザでは、Pagesのコンテナビルドの認証されていないHTTPプロキシはサポートされていませんでした。 changes: - - The logs for `babeld` now include a `cmd` field for HTTP ref advertisement requests instead of only including it during the negotiation requests. + - '`babeld`のログには、ネゴシエーションリクエストの際だけではなく、HTTP参照広告リクエストの`cmd`フィールドが含まれるようになりました。' known_issues: - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}で、攻撃者が最初の管理ユーザを作成できました。 - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/2-22/19.yml b/translations/ja-JP/data/release-notes/enterprise-server/2-22/19.yml index 9f3a28f7e2..9bb00d5718 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/2-22/19.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/2-22/19.yml @@ -2,9 +2,9 @@ date: '2021-08-10' sections: bugs: - - Audit log entries for changes made to "Repository creation" organization settings were inaccurate. + - '"Repository creation" Organizationの設定に対する変更の監査ログエントリが不正確でした。' changes: - - Abuse rate limits are now called Secondary rate limits, since the behavior they limit is not always abusive. + - 不正利用レート制限は、セカンダリレート制限と呼ばれるようになりました。これは、これによって制限されるのが必ずしも不正利用とは限らないためです。 known_issues: - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}で、攻撃者が最初の管理ユーザを作成できました。 - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/2-22/20.yml b/translations/ja-JP/data/release-notes/enterprise-server/2-22/20.yml index 287b128d0f..6e0e7f9a73 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/2-22/20.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/2-22/20.yml @@ -4,8 +4,8 @@ sections: security_fixes: - パッケージは最新のセキュリティバージョンにアップデートされました。 bugs: - - Journald messages related to automatic updates (`Adding h/m/s random time.`) were logged to syslog. - - Git hooks to the internal API that result in failing requests returned the exception `undefined method body for "success":String (NoMethodError)` instead of returning an explicit `nil`. + - 自動アップデートに関係するJournaldのメッセージ (`Adding h/m/s random time.`)が、syslogに記録されました。 + - リクエストに失敗する内部APIへのGitフックが、明示的な`nil`を返す代わりに`undefined method body for "success":String (NoMethodError)`という例外を返しました。 known_issues: - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}で、攻撃者が最初の管理ユーザを作成できました。 - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/2-22/22.yml b/translations/ja-JP/data/release-notes/enterprise-server/2-22/22.yml new file mode 100644 index 0000000000..ee8c2f9c35 --- /dev/null +++ b/translations/ja-JP/data/release-notes/enterprise-server/2-22/22.yml @@ -0,0 +1,15 @@ +--- +date: '2021-09-24' +sections: + security_fixes: + - '**高:** {% data variables.product.prodname_pages %}のサイトをビルドする際に利用される可能性があるパストラバーサルの脆弱性が、{% data variables.product.prodname_ghe_server %}で特定されました。{% data variables.product.prodname_pages %}が使用する、ユーザが制御する設定が十分に厳密ではなく、{% data variables.product.prodname_ghe_server %}インスタンス上でファイルを読めてしまいます。この脆弱性を利用するには、攻撃者は{% data variables.product.prodname_ghe_server %}インスタンス上で{% data variables.product.prodname_pages %}のサイトを作成してビルドする権限を持っていなければなりません。この脆弱性は3.1.8以前のすべての{% data variables.product.prodname_ghe_server %}のバージョンに影響し、3.1.8、3.0.16、2.22.22で修正されました。これは、CVE-2021-22867に対する不完全な修正の結果です。この脆弱性はGitHub Bug Bounty Programを通じて報告され、CVE-2020-22868が割り当てられました。{% comment %} https://github.com/github/pages/pull/3359, https://github.com/github/pages/pull/3357 {% endcomment %}' + bugs: + - 'ソースインスタンスの{% data variables.product.prodname_github_connect %}設定が、`ghe-restore`の`--config`オプションが使われていない場合でも、常に新しいインスタンスにリストアされました。これによって、ソース及び宛先のインスタンスがともにオンラインになっている場合に、{% data variables.product.prodname_github_connect %}の接続とライセンス同期で衝突が起きることになります。{% comment %} https://github.com/github/github/pull/192247, https://github.com/github/github/pull/191951, https://github.com/github/enterprise2/pull/26870, https://github.com/github/backup-utils/pull/770, https://github.com/github/connected-enterprise/issues/208 {% endcomment %}' + - '{% data variables.product.prodname_pages %}ビルドが修正され、アプライアンスのNO_PROXY設定を考慮に入れるようになりました。これが関係するのは、HTTPプロキシと設定されたアプライアンスのみです。{% comment %} https://github.com/github/github/pull/192380 {% endcomment %}' + known_issues: + - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}で、攻撃者が最初の管理ユーザを作成できました。 + - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。 + - Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。 + - 同じリポジトリ内のファイルパスが255文字を超えるblobへのパーマリンクを含むIssueをクローズできませんでした。 + - '"Users can search GitHub.com" が{% data variables.product.prodname_github_connect %}と合わせて有効化されている場合、プライベート及びインターナルリポジトリのIssueがGitHub.comの検索結果に含まれません。' + - High Availability構成でレプリカノードがオフラインの場合でも、{% data variables.product.product_name %}が{% data variables.product.prodname_pages %}リクエストをオフラインのノードにルーティングし続ける場合があり、それによってユーザにとっての{% data variables.product.prodname_pages %}の可用性が下がってしまいます。 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 5ecb522384..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://enterprise.githubsupport.com/hc/en-us) 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/0-rc1.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-0/0-rc1.yml index 400aaee052..5cc21d99c5 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-0/0-rc1.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-0/0-rc1.yml @@ -19,7 +19,7 @@ sections: - Backup-utilsが、不要なメールを管理者に送信することがあります。 - Organizationのメンバービューページに、正しくないPackagesの設定が表示されます - Enterpriseのオーナーとして自分自身を削除すると、404ページにリダイレクトされます。処理は成功します。 - - '`ghe-config-apply` occasionally fails with `ERROR: Failure waiting for nomad jobs to apply` until the Nomad job queue is cleared. This currently requires as admin to delete `/etc/nomad-jobs/queue`.' + - '`ghe-config-apply`は、Nomadのジョブキューがクリアされるまでの間、`ERROR: Failure waiting for nomad jobs to apply`で失敗することがあります。現時点では、ジョブキューをクリアするには管理者として`/etc/nomad-jobs/queue`を削除しなければなりません。' - 複数のレプリカノードを設定する際に、レプリカのステータスが不正確に同期されることがあります。 - 新しいインスタンスに3.0のバックアップをリストアしようとするお客様は、ユーザのログインの状態が悪くなることがあるため、そのインスタンスを事前設定しておくべきではありません。新しい、未設定のインスタンスにリストアすることをおすすめします。 - GitHub Enterprise Server 3.0のリリース候補版は、まだAzure Marketplaceで入手できません。リリース候補版をステージング環境でテストするには、2.21もしくは2.22のインスタンスを立ち上げ、それをダウンロードページ上のAzureアップグレードパッケージでアップグレードしてください。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-0/0.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-0/0.yml index 23972f5e0b..b46f1407e5 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-0/0.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-0/0.yml @@ -64,7 +64,7 @@ sections: - webhookイベントの配信システムは、スループットの向上、配信の高速化、遅延メッセージの減少のために再設計されました。{% data variables.product.prodname_ghe_server %} 3.0以降では、CPUとメモリの使用量も減少しています。 - OrganizationとEnterpriseのオーナーは、TeamのメンバーがTeamのメンテナに昇格したり、メンテナから降格されたときに、新しい`team.promote_maintainer`及び`team.demote_maintainer`監査ログイベントを通じて監査ログで知ることができるようになりました。詳しい情報については「[監査対象のアクション](/enterprise-server@3.0/admin/user-management/audited-actions)」を参照してください。 - '既存の{% data variables.product.prodname_pages %}サイトを持つリポジトリ管理者は、[以前のデフォルトブランチ名を容易に更新](/enterprise-server@3.0/github/working-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites)できるようになりました。' - - Additional hardware resources are required to run {% data variables.product.prodname_ghe_server %} with any of Actions, Packages or Advanced Security enabled. For more information on the minimum required resources for each supported platform, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise-server@3.0/admin/installation/setting-up-a-github-enterprise-server-instance)." + - Actions、Packages、Advanced Securityのいずれかを有効にして{% data variables.product.prodname_ghe_server %}を動作させるには、追加のハードウェアリソースが必要です。それぞれのサポートされているプラットフォームで必要な最小限のリソースに関する情報については、「[{% data variables.product.prodname_ghe_server %}インスタンスのセットアップ](/enterprise-server@3.0/admin/installation/setting-up-a-github-enterprise-server-instance)」を参照してください。 - 管理者は、すべてのユーザが受諾しなければならない[メッセージを公開](/enterprise-server@3.0/admin/user-management/customizing-user-messages-for-your-enterprise)できるようになりました。これは、新しいユーザの参加と、Organization固有の情報やポリシーを示すための役に立ちます。 - heading: セキュリティの変更 @@ -136,7 +136,7 @@ sections: - Pagesの古いビルドがクリーンアップされず、ユーザディスク(`/data/user/`)を使い切ってしまうことがあります。 - Pull Requestをマージした後にブランチを削除すると、ブランチの削除は成功しているにもかかわらずエラーメッセージが表示されます。 - High Availability構成でレプリカノードがオフラインの場合でも、{% data variables.product.product_name %}が{% data variables.product.prodname_pages %}リクエストをオフラインのノードにルーティングし続ける場合があり、それによってユーザにとっての{% data variables.product.prodname_pages %}の可用性が下がってしまいます。 - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. + - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 deprecations: - heading: GitHub Enterprise Server 2.19の非推奨化 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 6f0ceac7cd..74076415e9 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://enterprise.githubsupport.com/hc/en-us).' + - 'メンテナンスモードが有効化されているとき、サービスの中に引き続き"active processes"としてリストされるものがあります。特定されたサービスは、メンテナンスモード中にも実行されることが期待されるものです。この問題が生じており、不確実な場合は[GitHub Enterprise Support](https://enterprise.githubsupport.com/hc/en-us)にお問い合わせください。' - '`/var/log/messages`、`/var/log/syslog`、`/var/log/user.log`への重複したロギングによって、ルートボリュームの使用率が増大します。' - 'ユーザが、すべてのチェックボックスをチェックすることなく必須のメッセージを閉じることができます。' - '[pre-receiveフックスクリプト](/admin/policies/enforcing-policy-with-pre-receive-hooks)は一時ファイルを書くことができず、そのためにスクリプトの実行が失敗することがあります。pre-receiveフックを使うユーザは、ステージング環境でスクリプトが書き込みアクセス権を必要とするかを確認するためのテストをするべきです。' @@ -69,4 +69,4 @@ sections: 2. 1つ以上のノードが影響されていると表示されたら、影響されているノードを再起動してください。 - 'High Availability構成でレプリカノードがオフラインの場合でも、{% data variables.product.product_name %}が{% data variables.product.prodname_pages %}リクエストをオフラインのノードにルーティングし続ける場合があり、それによってユーザにとっての{% data variables.product.prodname_pages %}の可用性が下がってしまいます。' - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. + - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-0/10.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-0/10.yml index f412a8e83a..1339abefb8 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-0/10.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-0/10.yml @@ -17,4 +17,4 @@ sections: - 同じリポジトリ内のファイルパスが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 %}の可用性が下がってしまいます。 - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. + - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-0/11.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-0/11.yml index 82409c6b08..b5272674e6 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-0/11.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-0/11.yml @@ -2,21 +2,21 @@ date: '2021-07-14' sections: security_fixes: - - '**HIGH:** A path traversal vulnerability was identified in GitHub Enterprise Server that could be exploited when building a GitHub Pages site. User-controlled configuration options used by GitHub Pages were not sufficiently restricted and made it possible to read files on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.1.3 and has been assigned CVE-2021-22867. This vulnerability was reported via the GitHub Bug Bounty program.' + - '**高:** GitHubPagesのサイトをビルドする際に利用される可能性があるパストラバーサルの脆弱性が、GitHub Enterprise Serverで特定されました。GitHub Pagesが使用するユーザが制御する設定オプションが十分に厳密ではなく、GitHub Enterprise Serverインスタンス上のファイルを読めてしまいます。この脆弱性を利用するには、攻撃者はGitHub Enterprise Serverインスタンス上でGitHub Pagesのサイトを作成してビルドする権限を持っていなければなりません。この脆弱性は3.1.3以前のすべてのバージョンのGitHub Enterprise Serverに影響し、CVE-2021-22867が割り当てられました。この脆弱性はGitHub Bug Bountyプログラムを通じて報告されました。' - パッケージは最新のセキュリティバージョンにアップデートされました。 bugs: - - SAML expiration date variable was not configurable. - - Application services would fail their health checks during config apply before they could enter a healthy state. - - '`ghe-cluster-config-node-init` would fail during cluster setup if HTTP proxy is enabled.' - - Pre-receive hooks could encounter an error `Failed to resolve full path of the current executable` due to `/proc` not being mounted on the container. - - Collectd would not resolve the forwarding destination hostname after the initial startup. - - The job that purged stale deleted repositories could fail to make progress if some of those repositories were protected from deletion by legal holds. - - Running `git nw-gc --pristine` would result in an error. - - Background jobs were being queued to the `spam` queue which were not being processed. - - The preferred merge method would be reset when retrying after a failed PR merge. - - Git pushes could result in a 500 Internal Server Error during the user reconciliation process on instances using LDAP authentication mode. + - SAMLの期限切れの日付変数は設定できませんでした。 + - アプリケーションサービスは、設定の適用の間に健全な状態に入る前、ヘルスチェックに失敗します。 + - '`ghe-cluster-config-node-init`は、HTTPプロキシが有効化されているとクラスタのセットアップの間に失敗します。' + - pre-receive フックで、`/proc`がコンテナにマウントされていないために`Failed to resolve full path of the current executable`という失敗が生じることがあります。 + - collectdは、初期のセットアップ後にフォワード先のホスト名を解決しません。 + - 古い柵得除されたリポジトリをパージするジョブは、それらのリポジトリの中に訴訟ホールドによって削除から保護されているものがある場合、処理を進められないことがあります。 + - '`git nw-gc --pristine`を実行すると、エラーになります。' + - バックグラウンドジョブが、処理されていない`spam`キューにキューイングされました。 + - 失敗したPRマージ後にリトライする際に、優先されるマージ方法がリセットされます。 + - LDAP認証モードを使うインスタンスにおいて、Git pushがユーザ照合プロセス中に500 Internal Server Errorになることがあります。 changes: - - Improved the efficiency of config apply by skipping IP allow firewall rules that had not changed, which saved significant time on large clusters. + - 変更されなかったIP許可ファイアウォールルールをスキップすることによって、設定適用の効率性が改善されました。これは大規模なクラスタでは大きな時間の節約になります。 known_issues: - 新しくセットアップされたユーザを持たないGitHub Enterprise Serverで、攻撃者が最初の管理ユーザを作成できました。 - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。 @@ -24,4 +24,4 @@ sections: - 同じリポジトリ内のファイルパスが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 %}の可用性が下がってしまいます。 - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. + - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-0/12.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-0/12.yml index 28f09ed074..4c844e125c 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-0/12.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-0/12.yml @@ -4,14 +4,14 @@ sections: security_fixes: - パッケージは最新のセキュリティバージョンにアップデートされました。 bugs: - - 'Custom pre-receive hooks could lead to an error like `error: object directory /data/user/repositories/0/nw/12/34/56/7890/network.git/objects does not exist; check .git/objects/info/alternates`.' - - Unauthenticated HTTP proxy for the pages containers build was not supported for any users that use HTTP proxies. - - A significant number of 503 errors were logged every time a user visited a repository''s `/settings` page if the dependency graph was not enabled. - - Internal repositories were only returned when a user had affiliations with the repository through a team or through collaborator status, or queried with the `?type=internal` parameter. - - Failed background jobs had unlimited retries which could cause large queue depths. - - A significant number of 503 errors were being created if the scheduled job to sync vulnerabilities with GitHub.com attempted to run when dependency graph was not enabled and content analysis was enabled. + - 'カスタムのpre-receive フックで`error: object directory /data/user/repositories/0/nw/12/34/56/7890/network.git/objects does not exist; check .git/objects/info/alternates`のようなエラーが生じることがあります。' + - HTTPプロキシを使用するユーザでは、Pagesのコンテナビルドの認証されていないHTTPプロキシはサポートされていませんでした。 + - 依存関係グラフが有効化されていない場合、ユーザがリポジトリの`/settings`ページにアクセスするたびに大量の503エラーが記録されました。 + - インターナルリポジトリは、ユーザがそのリポジトリにTeamを通じて、あるいはコラボレータのステータスを通じて関係があるか、`?type=internal`パラメータ付きでクエリされた場合にのみ返されました。 + - 失敗したバックグラウンドジョブが無制限のリトライを行い、大きなキューの深さを生じさせることがありました。 + - 依存関係グラフが有効化されておらず、コンテンツ分析が有効化されている状態で、スケジュールジョブがGitHub.comと脆弱性を同期しようとすると、大量の503エラーが発生しました。 changes: - - The logs for `babeld` now include a `cmd` field for HTTP ref advertisement requests instead of only including it during the negotiation requests. + - '`babeld`のログには、ネゴシエーションリクエストの際だけではなく、HTTP参照広告リクエストの`cmd`フィールドが含まれるようになりました。' known_issues: - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}で、攻撃者が最初の管理ユーザを作成できました。 - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。 @@ -19,4 +19,4 @@ sections: - 同じリポジトリ内のファイルパスが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 %}の可用性が下がってしまいます。 - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. + - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-0/13.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-0/13.yml index 3224af0734..910ce9fa2f 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-0/13.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-0/13.yml @@ -2,12 +2,12 @@ date: '2021-08-10' sections: bugs: - - When GitHub Actions is enabled without running regular scheduled backups the MSSQL Transaction Log could grow unbounded and can consume all available space on the appliance's Data Disk causing a possible outage. - - Audit log entries for changes made to "Repository creation" organization settings were inaccurate. - - Excessive logging of `ActionController::UnknownFormat` exceptions caused unnecessary disk usage. - - "LDAP `group_dn` values longer than 255 characters would result in errors being logged: `Data truncated for column 'group_dn' at row 1`." + - 定期的なMSSQLのトランザクションログのスケジュールバックアップを実行することなくGitHub Actionsを有効化すると、ログが無制限に拡大し、アプライアンスのデータディスクの利用可能な領域をすべて消費し、障害につながる可能性があります。 + - '"Repository creation" Organizationの設定に対する変更の監査ログエントリが不正確でした。' + - '`ActionController::UnknownFormat`例外の過剰なロギングが、不要なディスク消費を招いていました。' + - "255文字以上のLDAP `group_dn`値によって、`Data truncated for column 'group_dn' at row 1`というエラーが記録されます。" changes: - - Abuse rate limits are now called Secondary rate limits, since the behavior they limit is not always abusive. + - 不正利用レート制限は、セカンダリレート制限と呼ばれるようになりました。これは、これによって制限されるのが必ずしも不正利用とは限らないためです。 known_issues: - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}で、攻撃者が最初の管理ユーザを作成できました。 - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。 @@ -15,4 +15,4 @@ sections: - 同じリポジトリ内のファイルパスが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 %}の可用性が下がってしまいます。 - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. + - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-0/14.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-0/14.yml index bf933f13ec..2859c247fa 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-0/14.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-0/14.yml @@ -4,14 +4,14 @@ sections: security_fixes: - パッケージは最新のセキュリティバージョンにアップデートされました。 bugs: - - Attaching very large images or animated GIFs to images or pull requests would fail. - - Journald messages related to automatic updates (`Adding h/m/s random time.`) were logged to syslog. - - 'Custom pre-receive hooks that used a bash subshell would return an error: `No such file or directory`.' - - Custom pre-receive hooks that created named pipes (FIFOs) would crash or hang, resulting in a timeout error. - - Adding filters to the audit log advanced search page did not populate the query text box in real-time with the correct facet prefix and value. - - Git hooks to the internal API that result in failing requests returned the exception `undefined method body for "success":String (NoMethodError)` instead of returning an explicit `nil`. - - When an integration was removed, it was possible for an unrelated OAuth application or integration to also be removed. - - When a mandatory message containing an emoji character was added, attempting to view or change the message would return a 500 Internal Server Error. + - 画像あるいはPull Requestに非常に大きな画像もしくはアニメーションGIFを添付すると失敗します。 + - 自動アップデートに関係するJournaldのメッセージ (`Adding h/m/s random time.`)が、syslogに記録されました。 + - 'bashのサブシェルを使うカスタムのpre-receive フックは、`No such file or directory`というエラーを返します。' + - 名前付きパイプ（FIFO）を作成したカスタムのpre-receive フックは、クラッシュもしくはハングし、タイムアウトエラーを生じさせます。 + - 監査ログの高度な検索ページにフィルタを追加しても、適切なファセットプレフィックスと値付きでクエリテキストボックスがリアルタイムで展開されませんでした。 + - リクエストに失敗する内部APIへのGitフックが、明示的な`nil`を返す代わりに`undefined method body for "success":String (NoMethodError)`という例外を返しました。 + - インテグレーションが削除されると、関係の無いOAuthアプリケーションあるいはインテグレーションも削除されてしまう可能性がありました。 + - 絵文字を含む必須のメッセージが追加された場合、そのメッセージを表示あるいは変更しようとすると500 Internal Server Errorが返されます。 known_issues: - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}で、攻撃者が最初の管理ユーザを作成できました。 - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。 @@ -19,4 +19,4 @@ sections: - 同じリポジトリ内のファイルパスが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 %}の可用性が下がってしまいます。 - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. + - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-0/15.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-0/15.yml index 09d63f13a0..411c4090c1 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-0/15.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-0/15.yml @@ -4,10 +4,10 @@ sections: security_fixes: - パッケージは最新のセキュリティバージョンにアップデートされました。 bugs: - - Attempting to tear down a newly-added replica node by specifying its UUID with `ghe-repl-teardown` would fail without reporting an error if replication was not started. - - GitHub Pages builds were being passed through an external proxy if there was one configured. - - Custom pre-receive hooks that created sub-processes would lack a `PATH` variable in their environment, resulting in "No such file or directory" errors. - - MySQL could failover during an upgrade if `mysql-auto-failover` was enabled. + - '`ghe-repl-teardown`でUUIDを指定して、新たに追加されたレプリカノードを破棄しようとすると、レプリケーションが開始されていなかった場合にエラーを報告することなく失敗します。' + - 外部プロキシが設定されている場合、GitHub Pagesのビルドがそれを通じて渡されていました。 + - サブプロセスを生成したカスタムのpre-receive フックの環境に`PATH`変数が欠如し、"No such file or directory"エラーが生じます。 + - '`mysql-auto-failover`が有効化されていると、MySQLがアップグレードの際にフェイルオーバーすることがあります。' known_issues: - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}で、攻撃者が最初の管理ユーザを作成できました。 - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。 @@ -15,4 +15,4 @@ sections: - 同じリポジトリ内のファイルパスが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 %}の可用性が下がってしまいます。 - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. + - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-0/16.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-0/16.yml new file mode 100644 index 0000000000..ed8ea0c7e5 --- /dev/null +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-0/16.yml @@ -0,0 +1,18 @@ +--- +date: '2021-09-24' +sections: + security_fixes: + - '**高:** {% data variables.product.prodname_pages %}のサイトをビルドする際に利用される可能性があるパストラバーサルの脆弱性が、{% data variables.product.prodname_ghe_server %}で特定されました。{% data variables.product.prodname_pages %}が使用する、ユーザが制御する設定が十分に厳密ではなく、{% data variables.product.prodname_ghe_server %}インスタンス上でファイルを読めてしまいます。この脆弱性を利用するには、攻撃者は{% data variables.product.prodname_ghe_server %}インスタンス上で{% data variables.product.prodname_pages %}のサイトを作成してビルドする権限を持っていなければなりません。この脆弱性は3.1.8以前のすべての{% data variables.product.prodname_ghe_server %}のバージョンに影響し、3.1.8、3.0.16、2.22.22で修正されました。これは、CVE-2021-22867に対する不完全な修正の結果です。この脆弱性はGitHub Bug Bounty Programを通じて報告され、CVE-2020-22868が割り当てられました。{% comment %} https://github.com/github/pages/pull/3360, https://github.com/github/pages/pull/3357 {% endcomment %}' + - '** 中 **: {% data variables.product.prodname_ghe_server %}の不適切なアクセス制御の脆弱性によって、アクセスできるべきではないワークフロージョブがセルフホストランナーグループ内で実行できてしまいます。これは、アクセス制御にセルフホストランナーグループを使うお客様に影響します。1つのEnterpriseランナーグループにアクセスできるリポジトリが、リクエスト中の不適切な認証チェックのために、Organization内のすべてのEnterpriseランナーグループにアクセスできてしまいます。これによって、意図せず不適切なランナーグループ内でコードが実行される事があります。この脆弱性は、{% data variables.product.prodname_ghe_server %}のバージョン3.0.0から3.0.15及び3.1.0から3.1.7に影響し、3.0.16及び3.1.8リリースで修正されました。これにはCVE-2021-22869が割り当てられました。{% comment %} https://github.com/github/enterprise2/pull/27003 {% endcomment %}' + bugs: + - 'メンテナンスモードの際に、レスキューワーカー数が不正確に表示されました。{% comment %} https://github.com/github/enterprise2/pull/26898, https://github.com/github/enterprise2/pull/26883 {% endcomment %}' + - 'クラスタリングモードにおいて、割り当てられたmemcachedのメモリがゼロになることがありました。{% comment %} https://github.com/github/enterprise2/pull/26927, https://github.com/github/enterprise2/pull/26832 {% endcomment %}' + - 'Fixes {% data variables.product.prodname_pages %} builds so they take into account the NO_PROXY setting of the appliance. This is relevant to appliances configured with an HTTP proxy only. (update 2021-09-30) {% comment %} https://github.com/github/pages/pull/3360 {% endcomment %}' + known_issues: + - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}で、攻撃者が最初の管理ユーザを作成できました。 + - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。 + - Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。 + - 同じリポジトリ内のファイルパスが255文字を超えるblobへのパーマリンクを含むIssueをクローズできませんでした。 + - GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。 + - High Availability構成でレプリカノードがオフラインの場合でも、{% data variables.product.product_name %}が{% data variables.product.prodname_pages %}リクエストをオフラインのノードにルーティングし続ける場合があり、それによってユーザにとっての{% data variables.product.prodname_pages %}の可用性が下がってしまいます。 + - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-0/2.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-0/2.yml index c836ecf986..562466cd15 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://enterprise.githubsupport.com/hc/en-us). + - メンテナンスモードが有効化されているとき、サービスの中に引き続き"active processes"としてリストされるものがあります。特定されたサービスは、メンテナンスモード中にも実行されることが期待されるものです。この問題が生じており、不確実な場合は[GitHub Enterprise Support](https://enterprise.githubsupport.com/hc/en-us)にお問い合わせください。 - ノートブックに非ASCIIのUTF-8文字が含まれている場合、Web UI中でのJupyter Notebookのレンダリングが失敗することがあります。 - Web UIでのreStructuredText (RST) のレンダリングが失敗し、代わりにRSTのマークアップテキストがそのまま表示されることがあります。 - Pagesの古いビルドがクリーンアップされず、ユーザディスク(`/data/user/`)を使い切ってしまうことがあります。 @@ -55,4 +55,4 @@ sections: 2. 1つ以上のノードが影響されていると表示されたら、影響されているノードを再起動してください。 - High Availability構成でレプリカノードがオフラインの場合でも、{% data variables.product.product_name %}が{% data variables.product.prodname_pages %}リクエストをオフラインのノードにルーティングし続ける場合があり、それによってユーザにとっての{% data variables.product.prodname_pages %}の可用性が下がってしまいます。 - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. + - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 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 07b8c91816..acbd1e4373 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,18 +26,18 @@ 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://enterprise.githubsupport.com/hc/en-us). + - メンテナンスモードが有効化されているとき、サービスの中に引き続き"active processes"としてリストされるものがあります。特定されたサービスは、メンテナンスモード中にも実行されることが期待されるものです。この問題が生じており、不確実な場合は[GitHub Enterprise Support](https://enterprise.githubsupport.com/hc/en-us)にお問い合わせください。 - ノートブックに非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://enterprise.githubsupport.com/hc/en-us) 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 sudo /usr/sbin/logrotate -f /etc/logrotate.conf ``` - High Availability構成でレプリカノードがオフラインの場合でも、{% data variables.product.product_name %}が{% data variables.product.prodname_pages %}リクエストをオフラインのノードにルーティングし続ける場合があり、それによってユーザにとっての{% data variables.product.prodname_pages %}の可用性が下がってしまいます。 - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. + - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-0/4.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-0/4.yml index ee0681aa9a..43648f2668 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-0/4.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-0/4.yml @@ -25,4 +25,4 @@ sections: - Web UIでのreStructuredText (RST) のレンダリングが失敗し、代わりにRSTのマークアップテキストがそのまま表示されることがあります。 - Pull Requestをマージした後にブランチを削除すると、ブランチの削除は成功しているにもかかわらずエラーメッセージが表示されます。 - High Availability構成でレプリカノードがオフラインの場合でも、{% data variables.product.product_name %}が{% data variables.product.prodname_pages %}リクエストをオフラインのノードにルーティングし続ける場合があり、それによってユーザにとっての{% data variables.product.prodname_pages %}の可用性が下がってしまいます。 - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. + - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-0/5.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-0/5.yml index 9b297a746d..d4bf6a5cee 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-0/5.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-0/5.yml @@ -26,4 +26,4 @@ sections: - GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。 - Pull Requestをマージした後にブランチを削除すると、ブランチの削除は成功しているにもかかわらずエラーメッセージが表示されます。 - High Availability構成でレプリカノードがオフラインの場合でも、{% data variables.product.product_name %}が{% data variables.product.prodname_pages %}リクエストをオフラインのノードにルーティングし続ける場合があり、それによってユーザにとっての{% data variables.product.prodname_pages %}の可用性が下がってしまいます。 - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. + - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-0/6.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-0/6.yml index 4c7b76352b..0739609fa8 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-0/6.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-0/6.yml @@ -29,4 +29,4 @@ sections: - 同じリポジトリ内のファイルパスが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 %}の可用性が下がってしまいます。 - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. + - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-0/7.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-0/7.yml index c0e4b910b4..75ac59114e 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-0/7.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-0/7.yml @@ -22,4 +22,4 @@ sections: - 同じリポジトリ内のファイルパスが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 %}の可用性が下がってしまいます。 - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. + - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-0/8.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-0/8.yml index 62037c2229..d8bcd4d785 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-0/8.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-0/8.yml @@ -25,4 +25,4 @@ sections: - 同じリポジトリ内のファイルパスが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 %}の可用性が下がってしまいます。 - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. + - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-0/9.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-0/9.yml index 636c8b2fde..0c5a55ecaa 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-0/9.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-0/9.yml @@ -22,4 +22,4 @@ sections: - 同じリポジトリ内のファイルパスが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 %}の可用性が下がってしまいます。 - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. + - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-1/0.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-1/0.yml index 168436290d..1975852e9d 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-1/0.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-1/0.yml @@ -139,7 +139,7 @@ sections: ghe-actions-console -s actions -c "Queue-ServiceJob -JobId 4DB1F4CF-19FD-40E0-A253-91288813DE8B" ``` - High Availability構成でレプリカノードがオフラインの場合でも、{% data variables.product.product_name %}が{% data variables.product.prodname_pages %}リクエストをオフラインのノードにルーティングし続ける場合があり、それによってユーザにとっての{% data variables.product.prodname_pages %}の可用性が下がってしまいます。 - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. + - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 deprecations: - heading: GitHub Enterprise Server 2.20の非推奨化 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-1/1.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-1/1.yml index 784e4d4e0b..9dd1a5686d 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-1/1.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-1/1.yml @@ -27,5 +27,5 @@ sections: ghe-actions-console -s actions -c "Queue-ServiceJob -JobId 4DB1F4CF-19FD-40E0-A253-91288813DE8B" ``` - High Availability構成でレプリカノードがオフラインの場合でも、{% data variables.product.product_name %}が{% data variables.product.prodname_pages %}リクエストをオフラインのノードにルーティングし続ける場合があり、それによってユーザにとっての{% data variables.product.prodname_pages %}の可用性が下がってしまいます。 - - 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. + - '{% data variables.product.prodname_ghe_server %}で{% data variables.product.prodname_actions %}が有効化されていると、`ghe-repl-teardown`でのレプリカノードの解体は成功しますが、`ERROR:Running migrations`が返されることがあります。' + - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-1/2.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-1/2.yml index abc4d00d5e..2968374438 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-1/2.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-1/2.yml @@ -23,5 +23,5 @@ sections: ``` ghe-actions-console -s actions -c "Queue-ServiceJob -JobId 4DB1F4CF-19FD-40E0-A253-91288813DE8B" ``` - - 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. + - '{% data variables.product.prodname_ghe_server %}で{% data variables.product.prodname_actions %}が有効化されていると、`ghe-repl-teardown`でのレプリカノードの解体は成功しますが、`ERROR:Running migrations`が返されることがあります。' + - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-1/3.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-1/3.yml index 0d64b0080a..15bdb9e677 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-1/3.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-1/3.yml @@ -2,21 +2,21 @@ date: '2021-07-14' sections: security_fixes: - - '**HIGH:** A path traversal vulnerability was identified in GitHub Enterprise Server that could be exploited when building a GitHub Pages site. User-controlled configuration options used by GitHub Pages were not sufficiently restricted and made it possible to read files on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.1.3 and has been assigned CVE-2021-22867. This vulnerability was reported via the GitHub Bug Bounty program.' + - '**高:** GitHubPagesのサイトをビルドする際に利用される可能性があるパストラバーサルの脆弱性が、GitHub Enterprise Serverで特定されました。GitHub Pagesが使用するユーザが制御する設定オプションが十分に厳密ではなく、GitHub Enterprise Serverインスタンス上のファイルを読めてしまいます。この脆弱性を利用するには、攻撃者はGitHub Enterprise Serverインスタンス上でGitHub Pagesのサイトを作成してビルドする権限を持っていなければなりません。この脆弱性は3.1.3以前のすべてのバージョンのGitHub Enterprise Serverに影響し、CVE-2021-22867が割り当てられました。この脆弱性はGitHub Bug Bountyプログラムを通じて報告されました。' - パッケージは最新のセキュリティバージョンにアップデートされました。 bugs: - - SAML expiration date variable was not configurable. - - Application services would fail their health checks during config apply before they could enter a healthy state. - - '`ghe-cluster-config-node-init` would fail during cluster setup if HTTP proxy is enabled.' - - Pre-receive hooks could encounter an error `Failed to resolve full path of the current executable` due to `/proc` not being mounted on the container. - - Collectd would not resolve the forwarding destination hostname after the initial startup. - - The job that purged stale deleted repositories could fail to make progress if some of those repositories were protected from deletion by legal holds. - - Background jobs were being queued to the `spam` queue which were not being processed. - - The preferred merge method would be reset when retrying after a failed PR merge. - - Git pushes could result in a 500 Internal Server Error during the user reconciliation process on instances using LDAP authentication mode. - - 'After upgrading from 3.0.x to 3.1.x, in some cases GitHub Actions would fail with an error: `An unexpected error occurred when executing this workflow.`' + - SAMLの期限切れの日付変数は設定できませんでした。 + - アプリケーションサービスは、設定の適用の間に健全な状態に入る前、ヘルスチェックに失敗します。 + - '`ghe-cluster-config-node-init`は、HTTPプロキシが有効化されているとクラスタのセットアップの間に失敗します。' + - pre-receive フックで、`/proc`がコンテナにマウントされていないために`Failed to resolve full path of the current executable`という失敗が生じることがあります。 + - collectdは、初期のセットアップ後にフォワード先のホスト名を解決しません。 + - 古い柵得除されたリポジトリをパージするジョブは、それらのリポジトリの中に訴訟ホールドによって削除から保護されているものがある場合、処理を進められないことがあります。 + - バックグラウンドジョブが、処理されていない`spam`キューにキューイングされました。 + - 失敗したPRマージ後にリトライする際に、優先されるマージ方法がリセットされます。 + - LDAP認証モードを使うインスタンスにおいて、Git pushがユーザ照合プロセス中に500 Internal Server Errorになることがあります。 + - '3.0.xから3.1.xへのアップグレード後に、GitHub Actionsが`An unexpected error occurred when executing this workflow.`というエラーで失敗することがあります。' changes: - - Improved the efficiency of config apply by skipping IP allow firewall rules that had not changed, which saved significant time on large clusters. + - 変更されなかったIP許可ファイアウォールルールをスキップすることによって、設定適用の効率性が改善されました。これは大規模なクラスタでは大きな時間の節約になります。 known_issues: - '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。' - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}で、攻撃者が最初の管理ユーザを作成できました。 @@ -24,5 +24,5 @@ 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が含まれません。 - - 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. + - '{% data variables.product.prodname_ghe_server %}で{% data variables.product.prodname_actions %}が有効化されていると、`ghe-repl-teardown`でのレプリカノードの解体は成功しますが、`ERROR:Running migrations`が返されることがあります。' + - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-1/4.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-1/4.yml index 5e1dc30fc3..751cfc75da 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-1/4.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-1/4.yml @@ -4,20 +4,20 @@ sections: security_fixes: - パッケージは最新のセキュリティバージョンにアップデートされました。 bugs: - - The counts on packages pages were not being incremented when a package was downloaded. - - '`ghe-config-apply` would timeout, ask for a prompt or fail for a customer that had {% data variables.product.prodname_secret_scanning %} enabled, and had either disabled or never enabled {% data variables.product.prodname_actions %} on their instance.' - - Log files were not reopened after rotation in some cases leading to high disk space usage on instances with high uptime. - - Upgrade could fail from older version of {% data variables.product.prodname_ghe_server %} due to a missing job in {% data variables.product.prodname_actions %}. - - 'Custom pre-receive hooks could lead to an error like `error: object directory /data/user/repositories/0/nw/12/34/56/7890/network.git/objects does not exist; check .git/objects/info/alternates`.' - - Unauthenticated HTTP proxy for the pages containers build was not supported for any users that use HTTP proxies. - - A significant number of 503 errors were logged every time a user visited a repository's `/settings` page if the dependency graph was not enabled. - - Internal repositories were only returned when a user had affiliations with the repository through a team or through collaborator status, or queried with the `?type=internal` parameter. - - Failed background jobs had unlimited retries which could cause large queue depths. - - A significant number of 503 errors were being created if the scheduled job to sync vulnerabilities with GitHub.com attempted to run when dependency graph was not enabled and content analysis was enabled. + - パッケージがダウンロードされたとき、packagesページのカウントが増えませんでした。 + - 'インスタンス上で{% data variables.product.prodname_secret_scanning %}を有効化し、{% data variables.product.prodname_actions %}を無効化するか、有効化したことがないお客様に対して、`ghe-config-apply`がタイムアウトになり、プロンプトを求めるか失敗するかします。' + - ローテーション後にログファイルが再オープンされず、稼働時間が長いインスタンスでディスク領域の使用量が多くなります。 + - '{% data variables.product.prodname_ghe_server %}の古いバージョンからのアップグレードが、{% data variables.product.prodname_actions %}でのジョブが不足しているために失敗することがあります。' + - 'カスタムのpre-receive フックで`error: object directory /data/user/repositories/0/nw/12/34/56/7890/network.git/objects does not exist; check .git/objects/info/alternates`のようなエラーが生じることがあります。' + - HTTPプロキシを使用するユーザでは、Pagesのコンテナビルドの認証されていないHTTPプロキシはサポートされていませんでした。 + - 依存関係グラフが有効化されていない場合、ユーザがリポジトリの`/settings`ページにアクセスするたびに大量の503エラーが記録されました。 + - インターナルリポジトリは、ユーザがそのリポジトリにTeamを通じて、あるいはコラボレータのステータスを通じて関係があるか、`?type=internal`パラメータ付きでクエリされた場合にのみ返されました。 + - 失敗したバックグラウンドジョブが無制限のリトライを行い、大きなキューの深さを生じさせることがありました。 + - 依存関係グラフが有効化されておらず、コンテンツ分析が有効化されている状態で、スケジュールジョブがGitHub.comと脆弱性を同期しようとすると、大量の503エラーが発生しました。 - | - When {% data variables.product.prodname_actions %} is enabled without running regular scheduled backups, the MSSQL transaction log could grow unbounded and can consume all available space on the appliance's data disk, causing a possible outage. + 定期的なスケジュールバックアップが実行されていない状態で{% data variables.product.prodname_actions %}が有効化されると、MSSQLのトランザクションログが無制限に大きくなり、アプリケーションのデータディスクの利用可能なすべての領域を消費してしまい、障害を引き起こすことがあります。 - If you have configured regularly scheduled MSSQL backups, no further actions is required. Otherwise, if you have {% data variables.product.prodname_actions %} previously enabled, run the following commands after installing this patch. + 定期的なMSSQLのスケジュールバックアップを設定しているなら、それ以上のアクションは不要です。そうでない場合は、{% data variables.product.prodname_actions %}を以前に有効化しているなら、このパッチをインストールしてから以下のコマンドを実行してください。 ``` ghe-actions-console -s Mps -c 'Update-Service -Force' @@ -25,7 +25,7 @@ sections: ghe-actions-console -s Actions -c 'Update-Service -Force' ``` changes: - - The logs for `babeld` now include a `cmd` field for HTTP ref advertisement requests instead of only including it during the negotiation requests. + - '`babeld`のログには、ネゴシエーションリクエストの際だけではなく、HTTP参照広告リクエストの`cmd`フィールドが含まれるようになりました。' known_issues: - '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。' - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}で、攻撃者が最初の管理ユーザを作成できました。 @@ -33,5 +33,5 @@ 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が含まれません。 - - 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. + - '{% data variables.product.prodname_ghe_server %}で{% data variables.product.prodname_actions %}が有効化されていると、`ghe-repl-teardown`でのレプリカノードの解体は成功しますが、`ERROR:Running migrations`が返されることがあります。' + - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-1/5.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-1/5.yml index 6396451788..071aa09415 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-1/5.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-1/5.yml @@ -2,14 +2,14 @@ date: '2021-08-10' sections: bugs: - - 'Custom pre-receive hooks that used a bash subshell would return an error: `No such file or directory`.' - - When GitHub Actions is enabled without running regular scheduled backups the MSSQL Transaction Log could grow unbounded and can consume all available space on the appliance's Data Disk causing a possible outage. - - Unnecessary database logging consumed a large amount of disk space on instances with heavy LFS usage. - - Audit log entries for changes made to "Repository creation" organization settings were inaccurate. - - Excessive logging of `ActionController::UnknownFormat` exceptions caused unnecessary disk usage. - - "LDAP `group_dn` values longer than 255 characters would result in errors being logged: `Data truncated for column 'group_dn' at row 1`." + - 'bashのサブシェルを使うカスタムのpre-receive フックは、`No such file or directory`というエラーを返します。' + - 定期的なMSSQLのトランザクションログのスケジュールバックアップを実行することなくGitHub Actionsを有効化すると、ログが無制限に拡大し、アプライアンスのデータディスクの利用可能な領域をすべて消費し、障害につながる可能性があります。 + - LFSの利用度が高いインスタンスにおいて、不要なデータベースのロギングが大量のディスク領域を消費しました。 + - '"Repository creation" Organizationの設定に対する変更の監査ログエントリが不正確でした。' + - '`ActionController::UnknownFormat`例外の過剰なロギングが、不要なディスク消費を招いていました。' + - "255文字以上のLDAP `group_dn`値によって、`Data truncated for column 'group_dn' at row 1`というエラーが記録されます。" changes: - - Abuse rate limits are now called Secondary rate limits, since the behavior they limit is not always abusive. + - 不正利用レート制限は、セカンダリレート制限と呼ばれるようになりました。これは、これによって制限されるのが必ずしも不正利用とは限らないためです。 known_issues: - '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。' - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}で、攻撃者が最初の管理ユーザを作成できました。 @@ -17,5 +17,5 @@ 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が含まれません。 - - 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. + - '{% data variables.product.prodname_ghe_server %}で{% data variables.product.prodname_actions %}が有効化されていると、`ghe-repl-teardown`でのレプリカノードの解体は成功しますが、`ERROR:Running migrations`が返されることがあります。' + - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-1/6.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-1/6.yml index d48861e42e..2d83094223 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-1/6.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-1/6.yml @@ -4,15 +4,15 @@ sections: security_fixes: - パッケージは最新のセキュリティバージョンにアップデートされました。 bugs: - - Attaching very large images or animated GIFs to images or pull requests would fail. - - Journald messages related to automatic updates (`Adding h/m/s random time.`) were logged to syslog. - - Custom pre-receive hooks that created named pipes (FIFOs) would crash or hang, resulting in a timeout error. - - Adding filters to the audit log advanced search page did not populate the query text box in real-time with the correct facet prefix and value. - - Git hooks to the internal API that result in failing requests returned the exception `undefined method body for "success":String (NoMethodError)` instead of returning an explicit `nil`. - - When an integration was removed, it was possible for an unrelated OAuth application or integration to also be removed. - - When a mandatory message containing an emoji character was added, attempting to view or change the message would return a 500 Internal Server Error. + - 画像あるいはPull Requestに非常に大きな画像もしくはアニメーションGIFを添付すると失敗します。 + - 自動アップデートに関係するJournaldのメッセージ (`Adding h/m/s random time.`)が、syslogに記録されました。 + - 名前付きパイプ（FIFO）を作成したカスタムのpre-receive フックは、クラッシュもしくはハングし、タイムアウトエラーを生じさせます。 + - 監査ログの高度な検索ページにフィルタを追加しても、適切なファセットプレフィックスと値付きでクエリテキストボックスがリアルタイムで展開されませんでした。 + - リクエストに失敗する内部APIへのGitフックが、明示的な`nil`を返す代わりに`undefined method body for "success":String (NoMethodError)`という例外を返しました。 + - インテグレーションが削除されると、関係の無いOAuthアプリケーションあるいはインテグレーションも削除されてしまう可能性がありました。 + - 絵文字を含む必須のメッセージが追加された場合、そのメッセージを表示あるいは変更しようとすると500 Internal Server Errorが返されます。 changes: - - Adds `triage` and `maintain` to the list of permissions returned by the REST API. + - REST APIが返す権限のリストに`triage`と`maintain` を追加しました。 known_issues: - '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。' - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}で、攻撃者が最初の管理ユーザを作成できました。 @@ -20,5 +20,5 @@ 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が含まれません。 - - 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. + - '{% data variables.product.prodname_ghe_server %}で{% data variables.product.prodname_actions %}が有効化されていると、`ghe-repl-teardown`でのレプリカノードの解体は成功しますが、`ERROR:Running migrations`が返されることがあります。' + - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-1/7.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-1/7.yml index 315a77a51d..308d91be3f 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-1/7.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-1/7.yml @@ -4,10 +4,10 @@ sections: security_fixes: - パッケージは最新のセキュリティバージョンにアップデートされました。 bugs: - - Attempting to tear down a newly-added replica node by specifying its UUID with `ghe-repl-teardown` would fail without reporting an error if replication was not started. - - GitHub Pages builds were being passed through an external proxy if there was one configured. - - Custom pre-receive hooks that created sub-processes would lack a `PATH` variable in their environment, resulting in "No such file or directory" errors. - - MySQL could failover during an upgrade if `mysql-auto-failover` was enabled. + - '`ghe-repl-teardown`でUUIDを指定して、新たに追加されたレプリカノードを破棄しようとすると、レプリケーションが開始されていなかった場合にエラーを報告することなく失敗します。' + - 外部プロキシが設定されている場合、GitHub Pagesのビルドがそれを通じて渡されていました。 + - サブプロセスを生成したカスタムのpre-receive フックの環境に`PATH`変数が欠如し、"No such file or directory"エラーが生じます。 + - '`mysql-auto-failover`が有効化されていると、MySQLがアップグレードの際にフェイルオーバーすることがあります。' known_issues: - '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。' - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}で、攻撃者が最初の管理ユーザを作成できました。 @@ -15,5 +15,5 @@ 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が含まれません。 - - 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. + - '{% data variables.product.prodname_ghe_server %}で{% data variables.product.prodname_actions %}が有効化されていると、`ghe-repl-teardown`でのレプリカノードの解体は成功しますが、`ERROR:Running migrations`が返されることがあります。' + - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-1/8.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-1/8.yml new file mode 100644 index 0000000000..87e052deda --- /dev/null +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-1/8.yml @@ -0,0 +1,20 @@ +--- +date: '2021-09-24' +sections: + security_fixes: + - '**高:** {% data variables.product.prodname_pages %}のサイトをビルドする際に利用される可能性があるパストラバーサルの脆弱性が、{% data variables.product.prodname_ghe_server %}で特定されました。{% data variables.product.prodname_pages %}が使用する、ユーザが制御する設定が十分に厳密ではなく、{% data variables.product.prodname_ghe_server %}インスタンス上でファイルを読めてしまいます。この脆弱性を利用するには、攻撃者は{% data variables.product.prodname_ghe_server %}インスタンス上で{% data variables.product.prodname_pages %}のサイトを作成してビルドする権限を持っていなければなりません。この脆弱性は3.1.8以前のすべての{% data variables.product.prodname_ghe_server %}のバージョンに影響し、3.1.8、3.0.16、2.22.22で修正されました。これは、CVE-2021-22867に対する不完全な修正の結果です。この脆弱性はGitHub Bug Bounty Programを通じて報告され、CVE-2020-22868が割り当てられました。{% comment %} https://github.com/github/pages/pull/3361, https://github.com/github/pages/pull/3357 {% endcomment %}' + - '** 中 **: {% data variables.product.prodname_ghe_server %}の不適切なアクセス制御の脆弱性によって、アクセスできるべきではないワークフロージョブがセルフホストランナーグループ内で実行できてしまいます。これは、アクセス制御にセルフホストランナーグループを使うお客様に影響します。1つのEnterpriseランナーグループにアクセスできるリポジトリが、リクエスト中の不適切な認証チェックのために、Organization内のすべてのEnterpriseランナーグループにアクセスできてしまいます。これによって、意図せず不適切なランナーグループ内でコードが実行される事があります。この脆弱性は、{% data variables.product.prodname_ghe_server %}のバージョン3.0.0から3.0.15及び3.1.0から3.1.7に影響し、3.0.16及び3.1.8リリースで修正されました。これにはCVE-2021-22869が割り当てられました。{% comment %} https://github.com/github/enterprise2/pull/27013 {% endcomment %}' + bugs: + - 'メンテナンスモードの際に、レスキューワーカー数が不正確に表示されました。{% comment %} https://github.com/github/enterprise2/pull/26899, https://github.com/github/enterprise2/pull/26883 {% endcomment %}' + - 'クラスタリングモードにおいて、割り当てられたmemcachedのメモリがゼロになることがありました。{% comment %} https://github.com/github/enterprise2/pull/26928, https://github.com/github/enterprise2/pull/26832 {% endcomment %}' + - 'Pull Requestの"Files"タブで、空ではないバイナリファイルのファイルタイプやサイズが不正確に表示されました。{% comment %} https://github.com/github/github/pull/192810, https://github.com/github/github/pull/172284, https://github.com/github/coding/issues/694 {% endcomment %}' + - 'Fixes {% data variables.product.prodname_pages %} builds so they take into account the NO_PROXY setting of the appliance. This is relevant to appliances configured with an HTTP proxy only. (update 2021-09-30) {% comment %} https://github.com/github/pages/pull/3360 {% endcomment %}' + known_issues: + - '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。' + - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}で、攻撃者が最初の管理ユーザを作成できました。 + - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。 + - Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。 + - 同じリポジトリ内のファイルパスが255文字を超えるblobへのパーマリンクを含むIssueをクローズできませんでした。 + - GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。 + - '{% data variables.product.prodname_ghe_server %}で{% data variables.product.prodname_actions %}が有効化されていると、`ghe-repl-teardown`でのレプリカノードの解体は成功しますが、`ERROR:Running migrations`が返されることがあります。' + - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-2/0-rc1.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-2/0-rc1.yml index a891ad2b98..8423faf957 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-2/0-rc1.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-2/0-rc1.yml @@ -1,84 +1,84 @@ --- date: '2021-09-09' release_candidate: true -deprecated: false +deprecated: true intro: '{% data variables.product.product_location %}がリリース候補ビルドを実行しているなら、ホットパッチでアップグレードはできません。リリース候補を動作させるのは、テスト環境のみにすることをおすすめします。' sections: features: - - heading: Custom patterns for secret scanning + heading: Secret Scanningのカスタムパターン notes: - | - {% data variables.product.prodname_GH_advanced_security %} customers can now specify custom patterns for secret scanning. When a new pattern is specified, secret scanning searches a repository's entire Git history for the pattern, as well as any new commits. + {% data variables.product.prodname_GH_advanced_security %}のお客様は、Secret scanningでカスタムパターンを指定できるようになりました。新しいパターンが指定されると、Secret scanningは新しいコミットとともに、リポジトリのGit履歴全体に対してそのパターンを検索します。 - User defined patterns are in beta for {% data variables.product.prodname_ghe_server %} 3.2. They can be defined at the repository, organization, and enterprise levels. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." + ユーザ定義パターンは、{% data variables.product.prodname_ghe_server %} 3.2ではベータです。ユーザ定義パターンは、リポジトリ、Organization、Enterpriseのレベルで定義できます。詳しい情報については「[Secret scanningのカスタムパターンの定義](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)」を参照してください。 - - heading: Security overview for Advanced Security (beta) + heading: Advanced Security（ベータ）のセキュリティの概要 notes: - | - {% data variables.product.prodname_GH_advanced_security %} customers now have an organization-level view of the application security risks detected by {% data variables.product.prodname_code_scanning %}, {% data variables.product.prodname_dependabot %}, and {% data variables.product.prodname_secret_scanning %}. The security overview shows the enablement status of security features on each repository, as well as the number of alerts detected. + {% data variables.product.prodname_GH_advanced_security %}のお客様は、{% data variables.product.prodname_code_scanning %}、{% data variables.product.prodname_dependabot %}、{% data variables.product.prodname_secret_scanning %}によって検出されたアプリケーションのセキュリティリスクのOrganizationレベルのビューを利用できるようになりました。このセキュリティの概要は、検出されたアラート数とともに、それぞれのリポジトリにおけるセキュリティ機能の有効化の状況を示します。 - In addition, the security overview lists all {% data variables.product.prodname_secret_scanning %} alerts at the organization level. Similar views for {% data variables.product.prodname_dependabot %} and {% data variables.product.prodname_code_scanning %} alerts are coming in future releases. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." + 加えて、このセキュリティの概要はすべての{% data variables.product.prodname_secret_scanning %}アラートをOrganizationレベルでリストします。{% data variables.product.prodname_dependabot %}及び{% data variables.product.prodname_code_scanning %}アラートの同様のビューが、将来のリリースで導入されます。詳しい情報に付いては「[セキュリティの概要について](/code-security/security-overview/about-the-security-overview)」を参照してください。 - ![Screenshot of security overview](/assets/images/enterprise/3.2/release-notes/security-overview-UI.png) + ![セキュリティの概要のスクリーンショット](/assets/images/enterprise/3.2/release-notes/security-overview-UI.png) - - heading: Dependency review (beta) + heading: 依存関係レビュー（ベータ） notes: - | - {% data variables.product.prodname_GH_advanced_security %} customers can now see a rich diff of the dependencies changed in a pull request. 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 these dependencies. 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)." + {% data variables.product.prodname_GH_advanced_security %}のお客様は、Pull Request内で変更された依存関係のリッチdiffを見ることができるようになりました。依存関係レビューは、Pull Requestの"Files changed"タブで、依存関係の変更とそのセキュリティへのインパクトの理解しやすいビューを提供します。これは、追加、削除、更新された依存関係を、それらについての脆弱性の情報とともに知らせてくれます。詳しい情報については「[Pull Request内での依存関係の変更のレビュー](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)」を参照してください。 - - heading: GitHub Actions environments + heading: GitHub Actionsの環境 notes: - | - Environments, environment protection rules, and environment secrets are now generally available for {% data variables.product.prodname_actions %} on {% data variables.product.product_name %}. For more information, see "[Environments](/actions/reference/environments)." + 環境、環境保護ルール、環境シークレットは{% data variables.product.product_name %}上の{% data variables.product.prodname_actions %}で一般に利用可能になりました。詳しい情報については「[環境](/actions/reference/environments)」を参照してください。 - ![Environment protection rules](/assets/images/enterprise/3.2/release-notes/actions-environments.png) + ![環境保護ルール](/assets/images/enterprise/3.2/release-notes/actions-environments.png) - - heading: SSH authentication with security keys + heading: セキュリティキーによるSSH認証 notes: - | - SSH authentication using a FIDO2 security key is now supported when you add a `sk-ecdsa-sha2-nistp256@openssh.com` or `sk-ssh-ed25519@openssh.com` SSH key to your account. SSH security keys store secret key material on a separate hardware device that requires verification, such as a tap, to operate. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)." + `sk-ecdsa-sha2-nistp256@openssh.com`あるいは`sk-ssh-ed25519@openssh.com`SSHキーをアカウントに追加すると、FIDO2セキュリティキーを使ったSSH認証がサポートされるようになりました。SSHセキュリティキーは、セキュリティキーの実体を、利用に際してタップのような検証を必要とする個別のハードウェアデバイスに保存します。詳しい情報については「[ 新しいSSHキーの生成とssh-agentへの追加](/github/authenticating-to-github/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)」を参照してください。 - - heading: 'Dark and dark dimmed themes' + heading: 'ダーク及びダーク淡色テーマ' notes: - | - Dark and dark dimmed themes are now available for the web UI. {% data variables.product.product_name %} will match your system preferences when you haven't set theme preferences in {% data variables.product.product_name %}. You can also choose which themes are active during the day and night. For more information, see "[Managing your theme settings](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)." + Web UIでダーク及びダーク淡色テーマが利用できるようになりました。{% data variables.product.product_name %}は、{% data variables.product.product_name %}でテーマの環境設定を設定していない場合、システムの環境設定に合わせます。また、昼間と夜間でアクティブにするテーマを選択できます。詳しい情報については「[テーマ設定の管理](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)」を参照してください。 - ![Dark and dark dimmed themes](https://user-images.githubusercontent.com/33528647/114629560-d2231f80-9c86-11eb-9bde-cc301a97040d.gif) + ![ダーク及びダーク淡色テーマ](https://user-images.githubusercontent.com/33528647/114629560-d2231f80-9c86-11eb-9bde-cc301a97040d.gif) - - heading: 'Approving unverified domains for email notifications' + heading: 'メール通知のための未検証ドメインの承認' notes: - - 'Domains that are not able to be verified can now be approved for email notification routing. Enterprise and organization owners will be able to approve domains and immediately augment their email notification restriction policy, allowing notifications to be sent to collaborators, consultants, acquisitions, or other partners. For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#about-approval-of-domains)" and "[Restricting email notifications for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise#restricting-email-notifications-for-your-enterprise-account)."' + - '検証不能なドメインを、メール通知のルーティングで承認できるようになりました。Enterprise及びOrganizationのオーナーは、ドメインを承認し、すぐにメール通知の制限ポリシーを拡張し、通知をコラボレータ、コンサルタント、買収先、その他のパートナーに送信できるようにすることができます。詳しい情報については「[Enterpriseでのドメインの検証もしくは承認](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#about-approval-of-domains)」及び「[Enterpriseでのメール通知の制限](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise#restricting-email-notifications-for-your-enterprise-account)」を参照してください。' - - heading: 'Git Credential Manager (GCM) secure credential storage and multi-factor authentication support' + heading: 'セキュアな認証情報ストレージGit Credential Manager (GCM)と多要素認証のサポート' notes: - | - Git Credential Manager (GCM) Core versions 2.0.452 and later now provide security-hardened credential storage and multi-factor authentication support for {% data variables.product.product_name %}. + Git Credential Manager (GCM) Coreバージョン2.0.452以降は、セキュリティ強化された認証情報のストレージと、{% data variables.product.product_name %}のための多要素認証を提供します。 - GCM Core with support for {% data variables.product.product_name %} is included with [Git for Windows](https://gitforwindows.org) versions 2.32 and later. GCM Core is not included with Git for macOS or Linux, but can be installed separately. For more information, see the [latest release](https://github.com/microsoft/Git-Credential-Manager-Core/releases/) and [installation instructions](https://github.com/microsoft/Git-Credential-Manager-Core/releases/) in the `microsoft/Git-Credential-Manager-Core` repository. + {% data variables.product.product_name %}をサポートするGCM Coreは[Git for Windows](https://gitforwindows.org)バージョン2.32以降に含まれています。GCM Coreは、Git for macOSもしくはLinuxには含まれていませんが、個別にインストールすることはできます。詳しい情報については、 `microsoft/Git-Credential-Manager-Core`リポジトリ中の[最新のリリース](https://github.com/microsoft/Git-Credential-Manager-Core/releases/)及び[インストール手順](https://github.com/microsoft/Git-Credential-Manager-Core/releases/)を参照してください。 changes: - heading: 管理に関する変更 notes: - - A 'User Agent Referrer Policy' setting has been added to the enterprise settings. This allows an admin to set a stricter `Referrer-Policy` to hide the hostname of a {% data variables.product.prodname_ghe_server %} installation from external sites. The setting is disabled by default and is tracked by audit log events for staff and enterprise owners when enabled or disabled. For more information, see "[Configuring Referrer Policy for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)." - - The MySQL health check was changed to use `mysqladmin ping` instead of TCP checks, which removes some unnecessary noise in the MySQL error log. Also, Orchestrator failover checks were improved to prevent unnecessary MySQL failovers when applying cluster config changes. - - 'The Resque service, which supports background job processing, has been replaced with Aqueduct Lite. This change makes the job system easier to manage and should not affect the user experience. For the new administration and debugging commands for Aqueduct, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-aqueduct)."' + - Enterprise設定に、'User Agent Referrer Policy''設定が追加されました。これによって、外部のサイトから{% data variables.product.prodname_ghe_server %}のインストールのホスト名を隠蔽する、厳格な`Referrer-Policy`を管理者が設定できるようになります。この設定はデフォルトで無効になっており、スタッフやEnterpriseのオーナーが有効化あるいは無効化した場合は監査ログイベントで追跡されます。詳しい情報については「[Enterpriseのリファラーポリシーの設定](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)」を参照してください。 + - MySQLのヘルスチェックはTCPのチェックの代わりに`mysqladmin ping`を使うよう変更され、これによってMySQLのエラーログから不要なノイズが取り除かれます。また、オーケストレーターのフェイルオーバーチェックが改善され、クラスタ設定の変更適用時の不要なMySQLのフェイルオーバーが回避されるようになりました。 + - 'バックグラウンドジョブの処理をサポートするレスキューサービスが、Aqueduct Liteで置き換えられました。この変更によってジョブシステムは管理しやすくなり、ユーザ体験には影響はないはずです。Aqueductの新しい管理及びデバッギングコマンドについては、「[コマンドラインユーティリティ](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-aqueduct)」を参照してください。' - - heading: Token Changes + heading: トークンの変更 notes: - | - The format of authentication tokens for {% data variables.product.product_name %} has changed. The change affects the format of personal access tokens and access tokens for {% data variables.product.prodname_oauth_apps %}, as well as user-to-server, server-to-server, and refresh tokens for {% data variables.product.prodname_github_apps %}. + {% data variables.product.product_name %}のための認証トークンのフォーマットは変更されました。この変更は、個人アクセストークンのフォーマットと、{% data variables.product.prodname_oauth_apps %}のためのアクセストークンとともに、{% data variables.product.prodname_github_apps %}のためのuser-to-server、server-to-server、リフレッシュトークンに影響します。 - The different token types now have unique identifiable prefixes, which allows for secret scanning to detect the tokens so that you can mitigate the impact of someone accidentally committing a token to a repository. {% data variables.product.company_short %} recommends updating existing tokens as soon as possible. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github#githubs-token-formats)" and "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)." + 様々なトークンの種類は、一意の特定可能なプレフィックスを持つようになったので、Secret scanningにそれらのトークンを検出してもらい、誰かがうっかりトークンをリポジトリにコミットしてしまった場合のインパクトを緩和できます。{% data variables.product.company_short %}は、既存のトークンをできるだけ早く更新することをおすすめします。詳しい情報については「[{% data variables.product.prodname_dotcom %}での認証について](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github#githubs-token-formats)」及び「[{% data variables.product.prodname_secret_scanning %}について](/code-security/secret-security/about-secret-scanning)を参照してください。 - - heading: 'Repositories changes' + heading: 'リポジトリの変更' notes: - - Repositories on user profiles and organization profiles now support sorting by star count. - - When viewing the commit history of a single file, you can now click {% octicon "file-code" aria-label="The code icon" %} to view that file at the selected point in history. - - When a submodule is defined with a relative path in {% data variables.product.product_location %}, the submodule is now clickable in the web UI. Clicking the submodule in the web UI will take you to the linked repository. Previously, only submodules with absolute URLs were clickable. This is supported for relative paths for repositories with the same owner that follow the pattern ../REPOSITORY or relative paths for repositories with a different owner that follow the pattern ../OWNER/REPOSITORY. For more information about working with submodules, see [Working with submodules](https://github.blog/2016-02-01-working-with-submodules/) on {% data variables.product.prodname_blog %}. - - 'The web UI can now be used to synchronize an out-of-date branch of a fork with the fork''s upstream branch. If there are no merge conflicts between the branches, the branch is updated either by fast-forwarding or by merging from upstream. If there are conflicts, you will be prompted to create a pull request to resolve the conflicts. For more information, see "[Syncing a fork](/github/collaborating-with-pull-requests/working-with-forks/syncing-a-fork#syncing-a-fork-from-the-web-ui)."' + - ユーザプロフィールとOrganizationプロフィール上のリポジトリは、Star数でのソートをサポートするようになりました。 + - 1つのファイルのコミット履歴を表示させている場合、{% octicon "file-code" aria-label="The code icon" %}をクリックして履歴中の選択した時点でのそのファイルを表示できるようになりました。 + - サブモジュールが{% data variables.product.product_location %}中で相対パスで定義されている場合、そのサブモジュールがWeb UI中でクリックできるようになりました。Web UIでサブモジュールをクリックすると、リンクしたリポジトリに行くことができます。以前は、絶対URLのサブモジュールだけがクリック可能でした。これは、同じオーナーの../REPOSITORYというパターンに従うリポジトリの相対パスか、異なるオーナーの../OWNER/REPOSITORYというパターンに従うリポジトリの相対パスでサポートされています。サブモジュールの扱いに関する詳しい情報については、{% data variables.product.prodname_blog %}の[サブモジュールの扱い](https://github.blog/2016-02-01-working-with-submodules/)を参照してください。 + - 'Web UIを使用して、古くなったフォークを上流のブランチと同期できるようになりました。ブランチ間でマージコンフリクトがない場合、ブランチはfast-forwardingもしくは上流からのマージによって更新されます。コンフリクトがある場合、そのコンフリクトを解決するためのPull Requestの作成が求められます。詳しい情報については「[フォークの同期](/github/collaborating-with-pull-requests/working-with-forks/syncing-a-fork#syncing-a-fork-from-the-web-ui)」を参照してください。' - - heading: 'Markdown changes' + heading: 'Markdownの変更' notes: - 'The markdown editor used when creating or editing a release in a repository now has a text-editing toolbar. For more information, see "[Managing releases in a repository](/github/administering-a-repository/releasing-projects-on-github/managing-releases-in-a-repository#creating-a-release)."' - Uploading video files is now supported everywhere you write Markdown on {% data variables.product.product_name %}. Share demos, reproduction steps, and more in your issue and pull request comments, as well as in Markdown files within repositories, such as READMEs. For more information, see "[Attaching files](/github/writing-on-github/working-with-advanced-formatting/attaching-files)." @@ -184,7 +184,7 @@ sections: - 同じリポジトリ内のファイルパスが255文字を超えるblobへのパーマリンクを含むIssueをクローズできませんでした。 - GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。 - '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。' - - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. + - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 deprecations: - heading: GitHub Enterprise Server 2.21の非推奨化 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-2/0.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-2/0.yml new file mode 100644 index 0000000000..14bba04aa3 --- /dev/null +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-2/0.yml @@ -0,0 +1,221 @@ +--- +date: '2021-09-28' +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: Secret Scanningのカスタムパターン + notes: + - | + {% data variables.product.prodname_GH_advanced_security %}のお客様は、Secret scanningでカスタムパターンを指定できるようになりました。新しいパターンが指定されると、Secret scanningは新しいコミットとともに、リポジトリのGit履歴全体に対してそのパターンを検索します。 + + ユーザ定義パターンは、{% data variables.product.prodname_ghe_server %} 3.2ではベータです。ユーザ定義パターンは、リポジトリ、Organization、Enterpriseのレベルで定義できます。詳しい情報については「[Secret scanningのカスタムパターンの定義](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)」を参照してください。 + - + heading: Advanced Security（ベータ）のセキュリティの概要 + notes: + - | + {% data variables.product.prodname_GH_advanced_security %}のお客様は、{% data variables.product.prodname_code_scanning %}、{% data variables.product.prodname_dependabot %}、{% data variables.product.prodname_secret_scanning %}によって検出されたアプリケーションのセキュリティリスクのOrganizationレベルのビューを利用できるようになりました。このセキュリティの概要は、検出されたアラート数とともに、それぞれのリポジトリにおけるセキュリティ機能の有効化の状況を示します。 + + 加えて、このセキュリティの概要はすべての{% data variables.product.prodname_secret_scanning %}アラートをOrganizationレベルでリストします。{% data variables.product.prodname_dependabot %}及び{% data variables.product.prodname_code_scanning %}アラートの同様のビューが、将来のリリースで導入されます。詳しい情報に付いては「[セキュリティの概要について](/code-security/security-overview/about-the-security-overview)」を参照してください。 + + ![セキュリティの概要のスクリーンショット](/assets/images/enterprise/3.2/release-notes/security-overview-UI.png) + - + heading: 依存関係レビュー（ベータ） + notes: + - | + {% data variables.product.prodname_GH_advanced_security %}のお客様は、Pull Request内で変更された依存関係のリッチdiffを見ることができるようになりました。依存関係レビューは、Pull Requestの"Files changed"タブで、依存関係の変更とそのセキュリティへのインパクトの理解しやすいビューを提供します。これは、追加、削除、更新された依存関係を、それらについての脆弱性の情報とともに知らせてくれます。詳しい情報については「[Pull Request内での依存関係の変更のレビュー](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)」を参照してください。 + - + heading: GitHub Actionsの環境 + notes: + - | + 環境、環境保護ルール、環境シークレットは{% data variables.product.product_name %}上の{% data variables.product.prodname_actions %}で一般に利用可能になりました。詳しい情報については「[環境](/actions/reference/environments)」を参照してください。 + + ![環境保護ルール](/assets/images/enterprise/3.2/release-notes/actions-environments.png) + - + heading: セキュリティキーによるSSH認証 + notes: + - | + `sk-ecdsa-sha2-nistp256@openssh.com`あるいは`sk-ssh-ed25519@openssh.com`SSHキーをアカウントに追加すると、FIDO2セキュリティキーを使ったSSH認証がサポートされるようになりました。SSHセキュリティキーは、セキュリティキーの実体を、利用に際してタップのような検証を必要とする個別のハードウェアデバイスに保存します。詳しい情報については「[ 新しいSSHキーの生成とssh-agentへの追加](/github/authenticating-to-github/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)」を参照してください。 + - + heading: 'ダーク及びダーク淡色テーマ' + notes: + - | + Web UIでダーク及びダーク淡色テーマが利用できるようになりました。{% data variables.product.product_name %}は、{% data variables.product.product_name %}でテーマの環境設定を設定していない場合、システムの環境設定に合わせます。また、昼間と夜間でアクティブにするテーマを選択できます。詳しい情報については「[テーマ設定の管理](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)」を参照してください。 + + ![ダーク及びダーク淡色テーマ](https://user-images.githubusercontent.com/33528647/114629560-d2231f80-9c86-11eb-9bde-cc301a97040d.gif) + - + heading: 'メール通知のための未検証ドメインの承認' + notes: + - '検証不能なドメインを、メール通知のルーティングで承認できるようになりました。Enterprise及びOrganizationのオーナーは、ドメインを承認し、すぐにメール通知の制限ポリシーを拡張し、通知をコラボレータ、コンサルタント、買収先、その他のパートナーに送信できるようにすることができます。詳しい情報については「[Enterpriseでのドメインの検証もしくは承認](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#about-approval-of-domains)」及び「[Enterpriseでのメール通知の制限](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise#restricting-email-notifications-for-your-enterprise-account)」を参照してください。' + - + heading: 'セキュアな認証情報ストレージGit Credential Manager (GCM)と多要素認証のサポート' + notes: + - | + Git Credential Manager (GCM) Coreバージョン2.0.452以降は、セキュリティ強化された認証情報のストレージと、{% data variables.product.product_name %}のための多要素認証を提供します。 + + {% data variables.product.product_name %}をサポートするGCM Coreは[Git for Windows](https://gitforwindows.org)バージョン2.32以降に含まれています。GCM Coreは、Git for macOSもしくはLinuxには含まれていませんが、個別にインストールすることはできます。詳しい情報については、 `microsoft/Git-Credential-Manager-Core`リポジトリ中の[最新のリリース](https://github.com/microsoft/Git-Credential-Manager-Core/releases/)及び[インストール手順](https://github.com/microsoft/Git-Credential-Manager-Core/releases/)を参照してください。 + changes: + - + heading: 管理に関する変更 + notes: + - Enterprise設定に、'User Agent Referrer Policy''設定が追加されました。これによって、外部のサイトから{% data variables.product.prodname_ghe_server %}のインストールのホスト名を隠蔽する、厳格な`Referrer-Policy`を管理者が設定できるようになります。この設定はデフォルトで無効になっており、スタッフやEnterpriseのオーナーが有効化あるいは無効化した場合は監査ログイベントで追跡されます。詳しい情報については「[Enterpriseのリファラーポリシーの設定](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)」を参照してください。 + - MySQLのヘルスチェックはTCPのチェックの代わりに`mysqladmin ping`を使うよう変更され、これによってMySQLのエラーログから不要なノイズが取り除かれます。また、オーケストレーターのフェイルオーバーチェックが改善され、クラスタ設定の変更適用時の不要なMySQLのフェイルオーバーが回避されるようになりました。 + - 'バックグラウンドジョブの処理をサポートするレスキューサービスが、Aqueduct Liteで置き換えられました。この変更によってジョブシステムは管理しやすくなり、ユーザ体験には影響はないはずです。Aqueductの新しい管理及びデバッギングコマンドについては、「[コマンドラインユーティリティ](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-aqueduct)」を参照してください。' + - + heading: トークンの変更 + notes: + - | + {% data variables.product.product_name %}のための認証トークンのフォーマットは変更されました。この変更は、個人アクセストークンのフォーマットと、{% data variables.product.prodname_oauth_apps %}のためのアクセストークンとともに、{% data variables.product.prodname_github_apps %}のためのuser-to-server、server-to-server、リフレッシュトークンに影響します。 + + 様々なトークンの種類は、一意の特定可能なプレフィックスを持つようになったので、Secret scanningにそれらのトークンを検出してもらい、誰かがうっかりトークンをリポジトリにコミットしてしまった場合のインパクトを緩和できます。{% data variables.product.company_short %}は、既存のトークンをできるだけ早く更新することをおすすめします。詳しい情報については「[{% data variables.product.prodname_dotcom %}での認証について](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github#githubs-token-formats)」及び「[{% data variables.product.prodname_secret_scanning %}について](/code-security/secret-security/about-secret-scanning)を参照してください。 + - + heading: 'リポジトリの変更' + notes: + - ユーザプロフィールとOrganizationプロフィール上のリポジトリは、Star数でのソートをサポートするようになりました。 + - 1つのファイルのコミット履歴を表示させている場合、{% octicon "file-code" aria-label="The code icon" %}をクリックして履歴中の選択した時点でのそのファイルを表示できるようになりました。 + - サブモジュールが{% data variables.product.product_location %}中で相対パスで定義されている場合、そのサブモジュールがWeb UI中でクリックできるようになりました。Web UIでサブモジュールをクリックすると、リンクしたリポジトリに行くことができます。以前は、絶対URLのサブモジュールだけがクリック可能でした。これは、同じオーナーの../REPOSITORYというパターンに従うリポジトリの相対パスか、異なるオーナーの../OWNER/REPOSITORYというパターンに従うリポジトリの相対パスでサポートされています。サブモジュールの扱いに関する詳しい情報については、{% data variables.product.prodname_blog %}の[サブモジュールの扱い](https://github.blog/2016-02-01-working-with-submodules/)を参照してください。 + - 'Web UIを使用して、古くなったフォークを上流のブランチと同期できるようになりました。ブランチ間でマージコンフリクトがない場合、ブランチはfast-forwardingもしくは上流からのマージによって更新されます。コンフリクトがある場合、そのコンフリクトを解決するためのPull Requestの作成が求められます。詳しい情報については「[フォークの同期](/github/collaborating-with-pull-requests/working-with-forks/syncing-a-fork#syncing-a-fork-from-the-web-ui)」を参照してください。' + - + heading: 'Markdownの変更' + notes: + - 'The markdown editor used when creating or editing a release in a repository now has a text-editing toolbar. For more information, see "[Managing releases in a repository](/github/administering-a-repository/releasing-projects-on-github/managing-releases-in-a-repository#creating-a-release)."' + - Uploading video files is now supported everywhere you write Markdown on {% data variables.product.product_name %}. Share demos, reproduction steps, and more in your issue and pull request comments, as well as in Markdown files within repositories, such as READMEs. For more information, see "[Attaching files](/github/writing-on-github/working-with-advanced-formatting/attaching-files)." + - Markdown files will now automatically generate a table of contents in the header when there are 2 or more headings. The table of contents is interactive and links to the selected section. All 6 Markdown heading levels are supported. + - 'There is a new keyboard shortcut, `cmd+e` on macOS or `ctrl+e` on Windows, to insert codeblocks in Markdown files, issues, pull requests, and comments.' + - 'Appending `?plain=1` to the URL for any Markdown file will now display the file without rendering and with line numbers. The plain view can be used to link other users to specific lines. For example, appending `?plain=1#L52` will highlight line 52 of a plain text Markdown file. For more information, "[Creating a permanent link to a code snippet](/github/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet#linking-to-markdown)."' + - + heading: 'Issues and pull requests changes' + notes: + - With the [latest version of Octicons](https://github.com/primer/octicons/releases), the states of issues and pull requests are now more visually distinct so you can scan their status more easily. For more information, see [{% data variables.product.prodname_blog %}](https://github.blog/changelog/2021-06-08-new-issue-and-pull-request-state-icons/). + - 'A new "Require conversation resolution before merging" branch protection rule and "Conversations" menu is now available. Easily discover your pull request comments from the "Files changed" tab, and require that all your pull request conversations are resolved before merging. For more information, see "[About pull request reviews](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews#discovering-and-navigating-conversations)" and "[About protected branches](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-conversation-resolution-before-merging)."' + - To prevent the merge of unexpected changes after auto-merge is enabled for a pull request, auto-merge is now disabled automatically when new changes are pushed by a user without write access to the repository. Users without write access can still update the pull request with changes from the base branch when auto-merge is enabled. To prevent a malicious user from using a merge conflict to introduce unexpected changes to the pull request, auto-merge for the pull request is disabled if the update causes a merge conflict. For more information about auto-merge, see "[Automatically merging a pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." + - 'People with maintain permissions 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 permissions 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. + - When a review is requested from a team of more than 100 people, developers are now shown a confirmation dialog box in order to prevent unnecessary notifications for large teams. + - Back-tick `code blocks` are now supported in issue titles, pull request titles, and in any place issue and pull request titles are referenced in {% data variables.product.prodname_ghe_server %}. + - 'Events for pull requests and pull request reviews are now included in the audit log for both [enterprises](/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise) and [organizations](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization). These events help admins better monitor pull request activity and help ensure security and compliance requirements are being met. Events can be viewed from the web UI, exported as CSV or JSON, or accessed via REST API. You can also search the audit log for specific pull request events. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#pull_request-category-actions)."' + - + heading: 'Branches changes' + notes: + - | + The default branch name for new repositories is now `main`. Existing repositories are not impacted by this change. If users, organization owners, or enterprise owners have previously specified a default branch for new repositories, they are also not impacted. + + If you want to set a different default branch name, you can do so in the [user](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories), [organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization), or [enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name) settings. + - | + Branches, including the default branch, can now be renamed using the the {% data variables.product.product_name %} web UI. When a branch is renamed, any open pull requests and draft releases targeting the renamed branch will be retargeted automatically, and branch protection rules that explicitly reference the renamed branch will be updated. + + Admin permissions are required to rename the default branch, but write permissions are sufficient to rename other branches. + + To help make the change as seamless as possible for users: + + * A notice is shown to contributors, maintainers, and admins on the repository homepage with instructions for updating their local repository. + * Web requests to the old branch will be redirected. + * A "moved permanently" HTTP response will be returned to REST API calls. + * An informational message is displayed to Git command line users that push to the old branch. + + For more information, see "[Renaming a branch](/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch)." + - + heading: 'GitHub Actions changes' + notes: + - '{% data variables.product.prodname_actions %} now lets you control the permissions granted to the `GITHUB_TOKEN` secret. The `GITHUB_TOKEN` is an automatically-generated secret that lets you make authenticated calls to the API for {% data variables.product.product_name %} in your workflow runs. {% data variables.product.prodname_actions %} generates a new token for each job and expires the token when a job completes. The token usually has `write` permissions to a number of [API endpoints](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token), except in the case of pull requests from forks, which are always `read`. These new settings allow you to follow a principle of least privilege in your workflows. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token)."' + - '{% data variables.product.prodname_cli %} 1.9 and later allows you to work with {% data variables.product.prodname_actions %} in your terminal. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-04-15-github-cli-1-9-enables-you-to-work-with-github-actions-from-your-terminal/).' + - 'The audit log now includes events associated with {% data variables.product.prodname_actions %} workflow runs. This data provides administrators with a greatly expanded data set for security and compliance audits. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#workflows-category-actions)."' + - '{% data variables.product.prodname_ghe_server %} 3.2 contains performance improvements for job concurrency with {% data variables.product.prodname_actions %}. For more information on the new performance targets on 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)."' + - + heading: 'GitHub Packages changes' + notes: + - Any package or package version for {% data variables.product.prodname_registry %} can now be deleted from {% data variables.product.product_name %}'s web UI. You can also undo the deletion of any package or package version within 30 days. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)". + - + heading: 'Dependabot and Dependency graph changes' + notes: + - 'The dependency graph can now be enabled using the Management Console, rather than needing to run a command in the administrative shell. For more information, see "[Enabling alerts for vulnerable dependencies {% data variables.product.prodname_ghe_server %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server#enabling-the-dependency-graph-and-dependabot-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."' + - Notifications for multiple {% data variables.product.prodname_dependabot_alerts %} are now grouped together if they're discovered at the same time. This significantly reduces the volume of {% data variables.product.prodname_dependabot %} alert notifications that users receive. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-03-18-grouped-dependabot-alert-notifications/). + - 'Dependency graph and {% data variables.product.prodname_dependabot_alerts %} now support Go modules. {% data variables.product.prodname_ghe_server %} analyzes a repository''s `go.mod` files to understand the repository’s dependencies. Along with security advisories, the dependency graph provides the information needed to alert developers to vulnerable dependencies. For more information about enabling the dependency graph on private repositories, see "[Securing your repository](/code-security/getting-started/securing-your-repository#managing-the-dependency-graph)."' + - The default notification settings for security alerts have changed. Previously, if you had permission to view security alerts in a repository, you would receive notifications for that repository as long as your settings allowed for security alert notifications. Now, you must opt in to security alert notifications by watching the repository. You will be notified if you select `All Activity` or configure `Custom` to include `Security alerts`. All existing repositories will be automatically migrated to these new settings and you will continue to receive notifications; however, any new repositories will require opting-in by watching the repository. 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)" and "[Managing alerts from secret scanning](/code-security/secret-security/managing-alerts-from-secret-scanning)." + - + heading: 'Code scanning and secret scanning changes' + notes: + - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} now generates diagnostic information for all supported languages. This helps check the state of the created database to understand the status and quality of performed analysis. The diagnostic information is available starting in [version 2.5.6](https://github.com/github/codeql-cli-binaries/releases) of the [{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/). You can see the detailed diagnostic information in the {% data variables.product.prodname_actions %} logs for {% data variables.product.prodname_codeql %}. For more information, see "[Viewing code scanning logs](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs)."' + - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql_cli %} now supports analyzing several languages during a single build. This makes it easier to run code analysis to use CI/CD systems other than {% data variables.product.prodname_actions %}. The new mode of the `codeql database create` command is available starting [version 2.5.6](https://github.com/github/codeql-cli-binaries/releases) of the [{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/). For more information about setting this up, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-cli-in-your-ci-system)."' + - '{% data variables.product.prodname_code_scanning_capc %} alerts from all enabled tools are now shown in one consolidated list, so that you can easily prioritize across all alerts. You can view alerts from a specific tool by using the "Tool" filter, and the "Rule" and "Tag" filters will dynamically update based on your "Tool" selection.' + - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} now includes beta support for analyzing C++20 code. This is only available when building codebases with GCC on Linux. C++20 modules are not supported yet.' + - 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 for several languages ([C++](https://github.com/github/codeql/tree/main/cpp), [JavaScript](https://github.com/github/codeql/tree/main/javascript), [Python](https://github.com/github/codeql/tree/main/python), and [Java](https://github.com/github/codeql/tree/main/java)). As a result, {% data variables.product.prodname_codeql %} can now detect even more potential sources of untrusted user data, review the steps through which that data flows, and identify potentially dangerous sinks in which this data could end up. This results in an overall improvement of the quality of the {% data variables.product.prodname_code_scanning %} alerts. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-07-01-codeql-code-scanning-now-recognizes-more-sources-and-uses-of-untrusted-user-data/). + - | + {% data variables.product.prodname_code_scanning_capc %} now shows `security-severity` levels for CodeQL security alerts. You can configure which `security-severity` levels will cause a check failure for a pull request. The severity level of security alerts can be `critical`, `high`, `medium`, or `low`. By default, any {% data variables.product.prodname_code_scanning %} alerts with a `security-severity` of `critical` or `high` will cause a pull request check failure. + + Additionally, you can now also configure which severity levels will cause a pull request check to fail for non-security alerts. You can configure this behavior at the repository level, and define whether alerts with the severity `error`, `warning`, or `note` will cause a pull request check to fail. By default, non-security {% data variables.product.prodname_code_scanning %} alerts with a severity of `error` will cause a pull request check failure. + + For more information see "[Defining which alert severity levels cause pull request check failure](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)." + + ![List of code scanning alerts with security levels](/assets/images/enterprise/3.2/release-notes/code-scanning-alerts.png) + - | + Improvements to the branch filter for {% data variables.product.prodname_code_scanning %} alerts make it clearer which {% data variables.product.prodname_code_scanning %} alerts are being displayed on the alerts page. By default, {% data variables.product.prodname_code_scanning %} alerts are filtered to show alerts for the default branch of the repository only. You can use the branch filter to display the alerts on any of the non-default branches. Any branch filter that has been applied is shown in the search bar. + + The search syntax has also been simplified to `branch:`. This syntax can be used multiple times in the search bar to filter on multiple branches. The previous syntax, `ref:refs/heads/`, is still supported, so any saved URLs will continue to work. + - | + Free text search is now available for code scanning alerts. You can search code scanning results to quickly find specific alerts without having to know exact search terms. The search is applied across the alert's name, description, and help text. The syntax is: + + - A single word returns all matches. + - Multiple search words returns matches to either word. + - Words in double quotes returns exact matches. + - The keyword 'AND' returns matches to multiple words. + - '{% data variables.product.prodname_secret_scanning_caps %} added patterns for 23 new service providers. For the updated list of supported secrets, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning)."' + - + heading: API の変更 + notes: + - 'Pagination support has been added to the Repositories REST API''s "compare two commits" endpoint, which returns a list of commits reachable from one commit or branch, but unreachable from another. The API can also now return the results for comparisons over 250 commits. For more information, see the "[Repositories](/rest/reference/repos#compare-two-commits)" REST API documentation and "[Traversing with pagination](/rest/guides/traversing-with-pagination)."' + - 'The REST API can now be used to programmatically resend or check the status of webhooks. For more information, see "[Repositories](/rest/reference/repos#webhooks)," "[Organizations](/rest/reference/orgs#webhooks)," and "[Apps](/rest/reference/apps#webhooks)" in the REST API documentation.' + - | + Improvements have been made to the code scanning and {% data variables.product.prodname_GH_advanced_security %} APIs: + + - The code scanning API now returns the CodeQL query version used for an analysis. This can be used to reproduce results or confirm that an analysis used the latest query. For more information, see "[Code scanning](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository)" in the REST API documentation. + - Admin users can now use the REST API to enable or disable {% data variables.product.prodname_GH_advanced_security %} for repositories, using the `security_and_analysis` object on `repos/{org}/{repo}`. In addition, admin users can check whether {% data variables.product.prodname_advanced_security %} is currently enabled for a repository by using a `GET /repos/{owner}/{repo}` request. These changes help you manage {% data variables.product.prodname_advanced_security %} repository access at scale. For more information, see "[Repositories](/rest/reference/repos#update-a-repository)" in the REST API documentation. + #No security/bug fixes for the RC release + #security_fixes: + #- PLACEHOLDER + #bugs: + #- PLACEHOLDER + 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 フックに失敗するものが生じることがあります。 + deprecations: + - + heading: GitHub Enterprise Server 2.21の非推奨化 + notes: + - '**{% data variables.product.prodname_ghe_server %} 2.21 was discontinued on June 6, 2021**. That 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.2/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' + - + heading: Deprecation of GitHub Enterprise Server 2.22 + notes: + - '**{% data variables.product.prodname_ghe_server %} 2.22 will be discontinued on September 23, 2021**. That 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.2/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' + - + heading: XenServer Hypervisorサポートの非推奨化 + notes: + - Beginning in {% data variables.product.prodname_ghe_server %} 3.1, we will begin discontinuing support for Xen Hypervisor. The complete deprecation is scheduled for {% data variables.product.prodname_ghe_server %} 3.3, following the standard one year deprecation window. Please contact [GitHub Support](https://enterprise.githubsupport.com/hc/en-us/signin) with questions or concerns. + - + heading: Removal of Legacy GitHub Services + notes: + - '{% data variables.product.prodname_ghe_server %} 3.2 removes unused GitHub Service database records. More information is available in the [deprecation announcement post](https://developer.github.com/changes/2018-04-25-github-services-deprecation/).' + - + heading: Deprecation of OAuth Application API endpoints and API authentication via query parameters + notes: + - | + To prevent accidental logging or exposure of `access_tokens`, we discourage the use of OAuth Application API endpoints and the use of API auth via query params. Visit the following posts to see the proposed replacements: + + * [Replacement OAuth Application API endpoints](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#changes-to-make) + * [Replacement auth via headers instead of query param](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make) + + These endpoints and auth route are planned to be removed from {% data variables.product.prodname_ghe_server %} in {% data variables.product.prodname_ghe_server %} 3.4. + - + heading: Removal of legacy GitHub App webhook events and endpoints + notes: + - | + Two legacy GitHub Apps-related webhook events have been removed: `integration_installation` and `integration_installation_repositories`. You should instead be listening to the `installation` and `installation_repositories` events. + - | + The following REST API endpoint has been removed: `POST /installations/{installation_id}/access_tokens`. You should instead be using the namespaced equivalent `POST /app/installations/{installation_id}/access_tokens`. + backups: + - '{% data variables.product.prodname_ghe_server %} 3.2 requires at least [GitHub Enterprise Backup Utilities 3.2.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/enterprise-server@3.2/admin/configuration/configuring-backups-on-your-appliance).' diff --git a/translations/ja-JP/data/reusables/actions/about-environments.md b/translations/ja-JP/data/reusables/actions/about-environments.md new file mode 100644 index 0000000000..ab9cfa899f --- /dev/null +++ b/translations/ja-JP/data/reusables/actions/about-environments.md @@ -0,0 +1 @@ +Environments are used to describe a general deployment target like `production`, `staging`, or `development`. When a {% data variables.product.prodname_actions %} workflow deploys to an environment, the environment is displayed on the main page of the repository. You can use environments to require approval for a job to proceed, restrict which branches can trigger a workflow, or limit access to secrets. For more information about creating environments, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/actions/actions-group-concurrency.md b/translations/ja-JP/data/reusables/actions/actions-group-concurrency.md index 206728fd01..2c756b7b2e 100644 --- a/translations/ja-JP/data/reusables/actions/actions-group-concurrency.md +++ b/translations/ja-JP/data/reusables/actions/actions-group-concurrency.md @@ -1,6 +1,6 @@ 並行ジョブもしくはワークフローがキューに入っている場合、リポジトリ内の同じ並行グループを使う他のジョブもしくはワークフローが進行中だと、キューイングされたジョブもしくはワークフローは`保留中`になります。 この並行グループ内の以前の保留中のジョブもしくはワークフローは、キャンセルされます。 同じ並行グループ内にある実行中のジョブもしくはワークフローもキャンセルするには、`cancel-in-progress: true`を指定してください。 -### 並行性とデフォルトの動作の使用例 +## 並行性とデフォルトの動作の使用例 {% raw %} ```yaml @@ -14,7 +14,7 @@ concurrency: ci-${{ github.ref }} ``` {% endraw %} -### 並行性を使って進行中のジョブもしくは実行をキャンセルする例 +## 並行性を使って進行中のジョブもしくは実行をキャンセルする例 {% raw %} ```yaml diff --git a/translations/ja-JP/data/reusables/actions/ae-hosted-runners-beta.md b/translations/ja-JP/data/reusables/actions/ae-hosted-runners-beta.md new file mode 100644 index 0000000000..804f22a849 --- /dev/null +++ b/translations/ja-JP/data/reusables/actions/ae-hosted-runners-beta.md @@ -0,0 +1,7 @@ +{% ifversion ghae %} +{% note %} + +**Note:** {% data variables.actions.hosted_runner %}s are currently in beta and subject to change. + +{% endnote %} +{% endif %} diff --git a/translations/ja-JP/data/reusables/actions/ae-self-hosted-runners-notice.md b/translations/ja-JP/data/reusables/actions/ae-self-hosted-runners-notice.md index 0d13b92873..142f059372 100644 --- a/translations/ja-JP/data/reusables/actions/ae-self-hosted-runners-notice.md +++ b/translations/ja-JP/data/reusables/actions/ae-self-hosted-runners-notice.md @@ -1,9 +1,19 @@ {% ifversion ghae %} + {% warning %} -** 警告:** セルフホストランナーは、現在{% data variables.product.prodname_ghe_managed %}で無効になっています。 これは、{% data variables.product.prodname_ghe_managed %}がセルフホストランナーの動作と互換性のないセキュリティ境界を保証しているためです。 ただし、{% data variables.product.prodname_ghe_managed %}でセルフホストランナーを使う必要があり、セキュリティへの影響を理解しているなら、セルフホストランナーを有効化するセキュリティ例外について{% data variables.product.prodname_dotcom %}サポートに連絡できます。 +{% ifversion ghae-next %} + +**Warning:** Self-hosted runners are enabled by default for {% data variables.product.prodname_ghe_managed %}. Self-hosted runners are long-lived, and any compromise to the host machine could leak secrets or credentials or enable other attacks. If you'd like to disable self-hosted runners for your enterprise, you can contact {% data variables.product.prodname_dotcom %} support. For more information about the risks of using self-hosted runners, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/security-hardening-for-github-actions#potential-impact-of-a-compromised-runner)." + +{% elsif ghae %} + +**Warning:** Self-hosted runners are currently disabled for {% data variables.product.prodname_ghe_managed %}. これは、{% data variables.product.prodname_ghe_managed %}がセルフホストランナーの動作と互換性のないセキュリティ境界を保証しているためです。 ただし、{% data variables.product.prodname_ghe_managed %}でセルフホストランナーを使う必要があり、セキュリティへの影響を理解しているなら、セルフホストランナーを有効化するセキュリティ例外について{% data variables.product.prodname_dotcom %}サポートに連絡できます。 セルフホストランナーが必要ないなら、ワークフローの実行には{% data variables.actions.hosted_runner %}が利用できます。 詳しい情報については「[{% data variables.actions.hosted_runner %}について](/actions/using-github-hosted-runners/about-ae-hosted-runners)」を参照してください。 -{% endwarning %} +{% endif %} + +{% endwarning %} + {% endif %} 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 e70c956db6..6ac256f0bb 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 @@ -1,7 +1,7 @@ **Allow select actions（アクションの選択を許可）**を選択すると、ローカルアクションが許可され、他の特定のアクションを許可するための追加のオプションがあります。 -- **Allow actions created by {% data variables.product.prodname_dotcom %}（{% data variables.product.prodname_dotcom %}が作成したアクションのを許可）:** {% data variables.product.prodname_dotcom %}が作成したすべてのアクションをワークフローから使うことを許可できます。 {% data variables.product.prodname_dotcom %}が作成したアクションは、`actions`及び`github` Organizationにあります。 For more information, see the [`actions`](https://github.com/actions) and [`github`](https://github.com/github) organizations.{% ifversion fpt or ghes > 3.0 %} -- **Allow Marketplace actions by verified creators:** {% ifversion ghes > 3.0 %}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 %}（{% data variables.product.prodname_dotcom %}が作成したアクションのを許可）:** {% data variables.product.prodname_dotcom %}が作成したすべてのアクションをワークフローから使うことを許可できます。 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 > 3.0 or ghae-issue-5094 %} +- **Allow Marketplace actions by verified creators:** {% ifversion ghes > 3.0 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 specified actions（指定したアクションの許可）:** ワークフローから利用できるのを特定のOrganizationやリポジトリ内のアクションに限定できます。 アクションの特定のタグあるいはコミットSHAにアクセスを制限するには、アクションを選択するためにワークフローで使われる野と同じ`/@`構文を使ってください。 たとえばタグを選択するために`actions/javascript-action@v1.0.1`、あるいはSHAを選択するために`actions/javascript-action@172239021f7ba04fe7327647b213799853a9eb89`というようにします。 詳しい情報については「[アクションの発見とカスタマイズ](/actions/learn-github-actions/finding-and-customizing-actions#using-release-management-for-your-custom-actions)」を参照してください。 diff --git a/translations/ja-JP/data/reusables/actions/autoscaling-parameters.md b/translations/ja-JP/data/reusables/actions/autoscaling-parameters.md new file mode 100644 index 0000000000..d9c4342b29 --- /dev/null +++ b/translations/ja-JP/data/reusables/actions/autoscaling-parameters.md @@ -0,0 +1,3 @@ +- Optionally, autoscaling parameters for each pool. + - Minimum number of idle runners for the pool + - Active timeout: The number of minutes that a runner should remain active in the pool before the pool is reduced to the idle count diff --git a/translations/ja-JP/data/reusables/actions/cd-templates-actions.md b/translations/ja-JP/data/reusables/actions/cd-templates-actions.md new file mode 100644 index 0000000000..c6eeec90db --- /dev/null +++ b/translations/ja-JP/data/reusables/actions/cd-templates-actions.md @@ -0,0 +1,3 @@ +{% data variables.product.product_name %} offers CD workflow templates for several popular services, such as Azure Web App. To learn how to get started using a workflow template, see "[Using workflow templates](/actions/learn-github-actions/using-workflow-templates)" or [browse the full list of deployment workflow templates](https://github.com/actions/starter-workflows/tree/main/deployments). You can also check out our more detailed guides for specific deployment workflows, such as "[Deploying to Azure App Service](/actions/deployment/deploying-to-azure-app-service)." + +Many service providers also offer actions on {% data variables.product.prodname_marketplace %} for deploying to their service. For the full list, see [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?category=deployment&type=actions). \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/actions/delete-env-key.md b/translations/ja-JP/data/reusables/actions/delete-env-key.md new file mode 100644 index 0000000000..380ebe5653 --- /dev/null +++ b/translations/ja-JP/data/reusables/actions/delete-env-key.md @@ -0,0 +1 @@ +If you configured a deployment environment, change the value of `environment` to be the name of your environment. If you did not configure an environment{% ifversion fpt %} or if your workflow is in a private repository and you do not use {% data variables.product.prodname_ghe_cloud %}{% endif %}, delete the `environment` key. \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/actions/environment-deployment-event.md b/translations/ja-JP/data/reusables/actions/environment-deployment-event.md new file mode 100644 index 0000000000..1a014fbfc6 --- /dev/null +++ b/translations/ja-JP/data/reusables/actions/environment-deployment-event.md @@ -0,0 +1 @@ +When a workflow job that references an environment runs, it creates a deployment object with the `environment` property set to the name of your environment. As the workflow progresses, it also creates deployment status objects with the `environment` property set to the name of your environment, the `environment_url` property set to the URL for environment (if specified in the workflow), and the `state` property set to the status of the job. \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/actions/environment-example.md b/translations/ja-JP/data/reusables/actions/environment-example.md new file mode 100644 index 0000000000..95ed6bc816 --- /dev/null +++ b/translations/ja-JP/data/reusables/actions/environment-example.md @@ -0,0 +1,45 @@ +You can specify an environment for each job in your workflow. To do so, add a `jobs..environment` key followed by the name of the environment. + +For example, this workflow will use an environment called `production`. + +```yaml +name: Deployment + +on: + push: + branches: + - main + +jobs: + deployment: + runs-on: ubuntu-latest + environment: production + steps: + - name: deploy + # ...deployment-specific steps +``` + +When the above workflow runs, the `deployment` job will be subject to any rules configured for the `production` environment. For example, if the environment requires reviewers, the job will pause until one of the reviewers approves the job. + +You can also specify a URL for the environment. The specified URL will appear on the deployments page for the repository (accessed by clicking **Environments** on the home page of your repository) and in the visualization graph for the workflow run. If a pull request triggered the workflow, the URL is also displayed as a **View deployment** button in the pull request timeline. + +```yaml +name: Deployment + +on: + push: + branches: + - main + +jobs: + deployment: + runs-on: ubuntu-latest + environment: + name: production + url: https://github.com + steps: + - name: deploy + # ...deployment-specific steps +``` + +![Workflow graph with URL](/assets/images/help/images/deploy-graph.png) \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/actions/reusable-workflow-artifacts.md b/translations/ja-JP/data/reusables/actions/reusable-workflow-artifacts.md new file mode 100644 index 0000000000..4f5210333f --- /dev/null +++ b/translations/ja-JP/data/reusables/actions/reusable-workflow-artifacts.md @@ -0,0 +1,3 @@ +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +All actions and workflows called within a run have write access to that run's artifacts. +{% endif %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/actions/reusable-workflows.md b/translations/ja-JP/data/reusables/actions/reusable-workflows.md new file mode 100644 index 0000000000..377f69ce32 --- /dev/null +++ b/translations/ja-JP/data/reusables/actions/reusable-workflows.md @@ -0,0 +1,5 @@ +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## Reusing workflows + +You can call one workflow from within another workflow. This allows you to reuse workflows, avoiding duplication and making your workflows easier to maintain. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." +{% endif %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/actions/runner-name-description.md b/translations/ja-JP/data/reusables/actions/runner-name-description.md new file mode 100644 index 0000000000..c3955e46ec --- /dev/null +++ b/translations/ja-JP/data/reusables/actions/runner-name-description.md @@ -0,0 +1 @@ +The name of the runner executing the job. diff --git a/translations/ja-JP/data/reusables/actions/uses-keyword-example.md b/translations/ja-JP/data/reusables/actions/uses-keyword-example.md new file mode 100644 index 0000000000..fac21c8a9f --- /dev/null +++ b/translations/ja-JP/data/reusables/actions/uses-keyword-example.md @@ -0,0 +1,7 @@ +```yaml +jobs: + call-workflow-1: + uses: octo-org/this-repo/.github/workflows/workflow-1.yml@172239021f7ba04fe7327647b213799853a9eb89 + call-workflow-2: + uses: octo-org/another-repo/.github/workflows/workflow-2.yml@v1 +``` \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/actions/workflow-organization-templates.md b/translations/ja-JP/data/reusables/actions/workflow-organization-templates.md new file mode 100644 index 0000000000..429154a991 --- /dev/null +++ b/translations/ja-JP/data/reusables/actions/workflow-organization-templates.md @@ -0,0 +1 @@ +Workflow templates allow everyone in your organization who has permission to create workflows to do so more quickly and easily. When you create a new workflow, you can choose a template and some or all of the work of writing the workflow will be done for you. ワークフローテンプレートは、カスタムワークフローの構築の出発点として利用することも、そのまま利用することもできます。 This not only saves time, it promotes consistency and best practice across your organization. \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/actions/workflow-run-approve-public-fork.md b/translations/ja-JP/data/reusables/actions/workflow-run-approve-public-fork.md index d325b96ec8..4cf445d072 100644 --- a/translations/ja-JP/data/reusables/actions/workflow-run-approve-public-fork.md +++ b/translations/ja-JP/data/reusables/actions/workflow-run-approve-public-fork.md @@ -1,3 +1,9 @@ パブリックリポジトリをフォークし、リポジトリの{% data variables.product.prodname_actions %}ワークフローへの変更を提案するPull Requestをサブミットすることは誰でもできます。 フォークからのワークフローはシークレットなどの機密データにアクセスできませんが、悪用目的で変更された場合、メンテナが迷惑を被る可能性があります。 これを防ぐために、外部コラボレータのパブリックリポジトリへのPull Requestではワークフローは自動的には動作せず、まず承認が必要になることがあります。 デフォルトでは、すべての初めてのコントリビューターは、ワークフローを実行するのに承認を必要とします。 + +{% note %} + +**Note:** Workflows triggered by `pull_request_target` events are run in the context of the base branch. Since the base branch is considered trusted, workflows triggered by these events will always run, regardless of approval settings. + +{% endnote %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/apps/oauth-auth-vary-response.md b/translations/ja-JP/data/reusables/apps/oauth-auth-vary-response.md new file mode 100644 index 0000000000..b76fef614b --- /dev/null +++ b/translations/ja-JP/data/reusables/apps/oauth-auth-vary-response.md @@ -0,0 +1 @@ +You can also receive the response in different formats if you provide the format in the `Accept` header. For example, `Accept: application/json` or `Accept: application/xml`: diff --git a/translations/ja-JP/data/reusables/code-scanning/upload-sarif-alert-limit.md b/translations/ja-JP/data/reusables/code-scanning/upload-sarif-alert-limit.md index b36e2995fe..79905c3f8e 100644 --- a/translations/ja-JP/data/reusables/code-scanning/upload-sarif-alert-limit.md +++ b/translations/ja-JP/data/reusables/code-scanning/upload-sarif-alert-limit.md @@ -1,5 +1,8 @@ {% note %} -**ノート:** SARIFのアップロードは、アップロードごとに最大で{% ifversion ghae-next or fpt or ghes > 3.0 %}5000{% else %}1000{% endif %}件の結果をサポートしています。 この制限を超えた結果は無視されます。 ツールがあまりに多くの結果を生成する場合、最も重要なルールやクエリに対する結果に焦点を当てるよう、設定を更新すべきです。 +**ノート:** +- SARIF upload supports a maximum of {% ifversion ghae-next or fpt or ghes > 3.0 %}5000{% else %}1000{% endif %} results per upload. この制限を超えた結果は無視されます。 ツールがあまりに多くの結果を生成する場合、最も重要なルールやクエリに対する結果に焦点を当てるよう、設定を更新すべきです。 + + - For each upload, SARIF upload supports a maximum size of 10 MB for the `gzip`-compressed SARIF file. Any uploads over this limit will be rejected. If your SARIF file is too large because it contains too many results, you should update the configuration to focus on results for the most important rules or queries. {% endnote %} diff --git a/translations/ja-JP/data/reusables/codespaces/create-or-switch-branch.md b/translations/ja-JP/data/reusables/codespaces/create-or-switch-branch.md new file mode 100644 index 0000000000..7844333dd8 --- /dev/null +++ b/translations/ja-JP/data/reusables/codespaces/create-or-switch-branch.md @@ -0,0 +1,3 @@ +1. 現在のブランチがステータスバーに表示されていない場合は、codespace の下部でステータスバーを右クリックし、[**Source control**] を選択します。 +1. ステータスバーでブランチ名をクリックします。 ![ステータスバーにあるブランチ](/assets/images/help/codespaces/branch-in-status-bar.png) +1. ドロップダウンで、切り替えるブランチをクリックするか、新しいブランチ名を入力して [**Create new branch**] をクリックします。 ![ブランチメニューから選択](/assets/images/help/codespaces/create-new-branch.png) \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/codespaces/source-control-commit-changes.md b/translations/ja-JP/data/reusables/codespaces/source-control-commit-changes.md new file mode 100644 index 0000000000..85eded2621 --- /dev/null +++ b/translations/ja-JP/data/reusables/codespaces/source-control-commit-changes.md @@ -0,0 +1,4 @@ +{% data reusables.codespaces.source-control-display-dark %} +1. 変更をステージングするには、変更したファイルの隣にある [**+**] をクリックするか、複数のファイルを変更してすべてをステージングする場合は [**Changes**] の隣をクリックします。 ![ステージングボタンが強調表示されたソースコントロールサイドバー](/assets/images/help/codespaces/codespaces-commit-stage.png) +1. 行った変更について説明するコミットメッセージを入力します。 ![コミットメッセージがあるソースコントロールサイドバー](/assets/images/help/codespaces/codespaces-commit-commit-message.png) +1. ステージングされた変更をコミットするには、ソースコントロールサイドバーの上部にあるチェックマークをクリックします。 ![チェックマークアイコンをクリックする](/assets/images/help/codespaces/codespaces-commit-checkmark-icon.png) \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/codespaces/source-control-pull-request.md b/translations/ja-JP/data/reusables/codespaces/source-control-pull-request.md new file mode 100644 index 0000000000..9f7f05ec30 --- /dev/null +++ b/translations/ja-JP/data/reusables/codespaces/source-control-pull-request.md @@ -0,0 +1,3 @@ +1. リポジトリのローカルコピーに変更をコミットしてから、[**Create Pull Request**] アイコンをクリックします。 ![ステージングボタンが強調表示されたソースコントロールサイドバー](/assets/images/help/codespaces/codespaces-commit-pr-button.png) +1. マージ元のローカルブランチとリポジトリ、およびマージ先のリモートブランチとリポジトリが正しいことを確認します。 そして、プルリクエストにタイトルと説明を付けます。 ![ステージングボタンが強調表示されたソースコントロールサイドバー](/assets/images/help/codespaces/codespaces-commit-pr.png) +1. ** Create（作成）**をクリックしてください。 \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/dependabot/supported-package-managers.md b/translations/ja-JP/data/reusables/dependabot/supported-package-managers.md index 92713d21e8..552e8be437 100644 --- a/translations/ja-JP/data/reusables/dependabot/supported-package-managers.md +++ b/translations/ja-JP/data/reusables/dependabot/supported-package-managers.md @@ -26,7 +26,7 @@ | Terraform | `terraform` | >= 0.13, <= 1.0 | **✓** | **✓** | | | yarn | `npm` | v1 | **✓** | **✓** | | -[1] {% data variables.product.prodname_dependabot %}はGradleを実行しませんが、`build.gradle`及び`build.gradle.kts`（Kotlinのプロジェクトの場合）という2つのファイルの更新はサポートしています。 +[1] {% data variables.product.prodname_dependabot %} doesn't run Gradle but supports updates to the following files: `build.gradle`, `build.gradle.kts` (for Kotlin projects), and files included via the `apply` declaration that have `dependencies` in the filename. Note that `apply` does not support `apply to`, recursion, or advanced syntaxes (for example, Kotlin's `apply` with `mapOf`, filenames defined by property). [2] {% data variables.product.prodname_dependabot %}はMavenを実行しませんが、`pom.xml`ファイルの更新はサポートします。 diff --git a/translations/ja-JP/data/reusables/dependency-review/beta.md b/translations/ja-JP/data/reusables/dependency-review/beta.md index d2d0ce3e3e..749601f15a 100644 --- a/translations/ja-JP/data/reusables/dependency-review/beta.md +++ b/translations/ja-JP/data/reusables/dependency-review/beta.md @@ -1,7 +1,8 @@ -{% ifversion fpt or ghes > 3.1 %} +{% ifversion ghes > 3.1 %} {% note %} **注釈:** 依存関係のレビューは現在ベータであり、変更される可能性があります。 {% endnote %} + {% endif %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/developer-site/pull_request_forked_repos_link.md b/translations/ja-JP/data/reusables/developer-site/pull_request_forked_repos_link.md index f5d89ed503..2f91203e7b 100644 --- a/translations/ja-JP/data/reusables/developer-site/pull_request_forked_repos_link.md +++ b/translations/ja-JP/data/reusables/developer-site/pull_request_forked_repos_link.md @@ -1,4 +1,4 @@ -#### フォークしたリポジトリのPull Requestイベント +### フォークしたリポジトリのPull Requestイベント {% note %} diff --git a/translations/ja-JP/data/reusables/dotcom_billing/pricing_cal.md b/translations/ja-JP/data/reusables/dotcom_billing/pricing_cal.md new file mode 100644 index 0000000000..6509379b28 --- /dev/null +++ b/translations/ja-JP/data/reusables/dotcom_billing/pricing_cal.md @@ -0,0 +1 @@ +To estimate the costs for consumptive services, you can use the {% data variables.product.prodname_dotcom %} pricing calculator. For more information, go to https://github.com/pricing/calculator. diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/about-enterprise-accounts.md b/translations/ja-JP/data/reusables/enterprise-accounts/about-enterprise-accounts.md index 44bf1dfcf3..b96a63e8d7 100644 --- a/translations/ja-JP/data/reusables/enterprise-accounts/about-enterprise-accounts.md +++ b/translations/ja-JP/data/reusables/enterprise-accounts/about-enterprise-accounts.md @@ -14,7 +14,7 @@ Organizations are shared accounts where enterprise members can collaborate acros {% ifversion fpt %} -Enterprise owners can create organizations and link the organizations to the enterprise. After you add organizations to your enterprise account, you can manage and enforce policies for the organizations. 特定の強制の選択肢は、設定によって異なります。概して、Enterprise アカウント内のすべての Organization に単一のポリシーを強制するか、Organization レベルでオーナーがポリシーを設定することを許可するかを選択できます。 For more information, see "[Setting policies for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account)." +Enterprise owners can create organizations and link the organizations to the enterprise. Alternatively, you can invite an existing organization to join your enterprise. After you add organizations to your enterprise account, you can manage and enforce policies for the organizations. 特定の強制の選択肢は、設定によって異なります。概して、Enterprise アカウント内のすべての Organization に単一のポリシーを強制するか、Organization レベルでオーナーがポリシーを設定することを許可するかを選択できます。 For more information, see "[Setting policies for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account)." {% elsif ghes or ghae %} @@ -58,6 +58,14 @@ You can also connect the enterprise account on {% data variables.product.product {% endif %} +{% ifversion fpt %} + +## {% data variables.product.prodname_emus %}について + +{% data reusables.enterprise-accounts.emu-short-summary %} + +{% endif %} + ## About billing for your enterprise account The bill for your enterprise account includes the monthly cost for each member of your enterprise. The bill includes {% ifversion fpt %}any paid licenses in organizations outside of your enterprise account, subscriptions to apps in {% data variables.product.prodname_marketplace %}, {% endif %}{% ifversion fpt or ghae %}additional paid services for your enterprise{% ifversion fpt %} like data packs for {% data variables.large_files.product_name_long %},{% endif %} and{% endif %} usage for {% data variables.product.prodname_GH_advanced_security %}. diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/access-enterprise.md b/translations/ja-JP/data/reusables/enterprise-accounts/access-enterprise.md index ba426b4ad0..b6830ebe1c 100644 --- a/translations/ja-JP/data/reusables/enterprise-accounts/access-enterprise.md +++ b/translations/ja-JP/data/reusables/enterprise-accounts/access-enterprise.md @@ -5,5 +5,4 @@ {% elsif ghes or ghae %}1. {% data variables.product.product_name %}の右上で、プロフィール写真をクリックし、続いて**Enterprise settings（Enterpriseの設定）**をクリックしてください。 ![{% data variables.product.product_name %}のプロフィール写真のドロップダウンメニュー内の"Enterprise settings"](/assets/images/enterprise/settings/enterprise-settings.png) - {% endif %} diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/actions-runners-tab.md b/translations/ja-JP/data/reusables/enterprise-accounts/actions-runners-tab.md index 4cf1a69bb0..d39f4fcaeb 100644 --- a/translations/ja-JP/data/reusables/enterprise-accounts/actions-runners-tab.md +++ b/translations/ja-JP/data/reusables/enterprise-accounts/actions-runners-tab.md @@ -1 +1 @@ -1. {% ifversion fpt %}**Runners（ランナー）**{% else %}**Self-hosted runners（セルフホストランナー）**{% endif %}タブをクリックしてください。 +1. {% ifversion fpt or ghes > 3.1 or ghae-next %}**Runners（ランナー）**{% else %}**Self-hosted runners（セルフホストランナー）**{% endif %}タブをクリックしてください。 diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/emu-forks.md b/translations/ja-JP/data/reusables/enterprise-accounts/emu-forks.md new file mode 100644 index 0000000000..315ee2736f --- /dev/null +++ b/translations/ja-JP/data/reusables/enterprise-accounts/emu-forks.md @@ -0,0 +1 @@ +{% data variables.product.prodname_managed_users_caps %} cannot fork repositories from outside of the enterprise or fork internal repositories. {% data variables.product.prodname_managed_users_caps %} can fork private repositories owned by organizations in the enterprise into other organizations owned by the enterprise, or as a fork owned by the {% data variables.product.prodname_managed_user %}. \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/emu-more-info-account.md b/translations/ja-JP/data/reusables/enterprise-accounts/emu-more-info-account.md new file mode 100644 index 0000000000..21302799fb --- /dev/null +++ b/translations/ja-JP/data/reusables/enterprise-accounts/emu-more-info-account.md @@ -0,0 +1 @@ +For more information, see "[Types of GitHub accounts](/get-started/learning-about-github/types-of-github-accounts#enterprise-managed-users)." \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/emu-password-reset-session.md b/translations/ja-JP/data/reusables/enterprise-accounts/emu-password-reset-session.md new file mode 100644 index 0000000000..65ed74cc65 --- /dev/null +++ b/translations/ja-JP/data/reusables/enterprise-accounts/emu-password-reset-session.md @@ -0,0 +1 @@ +If you need to reset the password for your setup user, use an incognito or private browsing window to request a new password. When the email arrives with the link to reset your password, copy the link into your browser. For more information on resetting your password, see "[Requesting a new password ](/github/authenticating-to-github/keeping-your-account-and-data-secure/updating-your-github-access-credentials#requesting-a-new-password)." \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/emu-permission-follow.md b/translations/ja-JP/data/reusables/enterprise-accounts/emu-permission-follow.md new file mode 100644 index 0000000000..f166721634 --- /dev/null +++ b/translations/ja-JP/data/reusables/enterprise-accounts/emu-permission-follow.md @@ -0,0 +1 @@ +{% ifversion fpt %} Members of an {% data variables.product.prodname_emu_enterprise %} can only follow other members of their enterprise. {% endif %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/emu-permission-fork.md b/translations/ja-JP/data/reusables/enterprise-accounts/emu-permission-fork.md new file mode 100644 index 0000000000..411dfeed7b --- /dev/null +++ b/translations/ja-JP/data/reusables/enterprise-accounts/emu-permission-fork.md @@ -0,0 +1 @@ +{% ifversion fpt %}Members of an {% data variables.product.prodname_emu_enterprise %} cannot fork repositories from outside of the enterprise or fork internal repositories.{% endif %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/emu-permission-gist.md b/translations/ja-JP/data/reusables/enterprise-accounts/emu-permission-gist.md new file mode 100644 index 0000000000..3164ea3434 --- /dev/null +++ b/translations/ja-JP/data/reusables/enterprise-accounts/emu-permission-gist.md @@ -0,0 +1 @@ +{% ifversion fpt %}Members of an {% data variables.product.prodname_emu_enterprise %} cannot create gists and have read-only access to gists.{% endif %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/emu-permission-interact.md b/translations/ja-JP/data/reusables/enterprise-accounts/emu-permission-interact.md new file mode 100644 index 0000000000..9bdeac19e8 --- /dev/null +++ b/translations/ja-JP/data/reusables/enterprise-accounts/emu-permission-interact.md @@ -0,0 +1 @@ +{% ifversion fpt %} Members of an {% data variables.product.prodname_emu_enterprise %} can only interact with repositories within their enterprise. {% endif %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/emu-permission-propose.md b/translations/ja-JP/data/reusables/enterprise-accounts/emu-permission-propose.md new file mode 100644 index 0000000000..85fd4f66e3 --- /dev/null +++ b/translations/ja-JP/data/reusables/enterprise-accounts/emu-permission-propose.md @@ -0,0 +1 @@ +{% ifversion fpt %} Members of an {% data variables.product.prodname_emu_enterprise %} can only propose changes in repositories that are part of their enterprise. {% endif %} diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/emu-permission-repo.md b/translations/ja-JP/data/reusables/enterprise-accounts/emu-permission-repo.md new file mode 100644 index 0000000000..b4278362a5 --- /dev/null +++ b/translations/ja-JP/data/reusables/enterprise-accounts/emu-permission-repo.md @@ -0,0 +1 @@ +{% ifversion fpt %} Members of an {% data variables.product.prodname_emu_enterprise %} can only make changes in repositories that are part of their enterprise. {% endif %} diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/emu-saml-note.md b/translations/ja-JP/data/reusables/enterprise-accounts/emu-saml-note.md new file mode 100644 index 0000000000..2a5bdae038 --- /dev/null +++ b/translations/ja-JP/data/reusables/enterprise-accounts/emu-saml-note.md @@ -0,0 +1,7 @@ +{% ifversion fpt%} +{% note %} + +**Note**: If your enterprise uses {% data variables.product.prodname_emus %}, you must follow a different process to configure SAML single sign-on. For more information, see "[Configuring SAML single sign-on for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." + +{% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/emu-scim-note.md b/translations/ja-JP/data/reusables/enterprise-accounts/emu-scim-note.md new file mode 100644 index 0000000000..309ec9adfb --- /dev/null +++ b/translations/ja-JP/data/reusables/enterprise-accounts/emu-scim-note.md @@ -0,0 +1,7 @@ +{% ifversion fpt%} +{% note %} + +**Note**: If your enterprise uses {% data variables.product.prodname_emus %}, you cannot use team synchronization and must instead configure SCIM to manage membership with your identity provider. For more information, see "[Configuring SCIM provisioning for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users)." + +{% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/emu-short-summary.md b/translations/ja-JP/data/reusables/enterprise-accounts/emu-short-summary.md new file mode 100644 index 0000000000..7e4f69fff9 --- /dev/null +++ b/translations/ja-JP/data/reusables/enterprise-accounts/emu-short-summary.md @@ -0,0 +1 @@ +{% data variables.product.prodname_emus %} is a feature of {% data variables.product.prodname_ghe_cloud %} that provides even greater control over enterprise members and resources. With {% data variables.product.prodname_emus %}, all members are provisioned and managed through your identity provider (IdP) instead of users creating their own accounts on {% data variables.product.product_name %}. Team membership can be managed using groups on your IdP. {% data variables.product.prodname_managed_users_caps %} are restricted to their enterprise and are unable to push code, collaborate, or interact with users, repositories, and organizations outside of their enterprise. For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/emu-shortcode.md b/translations/ja-JP/data/reusables/enterprise-accounts/emu-shortcode.md new file mode 100644 index 0000000000..ec695c807d --- /dev/null +++ b/translations/ja-JP/data/reusables/enterprise-accounts/emu-shortcode.md @@ -0,0 +1 @@ +The short code must be unique to your enterprise, a three-to-eight character alphanumeric string, and contain no special characters. \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/emu-supported-idps.md b/translations/ja-JP/data/reusables/enterprise-accounts/emu-supported-idps.md new file mode 100644 index 0000000000..375040efa3 --- /dev/null +++ b/translations/ja-JP/data/reusables/enterprise-accounts/emu-supported-idps.md @@ -0,0 +1,2 @@ +* Azure Active Directory (Azure AD) +* Okta \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/github-connect-tab.md b/translations/ja-JP/data/reusables/enterprise-accounts/github-connect-tab.md index bd5aa83fe4..8350dff6f4 100644 --- a/translations/ja-JP/data/reusables/enterprise-accounts/github-connect-tab.md +++ b/translations/ja-JP/data/reusables/enterprise-accounts/github-connect-tab.md @@ -1,3 +1,3 @@ {% ifversion ghes < 3.1 %} 1. 左のサイドバーで**{% data variables.product.prodname_github_connect %}**をクリックしてください。 ![GitHub Connect tab in the business account settings sidebar](/assets/images/enterprise/business-accounts/settings-github-connect-tab.png){% else %} -1. In the enterprise account sidebar, click {% octicon "plug" aria-label="The GitHub Connect gear" %} **{% data variables.product.prodname_github_connect %}**. ![GitHub Connect tab in the enterprise account sidebar](/assets/images/help//business-accounts/enterprise-account-github-connect-tab.png){% endif %} \ No newline at end of file +1. In the enterprise account sidebar, click {% octicon "plug" aria-label="The GitHub Connect gear" %} **{% data variables.product.prodname_github_connect %}**. ![GitHub Connect tab in the enterprise account sidebar](/assets/images/help//business-accounts/enterprise-account-github-connect-tab.png){% endif %} diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/identity-provider-tab.md b/translations/ja-JP/data/reusables/enterprise-accounts/identity-provider-tab.md new file mode 100644 index 0000000000..9e94eecb59 --- /dev/null +++ b/translations/ja-JP/data/reusables/enterprise-accounts/identity-provider-tab.md @@ -0,0 +1 @@ +1. Under your business account's name, click {% octicon "key" aria-label="The key icon" %} **Identity provider**. !["Identity provider" tab in enterprise sidebar](/assets/images/help/enterprises/enterprise-account-identity-provider-tab.png) \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/invite-organization.md b/translations/ja-JP/data/reusables/enterprise-accounts/invite-organization.md new file mode 100644 index 0000000000..1d5c99c11e --- /dev/null +++ b/translations/ja-JP/data/reusables/enterprise-accounts/invite-organization.md @@ -0,0 +1 @@ +Enterprise account owners and administrators can invite existing organization accounts to join their enterprise. For more information, see "[Inviting an organization to join your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account#inviting-an-organization-to-join-your-enterprise-account)" diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/team-sync-override.md b/translations/ja-JP/data/reusables/enterprise-accounts/team-sync-override.md new file mode 100644 index 0000000000..a39283eed0 --- /dev/null +++ b/translations/ja-JP/data/reusables/enterprise-accounts/team-sync-override.md @@ -0,0 +1 @@ +If your organization is owned by an enterprise account, enabling team synchronization or SCIM provisioning for the enterprise account will override your organization-level team synchronization settings. For more information, see "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)" and "[Configuring SCIM provisioning for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users)." \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/enterprise_clustering/proxy_protocol_ports.md b/translations/ja-JP/data/reusables/enterprise_clustering/proxy_protocol_ports.md index 4775392f71..5c60786fda 100644 --- a/translations/ja-JP/data/reusables/enterprise_clustering/proxy_protocol_ports.md +++ b/translations/ja-JP/data/reusables/enterprise_clustering/proxy_protocol_ports.md @@ -1,4 +1,4 @@ -#### PROXYプロトコルのTCPポートマッピング +### PROXYプロトコルのTCPポートマッピング | 送信元ポート | 宛先ポート | サービスの説明 | |:------:|:-----:|:------------------------:| diff --git a/translations/ja-JP/data/reusables/enterprise_clustering/without_proxy_protocol_ports.md b/translations/ja-JP/data/reusables/enterprise_clustering/without_proxy_protocol_ports.md index 301363f900..c03fc459f6 100644 --- a/translations/ja-JP/data/reusables/enterprise_clustering/without_proxy_protocol_ports.md +++ b/translations/ja-JP/data/reusables/enterprise_clustering/without_proxy_protocol_ports.md @@ -1,4 +1,4 @@ -#### PROXYサポートなしで使うプロトコルのTCPポートマッピング +### PROXYサポートなしで使うプロトコルのTCPポートマッピング | 送信元ポート | 宛先ポート | サービスの説明 | |:------:|:-----:|:------------------------:| diff --git a/translations/ja-JP/data/reusables/gated-features/code-scanning.md b/translations/ja-JP/data/reusables/gated-features/code-scanning.md index e231a77fdd..b0db784841 100644 --- a/translations/ja-JP/data/reusables/gated-features/code-scanning.md +++ b/translations/ja-JP/data/reusables/gated-features/code-scanning.md @@ -1,6 +1,6 @@ -{% if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_code_scanning_capc %}は、Organizationが所有する{% data variables.product.prodname_GH_advanced_security %}が有効化されたすべてのパブリック及びプライベートリポジトリで利用できます。 -{%- elsif currentVersion ver_gt "enterprise-server@3.0" or currentVersion == "github-ae@next" %}{% data variables.product.prodname_code_scanning_capc %}は、Organizationが所有するリポジトリで{% data variables.product.prodname_GH_advanced_security %}が有効化されていれば利用できます。 -{%- elsif currentVersion == "github-ae@latest" %} +{% ifversion fpt %}{% data variables.product.prodname_code_scanning_capc %}は、Organizationが所有する{% data variables.product.prodname_GH_advanced_security %}が有効化されたすべてのパブリック及びプライベートリポジトリで利用できます。 +{%- elsif ghes > 3.0 %}{% data variables.product.prodname_code_scanning_capc %}は、Organizationが所有するリポジトリで{% data variables.product.prodname_GH_advanced_security %}が有効化されていれば利用できます。 +{%- elsif ghae %} {% data variables.product.prodname_code_scanning_capc %}は、ベータリリースの間は無料の{% data variables.product.prodname_GH_advanced_security %}の一部として利用できます。 {%- else %} {% data variables.product.prodname_code_scanning_capc %}は、{% data variables.product.prodname_GH_advanced_security %}のライセンスを持っているなら利用できます。{% endif %} {% data reusables.advanced-security.more-info-ghas %} diff --git a/translations/ja-JP/data/reusables/gated-features/emus.md b/translations/ja-JP/data/reusables/gated-features/emus.md new file mode 100644 index 0000000000..f9f25095ea --- /dev/null +++ b/translations/ja-JP/data/reusables/gated-features/emus.md @@ -0,0 +1 @@ +To manage users in your enterprise with your identity provider, your enterprise must be enabled for {% data variables.product.prodname_emus %}, which are available with {% data variables.product.prodname_ghe_cloud %}. For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/getting-started/enterprise-advanced-security.md b/translations/ja-JP/data/reusables/getting-started/enterprise-advanced-security.md new file mode 100644 index 0000000000..faffbe7d63 --- /dev/null +++ b/translations/ja-JP/data/reusables/getting-started/enterprise-advanced-security.md @@ -0,0 +1 @@ +If you have a GitHub Advanced Security license for your enterprise account, you can enforce policies to manage {% data variables.product.prodname_dotcom %} Advanced Security features for organizations owned by an enterprise account. For more information, see "[Enforcing policies for Advanced Security in your enterprise account](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-policies-for-advanced-security-in-your-enterprise-account)." \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/github-actions/actions-on-examples.md b/translations/ja-JP/data/reusables/github-actions/actions-on-examples.md index 93890b0e2e..e49d700693 100644 --- a/translations/ja-JP/data/reusables/github-actions/actions-on-examples.md +++ b/translations/ja-JP/data/reusables/github-actions/actions-on-examples.md @@ -1,18 +1,18 @@ -### 単一のイベントを使用する例 +## 単一のイベントを使用する例 ```yaml # リポジトリ内の任意のブランチにコードがプッシュされたときにトリガーされる on: push ``` -### イベントのリストを使用する例 +## イベントのリストを使用する例 ```yaml # プッシュもしくはPull Requestイベントでワークフローをトリガーする on: [push, pull_request] ``` -### アクティビティの種類もしくは設定を伴う複数のイベントを使用する例 +## アクティビティの種類もしくは設定を伴う複数のイベントを使用する例 イベントに対してアクティビティの種類もしくは設定を指定する必要がある場合、それぞれのイベントを個別に設定しなければなりません。 設定を持たないイベントも含め、すべてのイベントにはコロン (`:`)を追加しなければなりません。 diff --git a/translations/ja-JP/data/reusables/github-actions/disabling-github-actions.md b/translations/ja-JP/data/reusables/github-actions/disabling-github-actions.md index f1d8e80a8b..cf191f85b6 100644 --- a/translations/ja-JP/data/reusables/github-actions/disabling-github-actions.md +++ b/translations/ja-JP/data/reusables/github-actions/disabling-github-actions.md @@ -1 +1 @@ -デフォルトでは、{% ifversion ghes or ghae %}{% data variables.product.product_location %}上で有効化されると、{% data variables.product.prodname_actions %}{% elsif fpt %}{% data variables.product.prodname_actions %}{% endif %}はすべてのリポジトリとOrganizationで有効になります。 {% data variables.product.prodname_actions %}を無効化したり、プライベートのアクションのみに制限し、リポジトリ内に存在するアクションだけを使えるようにすることができます。 +デフォルトでは、{% ifversion ghes or ghae %}{% data variables.product.product_location %}上で有効化されると、{% data variables.product.prodname_actions %}{% elsif fpt %}{% data variables.product.prodname_actions %}{% endif %}はすべてのリポジトリとOrganizationで有効になります。 You can choose to disable {% data variables.product.prodname_actions %} or limit them to local actions only, which means that people can only use actions that exist in your repository. diff --git a/translations/ja-JP/data/reusables/github-actions/name-environment.md b/translations/ja-JP/data/reusables/github-actions/name-environment.md new file mode 100644 index 0000000000..d8312e6d9e --- /dev/null +++ b/translations/ja-JP/data/reusables/github-actions/name-environment.md @@ -0,0 +1 @@ +1. 環境の名前を入力し、**Configure environment（環境を設定）**をクリックしてください。 環境名では、大文字と小文字は区別されません。 環境名は255文字を超えてはならず、リポジトリ内でユニークでなければなりません。 diff --git a/translations/ja-JP/data/reusables/github-actions/new-environment.md b/translations/ja-JP/data/reusables/github-actions/new-environment.md new file mode 100644 index 0000000000..ad2616ed42 --- /dev/null +++ b/translations/ja-JP/data/reusables/github-actions/new-environment.md @@ -0,0 +1 @@ +1. **New environment（新しい環境）**をクリックしてください。 diff --git a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md b/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md index f36be45f59..1151256351 100644 --- a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md +++ b/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md @@ -1,6 +1,7 @@ -1. 設定ページの{% ifversion fpt %}"Runners（ランナー）"{% else %}"Self-hosted runners（セルフホストランナー）"{% endif %}のセクションで、設定したいランナーグループの隣の{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}をクリックし、続いて**Edit name and [organization|repository] access（名前と[Organization|リポジトリ]アクセスの編集）<**クリックしてください。 ![リポジトリの権限の管理](/assets/images/help/settings/actions-runner-manage-permissions.png) +1. 設定ページの{% ifversion fpt or ghes > 3.1 or ghae-next %}"Runners（ランナー）"{% else %}"Self-hosted runners（セルフホストランナー）"{% endif %}のセクションで、設定したいランナーグループの隣の{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}をクリックし、続いて**Edit name and [organization|repository] access（名前と[Organization|リポジトリ]アクセスの編集）<**クリックしてください。 ![リポジトリの権限の管理](/assets/images/help/settings/actions-runner-manage-permissions.png) 1. ポリシーオプションを修正するか、ランナーグループ名を変更してください。 + {% ifversion not ghae %} {% warning %} **Warning** @@ -10,3 +11,4 @@ 詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)」を参照してください。 {% endwarning %} + {% endif %} diff --git a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-list.md b/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-list.md index cacf37aec8..c62435e62a 100644 --- a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-list.md +++ b/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-list.md @@ -1 +1 @@ - 1. {% ifversion fpt %}"Runners（ランナー）"{% else %}"Self-hosted runners（セルフホストランナー）"{% endif %}の下のランナーのリストを見つけてください。 + 1. {% ifversion fpt or ghes > 3.1 or ghae-next %}"Runners（ランナー）"{% else %}"Self-hosted runners（セルフホストランナー）"{% endif %}の下のランナーのリストを見つけてください。 diff --git a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md b/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md index 1525eb4db5..f5cf961bd9 100644 --- a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md +++ b/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md @@ -6,5 +6,5 @@ 1. 左のサイドバーで**Enterprise overview（Enterpriseの概要）**をクリックしてください。 1. {% endif %}Enterpriseサイドバー内で{% octicon "law" aria-label="The law icon" %}**Policies（ポリシー）**をクリックしてください。 1. {% data variables.product.prodname_actions %}設定にアクセスしてください: - * **Organizationもしくはリポジトリ内**: 左のサイドバーで**Actions**をクリック{% ifversion fpt %}し、続いて**Runners（ランナー）**をクリック{% endif %}してください。 - * {% ifversion fpt %}**Enterpriseアカウントを使っている場合**:{% elsif ghes or ghae %}**Enterpriseレベルのランナーを使っている場合**:{% endif %} "{% octicon "law" aria-label="The law icon" %} Policies（ポリシー）”の下の**Actions**をクリック{% ifversion fpt %}し、続いて**Runners（ランナー）**タブをクリック{% endif %}してください。 + * **Organizationもしくはリポジトリ内**: 左のサイドバーで**Actions**をクリック{% ifversion fpt or ghes > 3.1 or ghae-next %}し、続いて**Runners（ランナー）**をクリック{% endif %}してください。 + * {% ifversion fpt %}**Enterpriseアカウントを使っている場合**:{% elsif ghes or ghae %}**Enterpriseレベルのランナーを使っている場合**:{% endif %} "{% octicon "law" aria-label="The law icon" %} Policies（ポリシー）”の下の**Actions**をクリック{% ifversion fpt or ghes > 3.1 or ghae-next %}し、続いて**Runners（ランナー）**タブをクリック{% endif %}してください。 diff --git a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md b/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md index e6cb74dbab..6d2481ae6d 100644 --- a/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md +++ b/translations/ja-JP/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md @@ -1,4 +1,4 @@ -1. {% ifversion fpt %}"Runners（ランナー）"{% else %}"Self-hosted runners（セルフホストランナー）"{% endif %}の下で、リスト中のランナーを見つけてください。 ランナーがグループ内にあるなら、{% octicon "chevron-down" aria-label="The downwards chevron" %}をクリックしてリストを展開してください。 +1. {% ifversion fpt or ghes > 3.1 or ghae-next %}"Runners（ランナー）"{% else %}"Self-hosted runners（セルフホストランナー）"{% endif %}の下で、リスト中のランナーを見つけてください。 ランナーがグループ内にあるなら、{% octicon "chevron-down" aria-label="The downwards chevron" %}をクリックしてリストを展開してください。 1. 削除したいランナーの隣の{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}をクリックし、続いて** Remove（削除）**をクリックしてください。 ![セルフホストランナーの設定の削除](/assets/images/help/settings/actions-runner-remove.png) diff --git a/translations/ja-JP/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md b/translations/ja-JP/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md index 11414143c8..d51fdc01ef 100644 --- a/translations/ja-JP/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md +++ b/translations/ja-JP/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md @@ -1,2 +1,2 @@ -1. サイドバーで**Actions（アクション）**をクリックしてください。 -1. In the left sidebar, under "Actions", click **Runner groups**. +1. In the left sidebar, click **Actions**.{% ifversion fpt or ghes > 3.1 or ghae-next %} +1. In the left sidebar, under "Actions", click **Runner groups**.{% endif %} diff --git a/translations/ja-JP/data/reusables/github-actions/settings-sidebar-actions-runners.md b/translations/ja-JP/data/reusables/github-actions/settings-sidebar-actions-runners.md index 0fe6076840..cf59ce1c86 100644 --- a/translations/ja-JP/data/reusables/github-actions/settings-sidebar-actions-runners.md +++ b/translations/ja-JP/data/reusables/github-actions/settings-sidebar-actions-runners.md @@ -1 +1 @@ -1. 左のサイドバーで、**Actions**をクリック{% ifversion fpt %}し、続いて**Runners（ランナー）**をクリック{% endif %}してください。 +1. 左のサイドバーで、**Actions**をクリック{% ifversion fpt or ghes > 3.1 or ghae-next %}し、続いて**Runners（ランナー）**をクリック{% endif %}してください。 diff --git a/translations/ja-JP/data/reusables/github-actions/supported-github-runners.md b/translations/ja-JP/data/reusables/github-actions/supported-github-runners.md index 3f6c96aff2..ea7f62ea3d 100644 --- a/translations/ja-JP/data/reusables/github-actions/supported-github-runners.md +++ b/translations/ja-JP/data/reusables/github-actions/supported-github-runners.md @@ -60,17 +60,6 @@ Ubuntu 18.04     - - - - - @@ -353,7 +352,7 @@ codeql database analyze <database> --format=<format> \ @@ -406,7 +405,7 @@ codeql database analyze <database> --format=<format> \
    - チェックアウトして分析したrefの名前を指定して、結果が正しいコードとマッチできるようにします。 ブランチではrefs/heads/BRANCH-NAMEを、Pull Requestのheadコミットではrefs/pulls/NUMBER/headを、Pull Requestに対して{% data variables.product.product_name %}が生成したマージコミットではrefs/pulls/NUMBER/mergeを使ってください。 + チェックアウトして分析したrefの名前を指定して、結果が正しいコードとマッチできるようにします。 ブランチではrefs/heads/BRANCH-NAMEを、Pull Requestのheadコミットではrefs/pulls/NUMBER/headを、Pull Requestに対して{% data variables.product.prodname_dotcom %}が生成したマージコミットではrefs/pulls/NUMBER/mergeを使ってください。
    - ロードするSARIFファイルを指定してください。{% ifversion ghes > 3.0 or ghae-next %} + ロードするSARIFファイルを指定してください。{% ifversion ghes > 3.0 or ghae %}
    -Ubuntu 16.04[deprecated] - -ubuntu-16.04 - -Deprecated and limited to existing customers only. Migrate to Ubuntu 20.04. For more information, see the blog post. -
    macOS Big Sur 11 diff --git a/translations/ja-JP/data/reusables/github-connect/access-dotcom-and-enterprise.md b/translations/ja-JP/data/reusables/github-connect/access-dotcom-and-enterprise.md index 17f37c6d62..2f22dbfd74 100644 --- a/translations/ja-JP/data/reusables/github-connect/access-dotcom-and-enterprise.md +++ b/translations/ja-JP/data/reusables/github-connect/access-dotcom-and-enterprise.md @@ -1 +1 @@ -1. {% data variables.product.product_location_enterprise %}と{% data variables.product.prodname_dotcom_the_website %}にサインインしてください。 +1. Sign in to {% ifversion ghes %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_ghe_managed %}{% endif %} and {% data variables.product.prodname_dotcom_the_website %}. diff --git a/translations/ja-JP/data/reusables/github-connect/access-profile-settings.md b/translations/ja-JP/data/reusables/github-connect/access-profile-settings.md index 3470f012f1..594d515ed4 100644 --- a/translations/ja-JP/data/reusables/github-connect/access-profile-settings.md +++ b/translations/ja-JP/data/reusables/github-connect/access-profile-settings.md @@ -1 +1 @@ -1. {% data variables.product.product_location_enterprise %} にあるページの右上隅でプロフィール画像をクリックしてから、[**Settings**] をクリックします。 ![ユーザバーの [Settings（設定）] アイコン](/assets/images/help/settings/userbar-account-settings.png) +1. On {% ifversion ghes %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_ghe_managed %}{% endif %}, in the upper-right corner of any page, click your profile photo, then click **Settings**. ![ユーザバーの [Settings（設定）] アイコン](/assets/images/help/settings/userbar-account-settings.png) diff --git a/translations/ja-JP/data/reusables/github-connect/authorize-connection.md b/translations/ja-JP/data/reusables/github-connect/authorize-connection.md index 5e572793a9..7f60fcb86b 100644 --- a/translations/ja-JP/data/reusables/github-connect/authorize-connection.md +++ b/translations/ja-JP/data/reusables/github-connect/authorize-connection.md @@ -1 +1,7 @@ -1. {% data variables.product.prodname_dotcom_the_website %}アカウントから{% data variables.product.prodname_ghe_server %}がアクセスするリソースをレビューし、** Authorize（承認）**をクリックしてください。 ![GitHub Enterprise ServerとGitHub.com間の接続の承認](/assets/images/help/settings/authorize-ghe-to-connect-to-dotcom.png) +1. Review the resources that +{% data variables.product.product_name %} will access from your {% data variables.product.prodname_dotcom_the_website %} account, then click **Authorize**. +{% ifversion ghes %} + ![{% data variables.product.prodname_ghe_server %} と {% data variables.product.prodname_dotcom_the_website %} の間の接続を許可します。](/assets/images/help/settings/authorize-ghe-to-connect-to-dotcom.png) +{% elsif ghae %} + ![{% data variables.product.prodname_ghe_managed %} と {% data variables.product.prodname_dotcom_the_website %} の間の接続を許可します。](/assets/images/enterprise/github-ae/settings/authorize-ghae-to-connect-to-dotcom.png) +{% endif %} diff --git a/translations/ja-JP/data/reusables/github-connect/beta.md b/translations/ja-JP/data/reusables/github-connect/beta.md new file mode 100644 index 0000000000..991a98d3d6 --- /dev/null +++ b/translations/ja-JP/data/reusables/github-connect/beta.md @@ -0,0 +1,7 @@ +{% ifversion ghae-next %} +{% note %} + +**Note:** {% data variables.product.prodname_github_connect %} for {% data variables.product.product_name %} is currently in beta and subject to change. + +{% endnote %} +{% endif %} diff --git a/translations/ja-JP/data/reusables/github-connect/connect-dotcom-and-enterprise.md b/translations/ja-JP/data/reusables/github-connect/connect-dotcom-and-enterprise.md index d349957f9b..0485841ae1 100644 --- a/translations/ja-JP/data/reusables/github-connect/connect-dotcom-and-enterprise.md +++ b/translations/ja-JP/data/reusables/github-connect/connect-dotcom-and-enterprise.md @@ -1 +1,6 @@ -1. **Connect to {% data variables.product.prodname_dotcom_the_website %}（{% data variables.product.prodname_dotcom_the_website %}への接続）**をクリックしてください。 ![GitHub Enterprise Server設定からGitHub.comへの接続](/assets/images/help/settings/github.com_end_user_connection.png) +1. Click **Connect to {% data variables.product.prodname_dotcom_the_website %}**. +{% ifversion ghes %} + ![GitHub Enterprise Server設定からGitHub.comへの接続](/assets/images/help/settings/github.com_end_user_connection.png) +{% else %} + ![Connect to GitHub.com from GitHub AE settings](/assets/images/enterprise/github-ae/settings/github.com-end-user-connection.png) +{% endif %} diff --git a/translations/ja-JP/data/reusables/github-connect/send-contribution-counts-to-githubcom.md b/translations/ja-JP/data/reusables/github-connect/send-contribution-counts-to-githubcom.md new file mode 100644 index 0000000000..e4e4691378 --- /dev/null +++ b/translations/ja-JP/data/reusables/github-connect/send-contribution-counts-to-githubcom.md @@ -0,0 +1 @@ +1. [Contributions] の下で、[**Send my contribution counts to {% data variables.product.prodname_dotcom_the_website %}**] を選択し、[**Update contributions**] をクリックします。 ![コントリビューションを送信するチェックボックスとコントリビューション更新ボタン](/assets/images/help/settings/send-and-update-contributions.png) diff --git a/translations/ja-JP/data/reusables/github-connect/sync-frequency.md b/translations/ja-JP/data/reusables/github-connect/sync-frequency.md index fc0163e318..22143d23fa 100644 --- a/translations/ja-JP/data/reusables/github-connect/sync-frequency.md +++ b/translations/ja-JP/data/reusables/github-connect/sync-frequency.md @@ -1 +1 @@ -{% data variables.product.prodname_ghe_server %} は 1 時間ごとに更新を送信します。 +{% data variables.product.product_name %} は 1 時間ごとに更新を送信します。 diff --git a/translations/ja-JP/data/reusables/notifications-v2/custom-notification-types.md b/translations/ja-JP/data/reusables/notifications-v2/custom-notification-types.md index 0e19372aa5..259282ca15 100644 --- a/translations/ja-JP/data/reusables/notifications-v2/custom-notification-types.md +++ b/translations/ja-JP/data/reusables/notifications-v2/custom-notification-types.md @@ -1,2 +1,2 @@ {%- ifversion fpt or ghes > 3.1 or ghae-issue-4910 %}Issue、Pull Request、リリース、セキュリティアラート、ディスカッション{% endif %} -{%- ifversion ghes = 3.1 or ghae-next %}Issue、Pull Request、リリース、ディスカッション{% endif %} +{%- ifversion ghes = 3.1 %}Issue、Pull Request、リリース、ディスカッション{% endif %} diff --git a/translations/ja-JP/data/reusables/package_registry/public-or-private-packages.md b/translations/ja-JP/data/reusables/package_registry/public-or-private-packages.md index 2838a57470..8fa2e1b8ad 100644 --- a/translations/ja-JP/data/reusables/package_registry/public-or-private-packages.md +++ b/translations/ja-JP/data/reusables/package_registry/public-or-private-packages.md @@ -1 +1 @@ -You can publish packages in {% if currentVersion == "github-ae@latest" %}an internal{% else %}a public{% endif %} repository ({% if currentVersion == "github-ae@latest" %}internal{% else %}public{% endif %} packages) to share with {% if currentVersion == "free-pro-team@latest" %}all of {% data variables.product.prodname_dotcom %}{% else %}everyone on your enterprise{% endif %}, or in a private repository (private packages) to share with collaborators or an organization. +{% ifversion ghae %}インターナル{% else %}パブリック{% endif %}リポジトリで（{% ifversion ghae %}インターナル{% else %}パブリック{% endif %}パッケージ）パッケージを公開して、{% ifversion fpt %}{% data variables.product.prodname_dotcom %}全体{% else %}Enterpriseの全員{% endif %}と、もしくはプライベートリポジトリ（プライベートパッケージ）でパッケージを公開して、コラボレータあるいはOrganizationと共有できます。 diff --git a/translations/ja-JP/data/reusables/pages/about-private-publishing.md b/translations/ja-JP/data/reusables/pages/about-private-publishing.md index 6e3ac3a5d3..17b740c50d 100644 --- a/translations/ja-JP/data/reusables/pages/about-private-publishing.md +++ b/translations/ja-JP/data/reusables/pages/about-private-publishing.md @@ -1 +1 @@ -プロジェクトサイトが{% data variables.product.prodname_ghe_cloud %}を使用するOrganizationが所有するプライベートもしくはインターナルリポジトリから公開されるなら、そのサイトのアクセス制御を管理できます。 +プロジェクトサイトが{% data variables.product.prodname_ghe_cloud %}を使用するOrganizationが所有するプライベートもしくはインターナルリポジトリから公開されるなら、そのサイトのアクセス制御を管理できます。 In an {% data variables.product.prodname_emu_enterprise %}, all {% data variables.product.prodname_pages %} sites are privately published. diff --git a/translations/ja-JP/data/reusables/repositories/auto-gen-release-public-beta.md b/translations/ja-JP/data/reusables/repositories/auto-gen-release-public-beta.md new file mode 100644 index 0000000000..1271ce25e0 --- /dev/null +++ b/translations/ja-JP/data/reusables/repositories/auto-gen-release-public-beta.md @@ -0,0 +1 @@ +Automatically generated release notes are currently in public beta and subject to change. diff --git a/translations/ja-JP/data/reusables/repositories/disabling-markdown-rendering.md b/translations/ja-JP/data/reusables/repositories/disabling-markdown-rendering.md new file mode 100644 index 0000000000..86254f64ec --- /dev/null +++ b/translations/ja-JP/data/reusables/repositories/disabling-markdown-rendering.md @@ -0,0 +1,5 @@ +When viewing a Markdown file, you can click {% octicon "code" aria-label="The code icon" %} at the top of the file to disable Markdown rendering and view the file's source instead. + +![Display Markdown as source](/assets/images/help/writing/display-markdown-as-source.png) + +Disabling Markdown rendering enables you to use source view features, such as line linking, which is not possible when viewing rendered Markdown files. diff --git a/translations/ja-JP/data/reusables/repositories/request-security-advisory-cve-id.md b/translations/ja-JP/data/reusables/repositories/request-security-advisory-cve-id.md index 75304dd68b..b724fa4479 100644 --- a/translations/ja-JP/data/reusables/repositories/request-security-advisory-cve-id.md +++ b/translations/ja-JP/data/reusables/repositories/request-security-advisory-cve-id.md @@ -1,5 +1,3 @@ -まだプロジェクト中のセキュリティ脆弱性に対するCVE識別番号を持っていない場合は、{% data variables.product.prodname_dotcom %}にCVE識別番号をリクエストできます。 {% data variables.product.prodname_dotcom %}は通常、リクエストを72時間以内にレビューします。 CVE識別番号をリクエストしても、セキュリティアドバイザリはパブリックにはなりません。 セキュリティアドバイザリがCVEの対象となるなら、{% data variables.product.prodname_dotcom %}はそのアドバイザリのためにCVE識別番号を予約します。 そして、あなたがセキュリティアドバイザリを公開した後に、CVEの詳細を私たちがCVEの詳細を公開します。 +If you want a CVE identification number for the security vulnerability in your project, and don't already have one, you can request a CVE identification number from {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_dotcom %}は通常、リクエストを72時間以内にレビューします。 CVE識別番号をリクエストしても、セキュリティアドバイザリはパブリックにはなりません。 If your security advisory is eligible for a CVE, {% data variables.product.prodname_dotcom %} will reserve a CVE identification number for your advisory. We'll then publish the CVE details after you make your security advisory public. Anyone with admin permissions to a security advisory can request a CVE identification number. -使いたいCVEをすでに持っている場合、たとえば{% data variables.product.prodname_dotcom %}ではなくCNAを使う場合には、それをセキュリティアドバイザリのフォームに入力してください。 これはたとえば、公開時に送信することを計画している他の通信先と、アドバイザリが一貫しているようにしたい場合に生じるかもしれません。 - -アドバイザリのフォームにCVEがない場合は、アドバイザリをあなたが公開する際に私たちがあなたに代わってCVEをリクエストします。 +If you already have a CVE you want to use, for example, if you use a CVE Numbering Authority (CNA) other than {% data variables.product.prodname_dotcom %}, add the CVE to the security advisory form. これはたとえば、公開時に送信することを計画している他の通信先と、アドバイザリが一貫しているようにしたい場合に生じるかもしれません。 {% data variables.product.prodname_dotcom %} cannot assign CVEs to your project if it is covered by another CNA. \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/repositories/sidebar-issues.md b/translations/ja-JP/data/reusables/repositories/sidebar-issues.md index 5622877f7a..db7600b079 100644 --- a/translations/ja-JP/data/reusables/repositories/sidebar-issues.md +++ b/translations/ja-JP/data/reusables/repositories/sidebar-issues.md @@ -1,5 +1,5 @@ 2. リポジトリ名の下で、クリックします {% octicon "issue-opened" aria-label="The issues icon" %}**Issues** - {% ifversion fpt or ghes > 3.1 or ghae-issue-4483 %} + {% ifversion fpt or ghes > 3.1 or ghae-next %} ![Issueタブ](/assets/images/help/repository/repo-tabs-issues.png){% else %} ![Issues tab](/assets/images/enterprise/3.1/help/repository/repo-tabs-issues.png){% endif %} diff --git a/translations/ja-JP/data/reusables/repositories/sidebar-pr.md b/translations/ja-JP/data/reusables/repositories/sidebar-pr.md index b47fcc3c3c..5ec4149426 100644 --- a/translations/ja-JP/data/reusables/repositories/sidebar-pr.md +++ b/translations/ja-JP/data/reusables/repositories/sidebar-pr.md @@ -1,5 +1,5 @@ 1. リポジトリ名の下で、クリックします {% octicon "git-pull-request" aria-label="The pull request icon" %}**Pull requests** - {% ifversion fpt or ghes > 3.1 or ghae-issue-4483 %} + {% ifversion fpt or ghes > 3.1 or ghae-next %} ![Issue とプルリクエストのタブの選択](/assets/images/help/repository/repo-tabs-pull-requests.png){% else %} ![Issues tab](/assets/images/enterprise/3.1/help/repository/repo-tabs-pull-requests.png){% endif %} diff --git a/translations/ja-JP/data/reusables/repositories/workflow-notifications.md b/translations/ja-JP/data/reusables/repositories/workflow-notifications.md index 563c9258a5..9da78806ea 100644 --- a/translations/ja-JP/data/reusables/repositories/workflow-notifications.md +++ b/translations/ja-JP/data/reusables/repositories/workflow-notifications.md @@ -1,4 +1,4 @@ -{% data variables.product.prodname_actions %}に対するメールあるいはWeb通知を有効化すると、あなたが起動したワークフローの実行が完了すると通知されます。 この通知には、ワークフローの実行のステータス（成功、失敗、ニュートラル、キャンセルされた実行が含まれます）が含まれます。 ワークフローの実行が失敗したときにだけ通知を受けるようにすることもできます。 +{% data variables.product.prodname_actions %}に対するメールあるいはWeb通知を有効化すると、あなたが起動したワークフローの実行が完了すると通知されます。 この通知には、ワークフローの実行のステータス（成功、失敗、ニュートラル、キャンセルされた実行が含まれます）が含まれます。 ワークフローの実行が失敗したときにだけ通知を受けるようにすることもできます。 For more information about enabling or disabling notifications, see "[About notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)." スケジュールされたワークフローに関する通知は、最初にワークフローを作成したユーザに送信されます。 ワークフローファイルのcron構文を他のユーザが更新した場合、それ以降の通知はそのユーザに送られるようになります。{% ifversion fpt or ghes > 2.22 %}スケジュールされたワークフローが無効化され、その後に有効化されると、通知は最後にcron構文を変更したユーザではなく、ワークフローを再有効化したユーザに送られるようになります。{% endif %} diff --git a/translations/ja-JP/data/reusables/saml/about-linked-identities.md b/translations/ja-JP/data/reusables/saml/about-linked-identities.md index 93ec9dbbd4..3fc2157c4d 100644 --- a/translations/ja-JP/data/reusables/saml/about-linked-identities.md +++ b/translations/ja-JP/data/reusables/saml/about-linked-identities.md @@ -1,3 +1,3 @@ -メンバーが自分の{% data variables.product.product_name %}アカウントにリンクしたシングルサインオンのアイデンティティを見ることができます。 利用できる場合には、このエントリにはSCIMデータが含まれます。 詳しい情報については「[SCIMについて](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)」を参照してください。 +メンバーが自分の{% data variables.product.product_name %}アカウントにリンクしたシングルサインオンのアイデンティティを見ることができます。 メンバーが誤ったアイデンティティを{% data variables.product.product_name %}アカウントにリンクしている場合、リンクされたアイデンティティを取り消してメンバーにやり直してもらうことができます。 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 ba471b99d1..d77b3c3e80 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 @@ -1,7 +1,7 @@ | Provider | サポートされているシークレット | APIスラッグ | | -------- | --------------- | ------- | | | | | -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Adafruit IO | Adafruit IO Key | adafruit_io_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Adobe | Adobe Device Token | adobe_device_token{% endif %} @@ -11,73 +11,73 @@ Adobe | Adobe Service Token | adobe_service_token{% endif %} Adobe | Adobe Short-Lived Access Token | adobe_short_lived_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Adobe | Adobe JSON Web Token | adobe_jwt{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Alibaba Cloud | Alibaba Cloud Access Key ID | alibaba_cloud_access_key_id{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Alibaba Cloud | Alibaba Cloud Access Key Secret | alibaba_cloud_access_key_secret{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Amazon Web Services (AWS) | Amazon AWS Access Key ID | aws_access_key_id{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Amazon Web Services (AWS) | Amazon AWS Secret Access Key | aws_secret_access_key{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Amazon Web Services (AWS) | Amazon AWS Session Token | aws_session_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Amazon Web Services (AWS) | Amazon AWS Temporary Access Key ID | aws_temporary_access_key_id{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Asana | Asana Personal Access Token | asana_personal_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Atlassian | Atlassian API Token | atlassian_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Atlassian | Atlassian JSON Web Token | atlassian_jwt{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Atlassian | Bitbucket Server Personal Access Token | bitbucket_server_personal_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Azure | Azure SAS Token | azure_sas_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Azure | Azure Service Management Certificate | azure_management_certificate{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Azure | Azure SQL Connection String | azure_sql_connection_string{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Azure | Azure Storage Account Key | azure_storage_account_key{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Beamer | Beamer API Key | beamer_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Checkout.com | Checkout.com Production Secret Key | checkout_production_secret_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Checkout.com | Checkout.com Test Secret Key | checkout_test_secret_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Clojars | Clojars Deploy Token | clojars_deploy_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} CloudBees CodeShip | CloudBees CodeShip Credential | codeship_credential{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Contentful | Contentful Personal Access Token | contentful_personal_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Databricks | Databricks Access Token | databricks_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Discord | Discord Bot Token | discord_bot_token{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Doppler | Doppler Personal Token | doppler_personal_token{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Doppler | Doppler Service Token | doppler_service_token{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Doppler | Doppler CLI Token | doppler_cli_token{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Doppler | Doppler SCIM Token | doppler_scim_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Doppler | Doppler Audit Token | doppler_audit_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Dropbox | Dropbox Access Token | dropbox_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Dropbox | Dropbox Short Lived Access Token | dropbox_short_lived_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Duffel | Duffel Live Access Token | duffel_live_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Duffel | Duffel Test Access Token | duffel_test_access_token{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Dynatrace | Dynatrace Access Token | dynatrace_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Dynatrace | Dynatrace Internal Token | dynatrace_internal_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} EasyPost | EasyPost Production API Key | easypost_production_api_key{% endif %} @@ -87,17 +87,17 @@ EasyPost | EasyPost Test API Key | easypost_test_api_key{% endif %} Facebook | Facebook Access Token | facebook_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Fastly | Fastly API Token | fastly_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Finicity | Finicity App Key | finicity_app_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Flutterwave | Flutterwave Live API Secret Key | flutterwave_live_api_secret_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Flutterwave | Flutterwave Test API Secret Key | flutterwave_test_api_secret_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Frame.io | Frame.io JSON Web Token | frameio_jwt{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Frame.io| Frame.io Developer Token | frameio_developer_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} FullStory | FullStory API Key | fullstory_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} GitHub | GitHub個人アクセストークン | github_personal_access_token{% endif %} @@ -107,29 +107,29 @@ GitHub | GitHub OAuthアクセストークン | github_oauth_access_token{% endi GitHub | GitHubリフレッシュトークン | github_refresh_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} GitHub | GitHub Appインストールアクセストークン | github_app_installation_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} GitHub | GitHub SSH秘密鍵 | github_ssh_private_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} GoCardless | GoCardless Live Access Token | gocardless_live_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} GoCardless | GoCardless Sandbox Access Token | gocardless_sandbox_access_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Google | Firebase Cloud Messaging Server Key | firebase_cloud_messaging_server_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Google | Google API Key | google_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Google | Google Cloud Private Key ID | google_cloud_private_key_id{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Google | Google Cloud Storage Access Key Secret | google_cloud_storage_access_key_secret{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Google | Google Cloud Storage Service Account Access Key ID | google_cloud_storage_service_account_access_key_id{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Google | Google Cloud Storage User Access Key ID | google_cloud_storage_user_access_key_id{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Grafana | Grafana API Key | grafana_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Hashicorp Terraform | Terraform Cloud / Enterprise API Token | terraform_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Hubspot | Hubspot API Key | hubspot_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Intercom | Intercom Access Token | intercom_access_token{% endif %} @@ -137,9 +137,9 @@ Intercom | Intercom Access Token | intercom_access_token{% endif %} Ionic | Ionic Personal Access Token | ionic_personal_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Ionic | Ionic Refresh Token | ionic_refresh_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} JFrog | JFrog Platform Access Token | jfrog_platform_access_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} JFrog | JFrog Platform API Key | jfrog_platform_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Linear | Linear API Key | linear_api_key{% endif %} @@ -149,15 +149,23 @@ Linear | Linear OAuth Access Token | linear_oauth_access_token{% endif %} Lob | Lob Live API Key | lob_live_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Lob | Lob Test API Key | lob_test_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Mailchimp | Mailchimp API Key | mailchimp_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Mailgun | Mailgun API Key | mailgun_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} MessageBird | MessageBird API Key | messagebird_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} +New Relic | New Relic Personal API Key | new_relic_personal_api_key{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +New Relic | New Relic REST API Key | new_relic_rest_api_key{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +New Relic | New Relic Insights Query Key | new_relic_insights_query_key{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +New Relic | New Relic License Key | new_relic_license_key{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} npm | npm Access Token | npm_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} NuGet | NuGet API Key | nuget_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Onfido | Onfido Live API Token | onfido_live_api_token{% endif %} @@ -165,75 +173,75 @@ Onfido | Onfido Live API Token | onfido_live_api_token{% endif %} Onfido | Onfido Sandbox API Token | onfido_sandbox_api_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} OpenAI | OpenAI API Key | openai_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Palantir | Palantir JSON Web Token | palantir_jwt{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} PlanetScale | PlanetScale Database Password | planetscale_database_password{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} PlanetScale | PlanetScale OAuth Token | planetscale_oauth_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} PlanetScale | PlanetScale Service Token | planetscale_service_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Plivo | Plivo Auth ID | plivo_auth_id{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Plivo | Plivo Auth Token | plivo_auth_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Postman | Postman API Key | postman_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Proctorio | Proctorio Consumer Key | proctorio_consumer_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Proctorio | Proctorio Linkage Key | proctorio_linkage_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Proctorio | Proctorio Registration Key | proctorio_registration_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Proctorio | Proctorio Secret Key | proctorio_secret_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Pulumi | Pulumi Access Token | pulumi_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} PyPI | PyPI API Token | pypi_api_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} RubyGems | RubyGems API Key | rubygems_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Samsara | Samsara API Token | samsara_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Samsara | Samsara OAuth Access Token | samsara_oauth_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} SendGrid | SendGrid API Key | sendgrid_api_key{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Sendinblue | Sendinblue API Key | sendinblue_api_key{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Sendinblue | Sendinblue SMTP Key | sendinblue_smtp_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Shippo | Shippo Live API Token | shippo_live_api_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Shippo | Shippo Test API Token | shippo_test_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Shopify | Shopify App Shared Secret | shopify_app_shared_secret{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Shopify | Shopify Access Token | shopify_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Shopify | Shopify Custom App Access Token | shopify_custom_app_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Shopify | Shopify Private App Password | shopify_private_app_password{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Slack | Slack API Token | slack_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Slack | Slack Incoming Webhook URL | slack_incoming_webhook_url{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Slack | Slack Workflow Webhook URL | slack_workflow_webhook_url{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} SSLMate | SSLMate API Key | sslmate_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} SSLMate | SSLMate Cluster Secret | sslmate_cluster_secret{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Stripe | Stripe API Key | stripe_api_key{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Stripe | Stripe Live API Secret Key | stripe_live_secret_key{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Stripe | Stripe Test API Secret Key | stripe_test_secret_key{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Stripe | Stripe Live API Restricted Key | stripe_live_restricted_key{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Stripe | Stripe Test API Restricted Key | stripe_test_restricted_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Stripe | Stripe Webhook Signing Secret | stripe_webhook_signing_secret{% endif %} @@ -241,9 +249,9 @@ Stripe | Stripe Webhook Signing Secret | stripe_webhook_signing_secret{% endif % Tableau | Tableau Personal Access Token | tableau_personal_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Telegram | Telegram Bot Token | telegram_bot_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Tencent Cloud | Tencent Cloud Secret ID | tencent_cloud_secret_id{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Twilio | Twilio Account String Identifier | twilio_account_sid{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Twilio | Twilio API Key | twilio_api_key{% endif %} diff --git a/translations/ja-JP/data/reusables/sponsors/add-welcome-message.md b/translations/ja-JP/data/reusables/sponsors/add-welcome-message.md new file mode 100644 index 0000000000..8962236ad1 --- /dev/null +++ b/translations/ja-JP/data/reusables/sponsors/add-welcome-message.md @@ -0,0 +1 @@ +1. Optionally, type a welcome message for the tier. ![Add welcome message](/assets/images/help/sponsors/add-a-welcome-message.png) \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/sponsors/tier-details.md b/translations/ja-JP/data/reusables/sponsors/tier-details.md index 60794fde03..f63e5c6baa 100644 --- a/translations/ja-JP/data/reusables/sponsors/tier-details.md +++ b/translations/ja-JP/data/reusables/sponsors/tier-details.md @@ -1,4 +1,4 @@ -スポンサーが選択できる1回かぎりのスポンサーシップ層を最大10、月次の層を最大10作成できます。 各層には、それぞれの1回あるいは月次の支払い額が米ドルであり、カスタム金額の層を有効化することもできます。 加えて、カスタムの額（月額及び1回）の層の有効化を選択することもできます。 +You can create up to 10 one-time sponsorship tiers and 10 monthly tiers for sponsors to choose from. 各層には、それぞれの1回あるいは月次の支払い額が米ドルであり、カスタム金額の層を有効化することもできます。 加えて、カスタムの額（月額及び1回）の層の有効化を選択することもできます。 各層の謝礼をカスタマイズできます。 たとえば、層の謝礼には以下のようなものがあるでしょう: - 新バージョンへの早期アクセス @@ -7,4 +7,6 @@ - 週次のニュースレターの更新 - スポンサーが喜ぶその他の謝礼 +You can include a welcome message with information about accessing or receiving rewards, which will be visible after payment and in the welcome email. + 層を公開すると、その層の金額は編集できなくなります。 その代わりに、その層を止めて新しい層を作成できます。 終了した層の既存のスポンサーは、スポンサーシップの層を変更するか、スポンサーシップをキャンセルするか、1回のスポンサーシップの期間が終了するまで、そのまま残ります。 diff --git a/translations/ja-JP/data/reusables/ssh/add-ssh-key-to-ssh-agent-commandline.md b/translations/ja-JP/data/reusables/ssh/add-ssh-key-to-ssh-agent-commandline.md index 415f86736d..9bed61119b 100644 --- a/translations/ja-JP/data/reusables/ssh/add-ssh-key-to-ssh-agent-commandline.md +++ b/translations/ja-JP/data/reusables/ssh/add-ssh-key-to-ssh-agent-commandline.md @@ -1,3 +1,3 @@ ```shell -$ ssh-add ~/.ssh/id_ed25519 +$ ssh-add ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %} ``` diff --git a/translations/ja-JP/data/reusables/ssh/add-ssh-key-to-ssh-agent.md b/translations/ja-JP/data/reusables/ssh/add-ssh-key-to-ssh-agent.md index 6c0a9c55cb..43243b9f14 100644 --- a/translations/ja-JP/data/reusables/ssh/add-ssh-key-to-ssh-agent.md +++ b/translations/ja-JP/data/reusables/ssh/add-ssh-key-to-ssh-agent.md @@ -1 +1 @@ -キーを別の名前で作成したか、別の名前を持つ既存のキーを追加しようとしている場合は、コマンド内の*id_ed25519*を秘密鍵ファイルの名前で置き換えてください。 +If you created your key with a different name, or if you are adding an existing key that has a different name, replace *id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}* in the command with the name of your private key file. diff --git a/translations/ja-JP/data/reusables/user_settings/generate_new_token.md b/translations/ja-JP/data/reusables/user_settings/generate_new_token.md new file mode 100644 index 0000000000..87cdf2707e --- /dev/null +++ b/translations/ja-JP/data/reusables/user_settings/generate_new_token.md @@ -0,0 +1 @@ +1. [**Generate new token**] をクリックします。 ![[Generate new token] ボタン](/assets/images/help/settings/generate_new_token.png) \ No newline at end of file diff --git a/translations/ja-JP/data/ui.yml b/translations/ja-JP/data/ui.yml index e3ab8410e7..80a017790c 100644 --- a/translations/ja-JP/data/ui.yml +++ b/translations/ja-JP/data/ui.yml @@ -30,9 +30,10 @@ toc: guides: ガイド whats_new: 更新情報 pages: - article_version: '記事のバージョン：' + article_version: 'Article version' miniToc: 'ここには以下の内容があります:' contributor_callout: この記事は、次の人によってコントリビュートされ、管理されています。 + all_enterprise_releases: All Enterprise releases errors: oops: 問題が発生しています。 something_went_wrong: 何か問題が生じています。 @@ -155,13 +156,17 @@ product_sublanding: learning_paths_desc: 学習パスは、特定の課題をマスターするのに役立つガイド集です。 guides: '{{ productMap[currentProduct].name }}のガイド' more_guides: その他のガイド - no_result: 申し訳ありませんが、指定されたフィルタにマッチするガイドはありません。 load_more: さらにガイドをロード all_guides: 'すべての{{ productMap[currentProduct].name }}のガイド' + filter_instructions: Filter the guide list using these controls filters: type: 種類 topic: トピック all: すべて + guides_found: + multiple: '{n} guides found' + one: 1 guide found + none: No guides found guide_types: overview: 概要 quick_start: クイックスタート diff --git a/translations/ja-JP/data/variables/product.yml b/translations/ja-JP/data/variables/product.yml index 5d6a8a48e4..92a9cf1592 100644 --- a/translations/ja-JP/data/variables/product.yml +++ b/translations/ja-JP/data/variables/product.yml @@ -76,6 +76,14 @@ prodname_actions: 'GitHub Actions' prodname_debug: 'GitHub デバッグ' #GitHub Discussions prodname_discussions: 'GitHub Discussions' +#GitHub Enterprise Managed Users +prodname_emu_idp_application: 'GitHub Enterprise Managed User' +prodname_emus: 'Enterprise Managed Users' +prodname_managed_user: 'managed user' +prodname_managed_users: 'managed users' +prodname_managed_users_caps: 'Managed users' +prodname_emu_enterprise: 'enterprise with managed users' +prodname_emu_org: 'organization with managed users' #GitHub Issues prodname_github_issues: 'GitHubのIssue' #GitHub Packages @@ -94,6 +102,7 @@ prodname_security_center: 'セキュリティセンター' #Codespaces prodname_codespaces: 'Codespaces' prodname_github_codespaces: 'GitHub Codespaces' +prodname_serverless: 'web-based editor' #GitHub resources: blog, jobs, Learning Lab prodname_gcf: 'GitHub Community Support' prodname_blog: 'GitHub ブログ' @@ -135,6 +144,8 @@ prodname_dependabot_version_updates: 'Dependabotバージョンアップデー #GitHub Archive Program prodname_archive: 'GitHub Archive Program' prodname_arctic_vault: 'Arctic Code Vault' +#GitHub Copilot +prodname_copilot: 'GitHub Copilot' #Links product_url: >- {% ifversion fpt %}github.com{% else %}[hostname]{% endif %} diff --git a/translations/ja-JP/data/variables/release_candidate.yml b/translations/ja-JP/data/variables/release_candidate.yml index e6ddf079ac..ec65ef6f94 100644 --- a/translations/ja-JP/data/variables/release_candidate.yml +++ b/translations/ja-JP/data/variables/release_candidate.yml @@ -1,2 +1,2 @@ --- -version: enterprise-server@3.2 +version: '' diff --git a/translations/ko-KR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md b/translations/ko-KR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md index 92de06f4d9..b35abe777d 100644 --- a/translations/ko-KR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md +++ b/translations/ko-KR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md @@ -45,7 +45,7 @@ When you unsubscribe from notifications in your inbox, they will automatically d {% data reusables.notifications.access_notifications %} 1. From the notifications inbox, select the notifications you want to unsubscribe to. -2. Use the **selected** {% octicon "triangle-down" aria-label="The down triangle icon" %} drop-down to click **Unsubscribe.** ![Unsubscribe option from main inbox](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png) +2. Click **Unsubscribe.** ![Unsubscribe option from main inbox](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png) ## Unsubscribing from notifications on the subscriptions page @@ -61,13 +61,12 @@ When you unwatch a repository, you unsubscribe from future updates from that rep {% data reusables.notifications.access_notifications %} 1. In the left sidebar, under the list of repositories, use the "Manage notifications" drop-down to click **Watched repositories**. ![Manage notifications drop down menu options](/assets/images/help/notifications-v2/manage-notifications-options.png) 2. On the watched repositories page, after you've evaluated the repositories you're watching, choose whether to: - {% ifversion ghae or ghes < 3.1 %} - - Unwatch a repository - - Only watch releases for a repository - - Ignore all notifications for a repository - {% endif %} {% ifversion fpt or ghes > 3.0 or ghae-next %} - Unwatch a repository - Ignore all notifications for a repository - Customize the types of event you receive notifications for ({% data reusables.notifications-v2.custom-notification-types %}, if enabled) + {% else %} + - Unwatch a repository + - Only watch releases for a repository + - Ignore all notifications for a repository {% endif %} diff --git a/translations/ko-KR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md b/translations/ko-KR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md index c10fa59d6c..58aa0e954c 100644 --- a/translations/ko-KR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md +++ b/translations/ko-KR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md @@ -70,10 +70,10 @@ Many people forget about repositories that they've chosen to watch in the past. 1. In the left sidebar, under the list of repositories, use the "Manage notifications" drop-down menu and click **Watched repositories**. ![Manage notifications drop down menu options](/assets/images/help/notifications-v2/manage-notifications-options.png) 2. Evaluate the repositories that you are watching and decide if their updates are still relevant and helpful. When you watch a repository, you will be notified of all conversations for that repository. -{% ifversion ghae or ghes < 3.1 %} - ![Watched notifications page](/assets/images/help/notifications-v2/watched-notifications.png) -{% elsif fpt or ghes > 3.0 or ghae-next %} +{% ifversion fpt or ghes > 3.0 or ghae-next %} ![Watched notifications page](/assets/images/help/notifications-v2/watched-notifications-custom.png) +{% else %} + ![Watched notifications page](/assets/images/help/notifications-v2/watched-notifications.png) {% endif %} {% tip %} diff --git a/translations/ko-KR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md b/translations/ko-KR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md index 32f3efe5f6..a0b286312a 100644 --- a/translations/ko-KR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md +++ b/translations/ko-KR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md @@ -29,7 +29,7 @@ You can choose to subscribe to notifications for: - A conversation in a specific issue, pull request, or gist. - All activity in a repository or team discussion. - CI activity, such as the status of workflows in repositories set up with {% data variables.product.prodname_actions %}. {% ifversion fpt or ghes > 3.0 or ghae-next %} -- Repository {% data reusables.notifications-v2.custom-notification-types %} (if enabled). {% elsif ghae or ghes %} +- Repository {% data reusables.notifications-v2.custom-notification-types %} (if enabled).{% else %} - Releases in a repository.{% endif %} You can also choose to automatically watch all repositories that you have push access to, except forks. You can watch any other repository you have access to manually by clicking **Watch**. diff --git a/translations/ko-KR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md b/translations/ko-KR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md index 4f7b1645e4..fe904aa6fc 100644 --- a/translations/ko-KR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md +++ b/translations/ko-KR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md @@ -70,12 +70,14 @@ Email notifications also allow flexibility with the types of notifications you r When you watch a repository, you're subscribing to updates for activity in that repository. Similarly, when you watch a specific team's discussions, you're subscribing to all conversation updates on that team's page. For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)." To see repositories that you're watching, go to your [watching page](https://github.com/watching). For more information, see "[Managing subscriptions and notifications on GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)." + {% ifversion ghae or ghes < 3.1 %} ### Configuring notifications {% endif %} -You can configure notifications for a repository on the repository page, or on your watching page.{% ifversion ghae or ghes < 3.1 %} You can choose to only receive notifications for releases in a repository, or ignore all notifications for a repository.{% endif %} +You can configure notifications for a repository on the repository page, or on your watching page.{% ifversion ghes < 3.1 %} You can choose to only receive notifications for releases in a repository, or ignore all notifications for a repository.{% endif %} {% ifversion fpt or ghes > 3.0 or ghae-next %} + ### About custom notifications You can customize notifications for a repository. For example, you can choose to only be notified when updates to one or more types of events ({% data reusables.notifications-v2.custom-notification-types %}) happen within a repository, or ignore all notifications for a repository. {% endif %} For more information, see "[Configuring your watch settings for an individual repository](#configuring-your-watch-settings-for-an-individual-repository)" below. @@ -158,25 +160,18 @@ If "Automatically watch repositories" is disabled, then you will not automatical ## Configuring your watch settings for an individual repository -You can choose whether to watch or unwatch an individual repository. You can also choose to only be notified of {% ifversion fpt or ghes > 3.0 or ghae-next %}certain event types such as {% data reusables.notifications-v2.custom-notification-types %} (if enabled for the repository){% else %}new releases{% endif %}, or completely ignore an individual repository. +You can choose whether to watch or unwatch an individual repository. You can also choose to only be notified of {% ifversion fpt or ghes > 3.0 or ghae-next %}certain event types such as {% data reusables.notifications-v2.custom-notification-types %} (if enabled for the repository) {% else %}new releases{% endif %}, or completely ignore an individual repository. {% data reusables.repositories.navigate-to-repo %} 2. In the upper-right corner, click the "Watch" drop-down menu to select a watch option. -{% ifversion ghae or ghes < 3.1 %} - ![Watch options in a drop-down menu for a repository](/assets/images/help/notifications-v2/watch-repository-options.png) -{% elsif fpt or ghes > 3.0 or ghae-next %} +{% ifversion fpt or ghes > 3.0 or ghae-next %} ![Watch options in a drop-down menu for a repository](/assets/images/help/notifications-v2/watch-repository-options-custom.png) -The **Custom** option allows you to further customize notifications so that you're only notified when specific events happen in the repository, in addition to participating and @mentions. - -{% ifversion fpt or ghes > 3.1 or ghae-issue-4910 %} - ![Custom watch options in a drop-down menu for a repository](/assets/images/help/notifications-v2/watch-repository-options-custom2-dotcom.png) + The **Custom** option allows you to further customize notifications so that you're only notified when specific events happen in the repository, in addition to participating and @mentions. {% else %} - ![Custom watch options in a drop-down menu for a repository](/assets/images/enterprise/3.1/help/notifications-v2/watch-repository-options-custom2.png) -{% endif %} - -If you select "Issues", you will be notified about, and subscribed to, updates on every issue (including those that existed prior to you selecting this option) in the repository. If you're @mentioned in a pull request in this repository, you'll receive notifications for that too, and you'll be subscribed to updates on that specific pull request, in addition to being notified about issues. - + ![Watch options in a drop-down menu for a repository](/assets/images/help/notifications-v2/watch-repository-options.png){% endif %} +{% ifversion fpt or ghes > 3.0 or ghae-next %} + ![Custom watch options in a drop-down menu for a repository](/assets/images/help/notifications-v2/watch-repository-options-custom2-dotcom.png) If you select "Issues", you will be notified about, and subscribed to, updates on every issue (including those that existed prior to you selecting this option) in the repository. If you're @mentioned in a pull request in this repository, you'll receive notifications for that too, and you'll be subscribed to updates on that specific pull request, in addition to being notified about issues. {% endif %} ## Choosing where your organization’s email notifications are sent diff --git a/translations/ko-KR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md b/translations/ko-KR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md index 99d3f072af..53b8ca46c5 100644 --- a/translations/ko-KR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md +++ b/translations/ko-KR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md @@ -48,6 +48,14 @@ When you sign up for an account, {% data variables.product.product_name %} provi You can change the name that is displayed on your profile. This name may also be displayed next to comments you make on private repositories owned by an organization. For more information, see "[Managing the display of member names in your organization](/articles/managing-the-display-of-member-names-in-your-organization)." +{% ifversion fpt %} +{% note %} + +**Note:** If you're a member of an {% data variables.product.prodname_emu_enterprise %}, any changes to your profile name must be made through your identity provider instead of {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.emu-more-info-account %} + +{% endnote %} +{% endif %} + {% data reusables.user_settings.access_settings %} 2. Under "Name", type the name you want to be displayed on your profile. ![Name field in profile settings](/assets/images/help/profile/name-field.png) diff --git a/translations/ko-KR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/index.md b/translations/ko-KR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/index.md index cac9871846..11dd5764de 100644 --- a/translations/ko-KR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/index.md +++ b/translations/ko-KR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/index.md @@ -14,7 +14,7 @@ children: - /viewing-contributions-on-your-profile - /showing-an-overview-of-your-activity-on-your-profile - /publicizing-or-hiding-your-private-contributions-on-your-profile - - /sending-your-github-enterprise-server-contributions-to-your-githubcom-profile + - /sending-enterprise-contributions-to-your-githubcom-profile - /why-are-my-contributions-not-showing-up-on-my-profile - /troubleshooting-commits-on-your-timeline shortTitle: Manage contribution graph diff --git a/translations/ko-KR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md b/translations/ko-KR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md index bc34246b76..aa88fd43a1 100644 --- a/translations/ko-KR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md +++ b/translations/ko-KR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md @@ -14,14 +14,18 @@ topics: shortTitle: Private contributions --- -If you publicize your private contributions, people without access to the private repositories you work in won't be able to see the details of your private contributions. Instead, they'll see the number of private contributions you made on any given day. Your public contributions will include detailed information. For more information, see "[Viewing contributions on your profile page](/articles/viewing-contributions-on-your-profile-page)". +If you publicize your private contributions, people without access to the private repositories you work in won't be able to see the details of your private contributions. Instead, they'll see the number of private contributions you made on any given day. Your public contributions will include detailed information. For more information, see "[Viewing contributions on your profile page](/articles/viewing-contributions-on-your-profile-page)." + +{% note %} + +**Note:** {% ifversion fpt or ghes %}On {% ifversion fpt %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_name %}{% endif %}, public contributions on your profile are visible {% ifversion fpt %}to anyone in the world who can access {% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}only to other users of {% data variables.product.product_location%}{% endif %}.{% elsif ghae %}On {% data variables.product.prodname_ghe_managed %}, only other members of your enterprise can see the contributions on your profile.{% endif %} + +{% endnote %} ## Changing the visibility of your private contributions -By default, visitors only see public contributions on your profile. - {% data reusables.profile.access_profile %} -2. Publicize or hide your private contributions on your profile: +1. Publicize or hide your private contributions on your profile: - To publicize your private contributions, above your contributions graph, use the **Contribution settings** drop-down menu, and select **Private contributions**. Visitors will see your private contribution counts without further details. ![Enable visitors to see private contributions from contribution settings drop-down menu](/assets/images/help/profile/private-contributions-on.png) - To hide your private contributions, above your contributions graph, use the **Contribution settings** drop-down menu, and unselect **Private contributions.** Visitors will only see your public contributions. ![Enable visitors to see private contributions from contribution settings drop-down menu](/assets/images/help/profile/private-contributions-off.png) diff --git a/translations/ko-KR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md b/translations/ko-KR/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 new file mode 100644 index 0000000000..79c6391598 --- /dev/null +++ b/translations/ko-KR/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 @@ -0,0 +1,65 @@ +--- +title: Sending enterprise contributions to your GitHub.com profile +intro: 'You can highlight your work on {% data variables.product.prodname_enterprise %} by sending the contribution counts to your {% data variables.product.prodname_dotcom_the_website %} profile.' +redirect_from: + - /articles/sending-your-github-enterprise-contributions-to-your-github-com-profile/ + - /articles/sending-your-github-enterprise-server-contributions-to-your-github-com-profile + - /articles/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile + - /github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile + - /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile +versions: + fpt: '*' + ghes: '*' + ghae: next +topics: + - Profiles +shortTitle: Send enterprise contributions +--- + +## About enterprise contributions on your {% data variables.product.prodname_dotcom_the_website %} profile + +Your {% data variables.product.prodname_dotcom_the_website %} profile shows {% ifversion fpt %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae-next %} or {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} contribution counts from the past 90 days. {% data reusables.github-connect.sync-frequency %} Contribution counts from {% data variables.product.prodname_enterprise %} are considered private contributions. The commit details will only show the contribution counts and that these contributions were made in a {% data variables.product.prodname_enterprise %} environment outside of {% data variables.product.prodname_dotcom_the_website %}. + +You can decide whether to show counts for private contributions on your profile. For more information, see "[Publicizing or hiding your private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile/)." + +For more information about how contributions are calculated, see "[Managing contribution graphs on your profile](/articles/managing-contribution-graphs-on-your-profile/)." + +{% note %} + +**참고:** +- The connection between your accounts is governed by GitHub's Privacy Statement and users enabling the connection agree to the GitHub's Terms of Service. + +- Before you can connect your {% ifversion fpt %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae-next %} or {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} profile to your {% data variables.product.prodname_dotcom_the_website %} profile, your enterprise owner must enable {% data variables.product.prodname_github_connect %} and enable contribution sharing between the environments. For more information, contact your enterprise owner. + +{% endnote %} + +{% ifversion fpt or ghes or ghae %} + +## Sending your enterprise contributions to your {% data variables.product.prodname_dotcom_the_website %} profile + +{% ifversion fpt %} + +- To send enterprise contributions from {% data variables.product.prodname_ghe_server %} to your {% data variables.product.prodname_dotcom_the_website %} profile, see "[Sending enterprise contributions to your {% data variables.product.prodname_dotcom_the_website %} profile](/enterprise-server/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)" in the {% data variables.product.prodname_ghe_server %} documentation.{% ifversion ghae-next %} +- To send enterprise contributions from {% data variables.product.prodname_ghe_managed %} to your {% data variables.product.prodname_dotcom_the_website %} profile, see "[Sending enterprise contributions to your {% data variables.product.prodname_dotcom_the_website %} profile](/github-ae@latest/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)" in the {% data variables.product.prodname_ghe_managed %} documentation.{% endif %} + +{% elsif ghes %} + +1. Sign in to {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_dotcom_the_website %}. +1. On {% data variables.product.prodname_ghe_server %}, in the upper-right corner of any page, click your profile photo, then click **Settings**. ![Settings icon in the user bar](/assets/images/help/settings/userbar-account-settings.png) +{% data reusables.github-connect.github-connect-tab-user-settings %} +{% data reusables.github-connect.connect-dotcom-and-enterprise %} +1. Review the resources that {% data variables.product.prodname_ghe_server %} will access from your {% data variables.product.prodname_dotcom_the_website %} account, then click **Authorize**. ![Authorize connection between GitHub Enterprise Server and GitHub.com](/assets/images/help/settings/authorize-ghe-to-connect-to-dotcom.png) +{% data reusables.github-connect.send-contribution-counts-to-githubcom %} + +{% elsif ghae %} + +1. Sign in to {% data variables.product.prodname_ghe_managed %} and {% data variables.product.prodname_dotcom_the_website %}. +1. On {% data variables.product.prodname_ghe_managed %}, in the upper-right corner of any page, click your profile photo, then click **Settings**. ![Settings icon in the user bar](/assets/images/help/settings/userbar-account-settings.png) +{% data reusables.github-connect.github-connect-tab-user-settings %} +{% data reusables.github-connect.connect-dotcom-and-enterprise %} +{% data reusables.github-connect.authorize-connection %} +{% data reusables.github-connect.send-contribution-counts-to-githubcom %} + +{% endif %} + +{% endif %} diff --git a/translations/ko-KR/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/ko-KR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md index 6583ddc649..d2e6f9c342 100644 --- a/translations/ko-KR/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/ko-KR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md @@ -83,7 +83,7 @@ Timestamps are calculated differently for commits and pull requests: ![Activity overview section on profile](/assets/images/help/profile/activity-overview-section.png) -The organizations featured in the activity overview are prioritized according to how active you are in the organization. If you @mention an organization in your profile bio, and you’re an organization member, then that organization is prioritized first in the activity overview. For more information, see “[Mentioning people and teams](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)” or "[Adding a bio to your profile](/articles/adding-a-bio-to-your-profile/)." +The organizations featured in the activity overview are prioritized according to how active you are in the organization. If you @mention an organization in your profile bio, and you’re an organization member, then that organization is prioritized first in the activity overview. For more information, see "[Mentioning people and teams](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)” or "[Adding a bio to your profile](/articles/adding-a-bio-to-your-profile/)." ## Contribution activity @@ -91,15 +91,14 @@ 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 not ghae %} -## Viewing contributions from {% data variables.product.product_location_enterprise %} on {% data variables.product.prodname_dotcom_the_website %} +{% ifversion fpt or ghes or ghae-next %} + +## Viewing contributions from {% data variables.product.prodname_enterprise %} on {% data variables.product.prodname_dotcom_the_website %} + +If you use {% ifversion fpt %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae-next %} 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)." -If your site administrator has enabled {% data variables.product.prodname_unified_contributions %}, you can send {% data variables.product.prodname_enterprise %} contribution counts to your {% data variables.product.prodname_dotcom_the_website %} profile. For more information, see "[Sending your {% data variables.product.prodname_ghe_server %} contributions to your {% data variables.product.prodname_dotcom_the_website %}](/articles/sending-your-github-enterprise-server-contributions-to-your-github-com-profile)." {% endif %} ## 더 읽을거리 - "[Viewing contributions on your profile page](/articles/viewing-contributions-on-your-profile-page)" -- "[Why are my contributions not showing up on my profile?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)" -- "[Publicizing or hiding your private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)" -- "[Showing an overview of your activity on your profile](/articles/showing-an-overview-of-your-activity-on-your-profile)" diff --git a/translations/ko-KR/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/ko-KR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md index 3837bdd1ee..74090d353d 100644 --- a/translations/ko-KR/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/ko-KR/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 @@ -24,6 +24,8 @@ Repositories owned by an organization can grant more granular access. For more i {% ifversion fpt %} +If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you can only invite other members of your enterprise to collaborate with you. {% data reusables.enterprise-accounts.emu-more-info-account %} + {% note %} **Note:** {% data variables.product.company_short %} limits the number of people who can be invited to a repository within a 24-hour period. If you exceed this limit, either wait 24 hours or create an organization to collaborate with more people. diff --git a/translations/ko-KR/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/ko-KR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md index f393490e69..3fd1f663a9 100644 --- a/translations/ko-KR/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/ko-KR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md @@ -18,7 +18,9 @@ shortTitle: Add an email address {% note %} -**Note**: {% data reusables.user_settings.no-verification-disposable-emails %} +**Notes**: + - {% data reusables.user_settings.no-verification-disposable-emails %} + - If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you cannot make changes to your email address on {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.emu-more-info-account %} {% endnote %} diff --git a/translations/ko-KR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md b/translations/ko-KR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md index 87e65455db..19fca93416 100644 --- a/translations/ko-KR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md +++ b/translations/ko-KR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md @@ -31,6 +31,12 @@ After changing your username, your old username becomes available for anyone els - [@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 %} + +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. diff --git a/translations/ko-KR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md b/translations/ko-KR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md index 7844819b37..0d56da15cc 100644 --- a/translations/ko-KR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md +++ b/translations/ko-KR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md @@ -15,6 +15,7 @@ topics: children: - /about-your-personal-dashboard - /managing-your-theme-settings + - /managing-your-tab-size-rendering-preference - /changing-your-github-username - /merging-multiple-user-accounts - /converting-a-user-into-an-organization diff --git a/translations/ko-KR/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/ko-KR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md new file mode 100644 index 0000000000..cefff8afe9 --- /dev/null +++ b/translations/ko-KR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md @@ -0,0 +1,15 @@ +--- +title: Managing your tab size rendering preference +intro: 'You can manage the number of spaces a tab is equal to for your user account.' +versions: + fpt: '*' +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 user settings sidebar, click **Appearance**. !["Appearance" tab in user settings sidebar](/assets/images/help/settings/appearance-tab.png) +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) \ No newline at end of file diff --git a/translations/ko-KR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md b/translations/ko-KR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md index 4f8ab0af43..d1aad07848 100644 --- a/translations/ko-KR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md +++ b/translations/ko-KR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md @@ -3,6 +3,7 @@ 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: next ghes: '>=3.2' topics: - Accounts @@ -14,7 +15,15 @@ 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 ghae-issue-4618 %} People with visual impairment may benefit from the dark high contrast theme, with greater contrast between foreground and background elements.{% endif %} +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 ghae-issue-4618 %} 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 %} If you have colorblindness, you may benefit from our light and dark colorblind themes. + +{% note %} + +**Note:** The colorblind themes are currently in public beta. For more information on enabling features in public beta, see "[Exploring early access releases with feature preview](/get-started/using-github/exploring-early-access-releases-with-feature-preview)." + +{% endnote %}{% endif %} {% data reusables.user_settings.access_settings %} 1. In the user settings sidebar, click **Appearance**. !["Appearance" tab in user settings sidebar](/assets/images/help/settings/appearance-tab.png) @@ -24,6 +33,8 @@ You may want to use a dark theme to reduce power consumption on certain devices, {% ifversion fpt or ghae-issue-4618 %}![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 ghae-issue-4618 %}![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 ghae-issue-4619 %} + - 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/ko-KR/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/ko-KR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md index cabf9f9dee..b37cee2337 100644 --- a/translations/ko-KR/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/ko-KR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md @@ -35,7 +35,7 @@ The repository owner has full control of the repository. In addition to the acti | {% ifversion fpt %}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 %} -| Limit interactions with the repository | "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)" |{% endif %}{% ifversion fpt or ghes > 3.0 %} +| Limit interactions with the repository | "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)" |{% endif %}{% ifversion fpt or ghes > 3.0 or ghae-next %} | Rename a branch, including the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" {% endif %} | 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)" | @@ -73,7 +73,7 @@ Collaborators can also perform the following actions. | 동작 | More information | |:----------------------------------------------------------------------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Fork the repository | "[About forks](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% ifversion fpt or ghes > 3.1 %} +| Fork the repository | "[About forks](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% ifversion fpt or ghes > 3.1 or ghae-next %} | 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](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)"
    • "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"
    | diff --git a/translations/ko-KR/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md b/translations/ko-KR/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md index 2484d48e5d..d2d8a049c1 100644 --- a/translations/ko-KR/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md +++ b/translations/ko-KR/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md @@ -15,8 +15,6 @@ topics: - Workflows --- -{% data reusables.actions.ae-beta %} - ## About caching workflow dependencies Workflow runs often reuse the same outputs or downloaded dependencies from one run to another. For example, package and dependency management tools such as Maven, Gradle, npm, and Yarn keep a local cache of downloaded dependencies. diff --git a/translations/ko-KR/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md b/translations/ko-KR/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md index ceb63fab08..b172e98a01 100644 --- a/translations/ko-KR/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md +++ b/translations/ko-KR/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md @@ -20,11 +20,10 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About workflow artifacts -Artifacts allow you to persist data after a job has completed, and share that data with another job in the same workflow. An artifact is a file or collection of files produced during a workflow run. For example, you can use artifacts to save your build and test output after a workflow run has ended. +Artifacts allow you to persist data after a job has completed, and share that data with another job in the same workflow. An artifact is a file or collection of files produced during a workflow run. For example, you can use artifacts to save your build and test output after a workflow run has ended. {% data reusables.actions.reusable-workflow-artifacts %} {% data reusables.github-actions.artifact-log-retention-statement %} The retention period for a pull request restarts each time someone pushes a new commit to the pull request. diff --git a/translations/ko-KR/content/actions/automating-builds-and-tests/about-continuous-integration.md b/translations/ko-KR/content/actions/automating-builds-and-tests/about-continuous-integration.md index 55c86f00bd..e5ab532a1a 100644 --- a/translations/ko-KR/content/actions/automating-builds-and-tests/about-continuous-integration.md +++ b/translations/ko-KR/content/actions/automating-builds-and-tests/about-continuous-integration.md @@ -1,6 +1,6 @@ --- title: About continuous integration -intro: 'You can create custom continuous integration (CI) and continuous deployment (CD) workflows directly in your {% data variables.product.prodname_dotcom %} repository with {% data variables.product.prodname_actions %}.' +intro: 'You can create custom continuous integration (CI) workflows directly in your {% data variables.product.prodname_dotcom %} repository with {% data variables.product.prodname_actions %}.' product: '{% data reusables.gated-features.actions %}' redirect_from: - /articles/about-continuous-integration @@ -15,13 +15,11 @@ versions: type: overview topics: - CI - - CD shortTitle: 연속 통합 --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About continuous integration @@ -49,45 +47,12 @@ In addition to helping you set up CI workflows for your project, you can use {% For a definition of common terms, see "[Core concepts for {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/core-concepts-for-github-actions)." -## Supported languages - +## Workflow templates {% data variables.product.product_name %} offers CI workflow templates for a variety of languages and frameworks. Browse the complete list of CI workflow templates offered by {% data variables.product.product_name %} in the {% ifversion fpt %}[actions/starter-workflows](https://github.com/actions/starter-workflows/tree/main/ci) repository{% else %} `actions/starter-workflows` repository on {% data variables.product.product_location %}{% endif %}. -{% ifversion fpt or ghes > 3.0 or ghae-next %} -## Skipping workflow runs - -If you want to temporarily prevent a workflow from being triggered, you can add a skip instruction to the commit message. Workflows that would otherwise be triggered `on: push` or `on: pull_request`, won't be triggered if you add any of the following strings to the commit message in a push, or the HEAD commit of a pull request: - -* `[skip ci]` -* `[ci skip]` -* `[no ci]` -* `[skip actions]` -* `[actions skip]` - -Alternatively, you can end the commit message with two empty lines followed by either `skip-checks: true` or `skip-checks:true`. - -You won't be able to merge the pull request if your repository is configured to require specific checks to pass first. To allow the pull request to be merged you can push a new commit to the pull request without the skip instruction in the commit message. - -{% note %} - -**Note:** Skip instructions only apply to the `push` and `pull_request` events. For example, adding `[skip ci]` to a commit message won't stop a workflow that's triggered `on: pull_request_target` from running. - -{% endnote %} -{% endif %} - -## Notifications for workflow runs - -{% data reusables.repositories.workflow-notifications %} - -## Status badges for workflow runs - -{% 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)." - ## 더 읽을거리 {% ifversion fpt %} diff --git a/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md b/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md index 2c040d75e0..5dec175ec1 100644 --- a/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md +++ b/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md @@ -19,7 +19,6 @@ shortTitle: Build & test Java & Ant {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md b/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md index b635d38fd5..76feb2ab38 100644 --- a/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md +++ b/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md @@ -19,7 +19,6 @@ shortTitle: Build & test Java & Gradle {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md b/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md index 9c53ad5293..ab2b3374d9 100644 --- a/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md +++ b/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md @@ -19,7 +19,6 @@ shortTitle: Build & test Java with Maven {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-net.md b/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-net.md index 816be0861b..41a70d9d53 100644 --- a/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-net.md +++ b/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-net.md @@ -13,7 +13,6 @@ shortTitle: Build & test .NET {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md b/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md index 12e70c47fb..ddf64dd147 100644 --- a/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md +++ b/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md @@ -22,7 +22,6 @@ hasExperimentalAlternative: true {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-powershell.md b/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-powershell.md index 3ddacbac49..d23ecf0873 100644 --- a/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-powershell.md +++ b/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-powershell.md @@ -19,7 +19,6 @@ shortTitle: Build & test PowerShell {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-python.md b/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-python.md index 1062e13300..6fc9b2aff2 100644 --- a/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-python.md +++ b/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-python.md @@ -21,7 +21,6 @@ hasExperimentalAlternative: true {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-ruby.md b/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-ruby.md index 4e59d5641e..29116d9d59 100644 --- a/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-ruby.md +++ b/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-ruby.md @@ -17,7 +17,6 @@ shortTitle: Build & test Ruby {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-swift.md b/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-swift.md index 0f2415d9a1..f65d7f9264 100644 --- a/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-swift.md +++ b/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-swift.md @@ -17,7 +17,6 @@ shortTitle: Build & test Swift {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md b/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md index 26703cf4f3..7ad7877c0f 100644 --- a/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md +++ b/translations/ko-KR/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md @@ -21,7 +21,6 @@ shortTitle: Build & test Xamarin apps {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ko-KR/content/actions/creating-actions/about-custom-actions.md b/translations/ko-KR/content/actions/creating-actions/about-custom-actions.md index bd6e476672..ee69433143 100644 --- a/translations/ko-KR/content/actions/creating-actions/about-custom-actions.md +++ b/translations/ko-KR/content/actions/creating-actions/about-custom-actions.md @@ -20,7 +20,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About custom actions diff --git a/translations/ko-KR/content/actions/creating-actions/creating-a-composite-action.md b/translations/ko-KR/content/actions/creating-actions/creating-a-composite-action.md index 76eb1862d0..98dc0fe49b 100644 --- a/translations/ko-KR/content/actions/creating-actions/creating-a-composite-action.md +++ b/translations/ko-KR/content/actions/creating-actions/creating-a-composite-action.md @@ -16,7 +16,6 @@ shortTitle: Composite action {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ko-KR/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/ko-KR/content/actions/creating-actions/creating-a-docker-container-action.md index d9d449f7b1..9ce1edc1e5 100644 --- a/translations/ko-KR/content/actions/creating-actions/creating-a-docker-container-action.md +++ b/translations/ko-KR/content/actions/creating-actions/creating-a-docker-container-action.md @@ -20,7 +20,6 @@ shortTitle: Docker container action {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ko-KR/content/actions/creating-actions/creating-a-javascript-action.md b/translations/ko-KR/content/actions/creating-actions/creating-a-javascript-action.md index 74ba5de150..62cab4a37c 100644 --- a/translations/ko-KR/content/actions/creating-actions/creating-a-javascript-action.md +++ b/translations/ko-KR/content/actions/creating-actions/creating-a-javascript-action.md @@ -20,7 +20,6 @@ shortTitle: JavaScript action {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ko-KR/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/translations/ko-KR/content/actions/creating-actions/dockerfile-support-for-github-actions.md index 749bf9ab45..73ee877a94 100644 --- a/translations/ko-KR/content/actions/creating-actions/dockerfile-support-for-github-actions.md +++ b/translations/ko-KR/content/actions/creating-actions/dockerfile-support-for-github-actions.md @@ -14,7 +14,6 @@ type: reference {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About Dockerfile instructions diff --git a/translations/ko-KR/content/actions/creating-actions/index.md b/translations/ko-KR/content/actions/creating-actions/index.md index e8b1782c47..1d7ed199d2 100644 --- a/translations/ko-KR/content/actions/creating-actions/index.md +++ b/translations/ko-KR/content/actions/creating-actions/index.md @@ -24,4 +24,3 @@ children: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} diff --git a/translations/ko-KR/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/ko-KR/content/actions/creating-actions/metadata-syntax-for-github-actions.md index f76752a4e6..710c251d96 100644 --- a/translations/ko-KR/content/actions/creating-actions/metadata-syntax-for-github-actions.md +++ b/translations/ko-KR/content/actions/creating-actions/metadata-syntax-for-github-actions.md @@ -17,7 +17,6 @@ type: reference {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About YAML syntax for {% data variables.product.prodname_actions %} diff --git a/translations/ko-KR/content/actions/creating-actions/publishing-actions-in-github-marketplace.md b/translations/ko-KR/content/actions/creating-actions/publishing-actions-in-github-marketplace.md index 1af4c96b4e..6ce59f7d75 100644 --- a/translations/ko-KR/content/actions/creating-actions/publishing-actions-in-github-marketplace.md +++ b/translations/ko-KR/content/actions/creating-actions/publishing-actions-in-github-marketplace.md @@ -12,8 +12,6 @@ type: how_to shortTitle: Publish in GitHub Marketplace --- -{% data reusables.actions.ae-beta %} - You must accept the terms of service to publish actions in {% data variables.product.prodname_marketplace %}. ## About publishing actions diff --git a/translations/ko-KR/content/actions/creating-actions/setting-exit-codes-for-actions.md b/translations/ko-KR/content/actions/creating-actions/setting-exit-codes-for-actions.md index 3d00fb0a48..3993a37c13 100644 --- a/translations/ko-KR/content/actions/creating-actions/setting-exit-codes-for-actions.md +++ b/translations/ko-KR/content/actions/creating-actions/setting-exit-codes-for-actions.md @@ -14,7 +14,6 @@ type: how_to {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About exit codes diff --git a/translations/ko-KR/content/actions/deployment/about-continuous-deployment.md b/translations/ko-KR/content/actions/deployment/about-continuous-deployment.md new file mode 100644 index 0000000000..2a2d642517 --- /dev/null +++ b/translations/ko-KR/content/actions/deployment/about-continuous-deployment.md @@ -0,0 +1,41 @@ +--- +title: About continuous deployment +intro: 'You can create custom continuous deployment (CD) workflows directly in your {% data variables.product.prodname_dotcom %} repository with {% data variables.product.prodname_actions %}.' +product: '{% data reusables.gated-features.actions %}' +versions: + fpt: '*' + ghes: '*' + ghae: '*' +type: overview +topics: + - CD +shortTitle: Continuous deployment +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +## About continuous deployment + +_Continuous deployment_ (CD) is the practice of using automation to publish and deploy software updates. As part of the typical CD process, the code is automatically built and tested before deployment. + +Continuous deployment is often coupled with continuous integration. For more information about continuous integration, see "[About continuous integration](/actions/guides/about-continuous-integration)". + +## About continuous deployment using {% data variables.product.prodname_actions %} + +You can set up a {% data variables.product.prodname_actions %} workflow to deploy your software product. To verify that your product works as expected, your workflow can build the code in your repository and run your tests before deploying. + +You can configure your CD workflow to run when a {% data variables.product.product_name %} event occurs (for example, when new code is pushed to the default branch of your repository), on a set schedule, manually, or when an external event occurs using the repository dispatch webhook. For more information about when your workflow can run, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)." + +{% data variables.product.prodname_actions %} provides features that give you more control over deployments. For example, you can use environments to require approval for a job to proceed, restrict which branches can trigger a workflow, or limit access to secrets. You can use concurrency to limit your CD pipeline to a maximum of one in-progress deployment and one pending deployment. For more information about these features, see "[Deploying with GitHub Actions](/actions/deployment/deploying-with-github-actions)" and "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." + +## Workflow templates and third party actions + +{% data reusables.actions.cd-templates-actions %} + +## 더 읽을거리 + +- [Deploying with GitHub Actions](/actions/deployment/deploying-with-github-actions) +- [Using environments for deployment](/actions/deployment/using-environments-for-deployment){% ifversion fpt %} +- "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)" +{% endif %} diff --git a/translations/ko-KR/content/actions/deployment/deploying-to-amazon-elastic-container-service.md b/translations/ko-KR/content/actions/deployment/deploying-to-amazon-elastic-container-service.md index 9a794d7951..70de148527 100644 --- a/translations/ko-KR/content/actions/deployment/deploying-to-amazon-elastic-container-service.md +++ b/translations/ko-KR/content/actions/deployment/deploying-to-amazon-elastic-container-service.md @@ -18,11 +18,10 @@ shortTitle: Deploy to Amazon ECS {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction -This guide explains how to use {% data variables.product.prodname_actions %} to build a containerized application, push it to [Amazon Elastic Container Registry (ECR)](https://aws.amazon.com/ecr/), and deploy it to [Amazon Elastic Container Service (ECS)](https://aws.amazon.com/ecs/). +This guide explains how to use {% data variables.product.prodname_actions %} to build a containerized application, push it to [Amazon Elastic Container Registry (ECR)](https://aws.amazon.com/ecr/), and deploy it to [Amazon Elastic Container Service (ECS)](https://aws.amazon.com/ecs/) when a release is created. On every new release in your {% data variables.product.company_short %} repository, the {% data variables.product.prodname_actions %} workflow builds and pushes a new container image to Amazon ECR, and then deploys a new task definition to Amazon ECS. @@ -66,6 +65,8 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you See the documentation for each action used below for the recommended IAM policies for the IAM user, and methods for handling the access key credentials. +5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %} + ## Creating the workflow Once you've completed the prerequisites, you can proceed with creating the workflow. @@ -74,6 +75,8 @@ The following example workflow demonstrates how to build a container image and p Ensure that you provide your own values for all the variables in the `env` key of the workflow. +{% data reusables.actions.delete-env-key %} + ```yaml{:copy} {% data reusables.actions.actions-not-certified-by-github-comment %} @@ -93,17 +96,11 @@ env: CONTAINER_NAME: MY_CONTAINER_NAME # set this to the name of the container in the # containerDefinitions section of your task definition -defaults: - run: - shell: bash - jobs: deploy: name: Deploy - runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae-next %} - permissions: - packages: write - contents: read{% endif %} + runs-on: ubuntu-latest + environment: production {% raw %}steps: - name: Checkout @@ -150,9 +147,10 @@ jobs: wait-for-service-stability: true{% endraw %} ``` - ## Additional resources +For the original starter workflow, see [`aws.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/aws.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository. + For more information on the services used in these examples, see the following documentation: * "[Security best practices in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html)" in the Amazon AWS documentation. diff --git a/translations/ko-KR/content/actions/deployment/deploying-to-azure-app-service.md b/translations/ko-KR/content/actions/deployment/deploying-to-azure-app-service.md index 694ab97a53..9f2850ed4c 100644 --- a/translations/ko-KR/content/actions/deployment/deploying-to-azure-app-service.md +++ b/translations/ko-KR/content/actions/deployment/deploying-to-azure-app-service.md @@ -18,7 +18,6 @@ shortTitle: Deploy to Azure App Service {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction @@ -68,13 +67,19 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you In your {% data variables.product.prodname_dotcom %} repository, create a secret named `AZURE_WEBAPP_PUBLISH_PROFILE` that contains the contents of the publish profile. For more information on creating secrets, see "[Encrypted secrets](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)." +4. For Linux apps, add an app setting called `WEBSITE_WEBDEPLOY_USE_SCM` and set it to true in your app. For more information, see "[Configure apps in the portal](https://docs.microsoft.com/en-us/azure/app-service/configure-common#configure-app-settings)" in the Azure documentation. + +5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %} + ## Creating the workflow Once you've completed the prerequisites, you can proceed with creating the workflow. -The following example workflow demonstrates how to build, test, and deploy the Node.js project to Azure App Service. +The following example workflow demonstrates how to build, test, and deploy the Node.js project to Azure App Service when a release is created. -Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created. +Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created. You can also change `AZURE_WEBAPP_PACKAGE_PATH` if the path to your project is not the repository root and `NODE_VERSION` if you want to use a node version other than `10.x`. + +{% data reusables.actions.delete-env-key %} ```yaml{:copy} {% data reusables.actions.actions-not-certified-by-github-comment %} @@ -92,6 +97,8 @@ jobs: build-and-deploy: name: Build and Deploy runs-on: ubuntu-latest + environment: production + steps: - uses: actions/checkout@v2 @@ -122,4 +129,5 @@ The following resources may also be useful: * For the original starter workflow, see [`azure.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository. * 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/en-us/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). diff --git a/translations/ko-KR/content/actions/deployment/deploying-to-google-kubernetes-engine.md b/translations/ko-KR/content/actions/deployment/deploying-to-google-kubernetes-engine.md index fe15f9a1a3..1885dfde37 100644 --- a/translations/ko-KR/content/actions/deployment/deploying-to-google-kubernetes-engine.md +++ b/translations/ko-KR/content/actions/deployment/deploying-to-google-kubernetes-engine.md @@ -13,16 +13,15 @@ topics: - CD - Containers - Google Kubernetes Engine -shortTitle: Deploy to Kubernetes (GKE) +shortTitle: Deploy to Google Kubernetes Engine --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction -This guide explains how to use {% data variables.product.prodname_actions %} to build a containerized application, push it to Google Container Registry (GCR), and deploy it to Google Kubernetes Engine (GKE). +This guide explains how to use {% data variables.product.prodname_actions %} to build a containerized application, push it to Google Container Registry (GCR), and deploy it to Google Kubernetes Engine (GKE) when a release is created. GKE is a managed Kubernetes cluster service from Google Cloud that can host your containerized workloads in the cloud or in your own datacenter. For more information, see [Google Kubernetes Engine](https://cloud.google.com/kubernetes-engine). @@ -61,7 +60,7 @@ $ gcloud services enable \ ### Configuring a service account and storing its credentials -This procedure demonstrates how to create the service account for your GKE integration. It explains how to create the account, add roles to it, retrieve its keys, and store them as a base64-encoded [encrypted repository secret](/actions/reference/encrypted-secrets) named `GKE_SA_KEY`. +This procedure demonstrates how to create the service account for your GKE integration. It explains how to create the account, add roles to it, retrieve its keys, and store them as a base64-encoded encrypted repository secret named `GKE_SA_KEY`. 1. Create a new service account: {% raw %} @@ -97,16 +96,29 @@ This procedure demonstrates how to create the service account for your GKE integ $ export GKE_SA_KEY=$(cat key.json | base64) ``` {% endraw %} + For more information about how to store a secret, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)." + +### Storing your project name + +Store the name of your project as a secret named `GKE_PROJECT`. For more information about how to store a secret, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)." ### (Optional) Configuring kustomize Kustomize is an optional tool used for managing YAML specs. After creating a _kustomization_ file, the workflow below can be used to dynamically set fields of the image and pipe in the result to `kubectl`. For more information, see [kustomize usage](https://github.com/kubernetes-sigs/kustomize#usage). +### (Optional) Configure a deployment environment + +{% data reusables.actions.about-environments %} + ## Creating the workflow Once you've completed the prerequisites, you can proceed with creating the workflow. The following example workflow demonstrates how to build a container image and push it to GCR. It then uses the Kubernetes tools (such as `kubectl` and `kustomize`) to pull the image into the cluster deployment. +Under the `env` key, change the value of `GKE_CLUSTER` to the name of your cluster, `GKE_ZONE` to your cluster zone, `DEPLOYMENT_NAME` to the name of your deployment, and `IMAGE` to the name of your image. + +{% data reusables.actions.delete-env-key %} + ```yaml{:copy} {% data reusables.actions.actions-not-certified-by-github-comment %} @@ -127,8 +139,9 @@ jobs: setup-build-publish-deploy: name: Setup, Build, Publish, and Deploy runs-on: ubuntu-latest - steps: + environment: production + steps: - name: Checkout uses: actions/checkout@v2 @@ -138,7 +151,8 @@ jobs: service_account_key: {% raw %}${{ secrets.GKE_SA_KEY }}{% endraw %} project_id: {% raw %}${{ secrets.GKE_PROJECT }}{% endraw %} - # Configure docker to use the gcloud command-line tool as a credential helper + # Configure Docker to use the gcloud command-line tool as a credential + # helper for authentication - run: |- gcloud --quiet auth configure-docker @@ -166,7 +180,7 @@ jobs: # Set up kustomize - name: Set up Kustomize run: |- - curl --location https://github.com/kubernetes-sigs/kustomize/releases/download/kustomize%2Fv4.2.0/kustomize_v4.2.0_linux_amd64.tar.gz | tar xz + curl -sfLo kustomize https://github.com/kubernetes-sigs/kustomize/releases/download/v3.1.0/kustomize_3.1.0_linux_amd64 chmod u+x ./kustomize # Deploy the Docker image to the GKE cluster diff --git a/translations/ko-KR/content/actions/deployment/deploying-with-github-actions.md b/translations/ko-KR/content/actions/deployment/deploying-with-github-actions.md new file mode 100644 index 0000000000..3c6438831c --- /dev/null +++ b/translations/ko-KR/content/actions/deployment/deploying-with-github-actions.md @@ -0,0 +1,173 @@ +--- +title: Deploying with GitHub Actions +intro: Learn how to control deployments with features like environments and concurrency. +product: '{% data reusables.gated-features.actions %}' +versions: + fpt: '*' + ghes: '>=3.1' + ghae: '*' +type: overview +topics: + - CD +shortTitle: Deploy with 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: + +- 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)." + +## 빌드전 요구 사양 + +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)." + +## Triggering your deployment + +You can use a variety of events to trigger your deployment workflow. Some of the most common are: `pull_request`, `push`, `release`, and `workflow_dispatch`. + +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. +- A release is created. +- Someone manually triggers it. + +```yaml +on: + push: + branches: + - main + pull_request: + branches: + - main + release: + types: + - created + workflow_dispatch: +``` + +For more information, see "[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. + +{% 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. + +```yaml +name: Deployment + +concurrency: production + +on: + push: + branches: + - main + +jobs: + deployment: + runs-on: ubuntu-latest + environment: production + steps: + - name: deploy + # ...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`. + +```yaml +name: Deployment + +on: + push: + branches: + - main + +jobs: + deployment: + runs-on: ubuntu-latest + environment: production + concurrency: production + steps: + - name: deploy + # ...deployment-specific steps +``` + +You can also use `cancel-in-progress` to cancel any currently running job or workflow in the same concurrency group. + +```yaml +name: Deployment + +concurrency: + group: production + cancel-in-progress: true + +on: + push: + branches: + - main + +jobs: + deployment: + runs-on: ubuntu-latest + environment: production + steps: + - name: deploy + # ...deployment-specific steps +``` + +## 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)." + +## 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)." + +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)." + +## Tracking deployments through apps + +{% ifversion fpt %} +If your {% data variables.product.product_name %} personal account or organization 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)." +{% 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)." + +{% ifversion fpt or ghes %} + +## Choosing a runner + +You can run your deployment workflow on {% data variables.product.product_name %}-hosted runners or on self-hosted runners. Traffic from {% data variables.product.product_name %}-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.product_name %}-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)." + +{% 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 %} + +For more information, see "[Adding a workflow status badge](/actions/managing-workflow-runs/adding-a-workflow-status-badge)." + +## 다음 단계 + +This article demonstrated features of {% data variables.product.prodname_actions %} that you can add to your deployment workflows. + +{% data reusables.actions.cd-templates-actions %} diff --git a/translations/ko-KR/content/actions/deployment/index.md b/translations/ko-KR/content/actions/deployment/index.md index 2ae385cc62..0fbfa9c440 100644 --- a/translations/ko-KR/content/actions/deployment/index.md +++ b/translations/ko-KR/content/actions/deployment/index.md @@ -7,10 +7,13 @@ versions: ghes: '*' ghae: '*' children: + - /about-continuous-deployment + - /deploying-with-github-actions + - /using-environments-for-deployment + - /viewing-deployment-history - /deploying-to-amazon-elastic-container-service - /deploying-to-azure-app-service - /deploying-to-google-kubernetes-engine - /installing-an-apple-certificate-on-macos-runners-for-xcode-development - - /environments --- diff --git a/translations/ko-KR/content/actions/deployment/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md b/translations/ko-KR/content/actions/deployment/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md index 130c4c8a5d..8304195cbc 100644 --- a/translations/ko-KR/content/actions/deployment/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md +++ b/translations/ko-KR/content/actions/deployment/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md @@ -17,7 +17,6 @@ shortTitle: Sign Xcode applications {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ko-KR/content/actions/deployment/using-environments-for-deployment.md b/translations/ko-KR/content/actions/deployment/using-environments-for-deployment.md new file mode 100644 index 0000000000..8bdaa620eb --- /dev/null +++ b/translations/ko-KR/content/actions/deployment/using-environments-for-deployment.md @@ -0,0 +1,126 @@ +--- +title: Using environments for deployment +shortTitle: Use environments for deployment +intro: You can configure environments with protection rules and secrets. A workflow job that references an environment must follow any protection rules for the environment before running or accessing the environment's secrets. +product: '{% data reusables.gated-features.environments %}' +miniTocMaxHeadingLevel: 3 +redirect_from: + - /actions/reference/environments + - /actions/deployment/environments +versions: + fpt: '*' + ghes: '>=3.1' + ghae: '*' +--- + + +## About environments + +Environments are used to describe a general deployment target like `production`, `staging`, or `development`. 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)." + +You can configure environments with protection rules and secrets. When a workflow job references an environment, the job won't start until all of the environment's protection rules pass. A job also cannot access secrets that are defined in an environment until all the environment protection rules pass. + +{% ifversion fpt %} +{% note %} + +**Note:** If you don't use {% data variables.product.prodname_ghe_cloud %} and convert a repository from public to private, any configured protection rules or environment secrets will be ignored, and you will not be able to configure any environments. If you convert your repository back to public, you will have access to any previously configured protection rules and environment secrets. {% data reusables.enterprise.link-to-ghec-trial %} + +{% endnote %} +{% endif %} + +## Environment protection rules + +Environment protection rules require specific conditions to pass before a job referencing the environment can proceed. {% ifversion fpt or ghae-next or ghes > 3.1 %}You can use environment protection rules to require a manual approval, delay a job, or restrict the environment to certain branches.{% else %}You can use environment protection rules to require a manual approval or delay a job.{% endif %} + +### Required reviewers + +Use required reviewers to require a specific person or team to approve workflow jobs that reference the environment. You can list up to six users or teams as reviewers. The reviewers must have at least read access to the repository. Only one of the required reviewers needs to approve the job for it to proceed. + +For more information on reviewing jobs that reference an environment with required reviewers, see "[Reviewing deployments](/actions/managing-workflow-runs/reviewing-deployments)." + +### Wait timer + +Use a wait timer to delay a job for a specific amount of time after the job is initially triggered. The time (in minutes) must be an integer between 0 and 43,200 (30 days). + +{% ifversion fpt or ghae-next or ghes > 3.1 %} +### Deployment branches + +Use deployment branches to restrict which branches can deploy to the environment. Below are the options for deployment branches for an environment: + +* **All branches**: All branches in the repository can deploy to the environment. +* **Protected branches**: Only branches with branch protection rules enabled can deploy to the environment. If no branch protection rules are defined for any branch in the repository, then all branches can deploy. For more information about branch protection rules, see "[About protected branches](/github/administering-a-repository/about-protected-branches)." +* **Selected branches**: Only branches that match your specified name patterns can deploy to the environment. + + For example, if you specify `releases/*` as a deployment branch rule, only branches whose name begins with `releases/` can deploy to the environment. (Wildcard characters will not match `/`. To match branches that begin with `release/` and contain an additional single slash, use `release/*/*`.) If you add `main` as a deployment branch rule, a branch named `main` can also deploy to the environment. For more information about syntax options for deployment branches, see the [Ruby File.fnmatch documentation](https://ruby-doc.org/core-2.5.1/File.html#method-c-fnmatch). +{% endif %} +## Environment secrets + +Secrets stored in an environment are only available to workflow jobs that reference the environment. If the environment requires approval, a job cannot access environment secrets until one of the required reviewers approves it. For more information about secrets, see "[Encrypted secrets](/actions/reference/encrypted-secrets)." + +{% note %} + +**Note:** Workflows that run on self-hosted runners are not run in an isolated container, even if they use environments. Environment secrets should be treated with the same level of security as repository and organization secrets. For more information, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#hardening-for-self-hosted-runners)." + +{% endnote %} + +## Creating an environment + +{% data reusables.github-actions.permissions-statement-environment %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.github-actions.sidebar-environment %} +{% data reusables.github-actions.new-environment %} +{% data reusables.github-actions.name-environment %} +1. Optionally, specify people or teams that must approve workflow jobs that use this environment. + 1. Select **Required reviewers**. + 1. Enter up to 6 people or teams. Only one of the required reviewers needs to approve the job for it to proceed. + 1. Click **Save protection rules**. +2. Optionally, specify the amount of time to wait before allowing workflow jobs that use this environment to proceed. + 1. Select **Wait timer**. + 1. Enter the number of minutes to wait. + 1. Click **Save protection rules**. +3. Optionally, specify what branches can deploy to this environment. For more information about the possible values, see "[Deployment branches](#deployment-branches)." + 1. Select the desired option in the **Deployment branches** dropdown. + 1. If you chose **Selected branches**, enter the branch name patterns that you want to allow. +4. Optionally, add environment secrets. These secrets are only available to workflow jobs that use the environment. Additionally, workflow jobs that use this environment can only access these secrets after any configured rules (for example, required reviewers) pass. For more information about secrets, see "[Encrypted secrets](/actions/reference/encrypted-secrets)." + 1. Under **Environment secrets**, click **Add Secret**. + 1. Enter the secret name. + 1. Enter the secret value. + 1. Click **Add secret**. + +{% ifversion fpt or ghae-next or ghes > 3.1 %}You can also create and configure environments through the REST API. For more information, see "[Environments](/rest/reference/repos#environments)" and "[Secrets](/rest/reference/actions#secrets)."{% endif %} + +Running a workflow that references an environment that does not exist will create an environment with the referenced name. The newly created environment will not have any protection rules or secrets configured. Anyone that can edit workflows in the repository can create environments via a workflow file, but only repository admins can configure the environment. + +## Using an environment + +Each job in a workflow can reference a single environment. Any protection rules configured for the environment must pass before a job referencing the environment is sent to a runner. The job can access the environment's secrets only after the job is sent to a runner. + +When a workflow references an environment, the environment will appear in the repository's deployments. For more information about viewing current and previous deployments, see "[Viewing deployment history](/developers/overview/viewing-deployment-history)." + +{% data reusables.actions.environment-example %} + +## Deleting an environment + +{% data reusables.github-actions.permissions-statement-environment %} + +Deleting an environment will delete all secrets and protection rules associated with the environment. Any jobs currently waiting because of protection rules from the deleted environment will automatically fail. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.github-actions.sidebar-environment %} +1. Next to the environment that you want to delete, click {% octicon "trash" aria-label="The trash icon" %}. +2. Click **I understand, delete this environment**. + +{% ifversion fpt or ghae-next or ghes > 3.1 %}You can also delete environments through the REST API. For more information, see "[Environments](/rest/reference/repos#environments)."{% endif %} + +## How environments relate to deployments + +{% data reusables.actions.environment-deployment-event %} + +You can access these objects through the REST API or GraphQL API. You can also subscribe to these webhook events. For more information, see "[Repositories](/rest/reference/repos#deployments)" (REST API), "[Objects](/graphql/reference/objects#deployment)" (GraphQL API), or "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#deployment)." + +## 다음 단계 + +{% data variables.product.prodname_actions %} provides several features for managing your deployments. For more information, see "[Deploying with GitHub Actions](/actions/deployment/deploying-with-github-actions)." diff --git a/translations/ko-KR/content/actions/deployment/viewing-deployment-history.md b/translations/ko-KR/content/actions/deployment/viewing-deployment-history.md new file mode 100644 index 0000000000..16f184214e --- /dev/null +++ b/translations/ko-KR/content/actions/deployment/viewing-deployment-history.md @@ -0,0 +1,27 @@ +--- +title: Viewing deployment history +intro: View current and previous deployments for your repository. +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - API +shortTitle: View deployment history +redirect_from: + - /developers/overview/viewing-deployment-history +--- + + +You can deliver deployments through {% ifversion fpt or ghae or ghes > 3.0 %}{% data variables.product.prodname_actions %} and environments or with {% endif %}the REST API and third party apps. {% ifversion fpt or ghae ghes > 3.0 %}For more information about using environments to deploy with {% data variables.product.prodname_actions %}, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." {% endif %}For more information about deployments with the REST API, see "[Repositories](/rest/reference/repos#deployments)." + +To view current and past deployments, click **Environments** on the home page of your repository. +{% ifversion ghae or ghes < 3.0 %} +![Environments](/assets/images/enterprise/2.22/environments-sidebar.png){% else %} +![Environments](/assets/images/environments-sidebar.png){% endif %} + +The deployments page displays the last active deployment of each environment for your repository. If the deployment includes an environment URL, a **View deployment** button that links to the URL is shown next to the deployment. + +The activity log shows the deployment history for your environments. By default, only the most recent deployment for an environment has an `Active` status; all previously active deployments have an `Inactive` status. For more information on automatic inactivation of deployments, see "[Inactive deployments](/rest/reference/repos#inactive-deployments)." + +You can also use the REST API to get information about deployments. For more information, see "[Repositories](/rest/reference/repos#deployments)." diff --git a/translations/ko-KR/content/actions/hosting-your-own-runners/about-self-hosted-runners.md b/translations/ko-KR/content/actions/hosting-your-own-runners/about-self-hosted-runners.md index b543615f2a..d496e1e35d 100644 --- a/translations/ko-KR/content/actions/hosting-your-own-runners/about-self-hosted-runners.md +++ b/translations/ko-KR/content/actions/hosting-your-own-runners/about-self-hosted-runners.md @@ -14,7 +14,6 @@ type: overview {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About self-hosted runners @@ -172,7 +171,9 @@ You can also use self-hosted runners with a proxy server. For more information, ## Self-hosted runner security with public repositories +{% ifversion not ghae %} {% data reusables.github-actions.self-hosted-runner-security %} +{% endif %} This is not an issue with {% data variables.product.prodname_dotcom %}-hosted runners because each {% data variables.product.prodname_dotcom %}-hosted runner is always a clean isolated virtual machine, and it is destroyed at the end of the job execution. diff --git a/translations/ko-KR/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md b/translations/ko-KR/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md index 9a570e2545..dc34c77fc9 100644 --- a/translations/ko-KR/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md +++ b/translations/ko-KR/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md @@ -15,7 +15,6 @@ shortTitle: Add self-hosted runners {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} You can add a self-hosted runner to a repository, an organization, or an enterprise. @@ -23,6 +22,7 @@ If you are an organization or enterprise administrator, you might want to add yo For information on supported operating systems for self-hosted runners, or using self-hosted runners with a proxy server, see "[About self-hosted runners](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)." +{% ifversion not ghae %} {% warning %} **Warning:** {% data reusables.github-actions.self-hosted-runner-security %} @@ -30,6 +30,7 @@ For information on supported operating systems for self-hosted runners, or using For more information, see "[About self-hosted runners](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)." {% endwarning %} +{% endif %} ## Adding a self-hosted runner to a repository @@ -48,7 +49,7 @@ You can add self-hosted runners to a single repository. To add a self-hosted run {% data reusables.repositories.sidebar-settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} 1. Under -{% ifversion fpt %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**. +{% ifversion fpt or ghes > 3.1 or ghae %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**. {% data reusables.github-actions.self-hosted-runner-configure %} {% endif %} {% data reusables.github-actions.self-hosted-runner-check-installation-success %} @@ -70,7 +71,7 @@ You can add self-hosted runners at the organization level, where they can be use {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} 1. Under -{% ifversion fpt %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**. +{% ifversion fpt or ghes > 3.1 or ghae %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**. {% data reusables.github-actions.self-hosted-runner-configure %} {% endif %} diff --git a/translations/ko-KR/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md b/translations/ko-KR/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md index 9a049714a9..a54e972f26 100644 --- a/translations/ko-KR/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md +++ b/translations/ko-KR/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md @@ -10,7 +10,6 @@ type: overview {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About autoscaling diff --git a/translations/ko-KR/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md b/translations/ko-KR/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md index be2584a4df..de46a37697 100644 --- a/translations/ko-KR/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md +++ b/translations/ko-KR/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md @@ -15,7 +15,6 @@ shortTitle: Run runner app on startup {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% capture service_first_step %}1. Stop the self-hosted runner application if it is currently running.{% endcapture %} {% capture service_non_windows_intro_shell %}On the runner machine, open a shell in the directory where you installed the self-hosted runner application. Use the commands below to install and manage the self-hosted runner service.{% endcapture %} diff --git a/translations/ko-KR/content/actions/hosting-your-own-runners/index.md b/translations/ko-KR/content/actions/hosting-your-own-runners/index.md index 6fe2e32cb2..d2fb39d810 100644 --- a/translations/ko-KR/content/actions/hosting-your-own-runners/index.md +++ b/translations/ko-KR/content/actions/hosting-your-own-runners/index.md @@ -24,4 +24,3 @@ children: {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} diff --git a/translations/ko-KR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md b/translations/ko-KR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md index da2c2a6620..47184738cf 100644 --- a/translations/ko-KR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md +++ b/translations/ko-KR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md @@ -14,7 +14,6 @@ shortTitle: Manage runner groups {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About self-hosted runner groups @@ -173,14 +172,13 @@ Could not find any self-hosted runner group named "rg-runnergroup". ## Moving a self-hosted runner to a group If you don't specify a runner group during the registration process, your new self-hosted runners are automatically assigned to the default group, and can then be moved to another group. -{% ifversion fpt %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} 1. In the "Runners" list, click the runner that you want to configure. 1. Select the Runner group dropdown menu. 1. In "Move runner to group", choose a destination group for the runner. -{% endif %} -{% ifversion ghae or ghes %} -1. In the {% ifversion fpt %}"Runners"{% else %}"Self-hosted runners"{% endif %} section of the settings page, locate the current group of the runner you want to move and expand the list of group members. ![View runner group members](/assets/images/help/settings/actions-org-runner-group-members.png) +{% else %} +1. In the "Self-hosted runners" section of the settings page, locate the current group of the runner you want to move and expand the list of group members. ![View runner group members](/assets/images/help/settings/actions-org-runner-group-members.png) 1. Select the checkbox next to the self-hosted runner, and then click **Move to group** to see the available destinations. ![Runner group member move](/assets/images/help/settings/actions-org-runner-group-member-move.png) 1. To move the runner, click on the destination group. ![Runner group member move](/assets/images/help/settings/actions-org-runner-group-member-move-destination.png) {% endif %} @@ -188,14 +186,13 @@ If you don't specify a runner group during the registration process, your new se Self-hosted runners are automatically returned to the default group when their group is removed. -{% ifversion fpt %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} {% data reusables.github-actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %} 1. In the list of groups, to the right of the group you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. 1. To remove the group, click **Remove group**. 1. Review the confirmation prompts, and click **Remove this runner group**. -{% endif %} -{% ifversion ghae or ghes %} -1. In the {% ifversion fpt %}"Runners"{% else %}"Self-hosted runners"{% endif %} section of the settings page, locate the group you want to delete, and click the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} button. ![View runner group settings](/assets/images/help/settings/actions-org-runner-group-kebab.png) +{% else %} +1. In the "Self-hosted runners" section of the settings page, locate the group you want to delete, and click the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} button. ![View runner group settings](/assets/images/help/settings/actions-org-runner-group-kebab.png) 1. To remove the group, click **Remove group**. ![View runner group settings](/assets/images/help/settings/actions-org-runner-group-remove.png) diff --git a/translations/ko-KR/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md b/translations/ko-KR/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md index f05e1d2c8b..1d0408eddc 100644 --- a/translations/ko-KR/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md +++ b/translations/ko-KR/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md @@ -17,7 +17,6 @@ shortTitle: Monitor & troubleshoot {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Checking the status of a self-hosted runner @@ -25,7 +24,7 @@ shortTitle: Monitor & troubleshoot {% data reusables.github-actions.self-hosted-runner-navigate-repo-and-org %} {% data reusables.github-actions.settings-sidebar-actions-runners %} -1. Under {% ifversion fpt %}"Runners"{% else %}"Self-hosted runners"{% endif %}, you can view a list of registered runners, including the runner's name, labels, and status. +1. Under {% ifversion fpt or ghes > 3.1 or ghae-next %}"Runners"{% else %}"Self-hosted runners"{% endif %}, you can view a list of registered runners, including the runner's name, labels, and status. The status can be one of the following: diff --git a/translations/ko-KR/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md b/translations/ko-KR/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md index 284e7929d8..a545e0468c 100644 --- a/translations/ko-KR/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md +++ b/translations/ko-KR/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md @@ -15,7 +15,6 @@ shortTitle: Remove self-hosted runners {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Removing a runner from a repository @@ -57,15 +56,14 @@ To remove a self-hosted runner from a user repository you must be the repository To remove a self-hosted runner from an organization, you must be an organization owner. We recommend that you also have access to the self-hosted runner machine. {% data reusables.github-actions.self-hosted-runner-reusing %} -{% ifversion fpt %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions %} {% data reusables.github-actions.settings-sidebar-actions-runners-updated %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %} -{% endif %} -{% ifversion ghae or ghes %} +{% else %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} @@ -90,10 +88,9 @@ To remove a self-hosted runner from an enterprise account, you must be an enterp {% data reusables.enterprise-accounts.actions-runners-tab %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes %} To remove a self-hosted runner at the enterprise level of -{% data variables.product.product_location %}, you must be a site administrator. We recommend that you also have access to the self-hosted runner machine. +{% data variables.product.product_location %}, you must be an enterprise owner. We recommend that you also have access to the self-hosted runner machine. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} diff --git a/translations/ko-KR/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md b/translations/ko-KR/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md index 16bd9b7eca..c3cd43ba6e 100644 --- a/translations/ko-KR/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md +++ b/translations/ko-KR/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md @@ -14,7 +14,6 @@ shortTitle: Proxy servers {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Configuring a proxy server using environment variables diff --git a/translations/ko-KR/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md b/translations/ko-KR/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md index a1dc450503..1c1c1ef6d4 100644 --- a/translations/ko-KR/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md +++ b/translations/ko-KR/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md @@ -12,7 +12,6 @@ shortTitle: Label runners {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} For information on how to use labels to route jobs to specific types of self-hosted runners, see "[Using self-hosted runners in a workflow](/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow)." diff --git a/translations/ko-KR/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md b/translations/ko-KR/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md index 783159fd24..8a2213218f 100644 --- a/translations/ko-KR/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md +++ b/translations/ko-KR/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md @@ -15,7 +15,6 @@ shortTitle: Use runners in a workflow {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} For information on creating custom and default labels, see "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)." diff --git a/translations/ko-KR/content/actions/index.md b/translations/ko-KR/content/actions/index.md index 7c805084e4..d0e2899145 100644 --- a/translations/ko-KR/content/actions/index.md +++ b/translations/ko-KR/content/actions/index.md @@ -9,6 +9,7 @@ featuredLinks: guides: - /actions/learn-github-actions - /actions/guides/about-continuous-integration + - /actions/deployment/deploying-with-github-actions - /actions/guides/about-packaging-with-github-actions - /actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting guideCards: diff --git a/translations/ko-KR/content/actions/learn-github-actions/contexts.md b/translations/ko-KR/content/actions/learn-github-actions/contexts.md index 6e4b779215..c0ffb53287 100644 --- a/translations/ko-KR/content/actions/learn-github-actions/contexts.md +++ b/translations/ko-KR/content/actions/learn-github-actions/contexts.md @@ -18,7 +18,6 @@ miniTocMaxHeadingLevel: 3 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About contexts @@ -61,27 +60,29 @@ The `github` context contains information about the workflow run and the event t {% data reusables.github-actions.github-context-warning %} {% data reusables.github-actions.context-injection-warning %} -| Property name | 유형 | 설명 | -| ------------------------- | ----- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `github` | `개체` | The top-level context available during any job or step in a workflow. | -| `github.action` | `문자열` | The name of the action currently running. {% data variables.product.prodname_dotcom %} removes special characters or uses the name `run` when the current step runs a script. If you use the same action more than once in the same job, the name will include a suffix with the sequence number. For example, the first script you run will have the name `run1`, and the second script will be named `run2`. Similarly, the second invocation of `actions/checkout` will be `actionscheckout2`. | -| `github.action_path` | `문자열` | The path where your action is located. You can use this path to easily access files located in the same repository as your action. This attribute is only supported in composite actions. | -| `github.actor` | `문자열` | The login of the user that initiated the workflow run. | -| `github.base_ref` | `문자열` | The `base_ref` or target branch of the pull request in a workflow run. This property is only available when the event that triggers a workflow run is either `pull_request` or `pull_request_target`. | -| `github.event` | `개체` | The full event webhook payload. For more information, see "[Events that trigger workflows](/articles/events-that-trigger-workflows/)." You can access individual properties of the event using this context. | -| `github.event_name` | `문자열` | The name of the event that triggered the workflow run. | -| `github.event_path` | `문자열` | The path to the full event webhook payload on the runner. | -| `github.head_ref` | `문자열` | The `head_ref` or source branch of the pull request in a workflow run. This property is only available when the event that triggers a workflow run is either `pull_request` or `pull_request_target`. | -| `github.job` | `문자열` | The [`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) of the current job. | -| `github.ref` | `문자열` | The branch or tag ref that triggered the workflow run. For branches this is the format `refs/heads/`, and for tags it is `refs/tags/`. | -| `github.repository` | `문자열` | The owner and repository name. For example, `Codertocat/Hello-World`. | -| `github.repository_owner` | `문자열` | The repository owner's name. For example, `Codertocat`. | +| Property name | 유형 | 설명 | +| ------------------------- | ----- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `github` | `개체` | The top-level context available during any job or step in a workflow. | +| `github.action` | `문자열` | The name of the action currently running. {% data variables.product.prodname_dotcom %} removes special characters or uses the name `__run` when the current step runs a script. If you use the same action more than once in the same job, the name will include a suffix with the sequence number with underscore before it. For example, the first script you run will have the name `__run`, and the second script will be named `__run_2`. Similarly, the second invocation of `actions/checkout` will be `actionscheckout2`. | +| `github.action_path` | `문자열` | The path where your action is located. You can use this path to easily access files located in the same repository as your action. This attribute is only supported in composite actions. | +| `github.actor` | `문자열` | The login of the user that initiated the workflow run. | +| `github.base_ref` | `문자열` | The `base_ref` or target branch of the pull request in a workflow run. This property is only available when the event that triggers a workflow run is either `pull_request` or `pull_request_target`. | +| `github.event` | `개체` | The full event webhook payload. For more information, see "[Events that trigger workflows](/articles/events-that-trigger-workflows/)." You can access individual properties of the event using this context. | +| `github.event_name` | `문자열` | The name of the event that triggered the workflow run. | +| `github.event_path` | `문자열` | The path to the full event webhook payload on the runner. | +| `github.head_ref` | `문자열` | The `head_ref` or source branch of the pull request in a workflow run. This property is only available when the event that triggers a workflow run is either `pull_request` or `pull_request_target`. | +| `github.job` | `문자열` | The [`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) of the current job. | +| `github.ref` | `문자열` | The branch or tag ref that triggered the workflow run. For branches this is the format `refs/heads/`, and for tags it is `refs/tags/`. | +| `github.repository` | `문자열` | The owner and repository name. For example, `Codertocat/Hello-World`. | +| `github.repository_owner` | `문자열` | The repository owner's name. For example, `Codertocat`. | | `github.run_id` | `문자열` | {% data reusables.github-actions.run_id_description %} | `github.run_number` | `문자열` | {% data reusables.github-actions.run_number_description %} -| `github.sha` | `문자열` | The commit SHA that triggered the workflow run. | -| `github.token` | `문자열` | A token to authenticate on behalf of the GitHub App installed on your repository. This is functionally equivalent to the `GITHUB_TOKEN` secret. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)." | -| `github.workflow` | `문자열` | The name of the workflow. If the workflow file doesn't specify a `name`, the value of this property is the full path of the workflow file in the repository. | -| `github.workspace` | `문자열` | The default working directory for steps and the default location of your repository when using the [`checkout`](https://github.com/actions/checkout) action. | +| `github.run_attempt` | `문자열` | A unique number for each attempt of a particular workflow run in a repository. This number begins at 1 for the workflow run's first attempt, and increments with each re-run. | +| `github.server_url` | `문자열` | Returns the URL of the GitHub server. For example: `https://github.com`. | +| `github.sha` | `문자열` | The commit SHA that triggered the workflow run. | +| `github.token` | `문자열` | A token to authenticate on behalf of the GitHub App installed on your repository. This is functionally equivalent to the `GITHUB_TOKEN` secret. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)." | +| `github.workflow` | `문자열` | The name of the workflow. If the workflow file doesn't specify a `name`, the value of this property is the full path of the workflow file in the repository. | +| `github.workspace` | `문자열` | The default working directory for steps and the default location of your repository when using the [`checkout`](https://github.com/actions/checkout) action. | ### `env` context @@ -130,6 +131,7 @@ The `runner` context contains information about the runner that is executing the | Property name | 유형 | 설명 | | ------------------- | ----- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `runner.name` | `문자열` | {% data reusables.actions.runner-name-description %} | `runner.os` | `문자열` | {% data reusables.actions.runner-os-description %} | `runner.temp` | `문자열` | {% data reusables.actions.runner-temp-directory-description %} | `runner.tool_cache` | `문자열` | {% ifversion ghae %}For instructions on how to make sure your {% data variables.actions.hosted_runner %} has the required software installed, see "[Creating custom images](/actions/using-github-hosted-runners/creating-custom-images)." {% else %} {% data reusables.actions.runner-tool-cache-description %} {% endif %} diff --git a/translations/ko-KR/content/actions/learn-github-actions/creating-workflow-templates.md b/translations/ko-KR/content/actions/learn-github-actions/creating-workflow-templates.md new file mode 100644 index 0000000000..13f72b7b1d --- /dev/null +++ b/translations/ko-KR/content/actions/learn-github-actions/creating-workflow-templates.md @@ -0,0 +1,93 @@ +--- +title: Creating workflow templates +shortTitle: Creating templates +intro: Learn how you can create workflow templates to help people in your team add new workflows more easily. +redirect_from: + - /actions/configuring-and-managing-workflows/sharing-workflow-templates-within-your-organization +versions: + fpt: '*' + ghes: '*' + ghae: '*' +type: tutorial +topics: + - Workflows + - CI +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +## 개요 + +{% data reusables.actions.workflow-organization-templates %} + +## Creating a workflow template + +Workflow templates can be created by users with write access to the organization's `.github` repository. The templates can then be used by organization members who have permission to create workflows. You can share workflow templates if your organization's repository is public or if the repository is private and on an Enterprise plan. + +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +{% note %} + +**Note:** To avoid duplication in workflows created from a template you can call reusable workflows from within a workflow template. This can help make your workflows easier to maintain. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." + +{% endnote %} +{% endif %} + +This procedure demonstrates how to create a workflow template and metadata file. The metadata file describes how the template is presented to users when they are creating a new workflow. + +1. If it doesn't already exist, create a new public repository named `.github` in your organization. +2. Create a directory named `workflow-templates`. +3. Create your new workflow file inside the `workflow-templates` directory. + + If you need to refer to a repository's default branch, you can use the `$default-branch` placeholder. When a workflow is created using your template, the placeholder will be automatically replaced with the name of the repository's default branch. + + For example, this file named `octo-organization-ci.yml` demonstrates a basic workflow. + + ```yaml + name: Octo Organization CI + + on: + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] + + jobs: + build: + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v2 + + - name: Run a one-line script + run: echo Hello from Octo Organization + ``` +4. Create a metadata file inside the `workflow-templates` directory. The metadata file must have the same name as the workflow file, but instead of the `.yml` extension, it must be appended with `.properties.json`. For example, this file named `octo-organization-ci.properties.json` contains the metadata for a workflow file named `octo-organization-ci.yml`: + ```yaml + { + "name": "Octo Organization Workflow", + "description": "Octo Organization CI workflow template.", + "iconName": "example-icon", + "categories": [ + "Go" + ], + "filePatterns": [ + "package.json$", + "^Dockerfile", + ".*\\.md$" + ] + } + ``` + * `name` - **Required.** The name of the workflow template. This is displayed in the list of available templates. + * `description` - **Required.** The description of the workflow template. This is displayed in the list of available templates. + * `iconName` - **Required.** Defines an icon for the workflow's entry in the template list. The `iconName` must be an SVG icon of the same name, and must be stored in the `workflow-templates` directory. For example, a SVG file named `example-icon.svg` is referenced as `example-icon`. + * `categories` - **Optional.** Defines the language category of the workflow. When a user views the available templates, those templates that match the same language will feature more prominently. For information on the available language categories, see https://github.com/github/linguist/blob/master/lib/linguist/languages.yml. + * `filePatterns` - **Optional.** Allows the template to be used if the user's repository has a file in its root directory that matches a defined regular expression. + +To add another workflow template, add your files to the same `workflow-templates` directory. 예시: + +![Workflow template files](/assets/images/help/images/workflow-template-files.png) + +## 다음 단계 + +To continue learning about {% data variables.product.prodname_actions %}, see "[Using workflow templates](/actions/learn-github-actions/using-workflow-templates)." diff --git a/translations/ko-KR/content/actions/learn-github-actions/environment-variables.md b/translations/ko-KR/content/actions/learn-github-actions/environment-variables.md index 57c4fe372e..683075bb75 100644 --- a/translations/ko-KR/content/actions/learn-github-actions/environment-variables.md +++ b/translations/ko-KR/content/actions/learn-github-actions/environment-variables.md @@ -15,7 +15,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About environment variables @@ -73,6 +72,7 @@ We strongly recommend that actions use environment variables to access the files | `GITHUB_SERVER_URL` | Returns the URL of the {% data variables.product.product_name %} server. For example: `https://{% data variables.product.product_url %}`. | | `GITHUB_API_URL` | Returns the API URL. For example: `{% data variables.product.api_url_code %}`. | | `GITHUB_GRAPHQL_URL` | Returns the GraphQL API URL. For example: `{% data variables.product.graphql_url_code %}`. | +| `RUNNER_NAME` | {% data reusables.actions.runner-name-description %} | `RUNNER_OS` | {% data reusables.actions.runner-os-description %} | `RUNNER_TEMP` | {% data reusables.actions.runner-temp-directory-description %} {% ifversion not ghae %}| `RUNNER_TOOL_CACHE` | {% data reusables.actions.runner-tool-cache-description %}{% endif %} diff --git a/translations/ko-KR/content/actions/learn-github-actions/essential-features-of-github-actions.md b/translations/ko-KR/content/actions/learn-github-actions/essential-features-of-github-actions.md index 98ef451ced..f710aca28d 100644 --- a/translations/ko-KR/content/actions/learn-github-actions/essential-features-of-github-actions.md +++ b/translations/ko-KR/content/actions/learn-github-actions/essential-features-of-github-actions.md @@ -13,7 +13,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 개요 @@ -62,7 +61,7 @@ For more information, see "[Workflow syntax for {% data variables.product.prodna ## Sharing data between jobs -If your job generates files that you want to share with another job in the same workflow, or if you want to save the files for later reference, you can store them in {% data variables.product.prodname_dotcom %} as _artifacts_. Artifacts are the files created when you build and test your code. For example, artifacts might include binary or package files, test results, screenshots, or log files. Artifacts are associated with the workflow run where they were created and can be used by another job. +If your job generates files that you want to share with another job in the same workflow, or if you want to save the files for later reference, you can store them in {% data variables.product.prodname_dotcom %} as _artifacts_. Artifacts are the files created when you build and test your code. For example, artifacts might include binary or package files, test results, screenshots, or log files. Artifacts are associated with the workflow run where they were created and can be used by another job. {% data reusables.actions.reusable-workflow-artifacts %} For example, you can create a file and then upload it as an artifact. diff --git a/translations/ko-KR/content/actions/learn-github-actions/events-that-trigger-workflows.md b/translations/ko-KR/content/actions/learn-github-actions/events-that-trigger-workflows.md index 6edc70bbc8..2231553741 100644 --- a/translations/ko-KR/content/actions/learn-github-actions/events-that-trigger-workflows.md +++ b/translations/ko-KR/content/actions/learn-github-actions/events-that-trigger-workflows.md @@ -17,7 +17,6 @@ shortTitle: Events that trigger workflows {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Configuring workflow events @@ -165,6 +164,26 @@ on: types: [opened, deleted] ``` +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## Workflow reuse events + +`workflow_call` is a keyword used as the value of `on` in a workflow, in the same way as an event. It indicates that a workflow can be called from another workflow. For more information see, "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." + +### `workflow_call` + +| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | +| --------------------------- | -------------- | --------------------------- | --------------------------- | +| Same as the caller workflow | n/a | Same as the caller workflow | Same as the caller workflow | + +#### 예시 + +To make a workflow reusable it must include `workflow_call` as one of the values of `on`. The example below only runs the workflow when it's called from another workflow: + +```yaml +on: workflow_call +``` +{% endif %} + ## Webhook events You can configure your workflow to run when webhook events are generated on {% data variables.product.product_name %}. Some events have more than one activity type that triggers the event. If more than one activity type triggers the event, you can specify which activity types will trigger the workflow to run. For more information, see "[Webhooks](/webhooks)." diff --git a/translations/ko-KR/content/actions/learn-github-actions/expressions.md b/translations/ko-KR/content/actions/learn-github-actions/expressions.md index 6a48f08ecb..25e83e5c0d 100644 --- a/translations/ko-KR/content/actions/learn-github-actions/expressions.md +++ b/translations/ko-KR/content/actions/learn-github-actions/expressions.md @@ -12,7 +12,6 @@ miniTocMaxHeadingLevel: 3 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About expressions diff --git a/translations/ko-KR/content/actions/learn-github-actions/finding-and-customizing-actions.md b/translations/ko-KR/content/actions/learn-github-actions/finding-and-customizing-actions.md index db56d50f2e..585f9d1468 100644 --- a/translations/ko-KR/content/actions/learn-github-actions/finding-and-customizing-actions.md +++ b/translations/ko-KR/content/actions/learn-github-actions/finding-and-customizing-actions.md @@ -18,7 +18,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 개요 diff --git a/translations/ko-KR/content/actions/learn-github-actions/index.md b/translations/ko-KR/content/actions/learn-github-actions/index.md index 0c382694b3..2a211fefef 100644 --- a/translations/ko-KR/content/actions/learn-github-actions/index.md +++ b/translations/ko-KR/content/actions/learn-github-actions/index.md @@ -32,8 +32,10 @@ children: - /finding-and-customizing-actions - /essential-features-of-github-actions - /managing-complex-workflows - - /sharing-workflows-with-your-organization + - /sharing-workflows-secrets-and-runners-with-your-organization + - /creating-workflow-templates - /using-workflow-templates + - /reusing-workflows - /events-that-trigger-workflows - /expressions - /contexts diff --git a/translations/ko-KR/content/actions/learn-github-actions/managing-complex-workflows.md b/translations/ko-KR/content/actions/learn-github-actions/managing-complex-workflows.md index e54b057303..563b72e87a 100644 --- a/translations/ko-KR/content/actions/learn-github-actions/managing-complex-workflows.md +++ b/translations/ko-KR/content/actions/learn-github-actions/managing-complex-workflows.md @@ -13,7 +13,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 개요 @@ -170,10 +169,13 @@ To learn more about self-hosted runner labels, see ["Using labels with self-host {% data variables.product.prodname_dotcom %}-hosted runner labels, see ["Supported runners and hardware resources"](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources). {% endif %} -{% ifversion fpt or ghes > 3.0 %} +{% data reusables.actions.reusable-workflows %} + +{% ifversion fpt or ghes > 3.0 or ghae-next %} + ## Using environments -You can configure environments with protection rules and secrets. Each job in a workflow can reference a single environment. Any protection rules configured for the environment must pass before a job referencing the environment is sent to a runner. For more information, see "[Environments](/actions/reference/environments)." +You can configure environments with protection rules and secrets. Each job in a workflow can reference a single environment. Any protection rules configured for the environment must pass before a job referencing the environment is sent to a runner. For more information, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." {% endif %} ## Using a workflow template @@ -187,4 +189,4 @@ You can configure environments with protection rules and secrets. Each job in a ## 다음 단계 -To continue learning about {% data variables.product.prodname_actions %}, see "[Sharing workflows with your organization](/actions/learn-github-actions/sharing-workflows-with-your-organization)." +To continue learning about {% data variables.product.prodname_actions %}, see "[Sharing workflows, secrets, and runners with your organization](/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization)." diff --git a/translations/ko-KR/content/actions/learn-github-actions/reusing-workflows.md b/translations/ko-KR/content/actions/learn-github-actions/reusing-workflows.md new file mode 100644 index 0000000000..4f2f001597 --- /dev/null +++ b/translations/ko-KR/content/actions/learn-github-actions/reusing-workflows.md @@ -0,0 +1,195 @@ +--- +title: Reusing workflows +shortTitle: Reusing workflows +intro: Learn how to avoid duplication when creating a workflow by reusing existing workflows. +miniTocMaxHeadingLevel: 3 +versions: + fpt: '*' + ghes: '>=3.4' + ghae: issue-4757 +type: how_to +topics: + - Workflows +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +{% note %} + +**Note:** Reusable workflows are currently in beta and subject to change. + +{% endnote %} + +## 개요 + +Rather than copying and pasting from one workflow to another, you can make workflows reusable. You and anyone with access to the reusable workflow can then call the reusable workflow from another workflow. + +Reusing workflows avoids duplication. This makes workflows easier to maintain and allows you to create new workflows more quickly by building on the work of others, just as you do with actions. Workflow reuse also promotes best practice by helping you to use workflows that are well designed, have already been tested, and have been proved to be effective. Your organization can build up a library of reusable workflows that can be centrally maintained. + +A workflow that uses another workflow is referred to as a "caller" workflow. The reusable workflow is a "called" workflow. One caller workflow can use multiple called workflows. Each called workflow is referenced in a single line. The result is that the caller workflow file may contain just a few lines of YAML, but may perform a large number of tasks when it's run. When you reuse a workflow, the entire called workflow is used, just as if it was part of the caller workflow. + +If you reuse a workflow from a different repository, any actions in the called workflow run as if they were part of the caller workflow. For example, if the called workflow uses `actions/checkout`, the action checks out the contents of the repository that hosts the caller workflow, not the called workflow. + +When a reusable workflow is triggered by a caller workflow, the `github` context is always associated with the caller workflow. For more information about the `github` context, see "[Context and expression syntax for GitHub Actions](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)." + +## Access to reusable workflows + +A reusable workflow can be used by another workflow if any of the following is true: + +* Both workflows are in the same repository. +* The called workflow is stored in a public repository. +* The called workflow is stored in an internal repository and the settings for that repository allow it to be accessed. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#allowing-access-to-components-in-an-internal-repository)." + +## 제한 사항 + +* Reusable workflows can't call other reusable workflows. +* Reusable workflows stored within a private repository can only be used by workflows within the same repository. +* Any environment variables set in an `env` context defined at the workflow level in the caller workflow are not be propagated to the called workflow. For more information about the `env` context, see "[Context and expression syntax for GitHub Actions](/actions/reference/context-and-expression-syntax-for-github-actions#env-context)." + +The following limitations will be removed when workflow reuse moves out of beta: +* Reusable workflows can't reference self-hosted runners. +* You can't set the concurrency of a called workflow from the caller workflow. For more information about `jobs..concurrency`, see "[Workflow syntax for GitHub Actions](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idconcurrency)." +* Outputs generated by a called workflow can't be accessed by the caller workflow. + +## Creating a reusable workflow + +Reusable workflows are YAML-formatted files, very similar to any other workflow file. As with other workflow files, you locate reusable workflows in the `.github/workflows` directory of a repository. Subdirectories of the `workflows` directory are not supported. + +For a workflow to be reusable, the values for `on` must include `workflow_call`: + +```yaml +on: + workflow_call: +``` + +You can define inputs and secrets, which can be passed from the caller workflow and then used within the called workflow. The following example, from a reusable workflow, defines two inputs (called "ring" and "environment") and one secret (called "token"): + +```yaml +on: + workflow_call: + inputs: + ring: + description: 'Identifier for the target deployment ring' + default: 'ring-0' + required: false + type: string + environment: + required: false + type: string + secrets: + token: + required: false +``` + +For details of the syntax for defining inputs and secrets, see [on.workflow_call.inputs](/actions/reference/workflow-syntax-for-github-actions#onworkflow_callinputs) and [on.workflow_call.secrets](/actions/reference/workflow-syntax-for-github-actions#onworkflow_callsecrets). + +### Example reusable workflow + +This reusable workflow file named `workflow-B.yml` (we'll refer to this later) takes an input string and a secret from the caller workflow and uses them in an action. + +{% raw %} +```yaml{:copy} +name: Reusable workflow example + +on: + workflow_call: + inputs: + username: + required: true + type: string + secrets: + token: + required: true + +jobs: + example_job: + name: Pass input and secrets to my-action + runs-on: ubuntu-latest + steps: + - uses: ./.github/actions/my-action@v1 + with: + username: ${{ inputs.username }} + token: ${{ secrets.token }} +``` +{% endraw %} + +## Calling a reusable workflow + +You call a reusable workflow by using the `uses` keyword. Unlike when you are using actions within a workflow, you call reusable workflows directly within a job, and not from within job steps. + +[`jobs..uses`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_iduses) + +You reference reusable workflow files using the syntax: + +`{owner}/{repo}/{path}/{filename}@{ref}` + +You can call multiple workflows, referencing each in a separate job. + +{% data reusables.actions.uses-keyword-example %} + +### Passing inputs and secrets to a reusable workflow + +Use the `with` keyword in a job to pass named inputs to the called workflow. Use the `secrets` keyword to pass named secrets. The inputs and secrets you pass must be defined in the called workflow. For inputs, the data type of the input value must match the type specified for that input in the called workflow (boolean, number, or string). + +{% raw %} +```yaml +with: + username: mona +secrets: + token: ${{ secrets.TOKEN }} +``` +{% endraw %} + +### Supported keywords for jobs that call a reusable workflow + +When you call a reusable workflow, you can only use the following keywords in the job containing the call: + +* [`jobs..name`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idname) +* [`jobs..uses`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_iduses) +* [`jobs..with`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idwith) +* [`jobs..with.`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idwithinput_id) +* [`jobs..secrets`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idsecrets) +* [`jobs..secrets.`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idsecretssecret_id) +* [`jobs..needs`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds) +* [`jobs..if`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idif) +* [`jobs..permissions`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idpermissions) + + {% note %} + + **참고:** + + * If `jobs..permissions` is not specified in the calling job, the called workflow will have the default permissions for the `GITHUB_TOKEN`. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)." + * The `GITHUB_TOKEN` permissions passed from the caller workflow can be only downgraded (not elevated) by the called workflow. + + {% endnote %} + +### Example caller workflow + +This workflow file calls two workflow files. The second of these, `workflow-B.yml` (shown above), is passed an input, `username`, and a secret, `token`. + +{% raw %} +```yaml{:copy} +name: Call a reusable workflow + +on: + pull_request: + branches: + - main + +jobs: + call-workflow: + uses: octo-org/example-repo/.github/workflows/workflow-A.yml@v1 + + call-workflow-passing-data: + uses: octo-org/example-repo/.github/workflows/workflow-B.yml@main + with: + username: mona + secrets: + token: ${{ secrets.TOKEN }} +``` +{% endraw %} + +## 다음 단계 + +To continue learning about {% data variables.product.prodname_actions %}, see "[Events that trigger workflows](/actions/learn-github-actions/events-that-trigger-workflows)." diff --git a/translations/ko-KR/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md b/translations/ko-KR/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md new file mode 100644 index 0000000000..4c4b8d13e0 --- /dev/null +++ b/translations/ko-KR/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md @@ -0,0 +1,53 @@ +--- +title: 'Sharing workflows, secrets, and runners with your organization' +shortTitle: Sharing workflows with your organization +intro: 'Learn how you can use organization features to collaborate with your team, by sharing workflow templates, secrets, and self-hosted runners.' +redirect_from: + - /actions/learn-github-actions/sharing-workflows-with-your-organization +versions: + fpt: '*' + ghes: '*' + ghae: '*' +type: how_to +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +## 개요 + +If you need to share workflows and other {% data variables.product.prodname_actions %} features with your team, then consider collaborating within a {% data variables.product.prodname_dotcom %} organization. An organization allows you to centrally store and manage secrets, artifacts, and self-hosted runners. You can also create workflow templates in the `.github` repository and share them with other users in your organization. + +## Using workflow templates + +{% data reusables.actions.workflow-organization-templates %} For more information, see "[Creating workflow templates](/actions/learn-github-actions/creating-workflow-templates)." + +{% data reusables.actions.reusable-workflows %} + +## Sharing secrets within an organization + +You can centrally manage your secrets within an organization, and then make them available to selected repositories. This also means that you can update a secret in one location, and have the change apply to all repository workflows that use the secret. + +When creating a secret in an organization, you can use a policy to limit which repositories can access that secret. For example, you can grant access to all repositories, or limit access to only private repositories or a specified list of repositories. + +{% data reusables.github-actions.permissions-statement-secrets-organization %} + +{% data reusables.organizations.navigate-to-org %} +{% data reusables.organizations.org_settings %} +{% data reusables.github-actions.sidebar-secret %} +1. Click **New secret**. +1. Type a name for your secret in the **Name** input box. +1. Enter the **Value** for your secret. +1. From the **Repository access** dropdown list, choose an access policy. +1. Click **Add secret**. + +## Share self-hosted runners within an organization + +Organization admins can add their self-hosted runners to groups, and then create policies that control which repositories can access the group. + +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)." + + +## 다음 단계 + +To continue learning about {% data variables.product.prodname_actions %}, see "[Creating workflow templates](/actions/learn-github-actions/creating-workflow-templates)." diff --git a/translations/ko-KR/content/actions/learn-github-actions/understanding-github-actions.md b/translations/ko-KR/content/actions/learn-github-actions/understanding-github-actions.md index 3b836b5ade..ed3d6026a5 100644 --- a/translations/ko-KR/content/actions/learn-github-actions/understanding-github-actions.md +++ b/translations/ko-KR/content/actions/learn-github-actions/understanding-github-actions.md @@ -18,7 +18,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 개요 @@ -36,7 +35,7 @@ Below is a list of the multiple {% data variables.product.prodname_actions %} co ### Workflows -The workflow is an automated procedure that you add to your repository. Workflows are made up of one or more jobs and can be scheduled or triggered by an event. The workflow can be used to build, test, package, release, or deploy a project on {% data variables.product.prodname_dotcom %}. +The workflow is an automated procedure that you add to your repository. Workflows are made up of one or more jobs and can be scheduled or triggered by an event. The workflow can be used to build, test, package, release, or deploy a project on {% data variables.product.prodname_dotcom %}. {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %}You can reference a workflow within another workflow, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."{% endif %} ### 이벤트 diff --git a/translations/ko-KR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md b/translations/ko-KR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md index 8a03d7a851..54e88596f9 100644 --- a/translations/ko-KR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md +++ b/translations/ko-KR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md @@ -16,7 +16,6 @@ shortTitle: Workflow billing & limits {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About billing for {% data variables.product.prodname_actions %} @@ -61,6 +60,12 @@ Usage limits apply to self-hosted runners. For more information, see "[About sel In addition to the usage limits, you must ensure that you use {% data variables.product.prodname_actions %} within the [GitHub Terms of Service](/articles/github-terms-of-service/). For more information on {% data variables.product.prodname_actions %}-specific terms, see the [GitHub Additional Product Terms](/github/site-policy/github-additional-product-terms#a-actions-usage). {% endif %} +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## Billing for reusable workflows + +If you reuse a workflow, billing is always associated with the caller workflow. For more information see, "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." +{% endif %} + {% ifversion fpt or ghes > 2.22 or ghae %} ## Artifact and log retention policy diff --git a/translations/ko-KR/content/actions/learn-github-actions/using-workflow-templates.md b/translations/ko-KR/content/actions/learn-github-actions/using-workflow-templates.md index b9aaa079ee..e14c564414 100644 --- a/translations/ko-KR/content/actions/learn-github-actions/using-workflow-templates.md +++ b/translations/ko-KR/content/actions/learn-github-actions/using-workflow-templates.md @@ -1,7 +1,7 @@ --- title: Using workflow templates shortTitle: Using templates -intro: You can set up CI using a workflow template that matches the language and tooling you want to use. +intro: '{% data variables.product.product_name %} provides workflow templates for a variety of languages and tooling.' product: '{% data reusables.gated-features.actions %}' redirect_from: - /articles/setting-up-continuous-integration-using-github-actions @@ -17,34 +17,37 @@ type: tutorial topics: - Workflows - CI + - CD --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -Anyone with write permission to a repository can set up continuous integration (CI) using {% data variables.product.prodname_actions %}. +## About workflow templates -After you set up CI, you can customize the workflow to meet your needs. +{% data variables.product.product_name %} offers workflow templates for a variety of languages and tooling. When you set up workflows in your repository, {% data variables.product.product_name %} analyzes the code in your repository and recommends workflows based on the language and framework in your repository. For example, if you use [Node.js](https://nodejs.org/en/), {% data variables.product.product_name %} will suggest a template file that installs your Node.js packages and runs your tests. + +You can also create your own workflow templates to share with your organization. For more information, see "[Creating workflow templates](/actions/learn-github-actions/creating-workflow-templates)." + +## Using workflow templates + +Anyone with write permission to a repository can set up {% data variables.product.prodname_actions %} workflows for CI/CD or other automation. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} -1. Find the template that matches the language and tooling you want to use, then click **Set up this workflow**. ![Setup workflow button](/assets/images/help/repository/setup-workflow-button.png) -5. Click **Start commit**. ![Start commit button](/assets/images/help/repository/start-commit.png) -{% data reusables.files.write_commit_message %} -{% data reusables.files.choose_commit_branch %} -{% data reusables.files.propose_new_file %} - -Once a push is made to your repository, you can follow the status and detailed logs of your continuous integration workflow run on {% data variables.product.prodname_dotcom %} and receive customized notifications. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)" and "[Managing a workflow run](/articles/managing-a-workflow-run)." - -{% 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)." +1. If you already have a workflow in your repository, click **New workflow**. +1. Find the template that you want to use, then click **Set up this workflow**. +1. If the workflow template contains comments detailing additional setup steps, follow these steps. +1. Some workflow templates use secrets. For example, {% raw %}`${{ secrets.npm_token }}`{% endraw %}. If the workflow template uses a secret, store the value described in the secret name as a secret in your repository. For more information, see "[Encrypted secrets](/actions/reference/encrypted-secrets)." +1. Optionally, make additional changes. For example, you might want to change the value of `on` to change when the workflow runs. +1. Click **Start commit**. +1. Write a commit message and decide whether to commit directly to the default branch or to open a pull request. ## 더 읽을거리 - "[About continuous integration](/articles/about-continuous-integration)" -- "[Managing a workflow run](/articles/managing-a-workflow-run)" +- "[Managing workflow runs](/actions/managing-workflow-runs)" +- "[About monitoring and troubleshooting](/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting)" - "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" {% ifversion fpt %} - "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)" diff --git a/translations/ko-KR/content/actions/learn-github-actions/workflow-commands-for-github-actions.md b/translations/ko-KR/content/actions/learn-github-actions/workflow-commands-for-github-actions.md index 15ec4eb65a..1b93544dc8 100644 --- a/translations/ko-KR/content/actions/learn-github-actions/workflow-commands-for-github-actions.md +++ b/translations/ko-KR/content/actions/learn-github-actions/workflow-commands-for-github-actions.md @@ -18,7 +18,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About workflow commands @@ -89,7 +88,7 @@ The following table shows which toolkit functions are available within a workflo | `core.setOutput` | `set-output` | | `core.setSecret` | `add-mask` | | `core.startGroup` | `그룹` | -| `core.warning` | `warning file` | +| `core.warning` | `경고` | {% ifversion ghes < 3.0 %} ## Setting an environment variable @@ -331,6 +330,12 @@ echo "{name}={value}" >> $GITHUB_ENV Creates or updates an environment variable for any steps running next in a job. The step that creates or updates the environment variable does not have access to the new value, but all subsequent steps in a job will have access. Environment variables are case-sensitive and you can include punctuation. +{% note %} + +**Note:** Environment variables must be explicitly referenced using the [`env` context](/actions/reference/context-and-expression-syntax-for-github-actions#env-context) in expression syntax or through use of the `$GITHUB_ENV` file directly; environment variables are not implicitly available in shell commands. + +{% endnote %} + ### 예시 {% raw %} @@ -376,7 +381,7 @@ steps: echo "{path}" >> $GITHUB_PATH ``` -Prepends a directory to the system `PATH` variable and makes it available to all subsequent actions in the current job; the currently running action cannot access the updated path variable. To see the currently defined paths for your job, you can use `echo "$PATH"` in a step or an action. +Prepends a directory to the system `PATH` variable and automatically makes it available to all subsequent actions in the current job; the currently running action cannot access the updated path variable. To see the currently defined paths for your job, you can use `echo "$PATH"` in a step or an action. ### 예시 diff --git a/translations/ko-KR/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md b/translations/ko-KR/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md index 10ea7a44b7..20289a153a 100644 --- a/translations/ko-KR/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md +++ b/translations/ko-KR/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md @@ -16,7 +16,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About YAML syntax for workflows @@ -184,9 +183,91 @@ Diffs are limited to 300 files. If there are files changed that aren't matched i For more information, see "[About comparing branches in pull requests](/articles/about-comparing-branches-in-pull-requests)." +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## `on.workflow_call.inputs` + +When using the `workflow_call` keyword, you can optionally specify inputs that are passed to the called workflow from the caller workflow. Inputs for reusable workflows are specified with the same format as action inputs. For more information about inputs, see "[Metadata syntax for GitHub Actions](/actions/creating-actions/metadata-syntax-for-github-actions#inputs)." For more information about the `workflow_call` keyword, see "[Events that trigger workflows](/actions/learn-github-actions/events-that-trigger-workflows#workflow-reuse-events)." + +In addition to the standard input parameters that are available, `on.workflow_call.inputs` requires a `type` parameter. For more information, see [`on.workflow_call..type`](#onworkflow_callinput_idtype). + +If a `default` parameter is not set, the default value of the input is `false` for a boolean, `0` for a number, and `""` for a string. + +Within the called workflow, you can use the `inputs` context to refer to an input. + +If a caller workflow passes an input that is not specified in the called workflow, this results in an error. + +### 예시 + +{% raw %} +```yaml +on: + workflow_call: + inputs: + username: + description: 'A username passed from the caller workflow' + default: 'john-doe' + required: false + type: string + +jobs: + print-username: + runs-on: ubuntu-latest + + steps: + - name: Print the input name to STDOUT + run: echo The username is ${{ inputs.username }} +``` +{% endraw %} + +For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." + +## `on.workflow_call..type` + +Required if input is defined for the `on.workflow_call` keyword. The value of this parameter is a string specifying the data type of the input. This must be one of: `boolean`, `number`, or `string`. + +## `on.workflow_call.secrets` + +A map of the secrets that can be used in the called workflow. + +Within the called workflow, you can use the `secrets` context to refer to a secret. + +If a caller workflow passes a secret that is not specified in the called workflow, this results in an error. + +### 예시 + +{% raw %} +```yaml +on: + workflow_call: + secrets: + access-token: + description: 'A token passed from the caller workflow' + required: false + +jobs: + pass-secret-to-action: + runs-on: ubuntu-latest + + steps: + - name: Pass the received secret to an action + uses: ./.github/actions/my-action@v1 + with: + token: ${{ secrets.access-token }} +``` +{% endraw %} + +## `on.workflow_call.secrets.` + +A string identifier to associate with the secret. + +## `on.workflow_call.secrets..required` + +A boolean specifying whether the secret must be supplied. +{% endif %} + ## `on.workflow_dispatch.inputs` -When using `workflow_dispatch` event, you can optionally specify inputs that are passed to the workflow. Workflow dispatch inputs are specified with the same format as action inputs. For more information about the format see "[Metadata syntax for GitHub Actions](/actions/creating-actions/metadata-syntax-for-github-actions#inputs)." +When using the `workflow_dispatch` event, you can optionally specify inputs that are passed to the workflow. Workflow dispatch inputs are specified with the same format as action inputs. For more information about the format see "[Metadata syntax for GitHub Actions](/actions/creating-actions/metadata-syntax-for-github-actions#inputs)." ```yaml on: @@ -272,8 +353,6 @@ defaults: {% ifversion fpt or ghae-next or ghes > 3.1 %} ## `concurrency` -{% data reusables.actions.concurrency-beta %} - Concurrency ensures that only a single job or workflow using the same concurrency group will run at a time. A concurrency group can be any string or expression. The expression can only use the [`github` context](/actions/learn-github-actions/contexts#github-context). For more information about expressions, see "[Expressions](/actions/learn-github-actions/expressions)." You can also specify `concurrency` at the job level. For more information, see [`jobs..concurrency`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idconcurrency). @@ -428,7 +507,7 @@ jobs: {% ifversion fpt or ghes > 3.0 or ghae %} ## `jobs..environment` -The environment that the job references. All environment protection rules must pass before a job referencing the environment is sent to a runner. For more information, see "[Environments](/actions/reference/environments)." +The environment that the job references. All environment protection rules must pass before a job referencing the environment is sent to a runner. For more information, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." You can provide the environment as only the environment `name`, or as an environment object with the `name` and `url`. The URL maps to `environment_url` in the deployments API. For more information about the deployments API, see "[Deployments](/rest/reference/repos#deployments)." @@ -463,8 +542,6 @@ environment: {% ifversion fpt or ghae-next or ghes > 3.1 %} ## `jobs..concurrency` -{% data reusables.actions.concurrency-beta %} - {% note %} **Note:** When concurrency is specified at the job level, order is not guaranteed for jobs or runs that queue within 5 minutes of each other. @@ -1348,6 +1425,70 @@ Additional Docker container resource options. For a list of options, see "[`dock {% endwarning %} +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## `jobs..uses` + +The location and version of a reusable workflow file to run as a job. + +`{owner}/{repo}/{path}/{filename}@{ref}` + +`{ref}` can be a SHA, a release tag, or a branch name. Using the commit SHA is the safest for stability and security. For more information, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#reusing-third-party-workflows)." + +### 예시 + +{% data reusables.actions.uses-keyword-example %} + +For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." + +## `jobs..with` + +When a job is used to call a reusable workflow, you can use `with` to provide a map of inputs that are passed to the called workflow. + +Any inputs that you pass must match the input specifications defined in the called workflow. + +Unlike [`jobs..steps[*].with`](#jobsjob_idstepswith), the inputs you pass with `jobs..with` are not be available as environment variables in the called workflow. Instead, you can reference the inputs by using the `inputs` context. + +### 예시 + +```yaml +jobs: + call-workflow: + uses: octo-org/example-repo/.github/workflows/called-workflow.yml@main + with: + username: mona +``` + +## `jobs..with.` + +A pair consisting of a string identifier for the input and the value of the input. The identifier must match the name of an input defined by [`on.workflow_call.inputs.`](/actions/creating-actions/metadata-syntax-for-github-actions#inputsinput_id) in the called workflow. The data type of the value must match the type defined by [`on.workflow_call..type`](#onworkflow_callinput_idtype) in the called workflow. + +Allowed expression contexts: `github`, and `needs`. + +## `jobs..secrets` + +When a job is used to call a reusable workflow, you can use `secrets` to provide a map of secrets that are passed to the called workflow. + +Any secrets that you pass must match the names defined in the called workflow. + +### 예시 + +{% raw %} +```yaml +jobs: + call-workflow: + uses: octo-org/example-repo/.github/workflows/called-workflow.yml@main + secrets: + access-token: ${{ secrets.PERSONAL_ACCESS_TOKEN }} +``` +{% endraw %} + +## `jobs..secrets.` + +A pair consisting of a string identifier for the secret and the value of the secret. The identifier must match the name of a secret defined by [`on.workflow_call.secrets.`](#onworkflow_callsecretssecret_id) in the called workflow. + +Allowed expression contexts: `github`, `needs`, and `secrets`. +{% endif %} + ## Filter pattern cheat sheet You can use special characters in path, branch, and tag filters. diff --git a/translations/ko-KR/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md b/translations/ko-KR/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md index c6c1d10d0b..ff4e97f402 100644 --- a/translations/ko-KR/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md +++ b/translations/ko-KR/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md @@ -16,8 +16,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## Introduction diff --git a/translations/ko-KR/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md b/translations/ko-KR/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md index c39028db35..dd00d01a14 100644 --- a/translations/ko-KR/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md +++ b/translations/ko-KR/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md @@ -16,8 +16,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## Introduction diff --git a/translations/ko-KR/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md b/translations/ko-KR/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md index fc4b6c26dc..a47654c9ae 100644 --- a/translations/ko-KR/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md +++ b/translations/ko-KR/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md @@ -17,8 +17,6 @@ shortTitle: Add label to comment on issue {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## Introduction diff --git a/translations/ko-KR/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md b/translations/ko-KR/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md index 615255c452..d8ae9f5716 100644 --- a/translations/ko-KR/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md +++ b/translations/ko-KR/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md @@ -17,8 +17,6 @@ shortTitle: Move assigned issues {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## Introduction diff --git a/translations/ko-KR/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md b/translations/ko-KR/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md index e44322a3ff..298ab3f296 100644 --- a/translations/ko-KR/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md +++ b/translations/ko-KR/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md @@ -17,8 +17,6 @@ shortTitle: Remove label when adding card {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## Introduction diff --git a/translations/ko-KR/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md b/translations/ko-KR/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md index 236ba27b9c..f6c0ace9a7 100644 --- a/translations/ko-KR/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md +++ b/translations/ko-KR/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md @@ -16,8 +16,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## Introduction diff --git a/translations/ko-KR/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md b/translations/ko-KR/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md index fcb7ebb0dc..4a03ed477d 100644 --- a/translations/ko-KR/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md +++ b/translations/ko-KR/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md @@ -9,7 +9,9 @@ shortTitle: Approve public fork runs ## About workflow runs from public forks -{% data reusables.actions.workflow-run-approve-public-fork %} However, you can configure this behavior for a [repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks), [organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#configuring-required-approval-for-workflows-from-public-forks), or [enterprise](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account#configuring-required-approval-for-workflows-from-public-forks). +{% data reusables.actions.workflow-run-approve-public-fork %} + +You can configure workflow approval requirements for a [repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks), [organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#configuring-required-approval-for-workflows-from-public-forks), or [enterprise](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account#configuring-required-approval-for-workflows-from-public-forks). Workflow runs that have been awaiting approval for more than 30 days are automatically deleted. diff --git a/translations/ko-KR/content/actions/managing-workflow-runs/canceling-a-workflow.md b/translations/ko-KR/content/actions/managing-workflow-runs/canceling-a-workflow.md index e8cc76712f..a2ec8ffea1 100644 --- a/translations/ko-KR/content/actions/managing-workflow-runs/canceling-a-workflow.md +++ b/translations/ko-KR/content/actions/managing-workflow-runs/canceling-a-workflow.md @@ -10,7 +10,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.repositories.permissions-statement-write %} diff --git a/translations/ko-KR/content/actions/managing-workflow-runs/deleting-a-workflow-run.md b/translations/ko-KR/content/actions/managing-workflow-runs/deleting-a-workflow-run.md index 1bcb1d4e20..042897fe01 100644 --- a/translations/ko-KR/content/actions/managing-workflow-runs/deleting-a-workflow-run.md +++ b/translations/ko-KR/content/actions/managing-workflow-runs/deleting-a-workflow-run.md @@ -10,7 +10,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.repositories.permissions-statement-write %} diff --git a/translations/ko-KR/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md b/translations/ko-KR/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md index da8394877b..3f500570a8 100644 --- a/translations/ko-KR/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md +++ b/translations/ko-KR/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md @@ -11,7 +11,6 @@ shortTitle: Disable & enable a workflow {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} Disabling a workflow allows you to stop a workflow from being triggered without having to delete the file from the repo. You can easily re-enable the workflow again on {% data variables.product.prodname_dotcom %}. diff --git a/translations/ko-KR/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md b/translations/ko-KR/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md index fb3accb468..2e783da2ea 100644 --- a/translations/ko-KR/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md +++ b/translations/ko-KR/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md @@ -11,7 +11,6 @@ shortTitle: Download workflow artifacts {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% ifversion fpt or ghes > 2.22 or ghae %} By default, {% data variables.product.product_name %} stores build logs and artifacts for 90 days, and you can customize this retention period, depending on the type of repository. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)."{% endif %} {% ifversion ghes = 2.22 %} {% data variables.product.product_name %} stores full build logs and artifacts for 90 days.{% endif %} diff --git a/translations/ko-KR/content/actions/managing-workflow-runs/index.md b/translations/ko-KR/content/actions/managing-workflow-runs/index.md index 140eccb9dd..24c7206c85 100644 --- a/translations/ko-KR/content/actions/managing-workflow-runs/index.md +++ b/translations/ko-KR/content/actions/managing-workflow-runs/index.md @@ -19,6 +19,7 @@ children: - /approving-workflow-runs-from-public-forks - /reviewing-deployments - /disabling-and-enabling-a-workflow + - /skipping-workflow-runs - /deleting-a-workflow-run - /downloading-workflow-artifacts - /removing-workflow-artifacts @@ -26,5 +27,3 @@ children: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% ifversion fpt or ghes > 3.0 or ghae %}{% endif %} diff --git a/translations/ko-KR/content/actions/managing-workflow-runs/manually-running-a-workflow.md b/translations/ko-KR/content/actions/managing-workflow-runs/manually-running-a-workflow.md index c85e0946cf..db4c6e8234 100644 --- a/translations/ko-KR/content/actions/managing-workflow-runs/manually-running-a-workflow.md +++ b/translations/ko-KR/content/actions/managing-workflow-runs/manually-running-a-workflow.md @@ -11,7 +11,6 @@ shortTitle: Manually run a workflow {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Configuring a workflow to run manually diff --git a/translations/ko-KR/content/actions/managing-workflow-runs/re-running-a-workflow.md b/translations/ko-KR/content/actions/managing-workflow-runs/re-running-a-workflow.md index c0d2b16991..395186ab96 100644 --- a/translations/ko-KR/content/actions/managing-workflow-runs/re-running-a-workflow.md +++ b/translations/ko-KR/content/actions/managing-workflow-runs/re-running-a-workflow.md @@ -11,7 +11,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} Re-running a workflow uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (Git ref) of the original event that triggered the workflow run. You can re-run a workflow up to 30 days after the initial run. diff --git a/translations/ko-KR/content/actions/managing-workflow-runs/removing-workflow-artifacts.md b/translations/ko-KR/content/actions/managing-workflow-runs/removing-workflow-artifacts.md index 038f068d20..3b992c5d29 100644 --- a/translations/ko-KR/content/actions/managing-workflow-runs/removing-workflow-artifacts.md +++ b/translations/ko-KR/content/actions/managing-workflow-runs/removing-workflow-artifacts.md @@ -11,7 +11,6 @@ shortTitle: Remove workflow artifacts {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Deleting an artifact diff --git a/translations/ko-KR/content/actions/managing-workflow-runs/reviewing-deployments.md b/translations/ko-KR/content/actions/managing-workflow-runs/reviewing-deployments.md index 5649b60107..a4fdb44853 100644 --- a/translations/ko-KR/content/actions/managing-workflow-runs/reviewing-deployments.md +++ b/translations/ko-KR/content/actions/managing-workflow-runs/reviewing-deployments.md @@ -8,13 +8,12 @@ versions: ghae: '*' --- -{% data reusables.actions.ae-beta %} ## About required reviews in workflows Jobs that reference an environment configured with required reviewers will wait for an approval before starting. While a job is awaiting approval, it has a status of "Waiting". If a job is not approved within 30 days, the workflow run will be automatically canceled. -For more information about environments and required approvals, see "[Environments](/actions/reference/environments)."{% ifversion fpt or ghae-next or ghes > 3.1 %} For information about how to review deployments with the REST API, see "[Workflow Runs](/rest/reference/actions#workflow-runs)."{% endif %} +For more information about environments and required approvals, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)."{% ifversion fpt or ghae-next or ghes > 3.1 %} For information about how to review deployments with the REST API, see "[Workflow Runs](/rest/reference/actions#workflow-runs)."{% endif %} ## Approving or rejecting a job diff --git a/translations/ko-KR/content/actions/managing-workflow-runs/skipping-workflow-runs.md b/translations/ko-KR/content/actions/managing-workflow-runs/skipping-workflow-runs.md new file mode 100644 index 0000000000..09cd92c4fe --- /dev/null +++ b/translations/ko-KR/content/actions/managing-workflow-runs/skipping-workflow-runs.md @@ -0,0 +1,33 @@ +--- +title: Skipping workflow runs +intro: 'You can skip workflow runs triggered by the `push` and `pull_request` events by including a command in your commit message.' +product: '{% data reusables.gated-features.actions %}' +versions: + fpt: '*' + ghes: '>=3.0' + ghae: 'ghae-next' +shortTitle: Skip workflow runs +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +Workflows that would otherwise be triggered using `on: push` or `on: pull_request` won't be triggered if you add any of the following strings to the commit message in a push, or the HEAD commit of a pull request: + +* `[skip ci]` +* `[ci skip]` +* `[no ci]` +* `[skip actions]` +* `[actions skip]` + +Alternatively, you can end the commit message with two empty lines followed by either `skip-checks: true` or `skip-checks:true`. + +You won't be able to merge the pull request if your repository is configured to require specific checks to pass first. To allow the pull request to be merged you can push a new commit to the pull request without the skip instruction in the commit message. + +{% note %} + +**Note:** Skip instructions only apply to the `push` and `pull_request` events. For example, adding `[skip ci]` to a commit message won't stop a workflow that's triggered `on: pull_request_target` from running. + +{% endnote %} + +Skip instructions only apply to the workflow run(s) that would be triggered by the commit that contains the skip instructions. You can also disable a workflow from running. For more information, see "[Disabling and enabling a workflow](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)." \ No newline at end of file diff --git a/translations/ko-KR/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md b/translations/ko-KR/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md index e7d75e2786..7b984b2d75 100644 --- a/translations/ko-KR/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md +++ b/translations/ko-KR/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md @@ -19,7 +19,6 @@ shortTitle: Migrate from Azure Pipelines {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ko-KR/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md b/translations/ko-KR/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md index 1996ddfea7..945c505f2c 100644 --- a/translations/ko-KR/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md +++ b/translations/ko-KR/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md @@ -19,7 +19,6 @@ shortTitle: Migrate from CircleCI {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ko-KR/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md b/translations/ko-KR/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md index de26c22604..f598b1f9a1 100644 --- a/translations/ko-KR/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md +++ b/translations/ko-KR/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md @@ -18,7 +18,6 @@ shortTitle: Migrate from GitLab CI/CD {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ko-KR/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md b/translations/ko-KR/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md index 0d5dd0b9ec..053155ff55 100644 --- a/translations/ko-KR/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md +++ b/translations/ko-KR/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md @@ -19,7 +19,6 @@ shortTitle: Migrate from Jenkins {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ko-KR/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/ko-KR/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md index 5e067387f3..04407b01c5 100644 --- a/translations/ko-KR/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md +++ b/translations/ko-KR/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md @@ -19,7 +19,6 @@ shortTitle: Migrate from Travis CI {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ko-KR/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md b/translations/ko-KR/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md index 93f3d6062f..11709eb703 100644 --- a/translations/ko-KR/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md +++ b/translations/ko-KR/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md @@ -12,7 +12,6 @@ miniTocMaxHeadingLevel: 3 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Monitoring your workflows diff --git a/translations/ko-KR/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md b/translations/ko-KR/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md index 5c909329a6..26fd37d18f 100644 --- a/translations/ko-KR/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md +++ b/translations/ko-KR/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md @@ -13,7 +13,6 @@ shortTitle: Add a status badge {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.repositories.actions-workflow-status-badge-intro %} diff --git a/translations/ko-KR/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md b/translations/ko-KR/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md index 2b61c09cc5..a0d12f5bbf 100644 --- a/translations/ko-KR/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md +++ b/translations/ko-KR/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md @@ -12,7 +12,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} These extra logs are enabled by setting secrets in the repository containing the workflow, so the same permissions requirements will apply: diff --git a/translations/ko-KR/content/actions/monitoring-and-troubleshooting-workflows/index.md b/translations/ko-KR/content/actions/monitoring-and-troubleshooting-workflows/index.md index bda6bc8ded..36ad81e817 100644 --- a/translations/ko-KR/content/actions/monitoring-and-troubleshooting-workflows/index.md +++ b/translations/ko-KR/content/actions/monitoring-and-troubleshooting-workflows/index.md @@ -17,9 +17,8 @@ children: - /viewing-job-execution-time - /using-workflow-run-logs - /enabling-debug-logging + - /notifications-for-workflow-runs --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% ifversion fpt or ghes > 3.0 or ghae %}{% endif %} diff --git a/translations/ko-KR/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md b/translations/ko-KR/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md new file mode 100644 index 0000000000..6f0d46aa3d --- /dev/null +++ b/translations/ko-KR/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md @@ -0,0 +1,15 @@ +--- +title: Notifications for workflow runs +intro: You can subscribe to notifications about workflow runs that you trigger. +product: '{% data reusables.gated-features.actions %}' +versions: + fpt: '*' + ghes: '*' + ghae: '*' +shortTitle: 알림(Notifications) +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +{% data reusables.repositories.workflow-notifications %} diff --git a/translations/ko-KR/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md b/translations/ko-KR/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md index 9e777686f6..4561fca6cb 100644 --- a/translations/ko-KR/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md +++ b/translations/ko-KR/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md @@ -13,7 +13,6 @@ shortTitle: Use the visualization graph {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} diff --git a/translations/ko-KR/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md b/translations/ko-KR/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md index 5fc1154c66..d6654699fa 100644 --- a/translations/ko-KR/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md +++ b/translations/ko-KR/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md @@ -12,7 +12,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} You can see whether a workflow run is in progress or complete from the workflow run page. You must be logged in to a {% data variables.product.prodname_dotcom %} account to view workflow run information, including for public repositories. For more information, see "[Access permissions on GitHub](/articles/access-permissions-on-github)." diff --git a/translations/ko-KR/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md b/translations/ko-KR/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md index 761e2e50b8..39f9281319 100644 --- a/translations/ko-KR/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md +++ b/translations/ko-KR/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md @@ -11,7 +11,6 @@ shortTitle: View job execution time {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} Billable job execution minutes are only shown for jobs run on private repositories that use {% data variables.product.prodname_dotcom %}-hosted runners. There are no billable minutes when using {% data variables.product.prodname_actions %} in public repositories or for jobs run on self-hosted runners. diff --git a/translations/ko-KR/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md b/translations/ko-KR/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md index de5599a326..e9121d381f 100644 --- a/translations/ko-KR/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md +++ b/translations/ko-KR/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md @@ -13,7 +13,6 @@ shortTitle: View workflow run history {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.repositories.permissions-statement-read %} diff --git a/translations/ko-KR/content/actions/publishing-packages/about-packaging-with-github-actions.md b/translations/ko-KR/content/actions/publishing-packages/about-packaging-with-github-actions.md index 174f77c43d..629003aaae 100644 --- a/translations/ko-KR/content/actions/publishing-packages/about-packaging-with-github-actions.md +++ b/translations/ko-KR/content/actions/publishing-packages/about-packaging-with-github-actions.md @@ -18,7 +18,6 @@ shortTitle: Packaging with GitHub Actions {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.package_registry.about-packaging-and-actions %} diff --git a/translations/ko-KR/content/actions/publishing-packages/publishing-docker-images.md b/translations/ko-KR/content/actions/publishing-packages/publishing-docker-images.md index 7e9174157c..d13df43026 100644 --- a/translations/ko-KR/content/actions/publishing-packages/publishing-docker-images.md +++ b/translations/ko-KR/content/actions/publishing-packages/publishing-docker-images.md @@ -18,7 +18,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ko-KR/content/actions/publishing-packages/publishing-java-packages-with-gradle.md b/translations/ko-KR/content/actions/publishing-packages/publishing-java-packages-with-gradle.md index adb5b30e53..6c353ce745 100644 --- a/translations/ko-KR/content/actions/publishing-packages/publishing-java-packages-with-gradle.md +++ b/translations/ko-KR/content/actions/publishing-packages/publishing-java-packages-with-gradle.md @@ -20,7 +20,6 @@ shortTitle: Java packages with Gradle {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ko-KR/content/actions/publishing-packages/publishing-java-packages-with-maven.md b/translations/ko-KR/content/actions/publishing-packages/publishing-java-packages-with-maven.md index 53fad78e6c..87834cc0af 100644 --- a/translations/ko-KR/content/actions/publishing-packages/publishing-java-packages-with-maven.md +++ b/translations/ko-KR/content/actions/publishing-packages/publishing-java-packages-with-maven.md @@ -20,7 +20,6 @@ shortTitle: Java packages with Maven {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ko-KR/content/actions/publishing-packages/publishing-nodejs-packages.md b/translations/ko-KR/content/actions/publishing-packages/publishing-nodejs-packages.md index 2745de2563..2604bb2379 100644 --- a/translations/ko-KR/content/actions/publishing-packages/publishing-nodejs-packages.md +++ b/translations/ko-KR/content/actions/publishing-packages/publishing-nodejs-packages.md @@ -21,7 +21,6 @@ shortTitle: Node.js packages {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ko-KR/content/actions/quickstart.md b/translations/ko-KR/content/actions/quickstart.md index de7956c42e..073291d1bb 100644 --- a/translations/ko-KR/content/actions/quickstart.md +++ b/translations/ko-KR/content/actions/quickstart.md @@ -16,7 +16,6 @@ shortTitle: Quickstart {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ko-KR/content/actions/security-guides/automatic-token-authentication.md b/translations/ko-KR/content/actions/security-guides/automatic-token-authentication.md index 0f4ad9d47f..00c29ef8d0 100644 --- a/translations/ko-KR/content/actions/security-guides/automatic-token-authentication.md +++ b/translations/ko-KR/content/actions/security-guides/automatic-token-authentication.md @@ -16,7 +16,6 @@ shortTitle: Automatic token authentication {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About the `GITHUB_TOKEN` secret diff --git a/translations/ko-KR/content/actions/security-guides/encrypted-secrets.md b/translations/ko-KR/content/actions/security-guides/encrypted-secrets.md index de6ba33fee..c6d45f73ec 100644 --- a/translations/ko-KR/content/actions/security-guides/encrypted-secrets.md +++ b/translations/ko-KR/content/actions/security-guides/encrypted-secrets.md @@ -16,7 +16,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About encrypted secrets diff --git a/translations/ko-KR/content/actions/security-guides/security-hardening-for-github-actions.md b/translations/ko-KR/content/actions/security-guides/security-hardening-for-github-actions.md index f601ac10e2..6db6c98ac9 100644 --- a/translations/ko-KR/content/actions/security-guides/security-hardening-for-github-actions.md +++ b/translations/ko-KR/content/actions/security-guides/security-hardening-for-github-actions.md @@ -18,7 +18,6 @@ miniTocMaxHeadingLevel: 3 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 개요 @@ -48,7 +47,7 @@ To help prevent accidental disclosure, {% data variables.product.product_name %} - Rotate secrets periodically to reduce the window of time during which a compromised secret is valid. {% ifversion fpt or ghes > 3.0 or ghae %} - **Consider requiring review for access to secrets** - - You can use required reviewers to protect environment secrets. A workflow job cannot access environment secrets until approval is granted by a reviewer. For more information about storing secrets in environments or requiring reviews for environments, see "[Encrypted secrets](/actions/reference/encrypted-secrets)" and "[Environments](/actions/reference/environments)." + - You can use required reviewers to protect environment secrets. A workflow job cannot access environment secrets until approval is granted by a reviewer. For more information about storing secrets in environments or requiring reviews for environments, see "[Encrypted secrets](/actions/reference/encrypted-secrets)" and "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." {% endif %} ## Using `CODEOWNERS` to monitor changes @@ -183,6 +182,12 @@ You can help mitigate this risk by following these good practices: Although pinning to a commit SHA is the most secure option, specifying a tag is more convenient and is widely used. If you’d like to specify a tag, then be sure that you trust the action's creators. The ‘Verified creator’ badge on {% data variables.product.prodname_marketplace %} is a useful signal, as it indicates that the action was written by a team whose identity has been verified by {% data variables.product.prodname_dotcom %}. Note that there is risk to this approach even if you trust the author, because a tag can be moved or deleted if a bad actor gains access to the repository storing the action. +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## Reusing third-party workflows + +The same principles described above for using third-party actions also apply to using third-party workflows. You can help mitigate the risks associated with reusing workflows by following the same good practices outlined above. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." +{% endif %} + ## Potential impact of a compromised runner These sections consider some of the steps an attacker can take if they're able to run malicious commands on a {% data variables.product.prodname_actions %} runner. diff --git a/translations/ko-KR/content/actions/using-containerized-services/about-service-containers.md b/translations/ko-KR/content/actions/using-containerized-services/about-service-containers.md index a0357a7b9a..afc6c0d0dd 100644 --- a/translations/ko-KR/content/actions/using-containerized-services/about-service-containers.md +++ b/translations/ko-KR/content/actions/using-containerized-services/about-service-containers.md @@ -18,7 +18,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About service containers diff --git a/translations/ko-KR/content/actions/using-containerized-services/creating-postgresql-service-containers.md b/translations/ko-KR/content/actions/using-containerized-services/creating-postgresql-service-containers.md index d17d7723a2..378f832e1a 100644 --- a/translations/ko-KR/content/actions/using-containerized-services/creating-postgresql-service-containers.md +++ b/translations/ko-KR/content/actions/using-containerized-services/creating-postgresql-service-containers.md @@ -19,7 +19,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ko-KR/content/actions/using-containerized-services/creating-redis-service-containers.md b/translations/ko-KR/content/actions/using-containerized-services/creating-redis-service-containers.md index da2fcb46d9..22dde0831c 100644 --- a/translations/ko-KR/content/actions/using-containerized-services/creating-redis-service-containers.md +++ b/translations/ko-KR/content/actions/using-containerized-services/creating-redis-service-containers.md @@ -19,7 +19,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ko-KR/content/actions/using-github-hosted-runners/about-ae-hosted-runners.md b/translations/ko-KR/content/actions/using-github-hosted-runners/about-ae-hosted-runners.md index 00839bfb07..7f891d1b62 100644 --- a/translations/ko-KR/content/actions/using-github-hosted-runners/about-ae-hosted-runners.md +++ b/translations/ko-KR/content/actions/using-github-hosted-runners/about-ae-hosted-runners.md @@ -6,23 +6,16 @@ versions: ghae: '*' --- - - - -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} ## About {% data variables.actions.hosted_runner %}s -An {% data variables.actions.hosted_runner %} is a virtual machine hosted by {% data variables.product.prodname_dotcom %} with the {% data variables.product.prodname_actions %} runner service installed. +An {% data variables.actions.hosted_runner %} is a virtual machine managed by {% data variables.product.prodname_dotcom %} with the {% data variables.product.prodname_actions %} runner service installed. {% data variables.actions.hosted_runner %}s are dedicated to your enterprise, and you can choose from a range of hardware and software options. By default, {% data variables.actions.hosted_runner %}s are fully managed and auto-scaled by {% data variables.product.company_short %} to maximize performance while minimizing costs.{% ifversion ghae-next %} You can optionally configure the parameters of this auto-scaling to reduce your cost even more.{% endif %} -{% data variables.product.prodname_ghe_managed %} lets you create and customize {% data variables.actions.hosted_runner %}s using Ubuntu or Windows images; you can select the size of machine you want and configure security hardened networking for them. {% data variables.actions.hosted_runner %}s are fully managed and auto-scaled by {% data variables.product.prodname_dotcom %}. +{% data variables.product.prodname_ghe_managed %} lets you create and customize {% data variables.actions.hosted_runner %}s using Ubuntu or Windows images; you can select the size of machine you want and optionally configure a fixed public IP range for your {% data variables.actions.hosted_runner %}s. Each workflow job is executed in a fresh instance of the {% data variables.actions.hosted_runner %}, and you can run workflows directly on the virtual machine or in a Docker container. All steps in the job execute in the same instance, allowing the actions in that job to share information using the {% data variables.actions.hosted_runner %}'s filesystem. -{% note %} -{% data variables.actions.hosted_runner %}s are the only runners available for {% data variables.product.prodname_ghe_managed %}, and self-hosted runners are not available. -{% endnote %} - To add {% data variables.actions.hosted_runner %}s to your organization or enterprise, see ["Adding {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/adding-ae-hosted-runners)." ## Pool assignments for {% data variables.actions.hosted_runner %}s @@ -35,11 +28,9 @@ During the {% data variables.actions.hosted_runner %} beta, you can manage your ## Billing -{% data variables.product.prodname_actions %} is currently in beta for {% data variables.product.prodname_ghe_managed %}. During this beta period, {% data variables.actions.hosted_runner %}s are not billed, and can be used for free. - Once the beta ends, billed usage will include the full uptime of active instances in your AE hosted runner sets. 여기에는 다음이 포함됩니다. - Job time - minutes spent running Actions job. -- Management - minutes spent re-imaging machines and any idle time created as a result of desired auto-scale behavior. +- Management - minutes spent re-imaging machines{% ifversion ghae-next %} and any idle time created as a result of desired auto-scale behavior{% endif %}. Pricing will scale linearly with cores. For example, 4 cores will be twice the price of 2 cores. Windows VMs will be priced higher than Linux VMs. @@ -78,6 +69,14 @@ To get a list of IP address ranges that {% data variables.product.prodname_actio The list of {% data variables.product.prodname_actions %} IP addresses returned by the API is updated once a week. +{% ifversion ghae-next %} + +## Autoscaling + +Each pool of {% data variables.actions.hosted_runner %}s is fully managed by {% data variables.product.company_short %} to maximize performance while minimizing costs. Optionally, you can configure the autoscaling parameters for your enterprise by contacting {% data variables.contact.github_support %}. You can define the minimum number of idle runners and how long a runner should remain idle before being removed from the pool. Each pool can contain up to 600 runners. + +{% endif %} + ## Administrative privileges for {% data variables.actions.hosted_runner %}s The Linux virtual machines run using passwordless `sudo`. When you need to execute commands or install tools that require more privileges than the current user, you can use `sudo` without needing to provide a password. For more information, see the "[Sudo Manual](https://www.sudo.ws/man/1.8.27/sudo.man.html)." diff --git a/translations/ko-KR/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/translations/ko-KR/content/actions/using-github-hosted-runners/about-github-hosted-runners.md index 63c024ac8b..ccf9813e38 100644 --- a/translations/ko-KR/content/actions/using-github-hosted-runners/about-github-hosted-runners.md +++ b/translations/ko-KR/content/actions/using-github-hosted-runners/about-github-hosted-runners.md @@ -16,6 +16,7 @@ versions: shortTitle: GitHub-hosted runners --- +{% data reusables.actions.ae-hosted-runners-beta %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} diff --git a/translations/ko-KR/content/actions/using-github-hosted-runners/adding-ae-hosted-runners.md b/translations/ko-KR/content/actions/using-github-hosted-runners/adding-ae-hosted-runners.md index 93ccd85e4e..2dce61f658 100644 --- a/translations/ko-KR/content/actions/using-github-hosted-runners/adding-ae-hosted-runners.md +++ b/translations/ko-KR/content/actions/using-github-hosted-runners/adding-ae-hosted-runners.md @@ -5,7 +5,7 @@ versions: ghae: '*' --- -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} {% note %} @@ -19,7 +19,8 @@ versions: You can add {% data variables.actions.hosted_runner %}s that use the base Azure operating system images. To add {% data variables.actions.hosted_runner %}s to your organization or enterprise, contact {% data variables.product.prodname_dotcom %} support and have the following information ready: - Required operating system: Available options are listed at ["Software specifications](/actions/using-github-hosted-runners/about-ae-hosted-runners#software-specifications)." - - Choose a name for each pool of {% data variables.actions.hosted_runner %}s. These names are created as labels, allowing you to route your workflows to these runners. For more information, see ["Using {% data variables.actions.hosted_runner %}s in a workflow](/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow)." + - Choose a name for each pool of {% data variables.actions.hosted_runner %}s. These names are created as labels, allowing you to route your workflows to these runners. For more information, see ["Using {% data variables.actions.hosted_runner %}s in a workflow](/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow)."{% ifversion ghae-next %} +{% data reusables.actions.autoscaling-parameters %}{% endif %} - Where to add the {% data variables.actions.hosted_runner %}: Identify the names of the organizations and enterprises that will receive the runners. ## Adding an {% data variables.actions.hosted_runner %} with a custom image @@ -33,7 +34,8 @@ Once you've created a custom image using the above steps, contact {% data variab - Image name. - 버전. - VM SKU for the new pool. - - Choose a name for each pool of {% data variables.actions.hosted_runner %}s. These names are created as labels, allowing you to route your workflows to these runners. For more information, see ["Using {% data variables.actions.hosted_runner %}s in a workflow](/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow)." + - Choose a name for each pool of {% data variables.actions.hosted_runner %}s. These names are created as labels, allowing you to route your workflows to these runners. For more information, see ["Using {% data variables.actions.hosted_runner %}s in a workflow](/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow)."{% ifversion ghae-next %} +{% data reusables.actions.autoscaling-parameters %}{% endif %} - Where to add the {% data variables.actions.hosted_runner %}: Identify the names of the organizations and enterprises that will receive the runners. ## Reviewing your {% data variables.actions.hosted_runner %}s diff --git a/translations/ko-KR/content/actions/using-github-hosted-runners/creating-custom-images.md b/translations/ko-KR/content/actions/using-github-hosted-runners/creating-custom-images.md index c8369a8e24..5dfff3138d 100644 --- a/translations/ko-KR/content/actions/using-github-hosted-runners/creating-custom-images.md +++ b/translations/ko-KR/content/actions/using-github-hosted-runners/creating-custom-images.md @@ -5,7 +5,7 @@ versions: ghae: '*' --- -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} ## Creating an {% data variables.actions.hosted_runner %} with a custom image diff --git a/translations/ko-KR/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md b/translations/ko-KR/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md index db23278023..3fd637a69f 100644 --- a/translations/ko-KR/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md +++ b/translations/ko-KR/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md @@ -11,6 +11,7 @@ topics: shortTitle: Customize runners --- +{% data reusables.actions.ae-hosted-runners-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} If you require additional software packages on {% data variables.product.prodname_dotcom %}-hosted runners, you can create a job that installs the packages as part of your workflow. diff --git a/translations/ko-KR/content/actions/using-github-hosted-runners/index.md b/translations/ko-KR/content/actions/using-github-hosted-runners/index.md index 440c898ae1..16a4af837c 100644 --- a/translations/ko-KR/content/actions/using-github-hosted-runners/index.md +++ b/translations/ko-KR/content/actions/using-github-hosted-runners/index.md @@ -17,5 +17,6 @@ children: shortTitle: Use GitHub-hosted runners --- +{% data reusables.actions.ae-hosted-runners-beta %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} diff --git a/translations/ko-KR/content/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow.md b/translations/ko-KR/content/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow.md index 3e9154bf41..429c1cf356 100644 --- a/translations/ko-KR/content/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow.md +++ b/translations/ko-KR/content/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow.md @@ -6,7 +6,7 @@ versions: shortTitle: Use AE hosted runners --- -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} ## Using {% data variables.actions.hosted_runner %}s in a workflow diff --git a/translations/ko-KR/content/actions/using-github-hosted-runners/using-groups-to-manage-access-to-ae-hosted-runners.md b/translations/ko-KR/content/actions/using-github-hosted-runners/using-groups-to-manage-access-to-ae-hosted-runners.md index 8faf78c5c7..ea277daecd 100644 --- a/translations/ko-KR/content/actions/using-github-hosted-runners/using-groups-to-manage-access-to-ae-hosted-runners.md +++ b/translations/ko-KR/content/actions/using-github-hosted-runners/using-groups-to-manage-access-to-ae-hosted-runners.md @@ -6,7 +6,7 @@ versions: shortTitle: Manage AE runner groups --- -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} ## About {% data variables.actions.hosted_runner %} groups diff --git a/translations/ko-KR/content/actions/using-github-hosted-runners/using-labels-with-ae-hosted-runners.md b/translations/ko-KR/content/actions/using-github-hosted-runners/using-labels-with-ae-hosted-runners.md index a45dd40202..9b134dcf8f 100644 --- a/translations/ko-KR/content/actions/using-github-hosted-runners/using-labels-with-ae-hosted-runners.md +++ b/translations/ko-KR/content/actions/using-github-hosted-runners/using-labels-with-ae-hosted-runners.md @@ -6,7 +6,7 @@ versions: shortTitle: Label AE hosted runners --- -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} For information on how to use labels to route jobs to specific types of {% data variables.actions.hosted_runner %}s, see "[Using {% data variables.actions.hosted_runner %}s in a workflow](/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow)." diff --git a/translations/ko-KR/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md b/translations/ko-KR/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md index 1b7a037ec9..4eae978e32 100644 --- a/translations/ko-KR/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md +++ b/translations/ko-KR/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md @@ -62,13 +62,13 @@ If you set up the {% data variables.product.prodname_codeql %} action sync tool, {% ifversion ghes = 2.22 %} To run {% data variables.product.prodname_code_scanning %} on {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_actions %}, the appropriate actions must be available locally. You can make the actions available in three ways. -- **Recommended**: You can use [{% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud) to automatically download actions from {% data variables.product.prodname_dotcom_the_website %}. The machine that hosts your instance must be able to access {% data variables.product.prodname_dotcom_the_website %}. This approach ensures that you get the latest software automatically. For more information, see "[Configuring {% data variables.product.prodname_github_connect %} to sync {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)." +- **Recommended**: You can use [{% data variables.product.prodname_github_connect %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud) to automatically download actions from {% data variables.product.prodname_dotcom_the_website %}. The machine that hosts your instance must be able to access {% data variables.product.prodname_dotcom_the_website %}. This approach ensures that you get the latest software automatically. For more information, see "[Configuring {% data variables.product.prodname_github_connect %} to sync {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)." - If you want to use the {% data variables.product.prodname_codeql_workflow %}, you can sync the repository from {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.prodname_ghe_server %}, by using the {% data variables.product.prodname_codeql %} Action sync tool available at [https://github.com/github/codeql-action-sync-tool](https://github.com/github/codeql-action-sync-tool/). You can use this tool regardless of whether {% data variables.product.product_location %} or your {% data variables.product.prodname_actions %} runners have access to the internet, as long as you can access both {% data variables.product.product_location %} and {% data variables.product.prodname_dotcom_the_website %} simultaneously on your computer. - You can create a local copy of an action's repository on your server, by cloning the {% data variables.product.prodname_dotcom_the_website %} repository that contains the action. For example, if you want to use the actions for {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}, you can create a repository in your instance called `github/codeql-action`, then clone the [repository](https://github.com/github/codeql-action) from {% data variables.product.prodname_dotcom_the_website %}, and then push that repository to your instance's `github/codeql-action` repository. You will also need to download any of the releases from the repository on {% data variables.product.prodname_dotcom_the_website %} and upload them to your instance's `github/codeql-action` repository as releases. {% endif %} ### Configuring {% data variables.product.prodname_github_connect %} to sync {% data variables.product.prodname_actions %} -1. If you want to download action workflows on demand from {% data variables.product.prodname_dotcom_the_website %}, you need to enable {% data variables.product.prodname_github_connect %}. For more information, see "[Enabling {% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud#enabling-github-connect)." +1. If you want to download action workflows on demand from {% data variables.product.prodname_dotcom_the_website %}, you need to enable {% data variables.product.prodname_github_connect %}. For more information, see "[Enabling {% data variables.product.prodname_github_connect %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud#enabling-github-connect)." 2. You'll also need to enable {% data variables.product.prodname_actions %} for {% data variables.product.product_location %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)." 3. The next step is to configure access to actions on {% data variables.product.prodname_dotcom_the_website %} using {% data variables.product.prodname_github_connect %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)." 4. Add a self-hosted runner to your repository, organization, or enterprise account. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)." diff --git a/translations/ko-KR/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md b/translations/ko-KR/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md index e5a890b6c5..f1d4d798bc 100644 --- a/translations/ko-KR/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md +++ b/translations/ko-KR/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md @@ -83,10 +83,14 @@ For example, you can enable any {% data variables.product.prodname_GH_advanced_s ```shell ghe-config app.secret-scanning.enabled true ``` - - To enable {% data variables.product.prodname_dependabot %}, enter the following command. - ```shell - {% ifversion ghes > 3.1 %}ghe-config app.dependency-graph.enabled true{% else %}ghe-config app.github.dependency-graph-enabled true{% endif %} + - To enable {% data variables.product.prodname_dependabot %}, enter the following {% ifversion ghes > 3.1 %}command{% else %}commands{% endif %}. + {% ifversion ghes > 3.1 %}```shell + ghe-config app.dependency-graph.enabled true ``` + {% else %}```shell + ghe-config app.github.dependency-graph-enabled true + ghe-config app.github.vulnerability-alerting-and-settings-enabled true + ```{% endif %} 2. Optionally, disable features for {% data variables.product.prodname_GH_advanced_security %}. - To disable {% data variables.product.prodname_code_scanning %}, enter the following commands. @@ -98,11 +102,14 @@ For example, you can enable any {% data variables.product.prodname_GH_advanced_s ```shell ghe-config app.secret-scanning.enabled false ``` - - To disable {% data variables.product.prodname_dependabot %}, enter the following command. - ```shell - {% ifversion ghes > 3.1 %}ghe-config app.dependency-graph.enabled false{% else %}ghe-config app.github.dependency-graph-enabled false{% endif %} + - To disable {% data variables.product.prodname_dependabot %}, enter the following {% ifversion ghes > 3.1 %}command{% else %}commands{% endif %}. + {% ifversion ghes > 3.1 %}```shell + ghe-config app.dependency-graph.enabled false ``` - + {% else %}```shell + ghe-config app.github.dependency-graph-enabled false + ghe-config app.github.vulnerability-alerting-and-settings-enabled false + ```{% endif %} 3. Apply the configuration. ```shell ghe-config-apply diff --git a/translations/ko-KR/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md b/translations/ko-KR/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md index 3147524872..67c7d5b760 100644 --- a/translations/ko-KR/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md +++ b/translations/ko-KR/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md @@ -23,7 +23,7 @@ When a proxy server is enabled for {% data variables.product.product_location %} {% note %} -**Note:** To connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}, your proxy configuration must allow connectivity to `github.com` and `api.github.com`. For more information, see "[Connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_dotcom_the_website %}](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/connecting-github-enterprise-server-to-github-com)." +**Note:** To connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}, your proxy configuration must allow connectivity to `github.com` and `api.github.com`. For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_dotcom_the_website %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." {% endnote %} @@ -34,7 +34,7 @@ When a proxy server is enabled for {% data variables.product.product_location %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.privacy %} -4. Under **HTTP Proxy Server**, type the URL of your proxy server. ![Field to type the HTTP Proxy Server URL](/assets/images/enterprise/management-console/http-proxy-field.png) +1. Under **HTTP Proxy Server**, type the URL of your proxy server. ![Field to type the HTTP Proxy Server URL](/assets/images/enterprise/management-console/http-proxy-field.png) 5. Optionally, under **HTTP Proxy Exclusion**, type any hosts that do not require proxy access, separating hosts with commas. To exclude all hosts in a domain from requiring proxy access, you can use `.` as a wildcard prefix. For example: `.octo-org.tentacle` ![Field to type any HTTP Proxy Exclusions](/assets/images/enterprise/management-console/http-proxy-exclusion-field.png) diff --git a/translations/ko-KR/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md b/translations/ko-KR/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md index caa14be9ed..6727267f47 100644 --- a/translations/ko-KR/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md +++ b/translations/ko-KR/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md @@ -351,18 +351,6 @@ stop/waiting - ghe-replica-mode ``` -{% tip %} - -The service names returned from this command can be used with [`systemctl`](https://www.freedesktop.org/software/systemd/man/systemctl.html) commands to stop, start, or restart these services manually, if needed. 예시: - -```shell -$ sudo systemctl restart github-resqued -``` - -Stopping services will cause downtime on your installation, so we recommend you contact {% data variables.contact.contact_ent_support %} before stopping or restarting any service. - -{% endtip %} - ### ghe-set-password With `ghe-set-password`, you can set a new password to authenticate into the [{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-management-console). @@ -808,7 +796,7 @@ $ ssh -p 122 admin@hostname -- 'ghe-update-check' ### ghe-license-usage -This utility exports a list of the installation's users in JSON format. If your instance is connected to {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %} uses this information for reporting licensing information to {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %} ](/enterprise/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)." +This utility exports a list of the installation's users in JSON format. If your instance is connected to {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %} uses this information for reporting licensing information to {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %} ](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." By default, the list of users in the resulting JSON file is encrypted. Use the `-h` flag for more options. diff --git a/translations/ko-KR/content/admin/configuration/index.md b/translations/ko-KR/content/admin/configuration/index.md index 5b2cfee3b4..c8181bf7f7 100644 --- a/translations/ko-KR/content/admin/configuration/index.md +++ b/translations/ko-KR/content/admin/configuration/index.md @@ -12,7 +12,7 @@ topics: children: - /configuring-your-enterprise - /configuring-network-settings - - /managing-connections-between-github-enterprise-server-and-github-enterprise-cloud + - /managing-connections-between-your-enterprise-accounts --- {% ifversion ghes %} diff --git a/translations/ko-KR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md b/translations/ko-KR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md new file mode 100644 index 0000000000..f1989a6f40 --- /dev/null +++ b/translations/ko-KR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md @@ -0,0 +1,83 @@ +--- +title: Connecting your enterprise account to GitHub Enterprise Cloud +shortTitle: Connect enterprise accounts +intro: 'After you enable {% data variables.product.prodname_github_connect %}, you can share specific features and workflows between {% data variables.product.product_location %} and {% data variables.product.prodname_ghe_cloud %}.' +redirect_from: + - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-to-github-com/ + - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-server-to-github-com + - /enterprise/admin/developer-workflow/connecting-github-enterprise-server-to-githubcom/ + - /enterprise/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud + - /enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud + - /admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud +permissions: 'Enterprise owners who are also owners of a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable {% data variables.product.prodname_github_connect %}.' +versions: + ghes: '*' + ghae: next +type: how_to +topics: + - Enterprise + - GitHub Connect + - Infrastructure + - Networking +--- + +{% data reusables.github-connect.beta %} + +## About {% data variables.product.prodname_github_connect %} + +To enable {% data variables.product.prodname_github_connect %}, you must configure the connection in both {% data variables.product.product_location %} and in your {% data variables.product.prodname_ghe_cloud %} organization or enterprise account. + +{% ifversion ghes %} +To configure a connection, your proxy configuration must allow connectivity to `github.com` and `api.github.com`. For more information, see "[Configuring an outbound web proxy server](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-an-outbound-web-proxy-server)." +{% endif %} + +After enabling {% data variables.product.prodname_github_connect %}, you will be able to enable features such as unified search and unified contributions. For more information about all of the features available, see "[Managing connections between your enterprise accounts](/admin/configuration/managing-connections-between-your-enterprise-accounts)." + +When you connect {% data variables.product.product_location %} to {% data variables.product.prodname_ghe_cloud %}, a record on {% data variables.product.prodname_dotcom_the_website %} stores information about the connection: +{% ifversion ghes %} +- The public key portion of your {% data variables.product.prodname_ghe_server %} license +- A hash of your {% data variables.product.prodname_ghe_server %} license +- The customer name on your {% data variables.product.prodname_ghe_server %} license +- The version of {% data variables.product.product_location_enterprise %}{% endif %} +- The hostname of your {% data variables.product.product_name %} instance +- The organization or enterprise account on {% data variables.product.prodname_dotcom_the_website %} that's connected to {% data variables.product.product_location %} +- The authentication token that's used by {% data variables.product.product_location %} to make requests to {% data variables.product.prodname_dotcom_the_website %} + +Enabling {% data variables.product.prodname_github_connect %} also creates a {% data variables.product.prodname_github_app %} owned by your {% data variables.product.prodname_ghe_cloud %} organization or enterprise account. {% data variables.product.product_name %} uses the {% data variables.product.prodname_github_app %}'s credentials to make requests to {% data variables.product.prodname_dotcom_the_website %}. +{% ifversion ghes %} +{% data variables.product.prodname_ghe_server %} stores credentials from the {% data variables.product.prodname_github_app %}. These credentials will be replicated to any high availability or clustering environments, and stored in any backups, including snapshots created by {% data variables.product.prodname_enterprise_backup_utilities %}. +- An authentication token, which is valid for one hour +- A private key, which is used to generate a new authentication token +{% endif %} + +Enabling {% data variables.product.prodname_github_connect %} will not allow {% data variables.product.prodname_dotcom_the_website %} users to make changes to {% data variables.product.product_name %}. + +For more information about managing enterprise accounts using the GraphQL API, see "[Enterprise accounts](/graphql/guides/managing-enterprise-accounts)." +## Enabling {% data variables.product.prodname_github_connect %} + +{% ifversion ghes %} +1. Sign in to {% data variables.product.product_location %} and {% data variables.product.prodname_dotcom_the_website %}. +{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %}{% else %} +1. Sign in to {% data variables.product.product_location %} and {% data variables.product.prodname_dotcom_the_website %}. +{% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %} +1. Under "{% data variables.product.prodname_github_connect %} is not enabled yet", click **Enable {% data variables.product.prodname_github_connect %}**. By clicking **Enable {% data variables.product.prodname_github_connect %}**, you agree to the "{% data variables.product.prodname_dotcom %} Terms for Additional Products and Features." +{% ifversion ghes %} +![Enable GitHub Connect button](/assets/images/enterprise/business-accounts/enable-github-connect-button.png){% else %} +![Enable GitHub Connect button](/assets/images/enterprise/github-ae/enable-github-connect-button.png) +{% endif %} +1. Next to the enterprise account or organization you'd like to connect, click **Connect**. ![Connect button next to an enterprise account or business](/assets/images/enterprise/business-accounts/choose-enterprise-or-org-connect.png) + +## Disconnecting a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account from your enterprise account + +When you disconnect from {% data variables.product.prodname_ghe_cloud %}, the {% data variables.product.prodname_github_connect %} {% data variables.product.prodname_github_app %} is deleted from your enterprise account or organization and credentials stored on {% data variables.product.product_location %} are deleted. + +{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %} +1. Next to the enterprise account or organization you'd like to disconnect, click **Disable {% data variables.product.prodname_github_connect %}**. +{% ifversion ghes %} + ![Disable GitHub Connect button next to an enterprise account or organization name](/assets/images/enterprise/business-accounts/disable-github-connect-button.png) +1. Read the information about disconnecting and click **Disable {% data variables.product.prodname_github_connect %}**. ![Modal with warning information about disconnecting and confirmation button](/assets/images/enterprise/business-accounts/confirm-disable-github-connect.png) +{% else %} + ![Disable GitHub Connect button next to an enterprise account or organization name](/assets/images/enterprise/github-ae/disable-github-connect-button.png) +1. Read the information about disconnecting and click **Disable {% data variables.product.prodname_github_connect %}**. ![Modal with warning information about disconnecting and confirmation button](/assets/images/enterprise/github-ae/confirm-disable-github-connect.png) +{% endif %} diff --git a/translations/ko-KR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md b/translations/ko-KR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md new file mode 100644 index 0000000000..833252c0fb --- /dev/null +++ b/translations/ko-KR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md @@ -0,0 +1,97 @@ +--- +title: Enabling alerts for vulnerable dependencies on GitHub Enterprise Server +intro: 'You can connect {% data variables.product.product_location %} to {% data variables.product.prodname_ghe_cloud %} and enable the dependency graph and {% ifversion ghes %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts in repositories in your instance.' +shortTitle: Enable alerts for dependencies +miniTocMaxHeadingLevel: 3 +redirect_from: + - /enterprise/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /enterprise/admin/configuration/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /enterprise/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server +permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable the dependency graph and {% data variables.product.prodname_dependabot %} alerts on {% data variables.product.prodname_ghe_server %}.' +versions: + ghes: '*' +type: how_to +topics: + - Enterprise + - Security + - Dependency graph + - Dependabot +--- + +## About alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %} + +To identify vulnerable dependencies in your repository and receive alerts about vulnerabilities, you need to enable two security features: +- The dependency graph +- {% data variables.product.prodname_dependabot %} alerts + +For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" and "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." + +{% data reusables.repositories.tracks-vulnerabilities %} + +You can connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}, then sync vulnerability data to your instance and generate {% data variables.product.prodname_dependabot_alerts %} in repositories with a vulnerable dependency. + +After connecting {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %} and enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies, vulnerability data is synced from {% data variables.product.prodname_dotcom_the_website %} to your instance once every hour. You can also choose to manually sync vulnerability data at any time. No code or information about code from {% data variables.product.product_location %} is uploaded to {% data variables.product.prodname_dotcom_the_website %}. + +When {% data variables.product.product_location %} receives information about a vulnerability, it will identify repositories in your instance that use the affected version of the dependency and generate {% data variables.product.prodname_dependabot_alerts %}. You can customize how you receive {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies/#configuring-notifications-for-dependabot-alerts)." + +Before enabling the dependency graph and {% ifversion ghes > 2.21 %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts for vulnerable dependencies on {% data variables.product.product_location %}, you must connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." + +## Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} on GitHub Enterprise Server + +For {% data variables.product.product_location %} to generate {% data variables.product.prodname_dependabot_alerts %} whenever vulnerabilities are detected on your repositories: +- You must connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %}](/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)." +- You must enable the dependency graph. + +{% ifversion ghes > 3.1 %} +You can enable the dependency graph via the {% data variables.enterprise.management_console %} or the administrative shell. We recommend you follow the {% data variables.enterprise.management_console %} route unless {% data variables.product.product_location %} uses clustering. + +### Enabling the dependency graph via the {% data variables.enterprise.management_console %} +{% endif %}{% ifversion ghes > 3.1 %} +{% data reusables.enterprise_site_admin_settings.sign-in %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.advanced-security-tab %} +1. Under "Security," click **Dependency graph**. ![Checkbox to enable or disable the dependency graph](/assets/images/enterprise/3.2/management-console/enable-dependency-graph-checkbox.png) +{% data reusables.enterprise_management_console.save-settings %} +1. Click **Visit your instance**. + +### Enabling the dependency graph via the administrative shell +{% else %} +### Enabling the dependency graph +{% endif %} +{% data reusables.enterprise_site_admin_settings.sign-in %} +1. In the administrative shell, enable the dependency graph on {% data variables.product.product_location %}: + ``` shell + $ {% ifversion ghes > 3.1 %}ghe-config app.dependency-graph.enabled true{% else %}ghe-config app.github.dependency-graph-enabled true{% endif %} + ``` + {% note %} + + **Note**: For more information about enabling access to the administrative shell via SSH, see "[Accessing the administrative shell (SSH)](/enterprise/{{ currentVersion }}/admin/configuration/accessing-the-administrative-shell-ssh)." + + {% endnote %} +1. Apply the configuration. + ```shell + $ ghe-config-apply + ``` +1. Return to {% data variables.product.prodname_ghe_server %}. + +### Enabling {% data variables.product.prodname_dependabot_alerts %} + +Before enabling {% data variables.product.prodname_dependabot_alerts %} for your instance, you need to enable the dependency graph. For more information, see above. + +{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %} +1. Under "Repositories can be scanned for vulnerabilities", use the drop-down menu and select **Enabled without notifications**. Optionally, to enable alerts with notifications, select **Enabled with notifications**. ![Drop-down menu to enable scanning repositories for vulnerabilities](/assets/images/enterprise/site-admin-settings/enable-vulnerability-scanning-in-repositories.png) + {% note %} + + We recommend configuring {% data variables.product.prodname_dependabot_alerts %} without notifications for the first few days to avoid an overload of emails. After a few days, you can enable notifications to receive {% data variables.product.prodname_dependabot_alerts %} as usual. + + {% endnote %} +## Viewing vulnerable dependencies on {% data variables.product.prodname_ghe_server %} + +You can view all vulnerabilities in {% data variables.product.product_location %} and manually sync vulnerability data from {% data variables.product.prodname_dotcom_the_website %} to update the list. + +{% data reusables.enterprise_site_admin_settings.access-settings %} +2. In the left sidebar, click **Vulnerabilities**. ![Vulnerabilities tab in the site admin sidebar](/assets/images/enterprise/business-accounts/vulnerabilities-tab.png) +3. To sync vulnerability data, click **Sync Vulnerabilities now**. ![Sync vulnerabilities now button](/assets/images/enterprise/site-admin-settings/sync-vulnerabilities-button.png) diff --git a/translations/ko-KR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md b/translations/ko-KR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md new file mode 100644 index 0000000000..26eb670429 --- /dev/null +++ b/translations/ko-KR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md @@ -0,0 +1,31 @@ +--- +title: Enabling automatic user license sync between GitHub Enterprise Server and GitHub Enterprise Cloud +intro: 'You can connect {% data variables.product.product_location_enterprise %} to {% data variables.product.prodname_ghe_cloud %} and allow {% data variables.product.prodname_ghe_server %} to upload user license information to your enterprise account on {% data variables.product.prodname_dotcom_the_website %}.' +redirect_from: + - /enterprise/admin/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud + - /enterprise/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud + - /admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud +permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable automatic user license synchronization.' +versions: + ghes: '*' +type: how_to +topics: + - Enterprise + - GitHub Connect + - Licensing +shortTitle: Enable user license sync +--- + +## About license synchronization + +After you enable license synchronization, you'll be able to view license usage for your entire enterprise account, across {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}. {% data variables.product.prodname_github_connect %} syncs license between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %} weekly. For more information, see "[Managing your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise)." + +You can also manually upload {% data variables.product.prodname_ghe_server %} user license information to {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." + +## Enabling license synchronization + +Before enabling license synchronization on {% data variables.product.product_location_enterprise %}, you must connect {% data variables.product.product_location_enterprise %} to {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." + +{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %} +1. Under "Server can sync user license count and usage", use the drop-down menu and select **Enabled**. ![Drop-down menu to enable automatic user license sync](/assets/images/enterprise/site-admin-settings/enable-user-license-drop-down.png) diff --git a/translations/ko-KR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md b/translations/ko-KR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md new file mode 100644 index 0000000000..6d4a2dd1b1 --- /dev/null +++ b/translations/ko-KR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md @@ -0,0 +1,46 @@ +--- +title: Enabling unified contributions between your enterprise account and GitHub.com +shortTitle: Enable unified contributions +intro: 'After enabling {% data variables.product.prodname_github_connect %}, you can allow {% data variables.product.prodname_ghe_cloud %} members to highlight their work on {% data variables.product.product_name %} by sending the contribution counts to their {% data variables.product.prodname_dotcom_the_website %} profiles.' +redirect_from: + - /enterprise/admin/guides/developer-workflow/enabling-unified-contributions-between-github-enterprise-and-github-com/ + - /enterprise/admin/guides/developer-workflow/enabling-unified-contributions-between-github-enterprise-server-and-github-com/ + - /enterprise/admin/developer-workflow/enabling-unified-contributions-between-github-enterprise-server-and-githubcom/ + - /enterprise/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom + - /enterprise/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom + - /admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-unified-contributions-between-github-enterprise-server-and-githubcom +permissions: 'Enterprise owners who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable unified contributions between {% data variables.product.product_location %} and {% data variables.product.prodname_dotcom_the_website %}.' +versions: + ghes: '*' + ghae: next +type: how_to +topics: + - Enterprise + - GitHub Connect +--- + +{% data reusables.github-connect.beta %} + +As an enterprise owner, you can allow end users to send anonymized contribution counts for their work from {% data variables.product.product_location %} to their {% data variables.product.prodname_dotcom_the_website %} contribution graph. + +After you enable {% data variables.product.prodname_github_connect %} and enable {% data variables.product.prodname_unified_contributions %} in both environments, end users on your enterprise account can connect to their {% data variables.product.prodname_dotcom_the_website %} accounts and send contribution counts from {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.github-connect.sync-frequency %} 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)." + +If the enterprise owner disables the functionality or developers opt out of the connection, the {% data variables.product.product_name %} contribution counts will be deleted on {% data variables.product.prodname_dotcom_the_website %}. If the developer reconnects their profiles after disabling them, the contribution counts for the past 90 days are restored. + +{% data variables.product.product_name %} **only** sends the contribution count and source ({% data variables.product.product_name %}) for connected users. It does not send any information about the contribution or how it was made. + +Before enabling {% data variables.product.prodname_unified_contributions %} on {% data variables.product.product_location %}, you must connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_dotcom_the_website %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." + +{% ifversion ghes %} +{% data reusables.github-connect.access-dotcom-and-enterprise %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.business %} +{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %}{% else %} +1. Sign in to {% data variables.product.product_location %} and {% data variables.product.prodname_dotcom_the_website %}. +{% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %} +1. Under "Users can share contribution counts to {% data variables.product.prodname_dotcom_the_website %}", click **Request access**. ![Request access to unified contributions option](/assets/images/enterprise/site-admin-settings/dotcom-ghe-connection-request-access.png){% ifversion ghes %} +2. [Sign in](https://enterprise.github.com/login) to the {% data variables.product.prodname_ghe_server %} site to receive further instructions. + +When you request access, we may redirect you to the {% data variables.product.prodname_ghe_server %} site to check your current terms of service. +{% endif %} diff --git a/translations/ko-KR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md b/translations/ko-KR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md new file mode 100644 index 0000000000..abde191ac2 --- /dev/null +++ b/translations/ko-KR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md @@ -0,0 +1,44 @@ +--- +title: Enabling unified search between your enterprise account and GitHub.com +shortTitle: Enable unified search +intro: 'After enabling {% data variables.product.prodname_github_connect %}, you can allow search of {% data variables.product.prodname_dotcom_the_website %} for members of your enterprise on {% data variables.product.product_name %}.' +redirect_from: + - /enterprise/admin/guides/developer-workflow/enabling-unified-search-between-github-enterprise-and-github-com/ + - /enterprise/admin/guides/developer-workflow/enabling-unified-search-between-github-enterprise-server-and-github-com/ + - /enterprise/admin/developer-workflow/enabling-unified-search-between-github-enterprise-server-and-githubcom/ + - /enterprise/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom + - /enterprise/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom + - /admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-unified-search-between-github-enterprise-server-and-githubcom +permissions: 'Enterprise owners who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable unified search between {% data variables.product.product_name %} and {% data variables.product.prodname_dotcom_the_website %}.' +versions: + ghes: '*' + ghae: next +topics: + - Enterprise + - GitHub Connect + - GitHub search +--- + +{% data reusables.github-connect.beta %} + +When you enable unified search, users can view search results from public and private content on {% data variables.product.prodname_dotcom_the_website %} when searching from {% data variables.product.product_location %}{% ifversion ghae %} on {% data variables.product.prodname_ghe_managed %}{% endif %}. + +Users will not be able to search {% data variables.product.product_location %} from {% data variables.product.prodname_dotcom_the_website %}, even if they have access to both environments. Users can only search private repositories you've enabled {% data variables.product.prodname_unified_search %} for and that they have access to in the connected {% data variables.product.prodname_ghe_cloud %} organizations. For more information, see "[About searching on {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github/#searching-across-github-enterprise-and-githubcom-simultaneously)" and "[Enabling private {% data variables.product.prodname_dotcom_the_website %} repository search in your enterprise account](/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment)." + +Searching via the REST and GraphQL APIs does not include {% data variables.product.prodname_dotcom_the_website %} search results. Advanced search and searching for wikis in {% data variables.product.prodname_dotcom_the_website %} are not supported. + +{% ifversion ghes %} +{% data reusables.github-connect.access-dotcom-and-enterprise %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.business %} +{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %}{% else %} +1. Sign in to {% data variables.product.product_location %} and {% data variables.product.prodname_dotcom_the_website %}. +{% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %} +1. Under "Users can search {% data variables.product.prodname_dotcom_the_website %}", use the drop-down menu and click **Enabled**. ![Enable search option in the search GitHub.com drop-down menu](/assets/images/enterprise/site-admin-settings/github-dotcom-enable-search.png) +1. Optionally, under "Users can search private repositories on {% data variables.product.prodname_dotcom_the_website %}", use the drop-down menu and click **Enabled**. ![Enable private repositories search option in the search GitHub.com drop-down menu](/assets/images/enterprise/site-admin-settings/enable-private-search.png) + +## 더 읽을거리 + +- "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)" + diff --git a/translations/ko-KR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md b/translations/ko-KR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md new file mode 100644 index 0000000000..3da64d323b --- /dev/null +++ b/translations/ko-KR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md @@ -0,0 +1,25 @@ +--- +title: Managing connections between your enterprise accounts +intro: 'With {% data variables.product.prodname_github_connect %}, you can share certain features and data between {% data variables.product.product_location %} and your {% data variables.product.prodname_ghe_cloud %} organization or enterprise account on {% data variables.product.prodname_dotcom_the_website %}.' +redirect_from: + - /enterprise/admin/developer-workflow/connecting-github-enterprise-to-github-com + - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-and-github-com/ + - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-server-and-github-com/ + - /enterprise/admin/developer-workflow/connecting-github-enterprise-server-and-githubcom/ + - /enterprise/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud + - /enterprise/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud +versions: + ghes: '*' + ghae: next +topics: + - Enterprise +children: + - /connecting-your-enterprise-account-to-github-enterprise-cloud + - /enabling-unified-search-between-your-enterprise-account-and-githubcom + - /enabling-unified-contributions-between-your-enterprise-account-and-githubcom + - /enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud +shortTitle: Connect enterprise accounts +--- + diff --git a/translations/ko-KR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/ko-KR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md index f49b080b25..40796eebe5 100644 --- a/translations/ko-KR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md +++ b/translations/ko-KR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md @@ -37,19 +37,46 @@ This article explains how site administrators can configure {% data variables.pr {% endif %} +{%- ifversion ghes < 3.2 %} + The CPU and memory resources available to {% data variables.product.product_location %} determine the maximum job throughput for {% data variables.product.prodname_actions %}. Internal testing at {% data variables.product.company_short %} demonstrated the following maximum throughput for {% data variables.product.prodname_ghe_server %} instances with a range of CPU and memory configurations. You may see different throughput depending on the overall levels of activity on your instance. +{%- endif %} + +{%- ifversion ghes > 3.1 %} + +The CPU and memory resources available to {% data variables.product.product_location %} determine the number of jobs that can be run concurrently without performance loss. + +The peak quantity of concurrent jobs running without performance loss depends on such factors as job duration, artifact usage, number of repositories running Actions, and how much other work your instance is doing not related to Actions. Internal testing at GitHub demonstrated the following performance targets for GitHub Enterprise Server on a range of CPU and memory configurations: + +{% endif %} + +{%- ifversion ghes < 3.2 %} + | vCPUs | Memory | Maximum job throughput | |:----- |:------ |:---------------------- | -| | | | -{%- ifversion ghes > 3.1 %} -| 4 | 32 GB | Demo or light testing | | 8 | 64 GB | 30 jobs | | 16 | 128 GB | 60 jobs | | 32 | 256 GB | 120 jobs | | 64 | 512 GB | 160 jobs | -{%- else ifversion ghes < 3.2 %} -| 4 | 32 GB | Demo or light testing | | 8 | 64 GB | 25 jobs | | 16 | 160 GB | 35 jobs | | 32 | 256 GB | 100 jobs | +| 4 | 32 GB | Demo or light testing | +| 8 | 64 GB | 25 jobs | +| 16 | 160 GB | 35 jobs | +| 32 | 256 GB | 100 jobs | + {%- endif %} +{%- ifversion ghes > 3.1 %} + +| vCPUs | Memory | Maximum Concurrency* | +|:----- |:------ |:-------------------- | +| 32 | 128 GB | 1500 jobs | +| 64 | 256 GB | 1900 jobs | +| 96 | 384 GB | 2200 jobs | + +*Maximum concurrency was measured using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. You may experience different performance depending on the overall levels of activity on your instance. + +{%- endif %} + + If you {% ifversion ghes = 2.22 %}enabled the beta of{% else %}plan to enable{% endif %} {% data variables.product.prodname_actions %} for the users of an existing instance, review the levels of activity for users and automations on the instance and ensure that you have provisioned adequate CPU and memory for your users. For more information about monitoring the capacity and performance of {% data variables.product.prodname_ghe_server %}, see "[Monitoring your appliance](/admin/enterprise-management/monitoring-your-appliance)." For more information about minimum hardware requirements for {% data variables.product.product_location %}, see the hardware considerations for your instance's platform. diff --git a/translations/ko-KR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md b/translations/ko-KR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md index b527e6f084..812c378557 100644 --- a/translations/ko-KR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md +++ b/translations/ko-KR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md @@ -10,7 +10,6 @@ children: - /enabling-github-actions-with-azure-blob-storage - /enabling-github-actions-with-amazon-s3-storage - /enabling-github-actions-with-minio-gateway-for-nas-storage - - /enforcing-github-actions-policies-for-your-enterprise shortTitle: Enable GitHub Actions --- diff --git a/translations/ko-KR/content/admin/github-actions/index.md b/translations/ko-KR/content/admin/github-actions/index.md index fe0779539f..d0fb8bafcd 100644 --- a/translations/ko-KR/content/admin/github-actions/index.md +++ b/translations/ko-KR/content/admin/github-actions/index.md @@ -16,6 +16,5 @@ children: shortTitle: Manage GitHub Actions --- -{% data reusables.actions.ae-beta %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} diff --git a/translations/ko-KR/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md b/translations/ko-KR/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md index 42282a53e2..8b661db885 100644 --- a/translations/ko-KR/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md +++ b/translations/ko-KR/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md @@ -18,7 +18,6 @@ shortTitle: Add actions in your enterprise {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data variables.product.prodname_actions %} workflows can use _actions_, which are individual tasks that you can combine to create jobs and customize your workflow. You can create your own actions, or use and customize actions shared by the {% data variables.product.prodname_dotcom %} community. diff --git a/translations/ko-KR/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md b/translations/ko-KR/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md index 831d376076..a8ef49b657 100644 --- a/translations/ko-KR/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md +++ b/translations/ko-KR/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md @@ -19,7 +19,6 @@ shortTitle: Use GitHub Connect for actions {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.actions.enterprise-github-connect-warning %} -{% data reusables.actions.ae-beta %} By default, {% data variables.product.prodname_actions %} workflows on {% data variables.product.product_name %} cannot use actions directly from {% data variables.product.prodname_dotcom_the_website %} or [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions). @@ -27,8 +26,16 @@ To make all actions from {% data variables.product.prodname_dotcom_the_website % ## Enabling automatic access to all {% data variables.product.prodname_dotcom_the_website %} actions -Before enabling access to all actions from {% data variables.product.prodname_dotcom_the_website %} on your enterprise instance, you must connect your enterprise to {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %}](/enterprise/{{ currentVersion }}/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)." +Before enabling access to all actions from {% data variables.product.prodname_dotcom_the_website %} on your enterprise instance, you must connect your enterprise to {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Connecting your enterprise to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." -{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %} +{% data reusables.enterprise-accounts.access-enterprise %} +{%- ifversion ghes < 3.1 %} +{% data reusables.enterprise-accounts.settings-tab %} +{%- endif %} +{% data reusables.enterprise-accounts.github-connect-tab %} +{%- ifversion ghes > 3.0 or ghae %} +1. Under "Users can utilize actions from GitHub.com in workflow runs", use the drop-down menu and select **Enabled**. ![Drop-down menu to actions from GitHub.com in workflows runs](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down-ae.png) +{%- else %} 1. Under "Server can use actions from GitHub.com in workflows runs", use the drop-down menu and select **Enabled**. ![Drop-down menu to actions from GitHub.com in workflows runs](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down.png) +{%- endif %} 1. {% data reusables.actions.enterprise-limit-actions-use %} diff --git a/translations/ko-KR/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md b/translations/ko-KR/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md index 39ad93da5e..4993bf41c6 100644 --- a/translations/ko-KR/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md +++ b/translations/ko-KR/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md @@ -14,13 +14,14 @@ shortTitle: Manually sync actions {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.actions.enterprise-no-internet-actions %} -The recommended approach of enabling access to actions from {% data variables.product.prodname_dotcom_the_website %} is to enable automatic access to all actions. You can do this by using {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.product_name %} with {% data variables.product.prodname_ghe_cloud %} . For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". +{% ifversion ghes or ghae-next %} -However, if you want stricter control over which actions are allowed in your enterprise, you can follow this guide to use {% data variables.product.company_short %}'s open source [`actions-sync`](https://github.com/actions/actions-sync) tool to sync individual action repositories from {% data variables.product.prodname_dotcom_the_website %} to your enterprise. +The recommended approach of enabling access to actions from {% data variables.product.prodname_dotcom_the_website %} is to enable automatic access to all actions. You can do this by using {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.product_name %} with {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)." + +However, if you want stricter control over which actions are allowed in your enterprise, you{% else %}You{% endif %} can follow this guide to use {% data variables.product.company_short %}'s open source [`actions-sync`](https://github.com/actions/actions-sync) tool to sync individual action repositories from {% data variables.product.prodname_dotcom_the_website %} to your enterprise. ## About the `actions-sync` tool @@ -33,7 +34,7 @@ The `actions-sync` tool can only download actions from {% data variables.product ## 빌드전 요구 사양 * Before using the `actions-sync` tool, you must ensure that all destination organizations already exist in your enterprise. The following example demonstrates how to sync actions to an organization named `synced-actions`. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." -* You must create a personal access token (PAT) on your enterprise that can create and write to repositories in the destination organizations. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." +* You must create a personal access token (PAT) on your enterprise that can create and write to repositories in the destination organizations. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."{% ifversion ghes %} * If you want to sync the bundled actions in the `actions` organization on {% data variables.product.product_location %}, you must be an owner of the `actions` organization. {% note %} @@ -46,7 +47,7 @@ The `actions-sync` tool can only download actions from {% data variables.product ```shell ghe-org-admin-promote -u USERNAME -o actions - ``` + ```{% endif %} ## Example: Using the `actions-sync` tool diff --git a/translations/ko-KR/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md b/translations/ko-KR/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md index d4198fa660..963f784bf8 100644 --- a/translations/ko-KR/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md +++ b/translations/ko-KR/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md @@ -14,7 +14,6 @@ shortTitle: Tool cache for offline runners {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About the included setup actions and the runner tool cache diff --git a/translations/ko-KR/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md b/translations/ko-KR/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md index 48d0687447..668cbc3bc3 100644 --- a/translations/ko-KR/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md +++ b/translations/ko-KR/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md @@ -13,7 +13,6 @@ shortTitle: Use the latest bundled actions {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} Your enterprise instance includes a number of built-in actions that you can use in your workflows. For more information about the bundled actions, see "[Official actions bundled with your enterprise instance](/admin/github-actions/about-using-actions-in-your-enterprise#official-actions-bundled-with-your-enterprise-instance)." @@ -29,17 +28,13 @@ You can use {% data variables.product.prodname_github_connect %} to allow {% dat Once {% data variables.product.prodname_github_connect %} is configured, you can use the latest version of an action by deleting its local repository in the `actions` organization on your instance. For example, if your enterprise instance is using the `actions/checkout@v1` action, and you need to use `actions/checkout@v2` which isn't available on your enterprise instance, perform the following steps to be able to use the latest `checkout` action from {% data variables.product.prodname_dotcom_the_website %}: -1. By default, site administrators are not owners of the bundled actions organization. To get the required access to delete the `checkout` repository, use the `ghe-org-admin-promote` command to promote a user to be an owner of the bundled `actions` organization. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" and "[`ghe-org-admin-promote`](/admin/configuration/command-line-utilities#ghe-org-admin-promote)." 예시: - - ```shell - $ ghe-org-admin-promote -u octocat -o actions - Do you want to give organization admin privileges for actions to octocat? (y/N) y - Making octocat an admin of actions - --> Adding octocat as an admin of actions - --> octocat is now an admin of the actions organization - --> Done. - ``` -1. On your {% data variables.product.product_name %} instance, delete the `checkout` repository within the `actions` organization. For information on how to delete a repository, see "[Deleting a repository ](/github/administering-a-repository/deleting-a-repository)." -1. It is recommended that you leave the `actions` organization once you no longer require administrative access. For more information, see "[Removing yourself from an organization ](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization)." +1. From an enterprise owner account on {% data variables.product.product_name %}, navigate to the repository you want to delete from the *actions* organization (in this example `checkout`). +1. By default, site administrators are not owners of the bundled *actions* organization. To get the access required to delete the `checkout` repository, you must use the site admin tools. Click {% octicon "rocket" aria-label="The rocket ship" %} in the upper-right corner of any page in that repository. ![Rocketship icon for accessing site admin settings](/assets/images/enterprise/site-admin-settings/access-new-settings.png) +1. Click {% octicon "shield-lock" %} **Security** to see the security overview for the repository. ![Security header the repository](/assets/images/enterprise/site-admin-settings/access-repo-security-info.png) +1. Under "Privileged access", click **Unlock**. ![Unlock button](/assets/images/enterprise/site-admin-settings/unlock-priviledged-repo-access.png) +1. Under **Reason**, type a reason for unlocking the repository, then click **Unlock**. ![Confirmation dialog](/assets/images/enterprise/site-admin-settings/confirm-unlock-repo-access.png) +1. Now that the repository is unlocked, you can leave the site admin pages and delete the repository within the `actions` organization. At the top of the page, click the repository name, in this example **checkout**, to return to the summary page. ![Repository name link](/assets/images/enterprise/site-admin-settings/display-repository-admin-summary.png) +1. Under "Repository info", click **View code** to leave the site admin pages and display the `checkout` repository. +1. Delete the `checkout` repository within the `actions` organization. For information on how to delete a repository, see "[Deleting a repository](/github/administering-a-repository/deleting-a-repository)." ![View code link](/assets/images/enterprise/site-admin-settings/exit-admin-page-for-repository.png) 1. Configure your workflow's YAML to use `actions/checkout@v2`. 1. Each time your workflow runs, the runner will use the `v2` version of `actions/checkout` from {% data variables.product.prodname_dotcom_the_website %}. diff --git a/translations/ko-KR/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md b/translations/ko-KR/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md index 5337563413..e0bb78239d 100644 --- a/translations/ko-KR/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md +++ b/translations/ko-KR/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md @@ -13,7 +13,6 @@ redirect_from: - /admin/github-actions/getting-started-with-github-actions-for-github-ae --- -{% data reusables.actions.ae-beta %} This article explains how site administrators can configure {% data variables.product.prodname_ghe_managed %} to use {% data variables.product.prodname_actions %}. diff --git a/translations/ko-KR/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md b/translations/ko-KR/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md index 6a995ba974..9049ffa719 100644 --- a/translations/ko-KR/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md +++ b/translations/ko-KR/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md @@ -8,7 +8,6 @@ redirect_from: shortTitle: Use actions --- -{% data reusables.actions.ae-beta %} {% data variables.product.prodname_actions %} workflows can use _actions_, which are individual tasks that you can combine to create jobs and customize your workflow. You can create your own actions, or use and customize actions shared by the {% data variables.product.prodname_dotcom %} community. diff --git a/translations/ko-KR/content/admin/guides.md b/translations/ko-KR/content/admin/guides.md index 70dd559cd5..3491827fe8 100644 --- a/translations/ko-KR/content/admin/guides.md +++ b/translations/ko-KR/content/admin/guides.md @@ -35,13 +35,13 @@ includeGuides: - /admin/configuration/configuring-rate-limits - /admin/configuration/configuring-secret-scanning-for-your-appliance - /admin/configuration/configuring-tls - - /admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud + - /admin/configuration/connecting-your-enterprise-account-to-github-enterprise-cloud - /admin/configuration/enabling-and-scheduling-maintenance-mode - /admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud - /admin/configuration/enabling-private-mode - /admin/configuration/enabling-subdomain-isolation - - /admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom - - /admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom + - /admin/configuration/enabling-unified-contributions-between-your-enterprise-account-and-githubcom + - /admin/configuration/enabling-unified-search-between-your-enterprise-account-and-githubcom - /admin/configuration/initializing-github-ae - /admin/configuration/managing-github-for-mobile-for-your-enterprise - /admin/configuration/network-ports diff --git a/translations/ko-KR/content/admin/overview/about-upgrades-to-new-releases.md b/translations/ko-KR/content/admin/overview/about-upgrades-to-new-releases.md index 5a0cf5b66f..db601630d4 100644 --- a/translations/ko-KR/content/admin/overview/about-upgrades-to-new-releases.md +++ b/translations/ko-KR/content/admin/overview/about-upgrades-to-new-releases.md @@ -13,7 +13,7 @@ topics: {% data variables.product.product_name %} is constantly improving, with new functionality and bug fixes introduced through major and minor releases. {% ifversion ghae %}{% data variables.product.prodname_ghe_managed %} is a fully managed service, so {% data variables.product.company_short %} completes the upgrade process for your enterprise.{% endif %} -Major releases include new functionality and feature upgrades and typically occur {% ifversion ghae %}every few weeks or months{% else %} quarterly{% endif %}. {% ifversion ghae %}{% data variables.product.company_short %} will upgrade your enterprise to the latest major release. You will be given advance notice of any planned downtime for your enterprise.{% endif %} +Major releases include new functionality and feature upgrades and typically occur quarterly. {% ifversion ghae %}{% data variables.product.company_short %} will upgrade your enterprise to the latest major release. You will be given advance notice of any planned downtime for your enterprise.{% endif %} {% ifversion ghes %} @@ -43,7 +43,6 @@ To upgrade your enterprise to a new release, see "[Release notes](/enterprise-se ## 더 읽을거리 -- [ {% data variables.product.prodname_roadmap %} ]({% data variables.product.prodname_roadmap_link %}) in the `github/roadmap` repository -{% ifversion ghae %} +- [ {% data variables.product.prodname_roadmap %} ]({% data variables.product.prodname_roadmap_link %}) in the `github/roadmap` repository{% ifversion ghae %} - [ {% data variables.product.prodname_ghe_managed %} release notes](/admin/release-notes) {% endif %} diff --git a/translations/ko-KR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise.md b/translations/ko-KR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise.md new file mode 100644 index 0000000000..6975629cf9 --- /dev/null +++ b/translations/ko-KR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise.md @@ -0,0 +1,59 @@ +--- +title: Enforcing GitHub Actions policies for your enterprise +intro: 'Enterprise administrators can manage access to {% data variables.product.prodname_actions %} in an enterprise.' +redirect_from: + - /enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise + - /admin/github-actions/enforcing-github-actions-policies-for-your-enterprise + - /admin/github-actions/enabling-github-actions-for-github-enterprise-server/enforcing-github-actions-policies-for-your-enterprise +versions: + ghes: '*' + ghae: '*' +type: how_to +topics: + - Actions + - Enterprise + - Policies +shortTitle: GitHub Actions policies +--- + +{% data reusables.actions.enterprise-beta %} + +## About {% data variables.product.prodname_actions %} permissions for your enterprise + +{% ifversion ghae %}{% else %}When you enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}, it is enabled for all organizations in your enterprise. {% endif %}You can choose to disable {% data variables.product.prodname_actions %} for all organizations in your enterprise, or only allow specific organizations. You can also limit the use of public actions, so that people can only use local actions that exist in your enterprise. + +## Managing {% data variables.product.prodname_actions %} permissions for your enterprise + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.actions-tab %} +{% data reusables.actions.enterprise-actions-permissions %} + +{% ifversion ghes > 2.22 or ghae %} +## Allowing specific actions to run + +{% data reusables.actions.allow-specific-actions-intro %} + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.actions-tab %} +1. Under **Policies**, select **Allow select actions** and add your required actions to the list. + {%- ifversion ghes or ghae-issue-5094 %} + ![Add actions to allow list](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png) + {%- elsif ghae %} + ![Add actions to allow list](/assets/images/enterprise/github-ae/enterprise-actions-policy-allow-list.png) + {%- endif %} +{% endif %} + +{% ifversion ghes > 2.22 or ghae %} +## Enabling workflows for private repository forks + +{% data reusables.github-actions.private-repository-forks-overview %} + +### Configuring the private fork policy for your enterprise + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.actions-tab %} +{% data reusables.github-actions.private-repository-forks-configure %} +{% endif %} diff --git a/translations/ko-KR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md b/translations/ko-KR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md index b3b2b33e67..968c06b782 100644 --- a/translations/ko-KR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md +++ b/translations/ko-KR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md @@ -34,7 +34,7 @@ topics: - Enterprise - Policies - Security -shortTitle: Enforce repository policies +shortTitle: Repository management policies --- ## Configuring the default visibility of new repositories in your enterprise diff --git a/translations/ko-KR/content/admin/policies/enforcing-policies-for-your-enterprise/index.md b/translations/ko-KR/content/admin/policies/enforcing-policies-for-your-enterprise/index.md index 73c67d0923..f4cdf81f00 100644 --- a/translations/ko-KR/content/admin/policies/enforcing-policies-for-your-enterprise/index.md +++ b/translations/ko-KR/content/admin/policies/enforcing-policies-for-your-enterprise/index.md @@ -11,6 +11,7 @@ topics: children: - /enforcing-repository-management-policies-in-your-enterprise - /restricting-email-notifications-for-your-enterprise + - /enforcing-github-actions-policies-for-your-enterprise - /enforcing-policies-for-advanced-security-in-your-enterprise shortTitle: Enforce policies --- diff --git a/translations/ko-KR/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md b/translations/ko-KR/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md index 0f948aa7a7..2e0d06b567 100644 --- a/translations/ko-KR/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md +++ b/translations/ko-KR/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md @@ -30,6 +30,9 @@ If you can't access {% data variables.product.product_name %}, contact your loca {% data reusables.saml.dotcom-saml-explanation %} Organization owners can invite your user account on {% data variables.product.prodname_dotcom %} to join their organization that uses SAML SSO, which allows you to contribute to the organization and retain your existing identity and contributions on {% data variables.product.prodname_dotcom %}. +If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you will use a new account that is provisioned for you. {% data reusables.enterprise-accounts.emu-more-info-account %} + + When you access resources within an organization that uses SAML SSO, {% data variables.product.prodname_dotcom %} will redirect you to the organization's SAML IdP to authenticate. After you successfully authenticate with your account on the IdP, the IdP redirects you back to {% data variables.product.prodname_dotcom %}, where you can access the organization's resources. {% data reusables.saml.outside-collaborators-exemption %} diff --git a/translations/ko-KR/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md b/translations/ko-KR/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md index 8b7968af61..230456d327 100644 --- a/translations/ko-KR/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md +++ b/translations/ko-KR/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md @@ -20,7 +20,7 @@ shortTitle: Generate new SSH key If you don't already have an SSH key, you must generate a new SSH key to use for authentication. If you're unsure whether you already have an SSH key, you can check for existing keys. For more information, see "[Checking for existing SSH keys](/github/authenticating-to-github/checking-for-existing-ssh-keys)." -{% ifversion fpt %} +{% ifversion fpt or ghae-next or ghes > 3.1 %} If you want to use a hardware security key to authenticate to {% data variables.product.product_name %}, you must generate a new SSH key for your hardware security key. You must connect your hardware security key to your computer when you authenticate with the key pair. For more information, see the [OpenSSH 8.2 release notes](https://www.openssh.com/txt/release-8.2). @@ -31,6 +31,12 @@ If you don't want to reenter your passphrase every time you use your SSH key, yo {% data reusables.command_line.open_the_multi_os_terminal %} 2. Paste the text below, substituting in your {% data variables.product.product_name %} email address. + {% ifversion ghae %} + + ```shell + $ ssh-keygen -t rsa -b 4096 -C "your_email@example.com" + ``` + {% else %} ```shell $ ssh-keygen -t ed25519 -C "your_email@example.com" ``` @@ -38,20 +44,22 @@ If you don't want to reenter your passphrase every time you use your SSH key, yo **Note:** If you are using a legacy system that doesn't support the Ed25519 algorithm, use: ```shell - $ ssh-keygen -t rsa -b 4096 -C "your_email@example.com" + $ ssh-keygen -t rsa -b 4096 -C "your_email@example.com" ``` {% endnote %} + {% endif %} + This creates a new SSH key, using the provided email as a label. ```shell - > Generating public/private ed25519 key pair. + > Generating public/private algorithm key pair. ``` 3. When you're prompted to "Enter a file in which to save the key," press Enter. This accepts the default file location. {% mac %} ```shell - > Enter a file in which to save the key (/Users/you/.ssh/id_ed25519): [Press enter] + > Enter a file in which to save the key (/Users/you/.ssh/id_algorithm): [Press enter] ``` {% endmac %} @@ -59,7 +67,7 @@ If you don't want to reenter your passphrase every time you use your SSH key, yo {% windows %} ```shell - > Enter a file in which to save the key (/c/Users/you/.ssh/id_ed25519):[Press enter] + > Enter a file in which to save the key (/c/Users/you/.ssh/id_algorithm):[Press enter] ``` {% endwindows %} @@ -67,7 +75,7 @@ If you don't want to reenter your passphrase every time you use your SSH key, yo {% linux %} ```shell - > Enter a file in which to save the key (/home/you/.ssh/id_ed25519): [Press enter] + > Enter a file in which to save the key (/home/you/.ssh/algorithm): [Press enter] ``` {% endlinux %} @@ -107,7 +115,7 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav Host * AddKeysToAgent yes UseKeychain yes - IdentityFile ~/.ssh/id_ed25519 + IdentityFile ~/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %} ``` {% note %} @@ -137,7 +145,7 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav 3. Add your SSH private key to the ssh-agent and store your passphrase in the keychain. {% data reusables.ssh.add-ssh-key-to-ssh-agent %} ```shell - $ ssh-add -K ~/.ssh/id_ed25519 + $ ssh-add -K ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %} ``` {% note %} @@ -189,8 +197,10 @@ If you are using macOS or Linux, you may need to update your SSH client or insta {% data reusables.command_line.open_the_multi_os_terminal %} 3. Paste the text below, substituting in the email address for your account on {% data variables.product.product_name %}. ```shell - $ ssh-keygen -t ed25519-sk -C "your_email@example.com" + $ ssh-keygen -t {% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}-sk -C "your_email@example.com" ``` + + {% ifversion not ghae %} {% note %} **Note:** If the command fails and you receive the error `invalid format` or `feature not supported,` you may be using a hardware security key that does not support the Ed25519 algorithm. Enter the following command instead. @@ -199,13 +209,14 @@ If you are using macOS or Linux, you may need to update your SSH client or insta ``` {% endnote %} + {% endif %} 4. When you are prompted, touch the button on your hardware security key. 5. When you are prompted to "Enter a file in which to save the key," press Enter to accept the default file location. {% mac %} ```shell - > Enter a file in which to save the key (/Users/you/.ssh/id_ed25519_sk): [Press enter] + > Enter a file in which to save the key (/Users/you/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): [Press enter] ``` {% endmac %} @@ -213,7 +224,7 @@ If you are using macOS or Linux, you may need to update your SSH client or insta {% windows %} ```shell - > Enter a file in which to save the key (/c/Users/you/.ssh/id_ed25519_sk):[Press enter] + > Enter a file in which to save the key (/c/Users/you/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk):[Press enter] ``` {% endwindows %} @@ -221,7 +232,7 @@ If you are using macOS or Linux, you may need to update your SSH client or insta {% linux %} ```shell - > Enter a file in which to save the key (/home/you/.ssh/id_ed25519_sk): [Press enter] + > Enter a file in which to save the key (/home/you/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): [Press enter] ``` {% endlinux %} diff --git a/translations/ko-KR/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md b/translations/ko-KR/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md index c31e03d8e9..39da9dc9cd 100644 --- a/translations/ko-KR/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md +++ b/translations/ko-KR/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md @@ -28,6 +28,10 @@ You can access your resources in {% data variables.product.product_name %} in a 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 fpt %} +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](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users#authenticating-as-a-managed-user)". If you're not a member of an {% data variables.product.prodname_emu_enterprise %}, you will authenticate using your browser on {% data variables.product.prodname_dotcom_the_website %}. +{% endif %} + - **Username and password only** - You'll create a password when you create your user 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)." - **Two-factor authentication (2FA)** (recommended) diff --git a/translations/ko-KR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md b/translations/ko-KR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md index 99dd2bc8ff..26e18e037a 100644 --- a/translations/ko-KR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md +++ b/translations/ko-KR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md @@ -38,7 +38,7 @@ A token with no assigned scopes can only access public information. To use your {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.developer_settings %} {% data reusables.user_settings.personal_access_tokens %} -4. Click **Generate new token**. ![Generate new token button](/assets/images/help/settings/generate_new_token.png) +{% 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 %} 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**. diff --git a/translations/ko-KR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md b/translations/ko-KR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md index c8cdc1d4ea..02c1db35eb 100644 --- a/translations/ko-KR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md +++ b/translations/ko-KR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md @@ -75,33 +75,6 @@ You can use a fallback number regardless of whether you've configured authentica After setup, the backup device will receive a confirmation SMS. -## Adding a fallback authentication method with Recover Accounts Elsewhere - -You can generate an extra authentication credential for your account and store it with a partner recovery provider. - -### About Recover Accounts Elsewhere - -With Recover Accounts Elsewhere, you can add an extra security factor to your {% data variables.product.product_name %} account in case you lose access to your two-factor authentication method or recovery codes. - -Recover Accounts Elsewhere lets you associate your {% data variables.product.product_name %} account with your Facebook account. You can store an authentication credential in the form of an _account recovery token_ for your {% data variables.product.product_name %} account with Facebook. - -If you lose access to your {% data variables.product.product_name %} account because you no longer have access to your two-factor authentication method or recovery codes, you can retrieve your account recovery token from the recovery provider to help prove that you're the owner of your {% data variables.product.product_name %} account. - -After you retrieve your token, {% data variables.contact.contact_support %} may be able to disable two-factor authentication for your account. Then, you can provide or reset your password to regain access to your account. - -When you generate or retrieve an account recovery token, an event is added to your account's audit log. For more information, see "[Reviewing your security log](/articles/reviewing-your-security-log)." - -### Generating and storing an account recovery token - -You can generate an account recovery token and store it with a partner recovery provider. - -1. Sign in to your Facebook account, then return to {% data variables.product.product_name %}. -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.security %} -4. To generate a new token, under "Recovery tokens," click **Store new token**. ![Button for storing a new recovery token](/assets/images/help/settings/store-new-recovery-token.png) -5. Read the information about account recovery tokens, then click **Connect with https://www.facebook.com**. ![Button for connecting a recovery token with Facebook](/assets/images/help/settings/connect-recovery-token-with-facebook.png) -6. After you're redirected to Facebook, read the information about turning on account recovery with Facebook before you click **Save as [_YOUR NAME_]**. (If you save multiple tokens within a short period of time, Facebook may skip this confirmation step after you save your first token.) ![Facebook page with button for turning on account recovery](/assets/images/help/settings/security-turn-on-rae-facebook.png) - {% endif %} ## 더 읽을거리 diff --git a/translations/ko-KR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md b/translations/ko-KR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md index 44ee33b46f..fff15e65a7 100644 --- a/translations/ko-KR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md +++ b/translations/ko-KR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md @@ -28,6 +28,12 @@ We strongly recommend using a time-based one-time password (TOTP) application to {% endwarning %} +{% ifversion fpt %} + +If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you cannot configure 2FA for your {% data variables.product.prodname_managed_user %} account. 2FA should be configured through your identity provider. + +{% endif %} + ## Configuring two-factor authentication using a TOTP mobile app A time-based one-time password (TOTP) application automatically generates an authentication code that changes after a certain period of time. We recommend using cloud-based TOTP apps such as: diff --git a/translations/ko-KR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md b/translations/ko-KR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md index bf8f2ed2c7..9aa457e27e 100644 --- a/translations/ko-KR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md +++ b/translations/ko-KR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md @@ -71,6 +71,12 @@ You can use your two-factor authentication credentials or two-factor authenticat ## Authenticating with an account recovery token +{% warning %} + +**Warning:** Account recovery tokens are deprecated and will be disabled on **December 1st, 2021**. Please ensure you have configured other two-factor recovery methods. For more information, see "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)." + +{% endwarning %} + If you lose access to the two-factor authentication methods for your {% data variables.product.product_name %} account, you can retrieve your account recovery token from a partner recovery provider and ask {% data variables.product.prodname_dotcom %} Support to review it. If you don't have access to your two-factor authentication methods or recovery codes and you've stored an account recovery token with Facebook using Recover Accounts Elsewhere, you may be able to use your token to regain access to your account. diff --git a/translations/ko-KR/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md b/translations/ko-KR/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md index 63123794ff..b2d23ea724 100644 --- a/translations/ko-KR/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md +++ b/translations/ko-KR/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md @@ -68,6 +68,8 @@ The number of jobs you can run concurrently across all repositories in your user ## Calculating minute and storage spending +{% data reusables.dotcom_billing.pricing_cal %} + At the end of the month, {% data variables.product.prodname_dotcom %} calculates the cost of minutes and storage used over the amount included in your account. ### Sample minutes cost calculation diff --git a/translations/ko-KR/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md b/translations/ko-KR/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md index a256b5296d..24606df3e9 100644 --- a/translations/ko-KR/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md +++ b/translations/ko-KR/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md @@ -28,6 +28,8 @@ Your {% data variables.product.prodname_codespaces %} usage shares your account' 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 {% data variables.product.prodname_codespaces %} usage. For more information, see "[Connecting an Azure subscription to your enterprise](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)." +{% data reusables.dotcom_billing.pricing_cal %} + ## Setting a spending limit {% data reusables.codespaces.codespaces-spending-limit-requirement %} diff --git a/translations/ko-KR/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md b/translations/ko-KR/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md index 5f030f316c..49486b72c9 100644 --- a/translations/ko-KR/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md +++ b/translations/ko-KR/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md @@ -49,7 +49,7 @@ Storage usage is shared with build artifacts produced by {% data variables.produ {% 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. -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.25 USD per GB or $37 USD. The overage for data transfer would cost $0.50 USD per GB or $20 USD. {% data reusables.dotcom_billing.pricing_cal %} At the end of the month, {% data variables.product.prodname_dotcom %} rounds your data transfer to the nearest GB. diff --git a/translations/ko-KR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md b/translations/ko-KR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md index ab08469e6d..3a0d0b47cb 100644 --- a/translations/ko-KR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md +++ b/translations/ko-KR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md @@ -68,11 +68,9 @@ 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)." -{% note %} - -**Note**: If you want {% data variables.product.prodname_code_scanning %} alerts to appear as pull request checks, you must use the `pull_request` event, described below. - -{% endnote %} +{% ifversion fpt or ghes > 3.2 or ghae-issue-5093 %} +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 %} ### Scanning pull requests @@ -82,6 +80,10 @@ For more information about the `pull_request` event, see "[Workflow syntax for { 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 %} + 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 %} + {% ifversion fpt or ghes > 3.1 or ghae-next %} ### Defining the severities causing pull request check failure @@ -234,7 +236,6 @@ Alternatively, you can install Python dependencies manually on any operating sys ```yaml jobs: CodeQL-Build: - runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae-next %} permissions: security-events: write @@ -266,7 +267,7 @@ jobs: ``` {% endif %} -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ## Configuring a category for the analysis Use `category` to distinguish between multiple analyses for the same tool and commit, but performed on different languages or different parts of the code. The category you specify in your workflow will be included in the SARIF results file. diff --git a/translations/ko-KR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md b/translations/ko-KR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md index 628f1d518c..b33c6b2174 100644 --- a/translations/ko-KR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/ko-KR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md @@ -48,9 +48,9 @@ When {% data variables.product.prodname_code_scanning %} reports data-flow alert Alert severity levels may be `Error`, `Warning`, or `Note`. -By default, any code scanning results with a severity of `error` will cause check failure. {% ifversion fpt or ghes > 3.1 or ghae-next %}You can specify the severity level at which pull requests that trigger code scanning alerts should fail. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %} +By default, any code scanning results with a severity of `error` will cause check failure. {% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %}You can specify the severity level at which pull requests that trigger code scanning alerts should fail. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %} +{% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %} ### About security severity levels {% data variables.product.prodname_code_scanning_capc %} displays security severity levels for alerts that are generated by security queries. Security severity levels can be `Critical`, `High`, `Medium`, or `Low`. @@ -70,10 +70,10 @@ By default, the code scanning alerts page is filtered to show alerts for the def {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-code-scanning-alerts %} -{% ifversion fpt or ghes > 3.1 %} -1. Optionally, use{% ifversion fpt or ghes > 3.1 %} the free text search box or{% endif %} the drop-down menus to filter alerts. For example, you can filter by the tool that was used to identify alerts. ![Filter by tool](/assets/images/help/repository/code-scanning-filter-by-tool.png){% endif %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} +1. Optionally, use the free text search box or the drop-down menus to filter alerts. For example, you can filter by the tool that was used to identify alerts. ![Filter by tool](/assets/images/help/repository/code-scanning-filter-by-tool.png){% endif %} 1. Under "{% data variables.product.prodname_code_scanning_capc %}," click the alert you'd like to explore. -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ![Summary of alerts](/assets/images/help/repository/code-scanning-click-alert.png) {% else %} ![List of alerts from {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) @@ -81,7 +81,7 @@ By default, the code scanning alerts page is filtered to show alerts for the def 1. Optionally, if the alert highlights a problem with data flow, click **Show paths** to display the path from the data source to the sink where it's used. ![The "Show paths" link on an alert](/assets/images/help/repository/code-scanning-show-paths.png) 1. Alerts from {% data variables.product.prodname_codeql %} analysis include a description of the problem. Click **Show more** for guidance on how to fix your code. ![Details for an alert](/assets/images/help/repository/code-scanning-alert-details.png) -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} {% note %} **Note:** For {% data variables.product.prodname_code_scanning %} analysis with {% data variables.product.prodname_codeql %}, you can see information about the latest run in a header at the top of the list of {% data variables.product.prodname_code_scanning %} alerts for the repository. @@ -91,7 +91,6 @@ For example, you can see when the last scan ran, the number of lines of code ana {% endnote %} {% endif %} - ## Filtering {% data variables.product.prodname_code_scanning %} alerts You can filter the alerts shown in the {% data variables.product.prodname_code_scanning %} alerts view. This is useful if there are many alerts as you can focus on a particular type of alert. There are some predefined filters and a range of keywords that you can use to refine the list of alerts displayed. @@ -105,7 +104,21 @@ You can filter the alerts shown in the {% data variables.product.prodname_code_s The benefit of using keyword filters is that only values with results are shown in the drop-down lists. This makes it easy to avoid setting filters that find no results. +If you enter multiple filters, the view will show alerts matching _all_ these filters. For example, `is:closed severity:high branch:main` will only display closed high-severity alerts that are present on the `main` branch. The exception is filters relating to refs (`ref`, `branch` and `pr`): `is:open branch:main branch:next` will show you open alerts from both the `main` branch and the `next` branch. + +### Restricting results to application code only + +You can use the "Only alerts in application code" filter or `autofilter:true` keyword and value to restrict results to alerts in application code. Application code excludes the following. + +- Code generated by the build process +- Test code +- Library or third-party code +- 문서 + +{% data variables.product.prodname_code_scanning_capc %} categorizes files by file path. At this time, you cannot manually categorize source files. + {% ifversion fpt or ghes > 3.1 %} + ## Searching {% data variables.product.prodname_code_scanning %} alerts You can search the list of alerts. This is useful if there is a large number of alerts in your repository, or if you don't know the exact name for an alert for example. {% data variables.product.product_name %} performs the free text search across: @@ -145,11 +158,11 @@ Anyone with write permission for a repository can fix an alert by committing a c If you have write permission for a repository, you can view fixed alerts by viewing the summary of alerts and clicking **Closed**. For more information, see "[Viewing the alerts for a repository](#viewing-the-alerts-for-a-repository)." The "Closed" list shows fixed alerts and alerts that users have dismissed. -You can use{% ifversion fpt or ghes > 3.1 %} the free text search or{% endif %} the filters to display a subset of alerts and then in turn mark all matching alerts as closed. +You can use{% ifversion fpt or ghes > 3.1 or ghae-next %} the free text search or{% endif %} the filters to display a subset of alerts and then in turn mark all matching alerts as closed. Alerts may be fixed in one branch but not in another. You can use the "Branch" drop-down menu, on the summary of alerts, to check whether an alert is fixed in a particular branch. -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ![Filtering alerts by branch](/assets/images/help/repository/code-scanning-branch-filter.png) {% else %} ![Filtering alerts by branch](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png) @@ -185,9 +198,9 @@ To dismiss or delete alerts: ![Deleting alerts](/assets/images/help/repository/code-scanning-delete-alerts.png) - Optionally, you can use{% ifversion fpt or ghes > 3.1 %} the free text search or{% endif %} the filters to display a subset of alerts and then delete all matching alerts at once. For example, if you have removed a query from {% data variables.product.prodname_codeql %} analysis, you can use the "Rule" filter to list just the alerts for that query and then select and delete all of those alerts. + Optionally, you can use{% ifversion fpt or ghes > 3.1 or ghae-next %} the free text search or{% endif %} the filters to display a subset of alerts and then delete all matching alerts at once. For example, if you have removed a query from {% data variables.product.prodname_codeql %} analysis, you can use the "Rule" filter to list just the alerts for that query and then select and delete all of those alerts. -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ![Filter alerts by rule](/assets/images/help/repository/code-scanning-filter-by-rule.png) {% else %} ![Filter alerts by rule](/assets/images/enterprise/3.1/help/repository/code-scanning-filter-by-rule.png) @@ -195,12 +208,11 @@ To dismiss or delete alerts: 1. If you want to dismiss an alert, it's important to explore the alert first, so that you can choose the correct dismissal reason. Click the alert you'd like to explore. -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ![Open an alert from the summary list](/assets/images/help/repository/code-scanning-click-alert.png) {% else %} ![List of alerts from {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) {% endif %} - 1. Review the alert, then click **Dismiss** and choose a reason for closing the alert. ![Choosing a reason for dismissing an alert](/assets/images/help/repository/code-scanning-alert-close-drop-down.png) {% data reusables.code-scanning.choose-alert-dismissal-reason %} diff --git a/translations/ko-KR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md b/translations/ko-KR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md index c070036f9d..186747a113 100644 --- a/translations/ko-KR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md +++ b/translations/ko-KR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md @@ -40,8 +40,8 @@ You decide how to generate {% data variables.product.prodname_code_scanning %} a {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} -3. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. {% ifversion fpt or ghes > 3.0 %}If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}. 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)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %} !["Set up {% data variables.product.prodname_code_scanning %}" button to the right of "{% data variables.product.prodname_code_scanning_capc %}" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png) -4. Under "Get started with {% data variables.product.prodname_code_scanning %}", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png){% ifversion fpt or ghes > 2.22 %}Workflows are only displayed if they are relevant for the programming languages detected in the repository. The {% data variables.product.prodname_codeql_workflow %} is always displayed, but the "Set up this workflow" button is only enabled if {% data variables.product.prodname_codeql %} analysis supports the languages present in the repository.{% endif %} +3. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. {% ifversion fpt or ghes > 3.0 or ghae-next %}If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}. 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)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %} !["Set up {% data variables.product.prodname_code_scanning %}" button to the right of "{% data variables.product.prodname_code_scanning_capc %}" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png) +4. Under "Get started with {% data variables.product.prodname_code_scanning %}", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png){% ifversion fpt or ghes > 2.22 or ghae-next %}Workflows are only displayed if they are relevant for the programming languages detected in the repository. The {% data variables.product.prodname_codeql_workflow %} is always displayed, but the "Set up this workflow" button is only enabled if {% data variables.product.prodname_codeql %} analysis supports the languages present in the repository.{% endif %} 5. To customize how {% data variables.product.prodname_code_scanning %} scans your code, edit the workflow. Generally you can commit the {% data variables.product.prodname_codeql_workflow %} without making any changes to it. However, many of the third-party workflows require additional configuration, so read the comments in the workflow before committing. @@ -53,10 +53,43 @@ You decide how to generate {% data variables.product.prodname_code_scanning %} a In the default {% data variables.product.prodname_codeql_workflow %}, {% data variables.product.prodname_code_scanning %} is configured to analyze your code each time you either push a change to the default branch or any protected branches, or raise a pull request against the default branch. As a result, {% data variables.product.prodname_code_scanning %} will now commence. +The `on:pull_request` and `on:push` triggers for code scanning are each useful for different purposes. For more information, see "[Scanning pull requests](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-pull-requests)" and "[Scanning on push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)." ## Bulk set up of {% data variables.product.prodname_code_scanning %} You can set up {% data variables.product.prodname_code_scanning %} in many repositories at once using a script. If you'd like to use a script to raise pull requests that add a {% data variables.product.prodname_actions %} workflow to multiple repositories, see the [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) repository for an example using Powershell, or [`nickliffen/ghas-enablement`](https://github.com/NickLiffen/ghas-enablement) for teams who do not have Powershell and instead would like to use NodeJS. +## Viewing the logging output from {% data variables.product.prodname_code_scanning %} + +After setting up {% data variables.product.prodname_code_scanning %} for your repository, you can watch the output of the actions as they run. + +{% data reusables.repositories.actions-tab %} + + You'll see a list that includes an entry for running the {% data variables.product.prodname_code_scanning %} workflow. The text of the entry is the title you gave your commit message. + + ![Actions list showing {% data variables.product.prodname_code_scanning %} workflow](/assets/images/help/repository/code-scanning-actions-list.png) + +1. Click the entry for the {% data variables.product.prodname_code_scanning %} workflow. + +1. Click the job name on the left. For example, **Analyze (LANGUAGE)**. + + ![Log output from the {% data variables.product.prodname_code_scanning %} workflow](/assets/images/help/repository/code-scanning-logging-analyze-action.png) + +1. Review the logging output from the actions in this workflow as they run. + +1. Once all jobs are complete, you can view the details of any {% data variables.product.prodname_code_scanning %} alerts that were identified. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)." + +{% note %} + +**Note:** If you raised a pull request to add the {% data variables.product.prodname_code_scanning %} workflow to the repository, alerts from that pull request aren't displayed directly on the {% data variables.product.prodname_code_scanning_capc %} page until the pull request is merged. If any alerts were found you can view these, before the pull request is merged, by clicking the **_n_ alerts found** link in the banner on the {% data variables.product.prodname_code_scanning_capc %} page. + +{% ifversion fpt or ghes > 3.1 or ghae-next %} + ![Click the "n alerts found" link](/assets/images/help/repository/code-scanning-alerts-found-link.png) +{% else %} + ![Click the "n alerts found" link](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png) +{% endif %} + +{% endnote %} + ## Understanding the pull request checks Each {% data variables.product.prodname_code_scanning %} workflow you set to run on pull requests always has at least two entries listed in the checks section of a pull request. There is one entry for each of the analysis jobs in the workflow, and a final one for the results of the analysis. @@ -65,13 +98,25 @@ 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 a "Missing analysis" 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-issue-3891 %}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. - ![Missing analysis for commit message](/assets/images/help/repository/code-scanning-missing-analysis.png) +{% ifversion fpt or ghes > 3.2 or ghae-issue-3891 %} + ![Analysis not found for commit message](/assets/images/help/repository/code-scanning-analysis-not-found.png) -### Reasons for the "missing analysis" message +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. -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 "Missing analysis for base commit SHA-HASH" message. +For example, in the screenshot above, {% data variables.product.prodname_code_scanning %} found an analysis for the merge commit of the pull request, but no analysis for the head of the main branch. +{% else %} + ![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 %} +### 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 %}"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: @@ -79,7 +124,7 @@ There are other situations where there may be no analysis for the latest commit To check whether a branch has been scanned, go to the {% data variables.product.prodname_code_scanning_capc %} page, click the **Branch** drop-down and select the relevant branch. -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ![Choose a branch from the Branch drop-down menu](/assets/images/help/repository/code-scanning-branch-dropdown.png) {% else %} ![Choose a branch from the Branch drop-down menu](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-dropdown.png) diff --git a/translations/ko-KR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md b/translations/ko-KR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md index 14699ad149..7ccc224129 100644 --- a/translations/ko-KR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md +++ b/translations/ko-KR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md @@ -28,6 +28,9 @@ 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 %} +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 %} If your pull request targets a protected branch that uses {% data variables.product.prodname_code_scanning %}, and the repository owner has configured required status checks, then the "{% data variables.product.prodname_code_scanning_capc %} results" check must pass before you can merge the pull request. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)." diff --git a/translations/ko-KR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md b/translations/ko-KR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md index 191862e2cc..ae36c9908f 100644 --- a/translations/ko-KR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md +++ b/translations/ko-KR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md @@ -22,7 +22,7 @@ shortTitle: View code scanning logs You can use a variety of tools to set up {% data variables.product.prodname_code_scanning %} in your repository. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#options-for-setting-up-code-scanning)." -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} The log and diagnostic information available to you depends on the method you use for {% data variables.product.prodname_code_scanning %} in your repository. You can check the type of {% data variables.product.prodname_code_scanning %} you're using in the **Security** tab of your repository, by using the **Tool** drop-down menu in the alert list. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)." ## About analysis and diagnostic information @@ -35,7 +35,7 @@ You can see analysis and diagnostic information for {% data variables.product.pr If you're using the {% data variables.product.prodname_codeql_cli %} outside {% data variables.product.prodname_dotcom %}, you'll see diagnostic information in the output generated during database analysis. This information is also included in the SARIF results file you upload to {% data variables.product.prodname_dotcom %} with the {% data variables.product.prodname_code_scanning %} results. -For information about the {% data variables.product.prodname_codeql_cli %}, see "[Running {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-cli-in-your-ci-system#viewing-log-and-diagnostic-information)." +For information about the {% data variables.product.prodname_codeql_cli %}, see "[Configuring {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system#viewing-log-and-diagnostic-information)." ### About summary metrics @@ -72,7 +72,7 @@ After setting up {% data variables.product.prodname_code_scanning %} for your re **Note:** If you raised a pull request to add the {% data variables.product.prodname_code_scanning %} workflow to the repository, alerts from that pull request aren't displayed directly on the {% data variables.product.prodname_code_scanning_capc %} page until the pull request is merged. If any alerts were found you can view these, before the pull request is merged, by clicking the **_n_ alerts found** link in the banner on the {% data variables.product.prodname_code_scanning_capc %} page. -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae %} ![Click the "n alerts found" link](/assets/images/help/repository/code-scanning-alerts-found-link.png) {% else %} ![Click the "n alerts found" link](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png) diff --git a/translations/ko-KR/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md b/translations/ko-KR/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md index 27656ede23..30ba718238 100644 --- a/translations/ko-KR/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md +++ b/translations/ko-KR/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md @@ -37,7 +37,7 @@ If you're using {% data variables.product.prodname_actions %} with the {% data v {% ifversion fpt or ghes > 3.0 or ghae-next %} If you're using the {% data variables.product.prodname_codeql_cli %}, then you can specify the version of SARIF to use. For more information, see "[Configuring {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system#analyzing-a-codeql-database)."{% endif %} -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} You can upload multiple SARIF files for the same tool and commit, and analyze each file using {% data variables.product.prodname_code_scanning %}. You can indicate a "category" for each analysis by specifying a `runAutomationDetails.id` in each file. Only SARIF files with the same category will overwrite each other. For more information about this property, see [`runAutomationDetails` object](#runautomationdetails-object) below. {% endif %} @@ -141,7 +141,7 @@ A location within a programming artifact, such as a file in the repository or a | `region.endLine` | **Required.** The line number of the last character in the region. | | `region.endColumn` | **Required.** The column number of the character following the end of the region. | -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ### `runAutomationDetails` object The `runAutomationDetails` object contains information that specifies the identity of a run. @@ -245,7 +245,7 @@ This SARIF output file has example values to show the minimum required propertie This SARIF output file has example values to show all supported SARIF properties for {% data variables.product.prodname_code_scanning %}. -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ```json { "$schema": "https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json", diff --git a/translations/ko-KR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md b/translations/ko-KR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md index 347d7d8e0e..bf69c24193 100644 --- a/translations/ko-KR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md +++ b/translations/ko-KR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md @@ -91,8 +91,8 @@ For more information, see "[Running {% data variables.product.prodname_codeql_ru {% endif %} - -{% ifversion ghes = 3.0 or ghae %} + +{% ifversion ghes = 3.0 %} {% data reusables.code-scanning.upload-sarif-ghas %} You add the {% data variables.product.prodname_codeql_runner %} to your third-party system, then call the tool to analyze code and upload the SARIF results to {% data variables.product.product_name %}. The resulting {% data variables.product.prodname_code_scanning %} alerts are shown alongside any alerts generated within {% data variables.product.product_name %}. diff --git a/translations/ko-KR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md b/translations/ko-KR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md index 6c56cc98b5..91f603bfc6 100644 --- a/translations/ko-KR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md +++ b/translations/ko-KR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md @@ -30,7 +30,7 @@ Once you've made the {% data variables.product.prodname_codeql_cli %} available You use three different commands to generate results and upload them to {% data variables.product.product_name %}: -{% ifversion fpt or ghes > 3.1 or ghae-next %} +{% ifversion fpt or ghes > 3.1 or ghae %} 1. `database create` to create a {% data variables.product.prodname_codeql %} database to represent the hierarchical structure of each supported programming language in the repository. 2. `database analyze` to run queries to analyze each {% data variables.product.prodname_codeql %} database and summarize the results in a SARIF file. @@ -50,11 +50,11 @@ You can display the command-line help for any command using the `--help` 3.1 or ghae-next %} + {% ifversion fpt or ghes > 3.1 or ghae %} ```shell # Single supported language - create one CodeQL databsae codeql database create <database> --command<build> --language=<language-identifier> @@ -119,7 +119,7 @@ You can display the command-line help for any command using the `--help`     		- {% ifversion fpt or ghes > 3.1 or ghae-next %}When used with `--db-cluster`, the option accepts a comma-separated list, or can be specified more than once.{% endif %} + {% ifversion fpt or ghes > 3.1 or ghae %}When used with `--db-cluster`, the option accepts a comma-separated list, or can be specified more than once.{% endif %} @@ -144,7 +144,7 @@ You can display the command-line help for any command using the `--help` - {% ifversion fpt or ghes > 3.1 or ghae-next %} + {% ifversion fpt or ghes > 3.1 or ghae %} @@ -208,7 +208,7 @@ You can display the command-line help for any command using the `--help` 3.1 or ghae-next %}Single language example{% else %}Basic example{% endif %} +### {% ifversion fpt or ghes > 3.1 or ghae %}Single language example{% else %}Basic example{% endif %} This example creates a {% data variables.product.prodname_codeql %} database for the repository checked out at `/checkouts/example-repo`. It uses the JavaScript extractor to create a hierarchical representation of the JavaScript and TypeScript code in the repository. The resulting database is stored in `/codeql-dbs/example-repo`. @@ -226,7 +226,7 @@ $ codeql database create /codeql-dbs/example-repo --language=javascript \ > Successfully created database at /codeql-dbs/example-repo. ``` -{% ifversion fpt or ghes > 3.1 or ghae-next %} +{% ifversion fpt or ghes > 3.1 or ghae %} ### Multiple language example This example creates two {% data variables.product.prodname_codeql %} databases for the repository checked out at `/checkouts/example-repo-multi`. It uses: @@ -273,7 +273,7 @@ $ --output=<output> {% if codeql-packs %}<packs,queries>{% else %} <queries>{% endif %} ``` -{% ifversion fpt or ghes > 3.1 or ghae-next %} +{% ifversion fpt or ghes > 3.1 or ghae %} {% note %} **Note:** If you analyze more than one {% data variables.product.prodname_codeql %} database for a single commit, you must specify a SARIF category for each set of results generated by this command. When you upload the results to {% data variables.product.product_name %}, {% data variables.product.prodname_code_scanning %} uses this category to store the results for each language separately. If you forget to do this, each upload overwrites the previous results. @@ -317,15 +317,14 @@ codeql database analyze <database> --format=<format> \
    - <queries> + <packs,queries> - {% octicon "check-circle-fill" aria-label="Required" %} - Specify the queries to run. To run the standard queries used for {% data variables.product.prodname_code_scanning %}, use: <language>-code-scanning.qls where <language> is the short code for the language of the database. To see the other query suites included in the {% data variables.product.prodname_codeql_cli %} bundle, look in /<extraction-root>/codeql/qlpacks/codeql-<language>/codeql-suites. For information about creating your own query suite, see Creating CodeQL query suites in the documentation for the {% data variables.product.prodname_codeql_cli %}. + Specify {% data variables.product.prodname_codeql %} packs or queries to run. To run the standard queries used for {% data variables.product.prodname_code_scanning %}, omit this parameter. To see the other query suites included in the {% data variables.product.prodname_codeql_cli %} bundle, look in /<extraction-root>/codeql/qlpacks/codeql-<language>/codeql-suites. For information about creating your own query suite, see Creating CodeQL query suites in the documentation for the {% data variables.product.prodname_codeql_cli %}.
    - Specify where to save the SARIF results file.{% ifversion fpt or ghes > 3.1 or ghae-next %} + Specify where to save the SARIF results file.{% ifversion fpt or ghes > 3.1 or ghae %}
    - 선택 사항. Use to get more detailed information about the analysis process{% ifversion fpt or ghes > 3.1 or ghae-next %} and diagnostic data from the database creation process{% endif %}. + 선택 사항. Use to get more detailed information about the analysis process{% ifversion fpt or ghes > 3.1 or ghae %} and diagnostic data from the database creation process{% endif %}.
    @@ -415,11 +414,11 @@ For more information, see [Analyzing databases with the {% data variables.produc ### Basic example -This example analyzes a {% data variables.product.prodname_codeql %} database stored at `/codeql-dbs/example-repo` and saves the results as a SARIF file: `/temp/example-repo-js.sarif`. {% ifversion fpt or ghes > 3.1 or ghae-next %}It uses `--sarif-category` to include extra information in the SARIF file that identifies the results as JavaScript. This is essential when you have more than one {% data variables.product.prodname_codeql %} database to analyze for a single commit in a repository.{% endif %} +This example analyzes a {% data variables.product.prodname_codeql %} database stored at `/codeql-dbs/example-repo` and saves the results as a SARIF file: `/temp/example-repo-js.sarif`. {% ifversion fpt or ghes > 3.1 or ghae %}It uses `--sarif-category` to include extra information in the SARIF file that identifies the results as JavaScript. This is essential when you have more than one {% data variables.product.prodname_codeql %} database to analyze for a single commit in a repository.{% endif %} ``` $ codeql database analyze /codeql-dbs/example-repo \ - javascript-code-scanning.qls {% ifversion fpt or ghes > 3.1 or ghae-next %}--sarif-category=javascript{% endif %} + javascript-code-scanning.qls {% ifversion fpt or ghes > 3.1 or ghae %}--sarif-category=javascript{% endif %} --format={% ifversion fpt or ghae %}sarif-latest{% else %}sarifv2.1.0{% endif %} --output=/temp/example-repo-js.sarif > Running queries. @@ -444,7 +443,7 @@ When you have decided on the most secure and reliable method for your CI server, ```shell echo "$UPLOAD_TOKEN" | codeql github upload-results --repository=<repository-name> \ --ref=<ref> --commit=<commit> --sarif=<file> \ - {% ifversion ghes > 3.0 or ghae-next %}--github-url=<URL> {% endif %}--github-auth-stdin + {% ifversion ghes > 3.0 or ghae %}--github-url=<URL> {% endif %}--github-auth-stdin ``` @@ -486,7 +485,7 @@ When you have decided on the most secure and reliable method for your CI server, @@ -514,7 +513,7 @@ When you have decided on the most secure and reliable method for your CI server, @@ -555,7 +554,7 @@ This example uploads results from the SARIF file `temp/example-repo-js.sarif` to ``` $ echo $UPLOAD_TOKEN | codeql github upload-results --repository=my-org/example-repo \ --ref=refs/heads/main --commit=deb275d2d5fe9a522a0b7bd8b6b6a1c939552718 \ - --sarif=/temp/example-repo-js.sarif {% ifversion ghes > 3.0 or ghae-next %}--github-url={% data variables.command_line.git_url_example %} \ + --sarif=/temp/example-repo-js.sarif {% ifversion ghes > 3.0 or ghae %}--github-url={% data variables.command_line.git_url_example %} \ {% endif %}--github-auth-stdin ``` @@ -641,6 +640,7 @@ $ codeql database analyze /codeql-dbs/example-repo octo-org/security-queries \ {% endif %} {% ifversion fpt or ghes > 3.1 or ghae-next %} + ## Example CI configuration for {% data variables.product.prodname_codeql %} analysis This is an example of the series of commands that you might use to analyze a codebase with two supported languages and then upload the results to {% data variables.product.product_name %}. diff --git a/translations/ko-KR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md b/translations/ko-KR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md index 35fee2f3e3..9f862ce95a 100644 --- a/translations/ko-KR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md +++ b/translations/ko-KR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md @@ -190,7 +190,7 @@ Analyzes the code in the {% data variables.product.prodname_codeql %} databases | `--no-upload` | | None. Stops the {% data variables.product.prodname_codeql_runner %} from uploading the results to {% data variables.product.product_name %}. | | `--output-dir` | | Directory where the output SARIF files are stored. The default is in the directory of temporary files. | | `--ram` | | Amount of memory to use when running queries. The default is to use all available memory. | -| `--no-add-snippets` | | None. Excludes code snippets from the SARIF output. |{% ifversion fpt or ghes > 3.1 %} +| `--no-add-snippets` | | None. Excludes code snippets from the SARIF output. |{% ifversion fpt or ghes > 3.1 or ghae %} | `--category` | | Category to include in the SARIF results file for this analysis. A category can be used to distinguish multiple analyses for the same tool and commit, but performed on different languages or different parts of the code. This value will appear in the `.automationDetails.id` property in SARIF v2.1.0. {% endif %} | `--threads` | | Number of threads to use when running queries. The default is to use all available cores. | diff --git a/translations/ko-KR/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md b/translations/ko-KR/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md index 46ec04b016..b9fbfa6ec3 100644 --- a/translations/ko-KR/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md +++ b/translations/ko-KR/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md @@ -25,7 +25,7 @@ topics: {% data variables.product.company_short %} performs {% data variables.product.prodname_secret_scanning %} on {% ifversion fpt %}public and private{% endif %} repositories for secret patterns provided by {% data variables.product.company_short %} and {% data variables.product.company_short %} partners. For more information on the {% data variables.product.prodname_secret_scanning %} partner program, see "Secret scanning partner program." -However, there can be situations where you want to scan for other secret patterns in your {% ifversion fpt %}private{% endif %} repositories. For example, you might have a secret pattern that is internal to your organization. For these situations, you can define custom {% data variables.product.prodname_secret_scanning %} patterns in your enterprise, organization, or {% ifversion fpt %}private{% endif %} repository on {% data variables.product.product_name %}. You can define up to 20 custom patterns for each {% ifversion fpt %}private{% endif %} repository, organization, or enterprise account. +However, there can be situations where you want to scan for other secret patterns in your {% ifversion fpt %}private{% endif %} repositories. For example, you might have a secret pattern that is internal to your organization. For these situations, you can define custom {% data variables.product.prodname_secret_scanning %} patterns in your enterprise, organization, or {% ifversion fpt %}private{% endif %} repository on {% data variables.product.product_name %}. You can define up to 100 custom patterns for each organization or enterprise account, and up to 20 custom patterns per {% ifversion fpt %}private{% endif %} repository. {% ifversion ghes < 3.3 or ghae %} {% note %} diff --git a/translations/ko-KR/content/code-security/security-advisories/publishing-a-security-advisory.md b/translations/ko-KR/content/code-security/security-advisories/publishing-a-security-advisory.md index 5eaf38392c..9acc489a7a 100644 --- a/translations/ko-KR/content/code-security/security-advisories/publishing-a-security-advisory.md +++ b/translations/ko-KR/content/code-security/security-advisories/publishing-a-security-advisory.md @@ -61,19 +61,6 @@ After you publish a security advisory, the URL for the security advisory will re If you need to update or correct information in a security advisory that you've published, you can edit the security advisory. For more information, see "[Editing a security advisory](/github/managing-security-vulnerabilities/editing-a-security-advisory)." -## Requesting a CVE identification number - -Anyone with admin permissions to a security advisory can request a CVE identification number for the security advisory. - -{% data reusables.repositories.request-security-advisory-cve-id %} For more information, see "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories#cve-identification-numbers)." - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-security %} -{% data reusables.repositories.sidebar-advisories %} -4. In the "Security Advisories" list, click the security advisory you'd like to request a CVE identification number for. ![Security advisory in list](/assets/images/help/security/security-advisory-in-list.png) -5. Use the **Publish advisory** drop-down menu, and click **Request CVE**. ![Request CVE in drop-down](/assets/images/help/security/security-advisory-drop-down-request-cve.png) -6. Click **Request CVE**. ![Request CVE button](/assets/images/help/security/security-advisory-request-cve-button.png) - ## Publishing a security advisory Publishing a security advisory deletes the temporary private fork for the security advisory. @@ -88,6 +75,17 @@ Publishing a security advisory deletes the temporary private fork for the securi {% data reusables.repositories.github-reviews-security-advisories %} +## Requesting a CVE identification number (Optional) + +{% data reusables.repositories.request-security-advisory-cve-id %} For more information, see "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories#cve-identification-numbers)." + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-security %} +{% data reusables.repositories.sidebar-advisories %} +4. In the "Security Advisories" list, click the security advisory you'd like to request a CVE identification number for. ![Security advisory in list](/assets/images/help/security/security-advisory-in-list.png) +5. Use the **Publish advisory** drop-down menu, and click **Request CVE**. ![Request CVE in drop-down](/assets/images/help/security/security-advisory-drop-down-request-cve.png) +6. Click **Request CVE**. ![Request CVE button](/assets/images/help/security/security-advisory-request-cve-button.png) + ## 더 읽을거리 - "[Withdrawing a security advisory](/github/managing-security-vulnerabilities/withdrawing-a-security-advisory)" diff --git a/translations/ko-KR/content/code-security/security-overview/about-the-security-overview.md b/translations/ko-KR/content/code-security/security-overview/about-the-security-overview.md index 860b48234b..e3b04083a2 100644 --- a/translations/ko-KR/content/code-security/security-overview/about-the-security-overview.md +++ b/translations/ko-KR/content/code-security/security-overview/about-the-security-overview.md @@ -6,8 +6,8 @@ redirect_from: - /code-security/security-overview/exploring-security-alerts versions: fpt: '*' + ghae: issue-4554 ghes: '>3.1' - ghae: next type: how_to topics: - Security overview diff --git a/translations/ko-KR/content/code-security/security-overview/index.md b/translations/ko-KR/content/code-security/security-overview/index.md index 3adfe1802b..88ef0c8e5b 100644 --- a/translations/ko-KR/content/code-security/security-overview/index.md +++ b/translations/ko-KR/content/code-security/security-overview/index.md @@ -5,8 +5,8 @@ intro: 'View, sort, and filter the security alerts from across your organization product: '{% data reusables.gated-features.security-center %}' versions: fpt: '*' + ghae: issue-4554 ghes: '>3.1' - ghae: next topics: - Security overview - Advanced Security diff --git a/translations/ko-KR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md b/translations/ko-KR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md index 2088b810a5..ba0e0692cc 100644 --- a/translations/ko-KR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md +++ b/translations/ko-KR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md @@ -1,11 +1,11 @@ --- title: About dependency review intro: 'Dependency review lets you catch vulnerable dependencies before you introduce them to your environment, and provides information on license, dependents, and age of dependencies.' +product: '{% data reusables.gated-features.dependency-review %}' shortTitle: Dependency review versions: fpt: '*' ghes: '>= 3.2' - product: '{% data reusables.gated-features.dependency-review %}' type: overview topics: - Advanced Security diff --git a/translations/ko-KR/content/codespaces/developing-in-codespaces/index.md b/translations/ko-KR/content/codespaces/developing-in-codespaces/index.md index 14978ebfe8..12751acf49 100644 --- a/translations/ko-KR/content/codespaces/developing-in-codespaces/index.md +++ b/translations/ko-KR/content/codespaces/developing-in-codespaces/index.md @@ -15,6 +15,5 @@ children: - /forwarding-ports-in-your-codespace - /changing-the-machine-type-for-your-codespace - /using-codespaces-in-visual-studio-code - - /web-based-editor --- diff --git a/translations/ko-KR/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md b/translations/ko-KR/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md index 65c8f26777..d58c0f5f50 100644 --- a/translations/ko-KR/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md +++ b/translations/ko-KR/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md @@ -30,9 +30,7 @@ A typical workflow for updating a file using {% data variables.product.prodname_ ## Creating or switching branches -1. If the current branch is not shown in the status bar, at the bottom of your codespace, right-click the status bar and select **Source control**. -1. Click the branch name in the status bar. ![The branch in the status bar](/assets/images/help/codespaces/branch-in-status-bar.png) -1. In the drop-down, either click the branch you want to switch to, or enter the name for a new branch and click **Create new branch**. ![Choose from the branch menu](/assets/images/help/codespaces/create-new-branch.png) +{% data reusables.codespaces.create-or-switch-branch %} {% tip %} @@ -64,16 +62,11 @@ If the fetch operation detects new changes on the remote repository, you'll see ## Committing your changes -{% data reusables.codespaces.source-control-display-dark %} -1. To stage your changes, click **+** next to the file you've changed, or next to **Changes** if you've changed multiple files and you want to stage them all. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-stage.png) -1. Type a commit message describing the change you've made. ![Source control side bar with a commit message](/assets/images/help/codespaces/codespaces-commit-commit-message.png) -1. To commit your staged changes, click the check mark at the top the source control side bar. ![Click the check mark icon](/assets/images/help/codespaces/codespaces-commit-checkmark-icon.png) +{% data reusables.codespaces.source-control-commit-changes %} ## Raising a pull request -1. After you've committed changes to your local copy of the repository, click the **Create Pull Request** icon. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-pr-button.png) -1. Check that the local branch and repository you're merging from, and the remote branch and repository you're merging into, are correct. Then give the pull request a title and a description. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-pr.png) -1. Click **Create**. +{% data reusables.codespaces.source-control-pull-request %} ## Pushing changes to your remote repository diff --git a/translations/ko-KR/content/codespaces/index.md b/translations/ko-KR/content/codespaces/index.md index 06035cb35d..5c3572bab3 100644 --- a/translations/ko-KR/content/codespaces/index.md +++ b/translations/ko-KR/content/codespaces/index.md @@ -41,6 +41,7 @@ children: - /managing-codespaces-for-your-organization - /codespaces-reference - /troubleshooting + - /the-githubdev-web-based-editor - /guides --- diff --git a/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md b/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md index 8d3c4a9ee8..b92b37c6ef 100644 --- a/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md +++ b/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md @@ -72,3 +72,7 @@ You can check which access policies are applied to a secret in your organization {% data reusables.github-actions.sidebar-secret %} 1. The list of secrets includes any configured permissions and policies. 예시: ![Secrets list](/assets/images/help/settings/actions-org-secrets-list.png) 1. For more details on the configured permissions for each secret, click **Update**. + +## 더 읽을거리 + +- "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)" diff --git a/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md b/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md index 5674555da1..6a87e85096 100644 --- a/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md +++ b/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md @@ -26,3 +26,7 @@ To manage which users in your organization can use {% data variables.product.pro {% data reusables.organizations.click-codespaces %} 1. Under "Access and security", select the setting you want for your organization. ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-org-access-and-security-radio-buttons.png) 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 owned by your organization. Repeat for all repositories whose codespaces you want to access other repositories. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) + +## 더 읽을거리 + +- "[Managing repository access for your codespaces](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces)" diff --git a/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md b/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md index 860f8c42d6..3b660d07eb 100644 --- a/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md +++ b/translations/ko-KR/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md @@ -19,3 +19,7 @@ When any member of your organization performs an action related to {% data varia ![Audit log with Codespaces information](/assets/images/help/settings/codespaces-audit-log-org.png) The audit log includes details such as who performed the action, what the action was, and when the action was performed. For information on {% data variables.product.prodname_codespaces %} actions, see "[{% data variables.product.prodname_codespaces %} category actions](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#codespaces-category-actions)." + +## 더 읽을거리 + +- "[Reviewing your security logs for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces)" diff --git a/translations/ko-KR/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md b/translations/ko-KR/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md index c63591801a..aa2a2036bc 100644 --- a/translations/ko-KR/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md +++ b/translations/ko-KR/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md @@ -73,3 +73,7 @@ You can update the value of an existing secret, and you can change which reposit {% data reusables.user_settings.codespaces-tab %} 1. Under "Codespaces secrets", to the right of the secret you want to delete, click **Delete**. !["Delete" button](/assets/images/help/settings/codespaces-secret-delete-button.png) 1. Read the warning, then click **OK**. ![Confirmation to delete secret](/assets/images/help/settings/codespaces-secret-delete-warning.png) + +## 더 읽을거리 + +- "[Managing encrypted secrets for your repository and organization for {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces)" diff --git a/translations/ko-KR/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md b/translations/ko-KR/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md index 57753fbdaa..591a58c22d 100644 --- a/translations/ko-KR/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md +++ b/translations/ko-KR/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md @@ -29,6 +29,6 @@ Once you enable GPG verification, it will immediately take effect for all your c {% note %} -**Note:** Once you have enabled GPG verification for {% data variables.product.prodname_codespaces %}, you also must append `-s` to each commit in order for it to be signed. To do this in {% data variables.product.prodname_vscode %}, ensure the "Git: Enable Commit Signing" option is enabled from the Settings. +**Note:** Once you have enabled GPG verification for {% data variables.product.prodname_codespaces %}, you also must append `-S` to each commit in order for it to be signed. To do this in {% data variables.product.prodname_vscode %}, ensure the "Git: Enable Commit Signing" option is enabled from the Settings. {% endnote %} diff --git a/translations/ko-KR/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md b/translations/ko-KR/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md index d79c06de7f..10d6204f5e 100644 --- a/translations/ko-KR/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md +++ b/translations/ko-KR/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md @@ -20,3 +20,7 @@ When you enable access and security for a repository owned by your user account, {% data reusables.user_settings.codespaces-tab %} 1. Under "Access and security", select the setting you want for your user account. ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png) 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. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) + +## 더 읽을거리 + +- "[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/ko-KR/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md b/translations/ko-KR/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md index 956845aa41..649e557b60 100644 --- a/translations/ko-KR/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md +++ b/translations/ko-KR/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md @@ -20,3 +20,7 @@ When you perform an action related to {% data variables.product.prodname_codespa ![security log with Codespaces information](/assets/images/help/settings/codespaces-audit-log.png) The security log includes details on what action occurred and when you performed it. For information about {% data variables.product.prodname_codespaces %} actions, see "[{% data variables.product.prodname_codespaces %} category actions](/github/authenticating-to-github/reviewing-your-security-log#codespaces-category-actions)". + +## 더 읽을거리 + +- "[Reviewing your organization's audit logs for {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces)" diff --git a/translations/ko-KR/content/codespaces/the-githubdev-web-based-editor.md b/translations/ko-KR/content/codespaces/the-githubdev-web-based-editor.md new file mode 100644 index 0000000000..55e6edc2b0 --- /dev/null +++ b/translations/ko-KR/content/codespaces/the-githubdev-web-based-editor.md @@ -0,0 +1,106 @@ +--- +title: The github.dev web-based editor +intro: 'Use the github.dev {% data variables.product.prodname_serverless %} from your repository or pull request to create and commit changes.' +versions: + fpt: '*' +type: how_to +miniTocMaxHeadingLevel: 3 +topics: + - Codespaces + - Visual Studio Code + - Developer +shortTitle: Web-based editor +redirect_from: + - /codespaces/developing-in-codespaces/web-based-editor +--- + +{% note %} + +**Note:** The github.dev {% data variables.product.prodname_serverless %} is currently in beta preview. You can provide feedback [in our Discussions](https://github.co/browser-editor-feedback). + +{% endnote %} + +## About the {% data variables.product.prodname_serverless %} + +The {% data variables.product.prodname_serverless %} introduces a lightweight editing experience that runs entirely in your browser. With the {% data variables.product.prodname_serverless %}, you can navigate files and source code repositories from {% data variables.product.prodname_dotcom %}, and make and commit code changes. You can open any repository, fork, or pull request in the editor. + +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 %} 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. + +## Opening the {% data variables.product.prodname_serverless %} + +You can open any {% data variables.product.prodname_dotcom %} repository in the {% data variables.product.prodname_serverless %} in either of the following ways: + +- Press `.` while browsing any repository or pull request on {% data variables.product.prodname_dotcom %}. +- Change the URL from "github.com" to "github.dev". + +## {% data variables.product.prodname_codespaces %} and the {% data variables.product.prodname_serverless %} + +Both the {% data variables.product.prodname_serverless %} and {% data variables.product.prodname_codespaces %} allow you to edit your code straight from your repository. However, both have slightly different benefits, depending on your use case. + +| | {% data variables.product.prodname_serverless %} | {% data variables.product.prodname_codespaces %} +| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| **Cost** | 무료. | Costs for compute and storage. For information on pricing, see "[Codespaces pricing](/en/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)." | +| **Availability** | Available to everyone on GitHub.com. | Available for organizations using GitHub Team or GitHub Enterprise Cloud. | +| **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. | + +### Continue working on {% data variables.product.prodname_codespaces %} + +You can start your workflow in the {% data variables.product.prodname_serverless %} and continue working on a codespace, provided you have [access to {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces). If you try to access the Run and Debug View or the Terminal, you'll be notified that they are not available in the {% data variables.product.prodname_serverless %}. + +To continue your work in a codespace, click **Continue Working on…** and select **Create New Codespace** to create a codespace on your current branch. Before you choose this option, you must commit any changes. + +![A screenshot that shows the "Continue Working on" button in the UI](/assets/images/help/codespaces/codespaces-continue-working.png) + +## 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. + +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. + +### Create a new branch + +{% data reusables.codespaces.create-or-switch-branch %} + Any uncommited changes you have made in your old branch will be available on your new branch. + +### Commit your changes + +{% data reusables.codespaces.source-control-commit-changes %} +5. Once you have committed your changes, they will automatically be pushed to your branch on {% data variables.product.prodname_dotcom %}. +### Create a pull request + +{% data reusables.codespaces.source-control-pull-request %} + +### Working with an existing pull request + +You can use the {% data variables.product.prodname_serverless %} to work with an existing pull request. + +1. Browse to the pull request you'd like to open in the {% data variables.product.prodname_serverless %}. +2. Press `.` to open the pull request in the {% data variables.product.prodname_serverless %}. +3. Once you have made any changes, commit them using the steps in [Commit your changes](#commit-your-changes). Your changes will be committed directly to the branch, it's not necessary to push the changes. + +## 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. + +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. + + +## 문제 해결 + +If you have issues opening the {% data variables.product.prodname_serverless %}, try the following: + +- Make sure you are signed in to {% data variables.product.prodname_dotcom %}. +- Disable any ad blockers. +- Use a non-incognito window in your browser to open 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. diff --git a/translations/ko-KR/content/communities/documenting-your-project-with-wikis/about-wikis.md b/translations/ko-KR/content/communities/documenting-your-project-with-wikis/about-wikis.md index 6a4ff4c92f..b2b654ec64 100644 --- a/translations/ko-KR/content/communities/documenting-your-project-with-wikis/about-wikis.md +++ b/translations/ko-KR/content/communities/documenting-your-project-with-wikis/about-wikis.md @@ -34,4 +34,4 @@ You can edit wikis directly on {% data variables.product.product_name %}, or you - "[Creating a footer or sidebar for your wiki](/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki)" - "[Editing wiki content](/communities/documenting-your-project-with-wikis/editing-wiki-content)" - "[Viewing a wiki's history of changes](/articles/viewing-a-wiki-s-history-of-changes)" -- "[Searching wikis](/articles/searching-wikis)" +- "[Searching wikis](/search-github/searching-on-github/searching-wikis)" diff --git a/translations/ko-KR/content/communities/moderating-comments-and-conversations/locking-conversations.md b/translations/ko-KR/content/communities/moderating-comments-and-conversations/locking-conversations.md index db8434a5b6..c0731336c1 100644 --- a/translations/ko-KR/content/communities/moderating-comments-and-conversations/locking-conversations.md +++ b/translations/ko-KR/content/communities/moderating-comments-and-conversations/locking-conversations.md @@ -20,7 +20,7 @@ Locking a conversation creates a timeline event that is visible to anyone with r While a conversation is locked, only [people with write access](/articles/repository-permission-levels-for-an-organization/) and [repository owners and collaborators](/articles/permission-levels-for-a-user-account-repository/#collaborator-access-for-a-repository-owned-by-a-user-account) can add, hide, and delete comments. -To search for locked conversations in a repository that is not archived, you can use the search qualifiers `is:locked` and `archived:false`. Conversations are automatically locked in archived repositories. For more information, see "[Searching issues and pull requests](/articles/searching-issues-and-pull-requests#search-based-on-whether-a-conversation-is-locked)." +To search for locked conversations in a repository that is not archived, you can use the search qualifiers `is:locked` and `archived:false`. Conversations are automatically locked in archived repositories. For more information, see "[Searching issues and pull requests](/search-github/searching-on-github/searching-issues-and-pull-requests#search-based-on-whether-a-conversation-is-locked)." 1. Optionally, write a comment explaining why you're locking the conversation. 2. In the right margin of the issue or pull request, or above the comment box on the commit page, click **Lock conversation**. ![Lock conversation link](/assets/images/help/repository/lock-conversation.png) diff --git a/translations/ko-KR/content/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels.md b/translations/ko-KR/content/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels.md index 0698752dff..9063ed484b 100644 --- a/translations/ko-KR/content/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels.md +++ b/translations/ko-KR/content/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels.md @@ -12,7 +12,7 @@ topics: shortTitle: Encourage contributions --- -You can apply the `good first issue` label to issues in your public repository so that people can find them when searching by labels. For more information about searching by labels, see "[Searching issues and pull requests](/articles/searching-issues-and-pull-requests/#search-by-label)." +You can apply the `good first issue` label to issues in your public repository so that people can find them when searching by labels. For more information about searching by labels, see "[Searching issues and pull requests](/search-github/searching-on-github/searching-issues-and-pull-requests/#search-by-label)." {% data variables.product.prodname_dotcom %} uses an algorithm to determine the most approachable issues in each repository and surface them in various places on {% data variables.product.prodname_dotcom_the_website %}. Adding the `good first issue` label can increase the likelihood that your issues are surfaced. @@ -24,4 +24,4 @@ You can apply the `good first issue` label to issues in your public repository s ## 더 읽을거리 - "[About labels](/articles/about-labels)" -- "[Searching for repositories](/articles/searching-for-repositories)" +- "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories)" diff --git a/translations/ko-KR/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md b/translations/ko-KR/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md index 4048418111..458f0d7aaa 100644 --- a/translations/ko-KR/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md +++ b/translations/ko-KR/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md @@ -42,6 +42,7 @@ Using the web application flow, the process to identify users on your site is: If you select **Request user authorization (OAuth) during installation** when creating or modifying your app, step 1 will be completed during app installation. For more information, see "[Authorizing users during installation](/apps/installing-github-apps/#authorizing-users-during-installation)." ### 1. Request a user's GitHub identity +Direct the user to the following URL in their browser: GET {% data variables.product.oauth_host_code %}/login/oauth/authorize @@ -77,6 +78,8 @@ Exchange this `code` for an access token. When expiring tokens are enabled, the Expiring user tokens are currently an optional feature and subject to change. To opt-in to the user-to-server token expiration feature, see "[Activating optional features for apps](/developers/apps/activating-optional-features-for-apps)." +Make a request to the following endpoint to receive an access token: + POST {% data variables.product.oauth_host_code %}/login/oauth/access_token #### 매개변수 diff --git a/translations/ko-KR/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md b/translations/ko-KR/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md index 753b85353d..f68d96ceac 100644 --- a/translations/ko-KR/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md +++ b/translations/ko-KR/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md @@ -32,7 +32,7 @@ Different server-to-server request rate limits apply to {% data variables.produc ### {% data variables.product.prodname_ghe_cloud %} server-to-server rate limits -{% data variables.product.prodname_github_apps %} that are installed on an organization or repository owned by a {% data variables.product.prodname_ghe_cloud %} account and make server-to-server requests have a rate limit of 15,000 requests per hour. +{% data variables.product.prodname_github_apps %} that are installed on an organization or repository owned by a {% data variables.product.prodname_ghe_cloud %} account and make server-to-server requests have a rate limit of 15,000 requests per hour per organization for organization installations or per repository for repository installations. {% endif %} diff --git a/translations/ko-KR/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md b/translations/ko-KR/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md index 35a9d4124e..d31fc338ba 100644 --- a/translations/ko-KR/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md +++ b/translations/ko-KR/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md @@ -78,19 +78,29 @@ Exchange this `code` for an access token: By default, the response takes the following form: - access_token={% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&token_type=bearer +``` +access_token={% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&scope=repo%2Cgist&token_type=bearer +``` -You can also receive the content in different formats depending on the Accept header: +{% data reusables.apps.oauth-auth-vary-response %} - Accept: application/json - {"access_token":"{% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "scope":"repo,gist", "token_type":"bearer"} - - Accept: application/xml - - bearer - repo,gist - {% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %} - +```json +Accept: application/json +{ + "access_token":"{% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", + "scope":"repo,gist", + "token_type":"bearer" +} +``` + +```xml +Accept: application/xml + + bearer + repo,gist + {% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %} + +``` ### 3. Use the access token to access the API @@ -138,27 +148,35 @@ Your app must request a user verification code and verification URL that the app #### 응답 -{% ifversion fpt %} - ```JSON - { - "device_code": "3584d83530557fdd1f46af8289938c8ef79f9dc5", - "user_code": "WDJB-MJHT", - "verification_uri": "https://github.com/login/device", - "expires_in": 900, - "interval": 5 - } - ``` -{% else %} - ```JSON - { - "device_code": "3584d83530557fdd1f46af8289938c8ef79f9dc5", - "user_code": "WDJB-MJHT", - "verification_uri": "http(s)://[hostname]/login/device", - "expires_in": 900, - "interval": 5 - } - ``` -{% endif %} +By default, the response takes the following form: + +``` +device_code=3584d83530557fdd1f46af8289938c8ef79f9dc5&expires_in=900&interval=5&user_code=WDJB-MJHT&verification_uri=https%3A%2F%{% data variables.product.product_url %}%2Flogin%2Fdevice +``` + +{% data reusables.apps.oauth-auth-vary-response %} + +```json +Accept: application/json +{ + "device_code": "3584d83530557fdd1f46af8289938c8ef79f9dc5", + "user_code": "WDJB-MJHT", + "verification_uri": "{% data variables.product.oauth_host_code %}/login/device", + "expires_in": 900, + "interval": 5 +} +``` + +```xml +Accept: application/xml + + 3584d83530557fdd1f46af8289938c8ef79f9dc5 + WDJB-MJHT + {% data variables.product.oauth_host_code %}/login/device + 900 + 5 + +``` #### Response parameters @@ -196,14 +214,32 @@ Once the user has authorized, the app will receive an access token that can be u #### 응답 +By default, the response takes the following form: + +``` +access_token={% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&token_type=bearer&scope=repo%2Cgist +``` + +{% data reusables.apps.oauth-auth-vary-response %} + ```json +Accept: application/json { "access_token": "{% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "token_type": "bearer", - "scope": "user" + "scope": "repo,gist" } ``` +```xml +Accept: application/xml + + {% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %} + bearer + gist,repo + +``` + ### Rate limits for the device flow When a user submits the verification code on the browser, there is a rate limit of 50 submissions in an hour per application. diff --git a/translations/ko-KR/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md b/translations/ko-KR/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md index b266ea4dce..5185473a47 100644 --- a/translations/ko-KR/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md +++ b/translations/ko-KR/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md @@ -25,7 +25,7 @@ Public installation flows have a landing page to enable other people besides the ## Private installation flow -Private installation flows allow only the owner of a GitHub App to install it. Limited information about the GitHub App will still exist on a public page, but the **Install** button will only be available to organization administrators or the user account if the GitHub App is owned by an individual account. Private{% ifversion ghes < 3.2 or ghae %}, or internal,{% endif %} GitHub Apps can only be installed on the user or organization account of the owner. +Private installation flows allow only the owner of a GitHub App to install it. Limited information about the GitHub App will still exist on a public page, but the **Install** button will only be available to organization administrators or the user account if the GitHub App is owned by an individual account. {% ifversion fpt or ghes > 3.1 or ghae-next %}Private {% else %}Private (also known as internal){% endif %} GitHub Apps can only be installed on the user or organization account of the owner. ## Changing who can install your GitHub App @@ -36,5 +36,5 @@ To change who can install the GitHub App: {% data reusables.user-settings.github_apps %} 3. Select the GitHub App whose installation option you want to change. ![App selection](/assets/images/github-apps/github_apps_select-app.png) {% data reusables.user-settings.github_apps_advanced %} -5. Depending on the installation option of your GitHub App, click either **Make public** or **Make {% ifversion fpt or ghes > 3.1 %}private{% else %}internal{% endif %}**. ![Button to change the installation option of your GitHub App](/assets/images/github-apps/github_apps_make_public.png) -6. Depending on the installation option of your GitHub App, click either **Yes, make this GitHub App public** or **Yes, make this GitHub App {% ifversion fpt or ghes > 3.1 %}private{% else %}internal{% endif %}**. ![Button to confirm the change of your installation option](/assets/images/github-apps/github_apps_confirm_installation_option.png) +5. Depending on the installation option of your GitHub App, click either **Make public** or **Make {% ifversion fpt or ghes > 3.1 or ghae-next %}private{% else %}internal{% endif %}**. ![Button to change the installation option of your GitHub App](/assets/images/github-apps/github_apps_make_public.png) +6. Depending on the installation option of your GitHub App, click either **Yes, make this GitHub App public** or **Yes, make this GitHub App {% ifversion fpt or ghes < 3.2 %}internal{% else %}private{% endif %}**. ![Button to confirm the change of your installation option](/assets/images/github-apps/github_apps_confirm_installation_option.png) diff --git a/translations/ko-KR/content/developers/github-marketplace/github-marketplace-overview/about-marketplace-badges.md b/translations/ko-KR/content/developers/github-marketplace/github-marketplace-overview/about-marketplace-badges.md index 74cb9ed35a..092a97f372 100644 --- a/translations/ko-KR/content/developers/github-marketplace/github-marketplace-overview/about-marketplace-badges.md +++ b/translations/ko-KR/content/developers/github-marketplace/github-marketplace-overview/about-marketplace-badges.md @@ -30,7 +30,7 @@ Some apps on the {% data variables.product.prodname_marketplace %} have the {% o For more information about the requirements for listing an app on {% data variables.product.prodname_marketplace %}, see "[Requirements for listing an app on {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)." -For information on finding apps to use, see "[Searching {% data variables.product.prodname_marketplace %}](/github/searching-for-information-on-github/searching-github-marketplace)." +For information on finding apps to use, see "[Searching {% data variables.product.prodname_marketplace %}](/search-github/searching-on-github/searching-github-marketplace)." ## For GitHub actions diff --git a/translations/ko-KR/content/developers/overview/index.md b/translations/ko-KR/content/developers/overview/index.md index 069efb03bc..5422f566cb 100644 --- a/translations/ko-KR/content/developers/overview/index.md +++ b/translations/ko-KR/content/developers/overview/index.md @@ -8,7 +8,6 @@ versions: children: - /about-githubs-apis - /managing-deploy-keys - - /viewing-deployment-history - /using-ssh-agent-forwarding - /secret-scanning-partner-program - /replacing-github-services diff --git a/translations/ko-KR/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md b/translations/ko-KR/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md index ff738817a6..9240c7c672 100644 --- a/translations/ko-KR/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md +++ b/translations/ko-KR/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md @@ -190,7 +190,7 @@ Activity related to a branch protection rule. For more information, see "[About {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} -`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 %}`github` {% elsif ghes > 3.0 %}`github-enterprise` {% else %}empty {% endif %}for all other actions. +`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 %}`github`{% elsif ghes > 3.0 or ghae-next %}`github-enterprise`{% else %}empty{% endif %} for all other actions. ### Webhook payload example @@ -1032,24 +1032,29 @@ Deliveries for `review_requested` and `review_request_removed` events will have ### Webhook payload object -| 키 | 유형 | 설명 | -| -------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `ref` | `문자열` | The full [`git ref`](/rest/reference/git#refs) that was pushed. Example: `refs/heads/main`. | -| `before` | `문자열` | The SHA of the most recent commit on `ref` before the push. | -| `after` | `문자열` | The SHA of the most recent commit on `ref` after the push. | -| `commits` | `array` | An array of commit objects describing the pushed commits. (The array includes a maximum of 20 commits. If necessary, you can use the [Commits API](/rest/reference/repos#commits) to fetch additional commits. This limit is applied to timeline events only and isn't applied to webhook deliveries.) | -| `commits[][id]` | `문자열` | The SHA of the commit. | -| `commits[][timestamp]` | `문자열` | The ISO 8601 timestamp of the commit. | -| `commits[][message]` | `문자열` | The commit message. | -| `commits[][author]` | `개체` | The git author of the commit. | -| `commits[][author][name]` | `문자열` | The git author's name. | -| `commits[][author][email]` | `문자열` | 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` | `개체` | The user who pushed the commits. | +| 키 | 유형 | 설명 | +| -------------------------- | --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `ref` | `문자열` | The full [`git ref`](/rest/reference/git#refs) that was pushed. Example: `refs/heads/main` or `refs/tags/v3.14.1`. | +| `before` | `문자열` | The SHA of the most recent commit on `ref` before the push. | +| `after` | `문자열` | 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` | `개체` | 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` | `문자열` | 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.) The array includes a maximum of 20 commits. If necessary, you can use the [Commits API](/rest/reference/repos#commits) to fetch additional commits. This limit is applied to timeline events only and isn't applied to webhook deliveries. | +| `commits[][id]` | `문자열` | The SHA of the commit. | +| `commits[][timestamp]` | `문자열` | The ISO 8601 timestamp of the commit. | +| `commits[][message]` | `문자열` | The commit message. | +| `commits[][author]` | `개체` | The git author of the commit. | +| `commits[][author][name]` | `문자열` | The git author's name. | +| `commits[][author][email]` | `문자열` | 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` | `개체` | The user who pushed the commits. | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} diff --git a/translations/ko-KR/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md b/translations/ko-KR/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md index 76a02306c7..91937b4fe4 100644 --- a/translations/ko-KR/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md +++ b/translations/ko-KR/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md @@ -53,7 +53,7 @@ You can share your feedback about {% data variables.product.prodname_discussions ## 더 읽을거리 - "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)" -- "[Searching discussions](/github/searching-for-information-on-github/searching-discussions)" +- "[Searching discussions](/search-github/searching-on-github/searching-discussions)" - "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" - "[Moderating comments and conversations](/communities/moderating-comments-and-conversations)" - "[Maintaining your safety on {% data variables.product.prodname_dotcom %}](/communities/maintaining-your-safety-on-github)" diff --git a/translations/ko-KR/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md b/translations/ko-KR/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md index 058c38fb5f..cc2284fecb 100644 --- a/translations/ko-KR/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md +++ b/translations/ko-KR/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md @@ -2,7 +2,7 @@ title: Collaborating with maintainers using discussions shortTitle: Collaborating with maintainers intro: 'You can contribute to the goals, plans, health, and community for a project on {% data variables.product.product_name %} by communicating with the maintainers of the project in a discussion.' -permissions: People with read permissions to a repository can start and participate in discussions in the repository. +permissions: 'People with read access to a repository can start and participate in discussions in the repository. {% data reusables.enterprise-accounts.emu-permission-interact %}' versions: fpt: '*' --- @@ -32,7 +32,7 @@ To collaborate with maintainers in discussions, a repository administrator or pr ## Filtering the list of discussions -You can search for discussions and filter the list of discussions in a repository. For more information, see "[Searching discussions](/github/searching-for-information-on-github/searching-discussions)." +You can search for discussions and filter the list of discussions in a repository. For more information, see "[Searching discussions](/search-github/searching-on-github/searching-discussions)." {% data reusables.repositories.navigate-to-repo %} {% data reusables.discussions.discussions-tab %} diff --git a/translations/ko-KR/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md b/translations/ko-KR/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md index ab974fd44a..27e1af1723 100644 --- a/translations/ko-KR/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md +++ b/translations/ko-KR/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md @@ -1,7 +1,7 @@ --- title: Participating in a discussion intro: 'You can converse with the community and maintainers in a forum within the repository for a project on {% data variables.product.product_name %}.' -permissions: People with read permissions to a repository can participate in discussions in the repository. +permissions: 'People with read access to a repository can participate in discussions in the repository. {% data reusables.enterprise-accounts.emu-permission-interact %}' versions: fpt: '*' shortTitle: Participate in discussion diff --git a/translations/ko-KR/content/discussions/guides/finding-discussions-across-multiple-repositories.md b/translations/ko-KR/content/discussions/guides/finding-discussions-across-multiple-repositories.md index 2503b5899d..af5c882510 100644 --- a/translations/ko-KR/content/discussions/guides/finding-discussions-across-multiple-repositories.md +++ b/translations/ko-KR/content/discussions/guides/finding-discussions-across-multiple-repositories.md @@ -15,6 +15,6 @@ shortTitle: Find discussions ## 더 읽을거리 -- "[Searching discussions](/github/searching-for-information-on-github/searching-discussions)" +- "[Searching discussions](/search-github/searching-on-github/searching-discussions)" - "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)" - "[Managing discussions for your community](/discussions/managing-discussions-for-your-community)" diff --git a/translations/ko-KR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md index 407e760748..4a1ccb030c 100644 --- a/translations/ko-KR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md +++ b/translations/ko-KR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md @@ -8,12 +8,6 @@ redirect_from: shortTitle: Starter assignment --- -{% note %} - -**Note:** The Git & {% data variables.product.company_short %} starter assignment is in beta and subject to change. - -{% endnote %} - The Git & {% data variables.product.company_short %} starter assignment is a pre-made course that summarizes the basics of Git and {% data variables.product.company_short %} and links students to resources to learn more about specific topics. ## 빌드전 요구 사양 diff --git a/translations/ko-KR/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md b/translations/ko-KR/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md index fb7d82f0ea..73db2c20f8 100644 --- a/translations/ko-KR/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md +++ b/translations/ko-KR/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md @@ -1,6 +1,7 @@ --- title: Finding ways to contribute to open source on GitHub intro: 'You can find ways to contribute to open source projects on {% data variables.product.product_name %} that are relevant to you.' +permissions: '{% data reusables.enterprise-accounts.emu-permission-interact %}' redirect_from: - /articles/where-can-i-find-open-source-projects-to-work-on/ - /articles/finding-interesting-projects-on-github/ @@ -19,7 +20,7 @@ shortTitle: Contribute to open source ## Discovering relevant projects -If there's a particular topic that interests you, visit `github.com/topics/`. For example, if you are interested in machine learning, you can find relevant projects and good first issues by visiting https://github.com/topics/machine-learning. You can browse popular topics by visiting [Topics](https://github.com/topics). You can also search for repositories that match a topic you're interested in. For more information, see "[Searching for repositories](/articles/searching-for-repositories#search-by-topic)." +If there's a particular topic that interests you, visit `github.com/topics/`. For example, if you are interested in machine learning, you can find relevant projects and good first issues by visiting https://github.com/topics/machine-learning. You can browse popular topics by visiting [Topics](https://github.com/topics). You can also search for repositories that match a topic you're interested in. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories#search-by-topic)." If you've been active on {% data variables.product.product_name %}, you can find personalized recommendations for projects and good first issues based on your past contributions, stars, and other activities in [Explore](https://github.com/explore). You can also sign up for the Explore newsletter to receive emails about opportunities to contribute to {% data variables.product.product_name %} based on your interests. To sign up, see [Explore email newsletter](https://github.com/explore/subscribe). diff --git a/translations/ko-KR/content/get-started/exploring-projects-on-github/following-people.md b/translations/ko-KR/content/get-started/exploring-projects-on-github/following-people.md index c7cfe37bda..1696c135c8 100644 --- a/translations/ko-KR/content/get-started/exploring-projects-on-github/following-people.md +++ b/translations/ko-KR/content/get-started/exploring-projects-on-github/following-people.md @@ -1,6 +1,7 @@ --- title: Following people intro: 'You can follow people on {% data variables.product.product_name %} to receive notifications about their activity{% ifversion fpt %} and discover projects in their communities{% endif %}.' +permissions: '{% data reusables.enterprise-accounts.emu-permission-follow %}' redirect_from: - /articles/following-people - /github/getting-started-with-github/following-people diff --git a/translations/ko-KR/content/get-started/getting-started-with-git/associating-text-editors-with-git.md b/translations/ko-KR/content/get-started/getting-started-with-git/associating-text-editors-with-git.md index 3c23a58a47..10e31d5038 100644 --- a/translations/ko-KR/content/get-started/getting-started-with-git/associating-text-editors-with-git.md +++ b/translations/ko-KR/content/get-started/getting-started-with-git/associating-text-editors-with-git.md @@ -61,6 +61,7 @@ shortTitle: Associate text editors ## Using Atom as your editor 1. Install [Atom](https://atom.io/). For more information, see "[Installing Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" in the Atom documentation. +{% data reusables.command_line.open_the_multi_os_terminal %} 3. Type this command: ```shell $ git config --global core.editor "atom --wait" diff --git a/translations/ko-KR/content/get-started/learning-about-github/access-permissions-on-github.md b/translations/ko-KR/content/get-started/learning-about-github/access-permissions-on-github.md index 0ec09620de..18dc24d4ca 100644 --- a/translations/ko-KR/content/get-started/learning-about-github/access-permissions-on-github.md +++ b/translations/ko-KR/content/get-started/learning-about-github/access-permissions-on-github.md @@ -36,6 +36,8 @@ Organization members can have *owner*{% ifversion fpt %}, *billing manager*,{% e *Enterprise owners* have ultimate power over the enterprise account and can take every action in the enterprise account. *Billing managers* can manage your enterprise account's billing settings. Members and outside collaborators of organizations owned by your enterprise account are automatically members of the enterprise account, although they have no access to the enterprise account itself or its settings. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise)." +If an enterprise uses {% data variables.product.prodname_emus %}, members are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and are fully managed by the identity provider. The {% data variables.product.prodname_managed_users %} have read-only access to repositories that are not a part of their enterprise and cannot interact with users that are not also members of the enterprise. Within the organizations owned by the enterprise, the {% data variables.product.prodname_managed_users %} can be granted the same granular access levels available for regular organizations. For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." + {% data reusables.gated-features.enterprise-accounts %} {% endif %} diff --git a/translations/ko-KR/content/get-started/learning-about-github/githubs-products.md b/translations/ko-KR/content/get-started/learning-about-github/githubs-products.md index b1699eb724..9a967a5ec4 100644 --- a/translations/ko-KR/content/get-started/learning-about-github/githubs-products.md +++ b/translations/ko-KR/content/get-started/learning-about-github/githubs-products.md @@ -102,6 +102,7 @@ In addition to the features available with {% data variables.product.prodname_te - 50GB {% data variables.product.prodname_registry %} storage - Access control for {% data variables.product.prodname_pages %} sites. For more information, see Changing the visibility of your {% data variables.product.prodname_pages %} site" - A service level agreement for 99.9% monthly uptime +- The option to configure your enterprise for {% data variables.product.prodname_emus %}, so you can provision and manage members with your identity provider and restrict your member's contributions to just your enterprise. For more information, see "About {% data variables.product.prodname_emus %}." - The option to centrally manage policy and billing for multiple {% data variables.product.prodname_dotcom_the_website %} organizations with an enterprise account. For more information, see "About enterprise accounts." You can set up a trial to evaluate {% data variables.product.prodname_ghe_cloud %}. For more information, see "Setting up a trial of {% data variables.product.prodname_ghe_cloud %}." diff --git a/translations/ko-KR/content/get-started/learning-about-github/types-of-github-accounts.md b/translations/ko-KR/content/get-started/learning-about-github/types-of-github-accounts.md index f69effcb1f..a462379cb1 100644 --- a/translations/ko-KR/content/get-started/learning-about-github/types-of-github-accounts.md +++ b/translations/ko-KR/content/get-started/learning-about-github/types-of-github-accounts.md @@ -64,6 +64,14 @@ Every person who uses {% data variables.product.product_location %} has their ow {% endif %} +{% ifversion fpt %} +### {% data variables.product.prodname_emus %} + +With {% data variables.product.prodname_emus %}, instead of using your personal account, members of an {% data variables.product.prodname_emu_enterprise %} are provisioned accounts using the enterprise's identity provider (IdP). {% data variables.product.prodname_managed_users_caps %} authenticate using their IdP instead of a {% data variables.product.prodname_dotcom_the_website %} username and password. + +{% data variables.product.prodname_managed_users_caps %} can only interact with users, repositories, and organizations that are part of their enterprise. {% data variables.product.prodname_managed_users_caps %} have read-only access to the rest of {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." +{% endif %} + ## Organization accounts Organizations are shared accounts where groups of people can collaborate across many projects at once. Owners and administrators can manage member access to the organization's data and projects with sophisticated security and administrative features. diff --git a/translations/ko-KR/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md b/translations/ko-KR/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md index 67dc5449b4..57ece39a54 100644 --- a/translations/ko-KR/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md +++ b/translations/ko-KR/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md @@ -18,16 +18,19 @@ This guide will walk you through setting up, configuring and managing your {% da The main difference between the products is that {% data variables.product.prodname_ghe_cloud %} is hosted by {% data variables.product.prodname_dotcom %}, while {% data variables.product.prodname_ghe_server %} is self-hosted. -Within the {% data variables.product.prodname_ghe_cloud %} product, there are two different types of account that you can use: +With {% data variables.product.prodname_ghe_cloud %}, you have the option of using {% data variables.product.prodname_emus %}. {% data reusables.enterprise-accounts.emu-short-summary %} + +If you choose to let your members create and manage their own user accounts instead, there are two types of accounts you can use with {% data variables.product.prodname_ghe_cloud %}: - A single organization account - An enterprise account that contains multiple organizations -In either scenario, your users will use their own self-created user account and you'll invite them to join. ### 1. Understanding the differences between an organization account and enterprise account Both organization and enterprise accounts are available with {% data variables.product.prodname_ghe_cloud %}. An organization is a shared account where groups of people can collaborate across many projects at once, and owners and administrators can manage access to data and projects. An enterprise account enables collaboration between multiple organizations, and allows owners to centrally manage policy, billing and security for these organizations. For more information on the differences, see "[Organizations and enterprise accounts](/organizations/collaborating-with-groups-in-organizations/about-organizations#organizations-and-enterprise-accounts)." + + If you choose an enterprise account, keep in mind that some policies can be set only at an organization level, while others can be enforced for all organizations in an enterprise. Once you choose the account type you would like, you can proceed to setting up your account. In each of the sections in this guide, proceed to either the single organization or enterprise account section based on your account type. @@ -86,6 +89,11 @@ You can set permissions and member roles, create and manage teams, and give peop ### Managing members of an enterprise account Managing members of an enterprise is separate from managing members or teams in an organization. It is important to note that enterprise owners or administrators cannot access organization-level settings or manage members for organizations in their enterprise unless they are made an organization owner. For more information, see the above section, "[Managing members and teams in your organization](#managing-members-and-teams-in-your-organization)." + +If your enterprise uses {% data variables.product.prodname_emus %}, your members are fully managed through your identity provider. Adding members, making changes to their membership, and assigning roles is all managed using your IdP. For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." + +If your enterprise does not use {% data variables.product.prodname_emus %}, follow the steps below. + #### 1. Assigning roles in an enterprise By default, everyone in an enterprise is a member of the enterprise. There are also administrative roles, including enterprise owner and billing manager, that have different levels of access to enterprise settings and data. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)." #### 2. Inviting people to manage your enterprise @@ -97,6 +105,10 @@ To audit access to enterprise-owned resources or user license usage, you can vie ## Part 4: Managing security with {% data variables.product.prodname_ghe_cloud %} +* [Managing security for a single organization](#managing-security-for-a-single-organization) +* [Managing security for an {% data variables.product.prodname_emu_enterprise %}](#managing-security-for-an-enterprise-with-managed-users) +* [Managing security for an enterprise account without {% data variables.product.prodname_managed_users %}](#managing-security-for-an-enterprise-account-without-managed-users) + ### Managing security for a single organization You can help keep your organization secure by requiring two-factor authentication, configuring security features, reviewing your organization's audit log and integrations, and enabling SAML single sign-on and team synchronization. #### 1. Requiring two-factor authentication @@ -113,8 +125,28 @@ Organization owners can choose to disable, enable but not enforce, or enable and #### 5. Managing team synchronization for your organization Organization owners can enable team synchronization between your identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organization owners and team maintainers to connect teams in your organization with IdP groups. For more information, see "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)." -### Managing security for an enterprise account with multiple organizations +### Managing security for an {% data variables.product.prodname_emu_enterprise %} + +With {% data variables.product.prodname_emus %}, access and identity is managed centrally through your identity provider. Two-factor authentication and other login requirements should be enabled and enforced on your IdP. + +#### 1. Enabling and SAML single sign-on and provisioning in your {% data variables.product.prodname_emu_enterprise %} + +In an {% data variables.product.prodname_emu_enterprise %}, all members are provisioned and managed by your identity provider. You must enable SAML SSO and SCIM provisioning before you can start using your enterprise. For more information on configuring SAML SSO and provisioning for an {% data variables.product.prodname_emu_enterprise %}, see "[Configuring SAML single sign-on for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." + +#### 2. Managing teams in your {% data variables.product.prodname_emu_enterprise %} with your identity provider + +You can connect teams in your organizations to security groups in your identity provider, managing membership of your teams and access to repositories through your IdP. For more information, see "[Managing team memberships with identity provider groups](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)." + +#### 3. Managing allowed IP addresses for organizations in your {% data variables.product.prodname_emu_enterprise %} + +You can configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your {% data variables.product.prodname_emu_enterprise %}. For more information, see "[Enforcing security settings in your enterprise account](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-security-settings-in-your-enterprise-account#managing-allowed-ip-addresses-for-organizations-in-your-enterprise-account)." + +#### 4. Enforcing policies for Advanced Security features in your {% data variables.product.prodname_emu_enterprise %} +{% data reusables.getting-started.enterprise-advanced-security %} + +### Managing security for an enterprise account without {% data variables.product.prodname_managed_users %} To manage security for your enterprise, you can require two-factor authentication, manage allowed IP addresses, enable SAML single sign-on and team synchronization at an enterprise level, and sign up for and enforce GitHub Advanced Security features. + #### 1. Requiring two-factor authentication and managing allowed IP addresses for organizations in your enterprise account Enterprise owners can require that organization members, billing managers, and outside collaborators in all organizations owned by an enterprise account use two-factor authentication to secure their personal accounts. Before doing so, we recommend notifying all who have access to organizations in your enterprise. You can also configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account. @@ -126,7 +158,7 @@ You can centrally manage access to your enterprise's resources, organization mem You can enable and manage team sychronization between an identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organizations owned by your enterprise account to manage team membership with IdP groups. For more information, see "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/managing-team-synchronization-for-organizations-in-your-enterprise-account)." #### 4. Enforcing policies for Advanced Security features in your enterprise account -If you have a GitHub Advanced Security license for your enterprise account, you can enforce policies to manage {% data variables.product.prodname_dotcom %} Advanced Security features for organizations owned by an enterprise account. For more information, see "[Enforcing policies for Advanced Security in your enterprise account](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-policies-for-advanced-security-in-your-enterprise-account)." +{% data reusables.getting-started.enterprise-advanced-security %} ## Part 5: Managing organization and enterprise level policies and settings diff --git a/translations/ko-KR/content/get-started/quickstart/be-social.md b/translations/ko-KR/content/get-started/quickstart/be-social.md index e8b1926dec..4bc254fbc5 100644 --- a/translations/ko-KR/content/get-started/quickstart/be-social.md +++ b/translations/ko-KR/content/get-started/quickstart/be-social.md @@ -6,6 +6,7 @@ redirect_from: - /github/getting-started-with-github/be-social - /github/getting-started-with-github/quickstart/be-social intro: 'You can interact with people, repositories, and organizations on {% data variables.product.prodname_dotcom %}. See what others are working on and who they''re connecting with from your personal dashboard.' +permissions: '{% data reusables.enterprise-accounts.emu-permission-interact %}' versions: fpt: '*' ghes: '*' diff --git a/translations/ko-KR/content/get-started/quickstart/fork-a-repo.md b/translations/ko-KR/content/get-started/quickstart/fork-a-repo.md index 02e7b1a2ff..8c90b67b37 100644 --- a/translations/ko-KR/content/get-started/quickstart/fork-a-repo.md +++ b/translations/ko-KR/content/get-started/quickstart/fork-a-repo.md @@ -7,6 +7,7 @@ redirect_from: - /github/getting-started-with-github/fork-a-repo - /github/getting-started-with-github/quickstart/fork-a-repo intro: A fork is a copy of a repository. Forking a repository allows you to freely experiment with changes without affecting the original project. +permissions: '{% data reusables.enterprise-accounts.emu-permission-fork %}' versions: fpt: '*' ghes: '*' diff --git a/translations/ko-KR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md b/translations/ko-KR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md index 5a8b5acacc..bc9c06f70a 100644 --- a/translations/ko-KR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md +++ b/translations/ko-KR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md @@ -18,7 +18,7 @@ shortTitle: Enterprise Server trial You can request a 45-day trial to evaluate {% data variables.product.prodname_ghe_server %}. Your trial will be installed as a virtual appliance, with options for on-premises or cloud deployment. For a list of supported visualization platforms, see "[Setting up a GitHub Enterprise Server instance](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance)." -{% ifversion ghes %}{% data variables.product.prodname_dependabot %}{% else %}Security{% endif %} alerts and {% data variables.product.prodname_github_connect %} are not currently available in trials of {% data variables.product.prodname_ghe_server %}. For a demonstration of these features, contact {% data variables.contact.contact_enterprise_sales %}. For more information about these features, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" and "[Connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)." +{% ifversion ghes %}{% data variables.product.prodname_dependabot %}{% else %}Security{% endif %} alerts and {% data variables.product.prodname_github_connect %} are not currently available in trials of {% data variables.product.prodname_ghe_server %}. For a demonstration of these features, contact {% data variables.contact.contact_enterprise_sales %}. For more information about these features, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" and "[Connecting your enterprise account to {% data variables.product.prodname_dotcom_the_website %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." Trials are also available for {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_cloud %}](/articles/setting-up-a-trial-of-github-enterprise-cloud)." diff --git a/translations/ko-KR/content/get-started/using-git/dealing-with-special-characters-in-branch-and-tag-names.md b/translations/ko-KR/content/get-started/using-git/dealing-with-special-characters-in-branch-and-tag-names.md new file mode 100644 index 0000000000..e8c3daae8b --- /dev/null +++ b/translations/ko-KR/content/get-started/using-git/dealing-with-special-characters-in-branch-and-tag-names.md @@ -0,0 +1,48 @@ +--- +title: Dealing with special characters in branch and tag names +intro: 'Git is very permissive about what characters are allowed in branch and tag names. When using Git from a command-line shell, you may need to escape or quote special characters.' +versions: + fpt: '*' + ghes: '*' + ghae: '*' +shortTitle: Special characters in names +--- + +## About branch and tag names + +Most repositories use simple branch names, such as `main` or `update-icons`. Tag names also usually follow a basic format, such as a version number like `v1.2.3`. Both branch names and tag names may also use the path separator (`/`) for structure, for example `area/item` or `level-1/level-2/level-3`. Other than some exceptions — such as not starting or ending a name with a slash, or having consecutive slashes in the name — Git has very few restrictions on what characters may be used in branch and tag names. For more information, see "[git-check-ref-format](https://git-scm.com/docs/git-check-ref-format)" in the Git documentation. + +## Why you need to escape special characters + +When using a CLI, you might have situations where a branch or tag name contains special characters that have a special meaning for your shell environment. To use these characters safely in a Git command, they must be quoted or escaped, otherwise the command may have unintended effects. + +For example, the `$` character is used by many shells to refer to a variable. Most shells would interpret a valid branch name like `hello-$USER` as equivalent to the word "hello", followed by a hyphen, followed by the current value of the `USER` variable, rather than the literal string `hello-$USER`. If a branch name includes the `$` character, then the shell must be stopped from expanding it as a variable reference. Similarly, if a branch name contains a semi-colon (`;`), most shells interpret it as a command separator, so it needs to be quoted or escaped. + +## How to escape special characters in branch and tag names + +Most branch and tag names with special characters can be handled by including the name in single quotes, for example `'hello-$USER'`. + +* In the [Bash](https://www.gnu.org/software/bash/) shell, enclosing a string of characters in single quotes preserves the literal value of the characters within the single quotes. +* [Zsh](https://www.zsh.org/) behaves similar to Bash, however this behavior is configurable using the `RC_QUOTES` option. +* [PowerShell](https://microsoft.com/powershell) also treats characters literally when inside single quotes. + +For these shells, the main exception is when the branch or tag name itself contains a single quote. In this case, you should consult the official documentation for your shell: + +* [Bash documentation](https://www.gnu.org/software/bash/manual/) +* [Zsh documentation](https://zsh.sourceforge.io/Doc/) +* [Fish documentation](https://fishshell.com/docs/current/) +* [PowerShell documentation](https://docs.microsoft.com/en-gb/powershell/) + +## Naming branches and tags + +If possible, create branch and tag names that don't contain special characters, as these would need to be escaped. A safe default set of characters to use for branch names and tag names is: + +* The English alphabet (`a` to `z` and `A` to `Z`) +* Numbers (`0` to `9`) +* A limited set of punctuation characters: + * period (`.`) + * hyphen (`-`) + * underscore (`_`) + * forward slash (`/`) + +To avoid confusion, you should start branch names with a letter. diff --git a/translations/ko-KR/content/get-started/using-git/index.md b/translations/ko-KR/content/get-started/using-git/index.md index 2a8e883ff4..27ece3b345 100644 --- a/translations/ko-KR/content/get-started/using-git/index.md +++ b/translations/ko-KR/content/get-started/using-git/index.md @@ -23,5 +23,6 @@ children: - /about-git-rebase - /using-git-rebase-on-the-command-line - /resolving-merge-conflicts-after-a-git-rebase + - /dealing-with-special-characters-in-branch-and-tag-names --- diff --git a/translations/ko-KR/content/get-started/using-github/keyboard-shortcuts.md b/translations/ko-KR/content/get-started/using-github/keyboard-shortcuts.md index 38ee96b7f7..deef8759e0 100644 --- a/translations/ko-KR/content/get-started/using-github/keyboard-shortcuts.md +++ b/translations/ko-KR/content/get-started/using-github/keyboard-shortcuts.md @@ -24,7 +24,7 @@ Below is a list of some of the available keyboard shortcuts. | Keyboard shortcut | 설명 | | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| s or / | 검색 창 포커싱. For more information, see "[About searching on {% data variables.product.company_short %}](/articles/about-searching-on-github)." | +| s or / | 검색 창 포커싱. 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 %}"[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[About notifications](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}." | | esc | When focused on a user, issue, or pull request hovercard, closes the hovercard and refocuses on the element the hovercard is in | diff --git a/translations/ko-KR/content/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md b/translations/ko-KR/content/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md index 27389dc0df..6ee2aeb4fb 100644 --- a/translations/ko-KR/content/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md +++ b/translations/ko-KR/content/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md @@ -41,6 +41,12 @@ When _checks_ are set up in a repository, pull requests have a **Checks** tab wh ![Status checks within a pull request](/assets/images/help/pull_requests/checks.png) +{% note %} + +**Note:** The **Checks** tab only gets populated for pull requests if you set up _checks_, not _statuses_, for the repository. + +{% endnote %} + When a specific line in a commit causes a check to fail, you will see details about the failure, warning, or notice next to the relevant code in the **Files** tab of the pull request. ![Details of a status check](/assets/images/help/pull_requests/checks-detailed.png) diff --git a/translations/ko-KR/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork.md b/translations/ko-KR/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork.md index 735cf2081e..82aa24b5f7 100644 --- a/translations/ko-KR/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork.md +++ b/translations/ko-KR/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork.md @@ -5,7 +5,7 @@ redirect_from: - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork - /articles/creating-a-pull-request-from-a-fork - /github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork -permissions: Anyone with write access to a repository can create a pull request from a user-owned fork. +permissions: 'Anyone with write access to a repository can create a pull request from a user-owned fork. {% data reusables.enterprise-accounts.emu-permission-propose %}' versions: fpt: '*' ghes: '*' diff --git a/translations/ko-KR/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md b/translations/ko-KR/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md index c19bf02cd6..d89d558d07 100644 --- a/translations/ko-KR/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md +++ b/translations/ko-KR/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md @@ -1,6 +1,7 @@ --- title: Creating a pull request intro: 'Create a pull request to propose and collaborate on changes to a repository. These changes are proposed in a *branch*, which ensures that the default branch only contains finished and approved work.' +permissions: 'Anyone with read access to a repository can create a pull request. {% data reusables.enterprise-accounts.emu-permission-propose %}' redirect_from: - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request - /articles/creating-a-pull-request @@ -13,7 +14,7 @@ topics: - Pull requests --- -Anyone with read permissions to a repository can create a pull request, but you must have write permissions to create a branch. If you want to create a new branch for your pull request and don't have write permissions to the repository, you can fork the repository first. For more information, see "[Creating a pull request from a fork](/articles/creating-a-pull-request-from-a-fork)" and "[About forks](/articles/about-forks)." +If you want to create a new branch for your pull request and do not have write permissions to the repository, you can fork the repository first. For more information, see "[Creating a pull request from a fork](/articles/creating-a-pull-request-from-a-fork)" and "[About forks](/articles/about-forks)." You can specify which branch you'd like to merge your changes into when you create your pull request. Pull requests can only be opened between two branches that are different. diff --git a/translations/ko-KR/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/translations/ko-KR/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md index 2a3b4db14d..f294666a47 100644 --- a/translations/ko-KR/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md +++ b/translations/ko-KR/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md @@ -1,10 +1,10 @@ --- title: Reviewing dependency changes in a pull request intro: 'If a pull request contains changes to dependencies, you can view a summary of what has changed and whether there are known vulnerabilities in any of the dependencies.' +product: '{% data reusables.gated-features.dependency-review %}' versions: fpt: '*' ghes: '>= 3.2' - product: '{% data reusables.gated-features.dependency-review %}' type: how_to topics: - Pull requests @@ -38,19 +38,19 @@ Dependency review allows you to "shift left". You can use the provided predictiv 1. If the pull request contains many files, use the **File filter** drop-down menu to collapse all files that don't record dependencies. This will make it easier to focus your review on the dependency changes. - ![The file filter menu](/assets/images/help/pull_requests/file-filter-menu-json.png) + ![The file filter menu](/assets/images/help/pull_requests/file-filter-menu-json.png) The dependency review provides a clearer view of what has changed in large lock files, where the source diff is not rendered by default. + + {% note %} + + **Note:** Dependency review rich diffs are not available for committed static JavaScript files like `jquery.js`. + + {% endnote %} 1. On the right of the header for a manifest or lock file, display the dependency review by clicking the **{% octicon "file" aria-label="The rich diff icon" %}** rich diff button. ![The rich diff button](/assets/images/help/pull_requests/dependency-review-rich-diff.png) - {% note %} - - **Note:** The dependency review provides a clearer view of what has changed in large lock files, where the source diff is not rendered by default. - - {% endnote %} - -1. Check the dependencies listed in the dependency review. +2. Check the dependencies listed in the dependency review. ![Vulnerability warnings in a dependency review](/assets/images/help/pull_requests/dependency-review-vulnerability.png) diff --git a/translations/ko-KR/content/github/collaborating-with-pull-requests/working-with-forks/about-forks.md b/translations/ko-KR/content/github/collaborating-with-pull-requests/working-with-forks/about-forks.md index 9f858a7692..ae129cc1e1 100644 --- a/translations/ko-KR/content/github/collaborating-with-pull-requests/working-with-forks/about-forks.md +++ b/translations/ko-KR/content/github/collaborating-with-pull-requests/working-with-forks/about-forks.md @@ -20,6 +20,12 @@ Forking a repository is similar to copying a repository, with two major differen {% data reusables.repositories.you-can-fork %} +{% ifversion fpt %} + +If you're a member of a {% data variables.product.prodname_emu_enterprise %}, there are further restrictions on the repositories you can fork. {% data reusables.enterprise-accounts.emu-forks %} For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." + +{% endif %} + {% data reusables.repositories.desktop-fork %} Deleting a fork will not delete the original upstream repository. You can make any changes you want to your fork—add collaborators, rename files, generate {% data variables.product.prodname_pages %}—with no effect on the original.{% ifversion fpt %} You cannot restore a deleted forked repository. For more information, see "[Restoring a deleted repository](/articles/restoring-a-deleted-repository)."{% endif %} diff --git a/translations/ko-KR/content/github/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md b/translations/ko-KR/content/github/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md index e9d47e543d..20ed2d396d 100644 --- a/translations/ko-KR/content/github/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md +++ b/translations/ko-KR/content/github/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md @@ -52,4 +52,4 @@ If your local Git configuration contained a generic email address, or an email a ## 더 읽을거리 -* "[Searching commits](/articles/searching-commits)" +* "[Searching commits](/search-github/searching-on-github/searching-commits)" diff --git a/translations/ko-KR/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views.md b/translations/ko-KR/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views.md index 20e6d84a71..5cb22046d7 100644 --- a/translations/ko-KR/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views.md +++ b/translations/ko-KR/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views.md @@ -29,4 +29,4 @@ For more information on how Git considers commit history, see [the "History Simp ## 더 읽을거리 - "[Signing commits](/articles/signing-commits)" -- "[Searching commits](/articles/searching-commits)" +- "[Searching commits](/search-github/searching-on-github/searching-commits)" diff --git a/translations/ko-KR/content/github/copilot/about-github-copilot-telemetry.md b/translations/ko-KR/content/github/copilot/about-github-copilot-telemetry.md index 989263e8e0..7139ed503e 100644 --- a/translations/ko-KR/content/github/copilot/about-github-copilot-telemetry.md +++ b/translations/ko-KR/content/github/copilot/about-github-copilot-telemetry.md @@ -1,6 +1,6 @@ --- title: About GitHub Copilot telemetry -intro: '{% data variables.product.prodname_dotcom %} Copilot collects and relies on additional telemetry data beyond what other {% data variables.product.prodname_dotcom %} products and services collect.' +intro: '{% data variables.product.prodname_copilot %} collects and relies on additional telemetry data beyond what other {% data variables.product.company_short %} products and services collect.' redirect_from: - /early-access/github/copilot/about-github-copilot-telemetry versions: @@ -8,36 +8,21 @@ versions: --- ## What data is collected -The {% data variables.product.prodname_dotcom %} Copilot collects activity from the user’s Visual Studio Code editor, tied to a timestamp, and metadata. This metadata consists of the extension settings and the standard metadata collected by the [Visual Studio Code extension telemetry package](https://www.npmjs.com/package/vscode-extension-telemetry): -* Visual Studio Code machine ID (pseudonymized identifier) -* Visual Studio Code session ID (pseudonymized identifier) -* Visual Studio Code version -* [Geolocation from IP address](https://docs.microsoft.com/en-us/azure/azure-monitor/app/ip-collection?tabs=net) (country, state/province and city, but not the IP address itself) -* Operating system and version -* Extension version -* The VS Code UI (web or desktop) +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. -The activity collected consists of events that are triggered when: +## How the data is used by {% data variables.product.company_short %} -* An error occurs (it records the error kind and relevant background; e.g. if it’s an authentication error the key expiry date is recorded) -* Our models are accessed to ask for code suggestions (it records editor state like position of cursor and snippets of code)—this includes cases when the user takes an action to request code suggestions -* Code suggestions are received or displayed (it records the suggestions, post-processing, and metadata like model certainty and latency) -* Code suggestions are redacted due to filters that ensure AI safety -* The user acts on code suggestions (e.g. to accept or reject them) -* The user has acted on code suggestions and then it records whether or how they persisted in the code +{% data variables.product.company_short %} will use this data for: -## How the data is used -This data will only be used by {% data variables.product.company_short %} for: - -* Directly improving the product, including assessing different strategies in processing and predicting which suggestions users may find helpful -* Directly evaluating the product, e.g. by measuring the positive impact it has on the user -* Improving the underlying code generation models, e.g. by providing positive and negative examples (but always so that your private code is not used as input to suggest code for other users of {% data variables.product.prodname_dotcom %} Copilot) -* Guiding closely related {% data variables.product.prodname_dotcom %} products -* Investigating and detecting potential abuse of the {% data variables.product.prodname_dotcom %} Copilot service -* Other purposes related to improving the {% data variables.product.prodname_dotcom %} Copilot service +- Directly improving the product, including assessing different strategies in processing and predicting which suggestions users may find helpful +- Evaluating the product, e.g. by measuring the positive impact it has on the user +- Improving the underlying code generation models, e.g. by providing positive and negative examples (but always so that your private code is not used as input to suggest code for other users of {% data variables.product.prodname_copilot %}) +- Guiding closely related {% data variables.product.company_short %} products +- Investigating and detecting potential abuse of the {% data variables.product.prodname_copilot %} service +- Other purposes related to improving the {% data variables.product.prodname_copilot %} service, including sharing as described in the next section ## How the data is shared -The telemetry data is stored securely on {% data variables.product.prodname_dotcom %} systems, with appropriate encryption in place. -We know user edit actions and source code snippets are very sensitive data, and access is strictly controlled. The data can only be accessed by (1) named {% data variables.product.company_short %} personnel (employees and contractors) working on the {% data variables.product.company_short %} Copilot team or on the {% data variables.product.company_short %} platform health team, (2) select Microsoft personnel (employees and contractors) working on or with the {% data variables.product.company_short %} Copilot team, and (3) select employees of OpenAI who work on {% data variables.product.company_short %} Copilot. +The telemetry data is stored securely on {% data variables.product.company_short %} systems, with appropriate encryption in place. We know user edit actions, source code snippets, and URLs of repositories and file paths are sensitive data. Consequently, access is strictly controlled. The data can only be accessed by (1) named {% data variables.product.company_short %} personnel (employees and contractors) working on the {% data variables.product.prodname_copilot %} team or on the {% data variables.product.company_short %} platform health team, (2) Microsoft personnel (employees and contractors) working on or with the Azure and/or {% data variables.product.prodname_copilot %} teams, and (3) employees of OpenAI who work on {% data variables.product.prodname_copilot %}. + diff --git a/translations/ko-KR/content/github/copilot/github-copilot-telemetry-terms.md b/translations/ko-KR/content/github/copilot/github-copilot-telemetry-terms.md new file mode 100644 index 0000000000..6e178850e6 --- /dev/null +++ b/translations/ko-KR/content/github/copilot/github-copilot-telemetry-terms.md @@ -0,0 +1,16 @@ +--- +title: GitHub Copilot Telemetry Terms +intro: 'Acceptance of the additional telemetry described below is a condition to joining the wait list for the technical preview of {% data variables.product.prodname_copilot %} and using {% data variables.product.prodname_copilot %} during the technical preview.' +redirect_from: + - /early-access/github/copilot/telemetry-terms + - /github/copilot/telemetry-terms +versions: + fpt: '*' +--- + +## Additional telemetry + +If you use {% data variables.product.prodname_copilot %}, the {% data variables.product.prodname_copilot %} extension/plugin will collect usage information about events generated by interacting with the integrated development environment (IDE). These events include {% data variables.product.prodname_copilot %} performance, features used, and suggestions accepted, modified and accepted, or dismissed. This information may include personal data, including your User Personal Information, as defined in the [GitHub Privacy Statement](/github/site-policy/github-privacy-statement). + +This usage information is used by {% data variables.product.company_short %}, and shared with Microsoft and OpenAI, to develop and improve the extension/plugin and related products. OpenAI also uses this usage information to perform other services related to {% data variables.product.prodname_copilot %}. For example, when you edit files with the {% data variables.product.prodname_copilot %} extension/plugin enabled, file content snippets, suggestions, and any modifications to suggestions will be shared with {% data variables.product.company_short %}, Microsoft, and OpenAI, and used for diagnostic purposes to improve suggestions and related products. {% data variables.product.prodname_copilot %} relies on file content for context, both in the file you are editing and potentially other files open in the same IDE instance. When you are using {% data variables.product.prodname_copilot %}, it may also collect the URLs of repositories or file paths for relevant files. {% data variables.product.prodname_copilot %} does not use these URLs, file paths, or snippets collected in your telemetry as input to suggest code for other users of {% data variables.product.prodname_copilot %}. This information is treated as confidential information and accessed on a need-to-know basis. You are prohibited from collecting telemetry data about other users of {% data variables.product.prodname_copilot %} from the {% data variables.product.prodname_copilot %} extension/plugin. For more details about {% data variables.product.prodname_copilot %} telemetry, please see "[About {% data variables.product.prodname_copilot %} telemetry](/github/copilot/about-github-copilot-telemetry)." You may revoke your consent to the telemetry and personal data processing operations described in this paragraph by contacting GitHub and requesting removal from the technical preview. + diff --git a/translations/ko-KR/content/github/copilot/index.md b/translations/ko-KR/content/github/copilot/index.md index ef5fc94524..bc5bc35075 100644 --- a/translations/ko-KR/content/github/copilot/index.md +++ b/translations/ko-KR/content/github/copilot/index.md @@ -5,7 +5,7 @@ versions: fpt: '*' children: - /about-github-copilot-telemetry - - /telemetry-terms + - /github-copilot-telemetry-terms - /research-recitation --- diff --git a/translations/ko-KR/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md b/translations/ko-KR/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md index fafe64200f..4ed4d6fa7a 100644 --- a/translations/ko-KR/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md +++ b/translations/ko-KR/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md @@ -16,7 +16,7 @@ You may also have the option to select a free 14-day trial on some tools. You ca ## Finding tools on {% data variables.product.prodname_marketplace %} -You can discover, browse, and install apps and actions created by others on {% data variables.product.prodname_marketplace %}, see "[Searching {% data variables.product.prodname_marketplace %}](/github/searching-for-information-on-github/searching-github-marketplace)." +You can discover, browse, and install apps and actions created by others on {% data variables.product.prodname_marketplace %}, see "[Searching {% data variables.product.prodname_marketplace %}](/search-github/searching-on-github/searching-github-marketplace)." {% data reusables.actions.actions-not-verified %} diff --git a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning/sarif-support-for-code-scanning.md b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning/sarif-support-for-code-scanning.md index e6fd912ac7..ee57361223 100644 --- a/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning/sarif-support-for-code-scanning.md +++ b/translations/ko-KR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning/sarif-support-for-code-scanning.md @@ -31,7 +31,7 @@ If you're new to SARIF and want to learn more, see Microsoft's [`SARIF tutorials Each time the results of a new code scan are uploaded, the results are processed and alerts are added to the repository. To prevent duplicate alerts for the same problem, {% data variables.product.prodname_code_scanning %} uses fingerprints to match results across various runs so they only appear once in the latest run for the selected branch. This makes it possible to match alerts to the right line of code when files are edited. -{% data variables.product.prodname_dotcom %} uses the `partialFingerprints` property in the OASIS standard to detect when two results are logically identical. For more information, see the "[partialFingerprints property](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012611)" entry in the OASIS documentation. +{% data variables.product.prodname_dotcom %} uses the `partialFingerprints` property in the OASIS standard as an input in the computation of whether two results are logically identical. Specifically, the `primaryLocationLineHash` is used as a stable intra-file location, which is combined with the repository, file path, and rule data to form the full identity. For more information, see the "[partialFingerprints property](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012611)" entry in the OASIS documentation. SARIF files created by the {% data variables.product.prodname_codeql_workflow %} or using the {% data variables.product.prodname_codeql_runner %} include fingerprint data. If you upload a SARIF file using the `upload-sarif` action and this data is missing, {% data variables.product.prodname_dotcom %} attempts to populate the `partialFingerprints` field from the source files. For more information about uploading results, see "[Uploading a SARIF file to {% data variables.product.prodname_dotcom %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github#uploading-a-code-scanning-analysis-with-github-actions)." @@ -89,17 +89,17 @@ Any valid SARIF 2.1.0 output file can be uploaded, however, {% data variables.pr {% data reusables.code-scanning.upload-sarif-alert-limit %} -| 이름 | 설명 | -| --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `ruleId` | **Optional.** The unique identifier of the rule (`reportingDescriptor.id`). For more information, see the [`reportingDescriptor` object](#reportingdescriptor-object). {% data variables.product.prodname_code_scanning_capc %} uses the rule identifier to filter results by rule on {% data variables.product.prodname_dotcom %}. | -| `ruleIndex` | **Optional.** The index of the associated rule (`reportingDescriptor` object) in the tool component `rules` array. For more information, see the [`run` object](#run-object). | -| `rule` | **Optional.** A reference used to locate the rule (reporting descriptor) for this result. For more information, see the [`reportingDescriptor` object](#reportingdescriptor-object). | -| `level` | **Optional.** The severity of the result. This level overrides the default severity defined by the rule. {% data variables.product.prodname_code_scanning_capc %} uses the level to filter results by severity on {% data variables.product.prodname_dotcom %}. | -| `message.text` | **Required.** A message that describes the result. {% data variables.product.prodname_code_scanning_capc %} displays the message text as the title of the result. Only the first sentence of the message will be displayed when visible space is limited. | -| `locations[]` | **Required.** The set of locations where the result was detected up to a maximum of 10. Only one location should be included unless the problem can only be corrected by making a change at every specified location. **Note:** At least one location is required for {% data variables.product.prodname_code_scanning %} to display a result. {% data variables.product.prodname_code_scanning_capc %} will use this property to decide which file to annotate with the result. Only the first value of this array is used. All other values are ignored. | -| `partialFingerprints` | **Required.** A set of strings used to track the unique identity of the result. {% data variables.product.prodname_code_scanning_capc %} uses `partialFingerprints` to accurately identify which results are the same across commits and branches. {% data variables.product.prodname_code_scanning_capc %} will attempt to use `partialFingerprints` if they exist. If you are uploading third-party SARIF files with the `upload-action`, the action will create `partialFingerprints` for you when they are not included in the SARIF file. For more information, see "[Preventing duplicate alerts using fingerprints](#preventing-duplicate-alerts-using-fingerprints)." **Note:** {% data variables.product.prodname_code_scanning_capc %} only uses the `primaryLocationLineHash`. | -| `codeFlows[].threadFlows[].locations[]` | **Optional.** An array of `location` objects for a `threadFlow` object, which describes the progress of a program through a thread of execution. A `codeFlow` object describes a pattern of code execution used to detect a result. If code flows are provided, {% data variables.product.prodname_code_scanning %} will expand code flows on {% data variables.product.prodname_dotcom %} for the relevant result. For more information, see the [`location` object](#location-object). | -| `relatedLocations[]` | A set of locations relevant to this result. {% data variables.product.prodname_code_scanning_capc %} will link to related locations when they are embedded in the result message. For more information, see the [`location` object](#location-object). | +| 이름 | 설명 | +| --------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `ruleId` | **Optional.** The unique identifier of the rule (`reportingDescriptor.id`). For more information, see the [`reportingDescriptor` object](#reportingdescriptor-object). {% data variables.product.prodname_code_scanning_capc %} uses the rule identifier to filter results by rule on {% data variables.product.prodname_dotcom %}. | +| `ruleIndex` | **Optional.** The index of the associated rule (`reportingDescriptor` object) in the tool component `rules` array. For more information, see the [`run` object](#run-object). | +| `rule` | **Optional.** A reference used to locate the rule (reporting descriptor) for this result. For more information, see the [`reportingDescriptor` object](#reportingdescriptor-object). | +| `level` | **Optional.** The severity of the result. This level overrides the default severity defined by the rule. {% data variables.product.prodname_code_scanning_capc %} uses the level to filter results by severity on {% data variables.product.prodname_dotcom %}. | +| `message.text` | **Required.** A message that describes the result. {% data variables.product.prodname_code_scanning_capc %} displays the message text as the title of the result. Only the first sentence of the message will be displayed when visible space is limited. | +| `locations[]` | **Required.** The set of locations where the result was detected up to a maximum of 10. Only one location should be included unless the problem can only be corrected by making a change at every specified location. **Note:** At least one location is required for {% data variables.product.prodname_code_scanning %} to display a result. {% data variables.product.prodname_code_scanning_capc %} will use this property to decide which file to annotate with the result. Only the first value of this array is used. All other values are ignored. | +| `partialFingerprints` | **Required.** A set of strings used to track the unique identity of the result. {% data variables.product.prodname_code_scanning_capc %} uses `partialFingerprints` as part of the computation to accurately identify which results are the same across commits and branches. {% data variables.product.prodname_code_scanning_capc %} will attempt to use `partialFingerprints` if they exist. If you are uploading third-party SARIF files with the `upload-action`, the action will create `partialFingerprints` for you when they are not included in the SARIF file. For more information, see "[Preventing duplicate alerts using fingerprints](#preventing-duplicate-alerts-using-fingerprints)." **Note:** {% data variables.product.prodname_code_scanning_capc %} only uses the `primaryLocationLineHash`. | +| `codeFlows[].threadFlows[].locations[]` | **Optional.** An array of `location` objects for a `threadFlow` object, which describes the progress of a program through a thread of execution. A `codeFlow` object describes a pattern of code execution used to detect a result. If code flows are provided, {% data variables.product.prodname_code_scanning %} will expand code flows on {% data variables.product.prodname_dotcom %} for the relevant result. For more information, see the [`location` object](#location-object). | +| `relatedLocations[]` | A set of locations relevant to this result. {% data variables.product.prodname_code_scanning_capc %} will link to related locations when they are embedded in the result message. For more information, see the [`location` object](#location-object). | ### `location` object diff --git a/translations/ko-KR/content/github/index.md b/translations/ko-KR/content/github/index.md index 151b7b550b..28b87c4f27 100644 --- a/translations/ko-KR/content/github/index.md +++ b/translations/ko-KR/content/github/index.md @@ -15,7 +15,6 @@ children: - /writing-on-github - /committing-changes-to-your-project - /collaborating-with-pull-requests - - /searching-for-information-on-github - /importing-your-projects-to-github - /managing-security-vulnerabilities - /finding-security-vulnerabilities-and-errors-in-your-code diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/about-identity-and-access-management-for-your-enterprise-account.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/about-identity-and-access-management-for-your-enterprise-account.md index 3dfe3805c2..1f5322481a 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/about-identity-and-access-management-for-your-enterprise-account.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/about-identity-and-access-management-for-your-enterprise-account.md @@ -21,6 +21,12 @@ If you use Azure AD as your IDP, you can use team synchronization to manage team {% data reusables.saml.switching-from-org-to-enterprise %} For more information, see "[Switching your SAML configuration from an organization to an enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)." +## About {% data variables.product.prodname_emus %} + +{% data reusables.enterprise-accounts.emu-short-summary %} + +Configuring {% data variables.product.prodname_emus %} for SAML single-sign on and user provisioning involves following a different process than you would for an enterprise that isn't using {% data variables.product.prodname_managed_users %}. If your enterprise uses {% data variables.product.prodname_emus %}, see "[Configuring SAML single sign-on for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." + ## Supported IdPs We test and officially support the following IdPs. For SAML SSO, we offer limited support for all identity providers that implement the SAML 2.0 standard. For more information, see the [SAML Wiki](https://wiki.oasis-open.org/security) on the OASIS website. @@ -32,4 +38,3 @@ We test and officially support the following IdPs. For SAML SSO, we offer limite | OneLogin | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | PingOne | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | Shibboleth | {% octicon "check-circle-fill" aria-label="The check icon" %} | | - diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/configuring-saml-single-sign-on-for-your-enterprise-account-using-okta.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/configuring-saml-single-sign-on-for-your-enterprise-account-using-okta.md index 7d41e4d8dd..1ddfdb988b 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/configuring-saml-single-sign-on-for-your-enterprise-account-using-okta.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/configuring-saml-single-sign-on-for-your-enterprise-account-using-okta.md @@ -16,6 +16,8 @@ shortTitle: Configure SAML with Okta {% data reusables.enterprise-accounts.user-provisioning-release-stage %} +{% data reusables.enterprise-accounts.emu-saml-note %} + ## About SAML with Okta You can control access to your enterprise account in {% data variables.product.product_name %} and other web applications from one central interface by configuring the enterprise account to use SAML SSO with Okta, an Identity Provider (IdP). diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account.md index 0215514439..4c3a9efdf8 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account.md @@ -13,6 +13,8 @@ redirect_from: shortTitle: Enforce SAML --- +{% data reusables.enterprise-accounts.emu-saml-note %} + ## About SAML single sign-on for enterprise accounts {% data reusables.saml.dotcom-saml-explanation %} 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)." diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/managing-team-synchronization-for-organizations-in-your-enterprise-account.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/managing-team-synchronization-for-organizations-in-your-enterprise-account.md index 2c9bf5d425..d42bffba1f 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/managing-team-synchronization-for-organizations-in-your-enterprise-account.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/managing-team-synchronization-for-organizations-in-your-enterprise-account.md @@ -12,6 +12,8 @@ redirect_from: shortTitle: Manage team synchronization --- +{% data reusables.enterprise-accounts.emu-scim-note %} + ## About team synchronization for enterprise accounts If you use Azure AD as your IdP, you can enable team synchronization for your enterprise account to allow organization owners and team maintainers to synchronize teams in the organizations owned by your enterprise accounts with IdP groups. diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md index c0dd52afbf..3dcefef396 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md @@ -10,6 +10,8 @@ topics: shortTitle: Switching from organization --- +{% data reusables.enterprise-accounts.emu-saml-note %} + ## About SAML single sign-on for enterprise accounts {% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %} diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/index.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/index.md index 12012356e5..8d939d4737 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/index.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/index.md @@ -14,6 +14,7 @@ topics: children: - /managing-your-enterprise-account - /managing-users-in-your-enterprise + - /managing-your-enterprise-users-with-your-identity-provider - /managing-organizations-in-your-enterprise-account - /configuring-identity-and-access-management-for-your-enterprise-account - /setting-policies-for-organizations-in-your-enterprise-account diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account.md index e12d66ea3d..3f96297990 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account.md @@ -1,6 +1,6 @@ --- title: Adding organizations to your enterprise account -intro: You can create new organizations to manage within your enterprise account. +intro: You can create new organizations or invite existing organizations to manage within your enterprise account. product: '{% data reusables.gated-features.enterprise-accounts %}' redirect_from: - /articles/adding-organizations-to-your-enterprise-account @@ -13,9 +13,9 @@ topics: shortTitle: Add organizations --- -Enterprise owners can create new organizations within an enterprise account's settings. +Enterprise owners can create new organizations within an enterprise account's settings or invite existing organizations to join an enterprise account. -To add an organization to your enterprise account, you must create the organization from within the enterprise account settings. If you want to transfer an existing organization to your enterprise account, contact your {% data variables.product.prodname_dotcom %} sales account representative. +To add an organization to your enterprise account, you must create the organization from within the enterprise account settings. ## Creating an organization in your enterprise account @@ -29,3 +29,15 @@ Enterprise owners who create an organization owned by the enterprise account aut 4. Click **Create organization**. 5. Under "Invite owners", type the username of a person you'd like to invite to become an organization owner, then click **Invite**. ![Organization owner search field and Invite button](/assets/images/help/business-accounts/invite-org-owner.png) 6. Click **Finish**. + +## Inviting an organization to join your enterprise account + +Enterprise owners can invite existing organizations to join their enterprise account. If the organization you want to invite is already owned by another enterprise, you will not be able to issue an invitation until the previous enterprise gives up ownership of the organization. + +{% data reusables.enterprise-accounts.access-enterprise %} +2. On the **Organizations** tab, above the list of organizations, click **Invite organization**. ![Invite organization](/assets/images/help/business-accounts/enterprise-account-invite-organization.png) +3. Under "Organization name", start typing the name of the organization you want to invite and select it when it appears in the drop-down list. ![Search for organization](/assets/images/help/business-accounts/enterprise-account-search-for-organization.png) +4. Click **Invite organization**. +5. The organization owners will receive an email inviting them to join the organization. At least one owner needs to accept the invitation before the process can continue. You can cancel or resend the invitation at any time before an owner approves it. ![Cancel or resend](/assets/images/help/business-accounts/enterprise-account-invitation-sent.png) +6. Once an organization owner has approved the invitation, you can view its status in the list of pending invitations. ![Pending invitation](/assets/images/help/business-accounts/enterprise-account-pending.png) +7. Click **Approve** to complete the transfer, or **Cancel** to cancel it. ![Approve invitation](/assets/images/help/business-accounts/enterprise-account-transfer-approve.png) diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md index 065e4892bf..8b435c9f38 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md @@ -28,6 +28,12 @@ If you want to manage owners and billing managers for an enterprise account on { {% endif %} +{% ifversion fpt %} + +If your enterprise uses {% data variables.product.prodname_emus %}, enterprise owners can only be added or removed through your identity provider. For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." + +{% endif %} + {% tip %} **Tip:** For more information on managing users within an organization owned by your enterprise account, see "[Managing membership in your organization](/articles/managing-membership-in-your-organization)" and "[Managing people's access to your organization with roles](/articles/managing-peoples-access-to-your-organization-with-roles)." diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise.md index ced2ec4bd9..bd9d3a0613 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise.md @@ -21,7 +21,14 @@ Everyone in an enterprise is a member of the enterprise. You can also assign adm {% data reusables.enterprise-accounts.enterprise-administrators %} -For more information about adding people to your enterprise, see "{% ifversion fpt %}[Inviting people to manage your enterprise](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise){% else %}[Authentication](/admin/authentication){% endif %}". +{% ifversion fpt %} +If your enterprise does not use {% data variables.product.prodname_emus %}, you can invite someone to an administrative role using a user account on {% data variables.product.product_name %} that they control. For more information, see "[Inviting people to manage your enterprise](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)". + +In an enterprise using {% data variables.product.prodname_emus %}, new owners and members must be provisioned through your identity provider. Enterprise owners and organization owners cannot add new members or owners to the enterprise using {% data variables.product.prodname_dotcom %}. You can select a member's enterprise role using your IdP and it cannot be changed on {% data variables.product.prodname_dotcom %}. You can select a member's role in an organization on {% data variables.product.prodname_dotcom %}. For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." +{% else %} +For more information about adding people to your enterprise, see "[Authentication](/admin/authentication)". + +{% endif %} ## Enterprise owner diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md index ff0f3d7fc1..b4fbf2ada2 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md @@ -18,18 +18,13 @@ shortTitle: View & manage SAML access When you enable SAML single sign-on for your enterprise account, each enterprise member can link their external identity on your identity provider (IdP) to their existing {% data variables.product.product_name %} account. {% data reusables.saml.about-saml-access-enterprise-account %} +If your enterprise is uses {% data variables.product.prodname_emus %}, your members will use accounts provisioned through your IdP. {% data variables.product.prodname_managed_users_caps %} will not use their existing user account on {% data variables.product.product_name %}. For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." + ## Viewing and revoking a linked identity {% data reusables.saml.about-linked-identities %} -{% warning %} - -**Warning:** For organizations using SCIM: -- Revoking a linked user identity on {% data variables.product.product_name %} will also remove the SAML and SCIM metadata. As a result, the identity provider will not be able to synchronize or deprovision the linked user identity. -- An admin must revoke a linked identity through the identity provider. -- To revoke a linked identity and link a different account through the identity provider, an admin can remove and re-assign the user to the {% data variables.product.product_name %} application. For more information, see your identity provider's docs. - -{% endwarning %} +If your enterprise uses {% data variables.product.prodname_emus %}, you will not be able to deprovision or remove user accounts from the enterprise on {% data variables.product.product_name %}. Any changes you need to make to your enterprise's {% data variables.product.prodname_managed_users %} should be made through your IdP. {% data reusables.identity-and-permissions.revoking-identity-team-sync %} diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md new file mode 100644 index 0000000000..2929a15eaf --- /dev/null +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md @@ -0,0 +1,84 @@ +--- +title: About Enterprise Managed Users +shortTitle: About managed users +intro: 'You can centrally manage identity and access for your enterprise members on {% data variables.product.prodname_dotcom %} from your identity provider.' +product: '{% data reusables.gated-features.emus %}' +redirect_from: + - /early-access/github/articles/get-started-with-managed-users-for-your-enterprise +versions: + fpt: '*' +topics: + - Accounts + - Enterprise +--- + +## About {% data variables.product.prodname_emus %} + +With {% data variables.product.prodname_emus %}, you can control the user accounts of your enterprise members through your identity provider (IdP). You can simplify authentication with SAML single sign-on (SSO) and provision, update, and deprovision user accounts for your enterprise members. Users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your IdP are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and added to your enterprise. You control usernames, profile data, team membership, and repository access from your IdP. + +In your IdP, you can give each {% data variables.product.prodname_managed_user %} the role of user, enterprise owner, or billing manager. {% data variables.product.prodname_managed_users_caps %} can own organizations within your enterprise and can add other {% data variables.product.prodname_managed_users %} to the organizations and teams within. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" and "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)." + +You can also manage team membership within an organization in your enterprise directly through your IdP, allowing you to manage repository access using groups in your IdP. Organization membership can be managed manually or updated automatically as {% data variables.product.prodname_managed_users %} are added to teams within the organization. For more information, see "[Managing team memberships with identity provider groups](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)." + +You can grant {% data variables.product.prodname_managed_users %} access and the ability to contribute to repositories within your enterprise, but {% data variables.product.prodname_managed_users %} cannot create public content or collaborate with other users, organizations, and enterprises on the rest of {% data variables.product.prodname_dotcom %}. The {% data variables.product.prodname_managed_users %} provisioned for your enterprise cannot be invited to organizations or repositories outside of the enterprise, nor can the {% data variables.product.prodname_managed_users %} be invited to other enterprises. Outside collaborators are not supported by {% data variables.product.prodname_emus %}. + +The usernames of your enterprise's {% data variables.product.prodname_managed_users %} and their profile information, such as display names and email addresses, are set by through your IdP and cannot be changed by the users themselves. For more information, see "[Usernames and profile information](#usernames-and-profile-information)." + +{% data reusables.enterprise-accounts.emu-forks %} + +Enterprise owners can audit all of the {% data variables.product.prodname_managed_users %}' actions on {% data variables.product.prodname_dotcom %}. + +To use {% data variables.product.prodname_emus %}, you need a separate type of enterprise account with {% data variables.product.prodname_emus %} enabled. For more information about creating this account, see "[About enterprises with managed users](#about-enterprises-with-managed-users)." + + +## Identity provider support + +{% data variables.product.prodname_emus %} supports the following IdPs: + +{% data reusables.enterprise-accounts.emu-supported-idps %} + +## Abilities and restrictions of {% data variables.product.prodname_managed_users %} + +{% data variables.product.prodname_managed_users_caps %} can only contribute to private and internal repositories within their enterprise and private repositories owned by their user account. {% data variables.product.prodname_managed_users_caps %} have read-only access to the wider {% data variables.product.prodname_dotcom %} community. + +* {% data variables.product.prodname_managed_users_caps %} cannot create issues or pull requests in, comment or add reactions to, nor star, watch, or fork repositories outside of the enterprise. +* {% data variables.product.prodname_managed_users_caps %} cannot push code to repositories outside of the enterprise. +* {% data variables.product.prodname_managed_users_caps %} and the content they create is only visible to other members of the enterprise. +* {% data variables.product.prodname_managed_users_caps %} cannot follow users outside of the enterprise. +* {% data variables.product.prodname_managed_users_caps %} cannot create gists or comment on gists. +* {% data variables.product.prodname_managed_users_caps %} cannot install {% data variables.product.prodname_github_apps %} on their user accounts. +* Other {% data variables.product.prodname_dotcom %} users cannot see, mention, or invite a {% data variables.product.prodname_managed_user %} to collaborate. +* {% data variables.product.prodname_managed_users_caps %} can only own private repositories and {% data variables.product.prodname_managed_users %} can only invite other enterprise members to collaborate on their owned repositories. +* Only private and internal repositories can be created in organizations owned by an {% data variables.product.prodname_emu_enterprise %}, depending on organization and enterprise repository visibility settings. + +## About enterprises with managed users + +To use {% data variables.product.prodname_emus %}, you need a separate type of enterprise account with {% data variables.product.prodname_emus %} enabled. To try out {% data variables.product.prodname_emus %} or to discuss options for migrating from your existing enterprise, please contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact). + +Your contact on the GitHub Sales team will work with you to create your new {% data variables.product.prodname_emu_enterprise %}. You'll need to provide the email address for the user who will set up your enterprise and a short code that will be used as the suffix for your enterprise members' usernames. {% data reusables.enterprise-accounts.emu-shortcode %} For more information, see "[Usernames and profile information](#usernames-and-profile-information)." + +After we create your enterprise, you will receive an email from {% data variables.product.prodname_dotcom %} inviting you to choose a password for your enterprise's setup user, which will be the first owner in the enterprise. The setup user is only used to configure SAML single sign-on and SCIM provisioning integration for the enterprise. It will no longer have access to administer the enterprise account once SAML is successfully enabled. + +The setup user's username is your enterprise's shortcode suffixed with `_admin`. After you log in to your setup user, you can get started by configuring SAML SSO for your enterprise. For more information, see "[Configuring SAML single sign-on for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." + +{% note %} + +{% data reusables.enterprise-accounts.emu-password-reset-session %} + +{% endnote %} + +## Authenticating as a {% data variables.product.prodname_managed_user %} + +{% data variables.product.prodname_managed_users_caps %} must authenticate through their identity provider. + +To authenticate, {% data variables.product.prodname_managed_users %} must visit their IdP application portal or **https://github.com/enterprises/ENTERPRISE_NAME**, replacing **ENTERPRISE_NAME** with your enterprise's name. + +## Usernames and profile information + +When your {% data variables.product.prodname_emu_enterprise %} is created, you will choose a short code that will be used as the suffix for your enterprise member's usernames. {% data reusables.enterprise-accounts.emu-shortcode %} The setup user who configures SAML SSO has a username in the format of **@SHORT-CODE_admin**. + +When you provision a new user from your identity provider, the new {% data variables.product.prodname_managed_user %} will have a {% data variables.product.product_name %} username in the format of **@IDP-USERNAME_SHORT-CODE**. When using Azure Active Directory (Azure AD), _IDP-USERNAME_ is formed by normalizing the characters preceding the `@` character in the UPN (User Principal Name) provided by Azure AD. When using Okta, _IDP-USERNAME_ is the normalized username attribute provided by Okta. + +The username of the new account provisioned on {% data variables.product.product_name %}, including underscore and short code, must not exceed 39 characters. + +The profile name and email address of a {% data variables.product.prodname_managed_user %} is also provided by the IdP. {% data variables.product.prodname_managed_users_caps %} cannot change their profile name or email address on {% data variables.product.prodname_dotcom %}. diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/auditing-activity-in-your-enterprise.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/auditing-activity-in-your-enterprise.md new file mode 100644 index 0000000000..0da71cc51a --- /dev/null +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/auditing-activity-in-your-enterprise.md @@ -0,0 +1,32 @@ +--- +title: Auditing activity in your enterprise +shortTitle: Auditing activity +intro: 'You can audit the activity of the {% data variables.product.prodname_managed_users %} in your enterprise, viewing information about what actions were performed, by which user, and when they took place.' +permissions: Enterprise owners can access the audit log. +product: '{% data reusables.gated-features.emus %}' +versions: + fpt: '*' +topics: + - Accounts + - Enterprise +--- + +## About the audit log + +The audit log allows enterprise owners to quickly review or export the actions performed by both owners and members of your enterprise. Each audit log entry shows information about the event. + +- The organization an action was performed in +- The user who performed the action +- Which repository an action was performed in +- The action that was performed +- Which country the action took place in +- The date and time the action occurred + +## Accessing the audit log + +You can also access the audit log for your enterprise from the REST API. For more information, see "[GitHub Enterprise administration](/rest/reference/enterprise-admin#get-the-audit-log-for-an-enterprise)" in the API documentation. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.audit-log-tab %} +1. Optionally, above the list of events, select the **Export Git Events** or **Export** drop-down menu and choose options for exporting events from the audit log. !["Export Git Events" and "Export" drop-down menus for the enterprise audit log](/assets/images/help/enterprises/audit-log-export-drop-down-menus.png) diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users.md new file mode 100644 index 0000000000..8366161ea6 --- /dev/null +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users.md @@ -0,0 +1,109 @@ +--- +title: Configuring SAML single sign-on for Enterprise Managed Users +shortTitle: SAML for managed users +intro: 'You can automatically manage access to your enterprise account on {% data variables.product.prodname_dotcom %} by configuring Security Assertion Markup Language (SAML) single sign-on (SSO).' +product: '{% data reusables.gated-features.emus %}' +versions: + fpt: '*' +topics: + - Accounts + - Enterprise +--- + +## About SAML single sign-on for {% data variables.product.prodname_emus %} + +With {% data variables.product.prodname_emus %}, your enterprise uses SAML SSO to authenticate all members. Instead of signing in to {% data variables.product.prodname_dotcom %} with a {% data variables.product.prodname_dotcom %} username and password, members of your enterprise will sign in through your IdP. + +{% data variables.product.prodname_emus %} supports the following IdPs: + +{% data reusables.enterprise-accounts.emu-supported-idps %} + +After you configure SAML SSO, we recommend storing your recovery codes so you can recover access to your enterprise in the event that your identity provider is unavailable. For more information, see "[Saving your recovery codes](#saving-your-recovery-codes)." + +## Configuring SAML single sign-on for {% data variables.product.prodname_emus %} + +To configure SAML SSO for your {% data variables.product.prodname_emu_enterprise %}, you must configure an application on your IdP and then configure your enterprise on GitHub.com. After you configure SAML SSO, you can configure user provisioning. + +To install and configure the {% data variables.product.prodname_emu_idp_application %} application on your IdP, you must have a tenant and administrative access on a supported IdP. + +{% note %} + +{% data reusables.enterprise-accounts.emu-password-reset-session %} + +{% endnote %} + +1. [Configuring your identity provider](#configuring-your-identity-provider) +2. [Configuring your enterprise](#configuring-your-enterprise) +3. [Enabling provisioning](#enabling-provisioning) + +### Configuring your identity provider + +To configure your IdP, follow the instructions they provide for configuring the {% data variables.product.prodname_emu_idp_application %} application on your IdP. + +1. To install the {% data variables.product.prodname_emu_idp_application %} application, click the link for your IdP below: + + - [{% data variables.product.prodname_emu_idp_application %} application on Azure Active Directory](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/aad.githubenterprisemanageduser?tab=Overview) + - [{% data variables.product.prodname_emu_idp_application %} application on Okta](https://www.okta.com/integrations/github-enterprise-managed-user) + +1. To configure the {% data variables.product.prodname_emu_idp_application %} application and your IdP, click the link below and follow the instructions provided by your IdP: + + - [Azure Active Directory tutorial for {% data variables.product.prodname_emus %}](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-enterprise-managed-user-tutorial) + - [Okta documentation for {% data variables.product.prodname_emus %}](https://saml-doc.okta.com/SAML_Docs/How-to-Configure-SAML-2.0-for-GitHub-Enterprise-Managed-User.html) + +1. So you can test and configure your enterprise, assign yourself or the user that will be configuring SAML SSO on {% data variables.product.prodname_dotcom %} to the {% data variables.product.prodname_emu_idp_application %} application on your IdP. + +1. To enable you to continue configuring your enterprise on {% data variables.product.prodname_dotcom %}, locate and note the following information from the application you installed on your IdP: + + | Value | Other names | 설명 | + |:----------------------------------- |:------------------ |:---------------------------------------------------------------- | + | IdP Sign-On URL | Login URL, IdP URL | Application's URL on your IdP | + | IdP Identifier URL | Issuer | IdP's identifier to service providers for SAML authentication | + | Signing certificate, Base64-encoded | Public certificate | Public certificate that IdP uses to sign authentication requests | + +### Configuring your enterprise + +After you install and configure the {% data variables.product.prodname_emu_idp_application %} application on your identity provider, you can configure your enterprise. + +1. Sign into {% data variables.product.prodname_dotcom_the_website %} as the setup user for your new enterprise with the username **@SHORT-CODE_admin**. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} + +1. Under "SAML single sign-on", select **Require SAML authentication**. ![Checkbox for enabling SAML SSO](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) + +1. Under **Sign on URL**, type the HTTPS endpoint of your IdP for single sign-on requests that you noted while configuring your IdP. ![Field for the URL that members will be forwarded to when signing in](/assets/images/help/saml/saml_sign_on_url_business.png) + +1. Under **Issuer**, type your SAML issuer URL that you noted while configuring your IdP, to verify the authenticity of sent messages. ![Field for the SAML issuer's name](/assets/images/help/saml/saml_issuer.png) + +1. Under **Public Certificate**, paste the certificate that you noted while configuring your IdP, to verify SAML responses. ![Field for the public certificate from your identity provider](/assets/images/help/saml/saml_public_certificate.png) + +1. To verify the integrity of the requests from your SAML issuer, click {% octicon "pencil" aria-label="The edit icon" %}. Then, in the "Signature Method" and "Digest Method" drop-downs, choose the hashing algorithm used by your SAML issuer. ![Drop-downs for the Signature Method and Digest method hashing algorithms used by your SAML issuer](/assets/images/help/saml/saml_hashing_method.png) + +1. Before enabling SAML SSO for your enterprise, to ensure that the information you've entered is correct, click **Test SAML configuration**. ![Button to test SAML configuration before enforcing](/assets/images/help/saml/saml_test.png) + +1. Click **Save**. + + {% note %} + + **Note:** When you require SAML SSO for your enterprise, the setup user will no longer have access to the enterprise but will remain signed in to GitHub. Only {% data variables.product.prodname_managed_users %} provisioned by your IdP will have access to the enterprise. + + {% endnote %} + +1. To ensure you can still access your enterprise in the event that your identity provider is ever unavailable in the future, click **Download**, **Print**, or **Copy** to save your recovery codes. ![Button to test SAML configuration before enforcing](/assets/images/help/saml/saml_recovery_code_options.png) + +### Enabling provisioning + +After you enable SAML SSO, enable provisioning. For more information, see "[Configuring SCIM provisioning for enterprise managed users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users)." + +## Saving your recovery codes + +In the event that your identity provider is unavailable, you can use the setup user and a recovery code to sign in and access your enterprise. If you did not save your recovery codes when you configured SAML SSO, you can still access them from your enterprise's settings. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} + +1. Under "Require SAML authentication", click **Save your recovery codes**. ![Button to test SAML configuration before enforcing](/assets/images/help/enterprises/saml-recovery-codes-link.png) + +2. To save your recovery codes, click **Download**, **Print**, or **Copy**. ![Button to test SAML configuration before enforcing](/assets/images/help/saml/saml_recovery_code_options.png) diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md new file mode 100644 index 0000000000..74f7e843b7 --- /dev/null +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md @@ -0,0 +1,76 @@ +--- +title: Configuring SCIM provisioning for Enterprise Managed Users with Okta +shortTitle: Set up provisioning with Okta +intro: You can provision new users and manage their membership of your enterprise and teams using Okta as your identity provider. +product: '{% data reusables.gated-features.emus %}' +versions: + fpt: '*' +redirect_from: + - /early-access/github/articles/configuring-provisioning-for-managed-users-with-okta +topics: + - Accounts + - Enterprise +--- + +## About provisioning with Okta + +You can use {% data variables.product.prodname_emus %} with Okta as your identity provider to provision new accounts, manage enterprise membership, and manage team memberships for organizations in your enterprise. For more information about provisioning for {% data variables.product.prodname_emus %}, see "[Configuring SCIM provisioning for enterprise managed users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users)." + +Before you can configure provisioning with Okta, you must configure SAML single-sign on. For more information, see "[Configuring SAML single sign-on for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." + +To configure provisioning with Okta, you must set your enterprise's name in the {% data variables.product.prodname_emu_idp_application %} application and enter your setup user's personal access token. You can then start provisioning users in Okta. + +## Supported features + +{% data variables.product.prodname_emus %} supports many provisioning features in Okta. + +| Feature | 설명 | +| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Push New Users | Users that are assigned to the {% data variables.product.prodname_emu_idp_application %} application in Okta are automatically created in the enterprise on {% data variables.product.product_name %}. | +| Push Profile Update | Updates made to the user's profile in Okta will be pushed to {% data variables.product.product_name %}. | +| Push Groups | Groups in Okta that are assigned to the {% data variables.product.prodname_emu_idp_application %} application as Push Groups are automatically created in the enterprise on {% data variables.product.product_name %}. | +| Push User Deactivation | Unassigning the user from the {% data variables.product.prodname_emu_idp_application %} application in Okta will disable the user on {% data variables.product.product_name %}. The user will not be able to sign in, but the user's information is maintained. | +| Reactivate Users | Users in Okta whose Okta accounts are reactivated and who are assigned back to the {% data variables.product.prodname_emu_idp_application %} application will be enabled. | + +{% note %} + +**Note:** {% data variables.product.prodname_emus %} does not support modifications to usernames. + +{% endnote %} + +## Setting your enterprise name + +After your {% data variables.product.prodname_emu_enterprise %} has been created, you can begin to configure provisioning by setting your enterprise name in Okta. + +1. Navigate to your {% data variables.product.prodname_emu_idp_application %} application on Okta. +1. Click the **Sign On** tab. +1. To make changes, click **Edit**. +1. Under "Advanced Sign-on Settings", in the "Enterprise Name" text box, type your enterprise name. For example, if you access your enterprise at `https://github.com/enterprises/octoinc`, your enterprise name would be "octoinc". ![Screenshot of the Enterprise Name field on Okta](/assets/images/help/enterprises/okta-emu-enterprise-name.png) +1. To save your enterprise name, click **Save**. + +## Configuring provisioning + +After setting your enterprise name, you can proceed to configure provisioning settings. + +To configure provisioning, the setup user with the **@SHORT-CODE_admin** username will need to provide a personal access token with the **admin:enterprise** scope. For more information on creating a new token, see "[Creating a personal access token](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users#creating-a-personal-access-token)." + +1. Navigate to your {% data variables.product.prodname_emu_idp_application %} application on Okta. +1. Click the **Provisioning** tab. +1. In the settings menu, click **Integration**. +1. To make changes, click **Edit**. +1. Select **Enable API integration**. +1. In the "API Token" field, enter the personal access token with the **admin:enterprise** scope belonging to the setup user. ![Screenshot showing the API Token field on Okta](/assets/images/help/enterprises/okta-emu-token.png) +1. Click **Test API Credentials**. If the test is successful, a verification message will appear at the top of the screen. +1. To save the token, click **Save**. +1. In the settings menu, click **To App**. ![Screenshot showing the To App menu item on Okta](/assets/images/help/enterprises/okta-emu-to-app-menu.png) +1. To the right of "Provisioning to App", to allow changes to be made, click **Edit**. +1. Select **Enable** for **Create Users**, **Update User Attributes**, and **Deactivate Users**. ![Screenshot showing provisioning options on Okta](/assets/images/help/enterprises/okta-emu-provisioning-to-app.png) +1. To finish configuring provisioning, click **Save**. + +## Assigning users + +After you have configured SAML SSO and provisioning, you will be able provision new users on {% data variables.product.prodname_dotcom_the_website %} by assigning users to the {% data variables.product.prodname_emu_idp_application %} application. You can also automatically manage organization membership by assigning groups to the application as push groups and connecting the push groups to teams in your organizations. For more information about managing teams, see "[Managing team memberships with identity provider groups](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)." + +When assigning users, you can use the "Roles" attribute in the {% data variables.product.prodname_emu_idp_application %} application to set a user's role in your enterprise on {% data variables.product.product_name %}. For more information on roles, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)." + +![Screenshot showing the role options for provisioned user on Okta](/assets/images/help/enterprises/okta-emu-user-role.png) diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md new file mode 100644 index 0000000000..0fbfcb201b --- /dev/null +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md @@ -0,0 +1,54 @@ +--- +title: Configuring SCIM provisioning for Enterprise Managed Users +shortTitle: Provisioning managed users +intro: You can configure your identity provider to provision new users and manage their membership in your enterprise and teams. +product: '{% data reusables.gated-features.emus %}' +versions: + fpt: '*' +topics: + - Accounts + - Enterprise +--- + +## About provisioning for {% data variables.product.prodname_emus %} + +You can configure provisioning for {% data variables.product.prodname_emus %} to create, manage, and deactivate user accounts for your enterprise members. When you configure provisioning for {% data variables.product.prodname_emus %}, users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your identity provider are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} via SCIM, and the users are added to your enterprise. + +When you update information associated with a user's identity on your IdP, your IdP will update the user's account on GitHub.com. When you unassign the user from the {% data variables.product.prodname_emu_idp_application %} application or deactivate a user's account on your IdP, your IdP will communicate with {% data variables.product.prodname_dotcom %} to invalidate any SAML sessions and disable the member's account. The disabled account's information is maintained and their username is changed to a hash of their original username with the short code appended. If you reassign a user to the {% data variables.product.prodname_emu_idp_application %} application or reactivate their account on your IdP, the {% data variables.product.prodname_managed_user %} account on {% data variables.product.prodname_dotcom %} will be reactivated and username restored. + +Groups in your IdP can be used to manage team membership within your enterprise's organizations, allowing you to configure repository access and permissions through your IdP. For more information, see "[Managing team memberships with identity provider groups](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)." + +## 빌드전 요구 사양 + +Before you can configure provisioning for {% data variables.product.prodname_emus %}, you must configure SAML single-sign on. For more information, see "[Configuring SAML single sign-on for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." + +## Creating a personal access token + +To configure provisioning for your {% data variables.product.prodname_emu_enterprise %}, you need a personal access token with the **admin:enterprise** scope that belongs to the setup user. + +{% warning %} + +**Warning:** If the token expires or a provisioned user creates the token, SCIM provisioning may unexpectedly stop working. Make sure that you create the token while signed in as the setup user and that the token expiration is set to "No expiration". + +{% endwarning %} + +1. Sign into {% data variables.product.prodname_dotcom_the_website %} as the setup user for your new enterprise with the username **@SHORT-CODE_admin**. +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.developer_settings %} +{% data reusables.user_settings.personal_access_tokens %} +{% data reusables.user_settings.generate_new_token %} +1. Under **Note**, give your token a descriptive name. ![Screenshot showing the token's name](/assets/images/help/enterprises/emu-pat-name.png) +1. Select the **Expiration** drop-down menu, then click **No expiration**. ![Screenshot showing token expiration set to no expiration](/assets/images/help/enterprises/emu-pat-no-expiration.png) +1. Select the **admin:enterprise** scope. ![Screenshot showing the admin:enterprise scope](/assets/images/help/enterprises/enterprise-pat-scope.png) +1. Click **Generate token**. ![Generate token button](/assets/images/help/settings/generate_token.png) +1. To copy the token to your clipboard, click the {% octicon "paste" aria-label="The copy icon" %}. ![Newly created token](/assets/images/help/settings/personal_access_tokens.png) +2. To save the token for use later, store the new token securely in a password manager. + +## Configuring provisioning for {% data variables.product.prodname_emus %} + +After creating your personal access token and storing it securely, you can configure provisioning on your identity provider. + +To configure Azure Active Directory to provision users for your {% data variables.product.prodname_emu_enterprise %}, see [Tutorial: Configure GitHub Enterprise Managed User for automatic user provisioning](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-enterprise-managed-user-provisioning-tutorial) in the Azure AD documentation. + +To configure Okta to provision users for your {% data variables.product.prodname_emu_enterprise %}, see "[Configuring SCIM provisioning for Enterprise Managed Users with Okta](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users-with-okta)." + diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/index.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/index.md new file mode 100644 index 0000000000..7104779c1f --- /dev/null +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/index.md @@ -0,0 +1,19 @@ +--- +title: Managing your enterprise users with your identity provider +shortTitle: Manage users with your IdP +product: '{% data reusables.gated-features.emus %}' +intro: 'You can manage identity and access with your identity provider and provision accounts that can only contribute to your enterprise.' +versions: + fpt: '*' +topics: + - Enterprise + - Accounts +children: + - /about-enterprise-managed-users + - /configuring-saml-single-sign-on-for-enterprise-managed-users + - /configuring-scim-provisioning-for-enterprise-managed-users + - /configuring-scim-provisioning-for-enterprise-managed-users-with-okta + - /managing-team-memberships-with-identity-provider-groups + - /auditing-activity-in-your-enterprise +--- + diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups.md new file mode 100644 index 0000000000..86be52d7ce --- /dev/null +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups.md @@ -0,0 +1,67 @@ +--- +title: Managing team memberships with identity provider groups +shortTitle: Manage teams with your IdP +intro: 'You can manage team membership on {% data variables.product.product_name %} through your identity provider (IdP) by connecting IdP groups with your {% data variables.product.prodname_emu_enterprise %}.' +product: '{% data reusables.gated-features.emus %}' +versions: + fpt: '*' +topics: + - Accounts + - Enterprise +--- + +## About team management with {% data variables.product.prodname_emus %} + +With {% data variables.product.prodname_emus %}, you can manage team membership within your enterprise through your IdP. When you connect a team in one of your enterprise's organizations to an IdP group, changes to membership from the IdP group are reflected in your enterprise automatically, reducing the need for manual updates and custom scripts. + +When a change to an IdP group or a new team connection results in a {% data variables.product.prodname_managed_user %} joining a team in an organization they were not already a member of, the {% data variables.product.prodname_managed_user %} will automatically be added to the organization. Organization owners can also manage organization membership manually. When you disconnect a group from a team, users who became members of the organization via team membership are removed from the organization if they are not assigned membership in the organization by any other means. + +You can connect a team in your enterprise to one IdP group. You can assign the same IdP group to multiple teams in your enterprise. + +If you are connecting an existing team to an IdP group, you must first remove any members that were added manually. After you connect a team in your enterprise to an IdP group, your IdP administrator must make team membership changes through the identity provider. You cannot manage team membership on {% data variables.product.prodname_dotcom_the_website %}. + +When group membership changes on your IdP, your IdP sends a SCIM request with the changes to {% data variables.product.prodname_dotcom_the_website %} according to the schedule determined by your IdP, so change may not be immediate. Any requests that change team or organization membership will register in the audit log as changes made by the account used to configure user provisioning. + +Teams connected to IdP groups cannot be parents of other teams nor a child of another team. If the team you want to connect to an IdP group is a parent or child team, we recommend creating a new team or removing the nested relationships that make your team a parent team. + +To manage repository access for any team in your enterprise, including teams connected to an IdP group, you must make changes on {% data variables.product.prodname_dotcom_the_website %}. 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)". + +## Creating a new team connected to an IdP group + +Any member of an organization can create a new team and connect the team to an IdP group. + +{% data reusables.profile.access_org %} +{% data reusables.user_settings.access_org %} +{% data reusables.organizations.new_team %} +{% data reusables.organizations.team_name %} +{% data reusables.organizations.team_description %} +1. To connect a team, select the "Identity Provider Groups" drop-down menu and click the team you want to connect. ![Drop-down menu to choose identity provider groups](/assets/images/help/teams/choose-an-idp-group.png) +{% data reusables.organizations.team_visibility %} +{% data reusables.organizations.create_team %} + +## Managing the connection between an existing team and an IdP group + +Organization owners and team maintainers can manage the existing connection between an IdP group and a team. + +{% note %} + +**Note**: Before you connect an existing team on {% data variables.product.prodname_dotcom_the_website %} to an IdP group for the first time, all members of the team on {% data variables.product.prodname_dotcom_the_website %} must first be removed. For more information, see "[Removing organization members from a team](/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team)." + +{% endnote %} + +{% data reusables.profile.access_profile %} + +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +1. Optionally, under "Identity Provider Group", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="X symbol" %}. ![Unselect a connected IdP group from the GitHub team](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png) +1. To connect an IdP group, under "Identity Provider Group", select the drop-down menu, and click an identity provider group from the list. ![Drop-down menu to choose identity provider group](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png) +1. Click **Save changes**. + +## Viewing IdP groups and connected teams + +You can review a list of IdP groups, any teams connected to an IdP group, and see the membership of each IdP group on {% data variables.product.product_name %}. You must edit the membership for a group on your IdP. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.identity-provider-tab %} +1. Under "Identity Provider (IdP) Groups", review the list of IdP groups. diff --git a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account.md b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account.md index 0fda15faba..d60de68953 100644 --- a/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account.md +++ b/translations/ko-KR/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account.md @@ -42,7 +42,9 @@ You can disable all workflows for an enterprise or set a policy that configures ## Configuring required approval for workflows from public forks -{% data reusables.actions.workflow-run-approve-public-fork %} You can configure this behavior for your enterprise using the procedure below. +{% data reusables.actions.workflow-run-approve-public-fork %} + +You can configure this behavior for your enterprise using the procedure below. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} diff --git a/translations/ko-KR/content/github/site-policy/github-data-protection-agreement.md b/translations/ko-KR/content/github/site-policy/github-data-protection-agreement.md new file mode 100644 index 0000000000..09b0a4e474 --- /dev/null +++ b/translations/ko-KR/content/github/site-policy/github-data-protection-agreement.md @@ -0,0 +1,974 @@ +--- +title: GitHub Data Protection Agreement +redirect_from: + - /github/site-policy/github-data-protection-addendum + - /github/site-policy-deprecated/github-data-protection-addendum + - /github/site-policy/github-data-protection-agreement-non-enterprise-customers +versions: + fpt: '*' +--- + +## Introduction + +The parties agree that this GitHub Data Protection Agreement (“**DPA**”) sets forth their obligations with respect to the processing and security of Personal Data and, where explicitly stated in the DPA Terms, Customer Data in connection with the Online Services provided by GitHub, Inc. (“**GitHub**”). The DPA (including its Appendix and Attachments) is between GitHub and any customer receiving Online Services from GitHub based on the GitHub Customer Agreement (“**Customer**”), and is incorporated by reference into the GitHub Customer Agreement. + +In the event of any conflict or inconsistency between the DPA Terms and any other terms in the GitHub Customer Agreement, the DPA Terms will prevail. The provisions of the DPA Terms supersede any conflicting provisions of the GitHub Privacy Statement that otherwise may apply to processing of Personal Data. For clarity, the Standard Contractual Clauses prevail over any other term of the DPA Terms. + +### Applicable DPA Terms and Updates + +#### Limits on Updates + +When Customer renews or purchases a new subscription to an Online Service, the then-current DPA Terms will apply and will not change during the term of that new subscription for that Online Service. + +#### New Features, Supplements, or Related Software + +Notwithstanding the foregoing limits on updates, when GitHub introduces features, supplements or related software that are new (i.e., that were not previously included with the subscription), GitHub may provide terms or make updates to the DPA that apply to Customer’s use of those new features, supplements or related software. If those terms include any material adverse changes to the DPA Terms, GitHub will provide Customer a choice to use the new features, supplements, or related software, without loss of existing functionality of a generally available Online Service. If Customer does not use the new features, supplements, or related software, the corresponding new terms will not apply. + +#### Government Regulation and Requirements + +Notwithstanding the foregoing limits on updates, GitHub may modify or terminate an Online Service in any country or jurisdiction where there is any current or future government requirement or obligation that (1) subjects GitHub to any regulation or requirement not generally applicable to businesses operating there, (2) presents a hardship for GitHub to continue operating the Online Service without modification, and/or (3) causes GitHub to believe the DPA Terms or the Online Service may conflict with any such requirement or obligation. + +### Electronic Notices + +GitHub may provide Customer with information and notices about Online Services electronically, including via email, or through a web site that GitHub identifies. Notice is given as of the date it is made available by GitHub. + +### Prior Versions + +The DPA Terms provide terms for Online Services that are currently available. For earlier versions of the DPA Terms, Customer may contact its reseller or GitHub Account Manager. + +## 정의 + +Capitalized terms used but not defined in this DPA will have the meanings provided in the GitHub Customer Agreement. The following defined terms are used in this DPA: + +“**CCPA**” means the California Consumer Privacy Act as set forth in Cal. Civ. Code §1798.100 et seq. and its implementing regulations. + +“**Customer Data**” means all data, including all text, sound, video, or image files, and software, that are provided to GitHub by, or on behalf of, Customer through use of the Online Service. + +“**Data Protection Requirements**” means the GDPR, Local EU/EEA Data Protection Laws, CCPA, and any applicable laws, regulations, and other legal requirements relating to (a) privacy and data security; and (b) the use, collection, retention, storage, security, disclosure, transfer, disposal, and other processing of any Personal Data. + +“**Diagnostic Data**” means data collected or obtained by GitHub from software that is locally installed by Customer in connection with the Online Service. Diagnostic Data may also be referred to as telemetry. Diagnostic Data does not include Customer Data, Service Generated Data, or Professional Services Data. + +“**DPA Terms**” means both the terms in this DPA and any Online Service-specific terms in the GitHub Customer Agreement that specifically supplement or modify the privacy and security terms in this DPA for a specific Online Service (or feature of an Online Service). In the event of any conflict or inconsistency between the DPA and such Online Service-specific terms, the Online Service-specific terms shall prevail as to the applicable Online Service (or feature of that Online Service). + +“**GDPR**” means Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation). In connection with the United Kingdom, “GDPR” means Regulation (EU) 2016/679 as transposed into national law of the United Kingdom by the UK European Union (Withdrawal) Act 2018 and amended by the UK Data Protection, Privacy and Electronic Communications (Amendments etc.) (EU Exit) Regulations 2019 (as may be amended from time to time). + +“**Local EU/EEA Data Protection Laws**” means any subordinate legislation and regulation implementing the GDPR. + +“**GDPR Related Terms**” means the terms in Attachment 3, under which GitHub makes binding commitments regarding its processing of Personal Data as required by Article 28 of the GDPR. + +“**GitHub Affiliate**” means any entity that directly or indirectly controls, is controlled by or is under common control with GitHub. + +“**GitHub Customer Agreement**” means the service or other agreement(s) entered into by Customer with GitHub for Online Services. + +“**GitHub Privacy Statement**” means the GitHub privacy statement available at https://docs.github.com/en/github/site-policy/github-privacy-statement. + +“**Online Service**” means any service or software provided by GitHub to Customer under the GitHub Customer Agreement agreed upon with Customer, including Previews, updates, patches, bug fixes, and technical support. + +“**Personal Data**” means any information relating to an identified or identifiable natural person. An identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person. + +“**Preview**” means Online Services provided for preview, evaluation, demonstration or trial purposes, or pre-release versions of the Online Services. + +“**Professional Services Data**” means all data, including all text, sound, video, image files or software, that are provided to GitHub, by or on behalf of a Customer (or that Customer authorizes GitHub to obtain from an Online Service) or otherwise obtained or processed by or on behalf of GitHub through an engagement with GitHub to obtain Professional Services. Professional Services Data includes Support Data. + +“**Service Generated Data**” means data generated or derived by GitHub through the operation of an Online Service. Service Generated Data does not include Customer Data, Diagnostic Data, or Professional Services Data. + +“**Standard Contractual Clauses**” means either of the following sets of Standard Contractual Clauses, as applicable in the individual case to the transfer of personal data according to the section of this DPA entitled “Data Transfers and Location” below: +- the Standard Contractual Clauses (MODULE TWO: Transfer controller to processor), dated 4 June 2021, for the transfer of personal data to third countries pursuant to Regulation (EU) 2016/679 of the European Parliament and of the Council, as described in Article 46 of the GDPR and approved by European Commission Implementing Decision (EU) 2021/91 (“Standard Contractual Clauses (EU/EEA)”). The Standard Contractual Clauses (EU/EEA) are set forth in Attachment 1. +- the Standard Contractual Clauses (Processors), dated 5 February 2010, for the transfer of personal data to processors established in third countries which do not ensure an adequate level of data protection, as described in Article 46 of the GDPR, approved by European Commission Decision 2010/87/EU and recognized by the regulatory or supervisory authorities of the United Kingdom for use in connection with data transfers from the United Kingdom (“Standard Contractual Clauses (UK)”). The Standard Contractual Clauses (UK) are set forth in Attachment 2. + +“**Subprocessor**” means other processors used by GitHub to process Personal Data on behalf of Customer in connection with the Online Services, as described in Article 28 of the GDPR. + +“**Support Data**” means all data, including all text, sound, video, image files, or software, that are provided to GitHub by or on behalf of Customer (or that Customer authorizes GitHub to obtain from an Online Service) through an engagement with GitHub to obtain technical support for Online Services covered under this agreement. Support Data is a subset of Professional Services Data. + +Lower case terms used but not defined in this DPA, such as “personal data breach”, “processing”, “controller”, “processor”, “profiling”, “personal data”, and “data subject” will have the same meaning as set forth in Article 4 of the GDPR, irrespective of whether GDPR applies. The terms “data importer” and “data exporter” have the meanings given in the Standard Contractual Clauses. + +For clarity, and as detailed above, data defined as Customer Data, Diagnostic Data, Service Generated Data, and Professional Services Data may contain Personal Data. For illustrative purposes, please see the chart inserted below: + +
    + personal_data_types +
    + +Above is a visual representation of the data types defined in the DPA. All Personal Data is processed as a part of one of the other data types (all of which also include non-personal data). Support Data is a sub-set of Professional Services Data. Except where explicitly stated otherwise, the DPA Terms exclusively apply to Personal Data. + +## General Terms + +### Compliance with Laws + +GitHub will comply with all laws and regulations applicable to its provision of the Online Services, including security breach notification law and Data Protection Requirements. However, GitHub is not responsible for compliance with any laws or regulations applicable to Customer or Customer’s industry that are not generally applicable to information technology service providers. GitHub does not determine whether Customer Data includes information subject to any specific law or regulation. All Security Incidents are subject to the Security Incident Notification terms below. + +Customer must comply with all laws and regulations applicable to its use of Online Services, including laws related to biometric data, confidentiality of communications, and Data Protection Requirements. Customer is responsible for determining whether the Online Services are appropriate for storage and processing of information subject to any specific law or regulation and for using the Online Services in a manner consistent with Customer’s legal and regulatory obligations. Customer is responsible for responding to any request from a third party regarding Customer’s use of an Online Service, such as a request to take down content under the U.S. Digital Millennium Copyright Act or other applicable laws. + +## Data Protection + +Terms This section of the DPA includes the following subsections: +- 범위 +- Nature of Data Processing; Ownership +- Disclosure of Processed Data +- Processing of Personal Data; GDPR +- Data Security +- Security Incident Notification +- Data Transfers and Location +- Data Retention and Deletion +- Processor Confidentiality Commitment +- Notice and Controls on Use of Subprocessors +- Educational Institutions +- CJIS Customer Agreement, HIPAA Business Associate, Biometric Data +- California Consumer Privacy Act (CCPA) +- How to Contact GitHub +- Appendix A – Security Measures + +### 범위 + +The DPA Terms apply to all Online Services. + +Previews may employ lesser or different privacy and security measures than those typically present in the Online Services. Unless otherwise noted, Customer should not use Previews to process Personal Data or other data that is subject to legal or regulatory compliance requirements. The following terms in this DPA do not apply to Previews: Processing of Personal Data; GDPR, Data Security, and California Consumer Privacy Act. + +### Nature of Data Processing; Ownership + +Except as otherwise stated in the DPA Terms, GitHub will use and otherwise process Customer Data and Personal Data as described and subject to the limitations provided below (a) to provide Customer the Online Service in accordance with Customer’s documented instructions, and/or (b) for GitHub’s legitimate business operations incident to delivery of the Online Services to Customer. As between the parties, Customer retains all right, title and interest in and to Customer Data. GitHub acquires no rights in Customer Data other than the rights Customer grants to GitHub in this section. This paragraph does not affect GitHub’s rights in software or services GitHub licenses to Customer. + +#### Processing to Provide Customer the Online Services + +For purposes of this DPA, “to provide” an Online Service consists of: +- Delivering functional capabilities as licensed, configured, and used by Customer and its users, including providing personalized user experiences; +- Troubleshooting (e.g., preventing, detecting, and repairing problems); and +- Ongoing improvement (e.g., installing the latest updates and making improvements to user productivity, reliability, efficacy, and security). + +When providing Online Services, GitHub will use or otherwise process Personal Data only on Customer’s behalf and in accordance with Customer’s documented instructions. + +#### Processing for GitHub’s Legitimate Business Operations + +For purposes of this DPA, “GitHub’s legitimate business operations” consist of the following, each as incident to delivery of the Online Services to Customer: (1) billing and account management; (2) compensation (e.g., calculating employee commissions and partner incentives); (3) internal reporting and business modeling (e.g., forecasting, revenue, capacity planning, product strategy); (4) combatting fraud, abuse, cybercrime, or cyber-attacks that may affect GitHub or Online Services; (5) improving the core functionality of accessibility, privacy or energy-efficiency; (6) financial reporting and compliance with legal obligations (subject to the limitations on disclosure of Processed Data outlined below); (7) the creation or management of end user accounts and profiles by GitHub for individual users of Customer (except where Customer creates, manages or otherwise controls such end user accounts or profiles itself); and (8) other purposes pertaining to Personal Data not provided by Customer for storage in GitHub repositories or in connection with Professional Services. + +When processing for GitHub’s legitimate business operations, GitHub will not use or otherwise process Personal Data for: (a) user profiling, (b) advertising or similar commercial purposes, (c) data selling or brokering, or (d) any other purpose, other than for the purposes set out in this section. + +### Disclosure of Processed Data + +GitHub will not disclose or provide access to any Processed Data except: (1) as Customer directs; (2) as described in this DPA; or (3) as required by law. For purposes of this section, “Processed Data” means: (a) Customer Data; (b) Personal Data and (c) any other data processed by GitHub in connection with the Online Service that is Customer’s confidential information under the GitHub Customer Agreement. All processing of Processed Data is subject to GitHub’s obligation of confidentiality under the GitHub Customer Agreement. + +GitHub will not disclose or provide access to any Processed Data to law enforcement unless required by law. If law enforcement contacts GitHub with a demand for Processed Data, GitHub will attempt to redirect the law enforcement agency to request that data directly from Customer. If compelled to disclose or provide access to any Processed Data to law enforcement, GitHub will promptly notify Customer and provide a copy of the demand, unless legally prohibited from doing so. + +Upon receipt of any other third-party request for Processed Data, GitHub will promptly notify Customer unless prohibited by law. GitHub will reject the request unless required by law to comply. If the request is valid, GitHub will attempt to redirect the third party to request the data directly from Customer. + +GitHub will not provide any third party: (a) direct, indirect, blanket, or unfettered access to Processed Data; (b) platform encryption keys used to secure Processed Data or the ability to break such encryption; or (c) access to Processed Data if GitHub is aware that the data is to be used for purposes other than those stated in the third party’s request. + +In support of the above, GitHub may provide Customer’s basic contact information to the third party. + +### Processing of Personal Data; GDPR + +All Personal Data processed by GitHub in connection with the Online Services is obtained as part of either Customer Data, Professional Services Data (including Support Data), Diagnostic Data, or Service Generated Data. Personal Data provided to GitHub by, or on behalf of, Customer through use of the Online Service is also Customer Data. Pseudonymized identifiers may be included in Diagnostic Data or Service Generated Data and are also Personal Data. Any Personal Data pseudonymized, or de-identified but not anonymized, or Personal Data derived from Personal Data is also Personal Data. + +To the extent GitHub is a processor or subprocessor of Personal Data subject to the GDPR, the GDPR Related Terms in Attachment 3 govern that processing and the parties also agree to the following terms in this sub-section (“Processing of Personal Data; GDPR”): + +#### Processor and Controller Roles and Responsibilities + +Customer and GitHub agree that Customer is the controller of Personal Data and GitHub is the processor of such data, except (a) when Customer acts as a processor of Personal Data, in which case GitHub is a subprocessor; or (b) as stated otherwise in the GitHub Customer Agreement or this DPA. When GitHub acts as the processor or subprocessor of Personal Data, it will process Personal Data only on Customer’s behalf and in accordance with documented instructions from Customer. Customer agrees that its GitHub Customer Agreement (including the DPA Terms and any applicable updates), along with the product documentation and Customer’s use and configuration of features in the Online Services, are Customer’s complete documented instructions to GitHub for the processing of Personal Data. Information on use and configuration of the Online Services can be found at https://docs.github.com or a successor location. Any additional or alternate instructions must be agreed to according to the process for amending Customer’s GitHub Customer Agreement. In any instance where the GDPR applies and Customer is a processor, Customer warrants to GitHub that Customer’s instructions, including appointment of GitHub as a processor or subprocessor, have been authorized by the relevant controller. + +To the extent GitHub uses or otherwise processes Personal Data subject to the GDPR for GitHub’s legitimate business operations incident to delivery of the Online Services to Customer, GitHub will comply with the obligations of an independent data controller under GDPR for such use. GitHub is accepting the added responsibilities of a data “controller” under the GDPR for processing in connection with its legitimate business operations to: (a) act consistent with regulatory requirements, to the extent required under the GDPR; and (b) provide increased transparency to Customers and confirm GitHub’s accountability for such processing. GitHub employs safeguards to protect Personal Data in processing, including those identified in this DPA and those contemplated in Article 6(4) of the GDPR. With respect to processing of Personal Data under this paragraph, GitHub makes the commitments set forth in the Standard Contractual Clauses set forth in Attachment 1 or Attachment 2 (as applicable); for those purposes, (i) any GitHub disclosure of Personal Data, as described in Annex III to Attachment 1 or Appendix 3 to Attachment 2 (as applicable), that has been transferred in connection with GitHub’s legitimate business operations is deemed a “Relevant Disclosure” and (ii) the commitments in Annex III to Attachment 1 or Appendix 3 to Attachment 2 (as applicable) apply to such Personal Data. + +#### Processing Details + +The parties acknowledge and agree that: + +- **Subject Matter**. The subject-matter of the processing is limited to Personal Data within the scope of the section of this DPA entitled “Nature of Data Processing; Ownership” above and the GDPR. +- **Duration of the Processing**. The duration of the processing shall be in accordance with Customer instructions and the terms of the DPA. +- **Nature and Purpose of the Processing**. The nature and purpose of the processing shall be to provide the Online Service pursuant to Customer’s GitHub Customer Agreement and for GitHub’s legitimate business operations incident to delivery of the Online Service to Customer (as further described in the section of this DPA entitled “Nature of Data Processing; Ownership” above). +- **Categories of Data**. The types of Personal Data processed by GitHub when providing the Online Service include: (i) Personal Data that Customer elects to include in Customer Data or Professional Services Data (including, without limitation, Support Data); and (ii) those expressly identified in Article 4 of the GDPR that may be contained in Diagnostic Data or Service Generated Data. The types of Personal Data that Customer elects to include in Customer Data or Professional Services Data (including, without limitation, Support Data) may be any categories of Personal Data identified in records maintained by Customer acting as controller pursuant to Article 30 of the GDPR, including the categories of Personal Data set forth in Annex I to Attachment 1 or Appendix 1 to Attachment 2 (as applicable). +- Data Subjects. The categories of data subjects are Customer’s representatives and end users, such as employees, contractors, collaborators, and customers, and may include any other categories of data subjects as identified in records maintained by Customer acting as controller pursuant to Article 30 of the GDPR, including the categories of data subjects set forth in Annex I to Attachment 1 or Appendix 1 to Attachment 2 (as applicable). + +#### Data Subject Rights; Assistance with Requests + +GitHub will make available to Customer, in a manner consistent with the functionality of the Online Service and GitHub’s role as a processor of Personal Data of data subjects, the ability to fulfill data subject requests to exercise their rights under the GDPR. If GitHub receives a request from Customer’s data subject to exercise one or more of its rights under the GDPR in connection with an Online Service for which GitHub is a data processor or subprocessor, GitHub will redirect the data subject to make its request directly to Customer. Customer will be responsible for responding to any such request including, where necessary, by using the functionality of the Online Service. GitHub shall comply with reasonable requests by Customer to assist with Customer’s response to such a data subject request. + +#### Records of Processing Activities + +To the extent the GDPR requires GitHub to collect and maintain records of certain information relating to Customer, Customer will, where requested, supply such information to GitHub and keep it accurate and up-to-date. GitHub may make any such information available to the supervisory authority if required by the GDPR. + +### Data Security + +GitHub will implement and maintain appropriate technical and organizational measures and security safeguards against accidental or unlawful destruction, or loss, alteration, unauthorized disclosure of or access to, Customer Data and Personal Data processed by GitHub on behalf and in accordance with the documented instructions of Customer in connection with the Online Services. GitHub will regularly monitor compliance with these measures and safeguards and will continue to take appropriate steps throughout the term of the GitHub Customer Agreement. Appendix A – Security Safeguards contains a description of the technical and organizational measures and security safeguards implemented by GitHub. + +Customer is solely responsible for making an independent determination as to whether the technical and organizational measures and security safeguards for an Online Service meet Customer’s requirements, including any of its security obligations under applicable Data Protection Requirements. Customer acknowledges and agrees that (taking into account the state of the art, the costs of implementation, and the nature, scope, context and purposes of the processing of its Customer Data and Personal Data as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons) the technical and organizational measures and security safeguards implemented and maintained by GitHub provide a level of security appropriate to the risk with respect to its Customer Data and Personal Data. Customer is responsible for implementing and maintaining privacy protections and security measures for components that Customer provides or controls. + +GitHub will provide security compliance reporting such as external SOC1, type 2 and SOC2, type2 audit reports upon Customer request. Customer agrees that any information and audit rights granted by the applicable Data Protection Requirements (including, where applicable, Article 28(3)(h) of the GDPR) will be satisfied by these compliance reports, and will otherwise only arise to the extent that GitHub's provision of a compliance report does not provide sufficient information, or to the extent that Customer must respond to a regulatory or supervisory authority audit or investigation. + +Should Customer be subject to a regulatory or supervisory authority audit or investigation or carry out an audit or investigation in response to a request by a regulatory or supervisory authority that requires participation from GitHub, and Customers’ obligations cannot reasonably be satisfied (where allowable by Customer’s regulators) through audit reports, documentation, or compliance information that GitHub makes generally available to its customers, then GitHub will promptly respond to Customer’s additional instructions and requests for information, in accordance with the following terms and conditions: + +- GitHub will provide access to relevant knowledgeable personnel, documentation, and application software. +- Customer and GitHub will mutually agree in a prior written agreement (email is acceptable) upon the scope, timing, duration, control and evidence requirements, provided that this requirement to agree will not permit GitHub to unreasonably delay its cooperation. +- Customer must ensure its regulator’s use of an independent, accredited third-party audit firm, during regular business hours, with reasonable advance written notice to GitHub, and subject to reasonable confidentiality procedures. Neither Customer, its regulators, nor its regulators’ delegates shall have access to any data from GitHub’s other customers or to GitHub systems or facilities not involved in the Online Services. +- Customer is responsible for all costs and fees related to GitHub’s cooperation with the regulatory audit of Customer, including all reasonable costs and fees for any and all time GitHub expends, in addition to the rates for services performed by GitHub. +- If the report generated from GitHub’s cooperation with the regulatory audit of Customer includes any findings pertaining to GitHub, Customer will share such report, findings, and recommended actions with GitHub where allowed by Customer’s regulators. + +### Security Incident Notification + +If GitHub becomes aware of a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Customer Data or Personal Data processed by GitHub on behalf and in accordance with the documented instructions of Customer in connection with the Online Services (each a "Security Incident"), GitHub will promptly and without undue delay (1) notify Customer of the Security Incident; (2) investigate the Security Incident and provide Customer with detailed information about the Security Incident; (3) take reasonable steps to mitigate the effects and to minimize any damage resulting from the Security Incident. + +Notification(s) of Security Incidents will be delivered to one or more of Customer's administrators by any means GitHub selects, including via email. It is Customer's sole responsibility to ensure it maintains accurate contact information with GitHub and that Customer's administrators monitor for and respond to any notifications. Customer is solely responsible for complying with its obligations under incident notification laws applicable to Customer and fulfilling any third-party notification obligations related to any Security Incident. + +GitHub will make reasonable efforts to assist Customer in fulfilling Customer's obligation under GDPR Article 33 or other applicable law or regulations to notify the relevant regulatory or supervisory authority and individual data subjects about a Security Incident. + +GitHub’s notification of or response to a Security Incident under this section is not an acknowledgement by GitHub of any fault or liability with respect to the Security Incident. + +Customer must notify GitHub promptly about any possible misuse of its accounts or authentication credentials or any Security Incident related to an Online Service. + +### Data Transfers and Location + +Personal Data that GitHub processes on behalf and in accordance with the documented instructions of Customer in connection with the Online Services may not be transferred to, or stored and processed in a geographic location except in accordance with the DPA Terms and the safeguards provided below in this section. Taking into account such safeguards, Customer appoints GitHub to transfer Personal Data to the United States or any other country in which GitHub or its Subprocessors operate and to store and process Personal Data to provide the Online Services, except as may be described elsewhere in these DPA Terms. + +All transfers of Personal Data out of the European Union, European Economic Area, or Switzerland to provide the Online Services shall be governed by the Standard Contractual Clauses (EU/EEA) in Attachment 1. All transfers of Personal Data out of the United Kingdom to provide the Online Services shall be governed by the Standard Contractual Clauses (UK) in Attachment 2. For the purposes of the Standard Contractual Clauses (UK) in Attachment 2, references to the “European Union,” “EU,” “European Economic Area,” “EEA” or a “Member State” shall be interpreted to refer to the United Kingdom where reasonably necessary and appropriate to give full force and effect to the Standard Contractual Clauses (UK) with respect to transfers of Personal Data from the United Kingdom. This applies regardless of the fact that, effective January 31, 2020, the United Kingdom is no longer a Member State of the European Union or European Economic Area. + +GitHub will abide by the requirements of applicable European Union, European Economic Area, United Kingdom and Swiss data protection law, and other Data Protection Requirements, in each case regarding the transfer of Personal Data to recipients or jurisdictions outside such jurisdiction. All such transfers of Personal Data will, where applicable, be subject to appropriate safeguards as described in Article 46 of the GDPR and such transfers and safeguards will be documented according to Article 30(2) of the GDPR. + +Subject to the safeguards described above, GitHub may transfer, store and otherwise process Personal Data to or in jurisdictions and geographic locations worldwide as it, subject to its sole discretion, considers reasonably necessary in connection with the Online Services. + +### Data Retention and Deletion + +Upon Customer's reasonable request, unless prohibited by law, GitHub will return or destroy all Customer Data and Personal Data processed by GitHub on behalf and in accordance with the documented instructions of Customer in connection with the Online Services at all locations where it is stored within 30 days of the request, provided that it is no longer needed for providing the Online Services or the purposes for which a data subject had authorized the processing of their Personal Data. GitHub may retain Customer Data or Personal Data to the extent required by the applicable Data Protection Requirements or other applicable law, and only to the extent and for such period as required by the applicable Data Protection Requirements or other applicable law, provided that GitHub will ensure that the Customer Data or Personal Data is processed only as necessary for the purpose specified in the applicable Data Protection Requirements or other applicable law and no other purpose, and the Customer Data or Personal Data remains protected by the Applicable Data Protection Requirements or other applicable law. + +### Processor Confidentiality Commitment + +GitHub will ensure that its personnel engaged in the processing of Customer Data and Personal Data on behalf of Customer in connection with the Online Services (i) will process such data only on instructions from Customer or as described in this DPA, and (ii) will be obligated to maintain the confidentiality and security of such data even after their engagement ends. GitHub shall provide periodic and mandatory data privacy and security training and awareness to its employees with access to Customer Data and Personal Data in accordance with applicable Data Protection Requirements or other applicable law and industry standards. + +### Notice and Controls on Use of Subprocessors + +GitHub may hire Subprocessors to provide certain limited or ancillary services on its behalf. Customer consents to this engagement and to GitHub Affiliates as Subprocessors. The above authorizations will constitute Customer’s prior written consent to the subcontracting by GitHub of the processing of Personal Data if such consent is required under applicable law, the Standard Contractual Clauses or the GDPR Related Terms. + +GitHub is responsible for its Subprocessors’ compliance with GitHub’s obligations in this DPA. GitHub makes available information about Subprocessors on the GitHub website https://github.com/subprocessors (or a successor location). When engaging any Subprocessor, GitHub will ensure via a written contract that the Subprocessor may access and use Customer Data or Personal Data only to deliver the services GitHub has retained them to provide and is prohibited from using Customer Data or Personal Data for any other purpose. GitHub will ensure that Subprocessors are bound by written agreements that require them to provide at least the level of data protection required of GitHub by the DPA, including the limitations on disclosure of Personal Data. GitHub agrees to oversee the Subprocessors to ensure that these contractual obligations are met. + +From time to time, GitHub may engage new Subprocessors. GitHub will give Customer notice (by updating the website at https://github.com/github-subprocessors-list (or a successor location) and providing Customer with a mechanism to obtain notice of that update) of any new Subprocessor in advance of providing that Subprocessor with access to Customer Data. If GitHub engages a new Subprocessor for a new Online Service, GitHub will give Customer notice prior to availability of that Online Service. + +If Customer does not approve of a new Subprocessor, then Customer may terminate any subscription for the affected Online Service without penalty by providing, before the end of the relevant notice period, written notice of termination. Customer may also include an explanation of the grounds for non-approval together with the termination notice, in order to permit GitHub to re-evaluate any such new Subprocessor based on the applicable concerns. If the affected Online Service is part of a suite (or similar single purchase of services), then any termination will apply to the entire suite. After termination, GitHub will remove payment obligations for any subscriptions for the terminated Online Service from subsequent invoices to Customer or its reseller. + +### Educational Institutions +If Customer is an educational agency or institution subject to the regulations under the Family Educational Rights and Privacy Act, 20 U.S.C. § 1232g (FERPA), or similar state student or educational privacy laws (collectively “Educational Privacy Laws”), Customer shall not provide Personal Data covered by such Educational Privacy Laws to GitHub without obtaining GitHub’s prior, written and specific consent and entering into a separate agreement with GitHub governing the parties’ rights and obligations with respect to the processing of such Personal Data by GitHub in connection with the Online Services. + +Subject to the above, if Customer intends to provide to GitHub Personal Data covered by FERPA, the parties agree and acknowledge that, for the purposes of this DPA, GitHub is a “school official” with “legitimate educational interests” in the Personal Data, as those terms have been defined under FERPA and its implementing regulations. Customer understands that GitHub may possess limited or no contact information for Customer’s students and students’ parents. Consequently, Customer will be responsible for obtaining any student or parental consent for any end user’s use of the Online Services that may be required by applicable law and to convey notification on behalf of GitHub to students (or, with respect to a student under 18 years of age and not in attendance at a postsecondary institution, to the student’s parent) of any judicial order or lawfully-issued subpoena requiring the disclosure of Personal Data in GitHub’s possession as may be required under applicable law. + +### CJIS Customer Agreement, HIPAA Business Associate, Biometric Data + +Except with GitHub’s prior, written and specific consent, Customer shall not provide to GitHub any Personal Data + +- relating to criminal convictions and offenses or Personal Data collected or otherwise processed by Customer subject to or in connection with FBI Criminal Justice Information Services or the related Security Policy. +- constituting protected health information governed by the privacy, security, and breach notification rules issued by the United States Department of Health and Human Services, Parts 160 and 164 of Title 45 of the Code of Federal Regulations, established pursuant to the Health Insurance Portability and Accountability Act of 1996 (Public Law 104-191) or by state health or medical privacy laws. +- collected as part of a clinical trial or other biomedical research study subject to, or conducted in accordance with, the Federal Policy for the Protection of Human Subjects (Common Rule). +- covered by state, federal or foreign biometric privacy laws or otherwise constituting biometric information including information on an individual’s physical, physiological, biological or behavioral characteristics or information derived from such information that is used or intended to be used, singly or in combination with each other or with other information, to establish individual identity. + +### California Consumer Privacy Act (CCPA) / California Privacy Rights Act (CPRA) + +If and to the extent GitHub is processing Personal Data on behalf and in accordance with the documented instructions of Customer within the scope of the CCPA, GitHub makes the following additional commitments to Customer. GitHub will process the Personal Data on behalf of Customer and will not + +- sell the Personal Data as the term “selling” is defined in the CCPA. - share, rent, release, disclose, disseminate, make available, transfer or otherwise communicate orally, in writing or by electronic or other means, the Personal Data to a third party for cross-context behavioral advertising, whether or not for monetary or other valuable consideration, including transactions for cross-context behavioral advertising in which no money is exchanged. +- retain, use or disclose the Personal Data for any purpose other than for the business purposes specified in the DPA Terms and the GitHub Customer Agreement, including retaining, using or disclosing the Personal Data for a commercial purpose other than the business purposes specified in the DPA Terms or the GitHub Customer Agreement, or as otherwise permitted by the CCPA. +- retain, use or disclose the Personal Data outside of the direct business relationship with Customer. +- combine the Personal Data with personal information that it receives from or on behalf of a third party or collects from California residents, except that GitHub may combine Personal Data to perform any business purpose as permitted by the CCPA or any regulations adopted or issued under the CCPA. + +### How to Contact GitHub + +If Customer believes that GitHub is not adhering to its privacy or security commitments, Customer may contact customer support or use GitHub’s Privacy web form, located at https://support.github.com/contact/privacy. GitHub’s mailing address is: + +**GitHub Privacy**
    GitHub, Inc.
    88 Colin P. Kelly Jr. Street
    San Francisco, California 94107 USA
    + +GitHub B.V. is GitHub’s data protection representative for the European Economic Area. The privacy representative of GitHub B.V. can be reached at the following address: + +**GitHub B.V.**
    Vijzelstraat 68-72
    1017 HL Amsterdam
    The Netherlands
    + +

    Appendix A – Security Safeguards

    + +GitHub has implemented and will maintain for Customer Data and Personal Data processed by GitHub on behalf and in accordance with the documented instructions of Customer in connection with GitHub services the following technical and organizational measures and security safeguards, which in conjunction with the security commitments in this DPA (including the GDPR Related Terms), are GitHub’s only responsibility with respect to the security of that data: + +| Domain | Practices | +| ---------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Organization of Information Security | **Security Ownership**. GitHub has appointed one or more security officers responsible for coordinating and monitoring the security policies and procedures.

    **Security Roles and Responsibilities**. GitHub personnel with access to Customer Data and Personal Data are subject to confidentiality obligations.

    **Risk Management Program**. GitHub performs an annual risk assessment.
    GitHub retains its security documents pursuant to its retention requirements after they are no longer in effect.

    **Vendor Management**. GitHub has a vendor risk assessment process, vendor contract clauses and additional data protection agreements with vendors. | +| Asset Management | **Asset Inventory**. GitHub maintains an inventory of all media on which Customer Data and Personal Data is stored. Access to the inventories of such media is restricted to GitHub personnel authorized to have such access.

    **Asset Handling**
    - GitHub classifies Customer Data and Personal Data to help identify it and to allow for access to it to be appropriately restricted.
    - GitHub communicates employee responsibility and accountability for data protection up to and including cause for termination.
    GitHub personnel must obtain GitHub authorization prior to remotely accessing Customer Data and Personal Data or processing Customer Data and Personal Data outside GitHub’s facilities. | +| Human Resources Security | **Security Training**. GitHub requires all new hires to complete security and privacy awareness training as part of initial on-boarding. Participation in annual training is required for all employees to provide a baseline for security and privacy basics. | +| Physical and Environmental Security | **Physical Access to Facilities**. GitHub limits access to facilities where information systems that process Customer Data and Personal Data are located to identified authorized individuals.

    **Physical Access to Components**. GitHub maintains records of the incoming and outgoing media containing Customer Data, including the kind of media, the authorized sender/recipients, date and time, the number of media and the types of Customer Data and Personal Data they contain.

    **Protection from Disruptions**. GitHub uses a variety of industry standard systems to protect against loss of data due to power supply failure or line interference.

    **Component Disposal**. GitHub uses industry standard processes to delete Customer Data and Personal Data when it is no longer needed. | +| Communications and Operations Management | **Operational Policy**. GitHub maintains security documents describing its security measures and the relevant procedures and responsibilities of its personnel who have access to Customer Data.

    **Data Recovery Procedures**
    - On an ongoing basis, but in no case less frequently than once a week (unless no Customer Data and Personal Data has been updated during that period), GitHub maintains multiple copies of Customer Data and Personal Data from which Customer Data and Personal Data can be recovered.
    - GitHub stores copies of Customer Data and Personal Data and data recovery procedures in a different place from where the primary computer equipment processing the Customer Data and Personal Data is located.
    - GitHub has specific procedures in place governing access to copies of Customer Data.
    - GitHub logs data restoration efforts, including the person responsible, the description of the restored data and where applicable, the person responsible and which data (if any) had to be input manually in the data recovery process.

    **Malicious Software**. GitHub has threat detection controls to help identify and respond to anomalous or suspicious access to Customer Data, including malicious software originating from public networks.

    **Data Beyond Boundaries**
    - GitHub encrypts, or enables Customer to encrypt, Customer Data and Personal Data that is transmitted over public networks.
    - GitHub restricts access to Customer Data and Personal Data in media leaving its facilities.

    **Event Logging**. GitHub logs, or enables Customer to log, access and use of information systems containing Customer Data, registering the access ID, time, authorization granted or denied, and relevant activity. | +| Access Control | **Access Policy**. GitHub maintains a record of security privileges of individuals having access to Customer Data.

    **Access Authorization**
    - GitHub maintains and updates a record of personnel authorized to access GitHub systems that contain Customer Data.
    - GitHub identifies those personnel who may grant, alter or cancel authorized access to data and resources.
    - GitHub ensures that where more than one individual has access to systems containing Customer Data, the individuals have separate identifiers/log-ins where technically and architecturally feasible, and commercially reasonable.

    **Least Privilege**
    - Technical support personnel are only permitted to have access to Customer Data and Personal Data when needed.
    - GitHub restricts access to Customer Data and Personal Data to only those individuals who require such access to perform their job function. GitHub employees are only granted access to production systems based on their role within the organization.

    **Integrity and Confidentiality**

    - GitHub instructs GitHub personnel to disable administrative sessions when computers are left unattended.
    - GitHub stores passwords such that they are encrypted or unintelligible while they are in force.

    **Authentication**
    - GitHub uses industry standard practices to identify and authenticate users who attempt to access information systems.
    - Where authentication mechanisms are based solely on passwords, GitHub requires the password to be at least eight characters long.
    - GitHub ensures that de-activated or expired employee identifiers are not granted to other individuals.
    - GitHub monitors, or enables Customer to monitor, repeated attempts to gain access to the information system using an invalid password.
    - GitHub maintains industry standard procedures to deactivate passwords that have been corrupted or inadvertently disclosed.
    - GitHub uses industry standard password protection practices, including practices designed to maintain the confidentiality and integrity of passwords when they are assigned and distributed, and during storage.

    **Network Design**. GitHub has controls to ensure no systems storing Customer Data and Personal Data are part of the same logical network used for GitHub business operations. | +| Information Security Incident Management | **Incident Response Process**
    - GitHub maintains a record of security incidents with a description of the incidents, the time period, the consequences of the breach, the name of the reporter, and to whom the incident was reported, and details regarding the handling of the incident.
    - In the event that GitHub Security confirms or reasonably suspects that a GitHub.com customer is affected by a data breach, we will notify the customer without undue delay
    - GitHub tracks, or enables Customer to track, disclosures of Customer Data, including what data has been disclosed, to whom, and at what time.

    **Service Monitoring**. GitHub employs a wide range of continuous monitoring solutions for preventing, detecting, and mitigating attacks to the site. | +| Business Continuity Management | - GitHub maintains emergency and contingency plans for the facilities in which GitHub information systems that process Customer Data and Personal Data are located.
    - GitHub’s redundant storage and its procedures for recovering data are designed to attempt to reconstruct Customer Data and Personal Data in its original or last-replicated state from before the time it was lost or destroyed. | + +

    Attachment 1 - The Standard Contractual Clauses (EU/EEA)

    + +### Controller to Processor + +#### SECTION I + +##### Clause 1 + +**Purpose and scope** + +
      +
    1. The purpose of these standard contractual clauses is to ensure compliance with the requirements of Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data (General Data Protection Regulation) for the transfer of personal data to a third country.
      2. +
    2. The Parties: +
        +
      1. the natural or legal person(s), public authority/ies, agency/ies or other body/ies (hereinafter ‘entity/ies’) transferring the personal data, as listed in Annex I.A (hereinafter each ‘data exporter’), and
        2. +
      2. the entity/ies in a third country receiving the personal data from the data exporter, directly or indirectly via another entity also Party to these Clauses, as listed in Annex I.A (hereinafter each ‘data importer’)
        3. +
      + have agreed to these standard contractual clauses (hereinafter: ‘Clauses’).
      3. +
    3. These Clauses apply with respect to the transfer of personal data as specified in Annex I.B.
      4. +
    4. The Appendix to these Clauses containing the Annexes referred to therein forms an integral part of these Clauses.
      5. +
    + +##### Clause 2 + +**Effect and invariability of the Clauses** +
      +
    1. These Clauses set out appropriate safeguards, including enforceable data subject rights and effective legal remedies, pursuant to Article 46(1) and Article 46(2)(c) of Regulation (EU) 2016/679 and, with respect to data transfers from controllers to processors and/or processors to processors, standard contractual clauses pursuant to Article 28(7) of Regulation (EU) 2016/679, provided they are not modified, except to select the appropriate Module(s) or to add or update information in the Appendix. This does not prevent the Parties from including the standard contractual clauses laid down in these Clauses in a wider contract and/or to add other clauses or additional safeguards, provided that they do not contradict, directly or indirectly, these Clauses or prejudice the fundamental rights or freedoms of data subjects.
      2. +
    2. These Clauses are without prejudice to obligations to which the data exporter is subject by virtue of Regulation (EU) 2016/679.
      3. +
    + +##### Clause 3 + +**Third-party beneficiaries** + +
      +
    1. Data subjects may invoke and enforce these Clauses, as third-party beneficiaries, against the data exporter and/or data importer, with the following exceptions:
      2. +
        +
      1. Clause 1, Clause 2, Clause 3, Clause 6, Clause 7;
        2. +
      2. Clause 8.1(b), 8.9(a), (c), (d) and (e);
        3. +
      3. Clause 9(a), (c), (d) and (e);
        4. +
      4. Clause 12(a), (d) and (f);
        5. +
      5. Clause 13;
        6. +
      6. Clause 15.1(c), (d) and (e);
        7. +
      7. Clause 16(e);
        8. +
      8. Clause 18(a) and (b).
        9. +
      +
    2. Paragraph (a) is without prejudice to rights of data subjects under Regulation (EU) 2016/679.
      3. +
    + +##### Clause 4 + +**Interpretation** + +
      +
    1. Where these Clauses use terms that are defined in Regulation (EU) 2016/679, those terms shall have the same meaning as in that Regulation.
      2. +
    2. These Clauses shall be read and interpreted in the light of the provisions of Regulation (EU) 2016/679.
      3. +
    3. These Clauses shall not be interpreted in a way that conflicts with rights and obligations provided for in Regulation (EU) 2016/679.
      4. +
    + +##### Clause 5 + +**Hierarchy** + +In the event of a contradiction between these Clauses and the provisions of related agreements between the Parties, existing at the time these Clauses are agreed or entered into thereafter, these Clauses shall prevail. + +##### Clause 6 + +**Description of the transfer(s)** + +The details of the transfer(s), and in particular the categories of personal data that are transferred and the purpose(s) for which they are transferred, are specified in Annex I.B. + +##### Clause 7 + +**Docking clause** + +
      +
    1. An entity that is not a Party to these Clauses may, with the agreement of the Parties, accede to these Clauses at any time, either as a data exporter or as a data importer, by completing the Appendix and signing Annex I.A.
      2. +
    2. Once it has completed the Appendix and signed Annex I.A, the acceding entity shall become a Party to these Clauses and have the rights and obligations of a data exporter or data importer in accordance with its designation in Annex I.A.
      3. +
    3. The acceding entity shall have no rights or obligations arising under these Clauses from the period prior to becoming a Party.
      4. +
    + +#### SECTION II – OBLIGATIONS OF THE PARTIES + +##### Clause 8 + +**Data protection safeguards** + +The data exporter warrants that it has used reasonable efforts to determine that the data importer is able, through the implementation of appropriate technical and organisational measures, to satisfy its obligations under these Clauses. + +**8.1 Instructions**
      +
    1. The data importer shall process the personal data only on documented instructions from the data exporter. The data exporter may give such instructions throughout the duration of the contract.
      2. +
    2. The data importer shall immediately inform the data exporter if it is unable to follow those instructions.
      3. +
    + +**8.2 Purpose limitation** + +The data importer shall process the personal data only for the specific purpose(s) of the transfer, as set out in Annex I.B, unless on further instructions from the data exporter. + +**8.3 Transparency** + +On request, the data exporter shall make a copy of these Clauses, including the Appendix as completed by the Parties, available to the data subject free of charge. To the extent necessary to protect business secrets or other confidential information, including the measures described in Annex II and personal data, the data exporter may redact part of the text of the Appendix to these Clauses prior to sharing a copy, but shall provide a meaningful summary where the data subject would otherwise not be able to understand the its content or exercise his/her rights. On request, the Parties shall provide the data subject with the reasons for the redactions, to the extent possible without revealing the redacted information. This Clause is without prejudice to the obligations of the data exporter under Articles 13 and 14 of Regulation (EU) 2016/679. + +**8.4 Accuracy** + +If the data importer becomes aware that the personal data it has received is inaccurate, or has become outdated, it shall inform the data exporter without undue delay. In this case, the data importer shall cooperate with the data exporter to erase or rectify the data. + +**8.5 Duration of processing and erasure or return of data** + +Processing by the data importer shall only take place for the duration specified in Annex I.B. After the end of the provision of the processing services, the data importer shall, at the choice of the data exporter, delete all personal data processed on behalf of the data exporter and certify to the data exporter that it has done so, or return to the data exporter all personal data processed on its behalf and delete existing copies. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit return or deletion of the personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process it to the extent and for as long as required under that local law. This is without prejudice to Clause 14, in particular the requirement for the data importer under Clause 14(e) to notify the data exporter throughout the duration of the contract if it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under Clause 14(a). + +**8.6 Security of processing** + +
      +
    1. The data importer and, during transmission, also the data exporter shall implement appropriate technical and organisational measures to ensure the security of the data, including protection against a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access to that data (hereinafter ‘personal data breach’). In assessing the appropriate level of security, the Parties shall take due account of the state of the art, the costs of implementation, the nature, scope, context and purpose(s) of processing and the risks involved in the processing for the data subjects. The Parties shall in particular consider having recourse to encryption or pseudonymisation, including during transmission, where the purpose of processing can be fulfilled in that manner. In case of pseudonymisation, the additional information for attributing the personal data to a specific data subject shall, where possible, remain under the exclusive control of the data exporter. In complying with its obligations under this paragraph, the data importer shall at least implement the technical and organisational measures specified in Annex II. The data importer shall carry out regular checks to ensure that these measures continue to provide an appropriate level of security.
      2. +
    2. The data importer shall grant access to the personal data to members of its personnel only to the extent strictly necessary for the implementation, management and monitoring of the contract. It shall ensure that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.
      3. +
    3. In the event of a personal data breach concerning personal data processed by the data importer under these Clauses, the data importer shall take appropriate measures to address the breach, including measures to mitigate its adverse effects. The data importer shall also notify the data exporter without undue delay after having become aware of the breach. Such notification shall contain the details of a contact point where more information can be obtained, a description of the nature of the breach (including, where possible, categories and approximate number of data subjects and personal data records concerned), its likely consequences and the measures taken or proposed to address the breach including, where appropriate, measures to mitigate its possible adverse effects. Where, and in so far as, it is not possible to provide all information at the same time, the initial notification shall contain the information then available and further information shall, as it becomes available, subsequently be provided without undue delay.
      4. +
    4. The data importer shall cooperate with and assist the data exporter to enable the data exporter to comply with its obligations under Regulation (EU) 2016/679, in particular to notify the competent supervisory authority and the affected data subjects, taking into account the nature of processing and the information available to the data importer.
      5. +
    + +**8.7 Sensitive data** + +Where the transfer involves personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic data, or biometric data for the purpose of uniquely identifying a natural person, data concerning health or a person’s sex life or sexual orientation, or data relating to criminal convictions and offences (hereinafter ‘sensitive data’), the data importer shall apply the specific restrictions and/or additional safeguards described in Annex I.B. + +**8.8 Onward transfers** + +The data importer shall only disclose the personal data to a third party on documented instructions from the data exporter. In addition, the data may only be disclosed to a third party located outside the European Union (1) (in the same country as the data importer or in another third country, hereinafter ‘onward transfer’) if the third party is or agrees to be bound by these Clauses, under the appropriate Module, or if: + +
      +
    1. the onward transfer is to a country benefitting from an adequacy decision pursuant to Article 45 of Regulation (EU) 2016/679 that covers the onward transfer;
      2. +
    2. the third party otherwise ensures appropriate safeguards pursuant to Articles 46 or 47 Regulation of (EU) 2016/679 with respect to the processing in question;
      3. +
    3. the onward transfer is necessary for the establishment, exercise or defence of legal claims in the context of specific administrative, regulatory or judicial proceedings; or
      4. +
    4. the onward transfer is necessary in order to protect the vital interests of the data subject or of another natural person.

      5. + Any onward transfer is subject to compliance by the data importer with all the other safeguards under these Clauses, in particular purpose limitation. +
    + +**8.9 Documentation and compliance** + +
      +
    1. The data importer shall promptly and adequately deal with enquiries from the data exporter that relate to the processing under these Clauses.
      2. +
    2. The Parties shall be able to demonstrate compliance with these Clauses. In particular, the data importer shall keep appropriate documentation on the processing activities carried out on behalf of the data exporter.
      3. +
    3. The data importer shall make available to the data exporter all information necessary to demonstrate compliance with the obligations set out in these Clauses and at the data exporter’s request, allow for and contribute to audits of the processing activities covered by these Clauses, at reasonable intervals or if there are indications of non-compliance. In deciding on a review or audit, the data exporter may take into account relevant certifications held by the data importer.
      4. +
    4. The data exporter may choose to conduct the audit by itself or mandate an independent auditor. Audits may include inspections at the premises or physical facilities of the data importer and shall, where appropriate, be carried out with reasonable notice.
      5. +
    5. The Parties shall make the information referred to in paragraphs (b) and (c), including the results of any audits, available to the competent supervisory authority on request.
      6. +
    + +##### Clause 9 + +**Use of sub-processors** + +
      +
    1. GENERAL WRITTEN AUTHORISATION The data importer has the data exporter’s general authorisation for the engagement of sub-processor(s) from an agreed list. The data importer shall specifically inform the data exporter in writing of any intended changes to that list through the addition or replacement of sub-processors at least 90 days in advance, thereby giving the data exporter sufficient time to be able to object to such changes prior to the engagement of the sub-processor(s). The data importer shall provide the data exporter with the information necessary to enable the data exporter to exercise its right to object.
      2. +
    2. Where the data importer engages a sub-processor to carry out specific processing activities (on behalf of the data exporter), it shall do so by way of a written contract that provides for, in substance, the same data protection obligations as those binding the data importer under these Clauses, including in terms of third-party beneficiary rights for data subjects.(2) The Parties agree that, by complying with this Clause, the data importer fulfils its obligations under Clause 8.8. The data importer shall ensure that the sub-processor complies with the obligations to which the data importer is subject pursuant to these Clauses.
      3. +
    3. The data importer shall provide, at the data exporter’s request, a copy of such a sub-processor agreement and any subsequent amendments to the data exporter. To the extent necessary to protect business secrets or other confidential information, including personal data, the data importer may redact the text of the agreement prior to sharing a copy.
      4. +
    4. The data importer shall remain fully responsible to the data exporter for the performance of the sub-processor’s obligations under its contract with the data importer. The data importer shall notify the data exporter of any failure by the sub-processor to fulfil its obligations under that contract.
      5. +
    5. The data importer shall agree a third-party beneficiary clause with the sub-processor whereby – in the event the data importer has factually disappeared, ceased to exist in law or has become insolvent – the data exporter shall have the right to terminate the sub-processor contract and to instruct the sub-processor to erase or return the personal data.
      6. +
    + +##### Clause 10 + +**Data subject rights** + +
      +
    1. The data importer shall promptly notify the data exporter of any request it has received from a data subject. It shall not respond to that request itself unless it has been authorised to do so by the data exporter.
      2. +
    2. The data importer shall assist the data exporter in fulfilling its obligations to respond to data subjects’ requests for the exercise of their rights under Regulation (EU) 2016/679. In this regard, the Parties shall set out in Annex II the appropriate technical and organisational measures, taking into account the nature of the processing, by which the assistance shall be provided, as well as the scope and the extent of the assistance required.
      3. +
    3. In fulfilling its obligations under paragraphs (a) and (b), the data importer shall comply with the instructions from the data exporter.
      4. +
    + +##### Clause 11 + +**Redress** + +
      +
    1. The data importer shall inform data subjects in a transparent and easily accessible format, through individual notice or on its website, of a contact point authorised to handle complaints. It shall deal promptly with any complaints it receives from a data subject.
      2. +
    2. In case of a dispute between a data subject and one of the Parties as regards compliance with these Clauses, that Party shall use its best efforts to resolve the issue amicably in a timely fashion. The Parties shall keep each other informed about such disputes and, where appropriate, cooperate in resolving them.
      3. +
    3. Where the data subject invokes a third-party beneficiary right pursuant to Clause 3, the data importer shall accept the decision of the data subject to:
      4. +
        +
      1. lodge a complaint with the supervisory authority in the Member State of his/her habitual residence or place of work, or the competent supervisory authority pursuant to Clause 13;
        2. +
      2. refer the dispute to the competent courts within the meaning of Clause 18.
        3. +
      +
    4. The Parties accept that the data subject may be represented by a not-for-profit body, organisation or association under the conditions set out in Article 80(1) of Regulation (EU) 2016/679.
      5. +
    5. The data importer shall abide by a decision that is binding under the applicable EU or Member State law.
      6. +
    6. The data importer agrees that the choice made by the data subject will not prejudice his/her substantive and procedural rights to seek remedies in accordance with applicable laws.
      7. +
    + +##### Clause 12 + +**Liability** + +
      +
    1. Each Party shall be liable to the other Party/ies for any damages it causes the other Party/ies by any breach of these Clauses.
      2. +
    2. The data importer shall be liable to the data subject, and the data subject shall be entitled to receive compensation, for any material or non-material damages the data importer or its sub-processor causes the data subject by breaching the third-party beneficiary rights under these Clauses.
      3. +
    3. Notwithstanding paragraph (b), the data exporter shall be liable to the data subject, and the data subject shall be entitled to receive compensation, for any material or non-material damages the data exporter or the data importer (or its sub-processor) causes the data subject by breaching the third-party beneficiary rights under these Clauses. This is without prejudice to the liability of the data exporter and, where the data exporter is a processor acting on behalf of a controller, to the liability of the controller under Regulation (EU) 2016/679 or Regulation (EU) 2018/1725, as applicable.
      4. +
    4. The Parties agree that if the data exporter is held liable under paragraph (c) for damages caused by the data importer (or its sub-processor), it shall be entitled to claim back from the data importer that part of the compensation corresponding to the data importer’s responsibility for the damage.
      5. +
    5. Where more than one Party is responsible for any damage caused to the data subject as a result of a breach of these Clauses, all responsible Parties shall be jointly and severally liable and the data subject is entitled to bring an action in court against any of these Parties.
      6. +
    6. The Parties agree that if one Party is held liable under paragraph (e), it shall be entitled to claim back from the other Party/ies that part of the compensation corresponding to its/their responsibility for the damage.
      7. +
    7. The data importer may not invoke the conduct of a sub-processor to avoid its own liability.
      8. +
    + +##### Clause 13 + +**Supervision** + +
      +
    1. [Where the data exporter is established in an EU Member State:] The supervisory authority with responsibility for ensuring compliance by the data exporter with Regulation (EU) 2016/679 as regards the data transfer, as indicated in Annex I.C, shall act as competent supervisory authority.

      + [Where the data exporter is not established in an EU Member State, but falls within the territorial scope of application of Regulation (EU) 2016/679 in accordance with its Article 3(2) and has appointed a representative pursuant to Article 27(1) of Regulation (EU) 2016/679:] The supervisory authority of the Member State in which the representative within the meaning of Article 27(1) of Regulation (EU) 2016/679 is established, as indicated in Annex I.C, shall act as competent supervisory authority.

      + [Where the data exporter is not established in an EU Member State, but falls within the territorial scope of application of Regulation (EU) 2016/679 in accordance with its Article 3(2) without however having to appoint a representative pursuant to Article 27(2) of Regulation (EU) 2016/679:] The supervisory authority of one of the Member States in which the data subjects whose personal data is transferred under these Clauses in relation to the offering of goods or services to them, or whose behaviour is monitored, are located, as indicated in Annex I.C, shall act as competent supervisory authority.

      2. +
    2. The data importer agrees to submit itself to the jurisdiction of and cooperate with the competent supervisory authority in any procedures aimed at ensuring compliance with these Clauses. In particular, the data importer agrees to respond to enquiries, submit to audits and comply with the measures adopted by the supervisory authority, including remedial and compensatory measures. It shall provide the supervisory authority with written confirmation that the necessary actions have been taken.
      3. +
    + +#### SECTION III – LOCAL LAWS AND OBLIGATIONS IN CASE OF ACCESS BY PUBLIC AUTHORITIES + +##### Clause 14 + +**Local laws and practices affecting compliance with the Clauses** + +
      +
    1. The Parties warrant that they have no reason to believe that the laws and practices in the third country of destination applicable to the processing of the personal data by the data importer, including any requirements to disclose personal data or measures authorising access by public authorities, prevent the data importer from fulfilling its obligations under these Clauses. This is based on the understanding that laws and practices that respect the essence of the fundamental rights and freedoms and do not exceed what is necessary and proportionate in a democratic society to safeguard one of the objectives listed in Article 23(1) of Regulation (EU) 2016/679, are not in contradiction with these Clauses.
      2. +
    2. The Parties declare that in providing the warranty in paragraph (a), they have taken due account in particular of the following elements:
      3. +
        +
      1. the specific circumstances of the transfer, including the length of the processing chain, the number of actors involved and the transmission channels used; intended onward transfers; the type of recipient; the purpose of processing; the categories and format of the transferred personal data; the economic sector in which the transfer occurs; the storage location of the data transferred;
        2. +
      2. the laws and practices of the third country of destination– including those requiring the disclosure of data to public authorities or authorising access by such authorities – relevant in light of the specific circumstances of the transfer, and the applicable limitations and safeguards (3);
        3. +
      3. any relevant contractual, technical or organisational safeguards put in place to supplement the safeguards under these Clauses, including measures applied during transmission and to the processing of the personal data in the country of destination.
        4. +
      +
    3. The data importer warrants that, in carrying out the assessment under paragraph (b), it has made its best efforts to provide the data exporter with relevant information and agrees that it will continue to cooperate with the data exporter in ensuring compliance with these Clauses.
      4. +
    4. The Parties agree to document the assessment under paragraph (b) and make it available to the competent supervisory authority on request.
      5. +
    5. The data importer agrees to notify the data exporter promptly if, after having agreed to these Clauses and for the duration of the contract, it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under paragraph (a), including following a change in the laws of the third country or a measure (such as a disclosure request) indicating an application of such laws in practice that is not in line with the requirements in paragraph (a).
      6. +
    6. Following a notification pursuant to paragraph (e), or if the data exporter otherwise has reason to believe that the data importer can no longer fulfil its obligations under these Clauses, the data exporter shall promptly identify appropriate measures (e.g. technical or organisational measures to ensure security and confidentiality) to be adopted by the data exporter and/or data importer to address the situation. The data exporter shall suspend the data transfer if it considers that no appropriate safeguards for such transfer can be ensured, or if instructed by the competent supervisory authority to do so. In this case, the data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses. If the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise. Where the contract is terminated pursuant to this Clause, Clause 16(d) and (e) shall apply.
      7. +
    + +##### Clause 15 + +**Obligations of the data importer in case of access by public authorities** + +**15.1 Notification** + +
      +
    1. The data importer agrees to notify the data exporter and, where possible, the data subject promptly (if necessary with the help of the data exporter) if it:
      2. +
        +
      1. receives a legally binding request from a public authority, including judicial authorities, under the laws of the country of destination for the disclosure of personal data transferred pursuant to these Clauses; such notification shall include information about the personal data requested, the requesting authority, the legal basis for the request and the response provided; or
        2. +
      2. becomes aware of any direct access by public authorities to personal data transferred pursuant to these Clauses in accordance with the laws of the country of destination; such notification shall include all information available to the importer.
        3. +
      +
    2. If the data importer is prohibited from notifying the data exporter and/or the data subject under the laws of the country of destination, the data importer agrees to use its best efforts to obtain a waiver of the prohibition, with a view to communicating as much information as possible, as soon as possible. The data importer agrees to document its best efforts in order to be able to demonstrate them on request of the data exporter.
      3. +
    3. Where permissible under the laws of the country of destination, the data importer agrees to provide the data exporter, at regular intervals for the duration of the contract, with as much relevant information as possible on the requests received (in particular, number of requests, type of data requested, requesting authority/ies, whether requests have been challenged and the outcome of such challenges, etc.).
      4. +
    4. The data importer agrees to preserve the information pursuant to paragraphs (a) to (c) for the duration of the contract and make it available to the competent supervisory authority on request.
      5. +
    5. Paragraphs (a) to (c) are without prejudice to the obligation of the data importer pursuant to Clause 14(e) and Clause 16 to inform the data exporter promptly where it is unable to comply with these Clauses.
      6. +
    + +**15.2 Review of legality and data minimisation** + +
      +
    1. The data importer agrees to review the legality of the request for disclosure, in particular whether it remains within the powers granted to the requesting public authority, and to challenge the request if, after careful assessment, it concludes that there are reasonable grounds to consider that the request is unlawful under the laws of the country of destination, applicable obligations under international law and principles of international comity. The data importer shall, under the same conditions, pursue possibilities of appeal. When challenging a request, the data importer shall seek interim measures with a view to suspending the effects of the request until the competent judicial authority has decided on its merits. It shall not disclose the personal data requested until required to do so under the applicable procedural rules. These requirements are without prejudice to the obligations of the data importer under Clause 14(e).
      2. +
    2. The data importer agrees to document its legal assessment and any challenge to the request for disclosure and, to the extent permissible under the laws of the country of destination, make the documentation available to the data exporter. It shall also make it available to the competent supervisory authority on request.
      3. +
    3. The data importer agrees to provide the minimum amount of information permissible when responding to a request for disclosure, based on a reasonable interpretation of the request.
      4. +
    + +#### SECTION IV – FINAL PROVISIONS + +##### Clause 16 + +**Non-compliance with the Clauses and termination** + +
      +
    1. The data importer shall promptly inform the data exporter if it is unable to comply with these Clauses, for whatever reason.
      2. +
    2. In the event that the data importer is in breach of these Clauses or unable to comply with these Clauses, the data exporter shall suspend the transfer of personal data to the data importer until compliance is again ensured or the contract is terminated. This is without prejudice to Clause 14(f).
      3. +
    3. The data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses, where:
      4. +
        +
      1. the data exporter has suspended the transfer of personal data to the data importer pursuant to paragraph (b) and compliance with these Clauses is not restored within a reasonable time and in any event within one month of suspension;
        2. +
      2. the data importer is in substantial or persistent breach of these Clauses; or
        3. +
      3. the data importer fails to comply with a binding decision of a competent court or supervisory authority regarding its obligations under these Clauses.
        4. +

      + In these cases, it shall inform the competent supervisory authority of such non-compliance. Where the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise. +
    4. Personal data that has been transferred prior to the termination of the contract pursuant to paragraph (c) shall at the choice of the data exporter immediately be returned to the data exporter or deleted in its entirety. The same shall apply to any copies of the data. The data importer shall certify the deletion of the data to the data exporter. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit the return or deletion of the transferred personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process the data to the extent and for as long as required under that local law.
      5. +
    5. Either Party may revoke its agreement to be bound by these Clauses where (i) the European Commission adopts a decision pursuant to Article 45(3) of Regulation (EU) 2016/679 that covers the transfer of personal data to which these Clauses apply; or (ii) Regulation (EU) 2016/679 becomes part of the legal framework of the country to which the personal data is transferred. This is without prejudice to other obligations applying to the processing in question under Regulation (EU) 2016/679.
      6. +
    + +##### Clause 17 + +**Governing law** + +These Clauses shall be governed by the law of one of the EU Member States, provided such law allows for third-party beneficiary rights. The Parties agree that this shall be the law of the Netherlands. + +##### Clause 18 + +**Choice of forum and jurisdiction** + +
      +
    1. Any dispute arising from these Clauses shall be resolved by the courts of an EU Member State.
      2. +
    2. The Parties agree that those shall be the courts of the Netherlands.
      3. +
    3. A data subject may also bring legal proceedings against the data exporter and/or data importer before the courts of the Member State in which he/she has his/her habitual residence.
      4. +
    4. The Parties agree to submit themselves to the jurisdiction of such courts.
      5. +
    + +## ANNEX I + +**to the Standard Contractual Clauses (EU/EEA)** + +### A. LIST OF PARTIES + +**Data exporter(s)**: Customer is the data exporter
    Name: see GitHub Customer Agreement
    Address: see GitHub Customer Agreement
    Contact person’s name, position and contact details: see GitHub Customer Agreement
    Activities relevant to the data transferred under these Clauses:
    The data exporter is a user of Online Services or Professional Services as defined in the DPA and GitHub Customer Agreement.
    Signature and date: see GitHub Customer Agreement (the DPA and the Standard Contractual Clauses (EU/EEA) are incorporated into the GitHub Customer Agreement
    Role (controller/processor): controller (unless otherwise agreed in the Customer Agreement).
    + +**Data importer(s)**:
    Name: GitHub, Inc.
    Address: 88 Colin P Kelly Jr St, San Francisco, CA 94107, USA
    Contact person’s name, position and contact details: Frances Wiet, Head of Privacy, fwiet@github.com
    Activities relevant to the data transferred under these Clauses:
    GitHub, Inc. is a global producer of software and services
    Signature and date: see GitHub Customer Agreement (the DPA and the Standard Contractual Clauses (EU/EEA) are incorporated into the GitHub Customer Agreement)
    Role (controller/processor): processor or, depending on the agreements set forth in the Customer Agreement, subprocessor. + +### B. DESCRIPTION OF TRANSFER + +_Categories of data subjects whose personal data is transferred:_ + +Data subjects include the data exporter’s representatives and end-users including employees, contractors, collaborators, and customers of the data exporter. Data subjects may also include individuals attempting to communicate or transfer personal data to users of the services provided by data importer. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following types of data subjects in the personal data: +- Employees, contractors and temporary workers (current, former, prospective) of data exporter; +- Data exporter's collaborators/contact persons (natural persons) or employees, contractors or temporary workers of legal entity collaborators/contact persons (current, prospective, former); +- Users and other data subjects that are users of data exporter's services; +- Partners, stakeholders or individuals who actively collaborate, communicate or otherwise interact with employees of the data exporter and/or use communication tools such as apps and websites provided by the data exporter. + +_Categories of personal data transferred:_ + +The personal data transferred that is included in e-mail, documents and other data in an electronic form in the context of the Online Services or Professional Services. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following categories in the personal data: +- Basic personal data (for example place of birth, street name and house number (address), postal code, city of residence, country of residence, mobile phone number, first name, last name, initials, email address, gender, date of birth); +- Authentication data (for example user name, password or PIN code, security question, audit trail); +- Contact information (for example addresses, email, phone numbers, social media identifiers; emergency contact details); +- Unique identification numbers and signatures (for example IP addresses, employee number, student number); +- Pseudonymous identifiers; +- Photos, video and audio; +- Internet activity (for example browsing history, search history, reading and viewing activities); +- Device identification (for example IMEI-number, SIM card number, MAC address); +- Profiling (for example based on observed criminal or anti-social behavior or pseudonymous profiles based on visited URLs, click streams, browsing logs, IP-addresses, domains, apps installed, or profiles based on marketing preferences); +- Special categories of data as voluntarily provided by data subjects (for example racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health, data concerning a natural person’s sex life or sexual orientation, or data relating to criminal convictions or offences); or +- Any other personal data identified in Article 4 of the GDPR. + +_**Sensitive data** transferred (if applicable) and applied restrictions or safeguards that fully take into consideration the nature of the data and the risks involved, such as for instance strict purpose limitation, access restrictions (including access only for staff having followed specialised training), keeping a record of access to the data, restrictions for onward transfers or additional security measures:_
    GitHub does not request or otherwise ask for sensitive data and receives such data only if and when customers or data subjects decide to provide it. + +_**The frequency of the transfer** (e.g. whether the data is transferred on a one-off or continuous basis):_ + +Continuous as part of the Online Services or Professional Services. + +_**Nature of the processing:**_ + +The personal data transferred will be subject to the following basic processing activities: +
      +
    1. Duration and Object of Data Processing. The duration of data processing shall be for the term designated under the applicable GitHub Customer Agreement between data exporter and the data importer. The objective of the data processing is the performance of Online Services and Professional Services.
      2. +
    2. Personal Data Access. For the term designated under the applicable GitHub Customer Agreement, data importer will, at its election and as necessary under applicable law, either: (1) provide data exporter with the ability to correct, delete, or block personal data, or (2) make such corrections, deletions, or blockages on its behalf.
      3. +
    3. Data Exporter’s Instructions. For Online Services and Professional Services, data importer will only act upon data exporter’s instructions.
      4. +
    + +_Purpose(s) of the data transfer and further processing:_ + +The scope and purpose of processing personal data is described in the “Processing of Personal Data; GDPR” section of the DPA. The data importer operates a global network of data centers and management/support facilities, and processing may take place in any jurisdiction where data importer or its sub-processors operate such facilities in accordance with the “Security Practices and Policies” section of the DPA. + +_The period for which the personal data will be retained, or, if that is not possible, the criteria used to determine that period:_ + +Upon expiration or termination of data exporter’s use of Online Services or Professional Services, it may extract personal data and data importer will delete personal data, each in accordance with the DPA Terms applicable to the agreement. + +_For transfers to (sub-) processors, also specify subject matter, nature and duration of the processing:_ + +In accordance with the DPA, the data importer may hire other companies to provide limited services on data importer’s behalf, such as providing customer support. Any such subcontractors will be permitted to obtain personal data only to deliver the services the data importer has retained them to provide, and they are prohibited from using personal data for any other purpose. Unless a particular subcontractor is replaced ahead of time, the processing will be for the term designated under the applicable GitHub Customer Agreement between data exporter and data importer. + +### C. COMPETENT SUPERVISORY AUTHORITY + +_Identify the competent supervisory authority/ies in accordance with Clause 13:_ + +The supervisory authority with responsibility for ensuring compliance by the data exporter with Regulation (EU) 2016/679.   +## ANNEX II + +**to the Standard Contractual Clauses (EU/EEA)** + +**TECHNICAL AND ORGANISATIONAL MEASURES INCLUDING TECHNICAL AND ORGANISATIONAL MEASURES TO ENSURE THE SECURITY OF THE DATA** + +_Description of the technical and organisational measures implemented by the data importer(s) (including any relevant certifications) to ensure an appropriate level of security, taking into account the nature, scope, context and purpose of the processing, and the risks for the rights and freedoms of natural persons._ + +
      +
    1. Data Security Certifications. Data importer holds the following data security certifications:
      2. +
        +
      • SOC 1, Type 2;
        • +
      • SOC 2, Type 2;
        • +
      • NIST, to the extent incorporated for FedRAMP Low-Impact / Tailored ATO.
        • +
      +
    2. Personnel. Data importer’s personnel will not process personal data without authorization. Personnel are obligated to maintain the confidentiality of any such personal data and this obligation continues even after their engagement ends.
      3. +
    3. Data Privacy Contact. The data privacy officer of the data importer can be reached at the following address:

      + GitHub, Inc.
      + Attn: Privacy
      + 88 Colin P. Kelly Jr. Street
      + San Francisco, California 94107 USA

      4. +
    4. Technical and Organization Measures. The data importer has implemented and will maintain appropriate technical and organizational measures, internal controls, and information security routines intended to protect personal data, as defined in the Security Practices and Policies section of the DPA, against accidental loss, destruction, or alteration; unauthorized disclosure or access; or unlawful destruction as follows: The technical and organizational measures, internal controls, and information security routines set forth in the Data Security section of the DPA are hereby incorporated into this Annex II to Attachment 1 by this reference and are binding on the data importer as if they were set forth in this Annex 2 to Attachment 1 in their entirety.
      5. +
    + +_For transfers to (sub-) processors, also describe the specific technical and organisational measures to be taken by the (sub-) processor to be able to provide assistance to the controller and, for transfers from a processor to a sub-processor, to the data exporter:_ + +**Vendor management program - third-party risk program** + +The data importer has a vendor risk assessment process, vendor contract clauses and additional data protection agreements with vendors. Vendors undergo reassessment when a new business use case is requested. The data importer’s vendor risk program is structured so all of data importer’s vendors' risk assessments are refreshed two years from the last review date. + +Vendors deemed high risk, such as data center providers or other vendors storing or processing data in scope for the data importer’s regulatory or contractual requirements, undergo reassessment annually. + +## ANNEX III + +**to the Standard Contractual Clauses (EU/EEA)** + +**Additional Safeguards Addendum** + +By this Additional Safeguards Addendum to Standard Contractual Clauses (EU/EEA) (this “Addendum”), GitHub, Inc. (“GitHub”) provides additional safeguards to Customer and additional redress to the data subjects to whom Customer’s personal data relates. + +This Addendum supplements and is made part of, but is not in variation or modification of, the Standard Contractual Clauses (EU/EEA). + +
      +
    1. Challenges to Orders. In addition to Clause 15.1 of the Standard Contractual Clauses (EU/EEA), in the event GitHub receives an order from any third party for compelled disclosure of any personal data that has been transferred under the Standard Contractual Clauses (EU/EEA), GitHub shall:
      2. +
        +
      1. use every reasonable effort to redirect the third party to request data directly from Customer;
        2. +
      2. promptly notify Customer, unless prohibited under the law applicable to the requesting third party, and, if prohibited from notifying Customer, use all lawful efforts to obtain the right to waive the prohibition in order to communicate as much information to Customer as soon as possible; and
        3. +
      3. use all lawful efforts to challenge the order for disclosure on the basis of any legal deficiencies under the laws of the requesting party or any relevant conflicts with the law of the European Union or applicable Member State law.
        4. +

      + For purpose of this section, lawful efforts do not include actions that would result in civil or criminal penalty such as contempt of court under the laws of the relevant jurisdiction. +
    2. Indemnification of Data Subjects. Subject to Sections 3 and 4, GitHub shall indemnify a data subject for any material or non-material damage to the data subject caused by GitHub’s disclosure of personal data of the data subject that has been transferred under the Standard Contractual Clauses (EU/EEA) in response to an order from a non-EU/EEA government body or law enforcement agency (a “Relevant Disclosure”). Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under this Section 2 to the extent the data subject has already received compensation for the same damage, whether from GitHub or otherwise.
      3. +
    3. Conditions of Indemnification. Indemnification under Section 2 is conditional upon the data subject establishing, to GitHub’s reasonable satisfaction, that:
      4. +
        +
      1. GitHub engaged in a Relevant Disclosure;
        2. +
      2. the Relevant Disclosure was the basis of an official proceeding by the non-EU/EEA government body or law enforcement agency against the data subject; and
        3. +
      3. the Relevant Disclosure directly caused the data subject to suffer material or non-material damage.
        4. +

      + The data subject bears the burden of proof with respect to conditions a. though c.
      + Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under Section 2 if GitHub establishes that the Relevant Disclosure did not violate its obligations under Chapter V of the GDPR.
      +
    4. Scope of Damages. Indemnification under Section 2 is limited to material and non-material damages as provided in the GDPR and excludes consequential damages and all other damages not resulting from GitHub’s infringement of the GDPR.
      5. +
    5. Exercise of Rights. Rights granted to data subjects under this Addendum may be enforced by the data subject against GitHub irrespective of any restriction in Clauses 3 or 12 of the Standard Contractual Clauses (EU/EEA). The data subject may only bring a claim under this Addendum on an individual basis, and not part of a class, collective, group or representative action. Rights granted to data subjects under this Addendum are personal to the data subject and may not be assigned.
      6. +
    6. Notice of Change. In addition to Clause 14 of the Standard Contractual Clauses (EU/EEA), GitHub agrees and warrants that it has no reason to believe that the legislation applicable to it or its sub-processors, including in any country to which personal data is transferred either by itself or through a sub-processor, prevents it from fulfilling the instructions received from the data exporter and its obligations under this Addendum or the Standard Contractual Clauses (EU/EEA) and that in the event of a change in this legislation which is likely to have a substantial adverse effect on the warranties and obligations provided by this Addendum or the Standard Contractual Clauses (EU/EEA), it will promptly notify the change to Customer as soon as it is aware, in which case Customer is entitled to suspend the transfer of data and/or terminate the contract.
      7. +
    7. Termination. This Addendum shall automatically terminate if the European Commission, a competent Member State supervisory authority, or an EU or competent Member State court approves a different lawful transfer mechanism that would be applicable to the data transfers covered by the Standard Contractual Clauses (EU/EEA) (and if such mechanism applies only to some of the data transfers, this Addendum will terminate only with respect to those transfers) and that does not require the additional safeguards set forth in this Addendum.
      8. +
    + +

    Attachment 2 – The Standard Contractual Clauses (UK)

    + +Execution of the GitHub Customer Agreement by Customer includes execution of this Attachment 2, which is countersigned by GitHub, Inc. + +In countries where regulatory approval is required for use of the Standard Contractual Clauses, the Standard Contractual Clauses cannot be relied upon under European Commission 2010/87/EU (of February 2010) to legitimize export of data from the country, unless Customer has the required regulatory approval. + +Beginning May 25, 2018 and thereafter, references to various Articles from the Directive 95/46/EC in the Standard Contractual Clauses below will be treated as references to the relevant and appropriate Articles in the GDPR. + +For the purposes of Article 26(2) of Directive 95/46/EC for the transfer of personal data to processors established in third countries which do not ensure an adequate level of data protection, Customer (as data exporter) and GitHub, Inc. (as data importer, whose signature appears below), each a “party,” together “the parties,” have agreed on the following Contractual Clauses (the “Clauses” or “Standard Contractual Clauses”) in order to adduce adequate safeguards with respect to the protection of privacy and fundamental rights and freedoms of individuals for the transfer by the data exporter to the data importer of the personal data specified in Appendix 1. + +### Clause 1: Definitions + +
      +
    1. 'personal data', 'special categories of data', 'process/processing', 'controller', 'processor', 'data subject' and 'supervisory authority' shall have the same meaning as in Directive 95/46/EC of the European Parliament and of the Council of 24 October 1995 on the protection of individuals with regard to the processing of personal data and on the free movement of such data;
      2. +
    2. 'the data exporter' means the controller who transfers the personal data;
      3. +
    3. 'the data importer' means the processor who agrees to receive from the data exporter personal data intended for processing on his behalf after the transfer in accordance with his instructions and the terms of the Clauses and who is not subject to a third country's system ensuring adequate protection within the meaning of Article 25(1) of Directive 95/46/EC;
      4. +
    4. 'the subprocessor' means any processor engaged by the data importer or by any other subprocessor of the data importer who agrees to receive from the data importer or from any other subprocessor of the data importer personal data exclusively intended for processing activities to be carried out on behalf of the data exporter after the transfer in accordance with his instructions, the terms of the Clauses and the terms of the written subcontract;
      5. +
    5. 'the applicable data protection law' means the legislation protecting the fundamental rights and freedoms of individuals and, in particular, their right to privacy with respect to the processing of personal data applicable to a data controller in the Member State in which the data exporter is established;
      6. +
    6. 'technical and organisational security measures' means those measures aimed at protecting personal data against accidental or unlawful destruction or accidental loss, alteration, unauthorised disclosure or access, in particular where the processing involves the transmission of data over a network, and against all other unlawful forms of processing.
      7. +
    + +### Clause 2: Details of the transfer + +The details of the transfer and in particular the special categories of personal data where applicable are specified in Appendix 1 below which forms an integral part of the Clauses. + +### Clause 3: Third-party beneficiary clause + +
      +
    1. The data subject can enforce against the data exporter this Clause, Clause 4(b) to (i), Clause 5(a) to (e), and (g) to (j), Clause 6(1) and (2), Clause 7, Clause 8(2), and Clauses 9 to 12 as third-party beneficiary.
      2. +
    2. The data subject can enforce against the data importer this Clause, Clause 5(a) to (e) and (g), Clause 6, Clause 7, Clause 8(2), and Clauses 9 to 12, in cases where the data exporter has factually disappeared or has ceased to exist in law unless any successor entity has assumed the entire legal obligations of the data exporter by contract or by operation of law, as a result of which it takes on the rights and obligations of the data exporter, in which case the data subject can enforce them against such entity.
      3. +
    3. The data subject can enforce against the subprocessor this Clause, Clause 5(a) to (e) and (g), Clause 6, Clause 7, Clause 8(2), and Clauses 9 to 12, in cases where both the data exporter and the data importer have factually disappeared or ceased to exist in law or have become insolvent, unless any successor entity has assumed the entire legal obligations of the data exporter by contract or by operation of law as a result of which it takes on the rights and obligations of the data exporter, in which case the data subject can enforce them against such entity. Such third-party liability of the subprocessor shall be limited to its own processing operations under the Clauses.
      4. +
    4. The parties do not object to a data subject being represented by an association or other body if the data subject so expressly wishes and if permitted by national law.
      5. +
    + +### Clause 4: Obligations of the data exporter + +The data exporter agrees and warrants: + +
      +
    1. that the processing, including the transfer itself, of the personal data has been and will continue to be carried out in accordance with the relevant provisions of the applicable data protection law (and, where applicable, has been notified to the relevant authorities of the Member State where the data exporter is established) and does not violate the relevant provisions of that State;
      2. +
    2. that it has instructed and throughout the duration of the personal data processing services will instruct the data importer to process the personal data transferred only on the data exporter's behalf and in accordance with the applicable data protection law and the Clauses;
      3. +
    3. that the data importer will provide sufficient guarantees in respect of the technical and organisational security measures specified in Appendix 2 below;
      4. +
    4. that after assessment of the requirements of the applicable data protection law, the security measures are appropriate to protect personal data against accidental or unlawful destruction or accidental loss, alteration, unauthorised disclosure or access, in particular where the processing involves the transmission of data over a network, and against all other unlawful forms of processing, and that these measures ensure a level of security appropriate to the risks presented by the processing and the nature of the data to be protected having regard to the state of the art and the cost of their implementation;
      5. +
    5. that it will ensure compliance with the security measures;
      6. +
    6. that, if the transfer involves special categories of data, the data subject has been informed or will be informed before, or as soon as possible after, the transfer that its data could be transmitted to a third country not providing adequate protection within the meaning of Directive 95/46/EC;
      7. +
    7. to forward any notification received from the data importer or any subprocessor pursuant to Clause 5(b) and Clause 8(3) to the data protection supervisory authority if the data exporter decides to continue the transfer or to lift the suspension;
      8. +
    8. to make available to the data subjects upon request a copy of the Clauses, with the exception of Appendix 2, and a summary description of the security measures, as well as a copy of any contract for subprocessing services which has to be made in accordance with the Clauses, unless the Clauses or the contract contain commercial information, in which case it may remove such commercial information;
      9. +
    9. that, in the event of subprocessing, the processing activity is carried out in accordance with Clause 11 by a subprocessor providing at least the same level of protection for the personal data and the rights of data subject as the data importer under the Clauses; and
      10. +
    10. that it will ensure compliance with Clause 4(a) to (i).
      11. +
    + +### Clause 5: Obligations of the data importer + +The data importer agrees and warrants: + +
      +
    1. to process the personal data only on behalf of the data exporter and in compliance with its instructions and the Clauses; if it cannot provide such compliance for whatever reasons, it agrees to inform promptly the data exporter of its inability to comply, in which case the data exporter is entitled to suspend the transfer of data and/or terminate the contract;
      2. +
    2. that it has no reason to believe that the legislation applicable to it prevents it from fulfilling the instructions received from the data exporter and its obligations under the contract and that in the event of a change in this legislation which is likely to have a substantial adverse effect on the warranties and obligations provided by the Clauses, it will promptly notify the change to the data exporter as soon as it is aware, in which case the data exporter is entitled to suspend the transfer of data and/or terminate the contract;
      3. +
    3. that it has implemented the technical and organisational security measures specified in Appendix 2 before processing the personal data transferred;
      4. +
    4. that it will promptly notify the data exporter about:
      5. +
        +
      1. any legally binding request for disclosure of the personal data by a law enforcement authority unless otherwise prohibited, such as a prohibition under criminal law to preserve the confidentiality of a law enforcement investigation,
        2. +
      2. any accidental or unauthorised access, and
        3. +
      3. any request received directly from the data subjects without responding to that request, unless it has been otherwise authorised to do so;
        4. +
      + to deal promptly and properly with all inquiries from the data exporter relating to its processing of the personal data subject to the transfer and to abide by the advice of the supervisory authority with regard to the processing of the data transferred; + at the request of the data exporter to submit its data processing facilities for audit of the processing activities covered by the Clauses which shall be carried out by the data exporter or an inspection body composed of independent members and in possession of the required professional qualifications bound by a duty of confidentiality, selected by the data exporter, where applicable, in agreement with the supervisory authority; +
    5. to make available to the data subject upon request a copy of the Clauses, or any existing contract for subprocessing, unless the Clauses or contract contain commercial information, in which case it may remove such commercial information, with the exception of Appendix 2 which shall be replaced by a summary description of the security measures in those cases where the data subject is unable to obtain a copy from the data exporter;
      6. +
    6. that, in the event of subprocessing, it has previously informed the data exporter and obtained its prior written consent;
      7. +
    7. that the processing services by the subprocessor will be carried out in accordance with Clause 11; and
      8. +
    8. to send promptly a copy of any subprocessor agreement it concludes under the Clauses to the data exporter.
      9. +
    + +### Clause 6: Liability + +
      +
    1. The parties agree that any data subject who has suffered damage as a result of any breach of the obligations referred to in Clause 3 or in Clause 11 by any party or subprocessor is entitled to receive compensation from the data exporter for the damage suffered.
      2. + +
    2. If a data subject is not able to bring a claim for compensation in accordance with paragraph 1 against the data exporter, arising out of a breach by the data importer or his subprocessor of any of their obligations referred to in Clause 3 or in Clause 11, because the data exporter has factually disappeared or ceased to exist in law or has become insolvent, the data importer agrees that the data subject may issue a claim against the data importer as if it were the data exporter, unless any successor entity has assumed the entire legal obligations of the data exporter by contract of by operation of law, in which case the data subject can enforce its rights against such entity.

      + The data importer may not rely on a breach by a subprocessor of its obligations in order to avoid its own liabilities.
      3. + +
    3. If a data subject is not able to bring a claim against the data exporter or the data importer referred to in paragraphs 1 and 2, arising out of a breach by the subprocessor of any of their obligations referred to in Clause 3 or in Clause 11 because both the data exporter and the data importer have factually disappeared or ceased to exist in law or have become insolvent, the subprocessor agrees that the data subject may issue a claim against the data subprocessor with regard to its own processing operations under the Clauses as if it were the data exporter or the data importer, unless any successor entity has assumed the entire legal obligations of the data exporter or data importer by contract or by operation of law, in which case the data subject can enforce its rights against such entity. The liability of the subprocessor shall be limited to its own processing operations under the Clauses.
      4. +
    + +### Clause 7: Mediation and jurisdiction + +
      +
    1. The data importer agrees that if the data subject invokes against it third-party beneficiary rights and/or claims compensation for damages under the Clauses, the data importer will accept the decision of the data subject: +
        +
      1. to refer the dispute to mediation, by an independent person or, where applicable, by the supervisory authority; +
      2. to refer the dispute to the courts in the Member State in which the data exporter is established. +
      +
    2. The parties agree that the choice made by the data subject will not prejudice its substantive or procedural rights to seek remedies in accordance with other provisions of national or international law. +
    + +### Clause 8: Cooperation with supervisory authorities + +
      +
    1. The data exporter agrees to deposit a copy of this contract with the supervisory authority if it so requests or if such deposit is required under the applicable data protection law.
      2. + +
    2. The parties agree that the supervisory authority has the right to conduct an audit of the data importer, and of any subprocessor, which has the same scope and is subject to the same conditions as would apply to an audit of the data exporter under the applicable data protection law.
      3. + +
    3. The data importer shall promptly inform the data exporter about the existence of legislation applicable to it or any subprocessor preventing the conduct of an audit of the data importer, or any subprocessor, pursuant to paragraph 2. In such a case the data exporter shall be entitled to take the measures foreseen in Clause 5 (b).
      4. +
    + +### Clause 9: Governing Law. + +The Clauses shall be governed by the law of the Member State in which the data exporter is established. + +### Clause 10: Variation of the contract + +The parties undertake not to vary or modify the Clauses. This does not preclude the parties from adding clauses on business related issues where required as long as they do not contradict the Clause. + +### Clause 11: Subprocessing + +
      +
    1. The data importer shall not subcontract any of its processing operations performed on behalf of the data exporter under the Clauses without the prior written consent of the data exporter. Where the data importer subcontracts its obligations under the Clauses, with the consent of the data exporter, it shall do so only by way of a written agreement with the subprocessor which imposes the same obligations on the subprocessor as are imposed on the data importer under the Clauses. Where the subprocessor fails to fulfil its data protection obligations under such written agreement the data importer shall remain fully liable to the data exporter for the performance of the subprocessor's obligations under such agreement.
      2. + +
    2. The prior written contract between the data importer and the subprocessor shall also provide for a third-party beneficiary clause as laid down in Clause 3 for cases where the data subject is not able to bring the claim for compensation referred to in paragraph 1 of Clause 6 against the data exporter or the data importer because they have factually disappeared or have ceased to exist in law or have become insolvent and no successor entity has assumed the entire legal obligations of the data exporter or data importer by contract or by operation of law. Such third-party liability of the subprocessor shall be limited to its own processing operations under the Clauses.
      3. + +
    3. The provisions relating to data protection aspects for subprocessing of the contract referred to in paragraph 1 shall be governed by the law of the Member State in which the data exporter is established.
      4. + +
    4. The data exporter shall keep a list of subprocessing agreements concluded under the Clauses and notified by the data importer pursuant to Clause 5 (j), which shall be updated at least once a year. The list shall be available to the data exporter's data protection supervisory authority.
      5. +
    + +### Clause 12: Obligation after the termination of personal data processing services + +
      +
    1. The parties agree that on the termination of the provision of data processing services, the data importer and the subprocessor shall, at the choice of the data exporter, return all the personal data transferred and the copies thereof to the data exporter or shall destroy all the personal data and certify to the data exporter that it has done so, unless legislation imposed upon the data importer prevents it from returning or destroying all or part of the personal data transferred. In that case, the data importer warrants that it will guarantee the confidentiality of the personal data transferred and will not actively process the personal data transferred anymore.
      2. + +
    2. The data importer and the subprocessor warrant that upon request of the data exporter and/or of the supervisory authority, it will submit its data processing facilities for an audit of the measures referred to in paragraph 1.
      3. +
    + +### Appendix 1 to the Standard Contractual Clauses (UK) + +**Data exporter**: Customer is the data exporter. The data exporter is a user of Online Services or Professional Services as defined in the DPA and GitHub Customer Agreement. + +**Data importer**: The data importer is GitHub, Inc., a global producer of software and services. + +**Data subjects**: Data subjects include the data exporter’s representatives and end-users including employees, contractors, collaborators, and customers of the data exporter. Data subjects may also include individuals attempting to communicate or transfer personal data to users of the services provided by data importer. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following types of data subjects in the personal data: +- Employees, contractors and temporary workers (current, former, prospective) of data exporter; +- Data exporter's collaborators/contact persons (natural persons) or employees, contractors or temporary workers of legal entity collaborators/contact persons (current, prospective, former); +- Users and other data subjects that are users of data exporter's services; +- Partners, stakeholders or individuals who actively collaborate, communicate or otherwise interact with employees of the data exporter and/or use communication tools such as apps and websites provided by the data exporter. + +**Categories of data**: The personal data transferred that is included in e-mail, documents and other data in an electronic form in the context of the Online Services or Professional Services. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following categories in the personal data: +- Basic personal data (for example place of birth, street name and house number (address), postal code, city of residence, country of residence, mobile phone number, first name, last name, initials, email address, gender, date of birth); +- Authentication data (for example user name, password or PIN code, security question, audit trail); +- Contact information (for example addresses, email, phone numbers, social media identifiers; emergency contact details); +- Unique identification numbers and signatures (for example IP addresses, employee number, student number); +- Pseudonymous identifiers; +- Photos, video and audio; +- Internet activity (for example browsing history, search history, reading and viewing activities); +- Device identification (for example IMEI-number, SIM card number, MAC address); +- Profiling (for example based on observed criminal or anti-social behavior or pseudonymous profiles based on visited URLs, click streams, browsing logs, IP-addresses, domains, apps installed, or profiles based on marketing preferences); +- Special categories of data as voluntarily provided by data subjects (for example racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health, data concerning a natural person’s sex life or sexual orientation, or data relating to criminal convictions or offences); or +- Any other personal data identified in Article 4 of the GDPR. + +**Processing operations**: The personal data transferred will be subject to the following basic processing activities: + +
      +
    1. Duration and Object of Data Processing. The duration of data processing shall be for the term designated under the applicable GitHub Customer Agreement between data exporter and data importer. The objective of the data processing is the performance of Online Services and Professional Services.
      2. +
    2. Scope and Purpose of Data Processing. The scope and purpose of processing personal data is described in the “Processing of Personal Data; GDPR” section of the DPA. The data importer operates a global network of data centers and management/support facilities, and processing may take place in any jurisdiction where data importer or its sub-processors operate such facilities in accordance with the “Security Practices and Policies” section of the DPA.
      3. +
    3. Personal Data Access. For the term designated under the applicable GitHub Customer Agreement data importer will at its election and as necessary under applicable law, either: (1) provide data exporter with the ability to correct, delete, or block personal data, or (2) make such corrections, deletions, or blockages on its behalf.
      4. +
    4. Data Exporter’s Instructions. For Online Services and Professional Services, data importer will only act upon data exporter’s instructions as conveyed by GitHub.
      5. +
    5. Personal Data Deletion or Return. Upon expiration or termination of data exporter’s use of Online Services or Professional Services, it may extract personal data and data importer will delete personal data, each in accordance with the DPA Terms applicable to the agreement.
      6. +
    + +**Subcontractors**: In accordance with the DPA, the data importer may hire other companies to provide limited services on data importer’s behalf, such as providing customer support. Any such subcontractors will be permitted to obtain personal data only to deliver the services the data importer has retained them to provide, and they are prohibited from using personal data for any other purpose. + +### Appendix 2 to the Standard Contractual Clauses (UK) + +Description of the technical and organizational security measures implemented by the data importer in accordance with Clauses 4(d) and 5(c): + +
      +
    1. Personnel. Data importer’s personnel will not process personal data without authorization. Personnel are obligated to maintain the confidentiality of any such personal data and this obligation continues even after their engagement ends.
      2. + +
    2. Data Privacy Contact. The data privacy officer of the data importer can be reached at the following address:
      +GitHub, Inc.
      +Attn: Privacy
      +88 Colin P. Kelly Jr. Street
      +San Francisco, California 94107 USA
      3. + +
    3. Technical and Organization Measures. The data importer has implemented and will maintain appropriate technical and organizational measures, internal controls, and information security routines intended to protect personal data, as defined in the Security Practices and Policies section of the DPA, against accidental loss, destruction, or alteration; unauthorized disclosure or access; or unlawful destruction as follows: The technical and organizational measures, internal controls, and information security routines set forth in the Security Practices and Policies section of the DPA are hereby incorporated into this Appendix 2 by this reference and are binding on the data importer as if they were set forth in this Appendix 2 in their entirety.
      4. +
    + +### Appendix 3 to the Standard Contractual Clauses (UK) + +**Additional Safeguards Addendum** + +By this Additional Safeguards Addendum to Standard Contractual Clauses (UK) (this “Addendum”), GitHub, Inc. (“GitHub”) provides additional safeguards to Customer and additional redress to the data subjects to whom Customer’s personal data relates. + +This Addendum supplements and is made part of, but is not in variation or modification of, the Standard Contractual Clauses (UK). + +
      +
    1. Challenges to Orders. In addition to Clause 5(d)(i) of the Standard Contractual Clauses (UK), in the event GitHub receives an order from any third party for compelled disclosure of any personal data that has been transferred under the Standard Contractual Clauses (UK), GitHub shall:
      2. +
        +
      1. use every reasonable effort to redirect the third party to request data directly from Customer;
        2. +
      2. promptly notify Customer, unless prohibited under the law applicable to the requesting third party, and, if prohibited from notifying Customer, use all lawful efforts to obtain the right to waive the prohibition in order to communicate as much information to Customer as soon as possible; and
        3. +
      3. use all lawful efforts to challenge the order for disclosure on the basis of any legal deficiencies under the laws of the requesting party or any relevant conflicts with the law of the European Union or applicable Member State law.
        4. +

      + For purpose of this section, lawful efforts do not include actions that would result in civil or criminal penalty such as contempt of court under the laws of the relevant jurisdiction. +
    2. Indemnification of Data Subjects. Subject to Sections 3 and 4, GitHub shall indemnify a data subject for any material or non-material damage to the data subject caused by GitHub’s disclosure of personal data of the data subject that has been transferred under the Standard Contractual Clauses (UK) in response to an order from a non-EU/EEA government body or law enforcement agency (a “Relevant Disclosure”). Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under this Section 2 to the extent the data subject has already received compensation for the same damage, whether from GitHub or otherwise.
      3. +
    3. Conditions of Indemnification. Indemnification under Section 2 is conditional upon the data subject establishing, to GitHub’s reasonable satisfaction, that:
      4. +
        +
      1. GitHub engaged in a Relevant Disclosure;
        2. +
      2. the Relevant Disclosure was the basis of an official proceeding by the non-EU/EEA government body or law enforcement agency against the data subject; and
        3. +
      3. the Relevant Disclosure directly caused the data subject to suffer material or non-material damage.
        4. +

      + The data subject bears the burden of proof with respect to conditions a. though c.
      + Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under Section 2 if GitHub establishes that the Relevant Disclosure did not violate its obligations under Chapter V of the GDPR. +
    4. Scope of Damages. Indemnification under Section 2 is limited to material and non-material damages as provided in the GDPR and excludes consequential damages and all other damages not resulting from GitHub’s infringement of the GDPR.
      5. +
    5. Exercise of Rights. Rights granted to data subjects under this Addendum may be enforced by the data subject against GitHub irrespective of any restriction in Clauses 3 or 6 of the Standard Contractual Clauses (UK). The data subject may only bring a claim under this Addendum on an individual basis, and not part of a class, collective, group or representative action. Rights granted to data subjects under this Addendum are personal to the data subject and may not be assigned.
      6. +
    6. Notice of Change. In addition to Clause 5(b) of the Standard Contractual Clauses (UK), GitHub agrees and warrants that it has no reason to believe that the legislation applicable to it or its sub-processors, including in any country to which personal data is transferred either by itself or through a sub-processor, prevents it from fulfilling the instructions received from the data exporter and its obligations under this Addendum or the Standard Contractual Clauses (UK) and that in the event of a change in this legislation which is likely to have a substantial adverse effect on the warranties and obligations provided by this Addendum or the Standard Contractual Clauses (UK), it will promptly notify the change to Customer as soon as it is aware, in which case Customer is entitled to suspend the transfer of data and/or terminate the contract. +
    7. Termination. This Addendum shall automatically terminate if the European Commission, a competent Member State supervisory authority, or an EU or competent Member State court approves a different lawful transfer mechanism that would be applicable to the data transfers covered by the Standard Contractual Clauses (UK) (and if such mechanism applies only to some of the data transfers, this Addendum will terminate only with respect to those transfers) and that does not require the additional safeguards set forth in this Addendum.

      + Signing the Standard Contractual Clauses (UK), Appendix 1, Appendix 2 and +
    + +

    Attachment 3 – European Union General Data Protection Regulation Terms

    + +GitHub makes the commitments in these GDPR Related Terms, to all customers effective May 25, 2018. These commitments are binding upon GitHub with regard to Customer regardless of (1) the version of the GitHub Customer Agreement and DPA that is otherwise applicable to any given Online Services subscription or (2) any other agreement that references this attachment. + +For purposes of these GDPR Related Terms, Customer and GitHub agree that Customer is the controller of Personal Data and GitHub is the processor of such data, except when Customer acts as a processor of Personal Data, in which case GitHub is a subprocessor. These GDPR Related Terms apply to the processing of Personal Data, within the scope of the GDPR, by GitHub on behalf of Customer. These GDPR Related Terms do not limit or reduce any data protection commitments GitHub makes to Customer in the GitHub Customer Agreement or other agreement between GitHub and Customer. These GDPR Related Terms do not apply where GitHub is a controller of Personal Data. + +**Relevant GDPR Obligations: Articles 28, 32, and 33** + +
      +
    1. GitHub shall not engage another processor without prior specific or general written authorisation of Customer. In the case of general written authorisation, GitHub shall inform Customer of any intended changes concerning the addition or replacement of other processors, thereby giving Customer the opportunity to object to such changes. (Article 28(2))
      2. +
    2. Processing by GitHub shall be governed by these GDPR Related Terms under European Union (hereafter “Union”) or Member State law and are binding on GitHub with regard to Customer. The subject-matter and duration of the processing, the nature and purpose of the processing, the type of Personal Data, the categories of data subjects and the obligations and rights of the Customer are set forth in the Customer’s licensing agreement, including these GDPR Related Terms. In particular, GitHub shall:
      3. +
        +
      1. process the Personal Data only on documented instructions from Customer, including with regard to transfers of Personal Data to a third country or an international organisation, unless required to do so by Union or Member State law to which GitHub is subject; in such a case, GitHub shall inform Customer of that legal requirement before processing, unless that law prohibits such information on important grounds of public interest;
        2. +
      2. ensure that persons authorised to process the Personal Data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality;
        3. +
      3. take all measures required pursuant to Article 32 of the GDPR;
        4. +
      4. respect the conditions referred to in paragraphs 1 and 3 for engaging another processor;
        5. +
      5. taking into account the nature of the processing, assist Customer by appropriate technical and organisational measures, insofar as this is possible, for the fulfilment of the Customer’s obligation to respond to requests for exercising the data subject's rights laid down in Chapter III of the GDPR;
        6. +
      6. assist Customer in ensuring compliance with the obligations pursuant to Articles 32 to 36 of the GDPR, taking into account the nature of processing and the information available to GitHub;
        7. +
      7. at the choice of Customer, delete or return all the Personal Data to Customer after the end of the provision of services relating to processing, and delete existing copies unless Union or Member State law requires storage of the Personal Data;
        8. +
      8. make available to Customer all information necessary to demonstrate compliance with the obligations laid down in Article 28 of the GDPR and allow for and contribute to audits, including inspections, conducted by Customer or another auditor mandated by Customer.
        9. +

      + GitHub shall immediately inform Customer if, in its opinion, an instruction infringes the GDPR or other Union or Member State data protection provisions. (Article 28(3))

      +
    3. Where GitHub engages another processor for carrying out specific processing activities on behalf of Customer, the same data protection obligations as set out in these GDPR Related Terms shall be imposed on that other processor by way of a contract or other legal act under Union or Member State law, in particular providing sufficient guarantees to implement appropriate technical and organisational measures in such a manner that the processing will meet the requirements of the GDPR. Where that other processor fails to fulfil its data protection obligations, GitHub shall remain fully liable to the Customer for the performance of that other processor's obligations. (Article 28(4))
      4. +
    4. Taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of processing as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons, Customer and GitHub shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, including inter alia as appropriate:
      5. +
        +
      1. the pseudonymisation and encryption of Personal Data;
        2. +
      2. the ability to ensure the ongoing confidentiality, integrity, availability and resilience of processing systems and services;
        3. +
      3. the ability to restore the availability and access to Personal Data in a timely manner in the event of a physical or technical incident; and
        4. +
      4. a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the processing. (Article 32(1))
        5. +
      +
    5. In assessing the appropriate level of security, account shall be taken of the risks that are presented by processing, in particular from accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to Personal Data transmitted, stored or otherwise processed (Article 32(2)).
      6. +
    6. Customer and GitHub shall take steps to ensure that any natural person acting under the authority of Customer or GitHub who has access to Personal Data does not process them except on instructions from Customer, unless he or she is required to do so by Union or Member State law (Article 32(4)).
      7. +
    7. GitHub shall notify Customer without undue delay after becoming aware of a Personal Data breach (Article 33(2)). Such notification will include that information a processor must provide to a controller under Article 33(3) to the extent such information is reasonably available to GitHub.
      8. +
    + +--------------- + +

    (1) The Agreement on the European Economic Area (EEA Agreement) provides for the extension of the European Union’s internal market to the three EEA States Iceland, Liechtenstein and Norway. The Union data protection legislation, including Regulation (EU) 2016/679, is covered by the EEA Agreement and has been incorporated into Annex XI thereto. Therefore, any disclosure by the data importer to a third party located in the EEA does not qualify as an onward transfer for the purpose of these Clauses.

    + +

    (2) This requirement may be satisfied by the sub-processor acceding to these Clauses under the appropriate Module, in accordance with Clause 7.

    + +

    (3) As regards the impact of such laws and practices on compliance with these Clauses, different elements may be considered as part of an overall assessment. Such elements may include relevant and documented practical experience with prior instances of requests for disclosure from public authorities, or the absence of such requests, covering a sufficiently representative time-frame. This refers in particular to internal records or other documentation, drawn up on a continuous basis in accordance with due diligence and certified at senior management level, provided that this information can be lawfully shared with third parties. Where this practical experience is relied upon to conclude that the data importer will not be prevented from complying with these Clauses, it needs to be supported by other relevant, objective elements, and it is for the Parties to consider carefully whether these elements together carry sufficient weight, in terms of their reliability and representativeness, to support this conclusion. In particular, the Parties have to take into account whether their practical experience is corroborated and not contradicted by publicly available or otherwise accessible, reliable information on the existence or absence of requests within the same sector and/or the application of the law in practice, such as case law and reports by independent oversight bodies.

    diff --git a/translations/ko-KR/content/github/site-policy/github-terms-for-additional-products-and-features.md b/translations/ko-KR/content/github/site-policy/github-terms-for-additional-products-and-features.md index 1765ec8989..1ada6b768c 100644 --- a/translations/ko-KR/content/github/site-policy/github-terms-for-additional-products-and-features.md +++ b/translations/ko-KR/content/github/site-policy/github-terms-for-additional-products-and-features.md @@ -20,7 +20,7 @@ By using the Additional Products and Features, you also agree to the applicable - **GitHub Enterprise Server** users may have access to the following Additional Products and Features: Actions, Advanced Security, Advisory Database, Connect, Dependabot Preview, Learning Lab, Octoshift, Packages, Pages and SQL Server Images. -- **GitHub AE** users may have access to the following Additional Products and Features: Actions, Advanced Security, Advisory Database, {% ifversion ghae-next %}Connect, {% endif %}Dependabot Preview, Octoshift, Packages and Pages. +- **GitHub AE** users may have access to the following Additional Products and Features: Actions, Advanced Security, Advisory Database,{% ifversion ghae-next %}Connect, {% endif %}Dependabot Preview, Octoshift, Packages and Pages. ## Actions GitHub Actions enables you to create custom software development lifecycle workflows directly in your GitHub repository. Actions is billed on a usage basis. The [Actions documentation](/actions) includes details, including compute and storage quantities (depending on your Account plan), and how to monitor your Actions minutes usage and set usage limits. @@ -38,7 +38,7 @@ In order to prevent violations of these limitations and abuse of GitHub Actions, ## Advanced Security GitHub makes extra security features available to customers under an Advanced Security license. These features include code scanning, secret scanning, and dependency review. The [Advanced Security documentation](/github/getting-started-with-github/about-github-advanced-security) provides more details. -Advanced Security is licensed on a "Unique Committer" basis. A "Unique Committer" is a licensed user of GitHub Enterprise, GitHub Enterprise Cloud, GitHub Enterprise Server, or GitHub AE, who has made a code commit in the last 90 days to any repository with any GitHub Advanced Security functionality activated. You must acquire a GitHub Advanced Security User license for each of your Unique Committers. You may only use GitHub Advanced Security on codebases that are developed by or for you. For GitHub Enterprise Cloud users, some Advanced Security features also require the use of GitHub Actions. +Advanced Security is licensed on a "Unique Committer" basis. A "Unique Committer" is a licensed user of GitHub Enterprise, GitHub Enterprise Cloud, GitHub Enterprise Server, or GitHub AE, who has made a commit in the last 90 days to any repository with any GitHub Advanced Security functionality activated. You must acquire a GitHub Advanced Security User license for each of your Unique Committers. You may only use GitHub Advanced Security on codebases that are developed by or for you. For GitHub Enterprise Cloud users, some Advanced Security features also require the use of GitHub Actions. ## Advisory Database The GitHub Advisory Database allows you to browse or search for vulnerabilities that affect open source projects on GitHub. diff --git a/translations/ko-KR/content/github/site-policy/index.md b/translations/ko-KR/content/github/site-policy/index.md index b4ea2b422b..80677f1a31 100644 --- a/translations/ko-KR/content/github/site-policy/index.md +++ b/translations/ko-KR/content/github/site-policy/index.md @@ -12,7 +12,7 @@ children: - /github-terms-of-service - /github-corporate-terms-of-service - /github-privacy-statement - - /github-data-protection-agreement-non-enterprise-customers + - /github-data-protection-agreement - /global-privacy-practices - /github-sponsors-additional-terms - /github-codespaces-privacy-statement diff --git a/translations/ko-KR/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md b/translations/ko-KR/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md index 36cf4b4390..ade7ddd75b 100644 --- a/translations/ko-KR/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md +++ b/translations/ko-KR/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md @@ -1,6 +1,7 @@ --- title: Creating gists intro: 'You can create two kinds of gists: {% ifversion ghae %}internal{% else %}public{% endif %} and secret. Create {% ifversion ghae %}an internal{% else %}a public{% endif %} gist if you''re ready to share your ideas with {% ifversion ghae %}enterprise members{% else %}the world{% endif %} or a secret gist if you''re not.' +permissions: '{% data reusables.enterprise-accounts.emu-permission-gist %}' redirect_from: - /articles/about-gists/ - /articles/cannot-delete-an-anonymous-gist/ @@ -42,7 +43,7 @@ You can pin gists to your profile so other people can see them easily. For more {% endif %} -You can discover {% ifversion ghae %}internal{% else %}public{% endif %} gists others have created by going to the {% data variables.gists.gist_homepage %} and clicking **All Gists**. This will take you to a page of all gists sorted and displayed by time of creation or update. You can also search gists by language with {% data variables.gists.gist_search_url %}. Gist search uses the same search syntax as [code search](/articles/searching-code). +You can discover {% ifversion ghae %}internal{% else %}public{% endif %} gists others have created by going to the {% data variables.gists.gist_homepage %} and clicking **All Gists**. This will take you to a page of all gists sorted and displayed by time of creation or update. You can also search gists by language with {% data variables.gists.gist_search_url %}. Gist search uses the same search syntax as [code search](/search-github/searching-on-github/searching-code). Since gists are Git repositories, you can view their full commit history, complete with diffs. You can also fork or clone gists. For more information, see ["Forking and cloning gists"](/articles/forking-and-cloning-gists). diff --git a/translations/ko-KR/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md b/translations/ko-KR/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md index 94e12c96b9..35202d29ce 100644 --- a/translations/ko-KR/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md +++ b/translations/ko-KR/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md @@ -1,6 +1,7 @@ --- title: Forking and cloning gists intro: 'Gists are actually Git repositories, which means that you can fork or clone any gist, even if you aren''t the original author. You can also view a gist''s full commit history, including diffs.' +permissions: '{% data reusables.enterprise-accounts.emu-permission-gist %}' redirect_from: - /articles/forking-and-cloning-gists - /github/writing-on-github/forking-and-cloning-gists diff --git a/translations/ko-KR/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md b/translations/ko-KR/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md index b04cd1567c..4fcef7abdf 100644 --- a/translations/ko-KR/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md +++ b/translations/ko-KR/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md @@ -40,9 +40,9 @@ You can indicate emphasis with bold, italic, or strikethrough text in comment fi You can quote text with a `>`. ```markdown -In the words of Abraham Lincoln: +Text that is not a quote -> Pardon my French +> Text that is a quote ``` ![Rendered quoted text](/assets/images/help/writing/quoted-text-rendered.png) @@ -184,7 +184,7 @@ In this example, you could add a nested list item under the list item `100. Firs ![List with a nested list item](/assets/images/help/writing/nested-list-example-3.png) -You can create multiple levels of nested lists using the same method. For example, because the first nested list item has seven spaces (`␣␣␣␣␣-␣`) before the nested list content `First nested list item`, you would need to indent the second nested list item by seven spaces. +You can create multiple levels of nested lists using the same method. For example, because the first nested list item has seven characters (`␣␣␣␣␣-␣`) before the nested list content `First nested list item`, you would need to indent the second nested list item by seven spaces. ```markdown 100. First list item @@ -262,6 +262,30 @@ 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-next or ghes > 3.3 %} +## Footnotes + +You can add footnotes to your content by using this bracket syntax: + +``` +Here is a simple footnote[^1]. + +[^1]: My reference. +``` + +The footnote will render like this: + +![Rendered footnote](/assets/images/site/rendered-footnote.png) +{% endif %} + +## Hiding content with comments + +You can tell {% data variables.product.product_name %} to hide content from the rendered Markdown by placing the content in an HTML comment. + +
    +<!-- This content will not appear in the rendered Markdown -->
+
    + ## Ignoring Markdown formatting You can tell {% data variables.product.product_name %} to ignore (or escape) Markdown formatting by using `\` before the Markdown character. @@ -272,13 +296,13 @@ You can tell {% data variables.product.product_name %} to ignore (or escape) Mar For more information, see Daring Fireball's "[Markdown Syntax](https://daringfireball.net/projects/markdown/syntax#backslash)." -## Hiding content with comments +{% ifversion fpt or ghes > 3.2 or ghae-issue-5232 %} -You can tell {% data variables.product.product_name %} to hide content from the rendered Markdown by placing the content in an HTML comment. +## Disabling Markdown rendering -
    -<!-- This content will not appear in the rendered Markdown -->
-
    +{% data reusables.repositories.disabling-markdown-rendering %} + +{% endif %} ## 더 읽을거리 diff --git a/translations/ko-KR/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md b/translations/ko-KR/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md index 69e20a133a..42dde65c04 100644 --- a/translations/ko-KR/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md +++ b/translations/ko-KR/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md @@ -16,7 +16,7 @@ topics: {% warning %} -**Warning:** If you add an image {% ifversion fpt or ghes > 3.1 or ghae-next %} or video {% endif %} to a pull request or issue comment, anyone can view the anonymized URL without authentication, even if the pull request is in a private repository{% ifversion ghes %}, or if private mode is enabled{% endif %}. To keep sensitive media files private, serve them from a private network or server that requires authentication. {% ifversion fpt %}For more information on anonymized URLs see "[About anonymized URLs](/github/authenticating-to-github/about-anonymized-urls)".{% endif %} +**Warning:** If you add an image{% ifversion fpt or ghes > 3.1 or ghae-next %} or video{% endif %} to a pull request or issue comment, anyone can view the anonymized URL without authentication, even if the pull request is in a private repository{% ifversion ghes %}, or if private mode is enabled{% endif %}. To keep sensitive media files private, serve them from a private network or server that requires authentication. {% ifversion fpt %}For more information on anonymized URLs see "[About anonymized URLs](/github/authenticating-to-github/about-anonymized-urls)".{% endif %} {% endwarning %} @@ -31,9 +31,10 @@ To attach a file to an issue or pull request conversation, drag and drop it into {% endtip %} The maximum file size is: -- 10MB for images and gifs{% ifversion fpt or ghes > 3.1 or ghae-next %} +- 10MB for images and gifs{% ifversion fpt %} - 10MB for videos uploaded to a repository owned by a user or organization on a free GitHub plan -- 100MB for videos uploaded to a repository owned by a user or organization on a paid GitHub plan{% endif %} +- 100MB for videos uploaded to a repository owned by a user or organization on a paid GitHub plan{% elsif fpt or ghes > 3.1 or ghae-next %} +- 100MB for videos{% endif %} - 25MB for all other files We support these files: diff --git a/translations/ko-KR/content/graphql/guides/managing-enterprise-accounts.md b/translations/ko-KR/content/graphql/guides/managing-enterprise-accounts.md index ece4f89705..f97c8e6f93 100644 --- a/translations/ko-KR/content/graphql/guides/managing-enterprise-accounts.md +++ b/translations/ko-KR/content/graphql/guides/managing-enterprise-accounts.md @@ -58,8 +58,9 @@ For some example queries, see "[An example query using the Enterprise Accounts A - `admin:enterprise` The enterprise account specific scopes are: - - `admin:enterprise`: Gives full control of enterprises (includes `manage_billing:enterprise` and `read:enterprise`) - - `manage_billing:enterprise`: Read and write enterprise billing data. + - `admin:enterprise`: Gives full control of enterprises (includes {% ifversion ghes > 3.2 or fpt or ghae %}`manage_runners:enterprise`, {% endif %}`manage_billing:enterprise` and `read:enterprise`) + - `manage_billing:enterprise`: Read and write enterprise billing data.{% ifversion ghes > 3.2 or fpt or ghae %} + - `manage_runners:enterprise`: Access to manage GitHub Actions enterprise runners and runner-groups.{% endif %} - `read:enterprise`: Read enterprise profile data. 4. Copy your personal access token and keep it in a secure place until you add it to your GraphQL client. diff --git a/translations/ko-KR/content/graphql/guides/using-the-graphql-api-for-discussions.md b/translations/ko-KR/content/graphql/guides/using-the-graphql-api-for-discussions.md index 076f5787d6..0e7850ae6d 100644 --- a/translations/ko-KR/content/graphql/guides/using-the-graphql-api-for-discussions.md +++ b/translations/ko-KR/content/graphql/guides/using-the-graphql-api-for-discussions.md @@ -1080,4 +1080,4 @@ Return type fields: ## 검색 -Discussion may be returned from the top-level `search` field. To search for discussion, specify `type` as `DISCUSSION`. The `SearchResultItemConnection` type has a `discussionCount` field to report the number of returned discussions, and the `Discussion` type is added to the `SearchResultItem` union. For more information, see "[Queries](/graphql/reference/queries#searchresultitemconnection)" and "[Searching discussions](/github/searching-for-information-on-github/searching-discussions)." +Discussion may be returned from the top-level `search` field. To search for discussion, specify `type` as `DISCUSSION`. The `SearchResultItemConnection` type has a `discussionCount` field to report the number of returned discussions, and the `Discussion` type is added to the `SearchResultItem` union. For more information, see "[Queries](/graphql/reference/queries#searchresultitemconnection)" and "[Searching discussions](/search-github/searching-on-github/searching-discussions)." diff --git a/translations/ko-KR/content/index.md b/translations/ko-KR/content/index.md index 12ab7e6cd6..3a7fea8970 100644 --- a/translations/ko-KR/content/index.md +++ b/translations/ko-KR/content/index.md @@ -27,6 +27,7 @@ children: - actions - codespaces - packages + - search-github - developers - rest - graphql diff --git a/translations/ko-KR/content/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users.md b/translations/ko-KR/content/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users.md index 5cf52b4f8e..c0b83ffa76 100644 --- a/translations/ko-KR/content/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users.md +++ b/translations/ko-KR/content/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users.md @@ -1,6 +1,7 @@ --- title: Assigning issues and pull requests to other GitHub users intro: Assignees clarify who is working on specific issues and pull requests. +permissions: 'Anyone with write access to a repository can assign issues and pull requests. {% data reusables.enterprise-accounts.emu-permission-repo %}' redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/assigning-issues-and-pull-requests-to-other-github-users - /articles/assigning-issues-and-pull-requests-to-other-github-users @@ -15,8 +16,6 @@ topics: shortTitle: Assign issues & PRs --- -Anyone with write permissions to a repository can assign issues and pull requests. - ## About issue and pull request assignees You can assign up to 10 people to each issue or pull request, including yourself, anyone who has commented on the issue or pull request, anyone with write permissions to the repository, and organization members with read permissions to the repository. For more information, see "[Access permissions on {% data variables.product.prodname_dotcom %}](/articles/access-permissions-on-github)." diff --git a/translations/ko-KR/content/issues/tracking-your-work-with-issues/creating-an-issue.md b/translations/ko-KR/content/issues/tracking-your-work-with-issues/creating-an-issue.md index 726632abb0..f9da609d72 100644 --- a/translations/ko-KR/content/issues/tracking-your-work-with-issues/creating-an-issue.md +++ b/translations/ko-KR/content/issues/tracking-your-work-with-issues/creating-an-issue.md @@ -1,7 +1,7 @@ --- title: Creating an issue intro: 'Issues can be created in a variety of ways, so you can choose the most convenient method for your workflow.' -permissions: People with read permissions can create an issue in a repository where issues are enabled. +permissions: 'People with read access can create an issue in a repository where issues are enabled. {% data reusables.enterprise-accounts.emu-permission-repo %}' redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/creating-an-issue - /articles/creating-an-issue diff --git a/translations/ko-KR/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md b/translations/ko-KR/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md index f8121f5ecd..073be18cc0 100644 --- a/translations/ko-KR/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md +++ b/translations/ko-KR/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md @@ -102,7 +102,8 @@ You can filter a repository's list of pull requests to find: - Pull requests that [require a review](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging) before they can be merged - Pull requests that a reviewer has approved - Pull requests in which a reviewer has asked for changes -- Pull requests that you have reviewed +- Pull requests that you have reviewed{% ifversion fpt or ghae or ghes > 3.2 %} +- Pull requests that someone has asked you directly to review{% endif %} - Pull requests that [someone has asked you, or a team you're a member of, to review](/articles/requesting-a-pull-request-review) {% data reusables.repositories.navigate-to-repo %} @@ -185,7 +186,8 @@ For pull requests, you can also use search to: - Filter pull requests that a reviewer has approved: `state:open type:pr review:approved` - Filter pull requests in which a reviewer has asked for changes: `state:open type:pr review:changes_requested` - 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](/articles/requesting-a-pull-request-review): `state:open type:pr review-requested:octocat` +- Filter pull requests by the specific user [requested for review](/articles/requesting-a-pull-request-review): `state:open type:pr review-requested:octocat`{% ifversion fpt or ghae or ghes > 3.2 %} +- 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 %} - Filter for pull requests that are linked to an issue that the pull request may close: `linked:issue`{% endif %} diff --git a/translations/ko-KR/content/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository.md b/translations/ko-KR/content/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository.md index 6d5db5b0f7..32d493a909 100644 --- a/translations/ko-KR/content/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository.md +++ b/translations/ko-KR/content/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository.md @@ -1,6 +1,7 @@ --- title: Pinning an issue to your repository intro: You can pin up to three important issues above the issues list in your repository. +permissions: 'People with write access to a repository can pin issue in the repository. {% data reusables.enterprise-accounts.emu-permission-repo %}' redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/pinning-an-issue-to-your-repository - /articles/pinning-an-issue-to-your-repository @@ -17,8 +18,6 @@ shortTitle: Pin an issue ![Pinned issues](/assets/images/help/issues/pinned-issues.png) -To pin an issue, you must have write permissions for the repository the issue is in. - {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issues %} 1. In the list of issues, click the issue you'd like to pin. diff --git a/translations/ko-KR/content/issues/tracking-your-work-with-issues/quickstart.md b/translations/ko-KR/content/issues/tracking-your-work-with-issues/quickstart.md index 3149038c15..b72627f1ff 100644 --- a/translations/ko-KR/content/issues/tracking-your-work-with-issues/quickstart.md +++ b/translations/ko-KR/content/issues/tracking-your-work-with-issues/quickstart.md @@ -19,7 +19,7 @@ This guide demonstrates how to use {% data variables.product.prodname_github_iss ## 빌드전 요구 사양 -To create an issue, you need a repository. You can use an existing repository that you have write access to, or you can create a new repository. The repository must have issues enabled. For more information about creating a repository, see "[Creating a new repository](/articles/creating-a-new-repository)." For more information about enabling issues if they are disabled in your repository, see "[Disabling issues](/github/administering-a-repository/managing-repository-settings/disabling-issues)." +To create an issue, you need a repository. You can use an existing repository that you have write access to, or you can create a new repository. {% data reusables.enterprise-accounts.emu-permission-repo %} The repository must have issues enabled. For more information about creating a repository, see "[Creating a new repository](/articles/creating-a-new-repository)." For more information about enabling issues if they are disabled in your repository, see "[Disabling issues](/github/administering-a-repository/managing-repository-settings/disabling-issues)." ## Opening a blank issue diff --git a/translations/ko-KR/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md b/translations/ko-KR/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md index a59854f438..8ea8c58145 100644 --- a/translations/ko-KR/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md +++ b/translations/ko-KR/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md @@ -1,6 +1,7 @@ --- title: Managing labels intro: 'You can classify {% ifversion fpt %}issues, pull requests, and discussions{% else %}issues and pull requests{% endif %} by creating, editing, applying, and deleting labels.' +permissions: '{% data reusables.enterprise-accounts.emu-permission-repo %}' redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/managing-labels - /articles/managing-Labels @@ -30,8 +31,6 @@ topics: You can manage your work on {% data variables.product.product_name %} by creating labels to categorize {% ifversion fpt %}issues, pull requests, and discussions{% else %}issues and pull requests{% endif %}. You can apply labels in the repository the label was created in. Once a label exists, you can use the label on any {% ifversion fpt %}issue, pull request, or discussion{% else %}issue or pull request{% endif %} within that repository. -Anyone with read access to a repository can view and search the repository’s labels. Anyone with triage access to a repository can apply/dismiss existing labels. To create, edit, apply, or delete a label, you must have write access to the repository. - ## About default labels {% data variables.product.product_name %} provides default labels in every new repository. You can use these default labels to help create a standard workflow in a repository. @@ -58,6 +57,8 @@ Organization owners can customize the default labels for repositories in their o ## Creating a label +Anyone with write access to a repository can create a label. + {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} {% data reusables.project-management.labels %} @@ -69,11 +70,15 @@ Organization owners can customize the default labels for repositories in their o ## Applying a label +Anyone with triage access to a repository can apply and dismiss labels. + 1. Navigate to the {% ifversion fpt %}issue, pull request, or discussion{% else %}issue or pull request{% endif %}. 1. In the right sidebar, to the right of "Labels", click {% octicon "gear" aria-label="The gear icon" %}, then click a label. !["Labels" drop-down menu](/assets/images/help/issues/labels-drop-down.png) ## Editing a label +Anyone with write access to a repository can edit existing labels. + {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} {% data reusables.project-management.labels %} @@ -85,6 +90,8 @@ Organization owners can customize the default labels for repositories in their o ## Deleting a label +Anyone with write access to a repository can delete existing labels. + Deleting a label will remove the label from issues and pull requests. {% data reusables.repositories.navigate-to-repo %} diff --git a/translations/ko-KR/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md b/translations/ko-KR/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md index 082974d281..3833fc0b9b 100644 --- a/translations/ko-KR/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md +++ b/translations/ko-KR/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md @@ -24,6 +24,8 @@ Enterprise accounts allow owners to centrally manage policy and billing for mult For organizations that belong to an enterprise account, billing is managed at the enterprise account level, and billing settings are not available at the organization level. Enterprise owners can set policy for all organizations in the enterprise account or allow organization owners to set the policy at the organization level. Organization owners cannot change settings enforced for your organization at the enterprise account level. If you have questions about a policy or setting for your organization, contact the owner of your enterprise account. +{% data reusables.enterprise-accounts.invite-organization %} + {% data reusables.gated-features.enterprise-accounts %} {% data reusables.organizations.org-ownership-recommendation %} For more information, see "[Maintaining ownership continuity for your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)." diff --git a/translations/ko-KR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md b/translations/ko-KR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md index f4fce88cba..3b44c10f41 100644 --- a/translations/ko-KR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md +++ b/translations/ko-KR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md @@ -25,6 +25,18 @@ You can view and revoke each member's linked identity, active sessions, and auth {% data reusables.saml.about-linked-identities %} +When available, the entry will include SCIM data. For more information, see "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)." + +{% warning %} + +**Warning:** For organizations using SCIM: +- Revoking a linked user identity on {% data variables.product.product_name %} will also remove the SAML and SCIM metadata. As a result, the identity provider will not be able to synchronize or deprovision the linked user identity. +- An admin must revoke a linked identity through the identity provider. +- To revoke a linked identity and link a different account through the identity provider, an admin can remove and re-assign the user to the {% data variables.product.product_name %} application. For more information, see your identity provider's documentation. + +{% endwarning %} + + {% data reusables.identity-and-permissions.revoking-identity-team-sync %} {% data reusables.profile.access_org %} diff --git a/translations/ko-KR/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md b/translations/ko-KR/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md index c402465209..61ae0eac7e 100644 --- a/translations/ko-KR/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md +++ b/translations/ko-KR/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md @@ -50,6 +50,8 @@ To search for specific events, use the `action` qualifier in your query. Actions | [`엔터프라이즈`](#enterprise-category-actions) | Contains activities related to enterprise settings. |{% endif %} | [`후크`](#hook-category-actions) | Contains all activities related to webhooks. | | [`integration_installation_request`](#integration_installation_request-category-actions) | Contains all activities related to organization member requests for owners to approve integrations for use in the organization. | +| [`ip_allow_list`](#ip_allow_list) | Contains activitites related to enabling or disabling the IP allow list for an organization. | +| [`ip_allow_list_entry`](#ip_allow_list_entry) | Contains activities related to the creation, deletion, and editing of an IP allow list entry for an organization. | | [`이슈`](#issue-category-actions) | Contains activities related to deleting an issue. |{% ifversion fpt %} | [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | Contains all activities related to signing the {% data variables.product.prodname_marketplace %} Developer Agreement. | | [`marketplace_listing`](#marketplace_listing-category-actions) | Contains all activities related to listing apps in {% data variables.product.prodname_marketplace %}.{% endif %}{% ifversion fpt or ghes > 3.0 %} @@ -337,6 +339,23 @@ An overview of some of the most common actions that are recorded as events in th | `create` | Triggered when an organization member requests that an organization owner install an integration for use in the organization. | | `close` | Triggered when a request to install an integration for use in an organization is either approved or denied by an organization owner, or canceled by the organization member who opened the request. | +### `ip_allow_list` category actions + +| 동작 | 설명 | +| ---------------------------- | --------------------------------------------------------------------------------------------------------------- | +| `활성화` | Triggered when an IP allow list was enabled for an organization. | +| `비활성화` | Triggered when an IP allow list was disabled for an organization. | +| `enable_for_installed_apps` | Triggered when an IP allow list was enabled for installed {% data variables.product.prodname_github_apps %}. | +| `disable_for_installed_apps` | Triggered when an IP allow list was disabled for installed {% data variables.product.prodname_github_apps %}. | + +### `ip_allow_list_entry` category actions + +| 동작 | 설명 | +| --------- | --------------------------------------------------------------- | +| `create` | Triggered when an IP address was added to an IP allow list. | +| `업데이트` | Triggered when an IP address or its description was changed. | +| `destroy` | Triggered when an IP address was deleted from an IP allow list. | + ### `issue` category actions | 동작 | 설명 | diff --git a/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md index b5892f839e..f4d4a40226 100644 --- a/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md +++ b/translations/ko-KR/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md @@ -54,95 +54,96 @@ Some of the features listed below are limited to organizations using {% data var {% endnote %} {% endif %} -| Repository action | Read | 심사 | Write | Maintain | Admin | -|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-----:|:-----:|:--------:|:------------------------------------------------:| -| Pull from the person or team's assigned repositories | **X** | **X** | **X** | **X** | **X** | -| Fork the person or team's assigned repositories | **X** | **X** | **X** | **X** | **X** | -| Edit and delete their own comments | **X** | **X** | **X** | **X** | **X** | -| Open issues | **X** | **X** | **X** | **X** | **X** | -| Close issues they opened themselves | **X** | **X** | **X** | **X** | **X** | -| Reopen issues they closed themselves | **X** | **X** | **X** | **X** | **X** | -| Have an issue assigned to them | **X** | **X** | **X** | **X** | **X** | -| Send pull requests from forks of the team's assigned repositories | **X** | **X** | **X** | **X** | **X** | -| Submit reviews on pull requests | **X** | **X** | **X** | **X** | **X** | -| View published releases | **X** | **X** | **X** | **X** | **X** |{% ifversion fpt %} -| View [GitHub Actions workflow runs](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **X** | **X** | **X** | **X** | **X** +| Repository action | Read | 심사 | Write | Maintain | Admin | +|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-----:|:-----:|:--------:|:-----------------------------------------------------:| +| Pull from the person or team's assigned repositories | **X** | **X** | **X** | **X** | **X** | +| Fork the person or team's assigned repositories | **X** | **X** | **X** | **X** | **X** | +| Edit and delete their own comments | **X** | **X** | **X** | **X** | **X** | +| Open issues | **X** | **X** | **X** | **X** | **X** | +| Close issues they opened themselves | **X** | **X** | **X** | **X** | **X** | +| Reopen issues they closed themselves | **X** | **X** | **X** | **X** | **X** | +| Have an issue assigned to them | **X** | **X** | **X** | **X** | **X** | +| Send pull requests from forks of the team's assigned repositories | **X** | **X** | **X** | **X** | **X** | +| Submit reviews on pull requests | **X** | **X** | **X** | **X** | **X** | +| View published releases | **X** | **X** | **X** | **X** | **X** |{% ifversion fpt %} +| View [GitHub Actions workflow runs](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **X** | **X** | **X** | **X** | **X** {% endif %} -| Edit wikis | **X** | **X** | **X** | **X** | **X** |{% ifversion fpt %} -| [Report abusive or spammy content](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** +| Edit wikis in public repositories | **X** | **X** | **X** | **X** | **X** | +| Edit wikis in private repositories | | | **X** | **X** | **X** |{% ifversion fpt %} +| [Report abusive or spammy content](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** {% endif %} -| Apply/dismiss labels | | **X** | **X** | **X** | **X** | -| Create, edit, delete labels | | | **X** | **X** | **X** | -| Close, reopen, and assign all issues and pull requests | | **X** | **X** | **X** | **X** |{% ifversion fpt or ghae or ghes > 3.0 %} -| [Enable and disable auto-merge on a pull request](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** +| Apply/dismiss labels | | **X** | **X** | **X** | **X** | +| Create, edit, delete labels | | | **X** | **X** | **X** | +| Close, reopen, and assign all issues and pull requests | | **X** | **X** | **X** | **X** |{% ifversion fpt or ghae or ghes > 3.0 %} +| [Enable and disable auto-merge on a pull request](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** {% endif %} -| Apply milestones | | **X** | **X** | **X** | **X** | -| Mark [duplicate issues and pull requests](/articles/about-duplicate-issues-and-pull-requests) | | **X** | **X** | **X** | **X** | -| Request [pull request reviews](/articles/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** | -| Merge a [pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges) | | | **X** | **X** | **X** | -| Push to (write) the person or team's assigned repositories | | | **X** | **X** | **X** | -| Edit and delete anyone's comments on commits, pull requests, and issues | | | **X** | **X** | **X** | -| [Hide anyone's comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **X** | **X** | **X** | -| [Lock conversations](/communities/moderating-comments-and-conversations/locking-conversations) | | | **X** | **X** | **X** | -| Transfer issues (see "[Transferring an issue to another repository](/articles/transferring-an-issue-to-another-repository)" for details) | | | **X** | **X** | **X** | -| [Act as a designated code owner for a repository](/articles/about-code-owners) | | | **X** | **X** | **X** | -| [Mark a draft pull request as ready for review](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | -| [Convert a pull request to a draft](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | -| Submit reviews that affect a pull request's mergeability | | | **X** | **X** | **X** | -| [Apply suggested changes](/articles/incorporating-feedback-in-your-pull-request) to pull requests | | | **X** | **X** | **X** | -| Create [status checks](/articles/about-status-checks) | | | **X** | **X** | **X** |{% ifversion fpt %} -| Create, edit, run, re-run, and cancel [GitHub Actions workflows](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** +| Apply milestones | | **X** | **X** | **X** | **X** | +| Mark [duplicate issues and pull requests](/articles/about-duplicate-issues-and-pull-requests) | | **X** | **X** | **X** | **X** | +| Request [pull request reviews](/articles/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** | +| Merge a [pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges) | | | **X** | **X** | **X** | +| Push to (write) the person or team's assigned repositories | | | **X** | **X** | **X** | +| Edit and delete anyone's comments on commits, pull requests, and issues | | | **X** | **X** | **X** | +| [Hide anyone's comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **X** | **X** | **X** | +| [Lock conversations](/communities/moderating-comments-and-conversations/locking-conversations) | | | **X** | **X** | **X** | +| Transfer issues (see "[Transferring an issue to another repository](/articles/transferring-an-issue-to-another-repository)" for details) | | | **X** | **X** | **X** | +| [Act as a designated code owner for a repository](/articles/about-code-owners) | | | **X** | **X** | **X** | +| [Mark a draft pull request as ready for review](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | +| [Convert a pull request to a draft](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | +| Submit reviews that affect a pull request's mergeability | | | **X** | **X** | **X** | +| [Apply suggested changes](/articles/incorporating-feedback-in-your-pull-request) to pull requests | | | **X** | **X** | **X** | +| Create [status checks](/articles/about-status-checks) | | | **X** | **X** | **X** |{% ifversion fpt %} +| Create, edit, run, re-run, and cancel [GitHub Actions workflows](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** {% endif %} -| Create and edit releases | | | **X** | **X** | **X** | -| View draft releases | | | **X** | **X** | **X** | -| Edit a repository's description | | | | **X** | **X** |{% ifversion fpt or ghae %} -| [View and install packages](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | -| [Publish packages](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | -| | | | | | | -| {% ifversion fpt or ghes > 3.0 %}[Delete and restore packages](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Delete packages](/packages/learn-github-packages/deleting-a-package){% endif %} | | | | | **X** | {% endif %} -| Manage [topics](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** | -| Enable wikis and restrict wiki editors | | | | **X** | **X** | -| Enable project boards | | | | **X** | **X** | -| Configure [pull request merges](/articles/configuring-pull-request-merges) | | | | **X** | **X** | -| Configure [a publishing source for {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** | -| [Push to protected branches](/articles/about-protected-branches) | | | | **X** | **X** | -| [Create and edit repository social cards](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% ifversion fpt %} -| Limit [interactions in a repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository) | | | | **X** | **X** +| Create and edit releases | | | **X** | **X** | **X** | +| View draft releases | | | **X** | **X** | **X** | +| Edit a repository's description | | | | **X** | **X** |{% ifversion fpt or ghae %} +| [View and install packages](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | +| [Publish packages](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | +| | | | | | | +| {% ifversion fpt or ghes > 3.0 %}[Delete and restore packages](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Delete packages](/packages/learn-github-packages/deleting-a-package){% endif %} | | | | | **X** | {% endif %} +| Manage [topics](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** | +| Enable wikis and restrict wiki editors | | | | **X** | **X** | +| Enable project boards | | | | **X** | **X** | +| Configure [pull request merges](/articles/configuring-pull-request-merges) | | | | **X** | **X** | +| Configure [a publishing source for {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** | +| [Push to protected branches](/articles/about-protected-branches) | | | | **X** | **X** | +| [Create and edit repository social cards](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% ifversion fpt %} +| Limit [interactions in a repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository) | | | | **X** | **X** {% endif %} -| Delete an issue (see "[Deleting an issue](/articles/deleting-an-issue)") | | | | | **X** | -| Merge pull requests on protected branches, even if there are no approving reviews | | | | | **X** | -| [Define code owners for a repository](/articles/about-code-owners) | | | | | **X** | -| Add a repository to a team (see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)" for details) | | | | | **X** | -| [Manage outside collaborator access to a repository](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | -| [Change a repository's visibility](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | -| Make a repository a template (see "[Creating a template repository](/articles/creating-a-template-repository)") | | | | | **X** | -| Change a repository's settings | | | | | **X** | -| Manage team and collaborator access to the repository | | | | | **X** | -| Edit the repository's default branch | | | | | **X** |{% ifversion fpt or ghes > 3.0 %} -| Rename the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | | | **X** | -| Rename a branch other than the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | **X** | **X** | **X** +| Delete an issue (see "[Deleting an issue](/articles/deleting-an-issue)") | | | | | **X** | +| Merge pull requests on protected branches, even if there are no approving reviews | | | | | **X** | +| [Define code owners for a repository](/articles/about-code-owners) | | | | | **X** | +| Add a repository to a team (see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)" for details) | | | | | **X** | +| [Manage outside collaborator access to a repository](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | +| [Change a repository's visibility](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | +| Make a repository a template (see "[Creating a template repository](/articles/creating-a-template-repository)") | | | | | **X** | +| Change a repository's settings | | | | | **X** | +| Manage team and collaborator access to the repository | | | | | **X** | +| Edit the repository's default branch | | | | | **X** |{% ifversion fpt or ghes > 3.0 or ghae-next %} +| Rename the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | | | **X** | +| Rename a branch other than the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | **X** | **X** | **X** {% endif %} -| Manage webhooks and deploy keys | | | | | **X** |{% ifversion fpt %} -| [Manage data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **X** +| Manage webhooks and deploy keys | | | | | **X** |{% ifversion fpt %} +| [Manage data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **X** {% endif %} -| [Manage the forking policy for a repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | -| [Transfer repositories into the organization](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | -| [Delete or transfer repositories out of the organization](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | -| [Archive repositories](/articles/about-archiving-repositories) | | | | | **X** |{% ifversion fpt %} -| Display a sponsor button (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)") | | | | | **X** +| [Manage the forking policy for a repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | +| [Transfer repositories into the organization](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | +| [Delete or transfer repositories out of the organization](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | +| [Archive repositories](/articles/about-archiving-repositories) | | | | | **X** |{% ifversion fpt %} +| Display a sponsor button (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)") | | | | | **X** {% endif %} -| Create autolink references to external resources, like JIRA or Zendesk (see "[Configuring autolinks to reference external resources](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **X** |{% ifversion fpt %} -| [Enable {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) in a repository | | | | **X** | **X** | -| [Create and edit categories](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) for {% data variables.product.prodname_discussions %} | | | | **X** | **X** | -| [Move a discussion to a different category](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [Transfer a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) to a new repository | | | **X** | **X** | **X** | -| [Manage pinned discussions](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [Convert issues to discussions in bulk](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [Lock and unlock discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [Individually convert issues to discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [Create new discussions and comment on existing discussions](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** | -| [Delete a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion) | | | | **X** | **X** |{% endif %}{% ifversion fpt %} -| Create [codespaces](/codespaces/about-codespaces) | | | **X** | **X** | **X** +| Create autolink references to external resources, like JIRA or Zendesk (see "[Configuring autolinks to reference external resources](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **X** |{% ifversion fpt %} +| [Enable {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) in a repository | | | | **X** | **X** | +| [Create and edit categories](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) for {% data variables.product.prodname_discussions %} | | | | **X** | **X** | +| [Move a discussion to a different category](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Transfer a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) to a new repository | | | **X** | **X** | **X** | +| [Manage pinned discussions](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Convert issues to discussions in bulk](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Lock and unlock discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [Individually convert issues to discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [Create new discussions and comment on existing discussions](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** | +| [Delete a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion) | | | | **X** | **X** |{% endif %}{% ifversion fpt %} +| Create [codespaces](/codespaces/about-codespaces) | | | **X** | **X** | **X** {% endif %} ### Permission requirements for security features diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md b/translations/ko-KR/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md index da640abba9..3b49b64fe0 100644 --- a/translations/ko-KR/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md +++ b/translations/ko-KR/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md @@ -36,7 +36,7 @@ Alternatively, you can enable {% data variables.product.prodname_actions %} for {% endif %} -{% ifversion fpt or ghes > 2.22 %} +{% ifversion fpt or ghes > 2.22 or ghae-next %} ## Managing {% data variables.product.prodname_actions %} permissions for your organization @@ -63,7 +63,12 @@ You can disable all workflows for an organization or set a policy that configure {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.settings-sidebar-actions %} -1. Under **Policies**, select **Allow select actions** and add your required actions to the list. ![Add actions to allow list](/assets/images/help/organizations/actions-policy-allow-list.png) +1. Under **Policies**, select **Allow select actions** and add your required actions to the list. + {%- ifversion ghes %} + ![Add actions to allow list](/assets/images/help/organizations/actions-policy-allow-list.png) + {%- else %} + ![Add actions to allow list](/assets/images/enterprise/github-ae/organizations/actions-policy-allow-list.png) + {%- endif %} 1. Click **Save**. {% endif %} @@ -71,7 +76,9 @@ You can disable all workflows for an organization or set a policy that configure {% ifversion fpt %} ## Configuring required approval for workflows from public forks -{% data reusables.actions.workflow-run-approve-public-fork %} You can configure this behavior for an organization using the procedure below. Modifying this setting overrides the configuration set at the enterprise level. +{% data reusables.actions.workflow-run-approve-public-fork %} + +You can configure this behavior for an organization using the procedure below. Modifying this setting overrides the configuration set at the enterprise level. {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} diff --git a/translations/ko-KR/content/organizations/managing-organization-settings/transferring-organization-ownership.md b/translations/ko-KR/content/organizations/managing-organization-settings/transferring-organization-ownership.md index bb93e25f47..7086818ca3 100644 --- a/translations/ko-KR/content/organizations/managing-organization-settings/transferring-organization-ownership.md +++ b/translations/ko-KR/content/organizations/managing-organization-settings/transferring-organization-ownership.md @@ -15,6 +15,13 @@ topics: shortTitle: Transfer ownership --- +{% ifversion fpt %} +{% note %} + +**Note:** {% data reusables.enterprise-accounts.invite-organization %} + +{% endnote %}{% endif %} + 1. If you're the only member with *owner* privileges, give another organization member the owner role. For more information, see "[Appointing an organization owner](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization#appointing-an-organization-owner)." 2. Contact the new owner and make sure he or she is able to [access the organization's settings](/articles/accessing-your-organization-s-settings). {% ifversion fpt %} diff --git a/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md index a62587db32..096ca122cd 100644 --- a/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md +++ b/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md @@ -13,6 +13,8 @@ topics: shortTitle: IAM with SAML SSO --- +{% data reusables.enterprise-accounts.emu-saml-note %} + ## About SAML SSO {% data reusables.saml.dotcom-saml-explanation %} diff --git a/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md b/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md index 8d74ad486e..02d8d497de 100644 --- a/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md +++ b/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md @@ -12,6 +12,8 @@ topics: - Teams --- +{% data reusables.enterprise-accounts.emu-scim-note %} + If you use [SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on) in your organization, you can implement SCIM to add, manage, and remove organization members' access to {% data variables.product.product_name %}. For example, an administrator can deprovision an organization member using SCIM and automatically remove the member from the organization. If you use SAML SSO without implementing SCIM, you won't have automatic deprovisioning. When organization members' sessions expire after their access is removed from the IdP, they aren't automatically removed from the organization. Authorized tokens grant access to the organization even after their sessions expire. To remove access, organization administrators can either manually remove the authorized token from the organization or automate its removal with SCIM. diff --git a/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md b/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md index 6da4542225..7b1456d1f9 100644 --- a/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md +++ b/translations/ko-KR/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md @@ -17,6 +17,8 @@ topics: shortTitle: Manage team synchronization --- +{% data reusables.enterprise-accounts.emu-scim-note %} + {% data reusables.gated-features.okta-team-sync %} ## About team synchronization @@ -31,6 +33,8 @@ You can enable team synchronization between your IdP and {% data variables.produ You can also enable team synchronization for organizations owned by an enterprise account. For more information, see "[Enforcing security settings in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account)." +{% data reusables.enterprise-accounts.team-sync-override %} + {% data reusables.identity-and-permissions.team-sync-usage-limits %} ## Enabling team synchronization diff --git a/translations/ko-KR/content/organizations/organizing-members-into-teams/creating-a-team.md b/translations/ko-KR/content/organizations/organizing-members-into-teams/creating-a-team.md index b93c3dd93b..0b759244e0 100644 --- a/translations/ko-KR/content/organizations/organizing-members-into-teams/creating-a-team.md +++ b/translations/ko-KR/content/organizations/organizing-members-into-teams/creating-a-team.md @@ -25,11 +25,13 @@ Only organization owners and maintainers of a parent team can create a new child {% data reusables.organizations.team_description %} {% data reusables.organizations.create-team-choose-parent %} {% ifversion fpt %} -1. Optionally, if your organization or enterprise account uses team synchronization, to connect an identity provider group to your team, use the "Identity Provider Groups" drop-down menu, and select up to 5 identity provider groups. For more information, see "[Synchronizing a team with an identity provider group](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)." ![Drop-down menu to choose identity provider groups](/assets/images/help/teams/choose-an-idp-group.png) +1. Optionally, if your organization or enterprise account uses team synchronization or your enterprise uses {% data variables.product.prodname_emus %}, connect an identity provider group to your team. + * If your enterprise uses {% data variables.product.prodname_emus %}, use the "Identity Provider Groups" drop-down menu, and select a single identity provider group to connect to the new team. For more information, "[Managing team memberships with identity provider groups](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)." + * If your organization or enterprise account uses team synchronization, use the "Identity Provider Groups" drop-down menu, and select up to five identity provider groups to connect to the new team. For more information, see "[Synchronizing a team with an identity provider group](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)." ![Drop-down menu to choose identity provider groups](/assets/images/help/teams/choose-an-idp-group.png) {% endif %} {% data reusables.organizations.team_visibility %} {% data reusables.organizations.create_team %} -9. Optionally, [give the team access to organization repositories](/articles/managing-team-access-to-an-organization-repository). +1. Optionally, [give the team access to organization repositories](/articles/managing-team-access-to-an-organization-repository). ## 더 읽을거리 diff --git a/translations/ko-KR/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md b/translations/ko-KR/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md index 33de558346..2c5a81cef8 100644 --- a/translations/ko-KR/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md +++ b/translations/ko-KR/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md @@ -45,8 +45,11 @@ Any team members that have set their status to "Busy" will not be selected for r 7. Under "How many team members should be assigned to review?", use the drop-down menu and choose a number of reviewers to be assigned to each pull request. ![Number of reviewers dropdown](/assets/images/help/teams/review-assignment-number.png) 8. Under "Routing algorithm", use the drop-down menu and choose which algorithm you'd like to use. For more information, see "[Routing algorithms](#routing-algorithms)." ![Routing algorithm dropdown](/assets/images/help/teams/review-assignment-algorithm.png) 9. Optionally, to always skip certain members of the team, select **Never assign certain team members**. Then, select one or more team members you'd like to always skip. ![Never assign certain team members checkbox and dropdown](/assets/images/help/teams/review-assignment-skip-members.png) -10. Optionally, to only notify the team members chosen by code review assignment for each pull review request, under "Notifications" select **If assigning team members, don't notify the entire team.** ![Code review assignment notifications](/assets/images/help/teams/review-assignment-notifications.png) -11. Click **Save changes**. +10. Optionally, to only notify the team members chosen by code review assignment for each pull review request, under "Notifications" select **If assigning team members, don't notify the entire team.** ![Code review assignment notifications](/assets/images/help/teams/review-assignment-notifications.png){% ifversion fpt or ghae or ghes > 3.2 %} +11. Optionally, to include members of child teams as potential reviewers when assigning requests, select **Child team members**. +12. Optionally, to count any members whose review has already been requested against the total number of members to assign, select **Count existing requests**. +13. Optionally, to remove the review request from the team when assigning team members, select **Team review request**.{% endif %} +14. Click **Save changes**. ## Disabling code review assignment {% data reusables.profile.access_org %} diff --git a/translations/ko-KR/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/ko-KR/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md index 748d1f3098..12461c271f 100644 --- a/translations/ko-KR/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md +++ b/translations/ko-KR/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md @@ -16,6 +16,8 @@ shortTitle: Synchronize with an IdP {% data reusables.gated-features.okta-team-sync %} +{% data reusables.enterprise-accounts.emu-scim-note %} + ## About team synchronization {% data reusables.identity-and-permissions.about-team-sync %} @@ -26,6 +28,8 @@ shortTitle: Synchronize with an IdP Once a {% data variables.product.prodname_dotcom %} team is connected to an IdP group, your IdP administrator must make team membership changes through the identity provider. You cannot manage team membership on {% data variables.product.product_name %}{% ifversion fpt %} or using the API{% endif %}. +{% ifversion fpt %}{% data reusables.enterprise-accounts.team-sync-override %}{% endif %} + {% ifversion fpt %} All team membership changes made through your IdP will appear in the audit log on {% data variables.product.product_name %} as changes made by the team synchronization bot. Your IdP will send team membership data to {% data variables.product.prodname_dotcom %} once every hour. Connecting a team to an IdP group may remove some team members. For more information, see "[Requirements for members of synchronized teams](#requirements-for-members-of-synchronized-teams)." {% endif %} @@ -54,8 +58,6 @@ A removed team member can be added back to a team automatically once they have a To avoid unintentionally removing team members, we recommend enforcing SAML SSO in your organization or enterprise account, creating new teams to synchronize membership data, and checking IdP group membership before synchronizing existing teams. For more information, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)" and "[Enforcing SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account)." -If your organization is owned by an enterprise account, enabling team synchronization for the enterprise account will override your organization-level team synchronization settings. For more information, see "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)." - {% endif %} ## 빌드전 요구 사양 diff --git a/translations/ko-KR/content/packages/learn-github-packages/installing-a-package.md b/translations/ko-KR/content/packages/learn-github-packages/installing-a-package.md index 8a38d76f79..43ce0bf433 100644 --- a/translations/ko-KR/content/packages/learn-github-packages/installing-a-package.md +++ b/translations/ko-KR/content/packages/learn-github-packages/installing-a-package.md @@ -18,7 +18,7 @@ versions: ## About package installation -You can search {% data variables.product.product_name %} to find packages in {% data variables.product.prodname_registry %} that you can install in your own project. For more information, see "[Searching {% data variables.product.prodname_registry %} for packages](/github/searching-for-information-on-github/searching-for-packages)." +You can search {% data variables.product.product_name %} to find packages in {% data variables.product.prodname_registry %} that you can install in your own project. For more information, see "[Searching {% data variables.product.prodname_registry %} for packages](/search-github/searching-on-github/searching-for-packages)." After you find a package, you can read the package's description and installation and usage instructions on the package page. diff --git a/translations/ko-KR/content/packages/learn-github-packages/viewing-packages.md b/translations/ko-KR/content/packages/learn-github-packages/viewing-packages.md index ef106b5dc3..8589ce32f4 100644 --- a/translations/ko-KR/content/packages/learn-github-packages/viewing-packages.md +++ b/translations/ko-KR/content/packages/learn-github-packages/viewing-packages.md @@ -64,4 +64,4 @@ You can find and view any package you've published across all organizations and ## 더 읽을거리 -- "[Searching for packages](/github/searching-for-information-on-github/searching-for-packages)" +- "[Searching for packages](/search-github/searching-on-github/searching-for-packages)" diff --git a/translations/ko-KR/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md b/translations/ko-KR/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md index bb0d08585a..2c20440794 100644 --- a/translations/ko-KR/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md +++ b/translations/ko-KR/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md @@ -15,8 +15,6 @@ shortTitle: Publish & install with Actions {% data reusables.package_registry.packages-ghes-release-stage %} {% data reusables.package_registry.packages-ghae-release-stage %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## About {% data variables.product.prodname_registry %} with {% data variables.product.prodname_actions %} diff --git a/translations/ko-KR/content/packages/quickstart.md b/translations/ko-KR/content/packages/quickstart.md index 19fd21384c..d5e56a867e 100644 --- a/translations/ko-KR/content/packages/quickstart.md +++ b/translations/ko-KR/content/packages/quickstart.md @@ -10,8 +10,6 @@ shortTitle: Quickstart --- {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## Introduction diff --git a/translations/ko-KR/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md b/translations/ko-KR/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md index 12cbd04584..0c7f604563 100644 --- a/translations/ko-KR/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md +++ b/translations/ko-KR/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md @@ -157,7 +157,11 @@ You can install packages from {% data variables.product.prodname_registry %} by By default, you can add packages from one organization. For more information, see "[Installing packages from other organizations](#installing-packages-from-other-organizations)." -You also need to add the *.npmrc* file to your project so all requests to install packages will go through {% data variables.product.prodname_registry %}. When you route all package requests through {% data variables.product.prodname_registry %}, you can use both scoped and unscoped packages from *npmjs.com*. For more information, see "[npm-scope](https://docs.npmjs.com/misc/scope)" in the npm documentation. +You also need to add the *.npmrc* file to your project so that all requests to install packages will {% ifversion ghae %}be routed to{% else %}go through{% endif %} {% data variables.product.prodname_registry %}. {% ifversion fpt or ghes > 2.21 %}When you route all package requests through {% data variables.product.prodname_registry %}, you can use both scoped and unscoped packages from *npmjs.org*. For more information, see "[npm-scope](https://docs.npmjs.com/misc/scope)" in the npm documentation.{% endif %} + +{% ifversion ghae %} +By default, you can only use npm packages hosted on your enterprise, and you will not be able to use unscoped packages. For more information on package scoping, see "[npm-scope](https://docs.npmjs.com/misc/scope)" in the npm documentation. If required, {% data variables.product.prodname_dotcom %} support can enable an upstream proxy to npmjs.org. Once an upstream proxy is enabled, if a requested package isn't found on your enterprise, {% data variables.product.prodname_registry %} makes a proxy request to npmjs.org. +{% endif %} {% data reusables.package_registry.authenticate-step %} {% data reusables.package_registry.create-npmrc-owner-step %} diff --git a/translations/ko-KR/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md b/translations/ko-KR/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md index ccec9de88d..77e97fb2b3 100644 --- a/translations/ko-KR/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md +++ b/translations/ko-KR/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md @@ -12,7 +12,11 @@ shortTitle: Change visibility of site ## About access control for {% data variables.product.prodname_pages %} sites -If your project site is published from a private or internal repository that's owned by an organization using {% data variables.product.prodname_ghe_cloud %}, you can manage access control for the site. With access control, you can choose to publish the site publicly to anyone on the internet or privately to people with read access to your repository. A privately published site can be used to share your internal documentation or knowledge base with members of your enterprise. You cannot manage access control for an organization site. For more information about the types of {% data variables.product.prodname_pages %} sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)." +With access control for {% data variables.product.prodname_pages %}, you can restrict access to your {% data variables.product.prodname_pages %} site by publishing the site privately. A privately published site can only be accessed by people with read access to the repository the site is published from. You can use privately published sites to share your internal documentation or knowledge base with members of your enterprise. + +If your enterprise uses {% data variables.product.prodname_emus %}, all {% data variables.product.prodname_pages %} sites are privately published. For more information about {% data variables.product.prodname_emus %}, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." + +If your organization uses {% data variables.product.prodname_ghe_cloud %} without {% data variables.product.prodname_emus %}, you can choose to publish your sites privately or publicly to anyone on the internet. Access control is available for project sites that are published from a private or internal repository that are owned by the organization. You cannot manage access control for an organization site. For more information about the types of {% data variables.product.prodname_pages %} sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)." Privately published sites are available at a different subdomain than publicly published sites. This ensures that your {% data variables.product.prodname_pages %} site is secure from the moment it's published: diff --git a/translations/ko-KR/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md b/translations/ko-KR/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md index 97113bddbc..5fcba4f33c 100644 --- a/translations/ko-KR/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md +++ b/translations/ko-KR/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md @@ -22,6 +22,12 @@ All {% data variables.product.prodname_pages %} sites, including sites that are {% data reusables.pages.private_pages_are_public_warning %} +{% note %} + +**Note:** RFC3280 states that the maximum length of the common name should be 64 characters. Therefore, the entire domain name of your {% data variables.product.prodname_pages %} site must be less than 64 characters long for a certificate to be successfully created. + +{% endnote %} + ## Enforcing HTTPS for your {% data variables.product.prodname_pages %} site {% data reusables.pages.navigate-site-repo %} diff --git a/translations/ko-KR/content/repositories/archiving-a-github-repository/archiving-repositories.md b/translations/ko-KR/content/repositories/archiving-a-github-repository/archiving-repositories.md index eec5322862..749fd94971 100644 --- a/translations/ko-KR/content/repositories/archiving-a-github-repository/archiving-repositories.md +++ b/translations/ko-KR/content/repositories/archiving-a-github-repository/archiving-repositories.md @@ -32,7 +32,7 @@ Once a repository is archived, you cannot add or remove collaborators or teams. When a repository is archived, its issues, pull requests, code, labels, milestones, projects, wiki, releases, commits, tags, branches, reactions, code scanning alerts, and comments become read-only. To make changes in an archived repository, you must unarchive the repository first. -You can search for archived repositories. For more information, see "[Searching for repositories](/articles/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)." You can also search for issues and pull requests within archived repositories. For more information, see "[Searching issues and pull requests](/articles/searching-issues-and-pull-requests/#search-based-on-whether-a-repository-is-archived)." +You can search for archived repositories. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)." You can also search for issues and pull requests within archived repositories. For more information, see "[Searching issues and pull requests](/search-github/searching-on-github/searching-issues-and-pull-requests/#search-based-on-whether-a-repository-is-archived)." ## Archiving a repository diff --git a/translations/ko-KR/content/repositories/archiving-a-github-repository/backing-up-a-repository.md b/translations/ko-KR/content/repositories/archiving-a-github-repository/backing-up-a-repository.md index 6560b4fcfd..794c641501 100644 --- a/translations/ko-KR/content/repositories/archiving-a-github-repository/backing-up-a-repository.md +++ b/translations/ko-KR/content/repositories/archiving-a-github-repository/backing-up-a-repository.md @@ -36,7 +36,7 @@ When you clone a repository or wiki, only Git data, such as project files and co - [Projects](/rest/reference/projects#list-repository-projects) {% endif %} -Once you have {% ifversion ghes or ghae %}a local version of all the content you want to back up, you can create a zip archive and {% else %}downloaded your archive, you can {% endif %}copy it to an external hard drive and/or upload it to a cloud-based backup service such as [Google Drive](https://www.google.com/drive/) or [Dropbox](https://www.dropbox.com/). +Once you have {% ifversion ghes or ghae %}a local version of all the content you want to back up, you can create a zip archive and {% else %}downloaded your archive, you can {% endif %}copy it to an external hard drive and/or upload it to a cloud-based backup or storage service such as [Azure Blob Storage](https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-overview/), [Google Drive](https://www.google.com/drive/) or [Dropbox](https://www.dropbox.com/). {% ifversion fpt %} ## Third-party backup tools diff --git a/translations/ko-KR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md b/translations/ko-KR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md index 3cf3de4b88..fa8a289f02 100644 --- a/translations/ko-KR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md +++ b/translations/ko-KR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md @@ -28,13 +28,13 @@ You can choose the default branch for a repository. The default branch is the ba {% endnote %} {% endif %} -{% ifversion fpt or ghes > 3.0 %} +{% ifversion fpt or ghes > 3.0 or ghae-next %} You can also rename the default branch. For more information, see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)." {% endif %} -{% ifversion fpt or ghes > 2.22 %} +{% ifversion fpt or ghes > 2.22 or ghae-next %} {% data reusables.branches.set-default-branch %} diff --git a/translations/ko-KR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md b/translations/ko-KR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md index 1344afe816..0d325c4e14 100644 --- a/translations/ko-KR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md +++ b/translations/ko-KR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md @@ -5,6 +5,7 @@ permissions: People with write permissions to a repository can rename a branch i versions: fpt: '*' ghes: '>=3.1' + ghae: next topics: - Repositories redirect_from: diff --git a/translations/ko-KR/content/repositories/creating-and-managing-repositories/about-repositories.md b/translations/ko-KR/content/repositories/creating-and-managing-repositories/about-repositories.md index fbd0d9f62e..c49b0f1011 100644 --- a/translations/ko-KR/content/repositories/creating-and-managing-repositories/about-repositories.md +++ b/translations/ko-KR/content/repositories/creating-and-managing-repositories/about-repositories.md @@ -74,7 +74,7 @@ All enterprise members have read permissions to the internal repository, but int {% data reusables.repositories.internal-repo-default %} -If a user is removed from all organizations owned by the enterprise, that user's forks of internal repositories are removed automatically. +Any member of the enterprise can fork any internal repository owned by an organization in the enterprise. The forked repository will belong to the member's user account, and the visibility of the fork will be private. If a user is removed from all organizations owned by the enterprise, that user's forks of internal repositories are removed automatically. {% endif %} ## Limits for viewing content and diffs in a repository @@ -107,6 +107,7 @@ The compare view and pull requests pages display a list of commits between the ` ## 더 읽을거리 - "[Creating a new repository](/articles/creating-a-new-repository)" +- "[About forks](/github/collaborating-with-pull-requests/working-with-forks/about-forks)" - "[Collaborating with issues and pull requests](/categories/collaborating-with-issues-and-pull-requests)" - "[Managing your work on {% data variables.product.prodname_dotcom %}](/categories/managing-your-work-on-github/)" - "[Administering a repository](/categories/administering-a-repository)" diff --git a/translations/ko-KR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md b/translations/ko-KR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md index 33fea40dfb..044536d49e 100644 --- a/translations/ko-KR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md +++ b/translations/ko-KR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md @@ -46,18 +46,19 @@ Lisa, M., & Bot, H. (2017). My Research Software (Version 2.0.4) [Computer softw {% raw %} ``` -@misc{Lisa_My_Research_Software_2017, +@software{Lisa_My_Research_Software_2017, author = {Lisa, Mona and Bot, Hew}, doi = {10.5281/zenodo.1234}, month = {12}, title = {{My Research Software}}, url = {https://github.com/github/linguist}, + version = {2.0.4}, year = {2017} } ``` {% endraw %} -Note the example above produces a _software_ citation (i.e., `@misc` type in BibTeX rather than `@article`). +Note the example above produces a _software_ citation (i.e., `@software` type in BibTeX rather than `@article`). For more information, see the [Citation File Format](https://citation-file-format.github.io/) website. @@ -67,9 +68,15 @@ When you add a `CITATION.cff` file to the default branch of your repository, it ## Citing something other than software -If you would prefer the GitHub citation information to link to another resource such as a research paper then you can use the `preferred-citation` override in CFF. +If you would prefer the {% data variables.product.prodname_dotcom %} citation information to link to another resource such as a research article, then you can use the `preferred-citation` override in CFF with the following types. -Extended CITATION.cff file describing the software, but linking to a research paper as the preferred citation: +| Resource | 유형 | +| ---------------- | ------------------ | +| Research article | `article` | +| Conference paper | `conference-paper` | +| Book | `book` | + +Extended CITATION.cff file describing the software, but linking to a research article as the preferred citation: ``` cff-version: 1.2.0 @@ -132,6 +139,10 @@ Lisa, M., & Bot, H. (2021). My awesome research software. Journal Title, 1(1), 1 ``` {% endraw %} +## Citing a dataset + +If your repository contains a dataset, you can set `type: dataset` in your `CITATION.cff` file to produce a data citation string output in the {% data variables.product.prodname_dotcom %} citation prompt. + ## Other citation files The GitHub citation feature will also detect a small number of additional files that are often used by communities and projects to describe how they would like their work to be cited. diff --git a/translations/ko-KR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md b/translations/ko-KR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md index dbc1a4353b..2df9989080 100644 --- a/translations/ko-KR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md +++ b/translations/ko-KR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md @@ -29,7 +29,7 @@ Repository admins can add any topics they'd like to a repository. Helpful topics {% ifversion ghae %}Internal {% else %}Public, internal, {% endif %}and private repositories can have topics, although you will only see private repositories that you have access to in topic search results. -You can search for repositories that are associated with a particular topic. For more information, see "[Searching for repositories](/articles/searching-for-repositories#search-by-topic)." You can also search for a list of topics on {% data variables.product.product_name %}. For more information, see "[Searching topics](/articles/searching-topics)." +You can search for repositories that are associated with a particular topic. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories#search-by-topic)." You can also search for a list of topics on {% data variables.product.product_name %}. For more information, see "[Searching topics](/search-github/searching-on-github/searching-topics)." ## Adding topics to your repository diff --git a/translations/ko-KR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md b/translations/ko-KR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md index 9377767306..8db2dcc600 100644 --- a/translations/ko-KR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md +++ b/translations/ko-KR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md @@ -73,7 +73,7 @@ You can filter repositories based on their license or license family using the ` | | The Unlicense | `unlicense` | | | zLib License | `zlib` | -When you search by a family license, your results will include all licenses in that family. For example, when you use the query `license:gpl`, your results will include repositories licensed under GNU General Public License v2.0 and GNU General Public License v3.0. For more information, see "[Searching for repositories](/articles/searching-for-repositories/#search-by-license)." +When you search by a family license, your results will include all licenses in that family. For example, when you use the query `license:gpl`, your results will include repositories licensed under GNU General Public License v2.0 and GNU General Public License v3.0. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories/#search-by-license)." ## Detecting a license diff --git a/translations/ko-KR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md b/translations/ko-KR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md index fd62873788..452ebe2bec 100644 --- a/translations/ko-KR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md +++ b/translations/ko-KR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md @@ -43,7 +43,7 @@ Alternatively, you can enable {% data variables.product.prodname_actions %} in y {% endif %} -{% ifversion fpt or ghes > 2.22 %} +{% ifversion fpt or ghes > 2.22 or ghae-next %} ## Managing {% data variables.product.prodname_actions %} permissions for your repository @@ -72,14 +72,21 @@ You can disable all workflows for a repository or set a policy that configures w {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.settings-sidebar-actions %} -1. Under **Actions permissions**, select **Allow select actions** and add your required actions to the list. ![Add actions to allow list](/assets/images/help/repository/actions-policy-allow-list.png) +1. Under **Actions permissions**, select **Allow select actions** and add your required actions to the list. + {%- ifversion ghes %} + ![Add actions to allow list](/assets/images/help/repository/actions-policy-allow-list.png) + {%- else %} + ![Add actions to allow list](/assets/images/enterprise/github-ae/repository/actions-policy-allow-list.png) + {%- endif %} 2. Click **Save**. {% endif %} {% ifversion fpt %} ## Configuring required approval for workflows from public forks -{% data reusables.actions.workflow-run-approve-public-fork %} You can configure this behavior for a repository using the procedure below. Modifying this setting overrides the configuration set at the organization or enterprise level. +{% data reusables.actions.workflow-run-approve-public-fork %} + +You can configure this behavior for a repository using the procedure below. Modifying this setting overrides the configuration set at the organization or enterprise level. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} @@ -120,6 +127,29 @@ The default permissions can also be configured in the organization settings. If 1. Click **Save** to apply the settings. {% endif %} +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## Allowing access to components in an internal repository + +{% note %} + +**Note:** {% data reusables.gated-features.internal-repos %} + +{% endnote %} + +Members of your enterprise can use internal repositories to work on projects without sharing information publicly. For information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-internal-repositories)." + +To configure whether workflows in an internal repository can be accessed from outside the repository: + +1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of the internal repository. +1. Under your repository name, click {% octicon "gear" aria-label="The gear icon" %} **Settings**. +{% data reusables.repositories.settings-sidebar-actions %} +1. Under **Access**, choose one of the access settings: ![Set the access to Actions components](/assets/images/help/settings/actions-access-settings.png) + * **Not accessible** - Workflows in other repositories can't use workflows in this repository. + * **Accessible by any repository in the organization** - Workflows in other repositories can use workflows in this repository as long as they are part of the same organization. + * **Accessible by any repository in the enterprise** - Workflows in other repositories can use workflows in this repository as long as they are part of the same enterprise. +1. Click **Save** to apply the settings. +{% endif %} + {% ifversion fpt or ghes > 2.22 or ghae %} ## Configuring the retention period for {% data variables.product.prodname_actions %} artifacts and logs in your repository diff --git a/translations/ko-KR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md b/translations/ko-KR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md index 517e80d651..b8f2d1f6cd 100644 --- a/translations/ko-KR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md +++ b/translations/ko-KR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md @@ -21,6 +21,12 @@ shortTitle: Repository visibility Organization owners can restrict the ability to change repository visibility to organization owners only. For more information, see "[Restricting repository visibility changes in your organization](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)." +{% ifversion fpt %} + +If you're a member of an {% data variables.product.prodname_emu_enterprise %}, your repositories owned by your user account can only be private, and repositories in your enterprise's organizations can only be private or internal. + +{% endif %} + We recommend reviewing the following caveats before you change the visibility of a repository. {% ifversion ghes or ghae %} diff --git a/translations/ko-KR/content/repositories/releasing-projects-on-github/about-releases.md b/translations/ko-KR/content/repositories/releasing-projects-on-github/about-releases.md index 983bccd89d..2c2aac0b40 100644 --- a/translations/ko-KR/content/repositories/releasing-projects-on-github/about-releases.md +++ b/translations/ko-KR/content/repositories/releasing-projects-on-github/about-releases.md @@ -34,6 +34,9 @@ You can receive notifications when new releases are published in a repository wi 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)." {% ifversion fpt %} + +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)." + 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](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)." {% endif %} diff --git a/translations/ko-KR/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md b/translations/ko-KR/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md new file mode 100644 index 0000000000..ebf3aaaff1 --- /dev/null +++ b/translations/ko-KR/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md @@ -0,0 +1,93 @@ +--- +title: Automatically generated release notes +intro: You can automatically generate release notes for your GitHub releases +permissions: Repository collaborators and people with write access to a repository can generate and customize automated release notes for a release. +versions: + fpt: '*' +topics: + - Repositories +shortTitle: Automated release notes +--- + +{% note %} + +**Note:** {% data reusables.repositories.auto-gen-release-public-beta %} + +{% endnote %} + +## About automatically generated release notes + +Automatically generated release notes provide an automated alternative to manually writing release notes for your {% data variables.product.prodname_dotcom %} releases. With automatically generated release notes, you can quickly generate an overview of the contents of a release. You can also customize your automated release notes, using labels to create custom categories to organize pull requests you want to include, and exclude certain labels and users from appearing in the output. + +## Creating automatically generated release notes for a new release + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.releases %} +3. Click **Draft a new release**. ![Releases draft button](/assets/images/help/releases/draft_release_button.png) +4. {% ifversion fpt %}Click **Choose a tag** and type{% else %}Type{% endif %} a version number for your release. Alternatively, select an existing tag. + {% ifversion fpt %} + ![Enter a tag](/assets/images/help/releases/releases-tag-create.png) +5. If you are creating a new tag, click **Create new tag**. ![Confirm you want to create a new tag](/assets/images/help/releases/releases-tag-create-confirm.png) + {% else %} + ![Releases tagged version](/assets/images/enterprise/releases/releases-tag-version.png) +{% endif %} +6. If you have created a new tag, use the drop-down menu to select the branch that contains the project you want to release. + {% ifversion fpt %}![Choose a branch](/assets/images/help/releases/releases-choose-branch.png) + {% else %}![Releases tagged branch](/assets/images/enterprise/releases/releases-tag-branch.png) + {% endif %} +7. To the top right of the description text box, click **Auto-generate release notes**. ![Auto-generate release notes](/assets/images/help/releases/auto-generate-release-notes.png) +8. Check the generated notes to ensure they include all (and only) the information you want to include. +9. Optionally, to include binary files such as compiled programs in your release, drag and drop or manually select files in the binaries box. ![Providing a DMG with the Release](/assets/images/help/releases/releases_adding_binary.gif) +10. To notify users that the release is not ready for production and may be unstable, select **This is a pre-release**. ![Checkbox to mark a release as prerelease](/assets/images/help/releases/prerelease_checkbox.png) +{%- ifversion fpt %} +11. Optionally, select **Create a discussion for this release**, then select the **Category** drop-down menu and click a category for the release discussion. ![Checkbox to create a release discussion and drop-down menu to choose a category](/assets/images/help/releases/create-release-discussion.png) +{%- endif %} +12. If you're ready to publicize your release, click **Publish release**. To work on the release later, click **Save draft**. ![Publish release and Draft release buttons](/assets/images/help/releases/release_buttons.png) + + +## Creating a template for automatically generated release notes + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.files.add-file %} +3. In the file name field, type `.github/release.yml` to create the `release.yml` file in the `.github` directory. ![Create new file](/assets/images/help/releases/release-yml.png) +4. In the file, specify the pull request labels and authors you want to exclude from this release. You can also create new categories and list the pull request labels to be included in each of them. For more information, see "[Managing labels](/issues/using-labels-and-milestones-to-track-work/managing-labels)." + +## Example configuration + +{% raw %} +**release.yml** +```yaml{:copy} +# release.yml + +changelog: + exclude: + labels: + - ignore-for-release + authors: + - octocat + categories: + - title: Breaking Changes 🛠 + labels: + - Semver-Major + - breaking-change + - title: Exciting New Features 🎉 + labels: + - Semver-Minor + - enhancement + - title: Other Changes + labels: + - "*" +``` +{% endraw %} + +## Release template syntax + +| Parameter | 설명 | 필수 사항 | Value | +|:----------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:---------------------------------------------------------------------------- |:------------------------------------------------------------------------- | +| `changelog` | Defines the contents within it as the custom template for your release notes. | 필수 사항. | No value accepted. | +| `제외` | Creates a category of pull requests to be excluded from the release. Can be set at the top-level of the changelog to apply to all categories or applied on a per-category basis. | 선택 사항 | No value accepted. | +| `authors` | Specifies authors to be excluded from the release. | Optional for `exclude` category. | Accepts usernames and bots as values. | +| `카테고리들` | Defines the nested contents as custom categories to be included in the template. | 선택 사항 | No value accepted. | +| `title` | Creates an individual category. | Required if `categories` parameter exists. | Takes the category name as its value. | +| `labels` | Specifies labels to be used by the enclosing category. | Required if `categories` parameter exists, optional for `exclude` parameter. | Accepts any labels, whether currently existing or planned for the future. | +| `"*"` | Catchall for any pull request not included within a category *above*. If used, it must be added at the end of the file. | 선택 사항 | No value accepted. | diff --git a/translations/ko-KR/content/repositories/releasing-projects-on-github/index.md b/translations/ko-KR/content/repositories/releasing-projects-on-github/index.md index 14d8bc84fc..37b236ff9a 100644 --- a/translations/ko-KR/content/repositories/releasing-projects-on-github/index.md +++ b/translations/ko-KR/content/repositories/releasing-projects-on-github/index.md @@ -17,6 +17,7 @@ children: - /viewing-your-repositorys-releases-and-tags - /linking-to-releases - /comparing-releases + - /automatically-generated-release-notes - /automation-for-release-forms-with-query-parameters shortTitle: Release projects --- diff --git a/translations/ko-KR/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md b/translations/ko-KR/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md index 85facf5756..969459e95e 100644 --- a/translations/ko-KR/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md +++ b/translations/ko-KR/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md @@ -42,14 +42,14 @@ You can choose whether {% data variables.large_files.product_name_long %} ({% da {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.releases %} 3. Click **Draft a new release**. ![Releases draft button](/assets/images/help/releases/draft_release_button.png) -4. {% ifversion fpt %}Click **Choose a tag** and type{% else %}Type{% endif %} a version number for your release. +4. {% ifversion fpt %}Click **Choose a tag** and type{% else %}Type{% endif %} a version number for your release. Alternatively, select an existing tag. {% ifversion fpt %} ![Enter a tag](/assets/images/help/releases/releases-tag-create.png) -1. Click **Create new tag**. ![Confirm you want to create a new tag](/assets/images/help/releases/releases-tag-create-confirm.png) +1. If you are creating a new tag, click **Create new tag**. ![Confirm you want to create a new tag](/assets/images/help/releases/releases-tag-create-confirm.png) {% else %} ![Releases tagged version](/assets/images/enterprise/releases/releases-tag-version.png) {% endif %} -5. Use the drop-down menu to select the branch that contains the project you want to release. +5. If you have created a new tag, use the drop-down menu to select the branch that contains the project you want to release. {% ifversion fpt %}![Choose a branch](/assets/images/help/releases/releases-choose-branch.png) {% else %}![Releases tagged branch](/assets/images/enterprise/releases/releases-tag-branch.png) {% endif %} @@ -57,7 +57,9 @@ You can choose whether {% data variables.large_files.product_name_long %} ({% da {%- ifversion fpt or ghes > 3.2 or ghae-issue-4972 %} If you @mention any {% data variables.product.product_name %} users in the description, the published release will include a **Contributors** section with an avatar list of all the mentioned users. {%- endif %} - ![Releases description](/assets/images/help/releases/releases_description.png) + {% ifversion fpt %} Alternatively, you can automatically generate your release notes by clicking **Auto-generate release notes**. + {% endif %} + ![Releases description](/assets/images/help/releases/releases_description_auto.png) 7. Optionally, to include binary files such as compiled programs in your release, drag and drop or manually select files in the binaries box. ![Providing a DMG with the Release](/assets/images/help/releases/releases_adding_binary.gif) 8. To notify users that the release is not ready for production and may be unstable, select **This is a pre-release**. ![Checkbox to mark a release as prerelease](/assets/images/help/releases/prerelease_checkbox.png) {%- ifversion fpt %} diff --git a/translations/ko-KR/content/repositories/working-with-files/using-files/working-with-non-code-files.md b/translations/ko-KR/content/repositories/working-with-files/using-files/working-with-non-code-files.md index 7dbb8c366b..fe1d9a1ab0 100644 --- a/translations/ko-KR/content/repositories/working-with-files/using-files/working-with-non-code-files.md +++ b/translations/ko-KR/content/repositories/working-with-files/using-files/working-with-non-code-files.md @@ -188,6 +188,14 @@ You can click {% octicon "file" aria-label="The paper icon" %} to see the change ![Rendered Prose changes](/assets/images/help/repository/rendered_prose_changes.png) +{% ifversion fpt or ghes > 3.2 or ghae-issue-5232 %} + +### Disabling Markdown rendering + +{% data reusables.repositories.disabling-markdown-rendering %} + +{% endif %} + ### Visualizing attribute changes We provide a tooltip describing changes to attributes that, unlike words, would not otherwise be visible in the rendered document. For example, if a link URL changes from one website to another, we'd show a tooltip like this: diff --git a/translations/ko-KR/content/rest/guides/getting-started-with-the-rest-api.md b/translations/ko-KR/content/rest/guides/getting-started-with-the-rest-api.md index e535cd217d..bc982ec74c 100644 --- a/translations/ko-KR/content/rest/guides/getting-started-with-the-rest-api.md +++ b/translations/ko-KR/content/rest/guides/getting-started-with-the-rest-api.md @@ -122,10 +122,10 @@ $ curl -i -u your_username {% data variables.product.api_url_pre %}/use When prompted, you can enter your OAuth token, but we recommend you set up a variable for it: -You can use `-u "username:$token"` and set up a variable for `token` to avoid leaving your token in shell history, which should be avoided. +You can use `-u "your_username:$token"` and set up a variable for `token` to avoid leaving your token in shell history, which should be avoided. ```shell -$ curl -i -u username:$token {% data variables.product.api_url_pre %}/users/octocat +$ curl -i -u your_username:$token {% data variables.product.api_url_pre %}/users/octocat ``` diff --git a/translations/ko-KR/content/rest/overview/api-previews.md b/translations/ko-KR/content/rest/overview/api-previews.md index c38f9ed3cd..ce163a8a7c 100644 --- a/translations/ko-KR/content/rest/overview/api-previews.md +++ b/translations/ko-KR/content/rest/overview/api-previews.md @@ -18,13 +18,7 @@ During the preview period, we may change some features based on developer feedba To access an API preview, you'll need to provide a custom [media type](/rest/overview/media-types) in the `Accept` header for your requests. Feature documentation for each preview specifies which custom media type to provide. -{% ifversion fpt %} -## Migrations - -Allows you to download repositories from your GitHub user or organization account to review, backup, and [migrate](/rest/reference/migrations) data to {% data variables.product.prodname_ghe_server %}. - -**Custom media type:** `wyandotte-preview` **Announced:** [2018-05-24](https://developer.github.com/changes/2018-05-24-user-migration-api/) -{% endif %} +{% ifversion ghes < 3.3 %} ## Enhanced deployments @@ -32,18 +26,28 @@ Exercise greater control over [deployments](/rest/reference/repos#deployments) w **Custom media type:** `ant-man-preview` **Announced:** [2016-04-06](https://developer.github.com/changes/2016-04-06-deployment-and-deployment-status-enhancements/) +{% endif %} + +{% ifversion ghes < 3.3 %} + ## Reactions Manage [reactions](/rest/reference/reactions) for commits, issues, and comments. **Custom media type:** `squirrel-girl-preview` **Announced:** [2016-05-12](https://developer.github.com/changes/2016-05-12-reactions-api-preview/) **Update:** [2016-06-07](https://developer.github.com/changes/2016-06-07-reactions-api-update/) +{% endif %} + +{% ifversion ghes < 3.3 %} + ## Timeline Get a [list of events](/rest/reference/issues#timeline) for an issue or pull request. **Custom media type:** `mockingbird-preview` **Announced:** [2016-05-23](https://developer.github.com/changes/2016-05-23-timeline-preview-api/) +{% endif %} + {% ifversion ghes %} ## Pre-receive environments @@ -52,11 +56,13 @@ Create, list, update, and delete environments for pre-receive hooks. **Custom media type:** `eye-scream-preview` **Announced:** [2015-07-29](/rest/reference/enterprise-admin#pre-receive-environments) {% endif %} +{% ifversion ghes < 3.3 %} ## Projects Manage [projects](/rest/reference/projects). **Custom media type:** `inertia-preview` **Announced:** [2016-09-14](https://developer.github.com/changes/2016-09-14-projects-api/) **Update:** [2016-10-27](https://developer.github.com/changes/2016-10-27-changes-to-projects-api/) +{% endif %} ## Commit search @@ -70,12 +76,16 @@ View a list of [repository topics](/articles/about-topics/) in [calls](/rest/ref **Custom media type:** `mercy-preview` **Announced:** [2017-01-31](https://github.com/blog/2309-introducing-topics) +{% ifversion ghes < 3.3 %} + ## Codes of conduct View all [codes of conduct](/rest/reference/codes-of-conduct) or get which code of conduct a repository has currently. **Custom media type:** `scarlet-witch-preview` +{% endif %} + {% ifversion ghae or ghes %} ## Global webhooks @@ -93,12 +103,16 @@ You can now use the API to manage the setting for [requiring signed commits on p **Custom media type:** `zzzax-preview` **Announced:** [2018-02-22](https://developer.github.com/changes/2018-02-22-protected-branches-required-signatures) +{% ifversion ghes < 3.3 %} + ## Require multiple approving reviews You can now [require multiple approving reviews](/rest/reference/repos#branches) for a pull request using the API. **Custom media type:** `luke-cage-preview` **Announced:** [2018-03-16](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews) +{% endif %} + {% ifversion ghes < 3.0 %} ## Check runs and check suites API @@ -135,30 +149,42 @@ GitHub App Manifests allow people to create preconfigured GitHub Apps. See "[Cre {% endif %} +{% ifversion ghes < 3.3 %} + ## Deployment statuses You can now update the `environment` of a [deployment status](/rest/reference/repos#create-a-deployment-status) and use the `in_progress` and `queued` states. When you create deployment statuses, you can now use the `auto_inactive` parameter to mark old `production` deployments as `inactive`. **Custom media type:** `flash-preview` **Announced:** [2018-10-16](https://developer.github.com/changes/2018-10-16-deployments-environments-states-and-auto-inactive-updates/) +{% endif %} + +{% ifversion ghes < 3.3 %} + ## Repository creation permissions You can now configure whether organization members can create repositories and which types of repositories they can create. See "[Update an organization](/rest/reference/orgs#update-an-organization)" for more details. **Custom media types:** `surtur-preview` **Announced:** [2019-12-03](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/) +{% endif %} + ## Content attachments You can now provide more information in GitHub for URLs that link to registered domains by using the {% data variables.product.prodname_unfurls %} API. See "[Using content attachments](/apps/using-content-attachments/)" for more details. **Custom media types:** `corsair-preview` **Announced:** [2018-12-10](https://developer.github.com/changes/2018-12-10-content-attachments-api/) +{% ifversion ghes < 3.3 %} + ## Enable and disable Pages You can use the new endpoints in the [Pages API](/rest/reference/repos#pages) to enable or disable Pages. To learn more about Pages, see "[GitHub Pages Basics](/categories/github-pages-basics)". **Custom media types:** `switcheroo-preview` **Announced:** [2019-03-14](https://developer.github.com/changes/2019-03-14-enabling-disabling-pages/) +{% endif %} + {% ifversion ghes < 3.3 %} ## List branches or pull requests for a commit @@ -169,11 +195,7 @@ You can use two new endpoints in the [Commits API](/rest/reference/repos#commits {% endif %} -## Enable or disable vulnerability alerts for a repository - -You can use two new endpoints in the [Repos API](/rest/reference/repos) to enable or disable vulnerability alerts. - -**Custom media types:** `dorian-preview` **Announced:** [2019-04-24](https://developer.github.com/changes/2019-04-24-vulnerability-alerts/) +{% ifversion ghes < 3.3 %} ## Update a pull request branch @@ -181,12 +203,6 @@ You can use a new endpoint to [update a pull request branch](/rest/reference/pul **Custom media types:** `lydian-preview` **Announced:** [2019-05-29](https://developer.github.com/changes/2019-05-29-update-branch-api/) -{% ifversion fpt %} -## Enable or disable automated security fixes - -You can use a new set of endpoints to [enable and disable automated security fixes](/rest/reference/repos#enable-automated-security-fixes). - -**Custom media types:** `london-preview` **Announced:** [2019-06-04](https://developer.github.com/changes/2019-06-04-automated-security-fixes/) {% endif %} ## Create and use repository templates @@ -195,7 +211,8 @@ You can use a new endpoint to [Create a repository using a template](/rest/refer **Custom media types:** `baptiste-preview` **Announced:** [2019-07-05](https://developer.github.com/changes/2019-07-16-repository-templates-api/) -{% ifversion fpt or ghes or ghae %} +{% ifversion ghes < 3.3 %} + ## New visibility parameter for the Repositories API You can set and retrieve the visibility of a repository in the [Repositories API](/rest/reference/repos). diff --git a/translations/ko-KR/content/rest/overview/troubleshooting.md b/translations/ko-KR/content/rest/overview/troubleshooting.md index de8b488e17..bf79575da7 100644 --- a/translations/ko-KR/content/rest/overview/troubleshooting.md +++ b/translations/ko-KR/content/rest/overview/troubleshooting.md @@ -62,6 +62,10 @@ curl -u my_username:my_password -X POST "https://api.github.com/authorizations" Then you must switch to the [web application flow](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) to generate access tokens. +## Timeouts + +If {% data variables.product.product_name %} takes more than 10 seconds to process an API request, {% data variables.product.product_name %} will terminate the request and you will receive a timeout response. + {% endif %} [oap-guide]: https://developer.github.com/changes/2015-01-19-an-integrators-guide-to-organization-application-policies/ diff --git a/translations/ko-KR/content/rest/reference/actions.md b/translations/ko-KR/content/rest/reference/actions.md index 29c5559f0e..960575a19c 100644 --- a/translations/ko-KR/content/rest/reference/actions.md +++ b/translations/ko-KR/content/rest/reference/actions.md @@ -12,7 +12,6 @@ topics: miniTocMaxHeadingLevel: 3 --- -{% data reusables.actions.ae-beta %} The {% data variables.product.prodname_actions %} API enables you to manage {% data variables.product.prodname_actions %} using the REST API. {% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} require the permissions mentioned in each endpoint. For more information, see "[{% data variables.product.prodname_actions %} Documentation](/actions)." @@ -22,8 +21,6 @@ The {% data variables.product.prodname_actions %} API enables you to manage {% d ## Artifacts -{% data reusables.actions.ae-beta %} - The Artifacts API allows you to download, delete, and retrieve information about workflow artifacts. {% data reusables.actions.about-artifacts %} For more information, see "[Persisting workflow data using artifacts](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)." {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %} @@ -35,11 +32,9 @@ The Artifacts API allows you to download, delete, and retrieve information about {% ifversion fpt or ghes > 2.22 or ghae %} ## Permissions -{% data reusables.actions.ae-beta %} - The Permissions API allows you to set permissions for what organizations and repositories are allowed to run {% data variables.product.prodname_actions %}, and what actions are allowed to run. For more information, see "[Usage limits, billing, and administration](/actions/reference/usage-limits-billing-and-administration#disabling-or-limiting-github-actions-for-your-repository-or-organization)." -You can manage self-hosted runners for an enterprise. For more information, see the "[{% data variables.product.prodname_dotcom %} Enterprise administration](/rest/reference/enterprise-admin#actions)" REST API. +You can manage self-hosted runners for an enterprise. For more information, see the "[{% data variables.product.prodname_dotcom %} Enterprise administration](/rest/reference/enterprise-admin#github-actions)" REST API. {% for operation in currentRestOperations %} {% if operation.subcategory == 'permissions' %}{% include rest_operation %}{% endif %} @@ -48,8 +43,6 @@ You can manage self-hosted runners for an enterprise. For more information, see ## Secrets -{% data reusables.actions.ae-beta %} - The Secrets API lets you create, update, delete, and retrieve information about encrypted secrets. {% data reusables.actions.about-secrets %} For more information, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)." {% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `secrets` permission to use this API. Authenticated users must have collaborator access to a repository to create, update, or read secrets. @@ -60,14 +53,13 @@ The Secrets API lets you create, update, delete, and retrieve information about ## Self-hosted runners -{% data reusables.actions.ae-beta %} {% data reusables.actions.ae-self-hosted-runners-notice %} The Self-hosted Runners API allows you to register, view, and delete self-hosted runners. {% data reusables.actions.about-self-hosted-runners %} For more information, see "[Hosting your own runners](/actions/hosting-your-own-runners)." {% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `administration` permission for repositories or the `organization_self_hosted_runners` permission for organizations. Authenticated users must have admin access to the repository or organization to use this API. -You can manage self-hosted runners for an enterprise. For more information, see the "[{% data variables.product.prodname_dotcom %} Enterprise administration](/rest/reference/enterprise-admin#actions)" REST API. +You can manage self-hosted runners for an enterprise. For more information, see the "[{% data variables.product.prodname_dotcom %} Enterprise administration](/rest/reference/enterprise-admin#github-actions)" REST API. {% for operation in currentRestOperations %} {% if operation.subcategory == 'self-hosted-runners' %}{% include rest_operation %}{% endif %} @@ -75,7 +67,6 @@ You can manage self-hosted runners for an enterprise. For more information, see ## Self-hosted runner groups -{% data reusables.actions.ae-beta %} {% data reusables.actions.ae-self-hosted-runners-notice %} The Self-hosted Runners Groups API allows you manage groups of self-hosted runners. 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)." @@ -90,8 +81,6 @@ You can manage self-hosted runner groups for an enterprise. For more information ## Workflows -{% data reusables.actions.ae-beta %} - The Workflows API allows you to view workflows for a repository. {% data reusables.actions.about-workflows %} For more information, see "[Automating your workflow with GitHub Actions](/actions/automating-your-workflow-with-github-actions)." {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %} @@ -102,8 +91,6 @@ The Workflows API allows you to view workflows for a repository. {% data reusabl ## Workflow jobs -{% data reusables.actions.ae-beta %} - The Workflow Jobs API allows you to view logs and workflow jobs. {% data reusables.actions.about-workflow-jobs %} For more information, see "[Workflow syntax for GitHub Actions](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)". {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %} @@ -114,8 +101,6 @@ The Workflow Jobs API allows you to view logs and workflow jobs. {% data reusabl ## Workflow runs -{% data reusables.actions.ae-beta %} - The Workflow Runs API allows you to view, re-run, cancel, and view logs for workflow runs. {% data reusables.actions.about-workflow-runs %} For more information, see "[Managing a workflow run](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)." {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %} diff --git a/translations/ko-KR/content/rest/reference/activity.md b/translations/ko-KR/content/rest/reference/activity.md index bbb6d0f531..0a5f0bca62 100644 --- a/translations/ko-KR/content/rest/reference/activity.md +++ b/translations/ko-KR/content/rest/reference/activity.md @@ -145,6 +145,7 @@ Here's a list of potential `reason`s for receiving a notification: | `assign` | You were assigned to the issue. | | `저자` | You created the thread. | | `의견` | You commented on the thread. | +| `ci_activity` | A {% data variables.product.prodname_actions %} workflow run that you triggered was completed. | | `초대` | You accepted an invitation to contribute to the repository. | | `manual` | You subscribed to the thread (via an issue or pull request). | | `멘션` | You were specifically **@mentioned** in the content. | diff --git a/translations/ko-KR/content/rest/reference/enterprise-admin.md b/translations/ko-KR/content/rest/reference/enterprise-admin.md index 40588cb5c8..b5ec920e3b 100644 --- a/translations/ko-KR/content/rest/reference/enterprise-admin.md +++ b/translations/ko-KR/content/rest/reference/enterprise-admin.md @@ -81,7 +81,6 @@ The current version of your enterprise is returned in the response header of eve ## GitHub Actions -{% data reusables.actions.ae-beta %} {% for operation in currentRestOperations %} {% if operation.subcategory == 'actions' %}{% include rest_operation %}{% endif %} diff --git a/translations/ko-KR/content/rest/reference/projects.md b/translations/ko-KR/content/rest/reference/projects.md index aa8cf5ac71..13543ab310 100644 --- a/translations/ko-KR/content/rest/reference/projects.md +++ b/translations/ko-KR/content/rest/reference/projects.md @@ -1,6 +1,6 @@ --- title: Projects -intro: 'The Projects API lets you to create, list, update, delete and customize projects in a repository.' +intro: 'The Projects API lets you create, list, update, delete and customize projects in a repository.' redirect_from: - /v3/projects versions: diff --git a/translations/ko-KR/content/rest/reference/repos.md b/translations/ko-KR/content/rest/reference/repos.md index 9e6e43ec84..b3c108b5b6 100644 --- a/translations/ko-KR/content/rest/reference/repos.md +++ b/translations/ko-KR/content/rest/reference/repos.md @@ -175,7 +175,7 @@ You can communicate that a transient environment no longer exists by setting its {% ifversion fpt or ghes > 3.1 or ghae-next %} ## Environments -The Environments API allows you to create, configure, and delete environments. For more information about environments, see "[Environments](/actions/reference/environments)." To manage environment secrets, see "[Secrets](/rest/reference/actions#secrets)." +The Environments API allows you to create, configure, and delete environments. For more information about environments, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." To manage environment secrets, see "[Secrets](/rest/reference/actions#secrets)." {% for operation in currentRestOperations %} {% if operation.subcategory == 'environments' %}{% include rest_operation %}{% endif %} diff --git a/translations/ko-KR/content/rest/reference/scim.md b/translations/ko-KR/content/rest/reference/scim.md index 3701bb4836..cebf90d065 100644 --- a/translations/ko-KR/content/rest/reference/scim.md +++ b/translations/ko-KR/content/rest/reference/scim.md @@ -16,7 +16,9 @@ The SCIM API is used by SCIM-enabled Identity Providers (IdPs) to automate provi {% note %} -**Note:** The SCIM API is available only to organizations on [{% data variables.product.prodname_ghe_cloud %}](/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts) with [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) enabled. {% data reusables.scim.enterprise-account-scim %} For more information about SCIM, see "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)." +**참고:** + - The SCIM API is available only to organizations on [{% data variables.product.prodname_ghe_cloud %}](/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts) with [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) enabled. {% data reusables.scim.enterprise-account-scim %} For more information about SCIM, see "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)." + - The SCIM API cannot be used with {% data variables.product.prodname_emus %}. {% endnote %} diff --git a/translations/ko-KR/content/rest/reference/search.md b/translations/ko-KR/content/rest/reference/search.md index 0b21cb3e15..c7bd47ca1a 100644 --- a/translations/ko-KR/content/rest/reference/search.md +++ b/translations/ko-KR/content/rest/reference/search.md @@ -50,7 +50,7 @@ GitHub Octocat in:readme user:defunkt const queryString = 'q=' + encodeURIComponent('GitHub Octocat in:readme user:defunkt'); ``` -See "[Searching on GitHub](/articles/searching-on-github/)" for a complete list of available qualifiers, their format, and an example of how to use them. For information about how to use operators to match specific quantities, dates, or to exclude results, see "[Understanding the search syntax](/articles/understanding-the-search-syntax/)." +See "[Searching on GitHub](/articles/searching-on-github/)" for a complete list of available qualifiers, their format, and an example of how to use them. For information about how to use operators to match specific quantities, dates, or to exclude results, see "[Understanding the search syntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax/)." ### Limitations on query length diff --git a/translations/ko-KR/content/rest/reference/teams.md b/translations/ko-KR/content/rest/reference/teams.md index 60bd6aab7e..0627bb8a2e 100644 --- a/translations/ko-KR/content/rest/reference/teams.md +++ b/translations/ko-KR/content/rest/reference/teams.md @@ -58,6 +58,12 @@ The Team Synchronization API allows you to manage connections between {% data va You can manage GitHub team members through your IdP with team synchronization. Team synchronization must be enabled to use the Team Synchronization API. For more information, see "Synchronizing teams between your identity provider and GitHub." +{% note %} + +**Note:** The Team Synchronization API cannot be used with {% data variables.product.prodname_emus %}. + +{% endnote %} + {% for operation in currentRestOperations %} {% if operation.subcategory == 'team-sync' %}{% include rest_operation %}{% endif %} {% endfor %} diff --git a/translations/ko-KR/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md b/translations/ko-KR/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md new file mode 100644 index 0000000000..79790dacb2 --- /dev/null +++ b/translations/ko-KR/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md @@ -0,0 +1,90 @@ +--- +title: About searching on GitHub +intro: 'Our integrated search covers the many repositories, users, and lines of code on {% data variables.product.product_name %}.' +redirect_from: + - /articles/using-the-command-bar/ + - /articles/github-search-basics/ + - /articles/search-basics/ + - /articles/searching-github/ + - /articles/advanced-search/ + - /articles/about-searching-on-github + - /github/searching-for-information-on-github/about-searching-on-github + - /github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +{% data reusables.search.you-can-search-globally %} + +- To search globally across all of {% data variables.product.product_name %}, type what you're looking for into the search field at the top of any page, and choose "All {% data variables.product.prodname_dotcom %}" in the search drop-down menu. +- To search within a particular repository or organization, navigate to the repository or organization page, type what you're looking for into the search field at the top of the page, and press **Enter**. + +{% note %} + +**참고:** + +{% ifversion fpt or ghes %} +- {% data reusables.search.required_login %}{% endif %} +- {% data variables.product.prodname_pages %} sites are not searchable on {% data variables.product.product_name %}. However you can search the source content if it exists in the default branch of a repository, using code search. For more information, see "[Searching code](/search-github/searching-on-github/searching-code)." For more information about {% data variables.product.prodname_pages %}, see "[What is GitHub Pages?](/articles/what-is-github-pages/)" +- Currently our search doesn't support exact matching. +- Whenever you are searching in code files, only the first two results in each file will be returned. + +{% endnote %} + +After running a search on {% data variables.product.product_name %}, you can sort the results, or further refine them by clicking one of the languages in the sidebar. For more information, see "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results)." + +{% data variables.product.product_name %} search uses an ElasticSearch cluster to index projects every time a change is pushed to {% data variables.product.product_name %}. Issues and pull requests are indexed when they are created or modified. + +## Types of searches on {% data variables.product.prodname_dotcom %} + +You can search for the following information across all repositories you can access on {% data variables.product.product_location %}. + +- [Repositories](/search-github/searching-on-github/searching-for-repositories) +- [Topics](/search-github/searching-on-github/searching-topics) +- [Issues and pull requests](/search-github/searching-on-github/searching-issues-and-pull-requests){% ifversion fpt %} +- [Discussions](/search-github/searching-on-github/searching-discussions){% endif %} +- [Code](/search-github/searching-on-github/searching-code) +- [Commits](/search-github/searching-on-github/searching-commits) +- [Users](/search-github/searching-on-github/searching-users) +- [Packages](/search-github/searching-on-github/searching-for-packages) +- [Wikis](/search-github/searching-on-github/searching-wikis) + +## Searching using a visual interface + +Alternatively, you can search {% data variables.product.product_name %} using the {% data variables.search.search_page_url %} or {% data variables.search.advanced_url %}. + +The {% data variables.search.advanced_url %} provides a visual interface for constructing search queries. You can filter your searches by a variety of factors, such as the number of stars or number of forks a repository has. As you fill in the advanced search fields, your query will automatically be constructed in the top search bar. + +![Advanced Search](/assets/images/help/search/advanced_search_demo.gif) + +{% ifversion fpt or ghes or ghae-next %} + +## Searching repositories on {% data variables.product.prodname_dotcom_the_website %} from your private enterprise environment + +If you use {% ifversion fpt %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae-next %} or {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} and you're a member of a {% data variables.product.prodname_dotcom_the_website %} organization using {% data variables.product.prodname_ghe_cloud %}, an enterprise owner for your {% data variables.product.prodname_enterprise %} environment can enable {% data variables.product.prodname_github_connect %} so that you can search across both environments at the same time{% ifversion ghes or ghae %} from {% data variables.product.product_name %}{% endif %}. For more information, see the following. + +{% ifversion fpt or ghes %} +- "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/{% ifversion ghes %}{{ currentVersion }}{% else %}github-enterprise@latest{% endif %}/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_server %} documentation{% endif %}{% ifversion ghae-next %} +- "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/github-ae@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_managed %} documentation +{% endif %} + +{% ifversion ghes or ghae-next %} + +To scope your search by environment, you can use a filter option on the {% data variables.search.advanced_url %} or you can use the `environment:` search prefix. To only search for content on {% data variables.product.product_name %}, use the search syntax `environment:local`. To only search for content on {% data variables.product.prodname_dotcom_the_website %}, use `environment:github`. + +Your enterprise owner on {% data variables.product.product_name %} can enable {% data variables.product.prodname_unified_search %} for all public repositories, all private repositories, or only certain private repositories in the connected {% data variables.product.prodname_ghe_cloud %} organization. + +When you search from {% data variables.product.product_name %}, you can only search in the private repositories that you have access to in the connected {% data variables.product.prodname_dotcom_the_website %} organization. Enterprise owners for {% data variables.product.product_name %} and organization owners on {% data variables.product.prodname_dotcom_the_website %} cannot search private repositories owned by your account on {% data variables.product.prodname_dotcom_the_website %}. To search the applicable private repositories, you must enable private repository search for your personal accounts on {% data variables.product.product_name %}. For more information, see "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment)." + +{% endif %} + +{% endif %} + +## 더 읽을거리 + +- "[Understanding the search syntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)" +- "[Searching on GitHub](/articles/searching-on-github)" diff --git a/translations/ko-KR/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md b/translations/ko-KR/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md new file mode 100644 index 0000000000..883c68e584 --- /dev/null +++ b/translations/ko-KR/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md @@ -0,0 +1,54 @@ +--- +title: Enabling GitHub.com repository search from your private enterprise environment +shortTitle: Search GitHub.com from enterprise +intro: 'You can connect your personal accounts on {% data variables.product.prodname_dotcom_the_website %} and your private {% data variables.product.prodname_enterprise %} environment to search for content in certain {% data variables.product.prodname_dotcom_the_website %} repositories{% ifversion fpt %} from your private environment{% else %} from {% data variables.product.product_name %}{% endif %}.' +redirect_from: + - /articles/enabling-private-githubcom-repository-search-in-your-github-enterprise-account/ + - /articles/enabling-private-github-com-repository-search-in-your-github-enterprise-server-account/ + - /articles/enabling-private-githubcom-repository-search-in-your-github-enterprise-server-account/ + - /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 +versions: + fpt: '*' + ghes: '*' + ghae: next +topics: + - GitHub search +--- + +## About search for {% data variables.product.prodname_dotcom_the_website %} repositories from {% ifversion fpt %}your private enterprise environment{% else %}{% data variables.product.product_name %}{% endif %} + +You can search for designated private repositories on {% data variables.product.prodname_ghe_cloud %} from {% ifversion fpt %}your private {% data variables.product.prodname_enterprise %} environment{% else %}{% data variables.product.product_location %}{% ifversion ghae %} on {% data variables.product.prodname_ghe_managed %}{% endif %}{% endif %}. {% ifversion fpt %}For example, if you use {% data variables.product.prodname_ghe_server %}, you can search for private repositories from your enterprise from {% data variables.product.prodname_ghe_cloud %} in the web interface for {% data variables.product.prodname_ghe_server %}.{% endif %} + +## 빌드전 요구 사양 + +- An enterprise owner for {% ifversion fpt %}your private {% data variables.product.prodname_enterprise %} environment{% else %}{% data variables.product.product_name %}{% endif %} must enable {% data variables.product.prodname_github_connect %} and {% data variables.product.prodname_unified_search %} for private repositories. For more information, see the following.{% ifversion fpt or ghes %} + - "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/{% ifversion ghes %}{{ currentVersion }}{% else %}github-enterprise@latest{% endif %}/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_server %} documentation{% endif %}{% ifversion ghae-next %} + - "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/github-ae@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_managed %} documentation +{% endif %} + +- You must already have access to the private repositories and connect your account {% ifversion fpt %}in your private {% data variables.product.prodname_enterprise %} environment{% else %}on {% data variables.product.product_name %}{% endif %} with your account on {% data variables.product.prodname_dotcom_the_website %}. For more information about the repositories you can search, see "[About searching on GitHub](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github#searching-repositories-on-githubcom-from-your-private-enterprise-environment)." + +## Enabling GitHub.com repository search from {% ifversion fpt %}your private {% data variables.product.prodname_enterprise %} environment{% else %}{% data variables.product.product_name %}{% endif %} + +{% ifversion fpt %} + +For more information, see the following. + +| Your enterprise environment | More information | +|:--------------------------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| {% data variables.product.prodname_ghe_server %} | "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/enterprise-server@latest/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-enterprise-server)" |{% ifversion ghae-next %} +| +| {% data variables.product.prodname_ghe_managed %} | "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/github-ae@latest//search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-ae)" +{% endif %} + +{% elsif ghes or ghae %} + +1. Sign into {% data variables.product.product_name %} and {% data variables.product.prodname_dotcom_the_website %}. +1. On {% data variables.product.product_name %}, in the upper-right corner of any page, click your profile photo, then click **Settings**. ![Settings icon in the user bar](/assets/images/help/settings/userbar-account-settings.png) +{% data reusables.github-connect.github-connect-tab-user-settings %} +{% data reusables.github-connect.connect-dotcom-and-enterprise %} +{% data reusables.github-connect.connect-dotcom-and-enterprise %} + +{% endif %} diff --git a/translations/ko-KR/content/search-github/getting-started-with-searching-on-github/index.md b/translations/ko-KR/content/search-github/getting-started-with-searching-on-github/index.md new file mode 100644 index 0000000000..1a7a0faa9d --- /dev/null +++ b/translations/ko-KR/content/search-github/getting-started-with-searching-on-github/index.md @@ -0,0 +1,21 @@ +--- +title: Getting started with searching on GitHub +intro: 'You can use a wide range of syntax to search {% data variables.product.product_name %}. You can adjust the scope of your search, build and troubleshoot queries, and sort search results with qualifiers.' +redirect_from: + - /articles/getting-started-with-searching-on-github + - /github/searching-for-information-on-github/getting-started-with-searching-on-github +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +children: + - /about-searching-on-github + - /understanding-the-search-syntax + - /troubleshooting-search-queries + - /sorting-search-results + - /enabling-githubcom-repository-search-from-your-private-enterprise-environment +shortTitle: Start with search on GitHub +--- + diff --git a/translations/ko-KR/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md b/translations/ko-KR/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md new file mode 100644 index 0000000000..c54f597bc5 --- /dev/null +++ b/translations/ko-KR/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md @@ -0,0 +1,75 @@ +--- +title: Sorting search results +intro: 'You can sort [{% data variables.product.product_name %} search](/articles/searching-on-github) results using the Sort menu, or by adding a `sort` qualifier to your query.' +redirect_from: + - /articles/sorting-search-results + - /github/searching-for-information-on-github/sorting-search-results + - /github/searching-for-information-on-github/getting-started-with-searching-on-github/sorting-search-results +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +Use the Sort menu to sort results by relevance, number of stars, number of forks, and how recently the items were updated. + + ![Menu with options for sorting search results](/assets/images/help/search/repo-search-sort.png) + +To sort by interactions, reactions, author date, committer date, or how recently the items were updated, you can add a `sort` qualifier to your search query. + +## Sort by interactions + +The `sort:interactions` qualifier sorts by the highest combined number of reactions and comments. + +| Qualifier | 예시 | +| ----------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sort:interactions` or `sort:interactions-desc` | [**org:github sort:interactions**](https://github.com/search?q=org%3Agithub+sort%3Ainteractions&type=Issues) matches issues in repositories owned by {% data variables.product.product_name %}, sorted by the highest combined number of reactions and comments. | +| `sort:interactions-asc` | [**org:github sort:interactions-asc**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Ainteractions-asc&type=Issues) matches issues in repositories owned by {% data variables.product.product_name %}, sorted by the lowest combined number of reactions and comments. | + +## Sort by reactions + +The `sort:reactions` qualifier sorts by the number or type of reactions. + +| Qualifier | 예시 | +| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sort:reactions` or `sort:reactions-desc` | [**org:github sort:reactions**](https://github.com/search?q=org%3Agithub+sort%3Areactions&type=Issues) matches issues in repositories owned by {% data variables.product.product_name %}, sorted by the highest number of reactions. | +| `sort:reactions-asc` | [**org:github sort:reactions-asc**](https://github.com/search?q=org%3Agithub+sort%3Areactions-asc&type=Issues) matches issues in repositories owned by {% data variables.product.product_name %}, sorted by ascending number of reactions (the fewest to the most). | +| sort:reactions-reaction | [**org:github sort:reactions-+1**](https://github.com/search?q=org%3Agithub+sort%3Areactions-%2B1&type=Issues) matches issues in repositories owned by {% data variables.product.product_name %}, sorted by most thumbs up (:+1:) reactions. | +| | [**org:github sort:reactions--1**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Areactions--1&type=Issues) matches issues in repositories owned by {% data variables.product.product_name %}, sorted by most thumbs down (:-1:) reactions. | +| | [**org:github sort:reactions-smile**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Areactions-smile&type=Issues) matches issues in repositories owned by {% data variables.product.product_name %}, sorted by most laugh (:smile:) reactions. | +| | [**org:github sort:reactions-tada**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Areactions-tada&type=Issues) matches issues in repositories owned by {% data variables.product.product_name %}, sorted by most hurray (:tada:) reactions. | +| | [**org:github sort:reactions-heart**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Areactions-heart&type=Issues) matches issues in repositories owned by {% data variables.product.product_name %}, sorted by most heart (:heart:) reactions. | + +## Sort by author date + +The `sort:author-date` qualifier sorts by descending or ascending author date. + +| Qualifier | 예시 | +| --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sort:author-date` or `sort:author-date-desc` | [**feature org:github sort:author-date**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Aauthor-date&type=Commits) matches commits containing the word "feature" in repositories owned by {% data variables.product.product_name %}, sorted by descending author date. | +| `sort:author-date-asc` | [**feature org:github sort:author-date-asc**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Aauthor-date-asc&type=Commits) matches commits containing the word "feature" in repositories owned by {% data variables.product.product_name %}, sorted by ascending author date. | + +## Sort by committer date + +The `sort:committer-date` qualifier sorts by descending or ascending committer date. + +| Qualifier | 예시 | +| --------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sort:committer-date` or `sort:committer-date-desc` | [**feature org:github sort:committer-date**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Acommitter-date&type=Commits) matches commits containing the word "feature" in repositories owned by {% data variables.product.product_name %}, sorted by descending committer date. | +| `sort:committer-date-asc` | [**feature org:github sort:committer-date-asc**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Acommitter-date-asc&type=Commits) matches commits containing the word "feature" in repositories owned by {% data variables.product.product_name %}, sorted by ascending committer date. | + +## Sort by updated date + +The `sort:updated` qualifier sorts by how recently the items were updated. + +| Qualifier | 예시 | +| ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `sort:updated` or `sort:updated-desc` | [**feature sort:updated**](https://github.com/search?utf8=%E2%9C%93&q=feature+sort%3Aupdated&type=Repositories) matches repositories containing the word "feature," sorted by most recently updated date. | +| `sort:updated-asc` | [**feature sort:updated-asc**](https://github.com/search?utf8=%E2%9C%93&q=feature+sort%3Aupdated-asc&type=Repositories) matches repositories containing the word "feature," sorted by least recently updated date. | + +## 더 읽을거리 + +- "[About searching on {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)" +- "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)" diff --git a/translations/ko-KR/content/search-github/getting-started-with-searching-on-github/troubleshooting-search-queries.md b/translations/ko-KR/content/search-github/getting-started-with-searching-on-github/troubleshooting-search-queries.md new file mode 100644 index 0000000000..91b854131a --- /dev/null +++ b/translations/ko-KR/content/search-github/getting-started-with-searching-on-github/troubleshooting-search-queries.md @@ -0,0 +1,34 @@ +--- +title: Troubleshooting search queries +intro: 'If you encounter unexpected results while searching on {% data variables.product.product_name %}, you can troubleshoot by reviewing common problems and limitations.' +redirect_from: + - /articles/troubleshooting-search-queries + - /github/searching-for-information-on-github/troubleshooting-search-queries + - /github/searching-for-information-on-github/getting-started-with-searching-on-github/troubleshooting-search-queries +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +shortTitle: Troubleshoot search queries +--- + +## Potential timeouts + +Some queries are computationally expensive for our search infrastructure to execute. To keep search fast for everyone, we limit how long any individual query can run. In rare situations when a query exceeds the time limit, search returns all matches that were found prior to the timeout and informs you that a timeout occurred. + +Reaching a timeout does not necessarily mean that search results are incomplete. It just means that the query was discontinued before it searched through all possible data. + +## Limitations on query length + +There are some limits to the length of the queries when searching across {% data variables.product.product_name %}: + +* Queries longer than 256 characters are not supported +* You can't construct a query using more than five `AND`, `OR`, or `NOT` operators + +Specific search types, such as code search, might have additional limitations. Check the documentation for these search types for more information. + +## 더 읽을거리 + +- "[About searching on GitHub](/search-github/getting-started-with-searching-on-github/about-searching-on-github)" diff --git a/translations/ko-KR/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md b/translations/ko-KR/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md new file mode 100644 index 0000000000..172e609563 --- /dev/null +++ b/translations/ko-KR/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md @@ -0,0 +1,100 @@ +--- +title: Understanding the search syntax +intro: 'When searching {% data variables.product.product_name %}, you can construct queries that match specific numbers and words.' +redirect_from: + - /articles/search-syntax/ + - /articles/understanding-the-search-syntax + - /github/searching-for-information-on-github/understanding-the-search-syntax + - /github/searching-for-information-on-github/getting-started-with-searching-on-github/understanding-the-search-syntax +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +shortTitle: Understand search syntax +--- + +## Query for values greater or less than another value + +You can use `>`, `>=`, `<`, and `<=` to search for values that are greater than, greater than or equal to, less than, and less than or equal to another value. + +| Query | 예시 | +| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| >n | **[cats stars:>1000](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%3E1000&type=Repositories)** matches repositories with the word "cats" that have more than 1000 stars. | +| >=n | **[cats topics:>=5](https://github.com/search?utf8=%E2%9C%93&q=cats+topics%3A%3E%3D5&type=Repositories)** matches repositories with the word "cats" that have 5 or more topics. | +| <n | **[cats size:<10000](https://github.com/search?utf8=%E2%9C%93&q=cats+size%3A%3C10000&type=Code)** matches code with the word "cats" in files that are smaller than 10 KB. | +| <=n | **[cats stars:<=50](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%3C%3D50&type=Repositories)** matches repositories with the word "cats" that have 50 or fewer stars. | + +You can also use [range queries](#query-for-values-between-a-range) to search for values that are greater than or equal to, or less than or equal to, another value. + +| Query | 예시 | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| n..* | **[cats stars:10..*](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A10..*&type=Repositories)** is equivalent to `stars:>=10` and matches repositories with the word "cats" that have 10 or more stars. | +| *..n | **[cats stars:*..10](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%22*..10%22&type=Repositories)** is equivalent to `stars:<=10` and matches repositories with the word "cats" that have 10 or fewer stars. | + +## Query for values between a range + +You can use the range syntax n..n to search for values within a range, where the first number _n_ is the lowest value and the second is the highest value. + +| Query | 예시 | +| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| n..n | **[cats stars:10..50](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A10..50&type=Repositories)** matches repositories with the word "cats" that have between 10 and 50 stars. | + +## Query for dates + +You can search for dates that are earlier or later than another date, or that fall within a range of dates, by using `>`, `>=`, `<`, `<=`, and [range queries](#query-for-values-between-a-range). {% data reusables.time_date.date_format %} + +| Query | 예시 | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| >YYYY-MM-DD | **[cats created:>2016-04-29](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3E2016-04-29&type=Issues)** matches issues with the word "cats" that were created after April 29, 2016. | +| >=YYYY-MM-DD | **[cats created:>=2017-04-01](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3E%3D2017-04-01&type=Issues)** matches issues with the word "cats" that were created on or after April 1, 2017. | +| <YYYY-MM-DD | **[cats pushed:<2012-07-05](https://github.com/search?q=cats+pushed%3A%3C2012-07-05&type=Code&utf8=%E2%9C%93)** matches code with the word "cats" in repositories that were pushed to before July 5, 2012. | +| <=YYYY-MM-DD | **[cats created:<=2012-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3C%3D2012-07-04&type=Issues)** matches issues with the word "cats" that were created on or before July 4, 2012. | +| YYYY-MM-DD..YYYY-MM-DD | **[cats pushed:2016-04-30..2016-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+pushed%3A2016-04-30..2016-07-04&type=Repositories)** matches repositories with the word "cats" that were pushed to between the end of April and July of 2016. | +| YYYY-MM-DD..* | **[cats created:2012-04-30..*](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2012-04-30..*&type=Issues)** matches issues created after April 30th, 2012 containing the word "cats." | +| *..YYYY-MM-DD | **[cats created:*..2012-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A*..2012-07-04&type=Issues)** matches issues created before July 4th, 2012 containing the word "cats." | + +{% data reusables.time_date.time_format %} + +| Query | 예시 | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| YYYY-MM-DDTHH:MM:SS+00:00 | **[cats created:2017-01-01T01:00:00+07:00..2017-03-01T15:30:15+07:00](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2017-01-01T01%3A00%3A00%2B07%3A00..2017-03-01T15%3A30%3A15%2B07%3A00&type=Issues)** matches issues created between January 1, 2017 at 1 a.m. with a UTC offset of `07:00` and March 1, 2017 at 3 p.m. with a UTC offset of `07:00`. | +| YYYY-MM-DDTHH:MM:SSZ | **[cats created:2016-03-21T14:11:00Z..2016-04-07T20:45:00Z](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2016-03-21T14%3A11%3A00Z..2016-04-07T20%3A45%3A00Z&type=Issues)** matches issues created between March 21, 2016 at 2:11pm and April 7, 2106 at 8:45pm. | + +## Exclude certain results + +You can exclude results containing a certain word, using the `NOT` syntax. The `NOT` operator can only be used for string keywords. It does not work for numerals or dates. + +| Query | 예시 | +| ----- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `NOT` | **[hello NOT world](https://github.com/search?q=hello+NOT+world&type=Repositories)** matches repositories that have the word "hello" but not the word "world." | + +Another way you can narrow down search results is to exclude certain subsets. You can prefix any search qualifier with a `-` to exclude all results that are matched by that qualifier. + +| Query | 예시 | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| -QUALIFIER | **[cats stars:>10 -language:javascript](https://github.com/search?q=cats+stars%3A>10+-language%3Ajavascript&type=Repositories)** matches repositories with the word "cats" that have more than 10 stars but are not written in JavaScript. | +| | **[mentions:defunkt -org:github](https://github.com/search?utf8=%E2%9C%93&q=mentions%3Adefunkt+-org%3Agithub&type=Issues)** matches issues mentioning @defunkt that are not in repositories in the GitHub organization | + +## Use quotation marks for queries with whitespace + +If your search query contains whitespace, you will need to surround it with quotation marks. 예시: + +* [cats NOT "hello world"](https://github.com/search?utf8=✓&q=cats+NOT+"hello+world"&type=Repositories) matches repositories with the word "cats" but not the words "hello world." +* [build label:"bug fix"](https://github.com/search?utf8=%E2%9C%93&q=build+label%3A%22bug+fix%22&type=Issues) matches issues with the word "build" that have the label "bug fix." + +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 %} +## 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. + +| Query | 예시 | +| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `QUALIFIER:USERNAME` | [`author:nat`](https://github.com/search?q=author%3Anat&type=Commits) matches commits authored by @nat | +| `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/translations/ko-KR/content/search-github/index.md b/translations/ko-KR/content/search-github/index.md new file mode 100644 index 0000000000..c70346fc97 --- /dev/null +++ b/translations/ko-KR/content/search-github/index.md @@ -0,0 +1,20 @@ +--- +title: Searching for information on GitHub +intro: Use different types of searches to find the information you want. +redirect_from: + - /categories/78/articles/ + - /categories/search/ + - /categories/searching-for-information-on-github + - /github/searching-for-information-on-github +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +children: + - /getting-started-with-searching-on-github + - /searching-on-github +shortTitle: Search on GitHub +--- + diff --git a/translations/ko-KR/content/search-github/searching-on-github/finding-files-on-github.md b/translations/ko-KR/content/search-github/searching-on-github/finding-files-on-github.md new file mode 100644 index 0000000000..3ba29d5fae --- /dev/null +++ b/translations/ko-KR/content/search-github/searching-on-github/finding-files-on-github.md @@ -0,0 +1,32 @@ +--- +title: Finding files on GitHub +intro: 'You can search for a file in a repository using the file finder. To search for a file in multiple repositories on {% data variables.product.product_name %}, use the [`filename` code search qualifier](/search-github/searching-on-github/searching-code#search-by-filename).' +redirect_from: + - /articles/finding-files-on-github + - /github/searching-for-information-on-github/finding-files-on-github + - /github/searching-for-information-on-github/searching-on-github/finding-files-on-github +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +{% tip %} + +**팁:** + +- File finder results exclude some directories like `build`, `log`, `tmp`, and `vendor`. To search for files within these directories, use the [`filename` code search qualifier](/search-github/searching-on-github/searching-code#search-by-filename). +- You can also open the file finder by pressing `t` on your keyboard. For more information, see "[Keyboard shortcuts](/articles/keyboard-shortcuts)." + +{% endtip %} + +{% data reusables.repositories.navigate-to-repo %} +2. Above the list of files, click **Go to file**. ![Find file button](/assets/images/help/search/find-file-button.png) +3. In the search field, type the name of the file you'd like to find. ![Find file search field](/assets/images/help/search/find-file-search-field.png) +4. In the list of results, click the file you wanted to find. + +## 더 읽을거리 + +- "[About searching on GitHub](/search-github/getting-started-with-searching-on-github/about-searching-on-github)" diff --git a/translations/ko-KR/content/search-github/searching-on-github/index.md b/translations/ko-KR/content/search-github/searching-on-github/index.md new file mode 100644 index 0000000000..40b2461457 --- /dev/null +++ b/translations/ko-KR/content/search-github/searching-on-github/index.md @@ -0,0 +1,27 @@ +--- +title: Searching on GitHub +intro: You can use qualifiers to narrow your search and focus on specific categories of information. +redirect_from: + - /articles/searching-on-github + - /github/searching-for-information-on-github/searching-on-github +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +children: + - /finding-files-on-github + - /searching-for-repositories + - /searching-topics + - /searching-code + - /searching-commits + - /searching-issues-and-pull-requests + - /searching-discussions + - /searching-github-marketplace + - /searching-users + - /searching-for-packages + - /searching-wikis + - /searching-in-forks +--- + diff --git a/translations/ko-KR/content/search-github/searching-on-github/searching-code.md b/translations/ko-KR/content/search-github/searching-on-github/searching-code.md new file mode 100644 index 0000000000..f722ec86e7 --- /dev/null +++ b/translations/ko-KR/content/search-github/searching-on-github/searching-code.md @@ -0,0 +1,112 @@ +--- +title: Searching code +intro: 'You can search for code on {% data variables.product.product_name %} and narrow the results using these code search qualifiers in any combination.' +redirect_from: + - /articles/searching-code + - /github/searching-for-information-on-github/searching-files-in-a-repository-for-exact-matches + - /github/searching-for-information-on-github/searching-code-for-exact-matches + - /github/searching-for-information-on-github/searching-code + - /github/searching-for-information-on-github/searching-on-github/searching-code +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +{% data reusables.search.you-can-search-globally %} For more information, see "[About searching on GitHub](/search-github/getting-started-with-searching-on-github/about-searching-on-github)." + +You can only search code using these code search qualifiers. Search qualifiers specifically for repositories, users, or commits, will not work when searching for code. + +{% data reusables.search.syntax_tips %} + +## Considerations for code search + +Due to the complexity of searching code, there are some restrictions on how searches are performed: + +{% ifversion fpt or ghes %} +- {% data reusables.search.required_login %}{% endif %} +- Code in [forks](/articles/about-forks) is only searchable if the fork has more stars than the parent repository. Forks with fewer stars than the parent repository are **not** indexed for code search. To include forks with more stars than their parent in the search results, you will need to add `fork:true` or `fork:only` to your query. For more information, see "[Searching in forks](/search-github/searching-on-github/searching-in-forks)." +- Only the _default branch_ is indexed for code search.{% ifversion fpt %} +- Only files smaller than 384 KB are searchable.{% else %}* Only files smaller than 5 MB are searchable. +- Only the first 500 KB of each file is searchable.{% endif %} +- Only repositories with fewer than 500,000 files are searchable.{% ifversion fpt %} +- Only repositories that have had activity or have been returned in search results in the last year are searchable.{% endif %} +- Except with [`filename`](#search-by-filename) searches, you must always include at least one search term when searching source code. For example, searching for [`language:javascript`](https://github.com/search?utf8=%E2%9C%93&q=language%3Ajavascript&type=Code&ref=searchresults) is not valid, while [`amazing language:javascript`](https://github.com/search?utf8=%E2%9C%93&q=amazing+language%3Ajavascript&type=Code&ref=searchresults) is. +- At most, search results can show two fragments from the same file, but there may be more results within the file. +- You can't use the following wildcard characters as part of your search query: . , : ; / \ ` ' " = * ! ? # $ & + ^ | ~ < > ( ) { } [ ] @. The search will simply ignore these symbols. + +## Search by the file contents or file path + +With the `in` qualifier you can restrict your search to the contents of the source code file, the file path, or both. When you omit this qualifier, only the file contents are searched. + +| Qualifier | 예시 | +| --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `in:file` | [**octocat in:file**](https://github.com/search?q=octocat+in%3Afile&type=Code) matches code where "octocat" appears in the file contents. | +| `in:path` | [**octocat in:path**](https://github.com/search?q=octocat+in%3Apath&type=Code) matches code where "octocat" appears in the file path. | +| | [**octocat in:file,path**](https://github.com/search?q=octocat+in%3Afile%2Cpath&type=Code) matches code where "octocat" appears in the file contents or the file path. | + +## Search within a user's or organization's repositories + +To search the code in all repositories owned by a certain user or organization, you can use the `user` or `org` qualifier. To search the code in a specific repository, you can use the `repo` qualifier. + +| Qualifier | 예시 | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**user:defunkt extension:rb**](https://github.com/search?q=user%3Agithub+extension%3Arb&type=Code) matches code from @defunkt that ends in .rb. | +| org:ORGNAME | [**org:github extension:js**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+extension%3Ajs&type=Code) matches code from GitHub that ends in .js. | +| repo:USERNAME/REPOSITORY | [**repo:mozilla/shumway extension:as**](https://github.com/search?q=repo%3Amozilla%2Fshumway+extension%3Aas&type=Code) matches code from @mozilla's shumway project that ends in .as. | + +## Search by file location + +You can use the `path` qualifier to search for source code that appears at a specific location in a repository. Use `path:/` to search for files that are located at the root level of a repository. Or specify a directory name or the path to a directory to search for files that are located within that directory or any of its subdirectories. + +| Qualifier | 예시 | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| path:/ | [**octocat filename:readme path:/**](https://github.com/search?utf8=%E2%9C%93&q=octocat+filename%3Areadme+path%3A%2F&type=Code) matches _readme_ files with the word "octocat" that are located at the root level of a repository. | +| path:DIRECTORY | [**form path:cgi-bin language:perl**](https://github.com/search?q=form+path%3Acgi-bin+language%3Aperl&type=Code) matches Perl files with the word "form" in the cgi-bin directory, or in any of its subdirectories. | +| path:PATH/TO/DIRECTORY | [**console path:app/public language:javascript**](https://github.com/search?q=console+path%3A%22app%2Fpublic%22+language%3Ajavascript&type=Code) matches JavaScript files with the word "console" in the app/public directory, or in any of its subdirectories (even if they reside in app/public/js/form-validators). | + +## Search by language + + +You can search for code based on what language it's written in. The `language` qualifier can be the language name or alias. For a full list of supported languages with their names and aliases, see the [github/linguist repository](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml). + +| Qualifier | 예시 | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| language:LANGUAGE | [**element language:xml size:100**](https://github.com/search?q=element+language%3Axml+size%3A100&type=Code) matches code with the word "element" that's marked as being XML and has exactly 100 bytes. | +| | [**display language:scss**](https://github.com/search?q=display+language%3Ascss&type=Code) matches code with the word "display," that's marked as being SCSS. | +| | [**org:mozilla language:markdown**](https://github.com/search?utf8=%E2%9C%93&q=org%3Amozilla+language%3Amarkdown&type=Code) matches code from all @mozilla's repositories that's marked as Markdown. | + +## Search by file size + +You can use the `size` qualifier to search for source code based on the size of the file where the code exists. The `size` qualifier uses [greater than, less than, and range qualifiers](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax) to filter results based on the byte size of the file in which the code is found. + +| Qualifier | 예시 | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| size:n | [**function size:>10000 language:python**](https://github.com/search?q=function+size%3A%3E10000+language%3Apython&type=Code) matches code with the word "function," written in Python, in files that are larger than 10 KB. | + +## Search by filename + +The `filename` qualifier matches code files with a certain filename. You can also find a file in a repository using the file finder. For more information, see "[Finding files on GitHub](/search-github/searching-on-github/finding-files-on-github)." + +| Qualifier | 예시 | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| filename:FILENAME | [**filename:linguist**](https://github.com/search?utf8=%E2%9C%93&q=filename%3Alinguist&type=Code) matches files named "linguist." | +| | [**filename:.vimrc commands**](https://github.com/search?q=filename%3A.vimrc+commands&type=Code) matches *.vimrc* files with the word "commands." | +| | [**filename:test_helper path:test language:ruby**](https://github.com/search?q=minitest+filename%3Atest_helper+path%3Atest+language%3Aruby&type=Code) matches Ruby files named *test_helper* within the *test* directory. | + +## Search by file extension + +The `extension` qualifier matches code files with a certain file extension. + +| Qualifier | 예시 | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| extension:EXTENSION | [**form path:cgi-bin extension:pm**](https://github.com/search?q=form+path%3Acgi-bin+extension%3Apm&type=Code) matches code with the word "form," under cgi-bin, with the .pm file extension. | +| | [**icon size:>200000 extension:css**](https://github.com/search?utf8=%E2%9C%93&q=icon+size%3A%3E200000+extension%3Acss&type=Code) matches files larger than 200 KB that end in .css and have the word "icon." | + +## 더 읽을거리 + +- "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" +- "[Searching in forks](/search-github/searching-on-github/searching-in-forks)"{% ifversion fpt %} +- "[Navigating code on {% data variables.product.prodname_dotcom %}](/github/managing-files-in-a-repository/navigating-code-on-github)"{% endif %} diff --git a/translations/ko-KR/content/search-github/searching-on-github/searching-commits.md b/translations/ko-KR/content/search-github/searching-on-github/searching-commits.md new file mode 100644 index 0000000000..8c357bb40d --- /dev/null +++ b/translations/ko-KR/content/search-github/searching-on-github/searching-commits.md @@ -0,0 +1,111 @@ +--- +title: Searching commits +intro: 'You can search for commits on {% data variables.product.product_name %} and narrow the results using these commit search qualifiers in any combination.' +redirect_from: + - /articles/searching-commits + - /github/searching-for-information-on-github/searching-commits + - /github/searching-for-information-on-github/searching-on-github/searching-commits +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +You can search for commits globally across all of {% data variables.product.product_name %}, or search for commits within a particular repository or organization. For more information, see "[About searching on {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)." + +When you search for commits, only the [default branch](/articles/about-branches) of a repository is searched. + +{% data reusables.search.syntax_tips %} + +## Search within commit messages + +You can find commits that contain particular words in the message. For example, [**fix typo**](https://github.com/search?q=fix+typo&type=Commits) matches commits containing the words "fix" and "typo." + +## Search by author or committer + +You can find commits by a particular user with the `author` or `committer` qualifiers. + +| Qualifier | 예시 | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | +| author:USERNAME | [**author:defunkt**](https://github.com/search?q=author%3Adefunkt&type=Commits) matches commits authored by @defunkt. | +| committer:USERNAME | [**committer:defunkt**](https://github.com/search?q=committer%3Adefunkt&type=Commits) matches commits committed by @defunkt. | + +The `author-name` and `committer-name` qualifiers match commits by the name of the author or committer. + +| Qualifier | 예시 | +| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | +| author-name:NAME | [**author-name:wanstrath**](https://github.com/search?q=author-name%3Awanstrath&type=Commits) matches commits with "wanstrath" in the author name. | +| committer-name:NAME | [**committer-name:wanstrath**](https://github.com/search?q=committer-name%3Awanstrath&type=Commits) matches commits with "wanstrath" in the committer name. | + +The `author-email` and `committer-email` qualifiers match commits by the author's or committer's full email address. + +| Qualifier | 예시 | +| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| author-email:EMAIL | [**author-email:chris@github.com**](https://github.com/search?q=author-email%3Achris%40github.com&type=Commits) matches commits authored by chris@github.com. | +| committer-email:EMAIL | [**committer-email:chris@github.com**](https://github.com/search?q=committer-email%3Achris%40github.com&type=Commits) matches commits committed by chris@github.com. | + +## Search by authored or committed date + +Use the `author-date` and `committer-date` qualifiers to match commits authored or committed within the specified date range. + +{% data reusables.search.date_gt_lt %} + +| Qualifier | 예시 | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| author-date:YYYY-MM-DD | [**author-date:<2016-01-01**](https://github.com/search?q=author-date%3A<2016-01-01&type=Commits) matches commits authored before 2016-01-01. | +| committer-date:YYYY-MM-DD | [**committer-date:>2016-01-01**](https://github.com/search?q=committer-date%3A>2016-01-01&type=Commits) matches commits committed after 2016-01-01. | + +## Filter merge commits + +The `merge` qualifier filters merge commits. + +| Qualifier | 예시 | +| ------------- | ---------------------------------------------------------------------------------------------------- | +| `merge:true` | [**merge:true**](https://github.com/search?q=merge%3Atrue&type=Commits) matches merge commits. | +| `merge:false` | [**merge:false**](https://github.com/search?q=merge%3Afalse&type=Commits) matches non-merge commits. | + +## Search by hash + +The `hash` qualifier matches commits with the specified SHA-1 hash. + +| Qualifier | 예시 | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| hash:HASH | [**hash:124a9a0ee1d8f1e15e833aff432fbb3b02632105**](https://github.com/github/gitignore/search?q=hash%3A124a9a0ee1d8f1e15e833aff432fbb3b02632105&type=Commits) matches commits with the hash `124a9a0ee1d8f1e15e833aff432fbb3b02632105`. | + +## Search by parent + +The `parent` qualifier matches commits whose parent has the specified SHA-1 hash. + +| Qualifier | 예시 | +| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| parent:HASH | [**parent:124a9a0ee1d8f1e15e833aff432fbb3b02632105**](https://github.com/github/gitignore/search?q=parent%3A124a9a0ee1d8f1e15e833aff432fbb3b02632105&type=Commits&utf8=%E2%9C%93) matches children of commits with the hash `124a9a0ee1d8f1e15e833aff432fbb3b02632105`. | + +## Search by tree + +The `tree` qualifier matches commits with the specified SHA-1 git tree hash. + +| Qualifier | 예시 | +| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | +| tree:HASH | [**tree:99ca967**](https://github.com/github/gitignore/search?q=tree%3A99ca967&type=Commits) matches commits that refer to the tree hash `99ca967`. | + +## Search within a user's or organization's repositories + +To search commits in all repositories owned by a certain user or organization, use the `user` or `org` qualifier. To search commits in a specific repository, use the `repo` qualifier. + +| Qualifier | 예시 | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**gibberish user:defunkt**](https://github.com/search?q=gibberish+user%3Adefunkt&type=Commits&utf8=%E2%9C%93) matches commit messages with the word "gibberish" in repositories owned by @defunkt. | +| org:ORGNAME | [**test org:github**](https://github.com/search?utf8=%E2%9C%93&q=test+org%3Agithub&type=Commits) matches commit messages with the word "test" in repositories owned by @github. | +| repo:USERNAME/REPO | [**language repo:defunkt/gibberish**](https://github.com/search?utf8=%E2%9C%93&q=language+repo%3Adefunkt%2Fgibberish&type=Commits) matches commit messages with the word "language" in @defunkt's "gibberish" repository. | + +## Filter by repository visibility + +The `is` qualifier matches commits from repositories with the specified visibility. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." + +| Qualifier | Example | ------------- | ------------- |{% ifversion fpt or ghes %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Commits) matches commits to public repositories.{% endif %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Commits) matches commits to internal repositories. | `is:private` | [**is:private**](https://github.com/search?q=is%3Aprivate&type=Commits) matches commits to private repositories. + +## 더 읽을거리 + +- "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" diff --git a/translations/ko-KR/content/search-github/searching-on-github/searching-discussions.md b/translations/ko-KR/content/search-github/searching-on-github/searching-discussions.md new file mode 100644 index 0000000000..b47d2fabb2 --- /dev/null +++ b/translations/ko-KR/content/search-github/searching-on-github/searching-discussions.md @@ -0,0 +1,113 @@ +--- +title: Searching discussions +intro: 'You can search for discussions on {% data variables.product.product_name %} and narrow the results using search qualifiers.' +versions: + fpt: '*' +topics: + - GitHub search +redirect_from: + - /github/searching-for-information-on-github/searching-discussions + - /github/searching-for-information-on-github/searching-on-github/searching-discussions +--- + +## About searching for discussions + +You can search for discussions globally across all of {% data variables.product.product_name %}, or search for discussions within a particular organization or repository. For more information, see "[About searching on {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/about-searching-on-github)." + +{% data reusables.search.syntax_tips %} + +## Search by the title, body, or comments + +With the `in` qualifier you can restrict your search for discussions to the title, body, or comments. You can also combine qualifiers to search a combination of title, body, or comments. When you omit the `in` qualifier, {% data variables.product.product_name %} searches the title, body, and comments. + +| Qualifier | 예시 | +|:------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `in:title` | [**welcome in:title**](https://github.com/search?q=welcome+in%3Atitle&type=Discussions) matches discussions with "welcome" in the title. | +| `in:body` | [**onboard in:title,body**](https://github.com/search?q=onboard+in%3Atitle%2Cbody&type=Discussions) matches discussions with "onboard" in the title or body. | +| `in:comments` | [**thanks in:comments**](https://github.com/search?q=thanks+in%3Acomment&type=Discussions) matches discussions with "thanks" in the comments for the discussion. | + +## Search within a user's or organization's repositories + +To search discussions in all repositories owned by a certain user or organization, you can use the `user` or `org` qualifier. To search discussions in a specific repository, you can use the `repo` qualifier. + +| Qualifier | 예시 | +|:------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**user:octocat feedback**](https://github.com/search?q=user%3Aoctocat+feedback&type=Discussions) matches discussions with the word "feedback" from repositories owned by @octocat. | +| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=Discussions&utf8=%E2%9C%93) matches discussions in repositories owned by the GitHub organization. | +| repo:USERNAME/REPOSITORY | [**repo:nodejs/node created:<2021-01-01**](https://github.com/search?q=repo%3Anodejs%2Fnode+created%3A%3C2020-01-01&type=Discussions) matches discussions from @nodejs' Node.js runtime project that were created before January 2021. | + +## Filter by repository visibility + +You can filter by the visibility of the repository containing the discussions using the `is` qualifier. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." + +| Qualifier | Example | :- | :- |{% ifversion fpt or ghes %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Discussions) matches discussions in public repositories.{% endif %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Discussions) matches discussions in internal repositories. | `is:private` | [**is:private tiramisu**](https://github.com/search?q=is%3Aprivate+tiramisu&type=Discussions) matches discussions that contain the word "tiramisu" in private repositories you can access. + +## Search by author + +The `author` qualifier finds discussions created by a certain user. + +| Qualifier | 예시 | +|:------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| author:USERNAME | [**cool author:octocat**](https://github.com/search?q=cool+author%3Aoctocat&type=Discussions) matches discussions with the word "cool" that were created by @octocat. | +| | [**bootstrap in:body author:octocat**](https://github.com/search?q=bootstrap+in%3Abody+author%3Aoctocat&type=Discussions) matches discussions created by @octocat that contain the word "bootstrap" in the body. | + +## Search by commenter + +The `commenter` qualifier finds discussions that contain a comment from a certain user. + +| Qualifier | 예시 | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| commenter:USERNAME | [**github commenter:becca org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Abecca+org%3Agithub&type=Discussions) matches discussions in repositories owned by GitHub, that contain the word "github," and have a comment by @becca. | + +## Search by a user that's involved in a discussion + +You can use the `involves` qualifier to find discussions that involve a certain user. The qualifier returns discussions that were either created by a certain user, mention the user, or contain comments by the user. The `involves` qualifier is a logical OR between the `author`, `mentions`, and `commenter` qualifiers for a single user. + +| Qualifier | 예시 | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| involves:USERNAME | **[involves:becca involves:octocat](https://github.com/search?q=involves%3Abecca+involves%3Aoctocat&type=Discussions)** matches discussions either @becca or @octocat are involved in. | +| | [**NOT beta in:body involves:becca**](https://github.com/search?q=NOT+beta+in%3Abody+involves%3Abecca&type=Discussions) matches discussions @becca is involved in that do not contain the word "beta" in the body. | + +## Search by number of comments + +You can use the `comments` qualifier along with greater than, less than, and range qualifiers to search by the number of comments. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." + +| Qualifier | 예시 | +|:------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------- | +| comments:n | [**comments:>100**](https://github.com/search?q=comments%3A%3E100&type=Discussions) matches discussions with more than 100 comments. | +| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Discussions) matches discussions with comments ranging from 500 to 1,000. | + +## Search by number of interactions + +You can filter discussions by the number of interactions with the `interactions` qualifier along with greater than, less than, and range qualifiers. The interactions count is the number of reactions and comments on a discussion. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." + +| Qualifier | 예시 | +|:------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------- | +| interactions:n | [** interactions:>2000**](https://github.com/search?q=interactions%3A%3E2000) matches discussions with more than 2,000 interactions. | +| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) matches discussions with interactions ranging from 500 to 1,000. | + +## Search by number of reactions + +You can filter discussions by the number of reactions using the `reactions` qualifier along with greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." + +| Qualifier | 예시 | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------ | +| reactions:n | [** reactions:>1000**](https://github.com/search?q=reactions%3A%3E500) matches discussions with more than 500 reactions. | +| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) matches discussions with reactions ranging from 500 to 1,000. | + +## Search by when a discussion was created or last updated + +You can filter discussions based on times of creation, or when the discussion was last updated. For discussion creation, you can use the `created` qualifier; to find out when an discussion was last updated, use the `updated` qualifier. + +Both qualifiers take a date as a parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifier | 예시 | +|:-------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| created:YYYY-MM-DD | [**created:>2020-11-15**](https://github.com/search?q=created%3A%3E%3D2020-11-15&type=discussions) matches discussions that were created after November 15, 2020. | +| updated:YYYY-MM-DD | [**weird in:body updated:>=2020-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2020-12-01&type=Discussions) matches discussions with the word "weird" in the body that were updated after December 2020. | + +## 더 읽을거리 + +- "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" diff --git a/translations/ko-KR/content/search-github/searching-on-github/searching-for-packages.md b/translations/ko-KR/content/search-github/searching-on-github/searching-for-packages.md new file mode 100644 index 0000000000..91ba8cc15b --- /dev/null +++ b/translations/ko-KR/content/search-github/searching-on-github/searching-for-packages.md @@ -0,0 +1,45 @@ +--- +title: Searching for packages +intro: 'You can search for packages on {% data variables.product.product_name %} and narrow the results using search qualifiers.' +product: '{% data reusables.gated-features.packages %}' +permissions: Anyone can search for packages they have access to. +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +redirect_from: + - /github/searching-for-information-on-github/searching-for-packages + - /github/searching-for-information-on-github/searching-on-github/searching-for-packages +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +## About searching for packages + +You can search for packages globally across all of {% data variables.product.product_name %}, or search for packages within a particular organization. For more information, see "[About searching on {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)." + +{% ifversion ghes %} +You can only search for packages on {% data variables.product.product_name %}, not {% data variables.product.prodname_dotcom_the_website %}, even if {% data variables.product.prodname_github_connect %} is enabled. +{% endif %} + +{% data reusables.search.syntax_tips %} + +## Searching within a user's or organization's packages + +To find packages owned by a certain user or organization, use the `user` or `org` qualifier. + +| Qualifier | 예시 | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| user:USERNAME | [**user:codertocat**](https://github.com/search?q=user%3Acodertocat&type=RegistryPackages) matches packages owned by @codertocat | +| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=RegistryPackages) matches packages owned by the {% data variables.product.prodname_dotcom %} organization | + +## Filtering by package visibility + +To filter your search by whether a package is public or private, use the `is` qualifier. + +| Qualifier | 예시 | +| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `is:public` | [**is:public angular**](https://github.com/search?q=is%3Apublic+angular&type=RegistryPackages) matches public packages that contain the word "angular" | +| `is:private` | [**is:private php**](https://github.com/search?q=is%3Aprivate+php&type=RegistryPackages) matches private packages that contain the word "php" | diff --git a/translations/ko-KR/content/search-github/searching-on-github/searching-for-repositories.md b/translations/ko-KR/content/search-github/searching-on-github/searching-for-repositories.md new file mode 100644 index 0000000000..daf5218a74 --- /dev/null +++ b/translations/ko-KR/content/search-github/searching-on-github/searching-for-repositories.md @@ -0,0 +1,201 @@ +--- +title: Searching for repositories +intro: 'You can search for repositories on {% data variables.product.product_name %} and narrow the results using these repository search qualifiers in any combination.' +redirect_from: + - /articles/searching-repositories/ + - /articles/searching-for-repositories + - /github/searching-for-information-on-github/searching-for-repositories + - /github/searching-for-information-on-github/searching-on-github/searching-for-repositories +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +shortTitle: Search for repositories +--- + +You can search for repositories globally across all of {% data variables.product.product_location %}, or search for repositories within a particular organization. For more information, see "[About searching on {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)." + +To include forks in the search results, you will need to add `fork:true` or `fork:only` to your query. For more information, see "[Searching in forks](/search-github/searching-on-github/searching-in-forks)." + +{% data reusables.search.syntax_tips %} + +## Search by repository name, description, or contents of the README file + +With the `in` qualifier you can restrict your search to the repository name, repository description, contents of the README file, or any combination of these. When you omit this qualifier, only the repository name and description are searched. + +| Qualifier | 예시 | +| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `in:name` | [**jquery in:name**](https://github.com/search?q=jquery+in%3Aname&type=Repositories) matches repositories with "jquery" in the repository name. | +| `in:description` | [**jquery in:name,description**](https://github.com/search?q=jquery+in%3Aname%2Cdescription&type=Repositories) matches repositories with "jquery" in the repository name or description. | +| `in:readme` | [**jquery in:readme**](https://github.com/search?q=jquery+in%3Areadme&type=Repositories) matches repositories mentioning "jquery" in the repository's README file. | +| `repo:owner/name` | [**repo:octocat/hello-world**](https://github.com/search?q=repo%3Aoctocat%2Fhello-world) matches a specific repository name. | + +## Search based on the contents of a repository + +You can find a repository by searching for content in the repository's README file using the `in:readme` qualifier. For more information, see "[About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)." + +Besides using `in:readme`, it's not possible to find repositories by searching for specific content within the repository. To search for a specific file or content within a repository, you can use the file finder or code-specific search qualifiers. For more information, see "[Finding files on {% data variables.product.prodname_dotcom %}](/search-github/searching-on-github/finding-files-on-github)" and "[Searching code](/search-github/searching-on-github/searching-code)." + +| Qualifier | 예시 | +| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `in:readme` | [**octocat in:readme**](https://github.com/search?q=octocat+in%3Areadme&type=Repositories) matches repositories mentioning "octocat" in the repository's README file. | + +## Search within a user's or organization's repositories + +To search in all repositories owned by a certain user or organization, you can use the `user` or `org` qualifier. + +| Qualifier | 예시 | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**user:defunkt forks:>100**](https://github.com/search?q=user%3Adefunkt+forks%3A%3E%3D100&type=Repositories) matches repositories from @defunkt that have more than 100 forks. | +| org:ORGNAME | [**org:github**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub&type=Repositories) matches repositories from GitHub. | + +## Search by repository size + +The `size` qualifier finds repositories that match a certain size (in kilobytes), using greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." + +| Qualifier | 예시 | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | +| size:n | [**size:1000**](https://github.com/search?q=size%3A1000&type=Repositories) matches repositories that are 1 MB exactly. | +| | [**size:>=30000**](https://github.com/search?q=size%3A%3E%3D30000&type=Repositories) matches repositories that are at least 30 MB. | +| | [**size:<50**](https://github.com/search?q=size%3A%3C50&type=Repositories) matches repositories that are smaller than 50 KB. | +| | [**size:50..120**](https://github.com/search?q=size%3A50..120&type=Repositories) matches repositories that are between 50 KB and 120 KB. | + +## Search by number of followers + +You can filter repositories based on the number of users who follow the repositories, using the `followers` qualifier with greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." + +| Qualifier | 예시 | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| followers:n | [**node followers:>=10000**](https://github.com/search?q=node+followers%3A%3E%3D10000) matches repositories with 10,000 or more followers mentioning the word "node". | +| | [**styleguide linter followers:1..10**](https://github.com/search?q=styleguide+linter+followers%3A1..10&type=Repositories) matches repositories with between 1 and 10 followers, mentioning the word "styleguide linter." | + +## Search by number of forks + +The `forks` qualifier specifies the number of forks a repository should have, using greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." + +| Qualifier | 예시 | +| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | +| forks:n | [**forks:5**](https://github.com/search?q=forks%3A5&type=Repositories) matches repositories with only five forks. | +| | [**forks:>=205**](https://github.com/search?q=forks%3A%3E%3D205&type=Repositories) matches repositories with at least 205 forks. | +| | [**forks:<90**](https://github.com/search?q=forks%3A%3C90&type=Repositories) matches repositories with fewer than 90 forks. | +| | [**forks:10..20**](https://github.com/search?q=forks%3A10..20&type=Repositories) matches repositories with 10 to 20 forks. | + +## Search by number of stars + +You can search repositories based on the number of stars the repositories have, using greater than, less than, and range qualifiers. For more information, see "[Saving repositories with stars](/github/getting-started-with-github/saving-repositories-with-stars)" and "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." + +| Qualifier | 예시 | +| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| stars:n | [**stars:500**](https://github.com/search?utf8=%E2%9C%93&q=stars%3A500&type=Repositories) matches repositories with exactly 500 stars. | +| | [**stars:10..20**](https://github.com/search?q=stars%3A10..20+size%3A%3C1000&type=Repositories) matches repositories 10 to 20 stars, that are smaller than 1000 KB. | +| | [**stars:>=500 fork:true language:php**](https://github.com/search?q=stars%3A%3E%3D500+fork%3Atrue+language%3Aphp&type=Repositories) matches repositories with the at least 500 stars, including forked ones, that are written in PHP. | + +## Search by when a repository was created or last updated + +You can filter repositories based on time of creation or time of last update. For repository creation, you can use the `created` qualifier; to find out when a repository was last updated, you'll want to use the `pushed` qualifier. The `pushed` qualifier will return a list of repositories, sorted by the most recent commit made on any branch in the repository. + +Both take a date as a parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifier | 예시 | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| created:YYYY-MM-DD | [**webos created:<2011-01-01**](https://github.com/search?q=webos+created%3A%3C2011-01-01&type=Repositories) matches repositories with the word "webos" that were created before 2011. | +| pushed:YYYY-MM-DD | [**css pushed:>2013-02-01**](https://github.com/search?utf8=%E2%9C%93&q=css+pushed%3A%3E2013-02-01&type=Repositories) matches repositories with the word "css" that were pushed to after January 2013. | +| | [**case pushed:>=2013-03-06 fork:only**](https://github.com/search?q=case+pushed%3A%3E%3D2013-03-06+fork%3Aonly&type=Repositories) matches repositories with the word "case" that were pushed to on or after March 6th, 2013, and that are forks. | + +## Search by language + +You can search repositories based on the language of the code in the repositories. + +| Qualifier | 예시 | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| language:LANGUAGE | [**rails language:javascript**](https://github.com/search?q=rails+language%3Ajavascript&type=Repositories) matches repositories with the word "rails" that are written in JavaScript. | + +## Search by topic + +You can find all of the repositories that are classified with a particular topic. For more information, see "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)." + +| Qualifier | 예시 | +| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| topic:TOPIC | [**topic:jekyll**](https://github.com/search?utf8=%E2%9C%93&q=topic%3Ajekyll&type=Repositories&ref=searchresults) matches repositories that have been classified with the topic "jekyll." | + +## Search by number of topics + +You can search repositories by the number of topics that have been applied to the repositories, using the `topics` qualifier along with greater than, less than, and range qualifiers. For more information, see "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)" and "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." + +| Qualifier | 예시 | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| topics:n | [**topics:5**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A5&type=Repositories&ref=searchresults) matches repositories that have five topics. | +| | [**topics:>3**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A%3E3&type=Repositories&ref=searchresults) matches repositories that have more than three topics. | + +{% ifversion fpt or ghes %} + +## Search by license + +You can search repositories by the type of license in the repositories. You must use a license keyword to filter repositories by a particular license or license family. For more information, see "[Licensing a repository](/github/creating-cloning-and-archiving-repositories/licensing-a-repository)." + +| Qualifier | 예시 | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| license:LICENSE_KEYWORD | [**license:apache-2.0**](https://github.com/search?utf8=%E2%9C%93&q=license%3Aapache-2.0&type=Repositories&ref=searchresults) matches repositories that are licensed under Apache License 2.0. | + +{% endif %} + +## Search by repository visibility + +You can filter your search based on the visibility of the repositories. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." + +| Qualifier | Example | ------------- | ------------- |{% ifversion fpt or ghes %} | `is:public` | [**is:public org:github**](https://github.com/search?q=is%3Apublic+org%3Agithub&type=Repositories) matches public repositories owned by {% data variables.product.company_short %}.{% endif %} | `is:internal` | [**is:internal test**](https://github.com/search?q=is%3Ainternal+test&type=Repositories) matches internal repositories that you can access and contain the word "test". | `is:private` | [**is:private pages**](https://github.com/search?q=is%3Aprivate+pages&type=Repositories) matches private repositories that you can access and contain the word "pages." + +{% ifversion fpt %} + +## Search based on whether a repository is a mirror + +You can search repositories based on whether the repositories are mirrors and hosted elsewhere. 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)." + +| Qualifier | 예시 | +| -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `mirror:true` | [**mirror:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Atrue+GNOME&type=) matches repositories that are mirrors and contain the word "GNOME." | +| `mirror:false` | [**mirror:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Afalse+GNOME&type=) matches repositories that are not mirrors and contain the word "GNOME." | + +{% endif %} + +## Search based on whether a repository is archived + +You can search repositories based on whether or not the repositories are archived. For more information, see "[Archiving repositories](/repositories/archiving-a-github-repository/archiving-repositories)." + +| Qualifier | 예시 | +| ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `archived:true` | [**archived:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Atrue+GNOME&type=) matches repositories that are archived and contain the word "GNOME." | +| `archived:false` | [**archived:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Afalse+GNOME&type=) matches repositories that are not archived and contain the word "GNOME." | + +{% ifversion fpt %} + +## Search based on number of issues with `good first issue` or `help wanted` labels + +You can search for repositories that have a minimum number of issues labeled `help-wanted` or `good-first-issue` with the qualifiers `help-wanted-issues:>n` and `good-first-issues:>n`. For more information, see "[Encouraging helpful contributions to your project with labels](/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels)." + +| Qualifier | 예시 | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `good-first-issues:>n` | [**good-first-issues:>2 javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+good-first-issues%3A%3E2&type=) matches repositories with more than two issues labeled `good-first-issue` and that contain the word "javascript." | +| `help-wanted-issues:>n` | [**help-wanted-issues:>4 react**](https://github.com/search?utf8=%E2%9C%93&q=react+help-wanted-issues%3A%3E4&type=) matches repositories with more than four issues labeled `help-wanted` and that contain the word "React." | + +## Search based on ability to sponsor + +You can search for repositories whose owners can be sponsored on {% data variables.product.prodname_sponsors %} with the `is:sponsorable` qualifier. For more information, see "[About {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." + +You can search for repositories that have a funding file using the `has:funding-file` qualifier. For more information, see "[About FUNDING files](/github/administering-a-repository/managing-repository-settings/displaying-a-sponsor-button-in-your-repository#about-funding-files)." + +| Qualifier | 예시 | +| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `is:sponsorable` | [**is:sponsorable**](https://github.com/search?q=is%3Asponsorable&type=Repositories) matches repositories whose owners have a {% data variables.product.prodname_sponsors %} profile. | +| `has:funding-file` | [**has:funding-file**](https://github.com/search?q=has%3Afunding-file&type=Repositories) matches repositories that have a FUNDING.yml file. | + +{% endif %} + +## 더 읽을거리 + +- "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" +- "[Searching in forks](/search-github/searching-on-github/searching-in-forks)" diff --git a/translations/ko-KR/content/search-github/searching-on-github/searching-github-marketplace.md b/translations/ko-KR/content/search-github/searching-on-github/searching-github-marketplace.md new file mode 100644 index 0000000000..2789f809b4 --- /dev/null +++ b/translations/ko-KR/content/search-github/searching-on-github/searching-github-marketplace.md @@ -0,0 +1,38 @@ +--- +title: Searching GitHub Marketplace +intro: 'You can search for apps and actions that are available on {% data variables.product.prodname_marketplace %}.' +versions: + fpt: '*' +topics: + - GitHub search +redirect_from: + - /github/searching-for-information-on-github/searching-github-marketplace + - /github/searching-for-information-on-github/searching-on-github/searching-github-marketplace +shortTitle: Search GitHub Marketplace +--- + +## About searching {% data variables.product.prodname_marketplace %} + +You can find apps and actions on {% data variables.product.prodname_marketplace %} in two ways: + +- Search from in {% data variables.product.prodname_marketplace %}. +- Search across all of {% data variables.product.prodname_dotcom_the_website %} and then filter the results. + +## Searching in {% data variables.product.prodname_marketplace %} + +1. At the top of any page, click **Marketplace**. ![Marketplace link](/assets/images/help/search/marketplace-link.png) +2. Type any keywords and press **Enter**. ![Search for linter on {% data variables.product.prodname_marketplace %}](/assets/images/help/search/marketplace-apps-and-actions-search-field.png) +3. Optionally, filter your results by clicking one or more options in the left sidebar. + +## Searching across {% data variables.product.prodname_dotcom_the_website %} + +Anytime you search across all of {% data variables.product.prodname_dotcom_the_website %}, you can filter the results to see matching apps and actions from {% data variables.product.prodname_marketplace %}. + +1. Navigate to https://github.com/search. +2. Type any keywords and press **Enter**. ![search field](/assets/images/help/search/search-field.png) +3. In the left sidebar, click **Marketplace**. ![Search results for linter with Marketplace side-menu option highlighted](/assets/images/help/search/marketplace-left-side-navigation.png) + +## 더 읽을거리 + +- "[About {% data variables.product.prodname_marketplace %}](/github/customizing-your-github-workflow/about-github-marketplace)" +- "[Using actions from {% data variables.product.prodname_marketplace %} in your workflow](/actions/automating-your-workflow-with-github-actions/using-actions-from-github-marketplace-in-your-workflow)" diff --git a/translations/ko-KR/content/search-github/searching-on-github/searching-in-forks.md b/translations/ko-KR/content/search-github/searching-on-github/searching-in-forks.md new file mode 100644 index 0000000000..3abd13101f --- /dev/null +++ b/translations/ko-KR/content/search-github/searching-on-github/searching-in-forks.md @@ -0,0 +1,32 @@ +--- +title: Searching in forks +intro: 'By default, [forks](/articles/about-forks) are not shown in search results. You can choose to include them in repository searches, and in code searches if they meet certain criteria.' +redirect_from: + - /articles/searching-in-forks + - /github/searching-for-information-on-github/searching-in-forks + - /github/searching-for-information-on-github/searching-on-github/searching-in-forks +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +To show forks in [repository search](/search-github/searching-on-github/searching-for-repositories) results, add `fork:true` or `fork:only` to your query. + +Forks are only indexed for [code search](/search-github/searching-on-github/searching-code) when they have more stars than the parent repository. You will not be able to search the code in a fork that has less stars than its parent. To show forks with more stars than the parent repository in code search results, add `fork:true` or `fork:only` to your query. + +The `fork:true` qualifier finds all results that match your search query, including forks. The `fork:only` qualifier finds _only_ forks that match your search query. + +| Qualifier | 예시 | +| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `fork:true` | [**github fork:true**](https://github.com/search?q=github+fork%3Atrue&type=Repositories) matches all repositories containing the word "github," including forks. | +| | [**android language:java fork:true**](https://github.com/search?q=android+language%3Ajava+fork%3Atrue&type=Code) matches code with the word "android" that's written in Java, in both forks and regular repositories. | +| `fork:only` | [**github fork:only**](https://github.com/search?q=github+fork%3Aonly&type=Repositories) matches all fork repositories containing the word "github." | +| | [**forks:>500 fork:only**](https://github.com/search?q=forks%3A%3E500+fork%3Aonly&type=Repositories) matches repositories with more than 500 forks, and only returns those that are forks. | + +## 더 읽을거리 + +- "[About forks](/articles/about-forks)" +- "[About searching on GitHub](/search-github/getting-started-with-searching-on-github/about-searching-on-github)" diff --git a/translations/ko-KR/content/search-github/searching-on-github/searching-issues-and-pull-requests.md b/translations/ko-KR/content/search-github/searching-on-github/searching-issues-and-pull-requests.md new file mode 100644 index 0000000000..5de8b8967d --- /dev/null +++ b/translations/ko-KR/content/search-github/searching-on-github/searching-issues-and-pull-requests.md @@ -0,0 +1,343 @@ +--- +title: Searching issues and pull requests +intro: 'You can search for issues and pull requests on {% data variables.product.product_name %} and narrow the results using these search qualifiers in any combination.' +redirect_from: + - /articles/searching-issues/ + - /articles/searching-issues-and-pull-requests + - /github/searching-for-information-on-github/searching-issues-and-pull-requests + - /github/searching-for-information-on-github/searching-on-github/searching-issues-and-pull-requests +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +shortTitle: Search issues & PRs +--- + +You can search for issues and pull requests globally across all of {% data variables.product.product_name %}, or search for issues and pull requests within a particular organization. For more information, see "[About searching on {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)." + +{% tip %} + +**Tips:**{% ifversion ghes or ghae %} + - This article contains example searches on the {% data variables.product.prodname_dotcom %}.com website, but you can use the same search filters on {% data variables.product.product_location %}.{% endif %} + - For a list of search syntaxes that you can add to any search qualifier to further improve your results, see "[Understanding the search syntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)". + - Use quotations around multi-word search terms. For example, if you want to search for issues with the label "In progress," you'd search for `label:"in progress"`. Search is not case sensitive. + - {% data reusables.search.search_issues_and_pull_requests_shortcut %} + + {% endtip %} + +## Search only issues or pull requests + +By default, {% data variables.product.product_name %} search will return both issues and pull requests. However, you can restrict search results to just issues or pull requests using the `type` or `is` qualifier. + +| Qualifier | 예시 | +| ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `type:pr` | [**cat type:pr**](https://github.com/search?q=cat+type%3Apr&type=Issues) matches pull requests with the word "cat." | +| `type:issue` | [**github commenter:defunkt type:issue**](https://github.com/search?q=github+commenter%3Adefunkt+type%3Aissue&type=Issues) matches issues that contain the word "github," and have a comment by @defunkt. | +| `is:pr` | [**event is:pr**](https://github.com/search?utf8=%E2%9C%93&q=event+is%3Apr&type=) matches pull requests with the word "event." | +| `is:issue` | [**is:issue label:bug is:closed**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aissue+label%3Abug+is%3Aclosed&type=) matches closed issues with the label "bug." | + +## Search by the title, body, or comments + +With the `in` qualifier you can restrict your search to the title, body, comments, or any combination of these. When you omit this qualifier, the title, body, and comments are all searched. + +| Qualifier | 예시 | +| ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | +| `in:title` | [**warning in:title**](https://github.com/search?q=warning+in%3Atitle&type=Issues) matches issues with "warning" in their title. | +| `in:body` | [**error in:title,body**](https://github.com/search?q=error+in%3Atitle%2Cbody&type=Issues) matches issues with "error" in their title or body. | +| `in:comments` | [**shipit in:comments**](https://github.com/search?q=shipit+in%3Acomment&type=Issues) matches issues mentioning "shipit" in their comments. | + +## Search within a user's or organization's repositories + +To search issues and pull requests in all repositories owned by a certain user or organization, you can use the `user` or `org` qualifier. To search issues and pull requests in a specific repository, you can use the `repo` qualifier. + +{% data reusables.pull_requests.large-search-workaround %} + + +| Qualifier | 예시 | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 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. + +| Qualifier | 예시 | +| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `state:open` | [**libraries state:open mentions:vmg**](https://github.com/search?utf8=%E2%9C%93&q=libraries+state%3Aopen+mentions%3Avmg&type=Issues) matches open issues that mention @vmg with the word "libraries." | +| `state:closed` | [**design state:closed in:body**](https://github.com/search?utf8=%E2%9C%93&q=design+state%3Aclosed+in%3Abody&type=Issues) matches closed issues with the word "design" in the body. | +| `is:open` | [**performance is:open is:issue**](https://github.com/search?q=performance+is%3Aopen+is%3Aissue&type=Issues) matches open issues with the word "performance." | +| `is:closed` | [**android is:closed**](https://github.com/search?utf8=%E2%9C%93&q=android+is%3Aclosed&type=) matches closed issues and pull requests with the word "android." | + +## Filter by repository visibility + +You can filter by the visibility of the repository containing the issues and pull requests using the `is` qualifier. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." + +| Qualifier | Example | ------------- | ------------- |{% ifversion fpt or ghes %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Issues) matches issues and pull requests in public repositories.{% endif %}{% ifversion fpt or ghes or ghae %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Issues) matches issues and pull requests in internal repositories.{% endif %} | `is:private` | [**is:private cupcake**](https://github.com/search?q=is%3Aprivate+cupcake&type=Issues) matches issues and pull requests that contain the word "cupcake" in private repositories you can access. + +## Search by author + +The `author` qualifier finds issues and pull requests created by a certain user or integration account. + +| Qualifier | 예시 | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| author:USERNAME | [**cool author:gjtorikian**](https://github.com/search?q=cool+author%3Agjtorikian&type=Issues) matches issues and pull requests with the word "cool" that were created by @gjtorikian. | +| | [**bootstrap in:body author:mdo**](https://github.com/search?q=bootstrap+in%3Abody+author%3Amdo&type=Issues) matches issues written by @mdo that contain the word "bootstrap" in the body. | +| author:app/USERNAME | [**author:app/robot**](https://github.com/search?q=author%3Aapp%2Frobot&type=Issues) matches issues created by the integration account named "robot." | + +## Search by assignee + +The `assignee` qualifier finds issues and pull requests that are assigned to a certain user. You cannot search for issues and pull requests that have _any_ assignee, however, you can search for [issues and pull requests that have no assignee](#search-by-missing-metadata). + +| Qualifier | 예시 | +| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| assignee:USERNAME | [**assignee:vmg repo:libgit2/libgit2**](https://github.com/search?utf8=%E2%9C%93&q=assignee%3Avmg+repo%3Alibgit2%2Flibgit2&type=Issues) matches issues and pull requests in libgit2's project libgit2 that are assigned to @vmg. | + +## Search by mention + +The `mentions` qualifier finds issues that mention a certain user. For more information, see "[Mentioning people and teams](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)." + +| Qualifier | 예시 | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| mentions:USERNAME | [**resque mentions:defunkt**](https://github.com/search?q=resque+mentions%3Adefunkt&type=Issues) matches issues with the word "resque" that mention @defunkt. | + +## Search by team mention + +For organizations and teams you belong to, you can use the `team` qualifier to find issues or pull requests that @mention a certain team within that organization. Replace these sample names with your organization and team name to perform a search. + +| Qualifier | 예시 | +| ------------------------- | ----------------------------------------------------------------------------------------------------- | +| team:ORGNAME/TEAMNAME | **team:jekyll/owners** matches issues where the `@jekyll/owners` team is mentioned. | +| | **team:myorg/ops is:open is:pr** matches open pull requests where the `@myorg/ops` team is mentioned. | + +## Search by commenter + +The `commenter` qualifier finds issues that contain a comment from a certain user. + +| Qualifier | 예시 | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| commenter:USERNAME | [**github commenter:defunkt org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Adefunkt+org%3Agithub&type=Issues) matches issues in repositories owned by GitHub, that contain the word "github," and have a comment by @defunkt. | + +## Search by a user that's involved in an issue or pull request + +You can use the `involves` qualifier to find issues that in some way involve a certain user. The `involves` qualifier is a logical OR between the `author`, `assignee`, `mentions`, and `commenter` qualifiers for a single user. In other words, this qualifier finds issues and pull requests that were either created by a certain user, assigned to that user, mention that user, or were commented on by that user. + +| Qualifier | 예시 | +| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 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 %} +## 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. + +| Qualifier | 예시 | +| --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `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 %} + +## Search by label + +You can narrow your results by labels, using the `label` qualifier. Since issues can have multiple labels, you can list a separate qualifier for each issue. + +| Qualifier | 예시 | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| label:LABEL | [**label:"help wanted" language:ruby**](https://github.com/search?utf8=%E2%9C%93&q=label%3A%22help+wanted%22+language%3Aruby&type=Issues) matches issues with the label "help wanted" that are in Ruby repositories. | +| | [**broken in:body -label:bug label:priority**](https://github.com/search?q=broken+in%3Abody+-label%3Abug+label%3Apriority&type=Issues) matches issues with the word "broken" in the body, that lack the label "bug", but *do* have the label "priority." | +| | [**label:bug label:resolved**](https://github.com/search?l=&q=label%3Abug+label%3Aresolved&type=Issues) matches issues with the labels "bug" and "resolved."{% ifversion fpt or ghes > 3.2 or ghae-next %} +| | [**label:bug,resolved**](https://github.com/search?q=label%3Abug%2Cresolved&type=Issues) matches issues with the label "bug" or the label "resolved."{% endif %} + +## Search by milestone + +The `milestone` qualifier finds issues or pull requests that are a part of a [milestone](/articles/about-milestones) within a repository. + +| Qualifier | 예시 | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| milestone:MILESTONE | [**milestone:"overhaul"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22overhaul%22&type=Issues) matches issues that are in a milestone named "overhaul." | +| | [**milestone:"bug fix"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22bug+fix%22&type=Issues) matches issues that are in a milestone named "bug fix." | + +## Search by project board + +You can use the `project` qualifier to find issues that are associated with a specific [project board](/articles/about-project-boards/) in a repository or organization. You must search project boards by the project board number. You can find the project board number at the end of a project board's URL. + +| Qualifier | 예시 | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------- | +| project:PROJECT_BOARD | **project:github/57** matches issues owned by GitHub that are associated with the organization's project board 57. | +| project:REPOSITORY/PROJECT_BOARD | **project:github/linguist/1** matches issues that are associated with project board 1 in @github's linguist repository. | + +## Search by commit status + +You can filter pull requests based on the status of the commits. This is especially useful if you are using [the Status API](/rest/reference/repos#statuses) or a CI service. + +| Qualifier | 예시 | +| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `status:pending` | [**language:go status:pending**](https://github.com/search?utf8=%E2%9C%93&q=language%3Ago+status%3Apending) matches pull requests opened into Go repositories where the status is pending. | +| `status:success` | [**is:open status:success finally in:body**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aopen+status%3Asuccess+finally+in%3Abody&type=Issues) matches open pull requests with the word "finally" in the body with a successful status. | +| `status:failure` | [**created:2015-05-01..2015-05-30 status:failure**](https://github.com/search?utf8=%E2%9C%93&q=created%3A2015-05-01..2015-05-30+status%3Afailure&type=Issues) matches pull requests opened on May 2015 with a failed status. | + +## Search by commit SHA + +If you know the specific SHA hash of a commit, you can use it to search for pull requests that contain that SHA. The SHA syntax must be at least seven characters. + +| Qualifier | 예시 | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| SHA | [**e1109ab**](https://github.com/search?q=e1109ab&type=Issues) matches pull requests with a commit SHA that starts with `e1109ab`. | +| | [**0eff326d6213c is:merged**](https://github.com/search?q=0eff326d+is%3Amerged&type=Issues) matches merged pull requests with a commit SHA that starts with `0eff326d6213c`. | + +## Search by branch name + +You can filter pull requests based on the branch they came from (the "head" branch) or the branch they are merging into (the "base" branch). + +| Qualifier | 예시 | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| head:HEAD_BRANCH | [**head:change is:closed is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=head%3Achange+is%3Aclosed+is%3Aunmerged) matches pull requests opened from branch names beginning with the word "change" that are closed. | +| base:BASE_BRANCH | [**base:gh-pages**](https://github.com/search?utf8=%E2%9C%93&q=base%3Agh-pages) matches pull requests that are being merged into the `gh-pages` branch. | + +## Search by language + +With the `language` qualifier you can search for issues and pull requests within repositories that are written in a certain language. + +| Qualifier | 예시 | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | +| language:LANGUAGE | [**language:ruby state:open**](https://github.com/search?q=language%3Aruby+state%3Aopen&type=Issues) matches open issues that are in Ruby repositories. | + +## Search by number of 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. + +| Qualifier | 예시 | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| comments:n | [**state:closed comments:>100**](https://github.com/search?q=state%3Aclosed+comments%3A%3E100&type=Issues) matches closed issues with more than 100 comments. | +| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Issues) matches issues with comments ranging from 500 to 1,000. | + +## Search by number of interactions + +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). The interactions count is the number of reactions and comments on an issue or pull request. + +| Qualifier | 예시 | +| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| interactions:n | [** interactions:>2000**](https://github.com/search?q=interactions%3A%3E2000) matches pull requests or issues with more than 2000 interactions. | +| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) matches pull requests or issues with interactions ranging from 500 to 1,000. | + +## Search by number of reactions + +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 | 예시 | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | +| reactions:n | [** reactions:>1000**](https://github.com/search?q=reactions%3A%3E1000&type=Issues) matches issues with more than 1000 reactions. | +| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) matches issues with reactions ranging from 500 to 1,000. | + +## Search for draft pull requests +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 %} | `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 %} + +## Search by pull request review status and reviewer + +You can filter pull requests based on their [review status](/articles/about-pull-request-reviews) (_none_, _required_, _approved_, or _changes requested_), by reviewer, and by requested reviewer. + +| Qualifier | 예시 | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `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. Requested reviewers are no longer listed in the search results after they review a pull request. 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 or ghes > 3.2 %} +| 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) matches pull requests that have review requests from the team `atom/design`. Requested reviewers are no longer listed in the search results after they review a pull request. | + +## Search by when an issue or pull request was created or last updated + +You can filter issues based on times of creation, or when they were last updated. For issue creation, you can use the `created` qualifier; to find out when an issue was last updated, you'll want to use the `updated` qualifier. + +Both take a date as a parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifier | 예시 | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| created:YYYY-MM-DD | [**language:c# created:<2011-01-01 state:open**](https://github.com/search?q=language%3Ac%23+created%3A%3C2011-01-01+state%3Aopen&type=Issues) matches open issues that were created before 2011 in repositories written in C#. | +| updated:YYYY-MM-DD | [**weird in:body updated:>=2013-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2013-02-01&type=Issues) matches issues with the word "weird" in the body that were updated after February 2013. | + +## Search by when an issue or pull request was closed + +You can filter issues and pull requests based on when they were closed, using the `closed` qualifier. + +This qualifier takes a date as its parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifier | 예시 | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| closed:YYYY-MM-DD | [**language:swift closed:>2014-06-11**](https://github.com/search?q=language%3Aswift+closed%3A%3E2014-06-11&type=Issues) matches issues and pull requests in Swift that were closed after June 11, 2014. | +| | [**data in:body closed:<2012-10-01**](https://github.com/search?utf8=%E2%9C%93&q=data+in%3Abody+closed%3A%3C2012-10-01+&type=Issues) matches issues and pull requests with the word "data" in the body that were closed before October 2012. | + +## Search by when a pull request was merged + +You can filter pull requests based on when they were merged, using the `merged` qualifier. + +This qualifier takes a date as its parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifier | 예시 | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| merged:YYYY-MM-DD | [**language:javascript merged:<2011-01-01**](https://github.com/search?q=language%3Ajavascript+merged%3A%3C2011-01-01+&type=Issues) matches pull requests in JavaScript repositories that were merged before 2011. | +| | [**fast in:title language:ruby merged:>=2014-05-01**](https://github.com/search?q=fast+in%3Atitle+language%3Aruby+merged%3A%3E%3D2014-05-01+&type=Issues) matches pull requests in Ruby with the word "fast" in the title that were merged after May 2014. | + +## Search based on whether a pull request is merged or unmerged + +You can filter pull requests based on whether they're merged or unmerged using the `is` qualifier. + +| Qualifier | 예시 | +| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `is:merged` | [**bugfix is:pr is:merged**](https://github.com/search?utf8=%E2%9C%93&q=bugfix+is%3Apr+is%3Amerged&type=) matches merged pull requests with the word "bugfix." | +| `is:unmerged` | [**error is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=error+is%3Aunmerged&type=) matches closed issues and pull requests with the word "error." | + +## Search based on whether a repository is archived + +The `archived` qualifier filters your results based on whether an issue or pull request is in an archived repository. + +| Qualifier | 예시 | +| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `archived:true` | [**archived:true GNOME**](https://github.com/search?q=archived%3Atrue+GNOME&type=) matches issues and pull requests that contain the word "GNOME" in archived repositories you have access to. | +| `archived:false` | [**archived:false GNOME**](https://github.com/search?q=archived%3Afalse+GNOME&type=) matches issues and pull requests that contain the word "GNOME" in unarchived repositories you have access to. | + +## Search based on whether a conversation is locked + +You can search for an issue or pull request that has a locked conversation using the `is` qualifier. For more information, see "[Locking conversations](/communities/moderating-comments-and-conversations/locking-conversations)." + +| Qualifier | 예시 | +| ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `is:locked` | [**code of conduct is:locked is:issue archived:false**](https://github.com/search?q=code+of+conduct+is%3Alocked+is%3Aissue+archived%3Afalse) matches issues or pull requests with the words "code of conduct" that have a locked conversation in a repository that is not archived. | +| `is:unlocked` | [**code of conduct is:unlocked is:issue archived:false**](https://github.com/search?q=code+of+conduct+is%3Aunlocked+archived%3Afalse) matches issues or pull requests with the words "code of conduct" that have an unlocked conversation in a repository that is not archived. | + +## Search by missing metadata + +You can narrow your search to issues and pull requests that are missing certain metadata, using the `no` qualifier. That metadata includes: + +* Labels +* Milestones +* Assignees +* Projects + +| Qualifier | 예시 | +| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `no:label` | [**priority no:label**](https://github.com/search?q=priority+no%3Alabel&type=Issues) matches issues and pull requests with the word "priority" that also don't have any labels. | +| `no:milestone` | [**sprint no:milestone type:issue**](https://github.com/search?q=sprint+no%3Amilestone+type%3Aissue&type=Issues) matches issues not associated with a milestone containing the word "sprint." | +| `no:assignee` | [**important no:assignee language:java type:issue**](https://github.com/search?q=important+no%3Aassignee+language%3Ajava+type%3Aissue&type=Issues) matches issues not associated with an assignee, containing the word "important," and in Java repositories. | +| `no:project` | [**build no:project**](https://github.com/search?utf8=%E2%9C%93&q=build+no%3Aproject&type=Issues) matches issues not associated with a project board, containing the word "build." | + +## 더 읽을거리 + +- "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" diff --git a/translations/ko-KR/content/search-github/searching-on-github/searching-topics.md b/translations/ko-KR/content/search-github/searching-on-github/searching-topics.md new file mode 100644 index 0000000000..5503160150 --- /dev/null +++ b/translations/ko-KR/content/search-github/searching-on-github/searching-topics.md @@ -0,0 +1,55 @@ +--- +title: Searching topics +intro: 'You can search for topics associated with repositories on {% data variables.product.product_name %}.' +redirect_from: + - /articles/searching-topics + - /github/searching-for-information-on-github/searching-topics + - /github/searching-for-information-on-github/searching-on-github/searching-topics +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +## Search {% data variables.product.product_name %} for topics + +You can search for topics on {% data variables.product.product_name %}, explore related topics, and see how many repositories are associated with a certain topic. + +1. Navigate to https://github.com/search. +2. Type a topic keyword. ![search field](/assets/images/help/search/search-field.png) +3. In the left sidebar, to narrow your search to topics, click **Topics**. +{% ifversion fpt %} + ![Jekyll repository search results page with topics side-menu option highlighted](/assets/images/help/search/topic-left-side-navigation-dotcom.png){% else %} +![Jekyll repository search results page on dotcom with topics side-menu option highlighted](/assets/images/help/search/topic-left-side-navigation.png){% endif %} + +## Narrowing your search with search qualifiers + +If you want to explore repositories about a certain topic, find projects to contribute to, or learn which topics are most popular on {% data variables.product.product_name %}, you can search topics with the search qualifiers `is:featured`, `is:curated`, `repositories:n` and `created:YYYY-MM-DD`. + +The `is:featured` search qualifier will narrow search results to the topics with the most repositories on {% data variables.product.product_name %}. These topics are also featured at https://github.com/topics/. + +The `is:curated` search qualifier will narrow search results to topics that community members have added extra information to. For more information, see the [explore repository](https://github.com/github/explore). + +You can filter topics based when they were created using the date parameter and `created:` or based on how many repositories are associated with this topic using `repositories:n`. Both of these qualifiers can use the [greater than and less than range qualifiers](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). + +{% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifier | 예시 | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `is:curated` | [**is:curated javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+is%3Acurated&type=Topics) matches topics that are curated and contain the word "javascript." | +| `is:featured` | [**is:featured javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+is%3Afeatured&type=Topics) matches topics that are featured on https://github.com/topics/ and contain the word "javascript." | +| `is:not-curated` | [**is:not-curated javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+is%3Anot-curated&type=Topics) matches topics that don't have extra information, such as a description or logo, and contain the word "javascript." | +| `is:not-featured` | [**is:not-featured javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+is%3Anot-featured&type=Topics) matches topics that aren't featured on https://github.com/topics/ and contain the word "javascript." | +| `repositories:n` | [**repositories:>5000**](https://github.com/search?q=repositories%3A%3E5000) matches topics that have more than 5000 repositories. | +| created:YYYY-MM-DD | [**Serverless created:>2019-01-01**](https://github.com/search?q=Serverless+created%3A%3E2019-01-01&type=Topics) matches topics with the word "serverless" that were created after 2018. | + +## Search repositories by topic + +You can use the `topic:` qualifier to find every repository connected to a particular topic. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories/#search-by-topic)." + +## 더 읽을거리 +- "[Classifying your repository with topics](/articles/classifying-your-repository-with-topics)" diff --git a/translations/ko-KR/content/search-github/searching-on-github/searching-users.md b/translations/ko-KR/content/search-github/searching-on-github/searching-users.md new file mode 100644 index 0000000000..dc6e27b529 --- /dev/null +++ b/translations/ko-KR/content/search-github/searching-on-github/searching-users.md @@ -0,0 +1,106 @@ +--- +title: Searching users +intro: 'You can search for users on {% data variables.product.product_name %} and narrow the results using these user search qualifiers in any combination.' +redirect_from: + - /articles/searching-users + - /github/searching-for-information-on-github/searching-users + - /github/searching-for-information-on-github/searching-on-github/searching-users +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +You can search for users globally across all of {% data variables.product.product_name %}. For more information, see "[About searching on {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)." + +{% data reusables.search.syntax_tips %} + +## Search only users or organizations + +By default, searching users will return both personal and organizations. However, you can use the `type` qualifier to restrict search results to personal accounts or organizations only. + +| Qualifier | 예시 | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `type:user` | [**mike in:name created:<2011-01-01 type:user**](https://github.com/search?q=mike+in:name+created%3A%3C2011-01-01+type%3Auser&type=Users) matches personal accounts named "mike" that were created before 2011. | +| `type:org` | [**data in:email type:org**](https://github.com/search?q=data+in%3Aemail+type%3Aorg&type=Users) matches organizations with the word "data" in their email. | + +## Search by account name, full name, or public email + +You can filter your search to the personal user or organization account name with `user` or `org` qualifiers. + +With the `in` qualifier you can restrict your search to the username (`login`), full name, public email, or any combination of these. When you omit this qualifier, only the username and email address are searched. For privacy reasons, you cannot search by email domain name. + +| Qualifier | 예시 | +| ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `user:name` | [**user:octocat**](https://github.com/search?q=user%3Aoctocat&type=Users) matches the user with the username "octocat". | +| `org:name` | [**org:electron type:users**](https://github.com/search?q=org%3Aelectron+type%3Ausers&type=Users) matches the Electron organization's account name. | +| `in:login` | [**kenya in:login**](https://github.com/search?q=kenya+in%3Alogin&type=Users) matches users with the word "kenya" in their username. | +| `in:name` | [**bolton in:name**](https://github.com/search?q=bolton+in%3Afullname&type=Users) matches users whose real name contains the word "bolton." | +| `fullname:firstname lastname` | [**fullname:nat friedman**](https://github.com/search?q=fullname%3Anat+friedman&type=Users) matches a user with the full name "Nat Friedman." Note: This search qualifier is sensitive to spacing. | +| `in:email` | [**data in:email**](https://github.com/search?q=data+in%3Aemail&type=Users&utf8=%E2%9C%93) matches users with the word "data" in their email. | + +## Search by number of repositories a user owns + +You can filter users based on the number of repositories they own, using the `repos` qualifier and [greater than, less than, and range qualifiers](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). + +| Qualifier | 예시 | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| repos:n | [**repos:>9000**](https://github.com/search?q=repos%3A%3E%3D9000&type=Users) matches users whose repository count is over 9,000. | +| | [**bert repos:10..30**](https://github.com/search?q=bert+repos%3A10..30&type=Users) matches users with the word "bert" in their username or real name who own 10 to 30 repositories. | + +## Search by location + +You can search for users by the location indicated in their profile. + +| Qualifier | 예시 | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| location:LOCATION | [**repos:1 location:iceland**](https://github.com/search?q=repos%3A1+location%3Aiceland&type=Users) matches users with exactly one repository that live in Iceland. | + +## Search by repository language + +Using the `language` qualifier you can search for users based on the languages of repositories they own. + +| Qualifier | 예시 | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| language:LANGUAGE | [**language:javascript location:russia**](https://github.com/search?q=language%3Ajavascript+location%3Arussia&type=Users) matches users in Russia with a majority of their repositories written in JavaScript. | +| | [**jenny language:javascript in:fullname**](https://github.com/search?q=jenny+language%3Ajavascript+in%3Afullname&type=Users) matches users with JavaScript repositories whose full name contains the word "jenny." | + +## Search by when a user account was created + +You can filter users based on when they joined {% data variables.product.product_name %} with the `created` qualifier. This takes a date as its parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifier | 예시 | +| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| created:YYYY-MM-DD | [**created:<2011-01-01**](https://github.com/search?q=created%3A%3C2011-01-01&type=Users) matches users that joined before 2011. | +| | [**created:>=2013-05-11**](https://github.com/search?q=created%3A%3E%3D2013-05-11&type=Users) matches users that joined at or after May 11th, 2013. | +| | [**created:2013-03-06 location:london**](https://github.com/search?q=created%3A2013-03-06+location%3Alondon&type=Users) matches users that joined on March 6th, 2013, who list their location as London. | +| | [**created:2010-01-01..2011-01-01 john in:login**](https://github.com/search?q=created%3A2010-01-01..2011-01-01+john+in%3Ausername&type=Users) matches users that joined between 2010 and 2011 with the word "john" in their username. | + +## Search by number of followers + +You can filter users based on the number of followers that they have, using the `followers` qualifier with [greater than, less than, and range qualifiers](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). + +| Qualifier | 예시 | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| followers:n | [**followers:>=1000**](https://github.com/search?q=followers%3A%3E%3D1000&type=Users) matches users with 1,000 or more followers. | +| | [**sparkle followers:1..10**](https://github.com/search?q=sparkle+followers%3A1..10&type=Users) matches users with between 1 and 10 followers, with the word "sparkle" in their name. | + +{% ifversion fpt %} + +## Search based on ability to sponsor + +You can search for users and organizations who can be sponsored on {% data variables.product.prodname_sponsors %} with the `is:sponsorable` qualifier. For more information, see "[About {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." + +| Qualifier | 예시 | +| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `is:sponsorable` | [**is:sponsorable**](https://github.com/search?q=is%3Asponsorable&type=Users) matches users and organizations who have a {% data variables.product.prodname_sponsors %} profile. | + +{% endif %} + +## 더 읽을거리 + +- "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" diff --git a/translations/ko-KR/content/search-github/searching-on-github/searching-wikis.md b/translations/ko-KR/content/search-github/searching-on-github/searching-wikis.md new file mode 100644 index 0000000000..63b21c4fcb --- /dev/null +++ b/translations/ko-KR/content/search-github/searching-on-github/searching-wikis.md @@ -0,0 +1,51 @@ +--- +title: Searching wikis +intro: 'You can search wikis on {% data variables.product.product_name %} and narrow the results using these wiki search qualifiers in any combination.' +redirect_from: + - /articles/searching-wikis + - /github/searching-for-information-on-github/searching-wikis + - /github/searching-for-information-on-github/searching-on-github/searching-wikis +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +You can search wikis globally across all of {% data variables.product.product_name %}, or search wikis within a particular repository or organization. For more information, see "[About searching on {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)." + +{% data reusables.search.syntax_tips %} + +## Search within a user's or organization's repositories + +To find wiki pages from all repositories owned by a certain user or organization, use the `user` or `org` qualifier. To find wiki pages from a specific repository, use the `repo` qualifier. + +| Qualifier | 예시 | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**user:defunkt**](https://github.com/search?q=user%3Adefunkt&type=Wikis) matches wiki pages from repositories owned by @defunkt. | +| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=Wikis&utf8=%E2%9C%93) matches wikis in repositories owned by the GitHub organization. | +| repo:USERNAME/REPOSITORY | [**repo:defunkt/gibberish**](https://github.com/search?q=user%3Adefunkt&type=Wikis) matches wiki pages from @defunkt's "gibberish" repository. | + +## Search within a wiki page title or body text + +The `in` qualifier limits the search to the wiki page title or body text. Without the qualifier, both the title and body text are searched. + +| Qualifier | 예시 | +| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `in:title` | [**usage in:title**](https://github.com/search?q=usage+in%3Atitle&type=Wikis) matches wiki page titles with the word "usage." | +| `in:body` | [**installation in:body**](https://github.com/search?q=installation+in%3Abody&type=Wikis) matches wiki pages with the word "installation" in their main body text. | + +## Search by last updated date + +The `updated` qualifier matches wiki pages that were last updated within the specified date range. + +{% data reusables.search.date_gt_lt %} + +| Qualifier | 예시 | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| updated:YYYY-MM-DD | [**usage updated:>2016-01-01**](https://github.com/search?q=usage+updated%3A>2016-01-01&type=Wikis) matches wiki pages with the word "usage" that were last updated after 2016-01-01. | + +## 더 읽을거리 + +- "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" diff --git a/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md b/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md index 058fafa671..9ad81d898c 100644 --- a/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md +++ b/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md @@ -30,6 +30,7 @@ shortTitle: Manage payment tiers 1. Optionally, to edit a draft tier, find the draft tier and click **Edit**. ![Edit button next to draft tier](/assets/images/help/sponsors/draft-tier-edit.png) {% data reusables.sponsors.click-add-tier %} {% data reusables.sponsors.tier-price-description %} +{% data reusables.sponsors.add-welcome-message %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} diff --git a/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md b/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md index f0f6e763f7..9a8814b65c 100644 --- a/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md +++ b/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md @@ -51,6 +51,7 @@ To join {% data variables.product.prodname_sponsors %} as an individual contribu {% data reusables.sponsors.navigate-to-sponsor-tiers-tab %} {% data reusables.sponsors.click-add-tier %} {% data reusables.sponsors.tier-price-description %} +{% data reusables.sponsors.add-welcome-message %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} {% data reusables.sponsors.add-more-tiers %} diff --git a/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md b/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md index b2d9d81cf5..1dfe72626c 100644 --- a/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md +++ b/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md @@ -50,6 +50,7 @@ After {% data variables.product.prodname_dotcom %} reviews your application, you {% data reusables.sponsors.navigate-to-sponsor-tiers-tab %} {% data reusables.sponsors.click-add-tier %} {% data reusables.sponsors.tier-price-description %} +{% data reusables.sponsors.add-welcome-message %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} {% data reusables.sponsors.add-more-tiers %} diff --git a/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md b/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md index 3e8dd62c5c..793255f4ba 100644 --- a/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md +++ b/translations/ko-KR/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md @@ -37,6 +37,8 @@ The W-8 BEN and W-8 BEN-E tax forms ask for a "U.S. taxpayer identification numb If you are not a U.S. citizen or other U.S. person, including a resident alien individual, then you will usually need to provide the "Foreign tax identifying number". This is a tax identification number that your country of residence has issued you. +If your country of residence or billing country is India, then you can use your Permanent Account Number (PAN) as your tax identification number. + {% note %} **Note:** If your country does not require citizens to have a tax number issued by the government, then you can instead write "not legally required". @@ -56,6 +58,18 @@ If you are a taxpayer in the United States and earn more than 600 US dollars in {% data reusables.sponsors.sponsorships-not-tax-deductible %} +## Sales tax + +GitHub is providing information to assist you in calculating your sales tax obligations. This information is not personalized to your country or tax situation and we recommend you talk to a professional to understand your specific obligations. However, we'd like to provide some high-level information to help you understand the general principles of digital sales tax. + +In most countries around the world, sales tax for digital transactions is based on the location of the recipient, not on the seller. For example, if you are a maintainer in the United States and you provide a taxable benefit to a Sponsor in Germany, German sales tax would apply. + +Sales tax is generally only applicable when a good or service of value is being provided. Goodwill/general support/undying appreciation is not normally taxable. + +In the US, both B2B (business-to-business) and B2C (business-to-consumer) are subject to sales tax. + +In the EU and most other countries and regions, B2C sales are subject to sales tax. B2B sales are not subject to tax. C2C and C2B sales where a consumer is not registered for VAT are not taxable. + ## 더 읽을거리 - [Viewing your sponsors and sponsorships](/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships) diff --git a/translations/ko-KR/data/glossaries/external.yml b/translations/ko-KR/data/glossaries/external.yml index e13620346c..d9d3e07e05 100644 --- a/translations/ko-KR/data/glossaries/external.yml +++ b/translations/ko-KR/data/glossaries/external.yml @@ -9,7 +9,7 @@ - term: 계정 복구 토큰 description: >- - Recover Accounts Elsewhere라고 하는 계정 복구 설정의 일부로 저장된 인증 자격 증명입니다. Recover Accounts Elsewhere에 이 백업 자격 증명을 저장할 수 있습니다. + **Deprecated and will be disabled December 1st, 2021.** The authentication credential stored as part of an account recovery setup called Recover Accounts Elsewhere that allows you to store this backup credential. - term: API 미리 보기 description: >- @@ -574,7 +574,7 @@ - term: Recover Accounts Elsewhere description: >- - 사용자가 2단계 인증 방법 또는 복구 코드에 대한 액세스 권한을 잃은 경우 GitHub 계정에 추가 보안 요소를 추가할 수 있습니다. 사용자는 GitHub 계정에 대한 계정 복구 토큰 형태로 Facebook 계정에 대한 인증 자격 증명을 저장하여 GitHub 계정을 Facebook 계정과 연결할 수 있습니다. + **Deprecated and will be disabled December 1st, 2021.** Allows users to add an extra security factor to their GitHub account in case they lose access to their two-factor authentication method or recovery codes. Users can associate their GitHub account with their Facebook account by storing an authentication credential in the form of an account recovery token for their GitHub account with Facebook. - term: 복구 코드 description: GitHub 계정에 다시 액세스할 수 있는 코드입니다. diff --git a/translations/ko-KR/data/learning-tracks/actions.yml b/translations/ko-KR/data/learning-tracks/actions.yml index cac5e08917..3e7bb1a877 100644 --- a/translations/ko-KR/data/learning-tracks/actions.yml +++ b/translations/ko-KR/data/learning-tracks/actions.yml @@ -7,6 +7,7 @@ getting_started: - /actions/learn-github-actions/finding-and-customizing-actions - /actions/learn-github-actions/essential-features-of-github-actions - /actions/learn-github-actions/managing-complex-workflows + - /actions/learn-github-actions/reusing-workflows - /actions/learn-github-actions/security-hardening-for-github-actions featured_track: true continuous_integration: diff --git a/translations/ko-KR/data/release-notes/enterprise-server/2-20/15.yml b/translations/ko-KR/data/release-notes/enterprise-server/2-20/15.yml index 205a9bed6a..eb611e3aa6 100644 Binary files a/translations/ko-KR/data/release-notes/enterprise-server/2-20/15.yml and b/translations/ko-KR/data/release-notes/enterprise-server/2-20/15.yml differ diff --git a/translations/ko-KR/data/release-notes/enterprise-server/2-21/6.yml b/translations/ko-KR/data/release-notes/enterprise-server/2-21/6.yml index 98976d4fa2..f51e7b415f 100644 Binary files a/translations/ko-KR/data/release-notes/enterprise-server/2-21/6.yml and b/translations/ko-KR/data/release-notes/enterprise-server/2-21/6.yml differ diff --git a/translations/ko-KR/data/release-notes/enterprise-server/2-22/22.yml b/translations/ko-KR/data/release-notes/enterprise-server/2-22/22.yml new file mode 100644 index 0000000000..0bc20acf57 --- /dev/null +++ b/translations/ko-KR/data/release-notes/enterprise-server/2-22/22.yml @@ -0,0 +1,15 @@ +--- +date: '2021-09-24' +sections: + security_fixes: + - '**HIGH:** A path traversal vulnerability was identified in {% data variables.product.prodname_ghe_server %} that could be exploited when building a {% data variables.product.prodname_pages %} site. User-controlled configuration options used by {% data variables.product.prodname_pages %} were not sufficiently restricted and made it possible to read files on the {% data variables.product.prodname_ghe_server %} instance. To exploit this vulnerability, an attacker would need 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.1.8 and was fixed in 3.1.8, 3.0.16, and 2.22.22. This is the result of an incomplete fix for CVE-2021-22867. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned CVE-2021-22868. {% comment %} https://github.com/github/pages/pull/3359, https://github.com/github/pages/pull/3357 {% endcomment %}' + bugs: + - 'The {% data variables.product.prodname_github_connect %} configuration of the source instance was always restored to new instances even when the `--config` option for `ghe-restore` was not used. This would lead to a conflict with the {% data variables.product.prodname_github_connect %} connection and license synchronization if both the source and destination instances were online at the same time. {% comment %} https://github.com/github/github/pull/192247, https://github.com/github/github/pull/191951, https://github.com/github/enterprise2/pull/26870, https://github.com/github/backup-utils/pull/770, https://github.com/github/connected-enterprise/issues/208 {% endcomment %}' + - 'Fixes {% data variables.product.prodname_pages %} builds so they take into account the NO_PROXY setting of the appliance. This is relevant to appliances configured with an HTTP proxy only. {% comment %} https://github.com/github/github/pull/192380 {% endcomment %}' + known_issues: + - On a freshly set up {% data variables.product.prodname_ghe_server %} without any users, an attacker could create the first admin user. + - Custom firewall rules are removed during the upgrade process. + - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. + - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters. + - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_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. diff --git a/translations/ko-KR/data/release-notes/enterprise-server/3-0/16.yml b/translations/ko-KR/data/release-notes/enterprise-server/3-0/16.yml new file mode 100644 index 0000000000..c40eac2c61 --- /dev/null +++ b/translations/ko-KR/data/release-notes/enterprise-server/3-0/16.yml @@ -0,0 +1,18 @@ +--- +date: '2021-09-24' +sections: + security_fixes: + - '**HIGH:** A path traversal vulnerability was identified in {% data variables.product.prodname_ghe_server %} that could be exploited when building a {% data variables.product.prodname_pages %} site. User-controlled configuration options used by {% data variables.product.prodname_pages %} were not sufficiently restricted and made it possible to read files on the {% data variables.product.prodname_ghe_server %} instance. To exploit this vulnerability, an attacker would need 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.1.8 and was fixed in 3.1.8, 3.0.16, and 2.22.22. This is the result of an incomplete fix for CVE-2021-22867. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned CVE-2021-22868. {% comment %} https://github.com/github/pages/pull/3360, https://github.com/github/pages/pull/3357 {% endcomment %}' + - '**MEDIUM:** An improper access control vulnerability in {% data variables.product.prodname_ghe_server %} allowed a workflow job to execute in a self-hosted runner group it should not have had access to. This affects customers using self-hosted runner groups for access control. A repository with access to one enterprise runner group could access all of the enterprise runner groups within the organization because of improper authentication checks during the request. This could cause code to be run unintentionally by the incorrect runner group. This vulnerability affected {% data variables.product.prodname_ghe_server %} versions from 3.0.0 to 3.0.15 and 3.1.0 to 3.1.7 and was fixed in 3.0.16 and 3.1.8 releases. It has been assigned CVE-2021-22869. {% comment %} https://github.com/github/enterprise2/pull/27003 {% endcomment %}' + bugs: + - 'Resque worker counts were displayed incorrectly during maintenance mode. {% comment %} https://github.com/github/enterprise2/pull/26898, https://github.com/github/enterprise2/pull/26883 {% endcomment %}' + - 'Allocated memcached memory could be zero in clustering mode. {% comment %} https://github.com/github/enterprise2/pull/26927, https://github.com/github/enterprise2/pull/26832 {% endcomment %}' + - 'Fixes {% data variables.product.prodname_pages %} builds so they take into account the NO_PROXY setting of the appliance. This is relevant to appliances configured with an HTTP proxy only. (update 2021-09-30) {% comment %} https://github.com/github/pages/pull/3360 {% endcomment %}' + known_issues: + - On a freshly set up {% data variables.product.prodname_ghe_server %} without any users, an attacker could create the first admin user. + - Custom firewall rules are removed during the upgrade process. + - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. + - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters. + - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results. + - 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/ko-KR/data/release-notes/enterprise-server/3-1/8.yml b/translations/ko-KR/data/release-notes/enterprise-server/3-1/8.yml new file mode 100644 index 0000000000..77ecdaab2d --- /dev/null +++ b/translations/ko-KR/data/release-notes/enterprise-server/3-1/8.yml @@ -0,0 +1,20 @@ +--- +date: '2021-09-24' +sections: + security_fixes: + - '**HIGH:** A path traversal vulnerability was identified in {% data variables.product.prodname_ghe_server %} that could be exploited when building a {% data variables.product.prodname_pages %} site. User-controlled configuration options used by {% data variables.product.prodname_pages %} were not sufficiently restricted and made it possible to read files on the {% data variables.product.prodname_ghe_server %} instance. To exploit this vulnerability, an attacker would need 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.1.8 and was fixed in 3.1.8, 3.0.16, and 2.22.22. This is the result of an incomplete fix for CVE-2021-22867. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned CVE-2021-22868. {% comment %} https://github.com/github/pages/pull/3361, https://github.com/github/pages/pull/3357 {% endcomment %}' + - '**MEDIUM:** An improper access control vulnerability in {% data variables.product.prodname_ghe_server %} allowed a workflow job to execute in a self-hosted runner group it should not have had access to. This affects customers using self-hosted runner groups for access control. A repository with access to one enterprise runner group could access all of the enterprise runner groups within the organization because of improper authentication checks during the request. This could cause code to be run unintentionally by the incorrect runner group. This vulnerability affected {% data variables.product.prodname_ghe_server %} versions from 3.0.0 to 3.0.15 and 3.1.0 to 3.1.7 and was fixed in 3.0.16 and 3.1.8 releases. It has been assigned CVE-2021-22869. {% comment %} https://github.com/github/enterprise2/pull/27013 {% endcomment %}' + bugs: + - 'Resque worker counts were displayed incorrectly during maintenance mode. {% comment %} https://github.com/github/enterprise2/pull/26899, https://github.com/github/enterprise2/pull/26883 {% endcomment %}' + - 'Allocated memcached memory could be zero in clustering mode. {% comment %} https://github.com/github/enterprise2/pull/26928, https://github.com/github/enterprise2/pull/26832 {% endcomment %}' + - 'Non-empty binary files displayed an incorrect file type and size on the pull request "Files" tab. {% comment %} https://github.com/github/github/pull/192810, https://github.com/github/github/pull/172284, https://github.com/github/coding/issues/694 {% endcomment %}' + - 'Fixes {% data variables.product.prodname_pages %} builds so they take into account the NO_PROXY setting of the appliance. This is relevant to appliances configured with an HTTP proxy only. (update 2021-09-30) {% comment %} https://github.com/github/pages/pull/3360 {% endcomment %}' + known_issues: + - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. + - On a freshly set up {% data variables.product.prodname_ghe_server %} without any users, an attacker could create the first admin user. + - Custom firewall rules are removed during the upgrade process. + - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. + - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters. + - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results. + - If {% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_server %}, teardown of a replica node with `ghe-repl-teardown` will succeed, but may return `ERROR:Running migrations`. + - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. diff --git a/translations/ko-KR/data/release-notes/enterprise-server/3-2/0-rc1.yml b/translations/ko-KR/data/release-notes/enterprise-server/3-2/0-rc1.yml index 430e555020..e186c81135 100644 --- a/translations/ko-KR/data/release-notes/enterprise-server/3-2/0-rc1.yml +++ b/translations/ko-KR/data/release-notes/enterprise-server/3-2/0-rc1.yml @@ -1,7 +1,7 @@ --- date: '2021-09-09' release_candidate: true -deprecated: false +deprecated: true intro: 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. sections: features: diff --git a/translations/ko-KR/data/release-notes/enterprise-server/3-2/0.yml b/translations/ko-KR/data/release-notes/enterprise-server/3-2/0.yml new file mode 100644 index 0000000000..dab08920a6 --- /dev/null +++ b/translations/ko-KR/data/release-notes/enterprise-server/3-2/0.yml @@ -0,0 +1,221 @@ +--- +date: '2021-09-28' +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: Custom patterns for secret scanning + notes: + - | + {% data variables.product.prodname_GH_advanced_security %} customers can now specify custom patterns for secret scanning. When a new pattern is specified, secret scanning searches a repository's entire Git history for the pattern, as well as any new commits. + + User defined patterns are in beta for {% data variables.product.prodname_ghe_server %} 3.2. They can be defined at the repository, organization, and enterprise levels. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." + - + heading: Security overview for Advanced Security (beta) + notes: + - | + {% data variables.product.prodname_GH_advanced_security %} customers now have an organization-level view of the application security risks detected by {% data variables.product.prodname_code_scanning %}, {% data variables.product.prodname_dependabot %}, and {% data variables.product.prodname_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 {% data variables.product.prodname_secret_scanning %} alerts at the organization level. Similar views for {% data variables.product.prodname_dependabot %} and {% data variables.product.prodname_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 review (beta) + notes: + - | + {% data variables.product.prodname_GH_advanced_security %} customers can now see a rich diff of the dependencies changed in a pull request. 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 these dependencies. 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)." + - + heading: GitHub Actions environments + notes: + - | + Environments, environment protection rules, and environment secrets are now generally available for {% data variables.product.prodname_actions %} on {% data variables.product.product_name %}. For more information, see "[Environments](/actions/reference/environments)." + + ![Environment protection rules](/assets/images/enterprise/3.2/release-notes/actions-environments.png) + - + heading: SSH authentication with security keys + notes: + - | + SSH authentication using a FIDO2 security key is now supported when you add a `sk-ecdsa-sha2-nistp256@openssh.com` or `sk-ssh-ed25519@openssh.com` SSH key to your account. SSH security keys store secret key material on a separate hardware device that requires verification, such as a tap, to operate. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)." + - + heading: 'Dark and dark dimmed themes' + notes: + - | + Dark and dark dimmed themes are now available for the web UI. {% data variables.product.product_name %} will match your system preferences when you haven't set theme preferences in {% data variables.product.product_name %}. You can also choose which themes are active during the day and night. For more information, see "[Managing your theme settings](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)." + + ![Dark and dark dimmed themes](https://user-images.githubusercontent.com/33528647/114629560-d2231f80-9c86-11eb-9bde-cc301a97040d.gif) + - + heading: 'Approving unverified domains for email notifications' + notes: + - 'Domains that are not able to be verified can now be approved for email notification routing. Enterprise and organization owners will be able to approve domains and immediately augment their email notification restriction policy, allowing notifications to be sent to collaborators, consultants, acquisitions, or other partners. For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#about-approval-of-domains)" and "[Restricting email notifications for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise#restricting-email-notifications-for-your-enterprise-account)."' + - + heading: 'Git Credential Manager (GCM) secure credential storage and multi-factor authentication support' + notes: + - | + Git Credential Manager (GCM) Core versions 2.0.452 and later now provide security-hardened credential storage and multi-factor authentication support for {% data variables.product.product_name %}. + + GCM Core with support for {% data variables.product.product_name %} is included with [Git for Windows](https://gitforwindows.org) versions 2.32 and later. GCM Core is not included with Git for macOS or Linux, but can be installed separately. For more information, see the [latest release](https://github.com/microsoft/Git-Credential-Manager-Core/releases/) and [installation instructions](https://github.com/microsoft/Git-Credential-Manager-Core/releases/) in the `microsoft/Git-Credential-Manager-Core` repository. + changes: + - + heading: Administration Changes + notes: + - A 'User Agent Referrer Policy' setting has been added to the enterprise settings. This allows an admin to set a stricter `Referrer-Policy` to hide the hostname of a {% data variables.product.prodname_ghe_server %} installation from external sites. The setting is disabled by default and is tracked by audit log events for staff and enterprise owners when enabled or disabled. For more information, see "[Configuring Referrer Policy for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)." + - The MySQL health check was changed to use `mysqladmin ping` instead of TCP checks, which removes some unnecessary noise in the MySQL error log. Also, Orchestrator failover checks were improved to prevent unnecessary MySQL failovers when applying cluster config changes. + - 'The Resque service, which supports background job processing, has been replaced with Aqueduct Lite. This change makes the job system easier to manage and should not affect the user experience. For the new administration and debugging commands for Aqueduct, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-aqueduct)."' + - + heading: Token Changes + notes: + - | + The format of authentication tokens for {% data variables.product.product_name %} has changed. The change affects the format of personal access tokens and access tokens for {% data variables.product.prodname_oauth_apps %}, as well as user-to-server, server-to-server, and refresh tokens for {% data variables.product.prodname_github_apps %}. + + The different token types now have unique identifiable prefixes, which allows for secret scanning to detect the tokens so that you can mitigate the impact of someone accidentally committing a token to a repository. {% data variables.product.company_short %} recommends updating existing tokens as soon as possible. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github#githubs-token-formats)" and "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)." + - + heading: 'Repositories changes' + notes: + - Repositories on user profiles and organization profiles now support sorting by star count. + - When viewing the commit history of a single file, you can now click {% octicon "file-code" aria-label="The code icon" %} to view that file at the selected point in history. + - When a submodule is defined with a relative path in {% data variables.product.product_location %}, the submodule is now clickable in the web UI. Clicking the submodule in the web UI will take you to the linked repository. Previously, only submodules with absolute URLs were clickable. This is supported for relative paths for repositories with the same owner that follow the pattern ../REPOSITORY or relative paths for repositories with a different owner that follow the pattern ../OWNER/REPOSITORY. For more information about working with submodules, see [Working with submodules](https://github.blog/2016-02-01-working-with-submodules/) on {% data variables.product.prodname_blog %}. + - 'The web UI can now be used to synchronize an out-of-date branch of a fork with the fork''s upstream branch. If there are no merge conflicts between the branches, the branch is updated either by fast-forwarding or by merging from upstream. If there are conflicts, you will be prompted to create a pull request to resolve the conflicts. For more information, see "[Syncing a fork](/github/collaborating-with-pull-requests/working-with-forks/syncing-a-fork#syncing-a-fork-from-the-web-ui)."' + - + heading: 'Markdown changes' + notes: + - 'The markdown editor used when creating or editing a release in a repository now has a text-editing toolbar. For more information, see "[Managing releases in a repository](/github/administering-a-repository/releasing-projects-on-github/managing-releases-in-a-repository#creating-a-release)."' + - Uploading video files is now supported everywhere you write Markdown on {% data variables.product.product_name %}. Share demos, reproduction steps, and more in your issue and pull request comments, as well as in Markdown files within repositories, such as READMEs. For more information, see "[Attaching files](/github/writing-on-github/working-with-advanced-formatting/attaching-files)." + - Markdown files will now automatically generate a table of contents in the header when there are 2 or more headings. The table of contents is interactive and links to the selected section. All 6 Markdown heading levels are supported. + - 'There is a new keyboard shortcut, `cmd+e` on macOS or `ctrl+e` on Windows, to insert codeblocks in Markdown files, issues, pull requests, and comments.' + - 'Appending `?plain=1` to the URL for any Markdown file will now display the file without rendering and with line numbers. The plain view can be used to link other users to specific lines. For example, appending `?plain=1#L52` will highlight line 52 of a plain text Markdown file. For more information, "[Creating a permanent link to a code snippet](/github/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet#linking-to-markdown)."' + - + heading: 'Issues and pull requests changes' + notes: + - With the [latest version of Octicons](https://github.com/primer/octicons/releases), the states of issues and pull requests are now more visually distinct so you can scan their status more easily. For more information, see [{% data variables.product.prodname_blog %}](https://github.blog/changelog/2021-06-08-new-issue-and-pull-request-state-icons/). + - 'A new "Require conversation resolution before merging" branch protection rule and "Conversations" menu is now available. Easily discover your pull request comments from the "Files changed" tab, and require that all your pull request conversations are resolved before merging. For more information, see "[About pull request reviews](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews#discovering-and-navigating-conversations)" and "[About protected branches](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-conversation-resolution-before-merging)."' + - To prevent the merge of unexpected changes after auto-merge is enabled for a pull request, auto-merge is now disabled automatically when new changes are pushed by a user without write access to the repository. Users without write access can still update the pull request with changes from the base branch when auto-merge is enabled. To prevent a malicious user from using a merge conflict to introduce unexpected changes to the pull request, auto-merge for the pull request is disabled if the update causes a merge conflict. For more information about auto-merge, see "[Automatically merging a pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." + - 'People with maintain permissions 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 permissions 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. + - When a review is requested from a team of more than 100 people, developers are now shown a confirmation dialog box in order to prevent unnecessary notifications for large teams. + - Back-tick `code blocks` are now supported in issue titles, pull request titles, and in any place issue and pull request titles are referenced in {% data variables.product.prodname_ghe_server %}. + - 'Events for pull requests and pull request reviews are now included in the audit log for both [enterprises](/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise) and [organizations](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization). These events help admins better monitor pull request activity and help ensure security and compliance requirements are being met. Events can be viewed from the web UI, exported as CSV or JSON, or accessed via REST API. You can also search the audit log for specific pull request events. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#pull_request-category-actions)."' + - + heading: 'Branches changes' + notes: + - | + The default branch name for new repositories is now `main`. Existing repositories are not impacted by this change. If users, organization owners, or enterprise owners have previously specified a default branch for new repositories, they are also not impacted. + + If you want to set a different default branch name, you can do so in the [user](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories), [organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization), or [enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name) settings. + - | + Branches, including the default branch, can now be renamed using the the {% data variables.product.product_name %} web UI. When a branch is renamed, any open pull requests and draft releases targeting the renamed branch will be retargeted automatically, and branch protection rules that explicitly reference the renamed branch will be updated. + + Admin permissions are required to rename the default branch, but write permissions are sufficient to rename other branches. + + To help make the change as seamless as possible for users: + + * A notice is shown to contributors, maintainers, and admins on the repository homepage with instructions for updating their local repository. + * Web requests to the old branch will be redirected. + * A "moved permanently" HTTP response will be returned to REST API calls. + * An informational message is displayed to Git command line users that push to the old branch. + + For more information, see "[Renaming a branch](/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch)." + - + heading: 'GitHub Actions changes' + notes: + - '{% data variables.product.prodname_actions %} now lets you control the permissions granted to the `GITHUB_TOKEN` secret. The `GITHUB_TOKEN` is an automatically-generated secret that lets you make authenticated calls to the API for {% data variables.product.product_name %} in your workflow runs. {% data variables.product.prodname_actions %} generates a new token for each job and expires the token when a job completes. The token usually has `write` permissions to a number of [API endpoints](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token), except in the case of pull requests from forks, which are always `read`. These new settings allow you to follow a principle of least privilege in your workflows. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token)."' + - '{% data variables.product.prodname_cli %} 1.9 and later allows you to work with {% data variables.product.prodname_actions %} in your terminal. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-04-15-github-cli-1-9-enables-you-to-work-with-github-actions-from-your-terminal/).' + - 'The audit log now includes events associated with {% data variables.product.prodname_actions %} workflow runs. This data provides administrators with a greatly expanded data set for security and compliance audits. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#workflows-category-actions)."' + - '{% data variables.product.prodname_ghe_server %} 3.2 contains performance improvements for job concurrency with {% data variables.product.prodname_actions %}. For more information on the new performance targets on 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)."' + - + heading: 'GitHub Packages changes' + notes: + - Any package or package version for {% data variables.product.prodname_registry %} can now be deleted from {% data variables.product.product_name %}'s web UI. You can also undo the deletion of any package or package version within 30 days. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)". + - + heading: 'Dependabot and Dependency graph changes' + notes: + - 'The dependency graph can now be enabled using the Management Console, rather than needing to run a command in the administrative shell. For more information, see "[Enabling alerts for vulnerable dependencies {% data variables.product.prodname_ghe_server %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server#enabling-the-dependency-graph-and-dependabot-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."' + - Notifications for multiple {% data variables.product.prodname_dependabot_alerts %} are now grouped together if they're discovered at the same time. This significantly reduces the volume of {% data variables.product.prodname_dependabot %} alert notifications that users receive. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-03-18-grouped-dependabot-alert-notifications/). + - 'Dependency graph and {% data variables.product.prodname_dependabot_alerts %} now support Go modules. {% data variables.product.prodname_ghe_server %} analyzes a repository''s `go.mod` files to understand the repository’s dependencies. Along with security advisories, the dependency graph provides the information needed to alert developers to vulnerable dependencies. For more information about enabling the dependency graph on private repositories, see "[Securing your repository](/code-security/getting-started/securing-your-repository#managing-the-dependency-graph)."' + - The default notification settings for security alerts have changed. Previously, if you had permission to view security alerts in a repository, you would receive notifications for that repository as long as your settings allowed for security alert notifications. Now, you must opt in to security alert notifications by watching the repository. You will be notified if you select `All Activity` or configure `Custom` to include `Security alerts`. All existing repositories will be automatically migrated to these new settings and you will continue to receive notifications; however, any new repositories will require opting-in by watching the repository. 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)" and "[Managing alerts from secret scanning](/code-security/secret-security/managing-alerts-from-secret-scanning)." + - + heading: 'Code scanning and secret scanning changes' + notes: + - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} now generates diagnostic information for all supported languages. This helps check the state of the created database to understand the status and quality of performed analysis. The diagnostic information is available starting in [version 2.5.6](https://github.com/github/codeql-cli-binaries/releases) of the [{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/). You can see the detailed diagnostic information in the {% data variables.product.prodname_actions %} logs for {% data variables.product.prodname_codeql %}. For more information, see "[Viewing code scanning logs](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs)."' + - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql_cli %} now supports analyzing several languages during a single build. This makes it easier to run code analysis to use CI/CD systems other than {% data variables.product.prodname_actions %}. The new mode of the `codeql database create` command is available starting [version 2.5.6](https://github.com/github/codeql-cli-binaries/releases) of the [{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/). For more information about setting this up, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-cli-in-your-ci-system)."' + - '{% data variables.product.prodname_code_scanning_capc %} alerts from all enabled tools are now shown in one consolidated list, so that you can easily prioritize across all alerts. You can view alerts from a specific tool by using the "Tool" filter, and the "Rule" and "Tag" filters will dynamically update based on your "Tool" selection.' + - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} now includes beta support for analyzing C++20 code. This is only available when building codebases with GCC on Linux. C++20 modules are not supported yet.' + - 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 for several languages ([C++](https://github.com/github/codeql/tree/main/cpp), [JavaScript](https://github.com/github/codeql/tree/main/javascript), [Python](https://github.com/github/codeql/tree/main/python), and [Java](https://github.com/github/codeql/tree/main/java)). As a result, {% data variables.product.prodname_codeql %} can now detect even more potential sources of untrusted user data, review the steps through which that data flows, and identify potentially dangerous sinks in which this data could end up. This results in an overall improvement of the quality of the {% data variables.product.prodname_code_scanning %} alerts. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-07-01-codeql-code-scanning-now-recognizes-more-sources-and-uses-of-untrusted-user-data/). + - | + {% data variables.product.prodname_code_scanning_capc %} now shows `security-severity` levels for CodeQL security alerts. You can configure which `security-severity` levels will cause a check failure for a pull request. The severity level of security alerts can be `critical`, `high`, `medium`, or `low`. By default, any {% data variables.product.prodname_code_scanning %} alerts with a `security-severity` of `critical` or `high` will cause a pull request check failure. + + Additionally, you can now also configure which severity levels will cause a pull request check to fail for non-security alerts. You can configure this behavior at the repository level, and define whether alerts with the severity `error`, `warning`, or `note` will cause a pull request check to fail. By default, non-security {% data variables.product.prodname_code_scanning %} alerts with a severity of `error` will cause a pull request check failure. + + For more information see "[Defining which alert severity levels cause pull request check failure](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)." + + ![List of code scanning alerts with security levels](/assets/images/enterprise/3.2/release-notes/code-scanning-alerts.png) + - | + Improvements to the branch filter for {% data variables.product.prodname_code_scanning %} alerts make it clearer which {% data variables.product.prodname_code_scanning %} alerts are being displayed on the alerts page. By default, {% data variables.product.prodname_code_scanning %} alerts are filtered to show alerts for the default branch of the repository only. You can use the branch filter to display the alerts on any of the non-default branches. Any branch filter that has been applied is shown in the search bar. + + The search syntax has also been simplified to `branch:`. This syntax can be used multiple times in the search bar to filter on multiple branches. The previous syntax, `ref:refs/heads/`, is still supported, so any saved URLs will continue to work. + - | + Free text search is now available for code scanning alerts. You can search code scanning results to quickly find specific alerts without having to know exact search terms. The search is applied across the alert's name, description, and help text. The syntax is: + + - A single word returns all matches. + - Multiple search words returns matches to either word. + - Words in double quotes returns exact matches. + - The keyword 'AND' returns matches to multiple words. + - '{% data variables.product.prodname_secret_scanning_caps %} added patterns for 23 new service providers. For the updated list of supported secrets, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning)."' + - + heading: API Changes + notes: + - 'Pagination support has been added to the Repositories REST API''s "compare two commits" endpoint, which returns a list of commits reachable from one commit or branch, but unreachable from another. The API can also now return the results for comparisons over 250 commits. For more information, see the "[Repositories](/rest/reference/repos#compare-two-commits)" REST API documentation and "[Traversing with pagination](/rest/guides/traversing-with-pagination)."' + - 'The REST API can now be used to programmatically resend or check the status of webhooks. For more information, see "[Repositories](/rest/reference/repos#webhooks)," "[Organizations](/rest/reference/orgs#webhooks)," and "[Apps](/rest/reference/apps#webhooks)" in the REST API documentation.' + - | + Improvements have been made to the code scanning and {% data variables.product.prodname_GH_advanced_security %} APIs: + + - The code scanning API now returns the CodeQL query version used for an analysis. This can be used to reproduce results or confirm that an analysis used the latest query. For more information, see "[Code scanning](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository)" in the REST API documentation. + - Admin users can now use the REST API to enable or disable {% data variables.product.prodname_GH_advanced_security %} for repositories, using the `security_and_analysis` object on `repos/{org}/{repo}`. In addition, admin users can check whether {% data variables.product.prodname_advanced_security %} is currently enabled for a repository by using a `GET /repos/{owner}/{repo}` request. These changes help you manage {% data variables.product.prodname_advanced_security %} repository access at scale. For more information, see "[Repositories](/rest/reference/repos#update-a-repository)" in the REST API documentation. + #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 %} 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. + deprecations: + - + heading: Deprecation of GitHub Enterprise Server 2.21 + notes: + - '**{% data variables.product.prodname_ghe_server %} 2.21 was discontinued on June 6, 2021**. That 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.2/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' + - + heading: Deprecation of GitHub Enterprise Server 2.22 + notes: + - '**{% data variables.product.prodname_ghe_server %} 2.22 will be discontinued on September 23, 2021**. That 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.2/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' + - + heading: Deprecation of XenServer Hypervisor support + notes: + - Beginning in {% data variables.product.prodname_ghe_server %} 3.1, we will begin discontinuing support for Xen Hypervisor. The complete deprecation is scheduled for {% data variables.product.prodname_ghe_server %} 3.3, following the standard one year deprecation window. Please contact [GitHub Support](https://enterprise.githubsupport.com/hc/en-us/signin) with questions or concerns. + - + heading: Removal of Legacy GitHub Services + notes: + - '{% data variables.product.prodname_ghe_server %} 3.2 removes unused GitHub Service database records. More information is available in the [deprecation announcement post](https://developer.github.com/changes/2018-04-25-github-services-deprecation/).' + - + heading: Deprecation of OAuth Application API endpoints and API authentication via query parameters + notes: + - | + To prevent accidental logging or exposure of `access_tokens`, we discourage the use of OAuth Application API endpoints and the use of API auth via query params. Visit the following posts to see the proposed replacements: + + * [Replacement OAuth Application API endpoints](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#changes-to-make) + * [Replacement auth via headers instead of query param](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make) + + These endpoints and auth route are planned to be removed from {% data variables.product.prodname_ghe_server %} in {% data variables.product.prodname_ghe_server %} 3.4. + - + heading: Removal of legacy GitHub App webhook events and endpoints + notes: + - | + Two legacy GitHub Apps-related webhook events have been removed: `integration_installation` and `integration_installation_repositories`. You should instead be listening to the `installation` and `installation_repositories` events. + - | + The following REST API endpoint has been removed: `POST /installations/{installation_id}/access_tokens`. You should instead be using the namespaced equivalent `POST /app/installations/{installation_id}/access_tokens`. + backups: + - '{% data variables.product.prodname_ghe_server %} 3.2 requires at least [GitHub Enterprise Backup Utilities 3.2.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/enterprise-server@3.2/admin/configuration/configuring-backups-on-your-appliance).' diff --git a/translations/ko-KR/data/reusables/actions/about-environments.md b/translations/ko-KR/data/reusables/actions/about-environments.md new file mode 100644 index 0000000000..ab9cfa899f --- /dev/null +++ b/translations/ko-KR/data/reusables/actions/about-environments.md @@ -0,0 +1 @@ +Environments are used to describe a general deployment target like `production`, `staging`, or `development`. When a {% data variables.product.prodname_actions %} workflow deploys to an environment, the environment is displayed on the main page of the repository. You can use environments to require approval for a job to proceed, restrict which branches can trigger a workflow, or limit access to secrets. For more information about creating environments, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/actions/actions-group-concurrency.md b/translations/ko-KR/data/reusables/actions/actions-group-concurrency.md index acd4fab5e5..85aece27b2 100644 --- a/translations/ko-KR/data/reusables/actions/actions-group-concurrency.md +++ b/translations/ko-KR/data/reusables/actions/actions-group-concurrency.md @@ -1,6 +1,6 @@ When a concurrent job or workflow is queued, if another job or workflow using the same concurrency group in the repository is in progress, the queued job or workflow will be `pending`. Any previously pending job or workflow in the concurrency group will be canceled. To also cancel any currently running job or workflow in the same concurrency group, specify `cancel-in-progress: true`. -### Examples: Using concurrency and the default behavior +## Examples: Using concurrency and the default behavior {% raw %} ```yaml @@ -14,7 +14,7 @@ concurrency: ci-${{ github.ref }} ``` {% endraw %} -### Example: Using concurrency to cancel any in-progress job or run +## Example: Using concurrency to cancel any in-progress job or run {% raw %} ```yaml diff --git a/translations/ko-KR/data/reusables/actions/ae-hosted-runners-beta.md b/translations/ko-KR/data/reusables/actions/ae-hosted-runners-beta.md new file mode 100644 index 0000000000..804f22a849 --- /dev/null +++ b/translations/ko-KR/data/reusables/actions/ae-hosted-runners-beta.md @@ -0,0 +1,7 @@ +{% ifversion ghae %} +{% note %} + +**Note:** {% data variables.actions.hosted_runner %}s are currently in beta and subject to change. + +{% endnote %} +{% endif %} diff --git a/translations/ko-KR/data/reusables/actions/ae-self-hosted-runners-notice.md b/translations/ko-KR/data/reusables/actions/ae-self-hosted-runners-notice.md index cceda715dd..0dec49e4f5 100644 --- a/translations/ko-KR/data/reusables/actions/ae-self-hosted-runners-notice.md +++ b/translations/ko-KR/data/reusables/actions/ae-self-hosted-runners-notice.md @@ -1,9 +1,19 @@ {% ifversion ghae %} + {% warning %} -** Warning:** Self-hosted runners are currently disabled for {% data variables.product.prodname_ghe_managed %}. This is because {% data variables.product.prodname_ghe_managed %} offers guarantees for security boundaries which are incompatible with how self-hosted runners work. However, if you do need to use self-hosted runners with {% data variables.product.prodname_ghe_managed %} and understand the security implications, you can contact {% data variables.product.prodname_dotcom %} support for a security exception that will enable self-hosted runners. +{% ifversion ghae-next %} + +**Warning:** Self-hosted runners are enabled by default for {% data variables.product.prodname_ghe_managed %}. Self-hosted runners are long-lived, and any compromise to the host machine could leak secrets or credentials or enable other attacks. If you'd like to disable self-hosted runners for your enterprise, you can contact {% data variables.product.prodname_dotcom %} support. For more information about the risks of using self-hosted runners, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/security-hardening-for-github-actions#potential-impact-of-a-compromised-runner)." + +{% elsif ghae %} + +**Warning:** Self-hosted runners are currently disabled for {% data variables.product.prodname_ghe_managed %}. This is because {% data variables.product.prodname_ghe_managed %} offers guarantees for security boundaries which are incompatible with how self-hosted runners work. However, if you do need to use self-hosted runners with {% data variables.product.prodname_ghe_managed %} and understand the security implications, you can contact {% data variables.product.prodname_dotcom %} support for a security exception that will enable self-hosted runners. If you don't need self-hosted runners, then you can use {% data variables.actions.hosted_runner %}s to run your workflows. For more information, see "[About {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/about-ae-hosted-runners)." -{% endwarning %} +{% endif %} + +{% endwarning %} + {% endif %} diff --git a/translations/ko-KR/data/reusables/actions/allow-specific-actions-intro.md b/translations/ko-KR/data/reusables/actions/allow-specific-actions-intro.md index ea63a6c71c..1d10b77986 100644 --- a/translations/ko-KR/data/reusables/actions/allow-specific-actions-intro.md +++ b/translations/ko-KR/data/reusables/actions/allow-specific-actions-intro.md @@ -1,7 +1,7 @@ When you choose **Allow select actions**, local actions are allowed, and there are additional options for allowing other specific actions: -- **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` organization. For more information, see the [`actions`](https://github.com/actions) and [`github`](https://github.com/github) organizations.{% ifversion fpt or ghes > 3.0 %} -- **Allow Marketplace actions by verified creators:** {% ifversion ghes > 3.0 %}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 > 3.0 or ghae-issue-5094 %} +- **Allow Marketplace actions by verified creators:** {% ifversion ghes > 3.0 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 specified actions:** You can restrict workflows to use actions in specific organizations and repositories. To restrict access to specific tags or commit SHAs of an action, use the same `/@` syntax used in the workflow to select the action. For example, `actions/javascript-action@v1.0.1` to select a tag or `actions/javascript-action@172239021f7ba04fe7327647b213799853a9eb89` to select a SHA. For more information, see "[Finding and customizing actions](/actions/learn-github-actions/finding-and-customizing-actions#using-release-management-for-your-custom-actions)." diff --git a/translations/ko-KR/data/reusables/actions/autoscaling-parameters.md b/translations/ko-KR/data/reusables/actions/autoscaling-parameters.md new file mode 100644 index 0000000000..d9c4342b29 --- /dev/null +++ b/translations/ko-KR/data/reusables/actions/autoscaling-parameters.md @@ -0,0 +1,3 @@ +- Optionally, autoscaling parameters for each pool. + - Minimum number of idle runners for the pool + - Active timeout: The number of minutes that a runner should remain active in the pool before the pool is reduced to the idle count diff --git a/translations/ko-KR/data/reusables/actions/cd-templates-actions.md b/translations/ko-KR/data/reusables/actions/cd-templates-actions.md new file mode 100644 index 0000000000..c6eeec90db --- /dev/null +++ b/translations/ko-KR/data/reusables/actions/cd-templates-actions.md @@ -0,0 +1,3 @@ +{% data variables.product.product_name %} offers CD workflow templates for several popular services, such as Azure Web App. To learn how to get started using a workflow template, see "[Using workflow templates](/actions/learn-github-actions/using-workflow-templates)" or [browse the full list of deployment workflow templates](https://github.com/actions/starter-workflows/tree/main/deployments). You can also check out our more detailed guides for specific deployment workflows, such as "[Deploying to Azure App Service](/actions/deployment/deploying-to-azure-app-service)." + +Many service providers also offer actions on {% data variables.product.prodname_marketplace %} for deploying to their service. For the full list, see [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?category=deployment&type=actions). \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/actions/delete-env-key.md b/translations/ko-KR/data/reusables/actions/delete-env-key.md new file mode 100644 index 0000000000..380ebe5653 --- /dev/null +++ b/translations/ko-KR/data/reusables/actions/delete-env-key.md @@ -0,0 +1 @@ +If you configured a deployment environment, change the value of `environment` to be the name of your environment. If you did not configure an environment{% ifversion fpt %} or if your workflow is in a private repository and you do not use {% data variables.product.prodname_ghe_cloud %}{% endif %}, delete the `environment` key. \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/actions/environment-deployment-event.md b/translations/ko-KR/data/reusables/actions/environment-deployment-event.md new file mode 100644 index 0000000000..1a014fbfc6 --- /dev/null +++ b/translations/ko-KR/data/reusables/actions/environment-deployment-event.md @@ -0,0 +1 @@ +When a workflow job that references an environment runs, it creates a deployment object with the `environment` property set to the name of your environment. As the workflow progresses, it also creates deployment status objects with the `environment` property set to the name of your environment, the `environment_url` property set to the URL for environment (if specified in the workflow), and the `state` property set to the status of the job. \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/actions/environment-example.md b/translations/ko-KR/data/reusables/actions/environment-example.md new file mode 100644 index 0000000000..95ed6bc816 --- /dev/null +++ b/translations/ko-KR/data/reusables/actions/environment-example.md @@ -0,0 +1,45 @@ +You can specify an environment for each job in your workflow. To do so, add a `jobs..environment` key followed by the name of the environment. + +For example, this workflow will use an environment called `production`. + +```yaml +name: Deployment + +on: + push: + branches: + - main + +jobs: + deployment: + runs-on: ubuntu-latest + environment: production + steps: + - name: deploy + # ...deployment-specific steps +``` + +When the above workflow runs, the `deployment` job will be subject to any rules configured for the `production` environment. For example, if the environment requires reviewers, the job will pause until one of the reviewers approves the job. + +You can also specify a URL for the environment. The specified URL will appear on the deployments page for the repository (accessed by clicking **Environments** on the home page of your repository) and in the visualization graph for the workflow run. If a pull request triggered the workflow, the URL is also displayed as a **View deployment** button in the pull request timeline. + +```yaml +name: Deployment + +on: + push: + branches: + - main + +jobs: + deployment: + runs-on: ubuntu-latest + environment: + name: production + url: https://github.com + steps: + - name: deploy + # ...deployment-specific steps +``` + +![Workflow graph with URL](/assets/images/help/images/deploy-graph.png) \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/actions/reusable-workflow-artifacts.md b/translations/ko-KR/data/reusables/actions/reusable-workflow-artifacts.md new file mode 100644 index 0000000000..4f5210333f --- /dev/null +++ b/translations/ko-KR/data/reusables/actions/reusable-workflow-artifacts.md @@ -0,0 +1,3 @@ +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +All actions and workflows called within a run have write access to that run's artifacts. +{% endif %} \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/actions/reusable-workflows.md b/translations/ko-KR/data/reusables/actions/reusable-workflows.md new file mode 100644 index 0000000000..377f69ce32 --- /dev/null +++ b/translations/ko-KR/data/reusables/actions/reusable-workflows.md @@ -0,0 +1,5 @@ +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## Reusing workflows + +You can call one workflow from within another workflow. This allows you to reuse workflows, avoiding duplication and making your workflows easier to maintain. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." +{% endif %} \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/actions/runner-name-description.md b/translations/ko-KR/data/reusables/actions/runner-name-description.md new file mode 100644 index 0000000000..c3955e46ec --- /dev/null +++ b/translations/ko-KR/data/reusables/actions/runner-name-description.md @@ -0,0 +1 @@ +The name of the runner executing the job. diff --git a/translations/ko-KR/data/reusables/actions/uses-keyword-example.md b/translations/ko-KR/data/reusables/actions/uses-keyword-example.md new file mode 100644 index 0000000000..fac21c8a9f --- /dev/null +++ b/translations/ko-KR/data/reusables/actions/uses-keyword-example.md @@ -0,0 +1,7 @@ +```yaml +jobs: + call-workflow-1: + uses: octo-org/this-repo/.github/workflows/workflow-1.yml@172239021f7ba04fe7327647b213799853a9eb89 + call-workflow-2: + uses: octo-org/another-repo/.github/workflows/workflow-2.yml@v1 +``` \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/actions/workflow-organization-templates.md b/translations/ko-KR/data/reusables/actions/workflow-organization-templates.md new file mode 100644 index 0000000000..3ea3e19383 --- /dev/null +++ b/translations/ko-KR/data/reusables/actions/workflow-organization-templates.md @@ -0,0 +1 @@ +Workflow templates allow everyone in your organization who has permission to create workflows to do so more quickly and easily. When you create a new workflow, you can choose a template and some or all of the work of writing the workflow will be done for you. You can use workflow templates as a starting place to build your custom workflow or use them as-is. This not only saves time, it promotes consistency and best practice across your organization. \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/actions/workflow-run-approve-public-fork.md b/translations/ko-KR/data/reusables/actions/workflow-run-approve-public-fork.md index 1eeb41311a..1873b96f85 100644 --- a/translations/ko-KR/data/reusables/actions/workflow-run-approve-public-fork.md +++ b/translations/ko-KR/data/reusables/actions/workflow-run-approve-public-fork.md @@ -1,3 +1,9 @@ Anyone can fork a public repository, and then submit a pull request that proposes changes to the repository's {% data variables.product.prodname_actions %} workflows. Although workflows from forks do not have access to sensitive data such as secrets, they can be an annoyance for maintainers if they are modified for abusive purposes. To help prevent this, workflows on pull requests to public repositories from some outside contributors will not run automatically, and might need to be approved first. By default, all first-time contributors require approval to run workflows. + +{% note %} + +**Note:** Workflows triggered by `pull_request_target` events are run in the context of the base branch. Since the base branch is considered trusted, workflows triggered by these events will always run, regardless of approval settings. + +{% endnote %} \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/apps/oauth-auth-vary-response.md b/translations/ko-KR/data/reusables/apps/oauth-auth-vary-response.md new file mode 100644 index 0000000000..b76fef614b --- /dev/null +++ b/translations/ko-KR/data/reusables/apps/oauth-auth-vary-response.md @@ -0,0 +1 @@ +You can also receive the response in different formats if you provide the format in the `Accept` header. For example, `Accept: application/json` or `Accept: application/xml`: diff --git a/translations/ko-KR/data/reusables/code-scanning/upload-sarif-alert-limit.md b/translations/ko-KR/data/reusables/code-scanning/upload-sarif-alert-limit.md index 23aafdc414..2fb77318b7 100644 --- a/translations/ko-KR/data/reusables/code-scanning/upload-sarif-alert-limit.md +++ b/translations/ko-KR/data/reusables/code-scanning/upload-sarif-alert-limit.md @@ -1,5 +1,8 @@ {% note %} -**Note:** SARIF upload supports a maximum of {% ifversion ghae-next or fpt or ghes > 3.0 %}5000{% else %}1000{% endif %} results per upload. Any results over this limit are ignored. If a tool generates too many results, you should update the configuration to focus on results for the most important rules or queries. +**참고:** +- SARIF upload supports a maximum of {% ifversion ghae-next or fpt or ghes > 3.0 %}5000{% else %}1000{% endif %} results per upload. Any results over this limit are ignored. If a tool generates too many results, you should update the configuration to focus on results for the most important rules or queries. + + - For each upload, SARIF upload supports a maximum size of 10 MB for the `gzip`-compressed SARIF file. Any uploads over this limit will be rejected. If your SARIF file is too large because it contains too many results, you should update the configuration to focus on results for the most important rules or queries. {% endnote %} diff --git a/translations/ko-KR/data/reusables/codespaces/create-or-switch-branch.md b/translations/ko-KR/data/reusables/codespaces/create-or-switch-branch.md new file mode 100644 index 0000000000..caaf86c2d7 --- /dev/null +++ b/translations/ko-KR/data/reusables/codespaces/create-or-switch-branch.md @@ -0,0 +1,3 @@ +1. If the current branch is not shown in the status bar, at the bottom of your codespace, right-click the status bar and select **Source control**. +1. Click the branch name in the status bar. ![The branch in the status bar](/assets/images/help/codespaces/branch-in-status-bar.png) +1. In the drop-down, either click the branch you want to switch to, or enter the name for a new branch and click **Create new branch**. ![Choose from the branch menu](/assets/images/help/codespaces/create-new-branch.png) \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/codespaces/source-control-commit-changes.md b/translations/ko-KR/data/reusables/codespaces/source-control-commit-changes.md new file mode 100644 index 0000000000..19f38cca4a --- /dev/null +++ b/translations/ko-KR/data/reusables/codespaces/source-control-commit-changes.md @@ -0,0 +1,4 @@ +{% data reusables.codespaces.source-control-display-dark %} +1. To stage your changes, click **+** next to the file you've changed, or next to **Changes** if you've changed multiple files and you want to stage them all. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-stage.png) +1. Type a commit message describing the change you've made. ![Source control side bar with a commit message](/assets/images/help/codespaces/codespaces-commit-commit-message.png) +1. To commit your staged changes, click the check mark at the top the source control side bar. ![Click the check mark icon](/assets/images/help/codespaces/codespaces-commit-checkmark-icon.png) \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/codespaces/source-control-pull-request.md b/translations/ko-KR/data/reusables/codespaces/source-control-pull-request.md new file mode 100644 index 0000000000..803f8981b6 --- /dev/null +++ b/translations/ko-KR/data/reusables/codespaces/source-control-pull-request.md @@ -0,0 +1,3 @@ +1. After you've committed changes to your local copy of the repository, click the **Create Pull Request** icon. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-pr-button.png) +1. Check that the local branch and repository you're merging from, and the remote branch and repository you're merging into, are correct. Then give the pull request a title and a description. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-pr.png) +1. Click **Create**. \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/dependabot/supported-package-managers.md b/translations/ko-KR/data/reusables/dependabot/supported-package-managers.md index c36c86fce9..da7d7580cc 100644 --- a/translations/ko-KR/data/reusables/dependabot/supported-package-managers.md +++ b/translations/ko-KR/data/reusables/dependabot/supported-package-managers.md @@ -26,7 +26,7 @@ The following table shows, for each package manager: | Terraform | `terraform` | >= 0.13, <= 1.0 | **✓** | **✓** | | | yarn | `npm` | v1 | **✓** | **✓** | | -[1] {% data variables.product.prodname_dependabot %} doesn't run Gradle but supports updates to the following files: `build.gradle` and `build.gradle.kts` (for Kotlin projects). +[1] {% data variables.product.prodname_dependabot %} doesn't run Gradle but supports updates to the following files: `build.gradle`, `build.gradle.kts` (for Kotlin projects), and files included via the `apply` declaration that have `dependencies` in the filename. Note that `apply` does not support `apply to`, recursion, or advanced syntaxes (for example, Kotlin's `apply` with `mapOf`, filenames defined by property). [2] {% data variables.product.prodname_dependabot %} doesn't run Maven but supports updates to `pom.xml` files. diff --git a/translations/ko-KR/data/reusables/dependency-review/beta.md b/translations/ko-KR/data/reusables/dependency-review/beta.md index d8f7089def..3ca1720c35 100644 --- a/translations/ko-KR/data/reusables/dependency-review/beta.md +++ b/translations/ko-KR/data/reusables/dependency-review/beta.md @@ -1,7 +1,8 @@ -{% ifversion fpt or ghes > 3.1 %} +{% ifversion ghes > 3.1 %} {% note %} **Note:** Dependency review is currently in beta and subject to change. {% endnote %} + {% endif %} \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/developer-site/pull_request_forked_repos_link.md b/translations/ko-KR/data/reusables/developer-site/pull_request_forked_repos_link.md index a46c58ce61..b871adff69 100644 --- a/translations/ko-KR/data/reusables/developer-site/pull_request_forked_repos_link.md +++ b/translations/ko-KR/data/reusables/developer-site/pull_request_forked_repos_link.md @@ -1,4 +1,4 @@ -#### Pull request events for forked repositories +### Pull request events for forked repositories {% note %} diff --git a/translations/ko-KR/data/reusables/dotcom_billing/pricing_cal.md b/translations/ko-KR/data/reusables/dotcom_billing/pricing_cal.md new file mode 100644 index 0000000000..6509379b28 --- /dev/null +++ b/translations/ko-KR/data/reusables/dotcom_billing/pricing_cal.md @@ -0,0 +1 @@ +To estimate the costs for consumptive services, you can use the {% data variables.product.prodname_dotcom %} pricing calculator. For more information, go to https://github.com/pricing/calculator. diff --git a/translations/ko-KR/data/reusables/enterprise-accounts/about-enterprise-accounts.md b/translations/ko-KR/data/reusables/enterprise-accounts/about-enterprise-accounts.md index 6e93b02d5e..f33b5c1491 100644 --- a/translations/ko-KR/data/reusables/enterprise-accounts/about-enterprise-accounts.md +++ b/translations/ko-KR/data/reusables/enterprise-accounts/about-enterprise-accounts.md @@ -14,7 +14,7 @@ Organizations are shared accounts where enterprise members can collaborate acros {% ifversion fpt %} -Enterprise owners can create organizations and link the organizations to the enterprise. After you add organizations to your enterprise account, you can manage and enforce policies for the organizations. Specific enforcement options vary by setting; generally, you can choose to enforce a single policy for every organization in your enterprise account or allow owners to set policy on the organization level. For more information, see "[Setting policies for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account)." +Enterprise owners can create organizations and link the organizations to the enterprise. Alternatively, you can invite an existing organization to join your enterprise. After you add organizations to your enterprise account, you can manage and enforce policies for the organizations. Specific enforcement options vary by setting; generally, you can choose to enforce a single policy for every organization in your enterprise account or allow owners to set policy on the organization level. For more information, see "[Setting policies for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account)." {% elsif ghes or ghae %} @@ -58,6 +58,14 @@ For more information about the differences between {% data variables.product.pro {% endif %} +{% ifversion fpt %} + +## About {% data variables.product.prodname_emus %} + +{% data reusables.enterprise-accounts.emu-short-summary %} + +{% endif %} + ## About billing for your enterprise account The bill for your enterprise account includes the monthly cost for each member of your enterprise. The bill includes {% ifversion fpt %}any paid licenses in organizations outside of your enterprise account, subscriptions to apps in {% data variables.product.prodname_marketplace %}, {% endif %}{% ifversion fpt or ghae %}additional paid services for your enterprise{% ifversion fpt %} like data packs for {% data variables.large_files.product_name_long %},{% endif %} and{% endif %} usage for {% data variables.product.prodname_GH_advanced_security %}. diff --git a/translations/ko-KR/data/reusables/enterprise-accounts/access-enterprise.md b/translations/ko-KR/data/reusables/enterprise-accounts/access-enterprise.md index a47a055301..19b6004028 100644 --- a/translations/ko-KR/data/reusables/enterprise-accounts/access-enterprise.md +++ b/translations/ko-KR/data/reusables/enterprise-accounts/access-enterprise.md @@ -5,5 +5,4 @@ {% elsif ghes or ghae %}1. In the top-right corner of {% data variables.product.product_name %}, click your profile photo, then click **Enterprise settings**. !["Enterprise settings" in drop-down menu for profile photo on {% data variables.product.product_name %}](/assets/images/enterprise/settings/enterprise-settings.png) - {% endif %} diff --git a/translations/ko-KR/data/reusables/enterprise-accounts/actions-runners-tab.md b/translations/ko-KR/data/reusables/enterprise-accounts/actions-runners-tab.md index 19b2de94c1..b6dc023362 100644 --- a/translations/ko-KR/data/reusables/enterprise-accounts/actions-runners-tab.md +++ b/translations/ko-KR/data/reusables/enterprise-accounts/actions-runners-tab.md @@ -1 +1 @@ -1. Click the {% ifversion fpt %}**Runners**{% else %}**Self-hosted runners**{% endif %} tab. +1. Click the {% ifversion fpt or ghes > 3.1 or ghae-next %}**Runners**{% else %}**Self-hosted runners**{% endif %} tab. diff --git a/translations/ko-KR/data/reusables/enterprise-accounts/emu-forks.md b/translations/ko-KR/data/reusables/enterprise-accounts/emu-forks.md new file mode 100644 index 0000000000..315ee2736f --- /dev/null +++ b/translations/ko-KR/data/reusables/enterprise-accounts/emu-forks.md @@ -0,0 +1 @@ +{% data variables.product.prodname_managed_users_caps %} cannot fork repositories from outside of the enterprise or fork internal repositories. {% data variables.product.prodname_managed_users_caps %} can fork private repositories owned by organizations in the enterprise into other organizations owned by the enterprise, or as a fork owned by the {% data variables.product.prodname_managed_user %}. \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/enterprise-accounts/emu-more-info-account.md b/translations/ko-KR/data/reusables/enterprise-accounts/emu-more-info-account.md new file mode 100644 index 0000000000..21302799fb --- /dev/null +++ b/translations/ko-KR/data/reusables/enterprise-accounts/emu-more-info-account.md @@ -0,0 +1 @@ +For more information, see "[Types of GitHub accounts](/get-started/learning-about-github/types-of-github-accounts#enterprise-managed-users)." \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/enterprise-accounts/emu-password-reset-session.md b/translations/ko-KR/data/reusables/enterprise-accounts/emu-password-reset-session.md new file mode 100644 index 0000000000..65ed74cc65 --- /dev/null +++ b/translations/ko-KR/data/reusables/enterprise-accounts/emu-password-reset-session.md @@ -0,0 +1 @@ +If you need to reset the password for your setup user, use an incognito or private browsing window to request a new password. When the email arrives with the link to reset your password, copy the link into your browser. For more information on resetting your password, see "[Requesting a new password ](/github/authenticating-to-github/keeping-your-account-and-data-secure/updating-your-github-access-credentials#requesting-a-new-password)." \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/enterprise-accounts/emu-permission-follow.md b/translations/ko-KR/data/reusables/enterprise-accounts/emu-permission-follow.md new file mode 100644 index 0000000000..f166721634 --- /dev/null +++ b/translations/ko-KR/data/reusables/enterprise-accounts/emu-permission-follow.md @@ -0,0 +1 @@ +{% ifversion fpt %} Members of an {% data variables.product.prodname_emu_enterprise %} can only follow other members of their enterprise. {% endif %} \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/enterprise-accounts/emu-permission-fork.md b/translations/ko-KR/data/reusables/enterprise-accounts/emu-permission-fork.md new file mode 100644 index 0000000000..411dfeed7b --- /dev/null +++ b/translations/ko-KR/data/reusables/enterprise-accounts/emu-permission-fork.md @@ -0,0 +1 @@ +{% ifversion fpt %}Members of an {% data variables.product.prodname_emu_enterprise %} cannot fork repositories from outside of the enterprise or fork internal repositories.{% endif %} \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/enterprise-accounts/emu-permission-gist.md b/translations/ko-KR/data/reusables/enterprise-accounts/emu-permission-gist.md new file mode 100644 index 0000000000..3164ea3434 --- /dev/null +++ b/translations/ko-KR/data/reusables/enterprise-accounts/emu-permission-gist.md @@ -0,0 +1 @@ +{% ifversion fpt %}Members of an {% data variables.product.prodname_emu_enterprise %} cannot create gists and have read-only access to gists.{% endif %} \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/enterprise-accounts/emu-permission-interact.md b/translations/ko-KR/data/reusables/enterprise-accounts/emu-permission-interact.md new file mode 100644 index 0000000000..9bdeac19e8 --- /dev/null +++ b/translations/ko-KR/data/reusables/enterprise-accounts/emu-permission-interact.md @@ -0,0 +1 @@ +{% ifversion fpt %} Members of an {% data variables.product.prodname_emu_enterprise %} can only interact with repositories within their enterprise. {% endif %} \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/enterprise-accounts/emu-permission-propose.md b/translations/ko-KR/data/reusables/enterprise-accounts/emu-permission-propose.md new file mode 100644 index 0000000000..85fd4f66e3 --- /dev/null +++ b/translations/ko-KR/data/reusables/enterprise-accounts/emu-permission-propose.md @@ -0,0 +1 @@ +{% ifversion fpt %} Members of an {% data variables.product.prodname_emu_enterprise %} can only propose changes in repositories that are part of their enterprise. {% endif %} diff --git a/translations/ko-KR/data/reusables/enterprise-accounts/emu-permission-repo.md b/translations/ko-KR/data/reusables/enterprise-accounts/emu-permission-repo.md new file mode 100644 index 0000000000..b4278362a5 --- /dev/null +++ b/translations/ko-KR/data/reusables/enterprise-accounts/emu-permission-repo.md @@ -0,0 +1 @@ +{% ifversion fpt %} Members of an {% data variables.product.prodname_emu_enterprise %} can only make changes in repositories that are part of their enterprise. {% endif %} diff --git a/translations/ko-KR/data/reusables/enterprise-accounts/emu-saml-note.md b/translations/ko-KR/data/reusables/enterprise-accounts/emu-saml-note.md new file mode 100644 index 0000000000..2a5bdae038 --- /dev/null +++ b/translations/ko-KR/data/reusables/enterprise-accounts/emu-saml-note.md @@ -0,0 +1,7 @@ +{% ifversion fpt%} +{% note %} + +**Note**: If your enterprise uses {% data variables.product.prodname_emus %}, you must follow a different process to configure SAML single sign-on. For more information, see "[Configuring SAML single sign-on for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." + +{% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/enterprise-accounts/emu-scim-note.md b/translations/ko-KR/data/reusables/enterprise-accounts/emu-scim-note.md new file mode 100644 index 0000000000..309ec9adfb --- /dev/null +++ b/translations/ko-KR/data/reusables/enterprise-accounts/emu-scim-note.md @@ -0,0 +1,7 @@ +{% ifversion fpt%} +{% note %} + +**Note**: If your enterprise uses {% data variables.product.prodname_emus %}, you cannot use team synchronization and must instead configure SCIM to manage membership with your identity provider. For more information, see "[Configuring SCIM provisioning for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users)." + +{% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/enterprise-accounts/emu-short-summary.md b/translations/ko-KR/data/reusables/enterprise-accounts/emu-short-summary.md new file mode 100644 index 0000000000..7e4f69fff9 --- /dev/null +++ b/translations/ko-KR/data/reusables/enterprise-accounts/emu-short-summary.md @@ -0,0 +1 @@ +{% data variables.product.prodname_emus %} is a feature of {% data variables.product.prodname_ghe_cloud %} that provides even greater control over enterprise members and resources. With {% data variables.product.prodname_emus %}, all members are provisioned and managed through your identity provider (IdP) instead of users creating their own accounts on {% data variables.product.product_name %}. Team membership can be managed using groups on your IdP. {% data variables.product.prodname_managed_users_caps %} are restricted to their enterprise and are unable to push code, collaborate, or interact with users, repositories, and organizations outside of their enterprise. For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/enterprise-accounts/emu-shortcode.md b/translations/ko-KR/data/reusables/enterprise-accounts/emu-shortcode.md new file mode 100644 index 0000000000..ec695c807d --- /dev/null +++ b/translations/ko-KR/data/reusables/enterprise-accounts/emu-shortcode.md @@ -0,0 +1 @@ +The short code must be unique to your enterprise, a three-to-eight character alphanumeric string, and contain no special characters. \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/enterprise-accounts/emu-supported-idps.md b/translations/ko-KR/data/reusables/enterprise-accounts/emu-supported-idps.md new file mode 100644 index 0000000000..375040efa3 --- /dev/null +++ b/translations/ko-KR/data/reusables/enterprise-accounts/emu-supported-idps.md @@ -0,0 +1,2 @@ +* Azure Active Directory (Azure AD) +* Okta \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/enterprise-accounts/github-connect-tab.md b/translations/ko-KR/data/reusables/enterprise-accounts/github-connect-tab.md index fa8d262206..abb45a109b 100644 --- a/translations/ko-KR/data/reusables/enterprise-accounts/github-connect-tab.md +++ b/translations/ko-KR/data/reusables/enterprise-accounts/github-connect-tab.md @@ -1,3 +1,3 @@ {% ifversion ghes < 3.1 %} 1. In the left sidebar, click **{% data variables.product.prodname_github_connect %}**. ![GitHub Connect tab in the business account settings sidebar](/assets/images/enterprise/business-accounts/settings-github-connect-tab.png){% else %} -1. In the enterprise account sidebar, click {% octicon "plug" aria-label="The GitHub Connect gear" %} **{% data variables.product.prodname_github_connect %}**. ![GitHub Connect tab in the enterprise account sidebar](/assets/images/help//business-accounts/enterprise-account-github-connect-tab.png){% endif %} \ No newline at end of file +1. In the enterprise account sidebar, click {% octicon "plug" aria-label="The GitHub Connect gear" %} **{% data variables.product.prodname_github_connect %}**. ![GitHub Connect tab in the enterprise account sidebar](/assets/images/help//business-accounts/enterprise-account-github-connect-tab.png){% endif %} diff --git a/translations/ko-KR/data/reusables/enterprise-accounts/identity-provider-tab.md b/translations/ko-KR/data/reusables/enterprise-accounts/identity-provider-tab.md new file mode 100644 index 0000000000..9e94eecb59 --- /dev/null +++ b/translations/ko-KR/data/reusables/enterprise-accounts/identity-provider-tab.md @@ -0,0 +1 @@ +1. Under your business account's name, click {% octicon "key" aria-label="The key icon" %} **Identity provider**. !["Identity provider" tab in enterprise sidebar](/assets/images/help/enterprises/enterprise-account-identity-provider-tab.png) \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/enterprise-accounts/invite-organization.md b/translations/ko-KR/data/reusables/enterprise-accounts/invite-organization.md new file mode 100644 index 0000000000..1d5c99c11e --- /dev/null +++ b/translations/ko-KR/data/reusables/enterprise-accounts/invite-organization.md @@ -0,0 +1 @@ +Enterprise account owners and administrators can invite existing organization accounts to join their enterprise. For more information, see "[Inviting an organization to join your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account#inviting-an-organization-to-join-your-enterprise-account)" diff --git a/translations/ko-KR/data/reusables/enterprise-accounts/team-sync-override.md b/translations/ko-KR/data/reusables/enterprise-accounts/team-sync-override.md new file mode 100644 index 0000000000..a39283eed0 --- /dev/null +++ b/translations/ko-KR/data/reusables/enterprise-accounts/team-sync-override.md @@ -0,0 +1 @@ +If your organization is owned by an enterprise account, enabling team synchronization or SCIM provisioning for the enterprise account will override your organization-level team synchronization settings. For more information, see "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)" and "[Configuring SCIM provisioning for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users)." \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/enterprise_clustering/proxy_protocol_ports.md b/translations/ko-KR/data/reusables/enterprise_clustering/proxy_protocol_ports.md index 17d24f3f00..c0cc4f655f 100644 --- a/translations/ko-KR/data/reusables/enterprise_clustering/proxy_protocol_ports.md +++ b/translations/ko-KR/data/reusables/enterprise_clustering/proxy_protocol_ports.md @@ -1,4 +1,4 @@ -#### PROXY protocol TCP port mappings +### PROXY protocol TCP port mappings | Source port | Destination port | Service description | |:-----------:|:----------------:|:------------------------:| diff --git a/translations/ko-KR/data/reusables/enterprise_clustering/without_proxy_protocol_ports.md b/translations/ko-KR/data/reusables/enterprise_clustering/without_proxy_protocol_ports.md index f8570c7cfe..2c13369f10 100644 --- a/translations/ko-KR/data/reusables/enterprise_clustering/without_proxy_protocol_ports.md +++ b/translations/ko-KR/data/reusables/enterprise_clustering/without_proxy_protocol_ports.md @@ -1,4 +1,4 @@ -#### Protocol TCP port mappings for use without PROXY support +### Protocol TCP port mappings for use without PROXY support | Source port | Destination port | Service description | |:-----------:|:----------------:|:------------------------:| diff --git a/translations/ko-KR/data/reusables/gated-features/emus.md b/translations/ko-KR/data/reusables/gated-features/emus.md new file mode 100644 index 0000000000..f9f25095ea --- /dev/null +++ b/translations/ko-KR/data/reusables/gated-features/emus.md @@ -0,0 +1 @@ +To manage users in your enterprise with your identity provider, your enterprise must be enabled for {% data variables.product.prodname_emus %}, which are available with {% data variables.product.prodname_ghe_cloud %}. For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/getting-started/enterprise-advanced-security.md b/translations/ko-KR/data/reusables/getting-started/enterprise-advanced-security.md new file mode 100644 index 0000000000..faffbe7d63 --- /dev/null +++ b/translations/ko-KR/data/reusables/getting-started/enterprise-advanced-security.md @@ -0,0 +1 @@ +If you have a GitHub Advanced Security license for your enterprise account, you can enforce policies to manage {% data variables.product.prodname_dotcom %} Advanced Security features for organizations owned by an enterprise account. For more information, see "[Enforcing policies for Advanced Security in your enterprise account](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-policies-for-advanced-security-in-your-enterprise-account)." \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/github-actions/actions-on-examples.md b/translations/ko-KR/data/reusables/github-actions/actions-on-examples.md index 7b672ef593..bb945b991c 100644 --- a/translations/ko-KR/data/reusables/github-actions/actions-on-examples.md +++ b/translations/ko-KR/data/reusables/github-actions/actions-on-examples.md @@ -1,18 +1,18 @@ -### Example: Using a single event +## Example: Using a single event ```yaml # Triggered when code is pushed to any branch in a repository on: push ``` -### Example: Using a list of events +## Example: Using a list of events ```yaml # Triggers the workflow on push or pull request events on: [push, pull_request] ``` -### Example: Using multiple events with activity types or configuration +## Example: Using multiple events with activity types or configuration If you need to specify activity types or configuration for an event, you must configure each event separately. You must append a colon (`:`) to all events, including events without configuration. diff --git a/translations/ko-KR/data/reusables/github-actions/disabling-github-actions.md b/translations/ko-KR/data/reusables/github-actions/disabling-github-actions.md index ae73419a8d..afe8ee7f1f 100644 --- a/translations/ko-KR/data/reusables/github-actions/disabling-github-actions.md +++ b/translations/ko-KR/data/reusables/github-actions/disabling-github-actions.md @@ -1 +1 @@ -By default, {% ifversion ghes or ghae %}after {% data variables.product.prodname_actions %} is enabled on {% data variables.product.product_location %}, it{% elsif fpt %}{% data variables.product.prodname_actions %}{% endif %} is enabled on all repositories and organizations. You can choose to disable {% data variables.product.prodname_actions %} or limit them to private actions only, which means that people can only use actions that exist in your repository. +By default, {% ifversion ghes or ghae %}after {% data variables.product.prodname_actions %} is enabled on {% data variables.product.product_location %}, it{% elsif fpt %}{% data variables.product.prodname_actions %}{% endif %} is enabled on all repositories and organizations. You can choose to disable {% data variables.product.prodname_actions %} or limit them to local actions only, which means that people can only use actions that exist in your repository. diff --git a/translations/ko-KR/data/reusables/github-actions/name-environment.md b/translations/ko-KR/data/reusables/github-actions/name-environment.md new file mode 100644 index 0000000000..f6fd5c69d4 --- /dev/null +++ b/translations/ko-KR/data/reusables/github-actions/name-environment.md @@ -0,0 +1 @@ +1. Enter a name for the environment, then click **Configure environment**. Environment names are not case sensitive. An environment name may not exceed 255 characters and must be unique within the repository. diff --git a/translations/ko-KR/data/reusables/github-actions/new-environment.md b/translations/ko-KR/data/reusables/github-actions/new-environment.md new file mode 100644 index 0000000000..879f2bf20a --- /dev/null +++ b/translations/ko-KR/data/reusables/github-actions/new-environment.md @@ -0,0 +1 @@ +1. Click **New environment**. diff --git a/translations/ko-KR/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md b/translations/ko-KR/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md index 943a167ed5..256bd41f1c 100644 --- a/translations/ko-KR/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md +++ b/translations/ko-KR/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md @@ -1,6 +1,7 @@ -1. In the {% ifversion fpt %}"Runners"{% else %}"Self-hosted runners"{% endif %} section of the settings page, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} next to the runner group you'd like to configure, then click **Edit name and [organization|repository] access**. ![Manage repository permissions](/assets/images/help/settings/actions-runner-manage-permissions.png) +1. In the {% ifversion fpt or ghes > 3.1 or ghae-next %}"Runners"{% else %}"Self-hosted runners"{% endif %} section of the settings page, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} next to the runner group you'd like to configure, then click **Edit name and [organization|repository] access**. ![Manage repository permissions](/assets/images/help/settings/actions-runner-manage-permissions.png) 1. Modify your policy options, or change the runner group name. + {% ifversion not ghae %} {% warning %} **경고** @@ -10,3 +11,4 @@ For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)." {% endwarning %} + {% endif %} diff --git a/translations/ko-KR/data/reusables/github-actions/self-hosted-runner-list.md b/translations/ko-KR/data/reusables/github-actions/self-hosted-runner-list.md index 6edf2cb3f9..f6cb3732b1 100644 --- a/translations/ko-KR/data/reusables/github-actions/self-hosted-runner-list.md +++ b/translations/ko-KR/data/reusables/github-actions/self-hosted-runner-list.md @@ -1 +1 @@ - 1. Locate the list of runners under {% ifversion fpt %}"Runners"{% else %}"Self-hosted runners"{% endif %}. + 1. Locate the list of runners under {% ifversion fpt or ghes > 3.1 or ghae-next %}"Runners"{% else %}"Self-hosted runners"{% endif %}. diff --git a/translations/ko-KR/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md b/translations/ko-KR/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md index a8f6c616fb..eee56b2885 100644 --- a/translations/ko-KR/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md +++ b/translations/ko-KR/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md @@ -6,5 +6,5 @@ 1. In the left sidebar, click **Enterprise overview**. 1. {% endif %} In the enterprise sidebar, {% octicon "law" aria-label="The law icon" %} **Policies**. 1. Navigate to the {% data variables.product.prodname_actions %} settings: - * **In an organization or repository**: Click **Actions** in the left sidebar{% ifversion fpt %}, then click **Runners**{% endif %}. - * {% ifversion fpt %}**If using an enterprise account**:{% elsif ghes or ghae %}**If using an enterprise-level runner**:{% endif %} Click **Actions** under "{% octicon "law" aria-label="The law icon" %} Policies"{% ifversion fpt %}, then click the **Runners** tab{% endif %}. + * **In an organization or repository**: Click **Actions** in the left sidebar{% ifversion fpt or ghes > 3.1 or ghae-next %}, then click **Runners**{% endif %}. + * {% ifversion fpt %}**If using an enterprise account**:{% elsif ghes or ghae %}**If using an enterprise-level runner**:{% endif %} Click **Actions** under "{% octicon "law" aria-label="The law icon" %} Policies"{% ifversion fpt or ghes > 3.1 or ghae-next %}, then click the **Runners** tab{% endif %}. diff --git a/translations/ko-KR/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md b/translations/ko-KR/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md index 44f3b792d0..aac9a6f362 100644 --- a/translations/ko-KR/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md +++ b/translations/ko-KR/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md @@ -1,4 +1,4 @@ -1. Under {% ifversion fpt %}"Runners"{% else %}"Self-hosted runners"{% endif %}, locate the runner in the list. If your runner is in a group, click {% octicon "chevron-down" aria-label="The downwards chevron" %} to expand the list. +1. Under {% ifversion fpt or ghes > 3.1 or ghae-next %}"Runners"{% else %}"Self-hosted runners"{% endif %}, locate the runner in the list. If your runner is in a group, click {% octicon "chevron-down" aria-label="The downwards chevron" %} to expand the list. 1. Click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} next to the runner you want to remove, then click **Remove**. ![Removing a self-hosted runner setting](/assets/images/help/settings/actions-runner-remove.png) diff --git a/translations/ko-KR/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md b/translations/ko-KR/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md index 1be447145b..d51fdc01ef 100644 --- a/translations/ko-KR/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md +++ b/translations/ko-KR/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md @@ -1,2 +1,2 @@ -1. In the left sidebar, click **Actions**. -1. In the left sidebar, under "Actions", click **Runner groups**. +1. In the left sidebar, click **Actions**.{% ifversion fpt or ghes > 3.1 or ghae-next %} +1. In the left sidebar, under "Actions", click **Runner groups**.{% endif %} diff --git a/translations/ko-KR/data/reusables/github-actions/settings-sidebar-actions-runners.md b/translations/ko-KR/data/reusables/github-actions/settings-sidebar-actions-runners.md index cf1a5ba36f..181fbef515 100644 --- a/translations/ko-KR/data/reusables/github-actions/settings-sidebar-actions-runners.md +++ b/translations/ko-KR/data/reusables/github-actions/settings-sidebar-actions-runners.md @@ -1 +1 @@ -1. In the left sidebar, click **Actions**{% ifversion fpt %}, then click **Runners**{% endif %}. +1. In the left sidebar, click **Actions**{% ifversion fpt or ghes > 3.1 or ghae-next %}, then click **Runners**{% endif %}. diff --git a/translations/ko-KR/data/reusables/github-actions/supported-github-runners.md b/translations/ko-KR/data/reusables/github-actions/supported-github-runners.md index 525903bf25..958d5626ce 100644 --- a/translations/ko-KR/data/reusables/github-actions/supported-github-runners.md +++ b/translations/ko-KR/data/reusables/github-actions/supported-github-runners.md @@ -60,17 +60,6 @@ Ubuntu 18.04     - - - - - @@ -236,7 +235,7 @@ Assim que o seu trabalho começar a ser executado, você poderá {% ifversion fp Para continuar aprendendo sobre {% data variables.product.prodname_actions %}, consulte "[Encontrar e personalizar ações](/actions/learn-github-actions/finding-and-customizing-actions)". -To understand how billing works for {% data variables.product.prodname_actions %}, see "[About billing for {% data variables.product.prodname_actions %}](/actions/reference/usage-limits-billing-and-administration#about-billing-for-github-actions)". +Para entender como a cobrança funciona para {% data variables.product.prodname_actions %}, consulte "[Sobre cobrança para {% data variables.product.prodname_actions %}](/actions/reference/usage-limits-billing-and-administration#about-billing-for-github-actions)". ## Entrar em contato com o suporte diff --git a/translations/pt-BR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md b/translations/pt-BR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md index 7a1c570c4c..67d0a7fca7 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md +++ b/translations/pt-BR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md @@ -16,20 +16,19 @@ shortTitle: Cobrança do fluxo de trabalho & limites {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Sobre a cobrança do {% data variables.product.prodname_actions %} {% ifversion fpt %} {% data reusables.github-actions.actions-billing %} Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)". {% else %} -GitHub Actions usage is free for {% data variables.product.prodname_ghe_server %}s that use self-hosted runners. +O uso do GitHub Actions é gratuito para {% data variables.product.prodname_ghe_server %} que usam executores auto-hospedados. {% endif %} ## Limites de uso {% ifversion fpt %} -There are some limits on {% data variables.product.prodname_actions %} usage when using {% data variables.product.prodname_dotcom %}-hosted runners. Estes limites estão sujeitos a mudanças. +Existem alguns limites sobre o uso de {% data variables.product.prodname_actions %} ao usar executores hospedados em {% data variables.product.prodname_dotcom %}. Estes limites estão sujeitos a mudanças. {% note %} @@ -61,6 +60,12 @@ Os limites de uso aplicam-se a executores auto-hospedados. Para obter mais infor Além dos limites de uso, você deve garantir que você usa {% data variables.product.prodname_actions %} nos [Termos de serviço](/articles/github-terms-of-service/) do GitHub. Para obter mais informações sobre termos específicos de {% data variables.product.prodname_actions %}, consulte os [Termos adicionais do produto do GitHub](/github/site-policy/github-additional-product-terms#a-actions-usage). {% endif %} +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## Cobrança para fluxos de trabalho reutilizáveis + +Se você reutilizar um fluxo de trabalho, a cobrança será sempre associada ao fluxo de trabalho de chamadas. Para obter mais informações, consulte "[Reutilizando fluxos de trabalho](/actions/learn-github-actions/reusing-workflows)". +{% endif %} + {% ifversion fpt or ghes > 2.22 or ghae %} ## Artefato e política de retenção de registro @@ -70,9 +75,9 @@ Além dos limites de uso, você deve garantir que você usa {% data variables.pr Para obter mais informações, consulte: -- "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)" -- "[Configuring the retention period for {% data variables.product.prodname_actions %} for artifacts and logs in your organization](/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization)" -- "[Configuring the retention period for {% data variables.product.prodname_actions %} for artifacts and logs in your enterprise](/github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account)" +- "[Gerenciar 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#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)" +- "[Configurar o período de retenção para {% data variables.product.prodname_actions %} para artefatos e registros na sua organização](/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization)" +- "[Configurar o período de retenção para {% data variables.product.prodname_actions %} para artefatos e registros na sua empresa](/github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account)" {% endif %} ## Desativar ou limitar {% data variables.product.prodname_actions %} para o seu repositório ou organização @@ -80,7 +85,7 @@ Para obter mais informações, consulte: {% data reusables.github-actions.disabling-github-actions %} Para obter mais informações, consulte: -- "[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)" +- "[Gerenciar 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)" - "[Desabilitar ou limitar {% data variables.product.prodname_actions %} para a sua organização](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)"{% ifversion fpt %} - "[Aplicar as políticas de {% data variables.product.prodname_actions %} na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account)" para {% data variables.product.prodname_ghe_cloud %}{% endif %} diff --git a/translations/pt-BR/content/actions/learn-github-actions/using-workflow-templates.md b/translations/pt-BR/content/actions/learn-github-actions/using-workflow-templates.md index a09dc32ade..c22525a4a5 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/using-workflow-templates.md +++ b/translations/pt-BR/content/actions/learn-github-actions/using-workflow-templates.md @@ -1,7 +1,7 @@ --- -title: Using workflow templates -shortTitle: Using templates -intro: You can set up CI using a workflow template that matches the language and tooling you want to use. +title: Usando modelos de fluxo de trabalho +shortTitle: Usando modelos +intro: '{% data variables.product.product_name %} fornece modelos de fluxo de trabalho para uma série de linguagens e ferramentas.' product: '{% data reusables.gated-features.actions %}' redirect_from: - /articles/setting-up-continuous-integration-using-github-actions @@ -17,41 +17,38 @@ type: tutorial topics: - Workflows - CI + - CD --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -Qualquer pessoa com permissões de gravação em um repositório pode configurar a integração contínua (CI, Continuous Integration) usando o {% data variables.product.prodname_actions %}. +## Sobre os modelos do fluxo de trabalho -Depois de configurar a CI, você pode personalizar o fluxo de trabalho conforme as suas demandas. +{% data variables.product.product_name %} oferece modelos de fluxo de trabalho para uma série e linguagens e ferramentas. Ao configurar os fluxos de trabalho no repositório, {% data variables.product.product_name %} analisa o código no seu repositório e recomenda fluxos de trabalho baseados na linguagem e na estrutura do seu repositório. Por exemplo, se você usar o [Node.js](https://nodejs.org/en/), {% data variables.product.product_name %} irá sugerir um arquivo de modelo que instala seus pacotes Node.js e executa seus testes. + +Você também pode criar seus próprios modelos de fluxo de trabalho para compartilhar com sua organização. Para obter mais informações, consulte "[Criando modelos de fluxo de trabalho](/actions/learn-github-actions/creating-workflow-templates)". + +## Usando modelos de fluxo de trabalho + +Qualquer pessoa com a permissão de gravação em um repositório pode configurar fluxos de trabalho {% data variables.product.prodname_actions %} para CI/CD ou outra automatização. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} -1. Localize o modelo correspondente ao idioma e às ferramentas que você quer usar. Em seguida, clique em **Set up this workflow** (Configurar este fluxo de trabalho). ![Botão Setup workflow (Configurar fluxo de trabalho)](/assets/images/help/repository/setup-workflow-button.png) -5. Clique em **Start commit** (Iniciar commit). ![Botão Start commit (Iniciar commit)](/assets/images/help/repository/start-commit.png) -{% data reusables.files.write_commit_message %} -{% data reusables.files.choose_commit_branch %} -{% data reusables.files.propose_new_file %} - -Depois de fazer push no seu repositório, você pode acompanhar o status e os logs detalhados do fluxo de trabalho de integração contínua no {% data variables.product.prodname_dotcom %} e receber notificações personalizadas. Para obter mais informações, consulte "[Configurando notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)" e " -Gerenciando a execução do fluxo de trabalho".

    - -{% data reusables.repositories.actions-workflow-status-badge-intro %} - -Para obter mais informações, consulte "[Adicionando um selo de status do fluxo de trabalho](/actions/managing-workflow-runs/adding-a-workflow-status-badge)". - - +1. Se você já tem um fluxo de trabalho no seu repositório, clique em **Novo fluxo de trabalho**. +1. Encontre o modelo que deseja usar e, em seguida, clique em **Configurar este fluxo de trabalho**. +1. Se o modelo do fluxo de trabalho contiver comentários que detalham as etapas de instalação adicionais, siga estas etapas. +1. Alguns modelos de fluxo de trabalho usam segredos. Por exemplo, {% raw %}`${{ secrets.npm_token }}`{% endraw %}. Se o modelo do fluxo de trabalho usar um segredo, armazene o valor descrito no nome do segredo como um segredo no seu repositório. Para obter mais informações, consulte "[Segredos criptografados](/actions/reference/encrypted-secrets)". +1. Opcionalmente, faça as alterações adicionais. Por exemplo, talvez você queira alterar o valor de `on` para mudar quando o fluxo de trabalho é executado. +1. Clique em **Start commit** (Iniciar commit). +1. Escreva uma mensagem de commit e decida se você deseja de fazer o commit diretamente para o branch padrão ou abrir um pull request. ## Leia mais - [Sobre integração contínua](/articles/about-continuous-integration) -- [Gerenciar a execução de fluxos de trabalho](/articles/managing-a-workflow-run) -- "[Aprenda {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" - - {% ifversion fpt %} - -- "[Gerenciando cobrança para {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)" - - {% endif %} +- "[Gerenciando execuções de fluxo de trabalho](/actions/managing-workflow-runs)" +- "[Sobre o monitoramento e solução de problemas](/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting)" +- "[Aprenda {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" +{% ifversion fpt %} +- "[Gerenciando cobrança para {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)" +{% endif %} diff --git a/translations/pt-BR/content/actions/learn-github-actions/workflow-commands-for-github-actions.md b/translations/pt-BR/content/actions/learn-github-actions/workflow-commands-for-github-actions.md index fb6fe22f97..6254898382 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/workflow-commands-for-github-actions.md +++ b/translations/pt-BR/content/actions/learn-github-actions/workflow-commands-for-github-actions.md @@ -18,7 +18,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Sobre os comandos do fluxo de trabalho @@ -89,7 +88,7 @@ A tabela a seguir mostra quais funções do conjunto de ferramentas estão dispo | `core.setOutput` | `set-output` | | `core.setSecret` | `add-mask` | | `core.startGroup` | `grupo` | -| `core.warning` | `arquivo de aviso` | +| `core.warning` | `aviso` | {% ifversion ghes < 3.0 %} ## Definir uma variável de ambiente @@ -98,7 +97,7 @@ A tabela a seguir mostra quais funções do conjunto de ferramentas estão dispo ::set-env name={name}::{value} ``` -Creates or updates an environment variable for any steps running next in a job. The step that creates or updates the environment variable does not have access to the new value, but all subsequent steps in a job will have access. As variáveis de ambiente diferenciam maiúsculas de minúsculas e podem ter pontuação. +Cria ou atualiza uma variável de ambiente para quaisquer etapas a serem executadas em seguida no trabalho. A etapa que cria ou atualiza a variável de ambiente não tem acesso ao novo valor, mas todos os passos subsequentes em um trabalho terão acesso. As variáveis de ambiente diferenciam maiúsculas de minúsculas e podem ter pontuação. ### Exemplo @@ -155,13 +154,13 @@ echo "::debug::Set the Octocat variable" {% ifversion fpt or ghes > 3.2 or ghae-issue-4929 %} -## Setting a notice message +## Configurando uma mensagem de aviso ``` ::notice file={name},line={line},endLine={endLine},title={title}::{message} ``` -Creates a notice message and prints the message to the log. {% data reusables.actions.message-annotation-explanation %} +Cria uma mensagem de aviso e a imprime no registro. {% data reusables.actions.message-annotation-explanation %} {% data reusables.actions.message-parameters %} @@ -255,11 +254,11 @@ echo "::add-mask::$MY_NAME" Para de processar quaisquer comandos de fluxo de trabalho. Esse comando especial permite fazer o registro do que você desejar sem executar um comando do fluxo de trabalho acidentalmente. Por exemplo, é possível parar o log para gerar um script inteiro que tenha comentários. -To stop the processing of workflow commands, pass a unique token to `stop-commands`. To resume processing workflow commands, pass the same token that you used to stop workflow commands. +Para parar o processamento de comandos de fluxo de trabalho, passe um token único para `stop-commands`. Para retomar os comandos do fluxo de trabalho, passe o mesmo token que você usou para parar os comandos do fluxo de trabalho. {% warning %} -**Warning:** Make sure the token you're using is randomly generated and unique for each run. As demonstrated in the example below, you can generate a unique hash of your `github.token` for each run. +**Aviso:** Certifique-se de que o token que você está usando é gerado aleatoriamente e exclusivo para cada execução. Como demonstrado no exemplo abaixo, você pode gerar um hash exclusivo do seu `github.token` para cada execução. {% endwarning %} @@ -267,7 +266,7 @@ To stop the processing of workflow commands, pass a unique token to `stop-comman ::{endtoken}:: ``` -### Example stopping and starting workflow commands +### Exemplo de parar e iniciar comandos de workflow {% raw %} @@ -329,7 +328,13 @@ steps: echo "{name}={value}" >> $GITHUB_ENV ``` -Creates or updates an environment variable for any steps running next in a job. The step that creates or updates the environment variable does not have access to the new value, but all subsequent steps in a job will have access. As variáveis de ambiente diferenciam maiúsculas de minúsculas e podem ter pontuação. +Cria ou atualiza uma variável de ambiente para quaisquer etapas a serem executadas em seguida no trabalho. A etapa que cria ou atualiza a variável de ambiente não tem acesso ao novo valor, mas todos os passos subsequentes em um trabalho terão acesso. As variáveis de ambiente diferenciam maiúsculas de minúsculas e podem ter pontuação. + +{% note %} + +**Observação:** As variáveis de ambiente devem ser referenciadas explicitamente usando o [`env` contexto](/actions/reference/context-and-expression-syntax-for-github-actions#env-context) na sintaxe de expressão ou por meio do uso do arquivo `$GITHUB_ENV` diretamente. As variáveisde ambiente não estão implicitamente disponíveis nos comandos do shell. + +{% endnote %} ### Exemplo @@ -376,7 +381,7 @@ steps: echo "{path}" >> $GITHUB_PATH ``` -Prepara um diretório para a variável `PATH` do sistema e o torna disponível para todas as ações subsequentes no trabalho atual; a ação atualmente em execução não pode acessar a variável de caminho atualizada. Para ver os caminhos atualmente definidos para o seu trabalho, você pode usar o `echo "$PATH"` em uma etapa ou ação. +Prepara um diretório para a variável `PATH` do sistema e disponibiliza automaticamente para todas as ações subsequentes no trabalho atual; a ação atualmente em execução não pode acessar a variável de caminho atualizada. Para ver os caminhos atualmente definidos para o seu trabalho, você pode usar o `echo "$PATH"` em uma etapa ou ação. ### Exemplo diff --git a/translations/pt-BR/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md b/translations/pt-BR/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md index 0dbd66327d..a09bb12775 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md +++ b/translations/pt-BR/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md @@ -16,7 +16,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Sobre sintaxe YAML para fluxos de trabalho @@ -52,7 +51,7 @@ on: Ao usar os eventos `push` e `pull_request`, é possível configurar um fluxo de trabalho para ser executado em branches ou tags específicos. Para um evento de `pull_request`, são avaliados apenas os branches e tags na base. Se você definir apenas `tags` ou `branches`, o fluxo de trabalho não será executado para eventos que afetam o Git ref indefinido. -The `branches`, `branches-ignore`, `tags`, and `tags-ignore` keywords accept glob patterns that use characters like `*`, `**`, `+`, `?`, `!` and others to match more than one branch or tag name. If a name contains any of these characters and you want a literal match, you need to *escape* each of these special characters with `\`. For more information about glob patterns, see the "[Filter pattern cheat sheet](#filter-pattern-cheat-sheet)." +As palavras-chave `branches`, `branches-ignore`, `tags`, and `tags-ignore` aceitam padrões do glob que usam caracteres como `*`, `**`, `+`, `?`, `!` e outros para corresponder a mais de um nome do branch ou tag. Se um nome contiver qualquer um desses caracteres e você quiser uma correspondência literal, você deverá *escapar* de cada um desses caracteres especiais com `\`. Para obter mais informações sobre padrões de glob, consulte a "[Folha de informações para filtrar padrões](#filter-pattern-cheat-sheet)". ### Exemplo: Incluindo branches e tags @@ -169,7 +168,7 @@ on: {% note %} -**Note:** If you push more than 1,000 commits, or if {% data variables.product.prodname_dotcom %} does not generate the diff due to a timeout, the workflow will always run. +**Observação:** Se você fizer push de mais de 1.000 commits, ou se {% data variables.product.prodname_dotcom %} não gerar o diff devido a um tempo limite, o fluxo de trabalho sempre será executado. {% endnote %} @@ -180,13 +179,95 @@ O {% data variables.product.prodname_dotcom %} gera a lista de arquivos alterado - **Pushes para branches existentes:** um diff de dois pontos compara os SHAs head e base, um com o outro. - **Pushes para novos branches:** um diff de dois pontos compara o principal do ancestral do commit mais extenso que foi feito push. -Diffs are limited to 300 files. If there are files changed that aren't matched in the first 300 files returned by the filter, the workflow will not run. You may need to create more specific filters so that the workflow will run automatically. +Os diffs limitam-se a 300 arquivos. Se houver arquivos alterados que não correspondam aos primeiros 300 arquivos retornados pelo filtro, o fluxo de trabalho não será executado. Talvez seja necessário criar filtros mais específicos para que o fluxo de trabalho seja executado automaticamente. Para obter mais informações, consulte "[Sobre comparação de branches em pull requests](/articles/about-comparing-branches-in-pull-requests)". +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## `on.workflow_call.inputs` + +Ao usar a palavra-chave `workflow_call`, você poderá, opcionalmente, especificar entradas que são passadas para o fluxo de trabalho chamado no fluxo de trabalho de chamada. As entradas para fluxos de trabalho reutilizáveis são especificadas com o mesmo formato que entradas de ações. Para obter mais informações sobre as entradas, consulte "[Sintaxe de metadados para o GitHub Actions](/actions/creating-actions/metadata-syntax-for-github-actions#inputs)". Para obter mais informações sobre a palavra-chave `workflow_call`, consulte "[Eventos que acionam fluxos de trabalho](/actions/learn-github-actions/events-that-trigger-workflows#workflow-reuse-events)." + +Além dos parâmetros de entrada padrão que estão disponíveis, `on.workflow_call.inputs` exige um parâmetro `tipo`. Para obter mais informações, consulte [`on.workflow_call..type`](#onworkflow_callinput_idtype). + +Se um parâmetro `padrão` não fordefinido, o valor padrão da entrada será `falso` para um booleano, `0` para um número e `""` para uma string. + +No fluxo de trabalho chamado, você pode usar o contexto `entradas` para referir-se a uma entrada. + +Se um fluxo de trabalho de chamada passar uma entrada que não é especificada no fluxo de trabalho de chamada, isso irá gerar um erro. + +### Exemplo + +{% raw %} +```yaml +on: + workflow_call: + inputs: + username: + description: 'A username passed from the caller workflow' + default: 'john-doe' + required: false + type: string + +jobs: + print-username: + runs-on: ubuntu-latest + + steps: + - name: Print the input name to STDOUT + run: echo The username is ${{ inputs.username }} +``` +{% endraw %} + +Para obter mais informações, consulte "[Reutilizando fluxos de trabalho](/actions/learn-github-actions/reusing-workflows)". + +## `on.workflow_call..type` + +Necessário se a entrada for definida para a palavra-chave `on.workflow_call`. O valor deste parâmetro é uma string que especifica o tipo de dados da entrada. Este deve ser um dos valores a seguir: `booleano`, `número` ou `string`. + +## `on.workflow_call.secrets` + +Um mapa dos segredos que pode ser usado no fluxo de trabalho de chamada. + +Dentro do fluxo de trabalho de chamada, você pode usar o contexto `segredos` para consultar um segredo. + +Se um fluxo de trabalho de chamada passar um segredo que não é especificado no fluxo de trabalho chamado, isso irá gerar um erro. + +### Exemplo + +{% raw %} +```yaml +on: + workflow_call: + secrets: + access-token: + description: 'A token passed from the caller workflow' + required: false + +jobs: + pass-secret-to-action: + runs-on: ubuntu-latest + + steps: + - name: Pass the received secret to an action + uses: ./.github/actions/my-action@v1 + with: + token: ${{ secrets.access-token }} +``` +{% endraw %} + +## `on.workflow_call.secrets.` + +Um identificador de string para associar ao segredo. + +## `on.workflow_call.secrets..required` + +Um booleano que especifica se o segredo deve ser fornecido. +{% endif %} + ## `on.workflow_dispatch.inputs` -When using `workflow_dispatch` event, you can optionally specify inputs that are passed to the workflow. Workflow dispatch inputs are specified with the same format as action inputs. For more information about the format see "[Metadata syntax for GitHub Actions](/actions/creating-actions/metadata-syntax-for-github-actions#inputs)." +Ao usar o evento `workflow_dispatch`, você pode, opcionalmente, especificar as entradas que são passadas para o fluxo de trabalho. As entradas de fluxo de trabalho são especificadas no mesmo formato que as entradas de ações. Para obter mais informações sobre o formato, consulte "[Sintaxe de Metadados para o GitHub Actions](/actions/creating-actions/metadata-syntax-for-github-actions#inputs)". ```yaml on: @@ -201,7 +282,7 @@ on: required: false ``` -The triggered workflow receives the inputs in the `github.event.inputs` context. Para obter mais informações, consulte "[Contextos](/actions/learn-github-actions/contexts#github-context)". +O fluxo de trabalho acionado recebe as entradas no contexto `github.event.inputs`. Para obter mais informações, consulte "[Contextos](/actions/learn-github-actions/contexts#github-context)". ## `on.schedule` @@ -272,9 +353,7 @@ defaults: {% ifversion fpt or ghae-next or ghes > 3.1 %} ## `concorrência` -{% data reusables.actions.concurrency-beta %} - -A moeda garante que apenas um único trabalho ou fluxo de trabalho que usa o mesmo grupo de concorrência seja executado de cada vez. Um grupo de concorrência pode ser qualquer string ou expressão. The expression can only use the [`github` context](/actions/learn-github-actions/contexts#github-context). For more information about expressions, see "[Expressions](/actions/learn-github-actions/expressions)." +A moeda garante que apenas um único trabalho ou fluxo de trabalho que usa o mesmo grupo de concorrência seja executado de cada vez. Um grupo de concorrência pode ser qualquer string ou expressão. A expressão só pode usar o contexto [`github`](/actions/learn-github-actions/contexts#github-context). Para obter mais informações sobre expressões, consulte "[Expressões](/actions/learn-github-actions/expressions)". Você também pode especificar `concorrência` no nível do trabalho. Para obter mais informações, consulte [`jobs..concurrency`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idconcurrency). @@ -344,7 +423,7 @@ jobs: needs: [job1, job2] ``` -Neste exemplo, `job3` usa a expressão condicional `always()` para que ela sempre seja executada depois de `job1` e `job2` terem sido concluídos, independentemente de terem sido bem sucedidos. For more information, see "[Expressions](/actions/learn-github-actions/expressions#job-status-check-functions)." +Neste exemplo, `job3` usa a expressão condicional `always()` para que ela sempre seja executada depois de `job1` e `job2` terem sido concluídos, independentemente de terem sido bem sucedidos. Para obter mais informações, consulte "[Expressões](/actions/learn-github-actions/expressions#job-status-check-functions)". ## `jobs..runs-on` @@ -428,7 +507,7 @@ jobs: {% ifversion fpt or ghes > 3.0 or ghae %} ## `jobs..environment` -O ambiente ao qual o trabalho faz referência. Todas as regras de proteção do ambiente têm de ser aprovadas para que um trabalho que faça referência ao ambiente seja enviado a um executor. Para obter mais informações, consulte "[Ambientes](/actions/reference/environments)". +O ambiente ao qual o trabalho faz referência. Todas as regras de proteção do ambiente têm de ser aprovadas para que um trabalho que faça referência ao ambiente seja enviado a um executor. Para obter mais informações, consulte "[Usando ambientes para implantação](/actions/deployment/using-environments-for-deployment)". Você pode fornecer o ambiente apenas como o `nome` do ambiente, ou como um objeto de ambiente com o `nome` e `url`. A URL é mapeada com `environment_url` na API de implantações. Para obter mais informações sobre a API de implantações, consulte "[Implantações](/rest/reference/repos#deployments)". @@ -447,7 +526,7 @@ environment: url: https://github.com ``` -The URL can be an expression and can use any context except for the [`secrets` context](/actions/learn-github-actions/contexts#contexts). For more information about expressions, see "[Expressions](/actions/learn-github-actions/expressions)." +A URL pode ser uma expressão e pode usar qualquer contexto, exceto para o contexto [`segredos`](/actions/learn-github-actions/contexts#contexts). Para obter mais informações sobre expressões, consulte "[Expressões](/actions/learn-github-actions/expressions)". ### Exemplo {% raw %} @@ -463,15 +542,13 @@ environment: {% ifversion fpt or ghae-next or ghes > 3.1 %} ## `jobs..concurrency` -{% data reusables.actions.concurrency-beta %} - {% note %} **Observação:** Quando a concorrência é especificada no nível do trabalho, não se garante a ordem para trabalhos ou execuções que são enfileiradas em 5 minutos uma da outra. {% endnote %} -A moeda garante que apenas um único trabalho ou fluxo de trabalho que usa o mesmo grupo de concorrência seja executado de cada vez. Um grupo de concorrência pode ser qualquer string ou expressão. A expressão pode usar qualquer contexto, exceto para o contexto de `segredos`. For more information about expressions, see "[Expressions](/actions/learn-github-actions/expressions)." +A moeda garante que apenas um único trabalho ou fluxo de trabalho que usa o mesmo grupo de concorrência seja executado de cada vez. Um grupo de concorrência pode ser qualquer string ou expressão. A expressão pode usar qualquer contexto, exceto para o contexto de `segredos`. Para obter mais informações sobre expressões, consulte "[Expressões](/actions/learn-github-actions/expressions)". Você também pode especificar `concorrência` no nível do fluxo de trabalho. Para obter mais informações, consulte [`concorrência`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#concurrency). @@ -555,7 +632,7 @@ jobs: Você pode usar a condicional `if` (se) para evitar que um trabalho seja executado a não ser que determinada condição seja atendida. Você pode usar qualquer contexto e expressão compatível para criar uma condicional. -{% data reusables.github-actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)." +{% data reusables.github-actions.expression-syntax-if %} Para obter mais informações, consulte "[Expressões](/actions/learn-github-actions/expressions)". ## `jobs..steps` @@ -595,7 +672,7 @@ Identificador exclusivo da etapa. Você pode usar `id` para fazer referência à Você pode usar a condicional `if` (se) para evitar que uma etapa trabalho seja executada a não ser que determinada condição seja atendida. Você pode usar qualquer contexto e expressão compatível para criar uma condicional. -{% data reusables.github-actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)." +{% data reusables.github-actions.expression-syntax-if %} Para obter mais informações, consulte "[Expressões](/actions/learn-github-actions/expressions)". ### Exemplo: Usando contextos @@ -610,7 +687,7 @@ steps: ### Exemplo: Usando funções de verificação de status -A função `my backup step` (minha etapa de backup) somente é executada quando houver falha em uma etapa anterior do trabalho. For more information, see "[Expressions](/actions/learn-github-actions/expressions#job-status-check-functions)." +A função `my backup step` (minha etapa de backup) somente é executada quando houver falha em uma etapa anterior do trabalho. Para obter mais informações, consulte "[Expressões](/actions/learn-github-actions/expressions#job-status-check-functions)". ```yaml steps: @@ -656,7 +733,7 @@ steps: `{owner}/{repo}@{ref}` -You can specify a branch, ref, or SHA in a public {% data variables.product.prodname_dotcom %} repository. +É possível especificar um branch, ref, ou SHA em um repositório público de {% data variables.product.prodname_dotcom %}. ```yaml jobs: @@ -800,7 +877,7 @@ Com a palavra-chave `working-directory` (diretório de trabalho), é possível e ### Usar um shell específico -Você pode anular as configurações padrão de shell no sistema operacional do executor usando a palavra-chave `shell`. É possível usar palavras-chave integradas a `shell` ou definir um conjunto personalizado de opções de shell. The shell command that is run internally executes a temporary file that contains the commands specifed in the `run` keyword. +Você pode anular as configurações padrão de shell no sistema operacional do executor usando a palavra-chave `shell`. É possível usar palavras-chave integradas a `shell` ou definir um conjunto personalizado de opções de shell. O comando do shell executado internamente executa um arquivo temporário que contém os comandos especificados na palavra-chave `run`. | Plataforma compatível | Parâmetro `shell` | Descrição | Comando executado internamente | | --------------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- | @@ -964,7 +1041,7 @@ Define variáveis de ambiente para etapas a serem usadas no ambiente do executor {% data reusables.repositories.actions-env-var-note %} -Ações públicas podem especificar variáveis de ambiente esperadas no arquivo LEIAME. Se você está configurando um segredo em uma variável de ambiente, use o contexto `secrets`. For more information, see "[Using environment variables](/actions/automating-your-workflow-with-github-actions/using-environment-variables)" and "[Contexts](/actions/learn-github-actions/contexts)." +Ações públicas podem especificar variáveis de ambiente esperadas no arquivo LEIAME. Se você está configurando um segredo em uma variável de ambiente, use o contexto `secrets`. Para obter mais informações, consulte "[Usando variáveis de ambiente](/actions/automating-your-workflow-with-github-actions/using-environment-variables)" e "[Contextos](/actions/learn-github-actions/contexts)". ### Exemplo @@ -991,7 +1068,7 @@ Número máximo de minutos para executar a etapa antes de interromper o processo Número máximo de minutos para permitir a execução de um trabalho o antes que o {% data variables.product.prodname_dotcom %} o cancele automaticamente. Padrão: 360 -If the timeout exceeds the job execution time limit for the runner, the job will be canceled when the execution time limit is met instead. For more information about job execution time limits, see "[Usage limits, billing, and administration](/actions/reference/usage-limits-billing-and-administration#usage-limits)." +Se o tempo-limite exceder o tempo limite de execução do trabalho para o runner, o trabalho será cancelada quando o tempo limite de execução for atingido. Para obter mais informações sobre limites de tempo de execução do trabalho, consulte "[Limites de uso, cobrança e administração](/actions/reference/usage-limits-billing-and-administration#usage-limits)". ## `jobs..strategy` @@ -1248,7 +1325,7 @@ Opções adicionais de recursos do contêiner Docker. Para obter uma lista de op {% warning %} -**Warning:** The `--network` option is not supported. +**Aviso:** A opção `--network` não é compatível. {% endwarning %} @@ -1344,10 +1421,74 @@ Opções adicionais de recursos do contêiner Docker. Para obter uma lista de op {% warning %} -**Warning:** The `--network` option is not supported. +**Aviso:** A opção `--network` não é compatível. {% endwarning %} +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## `jobs..uses` + +O local e a versão de um arquivo de fluxo de trabalho reutilizável para ser executado como job. + +`{owner}/{repo}/{path}/{filename}@{ref}` + +`{ref}` pode ser um SHA, uma tag de de versão ou um nome de branch. Usar o commit SHA é o mais seguro para a estabilidade e segurança. Para obter mais informações, consulte "[Enrijecimento de segurança para o GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#reusing-third-party-workflows)". + +### Exemplo + +{% data reusables.actions.uses-keyword-example %} + +Para obter mais informações, consulte "[Reutilizando fluxos de trabalho](/actions/learn-github-actions/reusing-workflows)". + +## `jobs..with` + +Quando um trabalho é usado para chamar um fluxo de trabalho reutilizável, você pode usar `com` para fornecer um mapa de entradas que são passadas para o fluxo de trabalho de chamada. + +Qualquer entrada que você passe deve corresponder às especificações de entrada definidas no fluxo de trabalho de chamada. + +Diferentemente de [`jobs..steps[*].with`](#jobsjob_idstepswith), as entradas que você passar com `jobs..with` não estão disponíveis como variáveis de ambiente no fluxo de trabalho de chamada. Ao invés disso, você pode fazer referência às entradas usando o contexto `entrada`. + +### Exemplo + +```yaml +jobs: + call-workflow: + uses: octo-org/example-repo/.github/workflows/called-workflow.yml@main + with: + username: mona +``` + +## `jobs..with.` + +Um par composto de um identificador de string para a entrada e o valor da entrada. O identificador deve corresponder ao nome de uma entrada definida por [`on.workflow_call.inputs.`](/actions/creating-actions/metadata-syntax-for-github-actions#inputsinput_id) no fluxo de trabalho chamado. O tipo de dado do valor deve corresponder ao tipo definido por [`on.workflow_call..type`](#onworkflow_callinput_idtype) no fluxo de trabalho chamado. + +Contextos de expressão permitidos: `github` e `needs`. + +## `jobs..secrets` + +Quando um trabalho é usado para chamar um fluxo de trabalho reutilizável, você pode usar `segredos` para fornecer um mapa de segredos que foram passados para o fluxo de trabalho chamado. + +Qualquer segredo que você passar deve corresponder aos nomes definidos no fluxo de trabalho chamado. + +### Exemplo + +{% raw %} +```yaml +jobs: + call-workflow: + uses: octo-org/example-repo/.github/workflows/called-workflow.yml@main + secrets: + access-token: ${{ secrets.PERSONAL_ACCESS_TOKEN }} +``` +{% endraw %} + +## `jobs..secrets.` + +Um par composto por um identificador string para o segredo e o valor do segredo. O identificador deve corresponder ao nome de um segredo definido por [`on.workflow_call.secrets.`](#onworkflow_callsecretssecret_id) no fluxo de trabalho chamado. + +Contextos de expressão permitidos: `github`, `needs` e `segredos`. +{% endif %} + ## Folha de consulta de filtro padrão Você pode usar caracteres especiais nos filtros de caminhos, branches e tags. diff --git a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md index 5dc822cf83..d4ea6c5ffd 100644 --- a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md +++ b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md @@ -16,8 +16,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## Introdução diff --git a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md index ebff808f1e..1421b8de39 100644 --- a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md +++ b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md @@ -16,8 +16,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## Introdução @@ -73,7 +71,7 @@ Baseado no parâmetro `agendar` (por exemplo, todos os dias à 1:30 UTC), seu fl Você pode visualizar o histórico de execução do fluxo de trabalho para ver a execução deste fluxo de trabalho periodicamente. Para obter mais informações, consulte "[Visualizar histórico de execução de fluxo de trabalho](/actions/managing-workflow-runs/viewing-workflow-run-history)". -This workflow will only label and/or close 30 issues at a time in order to avoid exceeding a rate limit. Você pode definir isso com a configuração de `operations-por-run`. Para obter mais informações, consulte a documentação da ação [`ação/estale`](https://github.com/marketplace/actions/close-stale-issues). +Este fluxo de trabalho só irá etiquetar e/ou fechar 30 problemas de cada vez para evitar exceder um limite de taxa. Você pode definir isso com a configuração de `operations-por-run`. Para obter mais informações, consulte a documentação da ação [`ação/estale`](https://github.com/marketplace/actions/close-stale-issues). ## Próximas etapas diff --git a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md index be13300385..41f0830e97 100644 --- a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md +++ b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md @@ -17,8 +17,6 @@ shortTitle: Adicionar etiqueta ao comentário no problema {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## Introdução diff --git a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/index.md b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/index.md index c8998c1500..f8e8e707cf 100644 --- a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/index.md +++ b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/index.md @@ -1,7 +1,7 @@ --- -title: Managing issues and pull requests -shortTitle: Managing issues and pull requests -intro: 'You can automatically manage your issues and pull requests using {% data variables.product.prodname_actions %} workflows.' +title: Gerenciar problemas e pull requests +shortTitle: Gerenciar problemas e pull requests +intro: 'Você pode gerenciar automaticamente seus problemas e pull requests usando fluxos de trabalho de {% data variables.product.prodname_actions %}.' versions: fpt: '*' ghes: '*' diff --git a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md index 6ea084ff21..ca3b749716 100644 --- a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md +++ b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md @@ -17,8 +17,6 @@ shortTitle: Mover problemas atribuídos {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## Introdução diff --git a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md index 1f4c88c87c..d319939aef 100644 --- a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md +++ b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md @@ -17,8 +17,6 @@ shortTitle: Remover etiqueta ao adicionar cartão {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## Introdução diff --git a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md index b9f533fdc5..ea2041c444 100644 --- a/translations/pt-BR/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md +++ b/translations/pt-BR/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md @@ -16,8 +16,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## Introdução diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md b/translations/pt-BR/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md index 33222b9926..de9fdbaf8d 100644 --- a/translations/pt-BR/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md +++ b/translations/pt-BR/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md @@ -9,7 +9,9 @@ shortTitle: Aprovar execução da bifurcação pública ## Sobre as execuções de fluxo de trabalho a partir de bifurcações públicas -{% data reusables.actions.workflow-run-approve-public-fork %} However, you can configure this behavior for a [repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks), [organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#configuring-required-approval-for-workflows-from-public-forks), or [enterprise](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account#configuring-required-approval-for-workflows-from-public-forks). +{% data reusables.actions.workflow-run-approve-public-fork %} + +You can configure workflow approval requirements for a [repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks), [organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#configuring-required-approval-for-workflows-from-public-forks), or [enterprise](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account#configuring-required-approval-for-workflows-from-public-forks). As execuções de fluxo de trabalho que estão aguardando aprovação por mais de 30 dias são excluídas automaticamente. diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/canceling-a-workflow.md b/translations/pt-BR/content/actions/managing-workflow-runs/canceling-a-workflow.md index 9cf0e45c15..1d09be618e 100644 --- a/translations/pt-BR/content/actions/managing-workflow-runs/canceling-a-workflow.md +++ b/translations/pt-BR/content/actions/managing-workflow-runs/canceling-a-workflow.md @@ -10,7 +10,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.repositories.permissions-statement-write %} diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/deleting-a-workflow-run.md b/translations/pt-BR/content/actions/managing-workflow-runs/deleting-a-workflow-run.md index 36299033f4..dd42b6fcaa 100644 --- a/translations/pt-BR/content/actions/managing-workflow-runs/deleting-a-workflow-run.md +++ b/translations/pt-BR/content/actions/managing-workflow-runs/deleting-a-workflow-run.md @@ -10,7 +10,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.repositories.permissions-statement-write %} diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md b/translations/pt-BR/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md index f259677ac1..3f3325d379 100644 --- a/translations/pt-BR/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md +++ b/translations/pt-BR/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md @@ -11,7 +11,6 @@ shortTitle: Desabilitar & habilitar um fluxo de trabalho {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} Desabilitar um fluxo de trabalho permite que você impeça que um fluxo de trabalho seja acionado sem ter de excluir o arquivo do repositório. Você pode facilmente reabilitar o fluxo de trabalho novamente em {% data variables.product.prodname_dotcom %}. diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md b/translations/pt-BR/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md index 2d3af17cb7..7482bab78a 100644 --- a/translations/pt-BR/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md +++ b/translations/pt-BR/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md @@ -11,9 +11,8 @@ shortTitle: Fazer download dos artefatos do fluxo de trabalho {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% ifversion fpt or ghes > 2.22 or ghae %} Por padrão, {% data variables.product.product_name %} armazena registros de criação por 90 dias e você pode personalizar este período de retenção, dependendo do tipo de repositório. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)."{% endif %} +{% ifversion fpt or ghes > 2.22 or ghae %} Por padrão, {% data variables.product.product_name %} armazena registros de criação por 90 dias e você pode personalizar este período de retenção, dependendo do tipo de repositório. Para obter mais informações, consulte "[Gerenciar 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#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)".{% endif %} {% ifversion ghes = 2.22 %} {% data variables.product.product_name %} armazena registros de criação completos e artefatos por 90 dias.{% endif %} {% data reusables.repositories.permissions-statement-read %} diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/index.md b/translations/pt-BR/content/actions/managing-workflow-runs/index.md index df00a6b3c6..52cbf5562f 100644 --- a/translations/pt-BR/content/actions/managing-workflow-runs/index.md +++ b/translations/pt-BR/content/actions/managing-workflow-runs/index.md @@ -1,7 +1,7 @@ --- title: Gerenciar fluxos de trabalho shortTitle: Gerenciar fluxos de trabalho -intro: 'You can re-run or cancel a workflow, {% ifversion fpt or ghes > 3.0 or ghae %}review deployments, {% endif %}view billable job execution minutes, and download artifacts.' +intro: 'Você pode executar novamente ou cancelar um fluxo de trabalho, {% ifversion fpt or ghes > 3.0 or ghae %}revisar implantações, {% endif %}visualizar minutas de execução de trabalhos faturáveis e fazer o download de artefatos.' redirect_from: - /actions/configuring-and-managing-workflows/managing-a-workflow-run - /articles/managing-a-workflow-run @@ -19,6 +19,7 @@ children: - /approving-workflow-runs-from-public-forks - /reviewing-deployments - /disabling-and-enabling-a-workflow + - /skipping-workflow-runs - /deleting-a-workflow-run - /downloading-workflow-artifacts - /removing-workflow-artifacts @@ -26,5 +27,3 @@ children: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% ifversion fpt or ghes > 3.0 or ghae %}{% endif %} diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/manually-running-a-workflow.md b/translations/pt-BR/content/actions/managing-workflow-runs/manually-running-a-workflow.md index bc890d727d..620e1d3d55 100644 --- a/translations/pt-BR/content/actions/managing-workflow-runs/manually-running-a-workflow.md +++ b/translations/pt-BR/content/actions/managing-workflow-runs/manually-running-a-workflow.md @@ -11,7 +11,6 @@ shortTitle: Executar um fluxo de trabalho manualmente {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Configurar um fluxo de trabalho para ser executado manualmente diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/re-running-a-workflow.md b/translations/pt-BR/content/actions/managing-workflow-runs/re-running-a-workflow.md index 0a78d111b3..78a824e5c0 100644 --- a/translations/pt-BR/content/actions/managing-workflow-runs/re-running-a-workflow.md +++ b/translations/pt-BR/content/actions/managing-workflow-runs/re-running-a-workflow.md @@ -1,6 +1,6 @@ --- title: Reexecutar um fluxo de trabalho -intro: You can re-run an instance of a workflow up to 30 days after the initial run. +intro: Você pode executar novamente uma instância de um fluxo de trabalho até 30 dias após a execução inicial. product: '{% data reusables.gated-features.actions %}' permissions: People with write permissions to a repository can re-run workflows in the repository. versions: @@ -11,9 +11,8 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -Re-running a workflow uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (Git ref) of the original event that triggered the workflow run. You can re-run a workflow up to 30 days after the initial run. +A reexecução de um fluxo de trabalho usa o mesmo `GITHUB_SHA` (commit SHA) e `GITHUB_REF` (Git ref) do evento original que acionou a execução do fluxo de trabalho. Você pode executar novamente um fluxo de trabalho até 30 dias após a execução inicial. {% include tool-switcher %} diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/removing-workflow-artifacts.md b/translations/pt-BR/content/actions/managing-workflow-runs/removing-workflow-artifacts.md index 67994f74e2..ad36091ca1 100644 --- a/translations/pt-BR/content/actions/managing-workflow-runs/removing-workflow-artifacts.md +++ b/translations/pt-BR/content/actions/managing-workflow-runs/removing-workflow-artifacts.md @@ -11,7 +11,6 @@ shortTitle: Remover artefatos de fluxo de trabalho {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Excluir um artefato diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/reviewing-deployments.md b/translations/pt-BR/content/actions/managing-workflow-runs/reviewing-deployments.md index 17468a7204..36dded0142 100644 --- a/translations/pt-BR/content/actions/managing-workflow-runs/reviewing-deployments.md +++ b/translations/pt-BR/content/actions/managing-workflow-runs/reviewing-deployments.md @@ -8,13 +8,12 @@ versions: ghae: '*' --- -{% data reusables.actions.ae-beta %} ## Sobre revisões necessárias nos fluxos de trabalho Os trabalhos que fazem referência a um ambiente configurado com os revisores necessários irão aguardar a aprovação antes de serem iniciados. Enquanto um trabalho está aguardando aprovação, ele tem um status de "Aguardando". Se um trabalho não for aprovado em 30 dias, a execução do fluxo de trabalho será automaticamente cancelada. -Para obter mais informações sobre ambientes e aprovações necessárias, consulte "[Ambientes](/actions/reference/environments). {% ifversion fpt or ghae-next or ghes > 3.1 %} Para obter informações sobre como revisar implantações com a API REST, consulte "[Execuções de fluxo de trabalho](/rest/reference/actions#workflow-runs)."{% endif %} +Para obter mais informações sobre ambientes e aprovações necessárias, consulte "[Usando ambientes para implantação](/actions/deployment/using-environments-for-deployment).{% ifversion fpt or ghae-next or ghes > 3.1 %} Para obter informações sobre como revisar implantações com a API REST, consulte "[Execuções de trabalho](/rest/reference/actions#workflow-runs)."{% endif %} ## Aprovar ou rejeitar um trabalho 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 new file mode 100644 index 0000000000..1692cb1602 --- /dev/null +++ b/translations/pt-BR/content/actions/managing-workflow-runs/skipping-workflow-runs.md @@ -0,0 +1,33 @@ +--- +title: Ignorar execuções de fluxo de trabalho +intro: Você pode ignorar as execuções de fluxo de trabalho acionadas pelos eventos `push` e `pull_request` incluindo um comando na sua mensagem de commit. +product: '{% data reusables.gated-features.actions %}' +versions: + fpt: '*' + ghes: '>=3.0' + ghae: ghae-next +shortTitle: Ignorar execução de fluxo de trabalho +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +Os fluxos de trabalho que seriam acionados usando `on: push` ou `on: pull_request` não serão acionado se você adicionar qualquer uma das strings a seguir para a mensagem de commit em um push ou o commit HEAD de um pull request: + +* `[skip ci]` +* `[ci skip]` +* `[no ci]` +* `[skip actions]` +* `[actions skip]` + +Como alternativa, você pode terminar a mensagem de commit com duas linhas vazias seguidas de `skip-checks: true` ou `skip-checks:true`. + +Você não conseguirá fazer o merge do pull request se o repositório estiver configurado para exigir verificações específicas para passar primeiro. Para permitir que o merge do pull request, você pode fazer o push de um novo commit no pull request sem que a instrução seja ignorada na mensagem do commit. + +{% note %} + +**Observação:** Ignorar instruções só se aplica aos eventos `push` e `pull_request`. Por exemplo, adicionar `[skip ci]` a uma mensagem de commit não impedirá que um fluxo de trabalho que acionou `on : pull_request_target` seja executado. + +{% endnote %} + +Ignorar as instruções só se aplica às execuções do(s) fluxo(s) de trabalho que serão acionadas pelo commit que contém as instruções de para ignorar. Você também pode desabilitar um fluxo de trabalho da execução. Para obter mais informações, consulte "[Desabilitar e habilitar um fluxo de trabalho](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)". diff --git a/translations/pt-BR/content/actions/migrating-to-github-actions/index.md b/translations/pt-BR/content/actions/migrating-to-github-actions/index.md index f8adfd468d..b1055fe085 100644 --- a/translations/pt-BR/content/actions/migrating-to-github-actions/index.md +++ b/translations/pt-BR/content/actions/migrating-to-github-actions/index.md @@ -1,7 +1,7 @@ --- title: Migrar para o GitHub Actions shortTitle: Migrar para o GitHub Actions -intro: 'Learn how to migrate your existing CI/CD workflows to {% data variables.product.prodname_actions %}.' +intro: 'Aprenda como fazer a migração dos seus fluxos de trabalho de CI/CD existentes para {% data variables.product.prodname_actions %}.' versions: fpt: '*' ghes: '*' diff --git a/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md b/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md index b13dc42db4..0ee36a28c0 100644 --- a/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md +++ b/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md @@ -19,7 +19,6 @@ shortTitle: Fazer a migração a partir dos pipelines do Azure {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introdução @@ -204,7 +203,7 @@ jobs:
    - Specify the name of the ref you checked out and analyzed so that the results can be matched to the correct code. For a branch use: refs/heads/BRANCH-NAME, for the head commit of a pull request use refs/pulls/NUMBER/head, or for the {% data variables.product.product_name %}-generated merge commit of a pull request use refs/pulls/NUMBER/merge. + Specify the name of the ref you checked out and analyzed so that the results can be matched to the correct code. For a branch use: refs/heads/BRANCH-NAME, for the head commit of a pull request use refs/pulls/NUMBER/head, or for the {% data variables.product.prodname_dotcom %}-generated merge commit of a pull request use refs/pulls/NUMBER/merge.
    - Specify the SARIF file to load.{% ifversion ghes > 3.0 or ghae-next %} + Specify the SARIF file to load.{% ifversion ghes > 3.0 or ghae %}
    -Ubuntu 16.04[deprecated] - -ubuntu-16.04 - -Deprecated and limited to existing customers only. Migrate to Ubuntu 20.04. For more information, see the blog post. -
    macOS Big Sur 11 diff --git a/translations/ko-KR/data/reusables/github-connect/access-dotcom-and-enterprise.md b/translations/ko-KR/data/reusables/github-connect/access-dotcom-and-enterprise.md index 6b9b37d713..2f22dbfd74 100644 --- a/translations/ko-KR/data/reusables/github-connect/access-dotcom-and-enterprise.md +++ b/translations/ko-KR/data/reusables/github-connect/access-dotcom-and-enterprise.md @@ -1 +1 @@ -1. Sign in to {% data variables.product.product_location_enterprise %} and {% data variables.product.prodname_dotcom_the_website %}. +1. Sign in to {% ifversion ghes %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_ghe_managed %}{% endif %} and {% data variables.product.prodname_dotcom_the_website %}. diff --git a/translations/ko-KR/data/reusables/github-connect/access-profile-settings.md b/translations/ko-KR/data/reusables/github-connect/access-profile-settings.md index c157ad63e1..901722cd34 100644 --- a/translations/ko-KR/data/reusables/github-connect/access-profile-settings.md +++ b/translations/ko-KR/data/reusables/github-connect/access-profile-settings.md @@ -1 +1 @@ -1. On {% data variables.product.product_location_enterprise %}, in the upper-right corner of any page, click your profile photo, then click **Settings**. ![Settings icon in the user bar](/assets/images/help/settings/userbar-account-settings.png) +1. On {% ifversion ghes %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_ghe_managed %}{% endif %}, in the upper-right corner of any page, click your profile photo, then click **Settings**. ![Settings icon in the user bar](/assets/images/help/settings/userbar-account-settings.png) diff --git a/translations/ko-KR/data/reusables/github-connect/authorize-connection.md b/translations/ko-KR/data/reusables/github-connect/authorize-connection.md index def6828956..3f3f26a09f 100644 --- a/translations/ko-KR/data/reusables/github-connect/authorize-connection.md +++ b/translations/ko-KR/data/reusables/github-connect/authorize-connection.md @@ -1 +1,7 @@ -1. Review the resources that {% data variables.product.prodname_ghe_server %} will access from your {% data variables.product.prodname_dotcom_the_website %} account, then click **Authorize**. ![Authorize connection between GitHub Enterprise Server and GitHub.com](/assets/images/help/settings/authorize-ghe-to-connect-to-dotcom.png) +1. Review the resources that +{% data variables.product.product_name %} will access from your {% data variables.product.prodname_dotcom_the_website %} account, then click **Authorize**. +{% ifversion ghes %} + ![Authorize connection between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_dotcom_the_website %}](/assets/images/help/settings/authorize-ghe-to-connect-to-dotcom.png) +{% elsif ghae %} + ![Authorize connection between {% data variables.product.prodname_ghe_managed %} and {% data variables.product.prodname_dotcom_the_website %}](/assets/images/enterprise/github-ae/settings/authorize-ghae-to-connect-to-dotcom.png) +{% endif %} diff --git a/translations/ko-KR/data/reusables/github-connect/beta.md b/translations/ko-KR/data/reusables/github-connect/beta.md new file mode 100644 index 0000000000..991a98d3d6 --- /dev/null +++ b/translations/ko-KR/data/reusables/github-connect/beta.md @@ -0,0 +1,7 @@ +{% ifversion ghae-next %} +{% note %} + +**Note:** {% data variables.product.prodname_github_connect %} for {% data variables.product.product_name %} is currently in beta and subject to change. + +{% endnote %} +{% endif %} diff --git a/translations/ko-KR/data/reusables/github-connect/connect-dotcom-and-enterprise.md b/translations/ko-KR/data/reusables/github-connect/connect-dotcom-and-enterprise.md index b639ddaf90..c05d2afdae 100644 --- a/translations/ko-KR/data/reusables/github-connect/connect-dotcom-and-enterprise.md +++ b/translations/ko-KR/data/reusables/github-connect/connect-dotcom-and-enterprise.md @@ -1 +1,6 @@ -1. Click **Connect to {% data variables.product.prodname_dotcom_the_website %}**. ![Connect to GitHub.com from GitHub Enterprise Server settings](/assets/images/help/settings/github.com_end_user_connection.png) +1. Click **Connect to {% data variables.product.prodname_dotcom_the_website %}**. +{% ifversion ghes %} + ![Connect to GitHub.com from GitHub Enterprise Server settings](/assets/images/help/settings/github.com_end_user_connection.png) +{% else %} + ![Connect to GitHub.com from GitHub AE settings](/assets/images/enterprise/github-ae/settings/github.com-end-user-connection.png) +{% endif %} diff --git a/translations/ko-KR/data/reusables/github-connect/send-contribution-counts-to-githubcom.md b/translations/ko-KR/data/reusables/github-connect/send-contribution-counts-to-githubcom.md new file mode 100644 index 0000000000..8004aa7150 --- /dev/null +++ b/translations/ko-KR/data/reusables/github-connect/send-contribution-counts-to-githubcom.md @@ -0,0 +1 @@ +1. Under "Contributions", select **Send my contribution counts to {% data variables.product.prodname_dotcom_the_website %}**, then click **Update contributions.** ![Send contributions checkbox and update contributions button](/assets/images/help/settings/send-and-update-contributions.png) diff --git a/translations/ko-KR/data/reusables/github-connect/sync-frequency.md b/translations/ko-KR/data/reusables/github-connect/sync-frequency.md index 93f01ae837..75a4fd8218 100644 --- a/translations/ko-KR/data/reusables/github-connect/sync-frequency.md +++ b/translations/ko-KR/data/reusables/github-connect/sync-frequency.md @@ -1 +1 @@ -{% data variables.product.prodname_ghe_server %} sends updates hourly. +{% data variables.product.product_name %} sends updates hourly. diff --git a/translations/ko-KR/data/reusables/notifications-v2/custom-notification-types.md b/translations/ko-KR/data/reusables/notifications-v2/custom-notification-types.md index d29d7447d4..2299c52284 100644 --- a/translations/ko-KR/data/reusables/notifications-v2/custom-notification-types.md +++ b/translations/ko-KR/data/reusables/notifications-v2/custom-notification-types.md @@ -1,2 +1,2 @@ {%- ifversion fpt or ghes > 3.1 or ghae-issue-4910 %}issues, pulls requests, releases, security alerts, or discussions{% endif %} -{%- ifversion ghes = 3.1 or ghae-next %}issues, pull requests, releases, or discussions{% endif %} +{%- ifversion ghes = 3.1 %}issues, pull requests, releases, or discussions{% endif %} diff --git a/translations/ko-KR/data/reusables/pages/about-private-publishing.md b/translations/ko-KR/data/reusables/pages/about-private-publishing.md index f1f13531ce..7d6708b21e 100644 --- a/translations/ko-KR/data/reusables/pages/about-private-publishing.md +++ b/translations/ko-KR/data/reusables/pages/about-private-publishing.md @@ -1 +1 @@ -If your project site is published from a private or internal repository owned by an organization using {% data variables.product.prodname_ghe_cloud %}, you can manage access control for the site. +If your project site is published from a private or internal repository owned by an organization using {% data variables.product.prodname_ghe_cloud %}, you can manage access control for the site. In an {% data variables.product.prodname_emu_enterprise %}, all {% data variables.product.prodname_pages %} sites are privately published. diff --git a/translations/ko-KR/data/reusables/repositories/auto-gen-release-public-beta.md b/translations/ko-KR/data/reusables/repositories/auto-gen-release-public-beta.md new file mode 100644 index 0000000000..1271ce25e0 --- /dev/null +++ b/translations/ko-KR/data/reusables/repositories/auto-gen-release-public-beta.md @@ -0,0 +1 @@ +Automatically generated release notes are currently in public beta and subject to change. diff --git a/translations/ko-KR/data/reusables/repositories/disabling-markdown-rendering.md b/translations/ko-KR/data/reusables/repositories/disabling-markdown-rendering.md new file mode 100644 index 0000000000..86254f64ec --- /dev/null +++ b/translations/ko-KR/data/reusables/repositories/disabling-markdown-rendering.md @@ -0,0 +1,5 @@ +When viewing a Markdown file, you can click {% octicon "code" aria-label="The code icon" %} at the top of the file to disable Markdown rendering and view the file's source instead. + +![Display Markdown as source](/assets/images/help/writing/display-markdown-as-source.png) + +Disabling Markdown rendering enables you to use source view features, such as line linking, which is not possible when viewing rendered Markdown files. diff --git a/translations/ko-KR/data/reusables/repositories/request-security-advisory-cve-id.md b/translations/ko-KR/data/reusables/repositories/request-security-advisory-cve-id.md index 72b4465e0a..64c1f4bb0d 100644 --- a/translations/ko-KR/data/reusables/repositories/request-security-advisory-cve-id.md +++ b/translations/ko-KR/data/reusables/repositories/request-security-advisory-cve-id.md @@ -1,5 +1,3 @@ -If you don't already have a CVE identification number for the security vulnerability in your project, you can request a CVE identification number from {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_dotcom %} usually reviews the request within 72 hours. Requesting a CVE identification number doesn't make your security advisory public. If your security advisory is eligible for a CVE, {% data variables.product.prodname_dotcom %} will reserve a CVE identification number for your advisory. We'll then publish the CVE details after you publish the security advisory. +If you want a CVE identification number for the security vulnerability in your project, and don't already have one, you can request a CVE identification number from {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_dotcom %} usually reviews the request within 72 hours. Requesting a CVE identification number doesn't make your security advisory public. If your security advisory is eligible for a CVE, {% data variables.product.prodname_dotcom %} will reserve a CVE identification number for your advisory. We'll then publish the CVE details after you make your security advisory public. Anyone with admin permissions to a security advisory can request a CVE identification number. -If you already have a CVE you want to use, for example, if you use a CNA other than {% data variables.product.prodname_dotcom %}, add it to the security advisory form. This may happen, for example, if you want to get the advisory consistent with other communications you plan to send out at publication time. - -If an advisory form doesn't have a CVE, we will request a CVE for you when you publish the advisory. +If you already have a CVE you want to use, for example, if you use a CVE Numbering Authority (CNA) other than {% data variables.product.prodname_dotcom %}, add the CVE to the security advisory form. This may happen, for example, if you want to get the advisory consistent with other communications you plan to send out at publication time. {% data variables.product.prodname_dotcom %} cannot assign CVEs to your project if it is covered by another CNA. \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/repositories/sidebar-issues.md b/translations/ko-KR/data/reusables/repositories/sidebar-issues.md index 43cc9f72ca..60d381e767 100644 --- a/translations/ko-KR/data/reusables/repositories/sidebar-issues.md +++ b/translations/ko-KR/data/reusables/repositories/sidebar-issues.md @@ -1,5 +1,5 @@ 2. 리포지토리 이름 아래에서 클릭하십시오. {% octicon "issue-opened" aria-label="The issues icon" %} **Issues**. - {% ifversion fpt or ghes > 3.1 or ghae-issue-4483 %} + {% ifversion fpt or ghes > 3.1 or ghae-next %} ![Issues tab](/assets/images/help/repository/repo-tabs-issues.png){% else %} ![Issues tab](/assets/images/enterprise/3.1/help/repository/repo-tabs-issues.png){% endif %} diff --git a/translations/ko-KR/data/reusables/repositories/sidebar-pr.md b/translations/ko-KR/data/reusables/repositories/sidebar-pr.md index 0cead806a3..c2eea89273 100644 --- a/translations/ko-KR/data/reusables/repositories/sidebar-pr.md +++ b/translations/ko-KR/data/reusables/repositories/sidebar-pr.md @@ -1,5 +1,5 @@ 1. 리포지토리 이름 아래에서 클릭하십시오. {% octicon "git-pull-request" aria-label="The pull request icon" %} **Pull requests**. - {% ifversion fpt or ghes > 3.1 or ghae-issue-4483 %} + {% ifversion fpt or ghes > 3.1 or ghae-next %} ![Issues and pull requests tab selection](/assets/images/help/repository/repo-tabs-pull-requests.png){% else %} ![Issues tab](/assets/images/enterprise/3.1/help/repository/repo-tabs-pull-requests.png){% endif %} diff --git a/translations/ko-KR/data/reusables/repositories/workflow-notifications.md b/translations/ko-KR/data/reusables/repositories/workflow-notifications.md index c1399976e8..d9f2a271db 100644 --- a/translations/ko-KR/data/reusables/repositories/workflow-notifications.md +++ b/translations/ko-KR/data/reusables/repositories/workflow-notifications.md @@ -1,4 +1,4 @@ -If you enable email or web notifications for {% data variables.product.prodname_actions %}, you'll receive a notification when any workflow runs that you've triggered have completed. The notification will include the workflow run's status (including successful, failed, neutral, and canceled runs). You can also choose to receive a notification only when a workflow run has failed. +If you enable email or web notifications for {% data variables.product.prodname_actions %}, you'll receive a notification when any workflow runs that you've triggered have completed. The notification will include the workflow run's status (including successful, failed, neutral, and canceled runs). You can also choose to receive a notification only when a workflow run has failed. For more information about enabling or disabling notifications, see "[About notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)." Notifications for scheduled workflows are sent to the user who initially created the workflow. If a different user updates the cron syntax in the workflow file, subsequent notifications will be sent to that user instead.{% ifversion fpt or ghes > 2.22 %} If a scheduled workflow is disabled and then re-enabled, notifications will be sent to the user who re-enabled the workflow rather than the user who last modified the cron syntax.{% endif %} diff --git a/translations/ko-KR/data/reusables/saml/about-linked-identities.md b/translations/ko-KR/data/reusables/saml/about-linked-identities.md index f879d16402..25747fe629 100644 --- a/translations/ko-KR/data/reusables/saml/about-linked-identities.md +++ b/translations/ko-KR/data/reusables/saml/about-linked-identities.md @@ -1,3 +1,3 @@ -You can view the single sign-on identity that a member has linked to their {% data variables.product.product_name %} account. When available, the entry will include SCIM data. For more information, see "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)." +You can view the single sign-on identity that a member has linked to their {% data variables.product.product_name %} account. If a member links the wrong identity to their {% data variables.product.product_name %} account, you can revoke the linked identity to allow the member to try again. diff --git a/translations/ko-KR/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/ko-KR/data/reusables/secret-scanning/partner-secret-list-private-repo.md index 7bb265bee2..9e6a06ebd2 100644 --- a/translations/ko-KR/data/reusables/secret-scanning/partner-secret-list-private-repo.md +++ b/translations/ko-KR/data/reusables/secret-scanning/partner-secret-list-private-repo.md @@ -1,7 +1,7 @@ | Provider | Supported secret | API slug | | -------- | ---------------- | -------- | | | | | -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Adafruit IO | Adafruit IO Key | adafruit_io_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Adobe | Adobe Device Token | adobe_device_token{% endif %} @@ -11,73 +11,73 @@ Adobe | Adobe Service Token | adobe_service_token{% endif %} Adobe | Adobe Short-Lived Access Token | adobe_short_lived_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Adobe | Adobe JSON Web Token | adobe_jwt{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Alibaba Cloud | Alibaba Cloud Access Key ID | alibaba_cloud_access_key_id{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Alibaba Cloud | Alibaba Cloud Access Key Secret | alibaba_cloud_access_key_secret{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Amazon Web Services (AWS) | Amazon AWS Access Key ID | aws_access_key_id{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Amazon Web Services (AWS) | Amazon AWS Secret Access Key | aws_secret_access_key{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Amazon Web Services (AWS) | Amazon AWS Session Token | aws_session_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Amazon Web Services (AWS) | Amazon AWS Temporary Access Key ID | aws_temporary_access_key_id{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Asana | Asana Personal Access Token | asana_personal_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Atlassian | Atlassian API Token | atlassian_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Atlassian | Atlassian JSON Web Token | atlassian_jwt{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Atlassian | Bitbucket Server Personal Access Token | bitbucket_server_personal_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Azure | Azure SAS Token | azure_sas_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Azure | Azure Service Management Certificate | azure_management_certificate{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Azure | Azure SQL Connection String | azure_sql_connection_string{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Azure | Azure Storage Account Key | azure_storage_account_key{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Beamer | Beamer API Key | beamer_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Checkout.com | Checkout.com Production Secret Key | checkout_production_secret_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Checkout.com | Checkout.com Test Secret Key | checkout_test_secret_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Clojars | Clojars Deploy Token | clojars_deploy_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} CloudBees CodeShip | CloudBees CodeShip Credential | codeship_credential{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Contentful | Contentful Personal Access Token | contentful_personal_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Databricks | Databricks Access Token | databricks_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Discord | Discord Bot Token | discord_bot_token{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Doppler | Doppler Personal Token | doppler_personal_token{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Doppler | Doppler Service Token | doppler_service_token{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Doppler | Doppler CLI Token | doppler_cli_token{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Doppler | Doppler SCIM Token | doppler_scim_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Doppler | Doppler Audit Token | doppler_audit_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Dropbox | Dropbox Access Token | dropbox_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Dropbox | Dropbox Short Lived Access Token | dropbox_short_lived_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Duffel | Duffel Live Access Token | duffel_live_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Duffel | Duffel Test Access Token | duffel_test_access_token{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Dynatrace | Dynatrace Access Token | dynatrace_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Dynatrace | Dynatrace Internal Token | dynatrace_internal_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} EasyPost | EasyPost Production API Key | easypost_production_api_key{% endif %} @@ -87,17 +87,17 @@ EasyPost | EasyPost Test API Key | easypost_test_api_key{% endif %} Facebook | Facebook Access Token | facebook_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Fastly | Fastly API Token | fastly_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Finicity | Finicity App Key | finicity_app_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Flutterwave | Flutterwave Live API Secret Key | flutterwave_live_api_secret_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Flutterwave | Flutterwave Test API Secret Key | flutterwave_test_api_secret_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Frame.io | Frame.io JSON Web Token | frameio_jwt{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Frame.io| Frame.io Developer Token | frameio_developer_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} FullStory | FullStory API Key | fullstory_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} GitHub | GitHub Personal Access Token | github_personal_access_token{% endif %} @@ -107,29 +107,29 @@ GitHub | GitHub OAuth Access Token | github_oauth_access_token{% endif %} GitHub | GitHub Refresh Token | github_refresh_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} GitHub | GitHub App Installation Access Token | github_app_installation_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} GitHub | GitHub SSH Private Key | github_ssh_private_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} GoCardless | GoCardless Live Access Token | gocardless_live_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} GoCardless | GoCardless Sandbox Access Token | gocardless_sandbox_access_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Google | Firebase Cloud Messaging Server Key | firebase_cloud_messaging_server_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Google | Google API Key | google_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Google | Google Cloud Private Key ID | google_cloud_private_key_id{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Google | Google Cloud Storage Access Key Secret | google_cloud_storage_access_key_secret{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Google | Google Cloud Storage Service Account Access Key ID | google_cloud_storage_service_account_access_key_id{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Google | Google Cloud Storage User Access Key ID | google_cloud_storage_user_access_key_id{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Grafana | Grafana API Key | grafana_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Hashicorp Terraform | Terraform Cloud / Enterprise API Token | terraform_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Hubspot | Hubspot API Key | hubspot_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Intercom | Intercom Access Token | intercom_access_token{% endif %} @@ -137,9 +137,9 @@ Intercom | Intercom Access Token | intercom_access_token{% endif %} Ionic | Ionic Personal Access Token | ionic_personal_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Ionic | Ionic Refresh Token | ionic_refresh_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} JFrog | JFrog Platform Access Token | jfrog_platform_access_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} JFrog | JFrog Platform API Key | jfrog_platform_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Linear | Linear API Key | linear_api_key{% endif %} @@ -149,15 +149,23 @@ Linear | Linear OAuth Access Token | linear_oauth_access_token{% endif %} Lob | Lob Live API Key | lob_live_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Lob | Lob Test API Key | lob_test_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Mailchimp | Mailchimp API Key | mailchimp_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Mailgun | Mailgun API Key | mailgun_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} MessageBird | MessageBird API Key | messagebird_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} +New Relic | New Relic Personal API Key | new_relic_personal_api_key{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +New Relic | New Relic REST API Key | new_relic_rest_api_key{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +New Relic | New Relic Insights Query Key | new_relic_insights_query_key{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +New Relic | New Relic License Key | new_relic_license_key{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} npm | npm Access Token | npm_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} NuGet | NuGet API Key | nuget_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Onfido | Onfido Live API Token | onfido_live_api_token{% endif %} @@ -165,75 +173,75 @@ Onfido | Onfido Live API Token | onfido_live_api_token{% endif %} Onfido | Onfido Sandbox API Token | onfido_sandbox_api_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} OpenAI | OpenAI API Key | openai_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Palantir | Palantir JSON Web Token | palantir_jwt{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} PlanetScale | PlanetScale Database Password | planetscale_database_password{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} PlanetScale | PlanetScale OAuth Token | planetscale_oauth_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} PlanetScale | PlanetScale Service Token | planetscale_service_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Plivo | Plivo Auth ID | plivo_auth_id{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Plivo | Plivo Auth Token | plivo_auth_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Postman | Postman API Key | postman_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Proctorio | Proctorio Consumer Key | proctorio_consumer_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Proctorio | Proctorio Linkage Key | proctorio_linkage_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Proctorio | Proctorio Registration Key | proctorio_registration_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Proctorio | Proctorio Secret Key | proctorio_secret_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Pulumi | Pulumi Access Token | pulumi_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} PyPI | PyPI API Token | pypi_api_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} RubyGems | RubyGems API Key | rubygems_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Samsara | Samsara API Token | samsara_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Samsara | Samsara OAuth Access Token | samsara_oauth_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} SendGrid | SendGrid API Key | sendgrid_api_key{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Sendinblue | Sendinblue API Key | sendinblue_api_key{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Sendinblue | Sendinblue SMTP Key | sendinblue_smtp_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Shippo | Shippo Live API Token | shippo_live_api_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Shippo | Shippo Test API Token | shippo_test_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Shopify | Shopify App Shared Secret | shopify_app_shared_secret{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Shopify | Shopify Access Token | shopify_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Shopify | Shopify Custom App Access Token | shopify_custom_app_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Shopify | Shopify Private App Password | shopify_private_app_password{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Slack | Slack API Token | slack_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Slack | Slack Incoming Webhook URL | slack_incoming_webhook_url{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Slack | Slack Workflow Webhook URL | slack_workflow_webhook_url{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} SSLMate | SSLMate API Key | sslmate_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} SSLMate | SSLMate Cluster Secret | sslmate_cluster_secret{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Stripe | Stripe API Key | stripe_api_key{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Stripe | Stripe Live API Secret Key | stripe_live_secret_key{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Stripe | Stripe Test API Secret Key | stripe_test_secret_key{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Stripe | Stripe Live API Restricted Key | stripe_live_restricted_key{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Stripe | Stripe Test API Restricted Key | stripe_test_restricted_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Stripe | Stripe Webhook Signing Secret | stripe_webhook_signing_secret{% endif %} @@ -241,9 +249,9 @@ Stripe | Stripe Webhook Signing Secret | stripe_webhook_signing_secret{% endif % Tableau | Tableau Personal Access Token | tableau_personal_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Telegram | Telegram Bot Token | telegram_bot_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Tencent Cloud | Tencent Cloud Secret ID | tencent_cloud_secret_id{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Twilio | Twilio Account String Identifier | twilio_account_sid{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Twilio | Twilio API Key | twilio_api_key{% endif %} diff --git a/translations/ko-KR/data/reusables/sponsors/add-welcome-message.md b/translations/ko-KR/data/reusables/sponsors/add-welcome-message.md new file mode 100644 index 0000000000..8962236ad1 --- /dev/null +++ b/translations/ko-KR/data/reusables/sponsors/add-welcome-message.md @@ -0,0 +1 @@ +1. Optionally, type a welcome message for the tier. ![Add welcome message](/assets/images/help/sponsors/add-a-welcome-message.png) \ No newline at end of file diff --git a/translations/ko-KR/data/reusables/sponsors/tier-details.md b/translations/ko-KR/data/reusables/sponsors/tier-details.md index 7cd63f54a6..fe2189aabf 100644 --- a/translations/ko-KR/data/reusables/sponsors/tier-details.md +++ b/translations/ko-KR/data/reusables/sponsors/tier-details.md @@ -1,4 +1,4 @@ -You can create up to 10 one-time sponsorship tiers and 10 monthly tiers for sponsors to choose from. Each tier has its own one-time or monthly payment amount in US dollars, and you can choose to enable tiers for custom amounts. In addition, you can choose to enable tiers for custom amounts (monthly and one-time). +You can create up to 10 one-time sponsorship tiers and 10 monthly tiers for sponsors to choose from. Each tier has its own one-time or monthly payment amount in US dollars, and you can choose to enable tiers for custom amounts. In addition, you can choose to enable tiers for custom amounts (monthly and one-time). You can customize the rewards for each tier. For example, rewards for a tier could include: - Early access to new versions @@ -7,4 +7,6 @@ You can customize the rewards for each tier. For example, rewards for a tier cou - Weekly newsletter updates - Other rewards your sponsors would enjoy ✨ +You can include a welcome message with information about accessing or receiving rewards, which will be visible after payment and in the welcome email. + Once you have published a tier, you cannot edit the price of that tier. Instead, you must retire the tier and create a new tier. Existing sponsors will remain on the retired tier until they change their sponsorship tier, cancel their sponsorship, or their one-time sponsorship period expires. diff --git a/translations/ko-KR/data/reusables/ssh/add-ssh-key-to-ssh-agent-commandline.md b/translations/ko-KR/data/reusables/ssh/add-ssh-key-to-ssh-agent-commandline.md index 415f86736d..9bed61119b 100644 --- a/translations/ko-KR/data/reusables/ssh/add-ssh-key-to-ssh-agent-commandline.md +++ b/translations/ko-KR/data/reusables/ssh/add-ssh-key-to-ssh-agent-commandline.md @@ -1,3 +1,3 @@ ```shell -$ ssh-add ~/.ssh/id_ed25519 +$ ssh-add ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %} ``` diff --git a/translations/ko-KR/data/reusables/ssh/add-ssh-key-to-ssh-agent.md b/translations/ko-KR/data/reusables/ssh/add-ssh-key-to-ssh-agent.md index fb1ca5ec34..43243b9f14 100644 --- a/translations/ko-KR/data/reusables/ssh/add-ssh-key-to-ssh-agent.md +++ b/translations/ko-KR/data/reusables/ssh/add-ssh-key-to-ssh-agent.md @@ -1 +1 @@ -If you created your key with a different name, or if you are adding an existing key that has a different name, replace *id_ed25519* in the command with the name of your private key file. +If you created your key with a different name, or if you are adding an existing key that has a different name, replace *id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}* in the command with the name of your private key file. diff --git a/translations/ko-KR/data/reusables/user_settings/generate_new_token.md b/translations/ko-KR/data/reusables/user_settings/generate_new_token.md new file mode 100644 index 0000000000..adf9fe1f14 --- /dev/null +++ b/translations/ko-KR/data/reusables/user_settings/generate_new_token.md @@ -0,0 +1 @@ +1. Click **Generate new token**. ![Generate new token button](/assets/images/help/settings/generate_new_token.png) \ No newline at end of file diff --git a/translations/ko-KR/data/ui.yml b/translations/ko-KR/data/ui.yml index 90faeeb4c1..7abe348660 100644 --- a/translations/ko-KR/data/ui.yml +++ b/translations/ko-KR/data/ui.yml @@ -30,9 +30,10 @@ toc: guides: 안내서 whats_new: What's new pages: - article_version: '문서 버전:' + article_version: '문서 버전' miniToc: 기사 내용 contributor_callout: This article is contributed and maintained by + all_enterprise_releases: All Enterprise releases errors: oops: 이런! something_went_wrong: 뭔가 잘못된 것 같습니다. @@ -155,13 +156,17 @@ product_sublanding: learning_paths_desc: Learning paths are a collection of guides that help you master a particular subject. guides: '{{ productMap[currentProduct].name }} guides' more_guides: more guides - no_result: Sorry, there are no guides that match your filter. load_more: Load more guides all_guides: 'All {{ productMap[currentProduct].name }} guides' + filter_instructions: Filter the guide list using these controls filters: type: 유형 topic: Topic all: All + guides_found: + multiple: '{n} guides found' + one: 1 guide found + none: No guides found guide_types: overview: 개요 quick_start: Quickstart diff --git a/translations/ko-KR/data/variables/product.yml b/translations/ko-KR/data/variables/product.yml index 6ff344291b..b2af1814bd 100644 --- a/translations/ko-KR/data/variables/product.yml +++ b/translations/ko-KR/data/variables/product.yml @@ -76,6 +76,14 @@ prodname_actions: 'GitHub Actions' prodname_debug: 'GitHub Debug' #GitHub Discussions prodname_discussions: 'GitHub Discussions' +#GitHub Enterprise Managed Users +prodname_emu_idp_application: 'GitHub Enterprise Managed User' +prodname_emus: 'Enterprise Managed Users' +prodname_managed_user: 'managed user' +prodname_managed_users: 'managed users' +prodname_managed_users_caps: 'Managed users' +prodname_emu_enterprise: 'enterprise with managed users' +prodname_emu_org: 'organization with managed users' #GitHub Issues prodname_github_issues: 'GitHub Issues' #GitHub Packages @@ -94,6 +102,7 @@ prodname_security_center: 'Security Center' #Codespaces prodname_codespaces: 'Codespaces' prodname_github_codespaces: 'GitHub Codespaces' +prodname_serverless: 'web-based editor' #GitHub resources: blog, jobs, Learning Lab prodname_gcf: 'GitHub Community Support' prodname_blog: 'the GitHub Blog' @@ -135,6 +144,8 @@ prodname_dependabot_version_updates: 'Dependabot version updates' #GitHub Archive Program prodname_archive: 'GitHub Archive Program' prodname_arctic_vault: 'Arctic Code Vault' +#GitHub Copilot +prodname_copilot: 'GitHub Copilot' #Links product_url: >- {% ifversion fpt %}github.com{% else %}[hostname]{% endif %} diff --git a/translations/ko-KR/data/variables/release_candidate.yml b/translations/ko-KR/data/variables/release_candidate.yml index e6ddf079ac..ec65ef6f94 100644 --- a/translations/ko-KR/data/variables/release_candidate.yml +++ b/translations/ko-KR/data/variables/release_candidate.yml @@ -1,2 +1,2 @@ --- -version: enterprise-server@3.2 +version: '' diff --git a/translations/pt-BR/content/account-and-profile/index.md b/translations/pt-BR/content/account-and-profile/index.md index 795617d05b..e7ebaae44c 100644 --- a/translations/pt-BR/content/account-and-profile/index.md +++ b/translations/pt-BR/content/account-and-profile/index.md @@ -1,7 +1,7 @@ --- -title: Your account and profile on GitHub -shortTitle: Account and profile -intro: 'Make {% data variables.product.product_name %} work best for you by adjusting the settings for your user account, personalizing your profile page, and managing the notifications you receive for activity on {% data variables.product.prodname_dotcom %}.' +title: Sua conta e seu perfil no GitHub +shortTitle: Conta e perfil +intro: 'Faça {% data variables.product.product_name %} funcionar melhor para você, ajustando as configurações para sua conta de usuário, personalizando a página do seu perfil e gerenciando as notificações que você recebe para atividades em {% data variables.product.prodname_dotcom %}.' introLinks: quickstart: /get-started/onboarding/getting-started-with-your-github-account featuredLinks: diff --git a/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md b/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md index 86f24708a6..5d39a0e532 100644 --- a/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md +++ b/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md @@ -45,7 +45,7 @@ Ao cancelar a assinatura de notificações em sua caixa de entrada, elas desapar {% data reusables.notifications.access_notifications %} 1. Na caixa de entrada de notificações, selecione as notificações das quais você deseja cancelar sua assinatura. -2. Use o menu suspenso **selecionado** {% octicon "triangle-down" aria-label="The down triangle icon" %} para clicar em **Cancelar inscrição.** ![Cancele a assinatura na caixa de entrada principal](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png) +2. Clique em **Cancelar assinatura.** ![Cancele a assinatura na caixa de entrada principal](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png) ## Cancelar assinatura de notificações na página de assinaturas @@ -61,13 +61,12 @@ Quando você deixa de inspecionar um repositório, você cancela sua assinatura {% data reusables.notifications.access_notifications %} 1. Na barra lateral esquerda, na lista de repositórios, use o menu suspenso "Gerenciar notificações" para clicar em **Inspecionar repositórios**. ![Gerenciar as opções do menu suspenso notificações](/assets/images/help/notifications-v2/manage-notifications-options.png) 2. Na página de repositórios inspecionados, depois de ter avaliado os repositórios que você está inspecionando, escolha se deseja: - {% ifversion ghae or ghes < 3.1 %} - - Deixar de inspecionar um repositório - - Apenas inspecione versões para um repositório - - Ignorar todas as notificações de um repositório - {% endif %} {% ifversion fpt or ghes > 3.0 or ghae-next %} - Deixar de inspecionar um repositório - Ignorar todas as notificações de um repositório - Personalize os tipos de eventos que você recebe notificações para ({% data reusables.notifications-v2.custom-notification-types %}, se habilitado) + {% else %} + - Deixar de inspecionar um repositório + - Apenas inspecione versões para um repositório + - Ignorar todas as notificações de um repositório {% endif %} diff --git a/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md b/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md index 37ee82c271..6baf1b42ec 100644 --- a/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md +++ b/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md @@ -70,10 +70,10 @@ Muitas pessoas esquecem os repositórios que eles escolheram inspecionar no pass 1. Na barra lateral esquerda, na lista de repositórios, use o menu suspenso "Gerenciar notificações" e clique em **Repositórios inspecionados**. ![Gerenciar as opções do menu suspenso notificações](/assets/images/help/notifications-v2/manage-notifications-options.png) 2. Avalie os repositórios que você está inspecionando e decida se suas atualizações ainda são relevantes e úteis. Quando você inspeciona um repositório, você será notificado de todas as conversas desse repositório. -{% ifversion ghae or ghes < 3.1 %} - ![Página de notificações inspecionadas](/assets/images/help/notifications-v2/watched-notifications.png) -{% elsif fpt or ghes > 3.0 or ghae-next %} +{% ifversion fpt or ghes > 3.0 or ghae-next %} ![Página de notificações inspecionadas](/assets/images/help/notifications-v2/watched-notifications-custom.png) +{% else %} + ![Página de notificações inspecionadas](/assets/images/help/notifications-v2/watched-notifications.png) {% endif %} {% tip %} diff --git a/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md b/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md index d71873359c..5ae76daf2f 100644 --- a/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md +++ b/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md @@ -29,7 +29,7 @@ Você pode optar por assinar notificações para: - Uma conversa em um problema específico, pull request ou gist. - Todas as atividades em um repositório ou em uma discussão em equipe. - Atividade CI, como o status de fluxos de trabalho nos repositórios configurados com {% data variables.product.prodname_actions %}. {% ifversion fpt or ghes > 3.0 or ghae-next %} -- Repositório {% data reusables.notifications-v2.custom-notification-types %} (se habilitado). {% elsif ghae or ghes %} +- Repositório {% data reusables.notifications-v2.custom-notification-types %} (se habilitado).{% else %} - Versões em um repositório.{% endif %} Você também pode optar por assistir automaticamente todos os repositórios aos quais você tem acesso de push, exceto as bifurcações. É possível assistir qualquer outro repositório ao qual você tenha acesso manualmente clicando em **Watch** (Assistir). 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 5521ab2aab..d984ba13d6 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 @@ -70,12 +70,14 @@ As notificações de e-mail também permitem flexibilidade com os tipos de notif Quando você inspeciona um repositório, você assina atualizações de atividade nesse repositório. Da mesma forma, quando você inspeciona as discussões de uma equipe específica, você está inscrito em todas as atualizações de conversa na página daquela equipe. Para obter mais informações, consulte "[Sobre discussões de equipe](/organizations/collaborating-with-your-team/about-team-discussions)". Para ver repositórios que você está inspecionando, acesse a sua [página de inspeção](https://github.com/watching). Para obter mais informações, consulte "[Gerenciando assinaturas e notificações do GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)". + {% ifversion ghae or ghes < 3.1 %} ### Configurar notificações {% endif %} -É possível configurar as notificações para um repositório na página do repositório ou na página de inspeção.{% ifversion ghae or ghes < 3.1 %} Você pode optar por receber apenas notificações de versões em um repositório ou ignorar todas as notificações de um repositório.{% endif %} +É possível configurar as notificações para um repositório na página do repositório ou na página de inspeção.{% ifversion ghes < 3.1 %} Você pode optar por receber apenas notificações de versões em um repositório ou ignorar todas as notificações de um repositório.{% endif %} {% ifversion fpt or ghes > 3.0 or ghae-next %} + ### Sobre as notificações personalizadas É possível personalizar notificações para um repositório. Por exemplo, você pode optar por receber notificação apenas quando atualizações de um ou mais tipos de eventos ({% data reusables.notifications-v2.custom-notification-types %}) ocorrerem em um repositório, ou ignorar todas as notificações de um repositório. {% endif %} Para obter mais informações, consulte "[Definir as suas configurações de inspeção para um repositório individual](#configuring-your-watch-settings-for-an-individual-repository)" abaixo. @@ -158,25 +160,18 @@ Se "Inspecionar repositórios automaticamente" estiver desativado, então você ## Configurando as configurações de inspeção para um repositório individual -É possível escolher se deseja inspecionar ou não inspecionar um repositório individual. You can also choose to only be notified of {% ifversion fpt or ghes > 3.0 or ghae-next %}certain event types such as {% data reusables.notifications-v2.custom-notification-types %} (if enabled for the repository){% else %}new releases{% endif %}, or completely ignore an individual repository. +É possível escolher se deseja inspecionar ou não inspecionar um repositório individual. Você também pode optar por ser notificado apenas de {% ifversion fpt or ghes > 3.0 or ghae-next %}certos tipos de eventos como {% data reusables.notifications-v2.custom-notification-types %} (se habilitado para o repositório) {% else %}novas versões{% endif %}, ou ignorar completamente um repositório individual. {% data reusables.repositories.navigate-to-repo %} 2. No canto superior direito, clique no menu suspenso "Inspecionar" para selecionar uma opção de inspeção. -{% ifversion ghae or ghes < 3.1 %} - ![Opções de inspeção em um menu suspenso para repositórios](/assets/images/help/notifications-v2/watch-repository-options.png) -{% elsif fpt or ghes > 3.0 or ghae-next %} +{% ifversion fpt or ghes > 3.0 or ghae-next %} ![Opções de inspeção em um menu suspenso para repositórios](/assets/images/help/notifications-v2/watch-repository-options-custom.png) -A opção **Personalizar** permite que você personalize ainda mais as notificações para que você seja notificado apenas quando eventos específicos ocorrerem no repositório, além de participar e @mentions. - -{% ifversion fpt or ghes > 3.1 or ghae-issue-4910 %} - ![Opções de inspeção personalizadas em um menu suspenso para um repositório](/assets/images/help/notifications-v2/watch-repository-options-custom2-dotcom.png) + A opção **Personalizar** permite que você personalize ainda mais as notificações para que você seja notificado apenas quando eventos específicos ocorrerem no repositório, além de participar e @mentions. {% else %} - ![Opções de inspeção personalizadas em um menu suspenso para um repositório](/assets/images/enterprise/3.1/help/notifications-v2/watch-repository-options-custom2.png) -{% endif %} - -Se você selecionar "Problemas", você será notificado e irá inscrever-se para receber atualizações sobre cada problema (incluindo aqueles que existiam antes de você selecionar esta opção) no repositório. Se você for @mentioned em um pull request neste repositório, você receberá notificações sobre isso também e será inscrito em atualizações desse pull request específico, além de ser notificado sobre problemas. - + ![Opções de inspeção em um menu suspenso para repositórios](/assets/images/help/notifications-v2/watch-repository-options.png){% endif %} +{% ifversion fpt or ghes > 3.0 or ghae-next %} + ![Opções de inspeção personalizadas em um menu suspenso para um repositório](/assets/images/help/notifications-v2/watch-repository-options-custom2-dotcom.png) Se você selecionar "Problemas", você será notificado e irá inscrever-se para receber atualizações sobre cada problema (incluindo aqueles que existiam antes de você selecionar esta opção) no repositório. Se você for @mentioned em um pull request neste repositório, você receberá notificações sobre isso também e será inscrito em atualizações desse pull request específico, além de ser notificado sobre problemas. {% endif %} ## Escolhendo para onde as notificações de e-mail da sua organização são enviadas diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md index 6f7c8f2f38..63bf9a373b 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md @@ -15,9 +15,9 @@ topics: shortTitle: Perfil da organização --- -You can optionally choose to add a description, location, website, and email address for your organization, and pin important repositories. You can customize your organization's profile by adding a README.md file. For more information, see "[Customizing your organization's profile](/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile)." +Opcionalmente, é possível optar por adicionar uma descrição, localidade, site e endereço de e-mail da sua organização e fixar os repositórios importantes. Você pode personalizar o perfil da sua organização adicionando um arquivo README.md. Para obter mais informações, consulte "[Personalizar o perfil da sua organização](/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile)". -{% ifversion fpt %}Para confirmar a identidade da organização e exibir um selo "Verificado" na página do perfil da organização, você deve verificar os domínios da organização com o {% data variables.product.product_name %}. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."{% endif %} +{% ifversion fpt %}Para confirmar a identidade da organização e exibir um selo "Verificado" na página do perfil da organização, você deve verificar os domínios da organização com o {% data variables.product.product_name %}. Para obter mais informações, consulte "[Verificar ou aprovar um domínio para a sua organização](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)".{% endif %} {% ifversion fpt or ghes > 3.2 %} ![Exemplo de página de perfil da organização](/assets/images/help/organizations/org_profile_with_overview.png) diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md index 2922b11746..0b31036242 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md @@ -48,6 +48,14 @@ Ao se inscrever em uma conta, o {% data variables.product.product_name %} fornec Você pode alterar o nome que é exbido em seu perfil. Este nome também pode ser exibido ao lado dos comentários que você fizer em repositórios privados pertencentes a uma organização. Para obter mais informações, consulte "[Gerenciar a exibição de nomes de integrantes na organização](/articles/managing-the-display-of-member-names-in-your-organization)". +{% ifversion fpt %} +{% note %} + +**Observação:** Se você for integrante de um {% data variables.product.prodname_emu_enterprise %}, todas as alterações no nome do seu perfil devem ser feitas por meio do seu provedor de identidade ao invés de {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.emu-more-info-account %} + +{% endnote %} +{% endif %} + {% data reusables.user_settings.access_settings %} 2. Em "Name" (Nome), digite o nome que deseja exibir em seu perfil. ![Campo nome em configurações de perfil](/assets/images/help/profile/name-field.png) @@ -92,7 +100,7 @@ Ao definir o seu status, você também pode informar às pessoas que sua disponi ![Revisor solicitado apresenta "busy" (ocupado) ao lado do nome de usuário](/assets/images/help/profile/request-a-review-limited-availability-status.png) -Se você selecionar a opção "Busy" (Ocupado), quando as pessoas fizerem @menção ao seu nome de usuário, atribuírem um problema ou pull request a você ou solicitarem a você uma revisão de pull request, uma observação ao lado do seu nome mostrará que você está ocupado. You will also be excluded from automatic review assignment for pull requests assigned to any teams you belong to. Para obter mais informações, consulte "[Gerenciando a responsabilidade pela revisão de código para sua equipe](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)." +Se você selecionar a opção "Busy" (Ocupado), quando as pessoas fizerem @menção ao seu nome de usuário, atribuírem um problema ou pull request a você ou solicitarem a você uma revisão de pull request, uma observação ao lado do seu nome mostrará que você está ocupado. Você também será excluído da atribuição automática de revisão para os pull requests atribuídos a qualquer equipe a que você pertença. Para obter mais informações, consulte "[Gerenciando a responsabilidade pela revisão de código para sua equipe](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)." 1. No canto superior direito do {% data variables.product.product_name %}, clique em sua foto de perfil e em **Set your status** (Definir seu status) ou, se já tiver um status definido, clique em seu status atual. ![Botão no perfil para definir seu status](/assets/images/help/profile/set-status-on-profile.png) 2. Para adicionar um texto personalizado ao seu status, clique no campo de texto e digite uma mensagem. ![Campo para digitar mensagem de status](/assets/images/help/profile/type-a-status-message.png) diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/index.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/index.md index e71ed2c2a0..dd7581f027 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/index.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/index.md @@ -14,7 +14,7 @@ children: - /viewing-contributions-on-your-profile - /showing-an-overview-of-your-activity-on-your-profile - /publicizing-or-hiding-your-private-contributions-on-your-profile - - /sending-your-github-enterprise-server-contributions-to-your-githubcom-profile + - /sending-enterprise-contributions-to-your-githubcom-profile - /why-are-my-contributions-not-showing-up-on-my-profile - /troubleshooting-commits-on-your-timeline shortTitle: Gerenciar gráfico de contribuição diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-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/publicizing-or-hiding-your-private-contributions-on-your-profile.md index 7d648971e7..b4aa894a00 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-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/publicizing-or-hiding-your-private-contributions-on-your-profile.md @@ -14,14 +14,18 @@ topics: shortTitle: Contribuições privadas --- -Se você mostrar suas contribuições privadas, pessoas sem acesso aos repositórios nos quais você trabalha não poderão ver os detalhes de suas contribuições privadas. Em vez disso, elas verão o número de contribuições privadas que você fez em determinado dia. Suas contribuições públicas incluirão informações detalhadas. Para obter mais informações, consulte "[Visualizar contribuições na página de perfil](/articles/viewing-contributions-on-your-profile-page)". +Se você mostrar suas contribuições privadas, pessoas sem acesso aos repositórios nos quais você trabalha não poderão ver os detalhes de suas contribuições privadas. Em vez disso, elas verão o número de contribuições privadas que você fez em determinado dia. Suas contribuições públicas incluirão informações detalhadas. Para obter mais informações, consulte "[Visualizar contribuições na página de perfil](/articles/viewing-contributions-on-your-profile-page)." + +{% note %} + +**Observação:** {% ifversion fpt or ghes %}Em {% ifversion fpt %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_name %}{% endif %}, contribuições públicas no seu perfil são visíveis {% ifversion fpt %}para qualquer pessoa que pode acessar {% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}apenas para outros usuários de {% data variables.product.product_location%}{% endif %}.{% elsif ghae %}Em {% data variables.product.prodname_ghe_managed %}, apenas outros integrantes da empresa podem ver as contribuições no seu perfil.{% endif %} + +{% endnote %} ## Alterar a visibilidade de suas contribuições privadas -Por padrão, os visitantes só veem contribuições públicas em seu perfil. - {% data reusables.profile.access_profile %} -2. Mostre ou oculte contribuições privadas no perfil: +1. Mostre ou oculte contribuições privadas no perfil: - Para mostrar suas contribuições privadas, use o menu suspenso **Contribution settings** (Configurações de contribuição) localizado acima do gráfico de contribuições e marque **Private contributions** (Contribuições privadas). Os visitantes verão sua contagem de contribuições privadas sem informações adicionais. ![Habilitar visitantes para ver contribuições privadas a partir do menu suspenso contribution settings (configurações de contribuição)](/assets/images/help/profile/private-contributions-on.png) - Para ocultar suas contribuições privadas, use o menu suspenso **Contribution settings** (Configurações de contribuição) localizado acima do gráfico de contribuições e desmarque **Private contributions** (Contribuições privadas). Os visitantes verão apenas suas contribuições públicas. ![Habilitar visitantes para ver contribuições privadas a partir do menu suspenso contribution settings (configurações de contribuição)](/assets/images/help/profile/private-contributions-off.png) diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md b/translations/pt-BR/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 new file mode 100644 index 0000000000..a4ed4e3eee --- /dev/null +++ b/translations/pt-BR/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 @@ -0,0 +1,64 @@ +--- +title: Enviar contribuições corporativas para seu perfil do GitHub.com +intro: 'Você pode destacar seu trabalho no {% data variables.product.prodname_enterprise %} enviando as contagens de contribuição para seu perfil do {% data variables.product.prodname_dotcom_the_website %}.' +redirect_from: + - /articles/sending-your-github-enterprise-contributions-to-your-github-com-profile/ + - /articles/sending-your-github-enterprise-server-contributions-to-your-github-com-profile + - /articles/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile + - /github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile + - /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile +versions: + fpt: '*' + ghes: '*' + ghae: next +topics: + - Profiles +shortTitle: Envie contribuições corporativas +--- + +## Sobre contribuições corporativas no seu perfil de {% data variables.product.prodname_dotcom_the_website %} + +O seu perfil de {% data variables.product.prodname_dotcom_the_website %} mostra {% ifversion fpt %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae-next %} ou {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} contagens de contribuição dos últimos 90 dias. {% data reusables.github-connect.sync-frequency %} As contagens de contribuição do {% data variables.product.prodname_enterprise %} são consideradas contribuições privadas. Os detalhes de commit mostrarão apenas a contagem de contribuição e que essas contribuições foram feitas em um ambiente {% data variables.product.prodname_enterprise %} fora de {% data variables.product.prodname_dotcom_the_website %}. + +Você pode decidir se deseja mostrar contribuições privadas no seu perfil. Para obter mais informações, consulte "[Mostrar ou ocultar contribuições privadas no perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile/)". + +Para obter mais informações sobre como as contribuições são calculadas, consulte "[Gerenciar gráficos de contribuição no perfil](/articles/managing-contribution-graphs-on-your-profile/)". + +{% note %} + +**Notas:** +- A conexão entre as contas é controlada pela Declaração de privacidade do GitHub, e os usuários que ativam a conexão concordam com os Termos de serviço do GitHub. + +- Antes de poder conectar seu {% ifversion fpt %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae-next %} ou {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} perfil para o seu perfil de {% data variables.product.prodname_dotcom_the_website %}, o proprietário da sua empresa deverá habilitar {% data variables.product.prodname_github_connect %} e habilitar o compartilhamento de contribuições entre os ambientes. Para obter mais informações, entre em contato com o proprietário da empresa. + +{% endnote %} + +{% ifversion fpt or ghes or ghae %} + +## Enviando suas contribuições corporativas para o perfil de {% data variables.product.prodname_dotcom_the_website %} + +{% ifversion fpt %} + +- Para enviar contribuições corporativas de {% data variables.product.prodname_ghe_server %} para seu perfil de {% data variables.product.prodname_dotcom_the_website %}, consulte "[Enviando contribuições corporativas para o seu perfil de {% data variables.product.prodname_dotcom_the_website %}](/enterprise-server/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)" na documentação de {% data variables.product.prodname_ghe_server %}.{% ifversion ghae-next %}- Para enviar contribuições corporativas de {% data variables.product.prodname_ghe_managed %} para seu perfil de {% data variables.product.prodname_dotcom_the_website %}, consulte "[Enviando contribuições corporativas para o seu perfil de {% data variables.product.prodname_dotcom_the_website %}](/github-ae@latest/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)" na documentação de {% data variables.product.prodname_ghe_managed %}.{% endif %} + +{% elsif ghes %} + +1. Efetue o login em {% data variables.product.prodname_ghe_server %} e em {% data variables.product.prodname_dotcom_the_website %}. +1. No canto superior direito de qualquer página do {% data variables.product.prodname_ghe_server %}, clique na sua foto do perfil e em **Configurações**. ![Ícone Settings (Configurações) na barra de usuário](/assets/images/help/settings/userbar-account-settings.png) +{% data reusables.github-connect.github-connect-tab-user-settings %} +{% data reusables.github-connect.connect-dotcom-and-enterprise %} +1. Revise os recursos que {% data variables.product.prodname_ghe_server %} terá acesso a partir da sua conta {% data variables.product.prodname_dotcom_the_website %} e então, clique em **Authorize** (Autorizar). ![Autorizar conexão entre o GitHub Enterprise Server e GitHub.com](/assets/images/help/settings/authorize-ghe-to-connect-to-dotcom.png) +{% data reusables.github-connect.send-contribution-counts-to-githubcom %} + +{% elsif ghae %} + +1. Efetue o login em {% data variables.product.prodname_ghe_managed %} e em {% data variables.product.prodname_dotcom_the_website %}. +1. No canto superior direito de qualquer página do {% data variables.product.prodname_ghe_managed %}, clique na sua foto do perfil e em **Configurações**. ![Ícone Settings (Configurações) na barra de usuário](/assets/images/help/settings/userbar-account-settings.png) +{% data reusables.github-connect.github-connect-tab-user-settings %} +{% data reusables.github-connect.connect-dotcom-and-enterprise %} +{% data reusables.github-connect.authorize-connection %} +{% data reusables.github-connect.send-contribution-counts-to-githubcom %} + +{% endif %} + +{% endif %} 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 8cb65fd128..6e824085da 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 @@ -83,7 +83,7 @@ Os registros de data e hora são calculados de forma diferente para commits e pu ![Seção Visão geral de atividade no perfil](/assets/images/help/profile/activity-overview-section.png) -As organizações retratadas na visão geral da atividade são priorizadas de acordo com a forma como você está ativo na organização. Se você for integrante de uma organização e @mencioná-la na bio do perfil, essa organização será priorizada na visão geral da atividade. Para obter mais informações, consulte “[Mencionar pessoas e equipes](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)” ou "[Adicionar uma bio ao seu perfil](/articles/adding-a-bio-to-your-profile/)". +As organizações retratadas na visão geral da atividade são priorizadas de acordo com a forma como você está ativo na organização. Se você for integrante de uma organização e @mencioná-la na bio do perfil, essa organização será priorizada na visão geral da atividade. Para obter mais informações, consulte "[Mencionando pessoas e equipes](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)” or "[Adicionando uma biografia ao seu perfil](/articles/adding-a-bio-to-your-profile/)." ## Atividade de contribuição @@ -91,15 +91,14 @@ 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 not ghae %} -## Exibir contribuições da {% data variables.product.product_location_enterprise %} no {% data variables.product.prodname_dotcom_the_website %} +{% ifversion fpt or ghes or ghae-next %} + +## Exibir contribuições da {% data variables.product.prodname_enterprise %} no {% data variables.product.prodname_dotcom_the_website %} + +Se você usar {% ifversion fpt %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae-next %} 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)". -Se o administrador do site tiver ativado o {% data variables.product.prodname_unified_contributions %}, você poderá enviar contagens de contribuição do {% data variables.product.prodname_enterprise %} para o perfil do {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, consulte "[Enviar suas contribuições do {% data variables.product.prodname_ghe_server %} para o {% data variables.product.prodname_dotcom_the_website %}](/articles/sending-your-github-enterprise-server-contributions-to-your-github-com-profile)". {% endif %} ## Leia mais - "[Visualizar contribuições na página de perfil](/articles/viewing-contributions-on-your-profile-page)" -- "[Por que minhas contribuições não aparecem no meu perfil?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)" -- "[Mostrar ou ocultar contribuições privadas no perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)" -- "[Exibir a visão geral das atividades no perfil](/articles/showing-an-overview-of-your-activity-on-your-profile)" diff --git a/translations/pt-BR/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 b/translations/pt-BR/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 index 4ab3c91a7e..429702a8eb 100644 --- a/translations/pt-BR/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 +++ b/translations/pt-BR/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 @@ -1,6 +1,6 @@ --- title: Por que minhas contribuições não aparecem no meu perfil? -intro: Learn common reasons that contributions may be missing from your contributions graph. +intro: Entenda os motivos comuns que as contribuições podem não ter no seu gráfico de contribuição. redirect_from: - /articles/why-are-my-contributions-not-showing-up-on-my-profile - /github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile @@ -11,10 +11,10 @@ versions: ghae: '*' topics: - Profiles -shortTitle: Missing contributions +shortTitle: Contribuições ausentes --- -## About your contribution graph +## Sobre o seu gráfico de contribuição O gráfico de contribuições de perfil é um registro das contribuições que você fez em repositórios do {% data variables.product.product_name %}. As contribuições recebem registros de data e hora de acordo com o UTC (Coordinated Universal Time, Horário universal coordenado), e não com o fuso horário local. As contribuições só serão contabilizadas se atenderem a determinados critérios. Em alguns casos, pode ser necessário recriar o gráfico para que as contribuições sejam exibidas. diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md index 1ae53d4bf3..4914085015 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md @@ -24,6 +24,8 @@ Os repositórios de propriedade de uma organização podem conceder mais acesso {% ifversion fpt %} +Se você for integrante de um {% data variables.product.prodname_emu_enterprise %}, você só poderá convidar outros integrantes da sua empresa para colaborar com você. {% data reusables.enterprise-accounts.emu-more-info-account %} + {% note %} **Observação:** o {% data variables.product.company_short %} limita o número de pessoas que podem ser convidadas para um repositório dentro de um período de 24 horas. Se você exceder esse limite, aguarde 24 horas ou crie uma organização para colaborar com mais pessoas. @@ -44,7 +46,7 @@ Os repositórios de propriedade de uma organização podem conceder mais acesso 5. Na barra lateral esquerda, clique em **Collaborators** (Colaboradores). ![Barra lateral Repository settings (Configurações de repositório) com destaque para Collaborators (Colaboradores)](/assets/images/help/repository/user-account-repo-settings-collaborators.png) 6. Em "Collaborators" (Colaboradores), comece a digitar o nome de usuário do colaborador. 7. Selecione o nome de usuário do colaborador no menu suspenso. ![Menu suspenso lista Collaborator (Colaborador)](/assets/images/help/repository/repo-settings-collab-autofill.png) -8. Clique em **Add collaborator** (Adicionar colaborador). !["Add collaborator" button](/assets/images/help/repository/repo-settings-collab-add.png) +8. Clique em **Add collaborator** (Adicionar colaborador). ![Botão "Adicionar colaborador"](/assets/images/help/repository/repo-settings-collab-add.png) {% endif %} {% ifversion fpt %} 9. O usuário receberá um e-mail com o convite para o repositório. Ao aceitar o convite, a pessoa terá acesso de colaborador ao seu repositório. 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-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md index e6a716485f..41626a10fc 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-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md @@ -18,7 +18,9 @@ shortTitle: Adicionar endereços de e-mail {% note %} -**Observação**: {% data reusables.user_settings.no-verification-disposable-emails %} +**Atenção**: + - {% data reusables.user_settings.no-verification-disposable-emails %} + - Se você for integrante de um {% data variables.product.prodname_emu_enterprise %}, você não poderá fazer alterações no seu endereço de e-mail em {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.emu-more-info-account %} {% endnote %} 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-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md index 7b6e252c28..325326718b 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-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md @@ -49,7 +49,7 @@ Atualizações serão exibidas no feed de notícias quando um usuário que você - Abrir um problema ou uma pull request com a etiqueta "help wanted" ou "good first issue" em um repositório que você está inspecionando. - Faz push de commits para um repositório que você inspeciona.{% ifversion fpt or ghes %} - Bifurca um repositório público.{% endif %} -- Publishes a new release. +- Publica uma nova versão. Para obter mais informações sobre como atribuir estrelas a repositórios e seguir pessoas, consulte "[Salvar repositórios com estrelas](/articles/saving-repositories-with-stars/)" e "[Seguir pessoas](/articles/following-people)". 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-github-user-account/managing-user-account-settings/changing-your-github-username.md index a68870104d..ad1d7d99fa 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-github-user-account/managing-user-account-settings/changing-your-github-username.md @@ -19,11 +19,11 @@ shortTitle: Mude seu nome de usuário ## Sobre alterações no nome de usuário -You can change your username to another username that is not currently in use.{% ifversion fpt %} 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. +Você pode alterar seu nome de usuário para outro nome de usuário que não está atualmente em uso.{% ifversion fpt %} Se o nome de usuário que você deseja não estiver disponível, considere outros nomes ou variações exclusivas. Usar um número, hífen ou uma ortografia alternativa pode ajudar você a encontrar um nome de usuário semelhante que ainda está disponível. -If you hold a trademark for the username, you can find more information about making a trademark complaint on our [Trademark Policy](/articles/github-trademark-policy/) page. +Se você tem uma marca registrada para o nome de usuário, você pode encontrar mais informações sobre como fazer uma reclamação de marca registrada na nossa página de [Política da marca registrada](/articles/github-trademark-policy/). -If you do not hold a trademark for the name, you can choose another username or keep your current username. O {% data variables.contact.github_support %} não pode liberar o nome de usuário indisponível para você. Para obter mais informações, consulte "[Alterar nome de usuário](#changing-your-username)".{% endif %} +Se você não tiver uma marca registrada para o nome, você poderá escolher outro nome de usuário ou manter seu nome de usuário atual. O {% data variables.contact.github_support %} não pode liberar o nome de usuário indisponível para você. Para obter mais informações, consulte "[Alterar nome de usuário](#changing-your-username)".{% endif %} Depois de alterar seu nome de usuário, o nome antigo será disponibilizado para reivindicação por qualquer pessoa. A maioria das referências aos seus repositórios sob o nome de usuário antigo muda automaticamente para o novo nome de usuário. No entanto, alguns links para seu perfil não são redirecionados automaticamente. @@ -31,6 +31,12 @@ O {% data variables.product.product_name %} não pode configurar redirecionament - [@menções](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) usando o nome de usuário antigo - Links para [gists](/articles/creating-gists) que incluem o nome de usuário antigo +{% ifversion fpt %} + +Se você for integrante de um {% data variables.product.prodname_emu_enterprise %}, não será possível alterar seu nome de usuário. {% data reusables.enterprise-accounts.emu-more-info-account %} + +{% endif %} + ## Referências de repositório Após alteração do nome de usuário, o {% data variables.product.product_name %} redirecionará automaticamente as referências para os repositórios. 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-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md index 0f9ad34ff6..d3adc0046e 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-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md @@ -24,7 +24,7 @@ shortTitle: Usuário em uma organização - Uma organização **não pode** ser convertida de volta em um usuário. - As chaves SSH, os tokens do OAuth, o perfil de trabalho, as reações e as informações do usuário associadas, **não** serão transferidos para a organização. Isso é válido apenas para a conta de usuário que está sendo convertida, e não para colaboradores da conta de usuário. - Qualquer commit feito com a conta do usuário convertido **não será mais vinculado** a essa conta. Os commits em si **permanecerão** intactos. - - Any forks of private repositories made with the converted user account will be deleted. + - Todas as bifurcações de repositórios privados feitas com a conta de usuário convertida serão excluídas. {% endwarning %} 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-github-user-account/managing-user-account-settings/index.md index 4d0c5e999c..81feb0d6ca 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-github-user-account/managing-user-account-settings/index.md @@ -15,6 +15,7 @@ topics: children: - /about-your-personal-dashboard - /managing-your-theme-settings + - /managing-your-tab-size-rendering-preference - /changing-your-github-username - /merging-multiple-user-accounts - /converting-a-user-into-an-organization 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-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories.md index 23132edaef..c33f752515 100644 --- 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-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories.md @@ -1,6 +1,6 @@ --- title: Gerenciar o nome do branch-padrão para seus repositórios -intro: 'You can set the default branch name for new repositories that you create on {% data variables.product.product_location %}.' +intro: 'Você pode definir os novos repositórios para nome do branch-padrão que você criar em {% data variables.product.product_location %}.' versions: fpt: '*' ghes: '>=3.0' diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md new file mode 100644 index 0000000000..02db5dc1f4 --- /dev/null +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md @@ -0,0 +1,15 @@ +--- +title: Gerenciar a preferência de interpretação do tamanho da aba +intro: Você pode gerenciar o número de espaços que equivale a uma aba para a sua conta de usuário. +versions: + fpt: '*' +topics: + - Accounts +shortTitle: Gerenciando o tamanho da sua aba +--- + +Se você considerar que a indentação em abas no código interpretado em {% data variables.product.product_name %} demanda muito tempo, ou muito pouco espaço, você poderá alterar isto nas suas configurações. + +{% data reusables.user_settings.access_settings %} +1. Na barra lateral de configurações do usuário, clique em **Aparência**. ![Aba "Aparência" na barra lateral de configurações do usuário](/assets/images/help/settings/appearance-tab.png) +2. Em "Preferência do tamanho da aba", selecione o menu suspenso e escolha sua preferência. ![Botão de preferência do tamanho da aba](/assets/images/help/settings/tab-size-preference.png) diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md index 157c87e311..92c4aec56d 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md @@ -3,6 +3,7 @@ title: Gerenciar as configurações de temas intro: 'Você pode gerenciar como {% data variables.product.product_name %} se parece com você definindo uma preferência de tema que segue as configurações do seu sistema ou sempre usa um modo claro ou escuro.' versions: fpt: '*' + ghae: next ghes: '>=3.2' topics: - Accounts @@ -14,7 +15,15 @@ shortTitle: Gerenciar configurações de tema Por escolha e flexibilidade sobre como e quando você usa {% data variables.product.product_name %}, você pode configurar configurações de tema para mudar como {% data variables.product.product_name %} fica para você. Você pode escolher entre temas claros e escuros ou você pode configurar {% data variables.product.product_name %} para seguir as configurações do seu sistema. -Você deverá usar um tema escuro para reduzir o consumo de energia em certos dispositivos, reduzir o cansaço ocular em condições com pouca luz, ou porque você prefere a aparência do tema.{% ifversion fpt or ghae-issue-4618 %} Pessoas com deficiência visual podem beneficiar-se do tema de alto contraste escuro, com maior contraste entre primeiro plano e elementos de fundo.{% endif %} +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 ghae-issue-4618 %} 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 %} se você for daltônico, você poderá beneficiar-se dos nossos temas de cor clara e escura. + +{% note %} + +**Observação:** Os temas coloridos estão atualmente em beta público. Para obter mais informações sobre como habilitar funcionalidades no beta público, consulte "[Explorando versões de acesso antecipado com visualização de funcionalidades](/get-started/using-github/exploring-early-access-releases-with-feature-preview)". + +{% endnote %}{% endif %} {% data reusables.user_settings.access_settings %} 1. Na barra lateral de configurações do usuário, clique em **Aparência**. ![Aba "Aparência" na barra lateral de configurações do usuário](/assets/images/help/settings/appearance-tab.png) @@ -24,6 +33,8 @@ Você deverá usar um tema escuro para reduzir o consumo de energia em certos di {% ifversion fpt or ghae-issue-4618 %}![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 ghae-issue-4618 %}![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 ghae-issue-4619 %} + - 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 %} ## 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-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md index 2cf1cf3ec7..3a2df6538f 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-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md @@ -35,7 +35,7 @@ O proprietário do repositório tem controle total do repositório. Além das a | {% ifversion fpt %}Convidar colaboradores{% else %}Adicionar colaboradores{% endif %} | | | "[Convidar colaboradores para um repositório pessoal](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)" | | | Alterar a visibilidade do repositório | "[Configurar a visibilidade do repositório](/github/administering-a-repository/setting-repository-visibility)" {% ifversion fpt %} -| Limitar interações com o repositório | "[Limitar as interações no seu repositório](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)".|{% endif %}{% ifversion fpt or ghes > 3.0 %} +| Limitar interações com o repositório | "[Limitar as interações no seu repositório](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)".|{% endif %}{% ifversion fpt or ghes > 3.0 or ghae-next %} | Renomear um branch, incluindo o branch padrão | "[Renomear um branch](/github/administering-a-repository/renaming-a-branch)" ➲{% endif %} | Fazer merge de uma pull request em um branch protegido, mesmo sem revisões de aprovação | "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches)" | | Excluir o repositório | "[Excluir um repositório](/github/administering-a-repository/deleting-a-repository)" | @@ -53,7 +53,7 @@ O proprietário do repositório tem controle total do repositório. Além das a | Gerenciar o uso de dados para um repositório privado | "[Gerenciar as configurações de uso de dados para o seu repositório privado](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository)" {% endif %} | Definir os proprietários do código do repositório | "[Sobre proprietários do código](/github/creating-cloning-and-archiving-repositories/about-code-owners)" | -| Arquivar o repositório | "[Archiving repositories](/repositories/archiving-a-github-repository/archiving-repositories)" |{% ifversion fpt %} +| Arquivar o repositório | "[Arquivar repositórios](/repositories/archiving-a-github-repository/archiving-repositories)" |{% ifversion fpt %} | Criar consultorias de segurança | "[Sobre {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)" | | Exibir um botão de patrocinador | "[Exibir um botão de patrocinador no repositório](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)" |{% endif %}{% ifversion fpt or ghae or ghes > 3.0 %} | Permitir ou negar merge automático para pull requests | "[Gerenciar merge automático para pull requests no seu repositório](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)", {% endif %} @@ -72,7 +72,7 @@ Os colaboradores também podem executar as seguintes ações. | Ação | Mais informações | |:---------------------------------------------------------------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Bifurcar o repositório | "[Sobre bifurcações](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% ifversion fpt or ghes > 3.1 %} +| Bifurcar o repositório | "[Sobre bifurcações](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% ifversion fpt or ghes > 3.1 or ghae-next %} | Renomear um branch diferente do branch padrão | "[Renomear um branch](/github/administering-a-repository/renaming-a-branch)" ➲{% endif %} | Criar, editar e excluir comentários em commits, pull requests e problemas no repositório |
    • "[Sobre problemas](/github/managing-your-work-on-github/about-issues)"
    • "[Comentar em um pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)"
    • "[Gerenciar comentários disruptivos](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"
    | | Criar, atribuir, fechar e reabrir problemas no repositório | "[Gerenciar o seu trabalho com problemas](/github/managing-your-work-on-github/managing-your-work-with-issues)" | 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-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do.md index 2b9ec75274..1c5e12f757 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-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do.md @@ -14,7 +14,7 @@ shortTitle: Disponível para caixa de seleção de contratação {% warning %} -Observação de depreciação: O GitHub Jobs agora está obsoleto. A última data para publicar um trabalho foi 19 de maio de 2021. The GitHub Jobs site has shut down entirely on August 19, 2021, and now redirects to the [GitHub blog post](https://github.blog/changelog/2021-04-19-deprecation-notice-github-jobs-site/) notice, which has more information on the now-completed deprecation of GitHub Jobs. +Observação de depreciação: O GitHub Jobs agora está obsoleto. A última data para publicar um trabalho foi 19 de maio de 2021. O site dos do GitHub Jobs foi totalmente desativado em 19 de agosto de 2021 e agora faz o redirecionamento para a notificação da postagem no blogue [do GitHub](https://github.blog/changelog/2021-04-19-deprecation-notice-github-jobs-site/), que tem mais informações sobre a obsolescência concluída do GitHub Jobs. {% endwarning %} diff --git a/translations/pt-BR/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md b/translations/pt-BR/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md index 72da6401f0..7262bf4d8a 100644 --- a/translations/pt-BR/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md +++ b/translations/pt-BR/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md @@ -15,8 +15,6 @@ topics: - Workflows --- -{% data reusables.actions.ae-beta %} - ## Sobre a memorização das dependências do fluxo de trabalho As execuções do fluxo de trabalho geralmente reutilizam as mesmas saídas ou dependências baixadas de uma execução para outra. Por exemplo, as ferramentas de gerenciamento de pacotes e de dependência, como, por exemplo, Maven, Gradle, npm e Yarn mantêm uma cache local de dependências baixadas. @@ -27,9 +25,9 @@ Para memorizar as dependências para um trabalho, você precisará usar a ação Se você estiver armazenando gems do Ruby, disso considere usar a ação mantida pelo Ruby, que pode armazenar em cache as instalações do pacote na iniciação. Para obter mais informações, consulte [`ruby/setup-ruby`](https://github.com/ruby/setup-ruby#caching-bundle-install-automatically). -To cache and restore dependencies for npm, Yarn, or pnpm, you can use the [`actions/setup-node` action](https://github.com/actions/setup-node). +Para armazenar em cache e restaurar as dependências do npm, Yarn ou pnpm, você pode usar a ação [`actions/setup-node`](https://github.com/actions/setup-node). -Gradle and Maven caching is available with [`actions/setup-java` action](https://github.com/actions/setup-java). +O cache do Gradle e Maven está disponível com a ação [`actions/setup-java`](https://github.com/actions/setup-java). {% warning %} @@ -50,9 +48,9 @@ Com `v2` da ação da `cache`, você pode acessar a cache nos fluxos de trabalho Um fluxo de trabalho pode acessar e restaurar um cache criado no branch atual, no branch de base (incluindo branches base de repositórios bifurcados) ou no branch-padrão (geralmente `principal`). Por exemplo, um cache criado no branch-padrão pode ser acessado a partir de qualquer pull request. Além disso, se o branch `feature-b` tiver o branch de base `feature-a`, um fluxo de trabalho acionado em `feature-b` teria acesso a caches criados no branch-padrão (`principal`), `feature-a` e `feature-b`. -Access restrictions provide cache isolation and security by creating a logical boundary between different branches. Por exemplo, um cache criado para o branch `feature-a` (com a base no `principal`) não seria acessível para um pull request para o branch `feature-b` (com a base no `principal`). +As restrições de acesso fornecem o isolamento da cache e a segurança ao criar um limite lógico entre os diferentes branches. Por exemplo, um cache criado para o branch `feature-a` (com a base no `principal`) não seria acessível para um pull request para o branch `feature-b` (com a base no `principal`). -Multiple workflows within a repository share cache entries. A cache created for a branch within a workflow can be accessed and restored from another workflow for the same repository and branch. +Vários fluxos de trabalho dentro de um repositório compartilham entradas de cache. Uma cache criada para um branch de um fluxo de trabalho pode ser acessada e restaurada a partir de outro fluxo de trabalho para o mesmo repositório e branch. ## Usar a ação `cache` @@ -140,7 +138,7 @@ Para memorizar os arquivos em mais de um diretório, você precisará de uma eta ### Usar contextos para criar chaves da cache -Uma chave da cache pode incluir quaisquer contextos, funções, literais e operadores suportados por {% data variables.product.prodname_actions %}. For more information, see "[Expressions](/actions/learn-github-actions/expressions)." +Uma chave da cache pode incluir quaisquer contextos, funções, literais e operadores suportados por {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Expressões](/actions/learn-github-actions/expressions)". Usar expressões para criar uma `chave` permite que você crie automaticamente uma nova cache quando as dependências forem alteradas. Por exemplo, você pode criar uma `chave` usando uma expressão que calcula o hash de um arquivo `package-lock.json` de npm. diff --git a/translations/pt-BR/content/actions/advanced-guides/index.md b/translations/pt-BR/content/actions/advanced-guides/index.md index 3de81029ce..29a72f05c4 100644 --- a/translations/pt-BR/content/actions/advanced-guides/index.md +++ b/translations/pt-BR/content/actions/advanced-guides/index.md @@ -1,7 +1,7 @@ --- -title: Advanced guides -shortTitle: Advanced guides -intro: 'How to cache dependencies, store output as artifacts, and use the GitHub CLI in workflows.' +title: Guias avançados +shortTitle: Guias avançados +intro: 'Como armazenar dependências, armazenar os resultados como artefatos e usar a CLI do GitHub em fluxos de trabalho.' versions: fpt: '*' ghes: '*' diff --git a/translations/pt-BR/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md b/translations/pt-BR/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md index 1f668b2d8f..2f02805b66 100644 --- a/translations/pt-BR/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md +++ b/translations/pt-BR/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md @@ -20,11 +20,10 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Sobre artefatos de fluxos de trabalho -Os artefatos permitem que você persista com os dados após um trabalho ter sido concluído e compartilhe os dados com outro trabalho no mesmo fluxo de trabalho. Um artefato é um arquivo ou uma coleção de arquivos produzidos durante a execução de um fluxo de trabalho. Por exemplo, você pode usar artefatos para salvar a sua criação e testar a saída após uma conclusão da execução do fluxo de trabalho. +Os artefatos permitem que você persista com os dados após um trabalho ter sido concluído e compartilhe os dados com outro trabalho no mesmo fluxo de trabalho. Um artefato é um arquivo ou uma coleção de arquivos produzidos durante a execução de um fluxo de trabalho. Por exemplo, você pode usar artefatos para salvar a sua criação e testar a saída após uma conclusão da execução do fluxo de trabalho. {% data reusables.actions.reusable-workflow-artifacts %} {% data reusables.github-actions.artifact-log-retention-statement %} O período de retenção para um pull request reinicia toda vez que alguém fizer um push de um novo commit para o pull request. @@ -133,7 +132,7 @@ O valor `retention-days` não pode exceder o limite de retenção definido pelo ## Fazer o download ou excluir artefatos -During a workflow run, you can use the [`download-artifact`](https://github.com/actions/download-artifact) action to download artifacts that were previously uploaded in the same workflow run. +Durante a execução de um fluxo de trabalho, você pode usar a ação [`download-artifact`](https://github.com/actions/download-artifact)para fazer o download de artefatos previamente carregados na mesma execução de fluxo de trabalho. Após a conclusão da execução de um fluxo de trabalho, você pode fazer o download ou excluir artefatos em {% data variables.product.prodname_dotcom %} ou usar a API REST. Para obter mais informações, consulte "[Fazer o download de artefatos de fluxo de trabalho](/actions/managing-workflow-runs/downloading-workflow-artifacts), "[Remover artefatos do fluxo de trabalho](/actions/managing-workflow-runs/removing-workflow-artifacts)" e "[Artefatos da REST API](/rest/reference/actions#artifacts)". diff --git a/translations/pt-BR/content/actions/advanced-guides/using-github-cli-in-workflows.md b/translations/pt-BR/content/actions/advanced-guides/using-github-cli-in-workflows.md index f39d711c1d..f87771e635 100644 --- a/translations/pt-BR/content/actions/advanced-guides/using-github-cli-in-workflows.md +++ b/translations/pt-BR/content/actions/advanced-guides/using-github-cli-in-workflows.md @@ -1,7 +1,7 @@ --- -title: Using GitHub CLI in workflows -shortTitle: GitHub CLI in workflows -intro: 'You can script with {% data variables.product.prodname_cli %} in {% data variables.product.prodname_actions %} workflows.' +title: Usar o GitHub CLI em fluxos de trabalho +shortTitle: CLI do GitHub em fluxos de trabalho +intro: 'Você pode fazero script com {% data variables.product.prodname_cli %} em fluxos de trabalho {% data variables.product.prodname_actions %}.' redirect_from: - /actions/guides/using-github-cli-in-workflows versions: @@ -16,9 +16,9 @@ type: how_to {% data reusables.cli.cli-learn-more %} -{% data variables.product.prodname_cli %} is preinstalled on all {% data variables.product.prodname_dotcom %}-hosted runners. For each step that uses {% data variables.product.prodname_cli %}, you must set an environment variable called `GITHUB_TOKEN` to a token with the required scopes. +{% data variables.product.prodname_cli %} está pré-instalado em todos os executores hospedados em {% data variables.product.prodname_dotcom %}. Para cada etapa que usa {% data variables.product.prodname_cli %}, você deve definir uma variável de ambiente denominada `GITHUB_TOKEN` como um token com os escopos necessários. -You can execute any {% data variables.product.prodname_cli %} command. For example, this workflow uses the `gh issue comment` subcommand to add a comment when an issue is opened. +Você pode executar qualquer comando de {% data variables.product.prodname_cli %}. Por exemplo, este fluxo de trabalho usa o subcomando `gh issue comment` para adicionar um comentário quando um problema é aberto. ```yaml{:copy} name: Comment when opened @@ -36,7 +36,7 @@ jobs: ISSUE: {% raw %}${{ github.event.issue.html_url }}{% endraw %} ``` -You can also execute API calls through {% data variables.product.prodname_cli %}. For example, this workflow first uses the `gh api` subcommand to query the GraphQL API and parse the result. Then it stores the result in an environment variable that it can access in a later step. In the second step, it uses the `gh issue create` subcommand to create an issue containing the information from the first step. +Você também pode executar chamadas de API por meio de {% data variables.product.prodname_cli %}. Por exemplo, este fluxo de trabalho usa primeiro o subcomando `gh api` para consultar a API do GraphQL e analisar o resultado. Em seguida, ele armazena o resultado de uma variável de ambiente a qual pode acessar em uma etapa posterior. Na segunda etapa, ele usa o subcomando `gh issue create` para criar um problema que contém as informações da primeira etapa. ```yaml{:copy} name: Report remaining open issues diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/about-continuous-integration.md b/translations/pt-BR/content/actions/automating-builds-and-tests/about-continuous-integration.md index 8f589232f0..db57be1f33 100644 --- a/translations/pt-BR/content/actions/automating-builds-and-tests/about-continuous-integration.md +++ b/translations/pt-BR/content/actions/automating-builds-and-tests/about-continuous-integration.md @@ -1,6 +1,6 @@ --- title: Sobre integração contínua -intro: 'Você pode criar fluxos de trabalho personalizados de integração contínua (CI) e implantação contínua (CD) diretamente no seu repositório de {% data variables.product.prodname_dotcom %} com as {% data variables.product.prodname_actions %}.' +intro: 'Você pode criar fluxos de trabalho de integração contínua (CI) personalizados diretamente no repositório do {% data variables.product.prodname_dotcom %} com o {% data variables.product.prodname_actions %}.' product: '{% data reusables.gated-features.actions %}' redirect_from: - /articles/about-continuous-integration @@ -15,13 +15,11 @@ versions: type: overview topics: - CI - - CD shortTitle: Integração contínua --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Sobre integração contínua @@ -49,45 +47,12 @@ Além de ajudá-lo a configurar fluxos de trabalho de CI para seu projeto, você Para obter uma definição de termos comuns, consulte "[Conceitos básicos de {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/core-concepts-for-github-actions)". -## Linguagens compatíveis - +## Modelos de fluxo de trabalho {% data variables.product.product_name %} oferece modelos de fluxo de trabalho de CI para uma variedade de linguagens e estruturas. Pesquise a lista completa dos modelos de fluxo de trabalho de CI oferecidos por {% data variables.product.product_name %} no repositório {% ifversion fpt %}[actions/starter-workflows](https://github.com/actions/starter-workflows/tree/main/ci) {% else %} e no repositório `actions/starter-workflows` em {% data variables.product.product_location %}{% endif %}. -{% ifversion fpt or ghes > 3.0 or ghae-next %} -## Ignorar execuções de fluxo de trabalho - -Se você deseja impedir temporariamente que um fluxo de trabalho seja acionado, pode adicionar uma instrução para ignorar a mensagem de commit. Os fluxos de trabalho que seriam acionados `on: push` ou `on: pull_request` não serão acionado se você adicionar qualquer uma das strings a seguir para a mensagem de commit em um push, ou o commit HEAD de um pull request: - -* `[skip ci]` -* `[ci skip]` -* `[no ci]` -* `[skip actions]` -* `[actions skip]` - -Como alternativa, você pode terminar a mensagem de commit com duas linhas vazias seguidas de `skip-checks: true` ou `skip-checks:true`. - -Você não conseguirá fazer o merge do pull request se o repositório estiver configurado para exigir verificações específicas para passar primeiro. Para permitir que o merge do pull request, você pode fazer o push de um novo commit no pull request sem que a instrução seja ignorada na mensagem do commit. - -{% note %} - -**Observação:** Ignorar instruções só se aplica aos eventos `push` e `pull_request`. Por exemplo, adicionar `[skip ci]` a uma mensagem de commit não impedirá que um fluxo de trabalho que acionou `on : pull_request_target` seja executado. - -{% endnote %} -{% endif %} - -## Notificações para execução de fluxo de trabalho - -{% data reusables.repositories.workflow-notifications %} - -## Selos de status para execução de fluxo de trabalho - -{% data reusables.repositories.actions-workflow-status-badge-intro %} - -Para obter mais informações, consulte "[Adicionando um selo de status do fluxo de trabalho](/actions/managing-workflow-runs/adding-a-workflow-status-badge)". - ## Leia mais {% ifversion fpt %} diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md index 6f9ed9e257..7062ed8b7f 100644 --- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md +++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md @@ -19,7 +19,6 @@ shortTitle: Criar & testar Java & Ant {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introdução diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md index aa33548cc5..82009bcf98 100644 --- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md +++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md @@ -19,7 +19,6 @@ shortTitle: Criar & testar Java & Gradle {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introdução @@ -110,7 +109,7 @@ steps: ## Memorizar dependências -Ao usar executores hospedados em {% data variables.product.prodname_dotcom %}, você poderá armazenar em cache suas dependências para acelerar as execuções do seu fluxo de trabalho. Após a conclusão bem-sucedida, a sua cache do pacote do Gradle local será armazenada na infraestrutura do GitHub Actions. Para os fluxos de trabalho futuros, a cache será restaurada para que as dependências não precisem ser baixadas dos repositórios de pacotes remotos. You can cache dependencies simply using the [`setup-java` action](https://github.com/marketplace/actions/setup-java-jdk) or can use [`cache` action](https://github.com/actions/cache) for custom and more advanced configuration. +Ao usar executores hospedados em {% data variables.product.prodname_dotcom %}, você poderá armazenar em cache suas dependências para acelerar as execuções do seu fluxo de trabalho. Após a conclusão bem-sucedida, a sua cache do pacote do Gradle local será armazenada na infraestrutura do GitHub Actions. Para os fluxos de trabalho futuros, a cache será restaurada para que as dependências não precisem ser baixadas dos repositórios de pacotes remotos. Você pode armazenar dependências simplesmente usando a ação [`setup-java`](https://github.com/marketplace/actions/setup-java-jdk) ou pode usar a ação [`cache` ](https://github.com/actions/cache) para uma configuração mais avançada e personalizada. {% raw %} ```yaml{:copy} diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md index d20d58769b..5f608b047b 100644 --- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md +++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md @@ -19,7 +19,6 @@ shortTitle: Criar & testar o Java com o Maven {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introdução @@ -105,7 +104,7 @@ steps: ## Memorizar dependências -Ao usar executores hospedados em {% data variables.product.prodname_dotcom %}, você poderá armazenar em cache suas dependências para acelerar as execuções do seu fluxo de trabalho. Após a conclusão bem-sucedida, o seu repositório local do Maven será armazenado na infraestrutura do GitHub Actions. Para os fluxos de trabalho futuros, a cache será restaurada para que as dependências não precisem ser baixadas dos repositórios remotos do Maven. You can cache dependencies simply using the [`setup-java` action](https://github.com/marketplace/actions/setup-java-jdk) or can use [`cache` action](https://github.com/actions/cache) for custom and more advanced configuration. +Ao usar executores hospedados em {% data variables.product.prodname_dotcom %}, você poderá armazenar em cache suas dependências para acelerar as execuções do seu fluxo de trabalho. Após a conclusão bem-sucedida, o seu repositório local do Maven será armazenado na infraestrutura do GitHub Actions. Para os fluxos de trabalho futuros, a cache será restaurada para que as dependências não precisem ser baixadas dos repositórios remotos do Maven. Você pode armazenar dependências simplesmente usando a ação [`setup-java`](https://github.com/marketplace/actions/setup-java-jdk) ou pode usar a ação [`cache` ](https://github.com/actions/cache) para uma configuração mais avançada e personalizada. {% raw %} ```yaml{:copy} diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-net.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-net.md index 31251d2937..4924570dd0 100644 --- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-net.md +++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-net.md @@ -8,12 +8,11 @@ versions: fpt: '*' ghes: '*' ghae: '*' -shortTitle: Build & test .NET +shortTitle: Criar & test .NET --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introdução 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 index 27f1d53006..27873a096b 100644 --- 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 @@ -1,7 +1,7 @@ --- -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. +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. product: '{% data reusables.gated-features.actions %}' redirect_from: - /actions/guides/building-and-testing-nodejs-or-python @@ -14,4 +14,4 @@ topics: - CI --- - \ No newline at end of file + 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 375b850330..17fd2635bb 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 @@ -22,7 +22,6 @@ hasExperimentalAlternative: true {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introdução @@ -84,7 +83,7 @@ A ação `setup-node` considera uma versão do Node.js como uma entrada e config O modelo inclui uma estratégia matriz que cria e testa seu código com quatro versões de Node.js: 10.x, 12.x, 14.x e 15.x. O "x" é um caractere curinga que corresponde à última versão menor e à versão do patch disponível para uma versão. Cada versão do Node.js especificada na matriz `node-version` cria uma tarefa que executa as mesmas etapas. -Cada trabalho pode acessar o valor definido na matriz `node-version` usando o contexto `matriz`. A ação `setup-node` usa o contexto como entrada de `node-version`. A ação `setup-node` configura cada tarefa com uma versão diferente de Node.js antes de criar e testar o código. For more information about matrix strategies and contexts, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix)" and "[Contexts](/actions/learn-github-actions/contexts)." +Cada trabalho pode acessar o valor definido na matriz `node-version` usando o contexto `matriz`. A ação `setup-node` usa o contexto como entrada de `node-version`. A ação `setup-node` configura cada tarefa com uma versão diferente de Node.js antes de criar e testar o código. Para obter mais informações sobre estratégias e contextos de matriz, consulte "[Sintaxe do Fluxo de trabalho para {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix)" e "[Contextos](/actions/learn-github-actions/contexts)". {% raw %} ```yaml{:copy} @@ -268,7 +267,7 @@ steps: - run: yarn test ``` -The following example caches dependencies for pnpm (v6.10+). +O exemplo a seguir armazena dependências para pnpm (v6.10+). ```yaml{:copy} {% data reusables.actions.actions-not-certified-by-github-comment %} @@ -288,7 +287,7 @@ steps: - run: pnpm test ``` -To cache dependencies, you must have a `package-lock.json`, `yarn.lock`, or `pnpm-lock.yaml` file in the root of the repository. Se você precisar de uma personalização mais flexível, você poderá usar a ação [`cache`](https://github.com/marketplace/actions/cache). Para obter mais informações, consulte "Dependências de cache para acelerar fluxos de trabalho". +Para armazenar dependências de cache, você deve ter um `pacote-lock.json`, `yarn.lock` ou um arquivo `pnpm-lock.yaml` na raiz do repositório. Se você precisar de uma personalização mais flexível, você poderá usar a ação [`cache`](https://github.com/marketplace/actions/cache). Para obter mais informações, consulte "Dependências de cache para acelerar fluxos de trabalho". ## Criar e testar seu código diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-powershell.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-powershell.md index 3984c59db7..a2b5bb0cc7 100644 --- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-powershell.md +++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-powershell.md @@ -19,7 +19,6 @@ shortTitle: Criar & testar o PowerShell {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introdução 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 28485218c6..1bf6448a28 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 @@ -21,7 +21,6 @@ hasExperimentalAlternative: true {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introdução @@ -222,7 +221,7 @@ etapas: ### Arquivo de requisitos -Depois de atualizar o `pip`, um o próximo passo típico é instalar as dependências de *requirements.txt*. For more information, see [pip](https://pip.pypa.io/en/stable/cli/pip_install/#example-requirements-file). +Depois de atualizar o `pip`, um o próximo passo típico é instalar as dependências de *requirements.txt*. Para obter mais informações, consulte [pip](https://pip.pypa.io/en/stable/cli/pip_install/#example-requirements-file). {% raw %} ```yaml{:copy} @@ -326,7 +325,7 @@ etapas: ``` {% endraw %} -The linting step has `continue-on-error: true` set. This will keep the workflow from failing if the linting step doesn't succeed. Once you've addressed all of the linting errors, you can remove this option so the workflow will catch new issues. +O passo de limpeza de código foi configurado com `continue-on-error: true`. Isto impedirá que o fluxo de trabalho falhe se a etapa de limpeza de código não for bem-sucedida. Após corrigir todos os erros de limpeza de código, você poderá remover essa opção para que o fluxo de trabalho capture novos problemas. ### Executar testes com tox diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-ruby.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-ruby.md index c8c7e38f0e..0af26c3f0c 100644 --- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-ruby.md +++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-ruby.md @@ -12,12 +12,11 @@ type: tutorial topics: - CI - Ruby -shortTitle: Build & test Ruby +shortTitle: Criar & testar Ruby --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introdução @@ -98,7 +97,7 @@ strategy: ``` {% endraw %} -Cada versão do Ruby especificada no array `ruby-version` cria um trabalho que executa as mesmas etapas. O contexto {% raw %}`${{ matrix.ruby-version }}`{% endraw %} é usado para acessar a versão atual do trabalho. For more information about matrix strategies and contexts, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions)" and "[Contexts](/actions/learn-github-actions/contexts)." +Cada versão do Ruby especificada no array `ruby-version` cria um trabalho que executa as mesmas etapas. O contexto {% raw %}`${{ matrix.ruby-version }}`{% endraw %} é usado para acessar a versão atual do trabalho. Para obter mais informações sobre estratégias e contextos de matriz, consulte "[Sintaxe do Fluxo de trabalho para {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions)" e "[Contextos](/actions/learn-github-actions/contexts)". O fluxo de trabalho totalmente atualizado com uma estratégia de matriz pode parecer com isto: diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-swift.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-swift.md index 7a915399c0..0e22cfd6e3 100644 --- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-swift.md +++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-swift.md @@ -17,13 +17,12 @@ shortTitle: Criar & testar Swift {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introdução Este guia mostra como criar e testar um pacote do Swift. -{% ifversion ghae %} To build and test your Swift project on {% data variables.product.prodname_ghe_managed %}, you will need to create a custom operating system image that includes the necessary Swift dependencies. Para obter instruções sobre como garantir que o seu {% data variables.actions.hosted_runner %} tem o software necessário instalado, consulte "[Criar imagens personalizadas](/actions/using-github-hosted-runners/creating-custom-images)". +{% ifversion ghae %} Para criar e testar seu projeto Swift em {% data variables.product.prodname_ghe_managed %}, você deverá criar uma imagem personalizada do sistema operacional que inclua as dependências necessárias do Swift. Para obter instruções sobre como garantir que o seu {% data variables.actions.hosted_runner %} tem o software necessário instalado, consulte "[Criar imagens personalizadas](/actions/using-github-hosted-runners/creating-custom-images)". Executores hospedados em {% else %}{% data variables.product.prodname_dotcom %} têm um cache de ferramentas com software pré-instalado e os executores Ubuntu e macOS incluem as dependências para construir pacotes Swift. Para obter uma lista completa do software atualizado e das versões pré-instaladas do Swift e do Xcode, consulte "[Sobre executores hospedados pelo GitHub](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-software)."{% endif %} ## Pré-requisitos diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md index 5209e0c630..8878063cdc 100644 --- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md +++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md @@ -21,7 +21,6 @@ shortTitle: Criar & testar os aplicativos Xamarin {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introdução 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 c133dce634..ebba9961fb 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 @@ -1,7 +1,7 @@ --- -title: Automating builds and tests -shortTitle: Build and test -intro: 'You can automatically build and test your projects with {% data variables.product.prodname_actions %}.' +title: Automatizando criações e testes +shortTitle: Criar e testar +intro: 'Você pode criar e testar automaticamente os seus projetos com {% data variables.product.prodname_actions %}.' versions: fpt: '*' ghes: '*' diff --git a/translations/pt-BR/content/actions/creating-actions/about-custom-actions.md b/translations/pt-BR/content/actions/creating-actions/about-custom-actions.md index 50dbd9c698..60d24c2078 100644 --- a/translations/pt-BR/content/actions/creating-actions/about-custom-actions.md +++ b/translations/pt-BR/content/actions/creating-actions/about-custom-actions.md @@ -1,5 +1,5 @@ --- -title: About custom actions +title: Sobre ações personalizadas intro: 'Ações são tarefas individuais que você pode combinar para criar trabalhos e personalizar o seu fluxo de trabalho. Você pode criar suas próprias ações ou usar e personalizar ações compartilhadas pela comunidade {% data variables.product.prodname_dotcom %}.' product: '{% data reusables.gated-features.actions %}' redirect_from: @@ -20,9 +20,8 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -## About custom actions +## Sobre ações personalizadas Você pode criar ações gravando códigos personalizados que interajam com o seu repositório da maneira que você quiser, inclusive fazendo integrações com as APIs do {% data variables.product.prodname_dotcom %} e qualquer API de terceiros disponível publicamente. Por exemplo, as ações podem publicar módulos npm, enviar alertas SMS quando problemas urgentes forem criados ou implantar códigos prontos para produção. @@ -36,11 +35,11 @@ As ações podem ser executadas diretamente em uma máquina ou em um contêiner Você pode compilar ações do contêiner Docker e JavaScript. As ações exigem um arquivo de metadados para a definição de entradas, saídas e ponto de entrada principal para sua ação. O nome do arquivo dos metadados deve ser `action.yml` ou `action.yaml`. Para obter mais informações, consulte "[Sintaxe de metadados para o {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions)". -| Tipo | Sistema operacional | -| ----------------- | --------------------- | -| Contêiner Docker | Linux | -| JavaScript | Linux, macOS, Windows | -| Composite Actions | Linux, macOS, Windows | +| Tipo | Sistema operacional | +| ---------------- | --------------------- | +| Contêiner Docker | Linux | +| JavaScript | Linux, macOS, Windows | +| Ações compostas | Linux, macOS, Windows | ### Ações de contêiner docker @@ -58,9 +57,9 @@ As ações do JavaScript podem ser executadas diretamente em uma máquina execut Se você estiver desenvolvendo um projeto Node.js, o kit de ferramentas {% data variables.product.prodname_actions %} fornecerá pacotes que você poderá usar para acelerar o desenvolvimento. Para obter mais informações, consulte o repositório [ações/conjuntos de ferramentas](https://github.com/actions/toolkit). -### Composite Actions +### Ações compostas -A _composite_ action allows you to combine multiple workflow steps within one action. For example, you can use this feature to bundle together multiple run commands into an action, and then have a workflow that executes the bundled commands as a single step using that action. To see an example, check out "[Creating a composite action](/actions/creating-actions/creating-a-composite-action)". +Uma ação _composta_ permite que você combine várias etapas do fluxo de trabalho em uma ação. Por exemplo, você pode usar esse recurso para juntar vários comandos executando em uma ação e, em seguida, ter um fluxo de trabalho que executa os comandos empacotados como uma única etapa usando essa ação. Para ver um exemplo, confira "[Criar uma ação composta](/actions/creating-actions/creating-a-composite-action)". ## Definir o local da ação @@ -152,7 +151,7 @@ Se você planeja compartilhar sua ação publicamente, é recomendável criar um ### Vantagens do GitHub Actions e dos aplicativos GitHub -While both {% data variables.product.prodname_actions %} and {% data variables.product.prodname_github_apps %} provide ways to build automation and workflow tools, they each have strengths that make them useful in different ways. +Embora {% data variables.product.prodname_actions %} e {% data variables.product.prodname_github_apps %} forneçam maneiras de criar automação e ferramentas de fluxo de trabalho, cada um tem pontos fortes que os tornam úteis de maneiras diferentes. {% data variables.product.prodname_github_apps %}: * Executa, de modo persistente, e pode reagir a eventos rapidamente. diff --git a/translations/pt-BR/content/actions/creating-actions/creating-a-composite-action.md b/translations/pt-BR/content/actions/creating-actions/creating-a-composite-action.md index 65e48d896d..34787a4a7b 100644 --- a/translations/pt-BR/content/actions/creating-actions/creating-a-composite-action.md +++ b/translations/pt-BR/content/actions/creating-actions/creating-a-composite-action.md @@ -1,6 +1,6 @@ --- -title: Creating a composite action -intro: 'In this guide, you''ll learn how to build a composite action.' +title: Criar uma ação composta +intro: 'Neste guia, você aprenderá a criar uma ação composta.' product: '{% data reusables.gated-features.actions %}' redirect_from: - /actions/creating-actions/creating-a-composite-run-steps-action @@ -11,18 +11,17 @@ versions: type: tutorial topics: - Action development -shortTitle: Composite action +shortTitle: Ação composta --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introdução -In this guide, you'll learn about the basic components needed to create and use a packaged composite action. Para manter o foco deste guia nos componentes necessários para empacotar a ação, a funcionalidade do código da ação é mínima. A ação imprime "Hello World" e "Goodbye", ou, se você fornecer um nome personalizado, imprimirá "Hello [who-to-greet]" e "Goodbye". A ação também mapeia um número aleatório para a variável de saída `random-number` e executa um script denominado `goodbye.sh`. +Neste guia, você aprenderá os componentes básicos necessários para criar e usar uma ação composta empacotada. Para manter o foco deste guia nos componentes necessários para empacotar a ação, a funcionalidade do código da ação é mínima. A ação imprime "Hello World" e "Goodbye", ou, se você fornecer um nome personalizado, imprimirá "Hello [who-to-greet]" e "Goodbye". A ação também mapeia um número aleatório para a variável de saída `random-number` e executa um script denominado `goodbye.sh`. -Once you complete this project, you should understand how to build your own composite action and test it in a workflow. +Ao concluir este projeto, você entenderá como criar a sua própria ação composta e testá-la em um fluxo de trabalho. {% data reusables.github-actions.context-injection-warning %} @@ -30,7 +29,7 @@ Once you complete this project, you should understand how to build your own comp Antes de começar, você criará um repositório {% data variables.product.product_name %}. -1. Crie um repositório público novo no {% data variables.product.product_location %}. You can choose any repository name, or use the following `hello-world-composite-action` example. É possível adicionar esses arquivos após push do projeto no {% data variables.product.product_name %}. Para obter mais informações, consulte "[Criar um repositório novo](/articles/creating-a-new-repository)". +1. Crie um repositório público novo no {% data variables.product.product_location %}. Você pode escolher qualquer nome de repositório ou usar o exemplo `hello-world-composite-action`. É possível adicionar esses arquivos após push do projeto no {% data variables.product.product_name %}. Para obter mais informações, consulte "[Criar um repositório novo](/articles/creating-a-new-repository)". 1. Clone o repositório para seu computador. Para obter mais informações, consulte "[Clonar um repositório](/articles/cloning-a-repository)". @@ -40,7 +39,7 @@ Antes de começar, você criará um repositório {% data variables.product.produ cd hello-world-composite-action ``` -2. In the `hello-world-composite-action` repository, create a new file called `goodbye.sh`, and add the following example code: +2. No repositório `hello-world-composite-action`, crie um novo arquivo denominado `goodbye.sh` e adicione o seguinte código de exemplo: ```bash echo "Goodbye" @@ -61,7 +60,7 @@ Antes de começar, você criará um repositório {% data variables.product.produ ## Criar um arquivo de metadados de ação -1. In the `hello-world-composite-action` repository, create a new file called `action.yml` and add the following example code. For more information about this syntax, see "[`runs` for a composite actions](/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-composite-actions)". +1. No repositório `hello-world-composite-action`, crie um novo arquivo denominado `action.yml` e adicione o código de exemplo a seguir. Para obter mais informações sobre essa sintaxe, consulte "[`executa` para uma ação composta](/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-composite-actions)". {% raw %} **action.yml** @@ -89,9 +88,9 @@ Antes de começar, você criará um repositório {% data variables.product.produ shell: bash ``` {% endraw %} - Este arquivo define a entrada de `who-to-greet`, mapeia o número aleatório gerado para a variável de saída `random-number` e executa o script `goodbye.sh`. It also tells the runner how to execute the composite action. + Este arquivo define a entrada de `who-to-greet`, mapeia o número aleatório gerado para a variável de saída `random-number` e executa o script `goodbye.sh`. Também informa ao executor como executar a ação composta. - For more information about managing outputs, see "[`outputs` for a composite action](/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-composite-actions)". + Para obter mais informações sobre o gerenciamento de saídas, consulte "[`outputs` para uma ação composta](/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-composite-actions). Para obter mais informações sobre como usar `github.action_path`, consulte "[`github context`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)". @@ -114,7 +113,7 @@ Antes de começar, você criará um repositório {% data variables.product.produ O código de fluxo de trabalho a seguir usa a ação hello world completa que você fez em "[Criando uma ação arquivo de metadados](/actions/creating-actions/creating-a-composite-action#creating-an-action-metadata-file)". -Copy the workflow code into a `.github/workflows/main.yml` file in another repository, but replace `actions/hello-world-composite-action@v1` with the repository and tag you created. Você também pode substituir a entrada `who-to-greet` pelo seu nome. +Copie o código do fluxo de trabalho em um arquivo `.github/workflows/main.yml` em outro repositório, mas substitua `actions/hello-world-composite-action@v1` pelo repositório e pela tag que você criou. Você também pode substituir a entrada `who-to-greet` pelo seu nome. {% raw %} **.github/workflows/main.yml** diff --git a/translations/pt-BR/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/pt-BR/content/actions/creating-actions/creating-a-docker-container-action.md index 587aa7409a..9e0af7c1ff 100644 --- a/translations/pt-BR/content/actions/creating-actions/creating-a-docker-container-action.md +++ b/translations/pt-BR/content/actions/creating-actions/creating-a-docker-container-action.md @@ -20,7 +20,6 @@ shortTitle: Ação de contêiner do Docker {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introdução diff --git a/translations/pt-BR/content/actions/creating-actions/creating-a-javascript-action.md b/translations/pt-BR/content/actions/creating-actions/creating-a-javascript-action.md index 231a7b1f23..a14e782e26 100644 --- a/translations/pt-BR/content/actions/creating-actions/creating-a-javascript-action.md +++ b/translations/pt-BR/content/actions/creating-actions/creating-a-javascript-action.md @@ -20,7 +20,6 @@ shortTitle: Ação do JavaScript {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introdução diff --git a/translations/pt-BR/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/translations/pt-BR/content/actions/creating-actions/dockerfile-support-for-github-actions.md index ace2685b59..ab94e460cf 100644 --- a/translations/pt-BR/content/actions/creating-actions/dockerfile-support-for-github-actions.md +++ b/translations/pt-BR/content/actions/creating-actions/dockerfile-support-for-github-actions.md @@ -1,6 +1,6 @@ --- title: Suporte do arquivo Docker para GitHub Actions -shortTitle: Dockerfile support +shortTitle: Suporte ao Dockerfile intro: 'Ao criar um "arquivo Docker" para uma ação do contêiner Docker, você deverá ter em mente como algumas instruções do Docker interagem com o GitHub Actions e com um arquivo de metadados da ação.' product: '{% data reusables.gated-features.actions %}' redirect_from: @@ -14,7 +14,6 @@ type: reference {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Sobre as instruções do arquivo Docker diff --git a/translations/pt-BR/content/actions/creating-actions/index.md b/translations/pt-BR/content/actions/creating-actions/index.md index aef710f3b2..e924d9c8fc 100644 --- a/translations/pt-BR/content/actions/creating-actions/index.md +++ b/translations/pt-BR/content/actions/creating-actions/index.md @@ -24,4 +24,3 @@ children: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} 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 5a7005f8b4..d27200a991 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 @@ -17,7 +17,6 @@ type: reference {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Sobre sintaxe YAML para o {% data variables.product.prodname_actions %} @@ -27,11 +26,11 @@ Arquivos de metadados de ação usam a sintaxe YAML. Se você não souber o que ## `name` -**Necessário**: nome de sua ação. O {% data variables.product.prodname_dotcom %} exibe o `name` (nome) na aba **Actions** (Ações) para facilitar a identificação visual das ações em cada trabalho. +**Necessário**: O nome de sua ação. O {% data variables.product.prodname_dotcom %} exibe o `nome` na aba **Ações** para facilitar a identificação visual das ações em cada trabalho. ## `autor` -**Opcional**: nome do autor da ação. +**Opcional**: O nome do autor da ação. ## `descrição` @@ -74,7 +73,7 @@ Por exemplo, se um fluxo de trabalho definiu as entradas `numOctocats` e `octoca ### `inputs..required` -**Necessário**: um `boolean` (booleano) para indicar se a ação requer o parâmetro de entrada. Defina para `true` quando o parâmetro for necessário. +**Necessário**: um `booleano` para indicar se a ação exige o parâmetro de entrada. Defina para `true` quando o parâmetro for necessário. ### `inputs..default` @@ -106,7 +105,7 @@ saídas: **Necessário**: descrição de `string` do parâmetro de saída. -## `outputs` for composite actions +## `outputs` para ações compostas As **saídas** `opcionais` usam os mesmos parâmetros que `outputs.` e `outputs..description` (veja "[`saídas` para {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#outputs)"), mas também inclui o token do `valor`. @@ -131,7 +130,7 @@ runs: **Obrigatório** O valor com o qual o parâmetro de saída será mapeado. Você pode defini-lo como uma `string` ou uma expressão com contexto. Por exemplo, você pode usar o contexto das `etapas` para definir o `valor` de uma saída como o valor de saída de uma etapa. -For more information on how to use context syntax, see "[Contexts](/actions/learn-github-actions/contexts)." +Para obter mais informações sobre como usar a sintaxe de contexto, consulte "[Contextos](/actions/learn-github-actions/contexts)". ## `runs` para ações de JavaScript @@ -204,26 +203,26 @@ Por exemplo, este `cleanup.js` só será executado em executores baseados no Lin post-if: runner.os == 'linux' ``` -## `runs` for composite actions +## `runs` para ações compostas **Obrigatório** Configura o caminho para a ação composta, e o aplicativo usado para executar o código. ### `runs.using` -**Required** To use a composite action, set this to `"composite"`. +**Obrigatório** Para usar uma ação composta, defina-o como `"cmposto"`. ### `runs.steps` {% ifversion fpt or ghes > 3.2 or ghae-issue-4853 %} -**Required** The steps that you plan to run in this action. These can be either `run` steps or `uses` steps. +**Obrigatório** As etapas de que você planeja executar nesta ação. Elas podem ser etapas de `run` ou etapas de `uses`. {% else %} -**Required** The steps that you plan to run in this action. +**Obrigatório** As etapas de que você planeja executar nesta ação. {% endif %} #### `runs.steps[*].run` {% ifversion fpt or ghes > 3.2 or ghae-issue-4853 %} -**Optional** The command you want to run. Isso pode ser inline ou um script no seu repositório de ação: +**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: {% endif %} @@ -253,14 +252,14 @@ Para obter mais informações, consulte "[`github context`](/actions/reference/c #### `runs.steps[*].shell` {% ifversion fpt or ghes > 3.2 or ghae-issue-4853 %} -**Optional** The shell where you want to run the command. Você pode usar qualquer um dos shells listados [aqui](/actions/reference/workflow-syntax-for-github-actions#using-a-specific-shell). Required if `run` is set. +**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#using-a-specific-shell). 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#using-a-specific-shell). Required if `run` is set. +**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#using-a-specific-shell). Obrigatório se `run` estiver configurado. {% endif %} #### `runs.steps[*].name` -**Optional** The name of the composite step. +**Opcional** O nome da etapa composta. #### `runs.steps[*].id` @@ -268,7 +267,7 @@ Para obter mais informações, consulte "[`github context`](/actions/reference/c #### `runs.steps[*].env` -**Opcional** Define um `mapa` de variáveis de ambiente apenas para essa etapa. If you want to modify the environment variable stored in the workflow, use {% ifversion fpt or ghes > 2.22 or ghae %}`echo "{name}={value}" >> $GITHUB_ENV`{% else %}`echo "::set-env name={name}::{value}"`{% endif %} in a composite step. +**Opcional** Define um `mapa` de variáveis de ambiente apenas para essa etapa. Se você desejar modificar a variável de ambiente armazenada no fluxo de trabalho, use {% ifversion fpt or ghes > 2.22 or ghae %}`echo "{name}={value}" >> $GITHUB_ENV`{% else %}`echo "::set-env name={name}::{value}"`{% endif %} em uma etapa composta. #### `runs.steps[*].working-directory` @@ -277,14 +276,14 @@ Para obter mais informações, consulte "[`github context`](/actions/reference/c {% ifversion fpt or ghes > 3.2 or ghae-issue-4853 %} #### `runs.steps[*].uses` -**Optional** Selects an action to run as part of a step in your job. 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/). +**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/). É altamente recomendável incluir a versão da ação que você está usando ao especificar um número de tag Docker, SHA ou ref do Git. Se você não especificar uma versão, ela poderá interromper seus fluxos de trabalho ou causar um comportamento inesperado quando o proprietário da ação publicar uma atualização. - Usar o commit SHA de uma versão de ação lançada é a maneira mais garantida de obter estabilidade e segurança. - Usar a versão principal da ação permite receber correções importantes e patches de segurança sem perder a compatibilidade. Fazer isso também garante o funcionamento contínuo do fluxo de trabalho. - Usar o branch-padrão de uma ação pode ser conveniente, mas se alguém lançar uma nova versão principal com uma mudança significativa, seu fluxo de trabalho poderá ter problemas. -Algumas ações requerem entradas que devem ser definidas com a palavra-chave [`with`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepswith) (com). Revise o arquivo README da ação para determinar as entradas obrigatórias. +Algumas ações requerem entradas que devem ser definidas com a palavra-chave [`com`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepswith). Revise o arquivo README da ação para determinar as entradas obrigatórias. ```yaml runs: @@ -310,7 +309,7 @@ runs: #### `runs.steps[*].with` -**Optional** A `map` of the input parameters defined by the action. Cada parâmetro de entrada é um par chave/valor. Parâmetros de entrada são definidos como variáveis de ambiente. The variable is prefixed with INPUT_ and converted to upper case. +**Opcional** Um `mapa` dos parâmetros de entrada definidos pela ação. Cada parâmetro de entrada é um par chave/valor. Parâmetros de entrada são definidos como variáveis de ambiente. A variável é precedida por INPUT_ e convertida em letras maiúsculas. ```yaml runs: diff --git a/translations/pt-BR/content/actions/creating-actions/publishing-actions-in-github-marketplace.md b/translations/pt-BR/content/actions/creating-actions/publishing-actions-in-github-marketplace.md index 84a827afd3..692019c25a 100644 --- a/translations/pt-BR/content/actions/creating-actions/publishing-actions-in-github-marketplace.md +++ b/translations/pt-BR/content/actions/creating-actions/publishing-actions-in-github-marketplace.md @@ -12,8 +12,6 @@ type: how_to shortTitle: Publicar no GitHub Marketplace --- -{% data reusables.actions.ae-beta %} - Você deve aceitar os termos de serviço para publicar ações em {% data variables.product.prodname_marketplace %}. ## Sobre a publicação de ações diff --git a/translations/pt-BR/content/actions/creating-actions/setting-exit-codes-for-actions.md b/translations/pt-BR/content/actions/creating-actions/setting-exit-codes-for-actions.md index 5bc3626b00..ccabf6c08d 100644 --- a/translations/pt-BR/content/actions/creating-actions/setting-exit-codes-for-actions.md +++ b/translations/pt-BR/content/actions/creating-actions/setting-exit-codes-for-actions.md @@ -14,7 +14,6 @@ type: how_to {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Sobre os códigos de saída diff --git a/translations/pt-BR/content/actions/deployment/about-continuous-deployment.md b/translations/pt-BR/content/actions/deployment/about-continuous-deployment.md new file mode 100644 index 0000000000..9ea2efc6f5 --- /dev/null +++ b/translations/pt-BR/content/actions/deployment/about-continuous-deployment.md @@ -0,0 +1,41 @@ +--- +title: Sobre a implantação contínua +intro: 'Você pode criar fluxos de trabalho personalizados de implantação contínua (CD) diretamente no repositório de {% data variables.product.prodname_dotcom %} com {% data variables.product.prodname_actions %}.' +product: '{% data reusables.gated-features.actions %}' +versions: + fpt: '*' + ghes: '*' + ghae: '*' +type: overview +topics: + - CD +shortTitle: Implantação contínua +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +## Sobre a implantação contínua + +_Implantação contínua_ (CD) é a prática de usar a automação para publicar e implantar atualizações de software. Como parte do processo típico do CD, o código é automaticamente criado e testado antes da implantação. + +A implentação contínua é frequentemente acompanhada da integração contínua. Para obter mais informações sobre integração contínua, consulte "[Sobre integração contínua](/actions/guides/about-continuous-integration)". + +## Sobre a implantação contínua que usa {% data variables.product.prodname_actions %} + +É possível configurar um fluxo de trabalho de {% data variables.product.prodname_actions %} para implantar o produto do seu software. Para verificar se o produto funciona como esperado, seu fluxo de trabalho pode criar o código no repositório e executar seus testes antes da implantação. + +Você pode configurar seu fluxo de trabalho do CD para ser executado quando ocorrer um evento de {% data variables.product.product_name %} (por exemplo, quando o novo código é enviado para o branch padrão do seu repositório), em um cronograma definido, manualmente ou quando ocorre um evento externo usando o webhook de envio do repositório. Para obter mais informações sobre quando seu fluxo de trabalho pode ser executado, consulte "[Eventos que acionam fluxos de trabalho](/actions/reference/events-that-trigger-workflows)". + +{% data variables.product.prodname_actions %} fornece funcionalidades que dão mais controle sobre implantações. Por exemplo, você pode usar ambientes para exigir aprovação para um trabalho prosseguir, restringir quais branches podem acionar um fluxo de trabalho, ou limitar o acesso a segredos. Você pode usar concorrência para limitar o pipeline do CD até uma implantação em andamento e uma implantação pendente. Para obter mais informações sobre essas funcionalidades, consulte "[Implantando com GitHub Actions](/actions/deployment/deploying-with-github-actions)" e "[Usando ambientes para implantação](/actions/deployment/using-environments-for-deployment)". + +## Modelos de fluxo de trabalho e ações de terceiros + +{% data reusables.actions.cd-templates-actions %} + +## Leia mais + +- [Implantando com GitHub Actions](/actions/deployment/deploying-with-github-actions) +- [Usando ambientes para implantação](/actions/deployment/using-environments-for-deployment){% ifversion fpt %} +- "[Gerenciando cobrança para {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)" +{% endif %} diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-amazon-elastic-container-service.md b/translations/pt-BR/content/actions/deployment/deploying-to-amazon-elastic-container-service.md index eb119da197..c081e811aa 100644 --- a/translations/pt-BR/content/actions/deployment/deploying-to-amazon-elastic-container-service.md +++ b/translations/pt-BR/content/actions/deployment/deploying-to-amazon-elastic-container-service.md @@ -18,11 +18,10 @@ shortTitle: Implantar no Amazon ECS {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introdução -Este guia explica como usar {% data variables.product.prodname_actions %} para construir um aplicativo containerizado, fazer push no [Amazon Elastic Container Registry (ECR)](https://aws.amazon.com/ecr/) e fazer a implantação no [Amazon Elastic Container Service (ECS)](https://aws.amazon.com/ecs/). +Este guia explica como usar {% data variables.product.prodname_actions %} para construir um aplicativo containerizado, fazer push no [Amazon Elastic Container Registry (ECR)](https://aws.amazon.com/ecr/) e fazer a implantação no [Amazon Elastic Container Service (ECS)](https://aws.amazon.com/ecs/) quando uma versão é criada. Em cada nova versão no seu repositório de {% data variables.product.company_short %}, os fluxos de trabalho de {% data variables.product.prodname_actions %} criam e fazem push de uma nova imagem de contêiner para o Amazon ECR e, em seguida, implementa uma nova definição de tarefa para o Amazon ECS. @@ -66,14 +65,18 @@ Antes de criar seu fluxo de trabalho de {% data variables.product.prodname_actio Veja a documentação para cada ação usada abaixo para as políticas recomendadas de IAM para o usuário de IAM, bem como os métodos para lidar com as credenciais de acesso. +5. Opcionalmente, configure um ambiente de implantação. {% data reusables.actions.about-environments %} + ## Creating the workflow -Once you've completed the prerequisites, you can proceed with creating the workflow. +Após você ter atendido aos pré-requisitos, você poderá proceder com a criação do fluxo de trabalho. O fluxo de trabalho a seguir demonstra como construir uma imagem de contêiner e enviá-lo para o Amazon ECR. Em seguida, ele atualiza a definição da tarefa com o novo ID de imagem e implanta a definição da tarefa no Amazon ECS. Certifique-se de fornecer seus próprios valores para todas as variáveis na chave `env` do fluxo de trabalho. +{% data reusables.actions.delete-env-key %} + ```yaml{:copy} {% data reusables.actions.actions-not-certified-by-github-comment %} @@ -93,17 +96,11 @@ env: CONTAINER_NAME: MY_CONTAINER_NAME # set this to the name of the container in the # containerDefinitions section of your task definition -defaults: - run: - shell: bash - jobs: deploy: name: Deploy - runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae-next %} - permissions: - packages: write - contents: read{% endif %} + runs-on: ubuntu-latest + environment: production {% raw %}steps: - name: Checkout @@ -150,9 +147,10 @@ jobs: wait-for-service-stability: true{% endraw %} ``` - ## Recursos adicionais +Para o fluxo de trabalho inicial original, consulte [`aws.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/aws.yml) no repositório `starter-workflows` de {% data variables.product.prodname_actions %}. + Para mais informações sobre os serviços utilizados nestes exemplos, veja a seguinte documentação: * "[Práticas recomendadas de segurança no IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html)" na documentação da Amazon AWS. diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-azure-app-service.md b/translations/pt-BR/content/actions/deployment/deploying-to-azure-app-service.md index 339808933c..aff75bf9c2 100644 --- a/translations/pt-BR/content/actions/deployment/deploying-to-azure-app-service.md +++ b/translations/pt-BR/content/actions/deployment/deploying-to-azure-app-service.md @@ -18,7 +18,6 @@ shortTitle: Implantar no Azure App Service {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introdução @@ -68,13 +67,19 @@ Antes de criar seu fluxo de trabalho de {% data variables.product.prodname_actio No seu repositório {% data variables.product.prodname_dotcom %}, crie um segredo denominado `AZURE_WEBAPP_PUBLISH_PROFILE` que contém o conteúdo do perfil de publicação. Para obter mais informações sobre a criação de segredos, consulte "[Segredos criptografados](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)". +4. Para aplicativos Linux, adicione uma configuração de aplicativo denominada `WEBSITE_WEBDEPLOY_USE_SCM` e defina-a como verdadeiro no seu aplicativo. Para obter mais informações, consulte "[Configurar aplicativos no portal](https://docs.microsoft.com/en-us/azure/app-service/configure-common#configure-app-settings)" na documentação do Azure. + +5. Opcionalmente, configure um ambiente de implantação. {% data reusables.actions.about-environments %} + ## Criar o fluxo de trabalho Depois de preencher os pré-requisitos, você pode prosseguir com a criação do fluxo de trabalho. -O exemplo a seguir mostra como compilar, testar e implantar o projeto Node.js no Azure App Service. +O exemplo a seguir de fluxo de trabalho mostra como compilar, testar e implantar o projeto Node.js no Azure App Service quando uma versão é criada. -Certifique-se de definir `AZURE_WEBAPP_NAME` na chave de fluxo de trabalho `env` como o nome do aplicativo web que você criou. +Certifique-se de definir `AZURE_WEBAPP_NAME` na chave de fluxo de trabalho `env` como o nome do aplicativo web que você criou. Você também pode alterar `AZURE_WEBAPP_PACKAGE_PATH` se o caminho para o seu projeto não for a raiz do repositório e `NODE_VERSION` se você quiser usar uma versão de nó diferente de `10.x`. + +{% data reusables.actions.delete-env-key %} ```yaml{:copy} {% data reusables.actions.actions-not-certified-by-github-comment %} @@ -92,6 +97,8 @@ jobs: build-and-deploy: name: Build and Deploy runs-on: ubuntu-latest + environment: production + steps: - uses: actions/checkout@v2 @@ -120,6 +127,7 @@ jobs: Os seguintes recursos também podem ser úteis: -* For the original starter workflow, see [`azure.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository. +* Para o fluxo de trabalho inicial original, consulte [`azure.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure.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/en-us/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). diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-google-kubernetes-engine.md b/translations/pt-BR/content/actions/deployment/deploying-to-google-kubernetes-engine.md index f2857b2ce4..80e3496097 100644 --- a/translations/pt-BR/content/actions/deployment/deploying-to-google-kubernetes-engine.md +++ b/translations/pt-BR/content/actions/deployment/deploying-to-google-kubernetes-engine.md @@ -13,16 +13,15 @@ topics: - CD - Containers - Google Kubernetes Engine -shortTitle: Implantar no Kubernetes (GKE) +shortTitle: Implantar no Google Kubernetes Engine --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introdução -Este guia explica como usar {% data variables.product.prodname_actions %} para construir um aplicativo conteinerizado, fazer push no Google Container Registry (GCR) e fazer a implantação no Google Kubernetes Engine (GKE). +Este guia explica como usar {% data variables.product.prodname_actions %} para criar um aplicativo contêinerizado, fazer push no Google Container Registry (GCR) e implantar no Google Kubernetes Engine (GKE) quando uma versão for criada. O GKE é um serviço de cluster gerenciado do Kubernetes pelo Google Cloud que pode hospedar suas cargas de trabalho containerizadas na nuvem ou em seu próprio centro de dados. Para obter mais informações, consulte [Google Kubernetes Engine](https://cloud.google.com/kubernetes-engine). @@ -61,7 +60,7 @@ $ gcloud services enable \ ### Configurar uma conta de serviço e armazenar as suas credenciais -Este procedimento demonstra como criar a conta de serviço para sua integração com o GKE. Ele explica como criar a conta, adicionar funções, recuperar suas chaves, e armazená-las como um [secreto de repositório criptografado](/actions/reference/encrypted-secrets) codificado em base 64 denominado `GKE_SA_KEY`. +Este procedimento demonstra como criar a conta de serviço para sua integração com o GKE. Ele explica como criar a conta, adicionar funções, recuperar suas chaves, e armazená-las como um segredo de repositório criptografado codificado em base64 denominado `GKE_SA_KEY`. 1. Crie uma nova conta de serviço: {% raw %} @@ -91,22 +90,35 @@ Este procedimento demonstra como criar a conta de serviço para sua integração $ gcloud iam service-accounts keys create key.json --iam-account=$SA_EMAIL ``` {% endraw %} -1. Store the service account key as a secret named `GKE_SA_KEY`: +1. Armazenar a chave da conta de serviço como um segredo denominado `GKE_SA_KEY`: {% raw %} ``` $ export GKE_SA_KEY=$(cat key.json | base64) ``` {% endraw %} + Para obter mais informações sobre como armazenar um segredo, consulte "[Segredos criptografados](/actions/security-guides/encrypted-secrets)". + +### Armazenando o nome do seu projeto + +Armazene o nome do seu projeto como um segredo denominado `GKE_PROJECT`. Para obter mais informações sobre como armazenar um segredo, consulte "[Segredos criptografados](/actions/security-guides/encrypted-secrets)". ### (Opcional) Configurar kustomize Kustomize é uma ferramenta opcional usada para gerenciar especificações do YAML. Depois de criar um arquivo do _kustomization_, o fluxo de trabalho abaixo pode ser usado para definir dinamicamente os campos da imagem e adicionar o resultado ao `kubectl`. Para obter mais informações, consulte [uso de kustomize](https://github.com/kubernetes-sigs/kustomize#usage). +### (Opcional) Configure um ambiente de implantação + +{% data reusables.actions.about-environments %} + ## Criar o fluxo de trabalho Depois de preencher os pré-requisitos, você pode prosseguir com a criação do fluxo de trabalho. O fluxo de trabalho a seguir mostra como construir uma imagem de contêiner e como carregá-los no GCR. Em seguida, ele usa as ferramentas do Kubernetes (como `kubectl` e `kustomize`) para mover a imagem para a implantação do cluster. +Na chave `env`, altere o valor de `GKE_CLUSTER` para o nome do seu cluster, `GKE_ZONE` à sua zona de clustering. `DEPLOYMENT_NAME` ao nome da sua implantação e `IMAGE` ao nome da sua imagem. + +{% data reusables.actions.delete-env-key %} + ```yaml{:copy} {% data reusables.actions.actions-not-certified-by-github-comment %} @@ -127,8 +139,9 @@ jobs: setup-build-publish-deploy: name: Setup, Build, Publish, and Deploy runs-on: ubuntu-latest - steps: + environment: production + steps: - name: Checkout uses: actions/checkout@v2 @@ -138,7 +151,8 @@ jobs: service_account_key: {% raw %}${{ secrets.GKE_SA_KEY }}{% endraw %} project_id: {% raw %}${{ secrets.GKE_PROJECT }}{% endraw %} - # Configure docker to use the gcloud command-line tool as a credential helper + # Configure Docker to use the gcloud command-line tool as a credential + # helper for authentication - run: |- gcloud --quiet auth configure-docker @@ -166,7 +180,7 @@ jobs: # Set up kustomize - name: Set up Kustomize run: |- - curl --location https://github.com/kubernetes-sigs/kustomize/releases/download/kustomize%2Fv4.2.0/kustomize_v4.2.0_linux_amd64.tar.gz | tar xz + curl -sfLo kustomize https://github.com/kubernetes-sigs/kustomize/releases/download/v3.1.0/kustomize_3.1.0_linux_amd64 chmod u+x ./kustomize # Deploy the Docker image to the GKE cluster @@ -182,7 +196,7 @@ jobs: Para mais informações sobre as ferramentas usadas nesses exemplos, consulte a documentação a seguir: -* For the full starter workflow, see the ["Build and Deploy to GKE" workflow](https://github.com/actions/starter-workflows/blob/main/deployments/google.yml). +* Para o fluxo de trabalho inicial completo, consulte o [Fluxo de trabalho de "criar e implantar no GKE"](https://github.com/actions/starter-workflows/blob/main/deployments/google.yml). * Para mais fluxos de trabalho iniciais e código de acompanhamento, consulte o [fluxos de trabalho de exemplos de {% data variables.product.prodname_actions %} do Google](https://github.com/google-github-actions/setup-gcloud/tree/master/example-workflows/). * Mecanismo de personalização do YAML do Kubernetes: [Kustomize](https://kustomize.io/). * "[Implantarum aplicativo web conteinerizado](https://cloud.google.com/kubernetes-engine/docs/tutorials/hello-app)" na documentação do Google Kubernetes Engine . diff --git a/translations/pt-BR/content/actions/deployment/deploying-with-github-actions.md b/translations/pt-BR/content/actions/deployment/deploying-with-github-actions.md new file mode 100644 index 0000000000..ace08e9f7d --- /dev/null +++ b/translations/pt-BR/content/actions/deployment/deploying-with-github-actions.md @@ -0,0 +1,173 @@ +--- +title: Implantando com GitHub Actions +intro: Aprenda a controlar imolantações com funcionalidades como ambientes e simultaneidade. +product: '{% data reusables.gated-features.actions %}' +versions: + fpt: '*' + ghes: '>=3.1' + ghae: '*' +type: overview +topics: + - CD +shortTitle: Implantar com GitHub Actions +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +## Introdução + +{% data variables.product.prodname_actions %} oferece funcionalidades que permitem que você controle implantações. Você pode: + +- Acionar fluxos de trabalho com uma série de eventos. +- Configurar ambientes para definir regras antes que um trabalho possa prosseguir e limitar o acesso a segredos. +- Usar a simultaneidade para controlar o número de implantações em execução por vês. + +Para obter mais informações sobre a implantação contínua, consulte "[Sobre a implantação contínua](/actions/deployment/about-continuous-deployment)". + +## Pré-requisitos + +Você deve estar familiarizado com a sintaxe de {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Aprenda {% data variables.product.prodname_actions %}](/actions/learn-github-actions)". + +## Acionando a sua implantação + +Você pode usar uma série de eventos para acionar seu fluxo de trabalho de implantação. Alguns dos mais comuns são: `pull_request`, `push`, `release` e `workflow_despatch`. + +Por exemplo, um fluxo de trabalho com os seguintes gatilhos é executado sempre que: + +- Há um push para o branch `principal`. +- Um pull request direcionado ao branch `principal` está aberto, sincronizado ou reaberto. +- Uma versão foi criada. +- Alguém a aciona manualmente. + +```yaml +on: + push: + branches: + - main + pull_request: + branches: + - main + release: + types: + - created + workflow_dispatch: +``` + +Para obter mais informações, consulte "[Eventos que acionam fluxos de trabalho](/actions/reference/events-that-trigger-workflows)". + +## Usar ambientes + +{% data reusables.actions.about-environments %} + +## Usando simultaneidade + +A moeda garante que apenas um único trabalho ou fluxo de trabalho que usa o mesmo grupo de concorrência seja executado de cada vez. Você pode usar a concorrência para que um ambiente tenha, no máximo, uma implantação em andamento e uma implantação pendente por vez. + +{% note %} + +**Observação:** `simultaneidade` e `ambiente` não estão conectados. O valor da simultaneidade pode ser qualquer regra; não precisa ser o nome de um ambiente. Além disso, se outro fluxo de trabalho usar o mesmo ambiente, mas não especificar a equivalência, esse fluxo de trabalho não estará sujeito a nenhuma regra de simultaneidade. + +{% endnote %} + +Por exemplo, quando o fluxo de trabalho a seguir é executado, ele será pausado com o status `pendente` se algum trabalho ou fluxo de trabalho que usa a simultaneidade de `produção` estiver em andamento. Ele também cancelará qualquer trabalho ou fluxo de trabalho que usar o grupo de simultaneidade de `produção` e tiver o status `pendente`. Isto significa que haverá o máximo de uma execução e um trabalho pendente ou fluxo de trabalho no qual usa o grupo de concorrência `de produção`. + +```yaml +name: Deployment + +concurrency: production + +on: + push: + branches: + - main + +jobs: + deployment: + runs-on: ubuntu-latest + environment: production + steps: + - name: deploy + # ...deployment-specific steps +``` + +Você também pode especificar simultaneidade no nível do trabalho. Isso permitirá que outras tarefas no fluxo de trabalho prossigam mesmo se o trabalho simultâneo estará `pendente`. + +```yaml +name: Deployment + +on: + push: + branches: + - main + +jobs: + deployment: + runs-on: ubuntu-latest + environment: production + concurrency: production + steps: + - name: deploy + # ...deployment-specific steps +``` + +Você também pode usar o `cancel-in-progress` para cancelar qualquer trabalho ou fluxo de trabalho atualmente em execução no mesmo grupo de concorrência. + +```yaml +name: Deployment + +concurrency: + group: production + cancel-in-progress: true + +on: + push: + branches: + - main + +jobs: + deployment: + runs-on: ubuntu-latest + environment: production + steps: + - name: deploy + # ...deployment-specific steps +``` + +## Visualizar histórico de implantação + +Quando um fluxo de trabalho de {% data variables.product.prodname_actions %} é implantado em um ambiente, o ambiente é exibido na página principal do repositório. Para obter mais informações sobre a visualização de implantações em ambientes, consulte "[Visualizando histórico de implantação](/developers/overview/viewing-deployment-history)". + +## Monitoramento de fluxo de trabalho + +Cada execução de fluxo de trabalho gera um gráfico em tempo real que ilustra o progresso da execução. Você pode usar este gráfico para monitorar e depurar implantações. Para obter mais informações, "[Usando o gráfico de visualização](/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph)". + +Você também pode visualizar os registros de cada execução do fluxo de trabalho e o histórico de execuções do fluxo de trabalho. Para obter mais informações, consulte "[Visualizar histórico de execução de fluxo de trabalho](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)". + +## Rastreando implantações por meio de aplicativos + +{% ifversion fpt %} +Se a sua conta pessoal ou organização de {% data variables.product.product_name %} estiver integrada ao Microsoft Teams ou Slack, você pode acompanhar as implantações que usam ambientes por meio desses programas. Por exemplo, você pode receber notificações por meio do aplicativo quando uma implantação estiver pendente de aprovação, quando uma implantação for aprovada, ou quando o status de implantação for alterado. Para obter mais informações sobre integração do Microsoft Teams ou Slack, consulte "[Extensões e integrações do GitHub](/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations#team-communication-tools)". +{% endif %} + +Você também pode criar um aplicativo que usa webhooks de status de implantação e implantação para rastrear implantações. {% data reusables.actions.environment-deployment-event %} Para obter mais informações, consulte "[Apps](/developers/apps)" e "[Eventos e cargas do Webhook](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#deployment)." + +{% ifversion fpt or ghes %} + +## Escolhendo um corredor + +Você pode executar seu fluxo de trabalho de implantação em executores hospedados em {% data variables.product.product_name %} ou em executores auto-hospedados. O tráfego dos executores hospedados em {% data variables.product.product_name %} 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.product_name %} 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)." + +{% endif %} + +## Exibindo um selo de status + +Você pode usar um selo de status para exibir o status do seu fluxo de trabalho de implantação. {% data reusables.repositories.actions-workflow-status-badge-intro %} + +Para obter mais informações, consulte "[Adicionando um selo de status do fluxo de trabalho](/actions/managing-workflow-runs/adding-a-workflow-status-badge)". + +## Próximas etapas + +Este artigo mostrou as funcionalidades de {% data variables.product.prodname_actions %} que você pode adicionar aos seus fluxos de trabalho de implantação. + +{% data reusables.actions.cd-templates-actions %} diff --git a/translations/pt-BR/content/actions/deployment/index.md b/translations/pt-BR/content/actions/deployment/index.md index 5e60fcc9e6..e1b8133dbd 100644 --- a/translations/pt-BR/content/actions/deployment/index.md +++ b/translations/pt-BR/content/actions/deployment/index.md @@ -1,16 +1,19 @@ --- title: Implantação shortTitle: Implantação -intro: 'Automatically deploy projects with {% data variables.product.prodname_actions %}.' +intro: 'Implantar projetos automaticamente com {% data variables.product.prodname_actions %}.' versions: fpt: '*' ghes: '*' ghae: '*' children: + - /about-continuous-deployment + - /deploying-with-github-actions + - /using-environments-for-deployment + - /viewing-deployment-history - /deploying-to-amazon-elastic-container-service - /deploying-to-azure-app-service - /deploying-to-google-kubernetes-engine - /installing-an-apple-certificate-on-macos-runners-for-xcode-development - - /environments --- diff --git a/translations/pt-BR/content/actions/deployment/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md b/translations/pt-BR/content/actions/deployment/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md index 454d96e437..e0ef8f109e 100644 --- a/translations/pt-BR/content/actions/deployment/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md +++ b/translations/pt-BR/content/actions/deployment/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md @@ -17,7 +17,6 @@ shortTitle: Aplicativos Sign Xcode {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introdução diff --git a/translations/pt-BR/content/actions/deployment/using-environments-for-deployment.md b/translations/pt-BR/content/actions/deployment/using-environments-for-deployment.md new file mode 100644 index 0000000000..1e2e9d498d --- /dev/null +++ b/translations/pt-BR/content/actions/deployment/using-environments-for-deployment.md @@ -0,0 +1,126 @@ +--- +title: Usando ambientes para implantação +shortTitle: Usar ambientes para implantação +intro: Você pode configurar ambientes com regras de proteção e segredos. Um trabalho de fluxo de trabalho que faz referência a um ambiente deve seguir quaisquer regras de proteção para o ambiente antes de executar ou acessar os segredos do ambiente. +product: '{% data reusables.gated-features.environments %}' +miniTocMaxHeadingLevel: 3 +redirect_from: + - /actions/reference/environments + - /actions/deployment/environments +versions: + fpt: '*' + ghes: '>=3.1' + ghae: '*' +--- + + +## Sobre ambientes + +Os ambientes são usados para descrever um alvo geral de implantação como `produção`, `preparo` ou `desenvolvimento`. Quando um fluxo de trabalho de {% data variables.product.prodname_actions %} é implantado em um ambiente, o ambiente é exibido na página principal do repositório. Para obter mais informações sobre a visualização de implantações em ambientes, consulte "[Visualizando histórico de implantação](/developers/overview/viewing-deployment-history)". + +Você pode configurar ambientes com regras de proteção e segredos. Quando um trabalho de fluxo de trabalho faz referência a um ambiente, o trabalho não será iniciado até que todas as regras de proteção do ambiente sejam aprovadas. Um trabalho também não pode acessar segredos definidos em ambiente até que todas as regras de proteção do ambiente sejam aprovadas. + +{% ifversion fpt %} +{% note %} + +**Observação:** Se você não usar {% data variables.product.prodname_ghe_cloud %} e converter um repositório de público em privado, todas as regras de proteção configuradas ou segredos de ambiente serão ignorados e você não poderá de configurar nenhum ambiente. Se você converter seu repositório de volta para público, você terá acesso a todas as regras de proteção e segredos de ambiente previamente configurados. {% data reusables.enterprise.link-to-ghec-trial %} + +{% endnote %} +{% endif %} + +## Regras de proteção de ambiente + +As normas de proteção do ambiente exigem a aprovação de condições específicas antes que um trabalho que faz referência ao ambiente possa prosseguir. {% ifversion fpt or ghae-next or ghes > 3.1 %}Você pode usar regras de proteção do ambiente para exigir uma aprovação manual, atrasar um trabalho ou restringir o ambiente a certos branches.{% else %}Você pode usar as regras de proteção de ambiente para exigir uma aprovação manual ou atrasar um trabalho.{% endif %} + +### Revisores necessários + +Use os revisores necessários para exigir que uma pessoa ou equipe específica aprove os trabalhos do fluxo de trabalho que fazem referência ao ambiente. Você pode listar até seis usuários ou equipes como revisores. Os revisores devem ter, pelo menos, acesso de leitura ao repositório. Apenas um dos revisores precisam aprovar o trabalho para que prossiga. + +Para obter mais informações sobre os trabalhos de revisão que fazem referência a um ambiente com os revisores necessários, consulte "[Revisar implantações](/actions/managing-workflow-runs/reviewing-deployments)". + +### Temporizador de espera + +Use o temporizador de espera para atrasar o trabalho por um período específico de tempo depois que o trabalho for inicialmente acionado. O tempo (em minutos) deve ser um número inteiro entre 0 e 43.200 (30 dias). + +{% ifversion fpt or ghae-next or ghes > 3.1 %} +### Implementar branches + +Use os branches de implantação para restringir quais branches podem ser implementados no ambiente. Abaixo, estão as opções para branches de implantação para um ambiente: + +* **Todos os branches**: Todos os branches no repositório podem implantar no ambiente. +* **Branches protegidos**: Somente branches com regras de proteção de branch habilitadas podem implementar no ambiente. Se nenhuma regra de proteção de branch for definida para qualquer branch no repositório, todos os branches poderão implantar. Para obter mais informações sobre as regras de proteção de branches, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches)". +* **Branches selecionados**: Somente branches que correspondem a seus padrões de nome especificados podem implantar no ambiente. + + Por exemplo, se você especificar `releases/*` como uma regra de implantação de branch, apenas os branches cujo nome começa com `releases/` poderão fazer a implantação no ambiente. (Caracteres curinga não correspondem a `/`. Para corresponder aos branches que começam com `release/` e contêm uma única barra adicional, use `release/*/*`.) Se você adicionar `main` como uma regra de branch de implantação, um branch denominado `main` também poderá ser implantado no ambiente. Para obter mais informações sobre opções de sintaxe para branches de implantação, consulte a [Documentação File.fnmatch do Ruby](https://ruby-doc.org/core-2.5.1/File.html#method-c-fnmatch). +{% endif %} +## Segredos de ambiente + +Os segredos armazenados em um ambiente só estão disponíveis para trabalhos de fluxo de trabalho que fazem referência ao ambiente. Se o ambiente exigir aprovação, um trabalho não poderá acessar segredos de ambiente até que um dos revisores necessários o aprove. Para obter mais informações sobre segredos, consulte "[Segredos criptografados](/actions/reference/encrypted-secrets)". + +{% note %} + +**Observação:** Os fluxos de trabalho executados em executores auto-hospedados não são executados em um contêiner isolado, mesmo que usem ambientes. Os segredos de ambiente devem ser tratados com o mesmo nível de segurança que os segredos do repositório e da organização. Para obter mais informações, consulte "[Enrijecimento de segurança para o GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#hardening-for-self-hosted-runners)". + +{% endnote %} + +## Criar um ambiente + +{% data reusables.github-actions.permissions-statement-environment %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.github-actions.sidebar-environment %} +{% data reusables.github-actions.new-environment %} +{% data reusables.github-actions.name-environment %} +1. Opcionalmente, especifique as pessoas ou equipes que devem aprovar os trabalhos do fluxo de trabalho que usam esse ambiente. + 1. Selecione **Revisores necessários**. + 1. Insira até até 6 pessoas ou equipes. Apenas um dos revisores precisam aprovar o trabalho para que prossiga. + 1. Clique **Regras de proteção do salvamento**. +2. Opcionalmente, especifique o tempo a esperar antes de permitir que os trabalhos do fluxo de trabalho que usam esse ambiente prossigam. + 1. Selecione **Temporizador de espera**. + 1. Insira o número de minutos para esperar. + 1. Clique **Regras de proteção do salvamento**. +3. Opcionalmente, especifique quais branches podem implantar neste ambiente. Para obter mais informações sobre os valores possíveis, consulte "[Ramificações de implantação](#deployment-branches)". + 1. Selecione a opção desejada no menu suspenso dos **Branches de implantação**. + 1. Se escolheu **Branches selecionados**, digite os padrões de nome do branch que você deseja permitir. +4. Opcionalmente, adicione segredos de ambiente. Esses segredos só estão disponíveis para trabalhos de fluxo de trabalho que usam o ambiente. Além disso, os trabalhos do fluxo de trabalho que usam este ambiente só podem acessar esses segredos após todas as regras configuradas (por exemplo, revisores obrigatórios). Para obter mais informações sobre segredos, consulte "[Segredos criptografados](/actions/reference/encrypted-secrets)". + 1. Em **Segredos do ambiente**, clique em **Adicionar segredo**. + 1. Insira o nome do segredo. + 1. Insira o valor do segredo. + 1. Clique em **Add secret** (Adicionar segredo). + +{% ifversion fpt or ghae-next or ghes > 3.1 %}Você também pode criar e configurar ambientes por meio da API REST. Para obter mais informações, consulte "[Ambientes](/rest/reference/repos#environments)" e "[Segredos](/rest/reference/actions#secrets)."{% endif %} + +Executar um fluxo de trabalho que faz referência a um ambiente que não existe criará um ambiente com o nome referenciado. O novo ambiente não terá nenhuma regra de proteção ou segredos configurados. Qualquer pessoa que possa editar fluxos de trabalho no repositório pode criar ambientes por meio de um arquivo de fluxo de trabalho, mas apenas os administradores do repositório podem configurar o ambiente. + +## Usando um ambiente + +Cada trabalho em um fluxo de trabalho pode fazer referência a um único ambiente. Todas as regras de proteção configuradas para o ambiente têm de ser aprovadas antes que um trabalho de referência ao ambiente seja enviado a um executor. O trabalho só pode acessar os segredos do ambiente depois que for enviado para um executor. + +Quando um fluxo de trabalho faz referência a um ambiente, o ambiente aparecerá nas implantações do repositório. Para obter mais informações sobre a visualização de implementações atuais e anteriores, consulte "[Visualizar histórico de implantação](/developers/overview/viewing-deployment-history)". + +{% data reusables.actions.environment-example %} + +## Excluir um ambiente + +{% data reusables.github-actions.permissions-statement-environment %} + +A exclusão de um ambiente apagará todos os segredos e regras de proteção associados ao ambiente. Todos os trabalhos que estejam atualmente em espera devido às regras de proteção do ambiente eliminado falharão automaticamente. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.github-actions.sidebar-environment %} +1. Ao lado do ambiente que você deseja excluir, clique em {% octicon "trash" aria-label="The trash icon" %}. +2. Clique em **Eu entendi, exclua este ambiente**. + +{% ifversion fpt or ghae-next or ghes > 3.1 %}Você também pode excluir ambientes por meio da API REST. Para obter mais informações, consulte "[Ambientes](/rest/reference/repos#environments)."{% endif %} + +## Como os ambientes relacionam-se com as implantações + +{% data reusables.actions.environment-deployment-event %} + +Você pode acessar esses objetos por meio da API REST ou API do GraphQL. Você também pode assinar esses eventos de webhook. Para obter mais informações, consulte "[Repositórios](/rest/reference/repos#deployments)" (API REST), "[Objetos](/graphql/reference/objects#deployment)" (GraphQL API) ou "[Eventos de webhook e cargas](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#deployment)". + +## Próximas etapas + +{% data variables.product.prodname_actions %} fornece várias funcionalidades para gerenciar suas implantações. Para obter mais informações, consulte "[Implantando com o GitHub Actions](/actions/deployment/deploying-with-github-actions)". diff --git a/translations/pt-BR/content/actions/deployment/viewing-deployment-history.md b/translations/pt-BR/content/actions/deployment/viewing-deployment-history.md new file mode 100644 index 0000000000..9c710e5939 --- /dev/null +++ b/translations/pt-BR/content/actions/deployment/viewing-deployment-history.md @@ -0,0 +1,27 @@ +--- +title: Visualizar histórico de implantação +intro: Veja as implantações atuais e anteriores para o seu repositório. +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - API +shortTitle: Ver histórico de implantação +redirect_from: + - /developers/overview/viewing-deployment-history +--- + + +Você pode realizar implantações por meio de de {% ifversion fpt or ghae or ghes > 3.0 %}{% data variables.product.prodname_actions %} e ambientes ou com {% endif %}a API REST e aplicativos de terceiros. {% ifversion fpt or ghae ghes > 3.0 %}Para obter mais informações sobre o uso de ambientes para implantar com {% data variables.product.prodname_actions %}, consulte "[Usando ambientes para implantação](/actions/deployment/using-environments-for-deployment)". {% endif %}Para obter mais informações sobre implantações com a API REST, consulte "[Repositórios](/rest/reference/repos#deployments)". + +Para visualizar implantações atuais e anteriores, clique em **Ambientes** na página inicial do repositório. +{% ifversion ghae or ghes < 3.0 %} +![Ambientes](/assets/images/enterprise/2.22/environments-sidebar.png){% else %} +![Environments](/assets/images/environments-sidebar.png){% endif %} + +A página de implantações exibe a última implantação ativa de cada ambiente do seu repositório. Se a implantação incluir uma URL de ambiente, um botão **Exibir implantação** que vincula à URL será exibido ao lado da implantação. + +O registro da atividade mostra o histórico de implantação para seus ambientes. Por padrão, apenas a implantação mais recente para um ambiente tem um status `Ativo`; todas as implantações ativas anteriormente têm um status `Inativo`. Para obter mais informações sobre inativação automática de implantações, consulte "[Implantações inativas](/rest/reference/repos#inactive-deployments)". + +Você também pode usar a API REST para obter informações sobre implantações. Para obter mais informações, consulte "[Repositórios](/rest/reference/repos#deployments)". 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 3841d59917..4d7d3cdf21 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 @@ -14,7 +14,6 @@ type: overview {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Sobre executores auto-hospedados @@ -25,7 +24,7 @@ Você pode adicionar runners auto-hospedados em vários níveis na hierarquia de - Executores no nível da organização podem processar trabalhos para vários repositórios em uma organização. - Runners de nível empresarial podem ser atribuídos a várias organizações em uma conta corporativa. -Your runner machine connects to {% data variables.product.prodname_dotcom %} using the {% data variables.product.prodname_actions %} self-hosted runner application. {% data reusables.github-actions.runner-app-open-source %} Quando uma nova versão é lançada, o aplicativo do executor atualiza-se automaticamente quando uma tarefa é atribuída ao executor, ou dentro de uma semana após a liberação, caso o executor não tenha recebido nenhum trabalho. +A sua máquina do executor conecta-se ao {% data variables.product.product_name %} usando o aplicativo do executor auto-hospedado de {% data variables.product.prodname_actions %}. {% data reusables.github-actions.runner-app-open-source %} Quando uma nova versão é lançada, o aplicativo do executor atualiza-se automaticamente quando uma tarefa é atribuída ao executor, ou dentro de uma semana após a liberação, caso o executor não tenha recebido nenhum trabalho. {% data reusables.github-actions.self-hosted-runner-auto-removal %} @@ -58,9 +57,9 @@ Você pode usar qualquer máquina como um executor auto-hospedado, desde que ela * Se você desejar executar fluxos de trabalho que usam ações do contêiner do Docker ou dos contêineres de serviço, você deverá usar uma máquina Linux e o Docker deve estar instalados. {% ifversion fpt or ghes > 3.2 %} -## Autoscaling your self-hosted runners +## Dimensionar automaticamente os seus executores auto-hospedados -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)." +Você pode aumentar ou diminuir automaticamente o número de executores auto-hospedados no seu ambiente em resposta aos eventos que você receber. Para obter mais informações, consulte "[Dimensionamento automático com executores auto-hospedados](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)". {% endif %} @@ -119,7 +118,7 @@ As seguintes arquiteturas de processador são compatíveis com o aplicativo do e ## Comunicação entre executores auto-hospedados e {% data variables.product.prodname_dotcom %} -Some extra configuration might be required to use actions from {% data variables.product.prodname_dotcom_the_website %} with {% data variables.product.prodname_ghe_server %}, or to use the `actions/setup-LANGUAGE` actions with self-hosted runners that do not have internet access. Para obter mais informações, consulte "[Comunicação entre os executores auto-hospedados e {% data variables.product.prodname_dotcom %}](#communication-between-self-hosted-runners-and-github)". +Algumas configurações extras podem ser necessárias para usar ações de {% data variables.product.prodname_dotcom_the_website %} com {% data variables.product.prodname_ghe_server %} ou para usar as ações `actions/setup-LANGUAGE` com executores auto-hospedados sem acesso à internet. Para obter mais informações, consulte "[Comunicação entre os executores auto-hospedados e {% data variables.product.prodname_dotcom %}](#communication-between-self-hosted-runners-and-github)". {% endif %} @@ -164,7 +163,7 @@ Se você usar uma lista de endereços IP permitida para a sua a sua organizaçã {% else %} -You must ensure that the machine has the appropriate network access to communicate with {% data variables.product.product_location %}. +Você deve garantir que a máquina tenha acesso adequado à rede para comunicar-se com {% data variables.product.product_location %}. {% endif %} @@ -172,7 +171,9 @@ Você também pode usar executores auto-hospedados com um servidor proxy. Para o ## Segurança dos executores auto-hospedados com repositórios públicos +{% ifversion not ghae %} {% data reusables.github-actions.self-hosted-runner-security %} +{% endif %} Este não é um problema com executores hospedados no {% data variables.product.prodname_dotcom %}, pois cada executor hospedado no {% data variables.product.prodname_dotcom %} é sempre uma máquina virtual limpa e isolada, que é destruída no final da execução do trabalho. diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md b/translations/pt-BR/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md index 1676188771..c1eda210e2 100644 --- a/translations/pt-BR/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md +++ b/translations/pt-BR/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md @@ -9,12 +9,12 @@ versions: ghes: '*' ghae: '*' type: tutorial +shortTitle: Adicionar executores auto-hospedados --- {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} Você pode adicionar um executor auto-hospedado a {{ site.data.variables.product.prodname_actions }}. @@ -22,6 +22,7 @@ Se você é um administrador de empresa ou organização, talvez você queira ad Para obter informações sobre sistemas operacionais compatíveis com executores auto-hospedados ou sobre como usar executores auto-hospedados com um servidor proxy, consulte "[Sobre executores auto-hospedados](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)." +{% ifversion not ghae %} {% warning %} **Aviso:** {% data reusables.github-actions.self-hosted-runner-security %} @@ -29,55 +30,86 @@ Para obter informações sobre sistemas operacionais compatíveis com executores Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)." {% endwarning %} +{% endif %} -### Adicionar um executor auto-hospedado a um repositório +## Adicionar um executor auto-hospedado a um repositório Você pode adicionar executores auto-hospedados a um único repositório. Para adicionar um executor auto-hospedado a um repositório de usuário, você deve ser o proprietário do repositório. Para um repositório da organização, você deve ser um proprietário da organização ou ter acesso de administrador ao repositório. +{% ifversion fpt %} +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.github-actions.settings-sidebar-actions %} +{% data reusables.github-actions.settings-sidebar-actions-runners-updated %} +1. Clique em **Novo executor auto-hospedado**. +{% data reusables.github-actions.self-hosted-runner-configure %} +{% endif %} +{% ifversion ghae or ghes %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} 1. Abaixo -{% if currentVersion == "free-pro-team@latest" %}"Executores"{% else %}"Executores auto-hospedados"{% endif %}, clique **Adicionar executor**. +{% ifversion fpt or ghes > 3.1 or ghae %}"Executores"{% else %}"Executores auto-hospedados"{% endif %}, clique **Adicionar executor**. {% data reusables.github-actions.self-hosted-runner-configure %} +{% endif %} {% data reusables.github-actions.self-hosted-runner-check-installation-success %} -### Adicionar um executor auto-hospedado a uma organização +## Adicionar um executor auto-hospedado a uma organização Você pode adicionar executores auto-hospedados no nível da organização, onde podem ser usados para processar trabalhos para múltiplos repositórios em uma organização. Para adicionar um executor auto-hospedado a uma organização, você deve ser proprietário da organização. +{% ifversion fpt %} +{% data reusables.organizations.navigate-to-org %} +{% data reusables.organizations.org_settings %} +{% data reusables.github-actions.settings-sidebar-actions %} +{% data reusables.github-actions.settings-sidebar-actions-runners-updated %} +1. Clique em **Novo executor**. +{% data reusables.github-actions.self-hosted-runner-configure %} +{% endif %} +{% ifversion ghae or ghes %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} 1. Abaixo -{% if currentVersion == "free-pro-team@latest" %}"Executores"{% else %}"Executores auto-hospedados"{% endif %}, clique **Adicionar executor**. +{% ifversion fpt or ghes > 3.1 or ghae %}"Executores"{% else %}"Executores auto-hospedados"{% endif %}, clique **Adicionar executor**. {% data reusables.github-actions.self-hosted-runner-configure %} +{% endif %} + {% data reusables.github-actions.self-hosted-runner-check-installation-success %} {% data reusables.github-actions.self-hosted-runner-public-repo-access %} -### Adicionar um executor auto-hospedado a uma empresa +## Adicionar um executor auto-hospedado a uma empresa Você pode adicionar executores auto-hospedados a uma empresa, onde podem ser atribuídos a várias organizações. Os administradores da organização poderão então controlar quais repositórios podem usá-los. -{% if currentVersion == "free-pro-team@latest" %} +Novos runners são atribuídos ao grupo padrão. Você pode modificar o grupo do executor depois de registrar o runner (executor). Para obter mais informações, consulte "[Gerenciando acesso a runners auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)". + +{% ifversion fpt %} Para adicionar um executor auto-hospedado a uma conta corporativa, você deve ser proprietário da organização. -{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} -Para adicionar um executor auto-hospedado no nível de empresa de -{% data variables.product.product_location %}, você deve ser um administrador do site. -{% endif %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} {% data reusables.enterprise-accounts.actions-runners-tab %} -1. Clique em **Adicionar novo** e depois clique em **Novo executor**. Novos runners são atribuídos ao grupo padrão. Você pode modificar o grupo do executor depois de registrar o runner (executor). Para obter mais informações, consulte "[Gerenciando acesso a runners auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)". +1. Clique em **Novo executor**. {% data reusables.github-actions.self-hosted-runner-configure %} +{% endif %} +{% ifversion ghae or ghes %} +Para adicionar um executor auto-hospedado no nível de empresa de +{% data variables.product.product_location %}, você deve ser um administrador do site. +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.actions-tab %} +{% data reusables.enterprise-accounts.actions-runners-tab %} +1. Clique em **Adicionar novo** e depois clique em **Novo executor**. +{% data reusables.github-actions.self-hosted-runner-configure %} +{% endif %} {% data reusables.github-actions.self-hosted-runner-check-installation-success %} {% data reusables.github-actions.self-hosted-runner-public-repo-access %} -#### Disponibilizar executores corporativos para repositórios +### Disponibilizar executores corporativos para repositórios Por padrão, os executores do grupo de executores "Padrão" de uma empresa estão disponíveis para todas as organizações da empresa, mas não estão disponíveis para todos os repositórios em cada organização. 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 51e3fdfe0f..3358d5fb17 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 @@ -1,6 +1,6 @@ --- -title: Autoscaling with self-hosted runners -intro: You can automatically scale your self-hosted runners in response to webhook events. +title: Redimensionamento automático com executores auto-hospedados +intro: Você pode dimensionar automaticamente seus executores auto-hospedados em resposta a eventos de webhooks. versions: free-pro-team: '*' enterprise-server: '>3.2' @@ -10,48 +10,47 @@ type: overview {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -## About autoscaling +## Sobre o dimensionamento automático -You can automatically increase or decrease the number of self-hosted runners in your environment in response to the webhook events you receive with a particular label. For example, you can create automation that adds a new self-hosted runner each time you receive a [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook event with the [`queued`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) activity, which notifies you that a new job is ready for processing. The webhook payload includes label data, so you can identify the type of runner the job is requesting. Once the job has finished, you can then create automation that removes the runner in response to the `workflow_job` [`completed`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) activity. +Você pode aumentar ou diminuir automaticamente o número de executores auto-hospedados no seu ambiente em resposta aos eventos do webhook que você recebe com uma determinada etiqueta. Por exemplo, você pode criar uma automação que adiciona um novo executor auto-hospedado cada vez que você receber um evento de webhook [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) com a atividade [`queued`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job), que notifica você de que um novo trabalho está pronto para processamento. A carga do webhook inclui dados da etiqueta. Portanto, você pode identificar o tipo de executor que a tarefa está solicitando. Uma vez terminado o trabalho, você pode criar uma automação que remove o executor em resposta à atividade de `workflow_job` [`concluída`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job). -## Using ephemeral runners for autoscaling +## Usaar executores efêmeros para dimensionamento automático -{% data variables.product.prodname_dotcom %} recommends implementing autoscaling with ephemeral self-hosted runners; autoscaling with persistent self-hosted runners is not recommended. In certain cases, {% data variables.product.prodname_dotcom %} cannot guarantee that jobs are not assigned to persistent runners while they are shut down. With ephemeral runners, this can be guaranteed because {% data variables.product.prodname_dotcom %} only assigns one job to a runner. +{% data variables.product.prodname_dotcom %} recomenda implementar o dimensionamento automático com executores auto-hospedados efêmeros. Não se recomenda o dimensionamento automático com executores auto-hospedados persistentes. Em certos casos, {% data variables.product.prodname_dotcom %} não pode garantir que os trabalhos não sejam atribuídos a executores persistentes enquanto eles são desativados. Com executores efêmeros, é possível garantir iss, porque {% data variables.product.prodname_dotcom %} só atribui um trabalho a um executor. -This approach allows you to manage your runners as ephemeral systems, since you can use automation to provide a clean environment for each job. This helps limit the exposure of any sensitive resources from previous jobs, and also helps mitigate the risk of a compromised runner receiving new jobs. +Esta abordagem permite que você gerencie os seus executores como sistemas efêmeros, já que você pode usar automação para fornecer um ambiente limpo para cada trabalho. Isso ajuda a limitar a exposição de quaisquer recursos sensíveis de trabalhos anteriores e também ajuda a mitigar o risco de um executor comprometido receber novos trabalhos. -To add an ephemeral runner to your environment, include the `--ephemeral` parameter when registering your runner using `config.sh`. Por exemplo: +Para adicionar um executor efêmero ao seu ambiente, inclua o parâmetro `--ephemeral` ao registrar seu executor usando `config.sh`. Por exemplo: ``` $ ./config.sh --url https://github.com/octo-org --token example-token --ephemeral ``` -The {% data variables.product.prodname_actions %} service will then automatically de-register the runner after it has processed one job. You can then create your own automation that wipes the runner after it has been de-registered. +O serviço de {% data variables.product.prodname_actions %} irá cancelar o resgistro do executor automaticamente depois de ter processado um trabalho. Em seguida, você poderá criar a sua própria automação que limpa o executor depois que ele tiver seu registro cancelado. {% note %} -**Note:** If a job is labeled for a certain type of runner, but none matching that type are available, the job does not immediately fail at the time of queueing. Instead, the job will remain queued until the 24 hour timeout period expires. +**Observação:** Se um trabalho estiver etiquetado para um certo tipo de executor, mas nenhuma correspondência desse tipo estiver disponível, o trabalho não irá falhar imediatamente no momento da entrada na fila. Em vez disso, o trabalho permanecerá na fila até que o período de tempo limite de 24 horas expire. {% endnote %} -## Using webhooks for autoscaling +## Usando webhooks para dimensionamento automático -You can create your own autoscaling environment by using payloads received from the [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook. This webhook is available at the repository, organization, and enterprise levels, and the payload for this event contains an `action` key that corresponds to the stages of a workflow job's life-cycle; for example when jobs are `queued`, `in_progress`, and `completed`. You must then create your own scaling automation in response to these webhook payloads. +Você pode criar seu próprio ambiente de dimensionamento automático usando cargas recebidas do webhook [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job). Este webhook está disponível no repositório, organização e níveis corporativos e a carga deste evento contém uma chave de `ação` que corresponde aos estágios do ciclo de vida do trabalho de um fluxo de trabalho. Por exemplo, quando as tarefas estão `queued`, `in_progress` e `completed`. Você deverá criar a sua própria automação de dimensionamento em resposta a estas cargas de webhook. -- For more information about the `workflow_job` webhook, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job)." -- To learn how to work with webhooks, see "[Creating webhooks](/developers/webhooks-and-events/webhooks/creating-webhooks)." +- Para obter mais informações sobre o webhook do `workflow_job`, consulte "[Eventos e cargas do webhook](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job)". +- Para aprender como trabalhar com webhooks, consulte "[Criando webhooks](/developers/webhooks-and-events/webhooks/creating-webhooks)". -## Authentication requirements +## Requisitos de autenticação -You can register and delete self-hosted runners using [the API](/rest/reference/actions#self-hosted-runners). To authenticate to the API, your autoscaling implementation can use an access token or a {% data variables.product.prodname_dotcom %} app. +Você pode registrar e excluir executores auto-hospedados usando [API](/rest/reference/actions#self-hosted-runners). Para efetuar a autenticação na API, a implementação do seu dimensionamento automático pode usar um token de acesso ou um aplicativo de {% data variables.product.prodname_dotcom %}. -Your access token will require the following scope: +Seu token de acesso exigirá o seguinte escopo: -- For private repositories, use an access token with the [`repo` scope](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes). -- For public repositories, use an access token with the [`public_repo` scope](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes). +- Para repositórios privados, use um token de acesso com o escopo [`repo`](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes). +- Para repositórios públicos, use um token de acesso com o escopo [`public_repo`](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes). -To authenticate using a {% data variables.product.prodname_dotcom %} App, it must be assigned the following permissions: -- For repositories, assign the `administration` permission. -- for organizations, assign the `organization_self_hosted_runners` permission. +Para efetuar a autenticação usando um aplicativo de {% data variables.product.prodname_dotcom %}, este deverá ter as seguintes permissões: +- Para repositórios, atribua a permissão de `administração`. +- para organizações, atribua a permissão `organization_self_hosted_runners`. diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md b/translations/pt-BR/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md index 6795c10972..7b29c3c447 100644 --- a/translations/pt-BR/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md +++ b/translations/pt-BR/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md @@ -15,7 +15,6 @@ shortTitle: Executar o executor ao iniciar {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% capture service_first_step %}1. Pare o aplicativo do executor auto-hospedado se estiver em execução no momento.{% endcapture %} {% capture service_non_windows_intro_shell %}Na máquina, abra um shell no diretório onde você instalou o aplicativo do executor auto-hospedado. Use os comandos abaixo para instalar e gerenciar o serviço do executor auto-hospedado.{% endcapture %} diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/index.md b/translations/pt-BR/content/actions/hosting-your-own-runners/index.md index f416b9e834..45e1ed4efa 100644 --- a/translations/pt-BR/content/actions/hosting-your-own-runners/index.md +++ b/translations/pt-BR/content/actions/hosting-your-own-runners/index.md @@ -24,4 +24,3 @@ children: {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md b/translations/pt-BR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md index af75c9f8ba..c62906ff54 100644 --- a/translations/pt-BR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md +++ b/translations/pt-BR/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md @@ -8,13 +8,12 @@ versions: ghes: '*' ghae: '*' type: tutorial -shortTitle: Manage runner groups +shortTitle: Gerenciar grupos de executores --- {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Sobre grupos de executores auto-hospedados @@ -44,12 +43,12 @@ Ao criar um grupo, você deverá escolher uma política que defina quais reposit {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runner-groups %} -1. In the "Runner groups" section, click **New runner group**. +1. Na seção "Grupos de executores", clique em **Novo grupo de executor**. {% data reusables.github-actions.runner-group-assign-policy-repo %} {% warning %} - **Warning**: {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %} + **Aviso**: {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %} Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)." @@ -60,12 +59,12 @@ Ao criar um grupo, você deverá escolher uma política que defina quais reposit {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} -1. In the "Self-hosted runners" section, click **Add new**, and then **New group**. +1. Na seção "Executores auto-hospedados", clique em **Adicionar novo** e, em seguida, **Novo grupo**. ![Adicionar grupo de executor](/assets/images/help/settings/actions-org-add-runner-group.png) 1. Insira um nome para o seu grupo de executor e atribua uma política para acesso ao repositório. - {% ifversion ghes > 2.22 or ghae %} You can configure a runner group to be accessible to a specific list of repositories, or to all repositories in the organization. Por padrão, apenas repositórios privados podem acessar executores em um grupo de executores, mas você pode substituir isso. This setting can't be overridden if configuring an organization's runner group that was shared by an enterprise.{% endif %}{% ifversion ghes = 2.22 %}You can configure a runner group to be accessible to a specific list of repositories, all private repositories, or all repositories in the organization.{% endif %} + {% ifversion ghes > 2.22 or ghae %} Você pode configurar um grupo de executores para poder ser acessado por uma lista específica de repositórios ou por todos os repositórios na organização. Por padrão, apenas repositórios privados podem acessar executores em um grupo de executores, mas você pode substituir isso. Esta configuração não pode ser substituída se você estiver configurando o grupo de executores da organização que foi compartilhado por uma empresa.{% endif %}{% ifversion ghes = 2.22 %}Você pode configurar um grupo de executores para poder ser acessado por uma lista específica de repositórios, por todos os repositórios privados ou por todos os repositórios na organização.{% endif %} {% warning %} @@ -95,7 +94,7 @@ Ao criar um grupo, você deve escolher uma política que defina quais organizaç {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} {% data reusables.enterprise-accounts.actions-runner-groups-tab %} -1. Click **New runner group**. +1. Clique em **Novo grupo de executores**. {% data reusables.github-actions.runner-group-assign-policy-org %} {% warning %} @@ -119,7 +118,7 @@ Ao criar um grupo, você deve escolher uma política que defina quais organizaç ![Adicionar grupo de executor](/assets/images/help/settings/actions-enterprise-account-add-runner-group.png) 1. Insira um nome para o seu grupo de executor e atribua uma política para acesso à organização. - {% ifversion fpt or ghes > 2.22 or ghae %} Você pode configurar um grupo de executor para que possa ser acessado por uma lista específica de organizações ou todas as organizações da empresa. Por padrão, apenas repositórios privados podem acessar executores em um grupo de executores, mas você pode substituir isso. This setting can't be overridden if configuring an organization's runner group that was shared by an enterprise.{% elsif ghes = 2.22 %}You can configure a runner group to be accessible to all organizations in the enterprise or choose specific organizations.{% endif %} + {% ifversion fpt or ghes > 2.22 or ghae %} Você pode configurar um grupo de executor para que possa ser acessado por uma lista específica de organizações ou todas as organizações da empresa. Por padrão, apenas repositórios privados podem acessar executores em um grupo de executores, mas você pode substituir isso. Esta configuração não pode ser substituída se você estiver configurando o grupo de executores da organização que foi compartilhado por uma empresa.{% elsif ghes = 2.22 %}Você pode configurar um grupo de executores para que possa ser acessado por todas as organizações da empresa ou escolher organizações específicas.{% endif %} {% warning %} @@ -141,7 +140,7 @@ Você pode atualizar a política de acesso de um grupo de executores ou renomear {% ifversion fpt %} {% data reusables.github-actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.settings-sidebar-actions-runner-groups-selection %} -1. Modify the access options, or change the runner group name. +1. Modifique as opções de acesso ou altere o nome do grupo dp executor. {% warning %} @@ -156,31 +155,30 @@ Você pode atualizar a política de acesso de um grupo de executores ou renomear {% ifversion ghae or ghes %} {% data reusables.github-actions.self-hosted-runner-configure-runner-group-access %} {% endif %} -## Automatically adding a self-hosted runner to a group +## Adicionando um executor auto-hospedado a um grupo automaticamente -You can use the configuration script to automatically add a new self-hosted runner to a group. For example, this command registers a new self-hosted runner and uses the `--runnergroup` parameter to add it to a group named `rg-runnergroup`. +Você pode usar o script de configuração para adicionar automaticamente um novo executor auto-hospedado a um grupo. Por exemplo, este comando registra um novo executor auto-hospedado e usa o parâmetro `--runnergroup` para adicioná-lo a um grupo denominado `rg-runnergroup`. ```sh ./config.sh --url $org_or_enterprise_url --token $token --runnergroup rg-runnergroup ``` -The command will fail if the runner group doesn't exist: +O comando irá falhar se o grupo do executor não existir: ``` -Could not find any self-hosted runner group named "rg-runnergroup". +Não foi possível encontrar nenhum grupo de executor auto-hospedado denominado "rg-runnergroup". ``` ## Mover um executor auto-hospedado para um grupo -If you don't specify a runner group during the registration process, your new self-hosted runners are automatically assigned to the default group, and can then be moved to another group. -{% ifversion fpt %} +Se você não especificar o grupo de um executor durante o processo de registro, seus novos executores auto-hospedados são automaticamente atribuídos ao grupo padrão e poderão ser transferidos para outro grupo. +{% ifversion fpt or ghes > 3.1 or ghae-next %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} -1. In the "Runners" list, click the runner that you want to configure. -1. Select the Runner group dropdown menu. -1. In "Move runner to group", choose a destination group for the runner. -{% endif %} -{% ifversion ghae or ghes %} -1. Na seção {% ifversion fpt %}"Executores"{% else %}"Executores auto-hospedados"{% endif %} da página de configurações, localize o grupo atual do executor que deseja mover e expandir a lista de integrantes do grupo. ![Visualizar integrantes do grupo de executores](/assets/images/help/settings/actions-org-runner-group-members.png) +1. Na lista de "Executores", clique no executor que você deseja configurar. +1. Selecione o menu suspenso do grupo do executor. +1. Em "Transferir executor para o grupo", escolha um grupo de destino para o executor. +{% else %} +1. Na seção "executores auto-hospedados" da página de configurações, localize o grupo atual do executor que deseja mover e expandir a lista de integrantes do grupo. ![Visualizar integrantes do grupo de executores](/assets/images/help/settings/actions-org-runner-group-members.png) 1. Marque a caixa de seleção ao lado do executor auto-hospedado e, em seguida, clique em **Mover para o grupo** para ver os destinos disponíveis. ![Mover um membro do grupo de executores](/assets/images/help/settings/actions-org-runner-group-member-move.png) 1. Para mover o executor, clique no grupo de destino. ![Mover um membro do grupo de executores](/assets/images/help/settings/actions-org-runner-group-member-move-destination.png) {% endif %} @@ -188,14 +186,13 @@ If you don't specify a runner group during the registration process, your new se Os executores auto-hospedados são retornados automaticamente ao grupo-padrão quando seu grupo é removido. -{% ifversion fpt %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} {% data reusables.github-actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %} -1. In the list of groups, to the right of the group you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. +1. Na lista de grupos, à direita do grupo que você deseja excluir, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. 1. Para remover o grupo, clique em **Remover grupo**. 1. Revise os avisos de confirmação e, em seguida, clique em **Remover este grupo de executores**. -{% endif %} -{% ifversion ghae or ghes %} -1. Na seção {% ifversion fpt %}"Runners"{% else %}"Executores auto-hospedados"{% endif %} da página de configurações, localize o grupo que você deseja excluir e clique no botão {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. ![Exibir configurações do grupo de executores](/assets/images/help/settings/actions-org-runner-group-kebab.png) +{% else %} +1. Na seção "Executores auto-hospedados" da página de configurações, localize o grupo que você deseja excluir e clique no botão {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} . ![Exibir configurações do grupo de executores](/assets/images/help/settings/actions-org-runner-group-kebab.png) 1. Para remover o grupo, clique em **Remover grupo**. ![Exibir configurações do grupo de executores](/assets/images/help/settings/actions-org-runner-group-remove.png) diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md b/translations/pt-BR/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md index 4b86bab7f8..46d97951dc 100644 --- a/translations/pt-BR/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md +++ b/translations/pt-BR/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md @@ -17,7 +17,6 @@ shortTitle: Monitorar & solucionar problemas {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Verificar o status de um executor auto-hospedado usando {% data variables.product.prodname_dotcom %} @@ -25,7 +24,7 @@ shortTitle: Monitorar & solucionar problemas {% data reusables.github-actions.self-hosted-runner-navigate-repo-and-org %} {% data reusables.github-actions.settings-sidebar-actions-runners %} -1. Em {% ifversion fpt %}"Executores"{% else %}"Executores auto-hospedados"{% endif %}, você pode ver uma lista de executores registrados, incluindo nome do executor, etiqueta e status. +1. Em {% ifversion fpt or ghes > 3.1 or ghae-next %}"Executores"{% else %}"Executores auto-hospedados"{% endif %}, você pode ver uma lista de executores registrados, incluindo nome do executor, etiqueta e status. Pode haver os seguintes status: diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md b/translations/pt-BR/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md index 2ced943f5d..4efd08d8db 100644 --- a/translations/pt-BR/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md +++ b/translations/pt-BR/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md @@ -15,7 +15,6 @@ shortTitle: Remover executores auto-hospedados {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Remover um executor de um repositório @@ -57,15 +56,14 @@ Para remover um executor auto-hospedado de um repositório de usuário, você de Para remover um executor auto-hospedado de uma organização, você deve ser um proprietário da organização. Recomendamos que você também tenha acesso à máquina do executor auto-hospedado. {% data reusables.github-actions.self-hosted-runner-reusing %} -{% ifversion fpt %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions %} {% data reusables.github-actions.settings-sidebar-actions-runners-updated %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %} -{% endif %} -{% ifversion ghae or ghes %} +{% else %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} @@ -90,10 +88,9 @@ Para remover um executor auto-hospedado de uma conta corporativa, você deve ser {% data reusables.enterprise-accounts.actions-runners-tab %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes %} Para remover um executor auto-hospedado no nível da empresa de -{% data variables.product.product_location %}, você deve ser um administrador do site. Recomendamos que você também tenha acesso à máquina do executor auto-hospedado. +{% data variables.product.product_location %}, você deve ser um proprietário corporativo. Recomendamos que você também tenha acesso à máquina do executor auto-hospedado. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md b/translations/pt-BR/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md index d43cd80932..aadd75c6f3 100644 --- a/translations/pt-BR/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md +++ b/translations/pt-BR/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md @@ -14,7 +14,6 @@ shortTitle: Servidores proxy {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Configurar um servidor proxy usando variáveis de ambiente diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md b/translations/pt-BR/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md index 5dbdc996b1..37fab8a77c 100644 --- a/translations/pt-BR/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md +++ b/translations/pt-BR/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md @@ -12,7 +12,6 @@ shortTitle: Executores de etiqueta {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} Para obter informações sobre como usar etiquetas para encaminhar trabalhos para tipos específicos de executores auto-hospedados, consulte "[Usando executores auto-hospedados em um fluxo de trabalho](/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow)." @@ -22,8 +21,8 @@ Para obter informações sobre como usar etiquetas para encaminhar trabalhos par {% ifversion fpt %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} - 1. In the "Labels" section, click {% octicon "gear" aria-label="The Gear icon" %}. - 1. In the "Find or create a label" field, type the name of your new label and click **Create new label**. O rótulo personalizado é criado e atribuído ao executor auto-hospedado. É possível remover as etiquetas personalizadas dos executores auto-hospedados, mas não é possível excluí-las manualmente. {% data reusables.github-actions.actions-unused-labels %} + 1. Na seção "Etiquetas", clique em {% octicon "gear" aria-label="The Gear icon" %}. + 1. No campo "Encontrar ou criar uma etiqueta", digite o nome da sua nova etiqueta e clique em **Criar nova etiqueta**. O rótulo personalizado é criado e atribuído ao executor auto-hospedado. É possível remover as etiquetas personalizadas dos executores auto-hospedados, mas não é possível excluí-las manualmente. {% data reusables.github-actions.actions-unused-labels %} {% endif %} {% ifversion ghae or ghes %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} @@ -39,7 +38,7 @@ O rótulo personalizado é criado e atribuído ao executor auto-hospedado. É po {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.runner-label-settings %} - 1. To assign a label to your self-hosted runner, in the "Find or create a label" field, click the label. + 1. Para atribuir uma etiqueta ao executor auto-hospedado, no campo "Localizar ou criar uma etiqueta", clique na etiqueta. {% endif %} {% ifversion ghae or ghes %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} @@ -53,8 +52,8 @@ O rótulo personalizado é criado e atribuído ao executor auto-hospedado. É po {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.runner-label-settings %} - 1. In the "Find or create a label" field, assigned labels are marked with the -{% octicon "check" aria-label="The Check icon" %} icon. Click on a marked label to unassign it from your self-hosted runner. + 1. No campo "Encontre ou crie uma etiqueta", as etiquetas atribuídas são marcadas com a +Ícone de {% octicon "check" aria-label="The Check icon" %}. Clique em uma etiqueta marcada para cancelar a atribuição do seu executor auto-hospedado. {% endif %} {% ifversion ghae or ghes %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md b/translations/pt-BR/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md index 56dd32f469..dd1c944d8a 100644 --- a/translations/pt-BR/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md +++ b/translations/pt-BR/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md @@ -9,14 +9,16 @@ versions: ghes: '*' ghae: '*' type: tutorial +shortTitle: Usar executores em um fluxo de trabalho --- +{% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} Para obter informações sobre como criar etiquetas-padrão e etiquetas personalizadas, consulte "[Usando etiquetas com executores auto-hospedados](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)". -### Usar executores auto-hospedados em um fluxo de trabalho +## Usar executores auto-hospedados em um fluxo de trabalho As etiquetas permitem que você envie trabalhos do fluxo de trabalho para tipos específicos de executores auto-hospedados, com base em suas características compartilhadas. Por exemplo, se o seu trabalho exigir um componente de hardware específico ou um pacote de software, você poderá atribuir uma etiqueta personalizada a um executor e, em seguida, configurar seu trabalho para ser executado somente em executores com essa etiqueta. @@ -24,13 +26,13 @@ As etiquetas permitem que você envie trabalhos do fluxo de trabalho para tipos Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idruns-on)". -### Usar etiquetas-padrão para rotear tarefas +## Usar etiquetas-padrão para rotear tarefas Um executor auto-hospedado recebe automaticamente certas etiquetas ao ser adicionado a {% data variables.product.prodname_actions %}. Elas são usadas para indicar seu sistema operacional e sua plataforma de hardware: * `auto-hospedado`: Etiqueta-padrão aplicada a todos os executores auto-hospedados. * `Linux`, `Windows`, ou `macOS`: Aplicado, dependendo do sistema operacional. -* `x64`, `ARM`, or `ARM64`: Applied depending on hardware architecture. +* `x64`, `ARM`, ou `ARM64`: Aplicado dependendo da arquitetura do hardware. Você pode usar o YAML do seu fluxo de trabalho para enviar trabalhos para uma combinação dessas etiquetas. Neste exemplo, um executor auto-hospedado que corresponde a todas as três etiquetas será elegível para executar a o trabalho: @@ -44,7 +46,7 @@ runs-on: [self-hosted, linux, ARM64] As etiquetas-padrão são fixas e não podem ser alterados ou removidos. Considere usar etiquetas personalizadas caso precise de mais controle sobre o roteamento de trabalhos. -### Usar etiquetas personalizadas para rotear trabalhos +## Usar etiquetas personalizadas para rotear trabalhos Você pode criar etiquetas personalizadas e atribuí-las aos seus executores auto-hospedados a qualquer momento. As etiquetas personalizadas permitem que você envie trabalhos para determinados tipos de executores auto-hospedados, com base no modo como como são rotulados. @@ -63,13 +65,21 @@ runs-on: [self-hosted, linux, x64, gpu] Estas etiquetas operam cumulativamente. Portanto, as etiquetas de um executor auto-hospedado devem corresponder a todas as quatro para ser elegíveis a processar o trabalho. -### Precedência de encaminhamento para executores auto-hospedados +## Precedência de encaminhamento para executores auto-hospedados Ao encaminhar um trabalho para um executor auto-hospedado, {% data variables.product.prodname_dotcom %} procura um executor que corresponde às etiquetas `runs-on` do trabalho: -1. {% data variables.product.prodname_dotcom %} primeiro procura um executor no nível do repositório, depois no nível da organização{% if currentVersion ver_gt "enterprise-server@2.21" %} e, por fim, no nível empresarial{% endif %}. +{% ifversion fpt or ghes > 3.2 or ghae-next %} +- {% data variables.product.prodname_dotcom %} primeiro pesquisa um executor on-line e inativo no nível do repositório e, em seguida, no nível da organização. {% ifversion fpt %} e se a organização for parte de uma empresa,{% endif %}, irá pesquisar no nível da empresa. +- Se {% data variables.product.prodname_dotcom %} encontrar um executor on-line e inativo em um determinado nível que corresponde às etiquetas `runs-on` do trabalho, este será atribuído e enviado para o executor. + - Se o executor não pegar a tarefa atribuída em de 60 segundos, o trabalho entrará na fila de todos os níveis e irá esperar que um executor correspondente de qualquer nível fique on-line e pegue o trabalho. +- Se {% data variables.product.prodname_dotcom %} não encontrar um executor on-line e inativo em qualquer nível, o trabalho entrará na fila de todos os níveis e irá esperar que um executor correspondente de qualquer nível fique on-line e pegue o trabalho. +- Se o trabalho permanecer na fila por mais de 24 horas, o trabalho falhará. +{% else %} +1. {% data variables.product.prodname_dotcom %} primeiro procura um executor no nível do repositório, em seguida, no nível da organização e, por fim, no nível da empresa. 2. Em seguida, o trabalho é enviado para o primeiro executor correspondente que está on-line e inativo. - Se todos os executores on-line estiverem ocupados, o trabalho será agendado no nível com o maior número de executores on-line. - Se todos os runners correspondentes estiverem off-line, a tarefa será listada no nível com o maior número de executores off-line correspondentes. - Se não houver executores correspondentes em qualquer nível, o trabalho falhará. - Se o trabalho permanecer na fila por mais de 24 horas, o trabalho falhará. +{% endif %} diff --git a/translations/pt-BR/content/actions/index.md b/translations/pt-BR/content/actions/index.md index c1a95a4c69..2c8fbab499 100644 --- a/translations/pt-BR/content/actions/index.md +++ b/translations/pt-BR/content/actions/index.md @@ -9,6 +9,7 @@ featuredLinks: guides: - /actions/learn-github-actions - /actions/guides/about-continuous-integration + - /actions/deployment/deploying-with-github-actions - /actions/guides/about-packaging-with-github-actions - /actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting guideCards: diff --git a/translations/pt-BR/content/actions/learn-github-actions/contexts.md b/translations/pt-BR/content/actions/learn-github-actions/contexts.md index 55879d4f0e..53d5fb0dc9 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/contexts.md +++ b/translations/pt-BR/content/actions/learn-github-actions/contexts.md @@ -1,7 +1,7 @@ --- title: Contextos shortTitle: Contextos -intro: You can access context information in workflows and actions. +intro: Você pode acessar as informações de contexto nos fluxos de trabalho e nas ações. product: '{% data reusables.gated-features.actions %}' redirect_from: - /articles/contexts-and-expression-syntax-for-github-actions @@ -18,13 +18,12 @@ miniTocMaxHeadingLevel: 3 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -## About contexts +## Sobre os contextos {% data reusables.github-actions.context-injection-warning %} -Os contextos são uma forma de acessar informações sobre execuções de fluxo de trabalho, ambientes dos executores, trabalhos e etapas. Contextos usam a sintaxe de expressão. For more information, see "[Expressions](/actions/learn-github-actions/expressions)." +Os contextos são uma forma de acessar informações sobre execuções de fluxo de trabalho, ambientes dos executores, trabalhos e etapas. Contextos usam a sintaxe de expressão. Para obter mais informações, consulte "[Expressões](/actions/learn-github-actions/expressions)". {% raw %} `${{ }}` @@ -61,27 +60,29 @@ O contexto `github` context contém informações sobre a execução do fluxo de {% data reusables.github-actions.github-context-warning %} {% data reusables.github-actions.context-injection-warning %} -| Nome da propriedade | Tipo | Descrição | -| ------------------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `github` | `objeto` | Contexto de nível mais alto disponível em qualquer trabalho ou etapa de um fluxo de trabalho. | -| `github.action` | `string` | O nome da ação atualmente em execução. O {% data variables.product.prodname_dotcom %} remove os caracteres especiais ou usa o nome `executar` quando a etapa atual executa um script. Se você usar a mesma ação mais de uma vez no mesmo trabalho, o nome incluirá um sufixo com o número de sequência. Por exemplo, o primeiro script que você executa será denominado `run1`, e o segundo script será denominado `run2`. Da mesma forma, a segunda invocação de `actions/checkout` será `actionscheckout2`. | -| `github.action_path` | `string` | O caminho onde está localizada a sua ação. Você pode usar esse caminho para acessar facilmente os arquivos localizados no mesmo repositório que sua ação. This attribute is only supported in composite actions. | -| `github.actor` | `string` | Login do usuário que iniciou a execução do fluxo de trabalho. | -| `github.base_ref` | `string` | `base_ref` ou branch alvo da pull request em uma execução de fluxo de trabalho. Esta propriedade só está disponível quando o evento que aciona a execução de um fluxo de trabalho for `pull_request` ou `pull_request_target`. | -| `github.event` | `objeto` | Carga de evento de webhook completa. Para obter mais informações, consulte "[Eventos que acionam fluxos de trabalho](/articles/events-that-trigger-workflows/)". Você pode acessar as propriedades individuais do evento usando este contexto. | -| `github.event_name` | `string` | Nome do evento que acionou a execução do fluxo de trabalho. | -| `github.event_path` | `string` | O caminho para a carga completa do evento do webhook no executor. | -| `github.head_ref` | `string` | `head_ref` ou branch de origem da pull request em uma execução de fluxo de trabalho. Esta propriedade só está disponível quando o evento que aciona a execução de um fluxo de trabalho for `pull_request` ou `pull_request_target`. | -| `github.job` | `string` | O [`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) do trabalho atual. | -| `github.ref` | `string` | Branch ou ref tag que acionou a execução do fluxo de trabalho. For branches this is the format `refs/heads/`, and for tags it is `refs/tags/`. | -| `github.repository` | `string` | Nome do repositório e o proprietário. Por exemplo, `Codertocat/Hello-World`. | -| `github.repository_owner` | `string` | O nome do proprietário do repositório. Por exemplo, `Codertocat`. | +| Nome da propriedade | Tipo | Descrição | +| ------------------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `github` | `objeto` | Contexto de nível mais alto disponível em qualquer trabalho ou etapa de um fluxo de trabalho. | +| `github.action` | `string` | O nome da ação atualmente em execução. {% data variables.product.prodname_dotcom %} remove caracteres especiais ou usa o nome `__run` quando a etapa atual executa um script. Se você usar a mesma ação mais de uma vez no mesmo trabalho, o nome incluirá um sufixo com o número da sequência com o sublinhado antes dele. Por exemplo, o primeiro script que você executar terá o nome `__run` e o segundo script será denominado `__run_2`. Da mesma forma, a segunda invocação de `actions/checkout` será `actionscheckout2`. | +| `github.action_path` | `string` | O caminho onde está localizada a sua ação. Você pode usar esse caminho para acessar facilmente os arquivos localizados no mesmo repositório que sua ação. Este atributo é compatível apenas em ações compostas. | +| `github.actor` | `string` | Login do usuário que iniciou a execução do fluxo de trabalho. | +| `github.base_ref` | `string` | `base_ref` ou branch alvo da pull request em uma execução de fluxo de trabalho. Esta propriedade só está disponível quando o evento que aciona a execução de um fluxo de trabalho for `pull_request` ou `pull_request_target`. | +| `github.event` | `objeto` | Carga de evento de webhook completa. Para obter mais informações, consulte "[Eventos que acionam fluxos de trabalho](/articles/events-that-trigger-workflows/)". Você pode acessar as propriedades individuais do evento usando este contexto. | +| `github.event_name` | `string` | Nome do evento que acionou a execução do fluxo de trabalho. | +| `github.event_path` | `string` | O caminho para a carga completa do evento do webhook no executor. | +| `github.head_ref` | `string` | `head_ref` ou branch de origem da pull request em uma execução de fluxo de trabalho. Esta propriedade só está disponível quando o evento que aciona a execução de um fluxo de trabalho for `pull_request` ou `pull_request_target`. | +| `github.job` | `string` | O [`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) do trabalho atual. | +| `github.ref` | `string` | Branch ou ref tag que acionou a execução do fluxo de trabalho. Para branches, este é o formato `refs/heads/` e, para tags, é `refs/tags/`. | +| `github.repository` | `string` | Nome do repositório e o proprietário. Por exemplo, `Codertocat/Hello-World`. | +| `github.repository_owner` | `string` | O nome do proprietário do repositório. Por exemplo, `Codertocat`. | | `github.run_id` | `string` | {% data reusables.github-actions.run_id_description %} | `github.run_number` | `string` | {% data reusables.github-actions.run_number_description %} -| `github.sha` | `string` | Commit SHA que acionou a execução do fluxo de trabalho. | -| `github.token` | `string` | Um token para fazer a autenticação em nome do aplicativo GitHub instalado no seu repositório. Isso é funcionalmente equivalente ao segredo `GITHUB_TOKEN`. Para obter mais informações, consulte "[Permissões para o GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)". | -| `github.workflow` | `string` | Nome do fluxo de trabalho. Se o fluxo de trabalho não determina um `name` (nome), o valor desta propriedade é o caminho completo do arquivo do fluxo de trabalho no repositório. | -| `github.workspace` | `string` | O diretório-padrão de trabalho para etapas e a localização-padrão do repositório ao usar a ação [`checkout-`](https://github.com/actions/checkout). | +| `github.run_attempt` | `string` | Um número exclusivo para cada tentativa de execução de um fluxo de trabalho específico em um repositório. Este número começa em 1 para a primeira tentativa de execução do fluxo de trabalho e aumenta a cada nova execução. | +| `github.server_url` | `string` | Retorna a URL do servidor GitHub. Por exemplo: `https://github.com`. | +| `github.sha` | `string` | Commit SHA que acionou a execução do fluxo de trabalho. | +| `github.token` | `string` | Um token para fazer a autenticação em nome do aplicativo GitHub instalado no seu repositório. Isso é funcionalmente equivalente ao segredo `GITHUB_TOKEN`. Para obter mais informações, consulte "[Permissões para o GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)". | +| `github.workflow` | `string` | Nome do fluxo de trabalho. Se o fluxo de trabalho não determina um `name` (nome), o valor desta propriedade é o caminho completo do arquivo do fluxo de trabalho no repositório. | +| `github.workspace` | `string` | O diretório-padrão de trabalho para etapas e a localização-padrão do repositório ao usar a ação [`checkout-`](https://github.com/actions/checkout). | ### Contexto `env` @@ -130,6 +131,7 @@ O contexto do `executor` contém informações sobre o executor que está execut | Nome da propriedade | Tipo | Descrição | | ------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `runner.name` | `string` | {% data reusables.actions.runner-name-description %} | `runner.os` | `string` | {% data reusables.actions.runner-os-description %} | `runner.temp` | `string` | {% data reusables.actions.runner-temp-directory-description %} | `runner.tool_cache` | `string` | {% ifversion ghae %}Para instruções instruções sobre como ter certeza de que o seu {% data variables.actions.hosted_runner %} tem o software necessário instalado, consulte "[Criar imagens personalizadas](/actions/using-github-hosted-runners/creating-custom-images)". {% else %} {% data reusables.actions.runner-tool-cache-description %} {% endif %} diff --git a/translations/pt-BR/content/actions/learn-github-actions/creating-workflow-templates.md b/translations/pt-BR/content/actions/learn-github-actions/creating-workflow-templates.md new file mode 100644 index 0000000000..02b992ca90 --- /dev/null +++ b/translations/pt-BR/content/actions/learn-github-actions/creating-workflow-templates.md @@ -0,0 +1,93 @@ +--- +title: Criando modelos de fluxo de trabalho +shortTitle: Criando modelos +intro: Saiba como criar modelos de fluxo de trabalho para ajudar as pessoas na sua equipe a adicionar novos fluxos de trabalho com mais facilidade. +redirect_from: + - /actions/configuring-and-managing-workflows/sharing-workflow-templates-within-your-organization +versions: + fpt: '*' + ghes: '*' + ghae: '*' +type: tutorial +topics: + - Workflows + - CI +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +## Visão Geral + +{% data reusables.actions.workflow-organization-templates %} + +## Criar um modelo do fluxo de trabalho + +Os modelos do fluxo de trabalh podem ser criados por usuários com acesso de gravação ao repositório `.github` da organização. Em seguida, os modelos podem ser usados por integrantes da organização com permissão para criar fluxos de trabalho. Você pode compartilhar modelos de fluxo de trabalho se o repositório da sua organização for público ou se o repositório for privado e estiver em um plano corporativo. + +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +{% note %} + +**Observação:** Para evitar duplicação em fluxos de trabalho criados a partir de um modelo você pode chamar fluxos de trabalho reutilizáveis a partir de um modelo de fluxo de trabalho. Isso pode ajudar a manter seus fluxos de trabalho de forma mais fácil. Para obter mais informações, consulte "[Reutilizando fluxos de trabalho](/actions/learn-github-actions/reusing-workflows)". + +{% endnote %} +{% endif %} + +Este procedimento demonstra como criar um modelo de fluxo de trabalho e um arquivo de metadados. O arquivo de metadados descreve como o modelo é apresentado aos usuários quando estão criando um novo fluxo de trabalho. + +1. Se já não existir, crie um novo repositório público denominado `.github` na sua organização. +2. Crie um diretório denominado `workflow-templates`. +3. Crie seu novo arquivo de fluxo de trabalho dentro do diretório `workflow-templates`. + + Se você precisar referir-se ao branch-padrão de um repositório, você poderá usar o espaço reservado `branch$default`. Quando um fluxo de trabalho é criado usando seu modelo, o espaço reservado será automaticamente substituído pelo nome do branch-padrão do repositório. + + Por exemplo, este arquivo denominado `octo-organization-ci.yml` demonstra um fluxo de trabalho básico. + + ```yaml + name: Octo Organization CI + + on: + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] + + jobs: + build: + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v2 + + - name: Run a one-line script + run: echo Hello from Octo Organization + ``` +4. Crie um arquivo de metadados dentro do diretório `workflow-templates`. O arquivo de metadados deve ter o mesmo nome do arquivo de fluxo de trabalho, mas em vez da extensão `.yml`, deve-se adicionar `.properties.json`. Por exemplo, este arquivo denominado `octo-organization-ci.properties.json` contém os metadados para um arquivo de fluxo de trabalho denominado `octo-organization-ci.yml`: + ```yaml + { + "name": "Octo Organization Workflow", + "description": "Octo Organization CI workflow template.", + "iconName": "example-icon", + "categories": [ + "Go" + ], + "filePatterns": [ + "package.json$", + "^Dockerfile", + ".*\\.md$" + ] + } + ``` + * `nome` - **Obrigatório.** O nome do modelo de fluxo de trabalho. Isto é exibido na lista de modelos disponíveis. + * `descrição` - **Obrigatória.** A descrição do modelo de fluxo de trabalho. Isto é exibido na lista de modelos disponíveis. + * `iconName` - **Obrigatório.** Define um ícone para a entrada do fluxo de trabalho na lista de modelos. O `iconName` deve ser um ícone SVG com o mesmo nome e deve ser armazenado no diretório `workflow-templates`. Por exemplo, um arquivo SVG denominado `exemplo-icon.svg` é referenciado como `example-icon`. + * `categorias` - **Opcional.** Define a categoria de idioma do fluxo de trabalho. Quando um usuário visualiza os modelos disponíveis, esses modelos que correspondem àao mesmo idioma terão mais destaque. Para obter informações sobre as categorias de idioma disponíveis, consulte https://github.com/github/linguist/blob/master/lib/linguist/languages.yml. + * `filePatterns` - **Opcional.** Permite que o modelo seja usado se o repositório do usuário tiver um arquivo no diretório-raiz que corresponde a uma expressão regular definida. + +Para adicionar outro modelo de fluxo de trabalho, adicione seus arquivos ao mesmo diretório `workflow-templates`. Por exemplo: + +![Arquivos do modelo do fluxo de trabalho](/assets/images/help/images/workflow-template-files.png) + +## Próximas etapas + +Para continuar aprendendo sobre {% data variables.product.prodname_actions %}, consulte "[Usando modelos de fluxo de trabalho](/actions/learn-github-actions/using-workflow-templates)". diff --git a/translations/pt-BR/content/actions/learn-github-actions/environment-variables.md b/translations/pt-BR/content/actions/learn-github-actions/environment-variables.md index d7425850cc..a4eea9f1a5 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/environment-variables.md +++ b/translations/pt-BR/content/actions/learn-github-actions/environment-variables.md @@ -15,7 +15,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Sobre as variáveis de ambiente @@ -45,34 +44,35 @@ Para usar o valor de uma variável de ambiente em um arquivo do fluxo de trabalh Se você usar a chave `executar` do arquivo de fluxo de trabalho para ler variáveis de ambiente de dentro do sistema operacional do executor (como mostrado no exemplo acima), a variável será substituída no sistema operacional do executor depois que a tarefa for enviada para o executor. Para outras partes de um arquivo de fluxo de trabalho, você deve usar o contexto `env` para ler variáveis de ambiente. Isso ocorre porque as chaves do fluxo de trabalho (como `se`) exigem que a variável seja substituída durante o processamento do fluxo de trabalho antes de ser enviada para o executor. -You can also use the {% ifversion fpt or ghes > 2.22 or ghae %}`GITHUB_ENV` environment file{% else %} `set-env` workflow command{% endif %} to set an environment variable that the following steps in a job can use. O comando do {% ifversion fpt or ghes > 2.22 or ghae %}arquivo de ambiente{% else %} `set-env` {% endif %} pode ser usado diretamente por uma ação ou como um comando do shell em um arquivo de fluxo de trabalho usando a palavra-chave `executar`. Para obter mais informações, consulte "[Comandos do fluxo de trabalho para {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions/#setting-an-environment-variable)". +Você também pode usar o {% ifversion fpt or ghes > 2.22 or ghae %}`GITHUB_ENV` environment file{% else %} `set-env` fluxo de trabalho{% endif %} para definir uma variável de ambiente que as seguintes etapas em um trabalho podem usar. O comando do {% ifversion fpt or ghes > 2.22 or ghae %}arquivo de ambiente{% else %} `set-env` {% endif %} pode ser usado diretamente por uma ação ou como um comando do shell em um arquivo de fluxo de trabalho usando a palavra-chave `executar`. Para obter mais informações, consulte "[Comandos do fluxo de trabalho para {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions/#setting-an-environment-variable)". ## Variáveis padrão de ambiente É altamente recomendável que as ações usem as variáveis do ambiente para acessar o sistema do arquivo em vez de usar os caminhos do arquivo com codificação rígida. {% data variables.product.prodname_dotcom %} define as variáveis de ambiente para ações a serem usadas em todos os ambientes executores. -| Variável de ambiente | Descrição | -| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `CI` | Definido sempre como `verdadeiro`. | -| `GITHUB_WORKFLOW` | Nome do fluxo de trabalho. | +| Variável de ambiente | Descrição | +| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `CI` | Definido sempre como `verdadeiro`. | +| `GITHUB_WORKFLOW` | Nome do fluxo de trabalho. | | `GITHUB_RUN_ID` | {% data reusables.github-actions.run_id_description %} | `GITHUB_RUN_NUMBER` | {% data reusables.github-actions.run_number_description %} -| `GITHUB_JOB` | O [job_id](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) do trabalho atual. | -| `GITHUB_ACTION` | Identificador único (`id`) da ação. | -| `GITHUB_ACTION_PATH` | O caminho onde está localizada a sua ação. Você pode usar esse caminho para acessar os arquivos localizados no mesmo repositório que sua ação. This variable is only supported in composite actions. | -| `GITHUB_ACTIONS` | Definido sempre como `verdadeiro` quando {% data variables.product.prodname_actions %} estiver executando o fluxo de trabalho. Você pode usar esta variável para diferenciar quando os testes estão sendo executados localmente ou por {% data variables.product.prodname_actions %}. | -| `GITHUB_ACTOR` | Nome da pessoa ou aplicativo que iniciou o fluxo de trabalho. Por exemplo, `octocat`. | -| `GITHUB_REPOSITORY` | Nome do repositório e o proprietário. Por exemplo, `octocat/Hello-World`. | -| `GITHUB_EVENT_NAME` | Nome do evento de webhook que acionou o workflow. | -| `GITHUB_EVENT_PATH` | Caminho do arquivo com a carga completa do evento webhook. Por exemplo, `/github/workflow/event.json`. | -| `GITHUB_WORKSPACE` | The {% data variables.product.prodname_dotcom %} workspace directory path, initially empty. Por exemplo, `/home/runner/work/my-repo-name/my-repo-name`. The [actions/checkout](https://github.com/actions/checkout) action will check out files, by default a copy of your repository, within this directory. | -| `GITHUB_SHA` | Commit SHA que acionou o fluxo de trabalho. Por exemplo, `ffac537e6cbbf934b08745a378932722df287a53`. | -| `GITHUB_REF` | Branch ou ref tag que acionou o fluxo de trabalho. Por exemplo, `refs/heads/feature-branch-1`. Se não houver branch ou tag disponível para o tipo de evento, a variável não existirá. | -| `GITHUB_HEAD_REF` | Definir somente para eventos de pull request. O nome do branch principal. | -| `GITHUB_BASE_REF` | Definir somente para eventos de pull request. O nome do branch de base. | -| `GITHUB_SERVER_URL` | Retorna a URL do servidor {% data variables.product.product_name %}. Por exemplo: `https://{% data variables.product.product_url %}`. | -| `GITHUB_API_URL` | Retorna a URL da API. Por exemplo: `{% data variables.product.api_url_code %}`. | -| `GITHUB_GRAPHQL_URL` | Retorna a URL API do GraphQL. Por exemplo: `{% data variables.product.graphql_url_code %}`. | +| `GITHUB_JOB` | O [job_id](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) do trabalho atual. | +| `GITHUB_ACTION` | Identificador único (`id`) da ação. | +| `GITHUB_ACTION_PATH` | O caminho onde está localizada a sua ação. Você pode usar esse caminho para acessar os arquivos localizados no mesmo repositório que sua ação. Esta variável só é compatível em ações compostas. | +| `GITHUB_ACTIONS` | Definido sempre como `verdadeiro` quando {% data variables.product.prodname_actions %} estiver executando o fluxo de trabalho. Você pode usar esta variável para diferenciar quando os testes estão sendo executados localmente ou por {% data variables.product.prodname_actions %}. | +| `GITHUB_ACTOR` | Nome da pessoa ou aplicativo que iniciou o fluxo de trabalho. Por exemplo, `octocat`. | +| `GITHUB_REPOSITORY` | Nome do repositório e o proprietário. Por exemplo, `octocat/Hello-World`. | +| `GITHUB_EVENT_NAME` | Nome do evento de webhook que acionou o workflow. | +| `GITHUB_EVENT_PATH` | Caminho do arquivo com a carga completa do evento webhook. Por exemplo, `/github/workflow/event.json`. | +| `GITHUB_WORKSPACE` | O caminho do diretório do espaço de trabalho de {% data variables.product.prodname_dotcom %} está inicialmente vazio. Por exemplo, `/home/runner/work/my-repo-name/my-repo-name`. A ação [actions/checkout](https://github.com/actions/checkout) irá fazer o check-out dos arquivos, por padrão uma cópia do seu repositório, neste diretório. | +| `GITHUB_SHA` | Commit SHA que acionou o fluxo de trabalho. Por exemplo, `ffac537e6cbbf934b08745a378932722df287a53`. | +| `GITHUB_REF` | Branch ou ref tag que acionou o fluxo de trabalho. Por exemplo, `refs/heads/feature-branch-1`. Se não houver branch ou tag disponível para o tipo de evento, a variável não existirá. | +| `GITHUB_HEAD_REF` | Definir somente para eventos de pull request. O nome do branch principal. | +| `GITHUB_BASE_REF` | Definir somente para eventos de pull request. O nome do branch de base. | +| `GITHUB_SERVER_URL` | Retorna a URL do servidor {% data variables.product.product_name %}. Por exemplo: `https://{% data variables.product.product_url %}`. | +| `GITHUB_API_URL` | Retorna a URL da API. Por exemplo: `{% data variables.product.api_url_code %}`. | +| `GITHUB_GRAPHQL_URL` | Retorna a URL API do GraphQL. Por exemplo: `{% data variables.product.graphql_url_code %}`. | +| `RUNNER_NAME` | {% data reusables.actions.runner-name-description %} | `RUNNER_OS` | {% data reusables.actions.runner-os-description %} | `RUNNER_TEMP` | {% data reusables.actions.runner-temp-directory-description %} {% ifversion not ghae %}| `RUNNER_TOOL_CACHE` | {% data reusables.actions.runner-tool-cache-description %}{% endif %} diff --git a/translations/pt-BR/content/actions/learn-github-actions/essential-features-of-github-actions.md b/translations/pt-BR/content/actions/learn-github-actions/essential-features-of-github-actions.md index a21ffef4e0..341b3c910a 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/essential-features-of-github-actions.md +++ b/translations/pt-BR/content/actions/learn-github-actions/essential-features-of-github-actions.md @@ -13,7 +13,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Visão Geral @@ -62,7 +61,7 @@ Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para o {% ## Compartilhar dados entre trabalhos -Se o seu trabalho gera arquivos que você deseja compartilhar com outro trabalho no mesmo fluxo de trabalho, ou se você quiser salvar os arquivos para referência posterior, você pode armazená-los em {% data variables.product.prodname_dotcom %} como _artefatos_. Artefatos são os arquivos que surgem quando você compila e testa seu código. Por exemplo, os artefatos podem incluir arquivos binários ou de pacotes, resultados de testes, capturas de tela ou arquivos de log. Os artefatos estão associados à execução do fluxo de trabalho em que foram criados e podem ser usados por outro trabalho. +Se o seu trabalho gera arquivos que você deseja compartilhar com outro trabalho no mesmo fluxo de trabalho, ou se você quiser salvar os arquivos para referência posterior, você pode armazená-los em {% data variables.product.prodname_dotcom %} como _artefatos_. Artefatos são os arquivos que surgem quando você compila e testa seu código. Por exemplo, os artefatos podem incluir arquivos binários ou de pacotes, resultados de testes, capturas de tela ou arquivos de log. Os artefatos estão associados à execução do fluxo de trabalho em que foram criados e podem ser usados por outro trabalho. {% data reusables.actions.reusable-workflow-artifacts %} Por exemplo, você pode criar um arquivo e, em seguida, carregá-lo como um artefato. diff --git a/translations/pt-BR/content/actions/learn-github-actions/events-that-trigger-workflows.md b/translations/pt-BR/content/actions/learn-github-actions/events-that-trigger-workflows.md index 2a9eb383fc..e2720ed964 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/events-that-trigger-workflows.md +++ b/translations/pt-BR/content/actions/learn-github-actions/events-that-trigger-workflows.md @@ -17,7 +17,6 @@ shortTitle: Eventos que acionam fluxos de trabalho {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Configurar eventos de fluxo de trabalho @@ -165,6 +164,26 @@ em: tipos: [opened, deleted] ``` +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## Eventos de reutilização do fluxo de trabalho + +`workflow_call` é uma palavra-chave usada como o valor de `on` em um fluxo de trabalho, da mesma forma que um evento. Ele indica que um fluxo de trabalho pode ser chamado a prtir de outro fluxo de trabalho. Para obter mais informações, consulte "[Reutilizando fluxos de trabalho](/actions/learn-github-actions/reusing-workflows)". + +### `workflow_call` + +| Carga de evento webhook | Tipos de atividade | `GITHUB_SHA` | `GITHUB_REF` | +| -------------------------------------- | ------------------ | -------------------------------------- | -------------------------------------- | +| Igual ao fluxo de trabalho de chamadas | n/a | Igual ao fluxo de trabalho de chamadas | Igual ao fluxo de trabalho de chamadas | + +#### Exemplo + +Para tornar um fluxo de trabalho reutilizável, ele deve incluir `workflow_call` como um dos valores de `on`. O exemplo abaixo só executa o fluxo de trabalho quando é chamado a partir de outro fluxo de trabalho: + +```yaml +on: workflow_call +``` +{% endif %} + ## Eventos webhook Você pode configurar seu fluxo de trabalho para executar quando eventos de webhook forem gerados em {% data variables.product.product_name %}. Alguns eventos são acionados por mais de um tipo de atividade. Se mais de um tipo de atividade acionar o evento, especifique quais tipos de atividade ativarão a execução do fluxo de trabalho. Para obter mais informações, consulte "[Webhooks](/webhooks). @@ -298,7 +317,7 @@ Executa o fluxo de trabalho sempre que o evento `discussion` ocorrer. {% data re {% data reusables.developer-site.limit_workflow_to_activity_types %} -For example, you can run a workflow when a discussion has been `created`, `edited`, or `answered`. +Por exemplo, você pode executar um fluxo de trabalho quando uma discussão tiver sido `created`, `edited` ou `answered`. ```yaml on: @@ -571,8 +590,8 @@ Executa o fluxo de trabalho sempre que o evento `pull_request` ocorre. {% data r {% note %} **Notas:** -- By default, a workflow only runs when a `pull_request`'s activity type is `opened`, `synchronize`, or `reopened`. Para acionar fluxos de trabalho para mais tipos de atividade, use a palavra-chave `types`. -- Workflows will not run on `pull_request` activity if the pull request has a merge conflict. The merge conflict must be resolved first. +- Por padrão, um fluxo de trabalho só é executado quando um tipo de atividade de `pull_request` for `opened`, `sincronize`, ou `reopened`. Para acionar fluxos de trabalho para mais tipos de atividade, use a palavra-chave `types`. +- Os fluxos de trabalho não serão executados na atividade `pull_request` se o pull request tiver um conflito de merge. O conflito de merge tem de ser resolvido primeiro. {% endnote %} diff --git a/translations/pt-BR/content/actions/learn-github-actions/expressions.md b/translations/pt-BR/content/actions/learn-github-actions/expressions.md index af0e1e399b..e94820c136 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/expressions.md +++ b/translations/pt-BR/content/actions/learn-github-actions/expressions.md @@ -1,7 +1,7 @@ --- -title: Expressions -shortTitle: Expressions -intro: You can evaluate expressions in workflows and actions. +title: Expressões +shortTitle: Expressões +intro: Você pode avaliar expressões em fluxos de trabalho e ações. product: '{% data reusables.gated-features.actions %}' versions: fpt: '*' @@ -12,11 +12,10 @@ miniTocMaxHeadingLevel: 3 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -## About expressions +## Sobre as expressões -Você pode usar expressões para configurar variáveis por programação em arquivos de fluxo de trabalho e acessar contextos. Uma expressão pode ser qualquer combinação de valores literais, referências a um contexto ou funções. É possível combinar literais, referências de contexto e funções usando operadores. For more information about contexts, see "[Contexts](/actions/learn-github-actions/contexts)." +Você pode usar expressões para configurar variáveis por programação em arquivos de fluxo de trabalho e acessar contextos. Uma expressão pode ser qualquer combinação de valores literais, referências a um contexto ou funções. É possível combinar literais, referências de contexto e funções usando operadores. Para obter mais informações sobre os contextos, consulte "[Contextos](/actions/learn-github-actions/contexts)". Expressões são comumente usadas com a condicional `if` palavra-chave em um arquivo de fluxo de trabalho para determinar se uma etapa deve ser executada. Quando uma condicional `if` for `true`, a etapa será executada. @@ -286,7 +285,7 @@ etapas: ### always -Causes the step to always execute, and returns `true`, even when canceled. Um trabalho ou uma etapa não será executado(a) quando uma falha crítica impedir a tarefa de ser executada. Por exemplo, se houver falha ao obter as fontes. +Faz com que a etapa seja sempre executada e retorna `verdadeiro`, mesmo quando cancelada. Um trabalho ou uma etapa não será executado(a) quando uma falha crítica impedir a tarefa de ser executada. Por exemplo, se houver falha ao obter as fontes. #### Exemplo diff --git a/translations/pt-BR/content/actions/learn-github-actions/finding-and-customizing-actions.md b/translations/pt-BR/content/actions/learn-github-actions/finding-and-customizing-actions.md index f05345ba4c..b428d3e05c 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/finding-and-customizing-actions.md +++ b/translations/pt-BR/content/actions/learn-github-actions/finding-and-customizing-actions.md @@ -18,7 +18,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Visão Geral diff --git a/translations/pt-BR/content/actions/learn-github-actions/index.md b/translations/pt-BR/content/actions/learn-github-actions/index.md index 869dd7337f..8e803de8ac 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/index.md +++ b/translations/pt-BR/content/actions/learn-github-actions/index.md @@ -32,8 +32,10 @@ children: - /finding-and-customizing-actions - /essential-features-of-github-actions - /managing-complex-workflows - - /sharing-workflows-with-your-organization + - /sharing-workflows-secrets-and-runners-with-your-organization + - /creating-workflow-templates - /using-workflow-templates + - /reusing-workflows - /events-that-trigger-workflows - /expressions - /contexts diff --git a/translations/pt-BR/content/actions/learn-github-actions/managing-complex-workflows.md b/translations/pt-BR/content/actions/learn-github-actions/managing-complex-workflows.md index 736b0390db..9da6866cf4 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/managing-complex-workflows.md +++ b/translations/pt-BR/content/actions/learn-github-actions/managing-complex-workflows.md @@ -1,7 +1,7 @@ --- title: Gerenciar fluxos de trabalhos complexos shortTitle: Gerenciar fluxos de trabalhos complexos -intro: 'This guide shows you how to use the advanced features of {% data variables.product.prodname_actions %}, with secret management, dependent jobs, caching, build matrices,{% ifversion fpt or ghes > 3.0 or ghae %} environments,{% endif %} and labels.' +intro: 'Este guia mostra como usar as funcionalidades avançadas de {% data variables.product.prodname_actions %}, com gestão de segredos, trabalhos dependentes, cache, matrizes de criação{% ifversion fpt or ghes > 3.0 or ghae %} ambientes,{% endif %} e etiquetas.' versions: fpt: '*' ghes: '*' @@ -13,11 +13,10 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Visão Geral -This article describes some of the advanced features of {% data variables.product.prodname_actions %} that help you create more complex workflows. +Este artigo descreve alguns dos recursos avançados de {% data variables.product.prodname_actions %} que ajudam você a criar criar fluxos de trabalho mais complexos. ## Armazenar segredos @@ -143,7 +142,7 @@ Para obter mais informações, consulte "[Usar bancos de dados e contêineres de ## Usar etiquetas para encaminhar fluxos de trabalho -Esse recurso ajuda você a atribuir tarefas a um executor hospedado específico. Se você quiser ter certeza de que um determinado tipo de executor irá processar seu trabalho, você pode usar etiquetas para controlar os locais onde os trabalhos são executados. You can assign labels to a self-hosted runner in addition to their default label of `self-hosted`. Then, you can refer to these labels in your YAML workflow, ensuring that the job is routed in a predictable way.{% ifversion not ghae %} {% data variables.product.prodname_dotcom %}-hosted runners have predefined labels assigned.{% endif %} +Esse recurso ajuda você a atribuir tarefas a um executor hospedado específico. Se você quiser ter certeza de que um determinado tipo de executor irá processar seu trabalho, você pode usar etiquetas para controlar os locais onde os trabalhos são executados. Você pode atribuir etiquetas a um executor auto-hospedado, além de sua etiqueta padrão de `auto-hospedado`. Em seguida, você pode consultar essas etiquetas no seu fluxo de trabalho YAML, garantindo que o trabalho seja encaminhado de forma previsível. Os executores hospedados em {% ifversion not ghae %} {% data variables.product.prodname_dotcom %} têm etiquetas pré-definidas atribuídas.{% endif %} {% ifversion ghae %} Este exemplo mostra como um fluxo de trabalho pode usar etiquetas para especificar o executor obrigatório: @@ -164,16 +163,19 @@ jobs: runs-on: [self-hosted, linux, x64, gpu] ``` -A workflow will only run on a runner that has all the labels in the `runs-on` array. The job will preferentially go to an idle self-hosted runner with the specified labels. If none are available and a {% data variables.product.prodname_dotcom %}-hosted runner with the specified labels exists, the job will go to a {% data variables.product.prodname_dotcom %}-hosted runner. +Um fluxo de trabalho só é executado em um executor que possui todas as etiquetas na matriz `runs-on`. O trabalho irá preferencialmente para um executor auto-hospedado inativo com as etiquetas especificadas. Se não houver nenhum disponível e houver um corredor hospedado em {% data variables.product.prodname_dotcom %} com os rótulos especificados, o trabalho irá para um executor hospedado em {% data variables.product.prodname_dotcom %}. -To learn more about self-hosted runner labels, see ["Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)." To learn more about -{% data variables.product.prodname_dotcom %}-hosted runner labels, see ["Supported runners and hardware resources"](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources). +Para aprender mais sobre etiquetas de executores auto-hospedados, consulte ["Usando etiquetas com executores auto-hospedados](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)". Para saber mais sobre +Etiquetas de executores hospedados em {% data variables.product.prodname_dotcom %}, consulte ["Executores e recursos de hardware compatíveis"](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources). {% endif %} -{% ifversion fpt or ghes > 3.0 %} +{% data reusables.actions.reusable-workflows %} + +{% ifversion fpt or ghes > 3.0 or ghae-next %} + ## Usar ambientes -Você pode configurar ambientes com regras de proteção e segredos. Cada trabalho em um fluxo de trabalho pode fazer referência a um único ambiente. Todas as regras de proteção configuradas para o ambiente têm de ser aprovadas antes que um trabalho de referência ao ambiente seja enviado a um executor. Para obter mais informações, consulte "[Ambientes](/actions/reference/environments)". +Você pode configurar ambientes com regras de proteção e segredos. Cada trabalho em um fluxo de trabalho pode fazer referência a um único ambiente. Todas as regras de proteção configuradas para o ambiente têm de ser aprovadas antes que um trabalho de referência ao ambiente seja enviado a um executor. Para obter mais informações, consulte "[Usando ambientes para implantação](/actions/deployment/using-environments-for-deployment)". {% endif %} ## Usar um modelo do fluxo de trabalho @@ -187,4 +189,4 @@ Você pode configurar ambientes com regras de proteção e segredos. Cada trabal ## Próximas etapas -Para continuar aprendendo sobre {% data variables.product.prodname_actions %}, consulte "[Compartilhar fluxos de trabalho com a sua organização](/actions/learn-github-actions/sharing-workflows-with-your-organization)". +Para continuar aprendendo sobre {% data variables.product.prodname_actions %}, consulte "[Compartilhar fluxos de trabalho, segredos e executores com a sua organização](/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization)". diff --git a/translations/pt-BR/content/actions/learn-github-actions/reusing-workflows.md b/translations/pt-BR/content/actions/learn-github-actions/reusing-workflows.md new file mode 100644 index 0000000000..dc7c5f6a6c --- /dev/null +++ b/translations/pt-BR/content/actions/learn-github-actions/reusing-workflows.md @@ -0,0 +1,195 @@ +--- +title: Reutilizando fluxos de trabalho +shortTitle: Reutilizando fluxos de trabalho +intro: Aprenda a evitar a duplicação ao criar um fluxo de trabalho reutilizando os fluxos de trabalho existentes. +miniTocMaxHeadingLevel: 3 +versions: + fpt: '*' + ghes: '>=3.4' + ghae: issue-4757 +type: how_to +topics: + - Workflows +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +{% note %} + +**Observação:** Os fluxos de trabalho reutilizáveis estão atualmente na versão beta e sujeitos a alterações. + +{% endnote %} + +## Visão Geral + +Em vez de copiar e colar de um fluxo de trabalho para outro, você pode tornar os fluxos de trabalho reutilizáveis. Você e qualquer pessoa com acesso ao fluxo de trabalho reutilizável pode chamar o fluxo de trabalho reutilizável a partir de outro fluxo de trabalho. + +A reutilização dosfluxos de trabalho evita duplicação. Isso torna os fluxos de trabalho mais fáceis de manter e permite que você crie novos fluxos de trabalho mais rapidamente, desenvolvendo sobre o trabalho dos outros, assim como você faz com ações. A reutilização do fluxo de trabalho também promove práticas recomendadas, ajudando você a usar os fluxos de trabalho bem projetados, Já foram testados e sua eficiência é comprovada. Sua organização pode criar uma biblioteca de fluxos de trabalho reutilizáveis que pode ser mantida centralmente. + +Um fluxo de trabalho que usa outro fluxo de trabalho é referido como um fluxo de trabalho "de chamada". O fluxo de trabalho reutilizável é um fluxo de trabalho "chamado". Um fluxo de trabalho de chamada pode usar vários fluxos de trabalho chamados. Cada fluxo de trabalho chamado é referenciado em uma única linha. O resultado é que o arquivo de fluxo de trabalho de chamadas pode conter apenas algumas linhas de YAML mas pode executar um grande número de tarefas quando for executado. Quando um fluxo de trabalho é reutilizado, todo o fluxo de trabalho chamado é usado, como se fosse parte do fluxo de trabalho de chamada. + +Se você reutilizar um fluxo de trabalho de um repositório diferente, todas as ações no fluxo de trabalho chamado são como se fizessem parte do fluxo de trabalho de chamada. Por exemplo, se o fluxo de trabalho chamado usar `ações/checkout`, a ação verifica o conteúdo do repositório que hospeda o fluxo de trabalho de chamada, não o fluxo de trabalho chamado. + +Quando um fluxo de trabalho reutilizável é acionado por um fluxo de trabalho de chamadas, o contexto `github` está sempre associado ao fluxo de trabalho de chamada. Para obter mais informações sobre o contexto do github ``, consulte "[Contexto e sintaxe de expressão para o GitHub Actions](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)". + +## Acesso a fluxos de trabalho reutilizáveis + +Um fluxo de trabalho reutilizável pode ser usado por outro fluxo de trabalho se qualquer uma das seguintes opções for verdadeira: + +* Ambos os fluxos de trabalho estão no mesmo repositório. +* O fluxo de trabalho chamado é armazenado em um repositório público. +* O fluxo de trabalho chamado é armazenado em um repositório interno e as configurações para esse repositório permitem que ele seja acessado. Para obter mais informações, consulte "[Gerenciar 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#allowing-access-to-components-in-an-internal-repository)". + +## Limitações + +* Os fluxos de trabalho reutilizáveis não podem chamar outros fluxos de trabalho reutilizáveis. +* Os fluxos de trabalho armazenados dentro de um repositório privado só podem ser usados por fluxos de trabalho dentro do mesmo repositório. +* Qualquer variável de ambiente definida em um contexto `env` definido no nível do fluxo de trabalho no fluxo de trabalho da chamada não é propagada para o fluxo de trabalho chamado. Para obter mais informações sobre o contexto `env`, consulte "[Contexto e sintaxe de expressão para o GitHub Actions](/actions/reference/context-and-expression-syntax-for-github-actions#env-context)". + +As seguintes limitações serão removidas quando o fluxo de trabalho reutilizar os movimentos do beta: +* Os fluxos de trabalho reutilizáveis não podem fazer referência a executores auto-hospedados. +* Não é possível definir a concorrência de um fluxo de trabalho chamado a partir do fluxo de trabalho de chamada. Para obter mais informações sobre `trabalhos..concurrency`, consulte "[Sintaxe de fluxo de trabalho para o GitHub Actions](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idconcurrency)". +* As saídas geradas por um fluxo de trabalho chamado não podem ser acessadas pelo fluxo de trabalho de chamada. + +## Criar um fluxo de trabalho reutilizável + +Os fluxos de trabalho reutilizáveis são arquivos formatados com YAML, muito semelhantes a qualquer outro arquivo de fluxo de trabalho. Como em outros arquivos de fluxo de trabalho, você localiza os fluxos de trabalho reutilizáveis no diretório `.github/workflows` de um repositório. Os subdiretórios do diretóriio `fluxos de trabalho` não são compatíveis. + +Para que um fluxo de trabalho seja reutilizável, os valores de `on` devem incluir `workflow_call`: + +```yaml +on: + workflow_call: +``` + +Você pode definir entradas e segredos, que podem ser passados do fluxo de trabalho de de chamada e, em seguida, usados no fluxo de trabalho chamado. O exemplo a seguir de um fluxo de trabalho reutilizável define duas entradas (denominadas de "anel" e "ambiente") e um segredo (denominado "token"): + +```yaml +on: + workflow_call: + inputs: + ring: + description: 'Identifier for the target deployment ring' + default: 'ring-0' + required: false + type: string + environment: + required: false + type: string + secrets: + token: + required: false +``` + +Para obter informações sobre a sintaxe e definir entradas e segredos, consulte [on.workflow_call.inputs](/actions/reference/workflow-syntax-for-github-actions#onworkflow_callinputs) e [on.workflow_call.secrets](/actions/reference/workflow-syntax-for-github-actions#onworkflow_callsecrets). + +### Exemplo de fluxo de trabalho reutilizável + +Este arquivo de fluxo de trabalho reutilizável denominado `workflow-B. ml` (vamos mencioná-lo mais adiante) recebe uma string de entrada e um segredo do fluxo de trabalho de chamada e os usa em uma ação. + +{% raw %} +```yaml{:copy} +name: Reusable workflow example + +on: + workflow_call: + inputs: + username: + required: true + type: string + secrets: + token: + required: true + +jobs: + example_job: + name: Pass input and secrets to my-action + runs-on: ubuntu-latest + steps: + - uses: ./.github/actions/my-action@v1 + with: + username: ${{ inputs.username }} + token: ${{ secrets.token }} +``` +{% endraw %} + +## Chamando um fluxo de trabalho reutilizável + +Você chama um fluxo de trabalho reutilizável usando a chave `usa`. Ao contrário de quando você usa ações em um fluxo de trabalho, você chama os fluxos de trabalho reutilizáveis diretamente em um trabalho, e não de dentro de etapas de trabalho. + +[`jobs..uses`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_iduses) + +Você faz referência a arquivos reutilizáveis do fluxo de trabalho usando a sintaxe: + +`{owner}/{repo}/{path}/{filename}@{ref}` + +Você pode chamar vários fluxos de trabalho, fazendo referência a cada um em um trabalho separado. + +{% data reusables.actions.uses-keyword-example %} + +### Passando entradas e segredos para um fluxo de trabalho reutilizável + +Use a palavra-chave `com` em uma tarefa para passar entradas nomeadas para o fluxo de trabalho chamado. Use a palavra-chave `segredos` para passar segredos nomeados. As entradas e segredos que você passou devem ser definidos no fluxo de trabalho chamado. Para as entradas, o tipo de dado do valor de entrada deve corresponder ao tipo especificado para essa entrada no fluxo de trabalho chamado (booleano, número ou string). + +{% raw %} +```yaml +with: + username: mona +secrets: + token: ${{ secrets.TOKEN }} +``` +{% endraw %} + +### Palavras-chave compatíveis com trabalhos que chamam um fluxo de trabalho reutilizável + +Ao chamar um fluxo de trabalho reutilizável, você só poderá usar as palavras-chave a seguir no trabalho que contém a chamada: + +* [`jobs..name`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idname) +* [`jobs..uses`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_iduses) +* [`jobs..with`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idwith) +* [`jobs..with.`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idwithinput_id) +* [`jobs..secrets`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idsecrets) +* [`jobs..secrets.`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idsecretssecret_id) +* [`jobs..needs`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds) +* [`jobs..if`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idif) +* [`jobs..permissions`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idpermissions) + + {% note %} + + **Observação:** + + * Se `jobs..permissions` não for especificado no trabalho de chamadas, o fluxo de trabalho chamado terá as permissões padrão para o `GITHUB_TOKEN`. Para obter mais informações, consulte "[Autenticação em um fluxo de trabalho](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)". + * As permissões de `GITHUB_TOKEN` passadas do fluxo de trabalho de de cahamada só podem ser rebaixadas (não elevadas) pelo fluxo de trabalho chamado. + + {% endnote %} + +### Exemplo de fluxo de trabalho de chamada + +Este arquivo de fluxo de trabalho chama dois arquivos de fluxo de trabalho. O segundo deles: `workflow-B.yml` (exibido acima) passa uma entrada, `nome de usuário` e um segredo, `token`. + +{% raw %} +```yaml{:copy} +name: Call a reusable workflow + +on: + pull_request: + branches: + - main + +jobs: + call-workflow: + uses: octo-org/example-repo/.github/workflows/workflow-A.yml@v1 + + call-workflow-passing-data: + uses: octo-org/example-repo/.github/workflows/workflow-B.yml@main + with: + username: mona + secrets: + token: ${{ secrets.TOKEN }} +``` +{% endraw %} + +## Próximas etapas + +Para continuar aprendendo sobre {% data variables.product.prodname_actions %}, consulte "[Eventos que desencadeiam fluxos de trabalho](/actions/learn-github-actions/events-that-trigger-workflows)". diff --git a/translations/pt-BR/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md b/translations/pt-BR/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md new file mode 100644 index 0000000000..302740ba0a --- /dev/null +++ b/translations/pt-BR/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md @@ -0,0 +1,53 @@ +--- +title: 'Compartilhando fluxos de trabalho, segredos e executores com a sua organização' +shortTitle: Compartilhar fluxos de trabalho com a sua organização +intro: 'Aprenda como usar recursos da organização para colaborar com a sua equipe, compartilhando modelos de fluxo de trabalho, segredos e executores auto-hospedados.' +redirect_from: + - /actions/learn-github-actions/sharing-workflows-with-your-organization +versions: + fpt: '*' + ghes: '*' + ghae: '*' +type: how_to +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +## Visão Geral + +Se você precisar compartilhar fluxos de trabalho e outros recursos de {% data variables.product.prodname_actions %} com a sua equipe, considere colaborar dentro de uma organização de {% data variables.product.prodname_dotcom %}. Uma organização permite que você armazene e gerencie, centralizadamente, segredos, artefatos e executores auto-hospedados. Você também pode criar modelos de fluxo de trabalho no repositório `.github` e compartilhá-los com outros usuários na sua organização. + +## Usando modelos de fluxo de trabalho + +{% data reusables.actions.workflow-organization-templates %} Para obter mais informações, consulte "[Criando modelos de fluxo de trabalho](/actions/learn-github-actions/creating-workflow-templates)". + +{% data reusables.actions.reusable-workflows %} + +## Compartilhar segredos dentro de uma organização + +Você pode gerenciar seus segredos centralmente dentro de uma organização e, em seguida, disponibilizá-los para repositórios selecionados. Isso também significa que você pode atualizar um segredo em um único local e fazer com que a alteração seja aplicada em todos os fluxos de trabalho do repositório que usam o segredo. + +Ao criar um segredo em uma organização, você pode usar uma política para limitar quais repositórios podem acessar esse segredo. Por exemplo, você pode conceder acesso a todos os repositórios ou limitar o acesso a apenas repositórios privados ou a uma lista específica de repositórios. + +{% data reusables.github-actions.permissions-statement-secrets-organization %} + +{% data reusables.organizations.navigate-to-org %} +{% data reusables.organizations.org_settings %} +{% data reusables.github-actions.sidebar-secret %} +1. Clique em **Novo segredo**. +1. Digite um nome para o seu segredo na caixa de entrada **Nome**. +1. Insira o **Valor** para o seu segredo. +1. Na lista suspensa **Acesso do repositório**, escolha uma política de acesso. +1. Clique em **Add secret** (Adicionar segredo). + +## Compartilhe executores auto-hospedados dentro de uma organização + +Os administradores da organização podem adicionar seus executores auto-hospedados para grupos e, em seguida, criar políticas que controlam quais repositórios podem acessar o grupo. + +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)". + + +## Próximas etapas + +Para continuar aprendendo sobre {% data variables.product.prodname_actions %}, consulte "[Criar modelos de fluxo de trabalho](/actions/learn-github-actions/creating-workflow-templates)". diff --git a/translations/pt-BR/content/actions/learn-github-actions/understanding-github-actions.md b/translations/pt-BR/content/actions/learn-github-actions/understanding-github-actions.md index 384183a37f..b18e1b2690 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/understanding-github-actions.md +++ b/translations/pt-BR/content/actions/learn-github-actions/understanding-github-actions.md @@ -1,7 +1,7 @@ --- -title: Understanding GitHub Actions -shortTitle: Understanding GitHub Actions -intro: 'Learn the basics of {% data variables.product.prodname_actions %}, including core concepts and essential terminology.' +title: Entendendo o GitHub Actions +shortTitle: Entendendo o GitHub Actions +intro: 'Aprenda o básico de {% data variables.product.prodname_actions %}, incluindo conceitos fundamentais e terminologia essencial.' redirect_from: - /github/automating-your-workflow-with-github-actions/core-concepts-for-github-actions - /actions/automating-your-workflow-with-github-actions/core-concepts-for-github-actions @@ -18,7 +18,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Visão Geral @@ -36,7 +35,7 @@ Abaixo está uma lista dos múltiplos componentes de {% data variables.product.p ### Fluxos de trabalho -O fluxo de trabalho é um procedimento automatizado que você adiciona ao seu repositório. Os fluxos de trabalho são constituídos por um ou mais trabalhos e podem ser programados ou ativados por um evento. O fluxo de trabalho pode ser usado para criar, testar, empacotar, publicar ou implantar um projeto em {% data variables.product.prodname_dotcom %}. +O fluxo de trabalho é um procedimento automatizado que você adiciona ao seu repositório. Os fluxos de trabalho são constituídos por um ou mais trabalhos e podem ser programados ou ativados por um evento. O fluxo de trabalho pode ser usado para criar, testar, empacotar, publicar ou implantar um projeto em {% data variables.product.prodname_dotcom %}. {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %}Você pode consultar um fluxo de trabalho dentro de outro fluxo de trabalho. Consulte "[Reutilizando fluxos de trabalho](/actions/learn-github-actions/reusing-workflows)"{% endif %} ### Eventos @@ -179,7 +178,7 @@ Para ajudar você a entender como a sintaxe de YAML é usada para criar um arqui ```     		- This step uses the actions/setup-node@v2 action to install the specified version of the node software package on the runner, which gives you access to the npm command. + Esta etapa usa a ação actions/setup-node@v2 para instalar a versão especificada do pacote de software do nó no executor, que fornece a você acesso ao comando npm.
    -For more information, see "[Expressions](/actions/learn-github-actions/expressions)." +Para obter mais informações, consulte "[Expressões](/actions/learn-github-actions/expressions)". ## Dependências entre trabalhos diff --git a/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md b/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md index 5f6e79a582..37c6742679 100644 --- a/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md +++ b/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md @@ -19,7 +19,6 @@ shortTitle: Fazer a migração a partir do CircleCI {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introdução diff --git a/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md b/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md index 79bbb740a1..b4f6ad504c 100644 --- a/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md +++ b/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md @@ -18,7 +18,6 @@ shortTitle: Fazer a migração a partir da CI/CD do GitLab {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introdução @@ -133,7 +132,7 @@ Para obter mais informações, consulte "[Sintaxe do fluxo de trabalho para {% d ## Imagens do Docker -Tanto o GitLab CI/CD quanto o {% data variables.product.prodname_actions %} são compatíveis com trabalhos executados em uma imagem do Docker. In GitLab CI/CD, Docker images are defined with an `image` key, while in {% data variables.product.prodname_actions %} it is done with the `container` key. +Tanto o GitLab CI/CD quanto o {% data variables.product.prodname_actions %} são compatíveis com trabalhos executados em uma imagem do Docker. Na CI/CD do GitLab, as imagens do Docker são definidas com uma chave `de imagem`, enquanto em {% data variables.product.prodname_actions %}, isso é feito com a chave `contêiner`. Abaixo, há um exemplo da sintaxe para cada sistema: @@ -212,7 +211,7 @@ jobs: -For more information, see "[Expressions](/actions/learn-github-actions/expressions)." +Para obter mais informações, consulte "[Expressões](/actions/learn-github-actions/expressions)". ## Dependências entre trabalhos diff --git a/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md b/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md index aec442346d..d117c225d4 100644 --- a/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md +++ b/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md @@ -19,7 +19,6 @@ shortTitle: Fazer a migração a partir do Jenkins {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introdução @@ -43,7 +42,7 @@ Para obter mais informações, consulte "[Conceitos básicos para {% data variab O Jenkins permite que se envie criações para um único agente de criação, ou você pode distribuí-las entre vários agentes. Você também pode classificar esses agentes de acordo com vários atributos, como, por exemplo, tipos de sistema operacional. -De modo similar, o {% data variables.product.prodname_actions %} pode enviar trabalhos para executores hospedados em {% data variables.product.prodname_dotcom %} ou executores auto-hospedados, e você pode usar as etiquetas para classificar os executores de acordo com vários atributos. For more information, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions#runners)" and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)." +De modo similar, o {% data variables.product.prodname_actions %} pode enviar trabalhos para executores hospedados em {% data variables.product.prodname_dotcom %} ou executores auto-hospedados, e você pode usar as etiquetas para classificar os executores de acordo com vários atributos. Para obter mais informações, consulte "[Entender {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions#runners)" e "[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)". ### Usar seções para organizar pipelines 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 4249bac7b9..0ec69dfe60 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 @@ -19,7 +19,6 @@ shortTitle: Fazer a migração a partir da CI do Travis {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introdução @@ -205,7 +204,7 @@ 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: - - [Building and testing Node.js or Python](/actions/guides/building-and-testing-nodejs-or-python) + - [Criar e testar Node.js ou Python](/actions/guides/building-and-testing-nodejs-or-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) @@ -238,7 +237,7 @@ Ao migrar para {% data variables.product.prodname_actions %}, existem diferentes ## Migrar a sintaxe para condicionais e expressões -Para executar trabalhos sob expressões condicionais, o Travis CI e {% data variables.product.prodname_actions %} compartilham uma sintaxe condicional do tipo `se` similar. {% data variables.product.prodname_actions %} permite que você use a condicional do tipo `se` para evitar que um trabalho ou etapa seja executado, a menos que uma condição seja atendida. For more information, see "[Expressions](/actions/learn-github-actions/expressions)." +Para executar trabalhos sob expressões condicionais, o Travis CI e {% data variables.product.prodname_actions %} compartilham uma sintaxe condicional do tipo `se` similar. {% data variables.product.prodname_actions %} permite que você use a condicional do tipo `se` para evitar que um trabalho ou etapa seja executado, a menos que uma condição seja atendida. Para obter mais informações, consulte "[Expressões](/actions/learn-github-actions/expressions)". Este exemplo demonstra como uma condicional do tipo `se` pode controlar se uma etapa é executada: diff --git a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md index 897c706111..f27dbc3777 100644 --- a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md +++ b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md @@ -1,20 +1,19 @@ --- -title: About monitoring and troubleshooting -intro: 'You can use the tools in {% data variables.product.prodname_actions %} to monitor and debug your workflows.' +title: Sobre monitoramento e solução de problemas +intro: 'Você pode utilizar as ferramentas em {% data variables.product.prodname_actions %} para monitorar e depurar seus fluxos de trabalho.' product: '{% data reusables.gated-features.actions %}' versions: fpt: '*' ghes: '*' ghae: '*' -shortTitle: About monitoring and troubleshooting +shortTitle: Sobre monitoramento e solução de problemas miniTocMaxHeadingLevel: 3 --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -## Monitoring your workflows +## Monitorando seus fluxos de trabalho {% ifversion fpt or ghae or ghes > 3.0 %} @@ -24,7 +23,7 @@ Cada execução de fluxo de trabalho gera um gráfico em tempo real que ilustra ![Gráfico de fluxo de trabalho](/assets/images/help/images/workflow-graph.png) -For more information, see "[Using the visualization graph](/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph)." +Para obter mais informações, consulte "[Usar o gráfico de visualização](/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph)". {% endif %} @@ -37,7 +36,7 @@ Para obter mais informações, consulte "[Adicionando um selo de status do fluxo {% ifversion fpt %} ### Visualizar o tempo de execução do trabalho -To identify how long a job took to run, you can view its execution time. Por exemplo: +Para identificar quanto tempo um trabalho levou para ser executado, você pode ver seu tempo de execução. Por exemplo: ![Link com informações sobre o tempo faturável e execução](/assets/images/help/repository/view-run-billable-time.png) @@ -46,17 +45,17 @@ Para obter mais informações, consulte "[Visualizar o tempo de execução do tr ### Visualizar o histórico de execução do fluxo de trabalho -You can view the status of each job and step in a workflow. Por exemplo: +Você pode visualizar o status de cada trabalho e etapa de um fluxo de trabalho. Por exemplo: ![Nome da execução do fluxo de trabalho](/assets/images/help/repository/run-name.png) Para obter mais informações, consulte "[Visualizar histórico de execução de fluxo de trabalho](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)". -## Troubleshooting your workflows +## Solucionando problemas dos seus fluxos de trabalho ### Usar registros de execução do fluxo de trabalho -Each workflow run generates activity logs that you can view, search, and download. Por exemplo: +A execução de cada fluxo de trabalho gera registros de atividade que você pode visualizar, pesquisar e baixar. Por exemplo: ![Resultados do fluxo de trabalho do Super linter](/assets/images/help/repository/super-linter-workflow-results-updated-2.png) @@ -68,6 +67,6 @@ Se os logs do fluxo de trabalho não fornecerem detalhes suficientes para diagno ## Monitoramento e resolução de problemas dos executores auto-hospedados -If you use self-hosted runners, you can view their activity and diagnose common issues. +Se você usar executores auto-hospedados, você poderá ver a atividade deles e diagnosticar problemas comuns. Para obter mais informações, consulte "[Monitoring and troubleshooting self-hosted runners](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners)." diff --git a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md index 99c3e009a4..e37d6caa8c 100644 --- a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md +++ b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md @@ -13,7 +13,6 @@ shortTitle: Adicionar um selo de status {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.repositories.actions-workflow-status-badge-intro %} diff --git a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md index 63af1fb8d8..52d3c1a569 100644 --- a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md +++ b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md @@ -12,7 +12,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} Esses registros adicionais são habilitados pela definição dos segredos no repositório que contém o fluxo de trabalho. Portanto, aplicam-se os mesmos requisitos de permissão: diff --git a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/index.md b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/index.md index 86f4eb744d..3339a8377e 100644 --- a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/index.md +++ b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/index.md @@ -1,7 +1,7 @@ --- -title: Monitoring and troubleshooting workflows +title: Monitoramento e solução de problemas shortTitle: Monitorar & solucionar problemas -intro: 'You can view the status and results of each step in your workflow, debug a failed workflow, search and download logs, and view billable job execution minutes.' +intro: 'Você pode visualizar o status e os resultados de cada etapa do seu fluxo de trabalho, depurar um fluxo de trabalho com falha, pesquisar e fazer o download de registros e ver as minutas de execução de trabalhos faturáveis.' redirect_from: - /articles/viewing-your-repository-s-workflows - /articles/viewing-your-repositorys-workflows @@ -17,9 +17,8 @@ children: - /viewing-job-execution-time - /using-workflow-run-logs - /enabling-debug-logging + - /notifications-for-workflow-runs --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% ifversion fpt or ghes > 3.0 or ghae %}{% endif %} diff --git a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md new file mode 100644 index 0000000000..89803a5029 --- /dev/null +++ b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md @@ -0,0 +1,15 @@ +--- +title: Notificações para execução de fluxo de trabalho +intro: Você pode assinar as notificações sobre execuções do fluxo de trabalho que você acionar. +product: '{% data reusables.gated-features.actions %}' +versions: + fpt: '*' + ghes: '*' + ghae: '*' +shortTitle: Notificações +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +{% data reusables.repositories.workflow-notifications %} diff --git a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md index b6ded2d021..598c5e0184 100644 --- a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md +++ b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md @@ -13,7 +13,6 @@ shortTitle: Usar o gráfico de visualização {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} diff --git a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md index 17d71ec3c9..698b0481f0 100644 --- a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md +++ b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md @@ -12,7 +12,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} Na página de execução de fluxo de trabalho, você pode verificar se a execução está em andamento ou foi concluída. Você deve estar conectado a uma conta {% data variables.product.prodname_dotcom %} para visualizar as informações da execução do seu fluxo de trabalho, incluindo os repositórios públicos. Para obter mais informações, consulte "[Permissões de acesso no GitHub](/articles/access-permissions-on-github)". @@ -69,7 +68,7 @@ Você pode fazer o download dos arquivos de registro da execução do seu fluxo {% data reusables.repositories.view-run-superlinter %} {% data reusables.repositories.navigate-to-job-superlinter %} {% ifversion fpt or ghes > 2.22 or ghae %} -1. In the upper right corner, click {% ifversion fpt or ghes > 3.0 or ghae %}{% octicon "gear" aria-label="The gear icon" %}{% else %}{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}{% endif %} and select **Download log archive**. +1. No canto superior direito, clique em {% ifversion fpt or ghes > 3.0 or ghae %}{% octicon "gear" aria-label="The gear icon" %}{% else %}{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}{% endif %} e selecione **Fazer download do arquivo de registro**. {% ifversion fpt or ghes > 3.0 or ghae %} ![Menu suspenso Download logs (Baixar logs)](/assets/images/help/repository/download-logs-drop-down-updated-2.png) {% else %} diff --git a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md index 9d50d3a9df..05274f6b49 100644 --- a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md +++ b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md @@ -11,7 +11,6 @@ shortTitle: Visualizar tempo de execução do trabalho {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} Os minutos de execução de um trabalho faturável são exibidos para trabalhos executados em repositórios privados que usam executores hospedados em {% data variables.product.prodname_dotcom %}. Não há minutos faturáveis ao usar {% data variables.product.prodname_actions %} nos repositórios públicos ou para trabalhos executados em executores auto-hospedados. diff --git a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md index f2959f65f4..7e6d65aef2 100644 --- a/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md +++ b/translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md @@ -13,7 +13,6 @@ shortTitle: Visualizar o histórico de execução do fluxo de trabalho {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.repositories.permissions-statement-read %} diff --git a/translations/pt-BR/content/actions/publishing-packages/about-packaging-with-github-actions.md b/translations/pt-BR/content/actions/publishing-packages/about-packaging-with-github-actions.md index 654aca2eee..aa7260bfb7 100644 --- a/translations/pt-BR/content/actions/publishing-packages/about-packaging-with-github-actions.md +++ b/translations/pt-BR/content/actions/publishing-packages/about-packaging-with-github-actions.md @@ -18,7 +18,6 @@ shortTitle: Empacotando com GitHub Actions {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.package_registry.about-packaging-and-actions %} diff --git a/translations/pt-BR/content/actions/publishing-packages/index.md b/translations/pt-BR/content/actions/publishing-packages/index.md index c50c2bc55e..90d74ddc7b 100644 --- a/translations/pt-BR/content/actions/publishing-packages/index.md +++ b/translations/pt-BR/content/actions/publishing-packages/index.md @@ -1,7 +1,7 @@ --- title: Publicar pacotes shortTitle: Publicar pacotes -intro: 'You can automatically publish packages using {% data variables.product.prodname_actions %}.' +intro: 'Você pode publicar pacotes automaticamente usando {% data variables.product.prodname_actions %}.' versions: fpt: '*' ghes: '*' diff --git a/translations/pt-BR/content/actions/publishing-packages/publishing-docker-images.md b/translations/pt-BR/content/actions/publishing-packages/publishing-docker-images.md index 73faf50ade..c450f4b1b1 100644 --- a/translations/pt-BR/content/actions/publishing-packages/publishing-docker-images.md +++ b/translations/pt-BR/content/actions/publishing-packages/publishing-docker-images.md @@ -18,7 +18,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introdução @@ -121,7 +120,7 @@ As opções de `login-action` de login necessárias para {% data variables.produ * `senha`: Você pode usar o segredo `GITHUB_TOKEN` gerado automaticamente para a senha. Para obter mais informações, consulte "[Permissões para o GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)". {% ifversion fpt %} -The `metadata-action` option required for {% data variables.product.prodname_registry %} is: +A opção `metadata-action` obrigatória para {% data variables.product.prodname_registry %} é: * `imagens`: O espaço do nome e o nome da imagem Docker que você está criando. {% endif %} @@ -134,7 +133,7 @@ As opções de `build-push-action` necessárias para {% data variables.product.p {% ifversion fpt %} {% data reusables.package_registry.publish-docker-image %} -O fluxo de trabalho acima, se acionado por um push para o branch "versão". Ele verifica o repositório GitHub e usa `login-action` para fazer login no {% data variables.product.prodname_container_registry %}. Em seguida, extrai etiquetas e tags para a imagem do Docker. Finally, it uses the `build-push-action` action to build the image and publish it on the {% data variables.product.prodname_container_registry %}. +O fluxo de trabalho acima, se acionado por um push para o branch "versão". Ele verifica o repositório GitHub e usa `login-action` para fazer login no {% data variables.product.prodname_container_registry %}. Em seguida, extrai etiquetas e tags para a imagem do Docker. Finalmente, ele usa a ação `de build-push-action` para criar a imagem e publicá-la no {% data variables.product.prodname_container_registry %}. {% else %} ```yaml{:copy} @@ -173,7 +172,7 @@ jobs: {% ifversion ghae %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}{% raw %}/${{ github.repository }}/octo-image:${{ github.event.release.tag_name }}{% endraw %} ``` -The above workflow checks out the {% data variables.product.prodname_dotcom %} repository, uses the `login-action` to log in to the registry, and then uses the `build-push-action` action to: build a Docker image based on your repository's `Dockerfile`; push the image to the Docker registry, and apply the commit SHA and release version as image tags. +O fluxo de trabalho acima faz o check-out do repositório {% data variables.product.prodname_dotcom %}, usa o `login-action` para efetuar o login no registro e, em seguida, usa a ação `build-push-action` para criar uma imagem Docker com base no `arquivo Docker` do seu repositório; fazer push da imagem para o registro Docker e aplicar o commit SHA e a versão como tags de imagem. {% endif %} ## Publicar imagens no Docker Hub e {% data variables.product.prodname_registry %} diff --git a/translations/pt-BR/content/actions/publishing-packages/publishing-java-packages-with-gradle.md b/translations/pt-BR/content/actions/publishing-packages/publishing-java-packages-with-gradle.md index beb2cf6d0f..d60d501704 100644 --- a/translations/pt-BR/content/actions/publishing-packages/publishing-java-packages-with-gradle.md +++ b/translations/pt-BR/content/actions/publishing-packages/publishing-java-packages-with-gradle.md @@ -20,7 +20,6 @@ shortTitle: Pacotes do Java com Gradle {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introdução @@ -142,7 +141,7 @@ publishing { ``` {% endraw %} -With this configuration, you can create a workflow that publishes your package to {% data variables.product.prodname_registry %} by running the `gradle publish` command. +Com esta configuração, você pode criar um fluxo de trabalho que publica seu pacote em {% data variables.product.prodname_registry %}, executando o comando `gradle publish`. ```yaml{:copy} {% data reusables.actions.actions-not-certified-by-github-comment %} @@ -184,7 +183,7 @@ Certifique-se de que seu arquivo _build.gradle_ inclua um repositório para seu Por exemplo, se fizer a implementação no Repositório Central por meio do projecto de hospedagem OSSRH, é possível que você deseje especificá-lo em um repositório de gerenciamento de distribuição com o `nome` definido como `OSSRH`. Se você fizer a implementação em {% data variables.product.prodname_registry %}, é possível que você deseje especificá-lo em um repositório de gerenciamento de distribuição com o nome `` definido como `GitHubPackages`. -If your organization is named "octocat" and your repository is named "hello-world", then the configuration in _build.gradle_ would look similar to the below example. +Se sua organização for denominada "octocat" e seu repositório for denominado "hello-world", a configuração em _build.gradle_ será parecida ao exemplo abaixo. {% raw %} ```groovy{:copy} diff --git a/translations/pt-BR/content/actions/publishing-packages/publishing-java-packages-with-maven.md b/translations/pt-BR/content/actions/publishing-packages/publishing-java-packages-with-maven.md index aa8c215732..24814f96c6 100644 --- a/translations/pt-BR/content/actions/publishing-packages/publishing-java-packages-with-maven.md +++ b/translations/pt-BR/content/actions/publishing-packages/publishing-java-packages-with-maven.md @@ -20,7 +20,6 @@ shortTitle: Pacotes Java com Maven {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introdução diff --git a/translations/pt-BR/content/actions/publishing-packages/publishing-nodejs-packages.md b/translations/pt-BR/content/actions/publishing-packages/publishing-nodejs-packages.md index 98246ae887..9a21c69846 100644 --- a/translations/pt-BR/content/actions/publishing-packages/publishing-nodejs-packages.md +++ b/translations/pt-BR/content/actions/publishing-packages/publishing-nodejs-packages.md @@ -21,7 +21,6 @@ shortTitle: Pacotes do Node.js {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introdução diff --git a/translations/pt-BR/content/actions/quickstart.md b/translations/pt-BR/content/actions/quickstart.md index 880eeccfc4..ddf2dc111f 100644 --- a/translations/pt-BR/content/actions/quickstart.md +++ b/translations/pt-BR/content/actions/quickstart.md @@ -16,7 +16,6 @@ shortTitle: QuickStart {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introdução @@ -26,8 +25,8 @@ O exemplo a seguir mostra como os trabalhos de {% data variables.product.prodnam ## Criar o seu primeiro fluxo de trabalho -1. Create a `.github/workflows` directory in your repository on {% data variables.product.prodname_dotcom %} if this directory does not already exist. -2. In the `.github/workflows` directory, create a file named `github-actions-demo.yml`. Para obter mais informações, consulte "[Criar arquivos](/github/managing-files-in-a-repository/creating-new-files)". +1. Crie um diretório `.github/workflows` no repositório {% data variables.product.prodname_dotcom %} se este diretório não existir. +2. No diretório `.github/workflows`, crie um arquivo denominado `github-actions-demo.yml`. Para obter mais informações, consulte "[Criar arquivos](/github/managing-files-in-a-repository/creating-new-files)". 3. Copie o conteúdo de YAML a seguir para o arquivo `github-actions-demo.yml`: {% raw %} ```yaml{:copy} diff --git a/translations/pt-BR/content/actions/security-guides/automatic-token-authentication.md b/translations/pt-BR/content/actions/security-guides/automatic-token-authentication.md index 45798ae1d3..a25f70c419 100644 --- a/translations/pt-BR/content/actions/security-guides/automatic-token-authentication.md +++ b/translations/pt-BR/content/actions/security-guides/automatic-token-authentication.md @@ -1,5 +1,5 @@ --- -title: Automatic token authentication +title: Autenticação automática de token intro: '{% data variables.product.prodname_dotcom %} fornece um token que você pode usar para autenticar em nome de {% data variables.product.prodname_actions %}.' product: '{% data reusables.gated-features.actions %}' redirect_from: @@ -11,16 +11,15 @@ versions: fpt: '*' ghes: '*' ghae: '*' -shortTitle: Automatic token authentication +shortTitle: Autenticação automática de token --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Sobre o segredo `GITHUB_TOKEN` -At the start of each workflow run, {% data variables.product.prodname_dotcom %} automatically creates a unique `GITHUB_TOKEN` secret to use in your workflow. Você pode usar o `GITHUB_TOKEN` para autenticar em uma execução de fluxo de trabalho. +No início da execução de cada fluxo de trabalho, {% data variables.product.prodname_dotcom %} cria automaticamente um segredo exclusivo de `GITHUB_TOKEN` para usar no seu fluxo de trabalho. Você pode usar o `GITHUB_TOKEN` para autenticar em uma execução de fluxo de trabalho. Ao habilitar {% data variables.product.prodname_actions %}, {% data variables.product.prodname_dotcom %} instala um {% data variables.product.prodname_github_app %} no seu repositório. O segredo `GITHUB_TOKEN` é um token de acesso de instalação {% data variables.product.prodname_github_app %}. Você pode usar o token de acesso de instalação para autenticar em nome do {% data variables.product.prodname_github_app %} instalado no seu repositório. As permissões do token são restritas ao repositório do fluxo de trabalho. Para obter mais informações, consulte "[Permissões para o `GITHUB_TOKEN`](#permissions-for-the-github_token)". @@ -98,7 +97,7 @@ jobs: Para obter informações sobre quais os pontos de extremidade da API de {% data variables.product.prodname_github_apps %} podem acessar com cada permissão, consulte "[Permissões de {% data variables.product.prodname_github_app %}](/rest/reference/permissions-required-for-github-apps)." {% ifversion fpt or ghes > 3.1 or ghae-next %} -A tabela a seguir mostra as permissões concedidas ao `GITHUB_TOKEN` por padrão. People with admin permissions to an {% ifversion not ghes %}enterprise, organization, or repository,{% else %}organization or repository{% endif %} can set the default permissions to be either permissive or restricted. For information on how to set the default permissions for the `GITHUB_TOKEN` for your {% ifversion not ghes %}enterprise, organization, or repository,{% else %}organization or repository,{% endif %} see {% ifversion not ghes %}"[Enforcing {% data variables.product.prodname_actions %} policies in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account#setting-the-permissions-of-the-github_token-for-your-enterprise)," {% 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#setting-the-permissions-of-the-github_token-for-your-organization)," or "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#setting-the-permissions-of-the-github_token-for-your-repository)." +A tabela a seguir mostra as permissões concedidas ao `GITHUB_TOKEN` por padrão. As pessoas com permissões de administrador para uma empresa, organização ou repositório de {% ifversion not ghes %}{% else %}organização ou repositório{% endif %} pode definir as permissões padrão como permissivas ou restritas. Para obter informações sobre como definir permissões padrão para `GITHUB_TOKEN` para a sua {% ifversion not ghes %}empresa, organização ou repositório,{% else %}organização ou repositório,{% endif %}, consulte {% ifversion not ghes %}"[Aplicar políticas de {% data variables.product.prodname_actions %} na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account#setting-the-permissions-of-the-github_token-for-your-enterprise)," {% endif %}"[Desabilitar ou limitar organizações de {% 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#setting-the-permissions-of-the-github_token-for-your-organization)," ou "[Gerenciar 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#setting-the-permissions-of-the-github_token-for-your-repository)." | Escopo | Acesso padrão
    (permissivo) | Acesso padrão
    (restrito) | Acesso máximo
    por repositórios bifurcados | | ----------------------- | ----------------------------------- | --------------------------------- | -------------------------------------------------- | diff --git a/translations/pt-BR/content/actions/security-guides/encrypted-secrets.md b/translations/pt-BR/content/actions/security-guides/encrypted-secrets.md index b854df1c54..070f456918 100644 --- a/translations/pt-BR/content/actions/security-guides/encrypted-secrets.md +++ b/translations/pt-BR/content/actions/security-guides/encrypted-secrets.md @@ -16,7 +16,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Sobre os segredos encriptados @@ -62,7 +61,7 @@ Ao gerar credenciais, recomendamos que você conceda as permissões mínimas pos {% note %} -**Note:** You can use the REST API to manage secrets. Para obter mais informações, consulte "[{% data variables.product.prodname_actions %} secrets API](/rest/reference/actions#secrets)." +**Observação:** Você pode usar a API REST para gerenciar segredos. Para obter mais informações, consulte "[{% data variables.product.prodname_actions %} secrets API](/rest/reference/actions#secrets)." {% endnote %} @@ -90,19 +89,19 @@ Se o seu repositório {% ifversion fpt or ghes > 3.0 or ghae %}tiver segredos de {% data reusables.cli.cli-learn-more %} -To add a repository secret, use the `gh secret set` subcommand. Replace `secret-name` with the name of your secret. +Para adicionar um segredo de repositório, use o subcomando `gh secret set`. Substitua `nome secreto` pelo nome do seu segredo. ```shell gh secret set secret-name ``` -The CLI will prompt you to enter a secret value. Alternatively, you can read the value of the secret from a file. +A CLI solicitará que você digite o valor de um segredo. Como alternativa, você pode ler o valor do segredo a partir de um arquivo. ```shell gh secret set secret-name < secret.txt ``` -To list all secrets for the repository, use the `gh secret list` subcommand. +Para listar todos os segredos para o repositório, use o subcomando da lista `gh secret`. {% endcli %} @@ -129,13 +128,13 @@ To list all secrets for the repository, use the `gh secret list` subcommand. {% cli %} -To add a secret for an environment, use the `gh secret set` subcommand with the `--env` or `-e` flag followed by the environment name. +Para adicionar um segredo a um ambiente, use o subcomando `secret set` com o sinalizador `--env` ou `-e`, seguido do nome do ambiente. ```shell gh secret set --env environment-name secret-name ``` -To list all secrets for an environment, use the `gh secret list` subcommand with the `--env` or `-e` flag followed by the environment name. +Para listar todos os segredos para um ambiente use o subcomando `gh secret list` com o sinalizador `--env` ou `-e` seguido do nome do ambiente. ```shell gh secret list --env environment-name @@ -170,7 +169,7 @@ Ao criar um segredo em uma organização, você pode usar uma política para lim {% note %} -**Note:** By default, {% data variables.product.prodname_cli %} authenticates with the `repo` and `read:org` scopes. To manage organization secrets, you must additionally authorize the `admin:org` scope. +**Observação:** Por padrão, {% data variables.product.prodname_cli %} efetua a autenticação com os escopos `repo` e `read:org`. Para gerenciar segredos da organização, você deve adicionalmente autorizar o escopo `admin:org`. ``` gh auth login --scopes "admin:org" @@ -178,25 +177,25 @@ gh auth login --scopes "admin:org" {% endnote %} -To add a secret for an organization, use the `gh secret set` subcommand with the `--org` or `-o` flag followed by the organization name. +Para adicionar um segredo de uma organização, use o subcomando `gh secret set` com o sinalizador `--org` ou `-o`, seguido do nome da organização. ```shell gh secret set --org organization-name secret-name ``` -By default, the secret is only available to private repositories. To specify that the secret should be available to all repositories within the organization, use the `--visibility` or `-v` flag. +Por padrão, o segredo só está disponível para repositórios privados. Para especificar que o segredo deve estar disponível para todos os repositórios da organização, use o sinalizador `--visibility` ou `-v`. ```shell gh secret set --org organization-name secret-name --visibility all ``` -To specify that the secret should be available to selected repositories within the organization, use the `--repos` or `-r` flag. +Para especificar que o segredo deve estar disponível nos repositórios selecionados dentro da organização, use o sinalizador `--repos` ou `-r`. ```shell gh secret set --org organization-name secret-name --repos repo-name-1,repo-name-2" ``` -To list all secrets for an organization, use the `gh secret list` subcommand with the `--org` or `-o` flag followed by the organization name. +Para listar todos os segredos de uma organização, use o subcomando `gh secret list` com o sinalizador `--org` ou `-o` seguido do nome da organização. ```shell gh secret list --org organization-name @@ -222,7 +221,7 @@ Você pode verificar quais políticas de acesso são aplicadas a um segredo na s {% endnote %} -Para fornecer uma ação com um segredo como uma entrada ou variável de ambiente, você pode usar o contexto de `segredos` para acessar os segredos que você criou no seu repositório. For more information, see "[Contexts](/actions/learn-github-actions/contexts)" and "[Workflow syntax for {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)." +Para fornecer uma ação com um segredo como uma entrada ou variável de ambiente, você pode usar o contexto de `segredos` para acessar os segredos que você criou no seu repositório. Para obter mais informações, consulte "[Contextos](/actions/learn-github-actions/contexts)" e "[Sintaxe de fluxo de trabalho para {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)". {% raw %} ```yaml diff --git a/translations/pt-BR/content/actions/security-guides/index.md b/translations/pt-BR/content/actions/security-guides/index.md index 370de92095..97790d0b36 100644 --- a/translations/pt-BR/content/actions/security-guides/index.md +++ b/translations/pt-BR/content/actions/security-guides/index.md @@ -1,7 +1,7 @@ --- -title: Security guides -shortTitle: Security guides -intro: 'Security hardening and good practices for {% data variables.product.prodname_actions %}.' +title: Guias de segurança +shortTitle: Guias de segurança +intro: 'Enrijecimento de segurança e práticas recomendadas para {% data variables.product.prodname_actions %}.' versions: fpt: '*' ghes: '*' 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 f454e7c9d5..0485e1e42b 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 @@ -18,7 +18,6 @@ miniTocMaxHeadingLevel: 3 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Visão Geral @@ -48,7 +47,7 @@ Para ajudar a prevenir a divulgação acidental, o {% data variables.product.pro - Gire os segredos periodicamente para reduzir a janela de tempo durante a qual um segredo comprometido é válido. {% ifversion fpt or ghes > 3.0 or ghae %} - **Considere a necessidade de revisão para acesso a segredos** - - Você pode usar revisores necessários para proteger os segredos do ambiente. Um trabalho de fluxo de trabalho não pode acessar segredos de ambiente até que a aprovação seja concedida por um revisor. Para mais informações sobre armazenar segredos em ambientes ou exigir revisões para ambientes, consulte "[segredos criptografados](/actions/reference/encrypted-secrets)" e "[Ambientes](/actions/reference/environments)". + - Você pode usar revisores necessários para proteger os segredos do ambiente. Um trabalho de fluxo de trabalho não pode acessar segredos de ambiente até que a aprovação seja concedida por um revisor. Para mais informações sobre armazenar segredos em ambientes ou exigir revisões para ambientes, consulte "[segredos criptografados](/actions/reference/encrypted-secrets)" e "[Usando ambientes para implantação](/actions/deployment/using-environments-for-deployment)". {% endif %} ## Usar `CODEOWNERS` para monitorar alterações @@ -59,7 +58,7 @@ Para obter mais informações, consulte "[Sobre proprietários do código](/gith ## Entendendo o risco de injeções de script -When creating workflows, [custom actions](/actions/creating-actions/about-actions), and [composite actions](/actions/creating-actions/creating-a-composite-action) actions, you should always consider whether your code might execute untrusted input from attackers. Isso pode ocorrer quando um invasor adiciona comandos maliciosos e scripts em um contexto. Quando seu fluxo de trabalho é executado, essas strings podem ser interpretadas como código que é executado no executado. +Ao criar fluxos de trabalho, [ações personalizadas](/actions/creating-actions/about-actions)e [ações compostas](/actions/creating-actions/creating-a-composite-action), você deverá sempre considerar se seu código pode executar entrada não confiável de invasores. Isso pode ocorrer quando um invasor adiciona comandos maliciosos e scripts em um contexto. Quando seu fluxo de trabalho é executado, essas strings podem ser interpretadas como código que é executado no executado. Os invasores podem adicionar seu próprio conteúdo malicioso ao contexto do [`github`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context), que deve ser tratado como uma entrada potencialmente não confiável. Geralmente, esses contextos terminam com `body`, `default_branch`, `email`, `head_ref`, `label`, `message`, `name`, `page_name`,`ref` e `title`. Por exemplo: `github.event.issue.title` ou `github.event.pull_request.body`. @@ -183,6 +182,12 @@ Você pode ajudar a mitigar esse risco seguindo estas boas práticas: Embora a fixação de um commit de SHA seja a opção mais segura, especificar uma etiqueta é a opção mais conveniente, além de ser amplamente usada. Se você desejar de especificar uma etiqueta, certifique-se de que você confia nos criadores da ação. O selo "Criador verificado" em {% data variables.product.prodname_marketplace %} é um sinal útil, já que indica que a ação foi escrita por uma equipe cuja identidade foi verificada por {% data variables.product.prodname_dotcom %}. Observe que há risco para esta abordagem, mesmo que você confie no autor, porque uma etiqueta pode ser movida ou excluída se um ator malicioso obtiver acesso ao repositório que armazena a ação. +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## Reutilizando fluxos de trabalho de terceiros + +Os mesmos princípios descritos acima para o uso de ações de terceiros também se aplicam ao uso de fluxos de trabalho de terceiros. Você pode ajudar a mitigar os riscos associados à reutilização de fluxos de trabalho, seguindo as mesmas práticas recomendadas descritas acima. Para obter mais informações, consulte "[Reutilizando fluxos de trabalho](/actions/learn-github-actions/reusing-workflows)". +{% endif %} + ## Possível impacto de um executor comprometido Essas seções consideram alguns das etapas que um invasor pode dar se for capaz de executar comandos maliciosos em um executor de {% data variables.product.prodname_actions %}. @@ -296,40 +301,40 @@ As tabelas a seguir descrevem os eventos de {% data variables.product.prodname_a | ----------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `enterprise.register_self_hosted_runner` | Acionada quando um novo executor auto-hospedado é registrado. Para obter mais informações, consulte "[Adicionar um executor auto-hospedado a uma empresa](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-enterprise)". | | `enterprise.remove_self_hosted_runner` | Acionada quando um executor auto-hospedado é removido. | -| `enterprise.runner_group_runners_updated` | Triggered when a runner group's member list is 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).{% ifversion fpt or ghes > 3.1 or ghae-issue-1157 %} -| `enterprise.self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." | -| `enterprise.self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %} +| `enterprise.runner_group_runners_updated` | Acionada quando a lista de membros do grupo do executor é 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 ghes > 3.1 or ghae-issue-1157 %} +| `enterprise.self_hosted_runner_online` | Acionada quando o aplicativo do executor é 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)". | +| `enterprise.self_hosted_runner_offline` | Acionada quando o aplicativo do executor é 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 %} | `enterprise.self_hosted_runner_updated` | Acionada quando o executor é atualizado. Pode ser visualizado usando a API REST e a interface do usuário. Este evento não está incluído quando você exportar o log de auditoria como dados JSON ou um arquivo CSV. Para obter mais informações, consulte "[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)" e "[Revisar o log de auditoria para a sua organização](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#exporting-the-audit-log)". | | `org.register_self_hosted_runner` | Acionada quando um novo executor auto-hospedado é 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_self_hosted_runner` | Acionada quando um executor auto-hospedado é 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.runner_group_runners_updated` | Acionada quando a lista de integrantes do grupo de executor é 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)". | -| `org.runner_group_updated` | Acionada quando a configuração de um grupo de executor auto-hospedado é alterada. For more information, see "[Changing the access policy of a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)."{% ifversion fpt or ghes > 3.1 or ghae-issue-1157 %} -| `org.self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." | -| `org.self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %} +| `org.runner_group_updated` | Acionada quando a configuração de um grupo de executor auto-hospedado é alterada. Para obter mais informações, consulte "[Alterar a política de acesso de um grupo de executor auto-hospedado](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)".{% ifversion fpt or ghes > 3.1 or ghae-issue-1157 %} +| `org.self_hosted_runner_online` | Acionada quando o aplicativo do executor é 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` | Acionada quando o aplicativo do executor é 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 %} | `org.self_hosted_runner_updated` | Acionada quando o executor é 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)." | | `repo.register_self_hosted_runner` | Acionada quando um novo executor auto-hospedado é 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` | Acionada quando um executor auto-hospedado é removido. For more information, see "[Removing a runner from a repository](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)."{% ifversion fpt or ghes > 3.1 or ghae-issue-1157 %} -| `repo.self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." | -| `repo.self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %} +| `repo.remove_self_hosted_runner` | Acionada quando um executor auto-hospedado é 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)."{% ifversion fpt or ghes > 3.1 or ghae-issue-1157 %} +| `repo.self_hosted_runner_online` | Acionada quando o aplicativo do executor é 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` | Acionada quando o aplicativo do executor é 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 %} | `repo.self_hosted_runner_updated` | Acionada quando o executor é 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)." | ### Eventos para grupos de executores auto-hospedados -| Ação | Descrição | -| ------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `enterprise.runner_group_created` | Acionada quando um grupo de executores auto-hospedado é criado. Para obter mais informações, consulte "[Criar um grupo de um executor auto-hospedado para uma empresa](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-enterprise)". | -| `enterprise.runner_group_removed` | Acionada quando um grupo de executores auto-hospedados é 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)". | -| `enterprise.runner_group_runner_removed` | Acionada quando a API REST é usada para remover um executor auto-hospedado de um grupo. | -| `enterprise.runner_group_runners_added` | Acionada quando um executor auto-hospedado é adicionado a um grupo. For more information, see "[Moving a self-hosted runner to a group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)."{% ifversion fpt or ghes > 2.22 or ghae %} -| `enterprise.runner_group_updated` | Acionada quando a configuração de um grupo de executor auto-hospedado é alterada. For more information, see "[Changing the access policy of a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)."{% endif %}{% ifversion ghes = 2.22 %} -| `enterprise.runner_group_renamed` | Triggered when the self-hosted runner group is renamed. | -| `enterprise.runner_group_visiblity_updated` | Triggered when the visibility settings of the self-hosted runner group are changed.{% endif %} -| `org.runner_group_created` | Acionada quando um grupo de executores auto-hospedado é 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` | Acionada quando um grupo de executores auto-hospedados é removido. For more information, see "[Removing a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)."{% ifversion fpt or ghes > 2.22 or ghae %} -| `org.runner_group_updated` | Acionada quando a configuração de um grupo de executor auto-hospedado é alterada. For more information, see "[Changing the access policy of a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)."{% endif %} -| `org.runner_group_runners_added` | Acionada quando um executor auto-hospedado é adicionado a um grupo. Para obter mais informações, consulte "[Mover um executorauto-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_runner_removed` | Acionada quando a API REST é usada para remover um executor auto-hospedado de um grupo. For more information, see "[Remove a self-hosted runner from a group for an organization](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)."{% ifversion ghes = 2.22 %} -| `org.runner_group_renamed` | Triggered when the self-hosted runner group is renamed. | -| `org.runner_group_visiblity_updated` | Triggered when the visibility settings of the self-hosted runner group are changed.{% endif %} +| Ação | Descrição | +| ------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `enterprise.runner_group_created` | Acionada quando um grupo de executores auto-hospedado é criado. Para obter mais informações, consulte "[Criar um grupo de um executor auto-hospedado para uma empresa](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-enterprise)". | +| `enterprise.runner_group_removed` | Acionada quando um grupo de executores auto-hospedados é 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)". | +| `enterprise.runner_group_runner_removed` | Acionada quando a API REST é usada para remover um executor auto-hospedado de um grupo. | +| `enterprise.runner_group_runners_added` | Acionada quando um executor auto-hospedado é 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)."{% ifversion fpt or ghes > 2.22 or ghae %} +| `enterprise.runner_group_updated` | Acionada quando a configuração de um grupo de executor auto-hospedado é 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)".{% endif %}{% ifversion ghes = 2.22 %} +| `enterprise.runner_group_renamed` | Acionada quando o grupo do executor auto-hospedado é renomeado. | +| `enterprise.runner_group_visiblity_updated` | Acionada quando as configurações de visibilidade do grupo do executor auto-hospedado são alteradas.{% endif %} +| `org.runner_group_created` | Acionada quando um grupo de executores auto-hospedado é 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` | Acionada quando um grupo de executores auto-hospedados é removido. Para obter mais informações, consulte "[Remover o grupo de um executor auto-hospedado](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)."{% ifversion fpt or ghes > 2.22 or ghae %} +| `org.runner_group_updated` | Acionada quando a configuração de um grupo de executor auto-hospedado é alterada. Para obter mais informações, consulte "[Alterar a política de acesso de um grupo de executor auto-hospedado](/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_runners_added` | Acionada quando um executor auto-hospedado é adicionado a um grupo. Para obter mais informações, consulte "[Mover um executorauto-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_runner_removed` | Acionada quando a API REST é 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)."{% ifversion ghes = 2.22 %} +| `org.runner_group_renamed` | Acionada quando o grupo do executor auto-hospedado é renomeado. | +| `org.runner_group_visiblity_updated` | Acionada quando as configurações de visibilidade do grupo do executor auto-hospedado são alteradas.{% endif %} ### Eventos para atividades no fluxo de trabalho diff --git a/translations/pt-BR/content/actions/using-containerized-services/about-service-containers.md b/translations/pt-BR/content/actions/using-containerized-services/about-service-containers.md index 8f5d715d5b..5086dd9e9f 100644 --- a/translations/pt-BR/content/actions/using-containerized-services/about-service-containers.md +++ b/translations/pt-BR/content/actions/using-containerized-services/about-service-containers.md @@ -18,7 +18,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Sobre os contêineres de serviço diff --git a/translations/pt-BR/content/actions/using-containerized-services/creating-postgresql-service-containers.md b/translations/pt-BR/content/actions/using-containerized-services/creating-postgresql-service-containers.md index 5d89f50fc8..bc8eb723cd 100644 --- a/translations/pt-BR/content/actions/using-containerized-services/creating-postgresql-service-containers.md +++ b/translations/pt-BR/content/actions/using-containerized-services/creating-postgresql-service-containers.md @@ -19,7 +19,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introdução diff --git a/translations/pt-BR/content/actions/using-containerized-services/creating-redis-service-containers.md b/translations/pt-BR/content/actions/using-containerized-services/creating-redis-service-containers.md index 611d78ba43..885d71ecec 100644 --- a/translations/pt-BR/content/actions/using-containerized-services/creating-redis-service-containers.md +++ b/translations/pt-BR/content/actions/using-containerized-services/creating-redis-service-containers.md @@ -19,7 +19,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introdução diff --git a/translations/pt-BR/content/actions/using-containerized-services/index.md b/translations/pt-BR/content/actions/using-containerized-services/index.md index e18f2fb667..0a9edb8786 100644 --- a/translations/pt-BR/content/actions/using-containerized-services/index.md +++ b/translations/pt-BR/content/actions/using-containerized-services/index.md @@ -1,7 +1,7 @@ --- -title: Using containerized services -shortTitle: Containerized services -intro: 'You can use containerized services in your {% data variables.product.prodname_actions %} workflows.' +title: Usando serviços de contêineres +shortTitle: Serviços de contêineres +intro: 'Você pode usar os serviços de cotnêiner nos seus fluxos de trabalho de {% data variables.product.prodname_actions %}.' versions: fpt: '*' ghes: '*' diff --git a/translations/pt-BR/content/actions/using-github-hosted-runners/about-ae-hosted-runners.md b/translations/pt-BR/content/actions/using-github-hosted-runners/about-ae-hosted-runners.md index 0d023fd8c4..62929e9618 100644 --- a/translations/pt-BR/content/actions/using-github-hosted-runners/about-ae-hosted-runners.md +++ b/translations/pt-BR/content/actions/using-github-hosted-runners/about-ae-hosted-runners.md @@ -6,23 +6,16 @@ versions: ghae: '*' --- - - - -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} ## Sobre {% data variables.actions.hosted_runner %}s -Um {% data variables.actions.hosted_runner %} é uma máquina virtual hospedada por {% data variables.product.prodname_dotcom %} com o serviço do executor de {% data variables.product.prodname_actions %} instalado. +Um {% data variables.actions.hosted_runner %} é uma máquina virtual gerenciada por {% data variables.product.prodname_dotcom %} com o serviço de executor de {% data variables.product.prodname_actions %} instalado. {% data variables.actions.hosted_runner %} são dedicados à sua empresa e você pode escolher entre várias opções de hardware e software. Por padrão, {% data variables.actions.hosted_runner %} são totalmente gerenciados e autodimensionados por {% data variables.product.company_short %} para maximizar o desempenho, minimizando os custos.{% ifversion ghae-next %} Opcionalmente, você pode configurar os parâmetros deste autodimensionamento para reduzir ainda mais o seu custo.{% endif %} -{% data variables.product.prodname_ghe_managed %} permite criar e personalizar {% data variables.actions.hosted_runner %}s usando imagens do Ubuntu ou Windows. Você pode selecionar o tamanho da máquina que deseja e configurar redes enrijecidas de segurança para elas. {% data variables.actions.hosted_runner %}s são totalmente gerenciados e dimensionados automaticamente por {% data variables.product.prodname_dotcom %}. +{% data variables.product.prodname_ghe_managed %} permite que você crie e personalize {% data variables.actions.hosted_runner %} usando imagens do Ubuntu ou Windows. Você pode selecionar o tamanho da máquina que quiser e, opcionalmente, configurar um intervalo de IP público fixo para seus {% data variables.actions.hosted_runner %}s. Cada trabalho do fluxo de trabalho é executado em uma nova instância do {% data variables.actions.hosted_runner %} e você poderá executar fluxos de trabalho diretamente na máquina virtual ou em um contêiner do Docker. Todas as etapas da tarefa executada na mesma instância, permitindo que as ações desse trabalho compartilhem informações que usam o sistema de arquivos de {% data variables.actions.hosted_runner %}. -{% note %} -{% data variables.actions.hosted_runner %}s são os únicos executores disponíveis para {% data variables.product.prodname_ghe_managed %} e os executores auto-hospedados não estão disponíveis. -{% endnote %} - Para adicionar {% data variables.actions.hosted_runner %}s à sua organização ou empresa, consulte ["Adicionar {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/adding-ae-hosted-runners)". ## Recomendações de grupo para {% data variables.actions.hosted_runner %}s @@ -35,11 +28,9 @@ Durante o beta de {% data variables.actions.hosted_runner %}, você pode gerenci ## Cobrança -{% data variables.product.prodname_actions %} está atualmente em beta para {% data variables.product.prodname_ghe_managed %}. Durante este período beta, {% data variables.actions.hosted_runner %}s não são faturados e podem ser usados grátis. - Assim que a versão beta terminar, o uso faturado incluirá a atividade completa de instâncias ativas em seus conjuntos de executores hospedados de AE. Isto inclui: - Tempo de trabalho - minutos gastos executando o trabalho de ações. -- Gerenciamento - minutos gastos criando novas imagens de máquinas e tempo ocioso criado como resultado do comportamento da escala automática desejada. +- Gerenciamento - minutos gastos de para recriar as imagens das máquinas{% ifversion ghae-next %} e qualquer tempo ocioso criado como resultado do comportamento do autodimensionamento desejado{% endif %}. A precificação será escalada linearmente com núcleos. Por exemplo, 4 núcleos serão o dobro do preço de 2 núcleos. Os VMs do Windows terão um preço superior aos VMs do Linux. @@ -78,6 +69,14 @@ Para obter uma lista de intervalos de endereços IP que {% data variables.produc A lista de endereços IP de {% data variables.product.prodname_actions %} retornados pela API é atualizada uma vez por semana. +{% ifversion ghae-next %} + +## Autodimensionamento + +Cada conjunto de {% data variables.actions.hosted_runner %}s é totalmente gerenciado por {% data variables.product.company_short %} para maximizar o desempenho e minimizar os custos. Opcionalmente, você pode configurar os parâmetros de autodimensionamento para sua empresa entrando em contato com {% data variables.contact.github_support %}. Você pode definir o número mínimo de executores ociosos e quanto tempo um executor deve permanecer ocioso antes de ser removido do grupo. Cada grupo pode conter até 600 executores. + +{% endif %} + ## Privilégios administrativos para {% data variables.actions.hosted_runner %}s As máquinas virtuais do Linux são executadas, usando `sudo` sem senha. Quando precisar executar comandos ou instalar ferramentas que exigem mais permissões que o usuário atual possui, você pode usar `sudo` sem a necessidade de fornecer uma senha. Para obter mais informações, consulte o "[Manual do Sudo](https://www.sudo.ws/man/1.8.27/sudo.man.html)". diff --git a/translations/pt-BR/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/translations/pt-BR/content/actions/using-github-hosted-runners/about-github-hosted-runners.md index 88e9276f3c..84bb16bdbc 100644 --- a/translations/pt-BR/content/actions/using-github-hosted-runners/about-github-hosted-runners.md +++ b/translations/pt-BR/content/actions/using-github-hosted-runners/about-github-hosted-runners.md @@ -16,6 +16,7 @@ versions: shortTitle: Executores hospedados no GitHub --- +{% data reusables.actions.ae-hosted-runners-beta %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} diff --git a/translations/pt-BR/content/actions/using-github-hosted-runners/adding-ae-hosted-runners.md b/translations/pt-BR/content/actions/using-github-hosted-runners/adding-ae-hosted-runners.md index 2ad944bec6..ecd181bc9b 100644 --- a/translations/pt-BR/content/actions/using-github-hosted-runners/adding-ae-hosted-runners.md +++ b/translations/pt-BR/content/actions/using-github-hosted-runners/adding-ae-hosted-runners.md @@ -5,7 +5,7 @@ versions: ghae: '*' --- -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} {% note %} @@ -19,7 +19,8 @@ versions: Você pode adicionar {% data variables.actions.hosted_runner %}s que usam as imagens básicas do sistema operacional do Azure. Para adicionar {% data variables.actions.hosted_runner %}s à sua organização ou empresa, entre em contato com o suporte de {% data variables.product.prodname_dotcom %} e tenha as seguintes informações prontas: - Sistema operacional necessário: As opções disponíveis estão listadas nas ["Especificações do software](/actions/using-github-hosted-runners/about-ae-hosted-runners#software-specifications)". - - Selecione um nome para cada conjunto de {% data variables.actions.hosted_runner %}s. Estes nomes são criados como etiquetas, que permite que você roteie os seus fluxos de trabalho para esses executores. Para obter mais informações, consulte ["Usar {% data variables.actions.hosted_runner %}s em um fluxo de trabalho](/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow)". + - Selecione um nome para cada conjunto de {% data variables.actions.hosted_runner %}s. Estes nomes são criados como etiquetas, que permite que você roteie os seus fluxos de trabalho para esses executores. Para obter mais informações, consulte ["Usando {% data variables.actions.hosted_runner %}s em um fluxo de trabalho](/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow)."{% ifversion ghae-next %} +{% data reusables.actions.autoscaling-parameters %}{% endif %} - Onde adicionar o {% data variables.actions.hosted_runner %}: Identifique os nomes das organizações e empresas que receberão os executores. ## Adicionar um {% data variables.actions.hosted_runner %} com uma imagem personalizada @@ -33,7 +34,8 @@ Depois de criar uma imagem personalizada usando os passos acima, entre em contat - Nome da imagem. - Versão. - VM SKU para o novo grupo. - - Selecione um nome para cada conjunto de {% data variables.actions.hosted_runner %}s. Estes nomes são criados como etiquetas, que permite que você roteie os seus fluxos de trabalho para esses executores. Para obter mais informações, consulte ["Usar {% data variables.actions.hosted_runner %}s em um fluxo de trabalho](/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow)". + - Selecione um nome para cada conjunto de {% data variables.actions.hosted_runner %}s. Estes nomes são criados como etiquetas, que permite que você roteie os seus fluxos de trabalho para esses executores. Para obter mais informações, consulte ["Usando {% data variables.actions.hosted_runner %}s em um fluxo de trabalho](/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow)."{% ifversion ghae-next %} +{% data reusables.actions.autoscaling-parameters %}{% endif %} - Onde adicionar o {% data variables.actions.hosted_runner %}: Identifique os nomes das organizações e empresas que receberão os executores. ## Revisar seus {% data variables.actions.hosted_runner %}s diff --git a/translations/pt-BR/content/actions/using-github-hosted-runners/creating-custom-images.md b/translations/pt-BR/content/actions/using-github-hosted-runners/creating-custom-images.md index 0f39f5e55b..80b6896e6d 100644 --- a/translations/pt-BR/content/actions/using-github-hosted-runners/creating-custom-images.md +++ b/translations/pt-BR/content/actions/using-github-hosted-runners/creating-custom-images.md @@ -5,7 +5,7 @@ versions: ghae: '*' --- -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} ## Criar um {% data variables.actions.hosted_runner %} com uma imagem personalizada diff --git a/translations/pt-BR/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md b/translations/pt-BR/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md index c1fe573a0b..35bc19abf2 100644 --- a/translations/pt-BR/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md +++ b/translations/pt-BR/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md @@ -11,6 +11,7 @@ topics: shortTitle: Personalize executores --- +{% data reusables.actions.ae-hosted-runners-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} Se você precisar de pacotes de software adicionais em executores hospedados em {% data variables.product.prodname_dotcom %}, você poderá criar um trabalho que instale os pacotes como parte de seu fluxo de trabalho. diff --git a/translations/pt-BR/content/actions/using-github-hosted-runners/index.md b/translations/pt-BR/content/actions/using-github-hosted-runners/index.md index 4b6780f6dd..92dfe3d3d9 100644 --- a/translations/pt-BR/content/actions/using-github-hosted-runners/index.md +++ b/translations/pt-BR/content/actions/using-github-hosted-runners/index.md @@ -17,5 +17,6 @@ children: shortTitle: Usar executores hospedados no GitHub --- +{% data reusables.actions.ae-hosted-runners-beta %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} diff --git a/translations/pt-BR/content/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow.md b/translations/pt-BR/content/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow.md index 123a580dfb..be67400a99 100644 --- a/translations/pt-BR/content/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow.md +++ b/translations/pt-BR/content/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow.md @@ -6,7 +6,7 @@ versions: shortTitle: Usar executores hospedados no AE --- -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} ## Usar {% data variables.actions.hosted_runner %}s em um fluxo de trabalho diff --git a/translations/pt-BR/content/actions/using-github-hosted-runners/using-groups-to-manage-access-to-ae-hosted-runners.md b/translations/pt-BR/content/actions/using-github-hosted-runners/using-groups-to-manage-access-to-ae-hosted-runners.md index 8fd0959e2f..c294ebd2fe 100644 --- a/translations/pt-BR/content/actions/using-github-hosted-runners/using-groups-to-manage-access-to-ae-hosted-runners.md +++ b/translations/pt-BR/content/actions/using-github-hosted-runners/using-groups-to-manage-access-to-ae-hosted-runners.md @@ -6,7 +6,7 @@ versions: shortTitle: Gerenciar grupos de executores do AE --- -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} ## Sobre grupos de {% data variables.actions.hosted_runner %} diff --git a/translations/pt-BR/content/actions/using-github-hosted-runners/using-labels-with-ae-hosted-runners.md b/translations/pt-BR/content/actions/using-github-hosted-runners/using-labels-with-ae-hosted-runners.md index 4de0edf887..09b5b2d040 100644 --- a/translations/pt-BR/content/actions/using-github-hosted-runners/using-labels-with-ae-hosted-runners.md +++ b/translations/pt-BR/content/actions/using-github-hosted-runners/using-labels-with-ae-hosted-runners.md @@ -6,7 +6,7 @@ versions: shortTitle: Etiquetar executores hospedados no AE --- -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} Para informações sobre como usar as etiquetas para etiquetar trabalhos para tipos específicos de {% data variables.actions.hosted_runner %}s, consulte "[Usar {% data variables.actions.hosted_runner %}s em um fluxo de trabalho](/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow)". diff --git a/translations/pt-BR/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md b/translations/pt-BR/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md index 9d6a436606..1f32cb2177 100644 --- a/translations/pt-BR/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md +++ b/translations/pt-BR/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md @@ -29,7 +29,7 @@ Você pode configurar {% data variables.product.prodname_code_scanning %} para e ## Pré-requisitos para {% data variables.product.prodname_code_scanning %} -- A license for {% data variables.product.prodname_GH_advanced_security %}{% ifversion ghes > 3.0 %} (see "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)"){% endif %} +- Uma licença para {% data variables.product.prodname_GH_advanced_security %}{% ifversion ghes > 3.0 %} (consulte "[Sobre cobrança para {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)"){% endif %} - {% data variables.product.prodname_code_scanning_capc %} habilitado no console de gerenciamento (consulte "[Habilitando {% data variables.product.prodname_GH_advanced_security %} para a sua empresa](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)") @@ -62,13 +62,13 @@ Se você configurar a ferramenta de sincronização de ação de {% data variabl {% ifversion ghes = 2.22 %} Para executar {% data variables.product.prodname_code_scanning %} em {% data variables.product.prodname_ghe_server %} com {% data variables.product.prodname_actions %}, as ações apropriadas devem estar disponíveis localmente. Você pode disponibilizar as ações de três maneiras. -- **Recomendado**: Você pode usar [{% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud) para fazer o download automático das ações no {% data variables.product.prodname_dotcom_the_website %}. A máquina que hospeda sua instância deve conseguir acessar {% data variables.product.prodname_dotcom_the_website %}. Esta abordagem garante que você irá obter o software mais recente automaticamente. Para obter mais informações, consulte "[Configurar o {% data variables.product.prodname_github_connect %} para sincronizar com {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)". +- **Recomendado**: Você pode usar [{% data variables.product.prodname_github_connect %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud) para fazer o download automático das ações no {% data variables.product.prodname_dotcom_the_website %}. A máquina que hospeda sua instância deve conseguir acessar {% data variables.product.prodname_dotcom_the_website %}. Esta abordagem garante que você irá obter o software mais recente automaticamente. Para obter mais informações, consulte "[Configurar o {% data variables.product.prodname_github_connect %} para sincronizar com {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)". - Se você desejar usar o {% data variables.product.prodname_codeql_workflow %}, você pode sincronizar o repositório do {% data variables.product.prodname_dotcom_the_website %} ao {% data variables.product.prodname_ghe_server %}, usando a ferramenta de sincronização de Ação do {% data variables.product.prodname_codeql %} disponível em [https://github. om/github/codeql-action-sync-tool](https://github.com/github/codeql-action-sync-tool/). Você pode usar essa ferramenta independentemente se {% data variables.product.product_location %} ou seus executores de {% data variables.product.prodname_actions %} terem acesso à internet, contanto que você possa acessar {% data variables.product.product_location %} e {% data variables.product.prodname_dotcom_the_website %} simultaneamente no seu computador. - É possível criar uma cópia local do repositório de uma ação no servidor, clonando o repositório de {% data variables.product.prodname_dotcom_the_website %} que contém a ação. Por exemplo, se você quiser usar as ações para {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}, você poderá criar um repositório na sua instância denominado `github/codeql-action`. Em seguida, clone o [repositório](https://github.com/github/codeql-action) de {% data variables.product.prodname_dotcom_the_website %} depois faça push desse repositório no repositório `github/codeql-action` da instância. Você também deverá fazer o download de qualquer uma das versões do repositório no {% data variables.product.prodname_dotcom_the_website %} e fazer o upload no repositório `github/codeql-action` de sua instância como versões. {% endif %} ### Configurar {% data variables.product.prodname_github_connect %} para sincronizar {% data variables.product.prodname_actions %} -1. Se você deseja fazer o download dos fluxos de trabalho de ação sob demanda a partir de {% data variables.product.prodname_dotcom_the_website %}, você deverá habilitar o {% data variables.product.prodname_github_connect %}. Para obter mais informações, consulte "[Habilitar {% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud#enabling-github-connect)". +1. Se você deseja fazer o download dos fluxos de trabalho de ação sob demanda a partir de {% data variables.product.prodname_dotcom_the_website %}, você deverá habilitar o {% data variables.product.prodname_github_connect %}. Para obter mais informações, consulte "[Habilitar {% data variables.product.prodname_github_connect %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud#enabling-github-connect)". 2. Você também precisa habilitar o {% data variables.product.prodname_actions %} para {% data variables.product.product_location %}. Para obter mais informações, consulte "[Primeiros passos com {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)". 3. A próxima etapa é configurar o acesso a ações no {% data variables.product.prodname_dotcom_the_website %} usando {% data variables.product.prodname_github_connect %}. Para obter mais informações, consulte "[Habilitar o acesso automático às ações de {% data variables.product.prodname_dotcom_the_website %} usando o {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". 4. Adicione um executor auto-hospedado ao seu repositório, organização ou conta corporativa. Para obter mais informações, consulte "[Adicionando executores auto-hospedados](/actions/hosting-your-own-runners/adding-self-hosted-runners)". diff --git a/translations/pt-BR/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md b/translations/pt-BR/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md index d3830afc78..d1adad8c95 100644 --- a/translations/pt-BR/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md +++ b/translations/pt-BR/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md @@ -27,7 +27,7 @@ topics: - É necessário habilitar o sinalizador de CPU das [SSSE3](https://www.intel.com/content/dam/www/public/us/en/documents/manuals/64-ia-32-architectures-optimization-manual.pdf#G3.1106470) (Extensões SIMD de Streaming Suplementar 3) no VM/KVM que executa {% data variables.product.product_location %}. -- A license for {% data variables.product.prodname_GH_advanced_security %}{% ifversion ghes > 3.0 %} (see "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)"){% endif %} +- Uma licença para {% data variables.product.prodname_GH_advanced_security %}{% ifversion ghes > 3.0 %} (consulte "[Sobre cobrança para {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)"){% endif %} - {% data variables.product.prodname_secret_scanning_caps %} habilitado no console de gerenciamento (consulte "[Habilitando {% data variables.product.prodname_GH_advanced_security %} para a sua empresa](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)") @@ -50,11 +50,11 @@ Se isso não retornar `0`, SSSE3 não está habilitado no seu VM/KVM. Você prec {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} -1. Check if there is {% ifversion ghes < 3.2 %}an **{% data variables.product.prodname_advanced_security %}**{% else %}a **Security**{% endif %} entry in the left sidebar. +1. Verifique se há {% ifversion ghes < 3.2 %}um **{% data variables.product.prodname_advanced_security %}**{% else %}uma entrada de **de segurança**{% endif %} na barra lateral esquerda. {% ifversion ghes < 3.2 %} ![Barra lateral de segurança avançada](/assets/images/enterprise/management-console/sidebar-advanced-security.png) {% else %} - ![Security sidebar](/assets/images/enterprise/3.2/management-console/sidebar-security.png) + ![Barra lateral de segurança](/assets/images/enterprise/3.2/management-console/sidebar-security.png) {% endif %} {% data reusables.enterprise_management_console.advanced-security-license %} @@ -66,7 +66,7 @@ Se isso não retornar `0`, SSSE3 não está habilitado no seu VM/KVM. Você prec {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.advanced-security-tab %} -1. Under "{% ifversion ghes < 3.2 %}{% data variables.product.prodname_advanced_security %}{% else %}Security{% endif %}," click **{% data variables.product.prodname_secret_scanning_caps %}**. ![Caixa de seleção para habilitar ou desabilitar {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/enable-secret-scanning-checkbox.png) +1. Em "{% ifversion ghes < 3.2 %}{% data variables.product.prodname_advanced_security %}{% else %}Segurança{% endif %}", clique em **{% data variables.product.prodname_secret_scanning_caps %}**. ![Caixa de seleção para habilitar ou desabilitar {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/enable-secret-scanning-checkbox.png) {% data reusables.enterprise_management_console.save-settings %} ## Desabilitar {% data variables.product.prodname_secret_scanning %} @@ -76,5 +76,5 @@ Se isso não retornar `0`, SSSE3 não está habilitado no seu VM/KVM. Você prec {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.advanced-security-tab %} -1. Under "{% ifversion ghes < 3.2 %}{% data variables.product.prodname_advanced_security %}{% else %}Security{% endif %}," unselect **{% data variables.product.prodname_secret_scanning_caps %}**. ![Caixa de seleção para habilitar ou desabilitar {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/secret-scanning-disable.png) +1. Em "{% ifversion ghes < 3.2 %}{% data variables.product.prodname_advanced_security %}{% else %}Segurança{% endif %}", desmarque **{% data variables.product.prodname_secret_scanning_caps %}**. ![Caixa de seleção para habilitar ou desabilitar {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/secret-scanning-disable.png) {% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/pt-BR/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md b/translations/pt-BR/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md index e9da81357c..888086fe3b 100644 --- a/translations/pt-BR/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md @@ -26,14 +26,14 @@ Ao habilitar {% data variables.product.prodname_GH_advanced_security %} para a s ## Pré-requisitos para habilitar {% data variables.product.prodname_GH_advanced_security %} -1. Upgrade your license for {% data variables.product.product_name %} to include {% data variables.product.prodname_GH_advanced_security %}.{% ifversion ghes > 3.0 %} For information about licensing, see "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)."{% endif %} -2. Download the new license file. For more information, see "[Downloading your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)." -3. Upload the new license file to {% data variables.product.product_location %}. For more information, see "[Uploading a new license to {% data variables.product.prodname_ghe_server %}](/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)."{% ifversion ghes > 2.22 %} +1. Atualize a sua licença para {% data variables.product.product_name %} para incluir {% data variables.product.prodname_GH_advanced_security %}.{% ifversion ghes > 3.0 %} Para obter informações sobre a licença, consulte "[Sobre cobrança para {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)."{% endif %} +2. Faça o download do novo arquivo de licença. Para obter mais informações, consulte "[Fazer o download da sua licença para {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)". +3. Faça o upload do novo arquivo de licença para {% data variables.product.product_location %}. Para obter mais informações, consulte "[Fazer o upload de uma nova licença para {% data variables.product.prodname_ghe_server %}](/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)".{% ifversion ghes > 2.22 %} 4. Revise os pré-requisitos para as funcionalidades que você pretende habilitar. - {% data variables.product.prodname_code_scanning_capc %}, consulte "[Configurando {% data variables.product.prodname_code_scanning %} para seu dispositivo](/admin/advanced-security/configuring-code-scanning-for-your-appliance#prerequisites-for-code-scanning)." - {% data variables.product.prodname_secret_scanning_caps %}, consulte "[Configurando {% data variables.product.prodname_secret_scanning %} para seu dispositivo](/admin/advanced-security/configuring-secret-scanning-for-your-appliance#prerequisites-for-secret-scanning)."{% endif %} - - {% data variables.product.prodname_dependabot %}, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)." + - {% data variables.product.prodname_dependabot %}, consulte "[Habilitar alertas para dependências vulneráveis em {% data variables.product.prodname_ghe_server %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)". ## Verificando se a sua licença inclui {% data variables.product.prodname_GH_advanced_security %} @@ -59,50 +59,57 @@ Ao habilitar {% data variables.product.prodname_GH_advanced_security %} para a s {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.advanced-security-tab %}{% ifversion ghes > 2.22 %} -1. Under "{% ifversion ghes < 3.2 %}{% data variables.product.prodname_advanced_security %}{% else %}Security{% endif %}," select the features that you want to enable and deselect any features you want to disable. ![Checkbox to enable or disable {% data variables.product.prodname_advanced_security %} features](/assets/images/enterprise/management-console/enable-advanced-security-checkboxes.png){% else %} +1. Em "{% ifversion ghes < 3.2 %}{% data variables.product.prodname_advanced_security %}{% else %}Security{% endif %}", selecione as funcionalidades que você deseja habilitar e desmarque todos os recursos que deseja desabilitar. ![Checkbox to enable or disable {% data variables.product.prodname_advanced_security %} features](/assets/images/enterprise/management-console/enable-advanced-security-checkboxes.png){% else %} 1. Em "{% data variables.product.prodname_advanced_security %}," clique em **{% data variables.product.prodname_code_scanning_capc %}**. ![Checkbox to enable or disable {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/management-console/enable-code-scanning-checkbox.png){% endif %} {% data reusables.enterprise_management_console.save-settings %} Quando {% data variables.product.product_name %} terminar de reiniciar, você estará pronto para definir todas as funcionalidades adicionais necessárias para recursos recém-habilitados. Para obter mais informações, consulte "[Configurar o {% data variables.product.prodname_code_scanning %} para seu aplicativo ](/admin/advanced-security/configuring-code-scanning-for-your-appliance)". -## Enabling or disabling {% data variables.product.prodname_GH_advanced_security %} features via the administrative shell (SSH) +## Habilitar ou desabilitar as funcionalidades de {% data variables.product.prodname_GH_advanced_security %} por meio do shell administrativo (SSH) Você pode habilitar ou desabilitar as funcionalidades programaticamente em {% data variables.product.product_location %}. Para mais informações sobre o shell administrativo e os utilitários da linha de comando para {% data variables.product.prodname_ghe_server %}, consulte "[Acessar o shell administrativo (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" e "[Utilitários de linha de comando](/admin/configuration/command-line-utilities#ghe-config)". -For example, you can enable any {% data variables.product.prodname_GH_advanced_security %} feature with your infrastructure-as-code tooling when you deploy an instance for staging or disaster recovery. +Por exemplo, você pode habilitar qualquer recurso de {% data variables.product.prodname_GH_advanced_security %} com as suas ferramentas de código de infraestrutura ao implantar uma instância para preparação ou recuperação de desastres. 1. SSH em {% data variables.product.product_location %}. -1. Enable features for {% data variables.product.prodname_GH_advanced_security %}. +1. Habilitar funcionalidades para {% data variables.product.prodname_GH_advanced_security %}. - - To enable {% data variables.product.prodname_code_scanning_capc %}, enter the following commands. + - Para habilitar {% data variables.product.prodname_code_scanning_capc %}, digite os comandos a seguir. ```shell ghe-config app.minio.enabled true ghe-config app.code-scanning.enabled true ``` - - To enable {% data variables.product.prodname_secret_scanning_caps %}, enter the following command. + - Para habilitar {% data variables.product.prodname_secret_scanning_caps %}, digite o comando a seguir. ```shell ghe-config app.secret-scanning.enabled true ``` - - To enable {% data variables.product.prodname_dependabot %}, enter the following command. - ```shell - {% ifversion ghes > 3.1 %}ghe-config app.dependency-graph.enabled true{% else %}ghe-config app.github.dependency-graph-enabled true{% endif %} + - Para habilitar {% data variables.product.prodname_dependabot %}, digite os comandos a seguir {% ifversion ghes > 3.1 %}{% else %}comandos{% endif %}. + {% ifversion ghes > 3.1 %}```shell + ghe-config app.dependency-graph.enabled true ``` -2. Optionally, disable features for {% data variables.product.prodname_GH_advanced_security %}. + {% else %}```shell + ghe-config app.github.dependency-graph-enabled true + ghe-config app.github.vulnerability-alerting-and-settings-enabled true + ```{% endif %} +2. Opcionalmente, desabilite as funcionalidades para {% data variables.product.prodname_GH_advanced_security %}. - - To disable {% data variables.product.prodname_code_scanning %}, enter the following commands. + - Para desabilitar {% data variables.product.prodname_code_scanning %}, digite os seguintes comandos. ```shell ghe-config app.minio.enabled false ghe-config app.code-scanning.enabled false ``` - - To disable {% data variables.product.prodname_secret_scanning %}, enter the following command. + - Para desabilitar {% data variables.product.prodname_secret_scanning %}, digite o seguinte comando. ```shell ghe-config app.secret-scanning.enabled false ``` - - To disable {% data variables.product.prodname_dependabot %}, enter the following command. - ```shell - {% ifversion ghes > 3.1 %}ghe-config app.dependency-graph.enabled false{% else %}ghe-config app.github.dependency-graph-enabled false{% endif %} + - Para desabilitar {% data variables.product.prodname_dependabot %}, digite os comandos a seguir {% ifversion ghes > 3.1 %}{% else %}comandos{% endif %}. + {% ifversion ghes > 3.1 %}```shell + ghe-config app.dependency-graph.enabled false ``` - + {% else %}```shell + ghe-config app.github.dependency-graph-enabled false + ghe-config app.github.vulnerability-alerting-and-settings-enabled false + ```{% endif %} 3. Aplique a configuração. ```shell ghe-config-apply diff --git a/translations/pt-BR/content/admin/advanced-security/viewing-your-github-advanced-security-usage.md b/translations/pt-BR/content/admin/advanced-security/viewing-your-github-advanced-security-usage.md index 731b51e774..b69bcc7fdd 100644 --- a/translations/pt-BR/content/admin/advanced-security/viewing-your-github-advanced-security-usage.md +++ b/translations/pt-BR/content/admin/advanced-security/viewing-your-github-advanced-security-usage.md @@ -10,7 +10,7 @@ topics: shortTitle: Visualizar o uso avançado de segurança --- -## About licenses for {% data variables.product.prodname_GH_advanced_security %} +## Sobre as licenças para {% data variables.product.prodname_GH_advanced_security %} {% data reusables.advanced-security.about-ghas-license-seats %} Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)". diff --git a/translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/allowing-built-in-authentication-for-users-outside-your-identity-provider.md b/translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/allowing-built-in-authentication-for-users-outside-your-identity-provider.md index 631b377316..68611bb123 100644 --- a/translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/allowing-built-in-authentication-for-users-outside-your-identity-provider.md +++ b/translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/allowing-built-in-authentication-for-users-outside-your-identity-provider.md @@ -13,7 +13,7 @@ topics: - Authentication - Enterprise - Identity -shortTitle: Authentication outside IdP +shortTitle: Autenticação fora do IdP --- ## Sobre a autenticação integrada para usuários de fora do provedor de identidade diff --git a/translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-built-in-authentication.md b/translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-built-in-authentication.md index 56365a2923..bb334278d6 100644 --- a/translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-built-in-authentication.md +++ b/translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-built-in-authentication.md @@ -28,14 +28,14 @@ Você pode criar mensagens personalizadas que os usuários verão nas páginas d {% data reusables.enterprise_user_management.two_factor_auth_header %} {% data reusables.enterprise_user_management.2fa_is_available %} -## Creating your account +## Criando a sua conta -Once your instance has been created, you'll need to create your own admin account. +Uma vez que sua instância foi criada, você deverá criar a sua própria conta de administrador. 1. Na página "Create Admin Account" (Criar conta de administrador) em `http(s)://[hostname]/join`, defina seu nome de usuário, senha e endereço de e-mail. Em seguida, clique em **Create an account** (Criar conta). ![Criar conta de administrador](/assets/images/enterprise/site-admin-settings/create-first-admin-acct.png) {% data reusables.enterprise_site_admin_settings.sign-in %} -## Inviting users +## Convidar usuários {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.invite-user-sidebar-tab %} @@ -43,10 +43,10 @@ Once your instance has been created, you'll need to create your own admin accoun {% tip %} -**Tip:** If email for notifications is configured on the appliance, an invite will also be sent to the provided email address. +**Dica:** Se o e-mail para notificações estiver configurado no dispostivo, um convite também será enviado para o endereço de e-mail fornecido. {% endtip %} ## Leia mais -- "[Configuring email for notifications](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications)" +- "[Configurar e-mail para notificações](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications)" diff --git a/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md b/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md index 7bc75c2c54..1b60876b5c 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md +++ b/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md @@ -17,24 +17,24 @@ topics: shortTitle: Configurar um proxy de saída --- -## About proxies with {% data variables.product.product_name %} +## Sobre proxies com {% data variables.product.product_name %} Quando houver um servidor proxy habilitado para a {% data variables.product.product_location %}, as mensagens de saída enviadas para o {% data variables.product.prodname_ghe_server %} sairão primeiramente pelo servidor proxy, a menos que o host de destino seja adicionado como exclusão de proxy HTTP. Os tipos de mensagens de saída incluem webhooks de saída, pacotes para upload e fetch de avatares herdados. A URL do servidor proxy é o protocolo, domínio ou endereço IP e o número da porta, por exemplo: `http://127.0.0.1:8123`. {% note %} -**Observação:** para conectar a {% data variables.product.product_location %} ao {% data variables.product.prodname_dotcom_the_website %}, a sua configuração de proxy deve permitir conectividade com `github.com` e `api.github.com`. Para obter mais informações, consulte "[Conectar o {% data variables.product.prodname_ghe_server %} ao {% data variables.product.prodname_dotcom_the_website %}](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/connecting-github-enterprise-server-to-github-com)". +**Observação:** para conectar a {% data variables.product.product_location %} ao {% data variables.product.prodname_dotcom_the_website %}, a sua configuração de proxy deve permitir conectividade com `github.com` e `api.github.com`. Para obter mais informações, consulte "[Conectando sua conta corporativa a {% data variables.product.prodname_dotcom_the_website %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)". {% endnote %} -{% data reusables.actions.proxy-considerations %} For more information about using {% data variables.product.prodname_actions %} with {% data variables.product.prodname_ghe_server %}, 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)." +{% data reusables.actions.proxy-considerations %} Para obter mais informações sobre como usar {% data variables.product.prodname_actions %} com {% data variables.product.prodname_ghe_server %}, consulte "[Primeiros passos com {% data variables.product.prodname_actions %} para {% 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)". ## Configurar servidor proxy web de saída {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.privacy %} -4. Em **HTTP Proxy Server** (Servidor proxy HTTP), digite a URL do seu servidor proxy. ![Campo para digitar a URL do servidor proxy HTTP](/assets/images/enterprise/management-console/http-proxy-field.png) +1. Em **HTTP Proxy Server** (Servidor proxy HTTP), digite a URL do seu servidor proxy. ![Campo para digitar a URL do servidor proxy HTTP](/assets/images/enterprise/management-console/http-proxy-field.png) 5. Você também pode ir até **HTTP Proxy Exclusion** (Exclusão de proxy HTTP) e digitar qualquer host que não exija acesso por proxy, separando os hosts por vírgulas. Para excluir todos os hosts de um domínio que exige acesso ao proxy, você pode usar `.` como um prefixo curinga. Por exemplo: `octo-org.tentacle` ![Campo para digitar qualquer exclusão de proxy HTTP](/assets/images/enterprise/management-console/http-proxy-exclusion-field.png) diff --git a/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md b/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md index e1e7abb99f..63228d9211 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md +++ b/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md @@ -36,7 +36,7 @@ Os servidores de nomes que você especificar devem resolver o nome de host da {% ``` 3. Adicione quaisquer entradas `nameserver` e salve o arquivo. 4. Depois de verificar suas alterações, salve o arquivo. -5. To add your new nameserver entries to {% data variables.product.product_location %}, run the following: +5. Para adicionar as suas novas entradas de nameserver para {% data variables.product.product_location %}, execute o seguinte: ```shell $ sudo service resolvconf restart $ sudo service dnsmasq restart diff --git a/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-tls.md b/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-tls.md index 5c06283331..f30f796417 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-tls.md +++ b/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-tls.md @@ -75,5 +75,5 @@ Você também pode usar o utilitário de linha de comando `ghe-ssl-acme` na {% d {% data reusables.enterprise_management_console.save-settings %} {% data reusables.enterprise_management_console.privacy %} 7. Clique em **Request TLS certificate** (Solicitar certificado TSL). ![Botão Request TLS certificate (Solicitar certificado TSL)](/assets/images/enterprise/management-console/request-tls-button.png) -8. Wait for the "Status" to change from "STARTED" to "DONE". ![Let's Encrypt status](/assets/images/enterprise/management-console/lets-encrypt-status.png) +8. Espere o "Status" mudar de "INICIADO" para "Concluído". ![Status Let's Encrypt](/assets/images/enterprise/management-console/lets-encrypt-status.png) 9. Clique em **Save configuration** (Salvar configuração). diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md index 428f72ff83..0013d30c0c 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md +++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md @@ -35,7 +35,7 @@ Para acessar o {% data variables.enterprise.management_console %}, você deve us ## Acessar o {% data variables.enterprise.management_console %} como administrador do site -A primeira vez que você acessar o {% data variables.enterprise.management_console %} como administrador do site, você deve enviar seu arquivo de licença do {% data variables.product.prodname_enterprise %} para efetuar a autenticação no aplicativo. For more information, see "[Managing your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise)." +A primeira vez que você acessar o {% data variables.enterprise.management_console %} como administrador do site, você deve enviar seu arquivo de licença do {% data variables.product.prodname_enterprise %} para efetuar a autenticação no aplicativo. Para obter mais informações, consulte "[Gerenciar a sua licença para {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise)." {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} 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 8093bc161d..8446d5438c 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 @@ -44,14 +44,14 @@ $ ghe-announce -u Este utilitário exibe informações sobre trabalhos em segundo plano, ativos e em fila. Ele fornece os mesmos números de contagem de trabalhos que a barra de estatísticas de administração, na parte superior de todas as páginas. -This utility can help identify whether the Aqueduct server is having problems processing background jobs. Any of the following scenarios might be indicative of a problem with Aqueduct: +Este utilitário pode ajudar a identificar se o servidor de Aqueduct está tendo problemas no processamento de trabalhos em segundo plano. Qualquer dos seguintes cenários pode indicar um problema com o Aqueduct: * O número de trabalhos em segundo plano está aumentando, e os trabalhos ativos continuam iguais. * Os feeds de evento não estão sendo atualizados. * Webhooks não estão sendo acionados. * A interface web não atualiza após um push do Git. -If you suspect Aqueduct is failing, contact {% data variables.contact.contact_ent_support %} for help. +Se você suspeitar que o Aqueduct tem uma falha, entre em contato com {% data variables.contact.contact_ent_support %} para obter ajuda. Com este comando, também é possível pausar ou retomar trabalhos na fila. @@ -351,18 +351,6 @@ stop/waiting - ghe-replica-mode ``` -{% tip %} - -Os nomes de serviço retornados deste comando podem ser usados com comandos "[`systemctl`](https://www.freedesktop.org/software/systemd/man/systemctl.html)" para interromper, iniciar ou reiniciar esses serviços manualmente, se necessário. Por exemplo: - -```shell -$ sudo systemctl restart github-resqued -``` - -A interrupção dos serviços causará tempo de inatividade na instalação. Portanto, é recomendável entrar em contato com o {% data variables.contact.contact_ent_support %} antes de parar ou reiniciar qualquer serviço. - -{% endtip %} - ### ghe-set-password Com `ghe-set-password`, você pode definir uma nova senha para autenticação no [{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-management-console). @@ -808,7 +796,7 @@ $ ssh -p 122 admin@hostname -- 'ghe-update-check' ### ghe-license-usage -Este utilitário exporta uma lista de usuários da instalação em formato JSON. Se sua instância estiver conectada ao {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %} usa essa informação para reportar informações de licenciamento ao {% data variables.product.prodname_ghe_cloud %}. Para obter mais informações, consulte "[Conctando {% data variables.product.prodname_ghe_server %} ao {% data variables.product.prodname_ghe_cloud %}](/enterprise/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)". +Este utilitário exporta uma lista de usuários da instalação em formato JSON. Se sua instância estiver conectada ao {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %} usa essa informação para reportar informações de licenciamento ao {% data variables.product.prodname_ghe_cloud %}. Para obter mais informações, consulte "[Conectando a sua conta corporativa a {% data variables.product.prodname_ghe_cloud %} ](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)". Por padrão, a lista de usuários no arquivo JSON resultante é criptografada. Use o sinalizador `-h` para ver mais opções. diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md index f9dddfd5cc..7956d888bf 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md +++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md @@ -68,7 +68,7 @@ Podem ser necessários mais recursos dependendo do uso, como atividade do usuár {% note %} - **Note:** If your {% data variables.product.product_location %} is deployed as a cluster or in a high availability configuration using a load balancer, the `GHE_HOSTNAME` can be the load balancer hostname, as long as it allows SSH access (on port 122) to {% data variables.product.product_location %}. + **Observação:** Se o seu {% data variables.product.product_location %} for implantado como um cluster ou em uma configuração de alta disponibilidade usando um balanceador de carga, o `GHE_HOSTNAME` poderá ser o nome de host do balanceador da carga, desde que permita o acesso SSH (na porta 122) a {% data variables.product.product_location %}. {% endnote %} @@ -105,9 +105,9 @@ Em caso de interrupção prolongada ou evento catastrófico no site primário, {% note %} -**Note:** When performing backup restores to {% data variables.product.product_location %}, the same version supportability rules apply. You can only restore data from at most two feature releases behind. +**Observação:** Ao executar backup para {% data variables.product.product_location %}, aplicam-se as mesmas regras de suporte de versão. Você só pode restaurar dados de no máximo duas versões do recursos para trás. -For example, if you take a backup from GHES 3.0.x, you can restore it into a GHES 3.2.x instance. But, you cannot restore data from a backup of GHES 2.22.x onto 3.2.x, because that would be three jumps between versions (2.22 > 3.0 > 3.1 > 3.2). You would first need to restore onto a 3.1.x instance, and then upgrade to 3.2.x. +Por exemplo, se você receber um backup do GHES 3.0.x, você poderá restaurá-lo em uma instância GHES 3.2.x. No entanto, você não poderá restaurar dados de um backup do GHES 2.22.x para 3.2., porque seriam três saltos entre as versões (2.22 > 3.0 > 3.1 > 3.2). Primeiro, você deverá restaurar em uma instância de 3.1.x e, em seguida, atualizar para 3.2.x. {% endnote %} diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md index a6f22164dd..ed9ee19b6c 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md +++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md @@ -30,18 +30,18 @@ Habilitar limites de taxa na {{ site.data.variables.product.prodname_enterprise_ {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} -2. Under "Rate Limiting", select **Enable HTTP API Rate Limiting**. ![Caixa de seleção para habilitar limite de taxas de API](/assets/images/enterprise/management-console/api-rate-limits-checkbox.png) +2. Em "Limitede taxa", selecione **Habilitar limite de taxa para a API HTTP**. ![Caixa de seleção para habilitar limite de taxas de API](/assets/images/enterprise/management-console/api-rate-limits-checkbox.png) 3. Informe os limites para solicitações autenticadas e não autenticadas de cada API ou aceite os limites padrão sugeridos. {% data reusables.enterprise_management_console.save-settings %} -## Enabling secondary rate limits +## Habilitar limites de taxa secundária -Setting secondary rate limits protects the overall level of service on {% data variables.product.product_location %}. +A configuração dos limites de taxa secundária protege o nível geral do serviço em {% data variables.product.product_location %}. {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% ifversion ghes > 3.1 %} -2. Under "Rate Limiting", select **Enable Secondary Rate Limiting**. ![Checkbox for enabling secondary rate limiting](/assets/images/enterprise/management-console/secondary-rate-limits-checkbox.png) +2. Em "Limite de taxa", selecione **Habilitar taxa de limite secundária**. ![Caixa de seleção para habilitar o limite de taxa secundária](/assets/images/enterprise/management-console/secondary-rate-limits-checkbox.png) {% else %} 2. Em "Limites de taxa", selecione **Enable Abuse Rate Limiting** (Habilitar limite de taxa de abuso). ![Caixa de seleção para habilitar limite de taxas de abuso](/assets/images/enterprise/management-console/abuse-rate-limits-checkbox.png) {% endif %} diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md index 0bdaaa6ba8..92cd0abaa0 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md @@ -1,7 +1,7 @@ --- -title: Configuring the referrer policy for your enterprise -shortTitle: Configure referrer policy -intro: 'You can increase the privacy of {% data variables.product.product_location %} by configuring the policy for cross-origin requests.' +title: Configurar a política de indicação para a sua empresa +shortTitle: Configurar a política de indicação +intro: 'Você pode aumentar a privacidade do {% data variables.product.product_location %} configurando a política para solicitações de origem cruzada.' versions: ghes: '>=3.2' type: how_to @@ -12,25 +12,25 @@ topics: - Security --- -## About the referrer policy for your enterprise +## Sobre a política de indicação para a sua empresa -The referrer policy controls the information that {% data variables.product.product_name %} transmits in HTTP headers when someone visits a link from {% data variables.product.product_location %} to an external site. +A política de referência controla a informação que {% data variables.product.product_name %} transmite em cabeçalhos HTTP quando alguém visita um link de {% data variables.product.product_location %} para um site externo. -By default, when a user on {% data variables.product.product_location %} visits a link to another site from a file or comment on your instance, the request includes the hostname for your instance in plain text within the `Referer` header. If the link leads to an external website, the owner of the website could read the hostname for your instance in requests or log files. +Por padrão, quando um usuário em {% data variables.product.product_location %} acessa um link para outro site a partir de um arquivo ou comentário na sua instância, a solicitação inclui o nome do host para sua instância em texto simples dentro do cabeçalho `Referer`. Se o link levar a um site externo, o proprietário do site poderá ler o nome de host da sua instância em solicitações ou arquivos de registro. -You can control the information that {% data variables.product.product_name %} sends when a user visits a link from your instance. +Você pode controlar as informações que {% data variables.product.product_name %} envia quando um usuário acessa um link da sua instância. -## Enabling the `same-origin` referrer policy +## Habilitar a política de indicação de `same-origin` -You can enable the `same-origin` referrer policy to instruct modern browsers to exclude the hostname for {% data variables.product.product_location %} from requests to external websites. The setting applies to all links from the web interface on your instance. By default, {% data variables.product.product_name %} uses the `origin-when-cross-origin` and `strict-origin-when-cross-origin` referrer policies, which means your instance's hostname will appear in HTTP and HTTPS requests to external websites. +Você pode habilitar a política de indicação de `same-origin` para orientar navegadores modernos para excluir o nome de host de {% data variables.product.product_location %} de solicitações para sites externos. A configuração aplica-se a todos os links da interface web na sua instância. Por padrão, {% data variables.product.product_name %} usa as políticas de indicação `origin-when-cross-origin` e `strict-origin-when-cross-origin`, o que significa que o nome de host da sua instância irá aparecer em solicitações HTTP e HTTPS para sites externos. {% note %} -**Note**: Changing the referrer policy to `same-origin` can affect external sites that expect a hostname in the HTTP headers for a request. +**Observação**: Mudar a política de referência para `same-origin` pode afetar sites externos que esperam um nome de host nos cabeçalhos HTTP para uma solicitação. {% endnote %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} -1. Under "User Agent Referrer Policy", select **Enable same origin referrer policy for all organizations**. ![Checkbox for enabling same origin referrer policy](/assets/images/enterprise/settings/referrer-policy-checkbox.png) -1. Clique em **Salvar**. ![Save button for enabling same origin referrer policy](/assets/images/enterprise/settings/referrer-policy-save-button.png) +1. Em "Política do Agente Indicador do Usuário", selecione **Habilitar a mesma política de indicação de origem para todas as organizações**. ![Caixa de seleção para habilitar a mesma política de indicação de origem](/assets/images/enterprise/settings/referrer-policy-checkbox.png) +1. Clique em **Salvar**. ![Botão salvar para habilitar a mesma política de indicação de origem](/assets/images/enterprise/settings/referrer-policy-save-button.png) diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md index 62c4623eb0..d414f97e3a 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md +++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md @@ -14,7 +14,7 @@ redirect_from: Antes de inicializar sua empresa, você deve comprar {% data variables.product.product_name %}. Para mais informações, entre em contato com {% data variables.contact.contact_enterprise_sales %}. -{% data reusables.github-ae.initialize-enterprise %} Make sure the information you provide matches the intended enterprise owner's information in the IdP. Para obter mais informações sobre os proprietários corporativos, consulte "[Funções em uma empresa](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise#enterprise-owner)". +{% data reusables.github-ae.initialize-enterprise %} Certifique-se de que as informações fornecidas correspondem às informações do proprietário corporativo desejado no IdP. Para obter mais informações sobre os proprietários corporativos, consulte "[Funções em uma empresa](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise#enterprise-owner)". {% note %} diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md index 6a3a1cdba8..b0b0748a9d 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md +++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md @@ -165,19 +165,19 @@ Esta categoria controla a forma como o índice [Problemas][] é reparado. Você - iniciar um novo trabalho de reparo de índice; - redefinir o estado de todo o reparo de índice. {% endif %} -## Reserved logins +## Logins reservados -Certain words are reserved for internal use in {% data variables.product.product_location %}, which means that these words cannot be used as usernames. +Certas palavras são reservadas para uso interno em {% data variables.product.product_location %}, o que significa que essas palavras não podem ser usadas como nomes de usuário. -For example, the following words are reserved, among others: +Por exemplo, as palavras a seguir são reservadas, entre outras: - `administrador` - `enterprise` - `login` -- `staff` +- `equipe` - `suporte` -For the full list or reserved words, navigate to "Reserved logins" in the site admin dashboard. +Para a lista completa ou palavras reservadas, acesse "Logins reservados" no painel de administração do site. {% ifversion ghes or ghae %} @@ -197,7 +197,7 @@ Este espaço lista os repositórios da {% data variables.product.product_locatio ## Todos os usuários -Here you can see all of the users on {% data variables.product.product_location %}, and [initiate an SSH key audit](/enterprise/{{ currentVersion }}/admin/guides/user-management/auditing-ssh-keys). +Aqui você pode ver todos os usuários em {% data variables.product.product_location %}, e [iniciar uma auditoria de chave SSH](/enterprise/{{ currentVersion }}/admin/guides/user-management/auditing-ssh-keys). ## Administradores do site @@ -208,7 +208,7 @@ Aqui você verá todos os administradores da {% data variables.product.product_l Aqui você pode ver e [suspender](/enterprise/{{ currentVersion }}/admin/guides/user-management/suspending-and-unsuspending-users) todos os usuários inativos da {% data variables.product.product_location %}. Uma conta de usuário é considerada inativa quando: {% endif %} {% ifversion ghae %} -Here you can see and suspend all of the inactive users on {% data variables.product.product_location %}. Uma conta de usuário é considerada inativa quando: +Aqui você pode ver e suspender todos os usuários inativos em {% data variables.product.product_location %}. Uma conta de usuário é considerada inativa quando: {% endif %} - Seu tempo de existência supera o limite de inatividade configurado na {% data variables.product.product_location %}; diff --git a/translations/pt-BR/content/admin/configuration/index.md b/translations/pt-BR/content/admin/configuration/index.md index 716aea236a..77a4f5fbdd 100644 --- a/translations/pt-BR/content/admin/configuration/index.md +++ b/translations/pt-BR/content/admin/configuration/index.md @@ -12,7 +12,7 @@ topics: children: - /configuring-your-enterprise - /configuring-network-settings - - /managing-connections-between-github-enterprise-server-and-github-enterprise-cloud + - /managing-connections-between-your-enterprise-accounts --- {% ifversion ghes %} diff --git a/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md b/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md new file mode 100644 index 0000000000..fcf9a7c017 --- /dev/null +++ b/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md @@ -0,0 +1,83 @@ +--- +title: Conectar a sua conta corporativa ao GitHub Enterprise Cloud +shortTitle: Conectar as contas corporativas +intro: 'Ao habilitar o {% data variables.product.prodname_github_connect %}, você poderá compartilhar recursos e fluxos de trabalho específicos entre a {% data variables.product.product_location %} e o {% data variables.product.prodname_ghe_cloud %}.' +redirect_from: + - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-to-github-com/ + - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-server-to-github-com + - /enterprise/admin/developer-workflow/connecting-github-enterprise-server-to-githubcom/ + - /enterprise/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud + - /enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud + - /admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud +permissions: 'Enterprise owners who are also owners of a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable {% data variables.product.prodname_github_connect %}.' +versions: + ghes: '*' + ghae: next +type: how_to +topics: + - Enterprise + - GitHub Connect + - Infrastructure + - Networking +--- + +{% data reusables.github-connect.beta %} + +## Sobre o {% data variables.product.prodname_github_connect %} + +Para habilitar o {% data variables.product.prodname_github_connect %}, você deve configurar a conexão na {% data variables.product.product_location %} e na sua organização do {% data variables.product.prodname_ghe_cloud %} ou na conta corporativa. + +{% ifversion ghes %} +Para configurar uma conexão, sua configuração de proxy deve permitir conectividade com o `github.com` e o `api.github.com`. Para obter mais informações, consulte "[Configurar servidor proxy web de saída](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-an-outbound-web-proxy-server)". +{% endif %} + +Após habilitar o {% data variables.product.prodname_github_connect %}, você poderá ativar recursos como a pesquisa unificada e as contribuições unificadas. Para obter mais informações sobre todas as funcionalidades disponíveis, consulte "[Gerenciando conexões entre as suas contas corporativas](/admin/configuration/managing-connections-between-your-enterprise-accounts)". + +Ao conectar a {% data variables.product.product_location %} ao {% data variables.product.prodname_ghe_cloud %}, um registro no {% data variables.product.prodname_dotcom_the_website %} armazena as informações sobre a conexão: +{% ifversion ghes %} +- A parte da chave pública da sua licença do {% data variables.product.prodname_ghe_server %}; +- Um hash da sua licença do {% data variables.product.prodname_ghe_server %}; +- O nome do cliente da sua licença do {% data variables.product.prodname_ghe_server %}; +- A versão de {% data variables.product.product_location_enterprise %}{% endif %} +- O nome do host da sua instância de {% data variables.product.product_name %} +- A conta da organização ou empresa em {% data variables.product.prodname_dotcom_the_website %} que estiver conectada a {% data variables.product.product_location %} +- O token de autenticação usado pela {% data variables.product.product_location %} para fazer solicitações ao {% data variables.product.prodname_dotcom_the_website %}. + +Habilitar o {% data variables.product.prodname_github_connect %} também cria um {% data variables.product.prodname_github_app %} pertencente à sua conta corporativa ou organização do {% data variables.product.prodname_ghe_cloud %}. O {% data variables.product.product_name %} usa as credenciais do {% data variables.product.prodname_github_app %} para fazer solicitações ao {% data variables.product.prodname_dotcom_the_website %}. +{% ifversion ghes %} +O {% data variables.product.prodname_ghe_server %} armazena as credenciais do {% data variables.product.prodname_github_app %}. Essas credenciais serão replicadas em qualquer ambiente de clustering ou alta disponibilidade e serão armazenadas em qualquer backup, inclusive os instantâneos criados pelo {% data variables.product.prodname_enterprise_backup_utilities %}. +- Um token de autenticação válido por uma hora; +- Uma chave privada usada para gerar um novo token de autenticação. +{% endif %} + +Habilitar o {% data variables.product.prodname_github_connect %} não permitirá que os usuários do {% data variables.product.prodname_dotcom_the_website %} façam alterações no {% data variables.product.product_name %}. + +Para obter mais informações sobre o gerenciamento de contas corporativas usando a API GraphQL, consulte "[Contas corporativas](/graphql/guides/managing-enterprise-accounts)". +## Habilitar o {% data variables.product.prodname_github_connect %} + +{% ifversion ghes %} +1. Entre na {% data variables.product.product_location %} e no {% data variables.product.prodname_dotcom_the_website %}. +{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %}{% else %} +1. Entre na {% data variables.product.product_location %} e no {% data variables.product.prodname_dotcom_the_website %}. +{% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %} +1. Em "{% data variables.product.prodname_github_connect %} ainda não está habilitado", clique em **Habilitar {% data variables.product.prodname_github_connect %}**. Ao clicar em **Habilitar {% data variables.product.prodname_github_connect %}**, você concorda com os "Termos para Produtos e Funcionalidades adicionais de {% data variables.product.prodname_dotcom %}.". +{% ifversion ghes %} +![Enable GitHub Connect button](/assets/images/enterprise/business-accounts/enable-github-connect-button.png){% else %} +![Enable GitHub Connect button](/assets/images/enterprise/github-ae/enable-github-connect-button.png) +{% endif %} +1. Ao lado da conta corporativa ou organização que você pretende conectar, clique em **Connect** (Conectar). ![Botão Connect (Conectar) ao lado de uma conta corporativa ou empresa](/assets/images/enterprise/business-accounts/choose-enterprise-or-org-connect.png) + +## Desconectando uma organização ou conta corporativa de {% data variables.product.prodname_ghe_cloud %} da sua conta corporativa + +Ao se desconectar do {% data variables.product.prodname_ghe_cloud %}, o {% data variables.product.prodname_github_app %} do {% data variables.product.prodname_github_connect %} é excluído da sua conta corporativa ou organização e as credenciais armazenadas na {% data variables.product.product_location %} são excluídas. + +{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %} +1. Ao lado da conta corporativa ou organização que você gostaria de desconectar, clique em **Disable {% data variables.product.prodname_github_connect %})** (Desabilitar o {% data variables.product.prodname_github_connect %}). +{% ifversion ghes %} + ![Desabilitar o botão GitHub Connect ao lado do nome de uma conta corporativa ou organização](/assets/images/enterprise/business-accounts/disable-github-connect-button.png) +1. Leia as informações sobre a desconexão e clique em **Disable {% data variables.product.prodname_github_connect %}** (Desabilitar o {% data variables.product.prodname_github_connect %}). ![Botão Modal com informações de aviso sobre desconexão e confirmação](/assets/images/enterprise/business-accounts/confirm-disable-github-connect.png) +{% else %} + ![Desabilitar o botão GitHub Connect ao lado do nome de uma conta corporativa ou organização](/assets/images/enterprise/github-ae/disable-github-connect-button.png) +1. Leia as informações sobre a desconexão e clique em **Disable {% data variables.product.prodname_github_connect %}** (Desabilitar o {% data variables.product.prodname_github_connect %}). ![Botão Modal com informações de aviso sobre desconexão e confirmação](/assets/images/enterprise/github-ae/confirm-disable-github-connect.png) +{% endif %} diff --git a/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md b/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md new file mode 100644 index 0000000000..d9f778b165 --- /dev/null +++ b/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md @@ -0,0 +1,97 @@ +--- +title: Habilitar alertas para dependências vulneráveis no GitHub Enterprise Server +intro: 'Você pode conectar {% data variables.product.product_location %} a {% data variables.product.prodname_ghe_cloud %} e habilitar o gráfico de dependências e {% ifversion ghes %}{% data variables.product.prodname_dependabot %}{% else %}alertas de segurança{% endif %} em repositórios na sua instância.' +shortTitle: Habilitar alertas para dependências +miniTocMaxHeadingLevel: 3 +redirect_from: + - /enterprise/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /enterprise/admin/configuration/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /enterprise/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server +permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable the dependency graph and {% data variables.product.prodname_dependabot %} alerts on {% data variables.product.prodname_ghe_server %}.' +versions: + ghes: '*' +type: how_to +topics: + - Enterprise + - Security + - Dependency graph + - Dependabot +--- + +## Sobre alertas para dependências vulneráveis no {% data variables.product.prodname_ghe_server %} + +Para identificar dependências vulneráveis no seu repositório e receber alertas sobre vulnerabilidades, você deverá habilitar duas funcionalidades de segurança: +- O gráfico de dependências +- Alertas de {% data variables.product.prodname_dependabot %} + +Para obter mais informações, consulte "[Sobre o gráfico de dependências](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" e "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)". + +{% data reusables.repositories.tracks-vulnerabilities %} + +Você pode conectar {% data variables.product.product_location %} a {% data variables.product.prodname_dotcom_the_website %} e, em seguida, sincronizar os dados de vulnerabilidade na sua instância e gerar {% data variables.product.prodname_dependabot_alerts %} em repositórios com uma dependência vulnerável. + +Depois de conectar {% data variables.product.product_location %} a {% data variables.product.prodname_dotcom_the_website %} e habilitar o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %} para dependências vulneráveis, os dados de vulnerabilidade são sincronizados de {% data variables.product.prodname_dotcom_the_website %} para sua instância uma vez a cada hora. Também é possível sincronizar os dados de vulnerabilidade manualmente a qualquer momento. Nenhum código ou informações sobre o código da {% data variables.product.product_location %} são carregados para o {% data variables.product.prodname_dotcom_the_website %}. + +Quando {% data variables.product.product_location %} recebe informações sobre uma vulnerabilidade, ele identificará repositórios na sua instância que usam a versão afetada da dependência e gerará {% data variables.product.prodname_dependabot_alerts %}. Você pode personalizar como você recebe {% data variables.product.prodname_dependabot_alerts %}. Para obter mais informações, consulte "[Configurar notificações para dependências vulneráveis](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies/#configuring-notifications-for-dependabot-alerts)". + +Antes de ativar o gráfico de dependências e {% ifversion ghes > 2.21 %}{% data variables.product.prodname_dependabot %}{% else %}alertas de segurança{% endif %} para dependências vulneráveis em {% data variables.product.product_location %}, você deve conectar {% data variables.product.product_location %} a {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, consulte "[Conectando sua conta corporativa a {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)". + +## Habilitar o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %} no GitHub Enterprise Server + +Para {% data variables.product.product_location %} gerar {% data variables.product.prodname_dependabot_alerts %} sempre que forem detectadas vulnerabilidades nos seus repositórios: +- Você deve conectar {% data variables.product.product_location %} a {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, consulte "[Conectar o {% data variables.product.prodname_ghe_server %} ao {% data variables.product.prodname_ghe_cloud %}](/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)". +- Você deve habilitar o gráfico de dependências. + +{% ifversion ghes > 3.1 %} +Você pode habilitar o gráfico de dependências por meio do {% data variables.enterprise.management_console %} ou do shell administrativo. Recomendamos que você siga o encaminhamento de {% data variables.enterprise.management_console %} a menos que {% data variables.product.product_location %} use clustering. + +### Habilitando o gráfico de dependências por meio do {% data variables.enterprise.management_console %} +{% endif %}{% ifversion ghes > 3.1 %} +{% data reusables.enterprise_site_admin_settings.sign-in %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.advanced-security-tab %} +1. Em "Segurança", clique em **Gráfico de dependência**. ![Caixa de seleção para habilitar ou desabilitar o gráfico de dependências](/assets/images/enterprise/3.2/management-console/enable-dependency-graph-checkbox.png) +{% data reusables.enterprise_management_console.save-settings %} +1. Clique **Visit your instance** (Visite sua instância). + +### Habilitando o gráfico de dependências por meio do shell administrativo +{% else %} +### Habilitar o gráfico de dependências +{% endif %} +{% data reusables.enterprise_site_admin_settings.sign-in %} +1. No shell administrativo, habilite o gráfico de dependências em {% data variables.product.product_location %}: + ``` shell + $ {% ifversion ghes > 3.1 %}ghe-config app.dependency-graph.enabled true{% else %}ghe-config app.github.dependency-graph-enabled true{% endif %} + ``` + {% note %} + + **Observação**: Para obter mais informações sobre como habilitar o acesso ao shell administrativo via SSH, veja "[Acessar o shell administrativo (SSH)](/enterprise/{{ currentVersion }}/admin/configuration/accessing-the-administrative-shell-ssh)". + + {% endnote %} +1. Aplique a configuração. + ```shell + $ ghe-config-apply + ``` +1. Volte para o {% data variables.product.prodname_ghe_server %}. + +### Habilitar o {% data variables.product.prodname_dependabot_alerts %} + +Antes de habilitar {% data variables.product.prodname_dependabot_alerts %} para sua instância, você deverá habilitar o gráfico de dependências. Para obter mais informações, consulte acima. + +{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %} +1. Em "Repositories can be scanned for vulnerabilities" (Os repositórios podem ser examinados para vulnerabilidades), use o menu suspenso e clique em **Enabled without notifications** (Habilitado sem notificações). Opcionalmente, para habilitar alertas com notificações, selecione **Enabled with notifications**(Habilitado com notificações). ![Menu suspenso para habilitar a verificação vulnerabilidades nos repositórios](/assets/images/enterprise/site-admin-settings/enable-vulnerability-scanning-in-repositories.png) + {% note %} + + Recomendamos configurar {% data variables.product.prodname_dependabot_alerts %} sem notificações nos primeiros dias para evitar uma sobrecarga de e-mails. Após alguns dias, você poderá habilitar as notificações para receber {% data variables.product.prodname_dependabot_alerts %}, como de costume. + + {% endnote %} +## Exibir dependências vulneráveis no {% data variables.product.prodname_ghe_server %} + +Você pode exibir todas as vulnerabilidades na {% data variables.product.product_location %} e sincronizar manualmente os dados de vulnerabilidade do {% data variables.product.prodname_dotcom_the_website %} para atualizar a lista. + +{% data reusables.enterprise_site_admin_settings.access-settings %} +2. Na barra lateral esquerda, clique em **Vulnerabilities** (Vulnerabilidades). ![Guia Vulnerabilities (Vulnerabilidades) na barra lateral de administração do site](/assets/images/enterprise/business-accounts/vulnerabilities-tab.png) +3. Para sincronizar os dados de vulnerabilidade, clique em **Sync Vulnerabilities now** (Sincronizar vulnerabilidades agora). ![Botão Sync Vulnerabilities now (Sincronizar vulnerabilidades agora)](/assets/images/enterprise/site-admin-settings/sync-vulnerabilities-button.png) diff --git a/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md b/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md new file mode 100644 index 0000000000..7fd6a2e04e --- /dev/null +++ b/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md @@ -0,0 +1,31 @@ +--- +title: Habilitar a sincronização automática de licenças de usuários entre o GitHub Enterprise Server e o GitHub Enterprise Cloud +intro: 'É possível conectar a {% data variables.product.product_location_enterprise %} ao {% data variables.product.prodname_ghe_cloud %} e permitir que o {% data variables.product.prodname_ghe_server %} faça upload das informações de licença do usuário para a sua conta corporativa no {% data variables.product.prodname_dotcom_the_website %}.' +redirect_from: + - /enterprise/admin/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud + - /enterprise/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud + - /admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud +permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable automatic user license synchronization.' +versions: + ghes: '*' +type: how_to +topics: + - Enterprise + - GitHub Connect + - Licensing +shortTitle: Habilitar sincronização de licença do usuário +--- + +## Sobre a sincronização de licenças + +Depois de habilitar a sincronização de licença, você poderá visualizar o uso da licença em toda a sua conta corporativa, no {% data variables.product.prodname_ghe_server %} e no {% data variables.product.prodname_ghe_cloud %}. O {% data variables.product.prodname_github_connect %} sincroniza a licença entre {% data variables.product.prodname_ghe_server %} e {% data variables.product.prodname_ghe_cloud %} semanalmente. Para obter mais informações, consulte "[Gerenciar a sua licença para {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise)." + +Você também pode fazer upload manualmente das informações de licença do usuário do {% data variables.product.prodname_ghe_server %} para o {% data variables.product.prodname_ghe_cloud %}. Para obter mais informações, consulte "[Conectando sua conta corporativa a {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)". + +## Habilitar a sincronização de licenças + +Antes de habilitar a sincronização de licença na {% data variables.product.product_location_enterprise %}, conecte a {% data variables.product.product_location_enterprise %} ao {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, consulte "[Conectando sua conta corporativa a {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)". + +{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %} +1. Em "Server can sync user license count and usage" (Servidor pode sincronizar contagem e uso de licenças de usuário), selecione **Enabled** (Habilitado) no menu suspenso. ![Menu suspenso para habilitar a sincronização automática de licenças de usuário](/assets/images/enterprise/site-admin-settings/enable-user-license-drop-down.png) diff --git a/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md b/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md new file mode 100644 index 0000000000..e132d0ad21 --- /dev/null +++ b/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md @@ -0,0 +1,46 @@ +--- +title: Habilitar contribuições unificadas entre a conta corporativa e o GitHub.com +shortTitle: Habilitar contribuições unificadas +intro: 'Depois de habilitar o {% data variables.product.prodname_github_connect %}, você pode permitir que os integrantes do {% data variables.product.prodname_ghe_cloud %} destaquem o próprio trabalho no {% data variables.product.product_name %} enviando as contagens de contribuição para seus respectivos perfis do {% data variables.product.prodname_dotcom_the_website %}.' +redirect_from: + - /enterprise/admin/guides/developer-workflow/enabling-unified-contributions-between-github-enterprise-and-github-com/ + - /enterprise/admin/guides/developer-workflow/enabling-unified-contributions-between-github-enterprise-server-and-github-com/ + - /enterprise/admin/developer-workflow/enabling-unified-contributions-between-github-enterprise-server-and-githubcom/ + - /enterprise/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom + - /enterprise/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom + - /admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-unified-contributions-between-github-enterprise-server-and-githubcom +permissions: 'Enterprise owners who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable unified contributions between {% data variables.product.product_location %} and {% data variables.product.prodname_dotcom_the_website %}.' +versions: + ghes: '*' + ghae: next +type: how_to +topics: + - Enterprise + - GitHub Connect +--- + +{% data reusables.github-connect.beta %} + +Como proprietário de uma empresa, você pode permitir que os usuários finais enviem contagens de contribuições anônimas pelo trabalho deles de {% data variables.product.product_location %} para seu gráfico de contribuição de {% data variables.product.prodname_dotcom_the_website %}. + +Após habilitar a opção {% data variables.product.prodname_github_connect %} e habilitar {% data variables.product.prodname_unified_contributions %} em ambos os ambientes usuários finais na sua conta corporativa poderão conectar-se às suas contas de {% data variables.product.prodname_dotcom_the_website %} e enviar contagens de contribuição de {% data variables.product.product_name %} para {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.github-connect.sync-frequency %} Para obter mais informações, consulte "[Enviar 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)". + +Se o proprietário da empresa desabilitar a funcionalidade ou o os desenvolvedores optarem pelo cancelamento da conexão, as contagens de contribuição de {% data variables.product.product_name %} serão excluídas em {% data variables.product.prodname_dotcom_the_website %}. Se o desenvolvedor reconectar os perfis após desabilitá-los, as contagens de contribuição dos últimos 90 dias serão restauradas. + +O {% data variables.product.product_name %} envia a contagem de contribuição e a origem **somente** para os usuários conectados ({% data variables.product.product_name %}). Nenhuma informação sobre a contribuição ou sobre como ela foi feita é enviada. + +Antes de habilitar o {% data variables.product.prodname_unified_contributions %} no {% data variables.product.product_location %}, conecte o {% data variables.product.product_location %} ao {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, consulte "[Conectando sua conta corporativa a {% data variables.product.prodname_dotcom_the_website %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)". + +{% ifversion ghes %} +{% data reusables.github-connect.access-dotcom-and-enterprise %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.business %} +{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %}{% else %} +1. Entre na {% data variables.product.product_location %} e no {% data variables.product.prodname_dotcom_the_website %}. +{% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %} +1. Em "Users can share contribution counts to {% data variables.product.prodname_dotcom_the_website %}" (Usuários podem compartilhar contagens de contribuição com o {% data variables.product.prodname_dotcom_the_website %}), clique em **Request access** (Solicitar acesso). ![Request access to unified contributions option](/assets/images/enterprise/site-admin-settings/dotcom-ghe-connection-request-access.png){% ifversion ghes %} +2. [Faça login](https://enterprise.github.com/login) no site do {% data variables.product.prodname_ghe_server %} para obter mais instruções. + +Ao solicitar acesso, podemos redirecioná-lo para o site {% data variables.product.prodname_ghe_server %} para verificar os termos de serviço atuais. +{% endif %} diff --git a/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md b/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md new file mode 100644 index 0000000000..d72c6239e9 --- /dev/null +++ b/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md @@ -0,0 +1,44 @@ +--- +title: Habilitar a pesquisa unificada entre a sua conta corporativa e o GitHub.com +shortTitle: Habilitar pesquisa unificada +intro: 'Após habilitar a opção {% data variables.product.prodname_github_connect %}, você poderá permitir a pesquisa de {% data variables.product.prodname_dotcom_the_website %} para os integrantes da sua sua empresa em {% data variables.product.product_name %}.' +redirect_from: + - /enterprise/admin/guides/developer-workflow/enabling-unified-search-between-github-enterprise-and-github-com/ + - /enterprise/admin/guides/developer-workflow/enabling-unified-search-between-github-enterprise-server-and-github-com/ + - /enterprise/admin/developer-workflow/enabling-unified-search-between-github-enterprise-server-and-githubcom/ + - /enterprise/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom + - /enterprise/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom + - /admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-unified-search-between-github-enterprise-server-and-githubcom +permissions: 'Enterprise owners who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable unified search between {% data variables.product.product_name %} and {% data variables.product.prodname_dotcom_the_website %}.' +versions: + ghes: '*' + ghae: next +topics: + - Enterprise + - GitHub Connect + - GitHub search +--- + +{% data reusables.github-connect.beta %} + +Ao habilitar a pesquisa unificada, os usuários poderão visualizar os resultados da pesquisa de conteúdo público e privado em {% data variables.product.prodname_dotcom_the_website %} ao pesquisar em {% data variables.product.product_location %}{% ifversion ghae %} em {% data variables.product.prodname_ghe_managed %}{% endif %}. + +Os usuários não conseguirão pesquisar na {% data variables.product.product_location %} pelo {% data variables.product.prodname_dotcom_the_website %}, mesmo se tiverem acesso aos dois ambientes. Eles só poderão pesquisar nos repositórios privados em que você habilitou a {% data variables.product.prodname_unified_search %} e não terão acesso às organizações conectadas do {% data variables.product.prodname_ghe_cloud %}. Para obter mais informações, consulte "[Sobre a pesquisa em {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github/#searching-across-github-enterprise-and-githubcom-simultaneously)" e "[Habilitando uma pesquisa de repositório privado de {% data variables.product.prodname_dotcom_the_website %} na sua conta corporativa](/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment)." + +A pesquisa via APIs REST e GraphQL não inclui resultados do {% data variables.product.prodname_dotcom_the_website %}. Não há suporte para a pesquisa avançada e a pesquisa de wikis no {% data variables.product.prodname_dotcom_the_website %}. + +{% ifversion ghes %} +{% data reusables.github-connect.access-dotcom-and-enterprise %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.business %} +{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %}{% else %} +1. Entre na {% data variables.product.product_location %} e no {% data variables.product.prodname_dotcom_the_website %}. +{% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %} +1. Em "Users can search {% data variables.product.prodname_dotcom_the_website %}" (Usuários podem pesquisar no {% data variables.product.prodname_dotcom_the_website %}), use o menu suspenso e clique em **Enabled** (Habilitado). ![Habilitar a opção de pesquisa no menu suspenso de pesquisa do GitHub.com](/assets/images/enterprise/site-admin-settings/github-dotcom-enable-search.png) +1. Em "Users can search private repositories on {% data variables.product.prodname_dotcom_the_website %}" (Usuários podem pesquisar em repositórios privados no {% data variables.product.prodname_dotcom_the_website %}), use o menu suspenso e clique em **Enabled** (Habilitado). ![Habilitar a opção de pesquisa em repositórios privados no menu suspenso de pesquisa do GitHub.com](/assets/images/enterprise/site-admin-settings/enable-private-search.png) + +## Leia mais + +- "[Conectando a sua conta corporativa a {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)" + diff --git a/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md b/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md new file mode 100644 index 0000000000..7f05483ba0 --- /dev/null +++ b/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md @@ -0,0 +1,25 @@ +--- +title: Gerenciando conexões entre as suas corporativas +intro: 'Com o {% data variables.product.prodname_github_connect %}, você pode compartilhar determinados recursos entre a {% data variables.product.product_location %} e a sua conta corporativa ou de organização do {% data variables.product.prodname_ghe_cloud %} no {% data variables.product.prodname_dotcom_the_website %}.' +redirect_from: + - /enterprise/admin/developer-workflow/connecting-github-enterprise-to-github-com + - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-and-github-com/ + - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-server-and-github-com/ + - /enterprise/admin/developer-workflow/connecting-github-enterprise-server-and-githubcom/ + - /enterprise/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud + - /enterprise/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud +versions: + ghes: '*' + ghae: next +topics: + - Enterprise +children: + - /connecting-your-enterprise-account-to-github-enterprise-cloud + - /enabling-unified-search-between-your-enterprise-account-and-githubcom + - /enabling-unified-contributions-between-your-enterprise-account-and-githubcom + - /enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud +shortTitle: Conectar as contas corporativas +--- + diff --git a/translations/pt-BR/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md b/translations/pt-BR/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md index a1f2c8b88c..e2ff4eb99a 100644 --- a/translations/pt-BR/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md +++ b/translations/pt-BR/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md @@ -353,7 +353,7 @@ Você pode parar a replicação nos nós passivos para a sua implantação de cl {% data reusables.enterprise_clustering.open-configuration-file %} -3. In the top-level `[cluster]` section, delete the `redis-master-replica`, and `mysql-master-replica` key-value pairs. +3. Na seção de nível superior `[cluster]` exclua os pares chave-valor`redis-master-replica` e `mysql-master-replica`. 4. Exclua cada seção para um nó passivo. Para nódulos passivos, a `réplica` é configurada como habilitada.

    diff --git a/translations/pt-BR/content/admin/enterprise-management/configuring-clustering/upgrading-a-cluster.md b/translations/pt-BR/content/admin/enterprise-management/configuring-clustering/upgrading-a-cluster.md index 4cd9d70895..12b0d7a92d 100644 --- a/translations/pt-BR/content/admin/enterprise-management/configuring-clustering/upgrading-a-cluster.md +++ b/translations/pt-BR/content/admin/enterprise-management/configuring-clustering/upgrading-a-cluster.md @@ -79,7 +79,7 @@ Atualize para a versão mais recente do cluster do {% data variables.product.pro > gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u > gpg: Good signature from "GitHub Enterprise (Upgrade Package Key) > " ``` -5. Assim que for concluído, o processo de atualização reinicializará o nó primário MySQL. Verify that you can `ping` each node after it reboots.{% ifversion ghes > 2.22 %} -6. Connect to the administrative shell of the primary MySQL node and run the `ghe-cluster-config-apply` command. -7. When `ghe-cluster-config-apply` is complete, check that the services are in a healthy state by running `ghe-cluster-status`.{% endif %} +5. Assim que for concluído, o processo de atualização reinicializará o nó primário MySQL. Verifique se você pode fazer `ping` de cada nó depois que ele for reiniciado.{% ifversion ghes > 2.22 %} +6. Conecte-se ao shell administrativo do nó do MySQL primário e execute o comando `ghe-cluster-config-apply`. +7. Quando `ghe-cluster-config-apply` for concluído, verifique se os serviços estão em estado saudável executando `ghe-cluster-status`.{% endif %} 8. Saia do modo de manutenção do shell administrativo de qualquer nó executando o código `ghe-cluster-maintenance -u`. diff --git a/translations/pt-BR/content/admin/enterprise-support/overview/about-github-enterprise-support.md b/translations/pt-BR/content/admin/enterprise-support/overview/about-github-enterprise-support.md index 039b6b9f7d..1aefc2a97a 100644 --- a/translations/pt-BR/content/admin/enterprise-support/overview/about-github-enterprise-support.md +++ b/translations/pt-BR/content/admin/enterprise-support/overview/about-github-enterprise-support.md @@ -33,7 +33,7 @@ Além de todos os benefícios de {% data variables.contact.enterprise_support %} - Suporte gravado por meio de nosso portal de suporte 24 horas por dias, 7 dias por semana - Suporte por telefone 24 horas por dia, 7 dias por semana - Um Contrato de nível de serviço (SLA, Service Level Agreement) com tempos de resposta inicial garantidos - - Customer Reliability Engineers + - Engenheiros de Confiabilidade do Cliente - Acesso a conteúdo premium - Verificação de integridade agendadas - Horas administrativas gerenciadas diff --git a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md index 0322fbf7b5..07eeff2615 100644 --- a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md +++ b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md @@ -37,19 +37,46 @@ Este artigo explica como os administradores do site podem configurar {% data var {% endif %} +{%- ifversion ghes < 3.2 %} + Os recursos da CPU e memória disponíveis para {% data variables.product.product_location %} determinam o rendimento máximo do trabalho para {% data variables.product.prodname_actions %}. O teste interno em {% data variables.product.company_short %} demonstrou o rendimento máximo a seguir para instâncias de {% data variables.product.prodname_ghe_server %} com um intervalo de configurações da CPU e memória. Você pode ver diferentes tipos de transferência, dependendo dos níveis gerais de atividade na sua instância. -| vCPUs | Memória | Rendimento máximo do trabalho | -|:----- |:------- |:----------------------------- | -| | | | -{%- ifversion ghes > 3.1 %} -| 4 | 32 GB | Demo or light testing | | 8 | 64 GB | 30 jobs | | 16 | 128 GB | 60 jobs | | 32 | 256 GB | 120 jobs | | 64 | 512 GB | 160 jobs | -{%- else ifversion ghes < 3.2 %} -| 4 | 32 GB | Demo or light testing | | 8 | 64 GB | 25 jobs | | 16 | 160 GB | 35 jobs | | 32 | 256 GB | 100 jobs | {%- endif %} +{%- ifversion ghes > 3.1 %} + +Os recursos de CPU e memória disponíveis para {% data variables.product.product_location %} determinam o número de trabalhos que podem ser executados simultaneamente sem perda de desempenho. + +O pico de trabalhos simultâneos rodando sem perda de desempenho depende de fatores como duração do trabalho, uso de artefatos, número de repositórios em execução de ações, e quanto outro trabalho sua instância está fazendo não relacionado a ações. Os testes internos no GitHub demonstraram os objetivos de desempenho a seguir para o GitHub Enterprise Server em uma série de configurações de CPU e memória: + +{% endif %} + +{%- ifversion ghes < 3.2 %} + +| vCPUs | Memória | Rendimento máximo do trabalho | +|:----- |:------- |:------------------------------ | +| 4 | 32 GB | Demonstração ou testes rápidos | +| 8 | 64 GB | 25 trabalhos | +| 16 | 160 GB | 35 trabalhos | +| 32 | 256 GB | 100 trabalhos | + +{%- endif %} + +{%- ifversion ghes > 3.1 %} + +| vCPUs | Memória | Simultaneidade máxima* | +|:----- |:------- |:---------------------- | +| 32 | 128 GB | 1500 trabalhos | +| 64 | 256 GB | 1900 trabalhos | +| 96 | 384 GB | 2200 trabalhos | + +*A simultaneidade máxima foi medida usando vários repositórios, a duração do trabalho de aproximadamente 10 minutos e o upload de artefato de 10 MB. Você pode ter um desempenho diferente dependendo dos níveis gerais de atividade na sua instância. + +{%- endif %} + + Se você{% ifversion ghes = 2.22 %}habilitou o plano beta de{% else %}plano para habilitar{% endif %} {% data variables.product.prodname_actions %} para os usuários de uma instância existente, revise os níveis de atividade para usuários e automações na instância e garantir que você tenha fornecido CPU e memória adequadas para seus usuários. Para obter mais informações sobre o monitoramento da capacidade e desempenho de {% data variables.product.prodname_ghe_server %}, consulte "[Monitoramento do seu aplicativo](/admin/enterprise-management/monitoring-your-appliance)". Para obter mais informações sobre os requisitos mínimos de hardware para {% data variables.product.product_location %}, consulte as considerações sobre hardware para a plataforma da sua instância. @@ -98,9 +125,9 @@ O suporte de {% data variables.product.prodname_actions %} em {% data variables. {% endif %} -## Networking considerations +## Considerações de rede -{% data reusables.actions.proxy-considerations %} For more information about using a proxy with {% data variables.product.prodname_ghe_server %}, see "[Configuring an outbound web proxy server](/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server)." +{% data reusables.actions.proxy-considerations %} Para obter mais informações sobre o uso de um proxy com {% data variables.product.prodname_ghe_server %}, consulte "[Configurando um servidor de proxy web de saída](/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server)". {% ifversion ghes > 2.22 %} @@ -134,6 +161,6 @@ Se você quiser saber mais sobre as práticas de segurança para {% data variabl {% endif %} -## Reserved Names +## Nomes reservados -When you enable {% data variables.product.prodname_actions %} for your enterprise, two organizations are created: `github` and `actions`. If your enterprise already uses the `github` organization name, `github-org` (or `github-github-org` if `github-org` is also in use) will be used instead. If your enterprise already uses the `actions` organization name, `github-actions` (or `github-actions-org` if `github-actions` is also in use) will be used instead. Once actions is enabled, you won't be able to use these names anymore. +Ao habilitar {% data variables.product.prodname_actions %} para a sua empresa, serão criadas duas organizações: `github` e `actions`. Se sua empresa já usa o nome da organização `github`, `github-org` (ou `github-github-org` se `github-org` também estiver em uso) será usado. Se sua empresa já usa o nome da organização `actions`, `github-actions` (ou `github-actions-org` se `github-actions` também estiver em uso) será usado. Uma vez que as ações são habilitadas, você não poderá usar mais esses nomes. diff --git a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md index 4e0e2058db..371cd3f81b 100644 --- a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md +++ b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md @@ -10,7 +10,6 @@ children: - /enabling-github-actions-with-azure-blob-storage - /enabling-github-actions-with-amazon-s3-storage - /enabling-github-actions-with-minio-gateway-for-nas-storage - - /enforcing-github-actions-policies-for-your-enterprise shortTitle: Habilitar GitHub Actions --- diff --git a/translations/pt-BR/content/admin/github-actions/index.md b/translations/pt-BR/content/admin/github-actions/index.md index c776b49e2b..01ca76079e 100644 --- a/translations/pt-BR/content/admin/github-actions/index.md +++ b/translations/pt-BR/content/admin/github-actions/index.md @@ -16,6 +16,5 @@ children: shortTitle: Gerenciar o GitHub Actions --- -{% data reusables.actions.ae-beta %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} diff --git a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md index f793e38a7f..c61afdd7ac 100644 --- a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md +++ b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md @@ -18,7 +18,6 @@ shortTitle: Adicionar ações à sua empresa {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} Os fluxos de trabalho de {% data variables.product.prodname_actions %} podem usar _ações_, que são tarefas individuais que você pode combinar para criar tarefas e personalizar seu fluxo de trabalho. Você pode criar suas próprias ações ou usar e personalizar ações compartilhadas pela comunidade {% data variables.product.prodname_dotcom %}. 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 2dcf4fde90..5ff7f5dccc 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 @@ -19,7 +19,6 @@ shortTitle: Usar GitHub Connect para ações {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.actions.enterprise-github-connect-warning %} -{% data reusables.actions.ae-beta %} Por padrão, os fluxos de trabalho {% data variables.product.prodname_actions %} em {% data variables.product.product_name %} não podem usar ações diretamente de {% data variables.product.prodname_dotcom_the_website %} ou [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions). @@ -27,8 +26,16 @@ Para tornar todas as ações de {% data variables.product.prodname_dotcom_the_we ## Habilitar o acesso automático a todas as ações de {% data variables.product.prodname_dotcom_the_website %} -Antes de habilitar o acesso a todas as ações de {% data variables.product.prodname_dotcom_the_website %} na sua instância corporativa, você deve conectar sua empresa a {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, consulte "[Conectar o {% data variables.product.prodname_ghe_server %} ao {% data variables.product.prodname_ghe_cloud %}](/enterprise/{{ currentVersion }}/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)". +Antes de habilitar o acesso a todas as ações de {% data variables.product.prodname_dotcom_the_website %} na sua instância corporativa, você deve conectar sua empresa a {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, consulte "[Conectando sua empresa a {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)". -{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %} +{% data reusables.enterprise-accounts.access-enterprise %} +{%- ifversion ghes < 3.1 %} +{% data reusables.enterprise-accounts.settings-tab %} +{%- endif %} +{% data reusables.enterprise-accounts.github-connect-tab %} +{%- ifversion ghes > 3.0 or ghae %} +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) +{%- else %} 1. Em "Servidor pode usar ações do GitHub.com em execuções de fluxos 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.png) +{%- endif %} 1. {% data reusables.actions.enterprise-limit-actions-use %} 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 1fb86cf7ad..34ebc73e6f 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 @@ -14,13 +14,14 @@ shortTitle: Sincronizar ações manualmente {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.actions.enterprise-no-internet-actions %} -A abordagem recomendada de habilitar o acesso a ações a partir de {% data variables.product.prodname_dotcom_the_website %} é permitir o acesso automático para todas as ações. Você pode fazer isso usando {% data variables.product.prodname_github_connect %} para integrar {% data variables.product.product_name %} com {% data variables.product.prodname_ghe_cloud %} . Para obter mais informações, consulte "[Habilitar acesso automático a ações de {% data variables.product.prodname_dotcom_the_website %} usando {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". +{% ifversion ghes or ghae-next %} -No entanto, se você quer ter um controle mais rigoroso sobre quais as ações permitidas na sua empresa, você pode seguir esse guia para usar a ferramenta de código aberto de {% data variables.product.company_short %}de [`actions-sync`](https://github.com/actions/actions-sync) para sincronizar repositórios de ações individuais de {% data variables.product.prodname_dotcom_the_website %} da sua empresa. +A abordagem recomendada de habilitar o acesso a ações a partir de {% data variables.product.prodname_dotcom_the_website %} é permitir o acesso automático para todas as ações. Você pode fazer isso usando {% data variables.product.prodname_github_connect %} para integrar {% data variables.product.product_name %} com {% data variables.product.prodname_ghe_cloud %}. Para obter mais informações, consulte "[Habilitar o acesso automático às ações de {% data variables.product.prodname_dotcom_the_website %} usando o {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". + +No entanto, se você quiser um controle mais rigoroso sobre quais as ações são permitidas na sua empresa, você{% else %}Você{% endif %} poderá seguir este guia para usar a ferramenta de código aberto de {% data variables.product.company_short %} [`ação-sincronização`](https://github.com/actions/actions-sync) para sincronizar repositórios de ações individuais de {% data variables.product.prodname_dotcom_the_website %} para a sua empresa. ## Sobre a ferramenta `actions-sync` @@ -33,7 +34,7 @@ A ferramenta `actions-sync` só pode fazer download de ações de {% data variab ## Pré-requisitos * Antes de usar a ferramenta `actions-sync`, você deve garantir que todas as organizações de destino existem na sua empresa. O exemplo a seguir demonstra como sincronizar ações com uma organização com o nome de `synced-actions`. 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)". -* Você deve criar um token de acesso pessoal (PAT) na sua empresa que pode criar e gravar em repositórios nas organizações de destino. Para mais informação, consulte "[Criando um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)." +* Você deve criar um token de acesso pessoal (PAT) na sua empresa que pode criar e gravar em repositórios nas organizações de destino. Para obter mais informações, consulte[Criando um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)."{% ifversion ghes %} * Se você deseja sincronizar as ações empacotadas na organização das `ações` em {% data variables.product.product_location %}, você deverá ser proprietário da organização das `ações`. {% note %} @@ -46,21 +47,21 @@ A ferramenta `actions-sync` só pode fazer download de ações de {% data variab ```shell ghe-org-admin-promote -u USERNAME -o actions - ``` + ```{% endif %} -## Exemplo: Usando a ferramenta de `actions-sync` +## Example: Using the `actions-sync` tool -Este exemplo demonstra o uso da ferramenta de `actions-sync` para sincronizar uma ação individual do {% data variables.product.prodname_dotcom_the_website %} com uma instância corporativa. +Este exemplo demonstra o uso da ferramenta `actions-sync` para sincronizar uma ação individual a partir de {% data variables.product.prodname_dotcom_the_website %} para a instância de uma empresa. {% note %} -**Observação:** Este exemplo usa o comando `actions-sync`, que requer acesso simultâneo à API de {% data variables.product.prodname_dotcom_the_website %} e à API da instância empresarial a partir da sua máquina. Se você só puder acessar um sistema de cada vez, pode usar os comandos `actions-sync pull` e `push`. Para obter mais informações, consulte o README de [`actions-sync`](https://github.com/actions/actions-sync#not-connected-instances). +**Observação:** Este exemplo usa o comando `actions-sync sync`, que exige acesso simultâneo à API de {% data variables.product.prodname_dotcom_the_website %} e à API da instância empresarial da sua máquina. Se você puder acessar apenas um sistema de cada vez, você poderá usar os comandos `actions-sync pull` e `push`. Para obter mais informações, consulte [README de `actions-sync`](https://github.com/actions/actions-sync#not-connected-instances). {% endnote %} -1. Faça o download e extraia as últimas versões [`actions-sync`](https://github.com/actions/actions-sync/releases) para o sistema operacional da sua máquina. +1. Faça o download e extraia a versão mais recente [`actions-sync`](https://github.com/actions/actions-sync/releases) para o sistema operacional da sua máquina. 1. Crie um diretório para armazenar arquivos de cache para a ferramenta. -1. Execute o comando `actions-sync sync`: +1. Run the `actions-sync sync` command: ```shell ./actions-sync sync \ diff --git a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md index 71d653a385..fb198ed748 100644 --- a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md +++ b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md @@ -14,7 +14,6 @@ shortTitle: Cache de ferramentas para executores off-line {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Sobre as ações de configuração incluídas e o cache da ferramenta do executor 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 84ee55ed38..182a558daf 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 @@ -13,7 +13,6 @@ shortTitle: Use as últimas ações empacotadas {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} A instância da sua empresa inclui uma série de ações integradas que podem ser usadas nos seus fluxos de trabalho. Para obter mais informações sobre as ações agrupadas, consulte "[Ações oficiais agrupadas com a sua instância corporativa](/admin/github-actions/about-using-actions-in-your-enterprise#official-actions-bundled-with-your-enterprise-instance)". @@ -29,17 +28,13 @@ Você pode usar {% data variables.product.prodname_github_connect %} para permit Uma vez configurado {% data variables.product.prodname_github_connect %}, você poderá usar a última versão de uma ação, excluindo seu repositório local nas `ações` da organização na sua instância. Por exemplo, se a instância corporativa estiver usando a ação `actions/checkout@v1`, e você precisar usar `actions/checkout@v2` que não estão disponíveis na sua instância corporativa, por exemplo, siga as etapas a seguir para poder usar a última ação de `checkout` de {% data variables.product.prodname_dotcom_the_website %}: -1. Por padrão, os administradores do site não são proprietários da organização de ações agrupadas. Para obter o acesso necessário para excluir o repositório checkout`, use o comandoghe-org-admin-promote` para promover um usuário a proprietário da organização das `ações` empacotadas. Para obter mais informações, consulte "[Acessar o shell administrativa (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" e "[`ghe-org-admin-promote`](/admin/configuration/command-line-utilities#ghe-org-admin-promote)". Por exemplo: - - ```shell - $ ghe-org-admin-promote -u octocat -o actions - Do you want to give organization admin privileges for actions to octocat? (y/N) y - Making octocat an admin of actions - --> Adding octocat as an admin of actions - --> octocat is now an admin of the actions organization - --> Done. - ``` -1. Na sua instância {% data variables.product.product_name %}, exclua o repositório `checkout` dentro da organização de `ações`. Para obter informações sobre como excluir um repositório, consulte "[Excluir um repositório ](/github/administering-a-repository/deleting-a-repository)". -1. É recomendável que você deixe as `ações` da organização uma vez que não necessite mais de acesso administrativo. Para obter mais informações, consulte "[Remover-se de uma organização ](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization)". +1. Em uma conta de proprietário corporativo em {% data variables.product.product_name %}, acesse o repositório que você deseja excluir da organização *ações* (neste exemplo `checkout`). +1. Por padrão, os administradores do site não são proprietários da organização de *ações* agrupadas. Para obter o acesso necessário para excluir o repositório de `checkout`, você deve usar as ferramentas de administrador do site. Clique em {% octicon "rocket" aria-label="The rocket ship" %} no canto superior direito de qualquer página do repositório. ![Ícone de foguete para acessar as configurações de administrador do site](/assets/images/enterprise/site-admin-settings/access-new-settings.png) +1. Clique em {% octicon "shield-lock" %} **Segurança** para ver a visão geral de segurança do repositório. ![Cabeçalho de segurança do repositório](/assets/images/enterprise/site-admin-settings/access-repo-security-info.png) +1. Em "Privilégio de acesso", clique em **Desbloquear**. ![Botão Desbloquear](/assets/images/enterprise/site-admin-settings/unlock-priviledged-repo-access.png) +1. Em **Motivo**, digite um motivo para desbloquear o repositório e depois clique em **Desbloquear**. ![Diálogo de confirmação](/assets/images/enterprise/site-admin-settings/confirm-unlock-repo-access.png) +1. Agora que o repositório está desbloqueado, você pode sair das páginas de administrador do site e excluir o repositório dentro das `ações da organização`. Na parte superior da página, clique no nome do repositório, neste exemplo **check-out**, para retornar à página de resumo. ![Link para nome do repositório](/assets/images/enterprise/site-admin-settings/display-repository-admin-summary.png) +1. Em "Informações do repositório", clique em **Ver código** para sair das páginas de administração do site e exibir o repositório `check-out`. +1. Exclua o repositório do `check-out` dentro organização das `ações`. Para obter informações sobre como excluir um repositório, consulte "[Excluir um repositório](/github/administering-a-repository/deleting-a-repository)". ![Ver link de código](/assets/images/enterprise/site-admin-settings/exit-admin-page-for-repository.png) 1. Configure o YAML do seu fluxo de trabalho para usar `ações/checkout@v2`. 1. Cada vez que o seu fluxo de trabalho é executado, o executor usará a versão `v2` de `actions/checkout` de {% data variables.product.prodname_dotcom_the_website %}. diff --git a/translations/pt-BR/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md b/translations/pt-BR/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md index 1ab69d89f1..915bac0331 100644 --- a/translations/pt-BR/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md +++ b/translations/pt-BR/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md @@ -13,7 +13,6 @@ redirect_from: - /admin/github-actions/getting-started-with-github-actions-for-github-ae --- -{% data reusables.actions.ae-beta %} Este artigo explica como os administradores do site podem configurar {% data variables.product.prodname_ghe_managed %} para usar {% data variables.product.prodname_actions %}. diff --git a/translations/pt-BR/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md b/translations/pt-BR/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md index e98b9994a3..a84f2c6a8d 100644 --- a/translations/pt-BR/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md +++ b/translations/pt-BR/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md @@ -8,7 +8,6 @@ redirect_from: shortTitle: Usar ações --- -{% data reusables.actions.ae-beta %} Os fluxos de trabalho de {% data variables.product.prodname_actions %} podem usar _ações_, que são tarefas individuais que você pode combinar para criar tarefas e personalizar seu fluxo de trabalho. Você pode criar suas próprias ações ou usar e personalizar ações compartilhadas pela comunidade {% data variables.product.prodname_dotcom %}. diff --git a/translations/pt-BR/content/admin/guides.md b/translations/pt-BR/content/admin/guides.md index 20302a042f..214e6638da 100644 --- a/translations/pt-BR/content/admin/guides.md +++ b/translations/pt-BR/content/admin/guides.md @@ -35,13 +35,13 @@ includeGuides: - /admin/configuration/configuring-rate-limits - /admin/configuration/configuring-secret-scanning-for-your-appliance - /admin/configuration/configuring-tls - - /admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud + - /admin/configuration/connecting-your-enterprise-account-to-github-enterprise-cloud - /admin/configuration/enabling-and-scheduling-maintenance-mode - /admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud - /admin/configuration/enabling-private-mode - /admin/configuration/enabling-subdomain-isolation - - /admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom - - /admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom + - /admin/configuration/enabling-unified-contributions-between-your-enterprise-account-and-githubcom + - /admin/configuration/enabling-unified-search-between-your-enterprise-account-and-githubcom - /admin/configuration/initializing-github-ae - /admin/configuration/managing-github-for-mobile-for-your-enterprise - /admin/configuration/network-ports diff --git a/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md b/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md index 5315444166..51d9890f0c 100644 --- a/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md +++ b/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md @@ -27,7 +27,7 @@ Para usar este guia, você deve conhecer os seguintes conceitos do AWS: - [EC2 e Virtual Private Cloud](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-vpc.html) (se você pretende iniciar uma nuvem virtual privada) - [Preços do AWS](https://aws.amazon.com/pricing/) (para calcular e gerenciar custos) -For an architectural overview, see the "[AWS Architecture Diagram for Deploying GitHub Enterprise Server](/assets/images/installing-github-enterprise-server-on-aws.png)". +Para obter uma visão geral da arquitetura, consulte o "[Diagrama de arquitetura AWS para implantar o GitHub Enterprise Server](/assets/images/installing-github-enterprise-server-on-aws.png)". Este guia recomenda o princípio do menor privilégio ao configurar {% data variables.product.product_location %} no AWS. Para obter mais informações, consulte a [Documentação do Gerencimaento de acesso e Identidade (IAM) do AWS](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#grant-least-privilege). diff --git a/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md b/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md index 328936a0c4..d696eecb85 100644 --- a/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md +++ b/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md @@ -1,6 +1,6 @@ --- title: Sobre contas corporativas -intro: 'With {% data variables.product.product_name %}, you can use an enterprise account to give administrators a single point of visibility and management.' +intro: 'Com {% data variables.product.product_name %}, você pode usar uma conta corporativa para dar aos administradores um único ponto de visibilidade e gestão.' redirect_from: - /enterprise/admin/installation/about-enterprise-accounts - /enterprise/admin/overview/about-enterprise-accounts diff --git a/translations/pt-BR/content/admin/overview/about-upgrades-to-new-releases.md b/translations/pt-BR/content/admin/overview/about-upgrades-to-new-releases.md index 02ba08420f..44e54cfdd0 100644 --- a/translations/pt-BR/content/admin/overview/about-upgrades-to-new-releases.md +++ b/translations/pt-BR/content/admin/overview/about-upgrades-to-new-releases.md @@ -13,7 +13,7 @@ topics: {% data variables.product.product_name %} está constantemente melhorando, com novas funcionalidades e correções de erros introduzidas por meio de versões maiores e menores. {% ifversion ghae %}{% data variables.product.prodname_ghe_managed %} é um serviço totalmente gerenciado. Portanto, {% data variables.product.company_short %} conclui o processo de atualização da sua empresa.{% endif %} -As principais versões incluem novas funcionalidades e atualizações de recursos e, de modo geral, ocorrem {% ifversion ghae %}a cada algumas semanas ou meses{% else %} trimestralmente{% endif %}. {% ifversion ghae %}{% data variables.product.company_short %} irá atualizar a empresa para a última versão principal. Você será avisado antecipadamente de qualquer período de inatividade planejado para sua empresa.{% endif %} +As principais versões incluem novas funcionalidades e atualizações de recursos e normalmente ocorrem a cada trimestre. {% ifversion ghae %}{% data variables.product.company_short %} irá atualizar a empresa para a última versão principal. Você será avisado antecipadamente de qualquer período de inatividade planejado para sua empresa.{% endif %} {% ifversion ghes %} @@ -43,7 +43,6 @@ Para atualizar a sua empresa para uma nova versão, consulte "[Liberar notas](/e ## Leia mais -- [ {% data variables.product.prodname_roadmap %} ]({% data variables.product.prodname_roadmap_link %}) no repositório `github/roadmap` -{% ifversion ghae %} +- [ {% data variables.product.prodname_roadmap %} ]({% data variables.product.prodname_roadmap_link %}) no repositório `github/roadmap` {% ifversion ghae %} - [ Observações da versão de {% data variables.product.prodname_ghe_managed %}](/admin/release-notes) {% endif %} diff --git a/translations/pt-BR/content/admin/overview/system-overview.md b/translations/pt-BR/content/admin/overview/system-overview.md index fa491c52de..f2acbd40cc 100644 --- a/translations/pt-BR/content/admin/overview/system-overview.md +++ b/translations/pt-BR/content/admin/overview/system-overview.md @@ -74,11 +74,11 @@ O {% data variables.product.prodname_ghe_server %} também apresenta outros recu O {% data variables.product.prodname_ghe_server %} executa um sistema operacional Linux personalizado somente com os aplicativos e serviços necessários. O {% data variables.product.prodname_dotcom %} gerencia patches do sistema operacional central do appliance como parte do ciclo padrão de versões do produto. Os patches tratam de problemas de segurança não críticos, funcionalidade e estabilidade nos aplicativos do {% data variables.product.prodname_dotcom %}. O {% data variables.product.prodname_dotcom %} também oferece pacthes de segurança críticos, conforme necessário e fora do ciclo regular de versões. -{% data variables.product.prodname_ghe_server %} is provided as an appliance, and many of the operating system packages are modified compared to the usual Debian distribution. We do not support modifying the underlying operating system for this reason (including operating system upgrades), which is aligned with the [{% data variables.product.prodname_ghe_server %} license and support agreement](https://enterprise.github.com/license), under section 11.3 Exclusions. +{% data variables.product.prodname_ghe_server %} é fornecido como um dispositivo, e muitos dos pacotes do sistema operacional são modificados em comparação com a distribuição habitual do Debian. Não não damos suporte à modificação do sistema operacional subjacente por esta razão (incluindo atualizações do sistema operacional), que está alinhado à licença [{% data variables.product.prodname_ghe_server %} e acordo de suporte](https://enterprise.github.com/license), na seção 11.3 Exclusões. -Currently, the base of the {% data variables.product.prodname_ghe_server %} appliance is Debian 9 (Stretch) and receives support under the Debian Long Term Support program. There are plans to move to a newer base operating system before the end of the Debian LTS period for Stretch. +Atualmente, a base do dispositivo de {% data variables.product.prodname_ghe_server %} é o Debian 9 (Stretch) e recebe suporte como parte do programa de suporte de longo prazo Debian. Há planos para mudar para um sistema operacional base mais novo antes do final do período Debian LTS para o Stretch. -Regular patch updates are released on the {% data variables.product.prodname_ghe_server %} [releases](https://enterprise.github.com/releases) page, and the [release notes](/enterprise-server/admin/release-notes) page provides more information. These patches typically contain upstream vendor and project security patches after they've been tested and quality approved by our engineering team. There can be a slight time delay from when the upstream update is released to when it's tested and bundled in an upcoming {% data variables.product.prodname_ghe_server %} patch release. +Atualizações de atualização regulares são lançadas na página de {% data variables.product.prodname_ghe_server %} [versões](https://enterprise.github.com/releases) e a página [de notas de versão](/enterprise-server/admin/release-notes) fornece mais informações. De modo geral, estas atualizações contêm caminhos de segurança do fornecedor a montante e do projeto depois de terem sido testadas e de qualidade aprovadas pela nossa equipe de engenharia. Pode haver um pequeno atraso entre o lançamento da atualização upstream e o teste e empacotamento de uma versão futura de atualização de {% data variables.product.prodname_ghe_server %}. ### Segurança de rede diff --git a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise.md b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise.md new file mode 100644 index 0000000000..fd761f7d83 --- /dev/null +++ b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise.md @@ -0,0 +1,59 @@ +--- +title: Aplicar as políticas do GitHub Actions à sua empresa +intro: 'Os administradores das empresas podem gerenciar o acesso a {% data variables.product.prodname_actions %} em uma empresa.' +redirect_from: + - /enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise + - /admin/github-actions/enforcing-github-actions-policies-for-your-enterprise + - /admin/github-actions/enabling-github-actions-for-github-enterprise-server/enforcing-github-actions-policies-for-your-enterprise +versions: + ghes: '*' + ghae: '*' +type: how_to +topics: + - Actions + - Enterprise + - Policies +shortTitle: Políticas do GitHub Actions +--- + +{% data reusables.actions.enterprise-beta %} + +## Sobre as permissões de {% data variables.product.prodname_actions %} para sua empresa + +{% ifversion ghae %}{% else %}Ao habilitar {% data variables.product.prodname_actions %} em {% data variables.product.prodname_ghe_server %}, isso será habilitado para todas as organizações da sua empresa. {% endif %}Você pode escolher desabilitar {% data variables.product.prodname_actions %} para todas as organizações da sua empresa ou apenas permitir organizações específicas. Você também pode limitar o uso de ações públicas, de modo que as pessoas só possam usar ações locais que existem na sua empresa. + +## Gerenciar as permissões de {% data variables.product.prodname_actions %} para a sua empresa + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.actions-tab %} +{% data reusables.actions.enterprise-actions-permissions %} + +{% ifversion ghes > 2.22 or ghae %} +## Permitir a execução de ações específicas + +{% data reusables.actions.allow-specific-actions-intro %} + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.actions-tab %} +1. Em **Políticas**, selecione **Permitir ações específicas** e adicione as suas ações necessárias à lista. + {%- ifversion ghes or ghae-issue-5094 %} + ![Adicionar ações para permitir lista](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png) + {%- elsif ghae %} + ![Adicionar ações para permitir lista](/assets/images/enterprise/github-ae/enterprise-actions-policy-allow-list.png) + {%- endif %} +{% endif %} + +{% ifversion ghes > 2.22 or ghae %} +## Habilitar fluxos de trabalho para bifurcações privadas do repositório + +{% data reusables.github-actions.private-repository-forks-overview %} + +### Configurar a política de uma bifurcação privada para a sua empresa + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.actions-tab %} +{% data reusables.github-actions.private-repository-forks-configure %} +{% endif %} diff --git a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md index 07f224f544..ea486693b2 100644 --- a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md +++ b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md @@ -34,12 +34,12 @@ topics: - Enterprise - Policies - Security -shortTitle: Aplicar políticas do repositório +shortTitle: Políticas de gerenciamento do repositório --- ## Configurar a visibilidade padrão de novos repositórios na sua empresa -Toda vez que alguém criar um novo repositório na sua empresa, essa pessoa deverá escolher uma visibilidade para o repositório. Ao configurar uma configuração padrão de visibilidade para a empresa, você escolhe qual visibilidade será selecionada por padrão. For more information on repository visibility, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." +Toda vez que alguém criar um novo repositório na sua empresa, essa pessoa deverá escolher uma visibilidade para o repositório. Ao configurar uma configuração padrão de visibilidade para a empresa, você escolhe qual visibilidade será selecionada por padrão. 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)". Se um proprietário corporativo impedir que os integrantes criem certos tipos de repositórios, os integrantes não serão capazes de criar esse tipo de repositório, mesmo se a configuração de visibilidade for o padrão para esse tipo. Para obter mais informações, consulte "[Definir uma política para a criação de repositórios](#setting-a-policy-for-repository-creation)". diff --git a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/index.md b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/index.md index a770565ceb..724d61da1a 100644 --- a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/index.md +++ b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/index.md @@ -1,6 +1,6 @@ --- title: Aplicar as políticas para sua empresa -intro: You can configure policies for organizations in your enterprise. +intro: Você pode configurar políticas para organizações da sua empresa. redirect_from: - /enterprise/admin/policies/enforcing-policies-for-your-enterprise versions: @@ -11,6 +11,7 @@ topics: children: - /enforcing-repository-management-policies-in-your-enterprise - /restricting-email-notifications-for-your-enterprise + - /enforcing-github-actions-policies-for-your-enterprise - /enforcing-policies-for-advanced-security-in-your-enterprise shortTitle: Aplicar políticas --- diff --git a/translations/pt-BR/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md b/translations/pt-BR/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md index 85d189a29e..0a6dd5fea3 100644 --- a/translations/pt-BR/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md +++ b/translations/pt-BR/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md @@ -84,7 +84,7 @@ A variável `$GITHUB_VIA` está disponível no ambiente de pre-receive quando a | Valor | Ação | Mais informações | |:-------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 
    auto-merge deployment api
    | Merge automático do branch base através de uma implantação criada com a API | "[Repositórios](/rest/reference/repos#create-a-deployment)" na documentação da API REST | -| 
    blob#save
    | Mudar para o conteúdo de um arquivo na interface web | "[Editing files](/repositories/working-with-files/managing-files/editing-files)" | +| 
    blob#save
    | Mudar para o conteúdo de um arquivo na interface web | "[Editando arquivos](/repositories/working-with-files/managing-files/editing-files)" | | 
    branch merge api
    | Merge de um branch através da API | "[Repositórios](/rest/reference/repos#merge-a-branch)" na documentação da API REST | | 
    branches page delete button
    | Exclusão de um branch na interface web | "[Criar e excluir branches dentro do seu repositório](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#deleting-a-branch)" | | 
    git refs create api
    | Criação de um ref através da API | "[Banco de dados Git](/rest/reference/git#create-a-reference)" na documentação da API REST | diff --git a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/index.md b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/index.md index b217fb0ed0..3011f6429a 100644 --- a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/index.md +++ b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/index.md @@ -5,7 +5,7 @@ redirect_from: - /enterprise/admin/categories/admin-bootcamp/ - /enterprise/admin/user-management/organizations-and-teams - /enterprise/admin/user-management/managing-organizations-in-your-enterprise -intro: 'As organizações são uma forma excelente de criar conjuntos distintos de usuários na empresa, como divisões ou grupos que trabalham em projetos semelhantes. {% ifversion ghae %}Internal{% else %}Public and internal{% endif %} repositories that belong to an organization are accessible to members of other organizations in the enterprise, while private repositories are inaccessible to anyone but members of the organization that are granted access.' +intro: 'As organizações são uma forma excelente de criar conjuntos distintos de usuários na empresa, como divisões ou grupos que trabalham em projetos semelhantes. {% ifversion ghae %}Os repositórios internos{% else %}públicos e internos{% endif %} que pertencem a uma organização podem ser acessados por membros de outras organizações da empresa, enquanto os repositórios privados podem ser acessador por qualquer pessoa exceto integrantes da organização que recebem acesso.' versions: ghes: '*' ghae: '*' diff --git a/translations/pt-BR/content/admin/user-management/managing-repositories-in-your-enterprise/migrating-to-internal-repositories.md b/translations/pt-BR/content/admin/user-management/managing-repositories-in-your-enterprise/migrating-to-internal-repositories.md index d02aa84e14..5825ed1970 100644 --- a/translations/pt-BR/content/admin/user-management/managing-repositories-in-your-enterprise/migrating-to-internal-repositories.md +++ b/translations/pt-BR/content/admin/user-management/managing-repositories-in-your-enterprise/migrating-to-internal-repositories.md @@ -19,7 +19,7 @@ shortTitle: Migração interna de repositório ## Sobre repositórios internos -Os repositórios internos estão disponíveis em {% data variables.product.prodname_ghe_server %} 2.20+. {% data reusables.repositories.about-internal-repos %} For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." +Os repositórios internos estão disponíveis em {% data variables.product.prodname_ghe_server %} 2.20+. {% data reusables.repositories.about-internal-repos %} Para obter mais informações, consulte "[Sobre repositórios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)". Em versões futuras do {% data variables.product.prodname_ghe_server %}, ajustaremos como a visibilidade do repositório funciona para que os termos público, interno e privado tenham significados uniformes para desenvolvedores em {% data variables.product.prodname_ghe_server %} e {% data variables.product.prodname_ghe_cloud %}. diff --git a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/best-practices-for-user-security.md b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/best-practices-for-user-security.md index b14778b3be..d0d2961f01 100644 --- a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/best-practices-for-user-security.md +++ b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/best-practices-for-user-security.md @@ -25,7 +25,7 @@ Para obter mais informações sobre como configurar a autenticação de dois fat ## Exigir um gerenciador de senhas -We strongly recommend requiring your users to install and use a password manager--such as [LastPass](https://lastpass.com/) or [1Password](https://1password.com/)--on any computer they use to connect to your enterprise. Essa medida garante senhas mais fortes e muito menos passíveis de violação ou roubo. +É altamente recomendável exigir que seus usuários instalem e usem um gerenciador de senhas --tais como o [LastPass](https://lastpass.com/) ou [1Password](https://1password.com/) -- em qualquer computador que usarem para conectar-se à sua empresa. Essa medida garante senhas mais fortes e muito menos passíveis de violação ou roubo. ## Restringir o acesso a equipes e repositórios diff --git a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md index b5291b8de4..62a99b96c5 100644 --- a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md @@ -20,7 +20,7 @@ topics: Existem vários tipos de mensagens de usuário. - Mensagens que aparecem na página {% ifversion ghes %}página de ingresso ou {% endif %}saída{% ifversion ghes > 2.22 or ghae %} -- Mandatory messages, which appear once in a pop-up window that must be dismissed{% endif %}{% ifversion ghes or ghae %} +- Mensagens obrigatórias, que aparecem uma vez em uma janela pop-up que deve ser ignorada{% endif %}{% ifversion ghes or ghae %} - Banners de anúncios, que aparecem na parte superior de cada página{% endif %} {% ifversion ghes %} @@ -83,8 +83,8 @@ Cada vez que um usuário vê uma mensagem obrigatória, um evento de log de audi {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %} -1. À direita da "Mensagem obrigatória", clique em **Adicionar mensagem**. ![Add mandatory message button](/assets/images/enterprise/site-admin-settings/add-mandatory-message-button.png) -1. Em "Mensagem obrigatória", na caixa de texto, digite sua mensagem. ![Mandatory message text box](/assets/images/enterprise/site-admin-settings/mandatory-message-text-box.png) +1. À direita da "Mensagem obrigatória", clique em **Adicionar mensagem**. ![Botão de adicionar mensagem obrigatória](/assets/images/enterprise/site-admin-settings/add-mandatory-message-button.png) +1. Em "Mensagem obrigatória", na caixa de texto, digite sua mensagem. ![Caixa de texto obrigatória](/assets/images/enterprise/site-admin-settings/mandatory-message-text-box.png) {% data reusables.enterprise_site_admin_settings.message-preview-save %} {% endif %} diff --git a/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md b/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md index 545c9934c2..590c20f304 100644 --- a/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md +++ b/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md @@ -54,8 +54,8 @@ topics: | ------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion ghes > 3.0 or ghae-next %} | `business.advanced_security_policy_update` | Um administrador do site cria, atualiza ou remove uma política para {% data variables.product.prodname_GH_advanced_security %}. Para obter mais informações, consulte "[Aplicar políticas para {% data variables.product.prodname_advanced_security %} na sua empresa](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)".{% endif %} | `business.clear_members_can_create_repos` | Um administrador do site elimina uma restrição de criação de repositórios em organizações da empresa. Para obter mais informações, consulte "[Aplicar políticas de gerenciamento do repositório na sua empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)".{% ifversion ghes > 3.1 %} -| `business.referrer_override_enable` | A site admin enables the referrer policy override. For more information, see "[Configuring the referrer policy for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)." | -| `business.referrer_override_disable` | A site admin disables the referrer policy override. For more information, see "[Configuring the referrer policy for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)."{% endif %} +| `business.referrer_override_enable` | Um administrador do site habilita a substituição da política de indicação. Para obter mais informações, consulte "[Configurando a política de indicação para sua empresa](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)". | +| `business.referrer_override_disable` | O administrador de um site desabilita a substituição de política de indicação. Para obter mais informações, consulte "[Configurando a política de indicação para sua empresa](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)".{% endif %} | `business.update_member_repository_creation_permission` | Um administrador do site restringe a criação de repositórios em organizações da empresa. Para obter mais informações, consulte "[Aplicar políticas de gerenciamento do repositório na sua empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)".{% ifversion ghes %} | `enterprise.config.lock_anonymous_git_access` | Um administrador do site bloqueia acessos de leitura anônimos do Git para impedir que os administradores do repositório alterem as configurações de acessos de leitura anônimos do Git existentes nos repositórios da empresa. Para obter mais informações, consulte "[Aplicar políticas de gerenciamento do repositório na sua empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)". | | `enterprise.config.unlock_anonymous_git_access` | Um administrador do site desbloqueia acessos de leitura anônimos do Git para permitir que administradores alterem as configurações de acessos de leitura anônimos do Git existentes nos repositórios da empresa. Para obter mais informações, consulte "[Aplicar políticas de gerenciamento do repositório na sua empresa](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)".{% endif %} @@ -95,7 +95,7 @@ topics: ## Pull requests -| Action | Description | | :- | :- |{% ifversion ghes > 3.1 or ghae-next %} | `pull_request.create` | A pull request was created. Para obter mais informações, consulte "[Criar uma pull request](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)." | | `pull_request.close` | A pull request was closed without being merged. For more information, see "[Closing a pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)." | | `pull_request.reopen` | A pull request was reopened after previously being closed. | | `pull_request.merge` | A pull request was merged. Para obter mais informações, consulte "[Fazer merge de uma pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)". | | `pull_request.indirect_merge` | A pull request was considered merged because the pull request's commits were merged into the target branch. | | `pull_request.ready_for_review` | A pull request was marked as ready for review. Para obter mais informações, consulte "[Alterar o stage de um pull request](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request#marking-a-pull-request-as-ready-for-review)". | | `pull_request.converted_to_draft` | A pull request was converted to a draft. Para obter mais informações, consulte "[Alterar o stage de um 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_review_request` | A review was requested on a pull request. Para obter mais informações, consulte "[Sobre merges do pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)". | | `pull_request.remove_review_request` | A review request was removed from a pull request. Para obter mais informações, consulte "[Sobre merges do pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)". | | `pull_request_review.submit` | A review was submitted for a pull request. Para obter mais informações, consulte "[Sobre merges do pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)". | | `pull_request_review.dismiss` | A review on a pull request was dismissed. For more information, see "[Dismissing a pull request review](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)." | | `pull_request_review.delete` | A review on a pull request was deleted. | | `pull_request_review_comment.create` | A review comment was added to a pull request. Para obter mais informações, consulte "[Sobre merges do pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)". | | `pull_request_review_comment.update` | A review comment on a pull request was changed. |{% endif %} | `pull_request_review_comment.delete` | A review comment on a pull request was deleted. | +| Ação | Descrição | | :- | :- |{% ifversion ghes > 3.1 or ghae-next %} | `pull_request.create` | Um pull request foi criado. Para obter mais informações, consulte "[Criar uma pull request](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)." | | `pull_request.close` | Um pull request foi fechado sem fazer merge. Para obter mais informações, consulte "[Fechar um pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)". | | `pull_request.reopen` | Um pull request foi reaberto após ter sido fechado anteriormente. | | `pull_request.merge` | Um pull request foi mesclado. Para obter mais informações, consulte "[Fazer merge de uma pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)". | | `pull_request.indirect_merge` | Um pull request foi considerado como merge, porque os commits do pull request foram mesclados no branch de destino. | | `pull_request.ready_for_review` | Um pull request foi mercado como pronto para revisão. Para obter mais informações, consulte "[Alterar o stage de um pull request](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request#marking-a-pull-request-as-ready-for-review)". | | `pull_request.converted_to_draft` | Um pull request foi convertido em rascunho. Para obter mais informações, consulte "[Alterar o stage de um 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_review_request` | Uma revisão foi solicitada em um pull request. Para obter mais informações, consulte "[Sobre merges do pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)". | | `pull_request.remove_review_request` | Uma solicitação de revisão foi removida de um pull request. Para obter mais informações, consulte "[Sobre merges do pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)". | | `pull_request_review.submit` | Uma revisão foi enviada para um pull request. Para obter mais informações, consulte "[Sobre merges do pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)". | | `pull_request_review.dismiss` | Uma revisão em um pull request foi ignorada. Para obter mais informações, consulte "[Ignorar uma revisão de pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)". | | `pull_request_review.delete` | Uma revisão em um pull request foi excluída. | | `pull_request_review_comment.create` | O comentário de uma revisão foi adicionado a um ull request. Para obter mais informações, consulte "[Sobre merges do pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)". | | `pull_request_review_comment.update` | O comentário de uma revisão em um pull request foi alterado. |{% endif %} | `pull_request_review_comment.delete` | O comentário de uma revisão em um pull request foi excluído. | ## Branches protegidos diff --git a/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/index.md b/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/index.md index 596ffa7c02..4b61478c4f 100644 --- a/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/index.md +++ b/translations/pt-BR/content/admin/user-management/monitoring-activity-in-your-enterprise/index.md @@ -1,6 +1,6 @@ --- title: Monitorar atividades na sua empresa -intro: You can view activity by leveraging dashboards and logs in your enterprise. +intro: Você pode ver suas atividades aproveitando os painéis e seus registos na sua empresa. redirect_from: - /enterprise/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance - /enterprise/admin/user-management/monitoring-activity-in-your-enterprise diff --git a/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md b/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md index 45e28f8f2d..b8ceaf692c 100644 --- a/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md +++ b/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md @@ -30,6 +30,9 @@ Se você não puder acessar {% data variables.product.product_name %}, entre em {% data reusables.saml.dotcom-saml-explanation %} Os proprietários da organização podem convidar sua conta de usuário em {% data variables.product.prodname_dotcom %} para participar da organização que usa o SSO SAML, o que permite que você contribua com a organização e mantenha sua identidade e contribuições existentes em {% data variables.product.prodname_dotcom %}. +Se você for integrante de um {% data variables.product.prodname_emu_enterprise %}, você usará uma nova conta que lhe será fornecida. {% data reusables.enterprise-accounts.emu-more-info-account %} + + Ao acessar os recursos dentro de uma organização que usa o SSO SAML, o {% data variables.product.prodname_dotcom %} irá redirecionar você para o SAML IdP da organização para que você efetue a autenticação. Depois de efetuar a autenticação com sucesso com sua conta no IdP, este irá redirecionar você de volta para {% data variables.product.prodname_dotcom %}, onde você poderá acessar os recursos da organização. {% data reusables.saml.outside-collaborators-exemption %} diff --git a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md index 36952ecf5e..99419d0824 100644 --- a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md +++ b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md @@ -104,7 +104,7 @@ Depois de adicionar uma nova chave SSH à sua conta do {% data variables.product {% tip %} - **Tip:** Alternatively, you can locate the hidden `.ssh` folder, open the file in your favorite text editor, and copy it to your clipboard. + **Dica:** Como alternativa, você pode localizar a pasta oculta de `.ssh`, abrir o arquivo no seu editor de texto favorito e copiá-lo na sua área de transferência. {% endtip %} @@ -124,7 +124,7 @@ Depois de adicionar uma nova chave SSH à sua conta do {% data variables.product {% data reusables.cli.cli-learn-more %} -To add an SSH key to your GitHub account, use the `ssh-key add` subcommand, specifying your public key. +Para adicionar uma chave SSH à sua conta do GitHub, use o subcomando `ssh-key add`, especificando a sua chave pública. ```shell gh ssh-key add key-file diff --git a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md index 19873c5412..af801cd33e 100644 --- a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md +++ b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md @@ -20,7 +20,7 @@ shortTitle: Gerar nova chave SSH Se você ainda não tem uma chave SSH, você deve gerar uma nova chave SSH para usar para a autenticação. Se você não tem certeza se já tem uma chave SSH, você pode verificar se há chaves existentes. Para obter mais informações, consulte "[Verificar as chaves SSH existentes](/github/authenticating-to-github/checking-for-existing-ssh-keys)". -{% ifversion fpt %} +{% ifversion fpt or ghae-next or ghes > 3.1 %} Se você deseja usar uma chave de segurança de hardware para efetuar a autenticação em {% data variables.product.product_name %}, você deverá gerar uma nova chave SSH para a sua chave de segurança de hardware. Você deve conectar a sua chave de segurança de hardware ao seu computador ao efetuar a a sua autenticação com o par de chaves. Para obter mais informações, consulte as [notas de versão do OpenSSH 8.2](https://www.openssh.com/txt/release-8.2). @@ -31,6 +31,12 @@ Se não quiser reinserir a sua frase secreta toda vez que usar a sua chave SSH, {% data reusables.command_line.open_the_multi_os_terminal %} 2. Cole o texto abaixo, substituindo o endereço de e-mail pelo seu {% data variables.product.product_name %}. + {% ifversion ghae %} + + ```shell + $ ssh-keygen -t rsa -b 4096 -C "your_email@example.com" + ``` + {% else %} ```shell $ ssh-keygen -t ed25519 -C "your_email@example.com" ``` @@ -38,20 +44,22 @@ Se não quiser reinserir a sua frase secreta toda vez que usar a sua chave SSH, **Observação:** Se você estiver usando um sistema legado que não é compatível com o algoritmo Ed25519, use: ```shell - $ ssh-keygen -t rsa -b 4096 -C "your_email@example.com" + $ ssh-keygen -t rsa -b 4096 -C "your_email@example.com" ``` {% endnote %} - This creates a new SSH key, using the provided email as a label. + {% endif %} + + Isto cria uma nova chave SSH, usando o nome de e-mail fornecido como uma etiqueta. ```shell - > Generating public/private ed25519 key pair. + > Generating public/private algorithm key pair. ``` 3. Quando aparecer a solicitação "Enter a file in which to save the key" (Insira um arquivo no qual salvar a chave), presssione Enter. O local padrão do arquivo será aceito. {% mac %} ```shell - > Enter a file in which to save the key (/Users/you/.ssh/id_ed25519): [Press enter] + > Enter a file in which to save the key (/Users/you/.ssh/id_algorithm): [Press enter] ``` {% endmac %} @@ -59,7 +67,7 @@ Se não quiser reinserir a sua frase secreta toda vez que usar a sua chave SSH, {% windows %} ```shell - > Enter a file in which to save the key (/c/Users/you/.ssh/id_ed25519):[Press enter] + > Enter a file in which to save the key (/c/Users/you/.ssh/id_algorithm):[Press enter] ``` {% endwindows %} @@ -67,7 +75,7 @@ Se não quiser reinserir a sua frase secreta toda vez que usar a sua chave SSH, {% linux %} ```shell - > Enter a file in which to save the key (/home/you/.ssh/id_ed25519): [Press enter] + > Enter a file in which to save the key (/home/you/.ssh/algorithm): [Press enter] ``` {% endlinux %} @@ -107,7 +115,7 @@ Antes de adicionar uma nova chave SSH ao agente para gerenciar suas chaves, voc Host * AddKeysToAgent yes UseKeychain yes - IdentityFile ~/.ssh/id_ed25519 + IdentityFile ~/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %} ``` {% note %} @@ -137,11 +145,11 @@ Antes de adicionar uma nova chave SSH ao agente para gerenciar suas chaves, voc 3. Adicione sua chave SSH privada ao ssh-agent e armazene sua frase secreta no keychain. {% data reusables.ssh.add-ssh-key-to-ssh-agent %} ```shell - $ ssh-add -K ~/.ssh/id_ed25519 + $ ssh-add -K ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %} ``` {% note %} - **Note:** The `-K` option is Apple's standard version of `ssh-add`, which stores the passphrase in your keychain for you when you add an SSH key to the ssh-agent. Se você optou por não adicionar uma frase secreta à sua chave, execute o comando sem a opção `-K`. + **Observação:** A opção `-K` é a versão padrão da Apple de `ssh-add`, que armazena a frase secreta na sua keychain para você quando você adiciona uma chave SSH ao ssh-agent. Se você optou por não adicionar uma frase secreta à sua chave, execute o comando sem a opção `-K`. Caso não tenha a versão standard da Apple instalada, você poderá receber uma mensagem de erro. Para obter mais informações sobre como resolver esse erro, consulte "[Erro: ssh-add: opção ilícita -- K](/articles/error-ssh-add-illegal-option-k)". @@ -189,8 +197,10 @@ Se você estiver usando macOS ou Linux, Talvez você precise atualizar seu clien {% data reusables.command_line.open_the_multi_os_terminal %} 3. Cole o texto abaixo, substituindo o endereço de e-mail da sua conta em {% data variables.product.product_name %}. ```shell - $ ssh-keygen -t ed25519-sk -C "your_email@example.com" + $ ssh-keygen -t {% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}-sk -C "your_email@example.com" ``` + + {% ifversion not ghae %} {% note %} **Observação:** Se o comando falhar e você receber o erro `formato inválido` ou a funcionalidade `não compatível`, é possível que você esteja usando uma chave de segurança de hardware incompatível com o algoritmo Ed25519. Insira o comando a seguir. @@ -199,13 +209,14 @@ Se você estiver usando macOS ou Linux, Talvez você precise atualizar seu clien ``` {% endnote %} + {% endif %} 4. Quando solicitado, toque no botão da sua chave de segurança de hardware. 5. Quando for solicitado a "Insira um arquivo para salvar a chave", pressione Enter para aceitar o local padrão do arquivo. {% mac %} ```shell - > Enter a file in which to save the key (/Users/you/.ssh/id_ed25519_sk): [Press enter] + > Enter a file in which to save the key (/Users/you/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): [Press enter] ``` {% endmac %} @@ -213,7 +224,7 @@ Se você estiver usando macOS ou Linux, Talvez você precise atualizar seu clien {% windows %} ```shell - > Enter a file in which to save the key (/c/Users/you/.ssh/id_ed25519_sk):[Press enter] + > Enter a file in which to save the key (/c/Users/you/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk):[Press enter] ``` {% endwindows %} @@ -221,7 +232,7 @@ Se você estiver usando macOS ou Linux, Talvez você precise atualizar seu clien {% linux %} ```shell - > Enter a file in which to save the key (/home/you/.ssh/id_ed25519_sk): [Press enter] + > Enter a file in which to save the key (/home/you/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): [Press enter] ``` {% endlinux %} diff --git a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/index.md b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/index.md index c47c033296..8afd70871f 100644 --- a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/index.md +++ b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/index.md @@ -1,6 +1,6 @@ --- title: Conectar-se ao GitHub com SSH -intro: 'You can connect to {% data variables.product.product_name %} using the Secure Shell Protocol (SSH), which provides a secure channel over an unsecured network.' +intro: 'Você pode conectar-se a {% data variables.product.product_name %} usando o protocolo Secure Shell (SSH), que fornece um canal seguro por meio de uma rede insegura.' redirect_from: - /key-setup-redirect/ - /linux-key-setup/ 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 1ad5a4c457..34f7522637 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,6 +28,10 @@ Você pode acessar seus recursos em {% data variables.product.product_name %} de 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 fpt %} +Se você for 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](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users#authenticating-as-a-managed-user)". Se você não for integrante de um {% data variables.product.prodname_emu_enterprise %}, você irá efetuar a autenticação usando seu navegador em {% data variables.product.prodname_dotcom_the_website %}. +{% endif %} + - **Apenas nome de usuário e senha** - Você criará uma senha ao criar sua conta de usuário 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 "[Criar uma senha forte](/github/authenticating-to-github/creating-a-strong-password)". - **Autenticação de dois fatores (2FA)** (recomendado) @@ -66,9 +70,9 @@ Você pode acessar repositórios no {% data variables.product.product_name %} pe 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. -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). +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). -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). +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). @@ -76,13 +80,13 @@ If you authenticate without {% data variables.product.prodname_cli %}, you must Você pode trabalhar com todos os repositórios no {% data variables.product.product_name %} por meio de SSH, embora os firewalls e proxys possam se recusar a permitir conexões de SSH. -If you authenticate with {% data variables.product.prodname_cli %}, the CLI will find SSH public keys on your machine and will prompt you to select one for upload. If {% data variables.product.prodname_cli %} does not find a SSH public key for upload, it can generate a new SSH public/private keypair and upload the public key to your {% data variables.product.product_name %} account. Then, 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). +Se você efetuar a autenticação com {% data variables.product.prodname_cli %}, a CLI encontrará chaves públicas SSH no seu computador e solicitará que você selecione uma para upload. Se {% data variables.product.prodname_cli %} não encontrar uma chave pública SSH para upload, ele poderá gerar um novo conjunto de chaves SSH público/privado e enviar a chave pública para a sua conta de {% data variables.product.product_name %}. Em seguida, você pode 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). -If you authenticate without {% data variables.product.prodname_cli %}, you will need to generate an SSH public/private keypair on your local machine and add the public key to your {% data variables.product.product_name %} account. Para obter mais informações, consulte "[Gerar uma nova chave SSH e adicioná-la ao ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)". Sempre que usar o Git para efetuar a autenticação com {% data variables.product.product_name %}, será solicitado que você digite a senha da sua chave SSH, a menos que você [tenha armazenado a chave](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent). +Se você efetuar a autenticação sem {% data variables.product.prodname_cli %}, você deverá gerar um conjunto de chaves SSH público/privada na sua máquina local e adicionar a chave pública à sua conta de {% data variables.product.product_name %}. Para obter mais informações, consulte "[Gerar uma nova chave SSH e adicioná-la ao ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)". Sempre que usar o Git para efetuar a autenticação com {% data variables.product.product_name %}, será solicitado que você digite a senha da sua chave SSH, a menos que você [tenha armazenado a chave](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent). -### Authorizing for SAML single sign-on +### Autorizando para logon único SAML {% ifversion fpt %}Para usar um token de acesso pessoal ou chave SSH para acessar os recursos que pertencem a uma organização que usa o logon único SAML, você também deve autorizar o token pessoal ou chave SSH. Para obter mais informações consulte "[Autorizar um token de acesso pessoal para usar com logon único SAML](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" ou "[Autorizando uma chave SSH para uso com o logon único SAML](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on).{% endif %} diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/authorizing-github-apps.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/authorizing-github-apps.md index 2a5433cd93..a59722a2a5 100644 --- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/authorizing-github-apps.md +++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/authorizing-github-apps.md @@ -1,6 +1,6 @@ --- -title: Authorizing GitHub Apps -intro: 'You can authorize a {% data variables.product.prodname_github_app %} to allow an application to retrieve information about your {% data variables.product.prodname_dotcom %} account and, in some circumstances, to make changes on {% data variables.product.prodname_dotcom %} on your behalf.' +title: Autorizando aplicativos GitHub +intro: 'Você pode autorizar um {% data variables.product.prodname_github_app %} para permitir que um aplicativo recupere informações sobre sua conta de {% data variables.product.prodname_dotcom %} e, em algumas circunstâncias, para fazer mudanças em {% data variables.product.prodname_dotcom %} em seu nome.' versions: fpt: '*' ghes: '*' @@ -12,41 +12,41 @@ redirect_from: - /github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-github-apps --- -Third-party applications that need to verify your {% data variables.product.prodname_dotcom %} identity, or interact with the data on {% data variables.product.prodname_dotcom %} on your behalf, can ask you to authorize the {% data variables.product.prodname_github_app %} to do so. +Os plicativos de terceiros que precisam verificar a sua identidade {% data variables.product.prodname_dotcom %}, ou interagir com os dados em {% data variables.product.prodname_dotcom %} em seu nome, podem pedir para que você autorize {% data variables.product.prodname_github_app %} a fazê-lo. -When authorizing the {% data variables.product.prodname_github_app %}, you should ensure you trust the application, review who it's developed by, and review the kinds of information the application wants to access. +Ao autorizar o {% data variables.product.prodname_github_app %}, você deve ter certeza de que se trata de um aplicativo confiável, examinar por quem foi desenvolvido e analisar os tipos de informação que o aplicativo quer acessar. -During authorization, you'll be prompted to grant the {% data variables.product.prodname_github_app %} permission to: -* **Verify your {% data variables.product.prodname_dotcom %} identity**
    When authorized, the {% data variables.product.prodname_github_app %} will be able to programmatically retrieve your public GitHub profile, as well as some private details (such as your email address), depending on the level of access requested. -* **Know which resources you can access**
    When authorized, the {% data variables.product.prodname_github_app %} will be able to programmatically read the _private_ {% data variables.product.prodname_dotcom %} resources that you can access (such as private {% data variables.product.prodname_dotcom %} repositories) _where_ an installation of the {% data variables.product.prodname_github_app %} is also present. The application may use this, for example, so that it can show you an appropriate list of repositories. -* **Act on your behalf**
    The application may need to perform tasks on {% data variables.product.prodname_dotcom %}, as you. This might include creating an issue, or commenting on a pull request. This ability to act on your behalf is limited to the {% data variables.product.prodname_dotcom %} resources where _both_ you and the {% data variables.product.prodname_github_app %} have access. In some cases, however, the application may never make any changes on your behalf. +Durante a autorização, você será solicitado a conceder a permissão {% data variables.product.prodname_github_app %} para: +* **Verifique sua identidade de {% data variables.product.prodname_dotcom %}**
    Quando autorizado, o {% data variables.product.prodname_github_app %} poderá recuperar programaticamente seu perfil público do GitHub, bem como alguns dados privados (como seu endereço de e-mail), dependendo do nível de acesso solicitado. +* **Pode saber quais recursos você pode acessar**
    Quando autorizado, o {% data variables.product.prodname_github_app %} poderá ler programaticamente os _recursos privados_ {% data variables.product.prodname_dotcom %} que você pode acessar (como repositórios privados de {% data variables.product.prodname_dotcom %}) _, em que _ uma instalação do {% data variables.product.prodname_github_app %} também está presente. O aplicativo pode usar isso, por exemplo, para que possa exibir uma lista de repositórios apropriada. +* **Agir no seu nome**
    O aplicativo pode precisar executar tarefas em {% data variables.product.prodname_dotcom %}, como você. Isso pode incluir criar um problema ou comentar em um pull request. Essa capacidade de agir no seu nome limita-se aos recursos de {% data variables.product.prodname_dotcom %} em que _tanto_ você quanto {% data variables.product.prodname_github_app %} têm acesso. Em alguns casos, no entanto, é possível que o aplicativo nunca faça alterações em seu nome. -## When does a {% data variables.product.prodname_github_app %} act on your behalf? +## Quando um {% data variables.product.prodname_github_app %} age em seu nome? -The situations in which a {% data variables.product.prodname_github_app %} acts on your behalf vary according to the purpose of the {% data variables.product.prodname_github_app %} and the context in which it is being used. +As situações nas quais um {% data variables.product.prodname_github_app %} atua em seu nome variam de acordo com o propósito do {% data variables.product.prodname_github_app %} e o contexto em que ele está sendo usado. -For example, an integrated development environment (IDE) may use a {% data variables.product.prodname_github_app %} to interact on your behalf in order to push changes you have authored through the IDE back to repositories on {% data variables.product.prodname_dotcom %}. The {% data variables.product.prodname_github_app %} will achieve this through a [user-to-server request](/get-started/quickstart/github-glossary#user-to-server-request). +Por exemplo, um ambiente de desenvolvimento integrado (IDE) pode usar um {% data variables.product.prodname_github_app %} para interagir em seu nome para fazer push das alterações que você criou através do IDE de volta para repositórios em {% data variables.product.prodname_dotcom %}. O {% data variables.product.prodname_github_app %} vai conseguir isso por meio de uma solicitação de usuário para servidor [](/get-started/quickstart/github-glossary#user-to-server-request). -When a {% data variables.product.prodname_github_app %} acts on your behalf in this way, this is identified on GitHub via a special icon that shows a small avatar for the {% data variables.product.prodname_github_app %} overlaid onto your own avatar, similar to the one shown below. +Quando um {% data variables.product.prodname_github_app %} age em seu nome desta forma, isto é identificado no GitHub por meio de um ícone especial que mostra um avatar pequeno para {% data variables.product.prodname_github_app %} no seu próprio avatar, semelhante ao mostrado abaixo. -![An issue created by a "user-to-server" request from a {% data variables.product.prodname_github_app %}](/assets/images/help/apps/github-apps-new-issue.png) +![Um problema criado por uma slicitação de "usuário para servidor" de um {% data variables.product.prodname_github_app %}](/assets/images/help/apps/github-apps-new-issue.png) -## To what extent can a {% data variables.product.prodname_github_app %} know which resources you can access and act on your behalf? +## Até que ponto um {% data variables.product.prodname_github_app %} pode saber quais recursos você pode acessar e agir em seu nome? -The extent to which a {% data variables.product.prodname_github_app %} can know which resources you can access and act on your behalf, after you have authorized it, is limited by: +A medida que um {% data variables.product.prodname_github_app %} pode saber quais recursos você pode acessar e agir em seu nome, após autorizá-lo, é limitada por: -* The organizations or repositories on which the app is installed -* The permissions the app has requested -* Your access to {% data variables.product.prodname_dotcom %} resources +* As organizações ou repositórios nos quais o aplicativo está instalado +* As permissões que o aplicativo solicitou +* Seu acesso a recursos de {% data variables.product.prodname_dotcom %} -Let's use an example to explain this. +Vamos usar um exemplo para explicar isso. -{% data variables.product.prodname_dotcom %} user Alice logs into a third-party web application, ExampleApp, using their {% data variables.product.prodname_dotcom %} identity. During this process, Alice authorizes ExampleApp to perform actions on their behalf. +A usuária Alice de {% data variables.product.prodname_dotcom %} efetua o login em um aplicativo web de terceiros, ExempleApp, usando sua identidade de {% data variables.product.prodname_dotcom %}. Durante este processo, Alice autoriza o ExemploApp a executar ações em seu nome. -However, the activity ExampleApp is able to perform on Alice's behalf in {% data variables.product.prodname_dotcom %} is constrained by: the repositories on which ExampleApp is installed, the permissions ExampleApp has requested, and Alice's access to {% data variables.product.prodname_dotcom %} resources. +No entanto, a atividade que o ExampleApp pode executar em nome de Alice no {% data variables.product.prodname_dotcom %} é restringido: pelos repositórios nos quais o aplicativo é instalado, as permissões que o ExampleApp solicitou e o acesso de Alice aos recursos de {% data variables.product.prodname_dotcom %}. -This means that, in order for ExampleApp to create an issue on Alice's behalf, in a repository called Repo A, all of the following must be true: +Isto significa que, para o ExempleApp criar um novo problema em nome da Alice, em um repositório denominado Repo A, todas as afirmações a seguir devem ser verdadeiras: -* ExampleApp's {% data variables.product.prodname_github_app %} requests write access to issues. -* A user having admin access for Repo A must have installed ExampleApp's {% data variables.product.prodname_github_app %} on Repo A. -* Alice must have read permission for Repo A. For information about which permissions are required to perform various activities, see "[Repository permission levels for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization#repository-access-for-each-permission-level)." +* {% data variables.product.prodname_github_app %} do ExampleApp solicita acesso de gravação aos problemas. +* Um usuário que tenha acesso de administrador ao repositório A deve ter instalado o {% data variables.product.prodname_github_app %} do ExampleApp no repositório A. +* Alice deve ter lido a permissão para o Repo A. Para obter informações sobre quais permissões são necessárias para executar várias atividades, consulte "[Níveis de permissão do Repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization#repository-access-for-each-permission-level).". diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md index 1972bb5d0f..3ccfc422c9 100644 --- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md +++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md @@ -28,7 +28,7 @@ Quando um {% data variables.product.prodname_oauth_app %} quiser identificar voc ## Acesso do {% data variables.product.prodname_oauth_app %} -{% data variables.product.prodname_oauth_apps %} can have *read* or *write* access to your {% data variables.product.product_name %} data. +{% data variables.product.prodname_oauth_apps %} pode ter acesso *a* ou acesso de *gravação* aos seus dados de {% data variables.product.product_name %}. - O **acesso de leitura** permite que um app apenas *observe* os dados. - O **acesso de gravação** permite que um app *altere* os dados. @@ -43,7 +43,7 @@ Quando um {% data variables.product.prodname_oauth_app %} quiser identificar voc Os *escopos* são grupos de permissões nomeados que um {% data variables.product.prodname_oauth_app %} pode solicitar para acessar dados públicos e privados. -Quando quiser usar um {% data variables.product.prodname_oauth_app %} que se integre ao {% data variables.product.product_name %}, esse app permitirá que você saiba qual tipo de acesso aos seus dados será necessário. Se você conceder acesso ao app, este poderá executar ações em seu nome, como ler ou modificar os dados. Por exemplo, se você desejar usar um app que solicite o escopo `user:email`, o app terá acesso somente leitura aos seus endereços de e-mail privados. For more information, see "[About scopes for {% data variables.product.prodname_oauth_apps %}](/apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps)." +Quando quiser usar um {% data variables.product.prodname_oauth_app %} que se integre ao {% data variables.product.product_name %}, esse app permitirá que você saiba qual tipo de acesso aos seus dados será necessário. Se você conceder acesso ao app, este poderá executar ações em seu nome, como ler ou modificar os dados. Por exemplo, se você desejar usar um app que solicite o escopo `user:email`, o app terá acesso somente leitura aos seus endereços de e-mail privados. Para obter mais informações, consulte "[Sobre escopos para {% data variables.product.prodname_oauth_apps %}](/apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps)". {% tip %} @@ -55,7 +55,7 @@ Quando quiser usar um {% data variables.product.prodname_oauth_app %} que se int ### Tipos de dados solicitados -{% data variables.product.prodname_oauth_apps %} can request several types of data. +{% data variables.product.prodname_oauth_apps %} pode solicitar vários tipos de dados. | Tipos de dados | Descrição | | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -71,30 +71,30 @@ Quando quiser usar um {% data variables.product.prodname_oauth_app %} que se int ## Solicitar permissões atualizadas -When {% data variables.product.prodname_oauth_apps %} request new access permissions, they will notify you of the differences between their current permissions and the new permissions. +Quando {% data variables.product.prodname_oauth_apps %} solicitar novas permissões de acesso, você será notificado sobre as diferenças entre as permissões atuais e as novas permissões. {% ifversion fpt %} -## {% data variables.product.prodname_oauth_apps %} and organizations +## {% data variables.product.prodname_oauth_apps %} e organizações Ao autorizar um {% data variables.product.prodname_oauth_app %} para sua conta de usuário pessoal, você também verá como a autorização vai afetar cada organização da qual você faz parte. - **Para organizações *com* restrições de acesso do {% data variables.product.prodname_oauth_app %}, você poderá solicitar que os administradores da organização aprovem o aplicativo para uso nessa organização.** Se a organização não aprovar o aplicativo, o aplicativo só poderá acessar os recursos públicos da organização. Se você for administrador de uma organização, você mesmo poderá [aprovar o aplicativo](/articles/approving-oauth-apps-for-your-organization). -- **For organizations *without* {% data variables.product.prodname_oauth_app %} access restrictions, the application will automatically be authorized for access to that organization's resources.** For this reason, you should be careful about which {% data variables.product.prodname_oauth_apps %} you approve for access to your personal account resources as well as any organization resources. +- **Para organizações *sem restrições de acesso de* {% data variables.product.prodname_oauth_app %} o aplicativo será autorizado automaticamente para acesso aos recursos da organização.** Por esta razão, você deve ter cuidado com {% data variables.product.prodname_oauth_apps %} você aprova para acessar os recursos da sua conta pessoal, bem como todos os recursos da organização. Se você pertence a alguma organização que force o logon único SAML, você deve ter uma sessão de SAML ativa para cada organização toda cada vez que autorizar um {% data variables.product.prodname_oauth_app %}. {% note %} -**Note:** If you are encountering errors authenticating to an organization that enforces SAML single sign-on, you may need to revoke the OAuth App from your [account settings page](https://github.com/settings/applications) and repeat the authentication flow to reauthorize the app. +**Observação:** Se você encontrar erros ao efetuar a autenticação em uma organização que impõe o logon único do SAML, talvez você precise revogar o aplicativo OAuth da página de configurações da sua [página de configurações da sua conta](https://github.com/settings/applications) e repetir o fluxo de autenticação para autorizar novamente o aplicativo. {% endnote %} ## Leia mais - "[Sobre restrições de acesso do {% data variables.product.prodname_oauth_app %}](/articles/about-oauth-app-access-restrictions)" -- "[Authorizing GitHub Apps](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-github-apps)" +- "[Autorizando aplicativos GitHub](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-github-apps)" - "[Suporte do {% data variables.product.prodname_marketplace %}](/articles/github-marketplace-support)" {% endif %} diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md index 308ca89383..c164ad133f 100644 --- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md +++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md @@ -38,7 +38,7 @@ Os aplicativos podem ter acesso de *leitura* ou *gravação* aos seus dados no { Os *escopos* são grupos nomeados de permissões que um aplicativo pode solicitar para acessar dados públicos e não públicos. -Quando você quiser usar um aplicativo de terceiro que se integre ao {% data variables.product.product_name %}, esse aplicativo permitirá que você saiba qual tipo de acesso aos seus dados será necessário. Se você conceder acesso ao aplicativo, este poderá executar ações em seu nome, como ler ou modificar os dados. Por exemplo, se você desejar usar um app que solicite o escopo `user:email`, o app terá acesso somente leitura aos seus endereços de e-mail privados. For more information, see "[About scopes for {% data variables.product.prodname_oauth_apps %}](/apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps)." +Quando você quiser usar um aplicativo de terceiro que se integre ao {% data variables.product.product_name %}, esse aplicativo permitirá que você saiba qual tipo de acesso aos seus dados será necessário. Se você conceder acesso ao aplicativo, este poderá executar ações em seu nome, como ler ou modificar os dados. Por exemplo, se você desejar usar um app que solicite o escopo `user:email`, o app terá acesso somente leitura aos seus endereços de e-mail privados. Para obter mais informações, consulte "[Sobre escopos para {% data variables.product.prodname_oauth_apps %}](/apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps)". {% tip %} 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 146a12c365..c225a6c68e 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 @@ -20,7 +20,7 @@ shortTitle: Criar um PAT {% note %} -**Note:** If you use {% data variables.product.prodname_cli %} to authenticate to {% data variables.product.product_name %} on the command line, you can skip generating a personal access token and authenticate via the web browser instead. For more information about authenticating with {% data variables.product.prodname_cli %}, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login). +**Observação:** Se você usar {% data variables.product.prodname_cli %} para efetuar a autenticação para {% data variables.product.product_name %} na linha de comando você poderá ignorar a geração de um token de acesso pessoal e efetuar a autenticação por meio da 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). {% endnote %} @@ -30,7 +30,7 @@ Os tokens de acesso pessoal (PATs) são uma alternativa para o uso de senhas par {% ifversion fpt %}{% data reusables.user_settings.removes-personal-access-tokens %}{% endif %} -A token with no assigned scopes can only access public information. Para usar seu token para acessar repositórios da linha de comando, selecione `repo`. For more information, see “[Available scopes](/apps/building-oauth-apps/scopes-for-oauth-apps#available-scopes)”. +Um token com nenhum escopo atribuído só pode acessar informações públicas. Para usar seu token para acessar repositórios da linha de comando, selecione `repo`. Para obter mais informações, consulte “[Escopos disponíveis](/apps/building-oauth-apps/scopes-for-oauth-apps#available-scopes). ## Criar um token @@ -38,9 +38,9 @@ A token with no assigned scopes can only access public information. Para usar se {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.developer_settings %} {% data reusables.user_settings.personal_access_tokens %} -4. Clique em **Generate new token** (Gerar novo token). ![Botão Generate new token (Gerar novo token)](/assets/images/help/settings/generate_new_token.png) +{% 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 %} -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 %} +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 %} ![Selecionar escopos do token](/assets/images/help/settings/token_scopes.gif) @@ -75,5 +75,5 @@ Em vez de inserir manualmente seu PAT para cada operação de HTTPS do Git, voc ## Leia mais -- "[About authentication to GitHub](/github/authenticating-to-github/about-authentication-to-github)"{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 %} -- "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %} +- "[Sobre a autenticação no GitHub](/github/authenticating-to-github/about-authentication-to-github)"{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 %} +- "[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/githubs-ssh-key-fingerprints.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md index 1e68155084..079b25648d 100644 --- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md +++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md @@ -19,11 +19,11 @@ Estas são as impressões digitais de chave pública de {% data variables.produc - `SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8` (RSA) -These keys will be supported beginning September 14, 2021: +Estas chaves serão compatíveis no início de 14 de setembro de 2021: - `SHA256:p2QAMXNIC1TJYWeIOttrVc98/R1BUFWu3/LiyKgUfQM` (ECDSA) - `SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU` (Ed25519) -This key will be sunset on November 16, 2021: +Essa chave será desativada em 16 de novembro de 2021: - `SHA256:br9IjFspm1vxR3iA35FWE+4VTyz1hYVLIE2t1/CeyWQ` (DSA) 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 63a3b1f351..189071f447 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 @@ -1,6 +1,6 @@ --- title: Remover dados confidenciais do repositório -intro: 'Se você fizer commit de dados confidenciais, como uma senha ou chave SSH em um repositório Git, poderá removê-los do histórico. To entirely remove unwanted files from a repository''s history you can use either the `git filter-repo` tool or the BFG Repo-Cleaner open source tool.' +intro: 'Se você fizer commit de dados confidenciais, como uma senha ou chave SSH em um repositório Git, poderá removê-los do histórico. Para remover completamente arquivos indesejados do histórico de um repositório, você pode usar a ferramenta `git filter-repo` ou a ferramenta de código aberto BFG Repo-Cleaner.' redirect_from: - /remove-sensitive-data/ - /removing-sensitive-data/ @@ -18,15 +18,15 @@ topics: shortTitle: Remover dados confidenciais --- -The `git filter-repo` tool and the BFG Repo-Cleaner rewrite your repository's history, which changes the SHAs for existing commits that you alter and any dependent commits. Os SHAs do commit alterados podem afetar as pull requests abertas no repositório. Recomendamos que você faça merge ou feche todas todas as pull requests abertas antes de remover os arquivos do repositório. +A ferramenta `git filter-repo` e o BFG Repo-Cleaner reescrevem o histórico do seu repositório, que muda os SHAs para os commits existentes que você altera e quaisquer commits dependentes. Os SHAs do commit alterados podem afetar as pull requests abertas no repositório. Recomendamos que você faça merge ou feche todas todas as pull requests abertas antes de remover os arquivos do repositório. -Você pode remover o arquivo com o commit mais recente com `git rm`. For information on removing a file that was added with the latest commit, see "[About large files on {% data variables.product.prodname_dotcom %}](/repositories/working-with-files/managing-large-files/about-large-files-on-github#removing-files-from-a-repositorys-history)." +Você pode remover o arquivo com o commit mais recente com `git rm`. Para obter informações sobre a remoção de um arquivo que foi adicionado com o commit mais recente, consulte "[Sobre arquivos grandes em {% data variables.product.prodname_dotcom %}](/repositories/working-with-files/managing-large-files/about-large-files-on-github#removing-files-from-a-repositorys-history)". {% warning %} -Este artigo explica como fazer commits com dados confidenciais que não podem ser acessados de nenhum branch ou tag no repositório do {% data variables.product.product_name %}. 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. 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 %}. +Este artigo explica como fazer commits com dados confidenciais que não podem ser acessados de nenhum branch ou tag no repositório do {% data variables.product.product_name %}. 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 %}. -**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! Se tiver feito commit de uma chave, crie outra. 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. +**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. {% endwarning %} @@ -58,21 +58,21 @@ $ git push --force Consulte as instruções completas de download e uso na documentação do [BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/). -### Using git filter-repo +### Usando arquivo git filter-repo {% warning %} -**Warning:** If you run `git filter-repo` after stashing changes, you won't be able to retrieve your changes with other stash commands. Before running `git filter-repo`, we recommend unstashing any changes you've made. Para desfazer o stash do último conjunto de alterações no qual você fez stash, execute `git stash show -p | git apply -R`. For more information, see [Git Tools - Stashing and Cleaning](https://git-scm.com/book/en/v2/Git-Tools-Stashing-and-Cleaning). +**Aviso:** se você executar `git filter-repo` após acumular as alterações, você não poderá recuperar suas alterações com outros comandos acumulados. Antes de executar `git filter-repo`, recomendamos cancelar a acumulação de todas as alterações que você fez. Para desfazer o stash do último conjunto de alterações no qual você fez stash, execute `git stash show -p | git apply -R`. Para obter mais informações, consulte [Ferramentas do Git - Acúmulo e limpeza](https://git-scm.com/book/en/v2/Git-Tools-Stashing-and-Cleaning). {% endwarning %} -To illustrate how `git filter-repo` works, we'll show you how to remove your file with sensitive data from the history of your repository and add it to `.gitignore` to ensure that it is not accidentally re-committed. +Para ilustrar como `git filter-repo` funciona, mostraremos como remover seu arquivo com dados confidenciais do histórico do repositório e adicioná-lo a `. itignore` para garantir que não se faça o commit novamente de forma acindelal. -1. Install the latest release of the [git filter-repo](https://github.com/newren/git-filter-repo) tool. You can install `git-filter-repo` manually or by using a package manager. For example, to install the tool with HomeBrew, use the `brew install` command. +1. Instale a versão mais recente da ferramenta [git filter-repo](https://github.com/newren/git-filter-repo). Você pode instalar `git-filter-repo` manualmente ou usando um gerenciador de pacotes. Por exemplo, para instalar a ferramenta com o HomeBrew, use o comando `brew install`. ``` brew install git-filter-repo ``` - For more information, see [*INSTALL.md*](https://github.com/newren/git-filter-repo/blob/main/INSTALL.md) in the `newren/git-filter-repo` repository. + Para obter mais informações, consulte [*INSTALL.md*](https://github.com/newren/git-filter-repo/blob/main/INSTALL.md) no repositório `newren/git-filter-repo`. 2. Se você ainda não tiver uma cópia local do repositório com dados confidenciais no histórico, [faça um clone do repositório](/articles/cloning-a-repository/) no computador local. ```shell @@ -91,7 +91,7 @@ To illustrate how `git filter-repo` works, we'll show you how to remove your fil 4. Execute o seguinte comando substituindo `PATH-TO-YOUR-FILE-WITH-SENSITIVE-DATA` pelo **caminho do arquivo que deseja remover, não apenas o nome do arquivo**. Esses argumentos vão: - Forçar o Git a processar, mas não fazer checkout, do histórico completo de cada branch e tag - Remover o arquivo especificado, bem como qualquer commit vazio gerado como resultado - - Remove some configurations, such as the remote URL, stored in the *.git/config* file. You may want to back up this file in advance for restoration later. + - Remova algumas configurações, como a URL remota, armazenada no arquivo *.git/config*. Você deverá fazer backup deste arquivo com antecedência para a restauração mais adiante. - **Sobrescrever as tags existentes** ```shell $ git filter-repo --invert-paths --path PATH-TO-YOUR-FILE-WITH-SENSITIVE-DATA @@ -99,7 +99,7 @@ To illustrate how `git filter-repo` works, we'll show you how to remove your fil New history written in 0.11 seconds; now repacking/cleaning... Repacking your repo and cleaning out old unneeded objects Enumerating objects: 210, done. - Counting objects: 100% (210/210), done. + Contando objetos: 100% (210/210), concluído. Delta compression using up to 12 threads Compressing objects: 100% (127/127), done. Writing objects: 100% (210/210), done. diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations.md index cdd2d4e252..87e59c15be 100644 --- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations.md +++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations.md @@ -15,19 +15,19 @@ topics: shortTitle: Integrações autorizadas --- -## Reviewing your authorized {% data variables.product.prodname_oauth_apps %} +## Revisar os seus {% data variables.product.prodname_oauth_apps %} autorizados {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.access_applications %} {% data reusables.user_settings.access_authorized_oauth_apps %} {% data reusables.user_settings.review-oauth-apps %} -## Reviewing your authorized {% data variables.product.prodname_github_apps %} +## Revisar os seus {% data variables.product.prodname_github_apps %} autorizados {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.access_applications %} -3. Click the **Authorized {% data variables.product.prodname_github_apps %}** tab. ![Authorized {% data variables.product.prodname_github_apps %} tab](/assets/images/help/settings/settings-authorized-github-apps-tab.png) -3. Review the {% data variables.product.prodname_github_apps %} that have access to your account. Para os aplicativos não reconhecidos ou desatualizados, clique em **Revoke** (Revogar). To revoke all {% data variables.product.prodname_github_apps %}, click **Revoke all**. ![Lista de {% data variables.product.prodname_github_app %} autorizado](/assets/images/help/settings/revoke-github-app.png) +3. Clique na aba **{% data variables.product.prodname_github_apps %} autorizado**. ![Aba {% data variables.product.prodname_github_apps %} autorizado](/assets/images/help/settings/settings-authorized-github-apps-tab.png) +3. Revise o {% data variables.product.prodname_github_apps %} que tem acesso à sua conta. Para os aplicativos não reconhecidos ou desatualizados, clique em **Revoke** (Revogar). Para revogar todos os {% data variables.product.prodname_github_apps %}, clique em **Revogar todos**. ![Lista de {% data variables.product.prodname_github_app %} autorizado](/assets/images/help/settings/revoke-github-app.png) ## Leia mais {% ifversion fpt %} 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 0e0bd5ee35..c640c90216 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 @@ -48,7 +48,7 @@ Os eventos listados no seu registro de segurança são acionados por suas açõe | [`espaços de código`](#codespaces-category-actions) | Contém todas as atividades relacionadas a {% data variables.product.prodname_codespaces %}. Para obter mais informações, consulte "[Sobre o {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces)". | | [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | Contém todas as atividades relacionadas à assinatura do Contrato de desenvolvedor do {% data variables.product.prodname_marketplace %}. | | [`marketplace_listing`](#marketplace_listing-category-actions) | Contém todas as atividades relacionadas aos aplicativos listados no {% data variables.product.prodname_marketplace %}.{% endif %} -| [`oauth_access`](#oauth_access-category-actions) | Contains all activities related to [{% data variables.product.prodname_oauth_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps) you've connected with.{% ifversion fpt %} +| [`oauth_access`](#oauth_access-category-actions) | Contém todas as atividades relacionadas aos [{% data variables.product.prodname_oauth_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps) com os quais você se conectou.{% ifversion fpt %} | [`payment_method`](#payment_method-category-actions) | Contém todas as atividades relacionadas ao pagamento da sua assinatura do {% data variables.product.prodname_dotcom %}.{% endif %} | [`profile_picture`](#profile_picture-category-actions) | Contém todas as atividades relacionadas à imagem do seu perfil. | | [`project`](#project-category-actions) | Contém todas as atividades relacionadas aos quadros de projeto. | @@ -117,12 +117,12 @@ Uma visão geral de algumas das ações mais comuns que são registradas como ev {% endif %} -### `oauth_authorization` category actions +### Ações da categoria `oauth_authorization` -| Ação | Descrição | -| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `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 %} and when [authorizations are revoked or expire](/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` | 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 %} 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 %} {% ifversion fpt %} 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 7bbba2a3b0..651dd1d6df 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 @@ -1,6 +1,6 @@ --- -title: Token expiration and revocation -intro: 'Your tokens can expire and can also be revoked by you, applications you have authorized, and {% data variables.product.product_name %} itself.' +title: Vencimento e revogação de token +intro: 'Seus tokens podem vencer e também podem ser revogados por você, pelos aplicativos que você autorizou e pelo próprio {% data variables.product.product_name %}.' versions: fpt: '*' ghes: '*' @@ -8,55 +8,55 @@ versions: topics: - Identity - Access management -shortTitle: Token expiration +shortTitle: Vencimento do token 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 %}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. +Se um token {% ifversion fpt or ghae-issue-4374 or ghes > 3.2 %}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. -This article explains the possible reasons your {% data variables.product.product_name %} token might be revoked or expire. +Este artigo explica os possíveis motivos pelos quais seu token {% data variables.product.product_name %} pode ser revogado ou vencido. {% note %} -**Note:** When a personal access token or OAuth token expires or is revoked, you may see an `oauth_authorization.destroy` action in your security log. Para obter mais informações, consulte "[Revisar o log de segurança](/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-security-log)." +**Observação:** Quando um token de acesso pessoal ou token OAuth vence ou é revogado, você pode ver uma ação de `oauth_authorization.destroy` no seu log de segurança. Para obter mais informações, consulte "[Revisar o log de segurança](/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-security-log)." {% endnote %} {% ifversion fpt or ghae-issue-4374 or ghes > 3.2 %} -## Token revoked after reaching its expiration date +## Token revogado após atingir sua data de validade -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. 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)." +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)." {% endif %} {% ifversion fpt %} -## Token revoked when pushed to a public repository or public gist +## Token revogado quando enviado por push para um repositório público ou gist público -If a valid OAuth token, {% data variables.product.prodname_github_app %} token, or personal access token is pushed to a public repository or public gist, the token will be automatically revoked. +Se um token do OAuth válido, um token de {% data variables.product.prodname_github_app %} ou o token de acesso pessoal é receber push para um repositório público ou gist, o token será revogado automaticamente. -OAuth tokens and personal access tokens pushed to public repositories and public gists will only be revoked if the token has scopes. +Os tokens OAuth e os tokens de acesso pessoal enviados para repositórios públicos e gists públicos só serão revogados se o token tiver escopos. {% endif %} {% ifversion fpt %} -## Token expired due to lack of use +## Token vencido devido à falta de uso -{% data variables.product.product_name %} will automatically revoke an OAuth token or personal access token when the token hasn't been used in one year. +{% data variables.product.product_name %} irá revogar automaticamente um token OAuth ou um token de acesso pessoal quando o token não for usado em um ano. {% endif %} -## Token revoked by the user +## Token revogado pelo usuário -You can revoke your authorization of a {% data variables.product.prodname_github_app %} or {% data variables.product.prodname_oauth_app %} from your account settings which will revoke any tokens associated with the app. For more information, see "[Reviewing your authorized integrations](/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations)" and "[Reviewing your authorized applications (OAuth)](/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-authorized-applications-oauth)." +Você pode revogar a sua autorização de um {% data variables.product.prodname_github_app %} ou {% data variables.product.prodname_oauth_app %} a partir das configurações da sua conta que irão revogar todos tokens associados ao aplicativo. Para obter mais informações, consulte "[Revendo suas integrações autorizadas](/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations)" e "[Revendo seus aplicativos autorizados (OAuth)](/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-authorized-applications-oauth)". -Once an authorization is revoked, any tokens associated with the authorization will be revoked as well. To re-authorize an application, follow the instructions from the third-party application or website to connect your {% data variables.product.product_name %} account again. +Depois que uma autorização for revogada, todos os tokens associados à autorização também serão revogados. Para autorizar novamente um aplicativo, siga as instruções do aplicativo ou site de terceiros para conectar sua conta de {% data variables.product.product_name %} novamente. -## Token revoked by the {% data variables.product.prodname_oauth_app %} +## Token revogado por {% data variables.product.prodname_oauth_app %} -The owner of an {% data variables.product.prodname_oauth_app %} can revoke an account's authorization of their app, this will also revoke any tokens associated with the authorization. For more information about revoking authorizations of your OAuth app, see "[Delete an app authorization](/rest/reference/apps#delete-an-app-authorization)." +O proprietário de um {% data variables.product.prodname_oauth_app %} pode revogar a autorização de uma conta do seu aplicativo. Isso também irá revogar todos os tokens associados à autorização. Para obter mais informações sobre a revogação de autorizações do seu aplicativo OAuth, consulte[Excluir uma autorização de aplicativo](/rest/reference/apps#delete-an-app-authorization). " -## Token revoked due to excess of tokens for an {% data variables.product.prodname_oauth_app %} with the same scope +## Token revogado devido ao excesso de tokens para um {% data variables.product.prodname_oauth_app %} com o mesmo escopo {% data reusables.apps.oauth-token-limit %} -## User token revoked due to {% data variables.product.prodname_github_app %} configuration +## Token de usuário revogado devido à configuração de {% data variables.product.prodname_github_app %} -User-to-server tokens created by a {% data variables.product.prodname_github_app %} will expire after eight hours by default. Owners of {% data variables.product.prodname_github_apps %} can configure their apps so that user-to-server tokens do not expire. For more information about changing how your {% data variables.product.prodname_dotcom %} App's user-to-server tokens behave, see "[Activating optional features for apps](/developers/apps/getting-started-with-apps/activating-optional-features-for-apps)." +Por padrão, os tokens de usuário para servidor criados por um {% data variables.product.prodname_github_app %} vencerão após oito horas. Os proprietários de {% data variables.product.prodname_github_apps %} podem configurar seus aplicativos para que os tokens de usuário para servidor não vençam. Para obter mais informações sobre como se comportam os tokens de usuário para servidor do seu aplicativo de {% data variables.product.prodname_dotcom %}, consulte "[Habilitando as funcionalidaes opcionais para os aplicativos](/developers/apps/getting-started-with-apps/activating-optional-features-for-apps). " 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 24e7b01999..caedc42b49 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 @@ -30,7 +30,7 @@ shortTitle: Atualizar credenciais de acesso {% tip %} -To avoid losing your password in the future, we suggest using a secure password manager, like [LastPass](https://lastpass.com/) or [1Password](https://1password.com/). +Para evitar perder a sua senha no futuro, sugerimos o uso de um gerenciador de senhas seguro, como [LastPass](https://lastpass.com/) ou [1Password](https://1password.com/). {% endtip %} diff --git a/translations/pt-BR/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md b/translations/pt-BR/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md index b9fdada95c..1e75765677 100644 --- a/translations/pt-BR/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md +++ b/translations/pt-BR/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md @@ -86,7 +86,7 @@ Não é preciso fazer upload da chave pública no {% data variables.product.prod {% ifversion fpt %} ## Verificação de assinatura para bots -Organizations and {% data variables.product.prodname_github_apps %} that require commit signing can use bots to sign commits. Se um commit ou uma tag tiver uma assinatura de bot que possa ser verificada de maneira criptográfica, o {% data variables.product.product_name %} marcará o commit ou tag como verificado. +As organizações e {% data variables.product.prodname_github_apps %} que exigem a assinatura de commit podem usar bots para assinar commits. Se um commit ou uma tag tiver uma assinatura de bot que possa ser verificada de maneira criptográfica, o {% data variables.product.product_name %} marcará o commit ou tag como verificado. A verificação de assinatura para bots somente funcionará se a solicitação for verificada e autenticada como o {% data variables.product.prodname_github_app %} ou bot e se não tiver informações de autor personalizadas, informações de committer personalizadas e nenhuma informação de assinatura personalizada, como API de commits. {% endif %} diff --git a/translations/pt-BR/content/authentication/managing-commit-signature-verification/displaying-verification-statuses-for-all-of-your-commits.md b/translations/pt-BR/content/authentication/managing-commit-signature-verification/displaying-verification-statuses-for-all-of-your-commits.md index 90713a3d65..5c29035929 100644 --- a/translations/pt-BR/content/authentication/managing-commit-signature-verification/displaying-verification-statuses-for-all-of-your-commits.md +++ b/translations/pt-BR/content/authentication/managing-commit-signature-verification/displaying-verification-statuses-for-all-of-your-commits.md @@ -18,7 +18,7 @@ redirect_from: Ao trabalhar localmente no seu computador, o Git permite que você defina o autor das suas alterações e a identidade do autor do autor do autor do committer. Isso torna potencialmente difícil para outras pessoas estarem confiantes de que os commits e tags que você cria foram realmente criados por você. Para ajudar a resolver esse problema, você pode assinar seus commits e tags. Para obter mais informações, consulte "[Assinar commits](/github/authenticating-to-github/signing-commits)" e "[Assinar tags](/github/authenticating-to-github/signing-tags)". {% data variables.product.prodname_dotcom %} marca commits e tags assinadas com um status de verificação. -Por padrão, os commits e tags são marcados como "Verificados" se forem assinadas com uma chave GPG ou S/MIME que foi verificada com sucesso. If a commit or tag has a signature that can't be verified by {% data variables.product.prodname_dotcom %}, we mark the commit or tag "Unverified." Em todos os outros casos, não se exibe nenhum status de verificação. +Por padrão, os commits e tags são marcados como "Verificados" se forem assinadas com uma chave GPG ou S/MIME que foi verificada com sucesso. Se um commit ou tag tiver uma assinatura que não pode ser verificada por {% data variables.product.prodname_dotcom %}, nós marcaremos o commit ou a tag como "não verificado". Em todos os outros casos, não se exibe nenhum status de verificação. No entanto, você pode dar a outros usuários maior confiança na identidade atribuída aos seus commits e tags, habilitando o modo vigilante nas configurações do seu {% data variables.product.prodname_dotcom %} Com o modo vigilante habilitado, todos os seus commits e tags são marcados com um de três status de verificação. @@ -26,7 +26,7 @@ No entanto, você pode dar a outros usuários maior confiança na identidade atr {% data reusables.identity-and-permissions.vigilant-mode-verification-statuses %} -You should only enable vigilant mode if you sign all of your commits and tags and use an email address that is verified for your account on {% data variables.product.product_name %} as your committer email address. Depois de habilitar este modo, todos commits ou tags não assinados que você gerar localmente e fizer push em {% data variables.product.prodname_dotcom %} serão marcados como "não verificados". +Você só deve habilitar o modo vigilante se assinar todos os seus commits e tags e usar um endereço de e-mail que seja verificado para a sua conta no {% data variables.product.product_name %} como o seu endereço de e-mail do committer. Depois de habilitar este modo, todos commits ou tags não assinados que você gerar localmente e fizer push em {% data variables.product.prodname_dotcom %} serão marcados como "não verificados". {% data reusables.identity-and-permissions.verification-status-check %} diff --git a/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md b/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md index 0bd186ee21..d0b2542961 100644 --- a/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md +++ b/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md @@ -75,33 +75,6 @@ Você pode usar um número de fallback, independentemente de ter configurado a a Após a configuração, o dispositivo de backup receberá um SMS de confirmação. -## Adicionar um método de autenticação de fallback com recuperação de contas em outro lugar - -Você pode gerar uma credencial extra de autenticação para sua conta e armazená-la com um provedor de recuperação parceiro. - -### Sobre recuperação de contas em outro lugar - -Com a recuperação de contas em outro lugar, é possível adicionar um fator de segurança extra à sua conta do {% data variables.product.product_name %} para o caso de perda do acesso ao método de autenticação de dois fatores ou aos códigos de recuperação. - -A recuperação de contas em outro lugar permite associar a sua conta do {% data variables.product.product_name %} à sua conta do Facebook. É possível armazenar uma credencial de autenticação na forma de um _token de recuperação de conta_ para sua conta do {% data variables.product.product_name %} com o Facebook. - -Se você perder o acesso à sua conta do {% data variables.product.product_name %} porque não tem mais acesso ao método de autenticação de dois fatores nem aos códigos de recuperação, será possível recuperar seu token de recuperação de conta com o provedor de recuperação para ajudar a provar que você é o proprietário da sua conta no {% data variables.product.product_name %}. - -Depois de recuperar o token, o {% data variables.contact.contact_support %} pode desabilitar a autenticação de dois fatores da sua conta. Em seguida, você pode fornecer ou redefinir a senha para voltar a ter acesso à sua conta. - -Quando você gera ou recupera um token de recuperação de conta, um evento é adicionado ao log de auditoria da sua conta. Para obter mais informações, consulte "[Revisar o log de segurança](/articles/reviewing-your-security-log)." - -### Gerar e armazenar um token de recuperação de conta - -Você pode gerar um token de recuperação de conta e armazená-lo com um provedor de recuperação parceiro. - -1. Entre na sua conta do Facebook e retorne para o {% data variables.product.product_name %}. -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.security %} -4. Para gerar um token, em "Recovery tokens" (Tokens de recuperação), clique em **Store new token** (Armazenar novo token). ![Botão para armazenar um novo token de recuperação](/assets/images/help/settings/store-new-recovery-token.png) -5. Leia as informações sobre tokens de recuperação de conta e clique em **Connect with https://www.facebook.com** (Conectar com https://www.facebook.com). ![Botão para conectar um token de recuperação com o Facebook](/assets/images/help/settings/connect-recovery-token-with-facebook.png) -6. Depois que você for redirecionado para o Facebook, leia as informações sobre como ativar a recuperação da conta com o Facebook antes de clicar em **Save as [_YOUR NAME_]** (Salvar como [SEU NOME]). (Se vários tokens forem salvos em um curto intervalo de tempo, o Facebook poderá ignorar essa etapa de confirmação depois que você salvar o primeiro token.) ![Página do Facebook com botão para ativar recuperação da conta](/assets/images/help/settings/security-turn-on-rae-facebook.png) - {% endif %} ## Leia mais diff --git a/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md b/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md index afccff4a26..5a2ea5ad89 100644 --- a/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md +++ b/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md @@ -28,6 +28,12 @@ Você pode configurar a autenticação de dois fatores usando um app móvel{% if {% endwarning %} +{% ifversion fpt %} + +Se você for um integrante de um {% data variables.product.prodname_emu_enterprise %}, você não poderá configurar a 2FA para sua conta de {% data variables.product.prodname_managed_user %}. A 2FA deve ser configurado por meio do seu provedor de identidade. + +{% endif %} + ## Configurar a autenticação de dois fatores usando um app móvel TOTP Um aplicativo de senhas avulsas por tempo limitado (TOTP, Time-based One-Time Password) gera automaticamente um código de autenticação que é alterado após um determinado período. É recomendável usar apps TOTP baseados na nuvem, como: diff --git a/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/countries-where-sms-authentication-is-supported.md b/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/countries-where-sms-authentication-is-supported.md index d01245461d..a85fd98d4c 100644 --- a/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/countries-where-sms-authentication-is-supported.md +++ b/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/countries-where-sms-authentication-is-supported.md @@ -124,7 +124,7 @@ Se seu país não estiver nesta lista, isso significa que, no momento, não pode
  • Tanzânia
  • Togo
  • Trinidade e Tobago
    • -
  • Turkey
    • +
  • Turquia
  • Ilhas Turks e Caicos
  • Uganda
  • Ucrânia
    • diff --git a/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md b/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md index b830de6cbd..0d0537cdbd 100644 --- a/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md +++ b/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md @@ -71,6 +71,12 @@ Você pode usar as suas credenciais de autenticação de dois fatores ou os cód ## Autenticar com um token de recuperação de conta +{% warning %} + +**Aviso:** Os tokens de recuperação de conta estão obsoletos e serão desabilitados em **de 1 de dezembro de 2021 de**. Certifique-se de ter configurado outros métodos de recuperação de dois fatores. Para obter mais informações, consulte "[Configurando métodos de recuperação de autenticação de dois fatores](/articles/configuring-two-factor-authentication-recovery-methods)". + +{% endwarning %} + Em caso de perda de acesso aos métodos de autenticação de dois fatores de sua conta {% data variables.product.product_name %}, é possível acessar seu token de recuperação de conta de um fornecedor de recuperação parceiro e solicitar ao Suporte do {% data variables.product.prodname_dotcom %} para verificá-lo. Se você não tiver acesso aos seus métodos de autenticação de dois fatores ou códigos de recuperação e tiver armazenado um token de recuperação de conta no Facebook usando a recuperação de contas em outro lugar, pode ser que você consiga usar seu token para recuperar o acesso à sua conta. diff --git a/translations/pt-BR/content/authentication/troubleshooting-ssh/error-key-already-in-use.md b/translations/pt-BR/content/authentication/troubleshooting-ssh/error-key-already-in-use.md index 88166bbf45..b601cd594e 100644 --- a/translations/pt-BR/content/authentication/troubleshooting-ssh/error-key-already-in-use.md +++ b/translations/pt-BR/content/authentication/troubleshooting-ssh/error-key-already-in-use.md @@ -27,7 +27,7 @@ $ ssh -T -ai ~/.ssh/id_rsa git@{% data variables.command_line.codeblock O *username* na resposta é a conta do {% data variables.product.product_name %} a que a chave está vinculada no momento. Se a resposta for parecida com "username/repo", a chave foi vinculada a um repositório como [*chave de implantação*](/guides/managing-deploy-keys#deploy-keys). -To force SSH to use only the key provided on the command line, use `-o` to add the `IdentitiesOnly=yes` option: +Para forçar o SSH a usar apenas a chave fornecida na linha de comando, use `-o` para adicionar a opção `IdentitiesOnly=yes`: ```shell $ ssh -v -o "IdentitiesOnly=yes" -i ~/.ssh/id_rsa git@{% data variables.command_line.codeblock %} diff --git a/translations/pt-BR/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md b/translations/pt-BR/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md index a7da135c2b..71c1e4173f 100644 --- a/translations/pt-BR/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md +++ b/translations/pt-BR/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md @@ -30,15 +30,15 @@ Se deu certo, ótimo! Caso contrário, [siga nosso guia para solução de proble ## Habilitar conexões SSH por HTTPS -If you are able to SSH into `git@ssh.{% data variables.command_line.backticks %}` over port 443, you can override your SSH settings to force any connection to {% data variables.product.product_location %} to run through that server and port. +Se você conseguir fazer SSH para `git@ssh.{% data variables.command_line.backticks %}` por meio da porta 443, você poderá substituir as configurações SSH para forçar qualquer conexão ao {% data variables.product.product_location %} a ser executada nesse servidor e nessa porta. Para definir isso na configuração SSH, edite o arquivo em `~/.ssh/config` e adicione esta seção: ``` Host {% data variables.command_line.codeblock %} Hostname ssh.{% data variables.command_line.codeblock %} -Port 443 -User git +Porta 443 +Usuário do Git ``` Para testar se funciona, conecte-se mais uma vez ao {% data variables.product.product_location %}: diff --git a/translations/pt-BR/content/billing/index.md b/translations/pt-BR/content/billing/index.md index 7192f648ad..32f516f9e2 100644 --- a/translations/pt-BR/content/billing/index.md +++ b/translations/pt-BR/content/billing/index.md @@ -1,7 +1,7 @@ --- -title: Billing and payments for GitHub +title: Cobrança e pagamentos para o GitHub shortTitle: Faturamento e pagamentos -intro: '{% ifversion fpt %}{% data variables.product.product_name %} offers free and paid products for every account. You can upgrade, downgrade, and view pending changes to your account''s subscription at any time.{% elsif ghes or ghae %}{% data variables.product.company_short %} bills for your enterprise members'' {% ifversion ghae %}usage of {% data variables.product.product_name %}{% elsif ghes %} licence seats for {% data variables.product.product_name %}{% ifversion ghes > 3.0 %} and any additional services that you purchase{% endif %}{% endif %}.{% endif %}' +intro: '{% ifversion fpt %}{% data variables.product.product_name %} oferece produtos grátis e pagos para cada conta. Você pode atualizar, fazer o downgrade e visualizar as alterações pendentes da assinatura da sua conta a qualquer momento.{% elsif ghes or ghae %}{% data variables.product.company_short %} cobranças para os integrantes da sua empresa {% ifversion ghae %}uso de {% data variables.product.product_name %}{% elsif ghes %} estações de licença para {% data variables.product.product_name %}{% ifversion ghes > 3.0 %} e quaisquer serviços adicionais que você comprar{% endif %}{% endif %}.{% endif %}' redirect_from: - /github/setting-up-and-managing-billing-and-payments-on-github - /categories/setting-up-and-managing-billing-and-payments-on-github 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 840efaeb48..6a2ac1f30a 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 @@ -24,7 +24,7 @@ Se você comprou {% data variables.product.prodname_enterprise %} por meio de um Os minutos são reiniciados todos os meses, mas o uso do armazenamento não. -### Included storage and minutes +### Armazenamento e minutos incluídos | Produto | Armazenamento | Minutos (por mês) | | ------------------------------------------------------------------- | ------------- | ----------------- | @@ -36,7 +36,7 @@ Os minutos são reiniciados todos os meses, mas o uso do armazenamento não. Os trabalhos que são executados em Windows e macOS runners que o {% data variables.product.prodname_dotcom %} hospeda consomem minutos na proporção de 2 a 10 vezes a taxa que os trabalhos em Linux consomem. Por exemplo, usar 1.000 minutos do Windows consumiria 2.000 minutos incluídos em sua conta. O uso de 1.000 minutos no macOS consumiria 10.000 minutos incluídos em sua conta. -### Minute multipliers +### Multiplicadores de minutos | Sistema operacional | Multiplicador de minutos | | ------------------- | ------------------------ | @@ -46,7 +46,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)." - 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 %} arredonda os minutos que cada trabalho usa até o minuto mais próximo. + 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. {% note %} @@ -54,9 +54,9 @@ O armazenamento usado por um repositório é o armazenamento total usado por art {% endnote %} -### Per-minute rates +### Taxa por minuto -| Sistema operacional | Per-minute rate (USD) | +| Sistema operacional | Taxa por minuto (USD) | | ------------------- | --------------------- | | Linux | $0,008 | | macOS | $0,08 | @@ -68,19 +68,21 @@ O número de trabalhos que você pode executar simultaneamente em todos os repos ## Calculando minutos e gastos de armazenamento +{% data reusables.dotcom_billing.pricing_cal %} + No final do mês, {% data variables.product.prodname_dotcom %} calcula o custo de minutos e armazenamento usado sobre o valor incluído em sua conta. -### Sample minutes cost calculation +### Cálculo de custo de amostra em minutos -For example, if your organization uses {% data variables.product.prodname_team %} and allows unlimited spending, using 15,000 minutes could have a total storage and minute overage cost of $56 USD, depending on the operating systems used to run jobs. +Por exemplo, se sua organização usa {% data variables.product.prodname_team %} e permite gastos ilimitados, usando 15.000 minutos, poderia ter um custo total de armazenamento e custo médio de minuto de US$ 56,00, dependendo dos sistemas operacionais usados para executar trabalhos. -- 5,000 (3,000 Linux and 2,000 Windows) minutes = $56 USD ($24 USD + $32 USD). - - 3,000 Linux minutes at $0.008 USD per minute = $24 USD. - - 2,000 Windows minutes at $0.016 USD per minute = $32 USD. +- 5.000 (3.000 Linux e 2.000 Windows) minutos = US$ 56 (US$ 24 + US$ 32). + - 3.000 minutos de Linux por US$ 0,008 por minuto = US$ 24. + - 2.000 Windows minutos com US$ 0,016 por minuto = US$ 32. O {% data variables.product.prodname_dotcom %} calcula seu uso do armazenamento para cada mês com base no uso por hora durante aquele mês. -### Sample storage cost calculation +### Cálculo de custo de armazenamento Por exemplo, se você usar 3 GB de armazenamento por 10 dias de março e 12 GB durante 21 dias de março, seu uso de armazenamento seria: diff --git a/translations/pt-BR/content/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md b/translations/pt-BR/content/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md index 4968c6e852..2bf79abbcf 100644 --- a/translations/pt-BR/content/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md +++ b/translations/pt-BR/content/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md @@ -62,5 +62,5 @@ Proprietários de organizações e gestores de faturamento podem gerenciar o lim {% data reusables.dotcom_billing.update-spending-limit %} -## Managing usage and spending limit email notifications +## Gerenciamento de notificações por e-mail e limite de gastos {% data reusables.billing.email-notifications %} diff --git a/translations/pt-BR/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md b/translations/pt-BR/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md index 3560e4ce27..06a834b6c0 100644 --- a/translations/pt-BR/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md +++ b/translations/pt-BR/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md @@ -1,6 +1,6 @@ --- -title: About billing for GitHub Advanced Security -intro: 'If you want to use {% data variables.product.prodname_GH_advanced_security %} features{% ifversion fpt %} in a private or internal repository{% endif %}, you need a license.{% ifversion fpt %} These features are available free of charge for public repositories on {% data variables.product.prodname_dotcom_the_website %}.{% endif %}' +title: Sobre a cobrança para o GitHub Advanced Security +intro: 'Caso você queira usar {% data variables.product.prodname_GH_advanced_security %} funcionalidades{% ifversion fpt %} em um repositório privado ou interno{% endif %}, você precisará de uma licença.{% ifversion fpt %} Essas funcionalidades estão disponíveis gratuitamente para repositórios públicos em {% data variables.product.prodname_dotcom_the_website %}.{% endif %}' product: '{% data reusables.gated-features.ghas %}' redirect_from: - /admin/advanced-security/about-licensing-for-github-advanced-security @@ -15,7 +15,7 @@ topics: - Advanced Security - Enterprise - Licensing -shortTitle: Advanced Security billing +shortTitle: Cobrança da segurança avançada --- ## Sobre a cobrança do {% data variables.product.prodname_GH_advanced_security %} @@ -36,7 +36,7 @@ Você pode disponibilizar funcionalidades adicionais para segurança de código, {% endif %} -To discuss licensing {% data variables.product.prodname_GH_advanced_security %} for your enterprise, contact {% data variables.contact.contact_enterprise_sales %}. +Para discutir licenciamento de {% data variables.product.prodname_GH_advanced_security %} para a sua empresa, entre em contato com {% data variables.contact.contact_enterprise_sales %}. ## Sobre os números do committer para {% data variables.product.prodname_GH_advanced_security %} @@ -48,17 +48,17 @@ To discuss licensing {% data variables.product.prodname_GH_advanced_security %} {% endif %} -É possível aplicar políticas que permitam ou não o uso de {% data variables.product.prodname_advanced_security %} por parte de organizações pertencentes à conta corporativa. For more information, see "{% ifversion ghes %}[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise){% elsif fpt or ghae %}[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise-account){% endif %}." +É possível aplicar políticas que permitam ou não o uso de {% data variables.product.prodname_advanced_security %} por parte de organizações pertencentes à conta corporativa. Para obter mais informações, consulte "{% ifversion ghes %}[Aplicando políticas para {% data variables.product.prodname_advanced_security %} na sua empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise){% elsif fpt or ghae %}[Aplicando políticas para {% data variables.product.prodname_advanced_security %} na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise-account){% endif %}." {% ifversion fpt or ghes %} -For more information on viewing license usage, see "[Viewing your {% data variables.product.prodname_GH_advanced_security %} usage](/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage)." +Para obter mais informações sobre a visualização do uso da licença, consulte "[Visualizar o seu uso de {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage)". {% endif %} -## Calculating committer spending +## Calculando gastos do committer -The following example timeline demonstrates the events during a month that affect billing for {% data variables.product.prodname_GH_advanced_security %} in an enterprise. For each month, you will find events, the total committer count, and the total number of committers that {% data variables.product.company_short %} would bill for. +A linha do tempo a seguir demonstra os eventos ao longo de um mês que afetam a cobrança de {% data variables.product.prodname_GH_advanced_security %} em uma empresa. Para cada mês, você encontrará os eventos, a contagem total do committer e o número total de committers que {% data variables.product.company_short %} cobraria. @@ -67,25 +67,25 @@ The following example timeline demonstrates the events during a month that affec
    - Events during the month + Eventos durante o mês - Total committer count + Contagem total do committer - Committers billed for the month + Committers cobrados no mês
    - August 1 + 1 de agosto - A member of your enterprise enables {% data variables.product.prodname_GH_advanced_security %} for repository X. Repository X has 50 committers over the past 90 days. + Um membro da sua empresa habilita {% data variables.product.prodname_GH_advanced_security %} para o repositório X. O repositório X tem 50 committers nos últimos 90 dias. @@ -99,11 +99,11 @@ The following example timeline demonstrates the events during a month that affec
    - September 5 + 5 de setembro - Developer A leaves the team working on repository X. Developer A's contributions continue to count for 90 days. + Desenvolvedor A deixa a equipe que trabalha no repositório X. As contribuições do desenvolvedor A continuam sendo contabilizadas por 90 dias. @@ -117,11 +117,11 @@ The following example timeline demonstrates the events during a month that affec
    - September 8 + 8 de setembro - Developer B pushes a commit to repository X for the first time. Developer B's usage is pro-rated, because the developer began contributing to repository X partway through the month. + Desenvolvedor B faz push de um commit para o repositório X pela primeira vez. O uso do desenvolvedor B é pró-rateado, porque o desenvolvedor começou a contribuir para o repositório X quando o mês já havia começado. @@ -135,11 +135,11 @@ The following example timeline demonstrates the events during a month that affec
    - October and November + Outubro e novembro - Developer A's contributions to repository X continue to count because the contributions were within the past 90 days. {% data variables.product.company_short %} now bills for developer B for the entire month because developer B now has contributions within the past 90 days. + As contribuições do desenvolvedor A para o repositório X continuam sendo contabilizada, pois foram realizadas nos últimos 90 dias. {% data variables.product.company_short %} agora faz a cobrança do desenvolvedor B referente a todo o mês porque o desenvolvedor B agora tem contribuições nos últimos 90 dias. @@ -153,11 +153,11 @@ The following example timeline demonstrates the events during a month that affec
    - December 4 + 4 de dezembro - 90 days have passed since developer A's last contribution to repository _X. The 90 days lapsed after December started, so {% data variables.product.company_short %} bills for developer A for the entire month. + Passaram-se 90 dias desde a última contribuição do desenvolvedor A para o repositório _X. Passaram-se 90 dias após o início de dezembro. Portanto, {% data variables.product.company_short %} irá efetuar a cobrança do mês inteiro para o desenvolvedor A. @@ -171,11 +171,11 @@ The following example timeline demonstrates the events during a month that affec
    - December 11 + 11 de dezembro - Developer C joins the company and pushes a commit to repository X for the first time. Developer C's usage is pro-rated at 70% for 21 out of 30 days. + O desenvolvedor C junta-se à empresa e faz push de um commit para o repositório X pela primeira vez. O uso do desenvolvedor C é pró-rateado em 70% por 21 dias no total de 30. @@ -189,11 +189,11 @@ The following example timeline demonstrates the events during a month that affec
    - January + Janeiro - {% data variables.product.company_short %} no longer bills for developer A. {% data variables.product.company_short %} bills for developer C for the entire month. + {% data variables.product.company_short %} não mais efetua a cobrança para o desenvolvedor A. {% data variables.product.company_short %} efetua a cobrança para desenvolvedor C para todo o mês. @@ -207,11 +207,11 @@ The following example timeline demonstrates the events during a month that affec
    - February 15 + 15 de fevereiro - A member of your enterprise disables {% data variables.product.prodname_GH_advanced_security %} for repository X. The 51 contributors to repository X do not work in any other repositories with {% data variables.product.prodname_GH_advanced_security %}. {% data variables.product.company_short %} bills for the developers' usage in repository X for February. + Um membro da sua empresa desabilita {% data variables.product.prodname_GH_advanced_security %} para o repositório X. Os 51 contribuidores do repositório X não trabalham juntos em nenhum outro repositório com {% data variables.product.prodname_GH_advanced_security %}. {% data variables.product.company_short %} efetua a cobrança para o uso dos desenvolvedores no repositório X para fevereiro. @@ -225,11 +225,11 @@ The following example timeline demonstrates the events during a month that affec
    - March + Março - No repository owned by your enterprise has {% data variables.product.prodname_GH_advanced_security %} enabled. + Nenhum repositório pertencente à sua empresa tem {% data variables.product.prodname_GH_advanced_security %} habilitado. @@ -242,6 +242,6 @@ The following example timeline demonstrates the events during a month that affec
    -## Getting the most out of {% data variables.product.prodname_GH_advanced_security %} +## Aproveitando o máximo de {% data variables.product.prodname_GH_advanced_security %} {% data reusables.advanced-security.getting-the-most-from-your-license %} diff --git a/translations/pt-BR/content/billing/managing-billing-for-github-advanced-security/index.md b/translations/pt-BR/content/billing/managing-billing-for-github-advanced-security/index.md index 6b307f1a5a..346c9809e8 100644 --- a/translations/pt-BR/content/billing/managing-billing-for-github-advanced-security/index.md +++ b/translations/pt-BR/content/billing/managing-billing-for-github-advanced-security/index.md @@ -1,5 +1,5 @@ --- -title: Managing billing for GitHub Advanced Security +title: Gerenciando a cobrança para o GitHub Advanced Security shortTitle: Segurança Avançada GitHub intro: 'Você pode visualizar e gerenciar seu uso de estações em uma licença para {% data variables.product.prodname_advanced_security %}.' product: '{% data reusables.gated-features.ghas %}' diff --git a/translations/pt-BR/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md b/translations/pt-BR/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md index 7f73bb201b..7a28543b98 100644 --- a/translations/pt-BR/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md +++ b/translations/pt-BR/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md @@ -1,6 +1,6 @@ --- title: Visualizar o seu uso do GitHub Advanced Security -intro: 'You can view usage of {% data variables.product.prodname_GH_advanced_security %} for your enterprise.' +intro: 'Você pode ver o uso de {% data variables.product.prodname_GH_advanced_security %} para a sua empresa.' permissions: 'Enterprise owners can view usage for {% data variables.product.prodname_GH_advanced_security %}.' product: '{% data reusables.gated-features.ghas %}' redirect_from: @@ -19,7 +19,7 @@ topics: shortTitle: Visualizar o uso avançado de segurança --- -## About licenses for {% data variables.product.prodname_GH_advanced_security %} +## Sobre as licenças para {% data variables.product.prodname_GH_advanced_security %} {% data reusables.advanced-security.about-ghas-license-seats %} Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)". @@ -32,7 +32,7 @@ Você pode verificar quantas estações a sua licença inclui e quantas delas s {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.license-tab %} - A seção "{% data variables.product.prodname_GH_advanced_security %}" mostra os detalhes do uso atual. ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings](/assets/images/help/enterprises/enterprise-licensing-tab-ghas.png) If you run out of seats, the section will be red and show "Limit exceeded". Você deve quer reduzir o seu uso de {% data variables.product.prodname_GH_advanced_security %} ou comprar mais estações. Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security#getting-the-most-out-of-github-advanced-security)". ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings showing "Limit exceeded"](/assets/images/help/enterprises/enterprise-licensing-tab-ghas-no-seats.png) + A seção "{% data variables.product.prodname_GH_advanced_security %}" mostra os detalhes do uso atual. ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings](/assets/images/help/enterprises/enterprise-licensing-tab-ghas.png) If you run out of seats, the section will be red and show "Limit exceeded". Você deve quer reduzir o seu uso de {% data variables.product.prodname_GH_advanced_security %} ou comprar mais estações. Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security#getting-the-most-out-of-github-advanced-security)". ![{% data variables.product.prodname_GH_advanced_security %} em configurações de licenciamento corporativo, que mostra o "limite excedido"](/assets/images/help/enterprises/enterprise-licensing-tab-ghas-no-seats.png) 4. Opcionalmente, para ver uma análise detalhada do uso por organização, clique em **Cobrança**. ![Billing tab in the enterprise account settings sidebar](/assets/images/help/business-accounts/settings-billing-tab.png) Na seção "{% data variables.product.prodname_GH_advanced_security %}", você pode ver o número de committers e committers únicos para cada organização. ![{% data variables.product.prodname_GH_advanced_security %} em configurações de cobrança corporativa](/assets/images/help/billing/ghas-orgs-list-enterprise-dotcom.png) 5. Opcionalmente, clique no nome de uma organização em que você é um proprietário para exibir as configurações de segurança e análise para a organização. ![Organização proprietária na seção de {% data variables.product.prodname_GH_advanced_security %} das configurações de cobrança corporativa](/assets/images/help/billing/ghas-orgs-list-enterprise-click-org.png) 6. Na página de configurações "Análise de & segurança" desça até a seção "repositórios de {% data variables.product.prodname_GH_advanced_security %}" para ver uma descrição detalhada do uso por repositório para esta organização. ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/enterprises/settings-security-analysis-ghas-repos-list.png) Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise para a sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". diff --git a/translations/pt-BR/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md b/translations/pt-BR/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md index 415a3417bc..3fa9281c15 100644 --- a/translations/pt-BR/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md +++ b/translations/pt-BR/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md @@ -1,7 +1,7 @@ --- title: Sobre a cobrança para codespaces shortTitle: Sobre a cobrança -intro: 'View pricing and see how to manage {% data variables.product.prodname_codespaces %} billing for your organization.' +intro: 'Veja os preços e como gerenciar a cobrança de {% data variables.product.prodname_codespaces %} para a sua organização.' permissions: 'To manage billing for Codespaces for an organization, you must be an organization owner or a billing manager.' versions: fpt: '*' @@ -12,13 +12,13 @@ topics: - Billing --- -## {% data variables.product.prodname_codespaces %} pricing +## Preços de {% data variables.product.prodname_codespaces %} -{% data variables.product.prodname_codespaces %} usage is billed for all accounts on the Team and Enterprise plans, and does not include any entitlements. Individual accounts are not currently billed for {% data variables.product.prodname_codespaces %} usage. +O uso de {% data variables.product.prodname_codespaces %} é cobrado para todas as contas nos planos de equipe e corporativos e não inclui nenhum direito. Atualmente, as contas individuais não são cobradas para o uso de {% data variables.product.prodname_codespaces %}. -{% data variables.product.prodname_codespaces %} usage is billed according to the units of measure in the following table: +O uso de {% data variables.product.prodname_codespaces %} é cobrado de acordo com as unidades de medida na tabela a seguir: - Product | SKU | Unit of measure | Price | | ------------------- | -------- | --------------- | ----- | | Codespaces Compute | 2 core | 1 hour | $0.18 | | | 4 core | 1 hour | $0.36 | | | 8 core | 1 hour | $0.72 | | | 16 core | 1 hour | $1.44 | | | 32 core | 1 hour | $2.88 | | Codespaces Storage | Storage | 1 GB-month | $0.07 | + Produto | SKU | Unidade de medida | Preço | | ------------------- | -------- | --------------- | ----- | | Codespaces Compute | 2 núcleos | 1 hora | US$ 0,18 | | | 4 núcleos | 1 hora | US$ 0,36 | | | 8 núcleos | 1 hora | US$ 0,72 | | | 16 núcleos | 1 hora | US$ 1,44 | | | 32 núcleos | 1 hora | US$ 2,88 | | Codespaces Storage | Armazenamento | 1 GB por mês | US$ 0,07 | ## Sobre a cobrança do {% data variables.product.prodname_codespaces %} @@ -26,9 +26,11 @@ topics: Se uso de {% data variables.product.prodname_codespaces %} compartilha a data de cobrança, o método de pagamento e o recibo que já existem para sua conta. {% data reusables.dotcom_billing.view-all-subscriptions %} -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 {% data variables.product.prodname_codespaces %} usage. Para obter mais informações, consulte "[Conectar uma assinatura do Azure à sua empresa](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)". +Se você comprou {% data variables.product.prodname_enterprise %} por meio de um Contrato da Microsoft Enterprise, você pode conectar o seu ID de assinatura do Azure à sua conta corporativa para habilitar e pagar o uso de {% data variables.product.prodname_codespaces %}. Para obter mais informações, consulte "[Conectar uma assinatura do Azure à sua empresa](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)". -## Setting a spending limit +{% data reusables.dotcom_billing.pricing_cal %} + +## Definindo um limite de gastos {% data reusables.codespaces.codespaces-spending-limit-requirement %} @@ -36,16 +38,16 @@ Para obter informações sobre como gerenciar e alterar o limite de gastos da su {% data reusables.codespaces.exporting-changes %} -## How billing is handled for forked repositories +## Como a cobrança é administrada para repositórios bifurcados -{% data variables.product.prodname_codespaces %} can only be used in organizations where a billable owner has been defined. To incur charges to the organization, the user must be a member or collaborator, otherwise they cannot create a codespace. +{% data variables.product.prodname_codespaces %} só pode ser usado em organizações em que um proprietário cobrável tenha sido definido. Para incorrer em encargos com a organização, o usuário deve ser integrante ou colaborador. Caso contrário, não poderá criar um codespace. -For example, a user in a private organization can fork a repository within that organization, and can subsequently use a codespace billed to the organization; this is because the organization is the owner of the parent repository, which can remove the user's access, the forked repository, and the codespace. +Por exemplo, um usuário em uma organização privada pode bifurcar um repositório dentro dessa organização e, consequentemente, usar um codespace cobrado para a organização. Isto porque a organização é proprietária do repositório principal, que pode remover o acesso do usuário, o repositório bifurcado e o codespace. -## How billing is handled when a repository is transferred +## Como o faturamento é adminisrado quando um repositório é transferido -Usage is billed and reported on every hour. As such, you pay for any usage when a repository is within your organization. When a repository is transferred out of your organization, any codespaces in that repository are removed as part of the transfer process. +O uso é cobrado e informado a cada hora. Como tal, você paga qualquer uso quando um repositório está dentro da sua organização. Quando um repositório é transferido para fora da sua organização, todos os codespaces do repositório são removidos como parte do processo de transferência. -## What happens when users are removed +## O que acontece quando os usuários são removidos -If a user is removed from an organization or repository, their codespaces are automatically deleted. +Se um usuário for removido de uma organização ou repositório, seus codespaces serão automaticamente excluídos. diff --git a/translations/pt-BR/content/billing/managing-billing-for-github-codespaces/index.md b/translations/pt-BR/content/billing/managing-billing-for-github-codespaces/index.md index dc291fbe62..dcbe6e303e 100644 --- a/translations/pt-BR/content/billing/managing-billing-for-github-codespaces/index.md +++ b/translations/pt-BR/content/billing/managing-billing-for-github-codespaces/index.md @@ -1,5 +1,5 @@ --- -title: Managing billing for GitHub Codespaces +title: Gerenciando a cobrança para o GitHub Codespaces shortTitle: Codespaces intro: 'Você pode visualizar seu uso e definir um limite de gastos para {% data variables.product.prodname_codespaces %}.' versions: diff --git a/translations/pt-BR/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md b/translations/pt-BR/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md index edac3cdbf9..fa62f2ef92 100644 --- a/translations/pt-BR/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md +++ b/translations/pt-BR/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md @@ -1,5 +1,5 @@ --- -title: Managing spending limits for Codespaces +title: Gerenciar limites de gastos para codespaces intro: 'Você pode definir um limite de gastos para o uso do {% data variables.product.prodname_codespaces %}.' versions: fpt: '*' @@ -19,12 +19,12 @@ shortTitle: Limites de gastos {% data reusables.codespaces.codespaces-spending-limit-requirement %} -Once you've reached your spending limit, your organization or repository will no longer be able to create new codespaces, and won't be able to start existing codespaces. Any existing codespaces that are still running will not be shutdown; if you don't change the spending limit, you will not be charged for the amount that exceeds the limit. +Depois de atingir o limite de gastos, a sua organização ou repositório não poderão mais criar novos codespaces, e não será possível iniciar os codespaces existentes. Todos os codespaces que ainda estiverem em execução não serão desativados. Se você não alterar o limite de gastos, você não será cobrado pelo valor que exceder o limite. Para obter mais informações sobre preços para o uso de {% data variables.product.prodname_codespaces %}, consulte "[Sobre cobranças para o {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces)." -## Using your Azure Subscription -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 {% data variables.product.prodname_codespaces %} usage. Para obter mais informações, consulte "[Conectar uma assinatura do Azure à sua empresa](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)". +## Usando a sua assinatura do Azure +Se você comprou {% data variables.product.prodname_enterprise %} por meio de um Contrato da Microsoft Enterprise, você pode conectar o seu ID de assinatura do Azure à sua conta corporativa para habilitar e pagar o uso de {% data variables.product.prodname_codespaces %}. Para obter mais informações, consulte "[Conectar uma assinatura do Azure à sua empresa](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)". ## Gerenciando o limite de gastos de {% data variables.product.prodname_codespaces %} para sua organização @@ -42,15 +42,15 @@ Proprietários de organizações e gestores de faturamento podem gerenciar o lim {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.billing-tab %} -1. Above "{% data variables.product.prodname_codespaces %} monthly usage", click **Spending Limit**. ![Aba limite de gastos](/assets/images/help/settings/spending-limit-tab-enterprise.png) +1. Acima do uso mensal de {% data variables.product.prodname_codespaces %}", clique em **Limite de gastos**. ![Aba limite de gastos](/assets/images/help/settings/spending-limit-tab-enterprise.png) {% data reusables.dotcom_billing.monthly-spending-limit %} {% data reusables.dotcom_billing.update-spending-limit %} -## Exporting changes when you have reached your spending limit +## Exportar alterações quando você atingir seu limite de gastos {% data reusables.codespaces.exporting-changes %} -## Managing usage and spending limit email notifications +## Gerenciamento de notificações por e-mail e limite de gastos -Email notifications are sent to account owners and billing managers when spending reaches 50%, 75%, and 90% of your account's spending limit. +As notificações de e-mail são enviadas para os proprietários de contas e gerentes de cobrança quando os gastos chegam a 50%, 75% e 90% do limite de gastos da sua conta. -You can disable these notifications anytime by navigating to the bottom of the **Spending Limit** page. +Você pode desabilitar essas notificações a qualquer momento, acessando a parte inferior da página **limite de gastos**. diff --git a/translations/pt-BR/content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md b/translations/pt-BR/content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md index a9de3fe7da..257cfec2dc 100644 --- a/translations/pt-BR/content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md +++ b/translations/pt-BR/content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md @@ -1,7 +1,7 @@ --- -title: Viewing your Codespaces usage -shortTitle: Viewing your usage -intro: 'You can view the compute minutes and storage used by {% data variables.product.prodname_codespaces %}.' +title: Visualizando seu uso dos seus codespaces +shortTitle: Visualizando seu uso +intro: 'Você pode visualizar os minutos computados e o armazenamento usado pelo {% data variables.product.prodname_codespaces %}.' permissions: 'To manage billing for Codespaces for an organization, you must be an organization owner or a billing manager.' product: '{% data reusables.gated-features.codespaces %}' versions: @@ -14,7 +14,7 @@ topics: ## Visualizando o uso de {% data variables.product.prodname_codespaces %} para a sua organização -Os proprietários da organização e gerentes de faturamento podem ver o uso do {% data variables.product.prodname_codespaces %} para uma organização. For organizations managed by an enterprise account, the organization owners can view {% data variables.product.prodname_codespaces %} usage in the organization billing page, and enterprise admins can view the usage for the entire enterprise. +Os proprietários da organização e gerentes de faturamento podem ver o uso do {% data variables.product.prodname_codespaces %} para uma organização. Para organizações gerenciadas por uma conta corporativa, os proprietários da organização podem ver o uso de {% data variables.product.prodname_codespaces %} na página de cobrança da organização, e os administradores de empresas podem ver o uso para toda a empresa. {% data reusables.organizations.billing-settings %} {% data reusables.dotcom_billing.codespaces-minutes %} @@ -26,4 +26,4 @@ Proprietários de organizações e gestores de faturamento podem visualizar o us {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.billing-tab %} -1. Under "{% data variables.product.prodname_codespaces %}", view the usage details of each organization in your enterprise account. +1. Em "{% data variables.product.prodname_codespaces %}, veja as informações de uso de cada organização na sua conta corporativa. 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 a168b4b6b5..f89db73dcc 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 @@ -47,9 +47,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. 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. +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. -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.25 USD per GB or $37 USD. The overage for data transfer would cost $0.50 USD per GB or $20 USD. +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. {% data reusables.dotcom_billing.pricing_cal %} No final do mês, {% data variables.product.prodname_dotcom %} arredonda sua transferência de dados para o GB mais próximo. diff --git a/translations/pt-BR/content/billing/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages.md b/translations/pt-BR/content/billing/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages.md index 76b136ab6b..25912bae3d 100644 --- a/translations/pt-BR/content/billing/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages.md +++ b/translations/pt-BR/content/billing/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages.md @@ -61,5 +61,5 @@ Proprietários de organizações e gestores de faturamento podem gerenciar o lim {% data reusables.dotcom_billing.monthly-spending-limit %} {% data reusables.dotcom_billing.update-spending-limit %} -## Managing usage and spending limit email notifications +## Gerenciamento de notificações por e-mail e limite de gastos {% data reusables.billing.email-notifications %} diff --git a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md index 9d7fc1ae30..9ef5ced4bc 100644 --- a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md +++ b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md @@ -1,5 +1,5 @@ --- -title: About billing for your enterprise +title: Sobre a cobrança para a sua empresa intro: Você pode visualizar as informações de cobrança para a sua empresa. product: '{% data reusables.gated-features.enterprise-accounts %}' redirect_from: @@ -13,10 +13,10 @@ versions: ghae: '*' topics: - Enterprise -shortTitle: Billing for your enterprise +shortTitle: Cobrança para sua empresa --- -## About billing for your enterprise +## Sobre a cobrança para a sua empresa {% ifversion ghae %} @@ -45,23 +45,23 @@ Você pode ver seu uso atual no seu [Portal da conta do Azure](https://portal.az {% ifversion fpt %} -{% data variables.product.company_short %} bills monthly for the total number of members in your enterprise account, as well as any additional services you use with {% data variables.product.prodname_ghe_cloud %}. +{% data variables.product.company_short %} faz a cobrança mensal para o número total de membros da sua conta corporativa, bem como quaisquer serviços adicionais que você usar com {% data variables.product.prodname_ghe_cloud %}. {% elsif ghes %} -Each user on {% data variables.product.product_location %} consumes a seat on your license. {% data variables.product.company_short %} bills monthly for the total number of seats consumed on your license. +Cada usuário em {% data variables.product.product_location %} consome uma estação na sua licença. {% data variables.product.company_short %} faz a cobrança mensal no número total de estações consumidas na sua licença. {% endif %} -{% data reusables.billing.about-invoices-for-enterprises %} For more information about usage and invoices, see "[Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)" and {% ifversion ghes %}"Managing invoices for your enterprise" in the {% data variables.product.prodname_dotcom_the_website %} documentation.{% elsif fpt %}"[Managing invoices for your enterprise](/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise)."{% endif %} +{% data reusables.billing.about-invoices-for-enterprises %} Para mais informações sobre uso e faturas, consulte "[Visualizando a assinatura e o uso da sua conta corporativa](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)" e {% ifversion ghes %}"Gerenciando faturas da sua empresa" na documentação de {% data variables.product.prodname_dotcom_the_website %}.{% elsif fpt %}"[Gerenciando faturas para a sua empresa](/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise)."{% endif %} -Administrators for your enterprise account on {% data variables.product.prodname_dotcom_the_website %} can access and manage billing for the enterprise. +Os administradores da conta corporativa em {% data variables.product.prodname_dotcom_the_website %} podem acessar e gerenciar a cobrança da empresa. {% ifversion fpt %} -Each member of your enterprise account with a unique email address consumes a license. Billing managers do not consume a license. Each outside collaborator on a private repository that an organization in your enterprise owns consumes a license, unless the private repository is a fork. Each invitee to your enterprise account, including owners, members of organizations, and outside collaborators, consume a license. For more information about roles in an enterprise account, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" and "[Inviting people to manage your enterprise](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)." +Cada membro da sua conta corporativa com um endereço de e-mail exclusivo consome uma licença. Os gerentes de cobrança não consomem uma licença. Cada colaborador externo em um repositório privado que uma organização possui na sua empresa consome uma licença, a menos que o repositório privado seja uma bifurcação. Cada convidado à sua conta corporativa, incluindo proprietários, organizações e colaboradores externos, consuma uma licença. Para mais informações sobre funções em uma conta corporativa, consulte "[Funções em uma empresa](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" e "[Convidando pessoas para gerenciar sua empresa](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise). " -{% data reusables.enterprise-accounts.billing-microsoft-ea-overview %} For more information, see "[Connecting an Azure subscription to your enterprise](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)." +{% data reusables.enterprise-accounts.billing-microsoft-ea-overview %} Para obter mais informações, consulte "[Conectando uma assinatura do Azure à sua empresa](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)". {% endif %} @@ -71,15 +71,15 @@ Each member of your enterprise account with a unique email address consumes a li {% endif %} -## About synchronization of license usage +## Sobre a sincronização do uso da licença {% data reusables.enterprise.about-deployment-methods %} -{% data reusables.enterprise-licensing.about-license-sync %} For more information, see {% ifversion fpt %}"[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}"[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 %} +{% data reusables.enterprise-licensing.about-license-sync %} Para mais informações, consulte {% ifversion fpt %}"[Sincronizando o uso da licença entre {% data variables.product.prodname_ghe_server %} e {% data variables.product.prodname_ghe_cloud %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)" na documentação de {% data variables.product.prodname_ghe_server %}.{% elsif ghes %}"[Sincronizando o uso da licença entre {% data variables.product.prodname_ghe_server %} e {% 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 %} {% endif %} ## Leia mais -- "[About enterprise accounts]({% ifversion fpt or ghes %}/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts#about-enterprise-accounts-on-githubcom{% elsif ghae %}/admin/overview/about-enterprise-accounts{% endif %})"{% ifversion fpt or ghes %} -- "[About licenses for GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)"{% endif %} +- "[Sobre as contas corporativas]({% ifversion fpt or ghes %}/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts#about-enterprise-accounts-on-githubcom{% elsif ghae %}/admin/overview/about-enterprise-accounts{% endif %})"{% ifversion fpt or ghes %} +- "[Sobre licenças para o GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)"{% endif %} diff --git a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/index.md b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/index.md index cd6d659801..0db51cde43 100644 --- a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/index.md +++ b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/index.md @@ -1,7 +1,7 @@ --- title: Gerenciar a cobrança de sua conta GitHub shortTitle: Sua conta no GitHub -intro: '{% ifversion fpt %}{% data variables.product.product_name %} offers free and paid products for every account. You can upgrade, downgrade, and view pending changes to your account''s subscription at any time.{% elsif ghes or ghae %}You can manage billing for {% data variables.product.product_name %}{% ifversion ghae %}.{% elsif ghes %} from your enterprise account on {% data variables.product.prodname_dotcom_the_website %}.{% endif %}{% endif %}' +intro: '{% ifversion fpt %}{% data variables.product.product_name %} oferece produtos grátis e pagos para cada conta. Você pode atualizar, fazer o downgrade e visualizar as alterações pendentes da assinatura da sua conta a qualquer momento.{% elsif ghes or ghae %}Você pode gerenciar a cobrança para {% data variables.product.product_name %}{% ifversion ghae %}.{% elsif ghes %} a partir da sua conta corporativa em {% data variables.product.prodname_dotcom_the_website %}.{% endif %}{% endif %}' redirect_from: - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account - /categories/97/articles/ diff --git a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise.md b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise.md index df1595016c..9b9545b1dd 100644 --- a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise.md +++ b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise.md @@ -1,7 +1,7 @@ --- -title: Managing invoices for your enterprise -shortTitle: Manage invoices -intro: 'You can view, pay, or download a current invoice for your enterprise, and you can view your payment history.' +title: Gerenciando faturas da sua empresa +shortTitle: Gerenciar faturas +intro: 'Você pode visualizar, pagar ou fazer o download de uma fatura atual da sua empresa e poderá ver seu histórico de pagamentos.' product: '{% data reusables.gated-features.enterprise-accounts %}' versions: fpt: '*' @@ -11,11 +11,11 @@ topics: - Licensing --- -## About invoices for your enterprise +## Sobre as faturas da sua empresa -{% data reusables.billing.about-invoices-for-enterprises %} For more information, see "[About billing for your enterprise](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)." +{% data reusables.billing.about-invoices-for-enterprises %} Para obter mais informações, consulte "[Sobre cobrança para a sua empresa](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)". -For more information about viewing the subscription and usage for your enterprise account, see "[Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)." +Para obter mais informações sobre a visualização da assinatura e uso da conta corporativa, consulte "[Visualizando a assinatura e o uso da sua conta corporativa](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)". {% data reusables.billing.ghes-with-no-enterprise-account %} @@ -24,14 +24,14 @@ For more information about viewing the subscription and usage for your enterpris {% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.billing-tab %} -4. Under "Current Invoice", click **View invoice**. ![Link de visualização da fatura](/assets/images/help/business-accounts/view-invoice-link.png) +4. Em "Fatura atual", clique em **Visualizar fatura**. ![Link de visualização da fatura](/assets/images/help/business-accounts/view-invoice-link.png) ## Pagando sua fatura atual {% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.billing-tab %} -4. Under "Payment Due", click **Pay invoice**. ![Link de pagamento da fatura](/assets/images/help/business-accounts/pay-invoice-link.png) +4. Em "Pagamento devido", clique em **Pagar fatura**. ![Link de pagamento da fatura](/assets/images/help/business-accounts/pay-invoice-link.png) 5. Em "Pagar fatura", digite as informações do seu cartão de crédito no formulário de segurança e clique em **Pay Invoice** (Pagar fatura). ![Confirmar e pagar a fatura](/assets/images/help/business-accounts/pay-invoice.png) ## Baixando sua fatura atual @@ -46,4 +46,4 @@ For more information about viewing the subscription and usage for your enterpris {% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.billing-tab %} -4. To see a summary of your past billing activity, under "Billing", click the **Past Invoices** tab. ![Aba de visualização de histórico de pagamento](/assets/images/help/business-accounts/view-payment-history.png) +4. Para ver um resumo de sua atividade de cobrança anterior, em "Cobrança", clique na aba **Faturas anteriores**. ![Aba de visualização de histórico de pagamento](/assets/images/help/business-accounts/view-payment-history.png) diff --git a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md index bbb0ffcb2a..42b5f5c114 100644 --- a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md +++ b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md @@ -1,6 +1,6 @@ --- title: Exibir assinatura e uso da conta corporativa -intro: 'You can view the current {% ifversion fpt %}subscription, {% endif %}license usage{% ifversion fpt %}, invoices, payment history, and other billing information{% endif %} for {% ifversion fpt %}your enterprise account{% elsif ghes %}{% data variables.product.product_location_enterprise %}{% endif %}.' +intro: 'Você pode ver a assinatura atual {% ifversion fpt %}, {% endif %}uso da licença{% ifversion fpt %}faturas, histórico de pagamentos e outras informações de faturamento{% endif %} para {% ifversion fpt %}conta corporativa{% elsif ghes %}{% data variables.product.product_location_enterprise %}{% endif %}.' product: '{% data reusables.gated-features.enterprise-accounts %}' permissions: 'Enterprise owners {% ifversion fpt %}and billing managers {% endif %}can access and manage all billing settings for enterprise accounts.' redirect_from: @@ -18,21 +18,21 @@ shortTitle: Visualizar assinatura & uso ## Sobre a cobrança de contas corporativas -You can view an overview of {% ifversion fpt %}your subscription and paid{% elsif ghes %}the license{% endif %} usage for {% ifversion fpt %}your{% elsif ghes %}the{% endif %} enterprise account on {% ifversion fpt %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %}. +Você pode ver a visão geral da {% ifversion fpt %}sua assinatura e da licença{% elsif ghes %}a paga{% endif %} usada para a {% ifversion fpt %}sua{% elsif ghes %}a{% endif %} conta corporativa em {% ifversion fpt %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %}. -For invoiced {% data variables.product.prodname_enterprise %} customers{% ifversion ghes %} who use both {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}{% endif %}, each invoice includes details about billed services for all products. For example, in addition to your usage for {% ifversion fpt %}{% data variables.product.prodname_ghe_cloud %}{% elsif ghes %}{% data variables.product.product_name %}{% endif %}, you may have usage for {% data variables.product.prodname_GH_advanced_security %}{% ifversion fpt %}, {% elsif ghes %}. You may also have usage on {% data variables.product.prodname_dotcom_the_website %}, like {% endif %}paid licenses in organizations outside of your enterprise account, data packs for {% data variables.large_files.product_name_long %}, or subscriptions to apps in {% data variables.product.prodname_marketplace %}. For more information about invoices, see "{% ifversion fpt %}[Managing invoices for your enterprise](/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise)."{% elsif ghes %}Viewing the subscription and usage for your enterprise account" in the {% data variables.product.prodname_dotcom_the_website %} documentation.{% endif %} +Para {% data variables.product.prodname_enterprise %} clientes faturados{% ifversion ghes %} que usam {% data variables.product.prodname_ghe_cloud %} e {% data variables.product.prodname_ghe_server %}{% endif %}, cada fatura inclui as informações sobre os serviços cobrados para todos os produtos. Por exemplo, além do seu uso para {% ifversion fpt %}{% data variables.product.prodname_ghe_cloud %}{% elsif ghes %}{% data variables.product.product_name %}{% endif %}, você pode ter uso para {% data variables.product.prodname_GH_advanced_security %}{% ifversion fpt %}, {% elsif ghes %}. Você também pode ter uso em {% data variables.product.prodname_dotcom_the_website %}, como {% endif %}licenças pagas em organizações fora da conta corporativa, pacotes de dados para {% data variables.large_files.product_name_long %}ou assinaturas de aplicativos em {% data variables.product.prodname_marketplace %}. Para obter mais informações sobre faturas, consulte "{% ifversion fpt %}[Gerenciar faturas para a sua empresa](/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise).{% elsif ghes %}Visualizando a assinatura e o uso da sua conta corporativa" na documentação de {% data variables.product.prodname_dotcom_the_website %}.{% endif %} {% ifversion fpt %} -In addition to enterprise owners, billing managers can view the subscription and usage for your enterprise account. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise#billing-manager)" and "[Inviting people to manage your enterprise](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)." +Além dos proprietários da empresa, os gerentes de cobrança podem visualizar a assinatura e o uso da sua conta corporativa. Para obter mais informações, consulte "[Funções em uma empresa](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise#billing-manager)" e "[Convidando pessoas para gerenciar a sua empresa](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)". -{% data reusables.enterprise-accounts.billing-microsoft-ea-overview %} For more information, see "[Connecting an Azure subscription to your enterprise](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)." +{% data reusables.enterprise-accounts.billing-microsoft-ea-overview %} Para obter mais informações, consulte "[Conectando uma assinatura do Azure à sua empresa](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)". {% endif %} {% ifversion ghes %} -If you want to view an overview of your subscription and usage for {% data variables.product.prodname_enterprise %} and any related services on {% data variables.product.prodname_dotcom_the_website %}, see "[Viewing the subscription and usage for your enterprise account](/free-pro-team@latest/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)" in the {% data variables.product.prodname_dotcom_the_website %} documentation. +Se você deseja ver uma visão geral da sua assinatura e uso para {% data variables.product.prodname_enterprise %} e todos os serviços relacionados em {% data variables.product.prodname_dotcom_the_website %}, consulte "[Visualizando a assinatura e o uso da conta corporativa](/free-pro-team@latest/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)" na documentação de {% data variables.product.prodname_dotcom_the_website %}. {% endif %} @@ -41,9 +41,9 @@ If you want to view an overview of your subscription and usage for {% data varia {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.license-tab %} -1. Under "User licenses", view your total licenses, number of consumed licenses, and your subscription expiration date. +1. Em "Licenças de usuário", exiba o total de licenças, o número de licenças consumidas e a data de vencimento da sua assinatura. {% ifversion fpt %}![License and subscription information in enterprise billing settings](/assets/images/help/business-accounts/billing-license-info.png){% else %} ![Informações de assinaturas e licenças nas configurações de cobrança da empresa](/assets/images/enterprise/enterprise-server/enterprise-server-billing-license-info.png){% endif %} -1. Optionally, to view details for license usage or download a {% ifversion fpt %}CSV{% elsif ghes %}JSON{% endif %} file with license details{% ifversion fpt %}, to the right of "User Licenses"{% endif %}, click **View {% ifversion fpt %}details{% elsif ghes %}users{% endif %}** or {% ifversion fpt %}{% octicon "download" aria-label="The download icon" %}{% elsif ghes %}**Export license usage**{% endif %}.{% ifversion fpt %} !["View details" button and button with download icon to the right of "User Licenses"](/assets/images/help/business-accounts/billing-license-info-click-view-details-or-download.png){% endif %}{% ifversion fpt %} +1. Opcionalmente, para visualizar as informações referentes à licença ou para fazer o download de um arquivo {% ifversion fpt %}CSV{% elsif ghes %}JSON{% endif %} com as informações da licença{% ifversion fpt %}, à direita de "Licenças do usuário"{% endif %}, clique em **Visualizar {% ifversion fpt %}details{% elsif ghes %}users{% endif %}** ou {% ifversion fpt %}{% octicon "download" aria-label="The download icon" %}{% elsif ghes %}**Uso de licença de exportação**{% endif %}.{% ifversion fpt %} !["View details" button and button with download icon to the right of "User Licenses"](/assets/images/help/business-accounts/billing-license-info-click-view-details-or-download.png){% endif %}{% ifversion fpt %} 1. Opcionalmente, para visualizar os detalhes de uso para outras funcionalidades, clique em **Cobrança**. ![Aba de faturamento na barra lateral de configurações da conta corporativa](/assets/images/help/business-accounts/settings-billing-tab.png) {% endif %} diff --git a/translations/pt-BR/content/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method.md b/translations/pt-BR/content/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method.md index 49be4fd60c..377c3fc715 100644 --- a/translations/pt-BR/content/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method.md +++ b/translations/pt-BR/content/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method.md @@ -34,9 +34,9 @@ Não fornecemos fatura nem damos suporte a ordens de compra para contas pessoais {% data reusables.user_settings.billing_plans %} {% data reusables.dotcom_billing.update_payment_method %} -1. If your account has existing billing information that you want to update, click **Edit**. ![Botão de Cobrança de novo cartão](/assets/images/help/billing/billing-information-edit-button.png) +1. Se sua conta tiver informações de cobrança existentes que você deseja atualizar, clique em **Editar**. ![Botão de Cobrança de novo cartão](/assets/images/help/billing/billing-information-edit-button.png) {% data reusables.dotcom_billing.enter-billing-info %} -1. If your account has an existing payment method that you want to update, click **Edit**. ![Botão de Cobrança de novo cartão](/assets/images/help/billing/billing-payment-method-edit-button.png) +1. Se sua conta tem um método de pagamento existente que você deseja atualizar, clique em **Editar**. ![Botão de Cobrança de novo cartão](/assets/images/help/billing/billing-payment-method-edit-button.png) {% data reusables.dotcom_billing.enter-payment-info %} ## Atualizar a forma de pagamento da sua organização diff --git a/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md b/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md index 5fdb86c7b8..9350e9c795 100644 --- a/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md +++ b/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md @@ -1,6 +1,6 @@ --- -title: About licenses for GitHub Enterprise -intro: '{% ifversion fpt %}If you purchase {% data variables.product.prodname_enterprise %} and use {% data variables.product.prodname_ghe_server %}, each{% elsif ghes %}Each{% endif %} {% data variables.product.prodname_ghe_server %} instance requires a license file to validate and unlock the application.' +title: Sobre licenças para o GitHub Enterprise +intro: '{% ifversion fpt %}Se você comprar {% data variables.product.prodname_enterprise %} e usar {% data variables.product.prodname_ghe_server %}, cada{% elsif ghes %}Cada{% endif %} instância de {% data variables.product.prodname_ghe_server %} exige um arquivo de licença para validar e desbloquear o aplicativo.' versions: fpt: '*' ghes: '*' @@ -8,10 +8,10 @@ type: overview topics: - Enterprise - Licensing -shortTitle: About licenses +shortTitle: Sobre licenças --- -## About license files for {% data variables.product.prodname_enterprise %} +## Sobre os arquivos de licença para {% data variables.product.prodname_enterprise %} {% ifversion fpt %} @@ -19,13 +19,13 @@ shortTitle: About licenses {% endif %} -When you purchase or renew {% data variables.product.prodname_enterprise %}, {% data variables.product.company_short %} provides a license file {% ifversion fpt %}for your deployments of {% data variables.product.prodname_ghe_server %}{% elsif ghes %}for {% data variables.product.product_location_enterprise %}{% endif %}. A license file has an expiration date and controls the number of people who can use {% data variables.product.product_location_enterprise %}. After you download and install {% data variables.product.prodname_ghe_server %}, you must upload the license file to unlock the application for you to use. +Ao comprar ou renovar {% data variables.product.prodname_enterprise %}, {% data variables.product.company_short %} fornece o arquivo de uma licença {% ifversion fpt %}para suas implantações de {% data variables.product.prodname_ghe_server %}{% elsif ghes %}para {% data variables.product.product_location_enterprise %}{% endif %}. O arquivo de uma licença tem uma data de validade e controla o número de pessoas que podem usar {% data variables.product.product_location_enterprise %}. Após fazer o download e instalar o {% data variables.product.prodname_ghe_server %}, você deverá fazer o upload do arquivo de licença para desbloquear o aplicativo para você usar. -For more information about downloading your license file, see "[Downloading your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)." For more information about uploading your license file, see {% ifversion fpt %}"[Uploading a new license to {% data variables.product.prodname_ghe_server %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}"[Uploading a new license to {% data variables.product.prodname_ghe_server %}](/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)."{% endif %} +Para obter mais informações sobre a transferência de arquivo da sua licença, consulte "[Fazer o download da sua licença para {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)". Para obter mais informações sobre como fazer o upload do seu arquivo de licença, consulte {% ifversion fpt %}"[Fazer o upload de uma nova licença para {% data variables.product.prodname_ghe_server %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)" na documentação de {% data variables.product.prodname_ghe_server %}.{% elsif ghes %}"[Fazer o upload de uma nova licença para {% data variables.product.prodname_ghe_server %}](/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)."{% endif %} -If your license expires, you won't be able to access {% data variables.product.prodname_ghe_server %} via a web browser or Git. Se necessário, você poderá usar os utilitários de linha de comando para fazer backup de todos os seus dados. Para obter mais informações, consulte "[Configurar backups no appliance](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance)". Se você tiver alguma dúvida sobre a renovação da sua licença, contate {% data variables.contact.contact_enterprise_sales %}. +Se sua licença vencer, você não poderá acessar {% data variables.product.prodname_ghe_server %} por meio de um navegador ou Git. Se necessário, você poderá usar os utilitários de linha de comando para fazer backup de todos os seus dados. Para obter mais informações, consulte "[Configurar backups no appliance](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance)". Se você tiver alguma dúvida sobre a renovação da sua licença, contate {% data variables.contact.contact_enterprise_sales %}. -## About synchronization of license usage for {% data variables.product.prodname_enterprise %} +## Sobre a sincronização do uso da licença para {% data variables.product.prodname_enterprise %} {% ifversion ghes %} @@ -33,10 +33,10 @@ If your license expires, you won't be able to access {% data variables.product.p {% endif %} -{% data reusables.enterprise-licensing.about-license-sync %} For more information, see {% ifversion fpt %}"[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}"[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 %} +{% data reusables.enterprise-licensing.about-license-sync %} Para mais informações, consulte {% ifversion fpt %}"[Sincronizando o uso da licença entre {% data variables.product.prodname_ghe_server %} e {% data variables.product.prodname_ghe_cloud %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)" na documentação de {% data variables.product.prodname_ghe_server %}.{% elsif ghes %}"[Sincronizando o uso da licença entre {% data variables.product.prodname_ghe_server %} e {% 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 %} ## Leia mais -- "[About billing for your enterprise](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)" -- [{% data variables.product.prodname_enterprise %} Releases](https://enterprise.github.com/releases/) website -- "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/admin/installation/setting-up-a-github-enterprise-server-instance)" +- "[Sobre a cobrança para a sua empresa](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)" +- Site de [Versões de {% data variables.product.prodname_enterprise %}](https://enterprise.github.com/releases/) +- [Configurar instância do {% data variables.product.prodname_ghe_server %}](/admin/installation/setting-up-a-github-enterprise-server-instance) diff --git a/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md b/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md index 6ffab6391c..c15627a20f 100644 --- a/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md +++ b/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md @@ -1,6 +1,6 @@ --- -title: Downloading your license for GitHub Enterprise -intro: 'You can download a copy of your license file for {% data variables.product.prodname_ghe_server %}.' +title: Fazendo o download da sua licença para o GitHub Enterprise +intro: 'Você pode fazer o download de uma cópia do arquivo da sua licença para {% data variables.product.prodname_ghe_server %}.' permissions: 'Enterprise owners can download license files for {% data variables.product.prodname_ghe_server %}.' versions: fpt: '*' @@ -9,28 +9,28 @@ type: how_to topics: - Enterprise - Licensing -shortTitle: Download your license +shortTitle: Faça o download da sua licença --- -## About license files for {% data variables.product.prodname_enterprise %} +## Sobre os arquivos de licença para {% data variables.product.prodname_enterprise %} -After you purchase or upgrade a license for {% data variables.product.prodname_enterprise %} from {% data variables.contact.contact_enterprise_sales %}, you must download your new license file. For more information about licenses for {% data variables.product.prodname_enterprise %}, see "[About licenses for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)." +Após comprar ou atualizar uma licença para {% data variables.product.prodname_enterprise %} de {% data variables.contact.contact_enterprise_sales %}, você deverá fazer o download do arquivo da sua nova licença. Para obter mais informações sobre licenças para {% data variables.product.prodname_enterprise %}, consulte "[Sobre licenças para {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)". {% data reusables.enterprise-licensing.contact-sales-for-renewals-or-seats %} -## Downloading your license from {% data variables.product.prodname_dotcom_the_website %} +## Fazer o download da sua licença de {% data variables.product.prodname_dotcom_the_website %} -You must have an enterprise account on {% data variables.product.prodname_dotcom_the_website %} to download your license from {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações sobre contas corporativas, consulte "[Sobre contas corporativas](/admin/overview/about-enterprise-accounts)". +Você deve ter uma conta corporativa em {% data variables.product.prodname_dotcom_the_website %} para fazer o download da sua licença em {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações sobre contas corporativas, consulte "[Sobre contas corporativas](/admin/overview/about-enterprise-accounts)". {% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} {% data reusables.enterprise-accounts.settings-tab %} 1. Na barra lateral esquerda, clique em **Enterprise licensing** (Licenciamento Empresarial). ![Aba "Licenciamento empresarial" na barra lateral de configurações da conta corporativa](/assets/images/help/enterprises/enterprise-licensing-tab.png) 1. Em "Enterprise Server Instances", clique em {% octicon "download" aria-label="The download icon" %} para fazer o download do seu arquivo de licença. ![Baixar licença do GitHub Enterprise Server](/assets/images/help/business-accounts/download-ghes-license.png) -After you download your license file, you can upload the file to {% data variables.product.product_location_enterprise %} to validate your application. For more information, see {% ifversion fpt %}"[Uploading a new license to {% data variables.product.prodname_ghe_server %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}"[Uploading a new license to {% data variables.product.prodname_ghe_server %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)."{% endif %} +Depois de fazer o download do arquivo da sua licença, você poderá enviar o arquivo para {% data variables.product.product_location_enterprise %} para validar seu aplicativo. Para obter mais informações, consulte {% ifversion fpt %}"[Fazer o upload de uma nova licença para {% data variables.product.prodname_ghe_server %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)" na documentação de {% data variables.product.prodname_ghe_server %}. {% elsif ghes %}"[Fazero upload de uma nova licença para {% data variables.product.prodname_ghe_server %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)."{% endif %} -## Downloading your license if you don't have an enterprise account on {% data variables.product.prodname_dotcom_the_website %} +## Fazer o download da sua licença se você não tiver uma conta corporativa em {% data variables.product.prodname_dotcom_the_website %} -If you do not have an enterprise account on {% data variables.product.prodname_dotcom_the_website %}, or if you're not sure, you may be able to download your {% data variables.product.prodname_ghe_server %} license from the [{% data variables.product.prodname_enterprise %} website](https://enterprise.github.com/download). +Se você não tiver uma conta corporativa em {% data variables.product.prodname_dotcom_the_website %}, ou se você não tiver certeza, é possível que você consiga fazer o download da sua licença {% data variables.product.prodname_ghe_server %} no site [{% data variables.product.prodname_enterprise %}](https://enterprise.github.com/download). -If you have any questions about downloading your license, contact {% data variables.contact.contact_enterprise_sales %}. +Em caso de dúvidas sobre o download da sua licença, entre em contato com {% data variables.contact.contact_enterprise_sales %}. diff --git a/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/index.md b/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/index.md index 97f03f42b6..fd398da4c4 100644 --- a/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/index.md +++ b/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/index.md @@ -1,7 +1,7 @@ --- -title: Managing your license for GitHub Enterprise -shortTitle: GitHub Enterprise license -intro: 'You can view, manage, and update your license for {% data variables.product.prodname_enterprise %}, which unlocks the application on {% data variables.product.product_location_enterprise %}.' +title: Gerenciando a sua licença para o GitHub Enterprise +shortTitle: Licença do GitHub Enterprise +intro: 'Você pode visualizar, gerenciar e atualizar sua licença para {% data variables.product.prodname_enterprise %}, o que desbloqueia o aplicativo em {% data variables.product.product_location_enterprise %}.' redirect_from: - /enterprise/admin/installation/managing-your-github-enterprise-license - /enterprise/admin/categories/licenses/ diff --git a/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md b/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md index 3c79ef6b47..1e13770d13 100644 --- a/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md +++ b/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md @@ -1,6 +1,6 @@ --- -title: Syncing license usage between GitHub Enterprise Server and GitHub Enterprise Cloud -intro: 'You can sync license usage from {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %} to view all license usage across your enterprise in one place and ensure that people with accounts in both environments only consume one user license.' +title: Sincronizando o uso da licença entre o GitHub Enterprise Server e o GitHub Enterprise Cloud +intro: 'Você pode sincronizar o uso da licença de {% data variables.product.prodname_ghe_server %} com {% data variables.product.prodname_ghe_cloud %} para ver todas as licenças usadas por toda a sua empresa em um só lugar e garantir que as pessoas com contas em ambos os ambientes consomem apenas uma licença de usuário.' permissions: 'Enterprise owners can sync license usage between enterprise accounts on {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}.' versions: ghes: '*' @@ -8,22 +8,22 @@ type: how_to topics: - Enterprise - Licensing -shortTitle: Sync license usage +shortTitle: Sincronizar uso da licença --- -## About synchronization of license usage +## Sobre a sincronização do uso da licença {% data reusables.enterprise-licensing.about-license-sync %} -If you allow {% data variables.product.product_location %} to connect to {% data variables.product.prodname_dotcom_the_website %}, you can sync license usage between your enterprise accounts automatically. Automatic synchronization ensures that you see up-to-date license details on {% data variables.product.prodname_dotcom_the_website %}. If you don't want to allow {% data variables.product.product_location %} to connect to {% data variables.product.prodname_dotcom_the_website %}, you can manually sync license usage by uploading a file from {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}. +Se você permitir que {% data variables.product.product_location %} se conecte a {% data variables.product.prodname_dotcom_the_website %}, você poderá sincronizar automaticamente o uso da licença entre suas contas corporativas. A sincronização automática garante que você veja as informações atualizadas da licença em {% data variables.product.prodname_dotcom_the_website %}. Se você não deseja permitir que {% data variables.product.product_location %} conecte-se a {% data variables.product.prodname_dotcom_the_website %}, você poderá sincronizar manualmente o uso de licença, fazendo o upload de um arquivo de {% data variables.product.product_location %} para {% data variables.product.prodname_dotcom_the_website %}. -For more information about licenses and usage for {% data variables.product.prodname_ghe_server %}, see "[About licenses for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)." +Para obter mais informações sobre licenças e uso para {% data variables.product.prodname_ghe_server %}, consulte "[Sobre licenças para {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)". -## Automatically syncing license usage +## Sincronizar automaticamente o uso da licença É possível usar o {% data variables.product.prodname_github_connect %} para sincronizar automaticamente o uso e a contagem da licença de usuários entre o {% data variables.product.prodname_ghe_server %} e o {% data variables.product.prodname_ghe_cloud %}. Para obter mais informações, consulte "[Habilitar a sincronização de licenças de usuário entre o {% data variables.product.prodname_ghe_server %} e o {% data variables.product.prodname_ghe_cloud %}](/admin/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud)". -## Manually syncing license usage +## Uso da licença sincronizado manualmente Para sincronizar manualmente o uso das licenças de usuário entre as duas implantações, você pode baixar um arquivo JSON do {% data variables.product.prodname_ghe_server %} e fazer upload desse arquivo no {% data variables.product.prodname_ghe_cloud %}. diff --git a/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md b/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md index 6f0bbce447..89dc0db9c4 100644 --- a/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md +++ b/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md @@ -1,22 +1,22 @@ --- -title: Uploading a new license to GitHub Enterprise Server -intro: 'You can upload your license file for {% data variables.product.prodname_enterprise %} to {% data variables.product.product_location_enterprise %} to validate your application.' +title: Fazer o upload uma nova licença para o GitHub Enterprise Server +intro: 'Você pode fazer o upload do arquivo da sua licença para {% data variables.product.prodname_enterprise %} para {% data variables.product.product_location_enterprise %} a fim de validar seu aplicativo.' versions: ghes: '*' type: how_to topics: - Enterprise - Licensing -shortTitle: Upload a new license +shortTitle: Fazer o upload de uma nova licença --- -## About license files for {% data variables.product.prodname_enterprise %} +## Sobre os arquivos de licença para {% data variables.product.prodname_enterprise %} -After you purchase or upgrade a license for {% data variables.product.prodname_enterprise %} from {% data variables.contact.contact_enterprise_sales %}, you must upload the new license file to {% data variables.product.product_location_enterprise %} to unlock your new user licenses. For more information about licenses for {% data variables.product.product_name %}, see "[About licenses for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)" and "[Downloading your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)." +Após comprar ou atualizar uma licença para {% data variables.product.prodname_enterprise %} de {% data variables.contact.contact_enterprise_sales %}, você deverá fazer o upload do novo arquivo de licença para {% data variables.product.product_location_enterprise %} para desbloquear suas novas licenças de usuário. Para obter mais informações sobre licenças para {% data variables.product.product_name %}, consulte "[Sobre licenças para {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)" e "[Fazer o download da sua licença para {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)". {% data reusables.enterprise-licensing.contact-sales-for-renewals-or-seats %} -## Uploading your license to {% data variables.product.product_location_enterprise %} +## Fazendo o upload da sua licença para {% data variables.product.product_location_enterprise %} 1. Efetue o login em {% data variables.product.product_location_enterprise %} como administrador do site. {% data reusables.enterprise-accounts.access-enterprise %} @@ -28,7 +28,7 @@ After you purchase or upgrade a license for {% data variables.product.prodname_e {% ifversion ghes < 3.0 %} -If the web UI for {% data variables.product.prodname_ghe_server %} doesn't reflect your updated license immediately, see "[Troubleshooting](#troubleshooting)." +Se a interface web para {% data variables.product.prodname_ghe_server %} não refletir sua licença atualizada imediatamente, consulte "[Solução de problemas](#troubleshooting). " ## Solução de Problemas diff --git a/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md b/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md index e4d94ab171..d41ea60d91 100644 --- a/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md +++ b/translations/pt-BR/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md @@ -1,6 +1,6 @@ --- -title: Viewing license usage for GitHub Enterprise -intro: 'You can view license usage for your enterprise on {% ifversion fpt %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %}.' +title: Visualizando o uso da licença para o GitHub Enterprise +intro: 'Você pode visualizar o uso da licença da sua empresa em {% ifversion fpt %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %}.' permissions: 'Enterprise owners can view license usage for {% data variables.product.prodname_enterprise %}.' versions: fpt: '*' @@ -9,26 +9,26 @@ type: how_to topics: - Enterprise - Licensing -shortTitle: View license usage +shortTitle: Visualizar o uso da licença --- -## About license usage for {% data variables.product.prodname_enterprise %} +## Sobre o uso da licença para {% data variables.product.prodname_enterprise %} {% ifversion fpt %} -You can view license usage for your enterprise account on {% data variables.product.prodname_ghe_cloud %} on {% data variables.product.prodname_dotcom_the_website %}. +Você pode visualizar o uso da licença para a sua conta corporativa em {% data variables.product.prodname_ghe_cloud %} em {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-licensing.you-can-sync-for-a-combined-view %} {% elsif ghes %} -You can view license usage for {% data variables.product.prodname_ghe_server %} on {% data variables.product.product_location %}. +Você pode visualizar o uso da licença para {% data variables.product.prodname_ghe_server %} em {% data variables.product.product_location %}. -{% data reusables.enterprise-licensing.you-can-sync-for-a-combined-view %} For more information about the display of license usage on {% data variables.product.prodname_dotcom_the_website %}, see "Viewing license usage for {% data variables.product.prodname_enterprise %}" in the {% data variables.product.prodname_dotcom_the_website %} documentation. +{% data reusables.enterprise-licensing.you-can-sync-for-a-combined-view %} Para mais informações sobre a exibição do uso da licença em {% data variables.product.prodname_dotcom_the_website %}, consulte "Visualizando o uso da licença para {% data variables.product.prodname_enterprise %}" na documentação de {% data variables.product.prodname_dotcom_the_website %}. {% endif %} -## Viewing license usage on {% ifversion fpt %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %} +## Visualizando uso da licença em {% ifversion fpt %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %} {% ifversion fpt %} @@ -36,14 +36,14 @@ You can view license usage for {% data variables.product.prodname_ghe_server %} {% data reusables.enterprise-accounts.settings-tab %} 1. Na barra lateral esquerda, clique em **Enterprise licensing** (Licenciamento Empresarial). ![Aba "Licenciamento empresarial" na barra lateral de configurações da conta corporativa](/assets/images/help/enterprises/enterprise-licensing-tab.png) 1. Revise sua licença atual de {% data variables.product.prodname_enterprise %}, bem como licenças de usuário consumidas e disponíveis. - - If your license includes {% data variables.product.prodname_GH_advanced_security %}, you can review your total seat use. Para obter mais informações, consulte "[Visualizar o uso do seu {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage)". + - Se sua licença incluir {% data variables.product.prodname_GH_advanced_security %}, você poderá revisar o uso total de estações. Para obter mais informações, consulte "[Visualizar o uso do seu {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage)". {% elsif ghes %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.license-tab %} -1. Review your current {% data variables.product.prodname_enterprise %} license, as well as consumed and available user licenses.{% ifversion ghes > 3.0 %} - - If your license includes {% data variables.product.prodname_GH_advanced_security %}, you can review your total seat use as well as a per-organization breakdown of committers. Para obter mais informações, consulte "[Gerenciar {% data variables.product.prodname_GH_advanced_security %} para a sua empresa](/admin/advanced-security)".{% endif %} +1. Revise a sua licença atual de {% data variables.product.prodname_enterprise %}, bem como as licenças de usuário usadas e disponíveis.{% ifversion ghes > 3.0 %} + - Se sua licença incluir {% data variables.product.prodname_GH_advanced_security %}, você poderá revisar o uso total de estações, bem como o detalhamento por organização dos committers. Para obter mais informações, consulte "[Gerenciar {% data variables.product.prodname_GH_advanced_security %} para a sua empresa](/admin/advanced-security)".{% endif %} {% endif %} diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md index 08075f5057..9e93bae839 100644 --- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md +++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md @@ -1,7 +1,7 @@ --- -title: About code scanning with CodeQL -shortTitle: Code scanning with CodeQL -intro: 'You can use {% data variables.product.prodname_codeql %} to identify vulnerabilities and errors in your code. The results are shown as {% data variables.product.prodname_code_scanning %} alerts in {% data variables.product.prodname_dotcom %}.' +title: Sobre a digitalização de código com CodeQL +shortTitle: Digitalização de código com CodeQL +intro: 'Você pode usar {% data variables.product.prodname_codeql %} para identificar vulnerabilidades e erros no seu código. Os resultados são exibidos como alertas de {% data variables.product.prodname_code_scanning %} em {% data variables.product.prodname_dotcom %}.' product: '{% data reusables.gated-features.code-scanning %}' redirect_from: - /code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql @@ -23,39 +23,39 @@ topics: {% data reusables.code-scanning.about-codeql-analysis %} -There are two main ways to use {% data variables.product.prodname_codeql %} analysis for {% data variables.product.prodname_code_scanning %}: +Existem duas maneiras principais de usar {% data variables.product.prodname_codeql %} análise para {% data variables.product.prodname_code_scanning %}: -- Add the {% data variables.product.prodname_codeql %} workflow to your repository. This uses the [github/codeql-action](https://github.com/github/codeql-action/) to run the {% data variables.product.prodname_codeql_cli %}. Para obter mais informações, consulte "[Configurar {% data variables.product.prodname_code_scanning %} para um repositório](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)". -- Run the {% data variables.product.prodname_codeql %} {% ifversion fpt or ghes > 3.1 or ghae-next %}CLI directly {% elsif ghes = 3.0 %}CLI or runner {% else %}runner {% endif %} in an external CI system and upload the results to {% data variables.product.prodname_dotcom %}. For more information, see "[About {% data variables.product.prodname_codeql %} code scanning in your CI system ](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system)." +- Adicione o fluxo de trabalho de {% data variables.product.prodname_codeql %} ao seu repositório. Isto usa o [github/codeql-action](https://github.com/github/codeql-action/) para executar o {% data variables.product.prodname_codeql_cli %}. Para obter mais informações, consulte "[Configurar {% data variables.product.prodname_code_scanning %} para um repositório](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)". +- Execute {% data variables.product.prodname_codeql %} {% ifversion fpt or ghes > 3.1 or ghae-next %}CLI diretamente {% elsif ghes = 3.0 %}CLI ou executor {% else %}corredor {% endif %} em um sistema de CI externo e faça o upload dos resultados para {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Sobre a digitalização de código {% data variables.product.prodname_codeql %} no seu sistema de CI ](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system)." ## Sobre o {% data variables.product.prodname_codeql %} -{% data variables.product.prodname_codeql %} treats code like data, allowing you to find potential vulnerabilities in your code with greater confidence than traditional static analyzers. +O {% data variables.product.prodname_codeql %} trata o código como dados, permitindo que você encontre possíveis vulnerabilidades em seu código com maior confiança do que os analisadores estáticos tradicionais. -1. You generate a {% data variables.product.prodname_codeql %} database to represent your codebase. -2. Then you run {% data variables.product.prodname_codeql %} queries on that database to identify problems in the codebase. -3. The query results are shown as {% data variables.product.prodname_code_scanning %} alerts in {% data variables.product.product_name %} when you use {% data variables.product.prodname_codeql %} with {% data variables.product.prodname_code_scanning %}. +1. Você gera um banco de dados de {% data variables.product.prodname_codeql %} para representar a sua base de código. +2. Em seguida, você executa consultas de {% data variables.product.prodname_codeql %} nesse banco de dados para identificar problemas na base de código. +3. Os resultados da consulta são exibidos como alertas de {% data variables.product.prodname_code_scanning %} em {% data variables.product.product_name %} quando você usa {% data variables.product.prodname_codeql %} com {% data variables.product.prodname_code_scanning %}. O {% data variables.product.prodname_codeql %} é compatível com linguagens compiladas e interpretadas e é capaz de encontrar vulnerabilidades e erros no código escrito nos idiomas suportados. {% data reusables.code-scanning.codeql-languages-bullets %} -## About {% data variables.product.prodname_codeql %} queries +## Sobre consultas de {% data variables.product.prodname_codeql %} -{% data variables.product.company_short %} experts, security researchers, and community contributors write and maintain the default {% data variables.product.prodname_codeql %} queries used for {% data variables.product.prodname_code_scanning %}. The queries are regularly updated to improve analysis and reduce any false positive results. The queries are open source, so you can view and contribute to the queries in the [`github/codeql`](https://github.com/github/codeql) repository. Para obter mais informações, consulte [{% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql) no site do GitHub Security Lab. You can also write your own queries. For more information, see "[About {% data variables.product.prodname_codeql %} queries](https://codeql.github.com/docs/writing-codeql-queries/about-codeql-queries/)" in the {% data variables.product.prodname_codeql %} documentation. +{% data variables.product.company_short %} especialistas, pesquisadores de segurança e contribuidores da comunidade escrevem e mantêm as consultas padrão de {% data variables.product.prodname_codeql %} usadas por {% data variables.product.prodname_code_scanning %}. As consultas são regularmente atualizadas para melhorar a análise e reduzir quaisquer resultados falso-positivos. As consultas são de código aberto.Portanto, você pode ver e contribuir para as consultas no repositório [`github/codeql`](https://github.com/github/codeql). Para obter mais informações, consulte [{% data variables.product.prodname_codeql %}](https://securitylab.github.com/tools/codeql) no site do GitHub Security Lab. Você também pode escrever suas próprias consultas. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_codeql %} consultas](https://codeql.github.com/docs/writing-codeql-queries/about-codeql-queries/)" na documentação do {% data variables.product.prodname_codeql %}. -You can run additional queries as part of your code scanning analysis. +Você pode executar consultas adicionais como parte da sua análise de digitalização de código. {%- if codeql-packs %} -These queries must belong to a published {% data variables.product.prodname_codeql %} query pack (beta) or a QL pack in a repository. {% data variables.product.prodname_codeql %} packs (beta) provide the following benefits over traditional QL packs: +Essas consultas devem pertencer a um pacote de consulta de {% data variables.product.prodname_codeql %} publicado (beta) ou um pacote QL em um repositório. Os pacotes (beta) de {% data variables.product.prodname_codeql %} oferecem os seguintes benefícios sobre os pacotes QL tradicionais: -- When a {% data variables.product.prodname_codeql %} query pack (beta) is published to the {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %}, all the transitive dependencies required by the queries and a compilation cache are included in the package. This improves performance and ensures that running the queries in the pack gives identical results every time until you upgrade to a new version of the pack or the CLI. -- QL packs do not include transitive dependencies, so queries in the pack can depend only on the standard libraries (that is, the libraries referenced by an `import LANGUAGE` statement in your query), or libraries in the same QL pack as the query. +- Quando um pacote de consulta (beta) {% data variables.product.prodname_codeql %} é publicado em {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %}, todas as dependências transitórias exigidas pelas consultas e um cache de compilação estão incluídas no pacote. Isto melhora o desempenho e garante que a execução de consultas no pacote dê resultados idênticos toda vez até que você fizer a autalização para uma nova versão do pacote ou para o CLI. +- Os pacotes de QL não incluem dependências transitórias. Portanto, as consultas no pacote podem depender apenas das bibliotecas padrão (ou seja, as bibliotecas referenciadas por uma instrução `LINGUAGEM de importação` na sua consulta), ou bibliotecas no mesmo pacote QL da consulta. -For more information, see "[About {% data variables.product.prodname_codeql %} packs](https://codeql.github.com/docs/codeql-cli/about-codeql-packs/)" and "[About {% data variables.product.prodname_ql %} packs](https://codeql.github.com/docs/codeql-cli/about-ql-packs/)" in the {% data variables.product.prodname_codeql %} documentation. +Para obter mais informações, consulte "[Sobre pacotes de {% data variables.product.prodname_codeql %}](https://codeql.github.com/docs/codeql-cli/about-codeql-packs/)" e "[Sobre pacotes de {% data variables.product.prodname_ql %}](https://codeql.github.com/docs/codeql-cli/about-ql-packs/)" na documentação de {% data variables.product.prodname_codeql %}. {% data reusables.code-scanning.beta-codeql-packs-cli %} {%- else %} -The queries you want to run must belong to a QL pack in a repository. Queries must only depend on the standard libraries (that is, the libraries referenced by an `import LANGUAGE` statement in your query), or libraries in the same QL pack as the query. Para obter mais informações, consulte "[Sobre os pacotes de {% data variables.product.prodname_ql %}](https://codeql.github.com/docs/codeql-cli/about-ql-packs/). +As consultas que você deseja executar devem pertencer a um pacote QL em um repositório. As consultas só devem depender das bibliotecas-padrão (ou seja, as bibliotecas referenciadas por uma declaração de `LINGUAGEM de importação` na sua consulta), ou bibliotecas no mesmo pacote QL da consulta. Para obter mais informações, consulte "[Sobre os pacotes de {% data variables.product.prodname_ql %}](https://codeql.github.com/docs/codeql-cli/about-ql-packs/). {% endif %} diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md index 4c583dca74..a01cc79478 100644 --- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md +++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md @@ -42,13 +42,13 @@ Para começar com {% data variables.product.prodname_code_scanning %}, consulte {% endif %} -## About tools for {% data variables.product.prodname_code_scanning %} +## Sobre ferramentas para {% data variables.product.prodname_code_scanning %} -You can set up {% data variables.product.prodname_code_scanning %} to use the {% data variables.product.prodname_codeql %} product maintained by {% data variables.product.company_short%} or a third-party {% data variables.product.prodname_code_scanning %} tool. +Você pode configurar {% data variables.product.prodname_code_scanning %} para usar o produto de {% data variables.product.prodname_codeql %} mantido por {% data variables.product.company_short%} ou pela ferramenta {% data variables.product.prodname_code_scanning %} de terceiros. -### About {% data variables.product.prodname_codeql %} analysis +### Sobre a análise de {% data variables.product.prodname_codeql %} -{% data reusables.code-scanning.about-codeql-analysis %} For more information about {% data variables.product.prodname_codeql %}, see "[About code scanning with CodeQL](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)." +{% data reusables.code-scanning.about-codeql-analysis %} Para obter mais informações sobre {% data variables.product.prodname_codeql %}, consulte "[Sobre digitalização de código com CodeQL](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)". ### Sobre ferramentas de {% data variables.product.prodname_code_scanning %} de terceiros 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 3a323bfb82..380aa6111d 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 @@ -68,24 +68,26 @@ Se você usar o fluxo de trabalho padrão, o {% data variables.product.prodname_ Se você fizer uma varredura no push, os resultados aparecerão na aba **Segurança** do repositório. Para obter mais informações, consulte "[Gerenciar alertas de varredura de código para seu repositório](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository). " -{% note %} - -**Observação**: se você deseja que os alertas de {% data variables.product.prodname_code_scanning %} sejam exibidos como verificações de pull request, você deverá usar o evento `pull_request` descrito abaixo. - -{% endnote %} +{% ifversion fpt or ghes > 3.2 or ghae-issue-5093 %} +Além disso, quando uma verificação de `on:push` retorna resultados que podem ser mapeados com um pull request aberto, esses alertas serão automaticamente exibidos no pull request nos mesmos lugares que outros alertas de pull request. Os alertas são identificados comparando a análise existente do cabeçalho do branch com a análise do branch de destino. Para obter mais informações sobre alertas de {% data variables.product.prodname_code_scanning %} em pull requests, consulte "[Triando alertas de {% data variables.product.prodname_code_scanning %} em pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)". +{% endif %} ### Fazer a varredura de pull requests -O padrão {% data variables.product.prodname_codeql_workflow %} usa o evento `pull_request` para acionar uma verificação de código em pull requests direcionadas ao branch padrão. {% ifversion ghes %}O evento `pull_request` não será acionado se o pull request foi aberto através de uma bifurcação privada.{% else %}Se um pull request for de um fork privado, o evento `pull_request` só será acionado se você tiver selecionado a opção "Executar fluxos de trabalho a partir de pull requests" nas configurações do repositório. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#enabling-workflows-for-private-repository-forks)."{% endif %} +O padrão {% data variables.product.prodname_codeql_workflow %} usa o evento `pull_request` para acionar uma verificação de código em pull requests direcionadas ao branch padrão. {% ifversion ghes %}O evento `pull_request` não será acionado se o pull request foi aberto através de uma bifurcação privada.{% else %}Se um pull request for de um fork privado, o evento `pull_request` só será acionado se você tiver selecionado a opção "Executar fluxos de trabalho a partir de pull requests" nas configurações do repositório. Para obter mais informações, consulte "[Gerenciar 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#enabling-workflows-for-private-repository-forks)".{% endif %} Para obter mais informações sobre o evento `pull_request` , consulte "[Sintaxe de fluxo de trabalho para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags)". Se você realizar uma varredura de pull requests, os resultados aparecerão como alertas em uma verificação de pull request. Para obter mais informações, consulte "[Alertas de varredura de código de triagem em pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)". -{% ifversion fpt or ghes > 3.1 or ghae-next %} -### Defining the severities causing pull request check failure +{% ifversion fpt or ghes > 3.2 or ghae-issue-5093 %} + O uso o gatilho `pull_request`, configurado para verificar o commit de merge do pull request, em vez do commit do cabeçalho, produzirá resultados mais eficientes e precisos do que digitalizar o cabeçalho do branch em cada push. No entanto, se você usa um sistema de CI/CD que não pode ser configurado para acionar em pull requests, você ainda poderá usar o gatilho `on:push` e {% data variables.product.prodname_code_scanning %} mapeará os resultados para abrir os pull requests no branch e adicionar os alertas como anotações no 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 %} -By default, only alerts with the severity level of `Error`{% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %} or security severity level of `Critical` or `High`{% endif %} will cause a pull request check failure, and a check will still succeed with alerts of lower severities. You can change the levels of alert severities{% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %} and of security severities{% endif %} that will cause a pull request check failure in your repository settings. For more information about severity levels, see "[Managing code scanning alerts for your repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#about-alerts-details)." +{% ifversion fpt or ghes > 3.1 or ghae-next %} +### Definindo as severidades que causam falha na verificação de pull request + +Por padrão, apenas os alertas com o nível de gravidade `Error`{% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %} ou nível de segurança `Critical` ou `High`{% endif %} farão com que ocorra uma falha no pull request e uma verificação será bem-sucedida com alertas de menor gravidade. É possível alterar os níveis de gravide dos alertas{% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %} e de gravidades de segurança{% endif %} que causarão uma falha de verificação de pull request nas configurações do seu repositório. Para obter mais informações sobre os níveis de gravidade, consulte "[Gerenciar alertas de digitalização de códigos para o seu repositório](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#about-alerts-details). {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} @@ -234,7 +236,6 @@ Alternativamente, você pode instalar as dependências do Python manualmente em ```yaml jobs: CodeQL-Build: - runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae-next %} permissions: security-events: write @@ -266,7 +267,7 @@ jobs: ``` {% endif %} -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ## Configurar uma categoria para a análise Use a `categoria` para distinguir entre múltiplas análises para a mesma ferramenta e commit, mas executada em diferentes linguagens ou diferentes partes do código. A categoria especificada no seu fluxo de trabalho será incluída no arquivo de resultados SARIF. @@ -300,19 +301,19 @@ Sua categoria especificada não substituirá os detalhes do objeto `runAutomatio {% data reusables.code-scanning.run-additional-queries %} {% if codeql-packs %} -### Using {% data variables.product.prodname_codeql %} query packs +### Usando pacotes de consulta de {% data variables.product.prodname_codeql %} {% data reusables.code-scanning.beta-codeql-packs-cli %} -To add one or more {% data variables.product.prodname_codeql %} query packs (beta), add a `with: packs:` entry within the `uses: github/codeql-action/init@v1` section of the workflow. Within `packs` you specify one or more packages to use and, optionally, which version to download. Where you don't specify a version, the latest version is downloaded. If you want to use packages that are not publicly available, you need to set the `GITHUB_TOKEN` environment variable to a secret that has access to the packages. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)" and "[Encrypted secrets](/actions/reference/encrypted-secrets)." +Para adicionar um ou mais pacotes de consulta (beta) de {% data variables.product.prodname_codeql %}, adicione uma entrada `with: packs` à seção `uses: github/codeql-action/init@v1` do fluxo de trabalho. Dentro de `pacotes` você especifica um ou mais pacotes para usar e, opcionalmente, qual versão baixar. Quando você não especificar uma versão, será feito o download da versão mais recente. Se você quiser usar pacotes que não estão disponíveis publicamente, você precisa definir a variável de ambiente `GITHUB_TOKEN` para um segredo que tenha acesso aos pacotes. Para obter mais informações, consulte "[Autenticação em um fluxo de trabalho](/actions/reference/authentication-in-a-workflow)" e "[Segredos criptografados](/actions/reference/encrypted-secrets)". {% note %} -**Note:** For workflows that generate {% data variables.product.prodname_codeql %} databases for multiple languages, you must instead specify the {% data variables.product.prodname_codeql %} query packs in a configuration file. For more information, see "[Specifying {% data variables.product.prodname_codeql %} query packs](#specifying-codeql-query-packs)" below. +**Observação:** Para fluxos de trabalho que geram bancos de dados de {% data variables.product.prodname_codeql %} para várias linguagens, você deverá especificar pacotes de consulta de {% data variables.product.prodname_codeql %} em um arquivo de configuração. Para obter mais informações, consulte "[Especificando pacotes de consulta {% data variables.product.prodname_codeql %}](#specifying-codeql-query-packs)" abaixo. {% endnote %} -In the example below, `scope` is the organization or personal account that published the package. When the workflow runs, the three {% data variables.product.prodname_codeql %} query packs are downloaded from {% data variables.product.product_name %} and the default queries or query suite for each pack run. The latest version of `pack1` is downloaded as no version is specified. Version 1.2.3 of `pack2` is downloaded, as well as the latest version of `pack3` that is compatible with version 1.2.3. +No exemplo abaixo, `escopo` é toda organização ou conta pessoal que publicou o pacote. Quando o fluxo de trabalho é executado, os três pacotes de consulta de {% data variables.product.prodname_codeql %} são baixados de {% data variables.product.product_name %} e das consultas ou conjunto de consultas padrão para cada execução de pacote. É feito o download da versão mais recente do `pack1`, pois nenhuma versão é especificada. A versão 1.2.3 de `pack2` é baixada, bem como a última versão de `pack3` que é compatível com a versão 1.2.3. {% raw %} ``` yaml @@ -323,16 +324,16 @@ In the example below, `scope` is the organization or personal account that publi ``` {% endraw %} -### Using queries in QL packs +### Usando consultas em pacotes QL {% endif %} -Para adicionar uma ou mais consultas, adicione uma entrada `with: queries:` na seção `uses: github/codeql-action/init@v1` do fluxo de trabalho. If the queries are in a private repository, use the `external-repository-token` parameter to specify a token that has access to checkout the private repository. +Para adicionar uma ou mais consultas, adicione uma entrada `with: queries:` na seção `uses: github/codeql-action/init@v1` do fluxo de trabalho. Se as consultas estiverem em um repositório privado, use o parâmetro `external-repository-token` para especificar um token que tenha acesso ao check-out do repositório privado. {% raw %} ``` yaml - uses: github/codeql-action/init@v1 with: queries: COMMA-SEPARATED LIST OF PATHS - # Optional. Provide a token to access queries stored in private repositories. + # Optional. Forneça um token de acesso para consultas armazenadas em repositórios privados. external-repository-token: ${{ secrets.ACCESS_TOKEN }} ``` {% endraw %} @@ -342,12 +343,12 @@ Você também pode executar suítes de consultas adicionais especificando-os em {% data reusables.code-scanning.codeql-query-suites %} {% if codeql-packs %} -### Working with custom configuration files +### Trabalhando com arquivos de configuração personalizados {% endif %} -If you also use a configuration file for custom settings, any additional {% if codeql-packs %}packs or {% endif %}queries specified in your workflow are used instead of those specified in the configuration file. If you want to run the combined set of additional {% if codeql-packs %}packs or {% endif %}queries, prefix the value of {% if codeql-packs %}`packs` or {% endif %}`queries` in the workflow with the `+` symbol. Para obter exemplos de arquivos de configuração, consulte "[Exemplo de arquivos de configuração](#example-configuration-files)". +Se você também usar um arquivo de configuração para configurações personalizadas, todas os {% if codeql-packs %}pacotes ou {% endif %}consultas especificadas no seu fluxo de trabalho serão usados em vez daqueles especificados no arquivo de configuração. Se você quiser executar o conjunto combinado de {% if codeql-packs %}pacotes adicionais ou {% endif %}consultas, prefixe o valor de {% if codeql-packs %}`pacotes` ou {% endif %}`consultas` no fluxo de trabalho com o símbolo `+`. Para obter exemplos de arquivos de configuração, consulte "[Exemplo de arquivos de configuração](#example-configuration-files)". -In the following example, the `+` symbol ensures that the specified additional {% if codeql-packs %}packs and {% endif %}queries are used together with any specified in the referenced configuration file. +No exemplo a seguir, o símbolo `+` garante que os {% if codeql-packs %}pacotes e {% endif %}consultas especificados sejam usados em conjunto com qualquer um especificado no arquivo de configuração referenciado. ``` yaml - uses: github/codeql-action/init@v1 @@ -361,7 +362,7 @@ In the following example, the `+` symbol ensures that the specified additional { ## Usar uma ferramenta de varredura de código de terceiros -A custom configuration file is an alternative way to specify additional {% if codeql-packs %}packs and {% endif %}queries to run. You can also use the file to disable the default queries and to specify which directories to scan during analysis. +Um arquivo de configuração personalizado é uma forma alternativa de especificar as consultas adicionais de {% if codeql-packs %}e {% endif %}a serem executadas. Você também pode usar o arquivo para desabilitar as consultas padrão e especificar quais diretórios digitalizar durante a análise. No arquivo de workflow use o parâmetro `config-file` da ação `init` para especificar o caminho para o arquivo de configuração que você deseja usar. Este exemplo carrega o arquivo de configuração _./.github/codeql/codeql-config.yml_. @@ -386,11 +387,11 @@ Se o arquivo de configuração estiver localizado em um repositório privado ext As configurações no arquivo de configuração estão escritas no formato YAML. {% if codeql-packs %} -### Specifying {% data variables.product.prodname_codeql %} query packs +### Especificando pacotes de consulta de {% data variables.product.prodname_codeql %} {% data reusables.code-scanning.beta-codeql-packs-cli %} -You specify {% data variables.product.prodname_codeql %} query packs in an array. Note that the format is different from the format used by the workflow file. +Você especificou pacotes de consulta de {% data variables.product.prodname_codeql %} em uma matriz. Observe que o formato é diferente do formato usado pelo arquivo do fluxo de trabalho. {% raw %} ``` yaml @@ -404,7 +405,7 @@ packs: ``` {% endraw %} -If you have a workflow that generates more than one {% data variables.product.prodname_codeql %} database, you can specify any {% data variables.product.prodname_codeql %} query packs to run in a custom configuration file using a nested map of packs. +Se tiver um fluxo de trabalho que gera mais de um banco de dados de {% data variables.product.prodname_codeql %}, você poderá especificar todos os pacotes de consulta de {% data variables.product.prodname_codeql %} para executar em um arquivo de configuração personalizado usando um mapa aninhado de pacotes. {% raw %} ``` yaml diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md index a002f7461b..dfdac96c58 100644 --- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md @@ -36,7 +36,7 @@ Por padrão, {% data variables.product.prodname_code_scanning %} analisa seu có ## Sobre detalhes de alertas -Cada alerta destaca um problema com o código e o nome da ferramenta que o identificou. You can see the line of code that triggered the alert, as well as properties of the alert, such as the severity{% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %}, security severity,{% endif %} and the nature of the problem. Os alertas também informam quando o problema foi introduzido pela primeira vez. Para os alertas identificados pela análise do {% data variables.product.prodname_codeql %} , você também verá informações sobre como corrigir o problema. +Cada alerta destaca um problema com o código e o nome da ferramenta que o identificou. Você pode ver a linha de código que acionou o alerta, bem como as propriedades do alerta, como, por exemplo, a gravidade{% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %}, gravidade da segurança,{% endif %} e a natureza do problema. Os alertas também informam quando o problema foi introduzido pela primeira vez. Para os alertas identificados pela análise do {% data variables.product.prodname_codeql %} , você também verá informações sobre como corrigir o problema. ![Exemplo de alerta de {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-alert.png) @@ -44,20 +44,20 @@ Se você configurar o {% data variables.product.prodname_code_scanning %} usando Quando {% data variables.product.prodname_code_scanning %} relata alertas de fluxo de dados, {% data variables.product.prodname_dotcom %} mostra como os dados se movem através do código. {% data variables.product.prodname_code_scanning_capc %} permite que você identifique as áreas do seu código que vazam informações confidenciais que poderia ser o ponto de entrada para ataques de usuários maliciosos. -### About severity levels +### Sobre os níveis de gravidade -Alert severity levels may be `Error`, `Warning`, or `Note`. +Níveis de gravidade do alerta podem ser `Error`, `Warning` ou `Note`. -By default, any code scanning results with a severity of `error` will cause check failure. {% ifversion fpt or ghes > 3.1 or ghae-next %}You can specify the severity level at which pull requests that trigger code scanning alerts should fail. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %} +Por padrão, qualquer resultado de digitalização de código com uma gravidade de `error` irá gerar uma falha de verificação. {% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %}Você pode especificar o nível de gravidade no qual os pull requests que habilitam alertas de verificação de código devem falhar. Para obter mais informações, consulte[Definir as gravidades causadoras da falha de verificação de pull request](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %} -### About security severity levels +{% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %} +### Sobre níveis de gravidade de segurança -{% data variables.product.prodname_code_scanning_capc %} displays security severity levels for alerts that are generated by security queries. Security severity levels can be `Critical`, `High`, `Medium`, or `Low`. +{% data variables.product.prodname_code_scanning_capc %} exibe níveis de gravidade de segurança para alertas gerados por consultas de segurança. Níveis de severidade de segurança podem ser `graves`, `altos`, `médios` ou `baixos`. -To calculate the security severity of an alert, we use Common Vulnerability Scoring System (CVSS) data. CVSS is an open framework for communicating the characteristics and severity of software vulnerabilities, and is commonly used by other security products to score alerts. For more information about how severity levels are calculated, see [the blog post](https://github.blog/changelog/2021-07-19-codeql-code-scanning-new-severity-levels-for-security-alerts/). +Para calcular a gravidade da segurança de um alerta, usamos dados de Pontuação do Sistema de Vulnerabilidade Comum (CVSS). O CVSS é uma estrutura aberta para comunicar as características e gravidade das vulnerabilidades de software, e é comumente usado por outros produtos de segurança para pontuar alertas. Para obter mais informações sobre como os níveis de gravidade são calculados, consulte [o post do blogue](https://github.blog/changelog/2021-07-19-codeql-code-scanning-new-severity-levels-for-security-alerts/). -By default, any code scanning results with a security severity of `Critical` or `High` will cause a check failure. You can specify which security severity level for code scanning results should cause a check failure. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %} +Por padrão, qualquer resultado de verificação de código com uma gravidade de segurança de `Grave` ou `Alta` irá causar uma falha de verificação. Você pode especificar qual nível de segurança para os resultados da digitalização do código deve causar uma falha de verificação. Para obter mais informações, consulte[Definir as gravidades causadoras da falha de verificação de pull request](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %} ## Visualizar os alertas de um repositório @@ -65,15 +65,15 @@ Qualquer pessoa com permissão de leitura para um repositório pode ver anotaç Você precisa de permissão de gravação para visualizar um resumo de todos os alertas para um repositório na aba **Segurança**. -By default, the code scanning alerts page is filtered to show alerts for the default branch of the repository only. +Por padrão, a página de verificação de código de alertas é filtrada para mostrar alertas apenas para o branch padrão do repositório. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-code-scanning-alerts %} -{% ifversion fpt or ghes > 3.1 %} -1. Opcionalmente, use{% ifversion fpt or ghes > 3.1 %} a caixa de pesquisa de texto livre ou{% endif %} os menus suspensos para filtrar alertas. Por exemplo, você pode filtrar pela ferramenta usada para identificar alertas. ![Filter by tool](/assets/images/help/repository/code-scanning-filter-by-tool.png){% endif %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} +1. Opcionalmente, use a caixa de pesquisa de texto livre ou os menus suspensos para filtrar alertas. Por exemplo, você pode filtrar pela ferramenta usada para identificar alertas. ![Filter by tool](/assets/images/help/repository/code-scanning-filter-by-tool.png){% endif %} 1. Em "{% data variables.product.prodname_code_scanning_capc %}", clique no alerta que você gostaria de explorar. -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ![Resumo dos alertas](/assets/images/help/repository/code-scanning-click-alert.png) {% else %} ![Lista de alertas de {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) @@ -81,7 +81,7 @@ By default, the code scanning alerts page is filtered to show alerts for the def 1. Opcionalmente, se o alerta destacar um problema com o fluxo de dados, clique em **Mostrar caminhos** para exibir o caminho da fonte de dados até o destino onde é usado. ![O link "Exibir caminhos" em um alerta](/assets/images/help/repository/code-scanning-show-paths.png) 1. Alertas da análise de {% data variables.product.prodname_codeql %} incluem uma descrição do problema. Clique em **Mostrar mais** para obter orientação sobre como corrigir seu código. ![Detalhes para um alerta](/assets/images/help/repository/code-scanning-alert-details.png) -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} {% note %} **Observação:** Para análise de {% data variables.product.prodname_code_scanning %} com {% data variables.product.prodname_codeql %}, você pode ver informações sobre a última execução em um cabeçalho na parte superior da lista de alertas de {% data variables.product.prodname_code_scanning %} para o repositório. @@ -91,21 +91,34 @@ Por exemplo, você pode ver quando o último scanner foi executada, o número de {% endnote %} {% endif %} +## Filtrando alertas de {% data variables.product.prodname_code_scanning %} -## Filtering {% data variables.product.prodname_code_scanning %} alerts +Você pode filtrar os alertas exibidos no modo de exibição de alertas de {% data variables.product.prodname_code_scanning %}. Isso é útil caso haja muitos alertas pois você pode se concentrar em um determinado tipo de alerta. Existem alguns filtros predefinidos e uma série de palavras-chave que você pode usar para refinar a lista de alertas exibidos. -You can filter the alerts shown in the {% data variables.product.prodname_code_scanning %} alerts view. This is useful if there are many alerts as you can focus on a particular type of alert. There are some predefined filters and a range of keywords that you can use to refine the list of alerts displayed. - -- To use a predefined filter, click **Filters**, or a filter shown in the header of the list of alerts, and choose a filter from the drop-down list. - {% ifversion fpt or ghes > 3.0 %}![Predefined filters](/assets/images/help/repository/code-scanning-predefined-filters.png) +- Para usar um filtro predefinido, clique **Filtros** ou em um filtro exibido no cabeçalho da lista de alertas e escolha um filtro na lista suspensa. + {% ifversion fpt or ghes > 3.0 %}![Filtros predefinidos](/assets/images/help/repository/code-scanning-predefined-filters.png) {% else %}![Predefined filters](/assets/images/enterprise/3.0/code-scanning-predefined-filters.png){% endif %} -- To use a keyword, either type directly in the filters text box, or: - 1. Click in the filters text box to show a list of all available filter keywords. - 2. Click the keyword you want to use and then choose a value from the drop-down list. ![Keyword filters list](/assets/images/help/repository/code-scanning-filter-keywords.png) +- Para usar uma palavra-chave, digite diretamente na caixa de texto dos filtros ou: + 1. Clique na caixa de filtros para exibir uma lista de todas as palavras-chave de filtro disponíveis. + 2. Clique na palavra-chave que deseja usar e, em seguida, selecione um valor na lista suspensa. ![Lista de filtros de palavra-chave](/assets/images/help/repository/code-scanning-filter-keywords.png) -The benefit of using keyword filters is that only values with results are shown in the drop-down lists. This makes it easy to avoid setting filters that find no results. +O benefício de usar filtros de palavra-chave é que apenas os valores com resultados são exibidos nas listas suspensas. Isso facilita evitar filtros de configuração que não encontram resultados. + +Se você inserir vários filtros, a visualização mostrará alertas que correspondem a _todos_ esses filtros. Por exemplo, `is:closed severity:high branch:main` só exibirá alertas de alta gravidade fechados e que estão presentes no branch `principal`. A exceção são os filtros relacionados a refs (`ref`, `branch` e `pr`): `is:open branch:main branch:next` irá mostrar alertas abertos do branch `principal` do `próximo` branch. + +### Restringir resultados apenas ao código do aplicativo + +Você pode usar o filtro "Apenas alertas no código do aplicativo" ou a palavra-chave `autofilter:true` e valor para restringir os resultados de alertas no código do aplicativo. O código do aplicativo exclui o seguinte. + +- Código gerado pelo processo de compilação +- Código de teste +- Biblioteca ou código de terceiros +- Documentação + +{% data variables.product.prodname_code_scanning_capc %} categoriza arquivos por caminho do arquivo. No momento, você não pode categorizar manualmente os arquivos de origem. {% ifversion fpt or ghes > 3.1 %} + ## Pesquisando alertas de {% data variables.product.prodname_code_scanning %} Você pode pesquisar na lista de alertas. Isso é útil se houver um grande número de alertas no seu repositório, ou, por exemplo, se você não souber o nome exato de um alerta. {% data variables.product.product_name %} realiza a pesquisa de texto livre: @@ -145,11 +158,11 @@ Qualquer pessoa com permissão de gravação para um repositório pode corrigir Se você tem permissão de escrita em um repositório, você pode visualizar alertas corrigidos, vendo o resumo de alertas e clicando em **Fechado**. Para obter mais informações, consulte "[Visualizar os alertas de um repositório](#viewing-the-alerts-for-a-repository). A lista "Fechado" mostra alertas e alertas corrigidos que os usuários ignoraram. -Você pode usar{% ifversion fpt or ghes > 3.1 %} a pesquisa de texto livre ou{% endif %} os filtros para exibir um subconjunto de alertas e, em seguida, marcar, por sua vez, todos os alertas correspondentes como fechados. +Você pode usar{% ifversion fpt or ghes > 3.1 or ghae-next %} a pesquisa de texto livre ou{% endif %} os filtros para exibir um subconjunto de alertas e, em seguida, marcar, por sua vez, todos os alertas correspondentes como fechados. Alertas podem ser corrigidos em um branch, mas não em outro. Você pode usar o menu suspenso "Branch", no resumo dos alertas, para verificar se um alerta é corrigido em um branch específico. -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ![Filtrar alertas por branch](/assets/images/help/repository/code-scanning-branch-filter.png) {% else %} ![Filtrar alertas por branch](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png) @@ -185,9 +198,9 @@ Para ignorar ou excluir alertas: ![Excluir alertas](/assets/images/help/repository/code-scanning-delete-alerts.png) - Opcionalmente, você pode usar{% ifversion fpt or ghes > 3.1 %}} a pesquisa de texto livre ou{% endif %} os filtros para exibir um subconjunto de alertas e, em seguida, excluir todos os alertas correspondentes de uma só vez. Por exemplo, se você removeu uma consulta da análise de {% data variables.product.prodname_codeql %}, você pode usar o filtro "Regra" para listar apenas os alertas dessa consulta e, em seguida, selecionar e apagar todos esses alertas. + Opcionalmente, você pode usar{% ifversion fpt or ghes > 3.1 or ghae-next %}} a pesquisa de texto livre ou{% endif %} os filtros para exibir um subconjunto de alertas e, em seguida, excluir todos os alertas correspondentes de uma só vez. Por exemplo, se você removeu uma consulta da análise de {% data variables.product.prodname_codeql %}, você pode usar o filtro "Regra" para listar apenas os alertas dessa consulta e, em seguida, selecionar e apagar todos esses alertas. -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ![Filtrar alertas por regra](/assets/images/help/repository/code-scanning-filter-by-rule.png) {% else %} ![Filtrar alertas por regra](/assets/images/enterprise/3.1/help/repository/code-scanning-filter-by-rule.png) @@ -195,12 +208,11 @@ Para ignorar ou excluir alertas: 1. Se você deseja ignorar um alerta, é importante explorar primeiro o alerta para que você possa escolher o motivo correto para ignorá-lo. Clique no alerta que você deseja explorar. -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ![Abrir um alerta da lista de resumo](/assets/images/help/repository/code-scanning-click-alert.png) {% else %} ![Lista de alertas de {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) {% endif %} - 1. Revise o alerta e clique em **Ignorar** e escolha um motivo para fechar o alerta. ![Escolher um motivo para ignorar um alerta](/assets/images/help/repository/code-scanning-alert-close-drop-down.png) {% data reusables.code-scanning.choose-alert-dismissal-reason %} 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 6dd0f551ad..49319f412d 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 @@ -40,8 +40,8 @@ Você decide como gerar alertas de {% data variables.product.prodname_code_scann {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} -3. À direita dos " alertas de {% data variables.product.prodname_code_scanning_capc %}", clique em **Configurar {% data variables.product.prodname_code_scanning %}**. {% ifversion fpt or ghes > 3.0 %}Se {% data variables.product.prodname_code_scanning %} está faltando, peça ao proprietário da organização ou administrador do repositório para habilitar {% data variables.product.prodname_GH_advanced_security %}. Para mais informações consulte "[Gerenciar as configurações de segurança e análise para a sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" ou "[Gerenciar as configurações de segurança e análise para o seu repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository).{% endif %} ![Botão "Configurar {% data variables.product.prodname_code_scanning %}" à direita de "{% data variables.product.prodname_code_scanning_capc %}" na Visão Geral de Segurança](/assets/images/help/security/overview-set-up-code-scanning.png) -4. Em "Começar com {% data variables.product.prodname_code_scanning %}", clique em **Configurar este fluxo de trabalho** no {% data variables.product.prodname_codeql_workflow %} ou em um fluxo de trabalho de terceiros. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png){% ifversion fpt or ghes > 2.22 %}Os fluxos de trabalho são exibidos apenas se forem relevantes para as linguagens de programação detectadas no repositório. O {% data variables.product.prodname_codeql_workflow %} é sempre exibido, mas o botão "Configurar este fluxo de trabalho" só é habilitado se a análise de {% data variables.product.prodname_codeql %} for compatível com as linguagens presentes no repositório.{% endif %} +3. À direita dos " alertas de {% data variables.product.prodname_code_scanning_capc %}", clique em **Configurar {% data variables.product.prodname_code_scanning %}**. {% ifversion fpt or ghes > 3.0 or ghae-next %}Se {% data variables.product.prodname_code_scanning %} está faltando, peça ao proprietário da organização ou administrador do repositório para habilitar {% data variables.product.prodname_GH_advanced_security %}. Para mais informações consulte "[Gerenciar as configurações de segurança e análise para a sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" ou "[Gerenciar as configurações de segurança e análise para o seu repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository).{% endif %} ![Botão "Configurar {% data variables.product.prodname_code_scanning %}" à direita de "{% data variables.product.prodname_code_scanning_capc %}" na Visão Geral de Segurança](/assets/images/help/security/overview-set-up-code-scanning.png) +4. Em "Começar com {% data variables.product.prodname_code_scanning %}", clique em **Configurar este fluxo de trabalho** no {% data variables.product.prodname_codeql_workflow %} ou em um fluxo de trabalho de terceiros. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png){% ifversion fpt or ghes > 2.22 or ghae-next %}Os fluxos de trabalho são exibidos apenas se forem relevantes para as linguagens de programação detectadas no repositório. O {% data variables.product.prodname_codeql_workflow %} é sempre exibido, mas o botão "Configurar este fluxo de trabalho" só é habilitado se a análise de {% data variables.product.prodname_codeql %} for compatível com as linguagens presentes no repositório.{% endif %} 5. Para personalizar como {% data variables.product.prodname_code_scanning %} faz a varredura do seu código, edite o fluxo de trabalho. Geralmente, você pode fazer commit do {% data variables.product.prodname_codeql_workflow %} sem fazer nenhuma alteração nele. No entanto, muitos dos fluxos de trabalho de terceiros exigem uma configuração adicional. Portanto, leia os comentários no fluxo de trabalho antes de fazer o commit. @@ -53,9 +53,42 @@ Você decide como gerar alertas de {% data variables.product.prodname_code_scann No {% data variables.product.prodname_codeql_workflow %} padrão, {% data variables.product.prodname_code_scanning %} está configurado para analisar o seu código cada vez que você fizer push de uma alteração no branch-padrão ou em qualquer branch protegido, ou criar um pull request contra o branch padrão. Como resultado, {% data variables.product.prodname_code_scanning %} vai começar agora. +Os gatilhos `on:pull_request` e `on:push` para digitalização de código são úteis para diferentes finalidades. Para obter mais informações, consulte "[Digitalizando pull requests](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-pull-requests)" e "[Digitalizando ao fazer push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)". ## Configuração em massa de {% data variables.product.prodname_code_scanning %} -Você pode configurar {% data variables.product.prodname_code_scanning %} em vários repositórios de uma vez usando um script. If you'd like to use a script to raise pull requests that add a {% data variables.product.prodname_actions %} workflow to multiple repositories, see the [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) repository for an example using Powershell, or [`nickliffen/ghas-enablement`](https://github.com/NickLiffen/ghas-enablement) for teams who do not have Powershell and instead would like to use NodeJS. +Você pode configurar {% data variables.product.prodname_code_scanning %} em vários repositórios de uma vez usando um script. Se você desejar de usar um script para levantar pull requests que adicionam um fluxo de trabalho de {% data variables.product.prodname_actions %} a vários repositórios, consulte o repositório [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) para ver um exemplo usando Powershell ou [`nickliffen/ghas-enablement`](https://github.com/NickLiffen/ghas-enablement) para equipes que não possuem Powershell e que gostariam de usar o NodeJS. + +## Visualizar a saída do registro de {% data variables.product.prodname_code_scanning %} + +Depois de configurar o {% data variables.product.prodname_code_scanning %} para o seu repositório, você poderá inspecionar a saída das ações conforme forem executadas. + +{% data reusables.repositories.actions-tab %} + + Você verá uma lista que inclui uma entrada para executar o fluxo de trabalho de {% data variables.product.prodname_code_scanning %}. O texto da entrada é o título que você deu à sua mensagem de commit. + + ![Lista de ações que mostram o fluxo de trabalho de {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-actions-list.png) + +1. Clique na entrada para o fluxo de trabalho de {% data variables.product.prodname_code_scanning %}. + +1. Clique no nome do trabalho à esquerda. Por exemplo, **Analise (LANGUAGE)**. + + ![Saída do log do fluxo de trabalho de {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-logging-analyze-action.png) + +1. Revise a saída de log das ações deste fluxo de trabalho enquanto elas são executadas. + +1. Depois que todos os trabalhos forem concluídos, você poderá visualizar os as informações dos alertas de {% data variables.product.prodname_code_scanning %} que foram identificados. Para obter mais informações, consulte "[Gerenciar alertas de {% data variables.product.prodname_code_scanning %} para o seu repositório](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)". + +{% note %} + +**Observação:** Se você criou um pull request para adicionar o fluxo de trabalho de {% data variables.product.prodname_code_scanning %} ao repositório, os alertas desse pull request não serão exibidos diretamente na página de {% data variables.product.prodname_code_scanning_capc %} até que o pull request seja mesclado. Se algum alerta for encontrado, você poderá visualizá-los, antes do merge do pull request, clicando no link dos **_n_ alertas encontrados** no banner na página de {% data variables.product.prodname_code_scanning_capc %}. + +{% ifversion fpt or ghes > 3.1 or ghae-next %} + ![Clique no link "n alertas encontrados"](/assets/images/help/repository/code-scanning-alerts-found-link.png) +{% else %} + ![Clique no link "n alertas encontrados"](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png) +{% endif %} + +{% endnote %} ## Entendendo as verificações de pull request @@ -65,13 +98,25 @@ 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, você verá inicialmente uma mensagem de "Análise ausente" ao clicar em **Detalhes** na verificação de resultados de "{% data variables.product.prodname_code_scanning_capc %} / NOME DA FERRAMENTA". +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 %} "Análise não encontrada"{% else %}"Análise ausente"{% endif %} ao clicar em **Detalhes** na verificação de "resultados de {% data variables.product.prodname_code_scanning_capc %} NOME DA FERRAMENTA. - ![Análise ausente para mensagem de commit](/assets/images/help/repository/code-scanning-missing-analysis.png) +{% ifversion fpt or ghes > 3.2 or ghae-issue-3891 %} + ![Análise não encontrada para mensagem de commit](/assets/images/help/repository/code-scanning-analysis-not-found.png) -### Motivos da mensagem "faltando ausente" +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. -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, ao clicar na verificação de resultados no pull request você verá a mensagem "Análise ausente para o commit de base SHA-HASH". +Por exemplo, na captura de tela acima, {% data variables.product.prodname_code_scanning %} encontrou uma análise para o commit do merge do pull request, mas não há análise para o cabeçalho do branch principal. +{% else %} + ![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 %} +### 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 %}"Análise não encontrada"{% else %}"Análise ausente do commit base SHA-HASH"{% endif %}. 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: @@ -79,7 +124,7 @@ Há outras situações em que não pode haver análise para o último commit do Para verificar se um branch foi verificado, acesse a página {% data variables.product.prodname_code_scanning_capc %}, clique no menu suspenso **Branch** e selecione o branch relevante. -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ![Escolha um branch no menu suspenso Branch](/assets/images/help/repository/code-scanning-branch-dropdown.png) {% else %} ![Escolha um branch no menu suspenso Branch](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-dropdown.png) 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 cf99ec0b2e..a3e589d913 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,42 +28,45 @@ 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 %} +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 %} -If your pull request targets a protected branch that uses {% data variables.product.prodname_code_scanning %}, and the repository owner has configured required status checks, then the "{% data variables.product.prodname_code_scanning_capc %} results" check must pass before you can merge the pull request. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)". +Se o seu pull request for direcionado a um branch protegido que usa {% data variables.product.prodname_code_scanning %} e o proprietário do repositório tiver configurado as verificações de status necessárias, a verificação de "resultados de {% data variables.product.prodname_code_scanning_capc %}" deve passar antes que você possa fazer o merge do pull request. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)". ## Sobre {% data variables.product.prodname_code_scanning %} como uma verificação de pull request Há muitas opções para configurar {% data variables.product.prodname_code_scanning %} como uma verificação de pull request. Portanto, a configuração exata de cada repositório irá variar e alguns terão mais de uma verificação. -### {% data variables.product.prodname_code_scanning_capc %} results check +### Verificação de resultados de {% data variables.product.prodname_code_scanning_capc %} -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. +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 %} 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. 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-issue-4902 %} 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). " -![{% data variables.product.prodname_code_scanning_capc %} results check on a pull request](/assets/images/help/repository/code-scanning-results-check.png) +![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 %} -### {% data variables.product.prodname_code_scanning_capc %} results check failures +### Falhas de verificação de resultados {% data variables.product.prodname_code_scanning_capc %} -If the {% data variables.product.prodname_code_scanning %} results check finds any problems with a severity of `error`{% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %}, `critical`, or `high`,{% endif %} the check fails and the error is reported in the check results. If all the results found by {% data variables.product.prodname_code_scanning %} have lower severities, the alerts are treated as warnings or notes and the check succeeds. +Se os resultados {% data variables.product.prodname_code_scanning %} encontrarem algum problema com uma gravidade de `erro`{% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %}, `grave` ou `alto`,{% endif %} a verificação irá falhar e o erro será relatado nos resultados da verificação. Se todos os resultados encontrados por {% data variables.product.prodname_code_scanning %} tiverem gravidades menores, os alertas serão tratados como avisos ou observações e a verificação será considerada bem-sucedida. ![Ocorreu uma falha na verificação de {% data variables.product.prodname_code_scanning %} em um pull request](/assets/images/help/repository/code-scanning-check-failure.png) -{% ifversion fpt or ghes > 3.1 or ghae-next %}You can override the default behavior in your repository settings, by specifying the level of severities {% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %}and security severities {% endif %}that will cause a pull request check failure. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)". +{% ifversion fpt or ghes > 3.1 or ghae-next %}Você pode substituir o comportamento padrão nas configurações do repositório, ao especificar o nível de gravidade {% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %}e gravidade de segurança {% endif %}que causarão uma falha de verificação de pull request. Para obter mais informações, consulte[Definir as gravidades causadoras da falha de verificação de pull request](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)". {% endif %} -### Other {% data variables.product.prodname_code_scanning %} checks +### Outras verificações de {% data variables.product.prodname_code_scanning %} -Depending on your configuration, you may see additional checks running on pull requests with {% data variables.product.prodname_code_scanning %} configured. These are usually workflows that analyze the code or that upload {% data variables.product.prodname_code_scanning %} results. These checks are useful for troubleshooting when there are problems with the analysis. +Dependendo da sua configuração, você poderá ver verificações adicionais em execução em pull requests com {% data variables.product.prodname_code_scanning %} configurados. Estes são geralmente fluxos de trabalho que analisam o código ou que fazem o upload dos resultados de {% data variables.product.prodname_code_scanning %}. Essas verificações são úteis para a resolução de problemas em caso de problemas com a análise. -For example, if the repository uses the {% data variables.product.prodname_codeql_workflow %} a **{% data variables.product.prodname_codeql %} / Analyze (LANGUAGE)** check is run for each language before the results check runs. A verificação de análise pode falhar se houver problemas de configuração ou se o pull request altera a criação para uma linguagem que a análise precisa para compilar (por exemplo, C/C++, C#, ou Java). +Por exemplo, se o repositório usar o {% data variables.product.prodname_codeql_workflow %}, será executada uma verificação de **{% data variables.product.prodname_codeql %} / Analyze (LANGUAGE)** para cada linguagem antes que a verificação de resultados seja executada. A verificação de análise pode falhar se houver problemas de configuração ou se o pull request altera a criação para uma linguagem que a análise precisa para compilar (por exemplo, C/C++, C#, ou Java). Assim como com outras verificações de pull request, você poderá ver informações completas da falha de verificação na aba de **Verificações**. Para obter mais informações sobre configuração e solução de problemas, consulte "[Configurar {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)" ou "[Solução de problemas do fluxo de trabalho de {% data variables.product.prodname_codeql %}](/code-security/secure-coding/troubleshooting-the-codeql-workflow)". -## Viewing an alert on your pull request +## Visualizando um alerta no seu pull request -You can see any {% data variables.product.prodname_code_scanning %} alerts introduced in a pull request by displaying the **Files changed** tab. Each alert is shown as an annotation on the lines of code that triggered the alert. The severity of the alert is displayed in the annotation. +Você pode ver todos os alertas de {% data variables.product.prodname_code_scanning %} introduzidos em um pull request que exibem a guia **Arquivos alterados**. Cada alerta é exibido como uma anotação nas linhas de código que acionaram o alerta. A gravidade do alerta é exibida na anotação. ![Alerta de anotação em um diff de pull request](/assets/images/help/repository/code-scanning-pr-annotation.png) diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md index 1ee505fd17..26cbb6aaf7 100644 --- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md +++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md @@ -104,36 +104,36 @@ Para obter mais informações, consulte a extração de fluxo de trabalho em "[C Para obter mais informações sobre a especificação de etapas de criação, consulte "[Configurar o fluxo de trabalho do {% data variables.product.prodname_codeql %} para linguagens compiladas](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)". {% ifversion fpt or ghes > 3.1 or ghae-next %} -## Lines of code scanned are lower than expected +## As inhas de código digitalizadas são menores do que o esperado -For compiled languages like C/C++, C#, Go, and Java, {% data variables.product.prodname_codeql %} only scans files that are built during the analysis. Therefore the number of lines of code scanned will be lower than expected if some of the source code isn't compiled correctly. This can happen for several reasons: +Para linguagens compiladas como, por exemplo, C/C++, C#, Go e Java, {% data variables.product.prodname_codeql %} só faz a digitalização de arquivos criados durante a análise. Portanto, o número de linhas de código digitalizadas será menor do que o esperado se parte do código-fonte não for compilado corretamente. Isso pode acontecer por várias razões: -1. The {% data variables.product.prodname_codeql %} `autobuild` feature uses heuristics to build the code in a repository. However, sometimes this approach results in an incomplete analysis of a repository. For example, when multiple `build.sh` commands exist in a single repository, the analysis may not be complete since the `autobuild` step will only execute one of the commands, and therefore some source files may not be compiled. -1. Some compilers do not work with {% data variables.product.prodname_codeql %} and can cause issues while analyzing the code. For example, Project Lombok uses non-public compiler APIs to modify compiler behavior. The assumptions used in these compiler modifications are not valid for {% data variables.product.prodname_codeql %}'s Java extractor, so the code cannot be analyzed. +1. O recurso {% data variables.product.prodname_codeql %} `autobuild` usa heurística para criar o código em um repositório. No entanto, às vezes essa abordagem resulta em uma análise incompleta de um repositório. Por exemplo, quando vários comandos `build.sh` existem em um único repositório, a análise pode não estar completa, uma vez que a etapa de `autobuild` executará apenas um dos comandos. Portanto, alguns arquivos de origem podem não ser compilados. +1. Alguns compiladores não funcionam com {% data variables.product.prodname_codeql %} e podem causar problemas ao analisar o código. Por exemplo, o projeto Lombok usa APIs do compilador não público para modificar o comportamento do compilador. As suposições usadas nessas modificações do compilador não são válidas para o extrator Java do {% data variables.product.prodname_codeql %}. Portanto, o código não pode ser analisado. -If your {% data variables.product.prodname_codeql %} analysis scans fewer lines of code than expected, there are several approaches you can try to make sure all the necessary source files are compiled. +Se a sua análise de {% data variables.product.prodname_codeql %} digitalizar menos linhas de código do que o esperado, existem várias abordagens que você pode testar para garantir que todos os arquivos fonte necessários sejam compilados. -### Replace the `autobuild` step +### Substitua a etapa `autobuild` -Replace the `autobuild` step with the same build commands you would use in production. This makes sure that {% data variables.product.prodname_codeql %} knows exactly how to compile all of the source files you want to scan. Para obter mais informações, consulte "[Configurar o fluxo de trabalho do {% data variables.product.prodname_codeql %} para linguagens compiladas](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)". +Substitua a etapa `autobuild` pelos os mesmos comandos de compilação que você usaria em produção. Isso garante que {% data variables.product.prodname_codeql %} sabe exatamente como compilar todos os arquivos de origem que você deseja digitalizar. Para obter mais informações, consulte "[Configurar o fluxo de trabalho do {% data variables.product.prodname_codeql %} para linguagens compiladas](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)". -### Inspect the copy of the source files in the {% data variables.product.prodname_codeql %} database -You may be able to understand why some source files haven't been analyzed by inspecting the copy of the source code included with the {% data variables.product.prodname_codeql %} database. To obtain the database from your Actions workflow, add an `upload-artifact` action after the analysis step in your code scanning workflow: +### Inspecionar a cópia dos arquivos de origem no banco de dados de {% data variables.product.prodname_codeql %} +Talvez você seja possa entender por que alguns arquivos de origem não foram analisados inspecionando a cópia do código-fonte incluído na base de dados de {% data variables.product.prodname_codeql %}. Para obter o banco de dados de seu fluxo de trabalho de ações, adicione uma ação `upload-artifact` após a etapa de análise de seu fluxo de trabalho de digitalização de código: ``` - uses: actions/upload-artifact@v2 with: name: codeql-database path: ../codeql-database ``` -This uploads the database as an actions artifact that you can download to your local machine. For more information, see "[Storing workflow artifacts](/actions/guides/storing-workflow-data-as-artifacts)." +Isso faz o upload do banco de dados como um artefato de ações que você pode baixar para a sua máquina local. Para obter mais informações, consulte "[Armazenando artefatos de fluxo de trabalho](/actions/guides/storing-workflow-data-as-artifacts)". -The artifact will contain an archived copy of the source files scanned by {% data variables.product.prodname_codeql %} called _src.zip_. If you compare the source code files in the repository and the files in _src.zip_, you can see which types of file are missing. Once you know what types of file are not being analyzed, it is easier to understand how you may need to change the workflow for {% data variables.product.prodname_codeql %} analysis. +O artefato conterá uma cópia arquivada dos arquivos de origem digitalizados por {% data variables.product.prodname_codeql %} denominada _src.zip_. Se você comparar os arquivos do código-fonte no repositório e os arquivos em _src. ip_, você poderá ver quais tipos de arquivo estarão faltando. Uma vez que você sabe quais tipos de arquivo não estão sendo analisados, é mais fácil entender como você pode precisar alterar o fluxo de trabalho para a análise de {% data variables.product.prodname_codeql %}. -## Extraction errors in the database +## Erros de extração no banco de dados -The {% data variables.product.prodname_codeql %} team constantly works on critical extraction errors to make sure that all source files can be scanned. However, the {% data variables.product.prodname_codeql %} extractors do occasionally generate errors during database creation. {% data variables.product.prodname_codeql %} provides information about extraction errors and warnings generated during database creation in a log file. The extraction diagnostics information gives an indication of overall database health. Most extractor errors do not significantly impact the analysis. A small number of extractor errors is healthy and typically indicates a good state of analysis. +A equipe de {% data variables.product.prodname_codeql %} trabalha constantemente em erros críticos de extração para garantir que todos os arquivos de origem possam ser digitalizados. No entanto, os extratores de {% data variables.product.prodname_codeql %} às vezes geram erros durante a criação do banco de dados. {% data variables.product.prodname_codeql %} fornece informações sobre erros de extração e avisos gerados durante a criação do banco de dados em um arquivo de registro. A informação sobre o diagnóstico de extração fornece uma indicação da saúde geral do banco de dados. A maioria dos erros dos extratores não impactam a análise significativamente. Um pequeno número de erros de extrator é saudável e normalmente indica um bom estado de análise. -However, if you see extractor errors in the overwhelming majority of files that were compiled during database creation, you should look into the errors in more detail to try to understand why some source files weren't extracted properly. +No entanto, se você vir erros de extrator na grande maioria dos arquivos que foram compilados durante a criação do banco de dados, você deverá analisar os erros mais detalhadamente para tentar entender por que alguns arquivos de origem não foram extraídos corretamente. {% else %} ## Partes do meu repositório não foram analisadas usando `build automático` diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md index d136804f46..6c27950cae 100644 --- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md +++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md @@ -22,7 +22,7 @@ shortTitle: Visualizar os registros de digitalização de código Você pode usar uma série de ferramentas para configurar {% data variables.product.prodname_code_scanning %} no seu repositório. Para obter mais informações, consulte "[Configuração do {% data variables.product.prodname_code_scanning %} para um repositório](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#options-for-setting-up-code-scanning)". -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} A informação de registro e diagnóstico disponível para você depende do método que você usa para {% data variables.product.prodname_code_scanning %} no repositório. Você pode verificar o tipo de {% data variables.product.prodname_code_scanning %} que você está usando na aba **Segurança** do seu repositório, usando o menu suspenso **Ferramenta** na lista de alerta. Para obter mais informações, consulte "[Gerenciar alertas de {% data variables.product.prodname_code_scanning %} para o seu repositório](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)". ## Sobre análise e informações de diagnóstico @@ -35,7 +35,7 @@ Você pode visualizar as análises e informações de diagnóstico para {% data Se você estiver utilizando o {% data variables.product.prodname_codeql_cli %} fora de {% data variables.product.prodname_dotcom %}, você verá informações de diagnóstico na saída gerada durante a análise do banco de dados. Estas informações também estão incluídas nos resultados do SARIF que você enviou para {% data variables.product.prodname_dotcom %} com os resultados de {% data variables.product.prodname_code_scanning %}. -Para obter informações sobre o {% data variables.product.prodname_codeql_cli %}, consulte "[Executar {% data variables.product.prodname_codeql_cli %} no seu sistema de CI](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-cli-in-your-ci-system#viewing-log-and-diagnostic-information)". +Para obter informações sobre o {% data variables.product.prodname_codeql_cli %}, consulte "[Configurar {% data variables.product.prodname_codeql_cli %} no seu sistema de CI](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system#viewing-log-and-diagnostic-information)". ### Sobre métricas resumidas @@ -72,7 +72,7 @@ Depois de configurar o {% data variables.product.prodname_code_scanning %} para **Observação:** Se você criou um pull request para adicionar o fluxo de trabalho de {% data variables.product.prodname_code_scanning %} ao repositório, os alertas desse pull request não serão exibidos diretamente na página de {% data variables.product.prodname_code_scanning_capc %} até que o pull request seja mesclado. Se algum alerta for encontrado, você poderá visualizá-los, antes do merge do pull request, clicando no link dos **_n_ alertas encontrados** no banner na página de {% data variables.product.prodname_code_scanning_capc %}. -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae %} ![Clique no link "n alertas encontrados"](/assets/images/help/repository/code-scanning-alerts-found-link.png) {% else %} ![Clique no link "n alertas encontrados"](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png) diff --git a/translations/pt-BR/content/code-security/code-scanning/index.md b/translations/pt-BR/content/code-security/code-scanning/index.md index 10bcec39a3..16f4e19e1b 100644 --- a/translations/pt-BR/content/code-security/code-scanning/index.md +++ b/translations/pt-BR/content/code-security/code-scanning/index.md @@ -1,5 +1,5 @@ --- -title: Finding security vulnerabilities and errors in your code with code scanning +title: Encontrar vulnerabilidades e erros de segurança no seu código com a digitalização de código shortTitle: Varredura de código intro: 'Mantenha seu código seguro usando {% data variables.product.prodname_code_scanning %} para identificar e corrigir potenciais vulnerabilidades de segurança e outros erros no seu código.' product: '{% data reusables.gated-features.code-scanning %}' diff --git a/translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md b/translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md index a078427a5a..367fcb239a 100644 --- a/translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md +++ b/translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md @@ -30,7 +30,7 @@ Se você usar uma ferramenta de análise estática de terceiros que pode produzi ## Integrações com webhooks -You can use {% data variables.product.prodname_code_scanning %} webhooks to build or set up integrations, such as [{% data variables.product.prodname_github_apps %}](/apps/building-github-apps/) or [{% data variables.product.prodname_oauth_apps %}](/apps/building-oauth-apps/), that subscribe to {% data variables.product.prodname_code_scanning %} events in your repository. Por exemplo, você poderia criar uma integração que criasse um problema no {% data variables.product.product_name %} ou que envia uma notificação do Slack quando um novo alerta de {% data variables.product.prodname_code_scanning %} for adicionado ao seu repositório. Para obter mais informações, consulte "[Criar webhooks](/developers/webhooks-and-events/creating-webhooks)" e "[Eventos de Webhook e cargas](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)". +Você pode usar {% data variables.product.prodname_code_scanning %} webhooks para criar ou configurar integrações, tais como [{% data variables.product.prodname_github_apps %}s](/apps/building-github-apps/) ou [{% data variables.product.prodname_oauth_apps %}s](/apps/building-oauth-apps/), que assinam os eventos {% data variables.product.prodname_code_scanning %} no seu repositório. Por exemplo, você poderia criar uma integração que criasse um problema no {% data variables.product.product_name %} ou que envia uma notificação do Slack quando um novo alerta de {% data variables.product.prodname_code_scanning %} for adicionado ao seu repositório. Para obter mais informações, consulte "[Criar webhooks](/developers/webhooks-and-events/creating-webhooks)" e "[Eventos de Webhook e cargas](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)". ## Leia mais diff --git a/translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md b/translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md index e569faeb4b..0f979f3b45 100644 --- a/translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md +++ b/translations/pt-BR/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md @@ -37,7 +37,7 @@ Se o seu arquivo SARIF não incluir `partialFingerprints`, o campo `partialFinge {% ifversion fpt or ghes > 3.0 or ghae-next %} Se você estiver usando o {% data variables.product.prodname_codeql_cli %}, especifique a versão do SARIF a ser usada. Para obter mais informações, consulte "[Configurar {% data variables.product.prodname_codeql_cli %} no seu sistema de CI](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system#analyzing-a-codeql-database)."{% endif %} -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} Você pode fazer upload de vários arquivos SARIF para a mesma ferramenta e commit, e analisar cada arquivo usando {% data variables.product.prodname_code_scanning %}. Você pode indicar uma "categoria" para cada análise, especificando um `runAutomationDetails.id` em cada arquivo. Apenas arquivos SARIF com a mesma categoria irão sobrescrever um ao outro. Para obter mais informações sobre esta propriedade, consulte o objeto [`runAutomationDetails`](#runautomationdetails-object) abaixo. {% endif %} @@ -91,19 +91,19 @@ O {% data variables.product.prodname_code_scanning_capc %} usa o objeto `executa ### Objeto `reportingDescriptor` -| Nome | Descrição | -| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `id` | **Obrigatório.** Um identificador exclusivo para a regra. O id `` é referenciado a partir de outras partes do arquivo SARIF e pode ser usado por {% data variables.product.prodname_code_scanning %} para exibir URLs em {% data variables.product.prodname_dotcom %}. | -| `name` | **Opcional.** O nome da regra. {% data variables.product.prodname_code_scanning_capc %} exibe o nome para permitir que os resultados sejam filtrados pela regra em {% data variables.product.prodname_dotcom %}. | -| `shortDescription.text` | **Obrigatório.** Uma descrição concisa da regra. {% data variables.product.prodname_code_scanning_capc %} exibe a breve descrição em {% data variables.product.prodname_dotcom %} ao lado dos resultados associados. | -| `fullDescription.text` | **Obrigatório.** Uma descrição da regra. {% data variables.product.prodname_code_scanning_capc %} exibe a descrição completa em {% data variables.product.prodname_dotcom %} ao lado dos resultados associados. O número máximo de caracteres é 1000. | -| `defaultConfiguration.level` | **Opcional.** Gravidade-padrão da regra. {% data variables.product.prodname_code_scanning_capc %} usa níveis de gravidade para ajudar você a entender quão crítico é o resultado para uma determinada regra. Esse valor pode ser substituído pelo atributo de `nível` no objeto `resultado`. Para obter mais informações, consulte o objeto [`resultado`](#result-object). Padrão: `alerta`. | -| `help.text` | **Obrigatório.** Documentação para a regra usando o formato de texto. O {% data variables.product.prodname_code_scanning_capc %} exibe essa documentação de ajuda ao lado dos resultados associados. | -| `help.markdown` | **Recomendado.** Documentação para a regra que o formato Markdown. O {% data variables.product.prodname_code_scanning_capc %} exibe essa documentação de ajuda ao lado dos resultados associados. Quando `help.markdown` estiver disponível, será exibido em vez de `help.text`. | -| `properties.tags[]` | **Opcional.** Um array de strings. {% data variables.product.prodname_code_scanning_capc %} usa `tags` para permitir que você filtre resultados em {% data variables.product.prodname_dotcom %}. Por exemplo, é possível filtrar para todos os resultados que têm a tag `segurança`. | -| `properties.precision` | **Recomendado.** Uma string que indica quantas vezes os resultados indicados por esta regra são verdadeiros. Por exemplo, se uma regra tem uma alta taxa conhecida de falsos-positivos, a precisão deve ser `baixa`. {% data variables.product.prodname_code_scanning_capc %} ordena os resultados por precisão em {% data variables.product.prodname_dotcom %} de modo que os resultados com o mais alto `nível` e a mais alta `precisão` sejam exibidos primeiro. Pode ser: `very-high`, `high`, `medium` ou `low`. |{% ifversion fpt or ghes > 3.1 or ghae-next %} -| `properties.problem.severity` | **Recommended.** A string that indicates the level of severity of any alerts generated by a non-security query. This, with the `properties.precision` property, determines whether the results are displayed by default on {% data variables.product.prodname_dotcom %} so that the results with the highest `problem.severity`, and highest `precision` are shown first. Can be one of: `error`, `warning`, or `recommendation`. | -| `properties.security-severity` | **Recommended.** A score that indicates the level of severity, between 0.0 and 10.0, for security queries (`@tags` includes `security`). This, with the `properties.precision` property, determines whether the results are displayed by default on {% data variables.product.prodname_dotcom %} so that the results with the highest `security-severity`, and highest `precision` are shown first. {% data variables.product.prodname_code_scanning_capc %} translates numerical scores as follows: over 9.0 is `critical`, 7.0 to 8.9 is `high`, 4.0 to 6.9 is `medium` and 3.9 or less is `low`. {% endif %} +| Nome | Descrição | +| ---------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `id` | **Obrigatório.** Um identificador exclusivo para a regra. O id `` é referenciado a partir de outras partes do arquivo SARIF e pode ser usado por {% data variables.product.prodname_code_scanning %} para exibir URLs em {% data variables.product.prodname_dotcom %}. | +| `name` | **Opcional.** O nome da regra. {% data variables.product.prodname_code_scanning_capc %} exibe o nome para permitir que os resultados sejam filtrados pela regra em {% data variables.product.prodname_dotcom %}. | +| `shortDescription.text` | **Obrigatório.** Uma descrição concisa da regra. {% data variables.product.prodname_code_scanning_capc %} exibe a breve descrição em {% data variables.product.prodname_dotcom %} ao lado dos resultados associados. | +| `fullDescription.text` | **Obrigatório.** Uma descrição da regra. {% data variables.product.prodname_code_scanning_capc %} exibe a descrição completa em {% data variables.product.prodname_dotcom %} ao lado dos resultados associados. O número máximo de caracteres é 1000. | +| `defaultConfiguration.level` | **Opcional.** Gravidade-padrão da regra. {% data variables.product.prodname_code_scanning_capc %} usa níveis de gravidade para ajudar você a entender quão crítico é o resultado para uma determinada regra. Esse valor pode ser substituído pelo atributo de `nível` no objeto `resultado`. Para obter mais informações, consulte o objeto [`resultado`](#result-object). Padrão: `alerta`. | +| `help.text` | **Obrigatório.** Documentação para a regra usando o formato de texto. O {% data variables.product.prodname_code_scanning_capc %} exibe essa documentação de ajuda ao lado dos resultados associados. | +| `help.markdown` | **Recomendado.** Documentação para a regra que o formato Markdown. O {% data variables.product.prodname_code_scanning_capc %} exibe essa documentação de ajuda ao lado dos resultados associados. Quando `help.markdown` estiver disponível, será exibido em vez de `help.text`. | +| `properties.tags[]` | **Opcional.** Um array de strings. {% data variables.product.prodname_code_scanning_capc %} usa `tags` para permitir que você filtre resultados em {% data variables.product.prodname_dotcom %}. Por exemplo, é possível filtrar para todos os resultados que têm a tag `segurança`. | +| `properties.precision` | **Recomendado.** Uma string que indica quantas vezes os resultados indicados por esta regra são verdadeiros. Por exemplo, se uma regra tem uma alta taxa conhecida de falsos-positivos, a precisão deve ser `baixa`. {% data variables.product.prodname_code_scanning_capc %} ordena os resultados por precisão em {% data variables.product.prodname_dotcom %} de modo que os resultados com o mais alto `nível` e a mais alta `precisão` sejam exibidos primeiro. Pode ser: `very-high`, `high`, `medium` ou `low`. |{% ifversion fpt or ghes > 3.1 or ghae-next %} +| `properties.problem.severity` | **Recomendado.** Uma string indica o nível de gravidade de qualquer alerta gerado por uma consulta que não é segurança. Isso, com a propriedade `properties.precision`, determina se os resultados são exibidos por padrão em {% data variables.product.prodname_dotcom %} para que os resultados com `problem.severity` e `precision` mais altos sejam exibidos primeiro. Pode ser um dos valores a seguir `erro`, `aviso` ou `recomendação`. | +| `properties.security-severity` | **Recomendado.** A pontuação indica o nível de gravidade, entre 0,0 e 10, para consultas de segurança (`@tags` inclui `segurança`). Isso, com a propriedade `properties.precision`, determina se os resultados são exibidos por padrão em {% data variables.product.prodname_dotcom %} para que os resultados com `security-severity` e `precision` mais altos sejam exibidos primeiro. {% data variables.product.prodname_code_scanning_capc %} traduz pontuações numéricas da seguinte forma: acima de 9.0 é `crítico`, de 7.0 a 8. é `alto`, de 4.0 a 6. é `médio` e inferio a 3,9 é `baixo`. {% endif %} ### Objeto `resultado` @@ -141,7 +141,7 @@ Um local dentro de um artefato de programação, como, por exemplo, um arquivo n | `region.endLine` | **Requerido.** O número da linha do último caractere na região. | | `region.endColumn` | **Obrigatório.** O número da coluna do caractere após o final da região. | -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ### objeto `ExecutarDetalhes` O objeto `runAutomationDetails` contém informações que especificam a identidade de uma execução. @@ -245,7 +245,7 @@ Este arquivo de saída SARIF tem exemplo de valores para mostrar as propriedades Este arquivo de saída SARIF tem valores de exemplo para mostrar todas as propriedades do SARIF compatíveis com {% data variables.product.prodname_code_scanning %}. -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ```json { "$schema": "https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json", diff --git a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md index eec9628110..df6fea3106 100644 --- a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md +++ b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md @@ -28,7 +28,7 @@ redirect_from: ## Sobre {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} no seu sistema de CI -{% data reusables.code-scanning.about-code-scanning %} For information, see "[About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)." +{% data reusables.code-scanning.about-code-scanning %} Para obter informações, consulte "[Sobre {% data variables.product.prodname_code_scanning %} com {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)." Você pode executar {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} em {% data variables.product.product_name %} usando {% data variables.product.prodname_actions %}. Como alternativa, se você usar um sistema de integração contínua ou um sistema de entrega/Continuous Delivery (CI/CD) de terceiros você poderá executar a análise {% data variables.product.prodname_codeql %} no seu sistema existente e enviar os resultados para {% data variables.product.product_location %}. @@ -91,8 +91,8 @@ Para obter mais informações, consulte "[Executar o {% data variables.product.p {% endif %} - -{% ifversion ghes = 3.0 or ghae %} + +{% ifversion ghes = 3.0 %} {% data reusables.code-scanning.upload-sarif-ghas %} Se você adicionar {% data variables.product.prodname_codeql_runner %} ao seu sistema de terceiros, chame a ferramenta para analisar o código e fazer o upload dos resultados do SARIF para {% data variables.product.product_name %}. Os alertas de {% data variables.product.prodname_code_scanning %} resultantes são exibidos junto com todos os alertas gerados dentro de {% data variables.product.product_name %}. 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 488c5abc1b..bf696ba53f 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 @@ -30,7 +30,7 @@ Uma vez disponibilizado o {% data variables.product.prodname_codeql_cli %} para Você usa três comandos diferentes para gerar resultados e fazer o upload deles para {% data variables.product.product_name %}: -{% ifversion fpt or ghes > 3.1 or ghae-next %} +{% ifversion fpt or ghes > 3.1 or ghae %} 1. `criar um banco de dados` para criar um banco de dados de {% data variables.product.prodname_codeql %} para representar a estrutura hierárquica de cada linguagem de programação compatível no repositório. 2. `análise do banco de dados` para executar consultas para analisar cada banco de dados de {% data variables.product.prodname_codeql %} e resumir os resultados em um arquivo SARIF. @@ -50,11 +50,11 @@ Você pode mostrar a ajuda de linha de comando para qualquer comando usando 3.1 or ghae-next %} + {% ifversion fpt or ghes > 3.1 or ghae %} ```shell # Single supported language - create one CodeQL databsae codeql database create <database> --command<build> --language=<language-identifier> @@ -119,7 +119,7 @@ Você pode mostrar a ajuda de linha de comando para qualquer comando usando - {% ifversion fpt or ghes > 3.1 or ghae-next %}When used with     `--db-cluster`, a opção aceita uma lista separada por vírgulas, ou pode ser especificada mais de uma vez.{% endif %} + {% ifversion fpt or ghes > 3.1 or ghae %}When used with     `--db-cluster`, a opção aceita uma lista separada por vírgulas, ou pode ser especificada mais de uma vez.{% endif %} @@ -144,7 +144,7 @@ Você pode mostrar a ajuda de linha de comando para qualquer comando usando - {% ifversion fpt or ghes > 3.1 or ghae-next %} + {% ifversion fpt or ghes > 3.1 or ghae %} @@ -208,7 +208,7 @@ Você pode mostrar a ajuda de linha de comando para qualquer comando usando 3.1 or ghae-next %}Exemplo de linguagem única{% else %}Exemplo básico{% endif %} +### {% ifversion fpt or ghes > 3.1 or ghae %}Exemplo de linguagem única{% else %}Exemplo básico{% endif %} Este exemplo cria um banco de dados de {% data variables.product.prodname_codeql %} para o repositório verificado em `/checkouts/example-repo`. Ele usa o extrator do JavaScript para criar uma representação hierárquica do código JavaScript e TypeScript no repositório. O banco de dados resultante é armazenado em `/codeql-dbs/example-repo`. @@ -226,7 +226,7 @@ $ codeql database create /codeql-dbs/example-repo --language=javascript \ > Successfully created database at /codeql-dbs/example-repo. ``` -{% ifversion fpt or ghes > 3.1 or ghae-next %} +{% ifversion fpt or ghes > 3.1 or ghae %} ### Exemplo de linguagem múltipla Este exemplo cria dois bancos de dados de {% data variables.product.prodname_codeql %} para o repositório verificado em `/checkouts/example-repo-multi`. Ela usa: @@ -261,19 +261,19 @@ $ ## Analisando um banco de dados de {% data variables.product.prodname_codeql %} -1. Create a {% data variables.product.prodname_codeql %} database (see above).{% if codeql-packs %} -2. Optional, run `codeql pack download` to download any {% data variables.product.prodname_codeql %} packs (beta) that you want to run during analysis. For more information, see "[Downloading and using {% data variables.product.prodname_codeql %} query packs](#downloading-and-using-codeql-query-packs)" below. +1. Criar um banco de dados de {% data variables.product.prodname_codeql %} (ver acima).{% if codeql-packs %} +2. Opcional, execute `codeql pack download` para fazer o download de quaisquer pacotes (beta) de {% data variables.product.prodname_codeql %} que você deseja executar durante a análise. Para obter mais informações, consulte "[Fazer o download e usando pacotes de consulta de {% data variables.product.prodname_codeql %} pacotes de consulta](#downloading-and-using-codeql-query-packs)" abaixo. ```shell codeql pack download <packs> ``` {% endif %} -3. Run `codeql database analyze` on the database and specify which {% if codeql-packs %}packs and/or {% endif %}queries to use. +3. Executar `codeql database analyze` no banco de dados e especifique quais {% if codeql-packs %}pacotes e/ou {% endif %}consultas devem ser usados. ```shell codeql database analyze <database> --format=<format> \ --output=<output> {% if codeql-packs %}<packs,queries>{% else %} <queries>{% endif %} ``` -{% ifversion fpt or ghes > 3.1 or ghae-next %} +{% ifversion fpt or ghes > 3.1 or ghae %} {% note %} **Observação:** Se você analisar mais de um banco de dados de {% data variables.product.prodname_codeql %} para um único commit, você deverá especificar uma categoria SARIF para cada conjunto de resultados gerados por este comando. Ao fazer o upload dos resultados para {% data variables.product.product_name %}, {% data variables.product.prodname_code_scanning %} usa essa categoria para armazenar os resultados para cada linguagem separadamente. Se você esquecer de fazer isso, cada upload irá substituir os resultados anteriores. @@ -317,15 +317,14 @@ codeql database analyze <database> --format=<format> \ - <queries> + <packs,queries> - {% octicon "check-circle-fill" aria-label="Required" %} - Especifique as consultas a executar. Para executar as consultas padrão usadas para {% data variables.product.prodname_code_scanning %}, use: <language>-code-scanning.qls, em que <language> é um código curto para a linguagem do banco de dados. Para ver os outros itens de consultas incluídos no pacote de {% data variables.product.prodname_codeql_cli %}, procure em /<extraction-root>/codeql/qlpacks/codeql-<language>/codeql-suites. Para obter informações sobre como criar seu próprio conjunto de consulta, consulte Criando conjuntos de consultas de CodeQL na documentação do {% data variables.product.prodname_codeql_cli %}. + Specify {% data variables.product.prodname_codeql %} packs or queries to run. To run the standard queries used for {% data variables.product.prodname_code_scanning %}, omit this parameter. Para ver os outros itens de consultas incluídos no pacote de {% data variables.product.prodname_codeql_cli %}, procure em /<extraction-root>/codeql/qlpacks/codeql-<language>/codeql-suites. Para obter informações sobre como criar seu próprio conjunto de consulta, consulte Criando conjuntos de consultas de CodeQL na documentação do {% data variables.product.prodname_codeql_cli %}. @@ -353,7 +352,7 @@ codeql database analyze <database> --format=<format> \ - Especifique onde salvar o arquivo de resultados SARIF.{% ifversion fpt or ghes > 3.1 or ghae-next %} + Especifique onde salvar o arquivo de resultados SARIF.{% ifversion fpt or ghes > 3.1 or ghae %} @@ -367,7 +366,7 @@ codeql database analyze <database> --format=<format> \ - Opcional para análise única do banco de dados. Necessário para definir a linguagem quando você analisa vários bancos de dados para um único commit em um repositório. Especifique uma categoria a incluir no arquivo de resultados SARIF para esta análise. A category is used to distinguish multiple analyses for the same tool and commit, but performed on different languages or different parts of the code.|{% endif %}{% if codeql-packs %} + Opcional para análise única do banco de dados. Necessário para definir a linguagem quando você analisa vários bancos de dados para um único commit em um repositório. Especifique uma categoria a incluir no arquivo de resultados SARIF para esta análise. Usa-e uma categoria para distinguir várias análises para a mesma ferramenta e commit, mas é realizada em diferentes linguagens ou diferentes partes do código.{% endif %}{% if codeql-packs %} @@ -380,7 +379,7 @@ codeql database analyze <database> --format=<format> \ - Opcional. Use if you have downloaded CodeQL query packs and want to run the default queries or query suites specified in the packs. For more information, see "Downloading and using {% data variables.product.prodname_codeql %} packs."{% endif %} + Opcional. Use se você fez o download dos pacotes de consulta CodeQL e desejar executar as consultas padrão ou os conjuntos de consulta especificados nos pacotes. Para obter mais informações, consulte "Fazer o download e usar pacotes de {% data variables.product.prodname_codeql %}."{% endif %} @@ -406,7 +405,7 @@ codeql database analyze <database> --format=<format> \ - Opcional. Use para obter informações mais detalhadas sobre o processo de análise{% ifversion fpt or ghes > 3.1 or ghae-next %} e dados de diagnóstico do processo de criação do banco de dados{% endif %}. + Opcional. Use para obter informações mais detalhadas sobre o processo de análise{% ifversion fpt or ghes > 3.1 or ghae %} e dados de diagnóstico do processo de criação do banco de dados{% endif %}. @@ -415,11 +414,11 @@ Para obter mais informações, consulte [Analisando bancos de dados com {% data ### Exemplo básico -Este exemplo analisa um banco de dados {% data variables.product.prodname_codeql %} armazenado em `/codeql-dbs/example-repo` e salva os resultados como um arquivo SARIF: `/temp/example-repo-js.sarif`. {% ifversion fpt or ghes > 3.1 or ghae-next %}}Ele usa `--sarif-category` para incluir informações extras no arquivo SARIF que identifica os resultados como JavaScript. Isto é essencial quando você tem mais de um banco de dados de {% data variables.product.prodname_codeql %} para analisar um único commit em um repositório.{% endif %} +Este exemplo analisa um banco de dados {% data variables.product.prodname_codeql %} armazenado em `/codeql-dbs/example-repo` e salva os resultados como um arquivo SARIF: `/temp/example-repo-js.sarif`. {% ifversion fpt or ghes > 3.1 or ghae %}}Ele usa `--sarif-category` para incluir informações extras no arquivo SARIF que identifica os resultados como JavaScript. Isto é essencial quando você tem mais de um banco de dados de {% data variables.product.prodname_codeql %} para analisar um único commit em um repositório.{% endif %} ``` $ codeql database analyze /codeql-dbs/example-repo \ - javascript-code-scanning.qls {% ifversion fpt or ghes > 3.1 or ghae-next %}--sarif-category=javascript{% endif %} + javascript-code-scanning.qls {% ifversion fpt or ghes > 3.1 or ghae %}--sarif-category=javascript{% endif %} --format={% ifversion fpt or ghae %}sarif-latest{% else %}sarifv2.1.0{% endif %} --output=/temp/example-repo-js.sarif > Running queries. @@ -444,7 +443,7 @@ Quando você decidir o método mais seguro e confiável para o seu servidor de C ```shell echo "$UPLOAD_TOKEN" | codeql github upload-results --repository=<repository-name> \ --ref=<ref> --commit=<commit> --sarif=<file> \ - {% ifversion ghes > 3.0 or ghae-next %}--github-url=<URL> {% endif %}--github-auth-stdin + {% ifversion ghes > 3.0 or ghae %}--github-url=<URL> {% endif %}--github-auth-stdin ``` @@ -486,7 +485,7 @@ Quando você decidir o método mais seguro e confiável para o seu servidor de C @@ -514,7 +513,7 @@ Quando você decidir o método mais seguro e confiável para o seu servidor de C @@ -555,20 +554,20 @@ Este exemplo faz o upload dos resultados do arquivo SARIF `temp/example-repo-js. ``` $ echo $UPLOAD_TOKEN | codeql github upload-results --repository=my-org/example-repo \ --ref=refs/heads/main --commit=deb275d2d5fe9a522a0b7bd8b6b6a1c939552718 \ - --sarif=/temp/example-repo-js.sarif {% ifversion ghes > 3.0 or ghae-next %}--github-url={% data variables.command_line.git_url_example %} \ + --sarif=/temp/example-repo-js.sarif {% ifversion ghes > 3.0 or ghae %}--github-url={% data variables.command_line.git_url_example %} \ {% endif %}--github-auth-stdin ``` Não há saída deste comando a menos que o upload não tenha sido bem-sucedido. A instrução de comando retorna quando o upload foi concluído e o processamento de dados é iniciado. Em bases de código menores, você poderá explorar os alertas de {% data variables.product.prodname_code_scanning %} em {% data variables.product.product_name %} pouco tempo depois. É possível ver alertas diretamente no pull request ou na aba **Segurança** para branches, dependendo do código que você fizer checkout. Para obter mais informações, consulte "[Triar alertas de {% data variables.product.prodname_code_scanning %} em pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)" e "[Gerenciar alertas de {% data variables.product.prodname_code_scanning %} para o seu repositório](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)". {% if codeql-packs %} -## Downloading and using {% data variables.product.prodname_codeql %} query packs +## Fazendo o download e usando pacotes de consulta de {% data variables.product.prodname_codeql %} {% data reusables.code-scanning.beta-codeql-packs-cli %} -The {% data variables.product.prodname_codeql_cli %} bundle includes queries that are maintained by {% data variables.product.company_short %} experts, security researchers, and community contributors. If you want to run queries developed by other organizations, {% data variables.product.prodname_codeql %} query packs provide an efficient and reliable way to download and run queries. For more information, see "[About code scanning with CodeQL](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql#about-codeql-queries)." +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 %} by running `codeql pack download` and specifying the packages you want to download. If a package is not publicly available, you will need to use a {% data variables.product.prodname_github_app %} or personal access token to authenticate. For more information and an example, see "[Uploading results to {% data variables.product.product_name %}](#uploading-results-to-github)" above. +Antes de 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 precisar a partir de {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %} executando `codeql download` e especificando os pacotes que você deseja baixar. 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. ```shell codeql pack download <scope/name@version>,... @@ -599,7 +598,7 @@ codeql pack download <scope/name@version>,... @@ -612,14 +611,14 @@ codeql pack download <scope/name@version>,...
    - Especifique o nome do ref que você verificou e analisou para que os resultados possam ser correspondidos ao código correto. Para o uso de um branch: refs/heads/BRANCH-NAME, para o commit principal de um pull request, use refs/pulls/NUMBER/head ou para o commit de merge gerado por {% data variables.product.product_name %} do uso de um pull request refs/pulls/NUMBER/merge. + Especifique o nome do ref que você verificou e analisou para que os resultados possam ser correspondidos ao código correto. Para o uso de um branch: refs/heads/BRANCH-NAME, para o commit principal de um pull request, use refs/pulls/NUMBER/head ou para o commit de merge gerado por {% data variables.product.prodname_dotcom %} do uso de um pull request refs/pulls/NUMBER/merge.
    - Especifique o arquivo SARIF a ser carregado.{% ifversion ghes > 3.0 or ghae-next %} + Especifique o arquivo SARIF a ser carregado.{% ifversion ghes > 3.0 or ghae %}
    - Specify the scope and name of one or more CodeQL query packs to download using a comma-separated list. Optionally, include the version to download and unzip. By default the latest version of this pack is downloaded. + 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.
    - Opcional. Pass the {% data variables.product.prodname_github_app %} or personal access token created for authentication with {% data variables.product.company_short %}'s REST API to the CLI via standard input. Isso não é necessário se o comando tiver acesso a uma variável de ambiente GITHUB_TOKEN definida com este token. + Opcional. Passe o token de acesso {% data variables.product.prodname_github_app %} ou pessoal criado para autenticação com a API REST de {% data variables.product.company_short %}para a CLI por meio da entrada padrão. Isso não é necessário se o comando tiver acesso a uma variável de ambiente GITHUB_TOKEN definida com este token.
    ### Exemplo básico -This example runs two commands to download the latest version of the `octo-org/security-queries` pack and then analyze the database `/codeql-dbs/example-repo`. +Este exemplo executa dois comandos para baixar a última versão do pacote `octo-org/security-queries` e, em seguida, analisar o banco de dados `/codeql-dbs/exemplo-repo`. ``` $ echo $OCTO-ORG_ACCESS_TOKEN | codeql pack download octo-org/security-queries @@ -641,6 +640,7 @@ $ codeql database analyze /codeql-dbs/example-repo octo-org/security-queries \ {% endif %} {% ifversion fpt or ghes > 3.1 or ghae-next %} + ## Exemplo de configuração de CI para análise de {% data variables.product.prodname_codeql %} Este é um exemplo da série de comandos que você pode usar para analisar uma base de código com duas linguagens compatíveis e, em seguida, fazer o upload dos resultados para {% data variables.product.product_name %}. @@ -695,7 +695,7 @@ Se desejar fazer o upload de mais de um conjunto de resultados para a API de {% {% ifversion fpt or ghes > 3.2 or ghae-next %} -If your CI system cannot trigger the {% data variables.product.prodname_codeql_cli %} autobuild and you cannot specify a command line for the build, you can use indirect build tracing to create {% data variables.product.prodname_codeql %} databases for compiled languages. For more information, see [Using indirect build tracing](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#using-indirect-build-tracing) in the documentation for the {% data variables.product.prodname_codeql_cli %}. +Se o seu sistema CI não puder habilitar o autobuild {% data variables.product.prodname_codeql_cli %} e você não puder especificar uma linha de comando para a compilação, você poderá usar o rastreamento de compilação indireto para criar bancos de dados de {% data variables.product.prodname_codeql %} para linguagens compiladas. Para obter mais informações, consulte [Usando o rastreamento indireto de compilação](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#using-indirect-build-tracing) na documentação de {% data variables.product.prodname_codeql_cli %}. {% endif %} diff --git a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md index fec292fd91..318f037384 100644 --- a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md +++ b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md @@ -190,7 +190,7 @@ Analisa o código nos bancos de dados do {% data variables.product.prodname_code | `--no-upload` | | Nenhum. Impede que o {% data variables.product.prodname_codeql_runner %} faça o upload dos resultados para {% data variables.product.product_name %}. | | `--output-dir` | | Diretório onde os arquivos SARIF de saída são armazenados. O padrão está no diretório de arquivos temporários. | | `--ram` | | A quantidade de memória a ser usada ao executar consultas. O padrão é usar toda a memória disponível. | -| `--no-add-snippets` | | Nenhum. Exclui snippets de código da saída de SARIF. |{% ifversion fpt or ghes > 3.1 %} +| `--no-add-snippets` | | Nenhum. Exclui snippets de código da saída de SARIF. |{% ifversion fpt or ghes > 3.1 or ghae %} | `--category` | | A categoria a incluir no arquivo de resultados SARIF para esta análise. Uma categoria pode ser usada para distinguir várias análises para a mesma ferramenta e commit, mas executado em diferentes linguagens ou diferentes partes do código. Este valor aparecerá na propriedade `.automationDetails.id` no SARIF v2.1.0. {% endif %} | `--threads` | | Número de threads a serem usados ao executar consultas. O padrão é usar todos os núcleos disponíveis. | diff --git a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-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/installing-codeql-cli-in-your-ci-system.md index ef8f5e5818..08c01eb47a 100644 --- a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-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/installing-codeql-cli-in-your-ci-system.md @@ -28,7 +28,7 @@ redirect_from: ## Sobre o uso do {% data variables.product.prodname_codeql_cli %} for {% data variables.product.prodname_code_scanning %} -Você pode usar {% data variables.product.prodname_codeql_cli %} para executar o {% data variables.product.prodname_code_scanning %} no código que você está processando em um sistema de integração contínua (CI) de terceiros. {% data reusables.code-scanning.about-code-scanning %} For information, see "[About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)." +Você pode usar {% data variables.product.prodname_codeql_cli %} para executar o {% data variables.product.prodname_code_scanning %} no código que você está processando em um sistema de integração contínua (CI) de terceiros. {% data reusables.code-scanning.about-code-scanning %} Para obter informações, consulte "[Sobre {% data variables.product.prodname_code_scanning %} com {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)." {% data reusables.code-scanning.what-is-codeql-cli %} diff --git a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md index 7cb8ec3e97..d43ce63f97 100644 --- a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md +++ b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md @@ -1,7 +1,7 @@ --- -title: Migrating from the CodeQL runner to CodeQL CLI -shortTitle: Migrating from the CodeQL runner -intro: 'You can use the {% data variables.product.prodname_codeql_cli %} to complete the same tasks as with the {% data variables.product.prodname_codeql_runner %}.' +title: Fazendo a migração do executor CodeQL para a CLI do CodeQL +shortTitle: Fazendo a migração do executor do CodeQL +intro: 'Você pode usar o {% data variables.product.prodname_codeql_cli %} para realizar as mesmas tarefas que {% data variables.product.prodname_codeql_runner %}.' product: '{% data reusables.gated-features.code-scanning %}' versions: fpt: '*' @@ -13,45 +13,45 @@ topics: - CodeQL --- -# Migrating from the {% data variables.product.prodname_codeql_runner %} to the {% data variables.product.prodname_codeql_cli %} +# Fazendo a migração de {% data variables.product.prodname_codeql_runner %} para {% data variables.product.prodname_codeql_cli %} -The {% data variables.product.prodname_codeql_runner %} is being deprecated. You can use the {% data variables.product.prodname_codeql_cli %} version 2.6.2 and greater instead. This document describes how to migrate common workflows from the {% data variables.product.prodname_codeql_runner %} to the {% data variables.product.prodname_codeql_cli %}. +{% data variables.product.prodname_codeql_runner %} está tornando-se obsoleto. Em vez disso, você pode usar a versão 2.6.3 de {% data variables.product.prodname_codeql_cli %} ou superior. Este documento descreve como fazer a migração de fluxos de trabalho comuns de {% data variables.product.prodname_codeql_runner %} para {% data variables.product.prodname_codeql_cli %}. ## Instalação -Download the **{% data variables.product.prodname_codeql %} bundle** from the [`github/codeql-action` repository](https://github.com/github/codeql-action/releases). This bundle contains the {% data variables.product.prodname_codeql_cli %} and the standard {% data variables.product.prodname_codeql %} queries and libraries. +Faça o download do **{% data variables.product.prodname_codeql %} pacote** a partir do repositório [`github/codeql-action`](https://github.com/github/codeql-action/releases). Este pacote contém {% data variables.product.prodname_codeql_cli %} e as consultas e bibliotecas padrão de {% data variables.product.prodname_codeql %}. -For more information on setting up the {% data variables.product.prodname_codeql_cli %}, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)." +Para obter mais informações sobre como configurar o {% data variables.product.prodname_codeql_cli %}, consulte "[Instalando {% data variables.product.prodname_codeql_cli %} no seu sistema de CI](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)". -## Overview of workflow changes +## Visão geral das alterações do fluxo de trabalho -A typical workflow that uses the {% data variables.product.prodname_codeql_runner %} to analyze a codebase has the following steps. -- `codeql-runner- init` to start creating {% data variables.product.prodname_codeql %} databases and read the configuration. -- For compiled languages: set environment variables produced by the `init` step. -- For compiled languages: run autobuild or manual build steps. -- `codeql-runner- analyze` to finish creating {% data variables.product.prodname_codeql %} databases, run queries to analyze each {% data variables.product.prodname_codeql %} database, summarize the results in a SARIF file, and upload the results to {% data variables.product.prodname_dotcom %}. +Um fluxo de trabalho típico que usa o {% data variables.product.prodname_codeql_runner %} para analisar uma base de código tem as seguintes etapas. +- `codeql-runner- inicia` para começar a criar bancos de dados de {% data variables.product.prodname_codeql %} e ler a configuração. +- Para linguagens compiladas: defina variáveis de ambiente produzidas pela etapa `init`. +- Para linguagens compiladas: execute o autobuild ou etapas manuais de compilação. +- `codeql-runner- analise` para terminar de criar bancos de dados de {% data variables.product.prodname_codeql %}, executar consultas para analisar cada banco de dados de {% data variables.product.prodname_codeql %}, resumir os resultados em um arquivo SARIF e fazer o upload dos resultados para {% data variables.product.prodname_dotcom %}. -A typical workflow that uses the {% data variables.product.prodname_codeql_cli %} to analyze a codebase has the following steps. -- `codeql database create` to create {% data variables.product.prodname_codeql %} databases. - - For compiled languages: Optionally provide a build command. -- `codeql database analyze` to run queries to analyze each {% data variables.product.prodname_codeql %} database and summarize the results in a SARIF file. This command must be run once for each language or database. -- `codeql github upload-results` to upload the resulting SARIF files to {% data variables.product.prodname_dotcom %}, to be displayed as code scanning alerts. This command must be run once for each language or SARIF file. +Um fluxo de trabalho típico que usa o {% data variables.product.prodname_codeql_cli %} para analisar uma base de código tem as seguintes etapas. +- `codeql database create` para criar bancos de dados de {% data variables.product.prodname_codeql %}. + - Para linguagens compiladas: Opcionalmente, forneça um comando de criação. +- `codeql base de dados analisa` para executar consultas para analisar cada banco de dados de {% data variables.product.prodname_codeql %} e resumir os resultados de um arquivo SARIF. Esse comando deve ser executado uma vez para cada linguagem ou banco de dados. +- `github do codeql upload-results` para fazer o upload dos arquivos SARIF para {% data variables.product.prodname_dotcom %} resultantes e serem exibidos como alertas de verificação de código. Esse comando deve ser executado uma vez para cada linguagem ou arquivo SARIF. Para obter mais informações, consulte "[Configurar {% data variables.product.prodname_codeql_cli %} no seu sistema de CI](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system)." -## Examples of common uses for the {% data variables.product.prodname_codeql_cli %} +## Exemplos de usos comuns para o {% data variables.product.prodname_codeql_cli %} -### About the examples +### Sobre os exemplos -These examples assume that the source code has been checked out to the current working directory. If you use a different directory, change the `--source-root` argument and the build steps accordingly. +Estes exemplos assumem que o código-fonte foi check-out para o diretório de trabalho atual. Se você usa um diretório diferente, mude o argumento `--source-root` e as etapas de criação. -These examples also assume that the {% data variables.product.prodname_codeql_cli %} is placed on the current PATH. +Esses exemplos também assumem que a {% data variables.product.prodname_codeql_cli %} é colocado no PATH atual. -In these examples, a {% data variables.product.prodname_dotcom %} token with suitable scopes is stored in the `$TOKEN` environment variable and passed to the example commands via stdin, or is stored in the `$GITHUB_TOKEN` environment variable. +Nestes exemplos, um token de {% data variables.product.prodname_dotcom %} com escopos adequados é armazenado na variável de ambiente `$TOKEN` e passado para os comandos de exemplo via stdin ou é armazenado na variável de ambiente `$GITHUB_TOKEN`. -The ref name and commit SHA being checked out and analyzed in these examples are known during the workflow. For a branch, use `refs/heads/BRANCH-NAME` as the ref. For the head commit of a pull request, use `refs/pulls/NUMBER/head`. For a {% data variables.product.prodname_dotcom %}-generated merge commit of a pull request, use `refs/pulls/NUMBER/merge`. The examples below all use `refs/heads/main`. If you use a different branch name, you must modify the sample code. +O nome da ref e o commit SHA que está sendo verificado e analisado nesses exemplos são conhecidos durante o fluxo de trabalho. Para um branch, use `refs/heads/BRANCH-NAME` como ref. Para o commit principal de um pull request, use `refs/pulls/NUMBER/head`. Para um commit de merge gerado por {% data variables.product.prodname_dotcom %} de um pull request, use `refs/pulls/NUMBER/merge`. Todos ps exemplos abaixo usam `refs/heads/main`. Se você usar um nome de branch diferente, deverá modificar o código do exemplo. -### Single non-compiled language (JavaScript) +### Linguagem única não compilada (JavaScript) Executor: ```bash @@ -78,9 +78,9 @@ echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \ --sarif=/temp/example-repo-js.sarif --github-auth-stdin ``` -### Single non-compiled language (JavaScript) using a different query suite (security-and-quality) +### Linguagem única não compilada (JavaScript) que usa um conjunto de consultas diferente (segurança e qualidade) -A similar approach can be taken for compiled languages, or multiple languages. +É possível adotar uma abordagem semelhante para as linguagens compiladas ou para várias linguagens. Executor: ```bash @@ -108,9 +108,9 @@ echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \ --sarif=/temp/example-repo-js.sarif --github-auth-stdin ``` -### Single non-compiled language (JavaScript) using a custom configuration file +### Linguagem única não compilada (JavaScript) que usa um arquivo de configuração personalizado -A similar approach can be taken for compiled languages, or multiple languages. +É possível adotar uma abordagem semelhante para as linguagens compiladas ou para várias linguagens. Executor: ```bash @@ -139,7 +139,7 @@ echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \ --sarif=/temp/example-repo-js.sarif --github-auth-stdin ``` -### Single compiled language using autobuild (Java) +### Linguagem compilada única que usa autobuild (Java) Executor: ```bash @@ -173,7 +173,7 @@ echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \ --sarif=/temp/example-repo-java.sarif --github-auth-stdin ``` -### Single compiled language using a custom build command (Java) +### Uma linguagem compilada que usa um comando de criação personalizado (Java) Executor: ```bash @@ -206,9 +206,9 @@ echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \ --sarif=/temp/example-repo-java.sarif --github-auth-stdin ``` -### Single compiled language using indirect build tracing (C# on Windows within Azure DevOps) +### Linguagem compilada única que usa rastreamento de compilação indireta (C# no Windows dentro do Azure DevOps) -Indirect build tracing for a compiled language enables {% data variables.product.prodname_codeql %} to detect all build steps between the `init` and `analyze` steps, when the code cannot be built using the autobuilder or an explicit build command line. This is useful when using preconfigured build steps from your CI system, such as the `VSBuild` and `MSBuild` tasks in Azure DevOps. +O rastreamento indireto de compilação de uma linguagem permite que {% data variables.product.prodname_codeql %} detecte todos os passos de compilação entre as etapas `init` e `analyze`, quando o código não pode ser construído usando o autobuilder ou uma linha de comando de compilação explícita. Isso é útil ao usar as etapas de criação pré-configuradas do seu sistema de CI como, por exemplo, as tarefas `VSBuild` e `MSBuild` no Azure DevOps. Executor: ```yaml @@ -264,7 +264,7 @@ CLI: # For CodeQL to trace future build steps without knowing the explicit build commands, # it requires certain environment variables to be set during the build. # Read these generated environment variables and values, and set them so they are available for subsequent commands -# in the build pipeline. This is done in PowerShell in this example. +# in the build pipeline. Neste exemplo, isto é feito em PowerShell. - task: PowerShell@1 displayName: Set CodeQL environment variables inputs: @@ -279,7 +279,7 @@ CLI: echo "$template" } -# Execute the pre-defined build step. Note the `msbuildArgs` variable. +# Execute the pre-defined build step. Observe a variável `msbuildArgs`. - task: VSBuild@1 inputs: solution: '**/*.sln' @@ -291,7 +291,7 @@ CLI: clean: True displayName: Visual Studio Build -# Read and set the generated environment variables to end build tracing. This is done in PowerShell in this example. +# Read and set the generated environment variables to end build tracing. Neste exemplo, isto é feito em PowerShell. - task: PowerShell@1 displayName: Clear CodeQL environment variables inputs: @@ -328,9 +328,9 @@ CLI: ``` -### Multiple languages using autobuild (C++, Python) +### Várias linguagens que usam autobuild (C++, Python) -This example is not strictly possible with the {% data variables.product.prodname_codeql_runner %}. Only one language (the compiled language with the most files) will be analyzed. +Este exemplo não é estritamente possível com {% data variables.product.prodname_codeql_runner %}. Apenas uma linguagem (a linguagem compilada com mais arquivos) será analisada. Executor: ```bash @@ -370,7 +370,7 @@ for language in cpp python; do done ``` -### Multiple languages using a custom build command (C++, Python) +### Várias linguagens que usam um comando de compilação personalizada (C++, Python) Executor: ```bash diff --git a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md index dee506fd53..f7dcbc8be1 100644 --- a/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md +++ b/translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md @@ -34,7 +34,7 @@ topics: ## Sobre o {% data variables.product.prodname_codeql_runner %} -O {% data variables.product.prodname_codeql_runner %} é uma ferramenta que você pode usar para executar {% data variables.product.prodname_code_scanning %} no código que você está processando em um sistema de integração contínua de terceiros (CI). {% data reusables.code-scanning.about-code-scanning %} For information, see "[About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)." +O {% data variables.product.prodname_codeql_runner %} é uma ferramenta que você pode usar para executar {% data variables.product.prodname_code_scanning %} no código que você está processando em um sistema de integração contínua de terceiros (CI). {% data reusables.code-scanning.about-code-scanning %} Para obter informações, consulte "[Sobre {% data variables.product.prodname_code_scanning %} com {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)." {% ifversion fpt or ghes > 3.0 or ghae-next %} Em muitos casos, é mais fácil configurar {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} usando {% data variables.product.prodname_codeql_cli %} diretamente no seu sistema de CI. 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 97ac5f9dd5..32a1447f07 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 @@ -105,7 +105,7 @@ Para obter mais informações, consulte "[Gerenciar configurações de seguranç {% endif %} ## Próximas etapas -{% ifversion fpt or ghes > 3.1 or ghae-next %}You can view, filter, and sort security alerts for repositories owned by your organization in the security overview. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)."{% endif %} +{% ifversion fpt or ghes > 3.1 or ghae-next %}Você pode visualizar, filtrar e organizar alertas de segurança em repositórios pertencentes à sua organização na visão geral de segurança. Para obter mais informações, consulte "[Sobre a visão geral de segurança](/code-security/security-overview/about-the-security-overview)".{% endif %} Você pode visualizar e gerenciar alertas de funcionalidades de segurança para resolver dependências e vulnerabilidades no seu código. Para obter mais informações, consulte {% ifversion fpt or ghes > 2.22 %} "[Visualizar e atualizar as dependências vulneráveis no seu repositório](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository),"{% endif %} {% ifversion fpt %}"[Gerenciar pull requests para atualizações de dependência](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Gernciar {% data variables.product.prodname_code_scanning %} para o seu repositório](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," e "[Gerenciar alertas de {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." diff --git a/translations/pt-BR/content/code-security/getting-started/securing-your-repository.md b/translations/pt-BR/content/code-security/getting-started/securing-your-repository.md index 5d19e2f931..a8c6ed4897 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 @@ -49,7 +49,7 @@ Para obter mais informações, consulte "[Adicionar uma política de segurança {% ifversion fpt or ghes > 2.22 %} ## Gerenciar o gráfico de dependências -Once you have [enabled the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph#enabling-the-dependency-graph), it is automatically generated for {% ifversion fpt or ghes > 2.22 %} all public repositories, and you can choose to enable it for private repositories.{% else %} all repositories.{% endif %} +Depois que você tiver [habilitado o gráfico de dependências](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph#enabling-the-dependency-graph), este será gerado automaticamente para {% ifversion fpt or ghes > 2.22 %} todos os repositórios públicos e você poderá optar por habilitá-lo para repositórios privados.{% else %} todos os repositórios.{% endif %} 1. Na página principal do repositório, clique em **{% octicon "gear" aria-label="The Settings gear" %} Configurações**. 2. Clique em **Segurança & análise**. 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 443d4c8d63..d7cf9d8310 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 @@ -25,7 +25,7 @@ topics: {% data variables.product.company_short %} executa {% data variables.product.prodname_secret_scanning %} nos repositórios {% ifversion fpt %}públicos e privados{% endif %} para padrões de segredo fornecidos por parceiros de {% data variables.product.company_short %} e {% data variables.product.company_short %}. Para obter mais informações sobre o programa de parceria de {% data variables.product.prodname_secret_scanning %}, consulte "Programa de varredura de segredo de parceiros". -No entanto, pode haver situações em que você deverá pesquisar outros padrões secretos nos seus repositórios {% ifversion fpt %}privados{% endif %}. Por exemplo, você pode ter um padrão de segredo que é interno da sua organização. For these situations, you can define custom {% data variables.product.prodname_secret_scanning %} patterns in your enterprise, organization, or {% ifversion fpt %}private{% endif %} repository on {% data variables.product.product_name %}. You can define up to 20 custom patterns for each {% ifversion fpt %}private{% endif %} repository, organization, or enterprise account. +No entanto, pode haver situações em que você deverá pesquisar outros padrões secretos nos seus repositórios {% ifversion fpt %}privados{% endif %}. Por exemplo, você pode ter um padrão de segredo que é interno da sua organização. Para esses casos, você pode definir padrões personalizados de {% data variables.product.prodname_secret_scanning %} na sua empresa, organização ou {% ifversion fpt %}repositório{% endif %} privado em {% data variables.product.product_name %}. É possível definir até 100 padrões personalizados para cada conta da organização ou empresa e até 20 padrões personalizados por repositório {% ifversion fpt %}privado{% endif %}. {% ifversion ghes < 3.3 or ghae %} {% note %} @@ -62,7 +62,7 @@ Antes de definir um padrão personalizado, você deverá habilitar {% data varia {% note %} -**Note:** As there is no dry-run functionality, we recommend that you test your custom patterns in a repository before defining them for your entire organization. That way, you can avoid creating excess false-positive {% data variables.product.prodname_secret_scanning %} alerts. +**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 a organização. Dessa forma, você pode evitar criar alertas falsos-positivos de {% data variables.product.prodname_secret_scanning %}. {% endnote %} @@ -75,13 +75,13 @@ Antes de definir um padrão personalizado, você deverá habilitar {% data varia Depois que o padrão for criado, {% data variables.product.prodname_secret_scanning %} irá verificar todos os segredos nos repositórios {% ifversion fpt %}privados {% endif %} na sua organização, incluindo todo seu histórico do Git em todos os branches. Os proprietários da organização e administradores do repositório receberão um alerta sobre todos os segredos encontrados e poderão revisar o alerta no repositório onde o segredo for encontrado. Para obter mais informações sobre a visualização de alertas de {% data variables.product.prodname_secret_scanning %}, consulte "[Gerenciar alertas de {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)". -## Defining a custom pattern for an enterprise account +## Definir um padrão personalizado para uma conta corporativa -Before defining a custom pattern, you must ensure that you enable secret scanning for your enterprise account. For more information, see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)." +Antes de definir um padrão personalizado, você deverá garantir que você habilite a digitalização de segredo para a sua conta corporativa. Para obter mais informações, consulte "[Habilitar {% data variables.product.prodname_GH_advanced_security %} para a sua empresa](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)." {% note %} -**Note:** As there is no dry-run functionality, we recommend that you test your custom patterns in a repository before defining them for your entire enterprise. That way, you can avoid creating excess false-positive {% data variables.product.prodname_secret_scanning %} alerts. +**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 %}. {% endnote %} @@ -89,35 +89,35 @@ Before defining a custom pattern, you must ensure that you enable secret scannin {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.advanced-security-policies %} {% data reusables.enterprise-accounts.advanced-security-security-features %} -1. Under "Secret scanning custom patterns", click {% ifversion fpt or ghes > 3.2 or ghae-next %}**New pattern**{% elsif ghes = 3.2 %}**New custom pattern**{% endif %}. +1. Em "Padrões personalizados de digitalização de segredos", clique em {% ifversion fpt or ghes > 3.2 or ghae-next %}**Novo padrão**{% elsif ghes = 3.2 %}**Novo padrão personalizado**{% endif %}. {% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %} -After your pattern is created, {% data variables.product.prodname_secret_scanning %} scans for any secrets in {% ifversion fpt %}private{% endif %} repositories within your enterprise's organizations with {% data variables.product.prodname_GH_advanced_security %} enabled, including their entire Git history on all branches. Os proprietários da organização e administradores do repositório receberão um alerta sobre todos os segredos encontrados e poderão revisar o alerta no repositório onde o segredo for encontrado. Para obter mais informações sobre a visualização de alertas de {% data variables.product.prodname_secret_scanning %}, consulte "[Gerenciar alertas de {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)". +Depois que seu padrão for criado, {% data variables.product.prodname_secret_scanning %} irá verificar se há segredos em repositórios {% ifversion fpt %}privados{% endif %} dentro das organizações da sua empresa com {% data variables.product.prodname_GH_advanced_security %} habilitado, incluindo toda a sua história de Git em todos os branches. Os proprietários da organização e administradores do repositório receberão um alerta sobre todos os segredos encontrados e poderão revisar o alerta no repositório onde o segredo for encontrado. Para obter mais informações sobre a visualização de alertas de {% data variables.product.prodname_secret_scanning %}, consulte "[Gerenciar alertas de {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)". {% ifversion fpt or ghes > 3.2 %} -## Editing a custom pattern +## Editando um padrão personalizado -When you save a change to a custom pattern, this closes all the {% data variables.product.prodname_secret_scanning %} alerts that were created using the previous version of the pattern. -1. Navigate to where the custom pattern was created. A custom pattern can be created in a repository, organization, or enterprise account. - * For a repository or organization, display the "Security & analysis" settings for the repository or organization where the custom pattern was created. Para mais informações consulte "[Definir um padrão personalizado para um repositório](#defining-a-custom-pattern-for-a-repository)" ou "[Definir um padrão personalizado para uma organização](#defining-a-custom-pattern-for-an-organization)" acima. - * For an enterprise, under "Policies" display the "Advanced Security" area, and then click **Security features**. For more information, see "[Defining a custom pattern for an enterprise account](#defining-a-custom-pattern-for-an-enterprise-account)" above. -2. Under "{% data variables.product.prodname_secret_scanning_caps %}", to the right of the custom pattern you want to edit, click {% octicon "pencil" aria-label="The edit icon" %}. -3. When you have reviewed and tested your changes, click **Save changes**. +Ao salvar uma alteração em um padrão personalizado, isso irá fechar todos os alertas de {% data variables.product.prodname_secret_scanning %} que foram criados usando a versão anterior do padrão. +1. Acesse o local onde o padrão personalizado foi criado. Um padrão personalizado pode ser criado na conta de um repositório, organização ou empresa. + * Para um repositório ou organização, exiba as configurações "Segurança & análise" do repositório ou organização onde o padrão personalizado foi criado. Para mais informações consulte "[Definir um padrão personalizado para um repositório](#defining-a-custom-pattern-for-a-repository)" ou "[Definir um padrão personalizado para uma organização](#defining-a-custom-pattern-for-an-organization)" acima. + * Para uma empresa, em "Políticas" exiba a área "Segurança Avançada" e, em seguida, clique em **Funcionalidades de segurança**. Para obter mais informações, consulte "[Definindo um padrão personalizado para uma conta corporativa](#defining-a-custom-pattern-for-an-enterprise-account)" acima. +2. Em "{% data variables.product.prodname_secret_scanning_caps %}", à direita do padrão personalizado que você deseja editar, clique em {% octicon "pencil" aria-label="The edit icon" %}. +3. Ao revisar e testar suas alterações, clique em **Salvar alterações**. {% endif %} ## Removendo um padrão personalizado -1. Navigate to where the custom pattern was created. A custom pattern can be created in a repository, organization, or enterprise account. +1. Acesse o local onde o padrão personalizado foi criado. Um padrão personalizado pode ser criado na conta de um repositório, organização ou empresa. - * For a repository or organization, display the "Security & analysis" settings for the repository or organization where the custom pattern was created. Para mais informações consulte "[Definir um padrão personalizado para um repositório](#defining-a-custom-pattern-for-a-repository)" ou "[Definir um padrão personalizado para uma organização](#defining-a-custom-pattern-for-an-organization)" acima. - * For an enterprise, under "Policies" display the "Advanced Security" area, and then click **Security features**. For more information, see "[Defining a custom pattern for an enterprise account](#defining-a-custom-pattern-for-an-enterprise-account)" above. + * Para um repositório ou organização, exiba as configurações "Segurança & análise" do repositório ou organização onde o padrão personalizado foi criado. Para mais informações consulte "[Definir um padrão personalizado para um repositório](#defining-a-custom-pattern-for-a-repository)" ou "[Definir um padrão personalizado para uma organização](#defining-a-custom-pattern-for-an-organization)" acima. + * Para uma empresa, em "Políticas" exiba a área "Segurança Avançada" e, em seguida, clique em **Funcionalidades de segurança**. Para obter mais informações, consulte "[Definindo um padrão personalizado para uma conta corporativa](#defining-a-custom-pattern-for-an-enterprise-account)" acima. {%- ifversion fpt or ghes > 3.2 or ghae-next %} -1. To the right of the custom pattern you want to remove, click {% octicon "trash" aria-label="The trash icon" %}. -1. Review the confirmation, and select a method for dealing with any open alerts relating to the custom pattern. -1. Click **Yes, delete this pattern**. +1. À direita do padrão personalizado que você deseja remover, clique em {% octicon "trash" aria-label="The trash icon" %}. +1. Revise a confirmação e selecione um método para lidar com todos os alertas abertos relacionados ao padrão personalizado. +1. Clique em **Sim, excluir este padrão**. - ![Confirming deletion of a custom {% data variables.product.prodname_secret_scanning %} pattern ](/assets/images/help/repository/secret-scanning-confirm-deletion-custom-pattern.png) + ![Confirmando a exclusão de um padrão {% data variables.product.prodname_secret_scanning %} personalizado ](/assets/images/help/repository/secret-scanning-confirm-deletion-custom-pattern.png) {%- elsif ghes = 3.2 %} -1. To the right of the custom pattern you want to remove, click **Remove**. -1. Review the confirmation, and click **Remove custom pattern**. +1. À direita do padrão personalizado que você deseja remover, clique em **Remover**. +1. Revise a confirmação e clique em **Remover padrão personalizado**. {%- endif %} diff --git a/translations/pt-BR/content/code-security/secret-scanning/index.md b/translations/pt-BR/content/code-security/secret-scanning/index.md index cf338e52cd..ee78392d7d 100644 --- a/translations/pt-BR/content/code-security/secret-scanning/index.md +++ b/translations/pt-BR/content/code-security/secret-scanning/index.md @@ -1,5 +1,5 @@ --- -title: Keeping secrets secure with secret scanning +title: Manter segredos seguros com a digitalização de segredo shortTitle: Varredura secreta intro: 'Permita que {% data variables.product.company_short %} faça o trabalho duro de garantir que tokens, chaves privadas e outros segredos de código não sejam expostos no seu repositório.' product: '{% data reusables.gated-features.secret-scanning %}' diff --git a/translations/pt-BR/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md b/translations/pt-BR/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md index be9cb5d1e2..9401634e51 100644 --- a/translations/pt-BR/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md +++ b/translations/pt-BR/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md @@ -59,7 +59,7 @@ Uma vez que um segredo tenha sido committed a um repositório, você deve consid {% ifversion fpt or ghes > 3.1 or ghae-issue-4910 %} ## Configurando notificações para alertas de {% data variables.product.prodname_secret_scanning %} -Quando um novo segredo é detectado, {% data variables.product.product_name %} notifica todos os usuários com acesso a alertas de segurança para o repositório, de acordo com suas preferências de notificação. You will receive alerts if you are watching the repository, have enabled notifications for security alerts or for all the activity on the repository, are the author of the commit that contains the secret and are not ignoring the repository. +Quando um novo segredo é detectado, {% data variables.product.product_name %} notifica todos os usuários com acesso a alertas de segurança para o repositório, de acordo com suas preferências de notificação. Você receberá alertas se estiver inspecionando o repositório, se tiver habilitado as notificações para alertas de segurança ou para todas as atividades no repositório, se for o autor do commit que contém o segredo e não estiver ignorando o repositório. 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)" e "[Configurar notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)". {% endif %} diff --git a/translations/pt-BR/content/code-security/security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability.md b/translations/pt-BR/content/code-security/security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability.md index a06b03ac98..7ad551f877 100644 --- a/translations/pt-BR/content/code-security/security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability.md +++ b/translations/pt-BR/content/code-security/security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability.md @@ -44,7 +44,7 @@ Qualquer pessoa com permissões de gravação em uma consultoria de segurança p {% data reusables.repositories.sidebar-advisories %} 4. Na lista "consultoria de segurança", clique na consultoria de segurança à qual deseja adicionar alterações. ![Consultoria de segurança na lista](/assets/images/help/security/security-advisory-in-list.png) 5. Adicione as alterações no {% data variables.product.product_name %} ou localmente: - - Para adicionar alterações em {% data variables.product.product_name %}, em "Adicionar alterações a essa consultoria", clique em **bifurcação privada temporária**. Em seguida, crie um branch e edite os arquivos. For more information, see "[Creating and deleting branches within your repository](/articles/creating-and-deleting-branches-within-your-repository)" and "[Editing files](/repositories/working-with-files/managing-files/editing-files)." + - Para adicionar alterações em {% data variables.product.product_name %}, em "Adicionar alterações a essa consultoria", clique em **bifurcação privada temporária**. Em seguida, crie um branch e edite os arquivos. Para obter mais informações, consulte "[Criar e excluir branches dentro do seu repositório](/articles/creating-and-deleting-branches-within-your-repository)" e "[Editar arquivos](/repositories/working-with-files/managing-files/editing-files)". - Para adicionar as alterações localmente, siga as instruções em "Clonar e criar um novo branch" e "Faça suas alterações e, em seguida, faça o push." ![Caixa Add changes to this advisory (Adicionar alterações a esta consultoria)](/assets/images/help/security/add-changes-to-this-advisory-box.png) ## Criar uma pull request de uma bifurcação privada temporária diff --git a/translations/pt-BR/content/code-security/security-advisories/editing-a-security-advisory.md b/translations/pt-BR/content/code-security/security-advisories/editing-a-security-advisory.md index a2878330eb..bf4a2ab365 100644 --- a/translations/pt-BR/content/code-security/security-advisories/editing-a-security-advisory.md +++ b/translations/pt-BR/content/code-security/security-advisories/editing-a-security-advisory.md @@ -34,7 +34,7 @@ Se você acredita que deveria ser creditado por uma consultoria de segurança, e {% data reusables.repositories.security-advisory-edit-cwe-cve %} {% data reusables.repositories.security-advisory-edit-description %} 11. Opcionalmente, edite os "Créditos" para a consultoria de segurança. ![Créditos para uma consultoria de segurança](/assets/images/help/security/security-advisory-credits.png) -12. Clique em **Atualizar consultoria de segurança**. !["Update security advisory" button](/assets/images/help/security/update-advisory-button.png) +12. Clique em **Atualizar consultoria de segurança**. ![Botão "Atualizar consultoria de segurança"](/assets/images/help/security/update-advisory-button.png) 13. As pessoas listadas na seção "Créditos" receberão um e-mail ou uma notificação da web convidando-os a aceitar o crédito. Se uma pessoa aceitar, seu nome de usuário ficará visível publicamente assim que a consultoria de segurança for publicada. ## Leia mais diff --git a/translations/pt-BR/content/code-security/security-advisories/publishing-a-security-advisory.md b/translations/pt-BR/content/code-security/security-advisories/publishing-a-security-advisory.md index 49c4a31aba..4a15575f9a 100644 --- a/translations/pt-BR/content/code-security/security-advisories/publishing-a-security-advisory.md +++ b/translations/pt-BR/content/code-security/security-advisories/publishing-a-security-advisory.md @@ -61,19 +61,6 @@ Depois de publicar uma consultoria de segurança, sua URL permanecerá a mesma d Se você precisar atualizar ou corrigir informações em uma consultoria de segurança que publicou, poderá editar a consultoria de segurança. Para obter mais informações, consulte "[Editar um consultor de segurança](/github/managing-security-vulnerabilities/editing-a-security-advisory)". -## Solicitar um número de identificação CVE - -Qualquer pessoa com permissão de administrador a uma consultora de segurança pode solicitar um número de identificação CVE para a consultoria de segurança. - -{% data reusables.repositories.request-security-advisory-cve-id %} Para obter mais informações, consulte "[Sobre o {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories#cve-identification-numbers). - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-security %} -{% data reusables.repositories.sidebar-advisories %} -4. Na lista "consultoria de segurança", clique na consultoria de segurança para o qual deseja solicitar um número de identificação CVE. ![Consultoria de segurança na lista](/assets/images/help/security/security-advisory-in-list.png) -5. Use o menu suspenso **Publicar consultoria** e clique em **Solicitar CVE**. ![Solicitar CVE no menu suspenso](/assets/images/help/security/security-advisory-drop-down-request-cve.png) -6. Clique **Solicitar CVE**. ![Botão "Solicitar CVE"](/assets/images/help/security/security-advisory-request-cve-button.png) - ## Publicar uma consultoria de segurança A publicação de uma consultor de segurança elimina a bifurcação privada temporária para a consultoria de segurança. @@ -88,6 +75,17 @@ A publicação de uma consultor de segurança elimina a bifurcação privada tem {% data reusables.repositories.github-reviews-security-advisories %} +## Solicitando um número de identificação CVE (Opcional) + +{% data reusables.repositories.request-security-advisory-cve-id %} Para obter mais informações, consulte "[Sobre o {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories#cve-identification-numbers). + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-security %} +{% data reusables.repositories.sidebar-advisories %} +4. Na lista "consultoria de segurança", clique na consultoria de segurança para o qual deseja solicitar um número de identificação CVE. ![Consultoria de segurança na lista](/assets/images/help/security/security-advisory-in-list.png) +5. Use o menu suspenso **Publicar consultoria** e clique em **Solicitar CVE**. ![Solicitar CVE no menu suspenso](/assets/images/help/security/security-advisory-drop-down-request-cve.png) +6. Clique **Solicitar CVE**. ![Botão "Solicitar CVE"](/assets/images/help/security/security-advisory-request-cve-button.png) + ## Leia mais - "[Retirar uma consultora de segurança](/github/managing-security-vulnerabilities/withdrawing-a-security-advisory)" 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 3a449439ae..39fae18993 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: 'You can view, filter, and sort security alerts for repositories owned by your organization or team in one place: the Security Overview page.' +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.' product: '{% data reusables.gated-features.security-center %}' redirect_from: - /code-security/security-overview/exploring-security-alerts versions: fpt: '*' + ghae: issue-4554 ghes: '>3.1' - ghae: next type: how_to topics: - Security overview @@ -15,7 +15,7 @@ topics: - Alerts - Organizations - Teams -shortTitle: About security overview +shortTitle: Sobre a visão geral de segurança --- {% data reusables.security-center.beta %} @@ -24,15 +24,15 @@ shortTitle: About security overview Você pode usar a visão geral de segurança para uma visão de alto nível do status de segurança da sua organização ou para identificar repositórios problemáticos que exigem intervenção. A nível da organização, a visão geral de segurança exibe informações de segurança agregadas e específicas para repositórios pertencentes à sua organização. No nível da equipe, a visão geral de segurança exibe informações de segurança específicas para repositórios para os quais a equipe tem privilégios de administrador. Para obter mais informações, consulte "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)." -The security overview indicates whether {% ifversion fpt or ghes > 3.1 %}security{% endif %}{% ifversion ghae-next %}{% data variables.product.prodname_GH_advanced_security %}{% endif %} features are enabled for repositories owned by your organization and consolidates alerts for each feature.{% ifversion fpt or ghes > 3.1 %} Security features include {% data variables.product.prodname_GH_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_secret_scanning %}, as well as {% data variables.product.prodname_dependabot_alerts %}.{% endif %} For more information about {% data variables.product.prodname_GH_advanced_security %} features, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)."{% ifversion fpt or ghes > 3.1 %} For more information about {% data variables.product.prodname_dependabot_alerts %}, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)."{% endif %} +A visão geral de segurança indica se {% ifversion fpt or ghes > 3.1 %} as funcionalidades segurança{% endif %}{% ifversion ghae-next %}{% data variables.product.prodname_GH_advanced_security %}{% endif %} estão habilitadas para os repositórios pertencentes à sua organização e consolida alertas para cada funcionalidade.{% ifversion fpt or ghes > 3.1 %} As funcionalidades de segurança includem recursos de {% data variables.product.prodname_GH_advanced_security %} como, por exemplo, {% data variables.product.prodname_code_scanning %} e {% data variables.product.prodname_secret_scanning %}, bem como {% data variables.product.prodname_dependabot_alerts %}.{% endif %} Para obter mais informações sobre as funcionalidades de {% data variables.product.prodname_GH_advanced_security %}, consulte "[Sobre {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)."{% ifversion fpt or ghes > 3.1 %} Para obter mais informações sobre {% data variables.product.prodname_dependabot_alerts %}, consulte "[Sobre alertas de dependências vulneráveis](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)."{% endif %} -For more information about securing your code at the repository and organization levels, see "[Securing your repository](/code-security/getting-started/securing-your-repository)" and "[Securing your organization](/code-security/getting-started/securing-your-organization)." +Para obter mais informações sobre como proteger seu código nos níveis do repositório e da organização, consulte "[Protegendo seu repositório](/code-security/getting-started/securing-your-repository)" e "[Protegendo sua organização](/code-security/getting-started/securing-your-organization)". No resumo da segurança, é possível visualizar, ordenar e filtrar alertas para entender os riscos de segurança na sua organização e nos repositórios específicos. Você pode aplicar vários filtros para concentrar-se em áreas de interesse. Por exemplo, você pode identificar repositórios privados que têm um número elevado de {% data variables.product.prodname_dependabot_alerts %} ou repositórios que não têm alertas {% data variables.product.prodname_code_scanning %}. ![A visão geral de segurança de uma organização](/assets/images/help/organizations/security-overview.png) -For each repository in the security overview, you will see icons for each type of security feature and how many alerts there are of each type. If a security feature is not enabled for a repository, the icon for that feature will be grayed out. +Para cada repositório na visão de segurança, você verá ícones para cada tipo de recurso de segurança e quantos alertas existem de cada tipo. Se um recurso de segurança não estiver habilitado para um repositório, o ícone para esse recurso será cinza. ![Ícones na visão geral de segurança](/assets/images/help/organizations/security-overview-icons.png) @@ -41,12 +41,12 @@ For each repository in the security overview, you will see icons for each type o | {% octicon "code-square" aria-label="Code scanning alerts" %} | Alertas de {% data variables.product.prodname_code_scanning_capc %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-code-scanning) | | {% octicon "key" aria-label="Secret scanning alerts" %} | Alertas de {% data variables.product.prodname_secret_scanning_caps %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning) | | {% octicon "hubot" aria-label="Dependabot alerts" %} | {% data variables.product.prodname_dependabot_alerts %}. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)" | -| {% octicon "check" aria-label="Check" %} | The security feature is enabled, but does not raise alerts in this repository. | -| {% octicon "x" aria-label="x" %} | The security feature is not supported in this repository. | +| {% octicon "check" aria-label="Check" %} | O recurso de segurança está habilitado, mas não envia alertas neste repositório. | +| {% octicon "x" aria-label="x" %} | O recurso de segurança não é compatível com este repositório. | Por padrão, os repositórios arquivados são excluídos da visão geral de segurança de uma organização. É possível aplicar filtros para visualizar repositórios arquivados na visão geral de segurança. Para obter mais informações, consulte "[Filtrar a lista de alertas](#filtering-the-list-of-alerts)". -The security overview displays active alerts raised by security features. Se não houver alertas na visão geral de segurança de um repositório, as vulnerabilidades de segurança não detectadas ou erros de código ainda poderão existir. +A visão geral de segurança exibe alertas ativos criados por funcionalidades de segurança. Se não houver alertas na visão geral de segurança de um repositório, as vulnerabilidades de segurança não detectadas ou erros de código ainda poderão existir. ## Visualizar a visão geral de segurança de uma organização @@ -71,7 +71,7 @@ Os integrantes de uma equipe podem visualizar a visão geral de segurança dos r ### Filtrar por nível de risco para repositórios -The level of risk for a repository is determined by the number and severity of alerts from security features. If one or more security features are not enabled for a repository, the repository will have an unknown level of risk. If a repository has no risks that are detected by security features, the repository will have a clear level of risk. +O nível de risco para um repositório é determinado pelo número e gravidade dos alertas de funcionalidades de segurança. Se uma ou mais funcionalidades de segurança não estiverem habilitadas para um repositório, o repositório terá um nível de risco desconhecido. Se um repositório não tiver riscos detectados por funcionalidades de segurança, o repositório terá um nível claro de risco. | Qualifier | Descrição | | -------------- | ----------------------------------------------------------------- | @@ -89,7 +89,7 @@ The level of risk for a repository is determined by the number and severity of a | secret-scanning-alerts:n | Exibe repositórios que têm *n* alertas de {% data variables.product.prodname_secret_scanning %}. Este qualificador pode usar os operadores > e < de comparação. | | dependabot-alerts:n | Exibir repositórios que têm *n* {% data variables.product.prodname_dependabot_alerts %}. Este qualificador pode usar os operadores > e < de comparação. | -### Filter by whether security features are enabled +### Filtrar se as funcionalidades de segurança estão habilitadas | Qualifier | Descrição | | ------------------------------- | ---------------------------------------------------------------------------------------------------- | @@ -102,7 +102,7 @@ The level of risk for a repository is determined by the number and severity of a ### Filtrar por tipo de repositório -| Qualifier | Description | | -------- | -------- |{% ifversion fpt or ghes > 3.1 %} | `is:public` | Display public repositories. |{% endif %} | `is:internal` | Display internal repositories. | | `is:private` | Display private repositories. | | `archived:true` | Display archived repositories. | +| Qualificador | Descrição | | -------- | -------- |{% ifversion fpt or ghes > 3.1 %} | `is:public` | Exibe repositórios públicos. |{% endif %} | `is:internal` | Exibe repositórios internos. | | `is:private` | Exibe repositórios privados. | | `archived:true` | Exibe repositórios arquivados. | ### Filtrar por equipe 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 24a7793210..63ef51b9f5 100644 --- a/translations/pt-BR/content/code-security/security-overview/index.md +++ b/translations/pt-BR/content/code-security/security-overview/index.md @@ -5,8 +5,8 @@ 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 ghes: '>3.1' - ghae: next topics: - Security overview - Advanced Security diff --git a/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md b/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md index 9cfd82324c..690ee70b2c 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md @@ -14,7 +14,7 @@ topics: - Repositories - Dependencies - Pull requests -shortTitle: Use Dependabot with actions +shortTitle: Usar o Dependabot com ações --- ## Sobre {% data variables.product.prodname_dependabot %} e {% data variables.product.prodname_actions %} @@ -200,7 +200,7 @@ jobs: steps: - name: Dependabot metadata id: metadata - uses: dependabot/fetch-metadata@v1.1.1 + uses: dependabot/fetch-metadata@v1.1.0 with: github-token: "${{ secrets.GITHUB_TOKEN }}" - name: Add a label for all production dependencies diff --git a/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md b/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md index 88f26c09dc..0f83b4ac9d 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates.md @@ -181,7 +181,7 @@ Use a opção `allow` para personalizar quais dependências são atualizadas. Is | `direta` | Todas | Todas as dependências explicitamente definidas. | | `indireta` | `bundler`, `pip`, `composer`, `cargo` | Dependências de dependências diretas (também conhecidas como sub-dependências ou dependências transitórias). | | `todos` | Todas | Todas as dependências explicitamente definidas. Para `bundler`, `pip`, `composer`, `cargo`, também as dependências de dependências diretas. | - | `produção` | `bundler`, `composer`, `mix`, `maven`, `npm`, `pip` | Only dependencies in the "Production dependency group". | + | `produção` | `bundler`, `composer`, `mix`, `maven`, `npm`, `pip` | Apenas dependências no "Grupo de dependência de produção". | | `desenvolvimento` | `bundler`, `composer`, `mix`, `maven`, `npm`, `pip` | Somente dependências no "grupo de dependência do desenvolvimento". | ```yaml @@ -539,7 +539,7 @@ updates: ### `schedule.day` -When you set a `weekly` update schedule, by default, {% data variables.product.prodname_dependabot %} checks for new versions on Monday at a random set time for the repository. Use `schedule.day` para especificar um dia alternativo para procurar atualizações. +Ao definir um cronograma de atualização `semanal`, por padrão, {% data variables.product.prodname_dependabot %} verifica novas versões na segunda-feira em um horário aleatório definido para o repositório. Use `schedule.day` para especificar um dia alternativo para procurar atualizações. Valores suportados @@ -566,7 +566,7 @@ updates: ### `schedule.time` -By default, {% data variables.product.prodname_dependabot %} checks for new versions at a random set time for the repository. Use `schedule.time` para especificar um horário alternativo do dia para procurar por atualizações (format: `hh:mm`). +Por padrão, {% data variables.product.prodname_dependabot %} verifica se há novas versões em um horário aleatório definido para o repositório. Use `schedule.time` para especificar um horário alternativo do dia para procurar por atualizações (format: `hh:mm`). ```yaml # Configurar um horário para verificações @@ -582,7 +582,7 @@ updates: ### `schedule.timezone` -By default, {% data variables.product.prodname_dependabot %} checks for new versions at a random set time for the repository. Use `schedule.timezone` para especificar um fuso horário alternativo. O identificador do fuso horário deve ser do banco de dados do fuso horário mantido por [iana](https://www.iana.org/time-zones). Para obter mais informações, consulte [lista de fusos horários do banco de dados do tz](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones). +Por padrão, {% data variables.product.prodname_dependabot %} verifica se há novas versões em um horário aleatório definido para o repositório. Use `schedule.timezone` para especificar um fuso horário alternativo. O identificador do fuso horário deve ser do banco de dados do fuso horário mantido por [iana](https://www.iana.org/time-zones). Para obter mais informações, consulte [lista de fusos horários do banco de dados do tz](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones). ```yaml # Especificar o fuso horário para verificações @@ -827,7 +827,7 @@ registries: ### `maven-repository` -The `maven-repository` type supports username and password. +O tipo `maven-repository` é compatível com o nome de usuário e senha. {% raw %} ```yaml @@ -844,7 +844,7 @@ registries: O tipo `npm-registry` é compatível com o nome de usuário e senha ou token. -When using username and password, your `.npmrc`'s auth token may contain a `base64` encoded `_password`; however, the password referenced in your {% data variables.product.prodname_dependabot %} configuration file must be the original (unencoded) password. +Ao usar nome de usuário e senha, o seu token de autorização `.npmrc` pode conter um `base64` condificado e `_password`. No entanto, a senha especificada no arquivo de configuração {% data variables.product.prodname_dependabot %} deverá ser a senha original (não codificada). {% raw %} ```yaml diff --git a/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/upgrading-from-dependabotcom-to-github-native-dependabot.md b/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/upgrading-from-dependabotcom-to-github-native-dependabot.md index 18f4f5c7a7..f84d611325 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/upgrading-from-dependabotcom-to-github-native-dependabot.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/upgrading-from-dependabotcom-to-github-native-dependabot.md @@ -16,9 +16,9 @@ shortTitle: Atualizações do Dependabot.com {% warning %} -Dependabot Preview has been shut down as of August 3rd, 2021. In order to keep getting Dependabot updates, please migrate to GitHub-native Dependabot. +A visualização do Dependabot foi desativada a partir de 3 de agosto de 2021. A fim de continuar recebendo atualizações do Dependabot, faça a migração para o Dependabot nativo do GitHub. -Open pull requests from Dependabot Preview will remain open, including the pull request to upgrade to GitHub-native Dependabot, but the bot itself will no longer work on your {% data variables.product.prodname_dotcom %} accounts and organizations. +Os pull requests abertos a partir da visualização do Dependabot permanecerão abertos, incluindo o pull request para atualizar para Dependabot nativo do GitHub, mas o bot em si não funcionará mais nas suas contas e nas organizações do {% data variables.product.prodname_dotcom %}. {% endwarning %} @@ -31,7 +31,7 @@ A visualização do Dependabot foi construída diretamente em {% data variables. Embora a maior parte das funcionalidades do Dependabot Preview existam no nativo de {% data variables.product.prodname_dotcom %} {% data variables.product.prodname_dependabot %}, algumas permanecem indisponíveis: - **Atualizações ao vivo:** Esperamos trazê-las de volta no futuro. Por enquanto, você pode executar {% data variables.product.prodname_dotcom %} {% data variables.product.prodname_dependabot %} diariamente para pegar novos pacotes dentro de um dia de versão. - **Registros de variáveis de ambiente PHP:** Para projetos que dependem da variável de ambiente `ACF_PRO_KEY`, você poderá fornecer sua cópia licenciada do plugin Campos Personalizados Avançados. Por exemplo, consulte [dependabot/acf-php-example](https://github.com/dependabot/acf-php-example#readme). Para outras variáveis de ambiente, você pode usar {% data variables.product.prodname_actions %} para buscar dependências desses registros. -- **Auto-merge:** Sempre recomendamos verificar suas dependências antes de mesclá-las. Portanto, a fusão automática não será compatível em um futuro próximo. Para aqueles de vocês que avaliaram as suas dependências ou estiverem usando apenas dependências internas, recomendamos adicionar aplicativos de auto-merge de terceiros ou configurar o GitHub Actions para fazer o merge. We have provided the [`dependabot/fetch-metadata`](https://github.com/marketplace/actions/fetch-metadata-from-dependabot-prs) action to help developers [enable GitHub's automerge](https://github.com/dependabot/fetch-metadata/#enabling-auto-merge). +- **Auto-merge:** Sempre recomendamos verificar suas dependências antes de mesclá-las. Portanto, a fusão automática não será compatível em um futuro próximo. Para aqueles de vocês que avaliaram as suas dependências ou estiverem usando apenas dependências internas, recomendamos adicionar aplicativos de auto-merge de terceiros ou configurar o GitHub Actions para fazer o merge. Fornecemos a ação [`dependabo/buscar metadados`](https://github.com/marketplace/actions/fetch-metadata-from-dependabot-prs) para ajudar os desenvolvedores [a habilitar o merge automático do GitHub](https://github.com/dependabot/fetch-metadata/#enabling-auto-merge). Em nativo de {% data variables.product.prodname_dotcom %} {% data variables.product.prodname_dependabot %}, você pode configurar todas as atualizações da versão usando o arquivo de configuração. Este arquivo é semelhante ao arquivo de configuração do Dependabot Preview com algumas alterações e melhorias que serão incluídas automaticamente no seu pull request de atualização. Para obter mais informações sobre o pull request de atualização, consulte "[Atualizando para o Dependabot nativo do GitHub](/code-security/supply-chain-security/upgrading-from-dependabotcom-to-github-native-dependabot#upgrading-to-github-native-dependabot)". diff --git a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates.md b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates.md index 3749247922..a67cfa49c5 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates.md @@ -51,7 +51,7 @@ Ao fazer merge de um pull request que contém uma atualização de segurança, o ## Sobre pontuações de compatibilidade -{% data variables.product.prodname_dependabot_security_updates %} may include compatibility scores to let you know whether updating a dependency could cause breaking changes to your project. Estes são calculados a partir de testes de CI em outros repositórios públicos onde a mesma atualização de segurança foi gerada. Uma pontuação de compatibilidade da atualização é a porcentagem de execuções de CI que foram aprovadas durante a atualização entre versões específicas da dependência. +O {% data variables.product.prodname_dependabot_security_updates %} pode incluir uma pontuação de compatibilidade para que você saiba se atualizar uma dependência poderá causar alterações significativas no seu projeto. Estes são calculados a partir de testes de CI em outros repositórios públicos onde a mesma atualização de segurança foi gerada. Uma pontuação de compatibilidade da atualização é a porcentagem de execuções de CI que foram aprovadas durante a atualização entre versões específicas da dependência. ## Sobre notificações para atualizações de segurança de {% data variables.product.prodname_dependabot %} diff --git a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md index a67a1f9632..8946ff27e4 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md @@ -36,7 +36,7 @@ Por padrão, se o administrador do site tiver configurado o e-mail para notifica ## Configurar notificações para {% data variables.product.prodname_dependabot_alerts %} {% ifversion fpt or ghes > 3.1 %} -When a new {% data variables.product.prodname_dependabot %} alert is detected, {% data variables.product.product_name %} notifies all users with access to {% data variables.product.prodname_dependabot_alerts %} for the repository according to their notification preferences. You will receive alerts if you are watching the repository, have enabled notifications for security alerts or for all the activity on the repository, and are not ignoring the repository. Para obter mais informações, consulte “[Configurando notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)". +Quando um novo alerta do {% data variables.product.prodname_dependabot %} é detectado, {% data variables.product.product_name %} notifica todos os usuários com acesso a {% data variables.product.prodname_dependabot_alerts %} para o repositório de acordo com suas preferências de notificação. Você receberá alertas se estiver acompanhando o repositório, caso tenha habilitado notificações para alertas de segurança ou para toda a atividade no repositório e não estiver ignorando o repositório. Para obter mais informações, consulte “[Configurando notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)". {% endif %} Você pode definir as configurações de notificação para si mesmo ou para sua organização no menu suspenso Gerenciar notificações {% octicon "bell" aria-label="The notifications bell" %} exibido na parte superior de cada página. Para obter mais informações, consulte “[Configurar notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)". diff --git a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md index eea24b96ca..0387fb30dc 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md @@ -72,7 +72,7 @@ Sim, o gráfico de dependências tem duas categorias de limites: Manifestos com tamanho superior a 0.5 MB são processados apenas para contas corporativas. Para outras contas, manifestos acima de 0,5 MB são ignorados e não criarão {% data variables.product.prodname_dependabot_alerts %}. - Por padrão, o {% data variables.product.prodname_dotcom %} não processará mais de 20 manifestos por repositório. {% data variables.product.prodname_dependabot_alerts %} are not created for manifests beyond this limit. Se você precisar aumentar o limite, entre em contato com {% data variables.contact.contact_support %}. + Por padrão, o {% data variables.product.prodname_dotcom %} não processará mais de 20 manifestos por repositório. {% data variables.product.prodname_dependabot_alerts %} não foi criado para manifestos acima deste limite. Se você precisar aumentar o limite, entre em contato com {% data variables.contact.contact_support %}. 2. **Limites de visualização** 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 20dc5d4ba8..82f3051b54 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 @@ -1,11 +1,11 @@ --- title: Sobre revisão de dependências intro: 'A revisão de dependências permite que você capture dependências vulneráveis antes de introduzi-las no seu ambiente e fornece informações sobre licença, dependências e idade das dependências.' +product: '{% data reusables.gated-features.dependency-review %}' shortTitle: Revisão de dependência versions: fpt: '*' ghes: '>= 3.2' - product: '{% data reusables.gated-features.dependency-review %}' type: overview topics: - Advanced Security @@ -38,6 +38,6 @@ Ao verificar as revisões de dependências em um pull request e alterar todas as 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)". -## Enabling dependency review +## Habilitar revisão de dependências -The dependency review feature becomes available when you enable the dependency graph. {% ifversion fpt %}For more information, see "[Enabling the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph#enabling-the-dependency-graph)."{% endif %}{% ifversion ghes > 3.1 %}For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %} +O recurso de revisão de dependências é disponibilizado quando você habilitar o gráfico de dependências. {% ifversion fpt %}Para obter mais informações, consulte "[Habilitar o gráfico de dependências](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph#enabling-the-dependency-graph).{% endif %}{% ifversion ghes > 3.1 %}Para obter mais informações, consulte "[Habilitar alertas para dependências vulneráveis em {% data variables.product.prodname_ghe_server %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)".{% endif %} diff --git a/translations/pt-BR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md b/translations/pt-BR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md index 68d9106d06..d206e34e86 100644 --- a/translations/pt-BR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md +++ b/translations/pt-BR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md @@ -9,7 +9,7 @@ product: '{% data reusables.gated-features.codespaces %}' shortTitle: Registro de imagem privada --- -## About private image registries and {% data variables.product.prodname_codespaces %} +## Sobre registros de imagens privadas e {% data variables.product.prodname_codespaces %} Um registro é um espaço seguro para armazenar e gerenciar imagens de contêineres privadas, como Azure Container Registry ou DockerHub. Você pode criar segredos no GitHub para armazenar os detalhes de acesso de um registro privado e usá-los para dar ao seu código acesso as imagens armazenadas no registro. @@ -21,13 +21,13 @@ Ao iniciar iniciar um código, {% data variables.product.prodname_codespaces %} É possível armazenar segredos a nível do usuário, repositório ou organização, permitindo que você os compartilhe de forma segura entre diferentes codespaces. Ao criar um conjunto de segredos para um registro de imagem privado, você precisa substituir o "<*>" no nome por um identificador consistente. Para mais informações, consulte "[Gerenciar segredos criptografados para seus códigos](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)" e "[Gerenciar segredos criptografados para seu repositório e organização para os codespaces](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces)". -If you are setting the secrets at the user or organization level, make sure to assign those secrets to the repository you'll be creating the codespace in by choosing an access policy from the dropdown list. +Se você estiver definindo os segredos no nível do usuário ou da organização. certifique-se de atribuir esses segredos para o repositório no qual você irá criar o codespace, escolhendo uma política de acesso na lista suspensa. ![Exemplo de segredo do registro de imagem](/assets/images/help/codespaces/secret-repository-access.png) -## Example secrets +## Exemplos de segredos -For a private image registry in Azure, you could create the following secrets: +Para uma lista de imagens privadas no Azure, você pode criar os seguintes segredos: ``` ACR_CONTAINER_REGISTRY_SERVER = mycompany.azurecr.io @@ -35,18 +35,18 @@ ACR_CONTAINER_REGISTRY_USER = acr-user-here ACR_CONTAINER_REGISTRY_PASSWORD = ``` -For information on common image registries, see "[Common image registry servers](#common-image-registry-servers)." +Para obter informações sobre registros de imagens comuns, consulte "[Servidores de registro de imagens comuns](#common-image-registry-servers)". ![Exemplo de segredo do registro de imagem](/assets/images/help/settings/codespaces-image-registry-secret-example.png) -Once you've added the secrets, you may need to stop and then start the codespace you are in for the new environment variables to be passed into the container. For more information, see "[Suspending or stopping a codespace](/codespaces/codespaces-reference/using-the-command-palette-in-codespaces#suspending-or-stopping-a-codespace)." +Após adicionar os segredos, pode ser que você precise parar e, em seguida, iniciar o processo de codespace para que as novas variáveis de ambiente sejam passadas para o contêiner. Para obter mais informações, consulte "[Suspender ou interromper um codespace](/codespaces/codespaces-reference/using-the-command-palette-in-codespaces#suspending-or-stopping-a-codespace)". -## Common image registry servers +## Servidores de registro de imagens comuns -Some of the common image registry servers are listed below: +Alguns dos servidores comuns de registro de imagens estão listados abaixo: - [DockerHub](https://docs.docker.com/engine/reference/commandline/info/) - `https://index.docker.io/v1/` -- [GitHub Container Registry](/packages/working-with-a-github-packages-registry/working-with-the-container-registry) - `ghcr.io` -- [Azure Container Registry](https://docs.microsoft.com/azure/container-registry/) - `.azurecr.io` -- [Amazon Elastic Container Registry](https://docs.aws.amazon.com/AmazonECR/latest/userguide/Registries.html) - `.dkr.ecr..amazonaws.com` -- [Google Cloud Container Registry](https://cloud.google.com/container-registry/docs/overview#registries) - `gcr.io` (US), `eu.gcr.io` (EU), `asia.gcr.io` (Asia) +- [Registro de Contêiner do GitHub](/packages/working-with-a-github-packages-registry/working-with-the-container-registry) - `ghcr.io` +- [Registro do Contêiner do Azure](https://docs.microsoft.com/azure/container-registry/) - `.azurecr.io` +- [Registro de Contêiner Elástico da Amazon](https://docs.aws.amazon.com/AmazonECR/latest/userguide/Registries.html) - `.dkr.ecr..amazonaws.com` +- [Registro de Contêiner do Google Cloud](https://cloud.google.com/container-registry/docs/overview#registries) - `gcr.io` (US), `eu.gcr.io` (EU), `asia.gcr.io` (Asia) 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 bfe729c57f..187dba7d7d 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 @@ -6,7 +6,7 @@ versions: product: '{% data reusables.gated-features.codespaces %}' topics: - Codespaces -shortTitle: Disaster recovery +shortTitle: Recuperação de desastre --- Trabalhamos muito para ter a certeza de que {% data variables.product.prodname_codespaces %} esteja sempre disponível para você. No entanto, forças além do nosso controle às vezes impactam o serviço de formas que podem causar interrupções de serviços não planejadas. @@ -21,21 +21,21 @@ A orientação a seguir fornece opções sobre como lidar com interrupções de {% endnote %} -## Option 1: Create a new codespace in another region +## Opção 1: Crie um novo ritmo de código em outra região -In the case of a regional outage, we suggest you recreate your codespace in an unaffected region to continue working. Este novo código terá todas as alterações a partir do seu último push para {% data variables.product.prodname_dotcom %}. For information on manaully setting another region, see "[Setting your default region for Codespaces](/codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces)." +No caso de uma interrupção regional, sugerimos que recrie o seu codespace em uma região não afetada para continuar trabalhando. Este novo código terá todas as alterações a partir do seu último push para {% data variables.product.prodname_dotcom %}. Para obter informações sobre a configuração manual de outra região, consulte "[" Definir sua região padrão para os codespaces](/codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces)". -You can optimize recovery time by configuring a `devcontainer.json` in the project's repository, which allows you to define the tools, runtimes, frameworks, editor settings, extensions, and other configuration necessary to restore the development environment automatically. Para obter mais informações, consulte "[Configurar codespaces para o seu projeto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". +Você pode otimizar o tempo de recuperação configurando um `devcontainer.json` no repositório do projeto, que permite que você defina as ferramentas, tempo de execução, estruturas, configurações do editor, extensões e outras configurações necessárias para restaurar o ambiente de desenvolvimento automaticamente. Para obter mais informações, consulte "[Configurar codespaces para o seu projeto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". ## Opção 2: Aguardar a recuperação Neste caso, não é necessária nenhuma ação da sua parte. Saiba que estamos trabalhando diligentemente para restaurar a disponibilidade do serviço. -You can check the current service status on the [Status Dashboard](https://www.githubstatus.com/). +Você pode verificar o status do serviço atual no [Painel de Status](https://www.githubstatus.com/). ## Opção 3: Clonar o repositório localmente ou editá-lo no navegador -Embora o {% data variables.product.prodname_codespaces %} forneça o benefício de um ambiente de desenvolvedor pré-configurado, o seu código-fonte deve sempre poder ser acessado por meio do repositório hospedado em {% data variables.product.prodname_dotcom_the_website %}. Na hipótese de uma interrupção de {% data variables.product.prodname_codespaces %}, você ainda pode clonar o repositório localmente ou editar arquivos no editor do navegador de {% data variables.product.company_short %}. For more information, see "[Editing files](/repositories/working-with-files/managing-files/editing-files)." +Embora o {% data variables.product.prodname_codespaces %} forneça o benefício de um ambiente de desenvolvedor pré-configurado, o seu código-fonte deve sempre poder ser acessado por meio do repositório hospedado em {% data variables.product.prodname_dotcom_the_website %}. Na hipótese de uma interrupção de {% data variables.product.prodname_codespaces %}, você ainda pode clonar o repositório localmente ou editar arquivos no editor do navegador de {% data variables.product.company_short %}. Para obter mais informações, consulte "[Editando arquivos](/repositories/working-with-files/managing-files/editing-files)". Embora esta opção não configure um ambiente de desenvolvimento para você, ela permitirá que você faça alterações no seu código-fonte, conforme necessário, enquanto você aguarda que a interrupção do serviço seja resolvida. 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 40108d46f4..c264720624 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 @@ -1,6 +1,6 @@ --- -title: Security in Codespaces -intro: 'Overview of the {% data variables.product.prodname_codespaces %} security architecture, with guidelines to help you maintain security and minimize the risk of attack.' +title: Segurança nos codespaces +intro: 'Visão geral da arquitetura de segurança de {% data variables.product.prodname_codespaces %}, com orientações para ajudar a manter a segurança e minimizar o risco de ataque.' miniTocMaxHeadingLevel: 3 versions: fpt: '*' @@ -8,98 +8,98 @@ topics: - Codespaces - Security type: reference -shortTitle: Security in Codespaces +shortTitle: Segurança nos codespaces --- -## Overview of codespace security +## Visão geral da segurança do codespace -{% data variables.product.prodname_codespaces %} is designed to be security hardened by default. Consequently, you will need to ensure that your software development practices do not risk reducing the security posture of your codespace. +{% data variables.product.prodname_codespaces %} foi projetado para ser uma segurança enrijecida por padrão. Consequentemente, você deverá garantir que as suas práticas de desenvolvimento de software não corram o risco de reduzir a posição de segurança do seu codespace. -This guide describes the way Codespaces keeps your development environment secure and provides some of the good practices that will help maintain your security as you work. As with any development tool, remember that you should only open and work within repositories you know and trust. +Este guia descreve a forma como os Programas mantêm seu ambiente de desenvolvimento seguro e fornece algumas das práticas recomendadas que ajudarão a manter sua segurança enquanto você trabalha. Como em qualquer ferramenta de desenvolvimento, lembre-se de que você só deve abrir e trabalhar em repositórios que você conhece e confia. -### Environment isolation +### Isolamento de ambiente -{% data variables.product.prodname_codespaces %} is designed to keep your codespaces separate from each other, with each using its own virtual machine and network. +{% data variables.product.prodname_codespaces %} foi projetado para manter seus codespace separados um do outro, cada um usando sua própria máquina virtual e rede. -#### Isolated virtual machines +#### Máquinas virtuais isoladas -Each codespace is hosted on its own newly-built virtual machine (VM). Two codespaces are never co-located on the same VM. +Cada código é hospedado na sua própria máquina virtual recém-construída (VM). Dois códigos nunca são colocalizados na mesma VM. -Every time you restart a codespace, it's deployed to a new VM with the latest available security updates. +Toda vez que você reiniciar um codespace, ele será implantado em uma nova VM com as últimas atualizações de segurança disponíveis. -#### Isolated networking +#### Rede isolada -Each codespace has its own isolated virtual network. We use firewalls to block incoming connections from the internet and to prevent codespaces from communicating with each other on internal networks. By default, codespaces are allowed to make outbound connections to the internet. +Cada codespace tem a sua própria rede virtual isolada. Usamos firewalls para bloquear conexões recebidas da internet e impedir que os codespace se comuniquem entre si em redes internas. Por padrão, os codespace podem fazer conexões de saída na internet. ### Autenticação -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 %}. +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 %}. -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. +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. -The token's scope will vary depending on the access you have to the repository where the codespace was created: +O escopo do token irá variar dependendo do acesso ao repositório onde o codespace foi criado: -- **If you have write access to the repository**: The token will be scoped for read/write access to the repository. -- **If you only have read access to the repository**: The token will only allow the code to be cloned from the source repository. If you attempt to push to a private repo where you only have read access, {% data variables.product.prodname_codespaces %} will prompt you to create a personal fork of the repository. The token will then be updated to have read/write access to the new personal fork. -- **If you've enabled your codespace to access other repositories**: When a codespace has been granted [access to other repositories](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces), any codespace created from that repository will have read/write tokens scoped to the source repository. In addition, the tokens will also receive read access to other repositories indicated by the user or organization. +- **Se você tiver acesso de gravação ao repositório**: O token será escopo para acesso de leitura/gravação no repositório. +- **Se você tiver acesso somente leitura ao repositório**: O token somente permitirá que o c[odigo seja clonado a partir do repositório de origem. Se você tentar fazer push em um repositório privado onde você só tem acesso de leitura, {% data variables.product.prodname_codespaces %} solicitará que você crie uma bifurcação pessoal do repositório. O token será atualizado para ter acesso de leitura/gravação à nova bifurcação pessoal. +- **Se você habilitou seu codespace para acessar outros repositórios**: Quando um codespace receber [acesso a outros repositórios](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces), qualquer codespace criado a partir desse repositório terá escopo de leitura/gravação de tokens no repositório de origem. Além disso, os tokens também receberão acesso de leitura em outros repositórios indicados pelo usuário ou organização. -An organization's administrators specify which repositories should be considered trusted. An admin can [choose to trust](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces) none, all, or some of the organization's repositories. A codespace can't have greater permissions to access resources than the person who created it, even if the organization administrator has granted access to all users and all repositories. +Os administradores da organização especificam quais repositórios devem ser considerados confiáveis. Um administrador pode [optar por confiar](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces) em nenhum, todos ou em algum dos repositórios da organização. Um codespace não pode ter maiores permissões de acesso aos recursos do que a pessoa que o criou, mesmo que o administrador da organização tenha concedido acesso a todos os usuários e a todos os repositórios. -### Codespace connections +### Conexões de codespace -You can connect to your codespace using the TLS encrypted tunnel provided by the {% data variables.product.prodname_codespaces %} service. Only the creator of a codespace can connect to a codespace. Connections are authenticated with {% data variables.product.product_name %}. +Você pode conectar-se ao seu codespace usando o túnel criptografado TLS fornecido pelo serviço de {% data variables.product.prodname_codespaces %}. Somente o criador de um codespace pode conectar-se a um codespace. As conexões são autenticadas com {% data variables.product.product_name %}. -If you need to allow external access to services running on a codespace, you can enable port forwarding for private or public access. +Se você precisar permitir acesso externo a serviços em execução em um codespace, você poderá habilitar o encaminhamento de portas para acesso público ou privado. -### Port forwarding +### Encaminhamento de porta -If you need to connect to a service (such as a development web server) running within your codespace, you can configure port forwarding to make the service available on the internet. +Se você precisar conectar-se a um serviço (como um servidor web de desenvolvimento) em execução no seu codespace, você poderá configurar o encaminhamento de portas para tornar o serviço disponível na internet. -**Privately forwarded ports**: Are accessible on the internet, but only the codespace creator can access them, after authenticating to {% data variables.product.product_name %}. +**Portas encaminhadas em particular**: Podem ser acessadas na internet, mas somente o criador do codespace pode acessá-las, após efetuar a autenticação em {% data variables.product.product_name %}. -**Publicly forwarded ports**: Are accessible on the internet, and anyone on the internet can access them. No authentication is needed to access public forwarded ports. +**portas encaminhadas publicamente**: Podem ser acessadas na internet, e qualquer pessoa na internet pode acessá-las. Não é necessária autenticação para acessar portas públicas encaminhadas. -All forwarded ports are private by default, which means that you will need to authenticate before you can access the port. Access to a codespace's private forwarded ports is controlled by authentication cookies with a 3-hour expiry period. When the cookie expires, you will need to reauthenticate. +Todas as portas encaminhadas são privadas por padrão, o que significa que você precisará efetuar a autenticação antes de acessar a porta. O acesso às portas privadas encaminhadas por um codespace é controlado por cookies de autenticação, com um período de vencimento de 3 horas. Quando o cookie vencer, você deverá efetuar a autenticação novamente. -A public forwarded port will automatically revert back to private when you remove and re-add the port, or if you restart the codespace. +Uma porta pública encaminhada voltará automaticamente para a privada quando você remover e adicionar novamente a porta, ou se você reiniciar o codespace. -You can use the "Ports" panel to configure a port for public or private access, and can stop port forwarding when it's no longer required. For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)." +Você pode usar o painel "Portas" para configurar uma porta para acesso público ou privado, e você pode parar o encaminhamento de portas quando ela não for mais necessária. Para obter mais informações, consulte "[Encaminhando portas no seu codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)". -## Good security practices for your codespaces +## Práticas recomendadas de segurança para seus codespaces -Codespaces are designed to be security hardened by default. To help maintain this posture, we recommend that you follow good security practices during your development procedures: +Os codespaces são projetados para ter segurança enrijecida por padrão. Para ajudar a manter esta postura, recomendamos que você siga as práticas recomendadas de segurança durante seus procedimentos de desenvolvimento: -- As with any development tool, remember that you should only open and work within repositories you know and trust. -- Before you add new dependencies to the codespace, check whether they are well-maintained, and if they release updates to fix any security vulnerabilities found in their code. +- Como em qualquer ferramenta de desenvolvimento, lembre-se de que você só deve abrir e trabalhar em repositórios que você conhece e confia. +- Antes de adicionar novas dependências ao codespace, verifique se elas são bem mantidas e se lançam atualizações para corrigir quaisquer vulnerabilidades de segurança encontradas nos seus codespaces. -### Using secrets to access sensitive information +### Usando segredos para acessar informações confidenciais -Always use encrypted secrets when you want to use sensitive information (such as access tokens) in a codespace. You can access your secrets as environment variables in the codespace, including from the terminal. For example, you can launch a terminal within your codespace and use `echo $SECRET_NAME` to see the value of a secret. +Sempre use segredos criptografados quando você deseja usar informações confidenciais (como tokens de acesso) em um codespace. Você pode acessar seus segredos como variáveis de ambiente no codespace, inclusive a partir do terminal. Por exemplo, você pode iniciar um terminal dentro do seu codespace e usar `echo $SECRET_NAME` para ver o valor de um segredo. -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. +Os valores do segredo são copiados para variáveis de ambiente sempre que o codespace for retomado ou criado, Portanto, se você atualizar o valor de um segredo enquanto o codespace estiver em execução, você deverá suspender e retomar para retirar o valor atualizado. -For more information on secrets, see: -- "[Managing encrypted secrets for your 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)" +Para mais informações sobre segredos, consulte: +- "[Gerenciar segredos criptografados nos seus codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)" +- "[Gerenciando segredos criptografados do seu repositório e organização para os 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 +### Trabalhando com contribuições e repositórios de outras pessoas -When you create a codespace from a PR branch from a fork, the token in the codespace will vary depending on whether the repository is public or private: -- For a private repository, the codespace is granted access to both the fork and parent. -- For a public repository, the codespace will only have access to the fork and opening PRs on the parent. +Quando você cria um codespace a partir de um branch de PR a partir de uma bifurcação, o token na área do codespace irá variar dependendo se o repositório é público ou privado: +- Para um repositório privado, o codespace recebe acesso tanto à bigurcação quanto ao principal. +- Para um repositório público, o código só terá acesso à bifurcação e à abertura de PRs no principal. -### Additional good practices +### Práticas recomendadas adicionais -There are some additional good practices and risks that you should be aware of when using {% data variables.product.prodname_codespaces %}. +Há algumas práticas recomendadas e riscos adicionais dos quais você deve estar ciente ao usar {% data variables.product.prodname_codespaces %}. -#### Understanding a repository's devcontainer.json file +#### Compreendendo o arquivo devcontainer.json de um repositório -When creating a codespace, the [devcontainer.json](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) is parsed and applied from the source repo, if one exists. The devcontainer contains powerful features, such as installing third-party extensions and running arbitrary code through a supplied `postCreateCommand`. +Ao criar um codespace, o [devcontainer.json](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) é analisado e aplicado a partir do repositório de origem, se houver. O devcontainer contém funcionalidades poderosas como, por exemplo, instalar extensões de terceiros e executar código arbitrário por meio de um `postCreateCommand` fornecido. -#### Granting access through features +#### Conceder acesso por meio de funcionalidades -Certain development features can potentially add risk to your environment. For example, commit signing, secrets injected into environment variables, authenticated registry access, and packages access can all present potential security issues. We recommend that you only grant access to those who need it and adopt a policy of being as restrictive as possible. +Certos recursos de desenvolvimento podem potencialmente adicionar risco ao seu ambiente. Por exemplo, a assinatura, segredos injetados em variáveis de ambiente, acesso de registro autenticado e acesso a pacotes podem apresentar possíveis problemas de segurança. Recomendamos que se conceda acesso apenas àqueles que dela necessitem e que se adote uma política que seja o mais restritiva possível. -#### Using extensions +#### Usando extensões -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. +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. diff --git a/translations/pt-BR/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md b/translations/pt-BR/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md index 3b07012fd9..7ae097f923 100644 --- a/translations/pt-BR/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md +++ b/translations/pt-BR/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md @@ -1,6 +1,6 @@ --- -title: Understanding billing for Codespaces -intro: 'Learn how your {% data variables.product.prodname_codespaces %} usage is billed.' +title: Entendendo a cobrança para Codespaces +intro: 'Saiba como seu uso de {% data variables.product.prodname_codespaces %} é cobrado.' versions: fpt: '*' redirect_from: @@ -12,44 +12,44 @@ topics: - Codespaces - Billing product: '{% data reusables.gated-features.codespaces %}' -shortTitle: Understanding billing +shortTitle: Entendendo a cobrança --- -This article explains how billing works for your codespaces, and explains how your organization's billing manager can help. +Este artigo explica como a cobrança funciona para seus codespaces e explica como o gerente de cobrança da sua organização pode ajudar. -## Getting access to {% data variables.product.prodname_codespaces %} +## Obtendo acesso a {% data variables.product.prodname_codespaces %} -Your organization's administrator might limit {% data variables.product.prodname_codespaces %} usage to only specific user accounts. To get access, you will need to contact your billing manager. For more information, see "[Managing access and security for your codespaces](/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces)." +O administrador da sua organização pode limitar o uso de {% data variables.product.prodname_codespaces %} para apenas contas de usuário específicas. Para obter acesso, você deverá entrar em contato com o gerente de faturamento. Para obter mais informações, consulte "[Gerenciar acesso e segurança para seus codespaces](/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces)". -## How much it costs to use {% data variables.product.prodname_codespaces %} +## Quanto custa usar {% data variables.product.prodname_codespaces %} -To see the pricing for {% data variables.product.prodname_codespaces %} usage, see "[{% data variables.product.prodname_codespaces %} pricing](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)." +Para ver os preços para uso de {% data variables.product.prodname_codespaces %}, consulte "[Preços de {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)" -## How your codespace usage is billed +## Como é feita a cobrança do seu codespace -Your codespace is billed for its compute minutes and for the amount of storage it uses on disk. +A cobrança do seu codespace é feita por minutos de computação e para a quantidade de armazenamento que usa no disco. -### Understanding what compute minutes are -Your codespace is billed for the number of minutes that it's active. If your codespaces window is left idle for 30 minutes, it will automatically shutdown, and compute billing for the codespace will end until you start the codespace again. +### Ententendo quais minutos de computação são +A cobrança do seu codespace é feita pelo número de minutos ativos. Se sua janela de codespace estiver inativa por 30 minutos, ela será desligada automaticamente, e o cálculo da cobrança para o codespace terminará até que você inicie o codespace novamente. -### Understanding how codespace storage is billed -For {% data variables.product.prodname_codespaces %}, storage is defined to include any files relating to your codespace, such as the cloned repository, configuration files, and extensions, among others. This storage is billed while your codespace is shutdown. The storage billing for a codespace ends when you manually delete it from https://github.com/codespaces. +### Entender como o armazenamento de código é cobrado +Para o {% data variables.product.prodname_codespaces %}, o armazenamento é definido para incluir todos os arquivos relacionados ao seu codespace, como o repositório clonado, arquivos de configuração e extensões, entre outros. Este armazenamento é cobrado enquanto seu codespace é fechado. A cobrança de armazenamento de um código termina quando você o exclui manualmente de https://github.com/codespaces. -## How spending limits work +## Como os limites de gastos funcionam -Before your organization can use {% data variables.product.prodname_codespaces %}, your billing manager will need to set a spending limit. For more information, see "[Managing spending limits for {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)." +Antes de sua organização poder usar {% data variables.product.prodname_codespaces %}, seu gerente de cobrança deverá definir um limite de gastos. Para obter mais informações, consulte "[Gerenciando limites de gastos para {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)". -## Exporting changes when you have reached your spending limit +## Exportar alterações quando você atingir seu limite de gastos {% data reusables.codespaces.exporting-changes %} -## Checking your current usage and limits -If you need to check your current usage or spending limit, contact your organization's billing manager. For more information, see "[Viewing your Codespaces usage](/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage)." +## Verificando o uso e limites atuais +Se você precisar verificar seu limite de uso atual ou de gastos, entre em contato com o gerente de cobrança da sua organização. Para obter mais informações, consulte "[Visualizando o uso dos seus codespaces](/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage)". -## Codespaces can be automatically deleted +## Os codespaces podem ser excluídos automaticamente -Your codespace will be automatically deleted when you are removed from an organization or repository. +Seu código será automaticamente excluído quando você for removido de uma organização ou repositório. -## Deleting your unused codespaces +## Excluindo seus codespaces não utilizados -You can manually delete your codespaces in https://github.com/codespaces and from within {% data variables.product.prodname_vscode %}. To reduce the size of a codespace, you can manually delete files using the terminal or from within {% data variables.product.prodname_vscode %}. +Você pode excluir manualmente os seus codespaces em https://github.com/codespaces e de dentro de {% data variables.product.prodname_vscode %}. Para reduzir o tamanho de um codespace, você pode excluir arquivos manualmente usando o terminal ou de dentro de {% data variables.product.prodname_vscode %}. diff --git a/translations/pt-BR/content/codespaces/codespaces-reference/using-the-command-palette-in-codespaces.md b/translations/pt-BR/content/codespaces/codespaces-reference/using-the-command-palette-in-codespaces.md index 8de22f4452..750baaf670 100644 --- a/translations/pt-BR/content/codespaces/codespaces-reference/using-the-command-palette-in-codespaces.md +++ b/translations/pt-BR/content/codespaces/codespaces-reference/using-the-command-palette-in-codespaces.md @@ -35,7 +35,7 @@ Para ver todos os comandos relacionados a {% data variables.product.prodname_git ### Suspender ou interromper um codespace -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. +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 parar o contêiner do seu codespace, acesse a Paleta de Comando e, em seguida, comece a digitar "parar". Selecione **Codespaces: Parar o codespace atual**. diff --git a/translations/pt-BR/content/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project.md b/translations/pt-BR/content/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project.md index 01b984c03c..53e542d6e0 100644 --- a/translations/pt-BR/content/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project.md +++ b/translations/pt-BR/content/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project.md @@ -21,7 +21,7 @@ shortTitle: Configure o seu projeto ## Sobre contêineres de desenvolvimento -Um contêiner de desenvolvimento, ou dev container, é o ambiente que {% data variables.product.prodname_codespaces %} usa para fornecer as ferramentas e tempos de execução de que seu projeto precisa para desenvolvimento. When working with a dev container in {% data variables.product.prodname_codespaces %} you can either [use the default configuration](#using-the-default-configuration), [use a predefined configuration](#using-a-predefined-container-configuration), or [create your own configuration](#creating-a-custom-codespace-configuration). A opção escolhida depende das ferramentas, tempo de execução, dependências e fluxos de trabalho que um usuário pode precisar para ter sucesso com seu projeto. +Um contêiner de desenvolvimento, ou dev container, é o ambiente que {% data variables.product.prodname_codespaces %} usa para fornecer as ferramentas e tempos de execução de que seu projeto precisa para desenvolvimento. Ao trabalhar com um contêiner de desenvolvimento em {% data variables.product.prodname_codespaces %} você pode [usar a configuração padrão](#using-the-default-configuration), [usar uma configuração predefinida](#using-a-predefined-container-configuration) ou [criar sua própria configuração](#creating-a-custom-codespace-configuration). A opção escolhida depende das ferramentas, tempo de execução, dependências e fluxos de trabalho que um usuário pode precisar para ter sucesso com seu projeto. {% data variables.product.prodname_codespaces %} permite a personalização em uma base por projeto e por branch com um arquivo `devcontainer.json`. Este arquivo de configuração determina o ambiente de cada novo codespace que alguém criar para o repositório, definindo um contêiner de desenvolvimento que pode incluir estruturas, ferramentas, extensões e encaminhamento de porta. Um arquivo Docker também pode ser usado ao lado do arquivo `devcontainer.json` na pasta `devcontainer` para definir tudo o que é necessário para criar uma imagem de contêiner. diff --git a/translations/pt-BR/content/codespaces/customizing-your-codespace/index.md b/translations/pt-BR/content/codespaces/customizing-your-codespace/index.md index 80c90ab241..e18c8e4b77 100644 --- a/translations/pt-BR/content/codespaces/customizing-your-codespace/index.md +++ b/translations/pt-BR/content/codespaces/customizing-your-codespace/index.md @@ -1,6 +1,6 @@ --- -title: Customizing your codespace -intro: '{% data variables.product.prodname_codespaces %} é um ambiente dedicado a você. You can configure your repositories with a dev container to define their default Codespaces environment, and personalize your development experience across all of your codespaces with dotfiles and Settings Sync.' +title: Personalizando seu codespace +intro: '{% data variables.product.prodname_codespaces %} é um ambiente dedicado a você. É possível configurar seus repositórios com um contêiner de desenvolvimento para definir seu ambiente padrão de codespace e personalizar sua experiência de desenvolvimento por meio de todos os seus códigos com dotfiles e Settings Sync.' product: '{% data reusables.gated-features.codespaces %}' versions: free-pro-team: '*' diff --git a/translations/pt-BR/content/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account.md b/translations/pt-BR/content/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account.md index aeb3f128fc..b72d7eb1c4 100644 --- a/translations/pt-BR/content/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account.md +++ b/translations/pt-BR/content/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account.md @@ -32,7 +32,7 @@ Os mantenedores do projeto também podem definir uma configuração-padrão que A sincronização de configurações permite que você compartilhe configurações como configurações, atalhos de teclado, snippets, extensões e estado da interface de usuário entre as máquinas e instâncias de {% data variables.product.prodname_vscode %}. -To enable Settings Sync, in the bottom-left corner of the Activity Bar, select {% octicon "gear" aria-label="The gear icon" %} and click **Turn on Settings Sync…**. From the dialog, select which settings you'd like to sync. +Para habilitar a sincronização de configurações, no canto inferior esquerdo da barra de atividades, selecione {% octicon "gear" aria-label="The gear icon" %} e clique **Habilitar as configurações de sincronização…**. Na caixa de diálogo, selecione quais configurações você gostaria de sincronizar. ![Opção de configuração de sincronização no menu de gerenciamento](/assets/images/help/codespaces/codespaces-manage-settings-sync.png) @@ -67,31 +67,31 @@ Quaisquer alterações no repositório de `dotfiles` serão aplicadas apenas a c {% endnote %} -### Enabling your dotfiles repository for {% data variables.product.prodname_codespaces %} +### Habilitando o repositório de dotfiles para {% data variables.product.prodname_codespaces %} -You can use your public `dotfiles` repository to personalize your {% data variables.product.prodname_codespaces %} environment. Once you set up that repository, you can add your scripts, preferences, and configurations to it. You then need to enable your dotfiles from your personal {% data variables.product.prodname_codespaces %} settings page. +Você pode usar o seu repositório `dotfiles` público para personalizar o seu ambiente de {% data variables.product.prodname_codespaces %}. Depois de configurar esse repositório, é possível adicionar seus scripts, preferências e configurações a ele. Em seguida, você deverá habilitar os seus dotfiles na sua página pessoal de configurações de {% data variables.product.prodname_codespaces %}. {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.codespaces-tab %} -1. Under "Dotfiles", select "Automatically install dotfiles" so that {% data variables.product.prodname_codespaces %} automatically installs your dotfiles into every new codespace you create. ![Installing dotfiles](/assets/images/help/codespaces/install-dotfiles.png) +1. Em "Dotfiles", selecione "Instalar dotfiles automaticamente" para que {% data variables.product.prodname_codespaces %} instale automaticamente seus dotfiles em cada novo codespace que você criar. ![Instalando dotfiles](/assets/images/help/codespaces/install-dotfiles.png) {% note %} - **Note:** This option is only available if you've created a public `dotfiles` repository for your user account. + **Observação:** Esta opção só está disponível se você criou um repositório público de `dotfiles` para a sua conta de usuário. {% endnote %} -You can add further script, preferences, configuration files to your dotfiles repository or edit existing files whenever you want. Changes to settings will only be picked up by new codespaces. +Você pode adicionar mais script, preferências e arquivos de configuração ao repositório de dotfiles ou editar arquivos existentes sempre que quiser. As alterações nas configurações só serão selecionadas por novos codespaces. -## Other available settings +## Outras configurações disponíveis -You can also personalize {% data variables.product.prodname_codespaces %} using additional [Codespaces settings](https://github.com/settings/codespaces): +Você também pode personalizar {% data variables.product.prodname_codespaces %} usando outras [Configurações de codespace](https://github.com/settings/codespaces): -- To set your default region, see "[Setting your default region for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces)." -- To set your editor, see "[Setting your default editor for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/setting-your-default-editor-for-codespaces)." -- To add encrypted secrets, see "[Managing encrypted secrets for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)." -- To enable GPG verification, see "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)." -- To allow your codespaces to access other repositories, see "[Managing access and security for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)." +- Para definir sua região padrão, consulte "[Definindo sua região padrão para {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces)." +- Para definir seu editor, consulte "[Definindo seu editor padrão para {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/setting-your-default-editor-for-codespaces)" +- Para adicionar segredos criptografados, consulte "[Gerenciar segredos criptografados para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces)". +- Para habilitar a verificação do GPG, consulte "[Gerenciar a verificação de GPG para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)." +- Para permitir que seus codespaces acessem outros repositórios, consulte "[Gerenciar acesso e segurança para {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)". ## Leia mais diff --git a/translations/pt-BR/content/codespaces/customizing-your-codespace/prebuilding-codespaces-for-your-project.md b/translations/pt-BR/content/codespaces/customizing-your-codespace/prebuilding-codespaces-for-your-project.md index d5a23acd64..18ebaa63da 100644 --- a/translations/pt-BR/content/codespaces/customizing-your-codespace/prebuilding-codespaces-for-your-project.md +++ b/translations/pt-BR/content/codespaces/customizing-your-codespace/prebuilding-codespaces-for-your-project.md @@ -1,6 +1,6 @@ --- -title: Prebuilding Codespaces for your project -intro: You can configure your project to prebuild a codespace automatically each time you push a change to your repository. +title: Codespaces de pré-criação para o seu projeto +intro: Você pode configurar o seu projeto para pré-criar um codespace automaticamente cada vez que você fizer push de uma alteração no repositório. versions: fpt: '*' type: how_to @@ -9,17 +9,17 @@ topics: - Set up - Fundamentals product: '{% data reusables.gated-features.codespaces %}' -shortTitle: Prebuilding Codespaces +shortTitle: Codespace de pré-criação --- {% note %} -**Note:** This feature is currently in private preview. +**Observação:** Este recurso está atualmente em pré-visualização privada. {% endnote %} -## About prebuilding a Codespace +## Sobre a pré-criação de um codespace -Prebuilding your codespaces allows you to be more productive and access your codespace faster. This is because any source code, editor extensions, project dependencies, commands, or configurations have already been downloaded, installed, and applied before you begin your coding session. Once you push changes to your repository, {% data variables.product.prodname_codespaces %} automatically handles configuring the builds. +A pré-construção de seus codespace permite que você seja mais produtivo e acesse o seu codespace mais rapidamente. Isso ocorre porque qualquer código-fonte, extensões de editor, dependências de projetos, comandos, ou configurações já foram baixadas, instaladas e aplicadas antes de começar sua sessão de codificação. Depois de fazer push das alterações no repositório, o {% data variables.product.prodname_codespaces %} gerencia automaticamente a configuração das criações. -The ability to prebuild Codespaces is currently in private preview. To get access to this feature, contact codespaces@github.com. +A capacidade de pré-criar codespace está atualmente em visualização privada. Para obter acesso a este recurso, entre em contato com codespaces@github.com. diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/changing-the-machine-type-for-your-codespace.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/changing-the-machine-type-for-your-codespace.md index a730694d61..b1b90ffae8 100644 --- a/translations/pt-BR/content/codespaces/developing-in-codespaces/changing-the-machine-type-for-your-codespace.md +++ b/translations/pt-BR/content/codespaces/developing-in-codespaces/changing-the-machine-type-for-your-codespace.md @@ -1,7 +1,7 @@ --- -title: Changing the machine type for your codespace -shortTitle: Changing the machine type -intro: 'You can change the type of machine that''s running your codespace, so that you''re using resources appropriate for work you''re doing.' +title: Alterando o tipo de máquina para seu codespace +shortTitle: Alterando o tipo da máquina +intro: Você pode alterar o tipo de máquina que está executando o seu codespace para você usar os recursos apropriados para o trabalho que está fazendo. product: '{% data reusables.gated-features.codespaces %}' versions: free-pro-team: '*' @@ -9,51 +9,51 @@ topics: - Codespaces --- -## About machine types +## Sobre os tipos de máquina {% note %} -**Note:** You can only select or change the machine type if you are a member of an organization using {% data variables.product.prodname_codespaces %} and are creating a codespace on a repository owned by that organization. +**Observação:** Você só pode selecionar ou alterar o tipo de máquina se você for integrante de uma organização usando {% data variables.product.prodname_codespaces %} e estiver criando um codespace em um repositório pertencente a essa organização. {% endnote %} {% data reusables.codespaces.codespaces-machine-types %} -You can choose a machine type either when you create a codespace or you can change the machine type at any time after you've created a codespace. +Você pode escolher um tipo de máquina ao criar um codespace ou você pode mudar o tipo de máquina a qualquer momento depois de criar um codespace. -For information on choosing a machine type when you create a codespace, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)." For information on changing the machine type within {% data variables.product.prodname_vscode %}, see "[Using {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code#changing-the-machine-type-in-visual-studio-code)." +Para obter informações sobre como escolher um tipo de máquina ao criar um codespace, consulte "[Criando um codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)". Para informações sobre como mudar o tipo de máquina em {% data variables.product.prodname_vscode %}, consulte "[Usando {% data variables.product.prodname_codespaces %} em {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code#changing-the-machine-type-in-visual-studio-code)." ## Alterar o tipo da máquina em {% data variables.product.prodname_dotcom %} {% data reusables.codespaces.your-codespaces-procedure-step %} - The current machine type for each of your codespaces is displayed. + O tipo de máquina atual para cada um dos seus codespaces é exibido. - !['Your codespaces' list](/assets/images/help/codespaces/your-codespaces-list.png) + ![Lista "Seus codespaces"](/assets/images/help/codespaces/your-codespaces-list.png) -1. Click the ellipsis (**...**) to the right of the codespace you want to modify. -1. Click **Change machine type**. +1. Clique nas reticências (**...**) à direita do codespace que você deseja modificar. +1. Clique **Alterar tipo de máquina**. - !['Change machine type' menu option](/assets/images/help/codespaces/change-machine-type-menu-option.png) + ![Opção de menu '"Alterar tipo de máquina"](/assets/images/help/codespaces/change-machine-type-menu-option.png) -1. Choose the required machine type. +1. Escolha o tipo de máquina necessária. -2. Click **Update codespace**. +2. Clique **Atualizar o codespace**. - The change will take effect the next time your codespace restarts. + A alteração entrará em vigor na próxima vez que seu codespace for reiniciado. -## Force an immediate update of a currently running codespace +## Forçar uma atualização imediata de um codespace em execução no momento -If you change the machine type of a codespace you are currently using, and you want to apply the changes immediately, you can force the codespace to restart. +Se você mudar o tipo de máquina de um codespace que você está usando atualmente desejar aplicar as alterações imediatamente, você poderá forçar a reinicialização do codespace. -1. At the bottom left of your codespace window, click **{% data variables.product.prodname_codespaces %}**. +1. No canto inferior esquerdo da janela do seu codespace, clique em **{% data variables.product.prodname_codespaces %}**. - ![Click '{% data variables.product.prodname_codespaces %}'](/assets/images/help/codespaces/codespaces-button.png) + ![Clique em "{% data variables.product.prodname_codespaces %}"](/assets/images/help/codespaces/codespaces-button.png) -1. From the options that are displayed at the top of the page select **Codespaces: Stop Current Codespace**. +1. Entre opções que são exibidas na parte superior da página, selecione **Codespaces: Parar os codespaces atuais**. - !['Suspend Current Codespace' option](/assets/images/help/codespaces/suspend-current-codespace.png) + ![Opção "Suspender codespace atual"](/assets/images/help/codespaces/suspend-current-codespace.png) -1. After the codespace is stopped, click **Restart codespace**. +1. Após a interrupção do codespace, clique em **Reiniciar o codespace**. - ![Click 'Resume'](/assets/images/help/codespaces/resume-codespace.png) + ![Clique em "Retomar"](/assets/images/help/codespaces/resume-codespace.png) 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 def9bd63ec..aea1eba68e 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 @@ -22,42 +22,42 @@ Você pode criar um codespace em {% data variables.product.prodname_dotcom_the_w Os codespaces são associados a um branch específico de um repositório e o repositório não pode estar vazio. {% data reusables.codespaces.concurrent-codespace-limit %} Para obter mais informações, consulte "[Excluir um codespace](/github/developing-online-with-codespaces/deleting-a-codespace)". -When you create a codespace, a number of steps happen to create and connect you to your development environment: +Ao criar um codespace, várias etapas acontecem para criar e conectar você ao seu ambiente de desenvolvimento: -- Step 1: VM and storage are assigned to your codespace. -- Step 2: Container is created and your repository is cloned. -- Step 3: You can connect to the codespace. -- Step 4: Codespace continues with post-creation setup. +- Etapa 1: A VM e o armazenamento são atribuídos ao seu codespace. +- Etapa 2: O contêiner é criado e seu repositório é clonado. +- Passo 3: Você pode conectar-se ao codespace. +- Etapa 4: O codespace continua com a configuração pós-criação. -For more information on what happens when you create a codespace, see "[Deep Dive](/codespaces/getting-started/deep-dive)." +Para obter mais informações sobre o que acontece quando você cria um codespace, consulte "[Aprofundamento](/codespaces/getting-started/deep-dive)". {% data reusables.codespaces.use-visual-studio-features %} {% data reusables.codespaces.you-can-see-all-your-codespaces %} -## Access to {% data variables.product.prodname_codespaces %} +## Acesso a {% data variables.product.prodname_codespaces %} {% data reusables.codespaces.availability %} -When you have access to {% data variables.product.prodname_codespaces %}, you'll see a "Codespaces" tab within the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu when you view a repository. +Quando você tem acesso a {% data variables.product.prodname_codespaces %}, você verá uma aba "Codespace" dentro do menu suspenso ** Código de{% octicon "code" aria-label="The code icon" %} ** ao visualizar um repositório. -You'll have access to codespaces under the following conditions: +Você terá acesso a codespaces nas seguintes condições: -* You are a member of an organization that has enabled {% data variables.product.prodname_codespaces %} and set a spending limit. -* An organization owner has granted you access to {% data variables.product.prodname_codespaces %}. -* The repository is owned by the organization that has enabled {% data variables.product.prodname_codespaces %}. +* Você é um integrante de uma organização que habilitou {% data variables.product.prodname_codespaces %} e definiu um limite de gastos. +* Um proprietário da organização concedeu a você acesso a {% data variables.product.prodname_codespaces %}. +* O repositório pertence à organização que habilitou {% data variables.product.prodname_codespaces %}. {% note %} -**Note:** Individuals who have already joined the beta with their personal {% data variables.product.prodname_dotcom %} account will not lose access to {% data variables.product.prodname_codespaces %}, however {% data variables.product.prodname_codespaces %} for individuals will continue to remain in beta. +**Observação:** As pessoas que já aderiram ao beta com sua conta pessoal do {% data variables.product.prodname_dotcom %} não perderão acesso a {% data variables.product.prodname_codespaces %}. No entanto, {% data variables.product.prodname_codespaces %} para as pessoas, continuará sendo beta. {% endnote %} -Organization owners can allow all members of the organization to create codespaces, limit codespace creation to selected organization members, or disable codespace creation. For more information about managing access to codespaces within your organization, see "[Enable Codespaces for users in your organization](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization#enable-codespaces-for-users-in-your-organization)." +Os proprietários da organização podem permitir que todos os integrantes da organização criem codespaces, limitem a criação de códigos aos integrantes selecionados da organização ou desabilitem a criação de codespace. Para obter mais informações sobre como gerenciar o acesso aos codespaces dentro da sua organização, consulte "[Habilitar codespace para usuários da sua organização](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization#enable-codespaces-for-users-in-your-organization)". -Before {% data variables.product.prodname_codespaces %} can be used in an organization, an owner or billing manager must have set a spending limit. For more information, see "[About spending limits for Codespaces](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces#about-spending-limits-for-codespaces)." +Antes de {% data variables.product.prodname_codespaces %} pode ser usado em uma organização, um proprietário ou gerente de cobrança deverá ter um limite de gastos. Para obter mais informações, consulte "[Sobre limites de gastos para codespaces](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces#about-spending-limits-for-codespaces)". -If you would like to create a codespace for a repository owned by your personal account or another user, and you have permission to create repositories in an organization that has enabled {% data variables.product.prodname_codespaces %}, you can fork user-owned repositories to that organization and then create a codespace for the fork. +Se você deseja criar um codespace para um repositório pertencente à sua conta pessoal ou outro usuário e você tem permissão para criar repositórios em uma organização que habilitou {% data variables.product.prodname_codespaces %}, você poderá criar uma bifurcação de repositórios pertencentes ao usuário na organização e, em seguida, criar um codespace para a bifurcação. ## Criar um codespace @@ -66,8 +66,8 @@ If you would like to create a codespace for a repository owned by your personal ![Menu suspenso do branch](/assets/images/help/codespaces/branch-drop-down.png) -3. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu, and in the **Codespaces** tab, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. +3. No nome do repositório, use o menu suspenso **Código de {% octicon "code" aria-label="The code icon" %}** e na aba **Codespaces** de código, clique em {% octicon "plus" aria-label="The plus icon" %} **Novo codespace**. ![Botão de codespace novo](/assets/images/help/codespaces/new-codespace-button.png) - If you are a member of an organization and are creating a codespace on a repository owned by that organization, you can select the option of a different machine type. From the dialog, choose a machine type and then click **Create codespace**. ![Machine type choice](/assets/images/help/codespaces/choose-custom-machine-type.png) + Se você é integrante de uma organização e está criando um codespace em um repositório pertencente a essa organização, você poderá selecionar a opção de um tipo de máquina diferente. Na caixa de diálogo, escolha um tipo de máquina e clique em **Criar codespace**. ![Escolha do tipo da máquina](/assets/images/help/codespaces/choose-custom-machine-type.png) diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/deleting-a-codespace.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/deleting-a-codespace.md index 9d09b22f57..19c979dcb5 100644 --- a/translations/pt-BR/content/codespaces/developing-in-codespaces/deleting-a-codespace.md +++ b/translations/pt-BR/content/codespaces/developing-in-codespaces/deleting-a-codespace.md @@ -24,7 +24,7 @@ topics: {% endnote %} -1. Navigate to the "Your Codespaces" page at [github.com/codespaces](https://github.com/codespaces). +1. Acesse a página "Seus codespaces" em [github.com/codespaces](https://github.com/codespaces). 2. À direita do código que você deseja excluir, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, depois em **{% octicon "trash" aria-label="The trash icon" %} Apagar** ![Botão excluir](/assets/images/help/codespaces/delete-codespace.png) 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 23564efac9..9732672964 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 @@ Para obter mais informações sobre como usar {% data variables.product.prodname {% data reusables.codespaces.connect-to-codespace-from-vscode %} -{% data reusables.codespaces.use-chrome %} For more information, see "[Troubleshooting Codespaces clients](/codespaces/troubleshooting/troubleshooting-codespaces-clients)." +{% data reusables.codespaces.use-chrome %} Para obter mais informações, consulte "[Solução de problemas de codespaces](/codespaces/troubleshooting/troubleshooting-codespaces-clients)". ### Personalizando seu codespace @@ -57,4 +57,4 @@ A Paleta de Comando permite acessar e gerenciar muitas funcionalidades para {% d 1. {% data reusables.codespaces.you-can-see-all-your-codespaces %} 2. Clique no nome do codespace em que você deseja desenvolver. ![Nome do codespace](/assets/images/help/codespaces/click-name-codespace.png) -Alternatively, you can see any active codespaces for a repository by navigating to that repository and selecting **{% octicon "code" aria-label="The code icon" %} Code**. The drop-down menu will display all active codespaces for a repository. +Como alternativa, você pode ver qualquer codespace ativo para um repositório acessando esse repositório e selecionando o **Código de {% octicon "code" aria-label="The code icon" %}**. O menu suspenso exibirá todos os codespaces ativos de um repositório. diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md index 620f82a54d..bafd011485 100644 --- a/translations/pt-BR/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md +++ b/translations/pt-BR/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md @@ -44,7 +44,7 @@ Você pode etiquetar uma porta para tornar a porta mais facilmente identificáve ## Compartilhar uma porta -If you want to share a forwarded port with others, you need to make the port public. Após tornar uma porta pública, qualquer pessoa com a URL da porta poderá ver o aplicativo em execução sem precisar efetuar a autenticação. +Se você quiser compartilhar uma porta encaminhada com outras pessoas, você deverá tornar a porta pública. Após tornar uma porta pública, qualquer pessoa com a URL da porta poderá ver o aplicativo em execução sem precisar efetuar a autenticação. {% data reusables.codespaces.navigate-to-ports-tab %} 1. Clique com o botão direito na porta que você deseja compartilhar e clique em **Tornar pública**. ![Opção para tornar a porta pública no menu com o clique com o botão direito](/assets/images/help/codespaces/make-public-option.png) diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/index.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/index.md index 94681e88af..ccf8bc1ddf 100644 --- a/translations/pt-BR/content/codespaces/developing-in-codespaces/index.md +++ b/translations/pt-BR/content/codespaces/developing-in-codespaces/index.md @@ -15,6 +15,5 @@ children: - /forwarding-ports-in-your-codespace - /changing-the-machine-type-for-your-codespace - /using-codespaces-in-visual-studio-code - - /web-based-editor --- diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests.md index 104fc49cf4..001594bb65 100644 --- a/translations/pt-BR/content/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests.md +++ b/translations/pt-BR/content/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests.md @@ -1,7 +1,7 @@ --- -title: Using Codespaces for pull requests +title: Usando codespaces para pull requests shortTitle: Pull requests -intro: 'You can use {% data variables.product.prodname_codespaces %} in your development workflow to create pull requests, review pull requests, and address review comments.' +intro: 'Você pode usar {% data variables.product.prodname_codespaces %} no seu fluxo de trabalho de desenvolvimento para criar pull requests, revisar pull requests e resolver comentários de revisão.' product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' @@ -14,28 +14,28 @@ topics: ## Sobre pull requests no {% data variables.product.prodname_codespaces %} -{% data variables.product.prodname_codespaces %} provides you with many of the capabilities you might need to work with pull requests: +{% data variables.product.prodname_codespaces %} fornece a você muitas das funcionalidades que você pode precisar para trabalhar com pull requests: -- [Create a pull request](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#raising-a-pull-request) - Using either the Terminal and Git commands or the Source Control view, you can create pull requests just as you would on {% data variables.product.prodname_dotcom_the_website %}. If the repository uses a pull request template, you'll be able to use this within the Source Control view. -- [Open a pull request](#opening-a-pull-request-in-codespaces) – You can open an existing pull request in a codespace, provided you have codespace access to the branch that is being merged in. -- [Review a pull request](#reviewing-a-pull-request-in-codespaces) - Once you have opened a pull request in a codespace, you can use the "GitHub Pull Request" view to add review comments and approve pull requests. You can also use {% data variables.product.prodname_codespaces %} to [view review comments](#view-comments-from-a-review-in-codespaces). +- [Cria um pull request](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#raising-a-pull-request) - Ao usar os comandos Terminal e Git ou a visão de controle de origem, você pode criar pull requests da mesma forma que faria em {% data variables.product.prodname_dotcom_the_website %}. Se o repositório usar um modelo de pull request, você poderá usá-lo na visualização de controle de origem. +- [Abra um pull request](#opening-a-pull-request-in-codespaces) - Você pode abrir um pull request existente em um codespace, desde que você tenha acesso a um acesso de codespace ao branch no qual que está sendo mesclado. +- [Revise um pull request](#reviewing-a-pull-request-in-codespaces) - Após abrir um pull request em um codespace, você poderá usar a vista "Pull request do GitHub" para adicionar comentários e aprovar pull requests. Você também pode usar {% data variables.product.prodname_codespaces %} para [ver os comentários da revisão](#view-comments-from-a-review-in-codespaces). -## Opening a pull request in {% data variables.product.prodname_codespaces %} +## Abrir um pull request em {% data variables.product.prodname_codespaces %} {% data reusables.repositories.sidebar-pr %} -2. In the list of pull requests, click the pull request you'd like to open in {% data variables.product.prodname_codespaces %}. -3. On the right-hand side of your screen, click **{% octicon "code" aria-label="The code icon" %} Code**. -4. From the {% data variables.product.prodname_codespaces %} tab, click **New codespace**. ![Option to open PR in a codespace](/assets/images/help/codespaces/open-with-codespaces-pr.png) +2. Na lista de pull requests, clique no pull request que deseja abrir em {% data variables.product.prodname_codespaces %}. +3. No lado direito da sua tela, clique em **Código de {% octicon "code" aria-label="The code icon" %}**. +4. Na aba de {% data variables.product.prodname_codespaces %}, clique em **Novo codespace**. ![Opção para abrir RP em um codespace](/assets/images/help/codespaces/open-with-codespaces-pr.png) -## Reviewing a pull request in {% data variables.product.prodname_codespaces %} +## Revendo um pull request em {% data variables.product.prodname_codespaces %} {% data reusables.codespaces.review-pr %} -For more information on reviewing a pull request, see "[Reviewing proposed changes in a pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)." +Para obter mais informações sobre a revisão de um pull request, consulte "[Revisando alterações propostas em um pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)". -## View comments from a review in {% data variables.product.prodname_codespaces %} +## Visualizar de uma revisão em {% data variables.product.prodname_codespaces %} -Once you have received feedback on a pull request, you can [open it in a codespace](#opening-a-pull-request-in-codespaces) to see the [review comments](#reviewing-a-pull-request-in-codespaces). From there you can respond to comments, add reactions, or dismiss the review. +Depois de receber feedback em um pull request, você poderá [abri-lo em um codespace](#opening-a-pull-request-in-codespaces) para ver os [comentários de revisão](#reviewing-a-pull-request-in-codespaces). A partir de lá você pode responder a comentários, adicionar reações ou ignorar a revisão. - ![Option to open PR in a codespace](/assets/images/help/codespaces/incorporating-codespaces.png) + ![Opção para abrir RP em um codespace](/assets/images/help/codespaces/incorporating-codespaces.png) 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 d5702d3e8b..b7eb3ca21d 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 @@ -30,9 +30,7 @@ Um fluxo de trabalho típico para atualizar um arquivo que usa {% data variables ## Criar ou trocar de branches -1. Se o branch atual não for mostrado na barra de status, na parte inferior do seu codespace, clique com o botão direito na barra de status e selecione **Controle de origem**. -1. Clique no nome do branch na barra de status. ![O branch na barra de status](/assets/images/help/codespaces/branch-in-status-bar.png) -1. No menu suspenso, clique no branch para o qual você deseja alternar ou digite o nome de um novo branch e clique em **Criar novo branch**. ![Escolha no menu do branch](/assets/images/help/codespaces/create-new-branch.png) +{% data reusables.codespaces.create-or-switch-branch %} {% tip %} @@ -48,7 +46,7 @@ Você pode fazer pull das alterações do repositório remoto para seu codespace 1. Na parte superior da barra lateral, clique na elipse (**...**). ![Botão Elipsis para visualizar e mais ações](/assets/images/help/codespaces/source-control-ellipsis-button.png) 1. No menu suspenso, clique em **Pull**. -If the dev container configuration has been changed since you created the codespace, you can apply the changes by rebuilding the container for the codespace. Para obter mais informações, consulte "[Configurar codespaces para o seu projeto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)". +Se a configuração do contêiner dev foi alterada desde que você criou o codespace, você pode aplicar as alterações reconstruindo o contêiner para o codespace. Para obter mais informações, consulte "[Configurar codespaces para o seu projeto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)". ## Configurar o seu codespace para buscar novas alterações automaticamente @@ -64,16 +62,11 @@ Se a operação de busca detectarem novas alterações no repositório remoto, v ## Fazendo commit das suas alterações -{% data reusables.codespaces.source-control-display-dark %} -1. Para testar suas alterações, clique **+** ao lado do arquivo que você alterou, ou ao lado de **Alterações** se você mudou vários arquivos e quiser testar todos. ![Barra lateral de controle de origem com botão de staging destacado](/assets/images/help/codespaces/codespaces-commit-stage.png) -1. Digite uma mensagem do commit que descreve a alteração que você fez. ![Barra lateral do controle de origem com uma mensagem de commit](/assets/images/help/codespaces/codespaces-commit-commit-message.png) -1. Para fazer commit das alterações em fase de preparação, clique na marca de seleção na parte superior da barra lateral de controle de origem. ![Clique no ícone da marca de verificação](/assets/images/help/codespaces/codespaces-commit-checkmark-icon.png) +{% data reusables.codespaces.source-control-commit-changes %} ## Abrindo um pull request -1. Depois de realizar alterações na sua cópia local do repositório, clique no ícone **Criar Pull Request**. ![Barra lateral de controle de origem com botão de staging destacado](/assets/images/help/codespaces/codespaces-commit-pr-button.png) -1. Verifique se o branch local e o repositório do qual você está fazendo merge, o branch remoto e o repositório no qual você está fazendo merge estão corretos. Em seguida, dê ao pull request um título e uma descrição. ![Barra lateral de controle de origem com botão de staging destacado](/assets/images/help/codespaces/codespaces-commit-pr.png) -1. Clique em **Criar**. +{% data reusables.codespaces.source-control-pull-request %} ## Fazer push das alterações para o seu repositório remoto 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 4c34e70c76..a50956e4e1 100644 --- a/translations/pt-BR/content/codespaces/getting-started/deep-dive.md +++ b/translations/pt-BR/content/codespaces/getting-started/deep-dive.md @@ -1,6 +1,6 @@ --- -title: Deep dive into Codespaces -intro: 'Understand how {% data variables.product.prodname_codespaces %} works.' +title: Aprofundamento nos codespaces +intro: 'Entender o funcionamento do {% data variables.product.prodname_codespaces %};' allowTitleToDifferFromFilename: true product: '{% data reusables.gated-features.codespaces %}' versions: @@ -10,95 +10,95 @@ topics: - Codespaces --- -{% data variables.product.prodname_codespaces %} is an instant, cloud-based development environment that uses a container to provide you with common languages, tools, and utilities for development. {% data variables.product.prodname_codespaces %} is also configurable, allowing you to create a customized development environment for your project. By configuring a custom development environment for your project, you can have a repeatable codespace configuration for all users of your project. +{% data variables.product.prodname_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 é configurável, o que permite que você crie um ambiente de desenvolvimento personalizado para o seu projeto. Ao configurar um ambiente de desenvolvimento personalizado para seu projeto, você pode ter uma configuração de código reproduzível para todos os usuários do seu projeto. ## Criando seu codespace -There are a number of entry points to create a codespace. +Há uma série de pontos de entrada para criar um codespace. -- From your repository for new feature work. -- From an open pull request to explore work-in-progress. -- From a commit in the repository's history to investigate a bug at a specific point in time. -- From {% data variables.product.prodname_vscode %}. +- Do seu repositório para um novo recurso funcionar. +- De um pull request aberto para explorar o trabalho em andamento. +- De um commit no histórico do repositório para investigar um erro em um momento específico. +- De {% data variables.product.prodname_vscode %}. -Your codespace can be ephemeral if you need to test something or you can return to the same codespace to work on long-running feature work. Para obter mais informações, consulte "[Criar um codespace](/codespaces/developing-in-codespaces/creating-a-codespace)". +Seu codespace pode ser efêmero se você tiver de fazer algum teste ou você pode retornar ao mesmo codespace para fazer um trabalho de recurso de longo prazo. Para obter mais informações, consulte "[Criar um codespace](/codespaces/developing-in-codespaces/creating-a-codespace)". -Once you've selected the option to create a new codespace, some steps happen in the background before the codespace is available to you. +Depois de selecionar a opção de criar um novo codespace, algumas etapas são executadas em segundo plano antes que o codespace esteja disponível para você. ![Botão de abrir com codespaces](/assets/images/help/codespaces/new-codespace-button.png) -### Step 1: VM and storage are assigned to your codespace +### Etapa 1: A VM e o armazenamento são atribuídos ao seu codespace -When you create a codespace, a [shallow clone](https://github.blog/2020-12-21-get-up-to-speed-with-partial-clone-and-shallow-clone/) of your repository is made on a Linux virtual machine that is both dedicated and private to you. Having a dedicated VM ensures that you have the entire set of compute resources from that machine available to you. If necessary, this also allows you to have full root access to your container. +Ao criar um codespace, cria-se [clone superficial](https://github.blog/2020-12-21-get-up-to-speed-with-partial-clone-and-shallow-clone/) do seu repositório em uma máquina virtual Linux dedicada e exclusiva para você. Ter uma VM dedicada garante que você tenha todo o conjunto de recursos de computação daquela máquina disponível para você. Se necessário, isso também permite que você tenha acesso total à raiz do seu contêiner. -### Step 2: Container is created +### Etapa 2: O contêiner foi criado -{% data variables.product.prodname_codespaces %} uses a container as the development environment. This container is created based on the configurations that you can define in a `devcontainer.json` file and/or Dockerfile in your repository. If you don't [configure a container](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project), {% data variables.product.prodname_codespaces %} uses a [default image](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project#using-the-default-configuration), which has many languages and runtimes available. For information on what the default image contains, see the [`vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers/tree/main/containers/codespaces-linux) repository. +{% data variables.product.prodname_codespaces %} usa um contêiner como ambiente de desenvolvimento. Este contêiner foi criado com base nas configurações que você pode definir em um arquivo `devcontainer.json` e/ou arquivo Docker no seu repositório. Se você não [configurar um contêiner](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project), {% data variables.product.prodname_codespaces %} usará uma [imagem padrão](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project#using-the-default-configuration), que tem muitas linguages e tempos de execução disponíveis. Para obter informações sobre o que a imagem padrão contém, consulte o repositório [`vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers/tree/main/containers/codespaces-linux). -### Step 3: Connecting to the codespace +### Etapa 3: Conectando-se ao 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. +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. -### Step 4: Post-creation setup +### Passo 4: Configuração de pós-criação -Once you're connected to your codespace, automated setup that you specified in your `devcontainer.json` file, such as running the `postCreateCommand` and `postAttachCommand`, may continue. If you have a public dotfiles repository {% 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 look for an install file. 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)". +Após estar conectado ao seu codespace, configuração automatizada que você especificou no seu arquivo `devcontainer.json` como, por exemplo, executar `postCreateCommand` e `postAttachCommand`, pode continuar. Se você tiver um repositório de dotfiles público {% 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 procurarão por um arquivo de instalação. 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)". -Finally, the entire history of the repository is copied down with a full clone. +Por fim, toda a história do repositório é copiada com um clone completo. -During post-creation setup you'll still be able to use the integrated terminal and make edits to your files, but take care to avoid any race conditions between your work and the commands that are running. -## {% data variables.product.prodname_codespaces %} lifecycle +Durante a configuração de pós-criação, você ainda poderá usar o terminal integrado e fazer edições nos seus arquivos, mas tenha cuidado para evitar quaisquer condições de corrida entre seu trabalho e os comandos que estão sendo executados. +## Ciclo de vida de {% data variables.product.prodname_codespaces %} -### Saving files in your codespace +### Salvando arquivos no seu codespace -As you develop in your codespace, it will save any changes to your files every few seconds. Your codespace will keep running for 30 minutes after the last activity. After that time it will stop running but you can restart it from either from the existing browser tab or the list of existing codespaces. File changes from the editor and terminal output are counted as activity and so your codespace will not stop if terminal output is continuing. +À medida que você desenvolve no seu codespace, ele salvará todas as alterações nos seus arquivos a cada poucos segundos. Seu codespace continuará em execução por 30 minutos após a última atividade. Depois desse tempo ele irá parar de executar, mas você poderá reiniciá-lo a partir da aba do navegador existente ou da lista de codespaces existentes. As mudanças de arquivo do editor e saída terminal são contadas como atividade. Portanto, o seu código não parará se a saída do terminal continuar. {% 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). +**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). {% endnote %} -### Closing or stopping your codespace +### Fechando ou interrompendo seu codespace -To stop your codespace you can [use the command palette](/codespaces/codespaces-reference/using-the-command-palette-in-codespaces#suspending-or-stopping-a-codespace) (`Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows)). If you exit your codespace without running the stop command (for example, closing the browser tab), or if you leave the codespace running without interaction, the codespace and its running processes will continue until a window of inactivity occurs, after which the codespace will stop. By default, the window of inactivity is 30 minutes. +Para parar seu código, você pode [usar a paleta de comandos](/codespaces/codespaces-reference/using-the-command-palette-in-codespaces#suspending-or-stopping-a-codespace) (`Shift + Comando + P` (Mac) / `Ctrl + Shift + P` (Windows)). Se você sair do seu codespace sem executar o comando de interrupção (por exemplo, fechando a aba do navegador), ou se você sair do codespace em execução sem interação, o codespace e os seus processos em execução continuarão até que ocorra uma janela de inatividade, após a qual o código será interrompido. Por padrão, a janela de inatividade é de 30 minutos. -When you close or stop your codespace, all uncommitted changes are preserved until you connect to the codespace again. +Ao fechar ou interromper o seu codespace, todas as alterações não autorizadas são preservadas até você conectar-se ao codespace novamente. -## Running your application +## Executando seu aplicativo -O redirecionamento de porta dá acesso a portas TCP que estão em execução no seu codespace. For example, if you're running a web application on port 4000 within your codespace, you can automatically forward that port to make the application accessible from your browser. +O redirecionamento de porta dá acesso a portas TCP que estão em execução no seu codespace. Por exemplo, se você estiver executando um aplicativo web na porta 4000 dentro do seu codespace, você poderá encaminhar automaticamente a porta para tornar o aplicativo acessível a partir do seu navegador. -Port forwarding determines which ports are made accessible to you from the remote machine. Even if you do not forward a port, that port is still accessible to other processes running inside the codespace itself. +O encaminhamento de portas determina quais portas podem ser acessadas por você a partir da máquina remota. Mesmo que você não encaminhe uma porta, esse porta ainda poderá ser acessada para outros processos em execução dentro do próprio codespace. -![Diagram showing how port forwarding works in a codespace](/assets/images/help/codespaces/port-forwarding.png) +![Diagrama que mostra como funciona o encaminhamento de porta em um codespace](/assets/images/help/codespaces/port-forwarding.png) -When an application running inside {% data variables.product.prodname_codespaces %} outputs a port to the console, {% data variables.product.prodname_codespaces %} detects the localhost URL pattern and automatically forwards the port. You can click on the URL in the terminal or in the toast message to open the port in a browser. For more information on port forwarding, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)." +Quando um aplicativo em execução dentro de {% data variables.product.prodname_codespaces %} produz uma porta para o console, {% data variables.product.prodname_codespaces %} detecta o padrão da URL do host local e encaminha a porta automaticamente. Você pode clicar na URL no terminal ou na mensagem de alerta para abrir a porta em um navegador. Para obter mais informações sobre o encaminhamento de portas, consulte "[Encaminhando portas no seu codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)". -While ports can be forwarded automatically, they are not publicly accessible to the internet. By default, all ports are private, but you can [manually make a port public](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace#sharing-a-port) to share access through a URL. +Embora as portas possam ser encaminhadas automaticamente, elas não podem ser acessadas pelo público na internet. Por padrão, todas as portas são privadas, mas você pode [tornar uma porta pública manualmente](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace#sharing-a-port) para compartilhar acesso por meio de uma URL. -Running your application when you first land in your codespace can make for a fast inner dev loop. As you edit, your changes are automatically saved and available on your forwarded port. To view changes, go back to the running application tab in your browser and refresh it. +A execução do seu aplicativo ao chegar pela primeira vez no seu codespace pode fazer um loop de desenvolvimento rápido interno. À medida que você edita, as alterações são salvas automaticamente e ficam disponíveis na sua porta encaminhada. Para visualizar as alterações, volte para a aba do aplicativo em execução no seu navegador e atualize-as. -## Committing and pushing your changes +## Enviando e fazendo push das suas alterações -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)" +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)" -![Running git status in Codespaces Terminal](/assets/images/help/codespaces/git-status.png) +![Executando o status do git no terminal do codespaces](/assets/images/help/codespaces/git-status.png) -You can create a codespace from any branch, commit, or pull request in your project, or you can switch to a new or existing branch from within your active codespace. Because {% data variables.product.prodname_codespaces %} is designed to be ephemeral, you can use it as an isolated environment to experiment, check a teammate's pull request, or fix merge conflicts. Você pode criar mais de um código de espaço por repositório ou até mesmo por branch. However, each user account has a limit of 10 codespaces. Se você atingiu o limite e deseja criar um novo espaço de código, você deve primeiro excluir um código. +Você pode criar um codespace a partir de qualquer branch, commit ou pull request no seu projeto, ou você pode mudar para branch novo branch ou branch existente de dentro do seu codespace ativo. Uma vez que {% data variables.product.prodname_codespaces %} foi projetado para ser efêmero, você pode usá-lo como um ambiente isolado para experimentar, verificar o pull request de um amigo de equipe ou corrigir os conflitos de merge. Você pode criar mais de um código de espaço por repositório ou até mesmo por branch. No entanto, cada conta de usuário tem um limite de 10 codespaces. Se você atingiu o limite e deseja criar um novo espaço de código, você deve primeiro excluir um código. {% note %} -**Note:** Commits from your codespace will be attributed to the name and public email configured at https://github.com/settings/profile. A token scoped to the repository, included in the environment as `GITHUB_TOKEN`, and your GitHub credentials will be used to authenticate. +**Observação:** Os commits do seu codespace serão atribuídos ao nome e ao e-mail público configurado em https://github.com/settings/profile. Um token com escopo no repositório, incluído no ambiente como `GITHUB_TOKEN`, e as suas credenciais do GitHub serão usadas para efetuar a autenticação. {% endnote %} -## Personalizing your codespace with extensions +## Personalizando seu codespace com extensões -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. +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 %}. -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. +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. ## Leia mais -- [Enabling {% data variables.product.prodname_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization) -- [Managing billing for {% data variables.product.prodname_codespaces %} in your organization](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization) -- [Setting up your project for Codespaces](/codespaces/setting-up-your-project-for-codespaces) +- [Habilitando {% data variables.product.prodname_codespaces %} para a sua organização](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization) +- [Gerenciando a cobrança para {% data variables.product.prodname_codespaces %} na sua organização](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization) +- [Configurando seu projeto para os codespaces](/codespaces/setting-up-your-project-for-codespaces) diff --git a/translations/pt-BR/content/codespaces/getting-started/quickstart.md b/translations/pt-BR/content/codespaces/getting-started/quickstart.md index 61f3ef65fb..988f231798 100644 --- a/translations/pt-BR/content/codespaces/getting-started/quickstart.md +++ b/translations/pt-BR/content/codespaces/getting-started/quickstart.md @@ -1,6 +1,6 @@ --- -title: Quickstart for Codespaces -intro: 'Try out {% data variables.product.prodname_codespaces %} in 5 minutes.' +title: Início rápido para codespaces +intro: 'Experimente {% data variables.product.prodname_codespaces %} em 5 minutos.' allowTitleToDifferFromFilename: true product: '{% data reusables.gated-features.codespaces %}' versions: @@ -14,64 +14,64 @@ redirect_from: ## Introdução -In this guide, you'll create a codespace from a [template repository](https://github.com/2percentsilk/haikus-for-codespaces) and explore some of the essential features available to you within the codespace. +Neste guia, você irá criar um codespace a partir de um [repositório modelo](https://github.com/2percentsilk/haikus-for-codespaces) e explorar algumas das funcionalidades essenciais disponíveis para você dentro do codespace. -From this quickstart, you will learn how to create a codespace, connect to a forwarded port to view your running application, use version control in a codespace, and personalize your setup with extensions. +Neste início rápido, você aprenderá a criar um codespace, conectar-se a uma porta encaminhada para ver seu aplicativo em execução, usar o controle de versões em um codespace e personalizar a sua configuração com extensões. -For more information on exactly how {% data variables.product.prodname_codespaces %} works, see the companion guide "[Deep dive into {% data variables.product.prodname_codespaces %}](/codespaces/getting-started/deep-dive)." +Para obter mais informações sobre exatamente como {% data variables.product.prodname_codespaces %} funciona, consulte o guia "[Aprofundamento em {% data variables.product.prodname_codespaces %}](/codespaces/getting-started/deep-dive)." ## Criando seu codespace -1. Navigate to the [template repository](https://github.com/2percentsilk/haikus-for-codespaces) and select **Use this template**. +1. Acesse o r[repositório do modelo](https://github.com/2percentsilk/haikus-for-codespaces) e selecione **Usar este modelo**. -2. Name your repository, select your preferred privacy setting, and click **Create repository from this template**. +2. Nomeie seu repositório, selecione sua configuração de privacidade preferida e clique em **Criar repositório a partir desse modelo**. -3. Navigate to the main page of the newly created repository. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu, and in the **Codespaces** tab, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. +3. Acesse a página principal do repositório recém-criado. No nome do repositório, use o menu suspenso **Código de {% octicon "code" aria-label="The code icon" %}** e na aba **Codespaces** de código, clique em {% octicon "plus" aria-label="The plus icon" %} **Novo codespace**. ![Botão de codespace novo](/assets/images/help/codespaces/new-codespace-button.png) -## Running the application +## Executando o aplicativo -Once your codespace is created, your repository will be automatically cloned into it. Now you can run the application and launch it in a browser. +Uma vez criado o seu codespace, seu repositório será automaticamente clonado. Agora você pode executar o aplicativo e iniciá-lo em um navegador. -1. Since this example uses a Node.js project, start the application by entering `npm run dev` in the terminal. Este comando executa o script `dev` no arquivo package.json e inicia o aplicativo web definido no repositório de exemplo. +1. Como esse exemplo usa um projeto Node.js, inicie o aplicativo digitando `npm run dev` no terminal. Este comando executa o script `dev` no arquivo package.json e inicia o aplicativo web definido no repositório de exemplo. ![npm run dev no terminal](/assets/images/help/codespaces/codespaces-npm-run-dev.png) - If you're following along with a different application type, enter the corresponding start command for that project. + Se você estiver acompanhando com um tipo diferente de aplicativo, digite o comando inicial correspondente para esse projeto. -2. When your application starts, the codespace recognizes the port the application is running on and displays a prompt to forward that port so you can connect to it. +2. Quando o aplicativo iniciar, o código reconhece a porta na qual o aplicativo está sendo executado e irá exibir uma instrução para encaminhar a porta para que você possa conectar-se a ele. ![Notificação de encaminhamento de porta](/assets/images/help/codespaces/quickstart-port-toast.png) 3. Clique em **Abrir no navegador** para visualizar seu aplicativo em execução em uma nova aba. -## Edit the application and view changes +## Edite o aplicativo e veja as alterações -1. Switch back to your codespace and open the `haikus.json` file by double-clicking it in the File Explorer. +1. Volte para o seu codespace e abra o arquivo `haikus.json` clicando duas vezes no botão no Explorador de Arquivos. -2. Edit the `text` field of the first haiku to personalize the application with your own haiku. +2. Edite o campo `de` do primeiro haiku para personalizar o aplicativo com o seu próprio haiku. -3. Go back to the running application tab in your browser and refresh to see your changes. +3. Volte à aba do aplicativo em execução no seu navegador e atualize para visualizar as suas alterações. - {% octicon "light-bulb" aria-label="The lightbulb icon" %} If you've closed the tab, open the Ports panel and click the **Open in browser** icon for the running port. - ![Port Forwarding Panel](/assets/images/help/codespaces/quickstart-forward-port.png) + {% octicon "light-bulb" aria-label="The lightbulb icon" %} Se você fechou a aba, abra o painel de portas e clique no ícone **Abrir no navegador** para a porta em execução. + ![Painel de Encaminhamento de Portas](/assets/images/help/codespaces/quickstart-forward-port.png) -## Committing and pushing your changes +## Enviando e fazendo push das suas alterações -Now that you've made a few changes, you can use the integrated terminal or the source view to commit and push the changes back to the remote. +Agora que você fez algumas alterações, você poderá usar o terminal integrado ou a visão de origem para commit e fazer push das alterações de volta para remoto. {% data reusables.codespaces.source-control-display-dark %} 1. Para testar suas alterações, clique **+** ao lado do arquivo que você alterou, ou ao lado de **Alterações** se você mudou vários arquivos e quiser testar todos. ![Barra lateral de controle de origem com botão de staging destacado](/assets/images/help/codespaces/codespaces-commit-stage.png) 1. Digite uma mensagem do commit que descreve a alteração que você fez. ![Barra lateral do controle de origem com uma mensagem de commit](/assets/images/help/codespaces/codespaces-commit-commit-message.png) 1. Para fazer commit das alterações em fase de preparação, clique na marca de seleção na parte superior da barra lateral de controle de origem. ![Click the check mark icon](/assets/images/help/codespaces/codespaces-commit-checkmark-icon.png) - You can push the changes you've made. Isso aplica essas alterações ao branch upstream no repositório remoto. Você pode querer fazer isso se ainda não estiver pronto para criar um pull request, ou se você preferir criar um pull request em {% data variables.product.prodname_dotcom %}. + Você pode fazer push das alterações realizadas. Isso aplica essas alterações ao branch upstream no repositório remoto. Você pode querer fazer isso se ainda não estiver pronto para criar um pull request, ou se você preferir criar um pull request em {% data variables.product.prodname_dotcom %}. 1. Na parte superior da barra lateral, clique na elipse (**...**). ![Botão Elipsis para visualizar e mais ações](/assets/images/help/codespaces/source-control-ellipsis-button-nochanges.png) 1. No menu suspenso, clique em **Push**. -## Personalizing with an extension +## Personalizando com uma extensão -Dentro de um codespace, você tem acesso ao Marketplace do Visual Studio Code. For this example, you'll install an extension that alters the theme, but you can install any extension that is useful for your workflow. +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. 1. Na barra lateral esquerda, clique no ícone Extensões. @@ -83,16 +83,16 @@ Dentro de um codespace, você tem acesso ao Marketplace do Visual Studio Code. F ![Selecionar tema 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. 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. ## Próximos passos Você criou com sucesso, personalizou e executou seu primeiro aplicativo em um codespace, mas há muito mais para explorar! Aqui estão alguns recursos úteis para dar seus próximos passos com {% data variables.product.prodname_codespaces %}. - - [Deep dive](/codespaces/getting-started/deep-dive): This quickstart presented some of the features of {% data variables.product.prodname_codespaces %}. The deep dive looks at these areas from a technical standpoint. - - [Setting up your project for {% data variables.product.prodname_codespaces %}](/codespaces/getting-started-with-codespaces): These guides provide information on setting up your project to use {% data variables.product.prodname_codespaces %} with specific languages - - [Configuring {% data variables.product.prodname_codespaces %} for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project): This guide provides details on creating a custom configuration for {% data variables.product.prodname_codespaces %} for your project. + - [Aprofundamento](/codespaces/getting-started/deep-dive): Este início rápido apresentou algumas das funcionalidades de {% data variables.product.prodname_codespaces %}. O guia de aprofundamento analisa estas áreas a partir de um ponto de vista técnico. + - [Configurando seu projeto para {% data variables.product.prodname_codespaces %}](/codespaces/getting-started-with-codespaces): Estes guias fornecem informações sobre a configuração do seu projeto para usar {% data variables.product.prodname_codespaces %} com linguagens específicas + - [Configurar {% data variables.product.prodname_codespaces %} para o seu projeto](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project): Este guia fornece informações sobre a criação de uma configuração personalizada para {% data variables.product.prodname_codespaces %} para o seu projeto. ## Leia mais -- [Enabling {% data variables.product.prodname_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization) -- [Managing billing for {% data variables.product.prodname_codespaces %} in your organization](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization) +- [Habilitando {% data variables.product.prodname_codespaces %} para a sua organização](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization) +- [Gerenciando a cobrança para {% data variables.product.prodname_codespaces %} na sua organização](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization) diff --git a/translations/pt-BR/content/codespaces/guides.md b/translations/pt-BR/content/codespaces/guides.md index 3295976a32..7e0260d681 100644 --- a/translations/pt-BR/content/codespaces/guides.md +++ b/translations/pt-BR/content/codespaces/guides.md @@ -2,7 +2,7 @@ title: Guias de codespaces shortTitle: Guias product: '{% data reusables.gated-features.codespaces %}' -intro: Learn how to make the most of GitHub +intro: Aprenda a aproveitar ao máximo do GitHub allowTitleToDifferFromFilename: true layout: product-sublanding versions: diff --git a/translations/pt-BR/content/codespaces/index.md b/translations/pt-BR/content/codespaces/index.md index 5fe2b80ddf..8ad498a6eb 100644 --- a/translations/pt-BR/content/codespaces/index.md +++ b/translations/pt-BR/content/codespaces/index.md @@ -41,6 +41,7 @@ children: - /managing-codespaces-for-your-organization - /codespaces-reference - /troubleshooting + - /the-githubdev-web-based-editor - /guides --- 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 58aeb60c13..22e4199e4b 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 @@ -1,6 +1,6 @@ --- -title: Enabling Codespaces for your organization -shortTitle: Enabling Codespaces +title: Habilitando codespaces para a sua organização +shortTitle: Habilitando codespaces intro: 'Você pode controlar quais usuários da sua organização podem usar {% data variables.product.prodname_codespaces %}.' product: '{% data reusables.gated-features.codespaces %}' permissions: 'To manage user permissions for {% data variables.product.prodname_codespaces %} for an organization, you must be an organization owner.' @@ -16,19 +16,19 @@ topics: --- -## About enabling {% data variables.product.prodname_codespaces %} for your organization +## Sobre habilitar {% data variables.product.prodname_codespaces %} para a sua organização Os proprietários da organização podem controlar quais usuários da sua organização podem criar e usar cdespaces. -To use codespaces in your organization, you must do the following: +Para usar codespaces na sua organização, você deve fazer o seguinte: -- Ensure that users have [at least write access](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization) to the repositories where they want to use a codespace. -- [Enable {% data variables.product.prodname_codespaces %} for users in your organization](#configuring-which-users-in-your-organization-can-use-codespaces). You can choose allow {% data variables.product.prodname_codespaces %} for selected users or only for specific users. -- [Set a spending limit](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces) +- Certifique-se de que os usuários tenham [pelo menos acesso de gravação](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization) nos repositórios onde desejam usar um codespace. +- [Habilitar {% data variables.product.prodname_codespaces %} para os usuários da sua organização](#configuring-which-users-in-your-organization-can-use-codespaces). Você pode escolher permitir {% data variables.product.prodname_codespaces %} para usuários selecionados ou apenas para usuários específicos. +- [Definir um limite de gastos](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces) -By default, a codespace can only access the repository from which it was created. Se você quiser que os codespaces na sua organização possam acessar outros repositórios da organização que o criador do codespace possa acessar, consulte "[Gerenciar acesso e segurança para {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)". +Por padrão, um codespace só pode acessar o repositório no qual ele foi criado. Se você quiser que os codespaces na sua organização possam acessar outros repositórios da organização que o criador do codespace possa acessar, consulte "[Gerenciar acesso e segurança para {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)". -## Enable {% data variables.product.prodname_codespaces %} for users in your organization +## Habilitar {% data variables.product.prodname_codespaces %} para os usuários na sua organização {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} @@ -40,14 +40,14 @@ By default, a codespace can only access the repository from which it was created ![Botões de opção para "Permissões do usuário"](/assets/images/help/codespaces/organization-user-permission-settings.png) -## Disabling {% data variables.product.prodname_codespaces %} for your organization +## Desabilitando {% data variables.product.prodname_codespaces %} para sua organização {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.click-codespaces %} -1. Under "User permissions", select **Disabled**. +1. Em "Permissões de usuário", selecione **Desabilitado**. -## Setting a spending limit +## Definindo um limite de gastos {% data reusables.codespaces.codespaces-spending-limit-requirement %} diff --git a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/index.md b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/index.md index 0fe4cc7756..d209cf92b3 100644 --- a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/index.md +++ b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/index.md @@ -12,6 +12,6 @@ children: - /managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces - /managing-repository-access-for-your-organizations-codespaces - /reviewing-your-organizations-audit-logs-for-codespaces -shortTitle: Managing your organization +shortTitle: Gerenciando sua organização --- 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 9b3da3c85e..18277ddf71 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 @@ -1,7 +1,7 @@ --- -title: Managing billing for Codespaces in your organization -shortTitle: Managing billing for Codespaces -intro: 'You can check your {% data variables.product.prodname_codespaces %} usage and set usage limits.' +title: Gerenciar a cobrança de codespaces na sua organização +shortTitle: Gerenciamento de cobrança para codespaces +intro: 'Você pode verificar seu uso de {% data variables.product.prodname_codespaces %} e definir os limites de uso.' product: '{% data reusables.gated-features.codespaces %}' permissions: 'To manage billing for Codespaces for an organization, you must be an organization owner or a billing manager.' versions: @@ -14,31 +14,31 @@ topics: ## Visão Geral -To learn about pricing for {% data variables.product.prodname_codespaces %}, see "[{% data variables.product.prodname_codespaces %} pricing](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)." +Para saber mais sobre os preços para {% data variables.product.prodname_codespaces %}, consulte "[Preços de {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)". {% data reusables.codespaces.codespaces-billing %} -- As an an organization owner or a billing manager you can manage {% data variables.product.prodname_codespaces %} billing for your organization: ["About billing for Codespaces"](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces) +- Como proprietário de uma organização ou gerente de cobrança, você pode gerenciar a cobrança de {% data variables.product.prodname_codespaces %} para a sua organização: ["Sobre cobrança para codespaces"](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces) -- For users, there is a guide that explains how billing works: ["Understanding billing for Codespaces"](/codespaces/codespaces-reference/understanding-billing-for-codespaces) +- Para os usuários, há um guia que explica como a cobrança funciona: ["Entendendo a cobrança para codespace"](/codespaces/codespaces-reference/understanding-billing-for-codespaces) ## Limites de uso -You can set a usage limit for the codespaces in your organization or repository. This limit is applied to the compute and storage usage for {% data variables.product.prodname_codespaces %}: +Você pode definir um limite de uso para os codespaces na sua organização ou repositório. Este limite é aplicado ao uso de computação e armazenamento para {% data variables.product.prodname_codespaces %}: -- **Compute minutes:** Compute usage is calculated by the actual number of minutes used by all {% data variables.product.prodname_codespaces %} instances while they are active. These totals are reported to the billing service daily, and is billed monthly. You can set a spending limit for {% data variables.product.prodname_codespaces %} usage in your organization. For more information, see "[Managing spending limits for Codespaces](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)." +- **Minutos de cálculo:** Uso do cálculo é feito pelo número real de minutos usados por todas as instâncias de {% data variables.product.prodname_codespaces %} enquanto estão ativas. Estes montantes totais são comunicados diariamente ao serviço de cobrança e são cobrados mensalmente. Você pode definir um limite de gastos para uso de {% data variables.product.prodname_codespaces %} na sua organização. Para obter mais informações, consulte "[Gerenciando limites de gastos para os codespaces](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)". -- **Storage usage:** For {% data variables.product.prodname_codespaces %} billing purposes, this includes all storage used by all codespaces in your account. This includes all used by the codespaces, such as cloned repositories, configuration files, and extensions, among others. These totals are reported to the billing service daily, and is billed monthly. No final do mês, {% data variables.product.prodname_dotcom %} arredonda seu armazenamento para o MB mais próximo. To check how many compute minutes and storage GB have been used by {% data variables.product.prodname_codespaces %}, see "[Viewing your Codespaces usage"](/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage)." +- **Uso do armazenamento:** Para fins de cobrança de {% data variables.product.prodname_codespaces %}, isto inclui todo o armazenamento usado por todos os codespaces da sua conta. Isto inclui todos os codespacess usados pelos repositórios clonados, arquivos de configuração e extensões, entre outros. Estes montantes totais são comunicados diariamente ao serviço de cobrança e são cobrados mensalmente. No final do mês, {% data variables.product.prodname_dotcom %} arredonda seu armazenamento para o MB mais próximo. Para verificar quantos minutos de computação e armazenamento em GB foram usados por {% data variables.product.prodname_codespaces %}, consulte "[Visualizando o uso dos seus codespaces"](/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage)." -## Disabling or limiting {% data variables.product.prodname_codespaces %} +## Desabilitando ou limitando {% data variables.product.prodname_codespaces %} -You can disable the use of {% data variables.product.prodname_codespaces %} in your organization or repository. For more information, see "[Managing repository access for your organization's codespaces](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)." +É possível desabilitar o uso de {% data variables.product.prodname_codespaces %} na sua organização ou repositório. Para obter mais informações, consulte "[Gerenciar acesso ao repositório para os codespaces da sua organização](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces)". -You can also limit the individual users who can use {% data variables.product.prodname_codespaces %}. For more information, see "[Managing user permissions for your organization](/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization)." +Você também pode limitar os usuários individuais que podem usar {% data variables.product.prodname_codespaces %}. Para obter mais informações, consulte "[Gerenciando permissões de usuário para sua organização](/codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization)". -## Deleting unused codespaces +## Excluindo codespaces não utilizados -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. +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. {% note %} diff --git a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md index 15a1d9bd6e..bbbf8baec8 100644 --- a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md +++ b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md @@ -72,3 +72,7 @@ Você pode verificar quais políticas de acesso são aplicadas a um segredo na s {% data reusables.github-actions.sidebar-secret %} 1. A lista de segredos inclui quaisquer permissões e políticas configuradas. Por exemplo: ![Lista de segredos](/assets/images/help/settings/actions-org-secrets-list.png) 1. Para obter mais detalhes sobre as permissões configuradas para cada segredo, clique em **Atualizar**. + +## Leia mais + +- "[Gerenciar segredos criptografados nos seus codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)" diff --git a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md index 9c9f178214..d8cb520783 100644 --- a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md +++ b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md @@ -1,6 +1,6 @@ --- -title: Managing repository access for your organization's codespaces -shortTitle: Repository access +title: Gerenciando o acesso ao repositório para os codespaces da sua organização +shortTitle: Acesso ao repositório intro: 'Você pode gerenciar os repositórios na sua organização que {% data variables.product.prodname_codespaces %} pode acessar.' product: '{% data reusables.gated-features.codespaces %}' permissions: 'To manage access and security for Codespaces for an organization, you must be an organization owner.' @@ -26,3 +26,7 @@ Para gerenciar quais usuários na sua organização podem usar {% data variables {% data reusables.organizations.click-codespaces %} 1. Em "Acesso e segurança", selecione a configuração que você deseja para a sua organização. ![Botões de opção para gerenciar repositórios confiáveis](/assets/images/help/settings/codespaces-org-access-and-security-radio-buttons.png) 1. Se você escolheu "repositórios selecionados", selecione o menu suspenso e, em seguida, clique em um repositório para permitir que os codespaces do repositório acessem outros repositórios pertencentes à sua organização. Repita isso para todos os repositórios cujos códigos você deseja que acessem outros repositórios. ![Menu suspenso "Repositórios selecionados"](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) + +## Leia mais + +- "[Gerenciando acesso ao repositório para seus codespaces](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces)" diff --git a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md index ec9ce6cd2a..b6547377d1 100644 --- a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md +++ b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md @@ -19,3 +19,7 @@ Quando qualquer integrante da sua organização executa uma ação relacionada a ![Log de auditoria com informações sobre codespaces](/assets/images/help/settings/codespaces-audit-log-org.png) O log de auditoria inclui detalhes como quem realizou a ação, qual foi a ação e quando a ação foi realizada. Para obter informações sobre ações de {% data variables.product.prodname_codespaces %}, consulte "[ações de categoria de {% data variables.product.prodname_codespaces %}](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#codespaces-category-actions)." + +## Leia mais + +- "[Revisando seus logs de segurança para {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces)" diff --git a/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md b/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md index 58492fa2e0..2e178718a1 100644 --- a/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md +++ b/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md @@ -73,3 +73,7 @@ Você pode atualizar o valor de um segredo existente, bem como alterar quais rep {% data reusables.user_settings.codespaces-tab %} 1. Em "Segredos dos codespaces", à direita do segredo que você deseja excluir, clique em **Excluir**. ![Botão "Excluir"](/assets/images/help/settings/codespaces-secret-delete-button.png) 1. Leia o alerta e clique em **OK**. ![Confirmação para excluir um segredo](/assets/images/help/settings/codespaces-secret-delete-warning.png) + +## Leia mais + +- "[Gerenciando segredos criptografados para o seu repositório e organização para {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces)" diff --git a/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md b/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md index 12f8b540aa..faa5f86d9a 100644 --- a/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md +++ b/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md @@ -19,7 +19,7 @@ shortTitle: Verificação de GPG Depois que você habilitar a verificação do GPG, {% data variables.product.company_short %} assinará automaticamente os commits que você fizer em {% data variables.product.prodname_codespaces %}, e os commits terão um status de verificado em {% data variables.product.product_name %}. Por padrão, a verificação do GPG está desabilitada para os codespaces que você criar. Você pode optar por permitir a verificação do GPG para todos os repositórios ou repositórios específicos. Habilite apenas a verificação do GPG para repositórios nos quais você confia. Para obter mais informações sobre commits assinado por {% data variables.product.product_name %}, consulte "[Sobre a verificação de assinatura do commit](/github/authenticating-to-github/about-commit-signature-verification)". -Once you enable GPG verification, it will immediately take effect for all your codespaces. +Assim que você habilitar a verificação GPG, ela entrará em vigor para todos os seus codespaces. {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.codespaces-tab %} @@ -29,6 +29,6 @@ Once you enable GPG verification, it will immediately take effect for all your c {% note %} -**Note:** Once you have enabled GPG verification for {% data variables.product.prodname_codespaces %}, you also must append `-s` to each commit in order for it to be signed. To do this in {% data variables.product.prodname_vscode %}, ensure the "Git: Enable Commit Signing" option is enabled from the Settings. +**Observação:** Depois de habilitar a verificação GPG para {% data variables.product.prodname_codespaces %}, você também deverá adicionar `-S` a cada commit para que seja assinado. Para fazer isso em {% data variables.product.prodname_vscode %}, verifique se a opção "Git: Habilitar a assinatura do commit" está habilitada nas Configurações. {% endnote %} 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 c6a0fd1d9b..7f8330d67d 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 @@ -1,6 +1,6 @@ --- -title: Managing repository access for your codespaces -shortTitle: Repository access +title: Gerenciando acesso ao repositório para seus codespaces +shortTitle: Acesso ao repositório intro: 'Você pode gerenciar os repositórios que {% data variables.product.prodname_codespaces %} pode acessar.' product: '{% data reusables.gated-features.codespaces %}' versions: @@ -20,3 +20,7 @@ Ao habilitar o acesso e a segurança de um repositório pertencente à sua conta {% data reusables.user_settings.codespaces-tab %} 1. Em "Acesso e segurança", selecione a configuração que deseja para sua conta de usuário. ![Botões de opção para gerenciar repositórios confiáveis](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png) 1. Se você escolher "repositórios selecionados", selecione o menu suspenso e clique em um repositório para permitir que os codespaces do repositório tenham acesso a outros repositórios dos quais você é proprietário. Repita para todos os repositórios cujos codespaces você deseja que acessem outros repositórios dos quais você é proprietário. ![Menu suspenso "Repositórios selecionados"](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) + +## Leia mais + +- "[Gerenciando o acesso ao repositório para os codespaces da sua organização](/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces)" diff --git a/translations/pt-BR/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md b/translations/pt-BR/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md index 7b1e1bea66..1806556dc3 100644 --- a/translations/pt-BR/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md +++ b/translations/pt-BR/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md @@ -1,6 +1,6 @@ --- title: Revisando os logs de segurança dos codespaces -shortTitle: Security logs +shortTitle: Logs de segurança intro: 'Você pode usar o log de segurança para revisar todas as ações relacionadas a {% data variables.product.prodname_codespaces %}.' product: '{% data reusables.gated-features.codespaces %}' versions: @@ -20,3 +20,7 @@ Quando você executar uma ação relacionada a {% data variables.product.prodnam ![log de segurança com informações de codespaces](/assets/images/help/settings/codespaces-audit-log.png) O log de segurança inclui detalhes sobre a ação que ocorreu e quando você aexecutou. Para obter informações sobre ações de {% data variables.product.prodname_codespaces %}, consulte "[ações de categoria de {% data variables.product.prodname_codespaces %}](/github/authenticating-to-github/reviewing-your-security-log#codespaces-category-actions)". + +## Leia mais + +- "[Revisando os logs de auditoria da sua organização para {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces)" diff --git a/translations/pt-BR/content/codespaces/managing-your-codespaces/setting-your-default-editor-for-codespaces.md b/translations/pt-BR/content/codespaces/managing-your-codespaces/setting-your-default-editor-for-codespaces.md index d0c324a463..58273919b5 100644 --- a/translations/pt-BR/content/codespaces/managing-your-codespaces/setting-your-default-editor-for-codespaces.md +++ b/translations/pt-BR/content/codespaces/managing-your-codespaces/setting-your-default-editor-for-codespaces.md @@ -1,20 +1,20 @@ --- -title: Setting your default editor for Codespaces -intro: 'You can set your default editor for {% data variables.product.prodname_codespaces %} in your personal settings page.' +title: Definindo seu editor padrão para os codespaces +intro: 'Você pode definir seu editor padrão para {% data variables.product.prodname_codespaces %} na sua página de configurações pessoais.' product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' topics: - Codespaces -shortTitle: Set the default editor +shortTitle: Definir o editor padrão --- -On the settings page, you can set your editor preference so that any newly created codespaces are opened automatically in either {% data variables.product.prodname_vscode %} for Web or the {% data variables.product.prodname_vscode %} desktop application. +Na página de configurações você pode definir sua preferência de editor para que todos os codespaces sejam abertos automaticamente em {% data variables.product.prodname_vscode %} para a web ou em {% data variables.product.prodname_vscode %} para aplicativos de desktop. -If you want to use {% data variables.product.prodname_vscode %} as your default editor for {% data variables.product.prodname_codespaces %}, you need to install {% data variables.product.prodname_vscode %} and the {% data variables.product.prodname_github_codespaces %} extension for {% data variables.product.prodname_vscode %}. For more information, see the [download page for {% data variables.product.prodname_vscode %}](https://code.visualstudio.com/download/) and the [{% data variables.product.prodname_github_codespaces %} extension on the {% data variables.product.prodname_vscode %} marketplace](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces). +Se você quiser usar {% data variables.product.prodname_vscode %} como seu editor padrão para {% data variables.product.prodname_codespaces %}, você deverá instalar {% data variables.product.prodname_vscode %} e a extensão de {% data variables.product.prodname_github_codespaces %} para {% data variables.product.prodname_vscode %}. Para obter mais informações, consulte a página de download de [para {% data variables.product.prodname_vscode %}](https://code.visualstudio.com/download/) e a extensão de [{% data variables.product.prodname_github_codespaces %} no marketplace de {% data variables.product.prodname_vscode %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces). -## Setting your default editor +## Configurando o seu editor padrão {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.codespaces-tab %} -1. Under "Editor preference", select the option you want. ![Setting your editor](/assets/images/help/codespaces/select-default-editor.png) If you choose **{% data variables.product.prodname_vscode %}**, {% data variables.product.prodname_codespaces %} will automatically open in the desktop application when you next create a codespace. You may need to allow access to both your browser and {% data variables.product.prodname_vscode %} for it to open successfully. ![Setting your editor](/assets/images/help/codespaces/launch-default-editor.png) +1. Em "Editor de preferência", selecione a opção que você desejar. ![Setting your editor](/assets/images/help/codespaces/select-default-editor.png) Se você escolher **{% data variables.product.prodname_vscode %}**, {% data variables.product.prodname_codespaces %} será automaticamente aberto no aplicativo da área de trabalho na próxima vez que você criar um codespace. Talvez seja necessário permitir o acesso ao seu navegador e ao {% data variables.product.prodname_vscode %} para que seja aberto com sucesso. ![Configurando seu editor](/assets/images/help/codespaces/launch-default-editor.png) diff --git a/translations/pt-BR/content/codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces.md b/translations/pt-BR/content/codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces.md index 9b00a4f227..752dec4ad5 100644 --- a/translations/pt-BR/content/codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces.md +++ b/translations/pt-BR/content/codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces.md @@ -1,19 +1,19 @@ --- -title: Setting your default region for Codespaces -intro: 'You can set your default region in the {% data variables.product.prodname_github_codespaces %} profile settings page to personalize where your data is held.' +title: Definindo sua região padrão para os codespaces +intro: 'Você pode definir sua região padrão na página de configurações do perfil de {% data variables.product.prodname_github_codespaces %} para personalizar o local onde seus dados são mantidos.' product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' topics: - Codespaces -shortTitle: Set the default region +shortTitle: Definir a região padrão --- -You can manually select the region that your codespaces will be created in, allowing you to meet stringent security and compliance requirements. By default, your region is set automatically, based on your location. +Você pode selecionar manualmente a região em que os seus codespaces serão criados, permitindo que você atenda aos requisitos rigorosos de segurança e conformidade. Por padrão, a sua região é definida automaticamente com base na sua localização. -## Setting your default region +## Definindo sua região padrão {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.codespaces-tab %} -1. Under "Region", select the setting you want. -2. If you chose "Set manually", select your region in the drop-down list. ![Selecting your region](/assets/images/help/codespaces/select-default-region.png) +1. Em "Região", selecione a configuração desejada. +2. Se você escolheu "Definir manualmente", selecione sua região na lista suspensa. ![Selecionando sua região](/assets/images/help/codespaces/select-default-region.png) diff --git a/translations/pt-BR/content/codespaces/overview.md b/translations/pt-BR/content/codespaces/overview.md index 864393d57b..9d1439cbcb 100644 --- a/translations/pt-BR/content/codespaces/overview.md +++ b/translations/pt-BR/content/codespaces/overview.md @@ -1,8 +1,8 @@ --- -title: GitHub Codespaces overview +title: Visão geral do GitHub Codespaces shortTitle: Visão Geral product: '{% data reusables.gated-features.codespaces %}' -intro: 'This guide introduces {% data variables.product.prodname_codespaces %} and provides details on how it works and how to use it.' +intro: 'Este guia apresenta {% data variables.product.prodname_codespaces %} e fornece informações sobre como ele funciona e como usá-lo.' allowTitleToDifferFromFilename: true redirect_from: - /codespaces/codespaces-reference/about-codespaces @@ -17,26 +17,26 @@ topics: - Codespaces --- -## What is a codespace? +## O que é um codespace? -A codespace is a development environment that's hosted in the cloud. You can customize your project for {% data variables.product.prodname_codespaces %} by committing [configuration files](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project) to your repository (often known as Configuration-as-Code), which creates a repeatable codespace configuration for all users of your project. +Um codespace é um ambiente de desenvolvimento hospedado na nuvem. Você pode personalizar o seu projeto para {% data variables.product.prodname_codespaces %}, fazendo commit de [arquivos de configuração](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project) para o seu repositório (geralmente conhecido como configuração como código), que cria uma configuração de código reproduzível para todos os usuários do seu projeto. -{% data variables.product.prodname_codespaces %} run on a variety of VM-based compute options hosted by {% data variables.product.product_location %}, which you can configure from 2 core machines up to 32 core machines. You can connect to your codespaces from the browser or locally using {% data variables.product.prodname_vscode %}. +{% data variables.product.prodname_codespaces %} é executado em uma série de opções de computação baseadas em VM, hospedadas por {% data variables.product.product_location %}, que você pode configurar a partir de 2 a 32 máquinas centrais. Você pode conectar-se aos seus codespaces a partir do navegador ou localmente usando o {% data variables.product.prodname_vscode %}. -![A diagram showing how {% data variables.product.prodname_codespaces %} works](/assets/images/help/codespaces/codespaces-diagram.png) +![Um diagrama que mostra como {% data variables.product.prodname_codespaces %} funciona](/assets/images/help/codespaces/codespaces-diagram.png) -## Using Codespaces +## Usando codespaces -You can create a codespace from any branch or commit in your repository and begin developing using cloud-based compute resources. +Você pode criar um codespace a partir de qualquer branch ou commit no seu repositório e começar a desenvolver usando recursos de computação baseados na nuvem. -To customize the runtimes and tools in your codespace, you can create a custom configuration to define an environment (or _dev container_) that is specific for your repository. Using a dev container allows you to specify a Docker environment for development with a well-defined tool and runtime stack that can reference an image, Dockerfile, or docker-compose. This means that anyone using the repository will have the same tools available to them when they create a codespace. +Para personalizar os tempos de execução e ferramentas no seu codespace, você pode criar uma configuração personalizada para definir um ambiente (ou _contêiner dev_) que seja específico para o seu repositório. Usar um contêiner dev permite que você especifique um ambiente Docker para desenvolvimento com uma ferramenta bem definida de ferramenta e tempo de execução que pode fazer referência a uma imagem, arquivo Docker ou docker-compose. Isso significa que qualquer pessoa que estiver usando o repositório terá as mesmas ferramentas disponíveis ao criar o codespace. -If you don't do any custom 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 "[Configuring Codespaces for your project](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". +Se não definir nenhuma configuração personalizada, o {% data variables.product.prodname_codespaces %} clonará seu repositório em um ambiente com a imagem de codespace padrão que inclui muitas ferramentas, linguagens e ambientes de execução. Para obter mais informações, consulte "[Configurando codespaces para o seu projeto](/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)". +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)". ## Sobre a cobrança do {% data variables.product.prodname_codespaces %} -For information on billing for {% data variables.product.prodname_codespaces %}, see "[Managing billing for {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces)." +Para informações sobre faturamento para {% data variables.product.prodname_codespaces %}, consulte "[Gerenciar cobrança para {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces)". -{% data reusables.codespaces.codespaces-spending-limit-requirement %} For information on how organizations owners and billing managers can manage the spending limit for {% data variables.product.prodname_codespaces %} for an organization, see "[Managing your spending limit for {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)." +{% data reusables.codespaces.codespaces-spending-limit-requirement %} Para informações sobre como as organizações proprietários e gerentes de cobrança podem gerenciar o limite de gastos de {% data variables.product.prodname_codespaces %} para uma organização, consulte "[Gerenciar o seu limite de gastos para {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)". diff --git a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/index.md b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/index.md index 519b5550c5..34262b24a4 100644 --- a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/index.md +++ b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/index.md @@ -1,5 +1,5 @@ --- -title: 'Setting up your project for {% data variables.product.prodname_codespaces %}' +title: 'Configurando seu projeto para {% data variables.product.prodname_codespaces %}' intro: 'Aprenda como dar os primeiros passos com {% data variables.product.prodname_codespaces %}, incluindo a configuração para linguagens específicas.' product: '{% data reusables.gated-features.codespaces %}' versions: diff --git a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md index 19450ee42a..490cf33b71 100644 --- a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md +++ b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md @@ -1,6 +1,6 @@ --- -title: Setting up your C# (.NET) project for Codespaces -shortTitle: Setting up your C# (.NET) project +title: Configurando seu projeto C# (.NET) para os codespaces +shortTitle: Configurando seu projeto C# (.NET) allowTitleToDifferFromFilename: true product: '{% data reusables.gated-features.codespaces %}' intro: 'Primeiros passos com o seu projeto C# (.NET) em {% data variables.product.prodname_codespaces %} criando um contêiner de desenvolvimento personalizado.' @@ -25,11 +25,11 @@ Este guia mostra como configurar seu projeto C# (.NET) em {% data variables.prod ## Etapa 1: Abra o seu projeto em um codespace -1. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu, and in the **Codespaces** tab, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. +1. No nome do repositório, use o menu suspenso **Código de {% octicon "code" aria-label="The code icon" %}** e na aba **Codespaces** de código, clique em {% octicon "plus" aria-label="The plus icon" %} **Novo codespace**. ![Botão de codespace novo](/assets/images/help/codespaces/new-codespace-button.png) - If you don’t see this option, {% data variables.product.prodname_codespaces %} isn't available for your project. See [Access to {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) for more information. + Se você não vir esta opção, significa que {% data variables.product.prodname_codespaces %} não está disponível para o seu projeto. Consulte [Acesso a {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) para mais informações. Ao criar um código, seu projeto será criado em uma VM remota dedicada a você. Por padrão, o contêiner para o seu codespace têm várias linguagens e tempos de execução, incluindo .NET. Ele também inclui um conjunto comum de ferramentas, como git, wget, rsync, openssh e nano. @@ -168,7 +168,7 @@ Com o seu contêiner de desenvolvimento adicionado e um entendimento básico do 1. No Explorador, expanda a pasta `.devcontainer` e selecione o arquivo `devcontainer.json` a partir da árvore para abri-lo. - ![devcontainer.json file in the Explorer](/assets/images/help/codespaces/devcontainers-options.png) + ![Arquivo devcontainer.json no Explorador](/assets/images/help/codespaces/devcontainers-options.png) 2. Atualize a sua lista de `extensões` no seu arquivo `devcontainer.json` para adicionar algumas extensões úteis ao trabalhar com o seu projeto. diff --git a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md index a256c22993..5e2eae34e4 100644 --- a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md +++ b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md @@ -1,6 +1,6 @@ --- -title: Setting up your Java project for Codespaces -shortTitle: Setting up with your Java project +title: Configurando seu projeto Java para Codespaces +shortTitle: Configurando com seu projeto Java intro: 'Dê os primeiros passos com o seu projeto Java em {% data variables.product.prodname_codespaces %} criando um contêiner de desenvolvimento personalizado.' product: '{% data reusables.gated-features.codespaces %}' redirect_from: @@ -24,11 +24,11 @@ Este guia mostra como configurar seu projeto Java em {% data variables.product.p ## Etapa 1: Abra o seu projeto em um codespace -1. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu, and in the **Codespaces** tab, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. +1. No nome do repositório, use o menu suspenso **Código de {% octicon "code" aria-label="The code icon" %}** e na aba **Codespaces** de código, clique em {% octicon "plus" aria-label="The plus icon" %} **Novo codespace**. ![Botão de codespace novo](/assets/images/help/codespaces/new-codespace-button.png) - If you don’t see this option, {% data variables.product.prodname_codespaces %} isn't available for your project. See [Access to {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) for more information. + Se você não vir esta opção, significa que {% data variables.product.prodname_codespaces %} não está disponível para o seu projeto. Consulte [Acesso a {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) para mais informações. Ao criar um código, seu projeto será criado em uma VM remota dedicada a você. Por padrão, o contêiner do seu código possui muitas linguagens e tempos de execução, incluindo Java, nvm, npm e yarn. Ele também inclui um conjunto comum de ferramentas, como git, wget, rsync, openssh e nano. @@ -150,7 +150,7 @@ Com o seu contêiner de desenvolvimento adicionado e um entendimento básico do 1. No Explorer, selecione o arquivo `devcontainer.json` a partir da árvore para abri-lo. Você pode ter que expandir a pasta `.devcontainer` para vê-la. - ![devcontainer.json file in the Explorer](/assets/images/help/codespaces/devcontainers-options.png) + ![Arquivo devcontainer.json no Explorador](/assets/images/help/codespaces/devcontainers-options.png) 2. Adicione as seguintes linhas ao seu arquivo `devcontainer.json` após as `extensões`. diff --git a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md index b307c97f36..59149984ee 100644 --- a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md +++ b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md @@ -1,6 +1,6 @@ --- -title: Setting up your Node.js project for Codespaces -shortTitle: Setting up your Node.js project +title: Configurando seu projeto Node.js para Codespaces +shortTitle: Configurando seu projeto Node.js intro: 'Comece com seu projeto JavaScript, Node.js ou TypeScript em {% data variables.product.prodname_codespaces %} criando um contêiner de desenvolvimento personalizado.' product: '{% data reusables.gated-features.codespaces %}' versions: @@ -28,11 +28,11 @@ Este guia mostra como configurar seu projeto JavaScript, Node.js ou TypeScript e ## Etapa 1: Abra o seu projeto em um codespace -1. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu, and in the **Codespaces** tab, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. +1. No nome do repositório, use o menu suspenso **Código de {% octicon "code" aria-label="The code icon" %}** e na aba **Codespaces** de código, clique em {% octicon "plus" aria-label="The plus icon" %} **Novo codespace**. ![Botão de codespace novo](/assets/images/help/codespaces/new-codespace-button.png) - If you don’t see this option, {% data variables.product.prodname_codespaces %} isn't available for your project. See [Access to {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) for more information. + Se você não vir esta opção, significa que {% data variables.product.prodname_codespaces %} não está disponível para o seu projeto. Consulte [Acesso a {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) para mais informações. Ao criar um código, seu projeto será criado em uma VM remota dedicada a você. Por padrão, o contêiner para o seu código possui muitas linguagens e tempos de execução, incluindo Node.js, JavaScript, Typescript, nvm, npm e yarn. Ele também inclui um conjunto comum de ferramentas, como git, wget, rsync, openssh e nano. @@ -135,7 +135,7 @@ Com o seu contêiner de desenvolvimento adicionado e um entendimento básico do 1. No Explorer, selecione o arquivo `devcontainer.json` a partir da árvore para abri-lo. Você pode ter que expandir a pasta `.devcontainer` para vê-la. - ![devcontainer.json file in the Explorer](/assets/images/help/codespaces/devcontainers-options.png) + ![Arquivo devcontainer.json no Explorador](/assets/images/help/codespaces/devcontainers-options.png) 2. Adicione as seguintes linhas ao seu arquivo `devcontainer.json` após as `extensões`: diff --git a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md index 7fb9ffe8e7..fb121a656b 100644 --- a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md +++ b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md @@ -1,6 +1,6 @@ --- -title: Setting up your Python project for Codespaces -shortTitle: Setting up your Python project +title: Configurando seu projeto em Python para Codespaces +shortTitle: Configurando seu projeto Python intro: 'Dê os primeiros passos com seu projeto Python em {% data variables.product.prodname_codespaces %} criando um contêiner de desenvolvimento personalizado.' product: '{% data reusables.gated-features.codespaces %}' versions: @@ -27,11 +27,11 @@ Este guia mostra como configurar seu projeto Python em {% data variables.product ## Etapa 1: Abra o seu projeto em um codespace -1. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** drop-down menu, and in the **Codespaces** tab, click {% octicon "plus" aria-label="The plus icon" %} **New codespace**. +1. No nome do repositório, use o menu suspenso **Código de {% octicon "code" aria-label="The code icon" %}** e na aba **Codespaces** de código, clique em {% octicon "plus" aria-label="The plus icon" %} **Novo codespace**. ![Botão de codespace novo](/assets/images/help/codespaces/new-codespace-button.png) - If you don’t see this option, {% data variables.product.prodname_codespaces %} isn't available for your project. See [Access to {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) for more information. + Se você não vir esta opção, significa que {% data variables.product.prodname_codespaces %} não está disponível para o seu projeto. Consulte [Acesso a {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces) para mais informações. @@ -160,7 +160,7 @@ Com o seu contêiner de desenvolvimento adicionado e um entendimento básico do 1. No Explorador, expanda a pasta `.devcontainer` e selecione o arquivo `devcontainer.json` a partir da árvore para abri-lo. - ![devcontainer.json file in the Explorer](/assets/images/help/codespaces/devcontainers-options.png) + ![Arquivo devcontainer.json no Explorador](/assets/images/help/codespaces/devcontainers-options.png) 2. Atualize a lista de extensões `` no seu arquivo `devcontainer.json` para adicionar algumas extensões que são úteis ao trabalhar com seu projeto. 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 new file mode 100644 index 0000000000..f3bce2d560 --- /dev/null +++ b/translations/pt-BR/content/codespaces/the-githubdev-web-based-editor.md @@ -0,0 +1,106 @@ +--- +title: O editor github.dev baseado na web +intro: 'Use o github.dev {% data variables.product.prodname_serverless %} do seu repositório ou pull request para criar e fazer commit das alterações.' +versions: + fpt: '*' +type: how_to +miniTocMaxHeadingLevel: 3 +topics: + - Codespaces + - Visual Studio Code + - Developer +shortTitle: Editor baseado na web +redirect_from: + - /codespaces/developing-in-codespaces/web-based-editor +--- + +{% note %} + +**Observação:** O github.dev {% data variables.product.prodname_serverless %} está atualmente em visualização beta. Você pode fornecer feedback [nas nossas discussões](https://github.co/browser-editor-feedback). + +{% endnote %} + +## Sobre o {% data variables.product.prodname_serverless %} + +O {% data variables.product.prodname_serverless %} introduz uma experiência leve de edição, que é executada inteiramente no seu navegador. Com o {% data variables.product.prodname_serverless %}, você pode navegar por arquivos e repositórios de código-fonte do {% data variables.product.prodname_dotcom %}, bem como efetuar e fazer comite das alterações de código. É possível abrir qualquer repositório, bifurcação ou pull request no editor. + +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 %} é 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. + +## Abrindo o {% data variables.product.prodname_serverless %} + +Você pode abrir qualquer repositório de {% data variables.product.prodname_dotcom %} em {% data variables.product.prodname_serverless %} em qualquer uma das seguintes maneiras: + +- Pressione `.` enquanto navega em qualquer repositório ou pull request no {% data variables.product.prodname_dotcom %}. +- Alterando a URL de "github.com" para "github.dev". + +## {% data variables.product.prodname_codespaces %} e {% data variables.product.prodname_serverless %} + +Tanto o {% data variables.product.prodname_serverless %} quanto o {% data variables.product.prodname_codespaces %} permitem que você edite seu código diretamente do seu repositório. No entanto, ambos têm benefícios ligeiramente diferentes, dependendo da sua utilização. + +| | {% data variables.product.prodname_serverless %} | {% data variables.product.prodname_codespaces %} +| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| **Custo** | Grátis. | Custos de computação e armazenamento. Para obter informações sobre os preços, consulte "[Preços de codespaces](/en/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)" | +| **Disponibilidade** | Disponível para todos no GitHub.com. | Disponível para organizações que usam o GitHub Team ou GitHub Enterprise Cloud. | +| **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. | + +### Continue trabalhando em {% data variables.product.prodname_codespaces %} + +Você pode iniciar seu fluxo de trabalho em {% data variables.product.prodname_serverless %} e continuar trabalhando em um codespace, desde que você tenha [acesso a {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces). Se você tentar acessar a janela ou terminal Executar e Depurarl, você receberá uma mensagem de que eles não estão disponíveis em {% data variables.product.prodname_serverless %}. + +Para continuar seu trabalho em um codespace, clique em **Continuar trabalho em…** e selecione **Criar novo codespace** para criar um codespace no seu branch atual. Antes de selecionar esta opção, você precisa fazer commit de quaisquer alterações. + +![Uma captura de tela que mostra o botão "Continuar trabalhando em" na interface do usuário](/assets/images/help/codespaces/codespaces-continue-working.png) + +## 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 %}. + +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 %}. + +### Criar um branch + +{% data reusables.codespaces.create-or-switch-branch %} + Todas as alterações sem commit feitas no seu branch antigo estarão disponíveis no seu novo branch. + +### Faça commit das suas alterações + +{% data reusables.codespaces.source-control-commit-changes %} +5. Depois de ter feito as commit das suas alterações, elas serão automaticamente enviadas para o seu branch em {% data variables.product.prodname_dotcom %}. +### Criar um pull request + +{% data reusables.codespaces.source-control-pull-request %} + +### Trabalhando com um pull request existente + +Você pode usar o {% data variables.product.prodname_serverless %} para trabalhar com um pull request existente. + +1. Acesse o pull request que você gostaria de abrir em {% data variables.product.prodname_serverless %}. +2. Pressione `.` para abrir o pull request no {% data variables.product.prodname_serverless %}. +3. Depois de fazer as alterações, faça o commit delas seguindo as etapas em de [Fazer commit das suas alterações](#commit-your-changes). As suas alterações serão registradas diretamente no branch. Não é necessário fazer push das alterações. + +## 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 %}. + +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 %}. + + +## Solução de Problemas + +Se você tiver problemas ao abrir {% data variables.product.prodname_serverless %}, tente o seguinte: + +- Verifique se você está conectado a {% data variables.product.prodname_dotcom %}. +- Desabilita qualquer bloqueador de anúncios. +- Use uma janela não anônima no seu navegador para abrir o {% 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 %}. diff --git a/translations/pt-BR/content/codespaces/troubleshooting/codespaces-logs.md b/translations/pt-BR/content/codespaces/troubleshooting/codespaces-logs.md index ae34ea12c9..9640f4f2c3 100644 --- a/translations/pt-BR/content/codespaces/troubleshooting/codespaces-logs.md +++ b/translations/pt-BR/content/codespaces/troubleshooting/codespaces-logs.md @@ -1,6 +1,6 @@ --- title: Registros de codespaces -intro: 'Overview of the logging locations used by {% data variables.product.prodname_codespaces %}.' +intro: 'Visão geral dos locais de registros usados por {% data variables.product.prodname_codespaces %}.' product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' @@ -12,43 +12,43 @@ shortTitle: Registros de codespaces --- -Information on {% data variables.product.prodname_codespaces %} is output to three different logs: +As informações sobre {% data variables.product.prodname_codespaces %} são saídas para três registros diferentes: -- Codespace logs -- Creation logs -- Extension logs ({% data variables.product.prodname_vscode %} desktop) or Browser console logs ({% data variables.product.prodname_vscode %} in the web) +- Registros do codespace +- Registros de criação +- Registro de extensões ({% data variables.product.prodname_vscode %} desktop) ou registros de console do navegador ({% data variables.product.prodname_vscode %} na web) -## Codespace logs +## Registros do codespace -These logs contain detailed information about the codespace, the container, the session, and the {% data variables.product.prodname_vscode %} environment. They are useful for diagnosing connection issues and other unexpected behavior. For example, the codespace freezes but the "Reload Windows" option unfreezes it for a few minutes, or you are randomly disconnected from the codespace but able to reconnect immediately. +Esses registros contêm informações detalhadas sobre o codespace, container, sessão e ambiente de {% data variables.product.prodname_vscode %}. Eles são úteis para diagnosticar problemas de conexão e outros comportamentos inesperados. Por exemplo, o codespace congela, mas a opção "Recarregar Windows" o descongela por alguns minutos ou você será desconectado do codespace aleatoriamente, mas poderá reconectar-se imediatamente. -1. If you are using {% data variables.product.prodname_codespaces %} in the browser, ensure that you are connected to the codespace you want to debug. -2. Open the Command Palette (`Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows)) and type **Export logs**. Select **Codespaces: Export Logs** from the list to download the logs. -3. Define where to save the zip archive of logs then click **Save** (desktop) or click **OK** (web). -4. If you are using {% data variables.product.prodname_codespaces %} in the browser, right-click on the zip archive of logs from the Explorer view and select **Download…** to download them to your local machine. +1. Se estiver usando {% data variables.product.prodname_codespaces %} no navegador, certifique-se de que esteja conectado ao codespace que deseja depurar. +2. Abra a Paleta de Comando (`Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows)) e digite **Exportar registros**. Selecione **Codespaces: Exportar registros** na lista para fazer o download dos registros. +3. Defina o local onde salvar o arquivo zip dos registros e, em seguida, clique em **Salvar** (desktop) ou clique em **OK** (web). +4. Se estiver usando {% data variables.product.prodname_codespaces %} no navegador, clique com o botão direito do mouse no arquivo zip dos registros na exibição do Explorer e selecione **Download…** para fazer o download para a sua máquina local. -## Creation logs +## Registros de criação -These logs contain information about the container, dev container, and their configuration. They are useful for debugging configuration and setup problems. +Estes registros contêm informações sobre o contêiner, contêiner de desenvolvimento e sua configuração. Eles são úteis para depuração de configurações e problemas de instalação. -1. Connect to the codespace you want to debug. -2. Open the Command Palette (`Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows)) and type **Creation logs**. Select **Codespaces: View Creation Log** from the list to open the `creation.log` file. +1. Conecte-se ao codespace que você deseja depurar. +2. Abra a Paleta de Comando (`Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows)) e digite **Registros de criação**. Selecione **codespaces: Visualizar registro de criação** na lista para abrir o arquivo `creation.log`. -If you want to share the log with support, you can copy the text from the creation log into a text editor and save the file locally. +Se você quiser compartilhar o registro com suporte, você poderá copiar o texto do registro de criação em um editor de texto e salvar o arquivo localmente. -## Extension logs +## Registros de extensão -These logs are available for {% data variables.product.prodname_vscode %} desktop users only. They are useful if it seems like the {% data variables.product.prodname_codespaces %} extension or {% data variables.product.prodname_vscode %} editor are having issues that prevent creation or connection. +Estes registros estão disponíveis apenas para usuários de área de trabalho de {% data variables.product.prodname_vscode %}. Eles são úteis para o caso de parecer que o editor de {% data variables.product.prodname_codespaces %} ou {% data variables.product.prodname_vscode %} estejam com problemas que impedem a criação ou conexão. -1. In {% data variables.product.prodname_vscode %}, open the Command Palette. -2. Type **Logs** and select **Developer: Open Extension Logs Folder** from the list to open the extension log folder in your system's file explorer. +1. Em {% data variables.product.prodname_vscode %}, abra a paleta de comando. +2. Digite **Registros** e selecione **Desenvolvedor: Abrir pasta de registros de extensão** na lista para abrir a pasta de registro de extensões no explorador do arquivo do seu sistema. -From this view, you can access logs generated by the various extensions that you use in {% data variables.product.prodname_vscode %}. You will see logs for GitHub Codespaces, GitHub Authentication, and Git, in addition to any other extensions you have enabled. +Nesta visualização, você poderá acessar os registros gerados pelas várias extensões que você usa em {% data variables.product.prodname_vscode %}. Você verá registros para os codespaces e para a autenticação do GitHub e Git, além de qualquer outra extensão que você habilitou. -## Browser console logs +## Registros do console do navegador -These logs are useful only if you want to debug problems with using {% data variables.product.prodname_codespaces %} in the browser. They are useful for debugging problems creating and connecting to {% data variables.product.prodname_codespaces %}. +Esses registros são úteis apenas se você quiser depurar problemas com o uso do {% data variables.product.prodname_codespaces %} no navegador. Eles são úteis para depurar problemas de criação e conexão com {% data variables.product.prodname_codespaces %}. -1. In the browser window for the codespace you want to debug, open the developer tools window. -2. Display the "Console" tab and click **errors** in the left side bar to show only the errors. -3. In the log area on the right, right-click and select **Save as** to save a copy of the errors to your local machine. ![Save errors](/assets/images/help/codespaces/browser-console-log-save.png) +1. Na janela do navegador para o ambiente de codespace que você deseja depurar, abra a janela de ferramentas do desenvolvedor. +2. Exibe a aba "Console" e clique em em **erros** na barra do lado esquerdo para mostrar apenas os erros. +3. Na área do registro à direita, clique com o botão direito e selecione **Salvar como** para salvar uma cópia dos erros na sua máquina local. ![Salvar erros](/assets/images/help/codespaces/browser-console-log-save.png) diff --git a/translations/pt-BR/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md b/translations/pt-BR/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md index 517663a638..0d788aebb7 100644 --- a/translations/pt-BR/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md +++ b/translations/pt-BR/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md @@ -1,27 +1,27 @@ --- -title: Exporting changes to a branch -intro: This article provides steps for exporting your codespace changes to a branch. +title: Exportando alterações para um branch +intro: Este artigo fornece etapas para exportar suas alterações de codespace para um branch. product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' type: reference topics: - Codespaces -shortTitle: Exporting changes +shortTitle: Exportando alterações --- -## Exporting changes to a branch +## Exportando alterações para um branch -While using {% data variables.product.prodname_codespaces %}, you may want to export your changes to a branch without launching a your codespace. +Ao usar o {% data variables.product.prodname_codespaces %}, você deverá exportar suas alterações para um branch sem carregar o seu codespace. -This can be useful when you have hit a [spending limit](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces) or have a general issue accessing your codespace. +Isso pode ser útil quando você atingir um limite de gastos [](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces) ou tiver um problema geral ao acessar seu código. -To export your changes: +Para exportar suas alterações: -1. Browse to the "Your Codespaces" page at [github.com/codespaces](https://github.com/codespaces) or, for an individual repository, click the **{% octicon "code" aria-label="The code icon" %} Code** menu. -2. Click the ellipsis (**...**) to the right of the codespace you want to export from. -3. Select **{% octicon "git-branch" aria-label="The git branch icon" %} Export changes to branch**. +1. Acesse a página "Seus codespaces" em [github.com/codespaces](https://github.com/codespaces) ou, em um repositório individual, clique no menu **{% octicon "code" aria-label="The code icon" %} Código**. +2. Clique nas reticências (**...**) à direita do codespace a partir do qual que você deseja exportar. +3. Selecione **{% octicon "git-branch" aria-label="The git branch icon" %} Alterações de exportação para o branch**. - ![Export changes to a branch](/assets/images/help/codespaces/export-changes-to-a-branch.png) + ![Exportar alterações para um branch](/assets/images/help/codespaces/export-changes-to-a-branch.png) -4. From the popover, select **Create branch**. +4. No anúncio emergente, selecione **Criar branch**. diff --git a/translations/pt-BR/content/codespaces/troubleshooting/index.md b/translations/pt-BR/content/codespaces/troubleshooting/index.md index fdd6f685ef..babbfb34b4 100644 --- a/translations/pt-BR/content/codespaces/troubleshooting/index.md +++ b/translations/pt-BR/content/codespaces/troubleshooting/index.md @@ -1,8 +1,8 @@ --- -title: Troubleshooting Codespaces +title: Solucionar problemas de codespaces shortTitle: Solução de Problemas product: '{% data reusables.gated-features.codespaces %}' -intro: 'These guides provide information for troubleshooting {% data variables.product.prodname_codespaces %}' +intro: 'Estes guias fornecem informações sobre solução de problemas de {% data variables.product.prodname_codespaces %}' versions: fpt: '*' redirect_from: diff --git a/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md b/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md index ef5afb91e2..86f487c84c 100644 --- a/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md +++ b/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md @@ -1,25 +1,25 @@ --- -title: Troubleshooting Codespaces clients -intro: 'You can use {% data variables.product.prodname_codespaces %} in your browser or through {% data variables.product.prodname_vscode %}. This article provides troubleshooting steps for common client issues.' +title: Solucionar problemas de clientes de codespace +intro: 'Você pode usar {% data variables.product.prodname_codespaces %} no seu navegador ou por meio de {% data variables.product.prodname_vscode %}. Este artigo fornece etapas de solução de problemas para problemas comuns do cliente.' product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' type: reference topics: - Codespaces -shortTitle: Codespaces clients +shortTitle: Clientes de codespaces --- ## Solução de problemas de {% data variables.product.prodname_vscode %} -When you connect a desktop version of {% data variables.product.prodname_vscode %} to a codespace, you will notice few differences compared with working in a normal workspace but the experience will be fairly similar. +Ao conectar uma versão de desktop de {% data variables.product.prodname_vscode %} a um codespace, você notará poucas diferenças em comparação com o trabalho num espaço de trabalho normal, mas a experiência será bastante semelhante. -When you open a codespace in your browser using {% data variables.product.prodname_vscode %} in the web, you will notice more differences. For example, some key bindings will be different or missing, and some extensions may behave differently. For a summary, see: "[Known limitations and adaptions](https://code.visualstudio.com/docs/remote/codespaces#_known-limitations-and-adaptations)" in the {% data variables.product.prodname_vscode %} docs. +Ao abrir um codespace no navegador usando {% data variables.product.prodname_vscode %} na web, você notará mais diferenças. Por exemplo, algumas teclas vinculadas serão diferentes ou estarão ausentes e algumas extensões poderão comportar-se de maneira diferente. Para obter um resumo, consulte: "[Limitações e adaptações conhecidas](https://code.visualstudio.com/docs/remote/codespaces#_known-limitations-and-adaptations)" na documentação de {% data variables.product.prodname_vscode %}. -You can check for known issues and log new issues with the {% data variables.product.prodname_vscode %} experience in the [`microsoft/vscode`](https://github.com/microsoft/vscode/issues?q=is%3Aissue+is%3Aopen+codespaces) repository. +É possível verificar se há problemas conhecidos e registrar novos problemas com a experiência de {% data variables.product.prodname_vscode %} no repositório [`microsoft/vscode`](https://github.com/microsoft/vscode/issues?q=is%3Aissue+is%3Aopen+codespaces). ## Solução de problemas do navegador -If you encounter issues using codespaces in a browser that is not Chromium-based, try switching to a Chromium-based browser, or check for known issues with your browser in the `microsoft/vscode` repository by searching for issues labeled with the name of your browser, such as [`firefox`](https://github.com/microsoft/vscode/issues?q=is%3Aissue+is%3Aopen+label%3Afirefox) or [`safari`](https://github.com/Microsoft/vscode/issues?q=is%3Aopen+is%3Aissue+label%3Asafari). +Se você encontrar problemas ao usar codespaces em um navegador que não é baseado no Chromium, tente alternar para um navegador baseado no Chromium ou verifique se há problemas conhecidos com seu navegador no repositório `microsoft/vscode` procurando por problemas etiquetados com o nome do seu navegador, como, por exemplo, [`fogo-fogo`](https://github.com/microsoft/vscode/issues?q=is%3Aissue+is%3Aopen+label%3Afirefox) ou [`safari`](https://github.com/Microsoft/vscode/issues?q=is%3Aopen+is%3Aissue+label%3Asafari). -If you encounter issues using codespaces in a Chromium-based browser, you can check if you're experiencing another known issue with {% data variables.product.prodname_vscode %} in the [`microsoft/vscode`](https://github.com/microsoft/vscode/issues) repository. +Se você encontrar problemas ao usar um codespace em um navegador baseado em Chromium, você poderá verificar se você está tendo outro problema conhecido com {% data variables.product.prodname_vscode %} no repositório [`microsoft/vscode`](https://github.com/microsoft/vscode/issues). diff --git a/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md b/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md index cdb37d8163..3c8e02d781 100644 --- a/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md +++ b/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md @@ -1,46 +1,46 @@ --- -title: Troubleshooting creation and deletion of Codespaces -intro: 'This article provides troubleshooting steps for common issues you may experience when creating or deleting a codespace, including storage and configuration issues.' +title: Solucionar problemas de criação e exclusão de codespaces +intro: 'Este artigo fornece etapas de solução de problemas para problemas comuns que você pode ter ao criar ou excluir um codespace, incluindo problemas de armazenamento e configuração.' product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' type: reference topics: - Codespaces -shortTitle: Creation and deletion +shortTitle: Criação e exclusão --- -## Creating codespaces +## Criando codespaces -### No access to create a codespace -{% data variables.product.prodname_codespaces %} are not available for all repositories. If the “Open with Codespaces” button is missing, {% data variables.product.prodname_codespaces %} may not be available for that repository. Para obter mais informações, consulte "[Criar um codespace](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces)". +### Sem acesso para criar um codespace +{% data variables.product.prodname_codespaces %} não estão disponíveis para todos os repositórios. Se faltar o botão "Abrir com codespaces", é possível que {% data variables.product.prodname_codespaces %} não esteja disponível para o repositório. Para obter mais informações, consulte "[Criar um codespace](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces)". -If you believe your organization has [enabled {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization#about-enabling-codespaces-for-your-organization), make sure that an organization owner or billing manager has set the spending limit for {% data variables.product.prodname_codespaces %}. Para obter mais informações, consulte "[Gerenciar seu limite de gastos para {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)". +Se você acredita que sua organização [habilitou {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization#about-enabling-codespaces-for-your-organization), certifique-se de que um proprietário ou gerente de cobrança da organização definiu o limite de gastos para {% data variables.product.prodname_codespaces %}. Para obter mais informações, consulte "[Gerenciar seu limite de gastos para {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)". -### Codespace does not open when created +### O codespace não abre quando criado -If you create a codespace and it does not open: +Se você criar um codespace e ele não abrir: -1. Try reloading the page in case there was a caching or reporting problem. -2. Go to your {% data variables.product.prodname_codespaces %} page: https://github.com/codespaces and check whether the new codespace is listed there. The process may have successfully created the codespace but failed to report back to your browser. If the new codespace is listed, you can open it directly from that page. -3. Retry creating the codespace for the repository to rule out a transient communication failure. +1. Tente atualizar a página no caso de haver um problema de cache ou comunicação. +2. Acesse a sua página de {% data variables.product.prodname_codespaces %}: https://github.com/codespaces e verifique se o novo codespace está listado lá. O processo pode ter criado com sucesso o codespace, mas não foi possível reportar ao seu navegador. Se o novo codespace estiver listado, você poderá abri-lo diretamente a partir daquela página. +3. Tente criar o código novamente para que o repositório exclua uma falha de comunicação temporária. -If you still cannot create a codespace for a repository where {% data variables.product.prodname_codespaces %} are available, {% data reusables.codespaces.contact-support %} +Se você ainda não puder criar um codespace para um repositório em que {% data variables.product.prodname_codespaces %} estão disponíveis, {% data reusables.codespaces.contact-support %} -## Deleting codespaces +## Excluindo codespaces -The owner of a codespace has full control over it and only they can delete their codespaces. You cannot delete a codespace created by another user. +O proprietário de um codespace tem controle total sobre ele e apenas o proprietário pode excluir seus codespaces. Você não pode excluir um codespace criado por outro usuário. -## Container storage +## Armazenamento do contêiner -Ao criar um codespace, ele terá uma quantidade limitada de armazenamento e, após um tempo, poderá ser necessário que você libere espaço. Try running any of the following commands in the {% data variables.product.prodname_codespaces %} terminal to free up storage space. +Ao criar um codespace, ele terá uma quantidade limitada de armazenamento e, após um tempo, poderá ser necessário que você libere espaço. Tente executar qualquer um dos comandos a seguir no terminal de {% data variables.product.prodname_codespaces %} para liberar espaço de armazenamento. -- Remove packages that are no longer used by using `sudo apt autoremove`. +- Remova pacotes que não são mais usados usando `sudo apt autoremove`. - Limpe o cache apt usando `sudo apt clean`. -- See the top 10 largest files in the codespace with`sudo find / -printf '%s %p\n'| sort -nr | head -10`. -- Delete unneeded files, such as build artifacts and logs. +- Veja os primeiros 10 maiores arquivos no codespace com`sudo find / -printf '%s %p\n'| sort -nr | head -10`. +- Exclua arquivos desnecessários, como artefatos e registros de criação. -Some more destructive options: +Algumas opções mais destrutivas: - Remova imagens não utilizadas do Docker, redes, e contêineres utilizando o `docker system prune` (insira `-a` se desejar remover todas as imagens, e `--volumes` se desejar remover todos os volumes). - Remova os arquivos não rastreados da árvore de trabalho: `git clean -i`. @@ -53,4 +53,4 @@ Some more destructive options: Este codespace está em execução em modo de recuperação devido a um erro no contêiner. ``` -Revise os registros de criação, atualize a configuração conforme necessário e execute **Codespaces: Rebuild Container** na paleta de comandos para tentar novamente. For more information, see " [Codespaces logs](/codespaces/troubleshooting/codespaces-logs)" and "[Configuring {% data variables.product.prodname_codespaces %} for your project](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#apply-changes-to-your-configuration)." +Revise os registros de criação, atualize a configuração conforme necessário e execute **Codespaces: Rebuild Container** na paleta de comandos para tentar novamente. Para obter mais informações, consulte " [Programas registra](/codespaces/troubleshooting/codespaces-logs)" e "[Configurando {% data variables.product.prodname_codespaces %} para o seu projeto](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#apply-changes-to-your-configuration)". diff --git a/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-dotfiles-for-codespaces.md b/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-dotfiles-for-codespaces.md index 43347e9975..7cbff0018e 100644 --- a/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-dotfiles-for-codespaces.md +++ b/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-dotfiles-for-codespaces.md @@ -1,6 +1,6 @@ --- -title: Troubleshooting dotfiles for Codespaces -intro: Troubleshooting steps for common dotfiles issues. +title: Solucionando pontos para codespaces +intro: Etapas de solução de problemas para problemas comuns de dotfiles. product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' @@ -10,12 +10,12 @@ topics: shortTitle: Dotfiles --- -If your codespace fails to pick up configuration settings from dotfiles, you should work through the following debugging steps. +Se o seu codespace não consegue pegar as configurações de dotfiles, você deverá seguir as etapas de depuração a seguir. 1. Certifique-se de que seu repositório dotfiles seja público. Se você tem segredos ou dados confidenciais que você deseja usar em seu código, use [segredos de codespaces ](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces) em vez dos dotfiles privados. 2. Verifique `/workspaces/.codespaces/.persistedshare/dotfiles` para ver se seus dotfiles foram clonados. - - If your dotfiles were cloned, try manually re-running your install script to verify that it is executable. - - If your dotfiles were not cloned, check `/workspaces/.codespaces/.persistedshare/EnvironmentLog.txt` to see if there was a problem cloning them. -3. Verifique `/workspaces/.codespaces/.persistedshare/creation.log` com relação a possíveis problemas. For more information, see [Creation logs](/codespaces/troubleshooting/codespaces-logs#creation-logs). + - Se seus dotfiles foram clonados, tente reexecutar manualmente seu script de instalação para verificar se é executável. + - Se seus dotfiles não foram clonados, consulte `/workspaces/.codespaces/.persistedshare/EnvironmentLog.txt` para ver se houve um problema com a clonagem. +3. Verifique `/workspaces/.codespaces/.persistedshare/creation.log` com relação a possíveis problemas. Para obter mais informações, consulte [Registros de criação](/codespaces/troubleshooting/codespaces-logs#creation-logs). -If the configuration from your dotfiles is correctly picked up, but part of the configuration is incompatible with codespaces, use the `$CODESPACES` environment variable to add conditional logic for codespace-specific configuration settings. +Se a configuração de seus dotfiles for selecionada corretamente, mas parte da configuração for incompatível com os codespaces, use a variável de ambiente `$CODESPACES` para adicionar lógica condicional para configurações específicas do codespace. diff --git a/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-port-forwarding-for-codespaces.md b/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-port-forwarding-for-codespaces.md index 1f0bf8b863..7a87b3fd43 100644 --- a/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-port-forwarding-for-codespaces.md +++ b/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-port-forwarding-for-codespaces.md @@ -1,20 +1,20 @@ --- -title: Troubleshooting port forwarding for Codespaces -intro: Troubleshooting steps for common port forwarding issues. +title: Solução de problemas de encaminhamento de porta para codespaces +intro: Etapas de solução de problemas para problemas comuns de encaminhamento de portas. product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' type: reference topics: - Codespaces -shortTitle: Port forwarding +shortTitle: Encaminhamento de porta --- -When an application running inside a codespace outputs a port to the console, {% data variables.product.prodname_codespaces %} detects the localhost URL pattern and automatically forwards the port. For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)." +Quando um aplicativo em execução em uma saída de codespace gera uma porta para o console, {% data variables.product.prodname_codespaces %}, irá detectar o padrão da URL do host local e encaminhará a porta automaticamente. Para obter mais informações, consulte "[Encaminhando portas no seu codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)". -If a port is not automatically forwarded, you can forward it manually. For more information, see "[Forwarding a port](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace#forwarding-a-port)." +Se uma porta não for redirecionada automaticamente, você poderá redirecioná-la manualmente. Para obter mais informações, consulte "[Encaminhando uma porta](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace#forwarding-a-port). " -If port forwarding is set up, check the following: +Se o encaminhamento de porta estiver configurado, verifique o seguinte: -- Use the notification toast or click the URL in Terminal to open the forwarded port. Typing in `localhost:8000` (as an example) to your local machine will not work if you're connected to the codespace via the browser. -- Make sure to check that your application is still running from within your codespace. If your codespace has stopped after a period of inactivity, you'll need to ensure to restart your application once the codespace has restarted. +- Use o alerta de notificação ou clique no URL no Terminal para abrir a porta encaminhada. Digitar `localhost:8000` (como exemplo) na sua máquina local não funcionará se você estiver conectado ao codespace por meio do navegador. +- Certifique-se de verificar se seu aplicativo ainda está sendo executado dentro do seu codespace. Se seu codespace parou após um período de inatividade, você deverá certificar-se de reiniciar o seu aplicativo depois que o codespace for reiniciado. diff --git a/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-your-connection-to-codespaces.md b/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-your-connection-to-codespaces.md index fde9fd98f9..39c465cd9a 100644 --- a/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-your-connection-to-codespaces.md +++ b/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-your-connection-to-codespaces.md @@ -1,6 +1,6 @@ --- -title: Troubleshooting your connection to Codespaces -intro: 'Troubleshooting help for connecting to {% data variables.product.prodname_codespaces %}.' +title: Solucionando a sua conexão com codespaces +intro: 'Solução de problemas de ajuda para conectar-se a {% data variables.product.prodname_codespaces %}.' product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' @@ -12,35 +12,35 @@ shortTitle: Conexão ## 503 codespace service unavailable -Codespaces are set to stop after 30 minutes without any activity. If you try to interact with a codespace after it has stopped, you may see a `503 service unavailable` error. +Os codespaces são definidos para parar após 30 minutos sem atividade. Se você tentar interagir com um codespace depois de parar, é possível que você veja um erro `503 service unavailable`. -- If a **Start** button is shown in {% data variables.product.prodname_vscode %} or in your browser window, click **Start** to reconnect to the codespace. -- Reset your codespace by reloading the window. From the [command palette](/codespaces/codespaces-reference/using-the-command-palette-in-codespaces#accessing-the-command-palette) in {% data variables.product.prodname_vscode %}, click **Developer: Reload Window**. +- Se um botão **Iniciar** for exibido em {% data variables.product.prodname_vscode %} ou na janela do seu navegador, clique em **Iniciar** para reconectar ao codespace. +- Redefina o seu codespace recarregando a janela. A partir da [paleta de comando](/codespaces/codespaces-reference/using-the-command-palette-in-codespaces#accessing-the-command-palette) em {% data variables.product.prodname_vscode %}, clique em **Desenvolvedor: Recarregar Janela**. -## Browser cannot connect +## Não foi possível conectar o navegador -Sometimes you may not be able to access a codespace from your browser. If this happens, go to https://github.com/codespaces and try connecting to the codespace from that page. +Às vezes, é possível que você não consiga acessar um codespace a partir do seu navegador. Se isso acontecer, acesse https://github.com/codespaces e tente conectar-se ao codespace a partir da página. - - If the codespace is not listed on that page, check that you are the owner of the codespace you are trying to connect to. You can only open a codespace that you created. The URLs for your codespaces always include your {% data variables.product.company_short %} handle. - - If the codespace is listed but you cannot connect from that page, check whether you can connect using a different browser. + - Se o codespace não estiver listado nessa página, verifique se você é o proprietário do codespace que ao qual você está tentando se conectar. Você só pode abrir um codespace que você criou. As URLs dos seus codespace sempre incluem o seu gerenciamento de {% data variables.product.company_short %}. + - Se o codespace estiver listado, mas você não puder conectar-se a partir dessa página, verifique se você pode conectar-se usando um navegador diferente. -Your company network may be blocking the connection. If possible, check any logging for rejected connections on your device. +A rede da sua empresa pode estar bloqueando a conexão. Se possível, verifique qualquer registro com relação a conexões rejeitadas no seu dispositivo. -If you still cannot connect, {% data reusables.codespaces.contact-support %} +Se você ainda não conseguir conectar-se, {% data reusables.codespaces.contact-support %} -## {% data variables.product.prodname_github_codespaces %} extension for {% data variables.product.prodname_vscode %} cannot connect +## a extensão de {% data variables.product.prodname_github_codespaces %} para {% data variables.product.prodname_vscode %} não poderá conectar -If you cannot connect to a codespace from {% data variables.product.prodname_vscode %} desktop, use the following troubleshooting steps. +Se você não consegue conectar-se a um codespace a partir da área de trabalho de {% data variables.product.prodname_vscode %}, siga as etapas de solução de problemas a seguir. -1. Check that you have the latest version of the {% data variables.product.prodname_github_codespaces %} extension installed. The extension is a preview release and frequent updates are released. - 1. In {% data variables.product.prodname_vscode %}, display the "Extensions" tab. - 2. Select the {% data variables.product.prodname_github_codespaces %} extension to display the extension's overview page. - 3. If an update is available, a button is shown, click **Update to X.X.X** to upgrade to the latest version. -2. Check whether you are using the stable build of {% data variables.product.prodname_vscode %} or the [{% data variables.product.prodname_vscode %} Insiders](https://code.visualstudio.com/insiders/) release (nightly updates). If you are using the insiders release, try installing the [stable build](https://code.visualstudio.com/). -3. Your company network may be blocking the connection. If possible, check any logging for rejected connections on your device. +1. Verifique se você tem a versão mais recente da extensão de {% data variables.product.prodname_github_codespaces %} instalada. A extensão é uma versão de pré-visualização e atualizações frequentes são lançadas. + 1. Em {% data variables.product.prodname_vscode %}, exiba a aba "Extensões". + 2. Selecione a extensão {% data variables.product.prodname_github_codespaces %} para exibir a página de visão geral da extensão. + 3. Se uma atualização estiver disponível, userá exibido um botão. Clique em **Atualizar para X.X.X** para atualizar para a última versão. +2. Verifique se você está usando a compilação estável de {% data variables.product.prodname_vscode %} ou a versão de [{% data variables.product.prodname_vscode %} Insiders](https://code.visualstudio.com/insiders/) (com atualizações noturnas). Se você estiver usando a versão de insiders, tente instalar a [criação estável](https://code.visualstudio.com/). +3. A rede da sua empresa pode estar bloqueando a conexão. Se possível, verifique qualquer registro com relação a conexões rejeitadas no seu dispositivo. -If you still cannot connect, {% data reusables.codespaces.contact-support %} +Se você ainda não conseguir conectar-se, {% data reusables.codespaces.contact-support %} -### The codespace has latency issues +### O codespace tem problemas de latência -If the codespace seems particularly slow or has latency issues, it is possible that it has been created in a region that is far from you. To resolve this, you can [manually set your {% data variables.product.prodname_github_codespaces %} region](/codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces). +Se o codespace parecer particularmente lento ou tiver problemas de latência, é possível que tenha sido criado em região distante de você. Para resolver isso, você pode [definir manualmente a sua região de {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces). diff --git a/translations/pt-BR/content/codespaces/troubleshooting/working-with-support-for-codespaces.md b/translations/pt-BR/content/codespaces/troubleshooting/working-with-support-for-codespaces.md index bfc7bb64af..6ce17c5e35 100644 --- a/translations/pt-BR/content/codespaces/troubleshooting/working-with-support-for-codespaces.md +++ b/translations/pt-BR/content/codespaces/troubleshooting/working-with-support-for-codespaces.md @@ -1,6 +1,6 @@ --- -title: Working with support for Codespaces -intro: 'Tips on getting the best help from support for {% data variables.product.prodname_codespaces %}.' +title: Trabalhando com suporte para codespaces +intro: 'Dicas para obter a melhor ajuda do suporte para {% data variables.product.prodname_codespaces %}.' product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' @@ -10,24 +10,24 @@ topics: shortTitle: Trabalhando com suporte --- -Before support can help you with problems with codespaces, you need to know the name of the codespace and its codespaces ID (identifier). In addition, support may ask you to share some logs with them. For more information, see "[Codespaces logs](/codespaces/troubleshooting/codespaces-logs)" and "[About GitHub Support](/github/working-with-github-support/about-github-support)." +Antes de o suporte poder ajudar você com problemas com codespaces, você precisa saber o nome e o ID (identificador) do seu codespace. Além disso, o suporte pode pedir que você compartilhe alguns registros. Para obter mais informações, consulte "[Registros de codespace](/codespaces/troubleshooting/codespaces-logs)" e "[Sobre o suporte do GitHub](/github/working-with-github-support/about-github-support)". -### Codespace names +### Nomes do codespace -Each codespace has a unique name that is a combination of your {% data variables.product.company_short %} handle, the repository name, and some random characters. The additional characters allow you to have codespaces for different branches in the same repository. For example: `octocat-myrepo-gmc7`. +Cada codespace tem um nome único que é uma combinação da manipulação de {% data variables.product.company_short %}, do nome do repositório e alguns caracteres aleatórios. Os caracteres adicionais permitem que você tenha codespaces para diferentes branches no mesmo repositório. Por exemplo: `octocat-myrepo-gmc7`. -To find the name of a codespace: +Para encontrar o nome de um codespace: -- Open the codespace in the browser. The subdomain of the URL is the name of the codespace. For example: `https://octocat-myrepo-gmc7.github.dev` is the URL for the `octocat-myrepo-gmc7` codespace. -- If you cannot open a codespace, you can access the name in {% data variables.product.product_name %} on https://github.com/codespaces. The name is shown in a pop-up when you hover over the **Open in browser** option on https://github.com/codespaces. ![Codespace name shown on hover over](/assets/images/help/codespaces/find-codespace-name-github.png) +- Abra o codespace no navegador. O subdomínio da URL é o nome do codespace. Por exemplo: `https://octocat-myrepo-gmc7.github.dev` é a URL para o codespace `octocat-myrepo-gmc7`. +- Se você não puder abrir um codespace, você poderá acessar o nome em {% data variables.product.product_name %} em https://github.com/codespaces. O nome é exibido em uma janela pop-up, quando você passar o mouse sobre a opção **Abrir no navegador** em https://github.com/codespaces. ![O nome do código exibido ao passar o mouse sobre](/assets/images/help/codespaces/find-codespace-name-github.png) -The name the codespace is also included in many of the log files. For example, in the codespace logs as the value of `friendlyName`, in the {% data variables.product.prodname_github_codespaces %} extension log after `making GET request for`, and in the browser console log after `clientUrl`. For more information, see "[Codespaces logs](/codespaces/troubleshooting/codespaces-logs)." +O nome do código também está incluído em muitos dos arquivos de registro. Por exemplo, nos registros de código como o valor de `friendlyName`, no registro da extensão de {% data variables.product.prodname_github_codespaces %} após `fazer pedido GET para` e no registro do console de navegação após `clientUrl`. Para obter mais informações, consulte "[Registros de codespace](/codespaces/troubleshooting/codespaces-logs)". -### Codespaces IDs +### IDs de codespaces -Every codespace also has an ID (identifer). This is not shown by default in {% data variables.product.prodname_vscode %} so you may need to update the settings for the {% data variables.product.prodname_github_codespaces %} extension before you can access the ID. +Cada código tem também um ID (identificador). Ele não é exibido por padrão em {% data variables.product.prodname_vscode %}. Portanto, é possível que você precise atualizar as configurações para a extensão {% data variables.product.prodname_github_codespaces %} antes de acessar o ID. -1. In {% data variables.product.prodname_vscode %}, browser or desktop, in the Activity Bar on the left, click **Remote Explorer** to show details for the codespace. -2. If the sidebar includes a "Codespace Performance" section, hover over the "Codespace ID" and click the clipboard icon to copy the ID. -3. If the information is not shown, click {% octicon "gear" aria-label="The gear icon" %}, in the bottom-left corner of the Activity Bar, to display the "Settings" tab. -4. Expand **Extensions** and click **{% data variables.product.prodname_github_codespaces %}** to display the settings for the extension. Then enable **Show Performance Explorer** to display the "Codespace Performance" section in the sidebar. ![Codespace ID and settings required to display performance information](/assets/images/help/codespaces/find-codespace-id.png) +1. Em {% data variables.product.prodname_vscode %}, navegador ou área de trabalho, na barra de atividades à esquerda, clique em **Explorador remoto** para mostrar as informações para o codespace. +2. Se a barra lateral incluir uma seção "Desempenho do codespace", passe o mouse sobre o "ID do codespace" e clique no ícone da área de transferência para copiar o ID. +3. Se a informação não for exibida, clique em {% octicon "gear" aria-label="The gear icon" %} no canto inferior esquerdo da barra de atividade, para exibir a aba "Configurações". +4. Expanda **Extensões** e clique em **{% data variables.product.prodname_github_codespaces %}** para exibir as configurações da extensão. Em seguida, habilite o **Exibir o explorador de desempenho** para exibir a seção "Codespace" na barra lateral. ![O ID do codespace e configurações necessárias para exibir informações de desempenho](/assets/images/help/codespaces/find-codespace-id.png) diff --git a/translations/pt-BR/content/communities/documenting-your-project-with-wikis/about-wikis.md b/translations/pt-BR/content/communities/documenting-your-project-with-wikis/about-wikis.md index 06f34bf455..1e586b92d9 100644 --- a/translations/pt-BR/content/communities/documenting-your-project-with-wikis/about-wikis.md +++ b/translations/pt-BR/content/communities/documenting-your-project-with-wikis/about-wikis.md @@ -34,4 +34,4 @@ Você pode editar wikis diretamente no {% data variables.product.product_name %} - "[Criar um footer ou uma barra lateral para seu wiki](/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki)" - "[Editar conteúdo do wiki](/communities/documenting-your-project-with-wikis/editing-wiki-content)" - "[Exibir histórico de alterações de um wiki](/articles/viewing-a-wiki-s-history-of-changes)" -- "[Pesquisar wikis](/articles/searching-wikis)" +- "[Pesquisar wikis](/search-github/searching-on-github/searching-wikis)" diff --git a/translations/pt-BR/content/communities/index.md b/translations/pt-BR/content/communities/index.md index ce6c27c54f..cac9f0d72e 100644 --- a/translations/pt-BR/content/communities/index.md +++ b/translations/pt-BR/content/communities/index.md @@ -1,7 +1,7 @@ --- title: Criar comunidades shortTitle: Criar comunidades -intro: 'Learn best practices for moderating and setting up collaborative, safe, and effective communities using GitHub’s community-tested tools.' +intro: 'Aprenda as práticas recomendadas para moderar e configurar comunidades colaborativas, seguras e eficazes usando as ferramentas testadas pela comunidade do GitHub.' redirect_from: - /categories/building-a-strong-community - /github/building-a-strong-community diff --git a/translations/pt-BR/content/communities/moderating-comments-and-conversations/locking-conversations.md b/translations/pt-BR/content/communities/moderating-comments-and-conversations/locking-conversations.md index c7a9228d4b..79417d9010 100644 --- a/translations/pt-BR/content/communities/moderating-comments-and-conversations/locking-conversations.md +++ b/translations/pt-BR/content/communities/moderating-comments-and-conversations/locking-conversations.md @@ -20,7 +20,7 @@ Bloquear uma conversa cria um evento na linha do tempo visível a qualquer um co Quando uma conversa é bloqueada, somente [pessoas com acesso de gravação](/articles/repository-permission-levels-for-an-organization/) e [proprietários e colaboradores de repositórios](/articles/permission-levels-for-a-user-account-repository/#collaborator-access-for-a-repository-owned-by-a-user-account) podem adicionar, ocultar ou excluir comentários. -Para pesquisar conversas bloqueadas em um repositório que não está arquivado, é posível usar os qualificadores de pesquisa `is:locked` e `archived:false`. As conversas são automaticamente bloqueadas em repositórios arquivados. Para obter mais informações, consulte "[Pesquisar problemas e pull requests](/articles/searching-issues-and-pull-requests#search-based-on-whether-a-conversation-is-locked)". +Para pesquisar conversas bloqueadas em um repositório que não está arquivado, é posível usar os qualificadores de pesquisa `is:locked` e `archived:false`. As conversas são automaticamente bloqueadas em repositórios arquivados. Para obter mais informações, consulte "[Pesquisar problemas e pull requests](/search-github/searching-on-github/searching-issues-and-pull-requests#search-based-on-whether-a-conversation-is-locked)". 1. Como opção, escreva um comentário explicando por que você está bloqueando a conversa. 2. Na margem direita do problema ou pull request ou acima da caixa de comentários na página de commit, clique em **Lock conversation** (Bloquear conversa). ![Link Lock conversation (Bloquear conversa)](/assets/images/help/repository/lock-conversation.png) diff --git a/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md b/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md index e01ddc4c89..19cb5f57d8 100644 --- a/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md +++ b/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md @@ -15,7 +15,7 @@ shortTitle: Arquivo de integridade da comunidade ## Sobre arquivos padrão de integridade da comunidade -You can add default community health files to a public repository called `.github`, in the root of the repository or in the `docs` or `.github` folders. +Você pode adicionar arquivos padrão de saúde da comunidade a um repositório público denominado `git.hub` na raiz do repositório ou nas pastas `docs` ou `.github`. {% data variables.product.product_name %} usará e exibirá arquivos padrão para qualquer repositório pertencente à conta que não tem seu próprio arquivo desse tipo em nenhum dos seguintes lugares: - a raiz do repositório @@ -49,4 +49,4 @@ Você não pode criar um arquivo de licença padrão. Os arquivos de licença de 4. Certifique-se de que o status do repositório está definido como **Público** (um repositório-padrão para arquivos não pode ser privado). ![Botões de opção para selecionar status privado ou público](/assets/images/help/repository/create-repository-public-private.png) {% data reusables.repositories.initialize-with-readme %} {% data reusables.repositories.create-repo %} -7. No repositório, crie um dos arquivos compatíveis de integridade da comunidade. Modelos de problema{% ifversion fpt or ghae or ghes %} e seu arquivo de configuração{% endif %} devem estar em uma pasta chamada `.github/ISSUE_TEMPLATE`. All other supported files may be in the root of the repository, the `.github` folder, or the `docs` folder. Para obter mais informações, consulte "[Criar arquivos](/articles/creating-new-files/)". +7. No repositório, crie um dos arquivos compatíveis de integridade da comunidade. Modelos de problema{% ifversion fpt or ghae or ghes %} e seu arquivo de configuração{% endif %} devem estar em uma pasta chamada `.github/ISSUE_TEMPLATE`. Todos os outros arquivos compatíveis podem estar na raiz do repositório, na pasta `.github` ou na pasta `docs`. Para obter mais informações, consulte "[Criar arquivos](/articles/creating-new-files/)". diff --git a/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels.md b/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels.md index 8def4aeeae..9db25da9a6 100644 --- a/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels.md +++ b/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels.md @@ -12,7 +12,7 @@ topics: shortTitle: Incentivar contribuições --- -Você pode aplicar a etiqueta `good first issue` nos problemas em seu repositório público, assim as pessoas podem encontrá-los quando pesquisarem usando etiquetas. Para obter mais informações sobre como pesquisar com etiquetas, consulte "[Pesquisar problemas e pull requests](/articles/searching-issues-and-pull-requests/#search-by-label)". +Você pode aplicar a etiqueta `good first issue` nos problemas em seu repositório público, assim as pessoas podem encontrá-los quando pesquisarem usando etiquetas. Para obter mais informações sobre como pesquisar com etiquetas, consulte "[Pesquisar problemas e pull requests](/search-github/searching-on-github/searching-issues-and-pull-requests/#search-by-label)". O {% data variables.product.prodname_dotcom %} usa um algoritmo para determinar os problemas mais acessíveis em cada repositório e apresenta-os em vários lugares no {% data variables.product.prodname_dotcom_the_website %}. Adicionar a etiqueta `good first issue` (um bom primeiro problema) pode aumentar a probabilidade de seus problemas serem apresentados. @@ -24,4 +24,4 @@ O {% data variables.product.prodname_dotcom %} usa um algoritmo para determinar ## Leia mais - "[Sobre etiquetas](/articles/about-labels)" -- "[Pesquisar repositórios](/articles/searching-for-repositories)" +- "[Pesquisar repositórios](/search-github/searching-on-github/searching-for-repositories)" diff --git a/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md b/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md index 6b36b9aa9e..8218d2383a 100644 --- a/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md +++ b/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md @@ -41,7 +41,7 @@ Você pode criar diretrizes de contribuição padrão para sua organização{% i {% data reusables.repositories.navigate-to-repo %} {% data reusables.files.add-file %} -3. Decida se deseja armazenar as diretrizes de contribuição no diretório root, `docs` ou `.github` do repositório. Em seguida, no campo de nome do arquivo, digite o nome e a extensão do arquivo. Os nomes de arquivos com diretrizes de contribuição não são sensíveis a maiúsculas de minúsculas. Os arquivos são renderizados no formato de texto rich se a extensão do arquivo estiver em um formato compatível. For more information, see "[Working with non-code files](/repositories/working-with-files/using-files/working-with-non-code-files#rendering-differences-in-prose-documents)." ![Nome do novo arquivo](/assets/images/help/repository/new-file-name.png) +3. Decida se deseja armazenar as diretrizes de contribuição no diretório root, `docs` ou `.github` do repositório. Em seguida, no campo de nome do arquivo, digite o nome e a extensão do arquivo. Os nomes de arquivos com diretrizes de contribuição não são sensíveis a maiúsculas de minúsculas. Os arquivos são renderizados no formato de texto rich se a extensão do arquivo estiver em um formato compatível. Para obter mais informações, consulte "[Trabalhando com arquivos sem código](/repositories/working-with-files/using-files/working-with-non-code-files#rendering-differences-in-prose-documents)". ![Nome do novo arquivo](/assets/images/help/repository/new-file-name.png) - Para tornar as diretrizes de contribuição visíveis no diretório raiz do repositório, digite *CONTRIBUTING*. - Para tornar as diretrizes de contribuição visíveis no diretório `docs` do repositório, digite *docs/* para criar o diretório e, em seguida, digite *CONTRIBUTING*. - Se um repositório contiver mais de um arquivo *CONTRIBUTING*, o arquivo mostrado em links será escolhido entre locais na seguinte ordem: diretório do `.github`, em seguida, o diretório raiz do repositório e, finalmente, o diretório de `docs`. 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 490e563e2f..e695a78f7a 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 @@ -70,7 +70,7 @@ Você pode incentivar os contribuidores a usar modelos de problemas definindo `b {% note %} -**Note:** If you used the legacy workflow to manually create an `issue_template.md` file in the `.github` folder and enable blank issues in your *config.yml* file, the template in `issue_template.md` will be used when people chose to open a blank issue. Se você desativar problemas em branco, o modelo nunca será usado. +**Observação:** Se você usou o fluxo de trabalho de legado para criar manualmente um arquivo `issue_template.md` na pasta `.github` e habilitar problemas em branco no seu arquivo *config.yml*, o modelo em `issue_template.md` será usado quando as pessoas escolherem abrir um problema em branco. Se você desativar problemas em branco, o modelo nunca será usado. {% endnote %} diff --git a/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md b/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md index 10a7475f9f..77a1e7beb8 100644 --- a/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md +++ b/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md @@ -58,12 +58,12 @@ Por exemplo, a definição de formulário a seguir inclui quatro elementos de fo Para cada elemento de formulário, você pode definir as seguintes chaves. -| Tecla | Descrição | Obrigatório | Tipo | Padrão | Valores válidos | -| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | ------ | ----------------------------------------------- | ----------------------------------------------- | -| `tipo` | O tipo de elemento que você deseja definir. | Obrigatório | string | {% octicon "dash" aria-label="The dash icon" %} |
    • `checkboxes`
    • `dropdown`
    • `input`
    • `markdown`
    • `textarea`
    | -| `id` | The identifier for the element, except when `type` is set to `markdown`. {% data reusables.form-schema.id-must-be-unique %} Se fornecido, o `ID` é o identificador canônico para o campo no parâmetro de consulta da URL. | Opcional | string | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} -| `attributes` | Um conjunto de pares chave-valor que definem as propriedades do elemento. | Obrigatório | Hash | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} -| `validações` | Um conjunto de pares chave-valor que define restrições sobre o elemento. | Opcional | Hash | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} +| Tecla | Descrição | Obrigatório | Tipo | Padrão | Valores válidos | +| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | ------ | ----------------------------------------------- | ----------------------------------------------- | +| `tipo` | O tipo de elemento que você deseja definir. | Obrigatório | string | {% octicon "dash" aria-label="The dash icon" %} |
    • `checkboxes`
    • `dropdown`
    • `input`
    • `markdown`
    • `textarea`
    | +| `id` | O identificador para o elemento, exceto quando `tipo` é definido como `markdown`. {% data reusables.form-schema.id-must-be-unique %} Se fornecido, o `ID` é o identificador canônico para o campo no parâmetro de consulta da URL. | Opcional | string | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} +| `attributes` | Um conjunto de pares chave-valor que definem as propriedades do elemento. | Obrigatório | Hash | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} +| `validações` | Um conjunto de pares chave-valor que define restrições sobre o elemento. | Opcional | Hash | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} Você pode escolher entre os seguintes tipos de elementos de formulário. Cada tipo tem atributos e validações exclusivos. diff --git a/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md b/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md index 650fc8deee..ed6d123553 100644 --- a/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md +++ b/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md @@ -16,7 +16,7 @@ Você pode criar formulários de problemas personalizados adicionando um arquivo Quando um contribuidor preenche um formulário de problemas, as suas respostas para cada entrada são convertidas em markdown e adicionadas ao corpo de um issue. Os contribuidores podem editar seus problemas criados com formulários de problemas e outras pessoas podem interagir com problemas como um problema criado por meio de outros métodos. -Issue forms are not supported for pull requests. You can create pull request templates in your repositories for collaborators to use. Para obter mais informações, consulte "[Criar um modelo de pull request para o repositório](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository)". +Os formulários de problemas não são compatíveis com pull requests. É possível criar modelos de pull request nos seus repositórios para os colaboradores usarem. Para obter mais informações, consulte "[Criar um modelo de pull request para o repositório](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository)". Este exemplo de arquivo de configuração YAML define um formulário de problema utilizando várias entradas para reportar um erro. diff --git a/translations/pt-BR/content/developers/apps/building-github-apps/authenticating-with-github-apps.md b/translations/pt-BR/content/developers/apps/building-github-apps/authenticating-with-github-apps.md index d0daaa977f..59ded1bb75 100644 --- a/translations/pt-BR/content/developers/apps/building-github-apps/authenticating-with-github-apps.md +++ b/translations/pt-BR/content/developers/apps/building-github-apps/authenticating-with-github-apps.md @@ -87,7 +87,7 @@ jwt = JWT.encode(payload, private_key, "RS256") puts jwt ``` -`YOUR_PATH_TO_PEM` e `YOUR_APP_ID` são os valores que você deve substituir. Make sure to enclose the values in double quotes. +`YOUR_PATH_TO_PEM` e `YOUR_APP_ID` são os valores que você deve substituir. Certifique-se de incluir os valores entre aspas duplas. Use o seu identificador de {% data variables.product.prodname_github_app %}(`YOUR_APP_ID`) como o valor para a reivindicação do JWT [iss](https://tools.ietf.org/html/rfc7519#section-4.1.1) (emissor). Você pode obter o identificador {% data variables.product.prodname_github_app %} por meio do ping inicial do webhook, após [criar o aplicativo](/apps/building-github-apps/creating-a-github-app/), ou a qualquer momento na da página de configurações do aplicativo na UI do GitHub.com. @@ -116,7 +116,7 @@ Para obter uma lista dos pontos finais da API REST que você pode usar para obte ## Autenticar como uma instalação -Autenticar como uma instalação permite que você execute ações na API para essa instalação. Antes de autenticar como uma instalação, você deverá criar um token de acesso de instalação. Certifique-se de que você já instalou o aplicativo GitHub em pelo menos um repositório; é impossível criar um token de instalação sem uma única instalação. These installation access tokens are used by {% data variables.product.prodname_github_apps %} to authenticate. For more information, see "[Installing GitHub Apps](/developers/apps/managing-github-apps/installing-github-apps)." +Autenticar como uma instalação permite que você execute ações na API para essa instalação. Antes de autenticar como uma instalação, você deverá criar um token de acesso de instalação. Certifique-se de que você já instalou o aplicativo GitHub em pelo menos um repositório; é impossível criar um token de instalação sem uma única instalação. Estes tokens de acesso de instalação são usados por {% data variables.product.prodname_github_apps %} para efetuar a autenticação. Para obter mais informações, consulte "[Instalando aplicativos GitHub](/developers/apps/managing-github-apps/installing-github-apps)". Por padrão, os tokens de acesso de instalação são limitados em todos os repositórios que uma instalação pode acessar. É possível limitar o escopo do token de acesso de instalação a repositórios específicos usando o parâmetro `repository_ids`. Consulte [Criar um token de acesso de instalação para um ponto final de um aplicativo](/rest/reference/apps#create-an-installation-access-token-for-an-app) para obter mais informações. Os tokens de acesso de instalação têm as permissões configuradas pelo {% data variables.product.prodname_github_app %} e expiram após uma hora. @@ -155,7 +155,7 @@ $ curl -i \ ## Acessar pontos finais da API como uma instalação -For a list of REST API endpoints that are available for use by {% data variables.product.prodname_github_apps %} using an installation access token, see "[Available Endpoints](/rest/overview/endpoints-available-for-github-apps)." +Para obter uma lista de pontos de extremidade da API REST disponíveis para uso por {% data variables.product.prodname_github_apps %} usando um token de acesso de instalação, consulte "[pontos de extremidade disponíveis](/rest/overview/endpoints-available-for-github-apps)." Para obter uma lista de pontos finais relacionados a instalações, consulte "[Instalações](/rest/reference/apps#installations)". 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 bb8fb6c4b0..815a5792a9 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 @@ -42,6 +42,7 @@ Ao usar o fluxo de aplicativo web, o processo para identificar usuários no seu Se você selecionar **Solicitar autorização de usuário (OAuth) durante a instalação** ao criar ou modificar seu aplicativo, a etapa 1 será concluída durante a instalação do aplicativo. Para obter mais informações, consulte "[Autorizando usuários durante a instalação](/apps/installing-github-apps/#authorizing-users-during-installation)". ### 1. Solicitar identidade do GitHub de um usuário +Direcione o usuário para a seguinte URL em seu navegador: GET {% data variables.product.oauth_host_code %}/login/oauth/authorize @@ -73,10 +74,12 @@ Se o usuário aceitar o seu pedido, O GitHub irá fazer o redirecionamento para {% endnote %} -Troque este `código` por um token de acesso. When expiring tokens are enabled, the access token expires in 8 hours and the refresh token expires in 6 months. Toda vez que você atualizar o token, você receberá um novo token de atualização. Para obter mais informações, consulte "[Atualizando tokens de acesso do usuário para servidor](/developers/apps/refreshing-user-to-server-access-tokens)." +Troque este `código` por um token de acesso. Quando os tokens vencidos estiverem habilitados, token de acesso irá expirar em 8 horas e o token de atualização irá expirar em 6 meses. Toda vez que você atualizar o token, você receberá um novo token de atualização. Para obter mais informações, consulte "[Atualizando tokens de acesso do usuário para servidor](/developers/apps/refreshing-user-to-server-access-tokens)." Os tokens de usuário expirados são atualmente um recurso opcional e estão sujeitos a alterações. Para optar por participar do recurso de expiração de token de usuário para servidor, consulte "[Habilitar funcionalidades opcionais para aplicativos](/developers/apps/activating-optional-features-for-apps)." +Faça um pedido para o seguinte ponto de extremidade para receber um token de acesso: + POST {% data variables.product.oauth_host_code %}/login/oauth/access_token #### Parâmetros diff --git a/translations/pt-BR/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md b/translations/pt-BR/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md index 6c25f7da55..ed8492d5ea 100644 --- a/translations/pt-BR/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md +++ b/translations/pt-BR/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md @@ -20,7 +20,7 @@ shortTitle: Limites de taxa {% ifversion fpt %} -Different server-to-server request rate limits apply to {% data variables.product.prodname_github_apps %} if the app is installed on organizations or repositories owned by a {% data variables.product.prodname_ghe_cloud %} account. +Aplicam-se diferentes limites de solicitação de servidor para servidor a {% data variables.product.prodname_github_apps %} se o aplicativo estiver instalado em organizações ou repositórios pertencentes a uma conta de {% data variables.product.prodname_ghe_cloud %}. ### Limites de taxa normais de servidor a servidor @@ -32,17 +32,17 @@ Different server-to-server request rate limits apply to {% data variables.produc ### Limites de taxa de servidor a servidor de {% data variables.product.prodname_ghe_cloud %} -{% data variables.product.prodname_github_apps %} that are installed on an organization or repository owned by a {% data variables.product.prodname_ghe_cloud %} account and make server-to-server requests have a rate limit of 15,000 requests per hour. +{% data variables.product.prodname_github_apps %} que está instalado em uma organização ou repositório de propriedade de uma conta de {% data variables.product.prodname_ghe_cloud %} e que faz solicitações de servidor para servidor tem um limite de taxa de 15.000 requisições por hora por organização para instalações de organização ou por repositório para instalações de repositório. {% endif %} ## Solicitações de usuário para servidor -{% data variables.product.prodname_github_apps %} can also act [on behalf of a user](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-and-authorizing-users-for-github-apps), making user-to-server requests. +{% data variables.product.prodname_github_apps %} também pode atuar [em nome de um usuário](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-and-authorizing-users-for-github-apps), fazendo solicitações do usuário para servidor. {% ifversion fpt %} -Different user-to-server request rate limits apply to {% data variables.product.prodname_github_apps %} if the app is installed on organizations or repositories owned by a {% data variables.product.prodname_ghe_cloud %} account and the authenticated user also belongs to the same {% data variables.product.prodname_ghe_cloud %} account. +Aplicam-se diferentes limites de taxa de solicitação de usuário para servidor a {% data variables.product.prodname_github_apps %} se o aplicativo estiver instalado em organizações ou repositórios de propriedade de uma conta de {% data variables.product.prodname_ghe_cloud %} e o usuário autenticado também pertencer à mesma conta {% data variables.product.prodname_ghe_cloud %} . ### Limites de taxa normais de usuário para servidor diff --git a/translations/pt-BR/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md b/translations/pt-BR/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md index 7a8c95f1bb..de4528833c 100644 --- a/translations/pt-BR/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md +++ b/translations/pt-BR/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md @@ -71,9 +71,9 @@ Se você desejar que o seu aplicativo use tokens de acesso do usuário para serv ![Opção para expirar os tokens dos usuários durante a configuração dos aplicativos GitHub](/assets/images/github-apps/expire-user-tokens-selection.png) -Existing {% data variables.product.prodname_github_apps %} using user-to-server authorization tokens are only affected by this new flow when the app owner enables expiring user tokens for their app. +Os {% data variables.product.prodname_github_apps %} existentes que usa tokens de autorização de usuário para servidor só são afetados por este novo fluxo quando o proprietário do aplicativo habilita o vencimento de tokens de usuário para seu aplicativo. -Enabling expiring user tokens for existing {% data variables.product.prodname_github_apps %} requires sending users through the OAuth flow to re-issue new user tokens that will expire in 8 hours and making a request with the refresh token to get a new access token and refresh token. Para obter mais informações, consulte "[Identificar e autorizar usuários para aplicativos GitHub](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)". +Habilitar o vencimento de tokens de usuário para {% data variables.product.prodname_github_apps %} existentes exige o envio de usuários por meio do do fluxo do OAuth para reemitir tokens de usuário que vencerão em 8 horas e fazer uma solicitação com o token de atualização para obter um novo token de acesso e token de atualização. Para obter mais informações, consulte "[Identificar e autorizar usuários para aplicativos GitHub](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)". {% ifversion fpt or ghes > 3.1 or ghae-next %} 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 d80a01896c..6f1f15417d 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 @@ -17,14 +17,14 @@ topics: - OAuth Apps --- -{% data variables.product.product_name %}'s OAuth implementation supports the standard [authorization code grant type](https://tools.ietf.org/html/rfc6749#section-4.1) and the OAuth 2.0 [Device Authorization Grant](https://tools.ietf.org/html/rfc8628) for apps that don't have access to a web browser. +A implementação OAuth de {% data variables.product.product_name %} é compatível com o [ tipo de código de autorização padrão](https://tools.ietf.org/html/rfc6749#section-4.1) e com o OAuth 2.0 [Concessão de Autorização do Dispositivo](https://tools.ietf.org/html/rfc8628) para aplicativos que não têm acesso a um navegador web. Se você desejar ignorar a autorização do seu aplicativo da forma-padrão, como no teste do seu aplicativo, você poderá usar o fluxo do aplicativo [que não é web](#non-web-application-flow). Para autorizar o seu aplicativo OAuth, considere qual fluxo de autorização melhor se adequa ao seu aplicativo. -- [Fluxo de aplicativos web](#web-application-flow): Usado para autorizar usuários para aplicativos OAuth padrão executados no navegador. (The [implicit grant type](https://tools.ietf.org/html/rfc6749#section-4.2) is not supported.){% ifversion fpt or ghae or ghes > 3.0 %} -- [device flow](#device-flow): Used for headless apps, such as CLI tools.{% endif %} +- [Fluxo de aplicativos web](#web-application-flow): Usado para autorizar usuários para aplicativos OAuth padrão executados no navegador. (O [implícito tipo de concessão](https://tools.ietf.org/html/rfc6749#section-4.2) não é compatível){% ifversion fpt or ghae or ghes > 3.0 %} +- [fluxo do dispositivo](#device-flow): usado para sem cabeçalho, como ferramentas de CLI.{% endif %} ## Fluxo do aplicativo web @@ -78,19 +78,29 @@ Troque este `código` por um token de acesso: Por padrão, a resposta assume o seguinte formato: - access_token={% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&token_type=bearer +``` +access_token={% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&scope=repo%2Cgist&token_type=bearer +``` -Você também pode receber o conteúdo em diferentes formatos, dependendo do cabeçalho Aceitar: +{% data reusables.apps.oauth-auth-vary-response %} - Accept: application/json - {"access_token":"{% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "scope":"repo,gist", "token_type":"bearer"} - - Accept: application/xml - - bearer - repo,gist - {% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %} - +```json +Accept: application/json +{ + "access_token":"{% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", + "scope":"repo,gist", + "token_type":"bearer" +} +``` + +```xml +Accept: application/xml + + bearer + repo,gist + {% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %} + +``` ### 3. Use o token de acesso para acessar a API @@ -138,27 +148,35 @@ O seu aplicativo deve solicitar um código de verificação e uma URL de verific #### Resposta -{% ifversion fpt %} - ```JSON - { - "device_code": "3584d83530557fdd1f46af8289938c8ef79f9dc5", - "user_code": "WDJB-MJHT", - "verification_uri": "https://github.com/login/device", - "expires_in": 900, - "interval": 5 - } - ``` -{% else %} - ```JSON - { - "device_code": "3584d83530557fdd1f46af8289938c8ef79f9dc5", - "user_code": "WDJB-MJHT", - "verification_uri": "http(s)://[hostname]/login/device", - "expires_in": 900, - "interval": 5 - } - ``` -{% endif %} +Por padrão, a resposta assume o seguinte formato: + +``` +device_code=3584d83530557fdd1f46af8289938c8ef79f9dc5&expires_in=900&interval=5&user_code=WDJB-MJHT&verification_uri=https%3A%2F%{% data variables.product.product_url %}%2Flogin%2Fdevice +``` + +{% data reusables.apps.oauth-auth-vary-response %} + +```json +Accept: application/json +{ + "device_code": "3584d83530557fdd1f46af8289938c8ef79f9dc5", + "user_code": "WDJB-MJHT", + "verification_uri": "{% data variables.product.oauth_host_code %}/login/device", + "expires_in": 900, + "interval": 5 +} +``` + +```xml +Accept: application/xml + + 3584d83530557fdd1f46af8289938c8ef79f9dc5 + WDJB-MJHT + {% data variables.product.oauth_host_code %}/login/device + 900 + 5 + +``` #### Parâmetros de resposta @@ -196,14 +214,32 @@ Uma vez que o usuário tenha autorizado, o aplicativo receberá um token de aces #### Resposta +Por padrão, a resposta assume o seguinte formato: + +``` +access_token={% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&token_type=bearer&scope=repo%2Cgist +``` + +{% data reusables.apps.oauth-auth-vary-response %} + ```json +Accept: application/json { "access_token": "{% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "token_type": "bearer", - "scope": "user" + "scope": "repo,gist" } ``` +```xml +Accept: application/xml + + {% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %} + bearer + gist,repo + +``` + ### Limites de taxa para o fluxo do dispositivo Quando um usuário envia o código de verificação no navegador, há um limite de taxa de 50 envios por hora por aplicativo. @@ -292,8 +328,8 @@ 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)" -{% ifversion fpt or ghae or ghes > 3.0 %}* "[Device flow errors](#error-codes-for-the-device-flow)"{% endif %}{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 %} -* "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %} +{% ifversion fpt or ghae or ghes > 3.0 %}* "[Erros do fluxo do aplicativo](#error-codes-for-the-device-flow)"{% endif %}{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 %} +* "[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 e16f6464dc..cb0c87d0b5 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 @@ -47,7 +47,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 > 3.0 %} -|  `security_events` | Grants:
    read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning)
    read and write access to security events in the [{% data variables.product.prodname_secret_scanning %} API](/rest/reference/secret-scanning)
    This scope is only necessary to grant other users or services access to security events *without* granting access to the code.{% endif %}{% ifversion ghes < 3.1 %} +|  `security_events` | Concede:
    acesso de leitura e gravação a eventos de segurança na [API de {% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning)
    acesso de leitura e gravação a eventos de segurança na [API de {% data variables.product.prodname_secret_scanning %}](/rest/reference/secret-scanning)
    Este escopo só é necessário para conceder acesso a outros usuários ou serviços a eventos de segurança *sem* conceder acesso ao código.{% endif %}{% ifversion ghes < 3.1 %} |  `security_events` | Concede acesso de leitura e gravação a eventos de segurança na [API {% data variables.product.prodname_code_scanning %}](/rest/reference/code-scanning). Este escopo só é necessário para conceder a outros usuários ou serviços acesso a eventos de segurança *sem* conceder acesso ao código.{% endif %} | **`admin:repo_hook`** | Concede acesso de leitura, gravação, marcação e exclusão a hooks de repositório em {% ifversion not ghae %}público{% else %}interno{% endif %} e repositórios privados. O escopos do `repo` {% ifversion not ghae %}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 marcação a hooks em {% ifversion not ghae %}público{% else %}interno{% endif %} ou repositórios privados. | 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 632b9d9843..471d588fc4 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 @@ -17,7 +17,7 @@ topics: Os aplicativos no {% data variables.product.prodname_dotcom %} permitem que você automatize e melhore seu fluxo de trabalho. Você pode criar aplicativos para melhorar seu fluxo de trabalho. {% ifversion fpt %} Você também pode compartilhar ou vender aplicativos em [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace). Para aprender como listar um aplicativo no {% data variables.product.prodname_marketplace %}, consulte "[Introdução ao GitHub Marketplace](/marketplace/getting-started/)".{% endif %} -{% data reusables.marketplace.github_apps_preferred %}, but GitHub supports both {% data variables.product.prodname_oauth_apps %} and {% data variables.product.prodname_github_apps %}. Para obter informações sobre a escolha de um tipo de aplicativo, consulte "[Diferenças entre os aplicativos GitHub e os aplicativos OAuth](/developers/apps/differences-between-github-apps-and-oauth-apps)". +{% data reusables.marketplace.github_apps_preferred %}, mas o GitHub é compatível com {% data variables.product.prodname_oauth_apps %} e {% data variables.product.prodname_github_apps %}. Para obter informações sobre a escolha de um tipo de aplicativo, consulte "[Diferenças entre os aplicativos GitHub e os aplicativos OAuth](/developers/apps/differences-between-github-apps-and-oauth-apps)". {% data reusables.apps.general-apps-restrictions %} @@ -50,7 +50,7 @@ Tenha isso em mente ao criar {% data variables.product.prodname_github_apps %}: Para começar a desenvolver {% data variables.product.prodname_github_apps %}, comece com "[Criando um {% data variables.product.prodname_github_app %}](/apps/building-github-apps/creating-a-github-app/).{% ifversion fpt %} Para aprender a usar manifestos de {% data variables.product.prodname_github_app %}, que permitem que pessoas criem {% data variables.product.prodname_github_apps %} pré-configurados, consulte "[Criando {% data variables.product.prodname_github_apps %} a partir de um manifesto](/apps/building-github-apps/creating-github-apps-from-a-manifest/).{% endif %} -## About {% data variables.product.prodname_oauth_apps %} +## Sobre {% data variables.product.prodname_oauth_apps %} OAuth2 é um protocolo que permite que os aplicativos externos solicitem autorização para detalhes privados na conta {% data variables.product.prodname_dotcom %} de um usuário sem acessar sua senha. Isto é preferido em relação à autenticação básica, porque os tokens podem ser limitados a tipos específicos de dados e podem ser revogados pelos usuários a qualquer momento. @@ -58,19 +58,19 @@ OAuth2 é um protocolo que permite que os aplicativos externos solicitem autoriz Um {% data variables.product.prodname_oauth_app %} usa {% data variables.product.prodname_dotcom %} como um provedor de identidade para efetuar a autenticação como o usuário que concede acesso ao aplicativo. Isso significa que, quando um usuário concede acesso {% data variables.product.prodname_oauth_app %}, ele concedem permissões a _todos_ os repositórios aos quais tem acesso em sua conta, e também a qualquer organização a que pertence que não bloqueou o acesso de terceiros. -Construir um {% data variables.product.prodname_oauth_app %} é uma boa opção se você estiver criando processos mais complexos do que um simples script pode gerenciar. Note that {% data variables.product.prodname_oauth_apps %} are applications that need to be hosted somewhere. +Construir um {% data variables.product.prodname_oauth_app %} é uma boa opção se você estiver criando processos mais complexos do que um simples script pode gerenciar. Note que {% data variables.product.prodname_oauth_apps %} são aplicativos que precisam ser hospedados em algum lugar. -Keep these ideas in mind when creating {% data variables.product.prodname_oauth_apps %}: +Tenha isso em mente ao criar {% data variables.product.prodname_oauth_apps %}: {% ifversion fpt %} * {% data reusables.apps.maximum-oauth-apps-allowed %} {% endif %} * Um {% data variables.product.prodname_oauth_app %} deve sempre atuar como o usuário autenticado {% data variables.product.prodname_dotcom %} em todo o {% data variables.product.prodname_dotcom %} (por exemplo, ao fornecer notificações de usuário). * Um {% data variables.product.prodname_oauth_app %} pode ser usado como um provedor de identidade, habilitando um "Login com {% data variables.product.prodname_dotcom %}" para o usuário autenticado. -* Não crie um {% data variables.product.prodname_oauth_app %}, se desejar que seu aplicativo atue em um único repositório. With the `repo` OAuth scope, {% data variables.product.prodname_oauth_apps %} can act on _all_ of the authenticated user's repositories. -* Não crie um {% data variables.product.prodname_oauth_app %} para atuar como um aplicativo para sua equipe ou empresa. {% data variables.product.prodname_oauth_apps %} authenticate as a single user, so if one person creates an {% data variables.product.prodname_oauth_app %} for a company to use, and then they leave the company, no one else will have access to it.{% ifversion fpt %} +* Não crie um {% data variables.product.prodname_oauth_app %}, se desejar que seu aplicativo atue em um único repositório. Com o escopo de `repo` do OAuth, {% data variables.product.prodname_oauth_apps %} pode atuar em _todos_ os repositórios de usuários autenticados. +* Não crie um {% data variables.product.prodname_oauth_app %} para atuar como um aplicativo para sua equipe ou empresa. {% data variables.product.prodname_oauth_apps %} efetua a autenticação como um usuário único. Portanto se uma pessoa criar um {% data variables.product.prodname_oauth_app %} para uma empresa usar e, posteriormente, sair da empresa, ninguém mais terá acesso.{% ifversion fpt %} * {% data reusables.apps.oauth-apps-restrictions %}{% endif %} -For more on {% data variables.product.prodname_oauth_apps %}, see "[Creating an {% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/creating-an-oauth-app/)" and "[Registering your app](/rest/guides/basics-of-authentication#registering-your-app)." +Para obter mais informações sobre {% data variables.product.prodname_oauth_apps %}, consulte "[Criando um {% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/creating-an-oauth-app/)" e "[Registrando seu aplicativo](/rest/guides/basics-of-authentication#registering-your-app)". ## Tokens de acesso pessoal @@ -84,12 +84,12 @@ 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. -* Don't set up a shared user account to act as a bot user.{% ifversion fpt or ghes > 3.2 or ghae-issue-4374 %} -* Do set an expiration for your personal access tokens, to help keep your information secure.{% endif %} +* Não configure uma conta de usuário compartilhada para agir atuar um usuário bot.{% ifversion fpt or ghes > 3.2 or ghae-issue-4374 %} +* Defina um vencimento para os seus tokens de acesso pessoais para ajudar a manter suas informações seguras.{% endif %} ## Determinar qual integração criar -Antes de começar a criar integrações, você deve determinar a melhor maneira de acessar, autenticar e interagir com as APIs do {% data variables.product.prodname_dotcom %}. The following image offers some questions to ask yourself when deciding whether to use personal access tokens, {% data variables.product.prodname_github_apps %}, or {% data variables.product.prodname_oauth_apps %} for your integration. +Antes de começar a criar integrações, você deve determinar a melhor maneira de acessar, autenticar e interagir com as APIs do {% data variables.product.prodname_dotcom %}. A imagem a seguir oferece algumas perguntas de segurança ao decidir se usa tokens de acesso pessoais, {% data variables.product.prodname_github_apps %}ou {% data variables.product.prodname_oauth_apps %} para sua integração. ![Introdução ao fluxo de perguntas dos aplicativos](/assets/images/intro-to-apps-flow.png) diff --git a/translations/pt-BR/content/developers/apps/getting-started-with-apps/activating-optional-features-for-apps.md b/translations/pt-BR/content/developers/apps/getting-started-with-apps/activating-optional-features-for-apps.md index bd4a44a026..4b6c6d4fcd 100644 --- a/translations/pt-BR/content/developers/apps/getting-started-with-apps/activating-optional-features-for-apps.md +++ b/translations/pt-BR/content/developers/apps/getting-started-with-apps/activating-optional-features-for-apps.md @@ -1,6 +1,6 @@ --- title: Ativar funcionalidades opcionais para os aplicativos -intro: 'You can test new optional features for your {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}.' +intro: 'Você pode testar novas funcionalidades opcionais para seu {% data variables.product.prodname_github_apps %} e {% data variables.product.prodname_oauth_apps %}.' redirect_from: - /developers/apps/activating-beta-features-for-apps - /developers/apps/activating-optional-features-for-apps diff --git a/translations/pt-BR/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md b/translations/pt-BR/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md index 57b3af6580..41bfccb481 100644 --- a/translations/pt-BR/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md +++ b/translations/pt-BR/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md @@ -1,6 +1,6 @@ --- title: Diferenças entre os aplicativos GitHub e OAuth -intro: 'Understanding the differences between {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %} will help you decide which app you want to create. O {% data variables.product.prodname_oauth_app %} atua como usuário do GitHub, enquanto o {% data variables.product.prodname_github_app %} usa sua própria identidade quando instalado em uma organização ou em repositórios de uma organização.' +intro: 'Entender as diferenças entre {% data variables.product.prodname_github_apps %} e {% data variables.product.prodname_oauth_apps %} ajudará você a decidir qual aplicativo você deseja criar. O {% data variables.product.prodname_oauth_app %} atua como usuário do GitHub, enquanto o {% data variables.product.prodname_github_app %} usa sua própria identidade quando instalado em uma organização ou em repositórios de uma organização.' redirect_from: - /early-access/integrations/integrations-vs-oauth-applications/ - /apps/building-integrations/setting-up-a-new-integration/about-choosing-an-integration-type/ @@ -56,14 +56,14 @@ Um aplicativo OAuth _authorized_ tem acesso a todos os recursos acessíveis do u {% endnote %} -| Aplicativos do GitHub | Aplicativos OAuth | -| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Um aplicativo GitHub pode solicitar um token de acesso de instalação usando uma chave privada com um formato de token do JSON fora da banda. | Um aplicativo OAuth pode trocar um token de solicitação por um token de acesso após um redirecionamento por meio de uma solicitação da web. | -| Um token de instalação identifica o aplicativo como o bot do aplicativo GitHub, como, por exemplo, @jenkins-bot. | Um token de acesso identifica o aplicativo como o usuário que concedeu o token ao aplicativo, como, por exemplo, o @octocat. | -| Os tokens de instalação expiram após um tempo predefinido (atualmente, 1 hora). | Os tokens do OAuth permanecem ativos até que sejam cancelados pelo cliente. | -| {% data reusables.apps.api-rate-limits-non-ghec %}{% ifversion fpt %} Aplicam-se limites de taxa mais altos para {% data variables.product.prodname_ghe_cloud %}. Para obter mais informações, consulte "[Limites de taxas para os aplicativos GitHub](/developers/apps/rate-limits-for-github-apps)."{% endif %} | Os tokens do OAuth usam o limite de taxa de usuário de 5.000 solicitações por hora. | -| Os aumentos no limite de taxa pode ser concedido tanto no nível do aplicativo GitHub (afetando todas as instalações) quanto no nível de instalação individual. | Os aumentos no limite de taxa são concedidos pelo aplicativo OAuth. Todo token concedido para que o aplicativo OAuth obtém um aumento do limite. | -| {% data variables.product.prodname_github_apps %} can authenticate on behalf of the user, which is called user-to-server requests. O fluxo para autorizar é o mesmo que o fluxo de autorização do aplicativo OAuth. Os tokens de usuário para servidor podem expirar e ser renovados com um token de atualização. Para obter mais informações, consulte "[Atualizando tokens de acesso do usuário para servidor](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)" e "[identificando e autorizando os usuários para os aplicativos GitHub](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)". | The OAuth flow used by {% data variables.product.prodname_oauth_apps %} authorizes an {% data variables.product.prodname_oauth_app %} on behalf of the user. Este é o mesmo fluxo de uso na autorização de usuário para servidor do {% data variables.product.prodname_github_app %}. | +| Aplicativos do GitHub | Aplicativos OAuth | +| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| Um aplicativo GitHub pode solicitar um token de acesso de instalação usando uma chave privada com um formato de token do JSON fora da banda. | Um aplicativo OAuth pode trocar um token de solicitação por um token de acesso após um redirecionamento por meio de uma solicitação da web. | +| Um token de instalação identifica o aplicativo como o bot do aplicativo GitHub, como, por exemplo, @jenkins-bot. | Um token de acesso identifica o aplicativo como o usuário que concedeu o token ao aplicativo, como, por exemplo, o @octocat. | +| Os tokens de instalação expiram após um tempo predefinido (atualmente, 1 hora). | Os tokens do OAuth permanecem ativos até que sejam cancelados pelo cliente. | +| {% data reusables.apps.api-rate-limits-non-ghec %}{% ifversion fpt %} Aplicam-se limites de taxa mais altos para {% data variables.product.prodname_ghe_cloud %}. Para obter mais informações, consulte "[Limites de taxas para os aplicativos GitHub](/developers/apps/rate-limits-for-github-apps)."{% endif %} | Os tokens do OAuth usam o limite de taxa de usuário de 5.000 solicitações por hora. | +| Os aumentos no limite de taxa pode ser concedido tanto no nível do aplicativo GitHub (afetando todas as instalações) quanto no nível de instalação individual. | Os aumentos no limite de taxa são concedidos pelo aplicativo OAuth. Todo token concedido para que o aplicativo OAuth obtém um aumento do limite. | +| {% data variables.product.prodname_github_apps %} pode efetuar a autenticação em nome do usuário, que é denominado de solicitações de usuário para servidor. O fluxo para autorizar é o mesmo que o fluxo de autorização do aplicativo OAuth. Os tokens de usuário para servidor podem expirar e ser renovados com um token de atualização. Para obter mais informações, consulte "[Atualizando tokens de acesso do usuário para servidor](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)" e "[identificando e autorizando os usuários para os aplicativos GitHub](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)". | O fluxo do OAuth usado por {% data variables.product.prodname_oauth_apps %} autoriza um {% data variables.product.prodname_oauth_app %} em nome do usuário. Este é o mesmo fluxo de uso na autorização de usuário para servidor do {% data variables.product.prodname_github_app %}. | ## Solicitar níveis de permissão para os recursos diff --git a/translations/pt-BR/content/developers/apps/getting-started-with-apps/migrating-oauth-apps-to-github-apps.md b/translations/pt-BR/content/developers/apps/getting-started-with-apps/migrating-oauth-apps-to-github-apps.md index de94aca796..704851158b 100644 --- a/translations/pt-BR/content/developers/apps/getting-started-with-apps/migrating-oauth-apps-to-github-apps.md +++ b/translations/pt-BR/content/developers/apps/getting-started-with-apps/migrating-oauth-apps-to-github-apps.md @@ -10,7 +10,7 @@ versions: ghae: '*' topics: - GitHub Apps -shortTitle: Migrate from OAuth Apps +shortTitle: Fazer a migração dos aplicativos OAuth --- Este artigo fornece orientações para integradores existentes que estão considerando a migração de um aplicativo OAuth para um aplicativo GitHub. @@ -41,14 +41,14 @@ Essas diretrizes assumem que você tem um aplicativo OAuth registrado{% ifversio 1. [Entenda os diferentes métodos de autenticação](#understand-the-different-methods-of-authentication) 1. [Oriente os usuários para instalar o seu aplicativo GitHub nos repositórios](#direct-users-to-install-your-github-app-on-repositories) 1. [Remova quaisquer hooks de repositório desnecessários](#remove-any-unnecessary-repository-hooks) -1. [Encourage users to revoke access to your OAuth App](#encourage-users-to-revoke-access-to-your-oauth-app) -1. [Delete the OAuth App](#delete-the-oauth-app) +1. [Incentive os usuários a revogar o acesso ao seu aplicativo OAuth](#encourage-users-to-revoke-access-to-your-oauth-app) +1. [Exclua o aplicativo OAuth](#delete-the-oauth-app) ### Revise os pontos finais da API disponíveis para os aplicativos do GitHub Embora a maioria dos pontos finais da [API REST](/rest) e as consultas do [GraphQL](/graphql) estejam disponíveis para os aplicativos GitHub atualmente, ainda estamos em vias de habilitar alguns pontos finais. Revise os [pontos finais da REST disponíveis](/rest/overview/endpoints-available-for-github-apps) para garantir que os pontos finais de que você precisa sejam compatíveis com o aplicativo GitHub. Observe que alguns dos pontos finais da API ativados para os aplicativos GitHub permitem que o aplicativo aja em nome do usuário. Consulte "[Solicitações de usuário para servidor](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-to-server-requests)" para obter uma lista de pontos finais que permitem que um aplicativo GitHub seja autenticado como usuário. -Recomendamos que você reveja a lista de pontos finais de API de que você precisa assim que possível. Please let Support know if there is an endpoint you require that is not yet enabled for {% data variables.product.prodname_github_apps %}. +Recomendamos que você reveja a lista de pontos finais de API de que você precisa assim que possível. Informe ao suporte se há um ponto de extremidade necessário que ainda não esteja habilitado para {% data variables.product.prodname_github_apps %}. ### Projete para permanecer dentro dos limites de taxa da API @@ -102,8 +102,8 @@ Uma vez que seu aplicativo GitHub foi instalado em um repositório, você deve r ### Incentive os usuários a revogar o acesso ao seu aplicativo OAuth -As your GitHub App installation base grows, consider encouraging your users to revoke access to the legacy OAuth integration. Para obter mais informações, consulte "[Autorizar aplicativos OAuth](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps)". +À medida que sua base de instalação do aplicativo GitHub aumenta, incentive seus usuários a revogar o acesso à integração do legado do OAuth. Para obter mais informações, consulte "[Autorizar aplicativos OAuth](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps)". -### Delete the OAuth App +### Exclua o aplicativo OAuth -To avoid abuse of the OAuth App's credentials, consider deleting the OAuth App. This action will also revoke all of the OAuth App's remaining authorizations. For more information, see "[Deleting an OAuth App](/developers/apps/managing-oauth-apps/deleting-an-oauth-app)." +Para evitar o abuso das credenciais do aplicativo OAuth, considere excluir o aplicativo OAuth. Esta ação também irá revogar todas as autorizações restantes do aplicativo OAuth. Para obter mais informações, consulte "[Excluindo um aplicativo OAuth](/developers/apps/managing-oauth-apps/deleting-an-oauth-app)". diff --git a/translations/pt-BR/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md b/translations/pt-BR/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md index 2b44c51027..32a804ec77 100644 --- a/translations/pt-BR/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md +++ b/translations/pt-BR/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md @@ -25,7 +25,7 @@ Os fluxos de instalação pública têm uma página inicial para permitir que ou ## Fluxo privado de instalação -Os fluxos privados de instalação permitem que somente o proprietário de um aplicativo GitHub a instale. Informações limitadas sobre o GitHub App continuarão a existir em uma página pública, mas o botão **Instalar** só estará disponível para administradores da organização ou para a conta de usuário se o aplicativo GitHub for propriedade de uma conta individual. Privado{% ifversion ghes < 3.2 or ghae %} ou interno{% endif %} os aplicativos GitHub só podem ser instalados na conta de usuário ou da organização do proprietário. +Os fluxos privados de instalação permitem que somente o proprietário de um aplicativo GitHub a instale. Informações limitadas sobre o GitHub App continuarão a existir em uma página pública, mas o botão **Instalar** só estará disponível para administradores da organização ou para a conta de usuário se o aplicativo GitHub for propriedade de uma conta individual. {% ifversion fpt or ghes > 3.1 or ghae-next %}Privado {% else %}Privado (também conhecido como interno){% endif %} Os aplicativos GitHub só podem ser instalados na conta de usuário ou de organização do proprietário. ## Alterar quem pode instalar seu aplicativo GitHub @@ -36,5 +36,5 @@ Para alterar quem pode instalar o aplicativo GitHub: {% data reusables.user-settings.github_apps %} 3. Selecione o aplicativo GitHub cuja opção de instalação você deseja alterar. ![Seleção de aplicativo](/assets/images/github-apps/github_apps_select-app.png) {% data reusables.user-settings.github_apps_advanced %} -5. Dependendo da opção de instalação do seu aplicativo GitHub, clique em **Tornar público** ou **Tornar {% ifversion fpt or ghes > 3.1 %}privado{% else %}interno{% endif %}**. ![Botão para alterar a opção de instalação do seu aplicativo GitHub](/assets/images/github-apps/github_apps_make_public.png) -6. Dependendo da opção de instalação do seu aplicativo GitHub, clique **Sim, torne público este aplicativo GitHub** ou **Sim, torne este aplicativo GitHub {% ifversion fpt or ghes > 3.1 %}privado{% else %}interno{% endif %}**. ![Botão para confirmar a mudança de sua opção de instalação](/assets/images/github-apps/github_apps_confirm_installation_option.png) +5. Dependendo da opção de instalação do seu aplicativo GitHub, clique em **Tornar público** ou **Tornar {% ifversion fpt or ghes > 3.1 or ghae-next %}privado{% else %}interno{% endif %}**. ![Botão para alterar a opção de instalação do seu aplicativo GitHub](/assets/images/github-apps/github_apps_make_public.png) +6. Dependendo da opção de instalação do seu aplicativo GitHub, clique **Sim, torne público este aplicativo GitHub** ou **Sim, torne este aplicativo GitHub {% ifversion fpt or ghes < 3.2 %}interno{% else %}interno{% endif %}**. ![Botão para confirmar a mudança de sua opção de instalação](/assets/images/github-apps/github_apps_confirm_installation_option.png) diff --git a/translations/pt-BR/content/developers/apps/managing-github-apps/suspending-a-github-app-installation.md b/translations/pt-BR/content/developers/apps/managing-github-apps/suspending-a-github-app-installation.md index 0a44be8e9c..9fdf720435 100644 --- a/translations/pt-BR/content/developers/apps/managing-github-apps/suspending-a-github-app-installation.md +++ b/translations/pt-BR/content/developers/apps/managing-github-apps/suspending-a-github-app-installation.md @@ -19,7 +19,7 @@ O integrador que possui e mantém um aplicativo GitHub, também chamado de propr Pessoas que instalaram um aplicativo GitHub, também chamado de proprietários de instalação, só podem suspender ou cancelar a suspensão de um aplicativo GitHub através das configurações de instalação do aplicativo. Os proprietários de instalação não podem usar a API para suspender ou cancelar a suspensão da instalação do aplicativo. -If an installation has been suspended by the {% data variables.product.prodname_github_app %} owner, installation owners cannot unsuspend their installations of the {% data variables.product.prodname_github_app %}. However, installation owners can change other settings, such as repository selection, while the app is suspended. +Se uma instalação foi suspensa pelo proprietário de {% data variables.product.prodname_github_app %}, os proprietários da instalação não poderão cancelar a suspensão das suas instalações de {% data variables.product.prodname_github_app %}. No entanto, os proprietários de instalação podem alterar outras configurações, como a seleção de repositório, enquanto o aplicativo está suspenso. {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.developer_settings %} diff --git a/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md b/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md index da7858075a..e63a4a09d8 100644 --- a/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md +++ b/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md @@ -58,8 +58,8 @@ Se seu aplicativo já está publicado e você é um editor verificado, você pod Para publicar um aplicativo pago (ou um aplicativo que ofereça um plano pago), você também deve atender aos seguintes requisitos: -- {% data variables.product.prodname_github_apps %} should have a minimum of 100 installations. -- {% data variables.product.prodname_oauth_apps %} should have a minimum of 200 users. +- {% data variables.product.prodname_github_apps %} deve ter no mínimo 100 instalações. +- {% data variables.product.prodname_oauth_apps %} deve ter no mínimo 200 usuários. - Todos os aplicativos pagos devem lidar com eventos de compra de {% data variables.product.prodname_marketplace %} para novas compras, atualizações, downgrades, cancelamentos e testes grátis. Para obter mais informações, consulte "[Requisitos de cobrança para aplicativos pagos](#billing-requirements-for-paid-apps)" abaixo. Quando estiver pronto para publicar o aplicativo em {% data variables.product.prodname_marketplace %}, você deverá solicitar a verificação para o anúncio do aplicativo. diff --git a/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-transactions-for-your-listing.md b/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-transactions-for-your-listing.md index 9cb19ce819..8d0a2db6e8 100644 --- a/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-transactions-for-your-listing.md +++ b/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-transactions-for-your-listing.md @@ -31,8 +31,8 @@ Você pode visualizar ou fazer o download dos dados de transação para acompanh * **amount_in_centes:** O valor da transação em centavos. Quando um valor for inferior ao montante do plano, o usuário fez a atualização e o novo plano será rateado. Um valor zero indica que o usuário cancelou seu plano. * **renewal_frequency:** A frequência de renovação da assinatura, seja `Mensal` ou `Anual`. * **The following place_listing_plan_id:** O `id` do plano de assinatura. -* **region:** The name of the region present in billing address. -* **postal_code:** The postal code value present in billing address. +* **region:** O nome da região presente no endereço de cobrança. +* **postal_code:** O código postal presente no endereço de cobrança. ![Perspectivas do Marketplace](/assets/images/marketplace/marketplace_transactions.png) diff --git a/translations/pt-BR/content/developers/github-marketplace/github-marketplace-overview/about-github-marketplace.md b/translations/pt-BR/content/developers/github-marketplace/github-marketplace-overview/about-github-marketplace.md index 5845941841..7e9345f868 100644 --- a/translations/pt-BR/content/developers/github-marketplace/github-marketplace-overview/about-github-marketplace.md +++ b/translations/pt-BR/content/developers/github-marketplace/github-marketplace-overview/about-github-marketplace.md @@ -31,11 +31,11 @@ Para publicar aplicativos com planos grátis, você só precisa atender aos requ ### Novo nos aplicativos? -If you're interested in creating an app for {% data variables.product.prodname_marketplace %}, but you're new to {% data variables.product.prodname_github_apps %} or {% data variables.product.prodname_oauth_apps %}, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" or "[Building {% data variables.product.prodname_oauth_apps %}](/developers/apps/building-oauth-apps)." +Se você estiver interessado em criar um aplicativo para {% data variables.product.prodname_marketplace %}, mas você é novo em {% data variables.product.prodname_github_apps %} ou {% data variables.product.prodname_oauth_apps %}, consulte "[Criando {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" ou "[Criando {% data variables.product.prodname_oauth_apps %}](/developers/apps/building-oauth-apps)." ### {% data variables.product.prodname_github_apps %} vs. {% data variables.product.prodname_oauth_apps %} -{% data reusables.marketplace.github_apps_preferred %}, although you can list both OAuth and {% data variables.product.prodname_github_apps %} in {% data variables.product.prodname_marketplace %}. For more information, see "[Differences between {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}](/apps/differences-between-apps/)" and "[Migrating {% data variables.product.prodname_oauth_apps %} to {% data variables.product.prodname_github_apps %}](/apps/migrating-oauth-apps-to-github-apps/)." +{% data reusables.marketplace.github_apps_preferred %}, embora você possa anunciar OAuth e {% data variables.product.prodname_github_apps %} em {% data variables.product.prodname_marketplace %}. Para obter mais informações, consulte "[Diferenças entre {% data variables.product.prodname_github_apps %} e {% data variables.product.prodname_oauth_apps %}](/apps/differences-between-apps/)" e "[Fazendo a migração de {% data variables.product.prodname_oauth_apps %} para {% data variables.product.prodname_github_apps %}](/apps/migrating-oauth-apps-to-github-apps/)". ## Publicar um aplicativo na visão geral de {% data variables.product.prodname_marketplace %} diff --git a/translations/pt-BR/content/developers/github-marketplace/github-marketplace-overview/about-marketplace-badges.md b/translations/pt-BR/content/developers/github-marketplace/github-marketplace-overview/about-marketplace-badges.md index 3a7710a573..4ab0afa1c9 100644 --- a/translations/pt-BR/content/developers/github-marketplace/github-marketplace-overview/about-marketplace-badges.md +++ b/translations/pt-BR/content/developers/github-marketplace/github-marketplace-overview/about-marketplace-badges.md @@ -30,7 +30,7 @@ Alguns aplicativos em {% data variables.product.prodname_marketplace %} têm o s Para obter mais informações sobre os requisitos para a listagem de um aplicativo em {% data variables.product.prodname_marketplace %}, consulte "[Requisitos para listar um aplicativo em {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)". -Para obter informações sobre como encontrar aplicativos para usar, consulte "[Pesquisar {% data variables.product.prodname_marketplace %}](/github/searching-for-information-on-github/searching-github-marketplace)". +Para obter informações sobre como encontrar aplicativos para usar, consulte "[Pesquisar {% data variables.product.prodname_marketplace %}](/search-github/searching-on-github/searching-github-marketplace)". ## Para ações no GitHub diff --git a/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/receiving-payment-for-app-purchases.md b/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/receiving-payment-for-app-purchases.md index 99591eed2c..733ee9af81 100644 --- a/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/receiving-payment-for-app-purchases.md +++ b/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/receiving-payment-for-app-purchases.md @@ -17,7 +17,7 @@ shortTitle: Receber pagamentos Depois que o seu anúncio de {% data variables.product.prodname_marketplace %} para um aplicativo com um plano pago for criado e aprovado, você fornecerá detalhes de pagamento para {% data variables.product.product_name %} como parte do processo de integração financeira. -Once your revenue reaches a minimum of 500 US dollars for the month, you'll receive an electronic payment from {% data variables.product.company_short %}. Este será o rendimento das transações no mercado menos o valor cobrado por {% data variables.product.company_short %} para cobrir seus custos administrativos. +Quando sua receita atingir o mínimo de US$ 500 dólares no mês, você receberá um pagamento eletrônico de {% data variables.product.company_short %}. Este será o rendimento das transações no mercado menos o valor cobrado por {% data variables.product.company_short %} para cobrir seus custos administrativos. Para transações feitas antes de 1 de janeiro de 2021, {% data variables.product.company_short %} irá reter 25% da renda da transação. Para transações feitas após essa data, apenas 5% é será retido por {% data variables.product.company_short %}. Esta alteração irá refletir-se nos pagamentos recebidos a partir do final de Janeiro de 2021. diff --git a/translations/pt-BR/content/developers/overview/index.md b/translations/pt-BR/content/developers/overview/index.md index e04925ad35..d7117e2d07 100644 --- a/translations/pt-BR/content/developers/overview/index.md +++ b/translations/pt-BR/content/developers/overview/index.md @@ -8,7 +8,6 @@ versions: children: - /about-githubs-apis - /managing-deploy-keys - - /viewing-deployment-history - /using-ssh-agent-forwarding - /secret-scanning-partner-program - /replacing-github-services diff --git a/translations/pt-BR/content/developers/overview/replacing-github-services.md b/translations/pt-BR/content/developers/overview/replacing-github-services.md index 5c7a8f67fc..c948f1b4d1 100644 --- a/translations/pt-BR/content/developers/overview/replacing-github-services.md +++ b/translations/pt-BR/content/developers/overview/replacing-github-services.md @@ -70,4 +70,4 @@ A versão 2.17 do {% data variables.product.prodname_ghe_server %} será a prime Como uma visão geral de alto nível, o processo de migração normalmente envolve: - Identificar como e onde seu produto está usando o GitHub Services. - Identificar os eventos de webhook correspondentes que você precisa configurar para mover para webhooks simples. - - Implementing the design using either [{% data variables.product.prodname_oauth_apps %}](/apps/building-oauth-apps/) or [{% data variables.product.prodname_github_apps %}. {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/) are preferred. To learn more about why {% data variables.product.prodname_github_apps %} are preferred, see "[Reasons for switching to {% data variables.product.prodname_github_apps %}](/apps/migrating-oauth-apps-to-github-apps/#reasons-for-switching-to-github-apps)." + - Implementando o design usando [{% data variables.product.prodname_oauth_apps %}](/apps/building-oauth-apps/) ou [{% data variables.product.prodname_github_apps %}. {% data variables.product.prodname_github_apps %}s](/apps/building-github-apps/) são preferidos. Para saber mais sobre o porquê de {% data variables.product.prodname_github_apps %} ser preferido, consulte "[Motivos para mudar para {% data variables.product.prodname_github_apps %}](/apps/migrating-oauth-apps-to-github-apps/#reasons-for-switching-to-github-apps)". diff --git a/translations/pt-BR/content/developers/webhooks-and-events/webhooks/about-webhooks.md b/translations/pt-BR/content/developers/webhooks-and-events/webhooks/about-webhooks.md index 934b89b30d..acf437e382 100644 --- a/translations/pt-BR/content/developers/webhooks-and-events/webhooks/about-webhooks.md +++ b/translations/pt-BR/content/developers/webhooks-and-events/webhooks/about-webhooks.md @@ -12,7 +12,7 @@ topics: - Webhooks --- -Webhooks allow you to build or set up integrations, such as [{% data variables.product.prodname_github_apps %}](/apps/building-github-apps/) or [{% data variables.product.prodname_oauth_apps %}](/apps/building-oauth-apps/), which subscribe to certain events on GitHub.com. Quando um desses eventos é acionado, enviaremos uma carga de POST por HTTP POST para a URL de configuração do webhook. Os webhooks podem ser usados para atualizar um rastreador de problemas externo, acionar criações de CI, atualizar um espelho de backup, ou até mesmo fazer uma implantação no seu servidor de produção. A sua imaginação é o único limite. +Os webhooks permitem que você construa ou configure integrações, como [{% data variables.product.prodname_github_apps %}](/apps/building-github-apps/) ou [{% data variables.product.prodname_oauth_apps %}](/apps/building-oauth-apps/), que assinam certos eventos no GitHub.com. Quando um desses eventos é acionado, enviaremos uma carga de POST por HTTP POST para a URL de configuração do webhook. Os webhooks podem ser usados para atualizar um rastreador de problemas externo, acionar criações de CI, atualizar um espelho de backup, ou até mesmo fazer uma implantação no seu servidor de produção. A sua imaginação é o único limite. Os webhooks podem ser instalados em{% ifversion ghes or ghae %} [{% data variables.product.prodname_enterprise %}](/rest/reference/enterprise-admin#global-webhooks/),{% endif %} uma [organização][org-hooks], em um repositório[específico][repo-hooks] ou em {% data variables.product.prodname_github_app %}. Uma vez instalado, o webhook será enviado cada vez que ocorrer um ou mais eventos assinados. 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 ea077afaf1..d7b62bde4c 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 @@ -103,21 +103,21 @@ Além disso, o `User-Agent` para as solicitações terá o prefixo `GitHub-Hooks {% ifversion fpt or ghes > 3.2 or ghae-next %} ## branch_protection_rule -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)." +Atividade relacionada a uma regra de proteção do branch. Para obter mais informações, consulte[Sobre as regras de proteção do branch](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#about-branch-protection-rules)". ### Disponibilidade - Webhooks do repositório - Webhooks da organização -- {% data variables.product.prodname_github_apps %} with at least `read-only` access on repositories administration +- {% data variables.product.prodname_github_apps %} com pelo menos acesso `somente leitura` na administração de repositórios ### Objeto da carga do webhook -| Tecla | Tipo | Descrição | -| ------------ | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Ação` | `string` | A ação realizada. Pode ser `criado`, `editado` ou `excluído`. | -| `rule` | `objeto` | 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. | -| `alterações` | `objeto` | If the action was `edited`, the changes to the rule. | +| Tecla | Tipo | Descrição | +| ------------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `Ação` | `string` | A ação realizada. Pode ser `criado`, `editado` ou `excluído`. | +| `rule` | `objeto` | A regra de proteção do branch. Inclui um `nome` e todas as [configurações de proteção de branch](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#about-branch-protection-settings) aplicadas a branches que correspondem ao nome. As configurações binárias são booleanas. As configurações de multi-nível tem um dos valores a seguir:`off`, `non_admins` ou `everyone`. As listas do criador e da criação são matrizes de strings. | +| `alterações` | `objeto` | Se a ação foi `editada`, as alterações para a regra. | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.sender_desc %} @@ -136,7 +136,7 @@ Activity related to a branch protection rule. For more information, see "[About - Os webhooks de repositório só recebem cargas para os tipos de evento `criados` e `concluídos` em um repositório - Os webhooks da organização só recebem cargas para os tipos de eventos `criados` e `concluídos` nos repositórios -- {% 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. O aplicativo deve ter a permissão `checks:write` para receber os tipos de eventos `solicitados` e `requested_action`. As cargas do tipo de evento `solicitadas` e `requested_action` são enviadas apenas para o {% data variables.product.prodname_github_app %} que está sendo solicitado. {% data variables.product.prodname_github_apps %} with the `checks:write` are automatically subscribed to this webhook event. +- {% data variables.product.prodname_github_apps %} com a permissão `checks:read` recebem cargas para os tipos de evento `criados` e `concluídos` que ocorrem no repositório onde o aplicativo está instalado. O aplicativo deve ter a permissão `checks:write` para receber os tipos de eventos `solicitados` e `requested_action`. As cargas do tipo de evento `solicitadas` e `requested_action` são enviadas apenas para o {% data variables.product.prodname_github_app %} que está sendo solicitado. {% data variables.product.prodname_github_apps %} com `checks:write` são automaticamente inscritos neste evento webhook. ### Objeto da carga do webhook @@ -160,7 +160,7 @@ Activity related to a branch protection rule. For more information, see "[About - Os webhooks de repositório só recebem cargas para os tipos de evento `concluídos` em um repositório - Os webhooks da organização só recebem cargas para os tipos de eventos `concluídos` nos repositórios -- {% 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. O aplicativo deve ter a permissão `checks:write` para receber os tipos de eventos `solicitados` e `ressolicitados.`. As cargas de evento `solicitadas` e `ressolicitadas` são enviadas apenas para {% data variables.product.prodname_github_app %} que está sendo solicitado. {% data variables.product.prodname_github_apps %} with the `checks:write` are automatically subscribed to this webhook event. +- {% data variables.product.prodname_github_apps %} com a permissão `checks:read` recebem cargas para os tipos de evento `criados` e `concluídos` que ocorrem no repositório onde o aplicativo está instalado. O aplicativo deve ter a permissão `checks:write` para receber os tipos de eventos `solicitados` e `ressolicitados.`. As cargas de evento `solicitadas` e `ressolicitadas` são enviadas apenas para {% data variables.product.prodname_github_app %} que está sendo solicitado. {% data variables.product.prodname_github_apps %} com `checks:write` são automaticamente inscritos neste evento webhook. ### Objeto da carga do webhook @@ -182,7 +182,7 @@ Os {% data variables.product.prodname_github_app %}s com a permissão `security_ - Webhooks do repositório - Webhooks da organização -- {% data variables.product.prodname_github_apps %} with the `security_events :read` permission +- {% data variables.product.prodname_github_apps %} com a permissão de `security_events :read` ### Objeto da carga do webhook @@ -190,7 +190,7 @@ Os {% data variables.product.prodname_github_app %}s com a permissão `security_ {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} -    remetente`| objeto` | Se a de ação ` for reopened_by_user` ou `closed_by_user`, o objeto `remetente` será o usuário que ativou o evento. O objeto do `remetente` é {% ifversion fpt %}`github` {% elsif ghes > 3.0 %}`github-enterprise` {% else %}vazio {% endif %}para todas as outras ações. +remetente`| objeto` | Se a de ação ` for reopened_by_user` ou `closed_by_user`, o objeto `remetente` será o usuário que ativou o evento. O objeto `remetente` é {% ifversion fpt %}`github`{% elsif ghes > 3.0 or ghae-next %}`github-enterprise`{% else %}vazio{% endif %} para todas as outras ações. ### Exemplo de carga de webhook @@ -204,7 +204,7 @@ Os {% data variables.product.prodname_github_app %}s com a permissão `security_ - Webhooks do repositório - Webhooks da organização -- {% data variables.product.prodname_github_apps %} with the `contents` permission +- {% data variables.product.prodname_github_apps %} com a permissão `conteúdo` ### Objeto da carga do webhook @@ -226,7 +226,7 @@ Os eventos de webhook são acionados com base na especificidade do domínio que ### Disponibilidade -- {% data variables.product.prodname_github_apps %} with the `content_references:write` permission +- {% data variables.product.prodname_github_apps %} com a permissão `content_references:write` ### Exemplo de carga de webhook @@ -246,7 +246,7 @@ Os eventos de webhook são acionados com base na especificidade do domínio que - Webhooks do repositório - Webhooks da organização -- {% data variables.product.prodname_github_apps %} with the `contents` permission +- {% data variables.product.prodname_github_apps %} com a permissão `conteúdo` ### Objeto da carga do webhook @@ -275,7 +275,7 @@ Os eventos de webhook são acionados com base na especificidade do domínio que - Webhooks do repositório - Webhooks da organização -- {% data variables.product.prodname_github_apps %} with the `contents` permission +- {% data variables.product.prodname_github_apps %} com a permissão `conteúdo` ### Objeto da carga do webhook @@ -318,7 +318,7 @@ Os eventos de webhook são acionados com base na especificidade do domínio que - Webhooks do repositório - Webhooks da organização -- {% data variables.product.prodname_github_apps %} with the `deployments` permission +- {% data variables.product.prodname_github_apps %} com a permissão `implantações` ### Objeto da carga do webhook @@ -343,7 +343,7 @@ Os eventos de webhook são acionados com base na especificidade do domínio que - Webhooks do repositório - Webhooks da organização -- {% data variables.product.prodname_github_apps %} with the `deployments` permission +- {% data variables.product.prodname_github_apps %} com a permissão `implantações` ### Objeto da carga do webhook @@ -374,7 +374,7 @@ Atividade relacionada a uma discussão. Para obter mais informações, consulte - Webhooks do repositório - Webhooks da organização -- {% data variables.product.prodname_github_apps %} with the `discussions` permission +- {% data variables.product.prodname_github_apps %} com a permissão `discussões` ### Objeto da carga do webhook @@ -400,7 +400,7 @@ Atividade relacionada a um comentário em uma discussão. Para obter mais inform - Webhooks do repositório - Webhooks da organização -- {% data variables.product.prodname_github_apps %} with the `discussions` permission +- {% data variables.product.prodname_github_apps %} com a permissão `discussões` ### Objeto da carga do webhook @@ -448,7 +448,7 @@ Atividade relacionada a um comentário em uma discussão. Para obter mais inform - Webhooks do repositório - Webhooks da organização -- {% data variables.product.prodname_github_apps %} with the `contents` permission +- {% data variables.product.prodname_github_apps %} com a permissão `conteúdo` ### Objeto da carga do webhook @@ -466,7 +466,7 @@ Atividade relacionada a um comentário em uma discussão. Para obter mais inform Este evento ocorre quando alguém revoga a autorização de um {% data variables.product.prodname_github_app %}. Um {% data variables.product.prodname_github_app %} recebe este webhook por padrão e não pode cancelar a assinatura deste evento. -{% 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/)." +{% data reusables.webhooks.authorization_event %} Para obter informações sobre solicitações de usuário para servidor, que exigem autorização do {% data variables.product.prodname_github_app %}, consulte "[Identificando e autorizando usuários para {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)". ### Disponibilidade @@ -491,7 +491,7 @@ Este evento ocorre quando alguém revoga a autorização de um {% data variables - Webhooks do repositório - Webhooks da organização -- {% data variables.product.prodname_github_apps %} with the `contents` permission +- {% data variables.product.prodname_github_apps %} com a permissão `conteúdo` ### Objeto da carga do webhook @@ -549,7 +549,7 @@ Este evento ocorre quando alguém revoga a autorização de um {% data variables - Webhooks do repositório - Webhooks da organização -- {% data variables.product.prodname_github_apps %} with the `issues` permission +- {% data variables.product.prodname_github_apps %} com a permissão `problemas` ### Objeto da carga do webhook @@ -572,7 +572,7 @@ Este evento ocorre quando alguém revoga a autorização de um {% data variables - Webhooks do repositório - Webhooks da organização -- {% data variables.product.prodname_github_apps %} with the `issues` permission +- {% data variables.product.prodname_github_apps %} com a permissão `problemas` ### Objeto da carga do webhook @@ -595,7 +595,7 @@ Este evento ocorre quando alguém revoga a autorização de um {% data variables - Webhooks do repositório - Webhooks da organização -- {% data variables.product.prodname_github_apps %} with the `metadata` permission +- {% data variables.product.prodname_github_apps %} com a permissão `metadados` ### Objeto da carga do webhook @@ -646,7 +646,7 @@ Para obter uma descrição detalhada desta carga e da carga para cada tipo de `a - Webhooks do repositório - Webhooks da organização -- {% data variables.product.prodname_github_apps %} with the `members` permission +- {% data variables.product.prodname_github_apps %} com a permissão `integrantes` ### Objeto da carga do webhook @@ -668,7 +668,7 @@ Para obter uma descrição detalhada desta carga e da carga para cada tipo de `a ### Disponibilidade - Webhooks da organização -- {% data variables.product.prodname_github_apps %} with the `members` permission +- {% data variables.product.prodname_github_apps %} com a permissão `integrantes` ### Objeto da carga do webhook @@ -713,7 +713,7 @@ O webhook em que este evento está configurado em foi excluído. Este evento só - Webhooks do repositório - Webhooks da organização -- {% data variables.product.prodname_github_apps %} with the `pull_requests` permission +- {% data variables.product.prodname_github_apps %} com a permissão `pull_requests` ### Objeto da carga do webhook @@ -736,7 +736,7 @@ O webhook em que este evento está configurado em foi excluído. Este evento só {% ifversion ghes or ghae %} - Os webhooks do GitHub Enterprise recebem apenas eventos `criados` e `excluídos`. Para mais informações, consulte "[Webhooks globais](/rest/reference/enterprise-admin#global-webhooks/).{% endif %} - Os webhooks da organização recebem apenas os eventos `excluídos`, `adicionados`, `removidos`, `renomeado` e `convidados` -- {% data variables.product.prodname_github_apps %} with the `members` permission +- {% data variables.product.prodname_github_apps %} com a permissão `integrantes` ### Objeto da carga do webhook @@ -762,7 +762,7 @@ O webhook em que este evento está configurado em foi excluído. Este evento só ### Disponibilidade - Webhooks da organização -- {% data variables.product.prodname_github_apps %} with the `organization_administration` permission +- {% data variables.product.prodname_github_apps %} com a permissão `organization_administration` ### Objeto da carga do webhook @@ -811,7 +811,7 @@ Atividade relacionada a {% data variables.product.prodname_registry %}. {% data - Webhooks do repositório - Webhooks da organização -- {% data variables.product.prodname_github_apps %} with the `pages` permission +- {% data variables.product.prodname_github_apps %} com a permissão `pages` ### Objeto da carga do webhook @@ -836,7 +836,7 @@ Atividade relacionada a {% data variables.product.prodname_registry %}. {% data - Webhooks do repositório - Webhooks da organização -- {% data variables.product.prodname_github_apps %} receive a ping event with an `app_id` used to register the app +- {% data variables.product.prodname_github_apps %} recebe um evento de ping com um `app_id` usado para registrar o aplicativo ### Objeto da carga do webhook @@ -862,7 +862,7 @@ Atividade relacionada a {% data variables.product.prodname_registry %}. {% data - Webhooks do repositório - Webhooks da organização -- {% data variables.product.prodname_github_apps %} with the `repository_projects` or `organization_projects` permission +- {% data variables.product.prodname_github_apps %} com a permissão `repository_projects` ou `organization_projects` ### Objeto da carga do webhook @@ -884,7 +884,7 @@ Atividade relacionada a {% data variables.product.prodname_registry %}. {% data - Webhooks do repositório - Webhooks da organização -- {% data variables.product.prodname_github_apps %} with the `repository_projects` or `organization_projects` permission +- {% data variables.product.prodname_github_apps %} com a permissão `repository_projects` ou `organization_projects` ### Objeto da carga do webhook @@ -906,7 +906,7 @@ Atividade relacionada a {% data variables.product.prodname_registry %}. {% data - Webhooks do repositório - Webhooks da organização -- {% data variables.product.prodname_github_apps %} with the `repository_projects` or `organization_projects` permission +- {% data variables.product.prodname_github_apps %} com a permissão `repository_projects` ou `organization_projects` ### Objeto da carga do webhook @@ -928,7 +928,7 @@ Atividade relacionada a {% data variables.product.prodname_registry %}. {% data - Webhooks do repositório - Webhooks da organização -- {% data variables.product.prodname_github_apps %} with the `metadata` permission +- {% data variables.product.prodname_github_apps %} com a permissão `metadados` ### Objeto da carga do webhook @@ -952,7 +952,7 @@ Atividade relacionada a {% data variables.product.prodname_registry %}. {% data - Webhooks do repositório - Webhooks da organização -- {% data variables.product.prodname_github_apps %} with the `pull_requests` permission +- {% data variables.product.prodname_github_apps %} com a permissão `pull_requests` ### Objeto da carga do webhook @@ -977,7 +977,7 @@ As entregas para eventos `review_requested` e `review_request_removed` terão um - Webhooks do repositório - Webhooks da organização -- {% data variables.product.prodname_github_apps %} with the `pull_requests` permission +- {% data variables.product.prodname_github_apps %} com a permissão `pull_requests` ### Objeto da carga do webhook @@ -999,7 +999,7 @@ As entregas para eventos `review_requested` e `review_request_removed` terão um - Webhooks do repositório - Webhooks da organização -- {% data variables.product.prodname_github_apps %} with the `pull_requests` permission +- {% data variables.product.prodname_github_apps %} com a permissão `pull_requests` ### Objeto da carga do webhook @@ -1028,28 +1028,33 @@ As entregas para eventos `review_requested` e `review_request_removed` terão um - Webhooks do repositório - Webhooks da organização -- {% data variables.product.prodname_github_apps %} with the `contents` permission +- {% data variables.product.prodname_github_apps %} com a permissão `conteúdo` ### Objeto da carga do webhook -| Tecla | Tipo | Descrição | -| -------------------------- | --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `ref` | `string` | O [`git ref completo`](/rest/reference/git#refs) que foi empurrado. Exemplo: `refs/heads/master`. | -| `antes` | `string` | O SHA do último commit em `ref` antes do push. | -| `depois` | `string` | O SHA do último commit no `ref` após o push. | -| `commits` | `array` | Um array de objetos de commit, que descreve os commits carregados. (O array inclui um máximo de 20 commits. Se necessário, você pode usar a [API de Commits](/rest/reference/repos#commits) para obter commits adicionais. Este limite é aplicado apenas aos eventos da linha do tempo e não é aplicado às entregas do webhook.) | -| `commits[][id]` | `string` | O SHA do commit. | -| `commits[][timestamp]` | `string` | O carimbo de tempo ISO 8601 do commit. | -| `commits[][message]` | `string` | A mensagem do commit. | -| `commits[][author]` | `objeto` | O autor do git do commit. | -| `commits[][author][name]` | `string` | O nome do autor do git. | -| `commits[][author][email]` | `string` | O endereço de e-mail do autor do git. | -| `commits[][url]` | `url` | URL que aponta para o recurso de commit de API. | -| `commits[][distinct]` | `boolean` | Se este compromisso é diferente de qualquer outro que tenha sido carregado anteriormente. | -| `commits[][added]` | `array` | Um array de arquivos adicionados no commit. | -| `commits[][modified]` | `array` | Um array de arquivos modificados pelo commit. | -| `commits[][removed]` | `array` | Um array de arquivos removidos no commit. | -| `pusher` | `objeto` | O usuário que fez o push dos commits. | +| Tecla | Tipo | Descrição | +| -------------------------- | --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `ref` | `string` | O [`git ref completo`](/rest/reference/git#refs) que foi empurrado. Exemplo: `refs/heads/main` ou `refs/tags/v3.14.1`. | +| `antes` | `string` | O SHA do último commit em `ref` antes do push. | +| `depois` | `string` | O SHA do último commit no `ref` após o push. | +| `created` | `boolean` | Se este push criou o `ref`. | +| `deleted` | `boolean` | Se este push excluiu o `ref`. | +| `forced` | `boolean` | Se este push foi um push forçado do `ref`. | +| `head_commit` | `objeto` | Para pushes em que `after` é ou aponta para um objeto de commit, uma representação expandida desse commit. Para pushes em que `after` refere-se a um objeto de tag anotada, uma representação expandida do commit apontada pela tag anotada. | +| `compare` | `string` | A URL que mostra as alterações na atualização deste `ref`, do commit `before` para o commit `after`. Para um `ref` recém-criado que é diretamente baseado no branch padrão, esta é a comparação entre o cabeçalho do branch padrão e o commit `after`. Caso contrário, isso mostra todos os commits até o commit `after`. | +| `commits` | `array` | Um array de objetos de commit, que descreve os commits carregados. (Os commits que sofreram push são todos commits incluídos no `compare` entre o commit `before` e o commit `after`.) O array inclui um máximo de 20 commits. Se necessário, você pode usar a [API de Commits](/rest/reference/repos#commits) para obter commits adicionais. Este limite é aplicado apenas aos eventos da linha do tempo e não é aplicado às entregas do webhook. | +| `commits[][id]` | `string` | O SHA do commit. | +| `commits[][timestamp]` | `string` | O carimbo de tempo ISO 8601 do commit. | +| `commits[][message]` | `string` | A mensagem do commit. | +| `commits[][author]` | `objeto` | O autor do git do commit. | +| `commits[][author][name]` | `string` | O nome do autor do git. | +| `commits[][author][email]` | `string` | O endereço de e-mail do autor do git. | +| `commits[][url]` | `url` | URL que aponta para o recurso de commit de API. | +| `commits[][distinct]` | `boolean` | Se este compromisso é diferente de qualquer outro que tenha sido carregado anteriormente. | +| `commits[][added]` | `array` | Um array de arquivos adicionados no commit. | +| `commits[][modified]` | `array` | Um array de arquivos modificados pelo commit. | +| `commits[][removed]` | `array` | Um array de arquivos removidos no commit. | +| `pusher` | `objeto` | O usuário que fez o push dos commits. | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} @@ -1067,7 +1072,7 @@ As entregas para eventos `review_requested` e `review_request_removed` terão um - Webhooks do repositório - Webhooks da organização -- {% data variables.product.prodname_github_apps %} with the `contents` permission +- {% data variables.product.prodname_github_apps %} com a permissão `conteúdo` ### Objeto da carga do webhook @@ -1089,7 +1094,7 @@ Este evento ocorre quando um {% data variables.product.prodname_github_app %} en ### Disponibilidade -- {% data variables.product.prodname_github_apps %} must have the `contents` permission to receive this webhook. +- {% data variables.product.prodname_github_apps %} deve ter a permissão do conteúdo `` para receber este webhook. ### Exemplo de carga de webhook @@ -1104,7 +1109,7 @@ Este evento ocorre quando um {% data variables.product.prodname_github_app %} en - Os webhooks do repositório recebem todos os tipos de eventos, exceto `excluído` - Webhooks da organização -- {% data variables.product.prodname_github_apps %} with the `metadata` permission receive all event types except `deleted` +- {% data variables.product.prodname_github_apps %} com a permissão de `metadados`, recebe todos os tipos de eventos, exceto `excluídos` ### Objeto da carga do webhook @@ -1173,7 +1178,7 @@ Este evento ocorre quando um {% data variables.product.prodname_github_app %} en - Webhooks do repositório - Webhooks da organização -- {% data variables.product.prodname_github_apps %} with the `secret_scanning_alerts:read` permission +- {% data variables.product.prodname_github_apps %} com a permissão `secret_scanning_alerts:read` ### Objeto da carga do webhook @@ -1196,7 +1201,7 @@ Atividade relacionada a uma consultora de segurança. Uma consultoria de seguran ### Disponibilidade -- {% data variables.product.prodname_github_apps %} with the `security_events` permission +- {% data variables.product.prodname_github_apps %} com a permissão `security_events` ### Objeto da carga do webhook @@ -1264,7 +1269,7 @@ Você só pode criar um webhook de patrocínio em {% data variables.product.prod - Webhooks do repositório - Webhooks da organização -- {% data variables.product.prodname_github_apps %} with the `statuses` permission +- {% data variables.product.prodname_github_apps %} com a permissão `status` ### Objeto da carga do webhook @@ -1292,7 +1297,7 @@ Você só pode criar um webhook de patrocínio em {% data variables.product.prod ### Disponibilidade - Webhooks da organização -- {% data variables.product.prodname_github_apps %} with the `members` permission +- {% data variables.product.prodname_github_apps %} com a permissão `integrantes` ### Objeto da carga do webhook @@ -1323,7 +1328,7 @@ Você só pode criar um webhook de patrocínio em {% data variables.product.prod - Webhooks do repositório - Webhooks da organização -- {% data variables.product.prodname_github_apps %} with the `members` permission +- {% data variables.product.prodname_github_apps %} com a permissão `integrantes` ### Objeto da carga do webhook @@ -1364,7 +1369,7 @@ O ator do evento é o [usuário](/rest/reference/users) que favoritou um reposit - Webhooks do repositório - Webhooks da organização -- {% data variables.product.prodname_github_apps %} with the `metadata` permission +- {% data variables.product.prodname_github_apps %} com a permissão `metadados` ### Objeto da carga do webhook @@ -1385,7 +1390,7 @@ Esse evento ocorre quando alguém aciona a execução de um fluxo de trabalho no ### Disponibilidade -- {% data variables.product.prodname_github_apps %} must have the `contents` permission to receive this webhook. +- {% data variables.product.prodname_github_apps %} deve ter a permissão do conteúdo `` para receber este webhook. ### Exemplo de carga de webhook @@ -1402,7 +1407,7 @@ Esse evento ocorre quando alguém aciona a execução de um fluxo de trabalho no - Webhooks do repositório - Webhooks da organização -- Enterprise webhooks +- Webhooks corporativos ### Objeto da carga do webhook @@ -1423,7 +1428,7 @@ Quando uma execução do fluxo de trabalho de {% data variables.product.prodname ### Disponibilidade -- {% data variables.product.prodname_github_apps %} with the `actions` or `contents` permissions. +- {% data variables.product.prodname_github_apps %} com as permissões `ações` ou `conteúdos`. ### Objeto da carga do webhook diff --git a/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md b/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md index ad5ed1ec4a..479b97899a 100644 --- a/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md +++ b/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md @@ -18,7 +18,7 @@ Com {% data variables.product.prodname_discussions %}, a comunidade para o seu p Você não precisa fechar uma discussão como você fecha um problema ou um pull request. -If a repository administrator or project maintainer enables {% data variables.product.prodname_discussions %} for a repository, anyone who visits the repository can create and participate in discussions for the repository. Os administradores de repositório e mantenedores de projetos podem gerenciar as discussões e categorias de discussão em um repositório e fixar discussões para aumentar a visibilidade da discussão. Os moderadores e colaboradores podem marcar comentários como respostas, travar discussões e converter problemas em discussões. Para obter mais informações, consulte "[Níveis de permissão de repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)". +Se um administrador de repositório ou mantenedor do projeto habilitar {% data variables.product.prodname_discussions %} para um repositório, qualquer pessoa que visitar o repositório poderá criar e participar de discussões do repositório. Os administradores de repositório e mantenedores de projetos podem gerenciar as discussões e categorias de discussão em um repositório e fixar discussões para aumentar a visibilidade da discussão. Os moderadores e colaboradores podem marcar comentários como respostas, travar discussões e converter problemas em discussões. Para obter mais informações, consulte "[Níveis de permissão de repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)". Para obter mais informações sobre o gerenciamento de discussões para o repositório, consulte "[Gerenciar discussões no seu repositório](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)". @@ -36,7 +36,7 @@ Para obter mais informações, consulte "[Gerenciar categorias para discussões {% data reusables.discussions.you-can-label-discussions %} -## Best practices for {% data variables.product.prodname_discussions %} +## Práticas recomendadas para {% data variables.product.prodname_discussions %} Como integrante ou mantenedor da comunidade, inicie uma discussão para fazer uma pergunta ou discutir informações que afetem a comunidade. Para obter mais informações, consulte "[Colaborar com mantenedores usando as discussões](/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions)". @@ -53,7 +53,7 @@ Você pode compartilhar seus comentários sobre {% data variables.product.prodna ## Leia mais - "[Sobre escrita e formatação em {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)" -- "[Pesquisar discussões](/github/searching-for-information-on-github/searching-discussions)" +- "[Pesquisar discussões](/search-github/searching-on-github/searching-discussions)" - "[Sobre notificações](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" - "[Moderar comentários e conversas](/communities/moderating-comments-and-conversations)" - "[Mantendo sua segurança no {% data variables.product.prodname_dotcom %}](/communities/maintaining-your-safety-on-github)" diff --git a/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md b/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md index d920fd77b8..4d9e0dc363 100644 --- a/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md +++ b/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md @@ -2,13 +2,13 @@ title: Colaboração com mantenedores usando as discussões shortTitle: Colaborando com mantenedores intro: 'Você pode contribuir para objetivos, planos, saúde e comunidade para um projeto em {% data variables.product.product_name %} comunicando-se com os mantenedores do projeto em uma discussão.' -permissions: People with read permissions to a repository can start and participate in discussions in the repository. +permissions: 'People with read access to a repository can start and participate in discussions in the repository. {% data reusables.enterprise-accounts.emu-permission-interact %}' versions: fpt: '*' --- -## About collaboration with maintainers using {% data variables.product.prodname_discussions %} +## Sobre colaboração com mantenedores que usam {% data variables.product.prodname_discussions %} {% data reusables.discussions.about-discussions %} Se você usar ou contribuir para um projeto, você pode iniciar uma discussão para fazer sugestões e envolver-se com mantenedores e integrantes da comunidade sobre seus planos, dúvidas, ideias e feedback. Para obter mais informações, consulte "[Sobre discussões](/discussions/collaborating-with-your-community-using-discussions/about-discussions)". @@ -24,7 +24,7 @@ Para obter mais informações sobre a participação em discussões, consulte "[ ## Pré-requisitos -To collaborate with maintainers in discussions, a repository administrator or project maintainer must enable {% data variables.product.prodname_discussions %} for the repository. For more information, see "[Enabling or disabling {% data variables.product.prodname_discussions %} for a repository](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)." +Para colaborar com mantenedores em discussões, um administrador ou mantenedor do projeto deverá habilitar {% data variables.product.prodname_discussions %} para o repositório. Para obter mais informações, consulte "[Habilitando ou desabilitando {% data variables.product.prodname_discussions %} para um repositório](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)". ## Iniciar uma discussão @@ -32,7 +32,7 @@ To collaborate with maintainers in discussions, a repository administrator or pr ## Filtrar a lista de discussões -É possível pesquisar discussões e filtrar a lista de discussões em um repositório. Para obter mais informações, consulte "[Pesquisar discussões](/github/searching-for-information-on-github/searching-discussions)". +É possível pesquisar discussões e filtrar a lista de discussões em um repositório. Para obter mais informações, consulte "[Pesquisar discussões](/search-github/searching-on-github/searching-discussions)". {% data reusables.repositories.navigate-to-repo %} {% data reusables.discussions.discussions-tab %} diff --git a/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md b/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md index 4c5f3a0b70..47cd6473ca 100644 --- a/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md +++ b/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md @@ -1,7 +1,7 @@ --- title: Participando de uma discussão intro: 'Você pode conversar com a comunidade e mantenedores em um fórum do repositório para um projeto em {% data variables.product.product_name %}.' -permissions: People with read permissions to a repository can participate in discussions in the repository. +permissions: 'People with read access to a repository can participate in discussions in the repository. {% data reusables.enterprise-accounts.emu-permission-interact %}' versions: fpt: '*' shortTitle: Participar da discussão @@ -18,7 +18,7 @@ Você pode bloquear usuários e reportar conteúdo disruptivo para manter um amb ## Pré-requisitos -{% data variables.product.prodname_discussions %} must be enabled for the repository for you to participate in a discussion in the repository. For more information, see "[Enabling or disabling {% data variables.product.prodname_discussions %} for a repository](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)." +{% data variables.product.prodname_discussions %} deve estar habilitado para o repositório para que você participe de uma discussão no repositório. Para obter mais informações, consulte "[Habilitando ou desabilitando {% data variables.product.prodname_discussions %} para um repositório](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)". ## Criar uma discussão diff --git a/translations/pt-BR/content/discussions/guides/best-practices-for-community-conversations-on-github.md b/translations/pt-BR/content/discussions/guides/best-practices-for-community-conversations-on-github.md index a47c6486c2..bd79ce5276 100644 --- a/translations/pt-BR/content/discussions/guides/best-practices-for-community-conversations-on-github.md +++ b/translations/pt-BR/content/discussions/guides/best-practices-for-community-conversations-on-github.md @@ -1,7 +1,7 @@ --- title: Práticas recomendadas para conversas comunitárias no GitHub shortTitle: Práticas recomendadas para conversas comunitárias -intro: 'You can use discussions to brainstorm with your team, and eventually move the conversation to an issue when you are ready to scope out the work.' +intro: 'Você pode usar discussões para levantar hipóteses com a sua equipe e, por fim, transferir a conversa para um problema quando você estiver pronto para definir o escopo do trabalho.' versions: fpt: '*' --- @@ -21,7 +21,7 @@ Para mais informações sobre como abrir um problema e fazer referências cruzad Você pode criar e participar de discussões, problemas e pull requests, dependendo do tipo de conversa que você gostaria de ter. -Você pode usar {% data variables.product.prodname_discussions %} para discutir o panorama geral, levantamento de hipóteses e desenvolver detalhes específicos de um projeto antes de vinculá-lo a um problema, que poderá ter o escopo definido. {% data variables.product.prodname_discussions %} is useful for teams if: +Você pode usar {% data variables.product.prodname_discussions %} para discutir o panorama geral, levantamento de hipóteses e desenvolver detalhes específicos de um projeto antes de vinculá-lo a um problema, que poderá ter o escopo definido. {% data variables.product.prodname_discussions %} é útil para equipes se: - Você está na fase de descoberta de um projeto e ainda está aprendendo qual diretor sua equipe quer acessar - Você deseja coletar comentários de uma comunidade mais ampla sobre um projeto - Você deseja manter correções de erros, solicitações de recursos e conversas gerais separadas diff --git a/translations/pt-BR/content/discussions/guides/finding-discussions-across-multiple-repositories.md b/translations/pt-BR/content/discussions/guides/finding-discussions-across-multiple-repositories.md index ef411884a0..32b4635bd8 100644 --- a/translations/pt-BR/content/discussions/guides/finding-discussions-across-multiple-repositories.md +++ b/translations/pt-BR/content/discussions/guides/finding-discussions-across-multiple-repositories.md @@ -15,6 +15,6 @@ shortTitle: Encontrar discussões ## Leia mais -- "[Pesquisar discussões](/github/searching-for-information-on-github/searching-discussions)" +- "[Pesquisar discussões](/search-github/searching-on-github/searching-discussions)" - "[Sobre discussões](/discussions/collaborating-with-your-community-using-discussions/about-discussions)" - "[Gerenciar discussões para a sua comunidade](/discussions/managing-discussions-for-your-community)" diff --git a/translations/pt-BR/content/discussions/guides/granting-higher-permissions-to-top-contributors.md b/translations/pt-BR/content/discussions/guides/granting-higher-permissions-to-top-contributors.md index 1f3897e246..ab2a08c3cf 100644 --- a/translations/pt-BR/content/discussions/guides/granting-higher-permissions-to-top-contributors.md +++ b/translations/pt-BR/content/discussions/guides/granting-higher-permissions-to-top-contributors.md @@ -11,13 +11,13 @@ shortTitle: Conceder permissões superiores Os contribuidores mais úteis dos últimos 30 dias são destacados no painel de {% data variables.product.prodname_discussions %} baseado em quantos comentários foram marcados como respostas de outros integrantes da comunidade. Contribuidores úteis podem ajudar a conduzir uma comunidade saudável e moderada e guiar o espaço da comunidade, além de mantenedores. -## Step 1: Audit your {% data variables.product.prodname_discussions %} top contributors +## Etapa 1: Audite os seus melhores contribuidores de {% data variables.product.prodname_discussions %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.discussions.discussions-tab %} 1. Compare a lista de contribuidores com suas permissões de acesso para ver quem se qualifica para moderar a discussão. -## Step 2: Review permission levels for {% data variables.product.prodname_discussions %} +## Etapa 2: Reveja os níveis de permissão para {% data variables.product.prodname_discussions %} Pessoas com permissões de triagem para um repositório podem ajudar a moderar as discussões de um projeto marcando comentários como respostas, bloqueando discussões que já não são úteis ou prejudicam a comunidade e convertendo os problemas em discussões quando uma ideia ainda está nos primeiros estágios de desenvolvimento. Para obter mais informações, consulte "[Moderação de discussões](/discussions/managing-discussions-for-your-community/moderating-discussions)". diff --git a/translations/pt-BR/content/discussions/managing-discussions-for-your-community/index.md b/translations/pt-BR/content/discussions/managing-discussions-for-your-community/index.md index ae226f5882..9f5c75fe80 100644 --- a/translations/pt-BR/content/discussions/managing-discussions-for-your-community/index.md +++ b/translations/pt-BR/content/discussions/managing-discussions-for-your-community/index.md @@ -1,7 +1,7 @@ --- title: Gerenciando discussões para sua comunidade shortTitle: Gerenciando discussões -intro: 'You can enable and configure {% data variables.product.prodname_discussions %} for your repository, and you can use tools on {% data variables.product.product_name %} to moderate conversations among community members.' +intro: 'Você pode habilitar e configurar {% data variables.product.prodname_discussions %} para o seu repositório e você pode usar ferramentas em {% data variables.product.product_name %} para moderar conversas entre os membros da comunidade.' versions: fpt: '*' children: diff --git a/translations/pt-BR/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md b/translations/pt-BR/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md index 344abe1226..abff3421dd 100644 --- a/translations/pt-BR/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md +++ b/translations/pt-BR/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md @@ -16,7 +16,7 @@ Os proprietários da organização podem escolher as permissões necessárias pa Como mantenedor de discussões, você pode criar recursos da comunidade para incentivar discussões alinhadas com o objetivo geral do projeto e manter um fórum aberto amigável para os colaboradores. Criar um código de conduta ou diretrizes de contribuição para os colaboradores a seguir ajudará a facilitar um fórum colaborativo e produtivo. Para obter mais informações sobre como criar recursos da comunidade, consulte "[Adicionar um código de conduta ao seu projeto](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)" e "[Diretrizes de configuração para contribuidores do repositório](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)". -When a discussion yields an idea or bug that is ready to be worked on, you can create a new issue from a discussion. Para obter mais informações, consulte "[Criar um problema](/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-discussion)". +Quando uma discussão fornece uma ideia ou um erro que está pronto para ser trabalhado, você pode criar um novo problema a partir de uma discussão. Para obter mais informações, consulte "[Criar um problema](/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-discussion)". Para obter mais informações sobre como facilitar uma discussão saudável, consulte "[Moderar comentários e conversas](/communities/moderating-comments-and-conversations)". @@ -24,7 +24,7 @@ Para obter mais informações sobre como facilitar uma discussão saudável, con ## Pré-requisitos -To manage discussions in a repository, {% data variables.product.prodname_discussions %} must be enabled for the repository. For more information, see "[Enabling or disabling {% data variables.product.prodname_discussions %} for a repository](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)." +Para gerenciar as discussões em um repositório, {% data variables.product.prodname_discussions %} deve estar habilitado para o repositório. Para obter mais informações, consulte "[Habilitando ou desabilitando {% data variables.product.prodname_discussions %} para um repositório](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)". ## Alterar a categoria para uma discussão @@ -56,7 +56,7 @@ Editar uma discussão fixada não irá alterar a categoria da discussão. Para o {% data reusables.repositories.navigate-to-repo %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %} -1. Na barra lateral direita, clique em {% octicon "pencil" aria-label="The pencil icon" %} **Editar discussão fixada**. !["Edit pinned discussion" in right sidebar for discussion](/assets/images/help/discussions/click-edit-pinned-discussion.png) +1. Na barra lateral direita, clique em {% octicon "pencil" aria-label="The pencil icon" %} **Editar discussão fixada**. !["Editar discussão fixada" na barra lateral direita para discussão](/assets/images/help/discussions/click-edit-pinned-discussion.png) 1. Personalize a aparência da discussão fixada. ![Opções de personalização para uma discussão fixada](/assets/images/help/discussions/customize-pinned-discussion.png) 1. Clique em **Fixar discussão**. ![Botão "Fixar discussão" nas opções de personalização para discussão fixada](/assets/images/help/discussions/click-pin-discussion-button.png) diff --git a/translations/pt-BR/content/discussions/managing-discussions-for-your-community/moderating-discussions.md b/translations/pt-BR/content/discussions/managing-discussions-for-your-community/moderating-discussions.md index 1e9f3045f4..d2c809136a 100644 --- a/translations/pt-BR/content/discussions/managing-discussions-for-your-community/moderating-discussions.md +++ b/translations/pt-BR/content/discussions/managing-discussions-for-your-community/moderating-discussions.md @@ -1,6 +1,6 @@ --- title: Moderar discussões -intro: 'You can promote healthy collaboration by marking comments as answers, locking or unlocking discussions, converting issues to discussions, and editing or deleting comments, discussions, and categories that don''t align with your community''s code of conduct.' +intro: 'Você pode promover uma colaboração saudável marcando comentários como respostas, bloqueando ou desbloqueando discussões, convertendo problemas para discussões, bem como e editar ou excluir comentários, discussões e categorias que não estão alinhadas com o código de conduta da sua comunidade.' permissions: People with triage access to a repository can moderate discussions in the repository. versions: fpt: '*' diff --git a/translations/pt-BR/content/discussions/quickstart.md b/translations/pt-BR/content/discussions/quickstart.md index ae65dd81fc..cf06b42b4e 100644 --- a/translations/pt-BR/content/discussions/quickstart.md +++ b/translations/pt-BR/content/discussions/quickstart.md @@ -18,17 +18,17 @@ As discussões dão um espaço para conversas mais colaborativas, conectando-se Os proprietários de repositórios e pessoas com acesso de escrita podem habilitar {% data variables.product.prodname_discussions %} para uma comunidade nos seus repositórios públicos e privados. -When you first enable {% data variables.product.prodname_discussions %}, you will be invited to configure a welcome post. +Ao habilitar {% data variables.product.prodname_discussions %} pela primeira vez, você será convidado a configurar um post de boas-vindas. {% data reusables.repositories.navigate-to-repo %} 1. No nome do seu repositório, clique em {% octicon "gear" aria-label="The gear icon" %} **Configurações**. ![Botão de configurações públicas](/assets/images/help/discussions/public-repo-settings.png) -1. Em "Recursos", clique em **Configurar discussões**. ![Set up a discussion button under "Features" for enabling or disabling GitHub Discussions for a repository](/assets/images/help/discussions/setup-discussions-button.png) +1. Em "Recursos", clique em **Configurar discussões**. ![Configure um botão de discussão em "Recursos" para habilitar ou desabilitar as Discussões do GitHub para um repositório](/assets/images/help/discussions/setup-discussions-button.png) 1. Em "Iniciar uma nova discussão", edite o modelo para que fique alinhado aos recursos e tom que você deseja definir para sua comunidade. 1. Clique em **Iniciar discussão**. ![Botão "Iniciar discussão"](/assets/images/help/discussions/new-discussion-start-discussion-button.png) ## Dar as boas-vindas às contribuições para as suas discussões -You can welcome your community and introduce a new way to communicate in a repository by creating a welcome post and pinning the post to your {% data variables.product.prodname_discussions %} page. Fixar e bloquear discussões ajuda as pessoas a saber que uma publicação é feita como um anúncio. Você pode usar os anúncios como uma forma de vincular pessoas a mais recursos e oferecer orientação para abrir discussões na sua comunidade. Para obter mais informações sobre como fixar uma discussão, consulte "[Gerenciar discussões no seu repositório](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#pinning-a-discussion)". +Você pode dar as boas-vindas à sua comunidade e apresentar uma nova forma de se comunicar em um repositório, criando um post de boas-vindas e fixando o post na sua página de {% data variables.product.prodname_discussions %}. Fixar e bloquear discussões ajuda as pessoas a saber que uma publicação é feita como um anúncio. Você pode usar os anúncios como uma forma de vincular pessoas a mais recursos e oferecer orientação para abrir discussões na sua comunidade. Para obter mais informações sobre como fixar uma discussão, consulte "[Gerenciar discussões no seu repositório](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#pinning-a-discussion)". ## Configurar diretrizes da comunidade para colaboradores @@ -39,7 +39,7 @@ Para obter mais informações sobre como fornecer diretrizes para o seu projeto, ## Criar uma nova discussão -Any authenticated user who can view a repository can create a discussion. +Qualquer usuário autenticado que possa visualizar um repositório pode criar uma discussão. {% data reusables.discussions.starting-a-discussion %} 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 817d350d91..743855429f 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 @@ Usar o {% data variables.product.prodname_dotcom %} nos projetos da sua escola {% data reusables.education.about-github-education-link %} -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, which includes access to GitHub Global Campus, a digital campus for our GitHub student community to take advantage of some of the best programs that GitHub Education has to offer. GitHub Global Campus includes the {% data variables.product.prodname_student_pack %}, which offers free access to tools and services used by professional developers, as well as access to [Campus TV](https://www.twitch.tv/githubeducation) content, student events, GitHub Classroom Assignments, and much more, to help students with their technical career goals. 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 dos Alunos do GitHub, que inclui acesso ao Campo Global do GitHub, um campus digital para a nossa comunidade de alunos do GitHub para beneficiar-se de alguns dos melhores programas que o GitHub Education tem para oferecer. O Campus Global do GitHub inclui o {% data variables.product.prodname_student_pack %}, que oferece livre acesso a ferramentas e serviços usados pelos desenvolvedores profissionais, além de acessar o conteúdo de [Campus TV](https://www.twitch.tv/githubeducation), eventos de alunos, atividades de sala de aula GitHub e muito mais para ajudar os alunos a atingir seus objetivos técnicos de carreira. 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-makecode-arcade-with-github-classroom.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md index 0de02c72fc..7708358719 100644 --- a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md @@ -11,7 +11,7 @@ redirect_from: ## Sobre o MakeCode Arcade -O MakeCode Arcade é um ambiente de desenvolvimento integrado on-line (IDE) para o desenvolvimento de jogos retrô arcade que usa a programação de blocos de arrastar e soltar e JavaScript. Os alunos podem escrever, editar, executar, testar e depurar códigos em um navegador com o MakeCode Arcade. 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)." +O MakeCode Arcade é um ambiente de desenvolvimento integrado on-line (IDE) para o desenvolvimento de jogos retrô arcade que usa a programação de blocos de arrastar e soltar e JavaScript. Os alunos podem escrever, editar, executar, testar e depurar códigos em um navegador com o MakeCode Arcade. 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 reusables.classroom.readme-contains-button-for-online-ide %} 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 3e56b15403..e1fcf7cb48 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,44 +1,44 @@ --- -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 %}.' +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 %}.' versions: fpt: '*' redirect_from: - /education/manage-coursework-with-github-classroom/about-using-vs-code-with-github-classroom --- -## About Visual Studio Code +## Sobre o Visual Studio Code -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)." +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)". -### Your student's editor of choice -The GitHub Classroom integration with Visual Studio Code provides students with an extension pack which contains: +### 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: -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. +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. -### 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)." +### 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)". -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. +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. {% 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). +**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). {% endnote %} -### How to use GitHub Classroom extension pack -The GitHub Classroom extension has two major components: the 'Classrooms' view and the 'Active Assignment' view. +### 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". -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. +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. -![GitHub Classroom Active Assignment View](/assets/images/help/classroom/vs-code-active-assignment.png) +![Visão da atividade ativa do GitHub Classroom](/assets/images/help/classroom/vs-code-active-assignment.png) -The student can push their commits to the latest version of remote, by clicking the **sync changes** button, displayed when hovering over the "Active Assignment" line. This abstracts away source control with Git, allowing instructors to teach Git at their own pace. Synching changes also triggers "Tests" to run if a teacher has configured autograding for their assignment. +O aluno pode fazer push dos seus commits para a versão mais recente do controle remoto, ao clicar no botão **Sincronizar alterações**, exibido ao passar o mouse sobre a linha "atividade ativa". Isso abstrai o controle de origem com o Git, permitindo que instrutores ensinem o Git no seu próprio ritmo. A sincronização de alterações também aciona a execução de "testes", se um professor tiver configurado a avaliação automática para sua atividade. -The "Group" node under "Active Assignment" will show members of a group, if the assignment is a group project. It will also show the admin members of the repository who can help when a student is stuck. To collaborate on the project, a student can start a Live Share session with anyone in the group node, and they will immediately share the entire context of the repository with them. You can learn more about Live Share and collaborating with it [here](https://docs.microsoft.com/en-us/visualstudio/liveshare/). +O nó "grupo", em "atividade ativa", mostrará os integrantes de um grupo, se a tarefa for um projeto em grupo. Ele também mostrará os integrantes de administrador do repositório que podem ajudar quando um aluno estiver parado. Para colaborar no projeto, um aluno pode iniciar uma sessão de compartilhamento ao vivo com qualquer pessoa no nó do grupo, e ele irá compartilhar imediatamente todo o contexto do repositório com eles. Você pode aprender mais sobre o compartilhamento ao vivo e a colaboração [aqui](https://docs.microsoft.com/en-us/visualstudio/liveshare/). -Once a student is done with the assignment, they can also navigate to see other Assignments and Classrooms. These can be found under the GitHub tab. +Quando um aluno termina a tarefa, ele também pode navegar para ver outras atividades e salas de aula. Elas podem ser encontradas na aba do GitHub. 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 078b797e5c..c74ce7c1d1 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 @@ -1,7 +1,7 @@ --- title: Integrar GitHub Classroom com um IDE shortTitle: Integrar com um IDE -intro: 'You can preconfigure a supported integrated development environment (IDE) for assignments you create in {% data variables.product.prodname_classroom %}.' +intro: 'Você pode pré-configurar um ambiente de desenvolvimento integrado (IDE) compatível para atividades que você criar em {% data variables.product.prodname_classroom %}.' versions: fpt: '*' redirect_from: @@ -10,30 +10,30 @@ redirect_from: - /education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-online-ide --- -## About integration with an IDE +## Sobre a integração com um IDE {% data reusables.classroom.about-online-ides %} -After a student accepts an assignment with an IDE, the README file in the student's assignment repository will contain a button to open the assignment in the IDE. O aluno pode começar a trabalhar imediatamente, e nenhuma configuração adicional será necessária. +Depois que um aluno aceita um trabalho com um IDE, o arquivo README no repositório de atividades do aluno conterá um botão para abrir a atividade no IDE. O aluno pode começar a trabalhar imediatamente, e nenhuma configuração adicional será necessária. -## Supported IDEs +## IDEs compatíveis -{% data variables.product.prodname_classroom %} supports the following IDEs. Você pode aprender mais sobre a experiência do aluno para cada IDE. +{% data variables.product.prodname_classroom %} é compatível com os IDEs a seguir. Você pode aprender mais sobre a experiência do aluno para cada IDE. | IDE | Mais informações | |:------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 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 | [{% data variables.product.prodname_classroom %} extension](http://aka.ms/classroom-vscode-ext) in the Visual Studio Marketplace | +| Visual Studio Code | [Extensão de {% data variables.product.prodname_classroom %}](http://aka.ms/classroom-vscode-ext) no Marketplace do Visual Studio | -We know cloud IDE integrations are important to your classroom and are working to bring more options. +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. -## Configuring an IDE for an assignment +## Configurando um IDE para uma atividade -You can choose the IDE you'd like to use for an assignment when you create an assignment. To learn how to create a new assignment that uses an IDE, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" or "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)." +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)". -## Authorizing the OAuth app for an IDE +## Autorizando o aplicativo OAuth para um IDE -The first time you configure an assignment with an IDE, you must authorize the OAuth app for the IDE for your organization. +Na primeira vez que você configurar uma atividade com um IDE, você deverá autorizar o aplicativo OAuth para o IDE da 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)". diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/replit-with-github-classroom.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/replit-with-github-classroom.md index f11e41ef0b..9ac933f501 100644 --- a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/replit-with-github-classroom.md +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/replit-with-github-classroom.md @@ -1,7 +1,7 @@ --- -title: Repl.it with GitHub Classroom -shortTitle: Repl.it with GitHub Classroom -intro: 'As of July 13 2021, Repl.it integration is no longer available in {% data variables.product.prodname_classroom %}.' +title: Repl.it com GitHub Classroom +shortTitle: Repl.it com GitHub Classroom +intro: 'A partir de 13 de julho de 2021, a integração do Repl.it não estará disponível em {% data variables.product.prodname_classroom %}.' versions: fpt: '*' redirect_from: @@ -10,19 +10,19 @@ redirect_from: - /education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-replit-with-github-classroom --- -## What’s changing with Repl.it integration +## O que irá mudar com a integração do Repl.it -As of July 13 2021, Repl.it integration is no longer available. Here’s what’s changed: +A partir de 13 de Julho de 2021, a integração do Repl.it deixou de estar disponível. O que mudou: -- New private and public repls can no longer be created from within GitHub Classroom. -- Replit Hacker benefits, such as Always On and Boosts, are no longer available for new GitHub Classroom users. +- As novas respostas privadas e públicas não podem mais ser criadas a partir do GitHub Classroom. +- Os benefícios do Hacker como, por exemplo, Always On e Boosts, não estão mais disponíveis para novos usuários do GitHub Classroom. -## What does this mean for existing assignments? -Your existing GitHub Classroom repls will remain private forever and you can submit work to GitHub Classroom via these repls until September 30 2021. After September 2021, the Replit icon on the assignment README will no longer work. We suggest you remove the instructions from any README using the integration and let students know that the icon will no longer work. +## O que isso significa para as atividades existentes? +As suas respostas do GitHub Classroom permanecerão privadas para sempre e você poderá enviar o trabalho para o GitHub Classroom por meio destas respostas até 30 de Setembro de 2021. Após 21 de setembro, o ícone do Replit no README da atividade não funcionará mais. Sugerimos que você remova as instruções de qualquer README que usar a integração e diga aos alunos que o ícone não funcionará mais. -While you can no longer create private repls from within Classroom, you can continue to create private repls in Replit until September 30th. +Embora você não possa mais criar respostas privadas no Classroom, você poderá continuar criando respostas privadas no Replit até o 30 de setembro. -We know cloud IDE integrations are important to your classroom and are working hard to bring you more options. +Sabemos que as integrações do IDE na nuvem são importantes para a sua sala de aula e estamos trabalhando para oferecer mais opções para você. ## Leia mais diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/run-student-code-in-an-ide.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/run-student-code-in-an-ide.md index eb9a831e3f..124ea173c3 100644 --- a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/run-student-code-in-an-ide.md +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/run-student-code-in-an-ide.md @@ -1,22 +1,22 @@ --- -title: Run student code in an IDE -intro: You can run the code from a student assignment within the integrated development environment (IDE) that you configured for the assignment. +title: Execute o código do aluno em um IDE +intro: Você pode executar o código da atividade de um aluno dentro do ambiente de desenvolvimento integrado (IDE) que você configurou para a atividade. versions: fpt: '*' redirect_from: - /education/manage-coursework-with-github-classroom/running-student-code - /education/manage-coursework-with-github-classroom/run-student-code-in-an-online-ide - /education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/run-student-code-in-an-online-ide -shortTitle: Run code in IDE +shortTitle: Execute o código no IDE --- -## About student code and IDEs +## Sobre o código do aluno e os IDEs -If you configure an integrated development environment (IDE) for an assignment, you can run the code within the IDE. Você não precisa clonar o repositório da atividade no seu computador. +Se você configurar um ambiente integrado de desenvolvimento (IDE) para uma atividade, você poderá executar o código dentro do IDE. Você não precisa clonar o repositório da atividade no seu computador. -For more information about IDEs, 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)." +Para obter mais informações sobre IDEs, consulte "[Integrar {% data variables.product.prodname_classroom %} com um IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)". -## Running student code in the IDE +## Executando o código do aluno no IDE {% data reusables.classroom.sign-into-github-classroom %} {% data reusables.classroom.click-classroom-in-list %} diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md index 0487d74b93..fa0e4a3820 100644 --- a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md @@ -81,7 +81,7 @@ Se você já criou uma atividade em grupo para a sala de aula, você pode reutil {% data reusables.classroom.assignments-guide-intro-for-environment %} - [Escolher um repositório de modelo](#choosing-a-template-repository) -- [Choosing an integrated development environment (IDE)](#choosing-an-integrated-development-environment-ide) +- [Escolhendo um ambiente integrado de desenvolvimento (IDE)](#choosing-an-integrated-development-environment-ide) ### Escolher um repositório de modelo @@ -89,7 +89,7 @@ Por padrão, uma nova atividade criará um repositório vazio para cada equipe c {% data reusables.classroom.assignments-guide-choose-template-repository %} -### Choosing an integrated development environment (IDE) +### Escolhendo um ambiente integrado de desenvolvimento (IDE) {% data reusables.classroom.about-online-ides %} Para obter mais informações, consulte "[Integrar {% data variables.product.prodname_classroom %} com um IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)." @@ -128,7 +128,7 @@ Você pode ver as equipes que estão trabalhando ou que enviaram uma atividade n ## Próximas etapas -- Após criar a atividade e seus alunos formarem equipes, os integrantes da equipe poderão começar a trabalhar nas atividades usando os recursos do Git e do {% data variables.product.product_name %}. Os alunos podem clonar o repositório, realizar commits de push, gerenciar branches, criar e revisar pull requests, resolver conflitos de merge e discutir alterações com problemas. Tanto você como a equipe podem revisar o histórico de commit do repositório. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Repositories](/repositories)," "[Using Git](/github/getting-started-with-github/using-git)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)," and the free course on [managing merge conflicts](https://lab.github.com/githubtraining/managing-merge-conflicts) from {% data variables.product.prodname_learning %}. +- Após criar a atividade e seus alunos formarem equipes, os integrantes da equipe poderão começar a trabalhar nas atividades usando os recursos do Git e do {% data variables.product.product_name %}. Os alunos podem clonar o repositório, realizar commits de push, gerenciar branches, criar e revisar pull requests, resolver conflitos de merge e discutir alterações com problemas. Tanto você como a equipe podem revisar o histórico de commit do repositório. Para obter mais informações, consulte "[Primeiros passos com {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[repositórios](/repositories)," "[Usando o Git](/github/getting-started-with-github/using-git), e "[Colaborando com problemas e pull requests](/github/collaborating-with-issues-and-pull-requests)e o curso grátis em [Gerenciando conflitos de merge](https://lab.github.com/githubtraining/managing-merge-conflicts) de {% data variables.product.prodname_learning %}. - Quando uma equipe termina uma atividade, você poderá revisar os arquivos no repositório, ou você poderá revisar o histórico e as visualizações do repositório para entender melhor como a equipe colaborou. Para obter mais informações, consulte "[Visualizar dados do repositório com gráficos](/github/visualizing-repository-data-with-graphs)". diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md index 8c362f1c03..950f8d62e7 100644 --- a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md @@ -61,7 +61,7 @@ Em "Tarefa individual ou de grupo", selecione o menu suspenso e clique em **Tare {% data reusables.classroom.assignments-guide-intro-for-environment %} - [Escolher um repositório de modelo](#choosing-a-template-repository) -- [Choosing an integrated development environment (IDE)](#choosing-an-integrated-development-environment-ide) +- [Escolhendo um ambiente integrado de desenvolvimento (IDE)](#choosing-an-integrated-development-environment-ide) ### Escolher um repositório de modelo @@ -71,7 +71,7 @@ Por padrão, uma nova atividade criará um repositório vazio para cada aluno na {% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %} -### Choosing an integrated development environment (IDE) +### Escolhendo um ambiente integrado de desenvolvimento (IDE) {% data reusables.classroom.about-online-ides %} Para obter mais informações, consulte "[Integrar {% data variables.product.prodname_classroom %} com um IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)." @@ -108,7 +108,7 @@ Você pode ver se um aluno juntou-se à sala de aula e aceitou ou enviou uma ati ## Próximas etapas -- Depois de criar a atividade, os alunos poderão começar a trabalhar na atividade usando os recursos do Git e do {% data variables.product.product_name %}. Os alunos podem clonar o repositório, realizar commits de push, gerenciar branches, criar e revisar pull requests, resolver conflitos de merge e discutir alterações com problemas. Você e o aluno podem revisar o histórico do commit do repositório. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Repositories](/repositories)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)." +- Depois de criar a atividade, os alunos poderão começar a trabalhar na atividade usando os recursos do Git e do {% data variables.product.product_name %}. Os alunos podem clonar o repositório, realizar commits de push, gerenciar branches, criar e revisar pull requests, resolver conflitos de merge e discutir alterações com problemas. Você e o aluno podem revisar o histórico do commit do repositório. Para obter mais informações, consulte "[Começando com {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github), "[Repositórios](/repositories)" e "[Colaborando com problemas e pull requests](/github/collaborating-with-issues-and-pull-requests)". - Quando um aluno concluir uma atividade, você poderá revisar os arquivos no repositório ou você poderá revisar o histórico e as visualizações do repositório para entender melhor o trabalho do aluno. Para obter mais informações, consulte "[Visualizar dados do repositório com gráficos](/github/visualizing-repository-data-with-graphs)". diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md index 9d3efca67f..a5f0ffcde1 100644 --- a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md @@ -71,15 +71,15 @@ Você pode adicionar, editar ou excluir testes de avaliação automática para u - Para excluir um teste, à direita do nome do teste, clique em {% octicon "trash" aria-label="The trash icon" %}. ![Ícone da lixeira para excluir um teste de avaliação automática](/assets/images/help/classroom/autograding-click-trash.png) 1. Na parte inferior da página, clique em **Atualizar atividade**. ![Botão "Atualizar a atividade" na parte inferior da página](/assets/images/help/classroom/assignments-click-update-assignment.png) -## Viewing and downloading results from autograding tests +## Visualizar e fazer o download de resultados de testes de autoavaliação -### Download autograding results +### Fazer o download dos resultados da auto-avaliação -You can also download a CSV of your students' autograding scores via the "Download" button. This will generate and download a CSV containing a link to the student's repository, their {% data variables.product.prodname_dotcom %} handle, roster identifier, submission timestamp, and autograding score. +Você também pode fazer o download do CSV da pontuação da autoavaliação dos seus alunos por meio do botão "Download". Isso irá gerar e fazer o download de um CSV que contém um link para o repositório do aluno, seu gerenciador de {% data variables.product.prodname_dotcom %}, identificador da lista de participantes, registro de hora de envio e pontuação de da autoavaliação. -!["Download" button selected showing "Download grades highlighted" and an additional option to "Download repositories"](/assets/images/help/classroom/download-grades.png) +![O botão "Download" selecionado que mostra "Fazer o download de notas destacadas" e uma opção adicional para "Fazer o download dos repositórios"](/assets/images/help/classroom/download-grades.png) -### View individual logs +### Ver registros individuais {% data reusables.classroom.sign-into-github-classroom %} {% data reusables.classroom.click-classroom-in-list %} {% data reusables.classroom.click-assignment-in-list %} diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md index 8a8238cd6f..8869ccec0f 100644 --- a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md @@ -8,12 +8,6 @@ redirect_from: shortTitle: Atribuição inicial --- -{% note %} - -**Observação:** A atividade inicial do Git & {% data variables.product.company_short %} está em fase beta e sujeita a alterações. - -{% endnote %} - A atividade inicial do Git & {% data variables.product.company_short %} é um curso pré-fabricado que resume os conceitos básicos do Git e {% data variables.product.company_short %} e vincula os alunos a recursos para aprender mais sobre tópicos específicos. ## Pré-requisitos 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 e4be40b63c..2e8520378d 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 @@ -1,6 +1,7 @@ --- title: Encontrando maneiras de contribuir com o código aberto no GitHub intro: 'Você pode encontrar maneiras de contribuir para projetos de código aberto em {% data variables.product.product_name %} que são relevantes para você.' +permissions: '{% data reusables.enterprise-accounts.emu-permission-interact %}' redirect_from: - /articles/where-can-i-find-open-source-projects-to-work-on/ - /articles/finding-interesting-projects-on-github/ @@ -19,7 +20,7 @@ shortTitle: Contribuir para o código aberto ## Descobrir projetos relevantes -Se houver um tópico específico que lhe interessa, visite `github.com/topics/`. Por exemplo, se você estiver interessado em aprendizado de máquina, poderá encontrar projetos relevantes e bons problemas visitando https://github.com/topics/machine-learning. Você pode navegar por tópicos populares visitando [Tópicos](https://github.com/topics). Você também pode procurar repositórios que correspondam a um tópico do seu interesse. Para obter mais informações, consulte "[Pesquisar repositórios](/articles/searching-for-repositories#search-by-topic)". +Se houver um tópico específico que lhe interessa, visite `github.com/topics/`. Por exemplo, se você estiver interessado em aprendizado de máquina, poderá encontrar projetos relevantes e bons problemas visitando https://github.com/topics/machine-learning. Você pode navegar por tópicos populares visitando [Tópicos](https://github.com/topics). Você também pode procurar repositórios que correspondam a um tópico do seu interesse. Para obter mais informações, consulte "[Pesquisar repositórios](/search-github/searching-on-github/searching-for-repositories#search-by-topic)". Se você esteve ativo em {% data variables.product.product_name %}, você pode encontrar recomendações personalizadas para projetos e bons problemas iniciais com base em suas contribuições anteriores, estrelas e outras atividades em [Explorar](https://github.com/explore). Você também pode se inscrever no boletim informativo Explorar para receber e-mails sobre oportunidades de contribuir para {% data variables.product.product_name %} com base em seus interesses. Para se inscrever, consulte [Explorar newsletter de e-mail](https://github.com/explore/subscribe). diff --git a/translations/pt-BR/content/get-started/exploring-projects-on-github/following-people.md b/translations/pt-BR/content/get-started/exploring-projects-on-github/following-people.md index 4b355da238..cbee252d2f 100644 --- a/translations/pt-BR/content/get-started/exploring-projects-on-github/following-people.md +++ b/translations/pt-BR/content/get-started/exploring-projects-on-github/following-people.md @@ -1,6 +1,7 @@ --- title: Seguir pessoas intro: 'É possível seguir pessoas em {% data variables.product.product_name %} para receber notificações sobre as atividades delas {% ifversion fpt %} e descobrir projetos nas comunidades em que elas estão inseridas.{% endif %}.' +permissions: '{% data reusables.enterprise-accounts.emu-permission-follow %}' redirect_from: - /articles/following-people - /github/getting-started-with-github/following-people @@ -13,51 +14,51 @@ topics: - Profile --- -## About followers on {% data variables.product.product_name %} +## Sobre seguidores em {% data variables.product.product_name %} -When you follow people, you'll see their public activity in the activity view of your news feed.{% ifversion fpt %} If someone you follow stars a public repository, {% data variables.product.product_name %} may recommend the repository to you in the discovery view of your news feed.{% endif %} +Ao seguir pessoas, você verá a atividade pública deles na vista de atividades do seu feed de notícias.{% ifversion fpt %} Se alguém que você segue favoritar um repositório público, {% data variables.product.product_name %} poderá recomendar o repositório para você na vista de descoberta do seu feed de notícias.{% endif %} -You can unfollow someone if you do not wish to see their public activity on {% data variables.product.product_name %}. +Você pode deixar de seguir alguém, se você não quiser ver suas atividades públicas em {% data variables.product.product_name %}. -## Following a user on {% data variables.product.product_name %} +## Seguindo um usuário em {% data variables.product.product_name %} -1. Click a user image to display that user's profile. +1. Clique em uma imagem de usuário para exibir o perfil do usuário. - ![User image](/assets/images/help/profile/user-profile-image.png) + ![Imagem do usuário](/assets/images/help/profile/user-profile-image.png) -2. Click **Follow** under their profile image. +2. Clique em **Seguir** na imagem do seu perfil. ![Botão Follow user (Seguir usuário)](/assets/images/help/profile/follow-user-button.png) -## Unfollowing a user on {% data variables.product.product_name %} +## Deixando de seguir um usuário em {% data variables.product.product_name %} -1. Click a user image to display that user's profile. +1. Clique em uma imagem de usuário para exibir o perfil do usuário. - ![User image](/assets/images/help/profile/user-profile-image.png) + ![Imagem do usuário](/assets/images/help/profile/user-profile-image.png) -2. Click **Unfollow** under their profile image. +2. Clique em **Deixar de seguir** na imagem do perfil dele. - ![User profile button](/assets/images/help/profile/user-profile-unfollow-button.png) + ![Botão Perfil do Usuário](/assets/images/help/profile/user-profile-unfollow-button.png) -## Viewing followed users on {% data variables.product.product_name %} +## Visualizando usuários seguidos em {% data variables.product.product_name %} -1. Click a user image to display that user's profile. +1. Clique em uma imagem de usuário para exibir o perfil do usuário. - ![User image](/assets/images/help/profile/user-profile-image.png) + ![Imagem do usuário](/assets/images/help/profile/user-profile-image.png) -2. Click **following** under their profile image. +2. Clique em **Seguindo** na imagem do perfil deles. - ![User following](/assets/images/help/profile/user-profile-following.png) + ![Seguindo usuário](/assets/images/help/profile/user-profile-following.png) -## Viewing followers on {% data variables.product.product_name %} +## Visualizando seguidores em {% data variables.product.product_name %} -1. Click a user image to display that user's profile. +1. Clique em uma imagem de usuário para exibir o perfil do usuário. - ![User image](/assets/images/help/profile/user-profile-image.png) + ![Imagem do usuário](/assets/images/help/profile/user-profile-image.png) -2. Click **followers** under their profile image. +2. Clique em **seguidores** na imagem do perfil deles. - ![User following](/assets/images/help/profile/user-profile-followers.png) + ![Seguindo usuário](/assets/images/help/profile/user-profile-followers.png) diff --git a/translations/pt-BR/content/get-started/getting-started-with-git/associating-text-editors-with-git.md b/translations/pt-BR/content/get-started/getting-started-with-git/associating-text-editors-with-git.md index c6debb0f6a..7297c78717 100644 --- a/translations/pt-BR/content/get-started/getting-started-with-git/associating-text-editors-with-git.md +++ b/translations/pt-BR/content/get-started/getting-started-with-git/associating-text-editors-with-git.md @@ -61,6 +61,7 @@ shortTitle: Editores de texto associados ## Usar o Atom como seu editor 1. Instale o [Atom](https://atom.io/). Para obter mais informações, consulte "[Instalar o Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" na documentação do Atom. +{% data reusables.command_line.open_the_multi_os_terminal %} 3. Digite este comando: ```shell $ git config --global core.editor "atom --wait" diff --git a/translations/pt-BR/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md b/translations/pt-BR/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md index b7bb2fb1ab..f9e2d56cbf 100644 --- a/translations/pt-BR/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md +++ b/translations/pt-BR/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md @@ -7,7 +7,7 @@ redirect_from: - /github/using-git/caching-your-github-credentials-in-git - /github/getting-started-with-github/caching-your-github-credentials-in-git - /github/getting-started-with-github/getting-started-with-git/caching-your-github-credentials-in-git -intro: 'If you''re [cloning {% data variables.product.product_name %} repositories using HTTPS](/github/getting-started-with-github/about-remote-repositories), we recommend you use {% data variables.product.prodname_cli %} or Git Credential Manager Core (GCM Core) to remember your credentials.' +intro: 'Se você estiver [clonando repositórios de {% data variables.product.product_name %} que usam HTTPS](/github/getting-started-with-github/about-remote-repositories), recomendamos que você use {% data variables.product.prodname_cli %} ou Git Credential Manager Core (GCM Core) para lembrar suas credenciais.' versions: fpt: '*' ghes: '*' @@ -17,66 +17,66 @@ shortTitle: Armazenando credenciais {% tip %} -**Tip:** If you clone {% data variables.product.product_name %} repositories using SSH, then you can authenticate using an SSH key instead of using other credentials. Para obter informações sobre como configurar uma conexão SSH, consulte "[Gerar uma chave SSH](/articles/generating-an-ssh-key)". +Dica de **:** Se você clonar {% data variables.product.product_name %} repositórios usando SSH, você pode efetuar a autenticação usando uma chave SSH em vez de usar outras credenciais. Para obter informações sobre como configurar uma conexão SSH, consulte "[Gerar uma chave SSH](/articles/generating-an-ssh-key)". {% endtip %} ## {% data variables.product.prodname_cli %} -{% data variables.product.prodname_cli %} will automatically store your Git credentials for you when you choose `HTTPS` as your preferred protocol for Git operations and answer "yes" to the prompt asking if you would like to authenticate to Git with your {% data variables.product.product_name %} credentials. +{% data variables.product.prodname_cli %} armazenará automaticamente suas credenciais do Git para você escolher `HTTPS` como protocolo preferido para operações do Git e responder "sim" à instrução que pergunta se você gostaria de efetuar a autenticação no Git com a suas credenciais de {% data variables.product.product_name %}. -1. [Install](https://github.com/cli/cli#installation) {% data variables.product.prodname_cli %} on macOS, Windows, or Linux. -2. In the command line, enter `gh auth login`, then follow the prompts. - - When prompted for your preferred protocol for Git operations, select `HTTPS`. - - When asked if you would like to authenticate to Git with your {% data variables.product.product_name %} credentials, enter `Y`. +1. [Instale](https://github.com/cli/cli#installation) {% data variables.product.prodname_cli %} no macOS, Windows ou Linux. +2. Na linha de comando, digite `gh auth login` e, em seguida, siga as instruções. + - Quando for solicitado o protocolo preferido para operações do Git, selecione `HTTPS`. + - Quando for perguntado se você gostaria de efetuar a autenticação no Git com as suas credenciais de {% data variables.product.product_name %}, insira `Y`. -For more information about authenticating with {% data variables.product.prodname_cli %}, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login). +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). -## Git Credential Manager Core +## Núcleo de Administração de Credenciais do Git -[Git Credential Manager Core](https://github.com/microsoft/Git-Credential-Manager-Core) (GCM Core) is another way to store your credentials securely and connect to GitHub over HTTPS. With GCM Core, you don't have to manually [create and store a PAT](/github/authenticating-to-github/creating-a-personal-access-token), as GCM Core manages authentication on your behalf, including 2FA (two-factor authentication). +O [Núcleo de Administração de Credenciais do Git](https://github.com/microsoft/Git-Credential-Manager-Core) (GCM Core) é outra maneira de armazenar suas credenciais de forma segura e conectar-se ao GitHub por HTTPS. Com Núcleo GCM, você não precisa [criar e armazenar um PAT](/github/authenticating-to-github/creating-a-personal-access-token) manualmente, uma vez que o Núcleo GCM gerencia a autenticação em seu nome, incluindo 2FA (autenticação de dois fatores). {% mac %} -1. Install Git using [Homebrew](https://brew.sh/): +1. Instale o Git usando [Homebrew](https://brew.sh/): ```shell $ brew install git ``` -2. Install GCM Core using Homebrew: +2. Instale o GCM Core usando o Homebrew: ```shell $ brew tap microsoft/git $ brew install --cask git-credential-manager-core ``` - For MacOS, you don't need to run `git config` because GCM Core automatically configures Git for you. + Para MacOS, você não precisa executar a configuração do `git` porque o GCM Core configura o Git para você automaticamente. {% data reusables.gcm-core.next-time-you-clone %} -Após a autenticação ser concluída com sucesso, suas credenciais serão armazenadas no keychain do macOS e serão usadas toda vez que você clonar uma URL de HTTPS. Git will not require you to type your credentials in the command line again unless you change your credentials. +Após a autenticação ser concluída com sucesso, suas credenciais serão armazenadas no keychain do macOS e serão usadas toda vez que você clonar uma URL de HTTPS. O Git não exigirá que você digite suas credenciais na linha de comando novamente, a menos que você altere suas credenciais. {% endmac %} {% windows %} -1. Install Git for Windows, which includes GCM Core. For more information, see "[Git for Windows releases](https://github.com/git-for-windows/git/releases/latest)" from its [releases page](https://github.com/git-for-windows/git/releases/latest). +1. Instale o Git para Windows, que inclui o GCM Core. Para obter mais informações, consulte "[Git para versões do Windows](https://github.com/git-for-windows/git/releases/latest)" a partir da sua [página de versões](https://github.com/git-for-windows/git/releases/latest). -We recommend always installing the latest version. At a minimum, install version 2.29 or higher, which is the first version offering OAuth support for GitHub. +Recomenda-se instalar sempre a versão mais recente. No mínimo, instale a versão 2.29 ou superior, que é a primeira versão que oferece suporte do OAuth para o GitHub. {% data reusables.gcm-core.next-time-you-clone %} -Once you've authenticated successfully, your credentials are stored in the Windows credential manager and will be used every time you clone an HTTPS URL. Git will not require you to type your credentials in the command line again unless you change your credentials. +Depois de efetuar a autenticação com sucesso, as suas credenciais serão armazenadas no gerenciador de credenciais do Windows e serão usadas toda vez que você clonar uma URL de HTTPS. O Git não exigirá que você digite suas credenciais na linha de comando novamente, a menos que você altere suas credenciais.
    {% warning %} -**Warning:** Older versions of Git for Windows came with Git Credential Manager for Windows. This older product is no longer supported and cannot connect to GitHub via OAuth. We recommend you upgrade to [the latest version of Git for Windows](https://github.com/git-for-windows/git/releases/latest). +**Aviso:** As versões mais antigas do Git para Windows vieram com o Administrador de Credenciais do Git para Windows. Este produto antigo não é mais compatível e não pode se conectar ao GitHub via OAuth. Recomendamos que você faça atualização para [a versão mais recente do Git para Windows](https://github.com/git-for-windows/git/releases/latest). {% endwarning %} {% warning %} -**Warning:** If you cached incorrect or outdated credentials in Credential Manager for Windows, Git will fail to access {% data variables.product.product_name %}. To reset your cached credentials so that Git prompts you to enter your credentials, access the Credential Manager in the Windows Control Panel under User Accounts > Credential Manager. Look for the {% data variables.product.product_name %} entry and delete it. +**Aviso:** Se você fez cache de credenciais incorretas ou desatualizadas no Gerenciador de Credencial para Windows, o Git não terá acesso a {% data variables.product.product_name %}. Para redefinir as suas credenciais de cache para que o Git peça para inserir suas credenciais, acesse o Gerenciador de credenciais no Painel de Controle do Windows em Contas de Usuário > Gerenciador de Credenciais. Procure a entrada de {% data variables.product.product_name %} e exclua-a. {% endwarning %} @@ -84,17 +84,17 @@ Once you've authenticated successfully, your credentials are stored in the Windo {% linux %} -For Linux, install Git and GCM Core, then configure Git to use GCM Core. +Para Linux, instale o Git e GCM Core e, em seguida, configure o Git para usar o GCM Core. -1. Install Git from your distro's packaging system. Instructions will vary depending on the flavor of Linux you run. +1. Instale o Git a partir do sistema de pacotes da sua distribuição. As instruções vão variar dependendo da versão do Linux que você executar. -2. Install GCM Core. See the [instructions in the GCM Core repo](https://github.com/microsoft/Git-Credential-Manager-Core#linux-install-instructions), as they'll vary depending on the flavor of Linux you run. +2. Instale o GCM Core. Consulte as [instruções no repositório do GCM Core](https://github.com/microsoft/Git-Credential-Manager-Core#linux-install-instructions), já que elas variarão dependendo da versão do Linux que você executar. -3. Configure Git to use GCM Core. There are several backing stores that you may choose from, so see the GCM Core docs to complete your setup. For more information, see "[GCM Core Linux](https://aka.ms/gcmcore-linuxcredstores)." +3. Configure o Git para usar o GCM Core. Há várias lojas de apoio que você pode escolher. Portanto, consulte a documentação de do GCM Core para concluir a sua configuração. Para obter mais informações, consulte "[GCM Core Linux](https://aka.ms/gcmcore-linuxcredstores)". {% data reusables.gcm-core.next-time-you-clone %} -Once you've authenticated successfully, your credentials are stored on your system and will be used every time you clone an HTTPS URL. Git will not require you to type your credentials in the command line again unless you change your credentials. +Depois de autenticado com sucesso, as suas credenciais serão armazenadas no seu sistema e serão usadas toda vez que você clonar uma URL de HTTPS. O Git não exigirá que você digite suas credenciais na linha de comando novamente, a menos que você altere suas credenciais. Para obter mais opções para armazenar suas credenciais no Linux, consulte [Armazenamento de Credencial](https://git-scm.com/book/en/v2/Git-Tools-Credential-Storage) no Pro Git. @@ -102,4 +102,4 @@ Para obter mais opções para armazenar suas credenciais no Linux, consulte [Arm
    -For more information or to report issues with GCM Core, see the official GCM Core docs at "[Git Credential Manager Core](https://github.com/microsoft/Git-Credential-Manager-Core)." +Para obter mais informações ou relatar problemas com o GCM Core, consulte a documentação oficial do Núcleo GCM em"[Núcleo do Gerenciador de Credenciais do Git](https://github.com/microsoft/Git-Credential-Manager-Core)". diff --git a/translations/pt-BR/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md b/translations/pt-BR/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md index 1c6d9bfe34..a47a92af04 100644 --- a/translations/pt-BR/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md +++ b/translations/pt-BR/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md @@ -16,7 +16,7 @@ versions: shortTitle: Manusear delimitadores --- -## About line endings +## Sobre os delimitadores de linha Toda vez que você pressionar retornar no seu teclado, você insere um caractere invisível denominado delimitador. Os diferentes sistemas operacionais gerenciam os delimitadores de formas diferentes. Ao colaborar em projetos com Git e {% data variables.product.product_name %}, o Git pode produzir resultados inesperados se, por exemplo, você estiver trabalhando em uma máquina que use o Windows e o seu colaborador dizer uma mudança no macOS. diff --git a/translations/pt-BR/content/get-started/getting-started-with-git/setting-your-username-in-git.md b/translations/pt-BR/content/get-started/getting-started-with-git/setting-your-username-in-git.md index 87b26c6d29..02393bfea4 100644 --- a/translations/pt-BR/content/get-started/getting-started-with-git/setting-your-username-in-git.md +++ b/translations/pt-BR/content/get-started/getting-started-with-git/setting-your-username-in-git.md @@ -13,7 +13,7 @@ versions: shortTitle: Definir o seu nome de usuário --- -## About Git usernames +## Sobre nomes de usuários do Git Você pode alterar o nome associado aos commits do Git usando o comando `git config`. O novo nome configurado ficará visível em todos os commits futuros cujo push é feito para o {% data variables.product.product_name %} usando a linha de comando. Se não quiser usar seu nome verdadeiro, use qualquer texto como o nome de usuário do Git. Alterar o nome associado aos commits do Git usando o `git config` afeta somente os commits futuros e não altera o nome usado em commits antigos. diff --git a/translations/pt-BR/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md b/translations/pt-BR/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md index 667940b9d0..d6d83100be 100644 --- a/translations/pt-BR/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md +++ b/translations/pt-BR/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md @@ -16,9 +16,9 @@ shortTitle: Credenciais de keychain do macOS {% tip %} -**Note:** Updating credentials from the macOS Keychain only applies to users who manually configured a PAT using the `osxkeychain` helper that is built-in to macOS. +**Observação:** A atualização das credenciais do macOS Keychain aplica-se apenas a usuários que configuraram manualmente um PAT usando o auxiliar `osxkeychain` integrado ao macOS. -We recommend you either [configure SSH](/articles/generating-an-ssh-key) or upgrade to the [Git Credential Manager Core](/get-started/getting-started-with-git/caching-your-github-credentials-in-git) (GCM Core) instead. GCM Core can manage authentication on your behalf (no more manual PATs) including 2FA (two-factor auth). +Recomendamos que você [configure o SSH](/articles/generating-an-ssh-key) ou faça a atualização para o [Núcleo de Administração de Credenciais do Git](/get-started/getting-started-with-git/caching-your-github-credentials-in-git) (GCM Core). O GCM Core pode gerenciar a autenticação em seu nome (sem PATs manuais), incluindo a 2FA (autenticação de dois fatores). {% endtip %} diff --git a/translations/pt-BR/content/get-started/learning-about-github/about-github-advanced-security.md b/translations/pt-BR/content/get-started/learning-about-github/about-github-advanced-security.md index ea0aa61075..1f2d20652a 100644 --- a/translations/pt-BR/content/get-started/learning-about-github/about-github-advanced-security.md +++ b/translations/pt-BR/content/get-started/learning-about-github/about-github-advanced-security.md @@ -18,7 +18,7 @@ shortTitle: Segurança Avançada GitHub {% data variables.product.prodname_dotcom %} tem muitas funcionalidades que ajudam você a melhorar e manter a qualidade do seu código. Alguns deles são incluídos em todos os planos{% ifversion not ghae %}, como o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %}{% endif %}. Outras funcionalidades de segurança exigem uma licença de {% data variables.product.prodname_GH_advanced_security %} para ser executada em repositórios, além dos repositórios públicos em {% data variables.product.prodname_dotcom_the_website %}. -{% ifversion fpt or ghes > 3.0 %}For more information about purchasing {% data variables.product.prodname_GH_advanced_security %}, see "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)."{% elsif ghae %}There is no charge for {% data variables.product.prodname_GH_advanced_security %} on {% data variables.product.prodname_ghe_managed %} during the beta release.{% endif %} +{% ifversion fpt or ghes > 3.0 %}Para obter mais informações sobre a compra de {% data variables.product.prodname_GH_advanced_security %}, see "[Sobre a cobrança para {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)."{% elsif ghae %}Não há cobrança para {% data variables.product.prodname_GH_advanced_security %} em {% data variables.product.prodname_ghe_managed %} durante a versão beta.{% endif %} ## Sobre as funcionalidades de {% data variables.product.prodname_advanced_security %} diff --git a/translations/pt-BR/content/get-started/learning-about-github/access-permissions-on-github.md b/translations/pt-BR/content/get-started/learning-about-github/access-permissions-on-github.md index a13fb2da1d..e73cd1735d 100644 --- a/translations/pt-BR/content/get-started/learning-about-github/access-permissions-on-github.md +++ b/translations/pt-BR/content/get-started/learning-about-github/access-permissions-on-github.md @@ -36,6 +36,8 @@ Os integrantes da organização podem ter funções de *proprietário*{% ifversi Os *proprietários de empresa* têm poder absoluto sobre a conta corporativa e podem realizar todas as ações nela. Os *gerentes de cobrança* podem gerenciar as configurações de cobrança da sua conta corporativa. Os integrantes e colaboradores externos das organizações pertencentes à sua conta corporativa são automaticamente integrantes da conta corporativa, embora eles não tenham acesso à conta corporativa em si nem às configurações dela. Para obter mais informações, consulte "[Funções em uma empresa](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise)". +Se uma empresa usar {% data variables.product.prodname_emus %}, serão fornecidos novos os integrantes como novas contas de usuário em {% data variables.product.prodname_dotcom %} e serão totalmente gerenciados pelo provedor de identidade. O {% data variables.product.prodname_managed_users %} tem acesso somente leitura a repositórios que não fazem parte da sua empresa e não podem interagir com usuários que não são também integrantes da empresa. Nas organizações pertencentes à empresa, é possível conceder ao {% data variables.product.prodname_managed_users %} os mesmos níveis de acesso granular disponíveis para organizações regulares. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." + {% data reusables.gated-features.enterprise-accounts %} {% endif %} diff --git a/translations/pt-BR/content/get-started/learning-about-github/githubs-products.md b/translations/pt-BR/content/get-started/learning-about-github/githubs-products.md index dc6633f930..5ab7ffeaed 100644 --- a/translations/pt-BR/content/get-started/learning-about-github/githubs-products.md +++ b/translations/pt-BR/content/get-started/learning-about-github/githubs-products.md @@ -78,8 +78,8 @@ Além dos recursos disponíveis no {% data variables.product.prodname_free_team - Equipe de revisores de pull request - Lembretes agendados {% ifversion fpt %} -- The option to enable {% data variables.product.prodname_github_codespaces %} - - Organization owners can enable {% data variables.product.prodname_github_codespaces %} for the organization by setting a spending limit and granting user permissions for members of their organization. For more information, see "[Enabling Codespaces for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization)." +- A opção para habilitar {% data variables.product.prodname_github_codespaces %} + - Os proprietários da organização podem habilitar {% data variables.product.prodname_github_codespaces %} para a organização definindo um limite de gastos e concedendo permissões de usuário aos integrantes da sua organização. Para obter mais informações, consulte "[Habilitando codespaces para a sua organização](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization)". {% endif %} {% data reusables.github-actions.actions-billing %} @@ -102,6 +102,7 @@ O {% data variables.product.prodname_ghe_cloud %} também inclui: - 50GB {% data variables.product.prodname_registry %} de armazenamento - Controle de acesso para sites de {% data variables.product.prodname_pages %}. Para obter mais informações, consulte Alterar a visibilidade do seu site de {% data variables.product.prodname_pages %}" - Um acordo de nível de serviço para tempo de atividade de 99,9% por mês +- A opção de configurar sua empresa para {% data variables.product.prodname_emus %}, para que você possa fornecer e gerenciar integrantes com o seu provedor de identidade e restringir as contribuições dos integrantes para apenas a sua empresa. Para obter mais informações, consulte "Sobre {% data variables.product.prodname_emus %}." - A opção de gerenciar de forma centralizada a política e cobrança para várias organizações {% data variables.product.prodname_dotcom_the_website %} com uma conta corporativa. Para obter mais informações, consulte "Sobre contas corporativas". Você pode configurar uma versão para avaliar o {% data variables.product.prodname_ghe_cloud %}. Para obter mais informações, consulte "Configurar uma versão de avaliação do {% data variables.product.prodname_ghe_cloud %}". diff --git a/translations/pt-BR/content/get-started/learning-about-github/types-of-github-accounts.md b/translations/pt-BR/content/get-started/learning-about-github/types-of-github-accounts.md index 99bcb2d74d..68372090e1 100644 --- a/translations/pt-BR/content/get-started/learning-about-github/types-of-github-accounts.md +++ b/translations/pt-BR/content/get-started/learning-about-github/types-of-github-accounts.md @@ -64,6 +64,14 @@ Cada pessoa que utiliza {% data variables.product.product_location %} tem sua pr {% endif %} +{% ifversion fpt %} +### {% data variables.product.prodname_emus %} + +Com {% data variables.product.prodname_emus %}, em vez de usar sua conta pessoal, os integrantes de um {% data variables.product.prodname_emu_enterprise %} são contas fornecidas que usam o provedor de identidade da empresa (IdP). {% data variables.product.prodname_managed_users_caps %} efetua a autenticação usando seu IdP ao invés de um usuário e senha de {% data variables.product.prodname_dotcom_the_website %}. + +{% data variables.product.prodname_managed_users_caps %} só pode interagir com usuários, repositórios e organizações que fazem parte das suas empresas. {% data variables.product.prodname_managed_users_caps %} tem acesso somente leitura ao restante de {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." +{% endif %} + ## Contas da organização As organizações são contas compartilhadas, onde grupos de pessoas podem colaborar em vários projetos de uma vez. Os proprietários e administradores podem gerenciar o acesso de integrantes aos dados e projetos da organização com recursos avançados administrativos e de segurança. diff --git a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-ae.md b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-ae.md index aa9b1d6059..ce7e8d63fa 100644 --- a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-ae.md +++ b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-ae.md @@ -1,80 +1,80 @@ --- -title: Getting started with GitHub AE -intro: 'Get started with setting up and configuring {% data variables.product.product_name %} for {% data variables.product.product_location %}.' +title: Introdução ao GitHub AE +intro: 'Comece a configurar {% data variables.product.product_name %} para {% data variables.product.product_location %}.' versions: ghae: '*' --- -This guide will walk you through setting up, configuring, and managing settings for {% data variables.product.product_location %} on {% data variables.product.product_name %} as an enterprise owner. +Este guia irá ajudar você a configurar e gerenciar as configurações para {% data variables.product.product_location %} em {% data variables.product.product_name %} como proprietário corporativo. -## Part 1: Setting up {% data variables.product.product_name %} -To get started with {% data variables.product.product_name %}, you can create your enterprise account, initialize {% data variables.product.product_name %}, configure an IP allow list, configure user authentication and provisioning, and manage billing for {% data variables.product.product_location %}. +## Parte 1: Configurando {% data variables.product.product_name %} +Para dar os primeiros passos com {% data variables.product.product_name %}, você pode criar a conta corporativa, inicializar {% data variables.product.product_name %}, configurar uma lista de permissões de IP, configurar a autenticação e provisionamento de usuário e gerenciar a cobrança para {% data variables.product.product_location %}. -### 1. Creating your {% data variables.product.product_name %} enterprise account -You will first need to purchase {% data variables.product.product_name %}. For more information, contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact). +### 1. Criando sua conta corporativa de {% data variables.product.product_name %} +Primeiro você precisará comprar {% data variables.product.product_name %}. Para obter mais informações, entre em contato com [a equipe de vendas de {% data variables.product.prodname_dotcom %}](https://enterprise.github.com/contact). {% data reusables.github-ae.initialize-enterprise %} -### 2. Initializing {% data variables.product.product_name %} -After {% data variables.product.company_short %} creates the owner account for {% data variables.product.product_location %} on {% data variables.product.product_name %}, you will receive an email to sign in and complete the initialization. During initialization, you, as the enterprise owner, will name {% data variables.product.product_location %}, configure SAML SSO, create policies for all organizations in {% data variables.product.product_location %}, and configure a support contact for your enterprise members. Para obter mais informações, consulte "[Inicializar {% data variables.product.prodname_ghe_managed %}](/admin/configuration/configuring-your-enterprise/initializing-github-ae)". +### 2. Inicializando {% data variables.product.product_name %} +Depois de {% data variables.product.company_short %} criar a conta do proprietário para {% data variables.product.product_location %} em {% data variables.product.product_name %}, você receberá um e-mail para efetuar o login e e concluir a inicialização. Durante a inicialização, você, como o proprietário da empresa, irá nomear {% data variables.product.product_location %}, configurar o SAML SSO, criar políticas para todas as organizações em {% data variables.product.product_location %} e configurar um contato de suporte para os integrantes da empresa. Para obter mais informações, consulte "[Inicializar {% data variables.product.prodname_ghe_managed %}](/admin/configuration/configuring-your-enterprise/initializing-github-ae)". ### 3. Restringir tráfego de rede -You can configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account. Para obter mais informações, consulte "[Restringir tráfego de rede para a sua empresa](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise)". +É possível configurar uma lista de permissões para endereços IP específicos para restringir o acesso a ativos pertencentes a organizações na sua conta corporativa. Para obter mais informações, consulte "[Restringir tráfego de rede para a sua empresa](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise)". -### 4. Managing identity and access for {% data variables.product.product_location %} -You can centrally manage access to {% data variables.product.product_location %} on {% data variables.product.product_name %} from an identity provider (IdP) using SAML single sign-on (SSO) for user authentication and System for Cross-domain Identity Management (SCIM) for user provisioning. Once you configure provisioning, you can assign or unassign users to the application from the IdP, creating or disabling user accounts in the enterprise. Para obter mais informações, consulte "[Sobre identidade e gerenciamento de acesso para sua empresa](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)". +### 4. Gerenciando a identidade e o acesso para {% data variables.product.product_location %} +Você pode gerenciar centralmente o acesso a {% data variables.product.product_location %} em {% data variables.product.product_name %} a partir de um provedor de identidade (IdP) usando o logon único SAML (SSO) para autenticação de usuário e o sistema para gerenciamento de identidade de domínio cruzado (SCIM) para provisionamento de usuários. Depois de configurar o provisionamento, você poderá atribuir ou remover usuários para o aplicativo a partir do IdP, criando ou desabilitando as contas de usuários na empresa. Para obter mais informações, consulte "[Sobre identidade e gerenciamento de acesso para sua empresa](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)". -### 5. Managing billing for {% data variables.product.product_location %} -Owners of the subscription for {% data variables.product.product_location %} on {% data variables.product.product_name %} can view billing details for {% data variables.product.product_name %} in the Azure portal. For more information, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)." +### 5. Gerenciando cobrança para {% data variables.product.product_location %} +Os proprietários da assinatura de {% data variables.product.product_location %} em {% data variables.product.product_name %} podem ver informações de cobrança para {% data variables.product.product_name %} no portal do Azure. Para obter mais informações, consulte "[Gerenciando a cobrança da sua empresa](/admin/overview/managing-billing-for-your-enterprise)". -## Part 2: Organizing and managing enterprise members -As an enterprise owner for {% data variables.product.product_name %}, you can manage settings on user, repository, team, and organization levels. You can manage members of {% data variables.product.product_location %}, create and manage organizations, set policies for repository management, and create and manage teams. +## Parte 2: Organização e gestão dos integrantes da empresa +Como proprietário corporativo de {% data variables.product.product_name %}, você pode gerenciar as configurações nos níveis do usuário, repositório, equipe e organização. Você pode gerenciar os integrantes de {% data variables.product.product_location %}, criar e gerenciar organizações, definir políticas para o gerenciamento do repositório e criar e gerenciar equipes. -### 1. Managing members of {% data variables.product.product_location %} +### 1. Gerenciando integrantes de {% data variables.product.product_location %} {% data reusables.getting-started.managing-enterprise-members %} ### 2. Criar organizações {% data reusables.getting-started.creating-organizations %} -### 3. Adding members to organizations +### 3. Adicionando integrantes a organizações {% data reusables.getting-started.adding-members-to-organizations %} ### 4. Criar equipes {% data reusables.getting-started.creating-teams %} -### 5. Setting organization and repository permission levels +### 5. Definindo níveis de permissões para a organização e para o repositório {% data reusables.getting-started.setting-org-and-repo-permissions %} -### 6. Enforcing repository management policies +### 6. Aplicando políticas de gerenciamento do repositório {% data reusables.getting-started.enforcing-repo-management-policies %} -## Part 3: Building securely -To increase the security of {% data variables.product.product_location %}, you can monitor {% data variables.product.product_location %} and configure security and analysis features for your organizations. +## Parte 3: Criando com segurança +Para aumentar a segurança de {% data variables.product.product_location %}, você pode monitorar {% data variables.product.product_location %} e configurar as funcionalidades de segurança e análise das suas organizações. -### 1. Monitoring {% data variables.product.product_location %} -You can monitor {% data variables.product.product_location %} with your activity dashboard and audit logging. For more information, see "[Monitoring activity in your enterprise](/admin/user-management/monitoring-activity-in-your-enterprise)." +### 1. Monitorando {% data variables.product.product_location %} +Você pode monitorar {% data variables.product.product_location %} com o seu painel de atividade e log de auditoria. Para obter mais informações, consulte "[Atividade de monitoramento na sua empresa](/admin/user-management/monitoring-activity-in-your-enterprise)". -### 2. Configuring security features for your organizations +### 2. Configurar as funcionalidades de segurança para as suas organizações {% data reusables.getting-started.configuring-security-features %} -## Part 4: Customizing and automating work on {% data variables.product.product_location %} -You can customize and automate work in organizations in {% data variables.product.product_location %} with the {% data variables.product.prodname_dotcom %} API, {% data variables.product.prodname_actions %}, and {% data variables.product.prodname_pages %}. +## Parte 4: Personalizando e automatizando o trabalho em {% data variables.product.product_location %} +Você pode personalizar e automatizar o trabalho em organizações em {% data variables.product.product_location %} com a API de {% data variables.product.prodname_dotcom %}, {% data variables.product.prodname_actions %} e {% data variables.product.prodname_pages %}. -### 1. Using the {% data variables.product.prodname_dotcom %} API +### 1. Usando a API de {% data variables.product.prodname_dotcom %} {% data reusables.getting-started.api %} -### 2. Building {% data variables.product.prodname_actions %} +### 2. Criando {% data variables.product.prodname_actions %} {% data reusables.getting-started.actions %} -For more information on enabling and configuring {% data variables.product.prodname_actions %} for {% data variables.product.product_name %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae)." +Para obter mais informações sobre como habilitar e configurar {% data variables.product.prodname_actions %} para {% data variables.product.product_name %}, consulte "[Primeiros passos com {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae)". ### 3. Usar {% data variables.product.prodname_pages %} {% data reusables.getting-started.github-pages-enterprise %} -## Part 5: Using {% data variables.product.prodname_dotcom %}'s learning and support resources -Your enterprise members can learn more about Git and {% data variables.product.prodname_dotcom %} with our learning resources, and you can get the support you need with {% data variables.product.prodname_dotcom %} Enterprise Support. +## Parte 5: Usando o aprendizado de {% data variables.product.prodname_dotcom %} e os recursos de suporte +Os integrantes da sua empresa podem aprender mais sobre Git e {% data variables.product.prodname_dotcom %} com nossos recursos de aprendizado. e você pode obter o suporte de que precisa com o Suporte do Enterprise de {% data variables.product.prodname_dotcom %}. -### 1. Learning with {% data variables.product.prodname_learning %} +### 1. Aprendendo com {% data variables.product.prodname_learning %} {% data reusables.getting-started.learning-lab-enterprise %} -### 2. Working with {% data variables.product.prodname_dotcom %} Enterprise Support +### 2. Trabalhando com o Suporte do Enterprise de {% data variables.product.prodname_dotcom %} {% data reusables.getting-started.contact-support-enterprise %} diff --git a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md index e3d5f92c80..2daa92ba08 100644 --- a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md +++ b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md @@ -1,178 +1,210 @@ --- -title: Getting started with GitHub Enterprise Cloud -intro: 'Get started with setting up and managing your {% data variables.product.prodname_ghe_cloud %} organization or enterprise account.' +title: Introdução ao GitHub Enterprise Cloud +intro: 'Comece a criar e gerenciar sua organização ou conta corporativa de {% data variables.product.prodname_ghe_cloud %}.' versions: fpt: '*' --- -This guide will walk you through setting up, configuring and managing your {% data variables.product.prodname_ghe_cloud %} account as an organization or enterprise owner. +Este guia irá ajudar você a configurar e gerenciar sua conta de {% data variables.product.prodname_ghe_cloud %} como uma organização ou proprietário da empresa. {% data reusables.enterprise.ghec-cta-button %} -## Part 1: Choosing your account type +## Parte 1: Escolhendo o seu tipo de conta -{% data variables.product.prodname_dotcom %} provides two types of Enterprise products: +{% data variables.product.prodname_dotcom %} fornece dois tipos de produtos corporativos: - **{% data variables.product.prodname_ghe_cloud %}** - **{% data variables.product.prodname_ghe_server %}** -The main difference between the products is that {% data variables.product.prodname_ghe_cloud %} is hosted by {% data variables.product.prodname_dotcom %}, while {% data variables.product.prodname_ghe_server %} is self-hosted. +A principal diferença entre os produtos é que {% data variables.product.prodname_ghe_cloud %} é hospedado por {% data variables.product.prodname_dotcom %}, enquanto {% data variables.product.prodname_ghe_server %} é auto-hospedado. -Within the {% data variables.product.prodname_ghe_cloud %} product, there are two different types of account that you can use: +Com {% data variables.product.prodname_ghe_cloud %}, você tem a opção de usar {% data variables.product.prodname_emus %}. {% data reusables.enterprise-accounts.emu-short-summary %} -- A single organization account -- An enterprise account that contains multiple organizations +Se você optar por deixar seus integrantes criarem e gerenciarem suas próprias contas de usuário, há dois tipos de contas que você pode usar com {% data variables.product.prodname_ghe_cloud %}: -In either scenario, your users will use their own self-created user account and you'll invite them to join. -### 1. Understanding the differences between an organization account and enterprise account +- Uma conta de organização única +- Uma conta corporativa que contém várias organizações -Both organization and enterprise accounts are available with {% data variables.product.prodname_ghe_cloud %}. An organization is a shared account where groups of people can collaborate across many projects at once, and owners and administrators can manage access to data and projects. An enterprise account enables collaboration between multiple organizations, and allows owners to centrally manage policy, billing and security for these organizations. For more information on the differences, see "[Organizations and enterprise accounts](/organizations/collaborating-with-groups-in-organizations/about-organizations#organizations-and-enterprise-accounts)." +### 1. Compreender as diferenças entre uma conta de organização e a conta corporativa -If you choose an enterprise account, keep in mind that some policies can be set only at an organization level, while others can be enforced for all organizations in an enterprise. +As contas da organização e da empresa estão disponíveis com {% data variables.product.prodname_ghe_cloud %}. Uma organização é uma conta compartilhada em que grupos de pessoas podem colaborar em vários projetos de uma só vez, e os proprietários e administradores podem gerenciar o acesso a dados e projetos. Uma conta corporativa permite a colaboração entre várias organizações e permite que os proprietários gerenciem centralmente a política, cobrança e segurança dessas organizações. Para obter mais informações sobre as diferenças, consulte "[Organizações e contas corporativas](/organizations/collaborating-with-groups-in-organizations/about-organizations#organizations-and-enterprise-accounts)". -Once you choose the account type you would like, you can proceed to setting up your account. In each of the sections in this guide, proceed to either the single organization or enterprise account section based on your account type. -## Part 2: Setting up your account -To get started with {% data variables.product.prodname_ghe_cloud %}, you will want to create your organization or enterprise account and set up and view billing settings, subscriptions and usage. -### Setting up a single organization account with {% data variables.product.prodname_ghe_cloud %} + +Se você escolher uma conta corporativa, tenha em mente que algumas políticas só podem ser definidas no nível organizacional, enquanto outras podem ser aplicadas a todas as organizações de uma empresa. + +Depois de escolher o tipo de conta que você desejar, você poderá continuar a criar a sua conta. Em cada uma das seções deste guia, acesse a seção de organização única ou conta corporativa com base no seu tipo de conta. + +## Parte 2: Configurando a sua conta +Para começar com {% data variables.product.prodname_ghe_cloud %}, você deverá criar sua conta organizativa ou corporativa e configurar e ver as configurações de cobrança, assinaturas e uso. +### Como criar uma conta de organização única com {% data variables.product.prodname_ghe_cloud %} #### 1. Sobre organizações -As organizações são contas compartilhadas, onde grupos de pessoas podem colaborar em vários projetos de uma vez. With {% data variables.product.prodname_ghe_cloud %}, owners and administrators can manage their organization with sophisticated user authentication and management, as well as escalated support and security options. Para obter mais informações, consulte "[Sobre organizações](/organizations/collaborating-with-groups-in-organizations/about-organizations)". -#### 2. Creating or upgrading an organization account +As organizações são contas compartilhadas, onde grupos de pessoas podem colaborar em vários projetos de uma vez. Com o {% data variables.product.prodname_ghe_cloud %}, os proprietários e administradores podem gerenciar sua organização com autenticação e gestão de usuário sofisticada, bem como com opções de segurança e suporte escaladas. Para obter mais informações, consulte "[Sobre organizações](/organizations/collaborating-with-groups-in-organizations/about-organizations)". +#### 2. Criando ou atualizando a conta de uma organização -To use an organization account with {% data variables.product.prodname_ghe_cloud %}, you will first need to create an organization. When prompted to choose a plan, select "Enterprise". 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)". +Para usar a conta de uma organização com {% data variables.product.prodname_ghe_cloud %}, primeiro você precisará criar uma organização. Quando solicitado para escolher um plano, selecione "Enterprise". 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)". -Alternatively, if you have an existing organization account that you would like to upgrade, follow the steps in "[Upgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription#upgrading-your-organizations-subscription)." -#### 3. Setting up and managing billing +Como alternativa, se você tiver a conta de uma organização existente que você gostaria de atualizar, siga as etapas em "[atualizando a sua assinatura de {% data variables.product.prodname_dotcom %}](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription#upgrading-your-organizations-subscription)". +#### 3. Configuração e gerenciamento de cobrança -When you choose to use an organization account with {% data variables.product.prodname_ghe_cloud %}, you'll first have access to a [14-day trial](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud). If you don't purchase {% data variables.product.prodname_enterprise %} or {% data variables.product.prodname_team %} before your trial ends, your organization will be downgraded to {% data variables.product.prodname_free_user %} and lose access to any advanced tooling and features that are only included with paid products. For more information, see "[Finishing your trial](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud#finishing-your-trial)." +Ao optar por usar uma conta de organização com {% data variables.product.prodname_ghe_cloud %}, primeiro você terá acesso a um [](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud)de teste de 14 dias. Se você não comprar {% data variables.product.prodname_enterprise %} ou {% data variables.product.prodname_team %} antes do seu período de teste terminar, a sua organização será rebaixada para {% data variables.product.prodname_free_user %} e você perderá acesso a quaisquer ferramentas avançadas e recursos que sejam incluídos apenas com produtos pagos. Para obter mais informações, consulte "[Concluindo o seu teste](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud#finishing-your-trial)". -Your organization's billing settings page allows you to manage settings like your payment method and billing cycle, view information about your subscription, and upgrade your storage and {% data variables.product.prodname_actions %} minutes. For more information on managing your billing settings, see "[Managing your {% data variables.product.prodname_dotcom %} billing settings](/billing/managing-your-github-billing-settings)." +A página de configurações de cobrança da sua organização permite que você gerencie configurações como seu método de pagamento e ciclo de cobrança, exiba informações sobre sua assinatura e faça a atualização do seu armazenamento e minutos de {% data variables.product.prodname_actions %}. Para obter mais informações sobre como gerenciar suas configurações de cobrança, consulte "[Gerenciando suas configurações de cobrança de {% data variables.product.prodname_dotcom %}](/billing/managing-your-github-billing-settings)". -Only organization members with the *owner* or *billing manager* role can access or change billing settings for your organization. A billing manager is a user who manages the billing settings for your organization and does not use a paid license in your organization's subscription. For more information on adding a billing manager to your organization, see "[Adding a billing manager to your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)." +Apenas os integrantes da organização com a função de *proprietário* ou *gerente de cobrança* podem acessar ou alterar as configurações de cobrança da sua organização. Um gerente de cobrança é um usuário que gerencia as configurações de cobrança para sua organização e não usa uma licença paga na assinatura da sua organização. Para obter mais informações sobre como adicionar um gerente de cobrança à sua organização, consulte "[Adicionando um gerente de cobrança à sua organização](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)". -### Setting up an enterprise account with {% data variables.product.prodname_ghe_cloud %} +### Configurando uma conta corporativa com {% data variables.product.prodname_ghe_cloud %} {% note %} -To get an enterprise account created for you, contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact). +Para obter uma conta corporativa criada para você, entre em contato com [a equipe de vendas de {% data variables.product.prodname_dotcom %}](https://enterprise.github.com/contact). {% endnote %} #### 1. Sobre contas corporativas -An enterprise account allows you to centrally manage policy and settings for multiple {% data variables.product.prodname_dotcom %} organizations, including member access, billing and usage and security. Para obter mais informações, consulte "[Sobre contas corporativas](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts)". +Uma conta corporativa permite que você gerencie centralmente as políticas e configurações para várias organizações {% data variables.product.prodname_dotcom %}, incluindo acesso de integrantes, cobrança e uso e segurança. Para obter mais informações, consulte "[Sobre contas corporativas](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts)". #### 2. Adicionar organizações à suas conta corporativa -É possível criar novas organizações para serem gerenciadas em sua conta corporativa. For more information, see "[Adding organizations to your enterprise](/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account)." +É possível criar novas organizações para serem gerenciadas em sua conta corporativa. Para obter mais informações, consulte "[Adicionando organizações à sua empresa](/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account)". -Contact your {% data variables.product.prodname_dotcom %} sales account representative if you want to transfer an existing organization to your enterprise account. +Entre em contato com o seu representante da conta de vendas de {% data variables.product.prodname_dotcom %} se você quiser transferir uma organização existente para a sua conta corporativa. #### 3. Exibir assinatura e uso da conta corporativa -You can view your current subscription, license usage, invoices, payment history, and other billing information for your enterprise account at any time. Both enterprise owners and billing managers can access and manage billing settings for enterprise accounts. Para obter mais informações, consulte "[Exibir a assinatura e o uso de sua conta corporativa](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/viewing-the-subscription-and-usage-for-your-enterprise-account)". +Você pode visualizar a sua assinatura atual, uso da licença, faturas, histórico de pagamentos e outras informações de cobrança para sua conta corporativa a qualquer momento. Os proprietários da empresa e os gerentes de cobrança podem acessar e gerenciar as configurações de cobrança para contas corporativas. Para obter mais informações, consulte "[Exibir a assinatura e o uso de sua conta corporativa](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/viewing-the-subscription-and-usage-for-your-enterprise-account)". -## Part 3: Managing your organization or enterprise members and teams with {% data variables.product.prodname_ghe_cloud %} +## Parte 3: Gerenciando seus integrantes e equipes da empresa com {% data variables.product.prodname_ghe_cloud %} -### Managing members and teams in your organization -You can set permissions and member roles, create and manage teams, and give people access to repositories in your organization. -#### 1. Managing members of your organization +### Gerenciando integrantes e equipes na sua organização +Você pode definir permissões e funções dos integrantes, criar e gerenciar equipes e conceder acesso a repositórios na sua organização. +#### 1. Gerenciando integrantes da sua organização {% data reusables.getting-started.managing-org-members %} -#### 2. Organization permissions and roles +#### 2. Permissões e funções da organização {% data reusables.getting-started.org-permissions-and-roles %} -#### 3. About and creating teams +#### 3. Sobre e criar equipes {% data reusables.getting-started.about-and-creating-teams %} -#### 4. Managing team settings +#### 4. Gerenciando as configurações de equipe {% data reusables.getting-started.managing-team-settings %} -#### 5. Giving people and teams access to repositories, project boards and apps +#### 5. Dar às pessoas e equipes acesso a repositórios, seções de projetos e aplicativos {% data reusables.getting-started.giving-access-to-repositories-projects-apps %} -### Managing members of an enterprise account -Managing members of an enterprise is separate from managing members or teams in an organization. It is important to note that enterprise owners or administrators cannot access organization-level settings or manage members for organizations in their enterprise unless they are made an organization owner. For more information, see the above section, "[Managing members and teams in your organization](#managing-members-and-teams-in-your-organization)." -#### 1. Assigning roles in an enterprise -By default, everyone in an enterprise is a member of the enterprise. There are also administrative roles, including enterprise owner and billing manager, that have different levels of access to enterprise settings and data. Para obter mais informações, consulte "[Funções em uma empresa](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)". +### Gerenciando integrantes de uma conta corporativa +O gerenciamento dos integrantes de uma empresa é separado da gestão dos integrantes ou equipes em uma organização. É importante notar que os proprietários ou administradores da empresa não podem acessar as configurações a nível da organização ou gerenciar integrantes de organizações na sua empresa, a não ser que sejam proprietários de uma organização. Para obter mais informações, consulte a seção acima, "[Gerenciar integrantes e equipes da sua organização](#managing-members-and-teams-in-your-organization)". + +Se sua empresa usar {% data variables.product.prodname_emus %}, seus integrantes serão totalmente gerenciados por meio de seu provedor de identidade. As funções de adicionar integrantes, fazer alterações na sua associação e atribuir cargos são geranciadas usando seu IdP. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." + +Se a sua empresa não usar {% data variables.product.prodname_emus %}, siga as etapas abaixo. + +#### 1. Atribuindo funções em uma empresa +Por padrão, todas as pessoas em uma empresa são integrantes da empresa. Além disso, há funções administrativas, que incluem o proprietário da empresa e o gerente de cobrança, que têm diferentes níveis de acesso às configurações e dados da empresa. Para obter mais informações, consulte "[Funções em uma empresa](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)". #### 2. Convidar pessoas para gerenciar sua empresa -You can invite people to manage your enterprise as enterprise owners or billing managers, as well as remove those who no longer need access. For more information, see "[Inviting people to manage your enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)." +Você pode convidar pessoas para gerenciar a sua empresa como, por exemplo, proprietários corporativos ou gerentes de cobrança, bem como remover aqueles que não precisam mais de acesso. Para obter mais informações, consulte[Convidando pessoas para gerenciar a sua empresa](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)". -You can also grant enterprise members the ability to manage support tickets in the support portal. Para obter mais informações, consulte "[Gerenciar direitos de suporte para a sua empresa](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)". +Você também pode conceder aos integrandes da empresa a capacidade de gerenciar tíquetes de suporte no portal de suporte. Para obter mais informações, consulte "[Gerenciar direitos de suporte para a sua empresa](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)". #### 3. Visualizar pessoas na sua empresa -To audit access to enterprise-owned resources or user license usage, you can view every enterprise administrator, enterprise member, and outside collaborator in your enterprise. You can see the organizations that a member belongs to and the specific repositories that an outside collaborator has access to. Para obter mais informações, consulte "[Visualizar pessoas na sua empresa](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/viewing-people-in-your-enterprise)". +Para auditoria ao acesso a recursos pertencentes à empresa ou ao uso da licença de usuário, você pode ver todos os administradores corporativos, integrantes da empresa e colaboradores externos da sua empresa. Você pode ver as organizações às quais um integrante pertence e os repositórios específicos aos quais um colaborador externo tem acesso. Para obter mais informações, consulte "[Visualizar pessoas na sua empresa](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/viewing-people-in-your-enterprise)". -## Part 4: Managing security with {% data variables.product.prodname_ghe_cloud %} +## Parte 4: Gerenciando a segurança com {% data variables.product.prodname_ghe_cloud %} -### Managing security for a single organization -You can help keep your organization secure by requiring two-factor authentication, configuring security features, reviewing your organization's audit log and integrations, and enabling SAML single sign-on and team synchronization. -#### 1. Requiring two-factor authentication +* [Gerenciando a segurança de uma única organização](#managing-security-for-a-single-organization) +* [Gerenciando a segurança de {% data variables.product.prodname_emu_enterprise %}](#managing-security-for-an-enterprise-with-managed-users) +* [Gerenciando a segurança de uma conta corporativa sem {% data variables.product.prodname_managed_users %}](#managing-security-for-an-enterprise-account-without-managed-users) + +### Gerenciando a segurança de uma única organização +Você pode ajudar a manter sua organização segura exigindo autenticação de dois fatores, configurando recursos de segurança, revisando o log de auditoria e as integrações da sua organização e habilitando a sincronização de equipe e logon único SAML. +#### 1. Exigindo a autenticação de dois fatores {% data reusables.getting-started.requiring-2fa %} -#### 2. Configuring security features for your organization +#### 2. Configurando recursos de segurança para a sua organização {% data reusables.getting-started.configuring-security-features %} -#### 3. Reviewing your organization's audit log and integrations +#### 3. Revisando o log de auditoria e as integrações da sua organização {% data reusables.getting-started.reviewing-org-audit-log-and-integrations %} -#### 4. Enabling and enforcing SAML single sign-on for your organization -If you manage your applications and the identities of your organization members with an identity provider (IdP), you can configure SAML single-sign-on (SSO) to control and secure access to organization resources like repositories, issues and pull requests. When members of your organization access organization resources that use SAML SSO, {% data variables.product.prodname_dotcom %} will redirect them to your IdP to authenticate. 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)." +#### 4. Habilitando e aplicando o logon único SAML para a sua organização +Se você gerenciar seus aplicativos e as identidades dos integrantes da sua organização com um provedor de identidade (IdP), você poderá configurar logon único SAML (SSO) para controlar e proteger o acesso aos recursos da organização, como repositórios, problemas e pull requests. Quando os integrantes da sua organização acessam os recursos da organização que usam o SAML SSO, {% data variables.product.prodname_dotcom %} irá redirecioná-los para o seu dispositivo para autenticação. 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)". -Organization owners can choose to disable, enable but not enforce, or enable and enforce SAML SSO. For more information, see "[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)" and "[Enforcing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)." +Os proprietários da organização podem optar por habilitar e desabilitar, mas não implementar, habilitar e aplicar o SAML SSO. Para obter mais informações, consulte "[Habilitando e testando o login único SAML para a sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)" e "[Aplicando o login único SAML paraa sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)." #### 5. Gerenciar a sincronização de equipe para a sua organização -Organization owners can enable team synchronization between your identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organization owners and team maintainers to connect teams in your organization with IdP groups. Para obter mais informações, consulte "[Gerenciar a sincronização de equipe para a sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)". +Os proprietários da organização podem habilitar a sincronização de equipes entre o seu provedor de identidade (IdP) e {% data variables.product.prodname_dotcom %} para permitir que os proprietários da organização e mantenedores de equipes conectem equipes na sua organização aos grupos do IdP. Para obter mais informações, consulte "[Gerenciar a sincronização de equipe para a sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)". -### Managing security for an enterprise account with multiple organizations -To manage security for your enterprise, you can require two-factor authentication, manage allowed IP addresses, enable SAML single sign-on and team synchronization at an enterprise level, and sign up for and enforce GitHub Advanced Security features. -#### 1. Requiring two-factor authentication and managing allowed IP addresses for organizations in your enterprise account -Os proprietários corporativos podem exigir que integrantes da organização, gerentes de cobrança e colaboradores externos em todas as organizações pertencentes a uma conta corporativa usem autenticação de dois fatores para proteger suas contas pessoais. Before doing so, we recommend notifying all who have access to organizations in your enterprise. You can also configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account. +### Gerenciando a segurança de {% data variables.product.prodname_emu_enterprise %} -For more information on enforcing two-factor authentication and allowed IP address lists, see "[Enforcing security settings in your enterprise account](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-security-settings-in-your-enterprise-account#managing-allowed-ip-addresses-for-organizations-in-your-enterprise-account)." -#### 2. Enabling and enforcing SAML single sign-on for organizations in your enterprise account -You can centrally manage access to your enterprise's resources, organization membership and team membership using your IdP and SAM single sign-on (SSO). Enterprise owners can enable SAML SSO across all organizations owned by an enterprise account. For more information, see "[About identity and access management for your enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/about-identity-and-access-management-for-your-enterprise-account)." +Com {% data variables.product.prodname_emus %}, o acesso e a identidade são gerenciados centralmente por meio do seu provedor de identidade. A autenticação de dois fatores e outros requisitos de login devem ser habilitados e aplicados no seu IdP. -#### 3. Managing team synchronization -You can enable and manage team sychronization between an identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organizations owned by your enterprise account to manage team membership with IdP groups. Para obter mais informações, consulte "[Gerenciar a sincronização de equipes para organizações na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/managing-team-synchronization-for-organizations-in-your-enterprise-account)". +#### 1. Habilitando e o provisionamento de um logon único SAML no seu {% data variables.product.prodname_emu_enterprise %} -#### 4. Enforcing policies for Advanced Security features in your enterprise account -If you have a GitHub Advanced Security license for your enterprise account, you can enforce policies to manage {% data variables.product.prodname_dotcom %} Advanced Security features for organizations owned by an enterprise account. For more information, see "[Enforcing policies for Advanced Security in your enterprise account](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-policies-for-advanced-security-in-your-enterprise-account)." +Em um {% data variables.product.prodname_emu_enterprise %}, todos os integrantes são provisionados e gerenciados pelo seu provedor de identidade. Você deve habilitar o provisionamento SAML SSO e SCIM antes de começar a usar a sua empresa. Para mais informações sobre a configuração do SAML SSO e provisionamento para um {% data variables.product.prodname_emu_enterprise %}, consulte "[Configurando o logon único SAML para usuários gerenciados pela empresa](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." -## Part 5: Managing organization and enterprise level policies and settings +#### 2. Gerenciando equipes no seu {% data variables.product.prodname_emu_enterprise %} com o seu provedor de identidade -### Managing settings for a single organization -To manage and moderate your organization, you can set organization policies, manage permissions for repository changes, and use organization-level community health files. -#### 1. Managing organization policies +Você pode conectar as equipes das suas organizações a grupos de segurança do seu provedor de identidade, gerenciar integrantes das suas equipes e acesso aos repositórios por meio do seu IdP. Para obter mais informações, consulte "[Gerenciar associações de equipe com grupos de provedor de identidade](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)". + +#### 3. Gerenciar endereços IP permitidos para organizações no seu {% data variables.product.prodname_emu_enterprise %} + +Você pode configurar uma lista de permissões para endereços IP específicos para restringir o acesso a ativos pertencentes a organizações no seu {% data variables.product.prodname_emu_enterprise %}. Para obter mais informações, consulte "[Aplicar as configurações de segurança na conta corporativa](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-security-settings-in-your-enterprise-account#managing-allowed-ip-addresses-for-organizations-in-your-enterprise-account)". + +#### 4. Aplicando políticas de segurança avançada no seu {% data variables.product.prodname_emu_enterprise %} +{% data reusables.getting-started.enterprise-advanced-security %} + +### Gerenciando a segurança de uma conta corporativa sem {% data variables.product.prodname_managed_users %} +Para gerenciar a segurança da sua empresa, você pode exigir autenticação de dois fatores, gerenciar endereços IP permitidos, habilitar o logon único SAML e a sincronização de equipes no nível corporativo e inscrever-se aplicar as funcionalidades do GitHub Advanced Security. + +#### 1. Exigir autenticação de dois fatores e gerenciar endereços IP permitidos para organizações na conta corporativa +Os proprietários corporativos podem exigir que integrantes da organização, gerentes de cobrança e colaboradores externos em todas as organizações pertencentes a uma conta corporativa usem autenticação de dois fatores para proteger suas contas pessoais. Antes de fazer isso, recomendamos que você notifique todas as pessoas que têm acesso a organizações da sua empresa. Você também pode configurar uma lista de permissões para endereços IP específicos para restringir o acesso a ativos pertencentes a organizações na sua conta corporativa. + +Para obter mais informações sobre a aplicação da autenticação de dois fatores e listas de endereços IP permitidas, consulte "[Aplicando as configurações de segurança na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-security-settings-in-your-enterprise-account#managing-allowed-ip-addresses-for-organizations-in-your-enterprise-account)". +#### 2. Habilitar e aplicar o login único SAML para organizações na sua conta corporativa +Você pode gerenciar centralmente o acesso aos recursos da sua empresa, a associação à organização e a associação à equipe usando seu IdP e o logon único SAML (SSO). Os proprietários corporativos podem habilitar o SAML SSO em todas as organizações pertencentes a uma conta corporativa. Para obter mais informações, consulte "[Sobre a identidade e gerenciamento de acesso para a sua conta corporativa](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/about-identity-and-access-management-for-your-enterprise-account)". + +#### 3. Gerenciando a sincronização de equipe +Você pode habilitar e gerenciar a simulação de equipes entre um provedor de identidade (IdP) e {% data variables.product.prodname_dotcom %} para permitir que as organizações pertencentes à sua conta corporativa gerenciem a associação de equipes com grupos IdP. Para obter mais informações, consulte "[Gerenciar a sincronização de equipes para organizações na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/managing-team-synchronization-for-organizations-in-your-enterprise-account)". + +#### 4. Aplicando políticas de segurança avançada na sua conta corporativa +{% data reusables.getting-started.enterprise-advanced-security %} + +## Parte 5: Gerenciar políticas e configurações da organização e do nível empresarial + +### Gerenciando configurações para uma única organização +Para gerenciar e moderar sua organização, você pode definir políticas da organização, gerenciar permissões para alterações de repositórios e usar arquivos de saúde da comunidade no nível da organização. +#### 1. Gerenciando as políticas da organização {% data reusables.getting-started.managing-org-policies %} -#### 2. Managing repository changes +#### 2. Gerenciando alterações de repositório {% data reusables.getting-started.managing-repo-changes %} -#### 3. Using organization-level community health files and moderation tools +#### 3. Usando arquivos de saúde da comunidade no nível da organização e as ferramentas de moderação {% data reusables.getting-started.using-org-community-files-and-moderation-tools %} -### Managing settings for an enterprise account -To manage and moderate your enterprise, you can set policies for organizations within the enterprise, view audit logs, configure webhooks, and restrict email notifications. -#### 1. Managing policies for organizations in your enterprise account +### Gerenciando as configurações para uma conta corporativa +Para gerenciar e moderar sua empresa, você pode definir políticas para organizações dentro da empresa, visualizar logs de auditoria, configurar webhooks e restringir notificações de e-mail. +#### 1. Gerenciar políticas para organizações na sua conta corporativa -You can choose to enforce a number of policies for all organizations owned by your enterprise, or choose to allow these policies to be set in each organization. Types of policies you can enforce include repository management, project board, and team policies. For more information, see "[Set organization policies](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account)." -#### 2. Viewing audit logs, configuring webhooks, and restricting email notifications for your enterprise -You can view actions from all of the organizations owned by your enterprise account in the enterprise audit log. You can also configure webhooks to receive events from organizations owned by your enterprise account. For more information, see "[Viewing the audit logs for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account)" and "[Configuring webooks for organization events in your enterprise](/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/configuring-webhooks-for-organization-events-in-your-enterprise-account)." +Você pode optar por aplicar várias políticas para todas as organizações pertencentes à sua empresa, ou escolher permitir que essas políticas sejam definidas em cada organização. Os tipos de políticas que você pode aplicar incluem gerenciamento de repositórios, quadro de projetos e políticas de equipe. Para obter mais informações, consulte "[Definir políticas da organização](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account)". +#### 2. Visualizando logs de auditoria, configurando webhooks, e restringindo notificações de e-mail para a sua empresa +Você pode visualizar as ações de todas as organizações pertencentes à sua conta corporativa no log de auditoria da empresa. Você também pode configurar webhooks para receber eventos de organizações pertencentes à sua conta corporativa. Para obter mais informações, consulte "[Visualizando os logs de auditoria para organizações na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account)" e "[Configurando webooks para eventos da organização na sua empresa](/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/configuring-webhooks-for-organization-events-in-your-enterprise-account)". -You can also restrict email notifications for your enterprise account so that enterprise members can only use an email address in a verified or approved domain to receive notifications. For more information, see "[Restricting email notifications for your enterprise account](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/restricting-email-notifications-for-your-enterprise-account)." +Você também pode restringir as notificações de e-mail da conta corporativa para que os integrantes da empresa só possam usar um endereço de e-mail em um domínio verificado ou aprovado para receber notificações. Para obter mais informações, consulte "[Restringindo notificações de e-mail para a sua conta corporativa](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/restricting-email-notifications-for-your-enterprise-account)". -## Part 6: Customizing and automating your organization or enterprise's work on {% data variables.product.prodname_dotcom %} -Members of your organization or enterprise can use tools from the {% data variables.product.prodname_marketplace %}, the {% data variables.product.product_name %} API, and existing {% data variables.product.product_name %} features to customize and automate your work. +## Parte 6: Personalizar e automatizar o trabalho da sua organização ou empresa em {% data variables.product.prodname_dotcom %} +Os integrantes da sua organização ou empresa podem usar ferramentas de {% data variables.product.prodname_marketplace %}, a API de {% data variables.product.product_name %} e as funcionalidades de {% data variables.product.product_name %} existentes para personalizar e automatizar seu trabalho. ### 1. Usar {% data variables.product.prodname_marketplace %} {% data reusables.getting-started.marketplace %} -### 2. Using the {% data variables.product.prodname_dotcom %} API +### 2. Usando a API de {% data variables.product.prodname_dotcom %} {% data reusables.getting-started.api %} -### 3. Building {% data variables.product.prodname_actions %} +### 3. Criando {% data variables.product.prodname_actions %} {% data reusables.getting-started.actions %} -### 4. Publishing and managing {% data variables.product.prodname_registry %} +### 4. Publicando e gerenciando {% data variables.product.prodname_registry %} {% data reusables.getting-started.packages %} ### 5. Usar {% data variables.product.prodname_pages %} -{% data variables.product.prodname_pages %} is a static site hosting service that takes HTML, CSS, and JavaScript files straight from a repository and publishes a website. You can manage the publication of {% data variables.product.prodname_pages %} sites at the organization level. 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)" and "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)." -## Part 7: Participating in {% data variables.product.prodname_dotcom %}'s community +{% data variables.product.prodname_pages %} is a static site hosting service that takes HTML, CSS, and JavaScript files straight from a repository and publishes a website. Você pode gerenciar a publicação de sites de {% data variables.product.prodname_pages %} no nível da organização. Para obter mais informações, consulte "[Gerenciando a publicação de sites de {% data variables.product.prodname_pages %} para a sua organização](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)" e "[Sobre {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)". +## Parte 7: Participando da comunidade de {% data variables.product.prodname_dotcom %} -Members of your organization or enterprise can use GitHub's learning and support resources to get the help they need. You can also support the open source community. -### 1. Learning with {% data variables.product.prodname_learning %} -Members of your organization or enterprise can learn new skills by completing fun, realistic projects in your very own GitHub repository with [{% data variables.product.prodname_learning %}](https://lab.github.com/). Each course is a hands-on lesson created by the GitHub community and taught by the friendly Learning Lab bot. +Os integrantes da sua organização ou empresa podem usar os recursos de aprendizado e suporte do GitHub para obter a ajuda de que precisam. Você também pode apoiar a comunidade de código aberto. +### 1. Aprendendo com {% data variables.product.prodname_learning %} +Os integrantes da sua organização ou empresa podem aprender novas habilidades realizando projetos divertidos e realistas no seu repositório do GitHub com [{% data variables.product.prodname_learning %}](https://lab.github.com/). Each course is a hands-on lesson created by the GitHub community and taught by the friendly Learning Lab bot. -For more information, see "[Git and {% data variables.product.prodname_dotcom %} learning resources](/github/getting-started-with-github/quickstart/git-and-github-learning-resources)." -### 2. Supporting the open source community +Para obter mais informações, consulte "[Git e recursos de aprendizado de {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/quickstart/git-and-github-learning-resources). " +### 2. Apoiar a comunidade de código aberto {% data reusables.getting-started.sponsors %} ### 3. Entrar em contato com o {% data variables.contact.github_support %} {% data reusables.getting-started.contact-support %} -{% data variables.product.prodname_ghe_cloud %} allows you to submit priority support requests with a target eight-hour response time. For more information, see "[{% data variables.product.prodname_ghe_cloud %} support](/github/working-with-github-support/github-enterprise-cloud-support)." +{% data variables.product.prodname_ghe_cloud %} permite que você envie solicitações de suporte prioritárias com um tempo de resposta de oito horas. Para obter mais informações, consulte "[suporte do {% data variables.product.prodname_ghe_cloud %}](/github/working-with-github-support/github-enterprise-cloud-support)". diff --git a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-server.md b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-server.md index 18295bb95c..9f485ec38d 100644 --- a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-server.md +++ b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-server.md @@ -1,120 +1,120 @@ --- title: Introdução ao GitHub Enterprise Server -intro: 'Get started with setting up and managing {% data variables.product.product_location %}.' +intro: 'Comece a configurar e gerenciar {% data variables.product.product_location %}.' versions: ghes: '*' --- -This guide will walk you through setting up, configuring and managing {% data variables.product.product_location %} as an enterprise administrator. +Este guia irá ajudar você a configurar e gerenciar {% data variables.product.product_location %} como administrador da empresa. -{% data variables.product.company_short %} provides two ways to deploy {% data variables.product.prodname_enterprise %}. +{% data variables.product.company_short %} oferece duas maneiras de implantar {% data variables.product.prodname_enterprise %}. - **{% data variables.product.prodname_ghe_cloud %}** - **{% data variables.product.prodname_ghe_server %}** -{% data variables.product.company_short %} hosts {% data variables.product.prodname_ghe_cloud %}. You can deploy and host {% data variables.product.prodname_ghe_server %} in your own datacenter or a supported cloud provider. +{% data variables.product.company_short %} hospeda {% data variables.product.prodname_ghe_cloud %}. Você pode implantar e hospedar {% data variables.product.prodname_ghe_server %} no seu próprio centro de dados ou em um provedor da nuvem compatível. -For an overview of how {% data variables.product.product_name %} works, see "[System overview](/admin/overview/system-overview)." +Para obter uma visão geral de como {% data variables.product.product_name %} funciona, consulte "[Visão geral do sistema](/admin/overview/system-overview)". ## Parte 1: Instalar {% data variables.product.product_name %} -To get started with {% data variables.product.product_name %}, you will need to create your enterprise account, install the instance, use the Management Console for initial setup, configure your instance, and manage billing. -### 1. Creating your enterprise account -Before you install {% data variables.product.product_name %}, you can create an enterprise account on {% data variables.product.prodname_dotcom_the_website %} by contacting [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact). An enterprise account on {% data variables.product.prodname_dotcom_the_website %} is useful for billing and for shared features with {% data variables.product.prodname_dotcom_the_website %} via {% data variables.product.prodname_github_connect %}. Para obter mais informações, consulte "[Sobre contas corporativas](/admin/overview/about-enterprise-accounts)". +Para começar com {% data variables.product.product_name %}, você deverá criar a conta corporativa, instalar a instância, usar o Console de Gerenciamento para configuração inicial, configurar a sua instância e gerenciar a cobrança. +### 1. Criando a sua conta corporativa +Antes de instalar {% data variables.product.product_name %}, você pode criar uma conta corporativa em {% data variables.product.prodname_dotcom_the_website %} entrando em contato com a [](https://enterprise.github.com/contact) equipe de vendas de {% data variables.product.prodname_dotcom %}. Uma conta corporativa em {% data variables.product.prodname_dotcom_the_website %} é útil para a cobrança e para recursos compartilhados com o {% data variables.product.prodname_dotcom_the_website %} via {% data variables.product.prodname_github_connect %}. Para obter mais informações, consulte "[Sobre contas corporativas](/admin/overview/about-enterprise-accounts)". ### 2. Instalar o {% data variables.product.product_name %} -To get started with {% data variables.product.product_name %}, you will need to install the appliance on a virtualization platform of your choice. Para obter mais informações, consulte "[Configurar instância do {% data variables.product.prodname_ghe_server %}](/admin/installation/setting-up-a-github-enterprise-server-instance)". +Para começar com {% data variables.product.product_name %}, você deverá instalar o dispositivo em uma plataforma de virtualização de sua escolha. Para obter mais informações, consulte "[Configurar instância do {% data variables.product.prodname_ghe_server %}](/admin/installation/setting-up-a-github-enterprise-server-instance)". -### 3. Using the Management Console -You will use the Management Console to walk through the initial setup process when first launching {% data variables.product.product_location %}. You can also use the Management Console to manage instance settings such as the license, domain, authentication, and TLS. For more information, see "[Accessing the management console](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)." +### 3. Usando o Console de Gerenciamento +Você usará o Console de Gerenciamento para apresentar o processo de configuração inicial ao iniciar {% data variables.product.product_location %}. Você também pode usar o Console de Gerenciamento para gerenciar configurações de instância, como licença, domínio, autenticação e TLS. Para obter mais informações, consulte "[Acessando o console de gerenciamento](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)". ### 4. Configurar o {% data variables.product.product_location %}; -In addition to the Management Console, you can use the site admin dashboard and the administrative shell (SSH) to manage {% data variables.product.product_location %}. For example, you can configure applications and rate limits, view reports, use command-line utilities. For more information, see "[Configuring your enterprise](/admin/configuration/configuring-your-enterprise)." +Além do console de gerenciamento, você pode usar o painel de administração do site e o shell administrativo (SSH) para gerenciar {% data variables.product.product_location %}. Por exemplo, você pode configurar aplicativos e limites de taxa, ver relatórios, usar utilitários de linha de comando. Para obter mais informações, consulte "[Configurando sua empresa](/admin/configuration/configuring-your-enterprise)". -You can use the default network settings used by {% data variables.product.product_name %} via the dynamic host configuration protocol (DHCP), or you can also configure the network settings using the virtual machine console. Você também pode configurar um servidor proxy ou regras de firewall. For more information, see "[Configuring network settings](/admin/configuration/configuring-network-settings)." +Você pode usar as configurações de rede padrão usadas por {% data variables.product.product_name %} por meio do protocolo de configuração do host dinâmico (DHCP) ou você também pode definir as configurações de rede usando o console de máquina virtual. Você também pode configurar um servidor proxy ou regras de firewall. Para obter mais informações, consulte "[Definindo as configurações de rede](/admin/configuration/configuring-network-settings)". ### 5. Configurar alta disponibilidade -You can configure {% data variables.product.product_location %} for high availability to minimize the impact of hardware failures and network outages. For more information, see "[Configuring high availability](/admin/enterprise-management/configuring-high-availability)." +Você pode configurar {% data variables.product.product_location %} para alta disponibilidade a fim de minimizar o impacto de falhas de hardware e falhas de rede. Para obter mais informações, consulte "[Configurando alta disponibilidade](/admin/enterprise-management/configuring-high-availability)". ### 6. Configurar uma instância de preparo -You can set up a staging instance to test modifications, plan for disaster recovery, and try out updates before applying them to {% data variables.product.product_location %}. Para obter mais informações, consulte "[Configurar instância de preparo](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)". +Você pode configurar uma instância de preparo para testar modificações, planejar a recuperação de desastres e testar atualizações antes de aplicá-las a {% data variables.product.product_location %}. Para obter mais informações, consulte "[Configurar instância de preparo](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)". -### 7. Designating backups and disaster recovery -To protect your production data, you can configure automated backups of {% data variables.product.product_location %} with {% data variables.product.prodname_enterprise_backup_utilities %}. Para obter mais informações, consulte "[Configurar backups no appliance](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)". +### 7. Designando backups e recuperação de desastres +Para proteger seus dados de produção, você pode configurar backups automatizados de {% data variables.product.product_location %} com {% data variables.product.prodname_enterprise_backup_utilities %}. Para obter mais informações, consulte "[Configurar backups no appliance](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)". ### 8. Gerenciar a cobrança para a sua empresa -Billing for all the organizations and {% data variables.product.product_name %} instances connected to your enterprise account is aggregated into a single bill charge for all of your paid {% data variables.product.prodname_dotcom %}.com services. Enterprise owners and billing managers can access and manage billing settings for enterprise accounts. For more information, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)." +A cobrança para todas as organizações e instâncias de {% data variables.product.product_name %} conectadas à sua conta corporativa é agregada em uma única taxa de cobrança para todos os seus serviços pagos de {% data variables.product.prodname_dotcom %}.com. Proprietários corporativos e gerentes de cobrança podem acessar e gerenciar as configurações de cobrança relativas a contas corporativas. Para obter mais informações, consulte "[Gerenciando a cobrança da sua empresa](/admin/overview/managing-billing-for-your-enterprise)". -## Part 2: Organizing and managing your team -As an enterprise owner or administrator, you can manage settings on user, repository, team and organization levels. You can manage members of your enterprise, create and manage organizations, set policies for repository management, and create and manage teams. +## Parte 2: Organização e gerenciamento da sua equipe +Como proprietário corporativo ou administrador, você pode gerenciar configurações em níveis de usuário, repositório, equipe e organização. É possível gerenciar os integrantes da sua empresa, criar e gerenciar organizações, definir políticas para a gestão do repositório e criar e gerenciar as equipes. -### 1. Managing members of {% data variables.product.product_location %} +### 1. Gerenciando integrantes de {% data variables.product.product_location %} {% data reusables.getting-started.managing-enterprise-members %} ### 2. Criar organizações {% data reusables.getting-started.creating-organizations %} -### 3. Adding members to organizations +### 3. Adicionando integrantes a organizações {% data reusables.getting-started.adding-members-to-organizations %} ### 4. Criar equipes {% data reusables.getting-started.creating-teams %} -### 5. Setting organization and repository permission levels +### 5. Definindo níveis de permissões para a organização e para o repositório {% data reusables.getting-started.setting-org-and-repo-permissions %} -### 6. Enforcing repository management policies +### 6. Aplicando políticas de gerenciamento do repositório {% data reusables.getting-started.enforcing-repo-management-policies %} -## Part 3: Building securely -To increase the security of {% data variables.product.product_location %}, you can configure authentication for enterprise members, use tools and audit logging to stay in compliance, configure security and analysis features for your organizations, and optionally enable {% data variables.product.prodname_GH_advanced_security %}. -### 1. Authenticating enterprise members -You can use {% data variables.product.product_name %}'s built-in authentication method, or you can choose between an established authentication provider, such as CAS, LDAP, or SAML, to integrate your existing accounts and centrally manage user access to {% data variables.product.product_location %}. For more information, see "[Authenticating users for {% data variables.product.product_location %}](/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance)." +## Parte 3: Criando com segurança +Para aumentar a segurança de {% data variables.product.product_location %}, você pode configurar a autenticação para integrantes da empresa, usar ferramentas e registro de auditoria para manter a conformidade, configurar recursos de segurança e análise para as suas organizações e, opcionalmente, habilitar {% data variables.product.prodname_GH_advanced_security %}. +### 1. Efetuando a autenticação dos integrantes da empresa +Você pode usar o método de autenticação interno do {% data variables.product.product_name %} ou você pode escolher entre um provedor de autenticação estabelecido como o CAS, LDAP, ou SAML, para integrar suas contas existentes e gerenciar centralmente o acesso do usuário a {% data variables.product.product_location %}. Para obter mais informações, consulte "[Autenticando usuários para {% data variables.product.product_location %}](/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance)". -You can also require two-factor authentication for each of your organizations. For more information, see "[Requiring two factor authentication for an organization](/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization)." +Você também pode exigir autenticação de dois fatores para cada uma de suas organizações. Para obter mais informações, consulte "[Exigindo a autenticação de dois fatores para uma organização](/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization)". -### 2. Staying in compliance -You can implement required status checks and commit verifications to enforce your organization's compliance standards and automate compliance workflows. You can also use the audit log for your organization to review actions performed by your team. For more information, see "[Enforcing policy with pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks)" and "[Audit logging](/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging)." +### 2. Manter a conformidade +Você pode implementar verificações de status necessárias e realizar verificações de commit para fazer cumprir os padrões de conformidade da sua organização e automatizar os fluxos de trabalho de conformidade. Você também pode usar o log de auditoria para sua organização revisar as ações executadas pela sua equipe. Para obter mais informações, consulte "[Aplicando a política com hooks pre-receive](/admin/policies/enforcing-policy-with-pre-receive-hooks)" e "[Log de auditoria](/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging)". {% ifversion ghes > 2.22 %} -### 3. Configuring security features for your organizations +### 3. Configurar as funcionalidades de segurança para as suas organizações {% data reusables.getting-started.configuring-security-features %} {% endif %} {% ifversion ghes %} -### {% ifversion ghes = 2.22 %}3.{% else %}4.{% endif %} Enabling {% data variables.product.prodname_GH_advanced_security %} features -You can upgrade your {% data variables.product.product_name %} license to include {% data variables.product.prodname_GH_advanced_security %}. This provides extra features that help users find and fix security problems in their code, such as code and secret scanning. For more information, see "[{% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)." +### {% ifversion ghes = 2.22 %}3.{% else %}4.{% endif %} Habilitar funcionalidades de {% data variables.product.prodname_GH_advanced_security %} +Você pode atualizar sua licença do {% data variables.product.product_name %} para incluir {% data variables.product.prodname_GH_advanced_security %}. Isso fornece funcionalidades extras que ajudam os usuários a encontrar e corrigir problemas de segurança no seu código como, por exemplo, digitalização de código e segredo. Para obter mais informações, consulte "[{% data variables.product.prodname_GH_advanced_security %} para a sua empresa "](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)". {% endif %} -## Part 4: Customizing and automating your enterprise's work on {% data variables.product.prodname_dotcom %} -You can customize and automate work in organizations in your enterprise with {% data variables.product.prodname_dotcom %} and {% data variables.product.prodname_oauth_apps %}, {% data variables.product.prodname_dotcom %} API, {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %} , and {% data variables.product.prodname_pages %}. +## Parte 4: Personalizando e automatizando o trabalho da sua empresa em {% data variables.product.prodname_dotcom %} +Você pode personalizar e automatizar o trabalho em organizações da sua empresa com {% data variables.product.prodname_dotcom %} e {% data variables.product.prodname_oauth_apps %}, {% data variables.product.prodname_dotcom %} API, {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %} e {% data variables.product.prodname_pages %}. -### 1. Building {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %} -You can build integrations with the {% data variables.product.prodname_dotcom %} API, such as {% data variables.product.prodname_github_apps %} or {% data variables.product.prodname_oauth_apps %}, for use in organizations in your enterprise to complement and extend your workflows. Para obter mais informações, consulte "[Sobre os aplicativos](/developers/apps/getting-started-with-apps/about-apps)". -### 2. Using the {% data variables.product.prodname_dotcom %} API +### 1. Criando {% data variables.product.prodname_github_apps %} e {% data variables.product.prodname_oauth_apps %} +Você pode criar integrações com a API do {% data variables.product.prodname_dotcom %}, como, por exemplo, {% data variables.product.prodname_github_apps %} ou {% data variables.product.prodname_oauth_apps %}, para usar em organizações da sua empresa para complementar e ampliar seus fluxos de trabalho. Para obter mais informações, consulte "[Sobre os aplicativos](/developers/apps/getting-started-with-apps/about-apps)". +### 2. Usando a API de {% data variables.product.prodname_dotcom %} {% data reusables.getting-started.api %} {% ifversion ghes %} -### 3. Building {% data variables.product.prodname_actions %} +### 3. Criando {% data variables.product.prodname_actions %} {% data reusables.getting-started.actions %} -For more information on enabling and configuring {% data variables.product.prodname_actions %} on {% data variables.product.product_name %}, 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)." +Para obter mais informações sobre como ativar e configurar {% data variables.product.prodname_actions %} em {% data variables.product.product_name %}, consulte "[Primeiros passos com {% data variables.product.prodname_actions %} para {% 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)". -### 4. Publishing and managing {% data variables.product.prodname_registry %} +### 4. Publicando e gerenciando {% data variables.product.prodname_registry %} {% data reusables.getting-started.packages %} -For more information on enabling and configuring {% data variables.product.prodname_registry %} for {% data variables.product.product_location %}, see "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)." +Para obter mais informações sobre como habilitar e configurar {% data variables.product.prodname_registry %} para {% data variables.product.product_location %}, consulte "[Primeiros passos com {% data variables.product.prodname_registry %} para a sua empresa](/admin/packages/getting-started-with-github-packages-for-your-enterprise)". {% endif %} ### 5. Usar {% data variables.product.prodname_pages %} {% data reusables.getting-started.github-pages-enterprise %} -## Part 5: Connecting with other {% data variables.product.prodname_dotcom %} resources -You can use {% data variables.product.prodname_github_connect %} to share resources. +## Parte 5: Conectando com outros recursos de {% data variables.product.prodname_dotcom %} +Você pode usar {% data variables.product.prodname_github_connect %} para compartilhar recursos. -If you are the owner of both a {% data variables.product.product_name %} instance and a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account, you can enable {% data variables.product.prodname_github_connect %}. {% data variables.product.prodname_github_connect %} allows you to share specific workflows and features between {% data variables.product.product_location %} and {% data variables.product.prodname_ghe_cloud %}, such as unified search and contributions. Para obter mais informações, consulte "[Conectar o {% data variables.product.prodname_ghe_server %} ao {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)". +Se você for o proprietário de uma instância de {% data variables.product.product_name %} e uma organização ou conta corporativa de {% data variables.product.prodname_ghe_cloud %}, você poderá habilitar {% data variables.product.prodname_github_connect %}. {% data variables.product.prodname_github_connect %} permite que você compartilhe fluxos de trabalho específicos e recursos entre {% data variables.product.product_location %} e {% data variables.product.prodname_ghe_cloud %}, como pesquisa unificada e contribuições. Para obter mais informações, consulte "[Conectar o {% data variables.product.prodname_ghe_server %} ao {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)". -## Part 6: Using {% data variables.product.prodname_dotcom %}'s learning and support resources -Your enterprise members can learn more about Git and {% data variables.product.prodname_dotcom %} with our learning resources, and you can get the support you need when setting up and managing {% data variables.product.product_location %} with {% data variables.product.prodname_dotcom %} Enterprise Support. -### 1. Learning with {% data variables.product.prodname_learning %} +## Parte 6: Usando o aprendizado de {% data variables.product.prodname_dotcom %} e o suporte recursos +Os membros da sua empresa podem aprender mais sobre o Git e {% data variables.product.prodname_dotcom %} com os nossos recursos de aprendizagem. e você pode obter o suporte de que precisa ao configurar e gerenciar {% data variables.product.product_location %} com o suporte do enterprise de {% data variables.product.prodname_dotcom %}. +### 1. Aprendendo com {% data variables.product.prodname_learning %} {% data reusables.getting-started.learning-lab-enterprise %} -### 2. Working with {% data variables.product.prodname_dotcom %} Enterprise Support +### 2. Trabalhando com o Suporte do Enterprise de {% data variables.product.prodname_dotcom %} {% data reusables.getting-started.contact-support-enterprise %} diff --git a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-team.md b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-team.md index 1a1860b6b1..8139df6572 100644 --- a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-team.md +++ b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-team.md @@ -1,96 +1,96 @@ --- -title: Getting started with GitHub Team -intro: 'With {% data variables.product.prodname_team %} groups of people can collaborate across many projects at the same time in an organization account.' +title: Introdução ao GitHub Team +intro: 'Com grupos de {% data variables.product.prodname_team %}, as pessoas podem colaborar em vários projetos ao mesmo tempo na conta de uma organização.' versions: fpt: '*' --- -This guide will walk you through setting up, configuring and managing your {% data variables.product.prodname_team %} account as an organization owner. +Este guia irá ajudar você a configurar e gerenciar sua conta {% data variables.product.prodname_team %} como proprietário da organização. -## Part 1: Configuring your {% data variables.product.product_name %} account -As the first steps in starting with {% data variables.product.prodname_team %}, you will need to create a user account or log into your existing account on {% data variables.product.prodname_dotcom %}, create an organization, and set up billing. +## Parte 1: Configurando sua conta de {% data variables.product.product_name %} +Como os primeiros passos para começar com {% data variables.product.prodname_team %}, você deverá criar uma conta de usuário ou entrar na sua conta existente em {% data variables.product.prodname_dotcom %}, criar uma organização e configurar a cobrança. ### 1. Sobre organizações -As organizações são contas compartilhadas onde empresas e projetos de código aberto podem colaborar em muitos projetos de uma vez. Os proprietários e administradores podem gerenciar o acesso de integrantes aos dados e projetos da organização com recursos avançados administrativos e de segurança. For more information on the features of organizations, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations#terms-of-service-and-data-protection-for-organizations)." +As organizações são contas compartilhadas onde empresas e projetos de código aberto podem colaborar em muitos projetos de uma vez. Os proprietários e administradores podem gerenciar o acesso de integrantes aos dados e projetos da organização com recursos avançados administrativos e de segurança. Para obter mais informações sobre os recursos das organizações, consulte "[Sobre as organizações](/organizations/collaborating-with-groups-in-organizations/about-organizations#terms-of-service-and-data-protection-for-organizations)". -### 2. Creating an organization and signing up for {% data variables.product.prodname_team %} -Before creating an organization, you will need to create a user account or log in to your existing {% data variables.product.prodname_dotcom %} account. Para obter mais informações, consulte "[Inscrever-se em uma nova conta do {% data variables.product.prodname_dotcom %}](/get-started/signing-up-for-github/signing-up-for-a-new-github-account)". +### 2. Criando uma organização e inscrevendo-se em {% data variables.product.prodname_team %} +Antes de criar uma organização, você deverá criar a conta de um usuário ou entrar na sua conta de {% data variables.product.prodname_dotcom %} existente. Para obter mais informações, consulte "[Inscrever-se em uma nova conta do {% data variables.product.prodname_dotcom %}](/get-started/signing-up-for-github/signing-up-for-a-new-github-account)". -Once your user account is set up, you can create an organization and pick a plan. This is where you can choose a {% data variables.product.prodname_team %} subscription for your organization. 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)". +Uma vez que a sua conta de usuário está configurada, você derá criar uma organização e escolher um plano. Aqui é onde você pode escolher uma assinatura de {% data variables.product.prodname_team %} para a sua 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)". -### 3. Managing billing for an organization -You must manage billing settings, payment method, and paid features and products for each of your personal accounts and organizations separately. You can switch between settings for your different accounts using the context switcher in your settings. For more information, see "[Switching between settings for your different accounts](/billing/managing-your-github-billing-settings/about-billing-on-github#switching-between-settings-for-your-different-accounts)." +### 3. Gerenciando a cobrança para uma organização +Você deve gerenciar as configurações de cobrança, método de pagamento e produtos pagos para cada uma das suas contas pessoais e organizações separadamente. Você pode alternar entre as configurações para a suas diferentes contas usando o alternador de contexto nas suas configurações. For more information, see "[Switching between settings for your different accounts](/billing/managing-your-github-billing-settings/about-billing-on-github#switching-between-settings-for-your-different-accounts)." -Your organization's billing settings page allows you to manage settings like your payment method, billing cycle and billing email, or view information such as your subscription, billing date and payment history. You can also view and upgrade your storage and GitHub Actions minutes. For more information on managing your billing settings, see "[Managing your {% data variables.product.prodname_dotcom %} billing settings](/billing/managing-your-github-billing-settings)." +A página de configurações de cobrança da sua organização permite que você gerencie configurações como seu método de pagamento, ciclo de cobrança e e-mail de cobrança, ou visualize informações como a sua assinatura, data de faturamento e histórico de pagamento. Você também pode ver e fazer a atualização do seu armazenamento e dos minutos do GitHub Action. Para obter mais informações sobre como gerenciar suas configurações de cobrança, consulte "[Gerenciando suas configurações de cobrança de {% data variables.product.prodname_dotcom %}](/billing/managing-your-github-billing-settings)". -Only organization members with the *owner* or *billing manager* role can access or change billing settings for your organization. A billing manager is someone who manages the billing settings for your organization and does not use a paid license in your organization's subscription. For more information on adding a billing manager to your organization, see "[Adding a billing manager to your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)." +Apenas os integrantes da organização com a função de *proprietário* ou *gerente de cobrança* podem acessar ou alterar as configurações de cobrança da sua organização. Um gerente de cobrança é um usuário que gerencia as configurações de cobrança para sua organização e não usa uma licença paga na assinatura da sua organização. Para obter mais informações sobre como adicionar um gerente de cobrança à sua organização, consulte "[Adicionando um gerente de cobrança à sua organização](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)". -## Part 2: Adding members and setting up teams -After creating your organization, you can invite members and set permissions and roles. You can also create different levels of teams and set customized levels of permissions for your organization's repositories, project boards, and apps. +## Parte 2: Adicionar integrantes e criar equipes +Depois de criar a sua organização, você poderá convidar integrantes e definir permissões e funções. Você também pode criar diferentes níveis de equipes e definir níveis personalizados de permissões para repositórios da sua organização, quadros de projetos e aplicativos. -### 1. Managing members of your organization +### 1. Gerenciando integrantes da sua organização {% data reusables.getting-started.managing-org-members %} -### 2. Organization permissions and roles +### 2. Permissões e funções da organização {% data reusables.getting-started.org-permissions-and-roles %} -### 3. About and creating teams +### 3. Sobre e criar equipes {% data reusables.getting-started.about-and-creating-teams %} -### 4. Managing team settings +### 4. Gerenciando as configurações de equipe {% data reusables.getting-started.managing-team-settings %} -### 5. Giving people and teams access to repositories, project boards and apps +### 5. Dar às pessoas e equipes acesso a repositórios, seções de projetos e aplicativos {% data reusables.getting-started.giving-access-to-repositories-projects-apps %} -## Part 3: Managing security for your organization -You can help to make your organization more secure by recommending or requiring two-factor authentication for your organization members, configuring security features, and reviewing your organization's audit log and integrations. +## Parte 3: Gerenciando a segurança da sua organização +Você pode ajudar a tornar sua organização mais segura ao recomendar ou exigir a autenticação de dois fatores para os integrantes da sua organização, configurando as funcionalidades de segurança e revisando o log de auditoria e integrações da sua organização. -### 1. Requiring two-factor authentication +### 1. Exigindo a autenticação de dois fatores {% data reusables.getting-started.requiring-2fa %} -### 2. Configuring security features for your organization +### 2. Configurando recursos de segurança para a sua organização {% data reusables.getting-started.configuring-security-features %} -### 3. Reviewing your organization's audit log and integrations +### 3. Revisando o log de auditoria e as integrações da sua organização {% data reusables.getting-started.reviewing-org-audit-log-and-integrations %} -## Part 4: Setting organization level policies -### 1. Managing organization policies +## Parte 4: Definindo as políticas no nível da organização +### 1. Gerenciando as políticas da organização {% data reusables.getting-started.managing-org-policies %} -### 2. Managing repository changes +### 2. Gerenciando alterações de repositório {% data reusables.getting-started.managing-repo-changes %} -### 3. Using organization-level community health files and moderation tools +### 3. Usando arquivos de saúde da comunidade no nível da organização e as ferramentas de moderação {% data reusables.getting-started.using-org-community-files-and-moderation-tools %} -## Part 5: Customizing and automating your work on {% data variables.product.product_name %} +## Parte 5: Personalizando e automatizando seu trabalho em {% data variables.product.product_name %} {% data reusables.getting-started.customizing-and-automating %} ### 1. Usar {% data variables.product.prodname_marketplace %} {% data reusables.getting-started.marketplace %} -### 2. Using the {% data variables.product.prodname_dotcom %} API +### 2. Usando a API de {% data variables.product.prodname_dotcom %} {% data reusables.getting-started.api %} -### 3. Building {% data variables.product.prodname_actions %} +### 3. Criando {% data variables.product.prodname_actions %} {% data reusables.getting-started.actions %} -### 4. Publishing and managing {% data variables.product.prodname_registry %} +### 4. Publicando e gerenciando {% data variables.product.prodname_registry %} {% data reusables.getting-started.packages %} -## Part 6: Participating in {% data variables.product.prodname_dotcom %}'s community +## Parte 6: Participando da comunidade de {% data variables.product.prodname_dotcom %} {% data reusables.getting-started.participating-in-community %} -### 1. Contributing to open source projects +### 1. Contribuindo para projetos de código aberto {% data reusables.getting-started.open-source-projects %} -### 2. Interacting with the {% data variables.product.prodname_gcf %} +### 2. Interagindo com o {% data variables.product.prodname_gcf %} {% data reusables.support.ask-and-answer-forum %} -### 3. Learning with {% data variables.product.prodname_learning %} +### 3. Aprendendo com {% data variables.product.prodname_learning %} {% data reusables.getting-started.learning-lab %} -### 4. Supporting the open source community +### 4. Apoiar a comunidade de código aberto {% data reusables.getting-started.sponsors %} ### 5. Entrar em contato com o {% data variables.contact.github_support %} {% data reusables.getting-started.contact-support %} ## Leia mais -- "[Getting started with your GitHub account](/get-started/onboarding/getting-started-with-your-github-account)" +- "[Introdução à sua conta do GitHub](/get-started/onboarding/getting-started-with-your-github-account)" 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 4ec2a10f4a..ae1c956c71 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 @@ -1,145 +1,145 @@ --- -title: Getting started with your GitHub account -intro: 'With a user account on {% data variables.product.prodname_dotcom %}, you can import or create repositories, collaborate with others, and connect with the {% data variables.product.prodname_dotcom %} community.' +title: Introdução à sua conta do GitHub +intro: 'Com uma conta de usuário no {% data variables.product.prodname_dotcom %}, você pode importar ou criar repositórios, colaborar com outros e conectar-se com a comunidade de {% data variables.product.prodname_dotcom %}.' versions: fpt: '*' ghes: '*' ghae: '*' --- -This guide will walk you through setting up your {% data variables.product.prodname_dotcom %} account and getting started with {% data variables.product.prodname_dotcom %}'s features for collaboration and community. +Este guia irá ajudar você a configurar sua conta de {% data variables.product.prodname_dotcom %} e dar os primeiros passos com as funcionalidades de {% data variables.product.prodname_dotcom %} para colaboração e comunidade. -## Part 1: Configuring your {% data variables.product.prodname_dotcom %} account +## Parte 1: Configurando sua conta de {% data variables.product.prodname_dotcom %} {% ifversion fpt %} -The first steps in starting with {% data variables.product.product_name %} are to create an account, choose a product that fits your needs best, verify your email, set up two-factor authentication, and view your profile. +Os primeiros passos para começar com {% data variables.product.product_name %} são criar uma conta, escolher um produto que se adeque melhor às suas necessidades, verificar o seu e-mail, configurar a autenticação de dois fatores e verificar o seu perfil. {% elsif ghes %} -The first steps in starting with {% data variables.product.product_name %} are to access your account, set up two-factor authentication, and view your profile. +Os primeiros passos para começar com {% data variables.product.product_name %} são acessar sua conta, configurar a autenticação de dois fatores e ver seu perfil. {% elsif ghae %} -The first steps in starting with {% data variables.product.product_name %} are to access your account and view your profile. +Os primeiros passos para começar com {% data variables.product.product_name %} são acessar a sua conta e ver o seu perfil. {% endif %} -{% ifversion fpt %}There are several types of accounts on {% data variables.product.prodname_dotcom %}. {% endif %} Every person who uses {% data variables.product.product_name %} has their own user account, which can be part of multiple organizations and teams. Your user account is your identity on {% data variables.product.product_location %} and represents you as an individual. +{% ifversion fpt %}Existem vários tipos de contas em {% data variables.product.prodname_dotcom %}. {% endif %} Toda pessoa que usar {% data variables.product.product_name %} terá sua própria conta de usuário e poderá fazer parte de várias organizações e equipes. A sua conta de usuário é sua identidade em {% data variables.product.product_location %} e representa você como indivíduo. {% ifversion fpt %} ### 1. Criar uma conta -To sign up for a {% data variables.product.prodname_dotcom %} account, navigate to https://github.com/ and follow the prompts. +Para inscrever-se em uma conta de {% data variables.product.prodname_dotcom %}, acesse https://github.com/ e siga as instruções. -To keep your {% data variables.product.prodname_dotcom %} account secure you should use a strong and unique password. Para obter mais informações, consulte "[Criar uma senha forte](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-strong-password)". +Para manter a sua conta de {% data variables.product.prodname_dotcom %} segura, você deverá usar uma senha forte e exclusiva. Para obter mais informações, consulte "[Criar uma senha forte](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-strong-password)". -### 2. Choosing your {% data variables.product.prodname_dotcom %} product -You can choose {% data variables.product.prodname_free_user %} or {% data variables.product.prodname_pro %} to get access to different features for your personal account. You can upgrade at any time if you are unsure at first which product you want. +### 2. Escolhendo seu produto de {% data variables.product.prodname_dotcom %} +Você pode escolher {% data variables.product.prodname_free_user %} ou {% data variables.product.prodname_pro %} para obter acesso a diferentes recursos da sua conta pessoal. Você pode fazer a atualização a qualquer momento se não tiver certeza qual o produto você deseja. -For more information on all of {% data variables.product.prodname_dotcom %}'s plans, see "[{% data variables.product.prodname_dotcom %}'s products](/get-started/learning-about-github/githubs-products)." +Para obter mais informações sobre todos os planos de {% data variables.product.prodname_dotcom %}, consulte "[Produtos de {% data variables.product.prodname_dotcom %}de](/get-started/learning-about-github/githubs-products)". ### 3. Verificar endereço de e-mail -To ensure you can use all the features in your {% data variables.product.product_name %} plan, verify your email address after signing up for a new account. Para obter mais informações, consulte "[Verificar o endereço de e-mail](/github/getting-started-with-github/signing-up-for-github/verifying-your-email-address)". +Para garantir que você possa utilizar todos os recursos do seu plano de {% data variables.product.product_name %}, verifique o seu endereço de e-mail após inscrever-se em uma nova conta. Para obter mais informações, consulte "[Verificar o endereço de e-mail](/github/getting-started-with-github/signing-up-for-github/verifying-your-email-address)". {% endif %} {% ifversion ghes %} -### 1. Accessing your account -The administrator of your {% data variables.product.product_name %} instance will notify you about how to authenticate and access your account. The process varies depending on the authentication mode they have configured for the instance. +### 1. Acessando a sua conta +O administrador da sua instância de {% data variables.product.product_name %} irá notificar você sobre como efetuar a autenticação e acessar a sua conta. O processo varia dependendo do modo de autenticação que eles configuraram para a instância. {% endif %} {% ifversion ghae %} -### 1. Accessing your account -You will receive an email notification once your enterprise owner for {% data variables.product.product_name %} has set up your account, allowing you to authenticate with SAML single sign-on (SSO) and access your account. +### 1. Acessando a sua conta +Você receberá uma notificação por e-mail assim que o proprietário corporativo de {% data variables.product.product_name %} tiver configurado a sua conta permitindo que você efetue a autenticação com o logon único SAML (SSO) e acesse sua conta. {% endif %} {% ifversion fpt or ghes %} -### {% ifversion fpt %}4.{% else %}2.{% endif %} Configuring two-factor authentication -A autenticação de dois fatores, ou 2FA, é uma camada extra de segurança usada no logon em sites ou apps. We strongly urge you to configure 2FA for the safety of your account. Para obter mais informações, consulte "[Sobre a autenticação de dois fatores](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication)". +### {% ifversion fpt %}4.{% else %}2.{% endif %} Configurando a autenticação de dois fatores +A autenticação de dois fatores, ou 2FA, é uma camada extra de segurança usada no logon em sites ou apps. É altamente recomendável que você configure a 2FA para a segurança da sua conta. Para obter mais informações, consulte "[Sobre a autenticação de dois fatores](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication)". {% endif %} -### {% ifversion fpt %}5.{% elsif ghes %}3.{% else %}2.{% endif %} Viewing your {% data variables.product.product_name %} profile and contribution graph -Your {% data variables.product.product_name %} profile tells people the story of your work through the repositories and gists you've pinned, the organization memberships you've chosen to publicize, the contributions you've made, and the projects you've created. For more information, see "[About your profile](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile)" and "[Viewing contributions on your profile](/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile)." +### {% ifversion fpt %}5.{% elsif ghes %}3.{% else %}2.{% endif %} Visualizando seu {% data variables.product.product_name %} perfil e gráfico de contribuição +Seu perfil de {% data variables.product.product_name %} conta a história do seu trabalho por meio dos repositórios e dos gists que você fixou, as associações da organização que você escolheu divulgar, as contribuições que você fez e os projetos que você criou. Para obter mais informações, consulte "[Sobre o seu perfil](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile)" e "[Visualizando as contribuições no seu perfil](/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile)". -## Part 2: Using {% data variables.product.product_name %}'s tools and processes -To best use {% data variables.product.product_name %}, you'll need to set up Git. O Git é responsável por tudo relacionado ao {% data variables.product.prodname_dotcom %} que acontece localmente no computador. To effectively collaborate on {% data variables.product.product_name %}, you'll write in issues and pull requests using {% data variables.product.prodname_dotcom %} Flavored Markdown. +## Parte 2: Usando ferramentas e processos de {% data variables.product.product_name %} +Para usar {% data variables.product.product_name %} da melhor forma, você deverá configurar o Git. O Git é responsável por tudo relacionado ao {% data variables.product.prodname_dotcom %} que acontece localmente no computador. Para colaborar de forma efetiva em {% data variables.product.product_name %}, você escreverá em problemas e pull requests usando o Markdown enriquecido de {% data variables.product.prodname_dotcom %}. -### 1. Learning Git -{% data variables.product.prodname_dotcom %}'s collaborative approach to development depends on publishing commits from your local repository to {% data variables.product.product_name %} for other people to view, fetch, and update using Git. For more information about Git, see the "[Git Handbook](https://guides.github.com/introduction/git-handbook/)" guide. For more information about how Git is used on {% data variables.product.product_name %}, see "[{% data variables.product.prodname_dotcom %} flow](/get-started/quickstart/github-flow)." +### 1. Aprendendo a usar o Git +A abordagem colaborativa do {% data variables.product.prodname_dotcom %} para o desenvolvimento depende da publicação dos commits do repositório local para {% data variables.product.product_name %} para que outras pessoas vejam, busquem e atualizem outras pessoas que usam o Git. Para obter mais informações sobre o Git, consulte o guia "[Manual do Git](https://guides.github.com/introduction/git-handbook/)". Para obter mais informações sobre como Git é usado em {% data variables.product.product_name %}, consulte "[Fuxo de {% data variables.product.prodname_dotcom %}](/get-started/quickstart/github-flow)". ### 2. Configurar o Git -If you plan to use Git locally on your computer, whether through the command line, an IDE or text editor, you will need to install and set up Git. Para obter mais informações, consulte "[Configurar o Git](/get-started/quickstart/set-up-git)". +Se você planeja usar o Git localmente no seu computador, por meio da linha de comando, editor de IDE ou texto, você deverá instalar e configurar o Git. Para obter mais informações, consulte "[Configurar o Git](/get-started/quickstart/set-up-git)". -If you prefer to use a visual interface, you can download and use {% data variables.product.prodname_desktop %}. {% data variables.product.prodname_desktop %} comes packaged with Git, so there is no need to install Git separately. Para obter mais informações, consulte "[Introdução ao {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)". +Se você preferir usar uma interface visual, você poderá fazer o download e usar {% data variables.product.prodname_desktop %}. {% data variables.product.prodname_desktop %} vem empacotado com o Git. Portanto não há a necessidade de instalar o Git separadamente. Para obter mais informações, consulte "[Introdução ao {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)". -Once you install Git, you can connect to {% data variables.product.product_name %} repositories from your local computer, whether your own repository or another user's fork. Quando você se conecta a um repositório do {% data variables.product.product_name %} a partir do Git, precisa fazer a autenticação no {% data variables.product.product_name %} usando HTTPS ou SSH. Para obter mais informações, consulte "[Sobre repositórios remotos](/get-started/getting-started-with-git/about-remote-repositories)." +Depois de instalar o Git, você poderá conectar-se aos repositórios de {% data variables.product.product_name %} a partir do seu computador local, independentemente de ser o seu próprio repositório ou a bifurcação de outro usuário. Quando você se conecta a um repositório do {% data variables.product.product_name %} a partir do Git, precisa fazer a autenticação no {% data variables.product.product_name %} usando HTTPS ou SSH. Para obter mais informações, consulte "[Sobre repositórios remotos](/get-started/getting-started-with-git/about-remote-repositories)." -### 3. Choosing how to interact with {% data variables.product.product_name %} -Everyone has their own unique workflow for interacting with {% data variables.product.prodname_dotcom %}; the interfaces and methods you use depend on your preference and what works best for your needs. +### 3. Escolhendo como interagir com {% data variables.product.product_name %} +Todos têm seu próprio fluxo de trabalho único para interagir com {% data variables.product.prodname_dotcom %}; as interfaces e métodos que você usa dependem da sua preferência e do que funciona melhor para as suas necessidades. -For more information about how to authenticate to {% data variables.product.product_name %} with each of these methods, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github)." +Para obter mais informações sobre como efetuar a autenticação em {% data variables.product.product_name %} com cada um desses métodos, consulte "[Sobre autenticação em {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github)". -| **Método** | **Descrição** | **Use cases** | -| ----------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| 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 %} | 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. 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. | -| 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. | -| {% data variables.product.prodname_dotcom %} 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 {% data variables.product.prodname_dotcom %} 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 %} -To make your communication clear and organized in issues and pull requests, you can use {% data variables.product.prodname_dotcom %} Flavored Markdown for formatting, which combines an easy-to-read, easy-to-write syntax with some custom functionality. Para obter mais informações, consulte "[Sobre gravação e formatação no {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)". +| **Método** | **Descrição** | **Casos de uso** | +| ---------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| 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. | +| 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. | +| API de {% data variables.product.prodname_dotcom %} | {% 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 do {% data variables.product.prodname_dotcom %} 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 %} +Para deixar sua comunicação clara e organizada nos problemas e pull requests, você pode usar o Markdown enriquecido {% data variables.product.prodname_dotcom %} para formatação, que combina uma sintaxe fácil de ler e fácil de escrever com algumas funcionalidades personalizadas. Para obter mais informações, consulte "[Sobre gravação e formatação no {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)". -You can learn {% data variables.product.prodname_dotcom %} Flavored Markdown with the "[Communicating using Markdown](https://lab.github.com/githubtraining/communicating-using-markdown)" course on {% data variables.product.prodname_learning %}. +Você pode aprender o Markdown enriquecido de {% data variables.product.prodname_dotcom %} com o curso "[Comunicando-se usando o Markdown](https://lab.github.com/githubtraining/communicating-using-markdown)" em {% data variables.product.prodname_learning %}. -### 5. Searching on {% data variables.product.product_name %} -Our integrated search allows you to find what you are looking for among the many repositories, users and lines of code on {% data variables.product.product_name %}. You can search globally across all of {% data variables.product.product_name %} or limit your search to a particular repository or organization. For more information about the types of searches you can do on {% data variables.product.product_name %}, see "[About searching on {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github)." +### 5. Pesquisando em {% data variables.product.product_name %} +Nossa pesquisa integrada permite que você encontre o que você está procurando entre os muitos repositórios, usuários e linhas de código em {% data variables.product.product_name %}. Você pode pesquisar globalmente em todos os {% data variables.product.product_name %} ou limitar sua pesquisa a um repositório ou organização em particular. Para obter mais informações sobre os tipos de pesquisas que você pode fazer em {% data variables.product.product_name %}, consulte "[Sobre pesquisar no {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github)". -Our search syntax allows you to construct queries using qualifiers to specify what you want to search for. For more information on the search syntax to use in search, see "[Searching on {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/searching-on-github)." +Nossa sintaxe de pesquisa permite que você construa consultas usando qualificadores para especificar o que você deseja pesquisar. Para obter mais informações sobre a sintaxe de pesquisa para usar na pesquisa, consulte "[Pesquisando em {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/searching-on-github)". -### 6. Managing files on {% data variables.product.product_name %} -With {% data variables.product.product_name %}, you can create, edit, move and delete files in your repository or any repository you have write access to. You can also track the history of changes in a file line by line. For more information, see "[Managing files on {% data variables.product.prodname_dotcom %}](/github/managing-files-in-a-repository/managing-files-on-github)." +### 6. Gerenciando arquivos em {% data variables.product.product_name %} +Com {% data variables.product.product_name %}, você pode criar, editar, mover e excluir arquivos no seu repositório ou em qualquer repositório ao qual você tenha acesso de gravação. Você também pode acompanhar o histórico de alterações de um arquvo linha por linha. Para obter mais informações, consulte "[Gerenciar arquivos em {% data variables.product.prodname_dotcom %}](/github/managing-files-in-a-repository/managing-files-on-github)". -## Part 3: Collaborating on {% data variables.product.product_name %} -Any number of people can work together in repositories across {% data variables.product.product_name %}. You can configure settings, create project boards, and manage your notifications to encourage effective collaboration. +## Parte 3: Colaborando em {% data variables.product.product_name %} +Qualquer quantidade de pessoas pode trabalhar juntas nos repositórios de {% data variables.product.product_name %}. É possível configurar configurações, criar quadros de projetos e gerenciar suas notificações para incentivar uma colaboração eficaz. -### 1. Working with repositories +### 1. Trabalhando com repositórios #### Criar um repositório -Um repositório é como uma pasta para seu projeto. You can have any number of public and private repositories in your user account. Repositories can contain folders and files, images, videos, spreadsheets, and data sets, as well as the revision history for all files in the repository. Para obter mais informações, consulte "[Sobre repositórios](/github/creating-cloning-and-archiving-repositories/about-repositories)". +Um repositório é como uma pasta para seu projeto. Você pode ter qualquer número de repositórios públicos e privados na sua conta de usuário. Os repositórios podem conter pastas e arquivos, imagens, vídeos, planilhas e conjuntos de dados, bem como o histórico de revisão para todos os arquivos no repositório. Para obter mais informações, consulte "[Sobre repositórios](/github/creating-cloning-and-archiving-repositories/about-repositories)". -When you create a new repository, you should initialize the repository with a README file to let people know about your project. Para obter mais informações, consulte "[Criar um novo repositório](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-new-repository)." +Ao criar um novo repositório, você deverá inicializar o repositório com um arquivo README para que as pessoas conheçam o seu projeto. Para obter mais informações, consulte "[Criar um novo repositório](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-new-repository)." #### Clonar um repositório -You can clone an existing repository from {% data variables.product.product_name %} to your local computer, making it easier to add or remove files, fix merge conflicts, or make complex commits. Clonar um repositório extrai uma cópia completa de todos os dados do repositório que o {% data variables.product.prodname_dotcom %} tem nesse momento, incluindo todas as versões de cada arquivo e pasta do projeto. Para obter mais informações, consulte "[Clonar um repositório](/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository)". +Você pode clonar um repositório existente a partir de {% data variables.product.product_name %} para o seu computador local, facilitando a adição ou remoção dos arquivos, correção de conflitos de merge ou realização de commits complexos. Clonar um repositório extrai uma cópia completa de todos os dados do repositório que o {% data variables.product.prodname_dotcom %} tem nesse momento, incluindo todas as versões de cada arquivo e pasta do projeto. Para obter mais informações, consulte "[Clonar um repositório](/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository)". #### Bifurcar um repositório -A fork is a copy of a repository that you manage, where any changes you make will not affect the original repository unless you submit a pull request to the project owner. O uso mais comum das bifurcações são propostas de mudanças no projeto de alguma outra pessoa ou o uso do projeto de outra pessoa como ponto de partida para sua própria ideia. Para obter mais informações, consulte "[Trabalhando com as bifurcações](/github/collaborating-with-pull-requests/working-with-forks)". +Uma bifurcação é uma cópia de um repositório que você gerencia, em que todas as alterações que você fizer não afetarão o repositório original a menos que você envie um pull request para o proprietário do projeto. O uso mais comum das bifurcações são propostas de mudanças no projeto de alguma outra pessoa ou o uso do projeto de outra pessoa como ponto de partida para sua própria ideia. Para obter mais informações, consulte "[Trabalhando com as bifurcações](/github/collaborating-with-pull-requests/working-with-forks)". ### 2. Importar seus projetos -If you have existing projects you'd like to move over to {% data variables.product.product_name %} you can import projects using the {% data variables.product.prodname_dotcom %} Importer, the command line, or external migration tools. For more information, see "[Importing source code to {% data variables.product.prodname_dotcom %}](/github/importing-your-projects-to-github/importing-source-code-to-github)." +Se você tiver projetos existentes que deseja mover para {% data variables.product.product_name %}, você poderá importar projetos usando o Importador de {% data variables.product.prodname_dotcom %}, a linha de comando ou as ferramentas externas de migração. Para obter mais informações, consulte "[Importando código-fonte para {% data variables.product.prodname_dotcom %}](/github/importing-your-projects-to-github/importing-source-code-to-github)". -### 3. Managing collaborators and permissions -Você pode colaborar em seu projeto com outras pessoas usando os problemas, as pull requests e os quadros de projeto do repositório. You can invite other people to your repository as collaborators from the **Collaborators** tab in the repository settings. Para obter mais informações, consulte "[Convidar colaboradores para um repositório pessoal](/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository)". +### 3. Gerenciando colaboradores e permissões +Você pode colaborar em seu projeto com outras pessoas usando os problemas, as pull requests e os quadros de projeto do repositório. Você pode convidar outras pessoas para o seu repositório como colaboradores na aba **Colaboradores** nas configurações do repositório. Para obter mais informações, consulte "[Convidar colaboradores para um repositório pessoal](/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository)". -You are the owner of any repository you create in your user account and have full control of the repository. Collaborators have write access to your repository, limiting what they have permission to do. Para obter mais informações, consulte "[Níveis de permissão para um repositório de conta de usuário](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository)". +Você é o proprietário de qualquer repositório que você cria na sua conta de usuário e você tem controle total sobre repositório. Os colaboradores têm acesso de gravação ao seu repositório, limitando o que eles têm permissão para fazer. Para obter mais informações, consulte "[Níveis de permissão para um repositório de conta de usuário](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository)". ### 4. Gerenciar configurações do repositório -As the owner of a repository you can configure several settings, including the repository's visibility, topics, and social media preview. Para obter mais informações, consulte "[Gerenciar configurações do repositório](/github/administering-a-repository/managing-repository-settings)". +Como proprietário de um repositório, você pode configurar diversas configurações, incluindo a visibilidade do repositório, tópicos e a pré-visualização das mídias sociais. Para obter mais informações, consulte "[Gerenciar configurações do repositório](/github/administering-a-repository/managing-repository-settings)". ### 5. Configurar projeto para contribuições úteis {% ifversion fpt %} -To encourage collaborators in your repository, you need a community that encourages people to use, contribute to, and evangelize your project. For more information, see "[Building Welcoming Communities](https://opensource.guide/building-community/)" in the Open Source Guides. +Para incentivar os colaboradores do seu repositório, você precisa de uma comunidade que incentive as pessoas a usar, contribuir e evangelizar o seu projeto. Para obter mais informações, consulte "[Criando comunidades de bem-estar](https://opensource.guide/building-community/)" nos guias de código aberto. -By adding files like contributing guidelines, a code of conduct, and a license to your repository you can create an environment where it's easier for collaborators to make meaningful, useful contributions. Para obter mais informações, consulte "[Configurando seu projeto para Contribuições Úteis](/communities/setting-up-your-project-for-healthy-contributions)." +Ao adicionar arquivos como diretrizes de contribuição, um código de conduta e uma licença para o repositório é possível criar um ambiente em que seja mais fácil para os colaboradores fazerem contribuições úteis e significativas. Para obter mais informações, consulte "[Configurando seu projeto para Contribuições Úteis](/communities/setting-up-your-project-for-healthy-contributions)." {% endif %} {% ifversion ghes or ghae %} -By adding files like contributing guidelines, a code of conduct, and support resources to your repository you can create an environment where it's easier for collaborators to make meaningful, useful contributions. Para obter mais informações, consulte "[Configurando seu projeto para Contribuições Úteis](/communities/setting-up-your-project-for-healthy-contributions)." +Ao adicionar arquivos como diretrizes de contribuição, um código de conduta, e recursos de suporte ao seu repositório, você pode criar um ambiente em que seja mais fácil para os colaboradores fazerem contribuições significativas e úteis. Para obter mais informações, consulte "[Configurando seu projeto para Contribuições Úteis](/communities/setting-up-your-project-for-healthy-contributions)." {% endif %} -### 6. Using GitHub Issues and project boards -You can use GitHub Issues to organize your work with issues and pull requests and manage your workflow with project boards. For more information, see "[About issues](/issues/tracking-your-work-with-issues/about-issues)" and "[About project boards](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." +### 6. Usando os problemas e os quadros de projeto do GitHub +Você pode usar os problemas do GitHub para organizar seu trabalho com problemas e pull requests, bem como gerenciar seu fluxo de trabalho com quadros de projetos. Para obter mais informações, consulte "[Sobre os problemas](/issues/tracking-your-work-with-issues/about-issues)" e "[Sobre os quadros de projeto](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)". -### 7. Managing notifications -Notifications provide updates about the activity on {% data variables.product.product_name %} you've subscribed to or participated in. Se não estiver mais interessado em uma conversa, cancele a assinatura dela, deixe de acompanhar ou personalize os tipos de notificações que você receberá no futuro. Para obter mais informações, consulte "[Sobre notificações](/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)". +### 7. Gerenciando notificações +As notificações fornecem atualizações sobre a atividade em {% data variables.product.product_name %} que você assinou ou da qual você participou. Se não estiver mais interessado em uma conversa, cancele a assinatura dela, deixe de acompanhar ou personalize os tipos de notificações que você receberá no futuro. Para obter mais informações, consulte "[Sobre notificações](/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)". ### 8. Trabalhar com o {% data variables.product.prodname_pages %} -You can use {% data variables.product.prodname_pages %} to create and host a website directly from a {% data variables.product.product_name %} repository. For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)." +Você pode usar {% data variables.product.prodname_pages %} para criar e hospedar um site diretamente de um repositório do {% data variables.product.product_name %}. For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)." {% ifversion fpt %} ### 9. Usar {% data variables.product.prodname_discussions %} -You can enable {% data variables.product.prodname_discussions %} for your repository to help build a community around your project. Maintainers, contributors and visitors can use discussions to share announcements, ask and answer questions, and participate in conversations around goals. Para obter mais informações, consulte "[Sobre discussões](/discussions/collaborating-with-your-community-using-discussions/about-discussions)". +Você pode habilitar {% data variables.product.prodname_discussions %} para o repositório ajudar a criar uma comunidade em torno do seu projeto. Mantenedores, colaboradores e visitantes podem usar discussões para compartilhar anúncios, fazer e responder a perguntas e participar de conversas sobre objetivos. Para obter mais informações, consulte "[Sobre discussões](/discussions/collaborating-with-your-community-using-discussions/about-discussions)". {% endif %} -## Part 4: Customizing and automating your work on {% data variables.product.product_name %} +## Parte 4: Personalizando e automatizando seu trabalho em {% data variables.product.product_name %} {% data reusables.getting-started.customizing-and-automating %} @@ -147,47 +147,47 @@ You can enable {% data variables.product.prodname_discussions %} for your reposi ### 1. Usar {% data variables.product.prodname_marketplace %} {% data reusables.getting-started.marketplace %} {% endif %} -### {% ifversion fpt %}2.{% else %}1.{% endif %} Using the {% data variables.product.prodname_dotcom %} API +### {% ifversion fpt %}2.{% else %}1.{% endif %} Usando a API de{% data variables.product.prodname_dotcom %} {% data reusables.getting-started.api %} -### {% ifversion fpt %}3.{% else %}2.{% endif %} Building {% data variables.product.prodname_actions %} +### {% ifversion fpt %}3.{% else %}2.{% endif %} Criando {% data variables.product.prodname_actions %} {% data reusables.getting-started.actions %} -### {% ifversion fpt %}4.{% else %}3.{% endif %} Publishing and managing {% data variables.product.prodname_registry %} +### {% ifversion fpt %}4.{% else %}3.{% endif %} Publicando e gerenciando {% data variables.product.prodname_registry %} {% data reusables.getting-started.packages %} {% ifversion fpt or ghae or ghes > 2.22 %} -## Part 5: Building securely on {% data variables.product.product_name %} -{% data variables.product.product_name %} has a variety of security features that help keep code and secrets secure in repositories. Some features are available for all repositories, while others are only available for public repositories and repositories with a {% data variables.product.prodname_GH_advanced_security %} license. For an overview of {% data variables.product.product_name %} security features, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)." +## Parte 5: Criando com segurança em {% data variables.product.product_name %} +{% data variables.product.product_name %} tem uma variedade de recursos de segurança que ajudam a manter códigos e segredos seguros nos repositórios. Algumas funcionalidades estão disponíveis para todos os repositórios, enquanto outras estão disponíveis apenas para repositórios públicos e repositórios com uma licença de {% data variables.product.prodname_GH_advanced_security %}. Para uma visão geral das funcionalidades de segurança de {% data variables.product.product_name %}, consulte "[Funcionalidades de segurança de {% data variables.product.prodname_dotcom %}](/code-security/getting-started/github-security-features)". ### 1. Proteger o repositório -As a repository administrator, you can secure your repositories by configuring repository security settings. These include managing access to your repository, setting a security policy, and managing dependencies. For public repositories, and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled, you can also configure code and secret scanning to automatically identify vulnerabilities and ensure tokens and keys are not exposed. +Como administrador do repositório, você pode proteger os seus repositórios definindo as configurações de segurança do repositório. Elas incluem o gerenciamento de acesso ao seu repositório, a definição de uma política de segurança e o gerenciamento de dependências. Para repositórios públicos e para repositórios privados pertencentes a organizações em que o {% data variables.product.prodname_GH_advanced_security %} está habilitado, você também pode configurar o código e a digitalização de segredos para identificar automaticamente vulnerabilidades e garantir que os tokens e chaves não sejam expostos. -For more information on steps you can take to secure your repositories, see "[Securing your repository](/code-security/getting-started/securing-your-repository)." +Para obter mais informações sobre as medidas que você pode tomar para proteger seus repositórios, consulte "[Protegendo seu repositório](/code-security/getting-started/securing-your-repository)". {% endif %} {% ifversion fpt %} -### 2. Managing your dependencies -A large part of building securely is maintaining your project's dependencies to ensure that all packages and applications you depend on are updated and secure. You can manage your repository's dependencies on {% data variables.product.product_name %} by exploring the dependency graph for your repository, using Dependabot to automatically raise pull requests to keep your dependencies up-to-date, and receiving Dependabot alerts and security updates for vulnerable dependencies. +### 2. Gerenciando suas dependências +Uma grande parte da criação é manter as dependências do seu projeto para garantir que todos os pacotes e aplicativos dos quais você depende estejam atualizados e seguros. Você pode gerenciar as dependências do seu repositório em {% data variables.product.product_name %}, explorando o gráfico de dependências para o seu repositório, usando o Dependabot para aumentar automaticamente os pull requests para manter as suas dependências atualizadas e receber alertas de dependência e atualizações de segurança para dependências vulneráveis. -For more information, see "[Securing your software supply chain](/code-security/supply-chain-security)." +Para obter mais informações, consulte "[Protegendo a cadeia de suprimentos do seu software](/code-security/supply-chain-security)". {% endif %} -## Part {% ifversion ghes < 3.0 %}5:{% else %}6:{% endif %} Participating in {% data variables.product.prodname_dotcom %}'s community +## Parte {% ifversion ghes < 3.0 %}5:{% else %}6:{% endif %} Participando da comunidade de {% data variables.product.prodname_dotcom %} {% data reusables.getting-started.participating-in-community %} -### 1. Contributing to open source projects +### 1. Contribuindo para projetos de código aberto {% data reusables.getting-started.open-source-projects %} -### 2. Interacting with {% data variables.product.prodname_gcf %} +### 2. Interagindo com {% data variables.product.prodname_gcf %} {% data reusables.support.ask-and-answer-forum %} -### 3. Learning with {% data variables.product.prodname_learning %} +### 3. Aprendendo com {% data variables.product.prodname_learning %} {% data reusables.getting-started.learning-lab %} {% ifversion fpt %} -### 4. Supporting the open source community +### 4. Apoiar a comunidade de código aberto {% data reusables.getting-started.sponsors %} ### 5. Entrar em contato com o {% data variables.contact.github_support %} diff --git a/translations/pt-BR/content/get-started/onboarding/index.md b/translations/pt-BR/content/get-started/onboarding/index.md index a258e00fdc..0feb682910 100644 --- a/translations/pt-BR/content/get-started/onboarding/index.md +++ b/translations/pt-BR/content/get-started/onboarding/index.md @@ -1,5 +1,5 @@ --- -title: Onboarding +title: Integração intro: '' versions: fpt: '*' diff --git a/translations/pt-BR/content/get-started/quickstart/be-social.md b/translations/pt-BR/content/get-started/quickstart/be-social.md index 6f1eeb2c1a..8dcc75033d 100644 --- a/translations/pt-BR/content/get-started/quickstart/be-social.md +++ b/translations/pt-BR/content/get-started/quickstart/be-social.md @@ -6,6 +6,7 @@ redirect_from: - /github/getting-started-with-github/be-social - /github/getting-started-with-github/quickstart/be-social intro: 'Você pode interagir com pessoas, repositórios e organizações no {% data variables.product.prodname_dotcom %}. Veja em seu painel pessoal no que as outras pessoas estão trabalhando e com quem estão se conectando.' +permissions: '{% data reusables.enterprise-accounts.emu-permission-interact %}' versions: fpt: '*' ghes: '*' diff --git a/translations/pt-BR/content/get-started/quickstart/create-a-repo.md b/translations/pt-BR/content/get-started/quickstart/create-a-repo.md index adff0be00a..48b6981579 100644 --- a/translations/pt-BR/content/get-started/quickstart/create-a-repo.md +++ b/translations/pt-BR/content/get-started/quickstart/create-a-repo.md @@ -58,14 +58,14 @@ Parabéns! Você criou com êxito seu primeiro repositório e o inicializou com {% data reusables.cli.cli-learn-more %} -1. In the command line, navigate to the directory where you would like to create a local clone of your new project. -2. To create a repository for your project, use the `gh repo create` subcommand. Replace `project-name` with the desired name for your repository. If you want your project to belong to an organization instead of to your user account, specify the organization name and project name with `organization-name/project-name`. +1. Na linha de comando, acesse o diretório onde você gostaria de criar um clone local do seu novo projeto. +2. Para criar um repositório para o seu projeto, use o subcomando `gh repo create`. Substitua `project-name` pelo nome desejado para o repositório. Se você quiser que o seu projeto pertença a uma organização em vez de sua conta de usuário, especifique o nome da organização e o nome do projeto com `organization-name/project-name`. ```shell gh repo create project-name ``` -3. Follow the interactive prompts. To clone the repository locally, confirm yes when asked if you would like to clone the remote project directory. Alternatively, you can specify arguments to skip these prompts. For more information about possible arguments, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_repo_create). +3. Siga as instruções interativas. Para clonar o repositório localmente, marque sim quando perguntarem se você deseja clonar o diretório do projeto remoto. Como alternativa, você pode especificar argumentos para pular essas instruções. Para obter mais informações sobre possíveis argumentos, consulte [o manual de {% data variables.product.prodname_cli %}](https://cli.github.com/manual/gh_repo_create). {% endcli %} @@ -94,18 +94,18 @@ Vamos fazer commit de uma alteração no arquivo *README*. {% cli %} -Now that you have created a project, you can start committing changes. +Agora que você criou um projeto, você pode começar a fazer commit das alterações. -Os arquivos *README* são um excelente local para descrever seu projeto mais detalhadamente ou para adicionar alguma documentação, por exemplo, como instalar ou usar seu projeto. O conteúdo do arquivo *README* é mostrado automaticamente na primeira página do repositório. Follow these steps to add a *README* file. +Os arquivos *README* são um excelente local para descrever seu projeto mais detalhadamente ou para adicionar alguma documentação, por exemplo, como instalar ou usar seu projeto. O conteúdo do arquivo *README* é mostrado automaticamente na primeira página do repositório. Siga estas etapas para adicionar um arquivo *README*. -1. In the command line, navigate to the root directory of your new project. (This directory was created when you ran the `gh repo create` command.) -1. Create a *README* file with some information about the project. +1. Na linha de comando, acesse o diretório raiz do seu novo projeto. (Este diretório foi criado quando você executou o repositório `gh repo create`.) +1. Crie um arquivo *README* com algumas informações sobre o projeto. ```shell echo "info about this project" >> README.md ``` -1. Enter `git status`. You will see that you have an untracked `README.md` file. +1. Insira `git status`. Você verá que você tem um arquivo `README.md` não rastreado. ```shell $ git status @@ -117,13 +117,13 @@ Os arquivos *README* são um excelente local para descrever seu projeto mais det nothing added to commit but untracked files present (use "git add" to track) ``` -1. Stage and commit the file. +1. Stage e commit do arquivo. ```shell git add README.md && git commit -m "Add README" ``` -1. Push the changes to your branch. +1. Faça push das alterações para seu branch. ```shell git push --set-upstream origin HEAD diff --git a/translations/pt-BR/content/get-started/quickstart/fork-a-repo.md b/translations/pt-BR/content/get-started/quickstart/fork-a-repo.md index 1276a09e7e..b65a30111c 100644 --- a/translations/pt-BR/content/get-started/quickstart/fork-a-repo.md +++ b/translations/pt-BR/content/get-started/quickstart/fork-a-repo.md @@ -7,6 +7,7 @@ redirect_from: - /github/getting-started-with-github/fork-a-repo - /github/getting-started-with-github/quickstart/fork-a-repo intro: Uma bifurcação é uma cópia de um repositório. Bifurcar um repositório permite que você faça experiências à vontade sem comprometer o projeto original. +permissions: '{% data reusables.enterprise-accounts.emu-permission-fork %}' versions: fpt: '*' ghes: '*' @@ -83,7 +84,7 @@ gh repo fork repository --org "octo-org" ## Clonando o seu repositório bifurcado -Right now, you have a fork of the Spoon-Knife repository, but you don't have the files in that repository locally on your computer. +Agora, você tem uma bifurcação do repositório Spoon-Knife, mas você não tem os arquivos nesse repositório localmente no seu computador. {% include tool-switcher %} {% webui %} diff --git a/translations/pt-BR/content/get-started/quickstart/set-up-git.md b/translations/pt-BR/content/get-started/quickstart/set-up-git.md index 26760bbe27..06dcae02ca 100644 --- a/translations/pt-BR/content/get-started/quickstart/set-up-git.md +++ b/translations/pt-BR/content/get-started/quickstart/set-up-git.md @@ -26,7 +26,7 @@ topics: ## Usar o Git -Para usar o Git na linha de comando, você precisará fazer download, instalar e configurar o Git no computador. You can also install {% data variables.product.prodname_cli %} to use {% data variables.product.product_name %} from the command line. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)". +Para usar o Git na linha de comando, você precisará fazer download, instalar e configurar o Git no computador. Você também pode instalar {% data variables.product.prodname_cli %} para usar {% data variables.product.product_name %} a partir da linha de comando. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)". Se quiser trabalhar com o Git, mas não quiser usar a linha de comando, você poderá baixar e instalar o cliente do [{% data variables.product.prodname_desktop %}]({% data variables.product.desktop_link %}). Para obter mais informações, consulte "[Instalar e configurar o {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/)". @@ -49,7 +49,7 @@ Quando você se conecta a um repositório do {% data variables.product.product_n {% note %} -**Note:** You can authenticate to {% data variables.product.product_name %} using {% data variables.product.prodname_cli %}, for either HTTP or SSH. For more information, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login). +**Observação:** Você pode efetuar a autenticação em {% data variables.product.product_name %} usando {% data variables.product.prodname_cli %}, para HTTP ou SSH. Para obter mais informações, consulte [`login gh auth`](https://cli.github.com/manual/gh_auth_login). {% endnote %} diff --git a/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md b/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md index 650c81c723..6bd35ed5ac 100644 --- a/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md +++ b/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md @@ -20,7 +20,7 @@ shortTitle: Desafio da nuvem corporativa {% data reusables.organizations.about-organizations %} -You can use organizations for free with {% data variables.product.prodname_free_team %}, which includes limited features. For additional features, such as SAML single sign-on (SSO), access control for {% data variables.product.prodname_pages %}, and included {% data variables.product.prodname_actions %} minutes, you can upgrade to {% data variables.product.prodname_ghe_cloud %}. For a detailed list of the features available with {% data variables.product.prodname_ghe_cloud %}, see our [Pricing](https://github.com/pricing) page. +Você pode usar organizações gratuitamente com {% data variables.product.prodname_free_team %}, que inclui recursos limitados. Para funcionalidades adicionais, como o logon único SAML (SSO), controle de acesso para {% data variables.product.prodname_pages %} e minutos de {% data variables.product.prodname_actions %} incluídos, você pode fazer a atualização para {% data variables.product.prodname_ghe_cloud %}. Para obter uma lista detalhada dos recursos disponíveis com {% data variables.product.prodname_ghe_cloud %}, consulte nossa página de [Preços](https://github.com/pricing). {% data reusables.saml.saml-accounts %} Para obter mais informações, consulte "Sobre identidade e gerenciamento de acesso com o logon único SAML". @@ -28,7 +28,7 @@ You can use organizations for free with {% data variables.product.prodname_free_ ## Sobre as versões de avaliação do {% data variables.product.prodname_ghe_cloud %} -You can set up a 14-day trial to evaluate {% data variables.product.prodname_ghe_cloud %}. Não há necessidade de fornecer um método de pagamento durante a avaliação, a menos que você adicione à sua organização aplicativos do {% data variables.product.prodname_marketplace %} que exijam um método de pagamento. Para obter mais informações, consulte "Sobre a cobrança do {% data variables.product.prodname_marketplace %}". +Você pode definir uma avaliação de 14 dias para avaliar {% data variables.product.prodname_ghe_cloud %}. Não há necessidade de fornecer um método de pagamento durante a avaliação, a menos que você adicione à sua organização aplicativos do {% data variables.product.prodname_marketplace %} que exijam um método de pagamento. Para obter mais informações, consulte "Sobre a cobrança do {% data variables.product.prodname_marketplace %}". Sua versão de avaliação inclui 50 estações. Se precisar de mais estações para avaliar o {% data variables.product.prodname_ghe_cloud %}, entre em contato com {% data variables.contact.contact_enterprise_sales %}. Ao final da avaliação, você poderá escolher um número diferente de estações. @@ -36,12 +36,12 @@ As versões de avaliação também estão disponíveis para o {% data variables. ## Configurar a versão de avaliação do {% data variables.product.prodname_ghe_cloud %} -Before you can try {% data variables.product.prodname_ghe_cloud %}, you must be signed into a user account. If you don't already have a user account on {% data variables.product.prodname_dotcom_the_website %}, you must create one. Para obter mais informações, consulte "Inscrever-se em uma nova conta do {% data variables.product.prodname_dotcom %}". +Antes de testar {% data variables.product.prodname_ghe_cloud %}, você deverá estar conectado a uma conta de usuário. Se você ainda não tem uma conta de usuário em {% data variables.product.prodname_dotcom_the_website %}, você deverá criar uma. Para obter mais informações, consulte "Inscrever-se em uma nova conta do {% data variables.product.prodname_dotcom %}". -1. Navigate to [{% data variables.product.prodname_dotcom %} for enterprises](https://github.com/enterprise). -1. Click **Start a free trial**. !["Start a free trial" button](/assets/images/help/organizations/start-a-free-trial-button.png) -1. Click **Enterprise Cloud**. !["Enterprise Cloud" button](/assets/images/help/organizations/enterprise-cloud-trial-option.png) -1. Follow the prompts to configure your trial. +1. Acesse [{% data variables.product.prodname_dotcom %} para as empresas](https://github.com/enterprise). +1. Clique em **Iniciar teste grátis**. ![Botão "Iniciar teste grátisl"](/assets/images/help/organizations/start-a-free-trial-button.png) +1. Clique em **Nuvem Corporativa**. ![Botão "Nuvem Corporativa"](/assets/images/help/organizations/enterprise-cloud-trial-option.png) +1. Siga as instruções para configurar seu teste. ## Explorar o {% data variables.product.prodname_ghe_cloud %} diff --git a/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md b/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md index fa22ad8734..a45c11c2e8 100644 --- a/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md +++ b/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md @@ -18,7 +18,7 @@ shortTitle: Teste do servidor corporativo Você pode solicitar uma versão de avaliação por 45 dias do {% data variables.product.prodname_ghe_server %}. A versão de avaliação será instalada como um appliance virtual, com opções para implementação local ou na nuvem. Consulte a lista de plataformas de visualização compatíveis em "[Configurar uma instância do GitHub Enterprise Server](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance)". -{% ifversion ghes %}{% data variables.product.prodname_dependabot %}{% else %}Alertas de Segurança{% endif %} e {% data variables.product.prodname_github_connect %} não estão disponíveis atualmente nos testes de {% data variables.product.prodname_ghe_server %}. Para uma demonstração desses recursos, entre em contato com {% data variables.contact.contact_enterprise_sales %}. Para obter mais informações sobre esses recursos, consulte "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" e "[Conectando {% data variables.product.prodname_ghe_server %} a {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)". +{% ifversion ghes %}{% data variables.product.prodname_dependabot %}{% else %}Alertas de Segurança{% endif %} e {% data variables.product.prodname_github_connect %} não estão disponíveis atualmente nos testes de {% data variables.product.prodname_ghe_server %}. Para uma demonstração desses recursos, entre em contato com {% data variables.contact.contact_enterprise_sales %}. Para mais informações sobre esses recursos, consulte "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" e "[Conectando a sua conta corporativa a {% data variables.product.prodname_dotcom_the_website %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)" As versões de avaliação também estão disponíveis para {% data variables.product.prodname_ghe_cloud %}. Para obter mais informações, consulte "[Configurar uma versão de avaliação do {% data variables.product.prodname_ghe_cloud %}](/articles/setting-up-a-trial-of-github-enterprise-cloud)". @@ -28,7 +28,7 @@ As versões de avaliação também estão disponíveis para {% data variables.pr O {% data variables.product.prodname_ghe_server %} é instalado como um appliance virtual. Escolha uma pessoa na organização para configurar uma máquina virtual e peça para ela [solicitar uma versão de avaliação](https://enterprise.github.com/trial). Você pode iniciar a versão de avaliação imediatamente após enviar a solicitação. -Para configurar uma conta para o portal da web do {% data variables.product.prodname_enterprise %}, clique no link no e-mail recebido após enviar a solicitação da versão de avaliação e siga as instruções. Depois, baixe seu arquivo de licença. For more information, see "[Managing your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise)." +Para configurar uma conta para o portal da web do {% data variables.product.prodname_enterprise %}, clique no link no e-mail recebido após enviar a solicitação da versão de avaliação e siga as instruções. Depois, baixe seu arquivo de licença. Para obter mais informações, consulte "[Gerenciar a sua licença para {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise)." Para instalar o {% data variables.product.prodname_ghe_server %}, faça download dos componentes necessários e faça upload do arquivo da licença. Para obter mais informações, consulte as instruções da plataforma de visualização escolhida em "[Configurar uma instância do {% data variables.product.prodname_ghe_server %}](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance)". diff --git a/translations/pt-BR/content/get-started/using-git/dealing-with-special-characters-in-branch-and-tag-names.md b/translations/pt-BR/content/get-started/using-git/dealing-with-special-characters-in-branch-and-tag-names.md new file mode 100644 index 0000000000..1c91dc7b87 --- /dev/null +++ b/translations/pt-BR/content/get-started/using-git/dealing-with-special-characters-in-branch-and-tag-names.md @@ -0,0 +1,48 @@ +--- +title: Lidando com caracteres especiais nos nomes do branch e tags +intro: 'O Git é muito permissivo sobre quais caracteres são permitidos nos nomes de branches e tags. Ao usar o Git em uma linha de comando, talvez seja necessário que você escape ou cite caracteres especiais.' +versions: + fpt: '*' + ghes: '*' + ghae: '*' +shortTitle: Caracteres especiais em nomes +--- + +## Sobre os nomes dos branches e tags + +A maioria dos repositórios usa nomes de branch simples, como `main` ou `update-icons`. Os nomes das etiquetas também geralmente seguem um formato básico, como um número de versão como `v1.2.3`. Ambos os nomes de branches e tags também podem usar o separador de caminho (`/`) para estrutura como, por exemplo, `area/item` ou `level-1/level-2/level-3`. Além de algumas exceções — como não iniciar ou terminar um nome com uma barra, ou ter barras consecutivas no nome — O Git tem muito poucas restrições sobre quais caracteres podem ser usados em nomes de branches e tags. Para obter mais informações, consulte "[git-check-ref-formato](https://git-scm.com/docs/git-check-ref-format)" na documentação do Git. + +## Por que você precisa escapar de caracteres especiais + +Ao usar uma CLI, você pode passar por situações em que um branch ou tag contém caracteres especiais com um significado especial para o ambiente do seu shell. Para usar estes caracteres com segurança em um comando Git, eles devem ser citados ou escapados. Caso contrário, o comando poderá ter efeitos indesejados. + +Por exemplo, o caractere `$` é usado por muitos shells para referir-se a uma variável. A maioria dos shells interpretaria o nome de um branch válido como `hello-$USER` como um equivalente à palavra "hello", seguido por um hífen, seguido pelo valor atual do `USUÁRIO` variável, em vez da string literal `hello-$USER`. Se o nome de um branch incluir o caractere `$`, o shell deverá ser impedido de expandi-lo como uma referência variável. Da mesma forma, se um nome de branch contiver um ponto e vírgula (`;`), a maioria dos shells o interpretam como um separador de comando. Portanto, ele precisa ser citado ou escapado. + +## Como escapar dos caracteres especiais em nomes de branches e tags + +A maioria dos nomes de branches e tags com caracteres especiais podem ser administrados, incluindo o nome em aspas simples, por exemplo `'hello-$USER'`. + +* No shell [Bash](https://www.gnu.org/software/bash/), que contém uma série de caracteres em aspas simples, preserva o valor literal dos caracteres dentro das aspas simples. +* [Zsh](https://www.zsh.org/) comporta-se de forma parecida ao Bash. No entanto este comportamento pode ser configurado usando a opção `RC_QUOTES`. +* [PowerShell](https://microsoft.com/powershell) também trata caracteres literalmente quando dentro de aspas simples. + +Para esses shells, a exceção principal é quando o nome do branch ou tag em si contém aspas simples. Neste caso, você deve consultar a documentação oficial para seu shell: + +* [Documentação do Bash](https://www.gnu.org/software/bash/manual/) +* [Documentação do Zsh](https://zsh.sourceforge.io/Doc/) +* [Documentação do Fish](https://fishshell.com/docs/current/) +* [Documentação do PowerShell](https://docs.microsoft.com/en-gb/powershell/) + +## Nomeando branches e tags + +Se possível, crie nomes de branches e tags que não contenham caracteres especiais, pois seria necessário escapar deles. Um conjunto padrão seguro de caracteres para usar para nomes de branches e tags é: + +* O alfabeto inglês ( `a` a `z` e `A` a `Z`) +* Números (`0` a `9`) +* Um conjunto limitado de caracteres de pontuação: + * ponto (`.`) + * hífen (`-`) + * sublinhado (`_`) + * barra (`/`) + +Para evitar confusão, você deve iniciar os nomes dos branches com uma letra. diff --git a/translations/pt-BR/content/get-started/using-git/index.md b/translations/pt-BR/content/get-started/using-git/index.md index f3520b8ce6..5a47c32544 100644 --- a/translations/pt-BR/content/get-started/using-git/index.md +++ b/translations/pt-BR/content/get-started/using-git/index.md @@ -23,5 +23,6 @@ children: - /about-git-rebase - /using-git-rebase-on-the-command-line - /resolving-merge-conflicts-after-a-git-rebase + - /dealing-with-special-characters-in-branch-and-tag-names --- diff --git a/translations/pt-BR/content/get-started/using-git/pushing-commits-to-a-remote-repository.md b/translations/pt-BR/content/get-started/using-git/pushing-commits-to-a-remote-repository.md index 4ec7ccfa3e..441c02a246 100644 --- a/translations/pt-BR/content/get-started/using-git/pushing-commits-to-a-remote-repository.md +++ b/translations/pt-BR/content/get-started/using-git/pushing-commits-to-a-remote-repository.md @@ -14,7 +14,7 @@ versions: shortTitle: Fazer push de commits para um controle remoto --- -## About `git push` +## Sobre `git push` O comando `git push` usa dois argumentos: * Um nome de remote, por exemplo, `origin` diff --git a/translations/pt-BR/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md b/translations/pt-BR/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md index 069c15aa33..8bb86847a3 100644 --- a/translations/pt-BR/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md +++ b/translations/pt-BR/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md @@ -26,8 +26,8 @@ Se você criar um clone do repositório, não perderá nenhuma alteração ou hi ```shell $ cd REPOSITORY-NAME ``` -5. To filter out the subfolder from the rest of the files in the repository, run [`git filter-repo`](https://github.com/newren/git-filter-repo), supplying this information: - - `FOLDER-NAME`: The folder within your project where you'd like to create a separate repository. +5. Para filtrar a subpasta do restante dos arquivos no repositório, execute [`git filter-repo`](https://github.com/newren/git-filter-repo), fornecendo estas informações: + - `FOLDER-NAME`: A pasta dentro do seu projeto onde você deseja criar um repositório separado. {% windows %} @@ -45,7 +45,7 @@ Se você criar um clone do repositório, não perderá nenhuma alteração ou hi > Rewrite 48dc599c80e20527ed902928085e7861e6b3cbe6 (89/89) > Ref 'refs/heads/BRANCH-NAME' was rewritten ``` - The repository should now only contain the files that were in your subfolder(s). + Agora o repositório deve conter apenas os arquivos que estava(m) na(s) subpasta(s). 6. [Crie um repositório](/articles/creating-a-new-repository/) no {% data variables.product.product_name %}. 7. No topo da página Quick Setup (Configuração rápida) do novo repositório do {% data variables.product.product_name %}, clique em {% octicon "clippy" aria-label="The copy to clipboard icon" %} para copiar a URL do repositório remote. ![Campo Copy remote repository URL (Copiar URL do repositório remote)](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png) diff --git a/translations/pt-BR/content/get-started/using-github/github-cli.md b/translations/pt-BR/content/get-started/using-github/github-cli.md index 977d614119..c5a80d08c9 100644 --- a/translations/pt-BR/content/get-started/using-github/github-cli.md +++ b/translations/pt-BR/content/get-started/using-github/github-cli.md @@ -13,4 +13,4 @@ topics: {% data reusables.cli.cli-features %} -For more information, see "[{% data variables.product.prodname_cli %}](/github-cli)." +Para obter mais informações, consulte "[{% data variables.product.prodname_cli %}](/github-cli)". diff --git a/translations/pt-BR/content/get-started/using-github/github-for-mobile.md b/translations/pt-BR/content/get-started/using-github/github-for-mobile.md index 9d7fcde523..b5fa03a1cd 100644 --- a/translations/pt-BR/content/get-started/using-github/github-for-mobile.md +++ b/translations/pt-BR/content/get-started/using-github/github-for-mobile.md @@ -79,7 +79,7 @@ Para reabilitar o Universal Links, mantenha pressionado qualquer link {% data va Se você encontrar um erro em {% data variables.product.prodname_mobile %}, você pode nos enviar um e-mail para mobilefeedback@github.com. -You can submit feature requests or other feedback for {% data variables.product.prodname_mobile %} on [{% data variables.product.prodname_discussions %}](https://github.com/github/feedback/discussions?discussions_q=category%3A%22Mobile+Feedback%22). +Você pode enviar solicitações de recursos ou outros feedbacks para {% data variables.product.prodname_mobile %} em [{% data variables.product.prodname_discussions %}](https://github.com/github/feedback/discussions?discussions_q=category%3A%22Mobile+Feedback%22). ## Desativando versões beta para iOS 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 18e7c7b625..67ef5cfd57 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 @@ -24,7 +24,7 @@ Veja abaixo uma lista dos atalhos de teclado disponíveis. | Atalho | Descrição | | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| s or / | Evidencia a barra de pesquisa. Para obter mais informações, consulte "[Sobre pesquisar no {% data variables.product.company_short %}](/articles/about-searching-on-github)". | +| 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 %}"[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á | @@ -42,23 +42,23 @@ Veja abaixo uma lista dos atalhos de teclado disponíveis. ## Edição de código-fonte -| Atalho | Descrição | -| --------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion fpt %} -| . | Opens a repository or pull request in the web-based editor. For more information, see "[Web-based editor](/codespaces/developing-in-codespaces/web-based-editor)."{% endif %} -| control b ou command b | Insere formatação Markdown para texto em negrito | -| control i ou command i | Insere formatação Markdown para texto em itálico | -| control k ou command k | Insere formatação Markdown para criar um link | -| e | Abra o arquivo de código-fonte na aba **Editar arquivo** | -| control f ou command f | Começa a pesquisar no editor de arquivo | -| control g ou command g | Localiza o próximo | -| shift control g ou shift command g | Localiza o anterior | -| shift control f ou command option f | Substitui | -| shift control r ou shift command option f | Substitui todos | -| alt g | Pula para linha | -| control z ou command z | Desfaz | -| control y ou command y | Refaz | -| cmd + shift + p | Alterna entre as abas **Edit file** (Editar aquivo) e **Preview changes** (Visualizar alterações) | -| control s ou comando s | Escrever uma mensagem de commit | +| Atalho | Descrição | +| --------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion fpt %} +| . | Abre um repositório ou um pull request no editor baseado na web. Para obter mais informações, consulte "[Editor baseado na web](/codespaces/developing-in-codespaces/web-based-editor)".{% endif %} +| control b ou command b | Insere formatação Markdown para texto em negrito | +| control i ou command i | Insere formatação Markdown para texto em itálico | +| control k ou command k | Insere formatação Markdown para criar um link | +| e | Abra o arquivo de código-fonte na aba **Editar arquivo** | +| control f ou command f | Começa a pesquisar no editor de arquivo | +| control g ou command g | Localiza o próximo | +| shift control g ou shift command g | Localiza o anterior | +| shift control f ou command option f | Substitui | +| shift control r ou shift command option f | Substitui todos | +| alt g | Pula para linha | +| control z ou command z | Desfaz | +| control y ou command y | Refaz | +| cmd + shift + p | Alterna entre as abas **Edit file** (Editar aquivo) e **Preview changes** (Visualizar alterações) | +| control s ou comando s | Escrever uma mensagem de commit | Para mais atalhos de teclado, consulte a [Documentação CodeMirror](https://codemirror.net/doc/manual.html#commands). @@ -82,28 +82,28 @@ Para mais atalhos de teclado, consulte a [Documentação CodeMirror](https://cod | control i ou command i | Insere a formatação Markdown para texto em itálico{% ifversion fpt or ghae-next or ghes > 3.1 %} | controle e ou comando e | Insere a formatação Markdown para código ou um comando dentro da linha{% endif %} | control k ou command k | Insere formatação Markdown para criar um link | -| control shift p ou command shift p | Toggles between the **Write** and **Preview** comment tabs{% ifversion fpt or ghae-next or ghes > 3.2 %} -| control shift 7 or command shift 7 | Inserts Markdown formatting for an ordered list | -| control shift 8 or command shift 8 | Inserts Markdown formatting for an unordered list{% endif %} +| control shift p ou command shift p | Alterna entre as abas de comentários **Escrever** e **Visualizar**{% ifversion fpt or ghae-next or ghes > 3.2 %} +| control shift 7 ou command shift 7 | Insere a formatação de Markdown para uma lista ordenada | +| control shift 8 ou command shift 8 | Insere a formatação Markdown para uma lista não ordenada{% endif %} | control enter | Envia um comentário | | control . e control [número de resposta salvo] | Abre o menu de respostas salvas e autocompleta o campo de comentário com uma resposta salva. Para obter mais informações, consulte "[Sobre respostas salvas](/articles/about-saved-replies)".{% ifversion fpt or ghae-next or ghes > 3.2 %} -| control shift . or command shift. | Inserts Markdown formatting for a quote{% endif %}{% ifversion fpt %} +| control shift . ou command shift. | Insere a formatação Markdown para uma citação{% endif %}{% ifversion fpt %} | control g ou command g | Insere uma sugestão. Para obter mais informações, consulte "[Revisar alterações propostas em uma pull request](/articles/reviewing-proposed-changes-in-a-pull-request)". {% 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 | -| -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| c | Cria um problema | -| control / ou command / | Evidencia seu cursor na barra de pesquisa de problemas e pull requests. For more information, see "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)."| | -| u | Filtra por autor | -| l | Filtra por ou edita etiquetas. Para obter mais informações, consulte "[Filtrar problemas e pull requests por etiquetas](/articles/filtering-issues-and-pull-requests-by-labels)". | -| alt e clique | Ao filtrar por etiquetas, exclui etiquetas. Para obter mais informações, consulte "[Filtrar problemas e pull requests por etiquetas](/articles/filtering-issues-and-pull-requests-by-labels)". | -| m | Filtra por ou edita marcos. Para obter mais informações, consulte "[Filtrar problemas e pull requests por marcos](/articles/filtering-issues-and-pull-requests-by-milestone)". | -| a | Filtra por ou edita um responsável. Para obter mais informações, consulte "[Filtrar problemas e pull requests por responsáveis](/articles/filtering-issues-and-pull-requests-by-assignees)". | -| o ou enter | Abre um problema | +| Atalho | Descrição | +| -------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| c | Cria um problema | +| control / ou command / | Evidencia seu cursor na barra de pesquisa de problemas e pull requests. Para obter mais informações, consulte "[Filtrando e pesquisando problemas e pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests). "£" | +| u | Filtra por autor | +| l | Filtra por ou edita etiquetas. Para obter mais informações, consulte "[Filtrar problemas e pull requests por etiquetas](/articles/filtering-issues-and-pull-requests-by-labels)". | +| alt e clique | Ao filtrar por etiquetas, exclui etiquetas. Para obter mais informações, consulte "[Filtrar problemas e pull requests por etiquetas](/articles/filtering-issues-and-pull-requests-by-labels)". | +| m | Filtra por ou edita marcos. Para obter mais informações, consulte "[Filtrar problemas e pull requests por marcos](/articles/filtering-issues-and-pull-requests-by-milestone)". | +| a | Filtra por ou edita um responsável. Para obter mais informações, consulte "[Filtrar problemas e pull requests por responsáveis](/articles/filtering-issues-and-pull-requests-by-assignees)". | +| o ou enter | Abre um problema | ## Problemas e pull requests | Atalho | Descrição | diff --git a/translations/pt-BR/content/get-started/using-github/troubleshooting-connectivity-problems.md b/translations/pt-BR/content/get-started/using-github/troubleshooting-connectivity-problems.md index 2a57ff9fba..462da26208 100644 --- a/translations/pt-BR/content/get-started/using-github/troubleshooting-connectivity-problems.md +++ b/translations/pt-BR/content/get-started/using-github/troubleshooting-connectivity-problems.md @@ -30,7 +30,7 @@ Se você não conseguir verificar o captcha: ## Alternar métodos de clonagem -Alternar da clonagem via SSH para a clonagem via HTTPS (ou vice-versa) pode melhorar a conectividade. For more information, see "[Troubleshooting cloning errors](/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors)." +Alternar da clonagem via SSH para a clonagem via HTTPS (ou vice-versa) pode melhorar a conectividade. Para obter mais informações, consulte "[Solução de problemas de erros de clonagem](/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors)" Se você encontrar tempo limite com SSH, consulte "[Erro: número de arquivo inadequado](/articles/error-bad-file-number)". diff --git a/translations/pt-BR/content/github-cli/github-cli/about-github-cli.md b/translations/pt-BR/content/github-cli/github-cli/about-github-cli.md index 5f92b34a92..6d7bf8c743 100644 --- a/translations/pt-BR/content/github-cli/github-cli/about-github-cli.md +++ b/translations/pt-BR/content/github-cli/github-cli/about-github-cli.md @@ -1,5 +1,5 @@ --- -title: About GitHub CLI +title: Sobre o a CLI do GitHub intro: '{% data reusables.cli.cli-intro %}' versions: fpt: '*' diff --git a/translations/pt-BR/content/github-cli/github-cli/creating-github-cli-extensions.md b/translations/pt-BR/content/github-cli/github-cli/creating-github-cli-extensions.md index 5a295925fe..e0917a5255 100644 --- a/translations/pt-BR/content/github-cli/github-cli/creating-github-cli-extensions.md +++ b/translations/pt-BR/content/github-cli/github-cli/creating-github-cli-extensions.md @@ -1,6 +1,6 @@ --- -title: Creating GitHub CLI extensions -intro: 'Learn how to share new {% data variables.product.prodname_cli %} commands with other users by creating custom extensions for {% data variables.product.prodname_cli %}.' +title: Criando extensões da CLI do GitHub +intro: 'Aprenda a compartilhar novos comandos {% data variables.product.prodname_cli %} com outros usuários criando extensões personalizadas para {% data variables.product.prodname_cli %}.' versions: fpt: '*' ghes: '*' @@ -9,43 +9,43 @@ topics: - CLI --- -## About {% data variables.product.prodname_cli %} extensions +## Sobre extensões de {% data variables.product.prodname_cli %} -{% data reusables.cli.cli-extensions %} For more information about how to use {% data variables.product.prodname_cli %} extensions, see "[Using {% data variables.product.prodname_cli %} extensions](/github-cli/github-cli/using-github-cli-extensions)." +{% data reusables.cli.cli-extensions %} Para obter mais informações sobre como usar as extensões de {% data variables.product.prodname_cli %}, consulte "[Usando extensões de {% data variables.product.prodname_cli %}](/github-cli/github-cli/using-github-cli-extensions)". -You need a repository for each extension that you create. The repository name must start with `gh-`. The rest of the repository name is the name of the extension. At the root of the repository, there must be an executable file with the same name as the repository. This file will be executed when the extension is invoked. +É necessário um repositório para cada extensão que você criar. O nome do repositório deve iniciar com `gh-`. O restante do nome do repositório é o nome da extensão. Na raiz do repositório, deve haver um arquivo executável com o mesmo nome do repositório. Este arquivo será executado quando a extensão for chamada. {% note %} -**Note**: We recommend that the executable file is a bash script because bash is a widely available interpreter. You may use non-bash scripts, but the user must have the necessary interpreter installed in order to use the extension. +**Observação**: Recomendamos que o arquivo executável seja um script de bash, porque bash é um intérprete amplamente disponível. Você pode usar scripts que não são de bash, mas o usuário deverá ter o intérprete necessário instalado para usar a extensão. {% endnote %} -## Creating an extension with `gh extension create` +## Criando uma extensão com `gh extension create` -You can use the `gh extension create` command to create a project for your extension, including a bash script that contains some starter code. +Você pode usar o comando `gh extension create` para criar um projeto para sua extensão, incluindo um script de bash que contém um código inicial. -1. Set up a new extension by using the `gh extension create` subcommand. Replace `EXTENSION-NAME` with the name of your extension. +1. Configure uma nova extensão usando a o subcomando `gh extension create`. Substitua `EXTENSION-NAME` pelo nome da sua extensão. ```shell gh extension create EXTENSION-NAME ``` -1. Follow the printed instructions to finalize and optionally publish your extension. +1. Siga as instruções impressas para finalizar e, opcionalmente, publicar sua extensão. -## Creating an extension manually +## Criando uma extensão manualmente -1. Create a local directory called `gh-EXTENSION-NAME` for your extension. Replace `EXTENSION-NAME` with the name of your extension. For example, `gh-whoami`. +1. Crie um diretório local denominado `gh-EXTENSION-NAME` para a sua extensão. Substitua `EXTENSION-NAME` pelo nome da sua extensão. Por exemplo, `gh-whoami`. -1. In the directory that you created, add an executable file with the same name as the directory. +1. No diretório que você criou, adicione um arquivo executável com o mesmo nome do diretório. {% note %} - **Note:** Make sure that your file is executable. On Unix, you can execute `chmod +x file_name` in the command line to make `file_name` executable. On Windows, you can run `git init -b main`, `git add file_name`, then `git update-index --chmod=+x file_name`. + **Observação:** Certifique-se de que seu arquivo seja executável. No Unix, você pode executar `chmod +x file_name` na linha de comando para tornar `file_name` executável. No Windows, você pode executar `git init -b main`, `git add file_name` e, em seguida, `git update-index --chmod=+x file_name`. {% endnote %} -1. Write your script in the executable file. Por exemplo: +1. Escreva seu script no arquivo executável. Por exemplo: ```bash #!/usr/bin/env bash @@ -53,19 +53,19 @@ You can use the `gh extension create` command to create a project for your exten exec gh api user --jq '"You are @\(.login) (\(.name))."' ``` -1. From your directory, install the extension as a local extension. +1. No seu diretório, instale a extensão como uma extensão local. ```bash gh extension install . ``` -1. Verify that your extension works. Replace `EXTENSION-NAME` with the name of your extension. For example, `whoami`. +1. Verifique se sua extensão funciona. Substitua `EXTENSION-NAME` pelo nome da sua extensão. Por exemplo, `whoami`. ```shell gh EXTENSION-NAME ``` -1. From your directory, create a repository to publish your extension. Replace `EXTENSION-NAME` with the name of your extension. +1. No seu diretório, crie um repositório para publicar a sua extensão. Substitua `EXTENSION-NAME` pelo nome da sua extensão. ```shell git init -b main @@ -73,15 +73,23 @@ You can use the `gh extension create` command to create a project for your exten git add . && git commit -m "initial commit" && git push --set-upstream origin main ``` -1. Optionally, to help other users discover your extension, add the repository topic `gh-extension`. This will make the extension appear on the [`gh-extension` topic page](https://github.com/topics/gh-extension). For more information about how to add a repository topic, see "[Classifying your repository with topics](/github/administering-a-repository/managing-repository-settings/classifying-your-repository-with-topics)." +1. Opcionalmente, para ajudar outros usuários a descobrir sua extensão, adicione o tópico do repositório `gh-extension`. Isso fará com que a extensão apareça na página do tópico de -## Tips for writing {% data variables.product.prodname_cli %} extensions +`gh-extension`. Para obter mais informações sobre como adicionar um tópico do repositório, consulte "[Classificando seu repositório com tópicos](/github/administering-a-repository/managing-repository-settings/classifying-your-repository-with-topics)".

    + + -### Handling arguments and flags +## Dicas para escrever extensões de {% data variables.product.prodname_cli %} + + + +### Manipulando argumentos e sinalizadores + +Todos os argumentos de linha de comando após um `gh my-extension-name` serão passados para o script da extensão. Em um script de bash, você pode fazer referência a argumentos com `$1`, `$2`, etc. Você pode usar argumentos para inserir o usuário ou modificar o comportamento do script. + +Por exemplo, este script manipula vários sinalizadores. Quando o script é chamado com o sinalizador `-h` ou `--help` flag, o script imprime texto ao invés de continuar a execução. Quando o script é chamado com o o sinalizador `--name`, o script define o próximo valor após o sinalizador para `name_arg`. Quando o script é chamado com o sinalizador `--verbose`, o script imprime uma saudação diferente. -All command line arguments following a `gh my-extension-name` command will be passed to the extension script. In a bash script, you can reference arguments with `$1`, `$2`, etc. You can use arguments to take user input or to modify the behavior of the script. -For example, this script handles multiple flags. When the script is called with the `-h` or `--help` flag, the script prints help text instead of continuing execution. When the script is called with the `--name` flag, the script sets the next value after the flag to `name_arg`. When the script is called with the `--verbose` flag, the script prints a different greeting. ```bash #!/usr/bin/env bash @@ -117,36 +125,55 @@ else fi ``` -### Calling core commands in non-interactive mode -Some {% data variables.product.prodname_cli %} core commands will prompt the user for input. When scripting with those commands, a prompt is often undesirable. To avoid prompting, supply the necessary information explicitly via arguments. -For example, to create an issue programmatically, specify the title and body: + +### Chamar comandos do núcleo em modo não interativo + +Alguns comandos principais de {% data variables.product.prodname_cli %} principais pedirão entrada ao usuário. Ao escrever com esses comandos, a instrução é frequentemente indesejável. Para evitar a instrução, forneça a informação necessária explicitamente por meio de argumentos. + +Por exemplo, para criar um problema de modo programático, especifique o título e o texto: + + ```bash gh issue create --title "My Title" --body "Issue description" ``` -### Fetching data programatically -Many core commands support the `--json` flag for fetching data programatically. For example, to return a JSON object listing the number, title, and mergeability status of pull requests: + + +### Buscando dados programaticamente + +Muitos comandos principais são compatíveis o sinalizador `--json` para obter dados programaticamente. Por exemplo, para retornar um objeto JSON listando o número, título e status de mesclabilidade dos pull requests: + + ```bash gh pr list --json number,title,mergeStateStatus ``` -If there is not a core command to fetch specific data from GitHub, you can use the [`gh api`](https://cli.github.com/manual/gh_api) command to access the GitHub API. For example, to fetch information about the current user: + +Se não houver um comando do núcleo para buscar dados específicos do GitHub, você poderá usar o comando [`gh api`](https://cli.github.com/manual/gh_api) para acessar a API do GitHub. Por exemplo, para obter informações sobre o usuário atual: + + ```bash gh api user ``` -All commands that output JSON data also have options to filter that data into something more immediately usable by scripts. For example, to get the current user's name: + +Todos os comandos que os dados JSON de saída também têm opções para filtrar esses dados em algo mais imediatamente utilizável por scripts. Por exemplo, para obter o nome do usuário atual: + + ```bash gh api user --jq '.name' ``` -For more information, see [`gh help formatting`](https://cli.github.com/manual/gh_help_formatting). + +Para obter mais informações, consulte [`gh help formatting`](https://cli.github.com/manual/gh_help_formatting). + + ## Próximas etapas -To see more examples of {% data variables.product.prodname_cli %} extensions, look at [repositories with the `gh-extension` topic](https://github.com/topics/gh-extension). +Para ver mais exemplos de extensões {% data variables.product.prodname_cli %}, consulte [repositórios com o tópico de extensão `gh-extension`](https://github.com/topics/gh-extension). diff --git a/translations/pt-BR/content/github-cli/github-cli/github-cli-reference.md b/translations/pt-BR/content/github-cli/github-cli/github-cli-reference.md index c6672ce628..2de8ea777f 100644 --- a/translations/pt-BR/content/github-cli/github-cli/github-cli-reference.md +++ b/translations/pt-BR/content/github-cli/github-cli/github-cli-reference.md @@ -1,6 +1,6 @@ --- -title: GitHub CLI reference -intro: 'You can view all of the {% data variables.product.prodname_cli %} commands in your terminal or in the {% data variables.product.prodname_cli %} manual.' +title: Referência da CLI do GitHub +intro: 'Você pode visualizar todos os comandos de {% data variables.product.prodname_cli %} no seu terminal ou no manual de {% data variables.product.prodname_cli %}.' versions: fpt: '*' ghes: '*' @@ -10,19 +10,19 @@ topics: type: reference --- -To view all {% data variables.product.prodname_cli %} commands, see the [{% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_help_reference) or use the `reference` command. +Para ver todos os comandos de {% data variables.product.prodname_cli %}, consulte o manual [{% data variables.product.prodname_cli %}](https://cli.github.com/manual/gh_help_reference) ou use o comando `referência`. ```shell gh reference ``` -To view the environment variables that can be used with {% data variables.product.prodname_cli %}, see the [{% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_help_environment) or use the `environment` command. +Para ver as variáveis de ambiente que podem ser usadas com {% data variables.product.prodname_cli %}, consulte o [manual de {% data variables.product.prodname_cli %}](https://cli.github.com/manual/gh_help_environment) ou use o comando `ambiente`. ```shell gh environment ``` -To view the configuration settings that can be used with {% data variables.product.prodname_cli %}, see the [{% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_config) or use the `config` command. +Para ver as configurações que podem ser usadas com {% data variables.product.prodname_cli %}, consulte o [manual de {% data variables.product.prodname_cli %}](https://cli.github.com/manual/gh_config) ou use o comando `config`. ```shell gh config diff --git a/translations/pt-BR/content/github-cli/github-cli/quickstart.md b/translations/pt-BR/content/github-cli/github-cli/quickstart.md index b1c45920a0..e35a343567 100644 --- a/translations/pt-BR/content/github-cli/github-cli/quickstart.md +++ b/translations/pt-BR/content/github-cli/github-cli/quickstart.md @@ -1,6 +1,6 @@ --- -title: GitHub CLI quickstart -intro: 'Start using {% data variables.product.prodname_cli %} to work with {% data variables.product.company_short %} in the command line.' +title: Início rápido da CLI do GitHub +intro: 'Comece a usar {% data variables.product.prodname_cli %} para trabalhar com {% data variables.product.company_short %} na linha de comando.' versions: fpt: '*' ghes: '*' @@ -18,29 +18,29 @@ shortTitle: QuickStart ## Introdução -1. [Install](https://github.com/cli/cli#installation) {% data variables.product.prodname_cli %} on macOS, Windows, or Linux. -1. In the command line, authenticate to {% data variables.product.company_short %}. +1. [Instale](https://github.com/cli/cli#installation) {% data variables.product.prodname_cli %} no macOS, Windows ou Linux. +1. Na linha de comando, efetue a aitenticação em {% data variables.product.company_short %}. ```shell gh auth login ``` {% ifversion not fpt %} - To authenticate to {% data variables.product.product_location %}, use the `--hostname` flag. + Para efetuar a autenticação em {% data variables.product.product_location %}, use o sinalizador `--hostname`. ```shell gh auth login --hostname hostname ``` {% endif %} -1. Start working with {% data variables.product.company_short %} in the command line. For example, find an issue to work on with `gh issue status` or `gh issue list --assignee @me`. Create a pull request with `gh pr create`. Review a pull request with `gh pr checkout`, `gh pr diff` and `gh pr review`. +1. Comece a trabalhar com {% data variables.product.company_short %} na linha de comando. Por exemplo, encontre um problema para trabalhar com `gh issue status` ou `gh issue list --assignee @me`. Crie um pull request com `gh pr create`. Revise um pull request com `gh pr checkout`, `gh pr diff` e `gh gh pr review`. ## Próximas etapas -- Tell {% data variables.product.prodname_cli %} which text editor to use for commands that open a text editor. For example, enter `gh config set editor "code -w"` to set your preferred text editor to {% data variables.product.prodname_vscode %}. For more information, see [`gh config set`](https://cli.github.com/manual/gh_config_set). +- Diga a {% data variables.product.prodname_cli %} qual editor de texto usar para comandos que abram um editor de texto. Por exemplo, digite `gh config editor "code -w"` para definir seu editor de texto preferido para {% data variables.product.prodname_vscode %}. Para obter mais informações, consulte [`gh config set`](https://cli.github.com/manual/gh_config_set). -- Define aliases for commands that you commonly run. For example, if you run `gh alias set prd "pr create --draft"`, you will then be able to run `gh prd` to quickly open a draft pull request. For more information, see [`gh alias`](https://cli.github.com/manual/gh_alias). +- Defina aliases para comandos que você executa com frequência. Por exemplo, se você executar `gh alias set prd "pr create --draft"`, você poderá executar o `gh prd` para abrir rapidamente um pull request. Para obter mais informações, consulte [`gh alias`](https://cli.github.com/manual/gh_alias). -- Create or add custom commands with {% data variables.product.prodname_cli %} extensions. For more information, see "[Using {% data variables.product.prodname_cli %} extensions](/github-cli/github-cli/using-github-cli-extensions)" and "[Creating {% data variables.product.prodname_cli %} extensions](/github-cli/github-cli/creating-github-cli-extensions)." +- Crie ou adicione comandos personalizados com extensões de {% data variables.product.prodname_cli %}. Para obter mais informações, consulte "[Usando extensões de {% data variables.product.prodname_cli %}](/github-cli/github-cli/using-github-cli-extensions)" e "[Criando extensões de {% data variables.product.prodname_cli %}](/github-cli/github-cli/creating-github-cli-extensions)". -- For more information about all of the commands that you can run with {% data variables.product.prodname_cli %}, see "[{% data variables.product.prodname_cli %} reference](/github-cli/github-cli/github-cli-reference)." +- Para obter mais informações sobre todos os comandos que você pode executar com {% data variables.product.prodname_cli %}, consulte "[Referência de {% data variables.product.prodname_cli %}](/github-cli/github-cli/github-cli-reference)". diff --git a/translations/pt-BR/content/github-cli/github-cli/using-github-cli-extensions.md b/translations/pt-BR/content/github-cli/github-cli/using-github-cli-extensions.md index 27a2bc54fc..1d30f41ed8 100644 --- a/translations/pt-BR/content/github-cli/github-cli/using-github-cli-extensions.md +++ b/translations/pt-BR/content/github-cli/github-cli/using-github-cli-extensions.md @@ -1,6 +1,6 @@ --- -title: Using GitHub CLI extensions -intro: 'Learn how to use custom extensions written by other {% data variables.product.prodname_cli %} users.' +title: Usando as extensões de CLI do GitHub +intro: 'Aprenda a usar extensões personalizadas escritas por outros usuários de {% data variables.product.prodname_cli %}.' versions: fpt: '*' ghes: '*' @@ -9,61 +9,61 @@ topics: - CLI --- -## About {% data variables.product.prodname_cli %} extensions +## Sobre extensões de {% data variables.product.prodname_cli %} {% note %} -**Note:** Extensions outside of {% data variables.product.product_name %} and {% data variables.product.prodname_cli %} are not certified by {% data variables.product.product_name %} and are governed by separate terms of service, privacy policy, and support documentation. To mitigate risk when using third-party extensions, audit the source code of the extension before installing or updating the extension. +**Observação:** As extensões fora de {% data variables.product.product_name %} e {% data variables.product.prodname_cli %} não são certificadas por {% data variables.product.product_name %} e são regidas por termos de serviço separados, política de privacidade e documentação de suporte. Para mitigar o risco ao usar extensões de terceiros, faça a auditoria do código-fonte da extensão antes de instalá-la ou atualizá-la. {% endnote %} -{% data reusables.cli.cli-extensions %} For more information about how to create {% data variables.product.prodname_cli %} extensions, see "[Creating {% data variables.product.prodname_cli %} extensions](/github-cli/github-cli/creating-github-cli-extensions)." +{% data reusables.cli.cli-extensions %} Para obter mais informações sobre como criar extensões de {% data variables.product.prodname_cli %}, consulte "[Criando extensões de {% data variables.product.prodname_cli %}](/github-cli/github-cli/creating-github-cli-extensions)". -Extensions are locally installed and are scoped to the user. Therefore, if you access {% data variables.product.prodname_cli %} from a different machine or another user accesses {% data variables.product.prodname_cli %} from the same machine, the extension will not be available. +As extensões são instaladas localmente e têm seu escopo definido para o usuário. Portanto, se você acessar {% data variables.product.prodname_cli %} de uma máquina diferente ou outro usuário acessar {% data variables.product.prodname_cli %} da mesma máquina, a extensão não estará disponível. -## Finding extensions +## Localizando extensões -You can find extensions by browsing [repositories with the `gh-extension` topic](https://github.com/topics/gh-extension). +Você pode encontrar extensões acessando [repositórios com o tópico](https://github.com/topics/gh-extension) de `gh-extension`. -## Installing extensions +## Instalando as extensões -To install an extension, use the `extensions install` subcommand. Replace the `repo` parameter with the repository of the extension. You can use the full URL, such as `https://github.com/octocat/gh-whoami`, or just the owner and repository, such as `octocat/gh-whoami`. +Para instalar uma extensão, use o subcomando `extensions install`. Substitua o parâmetro `repo` pelo repositório da extensão. Você pode usar a URL completa, como `https://github.com/octocat/gh-whoami` ou apenas o proprietário e o repositório, como `octocat/gh-whoami`. -If the owner and repository are used, `gh` will install the extension using the hostname to which `gh` is currently authenticated. The full URL format is useful when installing extensions from a different host. For example, users on {% data variables.product.prodname_ghe_server %} should use the full repository URL to install extensions from {% data variables.product.prodname_dotcom_the_website %} or any other host. +Se o proprietário e repositório forem usados, `gh` irá instalar a extensão usando o nome de host com o qual `gh` está atualmente autenticado. O formato completo da URL é útil ao instalar extensões de um host diferente. Por exemplo, os usuários em {% data variables.product.prodname_ghe_server %} devem usar a URL completa do repositório para instalar extensões de {% data variables.product.prodname_dotcom_the_website %} ou de qualquer outro host. -To install an extension in development from the current directory, use `.` as the value for the `repo` parameter. +Para instalar uma extensão em desenvolvimento a partir do diretório atual, use `.` como o valor para o parâmetro `repo`. ```shell gh extension install repo ``` -If you already have an extension by the same name installed, the command will fail. For example, if you have installed `octocat/gh-whoami`, you must uninstall it before installing `hubot/gh-whoami`. +Se você já tem uma extensão com o mesmo nome instalado, o comando irá falhar. Por exemplo, se você instalou `octocat/gh-whoami`, você deverá desinstalá-lo antes de instalar `hubot/gh-whoami`. -## Viewing installed extensions +## Visualizando extensões instaladas -To view all installed extensions, use the `extensions list` subcommand. The output will also tell you which extensions have updates available. +Para ver todas as extensões instaladas, use o subcomando `lista de extensões`. A saída também informará quais extensões possuem atualizações disponíveis. ```shell gh extension list ``` -## Updating extensions +## Atualizando extensões -To update an extension, use the `extensions upgrade` subcommand. Replace the `extension` parameter with the name of the extension. +Para atualizar uma extensão, use o subcomando `extensions upgrade`. Substitua o parâmetro `extensão` pelo nome da extensão. ```shell gh extension upgrade extension ``` -To update all installed extensions, use the `--all` flag. +Para atualizar todas as extensões instaladas, use o sinalizador `--all`. ```shell gh extension upgrade --all ``` -## Uninstalling extensions +## Desinstalando extensões -To uninstall an extension, use the `extensions remove` subcommand. Replace the `extension` parameter with the name of the extension. +Para desinstalar uma extensão, use o subcomando `extensions remove`. Substitua o parâmetro `extensão` pelo nome da extensão. ```shell gh extension remove extension diff --git a/translations/pt-BR/content/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md b/translations/pt-BR/content/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md index 332e77105e..8abaf660af 100644 --- a/translations/pt-BR/content/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md +++ b/translations/pt-BR/content/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md @@ -31,7 +31,7 @@ Há dois tipos de verificação de status no {% data variables.product.product_n - Verificações - Status -_Checks_ are different from _statuses_ in that they provide line annotations, more detailed messaging, and are only available for use with {% data variables.product.prodname_github_apps %}. +As _Verificações_ são diferentes dos _status_ na medida que fornecem anotações de linha, mensagens mais detalhadas e só estão disponíveis para uso com {% data variables.product.prodname_github_apps %}. Os proprietários da organização e usuários com acesso push a um repositório podem criar verificações e status com a API do {% data variables.product.product_name %}. Para obter mais informações, consulte "[Verificações](/rest/reference/checks)" e "[Status](/rest/reference/repos#statuses)". @@ -41,6 +41,12 @@ Quando _verificações_ são configuradas em um repositório, as pull requests a ![Verificações de status em uma pull request](/assets/images/help/pull_requests/checks.png) +{% note %} + +**Observação:** A aba **Verificações** só é preenchida para pull requests se você configurar _verificações_, não _status_, para o repositório. + +{% endnote %} + Quando uma linha específica em um commit causar a falha de uma verificação, você verá detalhes sobre a falha, o aviso ou a advertência ao lado do código relevante na guia **Files** (Arquivos) da pull request. ![Detalhes de uma verificação de status](/assets/images/help/pull_requests/checks-detailed.png) diff --git a/translations/pt-BR/content/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md b/translations/pt-BR/content/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md index 340b3881c5..127e70609b 100644 --- a/translations/pt-BR/content/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md +++ b/translations/pt-BR/content/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md @@ -77,15 +77,15 @@ Se decidir que não quer que as alterações em um branch de tópico sofram merg {% data reusables.cli.cli-learn-more %} -To merge a pull request, use the `gh pr merge` subcommand. Replace `pull-request` with the number, URL, or head branch of the pull request. +Para fazer merge de um pull request, use o subcomando `gh pr merge`. Substitua `pull request` pelo número, URL ou branch principal do pull request. ```shell gh pr merge pull-request ``` -Follow the interactive prompts to complete the merge. For more information about the merge methods that you can choose, see "[About pull request merges](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)." +Siga as instruções interativas para realizar o merge. Para obter mais informações sobre os métodos de merge que você pode escolher, consulte "[Sobre merges do pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)". -Alternatively, you can use flags to skip the interactive prompts. For example, this command will squash the commits into a single commit with the commit message "my squash commit", merge the squashed commit into the base branch, and then delete the local and remote branch. +Como alternativa, você pode usar sinalizadores para ignorar as instruções interativas. Por exemplo, esse comando irá fazer a combinação por squash dos commits em um único commit com a mensagem de "my squash commit", faça o merge do commit combinado por squash no branch de base e exclua o branch local e o remoto. ```shell gh pr merge 523 --squash --body "my squash commit" --delete-branch diff --git a/translations/pt-BR/content/github/collaborating-with-pull-requests/index.md b/translations/pt-BR/content/github/collaborating-with-pull-requests/index.md index 4c43774acf..e06d2a7f2b 100644 --- a/translations/pt-BR/content/github/collaborating-with-pull-requests/index.md +++ b/translations/pt-BR/content/github/collaborating-with-pull-requests/index.md @@ -22,6 +22,6 @@ children: - /addressing-merge-conflicts - /reviewing-changes-in-pull-requests - /incorporating-changes-from-a-pull-request -shortTitle: Collaborate with pull requests +shortTitle: Colaborar com pull requests --- diff --git a/translations/pt-BR/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md b/translations/pt-BR/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md index 10bb7f9753..9f840bfc74 100644 --- a/translations/pt-BR/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md +++ b/translations/pt-BR/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md @@ -24,7 +24,7 @@ topics: {% endnote %} -You can create pull requests on {% data variables.product.prodname_dotcom_the_website %}, with {% data variables.product.prodname_desktop %}, in {% data variables.product.prodname_codespaces %}, on {% data variables.product.prodname_mobile %}, and when using GitHub CLI. +Você pode criar pull requests no {% data variables.product.prodname_dotcom_the_website %}, com {% data variables.product.prodname_desktop %}, em {% data variables.product.prodname_codespaces %}, em {% data variables.product.prodname_mobile %} e ao usar a CLI do GitHub. Após inicialização de uma pull request, você verá uma página de revisão que mostra uma visão geral de alto nível das alterações entre seu branch (o branch de comparação) e o branch base do repositório. É possível adicionar um resumo das alterações propostas, revisar as alterações feitas pelos commits, adicionar etiquetas, marcos e responsáveis, bem como fazer @menção a contribuidores individuais ou equipes. Para obter mais informações, consulte "[Criar uma pull request](/articles/creating-a-pull-request)". diff --git a/translations/pt-BR/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork.md b/translations/pt-BR/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork.md index 2a756490db..57af9d2414 100644 --- a/translations/pt-BR/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork.md +++ b/translations/pt-BR/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork.md @@ -5,7 +5,7 @@ redirect_from: - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork - /articles/creating-a-pull-request-from-a-fork - /github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork -permissions: Anyone with write access to a repository can create a pull request from a user-owned fork. +permissions: 'Anyone with write access to a repository can create a pull request from a user-owned fork. {% data reusables.enterprise-accounts.emu-permission-propose %}' versions: fpt: '*' ghes: '*' diff --git a/translations/pt-BR/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md b/translations/pt-BR/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md index bb3cdf6a47..dfaf046a79 100644 --- a/translations/pt-BR/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md +++ b/translations/pt-BR/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md @@ -1,6 +1,7 @@ --- title: Criar uma pull request intro: 'Crie um pull request para fazer sugestões e colaborar nas alterações de um repositório. Essas alterações são propostas em um *branch*, que garante que o branch-padrão só contém trabalho concluído e aprovado.' +permissions: 'Anyone with read access to a repository can create a pull request. {% data reusables.enterprise-accounts.emu-permission-propose %}' redirect_from: - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request - /articles/creating-a-pull-request @@ -13,7 +14,7 @@ topics: - Pull requests --- -Qualquer pessoa com permissões de leitura em um repositório pode criar uma pull request, mas você deve ter permissões de gravação para criar um branch. Se você quiser criar um branch para seu pull request e não tiver permissões de gravação no repositório, é possível bifurcar o repositório primeiro. Para obter mais informações, consulte "[Criar uma pull request de uma bifurcação](/articles/creating-a-pull-request-from-a-fork)" e "[Sobre bifurcações](/articles/about-forks)". +Caso deseje criar um novo branch para seu pull request e não tenha permissões de gravação no repositório, você pode bifurcar o repositório primeiro. Para obter mais informações, consulte "[Criar uma pull request de uma bifurcação](/articles/creating-a-pull-request-from-a-fork)" e "[Sobre bifurcações](/articles/about-forks)". É possível especificar em qual branch você deseja fazer merge de suas alterações quando cria sua pull request. As pull requests só podem ser abertas entre dois branches que são diferentes. @@ -150,11 +151,11 @@ gh pr create --web {% codespaces %} -1. Once you've committed changes to your local copy of the repository, click the **Create Pull Request** icon. ![Barra lateral de controle de origem com botão de staging destacado](/assets/images/help/codespaces/codespaces-commit-pr-button.png) +1. Depois de realizar alterações na sua cópia local do repositório, clique no ícone **Criar Pull Request**. ![Barra lateral de controle de origem com botão de staging destacado](/assets/images/help/codespaces/codespaces-commit-pr-button.png) 1. Verifique se o branch local e o repositório do qual você está fazendo merge, o branch remoto e o repositório no qual você está fazendo merge estão corretos. Em seguida, dê ao pull request um título e uma descrição. ![Barra lateral de controle de origem com botão de staging destacado](/assets/images/help/codespaces/codespaces-commit-pr.png) 1. Clique em **Criar**. -For more information on creating pull requests in {% data variables.product.prodname_codespaces %}, see "[Using Codespaces for pull requests](/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests)." +Para obter mais informações sobre a criação de pull requests em {% data variables.product.prodname_codespaces %}, consulte "[Usando codespaces para pull requests](/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests)" {% endcodespaces %} diff --git a/translations/pt-BR/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md b/translations/pt-BR/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md index 693cb81b1c..33f67db131 100644 --- a/translations/pt-BR/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md +++ b/translations/pt-BR/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md @@ -39,7 +39,7 @@ shortTitle: Fazer checkout de um PR localmente {% data reusables.cli.cli-learn-more %} -To check out a pull request locally, use the `gh pr checkout` subcommand. Replace `pull-request` with the number, URL, or head branch of the pull request. +Para fazer check-out de um pull request localmente, use o subcomando `gh pr check-out`. Substitua `pull request` pelo número, URL ou branch principal do pull request. ```shell gh pr checkout pull-request diff --git a/translations/pt-BR/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/translations/pt-BR/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md index 57e351bc22..8f0bc47ac8 100644 --- a/translations/pt-BR/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md +++ b/translations/pt-BR/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md @@ -1,10 +1,10 @@ --- title: Revendo alterações de dependência em um pull request intro: 'Se um pull request tiver alterações nas dependências, você poderá ver um resumo do que alterou e se há vulnerabilidades conhecidas em qualquer uma das dependências.' +product: '{% data reusables.gated-features.dependency-review %}' versions: fpt: '*' ghes: '>= 3.2' - product: '{% data reusables.gated-features.dependency-review %}' type: how_to topics: - Pull requests @@ -26,7 +26,7 @@ shortTitle: Revisar alterações de dependência {% data reusables.dependency-review.feature-overview %} -{% ifversion ghes > 3.1 %} Before you can use dependency review, you must enable the dependency graph and connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, consulte "[Habilitar alertas para dependências vulneráveis em {% data variables.product.prodname_ghe_server %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server){% endif %} +{% ifversion ghes > 3.1 %} Antes de você poder usar a revisão de dependências, você deverá habilitar o gráfico de dependências e conectar {% data variables.product.product_location %} a {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, consulte "[Habilitar alertas para dependências vulneráveis em {% data variables.product.prodname_ghe_server %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server){% endif %} 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)". @@ -38,19 +38,19 @@ Revisão de dependência permite a você "desloque para a esquerda". Você pode 1. Se o pull request contiver muitos arquivos, use o menu suspenso **Filtro de arquivo** para recolher todos os arquivos que não registram dependências. Isso fará com que seja mais fácil focar a sua revisão nas alterações de dependência. - ![Menu de filtro de arquivos](/assets/images/help/pull_requests/file-filter-menu-json.png) + ![Menu de filtro de arquivos](/assets/images/help/pull_requests/file-filter-menu-json.png) A revisão sobre dependências fornece uma visão mais clara do que mudou nos grandes arquivos de bloqueio, em que o diff de origem não é representado por padrão. + + {% note %} + + **Observação:** Revisões de Dependência de diffs avançados não estão disponíveis para arquivos estáticos do JavaScript que passaram por commit como, por exemplo, `jquery.js`. + + {% endnote %} 1. À direita do cabeçalho de um manifesto ou arquivo de bloqueio, exiba a revisão de dependências clicando no botão de diff avançado**{% octicon "file" aria-label="The rich diff icon" %}**. ![Botão de diff avançado](/assets/images/help/pull_requests/dependency-review-rich-diff.png) - {% note %} - - **Observação:** A revisão de dependências fornece uma visão mais clara do que foi alterado em arquivos de bloqueio grandes, em que o diff de origem não é renderizado por padrão. - - {% endnote %} - -1. Verifique as dependências listadas na revisão sobre dependências. +2. Verifique as dependências listadas na revisão sobre dependências. ![Alertas de vulnerabilidade em revisão de dependências](/assets/images/help/pull_requests/dependency-review-vulnerability.png) diff --git a/translations/pt-BR/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md b/translations/pt-BR/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md index 39533410ba..b9e7f3c725 100644 --- a/translations/pt-BR/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md +++ b/translations/pt-BR/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md @@ -43,11 +43,11 @@ Antes de enviar a revisão, os comentários em linha ficam com status _pendente_ {% codespaces %} -You can use [{% data variables.product.prodname_codespaces %}](/codespaces/overview) to test, run, and review pull requests. +Você pode usar [{% data variables.product.prodname_codespaces %}](/codespaces/overview) para testar, executar e revisar pull requests. {% data reusables.codespaces.review-pr %} -For more information on reviewing pull requests in {% data variables.product.prodname_codespaces %}, see "[Using Codespaces for pull requests](/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests)." +Para obter mais informações sobre a revisão de pull requests em {% data variables.product.prodname_codespaces %}, consulte "[Usando codespaces para pull requests](/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests)" {% endcodespaces %} {% endif %} diff --git a/translations/pt-BR/content/github/collaborating-with-pull-requests/working-with-forks/about-forks.md b/translations/pt-BR/content/github/collaborating-with-pull-requests/working-with-forks/about-forks.md index 870c10cae0..0e8713a7c4 100644 --- a/translations/pt-BR/content/github/collaborating-with-pull-requests/working-with-forks/about-forks.md +++ b/translations/pt-BR/content/github/collaborating-with-pull-requests/working-with-forks/about-forks.md @@ -20,6 +20,12 @@ Bifurcar um repositório é semelhante a copiar um repositório, com duas grande {% data reusables.repositories.you-can-fork %} +{% ifversion fpt %} + +Se você for um integrante de um {% data variables.product.prodname_emu_enterprise %}, existem outras restrições nos repositórios que você pode bifurcar. {% data reusables.enterprise-accounts.emu-forks %} Para obter mais informações, consulte "[Sobre o {% data variables.product.prodname_emus %}de](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." + +{% endif %} + {% data reusables.repositories.desktop-fork %} Excluir uma bifurcação não exclui o repositório upstream original. Você pode fazer quaisquer alterações que quiser em sua bifurcação — adicionar colaboradores, renomear arquivos, gerar {% data variables.product.prodname_pages %}— sem efeito no original.{% ifversion fpt %} Você não pode restaurar um repositório bifurcado excluído. Para obter mais informações, consulte "[Restaurar um repositório excluído](/articles/restoring-a-deleted-repository)".{% endif %} diff --git a/translations/pt-BR/content/github/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md b/translations/pt-BR/content/github/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md index d64b41abc1..84acba3baa 100644 --- a/translations/pt-BR/content/github/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md +++ b/translations/pt-BR/content/github/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md @@ -52,4 +52,4 @@ Caso a configuração local do Git contenha um endereço de e-mail genérico ou ## Leia mais -* "[Pesquisar commits](/articles/searching-commits)" +* "[Pesquisar commits](/search-github/searching-on-github/searching-commits)" diff --git a/translations/pt-BR/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views.md b/translations/pt-BR/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views.md index 06dddd0cfc..2a8931508f 100644 --- a/translations/pt-BR/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views.md +++ b/translations/pt-BR/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views.md @@ -29,4 +29,4 @@ Para obter mais informações sobre como o Git considera o histórico de commits ## Leia mais - "[Assinar commits](/articles/signing-commits)" -- "[Pesquisar commits](/articles/searching-commits)" +- "[Pesquisar commits](/search-github/searching-on-github/searching-commits)" 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 f8b0759ab4..545a88d6ea 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 @@ -1,6 +1,6 @@ --- title: Sobre a telemetria do GitHub Copilot -intro: 'O Copilot do {% data variables.product.prodname_dotcom %} coleta e depende de dados adicionais de telemetria além do que os outros produtos e serviços de {% data variables.product.prodname_dotcom %} coletam.' +intro: '{% data variables.product.prodname_copilot %} coleta e depende de dados adicionais de telemetria além do que outros produtos e serviços de {% data variables.product.company_short %} coletam.' redirect_from: - /early-access/github/copilot/about-github-copilot-telemetry versions: @@ -8,36 +8,21 @@ versions: --- ## Quais dados são coletados -O Copilot de {% data variables.product.prodname_dotcom %} coleta atividade do editor Visual Studio do usuário, vinculada a um registro de horário e metadados. Estes metadados consistem nas configurações da extensão e nos metadados padrão coletados pelo [pacote de telemetria da extensão Visual Studio Code](https://www.npmjs.com/package/vscode-extension-telemetry): -* ID da máquina do Visual Studio Code (identificador pseudonimizado) -* ID de sessão do Visual Studio Code (identificador pseudodonimizado) -* Versão do Visual Studio Code -* [Geolocalização do endereço IP](https://docs.microsoft.com/en-us/azure/azure-monitor/app/ip-collection?tabs=net) (país, estado/província e cidade, mas não o endereço IP propriamente dito) -* Versão e sistema operacional -* Versão da extensão -* A interface do usuário do VS Code (web ou desktop) +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. -A atividade coletada consiste em eventos acionados quando: +## Como os dados são usados pelo {% data variables.product.company_short %} -* Ocorre um erro (ele registra o tipo de erro e o plano de fundo relevante; por exemplo, se for um erro de autenticação, a data de vencimento da chave é gravada) -* Nossos modelos são acessados para pedir sugestões de código (ele registra o estado do editor como a posição do cursor e trechos de código) — isso inclui casos quando o usuário executa uma ação para solicitar sugestões de código -* Sugestões de código são recebidas ou exibidas (registra as sugestões, processamento posterior e metadados como certeza do modelo e latência) -* Sugestões de código são ancoradas devido a filtros que garantem segurança da IA -* O usuário age em sugestões de código (por exemplo, para aceitá-las ou rejeitá-las) -* O usuário agiu em sugestões de código e, em seguida, grava se ou como persistem no código +{% data variables.product.company_short %} usará estes dados para: -## Como os dados são usados -Estes dados serão usados somente por {% data variables.product.company_short %} para: - -* Melhorar diretamente o produto, incluindo a avaliação de diferentes estratégias no processamento e previsão de quais sugestões os usuários podem achar úteis -* Avaliação direta do produto, por exemplo, medindo o impacto positivo que ele tem no usuário -* Melhorar os modelos de geração de código subjacentes, por exemplo, fornecendo exemplos positivos e negativos (mas sempre para que o seu código privado não seja usado como entrada para sugerir código para outros usuários do Copilot de {% data variables.product.prodname_dotcom %}) -* Guiando produtos de {% data variables.product.prodname_dotcom %} intimamente relacionados -* Investigando e detectando possíveis abusos do serviço do Copilot de {% data variables.product.prodname_dotcom %} -* Outros propósitos relacionados com a melhoria do serviço do Copilot de {% data variables.product.prodname_dotcom %} +- Melhorar diretamente o produto, incluindo a avaliação de diferentes estratégias no processamento e previsão de quais sugestões os usuários podem achar úteis +- Avaliar o produto, por exemplo, medindo o impacto positivo que ele tem no usuário +- Melhorando os modelos de geração de código subjacentes, por exemplo, fornecendo exemplos positivos e negativos (mas sempre para que o seu código privado não seja usado como entrada para sugerir código para outros usuários de {% data variables.product.prodname_copilot %}) +- Guiando produtos de {% data variables.product.company_short %} intimamente relacionados +- Investigando e detectando possíveis abusos do serviço de {% data variables.product.prodname_copilot %} +- Outros propósitos relacionados à melhoria do serviço de {% data variables.product.prodname_copilot %}, incluindo o compartilhamento conforme descrito na próxima seção ## Como os dados são compartilhados -Os dados de telemetria são armazenados com segurança em sistemas de {% data variables.product.prodname_dotcom %}, com implementação da criptografia apropriada. -Sabemos que o usuário edita ações e os trechos de código fonte são dados muito sensíveis e o acesso é estritamente controlado. Os dados só podem ser acessados (1) por funcionários de {% data variables.product.company_short %} (funcionários e contratados) designada que trabalha na equipe do Copilot de {% data variables.product.company_short %} ou na equipe de saúde da plataforma {% data variables.product.company_short %}, (2) funcionários selecionados da Microsoft (funcionários e contratados) em ou com a equipe do Copilot de {% data variables.product.company_short %} e (3) funcionários da OpenAI selecionados que trabalham no Copilot de {% data variables.product.company_short %}. +Os dados de telemetria são armazenados com segurança em sistemas de {% data variables.product.company_short %}, com implementação da criptografia apropriada. Nós sabemos que o usuário edita ações, trechos de código-fonte e URLs de repositórios e caminhos de arquivos são dados confidenciais. Consequentemente, o acesso é rigorosamente controlado. Os dados só podem ser acessados por (1) equipe (funcionários e contratados indicados) de {% data variables.product.company_short %} que trabalham na equipe de {% data variables.product.prodname_copilot %} ou na equipe de saúde da plataforma {% data variables.product.company_short %}, (2) equipe da Microsoft (funcionários e contratados) que trabalham em ou com o Azure e/ou equipes de {% data variables.product.prodname_copilot %} e (3) funcionários da OpenAI que trabalham em {% data variables.product.prodname_copilot %}. + diff --git a/translations/pt-BR/content/github/copilot/github-copilot-telemetry-terms.md b/translations/pt-BR/content/github/copilot/github-copilot-telemetry-terms.md new file mode 100644 index 0000000000..b55d75272f --- /dev/null +++ b/translations/pt-BR/content/github/copilot/github-copilot-telemetry-terms.md @@ -0,0 +1,16 @@ +--- +title: Termos da Telemetria do Copilot do GitHub +intro: 'A aceitação da telemetria adicional descrita abaixo é uma condição para ingressar na lista de espera para a pré-visualização técnica do Copilot de {% data variables.product.prodname_copilot %} e usar {% data variables.product.prodname_copilot %} na pré-visualização técnica.' +redirect_from: + - /early-access/github/copilot/telemetry-terms + - /github/copilot/telemetry-terms +versions: + fpt: '*' +--- + +## Telemetria adicional + +Se você usar {% data variables.product.prodname_copilot %}, a extensão/plugin de {% data variables.product.prodname_copilot %} irá coletar informações de uso sobre eventos gerados pela interação com o ambiente integrado de desenvolvimento (IDE). Esses eventos incluem desempenho de {% data variables.product.prodname_copilot %}, funcionalidades usadas e sugestões aceitas, modificadas e aceitas, ou rejeitadas. Estas informações podem incluir dados pessoais, que incluem as suas Informações Pessoais do Usuário, conforme definido na [Declaração de Privacidade do GitHub](/github/site-policy/github-privacy-statement). + +Esta informação de uso é usada pelo {% data variables.product.company_short %} e compartilhada com a Microsoft e o OpenAI, para desenvolver e melhorar a extensão/plugin e produtos relacionados. O OpenAI também usa estas informações de uso para prestar outros serviços relacionados a {% data variables.product.prodname_copilot %}. Por exemplo, ao editar arquivos com a extensão/plugin de {% data variables.product.prodname_copilot %} habilitado, o conteúdo do arquivo snippets, sugestões, e todas as modificações nas sugestões serão compartilhadas com {% data variables.product.company_short %}, Microsoft e OpenAI, e usado para fins de diagnóstico para melhorar as sugestões e produtos relacionados. {% data variables.product.prodname_copilot %} depende do conteúdo do arquivo para o contexto, no arquivo que você está editando e potencialmente em outros arquivos abertos na mesma instância do IDE. Quando você estiver usando {% data variables.product.prodname_copilot %}, você também poderá coletar as URLs dos repositórios ou caminhos de arquivo para os arquivos relevantes. {% data variables.product.prodname_copilot %} não usa essas URLs, caminhos de arquivo ou trechos coletados na sua telemetria como entrada para sugerir código para outros usuários de {% data variables.product.prodname_copilot %}. Essas informações são tratadas como uma informações confidenciais e acessadas conforme necessário. Você está proibido de coletar dados de telemetria sobre outros usuários de {% data variables.product.prodname_copilot %} da extensão/plugin de {% data variables.product.prodname_copilot %} Para mais informações sobre a telemetria de {% data variables.product.prodname_copilot %}, consulte "[Sobre a telemetria de {% data variables.product.prodname_copilot %}](/github/copilot/about-github-copilot-telemetry)". Você pode revogar seu consentimento às operações de telemetria e processamento de dados pessoais descritas neste parágrafo entrando em contato com o GitHub e solicitando a remoção da pré-visualização técnica. + diff --git a/translations/pt-BR/content/github/copilot/index.md b/translations/pt-BR/content/github/copilot/index.md index 6c373875c6..fd303859f6 100644 --- a/translations/pt-BR/content/github/copilot/index.md +++ b/translations/pt-BR/content/github/copilot/index.md @@ -5,7 +5,7 @@ versions: fpt: '*' children: - /about-github-copilot-telemetry - - /telemetry-terms + - /github-copilot-telemetry-terms - /research-recitation --- diff --git a/translations/pt-BR/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md b/translations/pt-BR/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md index 0481ba8b79..980e28fd4b 100644 --- a/translations/pt-BR/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md +++ b/translations/pt-BR/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md @@ -8,7 +8,7 @@ versions: fpt: '*' --- -You can discover, browse, and install free and paid tools, including {% data variables.product.prodname_github_apps %}, {% data variables.product.prodname_oauth_apps %}, and {% data variables.product.prodname_actions %}, in [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace). +Você pode descobrir, navegar e instalar ferramentas grátis e pagas, incluindo {% data variables.product.prodname_github_apps %}, {% data variables.product.prodname_oauth_apps %} e {% data variables.product.prodname_actions %}, em [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace). Ao comprar uma ferramenta paga, você pagará pela assinatura da sua ferramenta com as mesmas informações de cobrança usadas para pagar sua assinatura do {% data variables.product.product_name %} e receberá uma fatura na data regular da cobrança. Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)". @@ -16,7 +16,7 @@ Em algumas ferramentas, você tem a opção de selecionar uma avaliação gratui ## Encontrar ferramentas em {% data variables.product.prodname_marketplace %} -Você pode descobrir, navegar e instalar aplicativos e ações criados por outros em {% data variables.product.prodname_marketplace %}. Consulte "[Pesquisar {% data variables.product.prodname_marketplace %}](/github/searching-for-information-on-github/searching-github-marketplace)". +Você pode descobrir, navegar e instalar aplicativos e ações criados por outros em {% data variables.product.prodname_marketplace %}. Consulte "[Pesquisar {% data variables.product.prodname_marketplace %}](/search-github/searching-on-github/searching-github-marketplace)". {% data reusables.actions.actions-not-verified %} diff --git a/translations/pt-BR/content/github/customizing-your-github-workflow/exploring-integrations/about-integrations.md b/translations/pt-BR/content/github/customizing-your-github-workflow/exploring-integrations/about-integrations.md index 9aedf868d2..c957be43ae 100644 --- a/translations/pt-BR/content/github/customizing-your-github-workflow/exploring-integrations/about-integrations.md +++ b/translations/pt-BR/content/github/customizing-your-github-workflow/exploring-integrations/about-integrations.md @@ -8,16 +8,16 @@ versions: fpt: '*' --- -Você pode instalar integrações em sua conta pessoal ou em organizações que possui. You can also install {% data variables.product.prodname_github_apps %} from a third-party in a specific repository where you have admin permissions or which is owned by your organization. +Você pode instalar integrações em sua conta pessoal ou em organizações que possui. Você também pode instalar {% data variables.product.prodname_github_apps %} a partir de um repositório específico em um repositório específico em que você tem permissões de administrador ou que pertencem à sua organização. -## Differences between {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %} +## Diferenças entre {% data variables.product.prodname_github_apps %} e {% data variables.product.prodname_oauth_apps %} -Integrations can be {% data variables.product.prodname_github_apps %}, {% data variables.product.prodname_oauth_apps %}, or anything that utilizes {% data variables.product.product_name %} APIs or webhooks. +As integrações podem ser {% data variables.product.prodname_github_apps %}, {% data variables.product.prodname_oauth_apps %} ou qualquer coisa que utilize as APIs ou webhooks do {% data variables.product.product_name %}. -{% data variables.product.prodname_github_apps %} offer granular permissions and request access to only what the app needs. {% data variables.product.prodname_github_apps %} also offer specific user-level permissions that each user must authorize individually when an app is installed or when the integrator changes the permissions requested by the app. +{% data variables.product.prodname_github_apps %} oferecem permissões granulares e solicitam acesso apenas ao que o aplicativo precisa. {% data variables.product.prodname_github_apps %} também oferece permissões específicas no nível de usuário que cada um deve autorizar individualmente quando um aplicativo está instalado ou quando o integrador altera as permissões solicitadas pelo aplicativo. Para obter mais informações, consulte: -- "[Differences between {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}](/apps/differences-between-apps/)" +- "[Diferenças entre {% data variables.product.prodname_github_apps %} e {% data variables.product.prodname_oauth_apps %}](/apps/differences-between-apps/)" - "[Sobre aplicativos](/apps/about-apps/)" - "[Permissões de nível de usuário](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-level-permissions)" - "[Autorizar {% data variables.product.prodname_oauth_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps)" @@ -32,10 +32,10 @@ Você poderá criar um {% data variables.product.prodname_github_app %} com conf É possível encontrar uma integração para instalar ou publicar a sua própria integração no {% data variables.product.prodname_marketplace %}. -[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) contains {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}. Para obter mais informações sobre como encontrar uma integração ou criar sua própria integração, consulte "[Sobre o {% data variables.product.prodname_marketplace %}](/articles/about-github-marketplace)". +[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) contém {% data variables.product.prodname_github_apps %} e {% data variables.product.prodname_oauth_apps %}. Para obter mais informações sobre como encontrar uma integração ou criar sua própria integração, consulte "[Sobre o {% data variables.product.prodname_marketplace %}](/articles/about-github-marketplace)". ## Integrações compradas diretamente de integradores Você também pode comprar algumas integrações diretamente de integradores. Como um integrante da organização, ao encontrar um {% data variables.product.prodname_github_app %} que queira usar, você poderá solicitar que uma organização aprove e instale o app para a organização. -If you have admin permissions for all organization-owned repositories the app is installed on, you can install {% data variables.product.prodname_github_apps %} with repository-level permissions without having to ask an organization owner to approve the app. Quando um integrador altera as permissões do app, se as permissões forem apenas para um repositório, os proprietários da organização e as pessoas com permissões de administrador para um repositório com esse app instalado poderão revisar e aceitar as novas permissões. +Se você tiver permissões de administrador para todos os repositórios de organizações em que o app está instalado, você poderá instalar {% data variables.product.prodname_github_apps %} com permissões de nível de repositório sem ter que solicitar que o proprietário da organização aprove o aplicativo. Quando um integrador altera as permissões do app, se as permissões forem apenas para um repositório, os proprietários da organização e as pessoas com permissões de administrador para um repositório com esse app instalado poderão revisar e aceitar as novas permissões. diff --git a/translations/pt-BR/content/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md b/translations/pt-BR/content/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md index 729c1a871a..865da9b884 100644 --- a/translations/pt-BR/content/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md +++ b/translations/pt-BR/content/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md @@ -44,8 +44,8 @@ Você pode integrar sua conta pessoal de {% data variables.product.product_name ### Integração com Slack e {% data variables.product.product_name %} -You can subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, releases, deployment reviews and deployment statuses. You can also perform activities like close or open issues, and provide rich references to issues and pull requests without leaving Slack. Para obter mais informações, visite o [aplicativo de integração do Slack](https://github.com/marketplace/slack-github) no Marketplace. +Você pode assinar os seus repositórios ou organizações e receber atualizações em tempo real sobre problemas, pull requests, commits, versões, análises de implantação e status da implantação. Você também pode realizar atividades como problemas fechados ou abertos e fornecer referências enriquecidas para problemas e pull requests sem sair do Slack. Para obter mais informações, visite o [aplicativo de integração do Slack](https://github.com/marketplace/slack-github) no Marketplace. ### Integração com o Microsoft Teams e {% data variables.product.product_name %} -You can subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, deployment reviews and deployment statuses. You can also perform activities like close or open issues, comment on your issues and pull requests, and provide rich references to issues and pull requests without leaving Microsoft Teams. Para obter mais informações, acesse o [aplicativo de integração do Microsoft Teams](https://appsource.microsoft.com/en-us/product/office/WA200002077) no Microsoft AppSource. +Você pode assinar os seus repositórios ou organizações e receber atualizações em tempo real sobre problemas, pull requests, commits, análises de implantação e status da implantação. Você também pode realizar atividades como fechar ou abrir problemas, comentar nos seus problemas e fornecer referências enriquecidas para problemas e pull requests sem sair do Microsoft Teams. Para obter mais informações, acesse o [aplicativo de integração do Microsoft Teams](https://appsource.microsoft.com/en-us/product/office/WA200002077) no Microsoft AppSource. diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md index 87609a8f27..abd81e474e 100644 --- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md +++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md @@ -42,7 +42,7 @@ No {% data variables.product.prodname_codeql_workflow %} padrão, {% data variab ## Configuração em massa de {% data variables.product.prodname_code_scanning %} -Você pode configurar {% data variables.product.prodname_code_scanning %} em vários repositórios de uma vez usando um script. For an example of a script that raises pull requests to add a {% data variables.product.prodname_actions %} workflow to multiple repositories, see the [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) repository for an example using Powershell, or [`nickliffen/ghas-enablement`](https://github.com/NickLiffen/ghas-enablement) for teams who do not have Powershell and instead would like to use NodeJS. +Você pode configurar {% data variables.product.prodname_code_scanning %} em vários repositórios de uma vez usando um script. Para obter um exemplo de um script que levanta pull requests para adicionar um fluxo de trabalho de {% data variables.product.prodname_actions %} em vários repositórios, consulte o repositório [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) para ver um exemplo que usa o Powershell ou [`nickliffen/ghas-enablement`](https://github.com/NickLiffen/ghas-enablement) para equipes que não possuem Powershell e que, em vez disso, prefeririam usar o NodeJS. ## Visualizar a saída do registro de {% data variables.product.prodname_code_scanning %} diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning/about-integration-with-code-scanning.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning/about-integration-with-code-scanning.md index 00b7759ac3..fdd583d9cc 100644 --- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning/about-integration-with-code-scanning.md +++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning/about-integration-with-code-scanning.md @@ -22,7 +22,7 @@ Se você usar uma ferramenta de análise estática de terceiros que pode produzi ## Integrações com webhooks -You can use {% data variables.product.prodname_code_scanning %} webhooks to build or set up integrations, such as [{% data variables.product.prodname_github_apps %}](/apps/building-github-apps/) or [{% data variables.product.prodname_oauth_apps %}](/apps/building-oauth-apps/), that subscribe to {% data variables.product.prodname_code_scanning %} events in your repository. Por exemplo, você poderia criar uma integração que criasse um problema no {% data variables.product.product_name %} ou que envia uma notificação do Slack quando um novo alerta de {% data variables.product.prodname_code_scanning %} for adicionado ao seu repositório. Para obter mais informações, consulte "[Criar webhooks](/developers/webhooks-and-events/creating-webhooks)" e "[Eventos de Webhook e cargas](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)". +Você pode usar {% data variables.product.prodname_code_scanning %} webhooks para criar ou configurar integrações, tais como [{% data variables.product.prodname_github_apps %}s](/apps/building-github-apps/) ou [{% data variables.product.prodname_oauth_apps %}s](/apps/building-oauth-apps/), que assinam os eventos {% data variables.product.prodname_code_scanning %} no seu repositório. Por exemplo, você poderia criar uma integração que criasse um problema no {% data variables.product.product_name %} ou que envia uma notificação do Slack quando um novo alerta de {% data variables.product.prodname_code_scanning %} for adicionado ao seu repositório. Para obter mais informações, consulte "[Criar webhooks](/developers/webhooks-and-events/creating-webhooks)" e "[Eventos de Webhook e cargas](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)". ## Leia mais diff --git a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning/sarif-support-for-code-scanning.md b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning/sarif-support-for-code-scanning.md index 611c01c460..01b5eef538 100644 --- a/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning/sarif-support-for-code-scanning.md +++ b/translations/pt-BR/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning/sarif-support-for-code-scanning.md @@ -31,7 +31,7 @@ Se você for novo no SARIF e quiser saber mais, consulte o repositório da Micro Cada vez que um fluxo de trabalho do {% data variables.product.prodname_actions %} executa uma nova varredura de código, os resultados de cada execução são processados e os alertas são adicionados ao repositório. Para evitar alertas duplicados para o mesmo problema, {% data variables.product.prodname_code_scanning %} usa impressões digitais para corresponder aos resultados em várias execuções, para que apareçam apenas uma vez na última execução do ramo selecionado. Isto torna possível combinar alertas com a linha de código correta quando os arquivos são editados. -O {% data variables.product.prodname_dotcom %} usa a propriedade `partialFingerprints` no padrão OASIS para detectar quando dois resultados são idênticos logicamente. Para obter mais informações, consulte a entrada "[partialFingerprints property](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012611)" na documentação do OASIS. +{% data variables.product.prodname_dotcom %} uses the `partialFingerprints` property in the OASIS standard as an input in the computation of whether two results are logically identical. Specifically, the `primaryLocationLineHash` is used as a stable intra-file location, which is combined with the repository, file path, and rule data to form the full identity. Para obter mais informações, consulte a entrada "[partialFingerprints property](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012611)" na documentação do OASIS. OS arquivos do SARIF criados pelo {% data variables.product.prodname_codeql_workflow %} ou usando {% data variables.product.prodname_codeql_runner %} incluem dados de impressão digital. Se você enviar um arquivo SARIF usando a ação `upload-sarif` e estes dados estiverem faltando, {% data variables.product.prodname_dotcom %} tenta preencher o campo `partialFingerprints` a partir dos arquivos de origem. Para obter mais informações sobre o upload de resultados, consulte "[Fazer o upload de um arquivo SARIF para o {% data variables.product.prodname_dotcom %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github#uploading-a-code-scanning-analysis-with-github-actions)". @@ -89,17 +89,17 @@ O {% data variables.product.prodname_code_scanning_capc %} usa o objeto `executa {% data reusables.code-scanning.upload-sarif-alert-limit %} -| Nome | Descrição | -| --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `ruleId` | **Opcional.** O identificador exclusivo da regra (`reportingDescriptor.id`). Para obter mais informações, consulte o objeto [`reportingDescriptor`](#reportingdescriptor-object). {% data variables.product.prodname_code_scanning_capc %} usa o identificador da regra para filtrar os resultados por regra em {% data variables.product.prodname_dotcom %}. | -| `ruleIndex` | **Opcional.** O índice da regra associada (objeto `reportingDescriptor`) no array `regras` no componente da ferramenta. Para obter mais informações, consulte o objeto [`executar`](#run-object). | -| `rule` | **Opcional.** Uma referência usada para localizar a regra (descritor de relatório) para este resultado. Para obter mais informações, consulte o objeto [`reportingDescriptor`](#reportingdescriptor-object). | -| `level` | **Opcional.** A gravidade do resultado. Esse nível sobrepõe a severidade-padrão definida pela regra. {% data variables.product.prodname_code_scanning_capc %} usa o nível para filtrar resultados por gravidade em {% data variables.product.prodname_dotcom %}. | -| `message.text` | **Obrigatório.** Uma mensagem que descreve o resultado. {% data variables.product.prodname_code_scanning_capc %} exibe o texto da mensagem como o título do resultado. Apenas a primeira frase da mensagem será exibida quando o espaço visível for limitado. | -| `locations[]` | **Obrigatório.** O conjunto de locais onde o resultado foi detectado até o máximo de 10. Só um local deve ser incluído, a não ser que o problema só possa ser corrigido fazendo uma alteração em cada local especificado. **Observação:** Pelo menos um local é necessário para {% data variables.product.prodname_code_scanning %} apresentar um resultado. {% data variables.product.prodname_code_scanning_capc %} usará essa propriedade para decidir qual arquivo fazer anotações com o resultado. Apenas o primeiro valor desse array é usado. Todos os outros valores são ignorados. | -| `partialFingerprints` | **Obrigatório.** Um conjunto de strings usado para rastrear a identidade única do resultado. {% data variables.product.prodname_code_scanning_capc %} usa `partialFingerprints` para identificar com precisão quais resultados são os mesmos em todos os commits e branches. O {% data variables.product.prodname_code_scanning_capc %} tentará usar `partialFingerprints`, se existirem. Se você estiver fazendo upload de arquivos SARIF de terceiros com `upload-action`, a ação irá criar `partialFingerprints` para você quando não estiverem incluídos no arquivo SARIF. Para obter mais informações, consulte "[Prevenir alertas duplicados usando impressões digitais](#preventing-duplicate-alerts-using-fingerprints)". **Observação:** {% data variables.product.prodname_code_scanning_capc %} usa apenas `primaryLocationLineHash`. | -| `codeFlows[].threadFlows[].locations[]` | **Opcional.** Uma array de objetos `local` para um objeto `threadFlow`, que descreve o progresso de um programa por meio de um thread de execução. Um objeto `codeFlow` descreve um padrão de execução de código usado para detectar um resultado. Se forem fornecidos fluxos de código, {% data variables.product.prodname_code_scanning %} irá expandir os fluxos de código em {% data variables.product.prodname_dotcom %} para o resultado relevante. Para obter mais informações, consulte o objeto [`local`](#location-object). | -| `relatedLocations[]` | Um conjunto de locais relevantes para este resultado. {% data variables.product.prodname_code_scanning_capc %} irá vincular a locais relacionados quando forem incorporados à mensagem do resultado. Para obter mais informações, consulte o objeto [`local`](#location-object). | +| Nome | Descrição | +| --------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `ruleId` | **Opcional.** O identificador exclusivo da regra (`reportingDescriptor.id`). Para obter mais informações, consulte o objeto [`reportingDescriptor`](#reportingdescriptor-object). {% data variables.product.prodname_code_scanning_capc %} usa o identificador da regra para filtrar os resultados por regra em {% data variables.product.prodname_dotcom %}. | +| `ruleIndex` | **Opcional.** O índice da regra associada (objeto `reportingDescriptor`) no array `regras` no componente da ferramenta. Para obter mais informações, consulte o objeto [`executar`](#run-object). | +| `rule` | **Opcional.** Uma referência usada para localizar a regra (descritor de relatório) para este resultado. Para obter mais informações, consulte o objeto [`reportingDescriptor`](#reportingdescriptor-object). | +| `level` | **Opcional.** A gravidade do resultado. Esse nível sobrepõe a severidade-padrão definida pela regra. {% data variables.product.prodname_code_scanning_capc %} usa o nível para filtrar resultados por gravidade em {% data variables.product.prodname_dotcom %}. | +| `message.text` | **Obrigatório.** Uma mensagem que descreve o resultado. {% data variables.product.prodname_code_scanning_capc %} exibe o texto da mensagem como o título do resultado. Apenas a primeira frase da mensagem será exibida quando o espaço visível for limitado. | +| `locations[]` | **Obrigatório.** O conjunto de locais onde o resultado foi detectado até o máximo de 10. Só um local deve ser incluído, a não ser que o problema só possa ser corrigido fazendo uma alteração em cada local especificado. **Observação:** Pelo menos um local é necessário para {% data variables.product.prodname_code_scanning %} apresentar um resultado. {% data variables.product.prodname_code_scanning_capc %} usará essa propriedade para decidir qual arquivo fazer anotações com o resultado. Apenas o primeiro valor desse array é usado. Todos os outros valores são ignorados. | +| `partialFingerprints` | **Obrigatório.** Um conjunto de strings usado para rastrear a identidade única do resultado. {% data variables.product.prodname_code_scanning_capc %} uses `partialFingerprints` as part of the computation to accurately identify which results are the same across commits and branches. O {% data variables.product.prodname_code_scanning_capc %} tentará usar `partialFingerprints`, se existirem. Se você estiver fazendo upload de arquivos SARIF de terceiros com `upload-action`, a ação irá criar `partialFingerprints` para você quando não estiverem incluídos no arquivo SARIF. Para obter mais informações, consulte "[Prevenir alertas duplicados usando impressões digitais](#preventing-duplicate-alerts-using-fingerprints)". **Observação:** {% data variables.product.prodname_code_scanning_capc %} usa apenas `primaryLocationLineHash`. | +| `codeFlows[].threadFlows[].locations[]` | **Opcional.** Uma array de objetos `local` para um objeto `threadFlow`, que descreve o progresso de um programa por meio de um thread de execução. Um objeto `codeFlow` descreve um padrão de execução de código usado para detectar um resultado. Se forem fornecidos fluxos de código, {% data variables.product.prodname_code_scanning %} irá expandir os fluxos de código em {% data variables.product.prodname_dotcom %} para o resultado relevante. Para obter mais informações, consulte o objeto [`local`](#location-object). | +| `relatedLocations[]` | Um conjunto de locais relevantes para este resultado. {% data variables.product.prodname_code_scanning_capc %} irá vincular a locais relacionados quando forem incorporados à mensagem do resultado. Para obter mais informações, consulte o objeto [`local`](#location-object). | ### Objeto `local` diff --git a/translations/pt-BR/content/github/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line.md b/translations/pt-BR/content/github/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line.md index 55a4852fa1..cc025c72bd 100644 --- a/translations/pt-BR/content/github/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line.md +++ b/translations/pt-BR/content/github/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line.md @@ -12,7 +12,7 @@ versions: shortTitle: Adicionar um projeto localmente --- -## About adding existing projects to {% data variables.product.product_name %} +## Sobre a adição de projetos existentes para {% data variables.product.product_name %} {% data reusables.repositories.migrating-from-codeplex %} @@ -24,37 +24,37 @@ shortTitle: Adicionar um projeto localmente {% data reusables.repositories.sensitive-info-warning %} -## Adding a project to {% data variables.product.product_name %} with {% data variables.product.prodname_cli %} +## Adicionando um projeto a {% data variables.product.product_name %} com {% data variables.product.prodname_cli %} -{% data variables.product.prodname_cli %} é uma ferramenta de código aberto para usar {% data variables.product.product_name %} a partir da linha de comando do seu computador. {% data variables.product.prodname_cli %} can simplify the process of adding an existing project to {% data variables.product.product_name %} using the command line. To learn more about {% data variables.product.prodname_cli %}, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)." +{% data variables.product.prodname_cli %} é uma ferramenta de código aberto para usar {% data variables.product.product_name %} a partir da linha de comando do seu computador. {% data variables.product.prodname_cli %} pode simplificar o processo de adicionar um projeto existente a {% data variables.product.product_name %} usando a linha de comando. Para saber mais sobre {% data variables.product.prodname_cli %}, consulte "[Sobre {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)." -1. In the command line, navigate to the root directory of your project. +1. Na linha de comando, acesse o diretório raiz do seu projeto. 1. Inicialize o diretório local como um repositório Git. ```shell git init -b main ``` -1. To create a repository for your project on {% data variables.product.product_name %}, use the `gh repo create` subcommand. Replace `project-name` with the desired name for your repository. If you want your project to belong to an organization instead of to your user account, specify the organization name and project name with `organization-name/project-name`. +1. Para criar um repositório para o seu projeto em {% data variables.product.product_name %}, use o subcomando `gh repo create`. Substitua `project-name` pelo nome desejado para o repositório. Se você quiser que o seu projeto pertença a uma organização em vez de sua conta de usuário, especifique o nome da organização e o nome do projeto com `organization-name/project-name`. ```shell gh repo create project-name ``` -1. Follow the interactive prompts. Alternatively, you can specify arguments to skip these prompts. For more information about possible arguments, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_repo_create). -1. Pull changes from the new repository that you created. (If you created a `.gitignore` or `LICENSE` file in the previous step, this will pull those changes to your local directory.) +1. Siga as instruções interativas. Como alternativa, você pode especificar argumentos para pular essas instruções. Para obter mais informações sobre possíveis argumentos, consulte [o manual de {% data variables.product.prodname_cli %}](https://cli.github.com/manual/gh_repo_create). +1. Faça pull das alterações do novo repositório que você criou. (Se você criou um arquivo `.gitignore` ou `LICENSE` na etapa anterior, isso irá fazer pull dessas alterações para seu diretório local.) ```shell git pull --set-upstream origin main ``` -1. Stage, commit, and push all of the files in your project. +1. Stage, commit e push de todos os arquivos do seu projeto. ```shell git add . && git commit -m "initial commit" && git push ``` -## Adding a project to {% data variables.product.product_name %} without {% data variables.product.prodname_cli %} +## Adicionando um projeto a {% data variables.product.product_name %} sem {% data variables.product.prodname_cli %} {% mac %} diff --git a/translations/pt-BR/content/github/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools.md b/translations/pt-BR/content/github/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools.md index b76d0b5313..694b9967ac 100644 --- a/translations/pt-BR/content/github/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools.md +++ b/translations/pt-BR/content/github/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools.md @@ -38,7 +38,7 @@ Recomendamos o [hg-fast-export](https://github.com/frej/fast-export) para conver Recomendamos [git-tfs](https://github.com/git-tfs/git-tfs) para transferir alterações entre TFVC e Git. -For more information about moving from TFVC (a centralized version control system) to Git, see "[Plan your Migration to Git](https://docs.microsoft.com/devops/develop/git/centralized-to-git)" from the Microsoft docs site. +Para obter mais informações sobre como mudar do TFVC (um sistema centralizado de controle de versão) para o Git, consulte "[Planeje sua migração para o Git](https://docs.microsoft.com/devops/develop/git/centralized-to-git)" no site da documentação da Microsoft. {% tip %} diff --git a/translations/pt-BR/content/github/index.md b/translations/pt-BR/content/github/index.md index c2d47a89b2..64df082782 100644 --- a/translations/pt-BR/content/github/index.md +++ b/translations/pt-BR/content/github/index.md @@ -1,5 +1,5 @@ --- -title: GitHub.com +title: GitHub redirect_from: - /articles/ - /common-issues-and-questions/ @@ -15,7 +15,6 @@ children: - /writing-on-github - /committing-changes-to-your-project - /collaborating-with-pull-requests - - /searching-for-information-on-github - /importing-your-projects-to-github - /managing-security-vulnerabilities - /finding-security-vulnerabilities-and-errors-in-your-code diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/about-identity-and-access-management-for-your-enterprise-account.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/about-identity-and-access-management-for-your-enterprise-account.md index 9f241b282e..eb6e29aefc 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/about-identity-and-access-management-for-your-enterprise-account.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/about-identity-and-access-management-for-your-enterprise-account.md @@ -13,13 +13,19 @@ shortTitle: IAM para a sua empresa ## Sobre a identidade e gestão de acesso para a sua conta corporativa -{% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %} For more information, see "[Enforcing SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account)." +{% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %} Para obter mais informações, consulte "[Aplicando o login único SAML para organizações na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account)." Depois de habilitar o SSO do SAML, dependendo do IdP que você usar, você poderá habilitar as funcionalidades adicionais de gerenciamento de identidade e acesso. {% data reusables.scim.enterprise-account-scim %} Se você usar o Azure AD como seu IDP, você poderá usar a sincronização de equipe para gerenciar a associação de equipe em cada organização. {% data reusables.identity-and-permissions.about-team-sync %} Para obter mais informações, consulte "[Gerenciar a sincronização de equipes para organizações na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)". -{% data reusables.saml.switching-from-org-to-enterprise %} For more information, see "[Switching your SAML configuration from an organization to an enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)." +{% data reusables.saml.switching-from-org-to-enterprise %} Para obter mais informações, consulte "[Alterando sua configuração do SAML de uma organização para uma conta corporativa](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)". + +## Sobre o {% data variables.product.prodname_emus %} + +{% data reusables.enterprise-accounts.emu-short-summary %} + +A configuração de {% data variables.product.prodname_emus %} para o logon único SAML e provisionamento de usuário envolve seguir um processo diferente do que você faria para uma empresa que não estivesse usando {% data variables.product.prodname_managed_users %}. Se a sua empresa usar {% data variables.product.prodname_emus %}, consute "[Configurando o logon único SAML para usuários gerenciados pela empresa](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)". ## IdPs compatíveis @@ -32,4 +38,3 @@ Nós testamos e oferecemos compatibilidade oficial os seguintes IdPs. Para o SSO | OneLogin | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | PingOne | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | Shibboleth | {% octicon "check-circle-fill" aria-label="The check icon" %} | | - diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/configuring-saml-single-sign-on-for-your-enterprise-account-using-okta.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/configuring-saml-single-sign-on-for-your-enterprise-account-using-okta.md index 1c1c5d1340..d9259b522d 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/configuring-saml-single-sign-on-for-your-enterprise-account-using-okta.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/configuring-saml-single-sign-on-for-your-enterprise-account-using-okta.md @@ -11,18 +11,20 @@ versions: fpt: '*' topics: - Enterprise -shortTitle: Configure SAML with Okta +shortTitle: Configurar o SAML com Okta --- {% data reusables.enterprise-accounts.user-provisioning-release-stage %} +{% data reusables.enterprise-accounts.emu-saml-note %} + ## Sobre o SAML com Okta Você pode controlar o acesso à conta corporativa no {% data variables.product.product_name %} e em outros aplicativos web, a partir de uma interface central, configurando a conta corporativa para usar SAML SSO com Okta, um provedor de identidade (IdP). -O SAML SSO controla e protege o acesso a recursos da conta corporativa, como, por exemplo, organizações, repositórios, problemas e pull requests. For more information, see "[Enforcing SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account)." +O SAML SSO controla e protege o acesso a recursos da conta corporativa, como, por exemplo, organizações, repositórios, problemas e pull requests. Para obter mais informações, consulte "[Aplicar o logon único SAML para organizações na conta corporativa](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account)". -{% data reusables.saml.switching-from-org-to-enterprise %} For more information, see "[Switching your SAML configuration from an organization to an enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)." +{% data reusables.saml.switching-from-org-to-enterprise %} Para obter mais informações, consulte "[Alterando sua configuração do SAML de uma organização para uma conta corporativa](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)". ## Pré-requisitos @@ -52,7 +54,7 @@ O SAML SSO controla e protege o acesso a recursos da conta corporativa, como, po 1. À direita do menu suspenso, digite `.*.*`. 1. Clique em **Salvar**. {% data reusables.saml.okta-view-setup-instructions %} -1. Habilite o SAML para a conta corporativa usando as informações nas instruções de configuração. For more information, see "[Enforcing SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account)." +1. Habilite o SAML para a conta corporativa usando as informações nas instruções de configuração. Para obter mais informações, consulte "[Aplicar o logon único SAML para organizações na conta corporativa](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account)". ## Criar grupos no Okta diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account.md index b1f4f40ffe..d199837118 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account.md @@ -1,6 +1,6 @@ --- -title: Enforcing SAML single sign-on for organizations in your enterprise account -intro: 'You can control and secure access to resources like repositories, issues, and pull requests by enforcing SAML single sign-on (SSO) and centralized authentication through an IdP across all organizations owned by an enterprise account.' +title: Aplicando o login único SAML para as organizações na sua conta corporativa +intro: 'É possível controlar e garantir o acesso a recursos como repositórios, problemas, e pull requests aplicando o logon único SAML (SSO) e a autenticação centralizada por meio de um IdP em todas as organizações pertencentes a uma conta corporativa.' product: '{% data reusables.gated-features.enterprise-accounts %}' permissions: Enterprise owners can enforce SAML single sign-on for organizations in an enterprise account. versions: @@ -10,9 +10,11 @@ topics: redirect_from: - /github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account - /github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account -shortTitle: Enforce SAML +shortTitle: Aplicar o SAML --- +{% data reusables.enterprise-accounts.emu-saml-note %} + ## Sobre o logon único SAML para contas corporativas {% data reusables.saml.dotcom-saml-explanation %} 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)". @@ -25,14 +27,14 @@ shortTitle: Enforce SAML {% data reusables.scim.enterprise-account-scim %} -## Enforcing SAML single-sign on for organizations in your enterprise account +## Aplicar o logon único SAML para organizações na sua conta corporativa {% note %} **Notas:** -- When you enable SAML SSO for your enterprise, the enterprise configuration will override any existing organization-level SAML configurations. {% data reusables.saml.switching-from-org-to-enterprise %} For more information, see "[Switching your SAML configuration from an organization to an enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)." -- When you enforce SAML SSO for an organization, {% data variables.product.company_short %} removes any members of the organization that have not authenticated successfully with your SAML IdP. When you require SAML SSO for your enterprise, {% data variables.product.company_short %} does not remove members of the enterprise that have not authenticated successfully with your SAML IdP. The next time a member accesses the enterprise's resources, the member must authenticate with your SAML IdP. +- Ao habilitar o logon único SAML SSO para sua empresa, a configuração corporativa substituirá todas as configurações do SAML existentes no nível da organização. {% data reusables.saml.switching-from-org-to-enterprise %} Para obter mais informações, consulte "[Alterando sua configuração do SAML de uma organização para uma conta corporativa](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)". +- Ao aplicar o SAML SSO para uma organização, {% data variables.product.company_short %} removerá todos os integrantes da organização que não tenham efetuado a autenticação com sucesso com seu IdP do SAML. Ao exigir o SAML SSO para a sua empresa, {% data variables.product.company_short %} não irá remover os integrantes da empresa que não tenham efetuado a autenticação com sucesso com o IdP do SAML. Na próxima vez que um integrante acessar os recursos da empresa, ele deverá efetuar a autenticação com o seu IdP do SAML. {% endnote %} @@ -42,7 +44,7 @@ Para obter informações mais detalhadas sobre como habilitar o SAML usando o Ok {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} 4. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} -5. Under "SAML single sign-on", select **Require SAML authentication**. ![Caixa de seleção para habilitar SAML SSO](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) +5. Em "Logon único SAML", selecione **Exigir autenticação do SAML**. ![Caixa de seleção para habilitar SAML SSO](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) 6. No campo **Sign on URL** (URL de logon), digite o ponto de extremidade HTTPS do seu IdP para solicitações de logon único. Esse valor está disponível na configuração do IdP. ![Campo referente à URL para a qual os integrantes serão encaminhados ao entrarem](/assets/images/help/saml/saml_sign_on_url_business.png) 7. Opcionalmente, no campo **Emissor**, digite a URL do emissor do SAML para verificar a autenticidade das mensagens enviadas. ![Campo referente ao nome do emissor de SAML](/assets/images/help/saml/saml_issuer.png) 8. Em **Public Certificate** (Certificado público), cole um certificado para verificar as respostas de SAML. ![Campo referente ao certificado público do seu provedor de identidade](/assets/images/help/saml/saml_public_certificate.png) diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/managing-team-synchronization-for-organizations-in-your-enterprise-account.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/managing-team-synchronization-for-organizations-in-your-enterprise-account.md index 12997ad5af..e1afa89af9 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/managing-team-synchronization-for-organizations-in-your-enterprise-account.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/managing-team-synchronization-for-organizations-in-your-enterprise-account.md @@ -12,6 +12,8 @@ redirect_from: shortTitle: Gerenciar sincronização de equipe --- +{% data reusables.enterprise-accounts.emu-scim-note %} + ## Sobre a sincronização de equipes para contas corporativas Se você usar o Azure AD como seu IdP, você pode habilitar a sincronização de equipes para sua conta corporativa para permitir que os proprietários da organização e mantenedores de equipe sincronizem as equipes nas organizações pertencentes às contas corporativas com os grupos de IdP. @@ -30,7 +32,7 @@ Você também pode configurar e gerenciar a sincronização da equipe para uma o Você ou o administrador do Azure AD deve ser um administrador global ou um administrador com função privilegiada no Azure AD. -You must enforce SAML single sign-on for organizations in your enterprise account with your supported IdP. For more information, see "[Enforcing SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account)." +Você deve aplicar o logon único SAML para organizações na sua conta corporativa com o IdP compatível. Para obter mais informações, consulte "[Aplicar o logon único SAML para organizações na conta corporativa](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account)". Você deve efetuar a autenticação na sua conta corporativa usando o SAML SSO e o IdP compatível. Para obter mais informações, consulte "[Autenticar com logon único de SAML](/articles/authenticating-with-saml-single-sign-on)". diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md index c5d97c167c..ce5aa1329a 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md @@ -1,39 +1,41 @@ --- -title: Switching your SAML configuration from an organization to an enterprise account -intro: Learn special considerations and best practices for replacing an organization-level SAML configuration with an enterprise-level SAML configuration. +title: Alterando a configuração do SAML de uma organização para uma conta corporativa +intro: Aprenda as considerações especiais e as práticas recomendas para substituir uma configuração do SAML no nível da organização por uma configuração do SAML de nível corporativo. product: '{% data reusables.gated-features.enterprise-accounts %}' permissions: Enterprise owners can configure SAML single sign-on for an enterprise account. versions: fpt: '*' topics: - Enterprise -shortTitle: Switching from organization +shortTitle: Alternando a partir da organização --- +{% data reusables.enterprise-accounts.emu-saml-note %} + ## Sobre o logon único SAML para contas corporativas {% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %} {% data reusables.saml.switching-from-org-to-enterprise %} -When you configure SAML SSO at the organization level, each organization must be configured with a unique SSO tenant in your IdP, which means that your members will be associated with a unique SAML identity record for each organization they have succesfully authenticated with. If you configure SAML SSO for your enterprise account instead, each enterprise member will have one SAML identity that is used for all organizations owned by the enterprise account. +Ao configurar o SAML SSO no nível da organização, cada uma deverpa ser configurada com um inquilino de SSO único no seu IdP, o que significa que os seus integrantes serão associados a um registro de identidade do SAML único para cada organização com a qual tenham efetuado a autenticação com sucesso. Se você configurar o SAML SSO para a sua conta corporativa, cada integrante da empresa terá uma identidade do SAML utilizada para todas as organizações pertencentes à conta corporativa. -After you configure SAML SSO for your enterprise account, the new configuration will override any existing SAML SSO configurations for organizations owned by the enterprise account. +Depois de configurar o SAML SSO para a conta corporativa, a nova configuração irá substituir todas as configurações do SAML SSO existentes para as organizações pertencentes à conta corporativa. -Enterprise members will not be notified when an enterprise owner enables SAML for the enterprise account. If SAML SSO was previously enforced at the organization level, members should not see a major difference when navigating directly to organization resources. The members will continue to be prompted to authenticate via SAML. If members navigate to organization resources via their IdP dashboard, they will need to click the new tile for the enterprise-level app, instead of the old tile for the organization-level app. The members will then be able to choose the organization to navigate to. +Os integrantes da empresa não serão notificados quando um proprietário corporativo permitir o SAML para a conta corporativa. Se o SAML SSO foi aplicado anteriormente no nível da organização, os integrantes não deverão ver uma grande diferença ao acessar diretamente os recursos da organização. Continuará sendo solicitado que os integrantes efetuem a autenticação por meio do SAML. Se os membros acessarem os recursos da organização por meio do painel do IdP, eles deverão clicar na nova seção do aplicativo de nível corporativo, em vez de clicar na seção antiga para o aplicativo de nível da organização. Em seguida, os integrantes poderão escolher a organização a qual acessar. -Any personal access tokens (PATs), SSH keys, {% data variables.product.prodname_oauth_apps %}, and {% data variables.product.prodname_github_apps %} that were previously authorized for the organization will continue to be authorized for the organization. However, members will need to authorize any PATs, SSH keys, {% data variables.product.prodname_oauth_apps %}, and {% data variables.product.prodname_github_apps %} that were never authorized for use with SAML SSO for the organization. +Todos os tokens de acesso pessoal (PATs), chaves SSH, {% data variables.product.prodname_oauth_apps %} e {% data variables.product.prodname_github_apps %} que foram previamente autorizados para a organização continuarão sendo autorizados para a organização. No entanto, os integrantes deverão autorizar todos os PATs, chaves SSH, {% data variables.product.prodname_oauth_apps %} e {% data variables.product.prodname_github_apps %} que nunca foram autorizados para uso com o SAML SSO para a organização. -SCIM provisioning is not currently supported when SAML SSO is configured for an enterprise account. If you are currently using SCIM for an organization owned by your enterprise account, you will lose this functionality when switching to an enterprise-level configuration. +O provisionamento do SCIM não é atualmente compatível quando o SAML SSO está configurado para uma conta corporativa. Se você estiver usando atualmente o SCIM para uma organização pertencente à sua conta corporativa, você perderá essa funcionalidade ao mudar para uma configuração de nível corporativo. -You are not required to remove any organization-level SAML configurations before configuring SAML SSO for your enterprise account, but you may want to consider doing so. If SAML is ever disabled for the enterprise account in the future, any remaining organization-level SAML configurations will take effect. Removing the organization-level configurations can prevent unexpected issues in the future. +Não é necessário remover nenhuma configuração do SAML no nível da organização antes de configurar o SAML SSO para a sua conta corporativa, mas talvez você deva considerar fazer isso. Se o SAML for desabilitado para a conta corporativa no futuro, todas as configurações restantes do SAML entrarão em vigor. A remoção das configurações ao nível da organização pode evitar problemas inesperados no futuro. -## Switching your SAML configuration from an organization to an enterprise account +## Alterando a configuração do SAML de uma organização para uma conta corporativa -1. Enforce SAML SSO for your enterprise account, making sure all organization members are assigned or given access to the IdP app being used for the enterprise account. For more information, see "[Enforcing SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account)." -1. Optionally, remove any existing SAML configuration for organizations owned by the enterprise account. To help you decide whether to remove the configurations, see "[About SAML single sign-on for enterprise accounts](#about-saml-single-sign-on-for-enterprise-accounts)." -1. If you kept any organization-level SAML configurations in place, to prevent confusion, consider hiding the tile for the organization-level apps in your IdP. -1. Advise your enterprise members about the change. - - Members will no longer be able to access their organizations by clicking the SAML app for the organization in the IdP dashboard. They will need to use the new app configured for the enterprise account. - - Members will need to authorize any PATs or SSH keys that were not previously authorized for use with SAML SSO for their organization. Para mais informações consulte "[Autorizar um token de acesso pessoal para usar com o logon único SAML](/github/authenticating-to-github/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" e "[Autorizar uma chave SSH para uso com o logon único SAML](/github/authenticating-to-github/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)." - - Members may need to reauthorize {% data variables.product.prodname_oauth_apps %} that were previously authorized for the organization. Para obter mais informações, consulte "[Sobre a autenticação com logon único SAML](/github/authenticating-to-github/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on#about-oauth-apps-and-saml-sso)". +1. Aplique o SAML SSO na sua conta corporativa, certificando-se de que todos os integrantes da organização recebam o acesso ao aplicativo do IdP que está sendo usado para a conta corporativa. Para obter mais informações, consulte "[Aplicar o logon único SAML para organizações na conta corporativa](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account)". +1. Opcionalmente, remova qualquer configuração existente do SAML para as organizações pertencentes à conta corporativa. Para ajudar você a decidir se deseja remover as configurações, consulte "[Sobre o logon único SAML para contas corporativas](#about-saml-single-sign-on-for-enterprise-accounts)". +1. Se você manteve as configurações do SAML no nível da organização, para evitar confusão, considere ocultar o botão para os aplicativos noe nível da organização no seu IdP. +1. Informe os integrantes da sua empresa sobre a alteração. + - Os integrantes não poderão mais acessar as suas organizações clicando no aplicativo SAML para a organização no painel do IdP. Eles deverão usar o novo aplicativo configurado para a conta corporativa. + - Os integrantes deverão autorizar todos PATs ou chaves SSH que não tenham sido previamente autorizadas para uso com o SAML SSO para a sua organização. Para mais informações consulte "[Autorizar um token de acesso pessoal para usar com o logon único SAML](/github/authenticating-to-github/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" e "[Autorizar uma chave SSH para uso com o logon único SAML](/github/authenticating-to-github/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)." + - É possível que os integrantes tenham de reautorizar {% data variables.product.prodname_oauth_apps %} que foram autorizados anteriormente para a organização. Para obter mais informações, consulte "[Sobre a autenticação com logon único SAML](/github/authenticating-to-github/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on#about-oauth-apps-and-saml-sso)". diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/index.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/index.md index 3cd4edf8a3..ff3187934b 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/index.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/index.md @@ -14,6 +14,7 @@ topics: children: - /managing-your-enterprise-account - /managing-users-in-your-enterprise + - /managing-your-enterprise-users-with-your-identity-provider - /managing-organizations-in-your-enterprise-account - /configuring-identity-and-access-management-for-your-enterprise-account - /setting-policies-for-organizations-in-your-enterprise-account diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account.md index eea794b23e..c50ea1bc57 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account.md @@ -1,6 +1,6 @@ --- title: Adicionar organizações à suas conta corporativa -intro: É possível criar novas organizações para serem gerenciadas em sua conta corporativa. +intro: É possível criar novas organizações ou convidar organizações existentes para gerenciar dentro da sua conta corporativa. product: '{% data reusables.gated-features.enterprise-accounts %}' redirect_from: - /articles/adding-organizations-to-your-enterprise-account @@ -13,9 +13,9 @@ topics: shortTitle: Adicionar organizações --- -Proprietários corporativos podem criar novas organizações nas configurações da conta corporativa. +Os proprietários corporativos podem criar novas organizações dentro das configurações de uma conta corporativa ou convidar organizações existentes para participar de uma conta corporativa. -Para adicionar uma organização à sua conta corporativa, você deve criar a organização dentro das configurações de conta corporativa. Se você deseja transferir uma organização existente para a conta corporativa, entre em contato com a representante de vendas da sua conta de {% data variables.product.prodname_dotcom %}. +Para adicionar uma organização à sua conta corporativa, você deve criar a organização dentro das configurações de conta corporativa. ## Criar uma organização em sua conta corporativa @@ -29,3 +29,15 @@ Os proprietários da empresa que criam uma organização pertencente à conta co 4. Clique em **Create organization** (Criar organização). 5. Em "Invite owners" (Convidar proprietários), digite o nome de usuário de uma pessoa que deseja convidar para se tornar um proprietário da organização e clique em **Invite** (Convidar). ![Campo de pesquisa do proprietário da organização e botão Invite (Convidar)](/assets/images/help/business-accounts/invite-org-owner.png) 6. Clique em **Finalizar**. + +## Convidar uma organização para se juntar-se à sua conta corporativa + +Os proprietários corporativos podem convidar organizações existentes para juntar-se à sua conta corporativa. Se a organização que deseja convidar já pertence a outra empresa, você não poderá enviar um convite até que a empresa anterior desista da propriedade da organização. + +{% data reusables.enterprise-accounts.access-enterprise %} +2. Na aba **Organizações**, acima da lista de organizações, clique em **Convidar organização**. ![Convidar organização](/assets/images/help/business-accounts/enterprise-account-invite-organization.png) +3. Em "Organização", comece a digitar o nome da organização que deseja convidar e selecione-a quando aparecer na lista suspensa. ![Pesquisar organização](/assets/images/help/business-accounts/enterprise-account-search-for-organization.png) +4. Clique em **Convidar organização**. +5. Os proprietários da organização receberão um e-mail convidando-os para participar da organização. Pelo menos um proprietário deverá aceitar o convite antes que o processo possa continuar. Você pode cancelar ou reenviar o convite a qualquer momento antes que um proprietário o aprove. ![Cancelar ou reenviar](/assets/images/help/business-accounts/enterprise-account-invitation-sent.png) +6. Uma vez que o proprietário da organização tenha aprovado o convite, você poderá ver o seu estado na lista de convites pendentes. ![Convite pendente](/assets/images/help/business-accounts/enterprise-account-pending.png) +7. Clique em **Aprovar** para concluir a transferência ou **Cancelar** para cancelá-la. ![Aprovar convite](/assets/images/help/business-accounts/enterprise-account-transfer-approve.png) diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md index ec92d89172..4f63666059 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md @@ -1,108 +1,108 @@ --- -title: Streaming the audit logs for organizations in your enterprise account -intro: 'Enterprise owners can stream audit and Git events data from {% data variables.product.prodname_dotcom %} to an external data management system.' +title: Transmitir os logs de auditoria para organizações da sua conta corporativa +intro: 'Os proprietários corporativos podem transmitir dados de auditoria e eventos Git de {% data variables.product.prodname_dotcom %} para um sistema externo de gerenciamento de dados.' product: '{% data reusables.gated-features.enterprise-accounts %}' miniTocMaxHeadingLevel: 3 versions: fpt: '*' topics: - Enterprise -shortTitle: Stream organization audit logs +shortTitle: Transmitir os logs de auditoria da organização --- {% note %} -**Note:** Audit log streaming is currently in beta for {% data variables.product.prodname_ghe_cloud %} and subject to change. +**Observação:** A transmissão do log de auditoria está atualmente em beta para {% data variables.product.prodname_ghe_cloud %} e sujeito a alterações. {% endnote %} -## About exporting audit data +## Sobre a exportação dos dados de auditoria -You can extract audit log and Git events data from {% data variables.product.prodname_dotcom %} in multiple ways: +Você pode extrair dados de eventos de auditoria de {% data variables.product.prodname_dotcom %} e Git de várias maneiras: -* Go to the Audit log page in {% data variables.product.prodname_dotcom %} and click **Export**.
    For more information, see "[Viewing the audit logs for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account)" and "[Exporting the audit log](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#exporting-the-audit-log)." -* Use the API to poll for new audit log events.
    For more information, see "[Using the audit log API](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#using-the-audit-log-api)." -* Set up {% data variables.product.product_name %} to stream audit data as events are logged. +* Acesse a página de log de auditoria em {% data variables.product.prodname_dotcom %} e clique em **Exportar**.
    Para obter mais informações, consulte "[Visualizando os logs de auditoria para organizações na conta corporativa](/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account)" e "[Exportando o log de auditoria](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#exporting-the-audit-log)". +* Use a API para fazer uma pesquisa para novos eventos de log de auditoria.
    Para obter mais informações, consulte "[Usando a API de log de auditoria](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#using-the-audit-log-api)". +* Configure {% data variables.product.product_name %} para transmitir dados de auditoria enquanto eventos são registrados. -## About audit log streaming +## Sobre a transmissão do log de auditoria -To help protect your intellectual property and maintain compliance for your organization, you can use streaming to keep copies of your audit log data and monitor: +Para ajudar a proteger sua propriedade intelectual e manter a conformidade da sua organização, você pode usar o a transmissão para manter cópias dos seus dados e monitoramento do log de auditoria: {% data reusables.audit_log.audited-data-list %} -The benefits of streaming audit data include: +Os benefícios do streaming de dados de auditoria incluem: -* **Data exploration**. You can examine streamed events using your preferred tool for querying large quantities of data. The stream contains both audit events and Git events across the entire enterprise account. -* **Data continuity**. You can pause the stream for up to seven days without losing any audit data. -* **Data retention**. You can keep your exported audit logs and Git data as long as you need to. +* **Exploração de dados**. Você pode examinar eventos transmitidos usando sua ferramenta preferida para consultar grandes quantidades de dados. A transmissão contém eventos de auditoria e Git em toda a conta corporativa. +* **Continuidade dos dados**. Você pode pausar a transmissão por até sete dias sem perder nenhum dado da auditoria. +* **Retenção de dados**. Você pode manter seus registros de auditoria exportados e dados do Git pelo tempo que precisar. -Enterprise owners can set up, pause, or delete a stream at any time. The stream exports the audit data for all of the organizations in your enterprise. +Os proprietários das empresas podem configurar, pausar ou excluir uma transmissão a qualquer momento. A transmissão exporta os dados de auditoria para todas as organizações da sua empresa. -## Setting up audit log streaming +## Configurando a transmissão do log de auditoria -{% data variables.product.prodname_dotcom %} supports streaming of audit data to either Splunk or Azure Event Hubs. -### Setting up streaming to Splunk +{% data variables.product.prodname_dotcom %} é compatível com a transmissão dos dados de auditoria para Centros de Eventos do Splunk ou do Azure. +### Configurando a transmissão para o Splunk -To stream audit logs to Splunk's HTTP Event Collector (HEC) endpoint you must make sure that the endpoint is configured to accept HTTPS connections. For more information, see the Splunk documentation article "[Set up and use HTTP Event Collector in Splunk Web](https://docs.splunk.com/Documentation/Splunk/latest/Data/UsetheHTTPEventCollector)." +Para transmitir os logs de auditoria para o Coletor de Eventos HTTP (HEC) do Splunk, você deverá garantir que o ponto de extremidade esteja configurado para aceitar conexões HTTPS. Para obter mais informações, consulte o artigo da documentação do Splunk "[Configurar e usar o Coletor de Eventos HTTP na Web do Splunk](https://docs.splunk.com/Documentation/Splunk/latest/Data/UsetheHTTPEventCollector)". {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.audit-log-tab %} -1. Click the **Log streaming** tab. -1. Click **Configure stream** and select **Splunk**. ![Choose Splunk from the drop-down menu](/assets/images/help/enterprises/audit-stream-choice-splunk.png) -1. On the configuration page, enter: - * The domain on which the application you want to stream to is hosted. +1. Clique na aba **Transmissão de log**. +1. Clique **Configurar transmissão** e selecione **Splunk**. ![Escolha Splunk no menu suspenso](/assets/images/help/enterprises/audit-stream-choice-splunk.png) +1. Na página de configuração, insira: + * O domínio para o qual o aplicativo deseja que você transmita está hospedado. - If you are using Splunk Cloud, `Domain` should be `http-inputs-`, where `host` is the domain you use in Splunk Cloud. Por exemplo: `http-inputs-mycompany.splunkcloud.com`. + Se você estiver usando a Nuvem do Splunk, o `Domínio` deverá ser `http-input- http`, em que `host` é o domínio que você usa na nuvem do Splunk. Por exemplo: `http-inputs-mycompany.splunkcloud.com`. - * The port on which the application accepts data.
    + * A porta sobre a qual o aplicativo aceita dados.
    - If you are using Splunk Cloud, `Port` should be `443` if you haven't changed the port configuration. If you are using the free trial version of Splunk Cloud, `Port` should be `8088`. + Se você estiver usando a Nuvem do Splunk, a `Porta` deverá ser `443` se você não mudou a configuração da porta. Se você estiver usando a versão de teste gratuito da Nuvem do Splunk, a `Porta` deverá ser `8088`. - * A token that {% data variables.product.prodname_dotcom %} can use to authenticate to the third-party application. ![Enter stream settings](/assets/images/help/enterprises/audit-stream-add-splunk.png) + * Um token que {% data variables.product.prodname_dotcom %} pode usar para efetuar a autenticação no aplicativo de terceiros. ![Insira as configurações da transmissão](/assets/images/help/enterprises/audit-stream-add-splunk.png) -2. Leave the **Enable SSL verification** check box selected. +2. Deixe a caixa de seleção **Habilitar verificação SSL** marcada. - Audit logs are always streamed as encrypted data, however, with this option selected, {% data variables.product.prodname_dotcom %} verifies the SSL certificate of your Splunk instance when delivering events. SSL verification helps ensure that events are delivered to your URL endpoint securely. You can clear the selection of this option, but we recommend you leave SSL verification enabled. -3. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect to the Splunk endpoint. ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check-splunk.png) -4. After you have successfully verified the endpoint, click **Save**. + Os logs de auditoria são sempre transmitidos como dados criptografados. No entanto, com esta opção selecionada, {% data variables.product.prodname_dotcom %} verifica o certificado SSL da sua instância do Splunk ao realizar os eventos. A verificação SSL ajuda a garantir que os eventos sejam entregues no ponto de extremidade da sua URL de forma segura. Você pode limpar a seleção desta opção, mas recomendamos que saia da verificação SSL habilitada. +3. Clique **Check endpoint** para verificar se {% data variables.product.prodname_dotcom %} pode conectar-se ao ponto de extremidade do Splunk. ![Verificar o ponto de extremidade](/assets/images/help/enterprises/audit-stream-check-splunk.png) +4. Depois de verificar com sucesso o ponto de extremidade, clique em **Salvar**. -### Setting up streaming to Azure Event Hubs +### Configurando a transmissão para os Centros de Evento do Azure -Before setting up a stream in {% data variables.product.prodname_dotcom %}, you must first have an event hub namespace in Microsoft Azure. Next, you must create an event hub instance within the namespace. You'll need the details of this event hub instance when you set up the stream. For details, see the Microsoft documentation, "[Quickstart: Create an event hub using Azure portal](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-create)." +Antes de configurar uma transmissão em {% data variables.product.prodname_dotcom %}, primeiro você deve ter o namespace do centro de um evento no Microsoft Azure. Em seguida, você deve criar uma instância do centro de um evento dentro do namespace. Você precisará das informações da instância do centro desse evento ao configurar a transmissão. Para obter mais informações, consulte a documentação da Microsoft, "[Início rápido: Criar um centro de eventos usando o portal do Azure](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-create)". -You need two pieces of information about your event hub: its instance name and the connection string. +Você precisa de duas informações sobre seu centro de eventos: o nome da sua instância e a sequência de caracteres de conexão. -**On Microsoft Azure portal**: -1. In the left menu select **Entities**. Then select **Event Hubs**. The names of your event hubs are listed. ![A list of event hubs](/assets/images/help/enterprises/azure-event-hubs-list.png) -1. Make a note of the name of the event hub you want to stream to. -1. Click the required event hub. Then, in the left menu, select **Shared Access Policies**. -1. Select a shared access policy in the list of policies, or create a new policy. ![A list of shared access policies](/assets/images/help/enterprises/azure-shared-access-policies.png) -1. Click the button to the right of the **Connection string-primary key** field to copy the connection string. ![The event hub connection string](/assets/images/help/enterprises/azure-connection-string.png) +**No portal do Microsoft Azure**: +1. No menu à esquerda selecione **Entidades**. Em seguida, selecione **Centros de Eventos**. Os nomes dos centros de eventos serão listados. ![Uma lista de centros de eventos](/assets/images/help/enterprises/azure-event-hubs-list.png) +1. Faça uma observação do nome do centro do evento para o qual você deseja transmitir. +1. Clique no centro de eventos necessário. Em seguida, no menu à esquerda, selecione **Políticas de Acesso Compartilhado**. +1. Selecione uma política de acesso compartilhada na lista de políticas ou crie uma nova política. ![Uma lista de políticas de acesso compartilhadas](/assets/images/help/enterprises/azure-shared-access-policies.png) +1. Clique no botão à direita do campo **Tecla primária da string de conexão** para copiar a string de conexão. ![A string de conexão do centro do evento](/assets/images/help/enterprises/azure-connection-string.png) -**On {% data variables.product.prodname_dotcom %}**: +**Em {% data variables.product.prodname_dotcom %}**: {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.audit-log-tab %} -1. Click the **Log streaming** tab. -1. Click **Configure stream** and select **Azure Event Hubs**. ![Choose Splunk from the drop-down menu](/assets/images/help/enterprises/audit-stream-choice-azure.png) -1. On the configuration page, enter: - * The name of the Azure Event Hubs instance. - * The connection string. ![Enter stream settings](/assets/images/help/enterprises/audit-stream-add-azure.png) -2. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect to the Azure endpoint. ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check-azure.png) -3. After you have successfully verified the endpoint, click **Save**. +1. Clique na aba **Transmissão de log**. +1. Clique **Configurar a transmissão ** e selecione **Centros de Evento do Azure**. ![Escolha Splunk no menu suspenso](/assets/images/help/enterprises/audit-stream-choice-azure.png) +1. Na página de configuração, insira: + * O nome da instância do Centro de Eventos do Azure. + * A string de conexão. ![Insira as configurações da transmissão](/assets/images/help/enterprises/audit-stream-add-azure.png) +2. Clique **Verificar ponto de extremidade** para verificar se {% data variables.product.prodname_dotcom %} pode conectar-se ao ponto de extremidade do Azure. ![Verificar o ponto de extremidade](/assets/images/help/enterprises/audit-stream-check-azure.png) +3. Depois de verificar com sucesso o ponto de extremidade, clique em **Salvar**. -## Pausing audit log streaming +## Pausando a transmissão do log de auditoria -Pausing the stream allows you to perform maintenance on the receiving application without losing audit data. Audit logs are stored for up to seven days on {% data variables.product.product_location %} and are then exported when you unpause the stream. +A pausa da transmissão permite que você execute a manutenção no aplicativo de recebimento sem perder dados de auditoria. Os logs de auditoria são armazenados por até sete dias em {% data variables.product.product_location %} e, em seguida, são exportados quando você suspender a pausa da transmissão. -1. Display the "Log streaming" tab, as described above. -1. Click **Pause stream**. ![Pause the stream](/assets/images/help/enterprises/audit-stream-pause.png) -1. A confirmation message is displayed. Click **Pause stream** to confirm. +1. Exibe a aba "Transmissão de registro", como descrito acima. +1. Clique **Pausar transmissão**. ![Pausar a transmissão](/assets/images/help/enterprises/audit-stream-pause.png) +1. Uma mensagem de confirmação é exibida. Clique **Pausar transmissão** para confirmar. -When the application is ready to receive audit logs again, click **Resume stream** to restart streaming audit logs. +Quando o aplicativo estiver pronto para receber registros de auditoria novamente, clique em **Retomar a transmissão** para reiniciar os logs de auditoria da transmissão. -## Deleting the audit log stream +## Excluindo a transmissão do log de auditoria -1. Display the "Log streaming" tab, as described above. -1. Click **Delete stream**. ![Delete the stream](/assets/images/help/enterprises/audit-stream-delete.png) -2. A confirmation message is displayed. Click **Delete stream** to confirm. +1. Exibe a aba "Transmissão de registro", como descrito acima. +1. Clique **Excluir Transmissão**. ![Excluir a transmissão](/assets/images/help/enterprises/audit-stream-delete.png) +2. Uma mensagem de confirmação é exibida. Clique **Excluir transmissão** para confirmar. diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md index f9acd7a1a3..7f1c14521c 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md @@ -1,6 +1,6 @@ --- title: Convidar pessoas para gerenciar sua empresa -intro: 'You can {% ifversion fpt %}invite people to become enterprise owners or billing managers for{% elsif ghes %}add enterprise owners to{% endif %} your enterprise account. You can also remove enterprise owners {% ifversion fpt %}or billing managers {% endif %}who no longer need access to the enterprise account.' +intro: 'Você pode {% ifversion fpt %}convidar pessoas para se tornarem proprietários corporativos ou gerentes de cobrança para{% elsif ghes %}adicionar proprietários corporativos à conta corporativa{% endif %}. Você também pode remover proprietários corporativos {% ifversion fpt %}ou gerentes de cobrança {% endif %}que não precisam mais de acesso à conta corporativa.' product: '{% data reusables.gated-features.enterprise-accounts %}' permissions: 'Enterprise owners can {% ifversion fpt %}invite other people to become{% elsif ghes %}add{% endif %} additional enterprise administrators.' redirect_from: @@ -18,13 +18,19 @@ topics: shortTitle: Convidar pessoas para gerenciar --- -## About users who can manage your enterprise account +## Sobre os usuários que podem gerenciar a sua conta corporativa {% data reusables.enterprise-accounts.enterprise-administrators %} Para obter mais informações, consulte "[Funções em uma empresa](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise)." {% ifversion ghes %} -If you want to manage owners and billing managers for an enterprise account on {% data variables.product.prodname_dotcom_the_website %}, see "[Inviting people to manage your enterprise](/free-pro-team@latest/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)" in the {% data variables.product.prodname_dotcom_the_website %} documentation. +Se você deseja gerenciar os proprietários e gerentes de cobrança para uma conta corporativa em {% data variables.product.prodname_dotcom_the_website %}, consulte "[Convidando pessoas para gerenciar sua empresa](/free-pro-team@latest/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)" na documentação do {% data variables.product.prodname_dotcom_the_website %}. + +{% endif %} + +{% ifversion fpt %} + +Se sua empresa usa {% data variables.product.prodname_emus %}, os proprietários da empresa só poderão ser adicionados ou removidos por meio do seu provedor de identidade. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." {% endif %} @@ -34,18 +40,18 @@ If you want to manage owners and billing managers for an enterprise account on { {% endtip %} -## {% ifversion fpt %}Inviting{% elsif ghes %}Adding{% endif %} an enterprise administrator to your enterprise account +## {% ifversion fpt %}Convidando{% elsif ghes %}adicionando{% endif %} um administrador corporativo à sua conta corporativa -{% ifversion fpt %}After you invite someone to join the enterprise account, they must accept the emailed invitation before they can access the enterprise account.{% endif %} +{% ifversion fpt %}Depois de convidar alguém para juntar-se à conta corporativa, a pessoa deverá aceitar o convite por e-mail antes que possa acessar a conta corporativa.{% endif %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.people-tab %} 1. Na barra lateral esquerda, clique em **Administrators** (Administradores). ![Aba Administrators (Administradores) na barra lateral esquerda](/assets/images/help/business-accounts/administrators-tab.png) -1. Above the list of administrators, click {% ifversion fpt %}**Invite admin**{% elsif ghes %}**Add owner**{% endif %}. +1. Acima da lista de administradores, clique em {% ifversion fpt %}**Convidar administrador**{% elsif ghes %}**Add proprietário**{% endif %}. {% ifversion fpt %} - !["Invite admin" button above the list of enterprise owners](/assets/images/help/business-accounts/invite-admin-button.png) + ![Botão "Convidar administrador" acima da lista de proprietários corporativos](/assets/images/help/business-accounts/invite-admin-button.png) {% elsif ghes %} - !["Add owner" button above the list of enterprise owners](/assets/images/help/business-accounts/add-owner-button.png) + ![Botão "Adicionar o proprietário" acima da lista de proprietários corporativos](/assets/images/help/business-accounts/add-owner-button.png) {% endif %} 1. Digite o nome de usuário, nome completo ou endereço de e-mail da pessoa que você quer convidar para ser um administrador corporativo e depois selecione a pessoa adequada a partir dos resultados. ![Modal box with field to type a person's username, full name, or email address, and Invite button](/assets/images/help/business-accounts/invite-admins-modal-button.png){% ifversion fpt %} 1. Selecione **Owner** (Proprietário) ou **Billing Manager** (Gerente de cobrança). ![Caixa de diálogo modal com opções de funções](/assets/images/help/business-accounts/invite-admins-roles.png) @@ -58,10 +64,10 @@ Somente proprietários corporativos podem remover outros administradores corpora {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.people-tab %} -1. Next to the username of the person you'd like to remove, click {% octicon "gear" aria-label="The Settings gear" %}, then click **Remove owner**{% ifversion fpt %} or **Remove billing manager**{% endif %}. +1. Ao lado do nome de usuário da pessoa que você deseja remover, clique em {% octicon "gear" aria-label="The Settings gear" %} e, em seguida, clique em **Remover proprietário**{% ifversion fpt %} ou **Remover gerente de cobrança**{% endif %}. {% ifversion fpt %} ![Ajuste de configurações com menu option (opções) para remover um administrador corporativo](/assets/images/help/business-accounts/remove-admin.png) {% elsif ghes %} ![Ajuste de configurações com menu option (opções) para remover um administrador corporativo](/assets/images/help/business-accounts/ghes-remove-owner.png) {% endif %} -1. Read the confirmation, then click **Remove owner**{% ifversion fpt %} or **Remove billing manager**{% endif %}. +1. Leia a confirmação, clique **Remover proprietário**{% ifversion fpt %} ou **Remover gerente de cobrança**{% endif %}. diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md index aa0f7b18a1..99a00f48ac 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md @@ -27,8 +27,8 @@ Os proprietários das empresas e os gerentes de cobrança têm automaticamente d {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} 3. Em "Configurações", clique em **Suporte**. ![Item do Menu Suporte](/assets/images/help/enterprises/settings-support.png) -4. Em "Adicionar integrante de suporte", comece a digitar o nome ou nome de usuário da pessoa que você deseja conceder o direito de suporte. Clique no nome deles na lista de correspondência. ![Add support entitlement search](/assets/images/help/enterprises/settings-support-entitlement-search.png) -5. Clique em **Adicionar direito de suporte**. ![Add support entitlement button](/assets/images/help/enterprises/settings-support-add-entitlement.png) +4. Em "Adicionar integrante de suporte", comece a digitar o nome ou nome de usuário da pessoa que você deseja conceder o direito de suporte. Clique no nome deles na lista de correspondência. ![Adicionar suporte a pesquisa titularidade](/assets/images/help/enterprises/settings-support-entitlement-search.png) +5. Clique em **Adicionar direito de suporte**. ![Adicionar botão de titularidade de suporte](/assets/images/help/enterprises/settings-support-add-entitlement.png) ## Removendo o direito de suporte de um integrante da empresa diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise.md index ce94c26dc9..83fe3b99ff 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise.md @@ -21,7 +21,14 @@ Todas as pessoas em uma empresa são integrantes da empresa. Você também pode {% data reusables.enterprise-accounts.enterprise-administrators %} -Para mais informações sobre como adicionar pessoas à sua empresa, consulte "{% ifversion fpt %}[Convidar pessoas para gerenciar a sua empresa](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise){% else %}[Autenticação](/admin/authentication){% endif %}". +{% ifversion fpt %} +Se sua empresa não usar {% data variables.product.prodname_emus %}, você poderá convidar alguém para uma função administrativa usando uma conta de usuário em {% data variables.product.product_name %} que ele controle. Para obter mais informações, consulte[Convidando pessoas para gerenciar a sua empresa](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)". + +Em uma empresa que usa {% data variables.product.prodname_emus %}, novos proprietários e integrantes devem ser fornecidos por meio de seu provedor de identidade. Os proprietários corporativos e proprietários da organização não podem adicionar novos integrantes ou proprietários à empresa usando {% data variables.product.prodname_dotcom %}. É possível selecionar a função corporativa do integrante usando seu IdP e este não pode ser alterado em {% data variables.product.prodname_dotcom %}. Você pode selecionar a função de um integrante em uma organização em {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." +{% else %} +Para obter mais informações sobre como adicionar pessoas à sua empresa, consulte "[Autenticação](/admin/authentication)". + +{% endif %} ## Proprietário corporativo diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md index 05e2066c4d..be58d5b32c 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md @@ -18,18 +18,13 @@ shortTitle: Visualizar & gerenciar acesso SAML Ao ativar o logon único do SAML para a sua conta corporativa, cada integrante da empresa pode vincular sua identidade externa no seu provedor de identidade (IdP) à sua conta de {% data variables.product.product_name %} existente. {% data reusables.saml.about-saml-access-enterprise-account %} +Se sua empresa usar {% data variables.product.prodname_emus %}, seus integrantes usarão contas fornecidas por meio de seu IdP. {% data variables.product.prodname_managed_users_caps %} não usará a sua conta de usuário existente em {% data variables.product.product_name %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." + ## Visualizar e revogar uma identidade vinculada {% data reusables.saml.about-linked-identities %} -{% warning %} - -**Aviso:** Para organizações que usam SCIM: -- A revogação de uma identidade de usuário vinculada em {% data variables.product.product_name %} também removerá os metadados SAML e SCIM. Como resultado, o provedor de identidade não poderá sincronizar ou desprovisionar a identidade do usuário vinculada. -- Um administrador deverá revogar uma identidade vinculada por meio do provedor de identidade. -- Para revogar uma identidade vinculada e vincular uma conta diferente por meio do provedor de identidade, um administrador pode remover e reatribuir o usuário ao aplicativo de {% data variables.product.product_name %}. Para obter mais informações, consulte a documentação do seu provedor de identidade. - -{% endwarning %} +Se o a sua empresa usar {% data variables.product.prodname_emus %}, você não poderá cancelar o provisionamento ou remover contas de usuário da empresa em {% data variables.product.product_name %}. Todas as alterações necessárias a fazer no {% data variables.product.prodname_managed_users %} da sua empresa devem ser feitas por meio do seu IdP. {% data reusables.identity-and-permissions.revoking-identity-team-sync %} diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts.md index 6af00ea4cd..34c7f9da8d 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts.md @@ -1,6 +1,6 @@ --- title: Sobre contas corporativas -intro: 'With {% data variables.product.product_name %}, you can use an enterprise account to {% ifversion fpt %}enable collaboration between your organizations, while giving{% elsif ghes or ghae %}give{% endif %} administrators a single point of visibility and management.' +intro: 'Com {% data variables.product.product_name %}, você pode usar uma conta corporativa para {% ifversion fpt %}habilitar a colaboração entre suas organizações, dando{% elsif ghes or ghae %}dando{% endif %} aos administradores um ponto único de visibilidade e gestão.' product: '{% data reusables.gated-features.enterprise-accounts %}' redirect_from: - /articles/about-github-business-accounts/ diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md new file mode 100644 index 0000000000..f21b5338a8 --- /dev/null +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md @@ -0,0 +1,84 @@ +--- +title: Sobre usuários gerenciados pela empresa +shortTitle: Sobre usuários gerenciados +intro: 'Você pode gerenciar centralmente a identidade e o acesso dos integrantes da empresa em {% data variables.product.prodname_dotcom %} a partir do seu provedor de identidade.' +product: '{% data reusables.gated-features.emus %}' +redirect_from: + - /early-access/github/articles/get-started-with-managed-users-for-your-enterprise +versions: + fpt: '*' +topics: + - Accounts + - Enterprise +--- + +## Sobre o {% data variables.product.prodname_emus %} + +Com {% data variables.product.prodname_emus %}, você pode controlar as contas de usuário dos integrantes da empresa por meio do provedor de identidade (IdP). Você pode simplificar a autenticação com o logon único SAML (SSO) e provisionar atualizar e cancelar o provisionamento das contas de usuário para os membors da sua empresa. Os usuários atribuídos ao aplicativo {% data variables.product.prodname_emu_idp_application %} no seu IdP são provisionados como novas contas de usuário em {% data variables.product.prodname_dotcom %} e adicionados à sua empresa. Você controla nomes de usuários, dados de perfil, associação de equipe e acesso ao repositório a partir do seu IdP. + +No seu IdP, você pode dar a cada {% data variables.product.prodname_managed_user %} a função do proprietário da empresa, usuário ou gerente de cobrança. {% data variables.product.prodname_managed_users_caps %} pode possuir organizações dentro da sua empresa e pode adicionar outros {% data variables.product.prodname_managed_users %} às organizações e equipes internamente. Para obter mais informações, consulte "[Funções em uma empresa](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" e "[Sobre as organizações](/organizations/collaborating-with-groups-in-organizations/about-organizations)". + +Você também pode gerenciar a associação à equipe de uma organização na sua empresa diretamente por meio do seu IdP, permitindo que você gerencie o acesso ao repositório usando grupos no seu IdP. Os integrantes da organização podem ser gerenciados manualmente ou atualizados automaticamente pois {% data variables.product.prodname_managed_users %} são adicionados às equipes da organização. Para obter mais informações, consulte "[Gerenciar associações de equipe com grupos de provedor de identidade](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)". + +Você pode conceder {% data variables.product.prodname_managed_users %} acesso e a capacidade de contribuir para repositórios na sua empresa, mas {% data variables.product.prodname_managed_users %} não pode criar conteúdo público ou colaborar com outros usuários, organizações e empresas no resto de {% data variables.product.prodname_dotcom %}. O {% data variables.product.prodname_managed_users %} provisionado para sua empresa não pode ser convidado para organizações ou repositórios fora da empresa, nem {% data variables.product.prodname_managed_users %} pode ser convidado para outras empresas. Os colaboradores externos não são compatíveis com {% data variables.product.prodname_emus %}. + +Os nomes de usuário do {% data variables.product.prodname_managed_users %} da empresa e as suas informações de perfil como, por exemplo, nomes de exibição e endereços de e-mail, são definidos por meio do seu IdP e não podem ser alterados pelos próprios usuários. Para obter mais informações, consulte "[Nomes de usuário e informações do perfil](#usernames-and-profile-information)". + +{% data reusables.enterprise-accounts.emu-forks %} + +Os proprietários de empresas podem auditar todas as ações de {% data variables.product.prodname_managed_users %}' em {% data variables.product.prodname_dotcom %}. + +Para usar {% data variables.product.prodname_emus %}, você precisa de um tipo de conta corporativa separado com {% data variables.product.prodname_emus %} habilitado. Para obter mais informações sobre a criação desta conta, consulte "[Sobre empresas com usuários gerenciados](#about-enterprises-with-managed-users)". + + +## Suporte do provedor de identidade + +{% data variables.product.prodname_emus %} é compatível com os seguintes IdPs: + +{% data reusables.enterprise-accounts.emu-supported-idps %} + +## Habilidades e restrições de {% data variables.product.prodname_managed_users %} + +O {% data variables.product.prodname_managed_users_caps %} só pode contribuir para repositórios privados e internos da sua empresa e repositórios privados pertencentes à sua conta de usuário. {% data variables.product.prodname_managed_users_caps %} tem acesso somente leitura a toda a comunidade de {% data variables.product.prodname_dotcom %} em geral. + +* {% data variables.product.prodname_managed_users_caps %} não pode criar problemas ou pull requests, comentar ou adicionar reações, nem estrelas, inspeção ou repositórios de bifurcação fora da empresa. +* {% data variables.product.prodname_managed_users_caps %} não pode fazer push de código para repositórios fora da empresa. +* {% data variables.product.prodname_managed_users_caps %} e o conteúdo que criaa é visível apenas para outros integrantes da empresa. +* {% data variables.product.prodname_managed_users_caps %} não pode seguir os usuários fora da empresa. +* {% data variables.product.prodname_managed_users_caps %} não pode criar gists ou comentários em gists. +* {% data variables.product.prodname_managed_users_caps %} não pode instalar {% data variables.product.prodname_github_apps %} nas suas contas de usuário. +* Outros usuários de {% data variables.product.prodname_dotcom %} não podem ver, mencionar ou convidar um {% data variables.product.prodname_managed_user %} para colaborar. +* {% data variables.product.prodname_managed_users_caps %} só pode criar repositórios privados e {% data variables.product.prodname_managed_users %} só pode convidar outros integrantes da empresa para colaborar nos seus próprios repositórios. +* Apenas repositórios privados e internos podem ser criados em organizações pertencentes a um {% data variables.product.prodname_emu_enterprise %}, dependendo das configurações de visibilidade da organização e do repositório corporativo. + +## Sobre empresas com usuários gerenciados + +Para usar {% data variables.product.prodname_emus %}, você precisa de um tipo de conta corporativa separado com {% data variables.product.prodname_emus %} habilitado. Para experimentar {% data variables.product.prodname_emus %} ou para discutir opções para a migração da sua empresa existente, entre em contato com a [Equipe de vendas de {% data variables.product.prodname_dotcom %}](https://enterprise.github.com/contact). + +Seu contato na equipe do GitHub de vendas vai trabalhar com você para criar seu novo {% data variables.product.prodname_emu_enterprise %}. Você deverá fornecer o endereço de e-mail para o usuário que irá configurar sua empresa e um código curto que será usado como sufixo para os nomes de usuários da sua empresa. {% data reusables.enterprise-accounts.emu-shortcode %} Para obter mais informações, consulte "[Nomes de usuário e informações do perfil](#usernames-and-profile-information)" + +Após criarmos sua empresa, você receberá um e-mail de {% data variables.product.prodname_dotcom %} convidando você a escolher uma senha para o usuário de configuração da sua empresa, que será o primeiro proprietário da empresa. O usuário de configuração é usado apenas para configurar o logon único SAML e o provisionamento do SCIM para a empresa. Ele não terá mais acesso para administrar a conta corporativa assim que o SAML for habilitado com sucesso. + +O nome do usuário de configuração é o código curto da sua empresa com o sufixo `_admin`. Depois de efetuar o login no seu usuário de configuração, você pode começar configurando o SAML SSO para a sua empresa. Para obter mais informações, consulte "[Configurando o logon único SAML para Usuários Gerenciados pela Empresa](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." + +{% note %} + +{% data reusables.enterprise-accounts.emu-password-reset-session %} + +{% endnote %} + +## Efetuar a autenticação um {% data variables.product.prodname_managed_user %} + +{% data variables.product.prodname_managed_users_caps %} deve efetuar a autenticação por meio de seu provedor de identidade. + +Para efetuar a autenticação, {% data variables.product.prodname_managed_users %} deverá acessar o portal do aplicativo do IdP ou **https://github.com/enterprises/ENTERPRISE_NAME**, substituindo **ENTERPRISE_NAME** pelo nome da sua empresa. + +## Nome de usuário e informações de perfil + +Quando o seu {% data variables.product.prodname_emu_enterprise %} for criado, você escolherá um código curto que será usado como sufixo para os nomes de usuários da sua empresa. {% data reusables.enterprise-accounts.emu-shortcode %} O usuário configurado que configurar o SAML SSO terá um nome de usuário no formato de **@SHORT-CODE_admin**. + +Ao fornecer um novo usuário a partir do provedor de identidade, o novo {% data variables.product.prodname_managed_user %} terá um nome de usuário de {% data variables.product.product_name %} no formato de **@IDP-USERNAME_SHORT-CODE**. Ao usar o Diretório Ativo do Azure (Azure AD), _IDP-USERNAME_ é formado, normalizando os caracateres anteriores ao caractere `@` no UPN (Nome Principal do usuário) fornecido pelo Azure AD. Ao usar o Okta, o _IDP-USERNAME_ é o atributo de nome de usuário normalizado fornecido pelo Okta. + +O nome de usuário da nova conta provisionada em {% data variables.product.product_name %}, incluindo sublinhado e código curto, não deverá exceder 39 caracteres. + +O nome do perfil e endereço de email de um {% data variables.product.prodname_managed_user %} também é fornecido pelo IdP. {% data variables.product.prodname_managed_users_caps %} não pode alterar seu nome de perfil ou endereço de e-mail em {% data variables.product.prodname_dotcom %}. diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/auditing-activity-in-your-enterprise.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/auditing-activity-in-your-enterprise.md new file mode 100644 index 0000000000..5924ca3a75 --- /dev/null +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/auditing-activity-in-your-enterprise.md @@ -0,0 +1,32 @@ +--- +title: Atividade de auditoria na sua empresa +shortTitle: Atividade de auditoria +intro: 'Você pode auditar a atividade do {% data variables.product.prodname_managed_users %} na sua empresa, visualizar informações sobre quais ações foram realizadas, por qual usuário e quando elas ocorreram.' +permissions: Enterprise owners can access the audit log. +product: '{% data reusables.gated-features.emus %}' +versions: + fpt: '*' +topics: + - Accounts + - Enterprise +--- + +## Sobre o log de auditoria + +O log de auditoria permite que os proprietários corporativos revisem ou exportem rapidamente as ações realizadas por proprietários e integrantes da sua empresa. Cada entrada do log de auditoria mostra informações sobre o evento. + +- A organização em que foi executada uma ação +- O usuário que executou a ação +- Em qual repositório uma ação foi executada +- A ação que foi executada +- Em que país a ação foi executada +- A data e a hora que a ação foi executada + +## Acessar o log de auditoria + +Você também pode acessar o log de auditoria da sua empresa a partir da API REST. Para obter mais informações, consulte "[Administração do GitHub Enterprise](/rest/reference/enterprise-admin#get-the-audit-log-for-an-enterprise)" na documentação da API. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.audit-log-tab %} +1. Opcionalmente, acima da lista de eventos, selecione o menu suspenso **Exportar Eventos do Git** ou **Exportar** e escolha opções para exportar eventos do log de auditoria. ![Os menus suspensos "Exportar eventos do Git" e "Exportar" para o log de auditoria da empresa](/assets/images/help/enterprises/audit-log-export-drop-down-menus.png) diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users.md new file mode 100644 index 0000000000..c9378f505b --- /dev/null +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users.md @@ -0,0 +1,109 @@ +--- +title: Configurar o logon único SAML para usuários gerenciados pela empresa +shortTitle: SAML para usuários gerenciados +intro: 'Pode gerenciar automaticamente o acesso à sua conta corporativa em {% data variables.product.prodname_dotcom %} configurando o logon único SAML (SSO) da Linguagem de Markup de Declaração de Segurança.' +product: '{% data reusables.gated-features.emus %}' +versions: + fpt: '*' +topics: + - Accounts + - Enterprise +--- + +## Sobre o logon único SAML para {% data variables.product.prodname_emus %} + +Com {% data variables.product.prodname_emus %}, a sua empresa usa o SAML SSO para autenticar todos os integrantes. Ao invés de efetuar o login em {% data variables.product.prodname_dotcom %} com um nome de usuário e senha {% data variables.product.prodname_dotcom %}, os integrantes da sua empresa efetuarão o login por meio do seu IdP. + +{% data variables.product.prodname_emus %} é compatível com os seguintes IdPs: + +{% data reusables.enterprise-accounts.emu-supported-idps %} + +Depois de configurar o SAM SSO, recomendamos armazenar seus códigos de recuperação para que você possa recuperar o acesso à sua empresa no caso de o seu provedor de identidade não estar disponível. Para obter mais informações, consulte[Salvando seus códigos de recuperação](#saving-your-recovery-codes)". + +## Configurando o logon único da SAML para {% data variables.product.prodname_emus %} + +Para configurar o SAML SSO para o seu {% data variables.product.prodname_emu_enterprise %}, configure um aplicativo no seu IdP e, em seguida, configure a sua empresa no GitHub.com. Depois de configurar o SAML SSO, você poderá configurar o provisionamento de usuários. + +Para instalar e configurar o aplicativo {% data variables.product.prodname_emu_idp_application %} no seu IdP, você deve ter acesso a de inquilino e acesso administrativo em um IdP compatível. + +{% note %} + +{% data reusables.enterprise-accounts.emu-password-reset-session %} + +{% endnote %} + +1. [Configurando seu provedor de identidade](#configuring-your-identity-provider) +2. [Configurar a sua empresa](#configuring-your-enterprise) +3. [Habilitando o provisionamento](#enabling-provisioning) + +### Configurando seu provedor de identidade + +Para configurar seu IdP, siga as instruções fornecidas para configurar o aplicativo de {% data variables.product.prodname_emu_idp_application %} no seu IdP. + +1. Para instalar o aplicativo {% data variables.product.prodname_emu_idp_application %}, clique no link para acessar o seu IdP abaixo: + + - [Aplicativo de {% data variables.product.prodname_emu_idp_application %} Diretório Ativo do Azure](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/aad.githubenterprisemanageduser?tab=Overview) + - [Alicativo de {% data variables.product.prodname_emu_idp_application %} no Okta](https://www.okta.com/integrations/github-enterprise-managed-user) + +1. Para configurar o aplicativo de {% data variables.product.prodname_emu_idp_application %} e seu IdP, clique no link abaixo e siga as instruções fornecidas pelo seu IdP: + + - [Tutorial do Diretório Ativo do Azure para {% data variables.product.prodname_emus %}](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-enterprise-managed-user-tutorial) + - [Documentação do Okta para {% data variables.product.prodname_emus %}](https://saml-doc.okta.com/SAML_Docs/How-to-Configure-SAML-2.0-for-GitHub-Enterprise-Managed-User.html) + +1. Dessa forma, você pode testar e configurar a sua empresa, atribuir a si mesmo ou o usuário que irá configurar o SAML SSO em {% data variables.product.prodname_dotcom %} para a o aplicativo de {% data variables.product.prodname_emu_idp_application %} no seu IdP. + +1. Para permitir que você continue configurando sua empresa em {% data variables.product.prodname_dotcom %}, localize e observe as informações a seguir do aplicativo que você instalou no seu IdP: + + | Valor | Outros nomes | Descrição | + |:----------------------------------------------- |:------------------- |:---------------------------------------------------------------------------- | + | IdP Sign-On URL | Login URL, IdP URL | URL do aplicativo no seu IdP | + | IdP Identifier URL | Emissor | Identificador de o IdP para prestadores de serviço para autenticação do SAML | + | Certificado de assinatura, codificado em Base64 | Certificado público | Certificado público que o IdP usa para assinar solicitações de autenticação | + +### Configurar a sua empresa + +Após instalar e configurar o aplicativo de {% data variables.product.prodname_emu_idp_application %} no seu provedor de identidade, você poderá configurar a sua empresa. + +1. Efetue o login em {% data variables.product.prodname_dotcom_the_website %} como usuário de configuração da sua nova empresa com o nome de usuário **@SHORT-CODE_admin**. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} + +1. Em "Logon único SAML", selecione **Exigir autenticação do SAML**. ![Caixa de seleção para habilitar SAML SSO](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) + +1. Em **URL de Login**, digite o ponto de extremidade HTTPS do seu IdP para solicitações de logon único que você tenha notado durante a configuração do seu IdP. ![Campo referente à URL para a qual os integrantes serão encaminhados ao entrarem](/assets/images/help/saml/saml_sign_on_url_business.png) + +1. Em **Emissor**, digite a URL do emissor do SAML que você notou durante a configuração do seu IdP para verificar a autenticidade das mensagens enviadas. ![Campo referente ao nome do emissor de SAML](/assets/images/help/saml/saml_issuer.png) + +1. Em **de Certificado Público**, cole o certificado que você anotou durante a configuração do seu IdP, para verificar as respostas do SAML. ![Campo referente ao certificado público do seu provedor de identidade](/assets/images/help/saml/saml_public_certificate.png) + +1. Para verificar a integridade das solicitações do emissor de SAML, clique em {% octicon "pencil" aria-label="The edit icon" %}. Em seguida, no menu suspenso "Método de assinatura" e "Método de resumo", escolha o algoritmo de hashing usado pelo seu emissor do SAML. ![Menus suspensos Signature Method (Método de assinatura) e Digest Method (Método de compilação) para os algoritmos de hash usados pelo emissor de SAML](/assets/images/help/saml/saml_hashing_method.png) + +1. Antes de habilitar o SAML SSO para a sua empresa, para garantir que a informação inserida está correta, clique em **Testar configuração do SAML**. ![Botão para testar a configuração de SAML antes da aplicação](/assets/images/help/saml/saml_test.png) + +1. Clique em **Salvar**. + + {% note %} + + **Observação:** Quando você exige o SAML SSO para a sua empresa, o usuário de configuração não terá mais acesso à empresa, mas permanecerá conectado ao GitHub. Apenas {% data variables.product.prodname_managed_users %} provisionados pelo seu IdP terão acesso à empresa. + + {% endnote %} + +1. Para garantir que você ainda pode acessar a sua empresa no caso de o seu provedor de identidade ficar indisponível no futuro clique em **Download**, **Imprimir** ou **Copiar** para salvar seus códigos de recuperação. ![Botão para testar a configuração de SAML antes da aplicação](/assets/images/help/saml/saml_recovery_code_options.png) + +### Habilitando o provisionamento + +Depois que você habilitar o SAML SSO, habilite o provisionamento. Para obter mais informações, consulte "[Configurando o provisionamento de SCIM para usuários gerenciados pela empresa](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users)". + +## Salvando os seus códigos de recuperação + +Caso o seu provedor de identidade esteja indisponível, você poderá usar o usuário de configuração e um código de recuperação para entrar e acessar a sua empresa. Se você não salvou seus códigos de recuperação ao configurar SAML SSO, você ainda poderá acessá-los nas configurações da sua empresa. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} + +1. Em "Exigir autenticação do SAML", clique em **Salvar seus códigos de recuperação**. ![Botão para testar a configuração de SAML antes da aplicação](/assets/images/help/enterprises/saml-recovery-codes-link.png) + +2. Para salvar seus códigos de recuperação, clique em **Download**, **Imprimir**ou **Copiar**. ![Botão para testar a configuração de SAML antes da aplicação](/assets/images/help/saml/saml_recovery_code_options.png) diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md new file mode 100644 index 0000000000..16fe39d78c --- /dev/null +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md @@ -0,0 +1,76 @@ +--- +title: Configurando o provisionamento do SCIM para usuários gerenciados pela empresa com Okta +shortTitle: Configurar provisionamento com Okta +intro: Você pode fornecer novos usuários e gerenciar os integrantes da sua empresa e das equipes usando o Okta como seu provedor de identidade. +product: '{% data reusables.gated-features.emus %}' +versions: + fpt: '*' +redirect_from: + - /early-access/github/articles/configuring-provisioning-for-managed-users-with-okta +topics: + - Accounts + - Enterprise +--- + +## Sobre o provisionamento com Okta + +Você pode usar {% data variables.product.prodname_emus %} com o Okta como seu provedor de identidade para fornecer novas contas, gerenciar a associação da empresa e gerenciar as associações das equipes para as organizações na sua empresa. Para obter mais informações sobre provisionamento para {% data variables.product.prodname_emus %}, consulte "[Configurando provisionamento de SCIM para usuários corporativos gerenciados](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users)". + +Antes de configurar o provisionamento com o Okta, você deverá configurar o logon único SAML. Para obter mais informações, consulte "[Configurando o logon único SAML para Usuários Gerenciados pela Empresa](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." + +Para configurar o provisionamento com o Okta, você deverá definir o nome da sua empresa no aplicativo {% data variables.product.prodname_emu_idp_application %} e inserir o token de acesso pessoal do seu usuário. Em seguida, você poderá começar a provisionar usuários no Okta. + +## Funcionalidades compatíveis + +{% data variables.product.prodname_emus %} é compatível com muitas funcionalidades no Okta. + +| Funcionalidade | Descrição | +| ------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Fazer push de novos usuários | Os usuários atribuídos ao aplicativo de {% data variables.product.prodname_emu_idp_application %} no Okta são automaticamente criados na empresa em {% data variables.product.product_name %}. | +| Fazer push da atualização do perfil | As atualizações feitas no perfil do usuário no Okta serão enviadas por push para {% data variables.product.product_name %}. | +| Grupos de Push | Os grupos no Okta atribuídos ao aplicativo de {% data variables.product.prodname_emu_idp_application %} como os Grupos Push são criados automaticamente na empresa em {% data variables.product.product_name %}. | +| Fazer push de desativações de usuário | Cancelar a atribuição do usuário do aplicativo de {% data variables.product.prodname_emu_idp_application %} no Okta irá desabilitar o usuário em {% data variables.product.product_name %}. O usuário não poderá efetuar o login, mas as informações do usuário serão mantidas. | +| Reativar usuários | Os Usuários do Okta cujas contas do Okta são reativadas e atribuídas de volta ao aplicativo de {% data variables.product.prodname_emu_idp_application %} serão habilitados. | + +{% note %} + +**Observação:** {% data variables.product.prodname_emus %} não é compatível com modificações em nomes de usuário. + +{% endnote %} + +## Configurando o nome da sua empresa + +Após a criação do seu {% data variables.product.prodname_emu_enterprise %}, você poderá começar a configurar o provisionamento definindo o nome da sua empresa no Okta. + +1. Acesse o seu aplicativo de{% data variables.product.prodname_emu_idp_application %} no Okta. +1. Clique na aba **Login**. +1. Para fazer as alterações, clique em **Editar**. +1. Em "Configurações Avançadas de Login", na caixa de texto "Nome da empresa", digite o nome da sua empresa. Por exemplo, se você acessar sua empresa em `https://github.com/enterprises/octoinc`, o nome da sua empresa seria "octoinc". ![Captura de tela do campo nome da empresa no Okta](/assets/images/help/enterprises/okta-emu-enterprise-name.png) +1. Para salvar o nome da empresa, clique em **Salvar**. + +## Configurando o provisionamento + +Após definir o nome da sua empresa, você poderá prosseguir para definir as configurações de provisionamento. + +Para configurar o provisionamento, o usuário configurado com o nome de usuário **@SHORT-CODE_admin** deverá fornecer um token de acesso pessoal com o escopo **admin:enterprise**. Para obter mais informações sobre como criar um novo token, consulte "[Criar um token de acesso pessoal](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users#creating-a-personal-access-token)." + +1. Acesse o seu aplicativo de{% data variables.product.prodname_emu_idp_application %} no Okta. +1. Clique na aba **Orovisionamento**. +1. No menu de configurações, clique em **Integração**. +1. Para fazer as alterações, clique em **Editar**. +1. Selecione **Habilitar a integração da API**. +1. No campo "API do Token" insira o token de acesso pessoal com o escopo de administração **admin:enterprise** pertencente ao usuário configurado. ![Captura de tela que mostra o campo do token da API no Okta](/assets/images/help/enterprises/okta-emu-token.png) +1. Clique em **Testar as credenciais da API**. Se o teste for bem sucedido, será exibida uma mensagem de verificação na parte superior da tela. +1. Para salvar o token, clique em **Salvar**. +1. No menu de configurações, clique em **Ao aplicativo**. ![Captura de tela que mostra o item de menu "Ao aplicativo" no Okta](/assets/images/help/enterprises/okta-emu-to-app-menu.png) +1. À direita do "Provisionamento para o aplicativo", para permitir alterações a serem feitas, clique em **Editar**. +1. Selecione **Habilitar** para **Criar usuários**, **Atualizar atributos do usuário** e **Desativar Usuários**. ![Captura de tela que mostra as opções de provisionamento no Okta](/assets/images/help/enterprises/okta-emu-provisioning-to-app.png) +1. Para concluir a configuração do provisionamento, clique em **Salvar**. + +## Atribuindo usuários + +Depois de configurar o SAML SSO e o provisionamento, você poderá fornecer novos usuários no {% data variables.product.prodname_dotcom_the_website %} atribuindo usuários ao aplicativo de {% data variables.product.prodname_emu_idp_application %}. Você também pode gerenciar automaticamente a associação da organização ao atribuir grupos ao aplicativo como grupos de push e conectar os grupos de push às equipes das suas organizações. Para obter mais informações sobre gerenciamento de equipes, consulte "[Gerenciando associações de equipe com grupos de provedores de identidade](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)". + +Ao atribuir aos usuários, você poderá usar o atributo "Funções" no aplicativo de {% data variables.product.prodname_emu_idp_application %} para definir a função de um usuário na sua empresa em {% data variables.product.product_name %}. Para obter mais informações sobre funções, consulte "[Funções em uma empresa](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)". + +![Captura de tela que mostra as opções da função para o usuário provisionado do Okta](/assets/images/help/enterprises/okta-emu-user-role.png) diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md new file mode 100644 index 0000000000..3bf0552aa0 --- /dev/null +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md @@ -0,0 +1,54 @@ +--- +title: Configurando o provisionamento de SCIM para usuários gerenciados pela empresa +shortTitle: Provisionamento de usuários gerenciados +intro: Você pode configurar seu provedor de identidade para fornecer novos usuários e gerenciar seus integrantes na sua empresa e equipes. +product: '{% data reusables.gated-features.emus %}' +versions: + fpt: '*' +topics: + - Accounts + - Enterprise +--- + +## Sobre o provisionamento para {% data variables.product.prodname_emus %} + +Você pode configurar o provisionamento para {% data variables.product.prodname_emus %} para criar, gerenciar e desativar contas de usuário para os integrantes da sua empresa. Ao configurar o provisionamento para {% data variables.product.prodname_emus %}, os usuários atribuídos ao aplicativo de {% data variables.product.prodname_emu_idp_application %} no seu provedor de identidade serão provisionados como novas contas de usuário em {% data variables.product.prodname_dotcom %} por meio do SCIM e os usuários serão adicionados à sua empresa. + +Ao atualizar as informações associadas à identidade de um usuário no seu IdP, este atualizará a conta do usuário no GitHub.com. Quando você cancelar a atribuição do usuário do aplicativo de {% data variables.product.prodname_emu_idp_application %} ou desativar a conta de um usuário no seu IdP, este irá comunicar-se com {% data variables.product.prodname_dotcom %} para invalidar qualquer sessão do SAML e desabilitar a conta do integrante. As informações da conta desativada serão mantidas e seu nome de usuário será alterado para hash do seu nome de usuário original com o código curto anexado. Se você reatribuir um usuário para o aplicativo {% data variables.product.prodname_emu_idp_application %} ou reativar sua conta no seu IdP, a conta de {% data variables.product.prodname_managed_user %} em {% data variables.product.prodname_dotcom %} será reativada e o nome de usuário restaurado. + +Os grupos no seu IdP podem ser usados para gerenciar a participação de equipe nas organizações de sua empresa, permitindo que você configure o acesso e as permissões do repositório por meio do seu IdP. Para obter mais informações, consulte "[Gerenciar associações de equipe com grupos de provedor de identidade](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)". + +## Pré-requisitos + +Antes de configurar o provisionamento para {% data variables.product.prodname_emus %}, você deverá configurar o logon único SAML. Para obter mais informações, consulte "[Configurando o logon único SAML para Usuários Gerenciados pela Empresa](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." + +## Criar um token de acesso pessoal + +Para configurar o provisionamento para o seu {% data variables.product.prodname_emu_enterprise %}, você precisa de um token de acesso pessoal com o escopo **admin:enterprise** que pertence ao usuário configurado. + +{% warning %} + +**Aviso:** Se o token vencer ou um usuário provisionado criar o token, o provisionamento do SCIM poderá parar de funcionar, inesperadamente. Certifique-se de criar o token enquanto estiver conectado como usuário de configuração e que o vencimento do token esteja definido como "Sem vencimento". + +{% endwarning %} + +1. Efetue o login em {% data variables.product.prodname_dotcom_the_website %} como usuário de configuração da sua nova empresa com o nome de usuário **@SHORT-CODE_admin**. +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.developer_settings %} +{% data reusables.user_settings.personal_access_tokens %} +{% data reusables.user_settings.generate_new_token %} +1. Em **Observação**, dê ao seu token um nome descritivo. ![Captura de tela que mostra o nome do token](/assets/images/help/enterprises/emu-pat-name.png) +1. Selecione o menu suspenso **Expiração** e, em seguida, clique **Sem vencimento**. ![Captura de tela que mostra o vencimento do token definido como sem vencimento](/assets/images/help/enterprises/emu-pat-no-expiration.png) +1. Selecione o escopo **admin:enterprise**. ![Captura de tela que mostra o escopo admin:enterprise](/assets/images/help/enterprises/enterprise-pat-scope.png) +1. Clique em **Generate token** (Gerar token). ![Botão Generate token (Gerar token)](/assets/images/help/settings/generate_token.png) +1. Para copiar o token para a área de transferência, clique no {% octicon "paste" aria-label="The copy icon" %}. ![Token recém-criado](/assets/images/help/settings/personal_access_tokens.png) +2. Para salvar o token para usar mais tarde, armazene o novo token de forma segura em um gerenciador de senhas. + +## Configurando provisionamento para {% data variables.product.prodname_emus %} + +Depois de criar seu token de acesso pessoal e armazená-lo com segurança, você pode configurar o provisionamento no seu provedor de identidade. + +Para configurar o Diretório Ativo do Azure para fornecer aos usuários do seu {% data variables.product.prodname_emu_enterprise %}, consulte [Tutorial: Configurar o usuário gerenciado do GitHub Enterprise para provisionamento automático de usuário](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-enterprise-managed-user-provisioning-tutorial) na documentação do Azure AD. + +Para configurar o Okta para prover usuários para seu {% data variables.product.prodname_emu_enterprise %}, consulte "[Configurando o provisionamento de SCIM para Usuários Corporativos Gerenciados com o Okta](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users-with-okta)". + diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/index.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/index.md new file mode 100644 index 0000000000..7f0284133b --- /dev/null +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/index.md @@ -0,0 +1,19 @@ +--- +title: Gerenciando os usuários da sua empresa com seu provedor de identidade +shortTitle: Gerenciar usuários com seu IdP +product: '{% data reusables.gated-features.emus %}' +intro: Você pode gerenciar a identidade e o acesso com o seu provedor de identidade e prover contas que só podem contribuir com para a sua empresa. +versions: + fpt: '*' +topics: + - Enterprise + - Accounts +children: + - /about-enterprise-managed-users + - /configuring-saml-single-sign-on-for-enterprise-managed-users + - /configuring-scim-provisioning-for-enterprise-managed-users + - /configuring-scim-provisioning-for-enterprise-managed-users-with-okta + - /managing-team-memberships-with-identity-provider-groups + - /auditing-activity-in-your-enterprise +--- + diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups.md new file mode 100644 index 0000000000..55704cf517 --- /dev/null +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups.md @@ -0,0 +1,67 @@ +--- +title: Gerenciando associações de equipes com grupos de provedores de identidade +shortTitle: Gerenciar equipes com seu IdP +intro: 'Você pode gerenciar a associação à equipe em {% data variables.product.product_name %} por meio do seu provedor de identidade (IdP) conectando os grupos do IdP ao seu {% data variables.product.prodname_emu_enterprise %}.' +product: '{% data reusables.gated-features.emus %}' +versions: + fpt: '*' +topics: + - Accounts + - Enterprise +--- + +## Sobre o gerenciamento da equipe com {% data variables.product.prodname_emus %} + +Com {% data variables.product.prodname_emus %}, você pode gerenciar a participação em equipe dentro da sua empresa por meio do seu IdP. Quando conectar uma equipe de uma das organizações da sua empresa a um grupo do IdP as alterações nos integrantes do grupo do IdP serão refletidas na sua empresa automaticamente, reduzindo a necessidade de atualizações manuais e scripts personalizados. + +Quando uma alteração em um grupo do IdP ou uma nova conexão de equipe faz com que {% data variables.product.prodname_managed_user %} entre em uma equipe em uma organização da qual já não faz parte, o {% data variables.product.prodname_managed_user %} será adicionado à organização automaticamente. Os proprietários da organização também podem gerenciar a associação da organização manualmente. Ao desconectar um grupo de uma equipe, usuários que se tornaram integrantes da organização por da associação da equipe são removidos da organização se uma associação não lhes for atribuída na organização por outros meios. + +É possível conectar uma equipe da sua empresa a um grupo de IdP. Você pode atribuir o mesmo grupo do IdP a várias equipes na sua empresa. + +Se você estiver conectando uma equipe existente a um grupo de IdP, primeiro você deverá remover todos os integrantes que foram adicionados manualmente. Depois de conectar uma equipe da sua empresa a um grupo do IdP, o administrador do IdP deverá realizar as alterações na associação da equipe por meio do provedor de identidade. Você não pode gerenciar a associação da equipe em {% data variables.product.prodname_dotcom_the_website %}. + +Quando o integrante do grupo mudar no seu IdP, este enviará uma solicitação de SCIM com alterações para {% data variables.product.prodname_dotcom_the_website %} de acordo com o cronograma determinado pelo seu IdP. Portanto, é possível que a alteração não seja imediata. Qualquer solicitação que altere a equipe de equipe ou associação da organização será registrada no log de auditoria como alterações feitas pela conta usada para configurar provisionamento do usuário. + +As quipes conectadas a grupos de IdP não podem ser equipes principais de outras equipes nem uma equipe secundária de outra equipe. Se a equipe que você deseja conectar a um grupo de IdP for uma equipe principal ou secundária recmendamos criar uma nova equipe ou remover a relação aninhada que faças da sua equipe uma equipe principal. + +Para gerenciar o acesso ao repositório para qualquer equipe do seu negócio, incluindo equipes conectadas a um grupo de IdP, você deverá fazer alterações em {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, consulte "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)". + +## Criando uma nova equipe conectada a um grupo de IdP + +Qualquer integrante de uma organização pode criar uma nova equipe e conectar a equipe a um grupo de IdP. + +{% data reusables.profile.access_org %} +{% data reusables.user_settings.access_org %} +{% data reusables.organizations.new_team %} +{% data reusables.organizations.team_name %} +{% data reusables.organizations.team_description %} +1. Para conectar uma equipe, selecione o menu suspenso "Grupos de Fornecedores de Identidade" e clique na equipe que você deseja se conectar. ![Menu suspenso para escolher grupos de provedores de identidade](/assets/images/help/teams/choose-an-idp-group.png) +{% data reusables.organizations.team_visibility %} +{% data reusables.organizations.create_team %} + +## Gerenciando a conexão entre uma equipe existente e um grupo de IdP + +Os proprietários da organização e mantenedores de equipe podem gerenciar a conexão existente entre um grupo de IdP e uma equipe. + +{% note %} + +**Observação**: Antes de conectar uma equipe existente em {% data variables.product.prodname_dotcom_the_website %} a um grupo de IdP pela primeira vez, todos os integrantes da equipe em {% data variables.product.prodname_dotcom_the_website %} devem primeiro ser removidos. Para obter mais informações, consulte "[Removendo integrantes da organização a partir de uma equipe](/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team)." + +{% endnote %} + +{% data reusables.profile.access_profile %} + +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +1. Opcionalmente, em "Grupo de Provedores de Identidade", à direita do grupo do IdP que deseja desconectar, clique em {% octicon "x" aria-label="X symbol" %}. ![Cancelar a seleção de um grupo de IdP conectado da equipe do GitHub](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png) +1. Para conectar um grupo de IdP, em "Grupo de Fornecedores de Identidade", selecione o menu suspenso e clique em um grupo de provedores de identidade da lista. ![Menu suspenso para escolher grupo de provedores de identidade](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png) +1. Clique em **Save changes** (Salvar alterações). + +## Visualizando grupos de IdP e equipes conectadas + +Você pode revisar uma lista de grupos de IdP, todas as equipes conectadas a um grupo de IdP, e ver a associação de cada grupo IdP no {% data variables.product.product_name %}. Você deve editar a associação de um grupo no seu IdP. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.identity-provider-tab %} +1. Em "Grupos de Provedores de Identidade (IdP)", revise a lista de grupos de IdP. diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account.md index dba5b500fc..d7295648be 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account.md @@ -42,7 +42,9 @@ Você pode desabilitar todos os fluxos de trabalho para uma empresa ou definir u ## Configurar a aprovação necessária para fluxos de trabalho de bifurcações públicas -{% data reusables.actions.workflow-run-approve-public-fork %} Você pode configurar esse comportamento para sua empresa seguindo o procedimento abaixo. +{% data reusables.actions.workflow-run-approve-public-fork %} + +You can configure this behavior for your enterprise using the procedure below. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} diff --git a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-repository-management-policies-in-your-enterprise-account.md b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-repository-management-policies-in-your-enterprise-account.md index a12e09b8bb..34c21f4715 100644 --- a/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-repository-management-policies-in-your-enterprise-account.md +++ b/translations/pt-BR/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-repository-management-policies-in-your-enterprise-account.md @@ -17,14 +17,14 @@ shortTitle: Políticas para repositórios Para obter mais informações, consulte "[Níveis de permissão do repositório para organizações](/articles/repository-permission-levels-for-an-organization)". -## Enforcing a policy on base repository permissions +## Aplicar política com base nas permissões do repositório -Across all organizations owned by your enterprise account, you can set a base repository permission level (none, read, write, or admin) for organization members, or allow owners to administer the setting on the organization level. +Em todas as organizações pertencentes à conta corporativa, é possível definir um nível de permissão de base do repositório (nenhum, leitura, gravação ou administrativo) para integrantes da organização ou permitir que os proprietários administrem a configuração no nível da organização. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} -4. On the **Repository policies** tab, under "Base permissions", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} -5. Under "Base permissions", use the drop-down menu and choose a policy. ![Menu suspenso com opções de políticas de permissões de repositório](/assets/images/help/business-accounts/repository-permissions-policy-drop-down.png) +4. Na aba **Políticas do repositório**, em "Permissões básicas", revise as informações sobre como alterar a configuração. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %} +5. Em "Permissões básicas", use o menu suspenso e escolha uma política. ![Menu suspenso com opções de políticas de permissões de repositório](/assets/images/help/business-accounts/repository-permissions-policy-drop-down.png) ## Aplicar política sobre como criar repositórios diff --git a/translations/pt-BR/content/github/site-policy/dmca-takedown-policy.md b/translations/pt-BR/content/github/site-policy/dmca-takedown-policy.md index 7c0f81b37b..6ccff50241 100644 --- a/translations/pt-BR/content/github/site-policy/dmca-takedown-policy.md +++ b/translations/pt-BR/content/github/site-policy/dmca-takedown-policy.md @@ -15,7 +15,7 @@ topics: Bem-vindo ao Guia do GitHub para a Lei dos Direitos Autorais do Milênio Digital, comumente conhecida como "DMCA" - Digital Millenium Copyright Act Policy. Esta página não tem a finalidade de ser uma cartilha abrangente sobre o regimento. No entanto, se você recebeu um aviso de retirada DMCA direcionado ao conteúdo que você postou no GitHub, ou se você é um detentor de direitos que pretende enviar tal aviso, esta página vai ajudá-lo a desmistificar a lei, bem como nossas políticas relacionadas. -(If you just want to submit a notice, you can skip to "[G. Submitting Notices](#g-submitting-notices).") +(Se você quiser apenas enviar uma notificação, você poderá pular para "[G. Enviando avisos](#g-submitting-notices).") Como em todas as questões jurídicas, é sempre melhor consultar um profissional sobre suas dúvidas ou situação específica. Incentivamos a fazê-lo antes de tomar quaisquer medidas que possam impactar seus direitos. Este guia não é um aconselhamento jurídico e não deve ser tomado como tal. @@ -85,7 +85,7 @@ Quando os nossos especialistas determinarem que uma reivindicação é completa, Tenha em mente que o nosso processo de revisão para contornar a tecnologia não se aplica ao conteúdo que, de outra forma, violaria as nossas restrições de uso aceitável da política de compartilhamento de chaves de licenciamento de produtos não autorizadas, software para gerar chaves de licenciamento de produtos não autorizadas ou software para ignorar verificações de chaves de licenciamento de produtos. Embora estes tipos de alegações também possam violar as disposições da DMCA sobre as tecnologias de circunvenção, trata-se de questões tipicamente simples e não justificam uma revisão técnica e jurídica adicional. No entanto, quando a reivindicação não for simples, por exemplo, no caso de infracções, será aplicado o processo de revisão de pedidos de indemnização por tecnologia. -When GitHub processes a DMCA takedown under our circumvention technology claim review process, we will offer the repository owner a referral to receive independent legal consultation through [GitHub’s Developer Defense Fund](https://github.blog/2021-07-27-github-developer-rights-fellowship-stanford-law-school/) at no cost to them. +Quando o GitHub processa um banco de dados do DMCA no nosso processo de análise de tecnologia de circunvenção, nós ofereceremos ao proprietário do repositório uma indicação para receber uma consultoria jurídica independente por meio do do [Fundo de Defesa de Desenvolvedor do GitHub](https://github.blog/2021-07-27-github-developer-rights-fellowship-stanford-law-school/) sem nenhum custo. ## D. E se eu, inadvertidamente, deixar passar o período para fazer as alterações? diff --git a/translations/pt-BR/content/github/site-policy/github-codespaces-privacy-statement.md b/translations/pt-BR/content/github/site-policy/github-codespaces-privacy-statement.md index 580ec9f90b..0437c03400 100644 --- a/translations/pt-BR/content/github/site-policy/github-codespaces-privacy-statement.md +++ b/translations/pt-BR/content/github/site-policy/github-codespaces-privacy-statement.md @@ -1,5 +1,5 @@ --- -title: GitHub Codespaces Privacy Statement +title: Declaração de Privacidade do GitHub Codespaces redirect_from: - /github/site-policy/github-codespaces-privacy-policy versions: @@ -9,14 +9,14 @@ topics: - Legal --- -Effective Date: August 10, 2021 +Data de entrada em vigor: 10 de agosto de 2021 -Use of GitHub Codespaces is subject to the [GitHub Privacy Statement](/github/site-policy/github-privacy-statement). +O uso do GitHub Codespaces está sujeito à [Declaração de Privacidade](/github/site-policy/github-privacy-statement) do GitHub. -Activity on github.dev is subject to [GitHub's Beta Previews terms](/github/site-policy/github-terms-of-service#j-beta-previews) +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) -## Using Visual Studio Code +## Usando o Visual Studio Code -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. +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. -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. +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. diff --git a/translations/pt-BR/content/github/site-policy/github-community-guidelines.md b/translations/pt-BR/content/github/site-policy/github-community-guidelines.md index a7f2b4d63a..0d6c678231 100644 --- a/translations/pt-BR/content/github/site-policy/github-community-guidelines.md +++ b/translations/pt-BR/content/github/site-policy/github-community-guidelines.md @@ -58,7 +58,7 @@ Estamos comprometidos em manter uma comunidade onde os usuários são livres par - #### Interromper a experiência de outros usuários Ser parte de uma comunidade inclui reconhecer como seu comportamento afeta os outros e envolver-se em interações significativas e produtivas com as pessoas e a plataforma de que dependem. Não são permitidos comportamentos como postar repetidamente comentários que fogem ao tópico, abrir problemas ou pull requests vazios ou sem sentido ou usar qualquer recurso de outra plataforma de uma forma que perturbe continuamente a experiência de outros usuários. Embora incentivemos os mantenedores a moderar os seus próprios projetos individualmente, a equipe do GitHub pode ter uma ação restritiva contra contas que estão se envolvendo com esses tipos de comportamento. -- #### Impersonation You may not impersonate another person by copying their avatar, posting content under their email address, using a similar username or otherwise posing as someone else. A falsidade ideológica é uma forma de assédio. +- #### Personificação Você não pode personificar outra pessoa, copiando o seu avatar, postando conteúdo no seu endereço de e-mail e usando um nome de usuário similar ou passar-se por outra pessoa. A falsidade ideológica é uma forma de assédio. - #### Doxxing e invasão de privacidade Não poste informações pessoais de outras pessoas, como endereços de e-mail pessoais e privados, números de telefone, endereços físicos, números de cartão de crédito, números de previdência social/identidade nacional ou senhas. Dependendo do contexto, como no caso de intimidação ou assédio, podemos considerar que outras informações, como fotos ou vídeos que foram tirados ou distribuídos sem o consentimento do indivíduo, constituem invasão da privacidade, especialmente quando esse material representa um risco para a segurança do indivíduo. diff --git a/translations/pt-BR/content/github/site-policy/github-data-protection-agreement.md b/translations/pt-BR/content/github/site-policy/github-data-protection-agreement.md new file mode 100644 index 0000000000..fbb24f902a --- /dev/null +++ b/translations/pt-BR/content/github/site-policy/github-data-protection-agreement.md @@ -0,0 +1,974 @@ +--- +title: GitHub Data Protection Agreement +redirect_from: + - /github/site-policy/github-data-protection-addendum + - /github/site-policy-deprecated/github-data-protection-addendum + - /github/site-policy/github-data-protection-agreement-non-enterprise-customers +versions: + fpt: '*' +--- + +## Introdução + +The parties agree that this GitHub Data Protection Agreement (“**DPA**”) sets forth their obligations with respect to the processing and security of Personal Data and, where explicitly stated in the DPA Terms, Customer Data in connection with the Online Services provided by GitHub, Inc. (“**GitHub**”). The DPA (including its Appendix and Attachments) is between GitHub and any customer receiving Online Services from GitHub based on the GitHub Customer Agreement (“**Customer**”), and is incorporated by reference into the GitHub Customer Agreement. + +In the event of any conflict or inconsistency between the DPA Terms and any other terms in the GitHub Customer Agreement, the DPA Terms will prevail. The provisions of the DPA Terms supersede any conflicting provisions of the GitHub Privacy Statement that otherwise may apply to processing of Personal Data. For clarity, the Standard Contractual Clauses prevail over any other term of the DPA Terms. + +### Applicable DPA Terms and Updates + +#### Limits on Updates + +When Customer renews or purchases a new subscription to an Online Service, the then-current DPA Terms will apply and will not change during the term of that new subscription for that Online Service. + +#### New Features, Supplements, or Related Software + +Notwithstanding the foregoing limits on updates, when GitHub introduces features, supplements or related software that are new (i.e., that were not previously included with the subscription), GitHub may provide terms or make updates to the DPA that apply to Customer’s use of those new features, supplements or related software. If those terms include any material adverse changes to the DPA Terms, GitHub will provide Customer a choice to use the new features, supplements, or related software, without loss of existing functionality of a generally available Online Service. If Customer does not use the new features, supplements, or related software, the corresponding new terms will not apply. + +#### Government Regulation and Requirements + +Notwithstanding the foregoing limits on updates, GitHub may modify or terminate an Online Service in any country or jurisdiction where there is any current or future government requirement or obligation that (1) subjects GitHub to any regulation or requirement not generally applicable to businesses operating there, (2) presents a hardship for GitHub to continue operating the Online Service without modification, and/or (3) causes GitHub to believe the DPA Terms or the Online Service may conflict with any such requirement or obligation. + +### Electronic Notices + +GitHub may provide Customer with information and notices about Online Services electronically, including via email, or through a web site that GitHub identifies. Notice is given as of the date it is made available by GitHub. + +### Prior Versions + +The DPA Terms provide terms for Online Services that are currently available. For earlier versions of the DPA Terms, Customer may contact its reseller or GitHub Account Manager. + +## Definições + +Capitalized terms used but not defined in this DPA will have the meanings provided in the GitHub Customer Agreement. The following defined terms are used in this DPA: + +“**CCPA**” means the California Consumer Privacy Act as set forth in Cal. Civ. Code §1798.100 et seq. and its implementing regulations. + +“**Customer Data**” means all data, including all text, sound, video, or image files, and software, that are provided to GitHub by, or on behalf of, Customer through use of the Online Service. + +“**Data Protection Requirements**” means the GDPR, Local EU/EEA Data Protection Laws, CCPA, and any applicable laws, regulations, and other legal requirements relating to (a) privacy and data security; and (b) the use, collection, retention, storage, security, disclosure, transfer, disposal, and other processing of any Personal Data. + +“**Diagnostic Data**” means data collected or obtained by GitHub from software that is locally installed by Customer in connection with the Online Service. Diagnostic Data may also be referred to as telemetry. Diagnostic Data does not include Customer Data, Service Generated Data, or Professional Services Data. + +“**DPA Terms**” means both the terms in this DPA and any Online Service-specific terms in the GitHub Customer Agreement that specifically supplement or modify the privacy and security terms in this DPA for a specific Online Service (or feature of an Online Service). In the event of any conflict or inconsistency between the DPA and such Online Service-specific terms, the Online Service-specific terms shall prevail as to the applicable Online Service (or feature of that Online Service). + +“**GDPR**” means Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation). In connection with the United Kingdom, “GDPR” means Regulation (EU) 2016/679 as transposed into national law of the United Kingdom by the UK European Union (Withdrawal) Act 2018 and amended by the UK Data Protection, Privacy and Electronic Communications (Amendments etc.) (EU Exit) Regulations 2019 (as may be amended from time to time). + +“**Local EU/EEA Data Protection Laws**” means any subordinate legislation and regulation implementing the GDPR. + +“**GDPR Related Terms**” means the terms in Attachment 3, under which GitHub makes binding commitments regarding its processing of Personal Data as required by Article 28 of the GDPR. + +“**GitHub Affiliate**” means any entity that directly or indirectly controls, is controlled by or is under common control with GitHub. + +“**GitHub Customer Agreement**” means the service or other agreement(s) entered into by Customer with GitHub for Online Services. + +“**GitHub Privacy Statement**” means the GitHub privacy statement available at https://docs.github.com/en/github/site-policy/github-privacy-statement. + +“**Online Service**” means any service or software provided by GitHub to Customer under the GitHub Customer Agreement agreed upon with Customer, including Previews, updates, patches, bug fixes, and technical support. + +“**Personal Data**” means any information relating to an identified or identifiable natural person. An identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person. + +“**Preview**” means Online Services provided for preview, evaluation, demonstration or trial purposes, or pre-release versions of the Online Services. + +“**Professional Services Data**” means all data, including all text, sound, video, image files or software, that are provided to GitHub, by or on behalf of a Customer (or that Customer authorizes GitHub to obtain from an Online Service) or otherwise obtained or processed by or on behalf of GitHub through an engagement with GitHub to obtain Professional Services. Professional Services Data includes Support Data. + +“**Service Generated Data**” means data generated or derived by GitHub through the operation of an Online Service. Service Generated Data does not include Customer Data, Diagnostic Data, or Professional Services Data. + +“**Standard Contractual Clauses**” means either of the following sets of Standard Contractual Clauses, as applicable in the individual case to the transfer of personal data according to the section of this DPA entitled “Data Transfers and Location” below: +- the Standard Contractual Clauses (MODULE TWO: Transfer controller to processor), dated 4 June 2021, for the transfer of personal data to third countries pursuant to Regulation (EU) 2016/679 of the European Parliament and of the Council, as described in Article 46 of the GDPR and approved by European Commission Implementing Decision (EU) 2021/91 (“Standard Contractual Clauses (EU/EEA)”). The Standard Contractual Clauses (EU/EEA) are set forth in Attachment 1. +- the Standard Contractual Clauses (Processors), dated 5 February 2010, for the transfer of personal data to processors established in third countries which do not ensure an adequate level of data protection, as described in Article 46 of the GDPR, approved by European Commission Decision 2010/87/EU and recognized by the regulatory or supervisory authorities of the United Kingdom for use in connection with data transfers from the United Kingdom (“Standard Contractual Clauses (UK)”). The Standard Contractual Clauses (UK) are set forth in Attachment 2. + +“**Subprocessor**” means other processors used by GitHub to process Personal Data on behalf of Customer in connection with the Online Services, as described in Article 28 of the GDPR. + +“**Support Data**” means all data, including all text, sound, video, image files, or software, that are provided to GitHub by or on behalf of Customer (or that Customer authorizes GitHub to obtain from an Online Service) through an engagement with GitHub to obtain technical support for Online Services covered under this agreement. Support Data is a subset of Professional Services Data. + +Lower case terms used but not defined in this DPA, such as “personal data breach”, “processing”, “controller”, “processor”, “profiling”, “personal data”, and “data subject” will have the same meaning as set forth in Article 4 of the GDPR, irrespective of whether GDPR applies. The terms “data importer” and “data exporter” have the meanings given in the Standard Contractual Clauses. + +For clarity, and as detailed above, data defined as Customer Data, Diagnostic Data, Service Generated Data, and Professional Services Data may contain Personal Data. For illustrative purposes, please see the chart inserted below: + +
    + personal_data_types +
    + +Above is a visual representation of the data types defined in the DPA. All Personal Data is processed as a part of one of the other data types (all of which also include non-personal data). Support Data is a sub-set of Professional Services Data. Except where explicitly stated otherwise, the DPA Terms exclusively apply to Personal Data. + +## General Terms + +### Compliance with Laws + +GitHub will comply with all laws and regulations applicable to its provision of the Online Services, including security breach notification law and Data Protection Requirements. However, GitHub is not responsible for compliance with any laws or regulations applicable to Customer or Customer’s industry that are not generally applicable to information technology service providers. GitHub does not determine whether Customer Data includes information subject to any specific law or regulation. All Security Incidents are subject to the Security Incident Notification terms below. + +Customer must comply with all laws and regulations applicable to its use of Online Services, including laws related to biometric data, confidentiality of communications, and Data Protection Requirements. Customer is responsible for determining whether the Online Services are appropriate for storage and processing of information subject to any specific law or regulation and for using the Online Services in a manner consistent with Customer’s legal and regulatory obligations. Customer is responsible for responding to any request from a third party regarding Customer’s use of an Online Service, such as a request to take down content under the U.S. Digital Millennium Copyright Act or other applicable laws. + +## Proteção de dados + +Terms This section of the DPA includes the following subsections: +- Escopo +- Nature of Data Processing; Ownership +- Disclosure of Processed Data +- Processing of Personal Data; GDPR +- Data Security +- Security Incident Notification +- Data Transfers and Location +- Data Retention and Deletion +- Processor Confidentiality Commitment +- Notice and Controls on Use of Subprocessors +- Educational Institutions +- CJIS Customer Agreement, HIPAA Business Associate, Biometric Data +- California Consumer Privacy Act (CCPA) +- How to Contact GitHub +- Appendix A – Security Measures + +### Escopo + +The DPA Terms apply to all Online Services. + +Previews may employ lesser or different privacy and security measures than those typically present in the Online Services. Unless otherwise noted, Customer should not use Previews to process Personal Data or other data that is subject to legal or regulatory compliance requirements. The following terms in this DPA do not apply to Previews: Processing of Personal Data; GDPR, Data Security, and California Consumer Privacy Act. + +### Nature of Data Processing; Ownership + +Except as otherwise stated in the DPA Terms, GitHub will use and otherwise process Customer Data and Personal Data as described and subject to the limitations provided below (a) to provide Customer the Online Service in accordance with Customer’s documented instructions, and/or (b) for GitHub’s legitimate business operations incident to delivery of the Online Services to Customer. As between the parties, Customer retains all right, title and interest in and to Customer Data. GitHub acquires no rights in Customer Data other than the rights Customer grants to GitHub in this section. This paragraph does not affect GitHub’s rights in software or services GitHub licenses to Customer. + +#### Processing to Provide Customer the Online Services + +For purposes of this DPA, “to provide” an Online Service consists of: +- Delivering functional capabilities as licensed, configured, and used by Customer and its users, including providing personalized user experiences; +- Troubleshooting (e.g., preventing, detecting, and repairing problems); and +- Ongoing improvement (e.g., installing the latest updates and making improvements to user productivity, reliability, efficacy, and security). + +When providing Online Services, GitHub will use or otherwise process Personal Data only on Customer’s behalf and in accordance with Customer’s documented instructions. + +#### Processing for GitHub’s Legitimate Business Operations + +For purposes of this DPA, “GitHub’s legitimate business operations” consist of the following, each as incident to delivery of the Online Services to Customer: (1) billing and account management; (2) compensation (e.g., calculating employee commissions and partner incentives); (3) internal reporting and business modeling (e.g., forecasting, revenue, capacity planning, product strategy); (4) combatting fraud, abuse, cybercrime, or cyber-attacks that may affect GitHub or Online Services; (5) improving the core functionality of accessibility, privacy or energy-efficiency; (6) financial reporting and compliance with legal obligations (subject to the limitations on disclosure of Processed Data outlined below); (7) the creation or management of end user accounts and profiles by GitHub for individual users of Customer (except where Customer creates, manages or otherwise controls such end user accounts or profiles itself); and (8) other purposes pertaining to Personal Data not provided by Customer for storage in GitHub repositories or in connection with Professional Services. + +When processing for GitHub’s legitimate business operations, GitHub will not use or otherwise process Personal Data for: (a) user profiling, (b) advertising or similar commercial purposes, (c) data selling or brokering, or (d) any other purpose, other than for the purposes set out in this section. + +### Disclosure of Processed Data + +GitHub will not disclose or provide access to any Processed Data except: (1) as Customer directs; (2) as described in this DPA; or (3) as required by law. For purposes of this section, “Processed Data” means: (a) Customer Data; (b) Personal Data and (c) any other data processed by GitHub in connection with the Online Service that is Customer’s confidential information under the GitHub Customer Agreement. All processing of Processed Data is subject to GitHub’s obligation of confidentiality under the GitHub Customer Agreement. + +GitHub will not disclose or provide access to any Processed Data to law enforcement unless required by law. If law enforcement contacts GitHub with a demand for Processed Data, GitHub will attempt to redirect the law enforcement agency to request that data directly from Customer. If compelled to disclose or provide access to any Processed Data to law enforcement, GitHub will promptly notify Customer and provide a copy of the demand, unless legally prohibited from doing so. + +Upon receipt of any other third-party request for Processed Data, GitHub will promptly notify Customer unless prohibited by law. GitHub will reject the request unless required by law to comply. If the request is valid, GitHub will attempt to redirect the third party to request the data directly from Customer. + +GitHub will not provide any third party: (a) direct, indirect, blanket, or unfettered access to Processed Data; (b) platform encryption keys used to secure Processed Data or the ability to break such encryption; or (c) access to Processed Data if GitHub is aware that the data is to be used for purposes other than those stated in the third party’s request. + +In support of the above, GitHub may provide Customer’s basic contact information to the third party. + +### Processing of Personal Data; GDPR + +All Personal Data processed by GitHub in connection with the Online Services is obtained as part of either Customer Data, Professional Services Data (including Support Data), Diagnostic Data, or Service Generated Data. Personal Data provided to GitHub by, or on behalf of, Customer through use of the Online Service is also Customer Data. Pseudonymized identifiers may be included in Diagnostic Data or Service Generated Data and are also Personal Data. Any Personal Data pseudonymized, or de-identified but not anonymized, or Personal Data derived from Personal Data is also Personal Data. + +To the extent GitHub is a processor or subprocessor of Personal Data subject to the GDPR, the GDPR Related Terms in Attachment 3 govern that processing and the parties also agree to the following terms in this sub-section (“Processing of Personal Data; GDPR”): + +#### Processor and Controller Roles and Responsibilities + +Customer and GitHub agree that Customer is the controller of Personal Data and GitHub is the processor of such data, except (a) when Customer acts as a processor of Personal Data, in which case GitHub is a subprocessor; or (b) as stated otherwise in the GitHub Customer Agreement or this DPA. When GitHub acts as the processor or subprocessor of Personal Data, it will process Personal Data only on Customer’s behalf and in accordance with documented instructions from Customer. Customer agrees that its GitHub Customer Agreement (including the DPA Terms and any applicable updates), along with the product documentation and Customer’s use and configuration of features in the Online Services, are Customer’s complete documented instructions to GitHub for the processing of Personal Data. Information on use and configuration of the Online Services can be found at https://docs.github.com or a successor location. Any additional or alternate instructions must be agreed to according to the process for amending Customer’s GitHub Customer Agreement. In any instance where the GDPR applies and Customer is a processor, Customer warrants to GitHub that Customer’s instructions, including appointment of GitHub as a processor or subprocessor, have been authorized by the relevant controller. + +To the extent GitHub uses or otherwise processes Personal Data subject to the GDPR for GitHub’s legitimate business operations incident to delivery of the Online Services to Customer, GitHub will comply with the obligations of an independent data controller under GDPR for such use. GitHub is accepting the added responsibilities of a data “controller” under the GDPR for processing in connection with its legitimate business operations to: (a) act consistent with regulatory requirements, to the extent required under the GDPR; and (b) provide increased transparency to Customers and confirm GitHub’s accountability for such processing. GitHub employs safeguards to protect Personal Data in processing, including those identified in this DPA and those contemplated in Article 6(4) of the GDPR. With respect to processing of Personal Data under this paragraph, GitHub makes the commitments set forth in the Standard Contractual Clauses set forth in Attachment 1 or Attachment 2 (as applicable); for those purposes, (i) any GitHub disclosure of Personal Data, as described in Annex III to Attachment 1 or Appendix 3 to Attachment 2 (as applicable), that has been transferred in connection with GitHub’s legitimate business operations is deemed a “Relevant Disclosure” and (ii) the commitments in Annex III to Attachment 1 or Appendix 3 to Attachment 2 (as applicable) apply to such Personal Data. + +#### Processing Details + +The parties acknowledge and agree that: + +- **Subject Matter**. The subject-matter of the processing is limited to Personal Data within the scope of the section of this DPA entitled “Nature of Data Processing; Ownership” above and the GDPR. +- **Duration of the Processing**. The duration of the processing shall be in accordance with Customer instructions and the terms of the DPA. +- **Nature and Purpose of the Processing**. The nature and purpose of the processing shall be to provide the Online Service pursuant to Customer’s GitHub Customer Agreement and for GitHub’s legitimate business operations incident to delivery of the Online Service to Customer (as further described in the section of this DPA entitled “Nature of Data Processing; Ownership” above). +- **Categories of Data**. The types of Personal Data processed by GitHub when providing the Online Service include: (i) Personal Data that Customer elects to include in Customer Data or Professional Services Data (including, without limitation, Support Data); and (ii) those expressly identified in Article 4 of the GDPR that may be contained in Diagnostic Data or Service Generated Data. The types of Personal Data that Customer elects to include in Customer Data or Professional Services Data (including, without limitation, Support Data) may be any categories of Personal Data identified in records maintained by Customer acting as controller pursuant to Article 30 of the GDPR, including the categories of Personal Data set forth in Annex I to Attachment 1 or Appendix 1 to Attachment 2 (as applicable). +- Data Subjects. The categories of data subjects are Customer’s representatives and end users, such as employees, contractors, collaborators, and customers, and may include any other categories of data subjects as identified in records maintained by Customer acting as controller pursuant to Article 30 of the GDPR, including the categories of data subjects set forth in Annex I to Attachment 1 or Appendix 1 to Attachment 2 (as applicable). + +#### Data Subject Rights; Assistance with Requests + +GitHub will make available to Customer, in a manner consistent with the functionality of the Online Service and GitHub’s role as a processor of Personal Data of data subjects, the ability to fulfill data subject requests to exercise their rights under the GDPR. If GitHub receives a request from Customer’s data subject to exercise one or more of its rights under the GDPR in connection with an Online Service for which GitHub is a data processor or subprocessor, GitHub will redirect the data subject to make its request directly to Customer. Customer will be responsible for responding to any such request including, where necessary, by using the functionality of the Online Service. O GitHub atenderá às solicitações justas do Cliente para auxiliar na resposta do Cliente a tal solicitação do titular de dados. + +#### Records of Processing Activities + +To the extent the GDPR requires GitHub to collect and maintain records of certain information relating to Customer, Customer will, where requested, supply such information to GitHub and keep it accurate and up-to-date. GitHub may make any such information available to the supervisory authority if required by the GDPR. + +### Data Security + +GitHub will implement and maintain appropriate technical and organizational measures and security safeguards against accidental or unlawful destruction, or loss, alteration, unauthorized disclosure of or access to, Customer Data and Personal Data processed by GitHub on behalf and in accordance with the documented instructions of Customer in connection with the Online Services. GitHub will regularly monitor compliance with these measures and safeguards and will continue to take appropriate steps throughout the term of the GitHub Customer Agreement. Appendix A – Security Safeguards contains a description of the technical and organizational measures and security safeguards implemented by GitHub. + +Customer is solely responsible for making an independent determination as to whether the technical and organizational measures and security safeguards for an Online Service meet Customer’s requirements, including any of its security obligations under applicable Data Protection Requirements. Customer acknowledges and agrees that (taking into account the state of the art, the costs of implementation, and the nature, scope, context and purposes of the processing of its Customer Data and Personal Data as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons) the technical and organizational measures and security safeguards implemented and maintained by GitHub provide a level of security appropriate to the risk with respect to its Customer Data and Personal Data. Customer is responsible for implementing and maintaining privacy protections and security measures for components that Customer provides or controls. + +GitHub will provide security compliance reporting such as external SOC1, type 2 and SOC2, type2 audit reports upon Customer request. Customer agrees that any information and audit rights granted by the applicable Data Protection Requirements (including, where applicable, Article 28(3)(h) of the GDPR) will be satisfied by these compliance reports, and will otherwise only arise to the extent that GitHub's provision of a compliance report does not provide sufficient information, or to the extent that Customer must respond to a regulatory or supervisory authority audit or investigation. + +Should Customer be subject to a regulatory or supervisory authority audit or investigation or carry out an audit or investigation in response to a request by a regulatory or supervisory authority that requires participation from GitHub, and Customers’ obligations cannot reasonably be satisfied (where allowable by Customer’s regulators) through audit reports, documentation, or compliance information that GitHub makes generally available to its customers, then GitHub will promptly respond to Customer’s additional instructions and requests for information, in accordance with the following terms and conditions: + +- GitHub will provide access to relevant knowledgeable personnel, documentation, and application software. +- Customer and GitHub will mutually agree in a prior written agreement (email is acceptable) upon the scope, timing, duration, control and evidence requirements, provided that this requirement to agree will not permit GitHub to unreasonably delay its cooperation. +- Customer must ensure its regulator’s use of an independent, accredited third-party audit firm, during regular business hours, with reasonable advance written notice to GitHub, and subject to reasonable confidentiality procedures. Neither Customer, its regulators, nor its regulators’ delegates shall have access to any data from GitHub’s other customers or to GitHub systems or facilities not involved in the Online Services. +- Customer is responsible for all costs and fees related to GitHub’s cooperation with the regulatory audit of Customer, including all reasonable costs and fees for any and all time GitHub expends, in addition to the rates for services performed by GitHub. +- If the report generated from GitHub’s cooperation with the regulatory audit of Customer includes any findings pertaining to GitHub, Customer will share such report, findings, and recommended actions with GitHub where allowed by Customer’s regulators. + +### Security Incident Notification + +If GitHub becomes aware of a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Customer Data or Personal Data processed by GitHub on behalf and in accordance with the documented instructions of Customer in connection with the Online Services (each a "Security Incident"), GitHub will promptly and without undue delay (1) notify Customer of the Security Incident; (2) investigate the Security Incident and provide Customer with detailed information about the Security Incident; (3) take reasonable steps to mitigate the effects and to minimize any damage resulting from the Security Incident. + +Notification(s) of Security Incidents will be delivered to one or more of Customer's administrators by any means GitHub selects, including via email. It is Customer's sole responsibility to ensure it maintains accurate contact information with GitHub and that Customer's administrators monitor for and respond to any notifications. O Cliente é o único responsável pelo cumprimento de suas obrigações perante as leis de notificação de incidentes aplicáveis ao Cliente e pelo cumprimento das obrigações de notificação de terceiros relacionadas a qualquer Incidente de segurança. + +GitHub will make reasonable efforts to assist Customer in fulfilling Customer's obligation under GDPR Article 33 or other applicable law or regulations to notify the relevant regulatory or supervisory authority and individual data subjects about a Security Incident. + +GitHub’s notification of or response to a Security Incident under this section is not an acknowledgement by GitHub of any fault or liability with respect to the Security Incident. + +Customer must notify GitHub promptly about any possible misuse of its accounts or authentication credentials or any Security Incident related to an Online Service. + +### Data Transfers and Location + +Personal Data that GitHub processes on behalf and in accordance with the documented instructions of Customer in connection with the Online Services may not be transferred to, or stored and processed in a geographic location except in accordance with the DPA Terms and the safeguards provided below in this section. Taking into account such safeguards, Customer appoints GitHub to transfer Personal Data to the United States or any other country in which GitHub or its Subprocessors operate and to store and process Personal Data to provide the Online Services, except as may be described elsewhere in these DPA Terms. + +All transfers of Personal Data out of the European Union, European Economic Area, or Switzerland to provide the Online Services shall be governed by the Standard Contractual Clauses (EU/EEA) in Attachment 1. All transfers of Personal Data out of the United Kingdom to provide the Online Services shall be governed by the Standard Contractual Clauses (UK) in Attachment 2. For the purposes of the Standard Contractual Clauses (UK) in Attachment 2, references to the “European Union,” “EU,” “European Economic Area,” “EEA” or a “Member State” shall be interpreted to refer to the United Kingdom where reasonably necessary and appropriate to give full force and effect to the Standard Contractual Clauses (UK) with respect to transfers of Personal Data from the United Kingdom. This applies regardless of the fact that, effective January 31, 2020, the United Kingdom is no longer a Member State of the European Union or European Economic Area. + +GitHub will abide by the requirements of applicable European Union, European Economic Area, United Kingdom and Swiss data protection law, and other Data Protection Requirements, in each case regarding the transfer of Personal Data to recipients or jurisdictions outside such jurisdiction. All such transfers of Personal Data will, where applicable, be subject to appropriate safeguards as described in Article 46 of the GDPR and such transfers and safeguards will be documented according to Article 30(2) of the GDPR. + +Subject to the safeguards described above, GitHub may transfer, store and otherwise process Personal Data to or in jurisdictions and geographic locations worldwide as it, subject to its sole discretion, considers reasonably necessary in connection with the Online Services. + +### Data Retention and Deletion + +Upon Customer's reasonable request, unless prohibited by law, GitHub will return or destroy all Customer Data and Personal Data processed by GitHub on behalf and in accordance with the documented instructions of Customer in connection with the Online Services at all locations where it is stored within 30 days of the request, provided that it is no longer needed for providing the Online Services or the purposes for which a data subject had authorized the processing of their Personal Data. GitHub may retain Customer Data or Personal Data to the extent required by the applicable Data Protection Requirements or other applicable law, and only to the extent and for such period as required by the applicable Data Protection Requirements or other applicable law, provided that GitHub will ensure that the Customer Data or Personal Data is processed only as necessary for the purpose specified in the applicable Data Protection Requirements or other applicable law and no other purpose, and the Customer Data or Personal Data remains protected by the Applicable Data Protection Requirements or other applicable law. + +### Processor Confidentiality Commitment + +GitHub will ensure that its personnel engaged in the processing of Customer Data and Personal Data on behalf of Customer in connection with the Online Services (i) will process such data only on instructions from Customer or as described in this DPA, and (ii) will be obligated to maintain the confidentiality and security of such data even after their engagement ends. GitHub shall provide periodic and mandatory data privacy and security training and awareness to its employees with access to Customer Data and Personal Data in accordance with applicable Data Protection Requirements or other applicable law and industry standards. + +### Notice and Controls on Use of Subprocessors + +GitHub may hire Subprocessors to provide certain limited or ancillary services on its behalf. Customer consents to this engagement and to GitHub Affiliates as Subprocessors. The above authorizations will constitute Customer’s prior written consent to the subcontracting by GitHub of the processing of Personal Data if such consent is required under applicable law, the Standard Contractual Clauses or the GDPR Related Terms. + +GitHub is responsible for its Subprocessors’ compliance with GitHub’s obligations in this DPA. GitHub makes available information about Subprocessors on the GitHub website https://github.com/subprocessors (or a successor location). When engaging any Subprocessor, GitHub will ensure via a written contract that the Subprocessor may access and use Customer Data or Personal Data only to deliver the services GitHub has retained them to provide and is prohibited from using Customer Data or Personal Data for any other purpose. GitHub will ensure that Subprocessors are bound by written agreements that require them to provide at least the level of data protection required of GitHub by the DPA, including the limitations on disclosure of Personal Data. GitHub agrees to oversee the Subprocessors to ensure that these contractual obligations are met. + +From time to time, GitHub may engage new Subprocessors. GitHub will give Customer notice (by updating the website at https://github.com/github-subprocessors-list (or a successor location) and providing Customer with a mechanism to obtain notice of that update) of any new Subprocessor in advance of providing that Subprocessor with access to Customer Data. If GitHub engages a new Subprocessor for a new Online Service, GitHub will give Customer notice prior to availability of that Online Service. + +If Customer does not approve of a new Subprocessor, then Customer may terminate any subscription for the affected Online Service without penalty by providing, before the end of the relevant notice period, written notice of termination. Customer may also include an explanation of the grounds for non-approval together with the termination notice, in order to permit GitHub to re-evaluate any such new Subprocessor based on the applicable concerns. If the affected Online Service is part of a suite (or similar single purchase of services), then any termination will apply to the entire suite. After termination, GitHub will remove payment obligations for any subscriptions for the terminated Online Service from subsequent invoices to Customer or its reseller. + +### Educational Institutions +If Customer is an educational agency or institution subject to the regulations under the Family Educational Rights and Privacy Act, 20 U.S.C. § 1232g (FERPA), or similar state student or educational privacy laws (collectively “Educational Privacy Laws”), Customer shall not provide Personal Data covered by such Educational Privacy Laws to GitHub without obtaining GitHub’s prior, written and specific consent and entering into a separate agreement with GitHub governing the parties’ rights and obligations with respect to the processing of such Personal Data by GitHub in connection with the Online Services. + +Subject to the above, if Customer intends to provide to GitHub Personal Data covered by FERPA, the parties agree and acknowledge that, for the purposes of this DPA, GitHub is a “school official” with “legitimate educational interests” in the Personal Data, as those terms have been defined under FERPA and its implementing regulations. Customer understands that GitHub may possess limited or no contact information for Customer’s students and students’ parents. Consequently, Customer will be responsible for obtaining any student or parental consent for any end user’s use of the Online Services that may be required by applicable law and to convey notification on behalf of GitHub to students (or, with respect to a student under 18 years of age and not in attendance at a postsecondary institution, to the student’s parent) of any judicial order or lawfully-issued subpoena requiring the disclosure of Personal Data in GitHub’s possession as may be required under applicable law. + +### CJIS Customer Agreement, HIPAA Business Associate, Biometric Data + +Except with GitHub’s prior, written and specific consent, Customer shall not provide to GitHub any Personal Data + +- relating to criminal convictions and offenses or Personal Data collected or otherwise processed by Customer subject to or in connection with FBI Criminal Justice Information Services or the related Security Policy. +- constituting protected health information governed by the privacy, security, and breach notification rules issued by the United States Department of Health and Human Services, Parts 160 and 164 of Title 45 of the Code of Federal Regulations, established pursuant to the Health Insurance Portability and Accountability Act of 1996 (Public Law 104-191) or by state health or medical privacy laws. +- collected as part of a clinical trial or other biomedical research study subject to, or conducted in accordance with, the Federal Policy for the Protection of Human Subjects (Common Rule). +- covered by state, federal or foreign biometric privacy laws or otherwise constituting biometric information including information on an individual’s physical, physiological, biological or behavioral characteristics or information derived from such information that is used or intended to be used, singly or in combination with each other or with other information, to establish individual identity. + +### California Consumer Privacy Act (CCPA) / California Privacy Rights Act (CPRA) + +If and to the extent GitHub is processing Personal Data on behalf and in accordance with the documented instructions of Customer within the scope of the CCPA, GitHub makes the following additional commitments to Customer. GitHub will process the Personal Data on behalf of Customer and will not + +- sell the Personal Data as the term “selling” is defined in the CCPA. - share, rent, release, disclose, disseminate, make available, transfer or otherwise communicate orally, in writing or by electronic or other means, the Personal Data to a third party for cross-context behavioral advertising, whether or not for monetary or other valuable consideration, including transactions for cross-context behavioral advertising in which no money is exchanged. +- retain, use or disclose the Personal Data for any purpose other than for the business purposes specified in the DPA Terms and the GitHub Customer Agreement, including retaining, using or disclosing the Personal Data for a commercial purpose other than the business purposes specified in the DPA Terms or the GitHub Customer Agreement, or as otherwise permitted by the CCPA. +- retain, use or disclose the Personal Data outside of the direct business relationship with Customer. +- combine the Personal Data with personal information that it receives from or on behalf of a third party or collects from California residents, except that GitHub may combine Personal Data to perform any business purpose as permitted by the CCPA or any regulations adopted or issued under the CCPA. + +### How to Contact GitHub + +If Customer believes that GitHub is not adhering to its privacy or security commitments, Customer may contact customer support or use GitHub’s Privacy web form, located at https://support.github.com/contact/privacy. GitHub’s mailing address is: + +**GitHub Privacy**
    GitHub, Inc.
    88 Colin P. Kelly Jr. Street
    San Francisco, California 94107 USA
    + +GitHub B.V. is GitHub’s data protection representative for the European Economic Area. The privacy representative of GitHub B.V. can be reached at the following address: + +**GitHub B.V.**
    Vijzelstraat 68-72
    1017 HL Amsterdam
    The Netherlands
    + +

    Appendix A – Security Safeguards

    + +GitHub has implemented and will maintain for Customer Data and Personal Data processed by GitHub on behalf and in accordance with the documented instructions of Customer in connection with GitHub services the following technical and organizational measures and security safeguards, which in conjunction with the security commitments in this DPA (including the GDPR Related Terms), are GitHub’s only responsibility with respect to the security of that data: + +| Domain | Practices | +| ---------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Organization of Information Security | **Security Ownership**. GitHub has appointed one or more security officers responsible for coordinating and monitoring the security policies and procedures.

    **Security Roles and Responsibilities**. GitHub personnel with access to Customer Data and Personal Data are subject to confidentiality obligations.

    **Risk Management Program**. GitHub performs an annual risk assessment.
    GitHub retains its security documents pursuant to its retention requirements after they are no longer in effect.

    **Vendor Management**. GitHub has a vendor risk assessment process, vendor contract clauses and additional data protection agreements with vendors. | +| Asset Management | **Asset Inventory**. GitHub maintains an inventory of all media on which Customer Data and Personal Data is stored. Access to the inventories of such media is restricted to GitHub personnel authorized to have such access.

    **Asset Handling**
    - GitHub classifies Customer Data and Personal Data to help identify it and to allow for access to it to be appropriately restricted.
    - GitHub communicates employee responsibility and accountability for data protection up to and including cause for termination.
    GitHub personnel must obtain GitHub authorization prior to remotely accessing Customer Data and Personal Data or processing Customer Data and Personal Data outside GitHub’s facilities. | +| Human Resources Security | **Security Training**. GitHub requires all new hires to complete security and privacy awareness training as part of initial on-boarding. Participation in annual training is required for all employees to provide a baseline for security and privacy basics. | +| Physical and Environmental Security | **Physical Access to Facilities**. GitHub limits access to facilities where information systems that process Customer Data and Personal Data are located to identified authorized individuals.

    **Physical Access to Components**. GitHub maintains records of the incoming and outgoing media containing Customer Data, including the kind of media, the authorized sender/recipients, date and time, the number of media and the types of Customer Data and Personal Data they contain.

    **Protection from Disruptions**. GitHub uses a variety of industry standard systems to protect against loss of data due to power supply failure or line interference.

    **Component Disposal**. GitHub uses industry standard processes to delete Customer Data and Personal Data when it is no longer needed. | +| Communications and Operations Management | **Operational Policy**. GitHub maintains security documents describing its security measures and the relevant procedures and responsibilities of its personnel who have access to Customer Data.

    **Data Recovery Procedures**
    - On an ongoing basis, but in no case less frequently than once a week (unless no Customer Data and Personal Data has been updated during that period), GitHub maintains multiple copies of Customer Data and Personal Data from which Customer Data and Personal Data can be recovered.
    - GitHub stores copies of Customer Data and Personal Data and data recovery procedures in a different place from where the primary computer equipment processing the Customer Data and Personal Data is located.
    - GitHub has specific procedures in place governing access to copies of Customer Data.
    - GitHub logs data restoration efforts, including the person responsible, the description of the restored data and where applicable, the person responsible and which data (if any) had to be input manually in the data recovery process.

    **Malicious Software**. GitHub has threat detection controls to help identify and respond to anomalous or suspicious access to Customer Data, including malicious software originating from public networks.

    **Data Beyond Boundaries**
    - GitHub encrypts, or enables Customer to encrypt, Customer Data and Personal Data that is transmitted over public networks.
    - GitHub restricts access to Customer Data and Personal Data in media leaving its facilities.

    **Event Logging**. GitHub logs, or enables Customer to log, access and use of information systems containing Customer Data, registering the access ID, time, authorization granted or denied, and relevant activity. | +| Access Control | **Access Policy**. GitHub maintains a record of security privileges of individuals having access to Customer Data.

    **Access Authorization**
    - GitHub maintains and updates a record of personnel authorized to access GitHub systems that contain Customer Data.
    - GitHub identifies those personnel who may grant, alter or cancel authorized access to data and resources.
    - GitHub ensures that where more than one individual has access to systems containing Customer Data, the individuals have separate identifiers/log-ins where technically and architecturally feasible, and commercially reasonable.

    **Least Privilege**
    - Technical support personnel are only permitted to have access to Customer Data and Personal Data when needed.
    - GitHub restricts access to Customer Data and Personal Data to only those individuals who require such access to perform their job function. GitHub employees are only granted access to production systems based on their role within the organization.

    **Integrity and Confidentiality**

    - GitHub instructs GitHub personnel to disable administrative sessions when computers are left unattended.
    - GitHub stores passwords such that they are encrypted or unintelligible while they are in force.

    **Authentication**
    - GitHub uses industry standard practices to identify and authenticate users who attempt to access information systems.
    - Where authentication mechanisms are based solely on passwords, GitHub requires the password to be at least eight characters long.
    - GitHub ensures that de-activated or expired employee identifiers are not granted to other individuals.
    - GitHub monitors, or enables Customer to monitor, repeated attempts to gain access to the information system using an invalid password.
    - GitHub maintains industry standard procedures to deactivate passwords that have been corrupted or inadvertently disclosed.
    - GitHub uses industry standard password protection practices, including practices designed to maintain the confidentiality and integrity of passwords when they are assigned and distributed, and during storage.

    **Network Design**. GitHub has controls to ensure no systems storing Customer Data and Personal Data are part of the same logical network used for GitHub business operations. | +| Information Security Incident Management | **Incident Response Process**
    - GitHub maintains a record of security incidents with a description of the incidents, the time period, the consequences of the breach, the name of the reporter, and to whom the incident was reported, and details regarding the handling of the incident.
    - In the event that GitHub Security confirms or reasonably suspects that a GitHub.com customer is affected by a data breach, we will notify the customer without undue delay
    - GitHub tracks, or enables Customer to track, disclosures of Customer Data, including what data has been disclosed, to whom, and at what time.

    **Service Monitoring**. GitHub employs a wide range of continuous monitoring solutions for preventing, detecting, and mitigating attacks to the site. | +| Business Continuity Management | - GitHub maintains emergency and contingency plans for the facilities in which GitHub information systems that process Customer Data and Personal Data are located.
    - GitHub’s redundant storage and its procedures for recovering data are designed to attempt to reconstruct Customer Data and Personal Data in its original or last-replicated state from before the time it was lost or destroyed. | + +

    Attachment 1 - The Standard Contractual Clauses (EU/EEA)

    + +### Controller to Processor + +#### SECTION I + +##### Clause 1 + +**Purpose and scope** + +
      +
    1. The purpose of these standard contractual clauses is to ensure compliance with the requirements of Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data (General Data Protection Regulation) for the transfer of personal data to a third country.
      2. +
    2. The Parties: +
        +
      1. the natural or legal person(s), public authority/ies, agency/ies or other body/ies (hereinafter ‘entity/ies’) transferring the personal data, as listed in Annex I.A (hereinafter each ‘data exporter’), and
        2. +
      2. the entity/ies in a third country receiving the personal data from the data exporter, directly or indirectly via another entity also Party to these Clauses, as listed in Annex I.A (hereinafter each ‘data importer’)
        3. +
      + have agreed to these standard contractual clauses (hereinafter: ‘Clauses’).
      3. +
    3. These Clauses apply with respect to the transfer of personal data as specified in Annex I.B.
      4. +
    4. The Appendix to these Clauses containing the Annexes referred to therein forms an integral part of these Clauses.
      5. +
    + +##### Clause 2 + +**Effect and invariability of the Clauses** +
      +
    1. These Clauses set out appropriate safeguards, including enforceable data subject rights and effective legal remedies, pursuant to Article 46(1) and Article 46(2)(c) of Regulation (EU) 2016/679 and, with respect to data transfers from controllers to processors and/or processors to processors, standard contractual clauses pursuant to Article 28(7) of Regulation (EU) 2016/679, provided they are not modified, except to select the appropriate Module(s) or to add or update information in the Appendix. This does not prevent the Parties from including the standard contractual clauses laid down in these Clauses in a wider contract and/or to add other clauses or additional safeguards, provided that they do not contradict, directly or indirectly, these Clauses or prejudice the fundamental rights or freedoms of data subjects.
      2. +
    2. These Clauses are without prejudice to obligations to which the data exporter is subject by virtue of Regulation (EU) 2016/679.
      3. +
    + +##### Clause 3 + +**Third-party beneficiaries** + +
      +
    1. Data subjects may invoke and enforce these Clauses, as third-party beneficiaries, against the data exporter and/or data importer, with the following exceptions:
      2. +
        +
      1. Clause 1, Clause 2, Clause 3, Clause 6, Clause 7;
        2. +
      2. Clause 8.1(b), 8.9(a), (c), (d) and (e);
        3. +
      3. Clause 9(a), (c), (d) and (e);
        4. +
      4. Clause 12(a), (d) and (f);
        5. +
      5. Clause 13;
        6. +
      6. Clause 15.1(c), (d) and (e);
        7. +
      7. Clause 16(e);
        8. +
      8. Clause 18(a) and (b).
        9. +
      +
    2. Paragraph (a) is without prejudice to rights of data subjects under Regulation (EU) 2016/679.
      3. +
    + +##### Clause 4 + +**Interpretation** + +
      +
    1. Where these Clauses use terms that are defined in Regulation (EU) 2016/679, those terms shall have the same meaning as in that Regulation.
      2. +
    2. These Clauses shall be read and interpreted in the light of the provisions of Regulation (EU) 2016/679.
      3. +
    3. These Clauses shall not be interpreted in a way that conflicts with rights and obligations provided for in Regulation (EU) 2016/679.
      4. +
    + +##### Clause 5 + +**Hierarchy** + +In the event of a contradiction between these Clauses and the provisions of related agreements between the Parties, existing at the time these Clauses are agreed or entered into thereafter, these Clauses shall prevail. + +##### Clause 6 + +**Description of the transfer(s)** + +The details of the transfer(s), and in particular the categories of personal data that are transferred and the purpose(s) for which they are transferred, are specified in Annex I.B. + +##### Clause 7 + +**Docking clause** + +
      +
    1. An entity that is not a Party to these Clauses may, with the agreement of the Parties, accede to these Clauses at any time, either as a data exporter or as a data importer, by completing the Appendix and signing Annex I.A.
      2. +
    2. Once it has completed the Appendix and signed Annex I.A, the acceding entity shall become a Party to these Clauses and have the rights and obligations of a data exporter or data importer in accordance with its designation in Annex I.A.
      3. +
    3. The acceding entity shall have no rights or obligations arising under these Clauses from the period prior to becoming a Party.
      4. +
    + +#### SECTION II – OBLIGATIONS OF THE PARTIES + +##### Clause 8 + +**Data protection safeguards** + +The data exporter warrants that it has used reasonable efforts to determine that the data importer is able, through the implementation of appropriate technical and organisational measures, to satisfy its obligations under these Clauses. + +**8.1 Instructions**
      +
    1. The data importer shall process the personal data only on documented instructions from the data exporter. The data exporter may give such instructions throughout the duration of the contract.
      2. +
    2. The data importer shall immediately inform the data exporter if it is unable to follow those instructions.
      3. +
    + +**8.2 Purpose limitation** + +The data importer shall process the personal data only for the specific purpose(s) of the transfer, as set out in Annex I.B, unless on further instructions from the data exporter. + +**8.3 Transparency** + +On request, the data exporter shall make a copy of these Clauses, including the Appendix as completed by the Parties, available to the data subject free of charge. To the extent necessary to protect business secrets or other confidential information, including the measures described in Annex II and personal data, the data exporter may redact part of the text of the Appendix to these Clauses prior to sharing a copy, but shall provide a meaningful summary where the data subject would otherwise not be able to understand the its content or exercise his/her rights. On request, the Parties shall provide the data subject with the reasons for the redactions, to the extent possible without revealing the redacted information. This Clause is without prejudice to the obligations of the data exporter under Articles 13 and 14 of Regulation (EU) 2016/679. + +**8.4 Accuracy** + +If the data importer becomes aware that the personal data it has received is inaccurate, or has become outdated, it shall inform the data exporter without undue delay. In this case, the data importer shall cooperate with the data exporter to erase or rectify the data. + +**8.5 Duration of processing and erasure or return of data** + +Processing by the data importer shall only take place for the duration specified in Annex I.B. After the end of the provision of the processing services, the data importer shall, at the choice of the data exporter, delete all personal data processed on behalf of the data exporter and certify to the data exporter that it has done so, or return to the data exporter all personal data processed on its behalf and delete existing copies. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit return or deletion of the personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process it to the extent and for as long as required under that local law. This is without prejudice to Clause 14, in particular the requirement for the data importer under Clause 14(e) to notify the data exporter throughout the duration of the contract if it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under Clause 14(a). + +**8.6 Security of processing** + +
      +
    1. The data importer and, during transmission, also the data exporter shall implement appropriate technical and organisational measures to ensure the security of the data, including protection against a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access to that data (hereinafter ‘personal data breach’). In assessing the appropriate level of security, the Parties shall take due account of the state of the art, the costs of implementation, the nature, scope, context and purpose(s) of processing and the risks involved in the processing for the data subjects. The Parties shall in particular consider having recourse to encryption or pseudonymisation, including during transmission, where the purpose of processing can be fulfilled in that manner. In case of pseudonymisation, the additional information for attributing the personal data to a specific data subject shall, where possible, remain under the exclusive control of the data exporter. In complying with its obligations under this paragraph, the data importer shall at least implement the technical and organisational measures specified in Annex II. The data importer shall carry out regular checks to ensure that these measures continue to provide an appropriate level of security.
      2. +
    2. The data importer shall grant access to the personal data to members of its personnel only to the extent strictly necessary for the implementation, management and monitoring of the contract. It shall ensure that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.
      3. +
    3. In the event of a personal data breach concerning personal data processed by the data importer under these Clauses, the data importer shall take appropriate measures to address the breach, including measures to mitigate its adverse effects. The data importer shall also notify the data exporter without undue delay after having become aware of the breach. Such notification shall contain the details of a contact point where more information can be obtained, a description of the nature of the breach (including, where possible, categories and approximate number of data subjects and personal data records concerned), its likely consequences and the measures taken or proposed to address the breach including, where appropriate, measures to mitigate its possible adverse effects. Where, and in so far as, it is not possible to provide all information at the same time, the initial notification shall contain the information then available and further information shall, as it becomes available, subsequently be provided without undue delay.
      4. +
    4. The data importer shall cooperate with and assist the data exporter to enable the data exporter to comply with its obligations under Regulation (EU) 2016/679, in particular to notify the competent supervisory authority and the affected data subjects, taking into account the nature of processing and the information available to the data importer.
      5. +
    + +**8.7 Sensitive data** + +Where the transfer involves personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic data, or biometric data for the purpose of uniquely identifying a natural person, data concerning health or a person’s sex life or sexual orientation, or data relating to criminal convictions and offences (hereinafter ‘sensitive data’), the data importer shall apply the specific restrictions and/or additional safeguards described in Annex I.B. + +**8.8 Onward transfers** + +The data importer shall only disclose the personal data to a third party on documented instructions from the data exporter. In addition, the data may only be disclosed to a third party located outside the European Union (1) (in the same country as the data importer or in another third country, hereinafter ‘onward transfer’) if the third party is or agrees to be bound by these Clauses, under the appropriate Module, or if: + +
      +
    1. the onward transfer is to a country benefitting from an adequacy decision pursuant to Article 45 of Regulation (EU) 2016/679 that covers the onward transfer;
      2. +
    2. the third party otherwise ensures appropriate safeguards pursuant to Articles 46 or 47 Regulation of (EU) 2016/679 with respect to the processing in question;
      3. +
    3. the onward transfer is necessary for the establishment, exercise or defence of legal claims in the context of specific administrative, regulatory or judicial proceedings; or
      4. +
    4. the onward transfer is necessary in order to protect the vital interests of the data subject or of another natural person.

      5. + Any onward transfer is subject to compliance by the data importer with all the other safeguards under these Clauses, in particular purpose limitation. +
    + +**8.9 Documentation and compliance** + +
      +
    1. The data importer shall promptly and adequately deal with enquiries from the data exporter that relate to the processing under these Clauses.
      2. +
    2. The Parties shall be able to demonstrate compliance with these Clauses. In particular, the data importer shall keep appropriate documentation on the processing activities carried out on behalf of the data exporter.
      3. +
    3. The data importer shall make available to the data exporter all information necessary to demonstrate compliance with the obligations set out in these Clauses and at the data exporter’s request, allow for and contribute to audits of the processing activities covered by these Clauses, at reasonable intervals or if there are indications of non-compliance. In deciding on a review or audit, the data exporter may take into account relevant certifications held by the data importer.
      4. +
    4. The data exporter may choose to conduct the audit by itself or mandate an independent auditor. Audits may include inspections at the premises or physical facilities of the data importer and shall, where appropriate, be carried out with reasonable notice.
      5. +
    5. The Parties shall make the information referred to in paragraphs (b) and (c), including the results of any audits, available to the competent supervisory authority on request.
      6. +
    + +##### Clause 9 + +**Use of sub-processors** + +
      +
    1. GENERAL WRITTEN AUTHORISATION The data importer has the data exporter’s general authorisation for the engagement of sub-processor(s) from an agreed list. The data importer shall specifically inform the data exporter in writing of any intended changes to that list through the addition or replacement of sub-processors at least 90 days in advance, thereby giving the data exporter sufficient time to be able to object to such changes prior to the engagement of the sub-processor(s). The data importer shall provide the data exporter with the information necessary to enable the data exporter to exercise its right to object.
      2. +
    2. Where the data importer engages a sub-processor to carry out specific processing activities (on behalf of the data exporter), it shall do so by way of a written contract that provides for, in substance, the same data protection obligations as those binding the data importer under these Clauses, including in terms of third-party beneficiary rights for data subjects.(2) The Parties agree that, by complying with this Clause, the data importer fulfils its obligations under Clause 8.8. The data importer shall ensure that the sub-processor complies with the obligations to which the data importer is subject pursuant to these Clauses.
      3. +
    3. The data importer shall provide, at the data exporter’s request, a copy of such a sub-processor agreement and any subsequent amendments to the data exporter. To the extent necessary to protect business secrets or other confidential information, including personal data, the data importer may redact the text of the agreement prior to sharing a copy.
      4. +
    4. The data importer shall remain fully responsible to the data exporter for the performance of the sub-processor’s obligations under its contract with the data importer. The data importer shall notify the data exporter of any failure by the sub-processor to fulfil its obligations under that contract.
      5. +
    5. The data importer shall agree a third-party beneficiary clause with the sub-processor whereby – in the event the data importer has factually disappeared, ceased to exist in law or has become insolvent – the data exporter shall have the right to terminate the sub-processor contract and to instruct the sub-processor to erase or return the personal data.
      6. +
    + +##### Clause 10 + +**Data subject rights** + +
      +
    1. The data importer shall promptly notify the data exporter of any request it has received from a data subject. It shall not respond to that request itself unless it has been authorised to do so by the data exporter.
      2. +
    2. The data importer shall assist the data exporter in fulfilling its obligations to respond to data subjects’ requests for the exercise of their rights under Regulation (EU) 2016/679. In this regard, the Parties shall set out in Annex II the appropriate technical and organisational measures, taking into account the nature of the processing, by which the assistance shall be provided, as well as the scope and the extent of the assistance required.
      3. +
    3. In fulfilling its obligations under paragraphs (a) and (b), the data importer shall comply with the instructions from the data exporter.
      4. +
    + +##### Clause 11 + +**Redress** + +
      +
    1. The data importer shall inform data subjects in a transparent and easily accessible format, through individual notice or on its website, of a contact point authorised to handle complaints. It shall deal promptly with any complaints it receives from a data subject.
      2. +
    2. In case of a dispute between a data subject and one of the Parties as regards compliance with these Clauses, that Party shall use its best efforts to resolve the issue amicably in a timely fashion. The Parties shall keep each other informed about such disputes and, where appropriate, cooperate in resolving them.
      3. +
    3. Where the data subject invokes a third-party beneficiary right pursuant to Clause 3, the data importer shall accept the decision of the data subject to:
      4. +
        +
      1. lodge a complaint with the supervisory authority in the Member State of his/her habitual residence or place of work, or the competent supervisory authority pursuant to Clause 13;
        2. +
      2. refer the dispute to the competent courts within the meaning of Clause 18.
        3. +
      +
    4. The Parties accept that the data subject may be represented by a not-for-profit body, organisation or association under the conditions set out in Article 80(1) of Regulation (EU) 2016/679.
      5. +
    5. The data importer shall abide by a decision that is binding under the applicable EU or Member State law.
      6. +
    6. The data importer agrees that the choice made by the data subject will not prejudice his/her substantive and procedural rights to seek remedies in accordance with applicable laws.
      7. +
    + +##### Clause 12 + +**Liability** + +
      +
    1. Each Party shall be liable to the other Party/ies for any damages it causes the other Party/ies by any breach of these Clauses.
      2. +
    2. The data importer shall be liable to the data subject, and the data subject shall be entitled to receive compensation, for any material or non-material damages the data importer or its sub-processor causes the data subject by breaching the third-party beneficiary rights under these Clauses.
      3. +
    3. Notwithstanding paragraph (b), the data exporter shall be liable to the data subject, and the data subject shall be entitled to receive compensation, for any material or non-material damages the data exporter or the data importer (or its sub-processor) causes the data subject by breaching the third-party beneficiary rights under these Clauses. This is without prejudice to the liability of the data exporter and, where the data exporter is a processor acting on behalf of a controller, to the liability of the controller under Regulation (EU) 2016/679 or Regulation (EU) 2018/1725, as applicable.
      4. +
    4. The Parties agree that if the data exporter is held liable under paragraph (c) for damages caused by the data importer (or its sub-processor), it shall be entitled to claim back from the data importer that part of the compensation corresponding to the data importer’s responsibility for the damage.
      5. +
    5. Where more than one Party is responsible for any damage caused to the data subject as a result of a breach of these Clauses, all responsible Parties shall be jointly and severally liable and the data subject is entitled to bring an action in court against any of these Parties.
      6. +
    6. The Parties agree that if one Party is held liable under paragraph (e), it shall be entitled to claim back from the other Party/ies that part of the compensation corresponding to its/their responsibility for the damage.
      7. +
    7. The data importer may not invoke the conduct of a sub-processor to avoid its own liability.
      8. +
    + +##### Clause 13 + +**Supervision** + +
      +
    1. [Where the data exporter is established in an EU Member State:] The supervisory authority with responsibility for ensuring compliance by the data exporter with Regulation (EU) 2016/679 as regards the data transfer, as indicated in Annex I.C, shall act as competent supervisory authority.

      + [Where the data exporter is not established in an EU Member State, but falls within the territorial scope of application of Regulation (EU) 2016/679 in accordance with its Article 3(2) and has appointed a representative pursuant to Article 27(1) of Regulation (EU) 2016/679:] The supervisory authority of the Member State in which the representative within the meaning of Article 27(1) of Regulation (EU) 2016/679 is established, as indicated in Annex I.C, shall act as competent supervisory authority.

      + [Where the data exporter is not established in an EU Member State, but falls within the territorial scope of application of Regulation (EU) 2016/679 in accordance with its Article 3(2) without however having to appoint a representative pursuant to Article 27(2) of Regulation (EU) 2016/679:] The supervisory authority of one of the Member States in which the data subjects whose personal data is transferred under these Clauses in relation to the offering of goods or services to them, or whose behaviour is monitored, are located, as indicated in Annex I.C, shall act as competent supervisory authority.

      2. +
    2. The data importer agrees to submit itself to the jurisdiction of and cooperate with the competent supervisory authority in any procedures aimed at ensuring compliance with these Clauses. In particular, the data importer agrees to respond to enquiries, submit to audits and comply with the measures adopted by the supervisory authority, including remedial and compensatory measures. It shall provide the supervisory authority with written confirmation that the necessary actions have been taken.
      3. +
    + +#### SECTION III – LOCAL LAWS AND OBLIGATIONS IN CASE OF ACCESS BY PUBLIC AUTHORITIES + +##### Clause 14 + +**Local laws and practices affecting compliance with the Clauses** + +
      +
    1. The Parties warrant that they have no reason to believe that the laws and practices in the third country of destination applicable to the processing of the personal data by the data importer, including any requirements to disclose personal data or measures authorising access by public authorities, prevent the data importer from fulfilling its obligations under these Clauses. This is based on the understanding that laws and practices that respect the essence of the fundamental rights and freedoms and do not exceed what is necessary and proportionate in a democratic society to safeguard one of the objectives listed in Article 23(1) of Regulation (EU) 2016/679, are not in contradiction with these Clauses.
      2. +
    2. The Parties declare that in providing the warranty in paragraph (a), they have taken due account in particular of the following elements:
      3. +
        +
      1. the specific circumstances of the transfer, including the length of the processing chain, the number of actors involved and the transmission channels used; intended onward transfers; the type of recipient; the purpose of processing; the categories and format of the transferred personal data; the economic sector in which the transfer occurs; the storage location of the data transferred;
        2. +
      2. the laws and practices of the third country of destination– including those requiring the disclosure of data to public authorities or authorising access by such authorities – relevant in light of the specific circumstances of the transfer, and the applicable limitations and safeguards (3);
        3. +
      3. any relevant contractual, technical or organisational safeguards put in place to supplement the safeguards under these Clauses, including measures applied during transmission and to the processing of the personal data in the country of destination.
        4. +
      +
    3. The data importer warrants that, in carrying out the assessment under paragraph (b), it has made its best efforts to provide the data exporter with relevant information and agrees that it will continue to cooperate with the data exporter in ensuring compliance with these Clauses.
      4. +
    4. The Parties agree to document the assessment under paragraph (b) and make it available to the competent supervisory authority on request.
      5. +
    5. The data importer agrees to notify the data exporter promptly if, after having agreed to these Clauses and for the duration of the contract, it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under paragraph (a), including following a change in the laws of the third country or a measure (such as a disclosure request) indicating an application of such laws in practice that is not in line with the requirements in paragraph (a).
      6. +
    6. Following a notification pursuant to paragraph (e), or if the data exporter otherwise has reason to believe that the data importer can no longer fulfil its obligations under these Clauses, the data exporter shall promptly identify appropriate measures (e.g. technical or organisational measures to ensure security and confidentiality) to be adopted by the data exporter and/or data importer to address the situation. The data exporter shall suspend the data transfer if it considers that no appropriate safeguards for such transfer can be ensured, or if instructed by the competent supervisory authority to do so. In this case, the data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses. If the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise. Where the contract is terminated pursuant to this Clause, Clause 16(d) and (e) shall apply.
      7. +
    + +##### Clause 15 + +**Obligations of the data importer in case of access by public authorities** + +**15.1 Notification** + +
      +
    1. The data importer agrees to notify the data exporter and, where possible, the data subject promptly (if necessary with the help of the data exporter) if it:
      2. +
        +
      1. receives a legally binding request from a public authority, including judicial authorities, under the laws of the country of destination for the disclosure of personal data transferred pursuant to these Clauses; such notification shall include information about the personal data requested, the requesting authority, the legal basis for the request and the response provided; or
        2. +
      2. becomes aware of any direct access by public authorities to personal data transferred pursuant to these Clauses in accordance with the laws of the country of destination; such notification shall include all information available to the importer.
        3. +
      +
    2. If the data importer is prohibited from notifying the data exporter and/or the data subject under the laws of the country of destination, the data importer agrees to use its best efforts to obtain a waiver of the prohibition, with a view to communicating as much information as possible, as soon as possible. The data importer agrees to document its best efforts in order to be able to demonstrate them on request of the data exporter.
      3. +
    3. Where permissible under the laws of the country of destination, the data importer agrees to provide the data exporter, at regular intervals for the duration of the contract, with as much relevant information as possible on the requests received (in particular, number of requests, type of data requested, requesting authority/ies, whether requests have been challenged and the outcome of such challenges, etc.).
      4. +
    4. The data importer agrees to preserve the information pursuant to paragraphs (a) to (c) for the duration of the contract and make it available to the competent supervisory authority on request.
      5. +
    5. Paragraphs (a) to (c) are without prejudice to the obligation of the data importer pursuant to Clause 14(e) and Clause 16 to inform the data exporter promptly where it is unable to comply with these Clauses.
      6. +
    + +**15.2 Review of legality and data minimisation** + +
      +
    1. The data importer agrees to review the legality of the request for disclosure, in particular whether it remains within the powers granted to the requesting public authority, and to challenge the request if, after careful assessment, it concludes that there are reasonable grounds to consider that the request is unlawful under the laws of the country of destination, applicable obligations under international law and principles of international comity. The data importer shall, under the same conditions, pursue possibilities of appeal. When challenging a request, the data importer shall seek interim measures with a view to suspending the effects of the request until the competent judicial authority has decided on its merits. It shall not disclose the personal data requested until required to do so under the applicable procedural rules. These requirements are without prejudice to the obligations of the data importer under Clause 14(e).
      2. +
    2. The data importer agrees to document its legal assessment and any challenge to the request for disclosure and, to the extent permissible under the laws of the country of destination, make the documentation available to the data exporter. It shall also make it available to the competent supervisory authority on request.
      3. +
    3. The data importer agrees to provide the minimum amount of information permissible when responding to a request for disclosure, based on a reasonable interpretation of the request.
      4. +
    + +#### SECTION IV – FINAL PROVISIONS + +##### Clause 16 + +**Non-compliance with the Clauses and termination** + +
      +
    1. The data importer shall promptly inform the data exporter if it is unable to comply with these Clauses, for whatever reason.
      2. +
    2. In the event that the data importer is in breach of these Clauses or unable to comply with these Clauses, the data exporter shall suspend the transfer of personal data to the data importer until compliance is again ensured or the contract is terminated. This is without prejudice to Clause 14(f).
      3. +
    3. The data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses, where:
      4. +
        +
      1. the data exporter has suspended the transfer of personal data to the data importer pursuant to paragraph (b) and compliance with these Clauses is not restored within a reasonable time and in any event within one month of suspension;
        2. +
      2. the data importer is in substantial or persistent breach of these Clauses; or
        3. +
      3. the data importer fails to comply with a binding decision of a competent court or supervisory authority regarding its obligations under these Clauses.
        4. +

      + In these cases, it shall inform the competent supervisory authority of such non-compliance. Where the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise. +
    4. Personal data that has been transferred prior to the termination of the contract pursuant to paragraph (c) shall at the choice of the data exporter immediately be returned to the data exporter or deleted in its entirety. The same shall apply to any copies of the data. The data importer shall certify the deletion of the data to the data exporter. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit the return or deletion of the transferred personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process the data to the extent and for as long as required under that local law.
      5. +
    5. Either Party may revoke its agreement to be bound by these Clauses where (i) the European Commission adopts a decision pursuant to Article 45(3) of Regulation (EU) 2016/679 that covers the transfer of personal data to which these Clauses apply; or (ii) Regulation (EU) 2016/679 becomes part of the legal framework of the country to which the personal data is transferred. This is without prejudice to other obligations applying to the processing in question under Regulation (EU) 2016/679.
      6. +
    + +##### Clause 17 + +**Governing law** + +These Clauses shall be governed by the law of one of the EU Member States, provided such law allows for third-party beneficiary rights. The Parties agree that this shall be the law of the Netherlands. + +##### Clause 18 + +**Choice of forum and jurisdiction** + +
      +
    1. Any dispute arising from these Clauses shall be resolved by the courts of an EU Member State.
      2. +
    2. The Parties agree that those shall be the courts of the Netherlands.
      3. +
    3. A data subject may also bring legal proceedings against the data exporter and/or data importer before the courts of the Member State in which he/she has his/her habitual residence.
      4. +
    4. The Parties agree to submit themselves to the jurisdiction of such courts.
      5. +
    + +## ANNEX I + +**to the Standard Contractual Clauses (EU/EEA)** + +### A. LIST OF PARTIES + +**Data exporter(s)**: Customer is the data exporter
    Name: see GitHub Customer Agreement
    Address: see GitHub Customer Agreement
    Contact person’s name, position and contact details: see GitHub Customer Agreement
    Activities relevant to the data transferred under these Clauses:
    The data exporter is a user of Online Services or Professional Services as defined in the DPA and GitHub Customer Agreement.
    Signature and date: see GitHub Customer Agreement (the DPA and the Standard Contractual Clauses (EU/EEA) are incorporated into the GitHub Customer Agreement
    Role (controller/processor): controller (unless otherwise agreed in the Customer Agreement).
    + +**Data importer(s)**:
    Name: GitHub, Inc.
    Address: 88 Colin P Kelly Jr St, San Francisco, CA 94107, USA
    Contact person’s name, position and contact details: Frances Wiet, Head of Privacy, fwiet@github.com
    Activities relevant to the data transferred under these Clauses:
    GitHub, Inc. is a global producer of software and services
    Signature and date: see GitHub Customer Agreement (the DPA and the Standard Contractual Clauses (EU/EEA) are incorporated into the GitHub Customer Agreement)
    Role (controller/processor): processor or, depending on the agreements set forth in the Customer Agreement, subprocessor. + +### B. DESCRIPTION OF TRANSFER + +_Categories of data subjects whose personal data is transferred:_ + +Data subjects include the data exporter’s representatives and end-users including employees, contractors, collaborators, and customers of the data exporter. Data subjects may also include individuals attempting to communicate or transfer personal data to users of the services provided by data importer. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following types of data subjects in the personal data: +- Empregados, contratados e trabalhadores temporários (atual, anterior, potencial) do exportador de dados; +- Os colaboradores/pontos de contato do exportador de dados (pessoas físicas) ou funcionários, contratados ou trabalhadores temporários de colaboradores de entidades legais colaboradores/contactar pessoas (atual, potencial, anterior); +- Users and other data subjects that are users of data exporter's services; +- Partners, stakeholders or individuals who actively collaborate, communicate or otherwise interact with employees of the data exporter and/or use communication tools such as apps and websites provided by the data exporter. + +_Categories of personal data transferred:_ + +The personal data transferred that is included in e-mail, documents and other data in an electronic form in the context of the Online Services or Professional Services. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following categories in the personal data: +- Basic personal data (for example place of birth, street name and house number (address), postal code, city of residence, country of residence, mobile phone number, first name, last name, initials, email address, gender, date of birth); +- Authentication data (for example user name, password or PIN code, security question, audit trail); +- Contact information (for example addresses, email, phone numbers, social media identifiers; emergency contact details); +- Unique identification numbers and signatures (for example IP addresses, employee number, student number); +- Pseudonymous identifiers; +- Photos, video and audio; +- Internet activity (for example browsing history, search history, reading and viewing activities); +- Device identification (for example IMEI-number, SIM card number, MAC address); +- Profiling (for example based on observed criminal or anti-social behavior or pseudonymous profiles based on visited URLs, click streams, browsing logs, IP-addresses, domains, apps installed, or profiles based on marketing preferences); +- Special categories of data as voluntarily provided by data subjects (for example racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health, data concerning a natural person’s sex life or sexual orientation, or data relating to criminal convictions or offences); or +- Any other personal data identified in Article 4 of the GDPR. + +_**Sensitive data** transferred (if applicable) and applied restrictions or safeguards that fully take into consideration the nature of the data and the risks involved, such as for instance strict purpose limitation, access restrictions (including access only for staff having followed specialised training), keeping a record of access to the data, restrictions for onward transfers or additional security measures:_
    GitHub does not request or otherwise ask for sensitive data and receives such data only if and when customers or data subjects decide to provide it. + +_**The frequency of the transfer** (e.g. whether the data is transferred on a one-off or continuous basis):_ + +Continuous as part of the Online Services or Professional Services. + +_**Nature of the processing:**_ + +The personal data transferred will be subject to the following basic processing activities: +
      +
    1. Duration and Object of Data Processing. The duration of data processing shall be for the term designated under the applicable GitHub Customer Agreement between data exporter and the data importer. The objective of the data processing is the performance of Online Services and Professional Services.
      2. +
    2. Personal Data Access. For the term designated under the applicable GitHub Customer Agreement, data importer will, at its election and as necessary under applicable law, either: (1) provide data exporter with the ability to correct, delete, or block personal data, or (2) make such corrections, deletions, or blockages on its behalf.
      3. +
    3. Data Exporter’s Instructions. For Online Services and Professional Services, data importer will only act upon data exporter’s instructions.
      4. +
    + +_Purpose(s) of the data transfer and further processing:_ + +The scope and purpose of processing personal data is described in the “Processing of Personal Data; GDPR” section of the DPA. The data importer operates a global network of data centers and management/support facilities, and processing may take place in any jurisdiction where data importer or its sub-processors operate such facilities in accordance with the “Security Practices and Policies” section of the DPA. + +_The period for which the personal data will be retained, or, if that is not possible, the criteria used to determine that period:_ + +Upon expiration or termination of data exporter’s use of Online Services or Professional Services, it may extract personal data and data importer will delete personal data, each in accordance with the DPA Terms applicable to the agreement. + +_For transfers to (sub-) processors, also specify subject matter, nature and duration of the processing:_ + +In accordance with the DPA, the data importer may hire other companies to provide limited services on data importer’s behalf, such as providing customer support. Any such subcontractors will be permitted to obtain personal data only to deliver the services the data importer has retained them to provide, and they are prohibited from using personal data for any other purpose. Unless a particular subcontractor is replaced ahead of time, the processing will be for the term designated under the applicable GitHub Customer Agreement between data exporter and data importer. + +### C. COMPETENT SUPERVISORY AUTHORITY + +_Identify the competent supervisory authority/ies in accordance with Clause 13:_ + +The supervisory authority with responsibility for ensuring compliance by the data exporter with Regulation (EU) 2016/679.   +## ANNEX II + +**to the Standard Contractual Clauses (EU/EEA)** + +**TECHNICAL AND ORGANISATIONAL MEASURES INCLUDING TECHNICAL AND ORGANISATIONAL MEASURES TO ENSURE THE SECURITY OF THE DATA** + +_Description of the technical and organisational measures implemented by the data importer(s) (including any relevant certifications) to ensure an appropriate level of security, taking into account the nature, scope, context and purpose of the processing, and the risks for the rights and freedoms of natural persons._ + +
      +
    1. Data Security Certifications. Data importer holds the following data security certifications:
      2. +
        +
      • SOC 1, Type 2;
        • +
      • SOC 2, Type 2;
        • +
      • NIST, to the extent incorporated for FedRAMP Low-Impact / Tailored ATO.
        • +
      +
    2. Personnel. Data importer’s personnel will not process personal data without authorization. Personnel are obligated to maintain the confidentiality of any such personal data and this obligation continues even after their engagement ends.
      3. +
    3. Data Privacy Contact. The data privacy officer of the data importer can be reached at the following address:

      + GitHub, Inc.
      + Attn: Privacy
      + 88 Colin P. Kelly Jr. Street
      + San Francisco, California 94107 USA

      4. +
    4. Technical and Organization Measures. The data importer has implemented and will maintain appropriate technical and organizational measures, internal controls, and information security routines intended to protect personal data, as defined in the Security Practices and Policies section of the DPA, against accidental loss, destruction, or alteration; unauthorized disclosure or access; or unlawful destruction as follows: The technical and organizational measures, internal controls, and information security routines set forth in the Data Security section of the DPA are hereby incorporated into this Annex II to Attachment 1 by this reference and are binding on the data importer as if they were set forth in this Annex 2 to Attachment 1 in their entirety.
      5. +
    + +_For transfers to (sub-) processors, also describe the specific technical and organisational measures to be taken by the (sub-) processor to be able to provide assistance to the controller and, for transfers from a processor to a sub-processor, to the data exporter:_ + +**Vendor management program - third-party risk program** + +The data importer has a vendor risk assessment process, vendor contract clauses and additional data protection agreements with vendors. Vendors undergo reassessment when a new business use case is requested. The data importer’s vendor risk program is structured so all of data importer’s vendors' risk assessments are refreshed two years from the last review date. + +Vendors deemed high risk, such as data center providers or other vendors storing or processing data in scope for the data importer’s regulatory or contractual requirements, undergo reassessment annually. + +## ANNEX III + +**to the Standard Contractual Clauses (EU/EEA)** + +**Additional Safeguards Addendum** + +By this Additional Safeguards Addendum to Standard Contractual Clauses (EU/EEA) (this “Addendum”), GitHub, Inc. (“GitHub”) provides additional safeguards to Customer and additional redress to the data subjects to whom Customer’s personal data relates. + +This Addendum supplements and is made part of, but is not in variation or modification of, the Standard Contractual Clauses (EU/EEA). + +
      +
    1. Challenges to Orders. In addition to Clause 15.1 of the Standard Contractual Clauses (EU/EEA), in the event GitHub receives an order from any third party for compelled disclosure of any personal data that has been transferred under the Standard Contractual Clauses (EU/EEA), GitHub shall:
      2. +
        +
      1. use every reasonable effort to redirect the third party to request data directly from Customer;
        2. +
      2. promptly notify Customer, unless prohibited under the law applicable to the requesting third party, and, if prohibited from notifying Customer, use all lawful efforts to obtain the right to waive the prohibition in order to communicate as much information to Customer as soon as possible; and
        3. +
      3. use all lawful efforts to challenge the order for disclosure on the basis of any legal deficiencies under the laws of the requesting party or any relevant conflicts with the law of the European Union or applicable Member State law.
        4. +

      + For purpose of this section, lawful efforts do not include actions that would result in civil or criminal penalty such as contempt of court under the laws of the relevant jurisdiction. +
    2. Indemnification of Data Subjects. Subject to Sections 3 and 4, GitHub shall indemnify a data subject for any material or non-material damage to the data subject caused by GitHub’s disclosure of personal data of the data subject that has been transferred under the Standard Contractual Clauses (EU/EEA) in response to an order from a non-EU/EEA government body or law enforcement agency (a “Relevant Disclosure”). Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under this Section 2 to the extent the data subject has already received compensation for the same damage, whether from GitHub or otherwise.
      3. +
    3. Conditions of Indemnification. Indemnification under Section 2 is conditional upon the data subject establishing, to GitHub’s reasonable satisfaction, that:
      4. +
        +
      1. GitHub engaged in a Relevant Disclosure;
        2. +
      2. the Relevant Disclosure was the basis of an official proceeding by the non-EU/EEA government body or law enforcement agency against the data subject; and
        3. +
      3. the Relevant Disclosure directly caused the data subject to suffer material or non-material damage.
        4. +

      + The data subject bears the burden of proof with respect to conditions a. though c.
      + Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under Section 2 if GitHub establishes that the Relevant Disclosure did not violate its obligations under Chapter V of the GDPR.
      +
    4. Scope of Damages. Indemnification under Section 2 is limited to material and non-material damages as provided in the GDPR and excludes consequential damages and all other damages not resulting from GitHub’s infringement of the GDPR.
      5. +
    5. Exercise of Rights. Rights granted to data subjects under this Addendum may be enforced by the data subject against GitHub irrespective of any restriction in Clauses 3 or 12 of the Standard Contractual Clauses (EU/EEA). The data subject may only bring a claim under this Addendum on an individual basis, and not part of a class, collective, group or representative action. Rights granted to data subjects under this Addendum are personal to the data subject and may not be assigned.
      6. +
    6. Notice of Change. In addition to Clause 14 of the Standard Contractual Clauses (EU/EEA), GitHub agrees and warrants that it has no reason to believe that the legislation applicable to it or its sub-processors, including in any country to which personal data is transferred either by itself or through a sub-processor, prevents it from fulfilling the instructions received from the data exporter and its obligations under this Addendum or the Standard Contractual Clauses (EU/EEA) and that in the event of a change in this legislation which is likely to have a substantial adverse effect on the warranties and obligations provided by this Addendum or the Standard Contractual Clauses (EU/EEA), it will promptly notify the change to Customer as soon as it is aware, in which case Customer is entitled to suspend the transfer of data and/or terminate the contract.
      7. +
    7. Termination. This Addendum shall automatically terminate if the European Commission, a competent Member State supervisory authority, or an EU or competent Member State court approves a different lawful transfer mechanism that would be applicable to the data transfers covered by the Standard Contractual Clauses (EU/EEA) (and if such mechanism applies only to some of the data transfers, this Addendum will terminate only with respect to those transfers) and that does not require the additional safeguards set forth in this Addendum.
      8. +
    + +

    Attachment 2 – The Standard Contractual Clauses (UK)

    + +Execution of the GitHub Customer Agreement by Customer includes execution of this Attachment 2, which is countersigned by GitHub, Inc. + +Em países onde a aprovação regulatória é necessária para o uso das Cláusulas Contratuais Padrão, estas não podem ser confiadas à Comissão Europeia 2010/87/UE (de fevereiro de 2010) para legitimar a exportação de dados do país, a menos que o Cliente tenha a aprovação regulatória necessária. + +Beginning May 25, 2018 and thereafter, references to various Articles from the Directive 95/46/EC in the Standard Contractual Clauses below will be treated as references to the relevant and appropriate Articles in the GDPR. + +For the purposes of Article 26(2) of Directive 95/46/EC for the transfer of personal data to processors established in third countries which do not ensure an adequate level of data protection, Customer (as data exporter) and GitHub, Inc. (as data importer, whose signature appears below), each a “party,” together “the parties,” have agreed on the following Contractual Clauses (the “Clauses” or “Standard Contractual Clauses”) in order to adduce adequate safeguards with respect to the protection of privacy and fundamental rights and freedoms of individuals for the transfer by the data exporter to the data importer of the personal data specified in Appendix 1. + +### Cláusula 1: Definições + +
      +
    1. 'personal data', 'special categories of data', 'process/processing', 'controller', 'processor', 'data subject' and 'supervisory authority' shall have the same meaning as in Directive 95/46/EC of the European Parliament and of the Council of 24 October 1995 on the protection of individuals with regard to the processing of personal data and on the free movement of such data;
      2. +
    2. 'the data exporter' means the controller who transfers the personal data;
      3. +
    3. 'the data importer' means the processor who agrees to receive from the data exporter personal data intended for processing on his behalf after the transfer in accordance with his instructions and the terms of the Clauses and who is not subject to a third country's system ensuring adequate protection within the meaning of Article 25(1) of Directive 95/46/EC;
      4. +
    4. 'the subprocessor' means any processor engaged by the data importer or by any other subprocessor of the data importer who agrees to receive from the data importer or from any other subprocessor of the data importer personal data exclusively intended for processing activities to be carried out on behalf of the data exporter after the transfer in accordance with his instructions, the terms of the Clauses and the terms of the written subcontract;
      5. +
    5. 'the applicable data protection law' means the legislation protecting the fundamental rights and freedoms of individuals and, in particular, their right to privacy with respect to the processing of personal data applicable to a data controller in the Member State in which the data exporter is established;
      6. +
    6. 'technical and organisational security measures' means those measures aimed at protecting personal data against accidental or unlawful destruction or accidental loss, alteration, unauthorised disclosure or access, in particular where the processing involves the transmission of data over a network, and against all other unlawful forms of processing.
      7. +
    + +### Cláusula 2: Detalhes da transferência + +Os detalhes da transferência e em particular as categorias especiais de dados pessoais quando aplicáveis estão especificadas no Apêndice 1 abaixo, que constitui parte integral das Cláusulas. + +### Cláusula 3: Cláusula de beneficiário de terceiros + +
      +
    1. O titular dos dados pode impor contra o exportador de dados esta Cláusula, a Cláusula 4(b) para (i), Cláusula 5(a) para (e), e (g) para (j), a Cláusula 6(1) e (2), a Cláusula 7, Cláusula 8(2), e as Cláusulas 9 a 12 como beneficiário de terceiros.
      2. +
    2. O titular dos dados pode aplicar contra o importador de dados esta Cláusula, a Cláusula 5(a) para (e) e (g), a Cláusula 6, a Cláusula 7, a Cláusula 8(2), e as Cláusulas 9 a 12, nos casos em que o exportador de dados desapareceu factualmente ou deixou de existir perante a lei, a menos que qualquer entidade sucessora tenha assumido todas as obrigações legais do exportador de dados por contrato ou por aplicação da lei. em resultado do qual assume os direitos e obrigações do exportador de dados. Nesse caso, a questão dos dados pode impô-los contra essa entidade.
      3. +
    3. O titular dos dados pode impor contra o subprocessador esta Cláusula, a Cláusula 5(a) para (e) e (g), a Cláusula 6, a Cláusula 7, a Cláusula 8(2), e as Cláusulas 9 a 12, nos casos em que tanto o exportador como o importador de dados desapareceram ou deixaram de existir perante a lei ou tornaram-se insolventes, a menos que qualquer entidade sucessora tenha assumido todas as obrigações legais do exportador de dados por contrato ou pelo funcionamento da lei, assumindo, como resultado, os direitos e obrigações do exportador de dados, em cujo caso, o titular dos dados pode impô-los contra essa entidade. Essa responsabilidade de terceiros do subprocessador estará limitada às suas próprias operações de processamento nos termos das Cláusulas.
      4. +
    4. As partes não se opõem, caso o titular dos dados seja representado por uma associação ou outro organismo se, expressamente, assim o desejar e a legislação nacional o permitir.
      5. +
    + +### Cláusula 4: Obrigações do exportador de dados + +O exportador de dados concorda e garante: + +
      +
    1. that the processing, including the transfer itself, of the personal data has been and will continue to be carried out in accordance with the relevant provisions of the applicable data protection law (and, where applicable, has been notified to the relevant authorities of the Member State where the data exporter is established) and does not violate the relevant provisions of that State;
      2. +
    2. that it has instructed and throughout the duration of the personal data processing services will instruct the data importer to process the personal data transferred only on the data exporter's behalf and in accordance with the applicable data protection law and the Clauses;
      3. +
    3. that the data importer will provide sufficient guarantees in respect of the technical and organisational security measures specified in Appendix 2 below;
      4. +
    4. that after assessment of the requirements of the applicable data protection law, the security measures are appropriate to protect personal data against accidental or unlawful destruction or accidental loss, alteration, unauthorised disclosure or access, in particular where the processing involves the transmission of data over a network, and against all other unlawful forms of processing, and that these measures ensure a level of security appropriate to the risks presented by the processing and the nature of the data to be protected having regard to the state of the art and the cost of their implementation;
      5. +
    5. that it will ensure compliance with the security measures;
      6. +
    6. that, if the transfer involves special categories of data, the data subject has been informed or will be informed before, or as soon as possible after, the transfer that its data could be transmitted to a third country not providing adequate protection within the meaning of Directive 95/46/EC;
      7. +
    7. to forward any notification received from the data importer or any subprocessor pursuant to Clause 5(b) and Clause 8(3) to the data protection supervisory authority if the data exporter decides to continue the transfer or to lift the suspension;
      8. +
    8. to make available to the data subjects upon request a copy of the Clauses, with the exception of Appendix 2, and a summary description of the security measures, as well as a copy of any contract for subprocessing services which has to be made in accordance with the Clauses, unless the Clauses or the contract contain commercial information, in which case it may remove such commercial information;
      9. +
    9. that, in the event of subprocessing, the processing activity is carried out in accordance with Clause 11 by a subprocessor providing at least the same level of protection for the personal data and the rights of data subject as the data importer under the Clauses; and
      10. +
    10. that it will ensure compliance with Clause 4(a) to (i).
      11. +
    + +### Cláusula 5: Obrigações do importador de dados + +O importador de dados concorda e garante: + +
      +
    1. to process the personal data only on behalf of the data exporter and in compliance with its instructions and the Clauses; if it cannot provide such compliance for whatever reasons, it agrees to inform promptly the data exporter of its inability to comply, in which case the data exporter is entitled to suspend the transfer of data and/or terminate the contract;
      2. +
    2. that it has no reason to believe that the legislation applicable to it prevents it from fulfilling the instructions received from the data exporter and its obligations under the contract and that in the event of a change in this legislation which is likely to have a substantial adverse effect on the warranties and obligations provided by the Clauses, it will promptly notify the change to the data exporter as soon as it is aware, in which case the data exporter is entitled to suspend the transfer of data and/or terminate the contract;
      3. +
    3. that it has implemented the technical and organisational security measures specified in Appendix 2 before processing the personal data transferred;
      4. +
    4. that it will promptly notify the data exporter about:
      5. +
        +
      1. any legally binding request for disclosure of the personal data by a law enforcement authority unless otherwise prohibited, such as a prohibition under criminal law to preserve the confidentiality of a law enforcement investigation,
        2. +
      2. any accidental or unauthorised access, and
        3. +
      3. any request received directly from the data subjects without responding to that request, unless it has been otherwise authorised to do so;
        4. +
      + to deal promptly and properly with all inquiries from the data exporter relating to its processing of the personal data subject to the transfer and to abide by the advice of the supervisory authority with regard to the processing of the data transferred; + at the request of the data exporter to submit its data processing facilities for audit of the processing activities covered by the Clauses which shall be carried out by the data exporter or an inspection body composed of independent members and in possession of the required professional qualifications bound by a duty of confidentiality, selected by the data exporter, where applicable, in agreement with the supervisory authority; +
    5. to make available to the data subject upon request a copy of the Clauses, or any existing contract for subprocessing, unless the Clauses or contract contain commercial information, in which case it may remove such commercial information, with the exception of Appendix 2 which shall be replaced by a summary description of the security measures in those cases where the data subject is unable to obtain a copy from the data exporter;
      6. +
    6. that, in the event of subprocessing, it has previously informed the data exporter and obtained its prior written consent;
      7. +
    7. that the processing services by the subprocessor will be carried out in accordance with Clause 11; and
      8. +
    8. to send promptly a copy of any subprocessor agreement it concludes under the Clauses to the data exporter.
      9. +
    + +### Cláusula 6: Responsabilidade + +
      +
    1. As partes concordam que qualquer titular de dados que tenha sofrido danos em consequência de qualquer violação das obrigações referidas na Cláusula 3 ou na Cláusula 11 por qualquer parte ou subprocessador tem o direito de receber compensação do exportador de dados pelos danos sofridos.
      2. + +
    2. If a data subject is not able to bring a claim for compensation in accordance with paragraph 1 against the data exporter, arising out of a breach by the data importer or his subprocessor of any of their obligations referred to in Clause 3 or in Clause 11, because the data exporter has factually disappeared or ceased to exist in law or has become insolvent, the data importer agrees that the data subject may issue a claim against the data importer as if it were the data exporter, unless any successor entity has assumed the entire legal obligations of the data exporter by contract of by operation of law, in which case the data subject can enforce its rights against such entity.

      + The data importer may not rely on a breach by a subprocessor of its obligations in order to avoid its own liabilities.
      3. + +
    3. Se um titular de dados não puder apresentar uma reivindicação contra o exportador ou o importador de dados referido nos parágrafos 1 e 2, decorrente de uma violação por parte do subprocessador de qualquer uma das suas obrigações referidas na Cláusula 3 ou 11, porque tanto o exportador como o importador de dados desapareceram ou deixaram de existir perante a lei ou tornaram-se insolventes, o subprocessador concorda que o titular dos dados poderá interpor uma reivindicação contra o subprocessador de dados no que diz respeito às suas próprias operações de processamento nos termos das Cláusulas como se fosse o exportador ou o importador de dados, salvo se qualquer entidade sucessora tenha assumido todas as obrigações legais do exportador ou do importador de dados por contrato ou por exercício da lei. Nesse caso, a o titular dos dados poderá impor seus direitos contra tal entidade. A responsabilidade do subprocessador é limitada às suas próprias atividades de processamento de dados nos termos previstas nas Cláusulas.
      4. +
    + +### Cláusula 7: Mediação e jurisdição + +
      +
    1. O importador de dados concorda que, se o titular dos dados pode invocar contra ele direitos de terceiros beneficiários e/ou reivindicar compensação por dados de acordo com as Cláusulas, o importador de dados irá aceitar a decisão do titular de dados: +
        +
      1. to refer the dispute to mediation, by an independent person or, where applicable, by the supervisory authority; +
      2. to refer the dispute to the courts in the Member State in which the data exporter is established. +
      +
    2. As partes concordam que a escolha feita pelo titular dos dados não prejudicará os seus direitos substantivos ou processuais de procurar recursos de acordo com as disposições da lei nacional ou internacional. +
    + +### Cláusula 8: Cooperação com as autoridades de supervisão + +
      +
    1. O exportador de dados concorda em depositar um exemplar deste contrato junto da autoridade de controle se esta assim requerer ou se a legislação de proteção de dados aplicável exigir.
      2. + +
    2. As partes concordam que a autoridade de supervisão tem o direito de realizar auditorias no importador de dados ou a qualquer subprocessador, que tenha o mesmo escopo e as mesmas condições das auditorias executadas no exportador de dados, em conformidade com a legislação de proteção de dados aplicável.
      3. + +
    3. O importador de dados deve prontamente informar o exportador de dados sobre a existência de legislação aplicável sobre tal ato, e de qualquer subprocessador que previna a condução de uma auditoria ao importador de dados, ou qualquer subprocessador, em conformidade com o parágrafo 2. Neste caso, o exportador de dados terá o direito de tomar as medidas previstas na Cláusula 5(b).
      4. +
    + +### Cláusula 9: Lei regente. + +As Cláusulas devem ser regidas pela lei do Estado-Membro onde o exportador de dados estiver estabelecido. + +### Cláusula 10: Variação do contrato + +As partes comprometem-se a não alterar as Cláusulas. Isso não impede que as partes adicionem cláusulas de caráter comercial sempre que necessário, desde que as mesmas não contrariem a Cláusula. + +### Cláusula 11: Subprocessamento + +
      +
    1. O importador de dados não deve subcontratar nenhuma de suas operações de processamento em nome do exportador de dados sob as Cláusulas sem o consentimento prévio por escrito do exportador de dados. Quando o importador de dados subcontratar suas obrigações sob as Cláusulas, com o consentimento do exportador, ele deverá fazê-lo somente por meio de um contrato por escrito com o subprocessador, que imponha a este as mesmas obrigações impostas ao importador de dados nos termos das Cláusulas. Nos casos em que o subcontratante não cumprir as suas obrigações de proteção de dados nos termos de tal contrato por escrito, o importador de dados permanecerá totalmente responsável perante o exportador de dados pelo desempenho das obrigações do subprocessador nos termos desse contrato.
      2. + +
    2. O contrato prévio por escrito entre o importador de dados e o subprocessador prevê também uma cláusula de beneficiário de terceiros, conforme estabelecido na Cláusula 3, para os casos em que o titular de dados não for capaz de interpor a reivindicação para a compensação referida no parágrafo 1 da Cláusula 6 contra o exportador ou o importador de dados porque eles desapareceram factualmente ou deixaram de existir perante lei ou tornaram-se insolventes, e nenhuma entidade sucessora assumiu todas as obrigações legais do exportador de dados ou importador de dados por contrato ou por operação da lei. Essa responsabilidade de terceiros do subprocessador estará limitada às suas próprias operações de processamento nos termos das Cláusulas.
      3. + +
    3. As disposições relativas aos aspectos de proteção de dados para o subprocessamento do contrato referido no parágrafo 1 serão regidas pela lei do Estado-Membro onde o exportador de dados estiver estabelecido.
      4. + +
    4. O exportador de dados deve manter uma lista dos acordos de subprocessamento concluídos sob as Cláusulas e notificados pelo importador de dados em conformidade com a Cláusula 5 (j), que deve ser atualizada pelo menos uma vez por ano. A lista deve estar disponível para a autoridade responsável pela supervisão da proteção de dados do exportador.
      5. +
    + +### Cláusula 12: Obrigação após a rescisão dos serviços de processamento de dados pessoais + +
      +
    1. As partes estão de acordo quanto à rescisão da prestação de serviços de processamento de dados, o importador de dados e o subprocessador, mediante a escolha do exportador de dados, devolverão todos os dados pessoais transferidos e as suas cópias ao exportador de dados ou destruirão todos os dados pessoais, e informarão ao exportador de dados que o procedimento foi realizado, a menos que a legislação imposta ao importador de dados os impeça de devolver ou de destruir a totalidade ou parte dos dados pessoais transferidos. Nesse caso, o importador de dados irá garantir a confidencialidade dos dados pessoais transferidos e não processará mais ativamente os dados pessoais transferidos.
      2. + +
    2. O importador de dados e o subprocessador garantem que, mediante solicitação do exportador de dados e/ou da autoridade supervisora, submeterão as suas instalações de processamento de dados a uma auditoria das medidas referidas no parágrafo 1.
      3. +
    + +### Appendix 1 to the Standard Contractual Clauses (UK) + +**Data exporter**: Customer is the data exporter. The data exporter is a user of Online Services or Professional Services as defined in the DPA and GitHub Customer Agreement. + +**Data importer**: The data importer is GitHub, Inc., a global producer of software and services. + +**Data subjects**: Data subjects include the data exporter’s representatives and end-users including employees, contractors, collaborators, and customers of the data exporter. Data subjects may also include individuals attempting to communicate or transfer personal data to users of the services provided by data importer. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following types of data subjects in the personal data: +- Empregados, contratados e trabalhadores temporários (atual, anterior, potencial) do exportador de dados; +- Os colaboradores/pontos de contato do exportador de dados (pessoas físicas) ou funcionários, contratados ou trabalhadores temporários de colaboradores de entidades legais colaboradores/contactar pessoas (atual, potencial, anterior); +- Users and other data subjects that are users of data exporter's services; +- Partners, stakeholders or individuals who actively collaborate, communicate or otherwise interact with employees of the data exporter and/or use communication tools such as apps and websites provided by the data exporter. + +**Categories of data**: The personal data transferred that is included in e-mail, documents and other data in an electronic form in the context of the Online Services or Professional Services. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following categories in the personal data: +- Basic personal data (for example place of birth, street name and house number (address), postal code, city of residence, country of residence, mobile phone number, first name, last name, initials, email address, gender, date of birth); +- Authentication data (for example user name, password or PIN code, security question, audit trail); +- Contact information (for example addresses, email, phone numbers, social media identifiers; emergency contact details); +- Unique identification numbers and signatures (for example IP addresses, employee number, student number); +- Pseudonymous identifiers; +- Photos, video and audio; +- Internet activity (for example browsing history, search history, reading and viewing activities); +- Device identification (for example IMEI-number, SIM card number, MAC address); +- Profiling (for example based on observed criminal or anti-social behavior or pseudonymous profiles based on visited URLs, click streams, browsing logs, IP-addresses, domains, apps installed, or profiles based on marketing preferences); +- Special categories of data as voluntarily provided by data subjects (for example racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health, data concerning a natural person’s sex life or sexual orientation, or data relating to criminal convictions or offences); or +- Any other personal data identified in Article 4 of the GDPR. + +**Processing operations**: The personal data transferred will be subject to the following basic processing activities: + +
      +
    1. Duration and Object of Data Processing. The duration of data processing shall be for the term designated under the applicable GitHub Customer Agreement between data exporter and data importer. The objective of the data processing is the performance of Online Services and Professional Services.
      2. +
    2. Scope and Purpose of Data Processing. The scope and purpose of processing personal data is described in the “Processing of Personal Data; GDPR” section of the DPA. The data importer operates a global network of data centers and management/support facilities, and processing may take place in any jurisdiction where data importer or its sub-processors operate such facilities in accordance with the “Security Practices and Policies” section of the DPA.
      3. +
    3. Personal Data Access. For the term designated under the applicable GitHub Customer Agreement data importer will at its election and as necessary under applicable law, either: (1) provide data exporter with the ability to correct, delete, or block personal data, or (2) make such corrections, deletions, or blockages on its behalf.
      4. +
    4. Data Exporter’s Instructions. For Online Services and Professional Services, data importer will only act upon data exporter’s instructions as conveyed by GitHub.
      5. +
    5. Personal Data Deletion or Return. Upon expiration or termination of data exporter’s use of Online Services or Professional Services, it may extract personal data and data importer will delete personal data, each in accordance with the DPA Terms applicable to the agreement.
      6. +
    + +**Subcontractors**: In accordance with the DPA, the data importer may hire other companies to provide limited services on data importer’s behalf, such as providing customer support. Any such subcontractors will be permitted to obtain personal data only to deliver the services the data importer has retained them to provide, and they are prohibited from using personal data for any other purpose. + +### Appendix 2 to the Standard Contractual Clauses (UK) + +Descrição das medidas de segurança técnicas e organizacionais implementadas pelo importador de dados, de acordo com as Cláusulas 4(d) e 5(c): + +
      +
    1. Personnel. Data importer’s personnel will not process personal data without authorization. Personnel are obligated to maintain the confidentiality of any such personal data and this obligation continues even after their engagement ends.
      2. + +
    2. Data Privacy Contact. The data privacy officer of the data importer can be reached at the following address:
      +GitHub, Inc.
      +Attn: Privacy
      +88 Colin P. Kelly Jr. Street
      +San Francisco, California 94107 USA
      3. + +
    3. Technical and Organization Measures. The data importer has implemented and will maintain appropriate technical and organizational measures, internal controls, and information security routines intended to protect personal data, as defined in the Security Practices and Policies section of the DPA, against accidental loss, destruction, or alteration; unauthorized disclosure or access; or unlawful destruction as follows: The technical and organizational measures, internal controls, and information security routines set forth in the Security Practices and Policies section of the DPA are hereby incorporated into this Appendix 2 by this reference and are binding on the data importer as if they were set forth in this Appendix 2 in their entirety.
      4. +
    + +### Appendix 3 to the Standard Contractual Clauses (UK) + +**Additional Safeguards Addendum** + +By this Additional Safeguards Addendum to Standard Contractual Clauses (UK) (this “Addendum”), GitHub, Inc. (“GitHub”) provides additional safeguards to Customer and additional redress to the data subjects to whom Customer’s personal data relates. + +This Addendum supplements and is made part of, but is not in variation or modification of, the Standard Contractual Clauses (UK). + +
      +
    1. Challenges to Orders. In addition to Clause 5(d)(i) of the Standard Contractual Clauses (UK), in the event GitHub receives an order from any third party for compelled disclosure of any personal data that has been transferred under the Standard Contractual Clauses (UK), GitHub shall:
      2. +
        +
      1. use every reasonable effort to redirect the third party to request data directly from Customer;
        2. +
      2. promptly notify Customer, unless prohibited under the law applicable to the requesting third party, and, if prohibited from notifying Customer, use all lawful efforts to obtain the right to waive the prohibition in order to communicate as much information to Customer as soon as possible; and
        3. +
      3. use all lawful efforts to challenge the order for disclosure on the basis of any legal deficiencies under the laws of the requesting party or any relevant conflicts with the law of the European Union or applicable Member State law.
        4. +

      + For purpose of this section, lawful efforts do not include actions that would result in civil or criminal penalty such as contempt of court under the laws of the relevant jurisdiction. +
    2. Indemnification of Data Subjects. Subject to Sections 3 and 4, GitHub shall indemnify a data subject for any material or non-material damage to the data subject caused by GitHub’s disclosure of personal data of the data subject that has been transferred under the Standard Contractual Clauses (UK) in response to an order from a non-EU/EEA government body or law enforcement agency (a “Relevant Disclosure”). Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under this Section 2 to the extent the data subject has already received compensation for the same damage, whether from GitHub or otherwise.
      3. +
    3. Conditions of Indemnification. Indemnification under Section 2 is conditional upon the data subject establishing, to GitHub’s reasonable satisfaction, that:
      4. +
        +
      1. GitHub engaged in a Relevant Disclosure;
        2. +
      2. the Relevant Disclosure was the basis of an official proceeding by the non-EU/EEA government body or law enforcement agency against the data subject; and
        3. +
      3. the Relevant Disclosure directly caused the data subject to suffer material or non-material damage.
        4. +

      + The data subject bears the burden of proof with respect to conditions a. though c.
      + Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under Section 2 if GitHub establishes that the Relevant Disclosure did not violate its obligations under Chapter V of the GDPR. +
    4. Scope of Damages. Indemnification under Section 2 is limited to material and non-material damages as provided in the GDPR and excludes consequential damages and all other damages not resulting from GitHub’s infringement of the GDPR.
      5. +
    5. Exercise of Rights. Rights granted to data subjects under this Addendum may be enforced by the data subject against GitHub irrespective of any restriction in Clauses 3 or 6 of the Standard Contractual Clauses (UK). The data subject may only bring a claim under this Addendum on an individual basis, and not part of a class, collective, group or representative action. Rights granted to data subjects under this Addendum are personal to the data subject and may not be assigned.
      6. +
    6. Notice of Change. In addition to Clause 5(b) of the Standard Contractual Clauses (UK), GitHub agrees and warrants that it has no reason to believe that the legislation applicable to it or its sub-processors, including in any country to which personal data is transferred either by itself or through a sub-processor, prevents it from fulfilling the instructions received from the data exporter and its obligations under this Addendum or the Standard Contractual Clauses (UK) and that in the event of a change in this legislation which is likely to have a substantial adverse effect on the warranties and obligations provided by this Addendum or the Standard Contractual Clauses (UK), it will promptly notify the change to Customer as soon as it is aware, in which case Customer is entitled to suspend the transfer of data and/or terminate the contract. +
    7. Termination. This Addendum shall automatically terminate if the European Commission, a competent Member State supervisory authority, or an EU or competent Member State court approves a different lawful transfer mechanism that would be applicable to the data transfers covered by the Standard Contractual Clauses (UK) (and if such mechanism applies only to some of the data transfers, this Addendum will terminate only with respect to those transfers) and that does not require the additional safeguards set forth in this Addendum.

      + Signing the Standard Contractual Clauses (UK), Appendix 1, Appendix 2 and +
    + +

    Attachment 3 – European Union General Data Protection Regulation Terms

    + +GitHub makes the commitments in these GDPR Related Terms, to all customers effective May 25, 2018. These commitments are binding upon GitHub with regard to Customer regardless of (1) the version of the GitHub Customer Agreement and DPA that is otherwise applicable to any given Online Services subscription or (2) any other agreement that references this attachment. + +For purposes of these GDPR Related Terms, Customer and GitHub agree that Customer is the controller of Personal Data and GitHub is the processor of such data, except when Customer acts as a processor of Personal Data, in which case GitHub is a subprocessor. These GDPR Related Terms apply to the processing of Personal Data, within the scope of the GDPR, by GitHub on behalf of Customer. These GDPR Related Terms do not limit or reduce any data protection commitments GitHub makes to Customer in the GitHub Customer Agreement or other agreement between GitHub and Customer. These GDPR Related Terms do not apply where GitHub is a controller of Personal Data. + +**Relevant GDPR Obligations: Articles 28, 32, and 33** + +
      +
    1. GitHub shall not engage another processor without prior specific or general written authorisation of Customer. In the case of general written authorisation, GitHub shall inform Customer of any intended changes concerning the addition or replacement of other processors, thereby giving Customer the opportunity to object to such changes. (Article 28(2))
      2. +
    2. Processing by GitHub shall be governed by these GDPR Related Terms under European Union (hereafter “Union”) or Member State law and are binding on GitHub with regard to Customer. The subject-matter and duration of the processing, the nature and purpose of the processing, the type of Personal Data, the categories of data subjects and the obligations and rights of the Customer are set forth in the Customer’s licensing agreement, including these GDPR Related Terms. In particular, GitHub shall:
      3. +
        +
      1. process the Personal Data only on documented instructions from Customer, including with regard to transfers of Personal Data to a third country or an international organisation, unless required to do so by Union or Member State law to which GitHub is subject; in such a case, GitHub shall inform Customer of that legal requirement before processing, unless that law prohibits such information on important grounds of public interest;
        2. +
      2. ensure that persons authorised to process the Personal Data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality;
        3. +
      3. take all measures required pursuant to Article 32 of the GDPR;
        4. +
      4. respect the conditions referred to in paragraphs 1 and 3 for engaging another processor;
        5. +
      5. taking into account the nature of the processing, assist Customer by appropriate technical and organisational measures, insofar as this is possible, for the fulfilment of the Customer’s obligation to respond to requests for exercising the data subject's rights laid down in Chapter III of the GDPR;
        6. +
      6. assist Customer in ensuring compliance with the obligations pursuant to Articles 32 to 36 of the GDPR, taking into account the nature of processing and the information available to GitHub;
        7. +
      7. at the choice of Customer, delete or return all the Personal Data to Customer after the end of the provision of services relating to processing, and delete existing copies unless Union or Member State law requires storage of the Personal Data;
        8. +
      8. make available to Customer all information necessary to demonstrate compliance with the obligations laid down in Article 28 of the GDPR and allow for and contribute to audits, including inspections, conducted by Customer or another auditor mandated by Customer.
        9. +

      + GitHub shall immediately inform Customer if, in its opinion, an instruction infringes the GDPR or other Union or Member State data protection provisions. (Article 28(3))

      +
    3. Where GitHub engages another processor for carrying out specific processing activities on behalf of Customer, the same data protection obligations as set out in these GDPR Related Terms shall be imposed on that other processor by way of a contract or other legal act under Union or Member State law, in particular providing sufficient guarantees to implement appropriate technical and organisational measures in such a manner that the processing will meet the requirements of the GDPR. Where that other processor fails to fulfil its data protection obligations, GitHub shall remain fully liable to the Customer for the performance of that other processor's obligations. (Article 28(4))
      4. +
    4. Taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of processing as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons, Customer and GitHub shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, including inter alia as appropriate:
      5. +
        +
      1. the pseudonymisation and encryption of Personal Data;
        2. +
      2. the ability to ensure the ongoing confidentiality, integrity, availability and resilience of processing systems and services;
        3. +
      3. the ability to restore the availability and access to Personal Data in a timely manner in the event of a physical or technical incident; and
        4. +
      4. a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the processing. (Article 32(1))
        5. +
      +
    5. In assessing the appropriate level of security, account shall be taken of the risks that are presented by processing, in particular from accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to Personal Data transmitted, stored or otherwise processed (Article 32(2)).
      6. +
    6. Customer and GitHub shall take steps to ensure that any natural person acting under the authority of Customer or GitHub who has access to Personal Data does not process them except on instructions from Customer, unless he or she is required to do so by Union or Member State law (Article 32(4)).
      7. +
    7. GitHub shall notify Customer without undue delay after becoming aware of a Personal Data breach (Article 33(2)). Such notification will include that information a processor must provide to a controller under Article 33(3) to the extent such information is reasonably available to GitHub.
      8. +
    + +--------------- + +

    (1) The Agreement on the European Economic Area (EEA Agreement) provides for the extension of the European Union’s internal market to the three EEA States Iceland, Liechtenstein and Norway. The Union data protection legislation, including Regulation (EU) 2016/679, is covered by the EEA Agreement and has been incorporated into Annex XI thereto. Therefore, any disclosure by the data importer to a third party located in the EEA does not qualify as an onward transfer for the purpose of these Clauses.

    + +

    (2) This requirement may be satisfied by the sub-processor acceding to these Clauses under the appropriate Module, in accordance with Clause 7.

    + +

    (3) As regards the impact of such laws and practices on compliance with these Clauses, different elements may be considered as part of an overall assessment. Such elements may include relevant and documented practical experience with prior instances of requests for disclosure from public authorities, or the absence of such requests, covering a sufficiently representative time-frame. This refers in particular to internal records or other documentation, drawn up on a continuous basis in accordance with due diligence and certified at senior management level, provided that this information can be lawfully shared with third parties. Where this practical experience is relied upon to conclude that the data importer will not be prevented from complying with these Clauses, it needs to be supported by other relevant, objective elements, and it is for the Parties to consider carefully whether these elements together carry sufficient weight, in terms of their reliability and representativeness, to support this conclusion. In particular, the Parties have to take into account whether their practical experience is corroborated and not contradicted by publicly available or otherwise accessible, reliable information on the existence or absence of requests within the same sector and/or the application of the law in practice, such as case law and reports by independent oversight bodies.

    diff --git a/translations/pt-BR/content/github/site-policy/github-marketplace-developer-agreement.md b/translations/pt-BR/content/github/site-policy/github-marketplace-developer-agreement.md index 1a2cf60100..d3ff9c7dc1 100644 --- a/translations/pt-BR/content/github/site-policy/github-marketplace-developer-agreement.md +++ b/translations/pt-BR/content/github/site-policy/github-marketplace-developer-agreement.md @@ -11,7 +11,7 @@ topics: **ESTES TERMOS E CONDIÇÕES (O "CONTRATO") REGEM SUA PARTICIPAÇÃO NO PROGRAMA DO GITHUB MARKETPLACE. AO SE INSCREVER PARA PARTICIPAR DO PROGRAMA DE MARKETPLACE OU AO CLICAR EM "ACEITO" ABAIXO, VOCÊ ESTÁ CONFIRMANDO QUE ENTENDE ESTE ACORDO E QUE ACEITA TODOS OS SEUS TERMOS E CONDIÇÕES. SE VOCÊ ESTÁ FIRMANDO ESTE CONTRATO EM NOME DE UMA EMPRESA OU OUTRA ENTIDADE LEGAL, VOCÊ CONFIRMA QUE POSSUI A AUTORIZAÇÃO LEGAL PARA VINCULAR A ENTIDADE A ESTE CONTRATO, NO QUAL "VOCÊ" REPRESENTARÁ A ENTIDADE QUE VOCÊ REPRESENTA.** -Effective Date: August 24, 2021 +Data de entrada em vigor: 24 de agosto de 2021 ## 1. DEFINIÇÕES diff --git a/translations/pt-BR/content/github/site-policy/github-marketplace-terms-of-service.md b/translations/pt-BR/content/github/site-policy/github-marketplace-terms-of-service.md index 5d9df66dae..221a27a9f3 100644 --- a/translations/pt-BR/content/github/site-policy/github-marketplace-terms-of-service.md +++ b/translations/pt-BR/content/github/site-policy/github-marketplace-terms-of-service.md @@ -39,7 +39,7 @@ Todos os pagamentos de Produtos de Desenvolvedor passarão pelo GitHub. Os termo **Cronograma de faturamento; sem reembolsos.** Seu cronograma de pagamento é determinado pelo cronograma de pagamento que você escolheu ao criar sua conta no GitHub (por exemplo, gratuito, mensal, anual). Para planos de pagamento mensais ou anuais, as compras do Marketplace são faturadas antecipadamente, respectivamente, mensal ou anualmente, e não são reembolsáveis. Não haverá reembolsos ou créditos para meses parciais de serviço, reembolsos para downgrade ou reembolsos por meses não utilizados; no entanto, o serviço permanecerá ativo durante o período de faturamento pago. Se você quiser cancelar os serviços de Produto de Desenvolvedor, você pode fazê-lo em suas Configurações na barra de navegação global na parte superior da tela. -If you would have a question, concern, or dispute regarding your billing, please contact [GitHub Support](https://support.github.com/contact?tags=docs-policy). +Se você tiver uma pergunta, preocupação ou dúvida sobre sua fatura, entre em contato com o [Suporte do GitHub](https://support.github.com/contact?tags=docs-policy). ## E. Seus Dados e a Política de Privacidade do GitHub @@ -87,4 +87,4 @@ Você concorda em indenizar-nos, defender-nos e isentar-nos de e contra todas e 6. **Licença para Políticas do GitHub.** Estes Termos de Marketplace são licenciados sob esta [Licença Creative Commons Zero](https://creativecommons.org/publicdomain/zero/1.0/). Para ver os detalhes, consulte nosso [repositório da Política do Site](https://github.com/github/site-policy#license). -7. **Fale Conosco.** Perguntas sobre os Termos do Marketplace? [Contact us](https://support.github.com/contact?tags=docs-policy). +7. **Fale Conosco.** Perguntas sobre os Termos do Marketplace? [Fale conosco](https://support.github.com/contact?tags=docs-policy). diff --git a/translations/pt-BR/content/github/site-policy/github-open-source-applications-terms-and-conditions.md b/translations/pt-BR/content/github/site-policy/github-open-source-applications-terms-and-conditions.md index 16e13a3914..7de454f368 100644 --- a/translations/pt-BR/content/github/site-policy/github-open-source-applications-terms-and-conditions.md +++ b/translations/pt-BR/content/github/site-policy/github-open-source-applications-terms-and-conditions.md @@ -63,4 +63,4 @@ O GitHub reserva-se o direito de, a qualquer momento e de tempos em tempos, modi 6. Licença para Políticas do GitHub. Esses Termos de Aplicação são licenciados sob a [Licença Creative Commons Zero](https://creativecommons.org/publicdomain/zero/1.0/). Para ver os detalhes, consulte nosso [repositório da Política do Site](https://github.com/github/site-policy#license). -7. Fale Conosco. Perguntas sobre os Termos de Serviço? [Contact us](https://support.github.com/contact?tags=docs-policy). +7. Fale Conosco. Perguntas sobre os Termos de Serviço? [Fale conosco](https://support.github.com/contact?tags=docs-policy). diff --git a/translations/pt-BR/content/github/site-policy/github-privacy-statement.md b/translations/pt-BR/content/github/site-policy/github-privacy-statement.md index 15f61dd7d9..857fe728ef 100644 --- a/translations/pt-BR/content/github/site-policy/github-privacy-statement.md +++ b/translations/pt-BR/content/github/site-policy/github-privacy-statement.md @@ -216,9 +216,9 @@ Você também pode adicionar aplicativos do GitHub, como nosso aplicativo Deskto ## Como você pode acessar e controlar as informações obtidas -If you're already a GitHub user, you may access, update, alter, or delete your basic user profile information by [editing your user profile](https://github.com/settings/profile) or contacting [GitHub Support](https://support.github.com/contact?tags=docs-policy). You can control the information we collect about you by limiting what information is in your profile, by keeping your information current, or by contacting [GitHub Support](https://support.github.com/contact?tags=docs-policy). +Se você já é um usuário do GitHub, você poderá acessar, atualizar, alterar, ou excluir as suas informações básicas de perfil de usuário, [editando seu perfil de usuário](https://github.com/settings/profile) ou entrando em contato com o [Suporte do GitHub](https://support.github.com/contact?tags=docs-policy). Você pode controlar as informações que coletamos sobre você limitando quais informações estão no seu perfil, mantendo sua informação atualizada ou entrando em contato com o [Suporte do GitHub](https://support.github.com/contact?tags=docs-policy). -If GitHub processes information about you, such as information [GitHub receives from third parties](#information-we-collect-from-third-parties), and you do not have an account, then you may, subject to applicable law, access, update, alter, delete, or object to the processing of your personal information by contacting [GitHub Support](https://support.github.com/contact?tags=docs-policy). +Se o GitHub processar informações sobre você como, por exemplo, informações que o [GitHub recebe de terceiros](#information-we-collect-from-third-parties), e você não tiver uma conta, você poderá, sujeito à lei, acessar, atualizar, alterar, excluir ou contestar o processamento das suas informações pessoais entrando em contato com o [Suporte do GitHub](https://support.github.com/contact?tags=docs-policy). ### Portabilidade de dados @@ -228,7 +228,7 @@ Como usuário do GitHub, você sempre pode levar seus dados com você. Por exemp Em geral, o GitHub retém as Informações Pessoais de Usuário enquanto a sua conta está ativa ou sempre que for necessário para prestar serviços a você. -Para cancelar sua conta ou excluir suas Informações Pessoais de Usuário, acesse o seu [perfil de usuário](https://github.com/settings/admin). Vamos reter e usar suas informações conforme o necessário para cumprir nossas obrigações legais, resolver conflitos e fazer valer nossos acordos; salvo em casos de requisitos legais, apagaremos seu perfil por completo (se razoável) dentro de 90 dias. You may contact [GitHub Support](https://support.github.com/contact?tags=docs-policy) to request the erasure of the data we process on the basis of consent within 30 days. +Para cancelar sua conta ou excluir suas Informações Pessoais de Usuário, acesse o seu [perfil de usuário](https://github.com/settings/admin). Vamos reter e usar suas informações conforme o necessário para cumprir nossas obrigações legais, resolver conflitos e fazer valer nossos acordos; salvo em casos de requisitos legais, apagaremos seu perfil por completo (se razoável) dentro de 90 dias. Você pode entrar em contato com o [Suporte do GitHub](https://support.github.com/contact?tags=docs-policy) para solicitar a eliminação dos dados que processamos com base no consentimento dentro de 30 dias. Alguns dados permanecerão após a exclusão de uma conta, como contribuições em repositórios de outros Usuários e comentários em problemas de outrem. Todavia, vamos excluir ou remover a identificação das suas Informações Pessoais de Usuário (inclusive nome de usuário e endereço de e-mail) do campo de autoria de problemas, pull requests e comentários, que serão associados a um [usuário fantasma](https://github.com/ghost). diff --git a/translations/pt-BR/content/github/site-policy/github-sponsors-additional-terms.md b/translations/pt-BR/content/github/site-policy/github-sponsors-additional-terms.md index c6118db316..91b0611637 100644 --- a/translations/pt-BR/content/github/site-policy/github-sponsors-additional-terms.md +++ b/translations/pt-BR/content/github/site-policy/github-sponsors-additional-terms.md @@ -68,7 +68,7 @@ A qualificação para o Fundo Correspondentes para Patrocinadores do GitHub é a * O GitHub reserva-se o direito de reter o dinheiro ou cancelar o Fundo Correspondente e bloquear qualquer usuário da participação no Fundo Correspondentes para Patrocinadores do GitHub por qualquer motivo, incluindo, mas não se limitando a postar conteúdo ou projetos que o GitHub determina serem ofensivos ou de outra forma censuráveis. #### 2.2.2. Período de correspondência. -The matching period begins after GitHub accepts an individual Sponsored Developer Account into GitHub Sponsors. Para cada Conta de Desenvolvedor Patrocinado individual qualificada para o Fundo Correspondentes para Patrocinadores do GitHub, o GitHub pode igualar o patrocínio da comunidade até US$ 5.000 no total durante os primeiros 12 meses da Conta de Desenvolvedor Patrocinado no Programa. O período de correspondência não pode ser prorrogado por nenhum motivo. Durante o período de correspondência, o GitHub não cobrará nenhuma taxa, então 100% dos patrocínios irão para o desenvolvedor patrocinado. No futuro, poderemos cobrar uma taxa nominal de processamento. +O período correspondente começa depois que o GitHub aceita uma conta de desenvolvedor patrocinada individual no GitHub Sponsors. Para cada Conta de Desenvolvedor Patrocinado individual qualificada para o Fundo Correspondentes para Patrocinadores do GitHub, o GitHub pode igualar o patrocínio da comunidade até US$ 5.000 no total durante os primeiros 12 meses da Conta de Desenvolvedor Patrocinado no Programa. O período de correspondência não pode ser prorrogado por nenhum motivo. Durante o período de correspondência, o GitHub não cobrará nenhuma taxa, então 100% dos patrocínios irão para o desenvolvedor patrocinado. No futuro, poderemos cobrar uma taxa nominal de processamento. * Se uma Assinatura de Patrocínio ou Patrocínio forem interrompidos por qualquer motivo, a correspondência associada também se interrompe. Os fundos que são cobrados de volta ao Patrocinador antes da data de pagamento do Desenvolvedor Patrocinado não são qualificados para correspondência. diff --git a/translations/pt-BR/content/github/site-policy/github-terms-for-additional-products-and-features.md b/translations/pt-BR/content/github/site-policy/github-terms-for-additional-products-and-features.md index 550ca7ba19..683b3783aa 100644 --- a/translations/pt-BR/content/github/site-policy/github-terms-for-additional-products-and-features.md +++ b/translations/pt-BR/content/github/site-policy/github-terms-for-additional-products-and-features.md @@ -9,7 +9,7 @@ topics: - Legal --- -Version Effective Date: August 10, 2021 +Data de vigência da versão: 10 de agosto de 2021 Ao usar o GitHub, você pode ter acesso a muitos produtos e funcionalidades adicionais ("Produtos e Funcionalidades Adicionais"). Porque muitos dos produtos e funcionalidades adicionais oferecem diferentes funcionalidades, termos específicos para esse produto ou recurso, podem-se aplicar, além do seu acordo principal — os Termos de Serviço do GitHub, Termos de Serviço Corporativo, Termos Gerais do GitHub ou contrato de licenciamento de volume da Microsoft (denominados o "Contrato"). Abaixo, listamos os produtos e funcionalidades, junto com os termos adicionais correspondentes que se aplicam ao seu uso. @@ -20,7 +20,7 @@ Ao usar as Funcionalidades e Produtos Adicionais, você também concorda com os - Os usuários do **GitHub Enterprise Server** podem ter acesso aos seguintes Produtos e Funcionalidades: Ações, Segurança Avançada, Dados de Consultoria, Conexões, Visualização de Dependabot, Laboratório, Octoshift, Pacotes, Páginas e Imagens de Servidor SQL. -- Os usuários do **GitHub AE** podem ter acesso aos seguintes produtos e funcionalidades: ações, segurança avançada, dados de consultoria, {% ifversion ghae-next %}conexões, {% endif %}visualização de dependência, Octoshift, pacotes e páginas. +- **GitHub AE** users may have access to the following Additional Products and Features: Actions, Advanced Security, Advisory Database,{% ifversion ghae-next %}Connect, {% endif %}Dependabot Preview, Octoshift, Packages and Pages. ## Ações As Ações GitHub permitem criar fluxos de trabalho personalizados do ciclo de vida de desenvolvimento de softwares diretamente no seu repositório GitHub. Ações são cobradas conforme o uso. A [Documentação de ações](/actions) inclui detalhes, que abrangem quantidades de computação e armazenamento (dependendo do plano da sua conta) e como monitorar seus minutos de ação de uso e definir limites de uso. @@ -38,7 +38,7 @@ Para evitar violações dessas limitações e abuso de Ações do GitHub, o GitH ## Segurança Avançada O GitHub disponibiliza funcionalidades adicionais de segurança aos clientes sob uma licença avançada de segurança. Essas funcionalidades incluem a verificação de código, varredura de segredo e revisão de dependências. A [documentação avançada de segurança](/github/getting-started-with-github/about-github-advanced-security) fornece mais informações. -A segurança avançada é licenciada conforme o "commiter único". Um "Committer único" é um usuário licenciado do GitHub Enterprise, GitHub Enterprise Cloud, GitHub Enterprise Server, ou GitHub AE, que criou um commit de código nos últimos 90 dias para qualquer repositório que tivesse qualquer recurso de Advanced Security do GitHub ativado. Você deve adquirir uma licença de Usuário GitHub Advanced Security para cada um dos seus Commiters únicos. Você só pode usar o GitHub Advanced Security em códigos desenvolvidos por ou para você. Para usuários do GitHub Enterprise Cloud, algumas funcionalidades de segurança avançada também exigem o uso de ações no GitHub. +A segurança avançada é licenciada conforme o "commiter único". A "Unique Committer" is a licensed user of GitHub Enterprise, GitHub Enterprise Cloud, GitHub Enterprise Server, or GitHub AE, who has made a commit in the last 90 days to any repository with any GitHub Advanced Security functionality activated. Você deve adquirir uma licença de Usuário GitHub Advanced Security para cada um dos seus Commiters únicos. Você só pode usar o GitHub Advanced Security em códigos desenvolvidos por ou para você. Para usuários do GitHub Enterprise Cloud, algumas funcionalidades de segurança avançada também exigem o uso de ações no GitHub. ## Banco de Dados Consultivo A base de dados do GitHub Advisory permite que você pesquise ou procure vulnerabilidades que afetem projetos de código aberto no GitHub. diff --git a/translations/pt-BR/content/github/site-policy/github-terms-of-service.md b/translations/pt-BR/content/github/site-policy/github-terms-of-service.md index 5703bfae05..2ceab04946 100644 --- a/translations/pt-BR/content/github/site-policy/github-terms-of-service.md +++ b/translations/pt-BR/content/github/site-policy/github-terms-of-service.md @@ -78,7 +78,7 @@ Temos algumas regras simples para Contas de Usuário no Serviço do GitHub. Você é responsável por manter sua Conta segura enquanto usa nosso Serviço. Nós oferecemos ferramentas como a autenticação de dois fatores para ajudá-lo a manter a segurança de sua Conta, mas o conteúdo de sua Conta e sua segurança são de sua responsabilidade. - Você é responsável por todos os conteúdos postados e atividades que ocorrem em sua Conta (mesmo quando o conteúdo é postado por outros que têm Contas em sua Conta). - Você é responsável por manter a segurança de sua Conta e senha. O GitHub não pode e não será responsabilizado por qualquer perda ou dano causado por sua falha em cumprir com esta obrigação de segurança. -- You will promptly [notify GitHub](https://support.github.com/contact?tags=docs-policy) if you become aware of any unauthorized use of, or access to, our Service through your Account, including any unauthorized use of your password or Account. +- Você irá rapidamente [notificar o GitHub](https://support.github.com/contact?tags=docs-policy) se estiver ciente de qualquer uso não autorizado de, ou acesso a, nosso Serviço através de sua Conta, incluindo qualquer uso não autorizado de sua senha ou Conta. ### 5. Termos adicionais Em algumas situações, os termos de terceiros podem ser aplicados ao seu uso do GitHub. Por exemplo, você pode ser integrante de uma organização no GitHub com seus próprios termos ou contratos de licença. Você poderá baixar um aplicativo que se integra ao GitHub; ou utilizar o GitHub para autenticar em outro serviço. Por favor, esteja ciente de que, embora esses Termos representem nosso acordo total com você, os termos de terceiros governam suas relações com você. @@ -183,7 +183,7 @@ O GitHub pode oferecer acesso baseado em assinaturas à nossa API para os Usuár Alguns recursos do Serviço podem estar sujeitos a termos adicionais específicos para aquele recurso ou produto, conforme definido nos Termos de Produto Adicionais no GitHub. Ao acessar ou utilizar os Serviços, você também concorda com os [Termos de Produto Adicionais do GitHub](/github/site-policy/github-additional-product-terms). ## J. Visualizações Beta -**Short version:** *Beta Previews may not be supported or may change at any time. You may receive confidential information through those programs that must remain confidential while the program is private. We'd love your feedback to make our Beta Previews better.* +**Versão curta:** Pré-visualizações Beta de *podem não ser compatíveis ou podem ser alteradas a qualquer momento. Você pode receber informações confidenciais por meio dos programas que devem permanecer confidenciais enquanto o programa for privado. Adoraríamos ouvir seu feedback para pode melhorar as nossas visualizações beta.* ### 1. Sujeito a alterações @@ -224,12 +224,12 @@ Nossos termos de preços e pagamento estão disponíveis em [github.com/pricing] Ao concordar com estes Termos, você está nos dando permissão para cobrar seu cartão de crédito registrado, sua conta do PayPal, ou outros métodos de pagamento aprovados para as taxas que você autorizou para o GitHub. ### 5. Responsabilidade do pagamento -Você é responsável por todas as taxas, incluindo impostos associados com seu uso do Serviço. Ao usar o Serviço, você concorda em pagar ao GitHub qualquer cobrança incorrida em relação ao seu uso do Serviço. If you dispute the matter, contact [GitHub Support](https://support.github.com/contact?tags=docs-policy). Você é responsável por nos fornecer um meio de pagamento válido para Contas pagas. Contas Grátis não são precisam fornecer informações de pagamento. +Você é responsável por todas as taxas, incluindo impostos associados com seu uso do Serviço. Ao usar o Serviço, você concorda em pagar ao GitHub qualquer cobrança incorrida em relação ao seu uso do Serviço. Se você não concorda com a cobrança, entre em contato com [Suporte do GitHub](https://support.github.com/contact?tags=docs-policy). Você é responsável por nos fornecer um meio de pagamento válido para Contas pagas. Contas Grátis não são precisam fornecer informações de pagamento. ## L. Cancelamento e Rescisão **Versão curta:** *Você pode encerrar sua Conta a qualquer momento. Se o fizer, trataremos suas informações de forma responsável.* -### 1. Account Cancellation +### 1. Cancelamento de conta É sua responsabilidade cancelar corretamente sua Conta com o GitHub. Você pode [cancelar sua Conta a qualquer momento](/articles/how-do-i-cancel-my-account/) indo em suas Configurações na barra global de navegação no topo da tela. A tela da Conta fornece um link simples, sem questionamentos, para você efetuar o cancelamento. Não cancelamos Contas por solicitações via e-mail ou telefone. ### 2. Após Cancelamento @@ -312,4 +312,4 @@ Se alguma parte deste Contrato for considerada inválida ou inaplicável, essa p Este Contrato só pode ser modificado por uma alteração escrita assinada por um representante autorizado do GitHub, ou pela postagem pelo GitHub de uma versão revisada de acordo com [Seção Q. Alterações nestes Termos](#q-changes-to-these-terms). Estes Termos de Serviço, juntamente com a Declaração de Privacidade do GitHub, representam a declaração completa e exclusiva do acordo entre você e nós. Este Contrato substitui qualquer proposta ou acordo prévio oral ou escrito, e quaisquer outras comunicações entre você e o GitHub relacionadas com o assunto desses termos, incluindo quaisquer acordos de confidencialidade ou de não divulgação. ### 6. Perguntas -Perguntas sobre os Termos de Serviço? [Contact us](https://support.github.com/contact?tags=docs-policy). +Perguntas sobre os Termos de Serviço? [Fale conosco](https://support.github.com/contact?tags=docs-policy). diff --git a/translations/pt-BR/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md b/translations/pt-BR/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md index 127dfaeeaf..0e1bd6785c 100644 --- a/translations/pt-BR/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md +++ b/translations/pt-BR/content/github/site-policy/githubs-notice-about-the-california-consumer-privacy-act.md @@ -21,7 +21,7 @@ O Github _não_ vende informações pessoais, incluindo informações pessoais d ## Seus direitos sob a CCPA -A CCPA fornece aos residentes da Califórnia certos direitos relacionados às suas informações pessoais. To submit a request based on these rights, please contact us via our [contact form](https://support.github.com/contact?tags=docs-policy). +A CCPA fornece aos residentes da Califórnia certos direitos relacionados às suas informações pessoais. Para enviar uma solicitação com base nesses direitos, entre em contato conosco por meio do nosso [formulário de contato](https://support.github.com/contact?tags=docs-policy). Ao receber uma solicitação, verificaremos se o indivíduo que fez a solicitação é o residente a quem pertencem as informações pessoais sujeitas à solicitação. Os residentes da Califórnia podem exercer seus direitos por si próprios ou podem usar um agente autorizado para fazer solicitações para divulgar certas informações sobre o processamento de suas informações pessoais ou para excluir informações pessoais em seu nome. Se você usar um agente autorizado para enviar uma solicitação, podemos exigir que você nos forneça informações adicionais demonstrando que o agente está agindo em seu nome. @@ -73,4 +73,4 @@ A CCPA prevê isenções, até 31 de dezembro de 2020 (inclusive), de algumas da informações pessoais que reflitam uma comunicação escrita ou verbal ou uma transação entre o GitHub e uma pessoa física, onde a pessoa física está agindo como funcionário, proprietário, diretor, responsável ou terceirizado de uma empresa, parceria, propriedade exclusiva, entidade sem fins lucrativos ou agência governamental e cujas comunicações ou transações com o GitHub ocorrem apenas no contexto do GitHub realizando due diligence em relação, ou fornecendo ou recebendo um produto ou serviço para ou de tal empresa, parceria, propriedade exclusiva, entidade sem fins lucrativos ou agência governamental. -If you have any questions about this page, please contact us via our [contact form](https://support.github.com/contact?tags=docs-policy). +Em caso de dúvidas sobre esta página, entre em contato conosco por meio do nosso [formulário de contato](https://support.github.com/contact?tags=docs-policy). diff --git a/translations/pt-BR/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md b/translations/pt-BR/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md index 9f1e024f87..42656ddf29 100644 --- a/translations/pt-BR/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md +++ b/translations/pt-BR/content/github/site-policy/guidelines-for-legal-requests-of-user-data.md @@ -104,7 +104,7 @@ Aqui está uma lista não exaustiva dos tipos de dados que mantemos a respeito d ## Notificaremos qualquer proprietário de conta afetado -É nossa política notificar os usuários sobre quaisquer pedidos pendentes relativos a suas contas ou seus repositórios, a não ser que sejamos proibidos por lei ou por decisão judicial. Antes de divulgar informações do usuário, faremos um esforço razoável para notificar qualquer proprietário da conta afetada enviando uma mensagem para seu endereço de e-mail verificado, fornecendo a ele uma cópia da intimação, da ordem judicial, ou do mandado, para que possa ter a oportunidade de contestar o processo judicial, se assim o desejar. In (rare) exigent circumstances, we may delay notification if we determine delay is necessary to prevent death or serious harm or due to an ongoing investigation. +É nossa política notificar os usuários sobre quaisquer pedidos pendentes relativos a suas contas ou seus repositórios, a não ser que sejamos proibidos por lei ou por decisão judicial. Antes de divulgar informações do usuário, faremos um esforço razoável para notificar qualquer proprietário da conta afetada enviando uma mensagem para seu endereço de e-mail verificado, fornecendo a ele uma cópia da intimação, da ordem judicial, ou do mandado, para que possa ter a oportunidade de contestar o processo judicial, se assim o desejar. Em (raras) circunstâncias exigentes, podemos atrasar a notificação, se determinarmos que os atrasos são necessários para evitar a morte ou danos graves ou devido a uma investigação em curso. ## Compartilhamento de informações não públicas diff --git a/translations/pt-BR/content/github/site-policy/index.md b/translations/pt-BR/content/github/site-policy/index.md index 544992319f..503cce406e 100644 --- a/translations/pt-BR/content/github/site-policy/index.md +++ b/translations/pt-BR/content/github/site-policy/index.md @@ -12,7 +12,7 @@ children: - /github-terms-of-service - /github-corporate-terms-of-service - /github-privacy-statement - - /github-data-protection-agreement-non-enterprise-customers + - /github-data-protection-agreement - /global-privacy-practices - /github-sponsors-additional-terms - /github-codespaces-privacy-statement diff --git a/translations/pt-BR/content/github/working-with-github-support/about-github-support.md b/translations/pt-BR/content/github/working-with-github-support/about-github-support.md index 1526f08dbb..79e01bee6f 100644 --- a/translations/pt-BR/content/github/working-with-github-support/about-github-support.md +++ b/translations/pt-BR/content/github/working-with-github-support/about-github-support.md @@ -27,7 +27,7 @@ Para verificar se, atualmente, há algum incidente afetando os serviços no {% d Você pode usar {% data variables.contact.community_support_forum %} para procurar tópicos, fazer perguntas, compartilhar soluções e interagir diretamente com {% data variables.contact.community_support %}. -Para relatar problemas de segurança, segurança e abuso ou receber suporte assistido para uma conta paga, acesse {% data variables.contact.contact_support_portal %}. Se você for um administrador de {% data variables.product.prodname_ghe_server %} sem uma conta de usuário em {% data variables.product.prodname_dotcom_the_website %}, acesse {% data variables.contact.contact_enterprise_portal %}. Email communication from GitHub Support will always be sent from either a `github.com` or `githubsupport.com` address. +Para relatar problemas de segurança, segurança e abuso ou receber suporte assistido para uma conta paga, acesse {% data variables.contact.contact_support_portal %}. Se você for um administrador de {% data variables.product.prodname_ghe_server %} sem uma conta de usuário em {% data variables.product.prodname_dotcom_the_website %}, acesse {% data variables.contact.contact_enterprise_portal %}. A comunicação de e-mail do GitHub Support sempre será enviada de um endereço `github.com` ou `githubsupport.com`. ## Conceder acesso temporário do {% data variables.contact.github_support %} a um repositório privado diff --git a/translations/pt-BR/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md b/translations/pt-BR/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md index 4fea514506..de9122bbf8 100644 --- a/translations/pt-BR/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md +++ b/translations/pt-BR/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md @@ -1,6 +1,7 @@ --- title: Criar gists intro: 'Você pode criar dois tipos de gists: {% ifversion ghae %}internos{% else %}públicos{% endif %} e secretos. Crie um gist {% ifversion ghae %}interno{% else %}um público{% endif %} se você estiver pronto para compartilhar suas ideias com {% ifversion ghae %}os integrantes corporativos{% else %}o mundo{% endif %} ou um gist secreto se você não estiver pronto.' +permissions: '{% data reusables.enterprise-accounts.emu-permission-gist %}' redirect_from: - /articles/about-gists/ - /articles/cannot-delete-an-anonymous-gist/ @@ -19,7 +20,7 @@ Cada gist é um repositório Git, o que significa que ele pode ser bifurcado e c Os gists podem ser {% ifversion ghae %}internos{% else %}públicos{% endif %} ou segredo. Gists{% ifversion ghae %}Internos{% else %}Públicos{% endif %} aparecem em {% data variables.gists.discover_url %}, em que os {% ifversion ghae %}integrantes da empresa{% else %}pessoas{% endif %} podem pesquisar novos gists criados. Eles também são pesquisáveis, de modo que é possível usá-los se desejar que outras pessoas encontrem e vejam seu trabalho. -Os gists secretos não aparecem em {% data variables.gists.discover_url %} e não são pesquisáveis. Os grupos de segredos não são privados. If you send the URL of a secret gist to {% ifversion ghae %}another enterprise member{% else %}a friend{% endif %}, they'll be able to see it. No entanto, se {% ifversion ghae %}qualquer outro integrante corporativo{% else %}alguém que você não conhece{% endif %} descobrir a URL, essa pessoa também poderá ver o seu gist. Se precisar manter seu código longe de olhares curiosos, pode ser mais conveniente [criar um repositório privado](/articles/creating-a-new-repository). +Os gists secretos não aparecem em {% data variables.gists.discover_url %} e não são pesquisáveis. Os grupos de segredos não são privados. Se você enviar a URL de um gist do segredo para {% ifversion ghae %}outro integrante da empresa{% else %}um amigo{% endif %}, eles poderão vê-la. No entanto, se {% ifversion ghae %}qualquer outro integrante corporativo{% else %}alguém que você não conhece{% endif %} descobrir a URL, essa pessoa também poderá ver o seu gist. Se precisar manter seu código longe de olhares curiosos, pode ser mais conveniente [criar um repositório privado](/articles/creating-a-new-repository). {% data reusables.gist.cannot-convert-public-gists-to-secret %} @@ -42,7 +43,7 @@ Você pode fixar os gists no seu perfil para que outras pessoas possam vê-los f {% endif %} -Você pode descobrir gists {% ifversion ghae %}internos{% else %}públicos{% endif %} que outros criaram, acessando {% data variables.gists.gist_homepage %} e clicando em **Todos os Gists**. Isso levará você a uma página com todos os gists classificados e exibidos por data de criação ou atualização. Também é possível pesquisar gists por linguagem com {% data variables.gists.gist_search_url %}. A pesquisa de gist usa a mesma sintaxe de pesquisa que a [pesquisa de código](/articles/searching-code). +Você pode descobrir gists {% ifversion ghae %}internos{% else %}públicos{% endif %} que outros criaram, acessando {% data variables.gists.gist_homepage %} e clicando em **Todos os Gists**. Isso levará você a uma página com todos os gists classificados e exibidos por data de criação ou atualização. Também é possível pesquisar gists por linguagem com {% data variables.gists.gist_search_url %}. A pesquisa de gist usa a mesma sintaxe de pesquisa que a [pesquisa de código](/search-github/searching-on-github/searching-code). Uma vez que os gists são repositórios Git, você pode exibir o histórico completo de commits deles, com diffs. Também é possível bifurcar ou clonar gists. Para obter mais informações, consulte ["Bifurcar e clonar gists"](/articles/forking-and-cloning-gists). @@ -50,7 +51,7 @@ Você pode baixar um arquivo ZIP de um gist clicando no botão **Download ZIP** {% ifversion fpt %} -O gist permite mapeamento de arquivos geoJSON. Esses mapas são exibidos em gists inseridos, de modo que você pode compartilhar e inserir mapas facilmente. For more information, see "[Working with non-code files](/repositories/working-with-files/using-files/working-with-non-code-files#mapping-geojson-files-on-github)." +O gist permite mapeamento de arquivos geoJSON. Esses mapas são exibidos em gists inseridos, de modo que você pode compartilhar e inserir mapas facilmente. Para obter mais informações, consulte "[Trabalhando com arquivos sem código](/repositories/working-with-files/using-files/working-with-non-code-files#mapping-geojson-files-on-github)". {% endif %} diff --git a/translations/pt-BR/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md b/translations/pt-BR/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md index 650ad89698..f26a0547de 100644 --- a/translations/pt-BR/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md +++ b/translations/pt-BR/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md @@ -1,6 +1,7 @@ --- title: Bifurcar e clonar gists intro: 'Gists são repositórios Git. Isso significa que é posível bifurcar ou clonar qualquer gist, mesmo não sendo o autor original. Também é possível visualizar o histórico completo de commits do gist, inclusive os diffs.' +permissions: '{% data reusables.enterprise-accounts.emu-permission-gist %}' redirect_from: - /articles/forking-and-cloning-gists - /github/writing-on-github/forking-and-cloning-gists diff --git a/translations/pt-BR/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md b/translations/pt-BR/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md index ad55299d1f..5061ddc931 100644 --- a/translations/pt-BR/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md +++ b/translations/pt-BR/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md @@ -40,9 +40,9 @@ Você pode indicar ênfase com texto em negrito, itálico ou riscado em campos d Você pode citar texto com um `>`. ```markdown -Nas palavras de Abraham Lincoln: +Texto que não é uma citação -> Pardon my French +> Texto que é uma citação ``` ![Texto citado renderizado](/assets/images/help/writing/quoted-text-rendered.png) @@ -100,39 +100,39 @@ Você pode criar um link inline colocando o texto do link entre colchetes `[ ]` {% data reusables.repositories.relative-links %} -## Images +## Imagens -You can display an image by adding `!` and wrapping the alt text in`[ ]`. Then wrap the link for the image in parentheses `()`. +Você pode exibir uma imagem adicionando `!` e por o texto alternativo em`[ ]`. Em seguida, coloque o link da imagem entre parênteses `()`. -`![This is an image](https://myoctocat.com/assets/images/base-octocat.svg)` +`![Isso é uma imagem](https://myoctocat.com/assets/images/base-octocat.svg)` -![Rendered Image](/assets/images/help/writing/image-rendered.png) +![Imagem interpretada](/assets/images/help/writing/image-rendered.png) -{% data variables.product.product_name %} supports embedding images into your issues, pull requests{% ifversion fpt %}, discussions{% endif %}, comments and `.md` files. You can display an image from your repository, add a link to an online image, or upload an image. For more information, see "[Uploading assets](#uploading-assets)." +{% data variables.product.product_name %} é compatível com a incorporação de imagens nos seus problemas, pull requests{% ifversion fpt %}, discussões{% endif %}, comentários e arquivos `.md`. Você pode exibir uma imagem do seu repositório, adicionar um link para uma imagem on-line ou fazer o upload de uma imagem. Para obter mais informações, consulte[Fazer o upload de ativos](#uploading-assets)". {% tip %} -**Tip:** When you want to display an image which is in your repository, you should use relative links instead of absolute links. +**Dica:** quando você quiser exibir uma imagem que está no seu repositório, você deverá usar links relativos em vez de links absolutos. {% endtip %} -Here are some examples for using relative links to display an image. +Aqui estão alguns exemplos para usar links relativos para exibir uma imagem. -| Contexto | Relative Link | -| ----------------------------------------------------------- | ---------------------------------------------------------------------- | -| In a `.md` file on the same branch | `/assets/images/electrocat.png` | -| In a `.md` file on another branch | `/../main/assets/images/electrocat.png` | -| In issues, pull requests and comments of the repository | `../blob/main/assets/images/electrocat.png` | -| In a `.md` file in another repository | `/../../../../github/docs/blob/main/assets/images/electrocat.png` | -| In issues, pull requests and comments of another repository | `../../../github/docs/blob/main/assets/images/electrocat.png?raw=true` | +| Contexto | Link relativo | +| -------------------------------------------------------------- | ---------------------------------------------------------------------- | +| Em um arquivo `.md` no mesmo branch | `/assets/images/electrocat.png` | +| Em um arquivo `.md` em outro branch | `/../main/assets/images/electrocat.png` | +| Em problemas, pull requests e comentários do repositório | `../blob/main/assets/images/electrocat.png` | +| Em um arquivo `.md` em outro repositório | `/../../../../github/docs/blob/main/assets/images/electrocat.png` | +| Em problemas, pull requests e comentários de outro repositório | `../../../github/docs/blob/main/assets/images/electrocat.png?raw=true` | {% note %} -**Note**: The last two relative links in the table above will work for images in a private repository only if the viewer has at least read access to the private repository which contains these images. +**Observação**: Os dois últimos links relativos na tabela acima funcionarão para imagens em um repositório privado somente se o visualizador tiver pelo menos acesso de leitura ao repositório privado que contém essas imagens. {% endnote %} -For more information, see "[Relative Links](#relative-links)." +Para obter mais informações, consulte[Links relativos,](#relative-links)." ## Listas @@ -184,7 +184,7 @@ Neste exemplo, você pode adicionar um item de lista aninhada abaixo do item de ![Lista com um item de lista aninhada](/assets/images/help/writing/nested-list-example-3.png) -Você pode criar vários níveis de listas aninhadas usando o mesmo método. Por exemplo, como o primeiro item da lista aninhada tem sete espaços (`␣␣␣␣␣-␣`) antes do conteúdo da lista aninhada `Primeiro item da lista aninhada`, você precisaria recuar o segundo item da lista aninhada com sete espaços. +Você pode criar vários níveis de listas aninhadas usando o mesmo método. Por exemplo, como o primeiro item da lista aninhada tem sete caracteres (`␣␣␣␣␣-␣`) antes do conteúdo da lista aninhada `Primeiro item da lista aninhada`, você precisaria recuar o segundo item da lista aninhada com sete espaços. ```markdown 100. Primeiro item da lista @@ -232,7 +232,7 @@ Para obter mais informações, consulte "[Referências e URLs vinculados automat ## Anexos de conteúdo -Some {% data variables.product.prodname_github_apps %} provide information in {% data variables.product.product_name %} for URLs that link to their registered domains. O {% data variables.product.product_name %} renderiza as informações fornecidas pelo app sob o URL no texto ou comentário de um problema ou uma pull request. +Alguns {% data variables.product.prodname_github_apps %} fornecem informações em {% data variables.product.product_name %} para URLs vinculadas aos seus domínios registrados. O {% data variables.product.product_name %} renderiza as informações fornecidas pelo app sob o URL no texto ou comentário de um problema ou uma pull request. ![Anexo de conteúdo](/assets/images/github-apps/content_reference_attachment.png) @@ -262,6 +262,30 @@ 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-next or ghes > 3.3 %} +## Notas de rodapé + +Você pode adicionar notas de rodapé ao seu conteúdo usando esta sintaxe entre colchetes: + +``` +Essa é uma simples nota de rodapé[^1]. + +[^1]: Minha referência. +``` + +A nota de rodapé será interpretada da seguinte forma: + +![Nota de rodapé interpretada](/assets/images/site/rendered-footnote.png) +{% endif %} + +## Ocultando o conteúdo com comentários + +Você pode dizer a {% data variables.product.product_name %} para ocultar o conteúdo do markdown interpretado, colocando o conteúdo em um comentário HTML. + +
    +<!-- This content will not appear in the rendered Markdown -->
+
    + ## Ignorar formatação markdown Você pode informar o {% data variables.product.product_name %} para ignorar (ou usar escape) a formatação markdown usando `\` antes do caractere markdown. @@ -272,13 +296,13 @@ Você pode informar o {% data variables.product.product_name %} para ignorar (ou Para obter mais informações, consulte "[Sintaxe markdown](https://daringfireball.net/projects/markdown/syntax#backslash)" de Daring Fireball. -## Hiding content with comments +{% ifversion fpt or ghes > 3.2 or ghae-issue-5232 %} -You can tell {% data variables.product.product_name %} to hide content from the rendered Markdown by placing the content in an HTML comment. +## Desabilitando a interpretação do Markdown -
    -<!-- This content will not appear in the rendered Markdown -->
-
    +{% data reusables.repositories.disabling-markdown-rendering %} + +{% endif %} ## Leia mais diff --git a/translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md b/translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md index 73b86a623b..465fc6d8a0 100644 --- a/translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md +++ b/translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md @@ -16,7 +16,7 @@ topics: {% warning %} -**Aviso:** Se você adicionar uma imagem {% ifversion fpt or ghes > 3.1 or ghae-next %} ou vídeo {% endif %} a uma pull request ou comentário de problema, qualquer um poderá ver a URL anônima sem autenticação, mesmo que o pull request esteja em um repositório privado{% ifversion ghes %} ou se o modo privado estiver habilitado{% endif %}. Para manter arquivos de mídia confidenciais privados, forneça-os a partir de uma rede privada ou servidor que exige autenticação. {% ifversion fpt %}Para mais informações sobre URLs anônimas, consulte "[Sobre URLs anônimas](/github/authenticating-to-github/about-anonymized-urls)".{% endif %} +**Aviso:** Se você adicionar uma imagem{% ifversion fpt or ghes > 3.1 or ghae-next %} ou vídeo{% endif %} a um comentário de pull request ou problema, qualquer um poderá ver a URL anônima sem autenticação, mesmo se o pull request estiver em um repositório privado{% ifversion ghes %} ou se o modo privado estiver habilitado{% endif %}. Para manter arquivos de mídia confidenciais privados, forneça-os a partir de uma rede privada ou servidor que exige autenticação. {% ifversion fpt %}Para mais informações sobre URLs anônimas, consulte "[Sobre URLs anônimas](/github/authenticating-to-github/about-anonymized-urls)".{% endif %} {% endwarning %} @@ -31,9 +31,10 @@ Para anexar um arquivo a uma conversa sobre um problema ou pull request, arraste {% endtip %} O tamanho máximo do arquivo é: -- 10MB de imagens e gifs{% ifversion fpt or ghes > 3.1 or ghae-next %} +- 10MB para imagens e gifs{% ifversion fpt %} - 10MB para vídeos enviados para um repositório pertencentes a um usuário ou organização em um plano grátis do GitHub -- 100MB para vídeos enviados para um repositório pertencente a um usuário ou organização em um plano pago do GitHub{% endif %} +- 100MB para vídeos enviados para um repositório pertencente a um usuário ou organização em um plano pago do GitHub{% elsif fpt or ghes > 3.1 or ghae-next %} +- 100MB para vídeos{% endif %} - 25MB para todos os outros arquivos Arquivos compatíveis: diff --git a/translations/pt-BR/content/github/writing-on-github/working-with-saved-replies/creating-a-saved-reply.md b/translations/pt-BR/content/github/writing-on-github/working-with-saved-replies/creating-a-saved-reply.md index 9dfca8310d..742b133b23 100644 --- a/translations/pt-BR/content/github/writing-on-github/working-with-saved-replies/creating-a-saved-reply.md +++ b/translations/pt-BR/content/github/writing-on-github/working-with-saved-replies/creating-a-saved-reply.md @@ -15,7 +15,7 @@ versions: 3. Em "Add a saved reply" (Adicionar uma resposta salva), adicione o título da resposta salva. ![Título da resposta salva](/assets/images/help/settings/saved-replies-title.png) 4. No campo "Write" (Gravar), adicione o conteúdo que deseja usar para a resposta salva. Para obter mais informações sobre como gravar no {% data variables.product.product_name %}, consulte "[Sintaxe básica de gravação e formatação](/articles/basic-writing-and-formatting-syntax)". ![Gravar uma resposta salva](/assets/images/help/settings/saved-replies-settings-adding.png) 5. Para revisar sua resposta, clique em **Preview** (Visualizar). ![Adicionar uma resposta salva](/assets/images/help/settings/saved-replies-preview.png) -6. Clique em **Add saved reply** (Adicionar resposta salva). !["Add saved reply" button](/assets/images/help/settings/saved-replies-add-button.png) +6. Clique em **Add saved reply** (Adicionar resposta salva). ![Botão "Adicionar resposta salva"](/assets/images/help/settings/saved-replies-add-button.png) ## Leia mais diff --git a/translations/pt-BR/content/graphql/guides/introduction-to-graphql.md b/translations/pt-BR/content/graphql/guides/introduction-to-graphql.md index 1f8a38ffaa..f2172e82e4 100644 --- a/translations/pt-BR/content/graphql/guides/introduction-to-graphql.md +++ b/translations/pt-BR/content/graphql/guides/introduction-to-graphql.md @@ -119,7 +119,7 @@ O GraphQL é [introspectivo](https://graphql.github.io/learn/introspection/). Is {% note %} - **Note**: If you get the response `"message": "Bad credentials"` or `401 Unauthorized`, check that you are using a valid token. Para mais informação, consulte "[Criando um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)." + **Observação**: Se você receber a resposta `"message": "Bad credentials"` ou `401 Unauthorized`, verifique se você está usando um token válido. Para mais informação, consulte "[Criando um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)." {% endnote %} diff --git a/translations/pt-BR/content/graphql/guides/managing-enterprise-accounts.md b/translations/pt-BR/content/graphql/guides/managing-enterprise-accounts.md index 7b8572348a..fc3873f6d5 100644 --- a/translations/pt-BR/content/graphql/guides/managing-enterprise-accounts.md +++ b/translations/pt-BR/content/graphql/guides/managing-enterprise-accounts.md @@ -58,8 +58,9 @@ Para alguns exemplos de consulta, veja "[Exemplo de consulta usando a API de Con - `admin:enterprise` Os escopos específicos da conta corporativa são: - - `admin:enterprise`: Fornece controle total de empresas (inclui `manage_billing:enterprise` e `read:enterprise`) - - `manage_billing:enterprise`: Lê e grava dados de cobrança da empresa. + - `admin:enterprise`: Gives full control of enterprises (includes {% ifversion ghes > 3.2 or fpt or ghae %}`manage_runners:enterprise`, {% endif %}`manage_billing:enterprise` and `read:enterprise`) + - `manage_billing:enterprise`: Read and write enterprise billing data.{% ifversion ghes > 3.2 or fpt or ghae %} + - `manage_runners:enterprise`: Access to manage GitHub Actions enterprise runners and runner-groups.{% endif %} - `read:enterprise`: Lê dados do perfil empresarial. 4. Copie seu token de acesso pessoal e guarde-o em um lugar seguro até adicioná-lo ao seu cliente do GraphQL. diff --git a/translations/pt-BR/content/graphql/guides/using-the-graphql-api-for-discussions.md b/translations/pt-BR/content/graphql/guides/using-the-graphql-api-for-discussions.md index 7949b6e3af..4b1c3c789b 100644 --- a/translations/pt-BR/content/graphql/guides/using-the-graphql-api-for-discussions.md +++ b/translations/pt-BR/content/graphql/guides/using-the-graphql-api-for-discussions.md @@ -1080,4 +1080,4 @@ Campos de tipo de retorno: ## Pesquisar -A discussão pode ser retornada do campo de `pesquisa` de alto nível. Para pesquisar uma discussão, especifique o `tipo` como `DSCUSSÃO`. O tipo `SearchResultItemConnection` tem um campo `discussionCount` para relatar o número de discussões retornadas, e o tipo `Discussão` é adicionado à união DE `SearchResultItem`. Para obter mais informações, consulte "[Consultas](/graphql/reference/queries#searchresultitemconnection)" e "[Pesquisando discussões](/github/searching-for-information-on-github/searching-discussions)". +A discussão pode ser retornada do campo de `pesquisa` de alto nível. Para pesquisar uma discussão, especifique o `tipo` como `DSCUSSÃO`. O tipo `SearchResultItemConnection` tem um campo `discussionCount` para relatar o número de discussões retornadas, e o tipo `Discussão` é adicionado à união DE `SearchResultItem`. Para obter mais informações, consulte "[Consultas](/graphql/reference/queries#searchresultitemconnection)" e "[Pesquisando discussões](/search-github/searching-on-github/searching-discussions)". diff --git a/translations/pt-BR/content/index.md b/translations/pt-BR/content/index.md index 22f2fbadfe..6d0e27e2ec 100644 --- a/translations/pt-BR/content/index.md +++ b/translations/pt-BR/content/index.md @@ -27,6 +27,7 @@ children: - actions - codespaces - packages + - search-github - developers - rest - graphql 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 85c1446f7f..54885fab7d 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 @@ -1,6 +1,7 @@ --- title: Atribuir problemas e pull requests a outros usuários do GitHub intro: Os responsáveis esclarecem quem está trabalhando em problemas e pull requests específicos. +permissions: 'Anyone with write access to a repository can assign issues and pull requests. {% data reusables.enterprise-accounts.emu-permission-repo %}' redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/assigning-issues-and-pull-requests-to-other-github-users - /articles/assigning-issues-and-pull-requests-to-other-github-users @@ -15,8 +16,6 @@ topics: shortTitle: Atribuir problemas & PRs --- -Qualquer pessoa com permissões de gravação em um repositório pode atribuir problemas e pull requests. - ## 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)". diff --git a/translations/pt-BR/content/issues/tracking-your-work-with-issues/creating-an-issue.md b/translations/pt-BR/content/issues/tracking-your-work-with-issues/creating-an-issue.md index 8057cf5889..242d8b7cdf 100644 --- a/translations/pt-BR/content/issues/tracking-your-work-with-issues/creating-an-issue.md +++ b/translations/pt-BR/content/issues/tracking-your-work-with-issues/creating-an-issue.md @@ -1,7 +1,7 @@ --- title: Criar um problema intro: 'Os problemas podem ser criados de várias maneiras. Portanto, você pode escolher o método mais conveniente para seu fluxo de trabalho.' -permissions: People with read permissions can create an issue in a repository where issues are enabled. +permissions: 'People with read access can create an issue in a repository where issues are enabled. {% data reusables.enterprise-accounts.emu-permission-repo %}' redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/creating-an-issue - /articles/creating-an-issue @@ -43,17 +43,17 @@ Os problemas podem ser usados para acompanhar erros, aprimoramentos ou outras so {% data reusables.repositories.assign-an-issue-as-project-maintainer %} {% data reusables.repositories.submit-new-issue %} -## Creating an issue with {% data variables.product.prodname_cli %} +## Criando um problema com {% data variables.product.prodname_cli %} -{% data reusables.cli.about-cli %} To learn more about {% data variables.product.prodname_cli %}, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)." +{% data reusables.cli.about-cli %} Para saber mais sobre {% data variables.product.prodname_cli %}, consulte "[Sobre {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)." -To create an issue, use the `gh issue create` subcommand. To skip the interactive prompts, include the `--body` and the `--title` flags. +Para criar um problema, use o subcomando `gh issue create`. Para ignorar as instruções interativas, inclua os sinalizadores `--body` e `--title`. ```shell gh issue create --title "My new issue" --body "Here are more details." ``` -You can also specify assignees, labels, milestones, and projects. +Você também pode especificar responsáveis, etiquetas, marcos e projetos. ```shell gh issue create --title "My new issue" --body "Here are more details." --assignee @me,monalisa --label "bug,help wanted" --project onboarding --milestone "learning codebase" @@ -90,15 +90,15 @@ Você pode abrir um novo problema a partir de um comentário em um problema ou p {% ifversion fpt %} -## Creating an issue from discussion +## Criando um problema da discussão -People with triage permission to a repository can create an issue from a discussion. +As pessoas com permissão de triagem para um repositório podem criar um problema a partir de uma discussão. -When you create an issue from a discussion, the contents of the discussion post will be automatically included in the issue body, and any labels will be retained. Creating an issue from a discussion does not convert the discussion to an issue or delete the existing discussion. For more information about {% data variables.product.prodname_discussions %}, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." +Ao criar um problema a partir de uma discussão, o conteúdo da postagem na discussão será automaticamente incluído no texto do problema e todas as etiquetas serão mantidas. A criação de um problema a partir de uma discussão não converte a discussão em um problema ou exclui a discussão existente. Para obter mais informações sobre {% data variables.product.prodname_discussions %}, consulte "[Sobre discussões "](/discussions/collaborating-with-your-community-using-discussions/about-discussions)". {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %} -1. In the right sidebar, click {% octicon "issue-opened" aria-label="The issues icon" %} **Create issue from discussion**. ![Button to create issue from discussion](/assets/images/help/discussions/create-issue-from-discussion.jpg) +1. Na barra lateral direita, clique em {% octicon "issue-opened" aria-label="The issues icon" %} **Criar problema a partir da discussão**. ![Botão para criar um problema da discussão](/assets/images/help/discussions/create-issue-from-discussion.jpg) {% data reusables.repositories.type-issue-title-and-description %} {% data reusables.repositories.assign-an-issue-as-project-maintainer %} {% data reusables.repositories.submit-new-issue %} 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 248ae847be..f089c4d243 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 @@ -1,6 +1,6 @@ --- -title: Filtering and searching issues and pull requests -intro: 'To find detailed information about a repository on {% data variables.product.product_name %}, you can filter, sort, and search issues and pull requests that are relevant to the repository.' +title: Filtrando e pesquisando problemas e pull requests +intro: 'Para encontrar informações detalhadas sobre um repositório em {% data variables.product.product_name %}, você pode filtrar, ordenar e pesquisar problemas e pull requests que são relevantes para o repositório.' redirect_from: - /github/managing-your-work-on-github/finding-information-in-a-repository/filtering-issues-and-pull-requests-by-assignees - /articles/filtering-issues-and-pull-requests-by-assignees @@ -40,7 +40,7 @@ versions: topics: - Issues - Pull requests -shortTitle: Filter and search +shortTitle: Filtrar e pesquisar --- {% data reusables.cli.filter-issues-and-pull-requests-tip %} @@ -65,7 +65,7 @@ Problemas e pull requests possuem um conjunto de filtros padrão que podem ser a ## Filtrar problemas e pull requests por responsáveis -Once you've [assigned an issue or pull request to someone](/articles/assigning-issues-and-pull-requests-to-other-github-users), you can find items based on who's working on them. +Uma vez que você [atribuiu um problema ou pull request a alguém](/articles/assigning-issues-and-pull-requests-to-other-github-users), você poderá encontrar itens baseado em quem está trabalhando neles. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} @@ -80,7 +80,7 @@ Para limpar a seleção de filtro, clique em **Clear current search query, filte ## Filtrar problemas e pull requests por etiquetas -Once you've [applied labels to an issue or pull request](/articles/applying-labels-to-issues-and-pull-requests), you can find items based on their labels. +Depois que [aplicou etiquetas a um problema ou pull request](/articles/applying-labels-to-issues-and-pull-requests), você poderá encontrar itens baseados nas suas etiquetas. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} @@ -102,7 +102,8 @@ Você pode filtrar uma lista de pull requests do repositório para encontrar: - Pull requests que [necessitam de revisão](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging) antes de serem mescladas - Pull requests que um revisor aprovou - Pull requests nas quais um revisor solicitou alterações -- Pull requests que você revisou +- Os pull requests que você revisou{% ifversion fpt or ghae or ghes > 3.2 %} +- Pull requests que alguém pediu para você para revisar diretamente{% endif %} - Pull requests que [alguém solicitou revisão a você ou a uma equipe a que você pertence](/articles/requesting-a-pull-request-review) {% data reusables.repositories.navigate-to-repo %} @@ -112,9 +113,9 @@ Você pode filtrar uma lista de pull requests do repositório para encontrar: ## Usar a pesquisa para filtrar problemas e pull requests -You can use advanced filters to search for issues and pull requests that meet specific criteria. +Você pode usar filtros avançados para pesquisar problemas e pull requests que atendam a critérios específicos. -### Searching for issues and pull requests +### Pesquisando problemas e pull requests {% include tool-switcher %} @@ -136,15 +137,15 @@ A barra de pesquisa de problemas e pull requests permite que você defina seus p {% data reusables.cli.cli-learn-more %} -You can use the {% data variables.product.prodname_cli %} to search for issues or pull requests. Use the `gh issue list` or `gh pr list` subcommand along with the `--search` argument and a search query. +Você pode usar o {% data variables.product.prodname_cli %} para pesquisar problemas ou pull requests. Use o subcomando `gh issue list` ou `gh pr list` junto com o argumento `--search` e uma consulta de pesquisa. -For example, you can list, in order of date created, all issues that have no assignee and that have the label `help wanted` or `bug`. +Por exemplo, você pode listar, na ordem da data de criação, todos os problemas que não têm nenhum responsável e que têm a etiqueta `help wanted` ou `erro`. ```shell gh issue list --search 'no:assignee label:"help wanted",bug sort:created-asc' ``` -You can also list all pull requests that mention the `octo-org/octo-team` team. +Você também pode listar todos os pull requests que mencionam a equipe `octo-org/octo-team`. ```shell gh pr list --search "team:octo-org/octo-team" @@ -152,7 +153,7 @@ gh pr list --search "team:octo-org/octo-team" {% endcli %} -### About search terms +### Sobre termos de pesquisa Com os termos da pesquisa de problemas e pull requests, é possível: @@ -165,9 +166,9 @@ Com os termos da pesquisa de problemas e pull requests, é possível: {% ifversion fpt or ghes > 3.2 or ghae-next %} {% tip %} -**Tip:** You can filter issues and pull requests by label using logical OR or using logical AND. -- To filter issues using logical OR, use the comma syntax: `label:"bug","wip"`. -- To filter issues using logical AND, use separate label filters: `label:"bug" label:"wip"`. +**Dica:** Você pode filtrar problemas e pull requests por etiqueta, usando a lógica OU ou E. +- Para filtrar problemas usando ROM OR, use a sintaxe de vírgula: `label:"bug","wip"`. +- Para filtrar problemas usando a lógica E, use filtros separados de etiqueta: `label:"bug" label:"wip"`. {% endtip %} {% endif %} @@ -185,7 +186,8 @@ Para pull requests, você também pode usar a pesquisa para: - Filtrar pull requests que tenham sido aprovadas por um revisor: `state:open type:pr review:approved` - Filtrar pull requests nas quais um revisor tenha solicitado alterações: `state:open type:pr review:changes_requested` - Filtrar pull requests por [revisor](/articles/about-pull-request-reviews/): `state:open type:pr reviewed-by:octocat` -- Filtrar pull requests pelo usuário específico [solicitado para revisão](/articles/requesting-a-pull-request-review): `state:open type:pr review-requested:octocat` +- Filtrar pull requests por usuário específico [solicitado para revisão](/articles/requesting-a-pull-request-review): `state:open type:pr review-requested:octocat`{% ifversion fpt or ghae or ghes > 3.2 %} +- 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 %} - Filtro por pull requests que estão vinculadas a um problema que a pull request pode concluir: `linked:issue`{% endif %} @@ -224,4 +226,4 @@ Por exemplo, se você filtrar por problemas atribuídos a Hubot e ordenar pelos ## Leia mais -- "[Searching issues and pull requests](/articles/searching-issues)"" +- "[Pesquisando problemas e pull requests](/articles/searching-issues)"" diff --git a/translations/pt-BR/content/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository.md b/translations/pt-BR/content/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository.md index 3b5335d342..21f51e1af7 100644 --- a/translations/pt-BR/content/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository.md +++ b/translations/pt-BR/content/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository.md @@ -1,6 +1,7 @@ --- title: Fixar um problema no repositório intro: Você pode fixar até três problemas importantes acima da lista de problemas em seu repositório. +permissions: 'People with write access to a repository can pin issue in the repository. {% data reusables.enterprise-accounts.emu-permission-repo %}' redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/pinning-an-issue-to-your-repository - /articles/pinning-an-issue-to-your-repository @@ -17,8 +18,6 @@ shortTitle: Fixar um problema ![Problemas fixos](/assets/images/help/issues/pinned-issues.png) -Para fixar um problema, você deve ter permissões de gravação no repositório onde está o problema. - {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issues %} 1. Na lista de problemas, clique no problema que deseja fixar. diff --git a/translations/pt-BR/content/issues/tracking-your-work-with-issues/quickstart.md b/translations/pt-BR/content/issues/tracking-your-work-with-issues/quickstart.md index b942f5ba71..ca0d37b956 100644 --- a/translations/pt-BR/content/issues/tracking-your-work-with-issues/quickstart.md +++ b/translations/pt-BR/content/issues/tracking-your-work-with-issues/quickstart.md @@ -19,7 +19,7 @@ Este guia demonstra como usar {% data variables.product.prodname_github_issues % ## Pré-requisitos -Para criar um problema, você precisa de um repositório. Você pode usar um repositório existente ao qual você tem acesso de gravação ou criar um novo repositório. O repositório deve ter problemas habilitados. Para obter mais informações sobre como criar um repositório, consulte "[Criar um repositório](/articles/creating-a-new-repository)". Para obter mais informações sobre problemas de habilitação se eles estiverem desabilitados no seu repositório, consulte "[Desabilitar problemas](/github/administering-a-repository/managing-repository-settings/disabling-issues)". +Para criar um problema, você precisa de um repositório. Você pode usar um repositório existente ao qual você tem acesso de gravação ou criar um novo repositório. {% data reusables.enterprise-accounts.emu-permission-repo %} The repository must have issues enabled. Para obter mais informações sobre como criar um repositório, consulte "[Criar um repositório](/articles/creating-a-new-repository)". Para obter mais informações sobre problemas de habilitação se eles estiverem desabilitados no seu repositório, consulte "[Desabilitar problemas](/github/administering-a-repository/managing-repository-settings/disabling-issues)". ## Abrir um problema em branco diff --git a/translations/pt-BR/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md b/translations/pt-BR/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md index 5e2baa3536..f33b919399 100644 --- a/translations/pt-BR/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md +++ b/translations/pt-BR/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md @@ -42,7 +42,7 @@ As pessoas ou equipes mencionadas no problema receberão uma notificação infor {% data reusables.cli.cli-learn-more %} -To transfer an issue, use the `gh issue transfer` subcommand. Replace the `issue` parameter with the number or URL of the issue. Replace the `{% ifversion ghes %}hostname/{% endif %}owner/repo` parameter with the {% ifversion ghes %}URL{% else %}name{% endif %} of the repository that you want to transfer the issue to, such as `{% ifversion ghes %}https://ghe.io/{% endif %}octocat/octo-repo`. +Para transferir um problema, use o subcomando `gh issue transfer`. Substitua o parâmetro `problema` pelo número ou URL do problema. Substitua o parâmetro `{% ifversion ghes %}nome do host/{% endif %}proprietário/repositório` pelo {% ifversion ghes %}URL{% else %}nome{% endif %} do repositório para o qual você deseja transferir o problema como, por exemplo, `{% ifversion ghes %}https://ghe. o/{% endif %}octocat/octo-repo`. ```shell gh issue transfer issue {% ifversion ghes %}hostname/{% endif %}owner/repo diff --git a/translations/pt-BR/content/issues/using-labels-and-milestones-to-track-work/filtering-issues-and-pull-requests-by-milestone.md b/translations/pt-BR/content/issues/using-labels-and-milestones-to-track-work/filtering-issues-and-pull-requests-by-milestone.md index eb64a4ba68..fe1822544e 100644 --- a/translations/pt-BR/content/issues/using-labels-and-milestones-to-track-work/filtering-issues-and-pull-requests-by-milestone.md +++ b/translations/pt-BR/content/issues/using-labels-and-milestones-to-track-work/filtering-issues-and-pull-requests-by-milestone.md @@ -31,5 +31,5 @@ shortTitle: Filtrar por marco ## Leia mais -- "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)" +- "[Filtrando e pesquisando problemas e pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)" - "[Filtrar cartões em um quadro de projeto](/articles/filtering-cards-on-a-project-board)" diff --git a/translations/pt-BR/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md b/translations/pt-BR/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md index 41154a57e5..4cf341bf17 100644 --- a/translations/pt-BR/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md +++ b/translations/pt-BR/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md @@ -1,6 +1,7 @@ --- title: Gerenciar etiquetas intro: 'Você pode classificar {% ifversion fpt %}problemas, pull requests e discussões{% else %}problemas e pull requests{% endif %} criando, editando, aplicando e excluindo etiquetas.' +permissions: '{% data reusables.enterprise-accounts.emu-permission-repo %}' redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/managing-labels - /articles/managing-Labels @@ -30,8 +31,6 @@ topics: Você pode gerenciar seu trabalho em {% data variables.product.product_name %} criando etiquetas para classificar {% ifversion fpt %}problemas, pull requests e discussões{% else %}problemas e pull requests{% endif %}. Você pode aplicar etiquetas no repositório em que foram criadas. Uma vez criada uma etiqueta, você poderá usá-la em qualquer {% ifversion fpt %}problema, pull request ou discussão{% else %}problema ou pull request{% endif %} dentro desse repositório. -Qualquer pessoa com acesso de leitura a um repositório pode exibir e pesquisar etiquetas do repositório. Qualquer pessoa com acesso de triagem a um repositório pode aplicar/ignorar etiquetas existentes. Para criar, editar, aplicar ou excluir uma etiqueta, é preciso ter acesso de gravação ao repositório. - ## Sobre as etiquetas padrão O {% data variables.product.product_name %} fornece etiquetas padrão para todos os repositórios novos. Você pode usar essas etiquetas padrão para ajudar com a criação de um fluxo de trabalho padronizado em um repositório. @@ -58,6 +57,8 @@ Os proprietários da organização podem personalizar as etiquetas padrão para ## Criar uma etiqueta +Anyone with write access to a repository can create a label. + {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} {% data reusables.project-management.labels %} @@ -69,11 +70,15 @@ Os proprietários da organização podem personalizar as etiquetas padrão para ## Aplicando uma etiqueta +Anyone with triage access to a repository can apply and dismiss labels. + 1. Acesse {% ifversion fpt %}problema, pull request ou discussão{% else %}problema ou pull request{% endif %}. 1. Na barra lateral direita, à direita de "Etiquetas", clique em {% octicon "gear" aria-label="The gear icon" %} e, em seguida, clique em uma etiqueta. ![Menu suspenso "Etiquetas"](/assets/images/help/issues/labels-drop-down.png) ## Editar uma etiqueta +Anyone with write access to a repository can edit existing labels. + {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} {% data reusables.project-management.labels %} @@ -85,6 +90,8 @@ Os proprietários da organização podem personalizar as etiquetas padrão para ## Excluir uma etiqueta +Anyone with write access to a repository can delete existing labels. + Excluir uma etiqueta removerá a etiqueta dos problemas e pull requests. {% data reusables.repositories.navigate-to-repo %} diff --git a/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md index e1f860da65..2bdeaefaaa 100644 --- a/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md +++ b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md @@ -24,6 +24,8 @@ As contas corporativas permitem que proprietários gerenciem centralmente a pol Para organizações que pertencem a uma conta corporativa, a cobrança é gerenciada no nível da conta corporativa e as configurações de cobrança não estão disponíveis no nível da organização. Os proprietários de empresa podem definir a política para todas as organizações na conta corporativa ou permitir que os proprietários da organização definam a política no nível da organização. Os proprietários da organização não podem alterar as configurações aplicadas à sua organização no nível da conta corporativa. Se você tiver dúvidas sobre uma política ou configuração da sua organização, entre em contato com o proprietário da conta corporativa. +{% data reusables.enterprise-accounts.invite-organization %} + {% data reusables.gated-features.enterprise-accounts %} {% data reusables.organizations.org-ownership-recommendation %} Para obter mais informações, consulte "[Manter a continuidade da propriedade para sua organização](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)". diff --git a/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md b/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md index f4360c4fff..faff294f53 100644 --- a/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md +++ b/translations/pt-BR/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md @@ -25,6 +25,18 @@ Você pode visualizar e revogar a identidade vinculada de cada integrante, as se {% data reusables.saml.about-linked-identities %} +Quando disponível, a entrada incluirá dados de SCIM. Para obter mais informações, consulte "[Sobre o SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)". + +{% warning %} + +**Aviso:** Para organizações que usam SCIM: +- A revogação de uma identidade de usuário vinculada em {% data variables.product.product_name %} também removerá os metadados SAML e SCIM. Como resultado, o provedor de identidade não poderá sincronizar ou desprovisionar a identidade do usuário vinculada. +- Um administrador deverá revogar uma identidade vinculada por meio do provedor de identidade. +- Para revogar uma identidade vinculada e vincular uma conta diferente por meio do provedor de identidade, um administrador pode remover e reatribuir o usuário ao aplicativo de {% data variables.product.product_name %}. For more information, see your identity provider's documentation. + +{% endwarning %} + + {% data reusables.identity-and-permissions.revoking-identity-team-sync %} {% data reusables.profile.access_org %} diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md index 803ffdc755..ece28fca4a 100644 --- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md +++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md @@ -54,95 +54,96 @@ Some of the features listed below are limited to organizations using {% data var {% endnote %} {% endif %} -| Ação no repositório | Leitura | Triagem | Gravação | Manutenção | Administrador | -|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-------:|:-------:|:--------:|:----------:|:------------------------------------------------:| -| Fazer pull nos repositórios atribuídos ao usuário ou à equipe | **X** | **X** | **X** | **X** | **X** | -| Bifurcar os repositórios atribuídos ao usuário ou à equipe | **X** | **X** | **X** | **X** | **X** | -| Editar e excluir seus próprios comentários | **X** | **X** | **X** | **X** | **X** | -| Criar problemas | **X** | **X** | **X** | **X** | **X** | -| Fechar os problemas que eles criaram | **X** | **X** | **X** | **X** | **X** | -| Reabrir problemas que eles fecharam | **X** | **X** | **X** | **X** | **X** | -| Ter um problema atribuído a eles | **X** | **X** | **X** | **X** | **X** | -| Enviar pull requests de bifurcações dos repositórios atribuídos à equipe | **X** | **X** | **X** | **X** | **X** | -| Enviar revisões em pull requests | **X** | **X** | **X** | **X** | **X** | -| Exibir as versões publicadas | **X** | **X** | **X** | **X** | **X** |{% ifversion fpt %} -| Visualizar [execuções de fluxo de trabalho no GitHub Actions](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **X** | **X** | **X** | **X** | **X** +| Ação no repositório | Leitura | Triagem | Gravação | Manutenção | Administrador | +|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-------:|:-------:|:--------:|:----------:|:-----------------------------------------------------:| +| Fazer pull nos repositórios atribuídos ao usuário ou à equipe | **X** | **X** | **X** | **X** | **X** | +| Bifurcar os repositórios atribuídos ao usuário ou à equipe | **X** | **X** | **X** | **X** | **X** | +| Editar e excluir seus próprios comentários | **X** | **X** | **X** | **X** | **X** | +| Criar problemas | **X** | **X** | **X** | **X** | **X** | +| Fechar os problemas que eles criaram | **X** | **X** | **X** | **X** | **X** | +| Reabrir problemas que eles fecharam | **X** | **X** | **X** | **X** | **X** | +| Ter um problema atribuído a eles | **X** | **X** | **X** | **X** | **X** | +| Enviar pull requests de bifurcações dos repositórios atribuídos à equipe | **X** | **X** | **X** | **X** | **X** | +| Enviar revisões em pull requests | **X** | **X** | **X** | **X** | **X** | +| Exibir as versões publicadas | **X** | **X** | **X** | **X** | **X** |{% ifversion fpt %} +| Visualizar [execuções de fluxo de trabalho no GitHub Actions](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **X** | **X** | **X** | **X** | **X** {% endif %} -| Editar wikis | **X** | **X** | **X** | **X** | **X** |{% ifversion fpt %} -| [Denunciar conteúdo abusivo ou spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** +| Edit wikis in public repositories | **X** | **X** | **X** | **X** | **X** | +| Edit wikis in private repositories | | | **X** | **X** | **X** |{% ifversion fpt %} +| [Denunciar conteúdo abusivo ou spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** {% endif %} -| Aplicar/ignorar etiquetas | | **X** | **X** | **X** | **X** | -| Criar, editar, excluir etiquetas | | | **X** | **X** | **X** | -| Fechar, reabrir e atribuir todos os problemas e pull requests | | **X** | **X** | **X** | **X** |{% ifversion fpt or ghae or ghes > 3.0 %} -| [Habilitar e desabilitar o merge automático em um pull request](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** +| Aplicar/ignorar etiquetas | | **X** | **X** | **X** | **X** | +| Criar, editar, excluir etiquetas | | | **X** | **X** | **X** | +| Fechar, reabrir e atribuir todos os problemas e pull requests | | **X** | **X** | **X** | **X** |{% ifversion fpt or ghae or ghes > 3.0 %} +| [Habilitar e desabilitar o merge automático em um pull request](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** {% endif %} -| Aplicar marcos | | **X** | **X** | **X** | **X** | -| Marcar [problemas e pull requests duplicados](/articles/about-duplicate-issues-and-pull-requests) | | **X** | **X** | **X** | **X** | -| Solicitar [revisões de pull requests](/articles/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** | -| Merge a [pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges) | | | **X** | **X** | **X** | -| Fazer push (gravar) nos repositórios atribuídos ao usuário ou à equipe | | | **X** | **X** | **X** | -| Editar e excluir comentários de qualquer usuário em commits, pull request e problemas | | | **X** | **X** | **X** | -| [Ocultar comentários de qualquer usuário](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **X** | **X** | **X** | -| [Bloquear conversas](/communities/moderating-comments-and-conversations/locking-conversations) | | | **X** | **X** | **X** | -| Transferir problemas (consulte "[Transferir um problema para outro repositório](/articles/transferring-an-issue-to-another-repository)" para obter mais informações) | | | **X** | **X** | **X** | -| [Atuar como um proprietário do código designado de um repositório](/articles/about-code-owners) | | | **X** | **X** | **X** | -| [Marcar uma pull request de rascunho como pronta para revisão](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | -| [Converter um pull request em rascunho](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | -| Enviar revisões que afetam a capacidade de merge de uma pull request | | | **X** | **X** | **X** | -| [Aplicar alterações sugeridas](/articles/incorporating-feedback-in-your-pull-request) a pull requests | | | **X** | **X** | **X** | -| Criar [verificações de status](/articles/about-status-checks) | | | **X** | **X** | **X** |{% ifversion fpt %} -| Criar, editar, executar, reexecutar e cancelar [fluxos de trabalho no GitHub Actions](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** +| Aplicar marcos | | **X** | **X** | **X** | **X** | +| Marcar [problemas e pull requests duplicados](/articles/about-duplicate-issues-and-pull-requests) | | **X** | **X** | **X** | **X** | +| Solicitar [revisões de pull requests](/articles/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** | +| Merge a [pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges) | | | **X** | **X** | **X** | +| Fazer push (gravar) nos repositórios atribuídos ao usuário ou à equipe | | | **X** | **X** | **X** | +| Editar e excluir comentários de qualquer usuário em commits, pull request e problemas | | | **X** | **X** | **X** | +| [Ocultar comentários de qualquer usuário](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **X** | **X** | **X** | +| [Bloquear conversas](/communities/moderating-comments-and-conversations/locking-conversations) | | | **X** | **X** | **X** | +| Transferir problemas (consulte "[Transferir um problema para outro repositório](/articles/transferring-an-issue-to-another-repository)" para obter mais informações) | | | **X** | **X** | **X** | +| [Atuar como um proprietário do código designado de um repositório](/articles/about-code-owners) | | | **X** | **X** | **X** | +| [Marcar uma pull request de rascunho como pronta para revisão](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | +| [Converter um pull request em rascunho](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | +| Enviar revisões que afetam a capacidade de merge de uma pull request | | | **X** | **X** | **X** | +| [Aplicar alterações sugeridas](/articles/incorporating-feedback-in-your-pull-request) a pull requests | | | **X** | **X** | **X** | +| Criar [verificações de status](/articles/about-status-checks) | | | **X** | **X** | **X** |{% ifversion fpt %} +| Criar, editar, executar, reexecutar e cancelar [fluxos de trabalho no GitHub Actions](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** {% endif %} -| Criar e editar versões | | | **X** | **X** | **X** | -| Exibir versões de rascunho | | | **X** | **X** | **X** | -| Editar a descrição de um repositório | | | | **X** | **X** |{% ifversion fpt or ghae %} -| [Visualizar e instalar pacotes](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | -| [Publicar pacotes](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | -| | | | | | | -| {% ifversion fpt or ghes > 3.0 %}[Excluir e restaurar pacoes](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Excluir pacotes](/packages/learn-github-packages/deleting-a-package){% endif %} | | | | | **X** | {% endif %} -| Gerenciar [tópicos](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** | -| Habilitar wikis e restringir editores de wiki | | | | **X** | **X** | -| Habilitar quadros de projeto | | | | **X** | **X** | -| Configurar [merges de pull request](/articles/configuring-pull-request-merges) | | | | **X** | **X** | -| Configurar [uma fonte de publicação para {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** | -| [Fazer push em branches protegidos](/articles/about-protected-branches) | | | | **X** | **X** | -| [Criar e editar cartões sociais do repositório](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% ifversion fpt %} -| Limitar [interações em um repositório](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository) | | | | **X** | **X** +| Criar e editar versões | | | **X** | **X** | **X** | +| Exibir versões de rascunho | | | **X** | **X** | **X** | +| Editar a descrição de um repositório | | | | **X** | **X** |{% ifversion fpt or ghae %} +| [Visualizar e instalar pacotes](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | +| [Publicar pacotes](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | +| | | | | | | +| {% ifversion fpt or ghes > 3.0 %}[Excluir e restaurar pacoes](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Excluir pacotes](/packages/learn-github-packages/deleting-a-package){% endif %} | | | | | **X** | {% endif %} +| Gerenciar [tópicos](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** | +| Habilitar wikis e restringir editores de wiki | | | | **X** | **X** | +| Habilitar quadros de projeto | | | | **X** | **X** | +| Configurar [merges de pull request](/articles/configuring-pull-request-merges) | | | | **X** | **X** | +| Configurar [uma fonte de publicação para {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** | +| [Fazer push em branches protegidos](/articles/about-protected-branches) | | | | **X** | **X** | +| [Criar e editar cartões sociais do repositório](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% ifversion fpt %} +| Limitar [interações em um repositório](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository) | | | | **X** | **X** {% endif %} -| Excluir um problema (consulte "[Excluir um problema](/articles/deleting-an-issue)") | | | | | **X** | -| Fazer merge de pull requests em branches protegidos, mesmo sem revisões de aprovação | | | | | **X** | -| [Definir os proprietários do código de um repositório](/articles/about-code-owners) | | | | | **X** | -| Adicionar um repositório a uma equipe (consulte "[Gerenciar 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#giving-a-team-access-to-a-repository)" para obter informações) | | | | | **X** | -| [Gerenciar o acesso dos colaboradores externos a um repositório](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | -| [Alterar a visibilidade de um repositório](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | -| Criar um modelo de repositório (consulte "[Criar um modelo de repositório](/articles/creating-a-template-repository)") | | | | | **X** | -| Alterar as configurações do repositório | | | | | **X** | -| Gerenciar o acesso de equipe e de colaborador ao repositório | | | | | **X** | -| Editar o branch padrão do repositório | | | | | **X** |{% ifversion fpt or ghes > 3.0 %} -| Renomeie o branch padrão do repositório (veja "[Renomear um branch](/github/administering-a-repository/renaming-a-branch)") | | | | | **X** | -| Renomeie um branch diferente do branch padrão do repositório (veja "[Renomear um branch](/github/administering-a-repository/renaming-a-branch)") | | | **X** | **X** | **X** +| Excluir um problema (consulte "[Excluir um problema](/articles/deleting-an-issue)") | | | | | **X** | +| Fazer merge de pull requests em branches protegidos, mesmo sem revisões de aprovação | | | | | **X** | +| [Definir os proprietários do código de um repositório](/articles/about-code-owners) | | | | | **X** | +| Adicionar um repositório a uma equipe (consulte "[Gerenciar 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#giving-a-team-access-to-a-repository)" para obter informações) | | | | | **X** | +| [Gerenciar o acesso dos colaboradores externos a um repositório](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | +| [Alterar a visibilidade de um repositório](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | +| Criar um modelo de repositório (consulte "[Criar um modelo de repositório](/articles/creating-a-template-repository)") | | | | | **X** | +| Alterar as configurações do repositório | | | | | **X** | +| Gerenciar o acesso de equipe e de colaborador ao repositório | | | | | **X** | +| Editar o branch padrão do repositório | | | | | **X** |{% ifversion fpt or ghes > 3.0 or ghae-next %} +| Renomeie o branch padrão do repositório (veja "[Renomear um branch](/github/administering-a-repository/renaming-a-branch)") | | | | | **X** | +| Renomeie um branch diferente do branch padrão do repositório (veja "[Renomear um branch](/github/administering-a-repository/renaming-a-branch)") | | | **X** | **X** | **X** {% endif %} -| Gerenciar webhooks e chaves de implantação | | | | | **X** |{% ifversion fpt %} -| [Gerenciar as configurações do uso de dados para seu repositório privado](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **X** +| Gerenciar webhooks e chaves de implantação | | | | | **X** |{% ifversion fpt %} +| [Gerenciar as configurações do uso de dados para seu repositório privado](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **X** {% endif %} -| [Gerenciar a política de bifurcação de um repositório](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | -| [Transferir repositório na organização](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | -| [Excluir ou transferir repositórios na organização](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | -| [Arquivar repositórios](/articles/about-archiving-repositories) | | | | | **X** |{% ifversion fpt %} -| Exibir um botão de patrocinador (consulte "[Exibir um botão de patrocinador no seu repositório](/articles/displaying-a-sponsor-button-in-your-repository)") | | | | | **X** +| [Gerenciar a política de bifurcação de um repositório](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | +| [Transferir repositório na organização](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | +| [Excluir ou transferir repositórios na organização](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | +| [Arquivar repositórios](/articles/about-archiving-repositories) | | | | | **X** |{% ifversion fpt %} +| Exibir um botão de patrocinador (consulte "[Exibir um botão de patrocinador no seu repositório](/articles/displaying-a-sponsor-button-in-your-repository)") | | | | | **X** {% endif %} -| Criar referências de link automático para recursos externos, como JIRA ou Zendesk (consulte "[Configurar links automáticos para apontar para recursos externos](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **X** |{% ifversion fpt %} -| [Habilitar {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) em um repositório | | | | **X** | **X** | -| [Criar e editar categorias](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) para {% data variables.product.prodname_discussions %} | | | | **X** | **X** | -| [Mover uma discussão para uma categoria diferente](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [Transferir uma discussão](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) para um novo repositório | | | **X** | **X** | **X** | -| [Gerenciar discussões fixadas](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [Converter problemas para discussões em massa](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [Bloquear e desbloquear discussões](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [Converter individualmente problemas em discussões](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [Criar novas discussões e comentar em discussões existentes](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** | -| [Excluir uma discussão](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion) | | | | **X** | **X** |{% endif %}{% ifversion fpt %} -| Crie [codespaces](/codespaces/about-codespaces) | | | **X** | **X** | **X** +| Criar referências de link automático para recursos externos, como JIRA ou Zendesk (consulte "[Configurar links automáticos para apontar para recursos externos](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **X** |{% ifversion fpt %} +| [Habilitar {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) em um repositório | | | | **X** | **X** | +| [Criar e editar categorias](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) para {% data variables.product.prodname_discussions %} | | | | **X** | **X** | +| [Mover uma discussão para uma categoria diferente](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Transferir uma discussão](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) para um novo repositório | | | **X** | **X** | **X** | +| [Gerenciar discussões fixadas](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Converter problemas para discussões em massa](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Bloquear e desbloquear discussões](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [Converter individualmente problemas em discussões](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [Criar novas discussões e comentar em discussões existentes](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** | +| [Excluir uma discussão](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion) | | | | **X** | **X** |{% endif %}{% ifversion fpt %} +| Crie [codespaces](/codespaces/about-codespaces) | | | **X** | **X** | **X** {% endif %} ### Requisitos de permissão para funcionalidades de segurança 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 9098c175ad..611f443cc4 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 @@ -36,7 +36,7 @@ Como alternativa, você pode habilitar o {% data variables.product.prodname_acti {% endif %} -{% ifversion fpt or ghes > 2.22 %} +{% ifversion fpt or ghes > 2.22 or ghae-next %} ## Gerenciar as permissões de {% data variables.product.prodname_actions %} para a sua organização @@ -63,7 +63,12 @@ Você pode desabilitar todos os fluxos de trabalho para uma organização ou def {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.settings-sidebar-actions %} -1. Em **Políticas**, selecione **Permitir ações específicas** e adicione as suas ações necessárias à lista. ![Adicionar ações para permitir lista](/assets/images/help/organizations/actions-policy-allow-list.png) +1. Em **Políticas**, selecione **Permitir ações específicas** e adicione as suas ações necessárias à lista. + {%- ifversion ghes %} + ![Adicionar ações para permitir lista](/assets/images/help/organizations/actions-policy-allow-list.png) + {%- else %} + ![Adicionar ações para permitir lista](/assets/images/enterprise/github-ae/organizations/actions-policy-allow-list.png) + {%- endif %} 1. Clique em **Salvar**. {% endif %} @@ -71,7 +76,9 @@ Você pode desabilitar todos os fluxos de trabalho para uma organização ou def {% ifversion fpt %} ## Configurar a aprovação necessária para fluxos de trabalho de bifurcações públicas -{% data reusables.actions.workflow-run-approve-public-fork %} Você pode configurar este comportamento para uma organização usando o procedimento abaixo. A modificação desta configuração substitui a configuração definida no nível corporativo. +{% data reusables.actions.workflow-run-approve-public-fork %} + +You can configure this behavior for an organization using the procedure below. A modificação desta configuração substitui a configuração definida no nível corporativo. {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/transferring-organization-ownership.md b/translations/pt-BR/content/organizations/managing-organization-settings/transferring-organization-ownership.md index 8d16c6bedd..7974ad8b40 100644 --- a/translations/pt-BR/content/organizations/managing-organization-settings/transferring-organization-ownership.md +++ b/translations/pt-BR/content/organizations/managing-organization-settings/transferring-organization-ownership.md @@ -15,6 +15,13 @@ topics: shortTitle: Transferir propriedade --- +{% ifversion fpt %} +{% note %} + +**Observação:** {% data reusables.enterprise-accounts.invite-organization %} + +{% endnote %}{% endif %} + 1. Caso você seja o único integrante com privilégios de *proprietário*, atribua a função de proprietário a outro integrante da organização. Para obter mais informações, consulte "[Designar um proprietário da organização](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization#appointing-an-organization-owner)". 2. Entre em contato com o novo proprietário e verifique se ele consegue [acessar as configurações da organização](/articles/accessing-your-organization-s-settings). {% ifversion fpt %} diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md index dba973d3f9..32a43859c1 100644 --- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md @@ -13,13 +13,15 @@ topics: shortTitle: IAM com SSO do SAML --- +{% data reusables.enterprise-accounts.emu-saml-note %} + ## Sobre o SAML SSO {% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.saml-accounts %} -Os proprietários da organização podem aplicar o SSO do SAML para uma organização individual ou os proprietários corporativos podem aplicar o SSO do SAML para todas as organizações em uma conta corporativa. For more information, see "[Enforcing SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account)." +Os proprietários da organização podem aplicar o SSO do SAML para uma organização individual ou os proprietários corporativos podem aplicar o SSO do SAML para todas as organizações em uma conta corporativa. Para obter mais informações, consulte "[Aplicar o logon único SAML para organizações na conta corporativa](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account)". {% data reusables.saml.saml-requires-ghec %} {% data reusables.enterprise.link-to-ghec-trial %} @@ -35,7 +37,7 @@ Para acessar os recursos protegidos da organização que usam a API e o Git na l A primeira vez que um membro usar o SAML SSO para acessar sua organização, o {% data variables.product.prodname_dotcom %} criará automaticamente um registro que irá vincular a sua organização, a conta do {% data variables.product.prodname_dotcom %} do integrante e a conta do integrante no seu IdP. Você pode visualizar e revogar a identidade de SAML vinculada, as sessões ativas e credenciais autorizadas para integrantes da sua empresa ou conta corporativa. Para obter mais informações consulte "[Visualizar e gerenciar o acesso de SAML de um integrante 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)" e "[Visualizar e gerenciar o acesso de SAML de um usuário à conta corporativa](/github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise-account)". -Se os integrantes estiverem conectados com uma sessão SAML SSO, ao criarem um novo repositório, a visibilidade-padrão desse repositório será privada. Caso contrário, a visibilidade-padrão será pública. For more information on repository visibility, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." +Se os integrantes estiverem conectados com uma sessão SAML SSO, ao criarem um novo repositório, a visibilidade-padrão desse repositório será privada. Caso contrário, a visibilidade-padrão será pública. 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)". Os integrantes da organização também devem ter uma sessão de SAML ativa para autorizar um {% data variables.product.prodname_oauth_app %}. Você pode optar por não participar deste requisito entrando em contato com {% data variables.contact.contact_support %}. {% data variables.product.product_name %} não recomenda a exclusão deste requisito, o que irá expor sua organização a um maior risco de aquisições de conta e perda potencial de dados. diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md index 7073f1c7ec..ee1cf1acd6 100644 --- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md @@ -12,6 +12,8 @@ topics: - Teams --- +{% data reusables.enterprise-accounts.emu-scim-note %} + Se você usa [SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on) em sua organização, é possível implementar o SCIM pra adicionar, gerenciar e remover o acesso dos integrantes da organização ao {% 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 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. Para remover o acesso, os administradores da organização podem remover o token autorizado manualmente da organização ou automatizar a remoção com o SCIM. 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 54e08df84e..86b46d4b51 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 @@ -25,7 +25,7 @@ Você poderá restaurar integrantes da organização depois que eles tiverem con Bots and service accounts that do not have external identities set up in your organization's IdP will also be removed when you enforce SAML SSO. For more information about bots and service accounts, see "[Managing bots and service accounts with SAML single sign-on](/articles/managing-bots-and-service-accounts-with-saml-single-sign-on)." -If your organization is owned by an enterprise account, requiring SAML for the enterprise account will override your organization-level SAML configuration and enforce SAML SSO for every organization in the enterprise. For more information, see "[Enforcing SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account)." +If your organization is owned by an enterprise account, requiring SAML for the enterprise account will override your organization-level SAML configuration and enforce SAML SSO for every organization in the enterprise. Para obter mais informações, consulte "[Aplicar o logon único SAML para organizações na conta corporativa](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account)". {% tip %} diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md index 397991e710..a94b1d166c 100644 --- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md @@ -17,6 +17,8 @@ topics: shortTitle: Gerenciar sincronização de equipe --- +{% data reusables.enterprise-accounts.emu-scim-note %} + {% data reusables.gated-features.okta-team-sync %} ## Sobre a sincronização de equipes @@ -31,6 +33,8 @@ shortTitle: Gerenciar sincronização de equipe Também é possível habilitar a sincronização de equipes para organizações que pertencem a uma conta corporativa. Para obter mais informações, consulte "[Aplicar as configurações de segurança na conta corporativa](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account)". +{% data reusables.enterprise-accounts.team-sync-override %} + {% data reusables.identity-and-permissions.team-sync-usage-limits %} ## Habilitar a sincronização de equipes diff --git a/translations/pt-BR/content/organizations/organizing-members-into-teams/creating-a-team.md b/translations/pt-BR/content/organizations/organizing-members-into-teams/creating-a-team.md index 11155da5aa..888eee4571 100644 --- a/translations/pt-BR/content/organizations/organizing-members-into-teams/creating-a-team.md +++ b/translations/pt-BR/content/organizations/organizing-members-into-teams/creating-a-team.md @@ -25,11 +25,13 @@ Apenas os proprietários e mantenedores de uma equipe principal podem criar uma {% data reusables.organizations.team_description %} {% data reusables.organizations.create-team-choose-parent %} {% ifversion fpt %} -1. Opcionalmente, se sua conta de organização ou empresa usar a sincronização de equipes, para conectar um grupo de provedor de identidade à sua equipe, use o menu suspenso "Grupos de provedores de identidade" e selecione até 5 grupos de provedores de identidade. Para obter mais informações, consulte "[Sincronizando uma equipe com um grupo de provedores de identidade ](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)." ![Menu suspenso para escolher grupos de provedores de identidade](/assets/images/help/teams/choose-an-idp-group.png) +1. Optionally, if your organization or enterprise account uses team synchronization or your enterprise uses {% data variables.product.prodname_emus %}, connect an identity provider group to your team. + * If your enterprise uses {% data variables.product.prodname_emus %}, use the "Identity Provider Groups" drop-down menu, and select a single identity provider group to connect to the new team. For more information, "[Managing team memberships with identity provider groups](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)." + * If your organization or enterprise account uses team synchronization, use the "Identity Provider Groups" drop-down menu, and select up to five identity provider groups to connect to the new team. Para obter mais informações, consulte "[Sincronizando uma equipe com um grupo de provedores de identidade ](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)." ![Menu suspenso para escolher grupos de provedores de identidade](/assets/images/help/teams/choose-an-idp-group.png) {% endif %} {% data reusables.organizations.team_visibility %} {% data reusables.organizations.create_team %} -9. Se desejar, [forneça à equipe acesso aos repositórios da organização](/articles/managing-team-access-to-an-organization-repository). +1. Se desejar, [forneça à equipe acesso aos repositórios da organização](/articles/managing-team-access-to-an-organization-repository). ## Leia mais diff --git a/translations/pt-BR/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md b/translations/pt-BR/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md index 1a80056592..285e14182c 100644 --- a/translations/pt-BR/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md +++ b/translations/pt-BR/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md @@ -45,8 +45,11 @@ Any team members that have set their status to "Busy" will not be selected for r 7. Em "Quantos membros da equipe devem ser atribuídos para a revisão?, use o menu suspenso e escolha um número de revisores a serem atribuídos a cada pull request. ![Menu suspenso do número de revisores](/assets/images/help/teams/review-assignment-number.png) 8. Em "Algoritmo de encaminhamento", use o menu suspenso e escolha qual algoritmo você gostaria de usar. Para obter mais informações, consulte "[Algoritmos de encaminhamento](#routing-algorithms)". ![Menu suspenso do algoritmo de encaminhamento](/assets/images/help/teams/review-assignment-algorithm.png) 9. Opcionalmente, para sempre ignorar determinados membros da equipe, selecione **Nunca atribuir certos integrantes da equipe**. Em seguida, selecione um ou mais integrantes da equipe que você gostaria de ignorar sempre. ![Menu suspenso e caixa de seleção "Nunca atribuir certos integrantes da equipe"](/assets/images/help/teams/review-assignment-skip-members.png) -10. Opcionalmente, para notificar apenas os integrantes da equipe escolhidos pela atribuição de revisão de código para cada solicitação de revisão de pull request, em "Notificações", selecione **Ao atribuir integrantes da equipe, não notifique toda a equipe.** ![Notificações de atribuições de revisão de código](/assets/images/help/teams/review-assignment-notifications.png) -11. Clique em **Save changes** (Salvar alterações). +10. Optionally, to only notify the team members chosen by code review assignment for each pull review request, under "Notifications" select **If assigning team members, don't notify the entire team.** ![Code review assignment notifications](/assets/images/help/teams/review-assignment-notifications.png){% ifversion fpt or ghae or ghes > 3.2 %} +11. Optionally, to include members of child teams as potential reviewers when assigning requests, select **Child team members**. +12. Optionally, to count any members whose review has already been requested against the total number of members to assign, select **Count existing requests**. +13. Optionally, to remove the review request from the team when assigning team members, select **Team review request**.{% endif %} +14. Clique em **Save changes** (Salvar alterações). ## Desabilitar atribuição de revisão de código {% data reusables.profile.access_org %} 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 710411d94a..084f3d9232 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 @@ -16,6 +16,8 @@ shortTitle: Sincronizar com um IdP {% data reusables.gated-features.okta-team-sync %} +{% data reusables.enterprise-accounts.emu-scim-note %} + ## Sobre a sincronização de equipes {% data reusables.identity-and-permissions.about-team-sync %} @@ -26,6 +28,8 @@ shortTitle: Sincronizar com um IdP Uma vez que uma equipe do {% data variables.product.prodname_dotcom %} está conectada a um grupo de IdP, o administrador do IdP deve efetuar as alterações da associação da equipe por meio do provedor de identidade. Você não pode gerenciar a associação da equipe em {% data variables.product.product_name %}{% ifversion fpt %} ou usando a API{% endif %}. +{% ifversion fpt %}{% data reusables.enterprise-accounts.team-sync-override %}{% endif %} + {% ifversion fpt %} Todas as alterações de membros da equipe feitas através do seu IdP aparecerão no log de auditoria do {% data variables.product.product_name %} como alterações feitas pelo bot de sincronização de equipe. Seu IdP enviará dados de membros da equipe para {% data variables.product.prodname_dotcom %} uma vez a cada hora. A conexão de uma equipe a um grupo de IdP pode remover alguns integrantes da equipe. Para obter mais informações, consulte "[Requisitos para integrantes de equipes sincronizadas](#requirements-for-members-of-synchronized-teams)". {% endif %} @@ -54,8 +58,6 @@ Um integrante removido da equipe pode ser adicionado de volta a uma equipe autom Para evitar a remoção involuntária dos integrantes da equipe, recomendamos a aplicar SSO SAML na conta da organização ou da empresa. criar novas equipes para sincronizar dados da associação e verificar a associação de grupo de IdP antes de sincronizar as equipes existentes. For more information, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)" and "[Enforcing SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account)." -Se sua organização pertencer a uma conta corporativa, habilitar a sincronização de equipes para a conta corporativa irá substituir as configurações de sincronização de equipe no nível da organização. Para obter mais informações, consulte "[Gerenciar a sincronização de equipes para organizações na sua conta corporativa](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)". - {% endif %} ## Pré-requisitos diff --git a/translations/pt-BR/content/packages/learn-github-packages/installing-a-package.md b/translations/pt-BR/content/packages/learn-github-packages/installing-a-package.md index e9c6fa026d..61ecd32878 100644 --- a/translations/pt-BR/content/packages/learn-github-packages/installing-a-package.md +++ b/translations/pt-BR/content/packages/learn-github-packages/installing-a-package.md @@ -18,7 +18,7 @@ versions: ## Sobre a instalação do pacote -Você pode pesquisar {% data variables.product.product_name %} para encontrar pacotes no {% data variables.product.prodname_registry %} que você pode instalar no seu próprio projeto. Para obter mais informações, consulte "[Pesquisar pacotes no {% data variables.product.prodname_registry %}](/github/searching-for-information-on-github/searching-for-packages)". +Você pode pesquisar {% data variables.product.product_name %} para encontrar pacotes no {% data variables.product.prodname_registry %} que você pode instalar no seu próprio projeto. Para obter mais informações, consulte "[Pesquisar pacotes no {% data variables.product.prodname_registry %}](/search-github/searching-on-github/searching-for-packages)". Depois de encontrar um pacote, você pode ler a descrição e as instruções de instalação e utilização na página de pacotes. diff --git a/translations/pt-BR/content/packages/learn-github-packages/viewing-packages.md b/translations/pt-BR/content/packages/learn-github-packages/viewing-packages.md index 5765328ea2..f73aa2d61d 100644 --- a/translations/pt-BR/content/packages/learn-github-packages/viewing-packages.md +++ b/translations/pt-BR/content/packages/learn-github-packages/viewing-packages.md @@ -64,4 +64,4 @@ Você pode encontrar e visualizar qualquer pacote que você publicou em todas as ## Leia mais -- "[Procurar pacotes](/github/searching-for-information-on-github/searching-for-packages)" +- "[Procurar pacotes](/search-github/searching-on-github/searching-for-packages)" diff --git a/translations/pt-BR/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md b/translations/pt-BR/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md index 7800cceba2..822a9bab0f 100644 --- a/translations/pt-BR/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md +++ b/translations/pt-BR/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md @@ -15,8 +15,6 @@ shortTitle: Publicar & instalar com ações {% data reusables.package_registry.packages-ghes-release-stage %} {% data reusables.package_registry.packages-ghae-release-stage %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## Sobre {% data variables.product.prodname_registry %} com {% data variables.product.prodname_actions %} diff --git a/translations/pt-BR/content/packages/quickstart.md b/translations/pt-BR/content/packages/quickstart.md index 4a34e0ea98..6146876a74 100644 --- a/translations/pt-BR/content/packages/quickstart.md +++ b/translations/pt-BR/content/packages/quickstart.md @@ -10,8 +10,6 @@ shortTitle: QuickStart --- {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## Introdução diff --git a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md index 18cc645620..f1d9f86ad0 100644 --- a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md +++ b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md @@ -160,7 +160,11 @@ Você pode instalar pacotes do {% data variables.product.prodname_registry %} ad Por padrão, você pode adicionar pacotes a partir de uma organização. Para obter mais informações, consulte [Instalar pacotes de outras organizações](#installing-packages-from-other-organizations)." -Você também precisa adicionar o arquivo *.npmrc* ao seu projeto para que todas as solicitações de instalação passem pelo {% data variables.product.prodname_registry %}. Ao encaminhar todas as solicitações através de {% data variables.product.prodname_registry %}, você pode usar pacotes com escopo e sem escopo de *npmjs.com*. Para obter mais informações, consulte "[npm-scope](https://docs.npmjs.com/misc/scope)" na documentação npm. +You also need to add the *.npmrc* file to your project so that all requests to install packages will {% ifversion ghae %}be routed to{% else %}go through{% endif %} {% data variables.product.prodname_registry %}. {% ifversion fpt or ghes > 2.21 %}When you route all package requests through {% data variables.product.prodname_registry %}, you can use both scoped and unscoped packages from *npmjs.org*. For more information, see "[npm-scope](https://docs.npmjs.com/misc/scope)" in the npm documentation.{% endif %} + +{% ifversion ghae %} +By default, you can only use npm packages hosted on your enterprise, and you will not be able to use unscoped packages. For more information on package scoping, see "[npm-scope](https://docs.npmjs.com/misc/scope)" in the npm documentation. If required, {% data variables.product.prodname_dotcom %} support can enable an upstream proxy to npmjs.org. Once an upstream proxy is enabled, if a requested package isn't found on your enterprise, {% data variables.product.prodname_registry %} makes a proxy request to npmjs.org. +{% endif %} {% data reusables.package_registry.authenticate-step %} {% data reusables.package_registry.create-npmrc-owner-step %} 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 88b61f137d..a005477b27 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 @@ -12,7 +12,11 @@ shortTitle: Alterar a visibilidade do site ## Sobre controle de acesso para sites de {% data variables.product.prodname_pages %} -Se o seu site de projeto for publicado de um repositório privado ou interno, pertencente a uma organização que usa {% data variables.product.prodname_ghe_cloud %}, você poderá gerenciar o controle de acesso para o site. Com controle de acesso, você pode optar por publicar o site publicamente para qualquer pessoa na internet ou em particular para pessoas com acesso de leitura ao seu repositório. Um site publicado de forma privada pode ser usado para compartilhar sua documentação interna ou base de conhecimento com integrantes da sua empresa. 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)". +With access control for {% data variables.product.prodname_pages %}, you can restrict access to your {% data variables.product.prodname_pages %} site by publishing the site privately. A privately published site can only be accessed by people with read access to the repository the site is published from. You can use privately published sites to share your internal documentation or knowledge base with members of your enterprise. + +If your enterprise uses {% data variables.product.prodname_emus %}, all {% data variables.product.prodname_pages %} sites are privately published. For more information about {% data variables.product.prodname_emus %}, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." + +If your organization uses {% data variables.product.prodname_ghe_cloud %} without {% data variables.product.prodname_emus %}, you can choose to publish your sites privately or publicly to anyone on the internet. Access control is available for project sites that are published from a private or internal repository that are owned by the organization. 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)". Os sites publicados em particular estão disponíveis em um subdomínio diferente dos sites publicados em modo público. Isso garante que seu site do {% data variables.product.prodname_pages %} esteja seguro a partir do momento em que for publicado: diff --git a/translations/pt-BR/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md b/translations/pt-BR/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md index 5b353c4379..0937343f7e 100644 --- a/translations/pt-BR/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md +++ b/translations/pt-BR/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md @@ -22,6 +22,12 @@ Todos os sites do {% data variables.product.prodname_pages %}, incluindo os site {% data reusables.pages.private_pages_are_public_warning %} +{% note %} + +**Note:** RFC3280 states that the maximum length of the common name should be 64 characters. Therefore, the entire domain name of your {% data variables.product.prodname_pages %} site must be less than 64 characters long for a certificate to be successfully created. + +{% endnote %} + ## Exigir HTTPS para o site do {% data variables.product.prodname_pages %} {% data reusables.pages.navigate-site-repo %} diff --git a/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md index 667a67a886..3c2869df0f 100644 --- a/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md +++ b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md @@ -157,7 +157,7 @@ Este erro significa que você tem permalinks relativos, que não são compatíve Permalinks são URLs permanentes que fazem referência a uma determinada página no seu site. Os permalinks absolutos iniciam com a raiz do site, enquanto os permalinks relativos iniciam com a pasta que contém a página referenciada. O {% data variables.product.prodname_pages %} e o Jekyll não são mais compatíveis com permalinks relativos. Para obter mais informações sobre permalinks, consulte "[Permalinks](https://jekyllrb.com/docs/permalinks/)" na documentação do Jekyll. -Para solucionar problemas, remova a linha `relative_permalinks` do arquivo *_config.yml* e reformate os permalinks relativos no site com permalinks absolutos. For more information, see "[Editing files](/repositories/working-with-files/managing-files/editing-files)." +Para solucionar problemas, remova a linha `relative_permalinks` do arquivo *_config.yml* e reformate os permalinks relativos no site com permalinks absolutos. Para obter mais informações, consulte "[Editando arquivos](/repositories/working-with-files/managing-files/editing-files)". ## O link simbólico não existe no repositório do site diff --git a/translations/pt-BR/content/repositories/archiving-a-github-repository/archiving-repositories.md b/translations/pt-BR/content/repositories/archiving-a-github-repository/archiving-repositories.md index 3dcced9cc8..cb92717d7f 100644 --- a/translations/pt-BR/content/repositories/archiving-a-github-repository/archiving-repositories.md +++ b/translations/pt-BR/content/repositories/archiving-a-github-repository/archiving-repositories.md @@ -32,7 +32,7 @@ Depois que um repositório é arquivado, não é possível adicionar nem remover Quando um repositório é arquivado, seus problemas, pull requests, código, etiquetas, marcos, projetos, wiki, versões, commits, tags, branches, reações, alertas de varredura de código e comentários tornam-se somente leitura. Para fazer alterações em um repositório arquivado, você deve desarquivar o repositório primeiro. -É possível pesquisar repositórios arquivados. Para obter mais informações, consulte "[Pesquisar repositórios](/articles/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)". Para obter mais informações, consulte "[Pesquisa de repositórios](/articles/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)". Para obter mais informações, consulte "[Pesquisa de problemas e pull requests](/articles/searching-issues-and-pull-requests/#search-based-on-whether-a-repository-is-archived)". +É possível pesquisar repositórios arquivados. Para obter mais informações, consulte "[Pesquisar repositórios](/search-github/searching-on-github/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)". Para obter mais informações, consulte "[Pesquisa de repositórios](/articles/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)". Para obter mais informações, consulte "[Pesquisa de problemas e pull requests](/search-github/searching-on-github/searching-issues-and-pull-requests/#search-based-on-whether-a-repository-is-archived)". ## Arquivar um repositório diff --git a/translations/pt-BR/content/repositories/archiving-a-github-repository/backing-up-a-repository.md b/translations/pt-BR/content/repositories/archiving-a-github-repository/backing-up-a-repository.md index 346f8be368..0cc6615374 100644 --- a/translations/pt-BR/content/repositories/archiving-a-github-repository/backing-up-a-repository.md +++ b/translations/pt-BR/content/repositories/archiving-a-github-repository/backing-up-a-repository.md @@ -36,7 +36,7 @@ Quando você clona um repositório ou wiki, somente os dados Git, como arquivos - [Projetos](/rest/reference/projects#list-repository-projects) {% endif %} -Assim que tiver {% ifversion ghes or ghae %}uma versão local de todo o conteúdo do qual deseja fazer backup, você poderá criar um arquivo zip e {% else %}baixado seu arquivo, você poderá{% endif %}copiá-lo em um disco rígido externo e/ou fazer upload dele em um serviço de backup baseado na nuvem, como o [Google Drive](https://www.google.com/drive/) ou [Dropbox](https://www.dropbox.com/). +Once you have {% ifversion ghes or ghae %}a local version of all the content you want to back up, you can create a zip archive and {% else %}downloaded your archive, you can {% endif %}copy it to an external hard drive and/or upload it to a cloud-based backup or storage service such as [Azure Blob Storage](https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-overview/), [Google Drive](https://www.google.com/drive/) or [Dropbox](https://www.dropbox.com/). {% ifversion fpt %} ## Ferramentas de backup de terceiros diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md index c7d29f07a2..997b95eba9 100644 --- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md +++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md @@ -28,13 +28,13 @@ Você pode escolher o branch-padrão para um repositório. O branch-padrão é o {% endnote %} {% endif %} -{% ifversion fpt or ghes > 3.0 %} +{% ifversion fpt or ghes > 3.0 or ghae-next %} Você também pode renomear o branch padrão. Para obter mais informações, consulte "[Renomear um branch](/github/administering-a-repository/renaming-a-branch). {% endif %} -{% ifversion fpt or ghes > 2.22 %} +{% ifversion fpt or ghes > 2.22 or ghae-next %} {% data reusables.branches.set-default-branch %} diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md index fe2a5742a2..d536d2b9d4 100644 --- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md +++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md @@ -5,6 +5,7 @@ permissions: People with write permissions to a repository can rename a branch i versions: fpt: '*' ghes: '>=3.1' + ghae: next topics: - Repositories redirect_from: 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 bd1c64a69e..6c9d150b27 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 @@ -74,7 +74,7 @@ Todos os integrantes da empresa têm permissões de leitura no repositório inte {% data reusables.repositories.internal-repo-default %} -Se um usuário for removido de todas as organizações pertencentes à empresa, essas bifurcações do usuário dos repositórios internos do usuário serão removidas automaticamente. +Any member of the enterprise can fork any internal repository owned by an organization in the enterprise. The forked repository will belong to the member's user account, and the visibility of the fork will be private. Se um usuário for removido de todas as organizações pertencentes à empresa, essas bifurcações do usuário dos repositórios internos do usuário serão removidas automaticamente. {% endif %} ## Limites para visualização de conteúdo e diffs no repositório @@ -107,6 +107,7 @@ As páginas de visualização comparada e pull requests exibem uma lista de comm ## Leia mais - "[Criar um repositório](/articles/creating-a-new-repository)" +- "[Sobre bifurcações](/github/collaborating-with-pull-requests/working-with-forks/about-forks)" - "[Colaborar com problemas e pull requests](/categories/collaborating-with-issues-and-pull-requests)" - "[Gerenciar seu trabalho no {% data variables.product.prodname_dotcom %}](/categories/managing-your-work-on-github/)" - "[Administrar um repositório](/categories/administering-a-repository)" diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md index 33fea40dfb..80b7636cda 100644 --- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md +++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md @@ -46,18 +46,19 @@ Lisa, M., & Bot, H. (2017). My Research Software (Version 2.0.4) [Computer softw {% raw %} ``` -@misc{Lisa_My_Research_Software_2017, +@software{Lisa_My_Research_Software_2017, author = {Lisa, Mona and Bot, Hew}, doi = {10.5281/zenodo.1234}, month = {12}, title = {{My Research Software}}, url = {https://github.com/github/linguist}, + version = {2.0.4}, year = {2017} } ``` {% endraw %} -Note the example above produces a _software_ citation (i.e., `@misc` type in BibTeX rather than `@article`). +Note the example above produces a _software_ citation (i.e., `@software` type in BibTeX rather than `@article`). For more information, see the [Citation File Format](https://citation-file-format.github.io/) website. @@ -67,9 +68,15 @@ When you add a `CITATION.cff` file to the default branch of your repository, it ## Citing something other than software -If you would prefer the GitHub citation information to link to another resource such as a research paper then you can use the `preferred-citation` override in CFF. +If you would prefer the {% data variables.product.prodname_dotcom %} citation information to link to another resource such as a research article, then you can use the `preferred-citation` override in CFF with the following types. -Extended CITATION.cff file describing the software, but linking to a research paper as the preferred citation: +| Resource | Tipo | +| ---------------- | ------------------ | +| Research article | `article` | +| Conference paper | `conference-paper` | +| Book | `livro` | + +Extended CITATION.cff file describing the software, but linking to a research article as the preferred citation: ``` cff-version: 1.2.0 @@ -132,6 +139,10 @@ Lisa, M., & Bot, H. (2021). My awesome research software. Journal Title, 1(1), 1 ``` {% endraw %} +## Citing a dataset + +If your repository contains a dataset, you can set `type: dataset` in your `CITATION.cff` file to produce a data citation string output in the {% data variables.product.prodname_dotcom %} citation prompt. + ## Other citation files The GitHub citation feature will also detect a small number of additional files that are often used by communities and projects to describe how they would like their work to be cited. diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md index 0503e08d07..b98b5b4586 100644 --- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md +++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md @@ -29,7 +29,7 @@ Os administradores de repositório podem adicionar qualquer tópico que desejare {% ifversion ghae %}Interno {% else %}Público, interna, {% endif %}e repositórios privados podem ter tópicos, embora você veja apenas repositórios privados aos quais você tem acesso nos resultados de pesquisa de tópicos. -Você pode pesquisar repositórios que são associados a um tópico específico. Para obter mais informações, consulte "[Pesquisar repositórios](/articles/searching-for-repositories#search-by-topic)". Também é possível pesquisar uma lista de tópicos no {% data variables.product.product_name %}. Para obter mais informações, consulte "[Pesquisar tópicos](/articles/searching-topics)". +Você pode pesquisar repositórios que são associados a um tópico específico. Para obter mais informações, consulte "[Pesquisar repositórios](/search-github/searching-on-github/searching-for-repositories#search-by-topic)". Também é possível pesquisar uma lista de tópicos no {% data variables.product.product_name %}. Para obter mais informações, consulte "[Pesquisar tópicos](/search-github/searching-on-github/searching-topics)". ## Adicionar tópicos ao repositório diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md index 892454b147..e21d342ef8 100644 --- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md +++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md @@ -73,7 +73,7 @@ Como uma prática recomendada, incentivamos que você inclua o arquivo da licen | | The Unlicense | `unlicense` | | | Licença zLib | `zlib` | -Quando você pesquisar uma família de licenças, os resultados incluirão todas as licenças daquela família. Por exemplo, quando você usa a consulta `license:gpl`, seus resultados incluirão repositórios licenciados sob a Licença Pública Geral GNU v2.0 e Licença Pública Geral GNU v3.0. Para obter mais informações, consulte "[Pesquisar repositórios](/articles/searching-for-repositories/#search-by-license)". +Quando você pesquisar uma família de licenças, os resultados incluirão todas as licenças daquela família. Por exemplo, quando você usa a consulta `license:gpl`, seus resultados incluirão repositórios licenciados sob a Licença Pública Geral GNU v2.0 e Licença Pública Geral GNU v3.0. Para obter mais informações, consulte "[Pesquisar repositórios](/search-github/searching-on-github/searching-for-repositories/#search-by-license)". ## Identificar uma licença 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 d638f29010..6cc4a7429b 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 @@ -43,7 +43,7 @@ Como alternativa, você pode habilitar o {% data variables.product.prodname_acti {% endif %} -{% ifversion fpt or ghes > 2.22 %} +{% ifversion fpt or ghes > 2.22 or ghae-next %} ## Gerenciando as permissões do {% data variables.product.prodname_actions %} para o seu repositório @@ -72,14 +72,21 @@ Como alternativa, você pode habilitar o {% data variables.product.prodname_acti {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.settings-sidebar-actions %} -1. Em **Permissões de ações**, selecione **Permitir ações específicas** e adicione as suas ações necessárias à lista. ![Adicionar ações para permitir lista](/assets/images/help/repository/actions-policy-allow-list.png) +1. Em **Permissões de ações**, selecione **Permitir ações específicas** e adicione as suas ações necessárias à lista. + {%- ifversion ghes %} + ![Adicionar ações para permitir lista](/assets/images/help/repository/actions-policy-allow-list.png) + {%- else %} + ![Adicionar ações para permitir lista](/assets/images/enterprise/github-ae/repository/actions-policy-allow-list.png) + {%- endif %} 2. Clique em **Salvar**. {% endif %} {% ifversion fpt %} ## Configurar a aprovação necessária para fluxos de trabalho de bifurcações públicas -{% data reusables.actions.workflow-run-approve-public-fork %} Você pode configurar este comportamento para um repositório usando o procedimento abaixo. A modificação desta configuração substitui a configuração definida no nível da organização ou empresa. +{% data reusables.actions.workflow-run-approve-public-fork %} + +You can configure this behavior for a repository using the procedure below. A modificação desta configuração substitui a configuração definida no nível da organização ou empresa. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} @@ -124,6 +131,43 @@ As permissões padrão também podem ser configuradas nas configurações da org

    {% endif %}

    +

    {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %}

    + +

    Allowing access to components in an internal repository

    + +

    {% note %}

    + +

    Observação: {% data reusables.gated-features.internal-repos %}

    + +

    {% endnote %}

    + +

    Members of your enterprise can use internal repositories to work on projects without sharing information publicly. For information, see "About repositories."

    + +

    To configure whether workflows in an internal repository can be accessed from outside the repository:

    + +
      +
    1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of the internal repository.
      2. +

    2. Under your repository name, click {% octicon "gear" aria-label="The gear icon" %} Settings. +

      + +

      {% data reusables.repositories.settings-sidebar-actions %}

      3. +

    3. Under Access, choose one of the access settings: +Set the access to Actions components

      4. +
    + +
      +
    • Not accessible - Workflows in other repositories can't use workflows in this repository.
      • +
    • Accessible by any repository in the organization - Workflows in other repositories can use workflows in this repository as long as they are part of the same organization.
      • +
    • Accessible by any repository in the enterprise - Workflows in other repositories can use workflows in this repository as long as they are part of the same enterprise. + +
        +

      1. Clique em Salvar para aplicar as configurações. +

        + +

        {% endif %}

        2. +
      • +
    +

    {% ifversion fpt or ghes > 2.22 or ghae %}

    Configuring the retention period for {% data variables.product.prodname_actions %} artifacts and logs in your repository

    diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md index acba572f1c..376c6a38e0 100644 --- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md +++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md @@ -21,6 +21,12 @@ shortTitle: Visibilidade do repositório Os proprietários da organização podem restringir a capacidade de alterar a visibilidade do repositório apenas para os proprietários da organização. Para obter mais informações, consulte "[Restringir as alterações de visibilidade do repositório na sua organização](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)". +{% ifversion fpt %} + +If you're a member of an {% data variables.product.prodname_emu_enterprise %}, your repositories owned by your user account can only be private, and repositories in your enterprise's organizations can only be private or internal. + +{% endif %} + Recomendamos revisar as seguintes advertências antes de alterar a visibilidade de um repositório. {% ifversion ghes or ghae %} 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 1674c66f5a..769c9ccffd 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 @@ -34,6 +34,9 @@ Você pode receber notificações quando novas versões são publicadas em um re 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)." {% ifversion fpt %} + +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)." + 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 {% data variables.large_files.product_name_short %} objetos nos arquivos de seu repositório](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)".

    diff --git a/translations/pt-BR/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md b/translations/pt-BR/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md new file mode 100644 index 0000000000..6b714826c6 --- /dev/null +++ b/translations/pt-BR/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md @@ -0,0 +1,93 @@ +--- +title: Automatically generated release notes +intro: You can automatically generate release notes for your GitHub releases +permissions: Repository collaborators and people with write access to a repository can generate and customize automated release notes for a release. +versions: + fpt: '*' +topics: + - Repositories +shortTitle: Automated release notes +--- + +{% note %} + +**Observação:** {% data reusables.repositories.auto-gen-release-public-beta %} + +{% endnote %} + +## About automatically generated release notes + +Automatically generated release notes provide an automated alternative to manually writing release notes for your {% data variables.product.prodname_dotcom %} releases. With automatically generated release notes, you can quickly generate an overview of the contents of a release. You can also customize your automated release notes, using labels to create custom categories to organize pull requests you want to include, and exclude certain labels and users from appearing in the output. + +## Creating automatically generated release notes for a new release + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.releases %} +3. Clique em **Draft a new release** (Rascunhar uma nova versão). ![Botão Releases draft (Rascunho de versões)](/assets/images/help/releases/draft_release_button.png) +4. {% ifversion fpt %}Click **Choose a tag** and type{% else %}Type{% endif %} a version number for your release. Alternatively, select an existing tag. + {% ifversion fpt %} + ![Enter a tag](/assets/images/help/releases/releases-tag-create.png) +5. If you are creating a new tag, click **Create new tag**. ![Confirm you want to create a new tag](/assets/images/help/releases/releases-tag-create-confirm.png) + {% else %} + ![Versão com tag das versões](/assets/images/enterprise/releases/releases-tag-version.png) +{% endif %} +6. If you have created a new tag, use the drop-down menu to select the branch that contains the project you want to release. + {% ifversion fpt %}![Choose a branch](/assets/images/help/releases/releases-choose-branch.png) + {% else %}![Branch com tag das versões](/assets/images/enterprise/releases/releases-tag-branch.png) + {% endif %} +7. To the top right of the description text box, click **Auto-generate release notes**. ![Auto-generate release notes](/assets/images/help/releases/auto-generate-release-notes.png) +8. Check the generated notes to ensure they include all (and only) the information you want to include. +9. Opcionalmente, para incluir arquivos binários, como programas compilados em sua versão, arraste e solte ou selecione arquivos manualmente na caixa de binários. ![Fornecer um DMG com a versão](/assets/images/help/releases/releases_adding_binary.gif) +10. Para notificar os usuários que a versão não está pronta para produção e pode ser instável, selecione **This is a pre-release** (Esta é uma versão prévia). ![Caixa de seleção para marcar uma versão como pré-versão](/assets/images/help/releases/prerelease_checkbox.png) +{%- ifversion fpt %} +11. Opcionalmente, selecione **Criar uma discussão para esta versão** e, em seguida, selecione a **Categoria** no menu suspenso e clique em uma categoria para a discussão da versão. ![Caixa de seleção para criar uma discussão de versão e menu suspenso para escolher uma categoria](/assets/images/help/releases/create-release-discussion.png) +{%- endif %} +12. Se estiver pronto para tornar pública a sua versão, clique em **Publish release** (Publicar versão). Para trabalhar na versão posteriormente, clique em **Save draft** (Salvar rascunho). ![Botões Publish release (Publicar versão) e Draft release (Rascunhar versão)](/assets/images/help/releases/release_buttons.png) + + +## Creating a template for automatically generated release notes + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.files.add-file %} +3. In the file name field, type `.github/release.yml` to create the `release.yml` file in the `.github` directory. ![Create new file](/assets/images/help/releases/release-yml.png) +4. In the file, specify the pull request labels and authors you want to exclude from this release. You can also create new categories and list the pull request labels to be included in each of them. Para obter mais informações, consulte "[Gerenciar etiquetas](/issues/using-labels-and-milestones-to-track-work/managing-labels)". + +## Exemplo de configuração + +{% raw %} +**release.yml** +```yaml{:copy} +# release.yml + +changelog: + exclude: + labels: + - ignore-for-release + authors: + - octocat + categories: + - title: Breaking Changes 🛠 + labels: + - Semver-Major + - breaking-change + - title: Exciting New Features 🎉 + labels: + - Semver-Minor + - enhancement + - title: Other Changes + labels: + - "*" +``` +{% endraw %} + +## Release template syntax + +| Parameter | Descrição | Obrigatório | Valor | +|:------------------------ |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:---------------------------------------------------------------------------- |:------------------------------------------------------------------------- | +| `registro de alterações` | Defines the contents within it as the custom template for your release notes. | Obrigatório. | No value accepted. | +| `exclusão` | Creates a category of pull requests to be excluded from the release. Can be set at the top-level of the changelog to apply to all categories or applied on a per-category basis. | Opcional | No value accepted. | +| `authors` | Specifies authors to be excluded from the release. | Optional for `exclude` category. | Accepts usernames and bots as values. | +| `categorias` | Defines the nested contents as custom categories to be included in the template. | Opcional | No value accepted. | +| `title` | Creates an individual category. | Required if `categories` parameter exists. | Takes the category name as its value. | +| `etiquetas` | Specifies labels to be used by the enclosing category. | Required if `categories` parameter exists, optional for `exclude` parameter. | Accepts any labels, whether currently existing or planned for the future. | +| `"*"` | Catchall for any pull request not included within a category *above*. If used, it must be added at the end of the file. | Opcional | No value accepted. | diff --git a/translations/pt-BR/content/repositories/releasing-projects-on-github/index.md b/translations/pt-BR/content/repositories/releasing-projects-on-github/index.md index 657ce8c7d0..2949a6282a 100644 --- a/translations/pt-BR/content/repositories/releasing-projects-on-github/index.md +++ b/translations/pt-BR/content/repositories/releasing-projects-on-github/index.md @@ -17,6 +17,7 @@ children: - /viewing-your-repositorys-releases-and-tags - /linking-to-releases - /comparing-releases + - /automatically-generated-release-notes - /automation-for-release-forms-with-query-parameters shortTitle: Projetos de versão --- diff --git a/translations/pt-BR/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md b/translations/pt-BR/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md index e4450564da..bd481fccfa 100644 --- a/translations/pt-BR/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md +++ b/translations/pt-BR/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md @@ -55,13 +55,13 @@ Você pode escolher se objetos {% data variables.large_files.product_name_long % 3. Clique em **Draft a new release** (Rascunhar uma nova versão). ![Botão Releases draft (Rascunho de versões)](/assets/images/help/releases/draft_release_button.png) -4. {% ifversion fpt %}Click **Choose a tag** and type{% else %}Type{% endif %} a version number for your release. +4. {% ifversion fpt %}Click **Choose a tag** and type{% else %}Type{% endif %} a version number for your release. Alternatively, select an existing tag. {% ifversion fpt %} ![Enter a tag](/assets/images/help/releases/releases-tag-create.png) -1. Click **Create new tag**. ![Confirm you want to create a new tag](/assets/images/help/releases/releases-tag-create-confirm.png) +1. If you are creating a new tag, click **Create new tag**. ![Confirm you want to create a new tag](/assets/images/help/releases/releases-tag-create-confirm.png) {% else %} @@ -69,7 +69,7 @@ Você pode escolher se objetos {% data variables.large_files.product_name_long % {% endif %} -5. Use o menu suspenso para selecionar o branch que contém o projeto que você deseja lançar. +5. If you have created a new tag, use the drop-down menu to select the branch that contains the project you want to release. {% ifversion fpt %}![Choose a branch](/assets/images/help/releases/releases-choose-branch.png) @@ -86,7 +86,13 @@ Você pode escolher se objetos {% data variables.large_files.product_name_long % {%- endif %} - ![Descrição das versões](/assets/images/help/releases/releases_description.png) + + + {% ifversion fpt %} Alternatively, you can automatically generate your release notes by clicking **Auto-generate release notes**. + + {% endif %} + + ![Descrição das versões](/assets/images/help/releases/releases_description_auto.png) 7. Opcionalmente, para incluir arquivos binários, como programas compilados em sua versão, arraste e solte ou selecione arquivos manualmente na caixa de binários. ![Fornecer um DMG com a versão](/assets/images/help/releases/releases_adding_binary.gif) @@ -124,7 +130,7 @@ Você pode escolher se objetos {% data variables.large_files.product_name_long % ``` -2. Follow the interactive prompts. Alternatively, you can specify arguments to skip these prompts. For more information about possible arguments, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_release_create). For example, this command creates a prerelease with the specified title and notes. +2. Siga as instruções interativas. Como alternativa, você pode especificar argumentos para pular essas instruções. Para obter mais informações sobre possíveis argumentos, consulte [o manual de {% data variables.product.prodname_cli %}](https://cli.github.com/manual/gh_release_create). For example, this command creates a prerelease with the specified title and notes. diff --git a/translations/pt-BR/content/repositories/working-with-files/using-files/working-with-non-code-files.md b/translations/pt-BR/content/repositories/working-with-files/using-files/working-with-non-code-files.md index cc9382c88d..86d41fd877 100644 --- a/translations/pt-BR/content/repositories/working-with-files/using-files/working-with-non-code-files.md +++ b/translations/pt-BR/content/repositories/working-with-files/using-files/working-with-non-code-files.md @@ -188,6 +188,14 @@ Você pode clicar em {% octicon "file" aria-label="The paper icon" %} para ver a ![Alterações em prosa renderizada](/assets/images/help/repository/rendered_prose_changes.png) +{% ifversion fpt or ghes > 3.2 or ghae-issue-5232 %} + +### Desabilitando a interpretação do Markdown + +{% data reusables.repositories.disabling-markdown-rendering %} + +{% endif %} + ### Exibir alterações nos atributos Nós fornecemos uma dica de ferramenta descrevendo as alterações nos atributos, que diferentes de palavras, não seriam visíveis no documento renderizado. Por exemplo, se a URL de um link for alterada, mostraremos uma dica de ferramenta como esta: 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 c92241226c..0db384925e 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 @@ -122,10 +122,10 @@ $ curl -i -u your_username {% data variables.product.api_url_pre %}/use Quando solicitado, você poderá inserir o seu token OAuth, mas nós recomendamos que você configure uma variável para isso: -Você pode usar `-u "username:$token"` e configurar uma variável para o `token` para evitar deixar seu token no histórico do shell, o que deve ser evitado. +You can use `-u "your_username:$token"` and set up a variable for `token` to avoid leaving your token in shell history, which should be avoided. ```shell -$ curl -i -u username:$token {% data variables.product.api_url_pre %}/users/octocat +$ curl -i -u your_username:$token {% data variables.product.api_url_pre %}/users/octocat ``` diff --git a/translations/pt-BR/content/rest/overview/api-previews.md b/translations/pt-BR/content/rest/overview/api-previews.md index 4590097d50..0768536c02 100644 --- a/translations/pt-BR/content/rest/overview/api-previews.md +++ b/translations/pt-BR/content/rest/overview/api-previews.md @@ -18,13 +18,7 @@ Durante o período de pré-visualização, poderemos alterar alguns recursos com Para acessar uma pré-visualização da API, você precisará fornecer um [tipo de mídia](/rest/overview/media-types) personalizado no cabeçalho `Aceitar` para suas solicitações. A documentação dos recursos para cada pré-visualização especifica qual tipo de mídia personalizado deve ser fornecido. -{% ifversion fpt %} -## Migrações - -Permite que você faça o download de repositórios da conta do usuário ou da organização do GitHub para revisar, fazer backup e [fazer a migração dos dados](/rest/reference/migrations) para {% data variables.product.prodname_ghe_server %}. - -**Tipo de mídia personalizada:** `wyandotte-preview` **Anunciado em:** [2018-05-24](https://developer.github.com/changes/2018-05-24-user-migration-api/) -{% endif %} +{% ifversion ghes < 3.3 %} ## Implementações aprimoradas @@ -32,14 +26,19 @@ Exerça um maior controle sobre as [implantações](/rest/reference/repos#deploy **Tipo de mídia personalizada:** `ant-man-preview` **Anunciado em:** [2016-04-06](https://developer.github.com/changes/2016-04-06-deployment-and-deployment-status-enhancements/) +{% endif %} + +{% ifversion ghes < 3.3 %} + ## Reações Gerencie as [reações](/rest/reference/reactions) de commits, problemas e comentários. -**Tipo de mídia personalizado:** `squirrel-girl-preview` **Anunciado em:** [2016-05-12](https://developer.github.com/changes/2016-05-12-reactions-api-preview/) **Atualização em:** -[ 2016-07](https://developer.github.com/changes/2016-06-07-reactions-api-update/)

    +**Custom media type:** `squirrel-girl-preview` **Announced:** [2016-05-12](https://developer.github.com/changes/2016-05-12-reactions-api-preview/) **Update:** [2016-06-07](https://developer.github.com/changes/2016-06-07-reactions-api-update/) +{% endif %} +{% ifversion ghes < 3.3 %} ## Linha do tempo @@ -47,26 +46,23 @@ Obter uma [lista de eventos](/rest/reference/issues#timeline) para um problema o **Tipo de mídia personalizada:** `mockingbird-preview` **Anunciado em:** [2016-05-23](https://developer.github.com/changes/2016-05-23-timeline-preview-api/) +{% endif %} + {% ifversion ghes %} - - ## Ambientes pre-receive Cria, lista, atualiza e exclui ambientes para hooks pre-receive. -**Tipo de mídia personalizada:** `eye-scream-preview` **Anunciado em:** [2015-07-29](/rest/reference/enterprise-admin#pre-receive-environments) - +**Tipo de mídia personalizada:** `eye-scream-preview` **Anunciado em:** [2015-07-29](/rest/reference/enterprise-admin#pre-receive-environments) {% endif %} - - +{% ifversion ghes < 3.3 %} ## Projetos Gerencie [projetos](/rest/reference/projects). **Custom media type:** `inertia-preview` **Announced:** [2016-09-14](https://developer.github.com/changes/2016-09-14-projects-api/) **Update:** [2016-10-27](https://developer.github.com/changes/2016-10-27-changes-to-projects-api/) - - +{% endif %} ## Pesquisa de commit @@ -74,15 +70,13 @@ Gerencie [projetos](/rest/reference/projects). **Tipo de mídia personalizada:** `cloak-preview` **Anunciado em:** [2017-01-05](https://developer.github.com/changes/2017-01-05-commit-search-api/) - - ## Tópicos do repositório Ver uma lista dos [tópicos do repositório](/articles/about-topics/) em [chamadas](/rest/reference/repos) que retornam resultados do repositório. **Tipo de mídia personalizada:** `mercy-preview` **Anunciado em:** [2017-01-31](https://github.com/blog/2309-introducing-topics) - +{% ifversion ghes < 3.3 %} ## Códigos de conduta @@ -90,10 +84,10 @@ Veja todos os [códigos de conduta](/rest/reference/codes-of-conduct) ou obtenha **Tipo de mídia personalizado:** `scarlet-witch-preview` +{% endif %} + {% ifversion ghae or ghes %} - - ## Webhooks globais Habilita [webhooks globais](/rest/reference/enterprise-admin#global-webhooks/) para [organizações](/webhooks/event-payloads/#organization) e tipos de evento do [usuário](/webhooks/event-payloads/#user). Esta visualização da API só está disponível para {% data variables.product.prodname_ghe_server %}. @@ -103,15 +97,13 @@ Habilita [webhooks globais](/rest/reference/enterprise-admin#global-webhooks/) p {% endif %} - - ## Exigir commits assinados Agora você pode usar a API para gerenciar a configuração para [exigir commits assinados em branches protegidos](/rest/reference/repos#branches). **Tipo de mídia personalizada:** `zzzax-preview` **Anunciado em:** [2018-02-22](https://developer.github.com/changes/2018-02-22-protected-branches-required-signatures) - +{% ifversion ghes < 3.3 %} ## Exigir múltiplas revisões de aprovação @@ -119,21 +111,18 @@ Agora você pode [exigir múltiplas revisões de aprovação](/rest/reference/re **Tipo de mídia personalizada:** `luke-cage-preview` **Anunciado em:** [2018-03-16](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews) +{% endif %} + {% ifversion ghes < 3.0 %} - - ## Verificar execuções e a API de conjuntos de verificações Permite que um aplicativo GitHub execute verificações externas no código de um repositório. Veja as [execuções de verificação](/rest/reference/checks#runs) e [Conjuntos de verificação](/rest/reference/checks#suites) das APIs para obter mais informações. -**Tipo de mídia personalizada:** `antiope-preview` **Anunciado:** [2018-05-07](https://developer.github.com/changes/2018-05-07-new-checks-api-public-beta/) - +**Tipo de mídia personalizada:** `antiope-preview` **Anunciado:** [2018-05-07](https://developer.github.com/changes/2018-05-07-new-checks-api-public-beta/) {% endif %} {% ifversion ghes %} - - ## Acesso de Git anônimo aos repositórios Quando uma instância do {% data variables.product.prodname_ghe_server %} estiver em modo privado, os administradores do site e do repositório podem habilitar o acesso anônimo ao Git para um repositório público. @@ -141,13 +130,8 @@ Quando uma instância do {% data variables.product.prodname_ghe_server %} estive **Tipo de mídia personalizada:** `x ray-preview` **Anunciado:** [2018-07-12](https://blog.github.com/2018-07-12-introducing-enterprise-2-14/) {% endif %} - - - {% ifversion ghes < 3.3 %} - - ## Detalhes do cartão de projeto As respostas da API REST para [eventos de problemas](/rest/reference/issues#events) e [eventos da linha do tempo de problemas](/rest/reference/issues#timeline) agora retornam o campo `project_card` para eventos relacionados ao projeto. @@ -155,13 +139,8 @@ As respostas da API REST para [eventos de problemas](/rest/reference/issues#even **Tipo de mídia personalizada:** `starfox-preview` **Anunciado:** [2018-09-05](https://developer.github.com/changes/2018-09-05-project-card-events) {% endif %} - - - {% ifversion fpt %} - - ## Manifestoes do aplicativo GitHub Os manifestos do aplicativo GitHub permitem que pessoas criem aplicativos GitHub pré-configurados. Veja "[Criar aplicativos GitHub a partir de um manifesto](/apps/building-github-apps/creating-github-apps-from-a-manifest/)" para obter mais inoformações. @@ -170,7 +149,7 @@ Os manifestos do aplicativo GitHub permitem que pessoas criem aplicativos GitHub {% endif %} - +{% ifversion ghes < 3.3 %} ## Status da implantação @@ -178,7 +157,9 @@ Agora você pode atualizar o ambiente `` de um [status de implantação](/rest/r **Tipo de mídia personalizada:** `flash-preview` **Anunciado:** [2018-10-16](https://developer.github.com/changes/2018-10-16-deployments-environments-states-and-auto-inactive-updates/) +{% endif %} +{% ifversion ghes < 3.3 %} ## Permissões de criação de repositório @@ -186,7 +167,7 @@ Agora você pode configurar se os integrantes da organização podem criar repos **Tipos de mídia personalizada:** `surtur-preview` **Anunciado:** [2019-12-03](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/) - +{% endif %} ## Anexos de conteúdo @@ -194,7 +175,7 @@ Agora você pode fornecer mais informações no GitHub para URLs vinculadas a do **Tipos de mídia personalizada:** `corsair-preview` **Anunciado:** [2018-12-10](https://developer.github.com/changes/2018-12-10-content-attachments-api/) - +{% ifversion ghes < 3.3 %} ## Habilitar e desabilitar páginas @@ -202,10 +183,10 @@ Você pode usar os novos pontos de extremidade no [API de páginas](/rest/refere **Tipos de mídia personalizada:** `switcheroo-preview` **Anunciado:** [2019-03-14](https://developer.github.com/changes/2019-03-14-enabling-disabling-pages/) +{% endif %} + {% ifversion ghes < 3.3 %} - - ## Listar branches ou pull requests para um commit Você pode usar dois novos pontos de extremidade na [API de commits](/rest/reference/repos#commits) para listar branches ou pull requests para um commit. @@ -214,15 +195,7 @@ Você pode usar dois novos pontos de extremidade na [API de commits](/rest/refer {% endif %} - - -## Habilitar ou desabilitar alertas de vulnerabilidade para um repositório - -Você pode usar dois novos pontos de extremidade na [API de Repositórios](/rest/reference/repos) para habilitar ou desabilitar os alertas de vulnerabilidade. - -**Tipos de mídia personalizada:** `dorian-preview` **Anunciado:** [2019-04-24](https://developer.github.com/changes/2019-04-24-vulnerability-alerts/) - - +{% ifversion ghes < 3.3 %} ## Atualizar um branch de pull request @@ -230,32 +203,19 @@ Você pode usar um novo ponto de extremidade para [atualizar um branch de pull r **Tipos de mídia personalizada:** `lidian-preview` **Anunciado:** [2019-05-29](https://developer.github.com/changes/2019-05-29-update-branch-api/) -{% ifversion fpt %} - - -## Habilitar ou desabilitar correções de segurança automatizadas - -Você pode usar um novo conjunto de pontos de extremidade para [habilitar e desabilitar as correções de segurança automatizadas](/rest/reference/repos#enable-automated-security-fixes). - -**Tipo de mídia personalizada:** `london-preview` **Anunciado:** [2019-06-04](https://developer.github.com/changes/2019-06-04-automated-security-fixes/) - {% endif %} - - ## Criar e usar modelos de repositório Você pode usar um novo ponto de extremidade para [Criar um repositório usando um modelo](/rest/reference/repos#create-a-repository-using-a-template) e [Criar um repositório para o usuário autenticado](/rest/reference/repos#create-a-repository-for-the-authenticated-user) que é um repositório de modelo, definindo o parâmetro `is_template` como `verdadeiro`. [Obter um repositório](/rest/reference/repos#get-a-repository) para verificar se ele é definido como um repositório de modelo usando a chave `is_template`. **Tipos de mídia personalizada:** `baptiste-preview` **Anunciado:** [2019-07-05](https://developer.github.com/changes/2019-07-16-repository-templates-api/) -{% ifversion fpt or ghes or ghae %} - +{% ifversion ghes < 3.3 %} ## Novo parâmetro de visibilidade para a API de repositórios Você pode definir e recuperar a visibilidade de um repositório na [API de repositórios](/rest/reference/repos). -**Tipos de mídia personalizada:** `nebula-preview` **Anunciado:** [2019-11-25](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/) - +**Tipos de mídia personalizada:** `nebula-preview` **Anunciado:** [2019-11-25](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/) {% endif %} diff --git a/translations/pt-BR/content/rest/overview/troubleshooting.md b/translations/pt-BR/content/rest/overview/troubleshooting.md index 9605abe12d..ae5b8d4611 100644 --- a/translations/pt-BR/content/rest/overview/troubleshooting.md +++ b/translations/pt-BR/content/rest/overview/troubleshooting.md @@ -62,6 +62,10 @@ curl -u my_username:my_password -X POST "https://api.github.com/authorizations" Você deverá alternar para o fluxo do aplicativo web [](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) para gerar tokens de acesso. +## Timeouts + +If {% data variables.product.product_name %} takes more than 10 seconds to process an API request, {% data variables.product.product_name %} will terminate the request and you will receive a timeout response. + {% endif %} [oap-guide]: https://developer.github.com/changes/2015-01-19-an-integrators-guide-to-organization-application-policies/ diff --git a/translations/pt-BR/content/rest/reference/actions.md b/translations/pt-BR/content/rest/reference/actions.md index c95969a40c..cbc6fa648b 100644 --- a/translations/pt-BR/content/rest/reference/actions.md +++ b/translations/pt-BR/content/rest/reference/actions.md @@ -12,7 +12,6 @@ topics: miniTocMaxHeadingLevel: 3 --- -{% data reusables.actions.ae-beta %} A API de {% data variables.product.prodname_actions %} permite que você gerencie {% data variables.product.prodname_actions %} usando a API REST. {% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} require the permissions mentioned in each endpoint. Para obter mais informações, consulte "[Documentação do {% data variables.product.prodname_actions %}](/actions)". @@ -22,8 +21,6 @@ A API de {% data variables.product.prodname_actions %} permite que você gerenci ## Artefatos -{% data reusables.actions.ae-beta %} - A API de Artefatos permite que você faça o download, exclua e recupere informações sobre artefatos de fluxo de trabalho. {% data reusables.actions.about-artifacts %} Para obter mais informações, consulte "[Dados recorrentes do fluxo de trabalho que usam artefatos](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)". {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %} @@ -35,8 +32,6 @@ A API de Artefatos permite que você faça o download, exclua e recupere informa {% ifversion fpt or ghes > 2.22 or ghae %} ## Permissões -{% data reusables.actions.ae-beta %} - A API de Permissões permite que você defina permissões para quais organizações e repositórios têm permissão para executar {% data variables.product.prodname_actions %}, e quais ações podem ser executadas. Para obter mais informações, consulte "[Limites de uso, cobrança e administração](/actions/reference/usage-limits-billing-and-administration#disabling-or-limiting-github-actions-for-your-repository-or-organization)". Você também pode definir permissões para uma empresa. Para obter mais informações, consulte a "[{% data variables.product.prodname_dotcom %} administração do Enterprise](/rest/reference/enterprise-admin#github-actions)" API REST. @@ -48,8 +43,6 @@ Você também pode definir permissões para uma empresa. Para obter mais informa ## Segredos -{% data reusables.actions.ae-beta %} - A API Segredos permite criar, atualizar, excluir e recuperar informações sobre segredos criptografados. {% data reusables.actions.about-secrets %} Para obter mais informações, consulte "[Criando e usando segredos encriptados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)". {% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `secrets` permission to use this API. Os usuários autenticados devem ter acesso de colaborador em um repositório para criar, atualizar ou ler segredos. @@ -60,7 +53,6 @@ A API Segredos permite criar, atualizar, excluir e recuperar informações sobre ## Executores auto-hospedados -{% data reusables.actions.ae-beta %} {% data reusables.actions.ae-self-hosted-runners-notice %} A API de executores auto-hospedados permite que você registre, visualize e exclua executores auto-hospedados. {% data reusables.actions.about-self-hosted-runners %} Para obter mais informações, consulte "[Hospedando seus próprios executores](/actions/hosting-your-own-runners)". @@ -75,7 +67,6 @@ Você pode gerenciar runners auto-hospedados para uma empresa. Para obter mais i ## Grupos de runner auto-hospedados -{% data reusables.actions.ae-beta %} {% data reusables.actions.ae-self-hosted-runners-notice %} A API dos Grupos de Runners auto-hospedados permite que você gerencie grupos de runners auto-hospedados. 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)". @@ -90,8 +81,6 @@ Você pode gerenciar grupos de runners auto-hospedados para uma empresa. Para ob ## Fluxos de trabalho -{% data reusables.actions.ae-beta %} - A API de fluxos de trabalho permite que você veja fluxos de trabalho para um repositório. {% data reusables.actions.about-workflows %} Para obter mais informações, consulte "[Automatizando seu fluxo de trabalho com o GitHub Actions](/actions/automating-your-workflow-with-github-actions)". {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %} @@ -102,8 +91,6 @@ A API de fluxos de trabalho permite que você veja fluxos de trabalho para um re ## Trabalhos de fluxo de trabalho -{% data reusables.actions.ae-beta %} - A API de Trabalhos de Fluxo de Trabalho permite que você visualize logs e trabalhos de fluxo de trabalho. {% data reusables.actions.about-workflow-jobs %} Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para GitHub Actions](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)". {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %} @@ -114,8 +101,6 @@ A API de Trabalhos de Fluxo de Trabalho permite que você visualize logs e traba ## Execução de fluxo de trabalho -{% data reusables.actions.ae-beta %} - A API de execução de fluxo de trabalho permite que você visualize, execute novamente, cancele e visualize os logs para executar o fluxo de trabalho. {% data reusables.actions.about-workflow-runs %} Para obter mais informações, consulte "[Gerenciando uma execução de fluxo de trabalho](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)". {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %} diff --git a/translations/pt-BR/content/rest/reference/activity.md b/translations/pt-BR/content/rest/reference/activity.md index 1f7d6fee49..915bdbf3c6 100644 --- a/translations/pt-BR/content/rest/reference/activity.md +++ b/translations/pt-BR/content/rest/reference/activity.md @@ -145,6 +145,7 @@ Aqui está uma lista da potencial `razão` para receber uma notificação: | `assign` | O problema foi atribuído a você. | | `autor` | Você criou a corrente. | | `comentário` | Você comentou na corrente. | +| `ci_activity` | A {% data variables.product.prodname_actions %} workflow run that you triggered was completed. | | `convite` | Você aceitou um convite para contribuir com o repositório. | | `manual` | Você assinou a corrente (por meio de um problema ou pull request). | | `menção` | Você foi especificamente **@mentioned** no conteúdo. | diff --git a/translations/pt-BR/content/rest/reference/enterprise-admin.md b/translations/pt-BR/content/rest/reference/enterprise-admin.md index 3308ffe049..b356165e3a 100644 --- a/translations/pt-BR/content/rest/reference/enterprise-admin.md +++ b/translations/pt-BR/content/rest/reference/enterprise-admin.md @@ -81,7 +81,6 @@ A versão atual da sua empresa é retornada no cabeçalho de resposta de cada AP ## GitHub Actions -{% data reusables.actions.ae-beta %} {% for operation in currentRestOperations %} {% if operation.subcategory == 'actions' %}{% include rest_operation %}{% endif %} diff --git a/translations/pt-BR/content/rest/reference/gists.md b/translations/pt-BR/content/rest/reference/gists.md index 09c96f7f3f..bd3cd6750c 100644 --- a/translations/pt-BR/content/rest/reference/gists.md +++ b/translations/pt-BR/content/rest/reference/gists.md @@ -1,5 +1,6 @@ --- title: Gists +intro: 'The Gists API enables the authorized user to list, create, update and delete the public gists on {% data variables.product.product_name %}.' redirect_from: - /v3/gists versions: @@ -8,11 +9,12 @@ versions: ghae: '*' topics: - API +miniTocMaxHeadingLevel: 3 --- ### Autenticação -Você pode ler gists públicos {% if currentVersion == "github-ae@latest" or enterpriseServerVersions contém currentVersion %}e criá-los para usuários anônimos sem um token{% else %} de forma anônima, mas você precisa entrar no GitHub para criar gists.{% endif %} Para ler ou escrever gists em nome do usuário, você precisa do escopo OAuth para gists e um token. Para obter mais informações, consulte "[Escopos para aplicativos OAuth](/developers/apps/scopes-for-oauth-apps)." +Você pode ler listas públicas {% ifversion ghae or ghes %}e criá-las para usuários anônimos sem um token.{% else %} anonimamente, mas você precisa conectar-se ao GitHub para criar gist.{% endif %} Para ler ou escrever gists em nome de um usuário, você precisa do escopo do OAuth e de um token. Para obter mais informações, consulte "[Escopos para aplicativos OAuth](/developers/apps/scopes-for-oauth-apps)." diff --git a/translations/pt-BR/content/rest/reference/projects.md b/translations/pt-BR/content/rest/reference/projects.md index c70d5cb30e..74be9ebbac 100644 --- a/translations/pt-BR/content/rest/reference/projects.md +++ b/translations/pt-BR/content/rest/reference/projects.md @@ -1,6 +1,6 @@ --- title: Projetos -intro: 'A API dos Projetos permite que você crie, lista, atualize, exclua e personalize projetos em um repositório.' +intro: 'The Projects API lets you create, list, update, delete and customize projects in a repository.' redirect_from: - /v3/projects versions: diff --git a/translations/pt-BR/content/rest/reference/repos.md b/translations/pt-BR/content/rest/reference/repos.md index d1282a8e36..5583803ac3 100644 --- a/translations/pt-BR/content/rest/reference/repos.md +++ b/translations/pt-BR/content/rest/reference/repos.md @@ -1,5 +1,6 @@ --- title: Repositórios +intro: 'A API Repos permite criar, gerenciar e controlar o fluxo de trabalho público e privado dos repositórios de {% data variables.product.product_name %}.' allowTitleToDifferFromFilename: true redirect_from: - /v3/repos @@ -9,12 +10,31 @@ versions: ghae: '*' topics: - API +miniTocMaxHeadingLevel: 3 --- {% for operation in currentRestOperations %} {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} {% endfor %} +{% ifversion fpt %} +## Autolinks + +{% tip %} + +**Note:** The Autolinks API is in beta and may change. + +{% endtip %} + +To help streamline your workflow, you can use the API to add autolinks to external resources like JIRA issues and Zendesk tickets. For more information, see "[Configuring autolinks to reference external resources](/github/administering-a-repository/configuring-autolinks-to-reference-external-resources)." + +{% data variables.product.prodname_github_apps %} require repository administration permissions with read or write access to use the Autolinks API. + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'autolinks' %}{% include rest_operation %}{% endif %} +{% endfor %} +{% endif %} + ## Branches {% for operation in currentRestOperations %} @@ -31,7 +51,7 @@ topics: ### Tipos de mídia personalizados para comentários de commit -Estes são os tipos de mídia compatíveis com os comentários do commit. Você pode ler mais sobre o uso de tipos de mídia na API [aqui](/rest/overview/media-types). +Estes são os tipos de mídia compatíveis com os comentários do commit. You can read more about the use of media types in the API [here](/rest/overview/media-types). application/vnd.github-commitcomment.raw+json application/vnd.github-commitcomment.text+json @@ -52,7 +72,7 @@ A API de Commits do repositório é compatível com a listagem, visualização e {% if operation.subcategory == 'commits' %}{% include rest_operation %}{% endif %} {% endfor %} -{% if currentVersion == "free-pro-team@latest" %} +{% ifversion fpt %} ## Comunidade {% for operation in currentRestOperations %} @@ -76,7 +96,7 @@ Use o tipo de mídia `.raw` para recuperar o conteúdo do arquivo. Para arquivos de markup, como Markdown ou AsciiDoc, você pode recuperar o HTML interpretado usando o tipo de mídia `.html`. As linguagens de markup são processadas em HTML usando nossa [biblioteca de markup](https://github.com/github/markup) de código aberto. -[Todos os objetos](/rest/reference/repos#get-repository-content) são compatíveis com o seguinte tipo de mídia personalizado: +[All objects](/rest/reference/repos#get-repository-content) support the following custom media type: application/vnd.github.VERSION.object @@ -139,12 +159,12 @@ Abaixo está um diagrama de sequência sobre para como essas interações funcio Tenha em mente que o GitHub nunca terá acesso aos seus servidores. Cabe à sua integração de terceiros interagir com os eventos de implantação. Vários sistemas podem ouvir eventos de implantação, e cabe a cada um desses sistemas decidir se serão responsáveis por retirar o código dos seus servidores, criar código nativo, etc. -Note that the `repo_deployment` [OAuth scope](/developers/apps/scopes-for-oauth-apps) grants targeted access to deployments and deployment statuses **without** granting access to repository code, while the {% if currentVersion != "github-ae@latest" %}`public_repo` and{% endif %}`repo` scopes grant permission to code as well. +Observe que o `repo_deployment` [OAuth escopo](/developers/apps/scopes-for-oauth-apps) concede acesso direcionado a implantações e status **sem** conceder acesso ao código do repositório, enquanto os es escopos {% ifversion not ghae %}`public_repo` e{% endif %}`repositório` também concedem permissão para codificar. ### Implantações inativas -Ao definir o estado de uma implantação como `sucesso`, todas as implantações de ambiente de não produção e não transitórios anteriores no mesmo nome do ambiente irão tornar-se `inativas`. Para evitar isso, você pode definir `auto_inactive` como `falso` ao criar o status de implantação. +When you set the state of a deployment to `success`, then all prior non-transient, non-production environment deployments in the same repository with the same environment name will become `inactive`. Para evitar isso, você pode definir `auto_inactive` como `falso` ao criar o status de implantação. Você pode informar que um ambiente transitório não existe mais definindo seu `estado` como `inativo`. Definir o `estado` como `inativo` mostra a implantação como `destruída` em {% data variables.product.prodname_dotcom %} e remove o acesso a ela. @@ -152,10 +172,10 @@ Você pode informar que um ambiente transitório não existe mais definindo seu {% if operation.subcategory == 'deployments' %}{% include rest_operation %}{% endif %} {% endfor %} -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.1" or currentVersion == "github-ae@next" %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ## Ambientes -The Environments API allows you to create, configure, and delete environments. For more information about environments, see "[Environments](/actions/reference/environments)." To manage environment secrets, see "[Secrets](/rest/reference/actions#secrets)." +A API de Ambientes permite que você crie, configure e exclua ambientes. For more information about environments, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." Para gerenciar segredos de ambiente, consulte "[Segredos](/rest/reference/actions#secrets)". {% for operation in currentRestOperations %} {% if operation.subcategory == 'environments' %}{% include rest_operation %}{% endif %} @@ -182,6 +202,16 @@ Use o ponto de extremidade da API para adicionar um colaborador. Para obter mais {% if operation.subcategory == 'invitations' %}{% include rest_operation %}{% endif %} {% endfor %} +{% ifversion fpt or ghae or ghes > 3.2 %} + +## Git LFS + +{% for operation in currentRestOperations %} + {% if operation.subcategory == 'lfs' %}{% include rest_operation %}{% endif %} +{% endfor %} + +{% endif %} + ## Mesclar A API de merge do repositório é compatível com o merge de branches em um repositório. Isso realiza, essencialmente, a mesma coisa que mesclar um branch em outro em um repositório local e, em seguida, fazer push para {% data variables.product.product_name %}. O benefício é que o merge é realizado no lado do servidor e não é necessário um repositório local. Isso o torna mais apropriado para automação e outras ferramentas em que a manutenção de repositórios locais seria pesada e ineficiente. @@ -194,7 +224,7 @@ O usuário autenticado será o autor de qualquer merge feito por meio deste pont ## Pages -A API de {% data variables.product.prodname_pages %} recupera informações sobre a sua configuração do {% data variables.product.prodname_pages %} e os status das suas criações. Information about the site and the builds can only be accessed by authenticated owners{% if currentVersion != "github-ae@latest" %}, even if the websites are public{% endif %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)". +A API de {% data variables.product.prodname_pages %} recupera informações sobre a sua configuração do {% data variables.product.prodname_pages %} e os status das suas criações. Informações sobre o site e as criações só podem ser acessadas pelos proprietários autenticados{% ifversion not ghae %}, mesmo que os sites sejam públicos{% endif %}. For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)." Nos pontos de extremidade da API de {% data variables.product.prodname_pages %} com uma chave de `status` na sua resposta, o valor pode ser: * `null`: O site ainda não foi criado. @@ -265,10 +295,10 @@ Se você está desenvolvendo um aplicativo GitHub e deseja fornecer informaçõe {% if operation.subcategory == 'statuses' %}{% include rest_operation %}{% endif %} {% endfor %} -{% if currentVersion == "free-pro-team@latest" %} +{% ifversion fpt %} ## Tráfego -Para repositórios aos quais você tem acesso de push, a API de tráfego fornece acesso às informações fornecidas no seu gráfico de repositório. Para obter mais informações, consulte "Visualizar tráfego para um repositório. " +Para repositórios aos quais você tem acesso de push, a API de tráfego fornece acesso às informações fornecidas no seu gráfico de repositório. For more information, see "Viewing traffic to a repository." {% for operation in currentRestOperations %} {% if operation.subcategory == 'traffic' %}{% include rest_operation %}{% endif %} @@ -277,10 +307,12 @@ Para repositórios aos quais você tem acesso de push, a API de tráfego fornece ## Webhooks -A API de Webhooks do Repositório permite que os administradores do repositório gerenciem os hooks post-receive de um repositório. Os webhooks podem ser gerenciados usando a API de HTTP do JSON ou a API de [SubHubbub](#PubSubHubbub). +Repository webhooks allow you to receive HTTP `POST` payloads whenever certain events happen in a repository. {% data reusables.webhooks.webhooks-rest-api-links %} Se você deseja configurar um único webhook para receber eventos de todos os repositórios da organização, consulte nossa documentação de API para [Webhooks de organização](/rest/reference/orgs#webhooks). +In addition to the REST API, {% data variables.product.prodname_dotcom %} can also serve as a [PubSubHubbub](#pubsubhubbub) hub for repositories. + {% for operation in currentRestOperations %} {% if operation.subcategory == 'webhooks' %}{% include rest_operation %}{% endif %} {% endfor %} @@ -309,19 +341,12 @@ O formato padrão é o que [os hooks post-receive existentes devem esperar](/pos https://github.com/{owner}/{repo}/events/push.json #### URLs de chamada de retorno -As URLs de chamada de retorno podem usar o protocolo `http://`. -{% if enterpriseServerVersions contém currentVersion e currentVersion ver_lt "enterprise-server@2.20" %}Você também pode fazer chamada de retorno `github://` para especificar um serviço do GitHub. -{% data reusables.apps.deprecating_github_services_ghe %} -{% endif %} +As URLs de chamada de retorno podem usar o protocolo `http://`. # Send updates to postbin.org http://postbin.org/123 -{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.20" %} - # Send updates to Campfire github://campfire?subdomain=github&room=Commits&token=abc123 -{% endif %} - #### Assinar O ponto de extremidade do GitHub PubSubHubbub é: `{% data variables.product.api_url_code %}/hub`. Uma solicitação bem-sucedida com o curl parece como: @@ -338,9 +363,9 @@ Solicitações do PubSubHubbub podem ser enviadas várias vezes. Se o hook já e ##### Parâmetros -| Nome | Tipo | Descrição | -| -------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `hub.mode` | `string` | **Obrigatório**. `Assine` ou `cancele a assinatura`. | -| `hub.topic` | `string` | **Obrigatório**. A URI do repositório do GitHub a ser assinada. O caminho deve estar no formato `/{owner}/{repo}/events/{event}`. | -| `hub.callback` | `string` | A URI para receber as atualizações do tópico. | -| `hub.secret` | `string` | Uma chave secreta compartilhada que gera um HMAC de SHA1 do conteúdo do texto de saída. Você pode verificar se um push veio do GitHub, comparando o texto da solicitação sem processamento com o conteúdo do cabeçalho `X-Hub-Signature`. Você pode ver [a documentação do PubSubHubbub](https://pubsubhubbub.github.io/PubSubHubbub/pubsubhubbub-core-0.4.html#authednotify) para obter mais informações. | +| Nome | Tipo | Descrição | +| -------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `hub.mode` | `string` | **Obrigatório**. `Assine` ou `cancele a assinatura`. | +| `hub.topic` | `string` | **Obrigatório**. A URI do repositório do GitHub a ser assinada. O caminho deve estar no formato `/{owner}/{repo}/events/{event}`. | +| `hub.callback` | `string` | A URI para receber as atualizações do tópico. | +| `hub.secret` | `string` | Uma chave de segredo compartilhado que gera uma assinatura de hash do conteúdo de saída do texto. Você pode verificar se um push veio do GitHub comparando o texto da solicitação sem processar com o conteúdo dos cabeçalho do {% ifversion fpt or ghes > 2.22 %}`X-Hub-Signature` ou `X-Hub-Signature-256` {% elsif ghes < 3.0 %}`X-Hub-Signature` {% elsif ghae %}cabeçalho `X-Hub-Signature-256` {% endif %}. Você pode ver [a documentação do PubSubHubbub](https://pubsubhubbub.github.io/PubSubHubbub/pubsubhubbub-core-0.4.html#authednotify) para obter mais informações. | diff --git a/translations/pt-BR/content/rest/reference/scim.md b/translations/pt-BR/content/rest/reference/scim.md index cd6b6a3190..ee3bef0459 100644 --- a/translations/pt-BR/content/rest/reference/scim.md +++ b/translations/pt-BR/content/rest/reference/scim.md @@ -16,7 +16,9 @@ A API do SCIM é usada pelos provedores de identidade (IdPs) habilitados pelo SC {% note %} -**Observação:** A API do SCIM está disponível apenas para organizações em [{% data variables.product.prodname_ghe_cloud %}](/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts) com [SSO de SAML](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) habilitado. {% data reusables.scim.enterprise-account-scim %} Para obter mais informações sobre o SCIM, consulte "[Sobre o SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)". +**Notas:** + - The SCIM API is available only to organizations on [{% data variables.product.prodname_ghe_cloud %}](/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts) with [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) enabled. {% data reusables.scim.enterprise-account-scim %} Para obter mais informações sobre o SCIM, consulte "[Sobre o SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)". + - The SCIM API cannot be used with {% data variables.product.prodname_emus %}. {% endnote %} diff --git a/translations/pt-BR/content/rest/reference/search.md b/translations/pt-BR/content/rest/reference/search.md index a8247b673b..24a4974c94 100644 --- a/translations/pt-BR/content/rest/reference/search.md +++ b/translations/pt-BR/content/rest/reference/search.md @@ -50,7 +50,7 @@ GitHub Octocat in:readme user:defunkt const queryString = 'q=' + encodeURIComponent('GitHub Octocat in:readme user:defunkt'); ``` -Veja "[Pesquisar no GitHub](/articles/searching-on-github/)" para obter uma lista completa de qualificadores disponíveis, seu formato e um exemplo de como usá-los. Para obter informações sobre como usar operadores para corresponder a quantidades e datas específicas ou para excluir resultados, consulte "[Entender a sintaxe de pesquisa](/articles/understanding-the-search-syntax/)". +Veja "[Pesquisar no GitHub](/articles/searching-on-github/)" para obter uma lista completa de qualificadores disponíveis, seu formato e um exemplo de como usá-los. For information about how to use operators to match specific quantities, dates, or to exclude results, see "[Understanding the search syntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax/)." ### Limitações no tamanho da consulta diff --git a/translations/pt-BR/content/rest/reference/teams.md b/translations/pt-BR/content/rest/reference/teams.md index 5784bd1553..92cd7a5ea0 100644 --- a/translations/pt-BR/content/rest/reference/teams.md +++ b/translations/pt-BR/content/rest/reference/teams.md @@ -58,6 +58,12 @@ A API de Sincronização da Equipe permite que você gerencie as conexões entre Você pode gerenciar os integrantes da equipe do GitHub através do seu IdP com a sincronização de equipe. A sincronização de equipe deve estar habilitada para usar a API de sincronização de equipe. Para obter mais informações, consulte "Sincronizar equipes entre seu provedor de identidade e o GitHub". +{% note %} + +**Note:** The Team Synchronization API cannot be used with {% data variables.product.prodname_emus %}. + +{% endnote %} + {% for operation in currentRestOperations %} {% if operation.subcategory == 'team-sync' %}{% include rest_operation %}{% endif %} {% endfor %} diff --git a/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md b/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md new file mode 100644 index 0000000000..0b8e5c96f4 --- /dev/null +++ b/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md @@ -0,0 +1,90 @@ +--- +title: Sobre a pesquisa no GitHub +intro: 'Use nossas potentes ferramentas de pesquisa para encontrar o que está procurando entre os muitos repositórios, usuários e linhas de código no {% data variables.product.product_name %}.' +redirect_from: + - /articles/using-the-command-bar/ + - /articles/github-search-basics/ + - /articles/search-basics/ + - /articles/searching-github/ + - /articles/advanced-search/ + - /articles/about-searching-on-github + - /github/searching-for-information-on-github/about-searching-on-github + - /github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +{% data reusables.search.you-can-search-globally %} + +- Para pesquisar globalmente em todo o {% data variables.product.product_name %}, digite o que está procurando no campo de pesquisa que fica na parte superior de qualquer página e escolha "All {% data variables.product.prodname_dotcom %}" (Em todo o GitHub) no menu suspenso da pesquisa. +- Para pesquisar em uma organização ou um repositório específico, navegue até a página da organização ou do repositório, digite o que está procurando no campo de pesquisa que fica na parte superior da página e pressione **Enter**. + +{% note %} + +**Notas:** + +{% ifversion fpt or ghes %} +- {% data reusables.search.required_login %}{% endif %} +- Os sites do {% data variables.product.prodname_pages %} não são pesquisáveis no {% data variables.product.product_name %}. No entanto, você pode pesquisar o conteúdo da fonte, se ele existir no branch padrão de um repositório, usando a pesquisa de código. Para obter mais informações, consulte "[Pesquisar código](/search-github/searching-on-github/searching-code)". Para obter mais informações sobre o {% data variables.product.prodname_pages %}, consulte "[O que é o GitHub Pages?](/articles/what-is-github-pages/)" +- Atualmente, a nossa pesquisa não é compatível com correspondência exata. +- Sempre que você estiver pesquisando em arquivos de código, serão retornados apenas os dois primeiros resultados de cada arquivo. + +{% endnote %} + +Após a realização de uma pesquisa no {% data variables.product.product_name %}, é possível ordenar os resultados ou refiná-los ainda mais clicando em uma das linguagens na barra lateral. Para obter mais informações, consulte "[Ordenar os resultados da pesquisa](/search-github/getting-started-with-searching-on-github/sorting-search-results)". + +A pesquisa do {% data variables.product.product_name %} usa um cluster do ElasticSearch para indexar projetos toda vez que uma alteração é enviada por push ao {% data variables.product.product_name %}. Problemas e pull requests são indexados quando são criados ou modificados. + +## Tipos de pesquisa no {% data variables.product.prodname_dotcom %} + +Você pode pesquisar as seguintes informações em todos os repositórios que você pode acessar em {% data variables.product.product_location %}. + +- [Repositórios](/search-github/searching-on-github/searching-for-repositories) +- [Tópicos](/search-github/searching-on-github/searching-topics) +- [Problemas e pull requests](/search-github/searching-on-github/searching-issues-and-pull-requests){% ifversion fpt %} +- [Discussões](/search-github/searching-on-github/searching-discussions){% endif %} +- [Código](/search-github/searching-on-github/searching-code) +- [Commits](/search-github/searching-on-github/searching-commits) +- [Usuários](/search-github/searching-on-github/searching-users) +- [Pacotes](/search-github/searching-on-github/searching-for-packages) +- [Wikis](/search-github/searching-on-github/searching-wikis) + +## Pesquisar usando uma interface visual + +Como alternativa, é possível pesquisar o {% data variables.product.product_name %} usando a {% data variables.search.search_page_url %} ou a {% data variables.search.advanced_url %}. + +A {% data variables.search.advanced_url %} fornece uma interface visual para construção de consultas de pesquisa. Você pode filtrar as pesquisas por diversos fatores, como o número de estrelas ou o número de bifurcações que um repositório tem. À medida que você preenche os campos de pesquisa avançada, sua consulta é automaticamente construída na barra de pesquisa superior. + +![Pesquisa avançada](/assets/images/help/search/advanced_search_demo.gif) + +{% ifversion fpt or ghes or ghae-next %} + +## Searching repositories on {% data variables.product.prodname_dotcom_the_website %} from your private enterprise environment + +If you use {% ifversion fpt %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae-next %} or {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} and you're a member of a {% data variables.product.prodname_dotcom_the_website %} organization using {% data variables.product.prodname_ghe_cloud %}, an enterprise owner for your {% data variables.product.prodname_enterprise %} environment can enable {% data variables.product.prodname_github_connect %} so that you can search across both environments at the same time{% ifversion ghes or ghae %} from {% data variables.product.product_name %}{% endif %}. For more information, see the following. + +{% ifversion fpt or ghes %} +- "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/{% ifversion ghes %}{{ currentVersion }}{% else %}github-enterprise@latest{% endif %}/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_server %} documentation{% endif %}{% ifversion ghae-next %} +- "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/github-ae@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_managed %} documentation +{% endif %} + +{% ifversion ghes or ghae-next %} + +Para definir o escopo da pesquisa por ambiente, você pode usar uma opção de filtro na {% data variables.search.advanced_url %} ou pode usar o prefixo de pesquisa `environment:`. Para pesquisar apenas por conteúdo no {% data variables.product.product_name %}, use a sintaxe de pesquisa `environment:local`. Para pesquisar apenas por conteúdo no {% data variables.product.prodname_dotcom_the_website %}, use `environment:github`. + +Your enterprise owner on {% data variables.product.product_name %} can enable {% data variables.product.prodname_unified_search %} for all public repositories, all private repositories, or only certain private repositories in the connected {% data variables.product.prodname_ghe_cloud %} organization. + +When you search from {% data variables.product.product_name %}, you can only search in the private repositories that you have access to in the connected {% data variables.product.prodname_dotcom_the_website %} organization. Enterprise owners for {% data variables.product.product_name %} and organization owners on {% data variables.product.prodname_dotcom_the_website %} cannot search private repositories owned by your account on {% data variables.product.prodname_dotcom_the_website %}. To search the applicable private repositories, you must enable private repository search for your personal accounts on {% data variables.product.product_name %}. For more information, see "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment)." + +{% endif %} + +{% endif %} + +## Leia mais + +- "[Entender a sintaxe de pesquisa](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)" +- "[Pesquisar no GitHub](/articles/searching-on-github)" diff --git a/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md b/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md new file mode 100644 index 0000000000..cb4c99853d --- /dev/null +++ b/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md @@ -0,0 +1,54 @@ +--- +title: Enabling GitHub.com repository search from your private enterprise environment +shortTitle: Search GitHub.com from enterprise +intro: 'You can connect your personal accounts on {% data variables.product.prodname_dotcom_the_website %} and your private {% data variables.product.prodname_enterprise %} environment to search for content in certain {% data variables.product.prodname_dotcom_the_website %} repositories{% ifversion fpt %} from your private environment{% else %} from {% data variables.product.product_name %}{% endif %}.' +redirect_from: + - /articles/enabling-private-githubcom-repository-search-in-your-github-enterprise-account/ + - /articles/enabling-private-github-com-repository-search-in-your-github-enterprise-server-account/ + - /articles/enabling-private-githubcom-repository-search-in-your-github-enterprise-server-account/ + - /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 +versions: + fpt: '*' + ghes: '*' + ghae: next +topics: + - GitHub search +--- + +## About search for {% data variables.product.prodname_dotcom_the_website %} repositories from {% ifversion fpt %}your private enterprise environment{% else %}{% data variables.product.product_name %}{% endif %} + +You can search for designated private repositories on {% data variables.product.prodname_ghe_cloud %} from {% ifversion fpt %}your private {% data variables.product.prodname_enterprise %} environment{% else %}{% data variables.product.product_location %}{% ifversion ghae %} on {% data variables.product.prodname_ghe_managed %}{% endif %}{% endif %}. {% ifversion fpt %}For example, if you use {% data variables.product.prodname_ghe_server %}, you can search for private repositories from your enterprise from {% data variables.product.prodname_ghe_cloud %} in the web interface for {% data variables.product.prodname_ghe_server %}.{% endif %} + +## Pré-requisitos + +- An enterprise owner for {% ifversion fpt %}your private {% data variables.product.prodname_enterprise %} environment{% else %}{% data variables.product.product_name %}{% endif %} must enable {% data variables.product.prodname_github_connect %} and {% data variables.product.prodname_unified_search %} for private repositories. For more information, see the following.{% ifversion fpt or ghes %} + - "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/{% ifversion ghes %}{{ currentVersion }}{% else %}github-enterprise@latest{% endif %}/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_server %} documentation{% endif %}{% ifversion ghae-next %} + - "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/github-ae@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_managed %} documentation +{% endif %} + +- You must already have access to the private repositories and connect your account {% ifversion fpt %}in your private {% data variables.product.prodname_enterprise %} environment{% else %}on {% data variables.product.product_name %}{% endif %} with your account on {% data variables.product.prodname_dotcom_the_website %}. For more information about the repositories you can search, see "[About searching on GitHub](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github#searching-repositories-on-githubcom-from-your-private-enterprise-environment)." + +## Enabling GitHub.com repository search from {% ifversion fpt %}your private {% data variables.product.prodname_enterprise %} environment{% else %}{% data variables.product.product_name %}{% endif %} + +{% ifversion fpt %} + +For more information, see the following. + +| Your enterprise environment | Mais informações | +|:--------------------------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| {% data variables.product.prodname_ghe_server %} | "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/enterprise-server@latest/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-enterprise-server)" |{% ifversion ghae-next %} +| +| {% data variables.product.prodname_ghe_managed %} | "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/github-ae@latest//search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-ae)" +{% endif %} + +{% elsif ghes or ghae %} + +1. Sign into {% data variables.product.product_name %} and {% data variables.product.prodname_dotcom_the_website %}. +1. On {% data variables.product.product_name %}, in the upper-right corner of any page, click your profile photo, then click **Settings**. ![Ícone Settings (Configurações) na barra de usuário](/assets/images/help/settings/userbar-account-settings.png) +{% data reusables.github-connect.github-connect-tab-user-settings %} +{% data reusables.github-connect.connect-dotcom-and-enterprise %} +{% data reusables.github-connect.connect-dotcom-and-enterprise %} + +{% endif %} diff --git a/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/index.md b/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/index.md new file mode 100644 index 0000000000..606842d7e9 --- /dev/null +++ b/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/index.md @@ -0,0 +1,21 @@ +--- +title: Introdução à pesquisa no GitHub +intro: 'You can use a wide range of syntax to search {% data variables.product.product_name %}. You can adjust the scope of your search, build and troubleshoot queries, and sort search results with qualifiers.' +redirect_from: + - /articles/getting-started-with-searching-on-github + - /github/searching-for-information-on-github/getting-started-with-searching-on-github +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +children: + - /about-searching-on-github + - /understanding-the-search-syntax + - /troubleshooting-search-queries + - /sorting-search-results + - /enabling-githubcom-repository-search-from-your-private-enterprise-environment +shortTitle: Iniciar com a pesquisa no GitHub +--- + diff --git a/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md b/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md new file mode 100644 index 0000000000..37fd39d993 --- /dev/null +++ b/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md @@ -0,0 +1,75 @@ +--- +title: Ordenar os resultados da pesquisa +intro: 'Você pode ordenar os resultados da [pesquisa do {% data variables.product.product_name %}](/articles/searching-on-github) usando o menu Sort (Ordenar) ou adicionando um qualificador "sort" na consulta.' +redirect_from: + - /articles/sorting-search-results + - /github/searching-for-information-on-github/sorting-search-results + - /github/searching-for-information-on-github/getting-started-with-searching-on-github/sorting-search-results +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +Use o menu Sort (Ordenar) para ordenar os resultados por relevância, número de estrelas, número de bifurcações e data da atualização dos itens. + + ![Menu com opções para ordenar os resultados da pesquisa](/assets/images/help/search/repo-search-sort.png) + +Para ordenar por interações, reações, data de criação, data do committer e data de atualização dos itens, adicione um qualificador `sort` na consulta de pesquisa. + +## Ordenar por interações + +O qualificador `sort:interactions` ordena pelo maior número combinado de reações e comentários. + +| Qualifier | Exemplo | +| ----------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sort:interactions` ou `sort:interactions-desc` | [**org:github sort:interactions**](https://github.com/search?q=org%3Agithub+sort%3Ainteractions&type=Issues) identifica os problemas nos repositórios do {% data variables.product.product_name %} ordenados pelo maior número combinado de reações e comentários. | +| `sort:interactions-asc` | [**org:github sort:interactions-asc**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Ainteractions-asc&type=Issues) identifica os problemas nos repositórios do {% data variables.product.product_name %} ordenados pelo menor número combinado de reações e comentários. | + +## Ordenar por reações + +O qualificador `sort:reactions` ordena pelo número ou tipo de reações. + +| Qualifier | Exemplo | +| ----------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sort:reactions` ou `sort:reactions-desc` | [**org:github sort:reactions**](https://github.com/search?q=org%3Agithub+sort%3Areactions&type=Issues) identifica os problemas nos repositórios do {% data variables.product.product_name %} ordenados pelo maior número de reações. | +| `sort:reactions-asc` | [**org:github sort:reactions-asc**](https://github.com/search?q=org%3Agithub+sort%3Areactions-asc&type=Issues) identifica os problemas nos repositórios do {% data variables.product.product_name %} ordenados pelo número crescente de reações (do menor para o maior). | +| sort:reactions-reaction | [**org:github sort:reactions-+1**](https://github.com/search?q=org%3Agithub+sort%3Areactions-%2B1&type=Issues) identifica os problemas nos repositórios do {% data variables.product.product_name %} ordenados pelo maior número de reações de curtida (:+1:). | +| | [**org:github sort:reactions--1**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Areactions--1&type=Issues) identifica os problemas em repositórios do {% data variables.product.product_name %} ordenados pelo maior número de reações de não curti (:-1:). | +| | [**org:github sort:reactions-smile**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Areactions-smile&type=Issues) identifica os problemas nos repositórios do {% data variables.product.product_name %} ordenados pelo maior número de reações de risada (:smile:). | +| | [**org:github sort:reactions-tada**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Areactions-tada&type=Issues) identifica os problemas nos repositórios do {% data variables.product.product_name %} ordenados pelo maior número de reações de "viva" (:tada:). | +| | [**org:github sort:reactions-heart**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Areactions-heart&type=Issues) identifica os problemas nos repositórios do {% data variables.product.product_name %} ordenados pelo maior número de reações de "amei" (:heart:). | + +## Ordenar por data de criação + +O qualificador `sort:author-date` ordena de forma crescente ou decrescente por data de criação. + +| Qualifier | Exemplo | +| --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sort:author-date` ou `sort:author-date-desc` | [**feature org:github sort:author-date**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Aauthor-date&type=Commits) identifica os commits que contêm a palavra "feature" nos repositórios do {% data variables.product.product_name %} ordenados de forma decrescente por data de criação. | +| `sort:author-date-asc` | [**feature org:github sort:author-date-asc**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Aauthor-date-asc&type=Commits) identifica os commits que contêm a palavra "feature" nos repositórios do {% data variables.product.product_name %} ordenados de forma crescente por data de criação. | + +## Ordenar por data do committer + +O qualificador `sort:committer-date` ordena de forma crescente ou decrescente por data do committer. + +| Qualifier | Exemplo | +| --------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sort:committer-date` ou `sort:committer-date-desc` | [**feature org:github sort:committer-date**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Acommitter-date&type=Commits) identifica os commits que contêm a palavra "feature" nos repositórios do {% data variables.product.product_name %} ordenados de forma decrescente por data do committer. | +| `sort:committer-date-asc` | [**feature org:github sort:committer-date-asc**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Acommitter-date-asc&type=Commits) identifica os commits que contêm a palavra "feature" nos repositórios do {% data variables.product.product_name %} ordenados de forma crescente por data do committer. | + +## Ordenar por data da atualização + +O qualificador `sort:updated` ordena pela data de atualização dos itens. + +| Qualifier | Exemplo | +| ------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sort:updated` ou `sort:updated-desc` | [**feature sort:updated**](https://github.com/search?utf8=%E2%9C%93&q=feature+sort%3Aupdated&type=Repositories) identifica os repositórios que contêm a palavra "feature" ordenados pela data mais recente de atualização. | +| `sort:updated-asc` | [**feature sort:updated-asc**](https://github.com/search?utf8=%E2%9C%93&q=feature+sort%3Aupdated-asc&type=Repositories) identifica os repositórios que contêm a palavra "feature" ordenados pela data mais antiga de atualização. | + +## Leia mais + +- "[About searching on {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)" +- "[Filtrando e pesquisando problemas e pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)" diff --git a/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/troubleshooting-search-queries.md b/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/troubleshooting-search-queries.md new file mode 100644 index 0000000000..610088b41c --- /dev/null +++ b/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/troubleshooting-search-queries.md @@ -0,0 +1,34 @@ +--- +title: Solucionar problemas de consultas de pesquisa +intro: 'Se você encontrar resultados inesperados ao pesquisar no {% data variables.product.product_name %}, poderá solucionar os problemas analisando problemas comuns e limitações.' +redirect_from: + - /articles/troubleshooting-search-queries + - /github/searching-for-information-on-github/troubleshooting-search-queries + - /github/searching-for-information-on-github/getting-started-with-searching-on-github/troubleshooting-search-queries +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +shortTitle: Solucionar problemas de consultas de pesquisa +--- + +## Possíveis tempos limite + +Algumas consultas têm uma computação dispendiosa para a nossa infraestrutura de pesquisa executar. Para manter a pesquisa rápida para todos, limitamos o tempo de execução das consultas individuais. Nas raras situações em que uma consulta excede o tempo limite, a pesquisa retorna todas as correspondências encontradas antes do tempo limite e informa a ocorrência dele. + +Atingir um tempo limite não significa necessariamente que os resultados da pesquisa estão incompletos. Significa apenas que a consulta foi interrompida antes que ela pesquisasse todos os dados possíveis. + +## Limitações no tamanho da consulta + +Há alguns limites no tamanho das consultas ao pesquisar no {% data variables.product.product_name %}: + +* Não são aceitas consultas com mais de 256 caracteres +* Não é possível construir uma consulta usando mais de cinco operadores `AND`, `OR` ou `NOT` + +Determinados tipos de pesquisa, como pesquisa de código, podem ter limitações adicionais. Consulte a documentação desses tipos de pesquisa para obter mais informações. + +## Leia mais + +- "[Sobre a pesquisa no GitHub](/search-github/getting-started-with-searching-on-github/about-searching-on-github)" 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 new file mode 100644 index 0000000000..3607532692 --- /dev/null +++ b/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md @@ -0,0 +1,100 @@ +--- +title: Entender a sintaxe de pesquisa +intro: 'Durante a pesquisa no {% data variables.product.product_name %}, é possível criar consultas que correspondam a palavras e números específicos.' +redirect_from: + - /articles/search-syntax/ + - /articles/understanding-the-search-syntax + - /github/searching-for-information-on-github/understanding-the-search-syntax + - /github/searching-for-information-on-github/getting-started-with-searching-on-github/understanding-the-search-syntax +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +shortTitle: Entender a sintaxe de pesquisa +--- + +## Consultar por valores maiores ou menores que outro valor + +Você pode usar `>`, `>=`, `<` e `<=` para pesquisar valores que sejam maiores, maiores ou iguais, menores e menores ou iguais a outro valor. + +| Consulta | Exemplo | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| >n | **[cats stars:>1000](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%3E1000&type=Repositories)** corresponde a repositórios com a palavra "cats" com mais de 1000 estrelas. | +| >=n | **[cats topics:>=5](https://github.com/search?utf8=%E2%9C%93&q=cats+topics%3A%3E%3D5&type=Repositories)** corresponde a repositórios com a palavra "cats" com 5 ou mais tópicos. | +| <n | **[cats size:<10000](https://github.com/search?utf8=%E2%9C%93&q=cats+size%3A%3C10000&type=Code)** corresponde ao código com a palavra "cats" nos arquivos com tamanho inferior a 10 KB. | +| <=n | **[cats stars:<=50](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%3C%3D50&type=Repositories)** corresponde a repositórios com a palavra "cats" com 50 estrelas ou menos. | + +Você também pode usar [consultas de intervalo](#query-for-values-between-a-range) para pesquisar valores que são maiores ou iguais ou menores ou iguais a outro valor. + +| Consulta | Exemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| n..* | **[cats stars:10..*](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A10..*&type=Repositories)** é equivalente a `stars:>=10` e corresponde a repositórios com a palavra "cats" que têm até 10 estrelas. | +| *..n | **[cats stars:*..10](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%22*..10%22&type=Repositories)** é equivalente a `stars:<=10` e corresponde a repositórios com a palavra "cats" que têm até 10 estrelas. | + +## Consultar por valores dentro de um intervalo + +Você pode usar a sintaxe de intervalo n..n para pesquisar valores dentro de um intervalo, em que o primeiro número _n_ é o valor mais baixo e o segundo é o valor mais alto. + +| Consulta | Exemplo | +| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| n..n | **[cats stars:10..50](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A10..50&type=Repositories)** corresponde a repositórios com a palavra "cats" que têm entre 10 e 50 estrelas. | + +## Consultar por datas + +Você pode usar `>`, `>=`, `<`, `<=` e [consultas de intervalo](#query-for-values-between-a-range) para pesquisar por datas anteriores ou posteriores a outra data ou que se enquadram em um intervalo de datas. {% data reusables.time_date.date_format %} + +| Consulta | Exemplo | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| >YYYY-MM-DD | **[cats created:>2016-04-29](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3E2016-04-29&type=Issues)** corresponde a problemas com a palavra "cats" que foram criados após 29 de abril de 2016. | +| >=YYYY-MM-DD | **[cats created:>=2017-04-01](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3E%3D2017-04-01&type=Issues)** corresponde a problemas com a palavra "cats" que foram criados a partir de 1 de abril de 2017. | +| <YYYY-MM-DD | **[cats pushed:<2012-07-05](https://github.com/search?q=cats+pushed%3A%3C2012-07-05&type=Code&utf8=%E2%9C%93)** corresponde ao código com a palavra "cats" em repositórios que foram carregados até 5 de julho de 2012. | +| <=YYYY-MM-DD | **[cats created:<=2012-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3C%3D2012-07-04&type=Issues)** corresponde a problemas com a palavra "cats" que foram criados em ou antes de 4 de julho de 2012. | +| YYYY-MM-DD..YYYY-MM-DD | **[cats pushed:2016-04-30..2016-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+pushed%3A2016-04-30..2016-07-04&type=Repositories)** corresponde a repositórios com a palavra "cats" nos quais foi feito push entre o final de abril e julho de 2016. | +| YYYY-MM-DD..* | **[cats created:2012-04-30..*](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2012-04-30..*&type=Issues)** corresponde a problemas criados após 30 de abril de 2012 contendo a palavra "cats". | +| *..YYYY-MM-DD | **[cats created:*..2012-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A*..2012-07-04&type=Issues)** corresponde a problemas criados antes de 4 de julho de 2012 contendo a palavra "cats". | + +{% data reusables.time_date.time_format %} + +| Consulta | Exemplo | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| YYYY-MM-DDTHH:MM:SS+00:00 | **[cats created:2017-01-01T01:00:00+07:00..2017-03-01T15:30:15+07:00](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2017-01-01T01%3A00%3A00%2B07%3A00..2017-03-01T15%3A30%3A15%2B07%3A00&type=Issues)** corresponde a problemas criados entre 01 de janeiro de 2017 à 1h, com uma diferença de fuso horário de `07:00` em relação ao UTC, e 01 de março de 2017 às 15h, com uma diferença de fuso horário de `07:00` em relação ao UTC. com um ajuste de UTC de `07:00` e 1 de março de 2017 às 15h. com um ajuste de UTC de `07:00`. | +| YYYY-MM-DDTHH:MM:SSZ | **[cats created:2016-03-21T14:11:00Z..2016-04-07T20:45:00Z](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2016-03-21T14%3A11%3A00Z..2016-04-07T20%3A45%3A00Z&type=Issues)** corresponde a problemas criados entre 21 de março de 2016 às 14h11 e 07 de abril de 2106 às 20h45. | + +## Excluir determinados resultados + +Usando a sintaxe `NOT`, é possível excluir resultados contendo uma determinada palavra. O operador `NOT` só pode ser usado para palavras-chave de string. Ele não funciona com numerais ou datas. + +| Consulta | Exemplo | +| -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `NOT` | **[hello NOT world](https://github.com/search?q=hello+NOT+world&type=Repositories)** corresponde a repositórios que têm a palavra "hello", mas não a palavra "world". | + +Outra maneira de restringir os resultados da pesquisa é excluir determinados subconjuntos. Adicione um prefixo a qualquer qualificador de pesquisa com um `-` para excluir todos os resultados correspondentes a esse qualificador. + +| Consulta | Exemplo | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| -QUALIFIER | **[cats stars:>10 -language:javascript](https://github.com/search?q=cats+stars%3A>10+-language%3Ajavascript&type=Repositories)** corresponde a repositórios com a palavra "cats" com mais de 10 estrelas mas não estão escritos em JavaScript. | +| | **[mentions:defunkt -org:github](https://github.com/search?utf8=%E2%9C%93&q=mentions%3Adefunkt+-org%3Agithub&type=Issues)** corresponde a problemas mencionando @defunkt que não estão em repositórios na organização do GitHub. | + +## Usar aspas para consultas com espaço em branco + +Se a consulta de pesquisa contém espaço em branco, é preciso colocá-lo entre aspas. Por exemplo: + +* [cats NOT "hello world"](https://github.com/search?utf8=✓&q=cats+NOT+"hello+world"&type=Repositories) corresponde a repositórios com a palavra "cats", mas não as palavras "hello world". +* [build label:"bug fix"](https://github.com/search?utf8=%E2%9C%93&q=build+label%3A%22bug+fix%22&type=Issues) corresponde a problemas com a palavra "build" que têm a etiqueta "bug fix". + +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 %} +## 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. + +| Consulta | Exemplo | +| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `QUALIFIER:USERNAME` | [`author:nat`](https://github.com/search?q=author%3Anat&type=Commits) corresponde a commits criados por @nat | +| `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/index.md b/translations/pt-BR/content/search-github/index.md new file mode 100644 index 0000000000..8e0f1ba48e --- /dev/null +++ b/translations/pt-BR/content/search-github/index.md @@ -0,0 +1,20 @@ +--- +title: Pesquisar informações no GitHub +intro: Use diferentes tipos de pesquisa para encontrar as informações desejadas. +redirect_from: + - /categories/78/articles/ + - /categories/search/ + - /categories/searching-for-information-on-github + - /github/searching-for-information-on-github +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +children: + - /getting-started-with-searching-on-github + - /searching-on-github +shortTitle: Pesquisar no GitHub +--- + diff --git a/translations/pt-BR/content/search-github/searching-on-github/finding-files-on-github.md b/translations/pt-BR/content/search-github/searching-on-github/finding-files-on-github.md new file mode 100644 index 0000000000..91d158eff7 --- /dev/null +++ b/translations/pt-BR/content/search-github/searching-on-github/finding-files-on-github.md @@ -0,0 +1,32 @@ +--- +title: Localizar arquivos no GitHub +intro: 'É possível localizar um arquivo em um repositório usando o localizador de arquivos. To search for a file in multiple repositories on {% data variables.product.product_name %}, use the [`filename` code search qualifier](/search-github/searching-on-github/searching-code#search-by-filename).' +redirect_from: + - /articles/finding-files-on-github + - /github/searching-for-information-on-github/finding-files-on-github + - /github/searching-for-information-on-github/searching-on-github/finding-files-on-github +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +{% tip %} + +**Dicas:** + +- Os resultados do localizador de arquivos excluem alguns diretórios, como `build`, `log`, `tmp` e `vendor`. Para pesquisar arquivos dentro desses diretórios, use o código qualificador da pesquisa [`filename` (nome do arquivo)](/search-github/searching-on-github/searching-code#search-by-filename). +- É possível também abrir o file finder (localizador de arquivos) digitando `t` no teclado. Para obter mais informações, consulte "[Atalhos de teclado](/articles/keyboard-shortcuts)". + +{% endtip %} + +{% data reusables.repositories.navigate-to-repo %} +2. Acima da lista de arquivos, clique em **Ir para o arquivo**. ![Botão Find file (Localizar arquivo)](/assets/images/help/search/find-file-button.png) +3. No campo de pesquisa, digite o nome do arquivo que está procurando. ![Campo de pesquisa Find file (Localizar arquivo)](/assets/images/help/search/find-file-search-field.png) +4. Na lista de resultados, clique no arquivo que você queria encontrar. + +## Leia mais + +- "[Sobre a pesquisa no GitHub](/search-github/getting-started-with-searching-on-github/about-searching-on-github)" diff --git a/translations/pt-BR/content/search-github/searching-on-github/index.md b/translations/pt-BR/content/search-github/searching-on-github/index.md new file mode 100644 index 0000000000..0e728af980 --- /dev/null +++ b/translations/pt-BR/content/search-github/searching-on-github/index.md @@ -0,0 +1,27 @@ +--- +title: Pesquisar no GitHub +intro: You can use qualifiers to narrow your search and focus on specific categories of information. +redirect_from: + - /articles/searching-on-github + - /github/searching-for-information-on-github/searching-on-github +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +children: + - /finding-files-on-github + - /searching-for-repositories + - /searching-topics + - /searching-code + - /searching-commits + - /searching-issues-and-pull-requests + - /searching-discussions + - /searching-github-marketplace + - /searching-users + - /searching-for-packages + - /searching-wikis + - /searching-in-forks +--- + diff --git a/translations/pt-BR/content/search-github/searching-on-github/searching-code.md b/translations/pt-BR/content/search-github/searching-on-github/searching-code.md new file mode 100644 index 0000000000..42cd928e84 --- /dev/null +++ b/translations/pt-BR/content/search-github/searching-on-github/searching-code.md @@ -0,0 +1,112 @@ +--- +title: Pesquisar códigos +intro: 'Você pode pesquisar códigos no {% data variables.product.product_name %} e limitar os resultados usando qualquer combinação dos qualificadores da pesquisa de código.' +redirect_from: + - /articles/searching-code + - /github/searching-for-information-on-github/searching-files-in-a-repository-for-exact-matches + - /github/searching-for-information-on-github/searching-code-for-exact-matches + - /github/searching-for-information-on-github/searching-code + - /github/searching-for-information-on-github/searching-on-github/searching-code +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +{% data reusables.search.you-can-search-globally %} Para obter mais informações, consulte "[Sobre pesquisar no GitHub](/search-github/getting-started-with-searching-on-github/about-searching-on-github)." + +Você pode pesquisar códigos usando somente estes qualificadores de pesquisa de código. Qualificadores de pesquisa específicos para repositórios, usuários ou commits não funcionarão com a pesquisa de códigos. + +{% data reusables.search.syntax_tips %} + +## Considerações sobre pesquisa de códigos + +Devido à complexidade da pesquisa de códigos, a execução das pesquisas apresenta algumas restrições: + +{% ifversion fpt or ghes %} +- {% data reusables.search.required_login %}{% endif %} +- O código em [bifurcações](/articles/about-forks) só poderá ser pesquisado se a bifurcação tiver mais estrelas do que o repositório principal. Bifurcações com menos estrelas do que o repositório principal **não** são indexadas para pesquisa de códigos. Para incluir bifurcações com mais estrelas que o repositório principal delas nos resultados da pesquisa, você precisará adicionar `fork:true` ou `fork:only` à sua consulta. Para obter mais informações, consulte "[Pesquisar em bifurcações](/search-github/searching-on-github/searching-in-forks)". +- Apenas o _branch-padrão_ é indexado para a busca de código.{% ifversion fpt %} +- Somente arquivos com menos de 384 KB são pesquisados.{% else %}* Somente arquivos com menos de 5 MB são pesquisados. +- Somente os primeiros 500 KB de cada arquivo são pesquisados.{% endif %} +- Apenas repositórios com menos de 500.000 arquivos são pesquisáveis.{% ifversion fpt %} +- Apenas repositórios que tiveram atividade ou apareceram nos resultados de pesquisa do último ano são pesquisáveis.{% endif %} +- Com exceção das pesquisas por [`filename`](#search-by-filename), é necessário incluir pelo menos um termo da pesquisa ao pesquisar o código-fonte. Por exemplo, pesquisar [`language:javascript`](https://github.com/search?utf8=%E2%9C%93&q=language%3Ajavascript&type=Code&ref=searchresults) não é válido, enquanto pesquisar [`amazing language:javascript`](https://github.com/search?utf8=%E2%9C%93&q=amazing+language%3Ajavascript&type=Code&ref=searchresults) é. +- Os resultados da pesquisa exibem no máximo dois fragmentos do mesmo arquivo, mas o arquivo pode ter mais resultados. +- Não é possível usar os seguintes caracteres-curinga na consulta de pesquisa: . , : ; / \ ` ' " = * ! ? # $ & + ^ | ~ < > ( ) { } [ ] @. A pesquisa simplesmente ignora esses símbolos. + +## Pesquisar pelo conteúdo ou caminho do arquivo + +Com o qualificador `in`, você pode restringir a pesquisa ao conteúdo do arquivo de código-fonte e/ou ao caminho do arquivo. Quando você omite esse qualificador, somente o conteúdo do arquivo é pesquisado. + +| Qualifier | Exemplo | +| --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `in:file` | [**octocat in:file**](https://github.com/search?q=octocat+in%3Afile&type=Code) identifica o código quando"octocat" aparece no conteúdo do arquivo. | +| `in:path` | [**octocat in:path**](https://github.com/search?q=octocat+in%3Apath&type=Code) identifica o código quando"octocat" aparece no caminho do arquivo. | +| | [**octocat in:file,path**](https://github.com/search?q=octocat+in%3Afile%2Cpath&type=Code) identifica o código quando"octocat" aparece no conteúdo ou no caminho do arquivo. | + +## Pesquisar nos repositórios de um usuário ou uma organização + +Para pesquisar códigos em todos os repositórios de um determinado usuário ou organização, você pode usar os qualificadores `user` ou `org`. Para pesquisar códigos em um repositório específico, você pode usar o qualificador `repo`. + +| Qualifier | Exemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| user:USERNAME | [**user:defunkt extension:rb**](https://github.com/search?q=user%3Agithub+extension%3Arb&type=Code) identifica o código de @defunkt que termina em .rb. | +| org:ORGNAME | [**org:github extension:js**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+extension%3Ajs&type=Code) identifica o código do GitHub que termina em .js. | +| repo:USERNAME/REPOSITORY | [**repo:mozilla/shumway extension:as**](https://github.com/search?q=repo%3Amozilla%2Fshumway+extension%3Aas&type=Code) identifica o código do projeto shumway de @mozilla que termina em .as. | + +## Pesquisar por local do arquivo + +Você pode usar o qualificador `path` para pesquisar o código-fonte que aparece em um local específico de um repositório. Use o `path:/` para pesquisar os arquivos que estão no diretório raiz de um repositório. Ou especifique o nome ou o caminho do diretório para pesquisar os arquivos presentes nesse diretório e em seus subdiretórios. + +| Qualifier | Exemplo | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| path:/ | [**octocat filename:readme path:/**](https://github.com/search?utf8=%E2%9C%93&q=octocat+filename%3Areadme+path%3A%2F&type=Code) identifica os arquivos _readme_ com a palavra "octocat" localizados no diretório raiz de um repositório. | +| path:DIRECTORY | [**form path:cgi-bin language:perl**](https://github.com/search?q=form+path%3Acgi-bin+language%3Aperl&type=Code) matches Perl files with the word "form" in the cgi-bin directory, or in any of its subdirectories. | +| path:PATH/TO/DIRECTORY | [**console path:app/public language:javascript**](https://github.com/search?q=console+path%3A%22app%2Fpublic%22+language%3Ajavascript&type=Code) matches JavaScript files with the word "console" in the app/public directory, or in any of its subdirectories (even if they reside in app/public/js/form-validators). | + +## Pesquisar por linguagem + + +Você pode pesquisar código com base na linguagem na qual ele foi escrito. O qualificador da `linguagem` pode ser o nome da linguagem ou o alias. Para obter uma lista completa de linguagens compatíveis com seus nomes e alias, consulte o repositório [github/linguist](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml). + +| Qualifier | Exemplo | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| language:LANGUAGE | [**element language:xml size:100**](https://github.com/search?q=element+language%3Axml+size%3A100&type=Code) identifica o código com a palavra "element", marcado como XML e que tem exatamente 100 bytes. | +| | [**display language:scss**](https://github.com/search?q=display+language%3Ascss&type=Code) identifica o código com a palavra "display" marcado como SCSS. | +| | [**org:mozilla language:markdown**](https://github.com/search?utf8=%E2%9C%93&q=org%3Amozilla+language%3Amarkdown&type=Code) identifica o código marcado como Markdown de todos os repositórios de @mozilla. | + +## Pesquisar por tamanho do arquivo + +Você pode usar o qualificador `size` para pesquisar o código-fonte com base no tamanho do arquivo do código. O qualificador `size` usa os [qualificadores maior que, menor que e intervalo](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax) para filtrar os resultados com base no tamanho em bytes do arquivo do código. + +| Qualifier | Exemplo | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| size:n | [**function size:>10000 language:python**](https://github.com/search?q=function+size%3A%3E10000+language%3Apython&type=Code) identifica o código com a palavra "function," escrito em Python, presente em arquivos com mais de 10 KB. | + +## Pesquisar por nome do arquivo + +O qualificador `filename` identifica os arquivos de código com um determinado nome de arquivo. Você também pode localizar um arquivo em um repositório usando o localizador de arquivos. Para obter mais informações, consulte "[Localizar arquivos no GitHub](/search-github/searching-on-github/finding-files-on-github)". + +| Qualifier | Exemplo | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| filename:FILENAME | [**filename:linguist**](https://github.com/search?utf8=%E2%9C%93&q=filename%3Alinguist&type=Code) identifica os arquivos com o nome "linguist". | +| | [**filename:.vimrc commands**](https://github.com/search?q=filename%3A.vimrc+commands&type=Code) identifica os arquivos *.vimrc* com a palavra "commands". | +| | [**filename:test_helper path:test language:ruby**](https://github.com/search?q=minitest+filename%3Atest_helper+path%3Atest+language%3Aruby&type=Code) identifica os arquivos de Ruby com nome *test_helper* no diretório *test*. | + +## Pesquisar por extensão do arquivo + +O qualificador `extension` identifica os arquivos de código com uma determinada extensão do arquivo. + +| Qualifier | Exemplo | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| extension:EXTENSION | [**form path:cgi-bin extension:pm**](https://github.com/search?q=form+path%3Acgi-bin+extension%3Apm&type=Code) identifica o código com a palavra "form" em cgi-bin, com a extensão de arquivo .pm. | +| | [**icon size:>200000 extension:css**](https://github.com/search?utf8=%E2%9C%93&q=icon+size%3A%3E200000+extension%3Acss&type=Code) corresponde a arquivos com um tamanho superior a 200 KB terminam em .css e têm a palavra "icon". | + +## Leia mais + +- "[Ordenar os resultados da pesquisa](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" +- "[Pesquisar nas bifurcações](/search-github/searching-on-github/searching-in-forks)"{% ifversion fpt %} +- "[Navegar pelo código em {% data variables.product.prodname_dotcom %}](/github/managing-files-in-a-repository/navigating-code-on-github)"{% endif %} diff --git a/translations/pt-BR/content/search-github/searching-on-github/searching-commits.md b/translations/pt-BR/content/search-github/searching-on-github/searching-commits.md new file mode 100644 index 0000000000..22b9a974fd --- /dev/null +++ b/translations/pt-BR/content/search-github/searching-on-github/searching-commits.md @@ -0,0 +1,111 @@ +--- +title: Pesquisar commits +intro: 'Você pode pesquisar commits no {% data variables.product.product_name %} e limitar os resultados usando qualquer combinação dos qualificadores de pesquisa de commits.' +redirect_from: + - /articles/searching-commits + - /github/searching-for-information-on-github/searching-commits + - /github/searching-for-information-on-github/searching-on-github/searching-commits +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +Você pode pesquisar commits globalmente no {% data variables.product.product_name %} ou pesquisar em uma organização ou um repositório específico. 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)". + +Quando você pesquisa commits, somente o [branch padrão](/articles/about-branches) de um repositório é pesquisado. + +{% data reusables.search.syntax_tips %} + +## Pesquisar em mensagens do commit + +Você pode pesquisar commits que contêm palavras específicas na mensagem. Por exemplo, [**fix typo**](https://github.com/search?q=fix+typo&type=Commits) identifica os commits que têm as palavras "fix" e "typo". + +## Pesquisar por autor ou committer + +Você pode pesquisar commits de um usuário específico com os qualificadores `author` ou `committer`. + +| Qualifier | Exemplo | +| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | +| author:USERNAME | [**author:defunkt**](https://github.com/search?q=author%3Adefunkt&type=Commits) identifica os commits de autoria de @defunkt. | +| committer:USERNAME | [**committer:defunkt**](https://github.com/search?q=committer%3Adefunkt&type=Commits) identifica os commits feitos por @defunkt. | + +Os qualificadores `author-name` e `committer-name` identifica os commits pelo nome do autor ou committer. + +| Qualifier | Exemplo | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| author-name:NAME | [**author-name:wanstrath**](https://github.com/search?q=author-name%3Awanstrath&type=Commits) identifica os commits com "wanstrath" no nome do autor. | +| committer-name:NAME | [**committer-name:wanstrath**](https://github.com/search?q=committer-name%3Awanstrath&type=Commits) identifica os commits com "wanstrath" no nome do committer. | + +Os qualificadores `author-email` e `committer-email` identificam commits pelo endereço de e-mail completo do autor ou committer. + +| Qualifier | Exemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| author-email:EMAIL | [**author-email:chris@github.com**](https://github.com/search?q=author-email%3Achris%40github.com&type=Commits) identifica os commits de autoria de chris@github.com. | +| committer-email:EMAIL | [**committer-email:chris@github.com**](https://github.com/search?q=committer-email%3Achris%40github.com&type=Commits) identifica os commits feitos por chris@github.com. | + +## Pesquisar por data de criação ou do commit + +Use os qualificadores `author-date` e `committer-date` para identificar commits criados ou feitos em um intervalo de datas específico. + +{% data reusables.search.date_gt_lt %} + +| Qualifier | Exemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| author-date:YYYY-MM-DD | [**author-date:<2016-01-01**](https://github.com/search?q=author-date%3A<2016-01-01&type=Commits) identifica os commits criados antes de 01-01-2016. | +| committer-date:YYYY-MM-DD | [**committer-date:>2016-01-01**](https://github.com/search?q=committer-date%3A>2016-01-01&type=Commits) corresponde a commits confirmados após 2016-01-01. | + +## Filtrar commits de merge + +O qualificador `merge` filtra os commits de merge. + +| Qualifier | Exemplo | +| ------------- | --------------------------------------------------------------------------------------------------------------------- | +| `merge:true` | [**merge:true**](https://github.com/search?q=merge%3Atrue&type=Commits) identifica os commits de merge. | +| `merge:false` | [**merge:false**](https://github.com/search?q=merge%3Afalse&type=Commits) identifica os commits que não são de merge. | + +## Pesquisar por hash + +O qualificador `hash` identifica os commits com o hash SHA-1 especificado. + +| Qualifier | Exemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| hash:HASH | [**hash:124a9a0ee1d8f1e15e833aff432fbb3b02632105**](https://github.com/github/gitignore/search?q=hash%3A124a9a0ee1d8f1e15e833aff432fbb3b02632105&type=Commits) identifica os commits com o hash `124a9a0ee1d8f1e15e833aff432fbb3b02632105`. | + +## Pesquisar por principal + +O qualificador `parent` identifica os commits cujo principal tem o hash SHA-1 especificado. + +| Qualifier | Exemplo | +| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| parent:HASH | [**parent:124a9a0ee1d8f1e15e833aff432fbb3b02632105**](https://github.com/github/gitignore/search?q=parent%3A124a9a0ee1d8f1e15e833aff432fbb3b02632105&type=Commits&utf8=%E2%9C%93) identifica os commits secundários com o hash `124a9a0ee1d8f1e15e833aff432fbb3b02632105`. | + +## Pesquisar por árvore + +O qualificador `tree` identifica os commits com o hash de árvore do Git SHA-1 especificado. + +| Qualifier | Exemplo | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| tree:HASH | [**tree:99ca967**](https://github.com/github/gitignore/search?q=tree%3A99ca967&type=Commits) identifica os commits que fazem referência ao hash de árvore `99ca967`. | + +## Pesquisar nos repositórios de um usuário ou uma organização + +Para pesquisar commits em todos os repositórios de um determinado usuário ou organização, use os qualificadores `user` ou `org`. Para pesquisar commits em um repositório específico, use o qualificador `repo`. + +| Qualifier | Exemplo | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**gibberish user:defunkt**](https://github.com/search?q=gibberish+user%3Adefunkt&type=Commits&utf8=%E2%9C%93) identifica as mensagens do commit com a palavra "gibberish" nos repositórios de @defunkt. | +| org:ORGNAME | [**test org:github**](https://github.com/search?utf8=%E2%9C%93&q=test+org%3Agithub&type=Commits) identifica as mensagens do commit com a palavra "test" nos repositórios de @github. | +| repo:USERNAME/REPO | [**language repo:defunkt/gibberish**](https://github.com/search?utf8=%E2%9C%93&q=language+repo%3Adefunkt%2Fgibberish&type=Commits) identifica as mensagens do commit com a palavra "language" no repositório "gibberish" de @defunkt. | + +## Filtrar por visibilidade do repositório + +O qualificador `is` corresponde a commits dos repositórios com a visibilidade especificada. Para obter mais informações, consulte "[Sobre repositórios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)". + +| Qualificador | Exemplo | ------------- | ------------- |{% ifversion fpt or ghes %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Commits) corresponde aos dos repositórios públicos.{% endif %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Commits) corresponde aos commits dos repositórios internos. | `is:private` | [**is:private**](https://github.com/search?q=is%3Aprivate&type=Commits) corresponde aos commits dos repositórios privados. + +## Leia mais + +- "[Ordenar os resultados da pesquisa](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" diff --git a/translations/pt-BR/content/search-github/searching-on-github/searching-discussions.md b/translations/pt-BR/content/search-github/searching-on-github/searching-discussions.md new file mode 100644 index 0000000000..bc4fc734db --- /dev/null +++ b/translations/pt-BR/content/search-github/searching-on-github/searching-discussions.md @@ -0,0 +1,113 @@ +--- +title: Pesquisar discussões +intro: 'Você pode pesquisar discussões em {% data variables.product.product_name %} e limitar os resultados usando os qualificadores de busca.' +versions: + fpt: '*' +topics: + - GitHub search +redirect_from: + - /github/searching-for-information-on-github/searching-discussions + - /github/searching-for-information-on-github/searching-on-github/searching-discussions +--- + +## Sobre a pesquisa de discussões + +É possível pesquisar discussões globalmente em todos os {% data variables.product.product_name %} ou pesquisar discussões dentro de uma determinada organização ou repositório. Para obter mais informações, consulte "[Sobre a pesquisa no {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/about-searching-on-github)". + +{% data reusables.search.syntax_tips %} + +## Pesquisar por título, texto ou comentários + +Com o qualificador `in`, você pode restringir sua pesquisa por discussões sobre título, texto ou comentários. Você também pode combinar os qualificadores para pesquisar uma combinação de título, texto ou comentários. Ao omitir o qualificador `in` qualificador, {% data variables.product.product_name %} irá pesquisar o título, o texto e os comentários. + +| Qualifier | Exemplo | +|:------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `in:title` | [**welcome in:title**](https://github.com/search?q=welcome+in%3Atitle&type=Discussions) corresponde discussões ao título "welcome". | +| `in:body` | [**onboard in:title,body**](https://github.com/search?q=onboard+in%3Atitle%2Cbody&type=Discussions) corresponde discussões com "onboard" no título ou texto. | +| `in:comments` | [**thanks in:comments**](https://github.com/search?q=thanks+in%3Acomment&type=Discussions) corresponde discussões com "thanks" nos comentários para a discussão. | + +## Pesquisar nos repositórios de um usuário ou uma organização + +Para pesquisar discussões em todos os repositórios pertencentes a um determinado usuário ou organização, você pode usar o qualificador `usuário` ou `org`. Para pesquisar discussões em um repositório específico, você pode usar o qualificador `repositório`. + +| Qualifier | Exemplo | +|:------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**user:octocat feedback**](https://github.com/search?q=user%3Aoctocat+feedback&type=Discussions) corresponde discussões com a palavra "feedback" dos repositórios pertencentes ao @octocat. | +| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=Discussions&utf8=%E2%9C%93) corresponde discussões em repositórios pertencentes à organização do GitHub. | +| repo:USERNAME/REPOSITORY | [**repo:nodejs/node created:<2021-01-01**](https://github.com/search?q=repo%3Anodejs%2Fnode+created%3A%3C2020-01-01&type=Discussions) corresponde discussões do projeto do tempo de execução do Node.js do @nodejs criadas antes de janeiro de 2021. | + +## Filtrar por visibilidade do repositório + +Você pode filtrar pela visibilidade do repositório que contém as discussões que usam o qualificador `is`. Para obter mais informações, consulte "[Sobre repositórios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)". + +| Qualificador | Exemplo | :- | :- |{% ifversion fpt or ghes %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Discussions) corresponde discussões em repositórios públicos.{% endif %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Discussions) corresponde discussões em repositórios internos. | `is:private` | [**is:private tiramisu**](https://github.com/search?q=is%3Aprivate+tiramisu&type=Discussions) corresponde discussões que contêm a palavra "tiramisu" em repositórios que você pode acessar. + +## Pesquisar por autor + +O qualificador do `autor` encontra discussões criadas por um determinado usuário. + +| Qualifier | Exemplo | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| author:USERNAME | [**cool author:octocat**](https://github.com/search?q=cool+author%3Aoctocat&type=Discussions) corresponde a discussões com a palavra "cool" criadas por @octocat. | +| | [**bootstrap in:body author:octocat**](https://github.com/search?q=bootstrap+in%3Abody+author%3Aoctocat&type=Discussions) corresponde a discussões criadas por @octocat que contêm a palavra "bootstrap" no texto. | + +## Pesquisar por autor do comentário + +O qualificador `commenter` encontra discussões que contêm um comentário de um usuário específico. + +| Qualifier | Exemplo | +|:------------------------- |:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| commenter:USERNAME | [**github commenter:becca org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Abecca+org%3Agithub&type=Discussions) corresponde às discussões em repositórios pertencentes ao GitHub, que contêm a palavra "github" e que têm um comentário de @becca. | + +## Procurar por um usuário envolvido em uma discussão + +Você pode usar o qualificador `envolve` para encontrar discussões que envolvam um determinado usuário. O qualificador retorna discussões que ou foram criadas por um determinado usuário, menciona o usuário, ou contém comentários feitos pelo usuário. O qualificador `involves` é um operador lógico OU entre os qualificadores `autor`, `mentions` e `commenter` para um único usuário. + +| Qualifier | Exemplo | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| involves:USERNAME | **[envolves:becca envolve:octocat](https://github.com/search?q=involves%3Abecca+involves%3Aoctocat&type=Discussions)** corresponde às discussões em que @becca ou @octocat estão envolvidos. | +| | [**NOT beta in:body involves:becca**](https://github.com/search?q=NOT+beta+in%3Abody+involves%3Abecca&type=Discussions) corresponde a discussões @becca que não contêm a palavra "beta" no texto. | + +## Pesquisar por número de comentários + +Você pode usar o qualificador `comments` com os qualificadores maior que, menor que e intervalo para pesquisar pelo número de comentários. Para obter mais informações, consulte "[Entender a sintaxe de pesquisa](/github/searching-for-information-on-github/understanding-the-search-syntax)". + +| Qualifier | Exemplo | +|:------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| comments:n | [**comments:>100**](https://github.com/search?q=comments%3A%3E100&type=Discussions) corresponde a discussões com mais de 100 comentários. | +| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Discussions) corresponde a discussões com comentários que variam de 500 a 1.000. | + +## Pesquisar por número de interações + +Você pode filtrar discussões pelo número de interações com o qualificador de `interações` com os qualificadores maior que, menor que e intervalo. A contagem das interações é o número de reações e comentários em uma discussão. Para obter mais informações, consulte "[Entender a sintaxe de pesquisa](/github/searching-for-information-on-github/understanding-the-search-syntax)". + +| Qualifier | Exemplo | +|:------------------------- |:----------------------------------------------------------------------------------------------------------------------------------------------------- | +| interactions:n | [** interactions:>2000**](https://github.com/search?q=interactions%3A%3E2000) corresponde a discussões com mais de 2.000 interações. | +| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) corresponde a discussões com interações que variam de 500 a 1.000. | + +## Pesquisar por número de reações + +Você pode filtrar discussões pelo número de reações usando o qualificador de `reações`, junto os qualificadores maior que, menor que e de intervalo. Para obter mais informações, consulte "[Entender a sintaxe de pesquisa](/github/searching-for-information-on-github/understanding-the-search-syntax)". + +| Qualifier | Exemplo | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------- | +| reactions:n | [** reactions:>1000**](https://github.com/search?q=reactions%3A%3E500) corresponde a discussões com mais de 500 reações. | +| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) corresponde a discussões com 500 a 1.000 reações. | + +## Procurar por quando uma discussão foi criada ou quando foi atualizada por último + +Você pode filtrar discussões com base no tempo de criação, ou quando a discussão foi atualizada pela última vez. Para a criação de discussões, você pode usar o qualificador `criado`; para saber quando uma discussão foi atualizada pela última vez, use o qualificador `atualizada`. + +Ambos os qualificadores tomam uma data como parâmetro. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifier | Exemplo | +|:-------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| created:YYYY-MM-DD | [**created:>2020-11-15**](https://github.com/search?q=created%3A%3E%3D2020-11-15&type=discussions) corresponde a discussões que foram criadas após 15 de novembro de 2020. | +| updated:YYYY-MM-DD | [**weird in:body updated:>=2020-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2020-12-01&type=Discussions) corresponde a discussões com a palavra "weird" no texto que foram atualizadas após dezembro de 2020. | + +## Leia mais + +- "[Ordenar os resultados da pesquisa](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" diff --git a/translations/pt-BR/content/search-github/searching-on-github/searching-for-packages.md b/translations/pt-BR/content/search-github/searching-on-github/searching-for-packages.md new file mode 100644 index 0000000000..832ef691c3 --- /dev/null +++ b/translations/pt-BR/content/search-github/searching-on-github/searching-for-packages.md @@ -0,0 +1,45 @@ +--- +title: Pesquisar pacotes +intro: 'Você pode procurar pacotes no {% data variables.product.product_name %} e limitar os resultados usando qualificadores de pesquisa.' +product: '{% data reusables.gated-features.packages %}' +permissions: Anyone can search for packages they have access to. +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +redirect_from: + - /github/searching-for-information-on-github/searching-for-packages + - /github/searching-for-information-on-github/searching-on-github/searching-for-packages +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +## Sobre a procura de pacotes + +É possível procurar pacotes globalmente em todos os {% data variables.product.product_name %} ou pesquisar pacotes dentro de uma determinada organização. Para obter mais informações, consulte "[Sobre a pesquisa no {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)". + +{% ifversion ghes %} +Você só pode procurar por pacotes em {% data variables.product.product_name %}, não {% data variables.product.prodname_dotcom_the_website %}, mesmo se {% data variables.product.prodname_github_connect %} estiver habilitado. +{% endif %} + +{% data reusables.search.syntax_tips %} + +## Procurar pacotes do usuário ou da organização + +Para encontrar pacotes que pertencem a um determinado usuário ou organização, use o `usuário` ou `org` qualificador. + +| Qualifier | Exemplo | +| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**user:codertocat**](https://github.com/search?q=user%3Acodertocat&type=RegistryPackages) corresponde pacotes que pertencem ao @codertocat | +| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=RegistryPackages) corresponde pacotes que pertencem à organização do {% data variables.product.prodname_dotcom %} + +## Filtrar por visibilidade do pacote + +Para filtrar sua pesquisa pelo status público ou privado do pacote, use o qualificador `is`. + +| Qualifier | Exemplo | +| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `is:public` | [**is:public angular**](https://github.com/search?q=is%3Apublic+angular&type=RegistryPackages) corresponde a pacotes públicos que contêm a palavra "angular" | +| `is:private` | [**is:private php**](https://github.com/search?q=is%3Aprivate+php&type=RegistryPackages) corresponde pacotes privados que contêm a palavra "php" | diff --git a/translations/pt-BR/content/search-github/searching-on-github/searching-for-repositories.md b/translations/pt-BR/content/search-github/searching-on-github/searching-for-repositories.md new file mode 100644 index 0000000000..bb21b3ad6f --- /dev/null +++ b/translations/pt-BR/content/search-github/searching-on-github/searching-for-repositories.md @@ -0,0 +1,201 @@ +--- +title: Pesquisar repositórios +intro: 'Você pode pesquisar repositórios no {% data variables.product.product_name %} e limitar os resultados usando qualquer combinação dos qualificadores de pesquisa de repositórios.' +redirect_from: + - /articles/searching-repositories/ + - /articles/searching-for-repositories + - /github/searching-for-information-on-github/searching-for-repositories + - /github/searching-for-information-on-github/searching-on-github/searching-for-repositories +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +shortTitle: Pesquisar repositórios +--- + +Você pode pesquisar repositórios globalmente no {% data variables.product.product_location %} ou pesquisar em uma organização específica. Para obter mais informações, consulte "[Sobre a pesquisa no {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)". + +Para incluir bifurcações nos resultados da pesquisa, você precisará adicionar `fork:true` ou `fork:only` à sua consulta. Para obter mais informações, consulte "[Pesquisar em bifurcações](/search-github/searching-on-github/searching-in-forks)". + +{% data reusables.search.syntax_tips %} + +## Pesquisar por nome do repositório, descrição ou conteúdo do arquivo README + +Com o qualificador `in`, você pode restringir a pesquisa ao nome do repositório, descrição do repositório, conteúdo do arquivo README ou qualquer combinação desses itens. Quando você omite esse qualificador, somente o nome e a descrição do repositório são pesquisados. + +| Qualifier | Exemplo | +| ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `in:name` | [**jquery in:name**](https://github.com/search?q=jquery+in%3Aname&type=Repositories) corresponde aos repositórios com "jquery" no nome do respositório. | +| `in:description` | [**jquery in:name,description**](https://github.com/search?q=jquery+in%3Aname%2Cdescription&type=Repositories) corresponde aos repositórios com "jquery" no nome ou descrição do repositório. | +| `in:readme` | [**jquery em:readme**](https://github.com/search?q=jquery+in%3Areadme&type=Repositories) corresponde aos repositórios que mencionam "jquery" no arquivo README do repositório. | +| `repo:owner/name` | [**repo:octocat/hello-world**](https://github.com/search?q=repo%3Aoctocat%2Fhello-world) identifica um nome de repositório específico. | + +## Pesquisar com base no conteúdo do repositório + +Você pode encontrar um repositório pesquisando pelo conteúdo no arquivo README do repositório usando o qualificador `in:readme`. Para obter mais informações, consulte "[Sobre README](/github/creating-cloning-and-archiving-repositories/about-readmes)". + +Além de usar o `in:readme`, não é possível encontrar repositórios pesquisando um conteúdo específico no repositório. Para pesquisar um arquivo ou conteúdo específico em um repositório, você pode usar o localizador de arquivos os qualificadores de pesquisa específicos para código. Para obter mais informações, consulte "[Localizar arquivos no {% data variables.product.prodname_dotcom %}](/search-github/searching-on-github/finding-files-on-github)" e "[Pesquisar códigos](/search-github/searching-on-github/searching-code)". + +| Qualifier | Exemplo | +| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `in:readme` | [**octocat in:readme**](https://github.com/search?q=octocat+in%3Areadme&type=Repositories) corresponde aos repositórios que mencionam "octocat" no arquivo README do repositório. | + +## Pesquisar nos repositórios de um usuário ou uma organização + +Para pesquisar em todos os repositórios de um determinado usuário ou organização, você pode usar os qualificadores `user` ou `org`. + +| Qualifier | Exemplo | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**user:defunkt forks:>100**](https://github.com/search?q=user%3Adefunkt+forks%3A%3E%3D100&type=Repositories) identifica os repositórios de @defunkt que têm mais de 100 bifurcações. | +| org:ORGNAME | [**org:github**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub&type=Repositories) identifica os repositórios do GitHub. | + +## Pesquisar por tamanho do repositório + +O qualificador `size` procura repositórios que têm um tamanho específico (em kilobytes) usando os qualificadores maior que, menor que e intervalo. Para obter mais informações, consulte "[Entender a sintaxe de pesquisa](/github/searching-for-information-on-github/understanding-the-search-syntax)". + +| Qualifier | Exemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| size:n | [**size:1000**](https://github.com/search?q=size%3A1000&type=Repositories) identifica os repositórios que têm exatamente 1 MB. | +| | [**size:>=30000**](https://github.com/search?q=size%3A%3E%3D30000&type=Repositories) identifica os repositórios que têm no mínimo 30 MB. | +| | [**size:<50**](https://github.com/search?q=size%3A%3C50&type=Repositories) identifica os repositórios que têm menos de 50 KB. | +| | [**size:50..120**](https://github.com/search?q=size%3A50..120&type=Repositories) identifica os repositórios que têm entre 50 KB e 120 KB. | + +## Pesquisar por número de seguidores + +É possível filtrar repositórios com base no número de usuários que seguem os repositórios, usando o qualificador `followers` com os qualificadores com maior que, menor que e intervalo. Para obter mais informações, consulte "[Entender a sintaxe de pesquisa](/github/searching-for-information-on-github/understanding-the-search-syntax)". + +| Qualifier | Exemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| followers:n | [**seguidores do nó:>=10000**](https://github.com/search?q=node+followers%3A%3E%3D10000) coincide com repositórios com 10.000 ou mais seguidores e que mencionam a palavra "nó". | +| | [**styleguide linter followers:1..10**](https://github.com/search?q=styleguide+linter+followers%3A1..10&type=Repositories) identifica os repositórios com 1 e 10 seguidores que mencionam a palavra "styleguide linter". | + +## Pesquisar por número de bifurcações + +O qualificador `forks` especifica o número de bifurcações que um repositório deve ter usando os qualificadores maior que, menor que e intervalo. Para obter mais informações, consulte "[Entender a sintaxe de pesquisa](/github/searching-for-information-on-github/understanding-the-search-syntax)". + +| Qualifier | Exemplo | +| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | +| forks:n | [**forks:5**](https://github.com/search?q=forks%3A5&type=Repositories) identifica repositórios com apenas cinco bifurcações. | +| | [**forks:>=205**](https://github.com/search?q=forks%3A%3E%3D205&type=Repositories) identifica repositórios com no mínimo 205 bifurcações. | +| | [**forks:<90**](https://github.com/search?q=forks%3A%3C90&type=Repositories) identifica repositórios com menos de 90 bifurcações. | +| | [**forks:10..20**](https://github.com/search?q=forks%3A10..20&type=Repositories) identifica repositórios com 10 a 20 bifurcações. | + +## Pesquisar por número de estrelas + +Você pode pesquisar repositórios com base no número de estrelas que os repositórios têm, usando os qualificadores maior que, menor que e intervalo. Para obter mais informações, consulte "[Salvar repositórios com estrelas](/github/getting-started-with-github/saving-repositories-with-stars)" e "[Entender a sintaxe de pesquisa](/github/searching-for-information-on-github/understanding-the-search-syntax)". + +| Qualifier | Exemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| stars:n | [**stars:500**](https://github.com/search?utf8=%E2%9C%93&q=stars%3A500&type=Repositories) identifica repositórios com exatamente 500 estrelas. | +| | [**stars:10..20**](https://github.com/search?q=stars%3A10..20+size%3A%3C1000&type=Repositories) identifica repositórios com 10 a 20 estrelas com menos de 1.000 KB. | +| | [**stars:>=500 fork:true language:php**](https://github.com/search?q=stars%3A%3E%3D500+fork%3Atrue+language%3Aphp&type=Repositories) identifica os repositórios que tem no mínimo 500 estrelas, incluindo os bifurcados e que foram escritos em PHP. | + +## Pesquisar por data da criação ou da última atualização do repositório + +Você pode filtrar repositórios com base na data de criação ou da última atualização. Para a criação do repositório, você pode usar o qualificador `created`. Para descobrir quando um repositório foi atualizado pela última vez, você precisará usar o qualificador `pushed`. O qualificador `pushed` retorna uma lista de repositórios, classificados pelo commit mais recente feito em qualquer branch no repositório. + +Os dois usam uma data como parâmetro. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifier | Exemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| created:YYYY-MM-DD | [**webos created:<2011-01-01**](https://github.com/search?q=webos+created%3A%3C2011-01-01&type=Repositories) identifica repositórios com a palavra "webos" que foram criados antes de 2011. | +| pushed:YYYY-MM-DD | [**css pushed:>2013-02-01**](https://github.com/search?utf8=%E2%9C%93&q=css+pushed%3A%3E2013-02-01&type=Repositories) identifica repositórios com a palavra "css" cujo push ocorreu antes de janeiro de 2013. | +| | [**case pushed:>=2013-03-06 fork:only**](https://github.com/search?q=case+pushed%3A%3E%3D2013-03-06+fork%3Aonly&type=Repositories) identifica repositórios com a palavra "case" cujo push foi feito em 6 de março de 2013 ou depois dessa data e que são bifurcações. | + +## Pesquisar por linguagem + +Você pode pesquisar repositórios com base na linguagem do código nos repositórios. + +| Qualifier | Exemplo | +| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| language:LANGUAGE | [**rails language:javascript**](https://github.com/search?q=rails+language%3Ajavascript&type=Repositories) identificar repositórios com a palavra"rails" e que foram escritos em JavaScript. | + +## Pesquisar por tópico + +Você pode encontrar todos os repositórios classificados com um determinado tópico. Para obter mais informações, consulte "[Classificar seu repositório com tópicos](/github/administering-a-repository/classifying-your-repository-with-topics)". + +| Qualifier | Exemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| topic:TOPIC | [**topic:jekyll**](https://github.com/search?utf8=%E2%9C%93&q=topic%3Ajekyll&type=Repositories&ref=searchresults) identifica os repositórios que foram classificados com o tópico "jekyll". | + +## Pesquisar por número de tópicos + +Você pode pesquisar repositórios pelo número de tópicos que foram aplicados aos repositórios, usando o qualificador `topics` junto com os qualificadores maior que, menor que e intervalo. Para obter mais informações, consulte "[Classificar seu repositório com tópicos](/github/administering-a-repository/classifying-your-repository-with-topics)" e "[Entender a sintaxe de pesquisa](/github/searching-for-information-on-github/understanding-the-search-syntax)". + +| Qualifier | Exemplo | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| topics:n | [**topics:5**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A5&type=Repositories&ref=searchresults) identifica os repositórios com cinco tópicos. | +| | [**tópicos:>3**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A%3E3&type=Repositories&ref=searchresults) correspondem a repositórios com mais de três tópicos. | + +{% ifversion fpt or ghes %} + +## Pesquisar por licença + +Você pode pesquisar repositórios pelo tipo de licença nos repositórios. É preciso usar uma palavra-chave de licença para filtrar repositórios por uma determinada licença ou família de licenças. Para obter mais informações, consulte "[Licenciar um repositório](/github/creating-cloning-and-archiving-repositories/licensing-a-repository)". + +| Qualifier | Exemplo | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| license:LICENSE_KEYWORD | [**license:apache-2.0**](https://github.com/search?utf8=%E2%9C%93&q=license%3Aapache-2.0&type=Repositories&ref=searchresults) identifica os repositórios que são licenciados com a Licença Apache 2.0. | + +{% endif %} + +## Pesquisar por visibilidade do repositório + +Você pode filtrar sua pesquisa com base na visibilidade dos repositórios. Para obter mais informações, consulte "[Sobre repositórios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)". + +| Qualificador | Exemplo | ------------- | ------------- |{% ifversion fpt or ghes %} | `is:public` | [**is:public org:github**](https://github.com/search?q=is%3Apublic+org%3Agithub&type=Repositories) corresponde repositórios públicos pertencentes a {% data variables.product.company_short %}.{% endif %} | `is:internal` | [**is:internal test**](https://github.com/search?q=is%3Ainternal+test&type=Repositories) corresponde repositórios internos que você pode acessar e que contêm a palavra "test". | `is:private` | [**is:private pages**](https://github.com/search?q=is%3Aprivate+pages&type=Repositories) corresponde a repositórios privados que você pode acessar e que contêm a palavra "pages". + +{% ifversion fpt %} + +## Pesquisar com base no fato de o repositório ser um espelho + +Você pode pesquisar repositórios com base no fato de os repositórios serem espelhos e hospedados em outro lugar. Para obter mais informações, consulte "[Encontrar maneiras de contribuir para o código aberto em {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)." + +| Qualifier | Exemplo | +| -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `mirror:true` | [**mirror:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Atrue+GNOME&type=) identifica os repositórios que são espelhos e contêm a palavra "GNOME". | +| `mirror:false` | [**mirror:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Afalse+GNOME&type=) corresponde aos repositórios que não são espelhos e contêm a palavra "GNOME". | + +{% endif %} + +## Pesquisar com base no fato de o repositório estar arquivado + +Você pode pesquisar repositórios com base no fato de os repositórios estarem ou não arquivados. Para obter mais informações, consulte "[Arquivando repositórios](/repositories/archiving-a-github-repository/archiving-repositories)". + +| Qualifier | Exemplo | +| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `archived:true` | [**archived:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Atrue+GNOME&type=) identifica os repositórios que estão arquivados e contêm a palavra "GNOME". | +| `archived:false` | [**archived:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Afalse+GNOME&type=) corresponde aos repositórios que não estão arquivados e contêm a palavra "GNOME". | + +{% ifversion fpt %} + +## Pesquisar com base no número de problemas com as etiquetas `good first issue` (um bom primeiro problema) ou `help wanted` (procura-se ajuda) + +Você pode pesquisar repositórios que têm um número mínimo de problemas com as etiquetas `help-wanted` (procura-se ajuda) ou `good-first-issue` (um bom primeiro problema) com os qualificadores `help-wanted-issues:>n` e `good-first-issues:>n`. Para obter mais informações, consulte "[Incentivar contribuições úteis para o seu projeto com etiquetas](/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels)". + +| Qualifier | Exemplo | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `good-first-issues:>n` | [**good-first-issues:>2 javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+good-first-issues%3A%3E2&type=) identifica os repositórios com mais de dois problemas com a etiqueta `good-first-issue` e que contêm a palavra "javascript". | +| `help-wanted-issues:>n` | [**help-wanted-issues:>4 react**](https://github.com/search?utf8=%E2%9C%93&q=react+help-wanted-issues%3A%3E4&type=) identifica os repositórios com mais de quatro problemas com a etiqueta `help-wanted` e que contêm a palavra "React". | + +## Pesquisar com base na capacidade de patrocinador + +Você pode pesquisar repositórios cujos proprietários podem ser patrocinados em {% data variables.product.prodname_sponsors %} com o qualificador `é:sponsorable`. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." + +Você pode pesquisar repositórios que têm um arquivo de financiamento que usa o qualificador `has:funding-file`. Para obter mais informações, consulte[Sobre os arquivos de FINANCIAMENTO](/github/administering-a-repository/managing-repository-settings/displaying-a-sponsor-button-in-your-repository#about-funding-files)". + +| Qualifier | Exemplo | +| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `is:sponsorable` | [**é:patrocinável**](https://github.com/search?q=is%3Asponsorable&type=Repositories) corresponde aos repositórios cujos proprietários têm um perfil de {% data variables.product.prodname_sponsors %}. | +| `has:funding-file` | [**has:funding-file**](https://github.com/search?q=has%3Afunding-file&type=Repositories) corresponde aos repositórios que têm um arquivo FUNDING.yml. | + +{% endif %} + +## Leia mais + +- "[Ordenar os resultados da pesquisa](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" +- "[Pesquisar em bifurcações](/search-github/searching-on-github/searching-in-forks)" diff --git a/translations/pt-BR/content/search-github/searching-on-github/searching-github-marketplace.md b/translations/pt-BR/content/search-github/searching-on-github/searching-github-marketplace.md new file mode 100644 index 0000000000..cb8cb41440 --- /dev/null +++ b/translations/pt-BR/content/search-github/searching-on-github/searching-github-marketplace.md @@ -0,0 +1,38 @@ +--- +title: Pesquisar no GitHub Marketplace +intro: 'Você pode pesquisar aplicativos e ações disponíveis em {% data variables.product.prodname_marketplace %}.' +versions: + fpt: '*' +topics: + - GitHub search +redirect_from: + - /github/searching-for-information-on-github/searching-github-marketplace + - /github/searching-for-information-on-github/searching-on-github/searching-github-marketplace +shortTitle: Pesquisar no GitHub Marketplace +--- + +## Sobre a busca no {% data variables.product.prodname_marketplace %} + +Você pode encontrar aplicativos e ações no {% data variables.product.prodname_marketplace %} de duas formas: + +- Pesquisa a partir de {% data variables.product.prodname_marketplace %}. +- Pesquisa em todos os {% data variables.product.prodname_dotcom_the_website %} e, em seguida, filtre os resultados. + +## Pesquisar em {% data variables.product.prodname_marketplace %} + +1. Na parte superior de qualquer página, clique em **Marketplace**. ![Link do Marketplace](/assets/images/help/search/marketplace-link.png) +2. Digite qualquer palavra-chave e pressione **Enter**. ![Pesquisar linter no {% data variables.product.prodname_marketplace %}](/assets/images/help/search/marketplace-apps-and-actions-search-field.png) +3. Opcionalmente, filtre seus resultados, clicando em uma ou mais opções na barra lateral esquerda. + +## Pesquisar em {% data variables.product.prodname_dotcom_the_website %} + +Sempre que você pesquisar em todos os {% data variables.product.prodname_dotcom_the_website %}, você poderá filtrar os resultados para ver aplicativos e ações correspondentes a partir do {% data variables.product.prodname_marketplace %}. + +1. Navegue até https://github.com/search. +2. Digite qualquer palavra-chave e pressione **Enter**. ![campo de pesquisa](/assets/images/help/search/search-field.png) +3. Na barra lateral esquerda, clique em **Marketplace**. ![Pesquisar resultados para linter com a opção de menu lateral do Marketplace destacado](/assets/images/help/search/marketplace-left-side-navigation.png) + +## Leia mais + +- "[Sobre o {% data variables.product.prodname_marketplace %}](/github/customizing-your-github-workflow/about-github-marketplace)" +- "[Usar ações do {% data variables.product.prodname_marketplace %} em seu fluxo de trabalho](/actions/automating-your-workflow-with-github-actions/using-actions-from-github-marketplace-in-your-workflow)" diff --git a/translations/pt-BR/content/search-github/searching-on-github/searching-in-forks.md b/translations/pt-BR/content/search-github/searching-on-github/searching-in-forks.md new file mode 100644 index 0000000000..d92838ce38 --- /dev/null +++ b/translations/pt-BR/content/search-github/searching-on-github/searching-in-forks.md @@ -0,0 +1,32 @@ +--- +title: Pesquisar em bifurcações +intro: 'Por padrão, [forks](/articles/about-forks) não são mostradas nos resultados da pesquisa. Você poderá optar por incluí-las nas pesquisas de repositórios e nas pesquisas de códigos se elas atenderem a determinados critérios.' +redirect_from: + - /articles/searching-in-forks + - /github/searching-for-information-on-github/searching-in-forks + - /github/searching-for-information-on-github/searching-on-github/searching-in-forks +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +Para exibir bifurcações nos resultados da [pesquisa no repositório](/search-github/searching-on-github/searching-for-repositories), adicione `fork:true` ou `fork:only` à sua consulta. + +As bifurcações somente são indexadas para [pesquisas de códigos](/search-github/searching-on-github/searching-code) quando têm mais estrelas do que o repositório principal. Não é possível pesquisar códigos em uma bifurcação que tem menos estrelas do que seu principal. Para exibir bifurcações com mais estrelas que o repositório principal nos resultados da pesquisa de código, adicione `fork:true` ou `fork:only` à sua consulta. + +O qualificador `fork:true` localiza todos os resultados que correspondem à sua pesquisa, inclusive bifurcações. O qualificador `fork:only` localiza _somente_ bifurcações que correspondem à consulta de pesquisa. + +| Qualifier | Exemplo | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `fork:true` | [**github fork:true**](https://github.com/search?q=github+fork%3Atrue&type=Repositories) identifica todos os repositórios que contém a palavra "github", inclusive as bifurcações. | +| | [**android language:java fork:true**](https://github.com/search?q=android+language%3Ajava+fork%3Atrue&type=Code) identifica o código com a palavra "android", escrita em Java, nas bifurcações e repositórios regulares. | +| `fork:only` | [**github fork:only**](https://github.com/search?q=github+fork%3Aonly&type=Repositories) identifica todas as bifurcações que contêm a palavra "github". | +| | [**forks:>500 fork:only**](https://github.com/search?q=forks%3A%3E500+fork%3Aonly&type=Repositories) corresponde a repositórios com mais de 500 bifurcações e retorna apenas aqueles que são bifurcações. | + +## Leia mais + +- "[Sobre bifurcações](/articles/about-forks)" +- "[Sobre a pesquisa no GitHub](/search-github/getting-started-with-searching-on-github/about-searching-on-github)" 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 new file mode 100644 index 0000000000..3a65a1d28f --- /dev/null +++ b/translations/pt-BR/content/search-github/searching-on-github/searching-issues-and-pull-requests.md @@ -0,0 +1,343 @@ +--- +title: Pesquisar problemas e pull requests +intro: 'Você pode pesquisar problemas e pull requests no {% data variables.product.product_name %} e limitar os resultados usando qualquer combinação destes qualificadores de pesquisa.' +redirect_from: + - /articles/searching-issues/ + - /articles/searching-issues-and-pull-requests + - /github/searching-for-information-on-github/searching-issues-and-pull-requests + - /github/searching-for-information-on-github/searching-on-github/searching-issues-and-pull-requests +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +shortTitle: Pesquisar problemas & PRs +--- + +Você pode pesquisar problemas e pull requests globalmente no {% data variables.product.product_name %} ou pesquisar em uma organização específica. 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)". + +{% tip %} + +**Dicas:**{% ifversion ghes or ghae %} + - Este artigo tem exemplos de pesquisa no site {% data variables.product.prodname_dotcom %}.com, mas você pode usar os mesmos filtros de pesquisa na {% data variables.product.product_location %}.{% endif %} + - Para obter uma lista de sintaxes de pesquisa que podem ser adicionadas a qualquer qualificador de pesquisa para melhorar ainda mais os resultados, consulte "[Entender a sintaxe de pesquisa](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)". + - Use aspas em termos de pesquisa com várias palavras. Por exemplo, se quiser pesquisar problemas com a etiqueta "In progress," pesquise `label:"in progress"`. A pesquisa não faz distinção entre maiúsculas e minúsculas. + - {% data reusables.search.search_issues_and_pull_requests_shortcut %} + + {% endtip %} + +## Pesquisar somente problemas e pull requests + +Por padrão, a pesquisa do {% data variables.product.product_name %} retorna problemas e pull requests. No entanto, você pode restringir os resultados da pesquisa a problemas ou pull requests usando os qualificadores `type` ou `is`. + +| Qualifier | Exemplo | +| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `type:pr` | [**cat type:pr**](https://github.com/search?q=cat+type%3Apr&type=Issues) identifica as pull requests com a palavra "cat". | +| `type:issue` | [**github commenter:defunkt type:issue**](https://github.com/search?q=github+commenter%3Adefunkt+type%3Aissue&type=Issues) identifica os problemas que contêm a palavra "github" e um comentário de @defunkt. | +| `is:pr` | [**event is:pr**](https://github.com/search?utf8=%E2%9C%93&q=event+is%3Apr&type=) identifica as pull requests com a palavra "event". | +| `is:issue` | [**is:issue label:bug is:closed**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aissue+label%3Abug+is%3Aclosed&type=) identifica os problemas fechados com a etiqueta "bug". | + +## Pesquisar por título, texto ou comentários + +Com o qualificador `in`, você pode restringir a pesquisa ao título, texto, comentário ou qualquer combinação desses itens. Quando você omite esse qualificador, o título, o texto e os comentários são pesquisados. + +| Qualifier | Exemplo | +| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `in:title` | [**warning in:title**](https://github.com/search?q=warning+in%3Atitle&type=Issues) identifica os problemas com a palavra "warning" no título. | +| `in:body` | [**error in:title,body**](https://github.com/search?q=error+in%3Atitle%2Cbody&type=Issues) identifica os problemas com a palavra "error" no título ou no texto. | +| `in:comments` | [**shipit in:comments**](https://github.com/search?q=shipit+in%3Acomment&type=Issues) identifica os problemas que mencionam "shipit" nos comentários. | + +## Pesquisar nos repositórios de um usuário ou uma organização + +Para pesquisar problemas e pull requests em todos os repositórios de um usuário ou organização específicos, você pode usar os qualificadores `user` ou `org`. Para pesquisar problemas e pull requests em um repositório específico, você pode usar o qualificador `repo`. + +{% 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`. + +| Qualifier | Exemplo | +| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `state:open` | [**libraries state:open mentions:vmg**](https://github.com/search?utf8=%E2%9C%93&q=libraries+state%3Aopen+mentions%3Avmg&type=Issues) identifica os problemas abertos que mencionam @vmg com a palavra "libraries". | +| `state:closed` | [**design state:closed in:body**](https://github.com/search?utf8=%E2%9C%93&q=design+state%3Aclosed+in%3Abody&type=Issues) identifica os problemas fechados com a palavra "design" no texto. | +| `is:open` | [**performance is:open is:issue**](https://github.com/search?q=performance+is%3Aopen+is%3Aissue&type=Issues) identifica os problemas abertos com a palavra "performance". | +| `is:closed` | [**android is:closed**](https://github.com/search?utf8=%E2%9C%93&q=android+is%3Aclosed&type=) identifica os problemas e as pull requests fechados com a palavra "android". | + +## Filtrar por visibilidade do repositório + +É possível filtrar pela visibilidade do repositório que contém os problemas e pull requests usando o qualificador `is`. Para obter mais informações, consulte "[Sobre repositórios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)". + +| Qualificador | Exemplo | ------------- | ------------- |{% ifversion fpt or ghes %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Issues) corresponde problemas e pull requests nos repositórios públicos.{% endif %}{% ifversion fpt or ghes or ghae %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Issues) corresponde problemas e pull requests em repositórios internos.{% endif %} | `is:private` | [**is:private cupcake**](https://github.com/search?q=is%3Aprivate+cupcake&type=Issues) corresponde problemas e pull requests que contêm a palavra "cupcake" em repositórios que você pode acessar. + +## Pesquisar por autor + +O qualificador `author` encontra problemas e pull requests criados por determinado usuário ou conta de integração. + +| Qualifier | Exemplo | +| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| author:USERNAME | [**cool author:gjtorikian**](https://github.com/search?q=cool+author%3Agjtorikian&type=Issues) corresponde os problemas e os pull requests com a palavra "cool" que foram criados por @gjtorikian. | +| | [**bootstrap in:body author:mdo**](https://github.com/search?q=bootstrap+in%3Abody+author%3Amdo&type=Issues) corresponde problemas escritos por @mdo que contêm a palavra "bootstrap" no texto. | +| author:app/USERNAME | [**author:app/robot**](https://github.com/search?q=author%3Aapp%2Frobot&type=Issues) corresponde a problemas criados pela conta de integração denominada "robot". | + +## Pesquisar por responsável + +O qualificador `assignee` encontra problemas e pull requests que foram atribuídos a um determinado usuário. Não é possível pesquisar problemas e pull requests que têm _qualquer_ responsável, mas é possível pesquisar [problemas e pull requests que não tem nenhum responsável](#search-by-missing-metadata). + +| Qualifier | Exemplo | +| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| assignee:USERNAME | [**assignee:vmg repo:libgit2/libgit2**](https://github.com/search?utf8=%E2%9C%93&q=assignee%3Avmg+repo%3Alibgit2%2Flibgit2&type=Issues) corresponde problemas e pull requests no libgit2 de libgit2 que foram atribuídos a @vmg. | + +## Pesquisar por menção + +O qualificador `mentions` encontra problemas que mencionam um usuário específico. Para obter mais informações, consulte "[Mencionar pessoas e equipes](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)". + +| Qualifier | Exemplo | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| mentions:USERNAME | [**resque mentions:defunkt**](https://github.com/search?q=resque+mentions%3Adefunkt&type=Issues) corresponde problemas com a palavra "resque" que mencionam @defunkt. | + +## Pesquisar por menção da equipe + +Para organizações e equipes das quais você faz parte, você pode usar o qualificador `team` para encontrar problemas ou pull requests que fazem @menção a uma equipe específica na organização. Substitua os nomes de exemplo pelos nome da organização e da equipe para fazer uma pesquisa. + +| Qualifier | Exemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------- | +| team:ORGNAME/TEAMNAME | **team:jekyll/owners** corresponde problemas em que a equipe `@jekyll/owners` é mencionada. | +| | **team:myorg/ops is:open is:pr** corresponde pull requests abertos em que a equipe `@myorg/ops` é mencionada. | + +## Pesquisar por autor do comentário + +O qualificador `commenter` encontra problemas que contêm um comentário de um usuário específico. + +| Qualifier | Exemplo | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| commenter:USERNAME | [**github commenter:defunkt org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Adefunkt+org%3Agithub&type=Issues) corresponde problemas nos repositórios do GitHub que contêm a palavra "github" e têm um comentário de @defunkt. | + +## Pesquisar por um usuário envolvido em um problema ou uma pull request + +Você pode usar o qualificador `involves` para encontrar problemas que envolvem de alguma forma um usuário específico. O qualificador `involves` é uma expressão lógica OR entre os qualificadores `author`, `assignee`, `mentions` e `commenter` para um único usuário. Em outras palavras, esse qualificador encontra problemas e pull requests que foram criados por um usuário, atribuídos a ele, que o mencionam ou que foram comentados por ele. + +| Qualifier | Exemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 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 %} +## 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 %} + +## Pesquisar por etiqueta + +Você pode limitar os resultados por etiquetas usando o qualificador `label`. Alguns problemas podem ter várias etiquetas, e você pode relacionar um qualificador separado para cada problema. + +| Qualifier | Exemplo | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| label:LABEL | [**label:"help wanted" language:ruby**](https://github.com/search?utf8=%E2%9C%93&q=label%3A%22help+wanted%22+language%3Aruby&type=Issues) identifica os problemas com a etiqueta "help wanted" nos repositórios de Ruby. | +| | [**broken in:body -label:bug label:priority**](https://github.com/search?q=broken+in%3Abody+-label%3Abug+label%3Apriority&type=Issues) identifica problemas com a palavra "broken" no texto e que não têm a etiqueta "bug", mas *têm* a etiqueta "priority". | +| | [**label:bug label:resolved**](https://github.com/search?l=&q=label%3Abug+label%3Aresolved&type=Issues) corresponde a problemas com as etiquetas "erro" e "resolvido".{% ifversion fpt or ghes > 3.2 or ghae-next %} +| | [**rótulo:bug,resolvido**](https://github.com/search?q=label%3Abug%2Cresolved&type=Issues) corresponde a problemas com a etiqueta "erro" ou a etiqueta "resolvido".{% endif %} + +## Pesquisar por marco + +O qualificador `milestone` encontra problemas ou pull requests que fazem parte de um [marco](/articles/about-milestones) em um repositório. + +| Qualifier | Exemplo | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| milestone:MILESTONE | [**milestone:"overhaul"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22overhaul%22&type=Issues) identifica os problemas que estão em um marco chamado "overhaul". | +| | [**milestone:"bug fix"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22bug+fix%22&type=Issues) identifica os problemas que estão em um marco chamado "bug fix". | + +## Pesquisar por quadro de projeto + +Você pode usar o qualificador `project` para encontrar problemas associados a um [quadro de projeto](/articles/about-project-boards/) específico em um repositório ou uma organização. Você deve pesquisar pelo número do quadro de projeto. Você pode encontrar o número do quadro de projeto no final da URL do quadro de projeto. + +| Qualifier | Exemplo | +| -------------------------- | --------------------------------------------------------------------------------------------------------------------------- | +| project:PROJECT_BOARD | **project:github/57** identifica os problemas do GitHub associados aos quadros de projeto 57 da organização. | +| project:REPOSITORY/PROJECT_BOARD | **project:github/linguist/1** identifica os problemas associados ao quadro de projeto 1 no repositório Linguist de @github. | + +## Pesquisar por status do commit + +Você pode filtrar pull requests com base no status dos commits. Isso é especialmente útil ao usar [a API de status](/rest/reference/repos#statuses) ou um serviço CI. + +| Qualifier | Exemplo | +| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `status:pending` | [**language:go status:pending**](https://github.com/search?utf8=%E2%9C%93&q=language%3Ago+status%3Apending) identifica as pull requests abertas nos repositórios de Go com status pendente. | +| `status:success` | [**is:open status:success finally in:body**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aopen+status%3Asuccess+finally+in%3Abody&type=Issues) identifica as pull requests abertas com a palavra "finally" no texto com status de sucesso. | +| `status:failure` | [**created:2015-05-01..2015-05-30 status:failure**](https://github.com/search?utf8=%E2%9C%93&q=created%3A2015-05-01..2015-05-30+status%3Afailure&type=Issues) identifica as pull requests abertas em maio de 2015 com status de falha. | + +## Pesquisar por SHA do commit + +Se você souber o hash SHA de um commit, poderá usá-lo para pesquisar pull requests que contêm esse SHA. A sintaxe do SHA deve ter no mínimo sete caracteres. + +| Qualifier | Exemplo | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| SHA | [**e1109ab**](https://github.com/search?q=e1109ab&type=Issues) identifica as pull requests com um SHA de commit que começa com `e1109ab`. | +| | [**0eff326d6213c is:merged**](https://github.com/search?q=0eff326d+is%3Amerged&type=Issues) identifica as pull requests com merge que têm um SHA de commit que começa com `0eff326d6213c`. | + +## Pesquisar por nome do branch + +Você pode filtrar pull requests com base no branch de origem (branch "head") ou no branch do merge (branch "base"). + +| Qualifier | Exemplo | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| head:HEAD_BRANCH | [**head:change is:closed is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=head%3Achange+is%3Aclosed+is%3Aunmerged) identifica as pull requests abertas de branchs cujo nome começa com a palavra "change" e estão fechados. | +| base:BASE_BRANCH | [**base:gh-pages**](https://github.com/search?utf8=%E2%9C%93&q=base%3Agh-pages) identifica as pull requests que estão sendo incorporadas no branch `gh-pages`. | + +## Pesquisar por linguagem + +Com o qualificador `language`, você pode pesquisar problemas e pull requests em repositórios que foram escritos em uma linguagem específica. + +| Qualifier | Exemplo | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| language:LANGUAGE | [**language:ruby state:open**](https://github.com/search?q=language%3Aruby+state%3Aopen&type=Issues) identifica os problemas abertos que estão em repositórios de Ruby. | + +## 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. + +| Qualifier | Exemplo | +| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| comments:n | [**state:closed comments:>100**](https://github.com/search?q=state%3Aclosed+comments%3A%3E100&type=Issues) identifica os problemas fechados com mais de 100 comentários. | +| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Issues) identifica os problemas com 500 a 1.000 comentários. | + +## 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. + +| Qualifier | Exemplo | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| interactions:n | [** interactions:>2000**](https://github.com/search?q=interactions%3A%3E2000) identifica pull requests ou problemas com mais de 2.000 interações. | +| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) identifica pull requests ou problemas com 500 a 1.000 interações. | + +## 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). + +| Qualifier | Exemplo | +| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | +| reactions:n | [** reactions:>1000**](https://github.com/search?q=reactions%3A%3E1000&type=Issues) identifica os problemas com mais de 1.000 reações. | +| | [**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)". + +| Qualificador | Exemplo | ------------- | -------------{% ifversion fpt or ghes or ghae %} | `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 %} + +## Pesquisar por status de revisão e revisor da pull request + +Você pode filtrar as pull requests com base no [status de revisão](/articles/about-pull-request-reviews) (_none_ (nenhuma), _required_ (obrigatória), _approved_ (aprovada) ou _changes requested_ (alterações solicitadas)), por revisor e por revisor solicitado. + +| 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. 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 or ghes > 3.2 %} +| 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) 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. | + +## Pesquisar por data da criação ou da última atualização de um problema ou uma pull request + +Você pode filtrar problemas com base na data de criação ou da última atualização. Para a criação do problema, você pode usar o qualificador `created`. Para descobrir quando um problema foi atualizado pela última vez, você precisará usar o qualificador `updated`. + +Os dois usam uma data como parâmetro. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifier | Exemplo | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| created:YYYY-MM-DD | [**language:c# created:<2011-01-01 state:open**](https://github.com/search?q=language%3Ac%23+created%3A%3C2011-01-01+state%3Aopen&type=Issues) corresponde a problemas abertos criados antes de 2011 nos repositórios escritos em C#. | +| updated:YYYY-MM-DD | [**weird in:body updated:>=2013-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2013-02-01&type=Issues) corresponde a problemas com a palavra "weird" no texto que foram atualizados após fevereiro de 2013. | + +## Pesquisar por data de encerramento de um problema ou uma pull request + +Você pode filtrar somente problemas e pull requests fechados usando o qualificador `closed`. + +Esse qualificador usa a data como parâmetro. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifier | Exemplo | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| closed:YYYY-MM-DD | [**language:swift closed:>2014-06-11**](https://github.com/search?q=language%3Aswift+closed%3A%3E2014-06-11&type=Issues) corresponde a problemas e pull requests no Swift fechados após 11 de junho de 2014. | +| | [**data in:body closed:<2012-10-01**](https://github.com/search?utf8=%E2%9C%93&q=data+in%3Abody+closed%3A%3C2012-10-01+&type=Issues) corresponde a problemas e pull requests com a palavra "data" no texto, que foram fechados antes de outubro de 2012. | + +## Pesquisar por data do merge da pull request + +Você pode filtrar somente as pull requests com merge usando o qualificador `merged`. + +Esse qualificador usa a data como parâmetro. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifier | Exemplo | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| merged:YYYY-MM-DD | [**language:javascript merge:<2011-01-01**](https://github.com/search?q=language%3Ajavascript+merged%3A%3C2011-01-01+&type=Issues) corresponde a pull requests em repositórios do JavaScript que foram mesclados antes de 2011. | +| | [**ast in:title language:ruby merged:>=2014-05-01**](https://github.com/search?q=fast+in%3Atitle+language%3Aruby+merged%3A%3E%3D2014-05-01+&type=Issues) corresponde a pull requests no Ruby com a palavra "fast" no título que foram mesclados após maio de 2014. | + +## Pesquisar somente pull request com merge ou sem merge + +Você pode filtrar as pull requests com ou sem merge usando o qualificador `is`. + +| Qualifier | Exemplo | +| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `is:merged` | [**bugfix is:pr is:merged**](https://github.com/search?utf8=%E2%9C%93&q=bugfix+is%3Apr+is%3Amerged&type=) identifica as pull requests com merge que têm a palavra "bugfix". | +| `is:unmerged` | [**error is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=error+is%3Aunmerged&type=) identifica problemas e pull requests fechados com a palavra "error". | + +## Pesquisar com base no fato de o repositório estar arquivado + +O qualificador `archived` restringe os resultados a problemas ou pull requests em um repositório arquivado. + +| Qualifier | Exemplo | +| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `archived:true` | [**archived:true GNOME**](https://github.com/search?q=archived%3Atrue+GNOME&type=) identifica problemas e pull requests que contêm a palavra "GNOME" em repositórios arquivados aos quais você tem acesso. | +| `archived:false` | [**archived:false GNOME**](https://github.com/search?q=archived%3Afalse+GNOME&type=) identifica problemas e pull requests que contêm a palavra "GNOME" em repositórios arquivados aos quais você tem acesso. | + +## Pesquisar conversas bloqueadas e não bloqueadas + +Você pode pesquisar problema ou pull requests que têm uma conversa bloqueada usando o qualificador `is`. Para obter mais informações, consulte "[Bloquear conversas](/communities/moderating-comments-and-conversations/locking-conversations)". + +| Qualifier | Exemplo | +| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `is:locked` | [**code of conduct is:locked is:issue archived:false**](https://github.com/search?q=code+of+conduct+is%3Alocked+is%3Aissue+archived%3Afalse) identifica problemas ou pull requests com as palavras "code of conduct" que têm uma conversa bloqueada em um repositório que não está arquivado. | +| `is:unlocked` | [**code of conduct is:unlocked is:issue archived:false**](https://github.com/search?q=code+of+conduct+is%3Aunlocked+archived%3Afalse) identifica problemas ou pull requests com as palavras "code of conduct" que têm uma conversa desbloqueada em um repositório que não está arquivado. | + +## Pesquisar por metadados ausentes + +Você pode limitar a pesquisa a problemas e pull requests que não têm determinados metadados usando o qualificador `no`. Esses metadados incluem: + +* Etiquetas +* Marcos +* Responsáveis +* Projetos + +| Qualifier | Exemplo | +| -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `no:label` | [**priority no:label**](https://github.com/search?q=priority+no%3Alabel&type=Issues) identifica problemas e pull requests com a palavra "priority" que não têm nenhuma etiqueta. | +| `no:milestone` | [**sprint no:milestone type:issue**](https://github.com/search?q=sprint+no%3Amilestone+type%3Aissue&type=Issues) identifica problemas que não estão associados a um marco e contêm a palavra "sprint". | +| `no:assignee` | [**important no:assignee language:java type:issue**](https://github.com/search?q=important+no%3Aassignee+language%3Ajava+type%3Aissue&type=Issues) identifica problemas que não estão associados a um responsável, contêm a palavra "important" e estão em repositórios Java. | +| `no:project` | [**build no:project**](https://github.com/search?utf8=%E2%9C%93&q=build+no%3Aproject&type=Issues) identifica problemas que não estão associados a um quadro de projeto e contêm a palavra "build". | + +## Leia mais + +- "[Ordenar os resultados da pesquisa](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" diff --git a/translations/pt-BR/content/search-github/searching-on-github/searching-topics.md b/translations/pt-BR/content/search-github/searching-on-github/searching-topics.md new file mode 100644 index 0000000000..e74c6fcf1a --- /dev/null +++ b/translations/pt-BR/content/search-github/searching-on-github/searching-topics.md @@ -0,0 +1,55 @@ +--- +title: Pesquisar tópicos +intro: 'Você pode pesquisar tópicos associados a repositórios no {% data variables.product.product_name %}.' +redirect_from: + - /articles/searching-topics + - /github/searching-for-information-on-github/searching-topics + - /github/searching-for-information-on-github/searching-on-github/searching-topics +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +## Pesquisar tópicos no {% data variables.product.product_name %} + +Você pode pesquisar tópicos no {% data variables.product.product_name %}, explorar tópicos relacionados e ver quantos repositórios estão associados a um tópico específico. + +1. Navegue até https://github.com/search. +2. Insira uma palavra-chave de tópico. ![campo de pesquisa](/assets/images/help/search/search-field.png) +3. Na barra lateral esquerda, para limitar a pesquisa aos tópicos, clique em **Topics** (Tópicos). +{% ifversion fpt %} + ![Página de resultados da pequisa do repositório Jekyll com opção de tópico do menu lateral em destaque](/assets/images/help/search/topic-left-side-navigation-dotcom.png){% else %} +![Jekyll repository search results page on dotcom with topics side-menu option highlighted](/assets/images/help/search/topic-left-side-navigation.png){% endif %} + +## Limitar a pesquisa com qualificadores de pesquisa + +Se quiser explorar repositórios sobre um tópico específico, encontrar projetos para contribuição ou saber quais são os tópicos mais populares no {% data variables.product.product_name %}, pesquise tópicos com os qualificadores de pesquisa `is:featured`, `is:curated`, `repositories:n` e `created:YYYY-MM-DD`. + +O qualificador de pesquisa `is:featured` limita os resultados da pequisa aos tópicos com mais repositórios no {% data variables.product.product_name %}. Esses tópicos também são apresentados em https://github.com/topics/. + +O qualificador de pesquisa `is:curated` limita os resultados da pequisa aos tópicos que os integrantes da comunidade adicionaram informações adicionais. Para obter mais informações, consulte o [explorar o repositório](https://github.com/github/explore). + +Você pode filtrar os tópicos com base na data de criação usando parâmetro de data e `created:` ou com base em quantos repositórios estão associados ao tópico usando `repositories:n`. Esses dois qualificadores podem usar os [qualificadores maior que, menor que e intervalo](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). + +{% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifier | Exemplo | +| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `is:curated` | [**is:curated javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+is%3Acurated&type=Topics) identifica os tópicos com curadoria que contêm a palavra "javascript". | +| `is:featured` | [**is:featured javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+is%3Afeatured&type=Topics) identifica os tópicos apresentados em https://github.com/topics/ que contêm a palavra "javascript". | +| `is:not-curated` | [**is:not-curated javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+is%3Anot-curated&type=Topics) identifica os tópicos que não têm informações adicionais, como descrições ou logotipos, e contêm a palavra "javascript". | +| `is:not-featured` | [**is:not-featured javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+is%3Anot-featured&type=Topics) identifica os tópicos que não são apresentados em https://github.com/topics/ e contêm a palavra "javascript". | +| `repositories:n` | [**repositories:>5000**](https://github.com/search?q=repositories%3A%3E5000) identifica os tópicos com mais de 5.000 repositórios. | +| created:YYYY-MM-DD | [**Serverless created:>2019-01-01**](https://github.com/search?q=Serverless+created%3A%3E2019-01-01&type=Topics) identifica os tópicos com a palavra "serverless" que foram criados depois de 2018. | + +## Pesquisar repositórios por tópico + +Você pode usar o qualificador `topic:` para encontrar os repositórios conectados a um tópico específico. Para obter mais informações, consulte "[Pesquisar repositórios](/search-github/searching-on-github/searching-for-repositories/#search-by-topic)". + +## Leia mais +- "[Classificar seu repositório com tópicos](/articles/classifying-your-repository-with-topics)" diff --git a/translations/pt-BR/content/search-github/searching-on-github/searching-users.md b/translations/pt-BR/content/search-github/searching-on-github/searching-users.md new file mode 100644 index 0000000000..a76bbab779 --- /dev/null +++ b/translations/pt-BR/content/search-github/searching-on-github/searching-users.md @@ -0,0 +1,106 @@ +--- +title: Pesquisar usuários +intro: 'Você pode pesquisar usuários no {% data variables.product.product_name %} e limitar os resultados usando qualquer combinação dos qualificadores da pesquisa de usuário.' +redirect_from: + - /articles/searching-users + - /github/searching-for-information-on-github/searching-users + - /github/searching-for-information-on-github/searching-on-github/searching-users +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +Você pode pesquisar usuários globalmente no {% data variables.product.product_name %}. 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)". + +{% data reusables.search.syntax_tips %} + +## Pesquisar somente usuários ou organizações + +Por padrão, a pesquisa de usuários retorna pessoas e organizações. No entanto, você pode usar o qualificador `type` para restringir os resultados a contas pessoais ou organizações. + +| Qualifier | Exemplo | +| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `type:user` | [**mike in:name created:<2011-01-01 type:user**](https://github.com/search?q=mike+in:name+created%3A%3C2011-01-01+type%3Auser&type=Users) identifica as contas pessoais com nome "mike" que foram criadas antes de 2011. | +| `type:org` | [**data in:email type:org**](https://github.com/search?q=data+in%3Aemail+type%3Aorg&type=Users) identifica as organizações com a palavra "data" no e-mail. | + +## Pesquisar por nome da conta, nome completo ou e-mail público + +Você pode restringir a pesquisa ao nome da conta da organização ou ao usuário pessoal com os qualificadores `user` ou `org`. + +Com o qualificador `in`, você pode restringir a pesquisa ao nome de usuário (`login`), nome completo, e-mail público e qualquer combinação desses itens. Quando você omite esse qualificador, somente o nome de usuário e o endereço de e-mail são pesquisados. Por questão de privacidade, não é possível pesquisar pelo nome do domínio do e-mail. + +| Qualifier | Exemplo | +| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `user:name` | [**user:octocat**](https://github.com/search?q=user%3Aoctocat&type=Users) identifica o usuário com o nome de usuário "octocat". | +| `org:name` | [**org:electron type:users**](https://github.com/search?q=org%3Aelectron+type%3Ausers&type=Users) identifica o nome da conta da organização Electron. | +| `in:login` | [**kenya in:login**](https://github.com/search?q=kenya+in%3Alogin&type=Users) identifica os usuários com a palavra "kenya" no nome de usuário. | +| `in:name` | [**bolton in:name**](https://github.com/search?q=bolton+in%3Afullname&type=Users) identifica os usuários cujo nome real contém a palavra "bolton". | +| `fullname:firstname lastname` | [**fullname:nat friedman**](https://github.com/search?q=fullname%3Anat+friedman&type=Users) identifica o usuário com o nome completo "Nat Friedman". Observação: esse qualificador de pesquisa considera o espaçamento. | +| `in:email` | [**data in:email**](https://github.com/search?q=data+in%3Aemail&type=Users&utf8=%E2%9C%93) identifica os usuários com a palavra "data" no e-mail. | + +## Pesquisar por número de repositórios do usuário + +Você pode filtrar usuários com base no número de repositórios usando o qualificador `repos` e os [qualificadores maior que, menor que e intervalo](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). + +| Qualifier | Exemplo | +| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| repos:n | [**repos:>9000**](https://github.com/search?q=repos%3A%3E%3D9000&type=Users) corresponde a usuários cujo número de repositórios é superior a 9.000. | +| | [**bert repos:10..30**](https://github.com/search?q=bert+repos%3A10..30&type=Users) identifica os usuários com a palavra "bert" no nome de usuário ou nome real que têm entre 10 e 30 repositório. | + +## Pesquisar por local + +Você pode pesquisar usuários pelo local indicado no perfil dele. + +| Qualifier | Exemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| location:LOCATION | [**repos:1 location:iceland**](https://github.com/search?q=repos%3A1+location%3Aiceland&type=Users) identifica os usuários com exatamente 1 repositório que moram na Islândia. | + +## Pesquisar por linguagem do repositório + +Com o qualificador `language`, você pode pesquisar usuários com base na linguagem dos repositórios deles. + +| Qualifier | Exemplo | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| language:LANGUAGE | [**language:javascript location:russia**](https://github.com/search?q=language%3Ajavascript+location%3Arussia&type=Users) identificar os usuários na Russia com a maior parte dos repositórios escritos em JavaScript. | +| | [**jenny language:javascript in:fullname**](https://github.com/search?q=jenny+language%3Ajavascript+in%3Afullname&type=Users) identificar os usuários com repositórios em JavaScript cujo nome completo contém a palavra "jenny". | + +## Pesquisar por data de criação da conta de usuário + +Você pode filtrar usuários com base na data de ingresso no {% data variables.product.product_name %} com o qualificador `created`. Esse qualificador usa uma data como parâmetro. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifier | Exemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| created:YYYY-MM-DD | [**created:<2011-01-01**](https://github.com/search?q=created%3A%3C2011-01-01&type=Users) corresponde a usuários que juntaram-se antes de 2011. | +| | [**created:>=2013-05-11**](https://github.com/search?q=created%3A%3E%3D2013-05-11&type=Users) corresponde a usuários que juntaram-se em ou após 11 de maio de 2013. | +| | [**created:2013-03-06 location:london**](https://github.com/search?q=created%3A2013-03-06+location%3Alondon&type=Users) identifica os usuários de Londres que ingressaram em 6 de março de 2013. | +| | [**created:2010-01-01..2011-01-01 john in:login**](https://github.com/search?q=created%3A2010-01-01..2011-01-01+john+in%3Ausername&type=Users) identifica os usuários que ingressaram entre 2010 e 2011 com a palavra "john" no nome de usuário. | + +## Pesquisar por número de seguidores + +Você pode filtrar usuários com base no número de seguidores usando o qualificador `followers` com os [qualificadores maior que, menor que e intervalo](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). + +| Qualifier | Exemplo | +| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| followers:n | [**followers:>=1000**](https://github.com/search?q=followers%3A%3E%3D1000&type=Users) corresponde a usuários com 1.000 seguidores ou mais. | +| | [**sparkle followers:1..10**](https://github.com/search?q=sparkle+followers%3A1..10&type=Users) identifica os usuários com 1 a 10 seguidores com a palavra "sparkle" no nome. | + +{% ifversion fpt %} + +## Pesquisar com base na capacidade de patrocinador + +Você pode fazer a pesquisa para usuários e organizações que podem ser patrocinados em {% data variables.product.prodname_sponsors %} com o qualificador`is:sponsorable`. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." + +| Qualifier | Exemplo | +| ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `is:sponsorable` | [**is:sponsorable**](https://github.com/search?q=is%3Asponsorable&type=Users) corresponde a usuários e organizações que têm um perfil de {% data variables.product.prodname_sponsors %}. | + +{% endif %} + +## Leia mais + +- "[Ordenar os resultados da pesquisa](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" diff --git a/translations/pt-BR/content/search-github/searching-on-github/searching-wikis.md b/translations/pt-BR/content/search-github/searching-on-github/searching-wikis.md new file mode 100644 index 0000000000..731277a88f --- /dev/null +++ b/translations/pt-BR/content/search-github/searching-on-github/searching-wikis.md @@ -0,0 +1,51 @@ +--- +title: Pesquisar wikis +intro: 'Você pode pesquisar wikis no {% data variables.product.product_name %} e limitar os resultados usando qualquer combinação dos qualificadores da pesquisa de wiki.' +redirect_from: + - /articles/searching-wikis + - /github/searching-for-information-on-github/searching-wikis + - /github/searching-for-information-on-github/searching-on-github/searching-wikis +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +Você pode pesquisar wikis globalmente no {% data variables.product.product_name %} ou pesquisar em uma organização ou um repositório específico. 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)". + +{% data reusables.search.syntax_tips %} + +## Pesquisar nos repositórios de um usuário ou uma organização + +Para pesquisar páginas wiki em todos os repositórios de um determinado usuário ou organização, use os qualificadores `user` ou `org`. Para pesquisar páginas wiki em um repositório específico, use o qualificador `repo`. + +| Qualifier | Exemplo | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**user:defunkt**](https://github.com/search?q=user%3Adefunkt&type=Wikis) identifica as páginas wikis nos repositórios de propriedade de @defunkt. | +| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=Wikis&utf8=%E2%9C%93) identifica os wikis nos repositórios de propriedade da orgain GitHub. | +| repo:USERNAME/REPOSITORY | [**repo:defunkt/gibberish**](https://github.com/search?q=user%3Adefunkt&type=Wikis) identifica as páginas wiki no repositório "gibberish" de @defunkt. | + +## Pesquisar no título ou no texto da página wiki + +Os qualificadores `in` limitam a pesquisa ao texto ou ao título da página wiki. Sem o qualificador, o título e o texto são pesquisados. + +| Qualifier | Exemplo | +| ---------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `in:title` | [**usage in:title**](https://github.com/search?q=usage+in%3Atitle&type=Wikis) identifica os títulos de página wiki com a palavra "usage". | +| `in:body` | [**installation in:body**](https://github.com/search?q=installation+in%3Abody&type=Wikis) identifica as páginas wiki com a palavra "installation" no texto principal. | + +## Pesquisar por data da última atualização + +O qualificador `updated` identifica as páginas wiki que foram atualizadas pela última vez no intervalo de datas especificado. + +{% data reusables.search.date_gt_lt %} + +| Qualifier | Exemplo | +| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| updated:YYYY-MM-DD | [**usage updated:>2016-01-01**](https://github.com/search?q=usage+updated%3A>2016-01-01&type=Wikis) corresponde a páginas de wiki com a palavra "uso", cuja última atualização foi depois de 01/01/2016. | + +## Leia mais + +- "[Ordenar os resultados da pesquisa](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" diff --git a/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md index ada0a4ae9b..fab07eb42b 100644 --- a/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md +++ b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md @@ -30,6 +30,7 @@ shortTitle: Gerenciar camadas de pagamento 1. Opcionalmente, para editar uma camada no rascunho, encontre a camada no rascunho e clique em **Editar**. ![Botão editar ao lado da camada no rascunho](/assets/images/help/sponsors/draft-tier-edit.png) {% data reusables.sponsors.click-add-tier %} {% data reusables.sponsors.tier-price-description %} +{% data reusables.sponsors.add-welcome-message %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} 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 f56d1f87a9..18fa23e2d6 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 @@ -51,6 +51,7 @@ Para se juntar ao {% data variables.product.prodname_sponsors %} como colaborado {% data reusables.sponsors.navigate-to-sponsor-tiers-tab %} {% data reusables.sponsors.click-add-tier %} {% data reusables.sponsors.tier-price-description %} +{% data reusables.sponsors.add-welcome-message %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} {% data reusables.sponsors.add-more-tiers %} 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-user-account.md index 3a62c41cdf..870148b0cb 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-user-account.md @@ -50,6 +50,7 @@ Depois de {% data variables.product.prodname_dotcom %} avaliar sua solicitação {% data reusables.sponsors.navigate-to-sponsor-tiers-tab %} {% data reusables.sponsors.click-add-tier %} {% data reusables.sponsors.tier-price-description %} +{% data reusables.sponsors.add-welcome-message %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} {% data reusables.sponsors.add-more-tiers %} 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 9e8807ff0c..9185d1e612 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 @@ -37,6 +37,8 @@ The W-8 BEN and W-8 BEN-E tax forms ask for a "U.S. taxpayer identification numb If you are not a U.S. citizen or other U.S. person, including a resident alien individual, then you will usually need to provide the "Foreign tax identifying number". This is a tax identification number that your country of residence has issued you. +If your country of residence or billing country is India, then you can use your Permanent Account Number (PAN) as your tax identification number. + {% note %} **Note:** If your country does not require citizens to have a tax number issued by the government, then you can instead write "not legally required". @@ -56,6 +58,18 @@ O {% data variables.product.prodname_dotcom %} não retém impostos de pagamento {% data reusables.sponsors.sponsorships-not-tax-deductible %} +## Sales tax + +GitHub is providing information to assist you in calculating your sales tax obligations. This information is not personalized to your country or tax situation and we recommend you talk to a professional to understand your specific obligations. However, we'd like to provide some high-level information to help you understand the general principles of digital sales tax. + +In most countries around the world, sales tax for digital transactions is based on the location of the recipient, not on the seller. For example, if you are a maintainer in the United States and you provide a taxable benefit to a Sponsor in Germany, German sales tax would apply. + +Sales tax is generally only applicable when a good or service of value is being provided. Goodwill/general support/undying appreciation is not normally taxable. + +In the US, both B2B (business-to-business) and B2C (business-to-consumer) are subject to sales tax. + +In the EU and most other countries and regions, B2C sales are subject to sales tax. B2B sales are not subject to tax. C2C and C2B sales where a consumer is not registered for VAT are not taxable. + ## Leia mais - [Exibir patrocinadores e patrocínios](/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships) diff --git a/translations/pt-BR/data/glossaries/external.yml b/translations/pt-BR/data/glossaries/external.yml index 6f0b1086c5..c57cf60278 100644 --- a/translations/pt-BR/data/glossaries/external.yml +++ b/translations/pt-BR/data/glossaries/external.yml @@ -9,7 +9,7 @@ - term: token de recuperação de conta description: >- - Credencial de autenticação armazenada como parte de uma configuração de recuperação de conta chamada Recuperação de contas em outro lugar que permite armazenar essa credencial de backup. + **Deprecated and will be disabled December 1st, 2021.** The authentication credential stored as part of an account recovery setup called Recover Accounts Elsewhere that allows you to store this backup credential. - term: Visualização da API description: >- @@ -574,7 +574,7 @@ - term: recuperação de contas em outro lugar description: >- - Permite aos usuários adicionar uma camada de segurança extra à conta do GitHub em caso de perda do acesso à autenticação de dois fatores ou aos códigos de recuperação. Os usuários podem associar suas contas do GitHub às contas do Facebook armazenando uma credencial de autenticação em forma de token de recuperação para a conta do GitHub no Facebook. + **Deprecated and will be disabled December 1st, 2021.** Allows users to add an extra security factor to their GitHub account in case they lose access to their two-factor authentication method or recovery codes. Users can associate their GitHub account with their Facebook account by storing an authentication credential in the form of an account recovery token for their GitHub account with Facebook. - term: código de recuperação description: Código que ajuda a recuperar o acesso à conta do GitHub. diff --git a/translations/pt-BR/data/learning-tracks/actions.yml b/translations/pt-BR/data/learning-tracks/actions.yml index 7893a722dc..c2e6fa25b8 100644 --- a/translations/pt-BR/data/learning-tracks/actions.yml +++ b/translations/pt-BR/data/learning-tracks/actions.yml @@ -7,6 +7,7 @@ getting_started: - /actions/learn-github-actions/finding-and-customizing-actions - /actions/learn-github-actions/essential-features-of-github-actions - /actions/learn-github-actions/managing-complex-workflows + - /actions/learn-github-actions/reusing-workflows - /actions/learn-github-actions/security-hardening-for-github-actions featured_track: true continuous_integration: diff --git a/translations/pt-BR/data/release-notes/enterprise-server/2-20/15.yml b/translations/pt-BR/data/release-notes/enterprise-server/2-20/15.yml index aa3c664487..29da15e1d2 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/2-20/15.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/2-20/15.yml @@ -1,24 +1,23 @@ date: '2020-08-26' sections: security_fixes: - - >- - **CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2883, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700, - https://github.com/github/pages/pull/2890, https://github.com/github/pages/pull/2898, https://github.com/github/pages/pull/2909, https://github.com/github/pages/pull/2891, https://github.com/github/pages/pull/2884, https://github.com/github/pages/pull/2889 {% endcomment %} - - '**MEDIUM:** An improper access control vulnerability was identified that allowed authenticated users of the instance to determine the names of unauthorized private repositories given their numerical IDs. This vulnerability did not allow unauthorized access to any repository content besides the name. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.22 and has been assigned [CVE-2020-10517](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10517). The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/151987, https://github.com/github/github/pull/151713 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21852, https://github.com/github/enterprise2/pull/21828, https://github.com/github/enterprise2/pull/22153, https://github.com/github/enterprise2/pull/21920, https://github.com/github/enterprise2/pull/22215, https://github.com/github/enterprise2/pull/22190 {% endcomment %}' + - '**CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2883, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700, https://github.com/github/pages/pull/2890, https://github.com/github/pages/pull/2898, https://github.com/github/pages/pull/2909, https://github.com/github/pages/pull/2891, https://github.com/github/pages/pull/2884, https://github.com/github/pages/pull/2889 {% endcomment %}' + - '**MÉDIO:** Identificou-se uma vulnerabilidade de controle de acesso imprópria, que permitiu que usuários autenticados da instância determinassem os nomes de repositórios privados não autorizados dados seus IDs numéricos. Esta vulnerabilidade não permitiu o acesso não autorizado a qualquer conteúdo de repositórios além do nome. Esta vulnerabilidade afetou todas as versões do GitHub Enterprise Server anteriores à 2.22 e foi atribuído [CVE-2020-10517](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10517). A vulnerabilidade foi relatada por meio do [programa de GitHub Bug Bounty](https://bounty. ithub.com). {% comment %} https://github.com/github/github/pull/151987, https://github.com/github/github/pull/151713 {% endcomment %}' + - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/21852, https://github.com/github/enterprise2/pull/21828, https://github.com/github/enterprise2/pull/22153, https://github.com/github/enterprise2/pull/21920, https://github.com/github/enterprise2/pull/22215, https://github.com/github/enterprise2/pull/22190 {% endcomment %}' bugs: - - 'A message was not logged when the ghe-config-apply process had finished running ghe-es-auto-expand. {% comment %} https://github.com/github/enterprise2/pull/22177, https://github.com/github/enterprise2/pull/22171 {% endcomment %}' - - 'Excessive logging to the `syslog` file could occur on high-availability replicas if the primary appliance is unavailable. {% comment %} https://github.com/github/enterprise2/pull/22267, https://github.com/github/enterprise2/pull/22124 {% endcomment %}' - - "Database re-seeding on a replica could fail with an error: `Got packet bigger than 'max_allowed_packet'` {% comment %} https://github.com/github/enterprise2/pull/22321, https://github.com/github/enterprise2/pull/20063 {% endcomment %}" - - 'In some cases duplicate user data could cause a 500 error while running the ghe-license-usage script. {% comment %} https://github.com/github/github/pull/152638 {% endcomment %}' + - 'Uma mensagem não foi registrada quando o processo ghe-config-apply terminou de executar ghe-es-auto-expand. {% comment %} https://github.com/github/enterprise2/pull/22177, https://github.com/github/enterprise2/pull/22171 {% endcomment %}' + - 'O registro excessivo para o arquivo `syslog` pôde ocorrer em replicas de alta disponibilidade se o aplicativo primário não estiver disponível. {% comment %} https://github.com/github/enterprise2/pull/22267, https://github.com/github/enterprise2/pull/22124 {% endcomment %}' + - 'A redisseminação do banco de dados em uma réplica pode falhar com um erro: `Got packet bigger than ''max_allowed_packet''` {% comment %} https://github.com/github/enterprise2/pull/22321, https://github.com/github/enterprise2/pull/20063 {% endcomment %}' + - 'Em alguns casos, os dados do usuário duplicados podem gerar um erro 500 durante a execução do script ghe-license-use. {% comment %} https://github.com/github/github/pull/152638 {% endcomment %}' changes: - - 'In a high availability or geo-replication configuration, replica instances would exit maintenance mode when ghe-config-apply ran. {% comment %} https://github.com/github/enterprise2/pull/21776, https://github.com/github/enterprise2/pull/21440 {% endcomment %}' - - "We've added support for the R5a and R5n AWS instance types. {% comment %} https://github.com/github/enterprise2/pull/21902, https://github.com/github/enterprise2/pull/21173 {% endcomment %}" - - 'Removed the license seat count information on the administrative SSH MOTD due to a performance issue impacting GitHub Enterprise Server clusters. {% comment %} https://github.com/github/enterprise2/pull/21993, https://github.com/github/enterprise2/pull/21870 {% endcomment %}' + - 'Em uma alta disponibilidade ou configuração da replicação geográfica, instâncias de réplica sairiam do modo de manutenção quando o ghe-config-apply foi executado. {% comment %} https://github.com/github/enterprise2/pull/21776, https://github.com/github/enterprise2/pull/21440 {% endcomment %}' + - 'Adicionamos suporte para os tipos de instância R5a e R5n AWS. {% comment %} https://github.com/github/enterprise2/pull/21902, https://github.com/github/enterprise2/pull/21173 {% endcomment %}' + - 'Removeram-se as informações de contagem de estações da licença no MOTD administrativo de SSH devido a um problema de desempenho que afeta os clusters do GitHub Enterprise Server. {% comment %} https://github.com/github/enterprise2/pull/21993, https://github.com/github/enterprise2/pull/21870 {% endcomment %}' known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Em uma nova configuração do GitHub Enterprise Server sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Os alertas de segurança não são relatados ao fazer envio por push em um repositório na linha de comando. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Quando um nó de réplica está off-line em uma configuração de alta disponibilidade, {% data variables.product.product_name %} ainda pode encaminhar solicitações de {% data variables.product.prodname_pages %} para o nó off-line, reduzindo a disponibilidade de {% data variables.product.prodname_pages %} para os usuários.' diff --git a/translations/pt-BR/data/release-notes/enterprise-server/2-21/6.yml b/translations/pt-BR/data/release-notes/enterprise-server/2-21/6.yml index 03c71afb3a..be32ee7368 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/2-21/6.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/2-21/6.yml @@ -1,27 +1,26 @@ date: '2020-08-26' sections: security_fixes: - - >- - **CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2882, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700, - https://github.com/github/pages/pull/2889, https://github.com/github/pages/pull/2899, https://github.com/github/pages/pull/2903, https://github.com/github/pages/pull/2890, https://github.com/github/pages/pull/2891, https://github.com/github/pages/pull/2884 {% endcomment %} - - '**MEDIUM:** An improper access control vulnerability was identified that allowed authenticated users of the instance to determine the names of unauthorized private repositories given their numerical IDs. This vulnerability did not allow unauthorized access to any repository content besides the name. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.22 and has been assigned [CVE-2020-10517](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10517). The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/151986, https://github.com/github/github/pull/151713 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21853, https://github.com/github/enterprise2/pull/21828, https://github.com/github/enterprise2/pull/22154, https://github.com/github/enterprise2/pull/21920, https://github.com/github/enterprise2/pull/22216, https://github.com/github/enterprise2/pull/22190 {% endcomment %}' + - '**CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2882, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700, https://github.com/github/pages/pull/2889, https://github.com/github/pages/pull/2899, https://github.com/github/pages/pull/2903, https://github.com/github/pages/pull/2890, https://github.com/github/pages/pull/2891, https://github.com/github/pages/pull/2884 {% endcomment %}' + - '**MÉDIO:** Identificou-se uma vulnerabilidade de controle de acesso imprópria, que permitiu que usuários autenticados da instância determinassem os nomes de repositórios privados não autorizados dados seus IDs numéricos. Esta vulnerabilidade não permitiu o acesso não autorizado a qualquer conteúdo de repositórios além do nome. Esta vulnerabilidade afetou todas as versões do GitHub Enterprise Server anteriores à 2.22 e foi atribuído [CVE-2020-10517](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10517). A vulnerabilidade foi relatada por meio do [programa de GitHub Bug Bounty](https://bounty. ithub.com). {% comment %} https://github.com/github/github/pull/151986, https://github.com/github/github/pull/151713 {% endcomment %}' + - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/21853, https://github.com/github/enterprise2/pull/21828, https://github.com/github/enterprise2/pull/22154, https://github.com/github/enterprise2/pull/21920, https://github.com/github/enterprise2/pull/22216, https://github.com/github/enterprise2/pull/22190 {% endcomment %}' bugs: - - 'A message was not logged when the ghe-config-apply process had finished running ghe-es-auto-expand. {% comment %} https://github.com/github/enterprise2/pull/22178, https://github.com/github/enterprise2/pull/22171 {% endcomment %}' - - 'Excessive logging to the `syslog` file could occur on high-availability replicas if the primary appliance is unavailable. {% comment %} https://github.com/github/enterprise2/pull/22268, https://github.com/github/enterprise2/pull/22124 {% endcomment %}' - - "Database re-seeding on a replica could fail with an error: `Got packet bigger than 'max_allowed_packet'` {% comment %} https://github.com/github/enterprise2/pull/22322, https://github.com/github/enterprise2/pull/20063 {% endcomment %}" - - 'In some cases duplicate user data could cause a 500 error while running the ghe-license-usage script. {% comment %} https://github.com/github/github/pull/152637 {% endcomment %}' - - 'Using `ghe-migrator`, the `add` command would fail to lock a repository when using the `--lock` flag. {% comment %} https://github.com/github/github/pull/152780, https://github.com/github/github/pull/152588 {% endcomment %}' + - 'Uma mensagem não foi registrada quando o processo ghe-config-apply terminou de executar ghe-es-auto-expand. {% comment %} https://github.com/github/enterprise2/pull/22178, https://github.com/github/enterprise2/pull/22171 {% endcomment %}' + - 'O registro excessivo para o arquivo `syslog` pôde ocorrer em replicas de alta disponibilidade se o aplicativo primário não estiver disponível. {% comment %} https://github.com/github/enterprise2/pull/22268, https://github.com/github/enterprise2/pull/22124 {% endcomment %}' + - 'A redisseminação do banco de dados em uma réplica pode falhar com um erro: `Got packet bigger than ''max_allowed_packet''` {% comment %} https://github.com/github/enterprise2/pull/22322, https://github.com/github/enterprise2/pull/20063 {% endcomment %}' + - 'Em alguns casos, os dados do usuário duplicados podem gerar um erro 500 durante a execução do script ghe-license-use. {% comment %} https://github.com/github/github/pull/152637 {% endcomment %}' + - 'Ao usar `ghe-migrator`, o comando `adicionar` falharia ao bloquear um repositório usando o sinalizador `--lock`. {% comment %} https://github.com/github/github/pull/152780, https://github.com/github/github/pull/152588 {% endcomment %}' changes: - - 'In a high availability or geo-replication configuration, replica instances would exit maintenance mode when ghe-config-apply ran. {% comment %} https://github.com/github/enterprise2/pull/21777, https://github.com/github/enterprise2/pull/21440 {% endcomment %}' - - "We've added support for the R5a and R5n AWS instance types. {% comment %} https://github.com/github/enterprise2/pull/21903, https://github.com/github/enterprise2/pull/21173 {% endcomment %}" - - 'Removed the license seat count information on the administrative SSH MOTD due to a performance issue impacting GitHub Enterprise Server clusters. {% comment %} https://github.com/github/enterprise2/pull/21994, https://github.com/github/enterprise2/pull/21870 {% endcomment %}' + - 'Em uma alta disponibilidade ou configuração da replicação geográfica, instâncias de réplica sairiam do modo de manutenção quando o ghe-config-apply foi executado. {% comment %} https://github.com/github/enterprise2/pull/21777, https://github.com/github/enterprise2/pull/21440 {% endcomment %}' + - 'Adicionamos suporte para os tipos de instância R5a e R5n AWS. {% comment %} https://github.com/github/enterprise2/pull/21903, https://github.com/github/enterprise2/pull/21173 {% endcomment %}' + - 'Removeram-se as informações de contagem de estações da licença no MOTD administrativo de SSH devido a um problema de desempenho que afeta os clusters do GitHub Enterprise Server. {% comment %} https://github.com/github/enterprise2/pull/21994, https://github.com/github/enterprise2/pull/21870 {% endcomment %}' known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - "Configuring a repository's permission to `Triage` or `Maintain` fails with an error message." + - 'Em uma nova configuração do GitHub Enterprise Server sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - 'Os alertas de segurança não são relatados ao fazer envio por push em um repositório na linha de comando. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - 'Os logs de auditoria podem ser atribuídos a 127.0.0.1 ao invés do endereço IP de origem real. (atualizado 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' + - 'Ocorre uma falha na configuração da permissão de um repositório para "Triagem" ou "Manter" com uma mensagem de erro.' + - 'Quando um nó de réplica está off-line em uma configuração de alta disponibilidade, {% data variables.product.product_name %} ainda pode encaminhar solicitações de {% data variables.product.prodname_pages %} para o nó off-line, reduzindo a disponibilidade de {% data variables.product.prodname_pages %} para os usuários.' diff --git a/translations/pt-BR/data/release-notes/enterprise-server/2-22/22.yml b/translations/pt-BR/data/release-notes/enterprise-server/2-22/22.yml new file mode 100644 index 0000000000..deb79e3a8b --- /dev/null +++ b/translations/pt-BR/data/release-notes/enterprise-server/2-22/22.yml @@ -0,0 +1,15 @@ +--- +date: '2021-09-24' +sections: + security_fixes: + - '**HIGH:** A path traversal vulnerability was identified in {% data variables.product.prodname_ghe_server %} that could be exploited when building a {% data variables.product.prodname_pages %} site. User-controlled configuration options used by {% data variables.product.prodname_pages %} were not sufficiently restricted and made it possible to read files on the {% data variables.product.prodname_ghe_server %} instance. To exploit this vulnerability, an attacker would need 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.1.8 and was fixed in 3.1.8, 3.0.16, and 2.22.22. This is the result of an incomplete fix for CVE-2021-22867. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned CVE-2021-22868. {% comment %} https://github.com/github/pages/pull/3359, https://github.com/github/pages/pull/3357 {% endcomment %}' + bugs: + - 'The {% data variables.product.prodname_github_connect %} configuration of the source instance was always restored to new instances even when the `--config` option for `ghe-restore` was not used. This would lead to a conflict with the {% data variables.product.prodname_github_connect %} connection and license synchronization if both the source and destination instances were online at the same time. {% comment %} https://github.com/github/github/pull/192247, https://github.com/github/github/pull/191951, https://github.com/github/enterprise2/pull/26870, https://github.com/github/backup-utils/pull/770, https://github.com/github/connected-enterprise/issues/208 {% endcomment %}' + - 'Fixes {% data variables.product.prodname_pages %} builds so they take into account the NO_PROXY setting of the appliance. This is relevant to appliances configured with an HTTP proxy only. {% comment %} https://github.com/github/github/pull/192380 {% endcomment %}' + known_issues: + - Em uma nova configuração de {% data variables.product.prodname_ghe_server %} sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. + - As regras de firewall personalizadas são removidas durante o processo de atualização. + - Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta. + - Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório, onde o caminho do arquivo blob's é maior que 255 caracteres. + - 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 GitHub.com search results. + - Quando um nó de réplica está off-line em uma configuração de alta disponibilidade, {% data variables.product.product_name %} ainda pode encaminhar solicitações de {% data variables.product.prodname_pages %} para o nó off-line, reduzindo a disponibilidade de {% data variables.product.prodname_pages %} para os usuários. diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-0/16.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-0/16.yml new file mode 100644 index 0000000000..20d2adc065 --- /dev/null +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-0/16.yml @@ -0,0 +1,18 @@ +--- +date: '2021-09-24' +sections: + security_fixes: + - '**HIGH:** A path traversal vulnerability was identified in {% data variables.product.prodname_ghe_server %} that could be exploited when building a {% data variables.product.prodname_pages %} site. User-controlled configuration options used by {% data variables.product.prodname_pages %} were not sufficiently restricted and made it possible to read files on the {% data variables.product.prodname_ghe_server %} instance. To exploit this vulnerability, an attacker would need 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.1.8 and was fixed in 3.1.8, 3.0.16, and 2.22.22. This is the result of an incomplete fix for CVE-2021-22867. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned CVE-2021-22868. {% comment %} https://github.com/github/pages/pull/3360, https://github.com/github/pages/pull/3357 {% endcomment %}' + - '**MEDIUM:** An improper access control vulnerability in {% data variables.product.prodname_ghe_server %} allowed a workflow job to execute in a self-hosted runner group it should not have had access to. This affects customers using self-hosted runner groups for access control. A repository with access to one enterprise runner group could access all of the enterprise runner groups within the organization because of improper authentication checks during the request. This could cause code to be run unintentionally by the incorrect runner group. This vulnerability affected {% data variables.product.prodname_ghe_server %} versions from 3.0.0 to 3.0.15 and 3.1.0 to 3.1.7 and was fixed in 3.0.16 and 3.1.8 releases. It has been assigned CVE-2021-22869. {% comment %} https://github.com/github/enterprise2/pull/27003 {% endcomment %}' + bugs: + - 'Resque worker counts were displayed incorrectly during maintenance mode. {% comment %} https://github.com/github/enterprise2/pull/26898, https://github.com/github/enterprise2/pull/26883 {% endcomment %}' + - 'Allocated memcached memory could be zero in clustering mode. {% comment %} https://github.com/github/enterprise2/pull/26927, https://github.com/github/enterprise2/pull/26832 {% endcomment %}' + - 'Fixes {% data variables.product.prodname_pages %} builds so they take into account the NO_PROXY setting of the appliance. This is relevant to appliances configured with an HTTP proxy only. (update 2021-09-30) {% comment %} https://github.com/github/pages/pull/3360 {% endcomment %}' + known_issues: + - Em uma nova configuração de {% data variables.product.prodname_ghe_server %} sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. + - As regras de firewall personalizadas são removidas durante o processo de atualização. + - Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta. + - Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório, onde o caminho do arquivo blob's é maior que 255 caracteres. + - Quando "Usuários podem pesquisar pelo GitHub.com" está habilitado com o GitHub Connect, os problemas em repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. + - Quando um nó de réplica está off-line em uma configuração de alta disponibilidade, {% data variables.product.product_name %} ainda pode encaminhar solicitações de {% data variables.product.prodname_pages %} para o nó off-line, reduzindo a disponibilidade de {% data variables.product.prodname_pages %} para os usuários. + - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-1/8.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-1/8.yml new file mode 100644 index 0000000000..23c8f8c88b --- /dev/null +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-1/8.yml @@ -0,0 +1,20 @@ +--- +date: '2021-09-24' +sections: + security_fixes: + - '**HIGH:** A path traversal vulnerability was identified in {% data variables.product.prodname_ghe_server %} that could be exploited when building a {% data variables.product.prodname_pages %} site. User-controlled configuration options used by {% data variables.product.prodname_pages %} were not sufficiently restricted and made it possible to read files on the {% data variables.product.prodname_ghe_server %} instance. To exploit this vulnerability, an attacker would need 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.1.8 and was fixed in 3.1.8, 3.0.16, and 2.22.22. This is the result of an incomplete fix for CVE-2021-22867. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned CVE-2021-22868. {% comment %} https://github.com/github/pages/pull/3361, https://github.com/github/pages/pull/3357 {% endcomment %}' + - '**MEDIUM:** An improper access control vulnerability in {% data variables.product.prodname_ghe_server %} allowed a workflow job to execute in a self-hosted runner group it should not have had access to. This affects customers using self-hosted runner groups for access control. A repository with access to one enterprise runner group could access all of the enterprise runner groups within the organization because of improper authentication checks during the request. This could cause code to be run unintentionally by the incorrect runner group. This vulnerability affected {% data variables.product.prodname_ghe_server %} versions from 3.0.0 to 3.0.15 and 3.1.0 to 3.1.7 and was fixed in 3.0.16 and 3.1.8 releases. It has been assigned CVE-2021-22869. {% comment %} https://github.com/github/enterprise2/pull/27013 {% endcomment %}' + bugs: + - 'Resque worker counts were displayed incorrectly during maintenance mode. {% comment %} https://github.com/github/enterprise2/pull/26899, https://github.com/github/enterprise2/pull/26883 {% endcomment %}' + - 'Allocated memcached memory could be zero in clustering mode. {% comment %} https://github.com/github/enterprise2/pull/26928, https://github.com/github/enterprise2/pull/26832 {% endcomment %}' + - 'Non-empty binary files displayed an incorrect file type and size on the pull request "Files" tab. {% comment %} https://github.com/github/github/pull/192810, https://github.com/github/github/pull/172284, https://github.com/github/coding/issues/694 {% endcomment %}' + - 'Fixes {% data variables.product.prodname_pages %} builds so they take into account the NO_PROXY setting of the appliance. This is relevant to appliances configured with an HTTP proxy only. (update 2021-09-30) {% comment %} https://github.com/github/pages/pull/3360 {% endcomment %}' + known_issues: + - O registro npm de {% data variables.product.prodname_registry %} não retorna mais o valor de tempo em respostas de metadados. Isso foi feito para permitir melhorias substanciais de desempenho. Continuamos a ter todos os dados necessários para devolver um valor de tempo como parte da resposta aos metadados e retomaremos o retorno desse valor no futuro, assim que tivermos resolvido os problemas de desempenho existentes. + - Em uma nova configuração de {% data variables.product.prodname_ghe_server %} sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. + - As regras de firewall personalizadas são removidas durante o processo de atualização. + - Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta. + - Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório, onde o caminho do arquivo blob's é maior que 255 caracteres. + - Quando "Usuários podem pesquisar pelo GitHub.com" está habilitado com o GitHub Connect, os problemas em repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. + - 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/pt-BR/data/release-notes/enterprise-server/3-2/0-rc1.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-2/0-rc1.yml index 662223d9fd..491d00e416 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-2/0-rc1.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-2/0-rc1.yml @@ -1,7 +1,7 @@ --- date: '2021-09-09' release_candidate: true -deprecated: false +deprecated: true intro: Se {% data variables.product.product_location %} estiver executando a criação de um candidato a versão, você não pode fazer a atualização com um hotpatch. Recomendamos apenas executar candidatos em ambientes de teste. sections: features: diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-2/0.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-2/0.yml new file mode 100644 index 0000000000..c9b37174b3 --- /dev/null +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-2/0.yml @@ -0,0 +1,221 @@ +--- +date: '2021-09-28' +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: Custom patterns for secret scanning + notes: + - | + {% data variables.product.prodname_GH_advanced_security %} customers can now specify custom patterns for secret scanning. When a new pattern is specified, secret scanning searches a repository's entire Git history for the pattern, as well as any new commits. + + User defined patterns are in beta for {% data variables.product.prodname_ghe_server %} 3.2. They can be defined at the repository, organization, and enterprise levels. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." + - + heading: Security overview for Advanced Security (beta) + notes: + - | + {% data variables.product.prodname_GH_advanced_security %} customers now have an organization-level view of the application security risks detected by {% data variables.product.prodname_code_scanning %}, {% data variables.product.prodname_dependabot %}, and {% data variables.product.prodname_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 {% data variables.product.prodname_secret_scanning %} alerts at the organization level. Similar views for {% data variables.product.prodname_dependabot %} and {% data variables.product.prodname_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 review (beta) + notes: + - | + {% data variables.product.prodname_GH_advanced_security %} customers can now see a rich diff of the dependencies changed in a pull request. 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 these dependencies. 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)." + - + heading: GitHub Actions environments + notes: + - | + Environments, environment protection rules, and environment secrets are now generally available for {% data variables.product.prodname_actions %} on {% data variables.product.product_name %}. For more information, see "[Environments](/actions/reference/environments)." + + ![Environment protection rules](/assets/images/enterprise/3.2/release-notes/actions-environments.png) + - + heading: SSH authentication with security keys + notes: + - | + SSH authentication using a FIDO2 security key is now supported when you add a `sk-ecdsa-sha2-nistp256@openssh.com` or `sk-ssh-ed25519@openssh.com` SSH key to your account. SSH security keys store secret key material on a separate hardware device that requires verification, such as a tap, to operate. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)." + - + heading: 'Dark and dark dimmed themes' + notes: + - | + Dark and dark dimmed themes are now available for the web UI. {% data variables.product.product_name %} will match your system preferences when you haven't set theme preferences in {% data variables.product.product_name %}. You can also choose which themes are active during the day and night. For more information, see "[Managing your theme settings](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)." + + ![Dark and dark dimmed themes](https://user-images.githubusercontent.com/33528647/114629560-d2231f80-9c86-11eb-9bde-cc301a97040d.gif) + - + heading: 'Approving unverified domains for email notifications' + notes: + - 'Domains that are not able to be verified can now be approved for email notification routing. Enterprise and organization owners will be able to approve domains and immediately augment their email notification restriction policy, allowing notifications to be sent to collaborators, consultants, acquisitions, or other partners. For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#about-approval-of-domains)" and "[Restricting email notifications for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise#restricting-email-notifications-for-your-enterprise-account)."' + - + heading: 'Git Credential Manager (GCM) secure credential storage and multi-factor authentication support' + notes: + - | + Git Credential Manager (GCM) Core versions 2.0.452 and later now provide security-hardened credential storage and multi-factor authentication support for {% data variables.product.product_name %}. + + GCM Core with support for {% data variables.product.product_name %} is included with [Git for Windows](https://gitforwindows.org) versions 2.32 and later. GCM Core is not included with Git for macOS or Linux, but can be installed separately. For more information, see the [latest release](https://github.com/microsoft/Git-Credential-Manager-Core/releases/) and [installation instructions](https://github.com/microsoft/Git-Credential-Manager-Core/releases/) in the `microsoft/Git-Credential-Manager-Core` repository. + changes: + - + heading: Alterações na administração + notes: + - A 'User Agent Referrer Policy' setting has been added to the enterprise settings. This allows an admin to set a stricter `Referrer-Policy` to hide the hostname of a {% data variables.product.prodname_ghe_server %} installation from external sites. The setting is disabled by default and is tracked by audit log events for staff and enterprise owners when enabled or disabled. For more information, see "[Configuring Referrer Policy for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)." + - The MySQL health check was changed to use `mysqladmin ping` instead of TCP checks, which removes some unnecessary noise in the MySQL error log. Also, Orchestrator failover checks were improved to prevent unnecessary MySQL failovers when applying cluster config changes. + - 'The Resque service, which supports background job processing, has been replaced with Aqueduct Lite. This change makes the job system easier to manage and should not affect the user experience. For the new administration and debugging commands for Aqueduct, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-aqueduct)."' + - + heading: Token Changes + notes: + - | + The format of authentication tokens for {% data variables.product.product_name %} has changed. The change affects the format of personal access tokens and access tokens for {% data variables.product.prodname_oauth_apps %}, as well as user-to-server, server-to-server, and refresh tokens for {% data variables.product.prodname_github_apps %}. + + The different token types now have unique identifiable prefixes, which allows for secret scanning to detect the tokens so that you can mitigate the impact of someone accidentally committing a token to a repository. {% data variables.product.company_short %} recommends updating existing tokens as soon as possible. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github#githubs-token-formats)" and "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)." + - + heading: 'Repositories changes' + notes: + - Repositories on user profiles and organization profiles now support sorting by star count. + - When viewing the commit history of a single file, you can now click {% octicon "file-code" aria-label="The code icon" %} to view that file at the selected point in history. + - When a submodule is defined with a relative path in {% data variables.product.product_location %}, the submodule is now clickable in the web UI. Clicking the submodule in the web UI will take you to the linked repository. Previously, only submodules with absolute URLs were clickable. This is supported for relative paths for repositories with the same owner that follow the pattern ../REPOSITORY or relative paths for repositories with a different owner that follow the pattern ../OWNER/REPOSITORY. For more information about working with submodules, see [Working with submodules](https://github.blog/2016-02-01-working-with-submodules/) on {% data variables.product.prodname_blog %}. + - 'The web UI can now be used to synchronize an out-of-date branch of a fork with the fork''s upstream branch. If there are no merge conflicts between the branches, the branch is updated either by fast-forwarding or by merging from upstream. If there are conflicts, you will be prompted to create a pull request to resolve the conflicts. For more information, see "[Syncing a fork](/github/collaborating-with-pull-requests/working-with-forks/syncing-a-fork#syncing-a-fork-from-the-web-ui)."' + - + heading: 'Markdown changes' + notes: + - 'The markdown editor used when creating or editing a release in a repository now has a text-editing toolbar. For more information, see "[Managing releases in a repository](/github/administering-a-repository/releasing-projects-on-github/managing-releases-in-a-repository#creating-a-release)."' + - Uploading video files is now supported everywhere you write Markdown on {% data variables.product.product_name %}. Share demos, reproduction steps, and more in your issue and pull request comments, as well as in Markdown files within repositories, such as READMEs. For more information, see "[Attaching files](/github/writing-on-github/working-with-advanced-formatting/attaching-files)." + - Markdown files will now automatically generate a table of contents in the header when there are 2 or more headings. The table of contents is interactive and links to the selected section. All 6 Markdown heading levels are supported. + - 'There is a new keyboard shortcut, `cmd+e` on macOS or `ctrl+e` on Windows, to insert codeblocks in Markdown files, issues, pull requests, and comments.' + - 'Appending `?plain=1` to the URL for any Markdown file will now display the file without rendering and with line numbers. The plain view can be used to link other users to specific lines. For example, appending `?plain=1#L52` will highlight line 52 of a plain text Markdown file. For more information, "[Creating a permanent link to a code snippet](/github/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet#linking-to-markdown)."' + - + heading: 'Issues and pull requests changes' + notes: + - With the [latest version of Octicons](https://github.com/primer/octicons/releases), the states of issues and pull requests are now more visually distinct so you can scan their status more easily. For more information, see [{% data variables.product.prodname_blog %}](https://github.blog/changelog/2021-06-08-new-issue-and-pull-request-state-icons/). + - 'A new "Require conversation resolution before merging" branch protection rule and "Conversations" menu is now available. Easily discover your pull request comments from the "Files changed" tab, and require that all your pull request conversations are resolved before merging. For more information, see "[About pull request reviews](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews#discovering-and-navigating-conversations)" and "[About protected branches](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-conversation-resolution-before-merging)."' + - To prevent the merge of unexpected changes after auto-merge is enabled for a pull request, auto-merge is now disabled automatically when new changes are pushed by a user without write access to the repository. Users without write access can still update the pull request with changes from the base branch when auto-merge is enabled. To prevent a malicious user from using a merge conflict to introduce unexpected changes to the pull request, auto-merge for the pull request is disabled if the update causes a merge conflict. For more information about auto-merge, see "[Automatically merging a pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." + - 'People with maintain permissions 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 permissions 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. + - When a review is requested from a team of more than 100 people, developers are now shown a confirmation dialog box in order to prevent unnecessary notifications for large teams. + - Back-tick `code blocks` are now supported in issue titles, pull request titles, and in any place issue and pull request titles are referenced in {% data variables.product.prodname_ghe_server %}. + - 'Events for pull requests and pull request reviews are now included in the audit log for both [enterprises](/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise) and [organizations](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization). These events help admins better monitor pull request activity and help ensure security and compliance requirements are being met. Events can be viewed from the web UI, exported as CSV or JSON, or accessed via REST API. You can also search the audit log for specific pull request events. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#pull_request-category-actions)."' + - + heading: 'Branches changes' + notes: + - | + The default branch name for new repositories is now `main`. Existing repositories are not impacted by this change. If users, organization owners, or enterprise owners have previously specified a default branch for new repositories, they are also not impacted. + + If you want to set a different default branch name, you can do so in the [user](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories), [organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization), or [enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name) settings. + - | + Branches, including the default branch, can now be renamed using the the {% data variables.product.product_name %} web UI. When a branch is renamed, any open pull requests and draft releases targeting the renamed branch will be retargeted automatically, and branch protection rules that explicitly reference the renamed branch will be updated. + + Admin permissions are required to rename the default branch, but write permissions are sufficient to rename other branches. + + To help make the change as seamless as possible for users: + + * A notice is shown to contributors, maintainers, and admins on the repository homepage with instructions for updating their local repository. + * Web requests to the old branch will be redirected. + * A "moved permanently" HTTP response will be returned to REST API calls. + * An informational message is displayed to Git command line users that push to the old branch. + + For more information, see "[Renaming a branch](/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch)." + - + heading: 'GitHub Actions changes' + notes: + - '{% data variables.product.prodname_actions %} now lets you control the permissions granted to the `GITHUB_TOKEN` secret. The `GITHUB_TOKEN` is an automatically-generated secret that lets you make authenticated calls to the API for {% data variables.product.product_name %} in your workflow runs. {% data variables.product.prodname_actions %} generates a new token for each job and expires the token when a job completes. The token usually has `write` permissions to a number of [API endpoints](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token), except in the case of pull requests from forks, which are always `read`. These new settings allow you to follow a principle of least privilege in your workflows. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token)."' + - '{% data variables.product.prodname_cli %} 1.9 and later allows you to work with {% data variables.product.prodname_actions %} in your terminal. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-04-15-github-cli-1-9-enables-you-to-work-with-github-actions-from-your-terminal/).' + - 'The audit log now includes events associated with {% data variables.product.prodname_actions %} workflow runs. This data provides administrators with a greatly expanded data set for security and compliance audits. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#workflows-category-actions)."' + - '{% data variables.product.prodname_ghe_server %} 3.2 contains performance improvements for job concurrency with {% data variables.product.prodname_actions %}. For more information on the new performance targets on 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)."' + - + heading: 'GitHub Packages changes' + notes: + - Any package or package version for {% data variables.product.prodname_registry %} can now be deleted from {% data variables.product.product_name %}'s web UI. You can also undo the deletion of any package or package version within 30 days. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)". + - + heading: 'Dependabot and Dependency graph changes' + notes: + - 'The dependency graph can now be enabled using the Management Console, rather than needing to run a command in the administrative shell. For more information, see "[Enabling alerts for vulnerable dependencies {% data variables.product.prodname_ghe_server %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server#enabling-the-dependency-graph-and-dependabot-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."' + - Notifications for multiple {% data variables.product.prodname_dependabot_alerts %} are now grouped together if they're discovered at the same time. This significantly reduces the volume of {% data variables.product.prodname_dependabot %} alert notifications that users receive. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-03-18-grouped-dependabot-alert-notifications/). + - 'Dependency graph and {% data variables.product.prodname_dependabot_alerts %} now support Go modules. {% data variables.product.prodname_ghe_server %} analyzes a repository''s `go.mod` files to understand the repository’s dependencies. Along with security advisories, the dependency graph provides the information needed to alert developers to vulnerable dependencies. For more information about enabling the dependency graph on private repositories, see "[Securing your repository](/code-security/getting-started/securing-your-repository#managing-the-dependency-graph)."' + - The default notification settings for security alerts have changed. Previously, if you had permission to view security alerts in a repository, you would receive notifications for that repository as long as your settings allowed for security alert notifications. Now, you must opt in to security alert notifications by watching the repository. You will be notified if you select `All Activity` or configure `Custom` to include `Security alerts`. All existing repositories will be automatically migrated to these new settings and you will continue to receive notifications; however, any new repositories will require opting-in by watching the repository. 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)" and "[Managing alerts from secret scanning](/code-security/secret-security/managing-alerts-from-secret-scanning)." + - + heading: 'Code scanning and secret scanning changes' + notes: + - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} now generates diagnostic information for all supported languages. This helps check the state of the created database to understand the status and quality of performed analysis. The diagnostic information is available starting in [version 2.5.6](https://github.com/github/codeql-cli-binaries/releases) of the [{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/). You can see the detailed diagnostic information in the {% data variables.product.prodname_actions %} logs for {% data variables.product.prodname_codeql %}. For more information, see "[Viewing code scanning logs](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs)."' + - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql_cli %} now supports analyzing several languages during a single build. This makes it easier to run code analysis to use CI/CD systems other than {% data variables.product.prodname_actions %}. The new mode of the `codeql database create` command is available starting [version 2.5.6](https://github.com/github/codeql-cli-binaries/releases) of the [{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/). For more information about setting this up, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-cli-in-your-ci-system)."' + - '{% data variables.product.prodname_code_scanning_capc %} alerts from all enabled tools are now shown in one consolidated list, so that you can easily prioritize across all alerts. You can view alerts from a specific tool by using the "Tool" filter, and the "Rule" and "Tag" filters will dynamically update based on your "Tool" selection.' + - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} now includes beta support for analyzing C++20 code. This is only available when building codebases with GCC on Linux. C++20 modules are not supported yet.' + - 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 for several languages ([C++](https://github.com/github/codeql/tree/main/cpp), [JavaScript](https://github.com/github/codeql/tree/main/javascript), [Python](https://github.com/github/codeql/tree/main/python), and [Java](https://github.com/github/codeql/tree/main/java)). As a result, {% data variables.product.prodname_codeql %} can now detect even more potential sources of untrusted user data, review the steps through which that data flows, and identify potentially dangerous sinks in which this data could end up. This results in an overall improvement of the quality of the {% data variables.product.prodname_code_scanning %} alerts. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-07-01-codeql-code-scanning-now-recognizes-more-sources-and-uses-of-untrusted-user-data/). + - | + {% data variables.product.prodname_code_scanning_capc %} now shows `security-severity` levels for CodeQL security alerts. You can configure which `security-severity` levels will cause a check failure for a pull request. The severity level of security alerts can be `critical`, `high`, `medium`, or `low`. By default, any {% data variables.product.prodname_code_scanning %} alerts with a `security-severity` of `critical` or `high` will cause a pull request check failure. + + Additionally, you can now also configure which severity levels will cause a pull request check to fail for non-security alerts. You can configure this behavior at the repository level, and define whether alerts with the severity `error`, `warning`, or `note` will cause a pull request check to fail. By default, non-security {% data variables.product.prodname_code_scanning %} alerts with a severity of `error` will cause a pull request check failure. + + For more information see "[Defining which alert severity levels cause pull request check failure](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)." + + ![List of code scanning alerts with security levels](/assets/images/enterprise/3.2/release-notes/code-scanning-alerts.png) + - | + Improvements to the branch filter for {% data variables.product.prodname_code_scanning %} alerts make it clearer which {% data variables.product.prodname_code_scanning %} alerts are being displayed on the alerts page. By default, {% data variables.product.prodname_code_scanning %} alerts are filtered to show alerts for the default branch of the repository only. You can use the branch filter to display the alerts on any of the non-default branches. Any branch filter that has been applied is shown in the search bar. + + The search syntax has also been simplified to `branch:`. This syntax can be used multiple times in the search bar to filter on multiple branches. The previous syntax, `ref:refs/heads/`, is still supported, so any saved URLs will continue to work. + - | + Free text search is now available for code scanning alerts. You can search code scanning results to quickly find specific alerts without having to know exact search terms. The search is applied across the alert's name, description, and help text. The syntax is: + + - A single word returns all matches. + - Multiple search words returns matches to either word. + - Words in double quotes returns exact matches. + - The keyword 'AND' returns matches to multiple words. + - '{% data variables.product.prodname_secret_scanning_caps %} added patterns for 23 new service providers. For the updated list of supported secrets, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning)."' + - + heading: Alterações de API + notes: + - 'Pagination support has been added to the Repositories REST API''s "compare two commits" endpoint, which returns a list of commits reachable from one commit or branch, but unreachable from another. The API can also now return the results for comparisons over 250 commits. For more information, see the "[Repositories](/rest/reference/repos#compare-two-commits)" REST API documentation and "[Traversing with pagination](/rest/guides/traversing-with-pagination)."' + - 'The REST API can now be used to programmatically resend or check the status of webhooks. For more information, see "[Repositories](/rest/reference/repos#webhooks)," "[Organizations](/rest/reference/orgs#webhooks)," and "[Apps](/rest/reference/apps#webhooks)" in the REST API documentation.' + - | + Improvements have been made to the code scanning and {% data variables.product.prodname_GH_advanced_security %} APIs: + + - The code scanning API now returns the CodeQL query version used for an analysis. This can be used to reproduce results or confirm that an analysis used the latest query. For more information, see "[Code scanning](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository)" in the REST API documentation. + - Admin users can now use the REST API to enable or disable {% data variables.product.prodname_GH_advanced_security %} for repositories, using the `security_and_analysis` object on `repos/{org}/{repo}`. In addition, admin users can check whether {% data variables.product.prodname_advanced_security %} is currently enabled for a repository by using a `GET /repos/{owner}/{repo}` request. These changes help you manage {% data variables.product.prodname_advanced_security %} repository access at scale. For more information, see "[Repositories](/rest/reference/repos#update-a-repository)" in the REST API documentation. + #No security/bug fixes for the RC release + #security_fixes: + #- PLACEHOLDER + #bugs: + #- PLACEHOLDER + known_issues: + - Em uma nova configuração de {% data variables.product.prodname_ghe_server %} sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. + - As regras de firewall personalizadas são removidas durante o processo de atualização. + - Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta. + - Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório, onde o caminho do arquivo blob's é maior que 255 caracteres. + - Quando "Usuários podem pesquisar pelo GitHub.com" está habilitado com o GitHub Connect, os problemas em repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. + - O registro npm de {% data variables.product.prodname_registry %} não retorna mais o valor de tempo em respostas de metadados. Isso foi feito para permitir melhorias substanciais de desempenho. Continuamos a ter todos os dados necessários para devolver um valor de tempo como parte da resposta aos metadados e retomaremos o retorno desse valor no futuro, assim que tivermos resolvido os problemas de desempenho existentes. + - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. + deprecations: + - + heading: Obsoletização do GitHub Enterprise Server 2.21 + notes: + - '**{% data variables.product.prodname_ghe_server %} 2.21 was discontinued on June 6, 2021**. That 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.2/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' + - + heading: Deprecation of GitHub Enterprise Server 2.22 + notes: + - '**{% data variables.product.prodname_ghe_server %} 2.22 will be discontinued on September 23, 2021**. That 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.2/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' + - + heading: Obsolescência do suporte para Hypervisor XenServer + notes: + - Beginning in {% data variables.product.prodname_ghe_server %} 3.1, we will begin discontinuing support for Xen Hypervisor. The complete deprecation is scheduled for {% data variables.product.prodname_ghe_server %} 3.3, following the standard one year deprecation window. Please contact [GitHub Support](https://enterprise.githubsupport.com/hc/en-us/signin) with questions or concerns. + - + heading: Removal of Legacy GitHub Services + notes: + - '{% data variables.product.prodname_ghe_server %} 3.2 removes unused GitHub Service database records. More information is available in the [deprecation announcement post](https://developer.github.com/changes/2018-04-25-github-services-deprecation/).' + - + heading: Deprecation of OAuth Application API endpoints and API authentication via query parameters + notes: + - | + To prevent accidental logging or exposure of `access_tokens`, we discourage the use of OAuth Application API endpoints and the use of API auth via query params. Visit the following posts to see the proposed replacements: + + * [Replacement OAuth Application API endpoints](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#changes-to-make) + * [Replacement auth via headers instead of query param](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make) + + These endpoints and auth route are planned to be removed from {% data variables.product.prodname_ghe_server %} in {% data variables.product.prodname_ghe_server %} 3.4. + - + heading: Removal of legacy GitHub App webhook events and endpoints + notes: + - | + Two legacy GitHub Apps-related webhook events have been removed: `integration_installation` and `integration_installation_repositories`. You should instead be listening to the `installation` and `installation_repositories` events. + - | + The following REST API endpoint has been removed: `POST /installations/{installation_id}/access_tokens`. You should instead be using the namespaced equivalent `POST /app/installations/{installation_id}/access_tokens`. + backups: + - '{% data variables.product.prodname_ghe_server %} 3.2 requires at least [GitHub Enterprise Backup Utilities 3.2.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/enterprise-server@3.2/admin/configuration/configuring-backups-on-your-appliance).' diff --git a/translations/pt-BR/data/reusables/actions/about-environments.md b/translations/pt-BR/data/reusables/actions/about-environments.md new file mode 100644 index 0000000000..d09e7b0aa0 --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/about-environments.md @@ -0,0 +1 @@ +Os ambientes são usados para descrever um alvo geral de implantação como `produção`, `preparo` ou `desenvolvimento`. Quando um fluxo de trabalho de {% data variables.product.prodname_actions %} é implantado em um ambiente, o ambiente é exibido na página principal do repositório. You can use environments to require approval for a job to proceed, restrict which branches can trigger a workflow, or limit access to secrets. For more information about creating environments, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/actions/actions-audit-events-for-enterprise.md b/translations/pt-BR/data/reusables/actions/actions-audit-events-for-enterprise.md index 96b77e9259..62c1b0aef9 100644 --- a/translations/pt-BR/data/reusables/actions/actions-audit-events-for-enterprise.md +++ b/translations/pt-BR/data/reusables/actions/actions-audit-events-for-enterprise.md @@ -1,16 +1,16 @@ -| Ação | Descrição | -| -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `remove_self_hosted_runner` | Acionada quando um executor auto-hospedado é removido. | -| `register_self_hosted_runner` | Acionada quando um novo executor auto-hospedado é registrado. Para obter mais informações, consulte "[Adicionando executores auto-hospedados](/actions/hosting-your-own-runners/adding-self-hosted-runners)". | -| `runner_group_created` | Acionada quando um grupo de executores auto-hospedado é criado. Para obter mais informações, consulte "[Sobre grupos de executores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#about-self-hosted-runner-groups). | +| Ação | Descrição | +| -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `remove_self_hosted_runner` | Acionada quando um executor auto-hospedado é removido. | +| `register_self_hosted_runner` | Acionada quando um novo executor auto-hospedado é registrado. Para obter mais informações, consulte "[Adicionando executores auto-hospedados](/actions/hosting-your-own-runners/adding-self-hosted-runners)". | +| `runner_group_created` | Acionada quando um grupo de executores auto-hospedado é criado. Para obter mais informações, consulte "[Sobre grupos de executores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#about-self-hosted-runner-groups). | | `runner_group_removed` | Acionada quando um grupo de executores auto-hospedados é removido. For more information, see "[Removing a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)."{% ifversion ghes = 2.22 %} -| `runner_group_renamed` | Triggered when the self-hosted runner group is renamed. | -| `runner_group_visiblity_updated` | Triggered when the visibility settings of the self-hosted runner group are changed.{% endif %} -| `runner_group_runner_removed` | Acionada quando a API REST é usada para remover um executor auto-hospedado de um grupo. | -| `runner_group_runners_added` | Acionada quando um executor auto-hospedado é adicionado a um grupo. Para obter mais informações, consulte "[Mover um executorauto-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)". | +| `runner_group_renamed` | Acionada quando o grupo do executor auto-hospedado é renomeado. | +| `runner_group_visiblity_updated` | Acionada quando as configurações de visibilidade do grupo do executor auto-hospedado são alteradas.{% endif %} +| `runner_group_runner_removed` | Acionada quando a API REST é usada para remover um executor auto-hospedado de um grupo. | +| `runner_group_runners_added` | Acionada quando um executor auto-hospedado é adicionado a um grupo. Para obter mais informações, consulte "[Mover um executorauto-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)". | | `runner_group_runners_updated` | Acionada quando a lista de integrantes do grupo de executor é 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 ghes > 2.22 or ghae %} -| `runner_group_updated` | Acionada quando a configuração de um grupo de executor auto-hospedado é alterada. For more information, see "[Changing the access policy of a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)."{% endif %} +| `runner_group_updated` | Acionada quando a configuração de um grupo de executor auto-hospedado é alterada. Para obter mais informações, consulte "[Alterar a política de acesso de um grupo de executor auto-hospedado](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)".{% endif %} | `self_hosted_runner_updated` | Acionada quando o executor é 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 executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."{% ifversion fpt %} -| `self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." | -| `self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %} +| `self_hosted_runner_online` | Acionada quando o aplicativo do executor é 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)". | +| `self_hosted_runner_offline` | Acionada quando o aplicativo do executor é 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 %} diff --git a/translations/pt-BR/data/reusables/actions/actions-group-concurrency.md b/translations/pt-BR/data/reusables/actions/actions-group-concurrency.md index ad26bd1093..70ceb56558 100644 --- a/translations/pt-BR/data/reusables/actions/actions-group-concurrency.md +++ b/translations/pt-BR/data/reusables/actions/actions-group-concurrency.md @@ -1,6 +1,6 @@ Quando um trabalho simultâneo ou fluxo de trabalho é enfileirado, se outro trbalho ou fluxo de trabalho que usa o mesmo grupo de concorrência no repositório estiver em andamento o trabalho na fila ou o fluxo de trabalho ficará `pendente`. Qualquer trabalho ou fluxo de trabalho anterior pendente no grupo de concorrência será cancelado. Para cancelar também qualquer trabalho atualmente em execução ou fluxo de trabalho no mesmo grupo de concorrência, especifique `cancel-in-progress: true`. -### Exemplos: Como usar a concorrência e o comportamento padrão +## Exemplos: Como usar a concorrência e o comportamento padrão {% raw %} ```yaml @@ -14,7 +14,7 @@ concurrency: ci-${{ github.ref }} ``` {% endraw %} -### Exemplo: Usar a concorrência para cancelar qualquer trabalho em andamento ou em execução +## Exemplo: Usar a concorrência para cancelar qualquer trabalho em andamento ou em execução {% raw %} ```yaml diff --git a/translations/pt-BR/data/reusables/actions/ae-hosted-runners-beta.md b/translations/pt-BR/data/reusables/actions/ae-hosted-runners-beta.md new file mode 100644 index 0000000000..804f22a849 --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/ae-hosted-runners-beta.md @@ -0,0 +1,7 @@ +{% ifversion ghae %} +{% note %} + +**Note:** {% data variables.actions.hosted_runner %}s are currently in beta and subject to change. + +{% endnote %} +{% endif %} diff --git a/translations/pt-BR/data/reusables/actions/ae-self-hosted-runners-notice.md b/translations/pt-BR/data/reusables/actions/ae-self-hosted-runners-notice.md index 28458a30d1..a806e70e2c 100644 --- a/translations/pt-BR/data/reusables/actions/ae-self-hosted-runners-notice.md +++ b/translations/pt-BR/data/reusables/actions/ae-self-hosted-runners-notice.md @@ -1,9 +1,19 @@ {% ifversion ghae %} + {% warning %} -** Aviso:** Os executores auto-hospedados estão desabilitados para {% data variables.product.prodname_ghe_managed %}. Isso porque {% data variables.product.prodname_ghe_managed %} oferece garantias para as fronteiras de segurança que são incompatíveis com a forma como os executores hospedados funcionam. No entanto, se você precisar usar executores auto-hospedados com {% data variables.product.prodname_ghe_managed %} e entender as implicações de segurança, você poderá entrar em contato com o suporte de {% data variables.product.prodname_dotcom %} para uma exceção de segurança que irá habilitar executores auto-hospedados. +{% ifversion ghae-next %} + +**Warning:** Self-hosted runners are enabled by default for {% data variables.product.prodname_ghe_managed %}. Self-hosted runners are long-lived, and any compromise to the host machine could leak secrets or credentials or enable other attacks. If you'd like to disable self-hosted runners for your enterprise, you can contact {% data variables.product.prodname_dotcom %} support. For more information about the risks of using self-hosted runners, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/security-hardening-for-github-actions#potential-impact-of-a-compromised-runner)." + +{% elsif ghae %} + +**Warning:** Self-hosted runners are currently disabled for {% data variables.product.prodname_ghe_managed %}. Isso porque {% data variables.product.prodname_ghe_managed %} oferece garantias para as fronteiras de segurança que são incompatíveis com a forma como os executores hospedados funcionam. No entanto, se você precisar usar executores auto-hospedados com {% data variables.product.prodname_ghe_managed %} e entender as implicações de segurança, você poderá entrar em contato com o suporte de {% data variables.product.prodname_dotcom %} para uma exceção de segurança que irá habilitar executores auto-hospedados. Se você não precisar de executores auto-hospedados, você poderá usar {% data variables.actions.hosted_runner %}s para executar seus fluxos de trabalho. Para obter mais informações, consulte "[Sobre {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/about-ae-hosted-runners)". -{% endwarning %} +{% endif %} + +{% endwarning %} + {% endif %} 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 9b1daf03f8..0f5473e854 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 @@ -1,7 +1,7 @@ Quando você escolher **Permitir selecionar ações**, ações locais são permitidas, e há opções adicionais para permitir outras ações específicas: -- **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. As ações criadas por {% data variables.product.prodname_dotcom %} estão localizadas nas `ações` e nas organizações do `github`. For more information, see the [`actions`](https://github.com/actions) and [`github`](https://github.com/github) organizations.{% ifversion fpt or ghes > 3.0 %} -- **Allow Marketplace actions by verified creators:** {% ifversion ghes > 3.0 %}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 %} +- **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. 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 > 3.0 or ghae-issue-5094 %} +- **Allow Marketplace actions by verified creators:** {% ifversion ghes > 3.0 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 %} - **Permitir ações específicas:** Você pode restringir fluxos de trabalho para usar ações em organizações específicas e em repositórios. Para restringir o acesso a tags específicas ou commit SHAs de uma ação, use a mesma sintaxe `/@` usada no fluxo de trabalho para selecionar a ação. Por exemplo, `actions/javascript-action@v1.0.1` para selecionar uma tag ou `actions/javascript-action@172239021f7ba04fe7327647b213799853a9eb89` para selecionar um SHA. Para obter mais informações, consulte "[Localizar e personalizar ações](/actions/learn-github-actions/finding-and-customizing-actions#using-release-management-for-your-custom-actions)". diff --git a/translations/pt-BR/data/reusables/actions/autoscaling-parameters.md b/translations/pt-BR/data/reusables/actions/autoscaling-parameters.md new file mode 100644 index 0000000000..d9c4342b29 --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/autoscaling-parameters.md @@ -0,0 +1,3 @@ +- Optionally, autoscaling parameters for each pool. + - Minimum number of idle runners for the pool + - Active timeout: The number of minutes that a runner should remain active in the pool before the pool is reduced to the idle count diff --git a/translations/pt-BR/data/reusables/actions/cd-templates-actions.md b/translations/pt-BR/data/reusables/actions/cd-templates-actions.md new file mode 100644 index 0000000000..c6eeec90db --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/cd-templates-actions.md @@ -0,0 +1,3 @@ +{% data variables.product.product_name %} offers CD workflow templates for several popular services, such as Azure Web App. To learn how to get started using a workflow template, see "[Using workflow templates](/actions/learn-github-actions/using-workflow-templates)" or [browse the full list of deployment workflow templates](https://github.com/actions/starter-workflows/tree/main/deployments). You can also check out our more detailed guides for specific deployment workflows, such as "[Deploying to Azure App Service](/actions/deployment/deploying-to-azure-app-service)." + +Many service providers also offer actions on {% data variables.product.prodname_marketplace %} for deploying to their service. For the full list, see [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?category=deployment&type=actions). \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/actions/delete-env-key.md b/translations/pt-BR/data/reusables/actions/delete-env-key.md new file mode 100644 index 0000000000..380ebe5653 --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/delete-env-key.md @@ -0,0 +1 @@ +If you configured a deployment environment, change the value of `environment` to be the name of your environment. If you did not configure an environment{% ifversion fpt %} or if your workflow is in a private repository and you do not use {% data variables.product.prodname_ghe_cloud %}{% endif %}, delete the `environment` key. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/actions/environment-deployment-event.md b/translations/pt-BR/data/reusables/actions/environment-deployment-event.md new file mode 100644 index 0000000000..1a014fbfc6 --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/environment-deployment-event.md @@ -0,0 +1 @@ +When a workflow job that references an environment runs, it creates a deployment object with the `environment` property set to the name of your environment. As the workflow progresses, it also creates deployment status objects with the `environment` property set to the name of your environment, the `environment_url` property set to the URL for environment (if specified in the workflow), and the `state` property set to the status of the job. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/actions/environment-example.md b/translations/pt-BR/data/reusables/actions/environment-example.md new file mode 100644 index 0000000000..95ed6bc816 --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/environment-example.md @@ -0,0 +1,45 @@ +You can specify an environment for each job in your workflow. To do so, add a `jobs..environment` key followed by the name of the environment. + +For example, this workflow will use an environment called `production`. + +```yaml +name: Deployment + +on: + push: + branches: + - main + +jobs: + deployment: + runs-on: ubuntu-latest + environment: production + steps: + - name: deploy + # ...deployment-specific steps +``` + +When the above workflow runs, the `deployment` job will be subject to any rules configured for the `production` environment. For example, if the environment requires reviewers, the job will pause until one of the reviewers approves the job. + +You can also specify a URL for the environment. The specified URL will appear on the deployments page for the repository (accessed by clicking **Environments** on the home page of your repository) and in the visualization graph for the workflow run. If a pull request triggered the workflow, the URL is also displayed as a **View deployment** button in the pull request timeline. + +```yaml +name: Deployment + +on: + push: + branches: + - main + +jobs: + deployment: + runs-on: ubuntu-latest + environment: + name: production + url: https://github.com + steps: + - name: deploy + # ...deployment-specific steps +``` + +![Workflow graph with URL](/assets/images/help/images/deploy-graph.png) \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/actions/reusable-workflow-artifacts.md b/translations/pt-BR/data/reusables/actions/reusable-workflow-artifacts.md new file mode 100644 index 0000000000..4f5210333f --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/reusable-workflow-artifacts.md @@ -0,0 +1,3 @@ +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +All actions and workflows called within a run have write access to that run's artifacts. +{% endif %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/actions/reusable-workflows.md b/translations/pt-BR/data/reusables/actions/reusable-workflows.md new file mode 100644 index 0000000000..c50bbe452b --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/reusable-workflows.md @@ -0,0 +1,5 @@ +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## Reutilizando fluxos de trabalho + +You can call one workflow from within another workflow. This allows you to reuse workflows, avoiding duplication and making your workflows easier to maintain. Para obter mais informações, consulte "[Reutilizando fluxos de trabalho](/actions/learn-github-actions/reusing-workflows)". +{% endif %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/actions/runner-name-description.md b/translations/pt-BR/data/reusables/actions/runner-name-description.md new file mode 100644 index 0000000000..c3955e46ec --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/runner-name-description.md @@ -0,0 +1 @@ +The name of the runner executing the job. diff --git a/translations/pt-BR/data/reusables/actions/uses-keyword-example.md b/translations/pt-BR/data/reusables/actions/uses-keyword-example.md new file mode 100644 index 0000000000..fac21c8a9f --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/uses-keyword-example.md @@ -0,0 +1,7 @@ +```yaml +jobs: + call-workflow-1: + uses: octo-org/this-repo/.github/workflows/workflow-1.yml@172239021f7ba04fe7327647b213799853a9eb89 + call-workflow-2: + uses: octo-org/another-repo/.github/workflows/workflow-2.yml@v1 +``` \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/actions/workflow-organization-templates.md b/translations/pt-BR/data/reusables/actions/workflow-organization-templates.md new file mode 100644 index 0000000000..d8856aeab6 --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/workflow-organization-templates.md @@ -0,0 +1 @@ +Workflow templates allow everyone in your organization who has permission to create workflows to do so more quickly and easily. When you create a new workflow, you can choose a template and some or all of the work of writing the workflow will be done for you. Você pode usar os modelos do fluxo de trabalho como um ponto de partida para criar o fluxo de trabalho personalizado ou usá-los como se apresentam. This not only saves time, it promotes consistency and best practice across your organization. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/actions/workflow-run-approve-public-fork.md b/translations/pt-BR/data/reusables/actions/workflow-run-approve-public-fork.md index 85cf6f5aa5..945dec2759 100644 --- a/translations/pt-BR/data/reusables/actions/workflow-run-approve-public-fork.md +++ b/translations/pt-BR/data/reusables/actions/workflow-run-approve-public-fork.md @@ -1,3 +1,9 @@ Qualquer pessoa pode bifurcar um repositório público e, em seguida, enviar um pull request que proponha alterações nos fluxos de trabalho do repositório de {% data variables.product.prodname_actions %}. Embora os fluxos de trabalho das bifurcações não tenham acesso a dados confidenciais como segredos, podem ser uma dor de cabeça para os mantenedores se forem modificados para fins abusivos. Para ajudar a evitar isso, os fluxos de trabalho em pull requests para repositórios públicos de alguns contribuidores externos não serão executados automaticamente, e é possível que tenham de ser aprovados primeiro. Por padrão, todos os colaboradores iniciantes exigem aprovação para executar fluxos de trabalho. + +{% note %} + +**Note:** Workflows triggered by `pull_request_target` events are run in the context of the base branch. Since the base branch is considered trusted, workflows triggered by these events will always run, regardless of approval settings. + +{% endnote %} \ No newline at end of file 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 437c1acc2f..d89aa93a61 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,9 +1,9 @@ -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" or currentVersion == "github-ae@latest" %} +{% ifversion fpt or ghes or ghae %} {% warning %} -**Aviso de método obsoleto:** {% data variables.product.prodname_dotcom %} irá descontinuar a autenticação para a API usando parâmetros de consulta. A autenticação para a API deve ser feita com a [autenticação básica HTTP](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens).{% if currentVersion == "free-pro-team@latest" %} Usar parâmetros de consulta para efetuar a autenticação na API não funcionará mais a partir de 5 de maio de 2021. {% endif %} Para mais informações, incluindo brownouts agendadas, veja [blog post](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/). +**Aviso de método obsoleto:** {% data variables.product.prodname_dotcom %} irá descontinuar a autenticação para a API usando parâmetros de consulta. A autenticação na API deve ser feita com [HTTP basic authentication](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens).{% ifversion fpt %} Usar parâmetros de consulta para autenticar na API não funcionará mais em 5 de maio de 2021. {% endif %} Para mais informações, incluindo brownouts agendadas, veja [blog post](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/). -{% if enterpriseServerVersions contém currentVersion ou currentVersion == "github-ae@latest" %} Autenticação na API usando parâmetros de consulta enquanto disponível não é mais compatível devido a questões de segurança. Em vez disso, recomendamos que integradores movam seu token de acesso, `client_id`, or `client_secret` no cabeçalho. {% data variables.product.prodname_dotcom %} anunciará a remoção da autenticação por parâmetros de consulta com aviso prévio. {% endif %} +{% ifversion ghes or ghae %} Autenticação à API usando parâmetros de consulta, enquanto disponível não é mais suportada devido a questões de segurança. Em vez disso, recomendamos que integradores movam seu token de acesso, `client_id`, or `client_secret` no cabeçalho. {% data variables.product.prodname_dotcom %} anunciará a remoção da autenticação por parâmetros de consulta com aviso prévio. {% endif %} {% endwarning %} {% endif %} diff --git a/translations/pt-BR/data/reusables/apps/oauth-auth-vary-response.md b/translations/pt-BR/data/reusables/apps/oauth-auth-vary-response.md new file mode 100644 index 0000000000..b76fef614b --- /dev/null +++ b/translations/pt-BR/data/reusables/apps/oauth-auth-vary-response.md @@ -0,0 +1 @@ +You can also receive the response in different formats if you provide the format in the `Accept` header. For example, `Accept: application/json` or `Accept: application/xml`: diff --git a/translations/pt-BR/data/reusables/billing/email-notifications.md b/translations/pt-BR/data/reusables/billing/email-notifications.md index 3dd296397f..f064c56138 100644 --- a/translations/pt-BR/data/reusables/billing/email-notifications.md +++ b/translations/pt-BR/data/reusables/billing/email-notifications.md @@ -1,3 +1,3 @@ Email notifications are sent to account owners and billing managers when spending reaches 50%, 75%, and 90% of your account's included usage and when spending reaches 50%, 75%, and 90% of your account's spending limit. -You can disable these notifications anytime by navigating to the bottom of the **Spending Limit** page. \ No newline at end of file +Você pode desabilitar essas notificações a qualquer momento, acessando a parte inferior da página **limite de gastos**. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/cli/cli-learn-more.md b/translations/pt-BR/data/reusables/cli/cli-learn-more.md index 9a7d8272ea..fb2240ab73 100644 --- a/translations/pt-BR/data/reusables/cli/cli-learn-more.md +++ b/translations/pt-BR/data/reusables/cli/cli-learn-more.md @@ -1,5 +1,5 @@ {% note %} -To learn more about {% data variables.product.prodname_cli %}, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)." +Para saber mais sobre {% data variables.product.prodname_cli %}, consulte "[Sobre {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)." {% endnote %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/code-scanning/upload-sarif-alert-limit.md b/translations/pt-BR/data/reusables/code-scanning/upload-sarif-alert-limit.md index 476de08398..0d12cd7c3e 100644 --- a/translations/pt-BR/data/reusables/code-scanning/upload-sarif-alert-limit.md +++ b/translations/pt-BR/data/reusables/code-scanning/upload-sarif-alert-limit.md @@ -1,5 +1,8 @@ {% note %} -**Observação:** O upload do SARIF é compatível com um máximo de {% ifversion ghae-next or fpt or ghes > 3.0 %}5000{% else %}1000{% endif %} resultados por upload. Todos os resultados acima deste limite são ignorados. Se uma ferramenta gerar muitos resultados, você deverá atualizar a configuração para focar nos resultados para as regras ou consultas mais importantes. +**Notas:** +- SARIF upload supports a maximum of {% ifversion ghae-next or fpt or ghes > 3.0 %}5000{% else %}1000{% endif %} results per upload. Todos os resultados acima deste limite são ignorados. Se uma ferramenta gerar muitos resultados, você deverá atualizar a configuração para focar nos resultados para as regras ou consultas mais importantes. + + - For each upload, SARIF upload supports a maximum size of 10 MB for the `gzip`-compressed SARIF file. Any uploads over this limit will be rejected. If your SARIF file is too large because it contains too many results, you should update the configuration to focus on results for the most important rules or queries. {% endnote %} diff --git a/translations/pt-BR/data/reusables/codespaces/concurrent-codespace-limit.md b/translations/pt-BR/data/reusables/codespaces/concurrent-codespace-limit.md index db7e86949d..23436563a3 100644 --- a/translations/pt-BR/data/reusables/codespaces/concurrent-codespace-limit.md +++ b/translations/pt-BR/data/reusables/codespaces/concurrent-codespace-limit.md @@ -1 +1 @@ -Você pode criar mais de um código de espaço por repositório ou até mesmo por branch. However, each user account has a limit of 10 codespaces. Se você atingiu o limite e deseja criar um novo espaço de código, você deve primeiro excluir um código. +Você pode criar mais de um código de espaço por repositório ou até mesmo por branch. No entanto, cada conta de usuário tem um limite de 10 codespaces. Se você atingiu o limite e deseja criar um novo espaço de código, você deve primeiro excluir um código. diff --git a/translations/pt-BR/data/reusables/codespaces/create-or-switch-branch.md b/translations/pt-BR/data/reusables/codespaces/create-or-switch-branch.md new file mode 100644 index 0000000000..4fe3104bb4 --- /dev/null +++ b/translations/pt-BR/data/reusables/codespaces/create-or-switch-branch.md @@ -0,0 +1,3 @@ +1. Se o branch atual não for mostrado na barra de status, na parte inferior do seu codespace, clique com o botão direito na barra de status e selecione **Controle de origem**. +1. Clique no nome do branch na barra de status. ![O branch na barra de status](/assets/images/help/codespaces/branch-in-status-bar.png) +1. No menu suspenso, clique no branch para o qual você deseja alternar ou digite o nome de um novo branch e clique em **Criar novo branch**. ![Escolha no menu do branch](/assets/images/help/codespaces/create-new-branch.png) \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/codespaces/review-pr.md b/translations/pt-BR/data/reusables/codespaces/review-pr.md index cf263511e8..aa4d965bf1 100644 --- a/translations/pt-BR/data/reusables/codespaces/review-pr.md +++ b/translations/pt-BR/data/reusables/codespaces/review-pr.md @@ -1,5 +1,5 @@ 1. Open the pull request in a codespace, as described in "[Opening a pull request](/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests#opening-a-pull-request-in-codespaces)." -2. In the Activity Bar, click the **GitHub Pull Request** view. This view only appears when you open a pull request in a codespace. ![Option to open PR in a codespace](/assets/images/help/codespaces/github-pr-view.png) -3. To review a specific file, click the **Open File** icon in the Side Bar. ![Option to open PR in a codespace](/assets/images/help/codespaces/changes-in-files.png) -4. To add review comments, click the **+** icon next to the line number. Type your review comment and then click **Start Review**. ![Option to open PR in a codespace](/assets/images/help/codespaces/start-review.png) -5. When you are finished adding review comments, from the Side Bar you can choose to either submit the comments, approve the changes, or request changes. ![Option to open PR in a codespace](/assets/images/help/codespaces/submit-review.png) +2. In the Activity Bar, click the **GitHub Pull Request** view. This view only appears when you open a pull request in a codespace. ![Opção para abrir RP em um codespace](/assets/images/help/codespaces/github-pr-view.png) +3. To review a specific file, click the **Open File** icon in the Side Bar. ![Opção para abrir RP em um codespace](/assets/images/help/codespaces/changes-in-files.png) +4. To add review comments, click the **+** icon next to the line number. Type your review comment and then click **Start Review**. ![Opção para abrir RP em um codespace](/assets/images/help/codespaces/start-review.png) +5. When you are finished adding review comments, from the Side Bar you can choose to either submit the comments, approve the changes, or request changes. ![Opção para abrir RP em um codespace](/assets/images/help/codespaces/submit-review.png) diff --git a/translations/pt-BR/data/reusables/codespaces/source-control-commit-changes.md b/translations/pt-BR/data/reusables/codespaces/source-control-commit-changes.md new file mode 100644 index 0000000000..958dde62a4 --- /dev/null +++ b/translations/pt-BR/data/reusables/codespaces/source-control-commit-changes.md @@ -0,0 +1,4 @@ +{% data reusables.codespaces.source-control-display-dark %} +1. Para testar suas alterações, clique **+** ao lado do arquivo que você alterou, ou ao lado de **Alterações** se você mudou vários arquivos e quiser testar todos. ![Barra lateral de controle de origem com botão de staging destacado](/assets/images/help/codespaces/codespaces-commit-stage.png) +1. Digite uma mensagem do commit que descreve a alteração que você fez. ![Barra lateral do controle de origem com uma mensagem de commit](/assets/images/help/codespaces/codespaces-commit-commit-message.png) +1. Para fazer commit das alterações em fase de preparação, clique na marca de seleção na parte superior da barra lateral de controle de origem. ![Clique no ícone da marca de verificação](/assets/images/help/codespaces/codespaces-commit-checkmark-icon.png) \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/codespaces/source-control-pull-request.md b/translations/pt-BR/data/reusables/codespaces/source-control-pull-request.md new file mode 100644 index 0000000000..af5a1fe787 --- /dev/null +++ b/translations/pt-BR/data/reusables/codespaces/source-control-pull-request.md @@ -0,0 +1,3 @@ +1. Depois de realizar alterações na sua cópia local do repositório, clique no ícone **Criar Pull Request**. ![Barra lateral de controle de origem com botão de staging destacado](/assets/images/help/codespaces/codespaces-commit-pr-button.png) +1. Verifique se o branch local e o repositório do qual você está fazendo merge, o branch remoto e o repositório no qual você está fazendo merge estão corretos. Em seguida, dê ao pull request um título e uma descrição. ![Barra lateral de controle de origem com botão de staging destacado](/assets/images/help/codespaces/codespaces-commit-pr.png) +1. Clique em **Criar**. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/dependabot/supported-package-managers.md b/translations/pt-BR/data/reusables/dependabot/supported-package-managers.md index 6d1cd5fc42..feeb115067 100644 --- a/translations/pt-BR/data/reusables/dependabot/supported-package-managers.md +++ b/translations/pt-BR/data/reusables/dependabot/supported-package-managers.md @@ -26,7 +26,7 @@ A tabela a seguir mostra, para cada gerenciador de pacotes: | Terraform | `terraform` | >= 0.13, <= 1.0 | **✓** | **✓** | | | yarn | `npm` | v1 | **✓** | **✓** | | -[1] {% data variables.product.prodname_dependabot %} não executa o Gradle, mas é compatível com atualizações para os seguintes arquivos: `build.gradle` e `build.gradle.kts` (para projetos do Kotlin). +[1] {% data variables.product.prodname_dependabot %} doesn't run Gradle but supports updates to the following files: `build.gradle`, `build.gradle.kts` (for Kotlin projects), and files included via the `apply` declaration that have `dependencies` in the filename. Note that `apply` does not support `apply to`, recursion, or advanced syntaxes (for example, Kotlin's `apply` with `mapOf`, filenames defined by property). [2] {% data variables.product.prodname_dependabot %} não executa o Maven, mas é compatível com atualizações para arquivos `pom.xml`. diff --git a/translations/pt-BR/data/reusables/dependency-review/beta.md b/translations/pt-BR/data/reusables/dependency-review/beta.md index d2820cf257..8abbc5dbbb 100644 --- a/translations/pt-BR/data/reusables/dependency-review/beta.md +++ b/translations/pt-BR/data/reusables/dependency-review/beta.md @@ -1,7 +1,8 @@ -{% ifversion fpt or ghes > 3.1 %} +{% ifversion ghes > 3.1 %} {% note %} **Observação:** A revisão de dependências está atualmente em fase beta e sujeita a alterações. {% endnote %} + {% endif %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/developer-site/pull_request_forked_repos_link.md b/translations/pt-BR/data/reusables/developer-site/pull_request_forked_repos_link.md index 8c6c125f10..b4ccf649b3 100644 --- a/translations/pt-BR/data/reusables/developer-site/pull_request_forked_repos_link.md +++ b/translations/pt-BR/data/reusables/developer-site/pull_request_forked_repos_link.md @@ -1,4 +1,4 @@ -#### Eventos de pull request para repositórios bifurcados +### Eventos de pull request para repositórios bifurcados {% note %} diff --git a/translations/pt-BR/data/reusables/dotcom_billing/pricing_cal.md b/translations/pt-BR/data/reusables/dotcom_billing/pricing_cal.md new file mode 100644 index 0000000000..6509379b28 --- /dev/null +++ b/translations/pt-BR/data/reusables/dotcom_billing/pricing_cal.md @@ -0,0 +1 @@ +To estimate the costs for consumptive services, you can use the {% data variables.product.prodname_dotcom %} pricing calculator. For more information, go to https://github.com/pricing/calculator. diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/about-enterprise-accounts.md b/translations/pt-BR/data/reusables/enterprise-accounts/about-enterprise-accounts.md index 8d2062a137..62ec967653 100644 --- a/translations/pt-BR/data/reusables/enterprise-accounts/about-enterprise-accounts.md +++ b/translations/pt-BR/data/reusables/enterprise-accounts/about-enterprise-accounts.md @@ -14,7 +14,7 @@ Organizations are shared accounts where enterprise members can collaborate acros {% ifversion fpt %} -Enterprise owners can create organizations and link the organizations to the enterprise. After you add organizations to your enterprise account, you can manage and enforce policies for the organizations. Opções específicas de aplicação variam de acordo com a configuração; normalmente, é possível optar por aplicar uma única política para cada organização na sua conta corporativa ou permitir que proprietários definam a política no nível da organização. For more information, see "[Setting policies for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account)." +Enterprise owners can create organizations and link the organizations to the enterprise. Alternatively, you can invite an existing organization to join your enterprise. After you add organizations to your enterprise account, you can manage and enforce policies for the organizations. Opções específicas de aplicação variam de acordo com a configuração; normalmente, é possível optar por aplicar uma única política para cada organização na sua conta corporativa ou permitir que proprietários definam a política no nível da organização. For more information, see "[Setting policies for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account)." {% elsif ghes or ghae %} @@ -58,6 +58,14 @@ For more information about the differences between {% data variables.product.pro {% endif %} +{% ifversion fpt %} + +## Sobre o {% data variables.product.prodname_emus %} + +{% data reusables.enterprise-accounts.emu-short-summary %} + +{% endif %} + ## About billing for your enterprise account The bill for your enterprise account includes the monthly cost for each member of your enterprise. The bill includes {% ifversion fpt %}any paid licenses in organizations outside of your enterprise account, subscriptions to apps in {% data variables.product.prodname_marketplace %}, {% endif %}{% ifversion fpt or ghae %}additional paid services for your enterprise{% ifversion fpt %} like data packs for {% data variables.large_files.product_name_long %},{% endif %} and{% endif %} usage for {% data variables.product.prodname_GH_advanced_security %}. diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/access-enterprise.md b/translations/pt-BR/data/reusables/enterprise-accounts/access-enterprise.md index 5402183f0e..36bb1a677f 100644 --- a/translations/pt-BR/data/reusables/enterprise-accounts/access-enterprise.md +++ b/translations/pt-BR/data/reusables/enterprise-accounts/access-enterprise.md @@ -5,5 +5,4 @@ {% elsif ghes or ghae %}1. No canto superior direito de {% data variables.product.product_name %}, clique na sua foto de perfil e, em seguida, clique em **Configurações da empresa**. !["Configurações da empresa" no menu suspenso para foto do perfil em {% data variables.product.product_name %}](/assets/images/enterprise/settings/enterprise-settings.png) - {% endif %} diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/actions-runners-tab.md b/translations/pt-BR/data/reusables/enterprise-accounts/actions-runners-tab.md index 4eae593fef..732bf52bc0 100644 --- a/translations/pt-BR/data/reusables/enterprise-accounts/actions-runners-tab.md +++ b/translations/pt-BR/data/reusables/enterprise-accounts/actions-runners-tab.md @@ -1 +1 @@ -1. Clique na aba {% ifversion fpt %}**Executores**{% else %}**Executores auto-hospedados **{% endif %}. +1. Clique na aba {% ifversion fpt or ghes > 3.1 or ghae-next %}**Executores**{% else %}**Executores auto-hospedados **{% endif %}. diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/emu-forks.md b/translations/pt-BR/data/reusables/enterprise-accounts/emu-forks.md new file mode 100644 index 0000000000..315ee2736f --- /dev/null +++ b/translations/pt-BR/data/reusables/enterprise-accounts/emu-forks.md @@ -0,0 +1 @@ +{% data variables.product.prodname_managed_users_caps %} cannot fork repositories from outside of the enterprise or fork internal repositories. {% data variables.product.prodname_managed_users_caps %} can fork private repositories owned by organizations in the enterprise into other organizations owned by the enterprise, or as a fork owned by the {% data variables.product.prodname_managed_user %}. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/emu-more-info-account.md b/translations/pt-BR/data/reusables/enterprise-accounts/emu-more-info-account.md new file mode 100644 index 0000000000..21302799fb --- /dev/null +++ b/translations/pt-BR/data/reusables/enterprise-accounts/emu-more-info-account.md @@ -0,0 +1 @@ +For more information, see "[Types of GitHub accounts](/get-started/learning-about-github/types-of-github-accounts#enterprise-managed-users)." \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/emu-password-reset-session.md b/translations/pt-BR/data/reusables/enterprise-accounts/emu-password-reset-session.md new file mode 100644 index 0000000000..65ed74cc65 --- /dev/null +++ b/translations/pt-BR/data/reusables/enterprise-accounts/emu-password-reset-session.md @@ -0,0 +1 @@ +If you need to reset the password for your setup user, use an incognito or private browsing window to request a new password. When the email arrives with the link to reset your password, copy the link into your browser. For more information on resetting your password, see "[Requesting a new password ](/github/authenticating-to-github/keeping-your-account-and-data-secure/updating-your-github-access-credentials#requesting-a-new-password)." \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-follow.md b/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-follow.md new file mode 100644 index 0000000000..f166721634 --- /dev/null +++ b/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-follow.md @@ -0,0 +1 @@ +{% ifversion fpt %} Members of an {% data variables.product.prodname_emu_enterprise %} can only follow other members of their enterprise. {% endif %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-fork.md b/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-fork.md new file mode 100644 index 0000000000..411dfeed7b --- /dev/null +++ b/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-fork.md @@ -0,0 +1 @@ +{% ifversion fpt %}Members of an {% data variables.product.prodname_emu_enterprise %} cannot fork repositories from outside of the enterprise or fork internal repositories.{% endif %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-gist.md b/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-gist.md new file mode 100644 index 0000000000..3164ea3434 --- /dev/null +++ b/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-gist.md @@ -0,0 +1 @@ +{% ifversion fpt %}Members of an {% data variables.product.prodname_emu_enterprise %} cannot create gists and have read-only access to gists.{% endif %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-interact.md b/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-interact.md new file mode 100644 index 0000000000..9bdeac19e8 --- /dev/null +++ b/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-interact.md @@ -0,0 +1 @@ +{% ifversion fpt %} Members of an {% data variables.product.prodname_emu_enterprise %} can only interact with repositories within their enterprise. {% endif %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-propose.md b/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-propose.md new file mode 100644 index 0000000000..85fd4f66e3 --- /dev/null +++ b/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-propose.md @@ -0,0 +1 @@ +{% ifversion fpt %} Members of an {% data variables.product.prodname_emu_enterprise %} can only propose changes in repositories that are part of their enterprise. {% endif %} diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-repo.md b/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-repo.md new file mode 100644 index 0000000000..b4278362a5 --- /dev/null +++ b/translations/pt-BR/data/reusables/enterprise-accounts/emu-permission-repo.md @@ -0,0 +1 @@ +{% ifversion fpt %} Members of an {% data variables.product.prodname_emu_enterprise %} can only make changes in repositories that are part of their enterprise. {% endif %} diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/emu-saml-note.md b/translations/pt-BR/data/reusables/enterprise-accounts/emu-saml-note.md new file mode 100644 index 0000000000..29c9bb6f8e --- /dev/null +++ b/translations/pt-BR/data/reusables/enterprise-accounts/emu-saml-note.md @@ -0,0 +1,7 @@ +{% ifversion fpt%} +{% note %} + +**Note**: If your enterprise uses {% data variables.product.prodname_emus %}, you must follow a different process to configure SAML single sign-on. Para obter mais informações, consulte "[Configurando o logon único SAML para Usuários Gerenciados pela Empresa](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." + +{% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/emu-scim-note.md b/translations/pt-BR/data/reusables/enterprise-accounts/emu-scim-note.md new file mode 100644 index 0000000000..309ec9adfb --- /dev/null +++ b/translations/pt-BR/data/reusables/enterprise-accounts/emu-scim-note.md @@ -0,0 +1,7 @@ +{% ifversion fpt%} +{% note %} + +**Note**: If your enterprise uses {% data variables.product.prodname_emus %}, you cannot use team synchronization and must instead configure SCIM to manage membership with your identity provider. For more information, see "[Configuring SCIM provisioning for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users)." + +{% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/emu-short-summary.md b/translations/pt-BR/data/reusables/enterprise-accounts/emu-short-summary.md new file mode 100644 index 0000000000..0236939a7b --- /dev/null +++ b/translations/pt-BR/data/reusables/enterprise-accounts/emu-short-summary.md @@ -0,0 +1 @@ +{% data variables.product.prodname_emus %} is a feature of {% data variables.product.prodname_ghe_cloud %} that provides even greater control over enterprise members and resources. With {% data variables.product.prodname_emus %}, all members are provisioned and managed through your identity provider (IdP) instead of users creating their own accounts on {% data variables.product.product_name %}. Team membership can be managed using groups on your IdP. {% data variables.product.prodname_managed_users_caps %} are restricted to their enterprise and are unable to push code, collaborate, or interact with users, repositories, and organizations outside of their enterprise. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/emu-shortcode.md b/translations/pt-BR/data/reusables/enterprise-accounts/emu-shortcode.md new file mode 100644 index 0000000000..ec695c807d --- /dev/null +++ b/translations/pt-BR/data/reusables/enterprise-accounts/emu-shortcode.md @@ -0,0 +1 @@ +The short code must be unique to your enterprise, a three-to-eight character alphanumeric string, and contain no special characters. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/emu-supported-idps.md b/translations/pt-BR/data/reusables/enterprise-accounts/emu-supported-idps.md new file mode 100644 index 0000000000..375040efa3 --- /dev/null +++ b/translations/pt-BR/data/reusables/enterprise-accounts/emu-supported-idps.md @@ -0,0 +1,2 @@ +* Azure Active Directory (Azure AD) +* Okta \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/github-connect-tab.md b/translations/pt-BR/data/reusables/enterprise-accounts/github-connect-tab.md index 07fd9fa0a7..99a13699d7 100644 --- a/translations/pt-BR/data/reusables/enterprise-accounts/github-connect-tab.md +++ b/translations/pt-BR/data/reusables/enterprise-accounts/github-connect-tab.md @@ -1,3 +1,3 @@ {% ifversion ghes < 3.1 %} 1. Na barra lateral esquerda, clique em **{% data variables.product.prodname_github_connect %}**. ![GitHub Connect tab in the business account settings sidebar](/assets/images/enterprise/business-accounts/settings-github-connect-tab.png){% else %} -1. In the enterprise account sidebar, click {% octicon "plug" aria-label="The GitHub Connect gear" %} **{% data variables.product.prodname_github_connect %}**. ![GitHub Connect tab in the enterprise account sidebar](/assets/images/help//business-accounts/enterprise-account-github-connect-tab.png){% endif %} \ No newline at end of file +1. In the enterprise account sidebar, click {% octicon "plug" aria-label="The GitHub Connect gear" %} **{% data variables.product.prodname_github_connect %}**. ![GitHub Connect tab in the enterprise account sidebar](/assets/images/help//business-accounts/enterprise-account-github-connect-tab.png){% endif %} diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/identity-provider-tab.md b/translations/pt-BR/data/reusables/enterprise-accounts/identity-provider-tab.md new file mode 100644 index 0000000000..9e94eecb59 --- /dev/null +++ b/translations/pt-BR/data/reusables/enterprise-accounts/identity-provider-tab.md @@ -0,0 +1 @@ +1. Under your business account's name, click {% octicon "key" aria-label="The key icon" %} **Identity provider**. !["Identity provider" tab in enterprise sidebar](/assets/images/help/enterprises/enterprise-account-identity-provider-tab.png) \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/invite-organization.md b/translations/pt-BR/data/reusables/enterprise-accounts/invite-organization.md new file mode 100644 index 0000000000..1d5c99c11e --- /dev/null +++ b/translations/pt-BR/data/reusables/enterprise-accounts/invite-organization.md @@ -0,0 +1 @@ +Enterprise account owners and administrators can invite existing organization accounts to join their enterprise. For more information, see "[Inviting an organization to join your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account#inviting-an-organization-to-join-your-enterprise-account)" diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/team-sync-override.md b/translations/pt-BR/data/reusables/enterprise-accounts/team-sync-override.md new file mode 100644 index 0000000000..a39283eed0 --- /dev/null +++ b/translations/pt-BR/data/reusables/enterprise-accounts/team-sync-override.md @@ -0,0 +1 @@ +If your organization is owned by an enterprise account, enabling team synchronization or SCIM provisioning for the enterprise account will override your organization-level team synchronization settings. For more information, see "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)" and "[Configuring SCIM provisioning for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users)." \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/enterprise_clustering/proxy_protocol_ports.md b/translations/pt-BR/data/reusables/enterprise_clustering/proxy_protocol_ports.md index d0c2e951c0..450a9c1674 100644 --- a/translations/pt-BR/data/reusables/enterprise_clustering/proxy_protocol_ports.md +++ b/translations/pt-BR/data/reusables/enterprise_clustering/proxy_protocol_ports.md @@ -1,4 +1,4 @@ -#### Mapeamentos das portas TCP PROXY +### Mapeamentos das portas TCP PROXY | Porta de origem | Porta de destino | Descrição do serviço | |:---------------:|:----------------:|:---------------------------------:| diff --git a/translations/pt-BR/data/reusables/enterprise_clustering/without_proxy_protocol_ports.md b/translations/pt-BR/data/reusables/enterprise_clustering/without_proxy_protocol_ports.md index 92fc706375..770be90032 100644 --- a/translations/pt-BR/data/reusables/enterprise_clustering/without_proxy_protocol_ports.md +++ b/translations/pt-BR/data/reusables/enterprise_clustering/without_proxy_protocol_ports.md @@ -1,4 +1,4 @@ -#### Mapeamentos de portas TCP para uso sem suporte PROXY +### Mapeamentos de portas TCP para uso sem suporte PROXY | Porta de origem | Porta de destino | Descrição do serviço | |:---------------:|:----------------:|:---------------------------------:| diff --git a/translations/pt-BR/data/reusables/enterprise_installation/upload-a-license-file.md b/translations/pt-BR/data/reusables/enterprise_installation/upload-a-license-file.md index d529feedc1..673db33af1 100644 --- a/translations/pt-BR/data/reusables/enterprise_installation/upload-a-license-file.md +++ b/translations/pt-BR/data/reusables/enterprise_installation/upload-a-license-file.md @@ -1 +1 @@ -2. No prompt, carregue seu arquivo de licença e defina uma senha de gerenciamento do console. For more information, see "[Managing your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise)." +2. No prompt, carregue seu arquivo de licença e defina uma senha de gerenciamento do console. Para obter mais informações, consulte "[Gerenciar a sua licença para {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise)." diff --git a/translations/pt-BR/data/reusables/gated-features/emus.md b/translations/pt-BR/data/reusables/gated-features/emus.md new file mode 100644 index 0000000000..ef212cd0c9 --- /dev/null +++ b/translations/pt-BR/data/reusables/gated-features/emus.md @@ -0,0 +1 @@ +To manage users in your enterprise with your identity provider, your enterprise must be enabled for {% data variables.product.prodname_emus %}, which are available with {% data variables.product.prodname_ghe_cloud %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/getting-started/enterprise-advanced-security.md b/translations/pt-BR/data/reusables/getting-started/enterprise-advanced-security.md new file mode 100644 index 0000000000..faffbe7d63 --- /dev/null +++ b/translations/pt-BR/data/reusables/getting-started/enterprise-advanced-security.md @@ -0,0 +1 @@ +If you have a GitHub Advanced Security license for your enterprise account, you can enforce policies to manage {% data variables.product.prodname_dotcom %} Advanced Security features for organizations owned by an enterprise account. For more information, see "[Enforcing policies for Advanced Security in your enterprise account](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-policies-for-advanced-security-in-your-enterprise-account)." \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/github-actions/actions-on-examples.md b/translations/pt-BR/data/reusables/github-actions/actions-on-examples.md index d1b4be5ef7..fef0c54575 100644 --- a/translations/pt-BR/data/reusables/github-actions/actions-on-examples.md +++ b/translations/pt-BR/data/reusables/github-actions/actions-on-examples.md @@ -1,18 +1,18 @@ -### Exemplo: Usando um único evento +## Exemplo: Usando um único evento ```yaml # Triggered when code is pushed to any branch in a repository on: push ``` -### Exemplo: Usando uma lista de eventos +## Exemplo: Usando uma lista de eventos ```yaml # Triggers the workflow on push or pull request events on: [push, pull_request] ``` -### Exemplo: Usando vários eventos com tipos de atividade ou configuração +## Exemplo: Usando vários eventos com tipos de atividade ou configuração Se você precisar especificar tipos de atividade ou configuração para um evento, você deve configurar cada evento separadamente. Você deve anexar dois pontos (`:`) a todos os eventos, incluindo eventos sem configuração. diff --git a/translations/pt-BR/data/reusables/github-actions/disabling-github-actions.md b/translations/pt-BR/data/reusables/github-actions/disabling-github-actions.md index 18b9312289..4547ca47f4 100644 --- a/translations/pt-BR/data/reusables/github-actions/disabling-github-actions.md +++ b/translations/pt-BR/data/reusables/github-actions/disabling-github-actions.md @@ -1 +1 @@ -Por padrão, {% ifversion ghes or ghae %}depois de habilitar {% data variables.product.prodname_actions %} em {% data variables.product.product_location %}, este {% elsif fpt %} {% data variables.product.prodname_actions %}{% endif %} está habilitado em todos os repositórios e organizações. Você pode optar por desabilitar {% data variables.product.prodname_actions %} ou limitá-los apenas a ações privadas, o que significa que as pessoas só poderão usar ações que existem no seu repositório. +Por padrão, {% ifversion ghes or ghae %}depois de habilitar {% data variables.product.prodname_actions %} em {% data variables.product.product_location %}, este {% elsif fpt %} {% data variables.product.prodname_actions %}{% endif %} está habilitado em todos os repositórios e organizações. You can choose to disable {% data variables.product.prodname_actions %} or limit them to local actions only, which means that people can only use actions that exist in your repository. diff --git a/translations/pt-BR/data/reusables/github-actions/name-environment.md b/translations/pt-BR/data/reusables/github-actions/name-environment.md new file mode 100644 index 0000000000..54e0fd05d3 --- /dev/null +++ b/translations/pt-BR/data/reusables/github-actions/name-environment.md @@ -0,0 +1 @@ +1. Insira um nome para o ambiente e clique em **Configurar ambiente**. Os nomes de ambiente não diferenciam maiúsculas de minúsculas. Um nome de ambiente não pode exceder 255 caracteres e deve ser único dentro do repositório. diff --git a/translations/pt-BR/data/reusables/github-actions/new-environment.md b/translations/pt-BR/data/reusables/github-actions/new-environment.md new file mode 100644 index 0000000000..e59bd3db3d --- /dev/null +++ b/translations/pt-BR/data/reusables/github-actions/new-environment.md @@ -0,0 +1 @@ +1. Clique em **Novo ambiente**. diff --git a/translations/pt-BR/data/reusables/github-actions/runner-label-settings.md b/translations/pt-BR/data/reusables/github-actions/runner-label-settings.md index 7fd28f8010..0590149ae6 100644 --- a/translations/pt-BR/data/reusables/github-actions/runner-label-settings.md +++ b/translations/pt-BR/data/reusables/github-actions/runner-label-settings.md @@ -1 +1 @@ - 1. In the "Labels" section, click {% octicon "gear" aria-label="The Gear icon" %}. \ No newline at end of file + 1. Na seção "Etiquetas", clique em {% octicon "gear" aria-label="The Gear icon" %}. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md b/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md index e1411d311b..81eca535b5 100644 --- a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md +++ b/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md @@ -1,6 +1,7 @@ -1. Na seção {% ifversion fpt %}"Executores"{% else %}"Executores auto-hospedados"{% endif %} da página de configurações, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} ao lado do grupo executor que você gostaria de configurar e, em seguida, clique em **Editar nome e acesso [organization|repository]**. ![Gerenciar permissões do repositório](/assets/images/help/settings/actions-runner-manage-permissions.png) +1. Na seção {% ifversion fpt or ghes > 3.1 or ghae-next %}"Executores"{% else %}"Executores auto-hospedados"{% endif %} da página de configurações, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} ao lado do grupo executor que você gostaria de configurar e, em seguida, clique em **Editar nome e acesso [organization|repository]**. ![Gerenciar permissões do repositório](/assets/images/help/settings/actions-runner-manage-permissions.png) 1. Modifique as suas opções de políticas, ou altere o nome do grupo do executor. + {% ifversion not ghae %} {% warning %} **Aviso** @@ -10,3 +11,4 @@ Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)." {% endwarning %} + {% endif %} diff --git a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-list.md b/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-list.md index fe145aaf8c..787a64ca5d 100644 --- a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-list.md +++ b/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-list.md @@ -1 +1 @@ - 1. Localize a lista de executores em {% ifversion fpt %}"Executores"{% else %}"Executores auto-hospedados"{% endif %}. + 1. Localize a lista de executores em {% ifversion fpt or ghes > 3.1 or ghae-next %}"Executores"{% else %}"Executores auto-hospedados"{% endif %}. diff --git a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-management-permissions-required.md b/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-management-permissions-required.md index 6b88ca8b5b..cbcc45abdf 100644 --- a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-management-permissions-required.md +++ b/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-management-permissions-required.md @@ -1,9 +1,9 @@ -A self-hosted runner can be located in either your repository, organization, or {% if currentVersion == "free-pro-team@latest" %}enterprise account settings on {% data variables.product.prodname_dotcom %}{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} enterprise settings on {% data variables.product.product_location %}{% endif %}. Para gerenciar um executor auto-hospedado, você deve ter as seguintes permissões, dependendo de onde o executor auto-hospedado foi adicionado: +Um executor auto-hospedado pode ser localizado no seu repositório, organização, ou {% ifversion fpt %}configurações da conta corporativa em {% data variables.product.prodname_dotcom %}{% elsif ghes or ghae %} configurações corporativas em {% data variables.product.product_location %}{% endif %}. Para gerenciar um executor auto-hospedado, você deve ter as seguintes permissões, dependendo de onde o executor auto-hospedado foi adicionado: - **Repositório de Usuário**: Você deve ser o proprietário do repositório. - **Organização**: Você deve ser um proprietário da organização. - **Repositório da organização**: Você deve ser o proprietário da organização ou ter acesso de administrador ao repositório. -{% if currentVersion == "free-pro-team@latest" %} +{% ifversion fpt %} - **Conta corporativa**: Você deve ser proprietário de uma empresa. -{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} +{% elsif ghes or ghae %} - **Empresa**: Você deve ser um administrador do site de {% data variables.product.prodname_enterprise %} {% endif %} diff --git a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md b/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md index 6dfd31c4c0..163a41e676 100644 --- a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md +++ b/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md @@ -1,10 +1,10 @@ 1. Navegue por onde seu runner auto-hospedado está registrado: * **Em uma organização ou repositório**: navegue até a página principal e clique em {% octicon "gear" aria-label="The Settings gear" %} **Configurações**. - * {% if currentVersion == "free-pro-team@latest" %}**If using an enterprise account**: navigate to your enterprise account by visiting `https://github.com/enterprises/ENTERPRISE-NAME`, replacing `ENTERPRISE-NAME` with your enterprise account's name.{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}**If using an enterprise-level runner**: + * {% ifversion fpt %}**Se você estiver usando uma conta corporativa**: acesse a conta corporativa visitando `https://github. om/enterprises/ENTERPRISE-NAME` e substituindo `ENTERPRISE-NAME` pelo nome da sua conta corporativa.{% elsif ghes or ghae %}**Se estiver usando um executor de nível corporativo**: 1. No canto superior direito de qualquer página, clique em {% octicon "rocket" aria-label="The rocket ship" %}. 1. Na barra lateral esquerda, clique em **Visão geral da empresa**. 1. {% endif %} Na barra lateral da empresa, {% octicon "law" aria-label="The law icon" %} **Políticas**. 1. Navegue até as configurações {% data variables.product.prodname_actions %}: - * **In an organization or repository**: Click **Actions** in the left sidebar{% if currentVersion == "free-pro-team@latest" %}, then click **Runners**{% endif %}. - * {% if currentVersion == "free-pro-team@latest" %}**If using an enterprise account**:{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %}**If using an enterprise-level runner**:{% endif %} Click **Actions** under "{% octicon "law" aria-label="The law icon" %} Policies"{% if currentVersion == "free-pro-team@latest" %}, then click the **Runners** tab{% endif %}. + * **Em uma organização ou repositório**: Clique em **Ações** na barra lateral esquerda{% ifversion fpt or ghes > 3.1 or ghae-next %} e, em seguida, clique em **Executores**{% endif %}. + * {% ifversion fpt %}**Se você estiver usando uma conta corporativa**:{% elsif ghes or ghae %}**Se estiver usando um executor de nível corporativo**:{% endif %} Clique em **Ações** em "{% octicon "law" aria-label="The law icon" %} Políticas"{% ifversion fpt or ghes > 3.1 or ghae-next %} e, em seguida, clique na aba **Executores**{% endif %}. diff --git a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md b/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md index 94f459d13c..3330e56231 100644 --- a/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md +++ b/translations/pt-BR/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md @@ -1,4 +1,4 @@ -1. Em {% ifversion fpt %}"Executores"{% else %}"Executores auto-hospedados"{% endif %}, localize o executor na lista. Se o seu runner estiver em um grupo, clique em {% octicon "chevron-down" aria-label="The downwards chevron" %} para expandir a lista. +1. Em {% ifversion fpt or ghes > 3.1 or ghae-next %}"Executores"{% else %}"Executores auto-hospedados"{% endif %}, localize o executor na lista. Se o seu runner estiver em um grupo, clique em {% octicon "chevron-down" aria-label="The downwards chevron" %} para expandir a lista. 1. Clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} ao lado do runner que deseja remover, depois clique em **Remover**. ![Removendo uma configuração do executor auto-hospedado](/assets/images/help/settings/actions-runner-remove.png) diff --git a/translations/pt-BR/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md b/translations/pt-BR/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md index 4016a4af79..d51fdc01ef 100644 --- a/translations/pt-BR/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md +++ b/translations/pt-BR/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md @@ -1,2 +1,2 @@ -1. Na barra lateral esquerda, clique em **Actions** (Ações). -1. In the left sidebar, under "Actions", click **Runner groups**. +1. In the left sidebar, click **Actions**.{% ifversion fpt or ghes > 3.1 or ghae-next %} +1. In the left sidebar, under "Actions", click **Runner groups**.{% endif %} diff --git a/translations/pt-BR/data/reusables/github-actions/settings-sidebar-actions-runners.md b/translations/pt-BR/data/reusables/github-actions/settings-sidebar-actions-runners.md index 6c248233a6..e176fa4be7 100644 --- a/translations/pt-BR/data/reusables/github-actions/settings-sidebar-actions-runners.md +++ b/translations/pt-BR/data/reusables/github-actions/settings-sidebar-actions-runners.md @@ -1 +1 @@ -1. Na barra lateral esquerda, clique em **Ações**{% ifversion fpt %} e, em seguida, clique em **Executores**{% endif %}. +1. Na barra lateral esquerda, clique em **Ações**{% ifversion fpt or ghes > 3.1 or ghae-next %} e, em seguida, clique em **Executores**{% endif %}. diff --git a/translations/pt-BR/data/reusables/github-actions/supported-github-runners.md b/translations/pt-BR/data/reusables/github-actions/supported-github-runners.md index cb307f9993..aa1e67b75b 100644 --- a/translations/pt-BR/data/reusables/github-actions/supported-github-runners.md +++ b/translations/pt-BR/data/reusables/github-actions/supported-github-runners.md @@ -60,17 +60,6 @@ Ubuntu 18.04 -Ubuntu 16.04[deprecated] - - -ubuntu-16.04 - - -Deprecated and limited to existing customers only. Migrate to Ubuntu 20.04. For more information, see the blog post. - - - - macOS Big Sur 11 diff --git a/translations/pt-BR/data/reusables/github-connect/access-dotcom-and-enterprise.md b/translations/pt-BR/data/reusables/github-connect/access-dotcom-and-enterprise.md index 09cbd0bdbe..2f22dbfd74 100644 --- a/translations/pt-BR/data/reusables/github-connect/access-dotcom-and-enterprise.md +++ b/translations/pt-BR/data/reusables/github-connect/access-dotcom-and-enterprise.md @@ -1 +1 @@ -1. Entre na {% data variables.product.product_location_enterprise %} e no {% data variables.product.prodname_dotcom_the_website %}. +1. Sign in to {% ifversion ghes %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_ghe_managed %}{% endif %} and {% data variables.product.prodname_dotcom_the_website %}. diff --git a/translations/pt-BR/data/reusables/github-connect/access-profile-settings.md b/translations/pt-BR/data/reusables/github-connect/access-profile-settings.md index 31dea8796f..98a8d1d228 100644 --- a/translations/pt-BR/data/reusables/github-connect/access-profile-settings.md +++ b/translations/pt-BR/data/reusables/github-connect/access-profile-settings.md @@ -1 +1 @@ -1. No canto superior direito de qualquer página do {% data variables.product.product_location_enterprise %}, clique na sua foto do perfil e em **Settings** (Configurações). ![Ícone Settings (Configurações) na barra de usuário](/assets/images/help/settings/userbar-account-settings.png) +1. On {% ifversion ghes %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_ghe_managed %}{% endif %}, in the upper-right corner of any page, click your profile photo, then click **Settings**. ![Ícone Settings (Configurações) na barra de usuário](/assets/images/help/settings/userbar-account-settings.png) diff --git a/translations/pt-BR/data/reusables/github-connect/authorize-connection.md b/translations/pt-BR/data/reusables/github-connect/authorize-connection.md index 0f848d87fe..000a069960 100644 --- a/translations/pt-BR/data/reusables/github-connect/authorize-connection.md +++ b/translations/pt-BR/data/reusables/github-connect/authorize-connection.md @@ -1 +1,7 @@ -1. Revise os recursos que {% data variables.product.prodname_ghe_server %} terá acesso a partir da sua conta {% data variables.product.prodname_dotcom_the_website %} e então, clique em **Authorize** (Autorizar). ![Autorizar conexão entre o GitHub Enterprise Server e GitHub.com](/assets/images/help/settings/authorize-ghe-to-connect-to-dotcom.png) +1. Review the resources that +{% data variables.product.product_name %} will access from your {% data variables.product.prodname_dotcom_the_website %} account, then click **Authorize**. +{% ifversion ghes %} + ![Autorizar a conexão entre o {% data variables.product.prodname_ghe_server %} e o {% data variables.product.prodname_dotcom_the_website %}](/assets/images/help/settings/authorize-ghe-to-connect-to-dotcom.png) +{% elsif ghae %} + ![Autorizar a conexão entre o {% data variables.product.prodname_ghe_managed %} e o {% data variables.product.prodname_dotcom_the_website %}](/assets/images/enterprise/github-ae/settings/authorize-ghae-to-connect-to-dotcom.png) +{% endif %} diff --git a/translations/pt-BR/data/reusables/github-connect/beta.md b/translations/pt-BR/data/reusables/github-connect/beta.md new file mode 100644 index 0000000000..991a98d3d6 --- /dev/null +++ b/translations/pt-BR/data/reusables/github-connect/beta.md @@ -0,0 +1,7 @@ +{% ifversion ghae-next %} +{% note %} + +**Note:** {% data variables.product.prodname_github_connect %} for {% data variables.product.product_name %} is currently in beta and subject to change. + +{% endnote %} +{% endif %} diff --git a/translations/pt-BR/data/reusables/github-connect/connect-dotcom-and-enterprise.md b/translations/pt-BR/data/reusables/github-connect/connect-dotcom-and-enterprise.md index c226898603..53e816b48b 100644 --- a/translations/pt-BR/data/reusables/github-connect/connect-dotcom-and-enterprise.md +++ b/translations/pt-BR/data/reusables/github-connect/connect-dotcom-and-enterprise.md @@ -1 +1,6 @@ -1. Clique em **Connect to {% data variables.product.prodname_dotcom_the_website %}**. ![Conecte-se ao GitHub.com a partir das configurações do GitHub Enterprise Server](/assets/images/help/settings/github.com_end_user_connection.png) +1. Clique em **Connect to {% data variables.product.prodname_dotcom_the_website %}**. +{% ifversion ghes %} + ![Conecte-se ao GitHub.com a partir das configurações do GitHub Enterprise Server](/assets/images/help/settings/github.com_end_user_connection.png) +{% else %} + ![Connect to GitHub.com from GitHub AE settings](/assets/images/enterprise/github-ae/settings/github.com-end-user-connection.png) +{% endif %} diff --git a/translations/pt-BR/data/reusables/github-connect/send-contribution-counts-to-githubcom.md b/translations/pt-BR/data/reusables/github-connect/send-contribution-counts-to-githubcom.md new file mode 100644 index 0000000000..6b302572fe --- /dev/null +++ b/translations/pt-BR/data/reusables/github-connect/send-contribution-counts-to-githubcom.md @@ -0,0 +1 @@ +1. Em "Contributions" (Contribuições), selecione **Send my contribution counts to {% data variables.product.prodname_dotcom_the_website %}** (Enviar minhas contagens de contribuição para o {% data variables.product.prodname_dotcom_the_website %}) e clique em **Update contributions** (Atualizar contribuições). ![Caixa de seleção Send contributions (Enviar contribuições) e botão update contributions (atualizar contribuições)](/assets/images/help/settings/send-and-update-contributions.png) diff --git a/translations/pt-BR/data/reusables/github-connect/sync-frequency.md b/translations/pt-BR/data/reusables/github-connect/sync-frequency.md index 6705bbb3b9..99ce5a6711 100644 --- a/translations/pt-BR/data/reusables/github-connect/sync-frequency.md +++ b/translations/pt-BR/data/reusables/github-connect/sync-frequency.md @@ -1 +1 @@ -{% data variables.product.prodname_ghe_server %} envia atualizações a cada hora. +{% data variables.product.product_name %} envia atualizações a cada hora. diff --git a/translations/pt-BR/data/reusables/notifications-v2/custom-notification-types.md b/translations/pt-BR/data/reusables/notifications-v2/custom-notification-types.md index e2e3b00b4c..a12fa0f660 100644 --- a/translations/pt-BR/data/reusables/notifications-v2/custom-notification-types.md +++ b/translations/pt-BR/data/reusables/notifications-v2/custom-notification-types.md @@ -1,2 +1,2 @@ {%- ifversion fpt or ghes > 3.1 or ghae-issue-4910 %}problemas, pull requests, versões, alertas de segurança ou discussões{% endif %} -{%- ifversion ghes = 3.1 or ghae-next %}problemas, pull requests, versões ou discussões{% endif %} +{%- ifversion ghes = 3.1 %}problemas, pull requests, versões ou discussões{% endif %} diff --git a/translations/pt-BR/data/reusables/pages/about-private-publishing.md b/translations/pt-BR/data/reusables/pages/about-private-publishing.md index f4c5a98628..17f798978e 100644 --- a/translations/pt-BR/data/reusables/pages/about-private-publishing.md +++ b/translations/pt-BR/data/reusables/pages/about-private-publishing.md @@ -1 +1 @@ -Se o seu site de projeto for publicado de um repositório privado ou interno pertencente a uma organização que usa {% data variables.product.prodname_ghe_cloud %}, você poderá gerenciar o controle de acesso para o site. +Se o seu site de projeto for publicado de um repositório privado ou interno pertencente a uma organização que usa {% data variables.product.prodname_ghe_cloud %}, você poderá gerenciar o controle de acesso para o site. In an {% data variables.product.prodname_emu_enterprise %}, all {% data variables.product.prodname_pages %} sites are privately published. diff --git a/translations/pt-BR/data/reusables/pages/decide-publishing-source.md b/translations/pt-BR/data/reusables/pages/decide-publishing-source.md index bde5e1718d..34567f7069 100644 --- a/translations/pt-BR/data/reusables/pages/decide-publishing-source.md +++ b/translations/pt-BR/data/reusables/pages/decide-publishing-source.md @@ -1 +1 @@ -1. {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 2" ou currentVersion == "github-ae@latest" %}Decida{% else %}Se você estiver criando um site de projeto, decida{% endif %} qual fonte de publicação você deseja usar. {% if currentVersion ver_lt "enterprise-server@2. 3" %}Se você estiver criando um site de usuário ou organização, você deverá armazenar o código-fonte do seu site no branch `mestre`.{% endif %} Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)". +1. {% ifversion fpt or ghes > 2.22 or ghae %}Decida{% else %}se você está criando um site de projeto, decida{% endif %} qual fonte de publicação você deseja usar. {% ifversion ghes < 3.0 %}Se você estiver criando um site de usuário ou organização, você deverá armazenar o código-fonte do seu site no branch `mestre`.{% endif %} Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)." 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 041d949ef2..b044542303 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{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" or currentVersion == "github-ae@latest" %} 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)." +Você pode vincular um pull request a um problema para{% ifversion fpt or ghes or ghae %} mostrar que uma correção está em andamento e para{% endif %} fechar automaticamente o problema quando alguém fizer merge do pull request. Para obter mais informações, consulte "[Vincular um pull request a um problema](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)." diff --git a/translations/pt-BR/data/reusables/repositories/auto-gen-release-public-beta.md b/translations/pt-BR/data/reusables/repositories/auto-gen-release-public-beta.md new file mode 100644 index 0000000000..1271ce25e0 --- /dev/null +++ b/translations/pt-BR/data/reusables/repositories/auto-gen-release-public-beta.md @@ -0,0 +1 @@ +Automatically generated release notes are currently in public beta and subject to change. diff --git a/translations/pt-BR/data/reusables/repositories/disabling-markdown-rendering.md b/translations/pt-BR/data/reusables/repositories/disabling-markdown-rendering.md new file mode 100644 index 0000000000..86254f64ec --- /dev/null +++ b/translations/pt-BR/data/reusables/repositories/disabling-markdown-rendering.md @@ -0,0 +1,5 @@ +When viewing a Markdown file, you can click {% octicon "code" aria-label="The code icon" %} at the top of the file to disable Markdown rendering and view the file's source instead. + +![Display Markdown as source](/assets/images/help/writing/display-markdown-as-source.png) + +Disabling Markdown rendering enables you to use source view features, such as line linking, which is not possible when viewing rendered Markdown files. diff --git a/translations/pt-BR/data/reusables/repositories/request-security-advisory-cve-id.md b/translations/pt-BR/data/reusables/repositories/request-security-advisory-cve-id.md index d149378289..ed17a1d32e 100644 --- a/translations/pt-BR/data/reusables/repositories/request-security-advisory-cve-id.md +++ b/translations/pt-BR/data/reusables/repositories/request-security-advisory-cve-id.md @@ -1,5 +1,3 @@ -Se você ainda não tem um número de identificação CVE para a vulnerabilidade de segurança no seu projeto, você pode solicitar um número de identificação CVE a partir de {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_dotcom %} geralmente revisa o pedido em 72 horas. Solicitar um número de identificação CVE não torna público a sua consultoria de segurança público. Se a sua consultoria de segurança for elegível para um CVE, {% data variables.product.prodname_dotcom %} reservará um número de identificação CVE para sua consultoria. Posteriormente, publicaremos os dados do CVE após publicar a consultoria de segurança. +If you want a CVE identification number for the security vulnerability in your project, and don't already have one, you can request a CVE identification number from {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_dotcom %} geralmente revisa o pedido em 72 horas. Solicitar um número de identificação CVE não torna público a sua consultoria de segurança público. If your security advisory is eligible for a CVE, {% data variables.product.prodname_dotcom %} will reserve a CVE identification number for your advisory. We'll then publish the CVE details after you make your security advisory public. Anyone with admin permissions to a security advisory can request a CVE identification number. -Se você já tem um CVE que você deseja usar, por exemplo, se você usar um CNA diferente de {% data variables.product.prodname_dotcom %}, adicione-o ao formulário de consultoria de segurança. Isso pode acontecer, por exemplo, se você quiser que a consultoria seja consistente com outras comunicações que pretende enviar no horário da publicação. - -Se um formulário de consultoria não tiver um CVE, vamos solicitar um CVE para você quando você publicar a consultoria. +If you already have a CVE you want to use, for example, if you use a CVE Numbering Authority (CNA) other than {% data variables.product.prodname_dotcom %}, add the CVE to the security advisory form. Isso pode acontecer, por exemplo, se você quiser que a consultoria seja consistente com outras comunicações que pretende enviar no horário da publicação. {% data variables.product.prodname_dotcom %} cannot assign CVEs to your project if it is covered by another CNA. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/repositories/sidebar-issues.md b/translations/pt-BR/data/reusables/repositories/sidebar-issues.md index ff52e8fea6..dd2597f31a 100644 --- a/translations/pt-BR/data/reusables/repositories/sidebar-issues.md +++ b/translations/pt-BR/data/reusables/repositories/sidebar-issues.md @@ -1,5 +1,5 @@ 2. Abaixo do nome do seu repositório, clique em {% octicon "issue-opened" aria-label="The issues icon" %} **Problemas**. - {% ifversion fpt or ghes > 3.1 or ghae-issue-4483 %} + {% ifversion fpt or ghes > 3.1 or ghae-next %} ![Aba de problemas](/assets/images/help/repository/repo-tabs-issues.png){% else %} ![Issues tab](/assets/images/enterprise/3.1/help/repository/repo-tabs-issues.png){% endif %} diff --git a/translations/pt-BR/data/reusables/repositories/sidebar-pr.md b/translations/pt-BR/data/reusables/repositories/sidebar-pr.md index 362c246441..6d4417b3bd 100644 --- a/translations/pt-BR/data/reusables/repositories/sidebar-pr.md +++ b/translations/pt-BR/data/reusables/repositories/sidebar-pr.md @@ -1,5 +1,5 @@ 1. Abaixo do nome do seu repositório, clique em {% octicon "git-pull-request" aria-label="The pull request icon" %} **Pull requests**. - {% ifversion fpt or ghes > 3.1 or ghae-issue-4483 %} + {% ifversion fpt or ghes > 3.1 or ghae-next %} ![Problemas e seleção da guia pull requests](/assets/images/help/repository/repo-tabs-pull-requests.png){% else %} ![Issues tab](/assets/images/enterprise/3.1/help/repository/repo-tabs-pull-requests.png){% 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 e46622acd1..5f58d2486d 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 @@ -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 9" ou currentVersion == "github-ae@latest" %}Se houver uma regra de branch protegido no repositório que exija um histórico de commit linear. você deve permitir merge de combinação por squash, merge de rebase ou ambos. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)."{% endif %} +{% ifversion fpt or ghes or ghae %}Se houver uma regra de branch protegido no seu repositório que exija um histórico de commit linear, você deverá permitir a combinação por squash, merge, merge de rebase ou ambos. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)."{% endif %} diff --git a/translations/pt-BR/data/reusables/repositories/suggest-changes.md b/translations/pt-BR/data/reusables/repositories/suggest-changes.md index 7405d386dd..61553e5960 100644 --- a/translations/pt-BR/data/reusables/repositories/suggest-changes.md +++ b/translations/pt-BR/data/reusables/repositories/suggest-changes.md @@ -1 +1 @@ -1. Opcionalmente, para sugerir uma alteração específica à linha{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2. 0" ou currentVersion == "github-ae@latest" %} ou linhas{% endif %}, clique em {% octicon "diff" aria-label="The diff symbol" %} e, em seguida, edite o texto dentro do bloco de sugestão. ![Bloco de sugestão](/assets/images/help/pull_requests/suggestion-block.png) +1. Opcionalmente, para sugerir uma alteração específica à linha{% ifversion fpt or ghes or ghae %} ou linhas{% endif %}, clique em {% octicon "diff" aria-label="The diff symbol" %} e, em seguida, edite o texto dentro do bloco de sugestão. ![Bloco de sugestão](/assets/images/help/pull_requests/suggestion-block.png) diff --git a/translations/pt-BR/data/reusables/repositories/workflow-notifications.md b/translations/pt-BR/data/reusables/repositories/workflow-notifications.md index e7d3734ce1..821bb69254 100644 --- a/translations/pt-BR/data/reusables/repositories/workflow-notifications.md +++ b/translations/pt-BR/data/reusables/repositories/workflow-notifications.md @@ -1,4 +1,4 @@ -Se você habilitar o e-mail ou as notificações da web para {% data variables.product.prodname_actions %}, você receberá uma notificação quando qualquer fluxo de trabalho que tenha sido acionado for concluído. A notificação incluirá o status da execução do fluxo de trabalho (incluindo execuções bem-sucedidas, com falhas, neutras e canceladas). Também pode optar por receber uma notificação apenas quando a execução de um fluxo de trabalho falhar. +Se você habilitar o e-mail ou as notificações da web para {% data variables.product.prodname_actions %}, você receberá uma notificação quando qualquer fluxo de trabalho que tenha sido acionado for concluído. A notificação incluirá o status da execução do fluxo de trabalho (incluindo execuções bem-sucedidas, com falhas, neutras e canceladas). Também pode optar por receber uma notificação apenas quando a execução de um fluxo de trabalho falhar. For more information about enabling or disabling notifications, see "[About notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)." As notificações de fluxos de trabalho agendados são enviadas ao usuário que inicialmente criou o fluxo de trabalho. Se um usuário diferente atualizar a sintaxe de cron no arquivo de fluxo de trabalho, as notificações subsequentes serão enviadas para esse usuário.{% ifversion fpt or ghes > 2.22 %} Se um fluxo de trabalho programado for desabilitado e depois reabilitado, as notificações serão enviadas ao usuário que reabilitou o fluxo de trabalho em vez de serem enviadas ao usuário que modificou a sintaxe de cron.{% endif %} diff --git a/translations/pt-BR/data/reusables/saml/about-linked-identities.md b/translations/pt-BR/data/reusables/saml/about-linked-identities.md index 51556686f5..d85f3f9376 100644 --- a/translations/pt-BR/data/reusables/saml/about-linked-identities.md +++ b/translations/pt-BR/data/reusables/saml/about-linked-identities.md @@ -1,3 +1,3 @@ -Você pode visualizar a identidade de logon único que um integrante vinculou à sua conta de {% data variables.product.product_name %} Quando disponível, a entrada incluirá dados de SCIM. Para obter mais informações, consulte "[Sobre o SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)". +Você pode visualizar a identidade de logon único que um integrante vinculou à sua conta de {% data variables.product.product_name %} Se um integrante vincular a identidade incorreta à sua conta de {% data variables.product.product_name %}, você poderá revogar a identidade vinculada para permitir que o integrante tente novamente. 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 eee0c20624..d347c8f178 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 @@ -1,7 +1,7 @@ | Provider | Segredo compatível | Slug da API | | -------- | ------------------ | ----------- | | | | | -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Adafruit IO | Adafruit IO Key | adafruit_io_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Adobe | Adobe Device Token | adobe_device_token{% endif %} @@ -11,73 +11,73 @@ Adobe | Adobe Service Token | adobe_service_token{% endif %} Adobe | Adobe Short-Lived Access Token | adobe_short_lived_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Adobe | Adobe JSON Web Token | adobe_jwt{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Alibaba Cloud | Alibaba Cloud Access Key ID | alibaba_cloud_access_key_id{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Alibaba Cloud | Alibaba Cloud Access Key Secret | alibaba_cloud_access_key_secret{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Amazon Web Services (AWS) | Amazon AWS Access Key ID | aws_access_key_id{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Amazon Web Services (AWS) | Amazon AWS Secret Access Key | aws_secret_access_key{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Amazon Web Services (AWS) | Amazon AWS Session Token | aws_session_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Amazon Web Services (AWS) | Amazon AWS Temporary Access Key ID | aws_temporary_access_key_id{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Asana | Asana Personal Access Token | asana_personal_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Atlassian | Atlassian API Token | atlassian_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Atlassian | Atlassian JSON Web Token | atlassian_jwt{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Atlassian | Bitbucket Server Personal Access Token | bitbucket_server_personal_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Azure | Azure SAS Token | azure_sas_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Azure | Azure Service Management Certificate | azure_management_certificate{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Azure | Azure SQL Connection String | azure_sql_connection_string{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Azure | Azure Storage Account Key | azure_storage_account_key{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Beamer | Beamer API Key | beamer_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Checkout.com | Checkout.com Production Secret Key | checkout_production_secret_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Checkout.com | Checkout.com Test Secret Key | checkout_test_secret_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Clojars | Clojars Deploy Token | clojars_deploy_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} CloudBees CodeShip | CloudBees CodeShip Credential | codeship_credential{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Contentful | Contentful Personal Access Token | contentful_personal_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Databricks | Databricks Access Token | databricks_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Discord | Discord Bot Token | discord_bot_token{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Doppler | Doppler Personal Token | doppler_personal_token{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Doppler | Doppler Service Token | doppler_service_token{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Doppler | Doppler CLI Token | doppler_cli_token{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Doppler | Doppler SCIM Token | doppler_scim_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Doppler | Doppler Audit Token | doppler_audit_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Dropbox | Dropbox Access Token | dropbox_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Dropbox | Dropbox Short Lived Access Token | dropbox_short_lived_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Duffel | Duffel Live Access Token | duffel_live_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Duffel | Duffel Test Access Token | duffel_test_access_token{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Dynatrace | Dynatrace Access Token | dynatrace_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Dynatrace | Dynatrace Internal Token | dynatrace_internal_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} EasyPost | EasyPost Production API Key | easypost_production_api_key{% endif %} @@ -87,17 +87,17 @@ EasyPost | EasyPost Test API Key | easypost_test_api_key{% endif %} Facebook | Facebook Access Token | facebook_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Fastly | Fastly API Token | fastly_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Finicity | Finicity App Key | finicity_app_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Flutterwave | Flutterwave Live API Secret Key | flutterwave_live_api_secret_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Flutterwave | Flutterwave Test API Secret Key | flutterwave_test_api_secret_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Frame.io | Frame.io JSON Web Token | frameio_jwt{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Frame.io| Frame.io Developer Token | frameio_developer_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} FullStory | FullStory API Key | fullstory_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} GitHub | GitHub Personal Access Token | github_personal_access_token{% endif %} @@ -107,29 +107,29 @@ GitHub | GitHub OAuth Access Token | github_oauth_access_token{% endif %} GitHub | GitHub Refresh Token | github_refresh_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} GitHub | GitHub App Installation Access Token | github_app_installation_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} GitHub | GitHub SSH Private Key | github_ssh_private_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} GoCardless | GoCardless Live Access Token | gocardless_live_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} GoCardless | GoCardless Sandbox Access Token | gocardless_sandbox_access_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Google | Firebase Cloud Messaging Server Key | firebase_cloud_messaging_server_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Google | Google API Key | google_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Google | Google Cloud Private Key ID | google_cloud_private_key_id{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Google | Google Cloud Storage Access Key Secret | google_cloud_storage_access_key_secret{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Google | Google Cloud Storage Service Account Access Key ID | google_cloud_storage_service_account_access_key_id{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Google | Google Cloud Storage User Access Key ID | google_cloud_storage_user_access_key_id{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Grafana | Grafana API Key | grafana_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Hashicorp Terraform | Terraform Cloud / Enterprise API Token | terraform_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Hubspot | Hubspot API Key | hubspot_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Intercom | Intercom Access Token | intercom_access_token{% endif %} @@ -137,9 +137,9 @@ Intercom | Intercom Access Token | intercom_access_token{% endif %} Ionic | Ionic Personal Access Token | ionic_personal_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Ionic | Ionic Refresh Token | ionic_refresh_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} JFrog | JFrog Platform Access Token | jfrog_platform_access_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} JFrog | JFrog Platform API Key | jfrog_platform_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Linear | Linear API Key | linear_api_key{% endif %} @@ -149,15 +149,23 @@ Linear | Linear OAuth Access Token | linear_oauth_access_token{% endif %} Lob | Lob Live API Key | lob_live_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Lob | Lob Test API Key | lob_test_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Mailchimp | Mailchimp API Key | mailchimp_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Mailgun | Mailgun API Key | mailgun_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} MessageBird | MessageBird API Key | messagebird_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} +New Relic | New Relic Personal API Key | new_relic_personal_api_key{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +New Relic | New Relic REST API Key | new_relic_rest_api_key{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +New Relic | New Relic Insights Query Key | new_relic_insights_query_key{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +New Relic | New Relic License Key | new_relic_license_key{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} npm | npm Access Token | npm_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} NuGet | NuGet API Key | nuget_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Onfido | Onfido Live API Token | onfido_live_api_token{% endif %} @@ -165,75 +173,75 @@ Onfido | Onfido Live API Token | onfido_live_api_token{% endif %} Onfido | Onfido Sandbox API Token | onfido_sandbox_api_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} OpenAI | OpenAI API Key | openai_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Palantir | Palantir JSON Web Token | palantir_jwt{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} PlanetScale | PlanetScale Database Password | planetscale_database_password{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} PlanetScale | PlanetScale OAuth Token | planetscale_oauth_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} PlanetScale | PlanetScale Service Token | planetscale_service_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Plivo | Plivo Auth ID | plivo_auth_id{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Plivo | Plivo Auth Token | plivo_auth_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Postman | Postman API Key | postman_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Proctorio | Proctorio Consumer Key | proctorio_consumer_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Proctorio | Proctorio Linkage Key | proctorio_linkage_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Proctorio | Proctorio Registration Key | proctorio_registration_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Proctorio | Proctorio Secret Key | proctorio_secret_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Pulumi | Pulumi Access Token | pulumi_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} PyPI | PyPI API Token | pypi_api_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} RubyGems | RubyGems API Key | rubygems_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Samsara | Samsara API Token | samsara_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Samsara | Samsara OAuth Access Token | samsara_oauth_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} SendGrid | SendGrid API Key | sendgrid_api_key{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Sendinblue | Sendinblue API Key | sendinblue_api_key{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Sendinblue | Sendinblue SMTP Key | sendinblue_smtp_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Shippo | Shippo Live API Token | shippo_live_api_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Shippo | Shippo Test API Token | shippo_test_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Shopify | Shopify App Shared Secret | shopify_app_shared_secret{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Shopify | Shopify Access Token | shopify_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Shopify | Shopify Custom App Access Token | shopify_custom_app_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Shopify | Shopify Private App Password | shopify_private_app_password{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Slack | Slack API Token | slack_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Slack | Slack Incoming Webhook URL | slack_incoming_webhook_url{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Slack | Slack Workflow Webhook URL | slack_workflow_webhook_url{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} SSLMate | SSLMate API Key | sslmate_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} SSLMate | SSLMate Cluster Secret | sslmate_cluster_secret{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Stripe | Stripe API Key | stripe_api_key{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Stripe | Stripe Live API Secret Key | stripe_live_secret_key{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Stripe | Stripe Test API Secret Key | stripe_test_secret_key{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Stripe | Stripe Live API Restricted Key | stripe_live_restricted_key{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Stripe | Stripe Test API Restricted Key | stripe_test_restricted_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Stripe | Stripe Webhook Signing Secret | stripe_webhook_signing_secret{% endif %} @@ -241,9 +249,9 @@ Stripe | Stripe Webhook Signing Secret | stripe_webhook_signing_secret{% endif % Tableau | Tableau Personal Access Token | tableau_personal_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Telegram | Telegram Bot Token | telegram_bot_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Tencent Cloud | Tencent Cloud Secret ID | tencent_cloud_secret_id{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Twilio | Twilio Account String Identifier | twilio_account_sid{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Twilio | Twilio API Key | twilio_api_key{% endif %} diff --git a/translations/pt-BR/data/reusables/sponsors/add-welcome-message.md b/translations/pt-BR/data/reusables/sponsors/add-welcome-message.md new file mode 100644 index 0000000000..8962236ad1 --- /dev/null +++ b/translations/pt-BR/data/reusables/sponsors/add-welcome-message.md @@ -0,0 +1 @@ +1. Optionally, type a welcome message for the tier. ![Add welcome message](/assets/images/help/sponsors/add-a-welcome-message.png) \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/sponsors/tier-details.md b/translations/pt-BR/data/reusables/sponsors/tier-details.md index c9aa9b524a..dc63a59f4d 100644 --- a/translations/pt-BR/data/reusables/sponsors/tier-details.md +++ b/translations/pt-BR/data/reusables/sponsors/tier-details.md @@ -1,4 +1,4 @@ -Você pode criar até 10 camadas únicas de patrocínio e 10 camadas mensais para os patrocinadores escolherem. Cada camada tem seu próprio valor de pagamento mensal em dólar e você pode escolher habilitar camadas para valores personalizados. Além disso, você pode optar por habilitar as camadas para quantidades personalizadas (mensais e únicas). +You can create up to 10 one-time sponsorship tiers and 10 monthly tiers for sponsors to choose from. Cada camada tem seu próprio valor de pagamento mensal em dólar e você pode escolher habilitar camadas para valores personalizados. Além disso, você pode optar por habilitar as camadas para quantidades personalizadas (mensais e únicas). Você pode personalizar as recompensas para cada camada. Por exemplo, as recompensas para uma camada poderiam incluir: - Acesso antecipado a novas versões @@ -7,4 +7,6 @@ Você pode personalizar as recompensas para cada camada. Por exemplo, as recompe - Atualizações semanais do boletim informativo - Outras recompensas que seus patrocinadores gostariam ✨ +You can include a welcome message with information about accessing or receiving rewards, which will be visible after payment and in the welcome email. + Depois de publicar uma camada, você não pode editar o preço dessa camada. Em vez disso, você deve se retirar a camada e criar uma nova. Os patrocinadores existentes permanecerão na camada retirada até que mudem a sua camada de patrocínio, cancelem seu patrocínio ou seu período de patrocínio único vença. diff --git a/translations/pt-BR/data/reusables/ssh/add-ssh-key-to-ssh-agent-commandline.md b/translations/pt-BR/data/reusables/ssh/add-ssh-key-to-ssh-agent-commandline.md index 415f86736d..9bed61119b 100644 --- a/translations/pt-BR/data/reusables/ssh/add-ssh-key-to-ssh-agent-commandline.md +++ b/translations/pt-BR/data/reusables/ssh/add-ssh-key-to-ssh-agent-commandline.md @@ -1,3 +1,3 @@ ```shell -$ ssh-add ~/.ssh/id_ed25519 +$ ssh-add ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %} ``` diff --git a/translations/pt-BR/data/reusables/ssh/add-ssh-key-to-ssh-agent.md b/translations/pt-BR/data/reusables/ssh/add-ssh-key-to-ssh-agent.md index f8573a36b1..43243b9f14 100644 --- a/translations/pt-BR/data/reusables/ssh/add-ssh-key-to-ssh-agent.md +++ b/translations/pt-BR/data/reusables/ssh/add-ssh-key-to-ssh-agent.md @@ -1 +1 @@ -Se você criou sua chave com um nome diferente ou se você estiver adicionando uma chave existente com um nome diferente, substitua *id_ed25519* no comando pelo nome do seu arquivo de chave privada. +If you created your key with a different name, or if you are adding an existing key that has a different name, replace *id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}* in the command with the name of your private key file. diff --git a/translations/pt-BR/data/reusables/user_settings/about-commit-email-addresses.md b/translations/pt-BR/data/reusables/user_settings/about-commit-email-addresses.md index 4aa11c15f2..104e287dcd 100644 --- a/translations/pt-BR/data/reusables/user_settings/about-commit-email-addresses.md +++ b/translations/pt-BR/data/reusables/user_settings/about-commit-email-addresses.md @@ -1 +1 @@ -Para obter mais informações sobre endereços de e-mail de commit,{% if currentVersion == "free-pro-team@latest" %} incluindo seu endereço de e-mail `noreply` fornecido por{% data variables.product.product_name %},{% endif %} consulte "[Configurar seu endereço de e-mail do commit](/articles/setting-your-commit-email-address)." +Para obter mais informações sobre endereços de e-mail de commit,{% ifversion fpt %} incluindo seu endereço de e-mail `noreply` fornecido por{% data variables.product.product_name %},{% endif %} consulte "[Configurar seu endereço de e-mail do commit](/articles/setting-your-commit-email-address)." diff --git a/translations/pt-BR/data/reusables/user_settings/generate_new_token.md b/translations/pt-BR/data/reusables/user_settings/generate_new_token.md new file mode 100644 index 0000000000..a537cbf32b --- /dev/null +++ b/translations/pt-BR/data/reusables/user_settings/generate_new_token.md @@ -0,0 +1 @@ +1. Clique em **Generate new token** (Gerar novo token). ![Botão Generate new token (Gerar novo token)](/assets/images/help/settings/generate_new_token.png) \ No newline at end of file diff --git a/translations/pt-BR/data/ui.yml b/translations/pt-BR/data/ui.yml index f9da550f50..7f46e8192c 100644 --- a/translations/pt-BR/data/ui.yml +++ b/translations/pt-BR/data/ui.yml @@ -30,9 +30,10 @@ toc: guides: Guias whats_new: O que há de novo pages: - article_version: 'Versão do artigo:' + article_version: 'Versão do artigo' miniToc: Neste artigo contributor_callout: This article is contributed and maintained by + all_enterprise_releases: All Enterprise releases errors: oops: Ops! something_went_wrong: Parece que algo deu errado. @@ -155,13 +156,17 @@ product_sublanding: learning_paths_desc: Os caminhos de aprendizado são uma coleção de guias que ajudam você a dominar um assunto específico. guides: '{{ productMap[currentProduct].name }} guides' more_guides: mais guias - no_result: Sorry, there are no guides that match your filter. load_more: Carregar mais guias all_guides: 'All {{ productMap[currentProduct].name }} guides' + filter_instructions: Filter the guide list using these controls filters: type: Tipo topic: Tópico all: Todas + guides_found: + multiple: '{n} guides found' + one: 1 guide found + none: No guides found guide_types: overview: Visão Geral quick_start: QuickStart diff --git a/translations/pt-BR/data/variables/product.yml b/translations/pt-BR/data/variables/product.yml index ff7f05c9da..8e84e033de 100644 --- a/translations/pt-BR/data/variables/product.yml +++ b/translations/pt-BR/data/variables/product.yml @@ -76,6 +76,14 @@ prodname_actions: 'GitHub Actions' prodname_debug: 'GitHub Debug' #GitHub Discussions prodname_discussions: 'GitHub Discussions' +#GitHub Enterprise Managed Users +prodname_emu_idp_application: 'GitHub Enterprise Managed User' +prodname_emus: 'Enterprise Managed Users' +prodname_managed_user: 'managed user' +prodname_managed_users: 'managed users' +prodname_managed_users_caps: 'Managed users' +prodname_emu_enterprise: 'enterprise with managed users' +prodname_emu_org: 'organization with managed users' #GitHub Issues prodname_github_issues: 'Problemas do GitHub' #GitHub Packages @@ -94,6 +102,7 @@ prodname_security_center: 'Security Center' #Codespaces prodname_codespaces: 'Codespaces' prodname_github_codespaces: 'GitHub Codespaces' +prodname_serverless: 'editor baseado na web' #GitHub resources: blog, jobs, Learning Lab prodname_gcf: 'Suporte à Comunidade GitHub' prodname_blog: 'GitHub Blog' @@ -135,6 +144,8 @@ prodname_dependabot_version_updates: 'Atualizações de versão do Dependabot' #GitHub Archive Program prodname_archive: 'Programa Arquivo do GitHub' prodname_arctic_vault: 'Cofre de Código do Ártico' +#GitHub Copilot +prodname_copilot: 'GitHub Copilot' #Links product_url: >- {% ifversion fpt %}github.com{% else %}[hostname]{% endif %} diff --git a/translations/pt-BR/data/variables/release_candidate.yml b/translations/pt-BR/data/variables/release_candidate.yml index e6ddf079ac..ec65ef6f94 100644 --- a/translations/pt-BR/data/variables/release_candidate.yml +++ b/translations/pt-BR/data/variables/release_candidate.yml @@ -1,2 +1,2 @@ --- -version: enterprise-server@3.2 +version: '' diff --git a/translations/ru-RU/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md b/translations/ru-RU/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md index 92de06f4d9..b35abe777d 100644 --- a/translations/ru-RU/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md +++ b/translations/ru-RU/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md @@ -45,7 +45,7 @@ When you unsubscribe from notifications in your inbox, they will automatically d {% data reusables.notifications.access_notifications %} 1. From the notifications inbox, select the notifications you want to unsubscribe to. -2. Use the **selected** {% octicon "triangle-down" aria-label="The down triangle icon" %} drop-down to click **Unsubscribe.** ![Unsubscribe option from main inbox](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png) +2. Click **Unsubscribe.** ![Unsubscribe option from main inbox](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png) ## Unsubscribing from notifications on the subscriptions page @@ -61,13 +61,12 @@ When you unwatch a repository, you unsubscribe from future updates from that rep {% data reusables.notifications.access_notifications %} 1. In the left sidebar, under the list of repositories, use the "Manage notifications" drop-down to click **Watched repositories**. ![Manage notifications drop down menu options](/assets/images/help/notifications-v2/manage-notifications-options.png) 2. On the watched repositories page, after you've evaluated the repositories you're watching, choose whether to: - {% ifversion ghae or ghes < 3.1 %} - - Unwatch a repository - - Only watch releases for a repository - - Ignore all notifications for a repository - {% endif %} {% ifversion fpt or ghes > 3.0 or ghae-next %} - Unwatch a repository - Ignore all notifications for a repository - Customize the types of event you receive notifications for ({% data reusables.notifications-v2.custom-notification-types %}, if enabled) + {% else %} + - Unwatch a repository + - Only watch releases for a repository + - Ignore all notifications for a repository {% endif %} diff --git a/translations/ru-RU/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md b/translations/ru-RU/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md index ecdd8e46c2..3faab8afd4 100644 --- a/translations/ru-RU/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md +++ b/translations/ru-RU/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md @@ -70,10 +70,10 @@ Many people forget about repositories that they've chosen to watch in the past. 1. In the left sidebar, under the list of repositories, use the "Manage notifications" drop-down menu and click **Watched repositories**. ![Manage notifications drop down menu options](/assets/images/help/notifications-v2/manage-notifications-options.png) 2. Evaluate the repositories that you are watching and decide if their updates are still relevant and helpful. When you watch a repository, you will be notified of all conversations for that repository. -{% ifversion ghae or ghes < 3.1 %} - ![Watched notifications page](/assets/images/help/notifications-v2/watched-notifications.png) -{% elsif fpt or ghes > 3.0 or ghae-next %} +{% ifversion fpt or ghes > 3.0 or ghae-next %} ![Watched notifications page](/assets/images/help/notifications-v2/watched-notifications-custom.png) +{% else %} + ![Watched notifications page](/assets/images/help/notifications-v2/watched-notifications.png) {% endif %} {% tip %} diff --git a/translations/ru-RU/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md b/translations/ru-RU/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md index 32f3efe5f6..a0b286312a 100644 --- a/translations/ru-RU/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md +++ b/translations/ru-RU/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md @@ -29,7 +29,7 @@ You can choose to subscribe to notifications for: - A conversation in a specific issue, pull request, or gist. - All activity in a repository or team discussion. - CI activity, such as the status of workflows in repositories set up with {% data variables.product.prodname_actions %}. {% ifversion fpt or ghes > 3.0 or ghae-next %} -- Repository {% data reusables.notifications-v2.custom-notification-types %} (if enabled). {% elsif ghae or ghes %} +- Repository {% data reusables.notifications-v2.custom-notification-types %} (if enabled).{% else %} - Releases in a repository.{% endif %} You can also choose to automatically watch all repositories that you have push access to, except forks. You can watch any other repository you have access to manually by clicking **Watch**. diff --git a/translations/ru-RU/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md b/translations/ru-RU/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md index 768fc50caf..6e2ac97819 100644 --- a/translations/ru-RU/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md +++ b/translations/ru-RU/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md @@ -70,12 +70,14 @@ Email notifications also allow flexibility with the types of notifications you r When you watch a repository, you're subscribing to updates for activity in that repository. Similarly, when you watch a specific team's discussions, you're subscribing to all conversation updates on that team's page. For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)." To see repositories that you're watching, go to your [watching page](https://github.com/watching). For more information, see "[Managing subscriptions and notifications on GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)." + {% ifversion ghae or ghes < 3.1 %} ### Configuring notifications {% endif %} -You can configure notifications for a repository on the repository page, or on your watching page.{% ifversion ghae or ghes < 3.1 %} You can choose to only receive notifications for releases in a repository, or ignore all notifications for a repository.{% endif %} +You can configure notifications for a repository on the repository page, or on your watching page.{% ifversion ghes < 3.1 %} You can choose to only receive notifications for releases in a repository, or ignore all notifications for a repository.{% endif %} {% ifversion fpt or ghes > 3.0 or ghae-next %} + ### About custom notifications You can customize notifications for a repository. For example, you can choose to only be notified when updates to one or more types of events ({% data reusables.notifications-v2.custom-notification-types %}) happen within a repository, or ignore all notifications for a repository. {% endif %} For more information, see "[Configuring your watch settings for an individual repository](#configuring-your-watch-settings-for-an-individual-repository)" below. @@ -158,25 +160,18 @@ If "Automatically watch repositories" is disabled, then you will not automatical ## Configuring your watch settings for an individual repository -You can choose whether to watch or unwatch an individual repository. You can also choose to only be notified of {% ifversion fpt or ghes > 3.0 or ghae-next %}certain event types such as {% data reusables.notifications-v2.custom-notification-types %} (if enabled for the repository){% else %}new releases{% endif %}, or completely ignore an individual repository. +You can choose whether to watch or unwatch an individual repository. You can also choose to only be notified of {% ifversion fpt or ghes > 3.0 or ghae-next %}certain event types such as {% data reusables.notifications-v2.custom-notification-types %} (if enabled for the repository) {% else %}new releases{% endif %}, or completely ignore an individual repository. {% data reusables.repositories.navigate-to-repo %} 2. In the upper-right corner, click the "Watch" drop-down menu to select a watch option. -{% ifversion ghae or ghes < 3.1 %} - ![Watch options in a drop-down menu for a repository](/assets/images/help/notifications-v2/watch-repository-options.png) -{% elsif fpt or ghes > 3.0 or ghae-next %} +{% ifversion fpt or ghes > 3.0 or ghae-next %} ![Watch options in a drop-down menu for a repository](/assets/images/help/notifications-v2/watch-repository-options-custom.png) -The **Custom** option allows you to further customize notifications so that you're only notified when specific events happen in the repository, in addition to participating and @mentions. - -{% ifversion fpt or ghes > 3.1 or ghae-issue-4910 %} - ![Custom watch options in a drop-down menu for a repository](/assets/images/help/notifications-v2/watch-repository-options-custom2-dotcom.png) + The **Custom** option allows you to further customize notifications so that you're only notified when specific events happen in the repository, in addition to participating and @mentions. {% else %} - ![Custom watch options in a drop-down menu for a repository](/assets/images/enterprise/3.1/help/notifications-v2/watch-repository-options-custom2.png) -{% endif %} - -If you select "Issues", you will be notified about, and subscribed to, updates on every issue (including those that existed prior to you selecting this option) in the repository. If you're @mentioned in a pull request in this repository, you'll receive notifications for that too, and you'll be subscribed to updates on that specific pull request, in addition to being notified about issues. - + ![Watch options in a drop-down menu for a repository](/assets/images/help/notifications-v2/watch-repository-options.png){% endif %} +{% ifversion fpt or ghes > 3.0 or ghae-next %} + ![Custom watch options in a drop-down menu for a repository](/assets/images/help/notifications-v2/watch-repository-options-custom2-dotcom.png) If you select "Issues", you will be notified about, and subscribed to, updates on every issue (including those that existed prior to you selecting this option) in the repository. If you're @mentioned in a pull request in this repository, you'll receive notifications for that too, and you'll be subscribed to updates on that specific pull request, in addition to being notified about issues. {% endif %} ## Choosing where your organization’s email notifications are sent diff --git a/translations/ru-RU/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md b/translations/ru-RU/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md index 4bc70fcbf4..01e56230f4 100644 --- a/translations/ru-RU/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md +++ b/translations/ru-RU/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md @@ -48,6 +48,14 @@ When you sign up for an account, {% data variables.product.product_name %} provi You can change the name that is displayed on your profile. This name may also be displayed next to comments you make on private repositories owned by an organization. For more information, see "[Managing the display of member names in your organization](/articles/managing-the-display-of-member-names-in-your-organization)." +{% ifversion fpt %} +{% note %} + +**Note:** If you're a member of an {% data variables.product.prodname_emu_enterprise %}, any changes to your profile name must be made through your identity provider instead of {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.emu-more-info-account %} + +{% endnote %} +{% endif %} + {% data reusables.user_settings.access_settings %} 2. Under "Name", type the name you want to be displayed on your profile. ![Name field in profile settings](/assets/images/help/profile/name-field.png) diff --git a/translations/ru-RU/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/index.md b/translations/ru-RU/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/index.md index cac9871846..11dd5764de 100644 --- a/translations/ru-RU/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/index.md +++ b/translations/ru-RU/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/index.md @@ -14,7 +14,7 @@ children: - /viewing-contributions-on-your-profile - /showing-an-overview-of-your-activity-on-your-profile - /publicizing-or-hiding-your-private-contributions-on-your-profile - - /sending-your-github-enterprise-server-contributions-to-your-githubcom-profile + - /sending-enterprise-contributions-to-your-githubcom-profile - /why-are-my-contributions-not-showing-up-on-my-profile - /troubleshooting-commits-on-your-timeline shortTitle: Manage contribution graph diff --git a/translations/ru-RU/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md b/translations/ru-RU/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md index 5965ca5cc5..0b4baf9249 100644 --- a/translations/ru-RU/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md +++ b/translations/ru-RU/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md @@ -14,14 +14,18 @@ topics: shortTitle: Private contributions --- -If you publicize your private contributions, people without access to the private repositories you work in won't be able to see the details of your private contributions. Instead, they'll see the number of private contributions you made on any given day. Your public contributions will include detailed information. For more information, see "[Viewing contributions on your profile page](/articles/viewing-contributions-on-your-profile-page)". +If you publicize your private contributions, people without access to the private repositories you work in won't be able to see the details of your private contributions. Instead, they'll see the number of private contributions you made on any given day. Your public contributions will include detailed information. For more information, see "[Viewing contributions on your profile page](/articles/viewing-contributions-on-your-profile-page)." + +{% note %} + +**Note:** {% ifversion fpt or ghes %}On {% ifversion fpt %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_name %}{% endif %}, public contributions on your profile are visible {% ifversion fpt %}to anyone in the world who can access {% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}only to other users of {% data variables.product.product_location%}{% endif %}.{% elsif ghae %}On {% data variables.product.prodname_ghe_managed %}, only other members of your enterprise can see the contributions on your profile.{% endif %} + +{% endnote %} ## Changing the visibility of your private contributions -By default, visitors only see public contributions on your profile. - {% data reusables.profile.access_profile %} -2. Publicize or hide your private contributions on your profile: +1. Publicize or hide your private contributions on your profile: - To publicize your private contributions, above your contributions graph, use the **Contribution settings** drop-down menu, and select **Private contributions**. Visitors will see your private contribution counts without further details. ![Enable visitors to see private contributions from contribution settings drop-down menu](/assets/images/help/profile/private-contributions-on.png) - To hide your private contributions, above your contributions graph, use the **Contribution settings** drop-down menu, and unselect **Private contributions.** Visitors will only see your public contributions. ![Enable visitors to see private contributions from contribution settings drop-down menu](/assets/images/help/profile/private-contributions-off.png) diff --git a/translations/ru-RU/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md b/translations/ru-RU/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 new file mode 100644 index 0000000000..83c1854ee9 --- /dev/null +++ b/translations/ru-RU/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 @@ -0,0 +1,65 @@ +--- +title: Sending enterprise contributions to your GitHub.com profile +intro: 'You can highlight your work on {% data variables.product.prodname_enterprise %} by sending the contribution counts to your {% data variables.product.prodname_dotcom_the_website %} profile.' +redirect_from: + - /articles/sending-your-github-enterprise-contributions-to-your-github-com-profile/ + - /articles/sending-your-github-enterprise-server-contributions-to-your-github-com-profile + - /articles/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile + - /github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile + - /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile +versions: + fpt: '*' + ghes: '*' + ghae: next +topics: + - Profiles +shortTitle: Send enterprise contributions +--- + +## About enterprise contributions on your {% data variables.product.prodname_dotcom_the_website %} profile + +Your {% data variables.product.prodname_dotcom_the_website %} profile shows {% ifversion fpt %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae-next %} or {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} contribution counts from the past 90 days. {% data reusables.github-connect.sync-frequency %} Contribution counts from {% data variables.product.prodname_enterprise %} are considered private contributions. The commit details will only show the contribution counts and that these contributions were made in a {% data variables.product.prodname_enterprise %} environment outside of {% data variables.product.prodname_dotcom_the_website %}. + +You can decide whether to show counts for private contributions on your profile. For more information, see "[Publicizing or hiding your private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile/)." + +For more information about how contributions are calculated, see "[Managing contribution graphs on your profile](/articles/managing-contribution-graphs-on-your-profile/)." + +{% note %} + +**Замечания:** +- The connection between your accounts is governed by GitHub's Privacy Statement and users enabling the connection agree to the GitHub's Terms of Service. + +- Before you can connect your {% ifversion fpt %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae-next %} or {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} profile to your {% data variables.product.prodname_dotcom_the_website %} profile, your enterprise owner must enable {% data variables.product.prodname_github_connect %} and enable contribution sharing between the environments. For more information, contact your enterprise owner. + +{% endnote %} + +{% ifversion fpt or ghes or ghae %} + +## Sending your enterprise contributions to your {% data variables.product.prodname_dotcom_the_website %} profile + +{% ifversion fpt %} + +- To send enterprise contributions from {% data variables.product.prodname_ghe_server %} to your {% data variables.product.prodname_dotcom_the_website %} profile, see "[Sending enterprise contributions to your {% data variables.product.prodname_dotcom_the_website %} profile](/enterprise-server/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)" in the {% data variables.product.prodname_ghe_server %} documentation.{% ifversion ghae-next %} +- To send enterprise contributions from {% data variables.product.prodname_ghe_managed %} to your {% data variables.product.prodname_dotcom_the_website %} profile, see "[Sending enterprise contributions to your {% data variables.product.prodname_dotcom_the_website %} profile](/github-ae@latest/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)" in the {% data variables.product.prodname_ghe_managed %} documentation.{% endif %} + +{% elsif ghes %} + +1. Sign in to {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_dotcom_the_website %}. +1. On {% data variables.product.prodname_ghe_server %}, in the upper-right corner of any page, click your profile photo, then click **Settings**. ![Settings icon in the user bar](/assets/images/help/settings/userbar-account-settings.png) +{% data reusables.github-connect.github-connect-tab-user-settings %} +{% data reusables.github-connect.connect-dotcom-and-enterprise %} +1. Review the resources that {% data variables.product.prodname_ghe_server %} will access from your {% data variables.product.prodname_dotcom_the_website %} account, then click **Authorize**. ![Authorize connection between GitHub Enterprise Server and GitHub.com](/assets/images/help/settings/authorize-ghe-to-connect-to-dotcom.png) +{% data reusables.github-connect.send-contribution-counts-to-githubcom %} + +{% elsif ghae %} + +1. Sign in to {% data variables.product.prodname_ghe_managed %} and {% data variables.product.prodname_dotcom_the_website %}. +1. On {% data variables.product.prodname_ghe_managed %}, in the upper-right corner of any page, click your profile photo, then click **Settings**. ![Settings icon in the user bar](/assets/images/help/settings/userbar-account-settings.png) +{% data reusables.github-connect.github-connect-tab-user-settings %} +{% data reusables.github-connect.connect-dotcom-and-enterprise %} +{% data reusables.github-connect.authorize-connection %} +{% data reusables.github-connect.send-contribution-counts-to-githubcom %} + +{% endif %} + +{% endif %} diff --git a/translations/ru-RU/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/ru-RU/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md index 68ceda45f6..006aa8787f 100644 --- a/translations/ru-RU/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/ru-RU/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md @@ -83,7 +83,7 @@ Timestamps are calculated differently for commits and pull requests: ![Activity overview section on profile](/assets/images/help/profile/activity-overview-section.png) -The organizations featured in the activity overview are prioritized according to how active you are in the organization. If you @mention an organization in your profile bio, and you’re an organization member, then that organization is prioritized first in the activity overview. For more information, see “[Mentioning people and teams](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)” or "[Adding a bio to your profile](/articles/adding-a-bio-to-your-profile/)." +The organizations featured in the activity overview are prioritized according to how active you are in the organization. If you @mention an organization in your profile bio, and you’re an organization member, then that organization is prioritized first in the activity overview. For more information, see "[Mentioning people and teams](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)” or "[Adding a bio to your profile](/articles/adding-a-bio-to-your-profile/)." ## Contribution activity @@ -91,15 +91,14 @@ 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 not ghae %} -## Viewing contributions from {% data variables.product.product_location_enterprise %} on {% data variables.product.prodname_dotcom_the_website %} +{% ifversion fpt or ghes or ghae-next %} + +## Viewing contributions from {% data variables.product.prodname_enterprise %} on {% data variables.product.prodname_dotcom_the_website %} + +If you use {% ifversion fpt %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae-next %} 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)." -If your site administrator has enabled {% data variables.product.prodname_unified_contributions %}, you can send {% data variables.product.prodname_enterprise %} contribution counts to your {% data variables.product.prodname_dotcom_the_website %} profile. For more information, see "[Sending your {% data variables.product.prodname_ghe_server %} contributions to your {% data variables.product.prodname_dotcom_the_website %}](/articles/sending-your-github-enterprise-server-contributions-to-your-github-com-profile)." {% endif %} ## Дополнительная литература - "[Viewing contributions on your profile page](/articles/viewing-contributions-on-your-profile-page)" -- "[Why are my contributions not showing up on my profile?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)" -- "[Publicizing or hiding your private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)" -- "[Showing an overview of your activity on your profile](/articles/showing-an-overview-of-your-activity-on-your-profile)" diff --git a/translations/ru-RU/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/ru-RU/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md index 7b3f4f9303..0d940099e2 100644 --- a/translations/ru-RU/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/ru-RU/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 @@ -24,6 +24,8 @@ Repositories owned by an organization can grant more granular access. For more i {% ifversion fpt %} +If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you can only invite other members of your enterprise to collaborate with you. {% data reusables.enterprise-accounts.emu-more-info-account %} + {% note %} **Note:** {% data variables.product.company_short %} limits the number of people who can be invited to a repository within a 24-hour period. If you exceed this limit, either wait 24 hours or create an organization to collaborate with more people. diff --git a/translations/ru-RU/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/ru-RU/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md index 5554ec25b7..97d8a0c867 100644 --- a/translations/ru-RU/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/ru-RU/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md @@ -18,7 +18,9 @@ shortTitle: Add an email address {% note %} -**Note**: {% data reusables.user_settings.no-verification-disposable-emails %} +**Notes**: + - {% data reusables.user_settings.no-verification-disposable-emails %} + - If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you cannot make changes to your email address on {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.emu-more-info-account %} {% endnote %} diff --git a/translations/ru-RU/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md b/translations/ru-RU/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md index c92f08aba7..af734c507b 100644 --- a/translations/ru-RU/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md +++ b/translations/ru-RU/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md @@ -31,6 +31,12 @@ After changing your username, your old username becomes available for anyone els - [@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 %} + +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. diff --git a/translations/ru-RU/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md b/translations/ru-RU/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md index 7844819b37..0d56da15cc 100644 --- a/translations/ru-RU/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md +++ b/translations/ru-RU/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md @@ -15,6 +15,7 @@ topics: children: - /about-your-personal-dashboard - /managing-your-theme-settings + - /managing-your-tab-size-rendering-preference - /changing-your-github-username - /merging-multiple-user-accounts - /converting-a-user-into-an-organization diff --git a/translations/ru-RU/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/ru-RU/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md new file mode 100644 index 0000000000..cefff8afe9 --- /dev/null +++ b/translations/ru-RU/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md @@ -0,0 +1,15 @@ +--- +title: Managing your tab size rendering preference +intro: 'You can manage the number of spaces a tab is equal to for your user account.' +versions: + fpt: '*' +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 user settings sidebar, click **Appearance**. !["Appearance" tab in user settings sidebar](/assets/images/help/settings/appearance-tab.png) +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) \ No newline at end of file diff --git a/translations/ru-RU/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md b/translations/ru-RU/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md index c8328cb4c8..51277d6428 100644 --- a/translations/ru-RU/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md +++ b/translations/ru-RU/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md @@ -3,6 +3,7 @@ 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: next ghes: '>=3.2' topics: - Accounts @@ -14,7 +15,15 @@ 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 ghae-issue-4618 %} People with visual impairment may benefit from the dark high contrast theme, with greater contrast between foreground and background elements.{% endif %} +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 ghae-issue-4618 %} 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 %} If you have colorblindness, you may benefit from our light and dark colorblind themes. + +{% note %} + +**Note:** The colorblind themes are currently in public beta. For more information on enabling features in public beta, see "[Exploring early access releases with feature preview](/get-started/using-github/exploring-early-access-releases-with-feature-preview)." + +{% endnote %}{% endif %} {% data reusables.user_settings.access_settings %} 1. In the user settings sidebar, click **Appearance**. !["Appearance" tab in user settings sidebar](/assets/images/help/settings/appearance-tab.png) @@ -24,6 +33,8 @@ You may want to use a dark theme to reduce power consumption on certain devices, {% ifversion fpt or ghae-issue-4618 %}![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 ghae-issue-4618 %}![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 ghae-issue-4619 %} + - 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/ru-RU/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/ru-RU/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md index b3d5097621..fde93544a3 100644 --- a/translations/ru-RU/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/ru-RU/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md @@ -35,7 +35,7 @@ The repository owner has full control of the repository. In addition to the acti | {% ifversion fpt %}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 %} -| Limit interactions with the repository | "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)" |{% endif %}{% ifversion fpt or ghes > 3.0 %} +| Limit interactions with the repository | "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)" |{% endif %}{% ifversion fpt or ghes > 3.0 or ghae-next %} | Rename a branch, including the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" {% endif %} | 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)" | @@ -73,7 +73,7 @@ Collaborators can also perform the following actions. | Действие | More information | |:----------------------------------------------------------------------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Fork the repository | "[About forks](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% ifversion fpt or ghes > 3.1 %} +| Fork the repository | "[About forks](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% ifversion fpt or ghes > 3.1 or ghae-next %} | 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](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)"
    • "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"
    | diff --git a/translations/ru-RU/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md b/translations/ru-RU/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md index d8409a609d..4fca14aff3 100644 --- a/translations/ru-RU/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md +++ b/translations/ru-RU/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md @@ -15,8 +15,6 @@ topics: - Workflows --- -{% data reusables.actions.ae-beta %} - ## About caching workflow dependencies Workflow runs often reuse the same outputs or downloaded dependencies from one run to another. For example, package and dependency management tools such as Maven, Gradle, npm, and Yarn keep a local cache of downloaded dependencies. diff --git a/translations/ru-RU/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md b/translations/ru-RU/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md index 523d9cc7ef..b7576f2e18 100644 --- a/translations/ru-RU/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md +++ b/translations/ru-RU/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md @@ -20,11 +20,10 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About workflow artifacts -Artifacts allow you to persist data after a job has completed, and share that data with another job in the same workflow. An artifact is a file or collection of files produced during a workflow run. For example, you can use artifacts to save your build and test output after a workflow run has ended. +Artifacts allow you to persist data after a job has completed, and share that data with another job in the same workflow. An artifact is a file or collection of files produced during a workflow run. For example, you can use artifacts to save your build and test output after a workflow run has ended. {% data reusables.actions.reusable-workflow-artifacts %} {% data reusables.github-actions.artifact-log-retention-statement %} The retention period for a pull request restarts each time someone pushes a new commit to the pull request. diff --git a/translations/ru-RU/content/actions/automating-builds-and-tests/about-continuous-integration.md b/translations/ru-RU/content/actions/automating-builds-and-tests/about-continuous-integration.md index 3b86554c86..06b02393f0 100644 --- a/translations/ru-RU/content/actions/automating-builds-and-tests/about-continuous-integration.md +++ b/translations/ru-RU/content/actions/automating-builds-and-tests/about-continuous-integration.md @@ -1,6 +1,6 @@ --- title: About continuous integration -intro: 'You can create custom continuous integration (CI) and continuous deployment (CD) workflows directly in your {% data variables.product.prodname_dotcom %} repository with {% data variables.product.prodname_actions %}.' +intro: 'You can create custom continuous integration (CI) workflows directly in your {% data variables.product.prodname_dotcom %} repository with {% data variables.product.prodname_actions %}.' product: '{% data reusables.gated-features.actions %}' redirect_from: - /articles/about-continuous-integration @@ -15,13 +15,11 @@ versions: type: overview topics: - CI - - CD shortTitle: Непрерывная интеграция --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About continuous integration @@ -49,45 +47,12 @@ In addition to helping you set up CI workflows for your project, you can use {% For a definition of common terms, see "[Core concepts for {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/core-concepts-for-github-actions)." -## Supported languages - +## Workflow templates {% data variables.product.product_name %} offers CI workflow templates for a variety of languages and frameworks. Browse the complete list of CI workflow templates offered by {% data variables.product.product_name %} in the {% ifversion fpt %}[actions/starter-workflows](https://github.com/actions/starter-workflows/tree/main/ci) repository{% else %} `actions/starter-workflows` repository on {% data variables.product.product_location %}{% endif %}. -{% ifversion fpt or ghes > 3.0 or ghae-next %} -## Skipping workflow runs - -If you want to temporarily prevent a workflow from being triggered, you can add a skip instruction to the commit message. Workflows that would otherwise be triggered `on: push` or `on: pull_request`, won't be triggered if you add any of the following strings to the commit message in a push, or the HEAD commit of a pull request: - -* `[skip ci]` -* `[ci skip]` -* `[no ci]` -* `[skip actions]` -* `[actions skip]` - -Alternatively, you can end the commit message with two empty lines followed by either `skip-checks: true` or `skip-checks:true`. - -You won't be able to merge the pull request if your repository is configured to require specific checks to pass first. To allow the pull request to be merged you can push a new commit to the pull request without the skip instruction in the commit message. - -{% note %} - -**Note:** Skip instructions only apply to the `push` and `pull_request` events. For example, adding `[skip ci]` to a commit message won't stop a workflow that's triggered `on: pull_request_target` from running. - -{% endnote %} -{% endif %} - -## Notifications for workflow runs - -{% data reusables.repositories.workflow-notifications %} - -## Status badges for workflow runs - -{% 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)." - ## Дополнительная литература {% ifversion fpt %} diff --git a/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md b/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md index 0100f4233e..cbfdfd53e9 100644 --- a/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md +++ b/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md @@ -19,7 +19,6 @@ shortTitle: Build & test Java & Ant {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md b/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md index 632a9060b3..49810a745d 100644 --- a/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md +++ b/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md @@ -19,7 +19,6 @@ shortTitle: Build & test Java & Gradle {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md b/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md index 64e72f3a55..0b687ea6c7 100644 --- a/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md +++ b/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md @@ -19,7 +19,6 @@ shortTitle: Build & test Java with Maven {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-net.md b/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-net.md index e5c2a5367a..3fd1ac849e 100644 --- a/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-net.md +++ b/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-net.md @@ -13,7 +13,6 @@ shortTitle: Build & test .NET {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md b/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md index fa3a09f780..fdd456eeb8 100644 --- a/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md +++ b/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md @@ -22,7 +22,6 @@ hasExperimentalAlternative: true {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-powershell.md b/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-powershell.md index ffa862392e..eee0f17c04 100644 --- a/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-powershell.md +++ b/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-powershell.md @@ -19,7 +19,6 @@ shortTitle: Build & test PowerShell {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-python.md b/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-python.md index 525a7460f4..acc939f0b2 100644 --- a/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-python.md +++ b/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-python.md @@ -21,7 +21,6 @@ hasExperimentalAlternative: true {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-ruby.md b/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-ruby.md index 4f8da2542e..7fdf57f594 100644 --- a/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-ruby.md +++ b/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-ruby.md @@ -17,7 +17,6 @@ shortTitle: Build & test Ruby {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-swift.md b/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-swift.md index 9a4bd84d1e..e02ae5a1de 100644 --- a/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-swift.md +++ b/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-swift.md @@ -17,7 +17,6 @@ shortTitle: Build & test Swift {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md b/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md index cdeddeb0a8..2c6ecfbf17 100644 --- a/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md +++ b/translations/ru-RU/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md @@ -21,7 +21,6 @@ shortTitle: Build & test Xamarin apps {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ru-RU/content/actions/creating-actions/about-custom-actions.md b/translations/ru-RU/content/actions/creating-actions/about-custom-actions.md index 149f4c25f9..94945a8c93 100644 --- a/translations/ru-RU/content/actions/creating-actions/about-custom-actions.md +++ b/translations/ru-RU/content/actions/creating-actions/about-custom-actions.md @@ -20,7 +20,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About custom actions diff --git a/translations/ru-RU/content/actions/creating-actions/creating-a-composite-action.md b/translations/ru-RU/content/actions/creating-actions/creating-a-composite-action.md index aadde45c1f..d5189614ea 100644 --- a/translations/ru-RU/content/actions/creating-actions/creating-a-composite-action.md +++ b/translations/ru-RU/content/actions/creating-actions/creating-a-composite-action.md @@ -16,7 +16,6 @@ shortTitle: Composite action {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ru-RU/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/ru-RU/content/actions/creating-actions/creating-a-docker-container-action.md index 2bf9151a5a..9388b90b08 100644 --- a/translations/ru-RU/content/actions/creating-actions/creating-a-docker-container-action.md +++ b/translations/ru-RU/content/actions/creating-actions/creating-a-docker-container-action.md @@ -20,7 +20,6 @@ shortTitle: Docker container action {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ru-RU/content/actions/creating-actions/creating-a-javascript-action.md b/translations/ru-RU/content/actions/creating-actions/creating-a-javascript-action.md index 89edae7622..e9d8ed5083 100644 --- a/translations/ru-RU/content/actions/creating-actions/creating-a-javascript-action.md +++ b/translations/ru-RU/content/actions/creating-actions/creating-a-javascript-action.md @@ -20,7 +20,6 @@ shortTitle: JavaScript action {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ru-RU/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/translations/ru-RU/content/actions/creating-actions/dockerfile-support-for-github-actions.md index 749bf9ab45..73ee877a94 100644 --- a/translations/ru-RU/content/actions/creating-actions/dockerfile-support-for-github-actions.md +++ b/translations/ru-RU/content/actions/creating-actions/dockerfile-support-for-github-actions.md @@ -14,7 +14,6 @@ type: reference {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About Dockerfile instructions diff --git a/translations/ru-RU/content/actions/creating-actions/index.md b/translations/ru-RU/content/actions/creating-actions/index.md index e8b1782c47..1d7ed199d2 100644 --- a/translations/ru-RU/content/actions/creating-actions/index.md +++ b/translations/ru-RU/content/actions/creating-actions/index.md @@ -24,4 +24,3 @@ children: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} diff --git a/translations/ru-RU/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/ru-RU/content/actions/creating-actions/metadata-syntax-for-github-actions.md index eb76ba46ab..8dd2b8b867 100644 --- a/translations/ru-RU/content/actions/creating-actions/metadata-syntax-for-github-actions.md +++ b/translations/ru-RU/content/actions/creating-actions/metadata-syntax-for-github-actions.md @@ -17,7 +17,6 @@ type: reference {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About YAML syntax for {% data variables.product.prodname_actions %} diff --git a/translations/ru-RU/content/actions/creating-actions/publishing-actions-in-github-marketplace.md b/translations/ru-RU/content/actions/creating-actions/publishing-actions-in-github-marketplace.md index 3026b5055f..38d86b42bc 100644 --- a/translations/ru-RU/content/actions/creating-actions/publishing-actions-in-github-marketplace.md +++ b/translations/ru-RU/content/actions/creating-actions/publishing-actions-in-github-marketplace.md @@ -12,8 +12,6 @@ type: how_to shortTitle: Publish in GitHub Marketplace --- -{% data reusables.actions.ae-beta %} - You must accept the terms of service to publish actions in {% data variables.product.prodname_marketplace %}. ## About publishing actions diff --git a/translations/ru-RU/content/actions/creating-actions/setting-exit-codes-for-actions.md b/translations/ru-RU/content/actions/creating-actions/setting-exit-codes-for-actions.md index 38558040ed..bd4ad15a24 100644 --- a/translations/ru-RU/content/actions/creating-actions/setting-exit-codes-for-actions.md +++ b/translations/ru-RU/content/actions/creating-actions/setting-exit-codes-for-actions.md @@ -14,7 +14,6 @@ type: how_to {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About exit codes @@ -27,7 +26,7 @@ type: how_to ## Setting a failure exit code in a JavaScript action -If you are creating a JavaScript action, you can use the actions toolkit [`@actions/core`](https://github.com/actions/toolkit/tree/master/packages/core) package to log a message and set a failure exit code. Например: +If you are creating a JavaScript action, you can use the actions toolkit [`@actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) package to log a message and set a failure exit code. Например: ```javascript try { diff --git a/translations/ru-RU/content/actions/deployment/about-continuous-deployment.md b/translations/ru-RU/content/actions/deployment/about-continuous-deployment.md new file mode 100644 index 0000000000..9212a77cd4 --- /dev/null +++ b/translations/ru-RU/content/actions/deployment/about-continuous-deployment.md @@ -0,0 +1,41 @@ +--- +title: About continuous deployment +intro: 'You can create custom continuous deployment (CD) workflows directly in your {% data variables.product.prodname_dotcom %} repository with {% data variables.product.prodname_actions %}.' +product: '{% data reusables.gated-features.actions %}' +versions: + fpt: '*' + ghes: '*' + ghae: '*' +type: overview +topics: + - CD +shortTitle: Continuous deployment +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +## About continuous deployment + +_Continuous deployment_ (CD) is the practice of using automation to publish and deploy software updates. As part of the typical CD process, the code is automatically built and tested before deployment. + +Continuous deployment is often coupled with continuous integration. For more information about continuous integration, see "[About continuous integration](/actions/guides/about-continuous-integration)". + +## About continuous deployment using {% data variables.product.prodname_actions %} + +You can set up a {% data variables.product.prodname_actions %} workflow to deploy your software product. To verify that your product works as expected, your workflow can build the code in your repository and run your tests before deploying. + +You can configure your CD workflow to run when a {% data variables.product.product_name %} event occurs (for example, when new code is pushed to the default branch of your repository), on a set schedule, manually, or when an external event occurs using the repository dispatch webhook. For more information about when your workflow can run, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)." + +{% data variables.product.prodname_actions %} provides features that give you more control over deployments. For example, you can use environments to require approval for a job to proceed, restrict which branches can trigger a workflow, or limit access to secrets. You can use concurrency to limit your CD pipeline to a maximum of one in-progress deployment and one pending deployment. For more information about these features, see "[Deploying with GitHub Actions](/actions/deployment/deploying-with-github-actions)" and "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." + +## Workflow templates and third party actions + +{% data reusables.actions.cd-templates-actions %} + +## Дополнительная литература + +- [Deploying with GitHub Actions](/actions/deployment/deploying-with-github-actions) +- [Using environments for deployment](/actions/deployment/using-environments-for-deployment){% ifversion fpt %} +- "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)" +{% endif %} diff --git a/translations/ru-RU/content/actions/deployment/deploying-to-amazon-elastic-container-service.md b/translations/ru-RU/content/actions/deployment/deploying-to-amazon-elastic-container-service.md index 613ca684e7..f017538789 100644 --- a/translations/ru-RU/content/actions/deployment/deploying-to-amazon-elastic-container-service.md +++ b/translations/ru-RU/content/actions/deployment/deploying-to-amazon-elastic-container-service.md @@ -18,11 +18,10 @@ shortTitle: Deploy to Amazon ECS {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction -This guide explains how to use {% data variables.product.prodname_actions %} to build a containerized application, push it to [Amazon Elastic Container Registry (ECR)](https://aws.amazon.com/ecr/), and deploy it to [Amazon Elastic Container Service (ECS)](https://aws.amazon.com/ecs/). +This guide explains how to use {% data variables.product.prodname_actions %} to build a containerized application, push it to [Amazon Elastic Container Registry (ECR)](https://aws.amazon.com/ecr/), and deploy it to [Amazon Elastic Container Service (ECS)](https://aws.amazon.com/ecs/) when a release is created. On every new release in your {% data variables.product.company_short %} repository, the {% data variables.product.prodname_actions %} workflow builds and pushes a new container image to Amazon ECR, and then deploys a new task definition to Amazon ECS. @@ -66,6 +65,8 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you See the documentation for each action used below for the recommended IAM policies for the IAM user, and methods for handling the access key credentials. +5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %} + ## Creating the workflow Once you've completed the prerequisites, you can proceed with creating the workflow. @@ -74,6 +75,8 @@ The following example workflow demonstrates how to build a container image and p Ensure that you provide your own values for all the variables in the `env` key of the workflow. +{% data reusables.actions.delete-env-key %} + ```yaml{:copy} {% data reusables.actions.actions-not-certified-by-github-comment %} @@ -93,17 +96,11 @@ env: CONTAINER_NAME: MY_CONTAINER_NAME # set this to the name of the container in the # containerDefinitions section of your task definition -defaults: - run: - shell: bash - jobs: deploy: name: Deploy - runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae-next %} - permissions: - packages: write - contents: read{% endif %} + runs-on: ubuntu-latest + environment: production {% raw %}steps: - name: Checkout @@ -150,9 +147,10 @@ jobs: wait-for-service-stability: true{% endraw %} ``` - ## Additional resources +For the original starter workflow, see [`aws.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/aws.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository. + For more information on the services used in these examples, see the following documentation: * "[Security best practices in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html)" in the Amazon AWS documentation. diff --git a/translations/ru-RU/content/actions/deployment/deploying-to-azure-app-service.md b/translations/ru-RU/content/actions/deployment/deploying-to-azure-app-service.md index d53ac0a8e1..2beb15e972 100644 --- a/translations/ru-RU/content/actions/deployment/deploying-to-azure-app-service.md +++ b/translations/ru-RU/content/actions/deployment/deploying-to-azure-app-service.md @@ -18,7 +18,6 @@ shortTitle: Deploy to Azure App Service {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction @@ -68,13 +67,19 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you In your {% data variables.product.prodname_dotcom %} repository, create a secret named `AZURE_WEBAPP_PUBLISH_PROFILE` that contains the contents of the publish profile. For more information on creating secrets, see "[Encrypted secrets](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)." +4. For Linux apps, add an app setting called `WEBSITE_WEBDEPLOY_USE_SCM` and set it to true in your app. For more information, see "[Configure apps in the portal](https://docs.microsoft.com/en-us/azure/app-service/configure-common#configure-app-settings)" in the Azure documentation. + +5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %} + ## Creating the workflow Once you've completed the prerequisites, you can proceed with creating the workflow. -The following example workflow demonstrates how to build, test, and deploy the Node.js project to Azure App Service. +The following example workflow demonstrates how to build, test, and deploy the Node.js project to Azure App Service when a release is created. -Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created. +Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created. You can also change `AZURE_WEBAPP_PACKAGE_PATH` if the path to your project is not the repository root and `NODE_VERSION` if you want to use a node version other than `10.x`. + +{% data reusables.actions.delete-env-key %} ```yaml{:copy} {% data reusables.actions.actions-not-certified-by-github-comment %} @@ -92,6 +97,8 @@ jobs: build-and-deploy: name: Build and Deploy runs-on: ubuntu-latest + environment: production + steps: - uses: actions/checkout@v2 @@ -122,4 +129,5 @@ The following resources may also be useful: * For the original starter workflow, see [`azure.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository. * 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/en-us/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). diff --git a/translations/ru-RU/content/actions/deployment/deploying-to-google-kubernetes-engine.md b/translations/ru-RU/content/actions/deployment/deploying-to-google-kubernetes-engine.md index 432b15d64d..fb3dbb17ed 100644 --- a/translations/ru-RU/content/actions/deployment/deploying-to-google-kubernetes-engine.md +++ b/translations/ru-RU/content/actions/deployment/deploying-to-google-kubernetes-engine.md @@ -13,16 +13,15 @@ topics: - CD - Containers - Google Kubernetes Engine -shortTitle: Deploy to Kubernetes (GKE) +shortTitle: Deploy to Google Kubernetes Engine --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction -This guide explains how to use {% data variables.product.prodname_actions %} to build a containerized application, push it to Google Container Registry (GCR), and deploy it to Google Kubernetes Engine (GKE). +This guide explains how to use {% data variables.product.prodname_actions %} to build a containerized application, push it to Google Container Registry (GCR), and deploy it to Google Kubernetes Engine (GKE) when a release is created. GKE is a managed Kubernetes cluster service from Google Cloud that can host your containerized workloads in the cloud or in your own datacenter. For more information, see [Google Kubernetes Engine](https://cloud.google.com/kubernetes-engine). @@ -61,7 +60,7 @@ $ gcloud services enable \ ### Configuring a service account and storing its credentials -This procedure demonstrates how to create the service account for your GKE integration. It explains how to create the account, add roles to it, retrieve its keys, and store them as a base64-encoded [encrypted repository secret](/actions/reference/encrypted-secrets) named `GKE_SA_KEY`. +This procedure demonstrates how to create the service account for your GKE integration. It explains how to create the account, add roles to it, retrieve its keys, and store them as a base64-encoded encrypted repository secret named `GKE_SA_KEY`. 1. Create a new service account: {% raw %} @@ -97,16 +96,29 @@ This procedure demonstrates how to create the service account for your GKE integ $ export GKE_SA_KEY=$(cat key.json | base64) ``` {% endraw %} + For more information about how to store a secret, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)." + +### Storing your project name + +Store the name of your project as a secret named `GKE_PROJECT`. For more information about how to store a secret, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)." ### (Optional) Configuring kustomize Kustomize is an optional tool used for managing YAML specs. After creating a _kustomization_ file, the workflow below can be used to dynamically set fields of the image and pipe in the result to `kubectl`. For more information, see [kustomize usage](https://github.com/kubernetes-sigs/kustomize#usage). +### (Optional) Configure a deployment environment + +{% data reusables.actions.about-environments %} + ## Creating the workflow Once you've completed the prerequisites, you can proceed with creating the workflow. The following example workflow demonstrates how to build a container image and push it to GCR. It then uses the Kubernetes tools (such as `kubectl` and `kustomize`) to pull the image into the cluster deployment. +Under the `env` key, change the value of `GKE_CLUSTER` to the name of your cluster, `GKE_ZONE` to your cluster zone, `DEPLOYMENT_NAME` to the name of your deployment, and `IMAGE` to the name of your image. + +{% data reusables.actions.delete-env-key %} + ```yaml{:copy} {% data reusables.actions.actions-not-certified-by-github-comment %} @@ -127,8 +139,9 @@ jobs: setup-build-publish-deploy: name: Setup, Build, Publish, and Deploy runs-on: ubuntu-latest - steps: + environment: production + steps: - name: Checkout uses: actions/checkout@v2 @@ -138,7 +151,8 @@ jobs: service_account_key: {% raw %}${{ secrets.GKE_SA_KEY }}{% endraw %} project_id: {% raw %}${{ secrets.GKE_PROJECT }}{% endraw %} - # Configure docker to use the gcloud command-line tool as a credential helper + # Configure Docker to use the gcloud command-line tool as a credential + # helper for authentication - run: |- gcloud --quiet auth configure-docker @@ -166,7 +180,7 @@ jobs: # Set up kustomize - name: Set up Kustomize run: |- - curl --location https://github.com/kubernetes-sigs/kustomize/releases/download/kustomize%2Fv4.2.0/kustomize_v4.2.0_linux_amd64.tar.gz | tar xz + curl -sfLo kustomize https://github.com/kubernetes-sigs/kustomize/releases/download/v3.1.0/kustomize_3.1.0_linux_amd64 chmod u+x ./kustomize # Deploy the Docker image to the GKE cluster diff --git a/translations/ru-RU/content/actions/deployment/deploying-with-github-actions.md b/translations/ru-RU/content/actions/deployment/deploying-with-github-actions.md new file mode 100644 index 0000000000..dc576f5ca6 --- /dev/null +++ b/translations/ru-RU/content/actions/deployment/deploying-with-github-actions.md @@ -0,0 +1,173 @@ +--- +title: Deploying with GitHub Actions +intro: Learn how to control deployments with features like environments and concurrency. +product: '{% data reusables.gated-features.actions %}' +versions: + fpt: '*' + ghes: '>=3.1' + ghae: '*' +type: overview +topics: + - CD +shortTitle: Deploy with 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: + +- 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)." + +## Требования + +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)." + +## Triggering your deployment + +You can use a variety of events to trigger your deployment workflow. Some of the most common are: `pull_request`, `push`, `release`, and `workflow_dispatch`. + +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. +- A release is created. +- Someone manually triggers it. + +```yaml +on: + push: + branches: + - main + pull_request: + branches: + - main + release: + types: + - created + workflow_dispatch: +``` + +For more information, see "[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. + +{% 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. + +```yaml +name: Deployment + +concurrency: production + +on: + push: + branches: + - main + +jobs: + deployment: + runs-on: ubuntu-latest + environment: production + steps: + - name: deploy + # ...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`. + +```yaml +name: Deployment + +on: + push: + branches: + - main + +jobs: + deployment: + runs-on: ubuntu-latest + environment: production + concurrency: production + steps: + - name: deploy + # ...deployment-specific steps +``` + +You can also use `cancel-in-progress` to cancel any currently running job or workflow in the same concurrency group. + +```yaml +name: Deployment + +concurrency: + group: production + cancel-in-progress: true + +on: + push: + branches: + - main + +jobs: + deployment: + runs-on: ubuntu-latest + environment: production + steps: + - name: deploy + # ...deployment-specific steps +``` + +## 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)." + +## 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)." + +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)." + +## Tracking deployments through apps + +{% ifversion fpt %} +If your {% data variables.product.product_name %} personal account or organization 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)." +{% 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)." + +{% ifversion fpt or ghes %} + +## Choosing a runner + +You can run your deployment workflow on {% data variables.product.product_name %}-hosted runners or on self-hosted runners. Traffic from {% data variables.product.product_name %}-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.product_name %}-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)." + +{% 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 %} + +For more information, see "[Adding a workflow status badge](/actions/managing-workflow-runs/adding-a-workflow-status-badge)." + +## Дальнейшие шаги + +This article demonstrated features of {% data variables.product.prodname_actions %} that you can add to your deployment workflows. + +{% data reusables.actions.cd-templates-actions %} diff --git a/translations/ru-RU/content/actions/deployment/index.md b/translations/ru-RU/content/actions/deployment/index.md index 2ae385cc62..0fbfa9c440 100644 --- a/translations/ru-RU/content/actions/deployment/index.md +++ b/translations/ru-RU/content/actions/deployment/index.md @@ -7,10 +7,13 @@ versions: ghes: '*' ghae: '*' children: + - /about-continuous-deployment + - /deploying-with-github-actions + - /using-environments-for-deployment + - /viewing-deployment-history - /deploying-to-amazon-elastic-container-service - /deploying-to-azure-app-service - /deploying-to-google-kubernetes-engine - /installing-an-apple-certificate-on-macos-runners-for-xcode-development - - /environments --- diff --git a/translations/ru-RU/content/actions/deployment/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md b/translations/ru-RU/content/actions/deployment/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md index a6ab753cfc..1579d3e367 100644 --- a/translations/ru-RU/content/actions/deployment/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md +++ b/translations/ru-RU/content/actions/deployment/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md @@ -17,7 +17,6 @@ shortTitle: Sign Xcode applications {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ru-RU/content/actions/deployment/using-environments-for-deployment.md b/translations/ru-RU/content/actions/deployment/using-environments-for-deployment.md new file mode 100644 index 0000000000..3dee6c54b5 --- /dev/null +++ b/translations/ru-RU/content/actions/deployment/using-environments-for-deployment.md @@ -0,0 +1,126 @@ +--- +title: Using environments for deployment +shortTitle: Use environments for deployment +intro: You can configure environments with protection rules and secrets. A workflow job that references an environment must follow any protection rules for the environment before running or accessing the environment's secrets. +product: '{% data reusables.gated-features.environments %}' +miniTocMaxHeadingLevel: 3 +redirect_from: + - /actions/reference/environments + - /actions/deployment/environments +versions: + fpt: '*' + ghes: '>=3.1' + ghae: '*' +--- + + +## About environments + +Environments are used to describe a general deployment target like `production`, `staging`, or `development`. 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)." + +You can configure environments with protection rules and secrets. When a workflow job references an environment, the job won't start until all of the environment's protection rules pass. A job also cannot access secrets that are defined in an environment until all the environment protection rules pass. + +{% ifversion fpt %} +{% note %} + +**Note:** If you don't use {% data variables.product.prodname_ghe_cloud %} and convert a repository from public to private, any configured protection rules or environment secrets will be ignored, and you will not be able to configure any environments. If you convert your repository back to public, you will have access to any previously configured protection rules and environment secrets. {% data reusables.enterprise.link-to-ghec-trial %} + +{% endnote %} +{% endif %} + +## Environment protection rules + +Environment protection rules require specific conditions to pass before a job referencing the environment can proceed. {% ifversion fpt or ghae-next or ghes > 3.1 %}You can use environment protection rules to require a manual approval, delay a job, or restrict the environment to certain branches.{% else %}You can use environment protection rules to require a manual approval or delay a job.{% endif %} + +### Required reviewers + +Use required reviewers to require a specific person or team to approve workflow jobs that reference the environment. You can list up to six users or teams as reviewers. The reviewers must have at least read access to the repository. Only one of the required reviewers needs to approve the job for it to proceed. + +For more information on reviewing jobs that reference an environment with required reviewers, see "[Reviewing deployments](/actions/managing-workflow-runs/reviewing-deployments)." + +### Wait timer + +Use a wait timer to delay a job for a specific amount of time after the job is initially triggered. The time (in minutes) must be an integer between 0 and 43,200 (30 days). + +{% ifversion fpt or ghae-next or ghes > 3.1 %} +### Deployment branches + +Use deployment branches to restrict which branches can deploy to the environment. Below are the options for deployment branches for an environment: + +* **All branches**: All branches in the repository can deploy to the environment. +* **Protected branches**: Only branches with branch protection rules enabled can deploy to the environment. If no branch protection rules are defined for any branch in the repository, then all branches can deploy. For more information about branch protection rules, see "[About protected branches](/github/administering-a-repository/about-protected-branches)." +* **Selected branches**: Only branches that match your specified name patterns can deploy to the environment. + + For example, if you specify `releases/*` as a deployment branch rule, only branches whose name begins with `releases/` can deploy to the environment. (Wildcard characters will not match `/`. To match branches that begin with `release/` and contain an additional single slash, use `release/*/*`.) If you add `main` as a deployment branch rule, a branch named `main` can also deploy to the environment. For more information about syntax options for deployment branches, see the [Ruby File.fnmatch documentation](https://ruby-doc.org/core-2.5.1/File.html#method-c-fnmatch). +{% endif %} +## Environment secrets + +Secrets stored in an environment are only available to workflow jobs that reference the environment. If the environment requires approval, a job cannot access environment secrets until one of the required reviewers approves it. For more information about secrets, see "[Encrypted secrets](/actions/reference/encrypted-secrets)." + +{% note %} + +**Note:** Workflows that run on self-hosted runners are not run in an isolated container, even if they use environments. Environment secrets should be treated with the same level of security as repository and organization secrets. For more information, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#hardening-for-self-hosted-runners)." + +{% endnote %} + +## Creating an environment + +{% data reusables.github-actions.permissions-statement-environment %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.github-actions.sidebar-environment %} +{% data reusables.github-actions.new-environment %} +{% data reusables.github-actions.name-environment %} +1. Optionally, specify people or teams that must approve workflow jobs that use this environment. + 1. Select **Required reviewers**. + 1. Enter up to 6 people or teams. Only one of the required reviewers needs to approve the job for it to proceed. + 1. Click **Save protection rules**. +2. Optionally, specify the amount of time to wait before allowing workflow jobs that use this environment to proceed. + 1. Select **Wait timer**. + 1. Enter the number of minutes to wait. + 1. Click **Save protection rules**. +3. Optionally, specify what branches can deploy to this environment. For more information about the possible values, see "[Deployment branches](#deployment-branches)." + 1. Select the desired option in the **Deployment branches** dropdown. + 1. If you chose **Selected branches**, enter the branch name patterns that you want to allow. +4. Optionally, add environment secrets. These secrets are only available to workflow jobs that use the environment. Additionally, workflow jobs that use this environment can only access these secrets after any configured rules (for example, required reviewers) pass. For more information about secrets, see "[Encrypted secrets](/actions/reference/encrypted-secrets)." + 1. Under **Environment secrets**, click **Add Secret**. + 1. Enter the secret name. + 1. Enter the secret value. + 1. Click **Add secret**. + +{% ifversion fpt or ghae-next or ghes > 3.1 %}You can also create and configure environments through the REST API. For more information, see "[Environments](/rest/reference/repos#environments)" and "[Secrets](/rest/reference/actions#secrets)."{% endif %} + +Running a workflow that references an environment that does not exist will create an environment with the referenced name. The newly created environment will not have any protection rules or secrets configured. Anyone that can edit workflows in the repository can create environments via a workflow file, but only repository admins can configure the environment. + +## Using an environment + +Each job in a workflow can reference a single environment. Any protection rules configured for the environment must pass before a job referencing the environment is sent to a runner. The job can access the environment's secrets only after the job is sent to a runner. + +When a workflow references an environment, the environment will appear in the repository's deployments. For more information about viewing current and previous deployments, see "[Viewing deployment history](/developers/overview/viewing-deployment-history)." + +{% data reusables.actions.environment-example %} + +## Deleting an environment + +{% data reusables.github-actions.permissions-statement-environment %} + +Deleting an environment will delete all secrets and protection rules associated with the environment. Any jobs currently waiting because of protection rules from the deleted environment will automatically fail. + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.github-actions.sidebar-environment %} +1. Next to the environment that you want to delete, click {% octicon "trash" aria-label="The trash icon" %}. +2. Click **I understand, delete this environment**. + +{% ifversion fpt or ghae-next or ghes > 3.1 %}You can also delete environments through the REST API. For more information, see "[Environments](/rest/reference/repos#environments)."{% endif %} + +## How environments relate to deployments + +{% data reusables.actions.environment-deployment-event %} + +You can access these objects through the REST API or GraphQL API. You can also subscribe to these webhook events. For more information, see "[Repositories](/rest/reference/repos#deployments)" (REST API), "[Objects](/graphql/reference/objects#deployment)" (GraphQL API), or "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#deployment)." + +## Дальнейшие шаги + +{% data variables.product.prodname_actions %} provides several features for managing your deployments. For more information, see "[Deploying with GitHub Actions](/actions/deployment/deploying-with-github-actions)." diff --git a/translations/ru-RU/content/actions/deployment/viewing-deployment-history.md b/translations/ru-RU/content/actions/deployment/viewing-deployment-history.md new file mode 100644 index 0000000000..16f184214e --- /dev/null +++ b/translations/ru-RU/content/actions/deployment/viewing-deployment-history.md @@ -0,0 +1,27 @@ +--- +title: Viewing deployment history +intro: View current and previous deployments for your repository. +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - API +shortTitle: View deployment history +redirect_from: + - /developers/overview/viewing-deployment-history +--- + + +You can deliver deployments through {% ifversion fpt or ghae or ghes > 3.0 %}{% data variables.product.prodname_actions %} and environments or with {% endif %}the REST API and third party apps. {% ifversion fpt or ghae ghes > 3.0 %}For more information about using environments to deploy with {% data variables.product.prodname_actions %}, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." {% endif %}For more information about deployments with the REST API, see "[Repositories](/rest/reference/repos#deployments)." + +To view current and past deployments, click **Environments** on the home page of your repository. +{% ifversion ghae or ghes < 3.0 %} +![Environments](/assets/images/enterprise/2.22/environments-sidebar.png){% else %} +![Environments](/assets/images/environments-sidebar.png){% endif %} + +The deployments page displays the last active deployment of each environment for your repository. If the deployment includes an environment URL, a **View deployment** button that links to the URL is shown next to the deployment. + +The activity log shows the deployment history for your environments. By default, only the most recent deployment for an environment has an `Active` status; all previously active deployments have an `Inactive` status. For more information on automatic inactivation of deployments, see "[Inactive deployments](/rest/reference/repos#inactive-deployments)." + +You can also use the REST API to get information about deployments. For more information, see "[Repositories](/rest/reference/repos#deployments)." diff --git a/translations/ru-RU/content/actions/hosting-your-own-runners/about-self-hosted-runners.md b/translations/ru-RU/content/actions/hosting-your-own-runners/about-self-hosted-runners.md index b543615f2a..d496e1e35d 100644 --- a/translations/ru-RU/content/actions/hosting-your-own-runners/about-self-hosted-runners.md +++ b/translations/ru-RU/content/actions/hosting-your-own-runners/about-self-hosted-runners.md @@ -14,7 +14,6 @@ type: overview {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About self-hosted runners @@ -172,7 +171,9 @@ You can also use self-hosted runners with a proxy server. For more information, ## Self-hosted runner security with public repositories +{% ifversion not ghae %} {% data reusables.github-actions.self-hosted-runner-security %} +{% endif %} This is not an issue with {% data variables.product.prodname_dotcom %}-hosted runners because each {% data variables.product.prodname_dotcom %}-hosted runner is always a clean isolated virtual machine, and it is destroyed at the end of the job execution. diff --git a/translations/ru-RU/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md b/translations/ru-RU/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md index 9a570e2545..dc34c77fc9 100644 --- a/translations/ru-RU/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md +++ b/translations/ru-RU/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md @@ -15,7 +15,6 @@ shortTitle: Add self-hosted runners {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} You can add a self-hosted runner to a repository, an organization, or an enterprise. @@ -23,6 +22,7 @@ If you are an organization or enterprise administrator, you might want to add yo For information on supported operating systems for self-hosted runners, or using self-hosted runners with a proxy server, see "[About self-hosted runners](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)." +{% ifversion not ghae %} {% warning %} **Warning:** {% data reusables.github-actions.self-hosted-runner-security %} @@ -30,6 +30,7 @@ For information on supported operating systems for self-hosted runners, or using For more information, see "[About self-hosted runners](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)." {% endwarning %} +{% endif %} ## Adding a self-hosted runner to a repository @@ -48,7 +49,7 @@ You can add self-hosted runners to a single repository. To add a self-hosted run {% data reusables.repositories.sidebar-settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} 1. Under -{% ifversion fpt %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**. +{% ifversion fpt or ghes > 3.1 or ghae %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**. {% data reusables.github-actions.self-hosted-runner-configure %} {% endif %} {% data reusables.github-actions.self-hosted-runner-check-installation-success %} @@ -70,7 +71,7 @@ You can add self-hosted runners at the organization level, where they can be use {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} 1. Under -{% ifversion fpt %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**. +{% ifversion fpt or ghes > 3.1 or ghae %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**. {% data reusables.github-actions.self-hosted-runner-configure %} {% endif %} diff --git a/translations/ru-RU/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md b/translations/ru-RU/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md index ef6289b492..e90c2a6648 100644 --- a/translations/ru-RU/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md +++ b/translations/ru-RU/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md @@ -10,7 +10,6 @@ type: overview {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About autoscaling diff --git a/translations/ru-RU/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md b/translations/ru-RU/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md index be2584a4df..de46a37697 100644 --- a/translations/ru-RU/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md +++ b/translations/ru-RU/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md @@ -15,7 +15,6 @@ shortTitle: Run runner app on startup {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% capture service_first_step %}1. Stop the self-hosted runner application if it is currently running.{% endcapture %} {% capture service_non_windows_intro_shell %}On the runner machine, open a shell in the directory where you installed the self-hosted runner application. Use the commands below to install and manage the self-hosted runner service.{% endcapture %} diff --git a/translations/ru-RU/content/actions/hosting-your-own-runners/index.md b/translations/ru-RU/content/actions/hosting-your-own-runners/index.md index 6fe2e32cb2..d2fb39d810 100644 --- a/translations/ru-RU/content/actions/hosting-your-own-runners/index.md +++ b/translations/ru-RU/content/actions/hosting-your-own-runners/index.md @@ -24,4 +24,3 @@ children: {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} diff --git a/translations/ru-RU/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md b/translations/ru-RU/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md index cb5e0b2a45..3395b9b486 100644 --- a/translations/ru-RU/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md +++ b/translations/ru-RU/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md @@ -14,7 +14,6 @@ shortTitle: Manage runner groups {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About self-hosted runner groups @@ -173,14 +172,13 @@ Could not find any self-hosted runner group named "rg-runnergroup". ## Moving a self-hosted runner to a group If you don't specify a runner group during the registration process, your new self-hosted runners are automatically assigned to the default group, and can then be moved to another group. -{% ifversion fpt %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} 1. In the "Runners" list, click the runner that you want to configure. 1. Select the Runner group dropdown menu. 1. In "Move runner to group", choose a destination group for the runner. -{% endif %} -{% ifversion ghae or ghes %} -1. In the {% ifversion fpt %}"Runners"{% else %}"Self-hosted runners"{% endif %} section of the settings page, locate the current group of the runner you want to move and expand the list of group members. ![View runner group members](/assets/images/help/settings/actions-org-runner-group-members.png) +{% else %} +1. In the "Self-hosted runners" section of the settings page, locate the current group of the runner you want to move and expand the list of group members. ![View runner group members](/assets/images/help/settings/actions-org-runner-group-members.png) 1. Select the checkbox next to the self-hosted runner, and then click **Move to group** to see the available destinations. ![Runner group member move](/assets/images/help/settings/actions-org-runner-group-member-move.png) 1. To move the runner, click on the destination group. ![Runner group member move](/assets/images/help/settings/actions-org-runner-group-member-move-destination.png) {% endif %} @@ -188,14 +186,13 @@ If you don't specify a runner group during the registration process, your new se Self-hosted runners are automatically returned to the default group when their group is removed. -{% ifversion fpt %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} {% data reusables.github-actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %} 1. In the list of groups, to the right of the group you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. 1. To remove the group, click **Remove group**. 1. Review the confirmation prompts, and click **Remove this runner group**. -{% endif %} -{% ifversion ghae or ghes %} -1. In the {% ifversion fpt %}"Runners"{% else %}"Self-hosted runners"{% endif %} section of the settings page, locate the group you want to delete, and click the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} button. ![View runner group settings](/assets/images/help/settings/actions-org-runner-group-kebab.png) +{% else %} +1. In the "Self-hosted runners" section of the settings page, locate the group you want to delete, and click the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} button. ![View runner group settings](/assets/images/help/settings/actions-org-runner-group-kebab.png) 1. To remove the group, click **Remove group**. ![View runner group settings](/assets/images/help/settings/actions-org-runner-group-remove.png) diff --git a/translations/ru-RU/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md b/translations/ru-RU/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md index 937c92e23b..ffc0b4fa57 100644 --- a/translations/ru-RU/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md +++ b/translations/ru-RU/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md @@ -17,7 +17,6 @@ shortTitle: Monitor & troubleshoot {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Checking the status of a self-hosted runner @@ -25,7 +24,7 @@ shortTitle: Monitor & troubleshoot {% data reusables.github-actions.self-hosted-runner-navigate-repo-and-org %} {% data reusables.github-actions.settings-sidebar-actions-runners %} -1. Under {% ifversion fpt %}"Runners"{% else %}"Self-hosted runners"{% endif %}, you can view a list of registered runners, including the runner's name, labels, and status. +1. Under {% ifversion fpt or ghes > 3.1 or ghae-next %}"Runners"{% else %}"Self-hosted runners"{% endif %}, you can view a list of registered runners, including the runner's name, labels, and status. The status can be one of the following: diff --git a/translations/ru-RU/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md b/translations/ru-RU/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md index 284e7929d8..a545e0468c 100644 --- a/translations/ru-RU/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md +++ b/translations/ru-RU/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md @@ -15,7 +15,6 @@ shortTitle: Remove self-hosted runners {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Removing a runner from a repository @@ -57,15 +56,14 @@ To remove a self-hosted runner from a user repository you must be the repository To remove a self-hosted runner from an organization, you must be an organization owner. We recommend that you also have access to the self-hosted runner machine. {% data reusables.github-actions.self-hosted-runner-reusing %} -{% ifversion fpt %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions %} {% data reusables.github-actions.settings-sidebar-actions-runners-updated %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %} -{% endif %} -{% ifversion ghae or ghes %} +{% else %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} @@ -90,10 +88,9 @@ To remove a self-hosted runner from an enterprise account, you must be an enterp {% data reusables.enterprise-accounts.actions-runners-tab %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes %} To remove a self-hosted runner at the enterprise level of -{% data variables.product.product_location %}, you must be a site administrator. We recommend that you also have access to the self-hosted runner machine. +{% data variables.product.product_location %}, you must be an enterprise owner. We recommend that you also have access to the self-hosted runner machine. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} diff --git a/translations/ru-RU/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md b/translations/ru-RU/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md index f83671ecc3..79cb92b0e1 100644 --- a/translations/ru-RU/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md +++ b/translations/ru-RU/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md @@ -14,7 +14,6 @@ shortTitle: Proxy servers {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Configuring a proxy server using environment variables diff --git a/translations/ru-RU/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md b/translations/ru-RU/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md index 9aa7b89c5c..48ed6142ca 100644 --- a/translations/ru-RU/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md +++ b/translations/ru-RU/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md @@ -12,7 +12,6 @@ shortTitle: Label runners {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} For information on how to use labels to route jobs to specific types of self-hosted runners, see "[Using self-hosted runners in a workflow](/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow)." diff --git a/translations/ru-RU/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md b/translations/ru-RU/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md index 783159fd24..8a2213218f 100644 --- a/translations/ru-RU/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md +++ b/translations/ru-RU/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md @@ -15,7 +15,6 @@ shortTitle: Use runners in a workflow {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} For information on creating custom and default labels, see "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)." diff --git a/translations/ru-RU/content/actions/index.md b/translations/ru-RU/content/actions/index.md index 3173f8b9a5..3348b6999c 100644 --- a/translations/ru-RU/content/actions/index.md +++ b/translations/ru-RU/content/actions/index.md @@ -9,6 +9,7 @@ featuredLinks: guides: - /actions/learn-github-actions - /actions/guides/about-continuous-integration + - /actions/deployment/deploying-with-github-actions - /actions/guides/about-packaging-with-github-actions - /actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting guideCards: diff --git a/translations/ru-RU/content/actions/learn-github-actions/contexts.md b/translations/ru-RU/content/actions/learn-github-actions/contexts.md index f350a353fa..698a2f6720 100644 --- a/translations/ru-RU/content/actions/learn-github-actions/contexts.md +++ b/translations/ru-RU/content/actions/learn-github-actions/contexts.md @@ -18,7 +18,6 @@ miniTocMaxHeadingLevel: 3 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About contexts @@ -61,27 +60,29 @@ The `github` context contains information about the workflow run and the event t {% data reusables.github-actions.github-context-warning %} {% data reusables.github-actions.context-injection-warning %} -| Property name | Тип | Description | -| ------------------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `github` | `объект` | The top-level context available during any job or step in a workflow. | -| `github.action` | `строка` | The name of the action currently running. {% data variables.product.prodname_dotcom %} removes special characters or uses the name `run` when the current step runs a script. If you use the same action more than once in the same job, the name will include a suffix with the sequence number. For example, the first script you run will have the name `run1`, and the second script will be named `run2`. Similarly, the second invocation of `actions/checkout` will be `actionscheckout2`. | -| `github.action_path` | `строка` | The path where your action is located. You can use this path to easily access files located in the same repository as your action. This attribute is only supported in composite actions. | -| `github.actor` | `строка` | The login of the user that initiated the workflow run. | -| `github.base_ref` | `строка` | The `base_ref` or target branch of the pull request in a workflow run. This property is only available when the event that triggers a workflow run is either `pull_request` or `pull_request_target`. | -| `github.event` | `объект` | The full event webhook payload. For more information, see "[Events that trigger workflows](/articles/events-that-trigger-workflows/)." You can access individual properties of the event using this context. | -| `github.event_name` | `строка` | The name of the event that triggered the workflow run. | -| `github.event_path` | `строка` | The path to the full event webhook payload on the runner. | -| `github.head_ref` | `строка` | The `head_ref` or source branch of the pull request in a workflow run. This property is only available when the event that triggers a workflow run is either `pull_request` or `pull_request_target`. | -| `github.job` | `строка` | The [`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) of the current job. | -| `github.ref` | `строка` | The branch or tag ref that triggered the workflow run. For branches this is the format `refs/heads/`, and for tags it is `refs/tags/`. | -| `github.repository` | `строка` | The owner and repository name. For example, `Codertocat/Hello-World`. | -| `github.repository_owner` | `строка` | The repository owner's name. For example, `Codertocat`. | +| Property name | Тип | Description | +| ------------------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `github` | `объект` | The top-level context available during any job or step in a workflow. | +| `github.action` | `строка` | The name of the action currently running. {% data variables.product.prodname_dotcom %} removes special characters or uses the name `__run` when the current step runs a script. If you use the same action more than once in the same job, the name will include a suffix with the sequence number with underscore before it. For example, the first script you run will have the name `__run`, and the second script will be named `__run_2`. Similarly, the second invocation of `actions/checkout` will be `actionscheckout2`. | +| `github.action_path` | `строка` | The path where your action is located. You can use this path to easily access files located in the same repository as your action. This attribute is only supported in composite actions. | +| `github.actor` | `строка` | The login of the user that initiated the workflow run. | +| `github.base_ref` | `строка` | The `base_ref` or target branch of the pull request in a workflow run. This property is only available when the event that triggers a workflow run is either `pull_request` or `pull_request_target`. | +| `github.event` | `объект` | The full event webhook payload. For more information, see "[Events that trigger workflows](/articles/events-that-trigger-workflows/)." You can access individual properties of the event using this context. | +| `github.event_name` | `строка` | The name of the event that triggered the workflow run. | +| `github.event_path` | `строка` | The path to the full event webhook payload on the runner. | +| `github.head_ref` | `строка` | The `head_ref` or source branch of the pull request in a workflow run. This property is only available when the event that triggers a workflow run is either `pull_request` or `pull_request_target`. | +| `github.job` | `строка` | The [`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) of the current job. | +| `github.ref` | `строка` | The branch or tag ref that triggered the workflow run. For branches this is the format `refs/heads/`, and for tags it is `refs/tags/`. | +| `github.repository` | `строка` | The owner and repository name. For example, `Codertocat/Hello-World`. | +| `github.repository_owner` | `строка` | The repository owner's name. For example, `Codertocat`. | | `github.run_id` | `строка` | {% data reusables.github-actions.run_id_description %} | `github.run_number` | `строка` | {% data reusables.github-actions.run_number_description %} -| `github.sha` | `строка` | The commit SHA that triggered the workflow run. | -| `github.token` | `строка` | A token to authenticate on behalf of the GitHub App installed on your repository. This is functionally equivalent to the `GITHUB_TOKEN` secret. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)." | -| `github.workflow` | `строка` | The name of the workflow. If the workflow file doesn't specify a `name`, the value of this property is the full path of the workflow file in the repository. | -| `github.workspace` | `строка` | The default working directory for steps and the default location of your repository when using the [`checkout`](https://github.com/actions/checkout) action. | +| `github.run_attempt` | `строка` | A unique number for each attempt of a particular workflow run in a repository. This number begins at 1 for the workflow run's first attempt, and increments with each re-run. | +| `github.server_url` | `строка` | Returns the URL of the GitHub server. For example: `https://github.com`. | +| `github.sha` | `строка` | The commit SHA that triggered the workflow run. | +| `github.token` | `строка` | A token to authenticate on behalf of the GitHub App installed on your repository. This is functionally equivalent to the `GITHUB_TOKEN` secret. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)." | +| `github.workflow` | `строка` | The name of the workflow. If the workflow file doesn't specify a `name`, the value of this property is the full path of the workflow file in the repository. | +| `github.workspace` | `строка` | The default working directory for steps and the default location of your repository when using the [`checkout`](https://github.com/actions/checkout) action. | ### `env` context @@ -130,6 +131,7 @@ The `runner` context contains information about the runner that is executing the | Property name | Тип | Description | | ------------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `runner.name` | `строка` | {% data reusables.actions.runner-name-description %} | `runner.os` | `строка` | {% data reusables.actions.runner-os-description %} | `runner.temp` | `строка` | {% data reusables.actions.runner-temp-directory-description %} | `runner.tool_cache` | `строка` | {% ifversion ghae %}For instructions on how to make sure your {% data variables.actions.hosted_runner %} has the required software installed, see "[Creating custom images](/actions/using-github-hosted-runners/creating-custom-images)." {% else %} {% data reusables.actions.runner-tool-cache-description %} {% endif %} diff --git a/translations/ru-RU/content/actions/learn-github-actions/creating-workflow-templates.md b/translations/ru-RU/content/actions/learn-github-actions/creating-workflow-templates.md new file mode 100644 index 0000000000..61d1cce306 --- /dev/null +++ b/translations/ru-RU/content/actions/learn-github-actions/creating-workflow-templates.md @@ -0,0 +1,93 @@ +--- +title: Creating workflow templates +shortTitle: Creating templates +intro: Learn how you can create workflow templates to help people in your team add new workflows more easily. +redirect_from: + - /actions/configuring-and-managing-workflows/sharing-workflow-templates-within-your-organization +versions: + fpt: '*' + ghes: '*' + ghae: '*' +type: tutorial +topics: + - Workflows + - CI +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +## Обзор + +{% data reusables.actions.workflow-organization-templates %} + +## Creating a workflow template + +Workflow templates can be created by users with write access to the organization's `.github` repository. The templates can then be used by organization members who have permission to create workflows. You can share workflow templates if your organization's repository is public or if the repository is private and on an Enterprise plan. + +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +{% note %} + +**Note:** To avoid duplication in workflows created from a template you can call reusable workflows from within a workflow template. This can help make your workflows easier to maintain. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." + +{% endnote %} +{% endif %} + +This procedure demonstrates how to create a workflow template and metadata file. The metadata file describes how the template is presented to users when they are creating a new workflow. + +1. If it doesn't already exist, create a new public repository named `.github` in your organization. +2. Create a directory named `workflow-templates`. +3. Create your new workflow file inside the `workflow-templates` directory. + + If you need to refer to a repository's default branch, you can use the `$default-branch` placeholder. When a workflow is created using your template, the placeholder will be automatically replaced with the name of the repository's default branch. + + For example, this file named `octo-organization-ci.yml` demonstrates a basic workflow. + + ```yaml + name: Octo Organization CI + + on: + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] + + jobs: + build: + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v2 + + - name: Run a one-line script + run: echo Hello from Octo Organization + ``` +4. Create a metadata file inside the `workflow-templates` directory. The metadata file must have the same name as the workflow file, but instead of the `.yml` extension, it must be appended with `.properties.json`. For example, this file named `octo-organization-ci.properties.json` contains the metadata for a workflow file named `octo-organization-ci.yml`: + ```yaml + { + "name": "Octo Organization Workflow", + "description": "Octo Organization CI workflow template.", + "iconName": "example-icon", + "categories": [ + "Go" + ], + "filePatterns": [ + "package.json$", + "^Dockerfile", + ".*\\.md$" + ] + } + ``` + * `name` - **Required.** The name of the workflow template. This is displayed in the list of available templates. + * `description` - **Required.** The description of the workflow template. This is displayed in the list of available templates. + * `iconName` - **Required.** Defines an icon for the workflow's entry in the template list. The `iconName` must be an SVG icon of the same name, and must be stored in the `workflow-templates` directory. For example, a SVG file named `example-icon.svg` is referenced as `example-icon`. + * `categories` - **Optional.** Defines the language category of the workflow. When a user views the available templates, those templates that match the same language will feature more prominently. For information on the available language categories, see https://github.com/github/linguist/blob/master/lib/linguist/languages.yml. + * `filePatterns` - **Optional.** Allows the template to be used if the user's repository has a file in its root directory that matches a defined regular expression. + +To add another workflow template, add your files to the same `workflow-templates` directory. Например: + +![Workflow template files](/assets/images/help/images/workflow-template-files.png) + +## Дальнейшие шаги + +To continue learning about {% data variables.product.prodname_actions %}, see "[Using workflow templates](/actions/learn-github-actions/using-workflow-templates)." diff --git a/translations/ru-RU/content/actions/learn-github-actions/environment-variables.md b/translations/ru-RU/content/actions/learn-github-actions/environment-variables.md index daca21e8ce..b5e5287c05 100644 --- a/translations/ru-RU/content/actions/learn-github-actions/environment-variables.md +++ b/translations/ru-RU/content/actions/learn-github-actions/environment-variables.md @@ -15,7 +15,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About environment variables @@ -73,6 +72,7 @@ We strongly recommend that actions use environment variables to access the files | `GITHUB_SERVER_URL` | Returns the URL of the {% data variables.product.product_name %} server. For example: `https://{% data variables.product.product_url %}`. | | `GITHUB_API_URL` | Returns the API URL. For example: `{% data variables.product.api_url_code %}`. | | `GITHUB_GRAPHQL_URL` | Returns the GraphQL API URL. For example: `{% data variables.product.graphql_url_code %}`. | +| `RUNNER_NAME` | {% data reusables.actions.runner-name-description %} | `RUNNER_OS` | {% data reusables.actions.runner-os-description %} | `RUNNER_TEMP` | {% data reusables.actions.runner-temp-directory-description %} {% ifversion not ghae %}| `RUNNER_TOOL_CACHE` | {% data reusables.actions.runner-tool-cache-description %}{% endif %} diff --git a/translations/ru-RU/content/actions/learn-github-actions/essential-features-of-github-actions.md b/translations/ru-RU/content/actions/learn-github-actions/essential-features-of-github-actions.md index a72dcfc595..40b868699e 100644 --- a/translations/ru-RU/content/actions/learn-github-actions/essential-features-of-github-actions.md +++ b/translations/ru-RU/content/actions/learn-github-actions/essential-features-of-github-actions.md @@ -13,7 +13,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Обзор @@ -62,7 +61,7 @@ For more information, see "[Workflow syntax for {% data variables.product.prodna ## Sharing data between jobs -If your job generates files that you want to share with another job in the same workflow, or if you want to save the files for later reference, you can store them in {% data variables.product.prodname_dotcom %} as _artifacts_. Artifacts are the files created when you build and test your code. For example, artifacts might include binary or package files, test results, screenshots, or log files. Artifacts are associated with the workflow run where they were created and can be used by another job. +If your job generates files that you want to share with another job in the same workflow, or if you want to save the files for later reference, you can store them in {% data variables.product.prodname_dotcom %} as _artifacts_. Artifacts are the files created when you build and test your code. For example, artifacts might include binary or package files, test results, screenshots, or log files. Artifacts are associated with the workflow run where they were created and can be used by another job. {% data reusables.actions.reusable-workflow-artifacts %} For example, you can create a file and then upload it as an artifact. diff --git a/translations/ru-RU/content/actions/learn-github-actions/events-that-trigger-workflows.md b/translations/ru-RU/content/actions/learn-github-actions/events-that-trigger-workflows.md index 8bb3bed620..585b9433c7 100644 --- a/translations/ru-RU/content/actions/learn-github-actions/events-that-trigger-workflows.md +++ b/translations/ru-RU/content/actions/learn-github-actions/events-that-trigger-workflows.md @@ -17,7 +17,6 @@ shortTitle: Events that trigger workflows {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Configuring workflow events @@ -165,6 +164,26 @@ on: types: [opened, deleted] ``` +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## Workflow reuse events + +`workflow_call` is a keyword used as the value of `on` in a workflow, in the same way as an event. It indicates that a workflow can be called from another workflow. For more information see, "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." + +### `workflow_call` + +| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | +| --------------------------- | -------------- | --------------------------- | --------------------------- | +| Same as the caller workflow | n/a | Same as the caller workflow | Same as the caller workflow | + +#### Пример + +To make a workflow reusable it must include `workflow_call` as one of the values of `on`. The example below only runs the workflow when it's called from another workflow: + +```yaml +on: workflow_call +``` +{% endif %} + ## Webhook events You can configure your workflow to run when webhook events are generated on {% data variables.product.product_name %}. Some events have more than one activity type that triggers the event. If more than one activity type triggers the event, you can specify which activity types will trigger the workflow to run. For more information, see "[Webhooks](/webhooks)." diff --git a/translations/ru-RU/content/actions/learn-github-actions/expressions.md b/translations/ru-RU/content/actions/learn-github-actions/expressions.md index 4bbf4ffa99..8fade99a26 100644 --- a/translations/ru-RU/content/actions/learn-github-actions/expressions.md +++ b/translations/ru-RU/content/actions/learn-github-actions/expressions.md @@ -12,7 +12,6 @@ miniTocMaxHeadingLevel: 3 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About expressions diff --git a/translations/ru-RU/content/actions/learn-github-actions/finding-and-customizing-actions.md b/translations/ru-RU/content/actions/learn-github-actions/finding-and-customizing-actions.md index 72d280a625..c3fc8ab25d 100644 --- a/translations/ru-RU/content/actions/learn-github-actions/finding-and-customizing-actions.md +++ b/translations/ru-RU/content/actions/learn-github-actions/finding-and-customizing-actions.md @@ -18,7 +18,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Обзор diff --git a/translations/ru-RU/content/actions/learn-github-actions/index.md b/translations/ru-RU/content/actions/learn-github-actions/index.md index 0c382694b3..2a211fefef 100644 --- a/translations/ru-RU/content/actions/learn-github-actions/index.md +++ b/translations/ru-RU/content/actions/learn-github-actions/index.md @@ -32,8 +32,10 @@ children: - /finding-and-customizing-actions - /essential-features-of-github-actions - /managing-complex-workflows - - /sharing-workflows-with-your-organization + - /sharing-workflows-secrets-and-runners-with-your-organization + - /creating-workflow-templates - /using-workflow-templates + - /reusing-workflows - /events-that-trigger-workflows - /expressions - /contexts diff --git a/translations/ru-RU/content/actions/learn-github-actions/managing-complex-workflows.md b/translations/ru-RU/content/actions/learn-github-actions/managing-complex-workflows.md index 44695f2e86..773fdec873 100644 --- a/translations/ru-RU/content/actions/learn-github-actions/managing-complex-workflows.md +++ b/translations/ru-RU/content/actions/learn-github-actions/managing-complex-workflows.md @@ -13,7 +13,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Обзор @@ -170,10 +169,13 @@ To learn more about self-hosted runner labels, see ["Using labels with self-host {% data variables.product.prodname_dotcom %}-hosted runner labels, see ["Supported runners and hardware resources"](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources). {% endif %} -{% ifversion fpt or ghes > 3.0 %} +{% data reusables.actions.reusable-workflows %} + +{% ifversion fpt or ghes > 3.0 or ghae-next %} + ## Using environments -You can configure environments with protection rules and secrets. Each job in a workflow can reference a single environment. Any protection rules configured for the environment must pass before a job referencing the environment is sent to a runner. For more information, see "[Environments](/actions/reference/environments)." +You can configure environments with protection rules and secrets. Each job in a workflow can reference a single environment. Any protection rules configured for the environment must pass before a job referencing the environment is sent to a runner. For more information, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." {% endif %} ## Using a workflow template @@ -187,4 +189,4 @@ You can configure environments with protection rules and secrets. Each job in a ## Дальнейшие шаги -To continue learning about {% data variables.product.prodname_actions %}, see "[Sharing workflows with your organization](/actions/learn-github-actions/sharing-workflows-with-your-organization)." +To continue learning about {% data variables.product.prodname_actions %}, see "[Sharing workflows, secrets, and runners with your organization](/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization)." diff --git a/translations/ru-RU/content/actions/learn-github-actions/reusing-workflows.md b/translations/ru-RU/content/actions/learn-github-actions/reusing-workflows.md new file mode 100644 index 0000000000..c51633def9 --- /dev/null +++ b/translations/ru-RU/content/actions/learn-github-actions/reusing-workflows.md @@ -0,0 +1,195 @@ +--- +title: Reusing workflows +shortTitle: Reusing workflows +intro: Learn how to avoid duplication when creating a workflow by reusing existing workflows. +miniTocMaxHeadingLevel: 3 +versions: + fpt: '*' + ghes: '>=3.4' + ghae: issue-4757 +type: how_to +topics: + - Workflows +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +{% note %} + +**Note:** Reusable workflows are currently in beta and subject to change. + +{% endnote %} + +## Обзор + +Rather than copying and pasting from one workflow to another, you can make workflows reusable. You and anyone with access to the reusable workflow can then call the reusable workflow from another workflow. + +Reusing workflows avoids duplication. This makes workflows easier to maintain and allows you to create new workflows more quickly by building on the work of others, just as you do with actions. Workflow reuse also promotes best practice by helping you to use workflows that are well designed, have already been tested, and have been proved to be effective. Your organization can build up a library of reusable workflows that can be centrally maintained. + +A workflow that uses another workflow is referred to as a "caller" workflow. The reusable workflow is a "called" workflow. One caller workflow can use multiple called workflows. Each called workflow is referenced in a single line. The result is that the caller workflow file may contain just a few lines of YAML, but may perform a large number of tasks when it's run. When you reuse a workflow, the entire called workflow is used, just as if it was part of the caller workflow. + +If you reuse a workflow from a different repository, any actions in the called workflow run as if they were part of the caller workflow. For example, if the called workflow uses `actions/checkout`, the action checks out the contents of the repository that hosts the caller workflow, not the called workflow. + +When a reusable workflow is triggered by a caller workflow, the `github` context is always associated with the caller workflow. For more information about the `github` context, see "[Context and expression syntax for GitHub Actions](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)." + +## Access to reusable workflows + +A reusable workflow can be used by another workflow if any of the following is true: + +* Both workflows are in the same repository. +* The called workflow is stored in a public repository. +* The called workflow is stored in an internal repository and the settings for that repository allow it to be accessed. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#allowing-access-to-components-in-an-internal-repository)." + +## Ограничения + +* Reusable workflows can't call other reusable workflows. +* Reusable workflows stored within a private repository can only be used by workflows within the same repository. +* Any environment variables set in an `env` context defined at the workflow level in the caller workflow are not be propagated to the called workflow. For more information about the `env` context, see "[Context and expression syntax for GitHub Actions](/actions/reference/context-and-expression-syntax-for-github-actions#env-context)." + +The following limitations will be removed when workflow reuse moves out of beta: +* Reusable workflows can't reference self-hosted runners. +* You can't set the concurrency of a called workflow from the caller workflow. For more information about `jobs..concurrency`, see "[Workflow syntax for GitHub Actions](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idconcurrency)." +* Outputs generated by a called workflow can't be accessed by the caller workflow. + +## Creating a reusable workflow + +Reusable workflows are YAML-formatted files, very similar to any other workflow file. As with other workflow files, you locate reusable workflows in the `.github/workflows` directory of a repository. Subdirectories of the `workflows` directory are not supported. + +For a workflow to be reusable, the values for `on` must include `workflow_call`: + +```yaml +on: + workflow_call: +``` + +You can define inputs and secrets, which can be passed from the caller workflow and then used within the called workflow. The following example, from a reusable workflow, defines two inputs (called "ring" and "environment") and one secret (called "token"): + +```yaml +on: + workflow_call: + inputs: + ring: + description: 'Identifier for the target deployment ring' + default: 'ring-0' + required: false + type: string + environment: + required: false + type: string + secrets: + token: + required: false +``` + +For details of the syntax for defining inputs and secrets, see [on.workflow_call.inputs](/actions/reference/workflow-syntax-for-github-actions#onworkflow_callinputs) and [on.workflow_call.secrets](/actions/reference/workflow-syntax-for-github-actions#onworkflow_callsecrets). + +### Example reusable workflow + +This reusable workflow file named `workflow-B.yml` (we'll refer to this later) takes an input string and a secret from the caller workflow and uses them in an action. + +{% raw %} +```yaml{:copy} +name: Reusable workflow example + +on: + workflow_call: + inputs: + username: + required: true + type: string + secrets: + token: + required: true + +jobs: + example_job: + name: Pass input and secrets to my-action + runs-on: ubuntu-latest + steps: + - uses: ./.github/actions/my-action@v1 + with: + username: ${{ inputs.username }} + token: ${{ secrets.token }} +``` +{% endraw %} + +## Calling a reusable workflow + +You call a reusable workflow by using the `uses` keyword. Unlike when you are using actions within a workflow, you call reusable workflows directly within a job, and not from within job steps. + +[`jobs..uses`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_iduses) + +You reference reusable workflow files using the syntax: + +`{owner}/{repo}/{path}/{filename}@{ref}` + +You can call multiple workflows, referencing each in a separate job. + +{% data reusables.actions.uses-keyword-example %} + +### Passing inputs and secrets to a reusable workflow + +Use the `with` keyword in a job to pass named inputs to the called workflow. Use the `secrets` keyword to pass named secrets. The inputs and secrets you pass must be defined in the called workflow. For inputs, the data type of the input value must match the type specified for that input in the called workflow (boolean, number, or string). + +{% raw %} +```yaml +with: + username: mona +secrets: + token: ${{ secrets.TOKEN }} +``` +{% endraw %} + +### Supported keywords for jobs that call a reusable workflow + +When you call a reusable workflow, you can only use the following keywords in the job containing the call: + +* [`jobs..name`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idname) +* [`jobs..uses`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_iduses) +* [`jobs..with`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idwith) +* [`jobs..with.`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idwithinput_id) +* [`jobs..secrets`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idsecrets) +* [`jobs..secrets.`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idsecretssecret_id) +* [`jobs..needs`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds) +* [`jobs..if`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idif) +* [`jobs..permissions`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idpermissions) + + {% note %} + + **Примечание:** + + * If `jobs..permissions` is not specified in the calling job, the called workflow will have the default permissions for the `GITHUB_TOKEN`. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)." + * The `GITHUB_TOKEN` permissions passed from the caller workflow can be only downgraded (not elevated) by the called workflow. + + {% endnote %} + +### Example caller workflow + +This workflow file calls two workflow files. The second of these, `workflow-B.yml` (shown above), is passed an input, `username`, and a secret, `token`. + +{% raw %} +```yaml{:copy} +name: Call a reusable workflow + +on: + pull_request: + branches: + - main + +jobs: + call-workflow: + uses: octo-org/example-repo/.github/workflows/workflow-A.yml@v1 + + call-workflow-passing-data: + uses: octo-org/example-repo/.github/workflows/workflow-B.yml@main + with: + username: mona + secrets: + token: ${{ secrets.TOKEN }} +``` +{% endraw %} + +## Дальнейшие шаги + +To continue learning about {% data variables.product.prodname_actions %}, see "[Events that trigger workflows](/actions/learn-github-actions/events-that-trigger-workflows)." diff --git a/translations/ru-RU/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md b/translations/ru-RU/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md new file mode 100644 index 0000000000..545859d416 --- /dev/null +++ b/translations/ru-RU/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md @@ -0,0 +1,53 @@ +--- +title: 'Sharing workflows, secrets, and runners with your organization' +shortTitle: Sharing workflows with your organization +intro: 'Learn how you can use organization features to collaborate with your team, by sharing workflow templates, secrets, and self-hosted runners.' +redirect_from: + - /actions/learn-github-actions/sharing-workflows-with-your-organization +versions: + fpt: '*' + ghes: '*' + ghae: '*' +type: how_to +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +## Обзор + +If you need to share workflows and other {% data variables.product.prodname_actions %} features with your team, then consider collaborating within a {% data variables.product.prodname_dotcom %} organization. An organization allows you to centrally store and manage secrets, artifacts, and self-hosted runners. You can also create workflow templates in the `.github` repository and share them with other users in your organization. + +## Using workflow templates + +{% data reusables.actions.workflow-organization-templates %} For more information, see "[Creating workflow templates](/actions/learn-github-actions/creating-workflow-templates)." + +{% data reusables.actions.reusable-workflows %} + +## Sharing secrets within an organization + +You can centrally manage your secrets within an organization, and then make them available to selected repositories. This also means that you can update a secret in one location, and have the change apply to all repository workflows that use the secret. + +When creating a secret in an organization, you can use a policy to limit which repositories can access that secret. For example, you can grant access to all repositories, or limit access to only private repositories or a specified list of repositories. + +{% data reusables.github-actions.permissions-statement-secrets-organization %} + +{% data reusables.organizations.navigate-to-org %} +{% data reusables.organizations.org_settings %} +{% data reusables.github-actions.sidebar-secret %} +1. Click **New secret**. +1. Type a name for your secret in the **Name** input box. +1. Enter the **Value** for your secret. +1. From the **Repository access** dropdown list, choose an access policy. +1. Click **Add secret**. + +## Share self-hosted runners within an organization + +Organization admins can add their self-hosted runners to groups, and then create policies that control which repositories can access the group. + +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)." + + +## Дальнейшие шаги + +To continue learning about {% data variables.product.prodname_actions %}, see "[Creating workflow templates](/actions/learn-github-actions/creating-workflow-templates)." diff --git a/translations/ru-RU/content/actions/learn-github-actions/understanding-github-actions.md b/translations/ru-RU/content/actions/learn-github-actions/understanding-github-actions.md index acf722d73a..d0d1cdcd3e 100644 --- a/translations/ru-RU/content/actions/learn-github-actions/understanding-github-actions.md +++ b/translations/ru-RU/content/actions/learn-github-actions/understanding-github-actions.md @@ -18,7 +18,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Обзор @@ -36,7 +35,7 @@ Below is a list of the multiple {% data variables.product.prodname_actions %} co ### Workflows -The workflow is an automated procedure that you add to your repository. Workflows are made up of one or more jobs and can be scheduled or triggered by an event. The workflow can be used to build, test, package, release, or deploy a project on {% data variables.product.prodname_dotcom %}. +The workflow is an automated procedure that you add to your repository. Workflows are made up of one or more jobs and can be scheduled or triggered by an event. The workflow can be used to build, test, package, release, or deploy a project on {% data variables.product.prodname_dotcom %}. {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %}You can reference a workflow within another workflow, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."{% endif %} ### События diff --git a/translations/ru-RU/content/actions/learn-github-actions/usage-limits-billing-and-administration.md b/translations/ru-RU/content/actions/learn-github-actions/usage-limits-billing-and-administration.md index dcf498b72b..35d0f2b572 100644 --- a/translations/ru-RU/content/actions/learn-github-actions/usage-limits-billing-and-administration.md +++ b/translations/ru-RU/content/actions/learn-github-actions/usage-limits-billing-and-administration.md @@ -16,7 +16,6 @@ shortTitle: Workflow billing & limits {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About billing for {% data variables.product.prodname_actions %} @@ -61,6 +60,12 @@ Usage limits apply to self-hosted runners. For more information, see "[About sel In addition to the usage limits, you must ensure that you use {% data variables.product.prodname_actions %} within the [GitHub Terms of Service](/articles/github-terms-of-service/). For more information on {% data variables.product.prodname_actions %}-specific terms, see the [GitHub Additional Product Terms](/github/site-policy/github-additional-product-terms#a-actions-usage). {% endif %} +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## Billing for reusable workflows + +If you reuse a workflow, billing is always associated with the caller workflow. For more information see, "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." +{% endif %} + {% ifversion fpt or ghes > 2.22 or ghae %} ## Artifact and log retention policy diff --git a/translations/ru-RU/content/actions/learn-github-actions/using-workflow-templates.md b/translations/ru-RU/content/actions/learn-github-actions/using-workflow-templates.md index f888cca74d..d1d2f6d1d0 100644 --- a/translations/ru-RU/content/actions/learn-github-actions/using-workflow-templates.md +++ b/translations/ru-RU/content/actions/learn-github-actions/using-workflow-templates.md @@ -1,7 +1,7 @@ --- title: Using workflow templates shortTitle: Using templates -intro: You can set up CI using a workflow template that matches the language and tooling you want to use. +intro: '{% data variables.product.product_name %} provides workflow templates for a variety of languages and tooling.' product: '{% data reusables.gated-features.actions %}' redirect_from: - /articles/setting-up-continuous-integration-using-github-actions @@ -17,34 +17,37 @@ type: tutorial topics: - Workflows - CI + - CD --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -Anyone with write permission to a repository can set up continuous integration (CI) using {% data variables.product.prodname_actions %}. +## About workflow templates -After you set up CI, you can customize the workflow to meet your needs. +{% data variables.product.product_name %} offers workflow templates for a variety of languages and tooling. When you set up workflows in your repository, {% data variables.product.product_name %} analyzes the code in your repository and recommends workflows based on the language and framework in your repository. For example, if you use [Node.js](https://nodejs.org/en/), {% data variables.product.product_name %} will suggest a template file that installs your Node.js packages and runs your tests. + +You can also create your own workflow templates to share with your organization. For more information, see "[Creating workflow templates](/actions/learn-github-actions/creating-workflow-templates)." + +## Using workflow templates + +Anyone with write permission to a repository can set up {% data variables.product.prodname_actions %} workflows for CI/CD or other automation. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} -1. Find the template that matches the language and tooling you want to use, then click **Set up this workflow**. ![Setup workflow button](/assets/images/help/repository/setup-workflow-button.png) -5. Click **Start commit**. ![Start commit button](/assets/images/help/repository/start-commit.png) -{% data reusables.files.write_commit_message %} -{% data reusables.files.choose_commit_branch %} -{% data reusables.files.propose_new_file %} - -Once a push is made to your repository, you can follow the status and detailed logs of your continuous integration workflow run on {% data variables.product.prodname_dotcom %} and receive customized notifications. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)" and "[Managing a workflow run](/articles/managing-a-workflow-run)." - -{% 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)." +1. If you already have a workflow in your repository, click **New workflow**. +1. Find the template that you want to use, then click **Set up this workflow**. +1. If the workflow template contains comments detailing additional setup steps, follow these steps. +1. Some workflow templates use secrets. For example, {% raw %}`${{ secrets.npm_token }}`{% endraw %}. If the workflow template uses a secret, store the value described in the secret name as a secret in your repository. For more information, see "[Encrypted secrets](/actions/reference/encrypted-secrets)." +1. Optionally, make additional changes. For example, you might want to change the value of `on` to change when the workflow runs. +1. Click **Start commit**. +1. Write a commit message and decide whether to commit directly to the default branch or to open a pull request. ## Дополнительная литература - "[About continuous integration](/articles/about-continuous-integration)" -- "[Managing a workflow run](/articles/managing-a-workflow-run)" +- "[Managing workflow runs](/actions/managing-workflow-runs)" +- "[About monitoring and troubleshooting](/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting)" - "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" {% ifversion fpt %} - "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)" diff --git a/translations/ru-RU/content/actions/learn-github-actions/workflow-commands-for-github-actions.md b/translations/ru-RU/content/actions/learn-github-actions/workflow-commands-for-github-actions.md index 6ae188632e..6476c856fa 100644 --- a/translations/ru-RU/content/actions/learn-github-actions/workflow-commands-for-github-actions.md +++ b/translations/ru-RU/content/actions/learn-github-actions/workflow-commands-for-github-actions.md @@ -18,7 +18,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About workflow commands @@ -89,7 +88,7 @@ The following table shows which toolkit functions are available within a workflo | `core.setOutput` | `set-output` | | `core.setSecret` | `add-mask` | | `core.startGroup` | `группа` | -| `core.warning` | `warning file` | +| `core.warning` | `предупреждение` | {% ifversion ghes < 3.0 %} ## Setting an environment variable @@ -331,6 +330,12 @@ echo "{name}={value}" >> $GITHUB_ENV Creates or updates an environment variable for any steps running next in a job. The step that creates or updates the environment variable does not have access to the new value, but all subsequent steps in a job will have access. Environment variables are case-sensitive and you can include punctuation. +{% note %} + +**Note:** Environment variables must be explicitly referenced using the [`env` context](/actions/reference/context-and-expression-syntax-for-github-actions#env-context) in expression syntax or through use of the `$GITHUB_ENV` file directly; environment variables are not implicitly available in shell commands. + +{% endnote %} + ### Пример {% raw %} @@ -376,7 +381,7 @@ steps: echo "{path}" >> $GITHUB_PATH ``` -Prepends a directory to the system `PATH` variable and makes it available to all subsequent actions in the current job; the currently running action cannot access the updated path variable. To see the currently defined paths for your job, you can use `echo "$PATH"` in a step or an action. +Prepends a directory to the system `PATH` variable and automatically makes it available to all subsequent actions in the current job; the currently running action cannot access the updated path variable. To see the currently defined paths for your job, you can use `echo "$PATH"` in a step or an action. ### Пример diff --git a/translations/ru-RU/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md b/translations/ru-RU/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md index d4abe2d924..847c8aef9d 100644 --- a/translations/ru-RU/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md +++ b/translations/ru-RU/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md @@ -16,7 +16,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About YAML syntax for workflows @@ -184,9 +183,91 @@ Diffs are limited to 300 files. If there are files changed that aren't matched i For more information, see "[About comparing branches in pull requests](/articles/about-comparing-branches-in-pull-requests)." +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## `on.workflow_call.inputs` + +When using the `workflow_call` keyword, you can optionally specify inputs that are passed to the called workflow from the caller workflow. Inputs for reusable workflows are specified with the same format as action inputs. For more information about inputs, see "[Metadata syntax for GitHub Actions](/actions/creating-actions/metadata-syntax-for-github-actions#inputs)." For more information about the `workflow_call` keyword, see "[Events that trigger workflows](/actions/learn-github-actions/events-that-trigger-workflows#workflow-reuse-events)." + +In addition to the standard input parameters that are available, `on.workflow_call.inputs` requires a `type` parameter. For more information, see [`on.workflow_call..type`](#onworkflow_callinput_idtype). + +If a `default` parameter is not set, the default value of the input is `false` for a boolean, `0` for a number, and `""` for a string. + +Within the called workflow, you can use the `inputs` context to refer to an input. + +If a caller workflow passes an input that is not specified in the called workflow, this results in an error. + +### Пример + +{% raw %} +```yaml +on: + workflow_call: + inputs: + username: + description: 'A username passed from the caller workflow' + default: 'john-doe' + required: false + type: string + +jobs: + print-username: + runs-on: ubuntu-latest + + steps: + - name: Print the input name to STDOUT + run: echo The username is ${{ inputs.username }} +``` +{% endraw %} + +For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." + +## `on.workflow_call..type` + +Required if input is defined for the `on.workflow_call` keyword. The value of this parameter is a string specifying the data type of the input. This must be one of: `boolean`, `number`, or `string`. + +## `on.workflow_call.secrets` + +A map of the secrets that can be used in the called workflow. + +Within the called workflow, you can use the `secrets` context to refer to a secret. + +If a caller workflow passes a secret that is not specified in the called workflow, this results in an error. + +### Пример + +{% raw %} +```yaml +on: + workflow_call: + secrets: + access-token: + description: 'A token passed from the caller workflow' + required: false + +jobs: + pass-secret-to-action: + runs-on: ubuntu-latest + + steps: + - name: Pass the received secret to an action + uses: ./.github/actions/my-action@v1 + with: + token: ${{ secrets.access-token }} +``` +{% endraw %} + +## `on.workflow_call.secrets.` + +A string identifier to associate with the secret. + +## `on.workflow_call.secrets..required` + +A boolean specifying whether the secret must be supplied. +{% endif %} + ## `on.workflow_dispatch.inputs` -When using `workflow_dispatch` event, you can optionally specify inputs that are passed to the workflow. Workflow dispatch inputs are specified with the same format as action inputs. For more information about the format see "[Metadata syntax for GitHub Actions](/actions/creating-actions/metadata-syntax-for-github-actions#inputs)." +When using the `workflow_dispatch` event, you can optionally specify inputs that are passed to the workflow. Workflow dispatch inputs are specified with the same format as action inputs. For more information about the format see "[Metadata syntax for GitHub Actions](/actions/creating-actions/metadata-syntax-for-github-actions#inputs)." ```yaml on: @@ -272,8 +353,6 @@ defaults: {% ifversion fpt or ghae-next or ghes > 3.1 %} ## `concurrency` -{% data reusables.actions.concurrency-beta %} - Concurrency ensures that only a single job or workflow using the same concurrency group will run at a time. A concurrency group can be any string or expression. The expression can only use the [`github` context](/actions/learn-github-actions/contexts#github-context). For more information about expressions, see "[Expressions](/actions/learn-github-actions/expressions)." You can also specify `concurrency` at the job level. For more information, see [`jobs..concurrency`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idconcurrency). @@ -428,7 +507,7 @@ jobs: {% ifversion fpt or ghes > 3.0 or ghae %} ## `jobs..environment` -The environment that the job references. All environment protection rules must pass before a job referencing the environment is sent to a runner. For more information, see "[Environments](/actions/reference/environments)." +The environment that the job references. All environment protection rules must pass before a job referencing the environment is sent to a runner. For more information, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." You can provide the environment as only the environment `name`, or as an environment object with the `name` and `url`. The URL maps to `environment_url` in the deployments API. For more information about the deployments API, see "[Deployments](/rest/reference/repos#deployments)." @@ -463,8 +542,6 @@ environment: {% ifversion fpt or ghae-next or ghes > 3.1 %} ## `jobs..concurrency` -{% data reusables.actions.concurrency-beta %} - {% note %} **Note:** When concurrency is specified at the job level, order is not guaranteed for jobs or runs that queue within 5 minutes of each other. @@ -1348,6 +1425,70 @@ Additional Docker container resource options. For a list of options, see "[`dock {% endwarning %} +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## `jobs..uses` + +The location and version of a reusable workflow file to run as a job. + +`{owner}/{repo}/{path}/{filename}@{ref}` + +`{ref}` can be a SHA, a release tag, or a branch name. Using the commit SHA is the safest for stability and security. For more information, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#reusing-third-party-workflows)." + +### Пример + +{% data reusables.actions.uses-keyword-example %} + +For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." + +## `jobs..with` + +When a job is used to call a reusable workflow, you can use `with` to provide a map of inputs that are passed to the called workflow. + +Any inputs that you pass must match the input specifications defined in the called workflow. + +Unlike [`jobs..steps[*].with`](#jobsjob_idstepswith), the inputs you pass with `jobs..with` are not be available as environment variables in the called workflow. Instead, you can reference the inputs by using the `inputs` context. + +### Пример + +```yaml +jobs: + call-workflow: + uses: octo-org/example-repo/.github/workflows/called-workflow.yml@main + with: + username: mona +``` + +## `jobs..with.` + +A pair consisting of a string identifier for the input and the value of the input. The identifier must match the name of an input defined by [`on.workflow_call.inputs.`](/actions/creating-actions/metadata-syntax-for-github-actions#inputsinput_id) in the called workflow. The data type of the value must match the type defined by [`on.workflow_call..type`](#onworkflow_callinput_idtype) in the called workflow. + +Allowed expression contexts: `github`, and `needs`. + +## `jobs..secrets` + +When a job is used to call a reusable workflow, you can use `secrets` to provide a map of secrets that are passed to the called workflow. + +Any secrets that you pass must match the names defined in the called workflow. + +### Пример + +{% raw %} +```yaml +jobs: + call-workflow: + uses: octo-org/example-repo/.github/workflows/called-workflow.yml@main + secrets: + access-token: ${{ secrets.PERSONAL_ACCESS_TOKEN }} +``` +{% endraw %} + +## `jobs..secrets.` + +A pair consisting of a string identifier for the secret and the value of the secret. The identifier must match the name of a secret defined by [`on.workflow_call.secrets.`](#onworkflow_callsecretssecret_id) in the called workflow. + +Allowed expression contexts: `github`, `needs`, and `secrets`. +{% endif %} + ## Filter pattern cheat sheet You can use special characters in path, branch, and tag filters. diff --git a/translations/ru-RU/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md b/translations/ru-RU/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md index 3719e310da..9d4fe60a67 100644 --- a/translations/ru-RU/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md +++ b/translations/ru-RU/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md @@ -16,8 +16,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## Introduction diff --git a/translations/ru-RU/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md b/translations/ru-RU/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md index c1200ee5ee..e65193ba9e 100644 --- a/translations/ru-RU/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md +++ b/translations/ru-RU/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md @@ -16,8 +16,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## Introduction diff --git a/translations/ru-RU/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md b/translations/ru-RU/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md index 892705d76b..5f8007b6dc 100644 --- a/translations/ru-RU/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md +++ b/translations/ru-RU/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md @@ -17,8 +17,6 @@ shortTitle: Add label to comment on issue {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## Introduction diff --git a/translations/ru-RU/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md b/translations/ru-RU/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md index 5b6b94eaab..4bcd2f98e4 100644 --- a/translations/ru-RU/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md +++ b/translations/ru-RU/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md @@ -17,8 +17,6 @@ shortTitle: Move assigned issues {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## Introduction diff --git a/translations/ru-RU/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md b/translations/ru-RU/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md index 516babeb7d..c297820500 100644 --- a/translations/ru-RU/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md +++ b/translations/ru-RU/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md @@ -17,8 +17,6 @@ shortTitle: Remove label when adding card {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## Introduction diff --git a/translations/ru-RU/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md b/translations/ru-RU/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md index 80f7e14f7c..5eabde35f7 100644 --- a/translations/ru-RU/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md +++ b/translations/ru-RU/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md @@ -16,8 +16,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## Introduction diff --git a/translations/ru-RU/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md b/translations/ru-RU/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md index fcb7ebb0dc..4a03ed477d 100644 --- a/translations/ru-RU/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md +++ b/translations/ru-RU/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md @@ -9,7 +9,9 @@ shortTitle: Approve public fork runs ## About workflow runs from public forks -{% data reusables.actions.workflow-run-approve-public-fork %} However, you can configure this behavior for a [repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks), [organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#configuring-required-approval-for-workflows-from-public-forks), or [enterprise](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account#configuring-required-approval-for-workflows-from-public-forks). +{% data reusables.actions.workflow-run-approve-public-fork %} + +You can configure workflow approval requirements for a [repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks), [organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#configuring-required-approval-for-workflows-from-public-forks), or [enterprise](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account#configuring-required-approval-for-workflows-from-public-forks). Workflow runs that have been awaiting approval for more than 30 days are automatically deleted. diff --git a/translations/ru-RU/content/actions/managing-workflow-runs/canceling-a-workflow.md b/translations/ru-RU/content/actions/managing-workflow-runs/canceling-a-workflow.md index e8cc76712f..a2ec8ffea1 100644 --- a/translations/ru-RU/content/actions/managing-workflow-runs/canceling-a-workflow.md +++ b/translations/ru-RU/content/actions/managing-workflow-runs/canceling-a-workflow.md @@ -10,7 +10,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.repositories.permissions-statement-write %} diff --git a/translations/ru-RU/content/actions/managing-workflow-runs/deleting-a-workflow-run.md b/translations/ru-RU/content/actions/managing-workflow-runs/deleting-a-workflow-run.md index 1bcb1d4e20..042897fe01 100644 --- a/translations/ru-RU/content/actions/managing-workflow-runs/deleting-a-workflow-run.md +++ b/translations/ru-RU/content/actions/managing-workflow-runs/deleting-a-workflow-run.md @@ -10,7 +10,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.repositories.permissions-statement-write %} diff --git a/translations/ru-RU/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md b/translations/ru-RU/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md index da8394877b..3f500570a8 100644 --- a/translations/ru-RU/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md +++ b/translations/ru-RU/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md @@ -11,7 +11,6 @@ shortTitle: Disable & enable a workflow {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} Disabling a workflow allows you to stop a workflow from being triggered without having to delete the file from the repo. You can easily re-enable the workflow again on {% data variables.product.prodname_dotcom %}. diff --git a/translations/ru-RU/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md b/translations/ru-RU/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md index fb3accb468..2e783da2ea 100644 --- a/translations/ru-RU/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md +++ b/translations/ru-RU/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md @@ -11,7 +11,6 @@ shortTitle: Download workflow artifacts {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% ifversion fpt or ghes > 2.22 or ghae %} By default, {% data variables.product.product_name %} stores build logs and artifacts for 90 days, and you can customize this retention period, depending on the type of repository. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)."{% endif %} {% ifversion ghes = 2.22 %} {% data variables.product.product_name %} stores full build logs and artifacts for 90 days.{% endif %} diff --git a/translations/ru-RU/content/actions/managing-workflow-runs/index.md b/translations/ru-RU/content/actions/managing-workflow-runs/index.md index 140eccb9dd..24c7206c85 100644 --- a/translations/ru-RU/content/actions/managing-workflow-runs/index.md +++ b/translations/ru-RU/content/actions/managing-workflow-runs/index.md @@ -19,6 +19,7 @@ children: - /approving-workflow-runs-from-public-forks - /reviewing-deployments - /disabling-and-enabling-a-workflow + - /skipping-workflow-runs - /deleting-a-workflow-run - /downloading-workflow-artifacts - /removing-workflow-artifacts @@ -26,5 +27,3 @@ children: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% ifversion fpt or ghes > 3.0 or ghae %}{% endif %} diff --git a/translations/ru-RU/content/actions/managing-workflow-runs/manually-running-a-workflow.md b/translations/ru-RU/content/actions/managing-workflow-runs/manually-running-a-workflow.md index c85e0946cf..db4c6e8234 100644 --- a/translations/ru-RU/content/actions/managing-workflow-runs/manually-running-a-workflow.md +++ b/translations/ru-RU/content/actions/managing-workflow-runs/manually-running-a-workflow.md @@ -11,7 +11,6 @@ shortTitle: Manually run a workflow {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Configuring a workflow to run manually diff --git a/translations/ru-RU/content/actions/managing-workflow-runs/re-running-a-workflow.md b/translations/ru-RU/content/actions/managing-workflow-runs/re-running-a-workflow.md index c0d2b16991..395186ab96 100644 --- a/translations/ru-RU/content/actions/managing-workflow-runs/re-running-a-workflow.md +++ b/translations/ru-RU/content/actions/managing-workflow-runs/re-running-a-workflow.md @@ -11,7 +11,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} Re-running a workflow uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (Git ref) of the original event that triggered the workflow run. You can re-run a workflow up to 30 days after the initial run. diff --git a/translations/ru-RU/content/actions/managing-workflow-runs/removing-workflow-artifacts.md b/translations/ru-RU/content/actions/managing-workflow-runs/removing-workflow-artifacts.md index 038f068d20..3b992c5d29 100644 --- a/translations/ru-RU/content/actions/managing-workflow-runs/removing-workflow-artifacts.md +++ b/translations/ru-RU/content/actions/managing-workflow-runs/removing-workflow-artifacts.md @@ -11,7 +11,6 @@ shortTitle: Remove workflow artifacts {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Deleting an artifact diff --git a/translations/ru-RU/content/actions/managing-workflow-runs/reviewing-deployments.md b/translations/ru-RU/content/actions/managing-workflow-runs/reviewing-deployments.md index 5649b60107..a4fdb44853 100644 --- a/translations/ru-RU/content/actions/managing-workflow-runs/reviewing-deployments.md +++ b/translations/ru-RU/content/actions/managing-workflow-runs/reviewing-deployments.md @@ -8,13 +8,12 @@ versions: ghae: '*' --- -{% data reusables.actions.ae-beta %} ## About required reviews in workflows Jobs that reference an environment configured with required reviewers will wait for an approval before starting. While a job is awaiting approval, it has a status of "Waiting". If a job is not approved within 30 days, the workflow run will be automatically canceled. -For more information about environments and required approvals, see "[Environments](/actions/reference/environments)."{% ifversion fpt or ghae-next or ghes > 3.1 %} For information about how to review deployments with the REST API, see "[Workflow Runs](/rest/reference/actions#workflow-runs)."{% endif %} +For more information about environments and required approvals, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)."{% ifversion fpt or ghae-next or ghes > 3.1 %} For information about how to review deployments with the REST API, see "[Workflow Runs](/rest/reference/actions#workflow-runs)."{% endif %} ## Approving or rejecting a job diff --git a/translations/ru-RU/content/actions/managing-workflow-runs/skipping-workflow-runs.md b/translations/ru-RU/content/actions/managing-workflow-runs/skipping-workflow-runs.md new file mode 100644 index 0000000000..09cd92c4fe --- /dev/null +++ b/translations/ru-RU/content/actions/managing-workflow-runs/skipping-workflow-runs.md @@ -0,0 +1,33 @@ +--- +title: Skipping workflow runs +intro: 'You can skip workflow runs triggered by the `push` and `pull_request` events by including a command in your commit message.' +product: '{% data reusables.gated-features.actions %}' +versions: + fpt: '*' + ghes: '>=3.0' + ghae: 'ghae-next' +shortTitle: Skip workflow runs +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +Workflows that would otherwise be triggered using `on: push` or `on: pull_request` won't be triggered if you add any of the following strings to the commit message in a push, or the HEAD commit of a pull request: + +* `[skip ci]` +* `[ci skip]` +* `[no ci]` +* `[skip actions]` +* `[actions skip]` + +Alternatively, you can end the commit message with two empty lines followed by either `skip-checks: true` or `skip-checks:true`. + +You won't be able to merge the pull request if your repository is configured to require specific checks to pass first. To allow the pull request to be merged you can push a new commit to the pull request without the skip instruction in the commit message. + +{% note %} + +**Note:** Skip instructions only apply to the `push` and `pull_request` events. For example, adding `[skip ci]` to a commit message won't stop a workflow that's triggered `on: pull_request_target` from running. + +{% endnote %} + +Skip instructions only apply to the workflow run(s) that would be triggered by the commit that contains the skip instructions. You can also disable a workflow from running. For more information, see "[Disabling and enabling a workflow](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)." \ No newline at end of file diff --git a/translations/ru-RU/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md b/translations/ru-RU/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md index e7d75e2786..7b984b2d75 100644 --- a/translations/ru-RU/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md +++ b/translations/ru-RU/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md @@ -19,7 +19,6 @@ shortTitle: Migrate from Azure Pipelines {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ru-RU/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md b/translations/ru-RU/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md index 1996ddfea7..945c505f2c 100644 --- a/translations/ru-RU/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md +++ b/translations/ru-RU/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md @@ -19,7 +19,6 @@ shortTitle: Migrate from CircleCI {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ru-RU/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md b/translations/ru-RU/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md index de26c22604..f598b1f9a1 100644 --- a/translations/ru-RU/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md +++ b/translations/ru-RU/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md @@ -18,7 +18,6 @@ shortTitle: Migrate from GitLab CI/CD {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ru-RU/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md b/translations/ru-RU/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md index 73cbaa2fd3..ec7b82f2b7 100644 --- a/translations/ru-RU/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md +++ b/translations/ru-RU/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md @@ -19,7 +19,6 @@ shortTitle: Migrate from Jenkins {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ru-RU/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/ru-RU/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md index 69fd2e71d3..fbb81a20c0 100644 --- a/translations/ru-RU/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md +++ b/translations/ru-RU/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md @@ -19,7 +19,6 @@ shortTitle: Migrate from Travis CI {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ru-RU/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md b/translations/ru-RU/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md index 725c03b82a..d418742dce 100644 --- a/translations/ru-RU/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md +++ b/translations/ru-RU/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md @@ -12,7 +12,6 @@ miniTocMaxHeadingLevel: 3 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Monitoring your workflows diff --git a/translations/ru-RU/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md b/translations/ru-RU/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md index 5c909329a6..26fd37d18f 100644 --- a/translations/ru-RU/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md +++ b/translations/ru-RU/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md @@ -13,7 +13,6 @@ shortTitle: Add a status badge {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.repositories.actions-workflow-status-badge-intro %} diff --git a/translations/ru-RU/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md b/translations/ru-RU/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md index 2b61c09cc5..a0d12f5bbf 100644 --- a/translations/ru-RU/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md +++ b/translations/ru-RU/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md @@ -12,7 +12,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} These extra logs are enabled by setting secrets in the repository containing the workflow, so the same permissions requirements will apply: diff --git a/translations/ru-RU/content/actions/monitoring-and-troubleshooting-workflows/index.md b/translations/ru-RU/content/actions/monitoring-and-troubleshooting-workflows/index.md index bda6bc8ded..36ad81e817 100644 --- a/translations/ru-RU/content/actions/monitoring-and-troubleshooting-workflows/index.md +++ b/translations/ru-RU/content/actions/monitoring-and-troubleshooting-workflows/index.md @@ -17,9 +17,8 @@ children: - /viewing-job-execution-time - /using-workflow-run-logs - /enabling-debug-logging + - /notifications-for-workflow-runs --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% ifversion fpt or ghes > 3.0 or ghae %}{% endif %} diff --git a/translations/ru-RU/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md b/translations/ru-RU/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md new file mode 100644 index 0000000000..dd1ef955b2 --- /dev/null +++ b/translations/ru-RU/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md @@ -0,0 +1,15 @@ +--- +title: Notifications for workflow runs +intro: You can subscribe to notifications about workflow runs that you trigger. +product: '{% data reusables.gated-features.actions %}' +versions: + fpt: '*' + ghes: '*' + ghae: '*' +shortTitle: Notification (Оповещения) +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +{% data reusables.repositories.workflow-notifications %} diff --git a/translations/ru-RU/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md b/translations/ru-RU/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md index 9e777686f6..4561fca6cb 100644 --- a/translations/ru-RU/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md +++ b/translations/ru-RU/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md @@ -13,7 +13,6 @@ shortTitle: Use the visualization graph {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} diff --git a/translations/ru-RU/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md b/translations/ru-RU/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md index 5fc1154c66..d6654699fa 100644 --- a/translations/ru-RU/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md +++ b/translations/ru-RU/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md @@ -12,7 +12,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} You can see whether a workflow run is in progress or complete from the workflow run page. You must be logged in to a {% data variables.product.prodname_dotcom %} account to view workflow run information, including for public repositories. For more information, see "[Access permissions on GitHub](/articles/access-permissions-on-github)." diff --git a/translations/ru-RU/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md b/translations/ru-RU/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md index 761e2e50b8..39f9281319 100644 --- a/translations/ru-RU/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md +++ b/translations/ru-RU/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md @@ -11,7 +11,6 @@ shortTitle: View job execution time {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} Billable job execution minutes are only shown for jobs run on private repositories that use {% data variables.product.prodname_dotcom %}-hosted runners. There are no billable minutes when using {% data variables.product.prodname_actions %} in public repositories or for jobs run on self-hosted runners. diff --git a/translations/ru-RU/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md b/translations/ru-RU/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md index 63f816006e..dede9fbe22 100644 --- a/translations/ru-RU/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md +++ b/translations/ru-RU/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md @@ -13,7 +13,6 @@ shortTitle: View workflow run history {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.repositories.permissions-statement-read %} diff --git a/translations/ru-RU/content/actions/publishing-packages/about-packaging-with-github-actions.md b/translations/ru-RU/content/actions/publishing-packages/about-packaging-with-github-actions.md index e9bdafc778..05af7afeaf 100644 --- a/translations/ru-RU/content/actions/publishing-packages/about-packaging-with-github-actions.md +++ b/translations/ru-RU/content/actions/publishing-packages/about-packaging-with-github-actions.md @@ -18,7 +18,6 @@ shortTitle: Packaging with GitHub Actions {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.package_registry.about-packaging-and-actions %} diff --git a/translations/ru-RU/content/actions/publishing-packages/publishing-docker-images.md b/translations/ru-RU/content/actions/publishing-packages/publishing-docker-images.md index 005a1401c6..5a26e8e259 100644 --- a/translations/ru-RU/content/actions/publishing-packages/publishing-docker-images.md +++ b/translations/ru-RU/content/actions/publishing-packages/publishing-docker-images.md @@ -18,7 +18,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ru-RU/content/actions/publishing-packages/publishing-java-packages-with-gradle.md b/translations/ru-RU/content/actions/publishing-packages/publishing-java-packages-with-gradle.md index a2b2a38fb7..a945659286 100644 --- a/translations/ru-RU/content/actions/publishing-packages/publishing-java-packages-with-gradle.md +++ b/translations/ru-RU/content/actions/publishing-packages/publishing-java-packages-with-gradle.md @@ -20,7 +20,6 @@ shortTitle: Java packages with Gradle {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ru-RU/content/actions/publishing-packages/publishing-java-packages-with-maven.md b/translations/ru-RU/content/actions/publishing-packages/publishing-java-packages-with-maven.md index 7812bd6103..144d68f629 100644 --- a/translations/ru-RU/content/actions/publishing-packages/publishing-java-packages-with-maven.md +++ b/translations/ru-RU/content/actions/publishing-packages/publishing-java-packages-with-maven.md @@ -20,7 +20,6 @@ shortTitle: Java packages with Maven {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ru-RU/content/actions/publishing-packages/publishing-nodejs-packages.md b/translations/ru-RU/content/actions/publishing-packages/publishing-nodejs-packages.md index 4f376933f6..c6c6278c6a 100644 --- a/translations/ru-RU/content/actions/publishing-packages/publishing-nodejs-packages.md +++ b/translations/ru-RU/content/actions/publishing-packages/publishing-nodejs-packages.md @@ -21,7 +21,6 @@ shortTitle: Node.js packages {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ru-RU/content/actions/quickstart.md b/translations/ru-RU/content/actions/quickstart.md index 7c29063e72..eb714c82f5 100644 --- a/translations/ru-RU/content/actions/quickstart.md +++ b/translations/ru-RU/content/actions/quickstart.md @@ -16,7 +16,6 @@ shortTitle: Quickstart {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ru-RU/content/actions/security-guides/automatic-token-authentication.md b/translations/ru-RU/content/actions/security-guides/automatic-token-authentication.md index a1d3d78ceb..712bc0b243 100644 --- a/translations/ru-RU/content/actions/security-guides/automatic-token-authentication.md +++ b/translations/ru-RU/content/actions/security-guides/automatic-token-authentication.md @@ -16,7 +16,6 @@ shortTitle: Automatic token authentication {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About the `GITHUB_TOKEN` secret diff --git a/translations/ru-RU/content/actions/security-guides/encrypted-secrets.md b/translations/ru-RU/content/actions/security-guides/encrypted-secrets.md index ff1f94eaf8..67422d81d6 100644 --- a/translations/ru-RU/content/actions/security-guides/encrypted-secrets.md +++ b/translations/ru-RU/content/actions/security-guides/encrypted-secrets.md @@ -16,7 +16,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About encrypted secrets diff --git a/translations/ru-RU/content/actions/security-guides/security-hardening-for-github-actions.md b/translations/ru-RU/content/actions/security-guides/security-hardening-for-github-actions.md index 48b283d979..74701e9673 100644 --- a/translations/ru-RU/content/actions/security-guides/security-hardening-for-github-actions.md +++ b/translations/ru-RU/content/actions/security-guides/security-hardening-for-github-actions.md @@ -18,7 +18,6 @@ miniTocMaxHeadingLevel: 3 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Обзор @@ -48,7 +47,7 @@ To help prevent accidental disclosure, {% data variables.product.product_name %} - Rotate secrets periodically to reduce the window of time during which a compromised secret is valid. {% ifversion fpt or ghes > 3.0 or ghae %} - **Consider requiring review for access to secrets** - - You can use required reviewers to protect environment secrets. A workflow job cannot access environment secrets until approval is granted by a reviewer. For more information about storing secrets in environments or requiring reviews for environments, see "[Encrypted secrets](/actions/reference/encrypted-secrets)" and "[Environments](/actions/reference/environments)." + - You can use required reviewers to protect environment secrets. A workflow job cannot access environment secrets until approval is granted by a reviewer. For more information about storing secrets in environments or requiring reviews for environments, see "[Encrypted secrets](/actions/reference/encrypted-secrets)" and "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." {% endif %} ## Using `CODEOWNERS` to monitor changes @@ -183,6 +182,12 @@ You can help mitigate this risk by following these good practices: Although pinning to a commit SHA is the most secure option, specifying a tag is more convenient and is widely used. If you’d like to specify a tag, then be sure that you trust the action's creators. The ‘Verified creator’ badge on {% data variables.product.prodname_marketplace %} is a useful signal, as it indicates that the action was written by a team whose identity has been verified by {% data variables.product.prodname_dotcom %}. Note that there is risk to this approach even if you trust the author, because a tag can be moved or deleted if a bad actor gains access to the repository storing the action. +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## Reusing third-party workflows + +The same principles described above for using third-party actions also apply to using third-party workflows. You can help mitigate the risks associated with reusing workflows by following the same good practices outlined above. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." +{% endif %} + ## Potential impact of a compromised runner These sections consider some of the steps an attacker can take if they're able to run malicious commands on a {% data variables.product.prodname_actions %} runner. diff --git a/translations/ru-RU/content/actions/using-containerized-services/about-service-containers.md b/translations/ru-RU/content/actions/using-containerized-services/about-service-containers.md index 198291beb5..af46f19707 100644 --- a/translations/ru-RU/content/actions/using-containerized-services/about-service-containers.md +++ b/translations/ru-RU/content/actions/using-containerized-services/about-service-containers.md @@ -18,7 +18,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About service containers diff --git a/translations/ru-RU/content/actions/using-containerized-services/creating-postgresql-service-containers.md b/translations/ru-RU/content/actions/using-containerized-services/creating-postgresql-service-containers.md index 885fcf9792..8c3a6167b6 100644 --- a/translations/ru-RU/content/actions/using-containerized-services/creating-postgresql-service-containers.md +++ b/translations/ru-RU/content/actions/using-containerized-services/creating-postgresql-service-containers.md @@ -19,7 +19,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ru-RU/content/actions/using-containerized-services/creating-redis-service-containers.md b/translations/ru-RU/content/actions/using-containerized-services/creating-redis-service-containers.md index 184c54a65b..378afa24fb 100644 --- a/translations/ru-RU/content/actions/using-containerized-services/creating-redis-service-containers.md +++ b/translations/ru-RU/content/actions/using-containerized-services/creating-redis-service-containers.md @@ -19,7 +19,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Introduction diff --git a/translations/ru-RU/content/actions/using-github-hosted-runners/about-ae-hosted-runners.md b/translations/ru-RU/content/actions/using-github-hosted-runners/about-ae-hosted-runners.md index 8b7ced1bdb..1963ba43e4 100644 --- a/translations/ru-RU/content/actions/using-github-hosted-runners/about-ae-hosted-runners.md +++ b/translations/ru-RU/content/actions/using-github-hosted-runners/about-ae-hosted-runners.md @@ -6,23 +6,16 @@ versions: ghae: '*' --- - - - -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} ## About {% data variables.actions.hosted_runner %}s -An {% data variables.actions.hosted_runner %} is a virtual machine hosted by {% data variables.product.prodname_dotcom %} with the {% data variables.product.prodname_actions %} runner service installed. +An {% data variables.actions.hosted_runner %} is a virtual machine managed by {% data variables.product.prodname_dotcom %} with the {% data variables.product.prodname_actions %} runner service installed. {% data variables.actions.hosted_runner %}s are dedicated to your enterprise, and you can choose from a range of hardware and software options. By default, {% data variables.actions.hosted_runner %}s are fully managed and auto-scaled by {% data variables.product.company_short %} to maximize performance while minimizing costs.{% ifversion ghae-next %} You can optionally configure the parameters of this auto-scaling to reduce your cost even more.{% endif %} -{% data variables.product.prodname_ghe_managed %} lets you create and customize {% data variables.actions.hosted_runner %}s using Ubuntu or Windows images; you can select the size of machine you want and configure security hardened networking for them. {% data variables.actions.hosted_runner %}s are fully managed and auto-scaled by {% data variables.product.prodname_dotcom %}. +{% data variables.product.prodname_ghe_managed %} lets you create and customize {% data variables.actions.hosted_runner %}s using Ubuntu or Windows images; you can select the size of machine you want and optionally configure a fixed public IP range for your {% data variables.actions.hosted_runner %}s. Each workflow job is executed in a fresh instance of the {% data variables.actions.hosted_runner %}, and you can run workflows directly on the virtual machine or in a Docker container. All steps in the job execute in the same instance, allowing the actions in that job to share information using the {% data variables.actions.hosted_runner %}'s filesystem. -{% note %} -{% data variables.actions.hosted_runner %}s are the only runners available for {% data variables.product.prodname_ghe_managed %}, and self-hosted runners are not available. -{% endnote %} - To add {% data variables.actions.hosted_runner %}s to your organization or enterprise, see ["Adding {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/adding-ae-hosted-runners)." ## Pool assignments for {% data variables.actions.hosted_runner %}s @@ -35,11 +28,9 @@ During the {% data variables.actions.hosted_runner %} beta, you can manage your ## Billing -{% data variables.product.prodname_actions %} is currently in beta for {% data variables.product.prodname_ghe_managed %}. During this beta period, {% data variables.actions.hosted_runner %}s are not billed, and can be used for free. - Once the beta ends, billed usage will include the full uptime of active instances in your AE hosted runner sets. This includes: - Job time - minutes spent running Actions job. -- Management - minutes spent re-imaging machines and any idle time created as a result of desired auto-scale behavior. +- Management - minutes spent re-imaging machines{% ifversion ghae-next %} and any idle time created as a result of desired auto-scale behavior{% endif %}. Pricing will scale linearly with cores. For example, 4 cores will be twice the price of 2 cores. Windows VMs will be priced higher than Linux VMs. @@ -78,6 +69,14 @@ To get a list of IP address ranges that {% data variables.product.prodname_actio The list of {% data variables.product.prodname_actions %} IP addresses returned by the API is updated once a week. +{% ifversion ghae-next %} + +## Autoscaling + +Each pool of {% data variables.actions.hosted_runner %}s is fully managed by {% data variables.product.company_short %} to maximize performance while minimizing costs. Optionally, you can configure the autoscaling parameters for your enterprise by contacting {% data variables.contact.github_support %}. You can define the minimum number of idle runners and how long a runner should remain idle before being removed from the pool. Each pool can contain up to 600 runners. + +{% endif %} + ## Administrative privileges for {% data variables.actions.hosted_runner %}s The Linux virtual machines run using passwordless `sudo`. When you need to execute commands or install tools that require more privileges than the current user, you can use `sudo` without needing to provide a password. For more information, see the "[Sudo Manual](https://www.sudo.ws/man/1.8.27/sudo.man.html)." diff --git a/translations/ru-RU/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/translations/ru-RU/content/actions/using-github-hosted-runners/about-github-hosted-runners.md index 53440aebaf..d30b13f5b6 100644 --- a/translations/ru-RU/content/actions/using-github-hosted-runners/about-github-hosted-runners.md +++ b/translations/ru-RU/content/actions/using-github-hosted-runners/about-github-hosted-runners.md @@ -16,6 +16,7 @@ versions: shortTitle: GitHub-hosted runners --- +{% data reusables.actions.ae-hosted-runners-beta %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} diff --git a/translations/ru-RU/content/actions/using-github-hosted-runners/adding-ae-hosted-runners.md b/translations/ru-RU/content/actions/using-github-hosted-runners/adding-ae-hosted-runners.md index 7dfa6fb26d..938ef00730 100644 --- a/translations/ru-RU/content/actions/using-github-hosted-runners/adding-ae-hosted-runners.md +++ b/translations/ru-RU/content/actions/using-github-hosted-runners/adding-ae-hosted-runners.md @@ -5,7 +5,7 @@ versions: ghae: '*' --- -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} {% note %} @@ -19,7 +19,8 @@ versions: You can add {% data variables.actions.hosted_runner %}s that use the base Azure operating system images. To add {% data variables.actions.hosted_runner %}s to your organization or enterprise, contact {% data variables.product.prodname_dotcom %} support and have the following information ready: - Required operating system: Available options are listed at ["Software specifications](/actions/using-github-hosted-runners/about-ae-hosted-runners#software-specifications)." - - Choose a name for each pool of {% data variables.actions.hosted_runner %}s. These names are created as labels, allowing you to route your workflows to these runners. For more information, see ["Using {% data variables.actions.hosted_runner %}s in a workflow](/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow)." + - Choose a name for each pool of {% data variables.actions.hosted_runner %}s. These names are created as labels, allowing you to route your workflows to these runners. For more information, see ["Using {% data variables.actions.hosted_runner %}s in a workflow](/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow)."{% ifversion ghae-next %} +{% data reusables.actions.autoscaling-parameters %}{% endif %} - Where to add the {% data variables.actions.hosted_runner %}: Identify the names of the organizations and enterprises that will receive the runners. ## Adding an {% data variables.actions.hosted_runner %} with a custom image @@ -33,7 +34,8 @@ Once you've created a custom image using the above steps, contact {% data variab - Image name. - Версия. - VM SKU for the new pool. - - Choose a name for each pool of {% data variables.actions.hosted_runner %}s. These names are created as labels, allowing you to route your workflows to these runners. For more information, see ["Using {% data variables.actions.hosted_runner %}s in a workflow](/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow)." + - Choose a name for each pool of {% data variables.actions.hosted_runner %}s. These names are created as labels, allowing you to route your workflows to these runners. For more information, see ["Using {% data variables.actions.hosted_runner %}s in a workflow](/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow)."{% ifversion ghae-next %} +{% data reusables.actions.autoscaling-parameters %}{% endif %} - Where to add the {% data variables.actions.hosted_runner %}: Identify the names of the organizations and enterprises that will receive the runners. ## Reviewing your {% data variables.actions.hosted_runner %}s diff --git a/translations/ru-RU/content/actions/using-github-hosted-runners/creating-custom-images.md b/translations/ru-RU/content/actions/using-github-hosted-runners/creating-custom-images.md index c8369a8e24..5dfff3138d 100644 --- a/translations/ru-RU/content/actions/using-github-hosted-runners/creating-custom-images.md +++ b/translations/ru-RU/content/actions/using-github-hosted-runners/creating-custom-images.md @@ -5,7 +5,7 @@ versions: ghae: '*' --- -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} ## Creating an {% data variables.actions.hosted_runner %} with a custom image diff --git a/translations/ru-RU/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md b/translations/ru-RU/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md index db23278023..3fd637a69f 100644 --- a/translations/ru-RU/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md +++ b/translations/ru-RU/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md @@ -11,6 +11,7 @@ topics: shortTitle: Customize runners --- +{% data reusables.actions.ae-hosted-runners-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} If you require additional software packages on {% data variables.product.prodname_dotcom %}-hosted runners, you can create a job that installs the packages as part of your workflow. diff --git a/translations/ru-RU/content/actions/using-github-hosted-runners/index.md b/translations/ru-RU/content/actions/using-github-hosted-runners/index.md index 440c898ae1..16a4af837c 100644 --- a/translations/ru-RU/content/actions/using-github-hosted-runners/index.md +++ b/translations/ru-RU/content/actions/using-github-hosted-runners/index.md @@ -17,5 +17,6 @@ children: shortTitle: Use GitHub-hosted runners --- +{% data reusables.actions.ae-hosted-runners-beta %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} diff --git a/translations/ru-RU/content/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow.md b/translations/ru-RU/content/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow.md index 3e9154bf41..429c1cf356 100644 --- a/translations/ru-RU/content/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow.md +++ b/translations/ru-RU/content/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow.md @@ -6,7 +6,7 @@ versions: shortTitle: Use AE hosted runners --- -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} ## Using {% data variables.actions.hosted_runner %}s in a workflow diff --git a/translations/ru-RU/content/actions/using-github-hosted-runners/using-groups-to-manage-access-to-ae-hosted-runners.md b/translations/ru-RU/content/actions/using-github-hosted-runners/using-groups-to-manage-access-to-ae-hosted-runners.md index 8faf78c5c7..ea277daecd 100644 --- a/translations/ru-RU/content/actions/using-github-hosted-runners/using-groups-to-manage-access-to-ae-hosted-runners.md +++ b/translations/ru-RU/content/actions/using-github-hosted-runners/using-groups-to-manage-access-to-ae-hosted-runners.md @@ -6,7 +6,7 @@ versions: shortTitle: Manage AE runner groups --- -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} ## About {% data variables.actions.hosted_runner %} groups diff --git a/translations/ru-RU/content/actions/using-github-hosted-runners/using-labels-with-ae-hosted-runners.md b/translations/ru-RU/content/actions/using-github-hosted-runners/using-labels-with-ae-hosted-runners.md index a45dd40202..9b134dcf8f 100644 --- a/translations/ru-RU/content/actions/using-github-hosted-runners/using-labels-with-ae-hosted-runners.md +++ b/translations/ru-RU/content/actions/using-github-hosted-runners/using-labels-with-ae-hosted-runners.md @@ -6,7 +6,7 @@ versions: shortTitle: Label AE hosted runners --- -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} For information on how to use labels to route jobs to specific types of {% data variables.actions.hosted_runner %}s, see "[Using {% data variables.actions.hosted_runner %}s in a workflow](/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow)." diff --git a/translations/ru-RU/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md b/translations/ru-RU/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md index 1b7a037ec9..4eae978e32 100644 --- a/translations/ru-RU/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md +++ b/translations/ru-RU/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md @@ -62,13 +62,13 @@ If you set up the {% data variables.product.prodname_codeql %} action sync tool, {% ifversion ghes = 2.22 %} To run {% data variables.product.prodname_code_scanning %} on {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_actions %}, the appropriate actions must be available locally. You can make the actions available in three ways. -- **Recommended**: You can use [{% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud) to automatically download actions from {% data variables.product.prodname_dotcom_the_website %}. The machine that hosts your instance must be able to access {% data variables.product.prodname_dotcom_the_website %}. This approach ensures that you get the latest software automatically. For more information, see "[Configuring {% data variables.product.prodname_github_connect %} to sync {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)." +- **Recommended**: You can use [{% data variables.product.prodname_github_connect %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud) to automatically download actions from {% data variables.product.prodname_dotcom_the_website %}. The machine that hosts your instance must be able to access {% data variables.product.prodname_dotcom_the_website %}. This approach ensures that you get the latest software automatically. For more information, see "[Configuring {% data variables.product.prodname_github_connect %} to sync {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)." - If you want to use the {% data variables.product.prodname_codeql_workflow %}, you can sync the repository from {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.prodname_ghe_server %}, by using the {% data variables.product.prodname_codeql %} Action sync tool available at [https://github.com/github/codeql-action-sync-tool](https://github.com/github/codeql-action-sync-tool/). You can use this tool regardless of whether {% data variables.product.product_location %} or your {% data variables.product.prodname_actions %} runners have access to the internet, as long as you can access both {% data variables.product.product_location %} and {% data variables.product.prodname_dotcom_the_website %} simultaneously on your computer. - You can create a local copy of an action's repository on your server, by cloning the {% data variables.product.prodname_dotcom_the_website %} repository that contains the action. For example, if you want to use the actions for {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}, you can create a repository in your instance called `github/codeql-action`, then clone the [repository](https://github.com/github/codeql-action) from {% data variables.product.prodname_dotcom_the_website %}, and then push that repository to your instance's `github/codeql-action` repository. You will also need to download any of the releases from the repository on {% data variables.product.prodname_dotcom_the_website %} and upload them to your instance's `github/codeql-action` repository as releases. {% endif %} ### Configuring {% data variables.product.prodname_github_connect %} to sync {% data variables.product.prodname_actions %} -1. If you want to download action workflows on demand from {% data variables.product.prodname_dotcom_the_website %}, you need to enable {% data variables.product.prodname_github_connect %}. For more information, see "[Enabling {% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud#enabling-github-connect)." +1. If you want to download action workflows on demand from {% data variables.product.prodname_dotcom_the_website %}, you need to enable {% data variables.product.prodname_github_connect %}. For more information, see "[Enabling {% data variables.product.prodname_github_connect %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud#enabling-github-connect)." 2. You'll also need to enable {% data variables.product.prodname_actions %} for {% data variables.product.product_location %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)." 3. The next step is to configure access to actions on {% data variables.product.prodname_dotcom_the_website %} using {% data variables.product.prodname_github_connect %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)." 4. Add a self-hosted runner to your repository, organization, or enterprise account. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)." diff --git a/translations/ru-RU/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md b/translations/ru-RU/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md index e5a890b6c5..f1d4d798bc 100644 --- a/translations/ru-RU/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md +++ b/translations/ru-RU/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md @@ -83,10 +83,14 @@ For example, you can enable any {% data variables.product.prodname_GH_advanced_s ```shell ghe-config app.secret-scanning.enabled true ``` - - To enable {% data variables.product.prodname_dependabot %}, enter the following command. - ```shell - {% ifversion ghes > 3.1 %}ghe-config app.dependency-graph.enabled true{% else %}ghe-config app.github.dependency-graph-enabled true{% endif %} + - To enable {% data variables.product.prodname_dependabot %}, enter the following {% ifversion ghes > 3.1 %}command{% else %}commands{% endif %}. + {% ifversion ghes > 3.1 %}```shell + ghe-config app.dependency-graph.enabled true ``` + {% else %}```shell + ghe-config app.github.dependency-graph-enabled true + ghe-config app.github.vulnerability-alerting-and-settings-enabled true + ```{% endif %} 2. Optionally, disable features for {% data variables.product.prodname_GH_advanced_security %}. - To disable {% data variables.product.prodname_code_scanning %}, enter the following commands. @@ -98,11 +102,14 @@ For example, you can enable any {% data variables.product.prodname_GH_advanced_s ```shell ghe-config app.secret-scanning.enabled false ``` - - To disable {% data variables.product.prodname_dependabot %}, enter the following command. - ```shell - {% ifversion ghes > 3.1 %}ghe-config app.dependency-graph.enabled false{% else %}ghe-config app.github.dependency-graph-enabled false{% endif %} + - To disable {% data variables.product.prodname_dependabot %}, enter the following {% ifversion ghes > 3.1 %}command{% else %}commands{% endif %}. + {% ifversion ghes > 3.1 %}```shell + ghe-config app.dependency-graph.enabled false ``` - + {% else %}```shell + ghe-config app.github.dependency-graph-enabled false + ghe-config app.github.vulnerability-alerting-and-settings-enabled false + ```{% endif %} 3. Apply the configuration. ```shell ghe-config-apply diff --git a/translations/ru-RU/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md b/translations/ru-RU/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md index 3147524872..67c7d5b760 100644 --- a/translations/ru-RU/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md +++ b/translations/ru-RU/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md @@ -23,7 +23,7 @@ When a proxy server is enabled for {% data variables.product.product_location %} {% note %} -**Note:** To connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}, your proxy configuration must allow connectivity to `github.com` and `api.github.com`. For more information, see "[Connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_dotcom_the_website %}](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/connecting-github-enterprise-server-to-github-com)." +**Note:** To connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}, your proxy configuration must allow connectivity to `github.com` and `api.github.com`. For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_dotcom_the_website %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." {% endnote %} @@ -34,7 +34,7 @@ When a proxy server is enabled for {% data variables.product.product_location %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.privacy %} -4. Under **HTTP Proxy Server**, type the URL of your proxy server. ![Field to type the HTTP Proxy Server URL](/assets/images/enterprise/management-console/http-proxy-field.png) +1. Under **HTTP Proxy Server**, type the URL of your proxy server. ![Field to type the HTTP Proxy Server URL](/assets/images/enterprise/management-console/http-proxy-field.png) 5. Optionally, under **HTTP Proxy Exclusion**, type any hosts that do not require proxy access, separating hosts with commas. To exclude all hosts in a domain from requiring proxy access, you can use `.` as a wildcard prefix. For example: `.octo-org.tentacle` ![Field to type any HTTP Proxy Exclusions](/assets/images/enterprise/management-console/http-proxy-exclusion-field.png) diff --git a/translations/ru-RU/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md b/translations/ru-RU/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md index b9ce8ba050..c87d6679e3 100644 --- a/translations/ru-RU/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md +++ b/translations/ru-RU/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md @@ -351,18 +351,6 @@ stop/waiting - ghe-replica-mode ``` -{% tip %} - -The service names returned from this command can be used with [`systemctl`](https://www.freedesktop.org/software/systemd/man/systemctl.html) commands to stop, start, or restart these services manually, if needed. Например: - -```shell -$ sudo systemctl restart github-resqued -``` - -Stopping services will cause downtime on your installation, so we recommend you contact {% data variables.contact.contact_ent_support %} before stopping or restarting any service. - -{% endtip %} - ### ghe-set-password With `ghe-set-password`, you can set a new password to authenticate into the [{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-management-console). @@ -808,7 +796,7 @@ $ ssh -p 122 admin@hostname -- 'ghe-update-check' ### ghe-license-usage -This utility exports a list of the installation's users in JSON format. If your instance is connected to {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %} uses this information for reporting licensing information to {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %} ](/enterprise/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)." +This utility exports a list of the installation's users in JSON format. If your instance is connected to {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %} uses this information for reporting licensing information to {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %} ](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." By default, the list of users in the resulting JSON file is encrypted. Use the `-h` flag for more options. diff --git a/translations/ru-RU/content/admin/configuration/index.md b/translations/ru-RU/content/admin/configuration/index.md index 5b2cfee3b4..c8181bf7f7 100644 --- a/translations/ru-RU/content/admin/configuration/index.md +++ b/translations/ru-RU/content/admin/configuration/index.md @@ -12,7 +12,7 @@ topics: children: - /configuring-your-enterprise - /configuring-network-settings - - /managing-connections-between-github-enterprise-server-and-github-enterprise-cloud + - /managing-connections-between-your-enterprise-accounts --- {% ifversion ghes %} diff --git a/translations/ru-RU/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md b/translations/ru-RU/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md new file mode 100644 index 0000000000..f1989a6f40 --- /dev/null +++ b/translations/ru-RU/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md @@ -0,0 +1,83 @@ +--- +title: Connecting your enterprise account to GitHub Enterprise Cloud +shortTitle: Connect enterprise accounts +intro: 'After you enable {% data variables.product.prodname_github_connect %}, you can share specific features and workflows between {% data variables.product.product_location %} and {% data variables.product.prodname_ghe_cloud %}.' +redirect_from: + - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-to-github-com/ + - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-server-to-github-com + - /enterprise/admin/developer-workflow/connecting-github-enterprise-server-to-githubcom/ + - /enterprise/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud + - /enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud + - /admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud +permissions: 'Enterprise owners who are also owners of a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable {% data variables.product.prodname_github_connect %}.' +versions: + ghes: '*' + ghae: next +type: how_to +topics: + - Enterprise + - GitHub Connect + - Infrastructure + - Networking +--- + +{% data reusables.github-connect.beta %} + +## About {% data variables.product.prodname_github_connect %} + +To enable {% data variables.product.prodname_github_connect %}, you must configure the connection in both {% data variables.product.product_location %} and in your {% data variables.product.prodname_ghe_cloud %} organization or enterprise account. + +{% ifversion ghes %} +To configure a connection, your proxy configuration must allow connectivity to `github.com` and `api.github.com`. For more information, see "[Configuring an outbound web proxy server](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-an-outbound-web-proxy-server)." +{% endif %} + +After enabling {% data variables.product.prodname_github_connect %}, you will be able to enable features such as unified search and unified contributions. For more information about all of the features available, see "[Managing connections between your enterprise accounts](/admin/configuration/managing-connections-between-your-enterprise-accounts)." + +When you connect {% data variables.product.product_location %} to {% data variables.product.prodname_ghe_cloud %}, a record on {% data variables.product.prodname_dotcom_the_website %} stores information about the connection: +{% ifversion ghes %} +- The public key portion of your {% data variables.product.prodname_ghe_server %} license +- A hash of your {% data variables.product.prodname_ghe_server %} license +- The customer name on your {% data variables.product.prodname_ghe_server %} license +- The version of {% data variables.product.product_location_enterprise %}{% endif %} +- The hostname of your {% data variables.product.product_name %} instance +- The organization or enterprise account on {% data variables.product.prodname_dotcom_the_website %} that's connected to {% data variables.product.product_location %} +- The authentication token that's used by {% data variables.product.product_location %} to make requests to {% data variables.product.prodname_dotcom_the_website %} + +Enabling {% data variables.product.prodname_github_connect %} also creates a {% data variables.product.prodname_github_app %} owned by your {% data variables.product.prodname_ghe_cloud %} organization or enterprise account. {% data variables.product.product_name %} uses the {% data variables.product.prodname_github_app %}'s credentials to make requests to {% data variables.product.prodname_dotcom_the_website %}. +{% ifversion ghes %} +{% data variables.product.prodname_ghe_server %} stores credentials from the {% data variables.product.prodname_github_app %}. These credentials will be replicated to any high availability or clustering environments, and stored in any backups, including snapshots created by {% data variables.product.prodname_enterprise_backup_utilities %}. +- An authentication token, which is valid for one hour +- A private key, which is used to generate a new authentication token +{% endif %} + +Enabling {% data variables.product.prodname_github_connect %} will not allow {% data variables.product.prodname_dotcom_the_website %} users to make changes to {% data variables.product.product_name %}. + +For more information about managing enterprise accounts using the GraphQL API, see "[Enterprise accounts](/graphql/guides/managing-enterprise-accounts)." +## Enabling {% data variables.product.prodname_github_connect %} + +{% ifversion ghes %} +1. Sign in to {% data variables.product.product_location %} and {% data variables.product.prodname_dotcom_the_website %}. +{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %}{% else %} +1. Sign in to {% data variables.product.product_location %} and {% data variables.product.prodname_dotcom_the_website %}. +{% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %} +1. Under "{% data variables.product.prodname_github_connect %} is not enabled yet", click **Enable {% data variables.product.prodname_github_connect %}**. By clicking **Enable {% data variables.product.prodname_github_connect %}**, you agree to the "{% data variables.product.prodname_dotcom %} Terms for Additional Products and Features." +{% ifversion ghes %} +![Enable GitHub Connect button](/assets/images/enterprise/business-accounts/enable-github-connect-button.png){% else %} +![Enable GitHub Connect button](/assets/images/enterprise/github-ae/enable-github-connect-button.png) +{% endif %} +1. Next to the enterprise account or organization you'd like to connect, click **Connect**. ![Connect button next to an enterprise account or business](/assets/images/enterprise/business-accounts/choose-enterprise-or-org-connect.png) + +## Disconnecting a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account from your enterprise account + +When you disconnect from {% data variables.product.prodname_ghe_cloud %}, the {% data variables.product.prodname_github_connect %} {% data variables.product.prodname_github_app %} is deleted from your enterprise account or organization and credentials stored on {% data variables.product.product_location %} are deleted. + +{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %} +1. Next to the enterprise account or organization you'd like to disconnect, click **Disable {% data variables.product.prodname_github_connect %}**. +{% ifversion ghes %} + ![Disable GitHub Connect button next to an enterprise account or organization name](/assets/images/enterprise/business-accounts/disable-github-connect-button.png) +1. Read the information about disconnecting and click **Disable {% data variables.product.prodname_github_connect %}**. ![Modal with warning information about disconnecting and confirmation button](/assets/images/enterprise/business-accounts/confirm-disable-github-connect.png) +{% else %} + ![Disable GitHub Connect button next to an enterprise account or organization name](/assets/images/enterprise/github-ae/disable-github-connect-button.png) +1. Read the information about disconnecting and click **Disable {% data variables.product.prodname_github_connect %}**. ![Modal with warning information about disconnecting and confirmation button](/assets/images/enterprise/github-ae/confirm-disable-github-connect.png) +{% endif %} diff --git a/translations/ru-RU/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md b/translations/ru-RU/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md new file mode 100644 index 0000000000..833252c0fb --- /dev/null +++ b/translations/ru-RU/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md @@ -0,0 +1,97 @@ +--- +title: Enabling alerts for vulnerable dependencies on GitHub Enterprise Server +intro: 'You can connect {% data variables.product.product_location %} to {% data variables.product.prodname_ghe_cloud %} and enable the dependency graph and {% ifversion ghes %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts in repositories in your instance.' +shortTitle: Enable alerts for dependencies +miniTocMaxHeadingLevel: 3 +redirect_from: + - /enterprise/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /enterprise/admin/configuration/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /enterprise/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server +permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable the dependency graph and {% data variables.product.prodname_dependabot %} alerts on {% data variables.product.prodname_ghe_server %}.' +versions: + ghes: '*' +type: how_to +topics: + - Enterprise + - Security + - Dependency graph + - Dependabot +--- + +## About alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %} + +To identify vulnerable dependencies in your repository and receive alerts about vulnerabilities, you need to enable two security features: +- The dependency graph +- {% data variables.product.prodname_dependabot %} alerts + +For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" and "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." + +{% data reusables.repositories.tracks-vulnerabilities %} + +You can connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}, then sync vulnerability data to your instance and generate {% data variables.product.prodname_dependabot_alerts %} in repositories with a vulnerable dependency. + +After connecting {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %} and enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies, vulnerability data is synced from {% data variables.product.prodname_dotcom_the_website %} to your instance once every hour. You can also choose to manually sync vulnerability data at any time. No code or information about code from {% data variables.product.product_location %} is uploaded to {% data variables.product.prodname_dotcom_the_website %}. + +When {% data variables.product.product_location %} receives information about a vulnerability, it will identify repositories in your instance that use the affected version of the dependency and generate {% data variables.product.prodname_dependabot_alerts %}. You can customize how you receive {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies/#configuring-notifications-for-dependabot-alerts)." + +Before enabling the dependency graph and {% ifversion ghes > 2.21 %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts for vulnerable dependencies on {% data variables.product.product_location %}, you must connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." + +## Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} on GitHub Enterprise Server + +For {% data variables.product.product_location %} to generate {% data variables.product.prodname_dependabot_alerts %} whenever vulnerabilities are detected on your repositories: +- You must connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %}](/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)." +- You must enable the dependency graph. + +{% ifversion ghes > 3.1 %} +You can enable the dependency graph via the {% data variables.enterprise.management_console %} or the administrative shell. We recommend you follow the {% data variables.enterprise.management_console %} route unless {% data variables.product.product_location %} uses clustering. + +### Enabling the dependency graph via the {% data variables.enterprise.management_console %} +{% endif %}{% ifversion ghes > 3.1 %} +{% data reusables.enterprise_site_admin_settings.sign-in %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.advanced-security-tab %} +1. Under "Security," click **Dependency graph**. ![Checkbox to enable or disable the dependency graph](/assets/images/enterprise/3.2/management-console/enable-dependency-graph-checkbox.png) +{% data reusables.enterprise_management_console.save-settings %} +1. Click **Visit your instance**. + +### Enabling the dependency graph via the administrative shell +{% else %} +### Enabling the dependency graph +{% endif %} +{% data reusables.enterprise_site_admin_settings.sign-in %} +1. In the administrative shell, enable the dependency graph on {% data variables.product.product_location %}: + ``` shell + $ {% ifversion ghes > 3.1 %}ghe-config app.dependency-graph.enabled true{% else %}ghe-config app.github.dependency-graph-enabled true{% endif %} + ``` + {% note %} + + **Note**: For more information about enabling access to the administrative shell via SSH, see "[Accessing the administrative shell (SSH)](/enterprise/{{ currentVersion }}/admin/configuration/accessing-the-administrative-shell-ssh)." + + {% endnote %} +1. Apply the configuration. + ```shell + $ ghe-config-apply + ``` +1. Return to {% data variables.product.prodname_ghe_server %}. + +### Enabling {% data variables.product.prodname_dependabot_alerts %} + +Before enabling {% data variables.product.prodname_dependabot_alerts %} for your instance, you need to enable the dependency graph. For more information, see above. + +{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %} +1. Under "Repositories can be scanned for vulnerabilities", use the drop-down menu and select **Enabled without notifications**. Optionally, to enable alerts with notifications, select **Enabled with notifications**. ![Drop-down menu to enable scanning repositories for vulnerabilities](/assets/images/enterprise/site-admin-settings/enable-vulnerability-scanning-in-repositories.png) + {% note %} + + We recommend configuring {% data variables.product.prodname_dependabot_alerts %} without notifications for the first few days to avoid an overload of emails. After a few days, you can enable notifications to receive {% data variables.product.prodname_dependabot_alerts %} as usual. + + {% endnote %} +## Viewing vulnerable dependencies on {% data variables.product.prodname_ghe_server %} + +You can view all vulnerabilities in {% data variables.product.product_location %} and manually sync vulnerability data from {% data variables.product.prodname_dotcom_the_website %} to update the list. + +{% data reusables.enterprise_site_admin_settings.access-settings %} +2. In the left sidebar, click **Vulnerabilities**. ![Vulnerabilities tab in the site admin sidebar](/assets/images/enterprise/business-accounts/vulnerabilities-tab.png) +3. To sync vulnerability data, click **Sync Vulnerabilities now**. ![Sync vulnerabilities now button](/assets/images/enterprise/site-admin-settings/sync-vulnerabilities-button.png) diff --git a/translations/ru-RU/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md b/translations/ru-RU/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md new file mode 100644 index 0000000000..26eb670429 --- /dev/null +++ b/translations/ru-RU/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md @@ -0,0 +1,31 @@ +--- +title: Enabling automatic user license sync between GitHub Enterprise Server and GitHub Enterprise Cloud +intro: 'You can connect {% data variables.product.product_location_enterprise %} to {% data variables.product.prodname_ghe_cloud %} and allow {% data variables.product.prodname_ghe_server %} to upload user license information to your enterprise account on {% data variables.product.prodname_dotcom_the_website %}.' +redirect_from: + - /enterprise/admin/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud + - /enterprise/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud + - /admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud +permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable automatic user license synchronization.' +versions: + ghes: '*' +type: how_to +topics: + - Enterprise + - GitHub Connect + - Licensing +shortTitle: Enable user license sync +--- + +## About license synchronization + +After you enable license synchronization, you'll be able to view license usage for your entire enterprise account, across {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}. {% data variables.product.prodname_github_connect %} syncs license between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %} weekly. For more information, see "[Managing your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise)." + +You can also manually upload {% data variables.product.prodname_ghe_server %} user license information to {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." + +## Enabling license synchronization + +Before enabling license synchronization on {% data variables.product.product_location_enterprise %}, you must connect {% data variables.product.product_location_enterprise %} to {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." + +{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %} +1. Under "Server can sync user license count and usage", use the drop-down menu and select **Enabled**. ![Drop-down menu to enable automatic user license sync](/assets/images/enterprise/site-admin-settings/enable-user-license-drop-down.png) diff --git a/translations/ru-RU/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md b/translations/ru-RU/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md new file mode 100644 index 0000000000..6d4a2dd1b1 --- /dev/null +++ b/translations/ru-RU/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md @@ -0,0 +1,46 @@ +--- +title: Enabling unified contributions between your enterprise account and GitHub.com +shortTitle: Enable unified contributions +intro: 'After enabling {% data variables.product.prodname_github_connect %}, you can allow {% data variables.product.prodname_ghe_cloud %} members to highlight their work on {% data variables.product.product_name %} by sending the contribution counts to their {% data variables.product.prodname_dotcom_the_website %} profiles.' +redirect_from: + - /enterprise/admin/guides/developer-workflow/enabling-unified-contributions-between-github-enterprise-and-github-com/ + - /enterprise/admin/guides/developer-workflow/enabling-unified-contributions-between-github-enterprise-server-and-github-com/ + - /enterprise/admin/developer-workflow/enabling-unified-contributions-between-github-enterprise-server-and-githubcom/ + - /enterprise/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom + - /enterprise/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom + - /admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-unified-contributions-between-github-enterprise-server-and-githubcom +permissions: 'Enterprise owners who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable unified contributions between {% data variables.product.product_location %} and {% data variables.product.prodname_dotcom_the_website %}.' +versions: + ghes: '*' + ghae: next +type: how_to +topics: + - Enterprise + - GitHub Connect +--- + +{% data reusables.github-connect.beta %} + +As an enterprise owner, you can allow end users to send anonymized contribution counts for their work from {% data variables.product.product_location %} to their {% data variables.product.prodname_dotcom_the_website %} contribution graph. + +After you enable {% data variables.product.prodname_github_connect %} and enable {% data variables.product.prodname_unified_contributions %} in both environments, end users on your enterprise account can connect to their {% data variables.product.prodname_dotcom_the_website %} accounts and send contribution counts from {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.github-connect.sync-frequency %} 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)." + +If the enterprise owner disables the functionality or developers opt out of the connection, the {% data variables.product.product_name %} contribution counts will be deleted on {% data variables.product.prodname_dotcom_the_website %}. If the developer reconnects their profiles after disabling them, the contribution counts for the past 90 days are restored. + +{% data variables.product.product_name %} **only** sends the contribution count and source ({% data variables.product.product_name %}) for connected users. It does not send any information about the contribution or how it was made. + +Before enabling {% data variables.product.prodname_unified_contributions %} on {% data variables.product.product_location %}, you must connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_dotcom_the_website %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." + +{% ifversion ghes %} +{% data reusables.github-connect.access-dotcom-and-enterprise %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.business %} +{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %}{% else %} +1. Sign in to {% data variables.product.product_location %} and {% data variables.product.prodname_dotcom_the_website %}. +{% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %} +1. Under "Users can share contribution counts to {% data variables.product.prodname_dotcom_the_website %}", click **Request access**. ![Request access to unified contributions option](/assets/images/enterprise/site-admin-settings/dotcom-ghe-connection-request-access.png){% ifversion ghes %} +2. [Sign in](https://enterprise.github.com/login) to the {% data variables.product.prodname_ghe_server %} site to receive further instructions. + +When you request access, we may redirect you to the {% data variables.product.prodname_ghe_server %} site to check your current terms of service. +{% endif %} diff --git a/translations/ru-RU/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md b/translations/ru-RU/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md new file mode 100644 index 0000000000..c42a1e12e5 --- /dev/null +++ b/translations/ru-RU/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md @@ -0,0 +1,44 @@ +--- +title: Enabling unified search between your enterprise account and GitHub.com +shortTitle: Enable unified search +intro: 'After enabling {% data variables.product.prodname_github_connect %}, you can allow search of {% data variables.product.prodname_dotcom_the_website %} for members of your enterprise on {% data variables.product.product_name %}.' +redirect_from: + - /enterprise/admin/guides/developer-workflow/enabling-unified-search-between-github-enterprise-and-github-com/ + - /enterprise/admin/guides/developer-workflow/enabling-unified-search-between-github-enterprise-server-and-github-com/ + - /enterprise/admin/developer-workflow/enabling-unified-search-between-github-enterprise-server-and-githubcom/ + - /enterprise/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom + - /enterprise/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom + - /admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-unified-search-between-github-enterprise-server-and-githubcom +permissions: 'Enterprise owners who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable unified search between {% data variables.product.product_name %} and {% data variables.product.prodname_dotcom_the_website %}.' +versions: + ghes: '*' + ghae: next +topics: + - Enterprise + - GitHub Connect + - GitHub search +--- + +{% data reusables.github-connect.beta %} + +When you enable unified search, users can view search results from public and private content on {% data variables.product.prodname_dotcom_the_website %} when searching from {% data variables.product.product_location %}{% ifversion ghae %} on {% data variables.product.prodname_ghe_managed %}{% endif %}. + +Users will not be able to search {% data variables.product.product_location %} from {% data variables.product.prodname_dotcom_the_website %}, even if they have access to both environments. Users can only search private repositories you've enabled {% data variables.product.prodname_unified_search %} for and that they have access to in the connected {% data variables.product.prodname_ghe_cloud %} organizations. For more information, see "[About searching on {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github/#searching-across-github-enterprise-and-githubcom-simultaneously)" and "[Enabling private {% data variables.product.prodname_dotcom_the_website %} repository search in your enterprise account](/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment)." + +Searching via the REST and GraphQL APIs does not include {% data variables.product.prodname_dotcom_the_website %} search results. Advanced search and searching for wikis in {% data variables.product.prodname_dotcom_the_website %} are not supported. + +{% ifversion ghes %} +{% data reusables.github-connect.access-dotcom-and-enterprise %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.business %} +{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %}{% else %} +1. Sign in to {% data variables.product.product_location %} and {% data variables.product.prodname_dotcom_the_website %}. +{% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %} +1. Under "Users can search {% data variables.product.prodname_dotcom_the_website %}", use the drop-down menu and click **Enabled**. ![Enable search option in the search GitHub.com drop-down menu](/assets/images/enterprise/site-admin-settings/github-dotcom-enable-search.png) +1. Optionally, under "Users can search private repositories on {% data variables.product.prodname_dotcom_the_website %}", use the drop-down menu and click **Enabled**. ![Enable private repositories search option in the search GitHub.com drop-down menu](/assets/images/enterprise/site-admin-settings/enable-private-search.png) + +## Дополнительная литература + +- "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)" + diff --git a/translations/ru-RU/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md b/translations/ru-RU/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md new file mode 100644 index 0000000000..3da64d323b --- /dev/null +++ b/translations/ru-RU/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md @@ -0,0 +1,25 @@ +--- +title: Managing connections between your enterprise accounts +intro: 'With {% data variables.product.prodname_github_connect %}, you can share certain features and data between {% data variables.product.product_location %} and your {% data variables.product.prodname_ghe_cloud %} organization or enterprise account on {% data variables.product.prodname_dotcom_the_website %}.' +redirect_from: + - /enterprise/admin/developer-workflow/connecting-github-enterprise-to-github-com + - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-and-github-com/ + - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-server-and-github-com/ + - /enterprise/admin/developer-workflow/connecting-github-enterprise-server-and-githubcom/ + - /enterprise/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud + - /enterprise/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud +versions: + ghes: '*' + ghae: next +topics: + - Enterprise +children: + - /connecting-your-enterprise-account-to-github-enterprise-cloud + - /enabling-unified-search-between-your-enterprise-account-and-githubcom + - /enabling-unified-contributions-between-your-enterprise-account-and-githubcom + - /enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud +shortTitle: Connect enterprise accounts +--- + diff --git a/translations/ru-RU/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/ru-RU/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md index c0c411a4fe..92384abe1e 100644 --- a/translations/ru-RU/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md +++ b/translations/ru-RU/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md @@ -37,19 +37,46 @@ This article explains how site administrators can configure {% data variables.pr {% endif %} +{%- ifversion ghes < 3.2 %} + The CPU and memory resources available to {% data variables.product.product_location %} determine the maximum job throughput for {% data variables.product.prodname_actions %}. Internal testing at {% data variables.product.company_short %} demonstrated the following maximum throughput for {% data variables.product.prodname_ghe_server %} instances with a range of CPU and memory configurations. You may see different throughput depending on the overall levels of activity on your instance. +{%- endif %} + +{%- ifversion ghes > 3.1 %} + +The CPU and memory resources available to {% data variables.product.product_location %} determine the number of jobs that can be run concurrently without performance loss. + +The peak quantity of concurrent jobs running without performance loss depends on such factors as job duration, artifact usage, number of repositories running Actions, and how much other work your instance is doing not related to Actions. Internal testing at GitHub demonstrated the following performance targets for GitHub Enterprise Server on a range of CPU and memory configurations: + +{% endif %} + +{%- ifversion ghes < 3.2 %} + | vCPUs | Memory | Maximum job throughput | |:----- |:------ |:---------------------- | -| | | | -{%- ifversion ghes > 3.1 %} -| 4 | 32 GB | Demo or light testing | | 8 | 64 GB | 30 jobs | | 16 | 128 GB | 60 jobs | | 32 | 256 GB | 120 jobs | | 64 | 512 GB | 160 jobs | -{%- else ifversion ghes < 3.2 %} -| 4 | 32 GB | Demo or light testing | | 8 | 64 GB | 25 jobs | | 16 | 160 GB | 35 jobs | | 32 | 256 GB | 100 jobs | +| 4 | 32 GB | Demo or light testing | +| 8 | 64 GB | 25 jobs | +| 16 | 160 GB | 35 jobs | +| 32 | 256 GB | 100 jobs | + {%- endif %} +{%- ifversion ghes > 3.1 %} + +| vCPUs | Memory | Maximum Concurrency* | +|:----- |:------ |:-------------------- | +| 32 | 128 GB | 1500 jobs | +| 64 | 256 GB | 1900 jobs | +| 96 | 384 GB | 2200 jobs | + +*Maximum concurrency was measured using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. You may experience different performance depending on the overall levels of activity on your instance. + +{%- endif %} + + If you {% ifversion ghes = 2.22 %}enabled the beta of{% else %}plan to enable{% endif %} {% data variables.product.prodname_actions %} for the users of an existing instance, review the levels of activity for users and automations on the instance and ensure that you have provisioned adequate CPU and memory for your users. For more information about monitoring the capacity and performance of {% data variables.product.prodname_ghe_server %}, see "[Monitoring your appliance](/admin/enterprise-management/monitoring-your-appliance)." For more information about minimum hardware requirements for {% data variables.product.product_location %}, see the hardware considerations for your instance's platform. diff --git a/translations/ru-RU/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md b/translations/ru-RU/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md index b527e6f084..812c378557 100644 --- a/translations/ru-RU/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md +++ b/translations/ru-RU/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md @@ -10,7 +10,6 @@ children: - /enabling-github-actions-with-azure-blob-storage - /enabling-github-actions-with-amazon-s3-storage - /enabling-github-actions-with-minio-gateway-for-nas-storage - - /enforcing-github-actions-policies-for-your-enterprise shortTitle: Enable GitHub Actions --- diff --git a/translations/ru-RU/content/admin/github-actions/index.md b/translations/ru-RU/content/admin/github-actions/index.md index fe0779539f..d0fb8bafcd 100644 --- a/translations/ru-RU/content/admin/github-actions/index.md +++ b/translations/ru-RU/content/admin/github-actions/index.md @@ -16,6 +16,5 @@ children: shortTitle: Manage GitHub Actions --- -{% data reusables.actions.ae-beta %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} diff --git a/translations/ru-RU/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md b/translations/ru-RU/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md index 42282a53e2..8b661db885 100644 --- a/translations/ru-RU/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md +++ b/translations/ru-RU/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md @@ -18,7 +18,6 @@ shortTitle: Add actions in your enterprise {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data variables.product.prodname_actions %} workflows can use _actions_, which are individual tasks that you can combine to create jobs and customize your workflow. You can create your own actions, or use and customize actions shared by the {% data variables.product.prodname_dotcom %} community. diff --git a/translations/ru-RU/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md b/translations/ru-RU/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md index 831d376076..a8ef49b657 100644 --- a/translations/ru-RU/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md +++ b/translations/ru-RU/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md @@ -19,7 +19,6 @@ shortTitle: Use GitHub Connect for actions {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.actions.enterprise-github-connect-warning %} -{% data reusables.actions.ae-beta %} By default, {% data variables.product.prodname_actions %} workflows on {% data variables.product.product_name %} cannot use actions directly from {% data variables.product.prodname_dotcom_the_website %} or [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions). @@ -27,8 +26,16 @@ To make all actions from {% data variables.product.prodname_dotcom_the_website % ## Enabling automatic access to all {% data variables.product.prodname_dotcom_the_website %} actions -Before enabling access to all actions from {% data variables.product.prodname_dotcom_the_website %} on your enterprise instance, you must connect your enterprise to {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %}](/enterprise/{{ currentVersion }}/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)." +Before enabling access to all actions from {% data variables.product.prodname_dotcom_the_website %} on your enterprise instance, you must connect your enterprise to {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Connecting your enterprise to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." -{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %} +{% data reusables.enterprise-accounts.access-enterprise %} +{%- ifversion ghes < 3.1 %} +{% data reusables.enterprise-accounts.settings-tab %} +{%- endif %} +{% data reusables.enterprise-accounts.github-connect-tab %} +{%- ifversion ghes > 3.0 or ghae %} +1. Under "Users can utilize actions from GitHub.com in workflow runs", use the drop-down menu and select **Enabled**. ![Drop-down menu to actions from GitHub.com in workflows runs](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down-ae.png) +{%- else %} 1. Under "Server can use actions from GitHub.com in workflows runs", use the drop-down menu and select **Enabled**. ![Drop-down menu to actions from GitHub.com in workflows runs](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down.png) +{%- endif %} 1. {% data reusables.actions.enterprise-limit-actions-use %} diff --git a/translations/ru-RU/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md b/translations/ru-RU/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md index 585f4adc7c..f24e7f028b 100644 --- a/translations/ru-RU/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md +++ b/translations/ru-RU/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md @@ -14,13 +14,14 @@ shortTitle: Manually sync actions {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.actions.enterprise-no-internet-actions %} -The recommended approach of enabling access to actions from {% data variables.product.prodname_dotcom_the_website %} is to enable automatic access to all actions. You can do this by using {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.product_name %} with {% data variables.product.prodname_ghe_cloud %} . For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". +{% ifversion ghes or ghae-next %} -However, if you want stricter control over which actions are allowed in your enterprise, you can follow this guide to use {% data variables.product.company_short %}'s open source [`actions-sync`](https://github.com/actions/actions-sync) tool to sync individual action repositories from {% data variables.product.prodname_dotcom_the_website %} to your enterprise. +The recommended approach of enabling access to actions from {% data variables.product.prodname_dotcom_the_website %} is to enable automatic access to all actions. You can do this by using {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.product_name %} with {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)." + +However, if you want stricter control over which actions are allowed in your enterprise, you{% else %}You{% endif %} can follow this guide to use {% data variables.product.company_short %}'s open source [`actions-sync`](https://github.com/actions/actions-sync) tool to sync individual action repositories from {% data variables.product.prodname_dotcom_the_website %} to your enterprise. ## About the `actions-sync` tool @@ -33,7 +34,7 @@ The `actions-sync` tool can only download actions from {% data variables.product ## Требования * Before using the `actions-sync` tool, you must ensure that all destination organizations already exist in your enterprise. The following example demonstrates how to sync actions to an organization named `synced-actions`. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." -* You must create a personal access token (PAT) on your enterprise that can create and write to repositories in the destination organizations. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." +* You must create a personal access token (PAT) on your enterprise that can create and write to repositories in the destination organizations. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."{% ifversion ghes %} * If you want to sync the bundled actions in the `actions` organization on {% data variables.product.product_location %}, you must be an owner of the `actions` organization. {% note %} @@ -46,7 +47,7 @@ The `actions-sync` tool can only download actions from {% data variables.product ```shell ghe-org-admin-promote -u USERNAME -o actions - ``` + ```{% endif %} ## Example: Using the `actions-sync` tool diff --git a/translations/ru-RU/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md b/translations/ru-RU/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md index 3c47b6781a..c468b08571 100644 --- a/translations/ru-RU/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md +++ b/translations/ru-RU/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md @@ -14,7 +14,6 @@ shortTitle: Tool cache for offline runners {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About the included setup actions and the runner tool cache diff --git a/translations/ru-RU/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md b/translations/ru-RU/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md index c22602048c..668cbc3bc3 100644 --- a/translations/ru-RU/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md +++ b/translations/ru-RU/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md @@ -13,7 +13,6 @@ shortTitle: Use the latest bundled actions {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} Your enterprise instance includes a number of built-in actions that you can use in your workflows. For more information about the bundled actions, see "[Official actions bundled with your enterprise instance](/admin/github-actions/about-using-actions-in-your-enterprise#official-actions-bundled-with-your-enterprise-instance)." @@ -29,17 +28,13 @@ You can use {% data variables.product.prodname_github_connect %} to allow {% dat Once {% data variables.product.prodname_github_connect %} is configured, you can use the latest version of an action by deleting its local repository in the `actions` organization on your instance. For example, if your enterprise instance is using the `actions/checkout@v1` action, and you need to use `actions/checkout@v2` which isn't available on your enterprise instance, perform the following steps to be able to use the latest `checkout` action from {% data variables.product.prodname_dotcom_the_website %}: -1. By default, site administrators are not owners of the bundled actions organization. To get the required access to delete the `checkout` repository, use the `ghe-org-admin-promote` command to promote a user to be an owner of the bundled `actions` organization. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" and "[`ghe-org-admin-promote`](/admin/configuration/command-line-utilities#ghe-org-admin-promote)." Например: - - ```shell - $ ghe-org-admin-promote -u octocat -o actions - Do you want to give organization admin privileges for actions to octocat? (y/N) y - Making octocat an admin of actions - --> Adding octocat as an admin of actions - --> octocat is now an admin of the actions organization - --> Done. - ``` -1. On your {% data variables.product.product_name %} instance, delete the `checkout` repository within the `actions` organization. For information on how to delete a repository, see "[Deleting a repository ](/github/administering-a-repository/deleting-a-repository)." -1. It is recommended that you leave the `actions` organization once you no longer require administrative access. For more information, see "[Removing yourself from an organization ](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization)." +1. From an enterprise owner account on {% data variables.product.product_name %}, navigate to the repository you want to delete from the *actions* organization (in this example `checkout`). +1. By default, site administrators are not owners of the bundled *actions* organization. To get the access required to delete the `checkout` repository, you must use the site admin tools. Click {% octicon "rocket" aria-label="The rocket ship" %} in the upper-right corner of any page in that repository. ![Rocketship icon for accessing site admin settings](/assets/images/enterprise/site-admin-settings/access-new-settings.png) +1. Click {% octicon "shield-lock" %} **Security** to see the security overview for the repository. ![Security header the repository](/assets/images/enterprise/site-admin-settings/access-repo-security-info.png) +1. Under "Privileged access", click **Unlock**. ![Unlock button](/assets/images/enterprise/site-admin-settings/unlock-priviledged-repo-access.png) +1. Under **Reason**, type a reason for unlocking the repository, then click **Unlock**. ![Confirmation dialog](/assets/images/enterprise/site-admin-settings/confirm-unlock-repo-access.png) +1. Now that the repository is unlocked, you can leave the site admin pages and delete the repository within the `actions` organization. At the top of the page, click the repository name, in this example **checkout**, to return to the summary page. ![Repository name link](/assets/images/enterprise/site-admin-settings/display-repository-admin-summary.png) +1. Under "Repository info", click **View code** to leave the site admin pages and display the `checkout` repository. +1. Delete the `checkout` repository within the `actions` organization. For information on how to delete a repository, see "[Deleting a repository](/github/administering-a-repository/deleting-a-repository)." ![View code link](/assets/images/enterprise/site-admin-settings/exit-admin-page-for-repository.png) 1. Configure your workflow's YAML to use `actions/checkout@v2`. 1. Each time your workflow runs, the runner will use the `v2` version of `actions/checkout` from {% data variables.product.prodname_dotcom_the_website %}. diff --git a/translations/ru-RU/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md b/translations/ru-RU/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md index 5337563413..e0bb78239d 100644 --- a/translations/ru-RU/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md +++ b/translations/ru-RU/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md @@ -13,7 +13,6 @@ redirect_from: - /admin/github-actions/getting-started-with-github-actions-for-github-ae --- -{% data reusables.actions.ae-beta %} This article explains how site administrators can configure {% data variables.product.prodname_ghe_managed %} to use {% data variables.product.prodname_actions %}. diff --git a/translations/ru-RU/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md b/translations/ru-RU/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md index 6a995ba974..9049ffa719 100644 --- a/translations/ru-RU/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md +++ b/translations/ru-RU/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md @@ -8,7 +8,6 @@ redirect_from: shortTitle: Use actions --- -{% data reusables.actions.ae-beta %} {% data variables.product.prodname_actions %} workflows can use _actions_, which are individual tasks that you can combine to create jobs and customize your workflow. You can create your own actions, or use and customize actions shared by the {% data variables.product.prodname_dotcom %} community. diff --git a/translations/ru-RU/content/admin/guides.md b/translations/ru-RU/content/admin/guides.md index e1921b7e12..93ad13c2b9 100644 --- a/translations/ru-RU/content/admin/guides.md +++ b/translations/ru-RU/content/admin/guides.md @@ -35,13 +35,13 @@ includeGuides: - /admin/configuration/configuring-rate-limits - /admin/configuration/configuring-secret-scanning-for-your-appliance - /admin/configuration/configuring-tls - - /admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud + - /admin/configuration/connecting-your-enterprise-account-to-github-enterprise-cloud - /admin/configuration/enabling-and-scheduling-maintenance-mode - /admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud - /admin/configuration/enabling-private-mode - /admin/configuration/enabling-subdomain-isolation - - /admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom - - /admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom + - /admin/configuration/enabling-unified-contributions-between-your-enterprise-account-and-githubcom + - /admin/configuration/enabling-unified-search-between-your-enterprise-account-and-githubcom - /admin/configuration/initializing-github-ae - /admin/configuration/managing-github-for-mobile-for-your-enterprise - /admin/configuration/network-ports diff --git a/translations/ru-RU/content/admin/overview/about-upgrades-to-new-releases.md b/translations/ru-RU/content/admin/overview/about-upgrades-to-new-releases.md index 50a70af40f..cc1e9cd9b6 100644 --- a/translations/ru-RU/content/admin/overview/about-upgrades-to-new-releases.md +++ b/translations/ru-RU/content/admin/overview/about-upgrades-to-new-releases.md @@ -13,7 +13,7 @@ topics: {% data variables.product.product_name %} is constantly improving, with new functionality and bug fixes introduced through major and minor releases. {% ifversion ghae %}{% data variables.product.prodname_ghe_managed %} is a fully managed service, so {% data variables.product.company_short %} completes the upgrade process for your enterprise.{% endif %} -Major releases include new functionality and feature upgrades and typically occur {% ifversion ghae %}every few weeks or months{% else %} quarterly{% endif %}. {% ifversion ghae %}{% data variables.product.company_short %} will upgrade your enterprise to the latest major release. You will be given advance notice of any planned downtime for your enterprise.{% endif %} +Major releases include new functionality and feature upgrades and typically occur quarterly. {% ifversion ghae %}{% data variables.product.company_short %} will upgrade your enterprise to the latest major release. You will be given advance notice of any planned downtime for your enterprise.{% endif %} {% ifversion ghes %} @@ -43,7 +43,6 @@ To upgrade your enterprise to a new release, see "[Release notes](/enterprise-se ## Дополнительная литература -- [ {% data variables.product.prodname_roadmap %} ]({% data variables.product.prodname_roadmap_link %}) in the `github/roadmap` repository -{% ifversion ghae %} +- [ {% data variables.product.prodname_roadmap %} ]({% data variables.product.prodname_roadmap_link %}) in the `github/roadmap` repository{% ifversion ghae %} - [ {% data variables.product.prodname_ghe_managed %} release notes](/admin/release-notes) {% endif %} diff --git a/translations/ru-RU/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise.md b/translations/ru-RU/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise.md new file mode 100644 index 0000000000..6975629cf9 --- /dev/null +++ b/translations/ru-RU/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise.md @@ -0,0 +1,59 @@ +--- +title: Enforcing GitHub Actions policies for your enterprise +intro: 'Enterprise administrators can manage access to {% data variables.product.prodname_actions %} in an enterprise.' +redirect_from: + - /enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise + - /admin/github-actions/enforcing-github-actions-policies-for-your-enterprise + - /admin/github-actions/enabling-github-actions-for-github-enterprise-server/enforcing-github-actions-policies-for-your-enterprise +versions: + ghes: '*' + ghae: '*' +type: how_to +topics: + - Actions + - Enterprise + - Policies +shortTitle: GitHub Actions policies +--- + +{% data reusables.actions.enterprise-beta %} + +## About {% data variables.product.prodname_actions %} permissions for your enterprise + +{% ifversion ghae %}{% else %}When you enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}, it is enabled for all organizations in your enterprise. {% endif %}You can choose to disable {% data variables.product.prodname_actions %} for all organizations in your enterprise, or only allow specific organizations. You can also limit the use of public actions, so that people can only use local actions that exist in your enterprise. + +## Managing {% data variables.product.prodname_actions %} permissions for your enterprise + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.actions-tab %} +{% data reusables.actions.enterprise-actions-permissions %} + +{% ifversion ghes > 2.22 or ghae %} +## Allowing specific actions to run + +{% data reusables.actions.allow-specific-actions-intro %} + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.actions-tab %} +1. Under **Policies**, select **Allow select actions** and add your required actions to the list. + {%- ifversion ghes or ghae-issue-5094 %} + ![Add actions to allow list](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png) + {%- elsif ghae %} + ![Add actions to allow list](/assets/images/enterprise/github-ae/enterprise-actions-policy-allow-list.png) + {%- endif %} +{% endif %} + +{% ifversion ghes > 2.22 or ghae %} +## Enabling workflows for private repository forks + +{% data reusables.github-actions.private-repository-forks-overview %} + +### Configuring the private fork policy for your enterprise + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.actions-tab %} +{% data reusables.github-actions.private-repository-forks-configure %} +{% endif %} diff --git a/translations/ru-RU/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md b/translations/ru-RU/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md index b3b2b33e67..968c06b782 100644 --- a/translations/ru-RU/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md +++ b/translations/ru-RU/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md @@ -34,7 +34,7 @@ topics: - Enterprise - Policies - Security -shortTitle: Enforce repository policies +shortTitle: Repository management policies --- ## Configuring the default visibility of new repositories in your enterprise diff --git a/translations/ru-RU/content/admin/policies/enforcing-policies-for-your-enterprise/index.md b/translations/ru-RU/content/admin/policies/enforcing-policies-for-your-enterprise/index.md index 73c67d0923..f4cdf81f00 100644 --- a/translations/ru-RU/content/admin/policies/enforcing-policies-for-your-enterprise/index.md +++ b/translations/ru-RU/content/admin/policies/enforcing-policies-for-your-enterprise/index.md @@ -11,6 +11,7 @@ topics: children: - /enforcing-repository-management-policies-in-your-enterprise - /restricting-email-notifications-for-your-enterprise + - /enforcing-github-actions-policies-for-your-enterprise - /enforcing-policies-for-advanced-security-in-your-enterprise shortTitle: Enforce policies --- diff --git a/translations/ru-RU/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md b/translations/ru-RU/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md index 1ae0f75084..6a6ad1f82d 100644 --- a/translations/ru-RU/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md +++ b/translations/ru-RU/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md @@ -30,6 +30,9 @@ If you can't access {% data variables.product.product_name %}, contact your loca {% data reusables.saml.dotcom-saml-explanation %} Organization owners can invite your user account on {% data variables.product.prodname_dotcom %} to join their organization that uses SAML SSO, which allows you to contribute to the organization and retain your existing identity and contributions on {% data variables.product.prodname_dotcom %}. +If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you will use a new account that is provisioned for you. {% data reusables.enterprise-accounts.emu-more-info-account %} + + When you access resources within an organization that uses SAML SSO, {% data variables.product.prodname_dotcom %} will redirect you to the organization's SAML IdP to authenticate. After you successfully authenticate with your account on the IdP, the IdP redirects you back to {% data variables.product.prodname_dotcom %}, where you can access the organization's resources. {% data reusables.saml.outside-collaborators-exemption %} diff --git a/translations/ru-RU/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md b/translations/ru-RU/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md index 5a03e8d800..94f40ab598 100644 --- a/translations/ru-RU/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md +++ b/translations/ru-RU/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md @@ -20,7 +20,7 @@ shortTitle: Generate new SSH key If you don't already have an SSH key, you must generate a new SSH key to use for authentication. If you're unsure whether you already have an SSH key, you can check for existing keys. For more information, see "[Checking for existing SSH keys](/github/authenticating-to-github/checking-for-existing-ssh-keys)." -{% ifversion fpt %} +{% ifversion fpt or ghae-next or ghes > 3.1 %} If you want to use a hardware security key to authenticate to {% data variables.product.product_name %}, you must generate a new SSH key for your hardware security key. You must connect your hardware security key to your computer when you authenticate with the key pair. For more information, see the [OpenSSH 8.2 release notes](https://www.openssh.com/txt/release-8.2). @@ -31,6 +31,12 @@ If you don't want to reenter your passphrase every time you use your SSH key, yo {% data reusables.command_line.open_the_multi_os_terminal %} 2. Paste the text below, substituting in your {% data variables.product.product_name %} email address. + {% ifversion ghae %} + + ```shell + $ ssh-keygen -t rsa -b 4096 -C "your_email@example.com" + ``` + {% else %} ```shell $ ssh-keygen -t ed25519 -C "your_email@example.com" ``` @@ -38,20 +44,22 @@ If you don't want to reenter your passphrase every time you use your SSH key, yo **Note:** If you are using a legacy system that doesn't support the Ed25519 algorithm, use: ```shell - $ ssh-keygen -t rsa -b 4096 -C "your_email@example.com" + $ ssh-keygen -t rsa -b 4096 -C "your_email@example.com" ``` {% endnote %} + {% endif %} + This creates a new SSH key, using the provided email as a label. ```shell - > Generating public/private ed25519 key pair. + > Generating public/private algorithm key pair. ``` 3. When you're prompted to "Enter a file in which to save the key," press Enter. This accepts the default file location. {% mac %} ```shell - > Enter a file in which to save the key (/Users/you/.ssh/id_ed25519): [Press enter] + > Enter a file in which to save the key (/Users/you/.ssh/id_algorithm): [Press enter] ``` {% endmac %} @@ -59,7 +67,7 @@ If you don't want to reenter your passphrase every time you use your SSH key, yo {% windows %} ```shell - > Enter a file in which to save the key (/c/Users/you/.ssh/id_ed25519):[Press enter] + > Enter a file in which to save the key (/c/Users/you/.ssh/id_algorithm):[Press enter] ``` {% endwindows %} @@ -67,7 +75,7 @@ If you don't want to reenter your passphrase every time you use your SSH key, yo {% linux %} ```shell - > Enter a file in which to save the key (/home/you/.ssh/id_ed25519): [Press enter] + > Enter a file in which to save the key (/home/you/.ssh/algorithm): [Press enter] ``` {% endlinux %} @@ -107,7 +115,7 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav Host * AddKeysToAgent yes UseKeychain yes - IdentityFile ~/.ssh/id_ed25519 + IdentityFile ~/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %} ``` {% note %} @@ -137,7 +145,7 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav 3. Add your SSH private key to the ssh-agent and store your passphrase in the keychain. {% data reusables.ssh.add-ssh-key-to-ssh-agent %} ```shell - $ ssh-add -K ~/.ssh/id_ed25519 + $ ssh-add -K ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %} ``` {% note %} @@ -189,8 +197,10 @@ If you are using macOS or Linux, you may need to update your SSH client or insta {% data reusables.command_line.open_the_multi_os_terminal %} 3. Paste the text below, substituting in the email address for your account on {% data variables.product.product_name %}. ```shell - $ ssh-keygen -t ed25519-sk -C "your_email@example.com" + $ ssh-keygen -t {% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}-sk -C "your_email@example.com" ``` + + {% ifversion not ghae %} {% note %} **Note:** If the command fails and you receive the error `invalid format` or `feature not supported,` you may be using a hardware security key that does not support the Ed25519 algorithm. Enter the following command instead. @@ -199,13 +209,14 @@ If you are using macOS or Linux, you may need to update your SSH client or insta ``` {% endnote %} + {% endif %} 4. When you are prompted, touch the button on your hardware security key. 5. When you are prompted to "Enter a file in which to save the key," press Enter to accept the default file location. {% mac %} ```shell - > Enter a file in which to save the key (/Users/you/.ssh/id_ed25519_sk): [Press enter] + > Enter a file in which to save the key (/Users/you/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): [Press enter] ``` {% endmac %} @@ -213,7 +224,7 @@ If you are using macOS or Linux, you may need to update your SSH client or insta {% windows %} ```shell - > Enter a file in which to save the key (/c/Users/you/.ssh/id_ed25519_sk):[Press enter] + > Enter a file in which to save the key (/c/Users/you/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk):[Press enter] ``` {% endwindows %} @@ -221,7 +232,7 @@ If you are using macOS or Linux, you may need to update your SSH client or insta {% linux %} ```shell - > Enter a file in which to save the key (/home/you/.ssh/id_ed25519_sk): [Press enter] + > Enter a file in which to save the key (/home/you/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): [Press enter] ``` {% endlinux %} diff --git a/translations/ru-RU/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md b/translations/ru-RU/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md index fd63e01143..d24691dea0 100644 --- a/translations/ru-RU/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md +++ b/translations/ru-RU/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md @@ -28,6 +28,10 @@ You can access your resources in {% data variables.product.product_name %} in a 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 fpt %} +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](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users#authenticating-as-a-managed-user)". If you're not a member of an {% data variables.product.prodname_emu_enterprise %}, you will authenticate using your browser on {% data variables.product.prodname_dotcom_the_website %}. +{% endif %} + - **Username and password only** - You'll create a password when you create your user 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)." - **Two-factor authentication (2FA)** (recommended) diff --git a/translations/ru-RU/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md b/translations/ru-RU/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md index 19e126d754..1714b1c969 100644 --- a/translations/ru-RU/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md +++ b/translations/ru-RU/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md @@ -38,7 +38,7 @@ A token with no assigned scopes can only access public information. To use your {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.developer_settings %} {% data reusables.user_settings.personal_access_tokens %} -4. Click **Generate new token**. ![Generate new token button](/assets/images/help/settings/generate_new_token.png) +{% 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 %} 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**. diff --git a/translations/ru-RU/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md b/translations/ru-RU/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md index daed4bc6b3..eea3d1d405 100644 --- a/translations/ru-RU/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md +++ b/translations/ru-RU/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md @@ -75,33 +75,6 @@ You can use a fallback number regardless of whether you've configured authentica After setup, the backup device will receive a confirmation SMS. -## Adding a fallback authentication method with Recover Accounts Elsewhere - -You can generate an extra authentication credential for your account and store it with a partner recovery provider. - -### About Recover Accounts Elsewhere - -With Recover Accounts Elsewhere, you can add an extra security factor to your {% data variables.product.product_name %} account in case you lose access to your two-factor authentication method or recovery codes. - -Recover Accounts Elsewhere lets you associate your {% data variables.product.product_name %} account with your Facebook account. You can store an authentication credential in the form of an _account recovery token_ for your {% data variables.product.product_name %} account with Facebook. - -If you lose access to your {% data variables.product.product_name %} account because you no longer have access to your two-factor authentication method or recovery codes, you can retrieve your account recovery token from the recovery provider to help prove that you're the owner of your {% data variables.product.product_name %} account. - -After you retrieve your token, {% data variables.contact.contact_support %} may be able to disable two-factor authentication for your account. Then, you can provide or reset your password to regain access to your account. - -When you generate or retrieve an account recovery token, an event is added to your account's audit log. For more information, see "[Reviewing your security log](/articles/reviewing-your-security-log)." - -### Generating and storing an account recovery token - -You can generate an account recovery token and store it with a partner recovery provider. - -1. Sign in to your Facebook account, then return to {% data variables.product.product_name %}. -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.security %} -4. To generate a new token, under "Recovery tokens," click **Store new token**. ![Button for storing a new recovery token](/assets/images/help/settings/store-new-recovery-token.png) -5. Read the information about account recovery tokens, then click **Connect with https://www.facebook.com**. ![Button for connecting a recovery token with Facebook](/assets/images/help/settings/connect-recovery-token-with-facebook.png) -6. After you're redirected to Facebook, read the information about turning on account recovery with Facebook before you click **Save as [_YOUR NAME_]**. (If you save multiple tokens within a short period of time, Facebook may skip this confirmation step after you save your first token.) ![Facebook page with button for turning on account recovery](/assets/images/help/settings/security-turn-on-rae-facebook.png) - {% endif %} ## Дополнительная литература diff --git a/translations/ru-RU/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md b/translations/ru-RU/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md index 789895f2fd..4e2f6ae306 100644 --- a/translations/ru-RU/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md +++ b/translations/ru-RU/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md @@ -28,6 +28,12 @@ We strongly recommend using a time-based one-time password (TOTP) application to {% endwarning %} +{% ifversion fpt %} + +If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you cannot configure 2FA for your {% data variables.product.prodname_managed_user %} account. 2FA should be configured through your identity provider. + +{% endif %} + ## Configuring two-factor authentication using a TOTP mobile app A time-based one-time password (TOTP) application automatically generates an authentication code that changes after a certain period of time. We recommend using cloud-based TOTP apps such as: diff --git a/translations/ru-RU/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md b/translations/ru-RU/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md index 39aac27070..0db9ef4ccd 100644 --- a/translations/ru-RU/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md +++ b/translations/ru-RU/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md @@ -71,6 +71,12 @@ You can use your two-factor authentication credentials or two-factor authenticat ## Authenticating with an account recovery token +{% warning %} + +**Warning:** Account recovery tokens are deprecated and will be disabled on **December 1st, 2021**. Please ensure you have configured other two-factor recovery methods. For more information, see "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)." + +{% endwarning %} + If you lose access to the two-factor authentication methods for your {% data variables.product.product_name %} account, you can retrieve your account recovery token from a partner recovery provider and ask {% data variables.product.prodname_dotcom %} Support to review it. If you don't have access to your two-factor authentication methods or recovery codes and you've stored an account recovery token with Facebook using Recover Accounts Elsewhere, you may be able to use your token to regain access to your account. diff --git a/translations/ru-RU/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md b/translations/ru-RU/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md index cdccde5c9a..cc0cade7fd 100644 --- a/translations/ru-RU/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md +++ b/translations/ru-RU/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md @@ -68,6 +68,8 @@ The number of jobs you can run concurrently across all repositories in your user ## Calculating minute and storage spending +{% data reusables.dotcom_billing.pricing_cal %} + At the end of the month, {% data variables.product.prodname_dotcom %} calculates the cost of minutes and storage used over the amount included in your account. ### Sample minutes cost calculation diff --git a/translations/ru-RU/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md b/translations/ru-RU/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md index a256b5296d..24606df3e9 100644 --- a/translations/ru-RU/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md +++ b/translations/ru-RU/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md @@ -28,6 +28,8 @@ Your {% data variables.product.prodname_codespaces %} usage shares your account' 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 {% data variables.product.prodname_codespaces %} usage. For more information, see "[Connecting an Azure subscription to your enterprise](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)." +{% data reusables.dotcom_billing.pricing_cal %} + ## Setting a spending limit {% data reusables.codespaces.codespaces-spending-limit-requirement %} diff --git a/translations/ru-RU/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md b/translations/ru-RU/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md index 9a3d1b42a1..4256ebae5b 100644 --- a/translations/ru-RU/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md +++ b/translations/ru-RU/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md @@ -49,7 +49,7 @@ Storage usage is shared with build artifacts produced by {% data variables.produ {% 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. -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.25 USD per GB or $37 USD. The overage for data transfer would cost $0.50 USD per GB or $20 USD. {% data reusables.dotcom_billing.pricing_cal %} At the end of the month, {% data variables.product.prodname_dotcom %} rounds your data transfer to the nearest GB. diff --git a/translations/ru-RU/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md b/translations/ru-RU/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md index 7441223f4a..09fee3bc77 100644 --- a/translations/ru-RU/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md +++ b/translations/ru-RU/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md @@ -68,11 +68,9 @@ 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)." -{% note %} - -**Note**: If you want {% data variables.product.prodname_code_scanning %} alerts to appear as pull request checks, you must use the `pull_request` event, described below. - -{% endnote %} +{% ifversion fpt or ghes > 3.2 or ghae-issue-5093 %} +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 %} ### Scanning pull requests @@ -82,6 +80,10 @@ For more information about the `pull_request` event, see "[Workflow syntax for { 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 %} + 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 %} + {% ifversion fpt or ghes > 3.1 or ghae-next %} ### Defining the severities causing pull request check failure @@ -234,7 +236,6 @@ Alternatively, you can install Python dependencies manually on any operating sys ```yaml jobs: CodeQL-Build: - runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae-next %} permissions: security-events: write @@ -266,7 +267,7 @@ jobs: ``` {% endif %} -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ## Configuring a category for the analysis Use `category` to distinguish between multiple analyses for the same tool and commit, but performed on different languages or different parts of the code. The category you specify in your workflow will be included in the SARIF results file. diff --git a/translations/ru-RU/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md b/translations/ru-RU/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md index 6277ea9912..5cf69a3aa1 100644 --- a/translations/ru-RU/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/ru-RU/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md @@ -48,9 +48,9 @@ When {% data variables.product.prodname_code_scanning %} reports data-flow alert Alert severity levels may be `Error`, `Warning`, or `Note`. -By default, any code scanning results with a severity of `error` will cause check failure. {% ifversion fpt or ghes > 3.1 or ghae-next %}You can specify the severity level at which pull requests that trigger code scanning alerts should fail. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %} +By default, any code scanning results with a severity of `error` will cause check failure. {% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %}You can specify the severity level at which pull requests that trigger code scanning alerts should fail. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %} +{% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %} ### About security severity levels {% data variables.product.prodname_code_scanning_capc %} displays security severity levels for alerts that are generated by security queries. Security severity levels can be `Critical`, `High`, `Medium`, or `Low`. @@ -70,10 +70,10 @@ By default, the code scanning alerts page is filtered to show alerts for the def {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-code-scanning-alerts %} -{% ifversion fpt or ghes > 3.1 %} -1. Optionally, use{% ifversion fpt or ghes > 3.1 %} the free text search box or{% endif %} the drop-down menus to filter alerts. For example, you can filter by the tool that was used to identify alerts. ![Filter by tool](/assets/images/help/repository/code-scanning-filter-by-tool.png){% endif %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} +1. Optionally, use the free text search box or the drop-down menus to filter alerts. For example, you can filter by the tool that was used to identify alerts. ![Filter by tool](/assets/images/help/repository/code-scanning-filter-by-tool.png){% endif %} 1. Under "{% data variables.product.prodname_code_scanning_capc %}," click the alert you'd like to explore. -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ![Summary of alerts](/assets/images/help/repository/code-scanning-click-alert.png) {% else %} ![List of alerts from {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) @@ -81,7 +81,7 @@ By default, the code scanning alerts page is filtered to show alerts for the def 1. Optionally, if the alert highlights a problem with data flow, click **Show paths** to display the path from the data source to the sink where it's used. ![The "Show paths" link on an alert](/assets/images/help/repository/code-scanning-show-paths.png) 1. Alerts from {% data variables.product.prodname_codeql %} analysis include a description of the problem. Click **Show more** for guidance on how to fix your code. ![Details for an alert](/assets/images/help/repository/code-scanning-alert-details.png) -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} {% note %} **Note:** For {% data variables.product.prodname_code_scanning %} analysis with {% data variables.product.prodname_codeql %}, you can see information about the latest run in a header at the top of the list of {% data variables.product.prodname_code_scanning %} alerts for the repository. @@ -91,7 +91,6 @@ For example, you can see when the last scan ran, the number of lines of code ana {% endnote %} {% endif %} - ## Filtering {% data variables.product.prodname_code_scanning %} alerts You can filter the alerts shown in the {% data variables.product.prodname_code_scanning %} alerts view. This is useful if there are many alerts as you can focus on a particular type of alert. There are some predefined filters and a range of keywords that you can use to refine the list of alerts displayed. @@ -105,7 +104,21 @@ You can filter the alerts shown in the {% data variables.product.prodname_code_s The benefit of using keyword filters is that only values with results are shown in the drop-down lists. This makes it easy to avoid setting filters that find no results. +If you enter multiple filters, the view will show alerts matching _all_ these filters. For example, `is:closed severity:high branch:main` will only display closed high-severity alerts that are present on the `main` branch. The exception is filters relating to refs (`ref`, `branch` and `pr`): `is:open branch:main branch:next` will show you open alerts from both the `main` branch and the `next` branch. + +### Restricting results to application code only + +You can use the "Only alerts in application code" filter or `autofilter:true` keyword and value to restrict results to alerts in application code. Application code excludes the following. + +- Code generated by the build process +- Test code +- Library or third-party code +- Документация + +{% data variables.product.prodname_code_scanning_capc %} categorizes files by file path. At this time, you cannot manually categorize source files. + {% ifversion fpt or ghes > 3.1 %} + ## Searching {% data variables.product.prodname_code_scanning %} alerts You can search the list of alerts. This is useful if there is a large number of alerts in your repository, or if you don't know the exact name for an alert for example. {% data variables.product.product_name %} performs the free text search across: @@ -145,11 +158,11 @@ Anyone with write permission for a repository can fix an alert by committing a c If you have write permission for a repository, you can view fixed alerts by viewing the summary of alerts and clicking **Closed**. For more information, see "[Viewing the alerts for a repository](#viewing-the-alerts-for-a-repository)." The "Closed" list shows fixed alerts and alerts that users have dismissed. -You can use{% ifversion fpt or ghes > 3.1 %} the free text search or{% endif %} the filters to display a subset of alerts and then in turn mark all matching alerts as closed. +You can use{% ifversion fpt or ghes > 3.1 or ghae-next %} the free text search or{% endif %} the filters to display a subset of alerts and then in turn mark all matching alerts as closed. Alerts may be fixed in one branch but not in another. You can use the "Branch" drop-down menu, on the summary of alerts, to check whether an alert is fixed in a particular branch. -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ![Filtering alerts by branch](/assets/images/help/repository/code-scanning-branch-filter.png) {% else %} ![Filtering alerts by branch](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png) @@ -185,9 +198,9 @@ To dismiss or delete alerts: ![Deleting alerts](/assets/images/help/repository/code-scanning-delete-alerts.png) - Optionally, you can use{% ifversion fpt or ghes > 3.1 %} the free text search or{% endif %} the filters to display a subset of alerts and then delete all matching alerts at once. For example, if you have removed a query from {% data variables.product.prodname_codeql %} analysis, you can use the "Rule" filter to list just the alerts for that query and then select and delete all of those alerts. + Optionally, you can use{% ifversion fpt or ghes > 3.1 or ghae-next %} the free text search or{% endif %} the filters to display a subset of alerts and then delete all matching alerts at once. For example, if you have removed a query from {% data variables.product.prodname_codeql %} analysis, you can use the "Rule" filter to list just the alerts for that query and then select and delete all of those alerts. -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ![Filter alerts by rule](/assets/images/help/repository/code-scanning-filter-by-rule.png) {% else %} ![Filter alerts by rule](/assets/images/enterprise/3.1/help/repository/code-scanning-filter-by-rule.png) @@ -195,12 +208,11 @@ To dismiss or delete alerts: 1. If you want to dismiss an alert, it's important to explore the alert first, so that you can choose the correct dismissal reason. Click the alert you'd like to explore. -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ![Open an alert from the summary list](/assets/images/help/repository/code-scanning-click-alert.png) {% else %} ![List of alerts from {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) {% endif %} - 1. Review the alert, then click **Dismiss** and choose a reason for closing the alert. ![Choosing a reason for dismissing an alert](/assets/images/help/repository/code-scanning-alert-close-drop-down.png) {% data reusables.code-scanning.choose-alert-dismissal-reason %} diff --git a/translations/ru-RU/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md b/translations/ru-RU/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md index dfc7a7bae7..5f5eabb210 100644 --- a/translations/ru-RU/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md +++ b/translations/ru-RU/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md @@ -40,8 +40,8 @@ You decide how to generate {% data variables.product.prodname_code_scanning %} a {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} -3. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. {% ifversion fpt or ghes > 3.0 %}If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}. 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)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %} !["Set up code scanning" button to the right of "Code scanning" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png) -4. Under "Get started with {% data variables.product.prodname_code_scanning %}", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png){% ifversion fpt or ghes > 2.22 %}Workflows are only displayed if they are relevant for the programming languages detected in the repository. The {% data variables.product.prodname_codeql_workflow %} is always displayed, but the "Set up this workflow" button is only enabled if {% data variables.product.prodname_codeql %} analysis supports the languages present in the repository.{% endif %} +3. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. {% ifversion fpt or ghes > 3.0 or ghae-next %}If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}. 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)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %} !["Set up code scanning" button to the right of "Code scanning" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png) +4. Under "Get started with {% data variables.product.prodname_code_scanning %}", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png){% ifversion fpt or ghes > 2.22 or ghae-next %}Workflows are only displayed if they are relevant for the programming languages detected in the repository. The {% data variables.product.prodname_codeql_workflow %} is always displayed, but the "Set up this workflow" button is only enabled if {% data variables.product.prodname_codeql %} analysis supports the languages present in the repository.{% endif %} 5. To customize how {% data variables.product.prodname_code_scanning %} scans your code, edit the workflow. Generally you can commit the {% data variables.product.prodname_codeql_workflow %} without making any changes to it. However, many of the third-party workflows require additional configuration, so read the comments in the workflow before committing. @@ -53,10 +53,43 @@ You decide how to generate {% data variables.product.prodname_code_scanning %} a In the default {% data variables.product.prodname_codeql_workflow %}, {% data variables.product.prodname_code_scanning %} is configured to analyze your code each time you either push a change to the default branch or any protected branches, or raise a pull request against the default branch. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)." +The `on:pull_request` and `on:push` triggers for code scanning are each useful for different purposes. For more information, see "[Scanning pull requests](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-pull-requests)" and "[Scanning on push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)." ## Bulk set up of {% data variables.product.prodname_code_scanning %} You can set up {% data variables.product.prodname_code_scanning %} in many repositories at once using a script. If you'd like to use a script to raise pull requests that add a {% data variables.product.prodname_actions %} workflow to multiple repositories, see the [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) repository for an example using Powershell, or [`nickliffen/ghas-enablement`](https://github.com/NickLiffen/ghas-enablement) for teams who do not have Powershell and instead would like to use NodeJS. +## Дальнейшие шаги + +After setting up {% data variables.product.prodname_code_scanning %} for your repository, you can watch the output of the actions as they run. + +{% data reusables.repositories.actions-tab %} + + You'll see a list that includes an entry for running the {% data variables.product.prodname_code_scanning %} workflow. The text of the entry is the title you gave your commit message. + + ![Actions list showing {% data variables.product.prodname_code_scanning %} workflow](/assets/images/help/repository/code-scanning-actions-list.png) + +1. Click the entry for the {% data variables.product.prodname_code_scanning %} workflow. + +1. Click the job name on the left. For example, **Analyze (LANGUAGE)**. + + ![Log output from the {% data variables.product.prodname_code_scanning %} workflow](/assets/images/help/repository/code-scanning-logging-analyze-action.png) + +1. Review the logging output from the actions in this workflow as they run. + +1. After a scan completes, you can view alerts from a completed scan. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)." + +{% note %} + +After you commit the workflow file or create a pull request, {% data variables.product.prodname_code_scanning %} will analyze your code according to the frequency you specified in your workflow file. If you created a pull request, {% data variables.product.prodname_code_scanning %} will only analyze the code on the pull request's topic branch until you merge the pull request into the default branch of the repository. + +{% ifversion fpt or ghes > 3.1 or ghae-next %} + ![Click the "n alerts found" link](/assets/images/help/repository/code-scanning-alerts-found-link.png) +{% else %} + ![Click the "n alerts found" link](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png) +{% endif %} + +{% endnote %} + ## Understanding the pull request checks Each {% data variables.product.prodname_code_scanning %} workflow you set to run on pull requests always has at least two entries listed in the checks section of a pull request. There is one entry for each of the analysis jobs in the workflow, and a final one for the results of the analysis. @@ -65,13 +98,25 @@ 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 a "Missing analysis" 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-issue-3891 %}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. - ![Missing analysis for commit message](/assets/images/help/repository/code-scanning-missing-analysis.png) +{% ifversion fpt or ghes > 3.2 or ghae-issue-3891 %} + ![Analysis not found for commit message](/assets/images/help/repository/code-scanning-analysis-not-found.png) -### Reasons for the "missing analysis" message +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. -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 "Missing analysis for base commit SHA-HASH" message. +For example, in the screenshot above, {% data variables.product.prodname_code_scanning %} found an analysis for the merge commit of the pull request, but no analysis for the head of the main branch. +{% else %} + ![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 %} +### 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 %}"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: @@ -79,7 +124,7 @@ There are other situations where there may be no analysis for the latest commit To the right of "Code scanning", click **Set up code scanning**. -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ![Choose a branch from the Branch drop-down menu](/assets/images/help/repository/code-scanning-branch-dropdown.png) {% else %} ![Choose a branch from the Branch drop-down menu](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-dropdown.png) diff --git a/translations/ru-RU/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md b/translations/ru-RU/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md index 14699ad149..7ccc224129 100644 --- a/translations/ru-RU/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md +++ b/translations/ru-RU/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md @@ -28,6 +28,9 @@ 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 %} +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 %} If your pull request targets a protected branch that uses {% data variables.product.prodname_code_scanning %}, and the repository owner has configured required status checks, then the "{% data variables.product.prodname_code_scanning_capc %} results" check must pass before you can merge the pull request. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)." diff --git a/translations/ru-RU/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md b/translations/ru-RU/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md index 8679701008..3d24818891 100644 --- a/translations/ru-RU/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md +++ b/translations/ru-RU/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md @@ -22,7 +22,7 @@ shortTitle: View code scanning logs You can use a variety of tools to set up {% data variables.product.prodname_code_scanning %} in your repository. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#options-for-setting-up-code-scanning)." -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} The log and diagnostic information available to you depends on the method you use for {% data variables.product.prodname_code_scanning %} in your repository. You can check the type of {% data variables.product.prodname_code_scanning %} you're using in the **Security** tab of your repository, by using the **Tool** drop-down menu in the alert list. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)." ## About analysis and diagnostic information @@ -35,7 +35,7 @@ You can see analysis and diagnostic information for {% data variables.product.pr If you're using the {% data variables.product.prodname_codeql_cli %} outside {% data variables.product.prodname_dotcom %}, you'll see diagnostic information in the output generated during database analysis. This information is also included in the SARIF results file you upload to {% data variables.product.prodname_dotcom %} with the {% data variables.product.prodname_code_scanning %} results. -For information about the {% data variables.product.prodname_codeql_cli %}, see "[Running {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-cli-in-your-ci-system#viewing-log-and-diagnostic-information)." +For information about the {% data variables.product.prodname_codeql_cli %}, see "[Configuring {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system#viewing-log-and-diagnostic-information)." ### About summary metrics @@ -72,7 +72,7 @@ After setting up {% data variables.product.prodname_code_scanning %} for your re After you commit the workflow file or create a pull request, {% data variables.product.prodname_code_scanning %} will analyze your code according to the frequency you specified in your workflow file. If you created a pull request, {% data variables.product.prodname_code_scanning %} will only analyze the code on the pull request's topic branch until you merge the pull request into the default branch of the repository. -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae %} ![Click the "n alerts found" link](/assets/images/help/repository/code-scanning-alerts-found-link.png) {% else %} ![Click the "n alerts found" link](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png) diff --git a/translations/ru-RU/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md b/translations/ru-RU/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md index 8457a514df..810d53d5db 100644 --- a/translations/ru-RU/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md +++ b/translations/ru-RU/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md @@ -37,7 +37,7 @@ If you're using {% data variables.product.prodname_actions %} with the {% data v {% ifversion fpt or ghes > 3.0 or ghae-next %} If you're using the {% data variables.product.prodname_codeql_cli %}, then you can specify the version of SARIF to use. For more information, see "[Configuring {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system#analyzing-a-codeql-database)."{% endif %} -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} You can upload multiple SARIF files for the same tool and commit, and analyze each file using {% data variables.product.prodname_code_scanning %}. You can indicate a "category" for each analysis by specifying a `runAutomationDetails.id` in each file. Only SARIF files with the same category will overwrite each other. For more information about this property, see [`runAutomationDetails` object](#runautomationdetails-object) below. {% endif %} @@ -141,7 +141,7 @@ A location within a programming artifact, such as a file in the repository or a | `region.endLine` | **Required.** The line number of the last character in the region. | | `region.endColumn` | **Required.** The column number of the character following the end of the region. | -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ### `runAutomationDetails` object The `runAutomationDetails` object contains information that specifies the identity of a run. @@ -245,7 +245,7 @@ This SARIF output file has example values to show the minimum required propertie This SARIF output file has example values to show all supported SARIF properties for {% data variables.product.prodname_code_scanning %}. -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ```json { "$schema": "https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json", diff --git a/translations/ru-RU/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md b/translations/ru-RU/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md index 347d7d8e0e..bf69c24193 100644 --- a/translations/ru-RU/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md +++ b/translations/ru-RU/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md @@ -91,8 +91,8 @@ For more information, see "[Running {% data variables.product.prodname_codeql_ru {% endif %} - -{% ifversion ghes = 3.0 or ghae %} + +{% ifversion ghes = 3.0 %} {% data reusables.code-scanning.upload-sarif-ghas %} You add the {% data variables.product.prodname_codeql_runner %} to your third-party system, then call the tool to analyze code and upload the SARIF results to {% data variables.product.product_name %}. The resulting {% data variables.product.prodname_code_scanning %} alerts are shown alongside any alerts generated within {% data variables.product.product_name %}. diff --git a/translations/ru-RU/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md b/translations/ru-RU/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md index 0bcaac5386..43e2898e53 100644 --- a/translations/ru-RU/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md +++ b/translations/ru-RU/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md @@ -30,7 +30,7 @@ Once you've made the {% data variables.product.prodname_codeql_cli %} available You use three different commands to generate results and upload them to {% data variables.product.product_name %}: -{% ifversion fpt or ghes > 3.1 or ghae-next %} +{% ifversion fpt or ghes > 3.1 or ghae %} 1. `database create` to create a {% data variables.product.prodname_codeql %} database to represent the hierarchical structure of each supported programming language in the repository. 2. `database analyze` to run queries to analyze each {% data variables.product.prodname_codeql %} database and summarize the results in a SARIF file. @@ -50,11 +50,11 @@ You can display the command-line help for any command using the     `--help` 3.1 or ghae-next %} + {% ifversion fpt or ghes > 3.1 or ghae %} ```shell # Single supported language - create one CodeQL databsae codeql database create <database> --command<build> --language=<language-identifier> @@ -119,7 +119,7 @@ You can display the command-line help for any command using the `--help` - {% ifversion fpt or ghes > 3.1 or ghae-next %}When used with `--db-cluster`, the option accepts a comma-separated list, or can be specified more than once.{% endif %} + {% ifversion fpt or ghes > 3.1 or ghae %}When used with `--db-cluster`, the option accepts a comma-separated list, or can be specified more than once.{% endif %} @@ -144,7 +144,7 @@ You can display the command-line help for any command using the `--help` - {% ifversion fpt or ghes > 3.1 or ghae-next %} + {% ifversion fpt or ghes > 3.1 or ghae %} @@ -208,7 +208,7 @@ You can display the command-line help for any command using the `--help` 3.1 or ghae-next %}Single language example{% else %}Basic example{% endif %} +### {% ifversion fpt or ghes > 3.1 or ghae %}Single language example{% else %}Basic example{% endif %} This example creates a {% data variables.product.prodname_codeql %} database for the repository checked out at `/checkouts/example-repo`. It uses the JavaScript extractor to create a hierarchical representation of the JavaScript and TypeScript code in the repository. The resulting database is stored in `/codeql-dbs/example-repo`. @@ -226,7 +226,7 @@ $ codeql database create /codeql-dbs/example-repo --language=javascript \ > Successfully created database at /codeql-dbs/example-repo. ``` -{% ifversion fpt or ghes > 3.1 or ghae-next %} +{% ifversion fpt or ghes > 3.1 or ghae %} ### Multiple language example This example creates two {% data variables.product.prodname_codeql %} databases for the repository checked out at `/checkouts/example-repo-multi`. It uses: @@ -273,7 +273,7 @@ $ --output=<output> {% if codeql-packs %}<packs,queries>{% else %} <queries>{% endif %} ``` -{% ifversion fpt or ghes > 3.1 or ghae-next %} +{% ifversion fpt or ghes > 3.1 or ghae %} {% note %} **Note:** If you analyze more than one {% data variables.product.prodname_codeql %} database for a single commit, you must specify a SARIF category for each set of results generated by this command. When you upload the results to {% data variables.product.product_name %}, {% data variables.product.prodname_code_scanning %} uses this category to store the results for each language separately. If you forget to do this, each upload overwrites the previous results. @@ -317,15 +317,14 @@ codeql database analyze <database> --format=<format> \ - <queries> + <packs,queries> - {% octicon "check-circle-fill" aria-label="Required" %} - Specify the queries to run. To run the standard queries used for {% data variables.product.prodname_code_scanning %}, use: <language>-code-scanning.qls where <language> is the short code for the language of the database. To see the other query suites included in the {% data variables.product.prodname_codeql_cli %} bundle, look in /<extraction-root>/codeql/qlpacks/codeql-<language>/codeql-suites. For information about creating your own query suite, see Creating CodeQL query suites in the documentation for the {% data variables.product.prodname_codeql_cli %}. + Specify {% data variables.product.prodname_codeql %} packs or queries to run. To run the standard queries used for {% data variables.product.prodname_code_scanning %}, omit this parameter. To see the other query suites included in the {% data variables.product.prodname_codeql_cli %} bundle, look in /<extraction-root>/codeql/qlpacks/codeql-<language>/codeql-suites. For information about creating your own query suite, see Creating CodeQL query suites in the documentation for the {% data variables.product.prodname_codeql_cli %}. @@ -353,7 +352,7 @@ codeql database analyze <database> --format=<format> \ - Specify where to save the SARIF results file.{% ifversion fpt or ghes > 3.1 or ghae-next %} + Specify where to save the SARIF results file.{% ifversion fpt or ghes > 3.1 or ghae %} @@ -406,7 +405,7 @@ codeql database analyze <database> --format=<format> \ - Optional. Use to get more detailed information about the analysis process{% ifversion fpt or ghes > 3.1 or ghae-next %} and diagnostic data from the database creation process{% endif %}. + Optional. Use to get more detailed information about the analysis process{% ifversion fpt or ghes > 3.1 or ghae %} and diagnostic data from the database creation process{% endif %}. @@ -415,11 +414,11 @@ For more information, see [Analyzing databases with the {% data variables.produc ### Basic example -This example analyzes a {% data variables.product.prodname_codeql %} database stored at `/codeql-dbs/example-repo` and saves the results as a SARIF file: `/temp/example-repo-js.sarif`. {% ifversion fpt or ghes > 3.1 or ghae-next %}It uses `--sarif-category` to include extra information in the SARIF file that identifies the results as JavaScript. This is essential when you have more than one {% data variables.product.prodname_codeql %} database to analyze for a single commit in a repository.{% endif %} +This example analyzes a {% data variables.product.prodname_codeql %} database stored at `/codeql-dbs/example-repo` and saves the results as a SARIF file: `/temp/example-repo-js.sarif`. {% ifversion fpt or ghes > 3.1 or ghae %}It uses `--sarif-category` to include extra information in the SARIF file that identifies the results as JavaScript. This is essential when you have more than one {% data variables.product.prodname_codeql %} database to analyze for a single commit in a repository.{% endif %} ``` $ codeql database analyze /codeql-dbs/example-repo \ - javascript-code-scanning.qls {% ifversion fpt or ghes > 3.1 or ghae-next %}--sarif-category=javascript{% endif %} + javascript-code-scanning.qls {% ifversion fpt or ghes > 3.1 or ghae %}--sarif-category=javascript{% endif %} --format={% ifversion fpt or ghae %}sarif-latest{% else %}sarifv2.1.0{% endif %} --output=/temp/example-repo-js.sarif > Running queries. @@ -444,7 +443,7 @@ When you have decided on the most secure and reliable method for your CI server, ```shell echo "$UPLOAD_TOKEN" | codeql github upload-results --repository=<repository-name> \ --ref=<ref> --commit=<commit> --sarif=<file> \ - {% ifversion ghes > 3.0 or ghae-next %}--github-url=<URL> {% endif %}--github-auth-stdin + {% ifversion ghes > 3.0 or ghae %}--github-url=<URL> {% endif %}--github-auth-stdin ``` @@ -486,7 +485,7 @@ When you have decided on the most secure and reliable method for your CI server, @@ -514,7 +513,7 @@ When you have decided on the most secure and reliable method for your CI server, @@ -555,7 +554,7 @@ This example uploads results from the SARIF file `temp/example-repo-js.sarif` to ``` $ echo $UPLOAD_TOKEN | codeql github upload-results --repository=my-org/example-repo \ --ref=refs/heads/main --commit=deb275d2d5fe9a522a0b7bd8b6b6a1c939552718 \ - --sarif=/temp/example-repo-js.sarif {% ifversion ghes > 3.0 or ghae-next %}--github-url={% data variables.command_line.git_url_example %} \ + --sarif=/temp/example-repo-js.sarif {% ifversion ghes > 3.0 or ghae %}--github-url={% data variables.command_line.git_url_example %} \ {% endif %}--github-auth-stdin ``` @@ -641,6 +640,7 @@ $ codeql database analyze /codeql-dbs/example-repo octo-org/security-queries \ {% endif %} {% ifversion fpt or ghes > 3.1 or ghae-next %} + ## Example CI configuration for {% data variables.product.prodname_codeql %} analysis This is an example of the series of commands that you might use to analyze a codebase with two supported languages and then upload the results to {% data variables.product.product_name %}. diff --git a/translations/ru-RU/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md b/translations/ru-RU/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md index e146c04727..79903f7964 100644 --- a/translations/ru-RU/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md +++ b/translations/ru-RU/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md @@ -190,7 +190,7 @@ Analyzes the code in the {% data variables.product.prodname_codeql %} databases | `--no-upload` | | None. Stops the {% data variables.product.prodname_codeql_runner %} from uploading the results to {% data variables.product.product_name %}. | | `--output-dir` | | Directory where the output SARIF files are stored. The default is in the directory of temporary files. | | `--ram` | | Amount of memory to use when running queries. The default is to use all available memory. | -| `--no-add-snippets` | | None. Excludes code snippets from the SARIF output. |{% ifversion fpt or ghes > 3.1 %} +| `--no-add-snippets` | | None. Excludes code snippets from the SARIF output. |{% ifversion fpt or ghes > 3.1 or ghae %} | `--category` | | Category to include in the SARIF results file for this analysis. A category can be used to distinguish multiple analyses for the same tool and commit, but performed on different languages or different parts of the code. This value will appear in the `.automationDetails.id` property in SARIF v2.1.0. {% endif %} | `--threads` | | Number of threads to use when running queries. The default is to use all available cores. | diff --git a/translations/ru-RU/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md b/translations/ru-RU/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md index 46ec04b016..b9fbfa6ec3 100644 --- a/translations/ru-RU/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md +++ b/translations/ru-RU/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md @@ -25,7 +25,7 @@ topics: {% data variables.product.company_short %} performs {% data variables.product.prodname_secret_scanning %} on {% ifversion fpt %}public and private{% endif %} repositories for secret patterns provided by {% data variables.product.company_short %} and {% data variables.product.company_short %} partners. For more information on the {% data variables.product.prodname_secret_scanning %} partner program, see "Secret scanning partner program." -However, there can be situations where you want to scan for other secret patterns in your {% ifversion fpt %}private{% endif %} repositories. For example, you might have a secret pattern that is internal to your organization. For these situations, you can define custom {% data variables.product.prodname_secret_scanning %} patterns in your enterprise, organization, or {% ifversion fpt %}private{% endif %} repository on {% data variables.product.product_name %}. You can define up to 20 custom patterns for each {% ifversion fpt %}private{% endif %} repository, organization, or enterprise account. +However, there can be situations where you want to scan for other secret patterns in your {% ifversion fpt %}private{% endif %} repositories. For example, you might have a secret pattern that is internal to your organization. For these situations, you can define custom {% data variables.product.prodname_secret_scanning %} patterns in your enterprise, organization, or {% ifversion fpt %}private{% endif %} repository on {% data variables.product.product_name %}. You can define up to 100 custom patterns for each organization or enterprise account, and up to 20 custom patterns per {% ifversion fpt %}private{% endif %} repository. {% ifversion ghes < 3.3 or ghae %} {% note %} diff --git a/translations/ru-RU/content/code-security/security-advisories/publishing-a-security-advisory.md b/translations/ru-RU/content/code-security/security-advisories/publishing-a-security-advisory.md index 7f8edca1bc..96f3cce443 100644 --- a/translations/ru-RU/content/code-security/security-advisories/publishing-a-security-advisory.md +++ b/translations/ru-RU/content/code-security/security-advisories/publishing-a-security-advisory.md @@ -61,19 +61,6 @@ After you publish a security advisory, the URL for the security advisory will re If you need to update or correct information in a security advisory that you've published, you can edit the security advisory. For more information, see "[Editing a security advisory](/github/managing-security-vulnerabilities/editing-a-security-advisory)." -## Requesting a CVE identification number - -Anyone with admin permissions to a security advisory can request a CVE identification number for the security advisory. - -{% data reusables.repositories.request-security-advisory-cve-id %} For more information, see "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories#cve-identification-numbers)." - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-security %} -{% data reusables.repositories.sidebar-advisories %} -4. In the "Security Advisories" list, click the security advisory you'd like to request a CVE identification number for. ![Security advisory in list](/assets/images/help/security/security-advisory-in-list.png) -5. Use the **Publish advisory** drop-down menu, and click **Request CVE**. ![Request CVE in drop-down](/assets/images/help/security/security-advisory-drop-down-request-cve.png) -6. Click **Request CVE**. ![Request CVE button](/assets/images/help/security/security-advisory-request-cve-button.png) - ## Publishing a security advisory Publishing a security advisory deletes the temporary private fork for the security advisory. @@ -88,6 +75,17 @@ Publishing a security advisory deletes the temporary private fork for the securi {% data reusables.repositories.github-reviews-security-advisories %} +## Requesting a CVE identification number (Optional) + +{% data reusables.repositories.request-security-advisory-cve-id %} For more information, see "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories#cve-identification-numbers)." + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-security %} +{% data reusables.repositories.sidebar-advisories %} +4. In the "Security Advisories" list, click the security advisory you'd like to request a CVE identification number for. ![Security advisory in list](/assets/images/help/security/security-advisory-in-list.png) +5. Use the **Publish advisory** drop-down menu, and click **Request CVE**. ![Request CVE in drop-down](/assets/images/help/security/security-advisory-drop-down-request-cve.png) +6. Click **Request CVE**. ![Request CVE button](/assets/images/help/security/security-advisory-request-cve-button.png) + ## Дополнительная литература - "[Withdrawing a security advisory](/github/managing-security-vulnerabilities/withdrawing-a-security-advisory)" diff --git a/translations/ru-RU/content/code-security/security-overview/about-the-security-overview.md b/translations/ru-RU/content/code-security/security-overview/about-the-security-overview.md index ded7b94e5b..8f64cf0ecf 100644 --- a/translations/ru-RU/content/code-security/security-overview/about-the-security-overview.md +++ b/translations/ru-RU/content/code-security/security-overview/about-the-security-overview.md @@ -6,8 +6,8 @@ redirect_from: - /code-security/security-overview/exploring-security-alerts versions: fpt: '*' + ghae: issue-4554 ghes: '>3.1' - ghae: next type: how_to topics: - Security overview diff --git a/translations/ru-RU/content/code-security/security-overview/index.md b/translations/ru-RU/content/code-security/security-overview/index.md index 3adfe1802b..88ef0c8e5b 100644 --- a/translations/ru-RU/content/code-security/security-overview/index.md +++ b/translations/ru-RU/content/code-security/security-overview/index.md @@ -5,8 +5,8 @@ intro: 'View, sort, and filter the security alerts from across your organization product: '{% data reusables.gated-features.security-center %}' versions: fpt: '*' + ghae: issue-4554 ghes: '>3.1' - ghae: next topics: - Security overview - Advanced Security diff --git a/translations/ru-RU/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md b/translations/ru-RU/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md index 2088b810a5..ba0e0692cc 100644 --- a/translations/ru-RU/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md +++ b/translations/ru-RU/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md @@ -1,11 +1,11 @@ --- title: About dependency review intro: 'Dependency review lets you catch vulnerable dependencies before you introduce them to your environment, and provides information on license, dependents, and age of dependencies.' +product: '{% data reusables.gated-features.dependency-review %}' shortTitle: Dependency review versions: fpt: '*' ghes: '>= 3.2' - product: '{% data reusables.gated-features.dependency-review %}' type: overview topics: - Advanced Security diff --git a/translations/ru-RU/content/codespaces/developing-in-codespaces/index.md b/translations/ru-RU/content/codespaces/developing-in-codespaces/index.md index 14978ebfe8..12751acf49 100644 --- a/translations/ru-RU/content/codespaces/developing-in-codespaces/index.md +++ b/translations/ru-RU/content/codespaces/developing-in-codespaces/index.md @@ -15,6 +15,5 @@ children: - /forwarding-ports-in-your-codespace - /changing-the-machine-type-for-your-codespace - /using-codespaces-in-visual-studio-code - - /web-based-editor --- diff --git a/translations/ru-RU/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md b/translations/ru-RU/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md index f4bf4506e8..34075e1b3a 100644 --- a/translations/ru-RU/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md +++ b/translations/ru-RU/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md @@ -30,9 +30,7 @@ A typical workflow for updating a file using {% data variables.product.prodname_ ## Creating or switching branches -1. If the current branch is not shown in the status bar, at the bottom of your codespace, right-click the status bar and select **Source control**. -1. Click the branch name in the status bar. ![The branch in the status bar](/assets/images/help/codespaces/branch-in-status-bar.png) -1. In the drop-down, either click the branch you want to switch to, or enter the name for a new branch and click **Create new branch**. ![Choose from the branch menu](/assets/images/help/codespaces/create-new-branch.png) +{% data reusables.codespaces.create-or-switch-branch %} {% tip %} @@ -64,16 +62,11 @@ If the fetch operation detects new changes on the remote repository, you'll see ## Committing your changes -{% data reusables.codespaces.source-control-display-dark %} -1. To stage your changes, click **+** next to the file you've changed, or next to **Changes** if you've changed multiple files and you want to stage them all. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-stage.png) -1. Type a commit message describing the change you've made. ![Source control side bar with a commit message](/assets/images/help/codespaces/codespaces-commit-commit-message.png) -1. To commit your staged changes, click the check mark at the top the source control side bar. ![Click the check mark icon](/assets/images/help/codespaces/codespaces-commit-checkmark-icon.png) +{% data reusables.codespaces.source-control-commit-changes %} ## Raising a pull request -1. After you've committed changes to your local copy of the repository, click the **Create Pull Request** icon. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-pr-button.png) -1. Check that the local branch and repository you're merging from, and the remote branch and repository you're merging into, are correct. Then give the pull request a title and a description. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-pr.png) -1. Click **Create**. +{% data reusables.codespaces.source-control-pull-request %} ## Pushing changes to your remote repository diff --git a/translations/ru-RU/content/codespaces/index.md b/translations/ru-RU/content/codespaces/index.md index 06035cb35d..5c3572bab3 100644 --- a/translations/ru-RU/content/codespaces/index.md +++ b/translations/ru-RU/content/codespaces/index.md @@ -41,6 +41,7 @@ children: - /managing-codespaces-for-your-organization - /codespaces-reference - /troubleshooting + - /the-githubdev-web-based-editor - /guides --- diff --git a/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md b/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md index e6f04da02e..0a55b19d4f 100644 --- a/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md +++ b/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md @@ -72,3 +72,7 @@ You can check which access policies are applied to a secret in your organization {% data reusables.github-actions.sidebar-secret %} 1. The list of secrets includes any configured permissions and policies. Например: ![Secrets list](/assets/images/help/settings/actions-org-secrets-list.png) 1. For more details on the configured permissions for each secret, click **Update**. + +## Дальнейшее изучение + +- "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)" diff --git a/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md b/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md index 5674555da1..8917329f7d 100644 --- a/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md +++ b/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md @@ -26,3 +26,7 @@ To manage which users in your organization can use {% data variables.product.pro {% data reusables.organizations.click-codespaces %} 1. Under "Access and security", select the setting you want for your organization. ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-org-access-and-security-radio-buttons.png) 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 owned by your organization. Repeat for all repositories whose codespaces you want to access other repositories. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) + +## Дальнейшее изучение + +- "[Managing repository access for your codespaces](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces)" diff --git a/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md b/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md index 860f8c42d6..d876a26f60 100644 --- a/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md +++ b/translations/ru-RU/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md @@ -19,3 +19,7 @@ When any member of your organization performs an action related to {% data varia ![Audit log with Codespaces information](/assets/images/help/settings/codespaces-audit-log-org.png) The audit log includes details such as who performed the action, what the action was, and when the action was performed. For information on {% data variables.product.prodname_codespaces %} actions, see "[{% data variables.product.prodname_codespaces %} category actions](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#codespaces-category-actions)." + +## Дальнейшее изучение + +- "[Reviewing your security logs for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces)" diff --git a/translations/ru-RU/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md b/translations/ru-RU/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md index c63591801a..88dc13b843 100644 --- a/translations/ru-RU/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md +++ b/translations/ru-RU/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md @@ -73,3 +73,7 @@ You can update the value of an existing secret, and you can change which reposit {% data reusables.user_settings.codespaces-tab %} 1. Under "Codespaces secrets", to the right of the secret you want to delete, click **Delete**. !["Delete" button](/assets/images/help/settings/codespaces-secret-delete-button.png) 1. Read the warning, then click **OK**. ![Confirmation to delete secret](/assets/images/help/settings/codespaces-secret-delete-warning.png) + +## Дальнейшее изучение + +- "[Managing encrypted secrets for your repository and organization for {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces)" diff --git a/translations/ru-RU/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md b/translations/ru-RU/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md index 57753fbdaa..591a58c22d 100644 --- a/translations/ru-RU/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md +++ b/translations/ru-RU/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md @@ -29,6 +29,6 @@ Once you enable GPG verification, it will immediately take effect for all your c {% note %} -**Note:** Once you have enabled GPG verification for {% data variables.product.prodname_codespaces %}, you also must append `-s` to each commit in order for it to be signed. To do this in {% data variables.product.prodname_vscode %}, ensure the "Git: Enable Commit Signing" option is enabled from the Settings. +**Note:** Once you have enabled GPG verification for {% data variables.product.prodname_codespaces %}, you also must append `-S` to each commit in order for it to be signed. To do this in {% data variables.product.prodname_vscode %}, ensure the "Git: Enable Commit Signing" option is enabled from the Settings. {% endnote %} diff --git a/translations/ru-RU/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md b/translations/ru-RU/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md index d79c06de7f..2024510ab7 100644 --- a/translations/ru-RU/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md +++ b/translations/ru-RU/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md @@ -20,3 +20,7 @@ When you enable access and security for a repository owned by your user account, {% data reusables.user_settings.codespaces-tab %} 1. Under "Access and security", select the setting you want for your user account. ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png) 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. !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) + +## Дальнейшее изучение + +- "[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/ru-RU/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md b/translations/ru-RU/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md index 956845aa41..388d1fb2aa 100644 --- a/translations/ru-RU/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md +++ b/translations/ru-RU/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md @@ -20,3 +20,7 @@ When you perform an action related to {% data variables.product.prodname_codespa ![security log with Codespaces information](/assets/images/help/settings/codespaces-audit-log.png) The security log includes details on what action occurred and when you performed it. For information about {% data variables.product.prodname_codespaces %} actions, see "[{% data variables.product.prodname_codespaces %} category actions](/github/authenticating-to-github/reviewing-your-security-log#codespaces-category-actions)". + +## Дальнейшее изучение + +- "[Reviewing your organization's audit logs for {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces)" diff --git a/translations/ru-RU/content/codespaces/the-githubdev-web-based-editor.md b/translations/ru-RU/content/codespaces/the-githubdev-web-based-editor.md new file mode 100644 index 0000000000..e003bf30f8 --- /dev/null +++ b/translations/ru-RU/content/codespaces/the-githubdev-web-based-editor.md @@ -0,0 +1,106 @@ +--- +title: The github.dev web-based editor +intro: 'Use the github.dev {% data variables.product.prodname_serverless %} from your repository or pull request to create and commit changes.' +versions: + fpt: '*' +type: how_to +miniTocMaxHeadingLevel: 3 +topics: + - Codespaces + - Visual Studio Code + - Developer +shortTitle: Web-based editor +redirect_from: + - /codespaces/developing-in-codespaces/web-based-editor +--- + +{% note %} + +**Note:** The github.dev {% data variables.product.prodname_serverless %} is currently in beta preview. You can provide feedback [in our Discussions](https://github.co/browser-editor-feedback). + +{% endnote %} + +## About the {% data variables.product.prodname_serverless %} + +The {% data variables.product.prodname_serverless %} introduces a lightweight editing experience that runs entirely in your browser. With the {% data variables.product.prodname_serverless %}, you can navigate files and source code repositories from {% data variables.product.prodname_dotcom %}, and make and commit code changes. You can open any repository, fork, or pull request in the editor. + +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 %} 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. + +## Opening the {% data variables.product.prodname_serverless %} + +You can open any {% data variables.product.prodname_dotcom %} repository in the {% data variables.product.prodname_serverless %} in either of the following ways: + +- Press `.` while browsing any repository or pull request on {% data variables.product.prodname_dotcom %}. +- Change the URL from "github.com" to "github.dev". + +## {% data variables.product.prodname_codespaces %} and the {% data variables.product.prodname_serverless %} + +Both the {% data variables.product.prodname_serverless %} and {% data variables.product.prodname_codespaces %} allow you to edit your code straight from your repository. However, both have slightly different benefits, depending on your use case. + +| | {% data variables.product.prodname_serverless %} | {% data variables.product.prodname_codespaces %} +| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| **Cost** | Бесплатные. | Costs for compute and storage. For information on pricing, see "[Codespaces pricing](/en/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)." | +| **Availability** | Available to everyone on GitHub.com. | Available for organizations using GitHub Team or GitHub Enterprise Cloud. | +| **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. | + +### Continue working on {% data variables.product.prodname_codespaces %} + +You can start your workflow in the {% data variables.product.prodname_serverless %} and continue working on a codespace, provided you have [access to {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces). If you try to access the Run and Debug View or the Terminal, you'll be notified that they are not available in the {% data variables.product.prodname_serverless %}. + +To continue your work in a codespace, click **Continue Working on…** and select **Create New Codespace** to create a codespace on your current branch. Before you choose this option, you must commit any changes. + +![A screenshot that shows the "Continue Working on" button in the UI](/assets/images/help/codespaces/codespaces-continue-working.png) + +## 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. + +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. + +### Create a new branch + +{% data reusables.codespaces.create-or-switch-branch %} + Any uncommited changes you have made in your old branch will be available on your new branch. + +### Commit your changes + +{% data reusables.codespaces.source-control-commit-changes %} +5. Once you have committed your changes, they will automatically be pushed to your branch on {% data variables.product.prodname_dotcom %}. +### Create a pull request + +{% data reusables.codespaces.source-control-pull-request %} + +### Working with an existing pull request + +You can use the {% data variables.product.prodname_serverless %} to work with an existing pull request. + +1. Browse to the pull request you'd like to open in the {% data variables.product.prodname_serverless %}. +2. Press `.` to open the pull request in the {% data variables.product.prodname_serverless %}. +3. Once you have made any changes, commit them using the steps in [Commit your changes](#commit-your-changes). Your changes will be committed directly to the branch, it's not necessary to push the changes. + +## 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. + +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. + + +## Устранение проблем + +If you have issues opening the {% data variables.product.prodname_serverless %}, try the following: + +- Make sure you are signed in to {% data variables.product.prodname_dotcom %}. +- Disable any ad blockers. +- Use a non-incognito window in your browser to open 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. diff --git a/translations/ru-RU/content/communities/documenting-your-project-with-wikis/about-wikis.md b/translations/ru-RU/content/communities/documenting-your-project-with-wikis/about-wikis.md index 51c8abb680..e573636acd 100644 --- a/translations/ru-RU/content/communities/documenting-your-project-with-wikis/about-wikis.md +++ b/translations/ru-RU/content/communities/documenting-your-project-with-wikis/about-wikis.md @@ -34,4 +34,4 @@ You can edit wikis directly on {% data variables.product.product_name %}, or you - "[Creating a footer or sidebar for your wiki](/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki)" - "[Editing wiki content](/communities/documenting-your-project-with-wikis/editing-wiki-content)" - "[Viewing a wiki's history of changes](/articles/viewing-a-wiki-s-history-of-changes)" -- "[Searching wikis](/articles/searching-wikis)" +- "[Searching wikis](/search-github/searching-on-github/searching-wikis)" diff --git a/translations/ru-RU/content/communities/moderating-comments-and-conversations/locking-conversations.md b/translations/ru-RU/content/communities/moderating-comments-and-conversations/locking-conversations.md index 5c03653af8..7f2f25fbf1 100644 --- a/translations/ru-RU/content/communities/moderating-comments-and-conversations/locking-conversations.md +++ b/translations/ru-RU/content/communities/moderating-comments-and-conversations/locking-conversations.md @@ -20,7 +20,7 @@ Locking a conversation creates a timeline event that is visible to anyone with r While a conversation is locked, only [people with write access](/articles/repository-permission-levels-for-an-organization/) and [repository owners and collaborators](/articles/permission-levels-for-a-user-account-repository/#collaborator-access-for-a-repository-owned-by-a-user-account) can add, hide, and delete comments. -To search for locked conversations in a repository that is not archived, you can use the search qualifiers `is:locked` and `archived:false`. Conversations are automatically locked in archived repositories. For more information, see "[Searching issues and pull requests](/articles/searching-issues-and-pull-requests#search-based-on-whether-a-conversation-is-locked)." +To search for locked conversations in a repository that is not archived, you can use the search qualifiers `is:locked` and `archived:false`. Conversations are automatically locked in archived repositories. For more information, see "[Searching issues and pull requests](/search-github/searching-on-github/searching-issues-and-pull-requests#search-based-on-whether-a-conversation-is-locked)." 1. Optionally, write a comment explaining why you're locking the conversation. 2. In the right margin of the issue or pull request, or above the comment box on the commit page, click **Lock conversation**. ![Lock conversation link](/assets/images/help/repository/lock-conversation.png) diff --git a/translations/ru-RU/content/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels.md b/translations/ru-RU/content/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels.md index 8b0911cb5b..397f1d48b2 100644 --- a/translations/ru-RU/content/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels.md +++ b/translations/ru-RU/content/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels.md @@ -12,7 +12,7 @@ topics: shortTitle: Encourage contributions --- -You can apply the `good first issue` label to issues in your public repository so that people can find them when searching by labels. For more information about searching by labels, see "[Searching issues and pull requests](/articles/searching-issues-and-pull-requests/#search-by-label)." +You can apply the `good first issue` label to issues in your public repository so that people can find them when searching by labels. For more information about searching by labels, see "[Searching issues and pull requests](/search-github/searching-on-github/searching-issues-and-pull-requests/#search-by-label)." {% data variables.product.prodname_dotcom %} uses an algorithm to determine the most approachable issues in each repository and surface them in various places on {% data variables.product.prodname_dotcom_the_website %}. Adding the `good first issue` label can increase the likelihood that your issues are surfaced. @@ -24,4 +24,4 @@ You can apply the `good first issue` label to issues in your public repository s ## Дополнительная литература - "[About labels](/articles/about-labels)" -- "[Searching for repositories](/articles/searching-for-repositories)" +- "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories)" diff --git a/translations/ru-RU/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md b/translations/ru-RU/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md index b8861d1097..44dc332188 100644 --- a/translations/ru-RU/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md +++ b/translations/ru-RU/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md @@ -42,6 +42,7 @@ Using the web application flow, the process to identify users on your site is: If you select **Request user authorization (OAuth) during installation** when creating or modifying your app, step 1 will be completed during app installation. For more information, see "[Authorizing users during installation](/apps/installing-github-apps/#authorizing-users-during-installation)." ### 1. Request a user's GitHub identity +Direct the user to the following URL in their browser: GET {% data variables.product.oauth_host_code %}/login/oauth/authorize @@ -77,6 +78,8 @@ Exchange this `code` for an access token. When expiring tokens are enabled, the Expiring user tokens are currently an optional feature and subject to change. To opt-in to the user-to-server token expiration feature, see "[Activating optional features for apps](/developers/apps/activating-optional-features-for-apps)." +Make a request to the following endpoint to receive an access token: + POST {% data variables.product.oauth_host_code %}/login/oauth/access_token #### Parameters diff --git a/translations/ru-RU/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md b/translations/ru-RU/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md index 753b85353d..f68d96ceac 100644 --- a/translations/ru-RU/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md +++ b/translations/ru-RU/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md @@ -32,7 +32,7 @@ Different server-to-server request rate limits apply to {% data variables.produc ### {% data variables.product.prodname_ghe_cloud %} server-to-server rate limits -{% data variables.product.prodname_github_apps %} that are installed on an organization or repository owned by a {% data variables.product.prodname_ghe_cloud %} account and make server-to-server requests have a rate limit of 15,000 requests per hour. +{% data variables.product.prodname_github_apps %} that are installed on an organization or repository owned by a {% data variables.product.prodname_ghe_cloud %} account and make server-to-server requests have a rate limit of 15,000 requests per hour per organization for organization installations or per repository for repository installations. {% endif %} diff --git a/translations/ru-RU/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md b/translations/ru-RU/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md index 615ee82d95..b78b1e152f 100644 --- a/translations/ru-RU/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md +++ b/translations/ru-RU/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md @@ -78,19 +78,29 @@ Exchange this `code` for an access token: By default, the response takes the following form: - access_token={% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&token_type=bearer +``` +access_token={% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&scope=repo%2Cgist&token_type=bearer +``` -You can also receive the content in different formats depending on the Accept header: +{% data reusables.apps.oauth-auth-vary-response %} - Accept: application/json - {"access_token":"{% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "scope":"repo,gist", "token_type":"bearer"} - - Accept: application/xml - - bearer - repo,gist - {% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %} - +```json +Accept: application/json +{ + "access_token":"{% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", + "scope":"repo,gist", + "token_type":"bearer" +} +``` + +```xml +Accept: application/xml + + bearer + repo,gist + {% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %} + +``` ### 3. Use the access token to access the API @@ -138,27 +148,35 @@ Your app must request a user verification code and verification URL that the app #### Response -{% ifversion fpt %} - ```JSON - { - "device_code": "3584d83530557fdd1f46af8289938c8ef79f9dc5", - "user_code": "WDJB-MJHT", - "verification_uri": "https://github.com/login/device", - "expires_in": 900, - "interval": 5 - } - ``` -{% else %} - ```JSON - { - "device_code": "3584d83530557fdd1f46af8289938c8ef79f9dc5", - "user_code": "WDJB-MJHT", - "verification_uri": "http(s)://[hostname]/login/device", - "expires_in": 900, - "interval": 5 - } - ``` -{% endif %} +By default, the response takes the following form: + +``` +device_code=3584d83530557fdd1f46af8289938c8ef79f9dc5&expires_in=900&interval=5&user_code=WDJB-MJHT&verification_uri=https%3A%2F%{% data variables.product.product_url %}%2Flogin%2Fdevice +``` + +{% data reusables.apps.oauth-auth-vary-response %} + +```json +Accept: application/json +{ + "device_code": "3584d83530557fdd1f46af8289938c8ef79f9dc5", + "user_code": "WDJB-MJHT", + "verification_uri": "{% data variables.product.oauth_host_code %}/login/device", + "expires_in": 900, + "interval": 5 +} +``` + +```xml +Accept: application/xml + + 3584d83530557fdd1f46af8289938c8ef79f9dc5 + WDJB-MJHT + {% data variables.product.oauth_host_code %}/login/device + 900 + 5 + +``` #### Response parameters @@ -196,14 +214,32 @@ Once the user has authorized, the app will receive an access token that can be u #### Response +By default, the response takes the following form: + +``` +access_token={% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&token_type=bearer&scope=repo%2Cgist +``` + +{% data reusables.apps.oauth-auth-vary-response %} + ```json +Accept: application/json { "access_token": "{% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "token_type": "bearer", - "scope": "user" + "scope": "repo,gist" } ``` +```xml +Accept: application/xml + + {% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %} + bearer + gist,repo + +``` + ### Rate limits for the device flow When a user submits the verification code on the browser, there is a rate limit of 50 submissions in an hour per application. diff --git a/translations/ru-RU/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md b/translations/ru-RU/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md index b266ea4dce..5185473a47 100644 --- a/translations/ru-RU/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md +++ b/translations/ru-RU/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md @@ -25,7 +25,7 @@ Public installation flows have a landing page to enable other people besides the ## Private installation flow -Private installation flows allow only the owner of a GitHub App to install it. Limited information about the GitHub App will still exist on a public page, but the **Install** button will only be available to organization administrators or the user account if the GitHub App is owned by an individual account. Private{% ifversion ghes < 3.2 or ghae %}, or internal,{% endif %} GitHub Apps can only be installed on the user or organization account of the owner. +Private installation flows allow only the owner of a GitHub App to install it. Limited information about the GitHub App will still exist on a public page, but the **Install** button will only be available to organization administrators or the user account if the GitHub App is owned by an individual account. {% ifversion fpt or ghes > 3.1 or ghae-next %}Private {% else %}Private (also known as internal){% endif %} GitHub Apps can only be installed on the user or organization account of the owner. ## Changing who can install your GitHub App @@ -36,5 +36,5 @@ To change who can install the GitHub App: {% data reusables.user-settings.github_apps %} 3. Select the GitHub App whose installation option you want to change. ![App selection](/assets/images/github-apps/github_apps_select-app.png) {% data reusables.user-settings.github_apps_advanced %} -5. Depending on the installation option of your GitHub App, click either **Make public** or **Make {% ifversion fpt or ghes > 3.1 %}private{% else %}internal{% endif %}**. ![Button to change the installation option of your GitHub App](/assets/images/github-apps/github_apps_make_public.png) -6. Depending on the installation option of your GitHub App, click either **Yes, make this GitHub App public** or **Yes, make this GitHub App {% ifversion fpt or ghes > 3.1 %}private{% else %}internal{% endif %}**. ![Button to confirm the change of your installation option](/assets/images/github-apps/github_apps_confirm_installation_option.png) +5. Depending on the installation option of your GitHub App, click either **Make public** or **Make {% ifversion fpt or ghes > 3.1 or ghae-next %}private{% else %}internal{% endif %}**. ![Button to change the installation option of your GitHub App](/assets/images/github-apps/github_apps_make_public.png) +6. Depending on the installation option of your GitHub App, click either **Yes, make this GitHub App public** or **Yes, make this GitHub App {% ifversion fpt or ghes < 3.2 %}internal{% else %}private{% endif %}**. ![Button to confirm the change of your installation option](/assets/images/github-apps/github_apps_confirm_installation_option.png) diff --git a/translations/ru-RU/content/developers/github-marketplace/github-marketplace-overview/about-marketplace-badges.md b/translations/ru-RU/content/developers/github-marketplace/github-marketplace-overview/about-marketplace-badges.md index 74cb9ed35a..092a97f372 100644 --- a/translations/ru-RU/content/developers/github-marketplace/github-marketplace-overview/about-marketplace-badges.md +++ b/translations/ru-RU/content/developers/github-marketplace/github-marketplace-overview/about-marketplace-badges.md @@ -30,7 +30,7 @@ Some apps on the {% data variables.product.prodname_marketplace %} have the {% o For more information about the requirements for listing an app on {% data variables.product.prodname_marketplace %}, see "[Requirements for listing an app on {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)." -For information on finding apps to use, see "[Searching {% data variables.product.prodname_marketplace %}](/github/searching-for-information-on-github/searching-github-marketplace)." +For information on finding apps to use, see "[Searching {% data variables.product.prodname_marketplace %}](/search-github/searching-on-github/searching-github-marketplace)." ## For GitHub actions diff --git a/translations/ru-RU/content/developers/overview/index.md b/translations/ru-RU/content/developers/overview/index.md index 7c84c71121..6dba622d13 100644 --- a/translations/ru-RU/content/developers/overview/index.md +++ b/translations/ru-RU/content/developers/overview/index.md @@ -8,7 +8,6 @@ versions: children: - /about-githubs-apis - /managing-deploy-keys - - /viewing-deployment-history - /using-ssh-agent-forwarding - /secret-scanning-partner-program - /replacing-github-services diff --git a/translations/ru-RU/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md b/translations/ru-RU/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md index ae91c26d77..351a0fba6a 100644 --- a/translations/ru-RU/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md +++ b/translations/ru-RU/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md @@ -190,7 +190,7 @@ Activity related to a branch protection rule. For more information, see "[About {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} -`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 %}`github` {% elsif ghes > 3.0 %}`github-enterprise` {% else %}empty {% endif %}for all other actions. +`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 %}`github`{% elsif ghes > 3.0 or ghae-next %}`github-enterprise`{% else %}empty{% endif %} for all other actions. ### Webhook payload example @@ -1032,24 +1032,29 @@ Deliveries for `review_requested` and `review_request_removed` events will have ### Webhook payload object -| Клавиша | Тип | Description | -| -------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `ref` | `строка` | The full [`git ref`](/rest/reference/git#refs) that was pushed. Example: `refs/heads/master`. | -| `before` | `строка` | The SHA of the most recent commit on `ref` before the push. | -| `after` | `строка` | The SHA of the most recent commit on `ref` after the push. | -| `commits` | `array` | An array of commit objects describing the pushed commits. (The array includes a maximum of 20 commits. If necessary, you can use the [Commits API](/rest/reference/repos#commits) to fetch additional commits. This limit is applied to timeline events only and isn't applied to webhook deliveries.) | -| `commits[][id]` | `строка` | The SHA of the commit. | -| `commits[][timestamp]` | `строка` | The ISO 8601 timestamp of the commit. | -| `commits[][message]` | `строка` | The commit message. | -| `commits[][author]` | `объект` | The git author of the commit. | -| `commits[][author][name]` | `строка` | The git author's name. | -| `commits[][author][email]` | `строка` | 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` | `объект` | The user who pushed the commits. | +| Клавиша | Тип | Description | +| -------------------------- | --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `ref` | `строка` | The full [`git ref`](/rest/reference/git#refs) that was pushed. Example: `refs/heads/main` or `refs/tags/v3.14.1`. | +| `before` | `строка` | The SHA of the most recent commit on `ref` before the push. | +| `after` | `строка` | 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` | `объект` | 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` | `строка` | 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.) The array includes a maximum of 20 commits. If necessary, you can use the [Commits API](/rest/reference/repos#commits) to fetch additional commits. This limit is applied to timeline events only and isn't applied to webhook deliveries. | +| `commits[][id]` | `строка` | The SHA of the commit. | +| `commits[][timestamp]` | `строка` | The ISO 8601 timestamp of the commit. | +| `commits[][message]` | `строка` | The commit message. | +| `commits[][author]` | `объект` | The git author of the commit. | +| `commits[][author][name]` | `строка` | The git author's name. | +| `commits[][author][email]` | `строка` | 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` | `объект` | The user who pushed the commits. | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} diff --git a/translations/ru-RU/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md b/translations/ru-RU/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md index f8447149e6..1c89c573c4 100644 --- a/translations/ru-RU/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md +++ b/translations/ru-RU/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md @@ -53,7 +53,7 @@ You can share your feedback about {% data variables.product.prodname_discussions ## Дополнительная литература - "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)" -- "[Searching discussions](/github/searching-for-information-on-github/searching-discussions)" +- "[Searching discussions](/search-github/searching-on-github/searching-discussions)" - "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" - "[Moderating comments and conversations](/communities/moderating-comments-and-conversations)" - "[Maintaining your safety on {% data variables.product.prodname_dotcom %}](/communities/maintaining-your-safety-on-github)" diff --git a/translations/ru-RU/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md b/translations/ru-RU/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md index 8a8d3d5cc2..a1bf0446ff 100644 --- a/translations/ru-RU/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md +++ b/translations/ru-RU/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md @@ -2,7 +2,7 @@ title: Collaborating with maintainers using discussions shortTitle: Collaborating with maintainers intro: 'You can contribute to the goals, plans, health, and community for a project on {% data variables.product.product_name %} by communicating with the maintainers of the project in a discussion.' -permissions: People with read permissions to a repository can start and participate in discussions in the repository. +permissions: 'People with read access to a repository can start and participate in discussions in the repository. {% data reusables.enterprise-accounts.emu-permission-interact %}' versions: fpt: '*' --- @@ -32,7 +32,7 @@ To collaborate with maintainers in discussions, a repository administrator or pr ## Filtering the list of discussions -You can search for discussions and filter the list of discussions in a repository. For more information, see "[Searching discussions](/github/searching-for-information-on-github/searching-discussions)." +You can search for discussions and filter the list of discussions in a repository. For more information, see "[Searching discussions](/search-github/searching-on-github/searching-discussions)." {% data reusables.repositories.navigate-to-repo %} {% data reusables.discussions.discussions-tab %} diff --git a/translations/ru-RU/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md b/translations/ru-RU/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md index 580fe89146..829e9da23d 100644 --- a/translations/ru-RU/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md +++ b/translations/ru-RU/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md @@ -1,7 +1,7 @@ --- title: Participating in a discussion intro: 'You can converse with the community and maintainers in a forum within the repository for a project on {% data variables.product.product_name %}.' -permissions: People with read permissions to a repository can participate in discussions in the repository. +permissions: 'People with read access to a repository can participate in discussions in the repository. {% data reusables.enterprise-accounts.emu-permission-interact %}' versions: fpt: '*' shortTitle: Participate in discussion diff --git a/translations/ru-RU/content/discussions/guides/finding-discussions-across-multiple-repositories.md b/translations/ru-RU/content/discussions/guides/finding-discussions-across-multiple-repositories.md index 1bfcd5132d..7a26545665 100644 --- a/translations/ru-RU/content/discussions/guides/finding-discussions-across-multiple-repositories.md +++ b/translations/ru-RU/content/discussions/guides/finding-discussions-across-multiple-repositories.md @@ -15,6 +15,6 @@ shortTitle: Find discussions ## Дополнительная литература -- "[Searching discussions](/github/searching-for-information-on-github/searching-discussions)" +- "[Searching discussions](/search-github/searching-on-github/searching-discussions)" - "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)" - "[Managing discussions for your community](/discussions/managing-discussions-for-your-community)" diff --git a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md index e344378535..880bd40c10 100644 --- a/translations/ru-RU/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md +++ b/translations/ru-RU/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md @@ -8,12 +8,6 @@ redirect_from: shortTitle: Starter assignment --- -{% note %} - -**Note:** The Git & {% data variables.product.company_short %} starter assignment is in beta and subject to change. - -{% endnote %} - The Git & {% data variables.product.company_short %} starter assignment is a pre-made course that summarizes the basics of Git and {% data variables.product.company_short %} and links students to resources to learn more about specific topics. ## Требования diff --git a/translations/ru-RU/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md b/translations/ru-RU/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md index b8a76aa3d3..fd40db22e0 100644 --- a/translations/ru-RU/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md +++ b/translations/ru-RU/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md @@ -1,6 +1,7 @@ --- title: Finding ways to contribute to open source on GitHub intro: 'You can find ways to contribute to open source projects on {% data variables.product.product_name %} that are relevant to you.' +permissions: '{% data reusables.enterprise-accounts.emu-permission-interact %}' redirect_from: - /articles/where-can-i-find-open-source-projects-to-work-on/ - /articles/finding-interesting-projects-on-github/ @@ -19,7 +20,7 @@ shortTitle: Contribute to open source ## Discovering relevant projects -If there's a particular topic that interests you, visit `github.com/topics/`. For example, if you are interested in machine learning, you can find relevant projects and good first issues by visiting https://github.com/topics/machine-learning. You can browse popular topics by visiting [Topics](https://github.com/topics). You can also search for repositories that match a topic you're interested in. For more information, see "[Searching for repositories](/articles/searching-for-repositories#search-by-topic)." +If there's a particular topic that interests you, visit `github.com/topics/`. For example, if you are interested in machine learning, you can find relevant projects and good first issues by visiting https://github.com/topics/machine-learning. You can browse popular topics by visiting [Topics](https://github.com/topics). You can also search for repositories that match a topic you're interested in. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories#search-by-topic)." If you've been active on {% data variables.product.product_name %}, you can find personalized recommendations for projects and good first issues based on your past contributions, stars, and other activities in [Explore](https://github.com/explore). You can also sign up for the Explore newsletter to receive emails about opportunities to contribute to {% data variables.product.product_name %} based on your interests. To sign up, see [Explore email newsletter](https://github.com/explore/subscribe). diff --git a/translations/ru-RU/content/get-started/exploring-projects-on-github/following-people.md b/translations/ru-RU/content/get-started/exploring-projects-on-github/following-people.md index 700df1a9a1..a014f4c8d1 100644 --- a/translations/ru-RU/content/get-started/exploring-projects-on-github/following-people.md +++ b/translations/ru-RU/content/get-started/exploring-projects-on-github/following-people.md @@ -1,6 +1,7 @@ --- title: Following people intro: 'You can follow people on {% data variables.product.product_name %} to receive notifications about their activity{% ifversion fpt %} and discover projects in their communities{% endif %}.' +permissions: '{% data reusables.enterprise-accounts.emu-permission-follow %}' redirect_from: - /articles/following-people - /github/getting-started-with-github/following-people diff --git a/translations/ru-RU/content/get-started/getting-started-with-git/associating-text-editors-with-git.md b/translations/ru-RU/content/get-started/getting-started-with-git/associating-text-editors-with-git.md index 3c23a58a47..10e31d5038 100644 --- a/translations/ru-RU/content/get-started/getting-started-with-git/associating-text-editors-with-git.md +++ b/translations/ru-RU/content/get-started/getting-started-with-git/associating-text-editors-with-git.md @@ -61,6 +61,7 @@ shortTitle: Associate text editors ## Using Atom as your editor 1. Install [Atom](https://atom.io/). For more information, see "[Installing Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" in the Atom documentation. +{% data reusables.command_line.open_the_multi_os_terminal %} 3. Type this command: ```shell $ git config --global core.editor "atom --wait" diff --git a/translations/ru-RU/content/get-started/learning-about-github/access-permissions-on-github.md b/translations/ru-RU/content/get-started/learning-about-github/access-permissions-on-github.md index 6860b070d5..fb9634f0ab 100644 --- a/translations/ru-RU/content/get-started/learning-about-github/access-permissions-on-github.md +++ b/translations/ru-RU/content/get-started/learning-about-github/access-permissions-on-github.md @@ -36,6 +36,8 @@ Organization members can have *owner*{% ifversion fpt %}, *billing manager*,{% e *Enterprise owners* have ultimate power over the enterprise account and can take every action in the enterprise account. *Billing managers* can manage your enterprise account's billing settings. Members and outside collaborators of organizations owned by your enterprise account are automatically members of the enterprise account, although they have no access to the enterprise account itself or its settings. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise)." +If an enterprise uses {% data variables.product.prodname_emus %}, members are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and are fully managed by the identity provider. The {% data variables.product.prodname_managed_users %} have read-only access to repositories that are not a part of their enterprise and cannot interact with users that are not also members of the enterprise. Within the organizations owned by the enterprise, the {% data variables.product.prodname_managed_users %} can be granted the same granular access levels available for regular organizations. For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." + {% data reusables.gated-features.enterprise-accounts %} {% endif %} diff --git a/translations/ru-RU/content/get-started/learning-about-github/githubs-products.md b/translations/ru-RU/content/get-started/learning-about-github/githubs-products.md index b1699eb724..9a967a5ec4 100644 --- a/translations/ru-RU/content/get-started/learning-about-github/githubs-products.md +++ b/translations/ru-RU/content/get-started/learning-about-github/githubs-products.md @@ -102,6 +102,7 @@ In addition to the features available with {% data variables.product.prodname_te - 50GB {% data variables.product.prodname_registry %} storage - Access control for {% data variables.product.prodname_pages %} sites. For more information, see Changing the visibility of your {% data variables.product.prodname_pages %} site" - A service level agreement for 99.9% monthly uptime +- The option to configure your enterprise for {% data variables.product.prodname_emus %}, so you can provision and manage members with your identity provider and restrict your member's contributions to just your enterprise. For more information, see "About {% data variables.product.prodname_emus %}." - The option to centrally manage policy and billing for multiple {% data variables.product.prodname_dotcom_the_website %} organizations with an enterprise account. For more information, see "About enterprise accounts." You can set up a trial to evaluate {% data variables.product.prodname_ghe_cloud %}. For more information, see "Setting up a trial of {% data variables.product.prodname_ghe_cloud %}." diff --git a/translations/ru-RU/content/get-started/learning-about-github/types-of-github-accounts.md b/translations/ru-RU/content/get-started/learning-about-github/types-of-github-accounts.md index 009c026854..3073a15641 100644 --- a/translations/ru-RU/content/get-started/learning-about-github/types-of-github-accounts.md +++ b/translations/ru-RU/content/get-started/learning-about-github/types-of-github-accounts.md @@ -64,6 +64,14 @@ Every person who uses {% data variables.product.product_location %} has their ow {% endif %} +{% ifversion fpt %} +### {% data variables.product.prodname_emus %} + +With {% data variables.product.prodname_emus %}, instead of using your personal account, members of an {% data variables.product.prodname_emu_enterprise %} are provisioned accounts using the enterprise's identity provider (IdP). {% data variables.product.prodname_managed_users_caps %} authenticate using their IdP instead of a {% data variables.product.prodname_dotcom_the_website %} username and password. + +{% data variables.product.prodname_managed_users_caps %} can only interact with users, repositories, and organizations that are part of their enterprise. {% data variables.product.prodname_managed_users_caps %} have read-only access to the rest of {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." +{% endif %} + ## Organization accounts Organizations are shared accounts where groups of people can collaborate across many projects at once. Owners and administrators can manage member access to the organization's data and projects with sophisticated security and administrative features. diff --git a/translations/ru-RU/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md b/translations/ru-RU/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md index 67dc5449b4..57ece39a54 100644 --- a/translations/ru-RU/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md +++ b/translations/ru-RU/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md @@ -18,16 +18,19 @@ This guide will walk you through setting up, configuring and managing your {% da The main difference between the products is that {% data variables.product.prodname_ghe_cloud %} is hosted by {% data variables.product.prodname_dotcom %}, while {% data variables.product.prodname_ghe_server %} is self-hosted. -Within the {% data variables.product.prodname_ghe_cloud %} product, there are two different types of account that you can use: +With {% data variables.product.prodname_ghe_cloud %}, you have the option of using {% data variables.product.prodname_emus %}. {% data reusables.enterprise-accounts.emu-short-summary %} + +If you choose to let your members create and manage their own user accounts instead, there are two types of accounts you can use with {% data variables.product.prodname_ghe_cloud %}: - A single organization account - An enterprise account that contains multiple organizations -In either scenario, your users will use their own self-created user account and you'll invite them to join. ### 1. Understanding the differences between an organization account and enterprise account Both organization and enterprise accounts are available with {% data variables.product.prodname_ghe_cloud %}. An organization is a shared account where groups of people can collaborate across many projects at once, and owners and administrators can manage access to data and projects. An enterprise account enables collaboration between multiple organizations, and allows owners to centrally manage policy, billing and security for these organizations. For more information on the differences, see "[Organizations and enterprise accounts](/organizations/collaborating-with-groups-in-organizations/about-organizations#organizations-and-enterprise-accounts)." + + If you choose an enterprise account, keep in mind that some policies can be set only at an organization level, while others can be enforced for all organizations in an enterprise. Once you choose the account type you would like, you can proceed to setting up your account. In each of the sections in this guide, proceed to either the single organization or enterprise account section based on your account type. @@ -86,6 +89,11 @@ You can set permissions and member roles, create and manage teams, and give peop ### Managing members of an enterprise account Managing members of an enterprise is separate from managing members or teams in an organization. It is important to note that enterprise owners or administrators cannot access organization-level settings or manage members for organizations in their enterprise unless they are made an organization owner. For more information, see the above section, "[Managing members and teams in your organization](#managing-members-and-teams-in-your-organization)." + +If your enterprise uses {% data variables.product.prodname_emus %}, your members are fully managed through your identity provider. Adding members, making changes to their membership, and assigning roles is all managed using your IdP. For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." + +If your enterprise does not use {% data variables.product.prodname_emus %}, follow the steps below. + #### 1. Assigning roles in an enterprise By default, everyone in an enterprise is a member of the enterprise. There are also administrative roles, including enterprise owner and billing manager, that have different levels of access to enterprise settings and data. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)." #### 2. Inviting people to manage your enterprise @@ -97,6 +105,10 @@ To audit access to enterprise-owned resources or user license usage, you can vie ## Part 4: Managing security with {% data variables.product.prodname_ghe_cloud %} +* [Managing security for a single organization](#managing-security-for-a-single-organization) +* [Managing security for an {% data variables.product.prodname_emu_enterprise %}](#managing-security-for-an-enterprise-with-managed-users) +* [Managing security for an enterprise account without {% data variables.product.prodname_managed_users %}](#managing-security-for-an-enterprise-account-without-managed-users) + ### Managing security for a single organization You can help keep your organization secure by requiring two-factor authentication, configuring security features, reviewing your organization's audit log and integrations, and enabling SAML single sign-on and team synchronization. #### 1. Requiring two-factor authentication @@ -113,8 +125,28 @@ Organization owners can choose to disable, enable but not enforce, or enable and #### 5. Managing team synchronization for your organization Organization owners can enable team synchronization between your identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organization owners and team maintainers to connect teams in your organization with IdP groups. For more information, see "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)." -### Managing security for an enterprise account with multiple organizations +### Managing security for an {% data variables.product.prodname_emu_enterprise %} + +With {% data variables.product.prodname_emus %}, access and identity is managed centrally through your identity provider. Two-factor authentication and other login requirements should be enabled and enforced on your IdP. + +#### 1. Enabling and SAML single sign-on and provisioning in your {% data variables.product.prodname_emu_enterprise %} + +In an {% data variables.product.prodname_emu_enterprise %}, all members are provisioned and managed by your identity provider. You must enable SAML SSO and SCIM provisioning before you can start using your enterprise. For more information on configuring SAML SSO and provisioning for an {% data variables.product.prodname_emu_enterprise %}, see "[Configuring SAML single sign-on for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." + +#### 2. Managing teams in your {% data variables.product.prodname_emu_enterprise %} with your identity provider + +You can connect teams in your organizations to security groups in your identity provider, managing membership of your teams and access to repositories through your IdP. For more information, see "[Managing team memberships with identity provider groups](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)." + +#### 3. Managing allowed IP addresses for organizations in your {% data variables.product.prodname_emu_enterprise %} + +You can configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your {% data variables.product.prodname_emu_enterprise %}. For more information, see "[Enforcing security settings in your enterprise account](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-security-settings-in-your-enterprise-account#managing-allowed-ip-addresses-for-organizations-in-your-enterprise-account)." + +#### 4. Enforcing policies for Advanced Security features in your {% data variables.product.prodname_emu_enterprise %} +{% data reusables.getting-started.enterprise-advanced-security %} + +### Managing security for an enterprise account without {% data variables.product.prodname_managed_users %} To manage security for your enterprise, you can require two-factor authentication, manage allowed IP addresses, enable SAML single sign-on and team synchronization at an enterprise level, and sign up for and enforce GitHub Advanced Security features. + #### 1. Requiring two-factor authentication and managing allowed IP addresses for organizations in your enterprise account Enterprise owners can require that organization members, billing managers, and outside collaborators in all organizations owned by an enterprise account use two-factor authentication to secure their personal accounts. Before doing so, we recommend notifying all who have access to organizations in your enterprise. You can also configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account. @@ -126,7 +158,7 @@ You can centrally manage access to your enterprise's resources, organization mem You can enable and manage team sychronization between an identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organizations owned by your enterprise account to manage team membership with IdP groups. For more information, see "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/managing-team-synchronization-for-organizations-in-your-enterprise-account)." #### 4. Enforcing policies for Advanced Security features in your enterprise account -If you have a GitHub Advanced Security license for your enterprise account, you can enforce policies to manage {% data variables.product.prodname_dotcom %} Advanced Security features for organizations owned by an enterprise account. For more information, see "[Enforcing policies for Advanced Security in your enterprise account](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-policies-for-advanced-security-in-your-enterprise-account)." +{% data reusables.getting-started.enterprise-advanced-security %} ## Part 5: Managing organization and enterprise level policies and settings diff --git a/translations/ru-RU/content/get-started/quickstart/be-social.md b/translations/ru-RU/content/get-started/quickstart/be-social.md index e8b1926dec..4bc254fbc5 100644 --- a/translations/ru-RU/content/get-started/quickstart/be-social.md +++ b/translations/ru-RU/content/get-started/quickstart/be-social.md @@ -6,6 +6,7 @@ redirect_from: - /github/getting-started-with-github/be-social - /github/getting-started-with-github/quickstart/be-social intro: 'You can interact with people, repositories, and organizations on {% data variables.product.prodname_dotcom %}. See what others are working on and who they''re connecting with from your personal dashboard.' +permissions: '{% data reusables.enterprise-accounts.emu-permission-interact %}' versions: fpt: '*' ghes: '*' diff --git a/translations/ru-RU/content/get-started/quickstart/fork-a-repo.md b/translations/ru-RU/content/get-started/quickstart/fork-a-repo.md index 36b08e207f..190729c17f 100644 --- a/translations/ru-RU/content/get-started/quickstart/fork-a-repo.md +++ b/translations/ru-RU/content/get-started/quickstart/fork-a-repo.md @@ -7,6 +7,7 @@ redirect_from: - /github/getting-started-with-github/fork-a-repo - /github/getting-started-with-github/quickstart/fork-a-repo intro: A fork is a copy of a repository. Forking a repository allows you to freely experiment with changes without affecting the original project. +permissions: '{% data reusables.enterprise-accounts.emu-permission-fork %}' versions: fpt: '*' ghes: '*' diff --git a/translations/ru-RU/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md b/translations/ru-RU/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md index 9f810d4bac..742af385a6 100644 --- a/translations/ru-RU/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md +++ b/translations/ru-RU/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md @@ -18,7 +18,7 @@ shortTitle: Enterprise Server trial You can request a 45-day trial to evaluate {% data variables.product.prodname_ghe_server %}. Your trial will be installed as a virtual appliance, with options for on-premises or cloud deployment. For a list of supported visualization platforms, see "[Setting up a GitHub Enterprise Server instance](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance)." -{% ifversion ghes %}{% data variables.product.prodname_dependabot %}{% else %}Security{% endif %} alerts and {% data variables.product.prodname_github_connect %} are not currently available in trials of {% data variables.product.prodname_ghe_server %}. For a demonstration of these features, contact {% data variables.contact.contact_enterprise_sales %}. For more information about these features, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" and "[Connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)." +{% ifversion ghes %}{% data variables.product.prodname_dependabot %}{% else %}Security{% endif %} alerts and {% data variables.product.prodname_github_connect %} are not currently available in trials of {% data variables.product.prodname_ghe_server %}. For a demonstration of these features, contact {% data variables.contact.contact_enterprise_sales %}. For more information about these features, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" and "[Connecting your enterprise account to {% data variables.product.prodname_dotcom_the_website %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." Trials are also available for {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_cloud %}](/articles/setting-up-a-trial-of-github-enterprise-cloud)." diff --git a/translations/ru-RU/content/get-started/using-git/dealing-with-special-characters-in-branch-and-tag-names.md b/translations/ru-RU/content/get-started/using-git/dealing-with-special-characters-in-branch-and-tag-names.md new file mode 100644 index 0000000000..e8c3daae8b --- /dev/null +++ b/translations/ru-RU/content/get-started/using-git/dealing-with-special-characters-in-branch-and-tag-names.md @@ -0,0 +1,48 @@ +--- +title: Dealing with special characters in branch and tag names +intro: 'Git is very permissive about what characters are allowed in branch and tag names. When using Git from a command-line shell, you may need to escape or quote special characters.' +versions: + fpt: '*' + ghes: '*' + ghae: '*' +shortTitle: Special characters in names +--- + +## About branch and tag names + +Most repositories use simple branch names, such as `main` or `update-icons`. Tag names also usually follow a basic format, such as a version number like `v1.2.3`. Both branch names and tag names may also use the path separator (`/`) for structure, for example `area/item` or `level-1/level-2/level-3`. Other than some exceptions — such as not starting or ending a name with a slash, or having consecutive slashes in the name — Git has very few restrictions on what characters may be used in branch and tag names. For more information, see "[git-check-ref-format](https://git-scm.com/docs/git-check-ref-format)" in the Git documentation. + +## Why you need to escape special characters + +When using a CLI, you might have situations where a branch or tag name contains special characters that have a special meaning for your shell environment. To use these characters safely in a Git command, they must be quoted or escaped, otherwise the command may have unintended effects. + +For example, the `$` character is used by many shells to refer to a variable. Most shells would interpret a valid branch name like `hello-$USER` as equivalent to the word "hello", followed by a hyphen, followed by the current value of the `USER` variable, rather than the literal string `hello-$USER`. If a branch name includes the `$` character, then the shell must be stopped from expanding it as a variable reference. Similarly, if a branch name contains a semi-colon (`;`), most shells interpret it as a command separator, so it needs to be quoted or escaped. + +## How to escape special characters in branch and tag names + +Most branch and tag names with special characters can be handled by including the name in single quotes, for example `'hello-$USER'`. + +* In the [Bash](https://www.gnu.org/software/bash/) shell, enclosing a string of characters in single quotes preserves the literal value of the characters within the single quotes. +* [Zsh](https://www.zsh.org/) behaves similar to Bash, however this behavior is configurable using the `RC_QUOTES` option. +* [PowerShell](https://microsoft.com/powershell) also treats characters literally when inside single quotes. + +For these shells, the main exception is when the branch or tag name itself contains a single quote. In this case, you should consult the official documentation for your shell: + +* [Bash documentation](https://www.gnu.org/software/bash/manual/) +* [Zsh documentation](https://zsh.sourceforge.io/Doc/) +* [Fish documentation](https://fishshell.com/docs/current/) +* [PowerShell documentation](https://docs.microsoft.com/en-gb/powershell/) + +## Naming branches and tags + +If possible, create branch and tag names that don't contain special characters, as these would need to be escaped. A safe default set of characters to use for branch names and tag names is: + +* The English alphabet (`a` to `z` and `A` to `Z`) +* Numbers (`0` to `9`) +* A limited set of punctuation characters: + * period (`.`) + * hyphen (`-`) + * underscore (`_`) + * forward slash (`/`) + +To avoid confusion, you should start branch names with a letter. diff --git a/translations/ru-RU/content/get-started/using-git/index.md b/translations/ru-RU/content/get-started/using-git/index.md index 2a8e883ff4..27ece3b345 100644 --- a/translations/ru-RU/content/get-started/using-git/index.md +++ b/translations/ru-RU/content/get-started/using-git/index.md @@ -23,5 +23,6 @@ children: - /about-git-rebase - /using-git-rebase-on-the-command-line - /resolving-merge-conflicts-after-a-git-rebase + - /dealing-with-special-characters-in-branch-and-tag-names --- diff --git a/translations/ru-RU/content/get-started/using-github/keyboard-shortcuts.md b/translations/ru-RU/content/get-started/using-github/keyboard-shortcuts.md index 476a909905..649bcdaab9 100644 --- a/translations/ru-RU/content/get-started/using-github/keyboard-shortcuts.md +++ b/translations/ru-RU/content/get-started/using-github/keyboard-shortcuts.md @@ -24,7 +24,7 @@ Below is a list of some of the available keyboard shortcuts. | Keyboard shortcut | Description | | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| s or / | Сфокусировать панель поиска. For more information, see "[About searching on {% data variables.product.company_short %}](/articles/about-searching-on-github)." | +| s or / | Сфокусировать панель поиска. 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 %}"[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[About notifications](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}." | | esc | When focused on a user, issue, or pull request hovercard, closes the hovercard and refocuses on the element the hovercard is in | diff --git a/translations/ru-RU/content/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md b/translations/ru-RU/content/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md index 27389dc0df..6ee2aeb4fb 100644 --- a/translations/ru-RU/content/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md +++ b/translations/ru-RU/content/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md @@ -41,6 +41,12 @@ When _checks_ are set up in a repository, pull requests have a **Checks** tab wh ![Status checks within a pull request](/assets/images/help/pull_requests/checks.png) +{% note %} + +**Note:** The **Checks** tab only gets populated for pull requests if you set up _checks_, not _statuses_, for the repository. + +{% endnote %} + When a specific line in a commit causes a check to fail, you will see details about the failure, warning, or notice next to the relevant code in the **Files** tab of the pull request. ![Details of a status check](/assets/images/help/pull_requests/checks-detailed.png) diff --git a/translations/ru-RU/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork.md b/translations/ru-RU/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork.md index 7311c3daed..220ba398f3 100644 --- a/translations/ru-RU/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork.md +++ b/translations/ru-RU/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork.md @@ -5,7 +5,7 @@ redirect_from: - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork - /articles/creating-a-pull-request-from-a-fork - /github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork -permissions: Anyone with write access to a repository can create a pull request from a user-owned fork. +permissions: 'Anyone with write access to a repository can create a pull request from a user-owned fork. {% data reusables.enterprise-accounts.emu-permission-propose %}' versions: fpt: '*' ghes: '*' diff --git a/translations/ru-RU/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md b/translations/ru-RU/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md index e4fd62bfba..1a45b10b47 100644 --- a/translations/ru-RU/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md +++ b/translations/ru-RU/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md @@ -1,6 +1,7 @@ --- title: Creating a pull request intro: 'Create a pull request to propose and collaborate on changes to a repository. These changes are proposed in a *branch*, which ensures that the default branch only contains finished and approved work.' +permissions: 'Anyone with read access to a repository can create a pull request. {% data reusables.enterprise-accounts.emu-permission-propose %}' redirect_from: - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request - /articles/creating-a-pull-request @@ -13,7 +14,7 @@ topics: - Pull requests --- -Anyone with read permissions to a repository can create a pull request, but you must have write permissions to create a branch. If you want to create a new branch for your pull request and don't have write permissions to the repository, you can fork the repository first. For more information, see "[Creating a pull request from a fork](/articles/creating-a-pull-request-from-a-fork)" and "[About forks](/articles/about-forks)." +If you want to create a new branch for your pull request and do not have write permissions to the repository, you can fork the repository first. For more information, see "[Creating a pull request from a fork](/articles/creating-a-pull-request-from-a-fork)" and "[About forks](/articles/about-forks)." You can specify which branch you'd like to merge your changes into when you create your pull request. Pull requests can only be opened between two branches that are different. diff --git a/translations/ru-RU/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/translations/ru-RU/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md index 2a3b4db14d..f294666a47 100644 --- a/translations/ru-RU/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md +++ b/translations/ru-RU/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md @@ -1,10 +1,10 @@ --- title: Reviewing dependency changes in a pull request intro: 'If a pull request contains changes to dependencies, you can view a summary of what has changed and whether there are known vulnerabilities in any of the dependencies.' +product: '{% data reusables.gated-features.dependency-review %}' versions: fpt: '*' ghes: '>= 3.2' - product: '{% data reusables.gated-features.dependency-review %}' type: how_to topics: - Pull requests @@ -38,19 +38,19 @@ Dependency review allows you to "shift left". You can use the provided predictiv 1. If the pull request contains many files, use the **File filter** drop-down menu to collapse all files that don't record dependencies. This will make it easier to focus your review on the dependency changes. - ![The file filter menu](/assets/images/help/pull_requests/file-filter-menu-json.png) + ![The file filter menu](/assets/images/help/pull_requests/file-filter-menu-json.png) The dependency review provides a clearer view of what has changed in large lock files, where the source diff is not rendered by default. + + {% note %} + + **Note:** Dependency review rich diffs are not available for committed static JavaScript files like `jquery.js`. + + {% endnote %} 1. On the right of the header for a manifest or lock file, display the dependency review by clicking the **{% octicon "file" aria-label="The rich diff icon" %}** rich diff button. ![The rich diff button](/assets/images/help/pull_requests/dependency-review-rich-diff.png) - {% note %} - - **Note:** The dependency review provides a clearer view of what has changed in large lock files, where the source diff is not rendered by default. - - {% endnote %} - -1. Check the dependencies listed in the dependency review. +2. Check the dependencies listed in the dependency review. ![Vulnerability warnings in a dependency review](/assets/images/help/pull_requests/dependency-review-vulnerability.png) diff --git a/translations/ru-RU/content/github/collaborating-with-pull-requests/working-with-forks/about-forks.md b/translations/ru-RU/content/github/collaborating-with-pull-requests/working-with-forks/about-forks.md index ae156dbbb8..a2e17f376e 100644 --- a/translations/ru-RU/content/github/collaborating-with-pull-requests/working-with-forks/about-forks.md +++ b/translations/ru-RU/content/github/collaborating-with-pull-requests/working-with-forks/about-forks.md @@ -20,6 +20,12 @@ Forking a repository is similar to copying a repository, with two major differen {% data reusables.repositories.you-can-fork %} +{% ifversion fpt %} + +If you're a member of a {% data variables.product.prodname_emu_enterprise %}, there are further restrictions on the repositories you can fork. {% data reusables.enterprise-accounts.emu-forks %} For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." + +{% endif %} + {% data reusables.repositories.desktop-fork %} Deleting a fork will not delete the original upstream repository. You can make any changes you want to your fork—add collaborators, rename files, generate {% data variables.product.prodname_pages %}—with no effect on the original.{% ifversion fpt %} You cannot restore a deleted forked repository. For more information, see "[Restoring a deleted repository](/articles/restoring-a-deleted-repository)."{% endif %} diff --git a/translations/ru-RU/content/github/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md b/translations/ru-RU/content/github/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md index 82ab74b446..36788dc021 100644 --- a/translations/ru-RU/content/github/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md +++ b/translations/ru-RU/content/github/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md @@ -52,4 +52,4 @@ If your local Git configuration contained a generic email address, or an email a ## Дополнительная литература -* "[Searching commits](/articles/searching-commits)" +* "[Searching commits](/search-github/searching-on-github/searching-commits)" diff --git a/translations/ru-RU/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views.md b/translations/ru-RU/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views.md index 184a9c0f89..17b3aeb6a9 100644 --- a/translations/ru-RU/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views.md +++ b/translations/ru-RU/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views.md @@ -29,4 +29,4 @@ For more information on how Git considers commit history, see [the "History Simp ## Дополнительная литература - "[Signing commits](/articles/signing-commits)" -- "[Searching commits](/articles/searching-commits)" +- "[Searching commits](/search-github/searching-on-github/searching-commits)" diff --git a/translations/ru-RU/content/github/copilot/about-github-copilot-telemetry.md b/translations/ru-RU/content/github/copilot/about-github-copilot-telemetry.md index 989263e8e0..7139ed503e 100644 --- a/translations/ru-RU/content/github/copilot/about-github-copilot-telemetry.md +++ b/translations/ru-RU/content/github/copilot/about-github-copilot-telemetry.md @@ -1,6 +1,6 @@ --- title: About GitHub Copilot telemetry -intro: '{% data variables.product.prodname_dotcom %} Copilot collects and relies on additional telemetry data beyond what other {% data variables.product.prodname_dotcom %} products and services collect.' +intro: '{% data variables.product.prodname_copilot %} collects and relies on additional telemetry data beyond what other {% data variables.product.company_short %} products and services collect.' redirect_from: - /early-access/github/copilot/about-github-copilot-telemetry versions: @@ -8,36 +8,21 @@ versions: --- ## What data is collected -The {% data variables.product.prodname_dotcom %} Copilot collects activity from the user’s Visual Studio Code editor, tied to a timestamp, and metadata. This metadata consists of the extension settings and the standard metadata collected by the [Visual Studio Code extension telemetry package](https://www.npmjs.com/package/vscode-extension-telemetry): -* Visual Studio Code machine ID (pseudonymized identifier) -* Visual Studio Code session ID (pseudonymized identifier) -* Visual Studio Code version -* [Geolocation from IP address](https://docs.microsoft.com/en-us/azure/azure-monitor/app/ip-collection?tabs=net) (country, state/province and city, but not the IP address itself) -* Operating system and version -* Extension version -* The VS Code UI (web or desktop) +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. -The activity collected consists of events that are triggered when: +## How the data is used by {% data variables.product.company_short %} -* An error occurs (it records the error kind and relevant background; e.g. if it’s an authentication error the key expiry date is recorded) -* Our models are accessed to ask for code suggestions (it records editor state like position of cursor and snippets of code)—this includes cases when the user takes an action to request code suggestions -* Code suggestions are received or displayed (it records the suggestions, post-processing, and metadata like model certainty and latency) -* Code suggestions are redacted due to filters that ensure AI safety -* The user acts on code suggestions (e.g. to accept or reject them) -* The user has acted on code suggestions and then it records whether or how they persisted in the code +{% data variables.product.company_short %} will use this data for: -## How the data is used -This data will only be used by {% data variables.product.company_short %} for: - -* Directly improving the product, including assessing different strategies in processing and predicting which suggestions users may find helpful -* Directly evaluating the product, e.g. by measuring the positive impact it has on the user -* Improving the underlying code generation models, e.g. by providing positive and negative examples (but always so that your private code is not used as input to suggest code for other users of {% data variables.product.prodname_dotcom %} Copilot) -* Guiding closely related {% data variables.product.prodname_dotcom %} products -* Investigating and detecting potential abuse of the {% data variables.product.prodname_dotcom %} Copilot service -* Other purposes related to improving the {% data variables.product.prodname_dotcom %} Copilot service +- Directly improving the product, including assessing different strategies in processing and predicting which suggestions users may find helpful +- Evaluating the product, e.g. by measuring the positive impact it has on the user +- Improving the underlying code generation models, e.g. by providing positive and negative examples (but always so that your private code is not used as input to suggest code for other users of {% data variables.product.prodname_copilot %}) +- Guiding closely related {% data variables.product.company_short %} products +- Investigating and detecting potential abuse of the {% data variables.product.prodname_copilot %} service +- Other purposes related to improving the {% data variables.product.prodname_copilot %} service, including sharing as described in the next section ## How the data is shared -The telemetry data is stored securely on {% data variables.product.prodname_dotcom %} systems, with appropriate encryption in place. -We know user edit actions and source code snippets are very sensitive data, and access is strictly controlled. The data can only be accessed by (1) named {% data variables.product.company_short %} personnel (employees and contractors) working on the {% data variables.product.company_short %} Copilot team or on the {% data variables.product.company_short %} platform health team, (2) select Microsoft personnel (employees and contractors) working on or with the {% data variables.product.company_short %} Copilot team, and (3) select employees of OpenAI who work on {% data variables.product.company_short %} Copilot. +The telemetry data is stored securely on {% data variables.product.company_short %} systems, with appropriate encryption in place. We know user edit actions, source code snippets, and URLs of repositories and file paths are sensitive data. Consequently, access is strictly controlled. The data can only be accessed by (1) named {% data variables.product.company_short %} personnel (employees and contractors) working on the {% data variables.product.prodname_copilot %} team or on the {% data variables.product.company_short %} platform health team, (2) Microsoft personnel (employees and contractors) working on or with the Azure and/or {% data variables.product.prodname_copilot %} teams, and (3) employees of OpenAI who work on {% data variables.product.prodname_copilot %}. + diff --git a/translations/ru-RU/content/github/copilot/github-copilot-telemetry-terms.md b/translations/ru-RU/content/github/copilot/github-copilot-telemetry-terms.md new file mode 100644 index 0000000000..6e178850e6 --- /dev/null +++ b/translations/ru-RU/content/github/copilot/github-copilot-telemetry-terms.md @@ -0,0 +1,16 @@ +--- +title: GitHub Copilot Telemetry Terms +intro: 'Acceptance of the additional telemetry described below is a condition to joining the wait list for the technical preview of {% data variables.product.prodname_copilot %} and using {% data variables.product.prodname_copilot %} during the technical preview.' +redirect_from: + - /early-access/github/copilot/telemetry-terms + - /github/copilot/telemetry-terms +versions: + fpt: '*' +--- + +## Additional telemetry + +If you use {% data variables.product.prodname_copilot %}, the {% data variables.product.prodname_copilot %} extension/plugin will collect usage information about events generated by interacting with the integrated development environment (IDE). These events include {% data variables.product.prodname_copilot %} performance, features used, and suggestions accepted, modified and accepted, or dismissed. This information may include personal data, including your User Personal Information, as defined in the [GitHub Privacy Statement](/github/site-policy/github-privacy-statement). + +This usage information is used by {% data variables.product.company_short %}, and shared with Microsoft and OpenAI, to develop and improve the extension/plugin and related products. OpenAI also uses this usage information to perform other services related to {% data variables.product.prodname_copilot %}. For example, when you edit files with the {% data variables.product.prodname_copilot %} extension/plugin enabled, file content snippets, suggestions, and any modifications to suggestions will be shared with {% data variables.product.company_short %}, Microsoft, and OpenAI, and used for diagnostic purposes to improve suggestions and related products. {% data variables.product.prodname_copilot %} relies on file content for context, both in the file you are editing and potentially other files open in the same IDE instance. When you are using {% data variables.product.prodname_copilot %}, it may also collect the URLs of repositories or file paths for relevant files. {% data variables.product.prodname_copilot %} does not use these URLs, file paths, or snippets collected in your telemetry as input to suggest code for other users of {% data variables.product.prodname_copilot %}. This information is treated as confidential information and accessed on a need-to-know basis. You are prohibited from collecting telemetry data about other users of {% data variables.product.prodname_copilot %} from the {% data variables.product.prodname_copilot %} extension/plugin. For more details about {% data variables.product.prodname_copilot %} telemetry, please see "[About {% data variables.product.prodname_copilot %} telemetry](/github/copilot/about-github-copilot-telemetry)." You may revoke your consent to the telemetry and personal data processing operations described in this paragraph by contacting GitHub and requesting removal from the technical preview. + diff --git a/translations/ru-RU/content/github/copilot/index.md b/translations/ru-RU/content/github/copilot/index.md index ef5fc94524..bc5bc35075 100644 --- a/translations/ru-RU/content/github/copilot/index.md +++ b/translations/ru-RU/content/github/copilot/index.md @@ -5,7 +5,7 @@ versions: fpt: '*' children: - /about-github-copilot-telemetry - - /telemetry-terms + - /github-copilot-telemetry-terms - /research-recitation --- diff --git a/translations/ru-RU/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md b/translations/ru-RU/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md index 5e6b94425a..cae3d72a6e 100644 --- a/translations/ru-RU/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md +++ b/translations/ru-RU/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md @@ -16,7 +16,7 @@ You may also have the option to select a free 14-day trial on some tools. You ca ## Finding tools on {% data variables.product.prodname_marketplace %} -You can discover, browse, and install apps and actions created by others on {% data variables.product.prodname_marketplace %}, see "[Searching {% data variables.product.prodname_marketplace %}](/github/searching-for-information-on-github/searching-github-marketplace)." +You can discover, browse, and install apps and actions created by others on {% data variables.product.prodname_marketplace %}, see "[Searching {% data variables.product.prodname_marketplace %}](/search-github/searching-on-github/searching-github-marketplace)." {% data reusables.actions.actions-not-verified %} diff --git a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning/sarif-support-for-code-scanning.md b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning/sarif-support-for-code-scanning.md index 19687f42e9..b155030ae2 100644 --- a/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning/sarif-support-for-code-scanning.md +++ b/translations/ru-RU/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning/sarif-support-for-code-scanning.md @@ -31,7 +31,7 @@ If you're new to SARIF and want to learn more, see Microsoft's [`SARIF tutorials Each time the results of a new code scan are uploaded, the results are processed and alerts are added to the repository. To prevent duplicate alerts for the same problem, {% data variables.product.prodname_code_scanning %} uses fingerprints to match results across various runs so they only appear once in the latest run for the selected branch. This makes it possible to match alerts to the right line of code when files are edited. -{% data variables.product.prodname_dotcom %} uses the `partialFingerprints` property in the OASIS standard to detect when two results are logically identical. For more information, see the "[partialFingerprints property](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012611)" entry in the OASIS documentation. +{% data variables.product.prodname_dotcom %} uses the `partialFingerprints` property in the OASIS standard as an input in the computation of whether two results are logically identical. Specifically, the `primaryLocationLineHash` is used as a stable intra-file location, which is combined with the repository, file path, and rule data to form the full identity. For more information, see the "[partialFingerprints property](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012611)" entry in the OASIS documentation. SARIF files created by the {% data variables.product.prodname_codeql_workflow %} or using the {% data variables.product.prodname_codeql_runner %} include fingerprint data. If you upload a SARIF file using the `upload-sarif` action and this data is missing, {% data variables.product.prodname_dotcom %} attempts to populate the `partialFingerprints` field from the source files. For more information about uploading results, see "[Uploading a SARIF file to {% data variables.product.prodname_dotcom %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github#uploading-a-code-scanning-analysis-with-github-actions)." @@ -89,17 +89,17 @@ Any valid SARIF 2.1.0 output file can be uploaded, however, {% data variables.pr {% data reusables.code-scanning.upload-sarif-alert-limit %} -| Name | Description | -| --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `ruleId` | **Optional.** The unique identifier of the rule (`reportingDescriptor.id`). For more information, see the [`reportingDescriptor` object](#reportingdescriptor-object). {% data variables.product.prodname_code_scanning_capc %} uses the rule identifier to filter results by rule on {% data variables.product.prodname_dotcom %}. | -| `ruleIndex` | **Optional.** The index of the associated rule (`reportingDescriptor` object) in the tool component `rules` array. For more information, see the [`run` object](#run-object). | -| `rule` | **Optional.** A reference used to locate the rule (reporting descriptor) for this result. For more information, see the [`reportingDescriptor` object](#reportingdescriptor-object). | -| `level` | **Optional.** The severity of the result. This level overrides the default severity defined by the rule. {% data variables.product.prodname_code_scanning_capc %} uses the level to filter results by severity on {% data variables.product.prodname_dotcom %}. | -| `message.text` | **Required.** A message that describes the result. {% data variables.product.prodname_code_scanning_capc %} displays the message text as the title of the result. Only the first sentence of the message will be displayed when visible space is limited. | -| `locations[]` | **Required.** The set of locations where the result was detected up to a maximum of 10. Only one location should be included unless the problem can only be corrected by making a change at every specified location. **Note:** At least one location is required for {% data variables.product.prodname_code_scanning %} to display a result. {% data variables.product.prodname_code_scanning_capc %} will use this property to decide which file to annotate with the result. Only the first value of this array is used. All other values are ignored. | -| `partialFingerprints` | **Required.** A set of strings used to track the unique identity of the result. {% data variables.product.prodname_code_scanning_capc %} uses `partialFingerprints` to accurately identify which results are the same across commits and branches. {% data variables.product.prodname_code_scanning_capc %} will attempt to use `partialFingerprints` if they exist. If you are uploading third-party SARIF files with the `upload-action`, the action will create `partialFingerprints` for you when they are not included in the SARIF file. For more information, see "[Preventing duplicate alerts using fingerprints](#preventing-duplicate-alerts-using-fingerprints)." **Note:** {% data variables.product.prodname_code_scanning_capc %} only uses the `primaryLocationLineHash`. | -| `codeFlows[].threadFlows[].locations[]` | **Optional.** An array of `location` objects for a `threadFlow` object, which describes the progress of a program through a thread of execution. A `codeFlow` object describes a pattern of code execution used to detect a result. If code flows are provided, {% data variables.product.prodname_code_scanning %} will expand code flows on {% data variables.product.prodname_dotcom %} for the relevant result. For more information, see the [`location` object](#location-object). | -| `relatedLocations[]` | A set of locations relevant to this result. {% data variables.product.prodname_code_scanning_capc %} will link to related locations when they are embedded in the result message. For more information, see the [`location` object](#location-object). | +| Name | Description | +| --------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `ruleId` | **Optional.** The unique identifier of the rule (`reportingDescriptor.id`). For more information, see the [`reportingDescriptor` object](#reportingdescriptor-object). {% data variables.product.prodname_code_scanning_capc %} uses the rule identifier to filter results by rule on {% data variables.product.prodname_dotcom %}. | +| `ruleIndex` | **Optional.** The index of the associated rule (`reportingDescriptor` object) in the tool component `rules` array. For more information, see the [`run` object](#run-object). | +| `rule` | **Optional.** A reference used to locate the rule (reporting descriptor) for this result. For more information, see the [`reportingDescriptor` object](#reportingdescriptor-object). | +| `level` | **Optional.** The severity of the result. This level overrides the default severity defined by the rule. {% data variables.product.prodname_code_scanning_capc %} uses the level to filter results by severity on {% data variables.product.prodname_dotcom %}. | +| `message.text` | **Required.** A message that describes the result. {% data variables.product.prodname_code_scanning_capc %} displays the message text as the title of the result. Only the first sentence of the message will be displayed when visible space is limited. | +| `locations[]` | **Required.** The set of locations where the result was detected up to a maximum of 10. Only one location should be included unless the problem can only be corrected by making a change at every specified location. **Note:** At least one location is required for {% data variables.product.prodname_code_scanning %} to display a result. {% data variables.product.prodname_code_scanning_capc %} will use this property to decide which file to annotate with the result. Only the first value of this array is used. All other values are ignored. | +| `partialFingerprints` | **Required.** A set of strings used to track the unique identity of the result. {% data variables.product.prodname_code_scanning_capc %} uses `partialFingerprints` as part of the computation to accurately identify which results are the same across commits and branches. {% data variables.product.prodname_code_scanning_capc %} will attempt to use `partialFingerprints` if they exist. If you are uploading third-party SARIF files with the `upload-action`, the action will create `partialFingerprints` for you when they are not included in the SARIF file. For more information, see "[Preventing duplicate alerts using fingerprints](#preventing-duplicate-alerts-using-fingerprints)." **Note:** {% data variables.product.prodname_code_scanning_capc %} only uses the `primaryLocationLineHash`. | +| `codeFlows[].threadFlows[].locations[]` | **Optional.** An array of `location` objects for a `threadFlow` object, which describes the progress of a program through a thread of execution. A `codeFlow` object describes a pattern of code execution used to detect a result. If code flows are provided, {% data variables.product.prodname_code_scanning %} will expand code flows on {% data variables.product.prodname_dotcom %} for the relevant result. For more information, see the [`location` object](#location-object). | +| `relatedLocations[]` | A set of locations relevant to this result. {% data variables.product.prodname_code_scanning_capc %} will link to related locations when they are embedded in the result message. For more information, see the [`location` object](#location-object). | ### `location` object diff --git a/translations/ru-RU/content/github/index.md b/translations/ru-RU/content/github/index.md index 151b7b550b..28b87c4f27 100644 --- a/translations/ru-RU/content/github/index.md +++ b/translations/ru-RU/content/github/index.md @@ -15,7 +15,6 @@ children: - /writing-on-github - /committing-changes-to-your-project - /collaborating-with-pull-requests - - /searching-for-information-on-github - /importing-your-projects-to-github - /managing-security-vulnerabilities - /finding-security-vulnerabilities-and-errors-in-your-code diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/about-identity-and-access-management-for-your-enterprise-account.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/about-identity-and-access-management-for-your-enterprise-account.md index 3dfe3805c2..bba82a799b 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/about-identity-and-access-management-for-your-enterprise-account.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/about-identity-and-access-management-for-your-enterprise-account.md @@ -21,6 +21,12 @@ If you use Azure AD as your IDP, you can use team synchronization to manage team {% data reusables.saml.switching-from-org-to-enterprise %} For more information, see "[Switching your SAML configuration from an organization to an enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)." +## About {% data variables.product.prodname_emus %} + +{% data reusables.enterprise-accounts.emu-short-summary %} + +Configuring {% data variables.product.prodname_emus %} for SAML single-sign on and user provisioning involves following a different process than you would for an enterprise that isn't using {% data variables.product.prodname_managed_users %}. If your enterprise uses {% data variables.product.prodname_emus %}, see "[Configuring SAML single sign-on for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." + ## Supported IdPs We test and officially support the following IdPs. For SAML SSO, we offer limited support for all identity providers that implement the SAML 2.0 standard. For more information, see the [SAML Wiki](https://wiki.oasis-open.org/security) on the OASIS website. @@ -31,5 +37,4 @@ We test and officially support the following IdPs. For SAML SSO, we offer limite | Azure Active Directory (Azure AD) | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label="The check icon" %} | OneLogin | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | PingOne | {% octicon "check-circle-fill" aria-label="The check icon" %} | | -| Shibboleth | {% octicon "check-circle-fill" aria-label="The check icon" %} | | - +| Shibboleth | {% octicon "check-circle-fill" aria-label="The check icon" %} | | \ No newline at end of file diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/configuring-saml-single-sign-on-for-your-enterprise-account-using-okta.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/configuring-saml-single-sign-on-for-your-enterprise-account-using-okta.md index f1f798715b..afa743a2d8 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/configuring-saml-single-sign-on-for-your-enterprise-account-using-okta.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/configuring-saml-single-sign-on-for-your-enterprise-account-using-okta.md @@ -16,6 +16,8 @@ shortTitle: Configure SAML with Okta {% data reusables.enterprise-accounts.user-provisioning-release-stage %} +{% data reusables.enterprise-accounts.emu-saml-note %} + ## About SAML with Okta You can control access to your enterprise account in {% data variables.product.product_name %} and other web applications from one central interface by configuring the enterprise account to use SAML SSO with Okta, an Identity Provider (IdP). diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account.md index e694f812ac..1ee39c4a68 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account.md @@ -13,6 +13,8 @@ redirect_from: shortTitle: Enforce SAML --- +{% data reusables.enterprise-accounts.emu-saml-note %} + ## About SAML single sign-on for enterprise accounts {% data reusables.saml.dotcom-saml-explanation %} 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)." diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/managing-team-synchronization-for-organizations-in-your-enterprise-account.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/managing-team-synchronization-for-organizations-in-your-enterprise-account.md index 244348225c..f7596fad1d 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/managing-team-synchronization-for-organizations-in-your-enterprise-account.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/managing-team-synchronization-for-organizations-in-your-enterprise-account.md @@ -12,6 +12,8 @@ redirect_from: shortTitle: Manage team synchronization --- +{% data reusables.enterprise-accounts.emu-scim-note %} + ## About team synchronization for enterprise accounts If you use Azure AD as your IdP, you can enable team synchronization for your enterprise account to allow organization owners and team maintainers to synchronize teams in the organizations owned by your enterprise accounts with IdP groups. diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md index 3ee8d6a055..a8e829d94d 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md @@ -10,6 +10,8 @@ topics: shortTitle: Switching from organization --- +{% data reusables.enterprise-accounts.emu-saml-note %} + ## About SAML single sign-on for enterprise accounts {% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %} diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/index.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/index.md index 12012356e5..8d939d4737 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/index.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/index.md @@ -14,6 +14,7 @@ topics: children: - /managing-your-enterprise-account - /managing-users-in-your-enterprise + - /managing-your-enterprise-users-with-your-identity-provider - /managing-organizations-in-your-enterprise-account - /configuring-identity-and-access-management-for-your-enterprise-account - /setting-policies-for-organizations-in-your-enterprise-account diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account.md index e12d66ea3d..3f96297990 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account.md @@ -1,6 +1,6 @@ --- title: Adding organizations to your enterprise account -intro: You can create new organizations to manage within your enterprise account. +intro: You can create new organizations or invite existing organizations to manage within your enterprise account. product: '{% data reusables.gated-features.enterprise-accounts %}' redirect_from: - /articles/adding-organizations-to-your-enterprise-account @@ -13,9 +13,9 @@ topics: shortTitle: Add organizations --- -Enterprise owners can create new organizations within an enterprise account's settings. +Enterprise owners can create new organizations within an enterprise account's settings or invite existing organizations to join an enterprise account. -To add an organization to your enterprise account, you must create the organization from within the enterprise account settings. If you want to transfer an existing organization to your enterprise account, contact your {% data variables.product.prodname_dotcom %} sales account representative. +To add an organization to your enterprise account, you must create the organization from within the enterprise account settings. ## Creating an organization in your enterprise account @@ -29,3 +29,15 @@ Enterprise owners who create an organization owned by the enterprise account aut 4. Click **Create organization**. 5. Under "Invite owners", type the username of a person you'd like to invite to become an organization owner, then click **Invite**. ![Organization owner search field and Invite button](/assets/images/help/business-accounts/invite-org-owner.png) 6. Click **Finish**. + +## Inviting an organization to join your enterprise account + +Enterprise owners can invite existing organizations to join their enterprise account. If the organization you want to invite is already owned by another enterprise, you will not be able to issue an invitation until the previous enterprise gives up ownership of the organization. + +{% data reusables.enterprise-accounts.access-enterprise %} +2. On the **Organizations** tab, above the list of organizations, click **Invite organization**. ![Invite organization](/assets/images/help/business-accounts/enterprise-account-invite-organization.png) +3. Under "Organization name", start typing the name of the organization you want to invite and select it when it appears in the drop-down list. ![Search for organization](/assets/images/help/business-accounts/enterprise-account-search-for-organization.png) +4. Click **Invite organization**. +5. The organization owners will receive an email inviting them to join the organization. At least one owner needs to accept the invitation before the process can continue. You can cancel or resend the invitation at any time before an owner approves it. ![Cancel or resend](/assets/images/help/business-accounts/enterprise-account-invitation-sent.png) +6. Once an organization owner has approved the invitation, you can view its status in the list of pending invitations. ![Pending invitation](/assets/images/help/business-accounts/enterprise-account-pending.png) +7. Click **Approve** to complete the transfer, or **Cancel** to cancel it. ![Approve invitation](/assets/images/help/business-accounts/enterprise-account-transfer-approve.png) diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md index 065e4892bf..8b435c9f38 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md @@ -28,6 +28,12 @@ If you want to manage owners and billing managers for an enterprise account on { {% endif %} +{% ifversion fpt %} + +If your enterprise uses {% data variables.product.prodname_emus %}, enterprise owners can only be added or removed through your identity provider. For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." + +{% endif %} + {% tip %} **Tip:** For more information on managing users within an organization owned by your enterprise account, see "[Managing membership in your organization](/articles/managing-membership-in-your-organization)" and "[Managing people's access to your organization with roles](/articles/managing-peoples-access-to-your-organization-with-roles)." diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise.md index d84b79432b..b92b3bd3a2 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise.md @@ -21,7 +21,14 @@ Everyone in an enterprise is a member of the enterprise. You can also assign adm {% data reusables.enterprise-accounts.enterprise-administrators %} -For more information about adding people to your enterprise, see "{% ifversion fpt %}[Inviting people to manage your enterprise](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise){% else %}[Authentication](/admin/authentication){% endif %}". +{% ifversion fpt %} +If your enterprise does not use {% data variables.product.prodname_emus %}, you can invite someone to an administrative role using a user account on {% data variables.product.product_name %} that they control. For more information, see "[Inviting people to manage your enterprise](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)". + +In an enterprise using {% data variables.product.prodname_emus %}, new owners and members must be provisioned through your identity provider. Enterprise owners and organization owners cannot add new members or owners to the enterprise using {% data variables.product.prodname_dotcom %}. You can select a member's enterprise role using your IdP and it cannot be changed on {% data variables.product.prodname_dotcom %}. You can select a member's role in an organization on {% data variables.product.prodname_dotcom %}. For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." +{% else %} +For more information about adding people to your enterprise, see "[Authentication](/admin/authentication)". + +{% endif %} ## Enterprise owner diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md index b5ee8e8c65..ef0052a060 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md @@ -18,18 +18,13 @@ shortTitle: View & manage SAML access When you enable SAML single sign-on for your enterprise account, each enterprise member can link their external identity on your identity provider (IdP) to their existing {% data variables.product.product_name %} account. {% data reusables.saml.about-saml-access-enterprise-account %} +If your enterprise is uses {% data variables.product.prodname_emus %}, your members will use accounts provisioned through your IdP. {% data variables.product.prodname_managed_users_caps %} will not use their existing user account on {% data variables.product.product_name %}. For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." + ## Viewing and revoking a linked identity {% data reusables.saml.about-linked-identities %} -{% warning %} - -**Warning:** For organizations using SCIM: -- Revoking a linked user identity on {% data variables.product.product_name %} will also remove the SAML and SCIM metadata. As a result, the identity provider will not be able to synchronize or deprovision the linked user identity. -- An admin must revoke a linked identity through the identity provider. -- To revoke a linked identity and link a different account through the identity provider, an admin can remove and re-assign the user to the {% data variables.product.product_name %} application. For more information, see your identity provider's docs. - -{% endwarning %} +If your enterprise uses {% data variables.product.prodname_emus %}, you will not be able to deprovision or remove user accounts from the enterprise on {% data variables.product.product_name %}. Any changes you need to make to your enterprise's {% data variables.product.prodname_managed_users %} should be made through your IdP. {% data reusables.identity-and-permissions.revoking-identity-team-sync %} diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md new file mode 100644 index 0000000000..40d84c367d --- /dev/null +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md @@ -0,0 +1,84 @@ +--- +title: About Enterprise Managed Users +shortTitle: About managed users +intro: You can centrally manage identity and access for your enterprise members on {% data variables.product.prodname_dotcom %} from your identity provider. +product: '{% data reusables.gated-features.emus %}' +redirect_from: + - /early-access/github/articles/get-started-with-managed-users-for-your-enterprise +versions: + fpt: '*' +topics: + - Accounts + - Enterprise +--- + +## About {% data variables.product.prodname_emus %} + +With {% data variables.product.prodname_emus %}, you can control the user accounts of your enterprise members through your identity provider (IdP). You can simplify authentication with SAML single sign-on (SSO) and provision, update, and deprovision user accounts for your enterprise members. Users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your IdP are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and added to your enterprise. You control usernames, profile data, team membership, and repository access from your IdP. + +In your IdP, you can give each {% data variables.product.prodname_managed_user %} the role of user, enterprise owner, or billing manager. {% data variables.product.prodname_managed_users_caps %} can own organizations within your enterprise and can add other {% data variables.product.prodname_managed_users %} to the organizations and teams within. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" and "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)." + +You can also manage team membership within an organization in your enterprise directly through your IdP, allowing you to manage repository access using groups in your IdP. Organization membership can be managed manually or updated automatically as {% data variables.product.prodname_managed_users %} are added to teams within the organization. For more information, see "[Managing team memberships with identity provider groups](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)." + +You can grant {% data variables.product.prodname_managed_users %} access and the ability to contribute to repositories within your enterprise, but {% data variables.product.prodname_managed_users %} cannot create public content or collaborate with other users, organizations, and enterprises on the rest of {% data variables.product.prodname_dotcom %}. The {% data variables.product.prodname_managed_users %} provisioned for your enterprise cannot be invited to organizations or repositories outside of the enterprise, nor can the {% data variables.product.prodname_managed_users %} be invited to other enterprises. Outside collaborators are not supported by {% data variables.product.prodname_emus %}. + +The usernames of your enterprise's {% data variables.product.prodname_managed_users %} and their profile information, such as display names and email addresses, are set by through your IdP and cannot be changed by the users themselves. For more information, see "[Usernames and profile information](#usernames-and-profile-information)." + +{% data reusables.enterprise-accounts.emu-forks %} + +Enterprise owners can audit all of the {% data variables.product.prodname_managed_users %}' actions on {% data variables.product.prodname_dotcom %}. + +To use {% data variables.product.prodname_emus %}, you need a separate type of enterprise account with {% data variables.product.prodname_emus %} enabled. For more information about creating this account, see "[About enterprises with managed users](#about-enterprises-with-managed-users)." + + +## Identity provider support + +{% data variables.product.prodname_emus %} supports the following IdPs: + +{% data reusables.enterprise-accounts.emu-supported-idps %} + +## Abilities and restrictions of {% data variables.product.prodname_managed_users %} + +{% data variables.product.prodname_managed_users_caps %} can only contribute to private and internal repositories within their enterprise and private repositories owned by their user account. {% data variables.product.prodname_managed_users_caps %} have read-only access to the wider {% data variables.product.prodname_dotcom %} community. + +* {% data variables.product.prodname_managed_users_caps %} cannot create issues or pull requests in, comment or add reactions to, nor star, watch, or fork repositories outside of the enterprise. +* {% data variables.product.prodname_managed_users_caps %} cannot push code to repositories outside of the enterprise. +* {% data variables.product.prodname_managed_users_caps %} and the content they create is only visible to other members of the enterprise. +* {% data variables.product.prodname_managed_users_caps %} cannot follow users outside of the enterprise. +* {% data variables.product.prodname_managed_users_caps %} cannot create gists or comment on gists. +* {% data variables.product.prodname_managed_users_caps %} cannot install {% data variables.product.prodname_github_apps %} on their user accounts. +* Other {% data variables.product.prodname_dotcom %} users cannot see, mention, or invite a {% data variables.product.prodname_managed_user %} to collaborate. +* {% data variables.product.prodname_managed_users_caps %} can only own private repositories and {% data variables.product.prodname_managed_users %} can only invite other enterprise members to collaborate on their owned repositories. +* Only private and internal repositories can be created in organizations owned by an {% data variables.product.prodname_emu_enterprise %}, depending on organization and enterprise repository visibility settings. + +## About enterprises with managed users + +To use {% data variables.product.prodname_emus %}, you need a separate type of enterprise account with {% data variables.product.prodname_emus %} enabled. To try out {% data variables.product.prodname_emus %} or to discuss options for migrating from your existing enterprise, please contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact). + +Your contact on the GitHub Sales team will work with you to create your new {% data variables.product.prodname_emu_enterprise %}. You'll need to provide the email address for the user who will set up your enterprise and a short code that will be used as the suffix for your enterprise members' usernames. {% data reusables.enterprise-accounts.emu-shortcode %} For more information, see "[Usernames and profile information](#usernames-and-profile-information)." + +After we create your enterprise, you will receive an email from {% data variables.product.prodname_dotcom %} inviting you to choose a password for your enterprise's setup user, which will be the first owner in the enterprise. The setup user is only used to configure SAML single sign-on and SCIM provisioning integration for the enterprise. It will no longer have access to administer the enterprise account once SAML is successfully enabled. + +The setup user's username is your enterprise's shortcode suffixed with `_admin`. After you log in to your setup user, you can get started by configuring SAML SSO for your enterprise. For more information, see "[Configuring SAML single sign-on for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." + +{% note %} + +{% data reusables.enterprise-accounts.emu-password-reset-session %} + +{% endnote %} + +## Authenticating as a {% data variables.product.prodname_managed_user %} + +{% data variables.product.prodname_managed_users_caps %} must authenticate through their identity provider. + +To authenticate, {% data variables.product.prodname_managed_users %} must visit their IdP application portal or **https://github.com/enterprises/ENTERPRISE_NAME**, replacing **ENTERPRISE_NAME** with your enterprise's name. + +## Usernames and profile information + +When your {% data variables.product.prodname_emu_enterprise %} is created, you will choose a short code that will be used as the suffix for your enterprise member's usernames. {% data reusables.enterprise-accounts.emu-shortcode %} The setup user who configures SAML SSO has a username in the format of **@SHORT-CODE_admin**. + +When you provision a new user from your identity provider, the new {% data variables.product.prodname_managed_user %} will have a {% data variables.product.product_name %} username in the format of **@IDP-USERNAME_SHORT-CODE**. When using Azure Active Directory (Azure AD), _IDP-USERNAME_ is formed by normalizing the characters preceding the `@` character in the UPN (User Principal Name) provided by Azure AD. When using Okta, _IDP-USERNAME_ is the normalized username attribute provided by Okta. + +The username of the new account provisioned on {% data variables.product.product_name %}, including underscore and short code, must not exceed 39 characters. + +The profile name and email address of a {% data variables.product.prodname_managed_user %} is also provided by the IdP. {% data variables.product.prodname_managed_users_caps %} cannot change their profile name or email address on {% data variables.product.prodname_dotcom %}. \ No newline at end of file diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/auditing-activity-in-your-enterprise.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/auditing-activity-in-your-enterprise.md new file mode 100644 index 0000000000..1d93fa2a72 --- /dev/null +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/auditing-activity-in-your-enterprise.md @@ -0,0 +1,32 @@ +--- +title: Auditing activity in your enterprise +shortTitle: Auditing activity +intro: 'You can audit the activity of the {% data variables.product.prodname_managed_users %} in your enterprise, viewing information about what actions were performed, by which user, and when they took place.' +permissions: 'Enterprise owners can access the audit log.' +product: '{% data reusables.gated-features.emus %}' +versions: + fpt: '*' +topics: + - Accounts + - Enterprise +--- + +## About the audit log + +The audit log allows enterprise owners to quickly review or export the actions performed by both owners and members of your enterprise. Each audit log entry shows information about the event. + +- The organization an action was performed in +- The user who performed the action +- Which repository an action was performed in +- The action that was performed +- Which country the action took place in +- The date and time the action occurred + +## Accessing the audit log + +You can also access the audit log for your enterprise from the REST API. For more information, see "[GitHub Enterprise administration](/rest/reference/enterprise-admin#get-the-audit-log-for-an-enterprise)" in the API documentation. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.audit-log-tab %} +1. Optionally, above the list of events, select the **Export Git Events** or **Export** drop-down menu and choose options for exporting events from the audit log. !["Export Git Events" and "Export" drop-down menus for the enterprise audit log](/assets/images/help/enterprises/audit-log-export-drop-down-menus.png) diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users.md new file mode 100644 index 0000000000..9d26a3e084 --- /dev/null +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users.md @@ -0,0 +1,109 @@ +--- +title: Configuring SAML single sign-on for Enterprise Managed Users +shortTitle: SAML for managed users +intro: 'You can automatically manage access to your enterprise account on {% data variables.product.prodname_dotcom %} by configuring Security Assertion Markup Language (SAML) single sign-on (SSO).' +product: '{% data reusables.gated-features.emus %}' +versions: + fpt: '*' +topics: + - Accounts + - Enterprise +--- + +## About SAML single sign-on for {% data variables.product.prodname_emus %} + +With {% data variables.product.prodname_emus %}, your enterprise uses SAML SSO to authenticate all members. Instead of signing in to {% data variables.product.prodname_dotcom %} with a {% data variables.product.prodname_dotcom %} username and password, members of your enterprise will sign in through your IdP. + +{% data variables.product.prodname_emus %} supports the following IdPs: + +{% data reusables.enterprise-accounts.emu-supported-idps %} + +After you configure SAML SSO, we recommend storing your recovery codes so you can recover access to your enterprise in the event that your identity provider is unavailable. For more information, see "[Saving your recovery codes](#saving-your-recovery-codes)." + +## Configuring SAML single sign-on for {% data variables.product.prodname_emus %} + +To configure SAML SSO for your {% data variables.product.prodname_emu_enterprise %}, you must configure an application on your IdP and then configure your enterprise on GitHub.com. After you configure SAML SSO, you can configure user provisioning. + +To install and configure the {% data variables.product.prodname_emu_idp_application %} application on your IdP, you must have a tenant and administrative access on a supported IdP. + +{% note %} + +{% data reusables.enterprise-accounts.emu-password-reset-session %} + +{% endnote %} + +1. [Configuring your identity provider](#configuring-your-identity-provider) +2. [Configuring your enterprise](#configuring-your-enterprise) +3. [Enabling provisioning](#enabling-provisioning) + +### Configuring your identity provider + +To configure your IdP, follow the instructions they provide for configuring the {% data variables.product.prodname_emu_idp_application %} application on your IdP. + +1. To install the {% data variables.product.prodname_emu_idp_application %} application, click the link for your IdP below: + + - [{% data variables.product.prodname_emu_idp_application %} application on Azure Active Directory](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/aad.githubenterprisemanageduser?tab=Overview) + - [{% data variables.product.prodname_emu_idp_application %} application on Okta](https://www.okta.com/integrations/github-enterprise-managed-user) + +1. To configure the {% data variables.product.prodname_emu_idp_application %} application and your IdP, click the link below and follow the instructions provided by your IdP: + + - [Azure Active Directory tutorial for {% data variables.product.prodname_emus %}](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-enterprise-managed-user-tutorial) + - [Okta documentation for {% data variables.product.prodname_emus %}](https://saml-doc.okta.com/SAML_Docs/How-to-Configure-SAML-2.0-for-GitHub-Enterprise-Managed-User.html) + +1. So you can test and configure your enterprise, assign yourself or the user that will be configuring SAML SSO on {% data variables.product.prodname_dotcom %} to the {% data variables.product.prodname_emu_idp_application %} application on your IdP. + +1. To enable you to continue configuring your enterprise on {% data variables.product.prodname_dotcom %}, locate and note the following information from the application you installed on your IdP: + + | Value | Other names | Description | + |:----------------------------------- |:------------------ |:---------------------------------------------------------------- | + | IdP Sign-On URL | Login URL, IdP URL | Application's URL on your IdP | + | IdP Identifier URL | Issuer | IdP's identifier to service providers for SAML authentication | + | Signing certificate, Base64-encoded | Public certificate | Public certificate that IdP uses to sign authentication requests | + +### Configuring your enterprise + +After you install and configure the {% data variables.product.prodname_emu_idp_application %} application on your identity provider, you can configure your enterprise. + +1. Sign into {% data variables.product.prodname_dotcom_the_website %} as the setup user for your new enterprise with the username **@SHORT-CODE_admin**. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} + +1. Under "SAML single sign-on", select **Require SAML authentication**. ![Checkbox for enabling SAML SSO](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) + +1. Under **Sign on URL**, type the HTTPS endpoint of your IdP for single sign-on requests that you noted while configuring your IdP. ![Field for the URL that members will be forwarded to when signing in](/assets/images/help/saml/saml_sign_on_url_business.png) + +1. Under **Issuer**, type your SAML issuer URL that you noted while configuring your IdP, to verify the authenticity of sent messages. ![Field for the SAML issuer's name](/assets/images/help/saml/saml_issuer.png) + +1. Under **Public Certificate**, paste the certificate that you noted while configuring your IdP, to verify SAML responses. ![Field for the public certificate from your identity provider](/assets/images/help/saml/saml_public_certificate.png) + +1. To verify the integrity of the requests from your SAML issuer, click {% octicon "pencil" aria-label="The edit icon" %}. Then, in the "Signature Method" and "Digest Method" drop-downs, choose the hashing algorithm used by your SAML issuer. ![Drop-downs for the Signature Method and Digest method hashing algorithms used by your SAML issuer](/assets/images/help/saml/saml_hashing_method.png) + +1. Before enabling SAML SSO for your enterprise, to ensure that the information you've entered is correct, click **Test SAML configuration**. ![Button to test SAML configuration before enforcing](/assets/images/help/saml/saml_test.png) + +1. Click **Save**. + + {% note %} + + **Note:** When you require SAML SSO for your enterprise, the setup user will no longer have access to the enterprise but will remain signed in to GitHub. Only {% data variables.product.prodname_managed_users %} provisioned by your IdP will have access to the enterprise. + + {% endnote %} + +1. To ensure you can still access your enterprise in the event that your identity provider is ever unavailable in the future, click **Download**, **Print**, or **Copy** to save your recovery codes. ![Button to test SAML configuration before enforcing](/assets/images/help/saml/saml_recovery_code_options.png) + +### Enabling provisioning + +After you enable SAML SSO, enable provisioning. For more information, see "[Configuring SCIM provisioning for enterprise managed users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users)." + +## Saving your recovery codes + +In the event that your identity provider is unavailable, you can use the setup user and a recovery code to sign in and access your enterprise. If you did not save your recovery codes when you configured SAML SSO, you can still access them from your enterprise's settings. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} + +1. Under "Require SAML authentication", click **Save your recovery codes**. ![Button to test SAML configuration before enforcing](/assets/images/help/enterprises/saml-recovery-codes-link.png) + +2. To save your recovery codes, click **Download**, **Print**, or **Copy**. ![Button to test SAML configuration before enforcing](/assets/images/help/saml/saml_recovery_code_options.png) diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md new file mode 100644 index 0000000000..d12f9dc843 --- /dev/null +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md @@ -0,0 +1,76 @@ +--- +title: Configuring SCIM provisioning for Enterprise Managed Users with Okta +shortTitle: Set up provisioning with Okta +intro: You can provision new users and manage their membership of your enterprise and teams using Okta as your identity provider. +product: '{% data reusables.gated-features.emus %}' +versions: + fpt: '*' +redirect_from: + - /early-access/github/articles/configuring-provisioning-for-managed-users-with-okta +topics: + - Accounts + - Enterprise +--- + +## About provisioning with Okta + +You can use {% data variables.product.prodname_emus %} with Okta as your identity provider to provision new accounts, manage enterprise membership, and manage team memberships for organizations in your enterprise. For more information about provisioning for {% data variables.product.prodname_emus %}, see "[Configuring SCIM provisioning for enterprise managed users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users)." + +Before you can configure provisioning with Okta, you must configure SAML single-sign on. For more information, see "[Configuring SAML single sign-on for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." + +To configure provisioning with Okta, you must set your enterprise's name in the {% data variables.product.prodname_emu_idp_application %} application and enter your setup user's personal access token. You can then start provisioning users in Okta. + +## Supported features + +{% data variables.product.prodname_emus %} supports many provisioning features in Okta. + +| Feature | Description | +| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Push New Users | Users that are assigned to the {% data variables.product.prodname_emu_idp_application %} application in Okta are automatically created in the enterprise on {% data variables.product.product_name %}. | +| Push Profile Update | Updates made to the user's profile in Okta will be pushed to {% data variables.product.product_name %}. | +| Push Groups | Groups in Okta that are assigned to the {% data variables.product.prodname_emu_idp_application %} application as Push Groups are automatically created in the enterprise on {% data variables.product.product_name %}. | +| Push User Deactivation | Unassigning the user from the {% data variables.product.prodname_emu_idp_application %} application in Okta will disable the user on {% data variables.product.product_name %}. The user will not be able to sign in, but the user's information is maintained. | +| Reactivate Users | Users in Okta whose Okta accounts are reactivated and who are assigned back to the {% data variables.product.prodname_emu_idp_application %} application will be enabled. | + +{% note %} + +**Note:** {% data variables.product.prodname_emus %} does not support modifications to usernames. + +{% endnote %} + +## Setting your enterprise name + +After your {% data variables.product.prodname_emu_enterprise %} has been created, you can begin to configure provisioning by setting your enterprise name in Okta. + +1. Navigate to your {% data variables.product.prodname_emu_idp_application %} application on Okta. +1. Click the **Sign On** tab. +1. To make changes, click **Edit**. +1. Under "Advanced Sign-on Settings", in the "Enterprise Name" text box, type your enterprise name. For example, if you access your enterprise at `https://github.com/enterprises/octoinc`, your enterprise name would be "octoinc". ![Screenshot of the Enterprise Name field on Okta](/assets/images/help/enterprises/okta-emu-enterprise-name.png) +1. To save your enterprise name, click **Save**. + +## Configuring provisioning + +After setting your enterprise name, you can proceed to configure provisioning settings. + +To configure provisioning, the setup user with the **@SHORT-CODE_admin** username will need to provide a personal access token with the **admin:enterprise** scope. For more information on creating a new token, see "[Creating a personal access token](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users#creating-a-personal-access-token)." + +1. Navigate to your {% data variables.product.prodname_emu_idp_application %} application on Okta. +1. Click the **Provisioning** tab. +1. In the settings menu, click **Integration**. +1. To make changes, click **Edit**. +1. Select **Enable API integration**. +1. In the "API Token" field, enter the personal access token with the **admin:enterprise** scope belonging to the setup user. ![Screenshot showing the API Token field on Okta](/assets/images/help/enterprises/okta-emu-token.png) +1. Click **Test API Credentials**. If the test is successful, a verification message will appear at the top of the screen. +1. To save the token, click **Save**. +1. In the settings menu, click **To App**. ![Screenshot showing the To App menu item on Okta](/assets/images/help/enterprises/okta-emu-to-app-menu.png) +1. To the right of "Provisioning to App", to allow changes to be made, click **Edit**. +1. Select **Enable** for **Create Users**, **Update User Attributes**, and **Deactivate Users**. ![Screenshot showing provisioning options on Okta](/assets/images/help/enterprises/okta-emu-provisioning-to-app.png) +1. To finish configuring provisioning, click **Save**. + +## Assigning users + +After you have configured SAML SSO and provisioning, you will be able provision new users on {% data variables.product.prodname_dotcom_the_website %} by assigning users to the {% data variables.product.prodname_emu_idp_application %} application. You can also automatically manage organization membership by assigning groups to the application as push groups and connecting the push groups to teams in your organizations. For more information about managing teams, see "[Managing team memberships with identity provider groups](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)." + +When assigning users, you can use the "Roles" attribute in the {% data variables.product.prodname_emu_idp_application %} application to set a user's role in your enterprise on {% data variables.product.product_name %}. For more information on roles, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)." + +![Screenshot showing the role options for provisioned user on Okta](/assets/images/help/enterprises/okta-emu-user-role.png) diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md new file mode 100644 index 0000000000..d8bd284a20 --- /dev/null +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md @@ -0,0 +1,54 @@ +--- +title: Configuring SCIM provisioning for Enterprise Managed Users +shortTitle: Provisioning managed users +intro: You can configure your identity provider to provision new users and manage their membership in your enterprise and teams. +product: '{% data reusables.gated-features.emus %}' +versions: + fpt: '*' +topics: + - Accounts + - Enterprise +--- + +## About provisioning for {% data variables.product.prodname_emus %} + +You can configure provisioning for {% data variables.product.prodname_emus %} to create, manage, and deactivate user accounts for your enterprise members. When you configure provisioning for {% data variables.product.prodname_emus %}, users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your identity provider are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} via SCIM, and the users are added to your enterprise. + +When you update information associated with a user's identity on your IdP, your IdP will update the user's account on GitHub.com. When you unassign the user from the {% data variables.product.prodname_emu_idp_application %} application or deactivate a user's account on your IdP, your IdP will communicate with {% data variables.product.prodname_dotcom %} to invalidate any SAML sessions and disable the member's account. The disabled account's information is maintained and their username is changed to a hash of their original username with the short code appended. If you reassign a user to the {% data variables.product.prodname_emu_idp_application %} application or reactivate their account on your IdP, the {% data variables.product.prodname_managed_user %} account on {% data variables.product.prodname_dotcom %} will be reactivated and username restored. + +Groups in your IdP can be used to manage team membership within your enterprise's organizations, allowing you to configure repository access and permissions through your IdP. For more information, see "[Managing team memberships with identity provider groups](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)." + +## Требования + +Before you can configure provisioning for {% data variables.product.prodname_emus %}, you must configure SAML single-sign on. For more information, see "[Configuring SAML single sign-on for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." + +## Creating a personal access token + +To configure provisioning for your {% data variables.product.prodname_emu_enterprise %}, you need a personal access token with the **admin:enterprise** scope that belongs to the setup user. + +{% warning %} + +**Warning:** If the token expires or a provisioned user creates the token, SCIM provisioning may unexpectedly stop working. Make sure that you create the token while signed in as the setup user and that the token expiration is set to "No expiration". + +{% endwarning %} + +1. Sign into {% data variables.product.prodname_dotcom_the_website %} as the setup user for your new enterprise with the username **@SHORT-CODE_admin**. +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.developer_settings %} +{% data reusables.user_settings.personal_access_tokens %} +{% data reusables.user_settings.generate_new_token %} +1. Under **Note**, give your token a descriptive name. ![Screenshot showing the token's name](/assets/images/help/enterprises/emu-pat-name.png) +1. Select the **Expiration** drop-down menu, then click **No expiration**. ![Screenshot showing token expiration set to no expiration](/assets/images/help/enterprises/emu-pat-no-expiration.png) +1. Select the **admin:enterprise** scope. ![Screenshot showing the admin:enterprise scope](/assets/images/help/enterprises/enterprise-pat-scope.png) +1. Click **Generate token**. ![Generate token button](/assets/images/help/settings/generate_token.png) +1. To copy the token to your clipboard, click the {% octicon "paste" aria-label="The copy icon" %}. ![Newly created token](/assets/images/help/settings/personal_access_tokens.png) +2. To save the token for use later, store the new token securely in a password manager. + +## Configuring provisioning for {% data variables.product.prodname_emus %} + +After creating your personal access token and storing it securely, you can configure provisioning on your identity provider. + +To configure Azure Active Directory to provision users for your {% data variables.product.prodname_emu_enterprise %}, see [Tutorial: Configure GitHub Enterprise Managed User for automatic user provisioning](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-enterprise-managed-user-provisioning-tutorial) in the Azure AD documentation. + +To configure Okta to provision users for your {% data variables.product.prodname_emu_enterprise %}, see "[Configuring SCIM provisioning for Enterprise Managed Users with Okta](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users-with-okta)." + diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/index.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/index.md new file mode 100644 index 0000000000..7104779c1f --- /dev/null +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/index.md @@ -0,0 +1,19 @@ +--- +title: Managing your enterprise users with your identity provider +shortTitle: Manage users with your IdP +product: '{% data reusables.gated-features.emus %}' +intro: 'You can manage identity and access with your identity provider and provision accounts that can only contribute to your enterprise.' +versions: + fpt: '*' +topics: + - Enterprise + - Accounts +children: + - /about-enterprise-managed-users + - /configuring-saml-single-sign-on-for-enterprise-managed-users + - /configuring-scim-provisioning-for-enterprise-managed-users + - /configuring-scim-provisioning-for-enterprise-managed-users-with-okta + - /managing-team-memberships-with-identity-provider-groups + - /auditing-activity-in-your-enterprise +--- + diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups.md new file mode 100644 index 0000000000..0b75da0895 --- /dev/null +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups.md @@ -0,0 +1,67 @@ +--- +title: Managing team memberships with identity provider groups +shortTitle: Manage teams with your IdP +intro: You can manage team membership on {% data variables.product.product_name %} through your identity provider (IdP) by connecting IdP groups with your {% data variables.product.prodname_emu_enterprise %}. +product: '{% data reusables.gated-features.emus %}' +versions: + fpt: '*' +topics: + - Accounts + - Enterprise +--- + +## About team management with {% data variables.product.prodname_emus %} + +With {% data variables.product.prodname_emus %}, you can manage team membership within your enterprise through your IdP. When you connect a team in one of your enterprise's organizations to an IdP group, changes to membership from the IdP group are reflected in your enterprise automatically, reducing the need for manual updates and custom scripts. + +When a change to an IdP group or a new team connection results in a {% data variables.product.prodname_managed_user %} joining a team in an organization they were not already a member of, the {% data variables.product.prodname_managed_user %} will automatically be added to the organization. Organization owners can also manage organization membership manually. When you disconnect a group from a team, users who became members of the organization via team membership are removed from the organization if they are not assigned membership in the organization by any other means. + +You can connect a team in your enterprise to one IdP group. You can assign the same IdP group to multiple teams in your enterprise. + +If you are connecting an existing team to an IdP group, you must first remove any members that were added manually. After you connect a team in your enterprise to an IdP group, your IdP administrator must make team membership changes through the identity provider. You cannot manage team membership on {% data variables.product.prodname_dotcom_the_website %}. + +When group membership changes on your IdP, your IdP sends a SCIM request with the changes to {% data variables.product.prodname_dotcom_the_website %} according to the schedule determined by your IdP, so change may not be immediate. Any requests that change team or organization membership will register in the audit log as changes made by the account used to configure user provisioning. + +Teams connected to IdP groups cannot be parents of other teams nor a child of another team. If the team you want to connect to an IdP group is a parent or child team, we recommend creating a new team or removing the nested relationships that make your team a parent team. + +To manage repository access for any team in your enterprise, including teams connected to an IdP group, you must make changes on {% data variables.product.prodname_dotcom_the_website %}. 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)". + +## Creating a new team connected to an IdP group + +Any member of an organization can create a new team and connect the team to an IdP group. + +{% data reusables.profile.access_org %} +{% data reusables.user_settings.access_org %} +{% data reusables.organizations.new_team %} +{% data reusables.organizations.team_name %} +{% data reusables.organizations.team_description %} +1. To connect a team, select the "Identity Provider Groups" drop-down menu and click the team you want to connect. ![Drop-down menu to choose identity provider groups](/assets/images/help/teams/choose-an-idp-group.png) +{% data reusables.organizations.team_visibility %} +{% data reusables.organizations.create_team %} + +## Managing the connection between an existing team and an IdP group + +Organization owners and team maintainers can manage the existing connection between an IdP group and a team. + +{% note %} + +**Note**: Before you connect an existing team on {% data variables.product.prodname_dotcom_the_website %} to an IdP group for the first time, all members of the team on {% data variables.product.prodname_dotcom_the_website %} must first be removed. For more information, see "[Removing organization members from a team](/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team)." + +{% endnote %} + +{% data reusables.profile.access_profile %} + +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +1. Optionally, under "Identity Provider Group", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="X symbol" %}. ![Unselect a connected IdP group from the GitHub team](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png) +1. To connect an IdP group, under "Identity Provider Group", select the drop-down menu, and click an identity provider group from the list. ![Drop-down menu to choose identity provider group](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png) +1. Click **Save changes**. + +## Viewing IdP groups and connected teams + +You can review a list of IdP groups, any teams connected to an IdP group, and see the membership of each IdP group on {% data variables.product.product_name %}. You must edit the membership for a group on your IdP. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.identity-provider-tab %} +1. Under "Identity Provider (IdP) Groups", review the list of IdP groups. \ No newline at end of file diff --git a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account.md b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account.md index 0fda15faba..d60de68953 100644 --- a/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account.md +++ b/translations/ru-RU/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account.md @@ -42,7 +42,9 @@ You can disable all workflows for an enterprise or set a policy that configures ## Configuring required approval for workflows from public forks -{% data reusables.actions.workflow-run-approve-public-fork %} You can configure this behavior for your enterprise using the procedure below. +{% data reusables.actions.workflow-run-approve-public-fork %} + +You can configure this behavior for your enterprise using the procedure below. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} diff --git a/translations/ru-RU/content/github/site-policy/github-data-protection-agreement.md b/translations/ru-RU/content/github/site-policy/github-data-protection-agreement.md new file mode 100644 index 0000000000..1b3d668d96 --- /dev/null +++ b/translations/ru-RU/content/github/site-policy/github-data-protection-agreement.md @@ -0,0 +1,974 @@ +--- +title: GitHub Data Protection Agreement +redirect_from: + - /github/site-policy/github-data-protection-addendum + - /github/site-policy-deprecated/github-data-protection-addendum + - /github/site-policy/github-data-protection-agreement-non-enterprise-customers +versions: + fpt: '*' +--- + +## Introduction + +The parties agree that this GitHub Data Protection Agreement (“**DPA**”) sets forth their obligations with respect to the processing and security of Personal Data and, where explicitly stated in the DPA Terms, Customer Data in connection with the Online Services provided by GitHub, Inc. (“**GitHub**”). The DPA (including its Appendix and Attachments) is between GitHub and any customer receiving Online Services from GitHub based on the GitHub Customer Agreement (“**Customer**”), and is incorporated by reference into the GitHub Customer Agreement. + +In the event of any conflict or inconsistency between the DPA Terms and any other terms in the GitHub Customer Agreement, the DPA Terms will prevail. The provisions of the DPA Terms supersede any conflicting provisions of the GitHub Privacy Statement that otherwise may apply to processing of Personal Data. For clarity, the Standard Contractual Clauses prevail over any other term of the DPA Terms. + +### Applicable DPA Terms and Updates + +#### Limits on Updates + +When Customer renews or purchases a new subscription to an Online Service, the then-current DPA Terms will apply and will not change during the term of that new subscription for that Online Service. + +#### New Features, Supplements, or Related Software + +Notwithstanding the foregoing limits on updates, when GitHub introduces features, supplements or related software that are new (i.e., that were not previously included with the subscription), GitHub may provide terms or make updates to the DPA that apply to Customer’s use of those new features, supplements or related software. If those terms include any material adverse changes to the DPA Terms, GitHub will provide Customer a choice to use the new features, supplements, or related software, without loss of existing functionality of a generally available Online Service. If Customer does not use the new features, supplements, or related software, the corresponding new terms will not apply. + +#### Government Regulation and Requirements + +Notwithstanding the foregoing limits on updates, GitHub may modify or terminate an Online Service in any country or jurisdiction where there is any current or future government requirement or obligation that (1) subjects GitHub to any regulation or requirement not generally applicable to businesses operating there, (2) presents a hardship for GitHub to continue operating the Online Service without modification, and/or (3) causes GitHub to believe the DPA Terms or the Online Service may conflict with any such requirement or obligation. + +### Electronic Notices + +GitHub may provide Customer with information and notices about Online Services electronically, including via email, or through a web site that GitHub identifies. Notice is given as of the date it is made available by GitHub. + +### Prior Versions + +The DPA Terms provide terms for Online Services that are currently available. For earlier versions of the DPA Terms, Customer may contact its reseller or GitHub Account Manager. + +## Определения + +Capitalized terms used but not defined in this DPA will have the meanings provided in the GitHub Customer Agreement. The following defined terms are used in this DPA: + +“**CCPA**” means the California Consumer Privacy Act as set forth in Cal. Civ. Code §1798.100 et seq. and its implementing regulations. + +“**Customer Data**” means all data, including all text, sound, video, or image files, and software, that are provided to GitHub by, or on behalf of, Customer through use of the Online Service. + +“**Data Protection Requirements**” means the GDPR, Local EU/EEA Data Protection Laws, CCPA, and any applicable laws, regulations, and other legal requirements relating to (a) privacy and data security; and (b) the use, collection, retention, storage, security, disclosure, transfer, disposal, and other processing of any Personal Data. + +“**Diagnostic Data**” means data collected or obtained by GitHub from software that is locally installed by Customer in connection with the Online Service. Diagnostic Data may also be referred to as telemetry. Diagnostic Data does not include Customer Data, Service Generated Data, or Professional Services Data. + +“**DPA Terms**” means both the terms in this DPA and any Online Service-specific terms in the GitHub Customer Agreement that specifically supplement or modify the privacy and security terms in this DPA for a specific Online Service (or feature of an Online Service). In the event of any conflict or inconsistency between the DPA and such Online Service-specific terms, the Online Service-specific terms shall prevail as to the applicable Online Service (or feature of that Online Service). + +“**GDPR**” means Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation). In connection with the United Kingdom, “GDPR” means Regulation (EU) 2016/679 as transposed into national law of the United Kingdom by the UK European Union (Withdrawal) Act 2018 and amended by the UK Data Protection, Privacy and Electronic Communications (Amendments etc.) (EU Exit) Regulations 2019 (as may be amended from time to time). + +“**Local EU/EEA Data Protection Laws**” means any subordinate legislation and regulation implementing the GDPR. + +“**GDPR Related Terms**” means the terms in Attachment 3, under which GitHub makes binding commitments regarding its processing of Personal Data as required by Article 28 of the GDPR. + +“**GitHub Affiliate**” means any entity that directly or indirectly controls, is controlled by or is under common control with GitHub. + +“**GitHub Customer Agreement**” means the service or other agreement(s) entered into by Customer with GitHub for Online Services. + +“**GitHub Privacy Statement**” means the GitHub privacy statement available at https://docs.github.com/en/github/site-policy/github-privacy-statement. + +“**Online Service**” means any service or software provided by GitHub to Customer under the GitHub Customer Agreement agreed upon with Customer, including Previews, updates, patches, bug fixes, and technical support. + +“**Personal Data**” means any information relating to an identified or identifiable natural person. An identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person. + +“**Preview**” means Online Services provided for preview, evaluation, demonstration or trial purposes, or pre-release versions of the Online Services. + +“**Professional Services Data**” means all data, including all text, sound, video, image files or software, that are provided to GitHub, by or on behalf of a Customer (or that Customer authorizes GitHub to obtain from an Online Service) or otherwise obtained or processed by or on behalf of GitHub through an engagement with GitHub to obtain Professional Services. Professional Services Data includes Support Data. + +“**Service Generated Data**” means data generated or derived by GitHub through the operation of an Online Service. Service Generated Data does not include Customer Data, Diagnostic Data, or Professional Services Data. + +“**Standard Contractual Clauses**” means either of the following sets of Standard Contractual Clauses, as applicable in the individual case to the transfer of personal data according to the section of this DPA entitled “Data Transfers and Location” below: +- the Standard Contractual Clauses (MODULE TWO: Transfer controller to processor), dated 4 June 2021, for the transfer of personal data to third countries pursuant to Regulation (EU) 2016/679 of the European Parliament and of the Council, as described in Article 46 of the GDPR and approved by European Commission Implementing Decision (EU) 2021/91 (“Standard Contractual Clauses (EU/EEA)”). The Standard Contractual Clauses (EU/EEA) are set forth in Attachment 1. +- the Standard Contractual Clauses (Processors), dated 5 February 2010, for the transfer of personal data to processors established in third countries which do not ensure an adequate level of data protection, as described in Article 46 of the GDPR, approved by European Commission Decision 2010/87/EU and recognized by the regulatory or supervisory authorities of the United Kingdom for use in connection with data transfers from the United Kingdom (“Standard Contractual Clauses (UK)”). The Standard Contractual Clauses (UK) are set forth in Attachment 2. + +“**Subprocessor**” means other processors used by GitHub to process Personal Data on behalf of Customer in connection with the Online Services, as described in Article 28 of the GDPR. + +“**Support Data**” means all data, including all text, sound, video, image files, or software, that are provided to GitHub by or on behalf of Customer (or that Customer authorizes GitHub to obtain from an Online Service) through an engagement with GitHub to obtain technical support for Online Services covered under this agreement. Support Data is a subset of Professional Services Data. + +Lower case terms used but not defined in this DPA, such as “personal data breach”, “processing”, “controller”, “processor”, “profiling”, “personal data”, and “data subject” will have the same meaning as set forth in Article 4 of the GDPR, irrespective of whether GDPR applies. The terms “data importer” and “data exporter” have the meanings given in the Standard Contractual Clauses. + +For clarity, and as detailed above, data defined as Customer Data, Diagnostic Data, Service Generated Data, and Professional Services Data may contain Personal Data. For illustrative purposes, please see the chart inserted below: + +
    + personal_data_types +
    + +Above is a visual representation of the data types defined in the DPA. All Personal Data is processed as a part of one of the other data types (all of which also include non-personal data). Support Data is a sub-set of Professional Services Data. Except where explicitly stated otherwise, the DPA Terms exclusively apply to Personal Data. + +## General Terms + +### Compliance with Laws + +GitHub will comply with all laws and regulations applicable to its provision of the Online Services, including security breach notification law and Data Protection Requirements. However, GitHub is not responsible for compliance with any laws or regulations applicable to Customer or Customer’s industry that are not generally applicable to information technology service providers. GitHub does not determine whether Customer Data includes information subject to any specific law or regulation. All Security Incidents are subject to the Security Incident Notification terms below. + +Customer must comply with all laws and regulations applicable to its use of Online Services, including laws related to biometric data, confidentiality of communications, and Data Protection Requirements. Customer is responsible for determining whether the Online Services are appropriate for storage and processing of information subject to any specific law or regulation and for using the Online Services in a manner consistent with Customer’s legal and regulatory obligations. Customer is responsible for responding to any request from a third party regarding Customer’s use of an Online Service, such as a request to take down content under the U.S. Digital Millennium Copyright Act or other applicable laws. + +## Data Protection + +Terms This section of the DPA includes the following subsections: +- Scope +- Nature of Data Processing; Ownership +- Disclosure of Processed Data +- Processing of Personal Data; GDPR +- Data Security +- Security Incident Notification +- Data Transfers and Location +- Data Retention and Deletion +- Processor Confidentiality Commitment +- Notice and Controls on Use of Subprocessors +- Educational Institutions +- CJIS Customer Agreement, HIPAA Business Associate, Biometric Data +- California Consumer Privacy Act (CCPA) +- How to Contact GitHub +- Appendix A – Security Measures + +### Scope + +The DPA Terms apply to all Online Services. + +Previews may employ lesser or different privacy and security measures than those typically present in the Online Services. Unless otherwise noted, Customer should not use Previews to process Personal Data or other data that is subject to legal or regulatory compliance requirements. The following terms in this DPA do not apply to Previews: Processing of Personal Data; GDPR, Data Security, and California Consumer Privacy Act. + +### Nature of Data Processing; Ownership + +Except as otherwise stated in the DPA Terms, GitHub will use and otherwise process Customer Data and Personal Data as described and subject to the limitations provided below (a) to provide Customer the Online Service in accordance with Customer’s documented instructions, and/or (b) for GitHub’s legitimate business operations incident to delivery of the Online Services to Customer. As between the parties, Customer retains all right, title and interest in and to Customer Data. GitHub acquires no rights in Customer Data other than the rights Customer grants to GitHub in this section. This paragraph does not affect GitHub’s rights in software or services GitHub licenses to Customer. + +#### Processing to Provide Customer the Online Services + +For purposes of this DPA, “to provide” an Online Service consists of: +- Delivering functional capabilities as licensed, configured, and used by Customer and its users, including providing personalized user experiences; +- Troubleshooting (e.g., preventing, detecting, and repairing problems); and +- Ongoing improvement (e.g., installing the latest updates and making improvements to user productivity, reliability, efficacy, and security). + +When providing Online Services, GitHub will use or otherwise process Personal Data only on Customer’s behalf and in accordance with Customer’s documented instructions. + +#### Processing for GitHub’s Legitimate Business Operations + +For purposes of this DPA, “GitHub’s legitimate business operations” consist of the following, each as incident to delivery of the Online Services to Customer: (1) billing and account management; (2) compensation (e.g., calculating employee commissions and partner incentives); (3) internal reporting and business modeling (e.g., forecasting, revenue, capacity planning, product strategy); (4) combatting fraud, abuse, cybercrime, or cyber-attacks that may affect GitHub or Online Services; (5) improving the core functionality of accessibility, privacy or energy-efficiency; (6) financial reporting and compliance with legal obligations (subject to the limitations on disclosure of Processed Data outlined below); (7) the creation or management of end user accounts and profiles by GitHub for individual users of Customer (except where Customer creates, manages or otherwise controls such end user accounts or profiles itself); and (8) other purposes pertaining to Personal Data not provided by Customer for storage in GitHub repositories or in connection with Professional Services. + +When processing for GitHub’s legitimate business operations, GitHub will not use or otherwise process Personal Data for: (a) user profiling, (b) advertising or similar commercial purposes, (c) data selling or brokering, or (d) any other purpose, other than for the purposes set out in this section. + +### Disclosure of Processed Data + +GitHub will not disclose or provide access to any Processed Data except: (1) as Customer directs; (2) as described in this DPA; or (3) as required by law. For purposes of this section, “Processed Data” means: (a) Customer Data; (b) Personal Data and (c) any other data processed by GitHub in connection with the Online Service that is Customer’s confidential information under the GitHub Customer Agreement. All processing of Processed Data is subject to GitHub’s obligation of confidentiality under the GitHub Customer Agreement. + +GitHub will not disclose or provide access to any Processed Data to law enforcement unless required by law. If law enforcement contacts GitHub with a demand for Processed Data, GitHub will attempt to redirect the law enforcement agency to request that data directly from Customer. If compelled to disclose or provide access to any Processed Data to law enforcement, GitHub will promptly notify Customer and provide a copy of the demand, unless legally prohibited from doing so. + +Upon receipt of any other third-party request for Processed Data, GitHub will promptly notify Customer unless prohibited by law. GitHub will reject the request unless required by law to comply. If the request is valid, GitHub will attempt to redirect the third party to request the data directly from Customer. + +GitHub will not provide any third party: (a) direct, indirect, blanket, or unfettered access to Processed Data; (b) platform encryption keys used to secure Processed Data or the ability to break such encryption; or (c) access to Processed Data if GitHub is aware that the data is to be used for purposes other than those stated in the third party’s request. + +In support of the above, GitHub may provide Customer’s basic contact information to the third party. + +### Processing of Personal Data; GDPR + +All Personal Data processed by GitHub in connection with the Online Services is obtained as part of either Customer Data, Professional Services Data (including Support Data), Diagnostic Data, or Service Generated Data. Personal Data provided to GitHub by, or on behalf of, Customer through use of the Online Service is also Customer Data. Pseudonymized identifiers may be included in Diagnostic Data or Service Generated Data and are also Personal Data. Any Personal Data pseudonymized, or de-identified but not anonymized, or Personal Data derived from Personal Data is also Personal Data. + +To the extent GitHub is a processor or subprocessor of Personal Data subject to the GDPR, the GDPR Related Terms in Attachment 3 govern that processing and the parties also agree to the following terms in this sub-section (“Processing of Personal Data; GDPR”): + +#### Processor and Controller Roles and Responsibilities + +Customer and GitHub agree that Customer is the controller of Personal Data and GitHub is the processor of such data, except (a) when Customer acts as a processor of Personal Data, in which case GitHub is a subprocessor; or (b) as stated otherwise in the GitHub Customer Agreement or this DPA. When GitHub acts as the processor or subprocessor of Personal Data, it will process Personal Data only on Customer’s behalf and in accordance with documented instructions from Customer. Customer agrees that its GitHub Customer Agreement (including the DPA Terms and any applicable updates), along with the product documentation and Customer’s use and configuration of features in the Online Services, are Customer’s complete documented instructions to GitHub for the processing of Personal Data. Information on use and configuration of the Online Services can be found at https://docs.github.com or a successor location. Any additional or alternate instructions must be agreed to according to the process for amending Customer’s GitHub Customer Agreement. In any instance where the GDPR applies and Customer is a processor, Customer warrants to GitHub that Customer’s instructions, including appointment of GitHub as a processor or subprocessor, have been authorized by the relevant controller. + +To the extent GitHub uses or otherwise processes Personal Data subject to the GDPR for GitHub’s legitimate business operations incident to delivery of the Online Services to Customer, GitHub will comply with the obligations of an independent data controller under GDPR for such use. GitHub is accepting the added responsibilities of a data “controller” under the GDPR for processing in connection with its legitimate business operations to: (a) act consistent with regulatory requirements, to the extent required under the GDPR; and (b) provide increased transparency to Customers and confirm GitHub’s accountability for such processing. GitHub employs safeguards to protect Personal Data in processing, including those identified in this DPA and those contemplated in Article 6(4) of the GDPR. With respect to processing of Personal Data under this paragraph, GitHub makes the commitments set forth in the Standard Contractual Clauses set forth in Attachment 1 or Attachment 2 (as applicable); for those purposes, (i) any GitHub disclosure of Personal Data, as described in Annex III to Attachment 1 or Appendix 3 to Attachment 2 (as applicable), that has been transferred in connection with GitHub’s legitimate business operations is deemed a “Relevant Disclosure” and (ii) the commitments in Annex III to Attachment 1 or Appendix 3 to Attachment 2 (as applicable) apply to such Personal Data. + +#### Processing Details + +The parties acknowledge and agree that: + +- **Subject Matter**. The subject-matter of the processing is limited to Personal Data within the scope of the section of this DPA entitled “Nature of Data Processing; Ownership” above and the GDPR. +- **Duration of the Processing**. The duration of the processing shall be in accordance with Customer instructions and the terms of the DPA. +- **Nature and Purpose of the Processing**. The nature and purpose of the processing shall be to provide the Online Service pursuant to Customer’s GitHub Customer Agreement and for GitHub’s legitimate business operations incident to delivery of the Online Service to Customer (as further described in the section of this DPA entitled “Nature of Data Processing; Ownership” above). +- **Categories of Data**. The types of Personal Data processed by GitHub when providing the Online Service include: (i) Personal Data that Customer elects to include in Customer Data or Professional Services Data (including, without limitation, Support Data); and (ii) those expressly identified in Article 4 of the GDPR that may be contained in Diagnostic Data or Service Generated Data. The types of Personal Data that Customer elects to include in Customer Data or Professional Services Data (including, without limitation, Support Data) may be any categories of Personal Data identified in records maintained by Customer acting as controller pursuant to Article 30 of the GDPR, including the categories of Personal Data set forth in Annex I to Attachment 1 or Appendix 1 to Attachment 2 (as applicable). +- Data Subjects. The categories of data subjects are Customer’s representatives and end users, such as employees, contractors, collaborators, and customers, and may include any other categories of data subjects as identified in records maintained by Customer acting as controller pursuant to Article 30 of the GDPR, including the categories of data subjects set forth in Annex I to Attachment 1 or Appendix 1 to Attachment 2 (as applicable). + +#### Data Subject Rights; Assistance with Requests + +GitHub will make available to Customer, in a manner consistent with the functionality of the Online Service and GitHub’s role as a processor of Personal Data of data subjects, the ability to fulfill data subject requests to exercise their rights under the GDPR. If GitHub receives a request from Customer’s data subject to exercise one or more of its rights under the GDPR in connection with an Online Service for which GitHub is a data processor or subprocessor, GitHub will redirect the data subject to make its request directly to Customer. Customer will be responsible for responding to any such request including, where necessary, by using the functionality of the Online Service. GitHub shall comply with reasonable requests by Customer to assist with Customer’s response to such a data subject request. + +#### Records of Processing Activities + +To the extent the GDPR requires GitHub to collect and maintain records of certain information relating to Customer, Customer will, where requested, supply such information to GitHub and keep it accurate and up-to-date. GitHub may make any such information available to the supervisory authority if required by the GDPR. + +### Data Security + +GitHub will implement and maintain appropriate technical and organizational measures and security safeguards against accidental or unlawful destruction, or loss, alteration, unauthorized disclosure of or access to, Customer Data and Personal Data processed by GitHub on behalf and in accordance with the documented instructions of Customer in connection with the Online Services. GitHub will regularly monitor compliance with these measures and safeguards and will continue to take appropriate steps throughout the term of the GitHub Customer Agreement. Appendix A – Security Safeguards contains a description of the technical and organizational measures and security safeguards implemented by GitHub. + +Customer is solely responsible for making an independent determination as to whether the technical and organizational measures and security safeguards for an Online Service meet Customer’s requirements, including any of its security obligations under applicable Data Protection Requirements. Customer acknowledges and agrees that (taking into account the state of the art, the costs of implementation, and the nature, scope, context and purposes of the processing of its Customer Data and Personal Data as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons) the technical and organizational measures and security safeguards implemented and maintained by GitHub provide a level of security appropriate to the risk with respect to its Customer Data and Personal Data. Customer is responsible for implementing and maintaining privacy protections and security measures for components that Customer provides or controls. + +GitHub will provide security compliance reporting such as external SOC1, type 2 and SOC2, type2 audit reports upon Customer request. Customer agrees that any information and audit rights granted by the applicable Data Protection Requirements (including, where applicable, Article 28(3)(h) of the GDPR) will be satisfied by these compliance reports, and will otherwise only arise to the extent that GitHub's provision of a compliance report does not provide sufficient information, or to the extent that Customer must respond to a regulatory or supervisory authority audit or investigation. + +Should Customer be subject to a regulatory or supervisory authority audit or investigation or carry out an audit or investigation in response to a request by a regulatory or supervisory authority that requires participation from GitHub, and Customers’ obligations cannot reasonably be satisfied (where allowable by Customer’s regulators) through audit reports, documentation, or compliance information that GitHub makes generally available to its customers, then GitHub will promptly respond to Customer’s additional instructions and requests for information, in accordance with the following terms and conditions: + +- GitHub will provide access to relevant knowledgeable personnel, documentation, and application software. +- Customer and GitHub will mutually agree in a prior written agreement (email is acceptable) upon the scope, timing, duration, control and evidence requirements, provided that this requirement to agree will not permit GitHub to unreasonably delay its cooperation. +- Customer must ensure its regulator’s use of an independent, accredited third-party audit firm, during regular business hours, with reasonable advance written notice to GitHub, and subject to reasonable confidentiality procedures. Neither Customer, its regulators, nor its regulators’ delegates shall have access to any data from GitHub’s other customers or to GitHub systems or facilities not involved in the Online Services. +- Customer is responsible for all costs and fees related to GitHub’s cooperation with the regulatory audit of Customer, including all reasonable costs and fees for any and all time GitHub expends, in addition to the rates for services performed by GitHub. +- If the report generated from GitHub’s cooperation with the regulatory audit of Customer includes any findings pertaining to GitHub, Customer will share such report, findings, and recommended actions with GitHub where allowed by Customer’s regulators. + +### Security Incident Notification + +If GitHub becomes aware of a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Customer Data or Personal Data processed by GitHub on behalf and in accordance with the documented instructions of Customer in connection with the Online Services (each a "Security Incident"), GitHub will promptly and without undue delay (1) notify Customer of the Security Incident; (2) investigate the Security Incident and provide Customer with detailed information about the Security Incident; (3) take reasonable steps to mitigate the effects and to minimize any damage resulting from the Security Incident. + +Notification(s) of Security Incidents will be delivered to one or more of Customer's administrators by any means GitHub selects, including via email. It is Customer's sole responsibility to ensure it maintains accurate contact information with GitHub and that Customer's administrators monitor for and respond to any notifications. Customer is solely responsible for complying with its obligations under incident notification laws applicable to Customer and fulfilling any third-party notification obligations related to any Security Incident. + +GitHub will make reasonable efforts to assist Customer in fulfilling Customer's obligation under GDPR Article 33 or other applicable law or regulations to notify the relevant regulatory or supervisory authority and individual data subjects about a Security Incident. + +GitHub’s notification of or response to a Security Incident under this section is not an acknowledgement by GitHub of any fault or liability with respect to the Security Incident. + +Customer must notify GitHub promptly about any possible misuse of its accounts or authentication credentials or any Security Incident related to an Online Service. + +### Data Transfers and Location + +Personal Data that GitHub processes on behalf and in accordance with the documented instructions of Customer in connection with the Online Services may not be transferred to, or stored and processed in a geographic location except in accordance with the DPA Terms and the safeguards provided below in this section. Taking into account such safeguards, Customer appoints GitHub to transfer Personal Data to the United States or any other country in which GitHub or its Subprocessors operate and to store and process Personal Data to provide the Online Services, except as may be described elsewhere in these DPA Terms. + +All transfers of Personal Data out of the European Union, European Economic Area, or Switzerland to provide the Online Services shall be governed by the Standard Contractual Clauses (EU/EEA) in Attachment 1. All transfers of Personal Data out of the United Kingdom to provide the Online Services shall be governed by the Standard Contractual Clauses (UK) in Attachment 2. For the purposes of the Standard Contractual Clauses (UK) in Attachment 2, references to the “European Union,” “EU,” “European Economic Area,” “EEA” or a “Member State” shall be interpreted to refer to the United Kingdom where reasonably necessary and appropriate to give full force and effect to the Standard Contractual Clauses (UK) with respect to transfers of Personal Data from the United Kingdom. This applies regardless of the fact that, effective January 31, 2020, the United Kingdom is no longer a Member State of the European Union or European Economic Area. + +GitHub will abide by the requirements of applicable European Union, European Economic Area, United Kingdom and Swiss data protection law, and other Data Protection Requirements, in each case regarding the transfer of Personal Data to recipients or jurisdictions outside such jurisdiction. All such transfers of Personal Data will, where applicable, be subject to appropriate safeguards as described in Article 46 of the GDPR and such transfers and safeguards will be documented according to Article 30(2) of the GDPR. + +Subject to the safeguards described above, GitHub may transfer, store and otherwise process Personal Data to or in jurisdictions and geographic locations worldwide as it, subject to its sole discretion, considers reasonably necessary in connection with the Online Services. + +### Data Retention and Deletion + +Upon Customer's reasonable request, unless prohibited by law, GitHub will return or destroy all Customer Data and Personal Data processed by GitHub on behalf and in accordance with the documented instructions of Customer in connection with the Online Services at all locations where it is stored within 30 days of the request, provided that it is no longer needed for providing the Online Services or the purposes for which a data subject had authorized the processing of their Personal Data. GitHub may retain Customer Data or Personal Data to the extent required by the applicable Data Protection Requirements or other applicable law, and only to the extent and for such period as required by the applicable Data Protection Requirements or other applicable law, provided that GitHub will ensure that the Customer Data or Personal Data is processed only as necessary for the purpose specified in the applicable Data Protection Requirements or other applicable law and no other purpose, and the Customer Data or Personal Data remains protected by the Applicable Data Protection Requirements or other applicable law. + +### Processor Confidentiality Commitment + +GitHub will ensure that its personnel engaged in the processing of Customer Data and Personal Data on behalf of Customer in connection with the Online Services (i) will process such data only on instructions from Customer or as described in this DPA, and (ii) will be obligated to maintain the confidentiality and security of such data even after their engagement ends. GitHub shall provide periodic and mandatory data privacy and security training and awareness to its employees with access to Customer Data and Personal Data in accordance with applicable Data Protection Requirements or other applicable law and industry standards. + +### Notice and Controls on Use of Subprocessors + +GitHub may hire Subprocessors to provide certain limited or ancillary services on its behalf. Customer consents to this engagement and to GitHub Affiliates as Subprocessors. The above authorizations will constitute Customer’s prior written consent to the subcontracting by GitHub of the processing of Personal Data if such consent is required under applicable law, the Standard Contractual Clauses or the GDPR Related Terms. + +GitHub is responsible for its Subprocessors’ compliance with GitHub’s obligations in this DPA. GitHub makes available information about Subprocessors on the GitHub website https://github.com/subprocessors (or a successor location). When engaging any Subprocessor, GitHub will ensure via a written contract that the Subprocessor may access and use Customer Data or Personal Data only to deliver the services GitHub has retained them to provide and is prohibited from using Customer Data or Personal Data for any other purpose. GitHub will ensure that Subprocessors are bound by written agreements that require them to provide at least the level of data protection required of GitHub by the DPA, including the limitations on disclosure of Personal Data. GitHub agrees to oversee the Subprocessors to ensure that these contractual obligations are met. + +From time to time, GitHub may engage new Subprocessors. GitHub will give Customer notice (by updating the website at https://github.com/github-subprocessors-list (or a successor location) and providing Customer with a mechanism to obtain notice of that update) of any new Subprocessor in advance of providing that Subprocessor with access to Customer Data. If GitHub engages a new Subprocessor for a new Online Service, GitHub will give Customer notice prior to availability of that Online Service. + +If Customer does not approve of a new Subprocessor, then Customer may terminate any subscription for the affected Online Service without penalty by providing, before the end of the relevant notice period, written notice of termination. Customer may also include an explanation of the grounds for non-approval together with the termination notice, in order to permit GitHub to re-evaluate any such new Subprocessor based on the applicable concerns. If the affected Online Service is part of a suite (or similar single purchase of services), then any termination will apply to the entire suite. After termination, GitHub will remove payment obligations for any subscriptions for the terminated Online Service from subsequent invoices to Customer or its reseller. + +### Educational Institutions +If Customer is an educational agency or institution subject to the regulations under the Family Educational Rights and Privacy Act, 20 U.S.C. § 1232g (FERPA), or similar state student or educational privacy laws (collectively “Educational Privacy Laws”), Customer shall not provide Personal Data covered by such Educational Privacy Laws to GitHub without obtaining GitHub’s prior, written and specific consent and entering into a separate agreement with GitHub governing the parties’ rights and obligations with respect to the processing of such Personal Data by GitHub in connection with the Online Services. + +Subject to the above, if Customer intends to provide to GitHub Personal Data covered by FERPA, the parties agree and acknowledge that, for the purposes of this DPA, GitHub is a “school official” with “legitimate educational interests” in the Personal Data, as those terms have been defined under FERPA and its implementing regulations. Customer understands that GitHub may possess limited or no contact information for Customer’s students and students’ parents. Consequently, Customer will be responsible for obtaining any student or parental consent for any end user’s use of the Online Services that may be required by applicable law and to convey notification on behalf of GitHub to students (or, with respect to a student under 18 years of age and not in attendance at a postsecondary institution, to the student’s parent) of any judicial order or lawfully-issued subpoena requiring the disclosure of Personal Data in GitHub’s possession as may be required under applicable law. + +### CJIS Customer Agreement, HIPAA Business Associate, Biometric Data + +Except with GitHub’s prior, written and specific consent, Customer shall not provide to GitHub any Personal Data + +- relating to criminal convictions and offenses or Personal Data collected or otherwise processed by Customer subject to or in connection with FBI Criminal Justice Information Services or the related Security Policy. +- constituting protected health information governed by the privacy, security, and breach notification rules issued by the United States Department of Health and Human Services, Parts 160 and 164 of Title 45 of the Code of Federal Regulations, established pursuant to the Health Insurance Portability and Accountability Act of 1996 (Public Law 104-191) or by state health or medical privacy laws. +- collected as part of a clinical trial or other biomedical research study subject to, or conducted in accordance with, the Federal Policy for the Protection of Human Subjects (Common Rule). +- covered by state, federal or foreign biometric privacy laws or otherwise constituting biometric information including information on an individual’s physical, physiological, biological or behavioral characteristics or information derived from such information that is used or intended to be used, singly or in combination with each other or with other information, to establish individual identity. + +### California Consumer Privacy Act (CCPA) / California Privacy Rights Act (CPRA) + +If and to the extent GitHub is processing Personal Data on behalf and in accordance with the documented instructions of Customer within the scope of the CCPA, GitHub makes the following additional commitments to Customer. GitHub will process the Personal Data on behalf of Customer and will not + +- sell the Personal Data as the term “selling” is defined in the CCPA. - share, rent, release, disclose, disseminate, make available, transfer or otherwise communicate orally, in writing or by electronic or other means, the Personal Data to a third party for cross-context behavioral advertising, whether or not for monetary or other valuable consideration, including transactions for cross-context behavioral advertising in which no money is exchanged. +- retain, use or disclose the Personal Data for any purpose other than for the business purposes specified in the DPA Terms and the GitHub Customer Agreement, including retaining, using or disclosing the Personal Data for a commercial purpose other than the business purposes specified in the DPA Terms or the GitHub Customer Agreement, or as otherwise permitted by the CCPA. +- retain, use or disclose the Personal Data outside of the direct business relationship with Customer. +- combine the Personal Data with personal information that it receives from or on behalf of a third party or collects from California residents, except that GitHub may combine Personal Data to perform any business purpose as permitted by the CCPA or any regulations adopted or issued under the CCPA. + +### How to Contact GitHub + +If Customer believes that GitHub is not adhering to its privacy or security commitments, Customer may contact customer support or use GitHub’s Privacy web form, located at https://support.github.com/contact/privacy. GitHub’s mailing address is: + +**GitHub Privacy**
    GitHub, Inc.
    88 Colin P. Kelly Jr. Street
    San Francisco, California 94107 USA
    + +GitHub B.V. is GitHub’s data protection representative for the European Economic Area. The privacy representative of GitHub B.V. can be reached at the following address: + +**GitHub B.V.**
    Vijzelstraat 68-72
    1017 HL Amsterdam
    The Netherlands
    + +

    Appendix A – Security Safeguards

    + +GitHub has implemented and will maintain for Customer Data and Personal Data processed by GitHub on behalf and in accordance with the documented instructions of Customer in connection with GitHub services the following technical and organizational measures and security safeguards, which in conjunction with the security commitments in this DPA (including the GDPR Related Terms), are GitHub’s only responsibility with respect to the security of that data: + +| Domain | Practices | +| ---------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Organization of Information Security | **Security Ownership**. GitHub has appointed one or more security officers responsible for coordinating and monitoring the security policies and procedures.

    **Security Roles and Responsibilities**. GitHub personnel with access to Customer Data and Personal Data are subject to confidentiality obligations.

    **Risk Management Program**. GitHub performs an annual risk assessment.
    GitHub retains its security documents pursuant to its retention requirements after they are no longer in effect.

    **Vendor Management**. GitHub has a vendor risk assessment process, vendor contract clauses and additional data protection agreements with vendors. | +| Asset Management | **Asset Inventory**. GitHub maintains an inventory of all media on which Customer Data and Personal Data is stored. Access to the inventories of such media is restricted to GitHub personnel authorized to have such access.

    **Asset Handling**
    - GitHub classifies Customer Data and Personal Data to help identify it and to allow for access to it to be appropriately restricted.
    - GitHub communicates employee responsibility and accountability for data protection up to and including cause for termination.
    GitHub personnel must obtain GitHub authorization prior to remotely accessing Customer Data and Personal Data or processing Customer Data and Personal Data outside GitHub’s facilities. | +| Human Resources Security | **Security Training**. GitHub requires all new hires to complete security and privacy awareness training as part of initial on-boarding. Participation in annual training is required for all employees to provide a baseline for security and privacy basics. | +| Physical and Environmental Security | **Physical Access to Facilities**. GitHub limits access to facilities where information systems that process Customer Data and Personal Data are located to identified authorized individuals.

    **Physical Access to Components**. GitHub maintains records of the incoming and outgoing media containing Customer Data, including the kind of media, the authorized sender/recipients, date and time, the number of media and the types of Customer Data and Personal Data they contain.

    **Protection from Disruptions**. GitHub uses a variety of industry standard systems to protect against loss of data due to power supply failure or line interference.

    **Component Disposal**. GitHub uses industry standard processes to delete Customer Data and Personal Data when it is no longer needed. | +| Communications and Operations Management | **Operational Policy**. GitHub maintains security documents describing its security measures and the relevant procedures and responsibilities of its personnel who have access to Customer Data.

    **Data Recovery Procedures**
    - On an ongoing basis, but in no case less frequently than once a week (unless no Customer Data and Personal Data has been updated during that period), GitHub maintains multiple copies of Customer Data and Personal Data from which Customer Data and Personal Data can be recovered.
    - GitHub stores copies of Customer Data and Personal Data and data recovery procedures in a different place from where the primary computer equipment processing the Customer Data and Personal Data is located.
    - GitHub has specific procedures in place governing access to copies of Customer Data.
    - GitHub logs data restoration efforts, including the person responsible, the description of the restored data and where applicable, the person responsible and which data (if any) had to be input manually in the data recovery process.

    **Malicious Software**. GitHub has threat detection controls to help identify and respond to anomalous or suspicious access to Customer Data, including malicious software originating from public networks.

    **Data Beyond Boundaries**
    - GitHub encrypts, or enables Customer to encrypt, Customer Data and Personal Data that is transmitted over public networks.
    - GitHub restricts access to Customer Data and Personal Data in media leaving its facilities.

    **Event Logging**. GitHub logs, or enables Customer to log, access and use of information systems containing Customer Data, registering the access ID, time, authorization granted or denied, and relevant activity. | +| Access Control | **Access Policy**. GitHub maintains a record of security privileges of individuals having access to Customer Data.

    **Access Authorization**
    - GitHub maintains and updates a record of personnel authorized to access GitHub systems that contain Customer Data.
    - GitHub identifies those personnel who may grant, alter or cancel authorized access to data and resources.
    - GitHub ensures that where more than one individual has access to systems containing Customer Data, the individuals have separate identifiers/log-ins where technically and architecturally feasible, and commercially reasonable.

    **Least Privilege**
    - Technical support personnel are only permitted to have access to Customer Data and Personal Data when needed.
    - GitHub restricts access to Customer Data and Personal Data to only those individuals who require such access to perform their job function. GitHub employees are only granted access to production systems based on their role within the organization.

    **Integrity and Confidentiality**

    - GitHub instructs GitHub personnel to disable administrative sessions when computers are left unattended.
    - GitHub stores passwords such that they are encrypted or unintelligible while they are in force.

    **Authentication**
    - GitHub uses industry standard practices to identify and authenticate users who attempt to access information systems.
    - Where authentication mechanisms are based solely on passwords, GitHub requires the password to be at least eight characters long.
    - GitHub ensures that de-activated or expired employee identifiers are not granted to other individuals.
    - GitHub monitors, or enables Customer to monitor, repeated attempts to gain access to the information system using an invalid password.
    - GitHub maintains industry standard procedures to deactivate passwords that have been corrupted or inadvertently disclosed.
    - GitHub uses industry standard password protection practices, including practices designed to maintain the confidentiality and integrity of passwords when they are assigned and distributed, and during storage.

    **Network Design**. GitHub has controls to ensure no systems storing Customer Data and Personal Data are part of the same logical network used for GitHub business operations. | +| Information Security Incident Management | **Incident Response Process**
    - GitHub maintains a record of security incidents with a description of the incidents, the time period, the consequences of the breach, the name of the reporter, and to whom the incident was reported, and details regarding the handling of the incident.
    - In the event that GitHub Security confirms or reasonably suspects that a GitHub.com customer is affected by a data breach, we will notify the customer without undue delay
    - GitHub tracks, or enables Customer to track, disclosures of Customer Data, including what data has been disclosed, to whom, and at what time.

    **Service Monitoring**. GitHub employs a wide range of continuous monitoring solutions for preventing, detecting, and mitigating attacks to the site. | +| Business Continuity Management | - GitHub maintains emergency and contingency plans for the facilities in which GitHub information systems that process Customer Data and Personal Data are located.
    - GitHub’s redundant storage and its procedures for recovering data are designed to attempt to reconstruct Customer Data and Personal Data in its original or last-replicated state from before the time it was lost or destroyed. | + +

    Attachment 1 - The Standard Contractual Clauses (EU/EEA)

    + +### Controller to Processor + +#### SECTION I + +##### Clause 1 + +**Purpose and scope** + +
      +
    1. The purpose of these standard contractual clauses is to ensure compliance with the requirements of Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data (General Data Protection Regulation) for the transfer of personal data to a third country.
      2. +
    2. The Parties: +
        +
      1. the natural or legal person(s), public authority/ies, agency/ies or other body/ies (hereinafter ‘entity/ies’) transferring the personal data, as listed in Annex I.A (hereinafter each ‘data exporter’), and
        2. +
      2. the entity/ies in a third country receiving the personal data from the data exporter, directly or indirectly via another entity also Party to these Clauses, as listed in Annex I.A (hereinafter each ‘data importer’)
        3. +
      + have agreed to these standard contractual clauses (hereinafter: ‘Clauses’).
      3. +
    3. These Clauses apply with respect to the transfer of personal data as specified in Annex I.B.
      4. +
    4. The Appendix to these Clauses containing the Annexes referred to therein forms an integral part of these Clauses.
      5. +
    + +##### Clause 2 + +**Effect and invariability of the Clauses** +
      +
    1. These Clauses set out appropriate safeguards, including enforceable data subject rights and effective legal remedies, pursuant to Article 46(1) and Article 46(2)(c) of Regulation (EU) 2016/679 and, with respect to data transfers from controllers to processors and/or processors to processors, standard contractual clauses pursuant to Article 28(7) of Regulation (EU) 2016/679, provided they are not modified, except to select the appropriate Module(s) or to add or update information in the Appendix. This does not prevent the Parties from including the standard contractual clauses laid down in these Clauses in a wider contract and/or to add other clauses or additional safeguards, provided that they do not contradict, directly or indirectly, these Clauses or prejudice the fundamental rights or freedoms of data subjects.
      2. +
    2. These Clauses are without prejudice to obligations to which the data exporter is subject by virtue of Regulation (EU) 2016/679.
      3. +
    + +##### Clause 3 + +**Third-party beneficiaries** + +
      +
    1. Data subjects may invoke and enforce these Clauses, as third-party beneficiaries, against the data exporter and/or data importer, with the following exceptions:
      2. +
        +
      1. Clause 1, Clause 2, Clause 3, Clause 6, Clause 7;
        2. +
      2. Clause 8.1(b), 8.9(a), (c), (d) and (e);
        3. +
      3. Clause 9(a), (c), (d) and (e);
        4. +
      4. Clause 12(a), (d) and (f);
        5. +
      5. Clause 13;
        6. +
      6. Clause 15.1(c), (d) and (e);
        7. +
      7. Clause 16(e);
        8. +
      8. Clause 18(a) and (b).
        9. +
      +
    2. Paragraph (a) is without prejudice to rights of data subjects under Regulation (EU) 2016/679.
      3. +
    + +##### Clause 4 + +**Interpretation** + +
      +
    1. Where these Clauses use terms that are defined in Regulation (EU) 2016/679, those terms shall have the same meaning as in that Regulation.
      2. +
    2. These Clauses shall be read and interpreted in the light of the provisions of Regulation (EU) 2016/679.
      3. +
    3. These Clauses shall not be interpreted in a way that conflicts with rights and obligations provided for in Regulation (EU) 2016/679.
      4. +
    + +##### Clause 5 + +**Hierarchy** + +In the event of a contradiction between these Clauses and the provisions of related agreements between the Parties, existing at the time these Clauses are agreed or entered into thereafter, these Clauses shall prevail. + +##### Clause 6 + +**Description of the transfer(s)** + +The details of the transfer(s), and in particular the categories of personal data that are transferred and the purpose(s) for which they are transferred, are specified in Annex I.B. + +##### Clause 7 + +**Docking clause** + +
      +
    1. An entity that is not a Party to these Clauses may, with the agreement of the Parties, accede to these Clauses at any time, either as a data exporter or as a data importer, by completing the Appendix and signing Annex I.A.
      2. +
    2. Once it has completed the Appendix and signed Annex I.A, the acceding entity shall become a Party to these Clauses and have the rights and obligations of a data exporter or data importer in accordance with its designation in Annex I.A.
      3. +
    3. The acceding entity shall have no rights or obligations arising under these Clauses from the period prior to becoming a Party.
      4. +
    + +#### SECTION II – OBLIGATIONS OF THE PARTIES + +##### Clause 8 + +**Data protection safeguards** + +The data exporter warrants that it has used reasonable efforts to determine that the data importer is able, through the implementation of appropriate technical and organisational measures, to satisfy its obligations under these Clauses. + +**8.1 Instructions**
      +
    1. The data importer shall process the personal data only on documented instructions from the data exporter. The data exporter may give such instructions throughout the duration of the contract.
      2. +
    2. The data importer shall immediately inform the data exporter if it is unable to follow those instructions.
      3. +
    + +**8.2 Purpose limitation** + +The data importer shall process the personal data only for the specific purpose(s) of the transfer, as set out in Annex I.B, unless on further instructions from the data exporter. + +**8.3 Transparency** + +On request, the data exporter shall make a copy of these Clauses, including the Appendix as completed by the Parties, available to the data subject free of charge. To the extent necessary to protect business secrets or other confidential information, including the measures described in Annex II and personal data, the data exporter may redact part of the text of the Appendix to these Clauses prior to sharing a copy, but shall provide a meaningful summary where the data subject would otherwise not be able to understand the its content or exercise his/her rights. On request, the Parties shall provide the data subject with the reasons for the redactions, to the extent possible without revealing the redacted information. This Clause is without prejudice to the obligations of the data exporter under Articles 13 and 14 of Regulation (EU) 2016/679. + +**8.4 Accuracy** + +If the data importer becomes aware that the personal data it has received is inaccurate, or has become outdated, it shall inform the data exporter without undue delay. In this case, the data importer shall cooperate with the data exporter to erase or rectify the data. + +**8.5 Duration of processing and erasure or return of data** + +Processing by the data importer shall only take place for the duration specified in Annex I.B. After the end of the provision of the processing services, the data importer shall, at the choice of the data exporter, delete all personal data processed on behalf of the data exporter and certify to the data exporter that it has done so, or return to the data exporter all personal data processed on its behalf and delete existing copies. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit return or deletion of the personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process it to the extent and for as long as required under that local law. This is without prejudice to Clause 14, in particular the requirement for the data importer under Clause 14(e) to notify the data exporter throughout the duration of the contract if it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under Clause 14(a). + +**8.6 Security of processing** + +
      +
    1. The data importer and, during transmission, also the data exporter shall implement appropriate technical and organisational measures to ensure the security of the data, including protection against a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access to that data (hereinafter ‘personal data breach’). In assessing the appropriate level of security, the Parties shall take due account of the state of the art, the costs of implementation, the nature, scope, context and purpose(s) of processing and the risks involved in the processing for the data subjects. The Parties shall in particular consider having recourse to encryption or pseudonymisation, including during transmission, where the purpose of processing can be fulfilled in that manner. In case of pseudonymisation, the additional information for attributing the personal data to a specific data subject shall, where possible, remain under the exclusive control of the data exporter. In complying with its obligations under this paragraph, the data importer shall at least implement the technical and organisational measures specified in Annex II. The data importer shall carry out regular checks to ensure that these measures continue to provide an appropriate level of security.
      2. +
    2. The data importer shall grant access to the personal data to members of its personnel only to the extent strictly necessary for the implementation, management and monitoring of the contract. It shall ensure that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.
      3. +
    3. In the event of a personal data breach concerning personal data processed by the data importer under these Clauses, the data importer shall take appropriate measures to address the breach, including measures to mitigate its adverse effects. The data importer shall also notify the data exporter without undue delay after having become aware of the breach. Such notification shall contain the details of a contact point where more information can be obtained, a description of the nature of the breach (including, where possible, categories and approximate number of data subjects and personal data records concerned), its likely consequences and the measures taken or proposed to address the breach including, where appropriate, measures to mitigate its possible adverse effects. Where, and in so far as, it is not possible to provide all information at the same time, the initial notification shall contain the information then available and further information shall, as it becomes available, subsequently be provided without undue delay.
      4. +
    4. The data importer shall cooperate with and assist the data exporter to enable the data exporter to comply with its obligations under Regulation (EU) 2016/679, in particular to notify the competent supervisory authority and the affected data subjects, taking into account the nature of processing and the information available to the data importer.
      5. +
    + +**8.7 Sensitive data** + +Where the transfer involves personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic data, or biometric data for the purpose of uniquely identifying a natural person, data concerning health or a person’s sex life or sexual orientation, or data relating to criminal convictions and offences (hereinafter ‘sensitive data’), the data importer shall apply the specific restrictions and/or additional safeguards described in Annex I.B. + +**8.8 Onward transfers** + +The data importer shall only disclose the personal data to a third party on documented instructions from the data exporter. In addition, the data may only be disclosed to a third party located outside the European Union (1) (in the same country as the data importer or in another third country, hereinafter ‘onward transfer’) if the third party is or agrees to be bound by these Clauses, under the appropriate Module, or if: + +
      +
    1. the onward transfer is to a country benefitting from an adequacy decision pursuant to Article 45 of Regulation (EU) 2016/679 that covers the onward transfer;
      2. +
    2. the third party otherwise ensures appropriate safeguards pursuant to Articles 46 or 47 Regulation of (EU) 2016/679 with respect to the processing in question;
      3. +
    3. the onward transfer is necessary for the establishment, exercise or defence of legal claims in the context of specific administrative, regulatory or judicial proceedings; or
      4. +
    4. the onward transfer is necessary in order to protect the vital interests of the data subject or of another natural person.

      5. + Any onward transfer is subject to compliance by the data importer with all the other safeguards under these Clauses, in particular purpose limitation. +
    + +**8.9 Documentation and compliance** + +
      +
    1. The data importer shall promptly and adequately deal with enquiries from the data exporter that relate to the processing under these Clauses.
      2. +
    2. The Parties shall be able to demonstrate compliance with these Clauses. In particular, the data importer shall keep appropriate documentation on the processing activities carried out on behalf of the data exporter.
      3. +
    3. The data importer shall make available to the data exporter all information necessary to demonstrate compliance with the obligations set out in these Clauses and at the data exporter’s request, allow for and contribute to audits of the processing activities covered by these Clauses, at reasonable intervals or if there are indications of non-compliance. In deciding on a review or audit, the data exporter may take into account relevant certifications held by the data importer.
      4. +
    4. The data exporter may choose to conduct the audit by itself or mandate an independent auditor. Audits may include inspections at the premises or physical facilities of the data importer and shall, where appropriate, be carried out with reasonable notice.
      5. +
    5. The Parties shall make the information referred to in paragraphs (b) and (c), including the results of any audits, available to the competent supervisory authority on request.
      6. +
    + +##### Clause 9 + +**Use of sub-processors** + +
      +
    1. GENERAL WRITTEN AUTHORISATION The data importer has the data exporter’s general authorisation for the engagement of sub-processor(s) from an agreed list. The data importer shall specifically inform the data exporter in writing of any intended changes to that list through the addition or replacement of sub-processors at least 90 days in advance, thereby giving the data exporter sufficient time to be able to object to such changes prior to the engagement of the sub-processor(s). The data importer shall provide the data exporter with the information necessary to enable the data exporter to exercise its right to object.
      2. +
    2. Where the data importer engages a sub-processor to carry out specific processing activities (on behalf of the data exporter), it shall do so by way of a written contract that provides for, in substance, the same data protection obligations as those binding the data importer under these Clauses, including in terms of third-party beneficiary rights for data subjects.(2) The Parties agree that, by complying with this Clause, the data importer fulfils its obligations under Clause 8.8. The data importer shall ensure that the sub-processor complies with the obligations to which the data importer is subject pursuant to these Clauses.
      3. +
    3. The data importer shall provide, at the data exporter’s request, a copy of such a sub-processor agreement and any subsequent amendments to the data exporter. To the extent necessary to protect business secrets or other confidential information, including personal data, the data importer may redact the text of the agreement prior to sharing a copy.
      4. +
    4. The data importer shall remain fully responsible to the data exporter for the performance of the sub-processor’s obligations under its contract with the data importer. The data importer shall notify the data exporter of any failure by the sub-processor to fulfil its obligations under that contract.
      5. +
    5. The data importer shall agree a third-party beneficiary clause with the sub-processor whereby – in the event the data importer has factually disappeared, ceased to exist in law or has become insolvent – the data exporter shall have the right to terminate the sub-processor contract and to instruct the sub-processor to erase or return the personal data.
      6. +
    + +##### Clause 10 + +**Data subject rights** + +
      +
    1. The data importer shall promptly notify the data exporter of any request it has received from a data subject. It shall not respond to that request itself unless it has been authorised to do so by the data exporter.
      2. +
    2. The data importer shall assist the data exporter in fulfilling its obligations to respond to data subjects’ requests for the exercise of their rights under Regulation (EU) 2016/679. In this regard, the Parties shall set out in Annex II the appropriate technical and organisational measures, taking into account the nature of the processing, by which the assistance shall be provided, as well as the scope and the extent of the assistance required.
      3. +
    3. In fulfilling its obligations under paragraphs (a) and (b), the data importer shall comply with the instructions from the data exporter.
      4. +
    + +##### Clause 11 + +**Redress** + +
      +
    1. The data importer shall inform data subjects in a transparent and easily accessible format, through individual notice or on its website, of a contact point authorised to handle complaints. It shall deal promptly with any complaints it receives from a data subject.
      2. +
    2. In case of a dispute between a data subject and one of the Parties as regards compliance with these Clauses, that Party shall use its best efforts to resolve the issue amicably in a timely fashion. The Parties shall keep each other informed about such disputes and, where appropriate, cooperate in resolving them.
      3. +
    3. Where the data subject invokes a third-party beneficiary right pursuant to Clause 3, the data importer shall accept the decision of the data subject to:
      4. +
        +
      1. lodge a complaint with the supervisory authority in the Member State of his/her habitual residence or place of work, or the competent supervisory authority pursuant to Clause 13;
        2. +
      2. refer the dispute to the competent courts within the meaning of Clause 18.
        3. +
      +
    4. The Parties accept that the data subject may be represented by a not-for-profit body, organisation or association under the conditions set out in Article 80(1) of Regulation (EU) 2016/679.
      5. +
    5. The data importer shall abide by a decision that is binding under the applicable EU or Member State law.
      6. +
    6. The data importer agrees that the choice made by the data subject will not prejudice his/her substantive and procedural rights to seek remedies in accordance with applicable laws.
      7. +
    + +##### Clause 12 + +**Liability** + +
      +
    1. Each Party shall be liable to the other Party/ies for any damages it causes the other Party/ies by any breach of these Clauses.
      2. +
    2. The data importer shall be liable to the data subject, and the data subject shall be entitled to receive compensation, for any material or non-material damages the data importer or its sub-processor causes the data subject by breaching the third-party beneficiary rights under these Clauses.
      3. +
    3. Notwithstanding paragraph (b), the data exporter shall be liable to the data subject, and the data subject shall be entitled to receive compensation, for any material or non-material damages the data exporter or the data importer (or its sub-processor) causes the data subject by breaching the third-party beneficiary rights under these Clauses. This is without prejudice to the liability of the data exporter and, where the data exporter is a processor acting on behalf of a controller, to the liability of the controller under Regulation (EU) 2016/679 or Regulation (EU) 2018/1725, as applicable.
      4. +
    4. The Parties agree that if the data exporter is held liable under paragraph (c) for damages caused by the data importer (or its sub-processor), it shall be entitled to claim back from the data importer that part of the compensation corresponding to the data importer’s responsibility for the damage.
      5. +
    5. Where more than one Party is responsible for any damage caused to the data subject as a result of a breach of these Clauses, all responsible Parties shall be jointly and severally liable and the data subject is entitled to bring an action in court against any of these Parties.
      6. +
    6. The Parties agree that if one Party is held liable under paragraph (e), it shall be entitled to claim back from the other Party/ies that part of the compensation corresponding to its/their responsibility for the damage.
      7. +
    7. The data importer may not invoke the conduct of a sub-processor to avoid its own liability.
      8. +
    + +##### Clause 13 + +**Supervision** + +
      +
    1. [Where the data exporter is established in an EU Member State:] The supervisory authority with responsibility for ensuring compliance by the data exporter with Regulation (EU) 2016/679 as regards the data transfer, as indicated in Annex I.C, shall act as competent supervisory authority.

      + [Where the data exporter is not established in an EU Member State, but falls within the territorial scope of application of Regulation (EU) 2016/679 in accordance with its Article 3(2) and has appointed a representative pursuant to Article 27(1) of Regulation (EU) 2016/679:] The supervisory authority of the Member State in which the representative within the meaning of Article 27(1) of Regulation (EU) 2016/679 is established, as indicated in Annex I.C, shall act as competent supervisory authority.

      + [Where the data exporter is not established in an EU Member State, but falls within the territorial scope of application of Regulation (EU) 2016/679 in accordance with its Article 3(2) without however having to appoint a representative pursuant to Article 27(2) of Regulation (EU) 2016/679:] The supervisory authority of one of the Member States in which the data subjects whose personal data is transferred under these Clauses in relation to the offering of goods or services to them, or whose behaviour is monitored, are located, as indicated in Annex I.C, shall act as competent supervisory authority.

      2. +
    2. The data importer agrees to submit itself to the jurisdiction of and cooperate with the competent supervisory authority in any procedures aimed at ensuring compliance with these Clauses. In particular, the data importer agrees to respond to enquiries, submit to audits and comply with the measures adopted by the supervisory authority, including remedial and compensatory measures. It shall provide the supervisory authority with written confirmation that the necessary actions have been taken.
      3. +
    + +#### SECTION III – LOCAL LAWS AND OBLIGATIONS IN CASE OF ACCESS BY PUBLIC AUTHORITIES + +##### Clause 14 + +**Local laws and practices affecting compliance with the Clauses** + +
      +
    1. The Parties warrant that they have no reason to believe that the laws and practices in the third country of destination applicable to the processing of the personal data by the data importer, including any requirements to disclose personal data or measures authorising access by public authorities, prevent the data importer from fulfilling its obligations under these Clauses. This is based on the understanding that laws and practices that respect the essence of the fundamental rights and freedoms and do not exceed what is necessary and proportionate in a democratic society to safeguard one of the objectives listed in Article 23(1) of Regulation (EU) 2016/679, are not in contradiction with these Clauses.
      2. +
    2. The Parties declare that in providing the warranty in paragraph (a), they have taken due account in particular of the following elements:
      3. +
        +
      1. the specific circumstances of the transfer, including the length of the processing chain, the number of actors involved and the transmission channels used; intended onward transfers; the type of recipient; the purpose of processing; the categories and format of the transferred personal data; the economic sector in which the transfer occurs; the storage location of the data transferred;
        2. +
      2. the laws and practices of the third country of destination– including those requiring the disclosure of data to public authorities or authorising access by such authorities – relevant in light of the specific circumstances of the transfer, and the applicable limitations and safeguards (3);
        3. +
      3. any relevant contractual, technical or organisational safeguards put in place to supplement the safeguards under these Clauses, including measures applied during transmission and to the processing of the personal data in the country of destination.
        4. +
      +
    3. The data importer warrants that, in carrying out the assessment under paragraph (b), it has made its best efforts to provide the data exporter with relevant information and agrees that it will continue to cooperate with the data exporter in ensuring compliance with these Clauses.
      4. +
    4. The Parties agree to document the assessment under paragraph (b) and make it available to the competent supervisory authority on request.
      5. +
    5. The data importer agrees to notify the data exporter promptly if, after having agreed to these Clauses and for the duration of the contract, it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under paragraph (a), including following a change in the laws of the third country or a measure (such as a disclosure request) indicating an application of such laws in practice that is not in line with the requirements in paragraph (a).
      6. +
    6. Following a notification pursuant to paragraph (e), or if the data exporter otherwise has reason to believe that the data importer can no longer fulfil its obligations under these Clauses, the data exporter shall promptly identify appropriate measures (e.g. technical or organisational measures to ensure security and confidentiality) to be adopted by the data exporter and/or data importer to address the situation. The data exporter shall suspend the data transfer if it considers that no appropriate safeguards for such transfer can be ensured, or if instructed by the competent supervisory authority to do so. In this case, the data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses. If the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise. Where the contract is terminated pursuant to this Clause, Clause 16(d) and (e) shall apply.
      7. +
    + +##### Clause 15 + +**Obligations of the data importer in case of access by public authorities** + +**15.1 Notification** + +
      +
    1. The data importer agrees to notify the data exporter and, where possible, the data subject promptly (if necessary with the help of the data exporter) if it:
      2. +
        +
      1. receives a legally binding request from a public authority, including judicial authorities, under the laws of the country of destination for the disclosure of personal data transferred pursuant to these Clauses; such notification shall include information about the personal data requested, the requesting authority, the legal basis for the request and the response provided; or
        2. +
      2. becomes aware of any direct access by public authorities to personal data transferred pursuant to these Clauses in accordance with the laws of the country of destination; such notification shall include all information available to the importer.
        3. +
      +
    2. If the data importer is prohibited from notifying the data exporter and/or the data subject under the laws of the country of destination, the data importer agrees to use its best efforts to obtain a waiver of the prohibition, with a view to communicating as much information as possible, as soon as possible. The data importer agrees to document its best efforts in order to be able to demonstrate them on request of the data exporter.
      3. +
    3. Where permissible under the laws of the country of destination, the data importer agrees to provide the data exporter, at regular intervals for the duration of the contract, with as much relevant information as possible on the requests received (in particular, number of requests, type of data requested, requesting authority/ies, whether requests have been challenged and the outcome of such challenges, etc.).
      4. +
    4. The data importer agrees to preserve the information pursuant to paragraphs (a) to (c) for the duration of the contract and make it available to the competent supervisory authority on request.
      5. +
    5. Paragraphs (a) to (c) are without prejudice to the obligation of the data importer pursuant to Clause 14(e) and Clause 16 to inform the data exporter promptly where it is unable to comply with these Clauses.
      6. +
    + +**15.2 Review of legality and data minimisation** + +
      +
    1. The data importer agrees to review the legality of the request for disclosure, in particular whether it remains within the powers granted to the requesting public authority, and to challenge the request if, after careful assessment, it concludes that there are reasonable grounds to consider that the request is unlawful under the laws of the country of destination, applicable obligations under international law and principles of international comity. The data importer shall, under the same conditions, pursue possibilities of appeal. When challenging a request, the data importer shall seek interim measures with a view to suspending the effects of the request until the competent judicial authority has decided on its merits. It shall not disclose the personal data requested until required to do so under the applicable procedural rules. These requirements are without prejudice to the obligations of the data importer under Clause 14(e).
      2. +
    2. The data importer agrees to document its legal assessment and any challenge to the request for disclosure and, to the extent permissible under the laws of the country of destination, make the documentation available to the data exporter. It shall also make it available to the competent supervisory authority on request.
      3. +
    3. The data importer agrees to provide the minimum amount of information permissible when responding to a request for disclosure, based on a reasonable interpretation of the request.
      4. +
    + +#### SECTION IV – FINAL PROVISIONS + +##### Clause 16 + +**Non-compliance with the Clauses and termination** + +
      +
    1. The data importer shall promptly inform the data exporter if it is unable to comply with these Clauses, for whatever reason.
      2. +
    2. In the event that the data importer is in breach of these Clauses or unable to comply with these Clauses, the data exporter shall suspend the transfer of personal data to the data importer until compliance is again ensured or the contract is terminated. This is without prejudice to Clause 14(f).
      3. +
    3. The data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses, where:
      4. +
        +
      1. the data exporter has suspended the transfer of personal data to the data importer pursuant to paragraph (b) and compliance with these Clauses is not restored within a reasonable time and in any event within one month of suspension;
        2. +
      2. the data importer is in substantial or persistent breach of these Clauses; or
        3. +
      3. the data importer fails to comply with a binding decision of a competent court or supervisory authority regarding its obligations under these Clauses.
        4. +

      + In these cases, it shall inform the competent supervisory authority of such non-compliance. Where the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise. +
    4. Personal data that has been transferred prior to the termination of the contract pursuant to paragraph (c) shall at the choice of the data exporter immediately be returned to the data exporter or deleted in its entirety. The same shall apply to any copies of the data. The data importer shall certify the deletion of the data to the data exporter. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit the return or deletion of the transferred personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process the data to the extent and for as long as required under that local law.
      5. +
    5. Either Party may revoke its agreement to be bound by these Clauses where (i) the European Commission adopts a decision pursuant to Article 45(3) of Regulation (EU) 2016/679 that covers the transfer of personal data to which these Clauses apply; or (ii) Regulation (EU) 2016/679 becomes part of the legal framework of the country to which the personal data is transferred. This is without prejudice to other obligations applying to the processing in question under Regulation (EU) 2016/679.
      6. +
    + +##### Clause 17 + +**Governing law** + +These Clauses shall be governed by the law of one of the EU Member States, provided such law allows for third-party beneficiary rights. The Parties agree that this shall be the law of the Netherlands. + +##### Clause 18 + +**Choice of forum and jurisdiction** + +
      +
    1. Any dispute arising from these Clauses shall be resolved by the courts of an EU Member State.
      2. +
    2. The Parties agree that those shall be the courts of the Netherlands.
      3. +
    3. A data subject may also bring legal proceedings against the data exporter and/or data importer before the courts of the Member State in which he/she has his/her habitual residence.
      4. +
    4. The Parties agree to submit themselves to the jurisdiction of such courts.
      5. +
    + +## ANNEX I + +**to the Standard Contractual Clauses (EU/EEA)** + +### A. LIST OF PARTIES + +**Data exporter(s)**: Customer is the data exporter
    Name: see GitHub Customer Agreement
    Address: see GitHub Customer Agreement
    Contact person’s name, position and contact details: see GitHub Customer Agreement
    Activities relevant to the data transferred under these Clauses:
    The data exporter is a user of Online Services or Professional Services as defined in the DPA and GitHub Customer Agreement.
    Signature and date: see GitHub Customer Agreement (the DPA and the Standard Contractual Clauses (EU/EEA) are incorporated into the GitHub Customer Agreement
    Role (controller/processor): controller (unless otherwise agreed in the Customer Agreement).
    + +**Data importer(s)**:
    Name: GitHub, Inc.
    Address: 88 Colin P Kelly Jr St, San Francisco, CA 94107, USA
    Contact person’s name, position and contact details: Frances Wiet, Head of Privacy, fwiet@github.com
    Activities relevant to the data transferred under these Clauses:
    GitHub, Inc. is a global producer of software and services
    Signature and date: see GitHub Customer Agreement (the DPA and the Standard Contractual Clauses (EU/EEA) are incorporated into the GitHub Customer Agreement)
    Role (controller/processor): processor or, depending on the agreements set forth in the Customer Agreement, subprocessor. + +### B. DESCRIPTION OF TRANSFER + +_Categories of data subjects whose personal data is transferred:_ + +Data subjects include the data exporter’s representatives and end-users including employees, contractors, collaborators, and customers of the data exporter. Data subjects may also include individuals attempting to communicate or transfer personal data to users of the services provided by data importer. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following types of data subjects in the personal data: +- Employees, contractors and temporary workers (current, former, prospective) of data exporter; +- Data exporter's collaborators/contact persons (natural persons) or employees, contractors or temporary workers of legal entity collaborators/contact persons (current, prospective, former); +- Users and other data subjects that are users of data exporter's services; +- Partners, stakeholders or individuals who actively collaborate, communicate or otherwise interact with employees of the data exporter and/or use communication tools such as apps and websites provided by the data exporter. + +_Categories of personal data transferred:_ + +The personal data transferred that is included in e-mail, documents and other data in an electronic form in the context of the Online Services or Professional Services. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following categories in the personal data: +- Basic personal data (for example place of birth, street name and house number (address), postal code, city of residence, country of residence, mobile phone number, first name, last name, initials, email address, gender, date of birth); +- Authentication data (for example user name, password or PIN code, security question, audit trail); +- Contact information (for example addresses, email, phone numbers, social media identifiers; emergency contact details); +- Unique identification numbers and signatures (for example IP addresses, employee number, student number); +- Pseudonymous identifiers; +- Photos, video and audio; +- Internet activity (for example browsing history, search history, reading and viewing activities); +- Device identification (for example IMEI-number, SIM card number, MAC address); +- Profiling (for example based on observed criminal or anti-social behavior or pseudonymous profiles based on visited URLs, click streams, browsing logs, IP-addresses, domains, apps installed, or profiles based on marketing preferences); +- Special categories of data as voluntarily provided by data subjects (for example racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health, data concerning a natural person’s sex life or sexual orientation, or data relating to criminal convictions or offences); or +- Any other personal data identified in Article 4 of the GDPR. + +_**Sensitive data** transferred (if applicable) and applied restrictions or safeguards that fully take into consideration the nature of the data and the risks involved, such as for instance strict purpose limitation, access restrictions (including access only for staff having followed specialised training), keeping a record of access to the data, restrictions for onward transfers or additional security measures:_
    GitHub does not request or otherwise ask for sensitive data and receives such data only if and when customers or data subjects decide to provide it. + +_**The frequency of the transfer** (e.g. whether the data is transferred on a one-off or continuous basis):_ + +Continuous as part of the Online Services or Professional Services. + +_**Nature of the processing:**_ + +The personal data transferred will be subject to the following basic processing activities: +
      +
    1. Duration and Object of Data Processing. The duration of data processing shall be for the term designated under the applicable GitHub Customer Agreement between data exporter and the data importer. The objective of the data processing is the performance of Online Services and Professional Services.
      2. +
    2. Personal Data Access. For the term designated under the applicable GitHub Customer Agreement, data importer will, at its election and as necessary under applicable law, either: (1) provide data exporter with the ability to correct, delete, or block personal data, or (2) make such corrections, deletions, or blockages on its behalf.
      3. +
    3. Data Exporter’s Instructions. For Online Services and Professional Services, data importer will only act upon data exporter’s instructions.
      4. +
    + +_Purpose(s) of the data transfer and further processing:_ + +The scope and purpose of processing personal data is described in the “Processing of Personal Data; GDPR” section of the DPA. The data importer operates a global network of data centers and management/support facilities, and processing may take place in any jurisdiction where data importer or its sub-processors operate such facilities in accordance with the “Security Practices and Policies” section of the DPA. + +_The period for which the personal data will be retained, or, if that is not possible, the criteria used to determine that period:_ + +Upon expiration or termination of data exporter’s use of Online Services or Professional Services, it may extract personal data and data importer will delete personal data, each in accordance with the DPA Terms applicable to the agreement. + +_For transfers to (sub-) processors, also specify subject matter, nature and duration of the processing:_ + +In accordance with the DPA, the data importer may hire other companies to provide limited services on data importer’s behalf, such as providing customer support. Any such subcontractors will be permitted to obtain personal data only to deliver the services the data importer has retained them to provide, and they are prohibited from using personal data for any other purpose. Unless a particular subcontractor is replaced ahead of time, the processing will be for the term designated under the applicable GitHub Customer Agreement between data exporter and data importer. + +### C. COMPETENT SUPERVISORY AUTHORITY + +_Identify the competent supervisory authority/ies in accordance with Clause 13:_ + +The supervisory authority with responsibility for ensuring compliance by the data exporter with Regulation (EU) 2016/679.   +## ANNEX II + +**to the Standard Contractual Clauses (EU/EEA)** + +**TECHNICAL AND ORGANISATIONAL MEASURES INCLUDING TECHNICAL AND ORGANISATIONAL MEASURES TO ENSURE THE SECURITY OF THE DATA** + +_Description of the technical and organisational measures implemented by the data importer(s) (including any relevant certifications) to ensure an appropriate level of security, taking into account the nature, scope, context and purpose of the processing, and the risks for the rights and freedoms of natural persons._ + +
      +
    1. Data Security Certifications. Data importer holds the following data security certifications:
      2. +
        +
      • SOC 1, Type 2;
        • +
      • SOC 2, Type 2;
        • +
      • NIST, to the extent incorporated for FedRAMP Low-Impact / Tailored ATO.
        • +
      +
    2. Personnel. Data importer’s personnel will not process personal data without authorization. Personnel are obligated to maintain the confidentiality of any such personal data and this obligation continues even after their engagement ends.
      3. +
    3. Data Privacy Contact. The data privacy officer of the data importer can be reached at the following address:

      + GitHub, Inc.
      + Attn: Privacy
      + 88 Colin P. Kelly Jr. Street
      + San Francisco, California 94107 USA

      4. +
    4. Technical and Organization Measures. The data importer has implemented and will maintain appropriate technical and organizational measures, internal controls, and information security routines intended to protect personal data, as defined in the Security Practices and Policies section of the DPA, against accidental loss, destruction, or alteration; unauthorized disclosure or access; or unlawful destruction as follows: The technical and organizational measures, internal controls, and information security routines set forth in the Data Security section of the DPA are hereby incorporated into this Annex II to Attachment 1 by this reference and are binding on the data importer as if they were set forth in this Annex 2 to Attachment 1 in their entirety.
      5. +
    + +_For transfers to (sub-) processors, also describe the specific technical and organisational measures to be taken by the (sub-) processor to be able to provide assistance to the controller and, for transfers from a processor to a sub-processor, to the data exporter:_ + +**Vendor management program - third-party risk program** + +The data importer has a vendor risk assessment process, vendor contract clauses and additional data protection agreements with vendors. Vendors undergo reassessment when a new business use case is requested. The data importer’s vendor risk program is structured so all of data importer’s vendors' risk assessments are refreshed two years from the last review date. + +Vendors deemed high risk, such as data center providers or other vendors storing or processing data in scope for the data importer’s regulatory or contractual requirements, undergo reassessment annually. + +## ANNEX III + +**to the Standard Contractual Clauses (EU/EEA)** + +**Additional Safeguards Addendum** + +By this Additional Safeguards Addendum to Standard Contractual Clauses (EU/EEA) (this “Addendum”), GitHub, Inc. (“GitHub”) provides additional safeguards to Customer and additional redress to the data subjects to whom Customer’s personal data relates. + +This Addendum supplements and is made part of, but is not in variation or modification of, the Standard Contractual Clauses (EU/EEA). + +
      +
    1. Challenges to Orders. In addition to Clause 15.1 of the Standard Contractual Clauses (EU/EEA), in the event GitHub receives an order from any third party for compelled disclosure of any personal data that has been transferred under the Standard Contractual Clauses (EU/EEA), GitHub shall:
      2. +
        +
      1. use every reasonable effort to redirect the third party to request data directly from Customer;
        2. +
      2. promptly notify Customer, unless prohibited under the law applicable to the requesting third party, and, if prohibited from notifying Customer, use all lawful efforts to obtain the right to waive the prohibition in order to communicate as much information to Customer as soon as possible; and
        3. +
      3. use all lawful efforts to challenge the order for disclosure on the basis of any legal deficiencies under the laws of the requesting party or any relevant conflicts with the law of the European Union or applicable Member State law.
        4. +

      + For purpose of this section, lawful efforts do not include actions that would result in civil or criminal penalty such as contempt of court under the laws of the relevant jurisdiction. +
    2. Indemnification of Data Subjects. Subject to Sections 3 and 4, GitHub shall indemnify a data subject for any material or non-material damage to the data subject caused by GitHub’s disclosure of personal data of the data subject that has been transferred under the Standard Contractual Clauses (EU/EEA) in response to an order from a non-EU/EEA government body or law enforcement agency (a “Relevant Disclosure”). Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under this Section 2 to the extent the data subject has already received compensation for the same damage, whether from GitHub or otherwise.
      3. +
    3. Conditions of Indemnification. Indemnification under Section 2 is conditional upon the data subject establishing, to GitHub’s reasonable satisfaction, that:
      4. +
        +
      1. GitHub engaged in a Relevant Disclosure;
        2. +
      2. the Relevant Disclosure was the basis of an official proceeding by the non-EU/EEA government body or law enforcement agency against the data subject; and
        3. +
      3. the Relevant Disclosure directly caused the data subject to suffer material or non-material damage.
        4. +

      + The data subject bears the burden of proof with respect to conditions a. though c.
      + Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under Section 2 if GitHub establishes that the Relevant Disclosure did not violate its obligations under Chapter V of the GDPR.
      +
    4. Scope of Damages. Indemnification under Section 2 is limited to material and non-material damages as provided in the GDPR and excludes consequential damages and all other damages not resulting from GitHub’s infringement of the GDPR.
      5. +
    5. Exercise of Rights. Rights granted to data subjects under this Addendum may be enforced by the data subject against GitHub irrespective of any restriction in Clauses 3 or 12 of the Standard Contractual Clauses (EU/EEA). The data subject may only bring a claim under this Addendum on an individual basis, and not part of a class, collective, group or representative action. Rights granted to data subjects under this Addendum are personal to the data subject and may not be assigned.
      6. +
    6. Notice of Change. In addition to Clause 14 of the Standard Contractual Clauses (EU/EEA), GitHub agrees and warrants that it has no reason to believe that the legislation applicable to it or its sub-processors, including in any country to which personal data is transferred either by itself or through a sub-processor, prevents it from fulfilling the instructions received from the data exporter and its obligations under this Addendum or the Standard Contractual Clauses (EU/EEA) and that in the event of a change in this legislation which is likely to have a substantial adverse effect on the warranties and obligations provided by this Addendum or the Standard Contractual Clauses (EU/EEA), it will promptly notify the change to Customer as soon as it is aware, in which case Customer is entitled to suspend the transfer of data and/or terminate the contract.
      7. +
    7. Termination. This Addendum shall automatically terminate if the European Commission, a competent Member State supervisory authority, or an EU or competent Member State court approves a different lawful transfer mechanism that would be applicable to the data transfers covered by the Standard Contractual Clauses (EU/EEA) (and if such mechanism applies only to some of the data transfers, this Addendum will terminate only with respect to those transfers) and that does not require the additional safeguards set forth in this Addendum.
      8. +
    + +

    Attachment 2 – The Standard Contractual Clauses (UK)

    + +Execution of the GitHub Customer Agreement by Customer includes execution of this Attachment 2, which is countersigned by GitHub, Inc. + +In countries where regulatory approval is required for use of the Standard Contractual Clauses, the Standard Contractual Clauses cannot be relied upon under European Commission 2010/87/EU (of February 2010) to legitimize export of data from the country, unless Customer has the required regulatory approval. + +Beginning May 25, 2018 and thereafter, references to various Articles from the Directive 95/46/EC in the Standard Contractual Clauses below will be treated as references to the relevant and appropriate Articles in the GDPR. + +For the purposes of Article 26(2) of Directive 95/46/EC for the transfer of personal data to processors established in third countries which do not ensure an adequate level of data protection, Customer (as data exporter) and GitHub, Inc. (as data importer, whose signature appears below), each a “party,” together “the parties,” have agreed on the following Contractual Clauses (the “Clauses” or “Standard Contractual Clauses”) in order to adduce adequate safeguards with respect to the protection of privacy and fundamental rights and freedoms of individuals for the transfer by the data exporter to the data importer of the personal data specified in Appendix 1. + +### Clause 1: Definitions + +
      +
    1. 'personal data', 'special categories of data', 'process/processing', 'controller', 'processor', 'data subject' and 'supervisory authority' shall have the same meaning as in Directive 95/46/EC of the European Parliament and of the Council of 24 October 1995 on the protection of individuals with regard to the processing of personal data and on the free movement of such data;
      2. +
    2. 'the data exporter' means the controller who transfers the personal data;
      3. +
    3. 'the data importer' means the processor who agrees to receive from the data exporter personal data intended for processing on his behalf after the transfer in accordance with his instructions and the terms of the Clauses and who is not subject to a third country's system ensuring adequate protection within the meaning of Article 25(1) of Directive 95/46/EC;
      4. +
    4. 'the subprocessor' means any processor engaged by the data importer or by any other subprocessor of the data importer who agrees to receive from the data importer or from any other subprocessor of the data importer personal data exclusively intended for processing activities to be carried out on behalf of the data exporter after the transfer in accordance with his instructions, the terms of the Clauses and the terms of the written subcontract;
      5. +
    5. 'the applicable data protection law' means the legislation protecting the fundamental rights and freedoms of individuals and, in particular, their right to privacy with respect to the processing of personal data applicable to a data controller in the Member State in which the data exporter is established;
      6. +
    6. 'technical and organisational security measures' means those measures aimed at protecting personal data against accidental or unlawful destruction or accidental loss, alteration, unauthorised disclosure or access, in particular where the processing involves the transmission of data over a network, and against all other unlawful forms of processing.
      7. +
    + +### Clause 2: Details of the transfer + +The details of the transfer and in particular the special categories of personal data where applicable are specified in Appendix 1 below which forms an integral part of the Clauses. + +### Clause 3: Third-party beneficiary clause + +
      +
    1. The data subject can enforce against the data exporter this Clause, Clause 4(b) to (i), Clause 5(a) to (e), and (g) to (j), Clause 6(1) and (2), Clause 7, Clause 8(2), and Clauses 9 to 12 as third-party beneficiary.
      2. +
    2. The data subject can enforce against the data importer this Clause, Clause 5(a) to (e) and (g), Clause 6, Clause 7, Clause 8(2), and Clauses 9 to 12, in cases where the data exporter has factually disappeared or has ceased to exist in law unless any successor entity has assumed the entire legal obligations of the data exporter by contract or by operation of law, as a result of which it takes on the rights and obligations of the data exporter, in which case the data subject can enforce them against such entity.
      3. +
    3. The data subject can enforce against the subprocessor this Clause, Clause 5(a) to (e) and (g), Clause 6, Clause 7, Clause 8(2), and Clauses 9 to 12, in cases where both the data exporter and the data importer have factually disappeared or ceased to exist in law or have become insolvent, unless any successor entity has assumed the entire legal obligations of the data exporter by contract or by operation of law as a result of which it takes on the rights and obligations of the data exporter, in which case the data subject can enforce them against such entity. Such third-party liability of the subprocessor shall be limited to its own processing operations under the Clauses.
      4. +
    4. The parties do not object to a data subject being represented by an association or other body if the data subject so expressly wishes and if permitted by national law.
      5. +
    + +### Clause 4: Obligations of the data exporter + +The data exporter agrees and warrants: + +
      +
    1. that the processing, including the transfer itself, of the personal data has been and will continue to be carried out in accordance with the relevant provisions of the applicable data protection law (and, where applicable, has been notified to the relevant authorities of the Member State where the data exporter is established) and does not violate the relevant provisions of that State;
      2. +
    2. that it has instructed and throughout the duration of the personal data processing services will instruct the data importer to process the personal data transferred only on the data exporter's behalf and in accordance with the applicable data protection law and the Clauses;
      3. +
    3. that the data importer will provide sufficient guarantees in respect of the technical and organisational security measures specified in Appendix 2 below;
      4. +
    4. that after assessment of the requirements of the applicable data protection law, the security measures are appropriate to protect personal data against accidental or unlawful destruction or accidental loss, alteration, unauthorised disclosure or access, in particular where the processing involves the transmission of data over a network, and against all other unlawful forms of processing, and that these measures ensure a level of security appropriate to the risks presented by the processing and the nature of the data to be protected having regard to the state of the art and the cost of their implementation;
      5. +
    5. that it will ensure compliance with the security measures;
      6. +
    6. that, if the transfer involves special categories of data, the data subject has been informed or will be informed before, or as soon as possible after, the transfer that its data could be transmitted to a third country not providing adequate protection within the meaning of Directive 95/46/EC;
      7. +
    7. to forward any notification received from the data importer or any subprocessor pursuant to Clause 5(b) and Clause 8(3) to the data protection supervisory authority if the data exporter decides to continue the transfer or to lift the suspension;
      8. +
    8. to make available to the data subjects upon request a copy of the Clauses, with the exception of Appendix 2, and a summary description of the security measures, as well as a copy of any contract for subprocessing services which has to be made in accordance with the Clauses, unless the Clauses or the contract contain commercial information, in which case it may remove such commercial information;
      9. +
    9. that, in the event of subprocessing, the processing activity is carried out in accordance with Clause 11 by a subprocessor providing at least the same level of protection for the personal data and the rights of data subject as the data importer under the Clauses; and
      10. +
    10. that it will ensure compliance with Clause 4(a) to (i).
      11. +
    + +### Clause 5: Obligations of the data importer + +The data importer agrees and warrants: + +
      +
    1. to process the personal data only on behalf of the data exporter and in compliance with its instructions and the Clauses; if it cannot provide such compliance for whatever reasons, it agrees to inform promptly the data exporter of its inability to comply, in which case the data exporter is entitled to suspend the transfer of data and/or terminate the contract;
      2. +
    2. that it has no reason to believe that the legislation applicable to it prevents it from fulfilling the instructions received from the data exporter and its obligations under the contract and that in the event of a change in this legislation which is likely to have a substantial adverse effect on the warranties and obligations provided by the Clauses, it will promptly notify the change to the data exporter as soon as it is aware, in which case the data exporter is entitled to suspend the transfer of data and/or terminate the contract;
      3. +
    3. that it has implemented the technical and organisational security measures specified in Appendix 2 before processing the personal data transferred;
      4. +
    4. that it will promptly notify the data exporter about:
      5. +
        +
      1. any legally binding request for disclosure of the personal data by a law enforcement authority unless otherwise prohibited, such as a prohibition under criminal law to preserve the confidentiality of a law enforcement investigation,
        2. +
      2. any accidental or unauthorised access, and
        3. +
      3. any request received directly from the data subjects without responding to that request, unless it has been otherwise authorised to do so;
        4. +
      + to deal promptly and properly with all inquiries from the data exporter relating to its processing of the personal data subject to the transfer and to abide by the advice of the supervisory authority with regard to the processing of the data transferred; + at the request of the data exporter to submit its data processing facilities for audit of the processing activities covered by the Clauses which shall be carried out by the data exporter or an inspection body composed of independent members and in possession of the required professional qualifications bound by a duty of confidentiality, selected by the data exporter, where applicable, in agreement with the supervisory authority; +
    5. to make available to the data subject upon request a copy of the Clauses, or any existing contract for subprocessing, unless the Clauses or contract contain commercial information, in which case it may remove such commercial information, with the exception of Appendix 2 which shall be replaced by a summary description of the security measures in those cases where the data subject is unable to obtain a copy from the data exporter;
      6. +
    6. that, in the event of subprocessing, it has previously informed the data exporter and obtained its prior written consent;
      7. +
    7. that the processing services by the subprocessor will be carried out in accordance with Clause 11; and
      8. +
    8. to send promptly a copy of any subprocessor agreement it concludes under the Clauses to the data exporter.
      9. +
    + +### Clause 6: Liability + +
      +
    1. The parties agree that any data subject who has suffered damage as a result of any breach of the obligations referred to in Clause 3 or in Clause 11 by any party or subprocessor is entitled to receive compensation from the data exporter for the damage suffered.
      2. + +
    2. If a data subject is not able to bring a claim for compensation in accordance with paragraph 1 against the data exporter, arising out of a breach by the data importer or his subprocessor of any of their obligations referred to in Clause 3 or in Clause 11, because the data exporter has factually disappeared or ceased to exist in law or has become insolvent, the data importer agrees that the data subject may issue a claim against the data importer as if it were the data exporter, unless any successor entity has assumed the entire legal obligations of the data exporter by contract of by operation of law, in which case the data subject can enforce its rights against such entity.

      + The data importer may not rely on a breach by a subprocessor of its obligations in order to avoid its own liabilities.
      3. + +
    3. If a data subject is not able to bring a claim against the data exporter or the data importer referred to in paragraphs 1 and 2, arising out of a breach by the subprocessor of any of their obligations referred to in Clause 3 or in Clause 11 because both the data exporter and the data importer have factually disappeared or ceased to exist in law or have become insolvent, the subprocessor agrees that the data subject may issue a claim against the data subprocessor with regard to its own processing operations under the Clauses as if it were the data exporter or the data importer, unless any successor entity has assumed the entire legal obligations of the data exporter or data importer by contract or by operation of law, in which case the data subject can enforce its rights against such entity. The liability of the subprocessor shall be limited to its own processing operations under the Clauses.
      4. +
    + +### Clause 7: Mediation and jurisdiction + +
      +
    1. The data importer agrees that if the data subject invokes against it third-party beneficiary rights and/or claims compensation for damages under the Clauses, the data importer will accept the decision of the data subject: +
        +
      1. to refer the dispute to mediation, by an independent person or, where applicable, by the supervisory authority; +
      2. to refer the dispute to the courts in the Member State in which the data exporter is established. +
      +
    2. The parties agree that the choice made by the data subject will not prejudice its substantive or procedural rights to seek remedies in accordance with other provisions of national or international law. +
    + +### Clause 8: Cooperation with supervisory authorities + +
      +
    1. The data exporter agrees to deposit a copy of this contract with the supervisory authority if it so requests or if such deposit is required under the applicable data protection law.
      2. + +
    2. The parties agree that the supervisory authority has the right to conduct an audit of the data importer, and of any subprocessor, which has the same scope and is subject to the same conditions as would apply to an audit of the data exporter under the applicable data protection law.
      3. + +
    3. The data importer shall promptly inform the data exporter about the existence of legislation applicable to it or any subprocessor preventing the conduct of an audit of the data importer, or any subprocessor, pursuant to paragraph 2. In such a case the data exporter shall be entitled to take the measures foreseen in Clause 5 (b).
      4. +
    + +### Clause 9: Governing Law. + +The Clauses shall be governed by the law of the Member State in which the data exporter is established. + +### Clause 10: Variation of the contract + +The parties undertake not to vary or modify the Clauses. This does not preclude the parties from adding clauses on business related issues where required as long as they do not contradict the Clause. + +### Clause 11: Subprocessing + +
      +
    1. The data importer shall not subcontract any of its processing operations performed on behalf of the data exporter under the Clauses without the prior written consent of the data exporter. Where the data importer subcontracts its obligations under the Clauses, with the consent of the data exporter, it shall do so only by way of a written agreement with the subprocessor which imposes the same obligations on the subprocessor as are imposed on the data importer under the Clauses. Where the subprocessor fails to fulfil its data protection obligations under such written agreement the data importer shall remain fully liable to the data exporter for the performance of the subprocessor's obligations under such agreement.
      2. + +
    2. The prior written contract between the data importer and the subprocessor shall also provide for a third-party beneficiary clause as laid down in Clause 3 for cases where the data subject is not able to bring the claim for compensation referred to in paragraph 1 of Clause 6 against the data exporter or the data importer because they have factually disappeared or have ceased to exist in law or have become insolvent and no successor entity has assumed the entire legal obligations of the data exporter or data importer by contract or by operation of law. Such third-party liability of the subprocessor shall be limited to its own processing operations under the Clauses.
      3. + +
    3. The provisions relating to data protection aspects for subprocessing of the contract referred to in paragraph 1 shall be governed by the law of the Member State in which the data exporter is established.
      4. + +
    4. The data exporter shall keep a list of subprocessing agreements concluded under the Clauses and notified by the data importer pursuant to Clause 5 (j), which shall be updated at least once a year. The list shall be available to the data exporter's data protection supervisory authority.
      5. +
    + +### Clause 12: Obligation after the termination of personal data processing services + +
      +
    1. The parties agree that on the termination of the provision of data processing services, the data importer and the subprocessor shall, at the choice of the data exporter, return all the personal data transferred and the copies thereof to the data exporter or shall destroy all the personal data and certify to the data exporter that it has done so, unless legislation imposed upon the data importer prevents it from returning or destroying all or part of the personal data transferred. In that case, the data importer warrants that it will guarantee the confidentiality of the personal data transferred and will not actively process the personal data transferred anymore.
      2. + +
    2. The data importer and the subprocessor warrant that upon request of the data exporter and/or of the supervisory authority, it will submit its data processing facilities for an audit of the measures referred to in paragraph 1.
      3. +
    + +### Appendix 1 to the Standard Contractual Clauses (UK) + +**Data exporter**: Customer is the data exporter. The data exporter is a user of Online Services or Professional Services as defined in the DPA and GitHub Customer Agreement. + +**Data importer**: The data importer is GitHub, Inc., a global producer of software and services. + +**Data subjects**: Data subjects include the data exporter’s representatives and end-users including employees, contractors, collaborators, and customers of the data exporter. Data subjects may also include individuals attempting to communicate or transfer personal data to users of the services provided by data importer. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following types of data subjects in the personal data: +- Employees, contractors and temporary workers (current, former, prospective) of data exporter; +- Data exporter's collaborators/contact persons (natural persons) or employees, contractors or temporary workers of legal entity collaborators/contact persons (current, prospective, former); +- Users and other data subjects that are users of data exporter's services; +- Partners, stakeholders or individuals who actively collaborate, communicate or otherwise interact with employees of the data exporter and/or use communication tools such as apps and websites provided by the data exporter. + +**Categories of data**: The personal data transferred that is included in e-mail, documents and other data in an electronic form in the context of the Online Services or Professional Services. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following categories in the personal data: +- Basic personal data (for example place of birth, street name and house number (address), postal code, city of residence, country of residence, mobile phone number, first name, last name, initials, email address, gender, date of birth); +- Authentication data (for example user name, password or PIN code, security question, audit trail); +- Contact information (for example addresses, email, phone numbers, social media identifiers; emergency contact details); +- Unique identification numbers and signatures (for example IP addresses, employee number, student number); +- Pseudonymous identifiers; +- Photos, video and audio; +- Internet activity (for example browsing history, search history, reading and viewing activities); +- Device identification (for example IMEI-number, SIM card number, MAC address); +- Profiling (for example based on observed criminal or anti-social behavior or pseudonymous profiles based on visited URLs, click streams, browsing logs, IP-addresses, domains, apps installed, or profiles based on marketing preferences); +- Special categories of data as voluntarily provided by data subjects (for example racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health, data concerning a natural person’s sex life or sexual orientation, or data relating to criminal convictions or offences); or +- Any other personal data identified in Article 4 of the GDPR. + +**Processing operations**: The personal data transferred will be subject to the following basic processing activities: + +
      +
    1. Duration and Object of Data Processing. The duration of data processing shall be for the term designated under the applicable GitHub Customer Agreement between data exporter and data importer. The objective of the data processing is the performance of Online Services and Professional Services.
      2. +
    2. Scope and Purpose of Data Processing. The scope and purpose of processing personal data is described in the “Processing of Personal Data; GDPR” section of the DPA. The data importer operates a global network of data centers and management/support facilities, and processing may take place in any jurisdiction where data importer or its sub-processors operate such facilities in accordance with the “Security Practices and Policies” section of the DPA.
      3. +
    3. Personal Data Access. For the term designated under the applicable GitHub Customer Agreement data importer will at its election and as necessary under applicable law, either: (1) provide data exporter with the ability to correct, delete, or block personal data, or (2) make such corrections, deletions, or blockages on its behalf.
      4. +
    4. Data Exporter’s Instructions. For Online Services and Professional Services, data importer will only act upon data exporter’s instructions as conveyed by GitHub.
      5. +
    5. Personal Data Deletion or Return. Upon expiration or termination of data exporter’s use of Online Services or Professional Services, it may extract personal data and data importer will delete personal data, each in accordance with the DPA Terms applicable to the agreement.
      6. +
    + +**Subcontractors**: In accordance with the DPA, the data importer may hire other companies to provide limited services on data importer’s behalf, such as providing customer support. Any such subcontractors will be permitted to obtain personal data only to deliver the services the data importer has retained them to provide, and they are prohibited from using personal data for any other purpose. + +### Appendix 2 to the Standard Contractual Clauses (UK) + +Description of the technical and organizational security measures implemented by the data importer in accordance with Clauses 4(d) and 5(c): + +
      +
    1. Personnel. Data importer’s personnel will not process personal data without authorization. Personnel are obligated to maintain the confidentiality of any such personal data and this obligation continues even after their engagement ends.
      2. + +
    2. Data Privacy Contact. The data privacy officer of the data importer can be reached at the following address:
      +GitHub, Inc.
      +Attn: Privacy
      +88 Colin P. Kelly Jr. Street
      +San Francisco, California 94107 USA
      3. + +
    3. Technical and Organization Measures. The data importer has implemented and will maintain appropriate technical and organizational measures, internal controls, and information security routines intended to protect personal data, as defined in the Security Practices and Policies section of the DPA, against accidental loss, destruction, or alteration; unauthorized disclosure or access; or unlawful destruction as follows: The technical and organizational measures, internal controls, and information security routines set forth in the Security Practices and Policies section of the DPA are hereby incorporated into this Appendix 2 by this reference and are binding on the data importer as if they were set forth in this Appendix 2 in their entirety.
      4. +
    + +### Appendix 3 to the Standard Contractual Clauses (UK) + +**Additional Safeguards Addendum** + +By this Additional Safeguards Addendum to Standard Contractual Clauses (UK) (this “Addendum”), GitHub, Inc. (“GitHub”) provides additional safeguards to Customer and additional redress to the data subjects to whom Customer’s personal data relates. + +This Addendum supplements and is made part of, but is not in variation or modification of, the Standard Contractual Clauses (UK). + +
      +
    1. Challenges to Orders. In addition to Clause 5(d)(i) of the Standard Contractual Clauses (UK), in the event GitHub receives an order from any third party for compelled disclosure of any personal data that has been transferred under the Standard Contractual Clauses (UK), GitHub shall:
      2. +
        +
      1. use every reasonable effort to redirect the third party to request data directly from Customer;
        2. +
      2. promptly notify Customer, unless prohibited under the law applicable to the requesting third party, and, if prohibited from notifying Customer, use all lawful efforts to obtain the right to waive the prohibition in order to communicate as much information to Customer as soon as possible; and
        3. +
      3. use all lawful efforts to challenge the order for disclosure on the basis of any legal deficiencies under the laws of the requesting party or any relevant conflicts with the law of the European Union or applicable Member State law.
        4. +

      + For purpose of this section, lawful efforts do not include actions that would result in civil or criminal penalty such as contempt of court under the laws of the relevant jurisdiction. +
    2. Indemnification of Data Subjects. Subject to Sections 3 and 4, GitHub shall indemnify a data subject for any material or non-material damage to the data subject caused by GitHub’s disclosure of personal data of the data subject that has been transferred under the Standard Contractual Clauses (UK) in response to an order from a non-EU/EEA government body or law enforcement agency (a “Relevant Disclosure”). Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under this Section 2 to the extent the data subject has already received compensation for the same damage, whether from GitHub or otherwise.
      3. +
    3. Conditions of Indemnification. Indemnification under Section 2 is conditional upon the data subject establishing, to GitHub’s reasonable satisfaction, that:
      4. +
        +
      1. GitHub engaged in a Relevant Disclosure;
        2. +
      2. the Relevant Disclosure was the basis of an official proceeding by the non-EU/EEA government body or law enforcement agency against the data subject; and
        3. +
      3. the Relevant Disclosure directly caused the data subject to suffer material or non-material damage.
        4. +

      + The data subject bears the burden of proof with respect to conditions a. though c.
      + Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under Section 2 if GitHub establishes that the Relevant Disclosure did not violate its obligations under Chapter V of the GDPR. +
    4. Scope of Damages. Indemnification under Section 2 is limited to material and non-material damages as provided in the GDPR and excludes consequential damages and all other damages not resulting from GitHub’s infringement of the GDPR.
      5. +
    5. Exercise of Rights. Rights granted to data subjects under this Addendum may be enforced by the data subject against GitHub irrespective of any restriction in Clauses 3 or 6 of the Standard Contractual Clauses (UK). The data subject may only bring a claim under this Addendum on an individual basis, and not part of a class, collective, group or representative action. Rights granted to data subjects under this Addendum are personal to the data subject and may not be assigned.
      6. +
    6. Notice of Change. In addition to Clause 5(b) of the Standard Contractual Clauses (UK), GitHub agrees and warrants that it has no reason to believe that the legislation applicable to it or its sub-processors, including in any country to which personal data is transferred either by itself or through a sub-processor, prevents it from fulfilling the instructions received from the data exporter and its obligations under this Addendum or the Standard Contractual Clauses (UK) and that in the event of a change in this legislation which is likely to have a substantial adverse effect on the warranties and obligations provided by this Addendum or the Standard Contractual Clauses (UK), it will promptly notify the change to Customer as soon as it is aware, in which case Customer is entitled to suspend the transfer of data and/or terminate the contract. +
    7. Termination. This Addendum shall automatically terminate if the European Commission, a competent Member State supervisory authority, or an EU or competent Member State court approves a different lawful transfer mechanism that would be applicable to the data transfers covered by the Standard Contractual Clauses (UK) (and if such mechanism applies only to some of the data transfers, this Addendum will terminate only with respect to those transfers) and that does not require the additional safeguards set forth in this Addendum.

      + Signing the Standard Contractual Clauses (UK), Appendix 1, Appendix 2 and +
    + +

    Attachment 3 – European Union General Data Protection Regulation Terms

    + +GitHub makes the commitments in these GDPR Related Terms, to all customers effective May 25, 2018. These commitments are binding upon GitHub with regard to Customer regardless of (1) the version of the GitHub Customer Agreement and DPA that is otherwise applicable to any given Online Services subscription or (2) any other agreement that references this attachment. + +For purposes of these GDPR Related Terms, Customer and GitHub agree that Customer is the controller of Personal Data and GitHub is the processor of such data, except when Customer acts as a processor of Personal Data, in which case GitHub is a subprocessor. These GDPR Related Terms apply to the processing of Personal Data, within the scope of the GDPR, by GitHub on behalf of Customer. These GDPR Related Terms do not limit or reduce any data protection commitments GitHub makes to Customer in the GitHub Customer Agreement or other agreement between GitHub and Customer. These GDPR Related Terms do not apply where GitHub is a controller of Personal Data. + +**Relevant GDPR Obligations: Articles 28, 32, and 33** + +
      +
    1. GitHub shall not engage another processor without prior specific or general written authorisation of Customer. In the case of general written authorisation, GitHub shall inform Customer of any intended changes concerning the addition or replacement of other processors, thereby giving Customer the opportunity to object to such changes. (Article 28(2))
      2. +
    2. Processing by GitHub shall be governed by these GDPR Related Terms under European Union (hereafter “Union”) or Member State law and are binding on GitHub with regard to Customer. The subject-matter and duration of the processing, the nature and purpose of the processing, the type of Personal Data, the categories of data subjects and the obligations and rights of the Customer are set forth in the Customer’s licensing agreement, including these GDPR Related Terms. In particular, GitHub shall:
      3. +
        +
      1. process the Personal Data only on documented instructions from Customer, including with regard to transfers of Personal Data to a third country or an international organisation, unless required to do so by Union or Member State law to which GitHub is subject; in such a case, GitHub shall inform Customer of that legal requirement before processing, unless that law prohibits such information on important grounds of public interest;
        2. +
      2. ensure that persons authorised to process the Personal Data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality;
        3. +
      3. take all measures required pursuant to Article 32 of the GDPR;
        4. +
      4. respect the conditions referred to in paragraphs 1 and 3 for engaging another processor;
        5. +
      5. taking into account the nature of the processing, assist Customer by appropriate technical and organisational measures, insofar as this is possible, for the fulfilment of the Customer’s obligation to respond to requests for exercising the data subject's rights laid down in Chapter III of the GDPR;
        6. +
      6. assist Customer in ensuring compliance with the obligations pursuant to Articles 32 to 36 of the GDPR, taking into account the nature of processing and the information available to GitHub;
        7. +
      7. at the choice of Customer, delete or return all the Personal Data to Customer after the end of the provision of services relating to processing, and delete existing copies unless Union or Member State law requires storage of the Personal Data;
        8. +
      8. make available to Customer all information necessary to demonstrate compliance with the obligations laid down in Article 28 of the GDPR and allow for and contribute to audits, including inspections, conducted by Customer or another auditor mandated by Customer.
        9. +

      + GitHub shall immediately inform Customer if, in its opinion, an instruction infringes the GDPR or other Union or Member State data protection provisions. (Article 28(3))

      +
    3. Where GitHub engages another processor for carrying out specific processing activities on behalf of Customer, the same data protection obligations as set out in these GDPR Related Terms shall be imposed on that other processor by way of a contract or other legal act under Union or Member State law, in particular providing sufficient guarantees to implement appropriate technical and organisational measures in such a manner that the processing will meet the requirements of the GDPR. Where that other processor fails to fulfil its data protection obligations, GitHub shall remain fully liable to the Customer for the performance of that other processor's obligations. (Article 28(4))
      4. +
    4. Taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of processing as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons, Customer and GitHub shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, including inter alia as appropriate:
      5. +
        +
      1. the pseudonymisation and encryption of Personal Data;
        2. +
      2. the ability to ensure the ongoing confidentiality, integrity, availability and resilience of processing systems and services;
        3. +
      3. the ability to restore the availability and access to Personal Data in a timely manner in the event of a physical or technical incident; and
        4. +
      4. a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the processing. (Article 32(1))
        5. +
      +
    5. In assessing the appropriate level of security, account shall be taken of the risks that are presented by processing, in particular from accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to Personal Data transmitted, stored or otherwise processed (Article 32(2)).
      6. +
    6. Customer and GitHub shall take steps to ensure that any natural person acting under the authority of Customer or GitHub who has access to Personal Data does not process them except on instructions from Customer, unless he or she is required to do so by Union or Member State law (Article 32(4)).
      7. +
    7. GitHub shall notify Customer without undue delay after becoming aware of a Personal Data breach (Article 33(2)). Such notification will include that information a processor must provide to a controller under Article 33(3) to the extent such information is reasonably available to GitHub.
      8. +
    + +--------------- + +

    (1) The Agreement on the European Economic Area (EEA Agreement) provides for the extension of the European Union’s internal market to the three EEA States Iceland, Liechtenstein and Norway. The Union data protection legislation, including Regulation (EU) 2016/679, is covered by the EEA Agreement and has been incorporated into Annex XI thereto. Therefore, any disclosure by the data importer to a third party located in the EEA does not qualify as an onward transfer for the purpose of these Clauses.

    + +

    (2) This requirement may be satisfied by the sub-processor acceding to these Clauses under the appropriate Module, in accordance with Clause 7.

    + +

    (3) As regards the impact of such laws and practices on compliance with these Clauses, different elements may be considered as part of an overall assessment. Such elements may include relevant and documented practical experience with prior instances of requests for disclosure from public authorities, or the absence of such requests, covering a sufficiently representative time-frame. This refers in particular to internal records or other documentation, drawn up on a continuous basis in accordance with due diligence and certified at senior management level, provided that this information can be lawfully shared with third parties. Where this practical experience is relied upon to conclude that the data importer will not be prevented from complying with these Clauses, it needs to be supported by other relevant, objective elements, and it is for the Parties to consider carefully whether these elements together carry sufficient weight, in terms of their reliability and representativeness, to support this conclusion. In particular, the Parties have to take into account whether their practical experience is corroborated and not contradicted by publicly available or otherwise accessible, reliable information on the existence or absence of requests within the same sector and/or the application of the law in practice, such as case law and reports by independent oversight bodies.

    diff --git a/translations/ru-RU/content/github/site-policy/github-terms-for-additional-products-and-features.md b/translations/ru-RU/content/github/site-policy/github-terms-for-additional-products-and-features.md index 1765ec8989..1ada6b768c 100644 --- a/translations/ru-RU/content/github/site-policy/github-terms-for-additional-products-and-features.md +++ b/translations/ru-RU/content/github/site-policy/github-terms-for-additional-products-and-features.md @@ -20,7 +20,7 @@ By using the Additional Products and Features, you also agree to the applicable - **GitHub Enterprise Server** users may have access to the following Additional Products and Features: Actions, Advanced Security, Advisory Database, Connect, Dependabot Preview, Learning Lab, Octoshift, Packages, Pages and SQL Server Images. -- **GitHub AE** users may have access to the following Additional Products and Features: Actions, Advanced Security, Advisory Database, {% ifversion ghae-next %}Connect, {% endif %}Dependabot Preview, Octoshift, Packages and Pages. +- **GitHub AE** users may have access to the following Additional Products and Features: Actions, Advanced Security, Advisory Database,{% ifversion ghae-next %}Connect, {% endif %}Dependabot Preview, Octoshift, Packages and Pages. ## Actions GitHub Actions enables you to create custom software development lifecycle workflows directly in your GitHub repository. Actions is billed on a usage basis. The [Actions documentation](/actions) includes details, including compute and storage quantities (depending on your Account plan), and how to monitor your Actions minutes usage and set usage limits. @@ -38,7 +38,7 @@ In order to prevent violations of these limitations and abuse of GitHub Actions, ## Advanced Security GitHub makes extra security features available to customers under an Advanced Security license. These features include code scanning, secret scanning, and dependency review. The [Advanced Security documentation](/github/getting-started-with-github/about-github-advanced-security) provides more details. -Advanced Security is licensed on a "Unique Committer" basis. A "Unique Committer" is a licensed user of GitHub Enterprise, GitHub Enterprise Cloud, GitHub Enterprise Server, or GitHub AE, who has made a code commit in the last 90 days to any repository with any GitHub Advanced Security functionality activated. You must acquire a GitHub Advanced Security User license for each of your Unique Committers. You may only use GitHub Advanced Security on codebases that are developed by or for you. For GitHub Enterprise Cloud users, some Advanced Security features also require the use of GitHub Actions. +Advanced Security is licensed on a "Unique Committer" basis. A "Unique Committer" is a licensed user of GitHub Enterprise, GitHub Enterprise Cloud, GitHub Enterprise Server, or GitHub AE, who has made a commit in the last 90 days to any repository with any GitHub Advanced Security functionality activated. You must acquire a GitHub Advanced Security User license for each of your Unique Committers. You may only use GitHub Advanced Security on codebases that are developed by or for you. For GitHub Enterprise Cloud users, some Advanced Security features also require the use of GitHub Actions. ## Advisory Database The GitHub Advisory Database allows you to browse or search for vulnerabilities that affect open source projects on GitHub. diff --git a/translations/ru-RU/content/github/site-policy/index.md b/translations/ru-RU/content/github/site-policy/index.md index b4ea2b422b..80677f1a31 100644 --- a/translations/ru-RU/content/github/site-policy/index.md +++ b/translations/ru-RU/content/github/site-policy/index.md @@ -12,7 +12,7 @@ children: - /github-terms-of-service - /github-corporate-terms-of-service - /github-privacy-statement - - /github-data-protection-agreement-non-enterprise-customers + - /github-data-protection-agreement - /global-privacy-practices - /github-sponsors-additional-terms - /github-codespaces-privacy-statement diff --git a/translations/ru-RU/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md b/translations/ru-RU/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md index 36cf4b4390..ade7ddd75b 100644 --- a/translations/ru-RU/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md +++ b/translations/ru-RU/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md @@ -1,6 +1,7 @@ --- title: Creating gists intro: 'You can create two kinds of gists: {% ifversion ghae %}internal{% else %}public{% endif %} and secret. Create {% ifversion ghae %}an internal{% else %}a public{% endif %} gist if you''re ready to share your ideas with {% ifversion ghae %}enterprise members{% else %}the world{% endif %} or a secret gist if you''re not.' +permissions: '{% data reusables.enterprise-accounts.emu-permission-gist %}' redirect_from: - /articles/about-gists/ - /articles/cannot-delete-an-anonymous-gist/ @@ -42,7 +43,7 @@ You can pin gists to your profile so other people can see them easily. For more {% endif %} -You can discover {% ifversion ghae %}internal{% else %}public{% endif %} gists others have created by going to the {% data variables.gists.gist_homepage %} and clicking **All Gists**. This will take you to a page of all gists sorted and displayed by time of creation or update. You can also search gists by language with {% data variables.gists.gist_search_url %}. Gist search uses the same search syntax as [code search](/articles/searching-code). +You can discover {% ifversion ghae %}internal{% else %}public{% endif %} gists others have created by going to the {% data variables.gists.gist_homepage %} and clicking **All Gists**. This will take you to a page of all gists sorted and displayed by time of creation or update. You can also search gists by language with {% data variables.gists.gist_search_url %}. Gist search uses the same search syntax as [code search](/search-github/searching-on-github/searching-code). Since gists are Git repositories, you can view their full commit history, complete with diffs. You can also fork or clone gists. For more information, see ["Forking and cloning gists"](/articles/forking-and-cloning-gists). diff --git a/translations/ru-RU/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md b/translations/ru-RU/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md index 94e12c96b9..35202d29ce 100644 --- a/translations/ru-RU/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md +++ b/translations/ru-RU/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md @@ -1,6 +1,7 @@ --- title: Forking and cloning gists intro: 'Gists are actually Git repositories, which means that you can fork or clone any gist, even if you aren''t the original author. You can also view a gist''s full commit history, including diffs.' +permissions: '{% data reusables.enterprise-accounts.emu-permission-gist %}' redirect_from: - /articles/forking-and-cloning-gists - /github/writing-on-github/forking-and-cloning-gists diff --git a/translations/ru-RU/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md b/translations/ru-RU/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md index 4685ac8fc8..bab8976145 100644 --- a/translations/ru-RU/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md +++ b/translations/ru-RU/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md @@ -40,9 +40,9 @@ You can indicate emphasis with bold, italic, or strikethrough text in comment fi You can quote text with a `>`. ```markdown -In the words of Abraham Lincoln: +Text that is not a quote -> Pardon my French +> Text that is a quote ``` ![Rendered quoted text](/assets/images/help/writing/quoted-text-rendered.png) @@ -184,7 +184,7 @@ In this example, you could add a nested list item under the list item `100. Firs ![List with a nested list item](/assets/images/help/writing/nested-list-example-3.png) -You can create multiple levels of nested lists using the same method. For example, because the first nested list item has seven spaces (`␣␣␣␣␣-␣`) before the nested list content `First nested list item`, you would need to indent the second nested list item by seven spaces. +You can create multiple levels of nested lists using the same method. For example, because the first nested list item has seven characters (`␣␣␣␣␣-␣`) before the nested list content `First nested list item`, you would need to indent the second nested list item by seven spaces. ```markdown 100. First list item @@ -262,6 +262,30 @@ 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-next or ghes > 3.3 %} +## Footnotes + +You can add footnotes to your content by using this bracket syntax: + +``` +Here is a simple footnote[^1]. + +[^1]: My reference. +``` + +The footnote will render like this: + +![Rendered footnote](/assets/images/site/rendered-footnote.png) +{% endif %} + +## Hiding content with comments + +You can tell {% data variables.product.product_name %} to hide content from the rendered Markdown by placing the content in an HTML comment. + +
    +<!-- This content will not appear in the rendered Markdown -->
+
    + ## Ignoring Markdown formatting You can tell {% data variables.product.product_name %} to ignore (or escape) Markdown formatting by using `\` before the Markdown character. @@ -272,13 +296,13 @@ You can tell {% data variables.product.product_name %} to ignore (or escape) Mar For more information, see Daring Fireball's "[Markdown Syntax](https://daringfireball.net/projects/markdown/syntax#backslash)." -## Hiding content with comments +{% ifversion fpt or ghes > 3.2 or ghae-issue-5232 %} -You can tell {% data variables.product.product_name %} to hide content from the rendered Markdown by placing the content in an HTML comment. +## Disabling Markdown rendering -
    -<!-- This content will not appear in the rendered Markdown -->
-
    +{% data reusables.repositories.disabling-markdown-rendering %} + +{% endif %} ## Дополнительная литература diff --git a/translations/ru-RU/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md b/translations/ru-RU/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md index 69e20a133a..42dde65c04 100644 --- a/translations/ru-RU/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md +++ b/translations/ru-RU/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md @@ -16,7 +16,7 @@ topics: {% warning %} -**Warning:** If you add an image {% ifversion fpt or ghes > 3.1 or ghae-next %} or video {% endif %} to a pull request or issue comment, anyone can view the anonymized URL without authentication, even if the pull request is in a private repository{% ifversion ghes %}, or if private mode is enabled{% endif %}. To keep sensitive media files private, serve them from a private network or server that requires authentication. {% ifversion fpt %}For more information on anonymized URLs see "[About anonymized URLs](/github/authenticating-to-github/about-anonymized-urls)".{% endif %} +**Warning:** If you add an image{% ifversion fpt or ghes > 3.1 or ghae-next %} or video{% endif %} to a pull request or issue comment, anyone can view the anonymized URL without authentication, even if the pull request is in a private repository{% ifversion ghes %}, or if private mode is enabled{% endif %}. To keep sensitive media files private, serve them from a private network or server that requires authentication. {% ifversion fpt %}For more information on anonymized URLs see "[About anonymized URLs](/github/authenticating-to-github/about-anonymized-urls)".{% endif %} {% endwarning %} @@ -31,9 +31,10 @@ To attach a file to an issue or pull request conversation, drag and drop it into {% endtip %} The maximum file size is: -- 10MB for images and gifs{% ifversion fpt or ghes > 3.1 or ghae-next %} +- 10MB for images and gifs{% ifversion fpt %} - 10MB for videos uploaded to a repository owned by a user or organization on a free GitHub plan -- 100MB for videos uploaded to a repository owned by a user or organization on a paid GitHub plan{% endif %} +- 100MB for videos uploaded to a repository owned by a user or organization on a paid GitHub plan{% elsif fpt or ghes > 3.1 or ghae-next %} +- 100MB for videos{% endif %} - 25MB for all other files We support these files: diff --git a/translations/ru-RU/content/graphql/guides/managing-enterprise-accounts.md b/translations/ru-RU/content/graphql/guides/managing-enterprise-accounts.md index 41736af9c0..fda55d7213 100644 --- a/translations/ru-RU/content/graphql/guides/managing-enterprise-accounts.md +++ b/translations/ru-RU/content/graphql/guides/managing-enterprise-accounts.md @@ -58,8 +58,9 @@ For some example queries, see "[An example query using the Enterprise Accounts A - `admin:enterprise` The enterprise account specific scopes are: - - `admin:enterprise`: Gives full control of enterprises (includes `manage_billing:enterprise` and `read:enterprise`) - - `manage_billing:enterprise`: Read and write enterprise billing data. + - `admin:enterprise`: Gives full control of enterprises (includes {% ifversion ghes > 3.2 or fpt or ghae %}`manage_runners:enterprise`, {% endif %}`manage_billing:enterprise` and `read:enterprise`) + - `manage_billing:enterprise`: Read and write enterprise billing data.{% ifversion ghes > 3.2 or fpt or ghae %} + - `manage_runners:enterprise`: Access to manage GitHub Actions enterprise runners and runner-groups.{% endif %} - `read:enterprise`: Read enterprise profile data. 4. Copy your personal access token and keep it in a secure place until you add it to your GraphQL client. diff --git a/translations/ru-RU/content/graphql/guides/using-the-graphql-api-for-discussions.md b/translations/ru-RU/content/graphql/guides/using-the-graphql-api-for-discussions.md index df30c4c4e8..bc6676948a 100644 --- a/translations/ru-RU/content/graphql/guides/using-the-graphql-api-for-discussions.md +++ b/translations/ru-RU/content/graphql/guides/using-the-graphql-api-for-discussions.md @@ -1080,4 +1080,4 @@ Return type fields: ## Поиск -Discussion may be returned from the top-level `search` field. To search for discussion, specify `type` as `DISCUSSION`. The `SearchResultItemConnection` type has a `discussionCount` field to report the number of returned discussions, and the `Discussion` type is added to the `SearchResultItem` union. For more information, see "[Queries](/graphql/reference/queries#searchresultitemconnection)" and "[Searching discussions](/github/searching-for-information-on-github/searching-discussions)." +Discussion may be returned from the top-level `search` field. To search for discussion, specify `type` as `DISCUSSION`. The `SearchResultItemConnection` type has a `discussionCount` field to report the number of returned discussions, and the `Discussion` type is added to the `SearchResultItem` union. For more information, see "[Queries](/graphql/reference/queries#searchresultitemconnection)" and "[Searching discussions](/search-github/searching-on-github/searching-discussions)." diff --git a/translations/ru-RU/content/index.md b/translations/ru-RU/content/index.md index 12ab7e6cd6..3a7fea8970 100644 --- a/translations/ru-RU/content/index.md +++ b/translations/ru-RU/content/index.md @@ -27,6 +27,7 @@ children: - actions - codespaces - packages + - search-github - developers - rest - graphql diff --git a/translations/ru-RU/content/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users.md b/translations/ru-RU/content/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users.md index b0e9bce98e..bca45dff11 100644 --- a/translations/ru-RU/content/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users.md +++ b/translations/ru-RU/content/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users.md @@ -1,6 +1,7 @@ --- title: Assigning issues and pull requests to other GitHub users intro: Assignees clarify who is working on specific issues and pull requests. +permissions: 'Anyone with write access to a repository can assign issues and pull requests. {% data reusables.enterprise-accounts.emu-permission-repo %}' redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/assigning-issues-and-pull-requests-to-other-github-users - /articles/assigning-issues-and-pull-requests-to-other-github-users @@ -15,8 +16,6 @@ topics: shortTitle: Assign issues & PRs --- -Anyone with write permissions to a repository can assign issues and pull requests. - ## About issue and pull request assignees You can assign up to 10 people to each issue or pull request, including yourself, anyone who has commented on the issue or pull request, anyone with write permissions to the repository, and organization members with read permissions to the repository. For more information, see "[Access permissions on {% data variables.product.prodname_dotcom %}](/articles/access-permissions-on-github)." diff --git a/translations/ru-RU/content/issues/tracking-your-work-with-issues/creating-an-issue.md b/translations/ru-RU/content/issues/tracking-your-work-with-issues/creating-an-issue.md index 1b7e2bf889..3cdb48a2e2 100644 --- a/translations/ru-RU/content/issues/tracking-your-work-with-issues/creating-an-issue.md +++ b/translations/ru-RU/content/issues/tracking-your-work-with-issues/creating-an-issue.md @@ -1,7 +1,7 @@ --- title: Creating an issue intro: 'Issues can be created in a variety of ways, so you can choose the most convenient method for your workflow.' -permissions: People with read permissions can create an issue in a repository where issues are enabled. +permissions: 'People with read access can create an issue in a repository where issues are enabled. {% data reusables.enterprise-accounts.emu-permission-repo %}' redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/creating-an-issue - /articles/creating-an-issue diff --git a/translations/ru-RU/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md b/translations/ru-RU/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md index da2fa42ecd..802bd13108 100644 --- a/translations/ru-RU/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md +++ b/translations/ru-RU/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md @@ -102,7 +102,8 @@ You can filter a repository's list of pull requests to find: - Pull requests that [require a review](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging) before they can be merged - Pull requests that a reviewer has approved - Pull requests in which a reviewer has asked for changes -- Pull requests that you have reviewed +- Pull requests that you have reviewed{% ifversion fpt or ghae or ghes > 3.2 %} +- Pull requests that someone has asked you directly to review{% endif %} - Pull requests that [someone has asked you, or a team you're a member of, to review](/articles/requesting-a-pull-request-review) {% data reusables.repositories.navigate-to-repo %} @@ -185,7 +186,8 @@ For pull requests, you can also use search to: - Filter pull requests that a reviewer has approved: `state:open type:pr review:approved` - Filter pull requests in which a reviewer has asked for changes: `state:open type:pr review:changes_requested` - 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](/articles/requesting-a-pull-request-review): `state:open type:pr review-requested:octocat` +- Filter pull requests by the specific user [requested for review](/articles/requesting-a-pull-request-review): `state:open type:pr review-requested:octocat`{% ifversion fpt or ghae or ghes > 3.2 %} +- 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 %} - Filter for pull requests that are linked to an issue that the pull request may close: `linked:issue`{% endif %} diff --git a/translations/ru-RU/content/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository.md b/translations/ru-RU/content/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository.md index 6d5db5b0f7..82597e6202 100644 --- a/translations/ru-RU/content/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository.md +++ b/translations/ru-RU/content/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository.md @@ -1,6 +1,7 @@ --- title: Pinning an issue to your repository intro: You can pin up to three important issues above the issues list in your repository. +permissions: People with write access to a repository can pin issue in the repository. {% data reusables.enterprise-accounts.emu-permission-repo %} redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/pinning-an-issue-to-your-repository - /articles/pinning-an-issue-to-your-repository @@ -17,8 +18,6 @@ shortTitle: Pin an issue ![Pinned issues](/assets/images/help/issues/pinned-issues.png) -To pin an issue, you must have write permissions for the repository the issue is in. - {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issues %} 1. In the list of issues, click the issue you'd like to pin. diff --git a/translations/ru-RU/content/issues/tracking-your-work-with-issues/quickstart.md b/translations/ru-RU/content/issues/tracking-your-work-with-issues/quickstart.md index d402d71529..d066efe63c 100644 --- a/translations/ru-RU/content/issues/tracking-your-work-with-issues/quickstart.md +++ b/translations/ru-RU/content/issues/tracking-your-work-with-issues/quickstart.md @@ -19,7 +19,7 @@ This guide demonstrates how to use {% data variables.product.prodname_github_iss ## Требования -To create an issue, you need a repository. You can use an existing repository that you have write access to, or you can create a new repository. The repository must have issues enabled. For more information about creating a repository, see "[Creating a new repository](/articles/creating-a-new-repository)." For more information about enabling issues if they are disabled in your repository, see "[Disabling issues](/github/administering-a-repository/managing-repository-settings/disabling-issues)." +To create an issue, you need a repository. You can use an existing repository that you have write access to, or you can create a new repository. {% data reusables.enterprise-accounts.emu-permission-repo %} The repository must have issues enabled. For more information about creating a repository, see "[Creating a new repository](/articles/creating-a-new-repository)." For more information about enabling issues if they are disabled in your repository, see "[Disabling issues](/github/administering-a-repository/managing-repository-settings/disabling-issues)." ## Opening a blank issue diff --git a/translations/ru-RU/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md b/translations/ru-RU/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md index cbc389c464..ddb709ed73 100644 --- a/translations/ru-RU/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md +++ b/translations/ru-RU/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md @@ -1,6 +1,7 @@ --- title: Managing labels intro: 'You can classify {% ifversion fpt %}issues, pull requests, and discussions{% else %}issues and pull requests{% endif %} by creating, editing, applying, and deleting labels.' +permissions: '{% data reusables.enterprise-accounts.emu-permission-repo %}' redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/managing-labels - /articles/managing-Labels @@ -30,8 +31,6 @@ topics: You can manage your work on {% data variables.product.product_name %} by creating labels to categorize {% ifversion fpt %}issues, pull requests, and discussions{% else %}issues and pull requests{% endif %}. You can apply labels in the repository the label was created in. Once a label exists, you can use the label on any {% ifversion fpt %}issue, pull request, or discussion{% else %}issue or pull request{% endif %} within that repository. -Anyone with read access to a repository can view and search the repository’s labels. Anyone with triage access to a repository can apply/dismiss existing labels. To create, edit, apply, or delete a label, you must have write access to the repository. - ## About default labels {% data variables.product.product_name %} provides default labels in every new repository. You can use these default labels to help create a standard workflow in a repository. @@ -58,6 +57,8 @@ Organization owners can customize the default labels for repositories in their o ## Creating a label +Anyone with write access to a repository can create a label. + {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} {% data reusables.project-management.labels %} @@ -69,11 +70,15 @@ Organization owners can customize the default labels for repositories in their o ## Applying a label +Anyone with triage access to a repository can apply and dismiss labels. + 1. Navigate to the {% ifversion fpt %}issue, pull request, or discussion{% else %}issue or pull request{% endif %}. 1. In the right sidebar, to the right of "Labels", click {% octicon "gear" aria-label="The gear icon" %}, then click a label. !["Labels" drop-down menu](/assets/images/help/issues/labels-drop-down.png) ## Editing a label +Anyone with write access to a repository can edit existing labels. + {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} {% data reusables.project-management.labels %} @@ -85,6 +90,8 @@ Organization owners can customize the default labels for repositories in their o ## Deleting a label +Anyone with write access to a repository can delete existing labels. + Deleting a label will remove the label from issues and pull requests. {% data reusables.repositories.navigate-to-repo %} diff --git a/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md b/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md index 082974d281..3833fc0b9b 100644 --- a/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md +++ b/translations/ru-RU/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md @@ -24,6 +24,8 @@ Enterprise accounts allow owners to centrally manage policy and billing for mult For organizations that belong to an enterprise account, billing is managed at the enterprise account level, and billing settings are not available at the organization level. Enterprise owners can set policy for all organizations in the enterprise account or allow organization owners to set the policy at the organization level. Organization owners cannot change settings enforced for your organization at the enterprise account level. If you have questions about a policy or setting for your organization, contact the owner of your enterprise account. +{% data reusables.enterprise-accounts.invite-organization %} + {% data reusables.gated-features.enterprise-accounts %} {% data reusables.organizations.org-ownership-recommendation %} For more information, see "[Maintaining ownership continuity for your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)." diff --git a/translations/ru-RU/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md b/translations/ru-RU/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md index 60e67e9c59..18cfbf55e7 100644 --- a/translations/ru-RU/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md +++ b/translations/ru-RU/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md @@ -25,6 +25,18 @@ You can view and revoke each member's linked identity, active sessions, and auth {% data reusables.saml.about-linked-identities %} +When available, the entry will include SCIM data. For more information, see "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)." + +{% warning %} + +**Warning:** For organizations using SCIM: +- Revoking a linked user identity on {% data variables.product.product_name %} will also remove the SAML and SCIM metadata. As a result, the identity provider will not be able to synchronize or deprovision the linked user identity. +- An admin must revoke a linked identity through the identity provider. +- To revoke a linked identity and link a different account through the identity provider, an admin can remove and re-assign the user to the {% data variables.product.product_name %} application. For more information, see your identity provider's documentation. + +{% endwarning %} + + {% data reusables.identity-and-permissions.revoking-identity-team-sync %} {% data reusables.profile.access_org %} diff --git a/translations/ru-RU/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md b/translations/ru-RU/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md index 125958db17..999f42c18c 100644 --- a/translations/ru-RU/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md +++ b/translations/ru-RU/content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md @@ -50,6 +50,8 @@ To search for specific events, use the `action` qualifier in your query. Actions | [`корпоративный`](#enterprise-category-actions) | Contains activities related to enterprise settings. |{% endif %} | [`перехватчик`](#hook-category-actions) | Contains all activities related to webhooks. | | [`integration_installation_request`](#integration_installation_request-category-actions) | Contains all activities related to organization member requests for owners to approve integrations for use in the organization. | +| [`ip_allow_list`](#ip_allow_list) | Contains activitites related to enabling or disabling the IP allow list for an organization. | +| [`ip_allow_list_entry`](#ip_allow_list_entry) | Contains activities related to the creation, deletion, and editing of an IP allow list entry for an organization. | | [`проблема`](#issue-category-actions) | Contains activities related to deleting an issue. |{% ifversion fpt %} | [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | Contains all activities related to signing the {% data variables.product.prodname_marketplace %} Developer Agreement. | | [`marketplace_listing`](#marketplace_listing-category-actions) | Contains all activities related to listing apps in {% data variables.product.prodname_marketplace %}.{% endif %}{% ifversion fpt or ghes > 3.0 %} @@ -337,6 +339,23 @@ An overview of some of the most common actions that are recorded as events in th | `create` | Triggered when an organization member requests that an organization owner install an integration for use in the organization. | | `close` | Triggered when a request to install an integration for use in an organization is either approved or denied by an organization owner, or canceled by the organization member who opened the request. | +### `ip_allow_list` category actions + +| Действие | Description | +| ---------------------------- | --------------------------------------------------------------------------------------------------------------- | +| `включить` | Triggered when an IP allow list was enabled for an organization. | +| `отключить` | Triggered when an IP allow list was disabled for an organization. | +| `enable_for_installed_apps` | Triggered when an IP allow list was enabled for installed {% data variables.product.prodname_github_apps %}. | +| `disable_for_installed_apps` | Triggered when an IP allow list was disabled for installed {% data variables.product.prodname_github_apps %}. | + +### `ip_allow_list_entry` category actions + +| Действие | Description | +| ------------ | --------------------------------------------------------------- | +| `create` | Triggered when an IP address was added to an IP allow list. | +| `обновление` | Triggered when an IP address or its description was changed. | +| `destroy` | Triggered when an IP address was deleted from an IP allow list. | + ### `issue` category actions | Действие | Description | diff --git a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md index 1e27411c4b..4a3f96141c 100644 --- a/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md +++ b/translations/ru-RU/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md @@ -54,95 +54,96 @@ Some of the features listed below are limited to organizations using {% data var {% endnote %} {% endif %} -| Repository action | Read | Приоритизация | Write | Maintain | Admin | -|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-------------:|:-----:|:--------:|:------------------------------------------------:| -| Pull from the person or team's assigned repositories | **X** | **X** | **X** | **X** | **X** | -| Fork the person or team's assigned repositories | **X** | **X** | **X** | **X** | **X** | -| Edit and delete their own comments | **X** | **X** | **X** | **X** | **X** | -| Open issues | **X** | **X** | **X** | **X** | **X** | -| Close issues they opened themselves | **X** | **X** | **X** | **X** | **X** | -| Reopen issues they closed themselves | **X** | **X** | **X** | **X** | **X** | -| Have an issue assigned to them | **X** | **X** | **X** | **X** | **X** | -| Send pull requests from forks of the team's assigned repositories | **X** | **X** | **X** | **X** | **X** | -| Submit reviews on pull requests | **X** | **X** | **X** | **X** | **X** | -| View published releases | **X** | **X** | **X** | **X** | **X** |{% ifversion fpt %} -| View [GitHub Actions workflow runs](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **X** | **X** | **X** | **X** | **X** +| Repository action | Read | Приоритизация | Write | Maintain | Admin | +|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-------------:|:-----:|:--------:|:-----------------------------------------------------:| +| Pull from the person or team's assigned repositories | **X** | **X** | **X** | **X** | **X** | +| Fork the person or team's assigned repositories | **X** | **X** | **X** | **X** | **X** | +| Edit and delete their own comments | **X** | **X** | **X** | **X** | **X** | +| Open issues | **X** | **X** | **X** | **X** | **X** | +| Close issues they opened themselves | **X** | **X** | **X** | **X** | **X** | +| Reopen issues they closed themselves | **X** | **X** | **X** | **X** | **X** | +| Have an issue assigned to them | **X** | **X** | **X** | **X** | **X** | +| Send pull requests from forks of the team's assigned repositories | **X** | **X** | **X** | **X** | **X** | +| Submit reviews on pull requests | **X** | **X** | **X** | **X** | **X** | +| View published releases | **X** | **X** | **X** | **X** | **X** |{% ifversion fpt %} +| View [GitHub Actions workflow runs](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **X** | **X** | **X** | **X** | **X** {% endif %} -| Edit wikis | **X** | **X** | **X** | **X** | **X** |{% ifversion fpt %} -| [Report abusive or spammy content](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** +| Edit wikis in public repositories | **X** | **X** | **X** | **X** | **X** | +| Edit wikis in private repositories | | | **X** | **X** | **X** |{% ifversion fpt %} +| [Report abusive or spammy content](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** {% endif %} -| Apply/dismiss labels | | **X** | **X** | **X** | **X** | -| Create, edit, delete labels | | | **X** | **X** | **X** | -| Close, reopen, and assign all issues and pull requests | | **X** | **X** | **X** | **X** |{% ifversion fpt or ghae or ghes > 3.0 %} -| [Enable and disable auto-merge on a pull request](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** +| Apply/dismiss labels | | **X** | **X** | **X** | **X** | +| Create, edit, delete labels | | | **X** | **X** | **X** | +| Close, reopen, and assign all issues and pull requests | | **X** | **X** | **X** | **X** |{% ifversion fpt or ghae or ghes > 3.0 %} +| [Enable and disable auto-merge on a pull request](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** {% endif %} -| Apply milestones | | **X** | **X** | **X** | **X** | -| Mark [duplicate issues and pull requests](/articles/about-duplicate-issues-and-pull-requests) | | **X** | **X** | **X** | **X** | -| Request [pull request reviews](/articles/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** | -| Merge a [pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges) | | | **X** | **X** | **X** | -| Push to (write) the person or team's assigned repositories | | | **X** | **X** | **X** | -| Edit and delete anyone's comments on commits, pull requests, and issues | | | **X** | **X** | **X** | -| [Hide anyone's comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **X** | **X** | **X** | -| [Lock conversations](/communities/moderating-comments-and-conversations/locking-conversations) | | | **X** | **X** | **X** | -| Transfer issues (see "[Transferring an issue to another repository](/articles/transferring-an-issue-to-another-repository)" for details) | | | **X** | **X** | **X** | -| [Act as a designated code owner for a repository](/articles/about-code-owners) | | | **X** | **X** | **X** | -| [Mark a draft pull request as ready for review](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | -| [Convert a pull request to a draft](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | -| Submit reviews that affect a pull request's mergeability | | | **X** | **X** | **X** | -| [Apply suggested changes](/articles/incorporating-feedback-in-your-pull-request) to pull requests | | | **X** | **X** | **X** | -| Create [status checks](/articles/about-status-checks) | | | **X** | **X** | **X** |{% ifversion fpt %} -| Create, edit, run, re-run, and cancel [GitHub Actions workflows](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** +| Apply milestones | | **X** | **X** | **X** | **X** | +| Mark [duplicate issues and pull requests](/articles/about-duplicate-issues-and-pull-requests) | | **X** | **X** | **X** | **X** | +| Request [pull request reviews](/articles/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** | +| Merge a [pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges) | | | **X** | **X** | **X** | +| Push to (write) the person or team's assigned repositories | | | **X** | **X** | **X** | +| Edit and delete anyone's comments on commits, pull requests, and issues | | | **X** | **X** | **X** | +| [Hide anyone's comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **X** | **X** | **X** | +| [Lock conversations](/communities/moderating-comments-and-conversations/locking-conversations) | | | **X** | **X** | **X** | +| Transfer issues (see "[Transferring an issue to another repository](/articles/transferring-an-issue-to-another-repository)" for details) | | | **X** | **X** | **X** | +| [Act as a designated code owner for a repository](/articles/about-code-owners) | | | **X** | **X** | **X** | +| [Mark a draft pull request as ready for review](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | +| [Convert a pull request to a draft](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | +| Submit reviews that affect a pull request's mergeability | | | **X** | **X** | **X** | +| [Apply suggested changes](/articles/incorporating-feedback-in-your-pull-request) to pull requests | | | **X** | **X** | **X** | +| Create [status checks](/articles/about-status-checks) | | | **X** | **X** | **X** |{% ifversion fpt %} +| Create, edit, run, re-run, and cancel [GitHub Actions workflows](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** {% endif %} -| Create and edit releases | | | **X** | **X** | **X** | -| View draft releases | | | **X** | **X** | **X** | -| Edit a repository's description | | | | **X** | **X** |{% ifversion fpt or ghae %} -| [View and install packages](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | -| [Publish packages](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | -| | | | | | | -| {% ifversion fpt or ghes > 3.0 %}[Delete and restore packages](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Delete packages](/packages/learn-github-packages/deleting-a-package){% endif %} | | | | | **X** | {% endif %} -| Manage [topics](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** | -| Enable wikis and restrict wiki editors | | | | **X** | **X** | -| Enable project boards | | | | **X** | **X** | -| Configure [pull request merges](/articles/configuring-pull-request-merges) | | | | **X** | **X** | -| Configure [a publishing source for {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** | -| [Push to protected branches](/articles/about-protected-branches) | | | | **X** | **X** | -| [Create and edit repository social cards](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% ifversion fpt %} -| Limit [interactions in a repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository) | | | | **X** | **X** +| Create and edit releases | | | **X** | **X** | **X** | +| View draft releases | | | **X** | **X** | **X** | +| Edit a repository's description | | | | **X** | **X** |{% ifversion fpt or ghae %} +| [View and install packages](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | +| [Publish packages](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | +| | | | | | | +| {% ifversion fpt or ghes > 3.0 %}[Delete and restore packages](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Delete packages](/packages/learn-github-packages/deleting-a-package){% endif %} | | | | | **X** | {% endif %} +| Manage [topics](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** | +| Enable wikis and restrict wiki editors | | | | **X** | **X** | +| Enable project boards | | | | **X** | **X** | +| Configure [pull request merges](/articles/configuring-pull-request-merges) | | | | **X** | **X** | +| Configure [a publishing source for {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** | +| [Push to protected branches](/articles/about-protected-branches) | | | | **X** | **X** | +| [Create and edit repository social cards](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% ifversion fpt %} +| Limit [interactions in a repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository) | | | | **X** | **X** {% endif %} -| Delete an issue (see "[Deleting an issue](/articles/deleting-an-issue)") | | | | | **X** | -| Merge pull requests on protected branches, even if there are no approving reviews | | | | | **X** | -| [Define code owners for a repository](/articles/about-code-owners) | | | | | **X** | -| Add a repository to a team (see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)" for details) | | | | | **X** | -| [Manage outside collaborator access to a repository](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | -| [Change a repository's visibility](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | -| Make a repository a template (see "[Creating a template repository](/articles/creating-a-template-repository)") | | | | | **X** | -| Change a repository's settings | | | | | **X** | -| Manage team and collaborator access to the repository | | | | | **X** | -| Edit the repository's default branch | | | | | **X** |{% ifversion fpt or ghes > 3.0 %} -| Rename the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | | | **X** | -| Rename a branch other than the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | **X** | **X** | **X** +| Delete an issue (see "[Deleting an issue](/articles/deleting-an-issue)") | | | | | **X** | +| Merge pull requests on protected branches, even if there are no approving reviews | | | | | **X** | +| [Define code owners for a repository](/articles/about-code-owners) | | | | | **X** | +| Add a repository to a team (see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)" for details) | | | | | **X** | +| [Manage outside collaborator access to a repository](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | +| [Change a repository's visibility](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | +| Make a repository a template (see "[Creating a template repository](/articles/creating-a-template-repository)") | | | | | **X** | +| Change a repository's settings | | | | | **X** | +| Manage team and collaborator access to the repository | | | | | **X** | +| Edit the repository's default branch | | | | | **X** |{% ifversion fpt or ghes > 3.0 or ghae-next %} +| Rename the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | | | **X** | +| Rename a branch other than the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | **X** | **X** | **X** {% endif %} -| Manage webhooks and deploy keys | | | | | **X** |{% ifversion fpt %} -| [Manage data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **X** +| Manage webhooks and deploy keys | | | | | **X** |{% ifversion fpt %} +| [Manage data use settings for your private repository](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **X** {% endif %} -| [Manage the forking policy for a repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | -| [Transfer repositories into the organization](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | -| [Delete or transfer repositories out of the organization](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | -| [Archive repositories](/articles/about-archiving-repositories) | | | | | **X** |{% ifversion fpt %} -| Display a sponsor button (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)") | | | | | **X** +| [Manage the forking policy for a repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | +| [Transfer repositories into the organization](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | +| [Delete or transfer repositories out of the organization](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | +| [Archive repositories](/articles/about-archiving-repositories) | | | | | **X** |{% ifversion fpt %} +| Display a sponsor button (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)") | | | | | **X** {% endif %} -| Create autolink references to external resources, like JIRA or Zendesk (see "[Configuring autolinks to reference external resources](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **X** |{% ifversion fpt %} -| [Enable {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) in a repository | | | | **X** | **X** | -| [Create and edit categories](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) for {% data variables.product.prodname_discussions %} | | | | **X** | **X** | -| [Move a discussion to a different category](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [Transfer a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) to a new repository | | | **X** | **X** | **X** | -| [Manage pinned discussions](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [Convert issues to discussions in bulk](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [Lock and unlock discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [Individually convert issues to discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [Create new discussions and comment on existing discussions](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** | -| [Delete a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion) | | | | **X** | **X** |{% endif %}{% ifversion fpt %} -| Create [codespaces](/codespaces/about-codespaces) | | | **X** | **X** | **X** +| Create autolink references to external resources, like JIRA or Zendesk (see "[Configuring autolinks to reference external resources](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **X** |{% ifversion fpt %} +| [Enable {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) in a repository | | | | **X** | **X** | +| [Create and edit categories](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) for {% data variables.product.prodname_discussions %} | | | | **X** | **X** | +| [Move a discussion to a different category](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Transfer a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) to a new repository | | | **X** | **X** | **X** | +| [Manage pinned discussions](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Convert issues to discussions in bulk](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [Lock and unlock discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [Individually convert issues to discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [Create new discussions and comment on existing discussions](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** | +| [Delete a discussion](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion) | | | | **X** | **X** |{% endif %}{% ifversion fpt %} +| Create [codespaces](/codespaces/about-codespaces) | | | **X** | **X** | **X** {% endif %} ### Permission requirements for security features diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md b/translations/ru-RU/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md index da640abba9..3b49b64fe0 100644 --- a/translations/ru-RU/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md +++ b/translations/ru-RU/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md @@ -36,7 +36,7 @@ Alternatively, you can enable {% data variables.product.prodname_actions %} for {% endif %} -{% ifversion fpt or ghes > 2.22 %} +{% ifversion fpt or ghes > 2.22 or ghae-next %} ## Managing {% data variables.product.prodname_actions %} permissions for your organization @@ -63,7 +63,12 @@ You can disable all workflows for an organization or set a policy that configure {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.settings-sidebar-actions %} -1. Under **Policies**, select **Allow select actions** and add your required actions to the list. ![Add actions to allow list](/assets/images/help/organizations/actions-policy-allow-list.png) +1. Under **Policies**, select **Allow select actions** and add your required actions to the list. + {%- ifversion ghes %} + ![Add actions to allow list](/assets/images/help/organizations/actions-policy-allow-list.png) + {%- else %} + ![Add actions to allow list](/assets/images/enterprise/github-ae/organizations/actions-policy-allow-list.png) + {%- endif %} 1. Click **Save**. {% endif %} @@ -71,7 +76,9 @@ You can disable all workflows for an organization or set a policy that configure {% ifversion fpt %} ## Configuring required approval for workflows from public forks -{% data reusables.actions.workflow-run-approve-public-fork %} You can configure this behavior for an organization using the procedure below. Modifying this setting overrides the configuration set at the enterprise level. +{% data reusables.actions.workflow-run-approve-public-fork %} + +You can configure this behavior for an organization using the procedure below. Modifying this setting overrides the configuration set at the enterprise level. {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} diff --git a/translations/ru-RU/content/organizations/managing-organization-settings/transferring-organization-ownership.md b/translations/ru-RU/content/organizations/managing-organization-settings/transferring-organization-ownership.md index bb93e25f47..7086818ca3 100644 --- a/translations/ru-RU/content/organizations/managing-organization-settings/transferring-organization-ownership.md +++ b/translations/ru-RU/content/organizations/managing-organization-settings/transferring-organization-ownership.md @@ -15,6 +15,13 @@ topics: shortTitle: Transfer ownership --- +{% ifversion fpt %} +{% note %} + +**Note:** {% data reusables.enterprise-accounts.invite-organization %} + +{% endnote %}{% endif %} + 1. If you're the only member with *owner* privileges, give another organization member the owner role. For more information, see "[Appointing an organization owner](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization#appointing-an-organization-owner)." 2. Contact the new owner and make sure he or she is able to [access the organization's settings](/articles/accessing-your-organization-s-settings). {% ifversion fpt %} diff --git a/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md index c7b000385b..cef462e0a9 100644 --- a/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md +++ b/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md @@ -13,6 +13,8 @@ topics: shortTitle: IAM with SAML SSO --- +{% data reusables.enterprise-accounts.emu-saml-note %} + ## About SAML SSO {% data reusables.saml.dotcom-saml-explanation %} diff --git a/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md b/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md index caea2307eb..3c9aa6f723 100644 --- a/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md +++ b/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md @@ -12,6 +12,8 @@ topics: - Teams --- +{% data reusables.enterprise-accounts.emu-scim-note %} + If you use [SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on) in your organization, you can implement SCIM to add, manage, and remove organization members' access to {% data variables.product.product_name %}. For example, an administrator can deprovision an organization member using SCIM and automatically remove the member from the organization. If you use SAML SSO without implementing SCIM, you won't have automatic deprovisioning. When organization members' sessions expire after their access is removed from the IdP, they aren't automatically removed from the organization. Authorized tokens grant access to the organization even after their sessions expire. To remove access, organization administrators can either manually remove the authorized token from the organization or automate its removal with SCIM. diff --git a/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md b/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md index 623f9625b1..17cfeb080e 100644 --- a/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md +++ b/translations/ru-RU/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md @@ -17,6 +17,8 @@ topics: shortTitle: Manage team synchronization --- +{% data reusables.enterprise-accounts.emu-scim-note %} + {% data reusables.gated-features.okta-team-sync %} ## About team synchronization @@ -31,6 +33,8 @@ You can enable team synchronization between your IdP and {% data variables.produ You can also enable team synchronization for organizations owned by an enterprise account. For more information, see "[Enforcing security settings in your enterprise account](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account)." +{% data reusables.enterprise-accounts.team-sync-override %} + {% data reusables.identity-and-permissions.team-sync-usage-limits %} ## Enabling team synchronization diff --git a/translations/ru-RU/content/organizations/organizing-members-into-teams/creating-a-team.md b/translations/ru-RU/content/organizations/organizing-members-into-teams/creating-a-team.md index 9df306e69d..14b9737a51 100644 --- a/translations/ru-RU/content/organizations/organizing-members-into-teams/creating-a-team.md +++ b/translations/ru-RU/content/organizations/organizing-members-into-teams/creating-a-team.md @@ -25,11 +25,13 @@ Only organization owners and maintainers of a parent team can create a new child {% data reusables.organizations.team_description %} {% data reusables.organizations.create-team-choose-parent %} {% ifversion fpt %} -1. Optionally, if your organization or enterprise account uses team synchronization, to connect an identity provider group to your team, use the "Identity Provider Groups" drop-down menu, and select up to 5 identity provider groups. For more information, see "[Synchronizing a team with an identity provider group](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)." ![Drop-down menu to choose identity provider groups](/assets/images/help/teams/choose-an-idp-group.png) +1. Optionally, if your organization or enterprise account uses team synchronization or your enterprise uses {% data variables.product.prodname_emus %}, connect an identity provider group to your team. + * If your enterprise uses {% data variables.product.prodname_emus %}, use the "Identity Provider Groups" drop-down menu, and select a single identity provider group to connect to the new team. For more information, "[Managing team memberships with identity provider groups](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)." + * If your organization or enterprise account uses team synchronization, use the "Identity Provider Groups" drop-down menu, and select up to five identity provider groups to connect to the new team. For more information, see "[Synchronizing a team with an identity provider group](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)." ![Drop-down menu to choose identity provider groups](/assets/images/help/teams/choose-an-idp-group.png) {% endif %} {% data reusables.organizations.team_visibility %} {% data reusables.organizations.create_team %} -9. Optionally, [give the team access to organization repositories](/articles/managing-team-access-to-an-organization-repository). +1. Optionally, [give the team access to organization repositories](/articles/managing-team-access-to-an-organization-repository). ## Дополнительная литература diff --git a/translations/ru-RU/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md b/translations/ru-RU/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md index 33de558346..2c5a81cef8 100644 --- a/translations/ru-RU/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md +++ b/translations/ru-RU/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md @@ -45,8 +45,11 @@ Any team members that have set their status to "Busy" will not be selected for r 7. Under "How many team members should be assigned to review?", use the drop-down menu and choose a number of reviewers to be assigned to each pull request. ![Number of reviewers dropdown](/assets/images/help/teams/review-assignment-number.png) 8. Under "Routing algorithm", use the drop-down menu and choose which algorithm you'd like to use. For more information, see "[Routing algorithms](#routing-algorithms)." ![Routing algorithm dropdown](/assets/images/help/teams/review-assignment-algorithm.png) 9. Optionally, to always skip certain members of the team, select **Never assign certain team members**. Then, select one or more team members you'd like to always skip. ![Never assign certain team members checkbox and dropdown](/assets/images/help/teams/review-assignment-skip-members.png) -10. Optionally, to only notify the team members chosen by code review assignment for each pull review request, under "Notifications" select **If assigning team members, don't notify the entire team.** ![Code review assignment notifications](/assets/images/help/teams/review-assignment-notifications.png) -11. Click **Save changes**. +10. Optionally, to only notify the team members chosen by code review assignment for each pull review request, under "Notifications" select **If assigning team members, don't notify the entire team.** ![Code review assignment notifications](/assets/images/help/teams/review-assignment-notifications.png){% ifversion fpt or ghae or ghes > 3.2 %} +11. Optionally, to include members of child teams as potential reviewers when assigning requests, select **Child team members**. +12. Optionally, to count any members whose review has already been requested against the total number of members to assign, select **Count existing requests**. +13. Optionally, to remove the review request from the team when assigning team members, select **Team review request**.{% endif %} +14. Click **Save changes**. ## Disabling code review assignment {% data reusables.profile.access_org %} diff --git a/translations/ru-RU/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/ru-RU/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md index 076d753345..5b299e6492 100644 --- a/translations/ru-RU/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md +++ b/translations/ru-RU/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md @@ -16,6 +16,8 @@ shortTitle: Synchronize with an IdP {% data reusables.gated-features.okta-team-sync %} +{% data reusables.enterprise-accounts.emu-scim-note %} + ## About team synchronization {% data reusables.identity-and-permissions.about-team-sync %} @@ -26,6 +28,8 @@ shortTitle: Synchronize with an IdP Once a {% data variables.product.prodname_dotcom %} team is connected to an IdP group, your IdP administrator must make team membership changes through the identity provider. You cannot manage team membership on {% data variables.product.product_name %}{% ifversion fpt %} or using the API{% endif %}. +{% ifversion fpt %}{% data reusables.enterprise-accounts.team-sync-override %}{% endif %} + {% ifversion fpt %} All team membership changes made through your IdP will appear in the audit log on {% data variables.product.product_name %} as changes made by the team synchronization bot. Your IdP will send team membership data to {% data variables.product.prodname_dotcom %} once every hour. Connecting a team to an IdP group may remove some team members. For more information, see "[Requirements for members of synchronized teams](#requirements-for-members-of-synchronized-teams)." {% endif %} @@ -54,8 +58,6 @@ A removed team member can be added back to a team automatically once they have a To avoid unintentionally removing team members, we recommend enforcing SAML SSO in your organization or enterprise account, creating new teams to synchronize membership data, and checking IdP group membership before synchronizing existing teams. For more information, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)" and "[Enforcing SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account)." -If your organization is owned by an enterprise account, enabling team synchronization for the enterprise account will override your organization-level team synchronization settings. For more information, see "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)." - {% endif %} ## Требования diff --git a/translations/ru-RU/content/packages/learn-github-packages/installing-a-package.md b/translations/ru-RU/content/packages/learn-github-packages/installing-a-package.md index 8a38d76f79..43ce0bf433 100644 --- a/translations/ru-RU/content/packages/learn-github-packages/installing-a-package.md +++ b/translations/ru-RU/content/packages/learn-github-packages/installing-a-package.md @@ -18,7 +18,7 @@ versions: ## About package installation -You can search {% data variables.product.product_name %} to find packages in {% data variables.product.prodname_registry %} that you can install in your own project. For more information, see "[Searching {% data variables.product.prodname_registry %} for packages](/github/searching-for-information-on-github/searching-for-packages)." +You can search {% data variables.product.product_name %} to find packages in {% data variables.product.prodname_registry %} that you can install in your own project. For more information, see "[Searching {% data variables.product.prodname_registry %} for packages](/search-github/searching-on-github/searching-for-packages)." After you find a package, you can read the package's description and installation and usage instructions on the package page. diff --git a/translations/ru-RU/content/packages/learn-github-packages/viewing-packages.md b/translations/ru-RU/content/packages/learn-github-packages/viewing-packages.md index 9a5a8b74c4..81ac8bc8bc 100644 --- a/translations/ru-RU/content/packages/learn-github-packages/viewing-packages.md +++ b/translations/ru-RU/content/packages/learn-github-packages/viewing-packages.md @@ -64,4 +64,4 @@ You can find and view any package you've published across all organizations and ## Дополнительная литература -- "[Searching for packages](/github/searching-for-information-on-github/searching-for-packages)" +- "[Searching for packages](/search-github/searching-on-github/searching-for-packages)" diff --git a/translations/ru-RU/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md b/translations/ru-RU/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md index bb0d08585a..2c20440794 100644 --- a/translations/ru-RU/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md +++ b/translations/ru-RU/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md @@ -15,8 +15,6 @@ shortTitle: Publish & install with Actions {% data reusables.package_registry.packages-ghes-release-stage %} {% data reusables.package_registry.packages-ghae-release-stage %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## About {% data variables.product.prodname_registry %} with {% data variables.product.prodname_actions %} diff --git a/translations/ru-RU/content/packages/quickstart.md b/translations/ru-RU/content/packages/quickstart.md index d87fe3626b..df69ee827d 100644 --- a/translations/ru-RU/content/packages/quickstart.md +++ b/translations/ru-RU/content/packages/quickstart.md @@ -10,8 +10,6 @@ shortTitle: Quickstart --- {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## Introduction diff --git a/translations/ru-RU/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md b/translations/ru-RU/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md index 702ec212a8..35317ba1c6 100644 --- a/translations/ru-RU/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md +++ b/translations/ru-RU/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md @@ -157,7 +157,11 @@ You can install packages from {% data variables.product.prodname_registry %} by By default, you can add packages from one organization. For more information, see "[Installing packages from other organizations](#installing-packages-from-other-organizations)." -You also need to add the *.npmrc* file to your project so all requests to install packages will go through {% data variables.product.prodname_registry %}. When you route all package requests through {% data variables.product.prodname_registry %}, you can use both scoped and unscoped packages from *npmjs.com*. For more information, see "[npm-scope](https://docs.npmjs.com/misc/scope)" in the npm documentation. +You also need to add the *.npmrc* file to your project so that all requests to install packages will {% ifversion ghae %}be routed to{% else %}go through{% endif %} {% data variables.product.prodname_registry %}. {% ifversion fpt or ghes > 2.21 %}When you route all package requests through {% data variables.product.prodname_registry %}, you can use both scoped and unscoped packages from *npmjs.org*. For more information, see "[npm-scope](https://docs.npmjs.com/misc/scope)" in the npm documentation.{% endif %} + +{% ifversion ghae %} +By default, you can only use npm packages hosted on your enterprise, and you will not be able to use unscoped packages. For more information on package scoping, see "[npm-scope](https://docs.npmjs.com/misc/scope)" in the npm documentation. If required, {% data variables.product.prodname_dotcom %} support can enable an upstream proxy to npmjs.org. Once an upstream proxy is enabled, if a requested package isn't found on your enterprise, {% data variables.product.prodname_registry %} makes a proxy request to npmjs.org. +{% endif %} {% data reusables.package_registry.authenticate-step %} {% data reusables.package_registry.create-npmrc-owner-step %} diff --git a/translations/ru-RU/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md b/translations/ru-RU/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md index ccec9de88d..77e97fb2b3 100644 --- a/translations/ru-RU/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md +++ b/translations/ru-RU/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md @@ -12,7 +12,11 @@ shortTitle: Change visibility of site ## About access control for {% data variables.product.prodname_pages %} sites -If your project site is published from a private or internal repository that's owned by an organization using {% data variables.product.prodname_ghe_cloud %}, you can manage access control for the site. With access control, you can choose to publish the site publicly to anyone on the internet or privately to people with read access to your repository. A privately published site can be used to share your internal documentation or knowledge base with members of your enterprise. You cannot manage access control for an organization site. For more information about the types of {% data variables.product.prodname_pages %} sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)." +With access control for {% data variables.product.prodname_pages %}, you can restrict access to your {% data variables.product.prodname_pages %} site by publishing the site privately. A privately published site can only be accessed by people with read access to the repository the site is published from. You can use privately published sites to share your internal documentation or knowledge base with members of your enterprise. + +If your enterprise uses {% data variables.product.prodname_emus %}, all {% data variables.product.prodname_pages %} sites are privately published. For more information about {% data variables.product.prodname_emus %}, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." + +If your organization uses {% data variables.product.prodname_ghe_cloud %} without {% data variables.product.prodname_emus %}, you can choose to publish your sites privately or publicly to anyone on the internet. Access control is available for project sites that are published from a private or internal repository that are owned by the organization. You cannot manage access control for an organization site. For more information about the types of {% data variables.product.prodname_pages %} sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)." Privately published sites are available at a different subdomain than publicly published sites. This ensures that your {% data variables.product.prodname_pages %} site is secure from the moment it's published: diff --git a/translations/ru-RU/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md b/translations/ru-RU/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md index 97113bddbc..5fcba4f33c 100644 --- a/translations/ru-RU/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md +++ b/translations/ru-RU/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md @@ -22,6 +22,12 @@ All {% data variables.product.prodname_pages %} sites, including sites that are {% data reusables.pages.private_pages_are_public_warning %} +{% note %} + +**Note:** RFC3280 states that the maximum length of the common name should be 64 characters. Therefore, the entire domain name of your {% data variables.product.prodname_pages %} site must be less than 64 characters long for a certificate to be successfully created. + +{% endnote %} + ## Enforcing HTTPS for your {% data variables.product.prodname_pages %} site {% data reusables.pages.navigate-site-repo %} diff --git a/translations/ru-RU/content/repositories/archiving-a-github-repository/archiving-repositories.md b/translations/ru-RU/content/repositories/archiving-a-github-repository/archiving-repositories.md index fb2927a52d..e529690e89 100644 --- a/translations/ru-RU/content/repositories/archiving-a-github-repository/archiving-repositories.md +++ b/translations/ru-RU/content/repositories/archiving-a-github-repository/archiving-repositories.md @@ -32,7 +32,7 @@ Once a repository is archived, you cannot add or remove collaborators or teams. When a repository is archived, its issues, pull requests, code, labels, milestones, projects, wiki, releases, commits, tags, branches, reactions, and comments become read-only. To make changes in an archived repository, you must unarchive the repository first. -You can search for archived repositories. For more information, see "[Searching for repositories](/articles/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)." You can also search for issues and pull requests within archived repositories. For more information, see "[Searching issues and pull requests](/articles/searching-issues-and-pull-requests/#search-based-on-whether-a-repository-is-archived)." +You can search for archived repositories. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)." You can also search for issues and pull requests within archived repositories. For more information, see "[Searching issues and pull requests](/search-github/searching-on-github/searching-issues-and-pull-requests/#search-based-on-whether-a-repository-is-archived)." ## Archiving a repository diff --git a/translations/ru-RU/content/repositories/archiving-a-github-repository/backing-up-a-repository.md b/translations/ru-RU/content/repositories/archiving-a-github-repository/backing-up-a-repository.md index 8e9172895e..75d108192c 100644 --- a/translations/ru-RU/content/repositories/archiving-a-github-repository/backing-up-a-repository.md +++ b/translations/ru-RU/content/repositories/archiving-a-github-repository/backing-up-a-repository.md @@ -36,7 +36,7 @@ When you clone a repository or wiki, only Git data, such as project files and co - [Projects](/rest/reference/projects#list-repository-projects) {% endif %} -Once you have {% ifversion ghes or ghae %}a local version of all the content you want to back up, you can create a zip archive and {% else %}downloaded your archive, you can {% endif %}copy it to an external hard drive and/or upload it to a cloud-based backup service such as [Google Drive](https://www.google.com/drive/) or [Dropbox](https://www.dropbox.com/). +Once you have {% ifversion ghes or ghae %}a local version of all the content you want to back up, you can create a zip archive and {% else %}downloaded your archive, you can {% endif %}copy it to an external hard drive and/or upload it to a cloud-based backup or storage service such as [Azure Blob Storage](https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-overview/), [Google Drive](https://www.google.com/drive/) or [Dropbox](https://www.dropbox.com/). {% ifversion fpt %} ## Third-party backup tools diff --git a/translations/ru-RU/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md b/translations/ru-RU/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md index b3ef3da1b6..15218c0f75 100644 --- a/translations/ru-RU/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md +++ b/translations/ru-RU/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md @@ -28,13 +28,13 @@ You can choose the default branch for a repository. The default branch is the ba {% endnote %} {% endif %} -{% ifversion fpt or ghes > 3.0 %} +{% ifversion fpt or ghes > 3.0 or ghae-next %} You can also rename the default branch. For more information, see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)." {% endif %} -{% ifversion fpt or ghes > 2.22 %} +{% ifversion fpt or ghes > 2.22 or ghae-next %} {% data reusables.branches.set-default-branch %} diff --git a/translations/ru-RU/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md b/translations/ru-RU/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md index 1344afe816..0d325c4e14 100644 --- a/translations/ru-RU/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md +++ b/translations/ru-RU/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md @@ -5,6 +5,7 @@ permissions: People with write permissions to a repository can rename a branch i versions: fpt: '*' ghes: '>=3.1' + ghae: next topics: - Repositories redirect_from: diff --git a/translations/ru-RU/content/repositories/creating-and-managing-repositories/about-repositories.md b/translations/ru-RU/content/repositories/creating-and-managing-repositories/about-repositories.md index 3156b42f5a..f8be787145 100644 --- a/translations/ru-RU/content/repositories/creating-and-managing-repositories/about-repositories.md +++ b/translations/ru-RU/content/repositories/creating-and-managing-repositories/about-repositories.md @@ -74,7 +74,7 @@ All enterprise members have read permissions to the internal repository, but int {% data reusables.repositories.internal-repo-default %} -If a user is removed from all organizations owned by the enterprise, that user's forks of internal repositories are removed automatically. +Any member of the enterprise can fork any internal repository owned by an organization in the enterprise. The forked repository will belong to the member's user account, and the visibility of the fork will be private. If a user is removed from all organizations owned by the enterprise, that user's forks of internal repositories are removed automatically. {% endif %} ## Limits for viewing content and diffs in a repository @@ -107,6 +107,7 @@ The compare view and pull requests pages display a list of commits between the ` ## Дополнительная литература - "[Creating a new repository](/articles/creating-a-new-repository)" +- "[About forks](/github/collaborating-with-pull-requests/working-with-forks/about-forks)" - "[Collaborating with issues and pull requests](/categories/collaborating-with-issues-and-pull-requests)" - "[Managing your work on {% data variables.product.prodname_dotcom %}](/categories/managing-your-work-on-github/)" - "[Administering a repository](/categories/administering-a-repository)" diff --git a/translations/ru-RU/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md b/translations/ru-RU/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md index 33fea40dfb..22d619640f 100644 --- a/translations/ru-RU/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md +++ b/translations/ru-RU/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md @@ -46,18 +46,19 @@ Lisa, M., & Bot, H. (2017). My Research Software (Version 2.0.4) [Computer softw {% raw %} ``` -@misc{Lisa_My_Research_Software_2017, +@software{Lisa_My_Research_Software_2017, author = {Lisa, Mona and Bot, Hew}, doi = {10.5281/zenodo.1234}, month = {12}, title = {{My Research Software}}, url = {https://github.com/github/linguist}, + version = {2.0.4}, year = {2017} } ``` {% endraw %} -Note the example above produces a _software_ citation (i.e., `@misc` type in BibTeX rather than `@article`). +Note the example above produces a _software_ citation (i.e., `@software` type in BibTeX rather than `@article`). For more information, see the [Citation File Format](https://citation-file-format.github.io/) website. @@ -67,9 +68,15 @@ When you add a `CITATION.cff` file to the default branch of your repository, it ## Citing something other than software -If you would prefer the GitHub citation information to link to another resource such as a research paper then you can use the `preferred-citation` override in CFF. +If you would prefer the {% data variables.product.prodname_dotcom %} citation information to link to another resource such as a research article, then you can use the `preferred-citation` override in CFF with the following types. -Extended CITATION.cff file describing the software, but linking to a research paper as the preferred citation: +| Resource | Тип | +| ---------------- | ------------------ | +| Research article | `article` | +| Conference paper | `conference-paper` | +| Book | `book` | + +Extended CITATION.cff file describing the software, but linking to a research article as the preferred citation: ``` cff-version: 1.2.0 @@ -132,6 +139,10 @@ Lisa, M., & Bot, H. (2021). My awesome research software. Journal Title, 1(1), 1 ``` {% endraw %} +## Citing a dataset + +If your repository contains a dataset, you can set `type: dataset` in your `CITATION.cff` file to produce a data citation string output in the {% data variables.product.prodname_dotcom %} citation prompt. + ## Other citation files The GitHub citation feature will also detect a small number of additional files that are often used by communities and projects to describe how they would like their work to be cited. diff --git a/translations/ru-RU/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md b/translations/ru-RU/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md index dbc1a4353b..2df9989080 100644 --- a/translations/ru-RU/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md +++ b/translations/ru-RU/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md @@ -29,7 +29,7 @@ Repository admins can add any topics they'd like to a repository. Helpful topics {% ifversion ghae %}Internal {% else %}Public, internal, {% endif %}and private repositories can have topics, although you will only see private repositories that you have access to in topic search results. -You can search for repositories that are associated with a particular topic. For more information, see "[Searching for repositories](/articles/searching-for-repositories#search-by-topic)." You can also search for a list of topics on {% data variables.product.product_name %}. For more information, see "[Searching topics](/articles/searching-topics)." +You can search for repositories that are associated with a particular topic. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories#search-by-topic)." You can also search for a list of topics on {% data variables.product.product_name %}. For more information, see "[Searching topics](/search-github/searching-on-github/searching-topics)." ## Adding topics to your repository diff --git a/translations/ru-RU/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md b/translations/ru-RU/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md index 7df745dec8..ebbb8c1400 100644 --- a/translations/ru-RU/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md +++ b/translations/ru-RU/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md @@ -73,7 +73,7 @@ You can filter repositories based on their license or license family using the ` | | The Unlicense | `unlicense` | | | zLib License | `zlib` | -When you search by a family license, your results will include all licenses in that family. For example, when you use the query `license:gpl`, your results will include repositories licensed under GNU General Public License v2.0 and GNU General Public License v3.0. For more information, see "[Searching for repositories](/articles/searching-for-repositories/#search-by-license)." +When you search by a family license, your results will include all licenses in that family. For example, when you use the query `license:gpl`, your results will include repositories licensed under GNU General Public License v2.0 and GNU General Public License v3.0. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories/#search-by-license)." ## Detecting a license diff --git a/translations/ru-RU/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md b/translations/ru-RU/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md index 4857b0f632..9eda8f6ec2 100644 --- a/translations/ru-RU/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md +++ b/translations/ru-RU/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md @@ -43,7 +43,7 @@ Alternatively, you can enable {% data variables.product.prodname_actions %} in y {% endif %} -{% ifversion fpt or ghes > 2.22 %} +{% ifversion fpt or ghes > 2.22 or ghae-next %} ## Managing {% data variables.product.prodname_actions %} permissions for your repository @@ -72,14 +72,21 @@ You can disable all workflows for a repository or set a policy that configures w {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.settings-sidebar-actions %} -1. Under **Actions permissions**, select **Allow select actions** and add your required actions to the list. ![Add actions to allow list](/assets/images/help/repository/actions-policy-allow-list.png) +1. Under **Actions permissions**, select **Allow select actions** and add your required actions to the list. + {%- ifversion ghes %} + ![Add actions to allow list](/assets/images/help/repository/actions-policy-allow-list.png) + {%- else %} + ![Add actions to allow list](/assets/images/enterprise/github-ae/repository/actions-policy-allow-list.png) + {%- endif %} 2. Click **Save**. {% endif %} {% ifversion fpt %} ## Configuring required approval for workflows from public forks -{% data reusables.actions.workflow-run-approve-public-fork %} You can configure this behavior for a repository using the procedure below. Modifying this setting overrides the configuration set at the organization or enterprise level. +{% data reusables.actions.workflow-run-approve-public-fork %} + +You can configure this behavior for a repository using the procedure below. Modifying this setting overrides the configuration set at the organization or enterprise level. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} @@ -120,6 +127,29 @@ The default permissions can also be configured in the organization settings. If 1. Click **Save** to apply the settings. {% endif %} +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## Allowing access to components in an internal repository + +{% note %} + +**Note:** {% data reusables.gated-features.internal-repos %} + +{% endnote %} + +Members of your enterprise can use internal repositories to work on projects without sharing information publicly. For information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-internal-repositories)." + +To configure whether workflows in an internal repository can be accessed from outside the repository: + +1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of the internal repository. +1. Under your repository name, click {% octicon "gear" aria-label="The gear icon" %} **Settings**. +{% data reusables.repositories.settings-sidebar-actions %} +1. Under **Access**, choose one of the access settings: ![Set the access to Actions components](/assets/images/help/settings/actions-access-settings.png) + * **Not accessible** - Workflows in other repositories can't use workflows in this repository. + * **Accessible by any repository in the organization** - Workflows in other repositories can use workflows in this repository as long as they are part of the same organization. + * **Accessible by any repository in the enterprise** - Workflows in other repositories can use workflows in this repository as long as they are part of the same enterprise. +1. Click **Save** to apply the settings. +{% endif %} + {% ifversion fpt or ghes > 2.22 or ghae %} ## Configuring the retention period for {% data variables.product.prodname_actions %} artifacts and logs in your repository diff --git a/translations/ru-RU/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md b/translations/ru-RU/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md index f31156b6d9..2fb29dd74c 100644 --- a/translations/ru-RU/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md +++ b/translations/ru-RU/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md @@ -21,6 +21,12 @@ shortTitle: Repository visibility Organization owners can restrict the ability to change repository visibility to organization owners only. For more information, see "[Restricting repository visibility changes in your organization](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)." +{% ifversion fpt %} + +If you're a member of an {% data variables.product.prodname_emu_enterprise %}, your repositories owned by your user account can only be private, and repositories in your enterprise's organizations can only be private or internal. + +{% endif %} + We recommend reviewing the following caveats before you change the visibility of a repository. {% ifversion ghes or ghae %} diff --git a/translations/ru-RU/content/repositories/releasing-projects-on-github/about-releases.md b/translations/ru-RU/content/repositories/releasing-projects-on-github/about-releases.md index 983bccd89d..2c2aac0b40 100644 --- a/translations/ru-RU/content/repositories/releasing-projects-on-github/about-releases.md +++ b/translations/ru-RU/content/repositories/releasing-projects-on-github/about-releases.md @@ -34,6 +34,9 @@ You can receive notifications when new releases are published in a repository wi 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)." {% ifversion fpt %} + +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)." + 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](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)." {% endif %} diff --git a/translations/ru-RU/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md b/translations/ru-RU/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md new file mode 100644 index 0000000000..9c8141111a --- /dev/null +++ b/translations/ru-RU/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md @@ -0,0 +1,93 @@ +--- +title: Automatically generated release notes +intro: You can automatically generate release notes for your GitHub releases +permissions: Repository collaborators and people with write access to a repository can generate and customize automated release notes for a release. +versions: + fpt: '*' +topics: + - Repositories +shortTitle: Automated release notes +--- + +{% note %} + +**Note:** {% data reusables.repositories.auto-gen-release-public-beta %} + +{% endnote %} + +## About automatically generated release notes + +Automatically generated release notes provide an automated alternative to manually writing release notes for your {% data variables.product.prodname_dotcom %} releases. With automatically generated release notes, you can quickly generate an overview of the contents of a release. You can also customize your automated release notes, using labels to create custom categories to organize pull requests you want to include, and exclude certain labels and users from appearing in the output. + +## Creating automatically generated release notes for a new release + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.releases %} +3. Click **Draft a new release**. ![Releases draft button](/assets/images/help/releases/draft_release_button.png) +4. {% ifversion fpt %}Click **Choose a tag** and type{% else %}Type{% endif %} a version number for your release. Alternatively, select an existing tag. + {% ifversion fpt %} + ![Enter a tag](/assets/images/help/releases/releases-tag-create.png) +5. If you are creating a new tag, click **Create new tag**. ![Confirm you want to create a new tag](/assets/images/help/releases/releases-tag-create-confirm.png) + {% else %} + ![Releases tagged version](/assets/images/enterprise/releases/releases-tag-version.png) +{% endif %} +6. If you have created a new tag, use the drop-down menu to select the branch that contains the project you want to release. + {% ifversion fpt %}![Choose a branch](/assets/images/help/releases/releases-choose-branch.png) + {% else %}![Releases tagged branch](/assets/images/enterprise/releases/releases-tag-branch.png) + {% endif %} +7. To the top right of the description text box, click **Auto-generate release notes**. ![Auto-generate release notes](/assets/images/help/releases/auto-generate-release-notes.png) +8. Check the generated notes to ensure they include all (and only) the information you want to include. +9. Optionally, to include binary files such as compiled programs in your release, drag and drop or manually select files in the binaries box. ![Providing a DMG with the Release](/assets/images/help/releases/releases_adding_binary.gif) +10. To notify users that the release is not ready for production and may be unstable, select **This is a pre-release**. ![Checkbox to mark a release as prerelease](/assets/images/help/releases/prerelease_checkbox.png) +{%- ifversion fpt %} +11. Optionally, select **Create a discussion for this release**, then select the **Category** drop-down menu and click a category for the release discussion. ![Checkbox to create a release discussion and drop-down menu to choose a category](/assets/images/help/releases/create-release-discussion.png) +{%- endif %} +12. If you're ready to publicize your release, click **Publish release**. To work on the release later, click **Save draft**. ![Publish release and Draft release buttons](/assets/images/help/releases/release_buttons.png) + + +## Creating a template for automatically generated release notes + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.files.add-file %} +3. In the file name field, type `.github/release.yml` to create the `release.yml` file in the `.github` directory. ![Create new file](/assets/images/help/releases/release-yml.png) +4. In the file, specify the pull request labels and authors you want to exclude from this release. You can also create new categories and list the pull request labels to be included in each of them. For more information, see "[Managing labels](/issues/using-labels-and-milestones-to-track-work/managing-labels)." + +## Example configuration + +{% raw %} +**release.yml** +```yaml{:copy} +# release.yml + +changelog: + exclude: + labels: + - ignore-for-release + authors: + - octocat + categories: + - title: Breaking Changes 🛠 + labels: + - Semver-Major + - breaking-change + - title: Exciting New Features 🎉 + labels: + - Semver-Minor + - enhancement + - title: Other Changes + labels: + - "*" +``` +{% endraw %} + +## Release template syntax + +| Parameter | Description | Required | Value | +|:----------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:---------------------------------------------------------------------------- |:------------------------------------------------------------------------- | +| `changelog` | Defines the contents within it as the custom template for your release notes. | Required. | No value accepted. | +| `исключить` | Creates a category of pull requests to be excluded from the release. Can be set at the top-level of the changelog to apply to all categories or applied on a per-category basis. | Optional | No value accepted. | +| `authors` | Specifies authors to be excluded from the release. | Optional for `exclude` category. | Accepts usernames and bots as values. | +| `категории` | Defines the nested contents as custom categories to be included in the template. | Optional | No value accepted. | +| `title` | Creates an individual category. | Required if `categories` parameter exists. | Takes the category name as its value. | +| `labels` | Specifies labels to be used by the enclosing category. | Required if `categories` parameter exists, optional for `exclude` parameter. | Accepts any labels, whether currently existing or planned for the future. | +| `"*"` | Catchall for any pull request not included within a category *above*. If used, it must be added at the end of the file. | Optional | No value accepted. | diff --git a/translations/ru-RU/content/repositories/releasing-projects-on-github/index.md b/translations/ru-RU/content/repositories/releasing-projects-on-github/index.md index 14d8bc84fc..37b236ff9a 100644 --- a/translations/ru-RU/content/repositories/releasing-projects-on-github/index.md +++ b/translations/ru-RU/content/repositories/releasing-projects-on-github/index.md @@ -17,6 +17,7 @@ children: - /viewing-your-repositorys-releases-and-tags - /linking-to-releases - /comparing-releases + - /automatically-generated-release-notes - /automation-for-release-forms-with-query-parameters shortTitle: Release projects --- diff --git a/translations/ru-RU/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md b/translations/ru-RU/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md index 714cdf4b15..9c25d34cf9 100644 --- a/translations/ru-RU/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md +++ b/translations/ru-RU/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md @@ -42,14 +42,14 @@ You can choose whether {% data variables.large_files.product_name_long %} ({% da {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.releases %} 3. Click **Draft a new release**. ![Releases draft button](/assets/images/help/releases/draft_release_button.png) -4. {% ifversion fpt %}Click **Choose a tag** and type{% else %}Type{% endif %} a version number for your release. +4. {% ifversion fpt %}Click **Choose a tag** and type{% else %}Type{% endif %} a version number for your release. Alternatively, select an existing tag. {% ifversion fpt %} ![Enter a tag](/assets/images/help/releases/releases-tag-create.png) -1. Click **Create new tag**. ![Confirm you want to create a new tag](/assets/images/help/releases/releases-tag-create-confirm.png) +1. If you are creating a new tag, click **Create new tag**. ![Confirm you want to create a new tag](/assets/images/help/releases/releases-tag-create-confirm.png) {% else %} ![Releases tagged version](/assets/images/enterprise/releases/releases-tag-version.png) {% endif %} -5. Use the drop-down menu to select the branch that contains the project you want to release. +5. If you have created a new tag, use the drop-down menu to select the branch that contains the project you want to release. {% ifversion fpt %}![Choose a branch](/assets/images/help/releases/releases-choose-branch.png) {% else %}![Releases tagged branch](/assets/images/enterprise/releases/releases-tag-branch.png) {% endif %} @@ -57,7 +57,9 @@ You can choose whether {% data variables.large_files.product_name_long %} ({% da {%- ifversion fpt or ghes > 3.2 or ghae-issue-4972 %} If you @mention any {% data variables.product.product_name %} users in the description, the published release will include a **Contributors** section with an avatar list of all the mentioned users. {%- endif %} - ![Releases description](/assets/images/help/releases/releases_description.png) + {% ifversion fpt %} Alternatively, you can automatically generate your release notes by clicking **Auto-generate release notes**. + {% endif %} + ![Releases description](/assets/images/help/releases/releases_description_auto.png) 7. Optionally, to include binary files such as compiled programs in your release, drag and drop or manually select files in the binaries box. ![Providing a DMG with the Release](/assets/images/help/releases/releases_adding_binary.gif) 8. To notify users that the release is not ready for production and may be unstable, select **This is a pre-release**. ![Checkbox to mark a release as prerelease](/assets/images/help/releases/prerelease_checkbox.png) {%- ifversion fpt %} diff --git a/translations/ru-RU/content/repositories/working-with-files/using-files/working-with-non-code-files.md b/translations/ru-RU/content/repositories/working-with-files/using-files/working-with-non-code-files.md index dd677d91eb..9836b3b4a2 100644 --- a/translations/ru-RU/content/repositories/working-with-files/using-files/working-with-non-code-files.md +++ b/translations/ru-RU/content/repositories/working-with-files/using-files/working-with-non-code-files.md @@ -188,6 +188,14 @@ You can click {% octicon "file" aria-label="The paper icon" %} to see the change ![Rendered Prose changes](/assets/images/help/repository/rendered_prose_changes.png) +{% ifversion fpt or ghes > 3.2 or ghae-issue-5232 %} + +### Disabling Markdown rendering + +{% data reusables.repositories.disabling-markdown-rendering %} + +{% endif %} + ### Visualizing attribute changes We provide a tooltip describing changes to attributes that, unlike words, would not otherwise be visible in the rendered document. For example, if a link URL changes from one website to another, we'd show a tooltip like this: diff --git a/translations/ru-RU/content/rest/guides/getting-started-with-the-rest-api.md b/translations/ru-RU/content/rest/guides/getting-started-with-the-rest-api.md index b68106d9e3..280b9aabda 100644 --- a/translations/ru-RU/content/rest/guides/getting-started-with-the-rest-api.md +++ b/translations/ru-RU/content/rest/guides/getting-started-with-the-rest-api.md @@ -122,10 +122,10 @@ $ curl -i -u your_username {% data variables.product.api_url_pre %}/use When prompted, you can enter your OAuth token, but we recommend you set up a variable for it: -You can use `-u "username:$token"` and set up a variable for `token` to avoid leaving your token in shell history, which should be avoided. +You can use `-u "your_username:$token"` and set up a variable for `token` to avoid leaving your token in shell history, which should be avoided. ```shell -$ curl -i -u username:$token {% data variables.product.api_url_pre %}/users/octocat +$ curl -i -u your_username:$token {% data variables.product.api_url_pre %}/users/octocat ``` diff --git a/translations/ru-RU/content/rest/overview/api-previews.md b/translations/ru-RU/content/rest/overview/api-previews.md index 76824dd9a6..ce163a8a7c 100644 --- a/translations/ru-RU/content/rest/overview/api-previews.md +++ b/translations/ru-RU/content/rest/overview/api-previews.md @@ -18,32 +18,36 @@ During the preview period, we may change some features based on developer feedba To access an API preview, you'll need to provide a custom [media type](/rest/overview/media-types) in the `Accept` header for your requests. Feature documentation for each preview specifies which custom media type to provide. -{% ifversion fpt %} -## Migrations - -Allows you to download repositories from your GitHub user or organization account to review, backup, and [migrate](/rest/reference/migrations) data to {% data variables.product.prodname_ghe_server %}. - -**Custom media type:** `wyandotte-preview` **Announced:** [2018-05-24](https://developer.github.com/changes/2018-05-24-user-migration-api/) -{% endif %} +{% ifversion ghes < 3.3 %} ## Enhanced deployments -Exercise greater control over [deployments](/v3/repos/deployments/) with more information and finer granularity. +Exercise greater control over [deployments](/rest/reference/repos#deployments) with more information and finer granularity. **Custom media type:** `ant-man-preview` **Announced:** [2016-04-06](https://developer.github.com/changes/2016-04-06-deployment-and-deployment-status-enhancements/) +{% endif %} + +{% ifversion ghes < 3.3 %} + ## Reactions Manage [reactions](/rest/reference/reactions) for commits, issues, and comments. **Custom media type:** `squirrel-girl-preview` **Announced:** [2016-05-12](https://developer.github.com/changes/2016-05-12-reactions-api-preview/) **Update:** [2016-06-07](https://developer.github.com/changes/2016-06-07-reactions-api-update/) +{% endif %} + +{% ifversion ghes < 3.3 %} + ## Timeline Get a [list of events](/rest/reference/issues#timeline) for an issue or pull request. **Custom media type:** `mockingbird-preview` **Announced:** [2016-05-23](https://developer.github.com/changes/2016-05-23-timeline-preview-api/) +{% endif %} + {% ifversion ghes %} ## Pre-receive environments @@ -52,11 +56,13 @@ Create, list, update, and delete environments for pre-receive hooks. **Custom media type:** `eye-scream-preview` **Announced:** [2015-07-29](/rest/reference/enterprise-admin#pre-receive-environments) {% endif %} +{% ifversion ghes < 3.3 %} ## Projects Manage [projects](/rest/reference/projects). **Custom media type:** `inertia-preview` **Announced:** [2016-09-14](https://developer.github.com/changes/2016-09-14-projects-api/) **Update:** [2016-10-27](https://developer.github.com/changes/2016-10-27-changes-to-projects-api/) +{% endif %} ## Commit search @@ -70,12 +76,16 @@ View a list of [repository topics](/articles/about-topics/) in [calls](/rest/ref **Custom media type:** `mercy-preview` **Announced:** [2017-01-31](https://github.com/blog/2309-introducing-topics) +{% ifversion ghes < 3.3 %} + ## Codes of conduct View all [codes of conduct](/rest/reference/codes-of-conduct) or get which code of conduct a repository has currently. **Custom media type:** `scarlet-witch-preview` +{% endif %} + {% ifversion ghae or ghes %} ## Global webhooks @@ -93,12 +103,16 @@ You can now use the API to manage the setting for [requiring signed commits on p **Custom media type:** `zzzax-preview` **Announced:** [2018-02-22](https://developer.github.com/changes/2018-02-22-protected-branches-required-signatures) +{% ifversion ghes < 3.3 %} + ## Require multiple approving reviews You can now [require multiple approving reviews](/rest/reference/repos#branches) for a pull request using the API. **Custom media type:** `luke-cage-preview` **Announced:** [2018-03-16](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews) +{% endif %} + {% ifversion ghes < 3.0 %} ## Check runs and check suites API @@ -135,30 +149,42 @@ GitHub App Manifests allow people to create preconfigured GitHub Apps. See "[Cre {% endif %} +{% ifversion ghes < 3.3 %} + ## Deployment statuses You can now update the `environment` of a [deployment status](/rest/reference/repos#create-a-deployment-status) and use the `in_progress` and `queued` states. When you create deployment statuses, you can now use the `auto_inactive` parameter to mark old `production` deployments as `inactive`. **Custom media type:** `flash-preview` **Announced:** [2018-10-16](https://developer.github.com/changes/2018-10-16-deployments-environments-states-and-auto-inactive-updates/) +{% endif %} + +{% ifversion ghes < 3.3 %} + ## Repository creation permissions You can now configure whether organization members can create repositories and which types of repositories they can create. See "[Update an organization](/rest/reference/orgs#update-an-organization)" for more details. **Custom media types:** `surtur-preview` **Announced:** [2019-12-03](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/) +{% endif %} + ## Content attachments You can now provide more information in GitHub for URLs that link to registered domains by using the {% data variables.product.prodname_unfurls %} API. See "[Using content attachments](/apps/using-content-attachments/)" for more details. **Custom media types:** `corsair-preview` **Announced:** [2018-12-10](https://developer.github.com/changes/2018-12-10-content-attachments-api/) +{% ifversion ghes < 3.3 %} + ## Enable and disable Pages You can use the new endpoints in the [Pages API](/rest/reference/repos#pages) to enable or disable Pages. To learn more about Pages, see "[GitHub Pages Basics](/categories/github-pages-basics)". **Custom media types:** `switcheroo-preview` **Announced:** [2019-03-14](https://developer.github.com/changes/2019-03-14-enabling-disabling-pages/) +{% endif %} + {% ifversion ghes < 3.3 %} ## List branches or pull requests for a commit @@ -169,11 +195,7 @@ You can use two new endpoints in the [Commits API](/rest/reference/repos#commits {% endif %} -## Enable or disable vulnerability alerts for a repository - -You can use two new endpoints in the [Repos API](/rest/reference/repos) to enable or disable vulnerability alerts. - -**Custom media types:** `dorian-preview` **Announced:** [2019-04-24](https://developer.github.com/changes/2019-04-24-vulnerability-alerts/) +{% ifversion ghes < 3.3 %} ## Update a pull request branch @@ -181,12 +203,6 @@ You can use a new endpoint to [update a pull request branch](/rest/reference/pul **Custom media types:** `lydian-preview` **Announced:** [2019-05-29](https://developer.github.com/changes/2019-05-29-update-branch-api/) -{% ifversion fpt %} -## Enable or disable automated security fixes - -You can use a new set of endpoints to [enable and disable automated security fixes](/rest/reference/repos#enable-automated-security-fixes). - -**Custom media types:** `london-preview` **Announced:** [2019-06-04](https://developer.github.com/changes/2019-06-04-automated-security-fixes/) {% endif %} ## Create and use repository templates @@ -195,7 +211,8 @@ You can use a new endpoint to [Create a repository using a template](/rest/refer **Custom media types:** `baptiste-preview` **Announced:** [2019-07-05](https://developer.github.com/changes/2019-07-16-repository-templates-api/) -{% ifversion fpt or ghes or ghae %} +{% ifversion ghes < 3.3 %} + ## New visibility parameter for the Repositories API You can set and retrieve the visibility of a repository in the [Repositories API](/rest/reference/repos). diff --git a/translations/ru-RU/content/rest/overview/troubleshooting.md b/translations/ru-RU/content/rest/overview/troubleshooting.md index 931e4c2f3a..d2ef6004cb 100644 --- a/translations/ru-RU/content/rest/overview/troubleshooting.md +++ b/translations/ru-RU/content/rest/overview/troubleshooting.md @@ -62,6 +62,10 @@ curl -u my_username:my_password -X POST "https://api.github.com/authorizations" Then you must switch to the [web application flow](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) to generate access tokens. +## Timeouts + +If {% data variables.product.product_name %} takes more than 10 seconds to process an API request, {% data variables.product.product_name %} will terminate the request and you will receive a timeout response. + {% endif %} [oap-guide]: https://developer.github.com/changes/2015-01-19-an-integrators-guide-to-organization-application-policies/ diff --git a/translations/ru-RU/content/rest/reference/actions.md b/translations/ru-RU/content/rest/reference/actions.md index e31bd3d07b..8dfa85c2ef 100644 --- a/translations/ru-RU/content/rest/reference/actions.md +++ b/translations/ru-RU/content/rest/reference/actions.md @@ -12,7 +12,6 @@ topics: miniTocMaxHeadingLevel: 3 --- -{% data reusables.actions.ae-beta %} The {% data variables.product.prodname_actions %} API enables you to manage {% data variables.product.prodname_actions %} using the REST API. {% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} require the permissions mentioned in each endpoint. For more information, see "[{% data variables.product.prodname_actions %} Documentation](/actions)." @@ -22,8 +21,6 @@ The {% data variables.product.prodname_actions %} API enables you to manage {% d ## Artifacts -{% data reusables.actions.ae-beta %} - The Artifacts API allows you to download, delete, and retrieve information about workflow artifacts. {% data reusables.actions.about-artifacts %} For more information, see "[Persisting workflow data using artifacts](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)." {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %} @@ -35,8 +32,6 @@ The Artifacts API allows you to download, delete, and retrieve information about {% ifversion fpt or ghes > 2.22 or ghae %} ## Permissions -{% data reusables.actions.ae-beta %} - The Permissions API allows you to set permissions for what organizations and repositories are allowed to run {% data variables.product.prodname_actions %}, and what actions are allowed to run. For more information, see "[Usage limits, billing, and administration](/actions/reference/usage-limits-billing-and-administration#disabling-or-limiting-github-actions-for-your-repository-or-organization)." You can also set permissions for an enterprise. For more information, see the "[{% data variables.product.prodname_dotcom %} Enterprise administration](/rest/reference/enterprise-admin#github-actions)" REST API. @@ -48,8 +43,6 @@ You can also set permissions for an enterprise. For more information, see the "[ ## Secrets -{% data reusables.actions.ae-beta %} - The Secrets API lets you create, update, delete, and retrieve information about encrypted secrets. {% data reusables.actions.about-secrets %} For more information, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)." {% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `secrets` permission to use this API. Authenticated users must have collaborator access to a repository to create, update, or read secrets. @@ -60,7 +53,6 @@ The Secrets API lets you create, update, delete, and retrieve information about ## Self-hosted runners -{% data reusables.actions.ae-beta %} {% data reusables.actions.ae-self-hosted-runners-notice %} The Self-hosted Runners API allows you to register, view, and delete self-hosted runners. {% data reusables.actions.about-self-hosted-runners %} For more information, see "[Hosting your own runners](/actions/hosting-your-own-runners)." @@ -75,7 +67,6 @@ You can manage self-hosted runners for an enterprise. For more information, see ## Self-hosted runner groups -{% data reusables.actions.ae-beta %} {% data reusables.actions.ae-self-hosted-runners-notice %} The Self-hosted Runners Groups API allows you manage groups of self-hosted runners. 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)." @@ -90,8 +81,6 @@ You can manage self-hosted runner groups for an enterprise. For more information ## Workflows -{% data reusables.actions.ae-beta %} - The Workflows API allows you to view workflows for a repository. {% data reusables.actions.about-workflows %} For more information, see "[Automating your workflow with GitHub Actions](/actions/automating-your-workflow-with-github-actions)." {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %} @@ -102,8 +91,6 @@ The Workflows API allows you to view workflows for a repository. {% data reusabl ## Workflow jobs -{% data reusables.actions.ae-beta %} - The Workflow Jobs API allows you to view logs and workflow jobs. {% data reusables.actions.about-workflow-jobs %} For more information, see "[Workflow syntax for GitHub Actions](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)". {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %} @@ -114,8 +101,6 @@ The Workflow Jobs API allows you to view logs and workflow jobs. {% data reusabl ## Workflow runs -{% data reusables.actions.ae-beta %} - The Workflow Runs API allows you to view, re-run, cancel, and view logs for workflow runs. {% data reusables.actions.about-workflow-runs %} For more information, see "[Managing a workflow run](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)." {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %} diff --git a/translations/ru-RU/content/rest/reference/activity.md b/translations/ru-RU/content/rest/reference/activity.md index e62b9897b7..2c5e86b9d9 100644 --- a/translations/ru-RU/content/rest/reference/activity.md +++ b/translations/ru-RU/content/rest/reference/activity.md @@ -145,6 +145,7 @@ Here's a list of potential `reason`s for receiving a notification: | `assign` | You were assigned to the issue. | | `автор` | You created the thread. | | `комментарий` | You commented on the thread. | +| `ci_activity` | A {% data variables.product.prodname_actions %} workflow run that you triggered was completed. | | `приглашение` | You accepted an invitation to contribute to the repository. | | `manual` | You subscribed to the thread (via an issue or pull request). | | `упоминание` | You were specifically **@mentioned** in the content. | diff --git a/translations/ru-RU/content/rest/reference/enterprise-admin.md b/translations/ru-RU/content/rest/reference/enterprise-admin.md index 181844d3d8..4b8b577a57 100644 --- a/translations/ru-RU/content/rest/reference/enterprise-admin.md +++ b/translations/ru-RU/content/rest/reference/enterprise-admin.md @@ -81,7 +81,6 @@ The current version of your enterprise is returned in the response header of eve ## GitHub Actions -{% data reusables.actions.ae-beta %} {% for operation in currentRestOperations %} {% if operation.subcategory == 'actions' %}{% include rest_operation %}{% endif %} diff --git a/translations/ru-RU/content/rest/reference/projects.md b/translations/ru-RU/content/rest/reference/projects.md index aa8cf5ac71..13543ab310 100644 --- a/translations/ru-RU/content/rest/reference/projects.md +++ b/translations/ru-RU/content/rest/reference/projects.md @@ -1,6 +1,6 @@ --- title: Projects -intro: 'The Projects API lets you to create, list, update, delete and customize projects in a repository.' +intro: 'The Projects API lets you create, list, update, delete and customize projects in a repository.' redirect_from: - /v3/projects versions: diff --git a/translations/ru-RU/content/rest/reference/repos.md b/translations/ru-RU/content/rest/reference/repos.md index 841f6f5edd..e0bd08c1dc 100644 --- a/translations/ru-RU/content/rest/reference/repos.md +++ b/translations/ru-RU/content/rest/reference/repos.md @@ -175,7 +175,7 @@ You can communicate that a transient environment no longer exists by setting its {% ifversion fpt or ghes > 3.1 or ghae-next %} ## Environments -The Environments API allows you to create, configure, and delete environments. For more information about environments, see "[Environments](/actions/reference/environments)." To manage environment secrets, see "[Secrets](/rest/reference/actions#secrets)." +The Environments API allows you to create, configure, and delete environments. For more information about environments, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." To manage environment secrets, see "[Secrets](/rest/reference/actions#secrets)." {% for operation in currentRestOperations %} {% if operation.subcategory == 'environments' %}{% include rest_operation %}{% endif %} diff --git a/translations/ru-RU/content/rest/reference/scim.md b/translations/ru-RU/content/rest/reference/scim.md index 35677eb7c5..3f2cc726d5 100644 --- a/translations/ru-RU/content/rest/reference/scim.md +++ b/translations/ru-RU/content/rest/reference/scim.md @@ -16,7 +16,9 @@ The SCIM API is used by SCIM-enabled Identity Providers (IdPs) to automate provi {% note %} -**Note:** The SCIM API is available only to organizations on [{% data variables.product.prodname_ghe_cloud %}](/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts) with [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) enabled. {% data reusables.scim.enterprise-account-scim %} For more information about SCIM, see "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)." +**Замечания:** + - The SCIM API is available only to organizations on [{% data variables.product.prodname_ghe_cloud %}](/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts) with [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) enabled. {% data reusables.scim.enterprise-account-scim %} For more information about SCIM, see "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)." + - The SCIM API cannot be used with {% data variables.product.prodname_emus %}. {% endnote %} diff --git a/translations/ru-RU/content/rest/reference/search.md b/translations/ru-RU/content/rest/reference/search.md index c7aa32146f..82872d4954 100644 --- a/translations/ru-RU/content/rest/reference/search.md +++ b/translations/ru-RU/content/rest/reference/search.md @@ -50,7 +50,7 @@ GitHub Octocat in:readme user:defunkt const queryString = 'q=' + encodeURIComponent('GitHub Octocat in:readme user:defunkt'); ``` -See "[Searching on GitHub](/articles/searching-on-github/)" for a complete list of available qualifiers, their format, and an example of how to use them. For information about how to use operators to match specific quantities, dates, or to exclude results, see "[Understanding the search syntax](/articles/understanding-the-search-syntax/)." +See "[Searching on GitHub](/articles/searching-on-github/)" for a complete list of available qualifiers, their format, and an example of how to use them. For information about how to use operators to match specific quantities, dates, or to exclude results, see "[Understanding the search syntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax/)." ### Limitations on query length diff --git a/translations/ru-RU/content/rest/reference/teams.md b/translations/ru-RU/content/rest/reference/teams.md index 60bd6aab7e..0627bb8a2e 100644 --- a/translations/ru-RU/content/rest/reference/teams.md +++ b/translations/ru-RU/content/rest/reference/teams.md @@ -58,6 +58,12 @@ The Team Synchronization API allows you to manage connections between {% data va You can manage GitHub team members through your IdP with team synchronization. Team synchronization must be enabled to use the Team Synchronization API. For more information, see "Synchronizing teams between your identity provider and GitHub." +{% note %} + +**Note:** The Team Synchronization API cannot be used with {% data variables.product.prodname_emus %}. + +{% endnote %} + {% for operation in currentRestOperations %} {% if operation.subcategory == 'team-sync' %}{% include rest_operation %}{% endif %} {% endfor %} diff --git a/translations/ru-RU/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md b/translations/ru-RU/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md new file mode 100644 index 0000000000..5fe9ad8dac --- /dev/null +++ b/translations/ru-RU/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md @@ -0,0 +1,90 @@ +--- +title: About searching on GitHub +intro: 'Our integrated search covers the many repositories, users, and lines of code on {% data variables.product.product_name %}.' +redirect_from: + - /articles/using-the-command-bar/ + - /articles/github-search-basics/ + - /articles/search-basics/ + - /articles/searching-github/ + - /articles/advanced-search/ + - /articles/about-searching-on-github + - /github/searching-for-information-on-github/about-searching-on-github + - /github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +{% data reusables.search.you-can-search-globally %} + +- To search globally across all of {% data variables.product.product_name %}, type what you're looking for into the search field at the top of any page, and choose "All {% data variables.product.prodname_dotcom %}" in the search drop-down menu. +- To search within a particular repository or organization, navigate to the repository or organization page, type what you're looking for into the search field at the top of the page, and press **Enter**. + +{% note %} + +**Замечания:** + +{% ifversion fpt or ghes %} +- {% data reusables.search.required_login %}{% endif %} +- {% data variables.product.prodname_pages %} sites are not searchable on {% data variables.product.product_name %}. However you can search the source content if it exists in the default branch of a repository, using code search. For more information, see "[Searching code](/search-github/searching-on-github/searching-code)." For more information about {% data variables.product.prodname_pages %}, see "[What is GitHub Pages?](/articles/what-is-github-pages/)" +- Currently our search doesn't support exact matching. +- Whenever you are searching in code files, only the first two results in each file will be returned. + +{% endnote %} + +After running a search on {% data variables.product.product_name %}, you can sort the results, or further refine them by clicking one of the languages in the sidebar. For more information, see "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results)." + +{% data variables.product.product_name %} search uses an ElasticSearch cluster to index projects every time a change is pushed to {% data variables.product.product_name %}. Issues and pull requests are indexed when they are created or modified. + +## Types of searches on {% data variables.product.prodname_dotcom %} + +You can search for the following information across all repositories you can access on {% data variables.product.product_location %}. + +- [Repositories](/search-github/searching-on-github/searching-for-repositories) +- [Topics](/search-github/searching-on-github/searching-topics) +- [Issues and pull requests](/search-github/searching-on-github/searching-issues-and-pull-requests){% ifversion fpt %} +- [Discussions](/search-github/searching-on-github/searching-discussions){% endif %} +- [Code](/search-github/searching-on-github/searching-code) +- [Commits](/search-github/searching-on-github/searching-commits) +- [Users](/search-github/searching-on-github/searching-users) +- [Packages](/search-github/searching-on-github/searching-for-packages) +- [Wikis](/search-github/searching-on-github/searching-wikis) + +## Searching using a visual interface + +Alternatively, you can search {% data variables.product.product_name %} using the {% data variables.search.search_page_url %} or {% data variables.search.advanced_url %}. + +The {% data variables.search.advanced_url %} provides a visual interface for constructing search queries. You can filter your searches by a variety of factors, such as the number of stars or number of forks a repository has. As you fill in the advanced search fields, your query will automatically be constructed in the top search bar. + +![Advanced Search](/assets/images/help/search/advanced_search_demo.gif) + +{% ifversion fpt or ghes or ghae-next %} + +## Searching repositories on {% data variables.product.prodname_dotcom_the_website %} from your private enterprise environment + +If you use {% ifversion fpt %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae-next %} or {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} and you're a member of a {% data variables.product.prodname_dotcom_the_website %} organization using {% data variables.product.prodname_ghe_cloud %}, an enterprise owner for your {% data variables.product.prodname_enterprise %} environment can enable {% data variables.product.prodname_github_connect %} so that you can search across both environments at the same time{% ifversion ghes or ghae %} from {% data variables.product.product_name %}{% endif %}. For more information, see the following. + +{% ifversion fpt or ghes %} +- "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/{% ifversion ghes %}{{ currentVersion }}{% else %}github-enterprise@latest{% endif %}/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_server %} documentation{% endif %}{% ifversion ghae-next %} +- "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/github-ae@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_managed %} documentation +{% endif %} + +{% ifversion ghes or ghae-next %} + +To scope your search by environment, you can use a filter option on the {% data variables.search.advanced_url %} or you can use the `environment:` search prefix. To only search for content on {% data variables.product.product_name %}, use the search syntax `environment:local`. To only search for content on {% data variables.product.prodname_dotcom_the_website %}, use `environment:github`. + +Your enterprise owner on {% data variables.product.product_name %} can enable {% data variables.product.prodname_unified_search %} for all public repositories, all private repositories, or only certain private repositories in the connected {% data variables.product.prodname_ghe_cloud %} organization. + +When you search from {% data variables.product.product_name %}, you can only search in the private repositories that you have access to in the connected {% data variables.product.prodname_dotcom_the_website %} organization. Enterprise owners for {% data variables.product.product_name %} and organization owners on {% data variables.product.prodname_dotcom_the_website %} cannot search private repositories owned by your account on {% data variables.product.prodname_dotcom_the_website %}. To search the applicable private repositories, you must enable private repository search for your personal accounts on {% data variables.product.product_name %}. For more information, see "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment)." + +{% endif %} + +{% endif %} + +## Дополнительная литература + +- "[Understanding the search syntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)" +- "[Searching on GitHub](/articles/searching-on-github)" diff --git a/translations/ru-RU/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md b/translations/ru-RU/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md new file mode 100644 index 0000000000..c693be985b --- /dev/null +++ b/translations/ru-RU/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md @@ -0,0 +1,54 @@ +--- +title: Enabling GitHub.com repository search from your private enterprise environment +shortTitle: Search GitHub.com from enterprise +intro: 'You can connect your personal accounts on {% data variables.product.prodname_dotcom_the_website %} and your private {% data variables.product.prodname_enterprise %} environment to search for content in certain {% data variables.product.prodname_dotcom_the_website %} repositories{% ifversion fpt %} from your private environment{% else %} from {% data variables.product.product_name %}{% endif %}.' +redirect_from: + - /articles/enabling-private-githubcom-repository-search-in-your-github-enterprise-account/ + - /articles/enabling-private-github-com-repository-search-in-your-github-enterprise-server-account/ + - /articles/enabling-private-githubcom-repository-search-in-your-github-enterprise-server-account/ + - /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 +versions: + fpt: '*' + ghes: '*' + ghae: next +topics: + - GitHub search +--- + +## About search for {% data variables.product.prodname_dotcom_the_website %} repositories from {% ifversion fpt %}your private enterprise environment{% else %}{% data variables.product.product_name %}{% endif %} + +You can search for designated private repositories on {% data variables.product.prodname_ghe_cloud %} from {% ifversion fpt %}your private {% data variables.product.prodname_enterprise %} environment{% else %}{% data variables.product.product_location %}{% ifversion ghae %} on {% data variables.product.prodname_ghe_managed %}{% endif %}{% endif %}. {% ifversion fpt %}For example, if you use {% data variables.product.prodname_ghe_server %}, you can search for private repositories from your enterprise from {% data variables.product.prodname_ghe_cloud %} in the web interface for {% data variables.product.prodname_ghe_server %}.{% endif %} + +## Требования + +- An enterprise owner for {% ifversion fpt %}your private {% data variables.product.prodname_enterprise %} environment{% else %}{% data variables.product.product_name %}{% endif %} must enable {% data variables.product.prodname_github_connect %} and {% data variables.product.prodname_unified_search %} for private repositories. For more information, see the following.{% ifversion fpt or ghes %} + - "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/{% ifversion ghes %}{{ currentVersion }}{% else %}github-enterprise@latest{% endif %}/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_server %} documentation{% endif %}{% ifversion ghae-next %} + - "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/github-ae@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_managed %} documentation +{% endif %} + +- You must already have access to the private repositories and connect your account {% ifversion fpt %}in your private {% data variables.product.prodname_enterprise %} environment{% else %}on {% data variables.product.product_name %}{% endif %} with your account on {% data variables.product.prodname_dotcom_the_website %}. For more information about the repositories you can search, see "[About searching on GitHub](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github#searching-repositories-on-githubcom-from-your-private-enterprise-environment)." + +## Enabling GitHub.com repository search from {% ifversion fpt %}your private {% data variables.product.prodname_enterprise %} environment{% else %}{% data variables.product.product_name %}{% endif %} + +{% ifversion fpt %} + +For more information, see the following. + +| Your enterprise environment | More information | +|:--------------------------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| {% data variables.product.prodname_ghe_server %} | "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/enterprise-server@latest/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-enterprise-server)" |{% ifversion ghae-next %} +| +| {% data variables.product.prodname_ghe_managed %} | "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/github-ae@latest//search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-ae)" +{% endif %} + +{% elsif ghes or ghae %} + +1. Sign into {% data variables.product.product_name %} and {% data variables.product.prodname_dotcom_the_website %}. +1. On {% data variables.product.product_name %}, in the upper-right corner of any page, click your profile photo, then click **Settings**. ![Settings icon in the user bar](/assets/images/help/settings/userbar-account-settings.png) +{% data reusables.github-connect.github-connect-tab-user-settings %} +{% data reusables.github-connect.connect-dotcom-and-enterprise %} +{% data reusables.github-connect.connect-dotcom-and-enterprise %} + +{% endif %} diff --git a/translations/ru-RU/content/search-github/getting-started-with-searching-on-github/index.md b/translations/ru-RU/content/search-github/getting-started-with-searching-on-github/index.md new file mode 100644 index 0000000000..b712ae3657 --- /dev/null +++ b/translations/ru-RU/content/search-github/getting-started-with-searching-on-github/index.md @@ -0,0 +1,21 @@ +--- +title: Getting started with searching on GitHub +intro: You can use a wide range of syntax to search {% data variables.product.product_name %}. You can adjust the scope of your search, build and troubleshoot queries, and sort search results with qualifiers. +redirect_from: + - /articles/getting-started-with-searching-on-github + - /github/searching-for-information-on-github/getting-started-with-searching-on-github +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +children: + - /about-searching-on-github + - /understanding-the-search-syntax + - /troubleshooting-search-queries + - /sorting-search-results + - /enabling-githubcom-repository-search-from-your-private-enterprise-environment +shortTitle: Start with search on GitHub +--- + diff --git a/translations/ru-RU/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md b/translations/ru-RU/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md new file mode 100644 index 0000000000..76e51116a5 --- /dev/null +++ b/translations/ru-RU/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md @@ -0,0 +1,75 @@ +--- +title: Sorting search results +intro: 'You can sort [{% data variables.product.product_name %} search](/articles/searching-on-github) results using the Sort menu, or by adding a `sort` qualifier to your query.' +redirect_from: + - /articles/sorting-search-results + - /github/searching-for-information-on-github/sorting-search-results + - /github/searching-for-information-on-github/getting-started-with-searching-on-github/sorting-search-results +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +Use the Sort menu to sort results by relevance, number of stars, number of forks, and how recently the items were updated. + + ![Menu with options for sorting search results](/assets/images/help/search/repo-search-sort.png) + +To sort by interactions, reactions, author date, committer date, or how recently the items were updated, you can add a `sort` qualifier to your search query. + +## Sort by interactions + +The `sort:interactions` qualifier sorts by the highest combined number of reactions and comments. + +| Qualifier | Пример | +| ----------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sort:interactions` or `sort:interactions-desc` | [**org:github sort:interactions**](https://github.com/search?q=org%3Agithub+sort%3Ainteractions&type=Issues) matches issues in repositories owned by {% data variables.product.product_name %}, sorted by the highest combined number of reactions and comments. | +| `sort:interactions-asc` | [**org:github sort:interactions-asc**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Ainteractions-asc&type=Issues) matches issues in repositories owned by {% data variables.product.product_name %}, sorted by the lowest combined number of reactions and comments. | + +## Sort by reactions + +The `sort:reactions` qualifier sorts by the number or type of reactions. + +| Qualifier | Пример | +| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sort:reactions` or `sort:reactions-desc` | [**org:github sort:reactions**](https://github.com/search?q=org%3Agithub+sort%3Areactions&type=Issues) matches issues in repositories owned by {% data variables.product.product_name %}, sorted by the highest number of reactions. | +| `sort:reactions-asc` | [**org:github sort:reactions-asc**](https://github.com/search?q=org%3Agithub+sort%3Areactions-asc&type=Issues) matches issues in repositories owned by {% data variables.product.product_name %}, sorted by ascending number of reactions (the fewest to the most). | +| sort:reactions-reaction | [**org:github sort:reactions-+1**](https://github.com/search?q=org%3Agithub+sort%3Areactions-%2B1&type=Issues) matches issues in repositories owned by {% data variables.product.product_name %}, sorted by most thumbs up (:+1:) reactions. | +| | [**org:github sort:reactions--1**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Areactions--1&type=Issues) matches issues in repositories owned by {% data variables.product.product_name %}, sorted by most thumbs down (:-1:) reactions. | +| | [**org:github sort:reactions-smile**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Areactions-smile&type=Issues) matches issues in repositories owned by {% data variables.product.product_name %}, sorted by most laugh (:smile:) reactions. | +| | [**org:github sort:reactions-tada**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Areactions-tada&type=Issues) matches issues in repositories owned by {% data variables.product.product_name %}, sorted by most hurray (:tada:) reactions. | +| | [**org:github sort:reactions-heart**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Areactions-heart&type=Issues) matches issues in repositories owned by {% data variables.product.product_name %}, sorted by most heart (:heart:) reactions. | + +## Sort by author date + +The `sort:author-date` qualifier sorts by descending or ascending author date. + +| Qualifier | Пример | +| --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sort:author-date` or `sort:author-date-desc` | [**feature org:github sort:author-date**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Aauthor-date&type=Commits) matches commits containing the word "feature" in repositories owned by {% data variables.product.product_name %}, sorted by descending author date. | +| `sort:author-date-asc` | [**feature org:github sort:author-date-asc**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Aauthor-date-asc&type=Commits) matches commits containing the word "feature" in repositories owned by {% data variables.product.product_name %}, sorted by ascending author date. | + +## Sort by committer date + +The `sort:committer-date` qualifier sorts by descending or ascending committer date. + +| Qualifier | Пример | +| --------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sort:committer-date` or `sort:committer-date-desc` | [**feature org:github sort:committer-date**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Acommitter-date&type=Commits) matches commits containing the word "feature" in repositories owned by {% data variables.product.product_name %}, sorted by descending committer date. | +| `sort:committer-date-asc` | [**feature org:github sort:committer-date-asc**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Acommitter-date-asc&type=Commits) matches commits containing the word "feature" in repositories owned by {% data variables.product.product_name %}, sorted by ascending committer date. | + +## Sort by updated date + +The `sort:updated` qualifier sorts by how recently the items were updated. + +| Qualifier | Пример | +| ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `sort:updated` or `sort:updated-desc` | [**feature sort:updated**](https://github.com/search?utf8=%E2%9C%93&q=feature+sort%3Aupdated&type=Repositories) matches repositories containing the word "feature," sorted by most recently updated date. | +| `sort:updated-asc` | [**feature sort:updated-asc**](https://github.com/search?utf8=%E2%9C%93&q=feature+sort%3Aupdated-asc&type=Repositories) matches repositories containing the word "feature," sorted by least recently updated date. | + +## Дополнительная литература + +- "[About searching on {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)" +- "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)" diff --git a/translations/ru-RU/content/search-github/getting-started-with-searching-on-github/troubleshooting-search-queries.md b/translations/ru-RU/content/search-github/getting-started-with-searching-on-github/troubleshooting-search-queries.md new file mode 100644 index 0000000000..84d03585c2 --- /dev/null +++ b/translations/ru-RU/content/search-github/getting-started-with-searching-on-github/troubleshooting-search-queries.md @@ -0,0 +1,34 @@ +--- +title: Troubleshooting search queries +intro: 'If you encounter unexpected results while searching on {% data variables.product.product_name %}, you can troubleshoot by reviewing common problems and limitations.' +redirect_from: + - /articles/troubleshooting-search-queries + - /github/searching-for-information-on-github/troubleshooting-search-queries + - /github/searching-for-information-on-github/getting-started-with-searching-on-github/troubleshooting-search-queries +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +shortTitle: Troubleshoot search queries +--- + +## Potential timeouts + +Some queries are computationally expensive for our search infrastructure to execute. To keep search fast for everyone, we limit how long any individual query can run. In rare situations when a query exceeds the time limit, search returns all matches that were found prior to the timeout and informs you that a timeout occurred. + +Reaching a timeout does not necessarily mean that search results are incomplete. It just means that the query was discontinued before it searched through all possible data. + +## Limitations on query length + +There are some limits to the length of the queries when searching across {% data variables.product.product_name %}: + +* Queries longer than 256 characters are not supported +* You can't construct a query using more than five `AND`, `OR`, or `NOT` operators + +Specific search types, such as code search, might have additional limitations. Check the documentation for these search types for more information. + +## Дополнительная литература + +- "[About searching on GitHub](/search-github/getting-started-with-searching-on-github/about-searching-on-github)" diff --git a/translations/ru-RU/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md b/translations/ru-RU/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md new file mode 100644 index 0000000000..406d442fb3 --- /dev/null +++ b/translations/ru-RU/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md @@ -0,0 +1,100 @@ +--- +title: Understanding the search syntax +intro: 'When searching {% data variables.product.product_name %}, you can construct queries that match specific numbers and words.' +redirect_from: + - /articles/search-syntax/ + - /articles/understanding-the-search-syntax + - /github/searching-for-information-on-github/understanding-the-search-syntax + - /github/searching-for-information-on-github/getting-started-with-searching-on-github/understanding-the-search-syntax +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +shortTitle: Understand search syntax +--- + +## Query for values greater or less than another value + +You can use `>`, `>=`, `<`, and `<=` to search for values that are greater than, greater than or equal to, less than, and less than or equal to another value. + +| Query | Пример | +| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| >n | **[cats stars:>1000](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%3E1000&type=Repositories)** matches repositories with the word "cats" that have more than 1000 stars. | +| >=n | **[cats topics:>=5](https://github.com/search?utf8=%E2%9C%93&q=cats+topics%3A%3E%3D5&type=Repositories)** matches repositories with the word "cats" that have 5 or more topics. | +| <n | **[cats size:<10000](https://github.com/search?utf8=%E2%9C%93&q=cats+size%3A%3C10000&type=Code)** matches code with the word "cats" in files that are smaller than 10 KB. | +| <=n | **[cats stars:<=50](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%3C%3D50&type=Repositories)** matches repositories with the word "cats" that have 50 or fewer stars. | + +You can also use [range queries](#query-for-values-between-a-range) to search for values that are greater than or equal to, or less than or equal to, another value. + +| Query | Пример | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| n..* | **[cats stars:10..*](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A10..*&type=Repositories)** is equivalent to `stars:>=10` and matches repositories with the word "cats" that have 10 or more stars. | +| *..n | **[cats stars:*..10](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%22*..10%22&type=Repositories)** is equivalent to `stars:<=10` and matches repositories with the word "cats" that have 10 or fewer stars. | + +## Query for values between a range + +You can use the range syntax n..n to search for values within a range, where the first number _n_ is the lowest value and the second is the highest value. + +| Query | Пример | +| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| n..n | **[cats stars:10..50](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A10..50&type=Repositories)** matches repositories with the word "cats" that have between 10 and 50 stars. | + +## Query for dates + +You can search for dates that are earlier or later than another date, or that fall within a range of dates, by using `>`, `>=`, `<`, `<=`, and [range queries](#query-for-values-between-a-range). {% data reusables.time_date.date_format %} + +| Query | Пример | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| >YYYY-MM-DD | **[cats created:>2016-04-29](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3E2016-04-29&type=Issues)** matches issues with the word "cats" that were created after April 29, 2016. | +| >=YYYY-MM-DD | **[cats created:>=2017-04-01](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3E%3D2017-04-01&type=Issues)** matches issues with the word "cats" that were created on or after April 1, 2017. | +| <YYYY-MM-DD | **[cats pushed:<2012-07-05](https://github.com/search?q=cats+pushed%3A%3C2012-07-05&type=Code&utf8=%E2%9C%93)** matches code with the word "cats" in repositories that were pushed to before July 5, 2012. | +| <=YYYY-MM-DD | **[cats created:<=2012-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3C%3D2012-07-04&type=Issues)** matches issues with the word "cats" that were created on or before July 4, 2012. | +| YYYY-MM-DD..YYYY-MM-DD | **[cats pushed:2016-04-30..2016-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+pushed%3A2016-04-30..2016-07-04&type=Repositories)** matches repositories with the word "cats" that were pushed to between the end of April and July of 2016. | +| YYYY-MM-DD..* | **[cats created:2012-04-30..*](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2012-04-30..*&type=Issues)** matches issues created after April 30th, 2012 containing the word "cats." | +| *..YYYY-MM-DD | **[cats created:*..2012-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A*..2012-07-04&type=Issues)** matches issues created before July 4th, 2012 containing the word "cats." | + +{% data reusables.time_date.time_format %} + +| Query | Пример | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| YYYY-MM-DDTHH:MM:SS+00:00 | **[cats created:2017-01-01T01:00:00+07:00..2017-03-01T15:30:15+07:00](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2017-01-01T01%3A00%3A00%2B07%3A00..2017-03-01T15%3A30%3A15%2B07%3A00&type=Issues)** matches issues created between January 1, 2017 at 1 a.m. with a UTC offset of `07:00` and March 1, 2017 at 3 p.m. with a UTC offset of `07:00`. | +| YYYY-MM-DDTHH:MM:SSZ | **[cats created:2016-03-21T14:11:00Z..2016-04-07T20:45:00Z](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2016-03-21T14%3A11%3A00Z..2016-04-07T20%3A45%3A00Z&type=Issues)** matches issues created between March 21, 2016 at 2:11pm and April 7, 2106 at 8:45pm. | + +## Exclude certain results + +You can exclude results containing a certain word, using the `NOT` syntax. The `NOT` operator can only be used for string keywords. It does not work for numerals or dates. + +| Query | Пример | +| ----- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `NOT` | **[hello NOT world](https://github.com/search?q=hello+NOT+world&type=Repositories)** matches repositories that have the word "hello" but not the word "world." | + +Another way you can narrow down search results is to exclude certain subsets. You can prefix any search qualifier with a `-` to exclude all results that are matched by that qualifier. + +| Query | Пример | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| -QUALIFIER | **[cats stars:>10 -language:javascript](https://github.com/search?q=cats+stars%3A>10+-language%3Ajavascript&type=Repositories)** matches repositories with the word "cats" that have more than 10 stars but are not written in JavaScript. | +| | **[mentions:defunkt -org:github](https://github.com/search?utf8=%E2%9C%93&q=mentions%3Adefunkt+-org%3Agithub&type=Issues)** matches issues mentioning @defunkt that are not in repositories in the GitHub organization | + +## Use quotation marks for queries with whitespace + +If your search query contains whitespace, you will need to surround it with quotation marks. Например: + +* [cats NOT "hello world"](https://github.com/search?utf8=✓&q=cats+NOT+"hello+world"&type=Repositories) matches repositories with the word "cats" but not the words "hello world." +* [build label:"bug fix"](https://github.com/search?utf8=%E2%9C%93&q=build+label%3A%22bug+fix%22&type=Issues) matches issues with the word "build" that have the label "bug fix." + +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 %} +## 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. + +| Query | Пример | +| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `QUALIFIER:USERNAME` | [`author:nat`](https://github.com/search?q=author%3Anat&type=Commits) matches commits authored by @nat | +| `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/translations/ru-RU/content/search-github/index.md b/translations/ru-RU/content/search-github/index.md new file mode 100644 index 0000000000..c70346fc97 --- /dev/null +++ b/translations/ru-RU/content/search-github/index.md @@ -0,0 +1,20 @@ +--- +title: Searching for information on GitHub +intro: Use different types of searches to find the information you want. +redirect_from: + - /categories/78/articles/ + - /categories/search/ + - /categories/searching-for-information-on-github + - /github/searching-for-information-on-github +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +children: + - /getting-started-with-searching-on-github + - /searching-on-github +shortTitle: Search on GitHub +--- + diff --git a/translations/ru-RU/content/search-github/searching-on-github/finding-files-on-github.md b/translations/ru-RU/content/search-github/searching-on-github/finding-files-on-github.md new file mode 100644 index 0000000000..fd070e349f --- /dev/null +++ b/translations/ru-RU/content/search-github/searching-on-github/finding-files-on-github.md @@ -0,0 +1,32 @@ +--- +title: Finding files on GitHub +intro: 'You can search for a file in a repository using the file finder. To search for a file in multiple repositories on {% data variables.product.product_name %}, use the [`filename` code search qualifier](/search-github/searching-on-github/searching-code#search-by-filename).' +redirect_from: + - /articles/finding-files-on-github + - /github/searching-for-information-on-github/finding-files-on-github + - /github/searching-for-information-on-github/searching-on-github/finding-files-on-github +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +{% tip %} + +**Советы:** + +- File finder results exclude some directories like `build`, `log`, `tmp`, and `vendor`. To search for files within these directories, use the [`filename` code search qualifier](/search-github/searching-on-github/searching-code#search-by-filename). +- You can also open the file finder by pressing `t` on your keyboard. For more information, see "[Keyboard shortcuts](/articles/keyboard-shortcuts)." + +{% endtip %} + +{% data reusables.repositories.navigate-to-repo %} +2. Above the list of files, click **Go to file**. ![Find file button](/assets/images/help/search/find-file-button.png) +3. In the search field, type the name of the file you'd like to find. ![Find file search field](/assets/images/help/search/find-file-search-field.png) +4. In the list of results, click the file you wanted to find. + +## Дополнительная литература + +- "[About searching on GitHub](/search-github/getting-started-with-searching-on-github/about-searching-on-github)" diff --git a/translations/ru-RU/content/search-github/searching-on-github/index.md b/translations/ru-RU/content/search-github/searching-on-github/index.md new file mode 100644 index 0000000000..40b2461457 --- /dev/null +++ b/translations/ru-RU/content/search-github/searching-on-github/index.md @@ -0,0 +1,27 @@ +--- +title: Searching on GitHub +intro: You can use qualifiers to narrow your search and focus on specific categories of information. +redirect_from: + - /articles/searching-on-github + - /github/searching-for-information-on-github/searching-on-github +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +children: + - /finding-files-on-github + - /searching-for-repositories + - /searching-topics + - /searching-code + - /searching-commits + - /searching-issues-and-pull-requests + - /searching-discussions + - /searching-github-marketplace + - /searching-users + - /searching-for-packages + - /searching-wikis + - /searching-in-forks +--- + diff --git a/translations/ru-RU/content/search-github/searching-on-github/searching-code.md b/translations/ru-RU/content/search-github/searching-on-github/searching-code.md new file mode 100644 index 0000000000..5848aa3759 --- /dev/null +++ b/translations/ru-RU/content/search-github/searching-on-github/searching-code.md @@ -0,0 +1,112 @@ +--- +title: Searching code +intro: 'You can search for code on {% data variables.product.product_name %} and narrow the results using these code search qualifiers in any combination.' +redirect_from: + - /articles/searching-code + - /github/searching-for-information-on-github/searching-files-in-a-repository-for-exact-matches + - /github/searching-for-information-on-github/searching-code-for-exact-matches + - /github/searching-for-information-on-github/searching-code + - /github/searching-for-information-on-github/searching-on-github/searching-code +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +{% data reusables.search.you-can-search-globally %} For more information, see "[About searching on GitHub](/search-github/getting-started-with-searching-on-github/about-searching-on-github)." + +You can only search code using these code search qualifiers. Search qualifiers specifically for repositories, users, or commits, will not work when searching for code. + +{% data reusables.search.syntax_tips %} + +## Considerations for code search + +Due to the complexity of searching code, there are some restrictions on how searches are performed: + +{% ifversion fpt or ghes %} +- {% data reusables.search.required_login %}{% endif %} +- Code in [forks](/articles/about-forks) is only searchable if the fork has more stars than the parent repository. Forks with fewer stars than the parent repository are **not** indexed for code search. To include forks with more stars than their parent in the search results, you will need to add `fork:true` or `fork:only` to your query. For more information, see "[Searching in forks](/search-github/searching-on-github/searching-in-forks)." +- Only the _default branch_ is indexed for code search.{% ifversion fpt %} +- Only files smaller than 384 KB are searchable.{% else %}* Only files smaller than 5 MB are searchable. +- Only the first 500 KB of each file is searchable.{% endif %} +- Only repositories with fewer than 500,000 files are searchable.{% ifversion fpt %} +- Only repositories that have had activity or have been returned in search results in the last year are searchable.{% endif %} +- Except with [`filename`](#search-by-filename) searches, you must always include at least one search term when searching source code. For example, searching for [`language:javascript`](https://github.com/search?utf8=%E2%9C%93&q=language%3Ajavascript&type=Code&ref=searchresults) is not valid, while [`amazing language:javascript`](https://github.com/search?utf8=%E2%9C%93&q=amazing+language%3Ajavascript&type=Code&ref=searchresults) is. +- At most, search results can show two fragments from the same file, but there may be more results within the file. +- You can't use the following wildcard characters as part of your search query: . , : ; / \ ` ' " = * ! ? # $ & + ^ | ~ < > ( ) { } [ ] @. The search will simply ignore these symbols. + +## Search by the file contents or file path + +With the `in` qualifier you can restrict your search to the contents of the source code file, the file path, or both. When you omit this qualifier, only the file contents are searched. + +| Qualifier | Пример | +| --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `in:file` | [**octocat in:file**](https://github.com/search?q=octocat+in%3Afile&type=Code) matches code where "octocat" appears in the file contents. | +| `in:path` | [**octocat in:path**](https://github.com/search?q=octocat+in%3Apath&type=Code) matches code where "octocat" appears in the file path. | +| | [**octocat in:file,path**](https://github.com/search?q=octocat+in%3Afile%2Cpath&type=Code) matches code where "octocat" appears in the file contents or the file path. | + +## Search within a user's or organization's repositories + +To search the code in all repositories owned by a certain user or organization, you can use the `user` or `org` qualifier. To search the code in a specific repository, you can use the `repo` qualifier. + +| Qualifier | Пример | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**user:defunkt extension:rb**](https://github.com/search?q=user%3Agithub+extension%3Arb&type=Code) matches code from @defunkt that ends in .rb. | +| org:ORGNAME | [**org:github extension:js**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+extension%3Ajs&type=Code) matches code from GitHub that ends in .js. | +| repo:USERNAME/REPOSITORY | [**repo:mozilla/shumway extension:as**](https://github.com/search?q=repo%3Amozilla%2Fshumway+extension%3Aas&type=Code) matches code from @mozilla's shumway project that ends in .as. | + +## Search by file location + +You can use the `path` qualifier to search for source code that appears at a specific location in a repository. Use `path:/` to search for files that are located at the root level of a repository. Or specify a directory name or the path to a directory to search for files that are located within that directory or any of its subdirectories. + +| Qualifier | Пример | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| path:/ | [**octocat filename:readme path:/**](https://github.com/search?utf8=%E2%9C%93&q=octocat+filename%3Areadme+path%3A%2F&type=Code) matches _readme_ files with the word "octocat" that are located at the root level of a repository. | +| path:DIRECTORY | [**form path:cgi-bin language:perl**](https://github.com/search?q=form+path%3Acgi-bin+language%3Aperl&type=Code) matches Perl files with the word "form" in the cgi-bin directory, or in any of its subdirectories. | +| path:PATH/TO/DIRECTORY | [**console path:app/public language:javascript**](https://github.com/search?q=console+path%3A%22app%2Fpublic%22+language%3Ajavascript&type=Code) matches JavaScript files with the word "console" in the app/public directory, or in any of its subdirectories (even if they reside in app/public/js/form-validators). | + +## Search by language + + +You can search for code based on what language it's written in. The `language` qualifier can be the language name or alias. For a full list of supported languages with their names and aliases, see the [github/linguist repository](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml). + +| Qualifier | Пример | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| language:LANGUAGE | [**element language:xml size:100**](https://github.com/search?q=element+language%3Axml+size%3A100&type=Code) matches code with the word "element" that's marked as being XML and has exactly 100 bytes. | +| | [**display language:scss**](https://github.com/search?q=display+language%3Ascss&type=Code) matches code with the word "display," that's marked as being SCSS. | +| | [**org:mozilla language:markdown**](https://github.com/search?utf8=%E2%9C%93&q=org%3Amozilla+language%3Amarkdown&type=Code) matches code from all @mozilla's repositories that's marked as Markdown. | + +## Search by file size + +You can use the `size` qualifier to search for source code based on the size of the file where the code exists. The `size` qualifier uses [greater than, less than, and range qualifiers](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax) to filter results based on the byte size of the file in which the code is found. + +| Qualifier | Пример | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| size:n | [**function size:>10000 language:python**](https://github.com/search?q=function+size%3A%3E10000+language%3Apython&type=Code) matches code with the word "function," written in Python, in files that are larger than 10 KB. | + +## Search by filename + +The `filename` qualifier matches code files with a certain filename. You can also find a file in a repository using the file finder. For more information, see "[Finding files on GitHub](/search-github/searching-on-github/finding-files-on-github)." + +| Qualifier | Пример | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| filename:FILENAME | [**filename:linguist**](https://github.com/search?utf8=%E2%9C%93&q=filename%3Alinguist&type=Code) matches files named "linguist." | +| | [**filename:.vimrc commands**](https://github.com/search?q=filename%3A.vimrc+commands&type=Code) matches *.vimrc* files with the word "commands." | +| | [**filename:test_helper path:test language:ruby**](https://github.com/search?q=minitest+filename%3Atest_helper+path%3Atest+language%3Aruby&type=Code) matches Ruby files named *test_helper* within the *test* directory. | + +## Search by file extension + +The `extension` qualifier matches code files with a certain file extension. + +| Qualifier | Пример | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| extension:EXTENSION | [**form path:cgi-bin extension:pm**](https://github.com/search?q=form+path%3Acgi-bin+extension%3Apm&type=Code) matches code with the word "form," under cgi-bin, with the .pm file extension. | +| | [**icon size:>200000 extension:css**](https://github.com/search?utf8=%E2%9C%93&q=icon+size%3A%3E200000+extension%3Acss&type=Code) matches files larger than 200 KB that end in .css and have the word "icon." | + +## Дополнительная литература + +- "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" +- "[Searching in forks](/search-github/searching-on-github/searching-in-forks)"{% ifversion fpt %} +- "[Navigating code on {% data variables.product.prodname_dotcom %}](/github/managing-files-in-a-repository/navigating-code-on-github)"{% endif %} diff --git a/translations/ru-RU/content/search-github/searching-on-github/searching-commits.md b/translations/ru-RU/content/search-github/searching-on-github/searching-commits.md new file mode 100644 index 0000000000..f5d36c72d0 --- /dev/null +++ b/translations/ru-RU/content/search-github/searching-on-github/searching-commits.md @@ -0,0 +1,111 @@ +--- +title: Searching commits +intro: 'You can search for commits on {% data variables.product.product_name %} and narrow the results using these commit search qualifiers in any combination.' +redirect_from: + - /articles/searching-commits + - /github/searching-for-information-on-github/searching-commits + - /github/searching-for-information-on-github/searching-on-github/searching-commits +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +You can search for commits globally across all of {% data variables.product.product_name %}, or search for commits within a particular repository or organization. For more information, see "[About searching on {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)." + +When you search for commits, only the [default branch](/articles/about-branches) of a repository is searched. + +{% data reusables.search.syntax_tips %} + +## Search within commit messages + +You can find commits that contain particular words in the message. For example, [**fix typo**](https://github.com/search?q=fix+typo&type=Commits) matches commits containing the words "fix" and "typo." + +## Search by author or committer + +You can find commits by a particular user with the `author` or `committer` qualifiers. + +| Qualifier | Пример | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | +| author:USERNAME | [**author:defunkt**](https://github.com/search?q=author%3Adefunkt&type=Commits) matches commits authored by @defunkt. | +| committer:USERNAME | [**committer:defunkt**](https://github.com/search?q=committer%3Adefunkt&type=Commits) matches commits committed by @defunkt. | + +The `author-name` and `committer-name` qualifiers match commits by the name of the author or committer. + +| Qualifier | Пример | +| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | +| author-name:NAME | [**author-name:wanstrath**](https://github.com/search?q=author-name%3Awanstrath&type=Commits) matches commits with "wanstrath" in the author name. | +| committer-name:NAME | [**committer-name:wanstrath**](https://github.com/search?q=committer-name%3Awanstrath&type=Commits) matches commits with "wanstrath" in the committer name. | + +The `author-email` and `committer-email` qualifiers match commits by the author's or committer's full email address. + +| Qualifier | Пример | +| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| author-email:EMAIL | [**author-email:chris@github.com**](https://github.com/search?q=author-email%3Achris%40github.com&type=Commits) matches commits authored by chris@github.com. | +| committer-email:EMAIL | [**committer-email:chris@github.com**](https://github.com/search?q=committer-email%3Achris%40github.com&type=Commits) matches commits committed by chris@github.com. | + +## Search by authored or committed date + +Use the `author-date` and `committer-date` qualifiers to match commits authored or committed within the specified date range. + +{% data reusables.search.date_gt_lt %} + +| Qualifier | Пример | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| author-date:YYYY-MM-DD | [**author-date:<2016-01-01**](https://github.com/search?q=author-date%3A<2016-01-01&type=Commits) matches commits authored before 2016-01-01. | +| committer-date:YYYY-MM-DD | [**committer-date:>2016-01-01**](https://github.com/search?q=committer-date%3A>2016-01-01&type=Commits) matches commits committed after 2016-01-01. | + +## Filter merge commits + +The `merge` qualifier filters merge commits. + +| Qualifier | Пример | +| ------------- | ---------------------------------------------------------------------------------------------------- | +| `merge:true` | [**merge:true**](https://github.com/search?q=merge%3Atrue&type=Commits) matches merge commits. | +| `merge:false` | [**merge:false**](https://github.com/search?q=merge%3Afalse&type=Commits) matches non-merge commits. | + +## Search by hash + +The `hash` qualifier matches commits with the specified SHA-1 hash. + +| Qualifier | Пример | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| hash:HASH | [**hash:124a9a0ee1d8f1e15e833aff432fbb3b02632105**](https://github.com/github/gitignore/search?q=hash%3A124a9a0ee1d8f1e15e833aff432fbb3b02632105&type=Commits) matches commits with the hash `124a9a0ee1d8f1e15e833aff432fbb3b02632105`. | + +## Search by parent + +The `parent` qualifier matches commits whose parent has the specified SHA-1 hash. + +| Qualifier | Пример | +| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| parent:HASH | [**parent:124a9a0ee1d8f1e15e833aff432fbb3b02632105**](https://github.com/github/gitignore/search?q=parent%3A124a9a0ee1d8f1e15e833aff432fbb3b02632105&type=Commits&utf8=%E2%9C%93) matches children of commits with the hash `124a9a0ee1d8f1e15e833aff432fbb3b02632105`. | + +## Search by tree + +The `tree` qualifier matches commits with the specified SHA-1 git tree hash. + +| Qualifier | Пример | +| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | +| tree:HASH | [**tree:99ca967**](https://github.com/github/gitignore/search?q=tree%3A99ca967&type=Commits) matches commits that refer to the tree hash `99ca967`. | + +## Search within a user's or organization's repositories + +To search commits in all repositories owned by a certain user or organization, use the `user` or `org` qualifier. To search commits in a specific repository, use the `repo` qualifier. + +| Qualifier | Пример | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**gibberish user:defunkt**](https://github.com/search?q=gibberish+user%3Adefunkt&type=Commits&utf8=%E2%9C%93) matches commit messages with the word "gibberish" in repositories owned by @defunkt. | +| org:ORGNAME | [**test org:github**](https://github.com/search?utf8=%E2%9C%93&q=test+org%3Agithub&type=Commits) matches commit messages with the word "test" in repositories owned by @github. | +| repo:USERNAME/REPO | [**language repo:defunkt/gibberish**](https://github.com/search?utf8=%E2%9C%93&q=language+repo%3Adefunkt%2Fgibberish&type=Commits) matches commit messages with the word "language" in @defunkt's "gibberish" repository. | + +## Filter by repository visibility + +The `is` qualifier matches commits from repositories with the specified visibility. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." + +| Qualifier | Example | ------------- | ------------- |{% ifversion fpt or ghes %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Commits) matches commits to public repositories.{% endif %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Commits) matches commits to internal repositories. | `is:private` | [**is:private**](https://github.com/search?q=is%3Aprivate&type=Commits) matches commits to private repositories. + +## Дополнительная литература + +- "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" diff --git a/translations/ru-RU/content/search-github/searching-on-github/searching-discussions.md b/translations/ru-RU/content/search-github/searching-on-github/searching-discussions.md new file mode 100644 index 0000000000..42c4968234 --- /dev/null +++ b/translations/ru-RU/content/search-github/searching-on-github/searching-discussions.md @@ -0,0 +1,113 @@ +--- +title: Searching discussions +intro: 'You can search for discussions on {% data variables.product.product_name %} and narrow the results using search qualifiers.' +versions: + fpt: '*' +topics: + - GitHub search +redirect_from: + - /github/searching-for-information-on-github/searching-discussions + - /github/searching-for-information-on-github/searching-on-github/searching-discussions +--- + +## About searching for discussions + +You can search for discussions globally across all of {% data variables.product.product_name %}, or search for discussions within a particular organization or repository. For more information, see "[About searching on {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/about-searching-on-github)." + +{% data reusables.search.syntax_tips %} + +## Search by the title, body, or comments + +With the `in` qualifier you can restrict your search for discussions to the title, body, or comments. You can also combine qualifiers to search a combination of title, body, or comments. When you omit the `in` qualifier, {% data variables.product.product_name %} searches the title, body, and comments. + +| Qualifier | Пример | +|:------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `in:title` | [**welcome in:title**](https://github.com/search?q=welcome+in%3Atitle&type=Discussions) matches discussions with "welcome" in the title. | +| `in:body` | [**onboard in:title,body**](https://github.com/search?q=onboard+in%3Atitle%2Cbody&type=Discussions) matches discussions with "onboard" in the title or body. | +| `in:comments` | [**thanks in:comments**](https://github.com/search?q=thanks+in%3Acomment&type=Discussions) matches discussions with "thanks" in the comments for the discussion. | + +## Search within a user's or organization's repositories + +To search discussions in all repositories owned by a certain user or organization, you can use the `user` or `org` qualifier. To search discussions in a specific repository, you can use the `repo` qualifier. + +| Qualifier | Пример | +|:------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**user:octocat feedback**](https://github.com/search?q=user%3Aoctocat+feedback&type=Discussions) matches discussions with the word "feedback" from repositories owned by @octocat. | +| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=Discussions&utf8=%E2%9C%93) matches discussions in repositories owned by the GitHub organization. | +| repo:USERNAME/REPOSITORY | [**repo:nodejs/node created:<2021-01-01**](https://github.com/search?q=repo%3Anodejs%2Fnode+created%3A%3C2020-01-01&type=Discussions) matches discussions from @nodejs' Node.js runtime project that were created before January 2021. | + +## Filter by repository visibility + +You can filter by the visibility of the repository containing the discussions using the `is` qualifier. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." + +| Qualifier | Example | :- | :- |{% ifversion fpt or ghes %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Discussions) matches discussions in public repositories.{% endif %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Discussions) matches discussions in internal repositories. | `is:private` | [**is:private tiramisu**](https://github.com/search?q=is%3Aprivate+tiramisu&type=Discussions) matches discussions that contain the word "tiramisu" in private repositories you can access. + +## Search by author + +The `author` qualifier finds discussions created by a certain user. + +| Qualifier | Пример | +|:------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| author:USERNAME | [**cool author:octocat**](https://github.com/search?q=cool+author%3Aoctocat&type=Discussions) matches discussions with the word "cool" that were created by @octocat. | +| | [**bootstrap in:body author:octocat**](https://github.com/search?q=bootstrap+in%3Abody+author%3Aoctocat&type=Discussions) matches discussions created by @octocat that contain the word "bootstrap" in the body. | + +## Search by commenter + +The `commenter` qualifier finds discussions that contain a comment from a certain user. + +| Qualifier | Пример | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| commenter:USERNAME | [**github commenter:becca org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Abecca+org%3Agithub&type=Discussions) matches discussions in repositories owned by GitHub, that contain the word "github," and have a comment by @becca. | + +## Search by a user that's involved in a discussion + +You can use the `involves` qualifier to find discussions that involve a certain user. The qualifier returns discussions that were either created by a certain user, mention the user, or contain comments by the user. The `involves` qualifier is a logical OR between the `author`, `mentions`, and `commenter` qualifiers for a single user. + +| Qualifier | Пример | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| involves:USERNAME | **[involves:becca involves:octocat](https://github.com/search?q=involves%3Abecca+involves%3Aoctocat&type=Discussions)** matches discussions either @becca or @octocat are involved in. | +| | [**NOT beta in:body involves:becca**](https://github.com/search?q=NOT+beta+in%3Abody+involves%3Abecca&type=Discussions) matches discussions @becca is involved in that do not contain the word "beta" in the body. | + +## Search by number of comments + +You can use the `comments` qualifier along with greater than, less than, and range qualifiers to search by the number of comments. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." + +| Qualifier | Пример | +|:------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------- | +| comments:n | [**comments:>100**](https://github.com/search?q=comments%3A%3E100&type=Discussions) matches discussions with more than 100 comments. | +| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Discussions) matches discussions with comments ranging from 500 to 1,000. | + +## Search by number of interactions + +You can filter discussions by the number of interactions with the `interactions` qualifier along with greater than, less than, and range qualifiers. The interactions count is the number of reactions and comments on a discussion. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." + +| Qualifier | Пример | +|:------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------- | +| interactions:n | [** interactions:>2000**](https://github.com/search?q=interactions%3A%3E2000) matches discussions with more than 2,000 interactions. | +| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) matches discussions with interactions ranging from 500 to 1,000. | + +## Search by number of reactions + +You can filter discussions by the number of reactions using the `reactions` qualifier along with greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." + +| Qualifier | Пример | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------ | +| reactions:n | [** reactions:>1000**](https://github.com/search?q=reactions%3A%3E500) matches discussions with more than 500 reactions. | +| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) matches discussions with reactions ranging from 500 to 1,000. | + +## Search by when a discussion was created or last updated + +You can filter discussions based on times of creation, or when the discussion was last updated. For discussion creation, you can use the `created` qualifier; to find out when an discussion was last updated, use the `updated` qualifier. + +Both qualifiers take a date as a parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifier | Пример | +|:-------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| created:YYYY-MM-DD | [**created:>2020-11-15**](https://github.com/search?q=created%3A%3E%3D2020-11-15&type=discussions) matches discussions that were created after November 15, 2020. | +| updated:YYYY-MM-DD | [**weird in:body updated:>=2020-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2020-12-01&type=Discussions) matches discussions with the word "weird" in the body that were updated after December 2020. | + +## Дополнительная литература + +- "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" diff --git a/translations/ru-RU/content/search-github/searching-on-github/searching-for-packages.md b/translations/ru-RU/content/search-github/searching-on-github/searching-for-packages.md new file mode 100644 index 0000000000..b93c80d965 --- /dev/null +++ b/translations/ru-RU/content/search-github/searching-on-github/searching-for-packages.md @@ -0,0 +1,45 @@ +--- +title: Searching for packages +intro: 'You can search for packages on {% data variables.product.product_name %} and narrow the results using search qualifiers.' +product: '{% data reusables.gated-features.packages %}' +permissions: Anyone can search for packages they have access to. +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +redirect_from: + - /github/searching-for-information-on-github/searching-for-packages + - /github/searching-for-information-on-github/searching-on-github/searching-for-packages +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +## About searching for packages + +You can search for packages globally across all of {% data variables.product.product_name %}, or search for packages within a particular organization. For more information, see "[About searching on {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)." + +{% ifversion ghes %} +You can only search for packages on {% data variables.product.product_name %}, not {% data variables.product.prodname_dotcom_the_website %}, even if {% data variables.product.prodname_github_connect %} is enabled. +{% endif %} + +{% data reusables.search.syntax_tips %} + +## Searching within a user's or organization's packages + +To find packages owned by a certain user or organization, use the `user` or `org` qualifier. + +| Qualifier | Пример | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| user:USERNAME | [**user:codertocat**](https://github.com/search?q=user%3Acodertocat&type=RegistryPackages) matches packages owned by @codertocat | +| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=RegistryPackages) matches packages owned by the {% data variables.product.prodname_dotcom %} organization | + +## Filtering by package visibility + +To filter your search by whether a package is public or private, use the `is` qualifier. + +| Qualifier | Пример | +| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `is:public` | [**is:public angular**](https://github.com/search?q=is%3Apublic+angular&type=RegistryPackages) matches public packages that contain the word "angular" | +| `is:private` | [**is:private php**](https://github.com/search?q=is%3Aprivate+php&type=RegistryPackages) matches private packages that contain the word "php" | diff --git a/translations/ru-RU/content/search-github/searching-on-github/searching-for-repositories.md b/translations/ru-RU/content/search-github/searching-on-github/searching-for-repositories.md new file mode 100644 index 0000000000..4461529d62 --- /dev/null +++ b/translations/ru-RU/content/search-github/searching-on-github/searching-for-repositories.md @@ -0,0 +1,201 @@ +--- +title: Searching for repositories +intro: 'You can search for repositories on {% data variables.product.product_name %} and narrow the results using these repository search qualifiers in any combination.' +redirect_from: + - /articles/searching-repositories/ + - /articles/searching-for-repositories + - /github/searching-for-information-on-github/searching-for-repositories + - /github/searching-for-information-on-github/searching-on-github/searching-for-repositories +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +shortTitle: Search for repositories +--- + +You can search for repositories globally across all of {% data variables.product.product_location %}, or search for repositories within a particular organization. For more information, see "[About searching on {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)." + +To include forks in the search results, you will need to add `fork:true` or `fork:only` to your query. For more information, see "[Searching in forks](/search-github/searching-on-github/searching-in-forks)." + +{% data reusables.search.syntax_tips %} + +## Search by repository name, description, or contents of the README file + +With the `in` qualifier you can restrict your search to the repository name, repository description, contents of the README file, or any combination of these. When you omit this qualifier, only the repository name and description are searched. + +| Qualifier | Пример | +| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `in:name` | [**jquery in:name**](https://github.com/search?q=jquery+in%3Aname&type=Repositories) matches repositories with "jquery" in the repository name. | +| `in:description` | [**jquery in:name,description**](https://github.com/search?q=jquery+in%3Aname%2Cdescription&type=Repositories) matches repositories with "jquery" in the repository name or description. | +| `in:readme` | [**jquery in:readme**](https://github.com/search?q=jquery+in%3Areadme&type=Repositories) matches repositories mentioning "jquery" in the repository's README file. | +| `repo:owner/name` | [**repo:octocat/hello-world**](https://github.com/search?q=repo%3Aoctocat%2Fhello-world) matches a specific repository name. | + +## Search based on the contents of a repository + +You can find a repository by searching for content in the repository's README file using the `in:readme` qualifier. For more information, see "[About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)." + +Besides using `in:readme`, it's not possible to find repositories by searching for specific content within the repository. To search for a specific file or content within a repository, you can use the file finder or code-specific search qualifiers. For more information, see "[Finding files on {% data variables.product.prodname_dotcom %}](/search-github/searching-on-github/finding-files-on-github)" and "[Searching code](/search-github/searching-on-github/searching-code)." + +| Qualifier | Пример | +| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `in:readme` | [**octocat in:readme**](https://github.com/search?q=octocat+in%3Areadme&type=Repositories) matches repositories mentioning "octocat" in the repository's README file. | + +## Search within a user's or organization's repositories + +To search in all repositories owned by a certain user or organization, you can use the `user` or `org` qualifier. + +| Qualifier | Пример | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**user:defunkt forks:>100**](https://github.com/search?q=user%3Adefunkt+forks%3A%3E%3D100&type=Repositories) matches repositories from @defunkt that have more than 100 forks. | +| org:ORGNAME | [**org:github**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub&type=Repositories) matches repositories from GitHub. | + +## Search by repository size + +The `size` qualifier finds repositories that match a certain size (in kilobytes), using greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." + +| Qualifier | Пример | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | +| size:n | [**size:1000**](https://github.com/search?q=size%3A1000&type=Repositories) matches repositories that are 1 MB exactly. | +| | [**size:>=30000**](https://github.com/search?q=size%3A%3E%3D30000&type=Repositories) matches repositories that are at least 30 MB. | +| | [**size:<50**](https://github.com/search?q=size%3A%3C50&type=Repositories) matches repositories that are smaller than 50 KB. | +| | [**size:50..120**](https://github.com/search?q=size%3A50..120&type=Repositories) matches repositories that are between 50 KB and 120 KB. | + +## Search by number of followers + +You can filter repositories based on the number of users who follow the repositories, using the `followers` qualifier with greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." + +| Qualifier | Пример | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| followers:n | [**node followers:>=10000**](https://github.com/search?q=node+followers%3A%3E%3D10000) matches repositories with 10,000 or more followers mentioning the word "node". | +| | [**styleguide linter followers:1..10**](https://github.com/search?q=styleguide+linter+followers%3A1..10&type=Repositories) matches repositories with between 1 and 10 followers, mentioning the word "styleguide linter." | + +## Search by number of forks + +The `forks` qualifier specifies the number of forks a repository should have, using greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." + +| Qualifier | Пример | +| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | +| forks:n | [**forks:5**](https://github.com/search?q=forks%3A5&type=Repositories) matches repositories with only five forks. | +| | [**forks:>=205**](https://github.com/search?q=forks%3A%3E%3D205&type=Repositories) matches repositories with at least 205 forks. | +| | [**forks:<90**](https://github.com/search?q=forks%3A%3C90&type=Repositories) matches repositories with fewer than 90 forks. | +| | [**forks:10..20**](https://github.com/search?q=forks%3A10..20&type=Repositories) matches repositories with 10 to 20 forks. | + +## Search by number of stars + +You can search repositories based on the number of stars the repositories have, using greater than, less than, and range qualifiers. For more information, see "[Saving repositories with stars](/github/getting-started-with-github/saving-repositories-with-stars)" and "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." + +| Qualifier | Пример | +| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| stars:n | [**stars:500**](https://github.com/search?utf8=%E2%9C%93&q=stars%3A500&type=Repositories) matches repositories with exactly 500 stars. | +| | [**stars:10..20**](https://github.com/search?q=stars%3A10..20+size%3A%3C1000&type=Repositories) matches repositories 10 to 20 stars, that are smaller than 1000 KB. | +| | [**stars:>=500 fork:true language:php**](https://github.com/search?q=stars%3A%3E%3D500+fork%3Atrue+language%3Aphp&type=Repositories) matches repositories with the at least 500 stars, including forked ones, that are written in PHP. | + +## Search by when a repository was created or last updated + +You can filter repositories based on time of creation or time of last update. For repository creation, you can use the `created` qualifier; to find out when a repository was last updated, you'll want to use the `pushed` qualifier. The `pushed` qualifier will return a list of repositories, sorted by the most recent commit made on any branch in the repository. + +Both take a date as a parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifier | Пример | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| created:YYYY-MM-DD | [**webos created:<2011-01-01**](https://github.com/search?q=webos+created%3A%3C2011-01-01&type=Repositories) matches repositories with the word "webos" that were created before 2011. | +| pushed:YYYY-MM-DD | [**css pushed:>2013-02-01**](https://github.com/search?utf8=%E2%9C%93&q=css+pushed%3A%3E2013-02-01&type=Repositories) matches repositories with the word "css" that were pushed to after January 2013. | +| | [**case pushed:>=2013-03-06 fork:only**](https://github.com/search?q=case+pushed%3A%3E%3D2013-03-06+fork%3Aonly&type=Repositories) matches repositories with the word "case" that were pushed to on or after March 6th, 2013, and that are forks. | + +## Search by language + +You can search repositories based on the language of the code in the repositories. + +| Qualifier | Пример | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| language:LANGUAGE | [**rails language:javascript**](https://github.com/search?q=rails+language%3Ajavascript&type=Repositories) matches repositories with the word "rails" that are written in JavaScript. | + +## Search by topic + +You can find all of the repositories that are classified with a particular topic. For more information, see "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)." + +| Qualifier | Пример | +| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| topic:TOPIC | [**topic:jekyll**](https://github.com/search?utf8=%E2%9C%93&q=topic%3Ajekyll&type=Repositories&ref=searchresults) matches repositories that have been classified with the topic "jekyll." | + +## Search by number of topics + +You can search repositories by the number of topics that have been applied to the repositories, using the `topics` qualifier along with greater than, less than, and range qualifiers. For more information, see "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)" and "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)." + +| Qualifier | Пример | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| topics:n | [**topics:5**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A5&type=Repositories&ref=searchresults) matches repositories that have five topics. | +| | [**topics:>3**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A%3E3&type=Repositories&ref=searchresults) matches repositories that have more than three topics. | + +{% ifversion fpt or ghes %} + +## Search by license + +You can search repositories by the type of license in the repositories. You must use a license keyword to filter repositories by a particular license or license family. For more information, see "[Licensing a repository](/github/creating-cloning-and-archiving-repositories/licensing-a-repository)." + +| Qualifier | Пример | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| license:LICENSE_KEYWORD | [**license:apache-2.0**](https://github.com/search?utf8=%E2%9C%93&q=license%3Aapache-2.0&type=Repositories&ref=searchresults) matches repositories that are licensed under Apache License 2.0. | + +{% endif %} + +## Search by repository visibility + +You can filter your search based on the visibility of the repositories. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." + +| Qualifier | Example | ------------- | ------------- |{% ifversion fpt or ghes %} | `is:public` | [**is:public org:github**](https://github.com/search?q=is%3Apublic+org%3Agithub&type=Repositories) matches public repositories owned by {% data variables.product.company_short %}.{% endif %} | `is:internal` | [**is:internal test**](https://github.com/search?q=is%3Ainternal+test&type=Repositories) matches internal repositories that you can access and contain the word "test". | `is:private` | [**is:private pages**](https://github.com/search?q=is%3Aprivate+pages&type=Repositories) matches private repositories that you can access and contain the word "pages." + +{% ifversion fpt %} + +## Search based on whether a repository is a mirror + +You can search repositories based on whether the repositories are mirrors and hosted elsewhere. 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)." + +| Qualifier | Пример | +| -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `mirror:true` | [**mirror:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Atrue+GNOME&type=) matches repositories that are mirrors and contain the word "GNOME." | +| `mirror:false` | [**mirror:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Afalse+GNOME&type=) matches repositories that are not mirrors and contain the word "GNOME." | + +{% endif %} + +## Search based on whether a repository is archived + +You can search repositories based on whether or not the repositories are archived. For more information, see "[Archiving repositories](/repositories/archiving-a-github-repository/archiving-repositories)." + +| Qualifier | Пример | +| ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `archived:true` | [**archived:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Atrue+GNOME&type=) matches repositories that are archived and contain the word "GNOME." | +| `archived:false` | [**archived:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Afalse+GNOME&type=) matches repositories that are not archived and contain the word "GNOME." | + +{% ifversion fpt %} + +## Search based on number of issues with `good first issue` or `help wanted` labels + +You can search for repositories that have a minimum number of issues labeled `help-wanted` or `good-first-issue` with the qualifiers `help-wanted-issues:>n` and `good-first-issues:>n`. For more information, see "[Encouraging helpful contributions to your project with labels](/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels)." + +| Qualifier | Пример | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `good-first-issues:>n` | [**good-first-issues:>2 javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+good-first-issues%3A%3E2&type=) matches repositories with more than two issues labeled `good-first-issue` and that contain the word "javascript." | +| `help-wanted-issues:>n` | [**help-wanted-issues:>4 react**](https://github.com/search?utf8=%E2%9C%93&q=react+help-wanted-issues%3A%3E4&type=) matches repositories with more than four issues labeled `help-wanted` and that contain the word "React." | + +## Search based on ability to sponsor + +You can search for repositories whose owners can be sponsored on {% data variables.product.prodname_sponsors %} with the `is:sponsorable` qualifier. For more information, see "[About {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." + +You can search for repositories that have a funding file using the `has:funding-file` qualifier. For more information, see "[About FUNDING files](/github/administering-a-repository/managing-repository-settings/displaying-a-sponsor-button-in-your-repository#about-funding-files)." + +| Qualifier | Пример | +| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `is:sponsorable` | [**is:sponsorable**](https://github.com/search?q=is%3Asponsorable&type=Repositories) matches repositories whose owners have a {% data variables.product.prodname_sponsors %} profile. | +| `has:funding-file` | [**has:funding-file**](https://github.com/search?q=has%3Afunding-file&type=Repositories) matches repositories that have a FUNDING.yml file. | + +{% endif %} + +## Дополнительная литература + +- "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" +- "[Searching in forks](/search-github/searching-on-github/searching-in-forks)" diff --git a/translations/ru-RU/content/search-github/searching-on-github/searching-github-marketplace.md b/translations/ru-RU/content/search-github/searching-on-github/searching-github-marketplace.md new file mode 100644 index 0000000000..fd124f974b --- /dev/null +++ b/translations/ru-RU/content/search-github/searching-on-github/searching-github-marketplace.md @@ -0,0 +1,38 @@ +--- +title: Searching GitHub Marketplace +intro: 'You can search for apps and actions that are available on {% data variables.product.prodname_marketplace %}.' +versions: + fpt: '*' +topics: + - GitHub search +redirect_from: + - /github/searching-for-information-on-github/searching-github-marketplace + - /github/searching-for-information-on-github/searching-on-github/searching-github-marketplace +shortTitle: Search GitHub Marketplace +--- + +## About searching {% data variables.product.prodname_marketplace %} + +You can find apps and actions on {% data variables.product.prodname_marketplace %} in two ways: + +- Search from in {% data variables.product.prodname_marketplace %}. +- Search across all of {% data variables.product.prodname_dotcom_the_website %} and then filter the results. + +## Searching in {% data variables.product.prodname_marketplace %} + +1. At the top of any page, click **Marketplace**. ![Marketplace link](/assets/images/help/search/marketplace-link.png) +2. Type any keywords and press **Enter**. ![Search for linter on {% data variables.product.prodname_marketplace %}](/assets/images/help/search/marketplace-apps-and-actions-search-field.png) +3. Optionally, filter your results by clicking one or more options in the left sidebar. + +## Searching across {% data variables.product.prodname_dotcom_the_website %} + +Anytime you search across all of {% data variables.product.prodname_dotcom_the_website %}, you can filter the results to see matching apps and actions from {% data variables.product.prodname_marketplace %}. + +1. Navigate to https://github.com/search. +2. Type any keywords and press **Enter**. ![search field](/assets/images/help/search/search-field.png) +3. In the left sidebar, click **Marketplace**. ![Search results for linter with Marketplace side-menu option highlighted](/assets/images/help/search/marketplace-left-side-navigation.png) + +## Дополнительная литература + +- "[About {% data variables.product.prodname_marketplace %}](/github/customizing-your-github-workflow/about-github-marketplace)" +- "[Using actions from {% data variables.product.prodname_marketplace %} in your workflow](/actions/automating-your-workflow-with-github-actions/using-actions-from-github-marketplace-in-your-workflow)" diff --git a/translations/ru-RU/content/search-github/searching-on-github/searching-in-forks.md b/translations/ru-RU/content/search-github/searching-on-github/searching-in-forks.md new file mode 100644 index 0000000000..158e4ae025 --- /dev/null +++ b/translations/ru-RU/content/search-github/searching-on-github/searching-in-forks.md @@ -0,0 +1,32 @@ +--- +title: Searching in forks +intro: 'By default, [forks](/articles/about-forks) are not shown in search results. You can choose to include them in repository searches, and in code searches if they meet certain criteria.' +redirect_from: + - /articles/searching-in-forks + - /github/searching-for-information-on-github/searching-in-forks + - /github/searching-for-information-on-github/searching-on-github/searching-in-forks +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +To show forks in [repository search](/search-github/searching-on-github/searching-for-repositories) results, add `fork:true` or `fork:only` to your query. + +Forks are only indexed for [code search](/search-github/searching-on-github/searching-code) when they have more stars than the parent repository. You will not be able to search the code in a fork that has less stars than its parent. To show forks with more stars than the parent repository in code search results, add `fork:true` or `fork:only` to your query. + +The `fork:true` qualifier finds all results that match your search query, including forks. The `fork:only` qualifier finds _only_ forks that match your search query. + +| Qualifier | Пример | +| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `fork:true` | [**github fork:true**](https://github.com/search?q=github+fork%3Atrue&type=Repositories) matches all repositories containing the word "github," including forks. | +| | [**android language:java fork:true**](https://github.com/search?q=android+language%3Ajava+fork%3Atrue&type=Code) matches code with the word "android" that's written in Java, in both forks and regular repositories. | +| `fork:only` | [**github fork:only**](https://github.com/search?q=github+fork%3Aonly&type=Repositories) matches all fork repositories containing the word "github." | +| | [**forks:>500 fork:only**](https://github.com/search?q=forks%3A%3E500+fork%3Aonly&type=Repositories) matches repositories with more than 500 forks, and only returns those that are forks. | + +## Дополнительная литература + +- "[About forks](/articles/about-forks)" +- "[About searching on GitHub](/search-github/getting-started-with-searching-on-github/about-searching-on-github)" diff --git a/translations/ru-RU/content/search-github/searching-on-github/searching-issues-and-pull-requests.md b/translations/ru-RU/content/search-github/searching-on-github/searching-issues-and-pull-requests.md new file mode 100644 index 0000000000..be3f9d1260 --- /dev/null +++ b/translations/ru-RU/content/search-github/searching-on-github/searching-issues-and-pull-requests.md @@ -0,0 +1,343 @@ +--- +title: Searching issues and pull requests +intro: 'You can search for issues and pull requests on {% data variables.product.product_name %} and narrow the results using these search qualifiers in any combination.' +redirect_from: + - /articles/searching-issues/ + - /articles/searching-issues-and-pull-requests + - /github/searching-for-information-on-github/searching-issues-and-pull-requests + - /github/searching-for-information-on-github/searching-on-github/searching-issues-and-pull-requests +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +shortTitle: Search issues & PRs +--- + +You can search for issues and pull requests globally across all of {% data variables.product.product_name %}, or search for issues and pull requests within a particular organization. For more information, see "[About searching on {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)." + +{% tip %} + +**Tips:**{% ifversion ghes or ghae %} + - This article contains example searches on the {% data variables.product.prodname_dotcom %}.com website, but you can use the same search filters on {% data variables.product.product_location %}.{% endif %} + - For a list of search syntaxes that you can add to any search qualifier to further improve your results, see "[Understanding the search syntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)". + - Use quotations around multi-word search terms. For example, if you want to search for issues with the label "In progress," you'd search for `label:"in progress"`. Search is not case sensitive. + - {% data reusables.search.search_issues_and_pull_requests_shortcut %} + + {% endtip %} + +## Search only issues or pull requests + +By default, {% data variables.product.product_name %} search will return both issues and pull requests. However, you can restrict search results to just issues or pull requests using the `type` or `is` qualifier. + +| Qualifier | Пример | +| ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `type:pr` | [**cat type:pr**](https://github.com/search?q=cat+type%3Apr&type=Issues) matches pull requests with the word "cat." | +| `type:issue` | [**github commenter:defunkt type:issue**](https://github.com/search?q=github+commenter%3Adefunkt+type%3Aissue&type=Issues) matches issues that contain the word "github," and have a comment by @defunkt. | +| `is:pr` | [**event is:pr**](https://github.com/search?utf8=%E2%9C%93&q=event+is%3Apr&type=) matches pull requests with the word "event." | +| `is:issue` | [**is:issue label:bug is:closed**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aissue+label%3Abug+is%3Aclosed&type=) matches closed issues with the label "bug." | + +## Search by the title, body, or comments + +With the `in` qualifier you can restrict your search to the title, body, comments, or any combination of these. When you omit this qualifier, the title, body, and comments are all searched. + +| Qualifier | Пример | +| ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | +| `in:title` | [**warning in:title**](https://github.com/search?q=warning+in%3Atitle&type=Issues) matches issues with "warning" in their title. | +| `in:body` | [**error in:title,body**](https://github.com/search?q=error+in%3Atitle%2Cbody&type=Issues) matches issues with "error" in their title or body. | +| `in:comments` | [**shipit in:comments**](https://github.com/search?q=shipit+in%3Acomment&type=Issues) matches issues mentioning "shipit" in their comments. | + +## Search within a user's or organization's repositories + +To search issues and pull requests in all repositories owned by a certain user or organization, you can use the `user` or `org` qualifier. To search issues and pull requests in a specific repository, you can use the `repo` qualifier. + +{% data reusables.pull_requests.large-search-workaround %} + + +| Qualifier | Пример | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 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. + +| Qualifier | Пример | +| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `state:open` | [**libraries state:open mentions:vmg**](https://github.com/search?utf8=%E2%9C%93&q=libraries+state%3Aopen+mentions%3Avmg&type=Issues) matches open issues that mention @vmg with the word "libraries." | +| `state:closed` | [**design state:closed in:body**](https://github.com/search?utf8=%E2%9C%93&q=design+state%3Aclosed+in%3Abody&type=Issues) matches closed issues with the word "design" in the body. | +| `is:open` | [**performance is:open is:issue**](https://github.com/search?q=performance+is%3Aopen+is%3Aissue&type=Issues) matches open issues with the word "performance." | +| `is:closed` | [**android is:closed**](https://github.com/search?utf8=%E2%9C%93&q=android+is%3Aclosed&type=) matches closed issues and pull requests with the word "android." | + +## Filter by repository visibility + +You can filter by the visibility of the repository containing the issues and pull requests using the `is` qualifier. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." + +| Qualifier | Example | ------------- | ------------- |{% ifversion fpt or ghes %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Issues) matches issues and pull requests in public repositories.{% endif %}{% ifversion fpt or ghes or ghae %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Issues) matches issues and pull requests in internal repositories.{% endif %} | `is:private` | [**is:private cupcake**](https://github.com/search?q=is%3Aprivate+cupcake&type=Issues) matches issues and pull requests that contain the word "cupcake" in private repositories you can access. + +## Search by author + +The `author` qualifier finds issues and pull requests created by a certain user or integration account. + +| Qualifier | Пример | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| author:USERNAME | [**cool author:gjtorikian**](https://github.com/search?q=cool+author%3Agjtorikian&type=Issues) matches issues and pull requests with the word "cool" that were created by @gjtorikian. | +| | [**bootstrap in:body author:mdo**](https://github.com/search?q=bootstrap+in%3Abody+author%3Amdo&type=Issues) matches issues written by @mdo that contain the word "bootstrap" in the body. | +| author:app/USERNAME | [**author:app/robot**](https://github.com/search?q=author%3Aapp%2Frobot&type=Issues) matches issues created by the integration account named "robot." | + +## Search by assignee + +The `assignee` qualifier finds issues and pull requests that are assigned to a certain user. You cannot search for issues and pull requests that have _any_ assignee, however, you can search for [issues and pull requests that have no assignee](#search-by-missing-metadata). + +| Qualifier | Пример | +| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| assignee:USERNAME | [**assignee:vmg repo:libgit2/libgit2**](https://github.com/search?utf8=%E2%9C%93&q=assignee%3Avmg+repo%3Alibgit2%2Flibgit2&type=Issues) matches issues and pull requests in libgit2's project libgit2 that are assigned to @vmg. | + +## Search by mention + +The `mentions` qualifier finds issues that mention a certain user. For more information, see "[Mentioning people and teams](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)." + +| Qualifier | Пример | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| mentions:USERNAME | [**resque mentions:defunkt**](https://github.com/search?q=resque+mentions%3Adefunkt&type=Issues) matches issues with the word "resque" that mention @defunkt. | + +## Search by team mention + +For organizations and teams you belong to, you can use the `team` qualifier to find issues or pull requests that @mention a certain team within that organization. Replace these sample names with your organization and team name to perform a search. + +| Qualifier | Пример | +| ------------------------- | ----------------------------------------------------------------------------------------------------- | +| team:ORGNAME/TEAMNAME | **team:jekyll/owners** matches issues where the `@jekyll/owners` team is mentioned. | +| | **team:myorg/ops is:open is:pr** matches open pull requests where the `@myorg/ops` team is mentioned. | + +## Search by commenter + +The `commenter` qualifier finds issues that contain a comment from a certain user. + +| Qualifier | Пример | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| commenter:USERNAME | [**github commenter:defunkt org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Adefunkt+org%3Agithub&type=Issues) matches issues in repositories owned by GitHub, that contain the word "github," and have a comment by @defunkt. | + +## Search by a user that's involved in an issue or pull request + +You can use the `involves` qualifier to find issues that in some way involve a certain user. The `involves` qualifier is a logical OR between the `author`, `assignee`, `mentions`, and `commenter` qualifiers for a single user. In other words, this qualifier finds issues and pull requests that were either created by a certain user, assigned to that user, mention that user, or were commented on by that user. + +| Qualifier | Пример | +| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 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 %} +## 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. + +| Qualifier | Пример | +| --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `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 %} + +## Search by label + +You can narrow your results by labels, using the `label` qualifier. Since issues can have multiple labels, you can list a separate qualifier for each issue. + +| Qualifier | Пример | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| label:LABEL | [**label:"help wanted" language:ruby**](https://github.com/search?utf8=%E2%9C%93&q=label%3A%22help+wanted%22+language%3Aruby&type=Issues) matches issues with the label "help wanted" that are in Ruby repositories. | +| | [**broken in:body -label:bug label:priority**](https://github.com/search?q=broken+in%3Abody+-label%3Abug+label%3Apriority&type=Issues) matches issues with the word "broken" in the body, that lack the label "bug", but *do* have the label "priority." | +| | [**label:bug label:resolved**](https://github.com/search?l=&q=label%3Abug+label%3Aresolved&type=Issues) matches issues with the labels "bug" and "resolved."{% ifversion fpt or ghes > 3.2 or ghae-next %} +| | [**label:bug,resolved**](https://github.com/search?q=label%3Abug%2Cresolved&type=Issues) matches issues with the label "bug" or the label "resolved."{% endif %} + +## Search by milestone + +The `milestone` qualifier finds issues or pull requests that are a part of a [milestone](/articles/about-milestones) within a repository. + +| Qualifier | Пример | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| milestone:MILESTONE | [**milestone:"overhaul"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22overhaul%22&type=Issues) matches issues that are in a milestone named "overhaul." | +| | [**milestone:"bug fix"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22bug+fix%22&type=Issues) matches issues that are in a milestone named "bug fix." | + +## Search by project board + +You can use the `project` qualifier to find issues that are associated with a specific [project board](/articles/about-project-boards/) in a repository or organization. You must search project boards by the project board number. You can find the project board number at the end of a project board's URL. + +| Qualifier | Пример | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------- | +| project:PROJECT_BOARD | **project:github/57** matches issues owned by GitHub that are associated with the organization's project board 57. | +| project:REPOSITORY/PROJECT_BOARD | **project:github/linguist/1** matches issues that are associated with project board 1 in @github's linguist repository. | + +## Search by commit status + +You can filter pull requests based on the status of the commits. This is especially useful if you are using [the Status API](/rest/reference/repos#statuses) or a CI service. + +| Qualifier | Пример | +| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `status:pending` | [**language:go status:pending**](https://github.com/search?utf8=%E2%9C%93&q=language%3Ago+status%3Apending) matches pull requests opened into Go repositories where the status is pending. | +| `status:success` | [**is:open status:success finally in:body**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aopen+status%3Asuccess+finally+in%3Abody&type=Issues) matches open pull requests with the word "finally" in the body with a successful status. | +| `status:failure` | [**created:2015-05-01..2015-05-30 status:failure**](https://github.com/search?utf8=%E2%9C%93&q=created%3A2015-05-01..2015-05-30+status%3Afailure&type=Issues) matches pull requests opened on May 2015 with a failed status. | + +## Search by commit SHA + +If you know the specific SHA hash of a commit, you can use it to search for pull requests that contain that SHA. The SHA syntax must be at least seven characters. + +| Qualifier | Пример | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| SHA | [**e1109ab**](https://github.com/search?q=e1109ab&type=Issues) matches pull requests with a commit SHA that starts with `e1109ab`. | +| | [**0eff326d6213c is:merged**](https://github.com/search?q=0eff326d+is%3Amerged&type=Issues) matches merged pull requests with a commit SHA that starts with `0eff326d6213c`. | + +## Search by branch name + +You can filter pull requests based on the branch they came from (the "head" branch) or the branch they are merging into (the "base" branch). + +| Qualifier | Пример | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| head:HEAD_BRANCH | [**head:change is:closed is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=head%3Achange+is%3Aclosed+is%3Aunmerged) matches pull requests opened from branch names beginning with the word "change" that are closed. | +| base:BASE_BRANCH | [**base:gh-pages**](https://github.com/search?utf8=%E2%9C%93&q=base%3Agh-pages) matches pull requests that are being merged into the `gh-pages` branch. | + +## Search by language + +With the `language` qualifier you can search for issues and pull requests within repositories that are written in a certain language. + +| Qualifier | Пример | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | +| language:LANGUAGE | [**language:ruby state:open**](https://github.com/search?q=language%3Aruby+state%3Aopen&type=Issues) matches open issues that are in Ruby repositories. | + +## Search by number of 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. + +| Qualifier | Пример | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| comments:n | [**state:closed comments:>100**](https://github.com/search?q=state%3Aclosed+comments%3A%3E100&type=Issues) matches closed issues with more than 100 comments. | +| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Issues) matches issues with comments ranging from 500 to 1,000. | + +## Search by number of interactions + +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). The interactions count is the number of reactions and comments on an issue or pull request. + +| Qualifier | Пример | +| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| interactions:n | [** interactions:>2000**](https://github.com/search?q=interactions%3A%3E2000) matches pull requests or issues with more than 2000 interactions. | +| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) matches pull requests or issues with interactions ranging from 500 to 1,000. | + +## Search by number of reactions + +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 | Пример | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | +| reactions:n | [** reactions:>1000**](https://github.com/search?q=reactions%3A%3E1000&type=Issues) matches issues with more than 1000 reactions. | +| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) matches issues with reactions ranging from 500 to 1,000. | + +## Search for draft pull requests +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 %} | `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 %} + +## Search by pull request review status and reviewer + +You can filter pull requests based on their [review status](/articles/about-pull-request-reviews) (_none_, _required_, _approved_, or _changes requested_), by reviewer, and by requested reviewer. + +| Qualifier | Пример | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `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. Requested reviewers are no longer listed in the search results after they review a pull request. 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 or ghes > 3.2 %} +| 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) matches pull requests that have review requests from the team `atom/design`. Requested reviewers are no longer listed in the search results after they review a pull request. | + +## Search by when an issue or pull request was created or last updated + +You can filter issues based on times of creation, or when they were last updated. For issue creation, you can use the `created` qualifier; to find out when an issue was last updated, you'll want to use the `updated` qualifier. + +Both take a date as a parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifier | Пример | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| created:YYYY-MM-DD | [**language:c# created:<2011-01-01 state:open**](https://github.com/search?q=language%3Ac%23+created%3A%3C2011-01-01+state%3Aopen&type=Issues) matches open issues that were created before 2011 in repositories written in C#. | +| updated:YYYY-MM-DD | [**weird in:body updated:>=2013-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2013-02-01&type=Issues) matches issues with the word "weird" in the body that were updated after February 2013. | + +## Search by when an issue or pull request was closed + +You can filter issues and pull requests based on when they were closed, using the `closed` qualifier. + +This qualifier takes a date as its parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifier | Пример | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| closed:YYYY-MM-DD | [**language:swift closed:>2014-06-11**](https://github.com/search?q=language%3Aswift+closed%3A%3E2014-06-11&type=Issues) matches issues and pull requests in Swift that were closed after June 11, 2014. | +| | [**data in:body closed:<2012-10-01**](https://github.com/search?utf8=%E2%9C%93&q=data+in%3Abody+closed%3A%3C2012-10-01+&type=Issues) matches issues and pull requests with the word "data" in the body that were closed before October 2012. | + +## Search by when a pull request was merged + +You can filter pull requests based on when they were merged, using the `merged` qualifier. + +This qualifier takes a date as its parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifier | Пример | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| merged:YYYY-MM-DD | [**language:javascript merged:<2011-01-01**](https://github.com/search?q=language%3Ajavascript+merged%3A%3C2011-01-01+&type=Issues) matches pull requests in JavaScript repositories that were merged before 2011. | +| | [**fast in:title language:ruby merged:>=2014-05-01**](https://github.com/search?q=fast+in%3Atitle+language%3Aruby+merged%3A%3E%3D2014-05-01+&type=Issues) matches pull requests in Ruby with the word "fast" in the title that were merged after May 2014. | + +## Search based on whether a pull request is merged or unmerged + +You can filter pull requests based on whether they're merged or unmerged using the `is` qualifier. + +| Qualifier | Пример | +| ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `is:merged` | [**bugfix is:pr is:merged**](https://github.com/search?utf8=%E2%9C%93&q=bugfix+is%3Apr+is%3Amerged&type=) matches merged pull requests with the word "bugfix." | +| `is:unmerged` | [**error is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=error+is%3Aunmerged&type=) matches closed issues and pull requests with the word "error." | + +## Search based on whether a repository is archived + +The `archived` qualifier filters your results based on whether an issue or pull request is in an archived repository. + +| Qualifier | Пример | +| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `archived:true` | [**archived:true GNOME**](https://github.com/search?q=archived%3Atrue+GNOME&type=) matches issues and pull requests that contain the word "GNOME" in archived repositories you have access to. | +| `archived:false` | [**archived:false GNOME**](https://github.com/search?q=archived%3Afalse+GNOME&type=) matches issues and pull requests that contain the word "GNOME" in unarchived repositories you have access to. | + +## Search based on whether a conversation is locked + +You can search for an issue or pull request that has a locked conversation using the `is` qualifier. For more information, see "[Locking conversations](/communities/moderating-comments-and-conversations/locking-conversations)." + +| Qualifier | Пример | +| ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `is:locked` | [**code of conduct is:locked is:issue archived:false**](https://github.com/search?q=code+of+conduct+is%3Alocked+is%3Aissue+archived%3Afalse) matches issues or pull requests with the words "code of conduct" that have a locked conversation in a repository that is not archived. | +| `is:unlocked` | [**code of conduct is:unlocked is:issue archived:false**](https://github.com/search?q=code+of+conduct+is%3Aunlocked+archived%3Afalse) matches issues or pull requests with the words "code of conduct" that have an unlocked conversation in a repository that is not archived. | + +## Search by missing metadata + +You can narrow your search to issues and pull requests that are missing certain metadata, using the `no` qualifier. That metadata includes: + +* Labels +* Milestones +* Assignees +* Projects + +| Qualifier | Пример | +| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `no:label` | [**priority no:label**](https://github.com/search?q=priority+no%3Alabel&type=Issues) matches issues and pull requests with the word "priority" that also don't have any labels. | +| `no:milestone` | [**sprint no:milestone type:issue**](https://github.com/search?q=sprint+no%3Amilestone+type%3Aissue&type=Issues) matches issues not associated with a milestone containing the word "sprint." | +| `no:assignee` | [**important no:assignee language:java type:issue**](https://github.com/search?q=important+no%3Aassignee+language%3Ajava+type%3Aissue&type=Issues) matches issues not associated with an assignee, containing the word "important," and in Java repositories. | +| `no:project` | [**build no:project**](https://github.com/search?utf8=%E2%9C%93&q=build+no%3Aproject&type=Issues) matches issues not associated with a project board, containing the word "build." | + +## Дополнительная литература + +- "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" diff --git a/translations/ru-RU/content/search-github/searching-on-github/searching-topics.md b/translations/ru-RU/content/search-github/searching-on-github/searching-topics.md new file mode 100644 index 0000000000..2b8bd21fa3 --- /dev/null +++ b/translations/ru-RU/content/search-github/searching-on-github/searching-topics.md @@ -0,0 +1,55 @@ +--- +title: Searching topics +intro: 'You can search for topics associated with repositories on {% data variables.product.product_name %}.' +redirect_from: + - /articles/searching-topics + - /github/searching-for-information-on-github/searching-topics + - /github/searching-for-information-on-github/searching-on-github/searching-topics +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +## Search {% data variables.product.product_name %} for topics + +You can search for topics on {% data variables.product.product_name %}, explore related topics, and see how many repositories are associated with a certain topic. + +1. Navigate to https://github.com/search. +2. Type a topic keyword. ![search field](/assets/images/help/search/search-field.png) +3. In the left sidebar, to narrow your search to topics, click **Topics**. +{% ifversion fpt %} + ![Jekyll repository search results page with topics side-menu option highlighted](/assets/images/help/search/topic-left-side-navigation-dotcom.png){% else %} +![Jekyll repository search results page on dotcom with topics side-menu option highlighted](/assets/images/help/search/topic-left-side-navigation.png){% endif %} + +## Narrowing your search with search qualifiers + +If you want to explore repositories about a certain topic, find projects to contribute to, or learn which topics are most popular on {% data variables.product.product_name %}, you can search topics with the search qualifiers `is:featured`, `is:curated`, `repositories:n` and `created:YYYY-MM-DD`. + +The `is:featured` search qualifier will narrow search results to the topics with the most repositories on {% data variables.product.product_name %}. These topics are also featured at https://github.com/topics/. + +The `is:curated` search qualifier will narrow search results to topics that community members have added extra information to. For more information, see the [explore repository](https://github.com/github/explore). + +You can filter topics based when they were created using the date parameter and `created:` or based on how many repositories are associated with this topic using `repositories:n`. Both of these qualifiers can use the [greater than and less than range qualifiers](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). + +{% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifier | Пример | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `is:curated` | [**is:curated javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+is%3Acurated&type=Topics) matches topics that are curated and contain the word "javascript." | +| `is:featured` | [**is:featured javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+is%3Afeatured&type=Topics) matches topics that are featured on https://github.com/topics/ and contain the word "javascript." | +| `is:not-curated` | [**is:not-curated javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+is%3Anot-curated&type=Topics) matches topics that don't have extra information, such as a description or logo, and contain the word "javascript." | +| `is:not-featured` | [**is:not-featured javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+is%3Anot-featured&type=Topics) matches topics that aren't featured on https://github.com/topics/ and contain the word "javascript." | +| `repositories:n` | [**repositories:>5000**](https://github.com/search?q=repositories%3A%3E5000) matches topics that have more than 5000 repositories. | +| created:YYYY-MM-DD | [**Serverless created:>2019-01-01**](https://github.com/search?q=Serverless+created%3A%3E2019-01-01&type=Topics) matches topics with the word "serverless" that were created after 2018. | + +## Search repositories by topic + +You can use the `topic:` qualifier to find every repository connected to a particular topic. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories/#search-by-topic)." + +## Дополнительная литература +- "[Classifying your repository with topics](/articles/classifying-your-repository-with-topics)" diff --git a/translations/ru-RU/content/search-github/searching-on-github/searching-users.md b/translations/ru-RU/content/search-github/searching-on-github/searching-users.md new file mode 100644 index 0000000000..02bf07c103 --- /dev/null +++ b/translations/ru-RU/content/search-github/searching-on-github/searching-users.md @@ -0,0 +1,106 @@ +--- +title: Searching users +intro: 'You can search for users on {% data variables.product.product_name %} and narrow the results using these user search qualifiers in any combination.' +redirect_from: + - /articles/searching-users + - /github/searching-for-information-on-github/searching-users + - /github/searching-for-information-on-github/searching-on-github/searching-users +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +You can search for users globally across all of {% data variables.product.product_name %}. For more information, see "[About searching on {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)." + +{% data reusables.search.syntax_tips %} + +## Search only users or organizations + +By default, searching users will return both personal and organizations. However, you can use the `type` qualifier to restrict search results to personal accounts or organizations only. + +| Qualifier | Пример | +| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `type:user` | [**mike in:name created:<2011-01-01 type:user**](https://github.com/search?q=mike+in:name+created%3A%3C2011-01-01+type%3Auser&type=Users) matches personal accounts named "mike" that were created before 2011. | +| `type:org` | [**data in:email type:org**](https://github.com/search?q=data+in%3Aemail+type%3Aorg&type=Users) matches organizations with the word "data" in their email. | + +## Search by account name, full name, or public email + +You can filter your search to the personal user or organization account name with `user` or `org` qualifiers. + +With the `in` qualifier you can restrict your search to the username (`login`), full name, public email, or any combination of these. When you omit this qualifier, only the username and email address are searched. For privacy reasons, you cannot search by email domain name. + +| Qualifier | Пример | +| ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `user:name` | [**user:octocat**](https://github.com/search?q=user%3Aoctocat&type=Users) matches the user with the username "octocat". | +| `org:name` | [**org:electron type:users**](https://github.com/search?q=org%3Aelectron+type%3Ausers&type=Users) matches the Electron organization's account name. | +| `in:login` | [**kenya in:login**](https://github.com/search?q=kenya+in%3Alogin&type=Users) matches users with the word "kenya" in their username. | +| `in:name` | [**bolton in:name**](https://github.com/search?q=bolton+in%3Afullname&type=Users) matches users whose real name contains the word "bolton." | +| `fullname:firstname lastname` | [**fullname:nat friedman**](https://github.com/search?q=fullname%3Anat+friedman&type=Users) matches a user with the full name "Nat Friedman." Note: This search qualifier is sensitive to spacing. | +| `in:email` | [**data in:email**](https://github.com/search?q=data+in%3Aemail&type=Users&utf8=%E2%9C%93) matches users with the word "data" in their email. | + +## Search by number of repositories a user owns + +You can filter users based on the number of repositories they own, using the `repos` qualifier and [greater than, less than, and range qualifiers](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). + +| Qualifier | Пример | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| repos:n | [**repos:>9000**](https://github.com/search?q=repos%3A%3E%3D9000&type=Users) matches users whose repository count is over 9,000. | +| | [**bert repos:10..30**](https://github.com/search?q=bert+repos%3A10..30&type=Users) matches users with the word "bert" in their username or real name who own 10 to 30 repositories. | + +## Search by location + +You can search for users by the location indicated in their profile. + +| Qualifier | Пример | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| location:LOCATION | [**repos:1 location:iceland**](https://github.com/search?q=repos%3A1+location%3Aiceland&type=Users) matches users with exactly one repository that live in Iceland. | + +## Search by repository language + +Using the `language` qualifier you can search for users based on the languages of repositories they own. + +| Qualifier | Пример | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| language:LANGUAGE | [**language:javascript location:russia**](https://github.com/search?q=language%3Ajavascript+location%3Arussia&type=Users) matches users in Russia with a majority of their repositories written in JavaScript. | +| | [**jenny language:javascript in:fullname**](https://github.com/search?q=jenny+language%3Ajavascript+in%3Afullname&type=Users) matches users with JavaScript repositories whose full name contains the word "jenny." | + +## Search by when a user account was created + +You can filter users based on when they joined {% data variables.product.product_name %} with the `created` qualifier. This takes a date as its parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| Qualifier | Пример | +| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| created:YYYY-MM-DD | [**created:<2011-01-01**](https://github.com/search?q=created%3A%3C2011-01-01&type=Users) matches users that joined before 2011. | +| | [**created:>=2013-05-11**](https://github.com/search?q=created%3A%3E%3D2013-05-11&type=Users) matches users that joined at or after May 11th, 2013. | +| | [**created:2013-03-06 location:london**](https://github.com/search?q=created%3A2013-03-06+location%3Alondon&type=Users) matches users that joined on March 6th, 2013, who list their location as London. | +| | [**created:2010-01-01..2011-01-01 john in:login**](https://github.com/search?q=created%3A2010-01-01..2011-01-01+john+in%3Ausername&type=Users) matches users that joined between 2010 and 2011 with the word "john" in their username. | + +## Search by number of followers + +You can filter users based on the number of followers that they have, using the `followers` qualifier with [greater than, less than, and range qualifiers](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). + +| Qualifier | Пример | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| followers:n | [**followers:>=1000**](https://github.com/search?q=followers%3A%3E%3D1000&type=Users) matches users with 1,000 or more followers. | +| | [**sparkle followers:1..10**](https://github.com/search?q=sparkle+followers%3A1..10&type=Users) matches users with between 1 and 10 followers, with the word "sparkle" in their name. | + +{% ifversion fpt %} + +## Search based on ability to sponsor + +You can search for users and organizations who can be sponsored on {% data variables.product.prodname_sponsors %} with the `is:sponsorable` qualifier. For more information, see "[About {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)." + +| Qualifier | Пример | +| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `is:sponsorable` | [**is:sponsorable**](https://github.com/search?q=is%3Asponsorable&type=Users) matches users and organizations who have a {% data variables.product.prodname_sponsors %} profile. | + +{% endif %} + +## Дополнительная литература + +- "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" diff --git a/translations/ru-RU/content/search-github/searching-on-github/searching-wikis.md b/translations/ru-RU/content/search-github/searching-on-github/searching-wikis.md new file mode 100644 index 0000000000..4487bf2034 --- /dev/null +++ b/translations/ru-RU/content/search-github/searching-on-github/searching-wikis.md @@ -0,0 +1,51 @@ +--- +title: Searching wikis +intro: 'You can search wikis on {% data variables.product.product_name %} and narrow the results using these wiki search qualifiers in any combination.' +redirect_from: + - /articles/searching-wikis + - /github/searching-for-information-on-github/searching-wikis + - /github/searching-for-information-on-github/searching-on-github/searching-wikis +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +You can search wikis globally across all of {% data variables.product.product_name %}, or search wikis within a particular repository or organization. For more information, see "[About searching on {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)." + +{% data reusables.search.syntax_tips %} + +## Search within a user's or organization's repositories + +To find wiki pages from all repositories owned by a certain user or organization, use the `user` or `org` qualifier. To find wiki pages from a specific repository, use the `repo` qualifier. + +| Qualifier | Пример | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**user:defunkt**](https://github.com/search?q=user%3Adefunkt&type=Wikis) matches wiki pages from repositories owned by @defunkt. | +| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=Wikis&utf8=%E2%9C%93) matches wikis in repositories owned by the GitHub organization. | +| repo:USERNAME/REPOSITORY | [**repo:defunkt/gibberish**](https://github.com/search?q=user%3Adefunkt&type=Wikis) matches wiki pages from @defunkt's "gibberish" repository. | + +## Search within a wiki page title or body text + +The `in` qualifier limits the search to the wiki page title or body text. Without the qualifier, both the title and body text are searched. + +| Qualifier | Пример | +| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `in:title` | [**usage in:title**](https://github.com/search?q=usage+in%3Atitle&type=Wikis) matches wiki page titles with the word "usage." | +| `in:body` | [**installation in:body**](https://github.com/search?q=installation+in%3Abody&type=Wikis) matches wiki pages with the word "installation" in their main body text. | + +## Search by last updated date + +The `updated` qualifier matches wiki pages that were last updated within the specified date range. + +{% data reusables.search.date_gt_lt %} + +| Qualifier | Пример | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| updated:YYYY-MM-DD | [**usage updated:>2016-01-01**](https://github.com/search?q=usage+updated%3A>2016-01-01&type=Wikis) matches wiki pages with the word "usage" that were last updated after 2016-01-01. | + +## Дополнительная литература + +- "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results/)" diff --git a/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md b/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md index 058fafa671..9ad81d898c 100644 --- a/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md +++ b/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md @@ -30,6 +30,7 @@ shortTitle: Manage payment tiers 1. Optionally, to edit a draft tier, find the draft tier and click **Edit**. ![Edit button next to draft tier](/assets/images/help/sponsors/draft-tier-edit.png) {% data reusables.sponsors.click-add-tier %} {% data reusables.sponsors.tier-price-description %} +{% data reusables.sponsors.add-welcome-message %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} diff --git a/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md b/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md index 2a607157a7..d0c3fad1eb 100644 --- a/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md +++ b/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md @@ -51,6 +51,7 @@ To join {% data variables.product.prodname_sponsors %} as an individual contribu {% data reusables.sponsors.navigate-to-sponsor-tiers-tab %} {% data reusables.sponsors.click-add-tier %} {% data reusables.sponsors.tier-price-description %} +{% data reusables.sponsors.add-welcome-message %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} {% data reusables.sponsors.add-more-tiers %} diff --git a/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md b/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md index b2d9d81cf5..1dfe72626c 100644 --- a/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md +++ b/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md @@ -50,6 +50,7 @@ After {% data variables.product.prodname_dotcom %} reviews your application, you {% data reusables.sponsors.navigate-to-sponsor-tiers-tab %} {% data reusables.sponsors.click-add-tier %} {% data reusables.sponsors.tier-price-description %} +{% data reusables.sponsors.add-welcome-message %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} {% data reusables.sponsors.add-more-tiers %} diff --git a/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md b/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md index 65f9fbf09a..33063b5929 100644 --- a/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md +++ b/translations/ru-RU/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md @@ -37,6 +37,8 @@ The W-8 BEN and W-8 BEN-E tax forms ask for a "U.S. taxpayer identification numb If you are not a U.S. citizen or other U.S. person, including a resident alien individual, then you will usually need to provide the "Foreign tax identifying number". This is a tax identification number that your country of residence has issued you. +If your country of residence or billing country is India, then you can use your Permanent Account Number (PAN) as your tax identification number. + {% note %} **Note:** If your country does not require citizens to have a tax number issued by the government, then you can instead write "not legally required". @@ -56,6 +58,18 @@ If you are a taxpayer in the United States and earn more than 600 US dollars in {% data reusables.sponsors.sponsorships-not-tax-deductible %} +## Sales tax + +GitHub is providing information to assist you in calculating your sales tax obligations. This information is not personalized to your country or tax situation and we recommend you talk to a professional to understand your specific obligations. However, we'd like to provide some high-level information to help you understand the general principles of digital sales tax. + +In most countries around the world, sales tax for digital transactions is based on the location of the recipient, not on the seller. For example, if you are a maintainer in the United States and you provide a taxable benefit to a Sponsor in Germany, German sales tax would apply. + +Sales tax is generally only applicable when a good or service of value is being provided. Goodwill/general support/undying appreciation is not normally taxable. + +In the US, both B2B (business-to-business) and B2C (business-to-consumer) are subject to sales tax. + +In the EU and most other countries and regions, B2C sales are subject to sales tax. B2B sales are not subject to tax. C2C and C2B sales where a consumer is not registered for VAT are not taxable. + ## Дополнительная литература - [Viewing your sponsors and sponsorships](/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships) diff --git a/translations/ru-RU/data/glossaries/external.yml b/translations/ru-RU/data/glossaries/external.yml index fb61250848..dc717388e7 100644 --- a/translations/ru-RU/data/glossaries/external.yml +++ b/translations/ru-RU/data/glossaries/external.yml @@ -9,7 +9,7 @@ - term: токен восстановления учетной записи description: >- - Учетные данные для проверки подлинности, хранящиеся в настройках восстановления учетной записи и называемые «Восстановление учетной записи в любом месте», позволяют сохранять эту резервную копию учетных данных. + **Deprecated and will be disabled December 1st, 2021.** The authentication credential stored as part of an account recovery setup called Recover Accounts Elsewhere that allows you to store this backup credential. - term: предпросмотр API description: >- @@ -574,7 +574,7 @@ - term: Восстановление учетных записей в любом месте description: >- - Позволяет пользователям настроить дополнительный уровень безопасности своей учетной записи GitHub на случай утери данных для двухфакторной аутентификации или кодов восстановления доступа. Пользователи могут связать свою учетную запись GitHub со своей учетной записью Facebook, сохранив данные для аутентификации в виде токена восстановления учетной записи для своей учетной записи GitHub, связанной с Facebook. + **Deprecated and will be disabled December 1st, 2021.** Allows users to add an extra security factor to their GitHub account in case they lose access to their two-factor authentication method or recovery codes. Users can associate their GitHub account with their Facebook account by storing an authentication credential in the form of an account recovery token for their GitHub account with Facebook. - term: код восстановления description: Код для восстановления доступа к учетной записи GitHub пользователя. diff --git a/translations/ru-RU/data/learning-tracks/actions.yml b/translations/ru-RU/data/learning-tracks/actions.yml index cac5e08917..3e7bb1a877 100644 --- a/translations/ru-RU/data/learning-tracks/actions.yml +++ b/translations/ru-RU/data/learning-tracks/actions.yml @@ -7,6 +7,7 @@ getting_started: - /actions/learn-github-actions/finding-and-customizing-actions - /actions/learn-github-actions/essential-features-of-github-actions - /actions/learn-github-actions/managing-complex-workflows + - /actions/learn-github-actions/reusing-workflows - /actions/learn-github-actions/security-hardening-for-github-actions featured_track: true continuous_integration: diff --git a/translations/ru-RU/data/release-notes/enterprise-server/2-20/15.yml b/translations/ru-RU/data/release-notes/enterprise-server/2-20/15.yml index 205a9bed6a..eb611e3aa6 100644 Binary files a/translations/ru-RU/data/release-notes/enterprise-server/2-20/15.yml and b/translations/ru-RU/data/release-notes/enterprise-server/2-20/15.yml differ diff --git a/translations/ru-RU/data/release-notes/enterprise-server/2-21/6.yml b/translations/ru-RU/data/release-notes/enterprise-server/2-21/6.yml index 98976d4fa2..f51e7b415f 100644 Binary files a/translations/ru-RU/data/release-notes/enterprise-server/2-21/6.yml and b/translations/ru-RU/data/release-notes/enterprise-server/2-21/6.yml differ diff --git a/translations/ru-RU/data/release-notes/enterprise-server/2-22/22.yml b/translations/ru-RU/data/release-notes/enterprise-server/2-22/22.yml new file mode 100644 index 0000000000..0bc20acf57 --- /dev/null +++ b/translations/ru-RU/data/release-notes/enterprise-server/2-22/22.yml @@ -0,0 +1,15 @@ +--- +date: '2021-09-24' +sections: + security_fixes: + - '**HIGH:** A path traversal vulnerability was identified in {% data variables.product.prodname_ghe_server %} that could be exploited when building a {% data variables.product.prodname_pages %} site. User-controlled configuration options used by {% data variables.product.prodname_pages %} were not sufficiently restricted and made it possible to read files on the {% data variables.product.prodname_ghe_server %} instance. To exploit this vulnerability, an attacker would need 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.1.8 and was fixed in 3.1.8, 3.0.16, and 2.22.22. This is the result of an incomplete fix for CVE-2021-22867. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned CVE-2021-22868. {% comment %} https://github.com/github/pages/pull/3359, https://github.com/github/pages/pull/3357 {% endcomment %}' + bugs: + - 'The {% data variables.product.prodname_github_connect %} configuration of the source instance was always restored to new instances even when the `--config` option for `ghe-restore` was not used. This would lead to a conflict with the {% data variables.product.prodname_github_connect %} connection and license synchronization if both the source and destination instances were online at the same time. {% comment %} https://github.com/github/github/pull/192247, https://github.com/github/github/pull/191951, https://github.com/github/enterprise2/pull/26870, https://github.com/github/backup-utils/pull/770, https://github.com/github/connected-enterprise/issues/208 {% endcomment %}' + - 'Fixes {% data variables.product.prodname_pages %} builds so they take into account the NO_PROXY setting of the appliance. This is relevant to appliances configured with an HTTP proxy only. {% comment %} https://github.com/github/github/pull/192380 {% endcomment %}' + known_issues: + - On a freshly set up {% data variables.product.prodname_ghe_server %} without any users, an attacker could create the first admin user. + - Custom firewall rules are removed during the upgrade process. + - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. + - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters. + - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_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. diff --git a/translations/ru-RU/data/release-notes/enterprise-server/3-0/16.yml b/translations/ru-RU/data/release-notes/enterprise-server/3-0/16.yml new file mode 100644 index 0000000000..c40eac2c61 --- /dev/null +++ b/translations/ru-RU/data/release-notes/enterprise-server/3-0/16.yml @@ -0,0 +1,18 @@ +--- +date: '2021-09-24' +sections: + security_fixes: + - '**HIGH:** A path traversal vulnerability was identified in {% data variables.product.prodname_ghe_server %} that could be exploited when building a {% data variables.product.prodname_pages %} site. User-controlled configuration options used by {% data variables.product.prodname_pages %} were not sufficiently restricted and made it possible to read files on the {% data variables.product.prodname_ghe_server %} instance. To exploit this vulnerability, an attacker would need 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.1.8 and was fixed in 3.1.8, 3.0.16, and 2.22.22. This is the result of an incomplete fix for CVE-2021-22867. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned CVE-2021-22868. {% comment %} https://github.com/github/pages/pull/3360, https://github.com/github/pages/pull/3357 {% endcomment %}' + - '**MEDIUM:** An improper access control vulnerability in {% data variables.product.prodname_ghe_server %} allowed a workflow job to execute in a self-hosted runner group it should not have had access to. This affects customers using self-hosted runner groups for access control. A repository with access to one enterprise runner group could access all of the enterprise runner groups within the organization because of improper authentication checks during the request. This could cause code to be run unintentionally by the incorrect runner group. This vulnerability affected {% data variables.product.prodname_ghe_server %} versions from 3.0.0 to 3.0.15 and 3.1.0 to 3.1.7 and was fixed in 3.0.16 and 3.1.8 releases. It has been assigned CVE-2021-22869. {% comment %} https://github.com/github/enterprise2/pull/27003 {% endcomment %}' + bugs: + - 'Resque worker counts were displayed incorrectly during maintenance mode. {% comment %} https://github.com/github/enterprise2/pull/26898, https://github.com/github/enterprise2/pull/26883 {% endcomment %}' + - 'Allocated memcached memory could be zero in clustering mode. {% comment %} https://github.com/github/enterprise2/pull/26927, https://github.com/github/enterprise2/pull/26832 {% endcomment %}' + - 'Fixes {% data variables.product.prodname_pages %} builds so they take into account the NO_PROXY setting of the appliance. This is relevant to appliances configured with an HTTP proxy only. (update 2021-09-30) {% comment %} https://github.com/github/pages/pull/3360 {% endcomment %}' + known_issues: + - On a freshly set up {% data variables.product.prodname_ghe_server %} without any users, an attacker could create the first admin user. + - Custom firewall rules are removed during the upgrade process. + - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. + - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters. + - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results. + - 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/ru-RU/data/release-notes/enterprise-server/3-1/8.yml b/translations/ru-RU/data/release-notes/enterprise-server/3-1/8.yml new file mode 100644 index 0000000000..77ecdaab2d --- /dev/null +++ b/translations/ru-RU/data/release-notes/enterprise-server/3-1/8.yml @@ -0,0 +1,20 @@ +--- +date: '2021-09-24' +sections: + security_fixes: + - '**HIGH:** A path traversal vulnerability was identified in {% data variables.product.prodname_ghe_server %} that could be exploited when building a {% data variables.product.prodname_pages %} site. User-controlled configuration options used by {% data variables.product.prodname_pages %} were not sufficiently restricted and made it possible to read files on the {% data variables.product.prodname_ghe_server %} instance. To exploit this vulnerability, an attacker would need 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.1.8 and was fixed in 3.1.8, 3.0.16, and 2.22.22. This is the result of an incomplete fix for CVE-2021-22867. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned CVE-2021-22868. {% comment %} https://github.com/github/pages/pull/3361, https://github.com/github/pages/pull/3357 {% endcomment %}' + - '**MEDIUM:** An improper access control vulnerability in {% data variables.product.prodname_ghe_server %} allowed a workflow job to execute in a self-hosted runner group it should not have had access to. This affects customers using self-hosted runner groups for access control. A repository with access to one enterprise runner group could access all of the enterprise runner groups within the organization because of improper authentication checks during the request. This could cause code to be run unintentionally by the incorrect runner group. This vulnerability affected {% data variables.product.prodname_ghe_server %} versions from 3.0.0 to 3.0.15 and 3.1.0 to 3.1.7 and was fixed in 3.0.16 and 3.1.8 releases. It has been assigned CVE-2021-22869. {% comment %} https://github.com/github/enterprise2/pull/27013 {% endcomment %}' + bugs: + - 'Resque worker counts were displayed incorrectly during maintenance mode. {% comment %} https://github.com/github/enterprise2/pull/26899, https://github.com/github/enterprise2/pull/26883 {% endcomment %}' + - 'Allocated memcached memory could be zero in clustering mode. {% comment %} https://github.com/github/enterprise2/pull/26928, https://github.com/github/enterprise2/pull/26832 {% endcomment %}' + - 'Non-empty binary files displayed an incorrect file type and size on the pull request "Files" tab. {% comment %} https://github.com/github/github/pull/192810, https://github.com/github/github/pull/172284, https://github.com/github/coding/issues/694 {% endcomment %}' + - 'Fixes {% data variables.product.prodname_pages %} builds so they take into account the NO_PROXY setting of the appliance. This is relevant to appliances configured with an HTTP proxy only. (update 2021-09-30) {% comment %} https://github.com/github/pages/pull/3360 {% endcomment %}' + known_issues: + - The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues. + - On a freshly set up {% data variables.product.prodname_ghe_server %} without any users, an attacker could create the first admin user. + - Custom firewall rules are removed during the upgrade process. + - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository. + - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters. + - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results. + - If {% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_server %}, teardown of a replica node with `ghe-repl-teardown` will succeed, but may return `ERROR:Running migrations`. + - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. diff --git a/translations/ru-RU/data/release-notes/enterprise-server/3-2/0-rc1.yml b/translations/ru-RU/data/release-notes/enterprise-server/3-2/0-rc1.yml index aecf79ca82..1c45fac016 100644 --- a/translations/ru-RU/data/release-notes/enterprise-server/3-2/0-rc1.yml +++ b/translations/ru-RU/data/release-notes/enterprise-server/3-2/0-rc1.yml @@ -1,7 +1,7 @@ --- date: '2021-09-09' release_candidate: true -deprecated: false +deprecated: true intro: 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. sections: features: diff --git a/translations/ru-RU/data/release-notes/enterprise-server/3-2/0.yml b/translations/ru-RU/data/release-notes/enterprise-server/3-2/0.yml new file mode 100644 index 0000000000..890fb5c8ed --- /dev/null +++ b/translations/ru-RU/data/release-notes/enterprise-server/3-2/0.yml @@ -0,0 +1,221 @@ +--- +date: '2021-09-28' +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: Custom patterns for secret scanning + notes: + - | + {% data variables.product.prodname_GH_advanced_security %} customers can now specify custom patterns for secret scanning. When a new pattern is specified, secret scanning searches a repository's entire Git history for the pattern, as well as any new commits. + + User defined patterns are in beta for {% data variables.product.prodname_ghe_server %} 3.2. They can be defined at the repository, organization, and enterprise levels. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." + - + heading: Security overview for Advanced Security (beta) + notes: + - | + {% data variables.product.prodname_GH_advanced_security %} customers now have an organization-level view of the application security risks detected by {% data variables.product.prodname_code_scanning %}, {% data variables.product.prodname_dependabot %}, and {% data variables.product.prodname_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 {% data variables.product.prodname_secret_scanning %} alerts at the organization level. Similar views for {% data variables.product.prodname_dependabot %} and {% data variables.product.prodname_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 review (beta) + notes: + - | + {% data variables.product.prodname_GH_advanced_security %} customers can now see a rich diff of the dependencies changed in a pull request. 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 these dependencies. 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)." + - + heading: GitHub Actions environments + notes: + - | + Environments, environment protection rules, and environment secrets are now generally available for {% data variables.product.prodname_actions %} on {% data variables.product.product_name %}. For more information, see "[Environments](/actions/reference/environments)." + + ![Environment protection rules](/assets/images/enterprise/3.2/release-notes/actions-environments.png) + - + heading: SSH authentication with security keys + notes: + - | + SSH authentication using a FIDO2 security key is now supported when you add a `sk-ecdsa-sha2-nistp256@openssh.com` or `sk-ssh-ed25519@openssh.com` SSH key to your account. SSH security keys store secret key material on a separate hardware device that requires verification, such as a tap, to operate. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)." + - + heading: 'Dark and dark dimmed themes' + notes: + - | + Dark and dark dimmed themes are now available for the web UI. {% data variables.product.product_name %} will match your system preferences when you haven't set theme preferences in {% data variables.product.product_name %}. You can also choose which themes are active during the day and night. For more information, see "[Managing your theme settings](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)." + + ![Dark and dark dimmed themes](https://user-images.githubusercontent.com/33528647/114629560-d2231f80-9c86-11eb-9bde-cc301a97040d.gif) + - + heading: 'Approving unverified domains for email notifications' + notes: + - 'Domains that are not able to be verified can now be approved for email notification routing. Enterprise and organization owners will be able to approve domains and immediately augment their email notification restriction policy, allowing notifications to be sent to collaborators, consultants, acquisitions, or other partners. For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#about-approval-of-domains)" and "[Restricting email notifications for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise#restricting-email-notifications-for-your-enterprise-account)."' + - + heading: 'Git Credential Manager (GCM) secure credential storage and multi-factor authentication support' + notes: + - | + Git Credential Manager (GCM) Core versions 2.0.452 and later now provide security-hardened credential storage and multi-factor authentication support for {% data variables.product.product_name %}. + + GCM Core with support for {% data variables.product.product_name %} is included with [Git for Windows](https://gitforwindows.org) versions 2.32 and later. GCM Core is not included with Git for macOS or Linux, but can be installed separately. For more information, see the [latest release](https://github.com/microsoft/Git-Credential-Manager-Core/releases/) and [installation instructions](https://github.com/microsoft/Git-Credential-Manager-Core/releases/) in the `microsoft/Git-Credential-Manager-Core` repository. + changes: + - + heading: Administration Changes + notes: + - A 'User Agent Referrer Policy' setting has been added to the enterprise settings. This allows an admin to set a stricter `Referrer-Policy` to hide the hostname of a {% data variables.product.prodname_ghe_server %} installation from external sites. The setting is disabled by default and is tracked by audit log events for staff and enterprise owners when enabled or disabled. For more information, see "[Configuring Referrer Policy for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)." + - The MySQL health check was changed to use `mysqladmin ping` instead of TCP checks, which removes some unnecessary noise in the MySQL error log. Also, Orchestrator failover checks were improved to prevent unnecessary MySQL failovers when applying cluster config changes. + - 'The Resque service, which supports background job processing, has been replaced with Aqueduct Lite. This change makes the job system easier to manage and should not affect the user experience. For the new administration and debugging commands for Aqueduct, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-aqueduct)."' + - + heading: Token Changes + notes: + - | + The format of authentication tokens for {% data variables.product.product_name %} has changed. The change affects the format of personal access tokens and access tokens for {% data variables.product.prodname_oauth_apps %}, as well as user-to-server, server-to-server, and refresh tokens for {% data variables.product.prodname_github_apps %}. + + The different token types now have unique identifiable prefixes, which allows for secret scanning to detect the tokens so that you can mitigate the impact of someone accidentally committing a token to a repository. {% data variables.product.company_short %} recommends updating existing tokens as soon as possible. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github#githubs-token-formats)" and "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)." + - + heading: 'Repositories changes' + notes: + - Repositories on user profiles and organization profiles now support sorting by star count. + - When viewing the commit history of a single file, you can now click {% octicon "file-code" aria-label="The code icon" %} to view that file at the selected point in history. + - When a submodule is defined with a relative path in {% data variables.product.product_location %}, the submodule is now clickable in the web UI. Clicking the submodule in the web UI will take you to the linked repository. Previously, only submodules with absolute URLs were clickable. This is supported for relative paths for repositories with the same owner that follow the pattern ../REPOSITORY or relative paths for repositories with a different owner that follow the pattern ../OWNER/REPOSITORY. For more information about working with submodules, see [Working with submodules](https://github.blog/2016-02-01-working-with-submodules/) on {% data variables.product.prodname_blog %}. + - 'The web UI can now be used to synchronize an out-of-date branch of a fork with the fork''s upstream branch. If there are no merge conflicts between the branches, the branch is updated either by fast-forwarding or by merging from upstream. If there are conflicts, you will be prompted to create a pull request to resolve the conflicts. For more information, see "[Syncing a fork](/github/collaborating-with-pull-requests/working-with-forks/syncing-a-fork#syncing-a-fork-from-the-web-ui)."' + - + heading: 'Markdown changes' + notes: + - 'The markdown editor used when creating or editing a release in a repository now has a text-editing toolbar. For more information, see "[Managing releases in a repository](/github/administering-a-repository/releasing-projects-on-github/managing-releases-in-a-repository#creating-a-release)."' + - Uploading video files is now supported everywhere you write Markdown on {% data variables.product.product_name %}. Share demos, reproduction steps, and more in your issue and pull request comments, as well as in Markdown files within repositories, such as READMEs. For more information, see "[Attaching files](/github/writing-on-github/working-with-advanced-formatting/attaching-files)." + - Markdown files will now automatically generate a table of contents in the header when there are 2 or more headings. The table of contents is interactive and links to the selected section. All 6 Markdown heading levels are supported. + - 'There is a new keyboard shortcut, `cmd+e` on macOS or `ctrl+e` on Windows, to insert codeblocks in Markdown files, issues, pull requests, and comments.' + - 'Appending `?plain=1` to the URL for any Markdown file will now display the file without rendering and with line numbers. The plain view can be used to link other users to specific lines. For example, appending `?plain=1#L52` will highlight line 52 of a plain text Markdown file. For more information, "[Creating a permanent link to a code snippet](/github/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet#linking-to-markdown)."' + - + heading: 'Issues and pull requests changes' + notes: + - With the [latest version of Octicons](https://github.com/primer/octicons/releases), the states of issues and pull requests are now more visually distinct so you can scan their status more easily. For more information, see [{% data variables.product.prodname_blog %}](https://github.blog/changelog/2021-06-08-new-issue-and-pull-request-state-icons/). + - 'A new "Require conversation resolution before merging" branch protection rule and "Conversations" menu is now available. Easily discover your pull request comments from the "Files changed" tab, and require that all your pull request conversations are resolved before merging. For more information, see "[About pull request reviews](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews#discovering-and-navigating-conversations)" and "[About protected branches](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-conversation-resolution-before-merging)."' + - To prevent the merge of unexpected changes after auto-merge is enabled for a pull request, auto-merge is now disabled automatically when new changes are pushed by a user without write access to the repository. Users without write access can still update the pull request with changes from the base branch when auto-merge is enabled. To prevent a malicious user from using a merge conflict to introduce unexpected changes to the pull request, auto-merge for the pull request is disabled if the update causes a merge conflict. For more information about auto-merge, see "[Automatically merging a pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." + - 'People with maintain permissions 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 permissions 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. + - When a review is requested from a team of more than 100 people, developers are now shown a confirmation dialog box in order to prevent unnecessary notifications for large teams. + - Back-tick `code blocks` are now supported in issue titles, pull request titles, and in any place issue and pull request titles are referenced in {% data variables.product.prodname_ghe_server %}. + - 'Events for pull requests and pull request reviews are now included in the audit log for both [enterprises](/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise) and [organizations](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization). These events help admins better monitor pull request activity and help ensure security and compliance requirements are being met. Events can be viewed from the web UI, exported as CSV or JSON, or accessed via REST API. You can also search the audit log for specific pull request events. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#pull_request-category-actions)."' + - + heading: 'Branches changes' + notes: + - | + The default branch name for new repositories is now `main`. Existing repositories are not impacted by this change. If users, organization owners, or enterprise owners have previously specified a default branch for new repositories, they are also not impacted. + + If you want to set a different default branch name, you can do so in the [user](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories), [organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization), or [enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name) settings. + - | + Branches, including the default branch, can now be renamed using the the {% data variables.product.product_name %} web UI. When a branch is renamed, any open pull requests and draft releases targeting the renamed branch will be retargeted automatically, and branch protection rules that explicitly reference the renamed branch will be updated. + + Admin permissions are required to rename the default branch, but write permissions are sufficient to rename other branches. + + To help make the change as seamless as possible for users: + + * A notice is shown to contributors, maintainers, and admins on the repository homepage with instructions for updating their local repository. + * Web requests to the old branch will be redirected. + * A "moved permanently" HTTP response will be returned to REST API calls. + * An informational message is displayed to Git command line users that push to the old branch. + + For more information, see "[Renaming a branch](/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch)." + - + heading: 'GitHub Actions changes' + notes: + - '{% data variables.product.prodname_actions %} now lets you control the permissions granted to the `GITHUB_TOKEN` secret. The `GITHUB_TOKEN` is an automatically-generated secret that lets you make authenticated calls to the API for {% data variables.product.product_name %} in your workflow runs. {% data variables.product.prodname_actions %} generates a new token for each job and expires the token when a job completes. The token usually has `write` permissions to a number of [API endpoints](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token), except in the case of pull requests from forks, which are always `read`. These new settings allow you to follow a principle of least privilege in your workflows. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token)."' + - '{% data variables.product.prodname_cli %} 1.9 and later allows you to work with {% data variables.product.prodname_actions %} in your terminal. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-04-15-github-cli-1-9-enables-you-to-work-with-github-actions-from-your-terminal/).' + - 'The audit log now includes events associated with {% data variables.product.prodname_actions %} workflow runs. This data provides administrators with a greatly expanded data set for security and compliance audits. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#workflows-category-actions)."' + - '{% data variables.product.prodname_ghe_server %} 3.2 contains performance improvements for job concurrency with {% data variables.product.prodname_actions %}. For more information on the new performance targets on 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)."' + - + heading: 'GitHub Packages changes' + notes: + - Any package or package version for {% data variables.product.prodname_registry %} can now be deleted from {% data variables.product.product_name %}'s web UI. You can also undo the deletion of any package or package version within 30 days. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)". + - + heading: 'Dependabot and Dependency graph changes' + notes: + - 'The dependency graph can now be enabled using the Management Console, rather than needing to run a command in the administrative shell. For more information, see "[Enabling alerts for vulnerable dependencies {% data variables.product.prodname_ghe_server %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server#enabling-the-dependency-graph-and-dependabot-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."' + - Notifications for multiple {% data variables.product.prodname_dependabot_alerts %} are now grouped together if they're discovered at the same time. This significantly reduces the volume of {% data variables.product.prodname_dependabot %} alert notifications that users receive. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-03-18-grouped-dependabot-alert-notifications/). + - 'Dependency graph and {% data variables.product.prodname_dependabot_alerts %} now support Go modules. {% data variables.product.prodname_ghe_server %} analyzes a repository''s `go.mod` files to understand the repository’s dependencies. Along with security advisories, the dependency graph provides the information needed to alert developers to vulnerable dependencies. For more information about enabling the dependency graph on private repositories, see "[Securing your repository](/code-security/getting-started/securing-your-repository#managing-the-dependency-graph)."' + - The default notification settings for security alerts have changed. Previously, if you had permission to view security alerts in a repository, you would receive notifications for that repository as long as your settings allowed for security alert notifications. Now, you must opt in to security alert notifications by watching the repository. You will be notified if you select `All Activity` or configure `Custom` to include `Security alerts`. All existing repositories will be automatically migrated to these new settings and you will continue to receive notifications; however, any new repositories will require opting-in by watching the repository. 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)" and "[Managing alerts from secret scanning](/code-security/secret-security/managing-alerts-from-secret-scanning)." + - + heading: 'Code scanning and secret scanning changes' + notes: + - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} now generates diagnostic information for all supported languages. This helps check the state of the created database to understand the status and quality of performed analysis. The diagnostic information is available starting in [version 2.5.6](https://github.com/github/codeql-cli-binaries/releases) of the [{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/). You can see the detailed diagnostic information in the {% data variables.product.prodname_actions %} logs for {% data variables.product.prodname_codeql %}. For more information, see "[Viewing code scanning logs](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs)."' + - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql_cli %} now supports analyzing several languages during a single build. This makes it easier to run code analysis to use CI/CD systems other than {% data variables.product.prodname_actions %}. The new mode of the `codeql database create` command is available starting [version 2.5.6](https://github.com/github/codeql-cli-binaries/releases) of the [{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/). For more information about setting this up, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-cli-in-your-ci-system)."' + - '{% data variables.product.prodname_code_scanning_capc %} alerts from all enabled tools are now shown in one consolidated list, so that you can easily prioritize across all alerts. You can view alerts from a specific tool by using the "Tool" filter, and the "Rule" and "Tag" filters will dynamically update based on your "Tool" selection.' + - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} now includes beta support for analyzing C++20 code. This is only available when building codebases with GCC on Linux. C++20 modules are not supported yet.' + - 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 for several languages ([C++](https://github.com/github/codeql/tree/main/cpp), [JavaScript](https://github.com/github/codeql/tree/main/javascript), [Python](https://github.com/github/codeql/tree/main/python), and [Java](https://github.com/github/codeql/tree/main/java)). As a result, {% data variables.product.prodname_codeql %} can now detect even more potential sources of untrusted user data, review the steps through which that data flows, and identify potentially dangerous sinks in which this data could end up. This results in an overall improvement of the quality of the {% data variables.product.prodname_code_scanning %} alerts. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-07-01-codeql-code-scanning-now-recognizes-more-sources-and-uses-of-untrusted-user-data/). + - | + {% data variables.product.prodname_code_scanning_capc %} now shows `security-severity` levels for CodeQL security alerts. You can configure which `security-severity` levels will cause a check failure for a pull request. The severity level of security alerts can be `critical`, `high`, `medium`, or `low`. By default, any {% data variables.product.prodname_code_scanning %} alerts with a `security-severity` of `critical` or `high` will cause a pull request check failure. + + Additionally, you can now also configure which severity levels will cause a pull request check to fail for non-security alerts. You can configure this behavior at the repository level, and define whether alerts with the severity `error`, `warning`, or `note` will cause a pull request check to fail. By default, non-security {% data variables.product.prodname_code_scanning %} alerts with a severity of `error` will cause a pull request check failure. + + For more information see "[Defining which alert severity levels cause pull request check failure](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)." + + ![List of code scanning alerts with security levels](/assets/images/enterprise/3.2/release-notes/code-scanning-alerts.png) + - | + Improvements to the branch filter for {% data variables.product.prodname_code_scanning %} alerts make it clearer which {% data variables.product.prodname_code_scanning %} alerts are being displayed on the alerts page. By default, {% data variables.product.prodname_code_scanning %} alerts are filtered to show alerts for the default branch of the repository only. You can use the branch filter to display the alerts on any of the non-default branches. Any branch filter that has been applied is shown in the search bar. + + The search syntax has also been simplified to `branch:`. This syntax can be used multiple times in the search bar to filter on multiple branches. The previous syntax, `ref:refs/heads/`, is still supported, so any saved URLs will continue to work. + - | + Free text search is now available for code scanning alerts. You can search code scanning results to quickly find specific alerts without having to know exact search terms. The search is applied across the alert's name, description, and help text. The syntax is: + + - A single word returns all matches. + - Multiple search words returns matches to either word. + - Words in double quotes returns exact matches. + - The keyword 'AND' returns matches to multiple words. + - '{% data variables.product.prodname_secret_scanning_caps %} added patterns for 23 new service providers. For the updated list of supported secrets, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning)."' + - + heading: Изменения API + notes: + - 'Pagination support has been added to the Repositories REST API''s "compare two commits" endpoint, which returns a list of commits reachable from one commit or branch, but unreachable from another. The API can also now return the results for comparisons over 250 commits. For more information, see the "[Repositories](/rest/reference/repos#compare-two-commits)" REST API documentation and "[Traversing with pagination](/rest/guides/traversing-with-pagination)."' + - 'The REST API can now be used to programmatically resend or check the status of webhooks. For more information, see "[Repositories](/rest/reference/repos#webhooks)," "[Organizations](/rest/reference/orgs#webhooks)," and "[Apps](/rest/reference/apps#webhooks)" in the REST API documentation.' + - | + Improvements have been made to the code scanning and {% data variables.product.prodname_GH_advanced_security %} APIs: + + - The code scanning API now returns the CodeQL query version used for an analysis. This can be used to reproduce results or confirm that an analysis used the latest query. For more information, see "[Code scanning](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository)" in the REST API documentation. + - Admin users can now use the REST API to enable or disable {% data variables.product.prodname_GH_advanced_security %} for repositories, using the `security_and_analysis` object on `repos/{org}/{repo}`. In addition, admin users can check whether {% data variables.product.prodname_advanced_security %} is currently enabled for a repository by using a `GET /repos/{owner}/{repo}` request. These changes help you manage {% data variables.product.prodname_advanced_security %} repository access at scale. For more information, see "[Repositories](/rest/reference/repos#update-a-repository)" in the REST API documentation. + #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 %} 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. + deprecations: + - + heading: Deprecation of GitHub Enterprise Server 2.21 + notes: + - '**{% data variables.product.prodname_ghe_server %} 2.21 was discontinued on June 6, 2021**. That 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.2/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' + - + heading: Deprecation of GitHub Enterprise Server 2.22 + notes: + - '**{% data variables.product.prodname_ghe_server %} 2.22 will be discontinued on September 23, 2021**. That 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.2/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' + - + heading: Deprecation of XenServer Hypervisor support + notes: + - Beginning in {% data variables.product.prodname_ghe_server %} 3.1, we will begin discontinuing support for Xen Hypervisor. The complete deprecation is scheduled for {% data variables.product.prodname_ghe_server %} 3.3, following the standard one year deprecation window. Please contact [GitHub Support](https://enterprise.githubsupport.com/hc/en-us/signin) with questions or concerns. + - + heading: Removal of Legacy GitHub Services + notes: + - '{% data variables.product.prodname_ghe_server %} 3.2 removes unused GitHub Service database records. More information is available in the [deprecation announcement post](https://developer.github.com/changes/2018-04-25-github-services-deprecation/).' + - + heading: Deprecation of OAuth Application API endpoints and API authentication via query parameters + notes: + - | + To prevent accidental logging or exposure of `access_tokens`, we discourage the use of OAuth Application API endpoints and the use of API auth via query params. Visit the following posts to see the proposed replacements: + + * [Replacement OAuth Application API endpoints](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#changes-to-make) + * [Replacement auth via headers instead of query param](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make) + + These endpoints and auth route are planned to be removed from {% data variables.product.prodname_ghe_server %} in {% data variables.product.prodname_ghe_server %} 3.4. + - + heading: Removal of legacy GitHub App webhook events and endpoints + notes: + - | + Two legacy GitHub Apps-related webhook events have been removed: `integration_installation` and `integration_installation_repositories`. You should instead be listening to the `installation` and `installation_repositories` events. + - | + The following REST API endpoint has been removed: `POST /installations/{installation_id}/access_tokens`. You should instead be using the namespaced equivalent `POST /app/installations/{installation_id}/access_tokens`. + backups: + - '{% data variables.product.prodname_ghe_server %} 3.2 requires at least [GitHub Enterprise Backup Utilities 3.2.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/enterprise-server@3.2/admin/configuration/configuring-backups-on-your-appliance).' diff --git a/translations/ru-RU/data/reusables/actions/about-environments.md b/translations/ru-RU/data/reusables/actions/about-environments.md new file mode 100644 index 0000000000..ab9cfa899f --- /dev/null +++ b/translations/ru-RU/data/reusables/actions/about-environments.md @@ -0,0 +1 @@ +Environments are used to describe a general deployment target like `production`, `staging`, or `development`. When a {% data variables.product.prodname_actions %} workflow deploys to an environment, the environment is displayed on the main page of the repository. You can use environments to require approval for a job to proceed, restrict which branches can trigger a workflow, or limit access to secrets. For more information about creating environments, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/actions/actions-group-concurrency.md b/translations/ru-RU/data/reusables/actions/actions-group-concurrency.md index acd4fab5e5..85aece27b2 100644 --- a/translations/ru-RU/data/reusables/actions/actions-group-concurrency.md +++ b/translations/ru-RU/data/reusables/actions/actions-group-concurrency.md @@ -1,6 +1,6 @@ When a concurrent job or workflow is queued, if another job or workflow using the same concurrency group in the repository is in progress, the queued job or workflow will be `pending`. Any previously pending job or workflow in the concurrency group will be canceled. To also cancel any currently running job or workflow in the same concurrency group, specify `cancel-in-progress: true`. -### Examples: Using concurrency and the default behavior +## Examples: Using concurrency and the default behavior {% raw %} ```yaml @@ -14,7 +14,7 @@ concurrency: ci-${{ github.ref }} ``` {% endraw %} -### Example: Using concurrency to cancel any in-progress job or run +## Example: Using concurrency to cancel any in-progress job or run {% raw %} ```yaml diff --git a/translations/ru-RU/data/reusables/actions/ae-hosted-runners-beta.md b/translations/ru-RU/data/reusables/actions/ae-hosted-runners-beta.md new file mode 100644 index 0000000000..804f22a849 --- /dev/null +++ b/translations/ru-RU/data/reusables/actions/ae-hosted-runners-beta.md @@ -0,0 +1,7 @@ +{% ifversion ghae %} +{% note %} + +**Note:** {% data variables.actions.hosted_runner %}s are currently in beta and subject to change. + +{% endnote %} +{% endif %} diff --git a/translations/ru-RU/data/reusables/actions/ae-self-hosted-runners-notice.md b/translations/ru-RU/data/reusables/actions/ae-self-hosted-runners-notice.md index cceda715dd..0dec49e4f5 100644 --- a/translations/ru-RU/data/reusables/actions/ae-self-hosted-runners-notice.md +++ b/translations/ru-RU/data/reusables/actions/ae-self-hosted-runners-notice.md @@ -1,9 +1,19 @@ {% ifversion ghae %} + {% warning %} -** Warning:** Self-hosted runners are currently disabled for {% data variables.product.prodname_ghe_managed %}. This is because {% data variables.product.prodname_ghe_managed %} offers guarantees for security boundaries which are incompatible with how self-hosted runners work. However, if you do need to use self-hosted runners with {% data variables.product.prodname_ghe_managed %} and understand the security implications, you can contact {% data variables.product.prodname_dotcom %} support for a security exception that will enable self-hosted runners. +{% ifversion ghae-next %} + +**Warning:** Self-hosted runners are enabled by default for {% data variables.product.prodname_ghe_managed %}. Self-hosted runners are long-lived, and any compromise to the host machine could leak secrets or credentials or enable other attacks. If you'd like to disable self-hosted runners for your enterprise, you can contact {% data variables.product.prodname_dotcom %} support. For more information about the risks of using self-hosted runners, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/security-hardening-for-github-actions#potential-impact-of-a-compromised-runner)." + +{% elsif ghae %} + +**Warning:** Self-hosted runners are currently disabled for {% data variables.product.prodname_ghe_managed %}. This is because {% data variables.product.prodname_ghe_managed %} offers guarantees for security boundaries which are incompatible with how self-hosted runners work. However, if you do need to use self-hosted runners with {% data variables.product.prodname_ghe_managed %} and understand the security implications, you can contact {% data variables.product.prodname_dotcom %} support for a security exception that will enable self-hosted runners. If you don't need self-hosted runners, then you can use {% data variables.actions.hosted_runner %}s to run your workflows. For more information, see "[About {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/about-ae-hosted-runners)." -{% endwarning %} +{% endif %} + +{% endwarning %} + {% endif %} diff --git a/translations/ru-RU/data/reusables/actions/allow-specific-actions-intro.md b/translations/ru-RU/data/reusables/actions/allow-specific-actions-intro.md index ea63a6c71c..1d10b77986 100644 --- a/translations/ru-RU/data/reusables/actions/allow-specific-actions-intro.md +++ b/translations/ru-RU/data/reusables/actions/allow-specific-actions-intro.md @@ -1,7 +1,7 @@ When you choose **Allow select actions**, local actions are allowed, and there are additional options for allowing other specific actions: -- **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` organization. For more information, see the [`actions`](https://github.com/actions) and [`github`](https://github.com/github) organizations.{% ifversion fpt or ghes > 3.0 %} -- **Allow Marketplace actions by verified creators:** {% ifversion ghes > 3.0 %}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 > 3.0 or ghae-issue-5094 %} +- **Allow Marketplace actions by verified creators:** {% ifversion ghes > 3.0 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 specified actions:** You can restrict workflows to use actions in specific organizations and repositories. To restrict access to specific tags or commit SHAs of an action, use the same `/@` syntax used in the workflow to select the action. For example, `actions/javascript-action@v1.0.1` to select a tag or `actions/javascript-action@172239021f7ba04fe7327647b213799853a9eb89` to select a SHA. For more information, see "[Finding and customizing actions](/actions/learn-github-actions/finding-and-customizing-actions#using-release-management-for-your-custom-actions)." diff --git a/translations/ru-RU/data/reusables/actions/autoscaling-parameters.md b/translations/ru-RU/data/reusables/actions/autoscaling-parameters.md new file mode 100644 index 0000000000..d9c4342b29 --- /dev/null +++ b/translations/ru-RU/data/reusables/actions/autoscaling-parameters.md @@ -0,0 +1,3 @@ +- Optionally, autoscaling parameters for each pool. + - Minimum number of idle runners for the pool + - Active timeout: The number of minutes that a runner should remain active in the pool before the pool is reduced to the idle count diff --git a/translations/ru-RU/data/reusables/actions/cd-templates-actions.md b/translations/ru-RU/data/reusables/actions/cd-templates-actions.md new file mode 100644 index 0000000000..c6eeec90db --- /dev/null +++ b/translations/ru-RU/data/reusables/actions/cd-templates-actions.md @@ -0,0 +1,3 @@ +{% data variables.product.product_name %} offers CD workflow templates for several popular services, such as Azure Web App. To learn how to get started using a workflow template, see "[Using workflow templates](/actions/learn-github-actions/using-workflow-templates)" or [browse the full list of deployment workflow templates](https://github.com/actions/starter-workflows/tree/main/deployments). You can also check out our more detailed guides for specific deployment workflows, such as "[Deploying to Azure App Service](/actions/deployment/deploying-to-azure-app-service)." + +Many service providers also offer actions on {% data variables.product.prodname_marketplace %} for deploying to their service. For the full list, see [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?category=deployment&type=actions). \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/actions/delete-env-key.md b/translations/ru-RU/data/reusables/actions/delete-env-key.md new file mode 100644 index 0000000000..380ebe5653 --- /dev/null +++ b/translations/ru-RU/data/reusables/actions/delete-env-key.md @@ -0,0 +1 @@ +If you configured a deployment environment, change the value of `environment` to be the name of your environment. If you did not configure an environment{% ifversion fpt %} or if your workflow is in a private repository and you do not use {% data variables.product.prodname_ghe_cloud %}{% endif %}, delete the `environment` key. \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/actions/environment-deployment-event.md b/translations/ru-RU/data/reusables/actions/environment-deployment-event.md new file mode 100644 index 0000000000..1a014fbfc6 --- /dev/null +++ b/translations/ru-RU/data/reusables/actions/environment-deployment-event.md @@ -0,0 +1 @@ +When a workflow job that references an environment runs, it creates a deployment object with the `environment` property set to the name of your environment. As the workflow progresses, it also creates deployment status objects with the `environment` property set to the name of your environment, the `environment_url` property set to the URL for environment (if specified in the workflow), and the `state` property set to the status of the job. \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/actions/environment-example.md b/translations/ru-RU/data/reusables/actions/environment-example.md new file mode 100644 index 0000000000..95ed6bc816 --- /dev/null +++ b/translations/ru-RU/data/reusables/actions/environment-example.md @@ -0,0 +1,45 @@ +You can specify an environment for each job in your workflow. To do so, add a `jobs..environment` key followed by the name of the environment. + +For example, this workflow will use an environment called `production`. + +```yaml +name: Deployment + +on: + push: + branches: + - main + +jobs: + deployment: + runs-on: ubuntu-latest + environment: production + steps: + - name: deploy + # ...deployment-specific steps +``` + +When the above workflow runs, the `deployment` job will be subject to any rules configured for the `production` environment. For example, if the environment requires reviewers, the job will pause until one of the reviewers approves the job. + +You can also specify a URL for the environment. The specified URL will appear on the deployments page for the repository (accessed by clicking **Environments** on the home page of your repository) and in the visualization graph for the workflow run. If a pull request triggered the workflow, the URL is also displayed as a **View deployment** button in the pull request timeline. + +```yaml +name: Deployment + +on: + push: + branches: + - main + +jobs: + deployment: + runs-on: ubuntu-latest + environment: + name: production + url: https://github.com + steps: + - name: deploy + # ...deployment-specific steps +``` + +![Workflow graph with URL](/assets/images/help/images/deploy-graph.png) \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/actions/reusable-workflow-artifacts.md b/translations/ru-RU/data/reusables/actions/reusable-workflow-artifacts.md new file mode 100644 index 0000000000..4f5210333f --- /dev/null +++ b/translations/ru-RU/data/reusables/actions/reusable-workflow-artifacts.md @@ -0,0 +1,3 @@ +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +All actions and workflows called within a run have write access to that run's artifacts. +{% endif %} \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/actions/reusable-workflows.md b/translations/ru-RU/data/reusables/actions/reusable-workflows.md new file mode 100644 index 0000000000..377f69ce32 --- /dev/null +++ b/translations/ru-RU/data/reusables/actions/reusable-workflows.md @@ -0,0 +1,5 @@ +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## Reusing workflows + +You can call one workflow from within another workflow. This allows you to reuse workflows, avoiding duplication and making your workflows easier to maintain. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." +{% endif %} \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/actions/runner-name-description.md b/translations/ru-RU/data/reusables/actions/runner-name-description.md new file mode 100644 index 0000000000..c3955e46ec --- /dev/null +++ b/translations/ru-RU/data/reusables/actions/runner-name-description.md @@ -0,0 +1 @@ +The name of the runner executing the job. diff --git a/translations/ru-RU/data/reusables/actions/uses-keyword-example.md b/translations/ru-RU/data/reusables/actions/uses-keyword-example.md new file mode 100644 index 0000000000..fac21c8a9f --- /dev/null +++ b/translations/ru-RU/data/reusables/actions/uses-keyword-example.md @@ -0,0 +1,7 @@ +```yaml +jobs: + call-workflow-1: + uses: octo-org/this-repo/.github/workflows/workflow-1.yml@172239021f7ba04fe7327647b213799853a9eb89 + call-workflow-2: + uses: octo-org/another-repo/.github/workflows/workflow-2.yml@v1 +``` \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/actions/workflow-organization-templates.md b/translations/ru-RU/data/reusables/actions/workflow-organization-templates.md new file mode 100644 index 0000000000..3ea3e19383 --- /dev/null +++ b/translations/ru-RU/data/reusables/actions/workflow-organization-templates.md @@ -0,0 +1 @@ +Workflow templates allow everyone in your organization who has permission to create workflows to do so more quickly and easily. When you create a new workflow, you can choose a template and some or all of the work of writing the workflow will be done for you. You can use workflow templates as a starting place to build your custom workflow or use them as-is. This not only saves time, it promotes consistency and best practice across your organization. \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/actions/workflow-run-approve-public-fork.md b/translations/ru-RU/data/reusables/actions/workflow-run-approve-public-fork.md index 1eeb41311a..1873b96f85 100644 --- a/translations/ru-RU/data/reusables/actions/workflow-run-approve-public-fork.md +++ b/translations/ru-RU/data/reusables/actions/workflow-run-approve-public-fork.md @@ -1,3 +1,9 @@ Anyone can fork a public repository, and then submit a pull request that proposes changes to the repository's {% data variables.product.prodname_actions %} workflows. Although workflows from forks do not have access to sensitive data such as secrets, they can be an annoyance for maintainers if they are modified for abusive purposes. To help prevent this, workflows on pull requests to public repositories from some outside contributors will not run automatically, and might need to be approved first. By default, all first-time contributors require approval to run workflows. + +{% note %} + +**Note:** Workflows triggered by `pull_request_target` events are run in the context of the base branch. Since the base branch is considered trusted, workflows triggered by these events will always run, regardless of approval settings. + +{% endnote %} \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/apps/oauth-auth-vary-response.md b/translations/ru-RU/data/reusables/apps/oauth-auth-vary-response.md new file mode 100644 index 0000000000..b76fef614b --- /dev/null +++ b/translations/ru-RU/data/reusables/apps/oauth-auth-vary-response.md @@ -0,0 +1 @@ +You can also receive the response in different formats if you provide the format in the `Accept` header. For example, `Accept: application/json` or `Accept: application/xml`: diff --git a/translations/ru-RU/data/reusables/code-scanning/upload-sarif-alert-limit.md b/translations/ru-RU/data/reusables/code-scanning/upload-sarif-alert-limit.md index 23aafdc414..9e565ee275 100644 --- a/translations/ru-RU/data/reusables/code-scanning/upload-sarif-alert-limit.md +++ b/translations/ru-RU/data/reusables/code-scanning/upload-sarif-alert-limit.md @@ -1,5 +1,8 @@ {% note %} -**Note:** SARIF upload supports a maximum of {% ifversion ghae-next or fpt or ghes > 3.0 %}5000{% else %}1000{% endif %} results per upload. Any results over this limit are ignored. If a tool generates too many results, you should update the configuration to focus on results for the most important rules or queries. +**Замечания:** +- SARIF upload supports a maximum of {% ifversion ghae-next or fpt or ghes > 3.0 %}5000{% else %}1000{% endif %} results per upload. Any results over this limit are ignored. If a tool generates too many results, you should update the configuration to focus on results for the most important rules or queries. + + - For each upload, SARIF upload supports a maximum size of 10 MB for the `gzip`-compressed SARIF file. Any uploads over this limit will be rejected. If your SARIF file is too large because it contains too many results, you should update the configuration to focus on results for the most important rules or queries. {% endnote %} diff --git a/translations/ru-RU/data/reusables/codespaces/create-or-switch-branch.md b/translations/ru-RU/data/reusables/codespaces/create-or-switch-branch.md new file mode 100644 index 0000000000..caaf86c2d7 --- /dev/null +++ b/translations/ru-RU/data/reusables/codespaces/create-or-switch-branch.md @@ -0,0 +1,3 @@ +1. If the current branch is not shown in the status bar, at the bottom of your codespace, right-click the status bar and select **Source control**. +1. Click the branch name in the status bar. ![The branch in the status bar](/assets/images/help/codespaces/branch-in-status-bar.png) +1. In the drop-down, either click the branch you want to switch to, or enter the name for a new branch and click **Create new branch**. ![Choose from the branch menu](/assets/images/help/codespaces/create-new-branch.png) \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/codespaces/source-control-commit-changes.md b/translations/ru-RU/data/reusables/codespaces/source-control-commit-changes.md new file mode 100644 index 0000000000..19f38cca4a --- /dev/null +++ b/translations/ru-RU/data/reusables/codespaces/source-control-commit-changes.md @@ -0,0 +1,4 @@ +{% data reusables.codespaces.source-control-display-dark %} +1. To stage your changes, click **+** next to the file you've changed, or next to **Changes** if you've changed multiple files and you want to stage them all. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-stage.png) +1. Type a commit message describing the change you've made. ![Source control side bar with a commit message](/assets/images/help/codespaces/codespaces-commit-commit-message.png) +1. To commit your staged changes, click the check mark at the top the source control side bar. ![Click the check mark icon](/assets/images/help/codespaces/codespaces-commit-checkmark-icon.png) \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/codespaces/source-control-pull-request.md b/translations/ru-RU/data/reusables/codespaces/source-control-pull-request.md new file mode 100644 index 0000000000..803f8981b6 --- /dev/null +++ b/translations/ru-RU/data/reusables/codespaces/source-control-pull-request.md @@ -0,0 +1,3 @@ +1. After you've committed changes to your local copy of the repository, click the **Create Pull Request** icon. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-pr-button.png) +1. Check that the local branch and repository you're merging from, and the remote branch and repository you're merging into, are correct. Then give the pull request a title and a description. ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-pr.png) +1. Click **Create**. \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/dependabot/supported-package-managers.md b/translations/ru-RU/data/reusables/dependabot/supported-package-managers.md index 486e05c72b..eaa4501350 100644 --- a/translations/ru-RU/data/reusables/dependabot/supported-package-managers.md +++ b/translations/ru-RU/data/reusables/dependabot/supported-package-managers.md @@ -26,7 +26,7 @@ The following table shows, for each package manager: | Terraform | `terraform` | >= 0.13, <= 1.0 | **✓** | **✓** | | | yarn | `npm` | v1 | **✓** | **✓** | | -[1] {% data variables.product.prodname_dependabot %} doesn't run Gradle but supports updates to the following files: `build.gradle` and `build.gradle.kts` (for Kotlin projects). +[1] {% data variables.product.prodname_dependabot %} doesn't run Gradle but supports updates to the following files: `build.gradle`, `build.gradle.kts` (for Kotlin projects), and files included via the `apply` declaration that have `dependencies` in the filename. Note that `apply` does not support `apply to`, recursion, or advanced syntaxes (for example, Kotlin's `apply` with `mapOf`, filenames defined by property). [2] {% data variables.product.prodname_dependabot %} doesn't run Maven but supports updates to `pom.xml` files. diff --git a/translations/ru-RU/data/reusables/dependency-review/beta.md b/translations/ru-RU/data/reusables/dependency-review/beta.md index d8f7089def..3ca1720c35 100644 --- a/translations/ru-RU/data/reusables/dependency-review/beta.md +++ b/translations/ru-RU/data/reusables/dependency-review/beta.md @@ -1,7 +1,8 @@ -{% ifversion fpt or ghes > 3.1 %} +{% ifversion ghes > 3.1 %} {% note %} **Note:** Dependency review is currently in beta and subject to change. {% endnote %} + {% endif %} \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/developer-site/pull_request_forked_repos_link.md b/translations/ru-RU/data/reusables/developer-site/pull_request_forked_repos_link.md index a46c58ce61..b871adff69 100644 --- a/translations/ru-RU/data/reusables/developer-site/pull_request_forked_repos_link.md +++ b/translations/ru-RU/data/reusables/developer-site/pull_request_forked_repos_link.md @@ -1,4 +1,4 @@ -#### Pull request events for forked repositories +### Pull request events for forked repositories {% note %} diff --git a/translations/ru-RU/data/reusables/dotcom_billing/pricing_cal.md b/translations/ru-RU/data/reusables/dotcom_billing/pricing_cal.md new file mode 100644 index 0000000000..6509379b28 --- /dev/null +++ b/translations/ru-RU/data/reusables/dotcom_billing/pricing_cal.md @@ -0,0 +1 @@ +To estimate the costs for consumptive services, you can use the {% data variables.product.prodname_dotcom %} pricing calculator. For more information, go to https://github.com/pricing/calculator. diff --git a/translations/ru-RU/data/reusables/enterprise-accounts/about-enterprise-accounts.md b/translations/ru-RU/data/reusables/enterprise-accounts/about-enterprise-accounts.md index 0ca23e37cf..e6c9ae6b28 100644 --- a/translations/ru-RU/data/reusables/enterprise-accounts/about-enterprise-accounts.md +++ b/translations/ru-RU/data/reusables/enterprise-accounts/about-enterprise-accounts.md @@ -14,7 +14,7 @@ Organizations are shared accounts where enterprise members can collaborate acros {% ifversion fpt %} -Enterprise owners can create organizations and link the organizations to the enterprise. After you add organizations to your enterprise account, you can manage and enforce policies for the organizations. Specific enforcement options vary by setting; generally, you can choose to enforce a single policy for every organization in your enterprise account or allow owners to set policy on the organization level. For more information, see "[Setting policies for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account)." +Enterprise owners can create organizations and link the organizations to the enterprise. Alternatively, you can invite an existing organization to join your enterprise. After you add organizations to your enterprise account, you can manage and enforce policies for the organizations. Specific enforcement options vary by setting; generally, you can choose to enforce a single policy for every organization in your enterprise account or allow owners to set policy on the organization level. For more information, see "[Setting policies for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account)." {% elsif ghes or ghae %} @@ -58,6 +58,14 @@ For more information about the differences between {% data variables.product.pro {% endif %} +{% ifversion fpt %} + +## About {% data variables.product.prodname_emus %} + +{% data reusables.enterprise-accounts.emu-short-summary %} + +{% endif %} + ## About billing for your enterprise account The bill for your enterprise account includes the monthly cost for each member of your enterprise. The bill includes {% ifversion fpt %}any paid licenses in organizations outside of your enterprise account, subscriptions to apps in {% data variables.product.prodname_marketplace %}, {% endif %}{% ifversion fpt or ghae %}additional paid services for your enterprise{% ifversion fpt %} like data packs for {% data variables.large_files.product_name_long %},{% endif %} and{% endif %} usage for {% data variables.product.prodname_GH_advanced_security %}. diff --git a/translations/ru-RU/data/reusables/enterprise-accounts/access-enterprise.md b/translations/ru-RU/data/reusables/enterprise-accounts/access-enterprise.md index a47a055301..19b6004028 100644 --- a/translations/ru-RU/data/reusables/enterprise-accounts/access-enterprise.md +++ b/translations/ru-RU/data/reusables/enterprise-accounts/access-enterprise.md @@ -5,5 +5,4 @@ {% elsif ghes or ghae %}1. In the top-right corner of {% data variables.product.product_name %}, click your profile photo, then click **Enterprise settings**. !["Enterprise settings" in drop-down menu for profile photo on {% data variables.product.product_name %}](/assets/images/enterprise/settings/enterprise-settings.png) - {% endif %} diff --git a/translations/ru-RU/data/reusables/enterprise-accounts/actions-runners-tab.md b/translations/ru-RU/data/reusables/enterprise-accounts/actions-runners-tab.md index 19b2de94c1..b6dc023362 100644 --- a/translations/ru-RU/data/reusables/enterprise-accounts/actions-runners-tab.md +++ b/translations/ru-RU/data/reusables/enterprise-accounts/actions-runners-tab.md @@ -1 +1 @@ -1. Click the {% ifversion fpt %}**Runners**{% else %}**Self-hosted runners**{% endif %} tab. +1. Click the {% ifversion fpt or ghes > 3.1 or ghae-next %}**Runners**{% else %}**Self-hosted runners**{% endif %} tab. diff --git a/translations/ru-RU/data/reusables/enterprise-accounts/emu-forks.md b/translations/ru-RU/data/reusables/enterprise-accounts/emu-forks.md new file mode 100644 index 0000000000..315ee2736f --- /dev/null +++ b/translations/ru-RU/data/reusables/enterprise-accounts/emu-forks.md @@ -0,0 +1 @@ +{% data variables.product.prodname_managed_users_caps %} cannot fork repositories from outside of the enterprise or fork internal repositories. {% data variables.product.prodname_managed_users_caps %} can fork private repositories owned by organizations in the enterprise into other organizations owned by the enterprise, or as a fork owned by the {% data variables.product.prodname_managed_user %}. \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/enterprise-accounts/emu-more-info-account.md b/translations/ru-RU/data/reusables/enterprise-accounts/emu-more-info-account.md new file mode 100644 index 0000000000..21302799fb --- /dev/null +++ b/translations/ru-RU/data/reusables/enterprise-accounts/emu-more-info-account.md @@ -0,0 +1 @@ +For more information, see "[Types of GitHub accounts](/get-started/learning-about-github/types-of-github-accounts#enterprise-managed-users)." \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/enterprise-accounts/emu-password-reset-session.md b/translations/ru-RU/data/reusables/enterprise-accounts/emu-password-reset-session.md new file mode 100644 index 0000000000..65ed74cc65 --- /dev/null +++ b/translations/ru-RU/data/reusables/enterprise-accounts/emu-password-reset-session.md @@ -0,0 +1 @@ +If you need to reset the password for your setup user, use an incognito or private browsing window to request a new password. When the email arrives with the link to reset your password, copy the link into your browser. For more information on resetting your password, see "[Requesting a new password ](/github/authenticating-to-github/keeping-your-account-and-data-secure/updating-your-github-access-credentials#requesting-a-new-password)." \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/enterprise-accounts/emu-permission-follow.md b/translations/ru-RU/data/reusables/enterprise-accounts/emu-permission-follow.md new file mode 100644 index 0000000000..f166721634 --- /dev/null +++ b/translations/ru-RU/data/reusables/enterprise-accounts/emu-permission-follow.md @@ -0,0 +1 @@ +{% ifversion fpt %} Members of an {% data variables.product.prodname_emu_enterprise %} can only follow other members of their enterprise. {% endif %} \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/enterprise-accounts/emu-permission-fork.md b/translations/ru-RU/data/reusables/enterprise-accounts/emu-permission-fork.md new file mode 100644 index 0000000000..411dfeed7b --- /dev/null +++ b/translations/ru-RU/data/reusables/enterprise-accounts/emu-permission-fork.md @@ -0,0 +1 @@ +{% ifversion fpt %}Members of an {% data variables.product.prodname_emu_enterprise %} cannot fork repositories from outside of the enterprise or fork internal repositories.{% endif %} \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/enterprise-accounts/emu-permission-gist.md b/translations/ru-RU/data/reusables/enterprise-accounts/emu-permission-gist.md new file mode 100644 index 0000000000..3164ea3434 --- /dev/null +++ b/translations/ru-RU/data/reusables/enterprise-accounts/emu-permission-gist.md @@ -0,0 +1 @@ +{% ifversion fpt %}Members of an {% data variables.product.prodname_emu_enterprise %} cannot create gists and have read-only access to gists.{% endif %} \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/enterprise-accounts/emu-permission-interact.md b/translations/ru-RU/data/reusables/enterprise-accounts/emu-permission-interact.md new file mode 100644 index 0000000000..9bdeac19e8 --- /dev/null +++ b/translations/ru-RU/data/reusables/enterprise-accounts/emu-permission-interact.md @@ -0,0 +1 @@ +{% ifversion fpt %} Members of an {% data variables.product.prodname_emu_enterprise %} can only interact with repositories within their enterprise. {% endif %} \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/enterprise-accounts/emu-permission-propose.md b/translations/ru-RU/data/reusables/enterprise-accounts/emu-permission-propose.md new file mode 100644 index 0000000000..85fd4f66e3 --- /dev/null +++ b/translations/ru-RU/data/reusables/enterprise-accounts/emu-permission-propose.md @@ -0,0 +1 @@ +{% ifversion fpt %} Members of an {% data variables.product.prodname_emu_enterprise %} can only propose changes in repositories that are part of their enterprise. {% endif %} diff --git a/translations/ru-RU/data/reusables/enterprise-accounts/emu-permission-repo.md b/translations/ru-RU/data/reusables/enterprise-accounts/emu-permission-repo.md new file mode 100644 index 0000000000..b4278362a5 --- /dev/null +++ b/translations/ru-RU/data/reusables/enterprise-accounts/emu-permission-repo.md @@ -0,0 +1 @@ +{% ifversion fpt %} Members of an {% data variables.product.prodname_emu_enterprise %} can only make changes in repositories that are part of their enterprise. {% endif %} diff --git a/translations/ru-RU/data/reusables/enterprise-accounts/emu-saml-note.md b/translations/ru-RU/data/reusables/enterprise-accounts/emu-saml-note.md new file mode 100644 index 0000000000..2a5bdae038 --- /dev/null +++ b/translations/ru-RU/data/reusables/enterprise-accounts/emu-saml-note.md @@ -0,0 +1,7 @@ +{% ifversion fpt%} +{% note %} + +**Note**: If your enterprise uses {% data variables.product.prodname_emus %}, you must follow a different process to configure SAML single sign-on. For more information, see "[Configuring SAML single sign-on for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." + +{% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/enterprise-accounts/emu-scim-note.md b/translations/ru-RU/data/reusables/enterprise-accounts/emu-scim-note.md new file mode 100644 index 0000000000..309ec9adfb --- /dev/null +++ b/translations/ru-RU/data/reusables/enterprise-accounts/emu-scim-note.md @@ -0,0 +1,7 @@ +{% ifversion fpt%} +{% note %} + +**Note**: If your enterprise uses {% data variables.product.prodname_emus %}, you cannot use team synchronization and must instead configure SCIM to manage membership with your identity provider. For more information, see "[Configuring SCIM provisioning for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users)." + +{% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/enterprise-accounts/emu-short-summary.md b/translations/ru-RU/data/reusables/enterprise-accounts/emu-short-summary.md new file mode 100644 index 0000000000..7e4f69fff9 --- /dev/null +++ b/translations/ru-RU/data/reusables/enterprise-accounts/emu-short-summary.md @@ -0,0 +1 @@ +{% data variables.product.prodname_emus %} is a feature of {% data variables.product.prodname_ghe_cloud %} that provides even greater control over enterprise members and resources. With {% data variables.product.prodname_emus %}, all members are provisioned and managed through your identity provider (IdP) instead of users creating their own accounts on {% data variables.product.product_name %}. Team membership can be managed using groups on your IdP. {% data variables.product.prodname_managed_users_caps %} are restricted to their enterprise and are unable to push code, collaborate, or interact with users, repositories, and organizations outside of their enterprise. For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/enterprise-accounts/emu-shortcode.md b/translations/ru-RU/data/reusables/enterprise-accounts/emu-shortcode.md new file mode 100644 index 0000000000..ec695c807d --- /dev/null +++ b/translations/ru-RU/data/reusables/enterprise-accounts/emu-shortcode.md @@ -0,0 +1 @@ +The short code must be unique to your enterprise, a three-to-eight character alphanumeric string, and contain no special characters. \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/enterprise-accounts/emu-supported-idps.md b/translations/ru-RU/data/reusables/enterprise-accounts/emu-supported-idps.md new file mode 100644 index 0000000000..375040efa3 --- /dev/null +++ b/translations/ru-RU/data/reusables/enterprise-accounts/emu-supported-idps.md @@ -0,0 +1,2 @@ +* Azure Active Directory (Azure AD) +* Okta \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/enterprise-accounts/github-connect-tab.md b/translations/ru-RU/data/reusables/enterprise-accounts/github-connect-tab.md index fa8d262206..abb45a109b 100644 --- a/translations/ru-RU/data/reusables/enterprise-accounts/github-connect-tab.md +++ b/translations/ru-RU/data/reusables/enterprise-accounts/github-connect-tab.md @@ -1,3 +1,3 @@ {% ifversion ghes < 3.1 %} 1. In the left sidebar, click **{% data variables.product.prodname_github_connect %}**. ![GitHub Connect tab in the business account settings sidebar](/assets/images/enterprise/business-accounts/settings-github-connect-tab.png){% else %} -1. In the enterprise account sidebar, click {% octicon "plug" aria-label="The GitHub Connect gear" %} **{% data variables.product.prodname_github_connect %}**. ![GitHub Connect tab in the enterprise account sidebar](/assets/images/help//business-accounts/enterprise-account-github-connect-tab.png){% endif %} \ No newline at end of file +1. In the enterprise account sidebar, click {% octicon "plug" aria-label="The GitHub Connect gear" %} **{% data variables.product.prodname_github_connect %}**. ![GitHub Connect tab in the enterprise account sidebar](/assets/images/help//business-accounts/enterprise-account-github-connect-tab.png){% endif %} diff --git a/translations/ru-RU/data/reusables/enterprise-accounts/identity-provider-tab.md b/translations/ru-RU/data/reusables/enterprise-accounts/identity-provider-tab.md new file mode 100644 index 0000000000..9e94eecb59 --- /dev/null +++ b/translations/ru-RU/data/reusables/enterprise-accounts/identity-provider-tab.md @@ -0,0 +1 @@ +1. Under your business account's name, click {% octicon "key" aria-label="The key icon" %} **Identity provider**. !["Identity provider" tab in enterprise sidebar](/assets/images/help/enterprises/enterprise-account-identity-provider-tab.png) \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/enterprise-accounts/invite-organization.md b/translations/ru-RU/data/reusables/enterprise-accounts/invite-organization.md new file mode 100644 index 0000000000..1d5c99c11e --- /dev/null +++ b/translations/ru-RU/data/reusables/enterprise-accounts/invite-organization.md @@ -0,0 +1 @@ +Enterprise account owners and administrators can invite existing organization accounts to join their enterprise. For more information, see "[Inviting an organization to join your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account#inviting-an-organization-to-join-your-enterprise-account)" diff --git a/translations/ru-RU/data/reusables/enterprise-accounts/team-sync-override.md b/translations/ru-RU/data/reusables/enterprise-accounts/team-sync-override.md new file mode 100644 index 0000000000..a39283eed0 --- /dev/null +++ b/translations/ru-RU/data/reusables/enterprise-accounts/team-sync-override.md @@ -0,0 +1 @@ +If your organization is owned by an enterprise account, enabling team synchronization or SCIM provisioning for the enterprise account will override your organization-level team synchronization settings. For more information, see "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)" and "[Configuring SCIM provisioning for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users)." \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/enterprise_clustering/proxy_protocol_ports.md b/translations/ru-RU/data/reusables/enterprise_clustering/proxy_protocol_ports.md index 17d24f3f00..c0cc4f655f 100644 --- a/translations/ru-RU/data/reusables/enterprise_clustering/proxy_protocol_ports.md +++ b/translations/ru-RU/data/reusables/enterprise_clustering/proxy_protocol_ports.md @@ -1,4 +1,4 @@ -#### PROXY protocol TCP port mappings +### PROXY protocol TCP port mappings | Source port | Destination port | Service description | |:-----------:|:----------------:|:------------------------:| diff --git a/translations/ru-RU/data/reusables/enterprise_clustering/without_proxy_protocol_ports.md b/translations/ru-RU/data/reusables/enterprise_clustering/without_proxy_protocol_ports.md index f8570c7cfe..2c13369f10 100644 --- a/translations/ru-RU/data/reusables/enterprise_clustering/without_proxy_protocol_ports.md +++ b/translations/ru-RU/data/reusables/enterprise_clustering/without_proxy_protocol_ports.md @@ -1,4 +1,4 @@ -#### Protocol TCP port mappings for use without PROXY support +### Protocol TCP port mappings for use without PROXY support | Source port | Destination port | Service description | |:-----------:|:----------------:|:------------------------:| diff --git a/translations/ru-RU/data/reusables/gated-features/emus.md b/translations/ru-RU/data/reusables/gated-features/emus.md new file mode 100644 index 0000000000..f9f25095ea --- /dev/null +++ b/translations/ru-RU/data/reusables/gated-features/emus.md @@ -0,0 +1 @@ +To manage users in your enterprise with your identity provider, your enterprise must be enabled for {% data variables.product.prodname_emus %}, which are available with {% data variables.product.prodname_ghe_cloud %}. For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/getting-started/enterprise-advanced-security.md b/translations/ru-RU/data/reusables/getting-started/enterprise-advanced-security.md new file mode 100644 index 0000000000..faffbe7d63 --- /dev/null +++ b/translations/ru-RU/data/reusables/getting-started/enterprise-advanced-security.md @@ -0,0 +1 @@ +If you have a GitHub Advanced Security license for your enterprise account, you can enforce policies to manage {% data variables.product.prodname_dotcom %} Advanced Security features for organizations owned by an enterprise account. For more information, see "[Enforcing policies for Advanced Security in your enterprise account](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-policies-for-advanced-security-in-your-enterprise-account)." \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/github-actions/actions-on-examples.md b/translations/ru-RU/data/reusables/github-actions/actions-on-examples.md index 7b672ef593..bb945b991c 100644 --- a/translations/ru-RU/data/reusables/github-actions/actions-on-examples.md +++ b/translations/ru-RU/data/reusables/github-actions/actions-on-examples.md @@ -1,18 +1,18 @@ -### Example: Using a single event +## Example: Using a single event ```yaml # Triggered when code is pushed to any branch in a repository on: push ``` -### Example: Using a list of events +## Example: Using a list of events ```yaml # Triggers the workflow on push or pull request events on: [push, pull_request] ``` -### Example: Using multiple events with activity types or configuration +## Example: Using multiple events with activity types or configuration If you need to specify activity types or configuration for an event, you must configure each event separately. You must append a colon (`:`) to all events, including events without configuration. diff --git a/translations/ru-RU/data/reusables/github-actions/disabling-github-actions.md b/translations/ru-RU/data/reusables/github-actions/disabling-github-actions.md index ae73419a8d..afe8ee7f1f 100644 --- a/translations/ru-RU/data/reusables/github-actions/disabling-github-actions.md +++ b/translations/ru-RU/data/reusables/github-actions/disabling-github-actions.md @@ -1 +1 @@ -By default, {% ifversion ghes or ghae %}after {% data variables.product.prodname_actions %} is enabled on {% data variables.product.product_location %}, it{% elsif fpt %}{% data variables.product.prodname_actions %}{% endif %} is enabled on all repositories and organizations. You can choose to disable {% data variables.product.prodname_actions %} or limit them to private actions only, which means that people can only use actions that exist in your repository. +By default, {% ifversion ghes or ghae %}after {% data variables.product.prodname_actions %} is enabled on {% data variables.product.product_location %}, it{% elsif fpt %}{% data variables.product.prodname_actions %}{% endif %} is enabled on all repositories and organizations. You can choose to disable {% data variables.product.prodname_actions %} or limit them to local actions only, which means that people can only use actions that exist in your repository. diff --git a/translations/ru-RU/data/reusables/github-actions/name-environment.md b/translations/ru-RU/data/reusables/github-actions/name-environment.md new file mode 100644 index 0000000000..f6fd5c69d4 --- /dev/null +++ b/translations/ru-RU/data/reusables/github-actions/name-environment.md @@ -0,0 +1 @@ +1. Enter a name for the environment, then click **Configure environment**. Environment names are not case sensitive. An environment name may not exceed 255 characters and must be unique within the repository. diff --git a/translations/ru-RU/data/reusables/github-actions/new-environment.md b/translations/ru-RU/data/reusables/github-actions/new-environment.md new file mode 100644 index 0000000000..879f2bf20a --- /dev/null +++ b/translations/ru-RU/data/reusables/github-actions/new-environment.md @@ -0,0 +1 @@ +1. Click **New environment**. diff --git a/translations/ru-RU/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md b/translations/ru-RU/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md index de019ae39c..2dbd7be129 100644 --- a/translations/ru-RU/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md +++ b/translations/ru-RU/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md @@ -1,6 +1,7 @@ -1. In the {% ifversion fpt %}"Runners"{% else %}"Self-hosted runners"{% endif %} section of the settings page, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} next to the runner group you'd like to configure, then click **Edit name and [organization|repository] access**. ![Manage repository permissions](/assets/images/help/settings/actions-runner-manage-permissions.png) +1. In the {% ifversion fpt or ghes > 3.1 or ghae-next %}"Runners"{% else %}"Self-hosted runners"{% endif %} section of the settings page, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} next to the runner group you'd like to configure, then click **Edit name and [organization|repository] access**. ![Manage repository permissions](/assets/images/help/settings/actions-runner-manage-permissions.png) 1. Modify your policy options, or change the runner group name. + {% ifversion not ghae %} {% warning %} **Предупреждение** @@ -10,3 +11,4 @@ For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)." {% endwarning %} + {% endif %} diff --git a/translations/ru-RU/data/reusables/github-actions/self-hosted-runner-list.md b/translations/ru-RU/data/reusables/github-actions/self-hosted-runner-list.md index 6edf2cb3f9..f6cb3732b1 100644 --- a/translations/ru-RU/data/reusables/github-actions/self-hosted-runner-list.md +++ b/translations/ru-RU/data/reusables/github-actions/self-hosted-runner-list.md @@ -1 +1 @@ - 1. Locate the list of runners under {% ifversion fpt %}"Runners"{% else %}"Self-hosted runners"{% endif %}. + 1. Locate the list of runners under {% ifversion fpt or ghes > 3.1 or ghae-next %}"Runners"{% else %}"Self-hosted runners"{% endif %}. diff --git a/translations/ru-RU/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md b/translations/ru-RU/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md index a8f6c616fb..eee56b2885 100644 --- a/translations/ru-RU/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md +++ b/translations/ru-RU/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md @@ -6,5 +6,5 @@ 1. In the left sidebar, click **Enterprise overview**. 1. {% endif %} In the enterprise sidebar, {% octicon "law" aria-label="The law icon" %} **Policies**. 1. Navigate to the {% data variables.product.prodname_actions %} settings: - * **In an organization or repository**: Click **Actions** in the left sidebar{% ifversion fpt %}, then click **Runners**{% endif %}. - * {% ifversion fpt %}**If using an enterprise account**:{% elsif ghes or ghae %}**If using an enterprise-level runner**:{% endif %} Click **Actions** under "{% octicon "law" aria-label="The law icon" %} Policies"{% ifversion fpt %}, then click the **Runners** tab{% endif %}. + * **In an organization or repository**: Click **Actions** in the left sidebar{% ifversion fpt or ghes > 3.1 or ghae-next %}, then click **Runners**{% endif %}. + * {% ifversion fpt %}**If using an enterprise account**:{% elsif ghes or ghae %}**If using an enterprise-level runner**:{% endif %} Click **Actions** under "{% octicon "law" aria-label="The law icon" %} Policies"{% ifversion fpt or ghes > 3.1 or ghae-next %}, then click the **Runners** tab{% endif %}. diff --git a/translations/ru-RU/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md b/translations/ru-RU/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md index 44f3b792d0..aac9a6f362 100644 --- a/translations/ru-RU/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md +++ b/translations/ru-RU/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md @@ -1,4 +1,4 @@ -1. Under {% ifversion fpt %}"Runners"{% else %}"Self-hosted runners"{% endif %}, locate the runner in the list. If your runner is in a group, click {% octicon "chevron-down" aria-label="The downwards chevron" %} to expand the list. +1. Under {% ifversion fpt or ghes > 3.1 or ghae-next %}"Runners"{% else %}"Self-hosted runners"{% endif %}, locate the runner in the list. If your runner is in a group, click {% octicon "chevron-down" aria-label="The downwards chevron" %} to expand the list. 1. Click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} next to the runner you want to remove, then click **Remove**. ![Removing a self-hosted runner setting](/assets/images/help/settings/actions-runner-remove.png) diff --git a/translations/ru-RU/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md b/translations/ru-RU/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md index 1be447145b..d51fdc01ef 100644 --- a/translations/ru-RU/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md +++ b/translations/ru-RU/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md @@ -1,2 +1,2 @@ -1. In the left sidebar, click **Actions**. -1. In the left sidebar, under "Actions", click **Runner groups**. +1. In the left sidebar, click **Actions**.{% ifversion fpt or ghes > 3.1 or ghae-next %} +1. In the left sidebar, under "Actions", click **Runner groups**.{% endif %} diff --git a/translations/ru-RU/data/reusables/github-actions/settings-sidebar-actions-runners.md b/translations/ru-RU/data/reusables/github-actions/settings-sidebar-actions-runners.md index cf1a5ba36f..181fbef515 100644 --- a/translations/ru-RU/data/reusables/github-actions/settings-sidebar-actions-runners.md +++ b/translations/ru-RU/data/reusables/github-actions/settings-sidebar-actions-runners.md @@ -1 +1 @@ -1. In the left sidebar, click **Actions**{% ifversion fpt %}, then click **Runners**{% endif %}. +1. In the left sidebar, click **Actions**{% ifversion fpt or ghes > 3.1 or ghae-next %}, then click **Runners**{% endif %}. diff --git a/translations/ru-RU/data/reusables/github-actions/supported-github-runners.md b/translations/ru-RU/data/reusables/github-actions/supported-github-runners.md index 29b2d96a5b..c634e7236c 100644 --- a/translations/ru-RU/data/reusables/github-actions/supported-github-runners.md +++ b/translations/ru-RU/data/reusables/github-actions/supported-github-runners.md @@ -60,17 +60,6 @@ Ubuntu 18.04     - - - - - @@ -353,7 +352,7 @@ codeql database analyze <database> --format=<format> \ @@ -406,7 +405,7 @@ codeql database analyze <database> --format=<format> \
    - Specify the name of the ref you checked out and analyzed so that the results can be matched to the correct code. For a branch use: refs/heads/BRANCH-NAME, for the head commit of a pull request use refs/pulls/NUMBER/head, or for the {% data variables.product.product_name %}-generated merge commit of a pull request use refs/pulls/NUMBER/merge. + Specify the name of the ref you checked out and analyzed so that the results can be matched to the correct code. For a branch use: refs/heads/BRANCH-NAME, for the head commit of a pull request use refs/pulls/NUMBER/head, or for the {% data variables.product.prodname_dotcom %}-generated merge commit of a pull request use refs/pulls/NUMBER/merge.
    - Specify the SARIF file to load.{% ifversion ghes > 3.0 or ghae-next %} + Specify the SARIF file to load.{% ifversion ghes > 3.0 or ghae %}
    -Ubuntu 16.04[deprecated] - -ubuntu-16.04 - -Deprecated and limited to existing customers only. Migrate to Ubuntu 20.04. For more information, see the blog post. -
    macOS Big Sur 11 diff --git a/translations/ru-RU/data/reusables/github-connect/access-dotcom-and-enterprise.md b/translations/ru-RU/data/reusables/github-connect/access-dotcom-and-enterprise.md index 6b9b37d713..2f22dbfd74 100644 --- a/translations/ru-RU/data/reusables/github-connect/access-dotcom-and-enterprise.md +++ b/translations/ru-RU/data/reusables/github-connect/access-dotcom-and-enterprise.md @@ -1 +1 @@ -1. Sign in to {% data variables.product.product_location_enterprise %} and {% data variables.product.prodname_dotcom_the_website %}. +1. Sign in to {% ifversion ghes %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_ghe_managed %}{% endif %} and {% data variables.product.prodname_dotcom_the_website %}. diff --git a/translations/ru-RU/data/reusables/github-connect/access-profile-settings.md b/translations/ru-RU/data/reusables/github-connect/access-profile-settings.md index c157ad63e1..901722cd34 100644 --- a/translations/ru-RU/data/reusables/github-connect/access-profile-settings.md +++ b/translations/ru-RU/data/reusables/github-connect/access-profile-settings.md @@ -1 +1 @@ -1. On {% data variables.product.product_location_enterprise %}, in the upper-right corner of any page, click your profile photo, then click **Settings**. ![Settings icon in the user bar](/assets/images/help/settings/userbar-account-settings.png) +1. On {% ifversion ghes %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_ghe_managed %}{% endif %}, in the upper-right corner of any page, click your profile photo, then click **Settings**. ![Settings icon in the user bar](/assets/images/help/settings/userbar-account-settings.png) diff --git a/translations/ru-RU/data/reusables/github-connect/authorize-connection.md b/translations/ru-RU/data/reusables/github-connect/authorize-connection.md index def6828956..3f3f26a09f 100644 --- a/translations/ru-RU/data/reusables/github-connect/authorize-connection.md +++ b/translations/ru-RU/data/reusables/github-connect/authorize-connection.md @@ -1 +1,7 @@ -1. Review the resources that {% data variables.product.prodname_ghe_server %} will access from your {% data variables.product.prodname_dotcom_the_website %} account, then click **Authorize**. ![Authorize connection between GitHub Enterprise Server and GitHub.com](/assets/images/help/settings/authorize-ghe-to-connect-to-dotcom.png) +1. Review the resources that +{% data variables.product.product_name %} will access from your {% data variables.product.prodname_dotcom_the_website %} account, then click **Authorize**. +{% ifversion ghes %} + ![Authorize connection between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_dotcom_the_website %}](/assets/images/help/settings/authorize-ghe-to-connect-to-dotcom.png) +{% elsif ghae %} + ![Authorize connection between {% data variables.product.prodname_ghe_managed %} and {% data variables.product.prodname_dotcom_the_website %}](/assets/images/enterprise/github-ae/settings/authorize-ghae-to-connect-to-dotcom.png) +{% endif %} diff --git a/translations/ru-RU/data/reusables/github-connect/beta.md b/translations/ru-RU/data/reusables/github-connect/beta.md new file mode 100644 index 0000000000..991a98d3d6 --- /dev/null +++ b/translations/ru-RU/data/reusables/github-connect/beta.md @@ -0,0 +1,7 @@ +{% ifversion ghae-next %} +{% note %} + +**Note:** {% data variables.product.prodname_github_connect %} for {% data variables.product.product_name %} is currently in beta and subject to change. + +{% endnote %} +{% endif %} diff --git a/translations/ru-RU/data/reusables/github-connect/connect-dotcom-and-enterprise.md b/translations/ru-RU/data/reusables/github-connect/connect-dotcom-and-enterprise.md index b639ddaf90..c05d2afdae 100644 --- a/translations/ru-RU/data/reusables/github-connect/connect-dotcom-and-enterprise.md +++ b/translations/ru-RU/data/reusables/github-connect/connect-dotcom-and-enterprise.md @@ -1 +1,6 @@ -1. Click **Connect to {% data variables.product.prodname_dotcom_the_website %}**. ![Connect to GitHub.com from GitHub Enterprise Server settings](/assets/images/help/settings/github.com_end_user_connection.png) +1. Click **Connect to {% data variables.product.prodname_dotcom_the_website %}**. +{% ifversion ghes %} + ![Connect to GitHub.com from GitHub Enterprise Server settings](/assets/images/help/settings/github.com_end_user_connection.png) +{% else %} + ![Connect to GitHub.com from GitHub AE settings](/assets/images/enterprise/github-ae/settings/github.com-end-user-connection.png) +{% endif %} diff --git a/translations/ru-RU/data/reusables/github-connect/send-contribution-counts-to-githubcom.md b/translations/ru-RU/data/reusables/github-connect/send-contribution-counts-to-githubcom.md new file mode 100644 index 0000000000..8004aa7150 --- /dev/null +++ b/translations/ru-RU/data/reusables/github-connect/send-contribution-counts-to-githubcom.md @@ -0,0 +1 @@ +1. Under "Contributions", select **Send my contribution counts to {% data variables.product.prodname_dotcom_the_website %}**, then click **Update contributions.** ![Send contributions checkbox and update contributions button](/assets/images/help/settings/send-and-update-contributions.png) diff --git a/translations/ru-RU/data/reusables/github-connect/sync-frequency.md b/translations/ru-RU/data/reusables/github-connect/sync-frequency.md index 93f01ae837..75a4fd8218 100644 --- a/translations/ru-RU/data/reusables/github-connect/sync-frequency.md +++ b/translations/ru-RU/data/reusables/github-connect/sync-frequency.md @@ -1 +1 @@ -{% data variables.product.prodname_ghe_server %} sends updates hourly. +{% data variables.product.product_name %} sends updates hourly. diff --git a/translations/ru-RU/data/reusables/notifications-v2/custom-notification-types.md b/translations/ru-RU/data/reusables/notifications-v2/custom-notification-types.md index d29d7447d4..2299c52284 100644 --- a/translations/ru-RU/data/reusables/notifications-v2/custom-notification-types.md +++ b/translations/ru-RU/data/reusables/notifications-v2/custom-notification-types.md @@ -1,2 +1,2 @@ {%- ifversion fpt or ghes > 3.1 or ghae-issue-4910 %}issues, pulls requests, releases, security alerts, or discussions{% endif %} -{%- ifversion ghes = 3.1 or ghae-next %}issues, pull requests, releases, or discussions{% endif %} +{%- ifversion ghes = 3.1 %}issues, pull requests, releases, or discussions{% endif %} diff --git a/translations/ru-RU/data/reusables/pages/about-private-publishing.md b/translations/ru-RU/data/reusables/pages/about-private-publishing.md index f1f13531ce..7d6708b21e 100644 --- a/translations/ru-RU/data/reusables/pages/about-private-publishing.md +++ b/translations/ru-RU/data/reusables/pages/about-private-publishing.md @@ -1 +1 @@ -If your project site is published from a private or internal repository owned by an organization using {% data variables.product.prodname_ghe_cloud %}, you can manage access control for the site. +If your project site is published from a private or internal repository owned by an organization using {% data variables.product.prodname_ghe_cloud %}, you can manage access control for the site. In an {% data variables.product.prodname_emu_enterprise %}, all {% data variables.product.prodname_pages %} sites are privately published. diff --git a/translations/ru-RU/data/reusables/repositories/auto-gen-release-public-beta.md b/translations/ru-RU/data/reusables/repositories/auto-gen-release-public-beta.md new file mode 100644 index 0000000000..1271ce25e0 --- /dev/null +++ b/translations/ru-RU/data/reusables/repositories/auto-gen-release-public-beta.md @@ -0,0 +1 @@ +Automatically generated release notes are currently in public beta and subject to change. diff --git a/translations/ru-RU/data/reusables/repositories/disabling-markdown-rendering.md b/translations/ru-RU/data/reusables/repositories/disabling-markdown-rendering.md new file mode 100644 index 0000000000..86254f64ec --- /dev/null +++ b/translations/ru-RU/data/reusables/repositories/disabling-markdown-rendering.md @@ -0,0 +1,5 @@ +When viewing a Markdown file, you can click {% octicon "code" aria-label="The code icon" %} at the top of the file to disable Markdown rendering and view the file's source instead. + +![Display Markdown as source](/assets/images/help/writing/display-markdown-as-source.png) + +Disabling Markdown rendering enables you to use source view features, such as line linking, which is not possible when viewing rendered Markdown files. diff --git a/translations/ru-RU/data/reusables/repositories/request-security-advisory-cve-id.md b/translations/ru-RU/data/reusables/repositories/request-security-advisory-cve-id.md index 72b4465e0a..64c1f4bb0d 100644 --- a/translations/ru-RU/data/reusables/repositories/request-security-advisory-cve-id.md +++ b/translations/ru-RU/data/reusables/repositories/request-security-advisory-cve-id.md @@ -1,5 +1,3 @@ -If you don't already have a CVE identification number for the security vulnerability in your project, you can request a CVE identification number from {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_dotcom %} usually reviews the request within 72 hours. Requesting a CVE identification number doesn't make your security advisory public. If your security advisory is eligible for a CVE, {% data variables.product.prodname_dotcom %} will reserve a CVE identification number for your advisory. We'll then publish the CVE details after you publish the security advisory. +If you want a CVE identification number for the security vulnerability in your project, and don't already have one, you can request a CVE identification number from {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_dotcom %} usually reviews the request within 72 hours. Requesting a CVE identification number doesn't make your security advisory public. If your security advisory is eligible for a CVE, {% data variables.product.prodname_dotcom %} will reserve a CVE identification number for your advisory. We'll then publish the CVE details after you make your security advisory public. Anyone with admin permissions to a security advisory can request a CVE identification number. -If you already have a CVE you want to use, for example, if you use a CNA other than {% data variables.product.prodname_dotcom %}, add it to the security advisory form. This may happen, for example, if you want to get the advisory consistent with other communications you plan to send out at publication time. - -If an advisory form doesn't have a CVE, we will request a CVE for you when you publish the advisory. +If you already have a CVE you want to use, for example, if you use a CVE Numbering Authority (CNA) other than {% data variables.product.prodname_dotcom %}, add the CVE to the security advisory form. This may happen, for example, if you want to get the advisory consistent with other communications you plan to send out at publication time. {% data variables.product.prodname_dotcom %} cannot assign CVEs to your project if it is covered by another CNA. \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/repositories/sidebar-issues.md b/translations/ru-RU/data/reusables/repositories/sidebar-issues.md index 13bed1db79..ade968c6b1 100644 --- a/translations/ru-RU/data/reusables/repositories/sidebar-issues.md +++ b/translations/ru-RU/data/reusables/repositories/sidebar-issues.md @@ -1,5 +1,5 @@ 2. Под именем вашего репозитория щелкните {% octicon "issue-opened" aria-label="The issues icon" %} **Issues**. - {% ifversion fpt or ghes > 3.1 or ghae-issue-4483 %} + {% ifversion fpt or ghes > 3.1 or ghae-next %} ![Issues tab](/assets/images/help/repository/repo-tabs-issues.png){% else %} ![Issues tab](/assets/images/enterprise/3.1/help/repository/repo-tabs-issues.png){% endif %} diff --git a/translations/ru-RU/data/reusables/repositories/sidebar-pr.md b/translations/ru-RU/data/reusables/repositories/sidebar-pr.md index 305bf7aeb2..c17858e727 100644 --- a/translations/ru-RU/data/reusables/repositories/sidebar-pr.md +++ b/translations/ru-RU/data/reusables/repositories/sidebar-pr.md @@ -1,5 +1,5 @@ 1. Под именем вашего репозитория щелкните {% octicon "git-pull-request" aria-label="The pull request icon" %} **Pull requests**. - {% ifversion fpt or ghes > 3.1 or ghae-issue-4483 %} + {% ifversion fpt or ghes > 3.1 or ghae-next %} ![Issues and pull requests tab selection](/assets/images/help/repository/repo-tabs-pull-requests.png){% else %} ![Issues tab](/assets/images/enterprise/3.1/help/repository/repo-tabs-pull-requests.png){% endif %} diff --git a/translations/ru-RU/data/reusables/repositories/workflow-notifications.md b/translations/ru-RU/data/reusables/repositories/workflow-notifications.md index c1399976e8..d9f2a271db 100644 --- a/translations/ru-RU/data/reusables/repositories/workflow-notifications.md +++ b/translations/ru-RU/data/reusables/repositories/workflow-notifications.md @@ -1,4 +1,4 @@ -If you enable email or web notifications for {% data variables.product.prodname_actions %}, you'll receive a notification when any workflow runs that you've triggered have completed. The notification will include the workflow run's status (including successful, failed, neutral, and canceled runs). You can also choose to receive a notification only when a workflow run has failed. +If you enable email or web notifications for {% data variables.product.prodname_actions %}, you'll receive a notification when any workflow runs that you've triggered have completed. The notification will include the workflow run's status (including successful, failed, neutral, and canceled runs). You can also choose to receive a notification only when a workflow run has failed. For more information about enabling or disabling notifications, see "[About notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)." Notifications for scheduled workflows are sent to the user who initially created the workflow. If a different user updates the cron syntax in the workflow file, subsequent notifications will be sent to that user instead.{% ifversion fpt or ghes > 2.22 %} If a scheduled workflow is disabled and then re-enabled, notifications will be sent to the user who re-enabled the workflow rather than the user who last modified the cron syntax.{% endif %} diff --git a/translations/ru-RU/data/reusables/saml/about-linked-identities.md b/translations/ru-RU/data/reusables/saml/about-linked-identities.md index f879d16402..25747fe629 100644 --- a/translations/ru-RU/data/reusables/saml/about-linked-identities.md +++ b/translations/ru-RU/data/reusables/saml/about-linked-identities.md @@ -1,3 +1,3 @@ -You can view the single sign-on identity that a member has linked to their {% data variables.product.product_name %} account. When available, the entry will include SCIM data. For more information, see "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)." +You can view the single sign-on identity that a member has linked to their {% data variables.product.product_name %} account. If a member links the wrong identity to their {% data variables.product.product_name %} account, you can revoke the linked identity to allow the member to try again. diff --git a/translations/ru-RU/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/ru-RU/data/reusables/secret-scanning/partner-secret-list-private-repo.md index 7bb265bee2..9e6a06ebd2 100644 --- a/translations/ru-RU/data/reusables/secret-scanning/partner-secret-list-private-repo.md +++ b/translations/ru-RU/data/reusables/secret-scanning/partner-secret-list-private-repo.md @@ -1,7 +1,7 @@ | Provider | Supported secret | API slug | | -------- | ---------------- | -------- | | | | | -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Adafruit IO | Adafruit IO Key | adafruit_io_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Adobe | Adobe Device Token | adobe_device_token{% endif %} @@ -11,73 +11,73 @@ Adobe | Adobe Service Token | adobe_service_token{% endif %} Adobe | Adobe Short-Lived Access Token | adobe_short_lived_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Adobe | Adobe JSON Web Token | adobe_jwt{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Alibaba Cloud | Alibaba Cloud Access Key ID | alibaba_cloud_access_key_id{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Alibaba Cloud | Alibaba Cloud Access Key Secret | alibaba_cloud_access_key_secret{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Amazon Web Services (AWS) | Amazon AWS Access Key ID | aws_access_key_id{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Amazon Web Services (AWS) | Amazon AWS Secret Access Key | aws_secret_access_key{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Amazon Web Services (AWS) | Amazon AWS Session Token | aws_session_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Amazon Web Services (AWS) | Amazon AWS Temporary Access Key ID | aws_temporary_access_key_id{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Asana | Asana Personal Access Token | asana_personal_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Atlassian | Atlassian API Token | atlassian_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Atlassian | Atlassian JSON Web Token | atlassian_jwt{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Atlassian | Bitbucket Server Personal Access Token | bitbucket_server_personal_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Azure | Azure SAS Token | azure_sas_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Azure | Azure Service Management Certificate | azure_management_certificate{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Azure | Azure SQL Connection String | azure_sql_connection_string{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Azure | Azure Storage Account Key | azure_storage_account_key{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Beamer | Beamer API Key | beamer_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Checkout.com | Checkout.com Production Secret Key | checkout_production_secret_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Checkout.com | Checkout.com Test Secret Key | checkout_test_secret_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Clojars | Clojars Deploy Token | clojars_deploy_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} CloudBees CodeShip | CloudBees CodeShip Credential | codeship_credential{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Contentful | Contentful Personal Access Token | contentful_personal_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Databricks | Databricks Access Token | databricks_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Discord | Discord Bot Token | discord_bot_token{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Doppler | Doppler Personal Token | doppler_personal_token{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Doppler | Doppler Service Token | doppler_service_token{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Doppler | Doppler CLI Token | doppler_cli_token{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Doppler | Doppler SCIM Token | doppler_scim_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Doppler | Doppler Audit Token | doppler_audit_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Dropbox | Dropbox Access Token | dropbox_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Dropbox | Dropbox Short Lived Access Token | dropbox_short_lived_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Duffel | Duffel Live Access Token | duffel_live_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Duffel | Duffel Test Access Token | duffel_test_access_token{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Dynatrace | Dynatrace Access Token | dynatrace_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Dynatrace | Dynatrace Internal Token | dynatrace_internal_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} EasyPost | EasyPost Production API Key | easypost_production_api_key{% endif %} @@ -87,17 +87,17 @@ EasyPost | EasyPost Test API Key | easypost_test_api_key{% endif %} Facebook | Facebook Access Token | facebook_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Fastly | Fastly API Token | fastly_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Finicity | Finicity App Key | finicity_app_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Flutterwave | Flutterwave Live API Secret Key | flutterwave_live_api_secret_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Flutterwave | Flutterwave Test API Secret Key | flutterwave_test_api_secret_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Frame.io | Frame.io JSON Web Token | frameio_jwt{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Frame.io| Frame.io Developer Token | frameio_developer_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} FullStory | FullStory API Key | fullstory_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} GitHub | GitHub Personal Access Token | github_personal_access_token{% endif %} @@ -107,29 +107,29 @@ GitHub | GitHub OAuth Access Token | github_oauth_access_token{% endif %} GitHub | GitHub Refresh Token | github_refresh_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} GitHub | GitHub App Installation Access Token | github_app_installation_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} GitHub | GitHub SSH Private Key | github_ssh_private_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} GoCardless | GoCardless Live Access Token | gocardless_live_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} GoCardless | GoCardless Sandbox Access Token | gocardless_sandbox_access_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Google | Firebase Cloud Messaging Server Key | firebase_cloud_messaging_server_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Google | Google API Key | google_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Google | Google Cloud Private Key ID | google_cloud_private_key_id{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Google | Google Cloud Storage Access Key Secret | google_cloud_storage_access_key_secret{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Google | Google Cloud Storage Service Account Access Key ID | google_cloud_storage_service_account_access_key_id{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Google | Google Cloud Storage User Access Key ID | google_cloud_storage_user_access_key_id{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Grafana | Grafana API Key | grafana_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Hashicorp Terraform | Terraform Cloud / Enterprise API Token | terraform_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Hubspot | Hubspot API Key | hubspot_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Intercom | Intercom Access Token | intercom_access_token{% endif %} @@ -137,9 +137,9 @@ Intercom | Intercom Access Token | intercom_access_token{% endif %} Ionic | Ionic Personal Access Token | ionic_personal_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Ionic | Ionic Refresh Token | ionic_refresh_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} JFrog | JFrog Platform Access Token | jfrog_platform_access_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} JFrog | JFrog Platform API Key | jfrog_platform_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Linear | Linear API Key | linear_api_key{% endif %} @@ -149,15 +149,23 @@ Linear | Linear OAuth Access Token | linear_oauth_access_token{% endif %} Lob | Lob Live API Key | lob_live_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Lob | Lob Test API Key | lob_test_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Mailchimp | Mailchimp API Key | mailchimp_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Mailgun | Mailgun API Key | mailgun_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} MessageBird | MessageBird API Key | messagebird_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} +New Relic | New Relic Personal API Key | new_relic_personal_api_key{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +New Relic | New Relic REST API Key | new_relic_rest_api_key{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +New Relic | New Relic Insights Query Key | new_relic_insights_query_key{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +New Relic | New Relic License Key | new_relic_license_key{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} npm | npm Access Token | npm_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} NuGet | NuGet API Key | nuget_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Onfido | Onfido Live API Token | onfido_live_api_token{% endif %} @@ -165,75 +173,75 @@ Onfido | Onfido Live API Token | onfido_live_api_token{% endif %} Onfido | Onfido Sandbox API Token | onfido_sandbox_api_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} OpenAI | OpenAI API Key | openai_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Palantir | Palantir JSON Web Token | palantir_jwt{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} PlanetScale | PlanetScale Database Password | planetscale_database_password{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} PlanetScale | PlanetScale OAuth Token | planetscale_oauth_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} PlanetScale | PlanetScale Service Token | planetscale_service_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Plivo | Plivo Auth ID | plivo_auth_id{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Plivo | Plivo Auth Token | plivo_auth_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Postman | Postman API Key | postman_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Proctorio | Proctorio Consumer Key | proctorio_consumer_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Proctorio | Proctorio Linkage Key | proctorio_linkage_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Proctorio | Proctorio Registration Key | proctorio_registration_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Proctorio | Proctorio Secret Key | proctorio_secret_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Pulumi | Pulumi Access Token | pulumi_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} PyPI | PyPI API Token | pypi_api_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} RubyGems | RubyGems API Key | rubygems_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Samsara | Samsara API Token | samsara_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Samsara | Samsara OAuth Access Token | samsara_oauth_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} SendGrid | SendGrid API Key | sendgrid_api_key{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Sendinblue | Sendinblue API Key | sendinblue_api_key{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Sendinblue | Sendinblue SMTP Key | sendinblue_smtp_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Shippo | Shippo Live API Token | shippo_live_api_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Shippo | Shippo Test API Token | shippo_test_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Shopify | Shopify App Shared Secret | shopify_app_shared_secret{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Shopify | Shopify Access Token | shopify_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Shopify | Shopify Custom App Access Token | shopify_custom_app_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Shopify | Shopify Private App Password | shopify_private_app_password{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Slack | Slack API Token | slack_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Slack | Slack Incoming Webhook URL | slack_incoming_webhook_url{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Slack | Slack Workflow Webhook URL | slack_workflow_webhook_url{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} SSLMate | SSLMate API Key | sslmate_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} SSLMate | SSLMate Cluster Secret | sslmate_cluster_secret{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Stripe | Stripe API Key | stripe_api_key{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Stripe | Stripe Live API Secret Key | stripe_live_secret_key{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Stripe | Stripe Test API Secret Key | stripe_test_secret_key{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Stripe | Stripe Live API Restricted Key | stripe_live_restricted_key{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Stripe | Stripe Test API Restricted Key | stripe_test_restricted_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Stripe | Stripe Webhook Signing Secret | stripe_webhook_signing_secret{% endif %} @@ -241,9 +249,9 @@ Stripe | Stripe Webhook Signing Secret | stripe_webhook_signing_secret{% endif % Tableau | Tableau Personal Access Token | tableau_personal_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Telegram | Telegram Bot Token | telegram_bot_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Tencent Cloud | Tencent Cloud Secret ID | tencent_cloud_secret_id{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Twilio | Twilio Account String Identifier | twilio_account_sid{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Twilio | Twilio API Key | twilio_api_key{% endif %} diff --git a/translations/ru-RU/data/reusables/sponsors/add-welcome-message.md b/translations/ru-RU/data/reusables/sponsors/add-welcome-message.md new file mode 100644 index 0000000000..8962236ad1 --- /dev/null +++ b/translations/ru-RU/data/reusables/sponsors/add-welcome-message.md @@ -0,0 +1 @@ +1. Optionally, type a welcome message for the tier. ![Add welcome message](/assets/images/help/sponsors/add-a-welcome-message.png) \ No newline at end of file diff --git a/translations/ru-RU/data/reusables/sponsors/tier-details.md b/translations/ru-RU/data/reusables/sponsors/tier-details.md index 7cd63f54a6..fe2189aabf 100644 --- a/translations/ru-RU/data/reusables/sponsors/tier-details.md +++ b/translations/ru-RU/data/reusables/sponsors/tier-details.md @@ -1,4 +1,4 @@ -You can create up to 10 one-time sponsorship tiers and 10 monthly tiers for sponsors to choose from. Each tier has its own one-time or monthly payment amount in US dollars, and you can choose to enable tiers for custom amounts. In addition, you can choose to enable tiers for custom amounts (monthly and one-time). +You can create up to 10 one-time sponsorship tiers and 10 monthly tiers for sponsors to choose from. Each tier has its own one-time or monthly payment amount in US dollars, and you can choose to enable tiers for custom amounts. In addition, you can choose to enable tiers for custom amounts (monthly and one-time). You can customize the rewards for each tier. For example, rewards for a tier could include: - Early access to new versions @@ -7,4 +7,6 @@ You can customize the rewards for each tier. For example, rewards for a tier cou - Weekly newsletter updates - Other rewards your sponsors would enjoy ✨ +You can include a welcome message with information about accessing or receiving rewards, which will be visible after payment and in the welcome email. + Once you have published a tier, you cannot edit the price of that tier. Instead, you must retire the tier and create a new tier. Existing sponsors will remain on the retired tier until they change their sponsorship tier, cancel their sponsorship, or their one-time sponsorship period expires. diff --git a/translations/ru-RU/data/reusables/ssh/add-ssh-key-to-ssh-agent-commandline.md b/translations/ru-RU/data/reusables/ssh/add-ssh-key-to-ssh-agent-commandline.md index 415f86736d..9bed61119b 100644 --- a/translations/ru-RU/data/reusables/ssh/add-ssh-key-to-ssh-agent-commandline.md +++ b/translations/ru-RU/data/reusables/ssh/add-ssh-key-to-ssh-agent-commandline.md @@ -1,3 +1,3 @@ ```shell -$ ssh-add ~/.ssh/id_ed25519 +$ ssh-add ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %} ``` diff --git a/translations/ru-RU/data/reusables/ssh/add-ssh-key-to-ssh-agent.md b/translations/ru-RU/data/reusables/ssh/add-ssh-key-to-ssh-agent.md index fb1ca5ec34..43243b9f14 100644 --- a/translations/ru-RU/data/reusables/ssh/add-ssh-key-to-ssh-agent.md +++ b/translations/ru-RU/data/reusables/ssh/add-ssh-key-to-ssh-agent.md @@ -1 +1 @@ -If you created your key with a different name, or if you are adding an existing key that has a different name, replace *id_ed25519* in the command with the name of your private key file. +If you created your key with a different name, or if you are adding an existing key that has a different name, replace *id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}* in the command with the name of your private key file. diff --git a/translations/ru-RU/data/reusables/user_settings/generate_new_token.md b/translations/ru-RU/data/reusables/user_settings/generate_new_token.md new file mode 100644 index 0000000000..adf9fe1f14 --- /dev/null +++ b/translations/ru-RU/data/reusables/user_settings/generate_new_token.md @@ -0,0 +1 @@ +1. Click **Generate new token**. ![Generate new token button](/assets/images/help/settings/generate_new_token.png) \ No newline at end of file diff --git a/translations/ru-RU/data/ui.yml b/translations/ru-RU/data/ui.yml index ba83c0a2ce..b08c4add27 100644 --- a/translations/ru-RU/data/ui.yml +++ b/translations/ru-RU/data/ui.yml @@ -30,9 +30,10 @@ toc: guides: Руководства whats_new: What's new pages: - article_version: 'Article version:' + article_version: 'Article version' miniToc: В этой статье contributor_callout: This article is contributed and maintained by + all_enterprise_releases: All Enterprise releases errors: oops: Ooops! something_went_wrong: It looks like something went wrong. @@ -155,13 +156,17 @@ product_sublanding: learning_paths_desc: Learning paths are a collection of guides that help you master a particular subject. guides: '{{ productMap[currentProduct].name }} guides' more_guides: more guides - no_result: Sorry, there are no guides that match your filter. load_more: Load more guides all_guides: 'All {{ productMap[currentProduct].name }} guides' + filter_instructions: Filter the guide list using these controls filters: type: Тип topic: Topic all: All + guides_found: + multiple: '{n} guides found' + one: 1 guide found + none: No guides found guide_types: overview: Обзор quick_start: Quickstart diff --git a/translations/ru-RU/data/variables/product.yml b/translations/ru-RU/data/variables/product.yml index c5f75ede3a..ba83d21ee9 100644 --- a/translations/ru-RU/data/variables/product.yml +++ b/translations/ru-RU/data/variables/product.yml @@ -76,6 +76,14 @@ prodname_actions: 'GitHub Actions' prodname_debug: 'GitHub Debug' #GitHub Discussions prodname_discussions: 'GitHub Discussions' +#GitHub Enterprise Managed Users +prodname_emu_idp_application: 'GitHub Enterprise Managed User' +prodname_emus: 'Enterprise Managed Users' +prodname_managed_user: 'managed user' +prodname_managed_users: 'managed users' +prodname_managed_users_caps: 'Managed users' +prodname_emu_enterprise: 'enterprise with managed users' +prodname_emu_org: 'organization with managed users' #GitHub Issues prodname_github_issues: 'GitHub Issues' #GitHub Packages @@ -94,6 +102,7 @@ prodname_security_center: 'Security Center' #Codespaces prodname_codespaces: 'Codespaces' prodname_github_codespaces: 'GitHub Codespaces' +prodname_serverless: 'web-based editor' #GitHub resources: blog, jobs, Learning Lab prodname_gcf: 'GitHub Community Support' prodname_blog: 'the GitHub Blog' @@ -135,6 +144,8 @@ prodname_dependabot_version_updates: 'Dependabot version updates' #GitHub Archive Program prodname_archive: 'GitHub Archive Program' prodname_arctic_vault: 'Arctic Code Vault' +#GitHub Copilot +prodname_copilot: 'GitHub Copilot' #Links product_url: >- {% ifversion fpt %}github.com{% else %}[hostname]{% endif %} diff --git a/translations/ru-RU/data/variables/release_candidate.yml b/translations/ru-RU/data/variables/release_candidate.yml index e6ddf079ac..ec65ef6f94 100644 --- a/translations/ru-RU/data/variables/release_candidate.yml +++ b/translations/ru-RU/data/variables/release_candidate.yml @@ -1,2 +1,2 @@ --- -version: enterprise-server@3.2 +version: '' diff --git a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md index 0f756e724f..e8ae8858c8 100644 --- a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md +++ b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md @@ -45,7 +45,7 @@ shortTitle: 管理您的订阅 {% data reusables.notifications.access_notifications %} 1. 从通知收件箱中选择您想要取消订阅的通知。 -2. 使用 **selected（已选择）** {% octicon "triangle-down" aria-label="The down triangle icon" %} 下拉列表单击 **Unsubscribe（取消订阅）**。 ![主收件箱中的取消订阅选项](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png) +2. Click **Unsubscribe.** ![主收件箱中的取消订阅选项](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png) ## 从订阅页面取消订阅通知 @@ -61,13 +61,12 @@ shortTitle: 管理您的订阅 {% data reusables.notifications.access_notifications %} 1. 在左侧边栏中的仓库列表下，使用“Manage notifications（管理通知）”下拉按钮单击 **Watched repositories（已关注的仓库）**。 ![管理通知下拉菜单选项](/assets/images/help/notifications-v2/manage-notifications-options.png) 2. 在关注的仓库页面上，评估您关注的仓库后，选择是否： - {% ifversion ghae or ghes < 3.1 %} - - 取消关注仓库 - - 只关注某仓库的发行版 - - 忽略某仓库的所有通知 - {% endif %} {% ifversion fpt or ghes > 3.0 or ghae-next %} - 取消关注仓库 - 忽略某仓库的所有通知 - 自定义接收通知的事件类型 （{% data reusables.notifications-v2.custom-notification-types %}，如果启用） + {% else %} + - 取消关注仓库 + - 只关注某仓库的发行版 + - 忽略某仓库的所有通知 {% endif %} diff --git a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md index 0e95c9ef30..42ff874879 100644 --- a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md +++ b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md @@ -70,10 +70,10 @@ To see an overview of your repository subscriptions, see "[Reviewing repositorie 1. 在左侧边栏中的仓库列表下，使用“Manage notifications（管理通知）”下拉菜单单击 **Watched repositories（已关注的仓库）**。 ![管理通知下拉菜单选项](/assets/images/help/notifications-v2/manage-notifications-options.png) 2. 评估您正在关注的仓库，确定它们更新是否仍然相关和有用。 关注某仓库后，您将收到该仓库所有对话的通知。 -{% ifversion ghae or ghes < 3.1 %} - ![已关注的通知页面](/assets/images/help/notifications-v2/watched-notifications.png) -{% elsif fpt or ghes > 3.0 or ghae-next %} +{% ifversion fpt or ghes > 3.0 or ghae-next %} ![已关注的通知页面](/assets/images/help/notifications-v2/watched-notifications-custom.png) +{% else %} + ![已关注的通知页面](/assets/images/help/notifications-v2/watched-notifications.png) {% endif %} {% tip %} diff --git a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md index 06de519779..9cbaa6c14b 100644 --- a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md +++ b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md @@ -29,7 +29,7 @@ topics: - 关于特定议题、拉取请求或 Gist 的对话。 - 仓库或团队讨论中的所有活动。 - CI 活动，例如仓库中使用 {% data variables.product.prodname_actions %} 设置的工作流程的状态。 {% ifversion fpt or ghes > 3.0 or ghae-next %} -- 仓库 {% data reusables.notifications-v2.custom-notification-types %} (如果启用)。 {% elsif ghae or ghes %} +- Repository {% data reusables.notifications-v2.custom-notification-types %} (if enabled).{% else %} - 在仓库中发布。{% endif %} 您也可以选择自动关注所有您有推送访问权限的仓库，但复刻除外。 您可以通过单击 **Watch（关注）**来手动关注您有权访问的任何其他仓库。 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 17cb0ea9f7..7b9d8b2db8 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 @@ -70,12 +70,14 @@ topics: 关注仓库，意味着订阅该仓库中的活动更新。 同样，关注特定团队的讨论，意味着订阅该团队页面上的所有对话更新。 更多信息请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions)”。 要查看您关注的仓库，请参阅[关注页面](https://github.com/watching)。 更多信息请参阅“[在 GitHub 上管理订阅和通知](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)”。 + {% ifversion ghae or ghes < 3.1 %} ### 配置通知 {% endif %} -您可以在资源库页面或在您观看页面上配置仓库的通知。{% ifversion ghae or ghes < 3.1 %} 您可以选择仅接收有关仓库中发布的通知，或忽略有关仓库的所有通知。{% endif %} +You can configure notifications for a repository on the repository page, or on your watching page.{% ifversion ghes < 3.1 %} You can choose to only receive notifications for releases in a repository, or ignore all notifications for a repository.{% endif %} {% ifversion fpt or ghes > 3.0 or ghae-next %} + ### 关于自定义通知 您可以自定义仓库的通知。 例如，您可以选择仅在仓库中发生一类或多类事件 ({% data reusables.notifications-v2.custom-notification-types %}) 的更新时收到通知，或者忽略仓库的所有通知。 {% endif %} 更多信息请参阅下面的“[配置单个仓库的关注设置](#configuring-your-watch-settings-for-an-individual-repository)”。 @@ -158,25 +160,18 @@ topics: ## 配置单个仓库的关注设置 -您可以选择关注还是取消关注单个仓库。 You can also choose to only be notified of {% ifversion fpt or ghes > 3.0 or ghae-next %}certain event types such as {% data reusables.notifications-v2.custom-notification-types %} (if enabled for the repository){% else %}new releases{% endif %}, or completely ignore an individual repository. +您可以选择关注还是取消关注单个仓库。 您也可以选择接收{% ifversion fpt or ghes > 3.0 or ghae-next %}特定事件类型，如 {% data reusables.notifications-v2.custom-notification-types %}（如已对仓库启用）{% else %}新版本{% endif %}的通知，或者完全忽略单个仓库。 {% data reusables.repositories.navigate-to-repo %} 2. 在右上角，单击“Watch（关注）”下拉菜单选择关注选项。 -{% ifversion ghae or ghes < 3.1 %} - ![仓库下拉菜单中的关注选项](/assets/images/help/notifications-v2/watch-repository-options.png) -{% elsif fpt or ghes > 3.0 or ghae-next %} +{% ifversion fpt or ghes > 3.0 or ghae-next %} ![仓库下拉菜单中的关注选项](/assets/images/help/notifications-v2/watch-repository-options-custom.png) -**Custom（自定义）** 选项可用于进一步自定义通知，以便除了参与和 @提及之外，您仅在仓库中发生特定事件时才收到通知。 - -{% ifversion fpt or ghes > 3.1 or ghae-issue-4910 %} - ![仓库下拉菜单中的自定义关注选项](/assets/images/help/notifications-v2/watch-repository-options-custom2-dotcom.png) + **Custom（自定义）** 选项可用于进一步自定义通知，以便除了参与和 @提及之外，您仅在仓库中发生特定事件时才收到通知。 {% else %} - ![仓库下拉菜单中的自定义关注选项](/assets/images/enterprise/3.1/help/notifications-v2/watch-repository-options-custom2.png) -{% endif %} - -如果选择“Issues（议题）”，您将收到仓库中每个议题（包括在您选择此选项之前存在的议题）的更新通知并订阅它们。 如果您被此仓库中的拉取请求 @提及，则除了收到有关议题的通知外，您还将收到有关该特定拉取请求更新的通知并订阅它们。 - + ![仓库下拉菜单中的关注选项](/assets/images/help/notifications-v2/watch-repository-options.png){% endif %} +{% ifversion fpt or ghes > 3.0 or ghae-next %} + ![仓库下拉菜单中的自定义关注选项](/assets/images/help/notifications-v2/watch-repository-options-custom2-dotcom.png) 如果选择“Issues（议题）”，您将收到仓库中每个议题（包括在您选择此选项之前存在的议题）的更新通知并订阅它们。 如果您被此仓库中的拉取请求 @提及，则除了收到有关议题的通知外，您还将收到有关该特定拉取请求更新的通知并订阅它们。 {% endif %} ## 选择接收组织的电子邮件通知的位置 diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md index ecba523083..b1f731bd82 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md @@ -48,6 +48,14 @@ shortTitle: 个性化 您可以更改显示在个人资料中的名称。 此名称也可能显示在您对于组织拥有的私有仓库所做的注释旁边。 更多信息请参阅“[管理组织中成员名称的显示](/articles/managing-the-display-of-member-names-in-your-organization)”。 +{% ifversion fpt %} +{% note %} + +**Note:** If you're a member of an {% data variables.product.prodname_emu_enterprise %}, any changes to your profile name must be made through your identity provider instead of {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.emu-more-info-account %} + +{% endnote %} +{% endif %} + {% data reusables.user_settings.access_settings %} 2. 在“Name（名称）”下，键入要显示在个人资料中的名称。 ![个人资料设置中的名称字段](/assets/images/help/profile/name-field.png) diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/index.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/index.md index 428acade71..f40a6b8a07 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/index.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/index.md @@ -14,7 +14,7 @@ children: - /viewing-contributions-on-your-profile - /showing-an-overview-of-your-activity-on-your-profile - /publicizing-or-hiding-your-private-contributions-on-your-profile - - /sending-your-github-enterprise-server-contributions-to-your-githubcom-profile + - /sending-enterprise-contributions-to-your-githubcom-profile - /why-are-my-contributions-not-showing-up-on-my-profile - /troubleshooting-commits-on-your-timeline shortTitle: 管理贡献图 diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-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/publicizing-or-hiding-your-private-contributions-on-your-profile.md index ecf4ce0ec7..947ce1554e 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-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/publicizing-or-hiding-your-private-contributions-on-your-profile.md @@ -14,14 +14,18 @@ topics: shortTitle: 私有贡献 --- -如果公开您的私有贡献，对您处理的私有仓库没有访问权限的人员将无法查看您的私有贡献详情， 而只能看到您在指定日期的贡献数。 您的公共贡献会包含详细信息。 更多信息请参阅“[在个人资料页面中查看贡献](/articles/viewing-contributions-on-your-profile-page)”。 +如果公开您的私有贡献，对您处理的私有仓库没有访问权限的人员将无法查看您的私有贡献详情， 而只能看到您在指定日期的贡献数。 您的公共贡献会包含详细信息。 For more information, see "[Viewing contributions on your profile page](/articles/viewing-contributions-on-your-profile-page)." + +{% note %} + +**Note:** {% ifversion fpt or ghes %}On {% ifversion fpt %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_name %}{% endif %}, public contributions on your profile are visible {% ifversion fpt %}to anyone in the world who can access {% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}only to other users of {% data variables.product.product_location%}{% endif %}.{% elsif ghae %}On {% data variables.product.prodname_ghe_managed %}, only other members of your enterprise can see the contributions on your profile.{% endif %} + +{% endnote %} ## 更改私有贡献的可见性 -默认情况下，访问者在您的个人资料中只能查看公共贡献。 - {% data reusables.profile.access_profile %} -2. 在个人资料中公开或隐藏您的私有贡献： +1. 在个人资料中公开或隐藏您的私有贡献： - 要公开您的私有贡献，在贡献图上方，使用 **Contribution settings（贡献设置）**下拉菜单，然后选择 **Private contributions（私有贡献）**。 访问者将会看到您的私有贡献数，但没有更多详细信息。 ![从贡献设置下拉菜单允许访问者查看私有贡献](/assets/images/help/profile/private-contributions-on.png) - 要隐藏您的私有贡献，在贡献图上方，使用 **Contribution settings（贡献设置）**下拉菜单，然后取消选择 **Private contributions（私有贡献）**。访问者只会看到您的公共贡献。 ![从贡献设置下拉菜单允许访问者查看私有贡献](/assets/images/help/profile/private-contributions-off.png) diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md new file mode 100644 index 0000000000..547efffd52 --- /dev/null +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md @@ -0,0 +1,65 @@ +--- +title: Sending enterprise contributions to your GitHub.com profile +intro: '通过将贡献计数发送到您的 {% data variables.product.prodname_dotcom_the_website %} 配置文件，可在 {% data variables.product.prodname_enterprise %} 上突出显示您的作品。' +redirect_from: + - /articles/sending-your-github-enterprise-contributions-to-your-github-com-profile/ + - /articles/sending-your-github-enterprise-server-contributions-to-your-github-com-profile + - /articles/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile + - /github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile + - /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile +versions: + fpt: '*' + ghes: '*' + ghae: next +topics: + - Profiles +shortTitle: Send enterprise contributions +--- + +## About enterprise contributions on your {% data variables.product.prodname_dotcom_the_website %} profile + +Your {% data variables.product.prodname_dotcom_the_website %} profile shows {% ifversion fpt %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae-next %} or {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} contribution counts from the past 90 days. {% data reusables.github-connect.sync-frequency %} 来自 {% data variables.product.prodname_enterprise %} 的贡献计数被视为私有贡献。 The commit details will only show the contribution counts and that these contributions were made in a {% data variables.product.prodname_enterprise %} environment outside of {% data variables.product.prodname_dotcom_the_website %}. + +You can decide whether to show counts for private contributions on your profile. 更多信息请参阅“[在配置文件中公开或隐藏私有贡献](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile/)”。 + +有关如何计算贡献的更多详细，请参阅“[管理您的配置文件中的贡献图](/articles/managing-contribution-graphs-on-your-profile/)”。 + +{% note %} + +**注意：** +- 帐户之间的连接受 GitHub 的隐私声明约束，用户允许连接即表示同意 GitHub 的服务条款。 + +- Before you can connect your {% ifversion fpt %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae-next %} or {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} profile to your {% data variables.product.prodname_dotcom_the_website %} profile, your enterprise owner must enable {% data variables.product.prodname_github_connect %} and enable contribution sharing between the environments. For more information, contact your enterprise owner. + +{% endnote %} + +{% ifversion fpt or ghes or ghae %} + +## Sending your enterprise contributions to your {% data variables.product.prodname_dotcom_the_website %} profile + +{% ifversion fpt %} + +- To send enterprise contributions from {% data variables.product.prodname_ghe_server %} to your {% data variables.product.prodname_dotcom_the_website %} profile, see "[Sending enterprise contributions to your {% data variables.product.prodname_dotcom_the_website %} profile](/enterprise-server/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)" in the {% data variables.product.prodname_ghe_server %} documentation.{% ifversion ghae-next %} +- To send enterprise contributions from {% data variables.product.prodname_ghe_managed %} to your {% data variables.product.prodname_dotcom_the_website %} profile, see "[Sending enterprise contributions to your {% data variables.product.prodname_dotcom_the_website %} profile](/github-ae@latest/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)" in the {% data variables.product.prodname_ghe_managed %} documentation.{% endif %} + +{% elsif ghes %} + +1. Sign in to {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_dotcom_the_website %}. +1. On {% data variables.product.prodname_ghe_server %}, in the upper-right corner of any page, click your profile photo, then click **Settings**. ![用户栏中的 Settings 图标](/assets/images/help/settings/userbar-account-settings.png) +{% data reusables.github-connect.github-connect-tab-user-settings %} +{% data reusables.github-connect.connect-dotcom-and-enterprise %} +1. 查看 {% data variables.product.prodname_ghe_server %} 将从您的 {% data variables.product.prodname_dotcom_the_website %} 帐户访问的资源，然后单击 **Authorize（授权）**。 ![授权 GitHub Enterprise Server 与 GitHub.com 之间的连接](/assets/images/help/settings/authorize-ghe-to-connect-to-dotcom.png) +{% data reusables.github-connect.send-contribution-counts-to-githubcom %} + +{% elsif ghae %} + +1. Sign in to {% data variables.product.prodname_ghe_managed %} and {% data variables.product.prodname_dotcom_the_website %}. +1. On {% data variables.product.prodname_ghe_managed %}, in the upper-right corner of any page, click your profile photo, then click **Settings**. ![用户栏中的 Settings 图标](/assets/images/help/settings/userbar-account-settings.png) +{% data reusables.github-connect.github-connect-tab-user-settings %} +{% data reusables.github-connect.connect-dotcom-and-enterprise %} +{% data reusables.github-connect.authorize-connection %} +{% data reusables.github-connect.send-contribution-counts-to-githubcom %} + +{% endif %} + +{% endif %} 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 3cd8e170e2..c705473aa3 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 @@ -83,7 +83,7 @@ shortTitle: 查看贡献 ![个人资料中的活动概览部分](/assets/images/help/profile/activity-overview-section.png) -活动概览中提供的组织根据您在组织中的活跃程度确定优先级。 如果您在个人资料简历中@提及某个组织，并且您是组织成员，则该组织首先在活动概览中确定优先级。 更多信息请参阅“[提及人员和团队](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)”或“[将个人简历添加到个人资料](/articles/adding-a-bio-to-your-profile/)”。 +活动概览中提供的组织根据您在组织中的活跃程度确定优先级。 如果您在个人资料简历中@提及某个组织，并且您是组织成员，则该组织首先在活动概览中确定优先级。 For more information, see "[Mentioning people and teams](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)” or "[Adding a bio to your profile](/articles/adding-a-bio-to-your-profile/)." ## 贡献活动 @@ -91,15 +91,14 @@ shortTitle: 查看贡献 ![贡献活动时间过滤器](/assets/images/help/profile/contributions_activity_time_filter.png) -{% ifversion not ghae %} -## 在 {% data variables.product.prodname_dotcom_the_website %} 上查看 {% data variables.product.product_location_enterprise %}的贡献 +{% ifversion fpt or ghes or ghae-next %} + +## 在 {% data variables.product.prodname_dotcom_the_website %} 上查看 {% data variables.product.prodname_enterprise %}的贡献 + +If you use {% ifversion fpt %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae-next %} 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)." -如果您的站点管理员已启用{% data variables.product.prodname_unified_contributions %}，您可以将 {% data variables.product.prodname_enterprise %} 贡献计数发送到 {% data variables.product.prodname_dotcom_the_website %} 配置文件。 更多信息请参阅“[将 {% data variables.product.prodname_ghe_server %} 贡献发送到 {% data variables.product.prodname_dotcom_the_website %}](/articles/sending-your-github-enterprise-server-contributions-to-your-github-com-profile)”。 {% endif %} ## 延伸阅读 - "[在个人资料页面中查看贡献](/articles/viewing-contributions-on-your-profile-page)" -- “[为什么我的贡献没有在我的个人资料中显示？](/articles/why-are-my-contributions-not-showing-up-on-my-profile)” -- "[在个人资料中公开或隐藏私有贡献](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)" -- “[在个人资料中显示活动概览](/articles/showing-an-overview-of-your-activity-on-your-profile)” diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md index 0c47ac9f51..48cecaea17 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md @@ -24,6 +24,8 @@ shortTitle: 邀请协作者 {% ifversion fpt %} +If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you can only invite other members of your enterprise to collaborate with you. {% data reusables.enterprise-accounts.emu-more-info-account %} + {% note %} **注：** {% data variables.product.company_short %} 会限制在 24 小时内可受邀参加仓库的人数。 如果您超过此限制，请等待 24 小时后再邀请，或者创建一个组织以与更多的人协作。 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-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md index 6e0b220bc8..01c894eeb0 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-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md @@ -18,7 +18,9 @@ shortTitle: 添加电子邮件地址 {% note %} -**注**：{% data reusables.user_settings.no-verification-disposable-emails %} +**注意**： + - {% data reusables.user_settings.no-verification-disposable-emails %} + - If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you cannot make changes to your email address on {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.emu-more-info-account %} {% endnote %} 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/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md index 1a9b7c29c9..18cfbaa7df 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/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md @@ -31,6 +31,12 @@ If you do not hold a trademark for the name, you can choose another username or - 使用旧用户名的[@提及](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) - 包含旧用户名的 [gists](/articles/creating-gists) 链接 +{% ifversion fpt %} + +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 %} + ## 仓库引用 您更改用户名后，{% 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/index.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md index b88970ba0c..328ecae6ef 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-github-user-account/managing-user-account-settings/index.md @@ -15,6 +15,7 @@ topics: children: - /about-your-personal-dashboard - /managing-your-theme-settings + - /managing-your-tab-size-rendering-preference - /changing-your-github-username - /merging-multiple-user-accounts - /converting-a-user-into-an-organization diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md new file mode 100644 index 0000000000..990c2e2442 --- /dev/null +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md @@ -0,0 +1,15 @@ +--- +title: Managing your tab size rendering preference +intro: You can manage the number of spaces a tab is equal to for your user account. +versions: + fpt: '*' +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. 在用户设置侧边栏中，单击 **Appearance（外观）**。 ![用户设置侧边栏中的"外观"选项卡](/assets/images/help/settings/appearance-tab.png) +2. Under "Tab size preference", select the drop-down menu and choose your preference. ![Tab size preference button](/assets/images/help/settings/tab-size-preference.png) diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md index 590bfe31a6..48f328b1f8 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md @@ -3,6 +3,7 @@ title: 管理主题设置 intro: '通过设置主题首选项以遵循系统设置或始终使用浅色模式或深色模式，您可以管理 {% data variables.product.product_name %} 的外观，' versions: fpt: '*' + ghae: next ghes: '>=3.2' topics: - Accounts @@ -14,7 +15,15 @@ shortTitle: 管理主题设置 为了选择和灵活地使用 {% data variables.product.product_name %}，您可以配置主题设置来更改 {% data variables.product.product_name %} 的外观。 您可以在浅色和深色两个主题中进行选择，也可以配置 {% data variables.product.product_name %} 遵循系统设置。 -您可能希望使用深色主题来降低某些设备的功耗，在低光条件下减少眼睛应变，或者因为您更喜欢主题的外观。{% ifversion fpt or ghae-issue-4618 %} 视力障碍者可能受益于深色高对比度主题，前景和背景元素之间的对比度更大。{% endif %} +您可能需要使用深色主题来减少某些设备的功耗，以在低光条件下减小眼睛的压力，或者因为您更喜欢主题的外观。 + +{% ifversion fpt or ghae-issue-4618 %} 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 %} If you have colorblindness, you may benefit from our light and dark colorblind themes. + +{% note %} + +**Note:** The colorblind themes are currently in public beta. For more information on enabling features in public beta, see "[Exploring early access releases with feature preview](/get-started/using-github/exploring-early-access-releases-with-feature-preview)." + +{% endnote %}{% endif %} {% data reusables.user_settings.access_settings %} 1. 在用户设置侧边栏中，单击 **Appearance（外观）**。 ![用户设置侧边栏中的"外观"选项卡](/assets/images/help/settings/appearance-tab.png) @@ -24,6 +33,8 @@ shortTitle: 管理主题设置 {% ifversion fpt or ghae-issue-4618 %}![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 ghae-issue-4618 %}![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 ghae-issue-4619 %} + - 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/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-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md index 65c4721d85..d95e2c1182 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-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md @@ -35,7 +35,7 @@ shortTitle: 权限用户仓库 | {% ifversion fpt %}邀请协作者{% else %}添加协作者{% endif %} | | | "[邀请个人仓库的协作者](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)" | | | 更改仓库的可见性 | “[设置仓库可见性](/github/administering-a-repository/setting-repository-visibility)” |{% ifversion fpt %} -| 限制与仓库的交互 | “[限制仓库中的交互](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)”|{% endif %}{% ifversion fpt or ghes > 3.0 %} +| 限制与仓库的交互 | “[限制仓库中的交互](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)”|{% endif %}{% ifversion fpt or ghes > 3.0 or ghae-next %} | 重命名分支，包括默认分支 | "[重命名分支](/github/administering-a-repository/renaming-a-branch)" {% endif %} | 合并受保护分支上的拉取请求（即使没有批准审查） | "[关于受保护分支](/github/administering-a-repository/about-protected-branches)" | @@ -73,7 +73,7 @@ shortTitle: 权限用户仓库 | 操作 | 更多信息 | |:--------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| 复刻仓库 | "[关于复刻](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% ifversion fpt or ghes > 3.1 %} +| 复刻仓库 | "[关于复刻](/github/collaborating-with-issues-and-pull-requests/about-forks)" |{% ifversion fpt or ghes > 3.1 or ghae-next %} | 重命名除默认分支以外的分支 | "[重命名分支](/github/administering-a-repository/renaming-a-branch)" {% endif %} | 在仓库中创建、编辑和删除关于提交、拉取请求和议题的评论 |
    • "[关于议题](/github/managing-your-work-on-github/about-issues)"
    • "[评论拉取请求](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request)"
    • "[管理破坏性评论](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"
    | diff --git a/translations/zh-CN/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md b/translations/zh-CN/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md index 237aacb702..57273e5ad0 100644 --- a/translations/zh-CN/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md +++ b/translations/zh-CN/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md @@ -15,8 +15,6 @@ topics: - Workflows --- -{% data reusables.actions.ae-beta %} - ## 关于缓存工作流程依赖项 工作流程运行通常在不同运行之间重新使用相同的输出或下载的依赖项。 例如，Maven、Gradle、npm 和 Yarn 等软件包和依赖项管理工具都会对下载的依赖项保留本地缓存。 diff --git a/translations/zh-CN/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md b/translations/zh-CN/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md index b1a3567bf2..1e6bd7203b 100644 --- a/translations/zh-CN/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md +++ b/translations/zh-CN/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md @@ -20,11 +20,10 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 关于工作流程构件 -构件允许您在作业完成后保留数据，并与同一工作流程中的另一个作业共享该数据。 构件是指在工作流程运行过程中产生的文件或文件集。 例如，在工作流程运行结束后，您可以使用构件保存您的构建和测试输出。 +构件允许您在作业完成后保留数据，并与同一工作流程中的另一个作业共享该数据。 构件是指在工作流程运行过程中产生的文件或文件集。 例如，在工作流程运行结束后，您可以使用构件保存您的构建和测试输出。 {% data reusables.actions.reusable-workflow-artifacts %} {% data reusables.github-actions.artifact-log-retention-statement %} 每当有人向拉取请求推送新提交时，拉取请求的保留期将重新开始。 diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/about-continuous-integration.md b/translations/zh-CN/content/actions/automating-builds-and-tests/about-continuous-integration.md index 73fc6ed147..1ea6e3f192 100644 --- a/translations/zh-CN/content/actions/automating-builds-and-tests/about-continuous-integration.md +++ b/translations/zh-CN/content/actions/automating-builds-and-tests/about-continuous-integration.md @@ -1,6 +1,6 @@ --- title: 关于持续集成 -intro: '您可以直接在 {% data variables.product.prodname_dotcom %} 仓库中通过 {% data variables.product.prodname_actions %} 创建自定义持续集成 (CI) 和持续部署 (CD) 工作流程。' +intro: 'You can create custom continuous integration (CI) workflows directly in your {% data variables.product.prodname_dotcom %} repository with {% data variables.product.prodname_actions %}.' product: '{% data reusables.gated-features.actions %}' redirect_from: - /articles/about-continuous-integration @@ -15,13 +15,11 @@ versions: type: overview topics: - CI - - CD shortTitle: 持续集成 --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 关于持续集成 @@ -49,45 +47,12 @@ shortTitle: 持续集成 有关常用术语的定义，请参阅“[{% data variables.product.prodname_actions %} 的核心概念](/github/automating-your-workflow-with-github-actions/core-concepts-for-github-actions)”。 -## 支持的语言 - +## Workflow templates {% data variables.product.product_name %} 提供各种不同语言和框架的 CI 工作流程模板。 在 {% ifversion fpt %}[actions/starter-workflows](https://github.com/actions/starter-workflows/tree/main/ci) 仓库{% else %}{% data variables.product.product_location %} 上的 `actions/starter-workflows` 仓库{% endif %}中浏览 {% data variables.product.product_name %} 提供的 CI 工作流程模板的完整列表。 -{% ifversion fpt or ghes > 3.0 or ghae-next %} -## 跳过工作流程运行 - -如果您想暂时阻止触发工作流程，可以对提交消息添加跳过指令。 本来会触发 `on: push` 或 `on: pull_request` 的工作流程，如果您将以下任何字符串添加到推送中的提交消息或者拉取请求的 HEAD 提交，则不会触发： - -* `[skip ci]` -* `[ci skip]` -* `[no ci]` -* `[skip actions]` -* `[actions skip]` - -或者，您也可以使用两个空行后接 `skip-checks: true` 或 `skip-checks:true` 来结束提交消息。 - -如果您的仓库配置为需要先通过特定检查，则无法合并拉取请求。 要允许合并拉取请求，您可以将新提交推送到拉取请求，而无需提交消息中的跳过指令。 - -{% note %} - -**注意：**跳过指令仅适用于 `push` 和 `pull_request` 事件。 例如，将 `[skip ci]` 添加到提交消息不会停止触发 `on: pull_request_target` 的工作流程运行。 - -{% endnote %} -{% endif %} - -## 工作流程运行通知 - -{% data reusables.repositories.workflow-notifications %} - -## 工作流程运行的状态徽章 - -{% data reusables.repositories.actions-workflow-status-badge-intro %} - -更多信息请参阅“[添加工作流程状态徽章](/actions/managing-workflow-runs/adding-a-workflow-status-badge)”。 - ## 延伸阅读 {% ifversion fpt %} diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md index 3ff8ab835b..87d26afc95 100644 --- a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md +++ b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md @@ -19,7 +19,6 @@ shortTitle: 构建和测试 Java & Ant {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 简介 diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md index 69de954387..ebe9ad6dfe 100644 --- a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md +++ b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md @@ -19,7 +19,6 @@ shortTitle: 构建和测试 Java & Gradle {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 简介 diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md index a2a9d2c7d8..d8e96f557a 100644 --- a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md +++ b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md @@ -19,7 +19,6 @@ shortTitle: 使用 Maven 构建和测试 Java {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 简介 diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-net.md b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-net.md index f1da5387fa..c109ee9547 100644 --- a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-net.md +++ b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-net.md @@ -13,7 +13,6 @@ shortTitle: Build & test .NET {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 简介 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 93e81cfeda..50af9d7c0c 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 @@ -22,7 +22,6 @@ hasExperimentalAlternative: true {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 简介 diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-powershell.md b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-powershell.md index 2192858695..aa12a4f62c 100644 --- a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-powershell.md +++ b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-powershell.md @@ -19,7 +19,6 @@ shortTitle: 构建和测试 PowerShell {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-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 e9a14705f4..738150f3f0 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 @@ -21,7 +21,6 @@ hasExperimentalAlternative: true {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 简介 diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-ruby.md b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-ruby.md index 90cdafebea..8ed2b60a24 100644 --- a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-ruby.md +++ b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-ruby.md @@ -17,7 +17,6 @@ shortTitle: Build & test Ruby {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 简介 diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-swift.md b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-swift.md index a89f4f88f4..4c93bd0f05 100644 --- a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-swift.md +++ b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-swift.md @@ -17,7 +17,6 @@ shortTitle: 构建和测试 Swift {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 简介 diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md index a1d0fe93ca..2d519e198f 100644 --- a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md +++ b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md @@ -21,7 +21,6 @@ shortTitle: 构建和测试 Xamarin 应用程序 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 简介 diff --git a/translations/zh-CN/content/actions/creating-actions/about-custom-actions.md b/translations/zh-CN/content/actions/creating-actions/about-custom-actions.md index 9af99068af..0642e98184 100644 --- a/translations/zh-CN/content/actions/creating-actions/about-custom-actions.md +++ b/translations/zh-CN/content/actions/creating-actions/about-custom-actions.md @@ -20,7 +20,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About custom actions @@ -36,11 +35,11 @@ topics: 您可以创建 Docker 容器和 JavaScript 操作。 操作需要元数据文件来定义操作的输入、输出和主要进入点。 元数据文件名必须是 `action.yml` 或 `action.yaml`。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的元数据语法](/articles/metadata-syntax-for-github-actions)”。 -| 类型 | 操作系统 | -| ----------------- | ------------------- | -| Docker 容器 | Linux | -| JavaScript | Linux、macOS、Windows | -| Composite Actions | Linux、macOS、Windows | +| 类型 | 操作系统 | +| ---------- | ------------------- | +| Docker 容器 | Linux | +| JavaScript | Linux、macOS、Windows | +| 复合操作 | Linux、macOS、Windows | ### Docker 容器操作 @@ -58,9 +57,9 @@ JavaScript 操作可以直接在运行器计算机上运行，并将操作代码 如果您正在开发 Node.js 项目，{% data variables.product.prodname_actions %} 工具包提供可用于项目中加速开发的软件包。 更多信息请参阅 [actions/toolkit](https://github.com/actions/toolkit) 仓库。 -### Composite Actions +### 复合操作 -A _composite_ action allows you to combine multiple workflow steps within one action. For example, you can use this feature to bundle together multiple run commands into an action, and then have a workflow that executes the bundled commands as a single step using that action. To see an example, check out "[Creating a composite action](/actions/creating-actions/creating-a-composite-action)". +_复合_操作允许您在一个操作中组合多个工作流程步骤。 例如，您可以使用此功能将多个运行命令捆绑到一个操作中，然后获得使用该操作在单一步骤中执行捆绑命令的工作流程。 要看到示例，请参阅“[创建复合操作](/actions/creating-actions/creating-a-composite-action)”。 ## 选择操作的位置 @@ -152,7 +151,7 @@ steps: ### GitHub Actions 和 GitHub 应用程序的设置 -While both {% data variables.product.prodname_actions %} and {% data variables.product.prodname_github_apps %} provide ways to build automation and workflow tools, they each have strengths that make them useful in different ways. +尽管 {% data variables.product.prodname_actions %} 和 {% data variables.product.prodname_github_apps %} 都提供了构建自动化和工作流程工具的方法，但它们各有优点，使其以不同的方式发挥作用。 {% data variables.product.prodname_github_apps %}： * 持续运行并且能够对事件迅速做出反应。 diff --git a/translations/zh-CN/content/actions/creating-actions/creating-a-composite-action.md b/translations/zh-CN/content/actions/creating-actions/creating-a-composite-action.md index 193a41d373..59e72f2323 100644 --- a/translations/zh-CN/content/actions/creating-actions/creating-a-composite-action.md +++ b/translations/zh-CN/content/actions/creating-actions/creating-a-composite-action.md @@ -16,7 +16,6 @@ shortTitle: Composite action {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 简介 diff --git a/translations/zh-CN/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/zh-CN/content/actions/creating-actions/creating-a-docker-container-action.md index ff133e3aee..a1d84caf00 100644 --- a/translations/zh-CN/content/actions/creating-actions/creating-a-docker-container-action.md +++ b/translations/zh-CN/content/actions/creating-actions/creating-a-docker-container-action.md @@ -20,7 +20,6 @@ shortTitle: Docker 容器操作 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 简介 diff --git a/translations/zh-CN/content/actions/creating-actions/creating-a-javascript-action.md b/translations/zh-CN/content/actions/creating-actions/creating-a-javascript-action.md index feeca2dc43..02024da97a 100644 --- a/translations/zh-CN/content/actions/creating-actions/creating-a-javascript-action.md +++ b/translations/zh-CN/content/actions/creating-actions/creating-a-javascript-action.md @@ -20,7 +20,6 @@ shortTitle: JavaScript 操作 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 简介 @@ -103,7 +102,7 @@ npm install @actions/github 此操作使用工具包获取操作元数据文件中所需的 `who-to-greet` 输入变量，然后在日志的调试消息中打印 "Hello [who-to-greet]"。 接下来，该脚本会获取当前时间并将其设置为作业中稍后运行的操作可以使用的输出变量。 -GitHub 操作提供有关 web 挂钩实践、Git 引用、工作流程、操作和触发工作流程的人员的上下文信息。 要访问上下文信息，您可以使用 `github` 包。 您将编写的操作将打印 web 挂钩事件有效负载日志。 +GitHub Actions 提供有关 web 挂钩实践、Git 引用、工作流程、操作和触发工作流程的人员的上下文信息。 要访问上下文信息，您可以使用 `github` 包。 您将编写的操作将打印 web 挂钩事件有效负载日志。 使用以下代码添加名为 `index.js` 的新文件。 diff --git a/translations/zh-CN/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/translations/zh-CN/content/actions/creating-actions/dockerfile-support-for-github-actions.md index dd671c4bac..f12f9f2c86 100644 --- a/translations/zh-CN/content/actions/creating-actions/dockerfile-support-for-github-actions.md +++ b/translations/zh-CN/content/actions/creating-actions/dockerfile-support-for-github-actions.md @@ -1,6 +1,6 @@ --- title: Dockerfile 对 GitHub Actions 的支持 -shortTitle: Dockerfile support +shortTitle: Dockerfile 支持 intro: 为 Docker 容器创建 `Dockerfile` 时， 您应该知道一些 Docker 指令如何与 GitHub Actions 及操作的元数据文件交互。 product: '{% data reusables.gated-features.actions %}' redirect_from: @@ -14,7 +14,6 @@ type: reference {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 关于 Dockerfile 指令 @@ -22,7 +21,7 @@ type: reference ## Dockerfile 指令和覆盖 -某些 Docker 指令与 GitHub 操作交互，操作的元数据文件可以覆盖某些 Docker 指令。 确保您熟悉 Dockerfile 如何与 {% data variables.product.prodname_actions %} 交互以防止任何意外行为。 +某些 Docker 指令与 GitHub Actions 交互，操作的元数据文件可以覆盖某些 Docker 指令。 确保您熟悉 Dockerfile 如何与 {% data variables.product.prodname_actions %} 交互以防止任何意外行为。 ### USER diff --git a/translations/zh-CN/content/actions/creating-actions/index.md b/translations/zh-CN/content/actions/creating-actions/index.md index 28430aa7d4..27cbb507de 100644 --- a/translations/zh-CN/content/actions/creating-actions/index.md +++ b/translations/zh-CN/content/actions/creating-actions/index.md @@ -24,4 +24,3 @@ children: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} 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 985b8a0ec6..472abeb71c 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 @@ -17,7 +17,6 @@ type: reference {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 关于 {% data variables.product.prodname_actions %} 的 YAML 语法 @@ -106,7 +105,7 @@ outputs: **必要** 输出参数的 `string` 描述。 -## `outputs` for composite actions +## 用于复合操作的 `outputs` **可选** `outputs` 使用与 `outputs.` 及 `outputs..description` 相同的参数（请参阅“用于 {% data variables.product.prodname_actions %} 的 @@ -141,7 +140,7 @@ runs: **必要** 输出参数将会映射到的值。 您可以使用上下文将此设置为 `string` 或表达式。 例如，您可以使用 `steps` 上下文将输出的 `value` 设置为步骤的输出值。 -For more information on how to use context syntax, see "[Contexts](/actions/learn-github-actions/contexts)." +有关如何使用上下文语法的更多信息，请参阅“[上下文](/actions/learn-github-actions/contexts)”。 @@ -247,7 +246,7 @@ runs: -## `runs` for composite actions +## 用于复合操作的 `runs` **必要** 配置组合操作的路径和用于执行代码的应用程序。 @@ -255,7 +254,7 @@ runs: ### `runs.using` -**Required** To use a composite action, set this to `"composite"`. +**必要** 要使用复合操作，请将此设置为 `"composite"`。 @@ -264,11 +263,11 @@ runs: {% ifversion fpt or ghes > 3.2 or ghae-issue-4853 %} -**Required** The steps that you plan to run in this action. These can be either `run` steps or `uses` steps. +**必要** 您计划在此操作中的步骤。 这些步骤可以是 `run` 步骤或 `uses` 步骤。 {% else %} -**Required** The steps that you plan to run in this action. +**必要** 您计划在此操作中的步骤。 {% endif %} @@ -279,7 +278,7 @@ runs: {% ifversion fpt or ghes > 3.2 or ghae-issue-4853 %} -**Optional** The command you want to run. 这可以是内联的，也可以是操作仓库中的脚本： +**可选** 您想要运行的命令。 这可以是内联的，也可以是操作仓库中的脚本： {% else %} @@ -323,11 +322,11 @@ runs: {% ifversion fpt or ghes > 3.2 or ghae-issue-4853 %} -**Optional** The shell where you want to run the command. 您可以使用[这里](/actions/reference/workflow-syntax-for-github-actions#using-a-specific-shell)列出的任何 shell。 Required if `run` is set. +**可选** 您想要在其中运行命令的 shell。 您可以使用[这里](/actions/reference/workflow-syntax-for-github-actions#using-a-specific-shell)列出的任何 shell。 如果设置了 `run`，则必填。 {% else %} -**必要** 您想要在其中运行命令的 shell。 您可以使用[这里](/actions/reference/workflow-syntax-for-github-actions#using-a-specific-shell)列出的任何 shell。 Required if `run` is set. +**必要** 您想要在其中运行命令的 shell。 您可以使用[这里](/actions/reference/workflow-syntax-for-github-actions#using-a-specific-shell)列出的任何 shell。 如果设置了 `run`，则必填。 {% endif %} @@ -335,7 +334,7 @@ runs: #### `runs.steps[*].name` -**Optional** The name of the composite step. +**可选** 复合步骤的名称。 @@ -347,7 +346,7 @@ runs: #### `runs.steps[*].env` -**可选** 设置环境变量的 `map` 仅用于该步骤。 If you want to modify the environment variable stored in the workflow, use {% ifversion fpt or ghes > 2.22 or ghae %}`echo "{name}={value}" >> $GITHUB_ENV`{% else %}`echo "::set-env name={name}::{value}"`{% endif %} in a composite step. +**可选** 设置环境变量的 `map` 仅用于该步骤。 如果要修改工作流程中存储的环境变量，请在复合步骤中使用 {% ifversion fpt or ghes > 2.22 or ghae %}`echo "{name}={value}" >> $GITHUB_ENV`{% else %}`echo "::set-env name={name}::{value}"`{% endif %}。 @@ -360,7 +359,7 @@ runs: #### `runs.steps[*].uses` -**Optional** Selects an action to run as part of a step in your job. 操作是一种可重复使用的代码单位。 您可以使用工作流程所在仓库中、公共仓库中或[发布 Docker 容器映像](https://hub.docker.com/)中定义的操作。 +**可选** 选择作为作业步骤一部分运行的操作。 操作是一种可重复使用的代码单位。 您可以使用工作流程所在仓库中、公共仓库中或[发布 Docker 容器映像](https://hub.docker.com/)中定义的操作。 强烈建议指定 Git ref、SHA 或 Docker 标记编号来包含所用操作的版本。 如果不指定版本，在操作所有者发布更新时可能会中断您的工作流程或造成非预期的行为。 @@ -399,7 +398,7 @@ runs: #### `runs.steps[*].with` -**Optional** A `map` of the input parameters defined by the action. 每个输入参数都是一个键/值对。 输入参数被设置为环境变量。 The variable is prefixed with INPUT_ and converted to upper case. +**可选** 输入参数的 `map` 由操作定义。 每个输入参数都是一个键/值对。 输入参数被设置为环境变量。 该变量的前缀为 INPUT_，并转换为大写。 diff --git a/translations/zh-CN/content/actions/creating-actions/publishing-actions-in-github-marketplace.md b/translations/zh-CN/content/actions/creating-actions/publishing-actions-in-github-marketplace.md index b981652313..fe70cd4c28 100644 --- a/translations/zh-CN/content/actions/creating-actions/publishing-actions-in-github-marketplace.md +++ b/translations/zh-CN/content/actions/creating-actions/publishing-actions-in-github-marketplace.md @@ -12,8 +12,6 @@ type: how_to shortTitle: 在 GitHub Marketplace 中发布 --- -{% data reusables.actions.ae-beta %} - 您必须接受服务条款才能在 {% data variables.product.prodname_marketplace %} 中发布操作。 ## 关于发布操作 diff --git a/translations/zh-CN/content/actions/creating-actions/setting-exit-codes-for-actions.md b/translations/zh-CN/content/actions/creating-actions/setting-exit-codes-for-actions.md index 7c59abe192..6d18e13522 100644 --- a/translations/zh-CN/content/actions/creating-actions/setting-exit-codes-for-actions.md +++ b/translations/zh-CN/content/actions/creating-actions/setting-exit-codes-for-actions.md @@ -14,7 +14,6 @@ type: how_to {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 关于退出代码 diff --git a/translations/zh-CN/content/actions/deployment/about-continuous-deployment.md b/translations/zh-CN/content/actions/deployment/about-continuous-deployment.md new file mode 100644 index 0000000000..8586a36d82 --- /dev/null +++ b/translations/zh-CN/content/actions/deployment/about-continuous-deployment.md @@ -0,0 +1,41 @@ +--- +title: About continuous deployment +intro: 'You can create custom continuous deployment (CD) workflows directly in your {% data variables.product.prodname_dotcom %} repository with {% data variables.product.prodname_actions %}.' +product: '{% data reusables.gated-features.actions %}' +versions: + fpt: '*' + ghes: '*' + ghae: '*' +type: overview +topics: + - CD +shortTitle: Continuous deployment +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +## About continuous deployment + +_Continuous deployment_ (CD) is the practice of using automation to publish and deploy software updates. As part of the typical CD process, the code is automatically built and tested before deployment. + +Continuous deployment is often coupled with continuous integration. For more information about continuous integration, see "[About continuous integration](/actions/guides/about-continuous-integration)". + +## About continuous deployment using {% data variables.product.prodname_actions %} + +You can set up a {% data variables.product.prodname_actions %} workflow to deploy your software product. To verify that your product works as expected, your workflow can build the code in your repository and run your tests before deploying. + +You can configure your CD workflow to run when a {% data variables.product.product_name %} event occurs (for example, when new code is pushed to the default branch of your repository), on a set schedule, manually, or when an external event occurs using the repository dispatch webhook. For more information about when your workflow can run, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)." + +{% data variables.product.prodname_actions %} provides features that give you more control over deployments. For example, you can use environments to require approval for a job to proceed, restrict which branches can trigger a workflow, or limit access to secrets. You can use concurrency to limit your CD pipeline to a maximum of one in-progress deployment and one pending deployment. For more information about these features, see "[Deploying with GitHub Actions](/actions/deployment/deploying-with-github-actions)" and "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." + +## Workflow templates and third party actions + +{% data reusables.actions.cd-templates-actions %} + +## 延伸阅读 + +- [Deploying with GitHub Actions](/actions/deployment/deploying-with-github-actions) +- [Using environments for deployment](/actions/deployment/using-environments-for-deployment){% ifversion fpt %} +- "[管理 {% data variables.product.prodname_actions %} 的计费](/billing/managing-billing-for-github-actions)" +{% endif %} diff --git a/translations/zh-CN/content/actions/deployment/deploying-to-amazon-elastic-container-service.md b/translations/zh-CN/content/actions/deployment/deploying-to-amazon-elastic-container-service.md index 74b2df1311..aa59007a33 100644 --- a/translations/zh-CN/content/actions/deployment/deploying-to-amazon-elastic-container-service.md +++ b/translations/zh-CN/content/actions/deployment/deploying-to-amazon-elastic-container-service.md @@ -18,11 +18,10 @@ shortTitle: 部署到 Amazon ECS {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 简介 -本指南介绍如何使用 {% data variables.product.prodname_actions %} 构建容器化应用程序，将其推送到 [Amazon Elastic Container Registry (ECR)](https://aws.amazon.com/ecr/)，以及将其部署到 [Amazon Elastic Container Service (ECS)](https://aws.amazon.com/ecs/)。 +This guide explains how to use {% data variables.product.prodname_actions %} to build a containerized application, push it to [Amazon Elastic Container Registry (ECR)](https://aws.amazon.com/ecr/), and deploy it to [Amazon Elastic Container Service (ECS)](https://aws.amazon.com/ecs/) when a release is created. 在 {% data variables.product.company_short %} 仓库的每个新版本上，{% data variables.product.prodname_actions %} 工作流程将生成新的容器映像并将其推送到 Amazon ECR，然后将新的任务定义部署到 Amazon ECS。 @@ -66,6 +65,8 @@ shortTitle: 部署到 Amazon ECS See the documentation for each action used below for the recommended IAM policies for the IAM user, and methods for handling the access key credentials. +5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %} + ## Creating the workflow Once you've completed the prerequisites, you can proceed with creating the workflow. @@ -74,6 +75,8 @@ The following example workflow demonstrates how to build a container image and p Ensure that you provide your own values for all the variables in the `env` key of the workflow. +{% data reusables.actions.delete-env-key %} + ```yaml{:copy} {% data reusables.actions.actions-not-certified-by-github-comment %} @@ -93,17 +96,11 @@ env: CONTAINER_NAME: MY_CONTAINER_NAME # set this to the name of the container in the # containerDefinitions section of your task definition -defaults: - run: - shell: bash - jobs: deploy: name: Deploy - runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae-next %} - permissions: - packages: write - contents: read{% endif %} + runs-on: ubuntu-latest + environment: production {% raw %}steps: - name: Checkout @@ -150,9 +147,10 @@ jobs: wait-for-service-stability: true{% endraw %} ``` - ## 其他资源 +For the original starter workflow, see [`aws.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/aws.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository. + 有关这些示例中使用的服务的详细信息，请参阅以下文档： * Amazon AWS 文档中的“[IAM 中的安全最佳实践](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html)”。 diff --git a/translations/zh-CN/content/actions/deployment/deploying-to-azure-app-service.md b/translations/zh-CN/content/actions/deployment/deploying-to-azure-app-service.md index b861bc127f..4e57b41803 100644 --- a/translations/zh-CN/content/actions/deployment/deploying-to-azure-app-service.md +++ b/translations/zh-CN/content/actions/deployment/deploying-to-azure-app-service.md @@ -18,7 +18,6 @@ shortTitle: 部署到 Azure App Service {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 简介 @@ -68,13 +67,19 @@ Azure App Service 可以用几种语言运行 web 应用程序，但本指南演 在 {% data variables.product.prodname_dotcom %} 仓库中，创建一个名为 `AZURE_WEBAPP_PUBLISH_PROFILE` 的机密，其中包含发布配置文件的内容。 有关创建机密的更多信息，请参阅“[加密密码](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)”。 +4. For Linux apps, add an app setting called `WEBSITE_WEBDEPLOY_USE_SCM` and set it to true in your app. For more information, see "[Configure apps in the portal](https://docs.microsoft.com/en-us/azure/app-service/configure-common#configure-app-settings)" in the Azure documentation. + +5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %} + ## 创建工作流程 完成先决条件后，可以继续创建工作流程。 -下面的示例工作流程演示如何生成、测试 Node.js 项目并将其部署到 Azure App Service。 +The following example workflow demonstrates how to build, test, and deploy the Node.js project to Azure App Service when a release is created. -确保在工作流程 `env` 中将 `AZURE_WEBAPP_NAME` 密钥设置为您创建的 web 应用程序名称。 +确保在工作流程 `env` 中将 `AZURE_WEBAPP_NAME` 密钥设置为您创建的 web 应用程序名称。 You can also change `AZURE_WEBAPP_PACKAGE_PATH` if the path to your project is not the repository root and `NODE_VERSION` if you want to use a node version other than `10.x`. + +{% data reusables.actions.delete-env-key %} ```yaml{:copy} {% data reusables.actions.actions-not-certified-by-github-comment %} @@ -92,6 +97,8 @@ jobs: build-and-deploy: name: Build and Deploy runs-on: ubuntu-latest + environment: production + steps: - uses: actions/checkout@v2 @@ -122,4 +129,5 @@ jobs: * For the original starter workflow, see [`azure.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository. * 用于部署 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. * Azure web 应用文档中的“[在 Azure 中创建 Node.js web 应用](https://docs.microsoft.com/en-us/azure/app-service/quickstart-nodejs)”快速入门说明如何通过 [Azure App Service 扩展](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azureappservice)使用 VS Code。 diff --git a/translations/zh-CN/content/actions/deployment/deploying-to-google-kubernetes-engine.md b/translations/zh-CN/content/actions/deployment/deploying-to-google-kubernetes-engine.md index ff799fc5b0..d290b3638c 100644 --- a/translations/zh-CN/content/actions/deployment/deploying-to-google-kubernetes-engine.md +++ b/translations/zh-CN/content/actions/deployment/deploying-to-google-kubernetes-engine.md @@ -13,16 +13,15 @@ topics: - CD - Containers - Google Kubernetes Engine -shortTitle: 部署到 Kubernetes (GKE) +shortTitle: Deploy to Google Kubernetes Engine --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 简介 -本指南介绍如何使用 {% data variables.product.prodname_actions %} 构建容器化应用程序，将其推送到 Google Container Registry (GCR)，以及将其部署到 Google Kubernetes Engine (GKE)。 +This guide explains how to use {% data variables.product.prodname_actions %} to build a containerized application, push it to Google Container Registry (GCR), and deploy it to Google Kubernetes Engine (GKE) when a release is created. GKE 是 Google Cloud 的托管 Kubernetes 群集服务，可以在云中或您自己的数据中心中托管您的容器化工作负载。 更多信息请参阅 [Google Kubernetes Engine](https://cloud.google.com/kubernetes-engine)。 @@ -61,7 +60,7 @@ $ gcloud services enable \ ### 配置服务帐户并存储其凭据 -此程序显示如何为您的 GKE 集成创建服务帐户。 它说明了如何创建帐户、向其添加角色、检索其密钥，以及将它们存储为名为 `GKE_SA_KEY`、以 base64 编码的[加密仓库机密](/actions/reference/encrypted-secrets)。 +此程序显示如何为您的 GKE 集成创建服务帐户。 It explains how to create the account, add roles to it, retrieve its keys, and store them as a base64-encoded encrypted repository secret named `GKE_SA_KEY`. 1. 创建新服务帐户： {% raw %} @@ -97,16 +96,29 @@ $ gcloud services enable \ $ export GKE_SA_KEY=$(cat key.json | base64) ``` {% endraw %} + For more information about how to store a secret, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)." + +### Storing your project name + +Store the name of your project as a secret named `GKE_PROJECT`. For more information about how to store a secret, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)." ### （可选）配置 kustomize Kustomize 是用于管理 YAML 规范的可选工具。 在创建 _kustomization_ 文件之后， 下面的工作流可用于将结果中的图像和管道字段动态设置为 `kubectl`。 更多信息请参阅 [kustomize 的用法](https://github.com/kubernetes-sigs/kustomize#usage)。 +### (Optional) Configure a deployment environment + +{% data reusables.actions.about-environments %} + ## 创建工作流程 完成先决条件后，可以继续创建工作流程。 下面的示例工作流程演示如何生成容器映像并推送到 GCR。 然后，它使用 Kubernetes 工具（如 `kubectl` 和 `kustomize`）将映像拉入群集部署。 +Under the `env` key, change the value of `GKE_CLUSTER` to the name of your cluster, `GKE_ZONE` to your cluster zone, `DEPLOYMENT_NAME` to the name of your deployment, and `IMAGE` to the name of your image. + +{% data reusables.actions.delete-env-key %} + ```yaml{:copy} {% data reusables.actions.actions-not-certified-by-github-comment %} @@ -127,8 +139,9 @@ jobs: setup-build-publish-deploy: name: Setup, Build, Publish, and Deploy runs-on: ubuntu-latest - steps: + environment: production + steps: - name: Checkout uses: actions/checkout@v2 @@ -138,7 +151,8 @@ jobs: service_account_key: {% raw %}${{ secrets.GKE_SA_KEY }}{% endraw %} project_id: {% raw %}${{ secrets.GKE_PROJECT }}{% endraw %} - # Configure docker to use the gcloud command-line tool as a credential helper + # Configure Docker to use the gcloud command-line tool as a credential + # helper for authentication - run: |- gcloud --quiet auth configure-docker @@ -166,7 +180,7 @@ jobs: # Set up kustomize - name: Set up Kustomize run: |- - curl --location https://github.com/kubernetes-sigs/kustomize/releases/download/kustomize%2Fv4.2.0/kustomize_v4.2.0_linux_amd64.tar.gz | tar xz + curl -sfLo kustomize https://github.com/kubernetes-sigs/kustomize/releases/download/v3.1.0/kustomize_3.1.0_linux_amd64 chmod u+x ./kustomize # Deploy the Docker image to the GKE cluster diff --git a/translations/zh-CN/content/actions/deployment/deploying-with-github-actions.md b/translations/zh-CN/content/actions/deployment/deploying-with-github-actions.md new file mode 100644 index 0000000000..e00eb619ea --- /dev/null +++ b/translations/zh-CN/content/actions/deployment/deploying-with-github-actions.md @@ -0,0 +1,173 @@ +--- +title: Deploying with GitHub Actions +intro: Learn how to control deployments with features like environments and concurrency. +product: '{% data reusables.gated-features.actions %}' +versions: + fpt: '*' + ghes: '>=3.1' + ghae: '*' +type: overview +topics: + - CD +shortTitle: Deploy with GitHub Actions +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +## 简介 + +{% data variables.product.prodname_actions %} offers features that let you control deployments. 您可以: + +- 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)." + +## 基本要求 + +You should be familiar with the syntax for {% 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`, `release`, and `workflow_dispatch`. + +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. +- A release is created. +- Someone manually triggers it. + +```yaml +on: + push: + branches: + - main + pull_request: + branches: + - main + release: + types: + - created + workflow_dispatch: +``` + +更多信息请参阅“[触发工作流程的事件](/actions/reference/events-that-trigger-workflows)”。 + +## 使用环境 + +{% data reusables.actions.about-environments %} + +## Using concurrency + +Concurrency 确保只有使用相同并发组的单一作业或工作流程才会同时运行。 您可以使用并发，以便环境中每次最多有一个正在进行的部署和一个待处理的部署。 + +{% 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. + +{% 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. + +```yaml +name: Deployment + +concurrency: production + +on: + push: + branches: + - main + +jobs: + deployment: + runs-on: ubuntu-latest + environment: production + steps: + - name: deploy + # ...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`. + +```yaml +name: Deployment + +on: + push: + branches: + - main + +jobs: + deployment: + runs-on: ubuntu-latest + environment: production + concurrency: production + steps: + - name: deploy + # ...deployment-specific steps +``` + +You can also use `cancel-in-progress` to cancel any currently running job or workflow in the same concurrency group. + +```yaml +name: Deployment + +concurrency: + group: production + cancel-in-progress: true + +on: + push: + branches: + - main + +jobs: + deployment: + runs-on: ubuntu-latest + environment: production + steps: + - name: deploy + # ...deployment-specific steps +``` + +## 查看部署历史记录 + +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)." + +## Monitoring workflow runs + +每个工作流程运行都会生成一个实时图表，说明运行进度。 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)." + +You can also view the logs of each workflow run and the history of workflow runs. 更多信息请参阅“[查看工作流程运行历史记录](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)”。 + +## Tracking deployments through apps + +{% ifversion fpt %} +If your {% data variables.product.product_name %} personal account or organization 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)." +{% 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)." + +{% ifversion fpt or ghes %} + +## 选择运行器 + +You can run your deployment workflow on {% data variables.product.product_name %}-hosted runners or on self-hosted runners. Traffic from {% data variables.product.product_name %}-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.product_name %}-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)." + +{% 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 %} + +更多信息请参阅“[添加工作流程状态徽章](/actions/managing-workflow-runs/adding-a-workflow-status-badge)”。 + +## 后续步骤 + +This article demonstrated features of {% data variables.product.prodname_actions %} that you can add to your deployment workflows. + +{% data reusables.actions.cd-templates-actions %} diff --git a/translations/zh-CN/content/actions/deployment/index.md b/translations/zh-CN/content/actions/deployment/index.md index 3c2688e4eb..92ff4c9791 100644 --- a/translations/zh-CN/content/actions/deployment/index.md +++ b/translations/zh-CN/content/actions/deployment/index.md @@ -7,10 +7,13 @@ versions: ghes: '*' ghae: '*' children: + - /about-continuous-deployment + - /deploying-with-github-actions + - /using-environments-for-deployment + - /viewing-deployment-history - /deploying-to-amazon-elastic-container-service - /deploying-to-azure-app-service - /deploying-to-google-kubernetes-engine - /installing-an-apple-certificate-on-macos-runners-for-xcode-development - - /environments --- diff --git a/translations/zh-CN/content/actions/deployment/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md b/translations/zh-CN/content/actions/deployment/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md index 093ccc60ef..d785f0eacf 100644 --- a/translations/zh-CN/content/actions/deployment/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md +++ b/translations/zh-CN/content/actions/deployment/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md @@ -17,7 +17,6 @@ shortTitle: 签名 Xcode 应用程序 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 简介 diff --git a/translations/zh-CN/content/actions/deployment/using-environments-for-deployment.md b/translations/zh-CN/content/actions/deployment/using-environments-for-deployment.md new file mode 100644 index 0000000000..67ecc5e72c --- /dev/null +++ b/translations/zh-CN/content/actions/deployment/using-environments-for-deployment.md @@ -0,0 +1,126 @@ +--- +title: Using environments for deployment +shortTitle: Use environments for deployment +intro: 您可以使用保护规则和机密配置环境。 A workflow job that references an environment must follow any protection rules for the environment before running or accessing the environment's secrets. +product: '{% data reusables.gated-features.environments %}' +miniTocMaxHeadingLevel: 3 +redirect_from: + - /actions/reference/environments + - /actions/deployment/environments +versions: + fpt: '*' + ghes: '>=3.1' + ghae: '*' +--- + + +## 关于环境 + +Environments are used to describe a general deployment target like `production`, `staging`, or `development`. 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)." + +您可以使用保护规则和机密配置环境。 当工作流程引用环境时，作业在环境的所有保护规则通过之前不会开始。 在所有环境保护规则通过之前，作业也不能访问在环境中定义的机密。 + +{% ifversion fpt %} +{% note %} + +**Note:** If you don't use {% data variables.product.prodname_ghe_cloud %} and convert a repository from public to private, any configured protection rules or environment secrets will be ignored, and you will not be able to configure any environments. 如果将仓库转换回公共，您将有权访问以前配置的任何保护规则和环境机密。 {% data reusables.enterprise.link-to-ghec-trial %} + +{% endnote %} +{% endif %} + +## 环境保护规则 + +环境保护规则要求通过特定的条件，然后引用环境的作业才能继续。 {% ifversion fpt or ghae-next or ghes > 3.1 %}您可以使用环境保护规则来要求手动批准、延迟作业或者将环境限于某些分支。{% else %}您可以使用环境保护规则要求手动批准或延迟作业。{% endif %} + +### 需要的审查者 + +使用所需的审查者要求特定人员或团队批准引用环境的工作流程作业。 您最多可以列出六个用户或团队作为审查者。 审查者必须至少具有对仓库的读取访问权限。 只有一个必需的审查者需要批准该作业才能继续。 + +有关与必需审查者一起审查引用环境的作业的详细信息，请参阅“[审查部署](/actions/managing-workflow-runs/reviewing-deployments)”。 + +### 等待计时器 + +在最初触发作业后，使用等待计时器将作业延迟特定时间。 时间（分钟）必须是 0 至 43,200（30天）之间的整数。 + +{% ifversion fpt or ghae-next or ghes > 3.1 %} +### 部署分支 + +使用部署分支来限制哪些分支可以部署到环境中。 以下是环境部署分支的选项： + +* **All branches（所有分支）**：仓库中的所有分支都可以部署到环境。 +* **Protected branches（受保护的分支）**：只有启用分支保护规则的分支才能部署到环境。 如果没有为仓库中的任何分支定义分支保护规则，那么所有分支都可以部署。 有关分支保护规则的更多信息，请参阅“[关于受保护分支](/github/administering-a-repository/about-protected-branches)”。 +* **Selected branches（所选分支）**：只有与指定的名称模式匹配的分支才能部署到环境。 + + 例如，如果您指定 `releases/*` 为部署分支规则，则只有其名称开头为 `releases/` 的分支才能部署到环境。 （通配符字符将不匹配 `/`。 要匹配以 `release/` 开头并且包含额外单一斜杠的分支，请使用 `release/*/*`）。 如果您添加 `main` 作为部署分支规则，则名为 `main` 的分支也可以部署到环境。 有关部署分支的语法选项的更多信息，请参阅 [Ruby File.fnmatch 文档](https://ruby-doc.org/core-2.5.1/File.html#method-c-fnmatch)。 +{% endif %} +## 环境机密 + +存储在环境中的机密仅可用于引用环境的工作流程作业。 如果环境需要批准，作业在所需的审查者批准之前不能访问环境机密。 有关机密的更多信息，请参阅“[加密密码](/actions/reference/encrypted-secrets)”。 + +{% note %} + +**注意：** 在自托管运行器上运行的工作流程不会在一个孤立的容器中运行，即使它们使用环境。 Environment secrets should be treated with the same level of security as repository and organization secrets. 更多信息请参阅“[GitHub Actions 的安全性增强](/actions/learn-github-actions/security-hardening-for-github-actions#hardening-for-self-hosted-runners)”。 + +{% endnote %} + +## 创建环境 + +{% data reusables.github-actions.permissions-statement-environment %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.github-actions.sidebar-environment %} +{% data reusables.github-actions.new-environment %} +{% data reusables.github-actions.name-environment %} +1. Optionally, specify people or teams that must approve workflow jobs that use this environment. + 1. Select **Required reviewers**. + 1. Enter up to 6 people or teams. 只有一个必需的审查者需要批准该作业才能继续。 + 1. Click **Save protection rules**. +2. Optionally, specify the amount of time to wait before allowing workflow jobs that use this environment to proceed. + 1. Select **Wait timer**. + 1. Enter the number of minutes to wait. + 1. Click **Save protection rules**. +3. Optionally, specify what branches can deploy to this environment. For more information about the possible values, see "[Deployment branches](#deployment-branches)." + 1. Select the desired option in the **Deployment branches** dropdown. + 1. If you chose **Selected branches**, enter the branch name patterns that you want to allow. +4. Optionally, add environment secrets. These secrets are only available to workflow jobs that use the environment. Additionally, workflow jobs that use this environment can only access these secrets after any configured rules (for example, required reviewers) pass. 有关机密的更多信息，请参阅“[加密密码](/actions/reference/encrypted-secrets)”。 + 1. Under **Environment secrets**, click **Add Secret**. + 1. Enter the secret name. + 1. Enter the secret value. + 1. 单击 **Add secret（添加密码）**。 + +{% ifversion fpt or ghae-next or ghes > 3.1 %}您也可以通过 REST API 创建和配置环境。 更多信息请参阅“[环境](/rest/reference/repos#environments)”和“[密码](/rest/reference/actions#secrets)”。{% endif %} + +运行引用不存在的环境的工作流程将使用引用的名称创建环境。 新创建的环境将不配置任何保护规则或机密。 可在仓库中编辑工作流程的任何人都可以通过工作流程文件创建环境，但只有仓库管理员才能配置环境。 + +## Using an environment + +工作流程中的每个作业都可以引用单个环境。 在将引用环境的作业发送到运行器之前，必须通过为环境配置的任何保护规则。 The job can access the environment's secrets only after the job is sent to a runner. + +当工作流程引用环境时，环境将显示在仓库的部署中。 有关查看当前和以前的部署的详细信息，请参阅“[查看部署历史记录](/developers/overview/viewing-deployment-history)”。 + +{% data reusables.actions.environment-example %} + +## 删除环境 + +{% data reusables.github-actions.permissions-statement-environment %} + +删除环境将删除与环境关联的所有机密和保护规则。 由于已删除环境的保护规则而正在等待的任何作业将自动失败。 + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.github-actions.sidebar-environment %} +1. 在要删除的环境旁边，单击 {% octicon "trash" aria-label="The trash icon" %}。 +2. 单击 **I understand, delete this environment（我了解，删除此环境）**。 + +{% ifversion fpt or ghae-next or ghes > 3.1 %}您也可以通过 REST API 删除环境。 更多信息请参阅“[环境](/rest/reference/repos#environments)”。{% endif %} + +## How environments relate to deployments + +{% data reusables.actions.environment-deployment-event %} + +You can access these objects through the REST API or GraphQL API. You can also subscribe to these webhook events. For more information, see "[Repositories](/rest/reference/repos#deployments)" (REST API), "[Objects](/graphql/reference/objects#deployment)" (GraphQL API), or "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#deployment)." + +## 后续步骤 + +{% data variables.product.prodname_actions %} provides several features for managing your deployments. For more information, see "[Deploying with GitHub Actions](/actions/deployment/deploying-with-github-actions)." diff --git a/translations/zh-CN/content/actions/deployment/viewing-deployment-history.md b/translations/zh-CN/content/actions/deployment/viewing-deployment-history.md new file mode 100644 index 0000000000..0c60baaae3 --- /dev/null +++ b/translations/zh-CN/content/actions/deployment/viewing-deployment-history.md @@ -0,0 +1,27 @@ +--- +title: 查看部署历史记录 +intro: 查看仓库的当前和先前部署。 +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - API +shortTitle: 查看部署历史记录 +redirect_from: + - /developers/overview/viewing-deployment-history +--- + + +您可以通过 {% ifversion fpt or ghae or ghes > 3.0 %}{% data variables.product.prodname_actions %} 和环境或使用 {% endif %} REST API 和第三方应用程序来交付部署。 {% ifversion fpt or ghae ghes > 3.0 %}For more information about using environments to deploy with {% data variables.product.prodname_actions %}, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." {% endif %}有关使用 REST API 进行部署的更多信息，请参阅“[仓库](/rest/reference/repos#deployments)”。 + +要查看当前和过去的部署，请在仓库的主页上单击 **Environments（环境）**。 +{% ifversion ghae or ghes < 3.0 %} +![环境](/assets/images/enterprise/2.22/environments-sidebar.png){% else %} +![Environments](/assets/images/environments-sidebar.png){% endif %} + +部署页显示仓库中每个环境的最新活动部署。 If the deployment includes an environment URL, a **View deployment** button that links to the URL is shown next to the deployment. + +活动日志显示环境的部署历史记录。 默认情况下，只有环境的最新部署具有 `Active` 状态；所有先前的活动部署具有 `Inactive` 状态。 有关自动失活部署的更多信息，请参阅“[非活动部署](/rest/reference/repos#inactive-deployments)”。 + +您也可以使用 REST API 来获取有关部署的信息。 更多信息请参阅“[仓库](/rest/reference/repos#deployments)”。 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 9d2a9aa2ed..d69efccdc8 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 @@ -14,7 +14,6 @@ type: overview {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 关于自托管运行器 @@ -58,9 +57,9 @@ type: overview * 如果您想运行使用 Docker 容器操作或服务容器的工作流程，您必须使用 Linux 机器并安装 Docker。 {% ifversion fpt or ghes > 3.2 %} -## 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)." +您可以自动增加或减少环境中自托管运行器的数量，以响应您收到的 web 挂钩事件。 更多信息请参阅“[使用自托管运行器自动缩放](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)”。 {% endif %} @@ -119,7 +118,7 @@ You can automatically increase or decrease the number of self-hosted runners in ## 自托管运行器与 {% data variables.product.prodname_dotcom %} 之间的通信 -Some extra configuration might be required to use actions from {% data variables.product.prodname_dotcom_the_website %} with {% data variables.product.prodname_ghe_server %}, or to use the `actions/setup-LANGUAGE` actions with self-hosted runners that do not have internet access. 更多信息请参阅“[自托管运行器与 {% data variables.product.prodname_dotcom %} 之间的通信](#communication-between-self-hosted-runners-and-github)”。 +可能需要额外配置才可结合使用来自 {% data variables.product.prodname_dotcom_the_website %} 的操作与 {% data variables.product.prodname_ghe_server %}，或者结合使用 `actions/setup-LANGUAGE` 操作与没有互联网连接的自托管运行器。 更多信息请参阅“[自托管运行器与 {% data variables.product.prodname_dotcom %} 之间的通信](#communication-between-self-hosted-runners-and-github)”。 {% endif %} @@ -172,7 +171,9 @@ pkg-containers-az.githubusercontent.com ## 使用公共仓库的自托管运行器安全性 +{% ifversion not ghae %} {% data reusables.github-actions.self-hosted-runner-security %} +{% endif %} 这对 {% data variables.product.prodname_dotcom %} 托管的运行器不是问题，因为每个 {% data variables.product.prodname_dotcom %} 托管的运行器始终是一个干净的独立虚拟机， 在作业执行结束时被销毁。 diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md b/translations/zh-CN/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md index 8a91de3657..f01181a802 100644 --- a/translations/zh-CN/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md +++ b/translations/zh-CN/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md @@ -9,12 +9,12 @@ versions: ghes: '*' ghae: '*' type: tutorial +shortTitle: 添加自托管的运行器 --- {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} 您可以将自托管的运行器添加到 {{ site.data.variables.product.prodname_actions }}。 @@ -22,6 +22,7 @@ type: tutorial 如果需要支持自托管运行器的操作系统的信息，或通过代理服务器的自托管运行器，请参阅“[关于自托管运行器](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)”。 +{% ifversion not ghae %} {% warning %} **警告：** {% data reusables.github-actions.self-hosted-runner-security %} @@ -29,55 +30,86 @@ type: tutorial 更多信息请参阅“[关于自托管运行器](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)”。 {% endwarning %} +{% endif %} -### 添加自托管的运行器到仓库 +## 添加自托管的运行器到仓库 您可以将自托管的运行器添加到单个仓库中。 要将自托管的运行器添加到用户仓库，您必须是仓库所有者。 对于组织仓库，您必须是组织所有者或拥有该仓库管理员的权限。 +{% ifversion fpt %} +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +{% data reusables.github-actions.settings-sidebar-actions %} +{% data reusables.github-actions.settings-sidebar-actions-runners-updated %} +1. 单击 **New self-hosted runner（新建自托管运行器）**。 +{% data reusables.github-actions.self-hosted-runner-configure %} +{% endif %} +{% ifversion ghae or ghes %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} 1. 在 -{% if currentVersion == "free-pro-team@latest" %}“Runners（运行器）”{% else %}“Self-hosted runners（自托管运行器）”{% endif %}下，单击 **Add runner（添加运行器）**。 +{% ifversion fpt or ghes > 3.1 or ghae %}“Runners（运行器）”{% else %}“Self-hosted runners（自托管运行器）”{% endif %}下，单击 **Add runner（添加运行器）**。 {% data reusables.github-actions.self-hosted-runner-configure %} +{% endif %} {% data reusables.github-actions.self-hosted-runner-check-installation-success %} -### 添加自托管的运行器到组织 +## 添加自托管的运行器到组织 您可以在组织级别添加自托管的运行器，其中它们可被用于处理组织中的多个仓库的作业。 要将自托管的运行器添加到组织，您必须是组织所有者。 +{% ifversion fpt %} +{% data reusables.organizations.navigate-to-org %} +{% data reusables.organizations.org_settings %} +{% data reusables.github-actions.settings-sidebar-actions %} +{% data reusables.github-actions.settings-sidebar-actions-runners-updated %} +1. 单击 **New runner（新运行器）**。 +{% data reusables.github-actions.self-hosted-runner-configure %} +{% endif %} +{% ifversion ghae or ghes %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} 1. 在 -{% if currentVersion == "free-pro-team@latest" %}“Runners（运行器）”{% else %}“Self-hosted runners（自托管运行器）”{% endif %}下，单击 **Add runner（添加运行器）**。 +{% ifversion fpt or ghes > 3.1 or ghae %}“Runners（运行器）”{% else %}“Self-hosted runners（自托管运行器）”{% endif %}下，单击 **Add runner（添加运行器）**。 {% data reusables.github-actions.self-hosted-runner-configure %} +{% endif %} + {% data reusables.github-actions.self-hosted-runner-check-installation-success %} {% data reusables.github-actions.self-hosted-runner-public-repo-access %} -### 添加自托管运行器到企业 +## 添加自托管运行器到企业 您可以将自托管运行器添加到企业，在该企业中可以将它们分配给多个组织。 然后，组织管理员能够控制哪些仓库可以使用它。 -{% if currentVersion == "free-pro-team@latest" %} +新运行器被分配到默认组。 您可以在注册运行器后修改运行器组。 更多信息请参阅“[管理对自托管运行器的访问](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)”。 + +{% ifversion fpt %} 要将自托管的运行器添加到企业帐户，您必须是组织所有者。 -{% elsif enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" or currentVersion == "github-ae@latest" %} -要在 -{% data variables.product.product_location %} 的企业级删除自托管运行器，您必须是网站管理员。 -{% endif %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} {% data reusables.enterprise-accounts.actions-runners-tab %} -1. 单击 **Add new（新增）**，然后单击 **New runner（新运行器）**。 新运行器被分配到默认组。 您可以在注册运行器后修改运行器组。 更多信息请参阅“[管理对自托管运行器的访问](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)”。 +1. 单击 **New runner（新运行器）**。 {% data reusables.github-actions.self-hosted-runner-configure %} +{% endif %} +{% ifversion ghae or ghes %} +要在 +{% data variables.product.product_location %} 的企业级删除自托管运行器，您必须是网站管理员。 +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.actions-tab %} +{% data reusables.enterprise-accounts.actions-runners-tab %} +1. 单击 **Add new（新增）**，然后单击 **New runner（新运行器）**。 +{% data reusables.github-actions.self-hosted-runner-configure %} +{% endif %} {% data reusables.github-actions.self-hosted-runner-check-installation-success %} {% data reusables.github-actions.self-hosted-runner-public-repo-access %} -#### 让企业运行器可用于仓库 +### 让企业运行器可用于仓库 在默认情况下，企业的“默认”自托管运行器组的运行器可用于企业中的所有组织，但不可用于每个组织中的所有仓库。 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 981ed6191e..11bc3525a6 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 @@ -10,7 +10,6 @@ type: overview {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About autoscaling diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md b/translations/zh-CN/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md index fab1e90313..977a4afc31 100644 --- a/translations/zh-CN/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md +++ b/translations/zh-CN/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md @@ -15,7 +15,6 @@ shortTitle: 启动时运行运行器应用程序 {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% capture service_first_step %}1. 如果自托管的运行器应用程序正在运行，请停止它。{% endcapture %} {% capture service_non_windows_intro_shell %}在运行器机器上，在安装了自托管运行器应用程序的目录中打开 shell。 使用以下命令安装和管理自托管的运行器服务。{% endcapture %} diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/index.md b/translations/zh-CN/content/actions/hosting-your-own-runners/index.md index 21ed7b8a2f..bd30bcc992 100644 --- a/translations/zh-CN/content/actions/hosting-your-own-runners/index.md +++ b/translations/zh-CN/content/actions/hosting-your-own-runners/index.md @@ -24,4 +24,3 @@ children: {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md b/translations/zh-CN/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md index 8b81537de7..592f925574 100644 --- a/translations/zh-CN/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md +++ b/translations/zh-CN/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md @@ -8,13 +8,12 @@ versions: ghes: '*' ghae: '*' type: tutorial -shortTitle: Manage runner groups +shortTitle: 管理运行器组 --- {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 关于自托管运行器组 @@ -44,12 +43,12 @@ shortTitle: Manage runner groups {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runner-groups %} -1. In the "Runner groups" section, click **New runner group**. +1. 在“Runner groups（运行器组）”部分，单击 **New runner group（新运行器组）**。 {% data reusables.github-actions.runner-group-assign-policy-repo %} {% warning %} - **Warning**: {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %} + **警告：** {% indented_data_reference reusables.github-actions.self-hosted-runner-security spaces=3 %} 更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)”。 @@ -60,12 +59,12 @@ shortTitle: Manage runner groups {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} -1. In the "Self-hosted runners" section, click **Add new**, and then **New group**. +1. 在“Self-hosted runners（自托管运行器）”部分，单击 **Add new（新增）**，然后单击 **New group（新组）**。 ![添加运行器组](/assets/images/help/settings/actions-org-add-runner-group.png) 1. 输入运行程序组的名称，并分配仓库访问策略。 - {% ifversion ghes > 2.22 or ghae %} 您可以配置一个运行器组可供一组特定的仓库或组织中所有仓库访问。 默认情况下，只有私有仓库可以访问运行器组中的运行器，但您可以覆盖此设置。 This setting can't be overridden if configuring an organization's runner group that was shared by an enterprise.{% endif %}{% ifversion ghes = 2.22 %}You can configure a runner group to be accessible to a specific list of repositories, all private repositories, or all repositories in the organization.{% endif %} + {% ifversion ghes > 2.22 or ghae %} 您可以配置一个运行器组可供一组特定的仓库或组织中所有仓库访问。 默认情况下，只有私有仓库可以访问运行器组中的运行器，但您可以覆盖此设置。 如果配置企业共享的组织运行组，则此设置无法覆盖。{% endif %}{% ifversion ghes = 2.22 %}您可以配置一个运行器组，以便访问特定的仓库列表、所有私有仓库或组织中的所有仓库。{% endif %} {% warning %} @@ -95,7 +94,7 @@ shortTitle: Manage runner groups {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} {% data reusables.enterprise-accounts.actions-runner-groups-tab %} -1. Click **New runner group**. +1. 单击 **New runner group（新运行器组）**。 {% data reusables.github-actions.runner-group-assign-policy-org %} {% warning %} @@ -119,7 +118,7 @@ shortTitle: Manage runner groups ![添加运行器组](/assets/images/help/settings/actions-enterprise-account-add-runner-group.png) 1. 输入运行程序组的名称，并分配组织访问策略。 - {% ifversion fpt or ghes > 2.22 or ghae %} 您可以配置运行器组供特定的组织列表或企业中所有组织访问。 默认情况下，只有私有仓库可以访问运行器组中的运行器，但您可以覆盖此设置。 This setting can't be overridden if configuring an organization's runner group that was shared by an enterprise.{% elsif ghes = 2.22 %}You can configure a runner group to be accessible to all organizations in the enterprise or choose specific organizations.{% endif %} + {% ifversion fpt or ghes > 2.22 or ghae %} 您可以配置运行器组供特定的组织列表或企业中所有组织访问。 默认情况下，只有私有仓库可以访问运行器组中的运行器，但您可以覆盖此设置。 如果配置企业共享的组织运行组，则此设置无法覆盖。{% elsif ghes = 2.22 %}您可以配置一个运行器组，以便访问企业中的所有组织或选择特定的组织。{% endif %} {% warning %} @@ -141,7 +140,7 @@ shortTitle: Manage runner groups {% ifversion fpt %} {% data reusables.github-actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %} {% data reusables.github-actions.settings-sidebar-actions-runner-groups-selection %} -1. Modify the access options, or change the runner group name. +1. 修改访问选项或更改运行器组名称。 {% warning %} @@ -156,31 +155,30 @@ shortTitle: Manage runner groups {% ifversion ghae or ghes %} {% data reusables.github-actions.self-hosted-runner-configure-runner-group-access %} {% endif %} -## Automatically adding a self-hosted runner to a group +## 自动向组添加自托管运行器 -You can use the configuration script to automatically add a new self-hosted runner to a group. For example, this command registers a new self-hosted runner and uses the `--runnergroup` parameter to add it to a group named `rg-runnergroup`. +您可以使用配置脚本自动向组添加新的自托管运行器。 例如， 此命令将注册一个新的自托管运行器，并使用 `--runnergroup` 参数将其添加到名为 `rg-runnergroup` 的组。 ```sh ./config.sh --url $org_or_enterprise_url --token $token --runnergroup rg-runnergroup ``` -The command will fail if the runner group doesn't exist: +如果运行器组不存在，命令将失败： ``` -Could not find any self-hosted runner group named "rg-runnergroup". +找不到名为 "rg-runnergroup" 的任何自托管运行器组。 ``` ## 将自托管的运行器移动到组 -If you don't specify a runner group during the registration process, your new self-hosted runners are automatically assigned to the default group, and can then be moved to another group. -{% ifversion fpt %} +如果您在注册过程中没有指定运行器组，新的自托管运行器将自动分配到默认组，然后可以移到另一个组。 +{% ifversion fpt or ghes > 3.1 or ghae-next %} {% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %} -1. In the "Runners" list, click the runner that you want to configure. -1. Select the Runner group dropdown menu. +1. 在“Runners（运行器）”列表中，单击您要配置的运行器。 +1. 选择运行器组下拉菜单。 1. In "Move runner to group", choose a destination group for the runner. -{% endif %} -{% ifversion ghae or ghes %} -1. 在设置页面的{% ifversion fpt %}“Runners（运行器）”{% else %}“Self-hosted runners（自托管运行器）”{% endif %}部分，找到要移动的运行器的当前组，并展开组成员列表。 ![查看运行器组成员](/assets/images/help/settings/actions-org-runner-group-members.png) +{% else %} +1. In the "Self-hosted runners" section of the settings page, locate the current group of the runner you want to move and expand the list of group members. ![查看运行器组成员](/assets/images/help/settings/actions-org-runner-group-members.png) 1. 选中自托管运行器旁边的复选框，然后单击 **Move to group（移动到组）**以查看可用的目的地。 ![运行器组成员移动](/assets/images/help/settings/actions-org-runner-group-member-move.png) 1. 要移动运行器，请单击目标组。 ![运行器组成员移动](/assets/images/help/settings/actions-org-runner-group-member-move-destination.png) {% endif %} @@ -188,14 +186,13 @@ If you don't specify a runner group during the registration process, your new se 自托管运行器在其组被删除时将自动返回到默认组。 -{% ifversion fpt %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} {% data reusables.github-actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %} 1. In the list of groups, to the right of the group you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. 1. 要删除组，请单击 **Remove group（删除组）**。 1. 查看确认提示，然后单击 **Remove this runner group（删除此运行器组）**。 -{% endif %} -{% ifversion ghae or ghes %} -1. 在设置页面的{% ifversion fpt %}“Runners（运行器）”{% else %}“Self-hosted runners（自托管运行器）”{% endif %}部分，找到要删除的组，然后单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} 按钮。 ![查看运行器组设置](/assets/images/help/settings/actions-org-runner-group-kebab.png) +{% else %} +1. In the "Self-hosted runners" section of the settings page, locate the group you want to delete, and click the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} button. ![查看运行器组设置](/assets/images/help/settings/actions-org-runner-group-kebab.png) 1. 要删除组，请单击 **Remove group（删除组）**。 ![查看运行器组设置](/assets/images/help/settings/actions-org-runner-group-remove.png) diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md b/translations/zh-CN/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md index ade76e77fa..a46cb2f3e9 100644 --- a/translations/zh-CN/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md +++ b/translations/zh-CN/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md @@ -17,7 +17,6 @@ shortTitle: 监控和故障排除 {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 使用 {% data variables.product.prodname_dotcom %} 检查自托管运行器的状态 @@ -25,7 +24,7 @@ shortTitle: 监控和故障排除 {% data reusables.github-actions.self-hosted-runner-navigate-repo-and-org %} {% data reusables.github-actions.settings-sidebar-actions-runners %} -1. 在{% ifversion fpt %}“Runners（运行器）”{% else %}“Self-hosted runners（自托管运行器）”{% endif %} 下，您可以查看已注册运行器的列表，包括运行器的名称、标签和状态。 +1. Under {% ifversion fpt or ghes > 3.1 or ghae-next %}"Runners"{% else %}"Self-hosted runners"{% endif %}, you can view a list of registered runners, including the runner's name, labels, and status. 可以是以下状态之一： diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md b/translations/zh-CN/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md index 164c5c5eb6..a9561abb48 100644 --- a/translations/zh-CN/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md +++ b/translations/zh-CN/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md @@ -15,7 +15,6 @@ shortTitle: 删除自托管的运行器 {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 从仓库中删除运行器 @@ -57,15 +56,14 @@ shortTitle: 删除自托管的运行器 要从组织删除自托管的运行器，您必须是组织所有者。 建议您也访问自托管的运行器机器。 {% data reusables.github-actions.self-hosted-runner-reusing %} -{% ifversion fpt %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions %} {% data reusables.github-actions.settings-sidebar-actions-runners-updated %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %} -{% endif %} -{% ifversion ghae or ghes %} +{% else %} {% data reusables.organizations.navigate-to-org %} {% data reusables.organizations.org_settings %} {% data reusables.github-actions.settings-sidebar-actions-runners %} @@ -90,10 +88,9 @@ shortTitle: 删除自托管的运行器 {% data reusables.enterprise-accounts.actions-runners-tab %} {% data reusables.github-actions.settings-sidebar-actions-runner-selection %} {% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %} -{% endif %} -{% ifversion ghae or ghes %} +{% elsif ghae or ghes %} 要在 -{% data variables.product.product_location %} 的企业级删除自托管运行器，您必须是网站管理员。 建议您也访问自托管的运行器机器。 +{% data variables.product.product_location %}, you must be an enterprise owner. 建议您也访问自托管的运行器机器。 {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md b/translations/zh-CN/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md index 3be2ca0976..453263489d 100644 --- a/translations/zh-CN/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md +++ b/translations/zh-CN/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md @@ -14,7 +14,6 @@ shortTitle: 代理服务器 {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 使用环境变量配置代理服务器 diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md b/translations/zh-CN/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md index 210c7c718b..bef76c2db2 100644 --- a/translations/zh-CN/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md +++ b/translations/zh-CN/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md @@ -12,7 +12,6 @@ shortTitle: 标签运行器 {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} 有关如何使用标签将作业路由到特定类型的自托管运行器的信息，请参阅“[在工作流程中使用自托管的运行器](/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow)”。 diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md b/translations/zh-CN/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md index 1316ed4567..57c7b777b9 100644 --- a/translations/zh-CN/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md +++ b/translations/zh-CN/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md @@ -15,7 +15,6 @@ shortTitle: 在工作流程中使用运行器 {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} 有关创建自定义和默认标签的信息，请参阅“[将标签与自托管运行器一起使用](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)。” diff --git a/translations/zh-CN/content/actions/index.md b/translations/zh-CN/content/actions/index.md index 6014d8c25f..7ef5705728 100644 --- a/translations/zh-CN/content/actions/index.md +++ b/translations/zh-CN/content/actions/index.md @@ -9,6 +9,7 @@ featuredLinks: guides: - /actions/learn-github-actions - /actions/guides/about-continuous-integration + - /actions/deployment/deploying-with-github-actions - /actions/guides/about-packaging-with-github-actions - /actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting guideCards: diff --git a/translations/zh-CN/content/actions/learn-github-actions/contexts.md b/translations/zh-CN/content/actions/learn-github-actions/contexts.md index b0c96ce9e3..682e99afb5 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/contexts.md +++ b/translations/zh-CN/content/actions/learn-github-actions/contexts.md @@ -18,7 +18,6 @@ miniTocMaxHeadingLevel: 3 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About contexts @@ -61,27 +60,29 @@ miniTocMaxHeadingLevel: 3 {% data reusables.github-actions.github-context-warning %} {% data reusables.github-actions.context-injection-warning %} -| 属性名称 | 类型 | 描述 | -| ------------------------- | ----- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `github` | `对象` | 工作流程中任何作业或步骤期间可用的顶层上下文。 | -| `github.action` | `字符串` | 正在运行的操作的名称。 在当前步骤运行脚本时，{% data variables.product.prodname_dotcom %} 删除特殊字符或使用名称 `run`。 如果在同一作业中多次使用相同的操作，则名称将包括带有序列号的后缀。 例如，运行的第一个脚本名称为 `run1`，则第二个脚本将命名为 `run2`。 同样，`actions/checkout` 第二次调用时将变成 `actionscheckout2`。 | -| `github.action_path` | `字符串` | 您的操作所在的路径。 您可以使用此路径轻松访问与操作位于同一仓库中的文件。 This attribute is only supported in composite actions. | -| `github.actor` | `字符串` | 发起工作流程运行的用户的登录名。 | -| `github.base_ref` | `字符串` | 工作流程运行中拉取请求的 `base_ref` 或目标分支。 此属性仅在触发工作流程运行的事件为 `pull_request` 或 `pull_request_target` 时才可用。 | -| `github.event` | `对象` | 完整事件 web 挂钩有效负载。 更多信息请参阅“[触发工作流程的事件](/articles/events-that-trigger-workflows/)”。 您可以使用上下文访问事件的个别属性。 | -| `github.event_name` | `字符串` | 触发工作流程运行的事件的名称。 | -| `github.event_path` | `字符串` | 运行器上完整事件 web 挂钩有效负载的路径。 | -| `github.head_ref` | `字符串` | 工作流程运行中拉取请求的 `head_ref` 或来源分支。 此属性仅在触发工作流程运行的事件为 `pull_request` 或 `pull_request_target` 时才可用。 | -| `github.job` | `字符串` | 当前作业的 [`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id)。 | -| `github.ref` | `字符串` | 触发工作流程的分支或标记参考。 For branches this is the format `refs/heads/`, and for tags it is `refs/tags/`. | -| `github.repository` | `字符串` | 所有者和仓库名称。 例如 `Codertocat/Hello-World`。 | -| `github.repository_owner` | `字符串` | 仓库所有者的名称。 例如 `Codertocat`。 | +| 属性名称 | 类型 | 描述 | +| ------------------------- | ----- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `github` | `对象` | 工作流程中任何作业或步骤期间可用的顶层上下文。 | +| `github.action` | `字符串` | 正在运行的操作的名称。 {% data variables.product.prodname_dotcom %} removes special characters or uses the name `__run` when the current step runs a script. If you use the same action more than once in the same job, the name will include a suffix with the sequence number with underscore before it. For example, the first script you run will have the name `__run`, and the second script will be named `__run_2`. 同样，`actions/checkout` 第二次调用时将变成 `actionscheckout2`。 | +| `github.action_path` | `字符串` | 您的操作所在的路径。 您可以使用此路径轻松访问与操作位于同一仓库中的文件。 此属性仅在复合操作中才受支持。 | +| `github.actor` | `字符串` | 发起工作流程运行的用户的登录名。 | +| `github.base_ref` | `字符串` | 工作流程运行中拉取请求的 `base_ref` 或目标分支。 此属性仅在触发工作流程运行的事件为 `pull_request` 或 `pull_request_target` 时才可用。 | +| `github.event` | `对象` | 完整事件 web 挂钩有效负载。 更多信息请参阅“[触发工作流程的事件](/articles/events-that-trigger-workflows/)”。 您可以使用上下文访问事件的个别属性。 | +| `github.event_name` | `字符串` | 触发工作流程运行的事件的名称。 | +| `github.event_path` | `字符串` | 运行器上完整事件 web 挂钩有效负载的路径。 | +| `github.head_ref` | `字符串` | 工作流程运行中拉取请求的 `head_ref` 或来源分支。 此属性仅在触发工作流程运行的事件为 `pull_request` 或 `pull_request_target` 时才可用。 | +| `github.job` | `字符串` | 当前作业的 [`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id)。 | +| `github.ref` | `字符串` | 触发工作流程的分支或标记参考。 对于分支，格式为 `refs/heads/`，对于标记是 `refs/tags/`。 | +| `github.repository` | `字符串` | 所有者和仓库名称。 例如 `Codertocat/Hello-World`。 | +| `github.repository_owner` | `字符串` | 仓库所有者的名称。 例如 `Codertocat`。 | | `github.run_id` | `字符串` | {% data reusables.github-actions.run_id_description %} | `github.run_number` | `字符串` | {% data reusables.github-actions.run_number_description %} -| `github.sha` | `字符串` | 触发工作流程的提交 SHA。 | -| `github.token` | `字符串` | 代表仓库上安装的 GitHub 应用程序进行身份验证的令牌。 这在功能上等同于 `GITHUB_TOKEN` 密码。 更多信息请参阅“[使用 GITHUB_TOKEN 验证身份](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)”。 | -| `github.workflow` | `字符串` | 工作流程的名称。 如果工作流程文件未指定 `name`，此属性的值将是仓库中工作流程文件的完整路径。 | -| `github.workspace` | `字符串` | 使用 [`checkout`](https://github.com/actions/checkout) 操作时步骤的默认工作目录和仓库的默认位置。 | +| `github.run_attempt` | `字符串` | A unique number for each attempt of a particular workflow run in a repository. This number begins at 1 for the workflow run's first attempt, and increments with each re-run. | +| `github.server_url` | `字符串` | Returns the URL of the GitHub server. 例如：`https://github.com`。 | +| `github.sha` | `字符串` | 触发工作流程的提交 SHA。 | +| `github.token` | `字符串` | 代表仓库上安装的 GitHub 应用程序进行身份验证的令牌。 这在功能上等同于 `GITHUB_TOKEN` 密码。 更多信息请参阅“[使用 GITHUB_TOKEN 验证身份](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)”。 | +| `github.workflow` | `字符串` | 工作流程的名称。 如果工作流程文件未指定 `name`，此属性的值将是仓库中工作流程文件的完整路径。 | +| `github.workspace` | `字符串` | 使用 [`checkout`](https://github.com/actions/checkout) 操作时步骤的默认工作目录和仓库的默认位置。 | ### `env` 上下文 @@ -130,6 +131,7 @@ miniTocMaxHeadingLevel: 3 | 属性名称 | 类型 | 描述 | | ------------------- | ----- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `runner.name` | `字符串` | {% data reusables.actions.runner-name-description %} | `runner.os` | `字符串` | {% data reusables.actions.runner-os-description %} | `runner.temp` | `字符串` | {% data reusables.actions.runner-temp-directory-description %} | `runner.tool_cache` | `字符串` | {% ifversion ghae %}有关如何确定 {% data variables.actions.hosted_runner %} 已安装所需软件的说明，请参阅“[创建自定义映像](/actions/using-github-hosted-runners/creating-custom-images)”。 {% else %} {% data reusables.actions.runner-tool-cache-description %} {% endif %} diff --git a/translations/zh-CN/content/actions/learn-github-actions/creating-workflow-templates.md b/translations/zh-CN/content/actions/learn-github-actions/creating-workflow-templates.md new file mode 100644 index 0000000000..2488eed982 --- /dev/null +++ b/translations/zh-CN/content/actions/learn-github-actions/creating-workflow-templates.md @@ -0,0 +1,93 @@ +--- +title: Creating workflow templates +shortTitle: Creating templates +intro: Learn how you can create workflow templates to help people in your team add new workflows more easily. +redirect_from: + - /actions/configuring-and-managing-workflows/sharing-workflow-templates-within-your-organization +versions: + fpt: '*' + ghes: '*' + ghae: '*' +type: tutorial +topics: + - Workflows + - CI +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +## 概览 + +{% data reusables.actions.workflow-organization-templates %} + +## 创建工作流程模板 + +对组织的 `.github` 仓库具有写入权限的用户可以创建工作流程模板。 然后，有权限创建工作流程的组织成员便可使用这些模板。 You can share workflow templates if your organization's repository is public or if the repository is private and on an Enterprise plan. + +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +{% note %} + +**Note:** To avoid duplication in workflows created from a template you can call reusable workflows from within a workflow template. This can help make your workflows easier to maintain. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." + +{% endnote %} +{% endif %} + +此过程展示如何创建工作流程模板和元数据文件。 元数据文件描述在用户新建工作流程时如何向其显示模板。 + +1. 如果组织中没有名为 `.github` 的公共仓库，请新建一个。 +2. 创建一个名为 `workflow-templates` 的目录。 +3. 在 `workflow-templates` 目录中创建新的工作流程文件。 + + 如果需要引用仓库的默认分支，可以使用 `$default-branch` 占位符。 使用模板创建工作流程时，占位符将自动替换为仓库默认分支的名称。 + + 例如，下面这个名为 `octo-organization-ci.yml` 的文件展示了一个基本的工作流程。 + + ```yaml + name: Octo Organization CI + + on: + push: + branches: [ $default-branch ] + pull_request: + branches: [ $default-branch ] + + jobs: + build: + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v2 + + - name: Run a one-line script + run: echo Hello from Octo Organization + ``` +4. 在 `workflow-templates` 目录中创建元数据文件。 元数据文件必须与工作流程文件同名，但扩展名不是 `.yml`，而必须附加 `.properties.json`。 例如，下面这个名为 `octo-organization-ci.properties.json` 的文件包含名为 `octo-organization-ci.yml` 的工作流程文件的元数据： + ```yaml + { + "name": "Octo Organization Workflow", + "description": "Octo Organization CI workflow template.", + "iconName": "example-icon", + "categories": [ + "Go" + ], + "filePatterns": [ + "package.json$", + "^Dockerfile", + ".*\\.md$" + ] + } + ``` + * `name` - **必要。**工作流程模板的名称。 这会显示在可用模板列表中。 + * `description` - **必要。**工作流程模板的描述。 这会显示在可用模板列表中。 + * `iconName` - **必要。**定义模板列表中工作流程项目的图标。 `iconName` 必须是同名的 SVG 图标，且必须存储在 `workflow-templates` 目录中。 例如，名为 `example-icon.svg` 的 SVG 文件被引用为 `example-icon`。 + * `categories` - **可选。**定义工作流程的语言类别。 当用户查看可用模板时，匹配相同语言的模板将更加突出。 有关可用语言类别的信息，请参阅https://github.com/github/linguist/blob/master/lib/linguist/languages.yml。 + * `filePatterns` - **可选。**如果用户仓库在其根目录中有符合定义的正则表达式的文件，则允许使用模板。 + +要添加另一个工作流模板，请将您的文件添加到同一 `workflow-templates` 目录中。 例如： + +![工作流程模板文件](/assets/images/help/images/workflow-template-files.png) + +## 后续步骤 + +To continue learning about {% data variables.product.prodname_actions %}, see "[Using workflow templates](/actions/learn-github-actions/using-workflow-templates)." diff --git a/translations/zh-CN/content/actions/learn-github-actions/environment-variables.md b/translations/zh-CN/content/actions/learn-github-actions/environment-variables.md index 998aa42d53..d06441e4f5 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/environment-variables.md +++ b/translations/zh-CN/content/actions/learn-github-actions/environment-variables.md @@ -15,7 +15,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 关于环境变量 @@ -73,6 +72,7 @@ You can also use the {% ifversion fpt or ghes > 2.22 or ghae %}`GITHUB_ENV` envi | `GITHUB_SERVER_URL` | 返回 {% data variables.product.product_name %} 服务器的 URL。 例如： `https://{% data variables.product.product_url %}`。 | | `GITHUB_API_URL` | 返回 API URL。 例如： `{% data variables.product.api_url_code %}`。 | | `GITHUB_GRAPHQL_URL` | 返回 GraphQL API URL。 例如： `{% data variables.product.graphql_url_code %}`。 | +| `RUNNER_NAME` | {% data reusables.actions.runner-name-description %} | `RUNNER_OS` | {% data reusables.actions.runner-os-description %} | `RUNNER_TEMP` | {% data reusables.actions.runner-temp-directory-description %} {% ifversion not ghae %}| `RUNNER_TOOL_CACHE` | {% data reusables.actions.runner-tool-cache-description %}{% endif %} diff --git a/translations/zh-CN/content/actions/learn-github-actions/essential-features-of-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/essential-features-of-github-actions.md index bc67268faf..f62b40b758 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/essential-features-of-github-actions.md +++ b/translations/zh-CN/content/actions/learn-github-actions/essential-features-of-github-actions.md @@ -13,7 +13,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 概览 @@ -62,7 +61,7 @@ jobs: ## 在作业之间共享数据 -如果作业生成您要与同一工作流程中的另一个作业共享的文件，或者您要保存这些文件供以后参考，可以将它们作为_构件_存储在 {% data variables.product.prodname_dotcom %} 中。 构件是创建并测试代码时所创建的文件。 例如，构件可能包含二进制或包文件、测试结果、屏幕截图或日志文件。 构件与其创建时所在的工作流程运行相关，可被另一个作业使用。 +如果作业生成您要与同一工作流程中的另一个作业共享的文件，或者您要保存这些文件供以后参考，可以将它们作为_构件_存储在 {% data variables.product.prodname_dotcom %} 中。 构件是创建并测试代码时所创建的文件。 例如，构件可能包含二进制或包文件、测试结果、屏幕截图或日志文件。 构件与其创建时所在的工作流程运行相关，可被另一个作业使用。 {% data reusables.actions.reusable-workflow-artifacts %} 例如，您可以创建一个文件，然后将其作为构件上传。 diff --git a/translations/zh-CN/content/actions/learn-github-actions/events-that-trigger-workflows.md b/translations/zh-CN/content/actions/learn-github-actions/events-that-trigger-workflows.md index 723954a69e..f7eb952f86 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/events-that-trigger-workflows.md +++ b/translations/zh-CN/content/actions/learn-github-actions/events-that-trigger-workflows.md @@ -17,7 +17,6 @@ shortTitle: 触发工作流程的事件 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 配置工作流程事件 @@ -165,6 +164,26 @@ on: types: [opened, deleted] ``` +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## Workflow reuse events + +`workflow_call` is a keyword used as the value of `on` in a workflow, in the same way as an event. It indicates that a workflow can be called from another workflow. For more information see, "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." + +### `workflow_call` + +| Web 挂钩事件有效负载 | 活动类型 | `GITHUB_SHA` | `GITHUB_REF` | +| --------------------------- | ---- | --------------------------- | --------------------------- | +| Same as the caller workflow | n/a | Same as the caller workflow | Same as the caller workflow | + +#### 示例 + +To make a workflow reusable it must include `workflow_call` as one of the values of `on`. The example below only runs the workflow when it's called from another workflow: + +```yaml +on: workflow_call +``` +{% endif %} + ## Web 挂钩事件 您可以将工作流程配置为在 {% data variables.product.product_name %} 上生成 web 挂钩事件时运行。 某些事件有多种触发事件的活动类型。 如果有多种活动类型触发事件，则可以指定哪些活动类型将触发工作流程运行。 更多信息请参阅“[web 挂钩](/webhooks)”。 @@ -298,7 +317,7 @@ on: {% data reusables.developer-site.limit_workflow_to_activity_types %} -For example, you can run a workflow when a discussion has been `created`, `edited`, or `answered`. +例如，您可以在讨论为 `created`、`edited` 或 `answered` 时运行工作流程。 ```yaml on: @@ -571,8 +590,8 @@ on: {% note %} **注意：** -- By default, a workflow only runs when a `pull_request`'s activity type is `opened`, `synchronize`, or `reopened`. 要让更多活动类型触发工作流程，请使用 `types` 关键词。 -- Workflows will not run on `pull_request` activity if the pull request has a merge conflict. The merge conflict must be resolved first. +- 默认情况下，工作流程仅在 `pull_request` 的活动类型为 `opened`、`synchronize` 或 `reopened` 时运行。 要让更多活动类型触发工作流程，请使用 `types` 关键词。 +- 如果拉取请求具有合并冲突，工作流程将不会在 `pull_request` 活动上运行。 必须先解决合并冲突。 {% endnote %} diff --git a/translations/zh-CN/content/actions/learn-github-actions/expressions.md b/translations/zh-CN/content/actions/learn-github-actions/expressions.md index a222240cdc..727db3ea60 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/expressions.md +++ b/translations/zh-CN/content/actions/learn-github-actions/expressions.md @@ -12,7 +12,6 @@ miniTocMaxHeadingLevel: 3 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## About expressions @@ -286,7 +285,7 @@ steps: ### always -Causes the step to always execute, and returns `true`, even when canceled. 作业或步骤在重大故障阻止任务运行时不会运行。 例如，如果获取来源失败。 +导致该步骤总是执行，并返回 `true`，即使取消也一样。 作业或步骤在重大故障阻止任务运行时不会运行。 例如，如果获取来源失败。 #### 示例 diff --git a/translations/zh-CN/content/actions/learn-github-actions/finding-and-customizing-actions.md b/translations/zh-CN/content/actions/learn-github-actions/finding-and-customizing-actions.md index 24009f2b2b..885003dee4 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/finding-and-customizing-actions.md +++ b/translations/zh-CN/content/actions/learn-github-actions/finding-and-customizing-actions.md @@ -18,7 +18,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 概览 diff --git a/translations/zh-CN/content/actions/learn-github-actions/index.md b/translations/zh-CN/content/actions/learn-github-actions/index.md index 97c7db6f9e..e56df3eb83 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/index.md +++ b/translations/zh-CN/content/actions/learn-github-actions/index.md @@ -32,8 +32,10 @@ children: - /finding-and-customizing-actions - /essential-features-of-github-actions - /managing-complex-workflows - - /sharing-workflows-with-your-organization + - /sharing-workflows-secrets-and-runners-with-your-organization + - /creating-workflow-templates - /using-workflow-templates + - /reusing-workflows - /events-that-trigger-workflows - /expressions - /contexts diff --git a/translations/zh-CN/content/actions/learn-github-actions/managing-complex-workflows.md b/translations/zh-CN/content/actions/learn-github-actions/managing-complex-workflows.md index b3449f4fd4..aa6aeca37a 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/managing-complex-workflows.md +++ b/translations/zh-CN/content/actions/learn-github-actions/managing-complex-workflows.md @@ -13,7 +13,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 概览 @@ -170,10 +169,13 @@ To learn more about self-hosted runner labels, see ["Using labels with self-host {% data variables.product.prodname_dotcom %}-hosted runner labels, see ["Supported runners and hardware resources"](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources). {% endif %} -{% ifversion fpt or ghes > 3.0 %} +{% data reusables.actions.reusable-workflows %} + +{% ifversion fpt or ghes > 3.0 or ghae-next %} + ## 使用环境 -您可以使用保护规则和机密配置环境。 工作流程中的每个作业都可以引用单个环境。 在将引用环境的作业发送到运行器之前，必须通过为环境配置的任何保护规则。 更多信息请参阅“[环境](/actions/reference/environments)”。 +您可以使用保护规则和机密配置环境。 工作流程中的每个作业都可以引用单个环境。 在将引用环境的作业发送到运行器之前，必须通过为环境配置的任何保护规则。 For more information, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." {% endif %} ## 使用工作流程模板 @@ -187,4 +189,4 @@ To learn more about self-hosted runner labels, see ["Using labels with self-host ## 后续步骤 -要继续了解 {% data variables.product.prodname_actions %}，请参阅“[与组织共享工作流程](/actions/learn-github-actions/sharing-workflows-with-your-organization)”。 +To continue learning about {% data variables.product.prodname_actions %}, see "[Sharing workflows, secrets, and runners with your organization](/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization)." diff --git a/translations/zh-CN/content/actions/learn-github-actions/reusing-workflows.md b/translations/zh-CN/content/actions/learn-github-actions/reusing-workflows.md new file mode 100644 index 0000000000..fd69fac034 --- /dev/null +++ b/translations/zh-CN/content/actions/learn-github-actions/reusing-workflows.md @@ -0,0 +1,195 @@ +--- +title: Reusing workflows +shortTitle: Reusing workflows +intro: Learn how to avoid duplication when creating a workflow by reusing existing workflows. +miniTocMaxHeadingLevel: 3 +versions: + fpt: '*' + ghes: '>=3.4' + ghae: issue-4757 +type: how_to +topics: + - Workflows +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +{% note %} + +**Note:** Reusable workflows are currently in beta and subject to change. + +{% endnote %} + +## 概览 + +Rather than copying and pasting from one workflow to another, you can make workflows reusable. You and anyone with access to the reusable workflow can then call the reusable workflow from another workflow. + +Reusing workflows avoids duplication. This makes workflows easier to maintain and allows you to create new workflows more quickly by building on the work of others, just as you do with actions. Workflow reuse also promotes best practice by helping you to use workflows that are well designed, have already been tested, and have been proved to be effective. Your organization can build up a library of reusable workflows that can be centrally maintained. + +A workflow that uses another workflow is referred to as a "caller" workflow. The reusable workflow is a "called" workflow. One caller workflow can use multiple called workflows. Each called workflow is referenced in a single line. The result is that the caller workflow file may contain just a few lines of YAML, but may perform a large number of tasks when it's run. When you reuse a workflow, the entire called workflow is used, just as if it was part of the caller workflow. + +If you reuse a workflow from a different repository, any actions in the called workflow run as if they were part of the caller workflow. For example, if the called workflow uses `actions/checkout`, the action checks out the contents of the repository that hosts the caller workflow, not the called workflow. + +When a reusable workflow is triggered by a caller workflow, the `github` context is always associated with the caller workflow. For more information about the `github` context, see "[Context and expression syntax for GitHub Actions](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)." + +## Access to reusable workflows + +A reusable workflow can be used by another workflow if any of the following is true: + +* Both workflows are in the same repository. +* The called workflow is stored in a public repository. +* The called workflow is stored in an internal repository and the settings for that repository allow it to be accessed. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#allowing-access-to-components-in-an-internal-repository)." + +## 限制 + +* Reusable workflows can't call other reusable workflows. +* Reusable workflows stored within a private repository can only be used by workflows within the same repository. +* Any environment variables set in an `env` context defined at the workflow level in the caller workflow are not be propagated to the called workflow. For more information about the `env` context, see "[Context and expression syntax for GitHub Actions](/actions/reference/context-and-expression-syntax-for-github-actions#env-context)." + +The following limitations will be removed when workflow reuse moves out of beta: +* Reusable workflows can't reference self-hosted runners. +* You can't set the concurrency of a called workflow from the caller workflow. For more information about `jobs..concurrency`, see "[Workflow syntax for GitHub Actions](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idconcurrency)." +* Outputs generated by a called workflow can't be accessed by the caller workflow. + +## Creating a reusable workflow + +Reusable workflows are YAML-formatted files, very similar to any other workflow file. As with other workflow files, you locate reusable workflows in the `.github/workflows` directory of a repository. Subdirectories of the `workflows` directory are not supported. + +For a workflow to be reusable, the values for `on` must include `workflow_call`: + +```yaml +on: + workflow_call: +``` + +You can define inputs and secrets, which can be passed from the caller workflow and then used within the called workflow. The following example, from a reusable workflow, defines two inputs (called "ring" and "environment") and one secret (called "token"): + +```yaml +on: + workflow_call: + inputs: + ring: + description: 'Identifier for the target deployment ring' + default: 'ring-0' + required: false + type: string + environment: + required: false + type: string + secrets: + token: + required: false +``` + +For details of the syntax for defining inputs and secrets, see [on.workflow_call.inputs](/actions/reference/workflow-syntax-for-github-actions#onworkflow_callinputs) and [on.workflow_call.secrets](/actions/reference/workflow-syntax-for-github-actions#onworkflow_callsecrets). + +### Example reusable workflow + +This reusable workflow file named `workflow-B.yml` (we'll refer to this later) takes an input string and a secret from the caller workflow and uses them in an action. + +{% raw %} +```yaml{:copy} +name: Reusable workflow example + +on: + workflow_call: + inputs: + username: + required: true + type: string + secrets: + token: + required: true + +jobs: + example_job: + name: Pass input and secrets to my-action + runs-on: ubuntu-latest + steps: + - uses: ./.github/actions/my-action@v1 + with: + username: ${{ inputs.username }} + token: ${{ secrets.token }} +``` +{% endraw %} + +## Calling a reusable workflow + +You call a reusable workflow by using the `uses` keyword. Unlike when you are using actions within a workflow, you call reusable workflows directly within a job, and not from within job steps. + +[`jobs..uses`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_iduses) + +You reference reusable workflow files using the syntax: + +`{owner}/{repo}/{path}/{filename}@{ref}` + +You can call multiple workflows, referencing each in a separate job. + +{% data reusables.actions.uses-keyword-example %} + +### Passing inputs and secrets to a reusable workflow + +Use the `with` keyword in a job to pass named inputs to the called workflow. Use the `secrets` keyword to pass named secrets. The inputs and secrets you pass must be defined in the called workflow. For inputs, the data type of the input value must match the type specified for that input in the called workflow (boolean, number, or string). + +{% raw %} +```yaml +with: + username: mona +secrets: + token: ${{ secrets.TOKEN }} +``` +{% endraw %} + +### Supported keywords for jobs that call a reusable workflow + +When you call a reusable workflow, you can only use the following keywords in the job containing the call: + +* [`jobs..name`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idname) +* [`jobs..uses`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_iduses) +* [`jobs..with`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idwith) +* [`jobs..with.`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idwithinput_id) +* [`jobs..secrets`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idsecrets) +* [`jobs..secrets.`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idsecretssecret_id) +* [`jobs..needs`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds) +* [`jobs..if`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idif) +* [`jobs..permissions`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idpermissions) + + {% note %} + + **注:** + + * If `jobs..permissions` is not specified in the calling job, the called workflow will have the default permissions for the `GITHUB_TOKEN`. 更多信息请参阅“[工作流程中的身份验证](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)。 + * The `GITHUB_TOKEN` permissions passed from the caller workflow can be only downgraded (not elevated) by the called workflow. + + {% endnote %} + +### Example caller workflow + +This workflow file calls two workflow files. The second of these, `workflow-B.yml` (shown above), is passed an input, `username`, and a secret, `token`. + +{% raw %} +```yaml{:copy} +name: Call a reusable workflow + +on: + pull_request: + branches: + - main + +jobs: + call-workflow: + uses: octo-org/example-repo/.github/workflows/workflow-A.yml@v1 + + call-workflow-passing-data: + uses: octo-org/example-repo/.github/workflows/workflow-B.yml@main + with: + username: mona + secrets: + token: ${{ secrets.TOKEN }} +``` +{% endraw %} + +## 后续步骤 + +To continue learning about {% data variables.product.prodname_actions %}, see "[Events that trigger workflows](/actions/learn-github-actions/events-that-trigger-workflows)." diff --git a/translations/zh-CN/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md b/translations/zh-CN/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md new file mode 100644 index 0000000000..2bd2ae82f5 --- /dev/null +++ b/translations/zh-CN/content/actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization.md @@ -0,0 +1,53 @@ +--- +title: 'Sharing workflows, secrets, and runners with your organization' +shortTitle: 与组织共享工作流程 +intro: 了解如何通过共享工作流模板、机密和自托管运行器，使用组织功能与团队协作。 +redirect_from: + - /actions/learn-github-actions/sharing-workflows-with-your-organization +versions: + fpt: '*' + ghes: '*' + ghae: '*' +type: how_to +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +## 概览 + +如果需要与您的团队共享工作流程和其他 {% data variables.product.prodname_actions %} 功能，则考虑在 {% data variables.product.prodname_dotcom %} 组织内协作。 组织允许您集中存储和管理机密、构件和自托管运行器。 您也可以在 `.github` 仓库中创建工作流程模板，并与您组织中的其他用户共享。 + +## Using workflow templates + +{% data reusables.actions.workflow-organization-templates %} For more information, see "[Creating workflow templates](/actions/learn-github-actions/creating-workflow-templates)." + +{% data reusables.actions.reusable-workflows %} + +## 在组织内共享机密 + +您可以在组织内集中管理您的机密，然后将其提供给选定的仓库。 这也意味着您可以在一个位置更新机密，并且将更改应用于使用该机密的所有仓库工作流程。 + +在组织中创建密码时，可以使用策略来限制可以访问该密码的仓库。 例如，您可以将访问权限授予所有仓库，也可以限制仅私有仓库或指定的仓库列表拥有访问权限。 + +{% data reusables.github-actions.permissions-statement-secrets-organization %} + +{% data reusables.organizations.navigate-to-org %} +{% data reusables.organizations.org_settings %} +{% data reusables.github-actions.sidebar-secret %} +1. 单击 **New secret（新建密码）**。 +1. 在 **Name（名称）**输入框中键入密码的名称。 +1. 输入密码的 **Value（值）**。 +1. 从 **Repository access（仓库访问权限）**下拉列表，选择访问策略。 +1. 单击 **Add secret（添加密码）**。 + +## 在组织内共享自托管运行器 + +组织管理员可以将其自托管的运行器添加到组，然后创建控制哪些仓库可访问该组的策略。 + +更多信息请参阅“[使用组管理对自托管运行器的访问](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)”。 + + +## 后续步骤 + +To continue learning about {% data variables.product.prodname_actions %}, see "[Creating workflow templates](/actions/learn-github-actions/creating-workflow-templates)." diff --git a/translations/zh-CN/content/actions/learn-github-actions/understanding-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/understanding-github-actions.md index 05b5f9df17..2ecee2be02 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/understanding-github-actions.md +++ b/translations/zh-CN/content/actions/learn-github-actions/understanding-github-actions.md @@ -18,7 +18,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 概览 @@ -36,7 +35,7 @@ topics: ### 工作流程 -工作流程是您添加到仓库的自动化过程。 工作流程由一项或多项作业组成，可以计划或由事件触发。 工作流程可用于在 {% data variables.product.prodname_dotcom %} 上构建、测试、打包、发布或部署项目。 +工作流程是您添加到仓库的自动化过程。 工作流程由一项或多项作业组成，可以计划或由事件触发。 工作流程可用于在 {% data variables.product.prodname_dotcom %} 上构建、测试、打包、发布或部署项目。 {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %}You can reference a workflow within another workflow, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."{% endif %} ### 事件 diff --git a/translations/zh-CN/content/actions/learn-github-actions/usage-limits-billing-and-administration.md b/translations/zh-CN/content/actions/learn-github-actions/usage-limits-billing-and-administration.md index 93d557764b..611e6b7915 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/usage-limits-billing-and-administration.md +++ b/translations/zh-CN/content/actions/learn-github-actions/usage-limits-billing-and-administration.md @@ -16,7 +16,6 @@ shortTitle: 工作流程计费和限制 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 关于 {% data variables.product.prodname_actions %} 的计费 @@ -61,6 +60,12 @@ There are some limits on {% data variables.product.prodname_actions %} usage whe 除了使用限制外，还必须确保使用 [GitHub 服务条款](/articles/github-terms-of-service/) 中的 {% data variables.product.prodname_actions %}。 有关 {% data variables.product.prodname_actions %} 特定条款的更多信息，请参阅 [GitHub 附加产品条款](/github/site-policy/github-additional-product-terms#a-actions-usage)。 {% endif %} +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## Billing for reusable workflows + +If you reuse a workflow, billing is always associated with the caller workflow. For more information see, "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." +{% endif %} + {% ifversion fpt or ghes > 2.22 or ghae %} ## 构件和日志保留策略 diff --git a/translations/zh-CN/content/actions/learn-github-actions/using-workflow-templates.md b/translations/zh-CN/content/actions/learn-github-actions/using-workflow-templates.md index adf9aff0b5..c8bc2caa47 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/using-workflow-templates.md +++ b/translations/zh-CN/content/actions/learn-github-actions/using-workflow-templates.md @@ -1,7 +1,7 @@ --- title: Using workflow templates shortTitle: Using templates -intro: You can set up CI using a workflow template that matches the language and tooling you want to use. +intro: '{% data variables.product.product_name %} provides workflow templates for a variety of languages and tooling.' product: '{% data reusables.gated-features.actions %}' redirect_from: - /articles/setting-up-continuous-integration-using-github-actions @@ -17,34 +17,37 @@ type: tutorial topics: - Workflows - CI + - CD --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -对仓库具有写入权限的任何人都可以使用 {% data variables.product.prodname_actions %} 设置持续集成 (CI)。 +## 关于工作流程模板 -在设置 CI 后，可以根据您的需求自定义工作流程。 +{% data variables.product.product_name %} offers workflow templates for a variety of languages and tooling. When you set up workflows in your repository, {% data variables.product.product_name %} analyzes the code in your repository and recommends workflows based on the language and framework in your repository. 例如，如果您使用 [Node.js](https://nodejs.org/en/)，{% data variables.product.product_name %} 将提议使用模板文件来安装 Node.js 包和运行测试。 + +You can also create your own workflow templates to share with your organization. For more information, see "[Creating workflow templates](/actions/learn-github-actions/creating-workflow-templates)." + +## Using workflow templates + +Anyone with write permission to a repository can set up {% data variables.product.prodname_actions %} workflows for CI/CD or other automation. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} -1. 找到与您要用的语言和工具匹配的模板，然后单击 **Set up this workflow（设置此工作流程）**。 ![设置工作流程按钮](/assets/images/help/repository/setup-workflow-button.png) -5. 单击 **Start commit（开始提交）**。 ![开始提交按钮](/assets/images/help/repository/start-commit.png) -{% data reusables.files.write_commit_message %} -{% data reusables.files.choose_commit_branch %} -{% data reusables.files.propose_new_file %} - -在推送到仓库后，您可以在 {% data variables.product.prodname_dotcom %} 上跟踪持续集成工作流程运行的状态和详细日志，并接收自定义的通知。 更多信息请参阅“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)”和“[管理工作流程运行](/articles/managing-a-workflow-run)”。 - -{% data reusables.repositories.actions-workflow-status-badge-intro %} - -更多信息请参阅“[添加工作流程状态徽章](/actions/managing-workflow-runs/adding-a-workflow-status-badge)”。 +1. If you already have a workflow in your repository, click **New workflow**. +1. Find the template that you want to use, then click **Set up this workflow**. +1. If the workflow template contains comments detailing additional setup steps, follow these steps. +1. Some workflow templates use secrets. For example, {% raw %}`${{ secrets.npm_token }}`{% endraw %}. If the workflow template uses a secret, store the value described in the secret name as a secret in your repository. 更多信息请参阅“[加密密码](/actions/reference/encrypted-secrets)”。 +1. Optionally, make additional changes. For example, you might want to change the value of `on` to change when the workflow runs. +1. 单击 **Start commit（开始提交）**。 +1. Write a commit message and decide whether to commit directly to the default branch or to open a pull request. ## 延伸阅读 - "[关于持续集成](/articles/about-continuous-integration)" -- "[管理工作流程运行](/articles/managing-a-workflow-run)" +- "[Managing workflow runs](/actions/managing-workflow-runs)" +- "[About monitoring and troubleshooting](/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting)" - "[了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" {% ifversion fpt %} - "[管理 {% data variables.product.prodname_actions %} 的计费](/billing/managing-billing-for-github-actions)" diff --git a/translations/zh-CN/content/actions/learn-github-actions/workflow-commands-for-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/workflow-commands-for-github-actions.md index 7607f29222..f1acfc9475 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/workflow-commands-for-github-actions.md +++ b/translations/zh-CN/content/actions/learn-github-actions/workflow-commands-for-github-actions.md @@ -18,7 +18,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 关于工作流程命令 @@ -89,7 +88,7 @@ core.setOutput('SELECTED_COLOR', 'green'); | `core.setOutput` | `set-output` | | `core.setSecret` | `add-mask` | | `core.startGroup` | `组` | -| `core.warning` | `warning file` | +| `core.warning` | `警告` | {% ifversion ghes < 3.0 %} ## 设置环境变量 @@ -98,7 +97,7 @@ core.setOutput('SELECTED_COLOR', 'green'); ::set-env name={name}::{value} ``` -Creates or updates an environment variable for any steps running next in a job. The step that creates or updates the environment variable does not have access to the new value, but all subsequent steps in a job will have access. 环境变量区分大小写，并且可以包含标点符号。 +为作业中接下来运行的任何步骤创建或更新环境变量。 The step that creates or updates the environment variable does not have access to the new value, but all subsequent steps in a job will have access. 环境变量区分大小写，并且可以包含标点符号。 ### 示例 @@ -329,7 +328,13 @@ steps: echo "{name}={value}" >> $GITHUB_ENV ``` -Creates or updates an environment variable for any steps running next in a job. The step that creates or updates the environment variable does not have access to the new value, but all subsequent steps in a job will have access. 环境变量区分大小写，并且可以包含标点符号。 +为作业中接下来运行的任何步骤创建或更新环境变量。 The step that creates or updates the environment variable does not have access to the new value, but all subsequent steps in a job will have access. 环境变量区分大小写，并且可以包含标点符号。 + +{% note %} + +**Note:** Environment variables must be explicitly referenced using the [`env` context](/actions/reference/context-and-expression-syntax-for-github-actions#env-context) in expression syntax or through use of the `$GITHUB_ENV` file directly; environment variables are not implicitly available in shell commands. + +{% endnote %} ### 示例 @@ -376,7 +381,7 @@ steps: echo "{path}" >> $GITHUB_PATH ``` -为系统 `PATH` 变量预先设置一个目录，使其可用于当前作业中的所有后续操作；当前运行的操作无法访问更新的路径变量。 要查看作业的当前定义路径，您可以在步骤或操作中使用 `echo "$PATH"`。 +Prepends a directory to the system `PATH` variable and automatically makes it available to all subsequent actions in the current job; the currently running action cannot access the updated path variable. 要查看作业的当前定义路径，您可以在步骤或操作中使用 `echo "$PATH"`。 ### 示例 diff --git a/translations/zh-CN/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md index 54da9c60c5..5818ab9f08 100644 --- a/translations/zh-CN/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md +++ b/translations/zh-CN/content/actions/learn-github-actions/workflow-syntax-for-github-actions.md @@ -16,7 +16,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 关于工作流程的 YAML 语法 @@ -184,9 +183,91 @@ Diffs are limited to 300 files. If there are files changed that aren't matched i 更多信息请参阅“[关于比较拉取请求中的分支](/articles/about-comparing-branches-in-pull-requests)”。 +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## `on.workflow_call.inputs` + +When using the `workflow_call` keyword, you can optionally specify inputs that are passed to the called workflow from the caller workflow. Inputs for reusable workflows are specified with the same format as action inputs. For more information about inputs, see "[Metadata syntax for GitHub Actions](/actions/creating-actions/metadata-syntax-for-github-actions#inputs)." For more information about the `workflow_call` keyword, see "[Events that trigger workflows](/actions/learn-github-actions/events-that-trigger-workflows#workflow-reuse-events)." + +In addition to the standard input parameters that are available, `on.workflow_call.inputs` requires a `type` parameter. For more information, see [`on.workflow_call..type`](#onworkflow_callinput_idtype). + +If a `default` parameter is not set, the default value of the input is `false` for a boolean, `0` for a number, and `""` for a string. + +Within the called workflow, you can use the `inputs` context to refer to an input. + +If a caller workflow passes an input that is not specified in the called workflow, this results in an error. + +### 示例 + +{% raw %} +```yaml +on: + workflow_call: + inputs: + username: + description: 'A username passed from the caller workflow' + default: 'john-doe' + required: false + type: string + +jobs: + print-username: + runs-on: ubuntu-latest + + steps: + - name: Print the input name to STDOUT + run: echo The username is ${{ inputs.username }} +``` +{% endraw %} + +For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." + +## `on.workflow_call..type` + +Required if input is defined for the `on.workflow_call` keyword. The value of this parameter is a string specifying the data type of the input. This must be one of: `boolean`, `number`, or `string`. + +## `on.workflow_call.secrets` + +A map of the secrets that can be used in the called workflow. + +Within the called workflow, you can use the `secrets` context to refer to a secret. + +If a caller workflow passes a secret that is not specified in the called workflow, this results in an error. + +### 示例 + +{% raw %} +```yaml +on: + workflow_call: + secrets: + access-token: + description: 'A token passed from the caller workflow' + required: false + +jobs: + pass-secret-to-action: + runs-on: ubuntu-latest + + steps: + - name: Pass the received secret to an action + uses: ./.github/actions/my-action@v1 + with: + token: ${{ secrets.access-token }} +``` +{% endraw %} + +## `on.workflow_call.secrets.` + +A string identifier to associate with the secret. + +## `on.workflow_call.secrets..required` + +A boolean specifying whether the secret must be supplied. +{% endif %} + ## `on.workflow_dispatch.inputs` -When using `workflow_dispatch` event, you can optionally specify inputs that are passed to the workflow. Workflow dispatch inputs are specified with the same format as action inputs. For more information about the format see "[Metadata syntax for GitHub Actions](/actions/creating-actions/metadata-syntax-for-github-actions#inputs)." +When using the `workflow_dispatch` event, you can optionally specify inputs that are passed to the workflow. Workflow dispatch inputs are specified with the same format as action inputs. For more information about the format see "[Metadata syntax for GitHub Actions](/actions/creating-actions/metadata-syntax-for-github-actions#inputs)." ```yaml on: @@ -272,8 +353,6 @@ defaults: {% ifversion fpt or ghae-next or ghes > 3.1 %} ## `concurrency` -{% data reusables.actions.concurrency-beta %} - Concurrency 确保只有使用相同并发组的单一作业或工作流程才会同时运行。 并发组可以是任何字符串或表达式。 The expression can only use the [`github` context](/actions/learn-github-actions/contexts#github-context). For more information about expressions, see "[Expressions](/actions/learn-github-actions/expressions)." 您也可以在作业级别指定 `concurrency`。 更多信息请参阅 [`jobs..concurrency`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idconcurrency)。 @@ -428,7 +507,7 @@ jobs: {% ifversion fpt or ghes > 3.0 or ghae %} ## `jobs..environment` -作业引用的环境。 在将引用环境的作业发送到运行器之前，必须通过所有环境保护规则。 更多信息请参阅“[环境](/actions/reference/environments)”。 +作业引用的环境。 在将引用环境的作业发送到运行器之前，必须通过所有环境保护规则。 For more information, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." 您可以将环境仅作为环境 `name`，或作为具有 `name` 和 `url` 的环境变量。 URL 映射到部署 API 中的 `environment_url`。 有关部署 API 的更多信息，请参阅“[部署](/rest/reference/repos#deployments)”。 @@ -463,8 +542,6 @@ environment: {% ifversion fpt or ghae-next or ghes > 3.1 %} ## `jobs..concurrency` -{% data reusables.actions.concurrency-beta %} - {% note %} **注意：** 在作业级别指定并发时，无法保证在 5 分钟内排队的作业或运行的互相顺序。 @@ -1248,7 +1325,7 @@ volumes: {% warning %} -**Warning:** The `--network` option is not supported. +**警告**：不支持 `--network` 选项。 {% endwarning %} @@ -1344,10 +1421,74 @@ volumes: {% warning %} -**Warning:** The `--network` option is not supported. +**警告**：不支持 `--network` 选项。 {% endwarning %} +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## `jobs..uses` + +The location and version of a reusable workflow file to run as a job. + +`{owner}/{repo}/{path}/{filename}@{ref}` + +`{ref}` can be a SHA, a release tag, or a branch name. Using the commit SHA is the safest for stability and security. 更多信息请参阅“[GitHub Actions 的安全性增强](/actions/learn-github-actions/security-hardening-for-github-actions#reusing-third-party-workflows)”。 + +### 示例 + +{% data reusables.actions.uses-keyword-example %} + +For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." + +## `jobs..with` + +When a job is used to call a reusable workflow, you can use `with` to provide a map of inputs that are passed to the called workflow. + +Any inputs that you pass must match the input specifications defined in the called workflow. + +Unlike [`jobs..steps[*].with`](#jobsjob_idstepswith), the inputs you pass with `jobs..with` are not be available as environment variables in the called workflow. Instead, you can reference the inputs by using the `inputs` context. + +### 示例 + +```yaml +jobs: + call-workflow: + uses: octo-org/example-repo/.github/workflows/called-workflow.yml@main + with: + username: mona +``` + +## `jobs..with.` + +A pair consisting of a string identifier for the input and the value of the input. The identifier must match the name of an input defined by [`on.workflow_call.inputs.`](/actions/creating-actions/metadata-syntax-for-github-actions#inputsinput_id) in the called workflow. The data type of the value must match the type defined by [`on.workflow_call..type`](#onworkflow_callinput_idtype) in the called workflow. + +Allowed expression contexts: `github`, and `needs`. + +## `jobs..secrets` + +When a job is used to call a reusable workflow, you can use `secrets` to provide a map of secrets that are passed to the called workflow. + +Any secrets that you pass must match the names defined in the called workflow. + +### 示例 + +{% raw %} +```yaml +jobs: + call-workflow: + uses: octo-org/example-repo/.github/workflows/called-workflow.yml@main + secrets: + access-token: ${{ secrets.PERSONAL_ACCESS_TOKEN }} +``` +{% endraw %} + +## `jobs..secrets.` + +A pair consisting of a string identifier for the secret and the value of the secret. The identifier must match the name of a secret defined by [`on.workflow_call.secrets.`](#onworkflow_callsecretssecret_id) in the called workflow. + +Allowed expression contexts: `github`, `needs`, and `secrets`. +{% endif %} + ## 过滤器模式备忘清单 您可以在路径、分支和标记过滤器中使用特殊字符。 diff --git a/translations/zh-CN/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md b/translations/zh-CN/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md index 9c854971a2..a9634d9613 100644 --- a/translations/zh-CN/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md +++ b/translations/zh-CN/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md @@ -16,8 +16,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## 简介 diff --git a/translations/zh-CN/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md b/translations/zh-CN/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md index 19b4df8b30..9ff7675d8e 100644 --- a/translations/zh-CN/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md +++ b/translations/zh-CN/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md @@ -16,8 +16,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## 简介 diff --git a/translations/zh-CN/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md b/translations/zh-CN/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md index 4e0d54b067..8f4d6451a4 100644 --- a/translations/zh-CN/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md +++ b/translations/zh-CN/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md @@ -17,8 +17,6 @@ shortTitle: 添加标签以评论议题 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## 简介 diff --git a/translations/zh-CN/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md b/translations/zh-CN/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md index 40fb3755dc..f949aceef1 100644 --- a/translations/zh-CN/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md +++ b/translations/zh-CN/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md @@ -17,8 +17,6 @@ shortTitle: 移动分配的议题 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## 简介 diff --git a/translations/zh-CN/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md b/translations/zh-CN/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md index b1393aef74..b1f71eba53 100644 --- a/translations/zh-CN/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md +++ b/translations/zh-CN/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md @@ -17,8 +17,6 @@ shortTitle: 添加卡片时删除标签 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## 简介 diff --git a/translations/zh-CN/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md b/translations/zh-CN/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md index 6a476870c4..138c33e89a 100644 --- a/translations/zh-CN/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md +++ b/translations/zh-CN/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md @@ -16,8 +16,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## 简介 diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md b/translations/zh-CN/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md index b9637dc922..5d4dfa5814 100644 --- a/translations/zh-CN/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md +++ b/translations/zh-CN/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md @@ -9,7 +9,9 @@ shortTitle: 批准公共复刻运行 ## 关于公共复刻中的工作流程运行 -{% data reusables.actions.workflow-run-approve-public-fork %} However, you can configure this behavior for a [repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks), [organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#configuring-required-approval-for-workflows-from-public-forks), or [enterprise](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account#configuring-required-approval-for-workflows-from-public-forks). +{% data reusables.actions.workflow-run-approve-public-fork %} + +You can configure workflow approval requirements for a [repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks), [organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#configuring-required-approval-for-workflows-from-public-forks), or [enterprise](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account#configuring-required-approval-for-workflows-from-public-forks). 已等待批准超过 30 天的工作流程运行将自动删除。 diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/canceling-a-workflow.md b/translations/zh-CN/content/actions/managing-workflow-runs/canceling-a-workflow.md index db1c239282..1db36f7450 100644 --- a/translations/zh-CN/content/actions/managing-workflow-runs/canceling-a-workflow.md +++ b/translations/zh-CN/content/actions/managing-workflow-runs/canceling-a-workflow.md @@ -10,7 +10,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.repositories.permissions-statement-write %} diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/deleting-a-workflow-run.md b/translations/zh-CN/content/actions/managing-workflow-runs/deleting-a-workflow-run.md index 860243fcb9..5dd739224a 100644 --- a/translations/zh-CN/content/actions/managing-workflow-runs/deleting-a-workflow-run.md +++ b/translations/zh-CN/content/actions/managing-workflow-runs/deleting-a-workflow-run.md @@ -10,7 +10,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.repositories.permissions-statement-write %} diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md b/translations/zh-CN/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md index 869fac03a0..78cc17f55c 100644 --- a/translations/zh-CN/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md +++ b/translations/zh-CN/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md @@ -11,7 +11,6 @@ shortTitle: 禁用和启用工作流程 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} 禁用工作流程允许您停止触发工作流程，而不必从仓库中删除文件。 您可以轻松地在 {% data variables.product.prodname_dotcom %} 上重新启用工作流程。 diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md b/translations/zh-CN/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md index e93181422d..1c45277aec 100644 --- a/translations/zh-CN/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md +++ b/translations/zh-CN/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md @@ -11,7 +11,6 @@ shortTitle: 下载工作流程构件 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% ifversion fpt or ghes > 2.22 or ghae %} 默认情况下，{% data variables.product.product_name %} 存储 90 天内的构建日志和构件，并且您可以根据仓库类型自定义此保留期。 For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)."{% endif %} {% ifversion ghes = 2.22 %} {% data variables.product.product_name %} 存储 90 天的完整构建日志和构件。{% endif %} diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/index.md b/translations/zh-CN/content/actions/managing-workflow-runs/index.md index 7fc513ce50..da4341ffdd 100644 --- a/translations/zh-CN/content/actions/managing-workflow-runs/index.md +++ b/translations/zh-CN/content/actions/managing-workflow-runs/index.md @@ -19,6 +19,7 @@ children: - /approving-workflow-runs-from-public-forks - /reviewing-deployments - /disabling-and-enabling-a-workflow + - /skipping-workflow-runs - /deleting-a-workflow-run - /downloading-workflow-artifacts - /removing-workflow-artifacts @@ -26,5 +27,3 @@ children: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% ifversion fpt or ghes > 3.0 or ghae %}{% endif %} diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/manually-running-a-workflow.md b/translations/zh-CN/content/actions/managing-workflow-runs/manually-running-a-workflow.md index 7c5f1acef8..104588c332 100644 --- a/translations/zh-CN/content/actions/managing-workflow-runs/manually-running-a-workflow.md +++ b/translations/zh-CN/content/actions/managing-workflow-runs/manually-running-a-workflow.md @@ -11,7 +11,6 @@ shortTitle: 手动运行工作流程 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 配置工作流程手动运行 diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/re-running-a-workflow.md b/translations/zh-CN/content/actions/managing-workflow-runs/re-running-a-workflow.md index 4618260bdd..24d10fb8e6 100644 --- a/translations/zh-CN/content/actions/managing-workflow-runs/re-running-a-workflow.md +++ b/translations/zh-CN/content/actions/managing-workflow-runs/re-running-a-workflow.md @@ -11,7 +11,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} Re-running a workflow uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (Git ref) of the original event that triggered the workflow run. You can re-run a workflow up to 30 days after the initial run. diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/removing-workflow-artifacts.md b/translations/zh-CN/content/actions/managing-workflow-runs/removing-workflow-artifacts.md index c77ec85b69..7647191149 100644 --- a/translations/zh-CN/content/actions/managing-workflow-runs/removing-workflow-artifacts.md +++ b/translations/zh-CN/content/actions/managing-workflow-runs/removing-workflow-artifacts.md @@ -11,7 +11,6 @@ shortTitle: 删除工作流程构件 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 删除构件 diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/reviewing-deployments.md b/translations/zh-CN/content/actions/managing-workflow-runs/reviewing-deployments.md index a488c615a0..0cd8ecd23d 100644 --- a/translations/zh-CN/content/actions/managing-workflow-runs/reviewing-deployments.md +++ b/translations/zh-CN/content/actions/managing-workflow-runs/reviewing-deployments.md @@ -8,16 +8,14 @@ versions: ghae: '*' --- -{% data reusables.actions.environments-beta %} -{% data reusables.actions.ae-beta %} -### 关于工作流程中所需的审查 +## 关于工作流程中所需的审查 引用配置了所需审查者的环境的作业将等待审批后再开始。 当作业正在等待批准时，其状态为“等待”。 如果作业在 30 天内未获得批准，工作流程运行将自动取消。 -For more information about environments and required approvals, see "[Environments](/actions/reference/environments)."{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %} For information about how to review deployments with the REST API, see "[Workflow Runs](/rest/reference/actions#workflow-runs)."{% endif %} +For more information about environments and required approvals, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)."{% ifversion fpt or ghae-next or ghes > 3.1 %} For information about how to review deployments with the REST API, see "[Workflow Runs](/rest/reference/actions#workflow-runs)."{% endif %} -### 批准或拒绝作业 +## 批准或拒绝作业 1. 导航到需要审核的工作流程运行。 有关导航到工作流程运行的更多信息，请参阅“[查看工作流程运行历史记录](/actions/managing-workflow-runs/viewing-workflow-run-history)”。 2. 单击 **Review deployments（审查部署）**。 ![审查部署](/assets/images/actions-review-deployments.png) diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/skipping-workflow-runs.md b/translations/zh-CN/content/actions/managing-workflow-runs/skipping-workflow-runs.md new file mode 100644 index 0000000000..9f8536c925 --- /dev/null +++ b/translations/zh-CN/content/actions/managing-workflow-runs/skipping-workflow-runs.md @@ -0,0 +1,33 @@ +--- +title: 跳过工作流程运行 +intro: You can skip workflow runs triggered by the `push` and `pull_request` events by including a command in your commit message. +product: '{% data reusables.gated-features.actions %}' +versions: + fpt: '*' + ghes: '>=3.0' + ghae: ghae-next +shortTitle: Skip workflow runs +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +Workflows that would otherwise be triggered using `on: push` or `on: pull_request` won't be triggered if you add any of the following strings to the commit message in a push, or the HEAD commit of a pull request: + +* `[skip ci]` +* `[ci skip]` +* `[no ci]` +* `[skip actions]` +* `[actions skip]` + +或者，您也可以使用两个空行后接 `skip-checks: true` 或 `skip-checks:true` 来结束提交消息。 + +如果您的仓库配置为需要先通过特定检查，则无法合并拉取请求。 要允许合并拉取请求，您可以将新提交推送到拉取请求，而无需提交消息中的跳过指令。 + +{% note %} + +**注意：**跳过指令仅适用于 `push` 和 `pull_request` 事件。 例如，将 `[skip ci]` 添加到提交消息不会停止触发 `on: pull_request_target` 的工作流程运行。 + +{% endnote %} + +Skip instructions only apply to the workflow run(s) that would be triggered by the commit that contains the skip instructions. You can also disable a workflow from running. 更多信息请参阅“[禁用和启用工作流程](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)。 diff --git a/translations/zh-CN/content/actions/migrating-to-github-actions/index.md b/translations/zh-CN/content/actions/migrating-to-github-actions/index.md index 4f4ae6885a..086c988b28 100644 --- a/translations/zh-CN/content/actions/migrating-to-github-actions/index.md +++ b/translations/zh-CN/content/actions/migrating-to-github-actions/index.md @@ -1,7 +1,7 @@ --- title: 迁移到 GitHub Actions shortTitle: 迁移到 GitHub Actions -intro: 'Learn how to migrate your existing CI/CD workflows to {% data variables.product.prodname_actions %}.' +intro: '了解如何将现有的 CI/CD 工作流程迁移到 {% data variables.product.prodname_actions %}。' versions: fpt: '*' ghes: '*' diff --git a/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md b/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md index 99e49bafb9..bcc556992d 100644 --- a/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md +++ b/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md @@ -19,7 +19,6 @@ shortTitle: 从 Azure Pelines 迁移 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 简介 diff --git a/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md b/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md index dd5b16329a..d9086ee9b0 100644 --- a/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md +++ b/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md @@ -19,7 +19,6 @@ shortTitle: 从 CircleCI 迁移 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 简介 diff --git a/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md b/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md index 5c3442b65a..26a0cebac5 100644 --- a/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md +++ b/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md @@ -18,7 +18,6 @@ shortTitle: 从 GitLab CI/CD 迁移 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 简介 diff --git a/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md b/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md index 5570222026..b291e0f671 100644 --- a/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md +++ b/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md @@ -19,7 +19,6 @@ shortTitle: 从 Jenkins 迁移 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 简介 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 971c6b399a..f0f614e3f6 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 @@ -19,7 +19,6 @@ shortTitle: 从 Travis CI 迁移 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 简介 diff --git a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md index 7a035f5843..fe1fc29d55 100644 --- a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md +++ b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md @@ -12,7 +12,6 @@ miniTocMaxHeadingLevel: 3 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## Monitoring your workflows diff --git a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md index 6da1843483..626ac5137d 100644 --- a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md +++ b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md @@ -13,7 +13,6 @@ shortTitle: 添加状态徽章 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.repositories.actions-workflow-status-badge-intro %} diff --git a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md index 952a802537..b26c965018 100644 --- a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md +++ b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md @@ -12,7 +12,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} 这些额外的日志将通过在包含工作流程的仓库中设置密码来启用，因此将应用相同的权限要求： diff --git a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/index.md b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/index.md index 950ed01f44..a8e2871b5a 100644 --- a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/index.md +++ b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/index.md @@ -17,9 +17,8 @@ children: - /viewing-job-execution-time - /using-workflow-run-logs - /enabling-debug-logging + - /notifications-for-workflow-runs --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% ifversion fpt or ghes > 3.0 or ghae %}{% endif %} diff --git a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md new file mode 100644 index 0000000000..9a8ebbbbea --- /dev/null +++ b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md @@ -0,0 +1,15 @@ +--- +title: 工作流程运行通知 +intro: You can subscribe to notifications about workflow runs that you trigger. +product: '{% data reusables.gated-features.actions %}' +versions: + fpt: '*' + ghes: '*' + ghae: '*' +shortTitle: 通知 +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +{% data reusables.repositories.workflow-notifications %} diff --git a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md index a6cc88ce20..309a81627f 100644 --- a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md +++ b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md @@ -13,7 +13,6 @@ shortTitle: 使用可视化图表 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} diff --git a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md index dce1d5065a..f0bf833942 100644 --- a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md +++ b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md @@ -12,7 +12,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} 您可以从工作流程运行页面查看工作流程运行是在进行中，还是已完成。 您必须登录到 {% data variables.product.prodname_dotcom %} 帐户才能查看工作流程运行信息，包括公共仓库。 更多信息请参阅“[GitHub 上的访问权限](/articles/access-permissions-on-github)”。 diff --git a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md index 660694c3c3..a05077a747 100644 --- a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md +++ b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md @@ -11,7 +11,6 @@ shortTitle: 查看作业执行时间 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} 仅为在私有仓库上运行，使用 {% data variables.product.prodname_dotcom %}- 托管的运行器的作业显示可计费作业执行分钟数。 如果在公共仓库中使用 {% data variables.product.prodname_actions %}，或在自托管的运行器中运行作业时，将没有可计费分钟数。 diff --git a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md index a45ceaa94c..739b9278cf 100644 --- a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md +++ b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md @@ -13,7 +13,6 @@ shortTitle: 查看工作流程运行历史记录 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.repositories.permissions-statement-read %} diff --git a/translations/zh-CN/content/actions/publishing-packages/about-packaging-with-github-actions.md b/translations/zh-CN/content/actions/publishing-packages/about-packaging-with-github-actions.md index 623c387ca9..51b19354b9 100644 --- a/translations/zh-CN/content/actions/publishing-packages/about-packaging-with-github-actions.md +++ b/translations/zh-CN/content/actions/publishing-packages/about-packaging-with-github-actions.md @@ -18,7 +18,6 @@ shortTitle: 使用 GitHub Actions 进行打包 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.package_registry.about-packaging-and-actions %} diff --git a/translations/zh-CN/content/actions/publishing-packages/publishing-docker-images.md b/translations/zh-CN/content/actions/publishing-packages/publishing-docker-images.md index 9de20b54b0..02128fb834 100644 --- a/translations/zh-CN/content/actions/publishing-packages/publishing-docker-images.md +++ b/translations/zh-CN/content/actions/publishing-packages/publishing-docker-images.md @@ -18,7 +18,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 简介 diff --git a/translations/zh-CN/content/actions/publishing-packages/publishing-java-packages-with-gradle.md b/translations/zh-CN/content/actions/publishing-packages/publishing-java-packages-with-gradle.md index 0561addce5..ba1d0eaf39 100644 --- a/translations/zh-CN/content/actions/publishing-packages/publishing-java-packages-with-gradle.md +++ b/translations/zh-CN/content/actions/publishing-packages/publishing-java-packages-with-gradle.md @@ -20,7 +20,6 @@ shortTitle: 带有 Gradle 的 Java 包 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 简介 diff --git a/translations/zh-CN/content/actions/publishing-packages/publishing-java-packages-with-maven.md b/translations/zh-CN/content/actions/publishing-packages/publishing-java-packages-with-maven.md index a2dd82e754..b92875f06b 100644 --- a/translations/zh-CN/content/actions/publishing-packages/publishing-java-packages-with-maven.md +++ b/translations/zh-CN/content/actions/publishing-packages/publishing-java-packages-with-maven.md @@ -20,7 +20,6 @@ shortTitle: 带有 Maven 的 Java 包 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 简介 diff --git a/translations/zh-CN/content/actions/publishing-packages/publishing-nodejs-packages.md b/translations/zh-CN/content/actions/publishing-packages/publishing-nodejs-packages.md index 2ec1917c12..00cad4d583 100644 --- a/translations/zh-CN/content/actions/publishing-packages/publishing-nodejs-packages.md +++ b/translations/zh-CN/content/actions/publishing-packages/publishing-nodejs-packages.md @@ -21,7 +21,6 @@ shortTitle: Node.js 包 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 简介 diff --git a/translations/zh-CN/content/actions/quickstart.md b/translations/zh-CN/content/actions/quickstart.md index c2e81db84f..6bc7c70690 100644 --- a/translations/zh-CN/content/actions/quickstart.md +++ b/translations/zh-CN/content/actions/quickstart.md @@ -16,7 +16,6 @@ shortTitle: 快速入门 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 简介 diff --git a/translations/zh-CN/content/actions/security-guides/automatic-token-authentication.md b/translations/zh-CN/content/actions/security-guides/automatic-token-authentication.md index 1007b248a2..601bc9d473 100644 --- a/translations/zh-CN/content/actions/security-guides/automatic-token-authentication.md +++ b/translations/zh-CN/content/actions/security-guides/automatic-token-authentication.md @@ -16,7 +16,6 @@ shortTitle: Automatic token authentication {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 关于 `GITHUB_TOKEN` 密码 diff --git a/translations/zh-CN/content/actions/security-guides/encrypted-secrets.md b/translations/zh-CN/content/actions/security-guides/encrypted-secrets.md index 4d4bc4ff8a..e2884db26f 100644 --- a/translations/zh-CN/content/actions/security-guides/encrypted-secrets.md +++ b/translations/zh-CN/content/actions/security-guides/encrypted-secrets.md @@ -16,7 +16,6 @@ versions: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 关于加密密码 diff --git a/translations/zh-CN/content/actions/security-guides/security-hardening-for-github-actions.md b/translations/zh-CN/content/actions/security-guides/security-hardening-for-github-actions.md index 1df6f668e1..bf57fc4771 100644 --- a/translations/zh-CN/content/actions/security-guides/security-hardening-for-github-actions.md +++ b/translations/zh-CN/content/actions/security-guides/security-hardening-for-github-actions.md @@ -18,7 +18,6 @@ miniTocMaxHeadingLevel: 3 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 概览 @@ -48,7 +47,7 @@ miniTocMaxHeadingLevel: 3 - 定期轮换密码，以减小泄露的密码有效的时间窗。 {% ifversion fpt or ghes > 3.0 or ghae %} - **考虑要求对访问密码进行审查** - - 您可以使用所需的审查者来保护环境机密。 在审查者批准之前，工作流程作业无法访问环境机密。 有关在环境中存储机密或需要审查环境的更多信息，请参阅“[加密秘密](/actions/reference/encrypted-secrets)”和“[环境](/actions/reference/environments)”。 + - 您可以使用所需的审查者来保护环境机密。 在审查者批准之前，工作流程作业无法访问环境机密。 For more information about storing secrets in environments or requiring reviews for environments, see "[Encrypted secrets](/actions/reference/encrypted-secrets)" and "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." {% endif %} ## 使用 `CODEOWNERS` 监控更改 @@ -183,6 +182,12 @@ with: 尽管固定到提交 SHA 是最安全的选项，但指定标记更方便，而且被广泛使用。 如果要指定标记，请确保信任该操作的创建者。 {% data variables.product.prodname_marketplace %} 上的“已验证创建者”徽章是一个有用的信号，因为它表示该操作是由其身份已被 {% data variables.product.prodname_dotcom %} 验证的团队编写的。 请注意，即使您信任作者，这种方法也存在风险，因为如果恶意执行者获得对存储操作的仓库的访问权限，便可移动或删除标记。 +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## Reusing third-party workflows + +The same principles described above for using third-party actions also apply to using third-party workflows. You can help mitigate the risks associated with reusing workflows by following the same good practices outlined above. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." +{% endif %} + ## 受损运行器的潜在影响 这些部分考虑了当攻击者能够对 {% data variables.product.prodname_actions %} 运行器运行恶意命令时可以采取的一些步骤。 diff --git a/translations/zh-CN/content/actions/using-containerized-services/about-service-containers.md b/translations/zh-CN/content/actions/using-containerized-services/about-service-containers.md index bca430d87f..3a6fece711 100644 --- a/translations/zh-CN/content/actions/using-containerized-services/about-service-containers.md +++ b/translations/zh-CN/content/actions/using-containerized-services/about-service-containers.md @@ -18,7 +18,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 关于服务容器 diff --git a/translations/zh-CN/content/actions/using-containerized-services/creating-postgresql-service-containers.md b/translations/zh-CN/content/actions/using-containerized-services/creating-postgresql-service-containers.md index 3ea9e0ce7c..f241c2f7ff 100644 --- a/translations/zh-CN/content/actions/using-containerized-services/creating-postgresql-service-containers.md +++ b/translations/zh-CN/content/actions/using-containerized-services/creating-postgresql-service-containers.md @@ -19,7 +19,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 简介 diff --git a/translations/zh-CN/content/actions/using-containerized-services/creating-redis-service-containers.md b/translations/zh-CN/content/actions/using-containerized-services/creating-redis-service-containers.md index 9aceca24bf..8df8798cdc 100644 --- a/translations/zh-CN/content/actions/using-containerized-services/creating-redis-service-containers.md +++ b/translations/zh-CN/content/actions/using-containerized-services/creating-redis-service-containers.md @@ -19,7 +19,6 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 简介 diff --git a/translations/zh-CN/content/actions/using-github-hosted-runners/about-ae-hosted-runners.md b/translations/zh-CN/content/actions/using-github-hosted-runners/about-ae-hosted-runners.md index 89212053a7..377fc6d827 100644 --- a/translations/zh-CN/content/actions/using-github-hosted-runners/about-ae-hosted-runners.md +++ b/translations/zh-CN/content/actions/using-github-hosted-runners/about-ae-hosted-runners.md @@ -6,23 +6,16 @@ versions: ghae: '*' --- - - - -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} ## 关于 {% data variables.actions.hosted_runner %} -{% data variables.actions.hosted_runner %} 是由安装了 {% data variables.product.prodname_dotcom %} 运行器服务的 {% data variables.product.prodname_actions %} 托管的虚拟机。 +An {% data variables.actions.hosted_runner %} is a virtual machine managed by {% data variables.product.prodname_dotcom %} with the {% data variables.product.prodname_actions %} runner service installed. {% data variables.actions.hosted_runner %}s are dedicated to your enterprise, and you can choose from a range of hardware and software options. By default, {% data variables.actions.hosted_runner %}s are fully managed and auto-scaled by {% data variables.product.company_short %} to maximize performance while minimizing costs.{% ifversion ghae-next %} You can optionally configure the parameters of this auto-scaling to reduce your cost even more.{% endif %} -{% data variables.product.prodname_ghe_managed %} 允许您使用 Ubuntu 或 Windows 映像创建和自定义 {% data variables.actions.hosted_runner %}；您可以选择您想要的机器大小并为其配置安全增强的网络。 {% data variables.actions.hosted_runner %} 由 {% data variables.product.prodname_dotcom %} 全面管理和自动扩展。 +{% data variables.product.prodname_ghe_managed %} lets you create and customize {% data variables.actions.hosted_runner %}s using Ubuntu or Windows images; you can select the size of machine you want and optionally configure a fixed public IP range for your {% data variables.actions.hosted_runner %}s. 每个工作流程作业都是在 {% data variables.actions.hosted_runner %} 的新实例中执行，您可以直接在虚拟机上或 Docker 容器中运行工作流程。 作业中的所有步骤都在同一实例中执行，允许该作业中的操作使用 {% data variables.actions.hosted_runner %} 的文件系统共享信息。 -{% note %} -{% data variables.actions.hosted_runner %} 是唯一可用于 {% data variables.product.prodname_ghe_managed %} 的运行器，而自托管的运行器则不可用。 -{% endnote %} - 要将 {% data variables.actions.hosted_runner %} 添加到您的组织或企业，请参阅[“添加 {% data variables.actions.hosted_runner %}](/actions/using-github-hosted-runners/adding-ae-hosted-runners)”。 ## {% data variables.actions.hosted_runner %} 的资源池分配 @@ -35,11 +28,9 @@ versions: ## 计费 -{% data variables.product.prodname_actions %} 目前正在测试用于 {% data variables.product.prodname_ghe_managed %} 。 在此测试阶段，{% data variables.actions.hosted_runner %} 不会计费，可以免费使用。 - 测试结束后，计费使用将包括您的 AE 托管运行器集中活动实例的全时运行时间。 这包括： - 作业时间 - 运行 Actions 作业所用的分钟数。 -- 管理 - 重新映像机器所用的分钟数，以及因所需的自动扩展行为而产生的任何空闲时间。 +- Management - minutes spent re-imaging machines{% ifversion ghae-next %} and any idle time created as a result of desired auto-scale behavior{% endif %}. 定价将与核心线性扩展。 例如，4 核价格将是 2 核的两倍。 Windows 虚拟机的定价将高于 Linux 虚拟机。 @@ -78,6 +69,14 @@ versions: API 返回的 {% data variables.product.prodname_actions %} IP 地址列表每周更新一次。 +{% ifversion ghae-next %} + +## Autoscaling + +Each pool of {% data variables.actions.hosted_runner %}s is fully managed by {% data variables.product.company_short %} to maximize performance while minimizing costs. Optionally, you can configure the autoscaling parameters for your enterprise by contacting {% data variables.contact.github_support %}. You can define the minimum number of idle runners and how long a runner should remain idle before being removed from the pool. Each pool can contain up to 600 runners. + +{% endif %} + ## {% data variables.actions.hosted_runner %} 的管理权限 Linux 虚拟机使用无密码的 `sudo` 运行。 在需要比当前用户更多的权限才能执行命令或安装工具时，您可以使用无需提供密码的 `sudo`。 更多信息请参阅“[Sudo 手册](https://www.sudo.ws/man/1.8.27/sudo.man.html)”。 diff --git a/translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md index 7003556e46..af8b19fb55 100644 --- a/translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md +++ b/translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md @@ -16,6 +16,7 @@ versions: shortTitle: GitHub 托管的运行器 --- +{% data reusables.actions.ae-hosted-runners-beta %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} diff --git a/translations/zh-CN/content/actions/using-github-hosted-runners/adding-ae-hosted-runners.md b/translations/zh-CN/content/actions/using-github-hosted-runners/adding-ae-hosted-runners.md index 03a442883b..f246bdceb5 100644 --- a/translations/zh-CN/content/actions/using-github-hosted-runners/adding-ae-hosted-runners.md +++ b/translations/zh-CN/content/actions/using-github-hosted-runners/adding-ae-hosted-runners.md @@ -5,7 +5,7 @@ versions: ghae: '*' --- -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} {% note %} @@ -19,7 +19,8 @@ versions: 您可以添加使用基础 Azure 操作系统映像的 {% data variables.actions.hosted_runner %}。 要将 {% data variables.actions.hosted_runner %} 添加到您的组织或企业，请联系 {% data variables.product.prodname_dotcom %} 支持并备好以下信息： - 所需的操作系统：可用选项请参阅[“软件规格](/actions/using-github-hosted-runners/about-ae-hosted-runners#software-specifications)”。 - - 为每个 {% data variables.actions.hosted_runner %} 池选择一个名称。 这些名称被创建为标签，允许您将工作流程路由到这些运行器。 更多信息请参阅[“在工作流程中使用 {% data variables.actions.hosted_runner %}](/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow)”。 + - 为每个 {% data variables.actions.hosted_runner %} 池选择一个名称。 这些名称被创建为标签，允许您将工作流程路由到这些运行器。 For more information, see ["Using {% data variables.actions.hosted_runner %}s in a workflow](/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow)."{% ifversion ghae-next %} +{% data reusables.actions.autoscaling-parameters %}{% endif %} - 将 {% data variables.actions.hosted_runner %} 添加到何处：确定将接收该运行器的组织和企业的名称。 ## 使用自定义映像添加 {% data variables.actions.hosted_runner %} @@ -33,7 +34,8 @@ versions: - 映像名称： - 版本. - 新池的 VM SKU。 - - 为每个 {% data variables.actions.hosted_runner %} 池选择一个名称。 这些名称被创建为标签，允许您将工作流程路由到这些运行器。 更多信息请参阅[“在工作流程中使用 {% data variables.actions.hosted_runner %}](/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow)”。 + - 为每个 {% data variables.actions.hosted_runner %} 池选择一个名称。 这些名称被创建为标签，允许您将工作流程路由到这些运行器。 For more information, see ["Using {% data variables.actions.hosted_runner %}s in a workflow](/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow)."{% ifversion ghae-next %} +{% data reusables.actions.autoscaling-parameters %}{% endif %} - 将 {% data variables.actions.hosted_runner %} 添加到何处：确定将接收该运行器的组织和企业的名称。 ## 查看您的 {% data variables.actions.hosted_runner %} diff --git a/translations/zh-CN/content/actions/using-github-hosted-runners/creating-custom-images.md b/translations/zh-CN/content/actions/using-github-hosted-runners/creating-custom-images.md index ba03bdfe00..dfc7e536c4 100644 --- a/translations/zh-CN/content/actions/using-github-hosted-runners/creating-custom-images.md +++ b/translations/zh-CN/content/actions/using-github-hosted-runners/creating-custom-images.md @@ -5,7 +5,7 @@ versions: ghae: '*' --- -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} ## 使用自定义映像创建 {% data variables.actions.hosted_runner %} diff --git a/translations/zh-CN/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md b/translations/zh-CN/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md index 363d368132..ad67124c06 100644 --- a/translations/zh-CN/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md +++ b/translations/zh-CN/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md @@ -11,6 +11,7 @@ topics: shortTitle: 自定义运行器 --- +{% data reusables.actions.ae-hosted-runners-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} 如果 {% data variables.product.prodname_dotcom %} 托管的运行器上需要其他软件包，您可以创建一个作业，将包的安装作为工作流程的一部分。 diff --git a/translations/zh-CN/content/actions/using-github-hosted-runners/index.md b/translations/zh-CN/content/actions/using-github-hosted-runners/index.md index 630c79fd57..d762916f77 100644 --- a/translations/zh-CN/content/actions/using-github-hosted-runners/index.md +++ b/translations/zh-CN/content/actions/using-github-hosted-runners/index.md @@ -17,5 +17,6 @@ children: shortTitle: 使用 GitHub 托管的运行器 --- +{% data reusables.actions.ae-hosted-runners-beta %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} diff --git a/translations/zh-CN/content/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow.md b/translations/zh-CN/content/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow.md index fbf0707e23..07871d4df2 100644 --- a/translations/zh-CN/content/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow.md +++ b/translations/zh-CN/content/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow.md @@ -6,7 +6,7 @@ versions: shortTitle: 使用 AE 托管的运行器 --- -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} ## 在工作流程中使用 {% data variables.actions.hosted_runner %} diff --git a/translations/zh-CN/content/actions/using-github-hosted-runners/using-groups-to-manage-access-to-ae-hosted-runners.md b/translations/zh-CN/content/actions/using-github-hosted-runners/using-groups-to-manage-access-to-ae-hosted-runners.md index 113ce6cae9..aec4ee0bbc 100644 --- a/translations/zh-CN/content/actions/using-github-hosted-runners/using-groups-to-manage-access-to-ae-hosted-runners.md +++ b/translations/zh-CN/content/actions/using-github-hosted-runners/using-groups-to-manage-access-to-ae-hosted-runners.md @@ -6,7 +6,7 @@ versions: shortTitle: 管理 AE 运行器组 --- -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} ## 关于 {% data variables.actions.hosted_runner %} 组 diff --git a/translations/zh-CN/content/actions/using-github-hosted-runners/using-labels-with-ae-hosted-runners.md b/translations/zh-CN/content/actions/using-github-hosted-runners/using-labels-with-ae-hosted-runners.md index d8c906705d..ef4b6b0fd4 100644 --- a/translations/zh-CN/content/actions/using-github-hosted-runners/using-labels-with-ae-hosted-runners.md +++ b/translations/zh-CN/content/actions/using-github-hosted-runners/using-labels-with-ae-hosted-runners.md @@ -6,7 +6,7 @@ versions: shortTitle: 标识 AE 托管的运行器 --- -{% data reusables.actions.ae-beta %} +{% data reusables.actions.ae-hosted-runners-beta %} 有关如何使用标签将作业路由到特定类型的 {% data variables.actions.hosted_runner %} 的信息，请参阅“[在工作流程中使用 {% data variables.actions.hosted_runner %}](/actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow)”。 diff --git a/translations/zh-CN/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md b/translations/zh-CN/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md index 3288562a82..a7d4bbabb3 100644 --- a/translations/zh-CN/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md +++ b/translations/zh-CN/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md @@ -62,13 +62,13 @@ topics: {% ifversion ghes = 2.22 %} 要在 {% data variables.product.prodname_ghe_server %} 上使用 {% data variables.product.prodname_actions %} 运行 {% data variables.product.prodname_code_scanning %}，必须在本地可以进行适当的操作。 您可以通过三种方式使操作可用。 -- **推荐**：您可以使用 [{% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud) 自动从 {% data variables.product.prodname_dotcom_the_website %} 下载操作。 托管实例的机器必须能够访问 {% data variables.product.prodname_dotcom_the_website %}。 此方法可确保自动获取最新软件。 更多信息请参阅“[配置 {% data variables.product.prodname_github_connect %} 以同步 {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)”。 +- **推荐**：您可以使用 [{% data variables.product.prodname_github_connect %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud) 自动从 {% data variables.product.prodname_dotcom_the_website %} 下载操作。 托管实例的机器必须能够访问 {% data variables.product.prodname_dotcom_the_website %}。 此方法可确保自动获取最新软件。 更多信息请参阅“[配置 {% data variables.product.prodname_github_connect %} 以同步 {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)”。 - 如果要使用 {% data variables.product.prodname_codeql_workflow %}，可以使用 [https://github.com/github/codeql-action-sync-tool](https://github.com/github/codeql-action-sync-tool/) 上的 {% data variables.product.prodname_codeql %} 操作同步工具将仓库从 {% data variables.product.prodname_dotcom_the_website %} 同步到 {% data variables.product.prodname_ghe_server %}。 无论您的 {% data variables.product.product_location %} 或 {% data variables.product.prodname_actions %} 运行器是否可以访问互联网， 只要您可以同时在计算机上访问 {% data variables.product.product_location %} 和 {% data variables.product.prodname_dotcom_the_website %}，您都可以使用此工具。 - 您可以通过克隆包含操作的 {% data variables.product.prodname_dotcom_the_website %} 仓库，在服务器上创建操作仓库的本地副本。 例如，如果要使用 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} 操作，可以在实例中创建一个名为 `github/codeql-action` 的仓库，然后从 {% data variables.product.prodname_dotcom_the_website %} 克隆[仓库](https://github.com/github/codeql-action)，再将该仓库推送到实例的 `github/codeql-action` 仓库。 您还需要从 {% data variables.product.prodname_dotcom_the_website %} 上的仓库下载任何发行版，并将它们作为发行版上传到实例的 `github/codeql-action` 仓库。 {% endif %} ### 配置 {% data variables.product.prodname_github_connect %} 以同步 {% data variables.product.prodname_actions %} -1. 如果要从 {% data variables.product.prodname_dotcom_the_website %} 下载按需操作工作流程，则需要启用 {% data variables.product.prodname_github_connect %}。 更多信息请参阅“[启用 {% data variables.product.prodname_github_connect %}](/enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud#enabling-github-connect)”。 +1. 如果要从 {% data variables.product.prodname_dotcom_the_website %} 下载按需操作工作流程，则需要启用 {% data variables.product.prodname_github_connect %}。 更多信息请参阅“[启用 {% data variables.product.prodname_github_connect %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud#enabling-github-connect)”。 2. 您还需要为 {% data variables.product.product_location %} 启用 {% data variables.product.prodname_actions %}。 更多信息请参阅“[{% data variables.product.prodname_ghe_server %} 的 {% data variables.product.prodname_actions %} 使用入门](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)”。 3. 下一步是使用 {% data variables.product.prodname_github_connect %} 配置对 {% data variables.product.prodname_dotcom_the_website %} 上的操作的访问权限。 更多信息请参阅“[启用使用 {% data variables.product.prodname_github_connect %} 自动访问 {% data variables.product.prodname_dotcom_the_website %} 操作](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)”。 4. 将自托管运行器添加到仓库、组织或企业帐户。 更多信息请参阅“[添加自托管的运行器](/actions/hosting-your-own-runners/adding-self-hosted-runners)”。 diff --git a/translations/zh-CN/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md b/translations/zh-CN/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md index 181dc21a11..b9c8f5141a 100644 --- a/translations/zh-CN/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md @@ -83,10 +83,14 @@ For example, you can enable any {% data variables.product.prodname_GH_advanced_s ```shell ghe-config app.secret-scanning.enabled true ``` - - To enable {% data variables.product.prodname_dependabot %}, enter the following command. - ```shell - {% ifversion ghes > 3.1 %}ghe-config app.dependency-graph.enabled true{% else %}ghe-config app.github.dependency-graph-enabled true{% endif %} + - To enable {% data variables.product.prodname_dependabot %}, enter the following {% ifversion ghes > 3.1 %}command{% else %}commands{% endif %}. + {% ifversion ghes > 3.1 %}```shell + ghe-config app.dependency-graph.enabled true ``` + {% else %}```shell + ghe-config app.github.dependency-graph-enabled true + ghe-config app.github.vulnerability-alerting-and-settings-enabled true + ```{% endif %} 2. Optionally, disable features for {% data variables.product.prodname_GH_advanced_security %}. - To disable {% data variables.product.prodname_code_scanning %}, enter the following commands. @@ -98,11 +102,14 @@ For example, you can enable any {% data variables.product.prodname_GH_advanced_s ```shell ghe-config app.secret-scanning.enabled false ``` - - To disable {% data variables.product.prodname_dependabot %}, enter the following command. - ```shell - {% ifversion ghes > 3.1 %}ghe-config app.dependency-graph.enabled false{% else %}ghe-config app.github.dependency-graph-enabled false{% endif %} + - To disable {% data variables.product.prodname_dependabot %}, enter the following {% ifversion ghes > 3.1 %}command{% else %}commands{% endif %}. + {% ifversion ghes > 3.1 %}```shell + ghe-config app.dependency-graph.enabled false ``` - + {% else %}```shell + ghe-config app.github.dependency-graph-enabled false + ghe-config app.github.vulnerability-alerting-and-settings-enabled false + ```{% endif %} 3. 应用配置。 ```shell ghe-config-apply diff --git a/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md b/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md index 3d51595d1b..9747327b23 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md +++ b/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md @@ -23,7 +23,7 @@ shortTitle: 配置出站代理 {% note %} -**注**：要将 {% data variables.product.product_location %} 连接到 {% data variables.product.prodname_dotcom_the_website %}，您的代理配置必须允许连接到 `github.com` 和 `api.github.com`。 更多信息请参阅“[将 {% data variables.product.prodname_ghe_server %} 连接到 {% data variables.product.prodname_dotcom_the_website %}](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/connecting-github-enterprise-server-to-github-com)”。 +**注**：要将 {% data variables.product.product_location %} 连接到 {% data variables.product.prodname_dotcom_the_website %}，您的代理配置必须允许连接到 `github.com` 和 `api.github.com`。 For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_dotcom_the_website %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." {% endnote %} @@ -34,7 +34,7 @@ shortTitle: 配置出站代理 {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.privacy %} -4. 在 **HTTP Proxy Server** 下，输入代理服务器的 URL。 ![用于输入 HTTP 代理服务器 URL 的字段](/assets/images/enterprise/management-console/http-proxy-field.png) +1. 在 **HTTP Proxy Server** 下，输入代理服务器的 URL。 ![用于输入 HTTP 代理服务器 URL 的字段](/assets/images/enterprise/management-console/http-proxy-field.png) 5. 或者在 **HTTP Proxy Exclusion** 下输入不需要进行代理访问的任意主机，并以逗号分隔主机。 要将域中的所有主机排除在需要代理访问权限之外，您可以使用 `.` 作为通配符前缀。 例如：`.octo-org.tentacle` ![输入任何 HTTP 代理排除项的字段](/assets/images/enterprise/management-console/http-proxy-exclusion-field.png) 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 fc8f20e297..ee24aa22b6 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 @@ -351,18 +351,6 @@ stop/waiting - ghe-replica-mode ``` -{% tip %} - -如有需要，可将此命令返回的服务名称与 [`systemctl`](https://www.freedesktop.org/software/systemd/man/systemctl.html) 命令结合使用，以手动停止、启动或重启这些服务。 例如： - -```shell -$ sudo systemctl restart github-resqued -``` - -停止服务会导致安装停机，因此建议您在停止或重启任何服务之前联系 {% data variables.contact.contact_ent_support %}。 - -{% endtip %} - ### ghe-set-password 使用 `ghe-set-password`，您可以设置新密码，在 [{% data variables.enterprise.management_console %}](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-management-console) 中进行身份验证。 @@ -808,7 +796,7 @@ $ ssh -p 122 admin@hostname -- 'ghe-update-check' ### ghe-license-usage -此实用程序可按 JSON 格式导出安装用户列表。 如果您的实例连接至 {% data variables.product.prodname_ghe_cloud %}，{% data variables.product.prodname_ghe_server %} 将使用此信息向 {% data variables.product.prodname_ghe_cloud %} 报告许可信息。 更多信息请参阅“[将 {% data variables.product.prodname_ghe_server %} 连接至 {% data variables.product.prodname_ghe_cloud %} ](/enterprise/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)。” +此实用程序可按 JSON 格式导出安装用户列表。 如果您的实例连接至 {% data variables.product.prodname_ghe_cloud %}，{% data variables.product.prodname_ghe_server %} 将使用此信息向 {% data variables.product.prodname_ghe_cloud %} 报告许可信息。 For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %} ](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." 默认情况下，生成的 JSON 文件中的用户列表为加密格式。 使用 `-h` 标志可获取更多选项。 diff --git a/translations/zh-CN/content/admin/configuration/index.md b/translations/zh-CN/content/admin/configuration/index.md index 08e9c6099e..cf73878672 100644 --- a/translations/zh-CN/content/admin/configuration/index.md +++ b/translations/zh-CN/content/admin/configuration/index.md @@ -12,7 +12,7 @@ topics: children: - /configuring-your-enterprise - /configuring-network-settings - - /managing-connections-between-github-enterprise-server-and-github-enterprise-cloud + - /managing-connections-between-your-enterprise-accounts --- {% ifversion ghes %} diff --git a/translations/zh-CN/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md b/translations/zh-CN/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md new file mode 100644 index 0000000000..c16cbd0435 --- /dev/null +++ b/translations/zh-CN/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md @@ -0,0 +1,83 @@ +--- +title: Connecting your enterprise account to GitHub Enterprise Cloud +shortTitle: Connect enterprise accounts +intro: '启用 {% data variables.product.prodname_github_connect %} 后，您可以在 {% data variables.product.product_location %} 与 {% data variables.product.prodname_ghe_cloud %} 之间共用特定的功能和工作流程。' +redirect_from: + - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-to-github-com/ + - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-server-to-github-com + - /enterprise/admin/developer-workflow/connecting-github-enterprise-server-to-githubcom/ + - /enterprise/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud + - /enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud + - /admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud +permissions: 'Enterprise owners who are also owners of a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable {% data variables.product.prodname_github_connect %}.' +versions: + ghes: '*' + ghae: next +type: how_to +topics: + - Enterprise + - GitHub Connect + - Infrastructure + - Networking +--- + +{% data reusables.github-connect.beta %} + +## 关于 {% data variables.product.prodname_github_connect %} + +要启用 {% data variables.product.prodname_github_connect %}，必须在 {% data variables.product.product_location %} 和 {% data variables.product.prodname_ghe_cloud %} 组织或企业帐户中配置连接。 + +{% ifversion ghes %} +要配置连接，您的代理配置必须允许连接到 `github.com` 和 `api.github.com`。 更多信息请参阅“[配置出站 Web 代理服务器](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-an-outbound-web-proxy-server)”。 +{% endif %} + +启用 {% data variables.product.prodname_github_connect %} 后，您将能够启用统一搜索和统一贡献等功能。 For more information about all of the features available, see "[Managing connections between your enterprise accounts](/admin/configuration/managing-connections-between-your-enterprise-accounts)." + +将 {% data variables.product.product_location %} 连接到 {% data variables.product.prodname_ghe_cloud %} 时，{% data variables.product.prodname_dotcom_the_website %} 上会有一条记录存储连接的相关信息： +{% ifversion ghes %} +- {% data variables.product.prodname_ghe_server %} 许可的公钥部分 +- {% data variables.product.prodname_ghe_server %} 许可的哈希 +- {% data variables.product.prodname_ghe_server %} 许可上的客户名称 +- The version of {% data variables.product.product_location_enterprise %}{% endif %} +- The hostname of your {% data variables.product.product_name %} instance +- 连接至 {% data variables.product.product_location %} 的 {% data variables.product.prodname_dotcom_the_website %} 上的组织或企业帐户 +- {% data variables.product.product_location %} 用于向 {% data variables.product.prodname_dotcom_the_website %} 发送请求的身份验证令牌 + +启用 {% data variables.product.prodname_github_connect %} 也可以创建由您的 {% data variables.product.prodname_ghe_cloud %} 组织或企业帐户所拥有的 {% data variables.product.prodname_github_app %}。 {% data variables.product.product_name %} 使用 {% data variables.product.prodname_github_app %} 的凭据向 {% data variables.product.prodname_dotcom_the_website %} 发送请求。 +{% ifversion ghes %} +{% data variables.product.prodname_ghe_server %} 会存储来自 {% data variables.product.prodname_github_app %} 的凭据。 这些凭据将复制到任何高可用性或集群环境，并存储在任何备份中，包括由 {% data variables.product.prodname_enterprise_backup_utilities %} 创建的快照。 +- 有效期为一小时的身份验证令牌 +- 用于生成新的身份验证令牌的私钥 +{% endif %} + +启用 {% data variables.product.prodname_github_connect %} 将不允许 {% data variables.product.prodname_dotcom_the_website %} 用户对 {% data variables.product.product_name %} 进行更改。 + +有关使用 GraphQL API 管理企业帐户的信息，请参阅“[企业帐户](/graphql/guides/managing-enterprise-accounts)”。 +## 启用 {% data variables.product.prodname_github_connect %} + +{% ifversion ghes %} +1. 登录到 {% data variables.product.product_location %} 和 {% data variables.product.prodname_dotcom_the_website %}。 +{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %}{% else %} +1. 登录到 {% data variables.product.product_location %} 和 {% data variables.product.prodname_dotcom_the_website %}。 +{% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %} +1. 在“{% data variables.product.prodname_github_connect %} is not enabled yet”下，单击 **Enable {% data variables.product.prodname_github_connect %}**。 By clicking **Enable {% data variables.product.prodname_github_connect %}**, you agree to the "{% data variables.product.prodname_dotcom %} Terms for Additional Products and Features." +{% ifversion ghes %} +![Enable GitHub Connect button](/assets/images/enterprise/business-accounts/enable-github-connect-button.png){% else %} +![Enable GitHub Connect button](/assets/images/enterprise/github-ae/enable-github-connect-button.png) +{% endif %} +1. 在要连接的企业帐户或组织旁，单击 **Connect**。 ![企业帐户或企业旁边的连接按钮](/assets/images/enterprise/business-accounts/choose-enterprise-or-org-connect.png) + +## Disconnecting a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account from your enterprise account + +与 {% data variables.product.prodname_ghe_cloud %} 断开连接后，{% data variables.product.prodname_github_connect %} {% data variables.product.prodname_github_app %} 会从企业帐户或组织中删除，{% data variables.product.product_location %} 上存储的凭据也会删除。 + +{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %} +1. 在要断开连接的企业帐户或组织旁，单击 **Disable {% data variables.product.prodname_github_connect %}**。 +{% ifversion ghes %} + ![企业帐户或组织名称旁的 Disable GitHub Connect 按钮](/assets/images/enterprise/business-accounts/disable-github-connect-button.png) +1. 阅读有关断开连接的信息，并单击 **Disable {% data variables.product.prodname_github_connect %}**。 ![包含关于断开连接的警告信息和确认按钮的模式窗口](/assets/images/enterprise/business-accounts/confirm-disable-github-connect.png) +{% else %} + ![企业帐户或组织名称旁的 Disable GitHub Connect 按钮](/assets/images/enterprise/github-ae/disable-github-connect-button.png) +1. 阅读有关断开连接的信息，并单击 **Disable {% data variables.product.prodname_github_connect %}**。 ![包含关于断开连接的警告信息和确认按钮的模式窗口](/assets/images/enterprise/github-ae/confirm-disable-github-connect.png) +{% endif %} diff --git a/translations/zh-CN/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md b/translations/zh-CN/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md new file mode 100644 index 0000000000..c59d5f100d --- /dev/null +++ b/translations/zh-CN/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server.md @@ -0,0 +1,97 @@ +--- +title: 为 GitHub Enterprise Server 上易受攻击的依赖项启用警报 +intro: 'You can connect {% data variables.product.product_location %} to {% data variables.product.prodname_ghe_cloud %} and enable the dependency graph and {% ifversion ghes %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts in repositories in your instance.' +shortTitle: 启用依赖项警报 +miniTocMaxHeadingLevel: 3 +redirect_from: + - /enterprise/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /enterprise/admin/configuration/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /enterprise/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server +permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable the dependency graph and {% data variables.product.prodname_dependabot %} alerts on {% data variables.product.prodname_ghe_server %}.' +versions: + ghes: '*' +type: how_to +topics: + - Enterprise + - Security + - Dependency graph + - Dependabot +--- + +## 关于 {% data variables.product.prodname_ghe_server %} 上易受攻击的依赖项的警报 + +To identify vulnerable dependencies in your repository and receive alerts about vulnerabilities, you need to enable two security features: +- The dependency graph +- {% data variables.product.prodname_dependabot %} 警报 + +For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" and "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." + +{% data reusables.repositories.tracks-vulnerabilities %} + +You can connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}, then sync vulnerability data to your instance and generate {% data variables.product.prodname_dependabot_alerts %} in repositories with a vulnerable dependency. + +After connecting {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %} and enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies, vulnerability data is synced from {% data variables.product.prodname_dotcom_the_website %} to your instance once every hour. 您还可以随时选择手动同步漏洞数据。 代码和关于代码的信息不会从 {% data variables.product.product_location %} 上传到 {% data variables.product.prodname_dotcom_the_website %}。 + +When {% data variables.product.product_location %} receives information about a vulnerability, it will identify repositories in your instance that use the affected version of the dependency and generate {% data variables.product.prodname_dependabot_alerts %}. 您可以自定义接收 {% data variables.product.prodname_dependabot_alerts %} 的方式。 更多信息请参阅“[为易受攻击的依赖项配置通知](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies/#configuring-notifications-for-dependabot-alerts)”。 + +Before enabling the dependency graph and {% ifversion ghes > 2.21 %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts for vulnerable dependencies on {% data variables.product.product_location %}, you must connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." + +## Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} on GitHub Enterprise Server + +For {% data variables.product.product_location %} to generate {% data variables.product.prodname_dependabot_alerts %} whenever vulnerabilities are detected on your repositories: +- You must connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}. 更多信息请参阅“[将 {% data variables.product.prodname_ghe_server %} 连接到 {% data variables.product.prodname_ghe_cloud %}](/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)”。 +- You must enable the dependency graph. + +{% ifversion ghes > 3.1 %} +You can enable the dependency graph via the {% data variables.enterprise.management_console %} or the administrative shell. We recommend you follow the {% data variables.enterprise.management_console %} route unless {% data variables.product.product_location %} uses clustering. + +### Enabling the dependency graph via the {% data variables.enterprise.management_console %} +{% endif %}{% ifversion ghes > 3.1 %} +{% data reusables.enterprise_site_admin_settings.sign-in %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.advanced-security-tab %} +1. Under "Security," click **Dependency graph**. ![Checkbox to enable or disable the dependency graph](/assets/images/enterprise/3.2/management-console/enable-dependency-graph-checkbox.png) +{% data reusables.enterprise_management_console.save-settings %} +1. 单击 **Visit your instance（访问您的实例）**。 + +### Enabling the dependency graph via the administrative shell +{% else %} +### 启用依赖关系图 +{% endif %} +{% data reusables.enterprise_site_admin_settings.sign-in %} +1. In the administrative shell, enable the dependency graph on {% data variables.product.product_location %}: + ``` shell + $ {% ifversion ghes > 3.1 %}ghe-config app.dependency-graph.enabled true{% else %}ghe-config app.github.dependency-graph-enabled true{% endif %} + ``` + {% note %} + + **注**：有关启用通过 SSH 访问管理 shell 的更多信息，请参阅“[访问管理 shell (SSH)](/enterprise/{{ currentVersion }}/admin/configuration/accessing-the-administrative-shell-ssh)”。 + + {% endnote %} +1. 应用配置。 + ```shell + $ ghe-config-apply + ``` +1. 返回到 {% data variables.product.prodname_ghe_server %}。 + +### 启用 {% data variables.product.prodname_dependabot_alerts %} + +Before enabling {% data variables.product.prodname_dependabot_alerts %} for your instance, you need to enable the dependency graph. For more information, see above. + +{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %} +1. 在“Repositories can be scanned for vulnerabilities（可扫描仓库漏洞）”下，使用下拉菜单，并选择 **Enabled without notifications（启用但不发通知）**。 （可选）要启用包含通知的警报，请选择 **Enabled with notifications（启用并发通知）**。 ![用于启用扫描仓库有无漏洞的下拉菜单](/assets/images/enterprise/site-admin-settings/enable-vulnerability-scanning-in-repositories.png) + {% note %} + + We recommend configuring {% data variables.product.prodname_dependabot_alerts %} without notifications for the first few days to avoid an overload of emails. 几天后，您可以开启通知，像往常一样接收 {% data variables.product.prodname_dependabot_alerts %}。 + + {% endnote %} +## 查看 {% data variables.product.prodname_ghe_server %} 上易受攻击的依赖项 + +您可以查看 {% data variables.product.product_location %} 中的所有漏洞，然后手动同步 {% data variables.product.prodname_dotcom_the_website %} 中的漏洞数据，以更新列表。 + +{% data reusables.enterprise_site_admin_settings.access-settings %} +2. 在左侧边栏中，单击 **Vulnerabilities**。 ![站点管理员边栏中的 Vulnerabilities 选项卡](/assets/images/enterprise/business-accounts/vulnerabilities-tab.png) +3. 要同步漏洞数据，请单击 **Sync Vulnerabilities now**。 ![Sync vulnerabilities now 按钮](/assets/images/enterprise/site-admin-settings/sync-vulnerabilities-button.png) diff --git a/translations/zh-CN/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md b/translations/zh-CN/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md new file mode 100644 index 0000000000..aa1e1cefad --- /dev/null +++ b/translations/zh-CN/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud.md @@ -0,0 +1,31 @@ +--- +title: 在 GitHub Enterprise Server 与 GitHub Enterprise Cloud 之间启用自动用户许可同步 +intro: '您可以将 {% data variables.product.product_location_enterprise %} 连接到 {% data variables.product.prodname_ghe_cloud %}，并允许 {% data variables.product.prodname_ghe_server %} 将用户许可信息上传到 {% data variables.product.prodname_dotcom_the_website %} 上的企业帐户。' +redirect_from: + - /enterprise/admin/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud + - /enterprise/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud + - /admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud +permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable automatic user license synchronization.' +versions: + ghes: '*' +type: how_to +topics: + - Enterprise + - GitHub Connect + - Licensing +shortTitle: 启用用户许可同步 +--- + +## 关于许可同步 + +在启用许可同步后，您将能够查看 {% data variables.product.prodname_ghe_server %} 和 {% data variables.product.prodname_ghe_cloud %} 上整个企业帐户的许可使用情况。 {% data variables.product.prodname_github_connect %} 每周在 {% data variables.product.prodname_ghe_server %} 与 {% data variables.product.prodname_ghe_cloud %} 之间同步许可。 For more information, see "[Managing your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise)." + +您还可以手动将 {% data variables.product.prodname_ghe_server %} 用户许可信息上传到 {% data variables.product.prodname_ghe_cloud %}。 For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." + +## 启用许可同步 + +在 {% data variables.product.product_location_enterprise %} 上启用许可同步之前，您必须将 {% data variables.product.product_location_enterprise %} 连接到 {% data variables.product.prodname_dotcom_the_website %}。 For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." + +{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %} +1. 在“Server can sync user license count and usage”下，使用下拉菜单，然后选择 **Enabled**。 ![用于启用自动用户许可同步的下拉菜单](/assets/images/enterprise/site-admin-settings/enable-user-license-drop-down.png) diff --git a/translations/zh-CN/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md b/translations/zh-CN/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md new file mode 100644 index 0000000000..86907ce605 --- /dev/null +++ b/translations/zh-CN/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md @@ -0,0 +1,46 @@ +--- +title: Enabling unified contributions between your enterprise account and GitHub.com +shortTitle: 启用统一贡献 +intro: '启用 {% data variables.product.prodname_github_connect %} 后，您可以允许 {% data variables.product.prodname_ghe_cloud %} 成员向其 {% data variables.product.prodname_dotcom_the_website %} 个人资料发送贡献计数，以突出显示他们在 {% data variables.product.product_name %} 上的工作。' +redirect_from: + - /enterprise/admin/guides/developer-workflow/enabling-unified-contributions-between-github-enterprise-and-github-com/ + - /enterprise/admin/guides/developer-workflow/enabling-unified-contributions-between-github-enterprise-server-and-github-com/ + - /enterprise/admin/developer-workflow/enabling-unified-contributions-between-github-enterprise-server-and-githubcom/ + - /enterprise/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom + - /enterprise/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom + - /admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-unified-contributions-between-github-enterprise-server-and-githubcom +permissions: 'Enterprise owners who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable unified contributions between {% data variables.product.product_location %} and {% data variables.product.prodname_dotcom_the_website %}.' +versions: + ghes: '*' + ghae: next +type: how_to +topics: + - Enterprise + - GitHub Connect +--- + +{% data reusables.github-connect.beta %} + +As an enterprise owner, you can allow end users to send anonymized contribution counts for their work from {% data variables.product.product_location %} to their {% data variables.product.prodname_dotcom_the_website %} contribution graph. + +After you enable {% data variables.product.prodname_github_connect %} and enable {% data variables.product.prodname_unified_contributions %} in both environments, end users on your enterprise account can connect to their {% data variables.product.prodname_dotcom_the_website %} accounts and send contribution counts from {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.github-connect.sync-frequency %} 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)." + +If the enterprise owner disables the functionality or developers opt out of the connection, the {% data variables.product.product_name %} contribution counts will be deleted on {% data variables.product.prodname_dotcom_the_website %}. 如果开发者在禁用它们后重新连接其个人资料，则会恢复过去 90 天的贡献计数。 + +{% data variables.product.product_name %} **仅**为已连接的用户发送贡献计数和来源 ({% data variables.product.product_name %})。 它不会发送有关贡献或做出该贡献的方式的任何信息。 + +在 {% data variables.product.product_location %} 上启用 {% data variables.product.prodname_unified_contributions %} 前，必须将 {% data variables.product.product_location %} 连接到 {% data variables.product.prodname_dotcom_the_website %}。 For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_dotcom_the_website %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." + +{% ifversion ghes %} +{% data reusables.github-connect.access-dotcom-and-enterprise %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.business %} +{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %}{% else %} +1. 登录到 {% data variables.product.product_location %} 和 {% data variables.product.prodname_dotcom_the_website %}。 +{% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %} +1. 在“Users can share contribution counts to {% data variables.product.prodname_dotcom_the_website %}”下，单击 **Request access**。 ![Request access to unified contributions option](/assets/images/enterprise/site-admin-settings/dotcom-ghe-connection-request-access.png){% ifversion ghes %} +2. [登录](https://enterprise.github.com/login) {% data variables.product.prodname_ghe_server %} 站点以接收其他说明。 + +When you request access, we may redirect you to the {% data variables.product.prodname_ghe_server %} site to check your current terms of service. +{% endif %} diff --git a/translations/zh-CN/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md b/translations/zh-CN/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md new file mode 100644 index 0000000000..a06226b3bc --- /dev/null +++ b/translations/zh-CN/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md @@ -0,0 +1,44 @@ +--- +title: Enabling unified search between your enterprise account and GitHub.com +shortTitle: 启用统一搜索 +intro: 'After enabling {% data variables.product.prodname_github_connect %}, you can allow search of {% data variables.product.prodname_dotcom_the_website %} for members of your enterprise on {% data variables.product.product_name %}.' +redirect_from: + - /enterprise/admin/guides/developer-workflow/enabling-unified-search-between-github-enterprise-and-github-com/ + - /enterprise/admin/guides/developer-workflow/enabling-unified-search-between-github-enterprise-server-and-github-com/ + - /enterprise/admin/developer-workflow/enabling-unified-search-between-github-enterprise-server-and-githubcom/ + - /enterprise/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom + - /enterprise/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom + - /admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-unified-search-between-github-enterprise-server-and-githubcom +permissions: 'Enterprise owners who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable unified search between {% data variables.product.product_name %} and {% data variables.product.prodname_dotcom_the_website %}.' +versions: + ghes: '*' + ghae: next +topics: + - Enterprise + - GitHub Connect + - GitHub search +--- + +{% data reusables.github-connect.beta %} + +When you enable unified search, users can view search results from public and private content on {% data variables.product.prodname_dotcom_the_website %} when searching from {% data variables.product.product_location %}{% ifversion ghae %} on {% data variables.product.prodname_ghe_managed %}{% endif %}. + +用户将无法从 {% data variables.product.prodname_dotcom_the_website %} 搜索 {% data variables.product.product_location %}，即使他们对这两个环境都具有访问权限。 用户只能搜索您已启用 {% data variables.product.prodname_unified_search %} 的私有仓库，并且他们可以在连接的 {% data variables.product.prodname_ghe_cloud %} 组织中访问。 For more information, see "[About searching on {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github/#searching-across-github-enterprise-and-githubcom-simultaneously)" and "[Enabling private {% data variables.product.prodname_dotcom_the_website %} repository search in your enterprise account](/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment)." + +通过 REST 和 GraphQL API 进行搜索不包含 {% data variables.product.prodname_dotcom_the_website %} 搜索结果。 不支持在 {% data variables.product.prodname_dotcom_the_website %} 中进行高级搜索和搜索 Wiki。 + +{% ifversion ghes %} +{% data reusables.github-connect.access-dotcom-and-enterprise %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.business %} +{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %}{% else %} +1. 登录到 {% data variables.product.product_location %} 和 {% data variables.product.prodname_dotcom_the_website %}。 +{% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %} +1. 在“Users can search {% data variables.product.prodname_dotcom_the_website %}”下，使用下拉菜单，然后单击 **Enabled**。 ![在搜索 GitHub.com 下拉菜单中启用搜索选项](/assets/images/enterprise/site-admin-settings/github-dotcom-enable-search.png) +1. （可选）在“用户可以在 {% data variables.product.prodname_dotcom_the_website %} 上搜索私有仓库”下，使用下拉菜单并单击 **Enabled（启用）**。 ![在搜索 GitHub.com 下拉菜单中启用私有仓库搜索选项](/assets/images/enterprise/site-admin-settings/enable-private-search.png) + +## 延伸阅读 + +- "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)" + diff --git a/translations/zh-CN/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md b/translations/zh-CN/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md new file mode 100644 index 0000000000..d5d19a3d0e --- /dev/null +++ b/translations/zh-CN/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md @@ -0,0 +1,25 @@ +--- +title: Managing connections between your enterprise accounts +intro: '利用 {% data variables.product.prodname_github_connect %}，您可以在 {% data variables.product.product_location %} 与 {% data variables.product.prodname_dotcom_the_website %} 上的 {% data variables.product.prodname_ghe_cloud %} 组织或企业帐户之间共享某些功能和数据。' +redirect_from: + - /enterprise/admin/developer-workflow/connecting-github-enterprise-to-github-com + - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-and-github-com/ + - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-server-and-github-com/ + - /enterprise/admin/developer-workflow/connecting-github-enterprise-server-and-githubcom/ + - /enterprise/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud + - /enterprise/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud +versions: + ghes: '*' + ghae: next +topics: + - Enterprise +children: + - /connecting-your-enterprise-account-to-github-enterprise-cloud + - /enabling-unified-search-between-your-enterprise-account-and-githubcom + - /enabling-unified-contributions-between-your-enterprise-account-and-githubcom + - /enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud +shortTitle: Connect enterprise accounts +--- + diff --git a/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md index c465ce6c6f..2087774240 100644 --- a/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md +++ b/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server.md @@ -37,19 +37,46 @@ topics: {% endif %} +{%- ifversion ghes < 3.2 %} + {% data variables.product.product_location %} 可用的 CPU 和内存资源决定了 {% data variables.product.prodname_actions %} 的最大作业吞吐量。 {% data variables.product.company_short %} 的内部测试展示了具有系列 CPU 和内存配置的 {% data variables.product.prodname_ghe_server %} 实例的以下最大吞吐量。 您可能会看到不同的吞吐量，具体取决于实例的总体活动水平。 -| vCPU | 内存 | 最大作业吞吐量 | -|:---- |:-- |:------- | -| | | | -{%- ifversion ghes > 3.1 %} -| 4 | 32 GB | Demo or light testing | | 8 | 64 GB | 30 jobs | | 16 | 128 GB | 60 jobs | | 32 | 256 GB | 120 jobs | | 64 | 512 GB | 160 jobs | -{%- else ifversion ghes < 3.2 %} -| 4 | 32 GB | Demo or light testing | | 8 | 64 GB | 25 jobs | | 16 | 160 GB | 35 jobs | | 32 | 256 GB | 100 jobs | {%- endif %} +{%- ifversion ghes > 3.1 %} + +The CPU and memory resources available to {% data variables.product.product_location %} determine the number of jobs that can be run concurrently without performance loss. + +The peak quantity of concurrent jobs running without performance loss depends on such factors as job duration, artifact usage, number of repositories running Actions, and how much other work your instance is doing not related to Actions. Internal testing at GitHub demonstrated the following performance targets for GitHub Enterprise Server on a range of CPU and memory configurations: + +{% endif %} + +{%- ifversion ghes < 3.2 %} + +| vCPU | 内存 | 最大作业吞吐量 | +|:---- |:------ |:------- | +| 4 | 32 GB | 演示或轻量测试 | +| 8 | 64 GB | 25 个作业 | +| 16 | 160 GB | 35 个作业 | +| 32 | 256 GB | 100 个作业 | + +{%- endif %} + +{%- ifversion ghes > 3.1 %} + +| vCPU | 内存 | Maximum Concurrency* | +|:---- |:------ |:-------------------- | +| 32 | 128 GB | 1500 个作业 | +| 64 | 256 GB | 1900 个作业 | +| 96 | 384 GB | 2200 个作业 | + +*Maximum concurrency was measured using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. You may experience different performance depending on the overall levels of activity on your instance. + +{%- endif %} + + 如果您{% ifversion ghes = 2.22 %}启用了{% else %}计划中的测试版以便为现有实例的用户启用{% endif %} {% data variables.product.prodname_actions %}，请查看用户的活动级别和实例上的自动化，并确保已为用户预配足够的 CPU 和内存。 有关监控 {% data variables.product.prodname_ghe_server %} 容量和性能的更多信息，请参阅“[监控您的设备](/admin/enterprise-management/monitoring-your-appliance)”。 有关 {% data variables.product.product_location %} 的最低硬件要求的更多信息，请参阅实例平台的硬件考虑因素。 diff --git a/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md b/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md index a2f7c17ebf..5f77d58b40 100644 --- a/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md +++ b/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md @@ -10,7 +10,6 @@ children: - /enabling-github-actions-with-azure-blob-storage - /enabling-github-actions-with-amazon-s3-storage - /enabling-github-actions-with-minio-gateway-for-nas-storage - - /enforcing-github-actions-policies-for-your-enterprise shortTitle: 启用 GitHub Actions --- diff --git a/translations/zh-CN/content/admin/github-actions/index.md b/translations/zh-CN/content/admin/github-actions/index.md index bd32af6548..862ccd8075 100644 --- a/translations/zh-CN/content/admin/github-actions/index.md +++ b/translations/zh-CN/content/admin/github-actions/index.md @@ -16,6 +16,5 @@ children: shortTitle: 管理 GitHub Actions --- -{% data reusables.actions.ae-beta %} {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} diff --git a/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md b/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md index 2452b80303..af380cceac 100644 --- a/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md +++ b/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md @@ -18,7 +18,6 @@ shortTitle: 在企业中添加操作 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data variables.product.prodname_actions %} 工作流程可使用_操作_，它们是一些单独的任务，您可以组合这些操作以创建作业并自定义工作流程。 您可以创建自己的操作，或者使用和自定义 {% data variables.product.prodname_dotcom %} 社区分享的操作。 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 6852c31516..cf65ee1d81 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 @@ -19,7 +19,6 @@ shortTitle: 对操作使用 GitHub Connect {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} {% data reusables.actions.enterprise-github-connect-warning %} -{% data reusables.actions.ae-beta %} 默认情况下，{% data variables.product.product_name %} 上的 {% data variables.product.prodname_actions %} 工作流程不能使用直接来自 {% data variables.product.prodname_dotcom_the_website %} 或 [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions) 的操作。 @@ -27,8 +26,16 @@ shortTitle: 对操作使用 GitHub Connect ## 启用对所有 {% data variables.product.prodname_dotcom_the_website %} 操作的自动访问 -在企业实例上启用访问来自 {% data variables.product.prodname_dotcom_the_website %} 的所有操作之前，必须将企业连接到 {% data variables.product.prodname_dotcom_the_website %}。 更多信息请参阅“[将 {% data variables.product.prodname_ghe_server %} 连接到 {% data variables.product.prodname_ghe_cloud %}](/enterprise/{{ currentVersion }}/admin/guides/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)”。 +在企业实例上启用访问来自 {% data variables.product.prodname_dotcom_the_website %} 的所有操作之前，必须将企业连接到 {% data variables.product.prodname_dotcom_the_website %}。 For more information, see "[Connecting your enterprise to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." -{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %} +{% data reusables.enterprise-accounts.access-enterprise %} +{%- ifversion ghes < 3.1 %} +{% data reusables.enterprise-accounts.settings-tab %} +{%- endif %} +{% data reusables.enterprise-accounts.github-connect-tab %} +{%- ifversion ghes > 3.0 or ghae %} +1. Under "Users can utilize actions from GitHub.com in workflow runs", use the drop-down menu and select **Enabled**. ![工作流程运行中用于访问 GitHub.com 上操作的下拉菜单](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down-ae.png) +{%- else %} 1. 在“Server can use actions from GitHub.com in workflows runs（服务器在工作流程运行中可以使用 GitHub.com 上的操作）”下，使用下拉菜单选择 **Enabled（已启用）**。 ![工作流程运行中用于访问 GitHub.com 上操作的下拉菜单](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down.png) +{%- endif %} 1. {% data reusables.actions.enterprise-limit-actions-use %} 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 73c1dd29c2..ef4be0cb57 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 @@ -14,13 +14,14 @@ shortTitle: 手动同步操作 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} {% data reusables.actions.enterprise-no-internet-actions %} +{% ifversion ghes or ghae-next %} + 推荐的允许从 {% data variables.product.prodname_dotcom_the_website %} 访问操作的方法是启用自动访问所有操作。 通过使用 {% data variables.product.prodname_github_connect %} 将 {% data variables.product.product_name %} 与 {% data variables.product.prodname_ghe_cloud %} 集成可实现这一点。 更多信息请参阅“[启用使用 {% data variables.product.prodname_github_connect %} 自动访问 {% data variables.product.prodname_dotcom_the_website %} 操作](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)”。 -但是，如果您想更严格地控制企业中允许的操作，您可以按照本指南使用 {% data variables.product.company_short %} 的开源 [`actions-sync`](https://github.com/actions/actions-sync) 工具将各个操作仓库从 {% data variables.product.prodname_dotcom_the_website %} 同步到企业。 +However, if you want stricter control over which actions are allowed in your enterprise, you{% else %}You{% endif %} can follow this guide to use {% data variables.product.company_short %}'s open source [`actions-sync`](https://github.com/actions/actions-sync) tool to sync individual action repositories from {% data variables.product.prodname_dotcom_the_website %} to your enterprise. ## 关于 `actions-sync` 工具 @@ -33,7 +34,7 @@ shortTitle: 手动同步操作 ## 基本要求 * 在使用 `actions-sync` 工具之前，您必须确保所有目标组织已经存在于您的企业中。 以下示例演示如何将操作同步到名为 `synced-actions` 的组织。 更多信息请参阅“[从头开始创建新组织](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)”。 -* 您必须在企业上创建可以创建并写入目标组织中的仓库的个人访问令牌 (PAT)。 更多信息请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。 +* 您必须在企业上创建可以创建并写入目标组织中的仓库的个人访问令牌 (PAT)。 For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."{% ifversion ghes %} * 如果您想同步 {% data variables.product.product_location %} 上 `actions` 组织中的捆绑操作，您必须是 `actions` 组织的所有者。 {% note %} @@ -46,21 +47,21 @@ shortTitle: 手动同步操作 ```shell ghe-org-admin-promote -u USERNAME -o actions - ``` + ```{% endif %} -## 示例：使用 `actions-sync` 工具 +## Example: Using the `actions-sync` tool -此示例演示使用 `actions-sync` 工具将个别操作从 {% data variables.product.prodname_dotcom_the_website %} 同步到企业实例。 +This example demonstrates using the `actions-sync` tool to sync an individual action from {% data variables.product.prodname_dotcom_the_website %} to an enterprise instance. {% note %} -**注：**此示例使用 `actions-sync sync` 命令 它要求从您的计算机同时访问 {% data variables.product.prodname_dotcom_the_website %} API 和企业实例的 API。 如果您一次只能访问一个系统，您可以使用 `actions-sync pull` 和 `push` 命令。 更多信息请参阅 [`actions-sync` README](https://github.com/actions/actions-sync#not-connected-instances)。 +**Note:** This example uses the `actions-sync sync` command, which requires concurrent access to both the {% data variables.product.prodname_dotcom_the_website %} API and your enterprise instance's API from your machine. If you can only access one system at a time, you can use the `actions-sync pull` and `push` commands. For more information, see the [`actions-sync` README](https://github.com/actions/actions-sync#not-connected-instances). {% endnote %} -1. 为您计算机的操作系统下载并解压缩最新的 [`actions-sync` 版本](https://github.com/actions/actions-sync/releases)。 +1. Download and extract the latest [`actions-sync` release](https://github.com/actions/actions-sync/releases) for your machine's operating system. 1. 创建一个目录来存储工具的缓存文件。 -1. 运行 `actions-sync sync` 命令： +1. Run the `actions-sync sync` command: ```shell ./actions-sync sync \ diff --git a/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md b/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md index c4ea3be26f..bd4525d5f7 100644 --- a/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md +++ b/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md @@ -14,7 +14,6 @@ shortTitle: 离线运行器的工具缓存 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} ## 关于包含的设置操作和运行器工具缓存 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 5a93c54cce..ece8ae8f3a 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 @@ -13,7 +13,6 @@ shortTitle: 使用最新的捆绑操作 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} 您的企业实例包含一些您可以在工作流程中使用的内置操作。 有关捆绑操作的更多信息，请参阅[“与企业实例捆绑的正式操作”](/admin/github-actions/about-using-actions-in-your-enterprise#official-actions-bundled-with-your-enterprise-instance)。 @@ -29,17 +28,13 @@ shortTitle: 使用最新的捆绑操作 配置 {% data variables.product.prodname_github_connect %} 后，您可以在实例上的 `actions` 组织中删除其本地仓库，以使用最新版本的操作。 例如，如果您的企业实例使用 `actions/checkout@v1` 操作，而且您需要使用在您的企业实例中不可用的 `actions/checkout@v2` ，执行以下步骤便可使用来自 {% data variables.product.prodname_dotcom_the_website %} 的最新 `checkout` 操作： -1. 默认情况下，站点管理员不是捆绑的操作组织的所有者。 要获得删除 `checkout` 仓库所需的访问权限，请使用 `ghe-org-admin-promote` 命令将用户升级为捆绑的 `actions` 组织的所有者。 更多信息请参阅“[访问管理 shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)”和“[`ghe-org-admin-promote`](/admin/configuration/command-line-utilities#ghe-org-admin-promote)”。 例如： - - ```shell - $ ghe-org-admin-promote -u octocat -o actions - Do you want to give organization admin privileges for actions to octocat? (y/N) y - Making octocat an admin of actions - --> Adding octocat as an admin of actions - --> octocat is now an admin of the actions organization - --> Done. - ``` -1. 在您的 {% data variables.product.product_name %} 实例中，删除 `actions` 组织中的 `checkout` 仓库。 有关如何删除仓库的信息，请参阅“[删除仓库](/github/administering-a-repository/deleting-a-repository)”。 -1. 建议您在不再需要管理性访问后离开 `actions` 组织。 更多信息请参阅“[将您自己从组织删除](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization)”。 +1. From an enterprise owner account on {% data variables.product.product_name %}, navigate to the repository you want to delete from the *actions* organization (in this example `checkout`). +1. By default, site administrators are not owners of the bundled *actions* organization. To get the access required to delete the `checkout` repository, you must use the site admin tools. Click {% octicon "rocket" aria-label="The rocket ship" %} in the upper-right corner of any page in that repository. ![用于访问站点管理员设置的火箭图标](/assets/images/enterprise/site-admin-settings/access-new-settings.png) +1. Click {% octicon "shield-lock" %} **Security** to see the security overview for the repository. ![Security header the repository](/assets/images/enterprise/site-admin-settings/access-repo-security-info.png) +1. Under "Privileged access", click **Unlock**. ![Unlock button](/assets/images/enterprise/site-admin-settings/unlock-priviledged-repo-access.png) +1. Under **Reason**, type a reason for unlocking the repository, then click **Unlock**. ![Confirmation dialog](/assets/images/enterprise/site-admin-settings/confirm-unlock-repo-access.png) +1. Now that the repository is unlocked, you can leave the site admin pages and delete the repository within the `actions` organization. At the top of the page, click the repository name, in this example **checkout**, to return to the summary page. ![Repository name link](/assets/images/enterprise/site-admin-settings/display-repository-admin-summary.png) +1. Under "Repository info", click **View code** to leave the site admin pages and display the `checkout` repository. +1. Delete the `checkout` repository within the `actions` organization. For information on how to delete a repository, see "[Deleting a repository](/github/administering-a-repository/deleting-a-repository)." ![View code link](/assets/images/enterprise/site-admin-settings/exit-admin-page-for-repository.png) 1. 配置您的工作流程的 YAML 以使用 `actions/checkout@v2`。 1. 每次您的工作流程运行时，运行器将从 {% data variables.product.prodname_dotcom_the_website %} 中使用 `v2` 版本的 `actions/checkout`。 diff --git a/translations/zh-CN/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md b/translations/zh-CN/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md index 5d620fdd98..1562a1f823 100644 --- a/translations/zh-CN/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md +++ b/translations/zh-CN/content/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae.md @@ -13,7 +13,6 @@ redirect_from: - /admin/github-actions/getting-started-with-github-actions-for-github-ae --- -{% data reusables.actions.ae-beta %} 本文介绍站点管理员如何配置 {% data variables.product.prodname_ghe_managed %} 来使用 {% data variables.product.prodname_actions %}。 diff --git a/translations/zh-CN/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md b/translations/zh-CN/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md index 670848b4fd..a522aff904 100644 --- a/translations/zh-CN/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md +++ b/translations/zh-CN/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md @@ -8,7 +8,6 @@ redirect_from: shortTitle: 使用操作 --- -{% data reusables.actions.ae-beta %} {% data variables.product.prodname_actions %} 工作流程可使用_操作_，它们是一些单独的任务，您可以组合这些操作以创建作业并自定义工作流程。 您可以创建自己的操作，或者使用和自定义 {% data variables.product.prodname_dotcom %} 社区分享的操作。 diff --git a/translations/zh-CN/content/admin/guides.md b/translations/zh-CN/content/admin/guides.md index 95d8e5b808..1232adc9d2 100644 --- a/translations/zh-CN/content/admin/guides.md +++ b/translations/zh-CN/content/admin/guides.md @@ -35,13 +35,13 @@ includeGuides: - /admin/configuration/configuring-rate-limits - /admin/configuration/configuring-secret-scanning-for-your-appliance - /admin/configuration/configuring-tls - - /admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud + - /admin/configuration/connecting-your-enterprise-account-to-github-enterprise-cloud - /admin/configuration/enabling-and-scheduling-maintenance-mode - /admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud - /admin/configuration/enabling-private-mode - /admin/configuration/enabling-subdomain-isolation - - /admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom - - /admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom + - /admin/configuration/enabling-unified-contributions-between-your-enterprise-account-and-githubcom + - /admin/configuration/enabling-unified-search-between-your-enterprise-account-and-githubcom - /admin/configuration/initializing-github-ae - /admin/configuration/managing-github-for-mobile-for-your-enterprise - /admin/configuration/network-ports diff --git a/translations/zh-CN/content/admin/overview/about-enterprise-accounts.md b/translations/zh-CN/content/admin/overview/about-enterprise-accounts.md index 359e209001..5a6c987f2a 100644 --- a/translations/zh-CN/content/admin/overview/about-enterprise-accounts.md +++ b/translations/zh-CN/content/admin/overview/about-enterprise-accounts.md @@ -1,39 +1,17 @@ --- -title: About enterprise accounts -intro: 'With {% data variables.product.product_name %}, you can use an enterprise account to give administrators a single point of visibility and management{% if enterpriseServerVersions contains currentVersion %} for billing and license usage{% endif %}.' +title: 关于企业帐户 +intro: 'With {% data variables.product.product_name %}, you can use an enterprise account to give administrators a single point of visibility and management.' redirect_from: - /enterprise/admin/installation/about-enterprise-accounts - /enterprise/admin/overview/about-enterprise-accounts versions: ghes: '*' ghae: '*' +type: overview topics: - Accounts - Enterprise - Fundamentals --- -### About enterprise accounts on {% data variables.product.product_name %} - -An enterprise account allows you to manage multiple organizations{% if enterpriseServerVersions contains currentVersion %} and {% data variables.product.prodname_ghe_server %} instances{% else %} on {% data variables.product.product_name %}{% endif %}. Your enterprise account must have a handle, like an organization or personal account on {% data variables.product.prodname_dotcom %}. Enterprise administrators can manage settings and preferences, like: - -- Member access and management (organization members, outside collaborators){% if enterpriseServerVersions contains currentVersion %} -- Billing and usage ({% data variables.product.prodname_ghe_server %} instances, user licenses, {% data variables.large_files.product_name_short %} packs){% endif %} -- Security {% if enterpriseServerVersions contains currentVersion %}(single sign-on, two factor authentication) -- Requests {% if enterpriseServerVersions contains currentVersion %}and support bundle sharing {% endif %}with {% data variables.contact.enterprise_support %}{% endif %} - -{% if enterpriseServerVersions contains currentVersion %}{% data reusables.enterprise-accounts.enterprise-accounts-billing %} For more information about the management of your {% data variables.product.prodname_ghe_cloud %} subscription, see "[Viewing the subscription and usage for your enterprise account](/articles/viewing-the-subscription-and-usage-for-your-enterprise-account)." {% endif %}For more information about managing your {% data variables.product.product_name %} billing settings, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)." - -For more information about the management of users, organizations, data, and policies for {% data variables.product.product_location %}, see "[Managing users, organizations, and repositories](/admin/user-management)" and "[Setting policies for your enterprise](/admin/policies)." - -For more information about the management of enterprise accounts using the GraphQL API, see "[Enterprise accounts](/graphql/guides/managing-enterprise-accounts)." - -{% if enterpriseServerVersions contains currentVersion %} - -For more information about the differences between {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}, see "[{% data variables.product.prodname_dotcom %}'s products](/articles/githubs-products)." To upgrade to {% data variables.product.prodname_enterprise %} or to get started with an enterprise account, contact {% data variables.contact.contact_enterprise_sales %}. - -### Managing {% data variables.product.prodname_ghe_server %} licenses linked to your enterprise account - -{% data reusables.enterprise-accounts.admin-managing-licenses %} - -{% endif %} +{% data reusables.enterprise-accounts.about-enterprise-accounts %} diff --git a/translations/zh-CN/content/admin/overview/about-upgrades-to-new-releases.md b/translations/zh-CN/content/admin/overview/about-upgrades-to-new-releases.md index 7e1f9f8ac4..8bbf7b08c0 100644 --- a/translations/zh-CN/content/admin/overview/about-upgrades-to-new-releases.md +++ b/translations/zh-CN/content/admin/overview/about-upgrades-to-new-releases.md @@ -13,7 +13,7 @@ topics: {% data variables.product.product_name %} 正在不断改进，通过主要和次要版本引入新功能和漏洞补丁。 {% ifversion ghae %}{% data variables.product.prodname_ghe_managed %} 是一项完全管理的服务，因此 {% data variables.product.company_short %} 可完成企业的升级过程。{% endif %} -主要版本包括新功能和功能升级，通常{% ifversion ghae %}每几个星期或几个月{% else %}每季度{% endif %}进行一次。 {% ifversion ghae %}{% data variables.product.company_short %} 会将您的企业升级到最新的主要版本。 您的企业如有任何计划内的停机，都会提前通知您。{% endif %} +Major releases include new functionality and feature upgrades and typically occur quarterly. {% ifversion ghae %}{% data variables.product.company_short %} 会将您的企业升级到最新的主要版本。 您的企业如有任何计划内的停机，都会提前通知您。{% endif %} {% ifversion ghes %} @@ -43,7 +43,6 @@ topics: ## 延伸阅读 -- `github/roadmap` 仓库中的 [ {% data variables.product.prodname_roadmap %} ]({% data variables.product.prodname_roadmap_link %}) -{% ifversion ghae %} +- [ {% data variables.product.prodname_roadmap %} ]({% data variables.product.prodname_roadmap_link %}) in the `github/roadmap` repository{% ifversion ghae %} - [ {% data variables.product.prodname_ghe_managed %} 发行说明](/admin/release-notes) {% endif %} diff --git a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise.md b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise.md new file mode 100644 index 0000000000..b4eb3d8528 --- /dev/null +++ b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise.md @@ -0,0 +1,59 @@ +--- +title: 为企业实施 GitHub Actions 策略 +intro: '企业管理员可以管理对企业中 {% data variables.product.prodname_actions %} 的访问。' +redirect_from: + - /enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise + - /admin/github-actions/enforcing-github-actions-policies-for-your-enterprise + - /admin/github-actions/enabling-github-actions-for-github-enterprise-server/enforcing-github-actions-policies-for-your-enterprise +versions: + ghes: '*' + ghae: '*' +type: how_to +topics: + - Actions + - Enterprise + - Policies +shortTitle: GitHub Actions policies +--- + +{% data reusables.actions.enterprise-beta %} + +## 关于企业的 {% data variables.product.prodname_actions %} 权限 + +{% ifversion ghae %}{% else %}在 {% data variables.product.prodname_ghe_server %} 上启用 {% data variables.product.prodname_actions %} 时，它会对您企业中的所有组织启用。 {% endif %}您可以选择对企业中的所有组织禁用 {% data variables.product.prodname_actions %}，或只允许特定的组织。 您还可以限制公共操作的使用，以使人们只能使用您的企业中存在的本地操作。 + +## 管理企业的 {% data variables.product.prodname_actions %} 权限 + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.actions-tab %} +{% data reusables.actions.enterprise-actions-permissions %} + +{% ifversion ghes > 2.22 or ghae %} +## 允许特定操作运行 + +{% data reusables.actions.allow-specific-actions-intro %} + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.actions-tab %} +1. 在 **Policies（策略）**下，选择 **Allow select actions（允许选择操作）**并将所需操作添加到列表中。 + {%- ifversion ghes or ghae-issue-5094 %} + ![添加操作到允许列表](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png) + {%- elsif ghae %} + ![添加操作到允许列表](/assets/images/enterprise/github-ae/enterprise-actions-policy-allow-list.png) + {%- endif %} +{% endif %} + +{% ifversion ghes > 2.22 or ghae %} +## 为私有仓库复刻启用工作流程 + +{% data reusables.github-actions.private-repository-forks-overview %} + +### 为企业配置私有复刻策略 + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.policies-tab %} +{% data reusables.enterprise-accounts.actions-tab %} +{% data reusables.github-actions.private-repository-forks-configure %} +{% endif %} diff --git a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md index bde7c9d379..7f32f372dc 100644 --- a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md +++ b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md @@ -34,7 +34,7 @@ topics: - Enterprise - Policies - Security -shortTitle: 执行仓库策略 +shortTitle: Repository management policies --- ## 配置企业中新仓库的默认可见性 diff --git a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/index.md b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/index.md index 95a7962865..b7c5c44599 100644 --- a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/index.md +++ b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/index.md @@ -11,6 +11,7 @@ topics: children: - /enforcing-repository-management-policies-in-your-enterprise - /restricting-email-notifications-for-your-enterprise + - /enforcing-github-actions-policies-for-your-enterprise - /enforcing-policies-for-advanced-security-in-your-enterprise shortTitle: 执行策略 --- diff --git a/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md b/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md index e2911a8eb6..f05141e550 100644 --- a/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md +++ b/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md @@ -30,6 +30,9 @@ SAML SSO 允许企业所有者从 SAML IdP 集中控制和安全访问 {% data v {% data reusables.saml.dotcom-saml-explanation %} 组织所有者可以邀请您在 {% data variables.product.prodname_dotcom %} 上的用户帐户加入其使用 SAML SSO 的组织，这样您可以对该组织做出贡献，并且保留您在 {% data variables.product.prodname_dotcom %} 上的现有身份和贡献。 +If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you will use a new account that is provisioned for you. {% data reusables.enterprise-accounts.emu-more-info-account %} + + 在访问使用 SAML SSO 的组织中的资源时，{% data variables.product.prodname_dotcom %} 会将您重定向到组织的 SAML IdP 进行身份验证。 在 IdP 上成功验证您的帐户后，IdP 会将您重定向回到 {% data variables.product.prodname_dotcom %}，您可以在那里访问组织的资源。 {% data reusables.saml.outside-collaborators-exemption %} diff --git a/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md b/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md index 6859aba283..747056c38c 100644 --- a/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md +++ b/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md @@ -20,7 +20,7 @@ shortTitle: 生成新 SSH 密钥 如果您还没有 SSH 密钥，则必须生成新 SSH 密钥用于身份验证。 如果不确定是否已经拥有 SSH 密钥，您可以检查现有密钥。 更多信息请参阅“[检查现有 SSH 密钥](/github/authenticating-to-github/checking-for-existing-ssh-keys)”。 -{% ifversion fpt %} +{% ifversion fpt or ghae-next or ghes > 3.1 %} 如果要使用硬件安全密钥向 {% data variables.product.product_name %} 验证，则必须为硬件安全密钥生成新的 SSH 密钥。 使用密钥对进行身份验证时，您必须将硬件安全密钥连接到计算机。 更多信息请参阅 [OpenSSH 8.2 发行说明](https://www.openssh.com/txt/release-8.2)。 @@ -31,6 +31,12 @@ shortTitle: 生成新 SSH 密钥 {% data reusables.command_line.open_the_multi_os_terminal %} 2. 粘贴下面的文本（替换为您的 {% data variables.product.product_name %} 电子邮件地址）。 + {% ifversion ghae %} + + ```shell + $ ssh-keygen -t rsa -b 4096 -C "your_email@example.com" + ``` + {% else %} ```shell $ ssh-keygen -t ed25519 -C "your_email@example.com" ``` @@ -38,20 +44,22 @@ shortTitle: 生成新 SSH 密钥 **注：**如果您使用的是不支持 Ed25519 算法的旧系统，请使用以下命令： ```shell - $ ssh-keygen -t rsa -b 4096 -C "your_email@example.com" + $ ssh-keygen -t rsa -b 4096 -C "your_email@example.com" ``` {% endnote %} + {% endif %} + This creates a new SSH key, using the provided email as a label. ```shell - > Generating public/private ed25519 key pair. + > Generating public/private algorithm key pair. ``` 3. 提示您“Enter a file in which to save the key（输入要保存密钥的文件）”时，按 Enter 键。 这将接受默认文件位置。 {% mac %} ```shell - > Enter a file in which to save the key (/Users/you/.ssh/id_ed25519): [Press enter] + > Enter a file in which to save the key (/Users/you/.ssh/id_algorithm): [Press enter] ``` {% endmac %} @@ -59,7 +67,7 @@ shortTitle: 生成新 SSH 密钥 {% windows %} ```shell - > Enter a file in which to save the key (/c/Users/you/.ssh/id_ed25519):[Press enter] + > Enter a file in which to save the key (/c/Users/you/.ssh/id_algorithm):[Press enter] ``` {% endwindows %} @@ -67,7 +75,7 @@ shortTitle: 生成新 SSH 密钥 {% linux %} ```shell - > Enter a file in which to save the key (/home/you/.ssh/id_ed25519): [Press enter] + > Enter a file in which to save the key (/home/you/.ssh/algorithm): [Press enter] ``` {% endlinux %} @@ -107,7 +115,7 @@ shortTitle: 生成新 SSH 密钥 Host * AddKeysToAgent yes UseKeychain yes - IdentityFile ~/.ssh/id_ed25519 + IdentityFile ~/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %} ``` {% note %} @@ -137,7 +145,7 @@ shortTitle: 生成新 SSH 密钥 3. 将 SSH 私钥添加到 ssh-agent 并将密码存储在密钥链中。 {% data reusables.ssh.add-ssh-key-to-ssh-agent %} ```shell - $ ssh-add -K ~/.ssh/id_ed25519 + $ ssh-add -K ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %} ``` {% note %} @@ -189,8 +197,10 @@ shortTitle: 生成新 SSH 密钥 {% data reusables.command_line.open_the_multi_os_terminal %} 3. 粘贴下面的文本，将电子邮件地址替换为您的 {% data variables.product.product_name %} 帐户的电子邮件地址。 ```shell - $ ssh-keygen -t ed25519-sk -C "your_email@example.com" + $ ssh-keygen -t {% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}-sk -C "your_email@example.com" ``` + + {% ifversion not ghae %} {% note %} **注：**如果命令失败，并且您收到错误 `invalid format` 或 `feature not supported`，则表明您可能在使用不支持 Ed25519 算法的硬件安全密钥。 请输入以下命令。 @@ -199,13 +209,14 @@ shortTitle: 生成新 SSH 密钥 ``` {% endnote %} + {% endif %} 4. 出现提示时，请触摸硬件安全密钥上的按钮。 5. 当提示您“Enter a file in which to save the key（输入要保存密钥的文件）”时，按 Enter 接受默认文件位置。 {% mac %} ```shell - > Enter a file in which to save the key (/Users/you/.ssh/id_ed25519_sk): [Press enter] + > Enter a file in which to save the key (/Users/you/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): [Press enter] ``` {% endmac %} @@ -213,7 +224,7 @@ shortTitle: 生成新 SSH 密钥 {% windows %} ```shell - > Enter a file in which to save the key (/c/Users/you/.ssh/id_ed25519_sk):[Press enter] + > Enter a file in which to save the key (/c/Users/you/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk):[Press enter] ``` {% endwindows %} @@ -221,7 +232,7 @@ shortTitle: 生成新 SSH 密钥 {% linux %} ```shell - > Enter a file in which to save the key (/home/you/.ssh/id_ed25519_sk): [Press enter] + > Enter a file in which to save the key (/home/you/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): [Press enter] ``` {% endlinux %} 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 16b038a7c1..8819a5bd5b 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 @@ -28,6 +28,10 @@ shortTitle: 向 GitHub 验证 您可以 {% ifversion ghae %}使用 IdP 在浏览器中向 {% data variables.product.product_name %} 验证。 更多信息请参阅“[关于使用 SAML 单点登录进行身份验证](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)”{% else %}。 +- {% ifversion fpt %} +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](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users#authenticating-as-a-managed-user)". If you're not a member of an {% data variables.product.prodname_emu_enterprise %}, you will authenticate using your browser on {% data variables.product.prodname_dotcom_the_website %}. +{% endif %} + - **仅用户名和密码** - 在 {% data variables.product.product_name %} 上创建用户帐户时，您将创建一个密码。 我们建议您使用密码管理器生成随机且唯一的密码。 更多信息请参阅“[创建强式密码](/github/authenticating-to-github/creating-a-strong-password)”。 - **双重身份验证 (2FA)**（推荐） 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 3a7f49662e..74edf7b1ff 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 @@ -38,7 +38,7 @@ A token with no assigned scopes can only access public information. 要使用令 {% data reusables.user_settings.access_settings %} {% data reusables.user_settings.developer_settings %} {% data reusables.user_settings.personal_access_tokens %} -4. 单击 **Generate new token（生成新令牌）**。 ![生成新令牌按钮](/assets/images/help/settings/generate_new_token.png) +{% 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 %} 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（仓库）**。 diff --git a/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md b/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md index b8ea0199ac..863b358a23 100644 --- a/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md +++ b/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md @@ -75,33 +75,6 @@ shortTitle: 配置 2FA 恢复 设置完成后，备用设备将收到确认短信。 -## 添加具有异地恢复帐户功能的后备身份验证方法 - -您可以为帐户生成额外的身份验证凭据，并通过合作伙伴的恢复提供程序存储它。 - -### 关于异地恢复帐户 - -通过异地恢复帐户功能，您可以为 {% data variables.product.product_name %} 帐户添加额外的安全因素，以应对无法访问双重身份验证方法或恢复代码的情况。 - -异地恢复帐户功能允许您将 {% data variables.product.product_name %} 帐户与您的 Facebook 帐户相关联。 您可以使用 Facebook 以_帐户恢复令牌_的形式存储 {% data variables.product.product_name %} 帐户的身份验证凭据。 - -如果因无法访问双重身份验证方法或恢复代码而无法访问 {% data variables.product.product_name %} 帐户，您可以从恢复提供程序取回您的帐户恢复令牌，以帮助证明您是您的 {% data variables.product.product_name %} 帐户的所有者。 - -取回令牌后，{% data variables.contact.contact_support %} 可能会对帐户禁用双重身份验证。 然后，您可以提供或重置密码以恢复帐户访问。 - -生成或取回帐户恢复令牌时，帐户的审核日志中会添加一个事件。 更多信息请参阅“[查看安全日志](/articles/reviewing-your-security-log)”。 - -### 生成并存储帐户恢复令牌 - -您可以生成帐户恢复令牌并通过合作伙伴的恢复提供程序存储它。 - -1. 登录您的 Facebook 帐户，然后返回到 {% data variables.product.product_name %}。 -{% data reusables.user_settings.access_settings %} -{% data reusables.user_settings.security %} -4. 要生成新令牌，请在“Recovery tokens（恢复令牌）”下，单击 **Store new token（存储新令牌）**。 ![用于存储新恢复令牌的按钮](/assets/images/help/settings/store-new-recovery-token.png) -5. 阅读有关帐户恢复令牌的信息，然后单击 **Connect with https://www.facebook.com（连接 https://www.facebook.com）**。 ![用于将恢复令牌与 Facebook 连接的按钮](/assets/images/help/settings/connect-recovery-token-with-facebook.png) -6. 重定向到 Facebook 后，阅读有关使用 Facebook 开启帐户恢复的信息，然后单击 **Save as [_YOUR NAME_]（另存为名称）**。 （如果您在短期内保存多个令牌，Facebook 可能会在您保存第一个令牌后跳过此确认步骤。） ![含有开启帐户恢复按钮的 Facebook 页面](/assets/images/help/settings/security-turn-on-rae-facebook.png) - {% endif %} ## 延伸阅读 diff --git a/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md b/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md index d9bffd528d..420d72a9a8 100644 --- a/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md +++ b/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md @@ -28,6 +28,12 @@ shortTitle: 配置 2FA {% endwarning %} +{% ifversion fpt %} + +If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you cannot configure 2FA for your {% data variables.product.prodname_managed_user %} account. 2FA should be configured through your identity provider. + +{% endif %} + ## 使用 TOTP 移动应用程序配置双重身份验证 基于时间的一次性密码 (TOTP) 应用程序可自动生成在特定时间后变化的验证码。 我们建议使用基于云的 TOTP 应用程序，例如： diff --git a/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md b/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md index 4ff9f8c755..4710ea3e4e 100644 --- a/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md +++ b/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md @@ -71,6 +71,12 @@ shortTitle: 使用 2FA 找回帐户 ## 使用帐户恢复令牌进行身份验证 +{% warning %} + +**Warning:** Account recovery tokens are deprecated and will be disabled on **December 1st, 2021**. Please ensure you have configured other two-factor recovery methods. For more information, see "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)." + +{% endwarning %} + 如果无法访问 {% data variables.product.product_name %} 帐户的双因素身份验证方法，您可以从合作伙伴的恢复提供程序提取帐户恢复令牌，并请求 {% data variables.product.prodname_dotcom %} 支持人员进行审查。 如果您无法访问双因素身份验证方法或恢复代码，并且已通过 Facebook 使用“异地恢复帐户”存储帐户恢复令牌，则可以使用您的令牌重新获得对帐户的访问权限。 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 13b06b4d6d..49a439eabd 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 @@ -68,6 +68,8 @@ shortTitle: GitHub Actions 的计费 ## 计算分钟和存储支出 +{% data reusables.dotcom_billing.pricing_cal %} + 在月末，{% data variables.product.prodname_dotcom %} 会计算您使用的超过帐户自带限额的分钟数和存储空间费用。 ### Sample minutes cost calculation diff --git a/translations/zh-CN/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md b/translations/zh-CN/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md index 7cec04c1f8..5a7d7e34f7 100644 --- a/translations/zh-CN/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md +++ b/translations/zh-CN/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md @@ -28,6 +28,8 @@ topics: 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 {% data variables.product.prodname_codespaces %} usage. 更多信息请参阅“[将 Azure 订阅连接到您的企业](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)”。 +{% data reusables.dotcom_billing.pricing_cal %} + ## Setting a spending limit {% data reusables.codespaces.codespaces-spending-limit-requirement %} 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 545f16b258..db68d3ab14 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,7 +49,7 @@ shortTitle: 关于计费 {% 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.25 USD per GB of storage and $0.50 USD per GB of data transfer. -例如，如果您的组织使用 {% data variables.product.prodname_team %}，允许无限制的支出，使用了 150GB 的存储量，一个月内还传输了 50GB 的数据，则组织在当月的存储量超限 148GB，数据传输量为 40GB。 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. +例如，如果您的组织使用 {% data variables.product.prodname_team %}，允许无限制的支出，使用了 150GB 的存储量，一个月内还传输了 50GB 的数据，则组织在当月的存储量超限 148GB，数据传输量为 40GB。 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. {% data reusables.dotcom_billing.pricing_cal %} 到月底，{% data variables.product.prodname_dotcom %} 会将您的数据传输舍入到最接近的 GB。 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 5e369c626f..49ba8c0ef6 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 @@ -68,11 +68,9 @@ shortTitle: 配置代码扫描 如果您在推送时扫描，则结果将出现在仓库的 **Security（安全性）**选项卡中。 更多信息请参阅“[管理仓库的代码扫描警报](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)”。 -{% note %} - -**注意**：如果您希望 {% data variables.product.prodname_code_scanning %} 警报显示为拉取请求检查，则必须使用下述 `pull_request` 事件。 - -{% endnote %} +{% ifversion fpt or ghes > 3.2 or ghae-issue-5093 %} +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 %} ### 扫描拉取请求 @@ -82,6 +80,10 @@ shortTitle: 配置代码扫描 如果您扫描拉取请求，则结果在拉取请求检查中显示为警报。 更多信息请参阅“[对拉取请求中的代码扫描警报分类](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)”。 +{% ifversion fpt or ghes > 3.2 or ghae-issue-5093 %} + 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 %} + {% ifversion fpt or ghes > 3.1 or ghae-next %} ### Defining the severities causing pull request check failure @@ -155,7 +157,7 @@ on: ## 指定操作系统 -如果您的代码需要使用特定的操作系统进行编译，您可以在工作流程中配置它。 编辑 `jobs.analyze.runs-on` 的值以指定运行 {% data variables.product.prodname_code_scanning %} 操作的机器操作系统。 {% ifversion ghes %}在 `self-hosted` 之后，使用适当的标签作为双元素数组中的第二个元素来指定操作系统。{% else %} +如果您的代码需要使用特定的操作系统进行编译，您可以在工作流程中配置它。 编辑 `jobs.analyze.runs-on` 的值以指定运行 {% data variables.product.prodname_code_scanning %} 操作的机器操作系统。 {% ifversion ghes %}You specify the operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% else %} 如果选择使用自托管的运行器进行代码扫描，可以在 `self-hosted` 之后，使用适当的标签作为双元素数组中的第二个元素来指定操作系统。{% endif %} @@ -168,9 +170,9 @@ jobs: {% ifversion fpt %}更多信息请参阅“[关于自托管的运行器](/actions/hosting-your-own-runners/about-self-hosted-runners)”和“[添加自托管的运行器](/actions/hosting-your-own-runners/adding-self-hosted-runners)”。{% endif %} -{% data variables.product.prodname_code_scanning_capc %} 支持 macOS、Ubuntu 和 Windows 的最新版本。 因此，此设置的典型值为：`ubuntu-latest`、`windows-latest` 和 `macos-latest`。 更多信息请参阅{% ifversion ghes %}“[GitHub Actions 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)”和“[将标签与自托管运行器一起使用](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}”[GitHub Actions 的工作流程语法](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}“。 +{% data variables.product.prodname_code_scanning_capc %} 支持 macOS、Ubuntu 和 Windows 的最新版本。 因此，此设置的典型值为：`ubuntu-latest`、`windows-latest` 和 `macos-latest`。 For more information, see {% ifversion ghes %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" and "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}." -{% ifversion ghes %}您必须确保 Git 位于自托管运行器的 PATH 变量中。{% else %}如果您使用自托管运行器，必须确保 Git 在 PATH 变量中。{% endif %} +{% ifversion ghes %}You must ensure that Git is in the PATH variable on your self-hosted runners.{% else %}If you use a self-hosted runner, you must ensure that Git is in the PATH variable.{% endif %} {% ifversion fpt or ghes > 3.1 or ghae-next %} ## 指定 {% data variables.product.prodname_codeql %} 数据库的位置 @@ -234,7 +236,6 @@ jobs: ```yaml jobs: CodeQL-Build: - runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae-next %} permissions: security-events: write @@ -266,7 +267,7 @@ jobs: ``` {% endif %} -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ## 配置分析类别 使用`类别`来区分同一工具和提交的多次分析，但是在不同语言或代码的不同部分进行。 您在工作流程中指定的类别将包含在 SARIF 结果文件中。 @@ -285,7 +286,7 @@ jobs: ``` {% endraw %} -如果您没有在工作流程中指定 `category` 参数，则 {% data variables.product.product_name %} 将根据触发操作的工作流程文件的名称、操作名称和任何矩阵变量为您生成类别名称。 例如： +If you don't specify a `category` parameter in your workflow, {% data variables.product.product_name %} will generate a category name for you, based on the name of the workflow file triggering the action, the action name, and any matrix variables. 例如： - `.github/workflows/codeql-analysis.yml` 工作流程和 `analyze` 操作将产生类别 `.github/workflows/codeql.yml:analyze`。 - `.github/workflows/codeql-analysis.yml` 工作流程、`analyze` 操作和 `{language: javascript, os: linux}` 矩阵变量将产生类别 `.github/workflows/codeql-analysis.yml:analyze/language:javascript/os:linux`。 diff --git a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md index 57fb97e9f4..3967ee5fc8 100644 --- a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md @@ -48,9 +48,9 @@ topics: Alert severity levels may be `Error`, `Warning`, or `Note`. -By default, any code scanning results with a severity of `error` will cause check failure. {% ifversion fpt or ghes > 3.1 or ghae-next %}You can specify the severity level at which pull requests that trigger code scanning alerts should fail. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %} +By default, any code scanning results with a severity of `error` will cause check failure. {% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %}You can specify the severity level at which pull requests that trigger code scanning alerts should fail. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."{% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %} +{% ifversion fpt or ghes > 3.1 or ghae-issue-4697 %} ### About security severity levels {% data variables.product.prodname_code_scanning_capc %} displays security severity levels for alerts that are generated by security queries. Security severity levels can be `Critical`, `High`, `Medium`, or `Low`. @@ -70,10 +70,10 @@ By default, the code scanning alerts page is filtered to show alerts for the def {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-code-scanning-alerts %} -{% ifversion fpt or ghes > 3.1 %} -1. （可选）使用 {% ifversion fpt or ghes > 3.1 %} 自由文本搜索框或{% endif %} 下拉菜单以过滤警报。 例如，您可以通过用于识别警报的工具进行过滤。 ![Filter by tool](/assets/images/help/repository/code-scanning-filter-by-tool.png){% endif %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} +1. Optionally, use the free text search box or the drop-down menus to filter alerts. 例如，您可以通过用于识别警报的工具进行过滤。 ![Filter by tool](/assets/images/help/repository/code-scanning-filter-by-tool.png){% endif %} 1. 在 "{% data variables.product.prodname_code_scanning_capc %}" 下，单击要探索的警报。 -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ![警报摘要](/assets/images/help/repository/code-scanning-click-alert.png) {% else %} ![来自 {% data variables.product.prodname_code_scanning %} 的警报列表](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) @@ -81,7 +81,7 @@ By default, the code scanning alerts page is filtered to show alerts for the def 1. （可选）如果警报突出显示数据流的问题，请单击 **Show paths（显示路径）**以显示从数据源到使用它的接收者的路径。 ![警报上的"显示路径"链接](/assets/images/help/repository/code-scanning-show-paths.png) 1. 来自 {% data variables.product.prodname_codeql %} 分析的警报包括对问题的描述。 单击 **Show more（显示更多）**以获取有关如何修复代码的指导。 ![警报的详细信息](/assets/images/help/repository/code-scanning-alert-details.png) -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} {% note %} **注意：** 对于 {% data variables.product.prodname_codeql %} 的 {% data variables.product.prodname_code_scanning %} 分析，您可以在仓库的 {% data variables.product.prodname_code_scanning %} 警报列表顶部的标头中看到有关最新运行的信息。 @@ -91,7 +91,6 @@ By default, the code scanning alerts page is filtered to show alerts for the def {% endnote %} {% endif %} - ## Filtering {% data variables.product.prodname_code_scanning %} alerts You can filter the alerts shown in the {% data variables.product.prodname_code_scanning %} alerts view. This is useful if there are many alerts as you can focus on a particular type of alert. There are some predefined filters and a range of keywords that you can use to refine the list of alerts displayed. @@ -105,7 +104,21 @@ You can filter the alerts shown in the {% data variables.product.prodname_code_s The benefit of using keyword filters is that only values with results are shown in the drop-down lists. This makes it easy to avoid setting filters that find no results. +If you enter multiple filters, the view will show alerts matching _all_ these filters. For example, `is:closed severity:high branch:main` will only display closed high-severity alerts that are present on the `main` branch. The exception is filters relating to refs (`ref`, `branch` and `pr`): `is:open branch:main branch:next` will show you open alerts from both the `main` branch and the `next` branch. + +### Restricting results to application code only + +You can use the "Only alerts in application code" filter or `autofilter:true` keyword and value to restrict results to alerts in application code. Application code excludes the following. + +- Code generated by the build process +- Test code +- Library or third-party code +- 文档 + +{% data variables.product.prodname_code_scanning_capc %} categorizes files by file path. At this time, you cannot manually categorize source files. + {% ifversion fpt or ghes > 3.1 %} + ## 搜索 {% data variables.product.prodname_code_scanning %} 警报 您可以搜索警报列表。 如果仓库中存在大量警报，或者您不知道警报的确切名称，这很有用。 {% data variables.product.product_name %} 可执行以下自由文本搜索： @@ -145,11 +158,11 @@ The benefit of using keyword filters is that only values with results are shown 如果您有仓库的写入权限，您可以通过查看警报摘要并单击 **Closed（已关闭）**来查看已修复的警报。 更多信息请参阅“[查看仓库的警报](#viewing-the-alerts-for-a-repository)”。 “Closed（已关闭）”列表显示已修复的警报和用户已忽略的警报。 -您可以使用{% ifversion fpt or ghes > 3.1 %} 自由文本搜索或{% endif %} 过滤器显示警报子集，然后依次将所有匹配的警报标记为已关闭。 +您可以使用{% ifversion fpt or ghes > 3.1 or ghae-next %} 自由文本搜索或{% endif %} 过滤器显示警报子集，然后依次将所有匹配的警报标记为已关闭。 警报只能在一个分支中修复。 您可以在警报摘要上使用“Branch（分支）”下拉菜单检查警报是否是在特定分支中修复的。 -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ![按分支过滤警报](/assets/images/help/repository/code-scanning-branch-filter.png) {% else %} ![按分支过滤警报](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-filter.png) @@ -185,9 +198,9 @@ The benefit of using keyword filters is that only values with results are shown ![删除警报](/assets/images/help/repository/code-scanning-delete-alerts.png) - （可选）您可以使用{% ifversion fpt or ghes > 3.1 %} 自由文本搜索或{% endif %} 过滤器显示警报子集，然后一次删除所有匹配的警报。 例如，如果您从 {% data variables.product.prodname_codeql %} 分析中删除了查询，您可以使用“Rule（规则）”过滤器仅列出该查询的警报，然后选择并删除所有这些警报。 + （可选）您可以使用{% ifversion fpt or ghes > 3.1 or ghae-next %} 自由文本搜索或{% endif %} 过滤器显示警报子集，然后一次删除所有匹配的警报。 例如，如果您从 {% data variables.product.prodname_codeql %} 分析中删除了查询，您可以使用“Rule（规则）”过滤器仅列出该查询的警报，然后选择并删除所有这些警报。 -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ![按规则过滤警报](/assets/images/help/repository/code-scanning-filter-by-rule.png) {% else %} ![按规则过滤警报](/assets/images/enterprise/3.1/help/repository/code-scanning-filter-by-rule.png) @@ -195,12 +208,11 @@ The benefit of using keyword filters is that only values with results are shown 1. 如果要忽略警报，请务必先了解警报，以便选择正确的忽略原因。 单击要了解的警报。 -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ![从摘要列表中打开警报](/assets/images/help/repository/code-scanning-click-alert.png) {% else %} ![来自 {% data variables.product.prodname_code_scanning %} 的警报列表](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) {% endif %} - 1. 查看警报，然后单击 **Dismiss（忽略）**并选择关闭警报的原因。 ![选择忽略警报的原因](/assets/images/help/repository/code-scanning-alert-close-drop-down.png) {% data reusables.code-scanning.choose-alert-dismissal-reason %} 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 0ab74be67a..64022211a0 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 @@ -40,8 +40,8 @@ topics: {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} -3. 在“{% data variables.product.prodname_code_scanning_capc %} 警报”右侧，单击**设置 {% data variables.product.prodname_code_scanning %}**。 {% ifversion fpt or ghes > 3.0 %}如果 {% data variables.product.prodname_code_scanning %} 缺少，您必须要求组织所有者或仓库管理员启用 {% data variables.product.prodname_GH_advanced_security %}。 更多信息请参阅“[管理组织的安全性和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”或“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)”。{% endif %} !["Set up code scanning" button to the right of "Code scanning" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png) -4. Under "Get started with code scanning", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png){% ifversion fpt or ghes > 2.22 %}工作流程仅在与仓库中检测到的编程语言相关时才会显示。 {% data variables.product.prodname_codeql_workflow %} 始终显示，但仅在 {% data variables.product.prodname_codeql %} 分析支持仓库中存在的语言时才启用“Set up this workflow（设置此工作流程）”按钮。{% endif %} +3. 在“{% data variables.product.prodname_code_scanning_capc %} 警报”右侧，单击**设置 {% data variables.product.prodname_code_scanning %}**。 {% ifversion fpt or ghes > 3.0 or ghae-next %}如果 {% data variables.product.prodname_code_scanning %} 缺少，您必须要求组织所有者或仓库管理员启用 {% data variables.product.prodname_GH_advanced_security %}。 更多信息请参阅“[管理组织的安全性和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”或“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)”。{% endif %} !["Set up code scanning" button to the right of "Code scanning" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png) +4. Under "Get started with code scanning", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png){% ifversion fpt or ghes > 2.22 or ghae-next %}工作流程仅在与仓库中检测到的编程语言相关时才会显示。 {% data variables.product.prodname_codeql_workflow %} 始终显示，但仅在 {% data variables.product.prodname_codeql %} 分析支持仓库中存在的语言时才启用“Set up this workflow（设置此工作流程）”按钮。{% endif %} 5. Optionally, to customize how {% data variables.product.prodname_code_scanning %} scans your code, edit the workflow. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning)." 一般来说，您可以提交 {% data variables.product.prodname_codeql_workflow %} 而不对其做任何更改。 但是，许多第三方工作流程需要额外的配置，因此在提交之前请阅读工作流程中的注释。 @@ -53,10 +53,43 @@ topics: 在默认 {% data variables.product.prodname_codeql_workflow %} 中，{% data variables.product.prodname_code_scanning %} 配置为在每次将更改推送到默认分支或任何受保护分支或者对默认分支提出拉取请求时分析代码。 因此，{% data variables.product.prodname_code_scanning %} 将立即开始。 +The `on:pull_request` and `on:push` triggers for code scanning are each useful for different purposes. For more information, see "[Scanning pull requests](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-pull-requests)" and "[Scanning on push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)." ## 批量设置 {% data variables.product.prodname_code_scanning %} 您可以使用脚本在多个仓库中一次设置 {% data variables.product.prodname_code_scanning %}。 If you'd like to use a script to raise pull requests that add a {% data variables.product.prodname_actions %} workflow to multiple repositories, see the [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) repository for an example using Powershell, or [`nickliffen/ghas-enablement`](https://github.com/NickLiffen/ghas-enablement) for teams who do not have Powershell and instead would like to use NodeJS. +## You decide how you generate {% data variables.product.prodname_code_scanning %} alerts, and which tools you use, at a repository level. {% data variables.product.product_name %} provides fully integrated support for {% data variables.product.prodname_codeql %} analysis, and also supports analysis using third-party tools. For more information, see "[About {% data variables.product.prodname_codeql %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning#about-codeql)." + +为仓库设置 {% data variables.product.prodname_code_scanning %} 后，您可以关注操作运行时的输出。 + +{% data reusables.repositories.actions-tab %} + + You can view the run status of {% data variables.product.prodname_code_scanning %} and get notifications for completed runs. For more information, see "[Managing a workflow run](/actions/configuring-and-managing-workflows/managing-a-workflow-run)" and "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)." 条目的文本是提交消息的标题。 + + ![After you commit the workflow file or create a pull request, {% data variables.product.prodname_code_scanning %} will analyze your code according to the frequency you specified in your workflow file. If you created a pull request, {% data variables.product.prodname_code_scanning %} will only analyze the code on the pull request's topic branch until you merge the pull request into the default branch of the repository.](/assets/images/help/repository/code-scanning-actions-list.png) + +1. 单击 {% data variables.product.prodname_code_scanning %} 工作流程的项目。 + +1. 单击左侧的作业名称。 例如 **Analyze (LANGUAGE)**。 + + ![{% data variables.product.prodname_code_scanning %} 工作流程的日志输出](/assets/images/help/repository/code-scanning-logging-analyze-action.png) + +1. 查看此工作流运行时操作的日志记录输出。 + +1. 在所有作业完成后，您可以查看已识别的任何 {% data variables.product.prodname_code_scanning %} 警报的详细信息。 更多信息请参阅“[管理仓库的 {% data variables.product.prodname_code_scanning %} 警报](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)”。 + +{% note %} + +**注意：** 如果您提出拉取请求以将 {% data variables.product.prodname_code_scanning %} 工作流程添加到仓库，则在合并拉取请求之前，来自该拉取请求的警报不会直接显示在 {% data variables.product.prodname_code_scanning_capc %} 页面上。 如果发现任何警报，您可以在合并拉取请求之前查看这些警报，方法是在 {% data variables.product.prodname_code_scanning_capc %} 页面上的横幅中点击**发现的 _n_ 条警报**链接。 + +{% ifversion fpt or ghes > 3.1 or ghae-next %} + ![点击"发现的 n 条警报"链接](/assets/images/help/repository/code-scanning-alerts-found-link.png) +{% else %} + ![点击"发现的 n 条警报"链接](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png) +{% endif %} + +{% endnote %} + ## 了解拉取请求检查 设置在拉取请求上运行的每个 {% data variables.product.prodname_code_scanning %} 工作流程始终有至少两个条目列在拉取请求的检查部分中。 工作流程中每个分析作业有一个条目，最后还有一个对应于分析结果的条目。 @@ -65,13 +98,25 @@ topics: ![After a scan completes, you can view alerts from a completed scan. For more information, see "Managing alerts from {% data variables.product.prodname_code_scanning %}."](/assets/images/help/repository/code-scanning-pr-checks.png) -当 {% data variables.product.prodname_code_scanning %} 作业完成后， {% data variables.product.prodname_dotcom %} 检查拉取请求是否添加了任何警报，并将“{% data variables.product.prodname_code_scanning_capc %} 结果/工具名称”条目添加到检查列表中。 在执行至少一次 {% data variables.product.prodname_code_scanning %} 后，您可以单击 **Details（详细信息）**查看分析结果。 如果使用拉取请求将 {% data variables.product.prodname_code_scanning %} 添加到存储库，则当您单击“{% data variables.product.prodname_code_scanning_capc %} 结果/工具名称”检查中的 **Details（详细信息）**时，您最初会看到“Missing analysis（缺少分析）”的消息。 +当 {% data variables.product.prodname_code_scanning %} 作业完成后， {% data variables.product.prodname_dotcom %} 检查拉取请求是否添加了任何警报，并将“{% data variables.product.prodname_code_scanning_capc %} 结果/工具名称”条目添加到检查列表中。 在执行至少一次 {% data variables.product.prodname_code_scanning %} 后，您可以单击 **Details（详细信息）**查看分析结果。 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 %}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. - ![缺少提交消息的分析](/assets/images/help/repository/code-scanning-missing-analysis.png) +{% ifversion fpt or ghes > 3.2 or ghae-issue-3891 %} + ![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. -在 {% data variables.product.prodname_code_scanning %} 分析拉取请求中的代码后，它需要将主题分支（用于创建拉取请求的分支）的分析与基本分支（要合并拉取请求的分支）的分析进行比较。 这允许 {% data variables.product.prodname_code_scanning %} 计算哪些警报是拉取请求新近引入的，哪些是基础分支中已经存在的，以及是否有任何现有的警报通过拉取请求中的更改来修复。 最初，如果使用拉取请求将 {% data variables.product.prodname_code_scanning %} 添加到仓库，则尚未分析基础分支，因此无法计算这些详细信息。 在这种情况下，当您从拉取请求的结果检查中点进时，将看到“Missing analysis for base commit SHA-HASH（缺少基础提交 SHA-HASH 的分析）”消息。 +For example, in the screenshot above, {% data variables.product.prodname_code_scanning %} found an analysis for the merge commit of the pull request, but no analysis for the head of the main branch. +{% else %} + ![缺少提交消息的分析](/assets/images/enterprise/3.2/repository/code-scanning-missing-analysis.png) +{% endif %} + +{% ifversion fpt or ghes > 3.2 or ghae-issue-3891 %} +### Reasons for the "Analysis not found" message +{% else %} +### Reasons for the "Missing analysis" message +{% endif %} + +在 {% data variables.product.prodname_code_scanning %} 分析拉取请求中的代码后，它需要将主题分支（用于创建拉取请求的分支）的分析与基本分支（要合并拉取请求的分支）的分析进行比较。 这允许 {% data variables.product.prodname_code_scanning %} 计算哪些警报是拉取请求新近引入的，哪些是基础分支中已经存在的，以及是否有任何现有的警报通过拉取请求中的更改来修复。 最初，如果使用拉取请求将 {% data variables.product.prodname_code_scanning %} 添加到仓库，则尚未分析基础分支，因此无法计算这些详细信息。 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 %}"Analysis not found"{% else %}"Missing analysis for base commit SHA-HASH"{% endif %} message. 在其他情况下，可能没有分析对拉取请求的基础分支的最新提交。 这些包括： @@ -79,7 +124,7 @@ topics: 要检查是否扫描了分支，请转到 {% data variables.product.prodname_code_scanning_capc %} 页面，单击 **Branch<（分支）**下拉菜单并选择相关分支。 -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ![从 Branch（分支）下拉菜单中选择一个分支](/assets/images/help/repository/code-scanning-branch-dropdown.png) {% else %} ![从 Branch（分支）下拉菜单中选择一个分支](/assets/images/enterprise/3.1/help/repository/code-scanning-branch-dropdown.png) 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 dc8e8d039e..b86786a32d 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,6 +28,9 @@ 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 %} +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 %} If your pull request targets a protected branch that uses {% data variables.product.prodname_code_scanning %}, and the repository owner has configured required status checks, then the "{% data variables.product.prodname_code_scanning_capc %} results" check must pass before you can merge the pull request. 更多信息请参阅“[关于受保护分支](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)”。 diff --git a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md index 4ddf78d355..176026d1df 100644 --- a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md +++ b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md @@ -22,7 +22,7 @@ shortTitle: 查看代码扫描日志 您可以使用各种工具在仓库中设置 {% data variables.product.prodname_code_scanning %} 。 更多信息请参阅“[为仓库设置 {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#options-for-setting-up-code-scanning)”。 -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} 您可用的日志和诊断信息取决于您在 {% data variables.product.prodname_code_scanning %} 中使用的方法。 您可以使用警报列表中的 **Tool（工具）**下拉菜单，检查仓库的 **Security（安全）**选项卡中使用的 {% data variables.product.prodname_code_scanning %} 类型。 更多信息请参阅“[管理仓库的 {% data variables.product.prodname_code_scanning %} 警报](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)”。 ## 关于分析和诊断信息 @@ -35,7 +35,7 @@ shortTitle: 查看代码扫描日志 如果您在 {% data variables.product.prodname_dotcom %} 外部使用 {% data variables.product.prodname_codeql_cli %} ，您将在数据库分析期间生成的输出中看到诊断信息。 此信息也包含在您随 {% data variables.product.prodname_code_scanning %} 结果上传到 {% data variables.product.prodname_dotcom %} 的 SARIF 结果文件中。 -有关 {% data variables.product.prodname_codeql_cli %} 的信息，请参阅“[在 CI 系统中运行 {% data variables.product.prodname_codeql_cli %}](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-cli-in-your-ci-system#viewing-log-and-diagnostic-information)”。 +For information about the {% data variables.product.prodname_codeql_cli %}, see "[Configuring {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system#viewing-log-and-diagnostic-information)." ### 关于摘要指标 @@ -72,7 +72,7 @@ shortTitle: 查看代码扫描日志 **注意：** 如果您提出拉取请求以将 {% data variables.product.prodname_code_scanning %} 工作流程添加到仓库，则在合并拉取请求之前，来自该拉取请求的警报不会直接显示在 {% data variables.product.prodname_code_scanning_capc %} 页面上。 如果发现任何警报，您可以在合并拉取请求之前查看这些警报，方法是在 {% data variables.product.prodname_code_scanning_capc %} 页面上的横幅中点击**发现的 _n_ 条警报**链接。 -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae %} ![点击"发现的 n 条警报"链接](/assets/images/help/repository/code-scanning-alerts-found-link.png) {% else %} ![点击"发现的 n 条警报"链接](/assets/images/enterprise/3.1/help/repository/code-scanning-alerts-found-link.png) diff --git a/translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md b/translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md index cebbbc43d8..cb547cdafd 100644 --- a/translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md +++ b/translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md @@ -37,7 +37,7 @@ SARIF（数据分析结果交换格式）是定义输出文件格式的 [OASIS {% ifversion fpt or ghes > 3.0 or ghae-next %} 如果您使用的是 {% data variables.product.prodname_codeql_cli %}，则可以指定要使用的 SARIF 版本。 更多信息请参阅“[在 CI 系统中配置 {% data variables.product.prodname_codeql_cli %}](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system#analyzing-a-codeql-database)”。{% endif %} -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} 您可以为相同的工具和提交上传多个 SARIF 文件，并使用 {% data variables.product.prodname_code_scanning %} 分析每个文件。 您可以在每个文件中指定 `runautomationDetails.id` 来表示每个分析的“类别”。 只有具有相同类别的 SARIF 文件才会相互覆盖。 关于此属性的更多信息，请参阅下面的 [`runAutomationDetails` 对象](#runautomationdetails-object)。 {% endif %} @@ -141,7 +141,7 @@ SARIF（数据分析结果交换格式）是定义输出文件格式的 [OASIS | `region.endLine` | **必选。**区域中最后一个字符的行号。 | | `region.endColumn` | **必选。**区域结束后字符的列编号。 | -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ### `runAutomationDetails` 对象 `runAutomationDetails` 对象包含指定运行身份的信息。 @@ -245,7 +245,7 @@ SARIF（数据分析结果交换格式）是定义输出文件格式的 [OASIS 此 SARIF 输出文件的示例值显示了 {% data variables.product.prodname_code_scanning %} 的所有受支持 SARIF 属性。 -{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt or ghes > 3.1 or ghae-next %} ```json { "$schema": "https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json", diff --git a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md index 40dfc5853b..7edc62be02 100644 --- a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md +++ b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md @@ -91,8 +91,8 @@ redirect_from: {% endif %} - -{% ifversion ghes = 3.0 or ghae %} + +{% ifversion ghes = 3.0 %} {% data reusables.code-scanning.upload-sarif-ghas %} 将 {% data variables.product.prodname_codeql_runner %} 添加到第三方系统，然后调用工具分析代码并将 SARIF 结果上传到 {% data variables.product.product_name %}。 由此产生的 {% data variables.product.prodname_code_scanning %} 警报与 {% data variables.product.product_name %} 内生成的任何警报一起显示。 diff --git a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md index bfba33c401..4c8a10fc0a 100644 --- a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md +++ b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md @@ -30,7 +30,7 @@ topics: 您使用三个不同的命令生成结果并将它们上传到 {% data variables.product.product_name %}： -{% ifversion fpt or ghes > 3.1 or ghae-next %} +{% ifversion fpt or ghes > 3.1 or ghae %} 1. `database create` 以创建 {% data variables.product.prodname_codeql %} 数据库，以代表仓库中每种支持的编程语言的层次结构。 2. `database analyze` 以运行查询，以分析每个 {% data variables.product.prodname_codeql %} 数据库，并在 SARIF 文件中概括结果。 @@ -50,11 +50,11 @@ topics: 1. 检出要分析的代码： - 对于分支，请检出要分析的分支的头部。 - - 对于拉取请求，请检出拉取请求的头部提交，或检出 {% data variables.product.product_name %} 生成的拉取请求的合并提交。 + - 对于拉取请求，请检出拉取请求的头部提交，或检出 {% data variables.product.prodname_dotcom %} 生成的拉取请求的合并提交。 2. 设置代码库的环境，确保任何依赖项都可用。 更多信息请参阅 {% data variables.product.prodname_codeql_cli %} 文档中的[为非编译语言创建数据库](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#creating-databases-for-non-compiled-languages)和[为编译语言创建数据库](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#creating-databases-for-compiled-languages)。 3. 查找代码库的生成命令（如果有）。 这通常在 CI 系统的配置文件中可用。 4. 从仓库的检出根目录运行 `codeql database create` 并构建代码库。 - {% ifversion fpt or ghes > 3.1 or ghae-next %} + {% ifversion fpt or ghes > 3.1 or ghae %} ```shell # Single supported language - create one CodeQL databsae codeql database create <database> --command<build> --language=<language-identifier> @@ -119,7 +119,7 @@ topics:
    - {% ifversion fpt or ghes > 3.1 or ghae-next %}当使用 `--db-cluster`时，该选项接受逗号分隔的列表，或者可以指定多次。{% endif %} + {% ifversion fpt or ghes > 3.1 or ghae %}当使用 `--db-cluster`时，该选项接受逗号分隔的列表，或者可以指定多次。{% endif %} @@ -144,7 +144,7 @@ topics:
    - {% ifversion fpt or ghes > 3.1 or ghae-next %} + {% ifversion fpt or ghes > 3.1 or ghae %} @@ -208,7 +208,7 @@ topics: 更多信息请参阅 {% data variables.product.prodname_codeql_cli %} 文档中的[创建 {% data variables.product.prodname_codeql %} 数据库](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/)。 -### {% ifversion fpt or ghes > 3.1 or ghae-next %}单一语言示例{% else %}基本示例{% endif %} +### {% ifversion fpt or ghes > 3.1 or ghae %}单一语言示例{% else %}基本示例{% endif %} 此示例在 `/checkouts/example-repo` 为检出的仓库创建 {% data variables.product.prodname_codeql %} 数据库。 它使用 JavaScript 提取器在仓库中创建 JavaScript 和 TypeScript 代码的分层表示。 生成的数据库存储在 `/codeql-dbs/example-repo` 中。 @@ -226,7 +226,7 @@ $ codeql database create /codeql-dbs/example-repo --language=javascript \ > Successfully created database at /codeql-dbs/example-repo. ``` -{% ifversion fpt or ghes > 3.1 or ghae-next %} +{% ifversion fpt or ghes > 3.1 or ghae %} ### 多语言示例 此示例在 `/checkouts/example-repo` 为检出的仓库创建两个 {% data variables.product.prodname_codeql %} 数据库。 它使用： @@ -273,7 +273,7 @@ Successfully created databases at /codeql-dbs/example-repo-multi. --output=<output> {% if codeql-packs %}<packs,queries>{% else %} <queries>{% endif %} ``` -{% ifversion fpt or ghes > 3.1 or ghae-next %} +{% ifversion fpt or ghes > 3.1 or ghae %} {% note %} **注意：** 如果您分析了一个以上的 {% data variables.product.prodname_codeql %} 数据库的单项提交，您必须为此命令生成的每组结果指定 SARIF 类别。 当您上传结果到 {% data variables.product.product_name %} 时，{% data variables.product.prodname_code_scanning %} 使用此类别来分别存储每种语言的结果。 如果你忘记了这样做，每次上传都会覆盖以前的结果。 @@ -317,15 +317,14 @@ codeql database analyze <database> --format=<format> \
    - <queries> + <packs,queries> - {% octicon "check-circle-fill" aria-label="Required" %} - 指定要运行的查询。 要运行用于 {% data variables.product.prodname_code_scanning %} 的标准查询，请使用: <language>-code-scanning.qls，其中 <language> 是数据库语言的短代码。 要查看 {% data variables.product.prodname_codeql_cli %} 捆绑包中包含的其他查询套件，请查看 /<extraction-root>/codeql/qlpacks/codeql-<language>/codeql-suites。 有关创建您自己的查询套件的信息，请参阅 {% data variables.product.prodname_codeql_cli %} 文档中的创建 CodeQL 查询套件。 + Specify {% data variables.product.prodname_codeql %} packs or queries to run. To run the standard queries used for {% data variables.product.prodname_code_scanning %}, omit this parameter. 要查看 {% data variables.product.prodname_codeql_cli %} 捆绑包中包含的其他查询套件，请查看 /<extraction-root>/codeql/qlpacks/codeql-<language>/codeql-suites。 有关创建您自己的查询套件的信息，请参阅 {% data variables.product.prodname_codeql_cli %} 文档中的创建 CodeQL 查询套件。
    - 指定保存 SARIF 结果文件的位置。{% ifversion fpt or ghes > 3.1 or ghae-next %} + 指定保存 SARIF 结果文件的位置。{% ifversion fpt or ghes > 3.1 or ghae %}
    - 可选. 用于从数据库创建过程获取有关分析过程的更详细的信息{% ifversion fpt or ghes > 3.1 or ghae-next %} 和诊断数据{% endif %}。 + 可选. 用于从数据库创建过程获取有关分析过程的更详细的信息{% ifversion fpt or ghes > 3.1 or ghae %} 和诊断数据{% endif %}。
    @@ -415,11 +414,11 @@ codeql database analyze <database> --format=<format> \ ### 基本示例 -此示例分析存储在 `/codeql-dbs/example-repo` 的 {% data variables.product.prodname_codeql %} 数据库并将结果保存为 SARIF 文件： `/temple/example-repo-js.sarif`。 {% ifversion fpt or ghes > 3.1 or ghae-next %}它使用 `--sarif-category` 在 SARIF 文件中包括额外的信息，以将结果标识为 JavaScript。 当您有多个 {% data variables.product.prodname_codeql %} 数据库来分析仓库中的单个提交时，这一点至关重要。{% endif %} +此示例分析存储在 `/codeql-dbs/example-repo` 的 {% data variables.product.prodname_codeql %} 数据库并将结果保存为 SARIF 文件： `/temple/example-repo-js.sarif`。 {% ifversion fpt or ghes > 3.1 or ghae %}它使用 `--sarif-category` 在 SARIF 文件中包括额外的信息，以将结果标识为 JavaScript。 当您有多个 {% data variables.product.prodname_codeql %} 数据库来分析仓库中的单个提交时，这一点至关重要。{% endif %} ``` $ codeql database analyze /codeql-dbs/example-repo \ - javascript-code-scanning.qls {% ifversion fpt or ghes > 3.1 or ghae-next %}--sarif-category=javascript{% endif %} + javascript-code-scanning.qls {% ifversion fpt or ghes > 3.1 or ghae %}--sarif-category=javascript{% endif %} --format={% ifversion fpt or ghae %}sarif-latest{% else %}sarifv2.1.0{% endif %} --output=/temp/example-repo-js.sarif > Running queries. @@ -444,7 +443,7 @@ $ codeql database analyze /codeql-dbs/example-repo \ ```shell echo "$UPLOAD_TOKEN" | codeql github upload-results --repository=<repository-name> \ --ref=<ref> --commit=<commit> --sarif=<file> \ - {% ifversion ghes > 3.0 or ghae-next %}--github-url=<URL> {% endif %}--github-auth-stdin + {% ifversion ghes > 3.0 or ghae %}--github-url=<URL> {% endif %}--github-auth-stdin ``` @@ -486,7 +485,7 @@ $ codeql database analyze /codeql-dbs/example-repo \ @@ -514,7 +513,7 @@ $ codeql database analyze /codeql-dbs/example-repo \ @@ -555,7 +554,7 @@ $ codeql database analyze /codeql-dbs/example-repo \ ``` $ echo $UPLOAD_TOKEN | codeql github upload-results --repository=my-org/example-repo \ --ref=refs/heads/main --commit=deb275d2d5fe9a522a0b7bd8b6b6a1c939552718 \ - --sarif=/temp/example-repo-js.sarif {% ifversion ghes > 3.0 or ghae-next %}--github-url={% data variables.command_line.git_url_example %} \ + --sarif=/temp/example-repo-js.sarif {% ifversion ghes > 3.0 or ghae %}--github-url={% data variables.command_line.git_url_example %} \ {% endif %}--github-auth-stdin ``` @@ -641,6 +640,7 @@ $ codeql database analyze /codeql-dbs/example-repo octo-org/security-queries \ {% endif %} {% ifversion fpt or ghes > 3.1 or ghae-next %} + ## 用于 {% data variables.product.prodname_codeql %} 分析的示例 CI 配置 这是一系列命令的示例，您可以使用两种支持的语言分析代码库，然后上传结果到 {% data variables.product.product_name %}。 diff --git a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md index 1dbe860ee2..114d85767d 100644 --- a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md +++ b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md @@ -191,7 +191,7 @@ $ /path/to-runner/codeql-runner-linux autobuild --language csharp | `--no-upload` | | 无. 阻止 {% data variables.product.prodname_codeql_runner %} 将结果上传到 {% data variables.product.product_name %}。 | | `--output-dir` | | 存储输出 SARIF 文件的目录。 默认在临时文件目录中。 | | `--ram` | | 运行查询时要使用的内存量。 默认使用所有可用的内存。 | -| `--no-add-snippets` | | 无. 从 SARIF 输出排除代码片段。 |{% ifversion fpt or ghes > 3.1 %} +| `--no-add-snippets` | | 无. 从 SARIF 输出排除代码片段。 |{% ifversion fpt or ghes > 3.1 or ghae %} | `--category` | | 用于此分析的 SARIF 结果文件中要包含的类别。 类别可用于区分同一工具和提交的多次分析，但是在不同语言或代码的不同部分进行。 此值将显示在 SARIF v2.1.0 的 `.automationDetails.id` 属性中。 {% endif %} | `--threads` | | 运行查询时要使用的线程数。 默认使用所有可用的核心。 | diff --git a/translations/zh-CN/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md b/translations/zh-CN/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md index 7e38a44808..7af4af1d64 100644 --- a/translations/zh-CN/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md +++ b/translations/zh-CN/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md @@ -25,7 +25,7 @@ topics: {% data variables.product.company_short %} 在 {% ifversion fpt %}公共和私有{% endif %} 仓库中执行performs {% data variables.product.prodname_secret_scanning %}，以用于 {% data variables.product.company_short %} 和 {% data variables.product.company_short %} 模式提供的密钥模式。 有关 {% data variables.product.prodname_secret_scanning %} 合作伙伴计划的更多信息，请参阅“密码扫描合作伙伴计划”。 -但是，在某些情况下，您需要扫描 {% ifversion fpt %}私有{% endif %} 仓库中的其他密钥模式。 例如，您可能有一个属于您组织内部的密钥模式。 For these situations, you can define custom {% data variables.product.prodname_secret_scanning %} patterns in your enterprise, organization, or {% ifversion fpt %}private{% endif %} repository on {% data variables.product.product_name %}. You can define up to 20 custom patterns for each {% ifversion fpt %}private{% endif %} repository, organization, or enterprise account. +但是，在某些情况下，您需要扫描 {% ifversion fpt %}私有{% endif %} 仓库中的其他密钥模式。 例如，您可能有一个属于您组织内部的密钥模式。 For these situations, you can define custom {% data variables.product.prodname_secret_scanning %} patterns in your enterprise, organization, or {% ifversion fpt %}private{% endif %} repository on {% data variables.product.product_name %}. You can define up to 100 custom patterns for each organization or enterprise account, and up to 20 custom patterns per {% ifversion fpt %}private{% endif %} repository. {% ifversion ghes < 3.3 or ghae %} {% note %} diff --git a/translations/zh-CN/content/code-security/security-advisories/publishing-a-security-advisory.md b/translations/zh-CN/content/code-security/security-advisories/publishing-a-security-advisory.md index 7288cc578f..3d991decf6 100644 --- a/translations/zh-CN/content/code-security/security-advisories/publishing-a-security-advisory.md +++ b/translations/zh-CN/content/code-security/security-advisories/publishing-a-security-advisory.md @@ -61,19 +61,6 @@ shortTitle: 发布咨询意见 如果需要更新或更正已发布的安全通告中的信息，可以编辑安全通告。 更多信息请参阅“[编辑安全通告](/github/managing-security-vulnerabilities/editing-a-security-advisory)”。 -## 申请 CVE 识别号 - -对安全通告具有管理员权限的任何人都可以为安全通告申请 CVE 标识号。 - -{% data reusables.repositories.request-security-advisory-cve-id %} 更多信息请参阅“[关于 {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories#cve-identification-numbers)”。 - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-security %} -{% data reusables.repositories.sidebar-advisories %} -4. 在“Security Advisories（安全通告）”列表中，单击要为其申请 CVE 识别号的安全通告。 ![列表中的安全通告](/assets/images/help/security/security-advisory-in-list.png) -5. 使用 **Publish advisory（发布通告）**下拉菜单，然后单击 **Request CVE（申请 CVE）**。 ![下拉列表中的“申请 CVE”](/assets/images/help/security/security-advisory-drop-down-request-cve.png) -6. 单击 **Request CVE（申请 CVE）**。 ![申请 CVE 按钮](/assets/images/help/security/security-advisory-request-cve-button.png) - ## 发布安全通告 发布安全通告会删除该安全通告的临时私有复刻。 @@ -88,6 +75,17 @@ shortTitle: 发布咨询意见 {% data reusables.repositories.github-reviews-security-advisories %} +## Requesting a CVE identification number (Optional) + +{% data reusables.repositories.request-security-advisory-cve-id %} 更多信息请参阅“[关于 {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories#cve-identification-numbers)”。 + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-security %} +{% data reusables.repositories.sidebar-advisories %} +4. 在“Security Advisories（安全通告）”列表中，单击要为其申请 CVE 识别号的安全通告。 ![列表中的安全通告](/assets/images/help/security/security-advisory-in-list.png) +5. 使用 **Publish advisory（发布通告）**下拉菜单，然后单击 **Request CVE（申请 CVE）**。 ![下拉列表中的“申请 CVE”](/assets/images/help/security/security-advisory-drop-down-request-cve.png) +6. 单击 **Request CVE（申请 CVE）**。 ![申请 CVE 按钮](/assets/images/help/security/security-advisory-request-cve-button.png) + ## 延伸阅读 - "[撤销安全通告](/github/managing-security-vulnerabilities/withdrawing-a-security-advisory)" 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 87d3b68673..d133131a4f 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 @@ -6,8 +6,8 @@ redirect_from: - /code-security/security-overview/exploring-security-alerts versions: fpt: '*' + ghae: issue-4554 ghes: '>3.1' - ghae: next type: how_to topics: - Security overview 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 a043f75d87..0a9f405893 100644 --- a/translations/zh-CN/content/code-security/security-overview/index.md +++ b/translations/zh-CN/content/code-security/security-overview/index.md @@ -5,8 +5,8 @@ intro: 在一个位置查看、排序和过滤整个组织的安全警报。 product: '{% data reusables.gated-features.security-center %}' versions: fpt: '*' + ghae: issue-4554 ghes: '>3.1' - ghae: next topics: - Security overview - Advanced Security 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 bae226e04e..59be1cdda5 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 @@ -1,11 +1,11 @@ --- title: 关于依赖项审查 intro: 依赖项审查可让您在将有漏洞的依赖项引入您的环境之前找到它们，并提供关于许可证、依赖项和依赖项存在时间的信息。 +product: '{% data reusables.gated-features.dependency-review %}' shortTitle: 依赖项审查 versions: fpt: '*' ghes: '>= 3.2' - product: '{% data reusables.gated-features.dependency-review %}' type: overview topics: - Advanced Security diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/index.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/index.md index 3e5858cbba..e34b423447 100644 --- a/translations/zh-CN/content/codespaces/developing-in-codespaces/index.md +++ b/translations/zh-CN/content/codespaces/developing-in-codespaces/index.md @@ -15,6 +15,5 @@ children: - /forwarding-ports-in-your-codespace - /changing-the-machine-type-for-your-codespace - /using-codespaces-in-visual-studio-code - - /web-based-editor --- 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 2cf7087ded..2e680a5408 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 @@ -30,9 +30,7 @@ shortTitle: 源控制 ## 创建或切换分支 -1. 如果当前分支未显示在状态栏中，请在代码空间的底部右键单击状态栏，然后选择 **Source control（源控制）**。 -1. 单击状态栏中的分支名称。 ![状态栏中的分支](/assets/images/help/codespaces/branch-in-status-bar.png) -1. 在下拉菜单中，单击要切换到的分支或输入新分支的名称，然后单击 **Create new branch（创建新分支）**。 ![从分支菜单中选择](/assets/images/help/codespaces/create-new-branch.png) +{% data reusables.codespaces.create-or-switch-branch %} {% tip %} @@ -64,16 +62,11 @@ If the dev container configuration has been changed since you created the codesp ## 提交更改 -{% data reusables.codespaces.source-control-display-dark %} -1. 要暂存更改，请单击已更改文件旁边的 **+**；如果您更改了多个文件并且要全部暂存，请单击 **Changes（更改）**旁边的该按钮。 ![高亮显示暂存按钮的源控制侧边栏](/assets/images/help/codespaces/codespaces-commit-stage.png) -1. 输入提交消息，描述您所做的更改。 ![带有提交消息的源控制侧栏](/assets/images/help/codespaces/codespaces-commit-commit-message.png) -1. 要提交暂存的更改，请单击源控制侧栏顶部的复选标记。 ![单击复选标记图标](/assets/images/help/codespaces/codespaces-commit-checkmark-icon.png) +{% data reusables.codespaces.source-control-commit-changes %} ## 提出拉取请求 -1. 将更改提交到仓库的本地副本后，请单击 **Create Pull Request（创建拉取请求）**图标。 ![高亮显示暂存按钮的源控制侧边栏](/assets/images/help/codespaces/codespaces-commit-pr-button.png) -1. 检查作为合并来源的本地分支和仓库以及作为合并目标的远程分支和仓库是否正确。 然后为拉取请求提供标题和描述。 ![高亮显示暂存按钮的源控制侧边栏](/assets/images/help/codespaces/codespaces-commit-pr.png) -1. 单击 **Create（创建）**。 +{% data reusables.codespaces.source-control-pull-request %} ## 将更改推送到远程仓库 diff --git a/translations/zh-CN/content/codespaces/index.md b/translations/zh-CN/content/codespaces/index.md index a125bf19e0..03d562f17d 100644 --- a/translations/zh-CN/content/codespaces/index.md +++ b/translations/zh-CN/content/codespaces/index.md @@ -41,6 +41,7 @@ children: - /managing-codespaces-for-your-organization - /codespaces-reference - /troubleshooting + - /the-githubdev-web-based-editor - /guides --- diff --git a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md index b77607a672..3ced795d55 100644 --- a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md +++ b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md @@ -72,3 +72,7 @@ topics: {% data reusables.github-actions.sidebar-secret %} 1. 密码列表包括任何已配置的权限和策略。 例如： ![密码列表](/assets/images/help/settings/actions-org-secrets-list.png) 1. 有关已为每个密码配置的权限的更多信息，请单击 **Update（更新）**。 + +## 延伸阅读 + +- "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)" diff --git a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md index bd5647914a..9c921b7a63 100644 --- a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md +++ b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md @@ -26,3 +26,7 @@ redirect_from: {% data reusables.organizations.click-codespaces %} 1. 在“Access and security（访问和安全）”下，为组织选择所需的设置。 ![管理信任仓库的单选按钮](/assets/images/help/settings/codespaces-org-access-and-security-radio-buttons.png) 1. 如果您选择了“Selected repositories（所选仓库）”，请选择下拉菜单，然后单击一个仓库，以允许该仓库的代码空间访问组织拥有的其他仓库。 对于您要允许其代码空间访问其他仓库的所有仓库重复此操作。 !["所选仓库" 下拉菜单](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) + +## 延伸阅读 + +- "[Managing repository access for your codespaces](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces)" diff --git a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md index 785ee66410..6d68fd5014 100644 --- a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md +++ b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md @@ -19,3 +19,7 @@ topics: ![包含代码空间信息的审核日志](/assets/images/help/settings/codespaces-audit-log-org.png) 审核日志包含操作执行人、操作内容和执行时间等详细信息。 有关 {% data variables.product.prodname_codespaces %} 操作的信息，请参阅“[{% data variables.product.prodname_codespaces %} 类别操作](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#codespaces-category-actions)”。 + +## 延伸阅读 + +- "[Reviewing your security logs for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces)" diff --git a/translations/zh-CN/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md b/translations/zh-CN/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md index 06872ebee9..d62458d3ec 100644 --- a/translations/zh-CN/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md +++ b/translations/zh-CN/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md @@ -73,3 +73,7 @@ shortTitle: 加密机密 {% data reusables.user_settings.codespaces-tab %} 1. 在“Codespaces secrets（代码空间密码）”下您要删除的密码右侧，单击 **Delete（删除）**。 !["删除" 按钮](/assets/images/help/settings/codespaces-secret-delete-button.png) 1. 阅读警告，然后单击 **OK（确定）**。 ![确认删除密码](/assets/images/help/settings/codespaces-secret-delete-warning.png) + +## 延伸阅读 + +- "[Managing encrypted secrets for your repository and organization for {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces)" diff --git a/translations/zh-CN/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md b/translations/zh-CN/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md index 847cc76dd6..016e0d3d6b 100644 --- a/translations/zh-CN/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md +++ b/translations/zh-CN/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md @@ -29,6 +29,6 @@ Once you enable GPG verification, it will immediately take effect for all your c {% note %} -**Note:** Once you have enabled GPG verification for {% data variables.product.prodname_codespaces %}, you also must append `-s` to each commit in order for it to be signed. To do this in {% data variables.product.prodname_vscode %}, ensure the "Git: Enable Commit Signing" option is enabled from the Settings. +**Note:** Once you have enabled GPG verification for {% data variables.product.prodname_codespaces %}, you also must append `-S` to each commit in order for it to be signed. To do this in {% data variables.product.prodname_vscode %}, ensure the "Git: Enable Commit Signing" option is enabled from the Settings. {% endnote %} 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 0a05eb775a..f103cc0f7b 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 @@ -20,3 +20,7 @@ redirect_from: {% data reusables.user_settings.codespaces-tab %} 1. 在“Access and security（访问和安全）”下，为用户帐户选择所需的设置。 ![管理信任仓库的单选按钮](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png) 1. 如果您选择了“Selected repositories（所选仓库）”，请选择下拉菜单，然后单击一个仓库，以允许该仓库的代码空间访问您拥有的其他仓库。 对于您要允许其代码空间访问您拥有的其他仓库的所有仓库重复此操作。 !["所选仓库" 下拉菜单](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) + +## 延伸阅读 + +- "[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/zh-CN/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md b/translations/zh-CN/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md index 74d092979d..d00c247b06 100644 --- a/translations/zh-CN/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md +++ b/translations/zh-CN/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md @@ -20,3 +20,7 @@ topics: ![包含代码空间信息的安全日志](/assets/images/help/settings/codespaces-audit-log.png) 安全日志包括发生了什么操作以及何时执行的操作等详细信息。 有关 {% data variables.product.prodname_codespaces %} 操作的信息，请参阅“[{% data variables.product.prodname_codespaces %} 类别操作](/github/authenticating-to-github/reviewing-your-security-log#codespaces-category-actions)”。 + +## 延伸阅读 + +- "[Reviewing your organization's audit logs for {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-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 new file mode 100644 index 0000000000..2267f68ebb --- /dev/null +++ b/translations/zh-CN/content/codespaces/the-githubdev-web-based-editor.md @@ -0,0 +1,106 @@ +--- +title: The github.dev web-based editor +intro: 'Use the github.dev {% data variables.product.prodname_serverless %} from your repository or pull request to create and commit changes.' +versions: + fpt: '*' +type: how_to +miniTocMaxHeadingLevel: 3 +topics: + - Codespaces + - Visual Studio Code + - Developer +shortTitle: Web-based editor +redirect_from: + - /codespaces/developing-in-codespaces/web-based-editor +--- + +{% note %} + +**Note:** The github.dev {% data variables.product.prodname_serverless %} is currently in beta preview. You can provide feedback [in our Discussions](https://github.co/browser-editor-feedback). + +{% endnote %} + +## 关于 {% data variables.product.prodname_serverless %} + +The {% data variables.product.prodname_serverless %} introduces a lightweight editing experience that runs entirely in your browser. With the {% data variables.product.prodname_serverless %}, you can navigate files and source code repositories from {% data variables.product.prodname_dotcom %}, and make and commit code changes. You can open any repository, fork, or pull request in the editor. + +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 %} 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. + +## Opening the {% data variables.product.prodname_serverless %} + +You can open any {% data variables.product.prodname_dotcom %} repository in the {% data variables.product.prodname_serverless %} in either of the following ways: + +- Press `.` while browsing any repository or pull request on {% data variables.product.prodname_dotcom %}. +- Change the URL from "github.com" to "github.dev". + +## {% data variables.product.prodname_codespaces %} and the {% data variables.product.prodname_serverless %} + +Both the {% data variables.product.prodname_serverless %} and {% data variables.product.prodname_codespaces %} allow you to edit your code straight from your repository. However, both have slightly different benefits, depending on your use case. + +| | {% data variables.product.prodname_serverless %} | {% data variables.product.prodname_codespaces %} +| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| **费用** | 免费. | Costs for compute and storage. For information on pricing, see "[Codespaces pricing](/en/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)." | +| **可用性** | Available to everyone on GitHub.com. | Available for organizations using GitHub Team or GitHub Enterprise Cloud. | +| **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. | + +### Continue working on {% data variables.product.prodname_codespaces %} + +You can start your workflow in the {% data variables.product.prodname_serverless %} and continue working on a codespace, provided you have [access to {% data variables.product.prodname_codespaces %}](/codespaces/developing-in-codespaces/creating-a-codespace#access-to-codespaces). If you try to access the Run and Debug View or the Terminal, you'll be notified that they are not available in the {% data variables.product.prodname_serverless %}. + +To continue your work in a codespace, click **Continue Working on…** and select **Create New Codespace** to create a codespace on your current branch. Before you choose this option, you must commit any changes. + +![A screenshot that shows the "Continue Working on" button in the UI](/assets/images/help/codespaces/codespaces-continue-working.png) + +## 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. + +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. + +### 创建新分支 + +{% data reusables.codespaces.create-or-switch-branch %} + Any uncommited changes you have made in your old branch will be available on your new branch. + +### Commit your changes + +{% data reusables.codespaces.source-control-commit-changes %} +5. Once you have committed your changes, they will automatically be pushed to your branch on {% data variables.product.prodname_dotcom %}. +### 创建拉取请求 + +{% data reusables.codespaces.source-control-pull-request %} + +### Working with an existing pull request + +You can use the {% data variables.product.prodname_serverless %} to work with an existing pull request. + +1. Browse to the pull request you'd like to open in the {% data variables.product.prodname_serverless %}. +2. Press `.` to open the pull request in the {% data variables.product.prodname_serverless %}. +3. Once you have made any changes, commit them using the steps in [Commit your changes](#commit-your-changes). Your changes will be committed directly to the branch, it's not necessary to push the changes. + +## 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. + +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. + + +## 疑难解答 + +If you have issues opening the {% data variables.product.prodname_serverless %}, try the following: + +- Make sure you are signed in to {% data variables.product.prodname_dotcom %}. +- Disable any ad blockers. +- Use a non-incognito window in your browser to open 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. diff --git a/translations/zh-CN/content/communities/documenting-your-project-with-wikis/about-wikis.md b/translations/zh-CN/content/communities/documenting-your-project-with-wikis/about-wikis.md index a58b71455c..443f1e0bf9 100644 --- a/translations/zh-CN/content/communities/documenting-your-project-with-wikis/about-wikis.md +++ b/translations/zh-CN/content/communities/documenting-your-project-with-wikis/about-wikis.md @@ -34,4 +34,4 @@ topics: - "[为 wiki 创建页脚或侧栏](/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki)" - "[编辑 wiki 内容](/communities/documenting-your-project-with-wikis/editing-wiki-content)" - "[查看 wiki 的更改记录](/articles/viewing-a-wiki-s-history-of-changes)" -- "[搜索 wikis](/articles/searching-wikis)" +- "[搜索 wikis](/search-github/searching-on-github/searching-wikis)" diff --git a/translations/zh-CN/content/communities/moderating-comments-and-conversations/locking-conversations.md b/translations/zh-CN/content/communities/moderating-comments-and-conversations/locking-conversations.md index fd873745f1..325657fff7 100644 --- a/translations/zh-CN/content/communities/moderating-comments-and-conversations/locking-conversations.md +++ b/translations/zh-CN/content/communities/moderating-comments-and-conversations/locking-conversations.md @@ -20,7 +20,7 @@ topics: 当对话锁定时，仅[具有写入权限的人员](/articles/repository-permission-levels-for-an-organization/)以及[仓库所有者和协作者](/articles/permission-levels-for-a-user-account-repository/#collaborator-access-for-a-repository-owned-by-a-user-account)才可添加、隐藏和删除评论。 -要搜索仓库中未存档的已锁定对话，可以使用搜索限定符 `is:locked` 和 `archived:false`。 对话在存档的仓库中会自动锁定。 更多信息请参阅“[搜索议题和拉取请求](/articles/searching-issues-and-pull-requests#search-based-on-whether-a-conversation-is-locked)”。 +要搜索仓库中未存档的已锁定对话，可以使用搜索限定符 `is:locked` 和 `archived:false`。 对话在存档的仓库中会自动锁定。 更多信息请参阅“[搜索议题和拉取请求](/search-github/searching-on-github/searching-issues-and-pull-requests#search-based-on-whether-a-conversation-is-locked)”。 1. 也可选择撰写注释，解释您锁定对话的原因。 2. 在议题或拉取请求的右边，或者提交页面中注释框的上方，单击 **Lock conversation（锁定对话）**。 ![锁定对话链接](/assets/images/help/repository/lock-conversation.png) diff --git a/translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels.md b/translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels.md index c995a25047..0c5f1565b3 100644 --- a/translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels.md +++ b/translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels.md @@ -12,7 +12,7 @@ topics: shortTitle: 鼓励参与 --- -您可以将 `good first issue` 标签应用到公共仓库中的议题，以便人们在按标签搜索时查找它们。 有关按标签搜索的更多信息，请参阅“[搜索议题和拉取请求](/articles/searching-issues-and-pull-requests/#search-by-label)”。 +您可以将 `good first issue` 标签应用到公共仓库中的议题，以便人们在按标签搜索时查找它们。 有关按标签搜索的更多信息，请参阅“[搜索议题和拉取请求](/search-github/searching-on-github/searching-issues-and-pull-requests/#search-by-label)”。 {% data variables.product.prodname_dotcom %} 使用算法确定每个仓库中最接近的议题，并将它们显示在 {% data variables.product.prodname_dotcom_the_website %} 上的不同位置。 添加 `good first issue` 标签可以提高您的议题显示的概率。 @@ -24,4 +24,4 @@ shortTitle: 鼓励参与 ## 延伸阅读 - "[关于标签](/articles/about-labels)" -- "[搜索仓库](/articles/searching-for-repositories)" +- "[搜索仓库](/search-github/searching-on-github/searching-for-repositories)" 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 8130e0dd3e..8b4daf3b25 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 @@ -42,6 +42,7 @@ shortTitle: 识别和授权用户 如果您在创建或修改应用程序时选择**在安装过程中请求用户授权 (OAuth)**，则步骤 1 将在应用程序安装过程中完成。 更多信息请参阅“[在安装过程中授权用户](/apps/installing-github-apps/#authorizing-users-during-installation)”。 ### 1. 请求用户的 GitHub 身份 +Direct the user to the following URL in their browser: GET {% data variables.product.oauth_host_code %}/login/oauth/authorize @@ -77,6 +78,8 @@ shortTitle: 识别和授权用户 过期用户令牌目前是一个可选的功能，可能会更改。 要选择使用用户到服务器令牌过期功能，请参阅“[激活应用程序的可选功能](/developers/apps/activating-optional-features-for-apps)”。 +Make a request to the following endpoint to receive an access token: + POST {% data variables.product.oauth_host_code %}/login/oauth/access_token #### 参数 diff --git a/translations/zh-CN/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md b/translations/zh-CN/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md index 1b96438959..1a9acfeb3e 100644 --- a/translations/zh-CN/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md +++ b/translations/zh-CN/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md @@ -32,7 +32,7 @@ Different server-to-server request rate limits apply to {% data variables.produc ### {% data variables.product.prodname_ghe_cloud %} 服务器到服务器速率限制 -{% data variables.product.prodname_github_apps %} that are installed on an organization or repository owned by a {% data variables.product.prodname_ghe_cloud %} account and make server-to-server requests have a rate limit of 15,000 requests per hour. +{% data variables.product.prodname_github_apps %} that are installed on an organization or repository owned by a {% data variables.product.prodname_ghe_cloud %} account and make server-to-server requests have a rate limit of 15,000 requests per hour per organization for organization installations or per repository for repository installations. {% 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 3627e4b256..c4ba806c4f 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 @@ -78,19 +78,29 @@ topics: 默认情况下，响应采用以下形式： - access_token={% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&token_type=bearer +``` +access_token={% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&scope=repo%2Cgist&token_type=bearer +``` -您也可以根据“接受”标头接收不同格式的内容： +{% data reusables.apps.oauth-auth-vary-response %} - Accept: application/json - {"access_token":"{% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "scope":"repo,gist", "token_type":"bearer"} - - Accept: application/xml - - bearer - repo,gist - {% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %} - +```json +Accept: application/json +{ + "access_token":"{% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", + "scope":"repo,gist", + "token_type":"bearer" +} +``` + +```xml +Accept: application/xml + + bearer + repo,gist + {% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %} + +``` ### 3. 使用访问令牌访问 API @@ -138,27 +148,35 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre #### 响应 -{% ifversion fpt %} - ```JSON - { - "device_code": "3584d83530557fdd1f46af8289938c8ef79f9dc5", - "user_code": "WDJB-MJHT", - "verification_uri": "https://github.com/login/device", - "expires_in": 900, - "interval": 5 - } - ``` -{% else %} - ```JSON - { - "device_code": "3584d83530557fdd1f46af8289938c8ef79f9dc5", - "user_code": "WDJB-MJHT", - "verification_uri": "http(s)://[hostname]/login/device", - "expires_in": 900, - "interval": 5 - } - ``` -{% endif %} +默认情况下，响应采用以下形式： + +``` +device_code=3584d83530557fdd1f46af8289938c8ef79f9dc5&expires_in=900&interval=5&user_code=WDJB-MJHT&verification_uri=https%3A%2F%{% data variables.product.product_url %}%2Flogin%2Fdevice +``` + +{% data reusables.apps.oauth-auth-vary-response %} + +```json +Accept: application/json +{ + "device_code": "3584d83530557fdd1f46af8289938c8ef79f9dc5", + "user_code": "WDJB-MJHT", + "verification_uri": "{% data variables.product.oauth_host_code %}/login/device", + "expires_in": 900, + "interval": 5 +} +``` + +```xml +Accept: application/xml + + 3584d83530557fdd1f46af8289938c8ef79f9dc5 + WDJB-MJHT + {% data variables.product.oauth_host_code %}/login/device + 900 + 5 + +``` #### 响应参数 @@ -196,14 +214,32 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre #### 响应 +默认情况下，响应采用以下形式： + +``` +access_token={% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}&token_type=bearer&scope=repo%2Cgist +``` + +{% data reusables.apps.oauth-auth-vary-response %} + ```json +Accept: application/json { "access_token": "{% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %}", "token_type": "bearer", - "scope": "user" + "scope": "repo,gist" } ``` +```xml +Accept: application/xml + + {% ifversion fpt or ghes > 3.1 or ghae-next %}gho_16C7e42F292c6912E7710c838347Ae178B4a{% else %}e72e16c7e42f292c6912e7710c838347ae178b4a{% endif %} + bearer + gist,repo + +``` + ### 设备流程的速率限制 当用户在浏览器上提交验证码时，每个应用程序在一个小时内的提交速率限制为 50 个。 diff --git a/translations/zh-CN/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md b/translations/zh-CN/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md index 4589c6713f..82435d417a 100644 --- a/translations/zh-CN/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md +++ b/translations/zh-CN/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md @@ -25,7 +25,7 @@ shortTitle: 管理应用可见性 ## 私有安装流程 -私有安装流程只允许 GitHub 应用程序的所有者安装它。 有关 GitHub 应用程序的有限信息仍将存在于公共页面，但 **Install（安装）**按钮仅对组织管理员或用户帐户（如果 GitHub 应用程序由个人帐户所有）可用。 私有{% ifversion ghes < 3.2 or ghae %} 或内部{% endif %} GitHub 应用程序只能安装在所有者的用户或组织帐户上。 +私有安装流程只允许 GitHub 应用程序的所有者安装它。 有关 GitHub 应用程序的有限信息仍将存在于公共页面，但 **Install（安装）**按钮仅对组织管理员或用户帐户（如果 GitHub 应用程序由个人帐户所有）可用。 {% ifversion fpt or ghes > 3.1 or ghae-next %}Private {% else %}Private (also known as internal){% endif %} GitHub Apps can only be installed on the user or organization account of the owner. ## 更改 GitHub 应用程序的安装权限 @@ -36,5 +36,5 @@ shortTitle: 管理应用可见性 {% data reusables.user-settings.github_apps %} 3. 选择要更改其安装权限选项的 GitHub 应用程序。 ![应用程序选择](/assets/images/github-apps/github_apps_select-app.png) {% data reusables.user-settings.github_apps_advanced %} -5. 根据 GitHub 应用程序的安装选项，单击 **Make public（设为公共）**或 **Make {% ifversion fpt or ghes > 3.1 %}private（设为私有）{% else %}internal（设为内部）{% endif %}**。 ![更改 GitHub 应用程序安装选项的按钮](/assets/images/github-apps/github_apps_make_public.png) -6. 根据 GitHub 应用程序的安装选项，单击 **Yes, make this GitHub App public（是，将此 GitHub 应用程序设为公共）**或 **Yes, make this GitHub App {% ifversion fpt or ghes > 3.1 %}private（是，将此 GitHub 应用程序设为私有）{% else %}internal（是，将此 GitHub 应用程序设为内部）{% endif %}**。 ![确认更改安装选项的按钮](/assets/images/github-apps/github_apps_confirm_installation_option.png) +5. 根据 GitHub 应用程序的安装选项，单击 **Make public（设为公共）**或 **Make {% ifversion fpt or ghes > 3.1 or ghae-next %}private（设为私有）{% else %}internal（设为内部）{% endif %}**。 ![更改 GitHub 应用程序安装选项的按钮](/assets/images/github-apps/github_apps_make_public.png) +6. Depending on the installation option of your GitHub App, click either **Yes, make this GitHub App public** or **Yes, make this GitHub App {% ifversion fpt or ghes < 3.2 %}internal{% else %}private{% endif %}**. ![确认更改安装选项的按钮](/assets/images/github-apps/github_apps_confirm_installation_option.png) diff --git a/translations/zh-CN/content/developers/github-marketplace/github-marketplace-overview/about-marketplace-badges.md b/translations/zh-CN/content/developers/github-marketplace/github-marketplace-overview/about-marketplace-badges.md index bd66e0521a..754eeebaa3 100644 --- a/translations/zh-CN/content/developers/github-marketplace/github-marketplace-overview/about-marketplace-badges.md +++ b/translations/zh-CN/content/developers/github-marketplace/github-marketplace-overview/about-marketplace-badges.md @@ -30,7 +30,7 @@ versions: 有关在 {% data variables.product.prodname_marketplace %} 中上架应用程序的要求，请参阅“[在 {% data variables.product.prodname_marketplace %} 中上架应用程序的要求](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)”。 -有关如何查找要使用的应用程序，请参阅“[搜索 {% data variables.product.prodname_marketplace %}](/github/searching-for-information-on-github/searching-github-marketplace)”。 +有关如何查找要使用的应用程序，请参阅“[搜索 {% data variables.product.prodname_marketplace %}](/search-github/searching-on-github/searching-github-marketplace)”。 ## 对于 GitHub Actions diff --git a/translations/zh-CN/content/developers/overview/index.md b/translations/zh-CN/content/developers/overview/index.md index b9f4ad4521..e02c1208b1 100644 --- a/translations/zh-CN/content/developers/overview/index.md +++ b/translations/zh-CN/content/developers/overview/index.md @@ -8,7 +8,6 @@ versions: children: - /about-githubs-apis - /managing-deploy-keys - - /viewing-deployment-history - /using-ssh-agent-forwarding - /secret-scanning-partner-program - /replacing-github-services diff --git a/translations/zh-CN/content/developers/overview/replacing-github-services.md b/translations/zh-CN/content/developers/overview/replacing-github-services.md index 14d1e01da9..aa2ea5612d 100644 --- a/translations/zh-CN/content/developers/overview/replacing-github-services.md +++ b/translations/zh-CN/content/developers/overview/replacing-github-services.md @@ -70,4 +70,4 @@ GitHub 服务与 web 挂钩之间的主要区别： 作为高度概述，迁移过程通常涉及： - 确定产品使用 GitHub 服务的方式和位置。 - 确定需要配置的相应 web 挂钩事件，以便移动到普通 web 挂钩。 - - Implementing the design using either [{% data variables.product.prodname_oauth_apps %}](/apps/building-oauth-apps/) or [{% data variables.product.prodname_github_apps %}. {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/) are preferred. To learn more about why {% data variables.product.prodname_github_apps %} are preferred, see "[Reasons for switching to {% data variables.product.prodname_github_apps %}](/apps/migrating-oauth-apps-to-github-apps/#reasons-for-switching-to-github-apps)." + - 使用 [{% data variables.product.prodname_oauth_apps %}](/apps/building-oauth-apps/) 或 [{% data variables.product.prodname_github_apps %} 实现设计。 {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/) 优先。 要了解为什么优先使用 {% data variables.product.prodname_github_apps %}，请参阅“[切换到 {% data variables.product.prodname_github_apps %} 的原因](/apps/migrating-oauth-apps-to-github-apps/#reasons-for-switching-to-github-apps)”。 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 aaa1056b67..a4919e19d5 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 @@ -190,7 +190,7 @@ Activity related to a branch protection rule. For more information, see "[About {% 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 %}`github` {% elsif ghes > 3.0 %}`github-enterprise` {% else %}空 {% endif %}。 +`sender` | `object` | 如果 `action` 是 `reopened_by_user` 或 `closed_by_user`，则 `sender` 对象将是触发事件的用户。 The `sender` object is {% ifversion fpt %}`github`{% elsif ghes > 3.0 or ghae-next %}`github-enterprise`{% else %}empty{% endif %} for all other actions. ### Web 挂钩有效负载示例 @@ -1032,24 +1032,29 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 ### Web 挂钩有效负载对象 -| 键 | 类型 | 描述 | -| -------------------------- | ----- | ---------------------------------------------------------------------------------------------------------------------- | -| `ref` | `字符串` | 被推送的完整 [`git ref`](/rest/reference/git#refs)。 例如：`refs/heads/main`。 | -| `before` | `字符串` | 推送之前在 `ref` 上最近提交的 SHA。 | -| `after` | `字符串` | 推送之后在 `ref` 上最近提交的 SHA。 | -| `commits` | `数组` | 描述所推送提交的提交对象数组。 （该数组最多包含 20 个提交。 如有必要，可使用[提交 API](/rest/reference/repos#commits) 获取更多提交。 此限制仅适用于时间表事件，而不适用于 web 挂钩递送。） | -| `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` | `对象` | 推送提交的用户。 | +| 键 | 类型 | 描述 | +| -------------------------- | ----- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `ref` | `字符串` | 被推送的完整 [`git ref`](/rest/reference/git#refs)。 Example: `refs/heads/main` or `refs/tags/v3.14.1`. | +| `before` | `字符串` | 推送之前在 `ref` 上最近提交的 SHA。 | +| `after` | `字符串` | 推送之后在 `ref` 上最近提交的 SHA。 | +| `created` | `布尔值` | Whether this push created the `ref`. | +| `deleted` | `布尔值` | Whether this push deleted the `ref`. | +| `forced` | `布尔值` | Whether this push was a force push of the `ref`. | +| `head_commit` | `对象` | 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` | `字符串` | 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` | `数组` | 描述所推送提交的提交对象数组。 (Pushed commits are all commits that are included in the `compare` between the `before` commit and the `after` commit.) The array includes a maximum of 20 commits. 如有必要，可使用[提交 API](/rest/reference/repos#commits) 获取更多提交。 This limit is applied to timeline events only and isn't applied to webhook deliveries. | +| `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` | `对象` | 推送提交的用户。 | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} diff --git a/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md b/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md index 9cae593be5..9f81f5c13f 100644 --- a/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md +++ b/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md @@ -53,7 +53,7 @@ If a repository administrator or project maintainer enables {% data variables.pr ## 延伸阅读 - “[关于 {% data variables.product.prodname_dotcom %} 上的书写和格式化](/github/writing-on-github/about-writing-and-formatting-on-github)” -- "[搜索讨论](/github/searching-for-information-on-github/searching-discussions)" +- "[搜索讨论](/search-github/searching-on-github/searching-discussions)" - "[关于通知](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" - "[调解评论和对话](/communities/moderating-comments-and-conversations)" - “[在 {% data variables.product.prodname_dotcom %} 上维护您的安全](/communities/maintaining-your-safety-on-github)” diff --git a/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md b/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md index 52e5247417..2f6e7fd270 100644 --- a/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md +++ b/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md @@ -2,7 +2,7 @@ title: 使用讨论与维护者协作 shortTitle: 与维护者协作 intro: '您可以通过在讨论中与项目的维护者沟通，为 {% data variables.product.product_name %} 项目的目标、计划、运行状况和社区做出贡献。' -permissions: People with read permissions to a repository can start and participate in discussions in the repository. +permissions: 'People with read access to a repository can start and participate in discussions in the repository. {% data reusables.enterprise-accounts.emu-permission-interact %}' versions: fpt: '*' --- @@ -32,7 +32,7 @@ To collaborate with maintainers in discussions, a repository administrator or pr ## 过滤讨论列表 -您可以在仓库中搜索讨论并过滤讨论列表。 更多信息请参阅“[搜索讨论](/github/searching-for-information-on-github/searching-discussions)”。 +您可以在仓库中搜索讨论并过滤讨论列表。 更多信息请参阅“[搜索讨论](/search-github/searching-on-github/searching-discussions)”。 {% data reusables.repositories.navigate-to-repo %} {% data reusables.discussions.discussions-tab %} diff --git a/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md b/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md index 8e812a4801..cfe0920e0b 100644 --- a/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md +++ b/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md @@ -1,7 +1,7 @@ --- title: 参与讨论 intro: '您可以在仓库的论坛中与社区和维护者交流 {% data variables.product.product_name %} 上的项目。' -permissions: People with read permissions to a repository can participate in discussions in the repository. +permissions: 'People with read access to a repository can participate in discussions in the repository. {% data reusables.enterprise-accounts.emu-permission-interact %}' versions: fpt: '*' shortTitle: 参与讨论 diff --git a/translations/zh-CN/content/discussions/guides/finding-discussions-across-multiple-repositories.md b/translations/zh-CN/content/discussions/guides/finding-discussions-across-multiple-repositories.md index 3ea0f0a958..c075fc96c9 100644 --- a/translations/zh-CN/content/discussions/guides/finding-discussions-across-multiple-repositories.md +++ b/translations/zh-CN/content/discussions/guides/finding-discussions-across-multiple-repositories.md @@ -15,6 +15,6 @@ shortTitle: 查找讨论 ## 延伸阅读 -- "[搜索讨论](/github/searching-for-information-on-github/searching-discussions)" +- "[搜索讨论](/search-github/searching-on-github/searching-discussions)" - "[关于讨论](/discussions/collaborating-with-your-community-using-discussions/about-discussions)" - "[管理社区的讨论](/discussions/managing-discussions-for-your-community)" diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md index 4ccfebffd8..cdb98b404a 100644 --- a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md @@ -8,12 +8,6 @@ redirect_from: shortTitle: 入门作业 --- -{% note %} - -**注意：**Git 和 {% data variables.product.company_short %} 起始作业目前处于测试阶段，可能会更改。 - -{% endnote %} - Git 和 {% data variables.product.company_short %} 起始作业是一个预制课程，概括了 Git 和 {% data variables.product.company_short %} 的基础知识，并将学生与资源联系起来以了解更多关于具体主题的信息。 ## 基本要求 diff --git a/translations/zh-CN/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md b/translations/zh-CN/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md index 5dd2646804..9e8608cb7c 100644 --- a/translations/zh-CN/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md +++ b/translations/zh-CN/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md @@ -1,6 +1,7 @@ --- title: 寻找在 GitHub 上参与开源项目的方法 intro: '您可以找到在 {% data variables.product.product_name %} 上参加与您相关的开源项目的方法。' +permissions: '{% data reusables.enterprise-accounts.emu-permission-interact %}' redirect_from: - /articles/where-can-i-find-open-source-projects-to-work-on/ - /articles/finding-interesting-projects-on-github/ @@ -19,7 +20,7 @@ shortTitle: 为开源做贡献 ## 发现相关项目 -如果有您感兴趣的特定主题，请访问 `github.com/topics/`。 例如，如果您对机器学习感兴趣，可以通过访问 https://github.com/topics/machine-learning 找到相关的项目和合适的第一个议题。 您可以通过访问[主题](https://github.com/topics)来浏览热门主题。 您还可以搜索与您感兴趣的主题相匹配的仓库。 更多信息请参阅“[搜索仓库](/articles/searching-for-repositories#search-by-topic)”。 +如果有您感兴趣的特定主题，请访问 `github.com/topics/`。 例如，如果您对机器学习感兴趣，可以通过访问 https://github.com/topics/machine-learning 找到相关的项目和合适的第一个议题。 您可以通过访问[主题](https://github.com/topics)来浏览热门主题。 您还可以搜索与您感兴趣的主题相匹配的仓库。 更多信息请参阅“[搜索仓库](/search-github/searching-on-github/searching-for-repositories#search-by-topic)”。 如果您一直活跃在 {% data variables.product.product_name %} 上，可以根据您过去的参与、标星以及在 [Explore](https://github.com/explore) 中的其他活动，为您的项目找到个性化的建议和合适的第一个议题。 您还可以注册 Explore 通讯以根据您的兴趣接收相关电子邮件，了解参与 {% data variables.product.product_name %} 的机会。 要注册，请参阅 [Explore 电子邮件通讯](https://github.com/explore/subscribe)。 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 919860f149..a9e911fd4e 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 @@ -1,6 +1,7 @@ --- title: 关注他人 intro: '您可以在 {% data variables.product.product_name %} 上关注他人，以接收有关其活动的通知{% ifversion fpt %} 和发现其社区中的项目{% endif %}。' +permissions: '{% data reusables.enterprise-accounts.emu-permission-follow %}' redirect_from: - /articles/following-people - /github/getting-started-with-github/following-people 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 2460733e1f..90060b4d72 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 @@ -61,6 +61,7 @@ shortTitle: 关联文本编辑器 ## 使用 Atom 作为编辑器 1. 安装 [Atom](https://atom.io/)。 更多信息请参阅 Atom 文档中的“[安装 Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)”。 +{% data reusables.command_line.open_the_multi_os_terminal %} 3. 输入此命令： ```shell $ git config --global core.editor "atom --wait" diff --git a/translations/zh-CN/content/get-started/learning-about-github/access-permissions-on-github.md b/translations/zh-CN/content/get-started/learning-about-github/access-permissions-on-github.md index 06173eff4d..b6787b8cc8 100644 --- a/translations/zh-CN/content/get-started/learning-about-github/access-permissions-on-github.md +++ b/translations/zh-CN/content/get-started/learning-about-github/access-permissions-on-github.md @@ -36,6 +36,8 @@ shortTitle: 访问权限 *企业所有者*对企业帐户拥有最终权力，可在企业帐户中执行任何操作。 *帐单管理员*可以管理企业帐户的帐单设置。 企业帐户拥有的组织的成员和外部协作者自动成为企业帐户的成员，但他们对企业帐户本身或其设置没有访问权限。 更多信息请参阅“[企业中的角色](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise)”。 +If an enterprise uses {% data variables.product.prodname_emus %}, members are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and are fully managed by the identity provider. The {% data variables.product.prodname_managed_users %} have read-only access to repositories that are not a part of their enterprise and cannot interact with users that are not also members of the enterprise. Within the organizations owned by the enterprise, the {% data variables.product.prodname_managed_users %} can be granted the same granular access levels available for regular organizations. For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." + {% data reusables.gated-features.enterprise-accounts %} {% endif %} diff --git a/translations/zh-CN/content/get-started/learning-about-github/githubs-products.md b/translations/zh-CN/content/get-started/learning-about-github/githubs-products.md index 0da7686925..86f4082445 100644 --- a/translations/zh-CN/content/get-started/learning-about-github/githubs-products.md +++ b/translations/zh-CN/content/get-started/learning-about-github/githubs-products.md @@ -102,6 +102,7 @@ topics: - 50GB {% data variables.product.prodname_registry %} 存储空间 - {% data variables.product.prodname_pages %} 站点的访问控制。 更多信息请参阅“更改 {% data variables.product.prodname_pages %} 站点的可见性” - 99.9% 月持续运行时间的服务等级协议 +- The option to configure your enterprise for {% data variables.product.prodname_emus %}, so you can provision and manage members with your identity provider and restrict your member's contributions to just your enterprise. For more information, see "About {% data variables.product.prodname_emus %}." - 通过企业帐户集中管理多个 {% data variables.product.prodname_dotcom_the_website %} 组织的策略和帐单的选项。 更多信息请参阅“关于企业帐户”。 您可以设置试用版来评估 {% data variables.product.prodname_ghe_cloud %}。 更多信息请参阅“设置 {% data variables.product.prodname_ghe_cloud %} 的试用”。 diff --git a/translations/zh-CN/content/get-started/learning-about-github/types-of-github-accounts.md b/translations/zh-CN/content/get-started/learning-about-github/types-of-github-accounts.md index 0117f8fc4a..afb13c1805 100644 --- a/translations/zh-CN/content/get-started/learning-about-github/types-of-github-accounts.md +++ b/translations/zh-CN/content/get-started/learning-about-github/types-of-github-accounts.md @@ -64,6 +64,14 @@ topics: {% endif %} +{% ifversion fpt %} +### {% data variables.product.prodname_emus %} + +With {% data variables.product.prodname_emus %}, instead of using your personal account, members of an {% data variables.product.prodname_emu_enterprise %} are provisioned accounts using the enterprise's identity provider (IdP). {% data variables.product.prodname_managed_users_caps %} authenticate using their IdP instead of a {% data variables.product.prodname_dotcom_the_website %} username and password. + +{% data variables.product.prodname_managed_users_caps %} can only interact with users, repositories, and organizations that are part of their enterprise. {% data variables.product.prodname_managed_users_caps %} have read-only access to the rest of {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." +{% endif %} + ## 组织帐户 组织是共享帐户，供多个项目的人员同时协作之用。 所有者和管理员可通过复杂的安全和管理功能管理成员对组织数据和项目的访问。 diff --git a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md index 82ce675d76..12af37dd20 100644 --- a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md +++ b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md @@ -18,16 +18,19 @@ This guide will walk you through setting up, configuring and managing your {% da The main difference between the products is that {% data variables.product.prodname_ghe_cloud %} is hosted by {% data variables.product.prodname_dotcom %}, while {% data variables.product.prodname_ghe_server %} is self-hosted. -Within the {% data variables.product.prodname_ghe_cloud %} product, there are two different types of account that you can use: +With {% data variables.product.prodname_ghe_cloud %}, you have the option of using {% data variables.product.prodname_emus %}. {% data reusables.enterprise-accounts.emu-short-summary %} + +If you choose to let your members create and manage their own user accounts instead, there are two types of accounts you can use with {% data variables.product.prodname_ghe_cloud %}: - A single organization account - An enterprise account that contains multiple organizations -In either scenario, your users will use their own self-created user account and you'll invite them to join. ### 1. Understanding the differences between an organization account and enterprise account Both organization and enterprise accounts are available with {% data variables.product.prodname_ghe_cloud %}. An organization is a shared account where groups of people can collaborate across many projects at once, and owners and administrators can manage access to data and projects. An enterprise account enables collaboration between multiple organizations, and allows owners to centrally manage policy, billing and security for these organizations. For more information on the differences, see "[Organizations and enterprise accounts](/organizations/collaborating-with-groups-in-organizations/about-organizations#organizations-and-enterprise-accounts)." + + If you choose an enterprise account, keep in mind that some policies can be set only at an organization level, while others can be enforced for all organizations in an enterprise. Once you choose the account type you would like, you can proceed to setting up your account. In each of the sections in this guide, proceed to either the single organization or enterprise account section based on your account type. @@ -86,6 +89,11 @@ You can set permissions and member roles, create and manage teams, and give peop ### Managing members of an enterprise account Managing members of an enterprise is separate from managing members or teams in an organization. It is important to note that enterprise owners or administrators cannot access organization-level settings or manage members for organizations in their enterprise unless they are made an organization owner. For more information, see the above section, "[Managing members and teams in your organization](#managing-members-and-teams-in-your-organization)." + +If your enterprise uses {% data variables.product.prodname_emus %}, your members are fully managed through your identity provider. Adding members, making changes to their membership, and assigning roles is all managed using your IdP. For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." + +If your enterprise does not use {% data variables.product.prodname_emus %}, follow the steps below. + #### 1. Assigning roles in an enterprise By default, everyone in an enterprise is a member of the enterprise. There are also administrative roles, including enterprise owner and billing manager, that have different levels of access to enterprise settings and data. 更多信息请参阅“[企业中的角色](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)”。 #### 2. 邀请人员管理企业 @@ -97,6 +105,10 @@ To audit access to enterprise-owned resources or user license usage, you can vie ## Part 4: Managing security with {% data variables.product.prodname_ghe_cloud %} +* [Managing security for a single organization](#managing-security-for-a-single-organization) +* [Managing security for an {% data variables.product.prodname_emu_enterprise %}](#managing-security-for-an-enterprise-with-managed-users) +* [Managing security for an enterprise account without {% data variables.product.prodname_managed_users %}](#managing-security-for-an-enterprise-account-without-managed-users) + ### Managing security for a single organization You can help keep your organization secure by requiring two-factor authentication, configuring security features, reviewing your organization's audit log and integrations, and enabling SAML single sign-on and team synchronization. #### 1. Requiring two-factor authentication @@ -113,8 +125,28 @@ Organization owners can choose to disable, enable but not enforce, or enable and #### 5. 管理组织的团队同步 Organization owners can enable team synchronization between your identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organization owners and team maintainers to connect teams in your organization with IdP groups. 更多信息请参阅“[管理组织的团队同步](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)”。 -### Managing security for an enterprise account with multiple organizations +### Managing security for an {% data variables.product.prodname_emu_enterprise %} + +With {% data variables.product.prodname_emus %}, access and identity is managed centrally through your identity provider. Two-factor authentication and other login requirements should be enabled and enforced on your IdP. + +#### 1. Enabling and SAML single sign-on and provisioning in your {% data variables.product.prodname_emu_enterprise %} + +In an {% data variables.product.prodname_emu_enterprise %}, all members are provisioned and managed by your identity provider. You must enable SAML SSO and SCIM provisioning before you can start using your enterprise. For more information on configuring SAML SSO and provisioning for an {% data variables.product.prodname_emu_enterprise %}, see "[Configuring SAML single sign-on for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." + +#### 2. Managing teams in your {% data variables.product.prodname_emu_enterprise %} with your identity provider + +You can connect teams in your organizations to security groups in your identity provider, managing membership of your teams and access to repositories through your IdP. For more information, see "[Managing team memberships with identity provider groups](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)." + +#### 3. Managing allowed IP addresses for organizations in your {% data variables.product.prodname_emu_enterprise %} + +You can configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your {% data variables.product.prodname_emu_enterprise %}. 更多信息请参阅“[在企业帐户中实施安全设置](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-security-settings-in-your-enterprise-account#managing-allowed-ip-addresses-for-organizations-in-your-enterprise-account)”。 + +#### 4. Enforcing policies for Advanced Security features in your {% data variables.product.prodname_emu_enterprise %} +{% data reusables.getting-started.enterprise-advanced-security %} + +### Managing security for an enterprise account without {% data variables.product.prodname_managed_users %} To manage security for your enterprise, you can require two-factor authentication, manage allowed IP addresses, enable SAML single sign-on and team synchronization at an enterprise level, and sign up for and enforce GitHub Advanced Security features. + #### 1. Requiring two-factor authentication and managing allowed IP addresses for organizations in your enterprise account 企业所有者可以要求企业帐户拥有的所有组织中的组织成员、帐单管理员和外部协作者使用双重身份验证来保护其个人帐户。 Before doing so, we recommend notifying all who have access to organizations in your enterprise. You can also configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account. @@ -126,7 +158,7 @@ You can centrally manage access to your enterprise's resources, organization mem You can enable and manage team sychronization between an identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organizations owned by your enterprise account to manage team membership with IdP groups. 更多信息请参阅“[管理企业帐户中组织的团队同步](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/managing-team-synchronization-for-organizations-in-your-enterprise-account)”。 #### 4. Enforcing policies for Advanced Security features in your enterprise account -If you have a GitHub Advanced Security license for your enterprise account, you can enforce policies to manage {% data variables.product.prodname_dotcom %} Advanced Security features for organizations owned by an enterprise account. For more information, see "[Enforcing policies for Advanced Security in your enterprise account](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-policies-for-advanced-security-in-your-enterprise-account)." +{% data reusables.getting-started.enterprise-advanced-security %} ## Part 5: Managing organization and enterprise level policies and settings diff --git a/translations/zh-CN/content/get-started/quickstart/be-social.md b/translations/zh-CN/content/get-started/quickstart/be-social.md index 2a034cd2a0..5521773491 100644 --- a/translations/zh-CN/content/get-started/quickstart/be-social.md +++ b/translations/zh-CN/content/get-started/quickstart/be-social.md @@ -6,6 +6,7 @@ redirect_from: - /github/getting-started-with-github/be-social - /github/getting-started-with-github/quickstart/be-social intro: '您可以在 {% data variables.product.prodname_dotcom %} 上与人员、仓库及组织进行互动。 从您的个人仪表板查看其他人正在做什么，在跟谁联系。' +permissions: '{% data reusables.enterprise-accounts.emu-permission-interact %}' versions: fpt: '*' ghes: '*' diff --git a/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md b/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md index cbc9d58bfe..60d9fc4fed 100644 --- a/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md +++ b/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md @@ -7,6 +7,7 @@ redirect_from: - /github/getting-started-with-github/fork-a-repo - /github/getting-started-with-github/quickstart/fork-a-repo intro: 复刻是仓库的副本。 通过复刻仓库，您可以自由地尝试更改而不会影响原始项目。 +permissions: '{% data reusables.enterprise-accounts.emu-permission-fork %}' versions: fpt: '*' ghes: '*' diff --git a/translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md b/translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md index e5f70424ae..c15fd6c616 100644 --- a/translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md +++ b/translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md @@ -18,7 +18,7 @@ shortTitle: Enterprise Server 试用版 您可以申请 45 天试用版来试用 {% data variables.product.prodname_ghe_server %}。 您的试用版将作为虚拟设备安装，带有内部或云部署选项。 有关支持的可视化平台列表，请参阅“[设置 GitHub Enterprise Server 实例](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance)”。 -{% ifversion ghes %}{% data variables.product.prodname_dependabot %}{% else %}安全{% endif %}警报和 {% data variables.product.prodname_github_connect %} 目前在 {% data variables.product.prodname_ghe_server %} 试用版中不可用。 要获取这些功能的演示，请联系 {% data variables.contact.contact_enterprise_sales %}。 有关这些功能的更多信息，请参阅“[关于对有漏洞的依赖项发出警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)”和“[将 {% data variables.product.prodname_ghe_server %} 连接到 {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud)”。 +{% ifversion ghes %}{% data variables.product.prodname_dependabot %}{% else %}安全{% endif %}警报和 {% data variables.product.prodname_github_connect %} 目前在 {% data variables.product.prodname_ghe_server %} 试用版中不可用。 要获取这些功能的演示，请联系 {% data variables.contact.contact_enterprise_sales %}。 For more information about these features, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" and "[Connecting your enterprise account to {% data variables.product.prodname_dotcom_the_website %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." 试用版也可用于 {% data variables.product.prodname_ghe_cloud %}。 更多信息请参阅“[设置 {% data variables.product.prodname_ghe_cloud %} 的试用](/articles/setting-up-a-trial-of-github-enterprise-cloud)”。 diff --git a/translations/zh-CN/content/get-started/using-git/dealing-with-special-characters-in-branch-and-tag-names.md b/translations/zh-CN/content/get-started/using-git/dealing-with-special-characters-in-branch-and-tag-names.md new file mode 100644 index 0000000000..e8c3daae8b --- /dev/null +++ b/translations/zh-CN/content/get-started/using-git/dealing-with-special-characters-in-branch-and-tag-names.md @@ -0,0 +1,48 @@ +--- +title: Dealing with special characters in branch and tag names +intro: 'Git is very permissive about what characters are allowed in branch and tag names. When using Git from a command-line shell, you may need to escape or quote special characters.' +versions: + fpt: '*' + ghes: '*' + ghae: '*' +shortTitle: Special characters in names +--- + +## About branch and tag names + +Most repositories use simple branch names, such as `main` or `update-icons`. Tag names also usually follow a basic format, such as a version number like `v1.2.3`. Both branch names and tag names may also use the path separator (`/`) for structure, for example `area/item` or `level-1/level-2/level-3`. Other than some exceptions — such as not starting or ending a name with a slash, or having consecutive slashes in the name — Git has very few restrictions on what characters may be used in branch and tag names. For more information, see "[git-check-ref-format](https://git-scm.com/docs/git-check-ref-format)" in the Git documentation. + +## Why you need to escape special characters + +When using a CLI, you might have situations where a branch or tag name contains special characters that have a special meaning for your shell environment. To use these characters safely in a Git command, they must be quoted or escaped, otherwise the command may have unintended effects. + +For example, the `$` character is used by many shells to refer to a variable. Most shells would interpret a valid branch name like `hello-$USER` as equivalent to the word "hello", followed by a hyphen, followed by the current value of the `USER` variable, rather than the literal string `hello-$USER`. If a branch name includes the `$` character, then the shell must be stopped from expanding it as a variable reference. Similarly, if a branch name contains a semi-colon (`;`), most shells interpret it as a command separator, so it needs to be quoted or escaped. + +## How to escape special characters in branch and tag names + +Most branch and tag names with special characters can be handled by including the name in single quotes, for example `'hello-$USER'`. + +* In the [Bash](https://www.gnu.org/software/bash/) shell, enclosing a string of characters in single quotes preserves the literal value of the characters within the single quotes. +* [Zsh](https://www.zsh.org/) behaves similar to Bash, however this behavior is configurable using the `RC_QUOTES` option. +* [PowerShell](https://microsoft.com/powershell) also treats characters literally when inside single quotes. + +For these shells, the main exception is when the branch or tag name itself contains a single quote. In this case, you should consult the official documentation for your shell: + +* [Bash documentation](https://www.gnu.org/software/bash/manual/) +* [Zsh documentation](https://zsh.sourceforge.io/Doc/) +* [Fish documentation](https://fishshell.com/docs/current/) +* [PowerShell documentation](https://docs.microsoft.com/en-gb/powershell/) + +## Naming branches and tags + +If possible, create branch and tag names that don't contain special characters, as these would need to be escaped. A safe default set of characters to use for branch names and tag names is: + +* The English alphabet (`a` to `z` and `A` to `Z`) +* Numbers (`0` to `9`) +* A limited set of punctuation characters: + * period (`.`) + * hyphen (`-`) + * underscore (`_`) + * forward slash (`/`) + +To avoid confusion, you should start branch names with a letter. diff --git a/translations/zh-CN/content/get-started/using-git/index.md b/translations/zh-CN/content/get-started/using-git/index.md index 77f571b80c..aa56554ca9 100644 --- a/translations/zh-CN/content/get-started/using-git/index.md +++ b/translations/zh-CN/content/get-started/using-git/index.md @@ -23,5 +23,6 @@ children: - /about-git-rebase - /using-git-rebase-on-the-command-line - /resolving-merge-conflicts-after-a-git-rebase + - /dealing-with-special-characters-in-branch-and-tag-names --- 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 ee4e3bddbd..2c196513c8 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 @@ -24,7 +24,7 @@ versions: | 键盘快捷键 | 描述 | | --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| s 或 / | 聚焦于搜索栏。 更多信息请参阅“[关于在 {% data variables.product.company_short %} 上搜索](/articles/about-searching-on-github)”。 | +| 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 %}"[关于通知](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}“[关于通知](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}”。 | | esc | 当聚焦于用户、议题或拉取请求悬停卡时，关闭悬停卡并重新聚焦于悬停卡所在的元素 | diff --git a/translations/zh-CN/content/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md b/translations/zh-CN/content/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md index 506b2fb9f9..e62915749f 100644 --- a/translations/zh-CN/content/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md +++ b/translations/zh-CN/content/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md @@ -41,6 +41,12 @@ _Checks_ are different from _statuses_ in that they provide line annotations, mo ![拉取请求中的状态检查](/assets/images/help/pull_requests/checks.png) +{% note %} + +**Note:** The **Checks** tab only gets populated for pull requests if you set up _checks_, not _statuses_, for the repository. + +{% endnote %} + 当提交中的特定行造成检查失败时，您会在拉取请求的 **Files（文件）**选项卡中相关代码旁边看到有关失败、警告或通知的详细信息。 ![状态检查详细信息](/assets/images/help/pull_requests/checks-detailed.png) diff --git a/translations/zh-CN/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork.md b/translations/zh-CN/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork.md index efbfd2d293..602c3e8e90 100644 --- a/translations/zh-CN/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork.md +++ b/translations/zh-CN/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork.md @@ -5,7 +5,7 @@ redirect_from: - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork - /articles/creating-a-pull-request-from-a-fork - /github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork -permissions: Anyone with write access to a repository can create a pull request from a user-owned fork. +permissions: 'Anyone with write access to a repository can create a pull request from a user-owned fork. {% data reusables.enterprise-accounts.emu-permission-propose %}' versions: fpt: '*' ghes: '*' diff --git a/translations/zh-CN/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md b/translations/zh-CN/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md index 295b446d53..b3e97504fc 100644 --- a/translations/zh-CN/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md +++ b/translations/zh-CN/content/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md @@ -1,6 +1,7 @@ --- title: 创建拉取请求 intro: 创建拉取请求以提议和协作处理对仓库的更改。 这些更改在*分支*中提议，以确保默认分支只包含已完成和已批准的工作。 +permissions: 'Anyone with read access to a repository can create a pull request. {% data reusables.enterprise-accounts.emu-permission-propose %}' redirect_from: - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request - /articles/creating-a-pull-request @@ -13,7 +14,7 @@ topics: - Pull requests --- -对仓库具有读取权限的任何人都可以创建拉取请求，但要创建分支，必须具有写入权限。 如果要为拉取请求创建新分支，又没有仓库的写入权限，可以先对仓库复刻。 更多信息请参阅“[从复刻创建拉取请求](/articles/creating-a-pull-request-from-a-fork)”和“[关于复刻](/articles/about-forks)”。 +If you want to create a new branch for your pull request and do not have write permissions to the repository, you can fork the repository first. 更多信息请参阅“[从复刻创建拉取请求](/articles/creating-a-pull-request-from-a-fork)”和“[关于复刻](/articles/about-forks)”。 您可以在创建拉取请求时指定要将更改合并到哪个分支。 拉取请求只能在不同的两个分支之间打开。 diff --git a/translations/zh-CN/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/translations/zh-CN/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md index 27cab1a304..55d5de5d74 100644 --- a/translations/zh-CN/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md +++ b/translations/zh-CN/content/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md @@ -1,10 +1,10 @@ --- title: 审查拉取请求中的依赖项更改 intro: 如果拉取请求包含对依赖项的更改，您可以查看已更改内容摘要以及任何依赖项中是否存在已知漏洞。 +product: '{% data reusables.gated-features.dependency-review %}' versions: fpt: '*' ghes: '>= 3.2' - product: '{% data reusables.gated-features.dependency-review %}' type: how_to topics: - Pull requests @@ -38,19 +38,19 @@ shortTitle: 查看依赖项更改 1. 如果拉取请求包含许多文件，请使用 **File filter（文件过滤器）**下拉菜单折叠所有不记录依赖项的文件。 这将有助于您将审查的重点放在依赖项更改上。 - ![文件过滤器菜单](/assets/images/help/pull_requests/file-filter-menu-json.png) + ![文件过滤器菜单](/assets/images/help/pull_requests/file-filter-menu-json.png) The dependency review provides a clearer view of what has changed in large lock files, where the source diff is not rendered by default. + + {% note %} + + **Note:** Dependency review rich diffs are not available for committed static JavaScript files like `jquery.js`. + + {% endnote %} 1. 在清单或锁定文件标头的右侧，单击 **{% octicon "file" aria-label="The rich diff icon" %}** 多差异按钮以显示依赖项审查。 ![多差异按钮](/assets/images/help/pull_requests/dependency-review-rich-diff.png) - {% note %} - - **注：**依赖项审查提供关于大型锁定文件中已更改内容的更清晰视图，源差异在默认情况下不会呈现。 - - {% endnote %} - -1. 检查依赖项审查中列出的依赖项。 +2. 检查依赖项审查中列出的依赖项。 ![依赖项审查中的漏洞警告](/assets/images/help/pull_requests/dependency-review-vulnerability.png) diff --git a/translations/zh-CN/content/github/collaborating-with-pull-requests/working-with-forks/about-forks.md b/translations/zh-CN/content/github/collaborating-with-pull-requests/working-with-forks/about-forks.md index fa7309cbe8..127dc9a013 100644 --- a/translations/zh-CN/content/github/collaborating-with-pull-requests/working-with-forks/about-forks.md +++ b/translations/zh-CN/content/github/collaborating-with-pull-requests/working-with-forks/about-forks.md @@ -20,6 +20,12 @@ topics: {% data reusables.repositories.you-can-fork %} +{% ifversion fpt %} + +If you're a member of a {% data variables.product.prodname_emu_enterprise %}, there are further restrictions on the repositories you can fork. {% data reusables.enterprise-accounts.emu-forks %} For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." + +{% endif %} + {% data reusables.repositories.desktop-fork %} 删除复刻不会删除原始上游仓库。 您可以对复刻执行所需的任何更改—添加协作者、重命名文件、生成 {% data variables.product.prodname_pages %}—不会影响原始仓库。{% ifversion fpt %} 复刻的仓库在删除后无法恢复。 更多信息请参阅“[恢复删除的仓库](/articles/restoring-a-deleted-repository)”。{% endif %} diff --git a/translations/zh-CN/content/github/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md b/translations/zh-CN/content/github/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md index 7f63b7ea9e..b9eff1eda9 100644 --- a/translations/zh-CN/content/github/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md +++ b/translations/zh-CN/content/github/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md @@ -52,4 +52,4 @@ shortTitle: 链接到错误的用户 ## 延伸阅读 -* "[搜索提交](/articles/searching-commits)" +* "[搜索提交](/search-github/searching-on-github/searching-commits)" diff --git a/translations/zh-CN/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views.md b/translations/zh-CN/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views.md index 128cea18b8..b7a31fb8aa 100644 --- a/translations/zh-CN/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views.md +++ b/translations/zh-CN/content/github/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views.md @@ -29,4 +29,4 @@ Git 有几种不同的方式来显示仓库的历史记录。 当 Git 显示单 ## 延伸阅读 - "[对提交签名](/articles/signing-commits)" -- "[搜索提交](/articles/searching-commits)" +- "[搜索提交](/search-github/searching-on-github/searching-commits)" 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 cc083cf752..abd6a29c2e 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 @@ -1,6 +1,6 @@ --- title: 关于 GitHub Copilot 遥测 -intro: '{% data variables.product.prodname_dotcom %} Copilot 收集并依赖超出其他 {% data variables.product.prodname_dotcom %} 产品和服务收集的额外遥测数据。' +intro: '{% data variables.product.prodname_copilot %} collects and relies on additional telemetry data beyond what other {% data variables.product.company_short %} products and services collect.' redirect_from: - /early-access/github/copilot/about-github-copilot-telemetry versions: @@ -8,36 +8,21 @@ versions: --- ## 哪些数据会被收集？ -{% data variables.product.prodname_dotcom %} Copilot 从用户的 Visual Studio Code 编辑器中收集与时间戳和元数据相关的活动。 此元数据由 [Visual Studio Code 扩展遥测包](https://www.npmjs.com/package/vscode-extension-telemetry)收集的扩展设置和标准元数据组成： -* Visual Studio Code 机器 ID（匿名标识符） -* Visual Studio Code 会话 ID（匿名标识符） -* Visual Studio Code 版本 -* [来自 IP 地址的地理位置](https://docs.microsoft.com/en-us/azure/azure-monitor/app/ip-collection?tabs=net)（国家、州/省和城市，但不是 IP 地址本身） -* 操作系统和版本 -* 扩展版本 -* VS 代码界面（网页或桌面） +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. -收集的活动包括在以下情况下触发的事件： +## How the data is used by {% data variables.product.company_short %} -* 发生错（它记录错误类型和相关背景；例如，如果它有认证错误，则会记录密钥过期日期） -* 访问我们的模型以询问代码建议（它记录编辑器的位置，如像光标和代码片段的位置）- 这包括用户采取行动请求代码建议的情况。 -* 收到或显示代码建议（它记录建议、后处理和元数据，例如模型确定性和延迟） -* 代码建议因确保 AI 安全的过滤而编辑 -* 用户对代码建议采取行动（例如接受或拒绝） -* 用户根据代码建议行事，然后它记录它们在代码中是否保持或如何保持 +{% data variables.product.company_short %} will use this data for: -## 如何使用数据 -此数据仅供 {% data variables.product.company_short %} 用于： - -* 直接改进产品，包括评估处理中的不同策略，并预测用户可能认为有用的建议 -* 直接评估产品，例如通过测量它对用户的积极影响 -* 改进基础代码生成模型，例如通过提供正面和负面示例（但始终不会将您的私有代码用作输入来为 {% data variables.product.prodname_dotcom %} Copilot 的其他用户建议代码） -* 引导密切相关的 {% data variables.product.prodname_dotcom %} 产品 -* 调查和发现可能滥用 {% data variables.product.prodname_dotcom %} Copilot 服务的情况 -* 与改进 {% data variables.product.prodname_dotcom %} Copilot 服务相关的其他目的 +- 直接改进产品，包括评估处理中的不同策略，并预测用户可能认为有用的建议 +- Evaluating the product, e.g. by measuring the positive impact it has on the user +- Improving the underlying code generation models, e.g. by providing positive and negative examples (but always so that your private code is not used as input to suggest code for other users of {% data variables.product.prodname_copilot %}) +- 引导密切相关的 {% data variables.product.company_short %} 产品 +- Investigating and detecting potential abuse of the {% data variables.product.prodname_copilot %} service +- Other purposes related to improving the {% data variables.product.prodname_copilot %} service, including sharing as described in the next section ## 如何共享数据 -遥测数据安全地存储在 {% data variables.product.prodname_dotcom %} 系统上，并进行了适当的加密。 -我们知道用户编辑操作和源代码片段是非常敏感的数据，访问受到严格控制。 数据访问仅限于 (1) {% data variables.product.company_short %} Copilot 团队或 {% data variables.product.company_short %} 平台健康团队中指定的 {% data variables.product.company_short %} 人员（员工和承包商），(2) 特选的在 {% data variables.product.company_short %} Copilot 团队工作或与之合作的 Microsoft 人员（员工和承包商），以及 (3) 特选的在 {% data variables.product.company_short %} Copilot 上工作的 OpenAI 员工。 +遥测数据安全地存储在 {% data variables.product.company_short %} 系统上，并进行了适当的加密。 We know user edit actions, source code snippets, and URLs of repositories and file paths are sensitive data. Consequently, access is strictly controlled. The data can only be accessed by (1) named {% data variables.product.company_short %} personnel (employees and contractors) working on the {% data variables.product.prodname_copilot %} team or on the {% data variables.product.company_short %} platform health team, (2) Microsoft personnel (employees and contractors) working on or with the Azure and/or {% data variables.product.prodname_copilot %} teams, and (3) employees of OpenAI who work on {% data variables.product.prodname_copilot %}. + diff --git a/translations/zh-CN/content/github/copilot/github-copilot-telemetry-terms.md b/translations/zh-CN/content/github/copilot/github-copilot-telemetry-terms.md new file mode 100644 index 0000000000..7ff00ef478 --- /dev/null +++ b/translations/zh-CN/content/github/copilot/github-copilot-telemetry-terms.md @@ -0,0 +1,16 @@ +--- +title: GitHub Copilot Telemetry Terms +intro: 'Acceptance of the additional telemetry described below is a condition to joining the wait list for the technical preview of {% data variables.product.prodname_copilot %} and using {% data variables.product.prodname_copilot %} during the technical preview.' +redirect_from: + - /early-access/github/copilot/telemetry-terms + - /github/copilot/telemetry-terms +versions: + fpt: '*' +--- + +## 附加遥测 + +If you use {% data variables.product.prodname_copilot %}, the {% data variables.product.prodname_copilot %} extension/plugin will collect usage information about events generated by interacting with the integrated development environment (IDE). These events include {% data variables.product.prodname_copilot %} performance, features used, and suggestions accepted, modified and accepted, or dismissed. This information may include personal data, including your User Personal Information, as defined in the [GitHub Privacy Statement](/github/site-policy/github-privacy-statement). + +This usage information is used by {% data variables.product.company_short %}, and shared with Microsoft and OpenAI, to develop and improve the extension/plugin and related products. OpenAI also uses this usage information to perform other services related to {% data variables.product.prodname_copilot %}. For example, when you edit files with the {% data variables.product.prodname_copilot %} extension/plugin enabled, file content snippets, suggestions, and any modifications to suggestions will be shared with {% data variables.product.company_short %}, Microsoft, and OpenAI, and used for diagnostic purposes to improve suggestions and related products. {% data variables.product.prodname_copilot %} relies on file content for context, both in the file you are editing and potentially other files open in the same IDE instance. When you are using {% data variables.product.prodname_copilot %}, it may also collect the URLs of repositories or file paths for relevant files. {% data variables.product.prodname_copilot %} does not use these URLs, file paths, or snippets collected in your telemetry as input to suggest code for other users of {% data variables.product.prodname_copilot %}. This information is treated as confidential information and accessed on a need-to-know basis. You are prohibited from collecting telemetry data about other users of {% data variables.product.prodname_copilot %} from the {% data variables.product.prodname_copilot %} extension/plugin. For more details about {% data variables.product.prodname_copilot %} telemetry, please see "[About {% data variables.product.prodname_copilot %} telemetry](/github/copilot/about-github-copilot-telemetry)." You may revoke your consent to the telemetry and personal data processing operations described in this paragraph by contacting GitHub and requesting removal from the technical preview. + diff --git a/translations/zh-CN/content/github/copilot/index.md b/translations/zh-CN/content/github/copilot/index.md index caee58a235..7c6a9a14ee 100644 --- a/translations/zh-CN/content/github/copilot/index.md +++ b/translations/zh-CN/content/github/copilot/index.md @@ -5,7 +5,7 @@ versions: fpt: '*' children: - /about-github-copilot-telemetry - - /telemetry-terms + - /github-copilot-telemetry-terms - /research-recitation --- diff --git a/translations/zh-CN/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md b/translations/zh-CN/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md index 9d8c941f67..3484852a0a 100644 --- a/translations/zh-CN/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md +++ b/translations/zh-CN/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md @@ -16,7 +16,7 @@ You can discover, browse, and install free and paid tools, including {% data var ## 在 {% data variables.product.prodname_marketplace %} 上查找工具 -您可以发现、浏览和安装其他人在 {% data variables.product.prodname_marketplace %} 上创建的 应用程序和操作，请参阅“[搜索 {% data variables.product.prodname_marketplace %}](/github/searching-for-information-on-github/searching-github-marketplace)”。 +您可以发现、浏览和安装其他人在 {% data variables.product.prodname_marketplace %} 上创建的 应用程序和操作，请参阅“[搜索 {% data variables.product.prodname_marketplace %}](/search-github/searching-on-github/searching-github-marketplace)”。 {% data reusables.actions.actions-not-verified %} diff --git a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning/sarif-support-for-code-scanning.md b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning/sarif-support-for-code-scanning.md index a8996ae49e..2aa48487af 100644 --- a/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning/sarif-support-for-code-scanning.md +++ b/translations/zh-CN/content/github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning/sarif-support-for-code-scanning.md @@ -31,7 +31,7 @@ SARIF（数据分析结果交换格式）是定义输出文件格式的 [OASIS 每次上传新的代码扫描结果时，都会处理结果并将警报添加到仓库中。 为防止出现针对同一问题的重复警报，{% data variables.product.prodname_code_scanning %} 使用指纹匹配各个运行的结果，使它们只会出现在所选分支的最新运行中出现一次。 这样可以在编辑文件时将警报与正确的代码行匹配。 -{% data variables.product.prodname_dotcom %} 使用 OASIS 标准中的 `partialFingerprints` 属性来检测两个结果在逻辑上是否相同。 更多信息请参阅 OASIS 文档中的 "[partialFingerprints property](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012611)" 条目。 +{% data variables.product.prodname_dotcom %} uses the `partialFingerprints` property in the OASIS standard as an input in the computation of whether two results are logically identical. Specifically, the `primaryLocationLineHash` is used as a stable intra-file location, which is combined with the repository, file path, and rule data to form the full identity. 更多信息请参阅 OASIS 文档中的 "[partialFingerprints property](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012611)" 条目。 通过 {% data variables.product.prodname_codeql_workflow %} 或 {% data variables.product.prodname_codeql_runner %} 创建的 SARIF 文件包含指纹数据。 如果使用 `upload-sarif` 操作上传 SARIF 文件且此数据缺少，则 {% data variables.product.prodname_dotcom %} 会尝试从源文件填充 `partialFingerprints` 字段。 有关上传结果的更多信息，请参阅“[将 SARIF 文件上传到 {% data variables.product.prodname_dotcom %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github#uploading-a-code-scanning-analysis-with-github-actions)”。 @@ -89,17 +89,17 @@ SARIF（数据分析结果交换格式）是定义输出文件格式的 [OASIS {% data reusables.code-scanning.upload-sarif-alert-limit %} -| 名称 | 描述 | -| --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `ruleId` | **可选。**规则的唯一标识符 (`reportingDescriptor.id`)。 更多信息请参阅 [`reportingDescriptor` 对象](#reportingdescriptor-object)。 {% data variables.product.prodname_code_scanning_capc %} 使用规则标识符在 {% data variables.product.prodname_dotcom %} 上按规则过滤结果。 | -| `ruleIndex` | **可选。**工具组件 `rules` 数组中相关规则（`reportingDescriptor` 对象）的索引。 更多信息请参阅 [`run` 对象](#run-object)。 | -| `rule` | **可选。**用于定位此结果的规则 (reportingdescriptor) 的引用。 更多信息请参阅 [`reportingDescriptor` 对象](#reportingdescriptor-object)。 | -| `level` | **可选。**结果的严重程度。 此级别覆盖规则定义的默认严重程度。 {% data variables.product.prodname_code_scanning_capc %} 使用级别在 {% data variables.product.prodname_dotcom %} 上按严重程度过滤结果。 | -| `message.text` | **必选。**描述结果的消息。 {% data variables.product.prodname_code_scanning_capc %} 显示消息文本作为结果的标题。 当可见空间有限时，仅显示消息的第一句。 | -| `locations[]` | **必填。**>最多可以检测到 10 个结果的位置集。 应只包含一个位置，除非只能通过在每个指定位置进行更改来更正问题。 **注：**{% data variables.product.prodname_code_scanning %} 至少需要一个位置才能显示结果。 {% data variables.product.prodname_code_scanning_capc %} 将使用此属性来决定要用结果注释哪个文件。 仅使用此数组的第一个值。 所有其他值都被忽略。 | -| `partialFingerprints` | **必选。**用于跟踪结果的唯一标识的一组字符串。 {% data variables.product.prodname_code_scanning_capc %} 使用 `partialFingerprints` 准确地识别在提交和分支之间相同的结果。 {% data variables.product.prodname_code_scanning_capc %} 将尝试使用 `partialFingerprints`（如果存在）。 如果您使用 `upload-action` 上传第三方 SARIF 文件，该操作将为您创建 `partialFingerprints`（如果它们未包含在 SARIF 文件中）。 更多信息请参阅“[使用指纹防止重复警报](#preventing-duplicate-alerts-using-fingerprints)”。 **注：**{% data variables.product.prodname_code_scanning_capc %} 只使用 `primaryLocationLineHash`。 | -| `codeFlows[].threadFlows[].locations[]` | **可选。**`threadFlow` 对象的 `location` 对象数组，它描述程序通过执行线程的进度。 `codeFlow` 对象描述用于检测结果的代码执行模式。 如果提供了代码流，{% data variables.product.prodname_code_scanning %} 将在 {% data variables.product.prodname_dotcom %} 上扩展代码流以获取相关结果。 更多信息请参阅 [`location` 对象](#location-object)。 | -| `relatedLocations[]` | 与此结果相关的一组位置。 当相关位置嵌入在结果消息中时，{% data variables.product.prodname_code_scanning_capc %} 将链接到这些位置。 更多信息请参阅 [`location` 对象](#location-object)。 | +| 名称 | 描述 | +| --------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `ruleId` | **可选。**规则的唯一标识符 (`reportingDescriptor.id`)。 更多信息请参阅 [`reportingDescriptor` 对象](#reportingdescriptor-object)。 {% data variables.product.prodname_code_scanning_capc %} 使用规则标识符在 {% data variables.product.prodname_dotcom %} 上按规则过滤结果。 | +| `ruleIndex` | **可选。**工具组件 `rules` 数组中相关规则（`reportingDescriptor` 对象）的索引。 更多信息请参阅 [`run` 对象](#run-object)。 | +| `rule` | **可选。**用于定位此结果的规则 (reportingdescriptor) 的引用。 更多信息请参阅 [`reportingDescriptor` 对象](#reportingdescriptor-object)。 | +| `level` | **可选。**结果的严重程度。 此级别覆盖规则定义的默认严重程度。 {% data variables.product.prodname_code_scanning_capc %} 使用级别在 {% data variables.product.prodname_dotcom %} 上按严重程度过滤结果。 | +| `message.text` | **必选。**描述结果的消息。 {% data variables.product.prodname_code_scanning_capc %} 显示消息文本作为结果的标题。 当可见空间有限时，仅显示消息的第一句。 | +| `locations[]` | **必填。**>最多可以检测到 10 个结果的位置集。 应只包含一个位置，除非只能通过在每个指定位置进行更改来更正问题。 **注：**{% data variables.product.prodname_code_scanning %} 至少需要一个位置才能显示结果。 {% data variables.product.prodname_code_scanning_capc %} 将使用此属性来决定要用结果注释哪个文件。 仅使用此数组的第一个值。 所有其他值都被忽略。 | +| `partialFingerprints` | **必选。**用于跟踪结果的唯一标识的一组字符串。 {% data variables.product.prodname_code_scanning_capc %} uses `partialFingerprints` as part of the computation to accurately identify which results are the same across commits and branches. {% data variables.product.prodname_code_scanning_capc %} 将尝试使用 `partialFingerprints`（如果存在）。 如果您使用 `upload-action` 上传第三方 SARIF 文件，该操作将为您创建 `partialFingerprints`（如果它们未包含在 SARIF 文件中）。 更多信息请参阅“[使用指纹防止重复警报](#preventing-duplicate-alerts-using-fingerprints)”。 **注：**{% data variables.product.prodname_code_scanning_capc %} 只使用 `primaryLocationLineHash`。 | +| `codeFlows[].threadFlows[].locations[]` | **可选。**`threadFlow` 对象的 `location` 对象数组，它描述程序通过执行线程的进度。 `codeFlow` 对象描述用于检测结果的代码执行模式。 如果提供了代码流，{% data variables.product.prodname_code_scanning %} 将在 {% data variables.product.prodname_dotcom %} 上扩展代码流以获取相关结果。 更多信息请参阅 [`location` 对象](#location-object)。 | +| `relatedLocations[]` | 与此结果相关的一组位置。 当相关位置嵌入在结果消息中时，{% data variables.product.prodname_code_scanning_capc %} 将链接到这些位置。 更多信息请参阅 [`location` 对象](#location-object)。 | ### `location` 对象 diff --git a/translations/zh-CN/content/github/index.md b/translations/zh-CN/content/github/index.md index f21fddcd84..d1e6b7c753 100644 --- a/translations/zh-CN/content/github/index.md +++ b/translations/zh-CN/content/github/index.md @@ -15,7 +15,6 @@ children: - /writing-on-github - /committing-changes-to-your-project - /collaborating-with-pull-requests - - /searching-for-information-on-github - /importing-your-projects-to-github - /managing-security-vulnerabilities - /finding-security-vulnerabilities-and-errors-in-your-code diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/about-identity-and-access-management-for-your-enterprise-account.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/about-identity-and-access-management-for-your-enterprise-account.md index b9c1585ce9..52c0b4b734 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/about-identity-and-access-management-for-your-enterprise-account.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/about-identity-and-access-management-for-your-enterprise-account.md @@ -21,6 +21,12 @@ shortTitle: 企业的 IAM {% data reusables.saml.switching-from-org-to-enterprise %} For more information, see "[Switching your SAML configuration from an organization to an enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)." +## 关于 {% data variables.product.prodname_emus %} + +{% data reusables.enterprise-accounts.emu-short-summary %} + +Configuring {% data variables.product.prodname_emus %} for SAML single-sign on and user provisioning involves following a different process than you would for an enterprise that isn't using {% data variables.product.prodname_managed_users %}. If your enterprise uses {% data variables.product.prodname_emus %}, see "[Configuring SAML single sign-on for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." + ## 支持的 IdP 我们测试并正式支持以下 IdP。 对于 SAML SSO，我们向执行 SAML 2.0 标准的所有身份提供程序提供有限的支持。 更多信息请参阅 OASIS 网站上的 [SAML Wiki](https://wiki.oasis-open.org/security)。 @@ -32,4 +38,3 @@ shortTitle: 企业的 IAM | OneLogin | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | PingOne | {% octicon "check-circle-fill" aria-label="The check icon" %} | | | Shibboleth | {% octicon "check-circle-fill" aria-label="The check icon" %} | | - diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/configuring-saml-single-sign-on-for-your-enterprise-account-using-okta.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/configuring-saml-single-sign-on-for-your-enterprise-account-using-okta.md index 03190be514..ff41c138b0 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/configuring-saml-single-sign-on-for-your-enterprise-account-using-okta.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/configuring-saml-single-sign-on-for-your-enterprise-account-using-okta.md @@ -16,6 +16,8 @@ shortTitle: Configure SAML with Okta {% data reusables.enterprise-accounts.user-provisioning-release-stage %} +{% data reusables.enterprise-accounts.emu-saml-note %} + ## 关于使用 Octa 的 SAML 您可以通过配置企业帐户使用 SAML SSO 以及身份提供程序 (IdP) Okta，从一个中心界面控制对 {% data variables.product.product_name %} 企业帐户及其他 web 应用程序的访问。 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account.md index 9253f87ad1..6379dffb4f 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account.md @@ -13,6 +13,8 @@ redirect_from: shortTitle: Enforce SAML --- +{% data reusables.enterprise-accounts.emu-saml-note %} + ## 关于企业帐户的 SAML 单点登录 {% data reusables.saml.dotcom-saml-explanation %}更多信息请参阅“[关于使用 SAML 单点登录管理身份和访问](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)”。 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/managing-team-synchronization-for-organizations-in-your-enterprise-account.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/managing-team-synchronization-for-organizations-in-your-enterprise-account.md index e9210a6dbf..5453a75226 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/managing-team-synchronization-for-organizations-in-your-enterprise-account.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/managing-team-synchronization-for-organizations-in-your-enterprise-account.md @@ -12,6 +12,8 @@ redirect_from: shortTitle: 管理团队同步 --- +{% data reusables.enterprise-accounts.emu-scim-note %} + ## 关于企业帐户的团队同步 如果使用 Azure AD 作为 IdP，您可以为企业帐户启用团队同步，以允许组织所有者和团队维护员将企业帐户拥有的组织中的团队与 IdP 组同步。 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md index e74f717200..70c2ba3f87 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md @@ -10,6 +10,8 @@ topics: shortTitle: Switching from organization --- +{% data reusables.enterprise-accounts.emu-saml-note %} + ## 关于企业帐户的 SAML 单点登录 {% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/index.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/index.md index 5da8df2ce3..7f8f8de24b 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/index.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/index.md @@ -14,6 +14,7 @@ topics: children: - /managing-your-enterprise-account - /managing-users-in-your-enterprise + - /managing-your-enterprise-users-with-your-identity-provider - /managing-organizations-in-your-enterprise-account - /configuring-identity-and-access-management-for-your-enterprise-account - /setting-policies-for-organizations-in-your-enterprise-account diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account.md index 4e6b28f548..da8833aad5 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account.md @@ -1,6 +1,6 @@ --- title: 将组织添加到企业帐户 -intro: 您可以在企业帐户中创建要管理的新组织。 +intro: You can create new organizations or invite existing organizations to manage within your enterprise account. product: '{% data reusables.gated-features.enterprise-accounts %}' redirect_from: - /articles/adding-organizations-to-your-enterprise-account @@ -13,9 +13,9 @@ topics: shortTitle: 添加组织 --- -企业所有者可在企业帐户的设置中创建新组织。 +Enterprise owners can create new organizations within an enterprise account's settings or invite existing organizations to join an enterprise account. -要将组织添加到企业帐户，必须在企业帐户设置中创建组织。 如果您想将现有组织转移到您的企业帐户，请联系您的 {% data variables.product.prodname_dotcom %} 销售客户代表。 +要将组织添加到企业帐户，必须在企业帐户设置中创建组织。 ## 在企业帐户中创建组织 @@ -29,3 +29,15 @@ shortTitle: 添加组织 4. 单击 **Create organization（创建组织）**。 5. 在 "Invite owners"（邀请所有者）下，输入您想邀其成为组织所有者的人员的用户名，然后单击 **Invite（邀请）**。 ![组织所有者搜索字段和邀请按钮](/assets/images/help/business-accounts/invite-org-owner.png) 6. 单击 **Finish（完成）**。 + +## Inviting an organization to join your enterprise account + +Enterprise owners can invite existing organizations to join their enterprise account. If the organization you want to invite is already owned by another enterprise, you will not be able to issue an invitation until the previous enterprise gives up ownership of the organization. + +{% data reusables.enterprise-accounts.access-enterprise %} +2. On the **Organizations** tab, above the list of organizations, click **Invite organization**. ![Invite organization](/assets/images/help/business-accounts/enterprise-account-invite-organization.png) +3. Under "Organization name", start typing the name of the organization you want to invite and select it when it appears in the drop-down list. ![Search for organization](/assets/images/help/business-accounts/enterprise-account-search-for-organization.png) +4. Click **Invite organization**. +5. The organization owners will receive an email inviting them to join the organization. At least one owner needs to accept the invitation before the process can continue. You can cancel or resend the invitation at any time before an owner approves it. ![Cancel or resend](/assets/images/help/business-accounts/enterprise-account-invitation-sent.png) +6. Once an organization owner has approved the invitation, you can view its status in the list of pending invitations. ![Pending invitation](/assets/images/help/business-accounts/enterprise-account-pending.png) +7. Click **Approve** to complete the transfer, or **Cancel** to cancel it. ![Approve invitation](/assets/images/help/business-accounts/enterprise-account-transfer-approve.png) diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md index 66846fe987..e0e6eb11a4 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md @@ -28,6 +28,12 @@ If you want to manage owners and billing managers for an enterprise account on { {% endif %} +{% ifversion fpt %} + +If your enterprise uses {% data variables.product.prodname_emus %}, enterprise owners can only be added or removed through your identity provider. For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." + +{% endif %} + {% tip %} **提示：**有关管理企业帐户拥有的组织中用户的更多信息，请参阅“[管理组织中的成员资格](/articles/managing-membership-in-your-organization)”和“[通过角色管理人们对组织的访问](/articles/managing-peoples-access-to-your-organization-with-roles)”。 diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md index 5c006c1600..ab54e68c79 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md @@ -18,18 +18,13 @@ shortTitle: 查看和管理 SAML 访问 对企业帐户启用 SAML 单点登录时，每个企业成员都可以将其在身份提供程序 (IdP) 上的外部身份链接到其现有的 {% data variables.product.product_name %} 帐户。 {% data reusables.saml.about-saml-access-enterprise-account %} +If your enterprise is uses {% data variables.product.prodname_emus %}, your members will use accounts provisioned through your IdP. {% data variables.product.prodname_managed_users_caps %} will not use their existing user account on {% data variables.product.product_name %}. For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." + ## 查看和撤销链接的身份 {% data reusables.saml.about-linked-identities %} -{% warning %} - -**警告：**对于使用 SCIM 的组织： -- 撤销 {% data variables.product.product_name %} 上链接的用户身份也会删除 SAML 和 SCIM 元数据。 因此，身份提供商无法同步或解除预配已链接的用户身份。 -- 管理员必须通过身份提供商撤销链接的身份。 -- 要撤销链接的身份并通过身份提供商链接其他帐户，管理员可以删除用户并重新分配给 {% data variables.product.product_name %} 应用程序。 更多信息请参阅身份提供商的文档。 - -{% endwarning %} +If your enterprise uses {% data variables.product.prodname_emus %}, you will not be able to deprovision or remove user accounts from the enterprise on {% data variables.product.product_name %}. Any changes you need to make to your enterprise's {% data variables.product.prodname_managed_users %} should be made through your IdP. {% data reusables.identity-and-permissions.revoking-identity-team-sync %} diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md new file mode 100644 index 0000000000..05d9159b5b --- /dev/null +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users.md @@ -0,0 +1,84 @@ +--- +title: About Enterprise Managed Users +shortTitle: About managed users +intro: 'You can centrally manage identity and access for your enterprise members on {% data variables.product.prodname_dotcom %} from your identity provider.' +product: '{% data reusables.gated-features.emus %}' +redirect_from: + - /early-access/github/articles/get-started-with-managed-users-for-your-enterprise +versions: + fpt: '*' +topics: + - Accounts + - Enterprise +--- + +## 关于 {% data variables.product.prodname_emus %} + +With {% data variables.product.prodname_emus %}, you can control the user accounts of your enterprise members through your identity provider (IdP). You can simplify authentication with SAML single sign-on (SSO) and provision, update, and deprovision user accounts for your enterprise members. Users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your IdP are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and added to your enterprise. You control usernames, profile data, team membership, and repository access from your IdP. + +In your IdP, you can give each {% data variables.product.prodname_managed_user %} the role of user, enterprise owner, or billing manager. {% data variables.product.prodname_managed_users_caps %} can own organizations within your enterprise and can add other {% data variables.product.prodname_managed_users %} to the organizations and teams within. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" and "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)." + +You can also manage team membership within an organization in your enterprise directly through your IdP, allowing you to manage repository access using groups in your IdP. Organization membership can be managed manually or updated automatically as {% data variables.product.prodname_managed_users %} are added to teams within the organization. For more information, see "[Managing team memberships with identity provider groups](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)." + +You can grant {% data variables.product.prodname_managed_users %} access and the ability to contribute to repositories within your enterprise, but {% data variables.product.prodname_managed_users %} cannot create public content or collaborate with other users, organizations, and enterprises on the rest of {% data variables.product.prodname_dotcom %}. The {% data variables.product.prodname_managed_users %} provisioned for your enterprise cannot be invited to organizations or repositories outside of the enterprise, nor can the {% data variables.product.prodname_managed_users %} be invited to other enterprises. Outside collaborators are not supported by {% data variables.product.prodname_emus %}. + +The usernames of your enterprise's {% data variables.product.prodname_managed_users %} and their profile information, such as display names and email addresses, are set by through your IdP and cannot be changed by the users themselves. For more information, see "[Usernames and profile information](#usernames-and-profile-information)." + +{% data reusables.enterprise-accounts.emu-forks %} + +Enterprise owners can audit all of the {% data variables.product.prodname_managed_users %}' actions on {% data variables.product.prodname_dotcom %}. + +To use {% data variables.product.prodname_emus %}, you need a separate type of enterprise account with {% data variables.product.prodname_emus %} enabled. For more information about creating this account, see "[About enterprises with managed users](#about-enterprises-with-managed-users)." + + +## Identity provider support + +{% data variables.product.prodname_emus %} supports the following IdPs: + +{% data reusables.enterprise-accounts.emu-supported-idps %} + +## Abilities and restrictions of {% data variables.product.prodname_managed_users %} + +{% data variables.product.prodname_managed_users_caps %} can only contribute to private and internal repositories within their enterprise and private repositories owned by their user account. {% data variables.product.prodname_managed_users_caps %} have read-only access to the wider {% data variables.product.prodname_dotcom %} community. + +* {% data variables.product.prodname_managed_users_caps %} cannot create issues or pull requests in, comment or add reactions to, nor star, watch, or fork repositories outside of the enterprise. +* {% data variables.product.prodname_managed_users_caps %} cannot push code to repositories outside of the enterprise. +* {% data variables.product.prodname_managed_users_caps %} and the content they create is only visible to other members of the enterprise. +* {% data variables.product.prodname_managed_users_caps %} cannot follow users outside of the enterprise. +* {% data variables.product.prodname_managed_users_caps %} cannot create gists or comment on gists. +* {% data variables.product.prodname_managed_users_caps %} cannot install {% data variables.product.prodname_github_apps %} on their user accounts. +* Other {% data variables.product.prodname_dotcom %} users cannot see, mention, or invite a {% data variables.product.prodname_managed_user %} to collaborate. +* {% data variables.product.prodname_managed_users_caps %} can only own private repositories and {% data variables.product.prodname_managed_users %} can only invite other enterprise members to collaborate on their owned repositories. +* Only private and internal repositories can be created in organizations owned by an {% data variables.product.prodname_emu_enterprise %}, depending on organization and enterprise repository visibility settings. + +## About enterprises with managed users + +To use {% data variables.product.prodname_emus %}, you need a separate type of enterprise account with {% data variables.product.prodname_emus %} enabled. To try out {% data variables.product.prodname_emus %} or to discuss options for migrating from your existing enterprise, please contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact). + +Your contact on the GitHub Sales team will work with you to create your new {% data variables.product.prodname_emu_enterprise %}. You'll need to provide the email address for the user who will set up your enterprise and a short code that will be used as the suffix for your enterprise members' usernames. {% data reusables.enterprise-accounts.emu-shortcode %} For more information, see "[Usernames and profile information](#usernames-and-profile-information)." + +After we create your enterprise, you will receive an email from {% data variables.product.prodname_dotcom %} inviting you to choose a password for your enterprise's setup user, which will be the first owner in the enterprise. The setup user is only used to configure SAML single sign-on and SCIM provisioning integration for the enterprise. It will no longer have access to administer the enterprise account once SAML is successfully enabled. + +The setup user's username is your enterprise's shortcode suffixed with `_admin`. After you log in to your setup user, you can get started by configuring SAML SSO for your enterprise. For more information, see "[Configuring SAML single sign-on for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." + +{% note %} + +{% data reusables.enterprise-accounts.emu-password-reset-session %} + +{% endnote %} + +## 验证为 {% data variables.product.prodname_managed_user %} + +{% data variables.product.prodname_managed_users_caps %} must authenticate through their identity provider. + +To authenticate, {% data variables.product.prodname_managed_users %} must visit their IdP application portal or **https://github.com/enterprises/ENTERPRISE_NAME**, replacing **ENTERPRISE_NAME** with your enterprise's name. + +## Usernames and profile information + +When your {% data variables.product.prodname_emu_enterprise %} is created, you will choose a short code that will be used as the suffix for your enterprise member's usernames. {% data reusables.enterprise-accounts.emu-shortcode %} The setup user who configures SAML SSO has a username in the format of **@SHORT-CODE_admin**. + +When you provision a new user from your identity provider, the new {% data variables.product.prodname_managed_user %} will have a {% data variables.product.product_name %} username in the format of **@IDP-USERNAME_SHORT-CODE**. When using Azure Active Directory (Azure AD), _IDP-USERNAME_ is formed by normalizing the characters preceding the `@` character in the UPN (User Principal Name) provided by Azure AD. When using Okta, _IDP-USERNAME_ is the normalized username attribute provided by Okta. + +The username of the new account provisioned on {% data variables.product.product_name %}, including underscore and short code, must not exceed 39 characters. + +The profile name and email address of a {% data variables.product.prodname_managed_user %} is also provided by the IdP. {% data variables.product.prodname_managed_users_caps %} cannot change their profile name or email address on {% data variables.product.prodname_dotcom %}. diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/auditing-activity-in-your-enterprise.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/auditing-activity-in-your-enterprise.md new file mode 100644 index 0000000000..dd9eba631a --- /dev/null +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/auditing-activity-in-your-enterprise.md @@ -0,0 +1,32 @@ +--- +title: Auditing activity in your enterprise +shortTitle: Auditing activity +intro: 'You can audit the activity of the {% data variables.product.prodname_managed_users %} in your enterprise, viewing information about what actions were performed, by which user, and when they took place.' +permissions: Enterprise owners can access the audit log. +product: '{% data reusables.gated-features.emus %}' +versions: + fpt: '*' +topics: + - Accounts + - Enterprise +--- + +## About the audit log + +The audit log allows enterprise owners to quickly review or export the actions performed by both owners and members of your enterprise. Each audit log entry shows information about the event. + +- 可在其中执行操作的组织 +- 执行操作的用户 +- 执行操作的仓库 +- 执行的操作内容 +- 发生操作的国家/地区 +- 操作发生的日期和时间 + +## 访问审核日志 + +You can also access the audit log for your enterprise from the REST API. For more information, see "[GitHub Enterprise administration](/rest/reference/enterprise-admin#get-the-audit-log-for-an-enterprise)" in the API documentation. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.audit-log-tab %} +1. Optionally, above the list of events, select the **Export Git Events** or **Export** drop-down menu and choose options for exporting events from the audit log. !["Export Git Events" and "Export" drop-down menus for the enterprise audit log](/assets/images/help/enterprises/audit-log-export-drop-down-menus.png) diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users.md new file mode 100644 index 0000000000..d89e584676 --- /dev/null +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users.md @@ -0,0 +1,109 @@ +--- +title: Configuring SAML single sign-on for Enterprise Managed Users +shortTitle: SAML for managed users +intro: 'You can automatically manage access to your enterprise account on {% data variables.product.prodname_dotcom %} by configuring Security Assertion Markup Language (SAML) single sign-on (SSO).' +product: '{% data reusables.gated-features.emus %}' +versions: + fpt: '*' +topics: + - Accounts + - Enterprise +--- + +## About SAML single sign-on for {% data variables.product.prodname_emus %} + +With {% data variables.product.prodname_emus %}, your enterprise uses SAML SSO to authenticate all members. Instead of signing in to {% data variables.product.prodname_dotcom %} with a {% data variables.product.prodname_dotcom %} username and password, members of your enterprise will sign in through your IdP. + +{% data variables.product.prodname_emus %} supports the following IdPs: + +{% data reusables.enterprise-accounts.emu-supported-idps %} + +After you configure SAML SSO, we recommend storing your recovery codes so you can recover access to your enterprise in the event that your identity provider is unavailable. For more information, see "[Saving your recovery codes](#saving-your-recovery-codes)." + +## Configuring SAML single sign-on for {% data variables.product.prodname_emus %} + +To configure SAML SSO for your {% data variables.product.prodname_emu_enterprise %}, you must configure an application on your IdP and then configure your enterprise on GitHub.com. After you configure SAML SSO, you can configure user provisioning. + +To install and configure the {% data variables.product.prodname_emu_idp_application %} application on your IdP, you must have a tenant and administrative access on a supported IdP. + +{% note %} + +{% data reusables.enterprise-accounts.emu-password-reset-session %} + +{% endnote %} + +1. [Configuring your identity provider](#configuring-your-identity-provider) +2. [配置企业](#configuring-your-enterprise) +3. [Enabling provisioning](#enabling-provisioning) + +### Configuring your identity provider + +To configure your IdP, follow the instructions they provide for configuring the {% data variables.product.prodname_emu_idp_application %} application on your IdP. + +1. To install the {% data variables.product.prodname_emu_idp_application %} application, click the link for your IdP below: + + - [{% data variables.product.prodname_emu_idp_application %} application on Azure Active Directory](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/aad.githubenterprisemanageduser?tab=Overview) + - [{% data variables.product.prodname_emu_idp_application %} application on Okta](https://www.okta.com/integrations/github-enterprise-managed-user) + +1. To configure the {% data variables.product.prodname_emu_idp_application %} application and your IdP, click the link below and follow the instructions provided by your IdP: + + - [Azure Active Directory tutorial for {% data variables.product.prodname_emus %}](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-enterprise-managed-user-tutorial) + - [Okta documentation for {% data variables.product.prodname_emus %}](https://saml-doc.okta.com/SAML_Docs/How-to-Configure-SAML-2.0-for-GitHub-Enterprise-Managed-User.html) + +1. So you can test and configure your enterprise, assign yourself or the user that will be configuring SAML SSO on {% data variables.product.prodname_dotcom %} to the {% data variables.product.prodname_emu_idp_application %} application on your IdP. + +1. To enable you to continue configuring your enterprise on {% data variables.product.prodname_dotcom %}, locate and note the following information from the application you installed on your IdP: + + | 值 | 其他名称 | 描述 | + |:----------------------------------- |:------------------ |:---------------------------------------------------------------- | + | IdP Sign-On URL | Login URL, IdP URL | Application's URL on your IdP | + | IdP Identifier URL | Issuer | IdP's identifier to service providers for SAML authentication | + | Signing certificate, Base64-encoded | Public certificate | Public certificate that IdP uses to sign authentication requests | + +### 配置企业 + +After you install and configure the {% data variables.product.prodname_emu_idp_application %} application on your identity provider, you can configure your enterprise. + +1. Sign into {% data variables.product.prodname_dotcom_the_website %} as the setup user for your new enterprise with the username **@SHORT-CODE_admin**. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} + +1. Under "SAML single sign-on", select **Require SAML authentication**. ![用于启用 SAML SSO 的复选框](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png) + +1. Under **Sign on URL**, type the HTTPS endpoint of your IdP for single sign-on requests that you noted while configuring your IdP. ![登录时将成员转发到的 URL 字段](/assets/images/help/saml/saml_sign_on_url_business.png) + +1. Under **Issuer**, type your SAML issuer URL that you noted while configuring your IdP, to verify the authenticity of sent messages. ![SAML 签发者姓名字段](/assets/images/help/saml/saml_issuer.png) + +1. Under **Public Certificate**, paste the certificate that you noted while configuring your IdP, to verify SAML responses. ![身份提供程序的公共证书字段](/assets/images/help/saml/saml_public_certificate.png) + +1. 要验证来自 SAML 签发者的请求的完整性，请单击 {% octicon "pencil" aria-label="The edit icon" %}。 Then, in the "Signature Method" and "Digest Method" drop-downs, choose the hashing algorithm used by your SAML issuer. ![SAML 签发者使用的签名方法和摘要方法哈希算法下拉列表](/assets/images/help/saml/saml_hashing_method.png) + +1. Before enabling SAML SSO for your enterprise, to ensure that the information you've entered is correct, click **Test SAML configuration**. ![实施前测试 SAML 配置的按钮](/assets/images/help/saml/saml_test.png) + +1. 单击 **Save（保存）**。 + + {% note %} + + **Note:** When you require SAML SSO for your enterprise, the setup user will no longer have access to the enterprise but will remain signed in to GitHub. Only {% data variables.product.prodname_managed_users %} provisioned by your IdP will have access to the enterprise. + + {% endnote %} + +1. To ensure you can still access your enterprise in the event that your identity provider is ever unavailable in the future, click **Download**, **Print**, or **Copy** to save your recovery codes. ![实施前测试 SAML 配置的按钮](/assets/images/help/saml/saml_recovery_code_options.png) + +### Enabling provisioning + +After you enable SAML SSO, enable provisioning. For more information, see "[Configuring SCIM provisioning for enterprise managed users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users)." + +## Saving your recovery codes + +In the event that your identity provider is unavailable, you can use the setup user and a recovery code to sign in and access your enterprise. If you did not save your recovery codes when you configured SAML SSO, you can still access them from your enterprise's settings. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.security-tab %} + +1. Under "Require SAML authentication", click **Save your recovery codes**. ![实施前测试 SAML 配置的按钮](/assets/images/help/enterprises/saml-recovery-codes-link.png) + +2. To save your recovery codes, click **Download**, **Print**, or **Copy**. ![实施前测试 SAML 配置的按钮](/assets/images/help/saml/saml_recovery_code_options.png) diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md new file mode 100644 index 0000000000..2979cdaf5a --- /dev/null +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md @@ -0,0 +1,76 @@ +--- +title: Configuring SCIM provisioning for Enterprise Managed Users with Okta +shortTitle: Set up provisioning with Okta +intro: You can provision new users and manage their membership of your enterprise and teams using Okta as your identity provider. +product: '{% data reusables.gated-features.emus %}' +versions: + fpt: '*' +redirect_from: + - /early-access/github/articles/configuring-provisioning-for-managed-users-with-okta +topics: + - Accounts + - Enterprise +--- + +## About provisioning with Okta + +You can use {% data variables.product.prodname_emus %} with Okta as your identity provider to provision new accounts, manage enterprise membership, and manage team memberships for organizations in your enterprise. For more information about provisioning for {% data variables.product.prodname_emus %}, see "[Configuring SCIM provisioning for enterprise managed users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users)." + +Before you can configure provisioning with Okta, you must configure SAML single-sign on. For more information, see "[Configuring SAML single sign-on for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." + +To configure provisioning with Okta, you must set your enterprise's name in the {% data variables.product.prodname_emu_idp_application %} application and enter your setup user's personal access token. You can then start provisioning users in Okta. + +## Supported features + +{% data variables.product.prodname_emus %} supports many provisioning features in Okta. + +| 功能 | 描述 | +| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 推送新用户 | Users that are assigned to the {% data variables.product.prodname_emu_idp_application %} application in Okta are automatically created in the enterprise on {% data variables.product.product_name %}. | +| Push Profile Update | Updates made to the user's profile in Okta will be pushed to {% data variables.product.product_name %}. | +| Push Groups | Groups in Okta that are assigned to the {% data variables.product.prodname_emu_idp_application %} application as Push Groups are automatically created in the enterprise on {% data variables.product.product_name %}. | +| 推送用户停用 | Unassigning the user from the {% data variables.product.prodname_emu_idp_application %} application in Okta will disable the user on {% data variables.product.product_name %}. The user will not be able to sign in, but the user's information is maintained. | +| 重新激活用户 | Users in Okta whose Okta accounts are reactivated and who are assigned back to the {% data variables.product.prodname_emu_idp_application %} application will be enabled. | + +{% note %} + +**Note:** {% data variables.product.prodname_emus %} does not support modifications to usernames. + +{% endnote %} + +## Setting your enterprise name + +After your {% data variables.product.prodname_emu_enterprise %} has been created, you can begin to configure provisioning by setting your enterprise name in Okta. + +1. Navigate to your {% data variables.product.prodname_emu_idp_application %} application on Okta. +1. Click the **Sign On** tab. +1. To make changes, click **Edit**. +1. Under "Advanced Sign-on Settings", in the "Enterprise Name" text box, type your enterprise name. For example, if you access your enterprise at `https://github.com/enterprises/octoinc`, your enterprise name would be "octoinc". ![Screenshot of the Enterprise Name field on Okta](/assets/images/help/enterprises/okta-emu-enterprise-name.png) +1. To save your enterprise name, click **Save**. + +## Configuring provisioning + +After setting your enterprise name, you can proceed to configure provisioning settings. + +To configure provisioning, the setup user with the **@SHORT-CODE_admin** username will need to provide a personal access token with the **admin:enterprise** scope. For more information on creating a new token, see "[Creating a personal access token](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users#creating-a-personal-access-token)." + +1. Navigate to your {% data variables.product.prodname_emu_idp_application %} application on Okta. +1. Click the **Provisioning** tab. +1. In the settings menu, click **Integration**. +1. To make changes, click **Edit**. +1. 选择 **Enable API integration（启用 API 集成）**。 +1. In the "API Token" field, enter the personal access token with the **admin:enterprise** scope belonging to the setup user. ![Screenshot showing the API Token field on Okta](/assets/images/help/enterprises/okta-emu-token.png) +1. Click **Test API Credentials**. If the test is successful, a verification message will appear at the top of the screen. +1. To save the token, click **Save**. +1. In the settings menu, click **To App**. ![Screenshot showing the To App menu item on Okta](/assets/images/help/enterprises/okta-emu-to-app-menu.png) +1. To the right of "Provisioning to App", to allow changes to be made, click **Edit**. +1. Select **Enable** for **Create Users**, **Update User Attributes**, and **Deactivate Users**. ![Screenshot showing provisioning options on Okta](/assets/images/help/enterprises/okta-emu-provisioning-to-app.png) +1. To finish configuring provisioning, click **Save**. + +## Assigning users + +After you have configured SAML SSO and provisioning, you will be able provision new users on {% data variables.product.prodname_dotcom_the_website %} by assigning users to the {% data variables.product.prodname_emu_idp_application %} application. You can also automatically manage organization membership by assigning groups to the application as push groups and connecting the push groups to teams in your organizations. For more information about managing teams, see "[Managing team memberships with identity provider groups](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)." + +When assigning users, you can use the "Roles" attribute in the {% data variables.product.prodname_emu_idp_application %} application to set a user's role in your enterprise on {% data variables.product.product_name %}. For more information on roles, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)." + +![Screenshot showing the role options for provisioned user on Okta](/assets/images/help/enterprises/okta-emu-user-role.png) diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md new file mode 100644 index 0000000000..dde0530365 --- /dev/null +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users.md @@ -0,0 +1,54 @@ +--- +title: Configuring SCIM provisioning for Enterprise Managed Users +shortTitle: Provisioning managed users +intro: You can configure your identity provider to provision new users and manage their membership in your enterprise and teams. +product: '{% data reusables.gated-features.emus %}' +versions: + fpt: '*' +topics: + - Accounts + - Enterprise +--- + +## About provisioning for {% data variables.product.prodname_emus %} + +You can configure provisioning for {% data variables.product.prodname_emus %} to create, manage, and deactivate user accounts for your enterprise members. When you configure provisioning for {% data variables.product.prodname_emus %}, users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your identity provider are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} via SCIM, and the users are added to your enterprise. + +When you update information associated with a user's identity on your IdP, your IdP will update the user's account on GitHub.com. When you unassign the user from the {% data variables.product.prodname_emu_idp_application %} application or deactivate a user's account on your IdP, your IdP will communicate with {% data variables.product.prodname_dotcom %} to invalidate any SAML sessions and disable the member's account. The disabled account's information is maintained and their username is changed to a hash of their original username with the short code appended. If you reassign a user to the {% data variables.product.prodname_emu_idp_application %} application or reactivate their account on your IdP, the {% data variables.product.prodname_managed_user %} account on {% data variables.product.prodname_dotcom %} will be reactivated and username restored. + +Groups in your IdP can be used to manage team membership within your enterprise's organizations, allowing you to configure repository access and permissions through your IdP. For more information, see "[Managing team memberships with identity provider groups](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)." + +## 基本要求 + +Before you can configure provisioning for {% data variables.product.prodname_emus %}, you must configure SAML single-sign on. For more information, see "[Configuring SAML single sign-on for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." + +## 创建个人访问令牌 + +To configure provisioning for your {% data variables.product.prodname_emu_enterprise %}, you need a personal access token with the **admin:enterprise** scope that belongs to the setup user. + +{% warning %} + +**Warning:** If the token expires or a provisioned user creates the token, SCIM provisioning may unexpectedly stop working. Make sure that you create the token while signed in as the setup user and that the token expiration is set to "No expiration". + +{% endwarning %} + +1. Sign into {% data variables.product.prodname_dotcom_the_website %} as the setup user for your new enterprise with the username **@SHORT-CODE_admin**. +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.developer_settings %} +{% data reusables.user_settings.personal_access_tokens %} +{% data reusables.user_settings.generate_new_token %} +1. Under **Note**, give your token a descriptive name. ![Screenshot showing the token's name](/assets/images/help/enterprises/emu-pat-name.png) +1. Select the **Expiration** drop-down menu, then click **No expiration**. ![Screenshot showing token expiration set to no expiration](/assets/images/help/enterprises/emu-pat-no-expiration.png) +1. Select the **admin:enterprise** scope. ![Screenshot showing the admin:enterprise scope](/assets/images/help/enterprises/enterprise-pat-scope.png) +1. 单击 **Generate token（生成令牌）**。 ![生成令牌按钮](/assets/images/help/settings/generate_token.png) +1. To copy the token to your clipboard, click the {% octicon "paste" aria-label="The copy icon" %}. ![新建的令牌](/assets/images/help/settings/personal_access_tokens.png) +2. To save the token for use later, store the new token securely in a password manager. + +## Configuring provisioning for {% data variables.product.prodname_emus %} + +After creating your personal access token and storing it securely, you can configure provisioning on your identity provider. + +To configure Azure Active Directory to provision users for your {% data variables.product.prodname_emu_enterprise %}, see [Tutorial: Configure GitHub Enterprise Managed User for automatic user provisioning](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-enterprise-managed-user-provisioning-tutorial) in the Azure AD documentation. + +To configure Okta to provision users for your {% data variables.product.prodname_emu_enterprise %}, see "[Configuring SCIM provisioning for Enterprise Managed Users with Okta](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users-with-okta)." + diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/index.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/index.md new file mode 100644 index 0000000000..8005a503ab --- /dev/null +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/index.md @@ -0,0 +1,19 @@ +--- +title: Managing your enterprise users with your identity provider +shortTitle: Manage users with your IdP +product: '{% data reusables.gated-features.emus %}' +intro: You can manage identity and access with your identity provider and provision accounts that can only contribute to your enterprise. +versions: + fpt: '*' +topics: + - Enterprise + - Accounts +children: + - /about-enterprise-managed-users + - /configuring-saml-single-sign-on-for-enterprise-managed-users + - /configuring-scim-provisioning-for-enterprise-managed-users + - /configuring-scim-provisioning-for-enterprise-managed-users-with-okta + - /managing-team-memberships-with-identity-provider-groups + - /auditing-activity-in-your-enterprise +--- + diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups.md new file mode 100644 index 0000000000..41aefa9470 --- /dev/null +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups.md @@ -0,0 +1,67 @@ +--- +title: Managing team memberships with identity provider groups +shortTitle: Manage teams with your IdP +intro: 'You can manage team membership on {% data variables.product.product_name %} through your identity provider (IdP) by connecting IdP groups with your {% data variables.product.prodname_emu_enterprise %}.' +product: '{% data reusables.gated-features.emus %}' +versions: + fpt: '*' +topics: + - Accounts + - Enterprise +--- + +## About team management with {% data variables.product.prodname_emus %} + +With {% data variables.product.prodname_emus %}, you can manage team membership within your enterprise through your IdP. When you connect a team in one of your enterprise's organizations to an IdP group, changes to membership from the IdP group are reflected in your enterprise automatically, reducing the need for manual updates and custom scripts. + +When a change to an IdP group or a new team connection results in a {% data variables.product.prodname_managed_user %} joining a team in an organization they were not already a member of, the {% data variables.product.prodname_managed_user %} will automatically be added to the organization. Organization owners can also manage organization membership manually. When you disconnect a group from a team, users who became members of the organization via team membership are removed from the organization if they are not assigned membership in the organization by any other means. + +You can connect a team in your enterprise to one IdP group. You can assign the same IdP group to multiple teams in your enterprise. + +If you are connecting an existing team to an IdP group, you must first remove any members that were added manually. After you connect a team in your enterprise to an IdP group, your IdP administrator must make team membership changes through the identity provider. You cannot manage team membership on {% data variables.product.prodname_dotcom_the_website %}. + +When group membership changes on your IdP, your IdP sends a SCIM request with the changes to {% data variables.product.prodname_dotcom_the_website %} according to the schedule determined by your IdP, so change may not be immediate. Any requests that change team or organization membership will register in the audit log as changes made by the account used to configure user provisioning. + +Teams connected to IdP groups cannot be parents of other teams nor a child of another team. If the team you want to connect to an IdP group is a parent or child team, we recommend creating a new team or removing the nested relationships that make your team a parent team. + +To manage repository access for any team in your enterprise, including teams connected to an IdP group, you must make changes on {% data variables.product.prodname_dotcom_the_website %}. 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)". + +## Creating a new team connected to an IdP group + +Any member of an organization can create a new team and connect the team to an IdP group. + +{% data reusables.profile.access_org %} +{% data reusables.user_settings.access_org %} +{% data reusables.organizations.new_team %} +{% data reusables.organizations.team_name %} +{% data reusables.organizations.team_description %} +1. To connect a team, select the "Identity Provider Groups" drop-down menu and click the team you want to connect. ![用于选择身份提供程序组的下拉菜单](/assets/images/help/teams/choose-an-idp-group.png) +{% data reusables.organizations.team_visibility %} +{% data reusables.organizations.create_team %} + +## Managing the connection between an existing team and an IdP group + +Organization owners and team maintainers can manage the existing connection between an IdP group and a team. + +{% note %} + +**Note**: Before you connect an existing team on {% data variables.product.prodname_dotcom_the_website %} to an IdP group for the first time, all members of the team on {% data variables.product.prodname_dotcom_the_website %} must first be removed. For more information, see "[Removing organization members from a team](/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team)." + +{% endnote %} + +{% data reusables.profile.access_profile %} + +{% data reusables.profile.access_org %} +{% data reusables.organizations.specific_team %} +{% data reusables.organizations.team_settings %} +1. Optionally, under "Identity Provider Group", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="X symbol" %}. ![从 GitHub 团队取消选择已连接的 IdP 组](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png) +1. To connect an IdP group, under "Identity Provider Group", select the drop-down menu, and click an identity provider group from the list. ![Drop-down menu to choose identity provider group](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png) +1. 单击 **Save changes（保存更改）**。 + +## Viewing IdP groups and connected teams + +You can review a list of IdP groups, any teams connected to an IdP group, and see the membership of each IdP group on {% data variables.product.product_name %}. You must edit the membership for a group on your IdP. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.identity-provider-tab %} +1. Under "Identity Provider (IdP) Groups", review the list of IdP groups. diff --git a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account.md b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account.md index 4303ea9886..5e87c0d143 100644 --- a/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account.md +++ b/translations/zh-CN/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account.md @@ -42,7 +42,9 @@ shortTitle: GitHub Actions 的策略 ## 配置公共复刻工作流程所需的批准 -{% data reusables.actions.workflow-run-approve-public-fork %} 您可以使用下面的程序为企业配置此行为。 +{% data reusables.actions.workflow-run-approve-public-fork %} + +You can configure this behavior for your enterprise using the procedure below. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} diff --git a/translations/zh-CN/content/github/site-policy/dmca-takedown-policy.md b/translations/zh-CN/content/github/site-policy/dmca-takedown-policy.md index 908b51168c..07c5abf8c7 100644 --- a/translations/zh-CN/content/github/site-policy/dmca-takedown-policy.md +++ b/translations/zh-CN/content/github/site-policy/dmca-takedown-policy.md @@ -15,7 +15,7 @@ topics: 欢迎阅读 GitHub 的《千禧年数字版权法案》（通常称为 "DMCA"）指南。 本页面并非该法案的综合入门读物。 但是，如果您收到针对您在 GitHub 上所发布内容的 DMCA 删除通知，或者您是要发出此类通知的权利持有者，此页面将有助于您了解该法案以及我们遵守该法案的政策。 -(If you just want to submit a notice, you can skip to "[G. Submitting Notices](#g-submitting-notices).") +（如果只想提交通知，您可以跳到“[G. 提交通告](#g-submitting-notices)。”） 与所有法律事务一样，就您的具体问题或情况咨询专业人员始终是最好的方式。 我们强烈建议您在采取任何可能影响您权利的行动之前这样做。 本指南不是法律意见，也不应作为法律意见。 diff --git a/translations/zh-CN/content/github/site-policy/github-community-guidelines.md b/translations/zh-CN/content/github/site-policy/github-community-guidelines.md index 665940c2ec..8215f39167 100644 --- a/translations/zh-CN/content/github/site-policy/github-community-guidelines.md +++ b/translations/zh-CN/content/github/site-policy/github-community-guidelines.md @@ -58,7 +58,7 @@ GitHub 社区的主要目的是协作处理软件项目。 我们希望人们能 - ### 破坏其他用户的体验 成为社区的一部分包括认识到您的行为如何影响他人，并与他人及其依赖的平台进行有意义和富有成效的互动。 不允许重复发布与主题无关的评论、开启空洞或无意义的议题或拉取请求，或者以不断破坏其他用户体验的方式使用任何其他平台功能等行为。 虽然我们鼓励维护人员根据个别情况调整自己的项目，但 GitHub 员工可能会对从事此类行为的帐户采取进一步的限制措施。 -- #### Impersonation You may not impersonate another person by copying their avatar, posting content under their email address, using a similar username or otherwise posing as someone else. 冒充是骚扰的一种形式。 +- #### 冒充 不得冒充他人，包括复制他人的头像、使用他人的电子邮件地址发布内容、使用相似用户名或其他冒充方式。 冒充是骚扰的一种形式。 - #### 人肉和侵犯隐私 不得发布他人的个人信息，例如个人、私人电子邮件地址、电话号码、实际地址、信用卡号码、社会保障/国民身份号码或密码。 根据具体情况，例如在恐吓或骚扰的情况下，我们可能会认为发布他人信息（例如未经当事人同意而拍摄或散发的照片或视频）是侵犯隐私的行为，特别是当此类材料会给当事人带来安全风险时。 diff --git a/translations/zh-CN/content/github/site-policy/github-data-protection-agreement.md b/translations/zh-CN/content/github/site-policy/github-data-protection-agreement.md new file mode 100644 index 0000000000..dbea19651e --- /dev/null +++ b/translations/zh-CN/content/github/site-policy/github-data-protection-agreement.md @@ -0,0 +1,974 @@ +--- +title: GitHub Data Protection Agreement +redirect_from: + - /github/site-policy/github-data-protection-addendum + - /github/site-policy-deprecated/github-data-protection-addendum + - /github/site-policy/github-data-protection-agreement-non-enterprise-customers +versions: + fpt: '*' +--- + +## 简介 + +The parties agree that this GitHub Data Protection Agreement (“**DPA**”) sets forth their obligations with respect to the processing and security of Personal Data and, where explicitly stated in the DPA Terms, Customer Data in connection with the Online Services provided by GitHub, Inc. (“**GitHub**”). The DPA (including its Appendix and Attachments) is between GitHub and any customer receiving Online Services from GitHub based on the GitHub Customer Agreement (“**Customer**”), and is incorporated by reference into the GitHub Customer Agreement. + +In the event of any conflict or inconsistency between the DPA Terms and any other terms in the GitHub Customer Agreement, the DPA Terms will prevail. The provisions of the DPA Terms supersede any conflicting provisions of the GitHub Privacy Statement that otherwise may apply to processing of Personal Data. For clarity, the Standard Contractual Clauses prevail over any other term of the DPA Terms. + +### Applicable DPA Terms and Updates + +#### Limits on Updates + +When Customer renews or purchases a new subscription to an Online Service, the then-current DPA Terms will apply and will not change during the term of that new subscription for that Online Service. + +#### New Features, Supplements, or Related Software + +Notwithstanding the foregoing limits on updates, when GitHub introduces features, supplements or related software that are new (i.e., that were not previously included with the subscription), GitHub may provide terms or make updates to the DPA that apply to Customer’s use of those new features, supplements or related software. If those terms include any material adverse changes to the DPA Terms, GitHub will provide Customer a choice to use the new features, supplements, or related software, without loss of existing functionality of a generally available Online Service. If Customer does not use the new features, supplements, or related software, the corresponding new terms will not apply. + +#### Government Regulation and Requirements + +Notwithstanding the foregoing limits on updates, GitHub may modify or terminate an Online Service in any country or jurisdiction where there is any current or future government requirement or obligation that (1) subjects GitHub to any regulation or requirement not generally applicable to businesses operating there, (2) presents a hardship for GitHub to continue operating the Online Service without modification, and/or (3) causes GitHub to believe the DPA Terms or the Online Service may conflict with any such requirement or obligation. + +### Electronic Notices + +GitHub may provide Customer with information and notices about Online Services electronically, including via email, or through a web site that GitHub identifies. Notice is given as of the date it is made available by GitHub. + +### Prior Versions + +The DPA Terms provide terms for Online Services that are currently available. For earlier versions of the DPA Terms, Customer may contact its reseller or GitHub Account Manager. + +## 定义 + +Capitalized terms used but not defined in this DPA will have the meanings provided in the GitHub Customer Agreement. The following defined terms are used in this DPA: + +“**CCPA**” means the California Consumer Privacy Act as set forth in Cal. 民事 Code §1798.100 et seq. and its implementing regulations. + +“**Customer Data**” means all data, including all text, sound, video, or image files, and software, that are provided to GitHub by, or on behalf of, Customer through use of the Online Service. + +“**Data Protection Requirements**” means the GDPR, Local EU/EEA Data Protection Laws, CCPA, and any applicable laws, regulations, and other legal requirements relating to (a) privacy and data security; and (b) the use, collection, retention, storage, security, disclosure, transfer, disposal, and other processing of any Personal Data. + +“**Diagnostic Data**” means data collected or obtained by GitHub from software that is locally installed by Customer in connection with the Online Service. Diagnostic Data may also be referred to as telemetry. Diagnostic Data does not include Customer Data, Service Generated Data, or Professional Services Data. + +“**DPA Terms**” means both the terms in this DPA and any Online Service-specific terms in the GitHub Customer Agreement that specifically supplement or modify the privacy and security terms in this DPA for a specific Online Service (or feature of an Online Service). In the event of any conflict or inconsistency between the DPA and such Online Service-specific terms, the Online Service-specific terms shall prevail as to the applicable Online Service (or feature of that Online Service). + +“**GDPR**” means Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation). In connection with the United Kingdom, “GDPR” means Regulation (EU) 2016/679 as transposed into national law of the United Kingdom by the UK European Union (Withdrawal) Act 2018 and amended by the UK Data Protection, Privacy and Electronic Communications (Amendments etc.) (EU Exit) Regulations 2019 (as may be amended from time to time). + +“**Local EU/EEA Data Protection Laws**” means any subordinate legislation and regulation implementing the GDPR. + +“**GDPR Related Terms**” means the terms in Attachment 3, under which GitHub makes binding commitments regarding its processing of Personal Data as required by Article 28 of the GDPR. + +“**GitHub Affiliate**” means any entity that directly or indirectly controls, is controlled by or is under common control with GitHub. + +“**GitHub Customer Agreement**” means the service or other agreement(s) entered into by Customer with GitHub for Online Services. + +“**GitHub Privacy Statement**” means the GitHub privacy statement available at https://docs.github.com/en/github/site-policy/github-privacy-statement. + +“**Online Service**” means any service or software provided by GitHub to Customer under the GitHub Customer Agreement agreed upon with Customer, including Previews, updates, patches, bug fixes, and technical support. + +“**Personal Data**” means any information relating to an identified or identifiable natural person. An identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person. + +“**Preview**” means Online Services provided for preview, evaluation, demonstration or trial purposes, or pre-release versions of the Online Services. + +“**Professional Services Data**” means all data, including all text, sound, video, image files or software, that are provided to GitHub, by or on behalf of a Customer (or that Customer authorizes GitHub to obtain from an Online Service) or otherwise obtained or processed by or on behalf of GitHub through an engagement with GitHub to obtain Professional Services. Professional Services Data includes Support Data. + +“**Service Generated Data**” means data generated or derived by GitHub through the operation of an Online Service. Service Generated Data does not include Customer Data, Diagnostic Data, or Professional Services Data. + +“**Standard Contractual Clauses**” means either of the following sets of Standard Contractual Clauses, as applicable in the individual case to the transfer of personal data according to the section of this DPA entitled “Data Transfers and Location” below: +- the Standard Contractual Clauses (MODULE TWO: Transfer controller to processor), dated 4 June 2021, for the transfer of personal data to third countries pursuant to Regulation (EU) 2016/679 of the European Parliament and of the Council, as described in Article 46 of the GDPR and approved by European Commission Implementing Decision (EU) 2021/91 (“Standard Contractual Clauses (EU/EEA)”). The Standard Contractual Clauses (EU/EEA) are set forth in Attachment 1. +- the Standard Contractual Clauses (Processors), dated 5 February 2010, for the transfer of personal data to processors established in third countries which do not ensure an adequate level of data protection, as described in Article 46 of the GDPR, approved by European Commission Decision 2010/87/EU and recognized by the regulatory or supervisory authorities of the United Kingdom for use in connection with data transfers from the United Kingdom (“Standard Contractual Clauses (UK)”). The Standard Contractual Clauses (UK) are set forth in Attachment 2. + +“**Subprocessor**” means other processors used by GitHub to process Personal Data on behalf of Customer in connection with the Online Services, as described in Article 28 of the GDPR. + +“**Support Data**” means all data, including all text, sound, video, image files, or software, that are provided to GitHub by or on behalf of Customer (or that Customer authorizes GitHub to obtain from an Online Service) through an engagement with GitHub to obtain technical support for Online Services covered under this agreement. Support Data is a subset of Professional Services Data. + +Lower case terms used but not defined in this DPA, such as “personal data breach”, “processing”, “controller”, “processor”, “profiling”, “personal data”, and “data subject” will have the same meaning as set forth in Article 4 of the GDPR, irrespective of whether GDPR applies. The terms “data importer” and “data exporter” have the meanings given in the Standard Contractual Clauses. + +For clarity, and as detailed above, data defined as Customer Data, Diagnostic Data, Service Generated Data, and Professional Services Data may contain Personal Data. For illustrative purposes, please see the chart inserted below: + +
    + personal_data_types +
    + +Above is a visual representation of the data types defined in the DPA. All Personal Data is processed as a part of one of the other data types (all of which also include non-personal data). Support Data is a sub-set of Professional Services Data. Except where explicitly stated otherwise, the DPA Terms exclusively apply to Personal Data. + +## General Terms + +### Compliance with Laws + +GitHub will comply with all laws and regulations applicable to its provision of the Online Services, including security breach notification law and Data Protection Requirements. However, GitHub is not responsible for compliance with any laws or regulations applicable to Customer or Customer’s industry that are not generally applicable to information technology service providers. GitHub does not determine whether Customer Data includes information subject to any specific law or regulation. All Security Incidents are subject to the Security Incident Notification terms below. + +Customer must comply with all laws and regulations applicable to its use of Online Services, including laws related to biometric data, confidentiality of communications, and Data Protection Requirements. Customer is responsible for determining whether the Online Services are appropriate for storage and processing of information subject to any specific law or regulation and for using the Online Services in a manner consistent with Customer’s legal and regulatory obligations. Customer is responsible for responding to any request from a third party regarding Customer’s use of an Online Service, such as a request to take down content under the U.S. Digital Millennium Copyright Act or other applicable laws. + +## 数据保护 + +Terms This section of the DPA includes the following subsections: +- 作用域 +- Nature of Data Processing; Ownership +- Disclosure of Processed Data +- Processing of Personal Data; GDPR +- Data Security +- Security Incident Notification +- Data Transfers and Location +- Data Retention and Deletion +- Processor Confidentiality Commitment +- Notice and Controls on Use of Subprocessors +- Educational Institutions +- CJIS Customer Agreement, HIPAA Business Associate, Biometric Data +- California Consumer Privacy Act (CCPA) +- How to Contact GitHub +- Appendix A – Security Measures + +### 作用域 + +The DPA Terms apply to all Online Services. + +Previews may employ lesser or different privacy and security measures than those typically present in the Online Services. Unless otherwise noted, Customer should not use Previews to process Personal Data or other data that is subject to legal or regulatory compliance requirements. The following terms in this DPA do not apply to Previews: Processing of Personal Data; GDPR, Data Security, and California Consumer Privacy Act. + +### Nature of Data Processing; Ownership + +Except as otherwise stated in the DPA Terms, GitHub will use and otherwise process Customer Data and Personal Data as described and subject to the limitations provided below (a) to provide Customer the Online Service in accordance with Customer’s documented instructions, and/or (b) for GitHub’s legitimate business operations incident to delivery of the Online Services to Customer. As between the parties, Customer retains all right, title and interest in and to Customer Data. GitHub acquires no rights in Customer Data other than the rights Customer grants to GitHub in this section. This paragraph does not affect GitHub’s rights in software or services GitHub licenses to Customer. + +#### Processing to Provide Customer the Online Services + +For purposes of this DPA, “to provide” an Online Service consists of: +- Delivering functional capabilities as licensed, configured, and used by Customer and its users, including providing personalized user experiences; +- Troubleshooting (e.g., preventing, detecting, and repairing problems); and +- Ongoing improvement (e.g., installing the latest updates and making improvements to user productivity, reliability, efficacy, and security). + +When providing Online Services, GitHub will use or otherwise process Personal Data only on Customer’s behalf and in accordance with Customer’s documented instructions. + +#### Processing for GitHub’s Legitimate Business Operations + +For purposes of this DPA, “GitHub’s legitimate business operations” consist of the following, each as incident to delivery of the Online Services to Customer: (1) billing and account management; (2) compensation (e.g., calculating employee commissions and partner incentives); (3) internal reporting and business modeling (e.g., forecasting, revenue, capacity planning, product strategy); (4) combatting fraud, abuse, cybercrime, or cyber-attacks that may affect GitHub or Online Services; (5) improving the core functionality of accessibility, privacy or energy-efficiency; (6) financial reporting and compliance with legal obligations (subject to the limitations on disclosure of Processed Data outlined below); (7) the creation or management of end user accounts and profiles by GitHub for individual users of Customer (except where Customer creates, manages or otherwise controls such end user accounts or profiles itself); and (8) other purposes pertaining to Personal Data not provided by Customer for storage in GitHub repositories or in connection with Professional Services. + +When processing for GitHub’s legitimate business operations, GitHub will not use or otherwise process Personal Data for: (a) user profiling, (b) advertising or similar commercial purposes, (c) data selling or brokering, or (d) any other purpose, other than for the purposes set out in this section. + +### Disclosure of Processed Data + +GitHub will not disclose or provide access to any Processed Data except: (1) as Customer directs; (2) as described in this DPA; or (3) as required by law. For purposes of this section, “Processed Data” means: (a) Customer Data; (b) Personal Data and (c) any other data processed by GitHub in connection with the Online Service that is Customer’s confidential information under the GitHub Customer Agreement. All processing of Processed Data is subject to GitHub’s obligation of confidentiality under the GitHub Customer Agreement. + +GitHub will not disclose or provide access to any Processed Data to law enforcement unless required by law. If law enforcement contacts GitHub with a demand for Processed Data, GitHub will attempt to redirect the law enforcement agency to request that data directly from Customer. If compelled to disclose or provide access to any Processed Data to law enforcement, GitHub will promptly notify Customer and provide a copy of the demand, unless legally prohibited from doing so. + +Upon receipt of any other third-party request for Processed Data, GitHub will promptly notify Customer unless prohibited by law. GitHub will reject the request unless required by law to comply. If the request is valid, GitHub will attempt to redirect the third party to request the data directly from Customer. + +GitHub will not provide any third party: (a) direct, indirect, blanket, or unfettered access to Processed Data; (b) platform encryption keys used to secure Processed Data or the ability to break such encryption; or (c) access to Processed Data if GitHub is aware that the data is to be used for purposes other than those stated in the third party’s request. + +In support of the above, GitHub may provide Customer’s basic contact information to the third party. + +### Processing of Personal Data; GDPR + +All Personal Data processed by GitHub in connection with the Online Services is obtained as part of either Customer Data, Professional Services Data (including Support Data), Diagnostic Data, or Service Generated Data. Personal Data provided to GitHub by, or on behalf of, Customer through use of the Online Service is also Customer Data. Pseudonymized identifiers may be included in Diagnostic Data or Service Generated Data and are also Personal Data. Any Personal Data pseudonymized, or de-identified but not anonymized, or Personal Data derived from Personal Data is also Personal Data. + +To the extent GitHub is a processor or subprocessor of Personal Data subject to the GDPR, the GDPR Related Terms in Attachment 3 govern that processing and the parties also agree to the following terms in this sub-section (“Processing of Personal Data; GDPR”): + +#### Processor and Controller Roles and Responsibilities + +Customer and GitHub agree that Customer is the controller of Personal Data and GitHub is the processor of such data, except (a) when Customer acts as a processor of Personal Data, in which case GitHub is a subprocessor; or (b) as stated otherwise in the GitHub Customer Agreement or this DPA. When GitHub acts as the processor or subprocessor of Personal Data, it will process Personal Data only on Customer’s behalf and in accordance with documented instructions from Customer. Customer agrees that its GitHub Customer Agreement (including the DPA Terms and any applicable updates), along with the product documentation and Customer’s use and configuration of features in the Online Services, are Customer’s complete documented instructions to GitHub for the processing of Personal Data. Information on use and configuration of the Online Services can be found at https://docs.github.com or a successor location. Any additional or alternate instructions must be agreed to according to the process for amending Customer’s GitHub Customer Agreement. In any instance where the GDPR applies and Customer is a processor, Customer warrants to GitHub that Customer’s instructions, including appointment of GitHub as a processor or subprocessor, have been authorized by the relevant controller. + +To the extent GitHub uses or otherwise processes Personal Data subject to the GDPR for GitHub’s legitimate business operations incident to delivery of the Online Services to Customer, GitHub will comply with the obligations of an independent data controller under GDPR for such use. GitHub is accepting the added responsibilities of a data “controller” under the GDPR for processing in connection with its legitimate business operations to: (a) act consistent with regulatory requirements, to the extent required under the GDPR; and (b) provide increased transparency to Customers and confirm GitHub’s accountability for such processing. GitHub employs safeguards to protect Personal Data in processing, including those identified in this DPA and those contemplated in Article 6(4) of the GDPR. With respect to processing of Personal Data under this paragraph, GitHub makes the commitments set forth in the Standard Contractual Clauses set forth in Attachment 1 or Attachment 2 (as applicable); for those purposes, (i) any GitHub disclosure of Personal Data, as described in Annex III to Attachment 1 or Appendix 3 to Attachment 2 (as applicable), that has been transferred in connection with GitHub’s legitimate business operations is deemed a “Relevant Disclosure” and (ii) the commitments in Annex III to Attachment 1 or Appendix 3 to Attachment 2 (as applicable) apply to such Personal Data. + +#### Processing Details + +The parties acknowledge and agree that: + +- **Subject Matter**. The subject-matter of the processing is limited to Personal Data within the scope of the section of this DPA entitled “Nature of Data Processing; Ownership” above and the GDPR. +- **Duration of the Processing**. The duration of the processing shall be in accordance with Customer instructions and the terms of the DPA. +- **Nature and Purpose of the Processing**. The nature and purpose of the processing shall be to provide the Online Service pursuant to Customer’s GitHub Customer Agreement and for GitHub’s legitimate business operations incident to delivery of the Online Service to Customer (as further described in the section of this DPA entitled “Nature of Data Processing; Ownership” above). +- **Categories of Data**. The types of Personal Data processed by GitHub when providing the Online Service include: (i) Personal Data that Customer elects to include in Customer Data or Professional Services Data (including, without limitation, Support Data); and (ii) those expressly identified in Article 4 of the GDPR that may be contained in Diagnostic Data or Service Generated Data. The types of Personal Data that Customer elects to include in Customer Data or Professional Services Data (including, without limitation, Support Data) may be any categories of Personal Data identified in records maintained by Customer acting as controller pursuant to Article 30 of the GDPR, including the categories of Personal Data set forth in Annex I to Attachment 1 or Appendix 1 to Attachment 2 (as applicable). +- Data Subjects. The categories of data subjects are Customer’s representatives and end users, such as employees, contractors, collaborators, and customers, and may include any other categories of data subjects as identified in records maintained by Customer acting as controller pursuant to Article 30 of the GDPR, including the categories of data subjects set forth in Annex I to Attachment 1 or Appendix 1 to Attachment 2 (as applicable). + +#### Data Subject Rights; Assistance with Requests + +GitHub will make available to Customer, in a manner consistent with the functionality of the Online Service and GitHub’s role as a processor of Personal Data of data subjects, the ability to fulfill data subject requests to exercise their rights under the GDPR. If GitHub receives a request from Customer’s data subject to exercise one or more of its rights under the GDPR in connection with an Online Service for which GitHub is a data processor or subprocessor, GitHub will redirect the data subject to make its request directly to Customer. Customer will be responsible for responding to any such request including, where necessary, by using the functionality of the Online Service. GitHub 应遵从客户的合理要求，以协助客户响应此类数据主体请求。 + +#### Records of Processing Activities + +To the extent the GDPR requires GitHub to collect and maintain records of certain information relating to Customer, Customer will, where requested, supply such information to GitHub and keep it accurate and up-to-date. GitHub may make any such information available to the supervisory authority if required by the GDPR. + +### Data Security + +GitHub will implement and maintain appropriate technical and organizational measures and security safeguards against accidental or unlawful destruction, or loss, alteration, unauthorized disclosure of or access to, Customer Data and Personal Data processed by GitHub on behalf and in accordance with the documented instructions of Customer in connection with the Online Services. GitHub will regularly monitor compliance with these measures and safeguards and will continue to take appropriate steps throughout the term of the GitHub Customer Agreement. Appendix A – Security Safeguards contains a description of the technical and organizational measures and security safeguards implemented by GitHub. + +Customer is solely responsible for making an independent determination as to whether the technical and organizational measures and security safeguards for an Online Service meet Customer’s requirements, including any of its security obligations under applicable Data Protection Requirements. Customer acknowledges and agrees that (taking into account the state of the art, the costs of implementation, and the nature, scope, context and purposes of the processing of its Customer Data and Personal Data as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons) the technical and organizational measures and security safeguards implemented and maintained by GitHub provide a level of security appropriate to the risk with respect to its Customer Data and Personal Data. Customer is responsible for implementing and maintaining privacy protections and security measures for components that Customer provides or controls. + +GitHub will provide security compliance reporting such as external SOC1, type 2 and SOC2, type2 audit reports upon Customer request. Customer agrees that any information and audit rights granted by the applicable Data Protection Requirements (including, where applicable, Article 28(3)(h) of the GDPR) will be satisfied by these compliance reports, and will otherwise only arise to the extent that GitHub's provision of a compliance report does not provide sufficient information, or to the extent that Customer must respond to a regulatory or supervisory authority audit or investigation. + +Should Customer be subject to a regulatory or supervisory authority audit or investigation or carry out an audit or investigation in response to a request by a regulatory or supervisory authority that requires participation from GitHub, and Customers’ obligations cannot reasonably be satisfied (where allowable by Customer’s regulators) through audit reports, documentation, or compliance information that GitHub makes generally available to its customers, then GitHub will promptly respond to Customer’s additional instructions and requests for information, in accordance with the following terms and conditions: + +- GitHub will provide access to relevant knowledgeable personnel, documentation, and application software. +- Customer and GitHub will mutually agree in a prior written agreement (email is acceptable) upon the scope, timing, duration, control and evidence requirements, provided that this requirement to agree will not permit GitHub to unreasonably delay its cooperation. +- Customer must ensure its regulator’s use of an independent, accredited third-party audit firm, during regular business hours, with reasonable advance written notice to GitHub, and subject to reasonable confidentiality procedures. Neither Customer, its regulators, nor its regulators’ delegates shall have access to any data from GitHub’s other customers or to GitHub systems or facilities not involved in the Online Services. +- Customer is responsible for all costs and fees related to GitHub’s cooperation with the regulatory audit of Customer, including all reasonable costs and fees for any and all time GitHub expends, in addition to the rates for services performed by GitHub. +- If the report generated from GitHub’s cooperation with the regulatory audit of Customer includes any findings pertaining to GitHub, Customer will share such report, findings, and recommended actions with GitHub where allowed by Customer’s regulators. + +### Security Incident Notification + +If GitHub becomes aware of a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Customer Data or Personal Data processed by GitHub on behalf and in accordance with the documented instructions of Customer in connection with the Online Services (each a "Security Incident"), GitHub will promptly and without undue delay (1) notify Customer of the Security Incident; (2) investigate the Security Incident and provide Customer with detailed information about the Security Incident; (3) take reasonable steps to mitigate the effects and to minimize any damage resulting from the Security Incident. + +Notification(s) of Security Incidents will be delivered to one or more of Customer's administrators by any means GitHub selects, including via email. It is Customer's sole responsibility to ensure it maintains accurate contact information with GitHub and that Customer's administrators monitor for and respond to any notifications. 客户独自负责履行事件通知法律下适用于客户的义务，并且履行与任何安全事件相关的任何第三方通知义务。 + +GitHub will make reasonable efforts to assist Customer in fulfilling Customer's obligation under GDPR Article 33 or other applicable law or regulations to notify the relevant regulatory or supervisory authority and individual data subjects about a Security Incident. + +GitHub’s notification of or response to a Security Incident under this section is not an acknowledgement by GitHub of any fault or liability with respect to the Security Incident. + +Customer must notify GitHub promptly about any possible misuse of its accounts or authentication credentials or any Security Incident related to an Online Service. + +### Data Transfers and Location + +Personal Data that GitHub processes on behalf and in accordance with the documented instructions of Customer in connection with the Online Services may not be transferred to, or stored and processed in a geographic location except in accordance with the DPA Terms and the safeguards provided below in this section. Taking into account such safeguards, Customer appoints GitHub to transfer Personal Data to the United States or any other country in which GitHub or its Subprocessors operate and to store and process Personal Data to provide the Online Services, except as may be described elsewhere in these DPA Terms. + +All transfers of Personal Data out of the European Union, European Economic Area, or Switzerland to provide the Online Services shall be governed by the Standard Contractual Clauses (EU/EEA) in Attachment 1. All transfers of Personal Data out of the United Kingdom to provide the Online Services shall be governed by the Standard Contractual Clauses (UK) in Attachment 2. For the purposes of the Standard Contractual Clauses (UK) in Attachment 2, references to the “European Union,” “EU,” “European Economic Area,” “EEA” or a “Member State” shall be interpreted to refer to the United Kingdom where reasonably necessary and appropriate to give full force and effect to the Standard Contractual Clauses (UK) with respect to transfers of Personal Data from the United Kingdom. This applies regardless of the fact that, effective January 31, 2020, the United Kingdom is no longer a Member State of the European Union or European Economic Area. + +GitHub will abide by the requirements of applicable European Union, European Economic Area, United Kingdom and Swiss data protection law, and other Data Protection Requirements, in each case regarding the transfer of Personal Data to recipients or jurisdictions outside such jurisdiction. All such transfers of Personal Data will, where applicable, be subject to appropriate safeguards as described in Article 46 of the GDPR and such transfers and safeguards will be documented according to Article 30(2) of the GDPR. + +Subject to the safeguards described above, GitHub may transfer, store and otherwise process Personal Data to or in jurisdictions and geographic locations worldwide as it, subject to its sole discretion, considers reasonably necessary in connection with the Online Services. + +### Data Retention and Deletion + +Upon Customer's reasonable request, unless prohibited by law, GitHub will return or destroy all Customer Data and Personal Data processed by GitHub on behalf and in accordance with the documented instructions of Customer in connection with the Online Services at all locations where it is stored within 30 days of the request, provided that it is no longer needed for providing the Online Services or the purposes for which a data subject had authorized the processing of their Personal Data. GitHub may retain Customer Data or Personal Data to the extent required by the applicable Data Protection Requirements or other applicable law, and only to the extent and for such period as required by the applicable Data Protection Requirements or other applicable law, provided that GitHub will ensure that the Customer Data or Personal Data is processed only as necessary for the purpose specified in the applicable Data Protection Requirements or other applicable law and no other purpose, and the Customer Data or Personal Data remains protected by the Applicable Data Protection Requirements or other applicable law. + +### Processor Confidentiality Commitment + +GitHub will ensure that its personnel engaged in the processing of Customer Data and Personal Data on behalf of Customer in connection with the Online Services (i) will process such data only on instructions from Customer or as described in this DPA, and (ii) will be obligated to maintain the confidentiality and security of such data even after their engagement ends. GitHub shall provide periodic and mandatory data privacy and security training and awareness to its employees with access to Customer Data and Personal Data in accordance with applicable Data Protection Requirements or other applicable law and industry standards. + +### Notice and Controls on Use of Subprocessors + +GitHub may hire Subprocessors to provide certain limited or ancillary services on its behalf. Customer consents to this engagement and to GitHub Affiliates as Subprocessors. The above authorizations will constitute Customer’s prior written consent to the subcontracting by GitHub of the processing of Personal Data if such consent is required under applicable law, the Standard Contractual Clauses or the GDPR Related Terms. + +GitHub is responsible for its Subprocessors’ compliance with GitHub’s obligations in this DPA. GitHub makes available information about Subprocessors on the GitHub website https://github.com/subprocessors (or a successor location). When engaging any Subprocessor, GitHub will ensure via a written contract that the Subprocessor may access and use Customer Data or Personal Data only to deliver the services GitHub has retained them to provide and is prohibited from using Customer Data or Personal Data for any other purpose. GitHub will ensure that Subprocessors are bound by written agreements that require them to provide at least the level of data protection required of GitHub by the DPA, including the limitations on disclosure of Personal Data. GitHub agrees to oversee the Subprocessors to ensure that these contractual obligations are met. + +From time to time, GitHub may engage new Subprocessors. GitHub will give Customer notice (by updating the website at https://github.com/github-subprocessors-list (or a successor location) and providing Customer with a mechanism to obtain notice of that update) of any new Subprocessor in advance of providing that Subprocessor with access to Customer Data. If GitHub engages a new Subprocessor for a new Online Service, GitHub will give Customer notice prior to availability of that Online Service. + +If Customer does not approve of a new Subprocessor, then Customer may terminate any subscription for the affected Online Service without penalty by providing, before the end of the relevant notice period, written notice of termination. Customer may also include an explanation of the grounds for non-approval together with the termination notice, in order to permit GitHub to re-evaluate any such new Subprocessor based on the applicable concerns. If the affected Online Service is part of a suite (or similar single purchase of services), then any termination will apply to the entire suite. After termination, GitHub will remove payment obligations for any subscriptions for the terminated Online Service from subsequent invoices to Customer or its reseller. + +### Educational Institutions +If Customer is an educational agency or institution subject to the regulations under the Family Educational Rights and Privacy Act, 20 U.S.C. § 1232g (FERPA), or similar state student or educational privacy laws (collectively “Educational Privacy Laws”), Customer shall not provide Personal Data covered by such Educational Privacy Laws to GitHub without obtaining GitHub’s prior, written and specific consent and entering into a separate agreement with GitHub governing the parties’ rights and obligations with respect to the processing of such Personal Data by GitHub in connection with the Online Services. + +Subject to the above, if Customer intends to provide to GitHub Personal Data covered by FERPA, the parties agree and acknowledge that, for the purposes of this DPA, GitHub is a “school official” with “legitimate educational interests” in the Personal Data, as those terms have been defined under FERPA and its implementing regulations. Customer understands that GitHub may possess limited or no contact information for Customer’s students and students’ parents. Consequently, Customer will be responsible for obtaining any student or parental consent for any end user’s use of the Online Services that may be required by applicable law and to convey notification on behalf of GitHub to students (or, with respect to a student under 18 years of age and not in attendance at a postsecondary institution, to the student’s parent) of any judicial order or lawfully-issued subpoena requiring the disclosure of Personal Data in GitHub’s possession as may be required under applicable law. + +### CJIS Customer Agreement, HIPAA Business Associate, Biometric Data + +Except with GitHub’s prior, written and specific consent, Customer shall not provide to GitHub any Personal Data + +- relating to criminal convictions and offenses or Personal Data collected or otherwise processed by Customer subject to or in connection with FBI Criminal Justice Information Services or the related Security Policy. +- constituting protected health information governed by the privacy, security, and breach notification rules issued by the United States Department of Health and Human Services, Parts 160 and 164 of Title 45 of the Code of Federal Regulations, established pursuant to the Health Insurance Portability and Accountability Act of 1996 (Public Law 104-191) or by state health or medical privacy laws. +- collected as part of a clinical trial or other biomedical research study subject to, or conducted in accordance with, the Federal Policy for the Protection of Human Subjects (Common Rule). +- covered by state, federal or foreign biometric privacy laws or otherwise constituting biometric information including information on an individual’s physical, physiological, biological or behavioral characteristics or information derived from such information that is used or intended to be used, singly or in combination with each other or with other information, to establish individual identity. + +### California Consumer Privacy Act (CCPA) / California Privacy Rights Act (CPRA) + +If and to the extent GitHub is processing Personal Data on behalf and in accordance with the documented instructions of Customer within the scope of the CCPA, GitHub makes the following additional commitments to Customer. GitHub will process the Personal Data on behalf of Customer and will not + +- sell the Personal Data as the term “selling” is defined in the CCPA. - share, rent, release, disclose, disseminate, make available, transfer or otherwise communicate orally, in writing or by electronic or other means, the Personal Data to a third party for cross-context behavioral advertising, whether or not for monetary or other valuable consideration, including transactions for cross-context behavioral advertising in which no money is exchanged. +- retain, use or disclose the Personal Data for any purpose other than for the business purposes specified in the DPA Terms and the GitHub Customer Agreement, including retaining, using or disclosing the Personal Data for a commercial purpose other than the business purposes specified in the DPA Terms or the GitHub Customer Agreement, or as otherwise permitted by the CCPA. +- retain, use or disclose the Personal Data outside of the direct business relationship with Customer. +- combine the Personal Data with personal information that it receives from or on behalf of a third party or collects from California residents, except that GitHub may combine Personal Data to perform any business purpose as permitted by the CCPA or any regulations adopted or issued under the CCPA. + +### How to Contact GitHub + +If Customer believes that GitHub is not adhering to its privacy or security commitments, Customer may contact customer support or use GitHub’s Privacy web form, located at https://support.github.com/contact/privacy. GitHub’s mailing address is: + +**GitHub Privacy**
    GitHub, Inc.
    88 Colin P. Kelly Jr. Street
    San Francisco, California 94107 USA
    + +GitHub B.V. is GitHub’s data protection representative for the European Economic Area. The privacy representative of GitHub B.V. can be reached at the following address: + +**GitHub B.V.**
    Vijzelstraat 68-72
    1017 HL Amsterdam
    The Netherlands
    + +

    Appendix A – Security Safeguards

    + +GitHub has implemented and will maintain for Customer Data and Personal Data processed by GitHub on behalf and in accordance with the documented instructions of Customer in connection with GitHub services the following technical and organizational measures and security safeguards, which in conjunction with the security commitments in this DPA (including the GDPR Related Terms), are GitHub’s only responsibility with respect to the security of that data: + +| Domain | Practices | +| ---------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Organization of Information Security | **Security Ownership**. GitHub has appointed one or more security officers responsible for coordinating and monitoring the security policies and procedures.

    **Security Roles and Responsibilities**. GitHub personnel with access to Customer Data and Personal Data are subject to confidentiality obligations.

    **Risk Management Program**. GitHub performs an annual risk assessment.
    GitHub retains its security documents pursuant to its retention requirements after they are no longer in effect.

    **Vendor Management**. GitHub has a vendor risk assessment process, vendor contract clauses and additional data protection agreements with vendors. | +| Asset Management | **Asset Inventory**. GitHub maintains an inventory of all media on which Customer Data and Personal Data is stored. Access to the inventories of such media is restricted to GitHub personnel authorized to have such access.

    **Asset Handling**
    - GitHub classifies Customer Data and Personal Data to help identify it and to allow for access to it to be appropriately restricted.
    - GitHub communicates employee responsibility and accountability for data protection up to and including cause for termination.
    GitHub personnel must obtain GitHub authorization prior to remotely accessing Customer Data and Personal Data or processing Customer Data and Personal Data outside GitHub’s facilities. | +| Human Resources Security | **Security Training**. GitHub requires all new hires to complete security and privacy awareness training as part of initial on-boarding. Participation in annual training is required for all employees to provide a baseline for security and privacy basics. | +| Physical and Environmental Security | **Physical Access to Facilities**. GitHub limits access to facilities where information systems that process Customer Data and Personal Data are located to identified authorized individuals.

    **Physical Access to Components**. GitHub maintains records of the incoming and outgoing media containing Customer Data, including the kind of media, the authorized sender/recipients, date and time, the number of media and the types of Customer Data and Personal Data they contain.

    **Protection from Disruptions**. GitHub uses a variety of industry standard systems to protect against loss of data due to power supply failure or line interference.

    **Component Disposal**. GitHub uses industry standard processes to delete Customer Data and Personal Data when it is no longer needed. | +| Communications and Operations Management | **Operational Policy**. GitHub maintains security documents describing its security measures and the relevant procedures and responsibilities of its personnel who have access to Customer Data.

    **Data Recovery Procedures**
    - On an ongoing basis, but in no case less frequently than once a week (unless no Customer Data and Personal Data has been updated during that period), GitHub maintains multiple copies of Customer Data and Personal Data from which Customer Data and Personal Data can be recovered.
    - GitHub stores copies of Customer Data and Personal Data and data recovery procedures in a different place from where the primary computer equipment processing the Customer Data and Personal Data is located.
    - GitHub has specific procedures in place governing access to copies of Customer Data.
    - GitHub logs data restoration efforts, including the person responsible, the description of the restored data and where applicable, the person responsible and which data (if any) had to be input manually in the data recovery process.

    **Malicious Software**. GitHub has threat detection controls to help identify and respond to anomalous or suspicious access to Customer Data, including malicious software originating from public networks.

    **Data Beyond Boundaries**
    - GitHub encrypts, or enables Customer to encrypt, Customer Data and Personal Data that is transmitted over public networks.
    - GitHub restricts access to Customer Data and Personal Data in media leaving its facilities.

    **Event Logging**. GitHub logs, or enables Customer to log, access and use of information systems containing Customer Data, registering the access ID, time, authorization granted or denied, and relevant activity. | +| Access Control | **Access Policy**. GitHub maintains a record of security privileges of individuals having access to Customer Data.

    **Access Authorization**
    - GitHub maintains and updates a record of personnel authorized to access GitHub systems that contain Customer Data.
    - GitHub identifies those personnel who may grant, alter or cancel authorized access to data and resources.
    - GitHub ensures that where more than one individual has access to systems containing Customer Data, the individuals have separate identifiers/log-ins where technically and architecturally feasible, and commercially reasonable.

    **Least Privilege**
    - Technical support personnel are only permitted to have access to Customer Data and Personal Data when needed.
    - GitHub restricts access to Customer Data and Personal Data to only those individuals who require such access to perform their job function. GitHub employees are only granted access to production systems based on their role within the organization.

    **Integrity and Confidentiality**

    - GitHub instructs GitHub personnel to disable administrative sessions when computers are left unattended.
    - GitHub stores passwords such that they are encrypted or unintelligible while they are in force.

    **Authentication**
    - GitHub uses industry standard practices to identify and authenticate users who attempt to access information systems.
    - Where authentication mechanisms are based solely on passwords, GitHub requires the password to be at least eight characters long.
    - GitHub ensures that de-activated or expired employee identifiers are not granted to other individuals.
    - GitHub monitors, or enables Customer to monitor, repeated attempts to gain access to the information system using an invalid password.
    - GitHub maintains industry standard procedures to deactivate passwords that have been corrupted or inadvertently disclosed.
    - GitHub uses industry standard password protection practices, including practices designed to maintain the confidentiality and integrity of passwords when they are assigned and distributed, and during storage.

    **Network Design**. GitHub has controls to ensure no systems storing Customer Data and Personal Data are part of the same logical network used for GitHub business operations. | +| Information Security Incident Management | **Incident Response Process**
    - GitHub maintains a record of security incidents with a description of the incidents, the time period, the consequences of the breach, the name of the reporter, and to whom the incident was reported, and details regarding the handling of the incident.
    - In the event that GitHub Security confirms or reasonably suspects that a GitHub.com customer is affected by a data breach, we will notify the customer without undue delay
    - GitHub tracks, or enables Customer to track, disclosures of Customer Data, including what data has been disclosed, to whom, and at what time.

    **Service Monitoring**. GitHub employs a wide range of continuous monitoring solutions for preventing, detecting, and mitigating attacks to the site. | +| Business Continuity Management | - GitHub maintains emergency and contingency plans for the facilities in which GitHub information systems that process Customer Data and Personal Data are located.
    - GitHub’s redundant storage and its procedures for recovering data are designed to attempt to reconstruct Customer Data and Personal Data in its original or last-replicated state from before the time it was lost or destroyed. | + +

    Attachment 1 - The Standard Contractual Clauses (EU/EEA)

    + +### Controller to Processor + +#### SECTION I + +##### Clause 1 + +**Purpose and scope** + +
      +
    1. The purpose of these standard contractual clauses is to ensure compliance with the requirements of Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data (General Data Protection Regulation) for the transfer of personal data to a third country.
      2. +
    2. The Parties: +
        +
      1. the natural or legal person(s), public authority/ies, agency/ies or other body/ies (hereinafter ‘entity/ies’) transferring the personal data, as listed in Annex I.A (hereinafter each ‘data exporter’), and
        2. +
      2. the entity/ies in a third country receiving the personal data from the data exporter, directly or indirectly via another entity also Party to these Clauses, as listed in Annex I.A (hereinafter each ‘data importer’)
        3. +
      + have agreed to these standard contractual clauses (hereinafter: ‘Clauses’).
      3. +
    3. These Clauses apply with respect to the transfer of personal data as specified in Annex I.B.
      4. +
    4. The Appendix to these Clauses containing the Annexes referred to therein forms an integral part of these Clauses.
      5. +
    + +##### Clause 2 + +**Effect and invariability of the Clauses** +
      +
    1. These Clauses set out appropriate safeguards, including enforceable data subject rights and effective legal remedies, pursuant to Article 46(1) and Article 46(2)(c) of Regulation (EU) 2016/679 and, with respect to data transfers from controllers to processors and/or processors to processors, standard contractual clauses pursuant to Article 28(7) of Regulation (EU) 2016/679, provided they are not modified, except to select the appropriate Module(s) or to add or update information in the Appendix. This does not prevent the Parties from including the standard contractual clauses laid down in these Clauses in a wider contract and/or to add other clauses or additional safeguards, provided that they do not contradict, directly or indirectly, these Clauses or prejudice the fundamental rights or freedoms of data subjects.
      2. +
    2. These Clauses are without prejudice to obligations to which the data exporter is subject by virtue of Regulation (EU) 2016/679.
      3. +
    + +##### Clause 3 + +**Third-party beneficiaries** + +
      +
    1. Data subjects may invoke and enforce these Clauses, as third-party beneficiaries, against the data exporter and/or data importer, with the following exceptions:
      2. +
        +
      1. Clause 1, Clause 2, Clause 3, Clause 6, Clause 7;
        2. +
      2. Clause 8.1(b), 8.9(a), (c), (d) and (e);
        3. +
      3. Clause 9(a), (c), (d) and (e);
        4. +
      4. Clause 12(a), (d) and (f);
        5. +
      5. Clause 13;
        6. +
      6. Clause 15.1(c), (d) and (e);
        7. +
      7. Clause 16(e);
        8. +
      8. Clause 18(a) and (b).
        9. +
      +
    2. Paragraph (a) is without prejudice to rights of data subjects under Regulation (EU) 2016/679.
      3. +
    + +##### Clause 4 + +**Interpretation** + +
      +
    1. Where these Clauses use terms that are defined in Regulation (EU) 2016/679, those terms shall have the same meaning as in that Regulation.
      2. +
    2. These Clauses shall be read and interpreted in the light of the provisions of Regulation (EU) 2016/679.
      3. +
    3. These Clauses shall not be interpreted in a way that conflicts with rights and obligations provided for in Regulation (EU) 2016/679.
      4. +
    + +##### Clause 5 + +**Hierarchy** + +In the event of a contradiction between these Clauses and the provisions of related agreements between the Parties, existing at the time these Clauses are agreed or entered into thereafter, these Clauses shall prevail. + +##### Clause 6 + +**Description of the transfer(s)** + +The details of the transfer(s), and in particular the categories of personal data that are transferred and the purpose(s) for which they are transferred, are specified in Annex I.B. + +##### Clause 7 + +**Docking clause** + +
      +
    1. An entity that is not a Party to these Clauses may, with the agreement of the Parties, accede to these Clauses at any time, either as a data exporter or as a data importer, by completing the Appendix and signing Annex I.A.
      2. +
    2. Once it has completed the Appendix and signed Annex I.A, the acceding entity shall become a Party to these Clauses and have the rights and obligations of a data exporter or data importer in accordance with its designation in Annex I.A.
      3. +
    3. The acceding entity shall have no rights or obligations arising under these Clauses from the period prior to becoming a Party.
      4. +
    + +#### SECTION II – OBLIGATIONS OF THE PARTIES + +##### Clause 8 + +**Data protection safeguards** + +The data exporter warrants that it has used reasonable efforts to determine that the data importer is able, through the implementation of appropriate technical and organisational measures, to satisfy its obligations under these Clauses. + +**8.1 Instructions**
      +
    1. The data importer shall process the personal data only on documented instructions from the data exporter. The data exporter may give such instructions throughout the duration of the contract.
      2. +
    2. The data importer shall immediately inform the data exporter if it is unable to follow those instructions.
      3. +
    + +**8.2 Purpose limitation** + +The data importer shall process the personal data only for the specific purpose(s) of the transfer, as set out in Annex I.B, unless on further instructions from the data exporter. + +**8.3 Transparency** + +On request, the data exporter shall make a copy of these Clauses, including the Appendix as completed by the Parties, available to the data subject free of charge. To the extent necessary to protect business secrets or other confidential information, including the measures described in Annex II and personal data, the data exporter may redact part of the text of the Appendix to these Clauses prior to sharing a copy, but shall provide a meaningful summary where the data subject would otherwise not be able to understand the its content or exercise his/her rights. On request, the Parties shall provide the data subject with the reasons for the redactions, to the extent possible without revealing the redacted information. This Clause is without prejudice to the obligations of the data exporter under Articles 13 and 14 of Regulation (EU) 2016/679. + +**8.4 Accuracy** + +If the data importer becomes aware that the personal data it has received is inaccurate, or has become outdated, it shall inform the data exporter without undue delay. In this case, the data importer shall cooperate with the data exporter to erase or rectify the data. + +**8.5 Duration of processing and erasure or return of data** + +Processing by the data importer shall only take place for the duration specified in Annex I.B. After the end of the provision of the processing services, the data importer shall, at the choice of the data exporter, delete all personal data processed on behalf of the data exporter and certify to the data exporter that it has done so, or return to the data exporter all personal data processed on its behalf and delete existing copies. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit return or deletion of the personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process it to the extent and for as long as required under that local law. This is without prejudice to Clause 14, in particular the requirement for the data importer under Clause 14(e) to notify the data exporter throughout the duration of the contract if it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under Clause 14(a). + +**8.6 Security of processing** + +
      +
    1. The data importer and, during transmission, also the data exporter shall implement appropriate technical and organisational measures to ensure the security of the data, including protection against a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access to that data (hereinafter ‘personal data breach’). In assessing the appropriate level of security, the Parties shall take due account of the state of the art, the costs of implementation, the nature, scope, context and purpose(s) of processing and the risks involved in the processing for the data subjects. The Parties shall in particular consider having recourse to encryption or pseudonymisation, including during transmission, where the purpose of processing can be fulfilled in that manner. In case of pseudonymisation, the additional information for attributing the personal data to a specific data subject shall, where possible, remain under the exclusive control of the data exporter. In complying with its obligations under this paragraph, the data importer shall at least implement the technical and organisational measures specified in Annex II. The data importer shall carry out regular checks to ensure that these measures continue to provide an appropriate level of security.
      2. +
    2. The data importer shall grant access to the personal data to members of its personnel only to the extent strictly necessary for the implementation, management and monitoring of the contract. It shall ensure that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.
      3. +
    3. In the event of a personal data breach concerning personal data processed by the data importer under these Clauses, the data importer shall take appropriate measures to address the breach, including measures to mitigate its adverse effects. The data importer shall also notify the data exporter without undue delay after having become aware of the breach. Such notification shall contain the details of a contact point where more information can be obtained, a description of the nature of the breach (including, where possible, categories and approximate number of data subjects and personal data records concerned), its likely consequences and the measures taken or proposed to address the breach including, where appropriate, measures to mitigate its possible adverse effects. Where, and in so far as, it is not possible to provide all information at the same time, the initial notification shall contain the information then available and further information shall, as it becomes available, subsequently be provided without undue delay.
      4. +
    4. The data importer shall cooperate with and assist the data exporter to enable the data exporter to comply with its obligations under Regulation (EU) 2016/679, in particular to notify the competent supervisory authority and the affected data subjects, taking into account the nature of processing and the information available to the data importer.
      5. +
    + +**8.7 Sensitive data** + +Where the transfer involves personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic data, or biometric data for the purpose of uniquely identifying a natural person, data concerning health or a person’s sex life or sexual orientation, or data relating to criminal convictions and offences (hereinafter ‘sensitive data’), the data importer shall apply the specific restrictions and/or additional safeguards described in Annex I.B. + +**8.8 Onward transfers** + +The data importer shall only disclose the personal data to a third party on documented instructions from the data exporter. In addition, the data may only be disclosed to a third party located outside the European Union (1) (in the same country as the data importer or in another third country, hereinafter ‘onward transfer’) if the third party is or agrees to be bound by these Clauses, under the appropriate Module, or if: + +
      +
    1. the onward transfer is to a country benefitting from an adequacy decision pursuant to Article 45 of Regulation (EU) 2016/679 that covers the onward transfer;
      2. +
    2. the third party otherwise ensures appropriate safeguards pursuant to Articles 46 or 47 Regulation of (EU) 2016/679 with respect to the processing in question;
      3. +
    3. the onward transfer is necessary for the establishment, exercise or defence of legal claims in the context of specific administrative, regulatory or judicial proceedings; or
      4. +
    4. the onward transfer is necessary in order to protect the vital interests of the data subject or of another natural person.

      5. + Any onward transfer is subject to compliance by the data importer with all the other safeguards under these Clauses, in particular purpose limitation. +
    + +**8.9 Documentation and compliance** + +
      +
    1. The data importer shall promptly and adequately deal with enquiries from the data exporter that relate to the processing under these Clauses.
      2. +
    2. The Parties shall be able to demonstrate compliance with these Clauses. In particular, the data importer shall keep appropriate documentation on the processing activities carried out on behalf of the data exporter.
      3. +
    3. The data importer shall make available to the data exporter all information necessary to demonstrate compliance with the obligations set out in these Clauses and at the data exporter’s request, allow for and contribute to audits of the processing activities covered by these Clauses, at reasonable intervals or if there are indications of non-compliance. In deciding on a review or audit, the data exporter may take into account relevant certifications held by the data importer.
      4. +
    4. The data exporter may choose to conduct the audit by itself or mandate an independent auditor. Audits may include inspections at the premises or physical facilities of the data importer and shall, where appropriate, be carried out with reasonable notice.
      5. +
    5. The Parties shall make the information referred to in paragraphs (b) and (c), including the results of any audits, available to the competent supervisory authority on request.
      6. +
    + +##### Clause 9 + +**Use of sub-processors** + +
      +
    1. GENERAL WRITTEN AUTHORISATION The data importer has the data exporter’s general authorisation for the engagement of sub-processor(s) from an agreed list. The data importer shall specifically inform the data exporter in writing of any intended changes to that list through the addition or replacement of sub-processors at least 90 days in advance, thereby giving the data exporter sufficient time to be able to object to such changes prior to the engagement of the sub-processor(s). The data importer shall provide the data exporter with the information necessary to enable the data exporter to exercise its right to object.
      2. +
    2. Where the data importer engages a sub-processor to carry out specific processing activities (on behalf of the data exporter), it shall do so by way of a written contract that provides for, in substance, the same data protection obligations as those binding the data importer under these Clauses, including in terms of third-party beneficiary rights for data subjects.(2) The Parties agree that, by complying with this Clause, the data importer fulfils its obligations under Clause 8.8. The data importer shall ensure that the sub-processor complies with the obligations to which the data importer is subject pursuant to these Clauses.
      3. +
    3. The data importer shall provide, at the data exporter’s request, a copy of such a sub-processor agreement and any subsequent amendments to the data exporter. To the extent necessary to protect business secrets or other confidential information, including personal data, the data importer may redact the text of the agreement prior to sharing a copy.
      4. +
    4. The data importer shall remain fully responsible to the data exporter for the performance of the sub-processor’s obligations under its contract with the data importer. The data importer shall notify the data exporter of any failure by the sub-processor to fulfil its obligations under that contract.
      5. +
    5. The data importer shall agree a third-party beneficiary clause with the sub-processor whereby – in the event the data importer has factually disappeared, ceased to exist in law or has become insolvent – the data exporter shall have the right to terminate the sub-processor contract and to instruct the sub-processor to erase or return the personal data.
      6. +
    + +##### Clause 10 + +**Data subject rights** + +
      +
    1. The data importer shall promptly notify the data exporter of any request it has received from a data subject. It shall not respond to that request itself unless it has been authorised to do so by the data exporter.
      2. +
    2. The data importer shall assist the data exporter in fulfilling its obligations to respond to data subjects’ requests for the exercise of their rights under Regulation (EU) 2016/679. In this regard, the Parties shall set out in Annex II the appropriate technical and organisational measures, taking into account the nature of the processing, by which the assistance shall be provided, as well as the scope and the extent of the assistance required.
      3. +
    3. In fulfilling its obligations under paragraphs (a) and (b), the data importer shall comply with the instructions from the data exporter.
      4. +
    + +##### Clause 11 + +**Redress** + +
      +
    1. The data importer shall inform data subjects in a transparent and easily accessible format, through individual notice or on its website, of a contact point authorised to handle complaints. It shall deal promptly with any complaints it receives from a data subject.
      2. +
    2. In case of a dispute between a data subject and one of the Parties as regards compliance with these Clauses, that Party shall use its best efforts to resolve the issue amicably in a timely fashion. The Parties shall keep each other informed about such disputes and, where appropriate, cooperate in resolving them.
      3. +
    3. Where the data subject invokes a third-party beneficiary right pursuant to Clause 3, the data importer shall accept the decision of the data subject to:
      4. +
        +
      1. lodge a complaint with the supervisory authority in the Member State of his/her habitual residence or place of work, or the competent supervisory authority pursuant to Clause 13;
        2. +
      2. refer the dispute to the competent courts within the meaning of Clause 18.
        3. +
      +
    4. The Parties accept that the data subject may be represented by a not-for-profit body, organisation or association under the conditions set out in Article 80(1) of Regulation (EU) 2016/679.
      5. +
    5. The data importer shall abide by a decision that is binding under the applicable EU or Member State law.
      6. +
    6. The data importer agrees that the choice made by the data subject will not prejudice his/her substantive and procedural rights to seek remedies in accordance with applicable laws.
      7. +
    + +##### Clause 12 + +**Liability** + +
      +
    1. Each Party shall be liable to the other Party/ies for any damages it causes the other Party/ies by any breach of these Clauses.
      2. +
    2. The data importer shall be liable to the data subject, and the data subject shall be entitled to receive compensation, for any material or non-material damages the data importer or its sub-processor causes the data subject by breaching the third-party beneficiary rights under these Clauses.
      3. +
    3. Notwithstanding paragraph (b), the data exporter shall be liable to the data subject, and the data subject shall be entitled to receive compensation, for any material or non-material damages the data exporter or the data importer (or its sub-processor) causes the data subject by breaching the third-party beneficiary rights under these Clauses. This is without prejudice to the liability of the data exporter and, where the data exporter is a processor acting on behalf of a controller, to the liability of the controller under Regulation (EU) 2016/679 or Regulation (EU) 2018/1725, as applicable.
      4. +
    4. The Parties agree that if the data exporter is held liable under paragraph (c) for damages caused by the data importer (or its sub-processor), it shall be entitled to claim back from the data importer that part of the compensation corresponding to the data importer’s responsibility for the damage.
      5. +
    5. Where more than one Party is responsible for any damage caused to the data subject as a result of a breach of these Clauses, all responsible Parties shall be jointly and severally liable and the data subject is entitled to bring an action in court against any of these Parties.
      6. +
    6. The Parties agree that if one Party is held liable under paragraph (e), it shall be entitled to claim back from the other Party/ies that part of the compensation corresponding to its/their responsibility for the damage.
      7. +
    7. The data importer may not invoke the conduct of a sub-processor to avoid its own liability.
      8. +
    + +##### Clause 13 + +**Supervision** + +
      +
    1. [Where the data exporter is established in an EU Member State:] The supervisory authority with responsibility for ensuring compliance by the data exporter with Regulation (EU) 2016/679 as regards the data transfer, as indicated in Annex I.C, shall act as competent supervisory authority.

      + [Where the data exporter is not established in an EU Member State, but falls within the territorial scope of application of Regulation (EU) 2016/679 in accordance with its Article 3(2) and has appointed a representative pursuant to Article 27(1) of Regulation (EU) 2016/679:] The supervisory authority of the Member State in which the representative within the meaning of Article 27(1) of Regulation (EU) 2016/679 is established, as indicated in Annex I.C, shall act as competent supervisory authority.

      + [Where the data exporter is not established in an EU Member State, but falls within the territorial scope of application of Regulation (EU) 2016/679 in accordance with its Article 3(2) without however having to appoint a representative pursuant to Article 27(2) of Regulation (EU) 2016/679:] The supervisory authority of one of the Member States in which the data subjects whose personal data is transferred under these Clauses in relation to the offering of goods or services to them, or whose behaviour is monitored, are located, as indicated in Annex I.C, shall act as competent supervisory authority.

      2. +
    2. The data importer agrees to submit itself to the jurisdiction of and cooperate with the competent supervisory authority in any procedures aimed at ensuring compliance with these Clauses. In particular, the data importer agrees to respond to enquiries, submit to audits and comply with the measures adopted by the supervisory authority, including remedial and compensatory measures. It shall provide the supervisory authority with written confirmation that the necessary actions have been taken.
      3. +
    + +#### SECTION III – LOCAL LAWS AND OBLIGATIONS IN CASE OF ACCESS BY PUBLIC AUTHORITIES + +##### Clause 14 + +**Local laws and practices affecting compliance with the Clauses** + +
      +
    1. The Parties warrant that they have no reason to believe that the laws and practices in the third country of destination applicable to the processing of the personal data by the data importer, including any requirements to disclose personal data or measures authorising access by public authorities, prevent the data importer from fulfilling its obligations under these Clauses. This is based on the understanding that laws and practices that respect the essence of the fundamental rights and freedoms and do not exceed what is necessary and proportionate in a democratic society to safeguard one of the objectives listed in Article 23(1) of Regulation (EU) 2016/679, are not in contradiction with these Clauses.
      2. +
    2. The Parties declare that in providing the warranty in paragraph (a), they have taken due account in particular of the following elements:
      3. +
        +
      1. the specific circumstances of the transfer, including the length of the processing chain, the number of actors involved and the transmission channels used; intended onward transfers; the type of recipient; the purpose of processing; the categories and format of the transferred personal data; the economic sector in which the transfer occurs; the storage location of the data transferred;
        2. +
      2. the laws and practices of the third country of destination– including those requiring the disclosure of data to public authorities or authorising access by such authorities – relevant in light of the specific circumstances of the transfer, and the applicable limitations and safeguards (3);
        3. +
      3. any relevant contractual, technical or organisational safeguards put in place to supplement the safeguards under these Clauses, including measures applied during transmission and to the processing of the personal data in the country of destination.
        4. +
      +
    3. The data importer warrants that, in carrying out the assessment under paragraph (b), it has made its best efforts to provide the data exporter with relevant information and agrees that it will continue to cooperate with the data exporter in ensuring compliance with these Clauses.
      4. +
    4. The Parties agree to document the assessment under paragraph (b) and make it available to the competent supervisory authority on request.
      5. +
    5. The data importer agrees to notify the data exporter promptly if, after having agreed to these Clauses and for the duration of the contract, it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under paragraph (a), including following a change in the laws of the third country or a measure (such as a disclosure request) indicating an application of such laws in practice that is not in line with the requirements in paragraph (a).
      6. +
    6. Following a notification pursuant to paragraph (e), or if the data exporter otherwise has reason to believe that the data importer can no longer fulfil its obligations under these Clauses, the data exporter shall promptly identify appropriate measures (e.g. technical or organisational measures to ensure security and confidentiality) to be adopted by the data exporter and/or data importer to address the situation. The data exporter shall suspend the data transfer if it considers that no appropriate safeguards for such transfer can be ensured, or if instructed by the competent supervisory authority to do so. In this case, the data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses. If the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise. Where the contract is terminated pursuant to this Clause, Clause 16(d) and (e) shall apply.
      7. +
    + +##### Clause 15 + +**Obligations of the data importer in case of access by public authorities** + +**15.1 Notification** + +
      +
    1. The data importer agrees to notify the data exporter and, where possible, the data subject promptly (if necessary with the help of the data exporter) if it:
      2. +
        +
      1. receives a legally binding request from a public authority, including judicial authorities, under the laws of the country of destination for the disclosure of personal data transferred pursuant to these Clauses; such notification shall include information about the personal data requested, the requesting authority, the legal basis for the request and the response provided; or
        2. +
      2. becomes aware of any direct access by public authorities to personal data transferred pursuant to these Clauses in accordance with the laws of the country of destination; such notification shall include all information available to the importer.
        3. +
      +
    2. If the data importer is prohibited from notifying the data exporter and/or the data subject under the laws of the country of destination, the data importer agrees to use its best efforts to obtain a waiver of the prohibition, with a view to communicating as much information as possible, as soon as possible. The data importer agrees to document its best efforts in order to be able to demonstrate them on request of the data exporter.
      3. +
    3. Where permissible under the laws of the country of destination, the data importer agrees to provide the data exporter, at regular intervals for the duration of the contract, with as much relevant information as possible on the requests received (in particular, number of requests, type of data requested, requesting authority/ies, whether requests have been challenged and the outcome of such challenges, etc.).
      4. +
    4. The data importer agrees to preserve the information pursuant to paragraphs (a) to (c) for the duration of the contract and make it available to the competent supervisory authority on request.
      5. +
    5. Paragraphs (a) to (c) are without prejudice to the obligation of the data importer pursuant to Clause 14(e) and Clause 16 to inform the data exporter promptly where it is unable to comply with these Clauses.
      6. +
    + +**15.2 Review of legality and data minimisation** + +
      +
    1. The data importer agrees to review the legality of the request for disclosure, in particular whether it remains within the powers granted to the requesting public authority, and to challenge the request if, after careful assessment, it concludes that there are reasonable grounds to consider that the request is unlawful under the laws of the country of destination, applicable obligations under international law and principles of international comity. The data importer shall, under the same conditions, pursue possibilities of appeal. When challenging a request, the data importer shall seek interim measures with a view to suspending the effects of the request until the competent judicial authority has decided on its merits. It shall not disclose the personal data requested until required to do so under the applicable procedural rules. These requirements are without prejudice to the obligations of the data importer under Clause 14(e).
      2. +
    2. The data importer agrees to document its legal assessment and any challenge to the request for disclosure and, to the extent permissible under the laws of the country of destination, make the documentation available to the data exporter. It shall also make it available to the competent supervisory authority on request.
      3. +
    3. The data importer agrees to provide the minimum amount of information permissible when responding to a request for disclosure, based on a reasonable interpretation of the request.
      4. +
    + +#### SECTION IV – FINAL PROVISIONS + +##### Clause 16 + +**Non-compliance with the Clauses and termination** + +
      +
    1. The data importer shall promptly inform the data exporter if it is unable to comply with these Clauses, for whatever reason.
      2. +
    2. In the event that the data importer is in breach of these Clauses or unable to comply with these Clauses, the data exporter shall suspend the transfer of personal data to the data importer until compliance is again ensured or the contract is terminated. This is without prejudice to Clause 14(f).
      3. +
    3. The data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses, where:
      4. +
        +
      1. the data exporter has suspended the transfer of personal data to the data importer pursuant to paragraph (b) and compliance with these Clauses is not restored within a reasonable time and in any event within one month of suspension;
        2. +
      2. the data importer is in substantial or persistent breach of these Clauses; or
        3. +
      3. the data importer fails to comply with a binding decision of a competent court or supervisory authority regarding its obligations under these Clauses.
        4. +

      + In these cases, it shall inform the competent supervisory authority of such non-compliance. Where the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise. +
    4. Personal data that has been transferred prior to the termination of the contract pursuant to paragraph (c) shall at the choice of the data exporter immediately be returned to the data exporter or deleted in its entirety. The same shall apply to any copies of the data. The data importer shall certify the deletion of the data to the data exporter. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit the return or deletion of the transferred personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process the data to the extent and for as long as required under that local law.
      5. +
    5. Either Party may revoke its agreement to be bound by these Clauses where (i) the European Commission adopts a decision pursuant to Article 45(3) of Regulation (EU) 2016/679 that covers the transfer of personal data to which these Clauses apply; or (ii) Regulation (EU) 2016/679 becomes part of the legal framework of the country to which the personal data is transferred. This is without prejudice to other obligations applying to the processing in question under Regulation (EU) 2016/679.
      6. +
    + +##### Clause 17 + +**Governing law** + +These Clauses shall be governed by the law of one of the EU Member States, provided such law allows for third-party beneficiary rights. The Parties agree that this shall be the law of the Netherlands. + +##### Clause 18 + +**Choice of forum and jurisdiction** + +
      +
    1. Any dispute arising from these Clauses shall be resolved by the courts of an EU Member State.
      2. +
    2. The Parties agree that those shall be the courts of the Netherlands.
      3. +
    3. A data subject may also bring legal proceedings against the data exporter and/or data importer before the courts of the Member State in which he/she has his/her habitual residence.
      4. +
    4. The Parties agree to submit themselves to the jurisdiction of such courts.
      5. +
    + +## ANNEX I + +**to the Standard Contractual Clauses (EU/EEA)** + +### A. LIST OF PARTIES + +**Data exporter(s)**: Customer is the data exporter
    Name: see GitHub Customer Agreement
    Address: see GitHub Customer Agreement
    Contact person’s name, position and contact details: see GitHub Customer Agreement
    Activities relevant to the data transferred under these Clauses:
    The data exporter is a user of Online Services or Professional Services as defined in the DPA and GitHub Customer Agreement.
    Signature and date: see GitHub Customer Agreement (the DPA and the Standard Contractual Clauses (EU/EEA) are incorporated into the GitHub Customer Agreement
    Role (controller/processor): controller (unless otherwise agreed in the Customer Agreement).
    + +**Data importer(s)**:
    Name: GitHub, Inc.
    Address: 88 Colin P Kelly Jr St, San Francisco, CA 94107, USA
    Contact person’s name, position and contact details: Frances Wiet, Head of Privacy, fwiet@github.com
    Activities relevant to the data transferred under these Clauses:
    GitHub, Inc. is a global producer of software and services
    Signature and date: see GitHub Customer Agreement (the DPA and the Standard Contractual Clauses (EU/EEA) are incorporated into the GitHub Customer Agreement)
    Role (controller/processor): processor or, depending on the agreements set forth in the Customer Agreement, subprocessor. + +### B. DESCRIPTION OF TRANSFER + +_Categories of data subjects whose personal data is transferred:_ + +Data subjects include the data exporter’s representatives and end-users including employees, contractors, collaborators, and customers of the data exporter. Data subjects may also include individuals attempting to communicate or transfer personal data to users of the services provided by data importer. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following types of data subjects in the personal data: +- 数据出口方的员工、承包商和临时工（现任、前任、未来）； +- 数据出口方的协作者/联系人（自然人）或法律实体协作者/联系人的员工、承包商或临时工（现任、未来、前任）； +- Users and other data subjects that are users of data exporter's services; +- Partners, stakeholders or individuals who actively collaborate, communicate or otherwise interact with employees of the data exporter and/or use communication tools such as apps and websites provided by the data exporter. + +_Categories of personal data transferred:_ + +The personal data transferred that is included in e-mail, documents and other data in an electronic form in the context of the Online Services or Professional Services. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following categories in the personal data: +- Basic personal data (for example place of birth, street name and house number (address), postal code, city of residence, country of residence, mobile phone number, first name, last name, initials, email address, gender, date of birth); +- Authentication data (for example user name, password or PIN code, security question, audit trail); +- Contact information (for example addresses, email, phone numbers, social media identifiers; emergency contact details); +- Unique identification numbers and signatures (for example IP addresses, employee number, student number); +- Pseudonymous identifiers; +- Photos, video and audio; +- Internet activity (for example browsing history, search history, reading and viewing activities); +- Device identification (for example IMEI-number, SIM card number, MAC address); +- Profiling (for example based on observed criminal or anti-social behavior or pseudonymous profiles based on visited URLs, click streams, browsing logs, IP-addresses, domains, apps installed, or profiles based on marketing preferences); +- Special categories of data as voluntarily provided by data subjects (for example racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health, data concerning a natural person’s sex life or sexual orientation, or data relating to criminal convictions or offences); or +- Any other personal data identified in Article 4 of the GDPR. + +_**Sensitive data** transferred (if applicable) and applied restrictions or safeguards that fully take into consideration the nature of the data and the risks involved, such as for instance strict purpose limitation, access restrictions (including access only for staff having followed specialised training), keeping a record of access to the data, restrictions for onward transfers or additional security measures:_
    GitHub does not request or otherwise ask for sensitive data and receives such data only if and when customers or data subjects decide to provide it. + +_**The frequency of the transfer** (e.g. whether the data is transferred on a one-off or continuous basis):_ + +Continuous as part of the Online Services or Professional Services. + +_**Nature of the processing:**_ + +The personal data transferred will be subject to the following basic processing activities: +
      +
    1. Duration and Object of Data Processing. The duration of data processing shall be for the term designated under the applicable GitHub Customer Agreement between data exporter and the data importer. The objective of the data processing is the performance of Online Services and Professional Services.
      2. +
    2. Personal Data Access. For the term designated under the applicable GitHub Customer Agreement, data importer will, at its election and as necessary under applicable law, either: (1) provide data exporter with the ability to correct, delete, or block personal data, or (2) make such corrections, deletions, or blockages on its behalf.
      3. +
    3. Data Exporter’s Instructions. For Online Services and Professional Services, data importer will only act upon data exporter’s instructions.
      4. +
    + +_Purpose(s) of the data transfer and further processing:_ + +The scope and purpose of processing personal data is described in the “Processing of Personal Data; GDPR” section of the DPA. The data importer operates a global network of data centers and management/support facilities, and processing may take place in any jurisdiction where data importer or its sub-processors operate such facilities in accordance with the “Security Practices and Policies” section of the DPA. + +_The period for which the personal data will be retained, or, if that is not possible, the criteria used to determine that period:_ + +Upon expiration or termination of data exporter’s use of Online Services or Professional Services, it may extract personal data and data importer will delete personal data, each in accordance with the DPA Terms applicable to the agreement. + +_For transfers to (sub-) processors, also specify subject matter, nature and duration of the processing:_ + +In accordance with the DPA, the data importer may hire other companies to provide limited services on data importer’s behalf, such as providing customer support. Any such subcontractors will be permitted to obtain personal data only to deliver the services the data importer has retained them to provide, and they are prohibited from using personal data for any other purpose. Unless a particular subcontractor is replaced ahead of time, the processing will be for the term designated under the applicable GitHub Customer Agreement between data exporter and data importer. + +### C. COMPETENT SUPERVISORY AUTHORITY + +_Identify the competent supervisory authority/ies in accordance with Clause 13:_ + +The supervisory authority with responsibility for ensuring compliance by the data exporter with Regulation (EU) 2016/679.   +## ANNEX II + +**to the Standard Contractual Clauses (EU/EEA)** + +**TECHNICAL AND ORGANISATIONAL MEASURES INCLUDING TECHNICAL AND ORGANISATIONAL MEASURES TO ENSURE THE SECURITY OF THE DATA** + +_Description of the technical and organisational measures implemented by the data importer(s) (including any relevant certifications) to ensure an appropriate level of security, taking into account the nature, scope, context and purpose of the processing, and the risks for the rights and freedoms of natural persons._ + +
      +
    1. Data Security Certifications. Data importer holds the following data security certifications:
      2. +
        +
      • SOC 1, Type 2;
        • +
      • SOC 2, Type 2;
        • +
      • NIST, to the extent incorporated for FedRAMP Low-Impact / Tailored ATO.
        • +
      +
    2. Personnel. Data importer’s personnel will not process personal data without authorization. Personnel are obligated to maintain the confidentiality of any such personal data and this obligation continues even after their engagement ends.
      3. +
    3. Data Privacy Contact. The data privacy officer of the data importer can be reached at the following address:

      + GitHub, Inc.
      + Attn: Privacy
      + 88 Colin P. Kelly Jr. Street
      + San Francisco, California 94107 USA

      4. +
    4. Technical and Organization Measures. The data importer has implemented and will maintain appropriate technical and organizational measures, internal controls, and information security routines intended to protect personal data, as defined in the Security Practices and Policies section of the DPA, against accidental loss, destruction, or alteration; unauthorized disclosure or access; or unlawful destruction as follows: The technical and organizational measures, internal controls, and information security routines set forth in the Data Security section of the DPA are hereby incorporated into this Annex II to Attachment 1 by this reference and are binding on the data importer as if they were set forth in this Annex 2 to Attachment 1 in their entirety.
      5. +
    + +_For transfers to (sub-) processors, also describe the specific technical and organisational measures to be taken by the (sub-) processor to be able to provide assistance to the controller and, for transfers from a processor to a sub-processor, to the data exporter:_ + +**Vendor management program - third-party risk program** + +The data importer has a vendor risk assessment process, vendor contract clauses and additional data protection agreements with vendors. Vendors undergo reassessment when a new business use case is requested. The data importer’s vendor risk program is structured so all of data importer’s vendors' risk assessments are refreshed two years from the last review date. + +Vendors deemed high risk, such as data center providers or other vendors storing or processing data in scope for the data importer’s regulatory or contractual requirements, undergo reassessment annually. + +## ANNEX III + +**to the Standard Contractual Clauses (EU/EEA)** + +**Additional Safeguards Addendum** + +By this Additional Safeguards Addendum to Standard Contractual Clauses (EU/EEA) (this “Addendum”), GitHub, Inc. (“GitHub”) provides additional safeguards to Customer and additional redress to the data subjects to whom Customer’s personal data relates. + +This Addendum supplements and is made part of, but is not in variation or modification of, the Standard Contractual Clauses (EU/EEA). + +
      +
    1. Challenges to Orders. In addition to Clause 15.1 of the Standard Contractual Clauses (EU/EEA), in the event GitHub receives an order from any third party for compelled disclosure of any personal data that has been transferred under the Standard Contractual Clauses (EU/EEA), GitHub shall:
      2. +
        +
      1. use every reasonable effort to redirect the third party to request data directly from Customer;
        2. +
      2. promptly notify Customer, unless prohibited under the law applicable to the requesting third party, and, if prohibited from notifying Customer, use all lawful efforts to obtain the right to waive the prohibition in order to communicate as much information to Customer as soon as possible; and
        3. +
      3. use all lawful efforts to challenge the order for disclosure on the basis of any legal deficiencies under the laws of the requesting party or any relevant conflicts with the law of the European Union or applicable Member State law.
        4. +

      + For purpose of this section, lawful efforts do not include actions that would result in civil or criminal penalty such as contempt of court under the laws of the relevant jurisdiction. +
    2. Indemnification of Data Subjects. Subject to Sections 3 and 4, GitHub shall indemnify a data subject for any material or non-material damage to the data subject caused by GitHub’s disclosure of personal data of the data subject that has been transferred under the Standard Contractual Clauses (EU/EEA) in response to an order from a non-EU/EEA government body or law enforcement agency (a “Relevant Disclosure”). Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under this Section 2 to the extent the data subject has already received compensation for the same damage, whether from GitHub or otherwise.
      3. +
    3. Conditions of Indemnification. Indemnification under Section 2 is conditional upon the data subject establishing, to GitHub’s reasonable satisfaction, that:
      4. +
        +
      1. GitHub engaged in a Relevant Disclosure;
        2. +
      2. the Relevant Disclosure was the basis of an official proceeding by the non-EU/EEA government body or law enforcement agency against the data subject; and
        3. +
      3. the Relevant Disclosure directly caused the data subject to suffer material or non-material damage.
        4. +

      + The data subject bears the burden of proof with respect to conditions a. though c.
      + Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under Section 2 if GitHub establishes that the Relevant Disclosure did not violate its obligations under Chapter V of the GDPR.
      +
    4. Scope of Damages. Indemnification under Section 2 is limited to material and non-material damages as provided in the GDPR and excludes consequential damages and all other damages not resulting from GitHub’s infringement of the GDPR.
      5. +
    5. Exercise of Rights. Rights granted to data subjects under this Addendum may be enforced by the data subject against GitHub irrespective of any restriction in Clauses 3 or 12 of the Standard Contractual Clauses (EU/EEA). The data subject may only bring a claim under this Addendum on an individual basis, and not part of a class, collective, group or representative action. Rights granted to data subjects under this Addendum are personal to the data subject and may not be assigned.
      6. +
    6. Notice of Change. In addition to Clause 14 of the Standard Contractual Clauses (EU/EEA), GitHub agrees and warrants that it has no reason to believe that the legislation applicable to it or its sub-processors, including in any country to which personal data is transferred either by itself or through a sub-processor, prevents it from fulfilling the instructions received from the data exporter and its obligations under this Addendum or the Standard Contractual Clauses (EU/EEA) and that in the event of a change in this legislation which is likely to have a substantial adverse effect on the warranties and obligations provided by this Addendum or the Standard Contractual Clauses (EU/EEA), it will promptly notify the change to Customer as soon as it is aware, in which case Customer is entitled to suspend the transfer of data and/or terminate the contract.
      7. +
    7. Termination. This Addendum shall automatically terminate if the European Commission, a competent Member State supervisory authority, or an EU or competent Member State court approves a different lawful transfer mechanism that would be applicable to the data transfers covered by the Standard Contractual Clauses (EU/EEA) (and if such mechanism applies only to some of the data transfers, this Addendum will terminate only with respect to those transfers) and that does not require the additional safeguards set forth in this Addendum.
      8. +
    + +

    Attachment 2 – The Standard Contractual Clauses (UK)

    + +Execution of the GitHub Customer Agreement by Customer includes execution of this Attachment 2, which is countersigned by GitHub, Inc. + +在使用标准合同条款需要监管机构批准的国家/地区，除非客户获得了所需的监管机构批准，否则根据欧洲委员会 2010/87/EU（2010 年 2 月）的规定，客户不得根据标准合同条款确定从此类国家/地区出口数据的合法性。 + +Beginning May 25, 2018 and thereafter, references to various Articles from the Directive 95/46/EC in the Standard Contractual Clauses below will be treated as references to the relevant and appropriate Articles in the GDPR. + +For the purposes of Article 26(2) of Directive 95/46/EC for the transfer of personal data to processors established in third countries which do not ensure an adequate level of data protection, Customer (as data exporter) and GitHub, Inc. (as data importer, whose signature appears below), each a “party,” together “the parties,” have agreed on the following Contractual Clauses (the “Clauses” or “Standard Contractual Clauses”) in order to adduce adequate safeguards with respect to the protection of privacy and fundamental rights and freedoms of individuals for the transfer by the data exporter to the data importer of the personal data specified in Appendix 1. + +### 第 1 条：定义 + +
      +
    1. 'personal data', 'special categories of data', 'process/processing', 'controller', 'processor', 'data subject' and 'supervisory authority' shall have the same meaning as in Directive 95/46/EC of the European Parliament and of the Council of 24 October 1995 on the protection of individuals with regard to the processing of personal data and on the free movement of such data;
      2. +
    2. 'the data exporter' means the controller who transfers the personal data;
      3. +
    3. 'the data importer' means the processor who agrees to receive from the data exporter personal data intended for processing on his behalf after the transfer in accordance with his instructions and the terms of the Clauses and who is not subject to a third country's system ensuring adequate protection within the meaning of Article 25(1) of Directive 95/46/EC;
      4. +
    4. 'the subprocessor' means any processor engaged by the data importer or by any other subprocessor of the data importer who agrees to receive from the data importer or from any other subprocessor of the data importer personal data exclusively intended for processing activities to be carried out on behalf of the data exporter after the transfer in accordance with his instructions, the terms of the Clauses and the terms of the written subcontract;
      5. +
    5. 'the applicable data protection law' means the legislation protecting the fundamental rights and freedoms of individuals and, in particular, their right to privacy with respect to the processing of personal data applicable to a data controller in the Member State in which the data exporter is established;
      6. +
    6. 'technical and organisational security measures' means those measures aimed at protecting personal data against accidental or unlawful destruction or accidental loss, alteration, unauthorised disclosure or access, in particular where the processing involves the transmission of data over a network, and against all other unlawful forms of processing.
      7. +
    + +### 第 2 条：转移细节 + +转移细节，尤其是特殊类别个人数据的转移，应遵守下文附录 1 中的规定，该附录构成了本条款的组成部分。 + +### 第 3 条：第三方受益人条款 + +
      +
    1. 数据主体可以作为第三方受益人对数据出口方执行本条、第 4(b) 至 (i)、第 5(a) 至 (e) 和 (g) 至 (j)、第 6(1) 和 (2)、第 7、第 8(2) 和第 9 至 12 条。
      2. +
    2. 在数据出口方事实上已经消失或在法律上不复存在的情况下，数据主体可对数据进口方执行本条、第 5(a) 至 (e) 和 (g)、第 6、第 7、第 8(2) 和第 9 至 12 条，除非任何继承实体通过合同或法律的实施承担了数据出口方的全部法律义务，并因此承担了数据出口方的权利和义务，在这种情况下，数据主体可以针对此类实体执行这些条款。
      3. +
    3. 在数据出口方和数据进口方事实上已经消失或在法律上不复存在或已经破产的情况下，数据主体可对再处理方执行本条、第 5(a) 至 (e) 和 (g)、第 6、第 7、第 8(2) 和第 9 至 12 条，除非任何继承实体通过合同或法律的实施承担了数据出口方的全部法律义务，并因此承担了数据出口方的权利和义务，在这种情况下，数据主体可以针对此类实体执行这些条款。 再处理方的此类第三方责任应限于其在本条款下的处理业务。
      4. +
    4. 如果数据主体有明确的意愿并且国家法律允许，当事方不反对由协会或其他机构代表数据主体。
      5. +
    + +### 第 4 条：数据出口方的义务 + +数据出口方同意并保证： + +
      +
    1. that the processing, including the transfer itself, of the personal data has been and will continue to be carried out in accordance with the relevant provisions of the applicable data protection law (and, where applicable, has been notified to the relevant authorities of the Member State where the data exporter is established) and does not violate the relevant provisions of that State;
      2. +
    2. that it has instructed and throughout the duration of the personal data processing services will instruct the data importer to process the personal data transferred only on the data exporter's behalf and in accordance with the applicable data protection law and the Clauses;
      3. +
    3. that the data importer will provide sufficient guarantees in respect of the technical and organisational security measures specified in Appendix 2 below;
      4. +
    4. that after assessment of the requirements of the applicable data protection law, the security measures are appropriate to protect personal data against accidental or unlawful destruction or accidental loss, alteration, unauthorised disclosure or access, in particular where the processing involves the transmission of data over a network, and against all other unlawful forms of processing, and that these measures ensure a level of security appropriate to the risks presented by the processing and the nature of the data to be protected having regard to the state of the art and the cost of their implementation;
      5. +
    5. that it will ensure compliance with the security measures;
      6. +
    6. that, if the transfer involves special categories of data, the data subject has been informed or will be informed before, or as soon as possible after, the transfer that its data could be transmitted to a third country not providing adequate protection within the meaning of Directive 95/46/EC;
      7. +
    7. to forward any notification received from the data importer or any subprocessor pursuant to Clause 5(b) and Clause 8(3) to the data protection supervisory authority if the data exporter decides to continue the transfer or to lift the suspension;
      8. +
    8. to make available to the data subjects upon request a copy of the Clauses, with the exception of Appendix 2, and a summary description of the security measures, as well as a copy of any contract for subprocessing services which has to be made in accordance with the Clauses, unless the Clauses or the contract contain commercial information, in which case it may remove such commercial information;
      9. +
    9. that, in the event of subprocessing, the processing activity is carried out in accordance with Clause 11 by a subprocessor providing at least the same level of protection for the personal data and the rights of data subject as the data importer under the Clauses; and
      10. +
    10. that it will ensure compliance with Clause 4(a) to (i).
      11. +
    + +### 第 5 条：数据进口方的义务 + +数据进口方同意并保证： + +
      +
    1. to process the personal data only on behalf of the data exporter and in compliance with its instructions and the Clauses; if it cannot provide such compliance for whatever reasons, it agrees to inform promptly the data exporter of its inability to comply, in which case the data exporter is entitled to suspend the transfer of data and/or terminate the contract;
      2. +
    2. that it has no reason to believe that the legislation applicable to it prevents it from fulfilling the instructions received from the data exporter and its obligations under the contract and that in the event of a change in this legislation which is likely to have a substantial adverse effect on the warranties and obligations provided by the Clauses, it will promptly notify the change to the data exporter as soon as it is aware, in which case the data exporter is entitled to suspend the transfer of data and/or terminate the contract;
      3. +
    3. that it has implemented the technical and organisational security measures specified in Appendix 2 before processing the personal data transferred;
      4. +
    4. that it will promptly notify the data exporter about:
      5. +
        +
      1. any legally binding request for disclosure of the personal data by a law enforcement authority unless otherwise prohibited, such as a prohibition under criminal law to preserve the confidentiality of a law enforcement investigation,
        2. +
      2. any accidental or unauthorised access, and
        3. +
      3. any request received directly from the data subjects without responding to that request, unless it has been otherwise authorised to do so;
        4. +
      + to deal promptly and properly with all inquiries from the data exporter relating to its processing of the personal data subject to the transfer and to abide by the advice of the supervisory authority with regard to the processing of the data transferred; + at the request of the data exporter to submit its data processing facilities for audit of the processing activities covered by the Clauses which shall be carried out by the data exporter or an inspection body composed of independent members and in possession of the required professional qualifications bound by a duty of confidentiality, selected by the data exporter, where applicable, in agreement with the supervisory authority; +
    5. to make available to the data subject upon request a copy of the Clauses, or any existing contract for subprocessing, unless the Clauses or contract contain commercial information, in which case it may remove such commercial information, with the exception of Appendix 2 which shall be replaced by a summary description of the security measures in those cases where the data subject is unable to obtain a copy from the data exporter;
      6. +
    6. that, in the event of subprocessing, it has previously informed the data exporter and obtained its prior written consent;
      7. +
    7. that the processing services by the subprocessor will be carried out in accordance with Clause 11; and
      8. +
    8. to send promptly a copy of any subprocessor agreement it concludes under the Clauses to the data exporter.
      9. +
    + +### 第 6 条：赔偿责任 + +
      +
    1. 双方同意，因任何一方或再处理方违反第 3 条或第 11 条所述义务而遭受损害的任何数据主体，有权就所遭受的损害向数据出口方索取赔偿。
      2. + +
    2. If a data subject is not able to bring a claim for compensation in accordance with paragraph 1 against the data exporter, arising out of a breach by the data importer or his subprocessor of any of their obligations referred to in Clause 3 or in Clause 11, because the data exporter has factually disappeared or ceased to exist in law or has become insolvent, the data importer agrees that the data subject may issue a claim against the data importer as if it were the data exporter, unless any successor entity has assumed the entire legal obligations of the data exporter by contract of by operation of law, in which case the data subject can enforce its rights against such entity.

      + The data importer may not rely on a breach by a subprocessor of its obligations in order to avoid its own liabilities.
      3. + +
    3. 如果由于再处理方违反第 3 条或第 11 条所述的任何义务，数据主体无法根据第 1 和第 2 款向数据出口方或数据进口方提出索赔，其原因是数据出口方和数据进口方均事实上已消失或在法律上不复存在或已破产，再处理方同意，数据主体可以像向数据出口方或数据进口方索赔一样，就再处理方在本条款下的处理业务向其提出索赔，除非任何继承实体通过合同或法律实施承担了数据出口方或数据进口方的全部法律义务，在这种情况下，数据主体可以针对此类实体履行其权利。 再处理方的赔偿责任应限于其在本条款下的处理业务。
      4. +
    + +### 第 7 条：调解和管辖权 + +
      +
    1. 数据进口方同意，如果数据主体援引第三方受益权和/或根据条款要求赔偿损失，数据进口方将接受数据主体的以下决定： +
        +
      1. to refer the dispute to mediation, by an independent person or, where applicable, by the supervisory authority; +
      2. to refer the dispute to the courts in the Member State in which the data exporter is established. +
      +
    2. 双方同意，数据主体的选择不影响其根据国内法或国际法的其他规定寻求补救的实质性或程序性权利。 +
    + +### 第 8 条：与监管机构的合作 + +
      +
    1. 数据出口方同意向监督机构交存本合同副本，如果监督机构或适用的数据保护法要求交存此类副本。
      2. + +
    2. 双方同意，监管机构有权对数据进口方和任何再处理方进行审核，审计范围和条件与适用数据保护法对数据出口方规定的审核相同。
      3. + +
    3. 如果存在阻止根据第 2 款对数据进口方或任何再处理方进行审核的适用立法，数据进口方应立即通知数据出口方。 在这种情况下，数据出口方应有权采取第 5(b) 条规定的措施。
      4. +
    + +### 第 9 条：管辖法律。 + +本条款应受数据出口方所在成员国的法律管辖。 + +### 第 10 条：合同变更 + +双方承诺不改变或修改条款。 但这并不妨碍双方在必要时添加有关业务问题的条款，前提是它们不与本条款相冲突。 + +### 第 11 条：再处理 + +
      +
    1. 未经数据出口方事先书面同意，数据进口方不得将其代表数据出口方执行的任何处理业务分包出去。 如果数据进口方在征得数据出口方同意的情况下，将其在本条款下的义务分包出去，则必须与再处理方签订书面协议，该协议对再处理方施加的义务应与本条款对数据进口方施加的义务相同。 如果再处理方未能履行该书面协议规定的数据保护义务，则数据进口方仍应对数据出口方负全部责任，以履行该协议下的再处理方义务。
      2. + +
    2. 数据进口方与再处理方之间的事先书面合同还应规定第 3 条中所述的第三方受益人条款，以防数据出口方或数据进口方事实上已消失或在法律上不复存在或已破产，而且没有任何继承实体通过合同或法律实施承担数据出口方或数据进口方的全部法律义务，导致数据主体无法向他们提出第 6 条第 1 款所述的索赔。 再处理方的此类第三方责任应限于其在本条款下的处理业务。
      3. + +
    3. 第 1 款所述再处理合同的数据保护方面的规定应受数据出口方所在成员国的法律管辖。
      4. + +
    4. 数据出口方应保留根据本条款缔结并由数据进口方根据第 5(j) 条通知的再处理协议的清单，该清单应每年至少更新一次。 该清单应提供给数据出口方的数据保护监管机构。
      5. +
    + +### 第 12 条：个人数据处理服务终止后的义务 + +
      +
    1. 双方同意，在终止提供数据处理服务时，数据进口方和再处理方应根据数据出口方的选择，将传输的所有个人数据及其副本返还给数据出口方，或者销毁所有个人数据并向数据出口方提供相关证明，除非适用于数据进口方的法律阻止其返还或销毁所传输的全部或部分个人数据。 在这种情况下，数据进口方应保证将确保所传输个人数据的机密性，并且不再主动处理所传输的个人数据。
      2. + +
    2. 数据进口方和再处理方保证，将应数据出口方和/或监管机构的要求，提交其数据处理设施以接受第 1 款所述的审核。
      3. +
    + +### Appendix 1 to the Standard Contractual Clauses (UK) + +**Data exporter**: Customer is the data exporter. The data exporter is a user of Online Services or Professional Services as defined in the DPA and GitHub Customer Agreement. + +**Data importer**: The data importer is GitHub, Inc., a global producer of software and services. + +**Data subjects**: Data subjects include the data exporter’s representatives and end-users including employees, contractors, collaborators, and customers of the data exporter. Data subjects may also include individuals attempting to communicate or transfer personal data to users of the services provided by data importer. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following types of data subjects in the personal data: +- 数据出口方的员工、承包商和临时工（现任、前任、未来）； +- 数据出口方的协作者/联系人（自然人）或法律实体协作者/联系人的员工、承包商或临时工（现任、未来、前任）； +- Users and other data subjects that are users of data exporter's services; +- Partners, stakeholders or individuals who actively collaborate, communicate or otherwise interact with employees of the data exporter and/or use communication tools such as apps and websites provided by the data exporter. + +**Categories of data**: The personal data transferred that is included in e-mail, documents and other data in an electronic form in the context of the Online Services or Professional Services. GitHub acknowledges that, depending on Customer’s use of the Online Service or Professional Services, Customer may elect to include personal data from any of the following categories in the personal data: +- Basic personal data (for example place of birth, street name and house number (address), postal code, city of residence, country of residence, mobile phone number, first name, last name, initials, email address, gender, date of birth); +- Authentication data (for example user name, password or PIN code, security question, audit trail); +- Contact information (for example addresses, email, phone numbers, social media identifiers; emergency contact details); +- Unique identification numbers and signatures (for example IP addresses, employee number, student number); +- Pseudonymous identifiers; +- Photos, video and audio; +- Internet activity (for example browsing history, search history, reading and viewing activities); +- Device identification (for example IMEI-number, SIM card number, MAC address); +- Profiling (for example based on observed criminal or anti-social behavior or pseudonymous profiles based on visited URLs, click streams, browsing logs, IP-addresses, domains, apps installed, or profiles based on marketing preferences); +- Special categories of data as voluntarily provided by data subjects (for example racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health, data concerning a natural person’s sex life or sexual orientation, or data relating to criminal convictions or offences); or +- Any other personal data identified in Article 4 of the GDPR. + +**Processing operations**: The personal data transferred will be subject to the following basic processing activities: + +
      +
    1. Duration and Object of Data Processing. The duration of data processing shall be for the term designated under the applicable GitHub Customer Agreement between data exporter and data importer. The objective of the data processing is the performance of Online Services and Professional Services.
      2. +
    2. Scope and Purpose of Data Processing. The scope and purpose of processing personal data is described in the “Processing of Personal Data; GDPR” section of the DPA. The data importer operates a global network of data centers and management/support facilities, and processing may take place in any jurisdiction where data importer or its sub-processors operate such facilities in accordance with the “Security Practices and Policies” section of the DPA.
      3. +
    3. Personal Data Access. For the term designated under the applicable GitHub Customer Agreement data importer will at its election and as necessary under applicable law, either: (1) provide data exporter with the ability to correct, delete, or block personal data, or (2) make such corrections, deletions, or blockages on its behalf.
      4. +
    4. Data Exporter’s Instructions. For Online Services and Professional Services, data importer will only act upon data exporter’s instructions as conveyed by GitHub.
      5. +
    5. Personal Data Deletion or Return. Upon expiration or termination of data exporter’s use of Online Services or Professional Services, it may extract personal data and data importer will delete personal data, each in accordance with the DPA Terms applicable to the agreement.
      6. +
    + +**Subcontractors**: In accordance with the DPA, the data importer may hire other companies to provide limited services on data importer’s behalf, such as providing customer support. Any such subcontractors will be permitted to obtain personal data only to deliver the services the data importer has retained them to provide, and they are prohibited from using personal data for any other purpose. + +### Appendix 2 to the Standard Contractual Clauses (UK) + +数据进口方根据第 4(d) 和 5(c) 条实施的技术和组织安全措施的说明： + +
      +
    1. Personnel. Data importer’s personnel will not process personal data without authorization. Personnel are obligated to maintain the confidentiality of any such personal data and this obligation continues even after their engagement ends.
      2. + +
    2. Data Privacy Contact. The data privacy officer of the data importer can be reached at the following address:
      +GitHub, Inc.
      +Attn: Privacy
      +88 Colin P. Kelly Jr. Street
      +San Francisco, California 94107 USA
      3. + +
    3. Technical and Organization Measures. The data importer has implemented and will maintain appropriate technical and organizational measures, internal controls, and information security routines intended to protect personal data, as defined in the Security Practices and Policies section of the DPA, against accidental loss, destruction, or alteration; unauthorized disclosure or access; or unlawful destruction as follows: The technical and organizational measures, internal controls, and information security routines set forth in the Security Practices and Policies section of the DPA are hereby incorporated into this Appendix 2 by this reference and are binding on the data importer as if they were set forth in this Appendix 2 in their entirety.
      4. +
    + +### Appendix 3 to the Standard Contractual Clauses (UK) + +**Additional Safeguards Addendum** + +By this Additional Safeguards Addendum to Standard Contractual Clauses (UK) (this “Addendum”), GitHub, Inc. (“GitHub”) provides additional safeguards to Customer and additional redress to the data subjects to whom Customer’s personal data relates. + +This Addendum supplements and is made part of, but is not in variation or modification of, the Standard Contractual Clauses (UK). + +
      +
    1. Challenges to Orders. In addition to Clause 5(d)(i) of the Standard Contractual Clauses (UK), in the event GitHub receives an order from any third party for compelled disclosure of any personal data that has been transferred under the Standard Contractual Clauses (UK), GitHub shall:
      2. +
        +
      1. use every reasonable effort to redirect the third party to request data directly from Customer;
        2. +
      2. promptly notify Customer, unless prohibited under the law applicable to the requesting third party, and, if prohibited from notifying Customer, use all lawful efforts to obtain the right to waive the prohibition in order to communicate as much information to Customer as soon as possible; and
        3. +
      3. use all lawful efforts to challenge the order for disclosure on the basis of any legal deficiencies under the laws of the requesting party or any relevant conflicts with the law of the European Union or applicable Member State law.
        4. +

      + For purpose of this section, lawful efforts do not include actions that would result in civil or criminal penalty such as contempt of court under the laws of the relevant jurisdiction. +
    2. Indemnification of Data Subjects. Subject to Sections 3 and 4, GitHub shall indemnify a data subject for any material or non-material damage to the data subject caused by GitHub’s disclosure of personal data of the data subject that has been transferred under the Standard Contractual Clauses (UK) in response to an order from a non-EU/EEA government body or law enforcement agency (a “Relevant Disclosure”). Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under this Section 2 to the extent the data subject has already received compensation for the same damage, whether from GitHub or otherwise.
      3. +
    3. Conditions of Indemnification. Indemnification under Section 2 is conditional upon the data subject establishing, to GitHub’s reasonable satisfaction, that:
      4. +
        +
      1. GitHub engaged in a Relevant Disclosure;
        2. +
      2. the Relevant Disclosure was the basis of an official proceeding by the non-EU/EEA government body or law enforcement agency against the data subject; and
        3. +
      3. the Relevant Disclosure directly caused the data subject to suffer material or non-material damage.
        4. +

      + The data subject bears the burden of proof with respect to conditions a. though c.
      + Notwithstanding the foregoing, GitHub shall have no obligation to indemnify the data subject under Section 2 if GitHub establishes that the Relevant Disclosure did not violate its obligations under Chapter V of the GDPR. +
    4. Scope of Damages. Indemnification under Section 2 is limited to material and non-material damages as provided in the GDPR and excludes consequential damages and all other damages not resulting from GitHub’s infringement of the GDPR.
      5. +
    5. Exercise of Rights. Rights granted to data subjects under this Addendum may be enforced by the data subject against GitHub irrespective of any restriction in Clauses 3 or 6 of the Standard Contractual Clauses (UK). The data subject may only bring a claim under this Addendum on an individual basis, and not part of a class, collective, group or representative action. Rights granted to data subjects under this Addendum are personal to the data subject and may not be assigned.
      6. +
    6. Notice of Change. In addition to Clause 5(b) of the Standard Contractual Clauses (UK), GitHub agrees and warrants that it has no reason to believe that the legislation applicable to it or its sub-processors, including in any country to which personal data is transferred either by itself or through a sub-processor, prevents it from fulfilling the instructions received from the data exporter and its obligations under this Addendum or the Standard Contractual Clauses (UK) and that in the event of a change in this legislation which is likely to have a substantial adverse effect on the warranties and obligations provided by this Addendum or the Standard Contractual Clauses (UK), it will promptly notify the change to Customer as soon as it is aware, in which case Customer is entitled to suspend the transfer of data and/or terminate the contract. +
    7. Termination. This Addendum shall automatically terminate if the European Commission, a competent Member State supervisory authority, or an EU or competent Member State court approves a different lawful transfer mechanism that would be applicable to the data transfers covered by the Standard Contractual Clauses (UK) (and if such mechanism applies only to some of the data transfers, this Addendum will terminate only with respect to those transfers) and that does not require the additional safeguards set forth in this Addendum.

      + Signing the Standard Contractual Clauses (UK), Appendix 1, Appendix 2 and +
    + +

    Attachment 3 – European Union General Data Protection Regulation Terms

    + +GitHub makes the commitments in these GDPR Related Terms, to all customers effective May 25, 2018. These commitments are binding upon GitHub with regard to Customer regardless of (1) the version of the GitHub Customer Agreement and DPA that is otherwise applicable to any given Online Services subscription or (2) any other agreement that references this attachment. + +For purposes of these GDPR Related Terms, Customer and GitHub agree that Customer is the controller of Personal Data and GitHub is the processor of such data, except when Customer acts as a processor of Personal Data, in which case GitHub is a subprocessor. These GDPR Related Terms apply to the processing of Personal Data, within the scope of the GDPR, by GitHub on behalf of Customer. These GDPR Related Terms do not limit or reduce any data protection commitments GitHub makes to Customer in the GitHub Customer Agreement or other agreement between GitHub and Customer. These GDPR Related Terms do not apply where GitHub is a controller of Personal Data. + +**Relevant GDPR Obligations: Articles 28, 32, and 33** + +
      +
    1. GitHub shall not engage another processor without prior specific or general written authorisation of Customer. In the case of general written authorisation, GitHub shall inform Customer of any intended changes concerning the addition or replacement of other processors, thereby giving Customer the opportunity to object to such changes. (Article 28(2))
      2. +
    2. Processing by GitHub shall be governed by these GDPR Related Terms under European Union (hereafter “Union”) or Member State law and are binding on GitHub with regard to Customer. The subject-matter and duration of the processing, the nature and purpose of the processing, the type of Personal Data, the categories of data subjects and the obligations and rights of the Customer are set forth in the Customer’s licensing agreement, including these GDPR Related Terms. In particular, GitHub shall:
      3. +
        +
      1. process the Personal Data only on documented instructions from Customer, including with regard to transfers of Personal Data to a third country or an international organisation, unless required to do so by Union or Member State law to which GitHub is subject; in such a case, GitHub shall inform Customer of that legal requirement before processing, unless that law prohibits such information on important grounds of public interest;
        2. +
      2. ensure that persons authorised to process the Personal Data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality;
        3. +
      3. take all measures required pursuant to Article 32 of the GDPR;
        4. +
      4. respect the conditions referred to in paragraphs 1 and 3 for engaging another processor;
        5. +
      5. taking into account the nature of the processing, assist Customer by appropriate technical and organisational measures, insofar as this is possible, for the fulfilment of the Customer’s obligation to respond to requests for exercising the data subject's rights laid down in Chapter III of the GDPR;
        6. +
      6. assist Customer in ensuring compliance with the obligations pursuant to Articles 32 to 36 of the GDPR, taking into account the nature of processing and the information available to GitHub;
        7. +
      7. at the choice of Customer, delete or return all the Personal Data to Customer after the end of the provision of services relating to processing, and delete existing copies unless Union or Member State law requires storage of the Personal Data;
        8. +
      8. make available to Customer all information necessary to demonstrate compliance with the obligations laid down in Article 28 of the GDPR and allow for and contribute to audits, including inspections, conducted by Customer or another auditor mandated by Customer.
        9. +

      + GitHub shall immediately inform Customer if, in its opinion, an instruction infringes the GDPR or other Union or Member State data protection provisions. (Article 28(3))

      +
    3. Where GitHub engages another processor for carrying out specific processing activities on behalf of Customer, the same data protection obligations as set out in these GDPR Related Terms shall be imposed on that other processor by way of a contract or other legal act under Union or Member State law, in particular providing sufficient guarantees to implement appropriate technical and organisational measures in such a manner that the processing will meet the requirements of the GDPR. Where that other processor fails to fulfil its data protection obligations, GitHub shall remain fully liable to the Customer for the performance of that other processor's obligations. (Article 28(4))
      4. +
    4. Taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of processing as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons, Customer and GitHub shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, including inter alia as appropriate:
      5. +
        +
      1. the pseudonymisation and encryption of Personal Data;
        2. +
      2. the ability to ensure the ongoing confidentiality, integrity, availability and resilience of processing systems and services;
        3. +
      3. the ability to restore the availability and access to Personal Data in a timely manner in the event of a physical or technical incident; and
        4. +
      4. a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the processing. (Article 32(1))
        5. +
      +
    5. In assessing the appropriate level of security, account shall be taken of the risks that are presented by processing, in particular from accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to Personal Data transmitted, stored or otherwise processed (Article 32(2)).
      6. +
    6. Customer and GitHub shall take steps to ensure that any natural person acting under the authority of Customer or GitHub who has access to Personal Data does not process them except on instructions from Customer, unless he or she is required to do so by Union or Member State law (Article 32(4)).
      7. +
    7. GitHub shall notify Customer without undue delay after becoming aware of a Personal Data breach (Article 33(2)). Such notification will include that information a processor must provide to a controller under Article 33(3) to the extent such information is reasonably available to GitHub.
      8. +
    + +--------------- + +

    (1) The Agreement on the European Economic Area (EEA Agreement) provides for the extension of the European Union’s internal market to the three EEA States Iceland, Liechtenstein and Norway. The Union data protection legislation, including Regulation (EU) 2016/679, is covered by the EEA Agreement and has been incorporated into Annex XI thereto. Therefore, any disclosure by the data importer to a third party located in the EEA does not qualify as an onward transfer for the purpose of these Clauses.

    + +

    (2) This requirement may be satisfied by the sub-processor acceding to these Clauses under the appropriate Module, in accordance with Clause 7.

    + +

    (3) As regards the impact of such laws and practices on compliance with these Clauses, different elements may be considered as part of an overall assessment. Such elements may include relevant and documented practical experience with prior instances of requests for disclosure from public authorities, or the absence of such requests, covering a sufficiently representative time-frame. This refers in particular to internal records or other documentation, drawn up on a continuous basis in accordance with due diligence and certified at senior management level, provided that this information can be lawfully shared with third parties. Where this practical experience is relied upon to conclude that the data importer will not be prevented from complying with these Clauses, it needs to be supported by other relevant, objective elements, and it is for the Parties to consider carefully whether these elements together carry sufficient weight, in terms of their reliability and representativeness, to support this conclusion. In particular, the Parties have to take into account whether their practical experience is corroborated and not contradicted by publicly available or otherwise accessible, reliable information on the existence or absence of requests within the same sector and/or the application of the law in practice, such as case law and reports by independent oversight bodies.

    diff --git a/translations/zh-CN/content/github/site-policy/github-terms-for-additional-products-and-features.md b/translations/zh-CN/content/github/site-policy/github-terms-for-additional-products-and-features.md index e914d48c58..ec73b08425 100644 --- a/translations/zh-CN/content/github/site-policy/github-terms-for-additional-products-and-features.md +++ b/translations/zh-CN/content/github/site-policy/github-terms-for-additional-products-and-features.md @@ -20,7 +20,7 @@ Version Effective Date: August 10, 2021 - **GitHub Enterprise Server** 用户可以访问以下附加产品和特性：Actions、Advanced Security、Advisory Database、Connect、Dependabot Preview、Learning Lab、Octoshift, Packages、Pages 和 SQL Server Images。 -- **GitHub AE** 用户可以访问以下附加产品和特性：Actions、Advanced Security、Advisory Database、{% ifversion ghae-next %}Connect、{% endif %}Dependabot Preview、Octoshift、Packages 和 Pages。 +- **GitHub AE** users may have access to the following Additional Products and Features: Actions, Advanced Security, Advisory Database,{% ifversion ghae-next %}Connect, {% endif %}Dependabot Preview, Octoshift, Packages and Pages. ## 操作 GitHub Actions 使您能够直接在您的 GitHub 仓库中创建自定义软件开发生命周期工作流程。 Actions 按使用情况计费。 [Actions 文档](/actions)包含详细信息，包括计算和存储量（取决于您的帐户计划）以及如何监控您的 Actions 分钟使用和设置使用限制。 @@ -38,7 +38,7 @@ Actions and any elements of the Actions product or service may not be used in vi ## Advanced Security GitHub 根据高级安全许可证向客户提供额外的安全功能。 这些功能包括代码扫描、秘密扫描和依赖项审查。 [Advanced Security 文档](/github/getting-started-with-github/about-github-advanced-security)提供更多详细信息。 -Advanced Security 按“唯一提交者”许可。 “唯一提交者”是 GitHub Enterprise、GitHub Enterprise Cloud、GitHub Enterprise Server 或 GitHub AE 的许可用户，他们在过去 90 天内向激活了 GitHub Advanced Security 功能的任意仓库提交过代码。 您必须为每个唯一提交者获取 GitHub Advanced Security 用户许可。 您只能在由您开发或为您开发的代码库上使用 GitHub Advanced Security。 对于 GitHub Enterprise Cloud 用户，一些高级安全功能也需要使用 GitHub Actions。 +Advanced Security 按“唯一提交者”许可。 A "Unique Committer" is a licensed user of GitHub Enterprise, GitHub Enterprise Cloud, GitHub Enterprise Server, or GitHub AE, who has made a commit in the last 90 days to any repository with any GitHub Advanced Security functionality activated. 您必须为每个唯一提交者获取 GitHub Advanced Security 用户许可。 您只能在由您开发或为您开发的代码库上使用 GitHub Advanced Security。 对于 GitHub Enterprise Cloud 用户，一些高级安全功能也需要使用 GitHub Actions。 ## Advisory Database GitHub 咨询数据库允许您浏览或搜索影响 GitHub 上开源项目的漏洞。 diff --git a/translations/zh-CN/content/github/site-policy/index.md b/translations/zh-CN/content/github/site-policy/index.md index f9151ad48b..fb3963d802 100644 --- a/translations/zh-CN/content/github/site-policy/index.md +++ b/translations/zh-CN/content/github/site-policy/index.md @@ -12,7 +12,7 @@ children: - /github-terms-of-service - /github-corporate-terms-of-service - /github-privacy-statement - - /github-data-protection-agreement-non-enterprise-customers + - /github-data-protection-agreement - /global-privacy-practices - /github-sponsors-additional-terms - /github-codespaces-privacy-statement diff --git a/translations/zh-CN/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md b/translations/zh-CN/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md index 605a3133c9..164fccd087 100644 --- a/translations/zh-CN/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md +++ b/translations/zh-CN/content/github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md @@ -1,6 +1,7 @@ --- title: 创建 Gist intro: '您可以创建两种 gist：{% ifversion ghae %}内部{% else %}公共{% endif %}和秘密。 如果您准备与{% ifversion ghae %}企业成员{% else %}全世界{% endif %}分享您的创意，请创建{% ifversion ghae %}内部{% else %}公共{% endif %} gist，否则请创建秘密 gist。' +permissions: '{% data reusables.enterprise-accounts.emu-permission-gist %}' redirect_from: - /articles/about-gists/ - /articles/cannot-delete-an-anonymous-gist/ @@ -42,7 +43,7 @@ Gist 可设为{% ifversion ghae %}内部{% else %}公共{% endif %}或秘密。 {% endif %} -通过访问 {% data variables.gists.gist_homepage %} 并单击 **All Gists（所有 Gist）**，您可以发现其他人创建的{% ifversion ghae %}内部{% else %}公共{% endif %} gist。 将会显示所有 gists 存储的页面，gist 按创建或更新时间显示。 您也可以通过 {% data variables.gists.gist_search_url %} 按语言搜索 gist。 Gist 搜索使用的搜索语法与[代码搜索](/articles/searching-code)相同。 +通过访问 {% data variables.gists.gist_homepage %} 并单击 **All Gists（所有 Gist）**，您可以发现其他人创建的{% ifversion ghae %}内部{% else %}公共{% endif %} gist。 将会显示所有 gists 存储的页面，gist 按创建或更新时间显示。 您也可以通过 {% data variables.gists.gist_search_url %} 按语言搜索 gist。 Gist 搜索使用的搜索语法与[代码搜索](/search-github/searching-on-github/searching-code)相同。 由于 gists 是 Git 仓库，因此您可以查看其整个提交历史记录，包括差异。 您也可以复刻或克隆 gists。 更多信息请参阅[“复刻和克隆 gists”](/articles/forking-and-cloning-gists)。 diff --git a/translations/zh-CN/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md b/translations/zh-CN/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md index a31906a236..8a5d6948ff 100644 --- a/translations/zh-CN/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md +++ b/translations/zh-CN/content/github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md @@ -1,6 +1,7 @@ --- title: 复刻和克隆 Gist intro: Gist 实际上是 Git 仓库，这意味着即使您不是原作者，也可以复刻或克隆任何 Gist。 还可以查看 Gist 的完整提交历史记录，包括差异。 +permissions: '{% data reusables.enterprise-accounts.emu-permission-gist %}' redirect_from: - /articles/forking-and-cloning-gists - /github/writing-on-github/forking-and-cloning-gists diff --git a/translations/zh-CN/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md b/translations/zh-CN/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md index 707e167754..869b466c32 100644 --- a/translations/zh-CN/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md +++ b/translations/zh-CN/content/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md @@ -40,9 +40,9 @@ shortTitle: 基本格式语法 您可以使用 `>` 来引用文本。 ```markdown -用 Abraham Lincoln 的话来说： +Text that is not a quote -> 原谅我爆粗口 +> Text that is a quote ``` ![渲染的引用文本](/assets/images/help/writing/quoted-text-rendered.png) @@ -184,7 +184,7 @@ For more information, see "[Relative Links](#relative-links)." ![含一个嵌套列表项的列表](/assets/images/help/writing/nested-list-example-3.png) -您可以使用相同的方法创建多层级嵌套列表。 例如，由于在第一个嵌套列表项中，嵌套列表项内容`第一个嵌套列表项`之前有七个空格 (`␣␣␣␣␣-␣`)，因此需要将第二个嵌套列表项缩进七个空格。 +您可以使用相同的方法创建多层级嵌套列表。 For example, because the first nested list item has seven characters (`␣␣␣␣␣-␣`) before the nested list content `First nested list item`, you would need to indent the second nested list item by seven spaces. ```markdown 100. 第一个列表项 @@ -262,6 +262,30 @@ Some {% data variables.product.prodname_github_apps %} provide information in {% 通过在文本行之间留一个空白行，可创建新段落。 +{% ifversion fpt or ghae-next or ghes > 3.3 %} +## 脚注 + +You can add footnotes to your content by using this bracket syntax: + +``` +Here is a simple footnote[^1]. + +[^1]: My reference. +``` + +The footnote will render like this: + +![Rendered footnote](/assets/images/site/rendered-footnote.png) +{% endif %} + +## Hiding content with comments + +You can tell {% data variables.product.product_name %} to hide content from the rendered Markdown by placing the content in an HTML comment. + +
    +<!-- This content will not appear in the rendered Markdown -->
+
    + ## 忽略 Markdown 格式 通过在 Markdown 字符前面输入 `\`，可告诉 {% data variables.product.product_name %} 忽略（或规避）Markdown 格式。 @@ -272,13 +296,13 @@ Some {% data variables.product.prodname_github_apps %} provide information in {% 更多信息请参阅 Daring Fireball 的“[Markdown 语法](https://daringfireball.net/projects/markdown/syntax#backslash)”。 -## Hiding content with comments +{% ifversion fpt or ghes > 3.2 or ghae-issue-5232 %} -You can tell {% data variables.product.product_name %} to hide content from the rendered Markdown by placing the content in an HTML comment. +## Disabling Markdown rendering -
    -<!-- This content will not appear in the rendered Markdown -->
-
    +{% data reusables.repositories.disabling-markdown-rendering %} + +{% endif %} ## 延伸阅读 diff --git a/translations/zh-CN/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md b/translations/zh-CN/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md index 1b525ee953..9f7ec55e74 100644 --- a/translations/zh-CN/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md +++ b/translations/zh-CN/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md @@ -16,7 +16,7 @@ topics: {% warning %} -**警告：**如果您将图像{% ifversion fpt or ghes > 3.1 or ghae-next %}或视频{% endif %}添加到拉取请求或议题评论中，则任何人都可以在未经身份验证的情况下查看匿名 URL，即使该拉取请求在私有仓库中{% ifversion ghes %}或启用了私有模式{% endif %}。 要对敏感媒体文件保密，请从需要身份验证的私有网络或服务器提供它们。 {% ifversion fpt %}有关匿名 URL 的更多信息，请参阅“[关于匿名 URL](/github/authenticating-to-github/about-anonymized-urls)”。{% endif %} +**Warning:** If you add an image{% ifversion fpt or ghes > 3.1 or ghae-next %} or video{% endif %} to a pull request or issue comment, anyone can view the anonymized URL without authentication, even if the pull request is in a private repository{% ifversion ghes %}, or if private mode is enabled{% endif %}. 要对敏感媒体文件保密，请从需要身份验证的私有网络或服务器提供它们。 {% ifversion fpt %}有关匿名 URL 的更多信息，请参阅“[关于匿名 URL](/github/authenticating-to-github/about-anonymized-urls)”。{% endif %} {% endwarning %} @@ -31,9 +31,10 @@ topics: {% endtip %} 最大文件大小为： -- 10MB，对于图像和 gif{% ifversion fpt or ghes > 3.1 or ghae-next %} +- 10MB for images and gifs{% ifversion fpt %} - 10MB，对于上传到使用免费 GitHub 计划的用户或组织所拥有仓库的视频 -- 100MB，对于上传到使用付费 GitHub 计划的用户或组织所拥有仓库的视频{% endif %} +- 100MB，对于上传到使用付费 GitHub 计划的用户或组织所拥有仓库的视频{% elsif fpt or ghes > 3.1 or ghae-next %} +- 100MB for videos{% endif %} - 25MB，对于所有其他文件 我们支持这些文件： diff --git a/translations/zh-CN/content/graphql/guides/managing-enterprise-accounts.md b/translations/zh-CN/content/graphql/guides/managing-enterprise-accounts.md index fe5c9bf66e..4d8fff2f4f 100644 --- a/translations/zh-CN/content/graphql/guides/managing-enterprise-accounts.md +++ b/translations/zh-CN/content/graphql/guides/managing-enterprise-accounts.md @@ -58,8 +58,9 @@ GraphQL 可用于仅请求和返回您指定的数据。 例如，您可以创 - `admin:enterprise` 企业帐户特定作用域包括： - - `admin:enterprise`：全面控制企业（包括 `manage_billing:enterprise` 和 `read:enterprise`） - - `manage_billing:enterprise`：读取和写入企业帐单数据。 + - `admin:enterprise`: Gives full control of enterprises (includes {% ifversion ghes > 3.2 or fpt or ghae %}`manage_runners:enterprise`, {% endif %}`manage_billing:enterprise` and `read:enterprise`) + - `manage_billing:enterprise`: Read and write enterprise billing data.{% ifversion ghes > 3.2 or fpt or ghae %} + - `manage_runners:enterprise`: Access to manage GitHub Actions enterprise runners and runner-groups.{% endif %} - `read:enterprise`：读取企业简介数据。 4. 复制个人访问令牌并保存在安全的位置，直到将其添加至您的 GraphQL 客户端。 diff --git a/translations/zh-CN/content/graphql/guides/using-the-graphql-api-for-discussions.md b/translations/zh-CN/content/graphql/guides/using-the-graphql-api-for-discussions.md index 8694a59ea3..ce16e4fd1d 100644 --- a/translations/zh-CN/content/graphql/guides/using-the-graphql-api-for-discussions.md +++ b/translations/zh-CN/content/graphql/guides/using-the-graphql-api-for-discussions.md @@ -1080,4 +1080,4 @@ mutation { ## 搜索 -讨论可从顶层`搜索`字段返回。 要搜索讨论，请将`类型`指定为 `DISCUSSION`。 `SearchResultItemConnect` 类型有一个 `discussionCount` 字段来报告返回的讨论数。`讨论`类型已添加到 `SearchResultItem` 并集。 更多信息请参阅“[查询](/graphql/reference/queries#searchresultitemconnection)”和“[搜索讨论](/github/searching-for-information-on-github/searching-discussions)”。 +讨论可从顶层`搜索`字段返回。 要搜索讨论，请将`类型`指定为 `DISCUSSION`。 `SearchResultItemConnect` 类型有一个 `discussionCount` 字段来报告返回的讨论数。`讨论`类型已添加到 `SearchResultItem` 并集。 更多信息请参阅“[查询](/graphql/reference/queries#searchresultitemconnection)”和“[搜索讨论](/search-github/searching-on-github/searching-discussions)”。 diff --git a/translations/zh-CN/content/index.md b/translations/zh-CN/content/index.md index ab7596fedf..4627059a37 100644 --- a/translations/zh-CN/content/index.md +++ b/translations/zh-CN/content/index.md @@ -27,6 +27,7 @@ children: - actions - codespaces - packages + - search-github - developers - rest - graphql 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 b8208082cc..2842596621 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 @@ -1,6 +1,7 @@ --- title: 分配议题和拉取请求到其他 GitHub 用户 intro: 受理人明确谁在处理特定议题和拉取请求。 +permissions: 'Anyone with write access to a repository can assign issues and pull requests. {% data reusables.enterprise-accounts.emu-permission-repo %}' redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/assigning-issues-and-pull-requests-to-other-github-users - /articles/assigning-issues-and-pull-requests-to-other-github-users @@ -15,8 +16,6 @@ topics: shortTitle: 分配议题和 PR --- -对仓库有写入权限的任何人都可以分配议题和拉取请求。 - ## 关于议题和拉取请求受理人 每个议题和拉取请求最多可分配给 10 个人，包括您自己、 任何评论了议题或拉取请求的人、任何对仓库有写入权限的人以及对仓库有读取权限的组织成员 。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 上的访问权限](/articles/access-permissions-on-github)”。 diff --git a/translations/zh-CN/content/issues/tracking-your-work-with-issues/creating-an-issue.md b/translations/zh-CN/content/issues/tracking-your-work-with-issues/creating-an-issue.md index d99669508c..c359b7d768 100644 --- a/translations/zh-CN/content/issues/tracking-your-work-with-issues/creating-an-issue.md +++ b/translations/zh-CN/content/issues/tracking-your-work-with-issues/creating-an-issue.md @@ -1,7 +1,7 @@ --- title: 创建议题 intro: 议题可以通过多种方式创建，因此您可以为工作流程选择最方便的方法。 -permissions: People with read permissions can create an issue in a repository where issues are enabled. +permissions: 'People with read access can create an issue in a repository where issues are enabled. {% data reusables.enterprise-accounts.emu-permission-repo %}' redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/creating-an-issue - /articles/creating-an-issue 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 e5b6dfd60a..270ad79e92 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 @@ -102,7 +102,8 @@ Once you've [applied labels to an issue or pull request](/articles/applying-labe - [需要审查](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)后才能合并的拉取请求 - 审查者已批准的拉取请求 - 审查者要求更改的拉取请求 -- 您已审查的拉取请求 +- Pull requests that you have reviewed{% ifversion fpt or ghae or ghes > 3.2 %} +- Pull requests that someone has asked you directly to review{% endif %} - [有人要求您或您所属团队进行审查](/articles/requesting-a-pull-request-review)的拉取请求 {% data reusables.repositories.navigate-to-repo %} @@ -185,7 +186,8 @@ gh pr list --search "team:octo-org/octo-team" - 过滤审查者已批准的拉取请求：`state:open type:pr review:approved` - 过滤审查者要求更改的拉取请求：`state:open type:pr review:changes_requested` - 按[审查者](/articles/about-pull-request-reviews/)过滤拉取请求：`state:open type:pr reviewed-by:octocat` -- 按[请求审查](/articles/requesting-a-pull-request-review)的特定用户过滤拉取请求：`state:open type:pr review-requested:octocat` +- Filter pull requests by the specific user [requested for review](/articles/requesting-a-pull-request-review): `state:open type:pr review-requested:octocat`{% ifversion fpt or ghae or ghes > 3.2 %} +- Filter pull requests that someone has asked you directly to review: `state:open type:pr user-review-requested:@me`{% endif %} - 按申请审查的团队过滤拉取请求：`state:open type:pr team-review-requested:github/atom`{% ifversion fpt or ghes or ghae %} - 过滤链接到拉取请求可能关闭的议题的拉取请求：`linked:issue`{% endif %} diff --git a/translations/zh-CN/content/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository.md b/translations/zh-CN/content/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository.md index 07a18769cf..514173d32a 100644 --- a/translations/zh-CN/content/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository.md +++ b/translations/zh-CN/content/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository.md @@ -1,6 +1,7 @@ --- title: 将议题固定到仓库 intro: 在仓库中议题列表的上方最多可以固定三个重要议题。 +permissions: 'People with write access to a repository can pin issue in the repository. {% data reusables.enterprise-accounts.emu-permission-repo %}' redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/pinning-an-issue-to-your-repository - /articles/pinning-an-issue-to-your-repository @@ -17,8 +18,6 @@ shortTitle: 固定议题 ![固定的议题](/assets/images/help/issues/pinned-issues.png) -要固定某个议题，必须对该议题所在的仓库具有写入权限。 - {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issues %} 1. 在议题列表中，单击您想要固定的议题。 diff --git a/translations/zh-CN/content/issues/tracking-your-work-with-issues/quickstart.md b/translations/zh-CN/content/issues/tracking-your-work-with-issues/quickstart.md index 0d034dfbdd..9d3b3cef3d 100644 --- a/translations/zh-CN/content/issues/tracking-your-work-with-issues/quickstart.md +++ b/translations/zh-CN/content/issues/tracking-your-work-with-issues/quickstart.md @@ -19,7 +19,7 @@ topics: ## 基本要求 -要创建议题，您需要一个仓库。 您可以使用您有写入权限的现有仓库，或者创建一个新的仓库。 仓库必须启用议题。 关于创建仓库的更多信息，请参阅“[创建新仓库](/articles/creating-a-new-repository)”。 关于启用议题（如果它们在您的仓库中被禁用）的更多信息，请参阅“[禁用议题](/github/administering-a-repository/managing-repository-settings/disabling-issues)“。 +要创建议题，您需要一个仓库。 您可以使用您有写入权限的现有仓库，或者创建一个新的仓库。 {% data reusables.enterprise-accounts.emu-permission-repo %} The repository must have issues enabled. 关于创建仓库的更多信息，请参阅“[创建新仓库](/articles/creating-a-new-repository)”。 关于启用议题（如果它们在您的仓库中被禁用）的更多信息，请参阅“[禁用议题](/github/administering-a-repository/managing-repository-settings/disabling-issues)“。 ## 打开空白议题 diff --git a/translations/zh-CN/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md b/translations/zh-CN/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md index 6c00418f41..8e563a250c 100644 --- a/translations/zh-CN/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md +++ b/translations/zh-CN/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md @@ -1,6 +1,7 @@ --- title: 管理标签 intro: '您可以通过创建、编辑、应用和删除标签，对 {% ifversion fpt %} 议题、拉取请求和讨论{% else %}议题和拉取请求{% endif %}进行分类。' +permissions: '{% data reusables.enterprise-accounts.emu-permission-repo %}' redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/managing-labels - /articles/managing-Labels @@ -30,8 +31,6 @@ topics: 您可以通过创建标签来分类{% ifversion fpt %}议题、拉取请求和讨论{% else %}议题和拉取请求{% endif %}，管理您在 {% data variables.product.product_name %} 上的工作。 您可以在创建标签的仓库中应用标签。 有了标签后，您可以在该仓库内的任何{% ifversion fpt %}议题、拉取请求或讨论{% else %}议题或拉取请求{% endif %}上使用标签、 -对仓库具有读取权限的任何人都能查看和搜索仓库的标签。 对仓库具有鉴定权限的任何人都可以应用/忽略现有标签。 要创建、编辑、应用或删除标签，必须对仓库具有写入权限。 - ## 关于默认标签 {% data variables.product.product_name %} 在每个新仓库中提供默认标签。 您可以使用这些默认标签帮助在仓库中创建标准工作流程。 @@ -58,6 +57,8 @@ topics: ## 创建标签 +Anyone with write access to a repository can create a label. + {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} {% data reusables.project-management.labels %} @@ -69,11 +70,15 @@ topics: ## 应用标记 +Anyone with triage access to a repository can apply and dismiss labels. + 1. 导航到{% ifversion fpt %}议题、拉取请求或讨论{% else %}议题或拉取请求{% endif %}。 1. 在右侧边栏中“Labels（标签）”的右侧，单击 {% octicon "gear" aria-label="The gear icon" %}，然后单击标签。 !["标签"下拉菜单](/assets/images/help/issues/labels-drop-down.png) ## 编辑标签 +Anyone with write access to a repository can edit existing labels. + {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} {% data reusables.project-management.labels %} @@ -85,6 +90,8 @@ topics: ## 删除标签 +Anyone with write access to a repository can delete existing labels. + 删除标签将从议题和拉取请求中删除标签。 {% data reusables.repositories.navigate-to-repo %} diff --git a/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md index 83fb0062f1..3e9245b496 100644 --- a/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md +++ b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md @@ -24,6 +24,8 @@ topics: 对于属于企业帐户的组织，帐单在企业帐户级别管理，并且帐单设置在组织级别不可用。 企业所有者可以为企业帐户中的所有组织设置策略，或者允许组织所有者在组织级别设置策略。 组织所有者无法更改在企业帐户级对组织执行的设置。 如果对组织的策略或设置有疑问，请联系企业帐户的所有者。 +{% data reusables.enterprise-accounts.invite-organization %} + {% data reusables.gated-features.enterprise-accounts %} {% data reusables.organizations.org-ownership-recommendation %} 更多信息请参阅“[管理组织的所有权连续性](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)”。 diff --git a/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md b/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md index 8c18837f2c..4038e72b10 100644 --- a/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md +++ b/translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md @@ -25,6 +25,18 @@ shortTitle: 管理 SAML 访问 {% data reusables.saml.about-linked-identities %} +如果可用，该条目将包含 SCIM 数据。 更多信息请参阅“[关于 SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)”。 + +{% warning %} + +**警告：**对于使用 SCIM 的组织： +- 撤销 {% data variables.product.product_name %} 上链接的用户身份也会删除 SAML 和 SCIM 元数据。 因此，身份提供商无法同步或解除预配已链接的用户身份。 +- 管理员必须通过身份提供商撤销链接的身份。 +- 要撤销链接的身份并通过身份提供商链接其他帐户，管理员可以删除用户并重新分配给 {% data variables.product.product_name %} 应用程序。 For more information, see your identity provider's documentation. + +{% endwarning %} + + {% data reusables.identity-and-permissions.revoking-identity-team-sync %} {% data reusables.profile.access_org %} diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md index 81db196dda..6708a83ebd 100644 --- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md +++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization.md @@ -54,95 +54,96 @@ Some of the features listed below are limited to organizations using {% data var {% endnote %} {% endif %} -| 仓库操作 | 读取 | 分类 | 写入 | 维护 | 管理员 | -|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-----:|:-----:|:-----:|:------------------------------------------------:| -| 从人员或团队的已分配仓库拉取 | **X** | **X** | **X** | **X** | **X** | -| 复刻人员或团队的已分配仓库 | **X** | **X** | **X** | **X** | **X** | -| 编辑和删除自己的评论 | **X** | **X** | **X** | **X** | **X** | -| 打开议题 | **X** | **X** | **X** | **X** | **X** | -| 关闭自己打开的议题 | **X** | **X** | **X** | **X** | **X** | -| 重新打开自己关闭的议题 | **X** | **X** | **X** | **X** | **X** | -| 受理议题 | **X** | **X** | **X** | **X** | **X** | -| 从团队已分配仓库的复刻发送拉取请求 | **X** | **X** | **X** | **X** | **X** | -| 提交拉取请求审查 | **X** | **X** | **X** | **X** | **X** | -| 查看已发布的版本 | **X** | **X** | **X** | **X** | **X** |{% ifversion fpt %} -| 查看 [GitHub Actions 工作流程运行](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **X** | **X** | **X** | **X** | **X** +| 仓库操作 | 读取 | 分类 | 写入 | 维护 | 管理员 | +|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-----:|:-----:|:-----:|:-----------------------------------------------------:| +| 从人员或团队的已分配仓库拉取 | **X** | **X** | **X** | **X** | **X** | +| 复刻人员或团队的已分配仓库 | **X** | **X** | **X** | **X** | **X** | +| 编辑和删除自己的评论 | **X** | **X** | **X** | **X** | **X** | +| 打开议题 | **X** | **X** | **X** | **X** | **X** | +| 关闭自己打开的议题 | **X** | **X** | **X** | **X** | **X** | +| 重新打开自己关闭的议题 | **X** | **X** | **X** | **X** | **X** | +| 受理议题 | **X** | **X** | **X** | **X** | **X** | +| 从团队已分配仓库的复刻发送拉取请求 | **X** | **X** | **X** | **X** | **X** | +| 提交拉取请求审查 | **X** | **X** | **X** | **X** | **X** | +| 查看已发布的版本 | **X** | **X** | **X** | **X** | **X** |{% ifversion fpt %} +| 查看 [GitHub Actions 工作流程运行](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **X** | **X** | **X** | **X** | **X** {% endif %} -| 编辑 wiki | **X** | **X** | **X** | **X** | **X** |{% ifversion fpt %} -| [举报滥用或垃圾内容](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** +| Edit wikis in public repositories | **X** | **X** | **X** | **X** | **X** | +| Edit wikis in private repositories | | | **X** | **X** | **X** |{% ifversion fpt %} +| [举报滥用或垃圾内容](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** {% endif %} -| 应用/忽略标签 | | **X** | **X** | **X** | **X** | -| 创建、编辑、删除标签 | | | **X** | **X** | **X** | -| 关闭、重新打开和分配所有议题与拉取请求 | | **X** | **X** | **X** | **X** |{% ifversion fpt or ghae or ghes > 3.0 %} -| [在拉取请求上启用和禁用自动合并](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** +| 应用/忽略标签 | | **X** | **X** | **X** | **X** | +| 创建、编辑、删除标签 | | | **X** | **X** | **X** | +| 关闭、重新打开和分配所有议题与拉取请求 | | **X** | **X** | **X** | **X** |{% ifversion fpt or ghae or ghes > 3.0 %} +| [在拉取请求上启用和禁用自动合并](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** {% endif %} -| 应用里程碑 | | **X** | **X** | **X** | **X** | -| 标记[重复的议题和拉取请求](/articles/about-duplicate-issues-and-pull-requests) | | **X** | **X** | **X** | **X** | -| 申请[拉取请求审查](/articles/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** | -| Merge a [pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges) | | | **X** | **X** | **X** | -| 推送到（写入）人员或团队的已分配仓库 | | | **X** | **X** | **X** | -| 编辑和删除任何人对提交、拉取请求和议题的评论 | | | **X** | **X** | **X** | -| [隐藏任何人的评论](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **X** | **X** | **X** | -| [锁定对话](/communities/moderating-comments-and-conversations/locking-conversations) | | | **X** | **X** | **X** | -| 转让议题（更多信息请参阅“[将议题转让给其他仓库](/articles/transferring-an-issue-to-another-repository)”） | | | **X** | **X** | **X** | -| [作为仓库的指定代码所有者](/articles/about-code-owners) | | | **X** | **X** | **X** | -| [将拉取请求草稿标记为可供审查](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | -| [将拉取请求转换为草稿](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | -| 提交影响拉取请求可合并性的审查 | | | **X** | **X** | **X** | -| 对拉取请求[应用建议的更改](/articles/incorporating-feedback-in-your-pull-request) | | | **X** | **X** | **X** | -| 创建[状态检查](/articles/about-status-checks) | | | **X** | **X** | **X** |{% ifversion fpt %} -| 创建、编辑、运行、重新运行和取消 [GitHub Actions 工作流程](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** +| 应用里程碑 | | **X** | **X** | **X** | **X** | +| 标记[重复的议题和拉取请求](/articles/about-duplicate-issues-and-pull-requests) | | **X** | **X** | **X** | **X** | +| 申请[拉取请求审查](/articles/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** | +| Merge a [pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges) | | | **X** | **X** | **X** | +| 推送到（写入）人员或团队的已分配仓库 | | | **X** | **X** | **X** | +| 编辑和删除任何人对提交、拉取请求和议题的评论 | | | **X** | **X** | **X** | +| [隐藏任何人的评论](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **X** | **X** | **X** | +| [锁定对话](/communities/moderating-comments-and-conversations/locking-conversations) | | | **X** | **X** | **X** | +| 转让议题（更多信息请参阅“[将议题转让给其他仓库](/articles/transferring-an-issue-to-another-repository)”） | | | **X** | **X** | **X** | +| [作为仓库的指定代码所有者](/articles/about-code-owners) | | | **X** | **X** | **X** | +| [将拉取请求草稿标记为可供审查](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | +| [将拉取请求转换为草稿](/articles/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | +| 提交影响拉取请求可合并性的审查 | | | **X** | **X** | **X** | +| 对拉取请求[应用建议的更改](/articles/incorporating-feedback-in-your-pull-request) | | | **X** | **X** | **X** | +| 创建[状态检查](/articles/about-status-checks) | | | **X** | **X** | **X** |{% ifversion fpt %} +| 创建、编辑、运行、重新运行和取消 [GitHub Actions 工作流程](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** {% endif %} -| 创建和编辑发行版 | | | **X** | **X** | **X** | -| 查看发行版草稿 | | | **X** | **X** | **X** | -| 编辑仓库的说明 | | | | **X** | **X** |{% ifversion fpt or ghae %} -| [查看和安装包](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | -| [发布包](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | -| | | | | | | -| {% ifversion fpt or ghes > 3.0 %}[删除和恢复包](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[删除包](/packages/learn-github-packages/deleting-a-package){% endif %} | | | | | **X** | {% endif %} -| 管理[主题](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** | -| 启用 wiki 和限制 wiki 编辑器 | | | | **X** | **X** | -| 启用项目板 | | | | **X** | **X** | -| 配置[拉取请求合并](/articles/configuring-pull-request-merges) | | | | **X** | **X** | -| 配置[ {% data variables.product.prodname_pages %} 的发布源](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** | -| [推送到受保护分支](/articles/about-protected-branches) | | | | **X** | **X** | -| [创建和编辑仓库社交卡](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% ifversion fpt %} -| 限制[仓库中的交互](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository) | | | | **X** | **X** +| 创建和编辑发行版 | | | **X** | **X** | **X** | +| 查看发行版草稿 | | | **X** | **X** | **X** | +| 编辑仓库的说明 | | | | **X** | **X** |{% ifversion fpt or ghae %} +| [查看和安装包](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | +| [发布包](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | +| | | | | | | +| {% ifversion fpt or ghes > 3.0 %}[删除和恢复包](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[删除包](/packages/learn-github-packages/deleting-a-package){% endif %} | | | | | **X** | {% endif %} +| 管理[主题](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** | +| 启用 wiki 和限制 wiki 编辑器 | | | | **X** | **X** | +| 启用项目板 | | | | **X** | **X** | +| 配置[拉取请求合并](/articles/configuring-pull-request-merges) | | | | **X** | **X** | +| 配置[ {% data variables.product.prodname_pages %} 的发布源](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** | +| [推送到受保护分支](/articles/about-protected-branches) | | | | **X** | **X** | +| [创建和编辑仓库社交卡](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% ifversion fpt %} +| 限制[仓库中的交互](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository) | | | | **X** | **X** {% endif %} -| 删除议题（请参阅“[删除议题](/articles/deleting-an-issue)”） | | | | | **X** | -| 合并受保护分支上的拉取请求（即使没有批准审查） | | | | | **X** | -| [定义仓库的代码所有者](/articles/about-code-owners) | | | | | **X** | -| 将仓库添加到团队（详细信息请参阅“[管理团队对组织仓库的访问](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)”） | | | | | **X** | -| [管理外部协作者对仓库的权限](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | -| [更改仓库的可见性](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | -| 将仓库设为模板（请参阅“[创建模板仓库](/articles/creating-a-template-repository)”） | | | | | **X** | -| 更改仓库设置 | | | | | **X** | -| 管理团队和协作者对仓库的权限 | | | | | **X** | -| 编辑仓库的默认分支 | | | | | **X** |{% ifversion fpt or ghes > 3.0 %} -| 重命名仓库的默认分支（请参阅“[重命名分支](/github/administering-a-repository/renaming-a-branch)”） | | | | | **X** | -| 重命名仓库默认分支以外的分支（请参阅“[重命名分支](/github/administering-a-repository/renaming-a-branch)”） | | | **X** | **X** | **X** +| 删除议题（请参阅“[删除议题](/articles/deleting-an-issue)”） | | | | | **X** | +| 合并受保护分支上的拉取请求（即使没有批准审查） | | | | | **X** | +| [定义仓库的代码所有者](/articles/about-code-owners) | | | | | **X** | +| 将仓库添加到团队（详细信息请参阅“[管理团队对组织仓库的访问](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)”） | | | | | **X** | +| [管理外部协作者对仓库的权限](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | +| [更改仓库的可见性](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | +| 将仓库设为模板（请参阅“[创建模板仓库](/articles/creating-a-template-repository)”） | | | | | **X** | +| 更改仓库设置 | | | | | **X** | +| 管理团队和协作者对仓库的权限 | | | | | **X** | +| 编辑仓库的默认分支 | | | | | **X** |{% ifversion fpt or ghes > 3.0 or ghae-next %} +| 重命名仓库的默认分支（请参阅“[重命名分支](/github/administering-a-repository/renaming-a-branch)”） | | | | | **X** | +| 重命名仓库默认分支以外的分支（请参阅“[重命名分支](/github/administering-a-repository/renaming-a-branch)”） | | | **X** | **X** | **X** {% endif %} -| 管理 web 挂钩和部署密钥 | | | | | **X** |{% ifversion fpt %} -| [管理私有仓库的数据使用设置](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **X** +| 管理 web 挂钩和部署密钥 | | | | | **X** |{% ifversion fpt %} +| [管理私有仓库的数据使用设置](/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository) | | | | | **X** {% endif %} -| [管理仓库的复刻策略](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | -| [将仓库转让给组织](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | -| [删除仓库或将仓库转让到组织外部](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | -| [存档仓库](/articles/about-archiving-repositories) | | | | | **X** |{% ifversion fpt %} -| 显示赞助按钮（请参阅“[在仓库中显示赞助按钮](/articles/displaying-a-sponsor-button-in-your-repository)”）。 | | | | | **X** +| [管理仓库的复刻策略](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | +| [将仓库转让给组织](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | +| [删除仓库或将仓库转让到组织外部](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | +| [存档仓库](/articles/about-archiving-repositories) | | | | | **X** |{% ifversion fpt %} +| 显示赞助按钮（请参阅“[在仓库中显示赞助按钮](/articles/displaying-a-sponsor-button-in-your-repository)”）。 | | | | | **X** {% endif %} -| 创建到外部资源的自动链接引用，如 JIRA 或 Zendesk（请参阅“[配置自动链接以引用外部资源](/articles/configuring-autolinks-to-reference-external-resources)”） | | | | | **X** |{% ifversion fpt %} -| 在仓库中[启用 {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) | | | | **X** | **X** | -| 为 {% data variables.product.prodname_discussions %} [创建和编辑类别](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) | | | | **X** | **X** | -| [将讨论移动到其他类别](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [将讨论转移到](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)新仓库 | | | **X** | **X** | **X** | -| [管理置顶的讨论](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [批量将议题转换为讨论](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | -| [锁定和解锁讨论](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [单独将议题转换为讨论](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [创建新的讨论并对现有讨论发表评论](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** | -| [删除讨论](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion) | | | | **X** | **X** |{% endif %}{% ifversion fpt %} -| 创建 [codespaces](/codespaces/about-codespaces) | | | **X** | **X** | **X** +| 创建到外部资源的自动链接引用，如 JIRA 或 Zendesk（请参阅“[配置自动链接以引用外部资源](/articles/configuring-autolinks-to-reference-external-resources)”） | | | | | **X** |{% ifversion fpt %} +| 在仓库中[启用 {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) | | | | **X** | **X** | +| 为 {% data variables.product.prodname_discussions %} [创建和编辑类别](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository) | | | | **X** | **X** | +| [将讨论移动到其他类别](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [将讨论转移到](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)新仓库 | | | **X** | **X** | **X** | +| [管理置顶的讨论](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [批量将议题转换为讨论](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository) | | | **X** | **X** | **X** | +| [锁定和解锁讨论](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [单独将议题转换为讨论](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | +| [创建新的讨论并对现有讨论发表评论](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** | +| [删除讨论](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion) | | | | **X** | **X** |{% endif %}{% ifversion fpt %} +| 创建 [codespaces](/codespaces/about-codespaces) | | | **X** | **X** | **X** {% endif %} ### 安全功能的权限要求 diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md index 7d699d584d..c8bbce1bd8 100644 --- a/translations/zh-CN/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md +++ b/translations/zh-CN/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md @@ -36,7 +36,7 @@ shortTitle: 禁用或限制操作 {% endif %} -{% ifversion fpt or ghes > 2.22 %} +{% ifversion fpt or ghes > 2.22 or ghae-next %} ## 管理组织的 {% data variables.product.prodname_actions %} 权限 @@ -63,7 +63,12 @@ shortTitle: 禁用或限制操作 {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.settings-sidebar-actions %} -1. 在 **Policies（策略）**下，选择 **Allow select actions（允许选择操作）**并将所需操作添加到列表中。 ![添加操作到允许列表](/assets/images/help/organizations/actions-policy-allow-list.png) +1. 在 **Policies（策略）**下，选择 **Allow select actions（允许选择操作）**并将所需操作添加到列表中。 + {%- ifversion ghes %} + ![添加操作到允许列表](/assets/images/help/organizations/actions-policy-allow-list.png) + {%- else %} + ![添加操作到允许列表](/assets/images/enterprise/github-ae/organizations/actions-policy-allow-list.png) + {%- endif %} 1. 单击 **Save（保存）**。 {% endif %} @@ -71,7 +76,9 @@ shortTitle: 禁用或限制操作 {% ifversion fpt %} ## 配置公共复刻工作流程所需的批准 -{% data reusables.actions.workflow-run-approve-public-fork %} 您可以使用下面的程序为组织配置此行为。 修改此设置会覆盖企业级别的配置集。 +{% data reusables.actions.workflow-run-approve-public-fork %} + +You can configure this behavior for an organization using the procedure below. 修改此设置会覆盖企业级别的配置集。 {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md index b211698538..07211512c9 100644 --- a/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md +++ b/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md @@ -1,6 +1,6 @@ --- -title: Managing the publication of GitHub Pages sites for your organization -intro: 'You can control whether organization members can publish {% data variables.product.prodname_pages %} sites from repositories in the organization{% if currentVersion == "free-pro-team@latest" %} and restrict the visibilities that members can choose for the sites{% endif %}.' +title: 管理组织的 GitHub Pages 站点发布 +intro: '您可以控制组织成员是否可以从组织仓库中发布 {% data variables.product.prodname_pages %} 站点，{% ifversion fpt %}并限制成员是否可以为站点选择可见性{% endif %}。' permissions: 'Organization owners can manage the publication of {% data variables.product.prodname_pages %} sites from repositories in the organization.' product: '{% data reusables.gated-features.pages %}' versions: @@ -13,24 +13,22 @@ redirect_from: topics: - Organizations - Teams +shortTitle: 管理 Pages 站点发布 --- -{% if currentVersion == "free-pro-team@latest" %} -If your organization uses {% data variables.product.prodname_ghe_cloud %}, you can choose to allow organization members to create publicly published sites, privately published sites, both, or neither. Otherwise, you can choose to allow or disallow public publishing. For more information about access control for {% data variables.product.prodname_pages %} sites, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)." +{% ifversion fpt %} +如果您的组织使用 {% data variables.product.prodname_ghe_cloud %}，您可以选择允许组织成员创建公开发布的站点和/或私下发布的站点。 否则，您可以选择允许或禁止公开发布。 有关 {% data variables.product.prodname_pages %} 站点访问权限控制的更多信息，请参阅“[更改 {% data variables.product.prodname_pages %} 站点的可见性](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)”。 {% endif %} -If you disallow publication of {% data variables.product.prodname_pages %} sites, any sites that are already published will remain published. You can manually unpublish the site. For more information, see "[Unpublishing a {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site)." +禁止发布 {% data variables.product.prodname_pages %} 站点后，任何已发布的站点仍将保持已发布状态。 您可以手动取消发布站点。 更多信息请参阅“[取消发布 {% data variables.product.prodname_pages %} 站点](/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site)”。 -{% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} -{% data reusables.organizations.org_settings %} -{% data reusables.organizations.member-privileges %}{% if currentVersion == "free-pro-team@latest" %} -1. Under "Pages creation", select the visibilities you want to allow and deselect the visibilities you want to disallow. - ![Checkboxes to allow or disallow creation of {% data variables.product.prodname_pages %} sites](/assets/images/help/organizations/github-pages-creation-checkboxes.png){% else %} -1. Under "Pages creation", select or deselect **Allow members to publish sites**. - ![Unselected checkbox for "Allow members to publish sites" option](/assets/images/help/organizations/org-settings-pages-disable-publication-checkbox.png){% endif %} -1. Click **Save**. +{% data reusables.profile.org_settings %} +{% data reusables.organizations.member-privileges %}{% ifversion fpt %} +1. 在“Pages creation（页面创建）”下，选择要允许的可见性，取消选择要禁止的可见性。 ![Checkboxes to allow or disallow creation of {% data variables.product.prodname_pages %} sites](/assets/images/help/organizations/github-pages-creation-checkboxes.png)用于启用 Public Pages 的复选框{% else %} +1. 在“Pages creation（页面创建）”下，选择或取消选择 **Allow members to publish sites（允许成员发布站点）**。 ![Unselected checkbox for "Allow members to publish sites" option](/assets/images/help/organizations/org-settings-pages-disable-publication-checkbox.png)用于启用 Public Pages 的复选框{% endif %} +1. 单击 **Save（保存）**。 -### Further reading +## 延伸阅读 -- "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)" +- "[关于 {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)" diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/transferring-organization-ownership.md b/translations/zh-CN/content/organizations/managing-organization-settings/transferring-organization-ownership.md index a6df012556..aa68ec049e 100644 --- a/translations/zh-CN/content/organizations/managing-organization-settings/transferring-organization-ownership.md +++ b/translations/zh-CN/content/organizations/managing-organization-settings/transferring-organization-ownership.md @@ -15,6 +15,13 @@ topics: shortTitle: 转移所有权 --- +{% ifversion fpt %} +{% note %} + +**注：**{% data reusables.enterprise-accounts.invite-organization %} + +{% endnote %}{% endif %} + 1. 如果您是具有*所有者*权限的唯一成员，则授予其他组织成员所有者角色。 更多信息请参阅“[任命组织所有者](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization#appointing-an-organization-owner)”。 2. 联系新的所有者，确保其能够[访问组织的设置](/articles/accessing-your-organization-s-settings)。 {% ifversion fpt %} diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md index 43117e5a38..0589e33284 100644 --- a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md +++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md @@ -13,6 +13,8 @@ topics: shortTitle: 使用 SAML SSO 的 IAM --- +{% data reusables.enterprise-accounts.emu-saml-note %} + ## 关于 SAML SSO {% data reusables.saml.dotcom-saml-explanation %} diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md index a63c4a53b1..bc89ea24be 100644 --- a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md +++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md @@ -12,6 +12,8 @@ topics: - Teams --- +{% data reusables.enterprise-accounts.emu-scim-note %} + 如果在组织中使用 [SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on)，您可以实施 SCIM 来添加、管理和删除组织成员对 {% data variables.product.product_name %} 的访问权限。 例如，管理员可以使用 SCIM 撤销配置组织成员，以及从组织中自动删除成员。 如果您使用 SAML SSO 而不实施 SCIM，将不能自动撤销配置。 当组织成员的会话在其访问权限从 IdP 删除后到期时，他们就会自动从组织中删除。 即使会话已到期，通过授权的令牌也可授予对组织的访问。 要删除访问权限，组织管理员可以手动从组织删除授权的令牌，或者通过 SCIM 自动执行删除。 diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md index 6258048555..c5e1c1cc22 100644 --- a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md +++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md @@ -17,6 +17,8 @@ topics: shortTitle: 管理团队同步 --- +{% data reusables.enterprise-accounts.emu-scim-note %} + {% data reusables.gated-features.okta-team-sync %} ## 关于团队同步 @@ -31,6 +33,8 @@ shortTitle: 管理团队同步 您还可以为企业帐户拥有的组织启用团队同步。 更多信息请参阅“[在企业帐户中实施安全设置](/github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account)”。 +{% data reusables.enterprise-accounts.team-sync-override %} + {% data reusables.identity-and-permissions.team-sync-usage-limits %} ## 启用团队同步 diff --git a/translations/zh-CN/content/organizations/organizing-members-into-teams/creating-a-team.md b/translations/zh-CN/content/organizations/organizing-members-into-teams/creating-a-team.md index 35ba535488..25ff9960f0 100644 --- a/translations/zh-CN/content/organizations/organizing-members-into-teams/creating-a-team.md +++ b/translations/zh-CN/content/organizations/organizing-members-into-teams/creating-a-team.md @@ -25,11 +25,13 @@ topics: {% data reusables.organizations.team_description %} {% data reusables.organizations.create-team-choose-parent %} {% ifversion fpt %} -1. （可选）如果您的组织或企业帐户使用团队同步，要将身份提供程序组连接到您的团队，请使用“Identity Provider Groups（身份提供程序组）”下拉菜单，并选择最多 5 个身份提供程序组。 更多信息请参阅“[同步团队与身份提供程序组](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)”。 ![用于选择身份提供程序组的下拉菜单](/assets/images/help/teams/choose-an-idp-group.png) +1. Optionally, if your organization or enterprise account uses team synchronization or your enterprise uses {% data variables.product.prodname_emus %}, connect an identity provider group to your team. + * If your enterprise uses {% data variables.product.prodname_emus %}, use the "Identity Provider Groups" drop-down menu, and select a single identity provider group to connect to the new team. For more information, "[Managing team memberships with identity provider groups](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)." + * If your organization or enterprise account uses team synchronization, use the "Identity Provider Groups" drop-down menu, and select up to five identity provider groups to connect to the new team. 更多信息请参阅“[同步团队与身份提供程序组](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)”。 ![用于选择身份提供程序组的下拉菜单](/assets/images/help/teams/choose-an-idp-group.png) {% endif %} {% data reusables.organizations.team_visibility %} {% data reusables.organizations.create_team %} -9. （可选）[授予团队访问组织仓库的权限](/articles/managing-team-access-to-an-organization-repository)。 +1. （可选）[授予团队访问组织仓库的权限](/articles/managing-team-access-to-an-organization-repository)。 ## 延伸阅读 diff --git a/translations/zh-CN/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md b/translations/zh-CN/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md index de800e33fb..5b797ee2b0 100644 --- a/translations/zh-CN/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md +++ b/translations/zh-CN/content/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team.md @@ -45,8 +45,11 @@ Any team members that have set their status to "Busy" will not be selected for r 7. 在“How many team members should be assigned to review?（应分配多少团队成员进行审查？）”下，使用下拉菜单选择多个要分配给每个拉取请求的审查者。 ![审查者人数下拉列表](/assets/images/help/teams/review-assignment-number.png) 8. 在“Routing algorithm（路由算法）”下，使用下拉菜单选择要使用的算法。 更多信息请参阅“[路由算法](#routing-algorithms)”。 ![路由算法下拉列表](/assets/images/help/teams/review-assignment-algorithm.png) 9. （可选）要始终跳过某些团队成员，请选择 **Never assign certain team members（永不分配某些团队成员）**。 然后，选择要始终跳过的一个或多个团队成员。 ![永不分配某些团队成员复选框和下拉列表](/assets/images/help/teams/review-assignment-skip-members.png) -10. （可选）要对每个拉取请求审查只通知代码审查分配所选择的团队成员，在“Notifications（通知）”下选择 **If assigning team members, don't notify the entire team（如果分配团队成员，请不要通知整个团队）**。 ![代码审查分配通知](/assets/images/help/teams/review-assignment-notifications.png) -11. 单击 **Save changes（保存更改）**。 +10. Optionally, to only notify the team members chosen by code review assignment for each pull review request, under "Notifications" select **If assigning team members, don't notify the entire team.** ![Code review assignment notifications](/assets/images/help/teams/review-assignment-notifications.png){% ifversion fpt or ghae or ghes > 3.2 %} +11. Optionally, to include members of child teams as potential reviewers when assigning requests, select **Child team members**. +12. Optionally, to count any members whose review has already been requested against the total number of members to assign, select **Count existing requests**. +13. Optionally, to remove the review request from the team when assigning team members, select **Team review request**.{% endif %} +14. 单击 **Save changes（保存更改）**。 ## 禁用代码审查分配 {% data reusables.profile.access_org %} diff --git a/translations/zh-CN/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/zh-CN/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md index 01fab06953..563fec94aa 100644 --- a/translations/zh-CN/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md +++ b/translations/zh-CN/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md @@ -16,6 +16,8 @@ shortTitle: 与 IdP 同步 {% data reusables.gated-features.okta-team-sync %} +{% data reusables.enterprise-accounts.emu-scim-note %} + ## 关于团队同步 {% data reusables.identity-and-permissions.about-team-sync %} @@ -26,6 +28,8 @@ shortTitle: 与 IdP 同步 {% data variables.product.prodname_dotcom %} 团队连接到 IdP 组后，您的 IdP 管理员必须通过身份提供程序进行团队成员资格更改。 您不能在 {% data variables.product.product_name %} 上{% ifversion fpt %}或使用 API{% endif %} 管理团队成员资格。 +{% ifversion fpt %}{% data reusables.enterprise-accounts.team-sync-override %}{% endif %} + {% ifversion fpt %} 通过 IdP 进行的所有团队成员资格更改都将在 {% data variables.product.product_name %} 审核日志中显示为团队同步自动程序所进行的更改。 您的 IdP 会将团队成员数据发送至 {% data variables.product.prodname_dotcom %}，每小时一次。 将团队连接到 IdP 组可能会删除一些团队成员。 更多信息请参阅“[已同步团队成员的要求](#requirements-for-members-of-synchronized-teams)”。 {% endif %} @@ -54,8 +58,6 @@ shortTitle: 与 IdP 同步 为避免无意中删除团队成员，建议在组织或企业帐户中强制实施 SAML SSO，创建新团队以同步成员资格数据，并在同步现有团队之前检查 IdP 组成员资格。 For more information, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)" and "[Enforcing SAML single sign-on for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account)." -如果您的组织由企业帐户拥有，则对企业帐户启用团队同步将覆盖组织级的团队同步设置。 更多信息请参阅“[管理企业帐户中组织的团队同步](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)”。 - {% endif %} ## 基本要求 diff --git a/translations/zh-CN/content/packages/learn-github-packages/installing-a-package.md b/translations/zh-CN/content/packages/learn-github-packages/installing-a-package.md index 9254e80d15..c5e138b427 100644 --- a/translations/zh-CN/content/packages/learn-github-packages/installing-a-package.md +++ b/translations/zh-CN/content/packages/learn-github-packages/installing-a-package.md @@ -18,7 +18,7 @@ versions: ## 关于包的安装 -您可以搜索 {% data variables.product.product_name %}，在 {% data variables.product.prodname_registry %} 中找到可安装在自己项目中的包。 更多信息请参阅“[搜索 {% data variables.product.prodname_registry %} 中的包](/github/searching-for-information-on-github/searching-for-packages)”。 +您可以搜索 {% data variables.product.product_name %}，在 {% data variables.product.prodname_registry %} 中找到可安装在自己项目中的包。 更多信息请参阅“[搜索 {% data variables.product.prodname_registry %} 中的包](/search-github/searching-on-github/searching-for-packages)”。 找到包后，您可以在包页面上阅读包的说明以及安装和使用说明。 diff --git a/translations/zh-CN/content/packages/learn-github-packages/viewing-packages.md b/translations/zh-CN/content/packages/learn-github-packages/viewing-packages.md index 6666cd6fe2..893ae18bd2 100644 --- a/translations/zh-CN/content/packages/learn-github-packages/viewing-packages.md +++ b/translations/zh-CN/content/packages/learn-github-packages/viewing-packages.md @@ -64,4 +64,4 @@ versions: ## 延伸阅读 -- “[搜索包](/github/searching-for-information-on-github/searching-for-packages)” +- “[搜索包](/search-github/searching-on-github/searching-for-packages)” diff --git a/translations/zh-CN/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md b/translations/zh-CN/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md index 3e8a72ac57..85a52ddd72 100644 --- a/translations/zh-CN/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md +++ b/translations/zh-CN/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md @@ -15,8 +15,6 @@ shortTitle: 使用 Actions 发布和安装 {% data reusables.package_registry.packages-ghes-release-stage %} {% data reusables.package_registry.packages-ghae-release-stage %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## 关于 {% data variables.product.prodname_registry %} 与 {% data variables.product.prodname_actions %} diff --git a/translations/zh-CN/content/packages/quickstart.md b/translations/zh-CN/content/packages/quickstart.md index dbc2fdfcbb..780f07eef1 100644 --- a/translations/zh-CN/content/packages/quickstart.md +++ b/translations/zh-CN/content/packages/quickstart.md @@ -10,8 +10,6 @@ shortTitle: 快速入门 --- {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.ae-beta %} -{% data reusables.actions.ae-self-hosted-runners-notice %} ## 简介 diff --git a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md index cb76c158f2..785674b270 100644 --- a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md +++ b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md @@ -160,7 +160,11 @@ $ npm login --scope=@OWNER --registry=https://HOSTNAME/_regist 默认情况下，您可以从一个组织添加包。 更多信息请参阅“[从其他组织安装包](#installing-packages-from-other-organizations)”。 -还需要将 *.npmrc* 文件添加到项目，使所有安装包的请求都会通过 {% data variables.product.prodname_registry %}。 通过 {% data variables.product.prodname_registry %} 路由所有包请求时，您可以使用 *npmjs.com* 作用域内和作用域外的包。 更多信息请参阅 npm 文档中的“[npm 作用域](https://docs.npmjs.com/misc/scope)”。 +You also need to add the *.npmrc* file to your project so that all requests to install packages will {% ifversion ghae %}be routed to{% else %}go through{% endif %} {% data variables.product.prodname_registry %}. {% ifversion fpt or ghes > 2.21 %}When you route all package requests through {% data variables.product.prodname_registry %}, you can use both scoped and unscoped packages from *npmjs.org*. For more information, see "[npm-scope](https://docs.npmjs.com/misc/scope)" in the npm documentation.{% endif %} + +{% ifversion ghae %} +By default, you can only use npm packages hosted on your enterprise, and you will not be able to use unscoped packages. For more information on package scoping, see "[npm-scope](https://docs.npmjs.com/misc/scope)" in the npm documentation. If required, {% data variables.product.prodname_dotcom %} support can enable an upstream proxy to npmjs.org. Once an upstream proxy is enabled, if a requested package isn't found on your enterprise, {% data variables.product.prodname_registry %} makes a proxy request to npmjs.org. +{% endif %} {% data reusables.package_registry.authenticate-step %} {% data reusables.package_registry.create-npmrc-owner-step %} diff --git a/translations/zh-CN/content/pages/getting-started-with-github-pages/about-github-pages.md b/translations/zh-CN/content/pages/getting-started-with-github-pages/about-github-pages.md index 36bee4363d..b5e60a93c0 100644 --- a/translations/zh-CN/content/pages/getting-started-with-github-pages/about-github-pages.md +++ b/translations/zh-CN/content/pages/getting-started-with-github-pages/about-github-pages.md @@ -1,6 +1,6 @@ --- -title: About GitHub Pages -intro: 'You can use {% data variables.product.prodname_pages %} to host a website about yourself, your organization, or your project directly from a {% data variables.product.product_name %} repository.' +title: 关于 GitHub Pages +intro: '您可以使用 {% data variables.product.prodname_pages %} 直接从 {% data variables.product.product_name %} 仓库托管关于自己、您的组织或您的项目的站点。' redirect_from: - /articles/what-are-github-pages/ - /articles/what-is-github-pages/ @@ -19,132 +19,124 @@ topics: - Pages --- -### About {% data variables.product.prodname_pages %} +## 关于 {% data variables.product.prodname_pages %} -{% data variables.product.prodname_pages %} is a static site hosting service that takes HTML, CSS, and JavaScript files straight from a repository on {% data variables.product.product_name %}, optionally runs the files through a build process, and publishes a website. You can see examples of {% data variables.product.prodname_pages %} sites in the [{% data variables.product.prodname_pages %} examples collection](https://github.com/collections/github-pages-examples). +{% data variables.product.prodname_pages %} 是一项静态站点托管服务，它直接从 {% data variables.product.product_name %} 上的仓库获取 HTML、CSS 和 JavaScript 文件，（可选）通过构建过程运行文件，然后发布网站。 您可以在 [{% data variables.product.prodname_pages %} 示例集合](https://github.com/collections/github-pages-examples)中查看 {% data variables.product.prodname_pages %} 站点的示例。 -{% if currentVersion == "free-pro-team@latest" %} -You can host your site on {% data variables.product.prodname_dotcom %}'s `github.io` domain or your own custom domain. For more information, see "[Using a custom domain with {% data variables.product.prodname_pages %}](/articles/using-a-custom-domain-with-github-pages)." +{% ifversion fpt %} +您可以在 {% data variables.product.prodname_dotcom %} 的 `github.io` 域或自己的自定义域上托管站点。 更多信息请参阅“[对 {% data variables.product.prodname_pages %} 使用自定义域](/articles/using-a-custom-domain-with-github-pages)”。 {% endif %} -{% if currentVersion == "free-pro-team@latest" %} -{% data reusables.pages.about-private-publishing %} For more information, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)." +{% ifversion fpt %} +{% data reusables.pages.about-private-publishing %}更多信息请参阅“[更改 {% data variables.product.prodname_pages %} 站点的可见性](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)”。 {% endif %} -To get started, see "[Creating a {% data variables.product.prodname_pages %} site](/articles/creating-a-github-pages-site)." +要开始使用，请参阅“[创建 {% data variables.product.prodname_pages %} 站点](/articles/creating-a-github-pages-site)”。 -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@3.0" %} -Organization owners can disable the publication of {% data variables.product.prodname_pages %} sites from the organization's repositories. 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)." +{% ifversion fpt or ghes > 3.0 %} +组织所有者可禁止从组织的仓库发布 {% data variables.product.prodname_pages %} 站点。 更多信息请参阅“[管理组织的 {% data variables.product.prodname_pages %} 站点发布](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)”。 {% endif %} -### Types of {% data variables.product.prodname_pages %} sites +## {% data variables.product.prodname_pages %} 站点的类型 -There are three types of {% data variables.product.prodname_pages %} sites: project, user, and organization. Project sites are connected to a specific project hosted on {% data variables.product.product_name %}, such as a JavaScript library or a recipe collection. User and organization sites are connected to a specific {% data variables.product.product_name %} account. +有三种类型的 {% data variables.product.prodname_pages %} 站点：项目、用户和组织。 项目站点连接到 {% data variables.product.product_name %} 上托管的特定项目，例如 JavaScript 库或配方集合。 用户和组织站点连接到特定的 {% data variables.product.product_name %} 帐户。 -To publish a user site, you must create a repository owned by your user account that's named {% if currentVersion == "free-pro-team@latest" %}`.github.io`{% else %}`.`{% endif %}. To publish an organization site, you must create a repository owned by an organization that's named {% if currentVersion == "free-pro-team@latest" %}`.github.io`{% else %}`.`{% endif %}. {% if currentVersion == "free-pro-team@latest" %}Unless you're using a custom domain, user and organization sites are available at `http(s)://.github.io` or `http(s)://.github.io`.{% elsif currentVersion == "github-ae@latest" %}User and organization sites are available at `http(s)://pages./` or `http(s)://pages./`.{% endif %} +要发布用户站点，必须创建用户帐户所拥有的名为 {% ifversion fpt %}`.github.io`{% else %}` 的仓库。`{% endif %}. 要发布组织站点，必须创建名为 {% ifversion fpt %}`.github.io`{% else %}`.`{% endif %} 的组织所拥有的仓库。 {% ifversion fpt %}除非您使用的是自定义域，否则用户和组织站点位于 `http(s)://.github.io` 或 `http(s)://.github.io`。{% elsif ghae %}用户和组织站点位于 `http(s)://pages./` 或 `http(s)://pages./`。{% endif %} -The source files for a project site are stored in the same repository as their project. {% if currentVersion == "free-pro-team@latest" %}Unless you're using a custom domain, project sites are available at `http(s)://.github.io/` or `http(s)://.github.io/`.{% elsif currentVersion == "github-ae@latest" %}Project sites are available at `http(s)://pages.///` or `http(s)://pages.///`.{% endif %} +项目站点的源文件与其项目存储在同一个仓库中。 {% ifversion fpt %}除非您使用的是自定义域，否则项目站点位于 `http(s)://.github.io/` 或 `http(s)://.github.io/`。{% elsif ghae %}项目站点位于 `http(s)://pages.///` 或 `http(s)://pages.///`。{% endif %} -{% if currentVersion == "free-pro-team@latest" %} -If you publish your site privately, the URL for your site will be different. For more information, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)." +{% ifversion fpt %} +如果您私下发布站点，则站点的 URL 将有所不同。 更多信息请参阅“[更改 {% data variables.product.prodname_pages %} 站点的可见性](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)”。 {% endif %} -{% if currentVersion == "free-pro-team@latest" %} -For more information about how custom domains affect the URL for your site, see "[About custom domains and {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages)." +{% ifversion fpt %} +有关自定义域如何影响站点 URL 的更多详细，请参阅“[关于自定义域和 {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages)”。 {% endif %} -You can only create one user or organization site for each account on {% data variables.product.product_name %}. Project sites, whether owned by an organization or a user account, are unlimited. +您只能为 {% data variables.product.product_name %} 上的每个帐户创建一个用户或组织站点。 项目站点（无论是组织还是用户帐户拥有）没有限制。 -{% if enterpriseServerVersions contains currentVersion %} -The URL where your site is available depends on whether subdomain isolation is enabled for {% data variables.product.product_location %}. +{% ifversion ghes %} +您的站点可用的 URL 取决于是否为 {% data variables.product.product_location %} 启用了子域隔离。 -| Type of site | Subdomain isolation enabled | Subdomain isolation disabled | -| ------------ | --------------------------- | ---------------------------- | -User | `http(s)://pages./` | `http(s):///pages/` | -Organization | `http(s)://pages./` | `http(s):///pages/` | -Project site owned by user account | `http(s)://pages.///` | `http(s):///pages///` -Project site owned by organization account | `http(s)://pages.///` | `http(s):///pages///` +| 站点类型 | 子域隔离已启用 | 子域隔离已禁用 | +| ---- | ------- | ------- | +| | | | + 用户 | -For more information, see "[Enabling subdomain isolation](/enterprise/{{ currentVersion }}/admin/installation/enabling-subdomain-isolation)" or contact your site administrator. +`http(s)://pages./` | `http(s):///pages/` | 组织 | `http(s)://pages./` | `http(s):///pages/` | 用户帐户拥有的项目站点 | `http(s)://pages.///` | `http(s):///pages///` 组织帐户拥有的项目站点 | `http(s)://pages.///` | `http(s):///pages///` + +更多信息请参阅“[启用子域隔离](/enterprise/{{ currentVersion }}/admin/installation/enabling-subdomain-isolation)”或联系您的站点管理员。 {% endif %} -{% if currentVersion == "free-pro-team@latest" %} -{% note %} +## {% data variables.product.prodname_pages %} 站点的发布来源 -**Note:** Repositories using the legacy `.github.com` naming scheme will still be published, but visitors will be redirected from `http(s)://.github.com` to `http(s)://.github.io`. If both a `.github.com` and `.github.io` repository exist, only the `.github.io` repository will be published. - -{% endnote %} -{% endif %} - -### Publishing sources for {% data variables.product.prodname_pages %} sites - -The publishing source for your {% data variables.product.prodname_pages %} site is the branch and folder where the source files for your site are stored. +{% data variables.product.prodname_pages %} 站点的发布来源是存储站点源文件的分支和文件夹。 {% data reusables.pages.private_pages_are_public_warning %} -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" or currentVersion == "github-ae@latest" %} +{% ifversion fpt or ghes > 2.22 or ghae %} -If the default publishing source exists in your repository, {% data variables.product.prodname_pages %} will automatically publish a site from that source. The default publishing source for user and organization sites is the root of the default branch for the repository. The default publishing source for project sites is the root of the `gh-pages` branch. +如果默认发布源在您的仓库中，{% data variables.product.prodname_pages %} 将自动从该源发布站点。 用户和组织站点的默认发布源是仓库默认分支的根目录。 项目站点的默认发布来源是 `gh-pages` 分支的根目录。 -If you want to keep the source files for your site in a different location, you can change the publishing source for your site. You can publish your site from any branch in the repository, either from the root of the repository on that branch, `/`, or from the `/docs` folder on that branch. For more information, see "[Configuring a publishing source for your {% data variables.product.prodname_pages %} site](/articles/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source)." +如果要将站点的源文件保留在不同的位置，您可以更改站点的发布源。 您可以从仓库的任何分支发布站点 - 从该分支上仓库的根目录 `/` 或从该分支上的 `/docs` 文件夹发布。 更多信息请参阅“[配置 {% data variables.product.prodname_pages %} 站点的发布来源](/articles/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source)”。 -If you choose the `/docs` folder of any branch as your publishing source, {% data variables.product.prodname_pages %} will read everything to publish your site{% if currentVersion == "free-pro-team@latest" %}, including the _CNAME_ file,{% endif %} from the `/docs` folder.{% if currentVersion == "free-pro-team@latest" %} For example, when you edit your custom domain through the {% data variables.product.prodname_pages %} settings, the custom domain will write to `/docs/CNAME`. For more information about _CNAME_ files, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)."{% endif %} +如果选择任何分支的 `/docs` 文件夹作为您的发布来源，{% data variables.product.prodname_pages %} 将读取 `/docs` 文件夹中的所有内容以发布您的站点{% ifversion fpt %}（包括 _CNAME_ 文件）{% endif %}。{% ifversion fpt %}例如，当您通过 {% data variables.product.prodname_pages %} 设置编辑自定义域时，该自定义域将写入 `/docs/CNAME`。 有关 _CNAME_ 文件的更多信息，请参阅“[管理 {% data variables.product.prodname_pages %} 站点的自定义域](/articles/managing-a-custom-domain-for-your-github-pages-site)”。{% endif %} {% else %} -The default publishing source for user and organization sites is the `master` branch. If the repository for your user or organization site has a `master` branch, your site will publish automatically from that branch. You cannot choose a different publishing source for user or organization sites. +用户和组织站点的默认发布来源是 `master` 分支。 如果用户和组织站点的仓库是 `master` 分支，您的站点将从该分支自动发布。 您无法为用户或组织站点选择不同的发布来源。 -The default publishing source for a project site is the `gh-pages` branch. If the repository for your project site has a `gh-pages` branch, your site will publish automatically from that branch. +项目站点的默认发布来源是 `gh-pages` 分支。 如果项目站点的仓库有 `gh-pages` 分支，您的站点将从该分支自动发布。 -Project sites can also be published from the `master` branch or a `/docs` folder on the `master` branch. To publish your site from one of these sources, you must configure a different publishing source. For more information, see "[Configuring a publishing source for your {% data variables.product.prodname_pages %} site](/articles/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source)." +项目站点也可以从 `master` 分支或 `master` 分支上的 `/docs` 文件夹发布。 要从这些来源之一发布站点，您必须配置不同的发布来源。 更多信息请参阅“[配置 {% data variables.product.prodname_pages %} 站点的发布来源](/articles/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source)”。 -If you choose the `/docs` folder of the `master` branch as your publishing source, {% data variables.product.prodname_pages %} will read everything to publish your site{% if currentVersion == "free-pro-team@latest" %}, including the _CNAME_ file,{% endif %} from the `/docs` folder.{% if currentVersion == "free-pro-team@latest" %} For example, when you edit your custom domain through the {% data variables.product.prodname_pages %} settings, the custom domain will write to `/docs/CNAME`. For more information about _CNAME_ files, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)."{% endif %} +如果选择 `master` 分支的 `/docs` 文件夹作为您的发布来源，{% data variables.product.prodname_pages %} 将读取 `/docs` 文件夹中的所有内容以发布您的站点{% ifversion fpt %}（包括 _CNAME_ 文件）{% endif %}。{% ifversion fpt %}例如，当您通过 {% data variables.product.prodname_pages %} 设置编辑自定义域时，该自定义域将写入 `/docs/CNAME`。 有关 _CNAME_ 文件的更多信息，请参阅“[管理 {% data variables.product.prodname_pages %} 站点的自定义域](/articles/managing-a-custom-domain-for-your-github-pages-site)”。{% endif %} -You cannot publish your project site from any other branch, even if the default branch is not `master` or `gh-pages`. +您不能从任何其他分支发布项目站点，即使默认分支不是 `master` 或 `gh-pages`。 {% endif %} -### Static site generators +## 静态站点生成器 -{% data variables.product.prodname_pages %} publishes any static files that you push to your repository. You can create your own static files or use a static site generator to build your site for you. You can also customize your own build process locally or on another server. We recommend Jekyll, a static site generator with built-in support for {% data variables.product.prodname_pages %} and a simplified build process. For more information, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll)." +{% data variables.product.prodname_pages %} 会发布您推送到仓库的任何静态文件。 您可以创建自己的静态文件或使用静态站点生成器为您构建站点。 您还可以在本地或其他服务器上自定义自己的构建过程。 我们建议使用 Jekyll，它是一个静态站点生成器，内置 {% data variables.product.prodname_pages %} 支持和简化的构建流程。 更多信息请参阅“[关于 {% data variables.product.prodname_pages %} 和 Jekyll](/articles/about-github-pages-and-jekyll)”。 -{% data variables.product.prodname_pages %} will use Jekyll to build your site by default. If you want to use a static site generator other than Jekyll, disable the Jekyll build process by creating an empty file called `.nojekyll` in the root of your publishing source, then follow your static site generator's instructions to build your site locally. +默认情况下，{% data variables.product.prodname_pages %} 将使用 Jekyll 来构建您的站点。 如果您想使用除 Jekyll 以外的静态站点生成器，通过在发布来源的根目录中创建一个名为 `.nojekyll` 的空文件来禁用 Jekyll 构建过程，然后按照静态站点生成器的说明在 本地构建站点。 -{% data variables.product.prodname_pages %} does not support server-side languages such as PHP, Ruby, or Python. +{% data variables.product.prodname_pages %} 不支持服务器端语言，例如 PHP、Ruby 或 Python。 -### Guidelines for using {% data variables.product.prodname_pages %} +## 使用 {% data variables.product.prodname_pages %} 的指南 -{% if currentVersion == "free-pro-team@latest" %} -- {% data variables.product.prodname_pages %} sites created after June 15, 2016 and using `github.io` domains are served over HTTPS. If you created your site before June 15, 2016, you can enable HTTPS support for traffic to your site. For more information, see "[Securing your {% data variables.product.prodname_pages %} with HTTPS](/articles/securing-your-github-pages-site-with-https)." +{% ifversion fpt %} +- 2016 年 6 月 15 日后创建并使用 `github.io` 域的 {% data variables.product.prodname_pages %} 站点通过 HTTPS 提供服务。 如果您在 2016 年 6 月 15 日之前创建站点，您可以为站点的流量启用 HTTPS 支持。 更多信息请参阅“[使用 HTTPS 保护 {% data variables.product.prodname_pages %}](/articles/securing-your-github-pages-site-with-https)”。 - {% data reusables.pages.no_sensitive_data_pages %} -- Your use of {% data variables.product.prodname_pages %} is subject to the [GitHub Terms of Service](/articles/github-terms-of-service/), including the prohibition on reselling. +- 您对 {% data variables.product.prodname_pages %} 的使用受 [GitHub 服务条款](/articles/github-terms-of-service/)的约束，包括禁止转售。 -#### Usage limits +### 使用限制 {% endif %} -{% data variables.product.prodname_pages %} sites are subject to the following usage limits: +{% data variables.product.prodname_pages %} 站点受到以下使用限制的约束： - - {% data variables.product.prodname_pages %} source repositories have a recommended limit of 1GB.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[What is my disk quota?"](/articles/what-is-my-disk-quota/#file-and-repository-size-limitations){% endif %} - - Published {% data variables.product.prodname_pages %} sites may be no larger than 1 GB. -{% if currentVersion == "free-pro-team@latest" %} - - {% data variables.product.prodname_pages %} sites have a *soft* bandwidth limit of 100GB per month. - - {% data variables.product.prodname_pages %} sites have a *soft* limit of 10 builds per hour. + - {% data variables.product.prodname_pages %} 源仓库建议的限制为 1GB。{% ifversion fpt %}更多信息请参阅“[我的磁盘配额是多少？](/articles/what-is-my-disk-quota/#file-and-repository-size-limitations)”{% endif %} + - 发布的 {% data variables.product.prodname_pages %} 站点不得超过 1 GB。 +{% ifversion fpt %} + - {% data variables.product.prodname_pages %} 站点的*软*带宽限制为每月 100GB。 + - {% data variables.product.prodname_pages %} 站点的*软*限制为每小时 10 次构建。 -If your site exceeds these usage quotas, we may not be able to serve your site, or you may receive a polite email from {% data variables.contact.contact_support %} suggesting strategies for reducing your site's impact on our servers, including putting a third-party content distribution network (CDN) in front of your site, making use of other {% data variables.product.prodname_dotcom %} features such as releases, or moving to a different hosting service that might better fit your needs. +如果您的站点超出这些使用配额，我们可能无法为您的站点提供服务；或者您可能收到来自 {% data variables.contact.contact_support %} 的礼貌电子邮件，建议降低站点对服务器影响的策略，包括将第三方内容分发网络 (CDN) 置于您的站点前，利用其他 {% data variables.product.prodname_dotcom %} 功能（如发行版）或转用可能更符合您需求的其他托管服务。 -#### Prohibited uses +### 禁止使用 -{% data variables.product.prodname_pages %} is not intended for or allowed to be used as a free web hosting service to run your online business, e-commerce site, or any other website that is primarily directed at either facilitating commercial transactions or providing commercial software as a service (SaaS). +{% data variables.product.prodname_pages %} 并非旨在用于或允许用作免费的 Web 托管服务来运行您的在线业务、电子商务站点或主要针对促进商业交易或提供商业软件即服务 (SaaS) 的任何其他网站。 -In addition, {% data variables.product.prodname_dotcom %} does not allow {% data variables.product.prodname_pages %} to be used for certain purposes or activities. For a list of prohibited uses, see "[{% data variables.product.prodname_dotcom %}'s Additional Product Terms for {% data variables.product.prodname_pages %}](/github/site-policy/github-additional-product-terms#4-pages)." +此外，{% data variables.product.prodname_dotcom %} 不允许 {% data variables.product.prodname_pages %} 用于某些目的或活动。 有关禁止用途的列表，请参阅“[{% data variables.product.prodname_dotcom %} {% data variables.product.prodname_pages %} 附加产品条款](/github/site-policy/github-additional-product-terms#4-pages)”。 {% endif %} -### MIME types on {% data variables.product.prodname_pages %} +## {% data variables.product.prodname_pages %} 上的 MIME 类型 -A MIME type is a header that a server sends to a browser, providing information about the nature and format of the files the browser requested. {% data variables.product.prodname_pages %} supports more than 750 MIME types across thousands of file extensions. The list of supported MIME types is generated from the [mime-db project](https://github.com/jshttp/mime-db). +MIME 类型是服务器发送到浏览器的标头，提供有关浏览器所请求文件性质和格式的信息。 {% data variables.product.prodname_pages %} 支持数千种文件扩展名中 750 多种 MIME 类型。 支持的 MIME 类型列表从 [mime-db project](https://github.com/jshttp/mime-db) 生成。 -While you can't specify custom MIME types on a per-file or per-repository basis, you can add or modify MIME types for use on {% data variables.product.prodname_pages %}. For more information, see [the mime-db contributing guidelines](https://github.com/jshttp/mime-db#adding-custom-media-types). +虽然无法基于每个文件或每个仓库指定自定义 MIME 类型，但您可以添加或修改 MIME 类型以在 {% data variables.product.prodname_pages %} 上使用。 更多信息请参阅 [mime-db 参与指南](https://github.com/jshttp/mime-db#adding-custom-media-types)。 -### Further reading +## 延伸阅读 -- [{% data variables.product.prodname_pages %}](https://lab.github.com/githubtraining/github-pages) on {% data variables.product.prodname_learning %} +- {% data variables.product.prodname_learning %} 上的 [{% data variables.product.prodname_pages %}](https://lab.github.com/githubtraining/github-pages) - "[{% data variables.product.prodname_pages %}](/rest/reference/repos#pages)" diff --git a/translations/zh-CN/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md b/translations/zh-CN/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md index 6e0c2b477c..c040102fed 100644 --- a/translations/zh-CN/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md +++ b/translations/zh-CN/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md @@ -12,7 +12,11 @@ shortTitle: 更改站点可见性 ## 关于 {% data variables.product.prodname_pages %} 站点的访问控制 -如果您的项目站点是从使用 {% data variables.product.prodname_ghe_cloud %} 的组织拥有的私有或内部仓库发布的，您可以管理站点的访问控制。 通过访问控制，您可以选择将站点公开发布给互联网上的任何人，也可以选择私下发布给对仓库拥有读取权限的人。 私下发布的站点可用于与企业成员分享您的内部文档或知识库。 您无法管理组织站点的访问控制。 有关 {% data variables.product.prodname_pages %} 站点类型的更多信息，请参阅“[关于 {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)”。 +With access control for {% data variables.product.prodname_pages %}, you can restrict access to your {% data variables.product.prodname_pages %} site by publishing the site privately. A privately published site can only be accessed by people with read access to the repository the site is published from. You can use privately published sites to share your internal documentation or knowledge base with members of your enterprise. + +If your enterprise uses {% data variables.product.prodname_emus %}, all {% data variables.product.prodname_pages %} sites are privately published. For more information about {% data variables.product.prodname_emus %}, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." + +If your organization uses {% data variables.product.prodname_ghe_cloud %} without {% data variables.product.prodname_emus %}, you can choose to publish your sites privately or publicly to anyone on the internet. Access control is available for project sites that are published from a private or internal repository that are owned by the organization. 您无法管理组织站点的访问控制。 有关 {% data variables.product.prodname_pages %} 站点类型的更多信息，请参阅“[关于 {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)”。 私下发布的站点与公开发布的站点位于不同的子域中。 这可确保您的 {% data variables.product.prodname_pages %} 站点从发布之日起是安全的： diff --git a/translations/zh-CN/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md b/translations/zh-CN/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md index 43e767a1c5..e65b8eadf9 100644 --- a/translations/zh-CN/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md +++ b/translations/zh-CN/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md @@ -22,6 +22,12 @@ shortTitle: 使用 HTTPS 保护站点 {% data reusables.pages.private_pages_are_public_warning %} +{% note %} + +**Note:** RFC3280 states that the maximum length of the common name should be 64 characters. Therefore, the entire domain name of your {% data variables.product.prodname_pages %} site must be less than 64 characters long for a certificate to be successfully created. + +{% endnote %} + ## 对您的 {% data variables.product.prodname_pages %} 站点强制实施 HTTPS {% data reusables.pages.navigate-site-repo %} diff --git a/translations/zh-CN/content/repositories/archiving-a-github-repository/archiving-repositories.md b/translations/zh-CN/content/repositories/archiving-a-github-repository/archiving-repositories.md index 44ba565fb5..e0d537964b 100644 --- a/translations/zh-CN/content/repositories/archiving-a-github-repository/archiving-repositories.md +++ b/translations/zh-CN/content/repositories/archiving-a-github-repository/archiving-repositories.md @@ -32,7 +32,7 @@ topics: 当仓库存档后，其议题、拉取请求、代码、标签、重要事件、项目、wiki、版本、提交、标记、分支、反应、代码扫描警报和注解都会变成只读。 要更改存档的仓库，必须先对仓库取消存档。 -您可以搜索已存档的仓库。 更多信息请参阅“[搜索仓库](/articles/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)”。 更多信息请参阅“[搜索仓库](/articles/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)”。 更多信息请参阅“[搜索议题和拉取请求](/articles/searching-issues-and-pull-requests/#search-based-on-whether-a-repository-is-archived)”。 +您可以搜索已存档的仓库。 更多信息请参阅“[搜索仓库](/search-github/searching-on-github/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)”。 更多信息请参阅“[搜索仓库](/articles/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)”。 更多信息请参阅“[搜索议题和拉取请求](/search-github/searching-on-github/searching-issues-and-pull-requests/#search-based-on-whether-a-repository-is-archived)”。 ## 存档仓库 diff --git a/translations/zh-CN/content/repositories/archiving-a-github-repository/backing-up-a-repository.md b/translations/zh-CN/content/repositories/archiving-a-github-repository/backing-up-a-repository.md index e1aad32b04..171d9fcb76 100644 --- a/translations/zh-CN/content/repositories/archiving-a-github-repository/backing-up-a-repository.md +++ b/translations/zh-CN/content/repositories/archiving-a-github-repository/backing-up-a-repository.md @@ -36,7 +36,7 @@ topics: - [项目](/rest/reference/projects#list-repository-projects) {% endif %} -一旦您拥有{% ifversion ghes or ghae %}所有要备份内容的本地版本，您就可以创建一个 zip 存档并{% else %}下载您的存档。您可以{% endif %}将其复制到外部硬盘和/或将其上传到基于云的备份服务，例如 [Google Drive](https://www.google.com/drive/) 或 [Dropbox](https://www.dropbox.com/)。 +Once you have {% ifversion ghes or ghae %}a local version of all the content you want to back up, you can create a zip archive and {% else %}downloaded your archive, you can {% endif %}copy it to an external hard drive and/or upload it to a cloud-based backup or storage service such as [Azure Blob Storage](https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-overview/), [Google Drive](https://www.google.com/drive/) or [Dropbox](https://www.dropbox.com/). {% ifversion fpt %} ## 第三方备份工具 diff --git a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md index fc12f26fa8..09b5ee336a 100644 --- a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md +++ b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md @@ -28,13 +28,13 @@ shortTitle: 更改默认分支 {% endnote %} {% endif %} -{% ifversion fpt or ghes > 3.0 %} +{% ifversion fpt or ghes > 3.0 or ghae-next %} 您也可以重命名默认分支。 更多信息请参阅“[重命名分支](/github/administering-a-repository/renaming-a-branch)”。 {% endif %} -{% ifversion fpt or ghes > 2.22 %} +{% ifversion fpt or ghes > 2.22 or ghae-next %} {% data reusables.branches.set-default-branch %} diff --git a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md index d70b5a5a53..f7407774ea 100644 --- a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md +++ b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md @@ -5,6 +5,7 @@ permissions: People with write permissions to a repository can rename a branch i versions: fpt: '*' ghes: '>=3.1' + ghae: next topics: - Repositories redirect_from: diff --git a/translations/zh-CN/content/repositories/creating-and-managing-repositories/about-repositories.md b/translations/zh-CN/content/repositories/creating-and-managing-repositories/about-repositories.md index 5e0840491e..0dff94b85c 100644 --- a/translations/zh-CN/content/repositories/creating-and-managing-repositories/about-repositories.md +++ b/translations/zh-CN/content/repositories/creating-and-managing-repositories/about-repositories.md @@ -74,7 +74,7 @@ topics: {% data reusables.repositories.internal-repo-default %} -如果用户从企业拥有的所有组织中删除，该用户的内部仓库复刻也会自动删除。 +Any member of the enterprise can fork any internal repository owned by an organization in the enterprise. The forked repository will belong to the member's user account, and the visibility of the fork will be private. 如果用户从企业拥有的所有组织中删除，该用户的内部仓库复刻也会自动删除。 {% endif %} ## 限制查看仓库中的内容和差异 @@ -107,6 +107,7 @@ Text files over **512 KB** are always displayed as plain text. 代码不强调 ## 延伸阅读 - "[创建新仓库](/articles/creating-a-new-repository)" +- "[关于复刻](/github/collaborating-with-pull-requests/working-with-forks/about-forks)" - "[通过议题和拉取请求进行协作](/categories/collaborating-with-issues-and-pull-requests)" - "[在 {% data variables.product.prodname_dotcom %} 上管理您的工作](/categories/managing-your-work-on-github/)" - "[管理仓库](/categories/administering-a-repository)" diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md index 33fea40dfb..abceec467b 100644 --- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md +++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md @@ -46,18 +46,19 @@ Lisa, M., & Bot, H. (2017). My Research Software (Version 2.0.4) [Computer softw {% raw %} ``` -@misc{Lisa_My_Research_Software_2017, +@software{Lisa_My_Research_Software_2017, author = {Lisa, Mona and Bot, Hew}, doi = {10.5281/zenodo.1234}, month = {12}, title = {{My Research Software}}, url = {https://github.com/github/linguist}, + version = {2.0.4}, year = {2017} } ``` {% endraw %} -Note the example above produces a _software_ citation (i.e., `@misc` type in BibTeX rather than `@article`). +Note the example above produces a _software_ citation (i.e., `@software` type in BibTeX rather than `@article`). For more information, see the [Citation File Format](https://citation-file-format.github.io/) website. @@ -67,9 +68,15 @@ When you add a `CITATION.cff` file to the default branch of your repository, it ## Citing something other than software -If you would prefer the GitHub citation information to link to another resource such as a research paper then you can use the `preferred-citation` override in CFF. +If you would prefer the {% data variables.product.prodname_dotcom %} citation information to link to another resource such as a research article, then you can use the `preferred-citation` override in CFF with the following types. -Extended CITATION.cff file describing the software, but linking to a research paper as the preferred citation: +| Resource | 类型 | +| ---------------- | ------------------ | +| Research article | `article` | +| Conference paper | `conference-paper` | +| Book | `book` | + +Extended CITATION.cff file describing the software, but linking to a research article as the preferred citation: ``` cff-version: 1.2.0 @@ -132,6 +139,10 @@ Lisa, M., & Bot, H. (2021). My awesome research software. Journal Title, 1(1), 1 ``` {% endraw %} +## Citing a dataset + +If your repository contains a dataset, you can set `type: dataset` in your `CITATION.cff` file to produce a data citation string output in the {% data variables.product.prodname_dotcom %} citation prompt. + ## Other citation files The GitHub citation feature will also detect a small number of additional files that are often used by communities and projects to describe how they would like their work to be cited. diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md index d4c3dc21a1..c44e99b798 100644 --- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md +++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md @@ -29,7 +29,7 @@ shortTitle: 按主题分类 {% ifversion ghae %}Internal {% else %}公共、内部{% endif %}和私有仓库可拥有主题，虽然您在主题搜索结果中只会看到您有权访问的私有仓库。 -您可以搜索与公共仓库关联的仓库。 更多信息请参阅“[搜索仓库](/articles/searching-for-repositories#search-by-topic)”。 您也可以搜索 {% data variables.product.product_name %} 中的主题列表。 更多信息请参阅“[搜索主题](/articles/searching-topics)”。 +您可以搜索与公共仓库关联的仓库。 更多信息请参阅“[搜索仓库](/search-github/searching-on-github/searching-for-repositories#search-by-topic)”。 您也可以搜索 {% data variables.product.product_name %} 中的主题列表。 更多信息请参阅“[搜索主题](/search-github/searching-on-github/searching-topics)”。 ## 添加主题到仓库 diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md index 343eb11bf5..c1451719e8 100644 --- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md +++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md @@ -73,7 +73,7 @@ topics: | | The Unlicense | `unlicense` | | | zLib License | `zlib` | -按系列许可搜索时，搜索结果将包含该系列的所有许可。 例如，在使用查询 `license:gpl` 时，搜索结果将包含在 GNU General Public License v2.0 和 GNU General Public License v3.0 下许可的仓库。 更多信息请参阅“[搜索仓库](/articles/searching-for-repositories/#search-by-license)”。 +按系列许可搜索时，搜索结果将包含该系列的所有许可。 例如，在使用查询 `license:gpl` 时，搜索结果将包含在 GNU General Public License v2.0 和 GNU General Public License v3.0 下许可的仓库。 更多信息请参阅“[搜索仓库](/search-github/searching-on-github/searching-for-repositories/#search-by-license)”。 ## 检测许可 diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md index 5817159bc2..6cf52c2c34 100644 --- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md +++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md @@ -43,7 +43,7 @@ shortTitle: Manage GitHub Actions settings {% endif %} -{% ifversion fpt or ghes > 2.22 %} +{% ifversion fpt or ghes > 2.22 or ghae-next %} ## 管理仓库的 {% data variables.product.prodname_actions %} 权限 @@ -72,14 +72,21 @@ shortTitle: Manage GitHub Actions settings {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.settings-sidebar-actions %} -1. 在 **Actions permissions（操作权限）**下，选择 **Allow select actions（允许选择操作）**并将所需操作添加到列表中。 ![添加操作到允许列表](/assets/images/help/repository/actions-policy-allow-list.png) +1. 在 **Actions permissions（操作权限）**下，选择 **Allow select actions（允许选择操作）**并将所需操作添加到列表中。 + {%- ifversion ghes %} + ![添加操作到允许列表](/assets/images/help/repository/actions-policy-allow-list.png) + {%- else %} + ![添加操作到允许列表](/assets/images/enterprise/github-ae/repository/actions-policy-allow-list.png) + {%- endif %} 2. 单击 **Save（保存）**。 {% endif %} {% ifversion fpt %} ## 配置公共复刻工作流程所需的批准 -{% data reusables.actions.workflow-run-approve-public-fork %} 您可以使用下面的程序为仓库配置此行为。 修改此设置会覆盖组织或企业级别的配置集。 +{% data reusables.actions.workflow-run-approve-public-fork %} + +You can configure this behavior for a repository using the procedure below. 修改此设置会覆盖组织或企业级别的配置集。 {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} @@ -120,6 +127,29 @@ shortTitle: Manage GitHub Actions settings 1. 单击 **Save（保存）**以应用设置。 {% endif %} +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## Allowing access to components in an internal repository + +{% note %} + +**注：**{% data reusables.gated-features.internal-repos %} + +{% endnote %} + +Members of your enterprise can use internal repositories to work on projects without sharing information publicly. For information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-internal-repositories)." + +To configure whether workflows in an internal repository can be accessed from outside the repository: + +1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of the internal repository. +1. Under your repository name, click {% octicon "gear" aria-label="The gear icon" %} **Settings**. +{% data reusables.repositories.settings-sidebar-actions %} +1. Under **Access**, choose one of the access settings: ![Set the access to Actions components](/assets/images/help/settings/actions-access-settings.png) + * **Not accessible** - Workflows in other repositories can't use workflows in this repository. + * **Accessible by any repository in the organization** - Workflows in other repositories can use workflows in this repository as long as they are part of the same organization. + * **Accessible by any repository in the enterprise** - Workflows in other repositories can use workflows in this repository as long as they are part of the same enterprise. +1. 单击 **Save（保存）**以应用设置。 +{% endif %} + {% ifversion fpt or ghes > 2.22 or ghae %} ## Configuring the retention period for {% data variables.product.prodname_actions %} artifacts and logs in your repository diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md index f98c21e470..30cbbed322 100644 --- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md +++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md @@ -21,6 +21,12 @@ shortTitle: 仓库可见性 组织所有者可以限制只有组织所有者才能更改仓库可见性。 更多信息请参阅“[限制组织的仓库可见性更改](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)”。 +{% ifversion fpt %} + +If you're a member of an {% data variables.product.prodname_emu_enterprise %}, your repositories owned by your user account can only be private, and repositories in your enterprise's organizations can only be private or internal. + +{% endif %} + 我们建议在您更改仓库可见性之前审查以下注意事项。 {% ifversion ghes or ghae %} 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 a637e6fc40..ed15f314bb 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 @@ -34,6 +34,9 @@ topics: 对仓库具有读取访问权限的任何人都可以查看和比较发行版，但只有对仓库具有写入权限的人员才能管理发行版。 更多信息请参阅“[管理仓库中的发行版](/github/administering-a-repository/managing-releases-in-a-repository)”。 {% ifversion fpt %} + +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)." + 对仓库具有管理员权限的人可以选择是否将 {% 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 %} 对象](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)”。 {% endif %} diff --git a/translations/zh-CN/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md b/translations/zh-CN/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md new file mode 100644 index 0000000000..61c5f6f222 --- /dev/null +++ b/translations/zh-CN/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md @@ -0,0 +1,93 @@ +--- +title: Automatically generated release notes +intro: You can automatically generate release notes for your GitHub releases +permissions: Repository collaborators and people with write access to a repository can generate and customize automated release notes for a release. +versions: + fpt: '*' +topics: + - Repositories +shortTitle: Automated release notes +--- + +{% note %} + +**注：**{% data reusables.repositories.auto-gen-release-public-beta %} + +{% endnote %} + +## About automatically generated release notes + +Automatically generated release notes provide an automated alternative to manually writing release notes for your {% data variables.product.prodname_dotcom %} releases. With automatically generated release notes, you can quickly generate an overview of the contents of a release. You can also customize your automated release notes, using labels to create custom categories to organize pull requests you want to include, and exclude certain labels and users from appearing in the output. + +## Creating automatically generated release notes for a new release + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.releases %} +3. 单击 **Draft a new release（草拟新发行版）**。 ![发行版草稿按钮](/assets/images/help/releases/draft_release_button.png) +4. {% ifversion fpt %}Click **Choose a tag** and type{% else %}Type{% endif %} a version number for your release. Alternatively, select an existing tag. + {% ifversion fpt %} + ![Enter a tag](/assets/images/help/releases/releases-tag-create.png) +5. If you are creating a new tag, click **Create new tag**. ![Confirm you want to create a new tag](/assets/images/help/releases/releases-tag-create-confirm.png) + {% else %} + ![发行版标记版本](/assets/images/enterprise/releases/releases-tag-version.png) +{% endif %} +6. If you have created a new tag, use the drop-down menu to select the branch that contains the project you want to release. + {% ifversion fpt %}![Choose a branch](/assets/images/help/releases/releases-choose-branch.png) + {% else %}![发行版标记分支](/assets/images/enterprise/releases/releases-tag-branch.png) + {% endif %} +7. To the top right of the description text box, click **Auto-generate release notes**. ![Auto-generate release notes](/assets/images/help/releases/auto-generate-release-notes.png) +8. Check the generated notes to ensure they include all (and only) the information you want to include. +9. （可选）要在发行版中包含二进制文件（例如已编译的程序），请在二进制文件框中拖放或手动选择文件。 ![通过发行版提供 DMG](/assets/images/help/releases/releases_adding_binary.gif) +10. 要通知用户发行版本尚不可用于生产，可能不稳定，请选择 **This is a pre-release（这是预发布）**。 ![将版本标记为预发行版的复选框](/assets/images/help/releases/prerelease_checkbox.png) +{%- ifversion fpt %} +11. （可选）选择 **Create a discussion for this release（为此版本创建讨论）**，然后选择 **Category（类别）**下拉菜单，然后点击类别进行版本讨论。 ![用于创建发行版讨论和下拉菜单以选择类别的复选框](/assets/images/help/releases/create-release-discussion.png) +{%- endif %} +12. 如果您准备推广您的发行版，请单击 **Publish release（发布版本）**。 要在以后处理该发行版，请单击 **Save draft（保存草稿）**。 ![发布版本和草拟发行版按钮](/assets/images/help/releases/release_buttons.png) + + +## Creating a template for automatically generated release notes + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.files.add-file %} +3. In the file name field, type `.github/release.yml` to create the `release.yml` file in the `.github` directory. ![Create new file](/assets/images/help/releases/release-yml.png) +4. In the file, specify the pull request labels and authors you want to exclude from this release. You can also create new categories and list the pull request labels to be included in each of them. 更多信息请参阅“[管理标签](/issues/using-labels-and-milestones-to-track-work/managing-labels)”。 + +## 示例配置 + +{% raw %} +**release.yml** +```yaml{:copy} +# release.yml + +changelog: + exclude: + labels: + - ignore-for-release + authors: + - octocat + categories: + - title: Breaking Changes 🛠 + labels: + - Semver-Major + - breaking-change + - title: Exciting New Features 🎉 + labels: + - Semver-Minor + - enhancement + - title: Other Changes + labels: + - "*" +``` +{% endraw %} + +## Release template syntax + +| Parameter | 描述 | 必选 | 值 | +|:--------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:---------------------------------------------------------------------------- |:------------------------------------------------------------------------- | +| `变更日志` | Defines the contents within it as the custom template for your release notes. | 必选. | No value accepted. | +| `排除` | Creates a category of pull requests to be excluded from the release. Can be set at the top-level of the changelog to apply to all categories or applied on a per-category basis. | 可选 | No value accepted. | +| `authors` | Specifies authors to be excluded from the release. | Optional for `exclude` category. | Accepts usernames and bots as values. | +| `分类` | Defines the nested contents as custom categories to be included in the template. | 可选 | No value accepted. | +| `title` | Creates an individual category. | Required if `categories` parameter exists. | Takes the category name as its value. | +| `labels` | Specifies labels to be used by the enclosing category. | Required if `categories` parameter exists, optional for `exclude` parameter. | Accepts any labels, whether currently existing or planned for the future. | +| `"*"` | Catchall for any pull request not included within a category *above*. If used, it must be added at the end of the file. | 可选 | No value accepted. | diff --git a/translations/zh-CN/content/repositories/releasing-projects-on-github/index.md b/translations/zh-CN/content/repositories/releasing-projects-on-github/index.md index aec81ce7b5..60c09566bf 100644 --- a/translations/zh-CN/content/repositories/releasing-projects-on-github/index.md +++ b/translations/zh-CN/content/repositories/releasing-projects-on-github/index.md @@ -17,6 +17,7 @@ children: - /viewing-your-repositorys-releases-and-tags - /linking-to-releases - /comparing-releases + - /automatically-generated-release-notes - /automation-for-release-forms-with-query-parameters shortTitle: 发布项目 --- diff --git a/translations/zh-CN/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md b/translations/zh-CN/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md index e07f60105e..2c9962e110 100644 --- a/translations/zh-CN/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md +++ b/translations/zh-CN/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md @@ -42,14 +42,14 @@ You can create new releases with release notes, @mentions of contributors, and l {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.releases %} 3. 单击 **Draft a new release（草拟新发行版）**。 ![发行版草稿按钮](/assets/images/help/releases/draft_release_button.png) -4. {% ifversion fpt %}Click **Choose a tag** and type{% else %}Type{% endif %} a version number for your release. +4. {% ifversion fpt %}Click **Choose a tag** and type{% else %}Type{% endif %} a version number for your release. Alternatively, select an existing tag. {% ifversion fpt %} ![Enter a tag](/assets/images/help/releases/releases-tag-create.png) -1. Click **Create new tag**. ![Confirm you want to create a new tag](/assets/images/help/releases/releases-tag-create-confirm.png) +1. If you are creating a new tag, click **Create new tag**. ![Confirm you want to create a new tag](/assets/images/help/releases/releases-tag-create-confirm.png) {% else %} ![发行版标记版本](/assets/images/enterprise/releases/releases-tag-version.png) {% endif %} -5. 使用下拉菜单，选择包含要发布的项目的分支。 +5. If you have created a new tag, use the drop-down menu to select the branch that contains the project you want to release. {% ifversion fpt %}![Choose a branch](/assets/images/help/releases/releases-choose-branch.png) {% else %}![发行版标记分支](/assets/images/enterprise/releases/releases-tag-branch.png) {% endif %} @@ -57,7 +57,9 @@ You can create new releases with release notes, @mentions of contributors, and l {%- ifversion fpt or ghes > 3.2 or ghae-issue-4972 %} If you @mention any {% data variables.product.product_name %} users in the description, the published release will include a **Contributors** section with an avatar list of all the mentioned users. {%- endif %} - ![发行版说明](/assets/images/help/releases/releases_description.png) + {% ifversion fpt %} Alternatively, you can automatically generate your release notes by clicking **Auto-generate release notes**. + {% endif %} + ![发行版说明](/assets/images/help/releases/releases_description_auto.png) 7. （可选）要在发行版中包含二进制文件（例如已编译的程序），请在二进制文件框中拖放或手动选择文件。 ![通过发行版提供 DMG](/assets/images/help/releases/releases_adding_binary.gif) 8. 要通知用户发行版本尚不可用于生产，可能不稳定，请选择 **This is a pre-release（这是预发布）**。 ![将版本标记为预发行版的复选框](/assets/images/help/releases/prerelease_checkbox.png) {%- ifversion fpt %} diff --git a/translations/zh-CN/content/repositories/working-with-files/using-files/working-with-non-code-files.md b/translations/zh-CN/content/repositories/working-with-files/using-files/working-with-non-code-files.md index 17ece624ec..06736bf26f 100644 --- a/translations/zh-CN/content/repositories/working-with-files/using-files/working-with-non-code-files.md +++ b/translations/zh-CN/content/repositories/working-with-files/using-files/working-with-non-code-files.md @@ -188,6 +188,14 @@ GitHub 支持呈现 PDF 文档。 ![呈现的散文更改](/assets/images/help/repository/rendered_prose_changes.png) +{% ifversion fpt or ghes > 3.2 or ghae-issue-5232 %} + +### Disabling Markdown rendering + +{% data reusables.repositories.disabling-markdown-rendering %} + +{% endif %} + ### 可视化属性更改 我们提供一个描述属性更改的工具提示，与字词不同的是，这些更改在呈现的文档中不可见。 例如，如果链接 URL 从一个网站更改为另一个，我们将显示类似如下的工具提示： diff --git a/translations/zh-CN/content/rest/guides/basics-of-authentication.md b/translations/zh-CN/content/rest/guides/basics-of-authentication.md index b306da7f2c..13d0be4ce8 100644 --- a/translations/zh-CN/content/rest/guides/basics-of-authentication.md +++ b/translations/zh-CN/content/rest/guides/basics-of-authentication.md @@ -22,7 +22,7 @@ topics: {% endtip %} -### 注册您的应用程序 +## 注册您的应用程序 首先，您需要注册[您的应用程序][new oauth app]。 每个注册的 OAuth 应用程序都被分配了一个唯一的客户端 ID 和客户端密钥。 不应共享客户端密钥！ 也不应将该字符串检入您的仓库。 @@ -30,7 +30,7 @@ topics: 由于我们运行常规的 Sinatra 服务器，因此本地实例的位置设置为 `http://localhost:4567`。 回调 URL 应填写为 `http://localhost:4567/callback`。 -### 接受用户授权 +## 接受用户授权 {% data reusables.apps.deprecating_auth_with_query_parameters %} @@ -50,7 +50,7 @@ end ``` 客户端 ID 和客户端密钥[来自应用程序的配置页面][app settings]。 -{% if currentVersion == "free-pro-team@latest" %} **永远_不要_**将该事项的这些值存储在 +{% ifversion fpt %} **永远_不要_**将该事项的这些值存储在 {% data variables.product.product_name %} 中或任何其他公共的地方。{% endif %} 建议将它们存储为 [环境变量][about env vars]--我们正是这样做的。 @@ -85,7 +85,7 @@ end 哦，还记得我们指定了一个回调 URL 用于 `callback` 吗？ 我们没有为它提供路由，因此 {% data variables.product.product_name %} 在用户授权应用程序后不知道将他们带去哪里。 现在我们来解决这个问题！ -#### 提供回调 +### 提供回调 在 _server.rb_ 中，添加路由以指定回调应执行的操作： @@ -108,7 +108,7 @@ end 在应用程序身份验证成功后，{% data variables.product.product_name %} 将提供一个临时的 `code` 值。 您需要将此代码 `POST` 到 {% data variables.product.product_name %} 以换取 `access_token`。 为了简化我们的 GET 和 POST HTTP 请求，我们使用 [rest-client][REST Client]。 请注意，您可能永远不会通过 REST 访问 API。 对于更重要的应用程序，您可能需要使用[一个用您选择的语言编写的库][libraries]。 -#### 检查授予的作用域 +### 检查授予的作用域 用户可以通过直接更改 URL 来编辑您请求的范围。 这可以授予您的应用程序比您最初请求的更少的访问权限。 因此，在使用令牌发出任何请求之前，您应该检查用户为令牌授予的作用域。 有关请求和授予的范围的更多信息，请参阅“[OAuth 应用程序的范围](/developers/apps/scopes-for-oauth-apps#requested-scopes-and-granted-scopes)”。 @@ -132,9 +132,9 @@ end 仅在发出请求之前检查作用域是不够的，因为用户可能会在检查与实际请求之间的时间段更改作用域。 如果发生这种情况，您期望成功的 API 调用可能会以 `404` 或 `401` 状态失败，或者返回不同的信息子集。 -为了帮助您妥善处理这些情况，使用有效令牌发出请求的所有 API 响应还包含一个 [`X-OAuth-Scopes` 标头][oauth scopes]。 此标头包含用于发出请求的令牌的作用域列表。 除此之外，OAuth 应用程序 API 还提供 {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.19" %} [检查令牌的有效性](/rest/reference/apps#check-a-token){% else %}[检查令牌的有效性](/rest/reference/apps#check-an-authorization){% endif %} 的端点。 使用此信息来检测令牌作用域中的更改，并将可用应用程序功能的更改告知用户。 +为了帮助您妥善处理这些情况，使用有效令牌发出请求的所有 API 响应还包含一个 [`X-OAuth-Scopes` 标头][oauth scopes]。 此标头包含用于发出请求的令牌的作用域列表。 除此之外，OAuth 应用程序 API 还提供 {% ifversion fpt or ghes %} [检查令牌的有效性](/rest/reference/apps#check-a-token){% else %}[检查令牌的有效性](/rest/reference/apps#check-an-authorization){% endif %} 的端点。 使用此信息来检测令牌作用域中的更改，并将可用应用程序功能的更改告知用户。 -#### 发出经过身份验证的请求 +### 发出经过身份验证的请求 最后，使用此访问令牌，您将能够将在用户登录时发出经过身份验证的请求： @@ -172,7 +172,7 @@ erb :basic, :locals => auth_result

    ``` -### 实现“持久”身份验证 +## 实现“持久”身份验证 如果我们要求用户每次访问网页时都必须登录应用程序，这将是一个非常糟糕的模式。 例如，尝试直接导航到 `http://localhost:4567/basic`。 您会收到一个错误。 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 394379d633..157d84017a 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 @@ -122,10 +122,10 @@ $ curl -i -u your_username {% data variables.product.api_url_pre %}/use 出现提示时，您可以输入 OAuth 令牌，但我们建议您为它设置一个变量： -您可以使用 `-u "username:$token"` 并为 `token` 设置一个变量，以避免您的令牌留在 shell 历史记录中，这种情况应尽量避免。 +You can use `-u "your_username:$token"` and set up a variable for `token` to avoid leaving your token in shell history, which should be avoided. ```shell -$ curl -i -u username:$token {% data variables.product.api_url_pre %}/users/octocat +$ curl -i -u your_username:$token {% data variables.product.api_url_pre %}/users/octocat ``` diff --git a/translations/zh-CN/content/rest/overview/api-previews.md b/translations/zh-CN/content/rest/overview/api-previews.md index a7de4f93e2..7fa4e02bcf 100644 --- a/translations/zh-CN/content/rest/overview/api-previews.md +++ b/translations/zh-CN/content/rest/overview/api-previews.md @@ -18,13 +18,7 @@ API 预览允许您试用新的 API 以及对现有 API 方法的更改（在它 要访问 API 预览，需要在 `Accept` 标头中为您的请求提供自定义[媒体类型](/rest/overview/media-types)。 每个预览的功能文档可指定要提供的自定义媒体类型。 -{% ifversion fpt %} -## 迁移 - -允许您从自己的 GitHub 用户或组织帐户下载仓库，以审查、备份以及[迁移](/rest/reference/migrations)数据到 {% data variables.product.prodname_ghe_server %}。 - -**自定义媒体类型：** `wyandotte-preview` **公布日期：** [2018-05-24](https://developer.github.com/changes/2018-05-24-user-migration-api/) -{% endif %} +{% ifversion ghes < 3.3 %} ## 增强型部署 @@ -32,18 +26,28 @@ API 预览允许您试用新的 API 以及对现有 API 方法的更改（在它 **自定义媒体类型：** `ant-man-preview` **公布日期：** [2016-04-06](https://developer.github.com/changes/2016-04-06-deployment-and-deployment-status-enhancements/) +{% endif %} + +{% ifversion ghes < 3.3 %} + ## 反应 管理对提交、议题和注释的[反应](/rest/reference/reactions)。 **自定义媒体类型：** `squirrel-girl-preview` **公布日期：** [2016-05-12](https://developer.github.com/changes/2016-05-12-reactions-api-preview/) **更新日期：** [2016-06-07](https://developer.github.com/changes/2016-06-07-reactions-api-update/) +{% endif %} + +{% ifversion ghes < 3.3 %} + ## 时间表 获取针对议题或拉取请求的[事件列表](/rest/reference/issues#timeline)。 **自定义媒体类型：** `mockingbird-preview` **公布日期：** [2016-05-23](https://developer.github.com/changes/2016-05-23-timeline-preview-api/) +{% endif %} + {% ifversion ghes %} ## 预接收环境 @@ -52,11 +56,13 @@ API 预览允许您试用新的 API 以及对现有 API 方法的更改（在它 **自定义媒体类型：** `eye-scream-preview` **公布日期：** [2015-07-29](/rest/reference/enterprise-admin#pre-receive-environments) {% endif %} +{% ifversion ghes < 3.3 %} ## 项目 管理[项目](/rest/reference/projects)。 **自定义媒体类型：** `inertia-preview` **公布日期：** [2016-09-14](https://developer.github.com/changes/2016-09-14-projects-api/) **更新日期：** [2016-10-27](https://developer.github.com/changes/2016-10-27-changes-to-projects-api/) +{% endif %} ## 提交搜索 @@ -70,12 +76,16 @@ API 预览允许您试用新的 API 以及对现有 API 方法的更改（在它 **自定义媒体类型：** `mercy-preview` **公布日期：** [2017-01-31](https://github.com/blog/2309-introducing-topics) +{% ifversion ghes < 3.3 %} + ## 行为准则 查看[所有行为准则](/rest/reference/codes-of-conduct)或获取仓库的当前行为准则。 **自定义媒体类型：** `scarlet-witch-preview` +{% endif %} + {% ifversion ghae or ghes %} ## 全局 web 挂钩 @@ -93,12 +103,16 @@ API 预览允许您试用新的 API 以及对现有 API 方法的更改（在它 **自定义媒体类型：** `zzzax-preview` **公布日期：** [2018-02-22](https://developer.github.com/changes/2018-02-22-protected-branches-required-signatures) +{% ifversion ghes < 3.3 %} + ## 要求多次审批 现在，您可以使用 API [要求多次审批](/rest/reference/repos#branches)拉取请求。 **自定义媒体类型：** `luke-cage-preview` **公布日期：** [2018-03-16](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews) +{% endif %} + {% ifversion ghes < 3.0 %} ## 检查运行和检查套件 API @@ -135,30 +149,42 @@ GitHub 应用程序清单允许用户创建预配置的 GitHub 应用程序。 {% endif %} +{% ifversion ghes < 3.3 %} + ## 部署状态 现在，您可以更新[部署状态](/rest/reference/repos#create-a-deployment-status)的 `environment` 并使用 `in_progress` 和 `queued` 状态。 创建部署状态时，现在可以使用 `auto_inactive` 参数将旧的 `production` 部署标记为 `inactive`。 **自定义媒体类型：** `flash-preview` **公布日期：** [2018-10-16](https://developer.github.com/changes/2018-10-16-deployments-environments-states-and-auto-inactive-updates/) +{% endif %} + +{% ifversion ghes < 3.3 %} + ## 仓库创建权限 现在，您可以配置组织成员是否可以创建仓库以及他们可以创建哪些类型的仓库。 更多信息请参阅“[更新组织](/rest/reference/orgs#update-an-organization)”。 **自定义媒体类型：** `surtur-preview` **公布日期：** [2019-12-03](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/) +{% endif %} + ## 内容附件 现在，您可以在 GitHub 中使用 {% data variables.product.prodname_unfurls %} API 提供有关链接到注册域的 URL 的更多信息。 更多信息请参阅“[使用内容附件](/apps/using-content-attachments/)”。 **自定义媒体类型：** `corsair-preview` **公布日期：** [2018-12-10](https://developer.github.com/changes/2018-12-10-content-attachments-api/) +{% ifversion ghes < 3.3 %} + ## 启用和禁用页面 您可以使用[页面 API](/rest/reference/repos#pages) 中的新端点来启用或禁用页面。 要了解有关页面的更多信息，请参阅“[GitHub Pages 基础知识](/categories/github-pages-basics)”。 **自定义媒体类型：** `switcheroo-preview` **公布日期：** [2019-03-14](https://developer.github.com/changes/2019-03-14-enabling-disabling-pages/) +{% endif %} + {% ifversion ghes < 3.3 %} ## 列出提交的分支或拉取请求 @@ -169,11 +195,7 @@ GitHub 应用程序清单允许用户创建预配置的 GitHub 应用程序。 {% endif %} -## 为仓库启用或禁用漏洞警报 - -您可以使用[仓库 API](/rest/reference/repos) 中的两个新端点来启用或禁用漏洞警报。 - -**自定义媒体类型：** `dorian-preview` **公布日期：** [2019-04-24](https://developer.github.com/changes/2019-04-24-vulnerability-alerts/) +{% ifversion ghes < 3.3 %} ## 更新拉取请求分支 @@ -181,12 +203,6 @@ GitHub 应用程序清单允许用户创建预配置的 GitHub 应用程序。 **自定义媒体类型：** `lydian-preview` **公布日期：** [2019-05-29](https://developer.github.com/changes/2019-05-29-update-branch-api/) -{% ifversion fpt %} -## 启用或禁用自动安全修复 - -您可以使用一组新的端点来[启用和禁用自动安全修复](/rest/reference/repos#enable-automated-security-fixes)。 - -**自定义媒体类型：** `london-preview` **公布日期：** [2019-06-04](https://developer.github.com/changes/2019-06-04-automated-security-fixes/) {% endif %} ## 创建和使用仓库模板 @@ -195,7 +211,8 @@ GitHub 应用程序清单允许用户创建预配置的 GitHub 应用程序。 **自定义媒体类型：** `baptiste-preview` **公布日期：** [2019-07-05](https://developer.github.com/changes/2019-07-16-repository-templates-api/) -{% ifversion fpt or ghes or ghae %} +{% ifversion ghes < 3.3 %} + ## 仓库 API 的新可见性参数 您可以在[仓库 API](/rest/reference/repos) 中设置和检索仓库可见性。 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 47dcef7a9b..41c5b3f711 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 @@ -14,21 +14,21 @@ topics: 本文介绍构成官方 {% data variables.product.product_name %} REST API 的资源。 如果您有任何问题或要求，请联系 {% data variables.contact.contact_support %}。 -### 当前版本 +## 当前版本 默认情况下，对 `{% data variables.product.api_url_code %}` 的所有请求都会收到 REST API 的 **v3** [版本](/developers/overview/about-githubs-apis)。 我们建议您[通过 `Accept` 标头明确请求此版本](/rest/overview/media-types#request-specific-version)。 Accept: application/vnd.github.v3+json -{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt '2.9' %} +{% ifversion fpt %} 有关 GitHub GraphQL API 的信息，请参阅 [v4 文档](/graphql)。 有关迁移到 GraphQL 的信息，请参阅“[从 REST 迁移](/graphql/guides/migrating-from-rest-to-graphql)”。 {% endif %} -### 架构 +## 架构 -{% if currentVersion == "free-pro-team@latest" %}所有 API 访问都通过 HTTPS 进行，{% else %}API{% endif %} 从 `{% data variables.product.api_url_code %}` 访问。 所有数据都 +{% ifversion fpt %}所有 API 访问都通过 HTTPS 进行，{% else %}API {% endif %}可以从 `{% data variables.product.api_url_code %}` 访问。 所有数据都 作为 JSON 发送和接收。 ```shell @@ -42,8 +42,8 @@ $ curl -I {% data variables.product.api_url_pre %}/users/octocat/orgs > X-GitHub-Media-Type: github.v3 > X-RateLimit-Limit: 5000 > X-RateLimit-Remaining: 4987 -> X-RateLimit-Reset: 1350085394{% if enterpriseServerVersions contains currentVersion %} -> X-GitHub-Enterprise-Version: {{ currentVersion | remove: "enterprise-server@" }}.0{% elsif currentVersion == "github-ae@latest" %} +> X-RateLimit-Reset: 1350085394{% ifversion ghes %} +> X-GitHub-Enterprise-Version: {{ currentVersion | remove: "enterprise-server@" }}.0{% elsif ghae %} > X-GitHub-Enterprise-Version: GitHub AE{% endif %} > Content-Length: 5 > Cache-Control: max-age=0, private, must-revalidate @@ -58,7 +58,7 @@ $ curl -I {% data variables.product.api_url_pre %}/users/octocat/orgs 有关时间戳中时区的更多信息，请参阅[此节](#timezones)。 -#### 摘要表示 +### 摘要表示 当您获取资源列表时，响应包括该资源的属性_子集_。 这就是资源的“摘要”表示。 （对于某些属性，API 要经过大量计算后才可提供。 出于性能考虑，摘要表示排除了这些属性。 要获得这些属性，请获取“详细”表示。) @@ -66,7 +66,7 @@ $ curl -I {% data variables.product.api_url_pre %}/users/octocat/orgs GET /orgs/octokit/repos -#### 详细表示 +### 详细表示 当您获取单个资源时，响应通常包括该资源的_所有_属性。 这就是资源的“详细”表示。 （请注意，授权有时会影响表示中包含的详细信息数量。） @@ -76,17 +76,17 @@ $ curl -I {% data variables.product.api_url_pre %}/users/octocat/orgs 本文档提供每种 API 方法的示例响应。 示例响应说明了该方法返回的所有属性。 -### 身份验证 +## 身份验证 -{% if currentVersion == "github-ae@latest" %} 我们建议通过 [web 应用程序流程](/developers/apps/authorizing-oauth-apps#web-application-flow)创建 OAuth2 令牌，以便向 {% data variables.product.product_name %} REST API 验证。 {% else %} 通过 {% data variables.product.product_name %} REST API 验证有两种方式。{% endif %} 需要身份验证的请求有时将返回 `404 Not Found`，而不是 `403 Forbidden`。 这是为了防止私有仓库意外泄露给未经授权的用户。 +{% ifversion ghae %} 我们建议通过 [web 应用程序流程](/developers/apps/authorizing-oauth-apps#web-application-flow)创建 OAuth2 令牌，以便向 {% data variables.product.product_name %} REST API 验证。 {% else %} 通过 {% data variables.product.product_name %} REST API 验证有两种方式。{% endif %} 需要身份验证的请求有时将返回 `404 Not Found`，而不是 `403 Forbidden`。 这是为了防止私有仓库意外泄露给未经授权的用户。 -#### 基本验证 +### 基本验证 ```shell $ curl -u "username" {% data variables.product.api_url_pre %} ``` -#### OAuth2 令牌（在标头中发送） +### OAuth2 令牌（在标头中发送） ```shell $ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %} @@ -100,8 +100,8 @@ $ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product. 阅读[关于 OAuth2 的更多信息](/apps/building-oauth-apps/)。 请注意，OAuth2 令牌可使用生产应用程序的 [web 应用程序流](/developers/apps/authorizing-oauth-apps#web-application-flow)来获取。 -{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %} -#### OAuth2 键/密钥 +{% ifversion fpt or ghes %} +### OAuth2 键/密钥 {% data reusables.apps.deprecating_auth_with_query_parameters %} @@ -114,13 +114,13 @@ curl -u my_client_id:my_client_secret '{% data variables.product.api_url_pre %}/ 在私有模式下无法使用 OAuth2 键和密钥进行身份验证，尝试验证时会返回 `401 Unauthorized`。 更多信息请参阅“[启用私有模式](/enterprise/admin/installation/enabling-private-mode)”。 {% endif %} -{% if currentVersion == "free-pro-team@latest" %} +{% ifversion fpt %} 阅读[有关未经验证速率限制的更多信息](#increasing-the-unauthenticated-rate-limit-for-oauth-applications)。 {% endif %} -#### 失败登录限制 +### 失败登录限制 使用无效凭据进行身份验证将返回 `401 Unauthorized`： @@ -137,8 +137,8 @@ $ curl -I {% data variables.product.api_url_pre %} -u foo:bar 在短时间内检测到多个使用无效凭据的请求后，API 将暂时拒绝该用户的所有身份验证尝试（包括使用有效凭据的尝试），并返回 `403 Forbidden`： ```shell -$ curl -i {% data variables.product.api_url_pre %} -u {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %} --u valid_username:valid_token {% endif %}{% if enterpriseServerVersions contains currentVersion %}-u valid_username:valid_password {% endif %} +$ curl -i {% data variables.product.api_url_pre %} -u {% ifversion fpt or ghae %} +-u valid_username:valid_token {% endif %}{% ifversion ghes %}-u valid_username:valid_password {% endif %} > HTTP/2 403 > { > "message": "Maximum number of login attempts exceeded. Please try again later.", @@ -146,7 +146,7 @@ $ curl -i {% data variables.product.api_url_pre %} -u {% if currentVersion == "f > } ``` -### 参数 +## 参数 许多 API 方法采用可选参数。 对于 `GET` 请求，任何未指定为路径段的参数都可以作为 HTTP 查询字符串参数进行传递： @@ -162,20 +162,20 @@ $ curl -i "{% data variables.product.api_url_pre %}/repos/vmg/redcarpet/issues?s $ curl -i -u username -d '{"scopes":["repo_deployment"]}' {% data variables.product.api_url_pre %}/authorizations ``` -### 根端点 +## 根端点 您可以向根端点发出 `GET` 请求，以获取 REST API 支持的所有端点类别： ```shell -$ curl {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" %} --u username:token {% endif %}{% if enterpriseServerVersions contains currentVersion %}-u username:password {% endif %}{% data variables.product.api_url_pre %} +$ curl {% ifversion fpt or ghae %} +-u username:token {% endif %}{% ifversion ghes %}-u username:password {% endif %}{% data variables.product.api_url_pre %} ``` -### GraphQL 全局节点 ID +## GraphQL 全局节点 ID 请参阅“[使用全局节点 ID](/graphql/guides/using-global-node-ids)”指南，详细了解如何通过 REST API 查找 `node_id` 以及如何在 GraphQL 操作中使用它们。 -### 客户端错误 +## 客户端错误 接收请求正文的 API 调用上可能存在三种类型的客户端错误： @@ -222,7 +222,7 @@ Request` 响应。 资源还可能发送自定义验证错误（其中 `code` 为 `custom`）。 自定义错误始终包括一个描述错误的 `message` 字段，大多数错误还包括 `documentation_url` 字段，该字段指向一些可能有助于解决错误的内容。 -### HTTP 重定向 +## HTTP 重定向 API v3 酌情使用 HTTP 重定向。 客户端应假定任何请求都可能会导致重定向。 接收 HTTP 重定向*不是*错误，客户端应该遵循该重定向。 重定向响应将包括 `Location` 标头字段，其中包含客户端应向其重复请求的资源的 URI。 @@ -233,7 +233,7 @@ API v3 酌情使用 HTTP 重定向。 客户端应假定任何请求都可能会 其他重定向状态代码可根据 HTTP 1.1 规范使用。 -### HTTP 请求方法 +## HTTP 请求方法 API v3 尽可能对每个操作使用适当的 HTTP 请求方法。 @@ -246,9 +246,9 @@ API v3 尽可能对每个操作使用适当的 HTTP 请求方法。 | `PUT` | 用于替换资源或集合。 对于没有 `body` 属性的 `PUT` 请求，请确保将 `Content-Length` 标头设置为零。 | | `DELETE` | 用于删除资源。 | -### 超媒体 +## 超媒体 -所有资源都可以具有一个或多个链接到其他资源的 `*_url` 属性。 这些属性旨在提供明确的 URL，使适当的 API 客户端不需要自己构建 URL。 强烈建议 API 客户端使用这些属性。 这样做有助于开发者未来更容易升级 API。 所有 URI 都应成为适当的 [RFC 6570][rfc] URI 模板。 +所有资源都可以具有一个或多个链接到其他资源的 `*_url` 属性。 这些属性旨在提供明确的 URL，使适当的 API 客户端不需要自己构建 URL。 强烈建议 API 客户端使用这些属性。 这样做有助于开发者未来更容易升级 API。 All URLs are expected to be proper [RFC 6570][rfc] URI templates. 然后，您可以使用 [uri_template][uri] gem 等命令扩展这些模板： @@ -262,7 +262,7 @@ API v3 尽可能对每个操作使用适当的 HTTP 请求方法。 >> tmpl.expand :all => 1, :participating => 1 => "/notifications?all=1&participating=1" -### 分页 +## 分页 默认情况下，如果请求返回了多个项，将按每页最多 30 项进行分页。 您可以使用 `page` 参数指定更多页面。 对于某些资源，您还可以使用 `per_page` 参数设置自定义页面大小，每页最多 100 项。 请注意，由于技术原因，并非所有端点都遵循 `per_page` 参数，相关示例请参阅[事件](/rest/reference/activity#events)。 @@ -276,7 +276,7 @@ $ curl '{% data variables.product.api_url_pre %}/user/repos?page=2&per_page=100' 有关分页的更多信息，请查看我们的[分页浏览][pagination-guide]指南。 -#### 链接标头 +### 链接标头 {% note %} @@ -284,7 +284,7 @@ $ curl '{% data variables.product.api_url_pre %}/user/repos?page=2&per_page=100' {% endnote %} -[链接标头](http://tools.ietf.org/html/rfc5988)包括分页信息： 例如： +The [Link header](https://datatracker.ietf.org/doc/html/rfc5988) includes pagination information. 例如： Link: <{% data variables.product.api_url_code %}/user/repos?page=3&per_page=100>; rel="next", <{% data variables.product.api_url_code %}/user/repos?page=50&per_page=100>; rel="last" @@ -295,7 +295,7 @@ _该示例包括换行符，以提高可读性。_ Link: <{% data variables.product.api_url_code %}/orgs/ORG/audit-log?after=MTYwMTkxOTU5NjQxM3xZbGI4VE5EZ1dvZTlla09uWjhoZFpR&before=>; rel="next", -此 `Link` 响应标头包含一个或多个[超媒体](/rest#hypermedia)链接关系，其中一些可能需要扩展为 [URI 模板](http://tools.ietf.org/html/rfc6570)。 +This `Link` response header contains one or more [Hypermedia](/rest#hypermedia) link relations, some of which may require expansion as [URI templates](https://datatracker.ietf.org/doc/html/rfc6570). 可能的 `rel` 值为： @@ -306,11 +306,11 @@ _该示例包括换行符，以提高可读性。_ | `first` | 结果第一页的链接关系。 | | `prev` | 结果前一页的链接关系。 | -### 速率限制 +## 速率限制 对于使用基本验证或 OAuth 的 API 请求，每小时最多可发出 5,000 个请求。 无论是使用[基本验证](#basic-authentication)还是 [OAuth 令牌](#oauth2-token-sent-in-a-header)，经验证的请求都与经验证的用户相关联。 这意味着在使用同一用户拥有的不同令牌进行验证时，该用户授权的所有 OAuth 应用程序将共享同一配额——每小时 5,000 个请求。 -{% if currentVersion == "free-pro-team@latest" %} +{% ifversion fpt %} 对于属于 {% data variables.product.prodname_ghe_cloud %} 帐户的用户，使用 OAuth 令牌对相同 {% data variables.product.prodname_ghe_cloud %} 帐户拥有的资源发出的请求上限已提升至每小时 15,000 点。 @@ -365,7 +365,7 @@ new Date(1372700873 * 1000) 您可以[检查速率限制状态](/rest/reference/rate-limit)，而不会引发 API 命中。 -#### 提高 OAuth 应用程序的未经验证速率限制 +### 提高 OAuth 应用程序的未经验证速率限制 如果您的 OAuth 应用程序需要以更高的速率限制进行未经验证的调用， 您可以在端点路由之前传递应用程序的客户端 ID 和密钥。 @@ -384,15 +384,15 @@ $ curl -u my_client_id:my_client_secret {% data variables.product.api_url_pre %} {% endnote %} -#### 保持在速率限制之内 +### 保持在速率限制之内 如果使用基本验证或 OAuth 时超出了速率限制，您可以通过缓存 API 响应和使用[条件请求](#conditional-requests)来解决此问题。 -#### 滥用速率限制 +### Secondary rate limits -为了在 {% data variables.product.product_name %} 上提供优质的服务，使用 API 时，某些操作可能会受到额外的速率限制。 例如，使用 API 快速创建内容、主动轮询而不是使用 web 挂钩、发出多个并发请求或重复请求计算成本高昂的数据，可能会导致滥用速率限制。 +为了在 {% data variables.product.product_name %} 上提供优质的服务，使用 API 时，某些操作可能会受到额外的速率限制。 For example, using the API to rapidly create content, poll aggressively instead of using webhooks, make multiple concurrent requests, or repeatedly request data that is computationally expensive may result in secondary rate limiting. -滥用速率限制无意干扰 API 的合法使用。 您的正常速率限制应该是您目标的唯一限制。 为确保您成为 API 的好公民，请查看我们的[最佳实践指南](/guides/best-practices-for-integrators/)。 +Secondary rate limits are not intended to interfere with legitimate use of the API. 您的正常速率限制应该是您目标的唯一限制。 为确保您成为 API 的好公民，请查看我们的[最佳实践指南](/guides/best-practices-for-integrators/)。 如果您的应用程序触发此速率限制，您将收到信息响应： @@ -402,14 +402,14 @@ $ curl -u my_client_id:my_client_secret {% data variables.product.api_url_pre %} > Connection: close > { -> "message": "You have triggered an abuse detection mechanism and have been temporarily blocked from content creation. Please retry your request again later.", -> "documentation_url": "{% data variables.product.doc_url_pre %}/overview/resources-in-the-rest-api#abuse-rate-limits" +> "message": "You have exceeded a secondary rate limit and have been temporarily blocked from content creation. Please retry your request again later.", +> "documentation_url": "{% data variables.product.doc_url_pre %}/overview/resources-in-the-rest-api#secondary-rate-limits" > } ``` -{% if currentVersion == "free-pro-team@latest" %} +{% ifversion fpt %} -### 必需用户代理 +## 必需用户代理 所有 API 请求都必须包含有效的 `User-Agent` 标头。 没有 `User-Agent` 标头的请求将被拒绝。 我们要求您使用 {% data variables.product.product_name %} 用户名或应用程序的名称作为 `User-Agent` 标头值。 这是为了方便我们在发现问题时与您联系 。 @@ -434,11 +434,11 @@ $ curl -IH 'User-Agent: ' {% data variables.product.api_url_pre %}/meta {% endif %} -### 条件请求 +## 条件请求 大多数响应返回 `ETag` 标头。 许多响应还会返回 `Last-Modified` 标头。 您可以根据这些标头的值，分别使用 `If-None-Match` 和 `If-Modified-Since` 标头对这些资源发出后续请求。 如果资源没有更改，服务器将返回 `304 Not Modified`。 -{% if currentVersion == "free-pro-team@latest" %} +{% ifversion fpt %} {% tip %} @@ -479,7 +479,7 @@ $ curl -I {% data variables.product.api_url_pre %}/user -H "If-Modified-Since: T > X-RateLimit-Reset: 1372700873 ``` -### 跨源资源共享 +## 跨源资源共享 API 支持适用于任何来源 AJAX 请求的跨源资源共享 (CORS)。 您可以阅读 [CORS W3C 建议](http://www.w3.org/TR/cors/)或 HTML 5 安全指南中的[这方面介绍](https://code.google.com/archive/p/html5security/wikis/CrossOriginRequestSecurity.wiki)。 @@ -504,7 +504,7 @@ Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-Ra Access-Control-Max-Age: 86400 ``` -### JSON-P 回调 +## JSON-P 回调 您可以向任何 GET 调用发送 `?callback` 参数，以便让结果包裹在 JSON 函数中。 当浏览器希望绕开跨域问题将 {% data variables.product.product_name %} 内容嵌入网页时，通常使用此方法。 响应包括与常规 API 相同的数据输出，加上相关的 HTTP 标头信息。 @@ -579,7 +579,7 @@ $ curl {% data variables.product.api_url_pre %}?callback=foo } ``` -### 时区 +## 时区 某些创建新数据的请求（例如创建新的提交）允许您在指定或生成时间戳时提供时区信息。 我们按照优先顺序应用以下规则来确定 API 调用的时区信息。 @@ -588,13 +588,13 @@ $ curl {% data variables.product.api_url_pre %}?callback=foo * [使用用户的最后一个已知时区](#using-the-last-known-timezone-for-the-user) * [在没有其他时区信息的情况下默认使用 UTC](#defaulting-to-utc-without-other-timezone-information) -#### 明确提供带有时区信息的 ISO 8601 时间戳 +### 明确提供带有时区信息的 ISO 8601 时间戳 对于允许指定时间戳的 API 调用，我们使用这种明确的时间戳。 这方面的示例是[提交 API](/rest/reference/git#commits)。 这些时间戳看起来像 `2014-02-27T15:05:06+01:00`。 另请参阅[本示例](/rest/reference/git#example-input)，了解如何指定这些时间戳。 -#### 使用 `Time-Zone` 标头 +### 使用 `Time-Zone` 标头 可以提供根据 [Olson 数据库中的名称列表](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones)定义时区的 `Time-Zone` 标头。 @@ -604,15 +604,15 @@ $ curl -H "Time-Zone: Europe/Amsterdam" -X POST {% data variables.product.api_ur 这意味着当您在这个标题定义的时区做出 API 调用时，我们会生成一个时间戳。 例如，[内容 API](/rest/reference/repos#contents)为每个添加或更改生成 git 提交，并使用当前时间作为时间戳。 此标头将确定用于生成当前时间戳的时区。 -#### 使用用户的最后一个已知时区 +### 使用用户的最后一个已知时区 如果未指定 `Time-Zone` 标头，并且您对 API 进行验证过身份的调用，则我们对经过身份验证的用户使用最后一个已知时区。 最新一个已知的时区在您浏览 {% data variables.product.product_name %} 网站时都会更新。 -#### 在没有其他时区信息的情况下默认使用 UTC +### 在没有其他时区信息的情况下默认使用 UTC 如果上述步骤未产生任何信息，我们将使用 UTC 作为时区来创建 git 提交。 -[rfc]: http://tools.ietf.org/html/rfc6570 +[rfc]: https://datatracker.ietf.org/doc/html/rfc6570 [uri]: https://github.com/hannesg/uri_template [pagination-guide]: /guides/traversing-with-pagination diff --git a/translations/zh-CN/content/rest/overview/troubleshooting.md b/translations/zh-CN/content/rest/overview/troubleshooting.md index c4652a2b10..8fb0f71016 100644 --- a/translations/zh-CN/content/rest/overview/troubleshooting.md +++ b/translations/zh-CN/content/rest/overview/troubleshooting.md @@ -62,6 +62,10 @@ curl -u my_username:my_password -X POST "https://api.github.com/authorizations" 然后您必须切换到 [web 应用程序流程](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow)来生成访问令牌。 +## Timeouts + +If {% data variables.product.product_name %} takes more than 10 seconds to process an API request, {% data variables.product.product_name %} will terminate the request and you will receive a timeout response. + {% endif %} [oap-guide]: https://developer.github.com/changes/2015-01-19-an-integrators-guide-to-organization-application-policies/ diff --git a/translations/zh-CN/content/rest/reference/actions.md b/translations/zh-CN/content/rest/reference/actions.md index 3647022a60..5db23c71fa 100644 --- a/translations/zh-CN/content/rest/reference/actions.md +++ b/translations/zh-CN/content/rest/reference/actions.md @@ -12,7 +12,6 @@ topics: miniTocMaxHeadingLevel: 3 --- -{% data reusables.actions.ae-beta %} {% data variables.product.prodname_actions %} API 允许您使用 REST API 来管理 {% data variables.product.prodname_actions %}。 {% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} require the permissions mentioned in each endpoint. 更多信息请参阅“[{% data variables.product.prodname_actions %} 文档](/actions)”。 @@ -22,8 +21,6 @@ miniTocMaxHeadingLevel: 3 ## 构件 -{% data reusables.actions.ae-beta %} - 构件 API 允许您下载、删除和检索有关工作流程构件的信息。 {% data reusables.actions.about-artifacts %}更多信息请参阅“[使用构件持久化工作流程](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)”。 {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %} @@ -35,8 +32,6 @@ miniTocMaxHeadingLevel: 3 {% ifversion fpt or ghes > 2.22 or ghae %} ## 权限 -{% data reusables.actions.ae-beta %} - 权限 API 允许您设置允许哪些组织和仓库运行 {% data variables.product.prodname_actions %}，以及允许运行哪些操作。 更多信息请参阅“[使用限制、计费和管理](/actions/reference/usage-limits-billing-and-administration#disabling-or-limiting-github-actions-for-your-repository-or-organization)”。 您还可以为企业设置权限。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} Enterprise 管理](/rest/reference/enterprise-admin#github-actions)”REST API。 @@ -48,8 +43,6 @@ miniTocMaxHeadingLevel: 3 ## 密码 -{% data reusables.actions.ae-beta %} - 密码 API 允许您创建、更新、删除和检索有关加密密码的信息。 {% data reusables.actions.about-secrets %}更多信息请参阅“[创建和使用加密密码](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。 {% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} must have the `secrets` permission to use this API. 经过身份验证的用户必须对仓库具有协作者权限才可创建、更新或读取密码。 @@ -60,7 +53,6 @@ miniTocMaxHeadingLevel: 3 ## 自托管运行器 -{% data reusables.actions.ae-beta %} {% data reusables.actions.ae-self-hosted-runners-notice %} 自托管运行器 API 允许您注册、查看和删除自托管的运行器。 {% data reusables.actions.about-self-hosted-runners %} 更多信息请参阅“[托管您自己的运行器](/actions/hosting-your-own-runners)”。 @@ -75,7 +67,6 @@ miniTocMaxHeadingLevel: 3 ## 自托管运行器组 -{% data reusables.actions.ae-beta %} {% data reusables.actions.ae-self-hosted-runners-notice %} 自托管运行器组 API 允许您管理自托运行器组。 更多信息请参阅“[使用组管理对自托管运行器的访问](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)”。 @@ -90,8 +81,6 @@ miniTocMaxHeadingLevel: 3 ## 工作流程 -{% data reusables.actions.ae-beta %} - 工作流程 API 允许您查看仓库的工作流程。 {% data reusables.actions.about-workflows %} 更多信息请参阅“[使用 GitHub Actions 自动化工作流程](/actions/automating-your-workflow-with-github-actions)”。 {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %} @@ -102,8 +91,6 @@ miniTocMaxHeadingLevel: 3 ## 工作流程作业 -{% data reusables.actions.ae-beta %} - 工作流程作业 API 允许您查看日志和工作流程作业。 {% data reusables.actions.about-workflow-jobs %} 更多信息请参阅“[GitHub Actions 的工作流程语法](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)”。 {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %} @@ -114,8 +101,6 @@ miniTocMaxHeadingLevel: 3 ## 工作流程运行 -{% data reusables.actions.ae-beta %} - 工作流程运行 API 允许您查看、重新运行、取消和查看工作流程运行的日志。 {% data reusables.actions.about-workflow-runs %} 更多信息请参阅“[管理工作流程运行](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)”。 {% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %} diff --git a/translations/zh-CN/content/rest/reference/activity.md b/translations/zh-CN/content/rest/reference/activity.md index e9dfa84956..738e735cce 100644 --- a/translations/zh-CN/content/rest/reference/activity.md +++ b/translations/zh-CN/content/rest/reference/activity.md @@ -145,6 +145,7 @@ $ -H "If-Modified-Since: Thu, 25 Oct 2012 15:16:27 GMT" | `assign` | 您被分配到议题。 | | `作者` | 您创建了帖子。 | | `注释，评论` | 您评论了帖子。 | +| `ci_activity` | A {% data variables.product.prodname_actions %} workflow run that you triggered was completed. | | `邀请` | 您接受了参与仓库的邀请。 | | `manual` | 您订阅了帖子（通过议题或拉取请求） | | `提及` | 您在内容中被特别 **@提及**。 | diff --git a/translations/zh-CN/content/rest/reference/enterprise-admin.md b/translations/zh-CN/content/rest/reference/enterprise-admin.md index 768afa20ed..018b25e93d 100644 --- a/translations/zh-CN/content/rest/reference/enterprise-admin.md +++ b/translations/zh-CN/content/rest/reference/enterprise-admin.md @@ -81,7 +81,6 @@ http(s)://hostname/ ## GitHub Actions -{% data reusables.actions.ae-beta %} {% for operation in currentRestOperations %} {% if operation.subcategory == 'actions' %}{% include rest_operation %}{% endif %} diff --git a/translations/zh-CN/content/rest/reference/projects.md b/translations/zh-CN/content/rest/reference/projects.md index 7defac6103..fd1f2930e3 100644 --- a/translations/zh-CN/content/rest/reference/projects.md +++ b/translations/zh-CN/content/rest/reference/projects.md @@ -1,6 +1,6 @@ --- title: 项目 -intro: 项目 API 允许您在仓库中创建、列出、更新、删除和自定义项目。 +intro: 'The Projects API lets you create, list, update, delete and customize projects in a repository.' redirect_from: - /v3/projects versions: diff --git a/translations/zh-CN/content/rest/reference/repos.md b/translations/zh-CN/content/rest/reference/repos.md index 668543f6d4..882ba62ae9 100644 --- a/translations/zh-CN/content/rest/reference/repos.md +++ b/translations/zh-CN/content/rest/reference/repos.md @@ -175,7 +175,7 @@ When you set the state of a deployment to `success`, then all prior non-transien {% ifversion fpt or ghes > 3.1 or ghae-next %} ## 环境 -环境 API 允许您创建、配置和删除环境。 有关环境的更多信息，请参阅“[环境](/actions/reference/environments)”。 要管理环境密码，请参阅“[密码](/rest/reference/actions#secrets)”。 +环境 API 允许您创建、配置和删除环境。 For more information about environments, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." 要管理环境密码，请参阅“[密码](/rest/reference/actions#secrets)”。 {% for operation in currentRestOperations %} {% if operation.subcategory == 'environments' %}{% include rest_operation %}{% endif %} diff --git a/translations/zh-CN/content/rest/reference/scim.md b/translations/zh-CN/content/rest/reference/scim.md index c0b3afcdad..5762015637 100644 --- a/translations/zh-CN/content/rest/reference/scim.md +++ b/translations/zh-CN/content/rest/reference/scim.md @@ -16,7 +16,9 @@ SCIM API 由 SCIM 启用的身份提供程序 (IdP) 用来自动预配 {% data v {% note %} -**注：**SCIM API 仅适用于 [{% data variables.product.prodname_ghe_cloud %}](/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts) 上启用了 [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) 的组织。 {% data reusables.scim.enterprise-account-scim %} 有关 SCIM 的更多信息，请参阅“[关于 SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)”。 +**注意：** + - The SCIM API is available only to organizations on [{% data variables.product.prodname_ghe_cloud %}](/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts) with [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) enabled. {% data reusables.scim.enterprise-account-scim %} 有关 SCIM 的更多信息，请参阅“[关于 SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)”。 + - The SCIM API cannot be used with {% data variables.product.prodname_emus %}. {% endnote %} diff --git a/translations/zh-CN/content/rest/reference/search.md b/translations/zh-CN/content/rest/reference/search.md index 33357dbcab..dbbb2269d3 100644 --- a/translations/zh-CN/content/rest/reference/search.md +++ b/translations/zh-CN/content/rest/reference/search.md @@ -50,7 +50,7 @@ GitHub Octocat in:readme user:defunkt const queryString = 'q=' + encodeURIComponent('GitHub Octocat in:readme user:defunkt'); ``` -有关可用限定符及其格式的完整列表和使用示例，请参阅“[在 GitHub 上搜索](/articles/searching-on-github/)”。 有关如何使用运算符匹配特定数量、日期或排除结果，请参阅“[了解搜索语法](/articles/understanding-the-search-syntax/)”。 +有关可用限定符及其格式的完整列表和使用示例，请参阅“[在 GitHub 上搜索](/articles/searching-on-github/)”。 For information about how to use operators to match specific quantities, dates, or to exclude results, see "[Understanding the search syntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax/)." ### 查询长度限制 diff --git a/translations/zh-CN/content/rest/reference/teams.md b/translations/zh-CN/content/rest/reference/teams.md index 158aa4dffc..99ff1756cb 100644 --- a/translations/zh-CN/content/rest/reference/teams.md +++ b/translations/zh-CN/content/rest/reference/teams.md @@ -58,6 +58,12 @@ miniTocMaxHeadingLevel: 3 您可以通过 IdP 通过团队同步管理 GitHub 团队成员。 必须启用团队同步才能使用团队同步 API。 更多信息请参阅“在身份提供程序与 GitHub 之间同步团队”。 +{% note %} + +**Note:** The Team Synchronization API cannot be used with {% data variables.product.prodname_emus %}. + +{% endnote %} + {% for operation in currentRestOperations %} {% if operation.subcategory == 'team-sync' %}{% include rest_operation %}{% endif %} {% endfor %} diff --git a/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md b/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md new file mode 100644 index 0000000000..ab6ef0b0f8 --- /dev/null +++ b/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md @@ -0,0 +1,90 @@ +--- +title: 关于在 GitHub 上搜索 +intro: '我们的集成搜索涵盖了 {% data variables.product.product_name %} 上的许多仓库、用户和代码行。' +redirect_from: + - /articles/using-the-command-bar/ + - /articles/github-search-basics/ + - /articles/search-basics/ + - /articles/searching-github/ + - /articles/advanced-search/ + - /articles/about-searching-on-github + - /github/searching-for-information-on-github/about-searching-on-github + - /github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +{% data reusables.search.you-can-search-globally %} + +- 要全局搜索所有 {% data variables.product.product_name %}，请在页面顶部的搜索字段中输入您要查找的内容，然后在搜索下拉菜单中选择“所有{% data variables.product.prodname_dotcom %}”。 +- 要在特定仓库或组织中搜索，请导航到该仓库或组织页面，在页面顶部的搜索字段中输入要查找的内容，然后按 **Enter**。 + +{% note %} + +**注意：** + +{% ifversion fpt or ghes %} +- {% data reusables.search.required_login %}{% endif %} +- {% data variables.product.prodname_pages %} 网站在 {% data variables.product.product_name %} 上不可搜索。 但如果源代码内容存在于仓库的默认分支中，您可以使用代码搜索来搜索。 更多信息请参阅“[搜索代码](/search-github/searching-on-github/searching-code)”。 有关 {% data variables.product.prodname_pages %} 的更多信息，请参阅“[什么是 GitHub Pages？ ](/articles/what-is-github-pages/)” +- 目前我们的搜索不支持精确匹配。 +- 每当您在代码文件中搜索时，将仅返回每个文件中的前两个结果。 + +{% endnote %} + +在 {% data variables.product.product_name %} 上搜索后，您可以对结果排序，或者单击侧栏中的任一语言进一步改进搜索。 更多信息请参阅“[对搜索结果排序](/search-github/getting-started-with-searching-on-github/sorting-search-results)”。 + +每次推送更改到 {% data variables.product.product_name %} 时，{% data variables.product.product_name %} 搜索都会使用 ElasticSearch 群集对项目编制索引。 议题和拉取请求在创建或修改时都会编制索引。 + +## {% data variables.product.prodname_dotcom %} 上的搜索类型 + +您可以在 {% data variables.product.product_location %} 上可以访问的所有仓库中搜索以下信息。 + +- [仓库](/search-github/searching-on-github/searching-for-repositories) +- [主题](/search-github/searching-on-github/searching-topics) +- [议题和拉取请求](/search-github/searching-on-github/searching-issues-and-pull-requests){% ifversion fpt %} +- [讨论](/search-github/searching-on-github/searching-discussions){% endif %} +- [代码](/search-github/searching-on-github/searching-code) +- [提交](/search-github/searching-on-github/searching-commits) +- [用户](/search-github/searching-on-github/searching-users) +- [包](/search-github/searching-on-github/searching-for-packages) +- [Wikis](/search-github/searching-on-github/searching-wikis) + +## 使用可视界面搜索 + +或者，您也可以使用 {% data variables.search.search_page_url %} 或 {% data variables.search.advanced_url %} 搜索 {% data variables.product.product_name %}。 + +{% data variables.search.advanced_url %} 提供用于构建搜索查询的可视界面。 您可以按各种因素过滤搜索，例如仓库具有的星标数或复刻数。 在填写高级搜索字段时，您的查询将在顶部搜索栏中自动构建。 + +![高级搜索](/assets/images/help/search/advanced_search_demo.gif) + +{% ifversion fpt or ghes or ghae-next %} + +## Searching repositories on {% data variables.product.prodname_dotcom_the_website %} from your private enterprise environment + +If you use {% ifversion fpt %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae-next %} or {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} and you're a member of a {% data variables.product.prodname_dotcom_the_website %} organization using {% data variables.product.prodname_ghe_cloud %}, an enterprise owner for your {% data variables.product.prodname_enterprise %} environment can enable {% data variables.product.prodname_github_connect %} so that you can search across both environments at the same time{% ifversion ghes or ghae %} from {% data variables.product.product_name %}{% endif %}. For more information, see the following. + +{% ifversion fpt or ghes %} +- "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/{% ifversion ghes %}{{ currentVersion }}{% else %}github-enterprise@latest{% endif %}/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_server %} documentation{% endif %}{% ifversion ghae-next %} +- "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/github-ae@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_managed %} documentation +{% endif %} + +{% ifversion ghes or ghae-next %} + +要按环境限制搜索范围，可以使用 {% data variables.search.advanced_url %} 上的过滤选项，或者使用 `environment:` 搜索前缀。 若只搜索 {% data variables.product.product_name %} 上的内容，请使用搜索语法 `environment:local`。 若只搜索 {% data variables.product.prodname_dotcom_the_website %} 上的内容，则使用 `environment:github`。 + +Your enterprise owner on {% data variables.product.product_name %} can enable {% data variables.product.prodname_unified_search %} for all public repositories, all private repositories, or only certain private repositories in the connected {% data variables.product.prodname_ghe_cloud %} organization. + +When you search from {% data variables.product.product_name %}, you can only search in the private repositories that you have access to in the connected {% data variables.product.prodname_dotcom_the_website %} organization. Enterprise owners for {% data variables.product.product_name %} and organization owners on {% data variables.product.prodname_dotcom_the_website %} cannot search private repositories owned by your account on {% data variables.product.prodname_dotcom_the_website %}. To search the applicable private repositories, you must enable private repository search for your personal accounts on {% data variables.product.product_name %}. For more information, see "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment)." + +{% endif %} + +{% endif %} + +## 延伸阅读 + +- "[了解搜索语法](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)" +- "[在 GitHub 上搜索](/articles/searching-on-github)" diff --git a/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md b/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md new file mode 100644 index 0000000000..3d3799ac30 --- /dev/null +++ b/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md @@ -0,0 +1,54 @@ +--- +title: Enabling GitHub.com repository search from your private enterprise environment +shortTitle: Search GitHub.com from enterprise +intro: 'You can connect your personal accounts on {% data variables.product.prodname_dotcom_the_website %} and your private {% data variables.product.prodname_enterprise %} environment to search for content in certain {% data variables.product.prodname_dotcom_the_website %} repositories{% ifversion fpt %} from your private environment{% else %} from {% data variables.product.product_name %}{% endif %}.' +redirect_from: + - /articles/enabling-private-githubcom-repository-search-in-your-github-enterprise-account/ + - /articles/enabling-private-github-com-repository-search-in-your-github-enterprise-server-account/ + - /articles/enabling-private-githubcom-repository-search-in-your-github-enterprise-server-account/ + - /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 +versions: + fpt: '*' + ghes: '*' + ghae: next +topics: + - GitHub search +--- + +## About search for {% data variables.product.prodname_dotcom_the_website %} repositories from {% ifversion fpt %}your private enterprise environment{% else %}{% data variables.product.product_name %}{% endif %} + +You can search for designated private repositories on {% data variables.product.prodname_ghe_cloud %} from {% ifversion fpt %}your private {% data variables.product.prodname_enterprise %} environment{% else %}{% data variables.product.product_location %}{% ifversion ghae %} on {% data variables.product.prodname_ghe_managed %}{% endif %}{% endif %}. {% ifversion fpt %}For example, if you use {% data variables.product.prodname_ghe_server %}, you can search for private repositories from your enterprise from {% data variables.product.prodname_ghe_cloud %} in the web interface for {% data variables.product.prodname_ghe_server %}.{% endif %} + +## 基本要求 + +- An enterprise owner for {% ifversion fpt %}your private {% data variables.product.prodname_enterprise %} environment{% else %}{% data variables.product.product_name %}{% endif %} must enable {% data variables.product.prodname_github_connect %} and {% data variables.product.prodname_unified_search %} for private repositories. For more information, see the following.{% ifversion fpt or ghes %} + - "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/{% ifversion ghes %}{{ currentVersion }}{% else %}github-enterprise@latest{% endif %}/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_server %} documentation{% endif %}{% ifversion ghae-next %} + - "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/github-ae@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_managed %} documentation +{% endif %} + +- You must already have access to the private repositories and connect your account {% ifversion fpt %}in your private {% data variables.product.prodname_enterprise %} environment{% else %}on {% data variables.product.product_name %}{% endif %} with your account on {% data variables.product.prodname_dotcom_the_website %}. For more information about the repositories you can search, see "[About searching on GitHub](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github#searching-repositories-on-githubcom-from-your-private-enterprise-environment)." + +## Enabling GitHub.com repository search from {% ifversion fpt %}your private {% data variables.product.prodname_enterprise %} environment{% else %}{% data variables.product.product_name %}{% endif %} + +{% ifversion fpt %} + +For more information, see the following. + +| Your enterprise environment | 更多信息 | +|:--------------------------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| {% data variables.product.prodname_ghe_server %} | "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/enterprise-server@latest/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-enterprise-server)" |{% ifversion ghae-next %} +| +| {% data variables.product.prodname_ghe_managed %} | "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/github-ae@latest//search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-ae)" +{% endif %} + +{% elsif ghes or ghae %} + +1. Sign into {% data variables.product.product_name %} and {% data variables.product.prodname_dotcom_the_website %}. +1. On {% data variables.product.product_name %}, in the upper-right corner of any page, click your profile photo, then click **Settings**. ![用户栏中的 Settings 图标](/assets/images/help/settings/userbar-account-settings.png) +{% data reusables.github-connect.github-connect-tab-user-settings %} +{% data reusables.github-connect.connect-dotcom-and-enterprise %} +{% data reusables.github-connect.connect-dotcom-and-enterprise %} + +{% endif %} diff --git a/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/index.md b/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/index.md new file mode 100644 index 0000000000..cce7ed2960 --- /dev/null +++ b/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/index.md @@ -0,0 +1,21 @@ +--- +title: 开始在 GitHub 上搜索 +intro: 'You can use a wide range of syntax to search {% data variables.product.product_name %}. You can adjust the scope of your search, build and troubleshoot queries, and sort search results with qualifiers.' +redirect_from: + - /articles/getting-started-with-searching-on-github + - /github/searching-for-information-on-github/getting-started-with-searching-on-github +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +children: + - /about-searching-on-github + - /understanding-the-search-syntax + - /troubleshooting-search-queries + - /sorting-search-results + - /enabling-githubcom-repository-search-from-your-private-enterprise-environment +shortTitle: 在 GitHub 上开始搜索 +--- + diff --git a/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md b/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md new file mode 100644 index 0000000000..2ca76678d4 --- /dev/null +++ b/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md @@ -0,0 +1,75 @@ +--- +title: 排序搜索结果 +intro: '您可以使用 Sort（排序）菜单或通过将 `sort` 限定符添加到查询来排序 [{% data variables.product.product_name %} 搜索](/articles/searching-on-github)结果。' +redirect_from: + - /articles/sorting-search-results + - /github/searching-for-information-on-github/sorting-search-results + - /github/searching-for-information-on-github/getting-started-with-searching-on-github/sorting-search-results +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +使用 Sort（排序）菜单可按相关性、星号数量、复刻数量以及项目最近更新时间来排序结果。 + + ![含有排序搜索结果选项的菜单](/assets/images/help/search/repo-search-sort.png) + +要按交互、反应、作者日期、提交者日期或项目最近更新时间来排序，您可以将 `sort` 限定符添加到搜索查询。 + +## 按交互排序 + +`sort:interactions` 限定符按最高反应和评论总数排序。 + +| 限定符 | 示例 | +| ---------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sort:interactions` 或 `sort:interactions-desc` | [**org:github sort:interactions**](https://github.com/search?q=org%3Agithub+sort%3Ainteractions&type=Issues) 匹配 {% data variables.product.product_name %} 所拥有仓库中的议题，按最高反应和评论总数排序。 | +| `sort:interactions-asc` | [**org:github sort:interactions-asc**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Ainteractions-asc&type=Issues) 匹配 {% data variables.product.product_name %} 所拥有仓库中的议题，按最低反应和评论总数排序。 | + +## 按反应排序 + +`sort:reactions` 限定符按反应数量或类型排序。 + +| 限定符 | 示例 | +| ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sort:reactions` 或 `sort:reactions-desc` | [**org:github sort:reactions**](https://github.com/search?q=org%3Agithub+sort%3Areactions&type=Issues) 匹配 {% data variables.product.product_name %} 所拥有仓库中的议题，按最高反应数量排序。 | +| `sort:reactions-asc` | [**org:github sort:reactions-asc**](https://github.com/search?q=org%3Agithub+sort%3Areactions-asc&type=Issues) 匹配 {% data variables.product.product_name %} 所拥有仓库中的议题，按反应数量升序排序（最少到最多）。 | +| sort:reactions-reaction | [**org:github sort:reactions-+1**](https://github.com/search?q=org%3Agithub+sort%3Areactions-%2B1&type=Issues) 匹配 {% data variables.product.product_name %} 所拥有仓库中的议题，按最多赞成 (:+1:) 反应数排序。 | +| | [**org:github sort:reactions--1**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Areactions--1&type=Issues) 匹配 {% data variables.product.product_name %} 所拥有仓库中的议题，按最多不赞成 (:-1:) 反应数排序。 | +| | [**org:github sort:reactions-smile**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Areactions-smile&type=Issues) 匹配 {% data variables.product.product_name %} 所拥有仓库中的议题，按最多大笑 (:smile:) 反应数排序。 | +| | [**org:github sort:reactions-tada**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Areactions-tada&type=Issues) 匹配 {% data variables.product.product_name %} 所拥有仓库中的议题，按最多欢呼 (:tada:) 反应数排序。 | +| | [**org:github sort:reactions-heart**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Areactions-heart&type=Issues) 匹配 {% data variables.product.product_name %} 所拥有仓库中的议题，按最多红心 (:heart:) 反应数排序。 | + +## 按作者日期排序 + +`sort:author-date` 限定符按作者日期降序或升序排序。 + +| 限定符 | 示例 | +| -------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sort:author-date` 或 `sort:author-date-desc` | [**feature org:github sort:author-date**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Aauthor-date&type=Commits) 匹配 {% data variables.product.product_name %} 所拥有仓库中含有 "feature" 字样的提交，按作者日期降序排序。 | +| `sort:author-date-asc` | [**feature org:github sort:author-date-asc**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Aauthor-date-asc&type=Commits) 匹配 {% data variables.product.product_name %} 所拥有仓库中含有 "feature" 字样的提交，按作者日期升序排序。 | + +## 按提交者日期排序 + +`sort:committer-date` 限定符按提交者日期降序或升序排序。 + +| 限定符 | 示例 | +| -------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `sort:committer-date` 或 `sort:committer-date-desc` | [**feature org:github sort:committer-date**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Acommitter-date&type=Commits) 匹配 {% data variables.product.product_name %} 所拥有仓库中含有 "feature" 字样的提交，按提交者日期降序排序。 | +| `sort:committer-date-asc` | [**feature org:github sort:committer-date-asc**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Acommitter-date-asc&type=Commits) 匹配 {% data variables.product.product_name %} 所拥有仓库中含有 "feature" 字样的提交，按提交者日期升序排序。 | + +## 按更新日期排序 + +`sort:updated` 限定符按项目最近更新日期排序。 + +| 限定符 | 示例 | +| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sort:updated` 或 `sort:updated-desc` | [**feature sort:updated**](https://github.com/search?utf8=%E2%9C%93&q=feature+sort%3Aupdated&type=Repositories) 匹配含有 "feature" 字样的仓库，按最近更新日期排序。 | +| `sort:updated-asc` | [**feature sort:updated-asc**](https://github.com/search?utf8=%E2%9C%93&q=feature+sort%3Aupdated-asc&type=Repositories) 匹配含有 "feature" 字样的仓库，按最远更新日期排序。 | + +## 延伸阅读 + +- "[About searching on {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)" +- "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)" diff --git a/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/troubleshooting-search-queries.md b/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/troubleshooting-search-queries.md new file mode 100644 index 0000000000..c4d5ff6c1b --- /dev/null +++ b/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/troubleshooting-search-queries.md @@ -0,0 +1,34 @@ +--- +title: 搜索查询故障排除 +intro: '如果您在 {% data variables.product.product_name %} 上搜索时遇到意外的结果，您可以通过查看常见问题和限制来进行故障排除。' +redirect_from: + - /articles/troubleshooting-search-queries + - /github/searching-for-information-on-github/troubleshooting-search-queries + - /github/searching-for-information-on-github/getting-started-with-searching-on-github/troubleshooting-search-queries +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +shortTitle: 搜索查询故障排除 +--- + +## 可能的超时 + +对于我们要执行的搜索基础架构来说，有些查询的计算成本很高。 为了让所有人都能快速搜索，我们会限制任何单个查询能够运行的时长。 在查询超过时间限制的极少数情况下，搜索将返回超时之前找到的所有匹配项，并通知您发生了超时。 + +达到超时并不意味着搜索结果不完整， 它只是表示查询在搜索所有可能的数据之前被中断。 + +## 查询长度限制 + +在 {% data variables.product.product_name %} 上搜索时，查询的长度有一些限制： + +* 不支持长度超过 256 个字符的查询 +* 您无法使用超过五个 `AND`、`OR` 或 `NOT` 运算符构造查询 + +特定搜索类型（例如，代码搜索）可能有其他限制。 查看这些搜索类型的文档以了解更多信息。 + +## 延伸阅读 + +- “[关于在 GitHub 上搜索](/search-github/getting-started-with-searching-on-github/about-searching-on-github)” 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 new file mode 100644 index 0000000000..ea82099694 --- /dev/null +++ b/translations/zh-CN/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md @@ -0,0 +1,100 @@ +--- +title: 了解搜索语法 +intro: '搜索 {% data variables.product.product_name %} 时，您可以构建匹配特定数字和单词的查询。' +redirect_from: + - /articles/search-syntax/ + - /articles/understanding-the-search-syntax + - /github/searching-for-information-on-github/understanding-the-search-syntax + - /github/searching-for-information-on-github/getting-started-with-searching-on-github/understanding-the-search-syntax +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +shortTitle: 了解搜索语法 +--- + +## 查询大于或小于另一个值的值 + +您可以使用 `>`、`>=`、`<` 和 `<=` 搜索大于、大于等于、小于以及小于等于另一个值的值。 + +| 查询 | 示例 | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | +| >n | **[cats stars:>1000](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%3E1000&type=Repositories)** 匹配含有 "cats" 字样、星标超过 1000 个的仓库。 | +| >=n | **[cats topics:>=5](https://github.com/search?utf8=%E2%9C%93&q=cats+topics%3A%3E%3D5&type=Repositories)** 匹配含有 "cats" 字样、有 5 个或更多主题的仓库。 | +| <n | **[cats size:<10000](https://github.com/search?utf8=%E2%9C%93&q=cats+size%3A%3C10000&type=Code)** 匹配小于 10 KB 的文件中含有 "cats" 字样的代码。 | +| <=n | **[cats stars:<=50](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%3C%3D50&type=Repositories)** 匹配含有 "cats" 字样、星标不超过 50 个的仓库。 | + +您还可以使用[范围查询](#query-for-values-between-a-range)搜索大于等于或小于等于另一个值的值。 + +| 查询 | 示例 | +| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| n..* | **[cats stars:10..*](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A10..*&type=Repositories)** 等同于 `stars:>=10` 并匹配含有 "cats" 字样、有 10 个或更多星号的仓库。 | +| *..n | **[cats stars:*..10](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%22*..10%22&type=Repositories)** 等同于 `stars:<=10` 并匹配含有 "cats" 字样、有不超过 10 个星号的仓库。 | + +## 查询范围之间的值 + +您可以使用范围语法 n..n 搜索范围内的值，其中第一个数字 _n_ 是最低值，而第二个是最高值。 + +| 查询 | 示例 | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | +| n..n | **[cats stars:10..50](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A10..50&type=Repositories)** 匹配含有 "cats" 字样、有 10 到 50 个星号的仓库。 | + +## 查询日期 + +您可以通过使用 `>`、`>=`、`<`、`<=` 和[范围查询](#query-for-values-between-a-range)搜索早于或晚于另一个日期，或者位于日期范围内的日期。 {% data reusables.time_date.date_format %} + +| 查询 | 示例 | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| >YYYY-MM-DD | **[cats created:>2016-04-29](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3E2016-04-29&type=Issues)** 匹配含有 "cats" 字样、在 2016 年 4 月 29 日之后创建的议题。 | +| >=YYYY-MM-DD | **[cats created:>=2017-04-01](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3E%3D2017-04-01&type=Issues)** 匹配含有 "cats" 字样、在 2017 年 4 月 1 日或之后创建的议题。 | +| <YYYY-MM-DD | **[cats pushed:<2012-07-05](https://github.com/search?q=cats+pushed%3A%3C2012-07-05&type=Code&utf8=%E2%9C%93)** 匹配在 2012 年 7 月 5 日之前推送的仓库中含有 "cats" 字样的代码。 | +| <=YYYY-MM-DD | **[cats created:<=2012-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3C%3D2012-07-04&type=Issues)** 匹配含有 "cats" 字样、在 2012 年 7 月 4 日或之前创建的议题。 | +| YYYY-MM-DD..YYYY-MM-DD | **[cats pushed:2016-04-30..2016-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+pushed%3A2016-04-30..2016-07-04&type=Repositories)** 匹配含有 "cats" 字样、在 2016 年 4 月末到 7 月之间推送的仓库。 | +| YYYY-MM-DD..* | **[cats created:2012-04-30..*](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2012-04-30..*&type=Issues)** 匹配在 2012 年 4 月 30 日之后创建、含有 "cats" 字样的议题。 | +| *..YYYY-MM-DD | **[cats created:*..2012-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A*..2012-07-04&type=Issues)** 匹配在 2012 年 7 月 4 日之前创建、含有 "cats" 字样的议题。 | + +{% data reusables.time_date.time_format %} + +| 查询 | 示例 | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| YYYY-MM-DDTHH:MM:SS+00:00 | **[cats created:2017-01-01T01:00:00+07:00..2017-03-01T15:30:15+07:00](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2017-01-01T01%3A00%3A00%2B07%3A00..2017-03-01T15%3A30%3A15%2B07%3A00&type=Issues)** 匹配在 2017 年 1 月 1 日凌晨 1 点（UTC 偏移为 `07:00`）与 2017 年 3 月 1 日下午 3 点（UTC 偏移为 `07:00`）之间创建的议题。 UTC 偏移量 `07:00`，2017 年 3 月 1 日下午 3 点。 UTC 偏移量 `07:00`。 | +| YYYY-MM-DDTHH:MM:SSZ | **[cats created:2016-03-21T14:11:00Z..2016-04-07T20:45:00Z](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2016-03-21T14%3A11%3A00Z..2016-04-07T20%3A45%3A00Z&type=Issues)** 匹配在 2016 年 3 月 21 日下午 2:11 与 2016 年 4 月 7 日晚上 8:45 之间创建的议题。 | + +## 排除特定结果 + +您可以使用 `NOT` 语法排除包含特定字词的结果。 `NOT` 运算符只能用于字符串关键词， 不适用于数字或日期。 + +| 查询 | 示例 | +| ----- | ----------------------------------------------------------------------------------------------------------------------- | +| `NOT` | **[hello NOT world](https://github.com/search?q=hello+NOT+world&type=Repositories)** 匹配含有 "hello" 字样但不含有 "world" 字样的仓库。 | + +缩小搜索结果范围的另一种途径是排除特定的子集。 您可以为任何搜索限定符添加 `-` 前缀，以排除该限定符匹配的所有结果。 + +| 查询 | 示例 | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| -QUALIFIER | **[cats stars:>10 -language:javascript](https://github.com/search?q=cats+stars%3A>10+-language%3Ajavascript&type=Repositories)** 匹配含有 "cats" 字样、有超过 10 个星号但并非以 JavaScript 编写的仓库。 | +| | **[mentions:defunkt -org:github](https://github.com/search?utf8=%E2%9C%93&q=mentions%3Adefunkt+-org%3Agithub&type=Issues)** 匹配提及 @defunkt 且不在 GitHub 组织仓库中的议题 | + +## 对带有空格的查询使用引号 + +如果搜索含有空格的查询，您需要用引号将其括起来。 例如： + +* [cats NOT "hello world"](https://github.com/search?utf8=✓&q=cats+NOT+"hello+world"&type=Repositories) 匹配含有 "cats" 字样但不含有 "hello world" 字样的仓库。 +* [build label:"bug fix"](https://github.com/search?utf8=%E2%9C%93&q=build+label%3A%22bug+fix%22&type=Issues) 匹配具有标签 "bug fix"、含有 "build" 字样的议题。 + +某些非字母数字符号（例如空格）会从引号内的代码搜索查询中删除，因此结果可能出乎意料。 + +{% ifversion fpt or ghes or ghae %} +## 使用用户名的查询 + +如果搜索查询包含需要用户名的限定符，例如 `user`、`actor` 或 `assignee`，您可以使用任何 {% data variables.product.product_name %} 用户名指定特定人员，或使用 `@me` 指定当前用户。 + +| 查询 | 示例 | +| -------------------- | ------------------------------------------------------------------------------------------------------------- | +| `QUALIFIER:USERNAME` | [`author:nat`](https://github.com/search?q=author%3Anat&type=Commits) 匹配 @nat 创作的提交。 | +| `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/index.md b/translations/zh-CN/content/search-github/index.md new file mode 100644 index 0000000000..393be5750e --- /dev/null +++ b/translations/zh-CN/content/search-github/index.md @@ -0,0 +1,20 @@ +--- +title: 在 GitHub 上搜索信息 +intro: 使用不同类型的搜索来查找您想要的信息。 +redirect_from: + - /categories/78/articles/ + - /categories/search/ + - /categories/searching-for-information-on-github + - /github/searching-for-information-on-github +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +children: + - /getting-started-with-searching-on-github + - /searching-on-github +shortTitle: 在 GitHub 上搜索 +--- + diff --git a/translations/zh-CN/content/search-github/searching-on-github/finding-files-on-github.md b/translations/zh-CN/content/search-github/searching-on-github/finding-files-on-github.md new file mode 100644 index 0000000000..0f05432fb7 --- /dev/null +++ b/translations/zh-CN/content/search-github/searching-on-github/finding-files-on-github.md @@ -0,0 +1,32 @@ +--- +title: 在 GitHub 上查找文件 +intro: '您可以使用文件查找器在仓库中搜索文件。 To search for a file in multiple repositories on {% data variables.product.product_name %}, use the [`filename` code search qualifier](/search-github/searching-on-github/searching-code#search-by-filename).' +redirect_from: + - /articles/finding-files-on-github + - /github/searching-for-information-on-github/finding-files-on-github + - /github/searching-for-information-on-github/searching-on-github/finding-files-on-github +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +{% tip %} + +**提示：** + +- 文件查找器的结果不包括某些目录，例如 `build`、`log`、`tmp` 和 `vendor`。 要搜索这些目录中的文件，请使用 [`filename` 代码搜索限定符](/search-github/searching-on-github/searching-code#search-by-filename)。 +- 按键盘上的 `t` 键也可以打开文件查找器。 更多信息请参阅“[键盘快捷键](/articles/keyboard-shortcuts)”。 + +{% endtip %} + +{% data reusables.repositories.navigate-to-repo %} +2. 在文件列表上方，单击 **Go to file（转到文件）**。 ![查找文件按钮](/assets/images/help/search/find-file-button.png) +3. 在搜索字段中，键入要查找文件的名称。 ![查找文件搜索字段](/assets/images/help/search/find-file-search-field.png) +4. 在结果列表中 ，单击要查找的文件。 + +## 延伸阅读 + +- “[关于在 GitHub 上搜索](/search-github/getting-started-with-searching-on-github/about-searching-on-github)” diff --git a/translations/zh-CN/content/search-github/searching-on-github/index.md b/translations/zh-CN/content/search-github/searching-on-github/index.md new file mode 100644 index 0000000000..d3f0e86d5f --- /dev/null +++ b/translations/zh-CN/content/search-github/searching-on-github/index.md @@ -0,0 +1,27 @@ +--- +title: 在 GitHub 上搜索 +intro: You can use qualifiers to narrow your search and focus on specific categories of information. +redirect_from: + - /articles/searching-on-github + - /github/searching-for-information-on-github/searching-on-github +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +children: + - /finding-files-on-github + - /searching-for-repositories + - /searching-topics + - /searching-code + - /searching-commits + - /searching-issues-and-pull-requests + - /searching-discussions + - /searching-github-marketplace + - /searching-users + - /searching-for-packages + - /searching-wikis + - /searching-in-forks +--- + diff --git a/translations/zh-CN/content/search-github/searching-on-github/searching-code.md b/translations/zh-CN/content/search-github/searching-on-github/searching-code.md new file mode 100644 index 0000000000..0892d9a32e --- /dev/null +++ b/translations/zh-CN/content/search-github/searching-on-github/searching-code.md @@ -0,0 +1,112 @@ +--- +title: 搜索代码 +intro: '您可以在 {% data variables.product.product_name %} 上搜索代码，并使用这些代码搜索限定符的任意组合缩小结果范围。' +redirect_from: + - /articles/searching-code + - /github/searching-for-information-on-github/searching-files-in-a-repository-for-exact-matches + - /github/searching-for-information-on-github/searching-code-for-exact-matches + - /github/searching-for-information-on-github/searching-code + - /github/searching-for-information-on-github/searching-on-github/searching-code +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +{% data reusables.search.you-can-search-globally %} 更多信息请参阅“[关于在 GitHub 上搜索](/search-github/getting-started-with-searching-on-github/about-searching-on-github)”。 + +您只能使用这些代码搜索限定符搜索代码。 搜索代码时，专用于仓库、用户或提交的搜索限定符将不起作用。 + +{% data reusables.search.syntax_tips %} + +## 代码搜索的注意事项 + +由于搜索代码的复杂性，执行搜索的方式有一些限制： + +{% ifversion fpt or ghes %} +- {% data reusables.search.required_login %}{% endif %} +- [复刻](/articles/about-forks)中的代码仅当复刻的星号超过父级仓库时可搜索。 星号少于父仓库的复刻**不**为代码搜索编索引。 要在搜索结果中包括星号比其父项多的复刻，您需要将 `fork:true` 或 `fork:only` 添加到查询。 更多信息请参阅“[在复刻中搜索](/search-github/searching-on-github/searching-in-forks)”。 +- 只有_默认分支_被索引用于代码搜索。{% ifversion fpt %} +- 只有小于 384 KB 的文件可搜索。{% else %}* 只有小于 5 MB 的文件可搜索。 +- 只有每个文件的前 500 KB 可搜索。{% endif %} +- 只能搜索少于 500,000 个文件的仓库。{% ifversion fpt %} +- 只能搜索去年有活动或已在搜索结果中返回的仓库。{% endif %} +- 除了 [`filename`](#search-by-filename) 搜索以外，搜索源代码时必须始终包括至少一个搜索词。 例如，搜索 [`language:javascript`](https://github.com/search?utf8=%E2%9C%93&q=language%3Ajavascript&type=Code&ref=searchresults) 无效，而搜索 [`amazing language:javascript`](https://github.com/search?utf8=%E2%9C%93&q=amazing+language%3Ajavascript&type=Code&ref=searchresults) 有效。 +- 搜索结果最多可显示同一文件的两个分段，但文件内可能有更多结果。 +- 您无法使用以下通配符作为搜索查询的一部分：. , : ; / \ ` ' " = * ! ? # $ & + ^ | ~ < > ( ) { } [ ] @. 搜索只会忽略这些符号。 + +## 按文件内容或文件路径搜索 + +使用 `in` 限定符，您可以将搜索限制为源代码文件的内容、文件路径或两者。 如果省略此限定符，则只搜索文件内容。 + +| 限定符 | 示例 | +| --------- | ------------------------------------------------------------------------------------------------------------------------ | +| `in:file` | [**octocat in:file**](https://github.com/search?q=octocat+in%3Afile&type=Code) 匹配文件内容中出现 "octocat" 的代码。 | +| `in:path` | [**octocat in:path**](https://github.com/search?q=octocat+in%3Apath&type=Code) 匹配文件路径中出现 "octocat" 的代码。 | +| | [**octocat in:file,path**](https://github.com/search?q=octocat+in%3Afile%2Cpath&type=Code) 匹配文件内容或文件路径中出现 "octocat" 的代码。 | + +## 在用户或组织的仓库内搜索 + +要在特定用户或组织拥有的所有仓库中搜索代码，您可以使用 `user` 或 `org` 限定符。 要在特定仓库中搜索代码，您可以使用 `repo` 限定符。 + +| 限定符 | 示例 | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**user:defunkt extension:rb**](https://github.com/search?q=user%3Agithub+extension%3Arb&type=Code) 匹配来自 @defunkt、以 .rb 结尾的代码。 | +| org:ORGNAME | [**org:github extension:js**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+extension%3Ajs&type=Code) 匹配来自 GitHub、以 .js 结尾的代码。 | +| repo:USERNAME/REPOSITORY | [**repo:mozilla/shumway extension:as**](https://github.com/search?q=repo%3Amozilla%2Fshumway+extension%3Aas&type=Code) 匹配来自 @mozilla 的 shumway 项目、以 .as 结尾的代码。 | + +## 按文件位置搜索 + +您可使用 `path` 限定符搜索仓库中特定位置显示的源代码。 使用 `path:/` 可搜索位于仓库根目录级别的文件。 或者，指定目录名称或目录路径以搜索位于该命令或其任何子目录中的文件。 + +| 限定符 | 示例 | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| path:/ | [**octocat filename:readme path:/**](https://github.com/search?utf8=%E2%9C%93&q=octocat+filename%3Areadme+path%3A%2F&type=Code) 匹配位于仓库根目录级别且含有 "octocat" 字样的 _readme_ 文件。 | +| path:DIRECTORY | [**form path:cgi-bin language:perl**](https://github.com/search?q=form+path%3Acgi-bin+language%3Aperl&type=Code) matches Perl files with the word "form" in the cgi-bin directory, or in any of its subdirectories. | +| path:PATH/TO/DIRECTORY | [**console path:app/public language:javascript**](https://github.com/search?q=console+path%3A%22app%2Fpublic%22+language%3Ajavascript&type=Code) matches JavaScript files with the word "console" in the app/public directory, or in any of its subdirectories (even if they reside in app/public/js/form-validators). | + +## 按语言搜索 + + +您可以基于所编写的语言搜索代码。 `language` 限定符可以是语言名称或别名。 For a full list of supported languages with their names and aliases, see the [github/linguist repository](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml). + +| 限定符 | 示例 | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| language:LANGUAGE | [**element language:xml size:100**](https://github.com/search?q=element+language%3Axml+size%3A100&type=Code) 匹配标记为 XML 且恰好有 100 个字节的并含有 "element" 字样的代码。 | +| | [**display language:scss**](https://github.com/search?q=display+language%3Ascss&type=Code) 匹配标记为 SCSS 且含有 "display" 字样的代码。 | +| | [**org:mozilla language:markdown**](https://github.com/search?utf8=%E2%9C%93&q=org%3Amozilla+language%3Amarkdown&type=Code) 匹配标记为 Markdown 且来自所有 @mozilla 仓库的代码。 | + +## 按文件大小搜索 + +您可以使用 `size` 限定符基于代码所在文件的大小搜索源代码。 `size` 限定符使用[大于、小于和范围限定符](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)基于在其中找到代码的文件的字节大小来过滤结果。 + +| 限定符 | 示例 | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| size:n | [**function size:>10000 language:python**](https://github.com/search?q=function+size%3A%3E10000+language%3Apython&type=Code) 匹配含有 "function" 字样、以 Python 编写、位于大于 10 KB 的文件中的代码。 | + +## 按文件名搜索 + +`filename` 限定符匹配具有特定文件名的代码文件。 您还可以使用文件查找器在仓库中查找文件。 更多信息请参阅“[在 GitHub 上查找文件](/search-github/searching-on-github/finding-files-on-github)”。 + +| 限定符 | 示例 | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| filename:FILENAME | [**filename:linguist**](https://github.com/search?utf8=%E2%9C%93&q=filename%3Alinguist&type=Code) 匹配名为 "linguist" 的文件。 | +| | [**filename:.vimrc commands**](https://github.com/search?q=filename%3A.vimrc+commands&type=Code) 匹配含有 "commands" 字样的 *.vimrc* 文件。 | +| | [**filename:test_helper path:test language:ruby**](https://github.com/search?q=minitest+filename%3Atest_helper+path%3Atest+language%3Aruby&type=Code) 匹配 *test* 目录内名为 *test_helper* 的 Ruby 文件。 | + +## 按文件扩展名搜索 + +`extension` 限定符匹配具有特定文件扩展名的代码文件。 + +| 限定符 | 示例 | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| extension:EXTENSION | [**form path:cgi-bin extension:pm**](https://github.com/search?q=form+path%3Acgi-bin+extension%3Apm&type=Code) 匹配含有 "form" 字样、位于 cgi-bin 下且具有 .pm 文件扩展名的代码。 | +| | [**icon size:>200000 extension:css**](https://github.com/search?utf8=%E2%9C%93&q=icon+size%3A%3E200000+extension%3Acss&type=Code) 匹配大于 200 KB、以 .css 结尾且含有 "icon" 字样的文件。 | + +## 延伸阅读 + +- “[排序搜索结果](/search-github/getting-started-with-searching-on-github/sorting-search-results/)” +- "[在复刻中搜索](/search-github/searching-on-github/searching-in-forks)"{% ifversion fpt %} +- "[在 {% data variables.product.prodname_dotcom %} 上导航代码](/github/managing-files-in-a-repository/navigating-code-on-github)"{% endif %} diff --git a/translations/zh-CN/content/search-github/searching-on-github/searching-commits.md b/translations/zh-CN/content/search-github/searching-on-github/searching-commits.md new file mode 100644 index 0000000000..0ae0f6422c --- /dev/null +++ b/translations/zh-CN/content/search-github/searching-on-github/searching-commits.md @@ -0,0 +1,111 @@ +--- +title: 搜索提交 +intro: '您可以在 {% data variables.product.product_name %} 上搜索提交，并使用这些提交搜索限定符的任意组合缩小结果范围。' +redirect_from: + - /articles/searching-commits + - /github/searching-for-information-on-github/searching-commits + - /github/searching-for-information-on-github/searching-on-github/searching-commits +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +您可以在所有 {% data variables.product.product_name %} 内全局搜索提交，也可以在特定仓库或组织内搜索提交。 更多信息请参阅“[关于在 {% data variables.product.company_short %} 上搜索](/search-github/getting-started-with-searching-on-github/about-searching-on-github)”。 + +当您搜索提交时，仅搜索仓库的[默认分支](/articles/about-branches)。 + +{% data reusables.search.syntax_tips %} + +## 在提交消息内搜索 + +您可以在消息中查找包含特定字词的提交。 例如，[**fix typo**](https://github.com/search?q=fix+typo&type=Commits) 匹配包含 "fix" 和 "typo" 字样的提交。 + +## 按作者或提交者搜索 + +您可以使用 `author` 或 `committer` 限定符按特定用户查找提交。 + +| 限定符 | 示例 | +| ------------------------- | -------------------------------------------------------------------------------------------------------- | +| author:USERNAME | [**author:defunkt**](https://github.com/search?q=author%3Adefunkt&type=Commits) 匹配 @defunkt 创作的提交。 | +| committer:USERNAME | [**committer:defunkt**](https://github.com/search?q=committer%3Adefunkt&type=Commits) 匹配 @defunkt 提交的提交。 | + +`author-name` 和 `committer-name` 限定符匹配按作者或提交者姓名的提交。 + +| 限定符 | 示例 | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------- | +| author-name:NAME | [**author-name:wanstrath**](https://github.com/search?q=author-name%3Awanstrath&type=Commits) 匹配作者姓名中包含 "wanstrath" 的提交。 | +| committer-name:NAME | [**committer-name:wanstrath**](https://github.com/search?q=committer-name%3Awanstrath&type=Commits) 匹配提交者姓名中包含 "wanstrath" 的提交。 | + +`author-email` 和 `committer-email` 限定符按作者或提交者的完整电子邮件地址匹配提交。 + +| 限定符 | 示例 | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | +| author-email:EMAIL | [**author-email:chris@github.com**](https://github.com/search?q=author-email%3Achris%40github.com&type=Commits) 匹配 chris@github.com 创作的提交。 | +| committer-email:EMAIL | [**committer-email:chris@github.com**](https://github.com/search?q=committer-email%3Achris%40github.com&type=Commits) 匹配 chris@github.com 提交的提交。 | + +## 按创作或提交日期搜索 + +使用 `author-date` 和 `committer-date` 限定符可匹配指定日期范围内创作或提交的提交。 + +{% data reusables.search.date_gt_lt %} + +| 限定符 | 示例 | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | +| author-date:YYYY-MM-DD | [**author-date:<2016-01-01**](https://github.com/search?q=author-date%3A<2016-01-01&type=Commits) 匹配 2016-01-01 之前创作的提交。 | +| committer-date:YYYY-MM-DD | [**committer-date:>2016-01-01**](https://github.com/search?q=committer-date%3A>2016-01-01&type=Commits) 匹配 2016-01-01 之后的提交。 | + +## 过滤合并提交 + +`merge` 限定符过滤合并提交。 + +| 限定符 | 示例 | +| ------------- | ---------------------------------------------------------------------------------- | +| `merge:true` | [**merge:true**](https://github.com/search?q=merge%3Atrue&type=Commits) 匹配合并提交。 | +| `merge:false` | [**merge:false**](https://github.com/search?q=merge%3Afalse&type=Commits) 匹配非合并提交。 | + +## 按哈希搜索 + +`hash` 限定符匹配具有指定 SHA-1 哈希的提交。 + +| 限定符 | 示例 | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| hash:HASH | [**hash:124a9a0ee1d8f1e15e833aff432fbb3b02632105**](https://github.com/github/gitignore/search?q=hash%3A124a9a0ee1d8f1e15e833aff432fbb3b02632105&type=Commits) 匹配具有哈希 `124a9a0ee1d8f1e15e833aff432fbb3b02632105` 的提交。 | + +## 按父项搜索 + +`parent` 限定符匹配其父项具有指定 SHA-1 哈希的提交。 + +| 限定符 | 示例 | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| parent:HASH | [**parent:124a9a0ee1d8f1e15e833aff432fbb3b02632105**](https://github.com/github/gitignore/search?q=parent%3A124a9a0ee1d8f1e15e833aff432fbb3b02632105&type=Commits&utf8=%E2%9C%93) 匹配具有哈希 `124a9a0ee1d8f1e15e833aff432fbb3b02632105` 的提交的子项。 | + +## 按树搜索 + +`tree` 限定符匹配具有指定 SHA-1 git 树哈希的提交。 + +| 限定符 | 示例 | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------- | +| tree:HASH | [**tree:99ca967**](https://github.com/github/gitignore/search?q=tree%3A99ca967&type=Commits) 匹配引用树哈希 `99ca967` 的提交。 | + +## 在用户或组织的仓库内搜索 + +要在特定用户或组织拥有的所有仓库中搜索提交，请使用 `user` 或 `org` 限定符。 要在特定仓库中搜索提交，请使用 `repo` 限定符。 + +| 限定符 | 示例 | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**gibberish user:defunkt**](https://github.com/search?q=gibberish+user%3Adefunkt&type=Commits&utf8=%E2%9C%93) 匹配 @defunkt 拥有的仓库中含有 "gibberish" 字样的提交消息。 | +| org:ORGNAME | [**test org:github**](https://github.com/search?utf8=%E2%9C%93&q=test+org%3Agithub&type=Commits) 匹配 @github 拥有的仓库中含有 "test" 字样的提交消息。 | +| repo:USERNAME/REPO | [**language repo:defunkt/gibberish**](https://github.com/search?utf8=%E2%9C%93&q=language+repo%3Adefunkt%2Fgibberish&type=Commits) 匹配 @defunkt 的 "gibberish" 仓库中含有 "language" 字样的提交消息。 | + +## 按仓库可见性过滤 + +`is` 限定符匹配具有指定可见性的仓库中的提交。 更多信息请参阅“[关于仓库](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)”。 + +| 限定符 | 示例 | ------------- | ------------- |{% ifversion fpt or ghes %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Commits) 匹配对公共仓库的提交。{% endif %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Commits) 匹配对内部仓库的提交。 | `is:private` | [**is:private**](https://github.com/search?q=is%3Aprivate&type=Commits) 匹配对私有仓库的提交。 + +## 延伸阅读 + +- “[排序搜索结果](/search-github/getting-started-with-searching-on-github/sorting-search-results/)” diff --git a/translations/zh-CN/content/search-github/searching-on-github/searching-discussions.md b/translations/zh-CN/content/search-github/searching-on-github/searching-discussions.md new file mode 100644 index 0000000000..a01b09b4c4 --- /dev/null +++ b/translations/zh-CN/content/search-github/searching-on-github/searching-discussions.md @@ -0,0 +1,113 @@ +--- +title: 搜索讨论 +intro: '您可以在 {% data variables.product.product_name %} 上搜索讨论，并使用搜索限定符缩小结果范围。' +versions: + fpt: '*' +topics: + - GitHub search +redirect_from: + - /github/searching-for-information-on-github/searching-discussions + - /github/searching-for-information-on-github/searching-on-github/searching-discussions +--- + +## 关于搜索讨论 + +您可以在所有 {% data variables.product.product_name %} 中全局搜索讨论，也可以在特定组织或仓库内搜索讨论。 更多信息请参阅“[关于在 {% data variables.product.prodname_dotcom %} 上搜索](/github/searching-for-information-on-github/about-searching-on-github)”。 + +{% data reusables.search.syntax_tips %} + +## 按标题、正文或评论搜索 + +使用 `in` 限定符可将讨论搜索范围限制在标题、正文或注释中。 您还可以组合限定符来搜索标题、正文或注释的组合。 省略 `in` 限定符时，{% data variables.product.product_name %} 将搜索标题、正文和注释。 + +| 限定符 | 示例 | +|:------------- |:----------------------------------------------------------------------------------------------------------------------------- | +| `in:title` | [**welcome in:title**](https://github.com/search?q=welcome+in%3Atitle&type=Discussions) 匹配标题中含有 "welcome" 的讨论。 | +| `in:body` | [**onboard in:title,body**](https://github.com/search?q=onboard+in%3Atitle%2Cbody&type=Discussions) 匹配标题或正文中含有 "onboard" 的讨论。 | +| `in:comments` | [**thanks in:comments**](https://github.com/search?q=thanks+in%3Acomment&type=Discussions) 匹配讨论注释中含有 "thanks" 的讨论。 | + +## 在用户或组织的仓库内搜索 + +要在特定用户或组织拥有的所有仓库中搜索讨论，您可以使用 `user` 或 `org` 限定符。 要在特定仓库中搜索讨论，您可以使用 `repo` 限定符。 + +| 限定符 | 示例 | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| user:USERNAME | [**user:octocat feedback**](https://github.com/search?q=user%3Aoctocat+feedback&type=Discussions) 匹配 @octocat 拥有的仓库中含有单词 "feedback" 的讨论。 | +| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=Discussions&utf8=%E2%9C%93) 匹配 GitHub 组织拥有的仓库中的讨论。 | +| repo:USERNAME/REPOSITORY | [**repo:nodejs/node created:<2021-01-01**](https://github.com/search?q=repo%3Anodejs%2Fnode+created%3A%3C2020-01-01&type=Discussions) 匹配 @nodejs' Node.js 运行时项目中在 2021 年 1 月之前创建的讨论。 | + +## 按仓库可见性过滤 + +您可以使用 `is` 限定符，按包含讨论的仓库的可见性进行过滤。 更多信息请参阅“[关于仓库](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)”。 + +| 限定符 | 示例 | :- | :- |{% ifversion fpt or ghes %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Discussions) 匹配公共仓库中的讨论。{% endif %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Discussions) 匹配内部仓库中的讨论。 | `is:private` | [**is:private tiramisu**](https://github.com/search?q=is%3Aprivate+tiramisu&type=Discussions) 匹配您有权访问的私有仓库含有单词 "tiramisu" 的讨论。 + +## 按作者搜索 + +`author` 限定符查找由特定用户创建的讨论。 + +| 限定符 | 示例 | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| author:USERNAME | [**cool author:octocat**](https://github.com/search?q=cool+author%3Aoctocat&type=Discussions) 匹配由 @octocat 创建的含有单词 "cool" 的讨论。 | +| | [**bootstrap in:body author:octocat**](https://github.com/search?q=bootstrap+in%3Abody+author%3Aoctocat&type=Discussions) 匹配由 @octocat 创建的正文中含有单词 "bootstrap" 的讨论。 | + +## 按评论者搜索 + +`commenter` 限定符查找含有特定用户评论的讨论。 + +| 限定符 | 示例 | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| commenter:USERNAME | [**github commenter:becca org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Abecca+org%3Agithub&type=Discussions) 匹配 GitHub 拥有的仓库中含有单词 "github" 并且由 @becca 评论的讨论。 | + +## 按涉及讨论的用户搜索 + +您可以使用 `involves` 限定符查找涉及特定用户的讨论。 该限定符返回由特定用户创建、提及该用户或包含该用户评论的讨论。 `involves` 限定符是单一用户 `author`、`mentions` 和 `commenter` 限定符之间的逻辑 OR（或）。 + +| 限定符 | 示例 | +|:------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------- | +| involves:USERNAME | **[involves:becca involves:octocat](https://github.com/search?q=involves%3Abecca+involves%3Aoctocat&type=Discussions)** 匹配涉及 @becca 或 @octocat 的讨论。 | +| | [**NOT beta in:body involves:becca**](https://github.com/search?q=NOT+beta+in%3Abody+involves%3Abecca&type=Discussions) 匹配涉及 @becca 且正文中不包含单词 "beta" 的讨论。 | + +## 按评论数量搜索 + +您可以使用 `comments` 限定符以及大于、小于和范围限定符以按评论数量搜索。 更多信息请参阅“[了解搜索语法](/github/searching-for-information-on-github/understanding-the-search-syntax)”。 + +| 限定符 | 示例 | +|:------------------------- |:-------------------------------------------------------------------------------------------------------------------- | +| comments:n | [**comments:>100**](https://github.com/search?q=comments%3A%3E100&type=Discussions) 匹配超过 100 条评论的讨论。 | +| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Discussions) 匹配具有 500 到 1,000 条评论的讨论。 | + +## 按交互数量搜索 + +您可以使用 `interactions` 限定符以及大于、小于和范围限定符按交互数量过滤讨论。 交互数量是对讨论的反应和评论数量。 更多信息请参阅“[了解搜索语法](/github/searching-for-information-on-github/understanding-the-search-syntax)”。 + +| 限定符 | 示例 | +|:------------------------- |:------------------------------------------------------------------------------------------------------------- | +| interactions:n | [** interactions:>2000**](https://github.com/search?q=interactions%3A%3E2000) 匹配超过 2,000 个交互的讨论。 | +| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) 匹配 500 至 1,000 个交互的讨论。 | + +## 按反应数量搜索 + +您可以使用 `reactions` 限定符以及大于、小于和范围限定符按反应数量过滤讨论。 更多信息请参阅“[了解搜索语法](/github/searching-for-information-on-github/understanding-the-search-syntax)”。 + +| 限定符 | 示例 | +|:------------------------- |:---------------------------------------------------------------------------------------------------- | +| reactions:n | [** reactions:>1000**](https://github.com/search?q=reactions%3A%3E500) 匹配超过 500 个反应的讨论。 | +| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) 匹配 500 至 1,000 个反应的讨论。 | + +## 按讨论创建或上次更新时间搜索 + +您可以基于创建时间或上次更新时间过滤讨论。 对于讨论创建，您可以使用 `created` 限定符；要了解讨论上次更新的时间，请使用 `updated` 限定符。 + +两个限定符都使用日期作为参数。 {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| 限定符 | 示例 | +|:-------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| created:YYYY-MM-DD | [**created:>2020-11-15**](https://github.com/search?q=created%3A%3E%3D2020-11-15&type=discussions) 匹配 2020 年 11 月 15 日之后创建的讨论。 | +| updated:YYYY-MM-DD | [**weird in:body updated:>=2020-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2020-12-01&type=Discussions) 匹配 2020 年 12 月之后更新的正文中含有单词 "weird" 的讨论。 | + +## 延伸阅读 + +- “[排序搜索结果](/search-github/getting-started-with-searching-on-github/sorting-search-results/)” diff --git a/translations/zh-CN/content/search-github/searching-on-github/searching-for-packages.md b/translations/zh-CN/content/search-github/searching-on-github/searching-for-packages.md new file mode 100644 index 0000000000..6931d54099 --- /dev/null +++ b/translations/zh-CN/content/search-github/searching-on-github/searching-for-packages.md @@ -0,0 +1,45 @@ +--- +title: 搜索包 +intro: '您可以在 {% data variables.product.product_name %} 上搜索包，并使用搜索限定符缩小结果范围。' +product: '{% data reusables.gated-features.packages %}' +permissions: Anyone can search for packages they have access to. +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +redirect_from: + - /github/searching-for-information-on-github/searching-for-packages + - /github/searching-for-information-on-github/searching-on-github/searching-for-packages +--- + +{% data reusables.package_registry.packages-ghes-release-stage %} + +## 关于搜索包 + +您可以在所有 {% data variables.product.product_name %} 中全局搜索包，也可以在特定组织内搜索包。 更多信息请参阅“[关于在 {% data variables.product.prodname_dotcom %} 上搜索](/search-github/getting-started-with-searching-on-github/about-searching-on-github)”。 + +{% ifversion ghes %} +您只能在 {% data variables.product.product_name %} 中搜索包，而不能在 {% data variables.product.prodname_dotcom_the_website %} 上搜索，即使启用了 {% data variables.product.prodname_github_connect %} 也一样。 +{% endif %} + +{% data reusables.search.syntax_tips %} + +## 搜索用户或组织的包 + +要查找特定用户或组织拥有的包，请使用 `user` 或 `org` 限定符。 + +| 限定符 | 示例 | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**user:codertocat**](https://github.com/search?q=user%3Acodertocat&type=RegistryPackages) 匹配 @codertocat 拥有的包 | +| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=RegistryPackages) 匹配 {% data variables.product.prodname_dotcom %} 组织拥有的包 | + +## 按包可见性过滤 + +要按包是公共还是私有来过滤搜索，请使用 `is` 限定符。 + +| 限定符 | 示例 | +| ------------ | -------------------------------------------------------------------------------------------------------------------- | +| `is:public` | [**is:public angular**](https://github.com/search?q=is%3Apublic+angular&type=RegistryPackages) 匹配含有文字 "angular" 的公共包 | +| `is:private` | [**is:private php**](https://github.com/search?q=is%3Aprivate+php&type=RegistryPackages) 匹配含有文字 "php" 的私有包 | diff --git a/translations/zh-CN/content/search-github/searching-on-github/searching-for-repositories.md b/translations/zh-CN/content/search-github/searching-on-github/searching-for-repositories.md new file mode 100644 index 0000000000..f2b383e575 --- /dev/null +++ b/translations/zh-CN/content/search-github/searching-on-github/searching-for-repositories.md @@ -0,0 +1,201 @@ +--- +title: 搜索仓库 +intro: '您可以在 {% data variables.product.product_name %} 上搜索仓库，并使用这些仓库搜索限定符的任意组合缩小结果范围。' +redirect_from: + - /articles/searching-repositories/ + - /articles/searching-for-repositories + - /github/searching-for-information-on-github/searching-for-repositories + - /github/searching-for-information-on-github/searching-on-github/searching-for-repositories +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +shortTitle: 搜索仓库 +--- + +您可以在所有 {% data variables.product.product_location %} 内全局搜索仓库，也可以在特定组织内搜索仓库。 更多信息请参阅“[关于在 {% data variables.product.prodname_dotcom %} 上搜索](/search-github/getting-started-with-searching-on-github/about-searching-on-github)”。 + +要在搜索结果中包括复刻，您需要将 `fork:true` 或 `fork:only` 添加到查询。 更多信息请参阅“[在复刻中搜索](/search-github/searching-on-github/searching-in-forks)”。 + +{% data reusables.search.syntax_tips %} + +## 按仓库名称、说明或自述文件内容搜索 + +通过 `in` 限定符，您可以将搜索限制为仓库名称、仓库说明、自述文件内容或这些的任意组合。 如果省略此限定符，则只搜索仓库名称和说明。 + +| 限定符 | 示例 | +| ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | +| `in:name` | [**jquery in:name**](https://github.com/search?q=jquery+in%3Aname&type=Repositories) 匹配仓库名称中含有 "jquery" 的仓库。 | +| `in:description` | [**jquery in:name,description**](https://github.com/search?q=jquery+in%3Aname%2Cdescription&type=Repositories) 匹配仓库名称或说明中含有 "jquery" 的仓库。 | +| `in:readme` | [**jquery in:readme**](https://github.com/search?q=jquery+in%3Areadme&type=Repositories) 匹配仓库自述文件中提及 "jquery" 的仓库。 | +| `repo:owner/name` | [**repo:octocat/hello-world**](https://github.com/search?q=repo%3Aoctocat%2Fhello-world) 匹配特定仓库名称。 | + +## 基于仓库的内容搜索 + +您可以使用 `in:readme` 限定符，通过搜索仓库自述文件中的内容来查找仓库。 更多信息请参阅“[关于自述文件](/github/creating-cloning-and-archiving-repositories/about-readmes)”。 + +除了使用 `in:readme` 以外，无法通过搜索仓库内的特定内容来查找仓库。 要搜索仓库内的特定文件或内容，您可以使用查找器或代码特定的搜索限定符。 更多信息请参阅“[在 {% data variables.product.prodname_dotcom %} 上查找文件](/search-github/searching-on-github/finding-files-on-github)”和“[搜索代码](/search-github/searching-on-github/searching-code)”。 + +| 限定符 | 示例 | +| ----------- | --------------------------------------------------------------------------------------------------------------------- | +| `in:readme` | [**octocat in:readme**](https://github.com/search?q=octocat+in%3Areadme&type=Repositories) 匹配仓库自述文件中提及 "octocat" 的仓库。 | + +## 在用户或组织的仓库内搜索 + +要在特定用户或组织拥有的所有仓库中搜索，您可以使用 `user` 或 `org` 限定符。 + +| 限定符 | 示例 | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**user:defunkt forks:>100**](https://github.com/search?q=user%3Adefunkt+forks%3A%3E%3D100&type=Repositories) 匹配来自 @defunkt、拥有超过 100 复刻的仓库。 | +| org:ORGNAME | [**org:github**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub&type=Repositories) 匹配来自 GitHub 的仓库。 | + +## 按仓库大小搜索 + +`size` 限定符使用大于、小于和范围限定符查找匹配特定大小（以千字节为单位）的仓库。 更多信息请参阅“[了解搜索语法](/github/searching-for-information-on-github/understanding-the-search-syntax)”。 + +| 限定符 | 示例 | +| ------------------------- | -------------------------------------------------------------------------------------------------------------- | +| size:n | [**size:1000**](https://github.com/search?q=size%3A1000&type=Repositories) 匹配恰好为 1 MB 的仓库。 | +| | [**size:>=30000**](https://github.com/search?q=size%3A%3E%3D30000&type=Repositories) 匹配至少为 30 MB 的仓库。 | +| | [**size:<50**](https://github.com/search?q=size%3A%3C50&type=Repositories) 匹配小于 50 KB 的仓库。 | +| | [**size:50..120**](https://github.com/search?q=size%3A50..120&type=Repositories) 匹配介于 50 KB 与 120 KB 之间的仓库。 | + +## 按关注者数量搜索 + +您可以使用 `followers` 限定符以及大于、小于和范围限定符，基于关注仓库的用户数量过滤仓库。 更多信息请参阅“[了解搜索语法](/github/searching-for-information-on-github/understanding-the-search-syntax)”。 + +| 限定符 | 示例 | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| followers:n | [**node followers:>=10000**](https://github.com/search?q=node+followers%3A%3E%3D10000) 匹配有 10,000 或更多关注者提及文字 "node" 的仓库。 | +| | [**styleguide linter followers:1..10**](https://github.com/search?q=styleguide+linter+followers%3A1..10&type=Repositories) 匹配拥有 1 到 10 个关注者并且提及 "styleguide linter" 一词的的仓库。 | + +## 按复刻数量搜索 + +`forks` 限定符使用大于、小于和范围限定符指定仓库应具有的复刻数量。 更多信息请参阅“[了解搜索语法](/github/searching-for-information-on-github/understanding-the-search-syntax)”。 + +| 限定符 | 示例 | +| ------------------------- | -------------------------------------------------------------------------------------------------------------- | +| forks:n | [**forks:5**](https://github.com/search?q=forks%3A5&type=Repositories) 匹配只有 5 个复刻的仓库。 | +| | [**forks:>=205**](https://github.com/search?q=forks%3A%3E%3D205&type=Repositories) 匹配具有至少 205 个复刻的仓库。 | +| | [**forks:<90**](https://github.com/search?q=forks%3A%3C90&type=Repositories) 匹配具有少于 90 个复刻的仓库。 | +| | [**forks:10..20**](https://github.com/search?q=forks%3A10..20&type=Repositories) 匹配具有 10 到 20 个复刻的仓库。 | + +## 按星号数量搜索 + +您可以使用大于、小于和范围限定符，基于仓库的星标数量来搜索仓库。 更多信息请参阅“[使用星标保存仓库](/github/getting-started-with-github/saving-repositories-with-stars)”和“[了解搜索语法](/github/searching-for-information-on-github/understanding-the-search-syntax)”。 + +| 限定符 | 示例 | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| stars:n | [**stars:500**](https://github.com/search?utf8=%E2%9C%93&q=stars%3A500&type=Repositories) 匹配恰好具有 500 个星号的仓库。 | +| | [**stars:10..20**](https://github.com/search?q=stars%3A10..20+size%3A%3C1000&type=Repositories) 匹配具有 10 到 20 个星号、小于 1000 KB 的仓库。 | +| | [**stars:>=500 fork:true language:php**](https://github.com/search?q=stars%3A%3E%3D500+fork%3Atrue+language%3Aphp&type=Repositories) 匹配具有至少 500 个星号，包括复刻的星号（以 PHP 编写）的仓库。 | + +## 按仓库创建或上次更新时间搜索 + +您可以基于创建时间或上次更新时间过滤仓库。 对于仓库创建，您可以使用 `created` 限定符；要了解仓库上次更新的时间，您要使用 `pushed` 限定符。 `pushed` 限定符将返回仓库列表，按仓库中任意分支上最近进行的提交排序。 + +两者均采用日期作为参数。 {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| 限定符 | 示例 | +| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| created:YYYY-MM-DD | [**webos created:<2011-01-01**](https://github.com/search?q=webos+created%3A%3C2011-01-01&type=Repositories) 匹配具有 "webos" 字样、在 2011 年之前创建的仓库。 | +| pushed:YYYY-MM-DD | [**css pushed:>2013-02-01**](https://github.com/search?utf8=%E2%9C%93&q=css+pushed%3A%3E2013-02-01&type=Repositories) 匹配具有 "css" 字样、在 2013 年 1 月之后收到推送的仓库。 | +| | [**case pushed:>=2013-03-06 fork:only**](https://github.com/search?q=case+pushed%3A%3E%3D2013-03-06+fork%3Aonly&type=Repositories) 匹配具有 "case" 字样、在 2013 年 3 月 6 日或之后收到推送并且作为复刻的仓库。 | + +## 按语言搜索 + +您可以根据仓库中代码的语言搜索仓库。 + +| 限定符 | 示例 | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | +| language:LANGUAGE | [**rails language:javascript**](https://github.com/search?q=rails+language%3Ajavascript&type=Repositories) 匹配具有 "rails" 字样、以 JavaScript 编写的仓库。 | + +## 按主题搜索 + +您可以找到按特定主题分类的所有仓库。 更多信息请参阅“[使用主题对仓库分类](/github/administering-a-repository/classifying-your-repository-with-topics)”。 + +| 限定符 | 示例 | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | +| topic:TOPIC | [**topic:jekyll**](https://github.com/search?utf8=%E2%9C%93&q=topic%3Ajekyll&type=Repositories&ref=searchresults)匹配已归类为 "jekyll" 主题的仓库。 | + +## 按主题数量搜索 + +您可以使用 `topics` 限定符以及大于、小于和范围限定符，根据应用于仓库的主题数量来搜索仓库。 更多信息请参阅“[使用主题对仓库分类](/github/administering-a-repository/classifying-your-repository-with-topics)”和“[了解搜索语法](/github/searching-for-information-on-github/understanding-the-search-syntax)”。 + +| 限定符 | 示例 | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------- | +| topics:n | [**topics:5**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A5&type=Repositories&ref=searchresults) 匹配具有五个主题的仓库。 | +| | [**topics:>3**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A%3E3&type=Repositories&ref=searchresults) 匹配超过三个主题的仓库。 | + +{% ifversion fpt or ghes %} + +## 按许可搜索 + +您可以根据仓库中许可的类型搜索仓库。 您必须使用许可关键字，按特定许可或许可系列来过滤仓库。 更多信息请参阅“[许可仓库](/github/creating-cloning-and-archiving-repositories/licensing-a-repository)”。 + +| 限定符 | 示例 | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| license:LICENSE_KEYWORD | [**license:apache-2.0**](https://github.com/search?utf8=%E2%9C%93&q=license%3Aapache-2.0&type=Repositories&ref=searchresults) 匹配根据 Apache License 2.0 授权的仓库。 | + +{% endif %} + +## 按仓库可见性搜索 + +您可以根据仓库的可见性过滤搜索。 更多信息请参阅“[关于仓库](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)”。 + +| 限定符 | 示例 | ------------- | ------------- |{% ifversion fpt or ghes %} | `is:public` | [**is:public org:github**](https://github.com/search?q=is%3Apublic+org%3Agithub&type=Repositories) 匹配 {% data variables.product.company_short %} 拥有的公共仓库。{% endif %} | `is:internal` | [**is:internal test**](https://github.com/search?q=is%3Ainternal+test&type=Repositories) 匹配您可以访问且包含文字 "test" 的内部仓库。 | `is:private` | [**is:private pages**](https://github.com/search?q=is%3Aprivate+pages&type=Repositories) 匹配您可以访问并且包含单词 "pages" 的私有仓库。 + +{% ifversion fpt %} + +## 基于仓库是否为镜像搜索 + +您可以根据仓库是否为镜像以及托管于其他位置托管来搜索仓库。 更多信息请参阅“[寻找在 {% data variables.product.prodname_dotcom %} 上参与开源项目的方法](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)”。 + +| 限定符 | 示例 | +| -------------- | ------------------------------------------------------------------------------------------------------------------------ | +| `mirror:true` | [**mirror:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Atrue+GNOME&type=) 匹配是镜像且包含 "GNOME" 字样的仓库。 | +| `mirror:false` | [**mirror:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Afalse+GNOME&type=) 匹配并非镜像且包含 "GNOME" 字样的仓库。 | + +{% endif %} + +## 基于仓库是否已存档搜索 + +您可以基于仓库是否已存档来搜索仓库。 For more information, see "[Archiving repositories](/repositories/archiving-a-github-repository/archiving-repositories)." + +| 限定符 | 示例 | +| ---------------- | --------------------------------------------------------------------------------------------------------------------------- | +| `archived:true` | [**archived:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Atrue+GNOME&type=) 匹配已存档且包含 "GNOME" 字样的仓库。 | +| `archived:false` | [**archived:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Afalse+GNOME&type=) 匹配未存档且包含 "GNOME" 字样的仓库。 | + +{% ifversion fpt %} + +## 基于具有 `good first issue` 或 `help wanted` 标签的议题数量搜索 + +您可以使用限定符 `help-wanted-issues:>n` 和 `good-first-issues:>n` 搜索具有最少数量标签为 `help-wanted` 或 `good-first-issue` 议题的仓库。 更多信息请参阅“[通过标签鼓励对项目做出有益的贡献](/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels)”。 + +| 限定符 | 示例 | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `good-first-issues:>n` | [**good-first-issues:>2 javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+good-first-issues%3A%3E2&type=) 匹配具有超过两个标签为 `good-first-issue` 的议题且包含 "javascript" 字样的仓库。 | +| `help-wanted-issues:>n` | [**help-wanted-issues:>4 react**](https://github.com/search?utf8=%E2%9C%93&q=react+help-wanted-issues%3A%3E4&type=) 匹配具有超过四个标签为 `help-wanted` 的议题且包含 "React" 字样的仓库。 | + +## Search based on ability to sponsor + +You can search for repositories whose owners can be sponsored on {% data variables.product.prodname_sponsors %} with the `is:sponsorable` qualifier. 更多信息请参阅“[关于 {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)”。 + +You can search for repositories that have a funding file using the `has:funding-file` qualifier. For more information, see "[About FUNDING files](/github/administering-a-repository/managing-repository-settings/displaying-a-sponsor-button-in-your-repository#about-funding-files)." + +| 限定符 | 示例 | +| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `is:sponsorable` | [**is:sponsorable**](https://github.com/search?q=is%3Asponsorable&type=Repositories) matches repositories whose owners have a {% data variables.product.prodname_sponsors %} profile. | +| `has:funding-file` | [**has:funding-file**](https://github.com/search?q=has%3Afunding-file&type=Repositories) matches repositories that have a FUNDING.yml file. | + +{% endif %} + +## 延伸阅读 + +- “[排序搜索结果](/search-github/getting-started-with-searching-on-github/sorting-search-results/)” +- “[在复刻中搜索](/search-github/searching-on-github/searching-in-forks)” diff --git a/translations/zh-CN/content/search-github/searching-on-github/searching-github-marketplace.md b/translations/zh-CN/content/search-github/searching-on-github/searching-github-marketplace.md new file mode 100644 index 0000000000..6e7518deb8 --- /dev/null +++ b/translations/zh-CN/content/search-github/searching-on-github/searching-github-marketplace.md @@ -0,0 +1,38 @@ +--- +title: 搜索 GitHub Marketplace +intro: '您可以搜索 {% data variables.product.prodname_marketplace %} 上可用的应用程序和操作。' +versions: + fpt: '*' +topics: + - GitHub search +redirect_from: + - /github/searching-for-information-on-github/searching-github-marketplace + - /github/searching-for-information-on-github/searching-on-github/searching-github-marketplace +shortTitle: 搜索 GitHub Marketplace +--- + +## 关于搜索 {% data variables.product.prodname_marketplace %} + +您可以通过以下两种方式在 {% data variables.product.prodname_marketplace %} 上查找应用程序和操作： + +- 在 {% data variables.product.prodname_marketplace %} 中搜索。 +- 在所有 {% data variables.product.prodname_dotcom_the_website %} 上搜索，然后过滤结果。 + +## 在 {% data variables.product.prodname_marketplace %} 中搜索 + +1. 在任一页面顶部，单击 **Marketplace**。 ![Marketplace 链接](/assets/images/help/search/marketplace-link.png) +2. 输入任何关键字，然后按 **Enter**。 ![搜索 {% data variables.product.prodname_marketplace %} 上的语法检查](/assets/images/help/search/marketplace-apps-and-actions-search-field.png) +3. （可选）通过单击左边栏中的一个或多个选项来过滤结果。 + +## 在 {% data variables.product.prodname_dotcom_the_website %} 上搜索 + +每次在所有 {% data variables.product.prodname_dotcom_the_website %} 上搜索时，都可以过滤结果以查看 {% data variables.product.prodname_marketplace %} 中匹配的应用程序和操作。 + +1. 导航到 https://github.com/search。 +2. 输入任何关键字，然后按 **Enter**。 ![搜索字段](/assets/images/help/search/search-field.png) +3. 在左边栏中，单击 **Marketplace**。 ![Marketplace 侧菜单选项突出显示的语法检查搜索结果](/assets/images/help/search/marketplace-left-side-navigation.png) + +## 延伸阅读 + +- "[关于 {% data variables.product.prodname_marketplace %}](/github/customizing-your-github-workflow/about-github-marketplace)" +- “[在工作流程中使用 {% data variables.product.prodname_marketplace %} 中的操作](/actions/automating-your-workflow-with-github-actions/using-actions-from-github-marketplace-in-your-workflow)” diff --git a/translations/zh-CN/content/search-github/searching-on-github/searching-in-forks.md b/translations/zh-CN/content/search-github/searching-on-github/searching-in-forks.md new file mode 100644 index 0000000000..11849bda46 --- /dev/null +++ b/translations/zh-CN/content/search-github/searching-on-github/searching-in-forks.md @@ -0,0 +1,32 @@ +--- +title: 在复刻中搜索 +intro: '默认情况下，[forks](/articles/about-forks) 不会在搜索结果中显示。 如果复刻满足特定条件，您可以选择在仓库搜索以及在代码搜索中包括它们。' +redirect_from: + - /articles/searching-in-forks + - /github/searching-for-information-on-github/searching-in-forks + - /github/searching-for-information-on-github/searching-on-github/searching-in-forks +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +要在[仓库搜索](/search-github/searching-on-github/searching-for-repositories)结果中显示复刻，请将 `fork:true` 或 `fork:only` 添加到查询。 + +仅当复刻具有比父仓库更多的星号时，才会为[代码搜索](/search-github/searching-on-github/searching-code)编索引。 您无法在比父项具有更少星号的复刻中搜索代码。 要在代码搜索结果中显示比父仓库具有更多星号的复刻，请将 `fork:true` 或 `fork:only` 添加到查询。 + +`fork:true` 限定符查找匹配搜索查询的所有结果，包括复刻。 `fork:only` 限定符_仅_查找匹配搜索查询的复刻。 + +| 限定符 | 示例 | +| ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `fork:true` | [**github fork:true**](https://github.com/search?q=github+fork%3Atrue&type=Repositories) 匹配包含 "github" 字样的所有仓库，包括复刻。 | +| | [**android language:java fork:true**](https://github.com/search?q=android+language%3Ajava+fork%3Atrue&type=Code) 匹配复刻和普通仓库中包含 "android" 字样、以 Java 编写的代码。 | +| `fork:only` | [**github fork:only**](https://github.com/search?q=github+fork%3Aonly&type=Repositories) 匹配包含 "github" 字样的所有复刻仓库。 | +| | [**forks:>500 fork:only**](https://github.com/search?q=forks%3A%3E500+fork%3Aonly&type=Repositories) 匹配具有超过 500 个复刻的仓库，并且只返回作为复刻的仓库。 | + +## 延伸阅读 + +- "[关于复刻](/articles/about-forks)" +- “[关于在 GitHub 上搜索](/search-github/getting-started-with-searching-on-github/about-searching-on-github)” 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 new file mode 100644 index 0000000000..031ddd37bd --- /dev/null +++ b/translations/zh-CN/content/search-github/searching-on-github/searching-issues-and-pull-requests.md @@ -0,0 +1,343 @@ +--- +title: 搜索议题和拉取请求 +intro: '您可以在 {% data variables.product.product_name %} 上搜索代码，并使用这些代码搜索限定符的任意组合缩小结果范围。' +redirect_from: + - /articles/searching-issues/ + - /articles/searching-issues-and-pull-requests + - /github/searching-for-information-on-github/searching-issues-and-pull-requests + - /github/searching-for-information-on-github/searching-on-github/searching-issues-and-pull-requests +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +shortTitle: 搜索议题和 PR +--- + +您可以在所有 {% data variables.product.product_name %} 内全局搜索议题和拉取请求，也可以在特定组织内搜索议题和拉取请求。 更多信息请参阅“[关于在 {% data variables.product.company_short %} 上搜索](/search-github/getting-started-with-searching-on-github/about-searching-on-github)”。 + +{% tip %} + +**提示：**{% ifversion ghes or ghae %} + - 本文章包含在 {% data variables.product.prodname_dotcom %}.com 网站上的示例搜索，但您可以在 {% data variables.product.product_location %} 上使用相同的搜索过滤器。{% endif %} + - 有关可以添加到任何搜索限定符以进一步改善结果的搜索语法列表，请参阅“[了解搜索语法](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)”。 + - 对多个字词的搜索词使用引号。 例如，如果要搜索具有标签 "In progress" 的议题，可搜索 `label:"in progress"`。 搜索不区分大小写。 + - {% data reusables.search.search_issues_and_pull_requests_shortcut %} + + {% endtip %} + +## 仅搜索议题或拉取请求 + +默认情况下，{% data variables.product.product_name %} 搜索将返回议题和拉取请求。 但您可以使用 `type` 或 `is` 限定符将搜索结果限制为仅议题或拉取请求。 + +| 限定符 | 示例 | +| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `type:pr` | [**cat type:pr**](https://github.com/search?q=cat+type%3Apr&type=Issues) 匹配含有 "cat" 字样的拉取请求。 | +| `type:issue` | [**github commenter:defunkt type:issue**](https://github.com/search?q=github+commenter%3Adefunkt+type%3Aissue&type=Issues) 匹配含有 "github" 字样且由 @defunkt 评论的议题。 | +| `is:pr` | [**event is:pr**](https://github.com/search?utf8=%E2%9C%93&q=event+is%3Apr&type=) 匹配含有 "event" 字样的拉取请求。 | +| `is:issue` | [**is:issue label:bug is:closed**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aissue+label%3Abug+is%3Aclosed&type=) 匹配具有标签 "bug" 的已关闭议题。 | + +## 按标题、正文或评论搜索 + +通过 `in` 限定符，您可以将搜索限制为标题、正文、评论或这些的任意组合。 如果省略此限定符，则标题、正文和评论全部搜索。 + +| 限定符 | 示例 | +| ------------- | ------------------------------------------------------------------------------------------------------------------- | +| `in:title` | [**warning in:title**](https://github.com/search?q=warning+in%3Atitle&type=Issues) 匹配其标题中含有 "warning" 的议题。 | +| `in:body` | [**error in:title,body**](https://github.com/search?q=error+in%3Atitle%2Cbody&type=Issues) 匹配其标题或正文中含有 "error" 的议题。 | +| `in:comments` | [**shipit in:comments**](https://github.com/search?q=shipit+in%3Acomment&type=Issues) 匹配其评论中提及 "shipit" 的议题。 | + +## 在用户或组织的仓库内搜索 + +要在特定用户或组织拥有的所有仓库中搜索议题和拉取请求，您可以使用 `user` 或 `org` 限定符。 要在特定仓库中搜索议题和拉取请求，您可以使用 `repo` 限定符。 + +{% 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` 限定符基于议题和拉取请求处于打开还是关闭状态进行过滤。 + +| 限定符 | 示例 | +| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `state:open` | [**libraries state:open mentions:vmg**](https://github.com/search?utf8=%E2%9C%93&q=libraries+state%3Aopen+mentions%3Avmg&type=Issues) 匹配提及 @vmg 且含有 "libraries" 字样的开放议题。 | +| `state:closed` | [**design state:closed in:body**](https://github.com/search?utf8=%E2%9C%93&q=design+state%3Aclosed+in%3Abody&type=Issues) 匹配正文中含有 "design" 字样的已关闭议题。 | +| `is:open` | [**performance is:open is:issue**](https://github.com/search?q=performance+is%3Aopen+is%3Aissue&type=Issues) 匹配含有 "performance" 字样的开放议题。 | +| `is:closed` | [**android is:closed**](https://github.com/search?utf8=%E2%9C%93&q=android+is%3Aclosed&type=) 匹配含有 "android" 字样的已关闭议题和拉取请求。 | + +## 按仓库可见性过滤 + +您可以使用 `is` 限定符，按包含议题和拉取请求的仓库的可见性进行过滤。 更多信息请参阅“[关于仓库](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)”。 + +| 限定符 | 示例 | ------------- | ------------- |{% ifversion fpt or ghes %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Issues) 匹配公共仓库中的议题和拉取请求。{% endif %}{% ifversion fpt or ghes or ghae %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Issues) 匹配内部仓库中的议题和拉取请求。{% endif %} | `is:private` | [**is:private cupcake**](https://github.com/search?q=is%3Aprivate+cupcake&type=Issues) 匹配您可以访问的仓库中包含单词 "cupcake" 的议题和拉取请求。 + +## 按作者搜索 + +`author` 限定符查找由特定用户或集成帐户创建的议题和拉取请求。 + +| 限定符 | 示例 | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | +| author:USERNAME | [**cool author:gjtorikian**](https://github.com/search?q=cool+author%3Agjtorikian&type=Issues) 匹配含有 "cool" 字样、由 @gjtorikian 创建的议题和拉取请求。 | +| | [**bootstrap in:body author:mdo**](https://github.com/search?q=bootstrap+in%3Abody+author%3Amdo&type=Issues) 匹配由 @mdo 撰写、正文中含有 "bootstrap" 字样的议题。 | +| author:app/USERNAME | [**author:app/robot**](https://github.com/search?q=author%3Aapp%2Frobot&type=Issues) 匹配由名为 "robot" 的集成帐户创建的议题。 | + +## 按受理人搜索 + +`assignee` 限定符查找分配给特定用户的议题和拉取请求。 您无法搜索具有 _any_ 受理人的议题和拉取请求，但可以搜索[没有受理人的议题和拉取请求](#search-by-missing-metadata)。 + +| 限定符 | 示例 | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| assignee:USERNAME | [**assignee:vmg repo:libgit2/libgit2**](https://github.com/search?utf8=%E2%9C%93&q=assignee%3Avmg+repo%3Alibgit2%2Flibgit2&type=Issues) 匹配分配给 @vmg 的 libgit2 项目 libgit2 中的议题和拉取请求。 | + +## 按提及搜索 + +`mentions` 限定符查找提及特定用户的议题。 更多信息请参阅“[提及人员和团队](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)”。 + +| 限定符 | 示例 | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | +| mentions:USERNAME | [**resque mentions:defunkt**](https://github.com/search?q=resque+mentions%3Adefunkt&type=Issues) 匹配含有 "resque" 字样、提及 @defunkt 的议题。 | + +## 按团队提及搜索 + +对于您所属的组织和团队，您可以使用 `team` 限定符查找提及该组织内特定团队的议题或拉取请求。 将这些示例名称替换为您的组织和团队的名称以执行搜索。 + +| 限定符 | 示例 | +| ------------------------- | ------------------------------------------------------------- | +| team:ORGNAME/TEAMNAME | **team:jekyll/owners** 匹配提及 `@jekyll/owners` 团队的议题。 | +| | **team:myorg/ops is:open is:pr** 匹配提及 `@myorg/ops` 团队的打开拉取请求。 | + +## 按评论者搜索 + +`commenter` 限定符查找含有来自特定用户评论的议题。 + +| 限定符 | 示例 | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| commenter:USERNAME | [**github commenter:defunkt org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Adefunkt+org%3Agithub&type=Issues) 匹配位于 GitHub 拥有的仓库中、含有 "github" 字样且由 @defunkt 评论的议题。 | + +## 按议题或拉取请求中涉及的用户搜索 + +您可以使用 `involves` 限定符查找以某种方式涉及特定用户的议题。 `involves` 限定符是单一用户 `author`、`assignee`、`mentions` 和 `commenter` 限定符之间的逻辑 OR（或）。 换句话说，此限定符查找由特定用户创建、分配给该用户、提及该用户或由该用户评论的议题和拉取请求。 + +| 限定符 | 示例 | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 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 %} +## 搜索链接的议题和拉取请求 +您可以将结果缩小到仅包括通过关闭引用链接到拉取请求的议题，或者链接到拉取请求可能关闭的议题的拉取请求。 + +| 限定符 | 示例 | +| --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `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 %} + +## 按标签搜索 + +您可以使用 `label` 限定符按标签缩小结果范围。 由于议题可有多个标签，因此您可为每个议题列出单独的限定符。 + +| 限定符 | 示例 | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| label:LABEL | [**label:"help wanted" language:ruby**](https://github.com/search?utf8=%E2%9C%93&q=label%3A%22help+wanted%22+language%3Aruby&type=Issues) 匹配标签为 "help wanted"、位于 Ruby 仓库中的议题。 | +| | [**broken in:body -label:bug label:priority**](https://github.com/search?q=broken+in%3Abody+-label%3Abug+label%3Apriority&type=Issues) 匹配正文中含有 "broken" 字样、没有 "bug" 标签但*有* "priority" 标签的议题。 | +| | [**label:bug label:resolved**](https://github.com/search?l=&q=label%3Abug+label%3Aresolved&type=Issues) matches issues with the labels "bug" and "resolved."{% ifversion fpt or ghes > 3.2 or ghae-next %} +| | [**label:bug,resolved**](https://github.com/search?q=label%3Abug%2Cresolved&type=Issues) matches issues with the label "bug" or the label "resolved."{% endif %} + +## 按里程碑搜索 + +`milestone` 限定符查找作为仓库内[里程碑](/articles/about-milestones)组成部分的议题或拉取请求。 + +| 限定符 | 示例 | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | +| milestone:MILESTONE | [**milestone:"overhaul"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22overhaul%22&type=Issues) 匹配位于名为 "overhaul" 的里程碑中的议题。 | +| | [**milestone:"bug fix"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22bug+fix%22&type=Issues) 匹配位于名为 "bug fix" 的里程碑中的议题。 | + +## 按项目板搜索 + +您可以使用 `project` 限定符查找与仓库或组织中特定[项目板](/articles/about-project-boards/)关联的议题。 必须按项目板编号搜索项目板。 您可在项目板 URL 的末尾找到项目板编号。 + +| 限定符 | 示例 | +| -------------------------- | --------------------------------------------------------------------- | +| project:PROJECT_BOARD | **project:github/57** 匹配 GitHub 拥有的、与组织项目板 57 关联的议题。 | +| project:REPOSITORY/PROJECT_BOARD | **project:github/linguist/1** 匹配与 @github 的 linguist 仓库中的项目板 1 关联的议题。 | + +## 按提交状态搜索 + +您可以基于提交的状态过滤拉取请求。 这在使用 [Status API](/rest/reference/repos#statuses) 或 CI 服务时特别有用。 + +| 限定符 | 示例 | +| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `status:pending` | [**language:go status:pending**](https://github.com/search?utf8=%E2%9C%93&q=language%3Ago+status%3Apending) 匹配在状态为待定的 Go 仓库中打开的拉取请求。 | +| `status:success` | [**is:open status:success finally in:body**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aopen+status%3Asuccess+finally+in%3Abody&type=Issues) 匹配正文中含有 "finally" 字样、具有成功状态的打开拉取请求。 | +| `status:failure` | [**created:2015-05-01..2015-05-30 status:failure**](https://github.com/search?utf8=%E2%9C%93&q=created%3A2015-05-01..2015-05-30+status%3Afailure&type=Issues) 匹配在 2015 年 5 月打开、具有失败状态的拉取请求。 | + +## 按提交 SHA 搜索 + +如果您知道提交的特定 SHA 哈希，您可以使用它来搜索包含该 SHA 的拉取请求。 SHA 语法必须至少 7 个字符。 + +| 限定符 | 示例 | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | +| SHA | [**e1109ab**](https://github.com/search?q=e1109ab&type=Issues) 匹配具有开头为 `e1109ab` 的提交 SHA 的拉取请求。 | +| | [**0eff326d6213c is:merged**](https://github.com/search?q=0eff326d+is%3Amerged&type=Issues) 匹配具有开头为 `0eff326d6213c` 的提交 SHA 的合并拉取请求。 | + +## 按分支名称搜索 + +您可以基于拉取请求来自的分支（"head" 分支）或其合并到的分支（"base" 分支）来过滤拉取请求。 + +| 限定符 | 示例 | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| head:HEAD_BRANCH | [**head:change is:closed is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=head%3Achange+is%3Aclosed+is%3Aunmerged) 匹配从名称以 "change" 字样开头的已关闭分支打开的拉取请求。 | +| base:BASE_BRANCH | [**base:gh-pages**](https://github.com/search?utf8=%E2%9C%93&q=base%3Agh-pages) 匹配合并到 `gh-pages` 分支中的拉取请求。 | + +## 按语言搜索 + +通过 `language` 限定符，您可以搜索以特定语言编写的仓库内的议题和拉取请求。 + +| 限定符 | 示例 | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------- | +| language:LANGUAGE | [**language:ruby state:open**](https://github.com/search?q=language%3Aruby+state%3Aopen&type=Issues) 匹配 Ruby 仓库中的开放议题。 | + +## 按评论数量搜索 + +您可以使用 `comments` 限定符以及[大于、小于和范围限定符](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)以按评论数量搜索。 + +| 限定符 | 示例 | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | +| comments:n | [**state:closed comments:>100**](https://github.com/search?q=state%3Aclosed+comments%3A%3E100&type=Issues) 匹配具有超过 100 条评论的已关闭议题。 | +| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Issues) 匹配具有 500 到 1,000 条评论的议题。 | + +## 按交互数量搜索 + +您可以使用 `interactions` 限定符以及[大于、小于和范围限定符](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)按交互数量过滤议题和拉取请求。 交互数量是对议题或拉取请求的反应和评论数量。 + +| 限定符 | 示例 | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------- | +| interactions:n | [** interactions:>2000**](https://github.com/search?q=interactions%3A%3E2000) 匹配超过 2000 个交互的拉取请求或议题。 | +| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) 匹配 500 至 1,000 个交互的拉取请求或议题。 | + +## 按反应数量搜索 + +您可以使用 `reactions` 限定符以及 [大于、小于和范围限定符](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)按反应数量过滤议题和拉取请求。 + +| 限定符 | 示例 | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------ | +| reactions:n | [** reactions:>1000**](https://github.com/search?q=reactions%3A%3E1000&type=Issues) 匹配超过 1000 个反应的议题。 | +| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) 匹配 500 至 1000 个反应的议题。 | + +## 搜索草稿拉取请求 +您可以过滤草稿拉取请求。 更多信息请参阅“[关于拉取请求](/articles/about-pull-requests#draft-pull-requests)”。 + +| 限定符 | 示例 | ------------- | -------------{% ifversion fpt or ghes or ghae %} | `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 %} + +## 按拉取请求审查状态和审查者搜索 + +您可以基于拉取请求的[审查状态](/articles/about-pull-request-reviews)（_无_、_必需_、_批准_或_请求更改_）、按审查者和请求的审查者过滤拉取请求。 + +| 限定符 | 示例 | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `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 or ghes > 3.2 %} +| 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) 匹配已审查团队 `atom/design` 请求的拉取请求。 申请的审查者在其审查拉取请求后不再在搜索结果中列出。 | + +## 按议题或拉取请求创建或上次更新的时间搜索 + +您可以基于创建时间或上次更新时间过滤议题。 对于议题创建，您可以使用 `created` 限定符；要了解议题上次更新的时间，您要使用 `updated` 限定符。 + +两者均采用日期作为参数。 {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| 限定符 | 示例 | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| created:YYYY-MM-DD | [**language:c# created:<2011-01-01 state:open**](https://github.com/search?q=language%3Ac%23+created%3A%3C2011-01-01+state%3Aopen&type=Issues) 匹配以 C# 编写的仓库中 2011 年以前创建的开放议题。 | +| updated:YYYY-MM-DD | [**weird in:body updated:>=2013-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2013-02-01&type=Issues) 匹配 2013 年 2 月后更新的、正文中含有 "weird" 字样的议题。 | + +## 按议题或拉取请求关闭的时间搜索 + +您可以使用 `closed` 限定符基于议题和拉取请求关闭的时间进行过滤。 + +此限定符采用日期作为其参数。 {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| 限定符 | 示例 | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| closed:YYYY-MM-DD | [**language:swift closed:>2014-06-11**](https://github.com/search?q=language%3Aswift+closed%3A%3E2014-06-11&type=Issues) 匹配 2014 年 6 月 11 日后关闭的 Swift 中的议题和拉取请求。 | +| | [**data in:body closed:<2012-10-01**](https://github.com/search?utf8=%E2%9C%93&q=data+in%3Abody+closed%3A%3C2012-10-01+&type=Issues) 匹配 2012 年 10 月后关闭、正文中含有 "data" 字样的议题和拉取请求。 | + +## 按拉取请求合并的时间搜索 + +您可以使用 `merged` 限定符基于拉取请求合并的时间进行过滤。 + +此限定符采用日期作为其参数。 {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| 限定符 | 示例 | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| merged:YYYY-MM-DD | [**language:javascript merged:<2011-01-01**](https://github.com/search?q=language%3Ajavascript+merged%3A%3C2011-01-01+&type=Issues) 匹配 2011 年以前合并的 JavaScript 仓库中的拉取请求。 | +| | [**fast in:title language:ruby merged:>=2014-05-01**](https://github.com/search?q=fast+in%3Atitle+language%3Aruby+merged%3A%3E%3D2014-05-01+&type=Issues) 匹配 2014 年 5 月之后合并、标题中含有 "fast" 字样、以 Ruby 编写的拉取请求。 | + +## 基于拉取请求是否已合并搜索 + +您可以使用 `is` 限定符基于拉取请求已合并还是未合并进行过滤。 + +| 限定符 | 示例 | +| ------------- | ----------------------------------------------------------------------------------------------------------------------------------- | +| `is:merged` | [**bugfix is:pr is:merged**](https://github.com/search?utf8=%E2%9C%93&q=bugfix+is%3Apr+is%3Amerged&type=) 匹配含有 "bugfix" 字样的已合并拉取请求。 | +| `is:unmerged` | [**error is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=error+is%3Aunmerged&type=) 匹配含有 "error" 字样的已关闭议题和拉取请求。 | + +## 基于仓库是否已存档搜索 + +`archived` 限定符基于议题或拉取请求是否位于已存档仓库中过滤结果。 + +| 限定符 | 示例 | +| ---------------- | --------------------------------------------------------------------------------------------------------------------------- | +| `archived:true` | [**archived:true GNOME**](https://github.com/search?q=archived%3Atrue+GNOME&type=) 匹配您具有访问权限的已存档仓库中含有 "GNOME" 字样的议题和拉取请求。 | +| `archived:false` | [**archived:false GNOME**](https://github.com/search?q=archived%3Afalse+GNOME&type=) 匹配您具有访问权限的未存档仓库中含有 "GNOME" 字样的议题和拉取请求。 | + +## 基于对话是否已锁定搜索 + +您可以使用 `is` 限定符搜索具有已锁定对话的议题或拉取请求。 更多信息请参阅“[锁定对话](/communities/moderating-comments-and-conversations/locking-conversations)”。 + +| 限定符 | 示例 | +| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `is:locked` | [**code of conduct is:locked is:issue archived:false**](https://github.com/search?q=code+of+conduct+is%3Alocked+is%3Aissue+archived%3Afalse) 匹配未存档仓库中具有已锁定对话且含有 "code of conduct" 字样的议题或拉取请求。 | +| `is:unlocked` | [**code of conduct is:unlocked is:issue archived:false**](https://github.com/search?q=code+of+conduct+is%3Aunlocked+archived%3Afalse) 匹配未存档仓库中具有未锁定对话且含有 "code of conduct" 字样的议题或拉取请求。 | + +## 按缺少的元数据搜索 + +您可以使用 `no` 限定符缩小搜索缺少特定元数据的议题和拉取请求的范围。 该元数据包括： + +* 标签 +* 里程碑 +* 受理人 +* 项目 + +| 限定符 | 示例 | +| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `no:label` | [**priority no:label**](https://github.com/search?q=priority+no%3Alabel&type=Issues) 匹配没有任何标签且含有 "priority" 字样的议题和拉取请求。 | +| `no:milestone` | [**sprint no:milestone type:issue**](https://github.com/search?q=sprint+no%3Amilestone+type%3Aissue&type=Issues) 匹配未与含有 "sprint" 字样的里程碑关联的议题。 | +| `no:assignee` | [**important no:assignee language:java type:issue**](https://github.com/search?q=important+no%3Aassignee+language%3Ajava+type%3Aissue&type=Issues) 匹配未与受理人关联、含有 "important" 字样且位于 Java 仓库中的议题。 | +| `no:project` | [**build no:project**](https://github.com/search?utf8=%E2%9C%93&q=build+no%3Aproject&type=Issues) 匹配未与项目板关联、含有 "build" 字样的议题。 | + +## 延伸阅读 + +- “[排序搜索结果](/search-github/getting-started-with-searching-on-github/sorting-search-results/)” diff --git a/translations/zh-CN/content/search-github/searching-on-github/searching-topics.md b/translations/zh-CN/content/search-github/searching-on-github/searching-topics.md new file mode 100644 index 0000000000..e2221b8398 --- /dev/null +++ b/translations/zh-CN/content/search-github/searching-on-github/searching-topics.md @@ -0,0 +1,55 @@ +--- +title: 搜索主题 +intro: '您可以在 {% data variables.product.product_name %} 上搜索与仓库关联的主题。' +redirect_from: + - /articles/searching-topics + - /github/searching-for-information-on-github/searching-topics + - /github/searching-for-information-on-github/searching-on-github/searching-topics +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +## 搜索 {% data variables.product.product_name %} 主题 + +您可以在 {% data variables.product.product_name %} 上搜索主题、探索相关主题以及查看有多少仓库与特定主题关联。 + +1. 导航到 https://github.com/search。 +2. 输入主题关键词。 ![搜索字段](/assets/images/help/search/search-field.png) +3. 在左侧边栏中，要将搜索范围缩小到主题，请单击 **Topics（主题）**。 +{% ifversion fpt %} + ![主题侧菜单选项突出显示的 Jekyll 仓库搜索结果页面](/assets/images/help/search/topic-left-side-navigation-dotcom.png){% else %} +![Jekyll repository search results page on dotcom with topics side-menu option highlighted](/assets/images/help/search/topic-left-side-navigation.png){% endif %} + +## 使用搜索限定符缩小搜索范围 + +如果您要探索关于特定主题的仓库、查找要贡献内容的项目或了解哪些主题在 {% data variables.product.product_name %} 上最受欢迎，您可以使用搜索限定符 `is:featured`、`is:curated`、`repositories:n` 和 `created:YYYY-MM-DD` 搜索主题。 + +`is:featured` 搜索限定符会将搜索结果范围缩小为 {% data variables.product.product_name %} 上具有最多仓库的主题。 这些主题还会在 https://github.com/topics/ 上提供。 + +`is:curated` 搜索限定符可将搜索结果范围缩小到社区成员已向其添加额外信息的主题。 更多信息请参阅[探索仓库](https://github.com/github/explore)。 + +您可以使用日期参数和 `created:` 根据创建时间过滤主题，也可以使用 `repositories:n` 根据与此主题关联的仓库数量过滤主题。 这两个限定符都可以使用[大于和小于范围限定符](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)。 + +{% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| 限定符 | 示例 | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `is:curated` | [**is:curated javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+is%3Acurated&type=Topics) 匹配精心策划且含有 "javascript" 字样的主题。 | +| `is:featured` | [**is:featured javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+is%3Afeatured&type=Topics) 匹配 https://github.com/topics/ 上提供且含有 "javascript" 字样的主题。 | +| `is:not-curated` | [**is:not-curated javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+is%3Anot-curated&type=Topics) 匹配没有额外信息（例如说明或徽标）且含有 "javascript" 字样的主题。 | +| `is:not-featured` | [**is:not-featured javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+is%3Anot-featured&type=Topics) 匹配 https://github.com/topics/ 上未提供且含有 "javascript" 字样的主题。 | +| `repositories:n` | [**repositories:>5000**](https://github.com/search?q=repositories%3A%3E5000) 匹配超过 5000 个仓库的主题。 | +| created:YYYY-MM-DD | [**Serverless created:>2019-01-01**](https://github.com/search?q=Serverless+created%3A%3E2019-01-01&type=Topics) 匹配含有 "serverless" 字样、在 2018 年之后创建的主题。 | + +## 按主题搜索仓库 + +您可以使用 `topic:` 限定符查找连接到特定主题的每个仓库。 更多信息请参阅“[搜索仓库](/search-github/searching-on-github/searching-for-repositories/#search-by-topic)”。 + +## 延伸阅读 +- "[使用主题对仓库分类](/articles/classifying-your-repository-with-topics)" diff --git a/translations/zh-CN/content/search-github/searching-on-github/searching-users.md b/translations/zh-CN/content/search-github/searching-on-github/searching-users.md new file mode 100644 index 0000000000..e4733257eb --- /dev/null +++ b/translations/zh-CN/content/search-github/searching-on-github/searching-users.md @@ -0,0 +1,106 @@ +--- +title: 搜索用户 +intro: '您可以在 {% data variables.product.product_name %} 上搜索用户，并使用这些用户搜索限定符的任意组合缩小结果范围。' +redirect_from: + - /articles/searching-users + - /github/searching-for-information-on-github/searching-users + - /github/searching-for-information-on-github/searching-on-github/searching-users +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +您可以在所有 {% data variables.product.product_name %} 内全局搜索用户。 更多信息请参阅“[关于在 {% data variables.product.company_short %} 上搜索](/search-github/getting-started-with-searching-on-github/about-searching-on-github)”。 + +{% data reusables.search.syntax_tips %} + +## 仅搜索用户或组织 + +默认情况下，搜索用户将同时返回个人和组织。 不过，您可以使用 `type` 限定符将搜索结果限制为仅个人帐户或组织。 + +| 限定符 | 示例 | +| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `type:user` | [**mike in:name created:<2011-01-01 type:user**](https://github.com/search?q=mike+in:name+created%3A%3C2011-01-01+type%3Auser&type=Users) 匹配 2011 年之前创建、名为 "mike" 的个人帐户。 | +| `type:org` | [**data in:email type:org**](https://github.com/search?q=data+in%3Aemail+type%3Aorg&type=Users) 匹配其电子邮件中含有 "data" 字样的组织。 | + +## 按帐户名、全名或公共电子邮件搜索 + +您可以使用 `user` 或 `org` 限定符根据个人用户或组织帐户的名称过滤搜索。 + +通过 `in` 限定符，您可以将搜索限制为用户名 (`login`)、全名、公共电子邮件或这些的任意组合。 如果省略此限定符，则只搜索用户名和电子邮件地址。 出于隐私原因，您无法按电子邮件域名搜索。 + +| 限定符 | 示例 | +| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | +| `user:name` | [**user:octocat**](https://github.com/search?q=user%3Aoctocat&type=Users) 匹配用户名为 "octocat" 的用户。 | +| `org:name` | [**org:electron type:users**](https://github.com/search?q=org%3Aelectron+type%3Ausers&type=Users) 匹配 Electron 组织的帐户名。 | +| `in:login` | [**kenya in:login**](https://github.com/search?q=kenya+in%3Alogin&type=Users) 匹配其用户名中含 "kenya" 字样的用户。 | +| `in:name` | [**bolton in:name**](https://github.com/search?q=bolton+in%3Afullname&type=Users) 匹配其真实姓名含有 "bolton" 字样的用户。 | +| `fullname:firstname lastname` | [**fullname:nat friedman**](https://github.com/search?q=fullname%3Anat+friedman&type=Users) 匹配全名为 "Nat Friedman" 的用户。 注：此搜索限定符区分空格。 | +| `in:email` | [**data in:email**](https://github.com/search?q=data+in%3Aemail&type=Users&utf8=%E2%9C%93) 匹配其电子邮件中含有 "data" 字样的用户。 | + +## 按用户拥有的仓库数量搜索 + +您可以使用 `repos` 限定符以及[大于、小于和范围限定符](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)基于用户拥有的仓库数量过滤用户。 + +| 限定符 | 示例 | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------ | +| repos:n | [**repos:>9000**](https://github.com/search?q=repos%3A%3E%3D9000&type=Users) 匹配其仓库数超过 9,000 的用户。 | +| | [**bert repos:10..30**](https://github.com/search?q=bert+repos%3A10..30&type=Users) 匹配拥有 10 到 30 个仓库、其用户名或真实姓名含有 "bert" 字样的用户。 | + +## 按位置搜索 + +您可以按其个人资料中指示的位置搜索用户。 + +| 限定符 | 示例 | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------- | +| location:LOCATION | [**repos:1 location:iceland**](https://github.com/search?q=repos%3A1+location%3Aiceland&type=Users) 匹配恰好有一个仓库位于冰岛的用户。 | + +## 按仓库语言搜索 + +使用 `language` 限定符，您可以基于用户所拥有仓库的语言搜索用户。 + +| 限定符 | 示例 | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| language:LANGUAGE | [**language:javascript location:russia**](https://github.com/search?q=language%3Ajavascript+location%3Arussia&type=Users) 匹配其大多数仓库均以 JavaScript 编写的俄罗斯用户。 | +| | [**jenny language:javascript in:fullname**](https://github.com/search?q=jenny+language%3Ajavascript+in%3Afullname&type=Users) 匹配其全名含有 "jenny" 字样、具有 JavaScript 仓库的用户。 | + +## 按用户帐户创建时间搜索 + +您可以使用 `created` 限定符基于用户加入 {% data variables.product.product_name %} 的时间过滤用户。 这将采用日期作为其参数。 {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} + +{% data reusables.search.date_gt_lt %} + +| 限定符 | 示例 | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| created:YYYY-MM-DD | [**created:<2011-01-01**](https://github.com/search?q=created%3A%3C2011-01-01&type=Users) 匹配在 2011 年之前加入的用户。 | +| | [**created:>=2013-05-11**](https://github.com/search?q=created%3A%3E%3D2013-05-11&type=Users) 匹配在 2013 年 5 月 11 日或之后加入的用户。 | +| | [**created:2013-03-06 location:london**](https://github.com/search?q=created%3A2013-03-06+location%3Alondon&type=Users) 匹配 2013 年 3 月 6 日加入、其位置列为伦敦的用户。 | +| | [**created:2010-01-01..2011-01-01 john in:login**](https://github.com/search?q=created%3A2010-01-01..2011-01-01+john+in%3Ausername&type=Users) 匹配在 2010 年与 2011 年之间加入、其用户名中含有 "john" 字样的用户。 | + +## 按关注者数量搜索 + +您可以使用 `followers` 限定符以及[大于、小于和范围限定符](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)基于用户拥有的关注者数量过滤用户。 + +| 限定符 | 示例 | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | +| followers:n | [**followers:>=1000**](https://github.com/search?q=followers%3A%3E%3D1000&type=Users) 匹配有 1,000 个或更多关注者的用户。 | +| | [**sparkle followers:1..10**](https://github.com/search?q=sparkle+followers%3A1..10&type=Users) 匹配具有 1 到 10 个关注者、其名称中含有 "sparkle" 字样的用户。 | + +{% ifversion fpt %} + +## Search based on ability to sponsor + +You can search for users and organizations who can be sponsored on {% data variables.product.prodname_sponsors %} with the `is:sponsorable` qualifier. 更多信息请参阅“[关于 {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)”。 + +| 限定符 | 示例 | +| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `is:sponsorable` | [**is:sponsorable**](https://github.com/search?q=is%3Asponsorable&type=Users) matches users and organizations who have a {% data variables.product.prodname_sponsors %} profile. | + +{% endif %} + +## 延伸阅读 + +- “[排序搜索结果](/search-github/getting-started-with-searching-on-github/sorting-search-results/)” diff --git a/translations/zh-CN/content/search-github/searching-on-github/searching-wikis.md b/translations/zh-CN/content/search-github/searching-on-github/searching-wikis.md new file mode 100644 index 0000000000..fa7c44c8f4 --- /dev/null +++ b/translations/zh-CN/content/search-github/searching-on-github/searching-wikis.md @@ -0,0 +1,51 @@ +--- +title: 搜索 wiki +intro: '您可以在 {% data variables.product.product_name %} 上搜索 wiki，并使用这些 wiki 搜索限定符的任意组合缩小结果范围。' +redirect_from: + - /articles/searching-wikis + - /github/searching-for-information-on-github/searching-wikis + - /github/searching-for-information-on-github/searching-on-github/searching-wikis +versions: + fpt: '*' + ghes: '*' + ghae: '*' +topics: + - GitHub search +--- + +您可以在所有 {% data variables.product.product_name %} 内全局搜索 wiki，也可以在特定仓库或组织内搜索 wiki。 更多信息请参阅“[关于在 {% data variables.product.company_short %} 上搜索](/search-github/getting-started-with-searching-on-github/about-searching-on-github)”。 + +{% data reusables.search.syntax_tips %} + +## 在用户或组织的仓库内搜索 + +要从特定用户或组织拥有的所有仓库中查找 wiki 页面，请使用 `user` 或 `org` 限定符。 要从特定仓库中查找 wiki 页面，请使用 `repo` 限定符。 + +| 限定符 | 示例 | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**user:defunkt**](https://github.com/search?q=user%3Adefunkt&type=Wikis) 匹配来自 @defunkt 拥有的仓库的 wiki 页面。 | +| org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=Wikis&utf8=%E2%9C%93) 匹配 GitHub 组织拥有的仓库中的 wiki。 | +| repo:USERNAME/REPOSITORY | [**repo:defunkt/gibberish**](https://github.com/search?q=user%3Adefunkt&type=Wikis) 匹配来自 @defunkt 的 "gibberish" 仓库的 wiki 页面。 | + +## 在 wiki 页面标题或正文文本中搜索 + +`in` 限定符将搜索限制为 wiki 页面标题或正文文本。 如果未使用该限定符，将同时搜索标题和正文文本。 + +| 限定符 | 示例 | +| ---------- | ---------------------------------------------------------------------------------------------------------------------------------- | +| `in:title` | [**usage in:title**](https://github.com/search?q=usage+in%3Atitle&type=Wikis) 匹配含有 "usage" 字样的 wiki 页面。 | +| `in:body` | [**installation in:body**](https://github.com/search?q=installation+in%3Abody&type=Wikis) 匹配其主要正文文本中含有 "installation" 字样的 wiki 页面。 | + +## 按上次更新日期搜索 + +`updated` 限定符匹配其上次更新在指定日期范围内的 wiki 页面。 + +{% data reusables.search.date_gt_lt %} + +| 限定符 | 示例 | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | +| updated:YYYY-MM-DD | [**usage updated:>2016-01-01**](https://github.com/search?q=usage+updated%3A>2016-01-01&type=Wikis) 匹配包含文字 "usage" 且上次更新在 2016-01-01 后的 wiki 页面。 | + +## 延伸阅读 + +- “[排序搜索结果](/search-github/getting-started-with-searching-on-github/sorting-search-results/)” diff --git a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md index 683b61006c..3c6713a5d6 100644 --- a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md +++ b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md @@ -30,6 +30,7 @@ shortTitle: 管理付款等级 1. （可选）要编辑草稿级，找到草稿级并点击 **Edit（编辑）**。 ![草稿等级旁边的编辑按钮](/assets/images/help/sponsors/draft-tier-edit.png) {% data reusables.sponsors.click-add-tier %} {% data reusables.sponsors.tier-price-description %} +{% data reusables.sponsors.add-welcome-message %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} 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 415c4868ce..2390520e30 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 @@ -51,6 +51,7 @@ shortTitle: 为组织设置 {% data reusables.sponsors.navigate-to-sponsor-tiers-tab %} {% data reusables.sponsors.click-add-tier %} {% data reusables.sponsors.tier-price-description %} +{% data reusables.sponsors.add-welcome-message %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} {% data reusables.sponsors.add-more-tiers %} 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-user-account.md index 131bafcb4d..f36d6edfbf 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-user-account.md @@ -50,6 +50,7 @@ shortTitle: 设置用户帐户 {% data reusables.sponsors.navigate-to-sponsor-tiers-tab %} {% data reusables.sponsors.click-add-tier %} {% data reusables.sponsors.tier-price-description %} +{% data reusables.sponsors.add-welcome-message %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} {% data reusables.sponsors.add-more-tiers %} 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 54a304146d..d791bead64 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 @@ -37,6 +37,8 @@ The W-8 BEN and W-8 BEN-E tax forms ask for a "U.S. taxpayer identification numb If you are not a U.S. citizen or other U.S. person, including a resident alien individual, then you will usually need to provide the "Foreign tax identifying number". This is a tax identification number that your country of residence has issued you. +If your country of residence or billing country is India, then you can use your Permanent Account Number (PAN) as your tax identification number. + {% note %} **Note:** If your country does not require citizens to have a tax number issued by the government, then you can instead write "not legally required". @@ -56,6 +58,18 @@ If you are a taxpayer in the United States and earn more than 600 US dollars in {% data reusables.sponsors.sponsorships-not-tax-deductible %} +## Sales tax + +GitHub is providing information to assist you in calculating your sales tax obligations. This information is not personalized to your country or tax situation and we recommend you talk to a professional to understand your specific obligations. However, we'd like to provide some high-level information to help you understand the general principles of digital sales tax. + +In most countries around the world, sales tax for digital transactions is based on the location of the recipient, not on the seller. For example, if you are a maintainer in the United States and you provide a taxable benefit to a Sponsor in Germany, German sales tax would apply. + +Sales tax is generally only applicable when a good or service of value is being provided. Goodwill/general support/undying appreciation is not normally taxable. + +In the US, both B2B (business-to-business) and B2C (business-to-consumer) are subject to sales tax. + +In the EU and most other countries and regions, B2C sales are subject to sales tax. B2B sales are not subject to tax. C2C and C2B sales where a consumer is not registered for VAT are not taxable. + ## 延伸阅读 - [查看您的赞助者和赞助](/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships) diff --git a/translations/zh-CN/data/glossaries/external.yml b/translations/zh-CN/data/glossaries/external.yml index be89a1e509..5e6a394f7b 100644 --- a/translations/zh-CN/data/glossaries/external.yml +++ b/translations/zh-CN/data/glossaries/external.yml @@ -9,7 +9,7 @@ - term: 帐户恢复令牌 description: >- - 作为帐户恢复设置一部分存储的身份验证凭据称为“异地恢复帐户”，用于存储此备份凭据。 + **Deprecated and will be disabled December 1st, 2021.** The authentication credential stored as part of an account recovery setup called Recover Accounts Elsewhere that allows you to store this backup credential. - term: API 预览 description: >- @@ -574,7 +574,7 @@ - term: 异地恢复帐户 description: >- - 允许用户在无法使用双重身份验证方法或恢复代码时向其 GitHub 帐户添加额外一重安全保护。用户可以通过 Facebook 以帐户恢复令牌的形式存储其 GitHub 帐户的身份验证凭据，将其 GitHub 帐户与其 Facebook 帐户相关联。 + **Deprecated and will be disabled December 1st, 2021.** Allows users to add an extra security factor to their GitHub account in case they lose access to their two-factor authentication method or recovery codes. Users can associate their GitHub account with their Facebook account by storing an authentication credential in the form of an account recovery token for their GitHub account with Facebook. - term: 恢复代码 description: 帮助您重新获取对 GitHub 帐户的访问权限的代码。 diff --git a/translations/zh-CN/data/learning-tracks/actions.yml b/translations/zh-CN/data/learning-tracks/actions.yml index 7ec87b6409..d0a27754d1 100644 --- a/translations/zh-CN/data/learning-tracks/actions.yml +++ b/translations/zh-CN/data/learning-tracks/actions.yml @@ -7,6 +7,7 @@ getting_started: - /actions/learn-github-actions/finding-and-customizing-actions - /actions/learn-github-actions/essential-features-of-github-actions - /actions/learn-github-actions/managing-complex-workflows + - /actions/learn-github-actions/reusing-workflows - /actions/learn-github-actions/security-hardening-for-github-actions featured_track: true continuous_integration: diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-20/15.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-20/15.yml index aa3c664487..f5de5bd11e 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-20/15.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-20/15.yml @@ -1,24 +1,25 @@ +--- date: '2020-08-26' sections: security_fixes: - >- - **CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2883, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700, - https://github.com/github/pages/pull/2890, https://github.com/github/pages/pull/2898, https://github.com/github/pages/pull/2909, https://github.com/github/pages/pull/2891, https://github.com/github/pages/pull/2884, https://github.com/github/pages/pull/2889 {% endcomment %} - - '**MEDIUM:** An improper access control vulnerability was identified that allowed authenticated users of the instance to determine the names of unauthorized private repositories given their numerical IDs. This vulnerability did not allow unauthorized access to any repository content besides the name. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.22 and has been assigned [CVE-2020-10517](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10517). The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/151987, https://github.com/github/github/pull/151713 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21852, https://github.com/github/enterprise2/pull/21828, https://github.com/github/enterprise2/pull/22153, https://github.com/github/enterprise2/pull/21920, https://github.com/github/enterprise2/pull/22215, https://github.com/github/enterprise2/pull/22190 {% endcomment %}' + **CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2883, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700, https://github.com/github/pages/pull/2890, https://github.com/github/pages/pull/2898, https://github.com/github/pages/pull/2909, https://github.com/github/pages/pull/2891, https://github.com/github/pages/pull/2884, https://github.com/github/pages/pull/2889 {% endcomment %} + - '**中：** 发现了不适当的访问控制漏洞，允许经验证的实例用户根据其数字 ID 来确定未授权私有仓库的名称。该漏洞不允许未授权访问除名称以外的任何仓库内容。此漏洞会影响 GitHub Enterprise Server 2.22 之前的所有版本，且已分配 [CVE-2020-10517](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CV-2020-10517)。漏洞是通过 [GitHub Bug Bounty 计划](https://bounty.github.com) 报告的。{% comment %} https://github.com/github/github/pull/151987, https://github.com/github/github/pull/151713 {% endcomment %}' + - '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/21852, https://github.com/github/enterprise2/pull/21828, https://github.com/github/enterprise2/pull/22153, https://github.com/github/enterprise2/pull/21920, https://github.com/github/enterprise2/pull/22215, https://github.com/github/enterprise2/pull/22190 {% endcomment %}' bugs: - - 'A message was not logged when the ghe-config-apply process had finished running ghe-es-auto-expand. {% comment %} https://github.com/github/enterprise2/pull/22177, https://github.com/github/enterprise2/pull/22171 {% endcomment %}' - - 'Excessive logging to the `syslog` file could occur on high-availability replicas if the primary appliance is unavailable. {% comment %} https://github.com/github/enterprise2/pull/22267, https://github.com/github/enterprise2/pull/22124 {% endcomment %}' - - "Database re-seeding on a replica could fail with an error: `Got packet bigger than 'max_allowed_packet'` {% comment %} https://github.com/github/enterprise2/pull/22321, https://github.com/github/enterprise2/pull/20063 {% endcomment %}" - - 'In some cases duplicate user data could cause a 500 error while running the ghe-license-usage script. {% comment %} https://github.com/github/github/pull/152638 {% endcomment %}' + - '当 ghe-config-application 进程运行完 ghe-es-auto-extension 时，消息未记录。{% comment %} https://github.com/github/enterprise2/pull/22177, https://github.com/github/enterprise2/pull/22171 {% endcomment %}' + - '如果主要设备不可用，则可能会在高可用性副本上过多记录到 `syslog` 文件。 {% comment %} https://github.com/github/enterprise2/pull/22267, https://github.com/github/enterprise2/pull/22124 {% endcomment %}' + - "副本上的数据库重新播种可能会失败，并显示错误：“获取的数据包大于 'max_allowed_packet'”{% comment %} https://github.com/github/enterprise2/pull/22321, https://github.com/github/enterprise2/pull/20063 {% endcomment %}" + - '在某些情况下，重复的用户数据可能在运行 ghe-license-usage 脚本时造成 500 错误。{% comment %} https://github.com/github/github/pull/152638 {% endcomment %}' changes: - - 'In a high availability or geo-replication configuration, replica instances would exit maintenance mode when ghe-config-apply ran. {% comment %} https://github.com/github/enterprise2/pull/21776, https://github.com/github/enterprise2/pull/21440 {% endcomment %}' - - "We've added support for the R5a and R5n AWS instance types. {% comment %} https://github.com/github/enterprise2/pull/21902, https://github.com/github/enterprise2/pull/21173 {% endcomment %}" - - 'Removed the license seat count information on the administrative SSH MOTD due to a performance issue impacting GitHub Enterprise Server clusters. {% comment %} https://github.com/github/enterprise2/pull/21993, https://github.com/github/enterprise2/pull/21870 {% endcomment %}' + - '在高可用性或地理复制配置中，副本实例在 ghe-config-apply 运行时会退出维护模式。{% comment %} https://github.com/github/enterprise2/pull/21776, https://github.com/github/enterprise2/pull/21440 {% endcomment %}' + - "我们添加了对 R5a 和 R5n AWS 实例类型的支持。{% comment %} https://github.com/github/enterprise2/pull/21902, https://github.com/github/enterprise2/pull/21173 {% endcomment %}" + - '由于影响 GitHub Enterprise Server 集群的性能问题，删除了管理 SSH MOTD 上的许可证席位计数信息。{% comment %} https://github.com/github/enterprise2/pull/21993, https://github.com/github/enterprise2/pull/21870 {% endcomment %}' known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - '在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可能创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - '自定义防火墙规则在升级期间没有维护。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '议题若是包含同一仓库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，私有和内部仓库中的议题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - '推送到命令行上的仓库时，不会报告安全警报。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - '当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-21/6.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-21/6.yml index 03c71afb3a..1fc801e97b 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/2-21/6.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-21/6.yml @@ -1,27 +1,28 @@ +--- date: '2020-08-26' sections: security_fixes: - >- - **CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2882, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700, - https://github.com/github/pages/pull/2889, https://github.com/github/pages/pull/2899, https://github.com/github/pages/pull/2903, https://github.com/github/pages/pull/2890, https://github.com/github/pages/pull/2891, https://github.com/github/pages/pull/2884 {% endcomment %} - - '**MEDIUM:** An improper access control vulnerability was identified that allowed authenticated users of the instance to determine the names of unauthorized private repositories given their numerical IDs. This vulnerability did not allow unauthorized access to any repository content besides the name. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.22 and has been assigned [CVE-2020-10517](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10517). The vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com). {% comment %} https://github.com/github/github/pull/151986, https://github.com/github/github/pull/151713 {% endcomment %}' - - 'Packages have been updated to the latest security versions. {% comment %} https://github.com/github/enterprise2/pull/21853, https://github.com/github/enterprise2/pull/21828, https://github.com/github/enterprise2/pull/22154, https://github.com/github/enterprise2/pull/21920, https://github.com/github/enterprise2/pull/22216, https://github.com/github/enterprise2/pull/22190 {% endcomment %}' + **CRITICAL:** A remote code execution vulnerability was identified in GitHub Pages that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. The underlying issues contributing to this vulnerability were identified both internally and through the GitHub Security Bug Bounty program. We have issued CVE-2020-10518. {% comment %} https://github.com/github/pages/pull/2882, https://github.com/github/pages/pull/2902, https://github.com/github/pages/pull/2894, https://github.com/github/pages/pull/2877, https://github.com/github/pages-gem/pull/700, https://github.com/github/pages/pull/2889, https://github.com/github/pages/pull/2899, https://github.com/github/pages/pull/2903, https://github.com/github/pages/pull/2890, https://github.com/github/pages/pull/2891, https://github.com/github/pages/pull/2884 {% endcomment %} + - '**中：** 发现了不适当的访问控制漏洞，允许经验证的实例用户根据其数字 ID 来确定未授权私有仓库的名称。该漏洞不允许未授权访问除名称以外的任何仓库内容。此漏洞会影响 GitHub Enterprise Server 2.22 之前的所有版本，且已分配 [CVE-2020-10517](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CV-2020-10517)。漏洞是通过 [GitHub Bug Bounty 计划](https://bounty.github.com) 报告的。 {% comment %} https://github.com/github/github/pull/151986, https://github.com/github/github/pull/151713 {% endcomment %}' + - '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/21853, https://github.com/github/enterprise2/pull/21828, https://github.com/github/enterprise2/pull/22154, https://github.com/github/enterprise2/pull/21920, https://github.com/github/enterprise2/pull/22216, https://github.com/github/enterprise2/pull/22190 {% endcomment %}' bugs: - - 'A message was not logged when the ghe-config-apply process had finished running ghe-es-auto-expand. {% comment %} https://github.com/github/enterprise2/pull/22178, https://github.com/github/enterprise2/pull/22171 {% endcomment %}' - - 'Excessive logging to the `syslog` file could occur on high-availability replicas if the primary appliance is unavailable. {% comment %} https://github.com/github/enterprise2/pull/22268, https://github.com/github/enterprise2/pull/22124 {% endcomment %}' - - "Database re-seeding on a replica could fail with an error: `Got packet bigger than 'max_allowed_packet'` {% comment %} https://github.com/github/enterprise2/pull/22322, https://github.com/github/enterprise2/pull/20063 {% endcomment %}" - - 'In some cases duplicate user data could cause a 500 error while running the ghe-license-usage script. {% comment %} https://github.com/github/github/pull/152637 {% endcomment %}' - - 'Using `ghe-migrator`, the `add` command would fail to lock a repository when using the `--lock` flag. {% comment %} https://github.com/github/github/pull/152780, https://github.com/github/github/pull/152588 {% endcomment %}' + - '当 ghe-config-application 进程运行完 ghe-es-auto-extension 时，消息未记录。{% comment %} https://github.com/github/enterprise2/pull/22178, https://github.com/github/enterprise2/pull/22171 {% endcomment %}' + - '如果主要设备不可用，则可能会在高可用性副本上过多记录到 `syslog` 文件。 {% comment %} https://github.com/github/enterprise2/pull/22268, https://github.com/github/enterprise2/pull/22124 {% endcomment %}' + - "副本上的数据库重新播种可能会失败，并显示错误：“获取的数据包大于 'max_allowed_packet'”{% comment %} https://github.com/github/enterprise2/pull/22322, https://github.com/github/enterprise2/pull/20063 {% endcomment %}" + - '在某些情况下，重复的用户数据可能在运行 ghe-license-usage 脚本时造成 500 错误。{% comment %} https://github.com/github/github/pull/152637 {% endcomment %}' + - '使用 `ghe-migrator`，`add` 命令在使用 `--lock` 标志时无法锁定仓库。{% comment %} https://github.com/github/github/pull/152780, https://github.com/github/github/pull/15258 {% endcomment %}' changes: - - 'In a high availability or geo-replication configuration, replica instances would exit maintenance mode when ghe-config-apply ran. {% comment %} https://github.com/github/enterprise2/pull/21777, https://github.com/github/enterprise2/pull/21440 {% endcomment %}' - - "We've added support for the R5a and R5n AWS instance types. {% comment %} https://github.com/github/enterprise2/pull/21903, https://github.com/github/enterprise2/pull/21173 {% endcomment %}" - - 'Removed the license seat count information on the administrative SSH MOTD due to a performance issue impacting GitHub Enterprise Server clusters. {% comment %} https://github.com/github/enterprise2/pull/21994, https://github.com/github/enterprise2/pull/21870 {% endcomment %}' + - '在高可用性或地理复制配置中，副本实例在 ghe-config-apply 运行时会退出维护模式。{% comment %} https://github.com/github/enterprise2/pull/21777, https://github.com/github/enterprise2/pull/21440 {% endcomment %}' + - "我们添加了对 R5a 和 R5n AWS 实例类型的支持。{% comment %} https://github.com/github/enterprise2/pull/21903, https://github.com/github/enterprise2/pull/21173 {% endcomment %}" + - '由于影响 GitHub Enterprise Server 集群的性能问题，删除了管理 SSH MOTD 上的许可证席位计数信息。{% comment %} https://github.com/github/enterprise2/pull/21994, https://github.com/github/enterprise2/pull/21870 {% endcomment %}' known_issues: - - 'On a freshly set up GitHub Enterprise Server without any users, an attacker could create the first admin user. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' - - 'Custom firewall rules are not maintained during an upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' - - '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. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' - - 'Issues cannot be closed if they contain a permalink to a blob in the same repository where the file path is longer than 255 characters. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' - - '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. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' - - 'Security alerts are not reported when pushing to a repository on the command line. {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' - - 'Audit logs may be attributed to 127.0.0.1 instead of the actual source IP address. (updated 2020-11-02) {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' - - "Configuring a repository's permission to `Triage` or `Maintain` fails with an error message." + - '在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可能创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}' + - '自定义防火墙规则在升级期间没有维护。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}' + - 'Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}' + - '议题若是包含同一仓库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}' + - '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，私有和内部仓库中的议题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}' + - '推送到命令行上的仓库时，不会报告安全警报。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}' + - '审核日志可归因于 127.0.0.1，而不是实际源 IP 地址。（更新于 2020-11-02） {% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}' + - "配置仓库的权限到“分类”或“维护”失败，且显示错误消息。" + - '当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/2-22/22.yml b/translations/zh-CN/data/release-notes/enterprise-server/2-22/22.yml new file mode 100644 index 0000000000..ce9c266a5e --- /dev/null +++ b/translations/zh-CN/data/release-notes/enterprise-server/2-22/22.yml @@ -0,0 +1,15 @@ +--- +date: '2021-09-24' +sections: + security_fixes: + - '**HIGH:** A path traversal vulnerability was identified in {% data variables.product.prodname_ghe_server %} that could be exploited when building a {% data variables.product.prodname_pages %} site. User-controlled configuration options used by {% data variables.product.prodname_pages %} were not sufficiently restricted and made it possible to read files on the {% data variables.product.prodname_ghe_server %} instance. To exploit this vulnerability, an attacker would need 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.1.8 and was fixed in 3.1.8, 3.0.16, and 2.22.22. This is the result of an incomplete fix for CVE-2021-22867. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned CVE-2021-22868. {% comment %} https://github.com/github/pages/pull/3359, https://github.com/github/pages/pull/3357 {% endcomment %}' + bugs: + - 'The {% data variables.product.prodname_github_connect %} configuration of the source instance was always restored to new instances even when the `--config` option for `ghe-restore` was not used. This would lead to a conflict with the {% data variables.product.prodname_github_connect %} connection and license synchronization if both the source and destination instances were online at the same time. {% comment %} https://github.com/github/github/pull/192247, https://github.com/github/github/pull/191951, https://github.com/github/enterprise2/pull/26870, https://github.com/github/backup-utils/pull/770, https://github.com/github/connected-enterprise/issues/208 {% endcomment %}' + - 'Fixes {% data variables.product.prodname_pages %} builds so they take into account the NO_PROXY setting of the appliance. This is relevant to appliances configured with an HTTP proxy only. {% comment %} https://github.com/github/github/pull/192380 {% endcomment %}' + 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 GitHub.com search results. + - 当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。 diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-0/16.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-0/16.yml new file mode 100644 index 0000000000..6208be4fc6 --- /dev/null +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-0/16.yml @@ -0,0 +1,18 @@ +--- +date: '2021-09-24' +sections: + security_fixes: + - '**HIGH:** A path traversal vulnerability was identified in {% data variables.product.prodname_ghe_server %} that could be exploited when building a {% data variables.product.prodname_pages %} site. User-controlled configuration options used by {% data variables.product.prodname_pages %} were not sufficiently restricted and made it possible to read files on the {% data variables.product.prodname_ghe_server %} instance. To exploit this vulnerability, an attacker would need 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.1.8 and was fixed in 3.1.8, 3.0.16, and 2.22.22. This is the result of an incomplete fix for CVE-2021-22867. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned CVE-2021-22868. {% comment %} https://github.com/github/pages/pull/3360, https://github.com/github/pages/pull/3357 {% endcomment %}' + - '**MEDIUM:** An improper access control vulnerability in {% data variables.product.prodname_ghe_server %} allowed a workflow job to execute in a self-hosted runner group it should not have had access to. This affects customers using self-hosted runner groups for access control. A repository with access to one enterprise runner group could access all of the enterprise runner groups within the organization because of improper authentication checks during the request. This could cause code to be run unintentionally by the incorrect runner group. This vulnerability affected {% data variables.product.prodname_ghe_server %} versions from 3.0.0 to 3.0.15 and 3.1.0 to 3.1.7 and was fixed in 3.0.16 and 3.1.8 releases. It has been assigned CVE-2021-22869. {% comment %} https://github.com/github/enterprise2/pull/27003 {% endcomment %}' + bugs: + - 'Resque worker counts were displayed incorrectly during maintenance mode. {% comment %} https://github.com/github/enterprise2/pull/26898, https://github.com/github/enterprise2/pull/26883 {% endcomment %}' + - 'Allocated memcached memory could be zero in clustering mode. {% comment %} https://github.com/github/enterprise2/pull/26927, https://github.com/github/enterprise2/pull/26832 {% endcomment %}' + - 'Fixes {% data variables.product.prodname_pages %} builds so they take into account the NO_PROXY setting of the appliance. This is relevant to appliances configured with an HTTP proxy only. (update 2021-09-30) {% comment %} https://github.com/github/pages/pull/3360 {% endcomment %}' + known_issues: + - 在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。 + - 自定义防火墙规则在升级过程中被删除。 + - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。 + - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。 + - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，私有和内部仓库中的议题不包括在 GitHub.com 搜索结果中。 + - 当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。 + - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-1/8.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-1/8.yml new file mode 100644 index 0000000000..25c8412da1 --- /dev/null +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-1/8.yml @@ -0,0 +1,20 @@ +--- +date: '2021-09-24' +sections: + security_fixes: + - '**HIGH:** A path traversal vulnerability was identified in {% data variables.product.prodname_ghe_server %} that could be exploited when building a {% data variables.product.prodname_pages %} site. User-controlled configuration options used by {% data variables.product.prodname_pages %} were not sufficiently restricted and made it possible to read files on the {% data variables.product.prodname_ghe_server %} instance. To exploit this vulnerability, an attacker would need 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.1.8 and was fixed in 3.1.8, 3.0.16, and 2.22.22. This is the result of an incomplete fix for CVE-2021-22867. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned CVE-2021-22868. {% comment %} https://github.com/github/pages/pull/3361, https://github.com/github/pages/pull/3357 {% endcomment %}' + - '**MEDIUM:** An improper access control vulnerability in {% data variables.product.prodname_ghe_server %} allowed a workflow job to execute in a self-hosted runner group it should not have had access to. This affects customers using self-hosted runner groups for access control. A repository with access to one enterprise runner group could access all of the enterprise runner groups within the organization because of improper authentication checks during the request. This could cause code to be run unintentionally by the incorrect runner group. This vulnerability affected {% data variables.product.prodname_ghe_server %} versions from 3.0.0 to 3.0.15 and 3.1.0 to 3.1.7 and was fixed in 3.0.16 and 3.1.8 releases. It has been assigned CVE-2021-22869. {% comment %} https://github.com/github/enterprise2/pull/27013 {% endcomment %}' + bugs: + - 'Resque worker counts were displayed incorrectly during maintenance mode. {% comment %} https://github.com/github/enterprise2/pull/26899, https://github.com/github/enterprise2/pull/26883 {% endcomment %}' + - 'Allocated memcached memory could be zero in clustering mode. {% comment %} https://github.com/github/enterprise2/pull/26928, https://github.com/github/enterprise2/pull/26832 {% endcomment %}' + - 'Non-empty binary files displayed an incorrect file type and size on the pull request "Files" tab. {% comment %} https://github.com/github/github/pull/192810, https://github.com/github/github/pull/172284, https://github.com/github/coding/issues/694 {% endcomment %}' + - 'Fixes {% data variables.product.prodname_pages %} builds so they take into account the NO_PROXY setting of the appliance. This is relevant to appliances configured with an HTTP proxy only. (update 2021-09-30) {% comment %} https://github.com/github/pages/pull/3360 {% endcomment %}' + known_issues: + - '{% data variables.product.prodname_registry %} npm 注册表不再返回元数据响应的时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。' + - 在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。 + - 自定义防火墙规则在升级过程中被删除。 + - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。 + - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。 + - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，私有和内部仓库中的议题不包括在 GitHub.com 搜索结果中。 + - If {% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_server %}, teardown of a replica node with `ghe-repl-teardown` will succeed, but may return `ERROR:Running migrations`. + - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-2/0-rc1.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-2/0-rc1.yml index 57a557e6cd..97d402c569 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/0-rc1.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-2/0-rc1.yml @@ -1,7 +1,7 @@ --- date: '2021-09-09' release_candidate: true -deprecated: false +deprecated: true intro: 如果 {% data variables.product.product_location %} 正在运行候选版本，则无法使用热补丁进行升级。我们建议仅在测试环境中运行候选版本。 sections: features: diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-2/0.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-2/0.yml new file mode 100644 index 0000000000..c3bf7d6ff7 --- /dev/null +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-2/0.yml @@ -0,0 +1,221 @@ +--- +date: '2021-09-28' +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: Custom patterns for secret scanning + notes: + - | + {% data variables.product.prodname_GH_advanced_security %} customers can now specify custom patterns for secret scanning. When a new pattern is specified, secret scanning searches a repository's entire Git history for the pattern, as well as any new commits. + + User defined patterns are in beta for {% data variables.product.prodname_ghe_server %} 3.2. They can be defined at the repository, organization, and enterprise levels. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." + - + heading: Security overview for Advanced Security (beta) + notes: + - | + {% data variables.product.prodname_GH_advanced_security %} customers now have an organization-level view of the application security risks detected by {% data variables.product.prodname_code_scanning %}, {% data variables.product.prodname_dependabot %}, and {% data variables.product.prodname_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 {% data variables.product.prodname_secret_scanning %} alerts at the organization level. Similar views for {% data variables.product.prodname_dependabot %} and {% data variables.product.prodname_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 review (beta) + notes: + - | + {% data variables.product.prodname_GH_advanced_security %} customers can now see a rich diff of the dependencies changed in a pull request. 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 these dependencies. 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)." + - + heading: GitHub Actions environments + notes: + - | + Environments, environment protection rules, and environment secrets are now generally available for {% data variables.product.prodname_actions %} on {% data variables.product.product_name %}. For more information, see "[Environments](/actions/reference/environments)." + + ![Environment protection rules](/assets/images/enterprise/3.2/release-notes/actions-environments.png) + - + heading: SSH authentication with security keys + notes: + - | + SSH authentication using a FIDO2 security key is now supported when you add a `sk-ecdsa-sha2-nistp256@openssh.com` or `sk-ssh-ed25519@openssh.com` SSH key to your account. SSH security keys store secret key material on a separate hardware device that requires verification, such as a tap, to operate. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)." + - + heading: 'Dark and dark dimmed themes' + notes: + - | + Dark and dark dimmed themes are now available for the web UI. {% data variables.product.product_name %} will match your system preferences when you haven't set theme preferences in {% data variables.product.product_name %}. You can also choose which themes are active during the day and night. For more information, see "[Managing your theme settings](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)." + + ![Dark and dark dimmed themes](https://user-images.githubusercontent.com/33528647/114629560-d2231f80-9c86-11eb-9bde-cc301a97040d.gif) + - + heading: 'Approving unverified domains for email notifications' + notes: + - 'Domains that are not able to be verified can now be approved for email notification routing. Enterprise and organization owners will be able to approve domains and immediately augment their email notification restriction policy, allowing notifications to be sent to collaborators, consultants, acquisitions, or other partners. For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#about-approval-of-domains)" and "[Restricting email notifications for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise#restricting-email-notifications-for-your-enterprise-account)."' + - + heading: 'Git Credential Manager (GCM) secure credential storage and multi-factor authentication support' + notes: + - | + Git Credential Manager (GCM) Core versions 2.0.452 and later now provide security-hardened credential storage and multi-factor authentication support for {% data variables.product.product_name %}. + + GCM Core with support for {% data variables.product.product_name %} is included with [Git for Windows](https://gitforwindows.org) versions 2.32 and later. GCM Core is not included with Git for macOS or Linux, but can be installed separately. For more information, see the [latest release](https://github.com/microsoft/Git-Credential-Manager-Core/releases/) and [installation instructions](https://github.com/microsoft/Git-Credential-Manager-Core/releases/) in the `microsoft/Git-Credential-Manager-Core` repository. + changes: + - + heading: 管理更改 + notes: + - A 'User Agent Referrer Policy' setting has been added to the enterprise settings. This allows an admin to set a stricter `Referrer-Policy` to hide the hostname of a {% data variables.product.prodname_ghe_server %} installation from external sites. The setting is disabled by default and is tracked by audit log events for staff and enterprise owners when enabled or disabled. For more information, see "[Configuring Referrer Policy for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)." + - The MySQL health check was changed to use `mysqladmin ping` instead of TCP checks, which removes some unnecessary noise in the MySQL error log. Also, Orchestrator failover checks were improved to prevent unnecessary MySQL failovers when applying cluster config changes. + - 'The Resque service, which supports background job processing, has been replaced with Aqueduct Lite. This change makes the job system easier to manage and should not affect the user experience. For the new administration and debugging commands for Aqueduct, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-aqueduct)."' + - + heading: Token Changes + notes: + - | + The format of authentication tokens for {% data variables.product.product_name %} has changed. The change affects the format of personal access tokens and access tokens for {% data variables.product.prodname_oauth_apps %}, as well as user-to-server, server-to-server, and refresh tokens for {% data variables.product.prodname_github_apps %}. + + The different token types now have unique identifiable prefixes, which allows for secret scanning to detect the tokens so that you can mitigate the impact of someone accidentally committing a token to a repository. {% data variables.product.company_short %} recommends updating existing tokens as soon as possible. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github#githubs-token-formats)" and "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)." + - + heading: 'Repositories changes' + notes: + - Repositories on user profiles and organization profiles now support sorting by star count. + - When viewing the commit history of a single file, you can now click {% octicon "file-code" aria-label="The code icon" %} to view that file at the selected point in history. + - When a submodule is defined with a relative path in {% data variables.product.product_location %}, the submodule is now clickable in the web UI. Clicking the submodule in the web UI will take you to the linked repository. Previously, only submodules with absolute URLs were clickable. This is supported for relative paths for repositories with the same owner that follow the pattern ../REPOSITORY or relative paths for repositories with a different owner that follow the pattern ../OWNER/REPOSITORY. For more information about working with submodules, see [Working with submodules](https://github.blog/2016-02-01-working-with-submodules/) on {% data variables.product.prodname_blog %}. + - 'The web UI can now be used to synchronize an out-of-date branch of a fork with the fork''s upstream branch. If there are no merge conflicts between the branches, the branch is updated either by fast-forwarding or by merging from upstream. If there are conflicts, you will be prompted to create a pull request to resolve the conflicts. For more information, see "[Syncing a fork](/github/collaborating-with-pull-requests/working-with-forks/syncing-a-fork#syncing-a-fork-from-the-web-ui)."' + - + heading: 'Markdown changes' + notes: + - 'The markdown editor used when creating or editing a release in a repository now has a text-editing toolbar. For more information, see "[Managing releases in a repository](/github/administering-a-repository/releasing-projects-on-github/managing-releases-in-a-repository#creating-a-release)."' + - Uploading video files is now supported everywhere you write Markdown on {% data variables.product.product_name %}. Share demos, reproduction steps, and more in your issue and pull request comments, as well as in Markdown files within repositories, such as READMEs. For more information, see "[Attaching files](/github/writing-on-github/working-with-advanced-formatting/attaching-files)." + - Markdown files will now automatically generate a table of contents in the header when there are 2 or more headings. The table of contents is interactive and links to the selected section. All 6 Markdown heading levels are supported. + - 'There is a new keyboard shortcut, `cmd+e` on macOS or `ctrl+e` on Windows, to insert codeblocks in Markdown files, issues, pull requests, and comments.' + - 'Appending `?plain=1` to the URL for any Markdown file will now display the file without rendering and with line numbers. The plain view can be used to link other users to specific lines. For example, appending `?plain=1#L52` will highlight line 52 of a plain text Markdown file. For more information, "[Creating a permanent link to a code snippet](/github/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet#linking-to-markdown)."' + - + heading: 'Issues and pull requests changes' + notes: + - With the [latest version of Octicons](https://github.com/primer/octicons/releases), the states of issues and pull requests are now more visually distinct so you can scan their status more easily. For more information, see [{% data variables.product.prodname_blog %}](https://github.blog/changelog/2021-06-08-new-issue-and-pull-request-state-icons/). + - 'A new "Require conversation resolution before merging" branch protection rule and "Conversations" menu is now available. Easily discover your pull request comments from the "Files changed" tab, and require that all your pull request conversations are resolved before merging. For more information, see "[About pull request reviews](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews#discovering-and-navigating-conversations)" and "[About protected branches](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-conversation-resolution-before-merging)."' + - To prevent the merge of unexpected changes after auto-merge is enabled for a pull request, auto-merge is now disabled automatically when new changes are pushed by a user without write access to the repository. Users without write access can still update the pull request with changes from the base branch when auto-merge is enabled. To prevent a malicious user from using a merge conflict to introduce unexpected changes to the pull request, auto-merge for the pull request is disabled if the update causes a merge conflict. For more information about auto-merge, see "[Automatically merging a pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)." + - 'People with maintain permissions 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 permissions 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. + - When a review is requested from a team of more than 100 people, developers are now shown a confirmation dialog box in order to prevent unnecessary notifications for large teams. + - Back-tick `code blocks` are now supported in issue titles, pull request titles, and in any place issue and pull request titles are referenced in {% data variables.product.prodname_ghe_server %}. + - 'Events for pull requests and pull request reviews are now included in the audit log for both [enterprises](/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise) and [organizations](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization). These events help admins better monitor pull request activity and help ensure security and compliance requirements are being met. Events can be viewed from the web UI, exported as CSV or JSON, or accessed via REST API. You can also search the audit log for specific pull request events. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#pull_request-category-actions)."' + - + heading: 'Branches changes' + notes: + - | + The default branch name for new repositories is now `main`. Existing repositories are not impacted by this change. If users, organization owners, or enterprise owners have previously specified a default branch for new repositories, they are also not impacted. + + If you want to set a different default branch name, you can do so in the [user](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories), [organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization), or [enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name) settings. + - | + Branches, including the default branch, can now be renamed using the the {% data variables.product.product_name %} web UI. When a branch is renamed, any open pull requests and draft releases targeting the renamed branch will be retargeted automatically, and branch protection rules that explicitly reference the renamed branch will be updated. + + Admin permissions are required to rename the default branch, but write permissions are sufficient to rename other branches. + + To help make the change as seamless as possible for users: + + * A notice is shown to contributors, maintainers, and admins on the repository homepage with instructions for updating their local repository. + * Web requests to the old branch will be redirected. + * A "moved permanently" HTTP response will be returned to REST API calls. + * An informational message is displayed to Git command line users that push to the old branch. + + For more information, see "[Renaming a branch](/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch)." + - + heading: 'GitHub Actions changes' + notes: + - '{% data variables.product.prodname_actions %} now lets you control the permissions granted to the `GITHUB_TOKEN` secret. The `GITHUB_TOKEN` is an automatically-generated secret that lets you make authenticated calls to the API for {% data variables.product.product_name %} in your workflow runs. {% data variables.product.prodname_actions %} generates a new token for each job and expires the token when a job completes. The token usually has `write` permissions to a number of [API endpoints](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token), except in the case of pull requests from forks, which are always `read`. These new settings allow you to follow a principle of least privilege in your workflows. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token)."' + - '{% data variables.product.prodname_cli %} 1.9 and later allows you to work with {% data variables.product.prodname_actions %} in your terminal. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-04-15-github-cli-1-9-enables-you-to-work-with-github-actions-from-your-terminal/).' + - 'The audit log now includes events associated with {% data variables.product.prodname_actions %} workflow runs. This data provides administrators with a greatly expanded data set for security and compliance audits. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#workflows-category-actions)."' + - '{% data variables.product.prodname_ghe_server %} 3.2 contains performance improvements for job concurrency with {% data variables.product.prodname_actions %}. For more information on the new performance targets on 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)."' + - + heading: 'GitHub Packages changes' + notes: + - Any package or package version for {% data variables.product.prodname_registry %} can now be deleted from {% data variables.product.product_name %}'s web UI. You can also undo the deletion of any package or package version within 30 days. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)". + - + heading: 'Dependabot and Dependency graph changes' + notes: + - 'The dependency graph can now be enabled using the Management Console, rather than needing to run a command in the administrative shell. For more information, see "[Enabling alerts for vulnerable dependencies {% data variables.product.prodname_ghe_server %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server#enabling-the-dependency-graph-and-dependabot-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."' + - Notifications for multiple {% data variables.product.prodname_dependabot_alerts %} are now grouped together if they're discovered at the same time. This significantly reduces the volume of {% data variables.product.prodname_dependabot %} alert notifications that users receive. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-03-18-grouped-dependabot-alert-notifications/). + - 'Dependency graph and {% data variables.product.prodname_dependabot_alerts %} now support Go modules. {% data variables.product.prodname_ghe_server %} analyzes a repository''s `go.mod` files to understand the repository’s dependencies. Along with security advisories, the dependency graph provides the information needed to alert developers to vulnerable dependencies. For more information about enabling the dependency graph on private repositories, see "[Securing your repository](/code-security/getting-started/securing-your-repository#managing-the-dependency-graph)."' + - The default notification settings for security alerts have changed. Previously, if you had permission to view security alerts in a repository, you would receive notifications for that repository as long as your settings allowed for security alert notifications. Now, you must opt in to security alert notifications by watching the repository. You will be notified if you select `All Activity` or configure `Custom` to include `Security alerts`. All existing repositories will be automatically migrated to these new settings and you will continue to receive notifications; however, any new repositories will require opting-in by watching the repository. 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)" and "[Managing alerts from secret scanning](/code-security/secret-security/managing-alerts-from-secret-scanning)." + - + heading: 'Code scanning and secret scanning changes' + notes: + - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} now generates diagnostic information for all supported languages. This helps check the state of the created database to understand the status and quality of performed analysis. The diagnostic information is available starting in [version 2.5.6](https://github.com/github/codeql-cli-binaries/releases) of the [{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/). You can see the detailed diagnostic information in the {% data variables.product.prodname_actions %} logs for {% data variables.product.prodname_codeql %}. For more information, see "[Viewing code scanning logs](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs)."' + - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql_cli %} now supports analyzing several languages during a single build. This makes it easier to run code analysis to use CI/CD systems other than {% data variables.product.prodname_actions %}. The new mode of the `codeql database create` command is available starting [version 2.5.6](https://github.com/github/codeql-cli-binaries/releases) of the [{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/). For more information about setting this up, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-cli-in-your-ci-system)."' + - '{% data variables.product.prodname_code_scanning_capc %} alerts from all enabled tools are now shown in one consolidated list, so that you can easily prioritize across all alerts. You can view alerts from a specific tool by using the "Tool" filter, and the "Rule" and "Tag" filters will dynamically update based on your "Tool" selection.' + - '{% data variables.product.prodname_code_scanning_capc %} with {% data variables.product.prodname_codeql %} now includes beta support for analyzing C++20 code. This is only available when building codebases with GCC on Linux. C++20 modules are not supported yet.' + - 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 for several languages ([C++](https://github.com/github/codeql/tree/main/cpp), [JavaScript](https://github.com/github/codeql/tree/main/javascript), [Python](https://github.com/github/codeql/tree/main/python), and [Java](https://github.com/github/codeql/tree/main/java)). As a result, {% data variables.product.prodname_codeql %} can now detect even more potential sources of untrusted user data, review the steps through which that data flows, and identify potentially dangerous sinks in which this data could end up. This results in an overall improvement of the quality of the {% data variables.product.prodname_code_scanning %} alerts. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-07-01-codeql-code-scanning-now-recognizes-more-sources-and-uses-of-untrusted-user-data/). + - | + {% data variables.product.prodname_code_scanning_capc %} now shows `security-severity` levels for CodeQL security alerts. You can configure which `security-severity` levels will cause a check failure for a pull request. The severity level of security alerts can be `critical`, `high`, `medium`, or `low`. By default, any {% data variables.product.prodname_code_scanning %} alerts with a `security-severity` of `critical` or `high` will cause a pull request check failure. + + Additionally, you can now also configure which severity levels will cause a pull request check to fail for non-security alerts. You can configure this behavior at the repository level, and define whether alerts with the severity `error`, `warning`, or `note` will cause a pull request check to fail. By default, non-security {% data variables.product.prodname_code_scanning %} alerts with a severity of `error` will cause a pull request check failure. + + For more information see "[Defining which alert severity levels cause pull request check failure](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)." + + ![List of code scanning alerts with security levels](/assets/images/enterprise/3.2/release-notes/code-scanning-alerts.png) + - | + Improvements to the branch filter for {% data variables.product.prodname_code_scanning %} alerts make it clearer which {% data variables.product.prodname_code_scanning %} alerts are being displayed on the alerts page. By default, {% data variables.product.prodname_code_scanning %} alerts are filtered to show alerts for the default branch of the repository only. You can use the branch filter to display the alerts on any of the non-default branches. Any branch filter that has been applied is shown in the search bar. + + The search syntax has also been simplified to `branch:`. This syntax can be used multiple times in the search bar to filter on multiple branches. The previous syntax, `ref:refs/heads/`, is still supported, so any saved URLs will continue to work. + - | + Free text search is now available for code scanning alerts. You can search code scanning results to quickly find specific alerts without having to know exact search terms. The search is applied across the alert's name, description, and help text. The syntax is: + + - A single word returns all matches. + - Multiple search words returns matches to either word. + - Words in double quotes returns exact matches. + - The keyword 'AND' returns matches to multiple words. + - '{% data variables.product.prodname_secret_scanning_caps %} added patterns for 23 new service providers. For the updated list of supported secrets, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning)."' + - + heading: API 更改 + notes: + - 'Pagination support has been added to the Repositories REST API''s "compare two commits" endpoint, which returns a list of commits reachable from one commit or branch, but unreachable from another. The API can also now return the results for comparisons over 250 commits. For more information, see the "[Repositories](/rest/reference/repos#compare-two-commits)" REST API documentation and "[Traversing with pagination](/rest/guides/traversing-with-pagination)."' + - 'The REST API can now be used to programmatically resend or check the status of webhooks. For more information, see "[Repositories](/rest/reference/repos#webhooks)," "[Organizations](/rest/reference/orgs#webhooks)," and "[Apps](/rest/reference/apps#webhooks)" in the REST API documentation.' + - | + Improvements have been made to the code scanning and {% data variables.product.prodname_GH_advanced_security %} APIs: + + - The code scanning API now returns the CodeQL query version used for an analysis. This can be used to reproduce results or confirm that an analysis used the latest query. For more information, see "[Code scanning](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository)" in the REST API documentation. + - Admin users can now use the REST API to enable or disable {% data variables.product.prodname_GH_advanced_security %} for repositories, using the `security_and_analysis` object on `repos/{org}/{repo}`. In addition, admin users can check whether {% data variables.product.prodname_advanced_security %} is currently enabled for a repository by using a `GET /repos/{owner}/{repo}` request. These changes help you manage {% data variables.product.prodname_advanced_security %} repository access at scale. For more information, see "[Repositories](/rest/reference/repos#update-a-repository)" in the REST API documentation. + #No security/bug fixes for the RC release + #security_fixes: + #- PLACEHOLDER + #bugs: + #- PLACEHOLDER + known_issues: + - 在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。 + - 自定义防火墙规则在升级过程中被删除。 + - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。 + - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。 + - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，私有和内部仓库中的议题不包括在 GitHub.com 搜索结果中。 + - '{% data variables.product.prodname_registry %} npm 注册表不再返回元数据响应的时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。' + - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. + deprecations: + - + heading: 弃用 GitHub Enterprise Server 2.21 + notes: + - '**{% data variables.product.prodname_ghe_server %} 2.21 was discontinued on June 6, 2021**. That 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.2/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' + - + heading: Deprecation of GitHub Enterprise Server 2.22 + notes: + - '**{% data variables.product.prodname_ghe_server %} 2.22 will be discontinued on September 23, 2021**. That 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.2/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' + - + heading: XenServer Hypervisor 支持终止 + notes: + - Beginning in {% data variables.product.prodname_ghe_server %} 3.1, we will begin discontinuing support for Xen Hypervisor. The complete deprecation is scheduled for {% data variables.product.prodname_ghe_server %} 3.3, following the standard one year deprecation window. Please contact [GitHub Support](https://enterprise.githubsupport.com/hc/en-us/signin) with questions or concerns. + - + heading: Removal of Legacy GitHub Services + notes: + - '{% data variables.product.prodname_ghe_server %} 3.2 removes unused GitHub Service database records. More information is available in the [deprecation announcement post](https://developer.github.com/changes/2018-04-25-github-services-deprecation/).' + - + heading: Deprecation of OAuth Application API endpoints and API authentication via query parameters + notes: + - | + To prevent accidental logging or exposure of `access_tokens`, we discourage the use of OAuth Application API endpoints and the use of API auth via query params. Visit the following posts to see the proposed replacements: + + * [Replacement OAuth Application API endpoints](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#changes-to-make) + * [Replacement auth via headers instead of query param](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make) + + These endpoints and auth route are planned to be removed from {% data variables.product.prodname_ghe_server %} in {% data variables.product.prodname_ghe_server %} 3.4. + - + heading: Removal of legacy GitHub App webhook events and endpoints + notes: + - | + Two legacy GitHub Apps-related webhook events have been removed: `integration_installation` and `integration_installation_repositories`. You should instead be listening to the `installation` and `installation_repositories` events. + - | + The following REST API endpoint has been removed: `POST /installations/{installation_id}/access_tokens`. You should instead be using the namespaced equivalent `POST /app/installations/{installation_id}/access_tokens`. + backups: + - '{% data variables.product.prodname_ghe_server %} 3.2 requires at least [GitHub Enterprise Backup Utilities 3.2.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/enterprise-server@3.2/admin/configuration/configuring-backups-on-your-appliance).' diff --git a/translations/zh-CN/data/reusables/actions/about-environments.md b/translations/zh-CN/data/reusables/actions/about-environments.md new file mode 100644 index 0000000000..ab9cfa899f --- /dev/null +++ b/translations/zh-CN/data/reusables/actions/about-environments.md @@ -0,0 +1 @@ +Environments are used to describe a general deployment target like `production`, `staging`, or `development`. When a {% data variables.product.prodname_actions %} workflow deploys to an environment, the environment is displayed on the main page of the repository. You can use environments to require approval for a job to proceed, restrict which branches can trigger a workflow, or limit access to secrets. For more information about creating environments, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/actions/actions-group-concurrency.md b/translations/zh-CN/data/reusables/actions/actions-group-concurrency.md index f8703279b2..2575f47952 100644 --- a/translations/zh-CN/data/reusables/actions/actions-group-concurrency.md +++ b/translations/zh-CN/data/reusables/actions/actions-group-concurrency.md @@ -1,6 +1,6 @@ 当并发作业或工作流程排队时，如果仓库中使用同一并发组的其他作业或工作流程正在运行，则排队的作业或工作流程将 `pending`。 在并发组中任何先前挂起的作业或工作流程都将被取消。 如果还要取消同一并发组中任何当前运行的作业或工作流程，请指定 `cancel-in-progress: true`。 -### 示例：使用并发和默认行为 +## 示例：使用并发和默认行为 {% raw %} ```yaml @@ -14,7 +14,7 @@ concurrency: ci-${{ github.ref }} ``` {% endraw %} -### 示例：使用并发取消任何当前作业或运行 +## 示例：使用并发取消任何当前作业或运行 {% raw %} ```yaml diff --git a/translations/zh-CN/data/reusables/actions/ae-hosted-runners-beta.md b/translations/zh-CN/data/reusables/actions/ae-hosted-runners-beta.md new file mode 100644 index 0000000000..804f22a849 --- /dev/null +++ b/translations/zh-CN/data/reusables/actions/ae-hosted-runners-beta.md @@ -0,0 +1,7 @@ +{% ifversion ghae %} +{% note %} + +**Note:** {% data variables.actions.hosted_runner %}s are currently in beta and subject to change. + +{% endnote %} +{% endif %} diff --git a/translations/zh-CN/data/reusables/actions/ae-self-hosted-runners-notice.md b/translations/zh-CN/data/reusables/actions/ae-self-hosted-runners-notice.md index e94e4ff4d1..b77aaae0a8 100644 --- a/translations/zh-CN/data/reusables/actions/ae-self-hosted-runners-notice.md +++ b/translations/zh-CN/data/reusables/actions/ae-self-hosted-runners-notice.md @@ -1,9 +1,19 @@ {% ifversion ghae %} + {% warning %} -** 警告：** 自托管运行器目前对 {% data variables.product.prodname_ghe_managed %} 禁用。 这是因为 {% data variables.product.prodname_ghe_managed %} 为安全边界提供了不符合自托管运行器工作方式的保证。 但是，如果您确实需要使用具有 {% data variables.product.prodname_ghe_managed %} 的自托管运行器并了解安全的意义，可以联系 {% data variables.product.prodname_dotcom %} 支持以了解将会启用自托管运行器的安全异常。 +{% ifversion ghae-next %} + +**Warning:** Self-hosted runners are enabled by default for {% data variables.product.prodname_ghe_managed %}. Self-hosted runners are long-lived, and any compromise to the host machine could leak secrets or credentials or enable other attacks. If you'd like to disable self-hosted runners for your enterprise, you can contact {% data variables.product.prodname_dotcom %} support. For more information about the risks of using self-hosted runners, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/security-hardening-for-github-actions#potential-impact-of-a-compromised-runner)." + +{% elsif ghae %} + +**Warning:** Self-hosted runners are currently disabled for {% data variables.product.prodname_ghe_managed %}. 这是因为 {% data variables.product.prodname_ghe_managed %} 为安全边界提供了不符合自托管运行器工作方式的保证。 但是，如果您确实需要使用具有 {% data variables.product.prodname_ghe_managed %} 的自托管运行器并了解安全的意义，可以联系 {% data variables.product.prodname_dotcom %} 支持以了解将会启用自托管运行器的安全异常。 如果您不需要自托管的运行器，则可使用 {% data variables.actions.hosted_runner %} 来运行您的工作流程。 更多信息请参阅“[关于 {% data variables.actions.hosted_runner %}](/actions/using-github-hosted-runners/about-ae-hosted-runners)”。 -{% endwarning %} +{% endif %} + +{% endwarning %} + {% endif %} 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 062c58d759..8ed9c6b244 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 @@ -1,7 +1,7 @@ 选择 **Allow select actions（允许选择操作）**时，允许本地操作，并且还有允许其他特定操作的其他选项。 -- **允许 {% data variables.product.prodname_dotcom %} 创建的操作：** 您可以允许 {% data variables.product.prodname_dotcom %} 创建的所有操作用于工作流程。 {% data variables.product.prodname_dotcom %} 创建的操作位于 `actions` 和 `github` 组织中。 For more information, see the [`actions`](https://github.com/actions) and [`github`](https://github.com/github) organizations.{% ifversion fpt or ghes > 3.0 %} -- **Allow Marketplace actions by verified creators:** {% ifversion ghes > 3.0 %}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 %} +- **允许 {% data variables.product.prodname_dotcom %} 创建的操作：** 您可以允许 {% data variables.product.prodname_dotcom %} 创建的所有操作用于工作流程。 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 > 3.0 or ghae-issue-5094 %} +- **Allow Marketplace actions by verified creators:** {% ifversion ghes > 3.0 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 specified actions（允许指定的操作）：**您可以限制工作流程使用特定组织和仓库中的操作。 要限制对操作中特定标记或提交 SHA 的访问，请使用工作流程中使用的 `/@` 语法来选择操作。 例如，使用 `actions/javascript-action@v1.0.1` 选择标记，或使用 `actions/javascript-action@172239021f7ba04fe7327647b213799853a9eb89` 选择 SHA。 更多信息请参阅“[查找和自定义操作](/actions/learn-github-actions/finding-and-customizing-actions#using-release-management-for-your-custom-actions)”。 diff --git a/translations/zh-CN/data/reusables/actions/autoscaling-parameters.md b/translations/zh-CN/data/reusables/actions/autoscaling-parameters.md new file mode 100644 index 0000000000..d9c4342b29 --- /dev/null +++ b/translations/zh-CN/data/reusables/actions/autoscaling-parameters.md @@ -0,0 +1,3 @@ +- Optionally, autoscaling parameters for each pool. + - Minimum number of idle runners for the pool + - Active timeout: The number of minutes that a runner should remain active in the pool before the pool is reduced to the idle count diff --git a/translations/zh-CN/data/reusables/actions/cd-templates-actions.md b/translations/zh-CN/data/reusables/actions/cd-templates-actions.md new file mode 100644 index 0000000000..c6eeec90db --- /dev/null +++ b/translations/zh-CN/data/reusables/actions/cd-templates-actions.md @@ -0,0 +1,3 @@ +{% data variables.product.product_name %} offers CD workflow templates for several popular services, such as Azure Web App. To learn how to get started using a workflow template, see "[Using workflow templates](/actions/learn-github-actions/using-workflow-templates)" or [browse the full list of deployment workflow templates](https://github.com/actions/starter-workflows/tree/main/deployments). You can also check out our more detailed guides for specific deployment workflows, such as "[Deploying to Azure App Service](/actions/deployment/deploying-to-azure-app-service)." + +Many service providers also offer actions on {% data variables.product.prodname_marketplace %} for deploying to their service. For the full list, see [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?category=deployment&type=actions). \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/actions/delete-env-key.md b/translations/zh-CN/data/reusables/actions/delete-env-key.md new file mode 100644 index 0000000000..380ebe5653 --- /dev/null +++ b/translations/zh-CN/data/reusables/actions/delete-env-key.md @@ -0,0 +1 @@ +If you configured a deployment environment, change the value of `environment` to be the name of your environment. If you did not configure an environment{% ifversion fpt %} or if your workflow is in a private repository and you do not use {% data variables.product.prodname_ghe_cloud %}{% endif %}, delete the `environment` key. \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/actions/environment-deployment-event.md b/translations/zh-CN/data/reusables/actions/environment-deployment-event.md new file mode 100644 index 0000000000..1a014fbfc6 --- /dev/null +++ b/translations/zh-CN/data/reusables/actions/environment-deployment-event.md @@ -0,0 +1 @@ +When a workflow job that references an environment runs, it creates a deployment object with the `environment` property set to the name of your environment. As the workflow progresses, it also creates deployment status objects with the `environment` property set to the name of your environment, the `environment_url` property set to the URL for environment (if specified in the workflow), and the `state` property set to the status of the job. \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/actions/environment-example.md b/translations/zh-CN/data/reusables/actions/environment-example.md new file mode 100644 index 0000000000..95ed6bc816 --- /dev/null +++ b/translations/zh-CN/data/reusables/actions/environment-example.md @@ -0,0 +1,45 @@ +You can specify an environment for each job in your workflow. To do so, add a `jobs..environment` key followed by the name of the environment. + +For example, this workflow will use an environment called `production`. + +```yaml +name: Deployment + +on: + push: + branches: + - main + +jobs: + deployment: + runs-on: ubuntu-latest + environment: production + steps: + - name: deploy + # ...deployment-specific steps +``` + +When the above workflow runs, the `deployment` job will be subject to any rules configured for the `production` environment. For example, if the environment requires reviewers, the job will pause until one of the reviewers approves the job. + +You can also specify a URL for the environment. The specified URL will appear on the deployments page for the repository (accessed by clicking **Environments** on the home page of your repository) and in the visualization graph for the workflow run. If a pull request triggered the workflow, the URL is also displayed as a **View deployment** button in the pull request timeline. + +```yaml +name: Deployment + +on: + push: + branches: + - main + +jobs: + deployment: + runs-on: ubuntu-latest + environment: + name: production + url: https://github.com + steps: + - name: deploy + # ...deployment-specific steps +``` + +![Workflow graph with URL](/assets/images/help/images/deploy-graph.png) \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/actions/reusable-workflow-artifacts.md b/translations/zh-CN/data/reusables/actions/reusable-workflow-artifacts.md new file mode 100644 index 0000000000..4f5210333f --- /dev/null +++ b/translations/zh-CN/data/reusables/actions/reusable-workflow-artifacts.md @@ -0,0 +1,3 @@ +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +All actions and workflows called within a run have write access to that run's artifacts. +{% endif %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/actions/reusable-workflows.md b/translations/zh-CN/data/reusables/actions/reusable-workflows.md new file mode 100644 index 0000000000..377f69ce32 --- /dev/null +++ b/translations/zh-CN/data/reusables/actions/reusable-workflows.md @@ -0,0 +1,5 @@ +{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 %} +## Reusing workflows + +You can call one workflow from within another workflow. This allows you to reuse workflows, avoiding duplication and making your workflows easier to maintain. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)." +{% endif %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/actions/runner-name-description.md b/translations/zh-CN/data/reusables/actions/runner-name-description.md new file mode 100644 index 0000000000..c3955e46ec --- /dev/null +++ b/translations/zh-CN/data/reusables/actions/runner-name-description.md @@ -0,0 +1 @@ +The name of the runner executing the job. diff --git a/translations/zh-CN/data/reusables/actions/uses-keyword-example.md b/translations/zh-CN/data/reusables/actions/uses-keyword-example.md new file mode 100644 index 0000000000..fac21c8a9f --- /dev/null +++ b/translations/zh-CN/data/reusables/actions/uses-keyword-example.md @@ -0,0 +1,7 @@ +```yaml +jobs: + call-workflow-1: + uses: octo-org/this-repo/.github/workflows/workflow-1.yml@172239021f7ba04fe7327647b213799853a9eb89 + call-workflow-2: + uses: octo-org/another-repo/.github/workflows/workflow-2.yml@v1 +``` \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/actions/workflow-organization-templates.md b/translations/zh-CN/data/reusables/actions/workflow-organization-templates.md new file mode 100644 index 0000000000..0c1911d3b2 --- /dev/null +++ b/translations/zh-CN/data/reusables/actions/workflow-organization-templates.md @@ -0,0 +1 @@ +Workflow templates allow everyone in your organization who has permission to create workflows to do so more quickly and easily. When you create a new workflow, you can choose a template and some or all of the work of writing the workflow will be done for you. 您可以使用工作流程模板作为基础来构建自定义工作流程，或按原样使用模板。 This not only saves time, it promotes consistency and best practice across your organization. \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/actions/workflow-run-approve-public-fork.md b/translations/zh-CN/data/reusables/actions/workflow-run-approve-public-fork.md index 922b771bb9..d445080057 100644 --- a/translations/zh-CN/data/reusables/actions/workflow-run-approve-public-fork.md +++ b/translations/zh-CN/data/reusables/actions/workflow-run-approve-public-fork.md @@ -1,3 +1,9 @@ 任何人都可以复刻公共仓库，然后提交建议更改仓库 {% data variables.product.prodname_actions %} 工作流程的拉取请求。 虽然来自复刻的工作流程无法访问敏感数据（如密钥），但如果出于滥用目的进行修改，可能会让维护者感到烦恼。 为了帮助防止这种情况，某些外部贡献者向公共仓库提出的关于拉取请求的工作流程不会自动运行，可能需要先批准。 默认情况下，所有首次贡献者都需要批准才能运行工作流程。 + +{% note %} + +**Note:** Workflows triggered by `pull_request_target` events are run in the context of the base branch. Since the base branch is considered trusted, workflows triggered by these events will always run, regardless of approval settings. + +{% endnote %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/apps/oauth-auth-vary-response.md b/translations/zh-CN/data/reusables/apps/oauth-auth-vary-response.md new file mode 100644 index 0000000000..b76fef614b --- /dev/null +++ b/translations/zh-CN/data/reusables/apps/oauth-auth-vary-response.md @@ -0,0 +1 @@ +You can also receive the response in different formats if you provide the format in the `Accept` header. For example, `Accept: application/json` or `Accept: application/xml`: diff --git a/translations/zh-CN/data/reusables/code-scanning/upload-sarif-alert-limit.md b/translations/zh-CN/data/reusables/code-scanning/upload-sarif-alert-limit.md index 5142d1fd6c..2f5da246f9 100644 --- a/translations/zh-CN/data/reusables/code-scanning/upload-sarif-alert-limit.md +++ b/translations/zh-CN/data/reusables/code-scanning/upload-sarif-alert-limit.md @@ -1,5 +1,8 @@ {% note %} -**注：**SARIF 上传支持每次上传最多 {% ifversion ghae-next or fpt or ghes > 3.0 %}5000{% else %}1000{% endif %} 个结果。 超过此限制的任何结果均被忽略。 如果工具产生太多结果，则应更新配置，以专注于最重要的规则或查询的结果。 +**注意：** +- SARIF upload supports a maximum of {% ifversion ghae-next or fpt or ghes > 3.0 %}5000{% else %}1000{% endif %} results per upload. 超过此限制的任何结果均被忽略。 如果工具产生太多结果，则应更新配置，以专注于最重要的规则或查询的结果。 + + - For each upload, SARIF upload supports a maximum size of 10 MB for the `gzip`-compressed SARIF file. Any uploads over this limit will be rejected. If your SARIF file is too large because it contains too many results, you should update the configuration to focus on results for the most important rules or queries. {% endnote %} diff --git a/translations/zh-CN/data/reusables/codespaces/create-or-switch-branch.md b/translations/zh-CN/data/reusables/codespaces/create-or-switch-branch.md new file mode 100644 index 0000000000..45e745a7cd --- /dev/null +++ b/translations/zh-CN/data/reusables/codespaces/create-or-switch-branch.md @@ -0,0 +1,3 @@ +1. 如果当前分支未显示在状态栏中，请在代码空间的底部右键单击状态栏，然后选择 **Source control（源控制）**。 +1. 单击状态栏中的分支名称。 ![状态栏中的分支](/assets/images/help/codespaces/branch-in-status-bar.png) +1. 在下拉菜单中，单击要切换到的分支或输入新分支的名称，然后单击 **Create new branch（创建新分支）**。 ![从分支菜单中选择](/assets/images/help/codespaces/create-new-branch.png) \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/codespaces/source-control-commit-changes.md b/translations/zh-CN/data/reusables/codespaces/source-control-commit-changes.md new file mode 100644 index 0000000000..e726a530ff --- /dev/null +++ b/translations/zh-CN/data/reusables/codespaces/source-control-commit-changes.md @@ -0,0 +1,4 @@ +{% data reusables.codespaces.source-control-display-dark %} +1. 要暂存更改，请单击已更改文件旁边的 **+**；如果您更改了多个文件并且要全部暂存，请单击 **Changes（更改）**旁边的该按钮。 ![高亮显示暂存按钮的源控制侧边栏](/assets/images/help/codespaces/codespaces-commit-stage.png) +1. 输入提交消息，描述您所做的更改。 ![带有提交消息的源控制侧栏](/assets/images/help/codespaces/codespaces-commit-commit-message.png) +1. 要提交暂存的更改，请单击源控制侧栏顶部的复选标记。 ![单击复选标记图标](/assets/images/help/codespaces/codespaces-commit-checkmark-icon.png) \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/codespaces/source-control-pull-request.md b/translations/zh-CN/data/reusables/codespaces/source-control-pull-request.md new file mode 100644 index 0000000000..61e9b5e152 --- /dev/null +++ b/translations/zh-CN/data/reusables/codespaces/source-control-pull-request.md @@ -0,0 +1,3 @@ +1. 将更改提交到仓库的本地副本后，请单击 **Create Pull Request（创建拉取请求）**图标。 ![高亮显示暂存按钮的源控制侧边栏](/assets/images/help/codespaces/codespaces-commit-pr-button.png) +1. 检查作为合并来源的本地分支和仓库以及作为合并目标的远程分支和仓库是否正确。 然后为拉取请求提供标题和描述。 ![高亮显示暂存按钮的源控制侧边栏](/assets/images/help/codespaces/codespaces-commit-pr.png) +1. 单击 **Create（创建）**。 \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/dependabot/supported-package-managers.md b/translations/zh-CN/data/reusables/dependabot/supported-package-managers.md index febfdd8726..48f013d7d3 100644 --- a/translations/zh-CN/data/reusables/dependabot/supported-package-managers.md +++ b/translations/zh-CN/data/reusables/dependabot/supported-package-managers.md @@ -26,7 +26,7 @@ | Terraform | `terraform` | >= 0.13, <= 1.0 | **✓** | **✓** | | | yarn | `npm` | v1 | **✓** | **✓** | | -[1] {% data variables.product.prodname_dependabot %} 不运行 Gradle，但支持更新以下文件：`build.gradle` 和 `build.gradle.kts`（用于 Kotlin 项目）。 +[1] {% data variables.product.prodname_dependabot %} doesn't run Gradle but supports updates to the following files: `build.gradle`, `build.gradle.kts` (for Kotlin projects), and files included via the `apply` declaration that have `dependencies` in the filename. Note that `apply` does not support `apply to`, recursion, or advanced syntaxes (for example, Kotlin's `apply` with `mapOf`, filenames defined by property). [2] {% data variables.product.prodname_dependabot %} 不运行 Maven ，但支持更新 `pom.xml` 文件。 diff --git a/translations/zh-CN/data/reusables/dependency-review/beta.md b/translations/zh-CN/data/reusables/dependency-review/beta.md index bf8b66ab64..5d359c07d9 100644 --- a/translations/zh-CN/data/reusables/dependency-review/beta.md +++ b/translations/zh-CN/data/reusables/dependency-review/beta.md @@ -1,7 +1,8 @@ -{% ifversion fpt or ghes > 3.1 %} +{% ifversion ghes > 3.1 %} {% note %} **注意：**依赖项审查目前处于测试阶段，可能会更改。 {% endnote %} + {% endif %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/developer-site/pull_request_forked_repos_link.md b/translations/zh-CN/data/reusables/developer-site/pull_request_forked_repos_link.md index a9cecc47b8..16df777a89 100644 --- a/translations/zh-CN/data/reusables/developer-site/pull_request_forked_repos_link.md +++ b/translations/zh-CN/data/reusables/developer-site/pull_request_forked_repos_link.md @@ -1,4 +1,4 @@ -#### 复刻的仓库的拉取请求事件 +### 复刻的仓库的拉取请求事件 {% note %} diff --git a/translations/zh-CN/data/reusables/dotcom_billing/pricing_cal.md b/translations/zh-CN/data/reusables/dotcom_billing/pricing_cal.md new file mode 100644 index 0000000000..6509379b28 --- /dev/null +++ b/translations/zh-CN/data/reusables/dotcom_billing/pricing_cal.md @@ -0,0 +1 @@ +To estimate the costs for consumptive services, you can use the {% data variables.product.prodname_dotcom %} pricing calculator. For more information, go to https://github.com/pricing/calculator. diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/about-enterprise-accounts.md b/translations/zh-CN/data/reusables/enterprise-accounts/about-enterprise-accounts.md index f7745b4ce9..f37350a706 100644 --- a/translations/zh-CN/data/reusables/enterprise-accounts/about-enterprise-accounts.md +++ b/translations/zh-CN/data/reusables/enterprise-accounts/about-enterprise-accounts.md @@ -14,7 +14,7 @@ Organizations are shared accounts where enterprise members can collaborate acros {% ifversion fpt %} -Enterprise owners can create organizations and link the organizations to the enterprise. After you add organizations to your enterprise account, you can manage and enforce policies for the organizations. 具体实施选项因设置而异；一般而言，您可以选择对企业帐户中的每个组织实施一种策略，或者让所有者在组织层级设置策略。 For more information, see "[Setting policies for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account)." +Enterprise owners can create organizations and link the organizations to the enterprise. Alternatively, you can invite an existing organization to join your enterprise. After you add organizations to your enterprise account, you can manage and enforce policies for the organizations. 具体实施选项因设置而异；一般而言，您可以选择对企业帐户中的每个组织实施一种策略，或者让所有者在组织层级设置策略。 For more information, see "[Setting policies for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account)." {% elsif ghes or ghae %} @@ -58,6 +58,14 @@ You can also connect the enterprise account on {% data variables.product.product {% endif %} +{% ifversion fpt %} + +## 关于 {% data variables.product.prodname_emus %} + +{% data reusables.enterprise-accounts.emu-short-summary %} + +{% endif %} + ## About billing for your enterprise account The bill for your enterprise account includes the monthly cost for each member of your enterprise. The bill includes {% ifversion fpt %}any paid licenses in organizations outside of your enterprise account, subscriptions to apps in {% data variables.product.prodname_marketplace %}, {% endif %}{% ifversion fpt or ghae %}additional paid services for your enterprise{% ifversion fpt %} like data packs for {% data variables.large_files.product_name_long %},{% endif %} and{% endif %} usage for {% data variables.product.prodname_GH_advanced_security %}. diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/access-enterprise.md b/translations/zh-CN/data/reusables/enterprise-accounts/access-enterprise.md index 5f116cb1dc..0a4079b315 100644 --- a/translations/zh-CN/data/reusables/enterprise-accounts/access-enterprise.md +++ b/translations/zh-CN/data/reusables/enterprise-accounts/access-enterprise.md @@ -5,5 +5,4 @@ {% elsif ghes or ghae %}1. 在 {% data variables.product.product_name %} 的右上角，单击您的个人资料照片，然后单击 **Enterprise settings（Enterprise 设置）**。 ![{% data variables.product.product_name %} 上个人资料照片下拉菜单中的"Enterprise settings（企业设置）"](/assets/images/enterprise/settings/enterprise-settings.png) - {% endif %} diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/actions-runners-tab.md b/translations/zh-CN/data/reusables/enterprise-accounts/actions-runners-tab.md index 592acea0d1..aa0c76aefe 100644 --- a/translations/zh-CN/data/reusables/enterprise-accounts/actions-runners-tab.md +++ b/translations/zh-CN/data/reusables/enterprise-accounts/actions-runners-tab.md @@ -1 +1 @@ -1. 单击 {% ifversion fpt %}**Runners**{% else %}**自托管运行器**{% endif %} 选项卡。 +1. 单击 {% ifversion fpt or ghes > 3.1 or ghae-next %}**Runners**{% else %}**自托管运行器**{% endif %} 选项卡。 diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/emu-forks.md b/translations/zh-CN/data/reusables/enterprise-accounts/emu-forks.md new file mode 100644 index 0000000000..315ee2736f --- /dev/null +++ b/translations/zh-CN/data/reusables/enterprise-accounts/emu-forks.md @@ -0,0 +1 @@ +{% data variables.product.prodname_managed_users_caps %} cannot fork repositories from outside of the enterprise or fork internal repositories. {% data variables.product.prodname_managed_users_caps %} can fork private repositories owned by organizations in the enterprise into other organizations owned by the enterprise, or as a fork owned by the {% data variables.product.prodname_managed_user %}. \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/emu-more-info-account.md b/translations/zh-CN/data/reusables/enterprise-accounts/emu-more-info-account.md new file mode 100644 index 0000000000..21302799fb --- /dev/null +++ b/translations/zh-CN/data/reusables/enterprise-accounts/emu-more-info-account.md @@ -0,0 +1 @@ +For more information, see "[Types of GitHub accounts](/get-started/learning-about-github/types-of-github-accounts#enterprise-managed-users)." \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/emu-password-reset-session.md b/translations/zh-CN/data/reusables/enterprise-accounts/emu-password-reset-session.md new file mode 100644 index 0000000000..65ed74cc65 --- /dev/null +++ b/translations/zh-CN/data/reusables/enterprise-accounts/emu-password-reset-session.md @@ -0,0 +1 @@ +If you need to reset the password for your setup user, use an incognito or private browsing window to request a new password. When the email arrives with the link to reset your password, copy the link into your browser. For more information on resetting your password, see "[Requesting a new password ](/github/authenticating-to-github/keeping-your-account-and-data-secure/updating-your-github-access-credentials#requesting-a-new-password)." \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-follow.md b/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-follow.md new file mode 100644 index 0000000000..f166721634 --- /dev/null +++ b/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-follow.md @@ -0,0 +1 @@ +{% ifversion fpt %} Members of an {% data variables.product.prodname_emu_enterprise %} can only follow other members of their enterprise. {% endif %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-fork.md b/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-fork.md new file mode 100644 index 0000000000..411dfeed7b --- /dev/null +++ b/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-fork.md @@ -0,0 +1 @@ +{% ifversion fpt %}Members of an {% data variables.product.prodname_emu_enterprise %} cannot fork repositories from outside of the enterprise or fork internal repositories.{% endif %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-gist.md b/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-gist.md new file mode 100644 index 0000000000..3164ea3434 --- /dev/null +++ b/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-gist.md @@ -0,0 +1 @@ +{% ifversion fpt %}Members of an {% data variables.product.prodname_emu_enterprise %} cannot create gists and have read-only access to gists.{% endif %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-interact.md b/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-interact.md new file mode 100644 index 0000000000..9bdeac19e8 --- /dev/null +++ b/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-interact.md @@ -0,0 +1 @@ +{% ifversion fpt %} Members of an {% data variables.product.prodname_emu_enterprise %} can only interact with repositories within their enterprise. {% endif %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-propose.md b/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-propose.md new file mode 100644 index 0000000000..85fd4f66e3 --- /dev/null +++ b/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-propose.md @@ -0,0 +1 @@ +{% ifversion fpt %} Members of an {% data variables.product.prodname_emu_enterprise %} can only propose changes in repositories that are part of their enterprise. {% endif %} diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-repo.md b/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-repo.md new file mode 100644 index 0000000000..b4278362a5 --- /dev/null +++ b/translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-repo.md @@ -0,0 +1 @@ +{% ifversion fpt %} Members of an {% data variables.product.prodname_emu_enterprise %} can only make changes in repositories that are part of their enterprise. {% endif %} diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/emu-saml-note.md b/translations/zh-CN/data/reusables/enterprise-accounts/emu-saml-note.md new file mode 100644 index 0000000000..2a5bdae038 --- /dev/null +++ b/translations/zh-CN/data/reusables/enterprise-accounts/emu-saml-note.md @@ -0,0 +1,7 @@ +{% ifversion fpt%} +{% note %} + +**Note**: If your enterprise uses {% data variables.product.prodname_emus %}, you must follow a different process to configure SAML single sign-on. For more information, see "[Configuring SAML single sign-on for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." + +{% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/emu-scim-note.md b/translations/zh-CN/data/reusables/enterprise-accounts/emu-scim-note.md new file mode 100644 index 0000000000..309ec9adfb --- /dev/null +++ b/translations/zh-CN/data/reusables/enterprise-accounts/emu-scim-note.md @@ -0,0 +1,7 @@ +{% ifversion fpt%} +{% note %} + +**Note**: If your enterprise uses {% data variables.product.prodname_emus %}, you cannot use team synchronization and must instead configure SCIM to manage membership with your identity provider. For more information, see "[Configuring SCIM provisioning for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users)." + +{% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/emu-short-summary.md b/translations/zh-CN/data/reusables/enterprise-accounts/emu-short-summary.md new file mode 100644 index 0000000000..7e4f69fff9 --- /dev/null +++ b/translations/zh-CN/data/reusables/enterprise-accounts/emu-short-summary.md @@ -0,0 +1 @@ +{% data variables.product.prodname_emus %} is a feature of {% data variables.product.prodname_ghe_cloud %} that provides even greater control over enterprise members and resources. With {% data variables.product.prodname_emus %}, all members are provisioned and managed through your identity provider (IdP) instead of users creating their own accounts on {% data variables.product.product_name %}. Team membership can be managed using groups on your IdP. {% data variables.product.prodname_managed_users_caps %} are restricted to their enterprise and are unable to push code, collaborate, or interact with users, repositories, and organizations outside of their enterprise. For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/emu-shortcode.md b/translations/zh-CN/data/reusables/enterprise-accounts/emu-shortcode.md new file mode 100644 index 0000000000..ec695c807d --- /dev/null +++ b/translations/zh-CN/data/reusables/enterprise-accounts/emu-shortcode.md @@ -0,0 +1 @@ +The short code must be unique to your enterprise, a three-to-eight character alphanumeric string, and contain no special characters. \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/emu-supported-idps.md b/translations/zh-CN/data/reusables/enterprise-accounts/emu-supported-idps.md new file mode 100644 index 0000000000..375040efa3 --- /dev/null +++ b/translations/zh-CN/data/reusables/enterprise-accounts/emu-supported-idps.md @@ -0,0 +1,2 @@ +* Azure Active Directory (Azure AD) +* Okta \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/github-connect-tab.md b/translations/zh-CN/data/reusables/enterprise-accounts/github-connect-tab.md index bce3df8194..848c15910e 100644 --- a/translations/zh-CN/data/reusables/enterprise-accounts/github-connect-tab.md +++ b/translations/zh-CN/data/reusables/enterprise-accounts/github-connect-tab.md @@ -1,3 +1,3 @@ {% ifversion ghes < 3.1 %} 1. 在左侧边栏中，单击 **{% data variables.product.prodname_github_connect %}**。 ![GitHub Connect tab in the business account settings sidebar](/assets/images/enterprise/business-accounts/settings-github-connect-tab.png){% else %} -1. In the enterprise account sidebar, click {% octicon "plug" aria-label="The GitHub Connect gear" %} **{% data variables.product.prodname_github_connect %}**. ![GitHub Connect tab in the enterprise account sidebar](/assets/images/help//business-accounts/enterprise-account-github-connect-tab.png){% endif %} \ No newline at end of file +1. In the enterprise account sidebar, click {% octicon "plug" aria-label="The GitHub Connect gear" %} **{% data variables.product.prodname_github_connect %}**. ![GitHub Connect tab in the enterprise account sidebar](/assets/images/help//business-accounts/enterprise-account-github-connect-tab.png){% endif %} diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/identity-provider-tab.md b/translations/zh-CN/data/reusables/enterprise-accounts/identity-provider-tab.md new file mode 100644 index 0000000000..9e94eecb59 --- /dev/null +++ b/translations/zh-CN/data/reusables/enterprise-accounts/identity-provider-tab.md @@ -0,0 +1 @@ +1. Under your business account's name, click {% octicon "key" aria-label="The key icon" %} **Identity provider**. !["Identity provider" tab in enterprise sidebar](/assets/images/help/enterprises/enterprise-account-identity-provider-tab.png) \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/invite-organization.md b/translations/zh-CN/data/reusables/enterprise-accounts/invite-organization.md new file mode 100644 index 0000000000..1d5c99c11e --- /dev/null +++ b/translations/zh-CN/data/reusables/enterprise-accounts/invite-organization.md @@ -0,0 +1 @@ +Enterprise account owners and administrators can invite existing organization accounts to join their enterprise. For more information, see "[Inviting an organization to join your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account#inviting-an-organization-to-join-your-enterprise-account)" diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/team-sync-override.md b/translations/zh-CN/data/reusables/enterprise-accounts/team-sync-override.md new file mode 100644 index 0000000000..a39283eed0 --- /dev/null +++ b/translations/zh-CN/data/reusables/enterprise-accounts/team-sync-override.md @@ -0,0 +1 @@ +If your organization is owned by an enterprise account, enabling team synchronization or SCIM provisioning for the enterprise account will override your organization-level team synchronization settings. For more information, see "[Managing team synchronization for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account)" and "[Configuring SCIM provisioning for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users)." \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/enterprise_clustering/proxy_protocol_ports.md b/translations/zh-CN/data/reusables/enterprise_clustering/proxy_protocol_ports.md index 901d4b5cf9..cca7bd8792 100644 --- a/translations/zh-CN/data/reusables/enterprise_clustering/proxy_protocol_ports.md +++ b/translations/zh-CN/data/reusables/enterprise_clustering/proxy_protocol_ports.md @@ -1,4 +1,4 @@ -#### PROXY 协议 TCP 端口映射 +### PROXY 协议 TCP 端口映射 | 源端口 | 目标端口 | 服务描述 | |:----:|:----:|:------------------------:| diff --git a/translations/zh-CN/data/reusables/enterprise_clustering/without_proxy_protocol_ports.md b/translations/zh-CN/data/reusables/enterprise_clustering/without_proxy_protocol_ports.md index 12af21aef1..5a0c59d512 100644 --- a/translations/zh-CN/data/reusables/enterprise_clustering/without_proxy_protocol_ports.md +++ b/translations/zh-CN/data/reusables/enterprise_clustering/without_proxy_protocol_ports.md @@ -1,4 +1,4 @@ -#### 协议 TCP 端口映射，无需 PROXY 支持即可使用 +### 协议 TCP 端口映射，无需 PROXY 支持即可使用 | 源端口 | 目标端口 | 服务描述 | |:----:|:----:|:------------------------:| diff --git a/translations/zh-CN/data/reusables/gated-features/emus.md b/translations/zh-CN/data/reusables/gated-features/emus.md new file mode 100644 index 0000000000..f9f25095ea --- /dev/null +++ b/translations/zh-CN/data/reusables/gated-features/emus.md @@ -0,0 +1 @@ +To manage users in your enterprise with your identity provider, your enterprise must be enabled for {% data variables.product.prodname_emus %}, which are available with {% data variables.product.prodname_ghe_cloud %}. For more information, see "[About {% data variables.product.prodname_emus %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/getting-started/enterprise-advanced-security.md b/translations/zh-CN/data/reusables/getting-started/enterprise-advanced-security.md new file mode 100644 index 0000000000..faffbe7d63 --- /dev/null +++ b/translations/zh-CN/data/reusables/getting-started/enterprise-advanced-security.md @@ -0,0 +1 @@ +If you have a GitHub Advanced Security license for your enterprise account, you can enforce policies to manage {% data variables.product.prodname_dotcom %} Advanced Security features for organizations owned by an enterprise account. For more information, see "[Enforcing policies for Advanced Security in your enterprise account](/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-policies-for-advanced-security-in-your-enterprise-account)." \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/github-actions/actions-on-examples.md b/translations/zh-CN/data/reusables/github-actions/actions-on-examples.md index 4c6d4c3a47..9819556eec 100644 --- a/translations/zh-CN/data/reusables/github-actions/actions-on-examples.md +++ b/translations/zh-CN/data/reusables/github-actions/actions-on-examples.md @@ -1,18 +1,18 @@ -### 示例：使用单一事件 +## 示例：使用单一事件 ```yaml # Triggered when code is pushed to any branch in a repository on: push ``` -### 示例：使用事件列表 +## 示例：使用事件列表 ```yaml # Triggers the workflow on push or pull request events on: [push, pull_request] ``` -### 示例：使用具有活动类型或配置的多个事件 +## 示例：使用具有活动类型或配置的多个事件 如果您需要为一个事件指定活动类型或配置，必须分别配置每个事件。 您必须为所有事件附加冒号 (`: diff --git a/translations/zh-CN/data/reusables/github-actions/disabling-github-actions.md b/translations/zh-CN/data/reusables/github-actions/disabling-github-actions.md index 927a9a0ed6..fde5192889 100644 --- a/translations/zh-CN/data/reusables/github-actions/disabling-github-actions.md +++ b/translations/zh-CN/data/reusables/github-actions/disabling-github-actions.md @@ -1 +1 @@ -默认情况下，{% ifversion ghes or ghae %}{% data variables.product.prodname_actions %} 在 {% data variables.product.product_location %} 上启用后，它{% elsif fpt %}{% data variables.product.prodname_actions %}{% endif %} 将在所有仓库和组织上启用。 您可以选择禁用 {% data variables.product.prodname_actions %} 或将其限制为私有操作，这意味着人们只能使用仓库中存在的操作。 +默认情况下，{% ifversion ghes or ghae %}{% data variables.product.prodname_actions %} 在 {% data variables.product.product_location %} 上启用后，它{% elsif fpt %}{% data variables.product.prodname_actions %}{% endif %} 将在所有仓库和组织上启用。 You can choose to disable {% data variables.product.prodname_actions %} or limit them to local actions only, which means that people can only use actions that exist in your repository. diff --git a/translations/zh-CN/data/reusables/github-actions/name-environment.md b/translations/zh-CN/data/reusables/github-actions/name-environment.md new file mode 100644 index 0000000000..1a25d1cfc4 --- /dev/null +++ b/translations/zh-CN/data/reusables/github-actions/name-environment.md @@ -0,0 +1 @@ +1. 为环境输入一个名称, 然后单击 **Configure environment（配置环境）**。 环境名称不区分大小写。 环境名称不能超过 255 个字符，且必须在仓库中唯一。 diff --git a/translations/zh-CN/data/reusables/github-actions/new-environment.md b/translations/zh-CN/data/reusables/github-actions/new-environment.md new file mode 100644 index 0000000000..d0b7b6a3fd --- /dev/null +++ b/translations/zh-CN/data/reusables/github-actions/new-environment.md @@ -0,0 +1 @@ +1. 单击 **New environment（新环境）**。 diff --git a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md b/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md index 5b0f75599c..4dd8c84dcb 100644 --- a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md +++ b/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-configure-runner-group-access.md @@ -1,6 +1,7 @@ -1. 在设置页面的 {% ifversion fpt %}“运行器”{% else %}“自托管运行器）”{% endif %} 部分，单击要配置的运行器组旁边的 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}，然后单击 **Edit name and [organization|repository] access（编辑名称和[组织|仓库] 权限）**。 ![管理仓库权限](/assets/images/help/settings/actions-runner-manage-permissions.png) +1. 在设置页面的 {% ifversion fpt or ghes > 3.1 or ghae-next %}“运行器”{% else %}“自托管运行器）”{% endif %} 部分，单击要配置的运行器组旁边的 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}，然后单击 **Edit name and [organization|repository] access（编辑名称和[组织|仓库] 权限）**。 ![管理仓库权限](/assets/images/help/settings/actions-runner-manage-permissions.png) 1. 修改策略选项，或更改运行器组名称。 + {% ifversion not ghae %} {% warning %} **警告** @@ -10,3 +11,4 @@ 更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)”。 {% endwarning %} + {% endif %} diff --git a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-list.md b/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-list.md index 2fa88dee88..65969b5b19 100644 --- a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-list.md +++ b/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-list.md @@ -1 +1 @@ - 1. 在{% ifversion fpt %}“运行器”{% else %}“自托管运行器”{% endif %} 下找到运行器列表。 + 1. 在{% ifversion fpt or ghes > 3.1 or ghae-next %}“运行器”{% else %}“自托管运行器”{% endif %} 下找到运行器列表。 diff --git a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md b/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md index d7b7c81175..085091ae5e 100644 --- a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md +++ b/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md @@ -6,5 +6,5 @@ 1. 在左边栏中，单击 **Enterprise overview（企业概览）**。 1. {% endif %} 在企业边栏中，单击 {% octicon "law" aria-label="The law icon" %} **Policies（政策）**。 1. 导航到 {% data variables.product.prodname_actions %} 设置： - * **在组织或仓库中**：点击左侧栏中的 **Actions**{% ifversion fpt %}，然后点击 **Runners（运行器）**{% endif %}。 - * {% ifversion fpt %}**如果使用企业帐户**{% elsif ghes or ghae %}**如果使用企业级运行器**{% endif %}：在“{% octicon "law" aria-label="The law icon" %} Policies（政策）”下单击 **Actions（操作）**{% ifversion fpt %}，然后单击 **Runners（运行器）**选项卡{% endif %}。 + * **在组织或仓库中**：点击左侧栏中的 **Actions**{% ifversion fpt or ghes > 3.1 or ghae-next %}，然后点击 **Runners（运行器）**{% endif %}。 + * {% ifversion fpt %}**如果使用企业帐户**{% elsif ghes or ghae %}**如果使用企业级运行器**{% endif %}：在“{% octicon "law" aria-label="The law icon" %} Policies（政策）”下单击 **Actions（操作）**{% ifversion fpt or ghes > 3.1 or ghae-next %}，然后单击 **Runners（运行器）**选项卡{% endif %}。 diff --git a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md b/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md index cda580d018..38971a4425 100644 --- a/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md +++ b/translations/zh-CN/data/reusables/github-actions/self-hosted-runner-removing-a-runner.md @@ -1,4 +1,4 @@ -1. 在 {% ifversion fpt %}“运行器”{% else %}“自托管运行器”{% endif %} 下，找到列表中的运行器。 如果您的运行器在一个组中，请单击 {% octicon "chevron-down" aria-label="The downwards chevron" %} 以展开列表。 +1. 在 {% ifversion fpt or ghes > 3.1 or ghae-next %}“运行器”{% else %}“自托管运行器”{% endif %} 下，找到列表中的运行器。 如果您的运行器在一个组中，请单击 {% octicon "chevron-down" aria-label="The downwards chevron" %} 以展开列表。 1. 单击要删除的运行器旁边的 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}，然后单击 **Remove（删除）**。 ![删除自托管运行器设置](/assets/images/help/settings/actions-runner-remove.png) diff --git a/translations/zh-CN/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md b/translations/zh-CN/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md index 8facf02d88..d51fdc01ef 100644 --- a/translations/zh-CN/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md +++ b/translations/zh-CN/data/reusables/github-actions/settings-sidebar-actions-runner-groups.md @@ -1,2 +1,2 @@ -1. 在左侧边栏中，单击 **Actions（操作）**。 -1. In the left sidebar, under "Actions", click **Runner groups**. +1. In the left sidebar, click **Actions**.{% ifversion fpt or ghes > 3.1 or ghae-next %} +1. In the left sidebar, under "Actions", click **Runner groups**.{% endif %} diff --git a/translations/zh-CN/data/reusables/github-actions/settings-sidebar-actions-runners.md b/translations/zh-CN/data/reusables/github-actions/settings-sidebar-actions-runners.md index b9b81c2a80..43d1c35374 100644 --- a/translations/zh-CN/data/reusables/github-actions/settings-sidebar-actions-runners.md +++ b/translations/zh-CN/data/reusables/github-actions/settings-sidebar-actions-runners.md @@ -1 +1 @@ -1. 在左侧边栏中，在左侧栏中，单击 **Actions**{% ifversion fpt %}，然后单击 **Runners（运行器）**{% endif %}。 +1. 在左侧边栏中，在左侧栏中，单击 **Actions**{% ifversion fpt or ghes > 3.1 or ghae-next %}，然后单击 **Runners（运行器）**{% endif %}。 diff --git a/translations/zh-CN/data/reusables/github-actions/supported-github-runners.md b/translations/zh-CN/data/reusables/github-actions/supported-github-runners.md index fedd68afb5..9e1bee7f3a 100644 --- a/translations/zh-CN/data/reusables/github-actions/supported-github-runners.md +++ b/translations/zh-CN/data/reusables/github-actions/supported-github-runners.md @@ -60,17 +60,6 @@ Ubuntu 18.04     - - - - -
    - 指定您检出并分析的 ref，以便结果可以匹配正确的代码。 对于分支，使用 refs/heads/BRANCH-NAME；对于拉取请求的头部提交，使用 refs/pulls/NUMBER/head；或者对于拉取请求的 {% data variables.product.product_name %} 生成的合并提交，使用 refs/pulls/NUMBER/merge。 + 指定您检出并分析的 ref，以便结果可以匹配正确的代码。 对于分支，使用 refs/heads/BRANCH-NAME；对于拉取请求的头部提交，使用 refs/pulls/NUMBER/head；或者对于拉取请求的 {% data variables.product.prodname_dotcom %} 生成的合并提交，使用 refs/pulls/NUMBER/merge。
    - 指定要加载的 SARIF 文件。{% ifversion ghes > 3.0 or ghae-next %} + 指定要加载的 SARIF 文件。{% ifversion ghes > 3.0 or ghae %}
    -Ubuntu 16.04[deprecated] - -ubuntu-16.04 - -Deprecated and limited to existing customers only. Migrate to Ubuntu 20.04. For more information, see the blog post. -
    macOS Big Sur 11 diff --git a/translations/zh-CN/data/reusables/github-connect/access-dotcom-and-enterprise.md b/translations/zh-CN/data/reusables/github-connect/access-dotcom-and-enterprise.md index f47994c12b..2f22dbfd74 100644 --- a/translations/zh-CN/data/reusables/github-connect/access-dotcom-and-enterprise.md +++ b/translations/zh-CN/data/reusables/github-connect/access-dotcom-and-enterprise.md @@ -1 +1 @@ -1. 登录到 {% data variables.product.product_location_enterprise %} 和 {% data variables.product.prodname_dotcom_the_website %}。 +1. Sign in to {% ifversion ghes %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_ghe_managed %}{% endif %} and {% data variables.product.prodname_dotcom_the_website %}. diff --git a/translations/zh-CN/data/reusables/github-connect/access-profile-settings.md b/translations/zh-CN/data/reusables/github-connect/access-profile-settings.md index 4af17862d0..0b5512bddf 100644 --- a/translations/zh-CN/data/reusables/github-connect/access-profile-settings.md +++ b/translations/zh-CN/data/reusables/github-connect/access-profile-settings.md @@ -1 +1 @@ -1. 在 {% data variables.product.product_location_enterprise %} 上任何页面的右上角，单击您的个人资料照片，然后单击**设置**。 ![用户栏中的 Settings 图标](/assets/images/help/settings/userbar-account-settings.png) +1. On {% ifversion ghes %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_ghe_managed %}{% endif %}, in the upper-right corner of any page, click your profile photo, then click **Settings**. ![用户栏中的 Settings 图标](/assets/images/help/settings/userbar-account-settings.png) diff --git a/translations/zh-CN/data/reusables/github-connect/authorize-connection.md b/translations/zh-CN/data/reusables/github-connect/authorize-connection.md index 554b8b8ba5..3f3f26a09f 100644 --- a/translations/zh-CN/data/reusables/github-connect/authorize-connection.md +++ b/translations/zh-CN/data/reusables/github-connect/authorize-connection.md @@ -1 +1,7 @@ -1. 查看 {% data variables.product.prodname_ghe_server %} 将从您的 {% data variables.product.prodname_dotcom_the_website %} 帐户访问的资源，然后单击 **Authorize（授权）**。 ![授权 GitHub Enterprise Server 与 GitHub.com 之间的连接](/assets/images/help/settings/authorize-ghe-to-connect-to-dotcom.png) +1. Review the resources that +{% data variables.product.product_name %} will access from your {% data variables.product.prodname_dotcom_the_website %} account, then click **Authorize**. +{% ifversion ghes %} + ![Authorize connection between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_dotcom_the_website %}](/assets/images/help/settings/authorize-ghe-to-connect-to-dotcom.png) +{% elsif ghae %} + ![Authorize connection between {% data variables.product.prodname_ghe_managed %} and {% data variables.product.prodname_dotcom_the_website %}](/assets/images/enterprise/github-ae/settings/authorize-ghae-to-connect-to-dotcom.png) +{% endif %} diff --git a/translations/zh-CN/data/reusables/github-connect/beta.md b/translations/zh-CN/data/reusables/github-connect/beta.md new file mode 100644 index 0000000000..991a98d3d6 --- /dev/null +++ b/translations/zh-CN/data/reusables/github-connect/beta.md @@ -0,0 +1,7 @@ +{% ifversion ghae-next %} +{% note %} + +**Note:** {% data variables.product.prodname_github_connect %} for {% data variables.product.product_name %} is currently in beta and subject to change. + +{% endnote %} +{% endif %} diff --git a/translations/zh-CN/data/reusables/github-connect/connect-dotcom-and-enterprise.md b/translations/zh-CN/data/reusables/github-connect/connect-dotcom-and-enterprise.md index ca3ceeb35f..0ae6fd7a2f 100644 --- a/translations/zh-CN/data/reusables/github-connect/connect-dotcom-and-enterprise.md +++ b/translations/zh-CN/data/reusables/github-connect/connect-dotcom-and-enterprise.md @@ -1 +1,6 @@ -1. 单击**连接 {% data variables.product.prodname_dotcom_the_website %}**。 ![从 GitHub Enterprise Server 设置连接到 GitHub.com](/assets/images/help/settings/github.com_end_user_connection.png) +1. 单击**连接 {% data variables.product.prodname_dotcom_the_website %}**。 +{% ifversion ghes %} + ![从 GitHub Enterprise Server 设置连接到 GitHub.com](/assets/images/help/settings/github.com_end_user_connection.png) +{% else %} + ![Connect to GitHub.com from GitHub AE settings](/assets/images/enterprise/github-ae/settings/github.com-end-user-connection.png) +{% endif %} diff --git a/translations/zh-CN/data/reusables/github-connect/send-contribution-counts-to-githubcom.md b/translations/zh-CN/data/reusables/github-connect/send-contribution-counts-to-githubcom.md new file mode 100644 index 0000000000..1bec933dad --- /dev/null +++ b/translations/zh-CN/data/reusables/github-connect/send-contribution-counts-to-githubcom.md @@ -0,0 +1 @@ +1. 在 Contributions（贡献）下，选择 **Send my contribution counts to {% data variables.product.prodname_dotcom_the_website %}（将我的贡献计数发送到 {% data variables.product.prodname_dotcom_the_website %}）**，然后单击 **Update contributions（更新贡献）**。 ![发送贡献复选框和更新贡献按钮](/assets/images/help/settings/send-and-update-contributions.png) diff --git a/translations/zh-CN/data/reusables/github-connect/sync-frequency.md b/translations/zh-CN/data/reusables/github-connect/sync-frequency.md index 9027b1d3e4..7f97626802 100644 --- a/translations/zh-CN/data/reusables/github-connect/sync-frequency.md +++ b/translations/zh-CN/data/reusables/github-connect/sync-frequency.md @@ -1 +1 @@ -{% data variables.product.prodname_ghe_server %} 每小时发送一次更新。 +{% data variables.product.product_name %} 每小时发送一次更新。 diff --git a/translations/zh-CN/data/reusables/notifications-v2/custom-notification-types.md b/translations/zh-CN/data/reusables/notifications-v2/custom-notification-types.md index 1e32f0c4d9..cf7e1f72e1 100644 --- a/translations/zh-CN/data/reusables/notifications-v2/custom-notification-types.md +++ b/translations/zh-CN/data/reusables/notifications-v2/custom-notification-types.md @@ -1,2 +1,2 @@ {%- ifversion fpt or ghes > 3.1 or ghae-issue-4910 %}议题、拉取请求、发行版、安全警报或讨论{% endif %} -{%- ifversion ghes = 3.1 or ghae-next %}议题、拉取请求、发行版或讨论{% endif %} +{%- ifversion ghes = 3.1 %}议题、拉取请求、发行版或讨论{% 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 d3e50c0e62..d8e9c11af1 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,33 +1,34 @@ -{% if currentVersion == "free-pro-team@latest" %} -默认情况下，您将收到新 -{% data variables.product.prodname_dependabot_alerts %} 的通知： -- 通过电子邮件收到通知， 每次发现关键或严重性高的漏洞时都会发送电子邮件（**每次发现漏洞时发送电子邮件**选项） -- 在用户界面中接收通知，如有任何漏洞依赖项，将在仓库的文件和代码视图中显示警告（**UI 警报**选项） -- 在命令行上接收通知，当您推送到具有任何漏洞依赖项的仓库时，警告将显示为回叫（**命令行**选项） -- 在收件箱中收到通知，关键或严重性高的新漏洞会显示 Web 通知（**Web** 选项） +{% ifversion fpt or ghes > 3.1 %} +{% ifversion fpt %}默认情况下，您将收到通知：{% endif %}{% ifversion ghes > 3.1 %}默认情况下，如果您的站点管理员在您的实例上配置了通知电子邮件，您将收到 {% data variables.product.prodname_dependabot_alerts %}︰{% endif %} + +- 通过电子邮件，在为仓库启用 {% data variables.product.prodname_dependabot %} 时，当有新的清单文件提交到仓库，以及当发现具有关键或高严重性的新漏洞时，将发送一封电子邮件（**Email each time a vulnerability is found（每次找到漏洞时发送电子邮件）**选项）。 +- 在用户界面中接收通知，如有任何漏洞依赖项，将在仓库的文件和代码视图中显示警告（**UI 警报**选项）。 +- 在命令行上接收通知，当您推送到具有任何漏洞依赖项的仓库时，警告将显示为回叫（**命令行**选项）。 +- 在您的收件箱中，作为 web 通知。 为仓库启用 {% data variables.product.prodname_dependabot %} 时，当有新的清单文件提交到仓库，以及当发现具有关键或高严重性的新漏洞时，将发送 web 通知（**Web** 选项）。 +- 在 {% data variables.product.prodname_mobile %} 上，作为 web 通知。 更多信息请参阅“[为移动版 GitHub 启用推送通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-for-mobile)”。 + +{% note %} + +**注意：**电子邮件和 web/{% data variables.product.prodname_mobile %} 通知是： + +- _按仓库_ 在存储库中启用 {% data variables.product.prodname_dependabot %} 时，或者当新的清单文件提交到仓库时。 + +- _按组织_，当发现新的漏洞时。 + +{% endnote %} 您可以自定义您接收 {% data variables.product.prodname_dependabot_alerts %} 的通知。 例如，您可以使用 **Email a digest summary of vulnerabilities（以电子邮件发送漏洞摘要）**和 **Weekly security email digest（每周安全性电子邮件摘要）**选项通过电子邮件接收最多 10 个仓库的每周警报摘要。 {% endif %} -{% if enterpriseServerVersions contains currentVersion and currentVersion ver_gt "enterprise-server@2.21" %} +{% ifversion ghes = 2.22 or ghes = 3.0 or ghes = 3.1 %} 默认情况下，如果站点管理员配置了使用电子邮件接收实例通知，您将 {% data variables.product.prodname_dependabot_alerts %} 的通知： -- 通过电子邮件收到通知， 每次发现{% if currentVersion ver_gt "enterprise-server@2.23" %}关键或严重性{% endif %}高的漏洞时都会发送电子邮件（**每次发现漏洞时发送电子邮件**选项） +- 通过电子邮件收到通知， 每次发现{% ifversion ghes > 3.0 %}关键或严重性{% endif %}高的漏洞时都会发送电子邮件（**每次发现漏洞时发送电子邮件**选项） - 在用户界面中接收通知，如有任何漏洞依赖项，将在仓库的文件和代码视图中显示警告（**UI 警报**选项） - 在命令行上接收通知，当您推送到具有任何漏洞依赖项的仓库时，警告将显示为回叫（**命令行**选项） -- 在收件箱中收到通知，{% if currentVersion ver_gt "enterprise-server@2.23" %}关键或严重性高的新漏洞{% endif %}会显示 Web 通知（**Web** 选项） +- 在收件箱中收到通知，{% ifversion ghes > 3.0 %}关键或严重性高的新漏洞{% endif %}会显示 Web 通知（**Web** 选项） 您可以自定义您接收 {% data variables.product.prodname_dependabot_alerts %} 的通知。 例如，您可以使用 **Email a digest summary of vulnerabilities（以电子邮件发送漏洞摘要）**和 **Weekly security email digest（每周安全性电子邮件摘要）**选项通过电子邮件接收最多 10 个仓库的每周警报摘要。 {% endif %} - -{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.22" %} -默认情况下，如果站点管理员为您实例上的通知配置了电子邮件，您将收到安全警报： -- 通过电子邮件收到通知， 每次发现漏洞时都会发送电子邮件（**每次发现漏洞时发送电子邮件**选项） -- 在用户界面中，作为仓库文件和代码视图中的警告（**UI 警报**选项） -- 在命令行上接收通知，当您推送到具有漏洞的仓库时，警告将显示为回叫（**命令行**选项） -- 在收件箱中收到警报，作为 web 通知（**Web** 选项） - -您可以自定义接收安全警报通知的方式。 例如，您可以使用 **Email a digest summary of vulnerabilities（以电子邮件发送漏洞摘要）**和 **Weekly security email digest（每周安全性电子邮件摘要）**选项通过电子邮件接收最多 10 个仓库的每周警报摘要。 -{% endif %} diff --git a/translations/zh-CN/data/reusables/package_registry/docker_registry_deprecation_status.md b/translations/zh-CN/data/reusables/package_registry/docker_registry_deprecation_status.md index ef48e1de96..9fce2eb7c0 100644 --- a/translations/zh-CN/data/reusables/package_registry/docker_registry_deprecation_status.md +++ b/translations/zh-CN/data/reusables/package_registry/docker_registry_deprecation_status.md @@ -1,5 +1,5 @@ {% warning %} -**注：**{% data variables.product.prodname_registry %} Docker 注册表 {% if enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %} 将在未来的 {% data variables.product.product_name %} 版本中被 {% data variables.product.prodname_container_registry %} 取代，后者将提供更好的容器支持。{% elsif currentVersion == "free-pro-team@latest" %} 被 {% data variables.product.prodname_container_registry %} 取代，后者提供更好的容器支持。 {% endif %} {% if currentVersion == "free-pro-team@latest" %} 要了解如何迁移现有的 Docker 映像以及任何使用它们的工作流程，请参阅“[从 Docker 注册表迁移到 {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry)”。 {% endif %} +**注：**{% data variables.product.prodname_registry %} Docker 注册表 {% ifversion ghes or ghae %} 将在未来的 {% data variables.product.product_name %} 版本中被 {% data variables.product.prodname_container_registry %} 取代，后者将提供更好的容器支持。{% elsif fpt %} 被 {% data variables.product.prodname_container_registry %} 取代，后者提供更好的容器支持。 {% endif %}{% ifversion fpt %}更多信息请参阅“[从 Docker 注册表迁移到 {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry)”。 {% endif %} {% endwarning %} diff --git a/translations/zh-CN/data/reusables/pages/about-private-publishing.md b/translations/zh-CN/data/reusables/pages/about-private-publishing.md index 7a4ff94921..77ac290235 100644 --- a/translations/zh-CN/data/reusables/pages/about-private-publishing.md +++ b/translations/zh-CN/data/reusables/pages/about-private-publishing.md @@ -1 +1 @@ -如果您的项目站点是从使用 {% data variables.product.prodname_ghe_cloud %} 的组织拥有的私有或内部仓库发布的，您可以管理站点的访问控制。 +如果您的项目站点是从使用 {% data variables.product.prodname_ghe_cloud %} 的组织拥有的私有或内部仓库发布的，您可以管理站点的访问控制。 In an {% data variables.product.prodname_emu_enterprise %}, all {% data variables.product.prodname_pages %} sites are privately published. diff --git a/translations/zh-CN/data/reusables/repositories/auto-gen-release-public-beta.md b/translations/zh-CN/data/reusables/repositories/auto-gen-release-public-beta.md new file mode 100644 index 0000000000..1271ce25e0 --- /dev/null +++ b/translations/zh-CN/data/reusables/repositories/auto-gen-release-public-beta.md @@ -0,0 +1 @@ +Automatically generated release notes are currently in public beta and subject to change. diff --git a/translations/zh-CN/data/reusables/repositories/disabling-markdown-rendering.md b/translations/zh-CN/data/reusables/repositories/disabling-markdown-rendering.md new file mode 100644 index 0000000000..86254f64ec --- /dev/null +++ b/translations/zh-CN/data/reusables/repositories/disabling-markdown-rendering.md @@ -0,0 +1,5 @@ +When viewing a Markdown file, you can click {% octicon "code" aria-label="The code icon" %} at the top of the file to disable Markdown rendering and view the file's source instead. + +![Display Markdown as source](/assets/images/help/writing/display-markdown-as-source.png) + +Disabling Markdown rendering enables you to use source view features, such as line linking, which is not possible when viewing rendered Markdown files. diff --git a/translations/zh-CN/data/reusables/repositories/request-security-advisory-cve-id.md b/translations/zh-CN/data/reusables/repositories/request-security-advisory-cve-id.md index 187c39267b..81130eb214 100644 --- a/translations/zh-CN/data/reusables/repositories/request-security-advisory-cve-id.md +++ b/translations/zh-CN/data/reusables/repositories/request-security-advisory-cve-id.md @@ -1,5 +1,3 @@ -如果项目中尚无表示安全漏洞的 CVE 识别码，您可以从 {% data variables.product.prodname_dotcom %} 请求一个 CVE 识别码。 {% data variables.product.prodname_dotcom %} 通常在 72 小时内审核请求。 请求 CVE 识别码不会公开您的安全通告。 如果您的安全通告符合 CVE 条件，{% data variables.product.prodname_dotcom %} 将为您的通告保留 CVE 识别码。 然后，我们将在发布安全通告后发布 CVE 详细信息。 +If you want a CVE identification number for the security vulnerability in your project, and don't already have one, you can request a CVE identification number from {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_dotcom %} 通常在 72 小时内审核请求。 请求 CVE 识别码不会公开您的安全通告。 If your security advisory is eligible for a CVE, {% data variables.product.prodname_dotcom %} will reserve a CVE identification number for your advisory. We'll then publish the CVE details after you make your security advisory public. Anyone with admin permissions to a security advisory can request a CVE identification number. -如果您已经拥有要使用的 CVE，例如，如果您使用 {% data variables.product.prodname_dotcom %} 以外的 CNA，请将其添加到安全通告表。 例如，如果您想要获得与计划在发布时间发送的其他通信一致的通告，则可能会发生这种情况。 - -如果通告表单没有 CVE，我们将在您发布通告时为您请求 CVE。 +If you already have a CVE you want to use, for example, if you use a CVE Numbering Authority (CNA) other than {% data variables.product.prodname_dotcom %}, add the CVE to the security advisory form. 例如，如果您想要获得与计划在发布时间发送的其他通信一致的通告，则可能会发生这种情况。 {% data variables.product.prodname_dotcom %} cannot assign CVEs to your project if it is covered by another CNA. \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/repositories/sidebar-issues.md b/translations/zh-CN/data/reusables/repositories/sidebar-issues.md index 9315535133..4f26f275ab 100644 --- a/translations/zh-CN/data/reusables/repositories/sidebar-issues.md +++ b/translations/zh-CN/data/reusables/repositories/sidebar-issues.md @@ -1,5 +1,5 @@ 2. 在仓库名称下，单击 {% octicon "issue-opened" aria-label="The issues icon" %} **议题**。 - {% ifversion fpt or ghes > 3.1 or ghae-issue-4483 %} + {% ifversion fpt or ghes > 3.1 or ghae-next %} ![议题选项卡](/assets/images/help/repository/repo-tabs-issues.png){% else %} ![Issues tab](/assets/images/enterprise/3.1/help/repository/repo-tabs-issues.png){% endif %} diff --git a/translations/zh-CN/data/reusables/repositories/sidebar-pr.md b/translations/zh-CN/data/reusables/repositories/sidebar-pr.md index 7acae09059..210a2f5160 100644 --- a/translations/zh-CN/data/reusables/repositories/sidebar-pr.md +++ b/translations/zh-CN/data/reusables/repositories/sidebar-pr.md @@ -1,5 +1,5 @@ 1. 在仓库名称下，单击 {% octicon "git-pull-request" aria-label="The pull request icon" %} **拉取请求**。 - {% ifversion fpt or ghes > 3.1 or ghae-issue-4483 %} + {% ifversion fpt or ghes > 3.1 or ghae-next %} ![议题和拉取请求选项卡选择](/assets/images/help/repository/repo-tabs-pull-requests.png){% else %} ![Issues tab](/assets/images/enterprise/3.1/help/repository/repo-tabs-pull-requests.png){% endif %} diff --git a/translations/zh-CN/data/reusables/repositories/workflow-notifications.md b/translations/zh-CN/data/reusables/repositories/workflow-notifications.md index 67eace8635..e23549c869 100644 --- a/translations/zh-CN/data/reusables/repositories/workflow-notifications.md +++ b/translations/zh-CN/data/reusables/repositories/workflow-notifications.md @@ -1,4 +1,4 @@ -如果为 {% data variables.product.prodname_actions %} 启用电子邮件或 web 通知，则在触发的任何工作流程运行完成时，您将收到通知。 通知将包括工作流程运行的状态（包括成功、失败、中立和取消的运行）。 您也可以选择仅在工作流程运行失败时接收通知。 +如果为 {% data variables.product.prodname_actions %} 启用电子邮件或 web 通知，则在触发的任何工作流程运行完成时，您将收到通知。 通知将包括工作流程运行的状态（包括成功、失败、中立和取消的运行）。 您也可以选择仅在工作流程运行失败时接收通知。 For more information about enabling or disabling notifications, see "[About notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)." 计划工作流程的通知将发送给最初创建该工作流程的用户。 如有不同的用户更新工作流程文件中的计划任务语法，后续通知将改为发送给该用户。{% ifversion fpt or ghes > 2.22 %} 如果预定的工作流程禁用后重新启用， 通知将发送给重新启用工作流程的用户，而不是最后修改计划任务语法的用户。{% endif %} diff --git a/translations/zh-CN/data/reusables/saml/about-linked-identities.md b/translations/zh-CN/data/reusables/saml/about-linked-identities.md index 0bb65a0baf..5cf00e40e7 100644 --- a/translations/zh-CN/data/reusables/saml/about-linked-identities.md +++ b/translations/zh-CN/data/reusables/saml/about-linked-identities.md @@ -1,3 +1,3 @@ -您可以查看成员已链接到其 {% data variables.product.product_name %} 帐户的单点登录身份。 如果可用，该条目将包含 SCIM 数据。 更多信息请参阅“[关于 SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)”。 +您可以查看成员已链接到其 {% data variables.product.product_name %} 帐户的单点登录身份。 如果成员将错误的身份链接到其 {% data variables.product.product_name %} 帐户，您可以撤销链接的身份以允许该成员重试。 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 fdfe8d9bb1..a70972c543 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 @@ -1,7 +1,7 @@ | Provider | 支持的密钥 | API slug | | -------- | ----- | -------- | | | | | -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Adafruit IO | Adafruit IO Key | adafruit_io_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Adobe | Adobe Device Token | adobe_device_token{% endif %} @@ -11,73 +11,73 @@ Adobe | Adobe Service Token | adobe_service_token{% endif %} Adobe | Adobe Short-Lived Access Token | adobe_short_lived_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Adobe | Adobe JSON Web Token | adobe_jwt{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Alibaba Cloud | Alibaba Cloud Access Key ID | alibaba_cloud_access_key_id{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Alibaba Cloud | Alibaba Cloud Access Key Secret | alibaba_cloud_access_key_secret{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Amazon Web Services (AWS) | Amazon AWS Access Key ID | aws_access_key_id{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Amazon Web Services (AWS) | Amazon AWS Secret Access Key | aws_secret_access_key{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Amazon Web Services (AWS) | Amazon AWS Session Token | aws_session_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Amazon Web Services (AWS) | Amazon AWS Temporary Access Key ID | aws_temporary_access_key_id{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Asana | Asana Personal Access Token | asana_personal_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Atlassian | Atlassian API Token | atlassian_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Atlassian | Atlassian JSON Web Token | atlassian_jwt{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Atlassian | Bitbucket Server Personal Access Token | bitbucket_server_personal_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Azure | Azure SAS Token | azure_sas_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Azure | Azure Service Management Certificate | azure_management_certificate{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Azure | Azure SQL Connection String | azure_sql_connection_string{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Azure | Azure Storage Account Key | azure_storage_account_key{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Beamer | Beamer API Key | beamer_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Checkout.com | Checkout.com Production Secret Key | checkout_production_secret_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Checkout.com | Checkout.com Test Secret Key | checkout_test_secret_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Clojars | Clojars Deploy Token | clojars_deploy_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} CloudBees CodeShip | CloudBees CodeShip Credential | codeship_credential{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Contentful | Contentful Personal Access Token | contentful_personal_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Databricks | Databricks Access Token | databricks_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Discord | Discord Bot Token | discord_bot_token{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Doppler | Doppler Personal Token | doppler_personal_token{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Doppler | Doppler Service Token | doppler_service_token{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Doppler | Doppler CLI Token | doppler_cli_token{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Doppler | Doppler SCIM Token | doppler_scim_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Doppler | Doppler Audit Token | doppler_audit_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Dropbox | Dropbox Access Token | dropbox_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Dropbox | Dropbox Short Lived Access Token | dropbox_short_lived_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Duffel | Duffel Live Access Token | duffel_live_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Duffel | Duffel Test Access Token | duffel_test_access_token{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Dynatrace | Dynatrace Access Token | dynatrace_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Dynatrace | Dynatrace Internal Token | dynatrace_internal_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} EasyPost | EasyPost Production API Key | easypost_production_api_key{% endif %} @@ -87,17 +87,17 @@ EasyPost | EasyPost Test API Key | easypost_test_api_key{% endif %} Facebook | Facebook Access Token | facebook_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Fastly | Fastly API Token | fastly_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Finicity | Finicity App Key | finicity_app_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Flutterwave | Flutterwave Live API Secret Key | flutterwave_live_api_secret_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Flutterwave | Flutterwave Test API Secret Key | flutterwave_test_api_secret_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Frame.io | Frame.io JSON Web Token | frameio_jwt{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Frame.io| Frame.io Developer Token | frameio_developer_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} FullStory | FullStory API Key | fullstory_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} GitHub | GitHub Personal Access Token | github_personal_access_token{% endif %} @@ -107,29 +107,29 @@ GitHub | GitHub OAuth Access Token | github_oauth_access_token{% endif %} GitHub | GitHub Refresh Token | github_refresh_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} GitHub | GitHub App Installation Access Token | github_app_installation_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} GitHub | GitHub SSH Private Key | github_ssh_private_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} GoCardless | GoCardless Live Access Token | gocardless_live_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} GoCardless | GoCardless Sandbox Access Token | gocardless_sandbox_access_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Google | Firebase Cloud Messaging Server Key | firebase_cloud_messaging_server_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Google | Google API Key | google_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Google | Google Cloud Private Key ID | google_cloud_private_key_id{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Google | Google Cloud Storage Access Key Secret | google_cloud_storage_access_key_secret{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Google | Google Cloud Storage Service Account Access Key ID | google_cloud_storage_service_account_access_key_id{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Google | Google Cloud Storage User Access Key ID | google_cloud_storage_user_access_key_id{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Grafana | Grafana API Key | grafana_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Hashicorp Terraform | Terraform Cloud / Enterprise API Token | terraform_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Hubspot | Hubspot API Key | hubspot_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Intercom | Intercom Access Token | intercom_access_token{% endif %} @@ -137,9 +137,9 @@ Intercom | Intercom Access Token | intercom_access_token{% endif %} Ionic | Ionic Personal Access Token | ionic_personal_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Ionic | Ionic Refresh Token | ionic_refresh_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} JFrog | JFrog Platform Access Token | jfrog_platform_access_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} JFrog | JFrog Platform API Key | jfrog_platform_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Linear | Linear API Key | linear_api_key{% endif %} @@ -149,15 +149,23 @@ Linear | Linear OAuth Access Token | linear_oauth_access_token{% endif %} Lob | Lob Live API Key | lob_live_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Lob | Lob Test API Key | lob_test_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Mailchimp | Mailchimp API Key | mailchimp_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Mailgun | Mailgun API Key | mailgun_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} MessageBird | MessageBird API Key | messagebird_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} +New Relic | New Relic Personal API Key | new_relic_personal_api_key{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +New Relic | New Relic REST API Key | new_relic_rest_api_key{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +New Relic | New Relic Insights Query Key | new_relic_insights_query_key{% endif %} +{%- ifversion fpt or ghes > 3.2 %} +New Relic | New Relic License Key | new_relic_license_key{% endif %} +{%- ifversion fpt or ghes > 2.22 or ghae %} npm | npm Access Token | npm_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} NuGet | NuGet API Key | nuget_api_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Onfido | Onfido Live API Token | onfido_live_api_token{% endif %} @@ -165,75 +173,75 @@ Onfido | Onfido Live API Token | onfido_live_api_token{% endif %} Onfido | Onfido Sandbox API Token | onfido_sandbox_api_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} OpenAI | OpenAI API Key | openai_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Palantir | Palantir JSON Web Token | palantir_jwt{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} PlanetScale | PlanetScale Database Password | planetscale_database_password{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} PlanetScale | PlanetScale OAuth Token | planetscale_oauth_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} PlanetScale | PlanetScale Service Token | planetscale_service_token{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Plivo | Plivo Auth ID | plivo_auth_id{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Plivo | Plivo Auth Token | plivo_auth_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Postman | Postman API Key | postman_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Proctorio | Proctorio Consumer Key | proctorio_consumer_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Proctorio | Proctorio Linkage Key | proctorio_linkage_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Proctorio | Proctorio Registration Key | proctorio_registration_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Proctorio | Proctorio Secret Key | proctorio_secret_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Pulumi | Pulumi Access Token | pulumi_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} PyPI | PyPI API Token | pypi_api_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} RubyGems | RubyGems API Key | rubygems_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Samsara | Samsara API Token | samsara_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Samsara | Samsara OAuth Access Token | samsara_oauth_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} SendGrid | SendGrid API Key | sendgrid_api_key{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Sendinblue | Sendinblue API Key | sendinblue_api_key{% endif %} -{%- ifversion fpt or ghes > 3.2 or ghae-next %} +{%- ifversion fpt or ghes > 3.2 %} Sendinblue | Sendinblue SMTP Key | sendinblue_smtp_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Shippo | Shippo Live API Token | shippo_live_api_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Shippo | Shippo Test API Token | shippo_test_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Shopify | Shopify App Shared Secret | shopify_app_shared_secret{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Shopify | Shopify Access Token | shopify_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Shopify | Shopify Custom App Access Token | shopify_custom_app_access_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Shopify | Shopify Private App Password | shopify_private_app_password{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Slack | Slack API Token | slack_api_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Slack | Slack Incoming Webhook URL | slack_incoming_webhook_url{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Slack | Slack Workflow Webhook URL | slack_workflow_webhook_url{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} SSLMate | SSLMate API Key | sslmate_api_key{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} SSLMate | SSLMate Cluster Secret | sslmate_cluster_secret{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Stripe | Stripe API Key | stripe_api_key{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Stripe | Stripe Live API Secret Key | stripe_live_secret_key{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Stripe | Stripe Test API Secret Key | stripe_test_secret_key{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Stripe | Stripe Live API Restricted Key | stripe_live_restricted_key{% endif %} -{%- ifversion fpt or ghes > 3.0 or ghae-next %} +{%- ifversion fpt or ghes > 3.0 or ghae %} Stripe | Stripe Test API Restricted Key | stripe_test_restricted_key{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Stripe | Stripe Webhook Signing Secret | stripe_webhook_signing_secret{% endif %} @@ -241,9 +249,9 @@ Stripe | Stripe Webhook Signing Secret | stripe_webhook_signing_secret{% endif % Tableau | Tableau Personal Access Token | tableau_personal_access_token{% endif %} {%- ifversion fpt or ghes > 3.1 or ghae-next %} Telegram | Telegram Bot Token | telegram_bot_token{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Tencent Cloud | Tencent Cloud Secret ID | tencent_cloud_secret_id{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Twilio | Twilio Account String Identifier | twilio_account_sid{% endif %} -{%- ifversion fpt or ghes > 2.22 or ghae-next %} +{%- ifversion fpt or ghes > 2.22 or ghae %} Twilio | Twilio API Key | twilio_api_key{% endif %} diff --git a/translations/zh-CN/data/reusables/sponsors/add-welcome-message.md b/translations/zh-CN/data/reusables/sponsors/add-welcome-message.md new file mode 100644 index 0000000000..8962236ad1 --- /dev/null +++ b/translations/zh-CN/data/reusables/sponsors/add-welcome-message.md @@ -0,0 +1 @@ +1. Optionally, type a welcome message for the tier. ![Add welcome message](/assets/images/help/sponsors/add-a-welcome-message.png) \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/sponsors/tier-details.md b/translations/zh-CN/data/reusables/sponsors/tier-details.md index cd716043e6..d0ba284139 100644 --- a/translations/zh-CN/data/reusables/sponsors/tier-details.md +++ b/translations/zh-CN/data/reusables/sponsors/tier-details.md @@ -1,4 +1,4 @@ -您可以创建最多 10 个一次性赞助等级和 10 个月度等级供赞助者选择。 每个等级都有自己的一次性或月度付款金额（以美元计），您可以选择对自定义金额启用等级。 此外，您可以选择为自定义金额启用等级（月度和一次性）。 +You can create up to 10 one-time sponsorship tiers and 10 monthly tiers for sponsors to choose from. 每个等级都有自己的一次性或月度付款金额（以美元计），您可以选择对自定义金额启用等级。 此外，您可以选择为自定义金额启用等级（月度和一次性）。 您可以自定义每个等级的奖励。 例如，一个等级的奖励可以包括： - 提早使用新版本 @@ -7,4 +7,6 @@ - 每周时事通讯更新 - 您的赞助者将享受其他奖励 ✨ +You can include a welcome message with information about accessing or receiving rewards, which will be visible after payment and in the welcome email. + 一旦您发布某个等级，便不能编辑这个等级的价格。 而只能撤销该等级并新建一个等级。 现有赞助者将保留在已撤销的等级中，直到他们更改其赞助等级、取消其赞助或其一次性赞助期满。 diff --git a/translations/zh-CN/data/reusables/ssh/add-ssh-key-to-ssh-agent-commandline.md b/translations/zh-CN/data/reusables/ssh/add-ssh-key-to-ssh-agent-commandline.md index 415f86736d..9bed61119b 100644 --- a/translations/zh-CN/data/reusables/ssh/add-ssh-key-to-ssh-agent-commandline.md +++ b/translations/zh-CN/data/reusables/ssh/add-ssh-key-to-ssh-agent-commandline.md @@ -1,3 +1,3 @@ ```shell -$ ssh-add ~/.ssh/id_ed25519 +$ ssh-add ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %} ``` diff --git a/translations/zh-CN/data/reusables/ssh/add-ssh-key-to-ssh-agent.md b/translations/zh-CN/data/reusables/ssh/add-ssh-key-to-ssh-agent.md index 35d15c8f52..43243b9f14 100644 --- a/translations/zh-CN/data/reusables/ssh/add-ssh-key-to-ssh-agent.md +++ b/translations/zh-CN/data/reusables/ssh/add-ssh-key-to-ssh-agent.md @@ -1 +1 @@ -如果您创建了不同名称的密钥，或者您要添加不同名称的现有密钥，请将命令中的 *id_ed25519* 替换为您的私钥文件的名称。 +If you created your key with a different name, or if you are adding an existing key that has a different name, replace *id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}* in the command with the name of your private key file. diff --git a/translations/zh-CN/data/reusables/user_settings/generate_new_token.md b/translations/zh-CN/data/reusables/user_settings/generate_new_token.md new file mode 100644 index 0000000000..91e2591503 --- /dev/null +++ b/translations/zh-CN/data/reusables/user_settings/generate_new_token.md @@ -0,0 +1 @@ +1. 单击 **Generate new token（生成新令牌）**。 ![生成新令牌按钮](/assets/images/help/settings/generate_new_token.png) \ No newline at end of file diff --git a/translations/zh-CN/data/ui.yml b/translations/zh-CN/data/ui.yml index 9581ff8224..2a73f2964e 100644 --- a/translations/zh-CN/data/ui.yml +++ b/translations/zh-CN/data/ui.yml @@ -30,9 +30,10 @@ toc: guides: 指南 whats_new: 新增内容 pages: - article_version: '文章版本：' + article_version: 'Article version' miniToc: 本文内容 contributor_callout: 这篇文章的参与者和维护者是 + all_enterprise_releases: All Enterprise releases errors: oops: 哎呀！ something_went_wrong: 看来出现了错误。 @@ -155,13 +156,17 @@ product_sublanding: learning_paths_desc: 学习路径是一系列帮助您掌握特定主题的指南。 guides: '{{ productMap[currentProduct].name }} 指南' more_guides: 更多指南 - no_result: 抱歉，没有与过滤条件匹配的指南。 load_more: 加载更多指南 all_guides: '所有 {{ productMap[currentProduct].name }} 指南' + filter_instructions: Filter the guide list using these controls filters: type: 类型 topic: 主题 all: 所有 + guides_found: + multiple: '{n} guides found' + one: 1 guide found + none: No guides found guide_types: overview: 概览 quick_start: 快速入门 diff --git a/translations/zh-CN/data/variables/product.yml b/translations/zh-CN/data/variables/product.yml index 7dac8c1601..1270f434b9 100644 --- a/translations/zh-CN/data/variables/product.yml +++ b/translations/zh-CN/data/variables/product.yml @@ -76,6 +76,14 @@ prodname_actions: 'GitHub Actions' prodname_debug: 'GitHub Debug' #GitHub Discussions prodname_discussions: 'GitHub Discussions' +#GitHub Enterprise Managed Users +prodname_emu_idp_application: 'GitHub Enterprise Managed User' +prodname_emus: 'Enterprise Managed Users' +prodname_managed_user: 'managed user' +prodname_managed_users: 'managed users' +prodname_managed_users_caps: 'Managed users' +prodname_emu_enterprise: 'enterprise with managed users' +prodname_emu_org: 'organization with managed users' #GitHub Issues prodname_github_issues: 'GitHub Issues' #GitHub Packages @@ -94,6 +102,7 @@ prodname_security_center: '安全中心' #Codespaces prodname_codespaces: 'Codespaces' prodname_github_codespaces: 'GitHub Codespaces' +prodname_serverless: 'web-based editor' #GitHub resources: blog, jobs, Learning Lab prodname_gcf: 'GitHub Community Support' prodname_blog: 'GitHub 博客' @@ -135,6 +144,8 @@ prodname_dependabot_version_updates: 'Dependabot 版本更新' #GitHub Archive Program prodname_archive: 'GitHub 存档计划' prodname_arctic_vault: 'Arctic 代码库' +#GitHub Copilot +prodname_copilot: 'GitHub Copilot' #Links product_url: >- {% ifversion fpt %}github.com{% else %}[hostname]{% endif %} diff --git a/translations/zh-CN/data/variables/release_candidate.yml b/translations/zh-CN/data/variables/release_candidate.yml index e6ddf079ac..ec65ef6f94 100644 --- a/translations/zh-CN/data/variables/release_candidate.yml +++ b/translations/zh-CN/data/variables/release_candidate.yml @@ -1,2 +1,2 @@ --- -version: enterprise-server@3.2 +version: ''